Version: 5.7.0+ds2-3 Hi Léo,
Thank you for taking the time to report this issue. The root cause of this non-deterministic failure was identified upstream and resolved in commit 4120115c862a70db59d66dd339c9d42703b14fdb, which was subsequently merged into the Podman 5.6.0 release.
This upstream fix has been incorporated into Debian in podman version 5.7.0+ds2-3, which is currently available in Debian testing. Because this version contains the patched logic, I am marking this bug as closed.
Could you please test this new version in testing to confirm that it fully resolves the dependency graph issue for your compose environments?
I acknowledge your request to have this fixed in the stable release to ensure a smooth upgrade path for users migrating from Debian 12. Please note that the process for updating packages in stable requires the issue to first be confirmed fixed and tested in testing. Furthermore, the Debian Stable Release Managers maintain a very high bar for accepting updates into a stable release; typically, only severe security vulnerabilities or critical regressions are approved for stable updates.
I invite you to participate in evaluating whether this issue meets those strict criteria for a Stable Release Update. I am personally not convinced that it meets the bar for an update to stable at this time, but I am happy to be convinced otherwise if you can help articulate the broader impact and severity. Once you are able to verify the fix in testing, we can discuss the justification further and decide whether to formally propose the stable update.
Best regards, -rt _______________________________________________ Pkg-go-maintainers mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
