Control: affects -1 lilypond
Hi,
On 21.08.2014 11:50, Guillem Jover wrote:
This and any other such package (although we did a quick check over
codesearch.d.o, but I guess missed this one due to the line breaks)
were broken already, and not performing the symlink to dir switch
anyway because the code is checking if the parameter matches the
canonicalized form («readlink -f»), which it will not.
This can make dpkg lose track, remove or overwrite unintended file,
as they might end up installed in a (real) path that does not match
with the one listed in the package metadata.
I think that for this reason dpkg needs to make those break explicitly,
and that having such version in testing is more valuable than trying to
avoid those packages to explicitly break, instead of allowing the
possibly silent breakage.
Thanks for the detailed explanation. :)
I'm thus probably just going to either close or reassign this bug
report to the affected package(s).
On 21.08.2014 12:01, Guillem Jover wrote:
> The only other affected package is lilypond. I'll check the actual
> effect from dir_to_symlink too, cook a list and send to debian-devel@.
> And file some RC bugs at the same time.
I also couldn't find more affected packages. It should be possible to
fix these two before dpkg migrates to testing in 9 days.
Best regards,
Andreas
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
