On Mon, Feb 07, 2022 at 09:28:16PM -0500, Theodore Ts'o wrote: > The argument why a package which has an upstream-induced shared > library version bump, has to go through the entire NEW gauntlet [...]
I hear your frustration but don't you think that language like "gauntlet"
makes it, uhm, very hard for the "gauntlet team" to reply, and even more
importantly, reason with you?
IOW: how can we get to 'no NEW (or a much lighter one) for new binary packages'
or how can we communicate this if we already have this, maybe also?
'cause I think the latter could very well also be true, or very close
to it.
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org
⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
⠈⠳⣄
Never waste a crisis.
signature.asc
Description: PGP signature
