Hello, On 18 February 2014 13:31, Raf Czlonka <rafal.czlo...@gmail.com> wrote: >> Yes, that's true; I don't currently know how to solve that issue >> properly. I've added a check in preinst script to remove that bogus >> directory, but that won't help with removing broken versions of the >> package co-installed with pkg-config: the only way to fix them is to >> upgrade then to a new version (or to fix the issue manually).
> Such, such check (like the one below) will only work if the package is > upgraded, not removed. Broken packages can only be fixed by manua > intervention when a user decides to purge them from the system, rather > than trying to install to a newer version. > Something like this would at least allow users to get passed the broken > package state, install the new version and, if they choose to do so, > remove the package from their system using apt/dpkg. Actually, this is exactly what I added in a -3 version: it allows users to unbreak things by upgrading the package. -- Cheers, Andrew -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
