Your message dated Fri, 13 Mar 2026 20:27:35 +0000
with message-id <[email protected]>
and subject line Re: Bug#1130639: key expired
has caused the Debian Bug report #1130639,
regarding key expired
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1130639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1130639
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: git-debpush
Version: 14.10~bpo13+1
Severity: important
X-Debbugs-Cc: [email protected]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi,

I get

gpg: WARNING: unsafe permissions on homedir '/home/builder/.gnupg'
gpg: Signature made Fri Mar 13 19:20:52 2026 UTC
gpg:                using RSA key 374D8CE4DB96E9CBD4C0972A606D084E4683C079
gpg: /home/builder/.gnupg/trustdb.gpg: trustdb created
gpg: Good signature from "Debian tag2upload service (key 1) 
<[email protected]>" [expired]
gpg: Note: This key has expired!
Primary key fingerprint: 374D 8CE4 DB96 E9CB D4C0  972A 606D 084E 4683 C079
dgit (build host): failed command: git verify-tag 
9b7cb3ac30820eb7cfaf182998164ad208e842cb
dgit (build host): error: subprocess failed with error exit status 1

I suspect that problem is not on my end.

   Simon

- -- System Information:
Debian Release: 13.3
  APT prefers stable-security
  APT policy: (990, 'stable-security'), (990, 'stable'), (500, 'stable-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.12.73+deb13-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages git-debpush depends on:
ii  git           1:2.47.3-0+deb13u1
ii  gpg           2.4.7-21+deb13u1+b1
ii  gpg-agent     2.4.7-21+deb13u1+b1
ii  libdpkg-perl  1.22.21

git-debpush recommends no packages.

git-debpush suggests no packages.

- -- no debconf information

-----BEGIN PGP SIGNATURE-----

iQFDBAEBCgAtFiEEtjuqOJSXmNjSiX3Tfr04e7CZCBEFAmm0ZTwPHHNqckBkZWJp
YW4ub3JnAAoJEH69OHuwmQgRv00H/1HGla8V5JbK/So3l5JI4WG4x+HK6uVa90Lm
UwbNgUQ9aojHsk4bqDqrklh1uNUaVaPBlzA6sxDc5ZEVToVpyvekJ+c/C/nbgKit
P2CUEcYVd2p5Jh5UmY5g+FLRad+dCYbAOpC2JreGFt1fhNW3xU4J2ZOGfbJeqtcq
vwPqpVdrp0t2VHNZeXu9KjAYWJX4OyhraIrPn/FyXUv1xjX4ALo0CpM3a97YXxI2
O1PontnhOpJlyY93ynsmW6wLNV5WsXk2oQXAlWTxDl1ljE65lOLwaDbxDnhrqqj/
fLxi4OdEvrOz+bHpHSzcQkIL8eYEtmWt43Nao4apZYPy6h+cJpM=
=4bYa
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message ---
tl;dr: One of the the copies of the public key hadn't been updated,
and we didn't spot this.

I have fixed it and a test job went through OK, so I think the service
is operational again.  Apologies for the inconvenience.

I am going to file a separate bug about the system and process
failures that led to this problem.

Ian.

-- 
Ian Jackson <[email protected]>   These opinions are my own.  

Pronouns: they/he.  If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.

--- End Message ---

Reply via email to