Re: Portupgrade now supports pkgng [/usr/ports/UPDATING]
On 10/28/2012 03:00 AM, Bryan Drewery wrote: PKGNG is a replacement for the pkg_* tools that record package data in /var/db/pkg. It also allows for binary package upgrades. If you are wanting to use pkgng for binary packages, there's no need to use portupgrade anymore. Just 'pkg install name', 'pkg upgrade', etc. Understood. Thanks. For some reason I thought I could use the PKGNG tool set together with portupgrade the same way the pkg_* tools are used. Is there a straightforward way to go back to using the pkg_* tools in 9.1? Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Portupgrade now supports pkgng [/usr/ports/UPDATING]
On 10/28/2012 2:16 AM, Alexander Kapshuk wrote: On 10/28/2012 03:00 AM, Bryan Drewery wrote: PKGNG is a replacement for the pkg_* tools that record package data in /var/db/pkg. It also allows for binary package upgrades. If you are wanting to use pkgng for binary packages, there's no need to use portupgrade anymore. Just 'pkg install name', 'pkg upgrade', etc. Understood. Thanks. For some reason I thought I could use the PKGNG tool set together with portupgrade the same way the pkg_* tools are used. pkgng obsoletes portupgrade -P and pkg_add -r. Even if portupgrade -P did have pkg support, it would not work right because of different OPTIONS/dependencies, and the desync between your local ports tree and the remote package server's versions. You can use 'pkg install' to replace 'portupgrade -P' right now, and just not use -P if you want to use the port. But it will not go smoothly. Picking one of the other is best. (Ports or packages) If you're managing multiple servers with packages, I recommend checking out ports-mgmt/poudriere (http://fossil.etoilebsd.net/poudriere) as it will build the binary packages to create your own remote pkgng repository. poudriere+pkgng really do obsolete portupgrade all together. Is there a straightforward way to go back to using the pkg_* tools in 9.1? If you have not installed, upgraded, or deinstalled anything, yes. You can cp all of the package dirs from /var/db/pkg.bak into /var/db/pkg, and remove WITH_PKGNG from /etc/make.conf and then run pkgdb -fu again. Thanks. -- Regards, Bryan Drewery bdrewery@freenode/EFNet ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Portupgrade now supports pkgng [/usr/ports/UPDATING]
Le Sat, 27 Oct 2012 21:22:32 +0300, Alexander Kapshuk alexander.kaps...@gmail.com a écrit : Having done all of the above, I ran portupgrade to update all the pkgs that needed upgrading on my system, and got the message below: root@box0:/root/tmp # portupgrade -varRP --batch -L '%s_%s' USING PKGNG Packages are not yet suported. Use pkg(8) directly. That doesn't sound like portupgrade supports pkgng, or did I misread the message in the UPDATING file? pkg is able to make packages upgrade by itself. I think the good way to update with packages is pkg updgrade then portupgrade to build the ports without packages avalaible. Anyway I had many problems with portupgrade and pkg (basically It was not able to build its database because of inconsistency in ports dependencies), portmaster with pkgng patch looks better. Regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Portupgrade now supports pkgng [/usr/ports/UPDATING]
Got it. Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Portupgrade now supports pkgng [/usr/ports/UPDATING]
On 10/28/2012 04:27 PM, Patrick Lamaiziere wrote: pkg is able to make packages upgrade by itself. I think the good way to update with packages is pkg updgrade then portupgrade to build the ports without packages avalaible. Anyway I had many problems with portupgrade and pkg (basically It was not able to build its database because of inconsistency in ports dependencies), portmaster with pkgng patch looks better. Regards. Understood. Thanks. I'll look into that. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
re: Portupgrade now supports pkgng [/usr/ports/UPDATING]
Quick question about portupgrade's support for pkgng. The /usr/ports/UPDATING says: 20121015: AFFECTS: users of ports-mgmt/portupgrade AUTHOR: bdrew...@freebsd.org Portupgrade now supports pkgng. To use pkgng, enable it in your make.conf, and convert your databases. This is optional and not currently required. # make -C /usr/ports/ports-mgmt/pkg install clean # echo 'WITH_PKGNG=yes' /etc/make.conf # pkg2ng # pkgdb -fu Having done all of the above, I ran portupgrade to update all the pkgs that needed upgrading on my system, and got the message below: root@box0:/root/tmp # portupgrade -varRP --batch -L '%s_%s' USING PKGNG Packages are not yet suported. Use pkg(8) directly. That doesn't sound like portupgrade supports pkgng, or did I misread the message in the UPDATING file? box0=; uname -a FreeBSD box0.my.domain 9.1-RC2 FreeBSD 9.1-RC2 #0 r241133: Tue Oct 2 17:11:45 UTC 2012 r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 Thanks. Alexander Kapshuk. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Fwd: re: Portupgrade now supports pkgng [/usr/ports/UPDATING]
If my reading the code snippet below is right, portupgrade-2.4.10.2 does not support pkgng yet if pkgdb has been converted for use with pkgng using pkg2ng. /usr/ports/ports-mgmt/portupgrade/work/pkgtools-2.4.10.2/bin/portupgrade:561,565 # FIXME: pkgng if $use_packages $pkgdb.with_pkgng? STDERR.puts Packages are not yet suported. Use pkg(8) directly. return 0 end Original Message Subject:re: Portupgrade now supports pkgng [/usr/ports/UPDATING] Date: Sat, 27 Oct 2012 21:22:32 +0300 From: Alexander Kapshuk alexander.kaps...@gmail.com To: freebsd-questions@freebsd.org Quick question about portupgrade's support for pkgng. The /usr/ports/UPDATING says: 20121015: AFFECTS: users of ports-mgmt/portupgrade AUTHOR: bdrew...@freebsd.org Portupgrade now supports pkgng. To use pkgng, enable it in your make.conf, and convert your databases. This is optional and not currently required. # make -C /usr/ports/ports-mgmt/pkg install clean # echo 'WITH_PKGNG=yes' /etc/make.conf # pkg2ng # pkgdb -fu Having done all of the above, I ran portupgrade to update all the pkgs that needed upgrading on my system, and got the message below: root@box0:/root/tmp # portupgrade -varRP --batch -L '%s_%s' USING PKGNG Packages are not yet suported. Use pkg(8) directly. That doesn't sound like portupgrade supports pkgng, or did I misread the message in the UPDATING file? box0=; uname -a FreeBSD box0.my.domain 9.1-RC2 FreeBSD 9.1-RC2 #0 r241133: Tue Oct 2 17:11:45 UTC 2012 r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 Thanks. Alexander Kapshuk. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Portupgrade now supports pkgng [/usr/ports/UPDATING]
On 10/27/2012 1:22 PM, Alexander Kapshuk wrote: Quick question about portupgrade's support for pkgng. The /usr/ports/UPDATING says: 20121015: AFFECTS: users of ports-mgmt/portupgrade AUTHOR: bdrew...@freebsd.org Portupgrade now supports pkgng. To use pkgng, enable it in your make.conf, and convert your databases. This is optional and not currently required. # make -C /usr/ports/ports-mgmt/pkg install clean # echo 'WITH_PKGNG=yes' /etc/make.conf # pkg2ng # pkgdb -fu Having done all of the above, I ran portupgrade to update all the pkgs that needed upgrading on my system, and got the message below: root@box0:/root/tmp # portupgrade -varRP --batch -L '%s_%s' USING PKGNG Packages are not yet suported. Use pkg(8) directly. That doesn't sound like portupgrade supports pkgng, or did I misread the message in the UPDATING file? PKGNG is a replacement for the pkg_* tools that record package data in /var/db/pkg. It also allows for binary package upgrades. If you are wanting to use pkgng for binary packages, there's no need to use portupgrade anymore. Just 'pkg install name', 'pkg upgrade', etc. box0=; uname -a FreeBSD box0.my.domain 9.1-RC2 FreeBSD 9.1-RC2 #0 r241133: Tue Oct 2 17:11:45 UTC 2012 r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 Thanks. Alexander Kapshuk. -- Regards, Bryan Drewery bdrewery@freenode/EFNet ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade -- is there a way to only build and update ports that actually NEED it?
On 6/25/12 9:53 AM, Dan Mahoney, System Admin wrote: Hey there, I'm presently in the process of trying to do a portupgrade from rt-3.8.8 to 3.8.13. By all estimations, this is a minor bump. Already, I've encountered several annoyances due to ABI changes, such as the libtool2.4 fun. With normal portupgrade, this forces you to go fix the dependent port. Finally, I just applied -r, which should update all dependent packages, but it seems to upgrade them unconditionally. Ergo, I've since built a new version of perl, a new verion of python, rebuilt every perl module on the system, am presently rebuilding apache22, and I'm sure the system will turn around and require me to rebuild postgres real soon. You would think there's an option to portupgrade that says don't upgrade every single package I've got, but if somewhere in the dependency chain I need a newer version of a thing, then do it. Am I just missing it in the manpages, or does such a thing really not exist? -Dan We've been happily using portmanager for ages, it does just that :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade -- is there a way to only build and update ports that actually NEED it?
On 25/06/2012 08:53, Dan Mahoney, System Admin wrote: I'm presently in the process of trying to do a portupgrade from rt-3.8.8 to 3.8.13. By all estimations, this is a minor bump. Already, I've encountered several annoyances due to ABI changes, such as the libtool2.4 fun. With normal portupgrade, this forces you to go fix the dependent port. Finally, I just applied -r, which should update all dependent packages, but it seems to upgrade them unconditionally. Ergo, I've since built a new version of perl, a new verion of python, rebuilt every perl module on the system, am presently rebuilding apache22, and I'm sure the system will turn around and require me to rebuild postgres real soon. You would think there's an option to portupgrade that says don't upgrade every single package I've got, but if somewhere in the dependency chain I need a newer version of a thing, then do it. Am I just missing it in the manpages, or does such a thing really not exist? It has been many years since I used portupgrade with any regularity, and many of those neurones have been recycled. However, I do recall that: portupgrade -a should update all out-of-date ports on your system. portupgrade -r pkgname should update pkgname (if out of date) and all packages that depend on pkgname. portupgrade -R pkgname should update everything that pkgname depends on plus pkgname (if out of date). 'portupgrade -R' sounds like what you want. I believe that the meaning of the -r and -R flags in portupgrade is reversed from pkg_info(1) which is annoyingly inconsistent. Nowadays I usually use portmaster, where: portmaster pkgname works equivalently to 'portupgrade -R pkgname' except that portmaster /always/ reinstalls pkgname even if it is up to date. ie. the standard default action of portmaster is to do exactly what you want. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: portupgrade -- is there a way to only build and update ports that actually NEED it?
On 06/25/12 10:40, Andrea Venturoli wrote: On 06/25/12 09:53, Dan Mahoney, System Admin wrote: Hey there, I'm presently in the process of trying to do a portupgrade from rt-3.8.8 to 3.8.13. By all estimations, this is a minor bump. Already, I've encountered several annoyances due to ABI changes, such as the libtool2.4 fun. With normal portupgrade, this forces you to go fix the dependent port. Finally, I just applied -r, which should update all dependent packages, but it seems to upgrade them unconditionally. -r will upgrade all dependent ports *if* a newer version is available. -rf will upgrade all dependent ports unconditionally. You would think there's an option to portupgrade that says don't upgrade every single package I've got, but if somewhere in the dependency chain I need a newer version of a thing, then do it. I'm not sure what you mean. I guess you waned portupgrade -R rt, which will upgrade all ports rt ^ wanted is depending on. HTH. bye av. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade -- is there a way to only build and update ports that actually NEED it?
On 06/25/12 09:53, Dan Mahoney, System Admin wrote: Hey there, I'm presently in the process of trying to do a portupgrade from rt-3.8.8 to 3.8.13. By all estimations, this is a minor bump. Already, I've encountered several annoyances due to ABI changes, such as the libtool2.4 fun. With normal portupgrade, this forces you to go fix the dependent port. Finally, I just applied -r, which should update all dependent packages, but it seems to upgrade them unconditionally. -r will upgrade all dependent ports *if* a newer version is available. -rf will upgrade all dependent ports unconditionally. You would think there's an option to portupgrade that says don't upgrade every single package I've got, but if somewhere in the dependency chain I need a newer version of a thing, then do it. I'm not sure what you mean. I guess you waned portupgrade -R rt, which will upgrade all ports rt is depending on. HTH. bye av. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade -- is there a way to only build and update ports that actually NEED it?
You would think there's an option to portupgrade that says don't upgrade every single package I've got, but if somewhere in the dependency chain I need a newer version of a thing, then do it. The problem is that the versioning in the ports system doesn't distinguish between upgrades that present interface changes and upgrades that are just nits, new features, or minor bug fixes. Port makefiles can contain version dependency info, e.g., this port needs at least version N.M of package X, but few of them do. This has bitten me in the past with PHP and pcre. In fact, PHP5 won't work with old versions of pcre, but the PHP port maintainer refuses to put in version dependency info, because he thinks that every port should be up to date all the time. R's, John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade -- is there a way to only build and update ports that actually NEED it?
On 2012-06-25 11:47, John Levine wrote: You would think there's an option to portupgrade that says don't upgrade every single package I've got, but if somewhere in the dependency chain I need a newer version of a thing, then do it. The problem is that the versioning in the ports system doesn't distinguish between upgrades that present interface changes and upgrades that are just nits, new features, or minor bug fixes. Port makefiles can contain version dependency info, e.g., this port needs at least version N.M of package X, but few of them do. This has bitten me in the past with PHP and pcre. In fact, PHP5 won't work with old versions of pcre, but the PHP port maintainer refuses to put in version dependency info, because he thinks that every port should be up to date all the time. There's also the issue of things like Perl modules - most of them will just work, even with a newer version of perl, but a few have sections that need to be compiled against perl itself. So if you update the Perl port, you need to at least recompile those. (I'm simplifying a bit.) But there is no good way to mark in general which ports will 'just work' with an updated dependency, and which care what version of the dependency was installed when they were compiled. This is separate from versioned dependencies: Again to use Perl modules as an example, DBI for instance is will work with any version of perl since 5.8 or so - but if you change which version of perl you are using you'll need to recompile and reinstall. Rebuilding everything is a bit overkill, but it beats missing one that needed to be rebuilt. Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade -- is there a way to only build and update ports that actually NEED it?
On Mon, 25 Jun 2012 00:53:50 -0700 (PDT) Dan Mahoney, System Admin wrote: Hey there, I'm presently in the process of trying to do a portupgrade from rt-3.8.8 to 3.8.13. By all estimations, this is a minor bump. Already, I've encountered several annoyances due to ABI changes, such as the libtool2.4 fun. With normal portupgrade, this forces you to go fix the dependent port. I don't know what you mean by that Finally, I just applied -r, which should update all dependent packages, but it seems to upgrade them unconditionally. That's because the revisions numbers will have been bumped, it's nothing to do with portupgrade. Ergo, I've since built a new version of perl, a new verion of python, rebuilt every perl module on the system, am presently rebuilding apache22, and I'm sure the system will turn around and require me to rebuild postgres real soon. You would think there's an option to portupgrade that says don't upgrade every single package I've got, Firstly it doesn't. Secondly no one is forcing you to do this, if you want to go through the ports and work out which need an update and which don't then portupgrade will let you do that. but if somewhere in the dependency chain I need a newer version of a thing, then do it. Am I just missing it in the manpages, or does such a thing really not exist? -Dan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade ... doesn't
On 25 May 2012 12:10, Gary Aitken free...@dreamchaser.org wrote: Has to be something stupid: 347 /usr/ports#pkg_version -v | grep updating p5-XML-Twig-3.39 needs updating (port has 3.40) 348 /usr/ports#portupgrade -Rv P5-XML-Twig --- Session started at: Fri, 25 May 2012 10:03:54 -0600 [Exclude up-to-date packages done] ** None has been installed or upgraded. --- Session ended at: Fri, 25 May 2012 10:03:54 -0600 (consumed 00:00:00) 350 /usr/ports#pkg_info | grep p5-XML-Twig p5-XML-Twig-3.39 Process huge XML documents by chunks via a tree interface hints? Do pkg_version -vl pkg_version -vIl give different results? (note that's an uppercase i followed by a lowercase L in case your screen font makes it hard to tell) I believe portupgrade uses the INDEX-* files to determine, whereas pkg_version uses the /usr/ports/*/*/distinfo file (unless -I is provided). -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade -cfa status while executing
On Sunday 29 April 2012, dgmm wrote: When running portupgrade -cfa, is there any way to find out where it's up to and/ot what is still in the queue to be re-built? Oops. It was obvious really. ls /var/db/pkg -htU ...is good enough for my needs. -- Dave ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade 2.4.9.3
On Wed, 2011-08-24 at 11:20 +, o...@aloha.com wrote: I too am stuck in ruby-portupgrade swamp :-) After a fresh install of FreeBSD 8.2 I built potupgrade, then did a portsnap and a portupgrade -a, in preparation to install Gnome2. When it stopped I followed the instructions in UPDATING, but when I try to upgrade portupgrade it fails because it cannot find the first server listed and the only other one, ftp.freebsd.org, does not have pkgtools- 2.4.9.3.tar.bz2. I verified by manual ftp connection. Do I just wait for ftp.freebsd.org to sync, or does someone need to do something? Thanks for all that you do!! For the record, this was fixed by Thursday, by Friday I had Gnome Power Tools and Gnome Office up and running. -- Gary Dunn, Honolulu Open Slate Project http://openslate.org http://www.facebook.com/garydunn808 http://e9erust.blogspot.com Twitter @garydunn808 Sent from Slate001 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Portupgrade Package Question
On Sun, 10 Jul 2011 00:35:28 -0400 b. f. articulated: This is the tag that you would use on src collections to update your base system sources (usually in /usr/src) to 8-STABLE. You would use RELENG_8_2 for the 8.2-STABLE security branch, RELENG_8_2_RELEASE for 8.2-RELEASE, and so on. Reading through the archives, several years worth, it appears that this is one of the most frequently asked questions. Many users, both new (obviously) and some not so new get confused as to what is the proper tag to use for each branch; ie Stable Current, etc.Maybe there should be some way to make it easier to understand. For example: 8.2-RELEASE: original release of code sans any updates, etc. 8.2-STABLE: released version plus security updates 8.2-CURRENT: All updates, security otherwise to the original version ?-CURRENT: The absolute latest release of FreeBSD irregardless of what version it is. Anyway, it is just a suggestion. In any case I think it might be easier for some to comprehend. Anything that eliminates confusion is a plus. -- Jerry ✌ jerry+f...@seibercom.net Disclaimer: off-list followups get on-list replies or ignored. Do not CC this poster. Please do not ignore the Reply-To header. http://www.catb.org/~esr/faqs/smart-questions.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Portupgrade Package Question
On Sun, 10 Jul 2011 00:35:28 -0400 b. f. articulated: This is the tag that you would use on src collections to update your base system sources (usually in /usr/src) to 8-STABLE. You would use RELENG_8_2 for the 8.2-STABLE security branch, RELENG_8_2_RELEASE for 8.2-RELEASE, and so on. Reading through the archives, several years worth, it appears that this is one of the most frequently asked questions. Many users, both new (obviously) and some not so new get confused as to what is the proper tag to use for each branch; ie Stable Current, etc.Maybe there should be some way to make it easier to understand. For example: 8.2-RELEASE: original release of code sans any updates, etc. 8.2-STABLE: released version plus security updates 8.2-CURRENT: All updates, security otherwise to the original version ?-CURRENT: The absolute latest release of FreeBSD irregardless of what version it is. Anyway, it is just a suggestion. In any case I think it might be easier for some to comprehend. Anything that eliminates confusion is a plus. I have 34 years experience as a Data Systems technician, system admin, developer, and tech writer, yet I till won't claim I know everything, so please don't flame me. Constructive, polite criticism is welcome. I began my career before Unix or MicroSucks even existed. It is a misnomer to attach a release number to current or stable. CURRENT is called HEAD in source code control vernacular. CURRENT's number is transient. It is often incorrectly referred to as 9. Please refrain from such usage. It is technically incorrect and confuses users who have no knowledge of source code control. Same goes for STABLE. In my opinion, the real confusion is in ascertaining what you SHOULD be using. If you want to run FreeBSD, KDE, gnome, etc., as a PRODUCTION machine, yo should NOT be using CURRENT or STABLE. You should be installing a RELEASE on a TEST machine, verify that ALL your user applications have no showstopper anomales, and DEPLOY the release AFTER testing has given you a great dela of confidence in the software. You should JUMP from a release to the next release, using the testing and deployment mentioned. You WILL get security updates if you track a release, such as 8.2. But again, don't just update your sources and deploy. TEST it on a test machine, before exposing your end users to it. This is referred to as PROFESSIONALISM. The ONLY people that should be tracking STABLE or CURRENT are the people who DON'T need their hand held for system administration. If you violate this protocol, you will be taking developers time away from development to TRAIN you in system admin. PLEASE don't. Hope this helps and if it offends you, please take the time to think about it before you flame me. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Portupgrade Package Question
On 10/07/2011 14:02, Jerry wrote: On Sun, 10 Jul 2011 00:35:28 -0400 b. f. articulated: This is the tag that you would use on src collections to update your base system sources (usually in /usr/src) to 8-STABLE. You would use RELENG_8_2 for the 8.2-STABLE security branch, RELENG_8_2_RELEASE for 8.2-RELEASE, and so on. Reading through the archives, several years worth, it appears that this is one of the most frequently asked questions. Many users, both new (obviously) and some not so new get confused as to what is the proper tag to use for each branch; ie Stable Current, etc.Maybe there should be some way to make it easier to understand. For example: I was one of them until I discovered that googling FreeBSD tags leads straight to http://www.freebsd.org/doc/handbook/cvs-tags.html Eg RELENG_8 The line of development for FreeBSD-8.X, also known as FreeBSD 8-STABLE RELENG_8_2 The release branch for FreeBSD-8.2, used only for security advisories and other critical fixes. ... RELENG_8_2_0_RELEASE FreeBSD 8.2 Release Chris 8.2-RELEASE: original release of code sans any updates, etc. 8.2-STABLE: released version plus security updates 8.2-CURRENT: All updates, security otherwise to the original version ?-CURRENT: The absolute latest release of FreeBSD irregardless of what version it is. Anyway, it is just a suggestion. In any case I think it might be easier for some to comprehend. Anything that eliminates confusion is a plus. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Portupgrade Package Question
On 7/9/2011 1:14 PM, Thomas D. Dean wrote: As root, I attempted to use portupgrade -PPRv m4 which attempted to access ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8.2-release/All/m4-1.4.16,1.tbz but failed - File unavailable (e.g. file not found, no access) I changed etc/pkgtools.conf OS_PKGBRANCH=8-STABLE and portupgrade -PPRv m4 which attempted to access ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/All/m4-1.4.16,1.tbz failed with the same message. I can ftp either file. I get the same error with any out-of-date port. What am I doing wrong? Have you made sure you updated ports? 'portsnap fetch extract' should be sufficient. -- Chris Brennan -- A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting frowned upon? http://xkcd.com/84/ | http://xkcd.com/149/ | http://xkcd.com/549/ GPG: D5B20C0C (6741 8EE4 6C7D 11FB 8DA8 9E4A EECD 9A84 D5B2 0C0C) signature.asc Description: OpenPGP digital signature
Re: Portupgrade Package Question
On Sat, 2011-07-09 at 14:15 -0400, Chris Brennan wrote: On 7/9/2011 1:14 PM, Thomas D. Dean wrote: As root, I attempted to use portupgrade -PPRv m4 which attempted to access ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8.2-release/All/m4-1.4.16,1.tbz but failed - File unavailable (e.g. file not found, no access) I changed etc/pkgtools.conf OS_PKGBRANCH=8-STABLE and portupgrade -PPRv m4 which attempted to access ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/All/m4-1.4.16,1.tbz failed with the same message. I can ftp either file. I get the same error with any out-of-date port. What am I doing wrong? Have you made sure you updated ports? 'portsnap fetch extract' should be sufficient. Sorry, I did not reply to the list. Yes, I did update ports. /usr/bin/fetch -v 'ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-8-STABLE/All/m4-1.4.16,1.tbz' looking up ftp.FreeBSD.org connecting to ftp.FreeBSD.org:21 fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-8-STABLE/All/m4-1.4.16,1.tbz: File unavailable (e.g., file not found, no access) tomdean ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Portupgrade Package Question
On Sat, 09 Jul 2011 11:33:00 -0700, Thomas D. Dean wrote: /usr/bin/fetch -v 'ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-8-STABLE/All/m4-1.4.16,1.tbz' looking up ftp.FreeBSD.org connecting to ftp.FreeBSD.org:21 fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-8-STABLE/All/m4-1.4.16,1.tbz: File unavailable (e.g., file not found, no access) It's quite simple if you investigate the content of the FTP server. :-) Doesn't work: ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-STABLE/All/m4-1.4.16,1.tbz Works: ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/All/m4-1.4.16,1.tbz Just change packages-8-STABLE to packages-8-stable and try again. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Portupgrade Package Question
On Sat, 2011-07-09 at 20:47 +0200, Polytropon wrote: On Sat, 09 Jul 2011 11:33:00 -0700, Thomas D. Dean wrote: /usr/bin/fetch -v 'ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-8-STABLE/All/m4-1.4.16,1.tbz' looking up ftp.FreeBSD.org connecting to ftp.FreeBSD.org:21 fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-8-STABLE/All/m4-1.4.16,1.tbz: File unavailable (e.g., file not found, no access) It's quite simple if you investigate the content of the FTP server. :-) Doesn't work: ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-STABLE/All/m4-1.4.16,1.tbz Works: ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/All/m4-1.4.16,1.tbz Just change packages-8-STABLE to packages-8-stable and try again. Yes. My error. I did not completely remove 8.2-RELEASE when I edited pkgtools.conf the 2nd time. I introduced this error when I typed the fetch command. Sorry. My original problem still exists: portupgrade fails with any out-of-date package. I should have sent the console output the first time... I restored pkgtools.conf to the original version, from the initial installation. Here is the output of the portupgrade attempt: uname -a FreeBSD toshiba.tddhome 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Fri Feb 18 02:24:46 UTC 2011 r...@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 portupgrade --version portupgrade 2.4.8 portupgrade -PPv m4 --- Session started at: Sat, 09 Jul 2011 11:55:55 -0700 --- Checking for the latest package of 'devel/m4' --- Found a package of 'devel/m4': /usr/ports/packages/All/m4-1.4.15,1.tbz (m4-1.4.15,1) --- Fetching the package(s) for 'm4-1.4.16,1' (devel/m4) --- Fetching m4-1.4.16,1 ++ Will try the following sites in the order named: ftp://ftp.FreeBSD.org//pub/FreeBSD/ports/i386/packages-8.2-release/ --- Invoking a command: /usr/bin/fetch -o '/var/tmp/portupgrademXjhTdVX/m4-1.4.16,1.tbz' 'ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-8.2-release/All/m4-1.4.16,1.tbz' fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-8.2-release/All/m4-1.4.16,1.tbz: 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-8.2-release/All/m4-1.4.16,1.tbz --- Invoking a command: /usr/bin/fetch -o '/var/tmp/portupgrademXjhTdVX/m4-1.4.16,1.txz' 'ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-8.2-release/All/m4-1.4.16,1.txz' fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-8.2-release/All/m4-1.4.16,1.txz: 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-8.2-release/All/m4-1.4.16,1.txz --- Invoking a command: /usr/bin/fetch -o '/var/tmp/portupgrademXjhTdVX/m4-1.4.16,1.tgz' 'ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-8.2-release/All/m4-1.4.16,1.tgz' fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-8.2-release/All/m4-1.4.16,1.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-8.2-release/All/m4-1.4.16,1.tgz ** Failed to fetch m4-1.4.16,1 --- Listing the results (+:done / -:ignored / *:skipped / !:failed) ! m4-1.4.16,1 (fetch error) --- Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed --- Fetching the latest package(s) for 'm4' (devel/m4) --- Fetching m4 ++ Will try the following sites in the order named: ftp://ftp.FreeBSD.org//pub/FreeBSD/ports/i386/packages-8.2-release/ --- Invoking a command: /usr/bin/fetch -o '/var/tmp/portupgradeyQuqTSRB/m4.tbz' 'ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-8.2-release/Latest/m4.tbz' /var/tmp/portupgradeyQuqTSRB/m4.tbz 100% of 185 kB 144 kBps --- Downloaded as m4.tbz --- Identifying the package /var/tmp/portupgradeyQuqTSRB/m4.tbz --- Saved as /usr/ports/packages/All/m4-1.4.15,1.tbz --- Listing the results (+:done / -:ignored / *:skipped / !:failed) + m4@ --- Packages processed: 1 done, 0 ignored, 0 skipped and 0 failed --- Found a package of 'devel/m4': /usr/ports/packages/All/m4-1.4.15,1.tbz (m4-1.4.15,1) --- Located a package version 1.4.15,1 (/usr/ports/packages/All/m4-1.4.15,1.tbz) --- ** Upgrade tasks 1: 0 done, 0 ignored, 0 skipped and 1 failed --- Listing the results (+:done / -:ignored / *:skipped / !:failed) ! devel/m4 (m4-1.4.15,1)(package not found) --- Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed --- Session ended at: Sat, 09 Jul 2011 11:56:29 -0700 (consumed 00:00:33) tomdean ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Portupgrade Package Question
On Sat, 2011-07-09 at 12:05 -0700, Thomas D. Dean wrote: Sorry to answer my own post. The packages that are out-of-date on the system I was updating are in relationship to 8.2-release. A couple days ago, I cvsup'd the port tree with *default release-cvs tag=. ports-all Today, portsnap fetch extract ... portsnap fetch update ... portupgrade -PPRva Does the portsnap update the port tree relative to 8.2-release or 8-stable? Or, did cvsup get ports from 8-stable? Looks like 8-stable. 8-stablem4-1.4.16,1.tbz 8.2-release m4-1.4.15,1.tbz Anyway, I can get there from here Thanks. tomdean ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Portupgrade Package Question
On Sat, 09 Jul 2011 12:32:12 -0700, Thomas D. Dean wrote: On Sat, 2011-07-09 at 12:05 -0700, Thomas D. Dean wrote: Sorry to answer my own post. The packages that are out-of-date on the system I was updating are in relationship to 8.2-release. A couple days ago, I cvsup'd the port tree with *default release-cvs tag=. ports-all Today, portsnap fetch extract ... portsnap fetch update ... portupgrade -PPRva Does the portsnap update the port tree relative to 8.2-release or 8-stable? Or, did cvsup get ports from 8-stable? Looks like 8-stable. 8-stablem4-1.4.16,1.tbz 8.2-release m4-1.4.15,1.tbz Anyway, I can get there from here If I understood everything correctly, CVS (csup) and portsnap do both follow the one tree which gets frequently updated, and by the tag specified above you'll always get the current version of the tree. Getting older versions (e. g. the RELEASE tree) involves specifying a different tag, or loading it from the installation media directly. The difference is that changes in the ports tree are reflected much faster in the CVS method than in the portsnap approach, which may lag a bit. However, portsnap seems to work faster and to perform better than CVS. It's also worth mentioning that it seems to fit better to the building cycle of the -stable ports to become precompiled packages (that you request using the -PP parameter, similar to the use of pkg_add -r in case of installation instead of update). But if you require the most recent ports tree, using CVS seems to be the better method. As you're updating binary, but with using the ports tree (portupgrade relies on that, pkg_add for example doesn't), you should make sure to always have the current version if you follow the stable OS branch. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Portupgrade Package Question
On Sat, 2011-07-09 at 21:45 +0200, Polytropon wrote: If I understood everything correctly, CVS (csup) and portsnap do both follow the one tree which gets frequently updated, and by the tag specified above you'll always get the current version of the tree. Getting older versions (e. g. the RELEASE tree) involves specifying a different tag, or loading it from the installation media directly. The difference is that changes in the ports tree are reflected much faster in the CVS method than in the portsnap approach, which may lag a bit. However, portsnap seems to work faster and to perform better than CVS. It's also worth mentioning that it seems to fit better to the building cycle of the -stable ports to become precompiled packages (that you request using the -PP parameter, similar to the use of pkg_add -r in case of installation instead of update). But if you require the most recent ports tree, using CVS seems to be the better method. As you're updating binary, but with using the ports tree (portupgrade relies on that, pkg_add for example doesn't), you should make sure to always have the current version if you follow the stable OS branch. I have always built ports from the source. I decided to try binary ports for things I have not modified. I cannot seem to get portupgrade to use the definitions I set in etc/pkgtools.conf. For the most recent try, I have ... # OS_PATCHLEVEL:-p8 # OS_PLATFORM:i386 amd64 # OS_PKGBRANCH: 7-current 6.1-release OS_RELEASE=8-STABLE OS_BRANCH=STABLE OS_PKGBRANCH=8-stable # Useful predefined functions: # # localbase() #Returns LOCALBASE. ... But, portupgrade still tries to fetch from 8.2-release. If I want to use binary ports it looks like I need to zap the ports tree and recreate it with portsnap. tomdean ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Portupgrade Package Question
Thomas D. Dean wrote:
...
For the most recent try, I have
...
# OS_PATCHLEVEL:-p8
# OS_PLATFORM:i386 amd64
# OS_PKGBRANCH: 7-current 6.1-release
OS_RELEASE=8-STABLE
OS_BRANCH=STABLE
OS_PKGBRANCH=8-stable
The comments above were not intended as an invitation to try to define
these constants here, but merely describe typical values that the
constants may have. The constants are computed from parsing your
'uname -rm' output in $LOCALBASE/$RUBY_SITELIBDIR/pkgtools.rb (usually
/usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb), so you cannot set them
in pkgtools.conf. They were only mentioned so that users would know
that they were available for defining other procedures and variables
(for an example, see below).
# Useful predefined functions:
#
# localbase()
#Returns LOCALBASE.
...
But, portupgrade still tries to fetch from 8.2-release.
If you are running 8.2-RELEASE, and yet wish to obtain 8-stable
packages (which are actually built on recent versions of 8.1-STABLE,
with recent versions of the ports tree), then set PKG_SITES
appropriately in pkgtools.conf. In this case, I think (untested) that
you could substitute
sprintf('%s/pub/FreeBSD/ports/%s/packages-%s-stable/',
ENV['PACKAGEROOT'] || 'ftp://ftp.FreeBSD.org', OS_PLATFORM, OS_MAJOR)
for the default
pkg_site_mirror(root)
in PKG_SITES. (It might be better to upgrade your base system to
8-STABLE, in which case the defaults will be correct without any need
for these changes, and other problems will also be fixed).
If I want to use binary ports it looks like I need to zap the ports tree
and recreate it with portsnap.
This should not be necessary. You should be able to use any method to
update the tree (anonymous cvs, csup/cvsup, portsnap, http/ftp, rsync,
ctm, etc.). Of course, if your tree and index file do not correspond
to the version of the binary packages that you want to use, you will
occasionally trip over problems that will require intervention. (Note
that in the section of the csup file that you reproduced in an earlier
message, 'release-cvs' should be 'release=cvs'.)
PKG_SITES will only be used by the ports-mgmt/portupgrade scripts; if
you want to use pkg_add(1) manually, and obtain the 8-stable packages,
then you should define PACKAGESITE in your environment, or provide a
full URL. The ports-mgmt/portupgrade scripts also respect
PACKAGESITE, which will override PACKAGEROOT and PKG_SITES in those
scripts.
b.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Portupgrade Package Question
On Sat, 2011-07-09 at 19:54 -0400, b. f. wrote: occasionally trip over problems that will require intervention. (Note that in the section of the csup file that you reproduced in an earlier message, 'release-cvs' should be 'release=cvs'.) The '-' was a typo on my part. The machine I used for email is not the machine I am updating. I am updating that machine, now. The supfile contains *default release=cvs tag=RELENG_8 This should track 8-stable. Correct? After the build finishes, portupgrade should fetch from 8-stable. A slow, remote machine... tomdean ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Portupgrade Package Question
On 7/9/11, Thomas D. Dean tomd...@speakeasy.org wrote: On Sat, 2011-07-09 at 19:54 -0400, b. f. wrote: occasionally trip over problems that will require intervention. (Note that in the section of the csup file that you reproduced in an earlier message, 'release-cvs' should be 'release=cvs'.) The '-' was a typo on my part. The machine I used for email is not the machine I am updating. I am updating that machine, now. The supfile contains *default release=cvs tag=RELENG_8 This should track 8-stable. Correct? This is the tag that you would use on src collections to update your base system sources (usually in /usr/src) to 8-STABLE. You would use RELENG_8_2 for the 8.2-STABLE security branch, RELENG_8_2_RELEASE for 8.2-RELEASE, and so on. But src tags are not the same as ports tags. That is why they have separate example supfiles for the base system sources, and for ports. And that is also why they have the prominent warning in the base system example supfiles: ### # # DANGER! WARNING! LOOK OUT! VORSICHT! # # If you add any of the ports or doc collections to this file, be sure to # specify them with a tag value set to ., like this: # # ports-all tag=. # doc-all tag=. # # If you leave out the tag=. portion, CVSup will delete all of # the files in your ports or doc tree. That is because the ports and doc # collections do not use the same tags as the main part of the FreeBSD # source tree. # ### As far as I know, the ports collection has no tags for any stable branches, only tags made at the time of releases. So for ports, if you are running 8.2-RELEASE, you have three choices: (1) use RELEASE_8_2_0 if you want to stick with a snapshot of the ports tree taken at the time of the release, or (2) use . if you want up-to-date ports, or (3) choose a specific snapshot of ports via date= instead of tag= (for details, see, for example, the csup(1) manpage.) After the build finishes, portupgrade should fetch from 8-stable. I'm not sure what you mean here. As I wrote before, you need to make some additional changes to ensure that portupgrade uses 8-stable packages if you have an 8.2-RELEASE base system. Just having a up-to-date ports tree and index isn't sufficient. However, if you replace your 8.2-RELEASE base system with a newer 8.2-STABLE or 8-STABLE base system, then portupgrade should fetch the 8-stable packages by default, without any additional changes. You could cheat, and neither upgrade your base system nor make the changes I mentioned in my last message, but instead fool portupgrade into thinking that you have a newer base system, by setting UNAME_R to something like 8.2-STABLE in your environment when you call portupgrade, but you are bound to run into problems eventually by lying in that way. b. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Portupgrade Package Question
On 7/10/11, b. f. bf1...@googlemail.com wrote: On 7/9/11, Thomas D. Dean tomd...@speakeasy.org wrote: On Sat, 2011-07-09 at 19:54 -0400, b. f. wrote: You could cheat, and neither upgrade your base system nor make the changes I mentioned in my last message, but instead fool portupgrade into thinking that you have a newer base system, by setting UNAME_R to Sorry, that should be UNAME_r, with a lower-case r, above. But, as I wrote, using that workaround is probably not a good idea. something like 8.2-STABLE in your environment when you call portupgrade, but you are bound to run into problems eventually by lying in that way. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Portupgrade and Updating the portsdb
2011/2/11 ill...@gmail.com ill...@gmail.com: On 10 February 2011 08:33, c0re nr1c...@gmail.com wrote: Hello all! I've got set of servers that uses NFS mounted /usr/ports. When I use portupgrade samba on 1st server it says [/usr/ports/INDEX-7.db: unexpected file type or format -- Invalid argument] [Updating the portsdb format:bdb_btree in /usr/ports ... - 22601 port entries found error] Remove and try again. [Updating the portsdb format:dbm_hash in /usr/ports ... - 22601 port entries found . . done] Okay. It took 10-15 mins to rebuild. Then I say portupgrade samba on 2nd server it says again [/usr/ports/INDEX-7.db: unexpected file type or format -- Invalid argument] [Updating the portsdb format:bdb_btree in /usr/ports ... - 22601 port entries found error] Remove and try again. and rebuild portsdb. Why is it so? Ports are updated via portsnap fetch update. /etc/portsnap.conf has INDEX INDEX-5 DESCRIBE.5 INDEX INDEX-6 DESCRIBE.6 INDEX INDEX-7 DESCRIBE.7 INDEX INDEX-8 DESCRIBE.8 So while portupgrade rebuilds portsdb it's not possible use portupgrade on 2nd server because later build process will fail on 1st or second server. What can I do with it? Why portupgrade always thinks that [/usr/ports/INDEX-7.db: unexpected file type or format -- Invalid argument]? The INDEX-n.db is a locally generated portupgrade thing. Edit your /usr/local/etc/pkgtools.conf for each machine to include a line such as: ENV['PORTS_INDEX'] ||= ENV['PORTSDIR'] + '/INDEX.local' Only instead of '/INDEX.local' use '/INDEX.your_hostname_here'. You might also look at changing the part ENV['PORTSDIR'] to something local (speed, etc), like adding a line up from that: ENV['LOCALINDICES'] ||= '/var/db' then ENV['PORTS_INDEX'] ||= ENV['LOCALINDICES'] + '/INDEX.thy_hostname_here' Also, if you have local space, settin' WRKDIRPREFIX= in /etc/make.conf will speed things up allow multiple machines to build at the same time. HTH -- -- It's time to make upgrade of some packages. I configured ENV['PORTS_INDEX'] = '/var/db/INDEX' ENV['PORTS_DBDIR'] = ENV['PKG_DBDIR'] in /usr/local/etc/pkgtools.conf, assuming that PKG_DBDIR is /var/db/pkg and portupgrade sudo results Fetching the ports index ... fetch: /usr/ports/INDEX-7.bz2: open(): Read-only file system *** Error code 1 Stop in /usr/ports. failed to fetch INDEX! Updating the ports index ... Generating INDEX.tmp - please wait..cannot create /usr/ports/INDEX.tmp.tmp: Read-only file system Warning: Duplicate INDEX entry: py25-bsddb-2.5.5_2 *** Error code 2 Stop in /usr/ports. *** Error code 1 Stop in /usr/ports. failed to generate INDEX! index generation error /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:493:in `open_db': database file error (PortsDB::DBError) from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:661:in `port' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:849:in `all_depends_list' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:843:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:835:in `each' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:835:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:857:in `sort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:861:in `sort_build!' from /usr/local/sbin/portupgrade:792:in `main' from /usr/local/lib/ruby/1.8/optparse.rb:791:in `initialize' from /usr/local/sbin/portupgrade:229:in `new' from /usr/local/sbin/portupgrade:229:in `main' from /usr/local/sbin/portupgrade:2213 Any workaround with Fetching the ports index? There exists /usr/ports/INDEX-7, but portupgrade tryes to fetch it again and failes, cose /usr/ports is read-only mounted. Changing ENV['PORTSDIR'] ||= '/var/ports' make no sense because it's obvious that PORTSDIR should look at ports base (/usr/ports) # portupgrade sudo ** Port directory not found: security/sudo ** Listing the failed packages (-:ignored / *:skipped / !:failed) - security/sudo (port directory error) Still looking for a solution about using portupgrade with read-only mounted /usr/ports. And yes, i'm using WRKDIRPREFIX in /etc/make.conf. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Portupgrade and Updating the portsdb
On 10 February 2011 08:33, c0re nr1c...@gmail.com wrote: Hello all! I've got set of servers that uses NFS mounted /usr/ports. When I use portupgrade samba on 1st server it says [/usr/ports/INDEX-7.db: unexpected file type or format -- Invalid argument] [Updating the portsdb format:bdb_btree in /usr/ports ... - 22601 port entries found error] Remove and try again. [Updating the portsdb format:dbm_hash in /usr/ports ... - 22601 port entries found . . done] Okay. It took 10-15 mins to rebuild. Then I say portupgrade samba on 2nd server it says again [/usr/ports/INDEX-7.db: unexpected file type or format -- Invalid argument] [Updating the portsdb format:bdb_btree in /usr/ports ... - 22601 port entries found error] Remove and try again. and rebuild portsdb. Why is it so? Ports are updated via portsnap fetch update. /etc/portsnap.conf has INDEX INDEX-5 DESCRIBE.5 INDEX INDEX-6 DESCRIBE.6 INDEX INDEX-7 DESCRIBE.7 INDEX INDEX-8 DESCRIBE.8 So while portupgrade rebuilds portsdb it's not possible use portupgrade on 2nd server because later build process will fail on 1st or second server. What can I do with it? Why portupgrade always thinks that [/usr/ports/INDEX-7.db: unexpected file type or format -- Invalid argument]? The INDEX-n.db is a locally generated portupgrade thing. Edit your /usr/local/etc/pkgtools.conf for each machine to include a line such as: ENV['PORTS_INDEX'] ||= ENV['PORTSDIR'] + '/INDEX.local' Only instead of '/INDEX.local' use '/INDEX.your_hostname_here'. You might also look at changing the part ENV['PORTSDIR'] to something local (speed, etc), like adding a line up from that: ENV['LOCALINDICES'] ||= '/var/db' then ENV['PORTS_INDEX'] ||= ENV['LOCALINDICES'] + '/INDEX.thy_hostname_here' Also, if you have local space, settin' WRKDIRPREFIX= in /etc/make.conf will speed things up allow multiple machines to build at the same time. HTH -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Portupgrade and Updating the portsdb
On Thu, Feb 10, 2011 at 04:33:17PM +0300, c0re wrote: Hello all! I've got set of servers that uses NFS mounted /usr/ports. When I use portupgrade samba on 1st server it says [/usr/ports/INDEX-7.db: unexpected file type or format -- Invalid argument] [Updating the portsdb format:bdb_btree in /usr/ports ... - 22601 port entries found error] Remove and try again. [Updating the portsdb format:dbm_hash in /usr/ports ... - 22601 port entries found .1000.2000.3000.4000.5000.6000.7000.8000.9000.1.11000.12000.13000.14000.15000.16000.17000.18000.19000.2.21000.22000.. . done] Okay. It took 10-15 mins to rebuild. Then I say portupgrade samba on 2nd server it says again [/usr/ports/INDEX-7.db: unexpected file type or format -- Invalid argument] [Updating the portsdb format:bdb_btree in /usr/ports ... - 22601 port entries found error] Remove and try again. and rebuild portsdb. Why is it so? Ports are updated via portsnap fetch update. /etc/portsnap.conf has INDEX INDEX-5 DESCRIBE.5 INDEX INDEX-6 DESCRIBE.6 INDEX INDEX-7 DESCRIBE.7 INDEX INDEX-8 DESCRIBE.8 So while portupgrade rebuilds portsdb it's not possible use portupgrade on 2nd server because later build process will fail on 1st or second server. What can I do with it? Why portupgrade always thinks that [/usr/ports/INDEX-7.db: unexpected file type or format -- Invalid argument]? Are you using the same versions of ruby, portupgrade, ruby-bdb and bdb on both machines? Dan -- Daniel Bye _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ pgp3ptuxyGw1i.pgp Description: PGP signature
Re: Portupgrade and Updating the portsdb
Try to move these files out of the way (all INDEX files and pkgdb.db) /usr/ports/INDEX-* /var/db/pkg/pkgdb.db and run (it will take a while) portsdb -Uu as another option you can remove the files above and reinstall ruby and ruby-bdb on those servers. Are you running on version 7 or 8 ? are you mounting the NFS rw ? On Thu, Feb 10, 2011 at 11:33 AM, c0re nr1c...@gmail.com wrote: Hello all! I've got set of servers that uses NFS mounted /usr/ports. When I use portupgrade samba on 1st server it says [/usr/ports/INDEX-7.db: unexpected file type or format -- Invalid argument] [Updating the portsdb format:bdb_btree in /usr/ports ... - 22601 port entries found error] Remove and try again. [Updating the portsdb format:dbm_hash in /usr/ports ... - 22601 port entries found .1000.2000.3000.4000.5000.6000.7000.8000.9000.1.11000.12000.13000.14000.15000.16000.17000.18000.19000.2.21000.22000.. . done] Okay. It took 10-15 mins to rebuild. Then I say portupgrade samba on 2nd server it says again [/usr/ports/INDEX-7.db: unexpected file type or format -- Invalid argument] [Updating the portsdb format:bdb_btree in /usr/ports ... - 22601 port entries found error] Remove and try again. and rebuild portsdb. Why is it so? Ports are updated via portsnap fetch update. /etc/portsnap.conf has INDEX INDEX-5 DESCRIBE.5 INDEX INDEX-6 DESCRIBE.6 INDEX INDEX-7 DESCRIBE.7 INDEX INDEX-8 DESCRIBE.8 So while portupgrade rebuilds portsdb it's not possible use portupgrade on 2nd server because later build process will fail on 1st or second server. What can I do with it? Why portupgrade always thinks that [/usr/ports/INDEX-7.db: unexpected file type or format -- Invalid argument]? Thanks!!! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade over http only
On Fri, Jan 14, 2011 at 3:07 PM, Michael mlmichae...@gmail.com wrote: Hello, Is it possible to force portupgrade to use only http protocol where possible and skip the ftp servers? It's because currently I'm using very restrictive public access point where they block everything other than port 80 and I don't have a chance to set up a tunnel or proxy anywhere outside that network. When I try to: portupgrade -arRF it looks like it prefers ftp. Eventually it falls back to http but it takes ages before it tries all ftp servers. What to do? You could set FTP_TIMEOUT to an absurdly low value. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade over http only
On 14/01/2011 21:32, Adam Vande More wrote: On Fri, Jan 14, 2011 at 3:07 PM, Michael mlmichae...@gmail.com wrote: Hello, Is it possible to force portupgrade to use only http protocol where possible and skip the ftp servers? It's because currently I'm using very restrictive public access point where they block everything other than port 80 and I don't have a chance to set up a tunnel or proxy anywhere outside that network. When I try to: portupgrade -arRF it looks like it prefers ftp. Eventually it falls back to http but it takes ages before it tries all ftp servers. What to do? You could set FTP_TIMEOUT to an absurdly low value. MASTER_SORT = http in /etc/make.conf -- should make the ports try http sites first. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: portupgrade over http only
On Fri, 14 Jan 2011 21:45:22 + Matthew Seaman m.sea...@infracaninophile.co.uk wrote: MASTER_SORT = http I used to use MASTER_SORT_REGEX = ^http for this when a former ISP traffic shaped ftp If you set MASTER_SORT = http, then you get ://[^/]*http/ in MASTER_SORT_REGEX, so it looks like MASTER_SORT is intended just to match hostnames/domains. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Portupgrade status
On Tue, 04 Jan 2011 11:04:03 -0500, Warren Block wbl...@wonkity.com wrote: On Tue, 4 Jan 2011, Matthew Seaman wrote: On 04/01/2011 00:51, ill...@gmail.com wrote: No, the -R flag in portmaster tells it to not rebuild ports taht have already been built on this run (I believe from reading man portmaster). The -R flag in portupgrade rebuilds the ports on which the named port depends -R --upward-recursive Act on all those packages required by the given packages as well. (When specified with -F, fetch recursively, including the brand new, uninstalled ports that an upgraded port requires) I don't see any equivalent functionality for portmaster, sadly. This is actually portmaster's default behaviour. So: portupgrade -R foo/bar is equivalent to portmaster foo/bar portupgrade -fRr foo/bar is equivalent to portmaster -fr foo/bar I'm not seeing where portmaster has the portupgrade -R functionality (rebuild this port and those it depends on). portmaster(8) says The focus of this tool is to keep the dependency tracking information for your ports up to date. This allows you to safely update a specific port without having to update all of the ports above it. That would make the default action equivalent to portupgrade's -r option (rebuild this port and all those that depend on it). What have I missed? I agree the quoted passage might admit of more than one interpretation, but here is what I think it's saying: Portmaster will automagically update the dependencies for the port you select (= portupgrade -R). Thus there is no need to update the ports that depend on the one you have selected (= portupgrade -r), since all downstream dependencies will be taken care of by default whenever you run portmaster against any of these upstream ports. Jud -- I'd take the awe of understanding over the awe of ignorance any day. - Douglas Adams ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Portupgrade status
On 04/01/2011 00:51, ill...@gmail.com wrote: No, the -R flag in portmaster tells it to not rebuild ports taht have already been built on this run (I believe from reading man portmaster). The -R flag in portupgrade rebuilds the ports on which the named port depends -R --upward-recursive Act on all those packages required by the given packages as well. (When specified with -F, fetch recursively, including the brand new, uninstalled ports that an upgraded port requires) I don't see any equivalent functionality for portmaster, sadly. This is actually portmaster's default behaviour. So: portupgrade -R foo/bar is equivalent to portmaster foo/bar portupgrade -fRr foo/bar is equivalent to portmaster -fr foo/bar There isn't actually a way to do the equivalent of portupgrade foo/bar -- that is, only update the specifically named port, without updating any dependencies as well. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: Portupgrade status
On Tue, 4 Jan 2011, Matthew Seaman wrote: On 04/01/2011 00:51, ill...@gmail.com wrote: No, the -R flag in portmaster tells it to not rebuild ports taht have already been built on this run (I believe from reading man portmaster). The -R flag in portupgrade rebuilds the ports on which the named port depends -R --upward-recursive Act on all those packages required by the given packages as well. (When specified with -F, fetch recursively, including the brand new, uninstalled ports that an upgraded port requires) I don't see any equivalent functionality for portmaster, sadly. This is actually portmaster's default behaviour. So: portupgrade -R foo/bar is equivalent to portmaster foo/bar portupgrade -fRr foo/bar is equivalent to portmaster -fr foo/bar I'm not seeing where portmaster has the portupgrade -R functionality (rebuild this port and those it depends on). portmaster(8) says The focus of this tool is to keep the dependency tracking information for your ports up to date. This allows you to safely update a specific port without having to update all of the ports above it. That would make the default action equivalent to portupgrade's -r option (rebuild this port and all those that depend on it). What have I missed? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Portupgrade status
so can i just ask, is portmaster or another port upgrading tool recommended over portupgrade now because i'm going to be upgrading all my ports soon and in the 18 months i've been using FreeBSD i've always used portupgrade but sounds like it's best to change now. jamie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Portupgrade status
On 3 January 2011 17:54, Jamie Paul Griffin ja...@gnix.co.uk wrote: so can i just ask, is portmaster or another port upgrading tool recommended over portupgrade now because i'm going to be upgrading all my ports soon and in the 18 months i've been using FreeBSD i've always used portupgrade but sounds like it's best to change now. jamie Unless you particularly despise some aspect or feature of portupgrade, I can see little point in switching. Portmaster has the advantage of not requiring ruby or an external database, but the disadvan- tage of not having an equivalent of # portupgrade -Rf (at least last time I used it) -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Portupgrade status
On Mon, Jan 3, 2011 at 6:37 PM, ill...@gmail.com ill...@gmail.com wrote: On 3 January 2011 17:54, Jamie Paul Griffin ja...@gnix.co.uk wrote: so can i just ask, is portmaster or another port upgrading tool recommended over portupgrade now because i'm going to be upgrading all my ports soon and in the 18 months i've been using FreeBSD i've always used portupgrade but sounds like it's best to change now. jamie Unless you particularly despise some aspect or feature of portupgrade, I can see little point in switching. Portmaster has the advantage of not requiring ruby or an external database, but the disadvan- tage of not having an equivalent of # portupgrade -Rf (at least last time I used it) man portmaster reveals [-R] -f always rebuild ports (overrides -i) C- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Portupgrade status
On 3 January 2011 18:39, Chris Brennan xa...@xaerolimit.net wrote: On Mon, Jan 3, 2011 at 6:37 PM, ill...@gmail.com ill...@gmail.com wrote: On 3 January 2011 17:54, Jamie Paul Griffin ja...@gnix.co.uk wrote: so can i just ask, is portmaster or another port upgrading tool recommended over portupgrade now because i'm going to be upgrading all my ports soon and in the 18 months i've been using FreeBSD i've always used portupgrade but sounds like it's best to change now. jamie Unless you particularly despise some aspect or feature of portupgrade, I can see little point in switching. Portmaster has the advantage of not requiring ruby or an external database, but the disadvan- tage of not having an equivalent of # portupgrade -Rf (at least last time I used it) man portmaster reveals [-R] -f always rebuild ports (overrides -i) No, the -R flag in portmaster tells it to not rebuild ports taht have already been built on this run (I believe from reading man portmaster). The -R flag in portupgrade rebuilds the ports on which the named port depends -R --upward-recursive Act on all those packages required by the given packages as well. (When specified with -F, fetch recursively, including the brand new, uninstalled ports that an upgraded port requires) I don't see any equivalent functionality for portmaster, sadly. Example scenario: firefox is failing to start keeps throwing weird gtk errors, even after rebuilding gtk firefox. So you issue portupgrade -Rf firefox\*. Well, it has fixed stuff in the dim distant past, any way. -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Portupgrade status
On Mon, Jan 03, 2011 at 07:51:48PM -0500, ill...@gmail.com wrote: No, the -R flag in portmaster tells it to not rebuild ports taht have already been built on this run (I believe from reading man portmaster). The -R flag in portupgrade rebuilds the ports on which the named port depends Indeed, this -R option is useful. Up-to-now i've not used anything else other than portupgrade but i'll have a look over the man pages of portmaster, etc.; i'll probably continue to use portupgrade for a while though. jamie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Portupgrade status
On 27/12/2010 01:32, Randal L. Schwartz wrote: Rob == Rob Farmer rfar...@predatorlabs.net writes: Rob Then, the removal of MD5 distinfo broke it and it stayed broken for Rob over a week with no indication given that a fix was in the works. On Rob the other hand, Doug Barton has been very responsive to issues with Rob portmaster and fixed this problem less than 48 hours after it Rob appeared. Hence my recommendation to switch. I switched to portmaster a few months ago after being firmly in the portupgrade camp, and have not regretted it in the slightest. Same here. The biggest conceptual gotcha in switching is that portmaster always reinstalls the ports you tell it to work on, unlike portupgrade which just upgrades what's out of date unless you tell it otherwise. I also have my machines set up with a portmaster.rc like this: # # portmaster global config overrides # NO_BACKUP=Bopt PM_DEL_BUILD_ONLY=pw_dbo ALWAYS_SCRUB_DISTFILES=dopt MAKE_PACKAGE=gopt PM_PACKAGES=first LOCAL_PACKAGEDIR=/usr/ports/packages PM_PACKAGES_LOCAL=pmp_local PM_IGNORE_FAILED_BACKUP_PACKAGE=pm_ignore_failed_backup_package # # That's All Folks! # Which has two good effects: it stops portmaster asking so many questions; and it keeps a local archive of packages of everything it builds and will re-install from that local package repo where an appropriate package is available. Oh, and it removes build dependencies rather than leaving them cluttering up the disk (but it does keep packages of them, so it's quick to reinstall where needed). This saves a lot of compiling if you share your local package repo amongst several machines, or (like I do) you have a lot of churn in installed package sets. I tried doing this sort of thing with portupgrade, but I never could get it to work quite right and I always had to remember to put extra flags on the command line -- with portmaster it just works (tm). Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: Portupgrade status
On Mon, 27 Dec 2010, Matthew Seaman wrote: On 27/12/2010 01:32, Randal L. Schwartz wrote: Rob == Rob Farmer rfar...@predatorlabs.net writes: Rob Then, the removal of MD5 distinfo broke it and it stayed broken for Rob over a week with no indication given that a fix was in the works. On Rob the other hand, Doug Barton has been very responsive to issues with Rob portmaster and fixed this problem less than 48 hours after it Rob appeared. Hence my recommendation to switch. I switched to portmaster a few months ago after being firmly in the portupgrade camp, and have not regretted it in the slightest. Same here. The biggest conceptual gotcha in switching is that portmaster always reinstalls the ports you tell it to work on, unlike portupgrade which just upgrades what's out of date unless you tell it otherwise. I also have my machines set up with a portmaster.rc like this: # # portmaster global config overrides # NO_BACKUP=Bopt PM_DEL_BUILD_ONLY=pw_dbo ALWAYS_SCRUB_DISTFILES=dopt MAKE_PACKAGE=gopt PM_PACKAGES=first LOCAL_PACKAGEDIR=/usr/ports/packages PM_PACKAGES_LOCAL=pmp_local PM_IGNORE_FAILED_BACKUP_PACKAGE=pm_ignore_failed_backup_package # # That's All Folks! # Which has two good effects: it stops portmaster asking so many questions; and it keeps a local archive of packages of everything it builds and will re-install from that local package repo where an appropriate package is available. Oh, and it removes build dependencies rather than leaving them cluttering up the disk (but it does keep packages of them, so it's quick to reinstall where needed). This saves a lot of compiling if you share your local package repo amongst several machines, or (like I do) you have a lot of churn in installed package sets. I tried doing this sort of thing with portupgrade, but I never could get it to work quite right and I always had to remember to put extra flags on the command line -- with portmaster it just works (tm). Also a happy portmaster user. Thanks for the portmaster.rc ideas. For me portupgrade never really worked because I only use port management tools on workstations and I go so long between upgrades I never had any sucess using portupgrade. I also like the fact that portmaster uses only the files that are there anyway. Doug Denault ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Portupgrade status [Was Re: Portmaster general questions and problems]
On Sun, Dec 26, 2010 at 13:42, Bob Hall rjh...@gmail.com wrote: On Sun, Dec 26, 2010 at 11:39:58AM -0800, Ron (Lists) wrote: But, due to portupgrade no longer being maintained and failing to work anymore, I'm a bit confused about this. I did a quick google search and saw that someone had stopped maintaining portupgrade, but I also saw things that suggested that other people were maintaining it. The handbook continues to list it ahead of portmanager and portmaster, with no mention that it isn't being maintained. I've never stopped using portupgrade, and it has always worked. Updates come through periodically, two in the past month. For a port that isn't being maintained, it seems to be remarkably well maintained. I assume you are referring to my message from a couple months ago. At the time, the previous maintainer dropped it and transferred it to a mailing list. There had been no commits for around a year and a half. I am personally skeptical of anything maintained by a mailing list, because that seems to frequently lead to patches and bug reports being ignored for months or years. Then, the removal of MD5 distinfo broke it and it stayed broken for over a week with no indication given that a fix was in the works. On the other hand, Doug Barton has been very responsive to issues with portmaster and fixed this problem less than 48 hours after it appeared. Hence my recommendation to switch. -- Rob Farmer ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Portupgrade status
Rob == Rob Farmer rfar...@predatorlabs.net writes: Rob Then, the removal of MD5 distinfo broke it and it stayed broken for Rob over a week with no indication given that a fix was in the works. On Rob the other hand, Doug Barton has been very responsive to issues with Rob portmaster and fixed this problem less than 48 hours after it Rob appeared. Hence my recommendation to switch. I switched to portmaster a few months ago after being firmly in the portupgrade camp, and have not regretted it in the slightest. -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 mer...@stonehenge.com URL:http://www.stonehenge.com/merlyn/ Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc. See http://methodsandmessages.posterous.com/ for Smalltalk discussion ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Portupgrade status
Quoth Randal L. Schwartz on Sunday, 26 December 2010: Rob == Rob Farmer rfar...@predatorlabs.net writes: Rob Then, the removal of MD5 distinfo broke it and it stayed broken for Rob over a week with no indication given that a fix was in the works. On Rob the other hand, Doug Barton has been very responsive to issues with Rob portmaster and fixed this problem less than 48 hours after it Rob appeared. Hence my recommendation to switch. I switched to portmaster a few months ago after being firmly in the portupgrade camp, and have not regretted it in the slightest. -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 mer...@stonehenge.com URL:http://www.stonehenge.com/merlyn/ Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc. See http://methodsandmessages.posterous.com/ for Smalltalk discussion What do you see as its primary practical benefits? -- Sterling (Chip) Camden| sterl...@camdensoftware.com | 2048D/3A978E4F http://camdensoftware.com | http://chipstips.com| http://chipsquips.com pgpLbLsbIJyyq.pgp Description: PGP signature
Re: portupgrade
On Wed, 15 Dec 2010 10:31:01 +0800 xinyou yan yxy@gmail.com wrote: if i use portupgrade -af --patch (it take much times) what's --patch? And i don't finish it Then the second time . i do it again Does it continue or reupgrade anythins It starts again. See pkg_glob(1) for how to avoid this. The gnome show me i can upgrade some software . However i can't upgrade ,because it can't get information ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade causes kernel message: maxproc limit exceeded by uid 0
On 12/05/2010 10:45 AM, Lowell Gilbert wrote: Yuri y...@rawbw.com writes: Beginning at some time less than 1 month ago I started getting such message. Increasing maxproc doesn't help. Current values are like this: kern.maxproc: 6164 kern.maxprocperuid: 5547 What may be causing such condition? limits(1), perhaps? I DoSed a remote box building devel/glib20 too. Just now reproduced it locally. It manifested as a forkbomb somewhere in gnome-libtool while building glib-2.26.1 inside a clean chroot (not a jail). The issue seemed to only manifest within the chroot, regardless of whether the configuration was identical to the host or not. It did not occur when attempting to build on the host machine. Every other package I built worked just fine. I eventually tracked it down to a stray colon at the start of the PATH variable in my chroot build environment: PATH=:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin Thus, it might be a good idea to verify that your build environment variables and config files are sane. == mv -f .deps/gdatetime.Tpo .deps/gdatetime.Po /bin/sh /usr/obj/usr/ports/devel/glib20/work/gnome-libtool --tag=CC --mode=link cc -O2 -pipe -O2 -pipe -march=nocona -fno-strict-aliasing -Wall -L/usr/local/lib -lintl -o strfuncs strfuncs.o ../../glib/libglib-2.0.la -lm mv -f .deps/regex.Tpo .deps/regex.Po /bin/sh /usr/obj/usr/ports/devel/glib20/work/gnome-libtool --tag=CC --mode=link cc -O2 -pipe -O2 -pipe -march=nocona -fno-strict-aliasing -Wall -L/usr/local/lib -lintl -o string string.o ../../glib/libglib-2.0.la -lm printf: Cannot fork: Resource temporarily unavailable printf: Cannot fork: Resource temporarily unavailable printf: Cannot fork: Resource temporarily unavailable printf: Cannot fork: Resource temporarily unavailable printf: Cannot fork: Resource temporarily unavailable /libexec/ld-elf.so.1: Shared object libglib-2.0.so.0 not found, required by printf == -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net cyber...@cyberleo.net Furry Peace! - http://.fur.com/peace/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade causes kernel message: maxproc limit exceeded by uid 0
Yuri y...@rawbw.com writes: Beginning at some time less than 1 month ago I started getting such message. Increasing maxproc doesn't help. Current values are like this: kern.maxproc: 6164 kern.maxprocperuid: 5547 What may be causing such condition? limits(1), perhaps? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade fails to run or do anything
On Sun, Nov 7, 2010 at 12:21 PM, Ron (Lists) rg.li...@rzweb.com wrote: I'm trying to upgrade my ports and I can't get portupgrade to do anything. I type 'sudo portupgrade apache' (or any package) and all I get back is a command prompt. No error or any other message. portversion seems to work correctly, showing my out of date ports, etc. Running portupgrade with -F doesn't help at all. I've also noticed that tab-expansion isn't working like it used to on the port names, so that makes me wonder if the database is screwed up. I've tried running pkgdb and it just returns like portupgrade. Running portsdb to try and rebuild the index doesn't help. Any ideas? I'm perplexed and Google is no help. Thanks Syntax is 'portupgrade www/apache' (/usr/ports is assumed) Did you know... If you play a Windows 2000 CD backwards, you hear satanic messages, but what's worse is when you play it forward ...it installs Windows 2000 -- Alfred Perlstein on chat at freebsd.org http://lists.freebsd.org/mailman/listinfo/freebsd-questions ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade fails to run or do anything
On Sun, 7 Nov 2010 12:57:03 -0500, Chris Brennan xa...@xaerolimit.net wrote: On Sun, Nov 7, 2010 at 12:21 PM, Ron (Lists) wrote: I'm trying to upgrade my ports and I can't get portupgrade to do anything. I type 'sudo portupgrade apache' (or any package) and all I get back is a command prompt. No error or any other message. portversion seems to work correctly, showing my out of date ports, etc. Running portupgrade with -F doesn't help at all. I've also noticed that tab-expansion isn't working like it used to on the port names, so that makes me wonder if the database is screwed up. I've tried running pkgdb and it just returns like portupgrade. Running portsdb to try and rebuild the index doesn't help. Any ideas? I'm perplexed and Google is no help. Thanks Syntax is 'portupgrade www/apache' (/usr/ports is assumed) 'portupgrade apache' has always worked before and adding the www/ in front does not fix the problem. Still the same results, e.g. nothing. :-) Ron ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade fails to run or do anything
On Sun, 07 Nov 2010 09:21:22 -0800, Ron (Lists) rg.li...@rzweb.com wrote: I'm trying to upgrade my ports and I can't get portupgrade to do anything. I type 'sudo portupgrade apache' (or any package) and all I get back is a command prompt. No error or any other message. portversion seems to work correctly, showing my out of date ports, etc. You need to be in /usr/ports and then issue the port name together with the category; in your case: % cd /usr/ports % sudo portupgrade www/apache Running portupgrade with -F doesn't help at all. I've also noticed that tab-expansion isn't working like it used to on the port names, so that makes me wonder if the database is screwed up. The expansion is handled by the shell, and based on the content of directories accessed. If you follow the example above, autocomplete should work fine. I've tried running pkgdb and it just returns like portupgrade. That should not be; did you run this? # pkgdb -aF This is the most common call for that program, issued as root (or via su or sudo or super). Running portsdb to try and rebuild the index doesn't help. See from the manpage: Note that INDEX file is updated every few hours on official site, it is recommended that you run ``portsdb -Fu'' after every CVSup of the ports tree in order to keep them always up-to-date and in sync with the ports tree. Any ideas? I'm perplexed and Google is no help. I can suggest reading the manpages of the programs in question before consulting google. One of FreeBSD's strengths is its EXCELLENT documentation. Know about that fact, and it will help you in many situations. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade fails to run or do anything
On Sun, 7 Nov 2010 19:08:23 +0100, Polytropon free...@edvax.de wrote: On Sun, 07 Nov 2010 09:21:22 -0800, Ron (Lists) rg.li...@rzweb.com wrote: I'm trying to upgrade my ports and I can't get portupgrade to do anything. I type 'sudo portupgrade apache' (or any package) and all I get back is a command prompt. No error or any other message. portversion seems to work correctly, showing my out of date ports, etc. You need to be in /usr/ports and then issue the port name together with the category; in your case: % cd /usr/ports % sudo portupgrade www/apache Running portupgrade with -F doesn't help at all. I've also noticed that tab-expansion isn't working like it used to on the port names, so that makes me wonder if the database is screwed up. The expansion is handled by the shell, and based on the content of directories accessed. If you follow the example above, autocomplete should work fine. I've tried running pkgdb and it just returns like portupgrade. That should not be; did you run this? # pkgdb -aF This is the most common call for that program, issued as root (or via su or sudo or super). Running portsdb to try and rebuild the index doesn't help. See from the manpage: Note that INDEX file is updated every few hours on official site, it is recommended that you run ``portsdb -Fu'' after every CVSup of the ports tree in order to keep them always up-to-date and in sync with the ports tree. Any ideas? I'm perplexed and Google is no help. I can suggest reading the manpages of the programs in question before consulting google. One of FreeBSD's strengths is its EXCELLENT documentation. Know about that fact, and it will help you in many situations. :-) None of these suggestions help. I have never had to put www/ in front of the port name before. The tab expansion is handled by bash-completion as used to be smart enough to know the command I was typing and could auto-complete port names, but no longer, which is why I suspect that I have a screwed up database. Ron ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade fails to run or do anything
On Sun, Nov 7, 2010 at 10:15, Ron (Lists) rg.li...@rzweb.com wrote: None of these suggestions help. I have never had to put www/ in front of the port name before. The tab expansion is handled by bash-completion as used to be smart enough to know the command I was typing and could auto-complete port names, but no longer, which is why I suspect that I have a screwed up database. Perhaps it is fallout from recent infrastructure changes? http://lists.freebsd.org/pipermail/cvs-ports/2010-October/205680.html Portupgrade doesn't seem to have an active maintainer, so perhaps try portmaster. -- Rob Farmer ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade fails to run or do anything
On Sun, Nov 07, 2010 at 09:21:22AM -0800, Ron (Lists) wrote: I'm trying to upgrade my ports and I can't get portupgrade to do anything. I type 'sudo portupgrade apache' (or any package) and all I get back is a command prompt. No error or any other message. portversion seems to work correctly, showing my out of date ports, etc. Running portupgrade with -F doesn't help at all. I've also noticed that tab-expansion isn't working like it used to on the port names, so that makes me wonder if the database is screwed up. I've tried running pkgdb and it just returns like portupgrade. Running portsdb to try and rebuild the index doesn't help. Any ideas? I'm perplexed and Google is no help. Thanks Give portupgrade the -v arg to get some debugging information. E.g: # sudo portupgrade -v apache\* Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade fails to run or do anything
On Sun, 7 Nov 2010 10:32:05 -0800 Rob Farmer rfar...@predatorlabs.net articulated: On Sun, Nov 7, 2010 at 10:15, Ron (Lists) rg.li...@rzweb.com wrote: None of these suggestions help. I have never had to put www/ in front of the port name before. The tab expansion is handled by bash-completion as used to be smart enough to know the command I was typing and could auto-complete port names, but no longer, which is why I suspect that I have a screwed up database. Perhaps it is fallout from recent infrastructure changes? http://lists.freebsd.org/pipermail/cvs-ports/2010-October/205680.html Portupgrade doesn't seem to have an active maintainer, so perhaps try portmaster. Really! When did r...@freebsd.org drop the port? If he is not actively maintaining the port then perhaps he should inform the proper authority. -- Jerry ✌ freebsd.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ Anoint, v.: To grease a king or other great functionary already sufficiently slippery. Ambrose Bierce, The Devil's Dictionary ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade fails to run or do anything
On Sun, Nov 7, 2010 at 12:12, Jerry freebsd.u...@seibercom.net wrote: Really! When did r...@freebsd.org drop the port? If he is not actively maintaining the port then perhaps he should inform the proper authority. He is a mailing list. ports/ports-mgmt/portupgrade/Makefile Revision 1.256 Tue Jul 21 13:12:15 2009 PDT (15 months, 2 weeks ago) by sem Log: - Drop maintainership to ruby@ Beyond this point virtually no development has happened. The sourceforge project hasn't been updated since around that time and there are open PRs over two years old. Unfortuantely, FreeBSD has a lot of these niche mailing lists that virtually nobody reads but have PRs auto-assigned to them, effectively acting as a black hole. freebsd-rc is one of the worst offenders - other than Doug Barton, there don't seem to be any developers involved there and it has a massive buildup of unreviewed patches. So I would say portupgrade is unmaintained and thus encourage people to move to portmaster. -- Rob Farmer ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade fails to run or do anything
On Sun, 7 Nov 2010, Ron (Lists) wrote: I'm trying to upgrade my ports and I can't get portupgrade to do anything. I type 'sudo portupgrade apache' (or any package) and all I get back is a command prompt. No error or any other message. portversion seems to work correctly, showing my out of date ports, etc. Is apache outdated? portupgrade won't update a port that's already at the current version unless you force it with -f. Running portupgrade with -F doesn't help at all. Well, no. -F means to only download distfiles. I've also noticed that tab-expansion isn't working like it used to on the port names, so that makes me wonder if the database is screwed up. Filename completion is a function of the shell. I try it accidentally from time to time with port names because it just would make sense to work, but it has never worked because they don't exist as files. 'portupgrade -r gcc' followed by Tab doesn't complete because there isn't a file named gcc-4.4.6.20101026 in the path (although they are in /var/db/pkg). Fortunately, name completion is not needed because portupgrade uses the pkg_name as a glob anyway. My portupgrade article: http://www.wonkity.com/~wblock/docs/html/portupgrade.html If that doesn't do it, please show what portversion -vl'' shows for apache. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade fails to run or do anything
On Sun, 7 Nov 2010, Polytropon wrote: On Sun, 07 Nov 2010 09:21:22 -0800, Ron (Lists) rg.li...@rzweb.com wrote: I'm trying to upgrade my ports and I can't get portupgrade to do anything. I type 'sudo portupgrade apache' (or any package) and all I get back is a command prompt. No error or any other message. portversion seems to work correctly, showing my out of date ports, etc. You need to be in /usr/ports and then issue the port name together with the category; in your case: % cd /usr/ports % sudo portupgrade www/apache For shell filename completion to work, that is. portupgrade doesn't care about the current directory. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade fails to run or do anything
On Sun, 7 Nov 2010, Ron (Lists) wrote: None of these suggestions help. I have never had to put www/ in front of the port name before. It's not needed. The tab expansion is handled by bash-completion as used to be smart enough to know the command I was typing and could auto-complete port names, but no longer, which is why I suspect that I have a screwed up database. No, more likely your path changed and left out /var/db/pkg. This is not needed anyway, since the pkg_name is a glob: portupgrade -r apache will upgrade all ports starting with apache. The -r is something I suggest using regularly with portupgrade. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade command line option -f problem
On Wed, 13 Oct 2010 13:24:26 +0100 David Southwell da...@vizion2000.net wrote: Tried that but no good - it still seems to goof up. I recall it used to work many versions ago but it may not have been picked up on a regression test. It works for me. Which port is it failing on portupgrade -frR apache22 does not rebuild apache modules david Should have mentioned this is after adding WITH_OPENSSL_FROM_PORTS=yes to make.conf. This change requires a rebuild of apache modules. david Photographic Artist Permanent Installations Design Creative Imagery and Advanced Digital Techniques High Dynamic Range Photography Official Portraiture Combined darkroom digital creations Systems Adminstrator for the vizion2000.net network ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade command line option -f problem
On Wed, 13 Oct 2010 13:24:26 +0100 David Southwell da...@vizion2000.net wrote: Tried that but no good - it still seems to goof up. I recall it used to work many versions ago but it may not have been picked up on a regression test. It works for me. Which port is it failing on portupgrade -frR apache22 does not rebuild apache modules david Photographic Artist Permanent Installations Design Creative Imagery and Advanced Digital Techniques High Dynamic Range Photography Official Portraiture Combined darkroom digital creations Systems Adminstrator for the vizion2000.net network ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade command line option -f problem
On Wed, 13 Oct 2010 10:14:30 +0100 David Southwell da...@vizion2000.net articulated: man portupgrade advises: -f --forceForce the upgrade of a package even if it is to be a downgrade or just a reinstall of the same ver- sion, or the port is held by user using the HOLD_PKGS variable in pkgtools.conf. In practice on freebsd 7.2 p3 amd generic I find that uptodate packages are excluded! [Exclude up-to-date packages [done] Whereas I wish to have all identified packages rebuilt even if they are shown as being up to date. This may be necessary if, for example, a change has been made to make.conf which affects ports might have an up to date version but were compiled prior to the changes in make.conf. Unless I am mistaken it seems as though the -f option not produce results I expect after reading the man page. You could use 'portmanager -f'. I can guarantee that it will rebuild everything. -- Jerry ✌ freebsd.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ Lawrence Radiation Laboratory keeps all its data in an old gray trunk. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade command line option -f problem
On Wed, 13 Oct 2010 10:14:30 +0100 David Southwell da...@vizion2000.net wrote: Hi man portupgrade advises: -f --forceForce the upgrade of a package even if it is to be a downgrade or just a reinstall of the same ver- sion, or the port is held by user using the HOLD_PKGS variable in pkgtools.conf. In practice on freebsd 7.2 p3 amd generic I find that uptodate packages are excluded! [Exclude up-to-date packages [done] I think it's misleading, in my experience it does then go on to reinstall the ports. If nothing gets rebuilt try specifying the full package name or the origin. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade command line option -f problem
On Wed, 13 Oct 2010 10:14:30 +0100 David Southwell da...@vizion2000.net wrote: Hi man portupgrade advises: -f --forceForce the upgrade of a package even if it is to be a downgrade or just a reinstall of the same ver- sion, or the port is held by user using the HOLD_PKGS variable in pkgtools.conf. In practice on freebsd 7.2 p3 amd generic I find that uptodate packages are excluded! [Exclude up-to-date packages [done] I think it's misleading, in my experience it does then go on to reinstall the ports. If nothing gets rebuilt try specifying the full package name or the origin. Tried that but no good - it still seems to goof up. I recall it used to work many versions ago but it may not have been picked up on a regression test. David Photographic Artist Permanent Installations Design Creative Imagery and Advanced Digital Techniques High Dynamic Range Photography Official Portraiture Combined darkroom digital creations Systems Adminstrator for the vizion2000.net network ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade command line option -f problem
On Wed, 13 Oct 2010 13:24:26 +0100 David Southwell da...@vizion2000.net wrote: Tried that but no good - it still seems to goof up. I recall it used to work many versions ago but it may not have been picked up on a regression test. It works for me. Which port is it failing on? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade -af in FreeBSDupdate to 8.0
On 23 June 2010 08:29, n dhert ndhert...@gmail.com wrote: in the process of upgrading 7.2 - 8.0, the last step is to recompile all ports (section 24.2.3 of freebsd manual) # portupgrade -f ruby # rm /var/db/pkg/pkgdb.db # portugprade -f ruby18-bdb # rm /var/db/pkg/pkgdb.db /usr/ports/INDEX-*.db # portupgrade -af Did that for my 760 ports, but after 499 ports reinstalled (and 11 hours), it stopped snip / Why does it stop? Can it be avoided? Or can I make portupgrade -af start from where it got so far in the first run ? I could do # portupgrade -af again, but this is again everything (11 hours)... I noticed on a different system (with only 64 ports), that it stopped at lang/ruby18 there as well, and after again # portugprade -af (which then continued past lang/ruby18), it stopped a second time in the same manner at --- Reinstallation of databases/ruby-bdb ended at: Mon, 14 Jun 2010 13:01:25 +0200 (consumed 00:00:28) AFAICR, portupgrade is written in Ruby, so strange things can happen if you pull the carpet out from under it like that. Not really your fault... I suggest you look at the man page for pkg_glob, and look for the kind of glob to supply for portupgrade; for example: The following command line arguments are supported: pkgname_globSpecify one of these: a full pkgname, a pkgname with- out version, or a shell glob pattern to match against pkgnames or their origins in which you can use wild- cards `*', `?', and `[..]', an extended regular expression preceded by a colon `:' to match against pkgnames or their origins, or a date range specifica- tion preceded by either `' or `'. So try [ch...@amnesiac]~% sudo portupgrade -f '2010-06-22' That should reinstall all the ports that were installed before yesterday. HTH Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade -af in FreeBSDupdate to 8.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 23/06/2010 08:29:41, n dhert wrote: Why does it stop? Can it be avoided? Or can I make portupgrade -af start from where it got so far in the first run ? portupgrade is written in ruby -- having its command interpreter ripped out from underneath it does tend to cramp its style somewhat. Actually, the specific reason it crashes is the ruby-18-dbXX module, which also needs to be recompiled. The best way around the problem is to delete portupgrade and everything it depends on, and then reinstall from the ports directly: # pkg_deinstall -Rf portupgrade-2.4.6_4,2 # cd /usr/ports/ports-mgmt/portupgrade # make install # make clean If you do this first, you can then run portupgrade -af, which will recompile ruby and dependencies, but because everything is already recompiled, its compatible and you don't get a crash. I could do # portupgrade -af again, but this is again everything (11 hours)... Fix portupgrade as shown above, then run something like this: # portupgrade -x =2010-06-23 -af This says: upgrade everything, except those packages installed more recently than 2010-06-23. You should chose the date where you *started* your original portupgrade -af session. Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkwhzMcACgkQ8Mjk52CukIzDsACeNRckO4634CcnAKcBPDduooos afIAnRsAWncQzPAndKR7v6ulNYdHIEXF =oSps -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade
2010/2/8 Dánielisz László laszlo_daniel...@yahoo.com: hi, do you have any idea why it is not upgrading: root# portversion -v|grep php php5-5.2.12 succeeds port (port has 5.2.10) php5-pcre-5.2.12 succeeds port (port has 5.2.10) php5-session-5.2.12 succeeds port (port has 5.2.10) php5-simplexml-5.2.12 succeeds port (port has 5.2.10) php5-spl-5.2.12 succeeds port (port has 5.2.10) php5-sqlite-5.2.12 succeeds port (port has 5.2.10) root# portupgrade -vr php5 --- Session started at: Mon, 08 Feb 2010 09:40:19 +0100 ** None has been installed or upgraded. --- Session ended at: Mon, 08 Feb 2010 09:40:20 +0100 (consumed 00:00:01 Do you use portsnap? If yes, try 'portsnap fetch update' - If you have '/usr/sbin/portsnap -I cron update' in your crontab it will only update the INDEX files. -- chs, ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade
Szia László! 2010/2/8 Dánielisz László laszlo_daniel...@yahoo.com hi, do you have any idea why it is not upgrading: root# portversion -v|grep php php5-5.2.12 succeeds port (port has 5.2.10) php5-pcre-5.2.12 succeeds port (port has 5.2.10) php5-session-5.2.12 succeeds port (port has 5.2.10) php5-simplexml-5.2.12 succeeds port (port has 5.2.10) php5-spl-5.2.12 succeeds port (port has 5.2.10) php5-sqlite-5.2.12succeeds port (port has 5.2.10) root# portupgrade -vr php5 --- Session started at: Mon, 08 Feb 2010 09:40:19 +0100 ** None has been installed or upgraded. --- Session ended at: Mon, 08 Feb 2010 09:40:20 +0100 (consumed 00:00:01 Because installed version is higher than version in port tree (5.2.12 5.2.10). Have you upgraded your port tree before? Bye, Zsolt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade
Szia Zsolt! Thank you everybody! Actually I use cvsup, and it is up to date, but now I give a try with portsnap. László From: Artifex Maximus artife...@gmail.com To: Dánielisz László laszlo_daniel...@yahoo.com Cc: freebsd-questions@freebsd.org Sent: Mon, February 8, 2010 10:34:53 AM Subject: Re: portupgrade Szia László! 2010/2/8 Dánielisz László laszlo_daniel...@yahoo.com hi, do you have any idea why it is not upgrading: root# portversion -v|grep php php5-5.2.12 succeeds port (port has 5.2.10) php5-pcre-5.2.12 succeeds port (port has 5.2.10) php5-session-5.2.12 succeeds port (port has 5.2.10) php5-simplexml-5.2.12 succeeds port (port has 5.2.10) php5-spl-5.2.12 succeeds port (port has 5.2.10) php5-sqlite-5.2.12succeeds port (port has 5.2.10) root# portupgrade -vr php5 --- Session started at: Mon, 08 Feb 2010 09:40:19 +0100 ** None has been installed or upgraded. --- Session ended at: Mon, 08 Feb 2010 09:40:20 +0100 (consumed 00:00:01 Because installed version is higher than version in port tree (5.2.12 5.2.10). Have you upgraded your port tree before? Bye, Zsolt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade
László wrote: Thank you everybody! Actually I use cvsup, and it is up to date, but now I give a try with portsnap. It sounds like your index file or your portsdb are older than the rest of your ports tree. Try running 'portsdb -Fu'. b. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade
On Mon, 8 Feb 2010, D?nielisz L?szl? wrote: do you have any idea why it is not upgrading: root# portversion -v|grep php php5-5.2.12 succeeds port (port has 5.2.10) php5-pcre-5.2.12 succeeds port (port has 5.2.10) php5-session-5.2.12 succeeds port (port has 5.2.10) php5-simplexml-5.2.12 succeeds port (port has 5.2.10) php5-spl-5.2.12 succeeds port (port has 5.2.10) php5-sqlite-5.2.12succeeds port (port has 5.2.10) root# portupgrade -vr php5 --- Session started at: Mon, 08 Feb 2010 09:40:19 +0100 ** None has been installed or upgraded. --- Session ended at: Mon, 08 Feb 2010 09:40:20 +0100 (consumed 00:00:01 Because you already have newer versions than are in ports, 5.2.12 installed when the port still has 5.2.10. This can happen if the ports tree or index file is outdated. csup/portsnap, run pkgdb -Fu, and try it again. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade, batch mode?
. use the the --batch switch or put BATCH=yes in make.conf IIRC. That particular make.conf is in /etc But IMHO, remembering to always give portupgrade the -C switch is the way to go. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade
This can happen if the ports tree or index file is outdated. csup/portsnap, run pkgdb -Fu, and try it again. I think you meant 'portsdb -Fu'. The pkgtools often run 'pkgdb -u' and 'pkgdb -aF' automatically, and a full-blown 'pkgdb -F' or 'pkgdb -L' usually isn't required unless there is an error, although in most cases it wouldn't do any harm. b. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade
On Mon, 8 Feb 2010, b. f. wrote: This can happen if the ports tree or index file is outdated. csup/portsnap, run pkgdb -Fu, and try it again. I think you meant 'portsdb -Fu'. The pkgtools often run 'pkgdb -u' and 'pkgdb -aF' automatically, and a full-blown 'pkgdb -F' or 'pkgdb -L' usually isn't required unless there is an error, although in most cases it wouldn't do any harm. Doh, that's correct--portsdb. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade
I resolve that problem, by the handbook I added 0 3 * * * root portsnap -I cron update pkg_version -vIL= Now it works awesome! From: Warren Block wbl...@wonkity.com To: b. f. bf1...@googlemail.com Cc: freebsd-questions@FreeBSD.org; Dánielisz László laszlo_daniel...@yahoo.com Sent: Mon, February 8, 2010 9:03:39 PM Subject: Re: portupgrade On Mon, 8 Feb 2010, b. f. wrote: This can happen if the ports tree or index file is outdated. csup/portsnap, run pkgdb -Fu, and try it again. I think you meant 'portsdb -Fu'. The pkgtools often run 'pkgdb -u' and 'pkgdb -aF' automatically, and a full-blown 'pkgdb -F' or 'pkgdb -L' usually isn't required unless there is an error, although in most cases it wouldn't do any harm. Doh, that's correct--portsdb. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade, batch mode?
I think you can try this: -y --yes Answer yes to all the questions. This option implies -v and negates -n . László On 2010.02.07., at 12:59, n dhert ndh...@gmail.com wrote: When using portupgrade, from time to time, there is a package that displays an options menu and waits for a interactive response (like hitting OK to accept the defaults and continue). Is there way to specify that portupgrade should always accept the defaults and not wait for user input? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade, batch mode?
On 07/02/2010 2:14 μ.μ., Dánielisz László wrote: I think you can try this: -y --yes Answer yes to all the questions. This option implies -v and negates -n . László On 2010.02.07., at 12:59, n dhert ndh...@gmail.com wrote: When using portupgrade, from time to time, there is a package that displays an options menu and waits for a interactive response (like hitting OK to accept the defaults and continue). Is there way to specify that portupgrade should always accept the defaults and not wait for user input? And in fact, you can also use --batch ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade, batch mode?
On Sun, Feb 07, 2010 at 12:59:53PM +0100, n dhert wrote: When using portupgrade, from time to time, there is a package that displays an options menu and waits for a interactive response (like hitting OK to accept the defaults and continue). Is there way to specify that portupgrade should always accept the defaults and not wait for user input? What I do when portupgrading something that will require user input in an options menu is to use the -C switch to portupgrade. This enables you to twiddle with the options of all the ports before the main build starts. If you know that you want to use the defaults, then you can use the the --batch switch or put BATCH=yes in make.conf IIRC. But IMHO, remembering to always give portupgrade the -C switch is the way to go. Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade, batch mode?
Frank == Frank Shute fr...@shute.org.uk writes: Frank But IMHO, remembering to always give portupgrade the -C switch is the Frank way to go. Sadly, I've run across Perl ports that still ask questions, even when being run from portupgrade, and -C doesn't help those. I'm guessing from this description that I should be noticing these and reporting it to someone? -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 mer...@stonehenge.com URL:http://www.stonehenge.com/merlyn/ Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc. See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade, batch mode?
On Sun, Feb 07, 2010 at 12:26:49PM -0800, Randal L. Schwartz wrote: Frank == Frank Shute fr...@shute.org.uk writes: Frank But IMHO, remembering to always give portupgrade the -C switch is the Frank way to go. Sadly, I've run across Perl ports that still ask questions, even when being run from portupgrade, and -C doesn't help those. All the Perl ports I've installed (e.g p5-*) have just installed for me without any curses options menu. Although I'd describe you as a Perl power user and undoubtedly have more Perl ports installed than I have. I'm guessing from this description that I should be noticing these and reporting it to someone? Are you talking about ports that depend on Perl? Can you give an example of a Perl port that asks you questions? Don't mean to be obstructive in any way; genuinely curious as AFAICR I haven't come across one. It could be that the questions asked of you when you install the ports are outside the scope of a curses interface i.e because you have to type something in rather than (un)tick an option. In that case, the -C option to portupgrade or the --batch option wont work. PS. Many thanks for your writings on Perl, they largely taught me what I know of Perl and led to many hours of enjoyment. Many Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade, batch mode?
Frank == Frank Shute fr...@shute.org.uk writes: Frank All the Perl ports I've installed (e.g p5-*) have just installed for Frank me without any curses options menu. Lucky. :) Frank Although I'd describe you as a Perl power user and undoubtedly have Frank more Perl ports installed than I have. red.stonehenge.com:~ +# pkg_info | grep -c 'p5-' 3314 red.stonehenge.com:~ +# cat MAKE_ALL_PERL_PORTS #!/bin/sh cd /usr/ports || exit 1 pkg_info -q -o -a /tmp/$$ for i in `ls -d */p5* | fgrep -vxf /tmp/$$` do if pkg_info -q -O $i | grep -q . then echo SKIPPING $i - INSTALLED; else ( cd $i echo == $i == if make missing | grep -v '/p5-' then echo SKIPPING $i - DEPENDENCIES else ( trap ':' 2 make BATCH=yes install clean /dev/null ) fi ) fi done Yes, I have actually installed all Perl ports that depend only on other CPAN modules, and not anything else that I didn't already have installed. Frank Are you talking about ports that depend on Perl? Can you give an Frank example of a Perl port that asks you questions? Don't mean to be Frank obstructive in any way; genuinely curious as AFAICR I haven't come Frank across one. I wish I could remember. Just that something comes up every once in a while and I curse that the upgrade has stopped. :) -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 mer...@stonehenge.com URL:http://www.stonehenge.com/merlyn/ Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc. See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade, batch mode?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/02/2010 21:38, Randal L. Schwartz wrote: I wish I could remember. Just that something comes up every once in a while and I curse that the upgrade has stopped. :) net/p5-Net is one I always keep coming across that asks annoying questions. Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAktvw3AACgkQ8Mjk52CukIxSHgCdGgNb0qLSwc1UGOW2pm10XRhN bF8An0cAff8a0uJCpg9ZXAvUXTYnV1bS =QCf9 -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade fail qt4-rcc-4.6.1
On Thursday 21 January 2010 10:34:59 pm n dhert wrote: Today there were about 7 portupgrades to qt4 packages. Upgrading 'qt4-rcc-4.5.3' to 'qt4-rcc-4.6.1' (devel/qt4-rcc) failed: ... c++ -c -O2 -fno-strict-aliasing -pipe -O2 -fPIC -Wall -W -DQT_BOOTSTRAPPED -DQT_ LITE_UNICODE -DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_TO_ASCII -DQT_NO_CODECS -DQT_N O_DATASTREAM -DQT_NO_GEOM_VARIANT -DQT_NO_LIBRARY -DQT_NO_QOBJECT -DQT_NO_STL -D QT_NO_SYSTEMLOCALE -DQT_NO_TEXTSTREAM -DQT_NO_THREAD -DQT_NO_UNICODETABLES -DQT_ NO_USING_NAMESPACE -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -I/usr/local/share/ qt4/mkspecs/freebsd-g++ -I. -I../../../include -I../../../include/QtCore -I../.. /../include/QtXml -I/usr/local/include -o .obj/release-static/qfsfileengine_unix .o ../../corelib/io/qfsfileengine_unix.cpp ../../corelib/io/qfsfileengine_unix.cpp: In member function 'uchar* QFSFileEngin ePrivate::map(qint64, qint64, QFile::MemoryMapFlags)': ../../corelib/io/qfsfileengine_unix.cpp:1273: warning: comparaison between signed and unsigned integer expressions ../../corelib/io/qfsfileengine_unix.cpp:1293: error: 'QT_MMAP' was not declared in this scope *** Error code 1 Stop in /usr/ports/devel/qt4-rcc/work/qt-everywhere-opensource-src-4.6.1/src/ too ls/bootstrap. *** Error code 1 Stop in /usr/ports/devel/qt4-rcc. --- Build of devel/qt4-rcc ended at: Fri, 22 Jan 2010 07:09:07 +0100 (consumed 00:01:47) --- Upgrade of devel/qt4-rcc ended at: Fri, 22 Jan 2010 07:09:07 +0100 (consum ed 00:01:47) Waht's wrong and how to remedy? I found that portugrade was trying to upgrade qt4-rcc or moc on my machines before it upgraded their only dependency, qt4-qmake. I updated that and then everything worked just fine. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade and checksum mismatch
Jamie Griffin wrote: been trying to portupgrade firefox3 for about a day but keep getting a checksum mismatch error and the build stops. What do I need to do to get it to upgrade? Try deleting the firefox sources you downloaded previously and start again. It seems your download somehow got corrupted: # cd /usr/ports/www/firefox35 # make distclean # make install If you still get a corrupted download, try fetching manually from one of the other FTP sites (hint: make -v MASTER_SITES) or grab the tarball from ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ -- then just put the source tarball into /usr/ports/distfiles and restart the build. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: portupgrade failure
On Wed, Dec 16, 2009 at 7:24 PM, Mark Linimon lini...@lonesome.com wrote: On Wed, Dec 16, 2009 at 11:13:36PM -0500, Robert Huff wrote: The maintainer, ruby@, is aware of this; a check of the PR database shows multiple open PRs, none critical but many serious going back six months and more. As an aside, the Severity and Priority fields have been so often abused as to have become meaningless. Although I still try to groom the db for critical ones, and thus try to get those some attention, I really don't think the committers pay much attention. (In general I think those should be reserved for data corruption and security.) The longer-term solution is to remove those as user-settable fields. This hard to understand given portupgrade is the recommended upgrade tool. Once the individual who was working on it gave it up to the mailing list, it became one of those everyone is responsible so no one is responsible problems. I don't have a recommended fix for this. Having said that, I have a ports tree as of a month ago and portupgrade was working ok for me. I don't have the cycles to go figure out where it fails to be able to fix it, sorry. mcl Thanks to everyone for the tips. I downgraded to portupgrade-2.4.6_2,2, and am able to update my ports/packages again. I had seen others commenting on portupgrade being broken in the past, but the ruby errors made me wonder if it was actually a ruby problem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade failure
On Wed, 16 Dec 2009, Kevin wrote: [...] The only other symptoms I can identify right now are related to the following entries in my crontab: 0 2 * * 6 /usr/local/sbin/portsclean -DD 0 2 * * 5 /usr/local/sbin/portsclean -C The e-mailed results simply say env: ruby: No such file or directory. However, these commands seem to run fine from an interactive shell (while logged in). Paths. When there's a problem with cron it's (almost) always paths. portsclean is a ruby script that starts with this line: #!/usr/bin/env ruby That should find and run ruby. Your /etc/crontab should have these lines: SHELL=/bin/sh PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin I also receive the same message at the end of the output for /usr/sbin/portsnap cron update /usr/local/sbin/portsdb -u /dev/null run from cron: portsdb is another ruby script. Same deal; cron running env can't find ruby. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade failure
Hi, On Wed, Dec 16, 2009 at 11:19 PM, Warren Block wbl...@wonkity.com wrote: On Wed, 16 Dec 2009, Kevin wrote: [...] The only other symptoms I can identify right now are related to the following entries in my crontab: 0 2 * * 6 /usr/local/sbin/portsclean -DD 0 2 * * 5 /usr/local/sbin/portsclean -C The e-mailed results simply say env: ruby: No such file or directory. However, these commands seem to run fine from an interactive shell (while logged in). Paths. When there's a problem with cron it's (almost) always paths. portsclean is a ruby script that starts with this line: Interestingly, my homemade port rebuild script is recently broken with similar symptoms, sans the dependencies on ruby. It's a very simple, low-level for i in `cat list` type script which recently has begun to fail repeatedly on gettext and autoconf dependencies on multiple machines, when I specifically have them set to be upon the first ports to build. More probably unrelated, but I thought I'd throw this out there just in case. Regards, -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade failure
Glen Barber wrote: Hi, On Wed, Dec 16, 2009 at 11:19 PM, Warren Block wbl...@wonkity.com wrote: On Wed, 16 Dec 2009, Kevin wrote: [...] The only other symptoms I can identify right now are related to the following entries in my crontab: 0 2 * * 6 /usr/local/sbin/portsclean -DD 0 2 * * 5 /usr/local/sbin/portsclean -C The e-mailed results simply say env: ruby: No such file or directory. However, these commands seem to run fine from an interactive shell (while logged in). Paths. When there's a problem with cron it's (almost) always paths. portsclean is a ruby script that starts with this line: Interestingly, my homemade port rebuild script is recently broken with similar symptoms, sans the dependencies on ruby. It's a very simple, low-level for i in `cat list` type script which recently has begun to fail repeatedly on gettext and autoconf dependencies on multiple machines, when I specifically have them set to be upon the first ports to build. More probably unrelated, but I thought I'd throw this out there just in case. Regards, I don't know if it's of any help, but I had a *somewhat* similar experience, I don't know if this will help, but I'll give it to you for what it's worth: I found in my environment, I had REINPLACE_CMD defined (seemed to be a good value), so (in my shell, tcsh) I removed the REINPLACE_CMD setting with unsetenv, and the problem disappeared. Use either env or printenv to scan your environment for anything to do with sed (as REINPLACE_CMD does) and try removing it. Oh, BTW, I can't seem to get the -l logfile option to portupgrade to work, any help on that would also be appreciated. I didn't use -L at all. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade failure
On Wed, 16 Dec 2009, Warren Block wrote: On Wed, 16 Dec 2009, Kevin wrote: [...] The only other symptoms I can identify right now are related to the following entries in my crontab: 0 2 * * 6 /usr/local/sbin/portsclean -DD 0 2 * * 5 /usr/local/sbin/portsclean -C The e-mailed results simply say env: ruby: No such file or directory. However, these commands seem to run fine from an interactive shell (while logged in). Paths. When there's a problem with cron it's (almost) always paths. portsclean is a ruby script that starts with this line: #!/usr/bin/env ruby That should find and run ruby. Your /etc/crontab should have these lines: SHELL=/bin/sh PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin And now that I tried a test with these manual paths, the same thing happens: # setenv PATH /etc:/bin:/sbin:/usr/bin:/usr/sbin # env ruby env: ruby: No such file or directory Doh. ruby and ruby18 are in /usr/local/bin. So it's working as designed. A reasonable way to fix this is to add :/usr/local/bin to the crontab path, but that may not be the right way to fix it. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: portupgrade print/cups-client (cups-client-1.3.10_4) fails
On Sun, Nov 29, 2009 at 11:40:58PM -0600, Richard Kolkovich wrote: On Sun, Nov 29, 2009 at 08:42:30AM +0100, n dhert wrote: In my nightly portupgrade I got, while upgrading print/cups-client : ... /usr/bin/ld: /usr/lib/crt1.o: relocation R_X86_64_32 can not be used when making a shared object; recompile with -fPIC /usr/lib/crt1.o: could not read symbols: Bad value gmake[1]: *** [bannertops] Error 1 gmake[1]: Leaving directory `/usr/ports/print/cups-client/work/cups-1.4.2/filter ' gmake: *** [all] Error 1 *** Error code 1 Stop in /usr/ports/print/cups-client. *** Error code 1 Stop in /usr/ports/print/cups-client. I can confirm this same build error on my (amd64) box after upgrading to 8.0-STABLE (RELENG_8). cups-image was compiled previously on 8.0-RC1. Try this; # cd /usr/ports/print/cups-client # make patch # cd work/cups-1.4.2 Open Makedefs.in in an editor and remove @PIEFLAGS@ from line 143. # cd ../.. # make It should then build OK. Tested on 8.0-RELEASE amd64. The same trick is needed for cups-image, IIRC. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpzgsFvXJoID.pgp Description: PGP signature
Re: portupgrade print/cups-client (cups-client-1.3.10_4) fails
On Mon, Nov 30, 2009 at 07:49:54PM +0100, Roland Smith wrote: Try this; # cd /usr/ports/print/cups-client # make patch # cd work/cups-1.4.2 Open Makedefs.in in an editor and remove @PIEFLAGS@ from line 143. # cd ../.. # make It should then build OK. Tested on 8.0-RELEASE amd64. The same trick is needed for cups-image, IIRC. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) This works for cups-image - thanks! It looks like the cups-base maintainer has removed those in the tree: http://www.freshports.org/print/cups-base/ A 'portsnap fetch update' is all that is needed now. -- Richard Kolkovich sarum...@sigil.org PGP Key: 0x9E54EF59 (http://pgp.mit.edu) pgpBGX06ZnfQN.pgp Description: PGP signature
Re: portupgrade for binaries fails miserably, but not completely
At 12:50 AM + 11/29/09, Frank Shute wrote: You don't mention what command you are using to upgrade your ports/packages. Sorry: portupgrade -aPPR You do realise that you don't have to upgrade your ports if you go from 7.1 to 7.2. You can do but don't have to. No, I didn't realize that. The FreeBSD Handbook indicates differently. You should upgrade python25 to python26. See /usr/ports/UPDATING dated 20090608 for instructions on how to do so. Thanks, but that didn't help. So, I have now done a long, painful 'portrupgrade -a', having it stop regularly to prompt me for configuration settings. We'll see what happens when I go to 8. --Paul Hoffman ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
