Your message dated Sat, 23 Dec 2023 07:23:12 +0000
with message-id <[email protected]>
and subject line Re: Bug#1059350: debian-keyring: missing update since 
2023.09.24
has caused the Debian Bug report #1059350,
regarding debian-keyring: missing update since 2023.09.24
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.)


-- 
1059350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059350
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: debian-keyring
X-Debbugs-Cc: [email protected]
Version: 2023.09.24
Severity: normal

Dear Maintainer,

* What led up to the situation?

debian-keyring package has not updated for a while.
(last update was debian-keyring 2023.09.24)

* What exactly did you do (or not do) that was effective (or
  ineffective)?

I've checked the recent activity on salsa.d.o

https://salsa.debian.org/debian-keyring/keyring/-/commits/master?ref_type=heads

It seems that tagged but not released yet.


* What was the outcome of this action?

Even though refreshed key was sent to keyring.debian.org,
 it was not reflected.
There is a case that contained key may be expired.

If there is no release in a long term, it will cause
delay of uploading package for affected DD.

Could you release newer version of debian-keyring?

* What outcome did you expect instead?

N/A.



-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-5-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=ja_JP.utf8, LC_CTYPE=ja_JP.utf8 (charmap=UTF-8), LANGUAGE
not set Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

debian-keyring depends on no packages.

Versions of packages debian-keyring recommends:
ii  gnupg  2.2.40-1.1

debian-keyring suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
On Sat, Dec 23, 2023 at 03:41:30PM +0900, Kentaro HAYASHI wrote:
> * What led up to the situation?
> 
> debian-keyring package has not updated for a while.
> (last update was debian-keyring 2023.09.24)
> 
> * What exactly did you do (or not do) that was effective (or
>   ineffective)?
> 
> I've checked the recent activity on salsa.d.o
> 
> https://salsa.debian.org/debian-keyring/keyring/-/commits/master?ref_type=heads
> 
> It seems that tagged but not released yet.
> 
> 
> * What was the outcome of this action?
> 
> Even though refreshed key was sent to keyring.debian.org,
>  it was not reflected.
> There is a case that contained key may be expired.
> 
> If there is no release in a long term, it will cause
> delay of uploading package for affected DD.
> 
> Could you release newer version of debian-keyring?

The debian-keyring package is a convenience package and we only make
efforts to ensure it is up to date around release time. The actual
keyring used by the Debian infrastructure is served via rsync and
matches the version that is currently available via salsa. For further
details on the workflow you might find
https://keyring.debian.org/keyring-workflow.html useful.

J.

-- 
... And you can't help my life. But you can hide the knives.

Attachment: signature.asc
Description: PGP signature


--- End Message ---

Reply via email to