Re: Problem with portupgrade
On April 6, 2007, [EMAIL PROTECTED] wrote:
deimos# portupgrade -PR libmpeg2
[Updating the portsdb format:bdb_btree in /usr/ports ... - 16851
port entries found
{lines cut} . done]
[missing key: categories: Cannot read the portsdb!
database file error
{following some ruby errors regarding the fact that the db can't be
read?!}
Try removing (or moving so you have a backup) your
/var/db/pkg/pkgdb.db file, then running pkgdb -u to update/create it.
Josh
I did that, it recreated the file w/o errors, but i get the same error
message.
Have you read the note of 20070205 in /usr/src/UPDATING? It looks you're
running the old version. Check the details in the note, remove portupgrade
and install it from the new location.
Andriy
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem with portupgrade
Hello,
I'm running 6.2-RELEASE-p2, SMP, x86.
I get the following error when using portupgrade (on every port, not
just this one):
deimos# portupgrade -PR libmpeg2
[Updating the portsdb format:bdb_btree in /usr/ports ... - 16851
port entries found
{lines cut} . done]
[missing key: categories: Cannot read the portsdb!
database file error
{following some ruby errors regarding the fact that the db can't be
read?!}
In /usr/ports/ i have .portsnap.INDEX, INDEX, INDEX-5, INDEX-6,
INDEX-6.db, and of course the ports folders.
Any idea what i'm doing wrong?
Thanks.
--
Best regards,
Ghirai.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with portupgrade
deimos# portupgrade -PR libmpeg2
[Updating the portsdb format:bdb_btree in /usr/ports ... - 16851
port entries found
{lines cut} . done]
[missing key: categories: Cannot read the portsdb!
database file error
{following some ruby errors regarding the fact that the db can't be
read?!}
Try removing (or moving so you have a backup) your
/var/db/pkg/pkgdb.db file, then running pkgdb -u to update/create it.
Josh
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re[2]: Problem with portupgrade
Hello Josh,
Friday, April 6, 2007, 11:08:02 PM, you wrote:
deimos# portupgrade -PR libmpeg2
[Updating the portsdb format:bdb_btree in /usr/ports ... - 16851
port entries found
{lines cut} . done]
[missing key: categories: Cannot read the portsdb!
database file error
{following some ruby errors regarding the fact that the db can't be
read?!}
Try removing (or moving so you have a backup) your
/var/db/pkg/pkgdb.db file, then running pkgdb -u to update/create it.
Josh
I did that, it recreated the file w/o errors, but i get the same error
message.
--
Best regards,
Ghirai.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re[3]: Problem with portupgrade - SOLVED
Hello Ghirai,
Friday, April 6, 2007, 11:48:29 PM, you wrote:
Hello Josh,
Friday, April 6, 2007, 11:08:02 PM, you wrote:
deimos# portupgrade -PR libmpeg2
[Updating the portsdb format:bdb_btree in /usr/ports ... - 16851
port entries found
{lines cut} . done]
[missing key: categories: Cannot read the portsdb!
database file error
{following some ruby errors regarding the fact that the db can't be
read?!}
Try removing (or moving so you have a backup) your
/var/db/pkg/pkgdb.db file, then running pkgdb -u to update/create it.
Josh
I did that, it recreated the file w/o errors, but i get the same error
message.
I did a make deinstall and a make reinstall for portupgrade, which
bumped the version mumber.
It works now.
Compiling new versions, hopefully everything will turn out ok.
I'll report back.
--
Best regards,
Ghirai.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
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]
Problem with portupgrade on 4.11-STABLE
For the past month or so I have a couple of ports that will no longer build on upgrade (graphics/libaux and x11-fonts/XFree86-4-fontEncodings) The precise error is: == Configuring for libaux-1.0_1 imake -DUseInstalled -I/usr/X11R6/lib/X11/config In file included from Imakefile.c:16: /usr/X11R6/lib/X11/config/Imake.tmpl:2136: noop.rules: No such file or directoryIn file included from Imakefile.c:16: /usr/X11R6/lib/X11/config/Imake.tmpl:2149: noop.rules: No such file or directoryimake: Exit code 1. --- I presume that I have something out of date that CVSUP/portupgrade failed to pick up on but I'm not sure what... Any suggestions ? Thanks a ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with portupgrade on 4.11-STABLE
On Sat, Apr 15, 2006 at 10:57:58PM -, [EMAIL PROTECTED] wrote: For the past month or so I have a couple of ports that will no longer build on upgrade (graphics/libaux and x11-fonts/XFree86-4-fontEncodings) OK, this isn't a problem with portupgrade then, it's a problem with those two ports. The precise error is: == Configuring for libaux-1.0_1 imake -DUseInstalled -I/usr/X11R6/lib/X11/config In file included from Imakefile.c:16: /usr/X11R6/lib/X11/config/Imake.tmpl:2136: noop.rules: No such file or directoryIn file included from Imakefile.c:16: /usr/X11R6/lib/X11/config/Imake.tmpl:2149: noop.rules: No such file or directoryimake: Exit code 1. --- I presume that I have something out of date that CVSUP/portupgrade failed to pick up on but I'm not sure what... Maybe your imake installation is broken, but it could also be a more subtle problem; note that FreeBSD 4.x is no longer well-supported by the ports collection since the world has moved on to running 6.x. Kris pgp0jewrSDWeq.pgp Description: PGP signature
Re: Problem with portupgrade on 4.11-STABLE
Ok thanks. I'm going to presume the problem is with the ports and I either need to upgrade to 6.x or wait until the ports are fixed. Hum. I guess I should check README/UPDATING to see how painful it will be to upgrade to 6.x. Thanks, a ||From [EMAIL PROTECTED] Sat Apr 15 16:23:25 2006 ||On Sat, Apr 15, 2006 at 10:57:58PM -, [EMAIL PROTECTED] wrote: ||=20 || For the past month or so I have a couple of ports that will no longer || build on upgrade (graphics/libaux and x11-fonts/XFree86-4-fontEncodings) ||OK, this isn't a problem with portupgrade then, it's a problem with ||those two ports. || The precise error is: ||=20 || =3D=3D Configuring for libaux-1.0_1 || imake -DUseInstalled -I/usr/X11R6/lib/X11/config || In file included from Imakefile.c:16: || /usr/X11R6/lib/X11/config/Imake.tmpl:2136: noop.rules: No such file or di= ||rectoryIn file included from Imakefile.c:16: || /usr/X11R6/lib/X11/config/Imake.tmpl:2149: noop.rules: No such file or di= ||rectoryimake: Exit code 1. || --- ||=20 || I presume that I have something out of date that CVSUP/portupgrade failed || to pick up on but I'm not sure what... ||Maybe your imake installation is broken, but it could also be a more ||subtle problem; note that FreeBSD 4.x is no longer well-supported by ||the ports collection since the world has moved on to running 6.x. ||Kris ||--ikeVEW9yuYc//A+q ||Content-Type: application/pgp-signature ||Content-Disposition: inline ||-BEGIN PGP SIGNATURE- ||Version: GnuPG v1.4.2.2 (FreeBSD) ||iD8DBQFEQYBnWry0BWjoQKURAnXOAKD7Rt1+6S+ScoGOeJZ1ni7VdzlbfwCgpp6D ||XpUNmXg2IIeA4OOPIZ4Cs1o= ||=S1JV ||-END PGP SIGNATURE- ||--ikeVEW9yuYc//A+q-- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem with portupgrade et. al. dumping core
I get the following when running portversion (or portversion -l '', or pkgdb, etc) =[EMAIL PROTECTED] portversion [Updating the pkgdb format:bdb1_btree in /var/db/pkg ... - 45 packages found (-3 +4) (...)(? portupgrade-20041226).Abort trap (core dumped) =[EMAIL PROTECTED] pkgdb -F --- Checking the package registry database [Updating the pkgdb format:bdb1_btree in /var/db/pkg ... - 45 packages found (-3 +4) (...)(? portupgrade-20041226)(? ruby-1.8.2_1)(? ruby18-bdb1-0.2.2).Abort trap (core dumped) I have a freshly (today) cvsupped ports tree, and have run portsdb -Uu. The machine is running 4.9 stable from march of last year. I have read /usr/ports/UPDATING and have tried uninstalling and reinstalling portupgrade alone, as well as uninstalling and reinstalling ruby_18, ruby_bdb, and portupgrade. I have also tried adding the following to my pkgtools.conf without it making any difference: ENV['PORTS_DBDRIVER'] = 'bdb1_hash' Here are the versions: ruby-1.8.2_1 ruby18-bdb1-0.2.2 portupgrade-20041226_1 My ports tree is maintained on one machine and shared over the network to several other machines. No other machines are having this problem and are running the same versions of the above software. Some have more current versions of the OS and some run stable from last march. Any suggestions on how to debug this further or outright solutions would be appreciated. Thanks -- Clint Gilders [EMAIL PROTECTED] Director of Technology Services OnlineHobbyist.com, Inc. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Package version problem with portupgrade(1)
On Thursday 02 September 2004 01:45 am, Philip Payne wrote: Well, png is up to png-1.2.5_8 and if you did a recent cvsup and recreated your INDEXs, that is what you should be seeing. OK, portupgrade(1) _is_ looking for 1.2.5_8 but it is trying to get it from ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-4.9-release/All where the version of png is 1.2.5_2, so how to resolve the conflict? Seems to me that portupgrade(1) needs to be getting the packages from packages-4-stable/All instead? Staying behind is a good way to end up with a security black hole :). Precisely. A cvsup of ports-all and a portsdb -uU should be a good way to keep your system current. Will that change where portupgrade(1) tries to get the packages from? I believe the package updates will lag behind the ports source update i.e. if you use portupgrade -PP and use packages only there will be the occasional port that does not have a package available. I'm not sure how long the lag is... I guess different for different ports. I think you'll just have to accept a slight lag on when you can update certain ports. If this is not the real error I'm sure someone will correct me. His PACKAGESITE environment variable is set to a wrong location. I think that he needs to set it using something like setenv PACKAGESITE ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-4-stable/All or his favorite mirror, as all one line. and then run portupgrade -PPa. It defaults to the 4.9 release packages and they never change. I have only used PACKAGESITE once and that was to update KDE. The sites were so busy that my computer would build it almost as fast as I could download it. Ah, OK. That makes sense. Didn't realise the package path problem. If you're using portinstall then you can set alternative package sites in /usr/local/etc/pkgtools.conf rather than setting the PACKAGESITE environment variable. Phil. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Package version problem with portupgrade(1)
kstewart wrote: His PACKAGESITE environment variable is set to a wrong location. I think that he needs to set it using something like setenv PACKAGESITE ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-4-stable/All Thanks Kent, but it didn't work. Setting it made it search in ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/All. I eventually found that it's PKG_SITES that needs setting (and you don't include 'All') after trawling through pkgtools.conf. Unfortunately it's not documented in the portupgrade manpage. Anyway, I've got it all working now - thanks for the push in the right direction, and thanks Phil too for the input. Regards, Mark or his favorite mirror, as all one line. and then run portupgrade -PPa. It defaults to the 4.9 release packages and they never change. I have only used PACKAGESITE once and that was to update KDE. The sites were so busy that my computer would build it almost as fast as I could download it. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Package version problem with portupgrade(1)
On Friday 03 September 2004 11:23 am, Mark Ovens wrote: kstewart wrote: His PACKAGESITE environment variable is set to a wrong location. I think that he needs to set it using something like setenv PACKAGESITE ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-4-stable/All Thanks Kent, but it didn't work. Setting it made it search in ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/All. I eventually found that it's PKG_SITES that needs setting (and you don't include 'All') after trawling through pkgtools.conf. Unfortunately it's not documented in the portupgrade manpage. Great! I tried it and it didn't work but I will save this for next time :). I use it so rarely that the mechanism is usally forgotten by the next time :). Kent Anyway, I've got it all working now - thanks for the push in the right direction, and thanks Phil too for the input. Regards, Mark or his favorite mirror, as all one line. and then run portupgrade -PPa. It defaults to the 4.9 release packages and they never change. I have only used PACKAGESITE once and that was to update KDE. The sites were so busy that my computer would build it almost as fast as I could download it. -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html Support the Bison at http://www.buffalofieldcampaign.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Package version problem with portupgrade(1)
Well, png is up to png-1.2.5_8 and if you did a recent cvsup and recreated your INDEXs, that is what you should be seeing. OK, portupgrade(1) _is_ looking for 1.2.5_8 but it is trying to get it from ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-4.9-release/All where the version of png is 1.2.5_2, so how to resolve the conflict? Seems to me that portupgrade(1) needs to be getting the packages from packages-4-stable/All instead? Staying behind is a good way to end up with a security black hole :). Precisely. A cvsup of ports-all and a portsdb -uU should be a good way to keep your system current. Will that change where portupgrade(1) tries to get the packages from? I believe the package updates will lag behind the ports source update i.e. if you use portupgrade -PP and use packages only there will be the occasional port that does not have a package available. I'm not sure how long the lag is... I guess different for different ports. I think you'll just have to accept a slight lag on when you can update certain ports. If this is not the real error I'm sure someone will correct me. Thanks, Phil. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Package version problem with portupgrade(1)
On Thursday 02 September 2004 01:45 am, Philip Payne wrote: Well, png is up to png-1.2.5_8 and if you did a recent cvsup and recreated your INDEXs, that is what you should be seeing. OK, portupgrade(1) _is_ looking for 1.2.5_8 but it is trying to get it from ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-4.9-release/All where the version of png is 1.2.5_2, so how to resolve the conflict? Seems to me that portupgrade(1) needs to be getting the packages from packages-4-stable/All instead? Staying behind is a good way to end up with a security black hole :). Precisely. A cvsup of ports-all and a portsdb -uU should be a good way to keep your system current. Will that change where portupgrade(1) tries to get the packages from? I believe the package updates will lag behind the ports source update i.e. if you use portupgrade -PP and use packages only there will be the occasional port that does not have a package available. I'm not sure how long the lag is... I guess different for different ports. I think you'll just have to accept a slight lag on when you can update certain ports. If this is not the real error I'm sure someone will correct me. His PACKAGESITE environment variable is set to a wrong location. I think that he needs to set it using something like setenv PACKAGESITE ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-4-stable/All or his favorite mirror, as all one line. and then run portupgrade -PPa. It defaults to the 4.9 release packages and they never change. I have only used PACKAGESITE once and that was to update KDE. The sites were so busy that my computer would build it almost as fast as I could download it. Kent Thanks, Phil. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html Support the Bison at http://www.buffalofieldcampaign.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Package version problem with portupgrade(1)
FreeBSD postie 4.9-RELEASE FreeBSD 4.9-RELEASE #1: Sun Mar 21 19:46:39 GMT 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/POSTIE i386 I'm trying to upgrade cups-base on this system, using packages (as the machine doesn't really have enough grunt for building ports), with portupgrade, but it is trying to get the wrong version: postie# portupgrade -RPPv cups-base --- Session started at: Wed, 01 Sep 2004 17:27:46 +0100 --- Checking the availability of the latest package of 'graphics/png' --- Fetching the package(s) for 'png-1.2.5_8' (graphics/png) --- Fetching png-1.2.5_8 ++ Will try the following sites in the order named: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4.9-release/ --- Invoking a command: /usr/bin/fetch -o '/var/tmp/png-1.2.5_8.tgz' 'ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4.9-release/All/png-1.2.5_8.tgz' fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4.9-release/All/png-1.2.5_8.tgz: File unavailable (e.g., file not found, no access) ** The command returned a non-zero exit status: 1 ** Failed to fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4.9-release/All/png-1.2.5_8.tgz The actual file in ports/i386/packages-4.9-release/All/ is png-1.2.5_2 I'm guessing that this is caused because my ports tree was cvsup'd and so is more up to date than the packages built for 4.9-RELEASE. Thing is, how to deal with it? I could set $PKG_SITES in pkgtools.conf to use packages-4.9-release/Latest but the files there have no version number at all, e.g. png.tgz What's the best solution here - before I go and screw my system ;-) Thanks. Regards, Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Package version problem with portupgrade(1)
On Wednesday 01 September 2004 12:41 pm, Mark Ovens wrote: FreeBSD postie 4.9-RELEASE FreeBSD 4.9-RELEASE #1: Sun Mar 21 19:46:39 GMT 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/POSTIE i386 I'm trying to upgrade cups-base on this system, using packages (as the machine doesn't really have enough grunt for building ports), with portupgrade, but it is trying to get the wrong version: postie# portupgrade -RPPv cups-base --- Session started at: Wed, 01 Sep 2004 17:27:46 +0100 --- Checking the availability of the latest package of 'graphics/png' --- Fetching the package(s) for 'png-1.2.5_8' (graphics/png) --- Fetching png-1.2.5_8 ++ Will try the following sites in the order named: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4.9-release/ --- Invoking a command: /usr/bin/fetch -o '/var/tmp/png-1.2.5_8.tgz' 'ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4.9-release/All/png- 1.2.5_8.tgz' fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4.9-release/All/png-1 .2.5_8.tgz: File unavailable (e.g., file not found, no access) ** The command returned a non-zero exit status: 1 ** Failed to fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4.9-release/All/png-1 .2.5_8.tgz The actual file in ports/i386/packages-4.9-release/All/ is png-1.2.5_2 I'm guessing that this is caused because my ports tree was cvsup'd and so is more up to date than the packages built for 4.9-RELEASE. Thing is, how to deal with it? I could set $PKG_SITES in pkgtools.conf to use packages-4.9-release/Latest but the files there have no version number at all, e.g. png.tgz What's the best solution here - before I go and screw my system ;-) Well, png is up to png-1.2.5_8 and if you did a recent cvsup and recreated your INDEXs, that is what you should be seeing. Staying behind is a good way to end up with a security black hole :). A cvsup of ports-all and a portsdb -uU should be a good way to keep your system current. Kent Thanks. Regards, Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html Support the Bison at http://www.buffalofieldcampaign.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Package version problem with portupgrade(1)
kstewart wrote: Well, png is up to png-1.2.5_8 and if you did a recent cvsup and recreated your INDEXs, that is what you should be seeing. OK, portupgrade(1) _is_ looking for 1.2.5_8 but it is trying to get it from ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-4.9-release/All where the version of png is 1.2.5_2, so how to resolve the conflict? Seems to me that portupgrade(1) needs to be getting the packages from packages-4-stable/All instead? Staying behind is a good way to end up with a security black hole :). Precisely. A cvsup of ports-all and a portsdb -uU should be a good way to keep your system current. Will that change where portupgrade(1) tries to get the packages from? Thanks. Regards, Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problem with portupgrade.. or so it seems
On Tuesday 24 August 2004 03:26 pm, LiQuiD [EMAIL PROTECTED] wrote: Hi all, I have a machine running 4.10 stable that has a problem whenever I try to run portsdb -Uu. The message the scrolls down the screen is as follows: /usr/ports/INDEX:11586:Port info line must consist of 10 fields. That number changes... it basically goes from 0 to that (for all I know) as I can only go as far back as about 11300 Well, a recent poster with this problem was able to solve it by updating portupgrade and the ports Makefiles (do make sure to search the list archives before asking a question). You might also try to cvsup again, as sometimes this happens when you cvsup in the middle of an update on the server. Are you using a refuse file? If you're going to generate your own INDEX, you shouldn't refuse any of the ports branches when you cvsup. This is a common problem - it's happened to me - although I'm not sure it would generate this error. - jt ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
problem with portupgrade.. or so it seems
Hi all, I have a machine running 4.10 stable that has a problem whenever I try to run portsdb -Uu. The message the scrolls down the screen is as follows: /usr/ports/INDEX:11586:Port info line must consist of 10 fields. That number changes... it basically goes from 0 to that (for all I know) as I can only go as far back as about 11300 I tried deleting the INDEX, INDEX.db files and such from /usr/ports and running make index to generate a new one, and I keep getting this error. I have even tried using a new tool I recently learned of here on this list called portindex, and I get the same error, except I don't have to wait 2 hours to see it. I even went as far as to delete /var/db/pkg/pkgdb.db and even rm -rf /usr/ports/* and using sysinstall to reinstall the ports. I can't avoid getting that error, and the result is portinstall simply doesn't work because it can't find any packages. The odd thing is that another box had freebsd installed and upgraded to -STABLE at about the same time, and while it at first had the same error, forcing portsdb to reconstruct the database worked for that machine, as was suggested on the man page. Why on earth wouldn't it work for this other machine? Thanks in advance for any insight into this Sandro M. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
courrier maildir problem after portupgrade
BSD fans, I had qmail/courier imapd running fine. I ran portupgrade -ra and after everyting was upgraded and restarted, my email works fine. but my courier imapd cannot find my ~/Maildir even though it is there. I look in my logs and I see that I am getting authenticated with imapd, but all I get when I login via imap to the server is BYE [ALERT] Fatal error: No such file or directory (I see this via a sniffer trace) Ive searched google for quite a while, but cant seem to figure this one out. How do I specify the default location that courier looks for my inbox in a maildir format? Jason ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
courrier maildir problem after portupgrade (SOLVED!)
finally found the answer.. gotta have MAILDIRPATH=Maildir in /usr/local/etc/courier-imap/imapd Jason ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mrtg problem after portupgrade
Hi, I've problem in my box, Yesterday I was try to upgrade port and packages with this step : 1. Update port tree without X system. $ cvsup -g -L 2 port-file 2. Backup packages database. $ cd /var/db $ cp -rf pkg pkg.old 3. Check all dependecy application. $pkgdb -F 4. Process updating. $portupgrade -a -O -l /root/UpdateLog I was add -O because Amavis-Perl-11 require qmail-1.03_1 but in my system installed qmail-1.03. 5. Check again dependecy. $ pkgdb -F After that my mrtg graphic was broken, Look like full traffic but scale does't increase (Only 1 bps/s - 10 bps/s), I tried to reinstall mrtg but no change. TIA -- budsz To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
