On Mon, Jan 10, 2005 at 11:00:57AM -0500, Adam C Powell IV wrote:
> Package: menu
> Version: 2.1.19
> Severity: serious
> Justification: Policy 10.9
>
> Greetings,
>
> During a woody->sarge upgrade, the new menu unpacked before the old
> ghostview was removed, resulting in the following breakage:
Thanks to notifying me!
May I ask why ghostview was removed here ?
> Removing ghostview ...
> /var/lib/dpkg/info/ghostview.postrm: /usr/bin/update-menus: Permission denied
> dpkg: error processing ghostview (--purge):
> subprocess post-removal script returned error exit status 1
So ghostview.postrm use the ominous command -v
if command -v update-menus > /dev/null 2>&1; then
update-menus
fi
(command -v has this nasty bug of finding non executable files in the
path and not being POSIX sh). This is serious multi-policy violation in
woody ghostview...
> I believe this is because update-menus was non-executable, which I have
> heard you do in order to prevent packages from calling it before the
> package is configured.
Yes, but this is the behaviour documented by _woody_ menu as well!
(but actually woody update-menu is shipped executable.)
> (I understand this is not quite the same as
> Policy 10.9, but reportbug asked for a policy section. :-)
Bah, use expert mode in reportbug!
> How to fix this? I suppose you could conflict with ghostview, which is
> now obsolete, so it gets removed before menu is upgraded. Most other
> woody packages (at least, all others installed on my one remaining woody
> system) use test -x update-menus to avoid calling it if not executable,
> so those should upgrade just fine.
I think you are right. I will try to check all relevant maintainers
scripts in woody first.
I am afraid apt prefer to keep ghostview than removing it, making hard
to upgrade. What do you think ?
Cheers,
--
Bill. <[EMAIL PROTECTED]>
Imagine a large red swirl here.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
