Bug#1132617: mesa: update debian trixie-backports to 26.0.x

Paul Gevers <[email protected]> Sun, 17 May 2026 09:10:17 +0200

Newsgroups	gmane.linux.debian.devel.x
Message-ID	<26d236f5-065c-4e0b-b54b-b96f34cf7207__42999.0993857913$1779002006$gmane$org@debian.org>

Hi,

On 5/17/26 07:36, Andreas Metzler wrote:
> On 2026-05-16 Charlemagne Lasse <[email protected]> wrote:
>> 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.

That's not my understanding of [1] this:
"""
This means, you have to keep track of the changes in unstable, update 
your backport when a new version enters testing...
"""
I've always understood that backports is supposed to follow testing, not 
some older version that the maintainer likes. If there are worries about 
the backport, there should be worries about it migrating to testing too 
(and it should have been hold in unstable longer, or should have been 
uploaded to experimental). If it breaks stuff, a +reallyv3 version 
should be in unstable/testing too. I assume the backport ftp-masters can 
confirm.

Paul

[1] https://backports.debian.org/Contribute/

OpenPGP_signature.asc (application/pgp-signature, 585 B)