#1 2025-07-17 13:21:14

citizen

Member

From: Kalamata Greece

Registered: 2015-10-06

Posts: 13

Update Upgrade Problem with GPG

When i am trying to update i recieving this error ? Is there any problem with GPG Keys ?

Hit:1 https://brave-browser-apt-release.s3.brave.com stable InRelease
Hit:2 https://updates.signal.org/desktop/apt xenial InRelease                                                                                                                                                                                        
Get:3 https://apt.syncthing.net syncthing InRelease [17.5 kB]                                                                                                                                   
Hit:4 https://pkg.bunsenlabs.org/debian bookworm-backports InRelease                                                                           
Hit:5 https://repo.protonvpn.com/debian stable InRelease                                                                    
Hit:6 https://deb.debian.org/debian bookworm InRelease                                                                      
Hit:7 https://pkg.bunsenlabs.org/debian boron InRelease             
Hit:8 https://deb.debian.org/debian-security bookworm-security InRelease
Err:4 https://pkg.bunsenlabs.org/debian bookworm-backports InRelease
  The following signatures were invalid: EXPKEYSIG 7C38E34CAED6420C BunsenLabs Release Key <bunsen-release@bunsenlabs.org>
Hit:9 https://deb.debian.org/debian bookworm-updates InRelease
Hit:10 https://deb.debian.org/debian bookworm-backports InRelease
Hit:11 https://dl.google.com/linux/chrome/deb stable InRelease
Err:7 https://pkg.bunsenlabs.org/debian boron InRelease
  The following signatures were invalid: EXPKEYSIG 7C38E34CAED6420C BunsenLabs Release Key <bunsen-release@bunsenlabs.org>
Fetched 17.5 kB in 1s (14.9 kB/s)
Reading package lists... Done
Building dependency tree... Done
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://pkg.bunsenlabs.org/debian bookworm-backports InRelease: The following signatures were invalid: EXPKEYSIG 7C38E34CAED6420C BunsenLabs Release Key <bunsen-release@bunsenlabs.org>
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://pkg.bunsenlabs.org/debian boron InRelease: The following signatures were invalid: EXPKEYSIG 7C38E34CAED6420C BunsenLabs Release Key <bunsen-release@bunsenlabs.org>
W: Failed to fetch https://pkg.bunsenlabs.org/debian/dists/bookworm-backports/InRelease  The following signatures were invalid: EXPKEYSIG 7C38E34CAED6420C BunsenLabs Release Key <bunsen-release@bunsenlabs.org>
W: Failed to fetch https://pkg.bunsenlabs.org/debian/dists/boron/InRelease  The following signatures were invalid: EXPKEYSIG 7C38E34CAED6420C BunsenLabs Release Key <bunsen-release@bunsenlabs.org>
W: Some index files failed to download. They have been ignored, or old ones used instead.

wheresalice

New Member

Registered: 2025-07-01

Posts: 2

Re: Update Upgrade Problem with GPG

looks like the release key expired today:

~ > gpg bunsen-release.asc
gpg: WARNING: no command supplied.  Trying to guess what you mean ...
pub   rsa4096/0x697962500AFF9B75 2022-07-18 [SC] [expired: 2025-07-17]
      0F54A73224390760EB5D9A04697962500AFF9B75
uid                             BunsenLabs Release Key <bunsen-release@bunsenlabs.org>
sub   rsa4096/0x574830196F0676E5 2022-07-18 [E] [expired: 2025-07-17]
sub   rsa4096/0x7C38E34CAED6420C 2022-07-18 [S] [expired: never     ]

eightysixed

Member

From: USA

Registered: 2024-11-24

Posts: 58

Re: Update Upgrade Problem with GPG

Came here to post exactly this

e: I just saw this post. Probably/obviously (??) related

Last edited by eightysixed (2025-07-17 19:33:21)

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,652

Website

Re: Update Upgrade Problem with GPG

looks like the release key expired today:

~ > gpg bunsen-release.asc
gpg: WARNING: no command supplied.  Trying to guess what you mean ...
pub   rsa4096/0x697962500AFF9B75 2022-07-18 [SC] [expired: 2025-07-17]
      0F54A73224390760EB5D9A04697962500AFF9B75
uid                             BunsenLabs Release Key <bunsen-release@bunsenlabs.org>
sub   rsa4096/0x574830196F0676E5 2022-07-18 [E] [expired: 2025-07-17]
sub   rsa4096/0x7C38E34CAED6420C 2022-07-18 [S] [expired: never     ]

Yes it did!
Oversight on my part.

What makes it worse is that I have to go out right now, and won't be able to upload an updated key till Monday.
Apologies for this terrible timing.

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

citizen

Member

From: Kalamata Greece

Registered: 2015-10-06

Posts: 13

Re: Update Upgrade Problem with GPG

Fixed

Read here
https://forums.bunsenlabs.org/viewtopic.php?pid=144667

Last edited by citizen (2025-07-23 12:52:39)