On Thu, Apr 10, 2014 at 04:47:36PM +0200, Andreas Beckmann wrote:
> Thanks a lot for getting this into production!
>
> On 2014-04-10 16:34, Agustin Martin wrote:
> > Just noticed piuparts unistallation errors in dictionaries with the new
> > stuff, /var/lib/{aspell,ispell} was left behind in piuparts run.
> >
> > This happens because piuparts removes dictionaries-common before the
> > dictionaries.
> >
> > Alhough that should not happen in normal life, is true that code must deal
> > gracefully with this, e.g.,
> >
> > # dpkg --purge --force-all dictionaries-common
> > # apt-get purge $dictionary
> >
> > should not leave anything behind.
>
> Use --force-anything and loose your warranty :-)
>
> That may just be a known dpkg bug leaving directories behind, that needs
> to be fixed in dpkg, now worked around elsewhere. If I can confirm this,
> I'll temporarily ignore these directories in piuparts. Right now I have
> no time to check.
Hi, Andreas, thanks for the feedback.
Do not worry to look into that, is not what happens here.
In this case, looking at piuparts log seems a matter of different removal
order in piuparts and in my sandbox. In my dict packages those dirs are not
explicitly shipped, but created on demand by autobuildhash scripts and
removed on removal from a script shipped with dictionaries-common.
However, postrm cannot rely on anything in dependencies, there is no
warranty on removal ordering. So, script is not available and not run if
dictionaries-common is removed first (which can happen) and those dirs are
left behind. This is something I am trying to fix in new -dev debhelper
snippets allowing for explicit removal of those dirs if empty.
Let's those errors exist until I can prepare new packages for the
dictionaries built against new stuff.
Regards,
--
Agustin
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
