13 Jan
2014
13 Jan
'14
7:08 p.m.
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 package database contains either both the old pth and old libgcrypt, or both the new pth and new libgcrypt.
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 would be related in any way.