On Sun, Jan 25, 2026 at 08:11:34PM +0100, Micha Lenk wrote: > Hi, > > Peter Pentchev <[email protected]> hat am 25.01.2026 12:55 CET geschrieben: > > [...] it would also make sense to have the new > > field be machine-readable, if only for reporting and planning work; > > you yourself mentioned the maintainer's dashboard, what if it could also > > show packages that have versions newer than the backported ones, and > > it knew how to limit those checks by release? > > But isn't this information already available on the maintainer's dashboard > today? I see the backport versions of packages where I am lagging behind > forky in trixie-backports are already colored with yellow background. > > I'm not conviced, yet curious to understand the purpose of the suggestion.
What if you could ask it - or another, dedicated service - to only show you packages which have unstable/testing versions that are newer than the ones in the official stable and oldstable suites, and they are also newer than the ones in the respective backports suites... ...but only going as far back as you have explicitly indicated that you want to backport stuff? Like, you have backported package A to <stable>-backports, and you have also backported package B to <stable>-backports, but you have indicated that you also want to maintain package B in oldstable, so the service will alert you to that, but keep silent about package A. G'luck, Peter -- Peter Pentchev [email protected] [email protected] [email protected] PGP key: https://www.ringlet.net/roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13
signature.asc
Description: PGP signature
