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]
