Bug#920733: freedink: missing Breaks+Replaces: freedink-engine (<< 109.4)

[beuc at debian.org]

Hi,

On 28/01/2019 21:11, Andreas Beckmann wrote:
> On 2019-01-28 20:45, beuc at debian.org wrote:
>> Hi,
>>
>> Would you mind detailing how you invoke piuparts so it gives that error?
> input comes from some script using dose to find potential candidates for
> file overwrites problems across distros
>
>> I've been running it for an hour and I only get successes (or false
>> positives about font dirs that I skipped with
>> --warn-on-leftovers-after-purge).
>> The logs you provide apparently initializes a server by installing
>> "hello" and running then seem to do special tests that are different
>> from e.g. https://piuparts.debian.org/sid/source/f/freedink.html .
> then some scripts generate more scripts to perform several partial
> upgrade scenarios within piuparts ... until one fails
>
> everything is running manually on a local machine ... I should get this
> automated on an official host ... it's hard to catch faulty packages
> before they migrate after two days ...

Hmm, I was about to add piuparts to my upstream release procedures but I
see this would miss this kind of bug anyway, so it's probably not worth
the time and effort.


>> This, so I can thoroughly reproduce the bug(s)
> apt-get install freedink-engine/buster freedink/sid
If I only did this check (which I already did - hence why I wrote
/thoroughly/), we'll certainly run into yet another corner case and
we'll both waste time.

Hence why I'd like to run checks before uploading.
Right now I'm just in a stressful situation where I'll do an upload and
maybe I'll have another SERIOUS bug coming out of nowhere a couple days
later and my package threatened for removal again.


>> (unless you have a working patch, that is).
> See Subject?
This is not a patch, merely a pointer.
Also both
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
and https://wiki.debian.org/PackageTransition don't give the same
directions for this bug (change 1 package vs. change 2 packages).

- Sylvain