Ben Munat wrote: > Calculating world dependencies . ...done! > [ebuild U ] net-dns/bind-9.2.5 [9.2.2-r3] > [ebuild U ] dev-php/php-4.3.11 [4.3.10] > [ebuild U ] sys-devel/gcc-config-1.3.10-r2 [1.3.6-r3] > [ebuild U ] sys-devel/gcc-3.3.5.20050130-r1 [3.3.5-r1] > [ebuild U ] dev-db/postgresql-8.0.1-r2 [7.4.7-r1] > [ebuild U ] sys-devel/libtool-1.5.14 [1.5.10-r4] > [ebuild U ] mail-filter/qmail-scanner-1.25-r1 [1.25] > [ebuild NS ] dev-php/mod_php-4.3.11 > [ebuild U ] www-servers/tomcat-5.0.27-r5 [5.0.27-r4] > [ebuild N ] sys-devel/binutils-config-1.8-r2 > [ebuild U ] sys-devel/binutils-2.15.92.0.2-r7 [2.15.92.0.2-r1] > [ebuild NS ] dev-db/phpmyadmin-2.6.2_rc1 > > > Seeing gcc, libtool and binutils mixed in there makes me a little wary. > Just thought I'd check to see if anyone's heard about any gaffes or > issues of late? Also, anyone know why mod_php (but not php) is slotted now?
The way I usually do these types of updates is: 1) Security update will go first 2) If its a toolchain app (gcc/binutils/etc), wait a week or two for it being in stable to see if any bugs are worked around 3) If its an app that isn't going to affect that much, go ahead and upgrade it. For the example above I would do the php/mod_php first since its a security update (or will be shortly if the GLSA hasn't been released). Then I would do phpmyadmin. After that its up to you. If its really a pain to update the others, just put them in your /etc/portage/package.mask file so you won't accidentally update it. Also, for those major updates, after the 1-2 weeks of waiting, I usually check the ML's/forums/bugs/changelog to see if there are any on going major issues and to see if anything major happened to people. Anyways, thats how I usually deal with upgrades :) -- Lance Albertson <[EMAIL PROTECTED]> Gentoo Infrastructure | Operational Manager --- Public GPG key: <http://www.ramereth.net/lance.asc> Key fingerprint: 0423 92F3 544A 1282 5AB1 4D07 416F A15D 27F4 B742 ramereth/irc.freenode.net
signature.asc
Description: OpenPGP digital signature
