Even though the root of this problem only lasted for 20 minutes, the
effect could be felt later as well, due to mirrors lagging behind.
The problem may be fixed now, but I think a news item would be in
order, since people rely on it for information about problems that
could arise when upgrading pa
On вто, 14 јан 2014 13:26:15 CET, Allan McRae wrote:
On 14/01/14 22:13, Damjan wrote:
On 13.01.2014 22:52, Thomas Bächler wrote:
Am 13.01.2014 22:48, schrieb Mark Lee:
Salutations,
All right then; if it works for you guys. Will an announcement be made
on the arch website to ensure the upgrade
On 14/01/14 22:13, Damjan wrote:
> On 13.01.2014 22:52, Thomas Bächler wrote:
>> Am 13.01.2014 22:48, schrieb Mark Lee:
>>> 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
>>> wil
I confirm
[killruana@fanstasmic tmp]$ gpg --verify
libgcrypt-1.6.0-1-i686.pkg.tar.xz.sig
gpg: Signature made Mon Dec 16 23:30:48 2013 CET using RSA key ID 0F2A092B
gpg: Good signature from "Andreas Radke "
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no
On 13.01.2014 22:52, Thomas Bächler wrote:
Am 13.01.2014 22:48, schrieb Mark Lee:
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 mirr
On 2014-01-13 10:17, Sebastian Lipp wrote:
> On 2014-01-13 10:06, Sebastian Lipp wrote:
> > On 2014-01-13 02:10, guns wrote:
> > > On Mon 13 Jan 2014 at 08:08:47PM +0100, Thomas Bächler wrote:
> > > > Am 13.01.2014 19:33, schrieb Mark E. Lee:
> > > > > 3) Failure to update libgcrypt before other pa
On 2014-01-13 10:06, Sebastian Lipp wrote:
> On 2014-01-13 02:10, guns wrote:
> > On Mon 13 Jan 2014 at 08:08:47PM +0100, Thomas Bächler wrote:
> > > Am 13.01.2014 19:33, schrieb Mark E. Lee:
> > > > 3) Failure to update libgcrypt before other packages resulted in a
> > > > kernel that seemed to be
On 2014-01-13 02:10, guns wrote:
> On Mon 13 Jan 2014 at 08:08:47PM +0100, Thomas Bächler wrote:
> > Am 13.01.2014 19:33, schrieb Mark E. Lee:
> > > 3) Failure to update libgcrypt before other packages resulted in a
> > > kernel that seemed to be hung at booting.
> >
> > Sorry, I can't see how that
On Mon, 2014-01-13 at 22:52 +0100, Thomas Bächler wrote:
> Am 13.01.2014 22:48, schrieb Mark Lee:
> > 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 wai
Am 13.01.2014 22:48, schrieb Mark Lee:
> 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 a
On Mon 13 Jan 2014 at 10:42:47PM +0100, Thomas Bächler wrote:
> Am 13.01.2014 20:34, schrieb Mark Lee:
>
> > 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
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
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 l
On Mon, 13 Jan 2014 at 21:30:53, guns wrote:
> On Mon 13 Jan 2014 at 03:12:33PM -0500, Mark Lee wrote:
> >
> > I don't have encrypt in my mkinitcpio hooks.
>
> Regardless, the sync state of the mirrors we pulled from
> are inconsistent. In my case, my top mirrors are all listed
> under "Successful
On Mon, 2014-01-13 at 20:08 +0100, Thomas Bächler wrote:
> Am 13.01.2014 19:33, schrieb Mark E. Lee:
> > However, I suggest an announcement on the website regarding this
> > problem.
>
> No.
>
> > I had three issues when trying to solve this problem:
> > 1) the mirror I was using wasn't up to dat
On Mon, 2014-01-13 at 14:30 -0600, guns wrote:
> On Mon 13 Jan 2014 at 03:12:33PM -0500, Mark Lee wrote:
> >
> > I don't have encrypt in my mkinitcpio hooks.
>
> Regardless, the sync state of the mirrors we pulled from
> are inconsistent. In my case, my top mirrors are all listed
> under "Successf
On Mon 13 Jan 2014 at 03:12:33PM -0500, Mark Lee wrote:
>
> I don't have encrypt in my mkinitcpio hooks.
Regardless, the sync state of the mirrors we pulled from
are inconsistent. In my case, my top mirrors are all listed
under "Successfully Syncing Mirrors" with 100% completion at
https://www.arc
On Mon, 2014-01-13 at 14:10 -0600, guns wrote:
> On Mon 13 Jan 2014 at 08:08:47PM +0100, Thomas Bächler wrote:
> > Am 13.01.2014 19:33, schrieb Mark E. Lee:
> >
> > > I had three issues when trying to solve this problem:
> > > 1) the mirror I was using wasn't up to date (still had
> > > libgcrypt-1
On Mon 13 Jan 2014 at 08:08:47PM +0100, Thomas Bächler wrote:
> Am 13.01.2014 19:33, schrieb Mark E. Lee:
>
> > I had three issues when trying to solve this problem:
> > 1) the mirror I was using wasn't up to date (still had
> > libgcrypt-1.5.3-1)
>
> You see, that is impossible. The package databa
On Mon, 2014-01-13 at 14:19 -0500, Mark Lee wrote:
> On Mon, 2014-01-13 at 20:08 +0100, Thomas Bächler wrote:
> > Am 13.01.2014 19:33, schrieb Mark E. Lee:
> > > However, I suggest an announcement on the website regarding this
> > > problem.
> >
> > No.
> >
> > > I had three issues when trying to
On Mon, 2014-01-13 at 20:08 +0100, Thomas Bächler wrote:
> Am 13.01.2014 19:33, schrieb Mark E. Lee:
> > However, I suggest an announcement on the website regarding this
> > problem.
>
> No.
>
> > I had three issues when trying to solve this problem:
> > 1) the mirror I was using wasn't up to dat
On Mon, 2014-01-13 at 20:08 +0100, Thomas Bächler wrote:
> Am 13.01.2014 19:33, schrieb Mark E. Lee:
> > However, I suggest an announcement on the website regarding this
> > problem.
>
> No.
>
> > I had three issues when trying to solve this problem:
> > 1) the mirror I was using wasn't up to dat
Am 13.01.2014 19:33, schrieb Mark E. Lee:
> However, I suggest an announcement on the website regarding this
> problem.
No.
> I had three issues when trying to solve this problem:
> 1) the mirror I was using wasn't up to date (still had
> libgcrypt-1.5.3-1)
You see, that is impossible. The packa
On Mon, 2014-01-13 at 19:13 +0100, Armin K. wrote:
> On 01/13/2014 07:08 PM, Mark E. Lee wrote:
> > Salutations!
> >
> > After an upgrade of my entire system, I am now unable to install
> > packages or run any programs that depend on libgcrypt. I get the
> > following error : libgrypt.so.20 not fo
On 01/13/2014 07:08 PM, Mark E. Lee wrote:
> Salutations!
>
> After an upgrade of my entire system, I am now unable to install
> packages or run any programs that depend on libgcrypt. I get the
> following error : libgrypt.so.20 not found.
>
> Looking at my pacman logs it seems that This error ap
Salutations!
After an upgrade of my entire system, I am now unable to install
packages or run any programs that depend on libgcrypt. I get the
following error : libgrypt.so.20 not found.
Looking at my pacman logs it seems that This error appeared after an
update to pth (2.0.7-4 -> 2.0.7-5). I've
26 matches
Mail list logo
