<!DOCTYPE html>
<html data-lt-installed="true">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body style="padding-bottom: 1px;">
<p><font face="monospace">Hi Reinhard,</font></p>
<p><font face="monospace">Thank you for your response to my bug
report.</font></p>
<p><font face="monospace">The bug was indeed solved upstream and
made available in testing. I confirm that the version in testing
solves my problem (I tested it today), however I'd like to
kindly motivate my request to have this bug fix (and the
corresponding new podman version) backported in stable, since
you invite me do to so.</font></p>
<p><font face="monospace">I understand that your criteria as Debian
package maintainers for merging such updates in stable are high,
and that's what I appreciate about Debian and which gives it its
reliability. This problem isn't a critical security
vulnerability, but it is from my point of view an important, if
not critical, regression.</font></p>
<p><font face="monospace">For a server running production projects
on Debian 12, this issue makes upgrading a difficult process as
it forces one to both perform the distribution upgrade and to
migrate hosted projects to quadlets at the same time (or to use
the official compose implementation, but as I wrote previously
it as some other drawbacks). I think the Debian upgrade process
should not lead to forward-incompatibility issues when a
working, compatible solution is known, and that if such an
incompatibility is detected and acknowledged at some point, then
it's probably better to either fix the incompatible package or
to warn users.</font></p>
<p><font face="monospace">My point here is to highlight the fact
that users may not be aware of this issue; they might (rightly
so) expect the provided version to work (modulo breaking changes
available to everyone in podman changelog), and end up with a
difficult to reproduce bug, since the problematic behavior is
intermittent. <span class="HwtZe" lang="en"><span
class="jCAhz ChMk0b"><span class="ryNqvb">This does not seem
to me to be in line with the Debian philosophy where
compatibility is thoroughly evaluated.</span></span></span></font></p>
<p><font face="monospace"><span class="HwtZe" lang="en"><span
class="jCAhz ChMk0b"><span class="ryNqvb">Finally, since
podman is a rapidly evolving software whose recent
versions fix many bugs and introduce useful features, I
think backporting would be beneficial for Debian stable
users when such bugs are found.</span></span></span></font></p>
<p><font face="monospace">Maybe one sub problem here is that we
don't have good alternative repos (AFAIK) to use more recent
podman versions on Debian 13 (maybe alvistack's repos?).</font></p>
<p><font face="monospace">Please don't take those motivating
elements as criticism, I totally understand that finding all
bugs is not possible, and I would be happy to help conduct
further evaluation if needed.</font></p>
<p><font face="monospace">Thanks for your work!</font></p>
<p><font face="monospace">Best regards,</font></p>
<p><font face="monospace">Léo</font></p>
<p><font face="monospace"><span class="HwtZe" lang="en"><span
class="jCAhz ChMk0b"><span class="ryNqvb"><br>
</span></span></span></font></p>
<div id="grammalecte_menu_main_button_shadow_host"
style="width: 0px; height: 0px;"></div>
</body>
<lt-container></lt-container>
</html>