On 2026-05-16 Charlemagne Lasse <[email protected]> wrote: > Am Fr., 3. Apr. 2026 um 23:09 Uhr schrieb Charlemagne Lasse > <[email protected]>: > > Source: mesa > > Version: 25.2.6-1~bpo13+1 > > Severity: wishlist > > X-Debbugs-CC: Dylan Aïssi <[email protected]> > > > > According to the backports guidelines [1], it is required to update > > backports when changes in testing are done. Of course, this is still > > volunteer work, but it would still be nice to have mesa 26.0.x in > > Debian trixie-backports > > > > [1] https://backports.debian.org/Contribute/
> Can somebody check if my understanding is correct and packages > uploaded to Debian backports should get updated when a new version > hits testing? Good morning, I do not think it is that simple. The main point is that bpo is not fire-and-forget. - If you upload you will need to support it. However that does not imply that bpo must strictly track testing. There can be reasons to have foo v2 in stable and keep bpo at v3 although v4 is available in testing. e.g. v4 breaks a huge number of rdeps but v4 doesn't. Or if v4 is at 4.0 and experience shows that a little bit of extra waiting time before upgrading foo has not hurt in there past. Imho a bpo maintainer may make judgement calls like these. cu Andreas -- "You people are noisy," Nia said. I made the gesture of agreement.
