[opensuse-factory] snapper rollback does not work for me
after having to use a snapshot to get my Tumblweed going again I found out that snapper rollback did not do as expected, see following message: Installation of digikam-doc-5.2.0-163.3.noarch failed: Error: Subprocess failed. Error: RPM failed: error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Read-only file system) It seems that .rpm.lock is the culprit. Looked at changing .rpm.lock with chpwn en chmod to no avail. Some body with a solution? Close to 600 files are waiting for an update. -- opensuse:tumbleweed:20161018 Qt: 5.7.0 KDE Frameworks: 5.26.0 kf5-config: 1.0 KDE Plasma: 5.8.1 Kernel: 4.7.5-1-default Linux User 183145 working on a Pentium IV . -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2016-10-21 T 15:12 +0700 Constant Brouerius van Nidek wrote:
after having to use a snapshot to get my Tumblweed going again I found out that snapper rollback did not do as expected, see following message:
Installation of digikam-doc-5.2.0-163.3.noarch failed: Error: Subprocess failed. Error: RPM failed: error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Read-only file system)
It seems that .rpm.lock is the culprit. Looked at changing .rpm.lock with chpwn en chmod to no avail.
Some body with a solution? Close to 600 files are waiting for an update.
After issuing "snapper rollback" from the commandline, you have to reboot, to land in a read-write filesystem again. This is on purpose. The technical reason needs a bit longer explanation, for here just one paragraph: we do not want to alter the "well known status" (=the existing read-only snapshots), thus once you have booted into your snapshot, you land in the read-only status; "snapper rollback" does this: create a read-write snapshot of the well-known status and set the new read-write snapshot as the "default", i.e. after a reboot you will automatically land where you want to be. HTH - MgE -- Matthias G. Eckermann, Director Product Management SUSE Linux Enterprise SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, Oct 21, 2016 at 11:12 AM, Constant Brouerius van Nidek <cbroueriusvannidek@gmail.com> wrote:
after having to use a snapshot to get my Tumblweed going again I found out that snapper rollback did not do as expected, see following message:
Installation of digikam-doc-5.2.0-163.3.noarch failed:
snapper rollback does not initiate any RPM installation. Please describe step by step how you performed "snapper rollback" and at which point during this procedure you tried to install RPM.
Error: Subprocess failed. Error: RPM failed: error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Read-only file system)
It seems that .rpm.lock is the culprit. Looked at changing .rpm.lock with chpwn en chmod to no avail.
Some body with a solution? Close to 600 files are waiting for an update.
-- opensuse:tumbleweed:20161018 Qt: 5.7.0 KDE Frameworks: 5.26.0 kf5-config: 1.0 KDE Plasma: 5.8.1 Kernel: 4.7.5-1-default Linux User 183145 working on a Pentium IV .
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Friday, October 21, 2016 12:19:44 PM WIB Andrei Borzenkov wrote:
On Fri, Oct 21, 2016 at 11:12 AM, Constant Brouerius van Nidek
<cbroueriusvannidek@gmail.com> wrote:
after having to use a snapshot to get my Tumblweed going again I found out that snapper rollback did not do as expected, see following message:
Installation of digikam-doc-5.2.0-163.3.noarch failed: snapper rollback does not initiate any RPM installation. Please describe step by step how you performed "snapper rollback" and at which point during this procedure you tried to install RPM.
Error: Subprocess failed. Error: RPM failed: error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Read-only file system)
It seems that .rpm.lock is the culprit. Looked at changing .rpm.lock with chpwn en chmod to no avail.
Some body with a solution? Close to 600 files are waiting for an update.
-- opensuse:tumbleweed:20161018 Qt: 5.7.0 KDE Frameworks: 5.26.0 kf5-config: 1.0 KDE Plasma: 5.8.1 Kernel: 4.7.5-1-default Linux User 183145 working on a Pentium IV .
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
The explanation is really simple.I did a zypper -vvv dup and after all the data were downloaded the installation should begin. The information popped up that /var/lib/rpm/.rpm.lock was still in effect. Just oversaw the fact that I should have rebooted before doing the install. Thanks everybody, for the help. My system is running again. -- opensuse:tumbleweed:20161019 Qt: 5.7.0 KDE Frameworks: 5.26.0 kf5-config: 1.0 KDE Plasma: 5.8.1 Kernel: 4.7.6-1-default Linux User 183145 working on a Pentium IV . -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Andrei Borzenkov -
C. Brouerius van Nidek -
Constant Brouerius van Nidek
-
Matthias G. Eckermann