Hello Sven,
On 2020-12-06 18:21, Sven Hartge wrote: > Hello! > > When trying to import the new 11.0.0 release into Debian our tooling > complains about it not being signed by the correct key. > > Until now, every release was signed by the key from > https://blog.bacula.org/downloads/Bacula-4096-Distribution-Verification-key.asc > > with the ID 5235F5B668D81DB61704A82DC0BE2A5FE9DF3643: > > pub rsa4096 2018-09-03 [SC] > 5235F5B668D81DB61704A82DC0BE2A5FE9DF3643 > uid Bacula 4096 Distribution Verification Key (www.bacula.org) > <k...@bacula.org> > > The new release is signed by > > gpgv: Signature made Do 03 Dez 2020 20:25:53 CET > gpgv: using RSA key > 270AC5018ED80662804BE9E97E73F0869FEC1047 > gpgv: issuer "techt...@baculasystems.com" > > but I am not able to find any official statement about this new key. We are in the process to release the files and files that are currently on the server are not signed with the community key. I'm working with Kern to sign the packages correctly and send an official announcement. You are a little bit too fast, and I'm a little bit too slow :-) I hope it will be solved in the next days. _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
