Guillaume Cottenceau wrote:
Ron Stodden <[EMAIL PROTECTED]> writes:
Oddly, installing all the 9.2 updates solved all problems (although there is no apparent reason why in the explains of the RPMs involved).
There seems there is still an odd "locking" problem when we launch update-menus from within %post scriptlet of an RPM (problems arises from the fact update-menus do itself an rpm call, "rpm -qa"), flepied spent a large amount of time trying to fix that before 9.2, actually had some success with some scenarios, thought he caught all of them, but apparently not really all, the problem being that it's very rare here and absolutely not reproductible :/.
If *anyone* can reproduce it, please post here the steps to reproduce it, I'm sure we can come up with a fix quickly. But without it, it's a hell to debug.
A workaround is to launch "update-menus" as root.
This looks to me like it might be related:
# urpmi --bug bug djbsupport
installing /contrib/i586/./djbsupport-1.0-5mdk.noarch.rpm
Preparing... ##################################################
1:djbsupport ##################################################
added medium qmail
urpmi database locked
error: %post(djbsupport-1.0-5mdk) scriptlet failed, exit status 7
This is reproducible in two attempts, when installing with urpmi, first, then adding the --bug option to urpmi after urpme djbsupport. There is not a qmail source added to urpmi sources:
# urpmi.update the entry to update is missing (one of CD1, CD2, CD3, CD4, club.comm_i586_9.2, contrib, plf, update_source)
There is a compressed archive of bug/ here: http://home.mindspring.com/~rolfpedersen/bug.tgz
Rolf
