pkgdb problem after portupgrade - operation not permitted
I just portupgrade'd portupgrade on a FreeBSD 6.0-RELEASE to portupgrade 2.0.1 (2006/06/18), and right after this pkgdb fails on all operations, i.e.: pkgdb -fu [Rebuilding the pkgdb format:bdb1_btree in /var/db/pkg ... - 63 packages found (-0 +63) Operation not permitted: skipping... . Operation not permitted: skipping... . ... etc. Operation not permitted: Cannot update the pkgdb!] Naturally, portupgrade itself now fails to do anything. I've googled for the Operation not permitted error in pkgdb, but I could not find any useful pointers to the source of the problem. Any help is much appreciated. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pkgdb problem after portupgrade - operation not permitted
Mon, 19 Jun 2006 14:29:17 +0200, Max Belushkin wrote: I just portupgrade'd portupgrade on a FreeBSD 6.0-RELEASE to portupgrade 2.0.1 (2006/06/18), and right after this pkgdb fails on all operations, i.e.: pkgdb -fu [Rebuilding the pkgdb format:bdb1_btree in /var/db/pkg ... - 63 packages found (-0 +63) Operation not permitted: skipping... . Operation not permitted: skipping... . ... etc. Operation not permitted: Cannot update the pkgdb!] Naturally, portupgrade itself now fails to do anything. I've googled for the Operation not permitted error in pkgdb, but I could not find any useful pointers to the source of the problem. Any help is much appreciated. Now portupgarde is back to stable 2.1.1 version. Update you ports tree. , | Subject: cvs commit: ports/sysutils/portupgrade Makefile distinfo | ports/sysutils/portupgrade/files patch-bin-portsclean patch-bin-portupgrade | patch-lib-pkgdb.rb patch-lib-pkgtools.rb | From: Sergey Matveychuk [EMAIL PROTECTED] | To: [EMAIL PROTECTED], [EMAIL PROTECTED], cvs-all@FreeBSD.org | X-Sent: 11 minutes, 17 seconds ago | | sem 2006-06-19 12:41:58 UTC | | FreeBSD ports repository | | Modified files: | sysutils/portupgrade Makefile distinfo | Added files: | sysutils/portupgrade/files patch-lib-pkgtools.rb | Removed files: | sysutils/portupgrade/files patch-bin-portsclean |patch-bin-portupgrade |patch-lib-pkgdb.rb | Log: | - Roll back to stable 2.1.1 version. | I'd like to wait a repocopy but marcus seems will unaccessible for a week. | | Revision ChangesPath | 1.224 +4 -5 ports/sysutils/portupgrade/Makefile | 1.164 +3 -3 ports/sysutils/portupgrade/distinfo | 1.3 +0 -11 ports/sysutils/portupgrade/files/patch-bin-portsclean (dead) | 1.6 +0 -28 ports/sysutils/portupgrade/files/patch-bin-portupgrade (dead) | 1.2 +0 -25 ports/sysutils/portupgrade/files/patch-lib-pkgdb.rb (dead) | 1.1 +20 -0 ports/sysutils/portupgrade/files/patch-lib-pkgtools.rb (new) ` -- Andrey Slusar ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
[SOLVED] Re: pkgdb problem after portupgrade - operation not permitted
Andrey Slusar wrote: Now portupgarde is back to stable 2.1.1 version. Update you ports tree. Thank you, this solved the problem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
pkgdb problem
Hi I managed to get my pkgdb entirely screwed up - and there is now no database. I tried pkgdb -fu And was told there were 0 pkgs! How do I rebuild from scratch? Thanks David -- 40 yrs navigating and screwed up computing in blue waters! English Owner Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing May/June bound for Europe via Panama Canal. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pkgdb problem
On Mon, Jun 06, 2005 at 02:14:16PM -0700, Vizion wrote: Hi I managed to get my pkgdb entirely screwed up - and there is now no database. I tried pkgdb -fu And was told there were 0 pkgs! How do I rebuild from scratch? If you accidentally delete your /var/db/pkg directory then the only way to recover it is to restore from backup. Kris pgpSDNRuN6mk6.pgp Description: PGP signature
Re: pkgdb problem
On Monday 06 June 2005 15:32, the author Kris Kennaway contributed to the dialogue on- Re: pkgdb problem: On Mon, Jun 06, 2005 at 02:14:16PM -0700, Vizion wrote: Hi I managed to get my pkgdb entirely screwed up - and there is now no database. I tried pkgdb -fu And was told there were 0 pkgs! How do I rebuild from scratch? If you accidentally delete your /var/db/pkg directory then the only way to recover it is to restore from backup. Ooh dear are there no recovery scripts - I lost my var partition - and the back up was overwritten by a blank db!! I have a file listing of all the packages installed on the system - an output from pkg_info. Do you happen to know if there is any way I can at least get that into the pkgdb? David -- 40 yrs navigating and computing in blue waters. English Owner Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing May/June bound for Europe via Panama Canal. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pkgdb problem
On Mon, Jun 06, 2005 at 05:30:01PM -0700, Vizion wrote: On Monday 06 June 2005 15:32, the author Kris Kennaway contributed to the dialogue on- Re: pkgdb problem: On Mon, Jun 06, 2005 at 02:14:16PM -0700, Vizion wrote: Hi I managed to get my pkgdb entirely screwed up - and there is now no database. I tried pkgdb -fu And was told there were 0 pkgs! How do I rebuild from scratch? If you accidentally delete your /var/db/pkg directory then the only way to recover it is to restore from backup. Ooh dear are there no recovery scripts - I lost my var partition - and the back up was overwritten by a blank db!! No, the information is only stored within that directory. I have a file listing of all the packages installed on the system - an output from pkg_info. Do you happen to know if there is any way I can at least get that into the pkgdb? Feed it to portinstall to reinstall all of the ports. Kris pgpZVIR7JFiEf.pgp Description: PGP signature
Re: pkgdb problem
On Monday 06 June 2005 17:30, the author Vizion contributed to the dialogue on- Re: pkgdb problem: On Monday 06 June 2005 15:32, the author Kris Kennaway contributed to the dialogue on- Re: pkgdb problem: On Mon, Jun 06, 2005 at 02:14:16PM -0700, Vizion wrote: Hi I managed to get my pkgdb entirely screwed up - and there is now no database. I tried pkgdb -fu And was told there were 0 pkgs! How do I rebuild from scratch? If you accidentally delete your /var/db/pkg directory then the only way to recover it is to restore from backup. Ooh dear are there no recovery scripts - I lost my var partition - and the back up was overwritten by a blank db!! I have a file listing of all the packages installed on the system - an output from pkg_info. Do you happen to know if there is any way I can at least get that into the pkgdb? The file listing is up to date! Could it be used to pull the rest of the data from elsewhere or am I clutching at straws chuckles :-( David -- 40 yrs navigating and computing in blue waters. English Owner Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing May/June bound for Europe via Panama Canal. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pkgdb problem
On Monday 06 June 2005 18:21, the author Kris Kennaway contributed to the dialogue on- Re: pkgdb problem: On Mon, Jun 06, 2005 at 05:30:01PM -0700, Vizion wrote: On Monday 06 June 2005 15:32, the author Kris Kennaway contributed to the dialogue on- Re: pkgdb problem: On Mon, Jun 06, 2005 at 02:14:16PM -0700, Vizion wrote: Hi I managed to get my pkgdb entirely screwed up - and there is now no database. I tried pkgdb -fu And was told there were 0 pkgs! How do I rebuild from scratch? If you accidentally delete your /var/db/pkg directory then the only way to recover it is to restore from backup. Ooh dear are there no recovery scripts - I lost my var partition - and the back up was overwritten by a blank db!! No, the information is only stored within that directory. I have a file listing of all the packages installed on the system - an output from pkg_info. Do you happen to know if there is any way I can at least get that into the pkgdb? Feed it to portinstall to reinstall all of the ports. Sounds like a long process and a sledge hammer to crack a nut - but I guess if one has no other tool a sledge hammer will have to do !!! David sighs BTW It looks as though I may have solved the eclipse-devel help bug - I have RC1 working now and am testing it to death. -- 40 yrs navigating and computing in blue waters. English Owner Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing May/June bound for Europe via Panama Canal. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pkgdb problem [maybe good news]
On Monday 06 June 2005 18:24, the author Vizion contributed to the dialogue on- Re: pkgdb problem: Feed it to portinstall to reinstall all of the ports. Sounds like a long process and a sledge hammer to crack a nut - but I guess if one has no other tool a sledge hammer will have to do !!! David sighs BTW It looks as though I may have solved the eclipse-devel help bug - I have RC1 working now and am testing it to death. Ok I have found an up to date copies of files elsewhere on the system - but before I do anything I want to be certain of the structure of the package database directories and files before I make any attempt to reconstruct the pkgdb Would you mind letting me have a print out of the directory structure. I have what looks files for each package containing - are they part of the pkgdb dns1# ls -l total 18 -rw-r--r-- 1 root wheel 46 May 10 11:05 +COMMENT -rw-r--r-- 1 root wheel442 May 10 11:05 +CONTENTS -rw-r--r-- 1 root wheel270 May 10 11:05 +DESC -r--r--r-- 1 root wheel 11209 May 10 11:05 +MTREE_DIRS and a file: pkgdb.db -rw-r--r-- 1 root wheel 23593984 May 30 20:43 pkgdb.db Thank you so much for all your warmth and the generosity with which you share your time David -- 40 yrs navigating and computing in blue waters. English Owner Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing May/June bound for Europe via Panama Canal. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pkgdb problem [solved]
On Monday 06 June 2005 19:20, the author Vizion contributed to the dialogue on- Re: pkgdb problem [maybe good news]: Thank you so much for all your warmth and the generosity with which you share your time OK its done and rebuilt -- thank heavens for my forgotten critical files backup directory!! David -- 40 yrs navigating and computing in blue waters. English Owner Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing May/June bound for Europe via Panama Canal. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Portupgrade problem, possible pkgdb problem?
I'm still getting this error after a cvsup+buildworld, a make fetchindex and I have deleted /var/db/pkg/pkgdb.db and rebuilt it, what's the patch?: test# uname -v FreeBSD 5.2.1-RELEASE-p11 #12: Wed Oct 6 17:13:13 CDT 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/TEST test# cd /usr/ports test# make fetchindex Receiving INDEX-5 (5881230 bytes): 100% 5881230 bytes transferred in 16.9 seconds (339.01 kBps) test# portupgrade -R sudo [Failed `Inappropriate file type or format'] [Updating the portsdb format:bdb1_btree in /usr/ports ... - 11735 port entries found .1000.2000.3000.4000.5000.60 00.7000.8000/usr/local/lib/ruby/site_ruby/1.8/portsdb.rb :587: [BUG] Bus Error ruby 1.8.2 (2004-07-29) [i386-freebsd5] Abort (core dumped) test# rm /var/db/pkg/pkgdb.db test# portupgrade -R sudo [Rebuilding the pkgdb format:bdb1_btree in /var/db/pkg ... - 54 packages found (-0 +54) .. done] [Failed `Inappropriate file type or format'] [Updating the portsdb format:bdb1_btree in /usr/ports ... - 11735 port entries found .1000.2000.3000.4000.5000.60 00.7000.8000/usr/local/lib/ruby/site_ruby/1.8/portsdb.rb :587: [BUG] Bus Error ruby 1.8.2 (2004-07-29) [i386-freebsd5] Abort (core dumped) test# -- Ethernet (n): something used to catch the etherbunny John Mire: [EMAIL PROTECTED]Network Administration 318-675-5434 LSU Health Sciences Center - Shreveport The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matthew Seaman Sent: Sunday, September 26, 2004 4:14 AM To: Matt Navarre Cc: [EMAIL PROTECTED] Subject: Re: Portupgrade problem, possible pkgdb problem? On Sat, Sep 25, 2004 at 06:14:18PM -0700, Matt Navarre wrote: On Saturday 25 September 2004 05:13, Alex de Kruijff wrote: It could be a problem with the DBDriver. You could try this: Edit /root/.cs... and add PORTS_DBDRIVER=bdb1_hash PKG_DBDRIVER=bdb1_hash Doesn't the DBDRIVER bug result in ruby dumping core? 'Cuz it isn't in this case, it fails gracefully. The core dump is seen with portsdb(1) trying to create /usr/ports/INDEX.db -- however, the underlying bug can affect anywhere that ruby uses bdb1_btree files. pkgdb(1) occasionally going a bit funny is a problem that's been known about for some time; usually just deleting and rebuilding /var/db/pkg/pkgdb.db will sort things out. However, I don't think anyone had ever tracked down the root cause of the problem. Then the portsdb coredumping thing came along, and it seems an obvious conclusion that the same thing might be affecting both programs. Note that a fix for the bdb1_btree problem has been in HEAD for a few weeks, and was MFC'd to both RELENG_4 and RELENG_5 a week or so ago. So an alternative fix could be cvsup+buildworld. Unfortunately, I don't think the fix will be applied to any of the existing 4.x-RELEASE or 5.x-RELEASE branches -- it will of course be in 5.3-RELEASE when that comes out, and it's pretty easy to do if you want to patch things yourself. I'll go ahead and try this, but I suspect that the /var/db/pkg info for gnucash or one of it's dependancies got horked up. We'll see. Then execute this in your shell also. Then do: pkgdb -u portsdb -u portupgrade -R gnucash Yup. That should ensure you get a clean install of gnucash and all of its dependencies. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade problem, possible pkgdb problem?
On Thu, Oct 07, 2004 at 10:45:46AM -0500, Mire, John wrote: I'm still getting this error after a cvsup+buildworld, a make fetchindex and I have deleted /var/db/pkg/pkgdb.db and rebuilt it, what's the patch?: test# uname -v FreeBSD 5.2.1-RELEASE-p11 #12: Wed Oct 6 17:13:13 CDT 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/TEST test# cd /usr/ports test# make fetchindex Receiving INDEX-5 (5881230 bytes): 100% 5881230 bytes transferred in 16.9 seconds (339.01 kBps) test# portupgrade -R sudo [Failed `Inappropriate file type or format'] [Updating the portsdb format:bdb1_btree in /usr/ports ... - 11735 port entries found .1000.2000.3000.4000.5000.60 00.7000.8000/usr/local/lib/ruby/site_ruby/1.8/portsdb.rb :587: [BUG] Bus Error ruby 1.8.2 (2004-07-29) [i386-freebsd5] Abort (core dumped) test# rm /var/db/pkg/pkgdb.db test# portupgrade -R sudo [Rebuilding the pkgdb format:bdb1_btree in /var/db/pkg ... - 54 packages found (-0 +54) .. done] [Failed `Inappropriate file type or format'] [Updating the portsdb format:bdb1_btree in /usr/ports ... - 11735 port entries found .1000.2000.3000.4000.5000.60 00.7000.8000/usr/local/lib/ruby/site_ruby/1.8/portsdb.rb :587: [BUG] Bus Error ruby 1.8.2 (2004-07-29) [i386-freebsd5] Abort (core dumped) test# The patch was only applied to RELENG_4, RELENG_5 and HEAD -- not RELENG_5_2. However, you can extract it from cvs and apply it yourself by hand if you aren't in a position to upgrade right now -- see: http://www.freebsd.org/cgi/cvsweb.cgi/src/lib/libc/db/btree/bt_split.c.diff?r1=1.5r2=1.7 (Remember that you'll have to re-apply that patch each time you cvsup(1) your src) Otherwise just use one of the variations on: setenv PORTS_DBDRIVER=bdb1_hash as a workaround. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgpRm4klv3Ptz.pgp Description: PGP signature
Re: Portupgrade problem, possible pkgdb problem?
Thanks, guess it's time to use the work around, the env setting worked fine. -- Ethernet (n): something used to catch the etherbunny John Mire: [EMAIL PROTECTED]Network Administration 318-675-5434 LSU Health Sciences Center - Shreveport -Original Message- From: Matthew Seaman [EMAIL PROTECTED] To: Mire, John [EMAIL PROTECTED] CC: Matt Navarre [EMAIL PROTECTED]; [EMAIL PROTECTED] [EMAIL PROTECTED] Sent: Thu Oct 07 12:41:17 2004 Subject: Re: Portupgrade problem, possible pkgdb problem? On Thu, Oct 07, 2004 at 10:45:46AM -0500, Mire, John wrote: I'm still getting this error after a cvsup+buildworld, a make fetchindex and I have deleted /var/db/pkg/pkgdb.db and rebuilt it, what's the patch?: test# uname -v FreeBSD 5.2.1-RELEASE-p11 #12: Wed Oct 6 17:13:13 CDT 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/TEST test# cd /usr/ports test# make fetchindex Receiving INDEX-5 (5881230 bytes): 100% 5881230 bytes transferred in 16.9 seconds (339.01 kBps) test# portupgrade -R sudo [Failed `Inappropriate file type or format'] [Updating the portsdb format:bdb1_btree in /usr/ports ... - 11735 port entries found .1000.2000.3000.4000.5000.60 00.7000.8000/usr/local/lib/ruby/site_ruby/1.8/portsdb.rb :587: [BUG] Bus Error ruby 1.8.2 (2004-07-29) [i386-freebsd5] Abort (core dumped) test# rm /var/db/pkg/pkgdb.db test# portupgrade -R sudo [Rebuilding the pkgdb format:bdb1_btree in /var/db/pkg ... - 54 packages found (-0 +54) .. done] [Failed `Inappropriate file type or format'] [Updating the portsdb format:bdb1_btree in /usr/ports ... - 11735 port entries found .1000.2000.3000.4000.5000.60 00.7000.8000/usr/local/lib/ruby/site_ruby/1.8/portsdb.rb :587: [BUG] Bus Error ruby 1.8.2 (2004-07-29) [i386-freebsd5] Abort (core dumped) test# The patch was only applied to RELENG_4, RELENG_5 and HEAD -- not RELENG_5_2. However, you can extract it from cvs and apply it yourself by hand if you aren't in a position to upgrade right now -- see: http://www.freebsd.org/cgi/cvsweb.cgi/src/lib/libc/db/btree/bt_split.c.diff? r1=1.5r2=1.7 (Remember that you'll have to re-apply that patch each time you cvsup(1) your src) Otherwise just use one of the variations on: setenv PORTS_DBDRIVER=bdb1_hash as a workaround. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade problem, possible pkgdb problem?
On Sat, Sep 25, 2004 at 06:14:18PM -0700, Matt Navarre wrote: On Saturday 25 September 2004 05:13, Alex de Kruijff wrote: It could be a problem with the DBDriver. You could try this: Edit /root/.cs... and add PORTS_DBDRIVER=bdb1_hash PKG_DBDRIVER=bdb1_hash Doesn't the DBDRIVER bug result in ruby dumping core? 'Cuz it isn't in this case, it fails gracefully. The core dump is seen with portsdb(1) trying to create /usr/ports/INDEX.db -- however, the underlying bug can affect anywhere that ruby uses bdb1_btree files. pkgdb(1) occasionally going a bit funny is a problem that's been known about for some time; usually just deleting and rebuilding /var/db/pkg/pkgdb.db will sort things out. However, I don't think anyone had ever tracked down the root cause of the problem. Then the portsdb coredumping thing came along, and it seems an obvious conclusion that the same thing might be affecting both programs. Note that a fix for the bdb1_btree problem has been in HEAD for a few weeks, and was MFC'd to both RELENG_4 and RELENG_5 a week or so ago. So an alternative fix could be cvsup+buildworld. Unfortunately, I don't think the fix will be applied to any of the existing 4.x-RELEASE or 5.x-RELEASE branches -- it will of course be in 5.3-RELEASE when that comes out, and it's pretty easy to do if you want to patch things yourself. I'll go ahead and try this, but I suspect that the /var/db/pkg info for gnucash or one of it's dependancies got horked up. We'll see. Then execute this in your shell also. Then do: pkgdb -u portsdb -u portupgrade -R gnucash Yup. That should ensure you get a clean install of gnucash and all of its dependencies. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgpVii1Bm2YMS.pgp Description: PGP signature
Portupgrade problem, possible pkgdb problem?
I'm trying to upgrade gnucash, but portupgrade is choking: reichlieu# portupgrade -R gnucash /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:323:in `deorigin': cannot convert nil into String (PkgDB::DBError) from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:916:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:915:in `each' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:915:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:907:in `each' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:907:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:929:in `sort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:933:in `sort_build!' from /usr/local/sbin/portupgrade:674:in `main' from /usr/local/sbin/portupgrade:207:in `initialize' from /usr/local/sbin/portupgrade:207:in `new' from /usr/local/sbin/portupgrade:207:in `main' from /usr/local/sbin/portupgrade:1845 It looks like the pkgdb has something wrong with it, but pkgdb -Fu doesn't report anything that seems like it would cause portupgrade to bomb. There's a duplicate origin for cdrtools, but that doesn't seem to pertain. Should I move /var/db/pkg/pkgdb.db out of the way and regenerate it? Will pkgdb -u recreate pkgdb.db? Thanks, Matt -- We all enter this world in the same way: naked, screaming, and soaked in blood. But if you live your life right, that kind of thing doesn't have to stop there. -- Dana Gould ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade problem, possible pkgdb problem?
On Saturday 25 September 2004 02:35, Matt Navarre wrote: I'm trying to upgrade gnucash, but portupgrade is choking: reichlieu# portupgrade -R gnucash /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:323:in `deorigin': cannot convert nil into String (PkgDB::DBError) from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:916:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:915:in `each' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:915:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:907:in `each' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:907:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:929:in `sort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:933:in `sort_build!' from /usr/local/sbin/portupgrade:674:in `main' from /usr/local/sbin/portupgrade:207:in `initialize' from /usr/local/sbin/portupgrade:207:in `new' from /usr/local/sbin/portupgrade:207:in `main' from /usr/local/sbin/portupgrade:1845 It looks like the pkgdb has something wrong with it, but pkgdb -Fu doesn't report anything that seems like it would cause portupgrade to bomb. There's a duplicate origin for cdrtools, but that doesn't seem to pertain. Should I move /var/db/pkg/pkgdb.db out of the way and regenerate it? Will pkgdb -u recreate pkgdb.db? Ok, that didn't work. I regenerated pkgdb.db using pkgdb -u and got the same problem. Odd thing is that so far gnucash is the only installed package that generates this error. I suppose I can pkg_delete it and try reinstalling. Thanks, Matt -- We all enter this world in the same way: naked, screaming, and soaked in blood. But if you live your life right, that kind of thing doesn't have to stop there. -- Dana Gould ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade problem, possible pkgdb problem?
On Sat, Sep 25, 2004 at 04:18:47PM -0700, Matt Navarre wrote: On Saturday 25 September 2004 02:35, Matt Navarre wrote: I'm trying to upgrade gnucash, but portupgrade is choking: reichlieu# portupgrade -R gnucash /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:323:in `deorigin': cannot convert nil into String (PkgDB::DBError) from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:916:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:915:in `each' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:915:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:907:in `each' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:907:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:929:in `sort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:933:in `sort_build!' from /usr/local/sbin/portupgrade:674:in `main' from /usr/local/sbin/portupgrade:207:in `initialize' from /usr/local/sbin/portupgrade:207:in `new' from /usr/local/sbin/portupgrade:207:in `main' from /usr/local/sbin/portupgrade:1845 It looks like the pkgdb has something wrong with it, but pkgdb -Fu doesn't report anything that seems like it would cause portupgrade to bomb. There's a duplicate origin for cdrtools, but that doesn't seem to pertain. Should I move /var/db/pkg/pkgdb.db out of the way and regenerate it? Will pkgdb -u recreate pkgdb.db? Ok, that didn't work. I regenerated pkgdb.db using pkgdb -u and got the same problem. Odd thing is that so far gnucash is the only installed package that generates this error. I suppose I can pkg_delete it and try reinstalling. It could be a problem with the DBDriver. You could try this: Edit /root/.cs... and add PORTS_DBDRIVER=bdb1_hash PKG_DBDRIVER=bdb1_hash Then execute this in your shell also. Then do: pkgdb -u portsdb -u portupgrade -R gnucash -- Alex Articles based on solutions that I use: http://www.kruijff.org/alex/FreeBSD/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade problem, possible pkgdb problem?
On Saturday 25 September 2004 05:13, Alex de Kruijff wrote: On Sat, Sep 25, 2004 at 04:18:47PM -0700, Matt Navarre wrote: On Saturday 25 September 2004 02:35, Matt Navarre wrote: I'm trying to upgrade gnucash, but portupgrade is choking: *snip* It looks like the pkgdb has something wrong with it, but pkgdb -Fu doesn't report anything that seems like it would cause portupgrade to bomb. There's a duplicate origin for cdrtools, but that doesn't seem to pertain. Should I move /var/db/pkg/pkgdb.db out of the way and regenerate it? Will pkgdb -u recreate pkgdb.db? Ok, that didn't work. I regenerated pkgdb.db using pkgdb -u and got the same problem. Odd thing is that so far gnucash is the only installed package that generates this error. I suppose I can pkg_delete it and try reinstalling. It could be a problem with the DBDriver. You could try this: Edit /root/.cs... and add PORTS_DBDRIVER=bdb1_hash PKG_DBDRIVER=bdb1_hash Doesn't the DBDRIVER bug result in ruby dumping core? 'Cuz it isn't in this case, it fails gracefully. I'll go ahead and try this, but I suspect that the /var/db/pkg info for gnucash or one of it's dependancies got horked up. We'll see. Then execute this in your shell also. Then do: pkgdb -u portsdb -u portupgrade -R gnucash -- We all enter this world in the same way: naked, screaming, and soaked in blood. But if you live your life right, that kind of thing doesn't have to stop there. -- Dana Gould ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Strange pkgdb problem...
When trying to run the Gnome-2.6 upgrade script, I get this: error checking for pkg-config... /usr/local/bin/pkg-config checking for libgnome-2.0 = 2.0.0 libgnomeui-2.0 = 2.0.0 gconf-2.0 = 1.1.5 libgtop-2.0 = 2.5.2 libwnck-1.0 = 2.5.0 gtk+-2.0 = 2.3.0... Requested 'libgtop-2.0 = 2.5.2' but version of libgtop is 2.0.7 configure: error: Library requirements (libgnome-2.0 = 2.0.0 libgnomeui-2.0 = 2.0.0 gconf-2.0 = 1.1.5 libgtop-2.0 = 2.5.2 libwnck-1.0 = 2.5.0 gtk+-2.0 = 2.3.0) not met; consider adjusting the PKG_CONFIG_PATH environment variable if your libraries are in a nonstandard prefix so pkg-config can find them. === Script configure failed unexpectedly. Please report the problem to [EMAIL PROTECTED] [maintainer] and attach the /usr/ports/sysutils/gnomesystemmonitor/work/gnome-system-monitor-2.6.0/config.log including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. an `ls /var/db/pkg`). *** Error code 1 /error What's strange is the following output: frog# ls /var/db/pkg | grep libgtop libgtop2-2.6.0 frog# OK... so now what do I do? I did a make deinstall, and make install of the latest libgtop, but to no avail. Please help if you know of a way I can resolve this! -- Mr. R M Los - Information Security Consultant Ralph (at) boundariez (dot) com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pkgdb problem!
On Wed, Mar 03, 2004 at 10:39:37PM -0500, Tsu-Fan Cheng wrote: Hi BSDers, I run pkgdb -F and get this: --- Checking the package registry database [Updating the pkgdb format:bdb1_btree in /var/db/pkg ... - 433 packages found (-21 +58) (...)Cannot allocate memory: Cannot update the pkgdb!] never has happened to me before, what's wrong? Take a look at /usr/ports/UPDATING. Kris pgp0.pgp Description: PGP signature
pkgdb problem!
Hi BSDers, I run pkgdb -F and get this: --- Checking the package registry database [Updating the pkgdb format:bdb1_btree in /var/db/pkg ... - 433 packages found (-21 +58) (...)Cannot allocate memory: Cannot update the pkgdb!] never has happened to me before, what's wrong? Best Regards, :-) Tsu-Fan Cheng [] (BIG5) SUNY at Stony Brook Stony Brook, NY, 11794 We are luckier than we think! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pkgdb problem!
On Wed, 3 Mar 2004 22:39:37 -0500 (EST) Tsu-Fan Cheng [EMAIL PROTECTED] wrote: Hi BSDers, I run pkgdb -F and get this: --- Checking the package registry database [Updating the pkgdb format:bdb1_btree in /var/db/pkg ... - 433 packages found (-21 +58) (...)Cannot allocate memory: Cannot update the pkgdb!] never has happened to me before, what's wrong? From: Ion-Mihai Tetcu [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: FreeBSD Port: portupgrade-20040208 Date: Tue, 2 Mar 2004 16:16:31 +0200 On Tue, 02 Mar 2004 08:51:59 -0500 J. W. Ballantine [EMAIL PROTECTED] wrote: After upgrading portupgrade and ruby, I started getting the following error: [..] .rb:467:in `select': failed to allocate memory (NoMemoryError) [..] Happened here too. First try to remove your /var/db/pkg/pkgdb.db (backup first). Do a pkg_db -F. If it ain't working or you still got the problem, make deinstall for portupgrade and all ruby*. make install ruby18, portupgrade, do a pkgdb -F, install the rest of removed ruby* -- IOnut Unregistered ;) FreeBSD user ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade/pkgdb problem
Roman Bogorodskiy wrote: Hi, As described in http://www.freshports.org/[EMAIL PROTECTED], I've reinstalled portupgrade-\*. And now when I try to run portupgrade I have such error: novel /usr/local/bin $ portupgrade -sfr lang/ruby16 --- [Executing a command as root: sudo /usr/local/sbin/pkgdb -u] --- Updating the pkgdb [Updating the pkgdb format:bdb1_btree in /var/db/pkg ... - 266 packages found (-41 +135) (...)ruby in malloc(): error: allocation failed --- [Executing a command as root: sudo /usr/local/sbin/pkgdb -u] --- Updating the pkgdb [Updating the pkgdb format:bdb1_btree in /var/db/pkg ... - 266 packages found (-41 +135) (...)ruby in malloc(): error: allocation failed The pkgdb must be updated. Please run 'pkgdb -u' as root. novel /usr/local/bin $ What's wrong? FreeBSD 5.2.1-RELEASE i386 portupgrade 1.8.1 ruby 1.8.1 (2003-12-25) [i386-freebsd5] I think this is because ruby-1.6 used to install /usr/local/bin/ruby, but by the recent upgrade this becomes /usr/local/bin/ruby16 and ruby is not there anymore. Since portupgrade needs ruby, portupgrade gets stuck as soon as upgrading ruby-1.6 removes the /usr/local/bin/ruby file. I have removed portupgrade and all related ruby stuff and then reinstalled portupgrade, which then installs ruby-1.8. All works well then. Rob. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade/pkgdb problem
Rob wrote: I think this is because ruby-1.6 used to install /usr/local/bin/ruby, but by the recent upgrade this becomes /usr/local/bin/ruby16 and ruby is not there anymore. Since portupgrade needs ruby, portupgrade gets stuck as soon as upgrading ruby-1.6 removes the /usr/local/bin/ruby file. I have removed portupgrade and all related ruby stuff and then reinstalled portupgrade, which then installs ruby-1.8. All works well then. I said that I've reinstalled portupgrade already. And I have no ruby16 installed now, my /usr/local/bin/ruby is a ruby-1.8 novel ~ $ ruby --version ruby 1.8.1 (2003-12-25) [i386-freebsd5] novel ~ $ -Roman Bogorodskiy pgp0.pgp Description: PGP signature
pkgdb problem
i have just upgraded ruby 1.8 and i wanted to run pkgdb and i get this: === Registering installation for ruby-1.8.1_2 === SECURITY REPORT: This port has installed the following files which may act as network servers and may therefore pose a remote security risk to the system. /usr/local/lib/ruby/1.8/i386-freebsd5/socket.so This port has installed the following world-writable files/directories. /usr/local/lib/libruby18.so If there are vulnerabilities in these programs there may be a security risk to the system. FreeBSD makes no guarantee about the security of ports included in the Ports Collection. Please type 'make deinstall' to deinstall the port if this is a concern. For more information, and contact details about the security status of this software, see the following webpage: http://www.ruby-lang.org/en/ danger# rehash danger# pkgdb -F /usr/local/sbin/pkgdb:35:in `require': No such file to load -- pkgtools (LoadError) from /usr/local/sbin/pkgdb:35 danger# -- DanGer [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pkgdb problem
On Saturday 28 February 2004 02:27 am, DanGer wrote: i have just upgraded ruby 1.8 and i wanted to run pkgdb and i get this: === Registering installation for ruby-1.8.1_2 === SECURITY REPORT: This port has installed the following files which may act as network servers and may therefore pose a remote security risk to the system. /usr/local/lib/ruby/1.8/i386-freebsd5/socket.so This port has installed the following world-writable files/directories. /usr/local/lib/libruby18.so If there are vulnerabilities in these programs there may be a security risk to the system. FreeBSD makes no guarantee about the security of ports included in the Ports Collection. Please type 'make deinstall' to deinstall the port if this is a concern. For more information, and contact details about the security status of this software, see the following webpage: http://www.ruby-lang.org/en/ danger# rehash danger# pkgdb -F /usr/local/sbin/pkgdb:35:in `require': No such file to load -- pkgtools (LoadError) from /usr/local/sbin/pkgdb:35 You have to rebuild portupgrade and all of its new dependancies. It is easier to start by deleting portupgrade and ruby* and then, rebuild portupgrade. 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]
Pkgdb Problem -- /usr/local/sbin/pkgdb:35:in
Hello, I run FreeBSD 4.9 and just ran my weekly CVSup followed by portsdb -uU and portupgrade -arR. I came across the following message which looks similar to one previously posted today. I'm relatively new at this and just question whether or not the previous response is the same for my situation (e.g., delete portupgrade and ruby* and then rebuild portupgrade). BTW, what happens to the ruby files that are removed? Thanks, Bob Perry /usr/local/sbin/pkgdb:35:in `require': No such file to load -- pkgtools (LoadError) from /usr/local/sbin/pkgdb:35 --- Backing up the old version --- Uninstalling the old version /usr/local/sbin/pkg_deinstall:35:in `require': No such file to load -- pkgtools (LoadError) from /usr/local/sbin/pkg_deinstall:35 ** The following packages were not installed or upgraded (*:skipped / !:failed) ! accessibility/gnomemag (gnomemag-0.10.6) (uninstall error) ! databases/ruby-bdb1 (ruby-bdb1-0.2.1) (uninstall error) ! math/gcalctool (gcalctool-4.3.46) (uninstall error) ! editors/AbiWord2 (AbiWord2-gnome-2.0.3_1) (uninstall error) -- I've learned that whatever hits the fan will not be evenly distributed. FreeBSD 4.9-RELEASE-p2 #0 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Pkgdb Problem -- /usr/local/sbin/pkgdb:35:in
On Saturday 28 February 2004 11:53 am, Bob Perry wrote: Hello, I run FreeBSD 4.9 and just ran my weekly CVSup followed by portsdb -uU and portupgrade -arR. I came across the following message which looks similar to one previously posted today. I'm relatively new at this and just question whether or not the previous response is the same for my situation (e.g., delete portupgrade and ruby* and then rebuild portupgrade). BTW, what happens to the ruby files that are removed? Ruby has been updated to version 1.8. Delete portupgrade and ruby*, which will delete all of the ruby-1.6 stuff. This will also delete 1.8. You can manually delete all of the ruby-1.6 or relax and let the portsytem rebuild it. At an rate, after you have deleted portupgrade and the ruby-1.6 ports, you can rebuild portupgrade, which will link to ruby-1.8. Kent Thanks, Bob Perry /usr/local/sbin/pkgdb:35:in `require': No such file to load -- pkgtools (LoadError) from /usr/local/sbin/pkgdb:35 --- Backing up the old version --- Uninstalling the old version /usr/local/sbin/pkg_deinstall:35:in `require': No such file to load -- pkgtools (LoadError) from /usr/local/sbin/pkg_deinstall:35 ** The following packages were not installed or upgraded (*:skipped / !:failed) ! accessibility/gnomemag (gnomemag-0.10.6) (uninstall error) ! databases/ruby-bdb1 (ruby-bdb1-0.2.1) (uninstall error) ! math/gcalctool (gcalctool-4.3.46) (uninstall error) ! editors/AbiWord2 (AbiWord2-gnome-2.0.3_1) (uninstall error) -- 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: Pkgdb Problem -- /usr/local/sbin/pkgdb:35:in
I had that a similiar problem - it broken portversion. I went and reinstalled it from the ports and everything is well again - you might need to do the same as well. -- - Rilindo Foster http://monzell.com AIM: rilindo ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Pkgdb Problem -- /usr/local/sbin/pkgdb:35:in
Kent Stewart wrote: On Saturday 28 February 2004 11:53 am, Bob Perry wrote: Hello, I run FreeBSD 4.9 and just ran my weekly CVSup followed by portsdb -uU and portupgrade -arR. I came across the following message which looks similar to one previously posted today. I'm relatively new at this and just question whether or not the previous response is the same for my situation (e.g., delete portupgrade and ruby* and then rebuild portupgrade). BTW, what happens to the ruby files that are removed? Ruby has been updated to version 1.8. Delete portupgrade and ruby*, which will delete all of the ruby-1.6 stuff. This will also delete 1.8. You can manually delete all of the ruby-1.6 or relax and let the portsytem rebuild it. At an rate, after you have deleted portupgrade and the ruby-1.6 ports, you can rebuild portupgrade, which will link to ruby-1.8. Kent Thanks, Bob Perry /usr/local/sbin/pkgdb:35:in `require': No such file to load -- pkgtools (LoadError) from /usr/local/sbin/pkgdb:35 --- Backing up the old version --- Uninstalling the old version /usr/local/sbin/pkg_deinstall:35:in `require': No such file to load -- pkgtools (LoadError) from /usr/local/sbin/pkg_deinstall:35 ** The following packages were not installed or upgraded (*:skipped / !:failed) ! accessibility/gnomemag (gnomemag-0.10.6) (uninstall error) ! databases/ruby-bdb1 (ruby-bdb1-0.2.1) (uninstall error) ! math/gcalctool (gcalctool-4.3.46) (uninstall error) ! editors/AbiWord2 (AbiWord2-gnome-2.0.3_1) (uninstall error) Sorry for being so thick, but I get more than just nervous when using the delete command. Do I understand you correctly in that I delete, as in rm, the portupgrade files in /usr/ports/sysutils/ directory and also all of the ruby files in the /usr/ports/ lang/ directory? Bob -- I've learned that whatever hits the fan will not be evenly distributed. FreeBSD 4.9-RELEASE-p2 #0 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Pkgdb Problem -- /usr/local/sbin/pkgdb:35:in
On Saturday 28 February 2004 12:54 pm, Bob Perry wrote: Kent Stewart wrote: On Saturday 28 February 2004 11:53 am, Bob Perry wrote: Hello, I run FreeBSD 4.9 and just ran my weekly CVSup followed by portsdb -uU and portupgrade -arR. I came across the following message which looks similar to one previously posted today. I'm relatively new at this and just question whether or not the previous response is the same for my situation (e.g., delete portupgrade and ruby* and then rebuild portupgrade). BTW, what happens to the ruby files that are removed? Ruby has been updated to version 1.8. Delete portupgrade and ruby*, which will delete all of the ruby-1.6 stuff. This will also delete 1.8. You can manually delete all of the ruby-1.6 or relax and let the portsytem rebuild it. At an rate, after you have deleted portupgrade and the ruby-1.6 ports, you can rebuild portupgrade, which will link to ruby-1.8. Kent Thanks, Bob Perry /usr/local/sbin/pkgdb:35:in `require': No such file to load -- pkgtools (LoadError) from /usr/local/sbin/pkgdb:35 --- Backing up the old version --- Uninstalling the old version /usr/local/sbin/pkg_deinstall:35:in `require': No such file to load -- pkgtools (LoadError) from /usr/local/sbin/pkg_deinstall:35 ** The following packages were not installed or upgraded (*:skipped / !:failed) ! accessibility/gnomemag (gnomemag-0.10.6) (uninstall error) ! databases/ruby-bdb1 (ruby-bdb1-0.2.1) (uninstall error) ! math/gcalctool (gcalctool-4.3.46) (uninstall error) ! editors/AbiWord2 (AbiWord2-gnome-2.0.3_1) (uninstall error) Sorry for being so thick, but I get more than just nervous when using the delete command. Do I understand you correctly in that I delete, as in rm, the portupgrade files in /usr/ports/sysutils/ directory and also all of the ruby files in the /usr/ports/ lang/ directory? No, you can pkg_delete portupgrade pkg_delete 'ruby*' cd /usr/ports/sysutils/portupgrade make install You can see options in the commit message at http://www.freebsd.org/cgi/cvsweb.cgi/ports/lang/ruby18/Makefile The pkg_delete of ruby* and portupgrade was the only thing that worked for me. There is a now ruby16 and a ruby18. Portupgrade now uses ruby18. 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: Pkgdb Problem -- /usr/local/sbin/pkgdb:35:in
On Sat, Feb 28, 2004 at 03:54:09PM -0500, Bob Perry wrote: Sorry for being so thick, but I get more than just nervous when using the delete command. Do I understand you correctly in that I delete, as in rm, the portupgrade files in /usr/ports/sysutils/ directory and also all of the ruby files in the /usr/ports/ lang/ directory? You can follow the instructions at http://www.freebsd.org/cgi/getmsg.cgi?fetch=1562140+0+current/cvs-ports from the original commit message. There's probably a more streamlined way of doing the upgrade, but this procedure works pretty smoothly. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
Re: Pkgdb Problem -- /usr/local/sbin/pkgdb:35:in
Sorry for being so thick, but I get more than just nervous when using the delete command. Do I understand you correctly in that I delete, as in rm, the portupgrade files in /usr/ports/sysutils/ directory and also all of the ruby files in the /usr/ports/ lang/ directory? No, you can pkg_delete portupgrade pkg_delete 'ruby*' cd /usr/ports/sysutils/portupgrade make install You can see options in the commit message at http://www.freebsd.org/cgi/cvsweb.cgi/ports/lang/ruby18/Makefile The pkg_delete of ruby* and portupgrade was the only thing that worked for me. There is a now ruby16 and a ruby18. Portupgrade now uses ruby18. Kent First, I deleted portupgrade. Ran into what seemed like a syntax error, but eventually deleted the port. Note the following: ==[EMAIL PROTECTED]:/usr/ports pkg_delete portupgrade pkg_delete: no such package 'portupgrade' installed ==[EMAIL PROTECTED]:/usr/ports pkg_delete portupgrade-\* Next, I deleted all ruby files, with some familiar messages following. ==[EMAIL PROTECTED]:/usr/ports pkg_delete 'ruby*' pkg_delete: unable to completely remove directory '/usr/local/lib/ruby/site_ruby/1.6/i386-freebsd4' pkg_delete: unable to completely remove directory '/usr/local/lib/ruby/site_ruby/1.6' pkg_delete: couldn't entirely delete package (perhaps the packing list is incorrectly specified?) pkg_delete: file '/usr/local/bin/erb' doesn't really exist pkg_delete: file '/usr/local/bin/h2rb' doesn't really exist pkg_delete: file '/usr/local/bin/rdoc' doesn't really exist pkg_delete: couldn't entirely delete package (perhaps the packing list is incorrectly specified?) Reinstalled portupgrade. ==[EMAIL PROTECTED]:/usr/ports cd sysutils/portupgrade/ ==[EMAIL PROTECTED]:/usr/ports/sysutils/portupgrade make install snip Warning: Object directory not changed from original /usr/ports/sysutils/portupgrade/work/pkgtools-20040208/bin /usr/local/bin/ruby18 -wc pkg_fetch /usr/local/bin/ruby18:No such file or directory *** Error code 1 Stop in /usr/ports/sysutils/portupgrade/work/pkgtools-20040208/bin. *** Error code 1 Had to run make clean before it would run successfully. Didn't run steps 2-4 of the options in the commit segment since I deleted all of the ruby files at the beginning. Hope no problems result. Just ran portupgrade again to complete what I had started this morning and it ran successfully. I was aware of similar problems others had encountered due to the change in the default version of ruby and read the commit in Fresh Ports. It just didn't register. I saw the phrase, If you are a ruby developer..., and ignored the rest. My bad. Thanks so much for your time and assistance. Bob Perry -- I've learned that whatever hits the fan will not be evenly distributed. FreeBSD 4.9-RELEASE-p2 #0 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
