https://bugzilla.novell.com/show_bug.cgi?id=721671
https://bugzilla.novell.com/show_bug.cgi?id=721671#c9
Michael Andres
Oh, I just met that /var/lib/rpm/.rpm.lock error as well. Michael, could you take a look?
We usually don't allow rpm to write something to the console. OTOH there have been a few buggy rpm versions, where rpm did not create the db directory (/var/lib/rpm/) on the fly upon rpm_init. So there've actually been a few libzypp versions writing this as error message to the screen. (bnc#697115) Libzypp works around this rpm bug since libzypp-9.5.0 (May 2011). AFAIK Beta1 contains libzypp-9.11.0, so this message should no longer occur, unless YaST calls zypp:target:init("/") within the instsys, where /var/lib/rpm/ exist, but is AFAIK readonly. I think YaST does this to utilize some of the libzypp methods and simply ignores the failed database init. Which might be ok as we don't want to install any packages to the instsys. Later, for the actual installation, YaST calls zypp:target:init("/mnt"), which initializes /mnt/var/lib/rpm/, and this is the call that must succeed in order to actually install some package. - IMO the 'create transaction lock on /var/lib/rpm/.rpm.lock' is due to YaSTs zypp:target:init("/") call, and if so, not causing any harm. If the above message was serious, we would not be able to install a single package to the system. So most probably not related to this bug. But it may also be YAST is calling rpm directly, and those calls are responsible for the message. Anyway I somewhat doubt, that the message is related to the aborted installation. Comment #1 et al. indicate these bugs may actually be caused by some XOrg problem. That's IMO more likely. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.