Re: ports hosed
On Sunday 04 April 2004 05:24 pm, you wrote: > > But I guess I'm not completely convinced that it'll take far less > > time. I started the K3b port install Friday evening... I'm on about > > the third iteration of portupgrade, and each iteration is an > > _extremely_ long process on this old 350 MHz system with 211+ ports. > > Several of the port installs require input from the console to > > continue, so I've been friggin' chained to this desk all weekend > > long. Too much work, too much time! > > I understand that problem. I have a P-II 400 that I don't build anything > on because it takes so long. I did the portupgrade -rf expat2 on an AMD > 2400+ XP and complained because it ran for 13 hours. If you use ratios, > which don't always apply, your 350 is close to 16x slower. It is 8x by > the clock and 2x for hardware speed ups. Whew! It took almost a month, but I think I made it - well, almost... I've had an unbelievable string of mishaps (UPS died, travel, etc, etc). I re-started 'portupgrade -rf textpproc/expat2' Thursday, and early this morning was able to startx & see KDE 3.2 for the first time - about a 3 day process to build on this 350 MHz machine. I say "almost" because two ports are still hosed: samba and openoffice. I'm thinking the best strategy from here is to remove these ports & re-install as pre-built packages... any analysis or comments on this approach? Best Rgds, Jay ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports hosed
On Monday 03 May 2004 05:20 pm, Jay Moore wrote: > On Sunday 04 April 2004 05:24 pm, you wrote: > > > But I guess I'm not completely convinced that it'll take far less > > > time. I started the K3b port install Friday evening... I'm on > > > about the third iteration of portupgrade, and each iteration is > > > an _extremely_ long process on this old 350 MHz system with 211+ > > > ports. Several of the port installs require input from the > > > console to continue, so I've been friggin' chained to this desk > > > all weekend long. Too much work, too much time! > > > > I understand that problem. I have a P-II 400 that I don't build > > anything on because it takes so long. I did the portupgrade -rf > > expat2 on an AMD 2400+ XP and complained because it ran for 13 > > hours. If you use ratios, which don't always apply, your 350 is > > close to 16x slower. It is 8x by the clock and 2x for hardware > > speed ups. > > Whew! It took almost a month, but I think I made it - well, > almost... I've had an unbelievable string of mishaps (UPS died, > travel, etc, etc). I re-started 'portupgrade -rf textpproc/expat2' > Thursday, and early this morning was able to startx & see KDE 3.2 for > the first time - about a 3 day process to build on this 350 MHz > machine. > There is no substitute for speed. Last weekend, I did a -prRfa on ruby and it had updated all 303 ports a little over 12 hours later. > I say "almost" because two ports are still hosed: samba and > openoffice. I'm thinking the best strategy from here is to remove > these ports & re-install as pre-built packages... any analysis or > comments on this approach? I can't think of anything. I don't use either but have seen a number of messages on OO. Since I don't user either, I didn't pay attention to what the problems were. Those are 2 ports that I wouldn't willingly add to my sacrificial system :). The snapshots.jp.freebsd.org site looks like it has current port packages for both 4-stable and 5-current. A download and pkg_add would probably much faster than a build from source :). Kent > > Best Rgds, > Jay > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports hosed
On Sunday 04 April 2004 04:08 pm, John Duffey wrote: > > So - again, is there any way to cleanly remove and re-install > > the entire ports tree from the 5.2 cd? > > Try > rm -r /usr/ports > > then << snipped for brevity >> --- > > I'd recommend you try and fix whatever it is that's gone wrong > with k3b though. > > It'll take far less time. Thanks for the detailed procedure! I think I get the point that you and Kent are trying to make. Some patches/ upgrades to the "base" 5.2 system will be required after I get there. But I guess I'm not completely convinced that it'll take far less time. I started the K3b port install Friday evening... I'm on about the third iteration of portupgrade, and each iteration is an _extremely_ long process on this old 350 MHz system with 211+ ports. Several of the port installs require input from the console to continue, so I've been friggin' chained to this desk all weekend long. Too much work, too much time! Reading /usr/ports/UPGRADING still worries me when I get to the part about KDE... at some point during the current "portupgrade" I expect my Konqueror windows will start dying off. And I still don't know what I did to (e.g.) my OpenOffice install when I responded to the prompts from pkgdb -F with "Delete". On the + side, I have learned some things about FreeBSD which is why I'm here in the first place. I think I'm going to take your (and Kent's) advice, and let this thing run its course. I've got new info re SSL and the instructions in the UPDATING file - and of course the "bulldozer" procedure if that fails. But best of all, I've got this list :) I'll close this thread for now with my thanks to all. Future issues will be posted to the list with the words "[5.2 portupgrade hairball]" in the subject (forewarned is forearmed :) Thanks Again, Jay ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports hosed
On 04 Apr, Jay Moore <[EMAIL PROTECTED]> wrote: > So - again, is there any way to cleanly remove and re-install > the entire ports tree from the 5.2 cd? Try rm -r /usr/ports then sysinstall Follow options: =Configure (do post install configuration of FreeBSD) -> =Distributions (Install additional distribution sets) -> =Ports (The FreeBSD Ports Collection) (Enter) * =CD/DVD (Install from a FreeBSD CD/DVD) * Should get the whole ports shebang back down to 5.2 CD Dist standards. You'll then need to reinstate the index as it was then... cd /usr/ports portsdb -Uu To get rid of every package you have installed currently, try pkg_delete * which should de-install every package you've got, and then rebuild everything you need, starting cd /usr/ports/net/cvsup/ make install clean to build cvsup. I assume you've already configured the example script from /usr/share/examples/cvsup/ports-supfile so we'll skip directly into cvsup -g /usr/share/examples/cvsup/ports-supfile cd /usr/ports/sysutils/portupgrade make install clean portinstall (any port you like) I'd recommend you try and fix whatever it is that's gone wrong with k3b though. It'll take far less time. John -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports hosed
On Sunday 04 April 2004 01:44 pm, Jay Moore wrote: > On Sunday 04 April 2004 03:29 pm, Kent Stewart wrote: > > > Well, done is done... no way I can "back up", and re-visit > > > questions that I've already answered incorrectly. And meanwhile > > > my machine is still crunching forward with the last "portupgrade > > > -a" that I did - this will likely continue for quite some time as > > > it reports 211 ports (and this # keeps growing!) I believe I've > > > lost control of the f**g thing... > > > > > > So - is there a way to go back to "ground zero"?... to just > > > remove everything from the ports tree, and re-install from the > > > 5.2 cd? > > > > I got to thinking about this more. I think you should have taken > > care of all of the problems in /usr/ports/UPDATING before you fire > > off portupgrade -a. You would have probably still bumped into the > > openssl problem but it is a good idea for a start. > > Agreed... _if_ I had known to read /usr/ports/UPDATING I might have > avoided the chaos I've created. For that matter if I'd known that the > K3b port was going to suck down a bazillion dependencies, I would > have foregone this whole quagmire :) > > But I didn't. I've learned a little bit, but I am where I am, and I > have no confidence that this thing is going to conclude in a stable > situation anytime soon - at least not without a lot more time and > effort. > > So - again, is there any way to cleanly remove and re-install the > entire ports tree from the 5.2 cd? You have the port structure on the CD. You can remove /usr/ports/* and then do the install. You should be aware that your are going back to a system with a security notice attached to openssl. You aren't saving problems but could be introducing a port security risk instead. If you haven't upgraded to 5.2.1, you already have a system with a security risk. FWIW, I have a clean port system on both 5-current and 4-stable. So, it is possible. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports hosed
On Sunday 04 April 2004 03:29 pm, Kent Stewart wrote: > > Well, done is done... no way I can "back up", and re-visit questions > > that I've already answered incorrectly. And meanwhile my machine is > > still crunching forward with the last "portupgrade -a" that I did - > > this will likely continue for quite some time as it reports 211 ports > > (and this # keeps growing!) I believe I've lost control of the f**g > > thing... > > > > So - is there a way to go back to "ground zero"?... to just remove > > everything from the ports tree, and re-install from the 5.2 cd? > > I got to thinking about this more. I think you should have taken care of > all of the problems in /usr/ports/UPDATING before you fire off > portupgrade -a. You would have probably still bumped into the openssl > problem but it is a good idea for a start. Agreed... _if_ I had known to read /usr/ports/UPDATING I might have avoided the chaos I've created. For that matter if I'd known that the K3b port was going to suck down a bazillion dependencies, I would have foregone this whole quagmire :) But I didn't. I've learned a little bit, but I am where I am, and I have no confidence that this thing is going to conclude in a stable situation anytime soon - at least not without a lot more time and effort. So - again, is there any way to cleanly remove and re-install the entire ports tree from the 5.2 cd? Thanks, Jay ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports hosed
On Sunday 04 April 2004 01:10 pm, Jay Moore wrote: > On Sunday 04 April 2004 02:27 pm, Kent Stewart wrote: > > > Bottom line here (in my case) is this: I'm afraid my ports tree > > > may be BFU; this all started when I tried to install the "K3b" > > > port which apparently has a bazillion dependencies. At least one > > > of the tar.gz files couldn't be located, and things have kind of > > > gone downhill from there :(For me, I'm afraid that salvation > > > may require "wiping" the entire ports tree, and re-installing it > > > from the 5.2 cd. Is there a safe & clean way to do that? > > > > It was the closest thing to openssl. There is what I think is a > > problem with ports such as openssl. It is in the makefile to > > portupgrade but if you do a make search, it doesn't show up. When > > you see an obvious link problem like you saw, check if you have it > > installed. If you do/don't just upgrade/install what is missing. > > Well, done is done... no way I can "back up", and re-visit questions > that I've already answered incorrectly. And meanwhile my machine is > still crunching forward with the last "portupgrade -a" that I did - > this will likely continue for quite some time as it reports 211 ports > (and this # keeps growing!) I believe I've lost control of the f**g > thing... > > So - is there a way to go back to "ground zero"?... to just remove > everything from the ports tree, and re-install from the 5.2 cd? > Why would you want to go back. I think that is comparable to rejecting brain surgery and asking them to reinsert a tumor. There are problems that occur and you can't always blindly run portupgrade -a. Most of the time, the fix is really simple and you fix it and move on. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports hosed
On Sunday 04 April 2004 02:27 pm, Kent Stewart wrote: > > Bottom line here (in my case) is this: I'm afraid my ports tree may > > be BFU; this all started when I tried to install the "K3b" port which > > apparently has a bazillion dependencies. At least one of the tar.gz > > files couldn't be located, and things have kind of gone downhill from > > there :(For me, I'm afraid that salvation may require "wiping" > > the entire ports tree, and re-installing it from the 5.2 cd. Is > > there a safe & clean way to do that? > > It was the closest thing to openssl. There is what I think is a problem > with ports such as openssl. It is in the makefile to portupgrade but if > you do a make search, it doesn't show up. When you see an obvious link > problem like you saw, check if you have it installed. If you do/don't > just upgrade/install what is missing. Well, done is done... no way I can "back up", and re-visit questions that I've already answered incorrectly. And meanwhile my machine is still crunching forward with the last "portupgrade -a" that I did - this will likely continue for quite some time as it reports 211 ports (and this # keeps growing!) I believe I've lost control of the f**g thing... So - is there a way to go back to "ground zero"?... to just remove everything from the ports tree, and re-install from the 5.2 cd? Thanks, Jay ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports hosed
On Sunday 04 April 2004 12:27 pm, Kent Stewart wrote: > On Sunday 04 April 2004 12:21 pm, Jay Moore wrote: > > On Sunday 04 April 2004 08:07 am, Kent Stewart wrote: > > > > # portupgrade -f lang/ruby18 > > > > Stale dependency: ruby-1.8.1_2 --> openssl-0.9.7d -- manually > > > > run 'pkgdb -F' to fix, or specify -O to force. > > > > # pkgdb -F > > > > ---> Checking the package registry database > > > > Stale dependency: openldap-client-2.1.29 -> openssl-0.9.7d > > > > (security/openssl): openoffice-1.1.0_1 (score:23%) ? > > > > > > > > > > What is this? I don't understand the question... Is this > > > > documented anywhere? > > > > > > You didn't do a portupgrade -rRa. The easy way is to upgrade or > > > install openssl-0.9.7d. > > > > Thanks, Kent. I was following the procedure in /usr/ports/UPDATING, > > and the question seemed so out of context... I mean > > "openoffice-1.1.0_1(score:23%)" - what's with that? > > > > Anyway, as I read ports-using.html from the Handbook, portupgrade > > -a is a "superset" of "portupgrade -rRa"... is that correct? > > > > Bottom line here (in my case) is this: I'm afraid my ports tree may > > be BFU; this all started when I tried to install the "K3b" port > > which apparently has a bazillion dependencies. At least one of the > > tar.gz files couldn't be located, and things have kind of gone > > downhill from there :(For me, I'm afraid that salvation may > > require "wiping" the entire ports tree, and re-installing it from > > the 5.2 cd. Is there a safe & clean way to do that? > > It was the closest thing to openssl. There is what I think is a > problem with ports such as openssl. It is in the makefile to > portupgrade but if you do a make search, it doesn't show up. When you > see an obvious link problem like you saw, check if you have it > installed. If you do/don't just upgrade/install what is missing. It is a dependancy to ruby-1.8 but it wasn't installed/upgraded for some reason. The same logic for a solution applies. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports hosed
On Sunday 04 April 2004 12:21 pm, Jay Moore wrote: > On Sunday 04 April 2004 08:07 am, Kent Stewart wrote: > > > # portupgrade -f lang/ruby18 > > > Stale dependency: ruby-1.8.1_2 --> openssl-0.9.7d -- manually run > > > 'pkgdb -F' to fix, or specify -O to force. > > > # pkgdb -F > > > ---> Checking the package registry database > > > Stale dependency: openldap-client-2.1.29 -> openssl-0.9.7d > > > (security/openssl): openoffice-1.1.0_1 (score:23%) ? > > > > > > What is this? I don't understand the question... Is this > > > documented anywhere? > > > > You didn't do a portupgrade -rRa. The easy way is to upgrade or > > install openssl-0.9.7d. > > Thanks, Kent. I was following the procedure in /usr/ports/UPDATING, > and the question seemed so out of context... I mean > "openoffice-1.1.0_1(score:23%)" - what's with that? > > Anyway, as I read ports-using.html from the Handbook, portupgrade -a > is a "superset" of "portupgrade -rRa"... is that correct? > > Bottom line here (in my case) is this: I'm afraid my ports tree may > be BFU; this all started when I tried to install the "K3b" port which > apparently has a bazillion dependencies. At least one of the tar.gz > files couldn't be located, and things have kind of gone downhill from > there :(For me, I'm afraid that salvation may require "wiping" > the entire ports tree, and re-installing it from the 5.2 cd. Is > there a safe & clean way to do that? > It was the closest thing to openssl. There is what I think is a problem with ports such as openssl. It is in the makefile to portupgrade but if you do a make search, it doesn't show up. When you see an obvious link problem like you saw, check if you have it installed. If you do/don't just upgrade/install what is missing. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports hosed
On Sunday 04 April 2004 08:07 am, Kent Stewart wrote: > > # portupgrade -f lang/ruby18 > > Stale dependency: ruby-1.8.1_2 --> openssl-0.9.7d -- manually run > > 'pkgdb -F' to fix, or specify -O to force. > > # pkgdb -F > > ---> Checking the package registry database > > Stale dependency: openldap-client-2.1.29 -> openssl-0.9.7d > > (security/openssl): openoffice-1.1.0_1 (score:23%) ? > > What is this? I don't understand the question... Is this documented > > anywhere? > > You didn't do a portupgrade -rRa. The easy way is to upgrade or install > openssl-0.9.7d. Thanks, Kent. I was following the procedure in /usr/ports/UPDATING, and the question seemed so out of context... I mean "openoffice-1.1.0_1(score:23%)" - what's with that? Anyway, as I read ports-using.html from the Handbook, portupgrade -a is a "superset" of "portupgrade -rRa"... is that correct? Bottom line here (in my case) is this: I'm afraid my ports tree may be BFU; this all started when I tried to install the "K3b" port which apparently has a bazillion dependencies. At least one of the tar.gz files couldn't be located, and things have kind of gone downhill from there :(For me, I'm afraid that salvation may require "wiping" the entire ports tree, and re-installing it from the 5.2 cd. Is there a safe & clean way to do that? Thanks, Jay ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports hosed
Jay Moore wrote: # portupgrade -f lang/ruby18 Stale dependency: ruby-1.8.1_2 --> openssl-0.9.7d -- manually run 'pkgdb -F' to fix, or specify -O to force. # pkgdb -F ---> Checking the package registry database Stale dependency: openldap-client-2.1.29 -> openssl-0.9.7d (security/openssl): openoffice-1.1.0_1 (score:23%) ? ([y]es/[n]o/[a]ll) [no] New dependency? (? to help): ? [Enter] to skip, [Ctrl]+[D] to delete, [.][Enter] to abort, [Tab] to complete New dependency? (? to help): What is this? I don't understand the question... Is this documented anywhere? I had the same thing happen earlier this week. I just installed openssl form the ports (security/openssl). I think this is due to a change in ruby's dependancies since the security advisory of a couple of weeks ago (FreeBSD-SA-04:05.openssl). -- Clint Gilders <[EMAIL PROTECTED]> Director of Technology Services OnlineHobbyist.com, Inc. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports hosed
On Saturday 03 April 2004 11:00 pm, Vulpes Velox wrote: > On Sun, 4 Apr 2004 01:53:11 -0600 > > Jay Moore <[EMAIL PROTECTED]> wrote: > > FreeBSD 5.2 installed from the cd a couple of weeks ago: > > > > I guess I've stepped into it, somehow... the sequence was: > > > > # cvsup -g -L 2 /root/ports-supfile > > # pkgdb -F > > # portupgrade -a > > Post where it failed at... this does not provide much to go on... > > > The failure appeared to be the result of inability to find a > > distfile: > > "docbook-xsl-1.65.1.tar.gz" > > > > So I manually d/l this file from sourceforge, copied it into > > /usr/ports/ distfiles, and ran 'portupgrade -a' again. Got > > following error: > > > > /usr/local/sbin/portupgrade:35:in `require': No such file to load > > -- pkgtools (LoadError) > > from /usr/local/sbin/portupgrade:35 > > May be a pkgdb, index problem, or something like that... delete > portupgrade and reinstalling it using the port... no run pkgdb -fu... > this will reinstall portupgrade and rebuild the pkg index or > whatever... you may aslo want to try a make index first... IIRC, this is the message that pops up when ruby has been upgraded from 1.6 to 1.8 and portupgrade hasn't been rebuilt. See /usr/ports/UPDATING for details on upgrading porupgrade and ruby. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports hosed
On Sunday 04 April 2004 03:26 am, Kris Kennaway wrote: > Looks like you need to follow some of the steps in > /usr/ports/UPDATING (specifically, related to ruby). OK, read UPDATING & here's the drill: Steps 1) & 2) went OK, but then: # portupgrade -f lang/ruby18 Stale dependency: ruby-1.8.1_2 --> openssl-0.9.7d -- manually run 'pkgdb -F' to fix, or specify -O to force. # pkgdb -F ---> Checking the package registry database Stale dependency: openldap-client-2.1.29 -> openssl-0.9.7d (security/openssl): openoffice-1.1.0_1 (score:23%) ? ([y]es/[n]o/[a]ll) [no] New dependency? (? to help): ? [Enter] to skip, [Ctrl]+[D] to delete, [.][Enter] to abort, [Tab] to complete New dependency? (? to help): What is this? I don't understand the question... Is this documented anywhere? Thanks, Jay ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports hosed
On Sun, 4 Apr 2004 01:53:11 -0600 Jay Moore <[EMAIL PROTECTED]> wrote: > FreeBSD 5.2 installed from the cd a couple of weeks ago: > > I guess I've stepped into it, somehow... the sequence was: > > # cvsup -g -L 2 /root/ports-supfile > # pkgdb -F > # portupgrade -a Post where it failed at... this does not provide much to go on... > The failure appeared to be the result of inability to find a > distfile: > "docbook-xsl-1.65.1.tar.gz" > > So I manually d/l this file from sourceforge, copied it into > /usr/ports/ distfiles, and ran 'portupgrade -a' again. Got following > error: > > /usr/local/sbin/portupgrade:35:in `require': No such file to load -- > pkgtools (LoadError) > from /usr/local/sbin/portupgrade:35 May be a pkgdb, index problem, or something like that... delete portupgrade and reinstalling it using the port... no run pkgdb -fu... this will reinstall portupgrade and rebuild the pkg index or whatever... you may aslo want to try a make index first... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports hosed
On Sun, Apr 04, 2004 at 01:53:11AM -0600, Jay Moore wrote: > FreeBSD 5.2 installed from the cd a couple of weeks ago: > > I guess I've stepped into it, somehow... the sequence was: > > # cvsup -g -L 2 /root/ports-supfile > # pkgdb -F > # portupgrade -a > > The failure appeared to be the result of inability to find a distfile: > "docbook-xsl-1.65.1.tar.gz" > > So I manually d/l this file from sourceforge, copied it into /usr/ports/ > distfiles, and ran 'portupgrade -a' again. Got following error: > > /usr/local/sbin/portupgrade:35:in `require': No such file to load -- pkgtools > (LoadError) > from /usr/local/sbin/portupgrade:35 > > How do I get back to Kansas (there's no place like home)? Looks like you need to follow some of the steps in /usr/ports/UPDATING (specifically, related to ruby). Kris pgp0.pgp Description: PGP signature
ports hosed
FreeBSD 5.2 installed from the cd a couple of weeks ago: I guess I've stepped into it, somehow... the sequence was: # cvsup -g -L 2 /root/ports-supfile # pkgdb -F # portupgrade -a The failure appeared to be the result of inability to find a distfile: "docbook-xsl-1.65.1.tar.gz" So I manually d/l this file from sourceforge, copied it into /usr/ports/ distfiles, and ran 'portupgrade -a' again. Got following error: /usr/local/sbin/portupgrade:35:in `require': No such file to load -- pkgtools (LoadError) from /usr/local/sbin/portupgrade:35 How do I get back to Kansas (there's no place like home)? Thanks, Jay ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
