[Solved] Error updating zotero-deb package on Linux

86ul

Hello,

Just a moment ago, I installed some updates by both the update manager and the terminal. In both I got an error, which says:

Update Manager:
An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://github.com/retorquere/zotero-deb/releases/download/apt-get ./ InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 996BEED4A27FACBDFailed to fetch https://github.com/retorquere/zotero-deb/releases/download/apt-get/./InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 996BEED4A27FACBDSome index files failed to download. They have been ignored, or old ones used instead.

Terminal:
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 996BEED4A27FACBD
Fetched 103 kB in 2s (62,3 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up-to-date.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://github.com/retorquere/zotero-deb/releases/download/apt-get ./ InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 996BEED4A27FACBD
W: Failed to fetch https://github.com/retorquere/zotero-deb/releases/download/apt-get/./InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 996BEED4A27FACBD
W: Some index files failed to download. They have been ignored, or old ones used instead.


Is there something what I can do to fix this error?

dstillman

That'd be a question for @emilianoeheyns. Those packages aren't from us.

emilianoeheyns

Debian/Ubuntu seems to have deprecated the keyring format that the verification keys are stored in. A fix is described here.

@dstillman I didn't see this coming unfortunately, and this is not something I can fix without user interaction. It might be worthwhile pinning this message so people can get pointed to the fix.

Apologies for the disruption people. It hasn't been a fun weekend :(

dstillman

Will this affect all existing users of the package?

emilianoeheyns

If not all then almost all. I'm testing a postinst script that will perform the key migration, but I'm afraid most users will already be on a OS version that deprecated keybox stores so they won't be able to get the baked-in migration.

dstillman

I don't know — it's the first we've heard of this. Possible that most people aren't yet on an OS version where they can't get a fix.

emilianoeheyns

If it saves the frustration for even one user it's worth it. The postinst is running through the tests now.

emilianoeheyns

The builds with a postinst have gone out.

86ul

It is fixed for my case, thanks for all these quick reactions.

emilianoeheyns

I've googled around a bit and the way to fix this is to be included in Debian or run your own keyserver. All other self-hosted repos must either have been hit by the same problem or have someone who knows debian repos better than me (which isn't hard) who knew about the problem and fixed it beforehand. But fixing beforehand means sticking it in a postscript, and the package manager is going to complain about that. Lesser of two evils in this case.

emilianoeheyns

I think this can be unpinned now. I actually haven't gotten new reports since it was pinned.

86ul

I think so too.

Since this problem almost 4 weeks ago, I have updated Zotero to 5.0.94 without any problem. I use a Mint 20 Cinnamon.