Dear all, It took me some time to get back to this but here’s sort of an update – well, maybe more like some piece of documentation for future reference: First, I was a little bit baffled because I knew I had updated the key already (and for at least two years). So I wondered why Nicholas encountered this expiration warning. Turns out I only updated the (secret) key with the extended validity on my local machine and pushed the (updated) public key to the TEI server (at /data/debian-packages/tei-c.pub.key.asc) and the key server hkps://keys.openpgp.org. During release Nicholas then tried to sign the Debian packages with the outdated secret key from the tei users keyring and had to extend it. The missing part was a `gpg --refresh-keys` for the tei user that would sync the keys. I now extended the key’s validity again to something more far from now (2023-07-09) and updated the respective places [1]. The key’s history can be viewed from [2]. But we might add the key syncing to the release procedure?! Hope that helps Peter [1] The places where the key can be found are: a) the tei user’s keyring on the Huma-Num server3, b) the TEI-apt-repo at https://github.com/TEIC/TEI-apt-repo/blob/master/tei-c.pub.key.asc, and c) the web space at https://packages.tei-c.org/deb/tei-c.pub.key.asc [2] https://keyserver.ubuntu.com/pks/lookup?search=tei+council+debian&fingerprint=on&op=index

Am 10.04.2021 um 19:30 schrieb Nicholas Cole :

Dear Council,

Just to let you know — as part of creating the P5 4.2.2 release, I needed to update the expiration date for the gpg key, in order to build the Debian Package.

I’ve set it for 3 months hence, but obviously it can be changed to whatever the Council thinks is appropriate!

Best wishes,

Nicholas _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council