<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Le 15/03/2026 à 19:13, Micha Lenk a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:b560e7be-e03c-434c-8ade-a7a6d1c1ce2a@debian.org">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p>Hi Roland,</p>
<div class="moz-cite-prefix">On 3/13/26 12:53, Roland Mas wrote:<br>
</div>
<blockquote type="cite"
cite="mid:bced7423-3498-4468-9eb3-80c2e83ce982@debian.org">
<blockquote type="cite" style="color: #007cff;">No upgrade path
to trixie (backported version 1.4.2+dfsg1-4~bpo12+1 >=
1.4.2+dfsg1-2) <br>
</blockquote>
<br>
The problem is that trixie and bookworm have the same
1.4.2+dfsg1-2 version, so there's nothing I could squeeze
in-between. There is, however, a 1.4.2+dfsg1-4~bpo13+1 version
in trixie-backports, so there is an upgrade path from bookworm
to bookworm-backports to trixie-backports to forky. <br>
<br>
I'd be happy to implement any suggestion leading to a working
solution 🙂</blockquote>
<p>Then you probably want to target bookworm-backports-sloppy
instead, which is meant for backports targeting bookworm with an
upgrade path (via trixie + trixie-backports) to forky -- exactly
what you were suggesting as alternative upgrade path.</p>
</blockquote>
<p>Ah, I see. Thanks for the tip, I had forgotten about that one.
I'll do the upload right away.</p>
<p>Sorry for the noise,</p>
<p>Roland.</p>
</body>
</html>