Re: gl2ps_1.4.2+dfsg1-4~bpo12+1_amd64.changes REJECTED
Micha Lenk <[email protected]> Sun, 15 Mar 2026 19:13:03 +0100
| Newsgroups | gmane.linux.debian.alioth.science-maintainers,gmane.linux.debian.backports.general |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--===============6240509193101790914==
Content-Type: multipart/alternative;
boundary="------------hIG3H7Pv6nM0XXDgfv4KhBBT"
Content-Language: en-US
This is a multi-part message in MIME format.
--------------hIG3H7Pv6nM0XXDgfv4KhBBT
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Hi Roland,
On 3/13/26 12:53, Roland Mas wrote:
>> No upgrade path to trixie (backported version 1.4.2+dfsg1-4~bpo12+1
>> >= 1.4.2+dfsg1-2)
>
> 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.
>
> I'd be happy to implement any suggestion leading to a working solution 🙂
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.
Best regards,
Micha
--------------hIG3H7Pv6nM0XXDgfv4KhBBT
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<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-8fiUuRrzOP0dnm+yROfE0A@public.gmane.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>
<p>Best regards,<br>
Micha</p>
</body>
</html>
--------------hIG3H7Pv6nM0XXDgfv4KhBBT--
--===============6240509193101790914==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline