On 1/22/20 7:04 PM, Sven-Haegar Koch wrote: > On Wed, 22 Jan 2020, Alberto Molina Coballes wrote: > >> A new commit which hopefully solves this bug has been uploaded [1], >> but this bug is affecting only 1.8.4-1 and a new release will not be >> uploaded inmediatly, but ASAP. > > Thanks for fixing it! > > This bug report was more for completeness - a second run of apt-get > makes the packages install, as on retry the conflicting package got > already upgraded, so the failed one is able to succeed. Also because it > only affects unstable and does not break upgrading completely I did not > give it a higher severity. >
That's true. I'm not sure a breaks+replaces is worth carrying over for a package version that was not even present in testing... @Alberto, I saw the commit. It is right, but perhaps it will pollute d/control for no strong reason. We could revert if you want. Up to you! regards.