Bug#852599: texlive-latex-recommended, texlive-latex-recommended-doc: Replaces without Breaks make files disappear from other installed packages
On 2017-01-25 16:24, Norbert Preining wrote:
> Hi Andreas,
>
> thanks for the report ... but I am stymed ... maybe *all* the
> TeX Live replace/breaks are wrong ... reading the policy again
> I see that yes, all are wrong ...
>
> I have wrong entries back to 2014 ...
>
> Now the question is, why did this never show up :-(
For this error to manifest, there must be a valid partial upgrade path.
Texlive is such a big stack, with so may (changing) cross-dependencies,
that I (well, rather a script) never found one (or at least none that
exposed this bug, the script could try harder in some cases).
>> This is a serious bug violating policy 7.6, see
>> https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces
>
> I can easily fix all the cases and upload new packages, but that would
> destroy the chance to enter testing/next-stable due to freeze bug.
Let the current set migrate first. Fixing upgrade issues (in a followup
upload) usually warrants a freeze exception.
> Do you have any suggestion how to proceed? I can do the following:
> * prepare new set of packages
> * maybe you can run your usual piuparts test on these new packages
> * if they are clean I upload them *after* the freeze and ask for
> an exception
If it's just "copy Breaks to Replaces" I'm pretty confident that it will
solve this bug. Plugging an external package source into my highly
experimental piuparts torturing engine (that specifically looks for file
overwrites and file disappearance) is not easily possible (and I don't
think I have the time to implement something like this in time)
>> 4m35.6s ERROR: FAIL: After purging files have been modified:
>> /var/lib/dpkg/info/texlive-latex-extra.list not owned
>
> That seems to be a dpkg problem, not mine. I never create these files, nor
> do I ship them by myself. If this is a bug, then dpkg one.
That just indicated that a part in dpkg's database changed (because some
files were removed from the list due to the Replaces), which should not
have happened (without upgrading/removing the mishandled package).
Andreas
Reply to: