I am back from 15 days of vacation and today I updated my TW. I had nearly 1.8Gb of updates, but it did not occur to me to check available disk space as I usually have plenty.
So, during the update (in the applying phase) I ran out of space, but I did not immediately recognize the condition because the error message was not very clear (cpio rename error or something like that).
After a few retries I aborted the update, which gave me the following message:
After deleting a few snapshots and rebalancing btrfs, I was able to complete the update by reissuing the “zypper dup” command.
However, the new output did not say anything about posttrans scripts. Now I am wondering if the posttrans scripts the were aborted have been run when reissuing “zypper dup” or not.
How do I check? How do I fix the problem (if there is one)?
Those scripts are required to run after a package is installed. The are included in the RPM and it is also defined in the RPM should run. Thus as you re-installed those packages/RPMs (which is what happens during an update), those scripts are run again.
Just thought I share some experience having the same problem but slightly more complicated. It happened today during zypper dup and exactly when it was installing some crucial rpms for zypper and rpm itself.
After that I got this:
# zypper dup
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
zypper: symbol lookup error: /usr/lib64/libzypp.so.1600: undefined symbol: addMacro
Solution was to force installation of the rpms for libsolv-tools, libzypp and zypper.
rpm --force -hiv <rpm that you need>
In my case I had downloaded the rpms in advance and could install them from cache
First. Been using TW for some time now. I don’t use applet to upgrade packets. This is my media box running Kodi for my TV and I don’t want it to update itself.
Second. Yes and No. At least not since my upgrade to TW.
According to my history my last “zypper up” was at:
597 2017-08-28 16:39:49 zypper up
That was before i upgraded this machine to TW.
My next step was.
610 2017-08-28 17:57:49 zypper dup
Don’t remember which opensuse version it was. Think it might have been Leap 42.2.
So. Your wrong. In my case, there is a way it could happen. And in my case the solution was to bootstrap zypper. And after that zypper dup. Problem solved. I admit it was a long time between the dups. Almost a year and a day, which shouldn’t, in theory be a problem.
Now. Care to explain in detail how this can’t happen?