[Bug 875457] New: Installing a package with zypper leaves a stale .rpm.lock in /var/lib/rpm/
https://bugzilla.novell.com/show_bug.cgi?id=875457 https://bugzilla.novell.com/show_bug.cgi?id=875457#c0 Summary: Installing a package with zypper leaves a stale .rpm.lock in /var/lib/rpm/ Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers@forge.provo.novell.com ReportedBy: stefan.bruens@rwth-aachen.de QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:22.0) Gecko/20100101 Firefox/22.0 Whenever I install a package with zypper, there is an empty /var/lib/rpm/.rpm.lock file afterwards. This at least breaks packagekit access to the rpm db (not able to fetch info) Reproducible: Always Steps to Reproduce: 1. make sure there is no .rpm.lock 2. install a package, e.g. "zypper in xinput" Actual Results: After the installation, the .rpm.lock is not removed. If there is a .rpm.lock zypper seems to be unaffected. Apper is not able to access update details. i | PackageKit-backend-zypp | package | 0.8.11-2.3.1 | x86_64 | openSUSE-13.1-Oss i | libzypp | package | 13.9.0-13.1 | x86_64 | openSUSE-13.1-Update i | snapper-zypp-plugin | package | 0.1.7-1.1 | x86_64 | openSUSE-13.1-Oss i | zypp-plugin-python | package | 0.3-10.1.2 | x86_64 | openSUSE-13.1-Oss i | zypper | package | 1.9.12-16.1 | x86_64 | openSUSE-13.1-Update i | zypper-aptitude | package | 1.9.12-16.1 | noarch | openSUSE-13.1-Update i | zypper-log | package | 1.9.12-16.1 | noarch | openSUSE-13.1-Update i | build-mkdrpms | package | 20131015-1.1 | noarch | openSUSE-13.1-Oss i | deltarpm | package | 3.6-2.1.2 | x86_64 | openSUSE-13.1-Oss i | rpm | package | 4.11.1-6.5.1 | x86_64 | openSUSE-13.1-Update i | rpm-32bit | package | 4.11.1-6.5.1 | x86_64 | openSUSE-13.1-Update i | rpm-build | package | 4.11.1-6.5.1 | x86_64 | openSUSE-13.1-Update i | rpm-python | package | 4.11.1-6.5.1 | x86_64 | openSUSE-13.1-Update i | systemd-rpm-macros | package | 2-19.1 | noarch | openSUSE-13.1-Update -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=875457 https://bugzilla.novell.com/show_bug.cgi?id=875457#c1 Wolfgang Bauer <wbauer@tmo.at> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wbauer@tmo.at --- Comment #1 from Wolfgang Bauer <wbauer@tmo.at> 2014-04-28 11:47:36 UTC --- (In reply to comment #0)
If there is a .rpm.lock zypper seems to be unaffected. Apper is not able to access update details.
That Apper cannot access update details has nothing to do with that .rpm.lock file. It's rather related to packagekitd's ShutdownTimeout, and already reported here: https://bugzilla.novell.com/show_bug.cgi?id=855993 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=875457 https://bugzilla.novell.com/show_bug.cgi?id=875457#c2 Michael Andres <ma@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE --- Comment #2 from Michael Andres <ma@suse.com> 2014-04-28 13:57:52 CEST --- closing as duplicate *** This bug has been marked as a duplicate of bug 855993 *** http://bugzilla.novell.com/show_bug.cgi?id=855993 -- 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.
participants (1)
-
bugzilla_noreply@novell.com