On Mon, 2014-01-13 at 22:42 +0100, Thomas Bächler wrote: > Am 13.01.2014 20:34, schrieb Mark Lee: > > On Mon, 2014-01-13 at 14:19 -0500, Mark Lee wrote: > >> The reason why packages couldn't upgrade was because of gnupg which is > >> needed for package signature verification from pacman. An updated gnupg > >> points to libgcrypt.so.20 while the old one points to libgcrypt.so.11. > >> Hence, what has to be done is gnupg must be updated before libgcrypt (or > >> else signature verification fails). Libgcrypt must be updated before the > >> system is rebooted or else gnupg fails. > >> > >> Hence, an advisory should be sent out that gnupg should be updated > >> before libgcrypt, and libgcrypt should be updated before the system's > >> ever rebooted. > > > > Salutations, > > > > Actually scratch that, one should install gnupg 2.0.22-2 and libgcrypt > > 1.6.0-1 simultaneously (same pacman line) before trying to install other > > things. > > That is all nonsense. Everything must be updated in a single transaction > using `pacman -Syu`. This has been done by countless [testing] users in > December without a single reported problem. > > Salutations, All right then; if it works for you guys. Will an announcement be made on the arch website to ensure the upgrade doesn't break more systems or will we continue the wait game and hope that all the mirrors sync and the issue just goes away? Regards, Mark -- Mark Lee <mark@xxxxxxxxxxxx>
