pe 17.7.2026 klo 15.27 Bill Allombert ([email protected]) kirjoitti: > On Fri, Jul 17, 2026 at 03:04:00PM +0300, Martin-Éric Racine wrote: > > Package: debian-policy > > Severity: wishlist > > X-Debbugs-Cc: [email protected] > > > > Standards-Version 4.7.4 was introduced during the development of Debian 14, > > but the version number doesn't reflect that. > > > > Meanwhile, debhelper-compat 14 was introduced during the same development > > cycle and it indeed matches the upcoming Debian release version. > > This is a pure coincidence, debhelper-compat 13 was introduced in debian 11. > > Your proposal would require all maintainers to update their control file even > though there was no change to policy. 4.7.3, 4.7.4 and 4.7.4.1 are relatively > minor update that affect a minority of packages.
I'd really like to know where you got this impression that this would force people to bump the number in their control file for no reason. Standards-Version merely is an indication of when the package's compliance to Policy was last checked. For instance, many packages still use debhelper-compat 13 and claim Standards-Version 4.6.2, etc. The way I see it, the major digit would be a good ballpark indication of when any major work was last done on a package's packaging, while the whole number could point us closer to the exact timeframe. One practical use for this would be to check for packages that haven't seen any upgrade in a couple of releases. Combined with uscan automation, it could be used to prod maintainers once in a while. Martin-Éric
