On Sun, Jan 25, 2026 at 07:43:50PM +0900, Simon Richter wrote: > Hi, > > On 1/25/26 06:38, Gioele Barabucci wrote: > > > Now the point of this proposal is to have a _standardized_ and _machine > > readable_ way to express support for old Debian releases. > > To what end? > > Any automated change that can be performed on a source package should be a > tool in devscripts that maintainers can use directly. There is no point in > wrapping this tool into logic to check out a project from git, perform the > change, commit the result and submit a merge request. It's not even saving > the maintainers any work compared to running the tool themselves.
This makes sense. However, IMHO 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? 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
