https://bugzilla.suse.com/show_bug.cgi?id=1178332 https://bugzilla.suse.com/show_bug.cgi?id=1178332#c6 Michael Andres <ma@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(ndordea@gmail.com | |) --- Comment #6 from Michael Andres <ma@suse.com> --- (In reply to Nick Dordea from comment #3)

I tried a test of installing them [ see below ]. But it complains and I do not know if this is OK . ... =================================================== rpm -i --test libzypp-17.24.2-lp152.2.10.1.x86_64.rpm

Never install package with '-i'! Always use 'rpm -U'! 'rpm -U' behaves as you expect it. It installs the package and auto-removes the previously installed version(s). 'rpm -i' just installs the package, leaving previously installed versions on disk. That's why you get the '...conflicts with file from package...' error messages. The new and the old package are overwriting each others files, so installing one damages the other. If 'rpm -q PACKAGE' list multiple versions, it's usually undesired (except for kernel and kernel related packages). In case of doubt re-install the package with zypper. (In reply to Nick Dordea from comment #4)

A). The laptop was shutdown on Oct-31 about 22:15 . Was the saving time change involved ?

I don't think this is likely.

B) On Nov 01, I started the laptop about 7:30 AM and some maintenance against zypper / libzypp was done ! [ as per journalctl output ... ]

What process triggered that maintenance ? Was it a left over of the maintenance done on October 28 ?

If you did not run it on your own, them maybe some updater applett. Basically: If the rpm commands were executed by libyzpp (i.e. via zypper, YAST or PackageKit) you should see entries for them in /var/log/zypp/history Then check the preceding 'DATE|command|...' entry. It should list the command that initiated the install. 'zypper log' will show you the zypper commands executed and still mentioned in /var/log/zypper.log 'zypper log -l /var/log/YaST2/y2log' will try to get the same info from YASTs logfile /var/log/YaST2/y2log

Did the above "maintenance" clobber parts of my laptop's software ?

Feel free to attach those 3 log files. We'll have a look at them. Maybe they reveal something. And please answer Marcus question in commen#5 (output of `rpm -qi libyaml-cpp0_6`) -- You are receiving this mail because: You are on the CC list for the bug.