On Thu, Jan 22, 2026 at 03:44:44PM +0100, Paul Gevers wrote: >... > Some ideas that came up: > * ben currently doesn't clearly show if successful rebuilds actually > migrated, but it does already know which packages are in which suite;
AFAIK ben is not currently able to handle more than one suite at a time, e.g. it is not possible to use "uninstallable" in a partial suite like experimental. > maybe > it could additionally show the status for testing (my idea would be one > column for testing, like the first one for unstable, maybe with a link to > the excuses (see next point)). > * the excuses.yaml could be processed and split into per transition pages; > either by ben directly (although I can recognize if that's considered a far > stretch for bens purpose), or by some stand-alone tool that takes the > excuses.yaml and the machine readable ben output. Since the vast majority of binNMUs are not related to transitions, I do not think giving ben a central role makes sense here. A proper solution also has to cover the regular "rebuild 1k packages for outdated Built-Using". Like apt is since trixie pretty useless if sqv is broken, and I do not see any tests (build time or autopkgtest) run by sqv itself to detect if it is broken after a rebuild with a new rustc. We really want the autopkgtests of rdeps here to avoid serious breakage migrating to testing. > Paul cu Adrian
