On Thu, 24 Jan 2013 10:21:12 +0100 arnaud gaboury <arnaud.gaboury@xxxxxxxxx> wrote: > On Wed, Jan 23, 2013 at 11:44 AM, Ralf Mardorf > <ralf.mardorf@xxxxxxxxxxxxx>wrote: > > > On Wed, 23 Jan 2013 11:25:16 +0100, Thomas Bächler <thomas@xxxxxxxxxxxxx> > > wrote: > > > >> Am 23.01.2013 11:10, schrieb arnaud gaboury: > >> > >>> Let me clarify a few things. > >>> 1- I didn't correctly understand the post from Allan about toolchain, > >>> thus > >>> my brocken update when #pacman - S filesystem > >>> > >> > >> Then why do you use testing? > >> > >> 2- As a newbye, > >>> > >> > >> Then why do you use testing? > >> > > > > Perhaps the OP needs a clarification. Arch Linux is a rolling release, you > > usually get latest software versions for a regular Arch install. For my > > taste sometimes the versions come to the repository too fast (at the moment > > I take a rest from Arch Linux, but I still recommend to use it and will use > > it in the future myself again). It's not comparable to testing of "release > > distros", were for stable releases software sometimes is outdated for the > > needs of some users and developers. > > > > When you are experienced using testing is helpful, to test new packages, > > since this would help the community. As long as you're a novice, you very > > unlikely will benefit from using testing. > > > > pacman -Syuu ;) > > > > Regards, > > Ralf > > > > Thank you Ralf, but this is my first ever serious issue when upgrading, so > I will stick with dev enabled. > > Following Allan instructions, on Archiso, I #pacman -Qk and no missing > files were returns. > Then #mkinitcpio -p linux > > I was thereafter happy to log into my system, with no kernel panic ! > I decided to reinstall all packages from the "broken" upgrade. > > Nevertheless, everything is not fine. Somme apps are broken, and do not > know why. I guess it is because of the /usr/lib64 issue. > For example, offlineimap and log are broken with no reasons, as they used > to work perfectly. There is always a reason... but it's not /usr/lib64. > > Allan, I think this upgrade is worth a news, as you mentioned it this > morning. > > I am always scare each time I run #pacman -Syu, as I know it could be > tricky. I usually pay very much attention, and this particular upgrade was > my first real issue leaving me with a broken system. > I may think breaking/fixing our system is the only way we learn. > > Thank you for your great work to the Arch community. > > Regards. -- Leonid Isaev GnuPG key: 0x164B5A6D Fingerprint: C0DF 20D0 C075 C3F1 E1BE 775A A7AE F6CB 164B 5A6D
Attachment:
signature.asc
Description: PGP signature
