Re: Problem upgrading from 8.1-8.2, ZFS as root filesystem
On 27 February 2011 21:29, Scott Ballantyne boyva...@gmail.com wrote: On Sun, Feb 27, 2011 at 4:04 PM, Adam Vande More amvandem...@gmail.comwrote: On Sun, Feb 27, 2011 at 2:36 PM, Scott Ballantyne boyva...@gmail.comwrote: ===sys/boot/i386/zfsloader (install) cp zfsloader.sym zfsloader.bin cp:No such file or directory *** Error code 1 Stop in /usr/src/sys/boot/i386/zfsloader *** Error code 1 Stop in /usr/src/sys/boot/i386 Any suggestions would be *very* appreciated! Thanks, Scott You can follow the intructions for building the loader which I believe are in the wiki or set LOADER_ZFS_SUPPORT=YES in /etc/src.conf prior to upgrade. Thanks Adam, but it still comes to a screaming stop with that set. ___ 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 mines in make.conf not src and it built fine ___ 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: Upgrading 7.1 to 7.3, use 7.2 as a safe step?
My upgrades were a success. I upgraded 3 machines: 1. 7.1 - 7.4 2. 8.0 - 8.1 3. 7.1 - 7.3 - 7.4 I don't use STABLE, but rather e.g. RELENG_7_4 ___ 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
Problem upgrading from 8.1-8.2, ZFS as root filesystem
Hi, Doing a source upgrade from 8.1-8.2, all went well up to the installworld step: Reboot into single user mode: mount -u ./ zfs mount -a cd /usr/src make installworld It goes fine up to this point: (copying by hand) ===sys/boot/i386/zfsloader (install) cp zfsloader.sym zfsloader.bin cp:No such file or directory *** Error code 1 Stop in /usr/src/sys/boot/i386/zfsloader *** Error code 1 Stop in /usr/src/sys/boot/i386 Any suggestions would be *very* appreciated! Thanks, Scott -- boyva...@gmail.com ___ 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: Problem upgrading from 8.1-8.2, ZFS as root filesystem
On Sun, Feb 27, 2011 at 2:36 PM, Scott Ballantyne boyva...@gmail.comwrote: ===sys/boot/i386/zfsloader (install) cp zfsloader.sym zfsloader.bin cp:No such file or directory *** Error code 1 Stop in /usr/src/sys/boot/i386/zfsloader *** Error code 1 Stop in /usr/src/sys/boot/i386 Any suggestions would be *very* appreciated! Thanks, Scott You can follow the intructions for building the loader which I believe are in the wiki or set LOADER_ZFS_SUPPORT=YES in /etc/src.conf prior to upgrade. -- 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: Problem upgrading from 8.1-8.2, ZFS as root filesystem
On Sun, Feb 27, 2011 at 4:04 PM, Adam Vande More amvandem...@gmail.comwrote: On Sun, Feb 27, 2011 at 2:36 PM, Scott Ballantyne boyva...@gmail.comwrote: ===sys/boot/i386/zfsloader (install) cp zfsloader.sym zfsloader.bin cp:No such file or directory *** Error code 1 Stop in /usr/src/sys/boot/i386/zfsloader *** Error code 1 Stop in /usr/src/sys/boot/i386 Any suggestions would be *very* appreciated! Thanks, Scott You can follow the intructions for building the loader which I believe are in the wiki or set LOADER_ZFS_SUPPORT=YES in /etc/src.conf prior to upgrade. Thanks Adam, but it still comes to a screaming stop with that set. ___ 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
Upgrading 7.1 to 7.3, use 7.2 as a safe step?
For me, time can be spared, but errors should be avoided at all costs. I have upgraded FreeBSD before, for example 7.0 - 7.1. I use the buildworld/buildkernel procedure. I now have a 7.1 system. Should I upgrade to 7.2 and then to 7.3, or is it safe to go directly from 7.1 to 7.3? - Nerius P.S. I will also be upgrading 8.0 to 8.2 on another system, and assume the answer you give can be applied there as well. ___ 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: Upgrading 7.1 to 7.3, use 7.2 as a safe step?
On Feb 25, 2011, at 1:39 PM, Nerius Landys wrote: For me, time can be spared, but errors should be avoided at all costs. I have upgraded FreeBSD before, for example 7.0 - 7.1. I use the buildworld/buildkernel procedure. I now have a 7.1 system. Should I upgrade to 7.2 and then to 7.3, or is it safe to go directly from 7.1 to 7.3? You shouldn't run into any unusual issues. Note that more care is needed if you are doing a major version bump-- ie, you should go to 7.4 - 8.0 - 8.2. Regards, -- -Chuck ___ 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: Upgrading 7.1 to 7.3, use 7.2 as a safe step?
--On February 25, 2011 1:39:47 PM -0800 Nerius Landys nlan...@gmail.com wrote: For me, time can be spared, but errors should be avoided at all costs. I have upgraded FreeBSD before, for example 7.0 - 7.1. I use the buildworld/buildkernel procedure. I now have a 7.1 system. Should I upgrade to 7.2 and then to 7.3, or is it safe to go directly from 7.1 to 7.3? I have upgraded several times across major versions without any problems. (5.x to 6.x, 6.x to 7.x). Each time I simply changed the supfile to the version I wanted to upgrade to, fetched the files and rebuilt world and kernel. After those are complete, I run a portupgrade -a to sync all the ports with the new sources. Note that this is *not* the way to do it if you absolutely must avoid problems, however slight the risk. -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead. Thomas Jefferson There are some ideas so wrong that only a very intelligent person could believe in them. George Orwell ___ 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
upgrading apr from v0 to v1 via portupgrade?
I recently moved my server to a new box and in the process of doing that, I upgraded from FreeBSD 7.3 to 8.1. When I say I moved, I mean I backed up all my personal data (databases, config values, etc.), made a list of all packages, and installed an identical box with the same pacakges. Recently I noticed that somehow I am on apr-0.9.19.0.9.19. On my old box, I was on apr-ipv6-devrandom-gdbm-db47-1.4.2.1.3.10. I didn't make that choice deliberarely, somehow when I installed all the pacakges, apr-0 was installed instead of apr-1. Normally I wouldn't care, but apr-0 has had an unpatched security advisory for a few weeks now, so I would like to upgrade all my packages that use apr-0 to apr-1. I use portupgrade, how can I do this? ___ 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: upgrading apr from v0 to v1 via portupgrade?
On 24 February 2011 11:09, Aleksandr Miroslav alexmiros...@gmail.com wrote: I recently moved my server to a new box and in the process of doing that, I upgraded from FreeBSD 7.3 to 8.1. When I say I moved, I mean I backed up all my personal data (databases, config values, etc.), made a list of all packages, and installed an identical box with the same pacakges. Recently I noticed that somehow I am on apr-0.9.19.0.9.19. On my old box, I was on apr-ipv6-devrandom-gdbm-db47-1.4.2.1.3.10. I didn't make that choice deliberarely, somehow when I installed all the pacakges, apr-0 was installed instead of apr-1. Normally I wouldn't care, but apr-0 has had an unpatched security advisory for a few weeks now, so I would like to upgrade all my packages that use apr-0 to apr-1. I use portupgrade, how can I do this? The general (untested) notion would be: portupgrade -o devel/apr1 apr-0 then portupgrade -frx apr apr (which hopefully will rebuild everything depending upon apr without rebuilding apr twice) -- -- ___ 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: upgrading apr from v0 to v1 via portupgrade?
On Thu, 24 Feb 2011, Aleksandr Miroslav wrote: Recently I noticed that somehow I am on apr-0.9.19.0.9.19. On my old box, I was on apr-ipv6-devrandom-gdbm-db47-1.4.2.1.3.10. See the 20100518 entry in /usr/ports/UPDATING. Well, the apr one, anyway. ___ 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
Upgrading ImageMagick fails 2 of 48 tests
I'm trying to upgrade ImageMagick from 6.6.5.10 to 6.6.6-10 on FreeBSD 8.1-RELEASE but 2 tests fail with segmentation faults - validate-formats-in-memory.sh and validate-formats-on-disk.sh. I'll stick with 6.6.5.10 for now but would welcome suggestions on how to deal with this problem = ImageMagick 6.6.6: ./test-suite.log = 2 of 48 tests failed. .. contents:: :depth: 2egmentation fault FAIL: tests/validate-formats-in-memory.sh (exit: 139) = Version: ImageMagick 6.6.6-10 2011-02-14 Q16 http://www.imagemagick.org Copyright: Copyright (C) 1999-2011 ImageMagick Studio LLC ImageMagick Validation Suite (FormatsInMemory) validate image formats in memory: test 0: ART/Undefined/TrueColor/8-bits... pass. test 1: ART/Undefined/TrueColorMatte/8-bits... pass. test 2: ART/Undefined/Grayscale/8-bits... pass. [Snip lots of passes] test 291: JPEG/Undefined/PaletteMatte/8-bits... pass. test 292: JPEG/Undefined/PaletteBilevelMatte/8-bits... pass. test 293: JPEG/Undefined/Bilevel/1-bits... pass. teSegmentation fault FAIL: tests/validate-formats-on-disk.sh (exit: 139) === Version: ImageMagick 6.6.6-10 2011-02-14 Q16 http://www.imagemagick.org Copyright: Copyright (C) 1999-2011 ImageMagick Studio LLC ImageMagick Validation Suite (FormatsOnDisk) validate image formats on disk: test 0: ART/Undefined/TrueColor/8-bits... pass. test 1: ART/Undefined/TrueColorMatte/8-bits... pass. test 2: ART/Undefined/Grayscale/8-bits... pass. [Snip lots more passes] test 291: JPEG/Undefined/PaletteMatte/8-bits... pass. test 292: JPEG/Undefined/PaletteBilevelMatte/8-bits... pass. test 293: JPEG/Undefined/Bilevel/1-bits... pass. test 2Segmentation fault -- Mike Clarke ___ 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: Issue upgrading to 7.4, looking for guidance
I ran into a similar issue upgrading from 7.2 to 7.3. Here's the thread where I worked it out; it might be helpful in your case: http://lists.freebsd.org/pipermail/freebsd-questions/2010-July/218443.html My eventual solution was here, if you don't want to read through the whole thread: http://lists.freebsd.org/pipermail/freebsd-questions/2010-July/218884.html On Wed, Jan 26, 2011 at 6:36 PM, Keith Seyffarth w...@weif.net wrote: I recently was having problems with Firefox crashing, which appear to be related to a requirement for semaphore support for Firefox after the upgrade to the new version of GTK. Anyway, this left me with a 7.4 kernel and a 7.2 world. Which I understand is supposed to work. However, this broke CUPS for printing, and I need to be able to print to pdf. This error is generated if I try to build cups, or when cups tries to load on startup: /libexec/ld-elf.so.1: ./mantohtml: invalid PT_PHDR From looking around on-line, it looks like somewhere between 7.2 and 7.4 there was an incompatibility that causes this error in a number of places (printing, samba, etc.) So, it looks like I need to upgrade the rest of the way. But I can't get the upgrade to work. I thought this was where to start: # freebsd-update -r 7.4-RELEASE upgrade Looking up update.FreeBSD.org mirrors... 4 mirrors found. Fetching public key from update5.FreeBSD.org... failed. Fetching public key from update4.FreeBSD.org... failed. Fetching public key from update2.FreeBSD.org... failed. Fetching public key from update3.FreeBSD.org... failed. No mirrors remaining, giving up. So I ran uname -a to find that this is 7.4-PRERELEASE FreeBSD janet.weif.net 7.4-PRERELEASE FreeBSD 7.4-PRERELEASE #0: Thu Jan 20 19:39:15 MST 2011 w...@janet.weif.net:/usr/obj/usr/src/sys/JANET i386 so I tried this: # freebsd-update -r 7.4-PRERELEASE upgrade freebsd-update: Cannot upgrade from 7.4-PRERELEASE to itself so, um, what do I need to do to address this error: /libexec/ld-elf.so.1: ./mantohtml: invalid PT_PHDR Keith S. ___ 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: Issue upgrading to 7.4, looking for guidance
David, I ran into a similar issue upgrading from 7.2 to 7.3. Here's the thread where I worked it out; it might be helpful in your case: http://lists.freebsd.org/pipermail/freebsd-questions/2010-July/218443.html My eventual solution was here, if you don't want to read through the whole thread: http://lists.freebsd.org/pipermail/freebsd-questions/2010-July/218884.html I ended up getting instructions from a friend n manually running # make buildworld # mergemaster -p # make installworld # mergemaster -i to get the world upgraded to 7.4-PRERELEASE. After this a bunch of removing, reinstalling, and upgrading of ports was necessary, but everything appears to be working now. Of course, not having a FreeBSD CD for any version of FreeBSD would make copying a file from the CD rather difficult... ;) Keith S. ___ 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: Issue upgrading to 7.4, looking for guidance
For me I used a quick and dirty solution for upgrade 1) build a machine (or a virtual one...) with the freebsd version you want, for example=8.2 cvsup the kernel in /usr/src 2) export KERNCONF=xx the name of the kernel config file you want to build 3) cd /usr/src;make buildworld buildkernel 4) mkdir /tmp/dist 5) export DESTDIR=/tmp/dist 6) make installworld installkernel 7) (cd /tmp/dist;tar cvzf - * ) /tmp/newsystem.tar.gz 8) move the newsystem.tar.gz to the machine you want to upgrade 9) /rescue/tar -xpvf newsystem.tar.gz -C / the system will not respond to comands any more because of rewrite of almost all libs... so the solution is fastboot When the system comes up, it shows the release you built from this way you can go from 7.0 to 8.2 in one single step. for me it worked in internet all times but, you are warned: use at you own risk... Sergio ___ 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
Issue upgrading to 7.4, looking for guidance
I recently was having problems with Firefox crashing, which appear to be related to a requirement for semaphore support for Firefox after the upgrade to the new version of GTK. Anyway, this left me with a 7.4 kernel and a 7.2 world. Which I understand is supposed to work. However, this broke CUPS for printing, and I need to be able to print to pdf. This error is generated if I try to build cups, or when cups tries to load on startup: /libexec/ld-elf.so.1: ./mantohtml: invalid PT_PHDR From looking around on-line, it looks like somewhere between 7.2 and 7.4 there was an incompatibility that causes this error in a number of places (printing, samba, etc.) So, it looks like I need to upgrade the rest of the way. But I can't get the upgrade to work. I thought this was where to start: # freebsd-update -r 7.4-RELEASE upgrade Looking up update.FreeBSD.org mirrors... 4 mirrors found. Fetching public key from update5.FreeBSD.org... failed. Fetching public key from update4.FreeBSD.org... failed. Fetching public key from update2.FreeBSD.org... failed. Fetching public key from update3.FreeBSD.org... failed. No mirrors remaining, giving up. So I ran uname -a to find that this is 7.4-PRERELEASE FreeBSD janet.weif.net 7.4-PRERELEASE FreeBSD 7.4-PRERELEASE #0: Thu Jan 20 19:39:15 MST 2011 w...@janet.weif.net:/usr/obj/usr/src/sys/JANET i386 so I tried this: # freebsd-update -r 7.4-PRERELEASE upgrade freebsd-update: Cannot upgrade from 7.4-PRERELEASE to itself so, um, what do I need to do to address this error: /libexec/ld-elf.so.1: ./mantohtml: invalid PT_PHDR Keith S. ___ 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: upgrading a dozen of servers from 7.0 to 8.1
Hello. Thank you and everyone who answered. I will share my experinece to the list when I walk my way throught the upgrade ) 21.01.2011, 17:13, Odhiambo Washington odhia...@gmail.com: On Fri, Jan 21, 2011 at 4:54 PM, Radomskiy Yuriy yuriu...@yandex.ua; wrote: Hello! I have around 15 servers running FreeBSD 7.0 across the country. I would like to upgrade them to 7.3 or even 8.1 using binary updates. They are primary mail servers all running apache-2.0 + php5-5.2.10, mysql-server-5.1, exim-4.69, dovecot-1.1 They are almost identical - they were identical a couple of years ago, but now they have some minor differences (soft, settings, scripts) Hardware is all the same. All the servers are in production. The steps I have to do and the questions about them i have: 1. update all soft to current versions (including change of config files) apache - goto v2.2 php - goto v5.3 mysql - stick with 5.1 exim - goto 4.73 dovecot - goto 1.2.16 q's: how can upgrading to apache 2.2 + php5.3 be done with minimal downtime? portupgrade -o lang/php52 lang/php5 That will upgrade your php from 5.2.10 to 5.2.17. Please stick with php-5.2.x unless you are sure php-5.3 will not break some web apps you are running. upgrade php-extensions the same way. can i upgrade or is it better to rebuild it from the scratch (because of major version changes)? You can upgrade. Please follow the instructions from http://people.freebsd.org/~rse/upgrade/freebsd-upgrade-7x-8x.txthttp://people.freebsd.org/%7Erse/upgrade/freebsd-upgrade-7x-8x.txt Just note one thing I noticed while upgrading my servers: s/compat7x-`uname -m`-7.2.702000.200906.1.tbz/compat7x-`uname -m`-7.3.703000.201008.tbz/g 2. do a binary upgrade of OS according to handbook http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html You can do that, but I personally prefer http://people.freebsd.org/~rse/upgrade/freebsd-upgrade-7x-8x.txthttp://people.freebsd.org/%7Erse/upgrade/freebsd-upgrade-7x-8x.txt. I have never used freebsd-update on any system I run, but that is out of choice, not any other reason! 3. rebuil all the software again portupgrade -af If you follow http://people.freebsd.org/~rse/upgrade/freebsd-upgrade-7x-8x.txthttp://people.freebsd.org/%7Erse/upgrade/freebsd-upgrade-7x-8x.txt, there will not be any urgency in doing portupgrade -af. .. ___ 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
upgrading a dozen of servers from 7.0 to 8.1
Hello! I have around 15 servers running FreeBSD 7.0 across the country. I would like to upgrade them to 7.3 or even 8.1 using binary updates. They are primary mail servers all running apache-2.0 + php5-5.2.10, mysql-server-5.1, exim-4.69, dovecot-1.1 They are almost identical - they were identical a couple of years ago, but now they have some minor differences (soft, settings, scripts) Hardware is all the same. All the servers are in production. The steps I have to do and the questions about them i have: 1. update all soft to current versions (including change of config files) apache - goto v2.2 php - goto v5.3 mysql - stick with 5.1 exim - goto 4.73 dovecot - goto 1.2.16 q's: how can upgrading to apache 2.2 + php5.3 be done with minimal downtime? can i upgrade or is it better to rebuild it from the scratch (because of major version changes)? 2. do a binary upgrade of OS according to handbook http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html 3. rebuil all the software again portupgrade -af I have two scenarios for this: I. 1. restore a server from a backup on a dedicated machine. 2. do all the upgrade procedures on this dedicated server. 3. clone this upgraded server to the original server. 4. Repeat this procedure for each server. Advantages: - almost garanteed reliability. Disadvantages: - need to sync data from the last backup with current one. - takes very long time. II. 1. restore one server from backup on a dedicated machine. 2. do all the upgrade procedures on this restored server. 3. write some sort of script that does the upgrate (or makes it easier). 4. upgrate all the servers (since they are almost identical) one at a time. Advantages: - should be faster Disadvantages: - something might go wrong on some particular server(s). Which method would you sudgest? Is there any other method or maybe enhancements ones to do the upgrade? How can it be used that all servers are almost identical? How can the process be automated? Should i be looking into building binary packages of required software and redistributing them to the servers instead of building them from the ports tree (as it is done now)? -- Yuriy. ___ 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: upgrading a dozen of servers from 7.0 to 8.1
On Fri, Jan 21, 2011 at 4:54 PM, Radomskiy Yuriy yuriu...@yandex.ua wrote: Hello! I have around 15 servers running FreeBSD 7.0 across the country. I would like to upgrade them to 7.3 or even 8.1 using binary updates. They are primary mail servers all running apache-2.0 + php5-5.2.10, mysql-server-5.1, exim-4.69, dovecot-1.1 They are almost identical - they were identical a couple of years ago, but now they have some minor differences (soft, settings, scripts) Hardware is all the same. All the servers are in production. The steps I have to do and the questions about them i have: 1. update all soft to current versions (including change of config files) apache - goto v2.2 php - goto v5.3 mysql - stick with 5.1 exim - goto 4.73 dovecot - goto 1.2.16 q's: how can upgrading to apache 2.2 + php5.3 be done with minimal downtime? portupgrade -o lang/php52 lang/php5 That will upgrade your php from 5.2.10 to 5.2.17. Please stick with php-5.2.x unless you are sure php-5.3 will not break some web apps you are running. upgrade php-extensions the same way. can i upgrade or is it better to rebuild it from the scratch (because of major version changes)? You can upgrade. Please follow the instructions from http://people.freebsd.org/~rse/upgrade/freebsd-upgrade-7x-8x.txthttp://people.freebsd.org/%7Erse/upgrade/freebsd-upgrade-7x-8x.txt Just note one thing I noticed while upgrading my servers: s/compat7x-`uname -m`-7.2.702000.200906.1.tbz/compat7x-`uname -m`-7.3.703000.201008.tbz/g 2. do a binary upgrade of OS according to handbook http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html You can do that, but I personally prefer http://people.freebsd.org/~rse/upgrade/freebsd-upgrade-7x-8x.txthttp://people.freebsd.org/%7Erse/upgrade/freebsd-upgrade-7x-8x.txt. I have never used freebsd-update on any system I run, but that is out of choice, not any other reason! 3. rebuil all the software again portupgrade -af If you follow http://people.freebsd.org/~rse/upgrade/freebsd-upgrade-7x-8x.txthttp://people.freebsd.org/%7Erse/upgrade/freebsd-upgrade-7x-8x.txt, there will not be any urgency in doing portupgrade -af. I have two scenarios for this: I. 1. restore a server from a backup on a dedicated machine. 2. do all the upgrade procedures on this dedicated server. 3. clone this upgraded server to the original server. 4. Repeat this procedure for each server. Advantages: - almost garanteed reliability. Disadvantages: - need to sync data from the last backup with current one. - takes very long time. Too tedious!! II. 1. restore one server from backup on a dedicated machine. 2. do all the upgrade procedures on this restored server. 3. write some sort of script that does the upgrate (or makes it easier). 4. upgrate all the servers (since they are almost identical) one at a time. Advantages: - should be faster Disadvantages: - something might go wrong on some particular server(s). Too tedious!! Which method would you sudgest? As I suggested above!! Is there any other method or maybe enhancements ones to do the upgrade? ?? How can it be used that all servers are almost identical? Using RSE's methods, your servers will remain as identical as they are now. Only you will end up running FreeBSD 8.x :-) How can the process be automated? Unattended? Never for a server!!! Scripted?? By RSE!! Should i be looking into building binary packages of required software and redistributing them to the servers instead of building them from the ports tree (as it is done now)? No. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Damn!! ___ 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: upgrading a dozen of servers from 7.0 to 8.1
On 21/01/2011 14:54, Radomskiy Yuriy wrote: how can upgrading to apache 2.2 + php5.3 be done with minimal downtime? That's the more important question. I think that upgrading the configuration of your software will take more time than upgrading FreeBSD. For example: apache22 port has a different (and better) configuration file structure than 2.0, and some web application still don't work with php 5.3. If you know reasonably good enough how FreeBSD works, I don't think you will have trouble with that part of the upgrade (especially if you have a remote KVM or other console access). ___ 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: Upgrading from FreeBSD 4.10 to 8.1?
On 6 January 2011 16:40, Mike Tancsa m...@sentex.net wrote: On 1/6/2011 11:27 AM, Robert Huff wrote: patrick writes: I know this is a bit crazy, but is there any opinion as to whether a binary upgrade using an 8.1 CD would work to upgrade a system running 4.10? Normally I would want to do a fresh install, but it's at a remote client site where it's not going to be easy to do it that way, and I'm going to need to guide someone less experienced through the install/upgrade process. While this may not be an option, my preference would be to 1) build a new machine, 2) install 8.1, 3) install the apps and data, 4) test thoroughly, then 5) ship the result to the remote location. Anything else is likely to be too painful for words. How old is the hardware as well? If its running 4.x, something is going to die on it sooner than later. I agree with the above. Send a new box or at the very least a new disk with 8.2 on it. Then, just mount the old 4.x disk and copy over the user data. ---Mike ___ 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 I have done such upgrades in the past but they are very high risk, so the chances are you will incur some prolonged downtime, and probably have to go to site anyway. It would be much easier to build a new system disk, install whatever ports you need and copy across anything else from the live system, then install the new disk to the box (or an entire new box) ___ 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: Upgrading from FreeBSD 4.10 to 8.1?
On Thu, Jan 06, 2011 at 07:45:28AM -0800, patrick wrote: I know this is a bit crazy, but is there any opinion as to whether a binary upgrade using an 8.1 CD would work to upgrade a system running 4.10? Normally I would want to do a fresh install, but it's at a remote client site where it's not going to be easy to do it that way, and I'm going to need to guide someone less experienced through the install/upgrade process. An upgrade using a CD wouldn't work as the filesystem changed from UFS1 to UFS2 betweeen 4 and 5. I'm afraid as others have indicated, you'll have to visit the site or ship a preconfigured box to the site. 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: Upgrading from FreeBSD 4.10 to 8.1?
On Fri, Jan 07, 2011 at 12:02:59PM +, Frank Shute wrote: On Thu, Jan 06, 2011 at 07:45:28AM -0800, patrick wrote: I know this is a bit crazy, but is there any opinion as to whether a binary upgrade using an 8.1 CD would work to upgrade a system running 4.10? Normally I would want to do a fresh install, but it's at a remote client site where it's not going to be easy to do it that way, and I'm going to need to guide someone less experienced through the install/upgrade process. An upgrade using a CD wouldn't work as the filesystem changed from UFS1 to UFS2 betweeen 4 and 5. That by itself should not be a showstopper, since newer FreeBSD releases (incl. 8.1) still support UFS1 and can run perfectly fine on it. Although it is generally a good idea to use UFS2 rather than UFS1 with FreeBSD 5+ it is certainly not necessary. -- 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
Re: Upgrading from FreeBSD 4.10 to 8.1?
On Fri, Jan 07, 2011 at 03:05:14PM +0100, Erik Trulsson wrote: On Fri, Jan 07, 2011 at 12:02:59PM +, Frank Shute wrote: On Thu, Jan 06, 2011 at 07:45:28AM -0800, patrick wrote: I know this is a bit crazy, but is there any opinion as to whether a binary upgrade using an 8.1 CD would work to upgrade a system running 4.10? Normally I would want to do a fresh install, but it's at a remote client site where it's not going to be easy to do it that way, and I'm going to need to guide someone less experienced through the install/upgrade process. An upgrade using a CD wouldn't work as the filesystem changed from UFS1 to UFS2 betweeen 4 and 5. That by itself should not be a showstopper, since newer FreeBSD releases (incl. 8.1) still support UFS1 and can run perfectly fine on it. Although it is generally a good idea to use UFS2 rather than UFS1 with FreeBSD 5+ it is certainly not necessary. The thing to do is create the UFS2 new system and use it to read the stuff you need from the old UFS1 system/disk. Then just use the new disk. jerry -- 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 ___ 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: Upgrading from FreeBSD 4.10 to 8.1?
Sent from my iPhone On Jan 7, 2011, at 7:07 AM, Jerry McAllister jerr...@msu.edu wrote: On Fri, Jan 07, 2011 at 03:05:14PM +0100, Erik Trulsson wrote: On Fri, Jan 07, 2011 at 12:02:59PM +, Frank Shute wrote: On Thu, Jan 06, 2011 at 07:45:28AM -0800, patrick wrote: I know this is a bit crazy, but is there any opinion as to whether a binary upgrade using an 8.1 CD would work to upgrade a system running 4.10? Normally I would want to do a fresh install, but it's at a remote client site where it's not going to be easy to do it that way, and I'm going to need to guide someone less experienced through the install/upgrade process. An upgrade using a CD wouldn't work as the filesystem changed from UFS1 to UFS2 betweeen 4 and 5. That by itself should not be a showstopper, since newer FreeBSD releases (incl. 8.1) still support UFS1 and can run perfectly fine on it. Although it is generally a good idea to use UFS2 rather than UFS1 with FreeBSD 5+ it is certainly not necessary. The thing to do is create the UFS2 new system and use it to read the stuff you need from the old UFS1 system/disk. Then just use the new disk. Maybe I'm just imagining things, but I somehow recall that some guru had posted a technique for converting UFS1 to UFS2 by way of dump/restore while booted from a live distro. Was I dreaming? -- Cheers, Devin jerry -- 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 ___ 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: Upgrading from FreeBSD 4.10 to 8.1?
On Fri, Jan 07, 2011 at 07:50:20AM -0800, Devin Teske wrote: Sent from my iPhone On Jan 7, 2011, at 7:07 AM, Jerry McAllister jerr...@msu.edu wrote: On Fri, Jan 07, 2011 at 03:05:14PM +0100, Erik Trulsson wrote: On Fri, Jan 07, 2011 at 12:02:59PM +, Frank Shute wrote: On Thu, Jan 06, 2011 at 07:45:28AM -0800, patrick wrote: I know this is a bit crazy, but is there any opinion as to whether a binary upgrade using an 8.1 CD would work to upgrade a system running 4.10? Normally I would want to do a fresh install, but it's at a remote client site where it's not going to be easy to do it that way, and I'm going to need to guide someone less experienced through the install/upgrade process. An upgrade using a CD wouldn't work as the filesystem changed from UFS1 to UFS2 betweeen 4 and 5. That by itself should not be a showstopper, since newer FreeBSD releases (incl. 8.1) still support UFS1 and can run perfectly fine on it. Although it is generally a good idea to use UFS2 rather than UFS1 with FreeBSD 5+ it is certainly not necessary. The thing to do is create the UFS2 new system and use it to read the stuff you need from the old UFS1 system/disk. Then just use the new disk. Maybe I'm just imagining things, but I somehow recall that some guru had posted a technique for converting UFS1 to UFS2 by way of dump/restore while booted from a live distro. Was I dreaming? Well, that should be easy.You just have a new disk, slice, partition and newfs it with a new UFS2 system. Then dump the old partitions and restore them on the new partitions.It is still a matter of creating a new system with new space. You could do it to a spare machine and then once it is all built, do the same back to the old machine and it would all be up-to-date. The new one would be nice and clean then too. jerry -- Cheers, Devin jerry -- 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 ___ 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 ___ 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
Upgrading from FreeBSD 4.10 to 8.1?
I know this is a bit crazy, but is there any opinion as to whether a binary upgrade using an 8.1 CD would work to upgrade a system running 4.10? Normally I would want to do a fresh install, but it's at a remote client site where it's not going to be easy to do it that way, and I'm going to need to guide someone less experienced through the install/upgrade process. ___ 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: Upgrading from FreeBSD 4.10 to 8.1?
On Thu, Jan 06, 2011 at 07:45:28AM -0800, patrick wrote: I know this is a bit crazy, but is there any opinion as to whether a binary upgrade using an 8.1 CD would work to upgrade a system running 4.10? Normally I would want to do a fresh install, but it's at a remote client site where it's not going to be easy to do it that way, and I'm going to need to guide someone less experienced through the install/upgrade process. It might work. But, I think you would save a lot of headache and time to just do a new scratch install of 8.xx (8.2 should be here soon). First, make a thorough list of everything that is installed on the old machine.List info from disk slice[s] and partitions and other configuration items. Then make copies (backups) of all user data and anything that needs to be kept from the old system and is not being newly installed from ports and such. Now would be a good/great time to replace/upgrade the hard disk or install a second (third..., etc) disk. Rethink the partitioning according to current usage and disk sizes. Then just build a new machine, configure it appropriately, install the ports and any other possible software - latest versions. Then restore all the user data that is needed on the new system and you should be ready to go. (Some old data may better be left in archive) jerry ___ 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
Upgrading from FreeBSD 4.10 to 8.1?
patrick writes: I know this is a bit crazy, but is there any opinion as to whether a binary upgrade using an 8.1 CD would work to upgrade a system running 4.10? Normally I would want to do a fresh install, but it's at a remote client site where it's not going to be easy to do it that way, and I'm going to need to guide someone less experienced through the install/upgrade process. While this may not be an option, my preference would be to 1) build a new machine, 2) install 8.1, 3) install the apps and data, 4) test thoroughly, then 5) ship the result to the remote location. Anything else is likely to be too painful for words. Robert Huff ___ 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: Upgrading from FreeBSD 4.10 to 8.1?
On 1/6/2011 11:27 AM, Robert Huff wrote: patrick writes: I know this is a bit crazy, but is there any opinion as to whether a binary upgrade using an 8.1 CD would work to upgrade a system running 4.10? Normally I would want to do a fresh install, but it's at a remote client site where it's not going to be easy to do it that way, and I'm going to need to guide someone less experienced through the install/upgrade process. While this may not be an option, my preference would be to 1) build a new machine, 2) install 8.1, 3) install the apps and data, 4) test thoroughly, then 5) ship the result to the remote location. Anything else is likely to be too painful for words. How old is the hardware as well? If its running 4.x, something is going to die on it sooner than later. I agree with the above. Send a new box or at the very least a new disk with 8.2 on it. Then, just mount the old 4.x disk and copy over the user data. ---Mike ___ 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
Upgrading from FreeBSD 4.10 to 8.1?
I know I'll take heat from everyone else who responded saying to effectively ship a new box. But maybe this user has significant costs involved with that. Along with any other reasons... v4 to v8 can be done. I've done it entirely live over the net. Nothing crazy about it. The basic idea is that there are too many changes and tools involved to fart around with build/install world, mergemaster, CD's, sysinstall, etc. And they're just not aware of such a jump. And you can't trust the idiots on the other end to get it right even if they would work. You are the SA, free your mind. To the initiate, it would be harrowing. To the seasoned SA, it's logical cake. So backup your entire 4.x box over the wire, there will be no return. Go find a box and install v8 however you want it. If you fail, this one goes to the shipper asap. You can use a vm but that will take longer to ship. You are very wise to also install a v4 box and overlay your backup on it first for testing the entire process. If you failed to heed SA wisdom about separating / /usr /usr/local /var /home /boot, free space, etc on the original v4 box, your life will be much harder. But if you have a ton of unpartitioned free space on it, you can fix that one at a time too ;) Be very aware of boot sectors, loaders, partitions, slices, fstab, sizes, /dev, ifconfig, packet filters, kernel config, etc. That kills most people. Also, since all your apps will be pristine v8 vers, you need to sort out their use of the old data and config. If you have space, rsync -Haxi upload your v8 mountpoints to separate staging dirs on the v4 box. It helps narrow your power fail window :) Get on the v4 box. If you've got console, re boot -s. If not, take it down till only init, sh and sshd remain. If you have space, rsync your current v4 mountpoints to some backup dirs. You're going to need static versions of rsync, openssh, sh, su, and any other tools. You'll need to kill and run the static sshd... re: fstat, umount, libs, etc. If you want, truncate /etc/rc to load only static sshd from /root. This gives you some chance at recovery. Again, do a local trial run to figure out what, where and when you want or need all the tricks and in what order. Mount everything read-write and rsync -Haxi --delete from your v8 staging dirs (whether local or remote) over top of the live but now library freed v4 mountpoints. Reboot ;) Don't forget to lay down new boot sectors etc as and when needed during or after the above. It works, don't complain to me or this list if you break 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: Upgrading from FreeBSD 4.10 to 8.1?
Sharing some of our experiences here at VICOR. On Thu, 2011-01-06 at 15:55 -0500, grarpamp wrote: I know I'll take heat from everyone else who responded saying to effectively ship a new box. But maybe this user has significant costs involved with that. Along with any other reasons... Our company is in that situation. In fact, we have: 1000 systems still running FreeBSD-4.11 200 systems still running FreeBSD-4.8 1 system still running FreeBSD-4.4 and 1 system still running FreeBSD-2.2.2 The 200 4.8 systems are actually in the process of upgrading to 4.11 this year (go ahead... roflmao your heart out). Later this year, we plan to migrate ~500 systems from 4.11 to 8.1 and we plan to do it with a binary upgrade package (of our own design). v4 to v8 can be done. I've done it entirely live over the net. Nothing crazy about it. Confirmed. We've done it too. Nothing special. The basic idea is that there are too many changes and tools involved to fart around with build/install world, mergemaster, CD's, sysinstall, etc. And they're just not aware of such a jump. And you can't trust the idiots on the other end to get it right even if they would work. You are the SA, free your mind. To the initiate, it would be harrowing. To the seasoned SA, it's logical cake. It takes time to be thorough, but if you're thorough there's no reason to fear a binary upgrade. In fact, you can logistically break it down into the following procedure: - Take vanilla 4.x host-one - Take vanilla 8.x host-two - Diff host-one to host-two - Build binary differential package - Package pre-install regresses the machine by uninstalling all packages - Package post-install builds the 8.x box back up with new packages So backup your entire 4.x box over the wire, there will be no return. In our 4.x-8.x binary upgrade, we have a back-out strategy because we've been doing binary upgrades for years. In essence, our company started on FreeBSD-2.2.2, then did binary upgrade to 4.4. Then binary upgrade to 4.8. Then binary upgrade to 4.11. Now binary upgrade to 8.1. The backout strategy is essentially to re-install the 4.11 upgrade package (downgrading from 8.1 back to 4.11). But really... in over 10 years, we've never had to back out a binary upgrade (the procedure to do so has been documented and there, but in the tens-of-thousands of binary upgrades we've done, we've never had to back it out... not even once). Go find a box and install v8 however you want it. If you fail, this one goes to the shipper asap. You can use a vm but that will take longer to ship. You are very wise to also install a v4 box and overlay your backup on it first for testing the entire process. If you failed to heed SA wisdom about separating / /usr /usr/local /var /home /boot, free space, etc on the original v4 box, your life will be much harder. But if you have a ton of unpartitioned free space on it, you can fix that one at a time too ;) Be very aware of boot sectors, loaders, partitions, slices, fstab, sizes, /dev, ifconfig, packet filters, kernel config, etc. That kills most people. Also, since all your apps will be pristine v8 vers, you need to sort out their use of the old data and config. If you have space, rsync -Haxi upload your v8 mountpoints to separate staging dirs on the v4 box. It helps narrow your power fail window :) Get on the v4 box. If you've got console, re boot -s. If not, take it down till only init, sh and sshd remain. If you have space, rsync your current v4 mountpoints to some backup dirs. You're going to need static versions of rsync, openssh, sh, su, and any other tools. You'll need to kill and run the static sshd... re: fstat, umount, libs, etc. If you want, truncate /etc/rc to load only static sshd from /root. This gives you some chance at recovery. Again, do a local trial run to figure out what, where and when you want or need all the tricks and in what order. Mount everything read-write and rsync -Haxi --delete from your v8 staging dirs (whether local or remote) over top of the live but now library freed v4 mountpoints. Reboot ;) Don't forget to lay down new boot sectors etc as and when needed during or after the above. It works, don't complain to me or this list if you break 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 -- Cheers, Devin Teske - CONTACT INFORMATION - Business Solutions Consultant II FIS - fisglobal.com 510-735-5650 Mobile 510-621-2038 Office 510-621-2020 Office Fax 909-477-4578 Home/Fax devin.te...@fisglobal.com - LEGAL DISCLAIMER - This message contains confidential and proprietary information of the sender, and is intended only for the person(s) to whom it is addressed. Any use, distribution, copying or disclosure by any other person is strictly prohibited
Upgrading python and it's ensuing issues
So, in the course of actually upgrading all of my ports (via portmaster -a), which I've been trying to do for weeks and weeks now. 1) 'portmaster -o lang/python26 lang/python25' was successful 2) Python 2.6.6 is installed. 3) 'cd /usr/ports/lang/python make upgrade-site-packages -DUSE_PORTMASTER' failes, every time, so I have no idea what has actually been successfully updated and what hasn't, short of comparing the below list. Copy/paste if a split tmux screen, the left is what SHOULD have been installed, the right is what WAS installed (*I think*) === The following actions will be taken if you choose to proceed: Upgrade py25-dbus-0.83.0_1 to py26-dbus-0.83.2 │=== The following actions were performed: Re-install dbus-glib-0.88│ Re-installation of libtool-2.2.10 Re-install dbus-1.4.1│ Re-installation of libiconv-1.13.1_1 Re-install gmake-3.81_4 │ Re-installation of gettext-0.18.1.1 Re-install gettext-0.18.1.1 │ Re-installation of gmake-3.81_4 Re-install libiconv-1.13.1_1 │ Re-installation of pkg-config-0.25_1 Re-install libtool-2.2.10│ Re-installation of expat-2.0.1_1 Re-install pkg-config-0.25_1 │ Re-installation of libxml2-2.7.8_1 Re-install gnome_subr-1.0│ Re-installation of libsigsegv-2.9 Re-install expat-2.0.1_1 │ Re-installation of m4-1.4.15,1 Re-install libxml2-2.7.8_1 │ Re-installation of perl-threaded-5.8.9_4 Re-install libX11-1.3.3_1,1 │ Re-installation of p5-Locale-gettext-1.05_3 Re-install autoconf-2.68 │ Re-installation of help2man-1.38.2_1 Re-install autoconf-wrapper-20101119 │ Re-installation of autoconf-wrapper-20101119 Re-install m4-1.4.15,1 │ Re-installation of autoconf-2.68 Re-install libsigsegv-2.9│ Re-installation of automake-wrapper-20101119 Re-install perl-threaded-5.8.9_4 │ Re-installation of automake-1.11.1 Re-install help2man-1.38.2_1 │ Re-installation of xorg-macros-1.6.0 Re-install p5-Locale-gettext-1.05_3 │ Re-installation of xf86bigfontproto-1.2.0 Re-install automake-1.11.1 │ Re-installation of bigreqsproto-1.1.0 Re-install automake-wrapper-20101119 │ Re-installation of inputproto-2.0 Re-install xorg-macros-1.6.0 │ Re-installation of kbproto-1.0.4 Re-install xf86bigfontproto-1.2.0│ Re-installation of xproto-7.0.16 Re-install bigreqsproto-1.1.0│ Re-installation of libXau-1.0.5 Re-install inputproto-2.0│ Re-installation of libXdmcp-1.0.3 Re-install kbproto-1.0.4 │ Re-installation of libcheck-0.9.8 Re-install libXau-1.0.5 │ Re-installation of libpthread-stubs-0.3_3 Re-install xproto-7.0.16 │ Re-installation of pth-2.0.7 Re-install libXdmcp-1.0.3│ Re-installation of python26-2.6.6 Re-install libxcb-1.7│ Re-installation of libgpg-error-1.10 Re-install libcheck-0.9.8│ Re-installation of libgcrypt-1.4.6 Re-install libpthread-stubs-0.3_3│ Re-installation of libxslt-1.1.26_2 Re-install python26-2.6.6│ Re-installation of xcb-proto-1.6 Re-install pth-2.0.7 │ Re-installation of libxcb-1.7 Re-install libxslt-1.1.26_2 │ Re-installation of xcmiscproto-1.2.0 Re-install libgcrypt-1.4.6 │ Re-installation of xextproto-7.1.1 Re-install libgpg-error-1.10 │ Re-installation of xtrans-1.2.5 Re-install xcb-proto-1.6 │ Re-installation of libX11-1.3.3_1,1 Re-install xcmiscproto-1.2.0 │ Re-installation of gnome_subr-1.0 Re-install xextproto-7.1.1 │ Re-installation of dbus-1.4.1 Re-install xtrans-1.2.5 │ Re-installation of icu-4.6 Re-install gio-fam-backend-2.26.1│ Re-installation of pcre-8.10 Re-install gamin-0.1.10_4│ Re-installation of glib-2.26.1_1 Re-install glib-2.26.1_1 │ Re-installation of gamin-0.1.10_4 Re-install icu-4.6
Re: portmaster problems upgrading to php 5.3.4
I should also mention that I have an almost-identical server running FreeBSD 7.3-release-p2 in backup production and did not experience these problems when upgrading from php 5.3.3_2 to php 5.3.4. Something in my 8.1-release development server is causing the problems with upgrading PHP, so I'm reluctant to upgrade my production servers as they are absolutely identical until I find a fix. Thanks, Kelly ___ 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
portmaster problems upgrading to php 5.3.4
Hi there, I'm having problems upgrading my php installation using the ports tree. I use the latest version of portmaster on FreeBSD 8.1-release inside a jail, with all patches. I'm trying to upgrade from php 5.3.3_2 to the new php 5.3.4 to fix a security vulnerability. Here is the problem. When upgrading my PHP, some of the dependencies fail because they are already installed. If I manually remove those port-installed packages it continues to build past this point but then the script breaks again with a later dependency. So the error below is just one example of several I've encountered during the attempted upgrade of a port. In the past this was never an issue because portmaster is smart and would recursively install/reinstall all required packages for me automatically. Something has changed now because this functionality is no longer working for me. I issue the command: dev:/#portmaster -t -d php5 [...large amount of compilation data for php and various supporting packages removed...] === Installing for libltdl-2.2.10 === Generating temporary packing list === Checking if devel/libltdl already installed === libltdl-2.2.10 is already installed You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of devel/libltdl without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. *** Error code 1 Stop in /usr/ports/devel/libltdl. === Installation of libltdl-2.2.10 (devel/libltdl) failed === Aborting update === Update for devel/libltdl failed === Aborting update === Update for php5-mcrypt-5.3.3_2 failed === Aborting update Terminated At this point I am half-way upgraded only. Here is what pkg_version -v shows now for php: dev:/#pkg_version -v php5-5.3.4 = up-to-date with port php5-ctype-5.3.4= up-to-date with port php5-curl-5.3.4 = up-to-date with port php5-dom-5.3.4 = up-to-date with port php5-extensions-1.4 = up-to-date with port php5-filter-5.3.4 = up-to-date with port php5-hash-5.3.4 = up-to-date with port php5-iconv-5.3.4= up-to-date with port php5-json-5.3.4 = up-to-date with port php5-mcrypt-5.3.3_2needs updating (port has 5.3.4) php5-mysql-5.3.3_2 needs updating (port has 5.3.4) php5-openssl-5.3.3_2 needs updating (port has 5.3.4) php5-pdo-5.3.3_2 needs updating (port has 5.3.4) php5-pdo_sqlite-5.3.3_2needs updating (port has 5.3.4) php5-posix-5.3.3_2 needs updating (port has 5.3.4) php5-session-5.3.3_2 needs updating (port has 5.3.4) php5-simplexml-5.3.3_2 needs updating (port has 5.3.4) php5-sqlite-5.3.3_2needs updating (port has 5.3.4) php5-tokenizer-5.3.3_2 needs updating (port has 5.3.4) php5-xml-5.3.3_2 needs updating (port has 5.3.4) php5-xmlreader-5.3.3_2 needs updating (port has 5.3.4) php5-xmlwriter-5.3.3_2 needs updating (port has 5.3.4) php5-zlib-5.3.3_2 needs updating (port has 5.3.4) Fortunately the security vulnerability appears to be gone now, at least: dev:/#portaudit -Fa auditfile.tbz 100% of 64 kB 64 kBps New database installed. 0 problem(s) in your installed packages found. So I'm probably fine but I'd like to get everything upgraded to the same version one day soon. Thanks, Kelly ___ 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: portmaster problems upgrading to php 5.3.4
On 28/12/2010 22:07, Kelly Martin wrote: I should also mention that I have an almost-identical server running FreeBSD 7.3-release-p2 in backup production and did not experience these problems when upgrading from php 5.3.3_2 to php 5.3.4. Something in my 8.1-release development server is causing the problems with upgrading PHP, so I'm reluctant to upgrade my production servers as they are absolutely identical until I find a fix. Try running 'portmaster --check-depends', then retry the update. If it still fails, then choose one or more of the php5 modules that fails and do a forced update of it and all of its dependencies: eg # portmaster -f php5-mcrypt-5.3.3_2 This will re-install quite a lot of packages, so be prepared for it to take a while. Something like this list, although details will vary depending on your configuration: #pkg_info -rRx php5-mcrypt Information for php5-mcrypt-5.3.4: Depends on: Dependency: expat-2.0.1_1 Dependency: openssl-1.0.0_4 Dependency: libmcrypt-2.5.8 Dependency: perl-5.10.1_3 Dependency: pkg-config-0.25_1 Dependency: pcre-8.10 Dependency: libltdl-2.2.10 Dependency: mysql-client-5.1.54_1 Dependency: db48-4.8.30.0 Dependency: libiconv-1.13.1_1 Dependency: libxml2-2.7.8_1 Dependency: apr-ipv6-devrandom-db48-mysql51-1.4.2.1.3.10 Dependency: apache-2.2.17_1 Dependency: php5-5.3.4 After that you should be able to finish off the updates as usual. Oh -- beware of the extension.ini ordering problem. If php starts crashing on you after the update, it's probably because the order of the modules in /usr/local/etc/php/extensions.ini has changed and needs to be edited back to something workable. 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: portmaster problems upgrading to php 5.3.4
2010/12/28 Maciej Milewski m...@dat.pl: Have you read /usr/ports/UPDATING? There is a note: 20101208: AFFECTS: autotools AUTHOR: autoto...@freebsd.org Another stage in the autotools cleanup that reduces tree churn whilst updating components, a number of ports have now moved to non-versioned locations since there is now only the concept of legacy and current versions. # portmaster -o devel/autoconf devel/autoconf268 # portmaster -o devel/automake devel/automake111 # portmaster -o devel/libtool devel/libtool22 # portmaster -o devel/libltdl devel/libltdl22 Awesome, that fixed my problem. Thanks very much! I hadn't seen that note in /usr/ports/UPDATING so I appreciate you pointing it out. And I just ran this on all my servers and everything is now up to date, cool! Cheers, Kelly ___ 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: ORBit not upgrading
Ok. So this is not just an upgrade issue, I can't build it on a fresh
install on another m/c either. Any fixes/workarounds? Is anyone aware of
this issue?
I'm afraid I'm not experienced enough to work this out- unless someone
can explain what the check is?
Cheers
Original Message
Subject:ORBit not upgrading
Date: Wed, 10 Nov 2010 15:09:04 +1100
From: freebsd-questi...@herveybayaustralia.com.au
Reply-To: freebsd-questi...@herveybayaustralia.com.au
To: freebsd-questions@freebsd.org
I have a wee problem... :) I've been naughty because I've been
working on other things and I was going to simply rebuild this m/c
when I got the chance anyway. Unfortunately I've run into a problem
where I need to upgrade because I've found a bug in php 5.3.2 which is
killing me. So I've run an upgrade at a rather late date, and
alswell... except ORBit is not behaving.
I've checked UPDATING and looked into the Makefiles, but for the life
of me I can't fathom what the hell is going on. It is running thru the
checks and stalls completely here:
...
checking for a BSD compatible install... /usr/bin/install -c -o root
-g wheel
checking whether build environment is sane... yes
checking whether gmake sets ${MAKE}... yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking for gcc... cc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for executable suffix...
checking for object suffix... o
checking whether we are using the GNU C compiler... yes
checking whether cc accepts -g... yes
checking for strerror in -lcposix... no
checking for gcc... (cached) cc
checking whether we are using the GNU C compiler... (cached) yes
checking whether cc accepts -g... (cached) yes
checking how to run the C preprocessor... cpp
checking if C preprocessor likes IDL... yes
checking if C preprocessor can read from stdin... yes
checking how to ignore standard include path...
Huh? Any reason it'd be looking for a non standard include path?
Whats the hold up?
Now this is ORBit-0.5.17_5, and I don't think a manual reinstall
would make much difference. But WTF? Any Ideas?
As for the php error: anybody have trouble with preg_match and the
subject string being a variable? If I manually put the contents in as
the subject it works, but it won't read out of the variable. I'm
actually exec something and the variable holds the output (and yes, it
does work, and the variable holds the info right- just ran a print on
the variable) but the stupid thing is sending me bald and I can't
register a bug before an upgrade.
Cheers
-
Message sent via Atmail Open - http://atmail.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
___
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
ORBit not upgrading
I have a wee problem... :) I've been naughty because I've been
working on other things and I was going to simply rebuild this m/c
when I got the chance anyway. Unfortunately I've run into a problem
where I need to upgrade because I've found a bug in php 5.3.2 which is
killing me. So I've run an upgrade at a rather late date, and
alswell... except ORBit is not behaving.
I've checked UPDATING and looked into the Makefiles, but for the life
of me I can't fathom what the hell is going on. It is running thru the
checks and stalls completely here:
...
checking for a BSD compatible install... /usr/bin/install -c -o root
-g wheel
checking whether build environment is sane... yes
checking whether gmake sets ${MAKE}... yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking for gcc... cc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for executable suffix...
checking for object suffix... o
checking whether we are using the GNU C compiler... yes
checking whether cc accepts -g... yes
checking for strerror in -lcposix... no
checking for gcc... (cached) cc
checking whether we are using the GNU C compiler... (cached) yes
checking whether cc accepts -g... (cached) yes
checking how to run the C preprocessor... cpp
checking if C preprocessor likes IDL... yes
checking if C preprocessor can read from stdin... yes
checking how to ignore standard include path...
Huh? Any reason it'd be looking for a non standard include path?
Whats the hold up?
Now this is ORBit-0.5.17_5, and I don't think a manual reinstall
would make much difference. But WTF? Any Ideas?
As for the php error: anybody have trouble with preg_match and the
subject string being a variable? If I manually put the contents in as
the subject it works, but it won't read out of the variable. I'm
actually exec something and the variable holds the output (and yes, it
does work, and the variable holds the info right- just ran a print on
the variable) but the stupid thing is sending me bald and I can't
register a bug before an upgrade.
Cheers
-
Message sent via Atmail Open - http://atmail.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
4.5.4 Upgrading Ports (Handbook)
Hi, I have a pretty simple question regarding upgrading ports.. I am following the handbook Section 4.5.4.. Step 1: pkg_version -v: Ok done.. bunch of stuff needs updating: Ex: hbca# pkg_version -v | grep -v up-to-date with port ImageMagick-6.6.3.10 needs updating (port has 6.6.4.10) apache-2.2.16_2needs updating (port has 2.2.17_1) avahi-app-0.6.25_3 needs updating (port has 0.6.27_2) bison-2.4.1_1,1needs updating (port has 2.4.3,1) bn-freebsd-doc-20100625needs updating (port has 20100926) boost-libs-1.43.0 needs updating (port has 1.43.0_1) cmake-2.8.2needs updating (port has 2.8.2_1) consolekit-0.4.1_3 needs updating (port has 0.4.1_4) cups-client-1.4.3 needs updating (port has 1.4.4) da-freebsd-doc-20100625needs updating (port has 20100926) dbus-1.2.24_1 needs updating (port has 1.2.24_2) dbus-glib-0.86_1 needs updating (port has 0.88) de-freebsd-doc-20100625needs updating (port has 20100926) el-freebsd-doc-20100625needs updating (port has 20100926) en-freebsd-doc-20100625needs updating (port has 20100926) enchant-1.4.2 needs updating (port has 1.6.0) es-freebsd-doc-20100625needs updating (port has 20100926) feh-1.5needs updating (port has 1.8) fr-freebsd-doc-20100625needs updating (port has 20100926) freetype2-2.3.12 needs updating (port has 2.4.2) gettext-0.18_1 needs updating (port has 0.18.1.1) gio-fam-backend-2.24.1_1 needs updating (port has 2.24.2) Step 2: Update Ports collection: Ports collection updated everynite via cron job and cvsup. Done... Check /usr/ports/UPDATING.. This seems very time consuming considering i have a long list of ports that need updating.. (can i safely skip this step?) Step 3: portupgrade installed, done Step 4: pkgdb -F here it is: hbca# pkgdb -F --- Checking the package registry database Stale origin: 'net/samba3': perhaps moved or obsoleted. - The port 'net/samba3' was removed on 2010-10-18 because: Has expired: Unsupported by the upstream. Please, consider to upgrade. - Hint: samba-3.0.37_1,1 is not required by any other package - Hint: checking for overwritten files... - No files installed by samba-3.0.37_1,1 have been overwritten by other packages. Deinstall samba-3.0.37_1,1 ? [no] no Duplicated origin: security/libgcrypt - libgcrypt-1.4.5_1 libgcrypt-1.4.6 Unregister any of them? [no] no hbca# So if i deinstall samba and unregister one of the duplicated origins for libgcrypt will portupgrade reinstall them or fix this mess? Thanks, Justin ___ 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: 4.5.4 Upgrading Ports (Handbook)
At 10:41 AM 10/22/2010, Justin Victoria wrote: hbca# pkgdb -F --- Checking the package registry database Stale origin: 'net/samba3': perhaps moved or obsoleted. - The port 'net/samba3' was removed on 2010-10-18 because: Has expired: Unsupported by the upstream. Please, consider to upgrade. - Hint: samba-3.0.37_1,1 is not required by any other package - Hint: checking for overwritten files... - No files installed by samba-3.0.37_1,1 have been overwritten by other packages. Deinstall samba-3.0.37_1,1 ? [no] no Duplicated origin: security/libgcrypt - libgcrypt-1.4.5_1 libgcrypt-1.4.6 Unregister any of them? [no] no hbca# So if i deinstall samba and unregister one of the duplicated origins for libgcrypt will portupgrade reinstall them or fix this mess? You might want to go back to step #2 and check what it says about this. ___ Boobs feed babies! - Jodi of Bronx Beat ___ 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: 4.5.4 Upgrading Ports (Handbook)
On Fri, 22 Oct 2010, Justin Victoria wrote: Step 1: pkg_version -v: Ok done.. bunch of stuff needs updating: ... Step 2: Update Ports collection: Ports collection updated everynite via cron job and cvsup. Done... Check /usr/ports/UPDATING.. This seems very time consuming considering i have a long list of ports that need updating.. (can i safely skip this step?) No. UPDATING lists the exceptions and problems. You only have to check it since the date of your last update, though. My Upgrading FreeBSD Ports article: http://www.wonkity.com/~wblock/docs/html/portupgrade.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: 4.5.4 Upgrading Ports (Handbook)
Ok, so let me get this straight. Here is what Ive deduced using the handbook: Step 1: run pkg_version -v will just stick with samba for now: [...@hbca ~]$ pkg_version -v | grep -i samba samba-3.0.37_1,1= up-to-date with index samba34-libsmbclient-3.4.8 needs updating (port has 3.4.9) pkg_version -v is telling me samba is up-to-date with index samba34-libsmbclient-3.4.8 needs updating.. ok. step 2, check /usr/ports/UPDATING hbca# grep samba-3.0.37 /usr/ports/UPDATING hbca# grep -i samba-3.0.37 /usr/ports/UPDATING hbca# grep -i samba34-lib /usr/ports/UPDATING hbca# grep -i samba34 /usr/ports/UPDATING AFFECTS: users of net/samba34 hbca# [...@hbca ~]$ grep 3.0.37 /usr/ports/UPDATING [...@hbca ~]$ 20100205: AFFECTS: users of net/samba34 AUTHOR: ti...@freebsd.org This port was developed with the generous help of Florent Brodin. The default passdb backend has been changed to `tdbsam'! That breaks existing setups using the `smbpasswd' backend without explicit declaration! Please use `passdb backend = smbpasswd' if you would like to stick to the `smbpasswd' backend or convert your smbpasswd entries using e.g. `pdbedit -i smbpasswd -e tdbsam'. The `tdbsam' backend is much more flexible concerning per user settings like `profile path' or `home directory' and there are some commands which do not work with the `smbpasswd' backend at all. I see an issue with samba34 but not samba34-libsmbclient-3.4.8 specifically. so Step 3: pkgdb -F hbca# pkgdb -F --- Checking the package registry database Stale origin: 'net/samba3': perhaps moved or obsoleted. - The port 'net/samba3' was removed on 2010-10-18 because: Has expired: Unsupported by the upstream. Please, consider to upgrade. - Hint: samba-3.0.37_1,1 is not required by any other package - Hint: checking for overwritten files... - No files installed by samba-3.0.37_1,1 have been overwritten by other packages. Deinstall samba-3.0.37_1,1 ? [no] no Duplicated origin: security/libgcrypt - libgcrypt-1.4.5_1 libgcrypt-1.4.6 Unregister any of them? [no] no pkg_version said samba-3.0.37_1,1 is up to date with the index. pkgdb doesnt mention anything about samba34-libsmbclient-3.4.8. Since samba is very to configure, I can simply deinstall samba all together and reinstall.. What exactly is the point of portupgrade then? On Fri, 22 Oct 2010, Warren Block wrote: On Fri, 22 Oct 2010, Justin Victoria wrote: Step 1: pkg_version -v: Ok done.. bunch of stuff needs updating: ... Step 2: Update Ports collection: Ports collection updated everynite via cron job and cvsup. Done... Check /usr/ports/UPDATING.. This seems very time consuming considering i have a long list of ports that need updating.. (can i safely skip this step?) No. UPDATING lists the exceptions and problems. You only have to check it since the date of your last update, though. My Upgrading FreeBSD Ports article: http://www.wonkity.com/~wblock/docs/html/portupgrade.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 ___ 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: 4.5.4 Upgrading Ports (Handbook)
On Fri, 22 Oct 2010, Justin Victoria wrote: Ok, so let me get this straight. Here is what Ive deduced using the handbook: Step 1: run pkg_version -v will just stick with samba for now: [...@hbca ~]$ pkg_version -v | grep -i samba samba-3.0.37_1,1= up-to-date with index samba34-libsmbclient-3.4.8 needs updating (port has 3.4.9) pkg_version -v is telling me samba is up-to-date with index samba34-libsmbclient-3.4.8 needs updating.. ok. step 2, check /usr/ports/UPDATING hbca# grep samba-3.0.37 /usr/ports/UPDATING Grepping for specific things in UPDATING is bound to miss big updates that affect lots of ports, like gettext. Look at what's new in that file since the last time you updated ports. hbca# pkgdb -F --- Checking the package registry database Stale origin: 'net/samba3': perhaps moved or obsoleted. - The port 'net/samba3' was removed on 2010-10-18 because: Has expired: Unsupported by the upstream. Please, consider to upgrade. - Hint: samba-3.0.37_1,1 is not required by any other package - Hint: checking for overwritten files... - No files installed by samba-3.0.37_1,1 have been overwritten by other packages. Deinstall samba-3.0.37_1,1 ? [no] no Duplicated origin: security/libgcrypt - libgcrypt-1.4.5_1 libgcrypt-1.4.6 Unregister any of them? [no] no Looks like you've already missed some notes in UPDATING: % less +/20100727 /usr/ports/UPDATING Since samba is very to configure, I can simply deinstall samba all together and reinstall.. What exactly is the point of portupgrade then? Automating the process of updating a web of dependencies. The article link speaks about this a bit: http://www.wonkity.com/~wblock/docs/html/portupgrade.html PS: please don't top-post, it makes responding more difficult. ___ 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: Upgrading to higher major version directly or via small steps?
I can't understand why should I use this adm tool instead of standard method, described in /usr/src/Makefile. And it's not an answer to this question: 6.2 to 7.3 is which one of the folowing: - 6.2-6.4-7.0-7.3 or - 6.2-7.3 directly? 2010/10/4 Odhiambo Washington odhia...@gmail.com: On Mon, Oct 4, 2010 at 4:47 PM, c0re nr1c...@gmail.com wrote: Hello all! I'm interested in 2 updates: - from 6.2 to 7.3 and - from 6.2 to 8.1 Can I update directly from 6.2 to 7.3? like set RELENG_7_3 in supfile and make csup. Or I should update to 6.4, then to 7.0, and then to 7.3? And same question about upgrading from 6.2 to 8.1 - can i csup directly to 8.1? If not - why is it so? http://people.freebsd.org/~rse/upgrade/ -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ If you have nothing good to say about someone, just shut up!. -- Lucky Dube ___ 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: Upgrading to higher major version directly or via small steps?
I can't understand why should I use this adm tool instead of standard method, described in /usr/src/Makefile. List subscribers generally ask that those sending messages to the list place their replies below quoted material, rather than above it. If you read /usr/src/UPDATING, you will see: To rebuild everything and install it on the current system. --- # Note: sometimes if you are running current you gotta do more than # is listed here if you are upgrading from a really old current. This same statement is valid with regard to releases, and the -STABLE branches. Engelschall's adm toolkit and associated scripts attempt to do more than is listed here, as Engelschall described clearly at the link that Washington gave you, http://people.freebsd.org/~rse/upgrade/ 'for upgrading from X-STABLE to (X+1)-STABLE ... the usual build and install everything from source does not work or at least requires additional preparations.' I would qualify that does not work with a sometimes. Of course you don't have to use this stuff, but you may want to at least look through his scripts, to see if some of the steps are applicable to your machines. In any event, before you attempt a major upgrade, you should back up your data, so that it will not be lost if something goes wrong. Also, you may want to consider simply wiping your disks and starting afresh with new binary installation, rather than attempting to upgrade directly. Sometimes that is easier. You can always customize it later. And it's not an answer to this question: 6.2 to 7.3 is which one of the folowing: - 6.2-6.4-7.0-7.3 or - 6.2-7.3 directly? See below. 2010/10/4 Odhiambo Washington odhiambo at gmail.com: On Mon, Oct 4, 2010 at 4:47 PM, c0re nr1c0re at gmail.com wrote: ... I'm interested in 2 updates: - from 6.2 to 7.3 and - from 6.2 to 8.1 Can I update directly from 6.2 to 7.3? like set RELENG_7_3 in supfile and make csup. Or I should update to 6.4, then to 7.0, and then to 7.3? And same question about upgrading from 6.2 to 8.1 - can i csup directly to 8.1? If not - why is it so? You might as well do both updates in just one step. You probably won't gain much by breaking it up into smaller steps, and that will take longer. It may be quicker and safer just to start with a new src collection, obtained via csup, svn, release media, or tarballs, rather than attempting to bring a very old src collection up to date. 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
Upgrading to higher major version directly or via small steps?
Hello all! I'm interested in 2 updates: - from 6.2 to 7.3 and - from 6.2 to 8.1 Can I update directly from 6.2 to 7.3? like set RELENG_7_3 in supfile and make csup. Or I should update to 6.4, then to 7.0, and then to 7.3? And same question about upgrading from 6.2 to 8.1 - can i csup directly to 8.1? If not - why is it so? 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: Upgrading to higher major version directly or via small steps?
On Mon, Oct 4, 2010 at 4:47 PM, c0re nr1c...@gmail.com wrote: Hello all! I'm interested in 2 updates: - from 6.2 to 7.3 and - from 6.2 to 8.1 Can I update directly from 6.2 to 7.3? like set RELENG_7_3 in supfile and make csup. Or I should update to 6.4, then to 7.0, and then to 7.3? And same question about upgrading from 6.2 to 8.1 - can i csup directly to 8.1? If not - why is it so? http://people.freebsd.org/~rse/upgrade/ -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ If you have nothing good to say about someone, just shut up!. -- Lucky Dube ___ 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
JAILS in FreeBSD manual - Minor ambiguity between 15.6.1.3 Creating Jails 15.6.1.4 Upgrading
Hello, 15.6.1.4 Upgrading in the FreeBSD manual provides a great step, by step way to safely update jails. I've just installed apache in the host system, and now I wish to propagate it to the system wide jail skeleton, and www jail. But given my limited experience with jails, I am perplexed to read in the 2nd last sentence of this section: Do not forget to run mergemaster in each jail. The instruction doesn't say between which steps (which one between 1 through 6) to run mergemaster, and I'm left guessing as I'm still coming up to speed on jail configuration and maintenance. Carefully reading *15.6.1.2 Creating the Template* it says that mergemaster is run in: Step 4 - Use Mergemaster to install missing configuration files... This follows: Step 1 - Create a read-only directory structure for the read-only file system...(make installworld) Step 2 - Prepare FreeBSD ports collection for the jails... Step 3 - Create a skeleton for the read-write portion... However *15.6.1.4 Upgrading* shares only step 1 (make installworld), but steps 2 through 6 are quite different. I am left wondering between which steps in 15.6.1.4 Upgrading that I am to run mergemaster on each jail. I would be very happy to get a tip. Thank you, Matthew ___ 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: Upgrading autoconf
On Thu, Sep 30, 2010 at 6:59 PM, Daniel Bye freebsd-questi...@slightlystrange.org wrote: On Thu, Sep 30, 2010 at 06:50:22PM +0300, Odhiambo Washington wrote: I am trying this out: #portupgrade -f 'autoconf*' 'automake*' Try upgrading the failing ports by hand. portupgrade tends to suppress full error output, making it difficult to ascertain exactly what's gone wrong. Alternatively, I would be tempted to just uninstall autoconf* and automake*, since they will get pulled in as dependencies whenever you come to build another port that requires them. Hi Dan, Turns out the culprit was m4. Once I did 'portupgrade m4' successfully, everything now compiled fine. The box is running FreeBSD 6.4-STABLE which I was ashamed to mention:-) Will migrate it to 8.x soon, by doing a new installation and migrating. Or should I wait for FreeBSD-9 ?? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ If you have nothing good to say about someone, just shut up!. -- Lucky Dube ___ 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: Upgrading autoconf
On Fri, Oct 01, 2010 at 12:13:28PM +0300, Odhiambo Washington wrote: On Thu, Sep 30, 2010 at 6:59 PM, Daniel Bye freebsd-questi...@slightlystrange.org wrote: On Thu, Sep 30, 2010 at 06:50:22PM +0300, Odhiambo Washington wrote: I am trying this out: #portupgrade -f 'autoconf*' 'automake*' Try upgrading the failing ports by hand. portupgrade tends to suppress full error output, making it difficult to ascertain exactly what's gone wrong. Alternatively, I would be tempted to just uninstall autoconf* and automake*, since they will get pulled in as dependencies whenever you come to build another port that requires them. Hi Dan, Turns out the culprit was m4. Once I did 'portupgrade m4' successfully, everything now compiled fine. The box is running FreeBSD 6.4-STABLE which I was ashamed to mention:-) Glad you fixed it! Will migrate it to 8.x soon, by doing a new installation and migrating. Or should I wait for FreeBSD-9 ?? I'd go for 8.x as soon as possible. It'll be a while before 9 is ready for production, and when it is released, it should be pretty straight forward to upgrade from 8.x using the standard buildworld cycle, provided your setup isn't too outlandish! Dan -- Daniel Bye _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ pgp7nxygb4Lhw.pgp Description: PGP signature
Re: Upgrading autoconf
On Fri, 1 Oct 2010 12:13:28 +0300 Odhiambo Washington odhia...@gmail.com articulated: Or should I wait for FreeBSD-9 ?? Or Freebsd-10.x perhaps! -- Jerry ✌ freebsd.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ 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: Upgrading autoconf
On Fri, Oct 1, 2010 at 12:36 PM, Daniel Bye freebsd-questi...@slightlystrange.org wrote: On Fri, Oct 01, 2010 at 12:13:28PM +0300, Odhiambo Washington wrote: On Thu, Sep 30, 2010 at 6:59 PM, Daniel Bye freebsd-questi...@slightlystrange.org wrote: On Thu, Sep 30, 2010 at 06:50:22PM +0300, Odhiambo Washington wrote: I am trying this out: #portupgrade -f 'autoconf*' 'automake*' Try upgrading the failing ports by hand. portupgrade tends to suppress full error output, making it difficult to ascertain exactly what's gone wrong. Alternatively, I would be tempted to just uninstall autoconf* and automake*, since they will get pulled in as dependencies whenever you come to build another port that requires them. Hi Dan, Turns out the culprit was m4. Once I did 'portupgrade m4' successfully, everything now compiled fine. The box is running FreeBSD 6.4-STABLE which I was ashamed to mention:-) Glad you fixed it! Will migrate it to 8.x soon, by doing a new installation and migrating. Or should I wait for FreeBSD-9 ?? I'd go for 8.x as soon as possible. It'll be a while before 9 is ready for production, and when it is released, it should be pretty straight forward to upgrade from 8.x using the standard buildworld cycle, provided your setup isn't too outlandish! Update 6.4 to 8.x?? Or you mean some upgrade path like install 8.x and then migrate services?:-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ If you have nothing good to say about someone, just shut up!. -- Lucky Dube ___ 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: Upgrading autoconf
On Fri, Oct 01, 2010 at 03:02:10PM +0300, Odhiambo Washington wrote: Will migrate it to 8.x soon, by doing a new installation and migrating. Or should I wait for FreeBSD-9 ?? I'd go for 8.x as soon as possible. It'll be a while before 9 is ready for production, and when it is released, it should be pretty straight forward to upgrade from 8.x using the standard buildworld cycle, provided your setup isn't too outlandish! Update 6.4 to 8.x?? Or you mean some upgrade path like install 8.x and then migrate services?:-) Since you're crossing two major versions, I'd go for a clean install. You could conceivably go straight to 8 using buildworld, but I think the safest and simplest course of action is to take good backups and start from scratch. As for going from 8.x to 9.x, that should be pretty easy, if, as I said, your setup isn't too far from the default. But of course, only you can make that call. Dan -- Daniel Bye _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ pgpH6dN2QDWf5.pgp Description: PGP signature
Re: Upgrading autoconf
On Fri, Oct 1, 2010 at 5:11 PM, Daniel Bye freebsd-questi...@slightlystrange.org wrote: On Fri, Oct 01, 2010 at 03:02:10PM +0300, Odhiambo Washington wrote: Will migrate it to 8.x soon, by doing a new installation and migrating. Or should I wait for FreeBSD-9 ?? I'd go for 8.x as soon as possible. It'll be a while before 9 is ready for production, and when it is released, it should be pretty straight forward to upgrade from 8.x using the standard buildworld cycle, provided your setup isn't too outlandish! Update 6.4 to 8.x?? Or you mean some upgrade path like install 8.x and then migrate services?:-) Since you're crossing two major versions, I'd go for a clean install. You could conceivably go straight to 8 using buildworld, but I think the safest and simplest course of action is to take good backups and start from scratch. As for going from 8.x to 9.x, that should be pretty easy, if, as I said, your setup isn't too far from the default. But of course, only you can make that call. My servers are pretty easy to migrate. It's just a case of a fresh install, install the applications, migrate the configs and data/databases since I try and keep up to date with the application versions as much as possible. The only thing that changes significantly is the base system. I will go for a clean install. Sometimes back I saw some instructions to upgrade upwards (6.x -7.x -8.x) but I cannot find them anymore, although the only time to do those are when the system is in the room next:-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ If you have nothing good to say about someone, just shut up!. -- Lucky Dube ___ 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
Upgrading autoconf
I am trying this out:
#portupgrade -f 'autoconf*' 'automake*'
and I end up with:
=== Building for autoconf-2.67
gmake all-recursive
gmake[1]: Entering directory
`/usr/ports/devel/autoconf267/work/autoconf-2.67'
Making all in bin
gmake[2]: Entering directory
`/usr/ports/devel/autoconf267/work/autoconf-2.67/bin'
rm -f autom4te autom4te.tmp
srcdir=''; \
test -f ./autom4te.in || srcdir=./; \
sed -e 's|@she...@]|/bin/sh|g' -e 's|@pe...@]|/usr/bin/perl|g' -e
's|@perl_flo...@]|yes|g' -e 's|@bind...@]|/usr/local/bin|g' -e 's|@pk
gdatad...@]|/usr/local/share/autoconf-2.67|g' -e 's|@pref...@]|/usr/local|g'
-e 's|@autoconf-na...@]|'`echo autoconf | sed 's$-2.67'`'|g' -e '
s|@autoheader-na...@]|'`echo autoheader | sed 's$-2.67'`'|g' -e
's|@autom4te-na...@]|'`echo autom4te | sed 's$-2.67'`'|g' -e
's|@m...@]|/usr
/local/bin/gm4|g' -e 's|@m4_debugfi...@]|--error-output|g' -e
's|@m4_g...@]||g' -e 's|@a...@]|/usr/bin/awk|g' -e 's|@release_ye...@]|'`sed
's/^\(
[0-9][0-9][0-9][0-9]\).*/\1/;q' ../ChangeLog`'|g' -e 's|@versi...@]|2.67|g'
-e 's|@package_na...@]|GNU Autoconf|g' -e 's|@configure_inp...@]|Gene
rated from autom4te.in; do not edit by hand.|g'
${srcdir}autom4te.inautom4te.tmp
chmod +x autom4te.tmp
chmod a-w autom4te.tmp
mv autom4te.tmp autom4te
cd ../lib gmake autom4te.cfg
gmake[3]: Entering directory
`/usr/ports/devel/autoconf267/work/autoconf-2.67/lib'
rm -f autom4te.cfg autom4te.tmp
sed -e 's|@she...@]|/bin/sh|g' -e 's|@pe...@]|/usr/bin/perl|g' -e
's|@bind...@]|/usr/local/bin|g' -e
's|@pkgdatad...@]|/usr/local/share/autoconf-
2.67|g' -e 's|@pref...@]|/usr/local|g' -e 's|@autoconf-na...@]|'`echo
autoconf | sed 's$-2.67'`'|g' -e 's|@autoheader-na...@]|'`echo autoheade
r | sed 's$-2.67'`'|g' -e 's|@autom4te-na...@]|'`echo autom4te | sed
's$-2.67'`'|g' -e 's|@m...@]|/usr/local/bin/gm4|g' -e 's|@a...@]|/usr/b
in/awk|g' -e 's|@versi...@]|2.67|g' -e 's|@package_na...@]|GNU Autoconf|g'
./autom4te.in autom4te.tmp
chmod a-w autom4te.tmp
mv autom4te.tmp autom4te.cfg
gmake[3]: Leaving directory
`/usr/ports/devel/autoconf267/work/autoconf-2.67/lib'
cd ../lib/m4sugar gmake version.m4
gmake[3]: Entering directory
`/usr/ports/devel/autoconf267/work/autoconf-2.67/lib/m4sugar'
:;{ \
echo '# This file is part of -*- Autoconf -*-.' \
echo '# Version of Autoconf.' \
echo '# Copyright (C) 1999, 2000, 2001, 2002, 2006, 2007, 2009'
\
echo '# Free Software Foundation, Inc.' \
echo \
echo 'm4_define([m4_PACKAGE_NAME], [GNU Autoconf])' \
echo 'm4_define([m4_PACKAGE_TARNAME], [autoconf])' \
echo 'm4_define([m4_PACKAGE_VERSION], [2.67])' \
echo 'm4_define([m4_PACKAGE_STRING],[GNU Autoconf 2.67])' \
echo 'm4_define([m4_PACKAGE_BUGREPORT], [bug-autoc...@gnu.org])'
\
echo 'm4_define([m4_PACKAGE_URL], [
http://www.gnu.org/software/autoconf/])' \
echo 'm4_define([m4_PACKAGE_YEAR], ['`sed
's/^\([0-9][0-9][0-9][0-9]\).*/\1/;q' ../../ChangeLog`'])'; \
} version.m4-t
mv version.m4-t version.m4
gmake[3]: Leaving directory
`/usr/ports/devel/autoconf267/work/autoconf-2.67/lib/m4sugar'
autom4te_perllibdir='..'/lib AUTOM4TE_CFG='../lib/autom4te.cfg'
../bin/autom4te -B '..'/lib -B '..'/lib --language M4sh --cache '
' --melt ./autoconf.as -o autoconf.in
autoconf.as:1: /usr/local/bin/gm4: Warning: Excess arguments to built-in
`_m4_popdef' ignored
autom4te: /usr/local/bin/gm4 failed with exit status: 1
gmake[2]: *** [autoconf.in] Error 1
gmake[2]: Leaving directory
`/usr/ports/devel/autoconf267/work/autoconf-2.67/bin'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory
`/usr/ports/devel/autoconf267/work/autoconf-2.67'
gmake: *** [all] Error 2
*** Error code 1
Stop in /usr/ports/devel/autoconf267.
** Command failed [exit code 1]: /usr/bin/script -qa
/tmp/portupgrade.11621.2 env UPGRADE_TOOL=portupgrade
UPGRADE_PORT=autoconf-2.62 UPGRADE_POR
T_VER=2.62 make
** Fix the problem and try again.
--- Skipping 'devel/automake19' (automake-1.9.6_3) because a requisite
package 'autoconf-2.62' (devel/autoconf267) failed (specify -k to force)
** Package 'automake' has been removed from ports tree.
--- Skipping 'devel/automake19' (automake-1.9.6) because it has already
been skipped
** Listing the failed packages (*:skipped / !:failed)
! devel/autoconf267 (autoconf-2.62) (unknown build error)
* devel/automake19 (automake-1.9.6_3)
* devel/automake19 (automake-1.9.6)
--- Packages processed: 2 done, 1 ignored, 2 skipped and 1 failed
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254733744121/+254722743223
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
If you have nothing good to say about someone, just shut up!.
-- Lucky Dube
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
Re: Upgrading autoconf
On Thu, Sep 30, 2010 at 06:50:22PM +0300, Odhiambo Washington wrote: I am trying this out: #portupgrade -f 'autoconf*' 'automake*' Try upgrading the failing ports by hand. portupgrade tends to suppress full error output, making it difficult to ascertain exactly what's gone wrong. Alternatively, I would be tempted to just uninstall autoconf* and automake*, since they will get pulled in as dependencies whenever you come to build another port that requires them. Dan -- Daniel Bye _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ pgpR3Lo2vM9Gt.pgp Description: PGP signature
Re: port upgrading
On Sunday 26 September 2010, Roland Smith wrote: If you are upgrading to another major version of FreeBSD (say 7.x to 8.x), make a list of all used ports with `portmaster -l ports.list`. Then delete all ports before updating the system. After the update, re-install the 'root' and 'leaf' ports from ports.list. A more convenient approach is to run 'portmaster --list-origins' which produces a list of root and leaf ports which you can feed back into portmaster when reinstalling the ports, all the other dependencies should sort themselves out. There is a good description of this in the final example near the bottom of the portmaster man page. -- Mike Clarke ___ 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
port upgrading
I'm in doubt. I wanted to bring my ports collection uptodate, so I ran csup -L 2 /root/ports-supfile and that updated my ports collection. At least, I hope so. Then I started googling and found that cvsup is not recommended. Better tot use portsnap (???) And also portupgrade was a no go. I should be using portmaster. Woh, I'm confused now. Question: what is best used to have an up2date ports collection nowadays? This system is FreeBSD8/amd64. ___ 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
Problems upgrading p5-IO-Compress
I went to upgrade my ports this morning and saw this: p5-Compress-Zlib-2.015needs updating (port has 2.030) (= 'archivers/p5-IO-Compress') p5-IO-Compress-Base-2.015 needs updating (port has 2.030) (= 'archivers/p5-IO-Compress') p5-IO-Compress-Bzip2-2.015needs updating (port has 2.030) (= 'archivers/p5-IO-Compress') p5-IO-Compress-Zlib-2.015_1needs updating (port has 2.030) (= 'archivers/p5-IO-Compress') After reading CHANGES and UPDATING I did a portupgrade p5-* since there were no specific instructions and I get this: === Checking if archivers/p5-IO-Compress already installed === An older version of archivers/p5-IO-Compress is already installed (p5-Compress-Zlib-2.015) You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of archivers/p5-IO-Compress without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. *** Error code 1 Stop in /usr/ports/archivers/p5-IO-Compress. *** Error code 1 Stop in /usr/ports/archivers/p5-IO-Zlib. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20100926-29184-lhtw7y-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=p5-IO-Zlib-1.10 UPGRADE_PORT_VER=1.10 make ** Fix the problem and try again. --- Skipping 'archivers/p5-Archive-Tar' (p5-Archive-Tar-1.68) because a requisite package 'p5-IO-Zlib-1.10' (archivers/p5-IO-Zlib) failed (specify -k to force) ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! archivers/p5-IO-Zlib (p5-IO-Zlib-1.10)(unknown build error) * archivers/p5-Archive-Tar (p5-Archive-Tar-1.68) If I try and run pkg_delete p5-IO-Compress-Zlib-2.015_1 it won't let me because the package is in use. How do I upgrade? Did I miss some obvious instructions? All UPDATING says is: 20100921: AFFECTS: users of p5-Compress-Zlib, p5-IO-Compress-* AUTHOR: m...@freebsd.org The p5-Compress-Zlib, p5-IO-Compress-Base, p5-IO-Compress-Zlib and p5-IO-Compress-Bzip2 ports have been replaced by p5-IO-Compress. Users of Perl 5.10 and higher do not need to install this module because it is already included in the standard perl distribution. I tried following the instructions above about running make deinstall and now I get: [Updating the pkgdb format:bdb_btree in /var/db/pkg ... - 238 packages found (-1 +0) (...) done] Stale dependency: p5-Archive-Tar-1.68 -- p5-IO-Zlib-1.10 -- manually run 'pkgdb -F' to fix, or specify -O to force. I've tried running pkgdb -F, but it is just asking my a lot of questions like: Duplicated origin: archivers/p5-IO-Compress - p5-Compress-Zlib-2.015 p5-IO-Compress-Base-2.015 p5-IO-Compress-Bzip2-2.015 p5-IO-Compress-Zlib-2.015_1 Unregister any of them? [no] and I have no idea what the right answer is. I am running perl 5.8.9 and Freebsd 7.1 Any help is appreciated since I am completely lost. I've been freebsd for many years on my personal server but never encountered a mess like this before. 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: port upgrading
On Sun, Sep 26, 2010 at 06:29:17PM +0200, Dick Hoogendijk wrote: Question: what is best used to have an up2date ports collection nowadays? This system is FreeBSD8/amd64. IMO if you don't mind compiling your own ports, use portsnap and portmaster. The sequence is like this; 1) Run `portsnap fetch update`, but see (a). 2) Read /usr/ports/UPDATING, and see if any additions to the top of the file apply to you. If so, take appropriate action. 3) If you have local patches to the ports tree, re-apply them if necessary. This is not really recommended but can be handy sometimes. 4) Run `portmaster -a -B -d` (a) When you run portsnap for the first time, or if you have damaged or deleted the contents of /var/db/portsnap, use 'portsnap fetch extract' instead. For me this is part of the weekly routine. Keep an eye on http://www.freshports.org/ to see if there are interesting changes for you. If you are upgrading to another major version of FreeBSD (say 7.x to 8.x), make a list of all used ports with `portmaster -l ports.list`. Then delete all ports before updating the system. After the update, re-install the 'root' and 'leaf' ports from ports.list. Hope this helps. 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) pgppn3aHOTHD4.pgp Description: PGP signature
Re: port upgrading
On 26/09/2010 17:29:17, Dick Hoogendijk wrote: I'm in doubt. I wanted to bring my ports collection uptodate, so I ran csup -L 2 /root/ports-supfile and that updated my ports collection. At least, I hope so. Then I started googling and found that cvsup is not recommended. Better tot use portsnap (???) And also portupgrade was a no go. I should be using portmaster. Woh, I'm confused now. Question: what is best used to have an up2date ports collection nowadays? This system is FreeBSD8/amd64. csup(1) works fine and there's no good reasons not to use it. portsnap(1) also works fine, and there aren't any obvious problems that mean you shouldn't use it either. There is one somewhat subtle difference, which won't affect most people. 'portsnap extract' will blow away any custom files (Makefile.local, extra patches etc.) that you've added to the ports tree. csup(1) leaves them put. Obviously, either of the two methods will revert any modifications you've made to any files already known to be part of the ports tree. Once you've updated the tree, then you've got several choices for updating your installed ports. portupgrade(1) and portmaster(1) are the leading candidates there: portupgrade probably still has the edge on features, although development seems to be stuttering a bit recently. portmaster wins on simplicity -- it's a shell script with no other dependencies -- but still packs an awful lot of good stuff into approximately 3600 lines. Doug B is actively working on it and very responsive to bug reports etc. Really either of those two will serve you well, as will various others I haven't mentioned. Try them out, see which is most to your taste. There isn't any one 'best' solution that everyone is enjoined to use. That's not the BSD way: Tools, not policy. There are several solutions that you can use, and it's up to you to select which one you prefer. Sure, people having strong opinions on the subject have posted their thoughts on various fora, but don't be misled: those are individual opinions, and not an official position. 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: Problems upgrading p5-IO-Compress
On 26/09/2010 17:44:06, Ron wrote: I've tried running pkgdb -F, but it is just asking my a lot of questions like: Duplicated origin: archivers/p5-IO-Compress - p5-Compress-Zlib-2.015 p5-IO-Compress-Base-2.015 p5-IO-Compress-Bzip2-2.015 p5-IO-Compress-Zlib-2.015_1 Unregister any of them? [no] and I have no idea what the right answer is. I am running perl 5.8.9 and Freebsd 7.1 Any help is appreciated since I am completely lost. I've been freebsd for many years on my personal server but never encountered a mess like this before. Since you're running perl-5.8.9 you need to have p5-IO-Compress installed as a separate port. Try this: # portupgrade -o archivers/p5-IO-Compress -f p5-Compress-Zlib-2.015 # portupgrade -o archivers/p5-IO-Compress -f p5-IO-Compress-Base-2.015 # portupgrade -o archivers/p5-IO-Compress -f p5-IO-Compress-Bzip2-2.015 # portupgrade -o archivers/p5-IO-Compress -f p5-IO-Compress-Zlib-2.015_1 That should transfer all dependencies on p5-(IO-)?Compress-* onto p5-IO-Compress, which is the desired result. 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: Problems upgrading p5-IO-Compress
On Sun, Sep 26, 2010 at 09:44:06AM -0700, Ron wrote: I went to upgrade my ports this morning and saw this: p5-Compress-Zlib-2.015needs updating (port has 2.030) (= 'archivers/p5-IO-Compress') p5-IO-Compress-Base-2.015 needs updating (port has 2.030) (= 'archivers/p5-IO-Compress') p5-IO-Compress-Bzip2-2.015needs updating (port has 2.030) (= 'archivers/p5-IO-Compress') p5-IO-Compress-Zlib-2.015_1needs updating (port has 2.030) (= 'archivers/p5-IO-Compress') After reading CHANGES and UPDATING I did a portupgrade p5-* since there were no specific instructions and I get this: === Checking if archivers/p5-IO-Compress already installed === An older version of archivers/p5-IO-Compress is already installed (p5-Compress-Zlib-2.015) You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of archivers/p5-IO-Compress without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. *** Error code 1 Stop in /usr/ports/archivers/p5-IO-Compress. *** Error code 1 Stop in /usr/ports/archivers/p5-IO-Zlib. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20100926-29184-lhtw7y-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=p5-IO-Zlib-1.10 UPGRADE_PORT_VER=1.10 make ** Fix the problem and try again. --- Skipping 'archivers/p5-Archive-Tar' (p5-Archive-Tar-1.68) because a requisite package 'p5-IO-Zlib-1.10' (archivers/p5-IO-Zlib) failed (specify -k to force) ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! archivers/p5-IO-Zlib (p5-IO-Zlib-1.10)(unknown build error) * archivers/p5-Archive-Tar (p5-Archive-Tar-1.68) If I try and run pkg_delete p5-IO-Compress-Zlib-2.015_1 it won't let me because the package is in use. How do I upgrade? Did I miss some obvious instructions? All UPDATING says is: 20100921: AFFECTS: users of p5-Compress-Zlib, p5-IO-Compress-* AUTHOR: m...@freebsd.org The p5-Compress-Zlib, p5-IO-Compress-Base, p5-IO-Compress-Zlib and p5-IO-Compress-Bzip2 ports have been replaced by p5-IO-Compress. Users of Perl 5.10 and higher do not need to install this module because it is already included in the standard perl distribution. I tried following the instructions above about running make deinstall and now I get: [Updating the pkgdb format:bdb_btree in /var/db/pkg ... - 238 packages found (-1 +0) (...) done] Stale dependency: p5-Archive-Tar-1.68 -- p5-IO-Zlib-1.10 -- manually run 'pkgdb -F' to fix, or specify -O to force. I've tried running pkgdb -F, but it is just asking my a lot of questions like: Duplicated origin: archivers/p5-IO-Compress - p5-Compress-Zlib-2.015 p5-IO-Compress-Base-2.015 p5-IO-Compress-Bzip2-2.015 p5-IO-Compress-Zlib-2.015_1 Unregister any of them? [no] The answer is to run pgdb -F and unregister: p5-Compress-Zlib p5-IO-Compress-Base p5-IO-Compress-Bzip2 p5-IO-Compress-Zlib and you should be in the clear. and I have no idea what the right answer is. I am running perl 5.8.9 and Freebsd 7.1 Any help is appreciated since I am completely lost. I've been freebsd for many years on my personal server but never encountered a mess like this before. Ron 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: Problems upgrading p5-IO-Compress
On Sep 26, 2010, at 10:26 AM, Frank Shute wrote: On Sun, Sep 26, 2010 at 09:44:06AM -0700, Ron wrote: I went to upgrade my ports this morning and saw this: p5-Compress-Zlib-2.015needs updating (port has 2.030) (= 'archivers/p5-IO-Compress') p5-IO-Compress-Base-2.015 needs updating (port has 2.030) (= 'archivers/p5-IO-Compress') p5-IO-Compress-Bzip2-2.015needs updating (port has 2.030) (= 'archivers/p5-IO-Compress') p5-IO-Compress-Zlib-2.015_1needs updating (port has 2.030) (= 'archivers/p5-IO-Compress') After reading CHANGES and UPDATING I did a portupgrade p5-* since there were no specific instructions and I get this: === Checking if archivers/p5-IO-Compress already installed === An older version of archivers/p5-IO-Compress is already installed (p5-Compress-Zlib-2.015) You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of archivers/p5-IO-Compress without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. *** Error code 1 Stop in /usr/ports/archivers/p5-IO-Compress. *** Error code 1 Stop in /usr/ports/archivers/p5-IO-Zlib. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20100926-29184-lhtw7y-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=p5-IO-Zlib-1.10 UPGRADE_PORT_VER=1.10 make ** Fix the problem and try again. --- Skipping 'archivers/p5-Archive-Tar' (p5-Archive-Tar-1.68) because a requisite package 'p5-IO-Zlib-1.10' (archivers/p5-IO-Zlib) failed (specify -k to force) ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! archivers/p5-IO-Zlib (p5-IO-Zlib-1.10)(unknown build error) * archivers/p5-Archive-Tar (p5-Archive-Tar-1.68) If I try and run pkg_delete p5-IO-Compress-Zlib-2.015_1 it won't let me because the package is in use. How do I upgrade? Did I miss some obvious instructions? All UPDATING says is: 20100921: AFFECTS: users of p5-Compress-Zlib, p5-IO-Compress-* AUTHOR: m...@freebsd.org The p5-Compress-Zlib, p5-IO-Compress-Base, p5-IO-Compress-Zlib and p5-IO-Compress-Bzip2 ports have been replaced by p5-IO-Compress. Users of Perl 5.10 and higher do not need to install this module because it is already included in the standard perl distribution. I tried following the instructions above about running make deinstall and now I get: [Updating the pkgdb format:bdb_btree in /var/db/pkg ... - 238 packages found (-1 +0) (...) done] Stale dependency: p5-Archive-Tar-1.68 -- p5-IO-Zlib-1.10 -- manually run 'pkgdb -F' to fix, or specify -O to force. I've tried running pkgdb -F, but it is just asking my a lot of questions like: Duplicated origin: archivers/p5-IO-Compress - p5-Compress-Zlib-2.015 p5-IO-Compress-Base-2.015 p5-IO-Compress-Bzip2-2.015 p5-IO-Compress-Zlib-2.015_1 Unregister any of them? [no] The answer is to run pgdb -F and unregister: p5-Compress-Zlib p5-IO-Compress-Base p5-IO-Compress-Bzip2 p5-IO-Compress-Zlib and you should be in the clear. and I have no idea what the right answer is. I am running perl 5.8.9 and Freebsd 7.1 Any help is appreciated since I am completely lost. I've been freebsd for many years on my personal server but never encountered a mess like this before. Ron Excellent, this seems to have fixed it! Thanks! Ron 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: port upgrading
On 26-9-2010 19:13, Matthew Seaman wrote: Really either of those two will serve you well, as will various others I like portupgrade. One question about dependencies: if I want to update *one* port I have to run portupgrade -R portname, right. But *when* do I run portupgrade -R ,name c.q. portupgrade -rR name? ___ 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: Problems upgrading p5-IO-Compress
On 26.09.2010 19:31, Ron wrote: On Sep 26, 2010, at 10:26 AM, Frank Shute wrote: On Sun, Sep 26, 2010 at 09:44:06AM -0700, Ron wrote: I went to upgrade my ports this morning and saw this: p5-Compress-Zlib-2.015 needs updating (port has 2.030) (= 'archivers/p5-IO-Compress') p5-IO-Compress-Base-2.015 needs updating (port has 2.030) (= 'archivers/p5-IO-Compress') p5-IO-Compress-Bzip2-2.015 needs updating (port has 2.030) (= 'archivers/p5-IO-Compress') p5-IO-Compress-Zlib-2.015_1 needs updating (port has 2.030) (= 'archivers/p5-IO-Compress') After reading CHANGES and UPDATING I did a portupgrade p5-* since there were no specific instructions and I get this: === Checking if archivers/p5-IO-Compress already installed ===An older version of archivers/p5-IO-Compress is already installed (p5-Compress-Zlib-2.015) You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of archivers/p5-IO-Compress without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. *** Error code 1 Stop in /usr/ports/archivers/p5-IO-Compress. *** Error code 1 Stop in /usr/ports/archivers/p5-IO-Zlib. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20100926-29184-lhtw7y-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=p5-IO-Zlib-1.10 UPGRADE_PORT_VER=1.10 make ** Fix the problem and try again. --- Skipping 'archivers/p5-Archive-Tar' (p5-Archive-Tar-1.68) because a requisite package 'p5-IO-Zlib-1.10' (archivers/p5-IO-Zlib) failed (specify -k to force) ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! archivers/p5-IO-Zlib (p5-IO-Zlib-1.10)(unknown build error) * archivers/p5-Archive-Tar (p5-Archive-Tar-1.68) If I try and run pkg_delete p5-IO-Compress-Zlib-2.015_1 it won't let me because the package is in use. How do I upgrade? Did I miss some obvious instructions? All UPDATING says is: 20100921: AFFECTS: users of p5-Compress-Zlib, p5-IO-Compress-* AUTHOR: m...@freebsd.org The p5-Compress-Zlib, p5-IO-Compress-Base, p5-IO-Compress-Zlib and p5-IO-Compress-Bzip2 ports have been replaced by p5-IO-Compress. Users of Perl 5.10 and higher do not need to install this module because it is already included in the standard perl distribution. I tried following the instructions above about running make deinstall and now I get: [Updating the pkgdbformat:bdb_btree in /var/db/pkg ... - 238 packages found (-1 +0) (...) done] Stale dependency: p5-Archive-Tar-1.68 -- p5-IO-Zlib-1.10 -- manually run 'pkgdb -F' to fix, or specify -O to force. I've tried running pkgdb -F, but it is just asking my a lot of questions like: Duplicated origin: archivers/p5-IO-Compress - p5-Compress-Zlib-2.015 p5-IO-Compress-Base-2.015 p5-IO-Compress-Bzip2-2.015 p5-IO-Compress-Zlib-2.015_1 Unregister any of them? [no] The answer is to run pgdb -F and unregister: p5-Compress-Zlib p5-IO-Compress-Base p5-IO-Compress-Bzip2 p5-IO-Compress-Zlib and you should be in the clear. and I have no idea what the right answer is. I am running perl 5.8.9 and Freebsd 7.1 Any help is appreciated since I am completely lost. I've been freebsd for many years on my personal server but never encountered a mess like this before. Ron Excellent, this seems to have fixed it! Thanks! Ron 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 Oh, here, I actually did not de-register anything. I first run pkgdb -F. It fixed something and I answer no to unregister ...?. Then, after reading /usr/ports/UPDATING 20100921: AFFECTS: users of p5-Compress-Zlib, p5-IO-Compress-* AUTHOR: m...@freebsd.org The p5-Compress-Zlib, p5-IO-Compress-Base, p5-IO-Compress-Zlib and p5-IO-Compress-Bzip2 ports have been replaced by p5-IO-Compress. Users of Perl 5.10 and higher do not need to install this module because it is already included in the standard perl distribution. I manually checked any dependencies of the cited ports (p5-...) and de-installed the cited ports that were actually installed here and not required by any other port. Later pkgdb did not make complaints anymore. Is this procedure probably... wrong ? :-) As of my opinion unregister means discarding information but the ports are still installed and probably not used anymore. BUt just my opinion... d ___ 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: port upgrading
On 26/09/2010 18:50:32, Dick Hoogendijk wrote: On 26-9-2010 19:13, Matthew Seaman wrote: Really either of those two will serve you well, as will various others I like portupgrade. One question about dependencies: if I want to update *one* port I have to run portupgrade -R portname, right. But *when* do I run portupgrade -R ,name c.q. portupgrade -rR name? It depends on what you want to update. 'portupgrade -R name' updates name plus anything name depends on. 'portupgrade -rR name' updates name plus anything name depends on, plus anything that depends on name. In all cases, only ports that have updates available are updated, so if everything in the dependency chain is already up to date, the command (either variant) may do nothing. 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: port upgrading
On Sun, 26 Sep 2010, Dick Hoogendijk wrote: I'm in doubt. I wanted to bring my ports collection uptodate, so I ran csup -L 2 /root/ports-supfile and that updated my ports collection. At least, I hope so. Then I started googling and found that cvsup is not recommended. Better tot use portsnap (???) And also portupgrade was a no go. I should be using portmaster. They are judgement calls. csup is one method, portsnap another. portsnap may be faster, and probably should be the default choice any more (lower bandwidth). portupgrade still works, and many of us still use it. For me, it's just that I almost know how to run portupgrade now, and portmaster didn't seem any better when I tried it. Woh, I'm confused now. Question: what is best used to have an up2date ports collection nowadays? This system is FreeBSD8/amd64. This is an overview of what works for me: http://www.wonkity.com/~wblock/docs/html/portupgrade.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: port upgrading
Woh, I'm confused now. Question: what is best used to have an up2date ports collection nowadays? portsnap fetch extract update for the first time after you've setup the FreeBSD for the very first time. As the parameters used, it fetch the ports tree, extract it to /usr/ports and update it. portsnap fetch update every now and then to update the ports tree. In addition, portmanager does a good job in managing ports in terms of install/update of ports. It doesn't required ports index to find out what is installed or needs to upgrade as it scans the ports tree for dependency, every time. This is good because I don't have to deal with the problem of ports index getting corrupted. Because of this, it does required more time to install/update ports compare to portmaster portupgrade. I've recorded some of my experience in using portmanager : http://scratching.psybermonkey.net/2010/01/freebsd-how-to-manage-ports-in-freebsd.html My 2 cents, Edward. ___ 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: Upgrading from 8.0-Release /
Dear all, Yes, start the upgrade from the beginning again. If this does not work and you don't intend to rollback from a previous update you may take a look at /var/db/freebsd-update and clean it out. OK. I know now. At some point the system asks if changes look reasonable. I pressed y for most cases but with sshd_config I pressed n, because I was not sure whether the changes will not delete some of the changes I implemented within the file. As soon as I did this, the process stopped. Does this look reasonable (y/n)? n # freebsd-update install No updates are available to install. Run '/usr/sbin/freebsd-update fetch' first. The suggested changes were mostly such as: -#VersionAddendum FreeBSD-20090522 +#VersionAddendum FreeBSD-20100308 So it seems I should press y each time? Many thanks! Zbigniew Szalbot ___ 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: Upgrading from 8.0-Release /
On 09/22/2010 08:10 AM, Zbigniew Szalbot wrote: Dear all, Yes, start the upgrade from the beginning again. If this does not work and you don't intend to rollback from a previous update you may take a look at /var/db/freebsd-update and clean it out. OK. I know now. At some point the system asks if changes look reasonable. I pressed y for most cases but with sshd_config I pressed n, because I was not sure whether the changes will not delete some of the changes I implemented within the file. As soon as I did this, the process stopped. Does this look reasonable (y/n)? n # freebsd-update install No updates are available to install. Run '/usr/sbin/freebsd-update fetch' first. The suggested changes were mostly such as: -#VersionAddendum FreeBSD-20090522 +#VersionAddendum FreeBSD-20100308 So it seems I should press y each time? Many thanks! Zbigniew Szalbot OK. Well this is a downside of freebsd-update (with major upgrades mostly), you have to go through these changes. With mergemaster, when doing source upgrades, this can be avoided by having a mergemaster.rc file, but freebsd-update uses another merge program for the config files. The changes that you see: - means this line will be deleted from the config file + means this line will be added to the config file These are the only changes that will be made to the files. You can confirm these changes If you are not sure, make a copy of your sshd_config and go ahead. Before you reboot compare your copy with the 'new' sshd_config and you will see that your modification will still be there. Good luck. DISCLAIMER: This e-mail is for the intended recipient(s) only. Access, disclosure, copying, distribution or reliance on any of it by anyone else is prohibited. If you have received it by mistake please let us know by reply and then delete it from your system. ___ 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
Upgrading from 8.0-Release /
Dear all, I hope you can advise. According to http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html once mergemaster is completed, I should issue freebsd-update install. However, when I do this, I get: # freebsd-update install No updates are available to install. Run '/usr/sbin/freebsd-update fetch' first. However, I did fetch first. 128601287012880128901290012910129201293012940129501296012970 done. Applying patches... done. Fetching 440 files... done. Attempting to automatically merge changes in files... done. So I am not sure where to go from here. Should I try to fetch again, reboot or do something else? I am using FreeBSD 8.0-RELEASE-p4 (GENERIC). Thank you! -- Zbigniew Szalbot ___ 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: Upgrading from 8.0-Release /
On 09/21/2010 03:05 PM, Zbigniew Szalbot wrote: Dear all, I hope you can advise. According to http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html once mergemaster is completed, I should issue freebsd-update install. However, when I do this, I get: # freebsd-update install No updates are available to install. Run '/usr/sbin/freebsd-update fetch' first. However, I did fetch first. 128601287012880128901290012910129201293012940129501296012970 done. Applying patches... done. Fetching 440 files... done. Attempting to automatically merge changes in files... done. So I am not sure where to go from here. Should I try to fetch again, reboot or do something else? I am using FreeBSD 8.0-RELEASE-p4 (GENERIC). Thank you! Sure you don't have a freebsd-update cron running which runs a the time just between executing freebsd-update -r 8.1-RELEASE + merging config files and executing freebsd-update install? I upgraded some boxes to 8.1 and did not see this problem. -- Systeembeheerder OverNite Software Europe BV Dr. Nolenslaan 157 6136 GM Sittard THE NETHERLANDS phone: +31464200933 fax: +31464200934 web: http://www.ose.nl DISCLAIMER: This e-mail is for the intended recipient(s) only. Access, disclosure, copying, distribution or reliance on any of it by anyone else is prohibited. If you have received it by mistake please let us know by reply and then delete it from your system. ___ 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: Upgrading from 8.0-Release /
On 09/21/2010 05:01 PM, Bas Smeelen wrote: On 09/21/2010 03:05 PM, Zbigniew Szalbot wrote: Dear all, I hope you can advise. According to http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html once mergemaster is completed, I should issue freebsd-update install. However, when I do this, I get: # freebsd-update install No updates are available to install. Run '/usr/sbin/freebsd-update fetch' first. However, I did fetch first. 128601287012880128901290012910129201293012940129501296012970 done. Applying patches... done. Fetching 440 files... done. Attempting to automatically merge changes in files... done. So I am not sure where to go from here. Should I try to fetch again, reboot or do something else? I am using FreeBSD 8.0-RELEASE-p4 (GENERIC). Thank you! Sure you don't have a freebsd-update cron running which runs a the time just between executing freebsd-update -r 8.1-RELEASE + merging config files and executing freebsd-update install? I upgraded some boxes to 8.1 and did not see this problem. Sorry, meant between 'freebsd-update -r 8.1-RELEASE upgrade' and 'freebsd-update install' DISCLAIMER: This e-mail is for the intended recipient(s) only. Access, disclosure, copying, distribution or reliance on any of it by anyone else is prohibited. If you have received it by mistake please let us know by reply and then delete it from your system. ___ 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: Upgrading from 8.0-Release /
Hello, Sure you don't have a freebsd-update cron running which runs a the time just between executing freebsd-update -r 8.1-RELEASE + merging config files and executing freebsd-update install? I upgraded some boxes to 8.1 and did not see this problem. No. Nothing automated. That's why I am surprised and not sure what to do next. Do you think I should try to invoke the upgrade (-r 8.1-RELEASE upgrade) command again? -- Zbigniew Szalbot ___ 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: Upgrading from 8.0-Release /
On 09/21/2010 06:59 PM, Zbigniew Szalbot wrote: Hello, Sure you don't have a freebsd-update cron running which runs a the time just between executing freebsd-update -r 8.1-RELEASE + merging config files and executing freebsd-update install? I upgraded some boxes to 8.1 and did not see this problem. No. Nothing automated. That's why I am surprised and not sure what to do next. Do you think I should try to invoke the upgrade (-r 8.1-RELEASE upgrade) command again? Yes, start the upgrade from the beginning again. If this does not work and you don't intend to rollback from a previous update you may take a look at /var/db/freebsd-update and clean it out. DISCLAIMER: This e-mail is for the intended recipient(s) only. Access, disclosure, copying, distribution or reliance on any of it by anyone else is prohibited. If you have received it by mistake please let us know by reply and then delete it from your system. ___ 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: Upgrading packages - portupgrade confusion
[...] Have you refreshed the ports tree(s) with csup using the same supfile to ensure the ports trees are up to date ( and therefore identical)? Since you are using portugrade, as I do, this is what I do to see what needs to be done: I cd to /usr/sup which is where I keep my supfiles and the housekeeping. Then using this command sequence will refresh the ports tree, the ports index database, and ensure the package database is clean and synced. Portversion then just tells you with a symbol any that are old and in need of an update. csup -L 2 ports portsdb -uF pkgdb -u portversion where ports above is my supfile for ports refresh and looks like this: *default host=cvsup.nl.freebsd.org *default base=/usr *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix compress ports-all Then a portupgrade -a as required. If all symbols in the right column are = everything is up to date and nothing is required. Adjust server location for mirror near you (or one that works best). -Mike ___ 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 Thanks alot Mike for the response!! I didn't actually refresh the ports tree so I'm gona have to do that. The thing I don't quite understand though is that if the ports tree gets refreshed, do the packages get upgraded or will I need to rebuild them?? I slightly recall the csup commnad, however I've never actually performed an inplace upgrade of a package in BSD. Only done this kind of thing in Linux - Debian/Ubuntu, CentOS and Solaris - OpenSolaris, Belenix where they have package managers. What's the process for upgrading a package? make reinstall clean?? Many Thanks Kaya ___ 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: Upgrading packages - portupgrade confusion
On Sun, 12 Sep 2010 14:34:52 +0300 Kaya Saman kayasa...@gmail.com articulated: [...] Have you refreshed the ports tree(s) with csup using the same supfile to ensure the ports trees are up to date ( and therefore identical)? Since you are using portugrade, as I do, this is what I do to see what needs to be done: I cd to /usr/sup which is where I keep my supfiles and the housekeeping. Then using this command sequence will refresh the ports tree, the ports index database, and ensure the package database is clean and synced. Portversion then just tells you with a symbol any that are old and in need of an update. csup -L 2 ports portsdb -uF pkgdb -u portversion where ports above is my supfile for ports refresh and looks like this: *default host=cvsup.nl.freebsd.org *default base=/usr *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix compress ports-all Then a portupgrade -a as required. If all symbols in the right column are = everything is up to date and nothing is required. Adjust server location for mirror near you (or one that works best). -Mike Thanks alot Mike for the response!! I didn't actually refresh the ports tree so I'm gona have to do that. The thing I don't quite understand though is that if the ports tree gets refreshed, do the packages get upgraded or will I need to rebuild them?? You have to rebuild them. I slightly recall the csup commnad, however I've never actually performed an inplace upgrade of a package in BSD. Only done this kind of thing in Linux - Debian/Ubuntu, CentOS and Solaris - OpenSolaris, Belenix where they have package managers. What's the process for upgrading a package? make reinstall clean?? If using a port maintenance application such as portupgrade or portmanager, you could simply do the following: portupgrade -a or portmanager -u depending on what application you are using. Switching between multiple port maintenance applications is not the worse thing you could do; however, I would not recommend it as an everyday occurrence. If doing it manually, you could just do: make make deinstall make reinstall make distclean There are other variations of course. I would recommend that you run: make config in the port's home directory prior to building it for the first time. there might be some useful features that you want to turn on or off. -- Jerry ✌ freebsd.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ Minicomputer: A computer that can be afforded on the budget of a middle-level manager. ___ 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: Upgrading packages - portupgrade confusion
Kaya Saman wrote: [...] csup -L 2 ports portsdb -uF pkgdb -u portversion To elaborate a little. csup -L 2 ports is what refreshes the ports tree. Portupgrade is a third party app you can install to assist in automating the updating process. Once you've installed portupgrade there are man pages for portsdb, pkgdb, and portversion to see what the switches described above do. The commands above are just strung together to prepare a system for updating. portupgrade -a is actually what does the actual updating. There are other tools as well, I'm just not as familiar with them. I think the other one is called portmaster. It may even be better, I don't know as I tend to stick with what I know as long as it keeps doing the job. [snip] I didn't actually refresh the ports tree so I'm gona have to do that. The thing I don't quite understand though is that if the ports tree gets refreshed, do the packages get upgraded or will I need to rebuild them?? I don't know if I can properly explain well enough, but I'll take a stab at it anyways. But I believe the first answer here would be no. Refreshing the ports tree does not install or update any installed software. I kind of keyed in on your mentioning of portupgrade. Portupgrade is a tool for automating the upgrading of installed software. While I believe it, and possibly portmaster can operate on pre-built packages I myself stopped using packages a long time ago. I compile everything. A pre-built package is built from the same ports system that you would use if you were compiling locally yourself. It's just someone else has done it for you. The thing to know is that in either situation, e.g. pre-built package or compile it yourself the ports tree is where the versioning and dependency tracking happens. There is more information in the Handbook, and probably presented better there than I can. It is spread out in several locations however. It may not be immediately apparent when reading the How to install software section that you also need to read the other sections further down that explain csup, portmaster, etc. The main thing we will keep reiterating though is the first step for updating installed apps is always refresh the ports tree first. I slightly recall the csup commnad, however I've never actually performed an inplace upgrade of a package in BSD. Only done this kind of thing in Linux - Debian/Ubuntu, CentOS and Solaris - OpenSolaris, Belenix where they have package managers. What's the process for upgrading a package? make reinstall clean?? Since I don't use packages my vantage point is centered around compiling locally myself. However, most of what I describe applies to both situations. Typically the first thing to do is update/refresh the ports tree. Should you determine something needs to be updated the manual approach would be to change to the directory of the app in ports system and do make, followed by make deinstall, and then make reinstall. The deinstall/reinstall leaves your configurations for installed apps in place. Portupgrade is a tool that automates this. After refreshing the ports tree the portupgrade -a command will pretty much do what was described in the previous paragraph automagically. It isn't perfect and sometimes it hiccups. I've noticed that doing this more often so that only a few out of date apps need upgrading at any one time is smoother. It's when you have a hundred things that are really old and out of date because updating has been infrequent is when you are most likely to experience trouble. Hope this helps. I'm not the best at explaining things, but the Handbook is a most excellent resource to be studied extensively. It is written much better than anything I can manage. And while much of it may seem cryptic at first glance, most of what you need to know is in there. -Mike ___ 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: Upgrading packages - portupgrade confusion
Hi Jerry and Michael, thanks for all the advise and information!! I think I was confusing terminologies a little I was trying to imply that I have been building from ports all this time and *not* using pkg_add to obtain pre-built packages. I think mainly it's just that I've been using package managers too much with Linux and OpenSolaris distros that it got burned into my brain. not to mention that yesterday was a 14 hour shift without break which didn't help. The thing I don't quite understand though is that if the ports tree gets refreshed, do the packages get upgraded or will I need to rebuild them?? You have to rebuild them. Does this apply to ports too?? portupgrade -a or portmanager -u depending on what application you are using. Switching between multiple port maintenance applications is not the worse thing you could do; however, I would not recommend it as an everyday occurrence. Ok so portupgrade -a upgrades all ports according to the manual. On 09/12/2010 03:52 PM, Michael Powell wrote: [...] To elaborate a little. csup -L 2 ports is what refreshes the ports tree. Portupgrade is a third party app you can install to assist in automating the updating process. Once you've installed portupgrade there are man pages for portsdb, pkgdb, and portversion to see what the switches described above do. The commands above are just strung together to prepare a system for updating. portupgrade -a is actually what does the actual updating. There are other tools as well, I'm just not as familiar with them. I think the other one is called portmaster. It may even be better, I don't know as I tend to stick with what I know as long as it keeps doing the job. [ Ok, so if I understand correctly now is that the csup command refreshes the ports tree while portupgrade upgrades the actual port itself eg: cd /usr/ports/*/nano make install clean although not the case but say if this was to build version 1.8 of the Nano text editor, running: csup -L 2 portupgrade nano would upgrade the installed version to 1.9?? Of course the current version of Nano is totally different I am just trying to understand here!! [...] I don't know if I can properly explain well enough, but I'll take a stab at it anyways. But I believe the first answer here would be no. Refreshing the ports tree does not install or update any installed software. I kind of keyed in on your mentioning of portupgrade. Portupgrade is a tool for automating the upgrading of installed software. While I believe it, and possibly portmaster can operate on pre-built packages I myself stopped using packages a long time ago. I compile everything. Ok I think this practically explains what I've just been trying to say above. [...] Hope this helps. I'm not the best at explaining things, but the Handbook is a most excellent resource to be studied extensively. It is written much better than anything I can manage. And while much of it may seem cryptic at first glance, most of what you need to know is in there. Yep I think this helps a lot!!! :-) -Mike ___ 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 Many thanks and best regards, Kaya ___ 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: Upgrading packages - portupgrade confusion
On Sun, 12 Sep 2010, Kaya Saman wrote: The thing I don't quite understand though is that if the ports tree gets refreshed, do the packages get upgraded or will I need to rebuild them?? The ports tree is just build instructions, so updating it doesn't update any installed applications. It does let you use a program to see which installed applications need to be updated, like pkg_version or portversion. Here's a document I've been working on lately about upgrading ports. I'm not sure it's really there yet, but it covers the basics: http://www.wonkity.com/~wblock/docs/html/portupgrade.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: Upgrading packages - portupgrade confusion
Kaya Saman wrote: [snip] The thing I don't quite understand though is that if the ports tree gets refreshed, do the packages get upgraded or will I need to rebuild them?? You have to rebuild them. Does this apply to ports too?? Yes. A package is just a port that someone has compiled into a pre-built binary package for use with pkg_add. These binary packages are placed on ftp servers where pkg_add may download from and install. A port is just you doing the compiling locally yourself using the ports system. The installed result is the same, except for one thing. When a package is built some build options may have been selected as defaults while others were excluded. When you build the port locally you have complete control over all options. portupgrade -a or portmanager -u depending on what application you are using. Switching between multiple port maintenance applications is not the worse thing you could do; however, I would not recommend it as an everyday occurrence. Ok so portupgrade -a upgrades all ports according to the manual. [snip] Ok, so if I understand correctly now is that the csup command refreshes the ports tree while portupgrade upgrades the actual port itself Update the ports tree first! csup -L 2 ports - this file ports is a supfile. An example of a supfile was included in a previous mail. More detailed info in the Handbook. eg: cd /usr/ports/*/nano make install clean cd /usr/ports/editors/nano/ make install clean This installs nano when it was not installed before. The manual method to update would be: (with a freshly updated ports tree) cd /usr/ports/editors/nano/ make make deinstall make reinstall although not the case but say if this was to build version 1.8 of the Nano text editor, running: portupgrade nano would upgrade the installed version to 1.9?? Yes - provided you had installed portupgrade and are using an up to date ports tree. If your ports tree is as old as the old version of nano then as far as FreeBSD is concerned it does not know of any new version. Refreshing your ports tree is where that information comes from. The utility of automation with portupgrade really comes into play when you are trying to update more than one port. One port at a time can be done manually as in the above example, but that quickly becomes tiresome when there are many. Sometimes a port may provide a shared library which many other ports depend upon. Updating that library may cause dependent apps to break. In such a situation portupgrade can recurse and rebuild all apps depending on that library so they will be linked against the new. Another tip: Whenever there are situations which can get sticky most of the time notes are placed into a file containing instructions on how to deal with the problem. Get into the habit of always reading the UPDATING file located in /usr/ports so you will know about these *before* updating. [snip] ___ 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: Upgrading packages - portupgrade confusion
Thanks Warren and Michael! :-)
On Sun, 12 Sep 2010, Kaya Saman wrote:
The thing I don't quite understand though is that if the ports tree
gets refreshed, do the packages get upgraded or will I need to rebuild
them??
The ports tree is just build instructions, so updating it doesn't update
any installed applications. It does let you use a program to see which
installed applications need to be updated, like pkg_version or
portversion.
Here's a document I've been working on lately about upgrading ports.
I'm not sure it's really there yet, but it covers the basics:
http://www.wonkity.com/~wblock/docs/html/portupgrade.html
Yep I kinda figured that before even posting and also I knew the
difference between packages built by pkg_add and compiling fresh from
ports since I've done a few BSD builds now but the really iffy thing was
a: communication - which let me down not explaining myself properly and
b: confusion of how to update
On 09/12/2010 05:36 PM, Michael Powell wrote:
[...]
Yes. A package is just a port that someone has compiled into a pre-built
binary package for use with pkg_add. These binary packages are placed on ftp
servers where pkg_add may download from and install.
A port is just you doing the compiling locally yourself using the ports
system. The installed result is the same, except for one thing. When a
package is built some build options may have been selected as defaults while
others were excluded. When you build the port locally you have complete
control over all options.
Ditto :-)
portupgrade -a or portmanager -u depending on what application you
are using. Switching between multiple port maintenance applications is
not the worse thing you could do; however, I would not recommend it as
an everyday occurrence.
Ok so portupgrade -a upgrades all ports according to the manual.
[snip]
Ok, so if I understand correctly now is that the csup command refreshes
the ports tree while portupgrade upgrades the actual port itself
Update the ports tree first! csup -L 2 ports- this file ports is a
supfile. An example of a supfile was included in a previous mail. More
detailed info in the Handbook.
This clarifies, I can't believe what's wrong with me today as I seem to
not be thinking :-(
I picked this up the first time round on a really good production build
that I made and now I lost all that knowledge oh well working with
MS can do that to you I guess??
[...]
Another tip: Whenever there are situations which can get sticky most of the
time notes are placed into a file containing instructions on how to deal
with the problem. Get into the habit of always reading the UPDATING file
located in /usr/ports so you will know about these *before* updating.
[snip]
This is really great advise as I'm kinda in the process of developing
documentation myself similar to Warren:
http://wiki.optiplex-networks.com/xwiki/bin/view/FreeBSD/
Luckily I build all my systems in jails so is easily managed and doesn't
blow up the whole system, however I do share the ports tree throughout
all jails and the base install meaning that things get simplified
although it can have its own problems such as version inconsistencies etc...
{{PS. this is also due to the fact that I only one available production
system and can't afford to get more although soon I hope to one day}}
Thanks so much guys and sorry for being so noobish these last 2 days,
just sorry you all had to put up with it!! :-)
Anyway best regards to all and hopefully mail along side you guys
helping out others some sunny day in the future :-D
Kaya
___
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
Upgrading packages - portupgrade confusion
Hi, I have 2 servers one production and another test. The test machine's packages however, seem to be older then the production machines one's even though I built the production system a few months ago. I used the: portupgrade command in order to try to upgrade the ports nad re-install the packages only the same versions seem to be compiling??? I ran: portupgrade -ai on the base system as the system where these packages are installed into is a FreeBSD jail. The ports in question are these: tomcat-6.0.29 Open-source Java web server by Apache, 6.x branch postgresql-client-8.2.17_1 PostgreSQL database (client) postgresql-server-8.2.17_1 The most advanced open-source database available anywhere Which on my newer test system show up as such: postgresql-client-8.2.13 PostgreSQL database (client) postgresql-server-8.2.13 The most advanced open-source database available anywhere tomcat-6.0.20_1 Open-source Java web server by Apache, 6.x branch I don't understand this 100%??? I would like the versions to be the same as the production system since I have a postgres-Tomcat connector which doesn't work on the test setup as my Tomcat webapp isn't being displayed!! Can I do anything about this?? I don't even know why it is like this although I must admit that it has been an exceptionally long day and am really suffering from fatigue now which might be a contributor but I can't tell. Can anyone give me any advise?? Many thanks and best regards, Kaya ___ 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: Upgrading packages - portupgrade confusion
Kaya Saman wrote: Hi, I have 2 servers one production and another test. The test machine's packages however, seem to be older then the production machines one's even though I built the production system a few months ago. I used the: portupgrade command in order to try to upgrade the ports nad re-install the packages only the same versions seem to be compiling??? I ran: portupgrade -ai on the base system as the system where these packages are installed into is a FreeBSD jail. The ports in question are these: tomcat-6.0.29 Open-source Java web server by Apache, 6.x branch postgresql-client-8.2.17_1 PostgreSQL database (client) postgresql-server-8.2.17_1 The most advanced open-source database available anywhere Which on my newer test system show up as such: postgresql-client-8.2.13 PostgreSQL database (client) postgresql-server-8.2.13 The most advanced open-source database available anywhere tomcat-6.0.20_1 Open-source Java web server by Apache, 6.x branch I don't understand this 100%??? I would like the versions to be the same as the production system since I have a postgres-Tomcat connector which doesn't work on the test setup as my Tomcat webapp isn't being displayed!! Can I do anything about this?? I don't even know why it is like this although I must admit that it has been an exceptionally long day and am really suffering from fatigue now which might be a contributor but I can't tell. Can anyone give me any advise?? Have you refreshed the ports tree(s) with csup using the same supfile to ensure the ports trees are up to date ( and therefore identical)? Since you are using portugrade, as I do, this is what I do to see what needs to be done: I cd to /usr/sup which is where I keep my supfiles and the housekeeping. Then using this command sequence will refresh the ports tree, the ports index database, and ensure the package database is clean and synced. Portversion then just tells you with a symbol any that are old and in need of an update. csup -L 2 ports portsdb -uF pkgdb -u portversion where ports above is my supfile for ports refresh and looks like this: *default host=cvsup.nl.freebsd.org *default base=/usr *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix compress ports-all Then a portupgrade -a as required. If all symbols in the right column are = everything is up to date and nothing is required. Adjust server location for mirror near you (or one that works best). -Mike ___ 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
wine doesnot work after upgrading to 8.1?
The wine works great when using freebsd 8.0. Yesterday i upgrading FB 8.0 to 8.1, the wine cannot display window without any message even if reinstalling wine under FB 8.1 . uname -a FreeBSD mybsd.zsoft.com 8.1-RELEASE FreeBSD 8.1-RELEASE #1: Wed Sep 8 09:07:54 CST 2010 r...@mybsd.zsoft.com:/media/G/usr/obj/media/G/usr/src/sys/MYKERNEL i386 pkg_info|grep wine wine-1.3.2_2,1 Microsoft Windows compatibility layer for Unix-like systems Any suggestion is appreciated! - e^(π⋅i) + 1 = 0 -- View this message in context: http://old.nabble.com/wine-doesnot-work-after-upgrading-to-8.1--tp29673647p29673647.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ 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: Upgrading ports while processes are running.
On 17.08.10 04:13, Mark Shroyer wrote: That isn't to say you won't see any negative consequences from overwriting a running port with a newer version. Hypothetically, you might install a new Python including a new standard library, and if your running (old) Python process tries to load one of its deleted modules from disk something could break. Or not; I'm no expert on the ports system, they might have some way of working around this. But as for a pragmatic answer to your question, I err on the side of caution with this stuff Wow, thanks for this perfect description how this is working. For my part, I am updating since many years regularly the ports. Never stop any daemon before. But after the upgrade I restart the daemon if it is something like apache, clamav, some milters, mysql. It never causes trouble. The only thing that if I use restart, rc says the daemon is not running (but running fine) . But after reading Your article it is now clear why. Beat ___ 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: Upgrading ports while processes are running.
On Tue, 17 Aug 2010 10:17:23 +0200 Beat Siegenthaler beat.siegentha...@beatsnet.com wrote: It never causes trouble. The only thing that if I use restart, rc says the daemon is not running (but running fine) . But after reading Your article it is now clear why. I don't think it should be. Most daemons write their pid (process ID) to a pid-file on startup. When you stop an rc script it reads the pid-file and checks to see that there is a process with that pid and which has the correct command line. If no match is found you get that warning. Reinstalling a port shouldn't affect the pid file. ___ 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: Upgrading ports while processes are running.
On 17/08/2010 12:13 PM, Mark Shroyer wrote: On Tue, 17 Aug 2010 03:23:27 +0200, Polytropon free...@edvax.de wrote: At least, the step that wants to write will fail, and this will mostly be (finally) signaled by a make error. snip! That isn't to say you won't see any negative consequences from overwriting a running port with a newer version. Hypothetically, you might install a new Python including a new standard library, and if your running (old) Python process tries to load one of its deleted modules from disk something could break. Or not; I'm no expert on the ports system, they might have some way of working around this. But as for a pragmatic answer to your question, I err on the side of caution with this stuff :) Thanks for the info... I guess I can take this to read: The way install works, the binary files can be updated even though they are in use. Restart of the port (or it's deps in the case of libs) is required. If nothing is restarted, then the old process code happily resides in memory until it's no longer referenced. This can cause a problem with a dynamically loaded lib that is not the same version as expected. I wonder what happens when you upgrade a port, don't restart, then the following week upgrade it again hmmm. In any case I like the restart the whole server option after a major upgrade because if it works then I can essentially rule out the upgrade if I have to troubleshoot a problem at a later date. -D ___ 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: Upgrading ports while processes are running.
On Tue 17 Aug 2010 at 15:05:27 PDT Danny Carroll wrote: I wonder what happens when you upgrade a port, don't restart, then the following week upgrade it again hmmm. I don't think it would be any different than not restarting it after the first upgrade (assuming the port doesn't try to open any libraries or data files that aren't already opened and that the second upgrade changes but the first upgrade does not.) As already explained, the inodes for the original files would still be valid, and so would any file handles the program has open. ___ 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
Upgrading ports while processes are running.
Hiya All, I just finished upgrading perl on one of my machines and something crossed my mind while it was busy compiling and reinstalling all of the ports that depended on perl. Will a port install fail if it cannot write to a file because it's in-use? Also, is it necessary to restart the server or at lease the apps after a port upgrade? The answer to the second question is certainly yes. But is it considered dangerous to upgrade a port that is currently running? Things like mysql and apache come to mind. To take it one step further, what about shared libraries? If a process is using a shared lib, then it seems that it does not lock the file for writing, but I would think that it would not start using the lib until you restarted all of the processes that used that shared lib. Once the last process using the shared lib is killed, is it automatically unlinked from memory? I guess best practice should be to restart the system after a major port upgrade (unless you know which processes depend on the files that have been upgraded - then you should just be able to restart those processes). -D ___ 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: Upgrading ports while processes are running.
On Tue, 17 Aug 2010 10:01:03 +1000, Danny Carroll f...@dannysplace.net wrote: Will a port install fail if it cannot write to a file because it's in-use? At least, the step that wants to write will fail, and this will mostly be (finally) signaled by a make error. UNIX doesn't have a file in use paradigm per se; i. e. you can open one and the same file in two editors simultaneously, and depending on which editor performs SAVE FILE, the file's content on disk will vary. Of course, there's file locking (see man flock). Also, is it necessary to restart the server or at lease the apps after a port upgrade? This depends on the programs. In most cases, it's useful to stop a kind of server app before performing the update, and then restarting it after the upgrade has been performed. Restarting the server isn't neccessary in most cases. You usually won't have much trouble with programs that are started many times (like editor, media player), as they will surely survive an update, and don't affect the system if they won't. The answer to the second question is certainly yes. But is it considered dangerous to upgrade a port that is currently running? Things like mysql and apache come to mind. I always went with the method stop, upgrade, start - it's not that short downtimes (planned!) have gotten me into trouble. :-) To take it one step further, what about shared libraries? If a process is using a shared lib, then it seems that it does not lock the file for writing, but I would think that it would not start using the lib until you restarted all of the processes that used that shared lib. Once the last process using the shared lib is killed, is it automatically unlinked from memory? I think so, allthough I think there's a caching mechanism for shared libraries (ld cache). I guess best practice should be to restart the system after a major port upgrade (unless you know which processes depend on the files that have been upgraded - then you should just be able to restart those processes). Most server apps provide rc.d style scripts which makes it quite easy to cleanly stop them before the update, so you don't have to manually hunt processes. This mechanism enables you to selectively prevent programs from being interfered by their respective updating procedures. A system reboot is highly encouraged when updating the OS or kernel components. If you are unsure and don't care for uptime, you *can* reboot, as it won't make things worse. :-) -- 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: Upgrading ports while processes are running.
On Tue, 17 Aug 2010 03:23:27 +0200, Polytropon free...@edvax.de wrote:
At least, the step that wants to write will fail, and this will
mostly be (finally) signaled by a make error.
This is sort of pedantic for me to bring up, but I wouldn't count on the
install failing. Because Unix makes a distinction between unlinking and
file deletion, you can generally unlink the binary of a running
executable without any problem; the filesystem won't actually delete it
at least until the process in question stops running and the inode's
reference count drops to zero. See Advanced Programming in the Unix
Environment for details.
Here's a quick example on FreeBSD:
$ cat hello.c
#include stdio.h
int main(int argc, char* argv[])
{
while (1) {
printf(Hello\n);
sleep(1);
}
return 0;
}
$ cc -o hello hello.c
$ ./hello
This simple program will start printing Hello repeatedly. Now if I
switch to another terminal, I can delete the hello binary:
$ rm hello
But switching back to the first terminal, I see the program is still
running just fine. Running programs can be unlinked.
And this is what the install program used by FreeBSD ports appears to
do; from /usr/src/usr.bin/xinstall/install.c:
create_newfile(const char *path, int target, struct stat *sbp)
{
char backup[MAXPATHLEN];
int saved_errno = 0;
int newfd;
if (target) {
/*
* Unlink now... avoid ETXTBSY errors later. Try to turn
* off the append/immutable bits -- if we fail, go ahead,
* it might work.
*/
if (sbp-st_flags NOCHANGEBITS)
(void)chflags(path, sbp-st_flags ~NOCHANGEBITS);
if (dobackup) {
if ((size_t)snprintf(backup, MAXPATHLEN, %s%s,
path, suffix) != strlen(path) + strlen(suffix))
errx(EX_OSERR, %s: backup filename too long,
path);
(void)snprintf(backup, MAXPATHLEN, %s%s,
path, suffix);
if (verbose)
(void)printf(install: %s - %s\n,
path, backup);
if (rename(path, backup) 0)
err(EX_OSERR, rename: %s to %s, path, backup);
} else
if (unlink(path) 0)
saved_errno = errno;
}
newfd = open(path, O_CREAT | O_RDWR | O_TRUNC, S_IRUSR | S_IWUSR);
if (newfd 0 saved_errno != 0)
errno = saved_errno;
return newfd;
}
That isn't to say you won't see any negative consequences from
overwriting a running port with a newer version. Hypothetically, you
might install a new Python including a new standard library, and if your
running (old) Python process tries to load one of its deleted modules
from disk something could break. Or not; I'm no expert on the ports
system, they might have some way of working around this. But as for a
pragmatic answer to your question, I err on the side of caution with
this stuff :)
--
Mark Shroyer
http://markshroyer.com/contact/
___
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
Upgrading Boot Loader
Hi, I want to update my boot loader based on upgrading to FreeBSD 8.1. I originally installed FreeBSD 8.0 using the zfsinstall utility available at http://mfsbsd.vx.sk/ and so my tank zpool is currently using version 13, whereas my other non-boot zpool is using version 14. After upgrading (via make buildworld buildkernel installkernel installworld) to FreeBSD 8.1, running zpool status tells me: The pool is formatted using an older on-disk format. The pool can still be used, but some features are unavailable. Upgrade the pool using 'zpool upgrade'. Once this is done, the pool will no longer be accessible on older software versions. I vaguely remember reading that the zfsboot and/or zfsloader need to be updated properly before you upgrade your root zfs pool or the loader won't be able to boot from that partition. So, my question is: how do I update the zfsboot and/or zfsloader to the new version? I've read that bsdlabel can install new boot code, but I'm not sure which one of those files (or both) need to be used. My best guess is that I need to run: bsdlabel -B -b /boot/zfsboot Is that correct? Is there anything else I should do? What's the proper way to roll back in the event that the system becomes unbootable? Tim Gustafson Baskin School of Engineering UC Santa Cruz t...@soe.ucsc.edu 831-459-5354 ___ 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: Upgrading Boot Loader
02.08.2010 21:49, Tim Gustafson написав(ла): Hi, I want to update my boot loader based on upgrading to FreeBSD 8.1. I originally installed FreeBSD 8.0 using the zfsinstall utility available at http://mfsbsd.vx.sk/ and so my tank zpool is currently using version 13, whereas my other non-boot zpool is using version 14. After upgrading (via make buildworld buildkernel installkernel installworld) to FreeBSD 8.1, running zpool status tells me: The pool is formatted using an older on-disk format. The pool can still be used, but some features are unavailable. Upgrade the pool using 'zpool upgrade'. Once this is done, the pool will no longer be accessible on older software versions. I vaguely remember reading that the zfsboot and/or zfsloader need to be updated properly before you upgrade your root zfs pool or the loader won't be able to boot from that partition. So, my question is: how do I update the zfsboot and/or zfsloader to the new version? I've read that bsdlabel can install new boot code, but I'm not sure which one of those files (or both) need to be used. My best guess is that I need to run: bsdlabel -B -b /boot/zfsboot Is that correct? Is there anything else I should do? What's the proper way to roll back in the event that the system becomes unbootable? Nope. Read http://www.mail-archive.com/freebsd-sta...@freebsd.org/msg103917.html You need the dd sequence. And you need to do that on exported pool. -- Sphinx of black quartz judge my vow. ___ 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: Upgrading Boot Loader
Nope. Read http://www.mail-archive.com/freebsd-sta...@freebsd.org/msg103917.html You need the dd sequence. And you need to do that on exported pool. So, just to be clear, I need to boot off a USB key (which will then allow me to write to ad8 and ad10, my two boot zpool devices), and then: dd if=/boot/zfsboot of=/dev/ad8 bs=512 count=1 dd if=/boot/zfsboot of=/dev/ad10 bs=512 count=1 dd if=/boot/zfsboot of=/dev/ad8 bs=512 skip=1 seek=1024 dd if=/boot/zfsboot of=/dev/ad10 bs=512 skip=1 seek=1024 And that assumes that I copy the newly-compiled zfsboot to the USB key after creating it, correct? Tim Gustafson Baskin School of Engineering UC Santa Cruz t...@soe.ucsc.edu 831-459-5354 ___ 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: Upgrading Boot Loader
02.08.2010 22:11, Tim Gustafson wrote: Nope. Read http://www.mail-archive.com/freebsd-sta...@freebsd.org/msg103917.html You need the dd sequence. And you need to do that on exported pool. So, just to be clear, I need to boot off a USB key (which will then allow me to write to ad8 and ad10, my two boot zpool devices), and then: dd if=/boot/zfsboot of=/dev/ad8 bs=512 count=1 dd if=/boot/zfsboot of=/dev/ad10 bs=512 count=1 dd if=/boot/zfsboot of=/dev/ad8 bs=512 skip=1 seek=1024 dd if=/boot/zfsboot of=/dev/ad10 bs=512 skip=1 seek=1024 And that assumes that I copy the newly-compiled zfsboot to the USB key after creating it, correct? Yes. PS: I've just recently changed my mind and moved from dedicated vdevs to gpart. This gives possibility of: 1. Having raw swap partition suitable for swapping/dumping. 2. Updating bootcode online without loosing uptime. Just in expense of some kilobytes of disk space. -- Sphinx of black quartz judge my vow. ___ 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: Upgrading Boot Loader
PS: I've just recently changed my mind and moved from dedicated vdevs to gpart. This gives possibility of: 1. Having raw swap partition suitable for swapping/dumping. 2. Updating bootcode online without loosing uptime. Just in expense of some kilobytes of disk space. I too am using gpart to partition the drives: ad8 and ad10 are partitioned using gpart. I'm attaching the output of gpart list to this e-mail. Is there an easier/better way to upgrade the boot loader with gpart partitions? Tim Gustafson Baskin School of Engineering UC Santa Cruz t...@soe.ucsc.edu 831-459-5354Geom name: ad8 fwheads: 16 fwsectors: 63 last: 1953525134 first: 34 entries: 128 scheme: GPT Providers: 1. Name: ad8p1 Mediasize: 65536 (64K) Sectorsize: 512 Mode: r0w0e0 rawtype: 83bd6b9d-7f41-11dc-be0b-001560b84f0f label: (null) length: 65536 offset: 17408 type: freebsd-boot index: 1 end: 161 start: 34 2. Name: ad8p2 Mediasize: 17179869184 (16G) Sectorsize: 512 Mode: r1w1e1 rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b label: (null) length: 17179869184 offset: 82944 type: freebsd-swap index: 2 end: 33554593 start: 162 3. Name: ad8p3 Mediasize: 983024916992 (916G) Sectorsize: 512 Mode: r1w1e1 rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b label: (null) length: 983024916992 offset: 17179952128 type: freebsd-zfs index: 3 end: 1953525134 start: 33554594 Consumers: 1. Name: ad8 Mediasize: 1000204886016 (932G) Sectorsize: 512 Mode: r2w2e4 Geom name: ad10 fwheads: 16 fwsectors: 63 last: 1953525134 first: 34 entries: 128 scheme: GPT Providers: 1. Name: ad10p1 Mediasize: 65536 (64K) Sectorsize: 512 Mode: r0w0e0 rawtype: 83bd6b9d-7f41-11dc-be0b-001560b84f0f label: (null) length: 65536 offset: 17408 type: freebsd-boot index: 1 end: 161 start: 34 2. Name: ad10p2 Mediasize: 17179869184 (16G) Sectorsize: 512 Mode: r0w0e0 rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b label: (null) length: 17179869184 offset: 82944 type: freebsd-swap index: 2 end: 33554593 start: 162 3. Name: ad10p3 Mediasize: 983024916992 (916G) Sectorsize: 512 Mode: r1w1e1 rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b label: (null) length: 983024916992 offset: 17179952128 type: freebsd-zfs index: 3 end: 1953525134 start: 33554594 Consumers: 1. Name: ad10 Mediasize: 1000204886016 (932G) Sectorsize: 512 Mode: r1w1e2 ___ 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: Upgrading Boot Loader
02.08.2010 22:29, Tim Gustafson написав(ла): PS: I've just recently changed my mind and moved from dedicated vdevs to gpart. This gives possibility of: 1. Having raw swap partition suitable for swapping/dumping. 2. Updating bootcode online without loosing uptime. Just in expense of some kilobytes of disk space. I too am using gpart to partition the drives: ad8 and ad10 are partitioned using gpart. I'm attaching the output of gpart list to this e-mail. Is there an easier/better way to upgrade the boot loader with gpart partitions? Then you have no need in zfsboot, you shoud use gptzfsboot instead. gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ad8 gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ad10 This will install Protective MBR to first disk sector and bootcode to first partition. You can backup them just-in-case or update one disk and try to boot from it leaving second as the known to work solution. -- Sphinx of black quartz judge my vow. ___ 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
