Re: Call for volunteers and GR draft: tag2upload key installation
- To: debian-vote@lists.debian.org
- Subject: Re: Call for volunteers and GR draft: tag2upload key installation
- From: Tollef Fog Heen <tfheen@err.no>
- Date: Sun, 04 May 2025 22:20:32 +0200
- Message-id: <[🔎] 87plgocelr.fsf@err.no>
- Mail-followup-to: debian-vote@lists.debian.org
- In-reply-to: <26636.42435.30154.379571@chiark.greenend.org.uk> (Ian Jackson's message of "Sat, 26 Apr 2025 10:22:11 +0100")
- References: <26607.41378.283822.404146@chiark.greenend.org.uk> <26611.44351.328322.934115@chiark.greenend.org.uk> <41749DDA-07C2-474E-AC2C-0BBFA14B4ADB@debian.org> <87tt6bli8q.fsf@melete.silentflame.com> <26636.42435.30154.379571@chiark.greenend.org.uk>
]] Ian Jackson
Sean Whitton writes ("Re: Call for volunteers and GR draft:
tag2upload key installation"):
On Mon 07 Apr 2025 at 05:23pm +0530, Micha Lenk wrote:
> When did it get backported to oldstable for use on
> fasolo.debian.org?
> I haven't seen it in the oldbackports-new queue yet.
src:debian-tag2upload-keyring was unblocked by the release
team,
migrated to trixie today, and I just uploaded it to
backports-NEW.
I wasn't aware that the intent was to provide this key to dak
via this
.deb. Our intent with the package was to provide it to programs
like
dscverify on end-user systems. But, OK.
No, not ok. We already have a keyring distribution mechanism for
keyrings that live on keyring.d.o. Please use that one.
Installing
packages from backports from the wrong distribution (relative to
what
the host is running) will not fill us with joy.
I believe the setup for that syncing is managed by keyring-maint,
but I
could be wrong about that.
Note that debian-tag2upload-keyring_1.1_all.deb from trixie is
directly installable on buster. So if DSA is able to organise
it,
that might be a simpler approach than going via oldbackports.
There's no way to get a package into oldstable-backports now.
--
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are
Reply to: