On Thursday 26 December 2002 12:59 pm, Philip J. Koenig wrote: > On 26 Dec 2002 at 11:56, Kent Stewart boldly uttered: > > On Thursday 26 December 2002 03:35 am, Philip J. Koenig wrote: > > [snip] > > > > Have things improved in the meantime? Is there an easy way to > > > upgrade Portupgrade without removing everything and > > > re-installing? I currently have the 20020706 version installed. > > > > You version is so far back that the upgrade is hopeless. You have > > things that no long exist as parts of portupgrade and your version > > can't deal with that. It is easier if you delete the portupgrade, > > ruby-*, pkg_tartup, and what ever is left and reinstall it. > > > > FWIW, it works flawlessly now. I just recently upgraded to the 1216 > > version by using "portupgrade -rpuf ruby". > > Thanks for the tip, although I must admit I'm kinda surprised that a > 5-month-old version of anything is considered so "ancient" as to be > "un-upgradeable"... particularly a program designed to upgrade other > programs.. <shrug>
The break point is around 20020907 and I can't be precise. Anything before that can't deal with ports that have disappeared. If you have a version before that, the easiest way is to delete portupgrade and its dependancies and reinstall it. Everything from ruby-1.6.8 to portupgrade is new so you don't lose any time but you do get a clean install on the first try. Running portsdb -F produces signal errors when you have a port installed that is no longer in the port tree. I don't remember if -fu worked at that point or not. Kent > > But I'm not really complaining, portupgrade is a boon to all > humanity. :-) -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
