ports problems
Hi, I've updated and upgraded the ports tree to the . branch but serveral of ports doesn't compile or are completly absent on the repositories. What can I do?, I need the system working. I'm using 6.3-STABLE. -8--8--8--8--8- pkg_create: make_dist: tar command failed with code 256 ** Command failed [exit code 1]: /usr/bin/script -qa /priv/down/dmw/tmp/portupgrade.86606.7 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=py25-setuptools-0.6c7 UPGRADE_PORT_VER=0.6c7 make -DFORCE_PKG_REGISTER reinstall ** Command failed [exit code 1]: /usr/bin/script -qa /priv/down/dmw/tmp/portupgrade.86606.5 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=py25-flup-0.5.r2311 UPGRADE_PORT_VER=0.5.r2311 make FETCH_BEFORE_ARGS=-q ** Command failed [exit code 1]: /usr/bin/script -qa /priv/down/dmw/tmp/portupgrade.86606.17 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=scons-0.97 UPGRADE_PORT_VER=0.97 make -DFORCE_PKG_REGISTER reinstall ** Command failed [exit code 1]: /usr/bin/script -qa /priv/down/dmw/tmp/portupgrade.86606.12 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=libusb-0.1.12_1 UPGRADE_PORT_VER=0.1.12_1 make FETCH_BEFORE_ARGS=-q ** Command failed [exit code 1]: /usr/bin/script -qa /priv/down/dmw/tmp/portupgrade.86606.4 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=nvidia-xconfig-1.0_1 UPGRADE_PORT_VER=1.0_1 make FETCH_BEFORE_ARGS=-q ** Command failed [exit code 1]: /usr/bin/script -qa /priv/down/dmw/tmp/portupgrade.86606.12 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=py25-numeric-24.2 UPGRADE_PORT_VER=24.2 make FETCH_BEFORE_ARGS=-q checking command to parse /usr/bin/nm -B output... failed ** Command failed [exit code 1]: /usr/bin/script -qa /priv/down/dmw/tmp/portupgrade.86606.21 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=py25-psycopg-1.1.21 UPGRADE_PORT_VER=1.1.21 make FETCH_BEFORE_ARGS=-q checking command to parse /usr/ports/lang/gcc42/work/build/./gcc/nm output... failed ** Command failed [exit code 1]: /usr/bin/script -qa /priv/down/dmw/tmp/portupgrade.86606.14 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=blas-1.0_1 UPGRADE_PORT_VER=1.0_1 make FETCH_BEFORE_ARGS=-q ** Command failed [exit code 1]: /usr/bin/script -qa /priv/down/dmw/tmp/portupgrade.86606.13 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=OpenEXR-1.4.0 UPGRADE_PORT_VER=1.4.0 make FETCH_BEFORE_ARGS=-q ** Command failed [exit code 1]: /usr/bin/script -qa /priv/down/dmw/tmp/portupgrade.86606.15 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=py25-MySQLdb-1.2.2 UPGRADE_PORT_VER=1.2.2 make FETCH_BEFORE_ARGS=-q of the failed make command, and (c) the gnomelogalyzer output. Also, it might ** Command failed [exit code 1]: /usr/bin/script -qa /priv/down/dmw/tmp/portupgrade.86606.5 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=py25-gobject-2.12.3 UPGRADE_PORT_VER=2.12.3 make FETCH_BEFORE_ARGS=-q ** Command failed [exit code 1]: /usr/bin/script -qa /priv/down/dmw/tmp/portupgrade.86606.9 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=mesa-demos-7.0.1 UPGRADE_PORT_VER=7.0.1 make FETCH_BEFORE_ARGS=-q ** Command failed [exit code 1]: /usr/bin/script -qa /priv/down/dmw/tmp/portupgrade.86606.19 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=gnome-libs-1.4.2_7 UPGRADE_PORT_VER=1.4.2_7 make FETCH_BEFORE_ARGS=-q ** Command failed [exit code 1]: /usr/bin/script -qa /priv/down/dmw/tmp/portupgrade.86606.3 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=ffmpeg-2007.10.04_1 UPGRADE_PORT_VER=2007.10.04_1 make FETCH_BEFORE_ARGS=-q ** Command failed [exit code 1]: /usr/bin/script -qa /priv/down/dmw/tmp/portupgrade.86606.1 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=linux-flashplugin-7.0r70 UPGRADE_PORT_VER=7.0r70 make FETCH_BEFORE_ARGS=-q ** Command failed [exit code 1]: /usr/bin/script -qa /priv/down/dmw/tmp/portupgrade.86606.7 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=gstreamer-0.10.14_1 UPGRADE_PORT_VER=0.10.14_1 make FETCH_BEFORE_ARGS=-q ** Command failed [exit code 1]: /usr/bin/script -qa /priv/down/dmw/tmp/portupgrade.86606.10 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=mplayer-0.99.10_13 UPGRADE_PORT_VER=0.99.10_13 make FETCH_BEFORE_ARGS=-q ** Command failed [exit code 1]: /usr/bin/script -qa /priv/down/dmw/tmp/portupgrade.86606.24 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=libgnome-2.18.0_2 UPGRADE_PORT_VER=2.18.0_2 make FETCH_BEFORE_ARGS=-q -8--8--8--8--8- Best regards, -- .O. | Daniel Molina Wegener | C/C++ Developer ..O | dmw [at] unete [dot] cl | FOSS Coding Adict OOO | FreeBSD Linux User| Standards Rocks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports problems
Download sources for software you need, and compile it manualy. but firstly i`d try to delete ports directory, and fetch ports again. Daniel Molina Wegener пишет: Hi, I've updated and upgraded the ports tree to the . branch but serveral of ports doesn't compile or are completly absent on the repositories. What can I do?, I need the system working. Best regards, ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
MailScanner Ports problems
I've been doing cvsup's on ports-all and src-all. After rebuilding world for the second time, I still get errors when building the ports. For example, I'm trying to rebuild MailScanner and I get the following: ===Verifying install for /usr/local/lib/perl5/site_perl/5.6.2/mach/Filesys/Df.pm in /usr/ports/sysutils/p5-Filesys-Df === p5-Filesys-Df-0.92 requires statvfs() which is not available before FreeBSD-5*. *** Error code 1 Stop in /usr/ports/sysutils/p5-Filesys-Df. *** Error code 1 Stop in /usr/ports/mail/mailscanner. Looks like some of the ports expect the code to have V5 routines available although I'm only updating from RELENG-4. The error message is originating from the Makefile which is specifically checking for an OS version = 5.0. Any ideas? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: MailScanner Ports problems
There was talk about this on the Mailscanner list a while ago. I use the tar.gz to install MailScanner direct (on 4.11), but then I do alot of beta testing and JPK can lag behind in getting releases out. Ask on the main MailScanner list as JPK hangs about there sometime,, -- Martin On 11/14/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I've been doing cvsup's on ports-all and src-all. After rebuilding world for the second time, I still get errors when building the ports. For example, I'm trying to rebuild MailScanner and I get the following: ===Verifying install for /usr/local/lib/perl5/site_perl/5.6.2/mach/Filesys/Df.pm in /usr/ports/sysutils/p5-Filesys-Df === p5-Filesys-Df-0.92 requires statvfs() which is not available before FreeBSD-5*. *** Error code 1 Stop in /usr/ports/sysutils/p5-Filesys-Df. *** Error code 1 Stop in /usr/ports/mail/mailscanner. Looks like some of the ports expect the code to have V5 routines available although I'm only updating from RELENG-4. The error message is originating from the Makefile which is specifically checking for an OS version = 5.0. Any ideas? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Various package/ports problems
Gerard Seibert wrote: Chris Whitehouse wrote: Dr. Jennifer Nussbaum wrote: So now i can find out what version each port is, but that doesnt help me know whether these are outdated, or to update them. For that im still stuck on the Ruby core dump problem. I did reinstall portupgrade, ruby18, and the ruby-bdb thing, but sadly i still get the same abort trap/core dump thing ive reported all along. Is there any other way i can attack this last issue? Thanks. Jen Have you tried portmanager (sysutils/portmanager)? The -s option just reports on what's required to upgrade. Assuming you have a freshly updated ports tree, you could also just run this little command: /usr/sbin/pkg_version -vIL= It will display what needs to be updated very quickly. I think that 'portmanager' would be the best way to update the ports however. Very useful and quick, but man pkg_version says the -I interrogates the INDEX file which in this case (I've lost previous posts) was corrupted or out of sync with the ports tree? In this case portmanager -s might give more accurate results even if it is a bit slow. Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Various package/ports problems
Dr. Jennifer Nussbaum wrote: So now i can find out what version each port is, but that doesnt help me know whether these are outdated, or to update them. For that im still stuck on the Ruby core dump problem. I did reinstall portupgrade, ruby18, and the ruby-bdb thing, but sadly i still get the same abort trap/core dump thing ive reported all along. Is there any other way i can attack this last issue? Thanks. Jen Have you tried portmanager (sysutils/portmanager)? The -s option just reports on what's required to upgrade. Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Various package/ports problems
Chris Whitehouse wrote: Dr. Jennifer Nussbaum wrote: So now i can find out what version each port is, but that doesnt help me know whether these are outdated, or to update them. For that im still stuck on the Ruby core dump problem. I did reinstall portupgrade, ruby18, and the ruby-bdb thing, but sadly i still get the same abort trap/core dump thing ive reported all along. Is there any other way i can attack this last issue? Thanks. Jen Have you tried portmanager (sysutils/portmanager)? The -s option just reports on what's required to upgrade. Assuming you have a freshly updated ports tree, you could also just run this little command: /usr/sbin/pkg_version -vIL= It will display what needs to be updated very quickly. I think that 'portmanager' would be the best way to update the ports however. -- Gerard Seibert [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Various package/ports problems
Kris Kennaway [EMAIL PROTECTED] wrote: On Sun, Sep 03, 2006 at 06:31:18PM -0700, Dr. Jennifer Nussbaum wrote: Kris Kennaway wrote: On Sun, Sep 03, 2006 at 05:58:36PM -0700, Dr. Jennifer Nussbaum wrote: Kris Kennaway wrote: On Mon, Aug 28, 2006 at 01:59:14PM -0700, Dr. Jennifer Nussbaum wrote: Thanks, i CAN compile from the ports collection (i never wanted to use packages). Its MANAGING this that i cant do. I can update my ports tree fine, and i can go into ports directory and do a make install, sure. But i cant do portsversion to see what needs updating, and i cant do pkg_info to find out what versions i have. So doing something like Why not (in both cases)?As i posted in the original message - the main question i was asking - both of these are broken in some way. Reposting: --- For example if i try to run portversion i get: undefined method `each' for nil:NilClass /usr/local/sbin/portversion:239: [BUG] Bus Error from Ruby (ruby 1.8.5 is up to date on the system). : pkgdb -f ~ $ sudo pkgdb -f ~ $ portversion undefined method `each' for nil:NilClass /usr/local/sbin/portversion:239: [BUG] Bus Error ruby 1.8.5 (2006-08-25) [i386-freebsd4] Abort trap (core dumped) ~ $ If i try to run pkg_info I quickly get: pkg_info: read_plist: bad command '@conflicts apache+ipv6-1.*' : Deinstall the package that was built for a later version of : FreeBSD. KrisHow do i tell which this is? Most of this box seems to be compiled from ports, not installed packages. apache+ipv6 is not installed. ~ $ pkg_info ImageMagick-nox11-6.0.2.7 Image processing tools analog-6.0_1,1 An extremely fast program for analysing WWW logfiles pkg_info: read_plist: bad command '@conflicts apache+ipv6-1.*' ~ I rebuilt analog from ports but that doesnt seem to be it. Thanks for your continued help. Jen - Get your own web address for just $1.99/1st yr. We'll help. Yahoo! Small Business. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Various package/ports problems
On Mon, Sep 04, 2006 at 04:52:08AM -0700, Dr. Jennifer Nussbaum wrote: Kris Kennaway [EMAIL PROTECTED] wrote: On Sun, Sep 03, 2006 at 06:31:18PM -0700, Dr. Jennifer Nussbaum wrote: Kris Kennaway wrote: On Sun, Sep 03, 2006 at 05:58:36PM -0700, Dr. Jennifer Nussbaum wrote: Kris Kennaway wrote: On Mon, Aug 28, 2006 at 01:59:14PM -0700, Dr. Jennifer Nussbaum wrote: Thanks, i CAN compile from the ports collection (i never wanted to use packages). Its MANAGING this that i cant do. I can update my ports tree fine, and i can go into ports directory and do a make install, sure. But i cant do portsversion to see what needs updating, and i cant do pkg_info to find out what versions i have. So doing something like Why not (in both cases)?As i posted in the original message - the main question i was asking - both of these are broken in some way. Reposting: --- For example if i try to run portversion i get: undefined method `each' for nil:NilClass /usr/local/sbin/portversion:239: [BUG] Bus Error from Ruby (ruby 1.8.5 is up to date on the system). : pkgdb -f ~ $ sudo pkgdb -f ~ $ portversion undefined method `each' for nil:NilClass /usr/local/sbin/portversion:239: [BUG] Bus Error ruby 1.8.5 (2006-08-25) [i386-freebsd4] Abort trap (core dumped) ~ $ Check the manpage, probably I meant pkgdb -fu If i try to run pkg_info I quickly get: pkg_info: read_plist: bad command '@conflicts apache+ipv6-1.*' : Deinstall the package that was built for a later version of : FreeBSD. KrisHow do i tell which this is? Most of this box seems to be compiled from ports, not installed packages. apache+ipv6 is not installed. ~ $ pkg_info ImageMagick-nox11-6.0.2.7 Image processing tools analog-6.0_1,1 An extremely fast program for analysing WWW logfiles pkg_info: read_plist: bad command '@conflicts apache+ipv6-1.*' ~ I rebuilt analog from ports but that doesnt seem to be it. grep -r @conflicts /var/db/pkg and remove all listed packages. Kris pgpIpriec72os.pgp Description: PGP signature
Re: Various package/ports problems
Kris Kennaway [EMAIL PROTECTED] wrote: On Mon, Sep 04, 2006 at 04:52:08AM -0700, Dr. Jennifer Nussbaum wrote: For example if i try to run portversion i get: undefined method `each' for nil:NilClass /usr/local/sbin/portversion:239: [BUG] Bus Error from Ruby (ruby 1.8.5 is up to date on the system). : pkgdb -f ~ $ sudo pkgdb -f ~ $ portversion undefined method `each' for nil:NilClass /usr/local/sbin/portversion:239: [BUG] Bus Error ruby 1.8.5 (2006-08-25) [i386-freebsd4] Abort trap (core dumped) ~ $ ::Check the manpage, probably I meant pkgdb -fu Sorry, i dont understand what im checking hte manpage to have it do. Running pkgdb -fu does rebuild the package database, but i get the same Bus Error thing from Ruby as above. If i try to run pkg_info I quickly get: pkg_info: read_plist: bad command '@conflicts apache+ipv6-1.*' : Deinstall the package that was built for a later version of : FreeBSD. KrisHow do i tell which this is? Most of this box seems to be compiled from ports, not installed packages. apache+ipv6 is not installed. ~ $ pkg_info ImageMagick-nox11-6.0.2.7 Image processing tools analog-6.0_1,1 An extremely fast program for analysing WWW logfiles pkg_info: read_plist: bad command '@conflicts apache+ipv6-1.*' ~ ::grep -r @conflicts /var/db/pkg and remove all listed packages. Kris Which listed packages? The output of this grep looks like: /var/db/pkg/mysql-server-4.1.20/+CONTENTS:@conflicts mysql-server-3.* /var/db/pkg/mysql-server-4.1.20/+CONTENTS:@conflicts mysql-server-4.[02-9].* /var/db/pkg/mysql-server-4.1.20/+CONTENTS:@conflicts mysql-server-5.* But i dont want to remove mysql-server-4.1.20, because this seems to be the version that is actively running on this machine, and i dont want to disable it. Same for apache+mod_ssl, which accounts for alot of the other conflicts. Also, when i try to delete one of the ports that seemed less critical, even that didnt work: ~ $ sudo pkg_delete -f jade-1.2.1_9 pkg_delete: package 'jade-1.2.1_9' is required by these other packages and may not be deinstalled (but I'll delete it anyway): sgmlformat-1.7_2 pkg_delete: read_plist: bad command '@conflicts sp-1.*' ~ ...and jade-1.2.1_9 is still there. Thank you again for your continued attention, Kris. Jen __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Various package/ports problems
On Mon, Sep 04, 2006 at 02:00:20PM -0700, Dr. Jennifer Nussbaum wrote: Kris Kennaway [EMAIL PROTECTED] wrote: On Mon, Sep 04, 2006 at 04:52:08AM -0700, Dr. Jennifer Nussbaum wrote: For example if i try to run portversion i get: undefined method `each' for nil:NilClass /usr/local/sbin/portversion:239: [BUG] Bus Error from Ruby (ruby 1.8.5 is up to date on the system). : pkgdb -f ~ $ sudo pkgdb -f ~ $ portversion undefined method `each' for nil:NilClass /usr/local/sbin/portversion:239: [BUG] Bus Error ruby 1.8.5 (2006-08-25) [i386-freebsd4] Abort trap (core dumped) ~ $ ::Check the manpage, probably I meant pkgdb -fu Sorry, i dont understand what im checking hte manpage to have it do. Running pkgdb -fu does rebuild the package database, but i get the same Bus Error thing from Ruby as above. Running which version of portupgrade? Also try 'cd /usr/ports; make fetchindex' first. If i try to run pkg_info I quickly get: pkg_info: read_plist: bad command '@conflicts apache+ipv6-1.*' : Deinstall the package that was built for a later version of : FreeBSD. KrisHow do i tell which this is? Most of this box seems to be compiled from ports, not installed packages. apache+ipv6 is not installed. ~ $ pkg_info ImageMagick-nox11-6.0.2.7 Image processing tools analog-6.0_1,1 An extremely fast program for analysing WWW logfiles pkg_info: read_plist: bad command '@conflicts apache+ipv6-1.*' ~ ::grep -r @conflicts /var/db/pkg and remove all listed packages. Kris Which listed packages? The output of this grep looks like: /var/db/pkg/mysql-server-4.1.20/+CONTENTS:@conflicts mysql-server-3.* /var/db/pkg/mysql-server-4.1.20/+CONTENTS:@conflicts mysql-server-4.[02-9].* /var/db/pkg/mysql-server-4.1.20/+CONTENTS:@conflicts mysql-server-5.* But i dont want to remove mysql-server-4.1.20, because this seems to be the version that is actively running on this machine, and i dont want to disable it. Same for apache+mod_ssl, which accounts for alot of the other conflicts. You need to recognize that you've got the system into a damaged state already, so it's going to take further intrusive work to repair it. Also, when i try to delete one of the ports that seemed less critical, even that didnt work: ~ $ sudo pkg_delete -f jade-1.2.1_9 pkg_delete: package 'jade-1.2.1_9' is required by these other packages and may not be deinstalled (but I'll delete it anyway): sgmlformat-1.7_2 pkg_delete: read_plist: bad command '@conflicts sp-1.*' ~ ...and jade-1.2.1_9 is still there. Thank you again for your continued attention, Kris. What happens if you try to reinstall it from the port, setting FORCE_PKG_REGISTER? Kris pgpNESpPRao4Z.pgp Description: PGP signature
Re: Various package/ports problems
Kris Kennaway [EMAIL PROTECTED] wrote: On Mon, Sep 04, 2006 at 02:00:20PM -0700, Dr. Jennifer Nussbaum wrote: Kris Check the manpage, probably I meant pkgdb -fu Sorry, i dont understand what im checking hte manpage to have it do. Running pkgdb -fu does rebuild the package database, but i get the same Bus Error thing from Ruby as above. Kris: Running which version of portupgrade? Also try 'cd /usr/ports; make fetchindex' first. No difference; its portupgrade version 2.0.1 (as reported by portupgrade --version). But i dont want to remove mysql-server-4.1.20, because this seems to be the version that is actively running on this machine, and i dont want to disable it. Same for apache+mod_ssl, which accounts for alot of the other conflicts. Kris: You need to recognize that you've got the system into a damaged state already, so it's going to take further intrusive work to repair it. True. But the system does WORK now, and id rather not make it NOT WORK in the process of making it easier to upgrade ports. Also, when i try to delete one of the ports that seemed less critical, even that didnt work: ~ $ sudo pkg_delete -f jade-1.2.1_9 pkg_delete: package 'jade-1.2.1_9' is required by these other packages and may not be deinstalled (but I'll delete it anyway): sgmlformat-1.7_2 pkg_delete: read_plist: bad command '@conflicts sp-1.*' ~ ...and jade-1.2.1_9 is still there. Thank you again for your continued attention, Kris. Kris: What happens if you try to reinstall it from the port, setting FORCE_PKG_REGISTER? Oh yes! This does work. After this worked i went and reinstalled all the ports listed, and now pkg_info (and pkg_delete, etc.) is working correctly. Thanks! Something working at last. So now i can find out what version each port is, but that doesnt help me know whether these are outdated, or to update them. For that im still stuck on the Ruby core dump problem. I did reinstall portupgrade, ruby18, and the ruby-bdb thing, but sadly i still get the same abort trap/core dump thing ive reported all along. Is there any other way i can attack this last issue? Thanks. Jen - Get your own web address for just $1.99/1st yr. We'll help. Yahoo! Small Business. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Various package/ports problems
On Mon, Sep 04, 2006 at 08:57:51PM -0700, Dr. Jennifer Nussbaum wrote: Kris Kennaway [EMAIL PROTECTED] wrote: On Mon, Sep 04, 2006 at 02:00:20PM -0700, Dr. Jennifer Nussbaum wrote: Kris Check the manpage, probably I meant pkgdb -fu Sorry, i dont understand what im checking hte manpage to have it do. Running pkgdb -fu does rebuild the package database, but i get the same Bus Error thing from Ruby as above. Kris: Running which version of portupgrade? Also try 'cd /usr/ports; make fetchindex' first. No difference; its portupgrade version 2.0.1 (as reported by portupgrade --version). You'll have to report this to the author. Kris: What happens if you try to reinstall it from the port, setting FORCE_PKG_REGISTER? Oh yes! This does work. After this worked i went and reinstalled all the ports listed, and now pkg_info (and pkg_delete, etc.) is working correctly. Thanks! Something working at last. Glad to hear it :) Kris pgp0BiVQc0oxI.pgp Description: PGP signature
Re: Various package/ports problems
Kris Kennaway [EMAIL PROTECTED] wrote: On Mon, Aug 28, 2006 at 01:59:14PM -0700, Dr. Jennifer Nussbaum wrote: I wish i could, but i dont have physical access to the machine - its in a remote location with no serial console. So if anything gets messed up during an upgrade, im in a hell of a lot of trouble. I dont know when i'll be able to fix this problem so until i can upgrade the OS i at least want to keep the rest of it up to date. The packages are compiled for 4.11-stable and do not work with systems much older than this (e.g. 4.8, as you discovered). You might have more luck compiling from the ports collection, although that too only supports 4.11 officially (and modern releases, of course). Thanks, i CAN compile from the ports collection (i never wanted to use packages). Its MANAGING this that i cant do. I can update my ports tree fine, and i can go into ports directory and do a make install, sure. But i cant do portsversion to see what needs updating, and i cant do pkg_info to find out what versions i have. So doing something like upgrading Perl and all it's dependencies--wow what a nightmare that would be. But for another way of fixing the problem, is there any trustworthy way i can do a clean install of 6.1 on a box i dont have access to? I can backup everything offsite and ship a CD or an external drive to the facility, if there is some way i can be assured of getting back into the box after some install procedure is run by a tech there. Jen __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Various package/ports problems
On Sun, Sep 03, 2006 at 05:58:36PM -0700, Dr. Jennifer Nussbaum wrote: Kris Kennaway [EMAIL PROTECTED] wrote: On Mon, Aug 28, 2006 at 01:59:14PM -0700, Dr. Jennifer Nussbaum wrote: I wish i could, but i dont have physical access to the machine - its in a remote location with no serial console. So if anything gets messed up during an upgrade, im in a hell of a lot of trouble. I dont know when i'll be able to fix this problem so until i can upgrade the OS i at least want to keep the rest of it up to date. The packages are compiled for 4.11-stable and do not work with systems much older than this (e.g. 4.8, as you discovered). You might have more luck compiling from the ports collection, although that too only supports 4.11 officially (and modern releases, of course). Thanks, i CAN compile from the ports collection (i never wanted to use packages). Its MANAGING this that i cant do. I can update my ports tree fine, and i can go into ports directory and do a make install, sure. But i cant do portsversion to see what needs updating, and i cant do pkg_info to find out what versions i have. So doing something like Why not (in both cases)? upgrading Perl and all it's dependencies--wow what a nightmare that would be. But for another way of fixing the problem, is there any trustworthy way i can do a clean install of 6.1 on a box i dont have access to? I can backup everything offsite and ship a CD or an external drive to the facility, if there is some way i can be assured of getting back into the box after some install procedure is run by a tech there. You can do an 'upgrade install' from the install media...it's something you should definitely practise on a local system first though (not because it's hard, but so you know what you're doing). Kris pgpj5Q9Ob5X3S.pgp Description: PGP signature
Re: Various package/ports problems
Kris Kennaway [EMAIL PROTECTED] wrote: On Sun, Sep 03, 2006 at 05:58:36PM -0700, Dr. Jennifer Nussbaum wrote: Kris Kennaway wrote: On Mon, Aug 28, 2006 at 01:59:14PM -0700, Dr. Jennifer Nussbaum wrote: Thanks, i CAN compile from the ports collection (i never wanted to use packages). Its MANAGING this that i cant do. I can update my ports tree fine, and i can go into ports directory and do a make install, sure. But i cant do portsversion to see what needs updating, and i cant do pkg_info to find out what versions i have. So doing something like Why not (in both cases)?As i posted in the original message - the main question i was asking - both of these are broken in some way. Reposting: --- For example if i try to run portversion i get: undefined method `each' for nil:NilClass /usr/local/sbin/portversion:239: [BUG] Bus Error from Ruby (ruby 1.8.5 is up to date on the system). If i try to run pkg_info I quickly get: pkg_info: read_plist: bad command '@conflicts apache+ipv6-1.*' (i googled for similar problems and there were a few other reports of this, with other packages, but no suggestion of how to fix them.) --- I manually updated Ruby and portupgrade (by updating my ports tree and going into their /usr/ports directories and doing make install) with no change. This is what i am trying to solve. Thanks. Jen - Get your own web address for just $1.99/1st yr. We'll help. Yahoo! Small Business. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Various package/ports problems
On Sun, Sep 03, 2006 at 06:31:18PM -0700, Dr. Jennifer Nussbaum wrote: Kris Kennaway [EMAIL PROTECTED] wrote: On Sun, Sep 03, 2006 at 05:58:36PM -0700, Dr. Jennifer Nussbaum wrote: Kris Kennaway wrote: On Mon, Aug 28, 2006 at 01:59:14PM -0700, Dr. Jennifer Nussbaum wrote: Thanks, i CAN compile from the ports collection (i never wanted to use packages). Its MANAGING this that i cant do. I can update my ports tree fine, and i can go into ports directory and do a make install, sure. But i cant do portsversion to see what needs updating, and i cant do pkg_info to find out what versions i have. So doing something like Why not (in both cases)?As i posted in the original message - the main question i was asking - both of these are broken in some way. Reposting: --- For example if i try to run portversion i get: undefined method `each' for nil:NilClass /usr/local/sbin/portversion:239: [BUG] Bus Error from Ruby (ruby 1.8.5 is up to date on the system). pkgdb -f If i try to run pkg_info I quickly get: pkg_info: read_plist: bad command '@conflicts apache+ipv6-1.*' (i googled for similar problems and there were a few other reports of this, with other packages, but no suggestion of how to fix them.) Deinstall the package that was built for a later version of FreeBSD. Kris pgpOQzObD7MKY.pgp Description: PGP signature
Re: Various package/ports problems
On Monday 28 August 2006 23:59, Dr. Jennifer Nussbaum wrote: Gerard Seibert [EMAIL PROTECTED] wrote: On Mon, 28 Aug 2006, Dr. Jennifer Nussbaum wrote: Hi, I inherited a FreeBSD 4.8 box that had a lot of out of date ports on it. in trying to fix some of this, i seem to have screwed up the package or ports system in a way i cant manage to fix. That is really quite an old version of FSBD. If possible, I think you would be well served by updating to the latest version - 6.1 - if possible. I may be wrong, but I do not believe that there is a lot of support for that version anymore. There is some support... I wish i could, but i dont have physical access to the machine - its in a remote location with no serial console. So if anything gets messed up during an upgrade, im in a hell of a lot of trouble. I suppose, you can update to 4.11-STABLE without physical access to the machine. I suppose it will work. Then you could use binary packages(pkg_add -r something). Packages are built for 4-STABLE. ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-4-stable/ I dont know when i'll be able to fix this problem so until i can upgrade the OS i at least want to keep the rest of it up to date. Why don't you use cvs to get your ports tree up to date? and then build everything you want? Jen. - Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Νικόλαος Βασιλειάδης Τεχνικός Δικτύου Teledome SA Φιλαρέτου 10 Δοϊράνης Καλλιθέα 176 72 Τηλ.: 210 955 1500 Φάξ: 210 956 3882 e-mail:[EMAIL PROTECTED] http://www.teledome.gr This e-mail is confidential. If you are not the intended recipient, you should not copy it, re-transmit it, use it or disclose its contents, but should return it to the sender immediately and delete the copy from your system. TELEDOME SA is not responsible for, nor endorses, any opinion, recommendation, conclusion, solicitation, offer or agreement or any information contained in this communication. TELEDOME SA cannot accept any responsibility for the accuracy or completeness of this message as it has been transmitted over a public network. If you suspect that the message may have been intercepted or amended, please contact the sender. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Various package/ports problems
On Mon, Aug 28, 2006 at 01:59:14PM -0700, Dr. Jennifer Nussbaum wrote: I wish i could, but i dont have physical access to the machine - its in a remote location with no serial console. So if anything gets messed up during an upgrade, im in a hell of a lot of trouble. I dont know when i'll be able to fix this problem so until i can upgrade the OS i at least want to keep the rest of it up to date. The packages are compiled for 4.11-stable and do not work with systems much older than this (e.g. 4.8, as you discovered). You might have more luck compiling from the ports collection, although that too only supports 4.11 officially (and modern releases, of course). Kris pgpGbuUs7AIkx.pgp Description: PGP signature
Various package/ports problems
Hi, I inherited a FreeBSD 4.8 box that had a lot of out of date ports on it. in trying to fix some of this, i seem to have screwed up the package or ports system in a way i cant manage to fix. For example if i try to run portversion i get: undefined method `each' for nil:NilClass /usr/local/sbin/portversion:239: [BUG] Bus Error from Ruby (ruby 1.8.5 is up to date on the system). If i try to run pkg_info I quickly get: pkg_info: read_plist: bad command '@conflicts apache+ipv6-1.*' (i googled for similar problems and there were a few other reports of this, with other packages, but no suggestion of how to fix them.) If i try to rebuild my ports index, I get gnopernicus-0.12.0: /usr/ports/accessibility/gnome-speech non-existent -- dependency list incomplete and nothing will go further. How can i get all of this sorted? i was really hoping to be able to update most of this sytem but now i cant even get started to find out what needs it :-( Jen - All-new Yahoo! Mail - Fire up a more powerful email and get things done faster. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Various package/ports problems
On Mon, 28 Aug 2006, Dr. Jennifer Nussbaum wrote: Hi, I inherited a FreeBSD 4.8 box that had a lot of out of date ports on it. in trying to fix some of this, i seem to have screwed up the package or ports system in a way i cant manage to fix. For example if i try to run portversion i get: undefined method `each' for nil:NilClass /usr/local/sbin/portversion:239: [BUG] Bus Error from Ruby (ruby 1.8.5 is up to date on the system). If i try to run pkg_info I quickly get: pkg_info: read_plist: bad command '@conflicts apache+ipv6-1.*' (i googled for similar problems and there were a few other reports of this, with other packages, but no suggestion of how to fix them.) If i try to rebuild my ports index, I get gnopernicus-0.12.0: /usr/ports/accessibility/gnome-speech non-existent -- dependency list incomplete and nothing will go further. How can i get all of this sorted? i was really hoping to be able to update most of this sytem but now i cant even get started to find out what needs it :-( Jen That is really quite an old version of FSBD. If possible, I think you would be well served by updating to the latest version - 6.1 - if possible. I may be wrong, but I do not believe that there is a lot of support for that version anymore. -- Gerard Seibert [EMAIL PROTECTED] Has anyone ever tasted an end? Are they really bitter? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Various package/ports problems
On Aug 28, 2006, at 1:21 PM, Gerard Seibert wrote: On Mon, 28 Aug 2006, Dr. Jennifer Nussbaum wrote: Hi, I inherited a FreeBSD 4.8 box that had a lot of out of date ports on it. in trying to fix some of this, i seem to have screwed up the package or ports system in a way i cant manage to fix. For example if i try to run portversion i get: undefined method `each' for nil:NilClass /usr/local/sbin/portversion:239: [BUG] Bus Error from Ruby (ruby 1.8.5 is up to date on the system). If i try to run pkg_info I quickly get: pkg_info: read_plist: bad command '@conflicts apache+ipv6-1.*' (i googled for similar problems and there were a few other reports of this, with other packages, but no suggestion of how to fix them.) If i try to rebuild my ports index, I get gnopernicus-0.12.0: /usr/ports/accessibility/gnome-speech non- existent -- dependency list incomplete and nothing will go further. How can i get all of this sorted? i was really hoping to be able to update most of this sytem but now i cant even get started to find out what needs it :-( Jen That is really quite an old version of FSBD. If possible, I think you would be well served by updating to the latest version - 6.1 - if possible. I may be wrong, but I do not believe that there is a lot of support for that version anymore. -- Gerard Seibert [EMAIL PROTECTED] Has anyone ever tasted an end? Are they really bitter? Version 4.x is no longer supported by FreeBSD at all. I suggest either reinstalling FreeBSD 5.4 or just install 6.1. -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Various package/ports problems
Gerard Seibert [EMAIL PROTECTED] wrote: On Mon, 28 Aug 2006, Dr. Jennifer Nussbaum wrote: Hi, I inherited a FreeBSD 4.8 box that had a lot of out of date ports on it. in trying to fix some of this, i seem to have screwed up the package or ports system in a way i cant manage to fix. That is really quite an old version of FSBD. If possible, I think you would be well served by updating to the latest version - 6.1 - if possible. I may be wrong, but I do not believe that there is a lot of support for that version anymore. I wish i could, but i dont have physical access to the machine - its in a remote location with no serial console. So if anything gets messed up during an upgrade, im in a hell of a lot of trouble. I dont know when i'll be able to fix this problem so until i can upgrade the OS i at least want to keep the rest of it up to date. Jen. - Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Various package/ports problems
In response to Garrett Cooper [EMAIL PROTECTED]: Version 4.x is no longer supported by FreeBSD at all. I suggest either reinstalling FreeBSD 5.4 or just install 6.1. That's a bit of an exaggeration. http://security.freebsd.org/#adv FreeBSD 4.11 and 4-STABLE are officially supported until Jan 2007. although 4.8 hasn't been supported in quite a while. -- Bill Moran Collaborative Fusion Inc. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Various package/ports problems
Gosh.. I'm still enjoying my 4.11 prod box ( most of it ).. well time to think abt migration? - Original Message - From: Bill Moran [EMAIL PROTECTED] To: Garrett Cooper [EMAIL PROTECTED] Subject: Re: Various package/ports problems Date: Mon, 28 Aug 2006 17:01:33 -0400 In response to Garrett Cooper [EMAIL PROTECTED]: Version 4.x is no longer supported by FreeBSD at all. I suggest either reinstalling FreeBSD 5.4 or just install 6.1. That's a bit of an exaggeration. http://security.freebsd.org/#adv FreeBSD 4.11 and 4-STABLE are officially supported until Jan 2007. although 4.8 hasn't been supported in quite a while. -- Bill Moran Collaborative Fusion Inc. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- ___ Play 100s of games for FREE! http://games.mail.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports problems
RYAN vAN GINNEKEN [EMAIL PROTECTED] writes: when i run portsdb -Uu i get many errors like the one below is there anyone who can help me fileroller-2.4.2_1,1:/usr/ports/x11-toolkits/pango non-existent -- dependency list incomplete That just means you didn't have /usr/ports/x11-toolkits/pango in your ports tree. Assuming this is intentional (you didn't update the whole ports tree for some reason?) then there's no problem. If you wanted to update the whole tree, then you need to figure out what you did wrong with your update operation (e.g., maybe you need to get rid of a refuse file for the ports collection). ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports problems
Lowell Gilbert wrote: RYAN vAN GINNEKEN [EMAIL PROTECTED] writes: when i run portsdb -Uu i get many errors like the one below is there anyone who can help me fileroller-2.4.2_1,1:/usr/ports/x11-toolkits/pango non-existent -- dependency list incomplete That just means you didn't have /usr/ports/x11-toolkits/pango in your ports tree. Assuming this is intentional (you didn't update the whole ports tree for some reason?) then there's no problem. If you wanted to update the whole tree, then you need to figure out what you did wrong with your update operation (e.g., maybe you need to get rid of a refuse file for the ports collection). Also note, that there errors are not completely unheard of. I run a ports cvsup nightly, update the index database, and send the output of portversion to myself. looking back in my logs, it looks as if i almost always have at least a few of these types of errors ~jon -- Yesterday upon the stair I saw a man who wasn't there, he wasn't there again today, oh how i wish he'd go away Rev. Jonathan T. Sage Lighting / Set Designer Professional Web Design [HTTP://thr.msu.edu] [EMAIL PROTECTED] [PGP: www.keyserver.net] pgp0.pgp Description: PGP signature
Re: ports problems
On Tue, 02 Dec 2003 11:28:22 -0500 Jonathan T. Sage [EMAIL PROTECTED] wrote: Lowell Gilbert wrote: RYAN vAN GINNEKEN [EMAIL PROTECTED] writes: when i run portsdb -Uu i get many errors like the one below is there anyone who can help me fileroller-2.4.2_1,1:/usr/ports/x11-toolkits/pango non-existent -- dependency list incomplete That just means you didn't have /usr/ports/x11-toolkits/pango in your ports tree. Assuming this is intentional (you didn't update the whole ports tree for some reason?) then there's no problem. If you wanted to update the whole tree, then you need to figure out what you did wrong with your update operation (e.g., maybe you need to get rid of a refuse file for the ports collection). Also note, that there errors are not completely unheard of. I run a ports cvsup nightly, update the index database, and send the output of portversion to myself. looking back in my logs, it looks as if i almost always have at least a few of these types of errors Try using 'make index then 'portsdb -u' instead, this seems to almost always give me better results. Set your /usr/local/etc/pkgtools.conf variables appropriately. Regards, Stephen Hilton [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports problems
On Tue, 2 Dec 2003 13:36:52 -0600 Stephen Hilton [EMAIL PROTECTED] wrote: On Tue, 02 Dec 2003 11:28:22 -0500 Jonathan T. Sage [EMAIL PROTECTED] wrote: Lowell Gilbert wrote: RYAN vAN GINNEKEN [EMAIL PROTECTED] writes: when i run portsdb -Uu i get many errors like the one below is there anyone who can help me fileroller-2.4.2_1,1:/usr/ports/x11-toolkits/pango non-existent -- dependency list incomplete That just means you didn't have /usr/ports/x11-toolkits/pango in your ports tree. Assuming this is intentional (you didn't update the whole ports tree for some reason?) then there's no problem. If you wanted to update the whole tree, then you need to figure out what you did wrong with your update operation (e.g., maybe you need to get rid of a refuse file for the ports collection). Also note, that there errors are not completely unheard of. I run a ports cvsup nightly, update the index database, and send the output of portversion to myself. looking back in my logs, it looks as if i almost always have at least a few of these types of errors Try using 'make index then 'portsdb -u' instead, this seems to almost always give me better results. Set your /usr/local/etc/pkgtools.conf variables appropriately. This may help also: http://www.freebsd.org/cgi/getmsg.cgi?fetch=2841035+2848911+ /usr/local/www/db/text/2003/freebsd-questions/20031130.freebsd-questions Regards, Stephen Hilton [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports problems
Stephen Hilton wrote: *snip* when i run portsdb -Uu i get many errors like the one below is there anyone who can help me *snip* Also note, that there errors are not completely unheard of. I run a ports cvsup nightly, update the index database, and send the output of portversion to myself. looking back in my logs, it looks as if i almost always have at least a few of these types of errors Try using 'make index then 'portsdb -u' instead, this seems to almost always give me better results. Set your /usr/local/etc/pkgtools.conf variables appropriately. Steven - any idea what the time (speed) difference is on this? more of a curiosity that a question... ~j -- Yesterday upon the stair I saw a man who wasn't there, he wasn't there again today, oh how i wish he'd go away Rev. Jonathan T. Sage Lighting / Set Designer Professional Web Design [HTTP://thr.msu.edu] [EMAIL PROTECTED] [PGP: www.keyserver.net] pgp0.pgp Description: PGP signature
ports problems
when i run portsdb -Uu i get many errors like the one below is there anyone who can help me ileroller-2.4.2_1,1:/usr/ports/x11-toolkits/pango non-existent -- dependency list incomplete fileroller-2.4.2_1,1:/usr/ports/x11-toolkits/gtk20 non-existent -- dependency list incomplete fileroller-2.4.2_1,1:/usr/ports/graphics/libgnomecanvas non-existent -- dependency list incomplete fileroller-2.4.2_1,1:/usr/ports/graphics/libart_lgpl2 non-existent -- dependency list incomplete fileroller-2.4.2_1,1:/usr/ports/x11/libgnome non-existent -- dependency list incomplete fileroller-2.4.2_1,1:/usr/ports/x11-toolkits/libbonoboui non-existent -- dependency list incomplete fileroller-2.4.2_1,1:/usr/ports/x11-toolkits/libgnomeui non-existent -- dependency list incomplete ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports problems
On Dec 1, 2003, at 7:28 PM, RYAN vAN GINNEKEN wrote: when i run portsdb -Uu i get many errors like the one below is there anyone who can help me try pkgdb -F and see how that goes. -- Paul Beard paulbeard.no-ip.org/movabletype/ paulbeard [at] mac.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Ports problems
I have a problem installing from the ports collection. No matter what i try to install i get an error 1 when it is trying to check if the port i allready installed. I tried running pkdb -F, but that does not help. any ideas ? /thomas ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports problems
On tirsdag, jul 15, 2003, at 00:18 Europe/Copenhagen, Patrick O'Reilly wrote: From: Thomas von Hassel [EMAIL PROTECTED] I have a problem installing from the ports collection. No matter what i try to install i get an error 1 when it is trying to check if the port i allready installed. I tried running pkdb -F, but that does not help. any ideas ? Sometimes it helps to do a 'make clean', then try 'make install' again. been there, tried that, it also doesn't work for ports that were never installed before ... /thomas ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports problems
In bish.lists.freebsd.questions, you wrote: I have a problem installing from the ports collection. No matter what i try to install i get an error 1 when it is trying to check if the port i allready installed. I tried running pkdb -F, but that does not help. any ideas ? Yes, I'd noticed this too - only today. It appears the Mk file has been changed to use the -O option of pkg_info That is a new option, that wasn't added to pkg_info on a release version until FreeBSD 4.7-RELEASE So someone will either have to regress it, or you'll need to upgrade to freebsd 4.8, or patch pkg_info (/usr/src/usr.sbin/pkg_install/info) Work Around ~~~ Define the environment variable FORCE_PKG_REGISTER to anything from the command line before running the install, it will work (as it will skip the part that checks if the port is already installed.) Fix ~~~ For my machine on 4.4 I needed to download and replace /usr/share/Mk/* and then /usr/src/usr.sbin/pkg_install/* from the freebsd 4.8 sources. Your /usr/share/Mk may be recent enough.. I don't know. from there, cd to /usr/src/usr.sbin/pkg_install and make make install make clean Alternatively, download my binaries, made from 4.8-release sources. De-tar the bzipped archive, and move the files from usr.sbin into /usr/sbin and the files from usr.share.man.man1 into /usr/share/man/man1 - being careful to preserve file permissions. http://www.bishopston.com/jamie/pkg_install/pkg_install_binaries_4.8.tar.bz2 (approx 90K) Cheers, Jamie ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports problems
On tirsdag, jul 15, 2003, at 01:07 Europe/Copenhagen, Jamie Jones wrote: In bish.lists.freebsd.questions, you wrote: I have a problem installing from the ports collection. No matter what i try to install i get an error 1 when it is trying to check if the port i allready installed. I tried running pkdb -F, but that does not help. any ideas ? Yes, I'd noticed this too - only today. It appears the Mk file has been changed to use the -O option of pkg_info That is a new option, that wasn't added to pkg_info on a release version until FreeBSD 4.7-RELEASE aaah ok, this system is 4.6. I have a 4.8 system too that obviously doesn't have that problem. Thanx allot. /thomas ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports problems
aaah ok, this system is 4.6. I have a 4.8 system too that obviously doesn't have that problem. Thanx allot. Hi. The patch I listed fixed the problem on my 4.4 and my 4.5 machines. It's compiled generically, so will work on all i386 systems. Alternateively, if your 4.8 system has a non-cpu specific build, (or the 4.6 system has the same cpu) simpy copy /usr/sbin/pkg_* over from 4.8 to 4.6 (and /usr/share/man/man1/pkg_* to also update the man pages) Cheers, jamie ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports problems
On Mon, Jul 14, 2003 at 11:49:02PM +0200, Thomas von Hassel wrote: I have a problem installing from the ports collection. No matter what i try to install i get an error 1 when it is trying to check if the port i allready installed. I tried running pkdb -F, but that does not help. Old releases are not officially supported. Update to 4.8 or wait a few days until I can commit a patch. Kris pgp0.pgp Description: PGP signature
