On Tue, 6 Nov 2007 14:29:50 +0100 Dirk Kredler <[EMAIL PROTECTED]> wrote:
> Hello! > > Thank you all for the responses! > > Am Dienstag, 6. November 2007 13:55:19 schrieb RedShift: > > > > Testing it on a non-production box helps ;-) > > > > Yes. I will do that - at least for the server... but unfortunately i > dont have the ressources to double all machines ;-) > > > > > > So heres is my decision: > > > - no "pacman -Syu" will ever happen again, instead i do "pacman > > > -Su" and "pacman -U <pkg>" for choosen packages and immeadiate > > > test, to check that the update was OK. > > > > Then Archlinux is not the distribution for you. > > Why? Isnt it ok to update only selected packages? > Are there any problems that arise if i do so? > > I do it this way on the servers (no kernel or fcpci updates anymore) > - that should be save, or can i run into other problems? > > # pacman -Sy > # pacman -Qu > > than i choose what to update and do > # pacman -U <pgk> > > are there any problems with that? > Do i need to do a "pacman -Syu" to run ArchLinux? (i hope not) You have to be very careful if you do it this way - you have to upgrade the package you _want_ AND all of its dependencies. Otherwise, you'll frequently run into problems where the upgraded version of your app can't find the right libraries, because the libs on your system are too old. -- Travis _______________________________________________ arch mailing list arch@archlinux.org http://archlinux.org/mailman/listinfo/arch
