Re: 7.2-STABLE to 8-R
On Wed, Nov 25, 2009 at 08:28:52AM +, John wrote: [..stuff...] Looks like I had to learn the hard way. portmanager won't fix it all. Basically had to make delete old libs and files as per the Makefile in /usr/src, then did pkg_delete -a then rm -rf /usr/ports then portsnap, then installed what ports I needed starting off with the monsters like the latest perl and xorg. -- John - comp dot john at googlemail dot com OpenBSD firewall | FreeBSD desktop | Ubuntu Karmic laptop GPG: 0xF08A33C5 ___ 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: 7.2-STABLE to 8-R
On Sun, Nov 29, 2009 at 09:49:32AM +, John wrote: Looks like I had to learn the hard way. portmanager won't fix it all. Been there, done that. :-) I think this problem is just too complex when updating between major versions, for several reasons. First of all being that the port management tool probably do not know they are updating to a new major version of the system libraries. Sometimes a port will not build correctly when an older version is installed. And there can be special instructions in /usr/ports/UPDATING that the upgrade tools can't read. IMO building a tool that can rebuild ports between major versions would be nice but not worth the effort, since it happens so infrequently. Basically had to make delete old libs and files as per the Makefile in /usr/src, then did pkg_delete -a then rm -rf /usr/ports then portsnap, then installed what ports I needed starting off with the monsters like the latest perl and xorg. It seems to me that deleting the entire ports tree is not necessary. That would delete all the distfiles as well. Next time just update it with portsnap, it will save you a lot of downloading. And if you have a spare machine, update that first and then copy /usr/local, /var/db/ports and /var/db/pkg to the other machines with the same hardware architecture. That will save you a lot of time and effort and will result in minimal downtime and risk. 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) pgpLHlNyoFGS7.pgp Description: PGP signature
Re: 7.2-STABLE to 8-R
On Tue 24 Nov 2009 at 13:29:44 PST Rolf G Nielsen wrote: Charlie Kester wrote: Can someone remind me once again, when rebuilding all of my ports, what is the trick for avoiding the options dialogs? I'd like to have this run largely unattended. I seem to recall someone describing a method to go through all of them upfront, rather than having the build process interrupted each time a port wants that input. I know that portupgrade has a batch build option, but unless I'm mistaken, that skips any ports that need interaction to build. ___ 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 With portupgrade give -C to run make make config or -c to run make config-conditional for all tasks before everything else. To skip the config dialogs altogether, specify -DBATCH on the make commandline (-m -DBATCH or -M -DBATCH to portupgrade to append or prepend the -DBATCH to the make commandline). Thanks for your replies! To do the complete reinstall of my ports after upgrading to 8.0, I've elected to use the method documented on the manpage for portmaster. ___ 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: 7.2-STABLE to 8-R
On Tue, Nov 24, 2009 at 10:09:48PM +0100, Roland Smith wrote: I would _strongly_ advise you to make a list of all your current ports, e.g. with 'portmaster -L ports.list', deleting all ports and re-installing the ports labeled as 'leaf ports' and 'root ports' in ports.list. oops! already started! ;) While portmaster/-manager do their best, they just cannot cover all the corner cases, especially since some ports require extra action (e.g. perl!) There is a good chance you'll end up with a big mess like binaries linked to both 7.x and 8.x libraries or ports failing to build for mysterious reasons. Both have happened to me in the past and are a major PITA to fix. As it happens, I noticed installed perl was 5.8 whilst latest is 5.10, so that was built before buildworld. I know what you mean, though. portmanager -u -f -l forces everything to be rebuilt and logs what it did. I then check the output when it's finished and manually rebuild what it can't fix. Not failed me yet, although before doing this I rebuilt portmanager. -- 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: 7.2-STABLE to 8-R
On Tue, Nov 24, 2009 at 05:25:42PM +0100, Pieter de Goeje wrote: On Tuesday 24 November 2009 16:45:14 John wrote: Hello list I've looked high and low for a howto/link showing how to update to 8, to no avail. Is it just a case of the regular buildworld process or are there gotchas because we are crossing major version numbers. You got it right. Just the regular upgrade procedure as documented in /usr/src/UPDATING. The gotcha is that you need to rebuild all ports. If you don't do that you can run in to trouble when you later build a port. I found that usually it is fastest to just take note of which ports you need, delete all existing ports, then after the upgrade reinstall the required ports. Thanks, that's a relief! I looked at the url the other chap posted and it seems to be the same thing although he uses a slightly different syntax and I think he is talking about upgrading in a datacentre, remotely. cheers -- John - comp dot john at googlemail dot com OpenBSD firewall | FreeBSD desktop | Ubuntu Karmic laptop GPG: 0xF08A33C5 ___ 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: 7.2-STABLE to 8-R
On Tuesday 24 November 2009 16:45:14 John wrote: Hello list I've looked high and low for a howto/link showing how to update to 8, to no avail. Is it just a case of the regular buildworld process or are there gotchas because we are crossing major version numbers. You got it right. Just the regular upgrade procedure as documented in /usr/src/UPDATING. The gotcha is that you need to rebuild all ports. If you don't do that you can run in to trouble when you later build a port. I found that usually it is fastest to just take note of which ports you need, delete all existing ports, then after the upgrade reinstall the required ports. -- Pieter de Goeje ___ 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: 7.2-STABLE to 8-R
John wrote: On Tue, Nov 24, 2009 at 05:25:42PM +0100, Pieter de Goeje wrote: On Tuesday 24 November 2009 16:45:14 John wrote: Hello list I've looked high and low for a howto/link showing how to update to 8, to no avail. Is it just a case of the regular buildworld process or are there gotchas because we are crossing major version numbers. You got it right. Just the regular upgrade procedure as documented in /usr/src/UPDATING. The gotcha is that you need to rebuild all ports. If you don't do that you can run in to trouble when you later build a port. I found that usually it is fastest to just take note of which ports you need, delete all existing ports, then after the upgrade reinstall the required ports. Thanks, that's a relief! I looked at the url the other chap posted and it seems to be the same thing although he uses a slightly different syntax and I think he is talking about upgrading in a datacentre, remotely. cheers Just another note or two. If you decide to recompile the ports using portupgrade, portmaster or a similar tool, rather than, as Pieter suggested, deleting them and re-installing, make sure your ports are up to date before upgrading the system. That way you are less likely to run into problems when recompiling them after upgrading. After running mergemaster, do a make delete-old to remove any 7.2 binaries remaining (libraries still in use won't be deleted). I usually do this while still in single user, but I believe it can be done in multi user as well. After upgrading the ports, cd to /usr/src and do a make delete-old-libs. If you upgrade them using portupgrade, portmaster or a similar tool, do the delete-old-libs AFTER all ports are successfully upgraded. The reason for this is that the ports you have installed are still linked to the 7.2 libraries. If you decide to delete all ports, delete them before upgrading the system, then do the delete-old and delete-old-libs before installing any new ports. I usually delete all ports and re-install the essential ones after upgrading, but I've tried the portupgrade approach too, and both have worked well for me. The latter approach is more time consuming, but ensures you have all your ports after the upgrade, while the former approach takes less time and may help get rid of ports you no longer need. Good luck. :) Rolf Nielsen ___ 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: 7.2-STABLE to 8-R
On Tue, Nov 24, 2009 at 06:05:13PM +0100, Rolf G Nielsen wrote: Just another note or two. If you decide to recompile the ports using portupgrade, portmaster or a similar tool, rather than, as Pieter suggested, deleting them and re-installing, make sure your ports are up to date before upgrading the system. That way you are less likely to run into problems when recompiling them after upgrading. After running mergemaster, do a make delete-old to remove any 7.2 binaries remaining (libraries still in use won't be deleted). I usually do this while still in single user, but I believe it can be done in multi user as well. Yes, this is good advice. When crossing even a minor version boundary, I do this, though it might be overkill with minor version changes. make delete-old and make delete-old-libs. I also run make delete-old-dirs and make delete-old-files Regarding ports, I think I'll take the long route. This box is my main machine, my desktop - and so there are a LOT of ports installed. It will be easier to make portmanager rebuild everything in pristine mode. It will take a long time, but I accept this. Before this is done, I run the built-in routines in /usr/ports - clean out */work/* and distfiles. It's a fast machine though - shouldn't take too long. What I'm thinking about now is speeding up make. There are two cores in this CPU. Can I specify -j2 ? Is it one per core or more? I have also specified CPUTYPE?=athlon64 in make.conf. dmesg shows this: CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 6000+ (3006.83-MHz K8-class CPU) Can I specify -j somewhere? man make.conf doesn't cite examples of -j and I'm unsure where (or if it is even desirable) to put it. Any clues? cheers -- John - comp dot john at googlemail dot com OpenBSD firewall | FreeBSD desktop | Ubuntu Karmic laptop GPG: 0xF08A33C5 ___ 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: 7.2-STABLE to 8-R
John wrote: Hello list I've looked high and low for a howto/link showing how to update to 8, to no avail. Is it just a case of the regular buildworld process or are there gotchas because we are crossing major version numbers. You can go the source way or the 'freebsd-update' way. Either way, you will have to rebuild all ports. Detailed instructions are in the Handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html (see 24.2.3) ___ 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: 7.2-STABLE to 8-R
On Tue, 24 Nov 2009, John wrote: Regarding ports, I think I'll take the long route. This box is my main machine, my desktop - and so there are a LOT of ports installed. It will be easier to make portmanager rebuild everything in pristine mode. It will take a long time, but I accept this. Before this is done, I run the built-in routines in /usr/ports - clean out */work/* and distfiles. It's a fast machine though - shouldn't take too long. What I'm thinking about now is speeding up make. There are two cores in this CPU. Can I specify -j2 ? Is it one per core or more? This is now supposed to happen automatically on ports that are safe to build with multiple jobs. Offhand I don't know how to show what's really happening other than something crude like watching top. -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: 7.2-STABLE to 8-R
On Tue, Nov 24, 2009 at 05:40:25PM +, John wrote: Regarding ports, I think I'll take the long route. This box is my main machine, my desktop - and so there are a LOT of ports installed. It will be easier to make portmanager rebuild everything in pristine mode. It will take a long time, but I accept this. Before this is done, I run the built-in routines in /usr/ports - clean out */work/* and distfiles. I would _strongly_ advise you to make a list of all your current ports, e.g. with 'portmaster -L ports.list', deleting all ports and re-installing the ports labeled as 'leaf ports' and 'root ports' in ports.list. While portmaster/-manager do their best, they just cannot cover all the corner cases, especially since some ports require extra action (e.g. perl!) There is a good chance you'll end up with a big mess like binaries linked to both 7.x and 8.x libraries or ports failing to build for mysterious reasons. Both have happened to me in the past and are a major PITA to fix. I've done the complete delete/reinstall run a couple of times now on my desktop with ≈490 ports installed. 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) pgpapl4IhXrES.pgp Description: PGP signature
Re: 7.2-STABLE to 8-R
On Tue 24 Nov 2009 at 13:09:48 PST Roland Smith wrote: On Tue, Nov 24, 2009 at 05:40:25PM +, John wrote: Regarding ports, I think I'll take the long route. This box is my main machine, my desktop - and so there are a LOT of ports installed. It will be easier to make portmanager rebuild everything in pristine mode. It will take a long time, but I accept this. Before this is done, I run the built-in routines in /usr/ports - clean out */work/* and distfiles. I would _strongly_ advise you to make a list of all your current ports, e.g. with 'portmaster -L ports.list', deleting all ports and re-installing the ports labeled as 'leaf ports' and 'root ports' in ports.list. While portmaster/-manager do their best, they just cannot cover all the corner cases, especially since some ports require extra action (e.g. perl!) There is a good chance you'll end up with a big mess like binaries linked to both 7.x and 8.x libraries or ports failing to build for mysterious reasons. Both have happened to me in the past and are a major PITA to fix. I've done the complete delete/reinstall run a couple of times now on my desktop with ???490 ports installed. Can someone remind me once again, when rebuilding all of my ports, what is the trick for avoiding the options dialogs? I'd like to have this run largely unattended. I seem to recall someone describing a method to go through all of them upfront, rather than having the build process interrupted each time a port wants that input. I know that portupgrade has a batch build option, but unless I'm mistaken, that skips any ports that need interaction to build. ___ 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: 7.2-STABLE to 8-R
Charlie Kester wrote: On Tue 24 Nov 2009 at 13:09:48 PST Roland Smith wrote: On Tue, Nov 24, 2009 at 05:40:25PM +, John wrote: Regarding ports, I think I'll take the long route. This box is my main machine, my desktop - and so there are a LOT of ports installed. It will be easier to make portmanager rebuild everything in pristine mode. It will take a long time, but I accept this. Before this is done, I run the built-in routines in /usr/ports - clean out */work/* and distfiles. I would _strongly_ advise you to make a list of all your current ports, e.g. with 'portmaster -L ports.list', deleting all ports and re-installing the ports labeled as 'leaf ports' and 'root ports' in ports.list. While portmaster/-manager do their best, they just cannot cover all the corner cases, especially since some ports require extra action (e.g. perl!) There is a good chance you'll end up with a big mess like binaries linked to both 7.x and 8.x libraries or ports failing to build for mysterious reasons. Both have happened to me in the past and are a major PITA to fix. I've done the complete delete/reinstall run a couple of times now on my desktop with ???490 ports installed. Can someone remind me once again, when rebuilding all of my ports, what is the trick for avoiding the options dialogs? I'd like to have this run largely unattended. I seem to recall someone describing a method to go through all of them upfront, rather than having the build process interrupted each time a port wants that input. I know that portupgrade has a batch build option, but unless I'm mistaken, that skips any ports that need interaction to build. ___ 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 With portupgrade give -C to run make make config or -c to run make config-conditional for all tasks before everything else. To skip the config dialogs altogether, specify -DBATCH on the make commandline (-m -DBATCH or -M -DBATCH to portupgrade to append or prepend the -DBATCH to the make commandline). Cheers, Rolf Nielsen ___ 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: 7.2-STABLE to 8-R
On Tue, Nov 24, 2009 at 01:18:51PM -0800, Charlie Kester wrote: On Tue 24 Nov 2009 at 13:09:48 PST Roland Smith wrote: On Tue, Nov 24, 2009 at 05:40:25PM +, John wrote: Regarding ports, I think I'll take the long route. This box is my main machine, my desktop - and so there are a LOT of ports installed. It will be easier to make portmanager rebuild everything in pristine mode. It will take a long time, but I accept this. Before this is done, I run the built-in routines in /usr/ports - clean out */work/* and distfiles. I would _strongly_ advise you to make a list of all your current ports, e.g. with 'portmaster -L ports.list', deleting all ports and re-installing the ports labeled as 'leaf ports' and 'root ports' in ports.list. While portmaster/-manager do their best, they just cannot cover all the corner cases, especially since some ports require extra action (e.g. perl!) There is a good chance you'll end up with a big mess like binaries linked to both 7.x and 8.x libraries or ports failing to build for mysterious reasons. Both have happened to me in the past and are a major PITA to fix. I've done the complete delete/reinstall run a couple of times now on my desktop with ???490 ports installed. Can someone remind me once again, when rebuilding all of my ports, what is the trick for avoiding the options dialogs? I'd like to have this run largely unattended. I seem to recall someone describing a method to go through all of them upfront, rather than having the build process interrupted each time a port wants that input. Use 'make config-recursive' to go through all the option dialogs first. See the ports(7) manpage for other make targets and variables that influence which/how ports are built. I know that portupgrade has a batch build option, but unless I'm mistaken, that skips any ports that need interaction to build. ___ 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 -- Insert your favourite quote here. Erik Trulsson ertr1...@student.uu.se ___ 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
