On Mon, Jan 10, 2005 at 11:00:57AM -0500, Adam C Powell IV wrote: > During a woody->sarge upgrade, the new menu unpacked before the old > ghostview was removed, resulting in the following breakage: > > 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
After inspection, I think the following packages have the same bug: ghostview/postinst: if command -v update-menus > /dev/null 2>&1; then gwm/postinst: if command -v update-menus > /dev/null 2>&1; then joe/postinst: if command -v update-menus >/dev/null 2>&1; then update-menus; fivim-gtk/postinst: if command -v update-menus >/dev/null 2>&1 ; then vim-perl/postinst: if command -v update-menus >/dev/null 2>&1 ; then vim-python/postinst: if command -v update-menus >/dev/null 2>&1 ; then vim-ruby/postinst: if command -v update-menus >/dev/null 2>&1 ; then vim-tcl/postinst: if command -v update-menus >/dev/null 2>&1 ; then vim/postinst: if command -v update-menus >/dev/null 2>&1 ; then xodo/postinst: if command -v update-menus >/dev/null 2>&1; then update-menus; fi xvier/postinst:if command -v update-menus >/dev/null 2>&1; then wn/postinst: if which update-menus > /dev/null ghostview and gwm have been removed from sarge. xodo still has the bug in sarge. I suppose I need a versionned conflict against vim*, xvier and wn. 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]
