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