Why not update keyring on old Ubuntu release?

Asked by Jax Young

I notice that only mantic & lunar has the up-to-date keyring for now (2023-07-18). The older release has a older keyring version. Even LTS release jammy use a outdated version. I thought kerying should always be up to date.

I want to issue a bug at first, but there's allready a same bug unresolved (open on 2022-04-15). So I want to ask why not update the keyring?

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu debian-ports-archive-keyring Edit question
Assignee:
No assignee Edit question
Solved by:
Jax Young
Solved:
Last query:
Last reply:
Revision history for this message
Manfred Hampl (m-hampl) said :
#1

If the outdated key is a problem for you:

1. I suggest that you modify the bug report and set its status to "confirmed"

2. You can try manually downloading and installing the package for lunar.

Revision history for this message
Jax Young (jaxvanyang) said :
#2

Thanks reply. I have confirmed that bug. I also manually installed the newest version on my jammy machine. It seems good.

BTW, let me explain why I need this update. I use `mmdebstrap` to bootstrap a debian rootfs. It has a `--keyring` option to specify
the gpg file. I copied the up-to-date keyring at first and feed it to `--keyring`, but it doesn't work. I think it's a bug of `mmdebstrap`,
because it works on my Arch machine. `mmdebstrap` is 1.3.6 on Arch, while it's 0.8.4 on jammy. So I use a workaround for this.
`mmdebstrap` supports mirror format like this: `deb [signed-by=/path/to/keyring] https://...`, but it won't copy the keyring into
the rootfs. This is intened by the developer [1]. So if this package is up-to-date, I can use the same keyring on my host and in
the keyring without bothering to create extra hook.

TLDR: I need the same path for the keyring on my host and in the rootfs. Hope this could be a rationale.

- [1] https://groups.google.com/g/linux.debian.bugs.dist/c/MCnu7UiZIn4/m/UUCR7zpWAAAJ