On Mon, Jun 19, 2006 at 09:10:14AM +1000, Peter Chubb wrote: > >>>>> "Bill" == allomber <[EMAIL PROTECTED]> writes: > > Bill> On Thu, May 25, 2006 at 01:27:45PM +1000, Peter Chubb wrote: > >> Looks like the problem is that update-menus is crashing; I > >> temporarily removed the `menu' package and then was able to > >> upgrade. > > Bill> Hello Peter, The bug was not forwarded to me so I missed it. > > Bill> Can you still reproduce the problem ? In that case, I would > Bill> like the output of update-menus --stdout. > > After deinstalling, upgrading, and reinstalling, everything works, so > I can no longer reproduce the problem.
Hello Peter, I think I found the bug anyway: the error message you repotyed clearly come from libstdc++. This might happen if menu is unpacked before libstdc++: packages could try to execute update-menus before libstdc++ is ready to be used. To avoid that, sarge shipped update-menus non-executable and menu postinst was responsible to chmod a+x it. This way packages will not try to start update-menus before it is configured. Unfortunately I had to add a kludge to update-menus to catter for some broken woody packages and when removing the code, I accidentally removed the code that ship update-menus non-executable in menu 2.1.26. So I will readd this code and close this bug with the upload of menu 2.1.28. I pretty glad we uncovered this error before Etch release. 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]
