Trixie suite regularly with conflicting package versions/dependencies
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Raspbian |
New
|
Undecided
|
Unassigned |
Bug Description
Hey guys,
we start testing and building for Debian testing pretty early, basically once it is forked off as new testing version. What happens every few weeks is that the sync with Debian testing is somehow incomplete or done at a bad time, so that some packages have a newer version and dependencies for other packages which are not available yet.
Current example is liblocale-
I know the testing suite has no priority, but probably there is some easy solution? I observe this since years, as well when Buster, Bullseye and Bookworm were testing, I guess syncing versions/sources with Debian is a longer process during which changes can happen in Debian's volatile testing repo. Not sure whether an internal consistency test is suitable, or whether there are time frames during which changes in Debian can be ruled out. I never observed such problems with Raspbian's stable suite, so probably some mechanism is applied there, which could be applied to testing as well?
Best regards,
Micha
Raspbian is a rebuild, so after stuff is imported from Debian it must be built. Similarly when transitions happen we must rebuild the effected packages.
We have a "migrator" script which is supposed to keep the worst breakage out of the main testing suite but it's far from perfect. A "better" script could keep more breakage out but would also likely make it harder to troubleshoot why things are not migrating (I rejected Debian's "britney" because it's output is unusablly crap)
The reason you see a lot less of this in the stable suites is simply that there is far less chur