Bug#984884: libgcrypt20: Unknown error executing apt-key [Bullseye]

[Davide Prina]

Hi Andreas,

On 10/03/21 07:37, Andreas Metzler wrote:

> On 2021-03-09 Davide Prina wrote:
> [...]
>> Some users in Italian mailing list have reported that they have an error
>> when they try upgrade/install packages:
> [...]
>> dig the problem we found that they have the following files on their system:
> [...]
>> $ ls -l /lib/x86_64-linux-gnu/libgcrypt.so.20.1.5
>> -rw-r--r-- 1 root root 1112184 14 gen  2017
>> /lib/x86_64-linux-gnu/libgcrypt.so.20.1.5
> 
>> but these files are from package migrated to testing in:
>> [2017-01-25] libgcrypt20 1.7.5-3 MIGRATED to testing (Debian testing
>> watch)[¹]
> 
>> So for some reason when the library path change they have not been deleted.

> Another possibility would be that the user tried to upgrade from
> pre-oldstable directly to current-testing, skipping releases.

he never do that

> Do you have any further information on the upgrade, which version of
> libgcrypt was upgraded with what version of dpkg/apt to which version?

in /var/log/dpkg.log* user has no more info of that old version

he think he has Debian stable until summer 2020 or few month before, 
than he upgrades to testing. He has problems with samba, so he 
downgraded samba and he used pinning (samba/winbind/...) or used a 
stable/testing repositories (he don't remember).
At 14th October he change his domain and removed all (pinning and/or 
stable repo) and since that he has used only testing without security 
repository in his sources.list

But the library version is from 2017, so probably the problem is 
generated before.

> [...]
>> I suggest to check that those file are removed from
>> /lib/x86_64-linux-gnu/
>> in all new libgcrypt20 new version, elsewhere when Bullseye become stable
>> more user can have that problem.
> [...]
> 
> Sure it is possible to apply a bandaid but this just scale. Packages
> normally need to be able to rely on dpkg to work. If it is a wide-spread
> problem the cost/benefit ration can make sense.

it can be interesting to know if there are other user that have this 
older library in their systems... but I don't know if there is a good 
solution (the only thing I can imagine is something like this: let apt 
check and ask people to report this issue to this bug report)

Ciao
Davide