Keep in mind that to solve things probably a lot more information is needed because I am almost sure that for most people this works without problems so people will need to know what is different on your system that is triggering this and it is good to provide that information beforehand.
On:
But I got surprised (and annoyed) by an error message for a Ruby component.
Yes, that is not fun, can you make a screen shot and share that in this topic? If possible everything between the last thing that was fine and where you were presented the debug interface.
I have tried once more to improve this situation by the means of further software updates together with the file “openSUSE-Tumbleweed-KDE-Live-x86_64-Snapshot20210829-Media.iso”.
Unfortunately, I stumbled on the following YaST2 message.
Subprocess failed. Error: RPM failed: error: lua script failed: [string "%prein(filesystem-84.87-2.1.x86_64)"]:15: No such file or directory
error: filesystem-84.87-2.1.x86_64: install failed
error: filesystem-15.5-40.1.x86_64: erase skipped
How should such information lead to another system correction? :\
Another bit of progress was achieved in the meantime.
I could configure a chroot environment for my needs (in principle) for a terminal interface by an Ubuntu 21.04 session where internet access is working so far.
But I stumbled on the following information.
markus-elfring@bw-wst-linux1:~/root-Alternative$ sudo chroot ${chr}
bw-wst-linux1:/ # zypper info zypper
…
Problem retrieving files from 'Haupt-Repository (OSS)'.
Download (curl) error for 'http://download.opensuse.org/tumbleweed/repo/oss/repodata/repomd.xml':
Error code: Connection failed
Error message: Could not resolve host: download.opensuse.org
Please see the above error message for a hint.
Warning: Skipping repository 'Haupt-Repository (OSS)' because of the above error.
…
Information for package zypper:
…
Version : 1.14.44-1.1
…
I saw that thread, but did not think it worth adding the same comment. You seem to have other issues in that thread.
These days, when I use “chroot”, I first do a “–bind” mount of “/run” and “/tmp”. The bind mount of “/run” gets me access to “resolv.conf”, and the bind mount of “/tmp” avoids putting any temporary files in a permanent directory.
The software distributions manage the resolver configuration file in different ways, don’t they? :\
Another attempt for installation of relevant software components:
**bw-wst-linux1:/ #** zypper update filesystem
…
Some of the repositories have not been refreshed because of an error.
Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following package is going to be upgraded:
filesystem
1 package to upgrade.
Overall download size: 0 B. Already cached: 66.5 KiB. After the operation, additional 31.0 B will be used.
**Continue? [y/n/v/...? shows all options] (y): **
In cache filesystem-84.87-2.2.x86_64.rpm (1/1), 66.5 KiB ( 584 B unpacked)
Checking for file conflicts: ..........................................................................................................................................................[done]
(1/1) Installing: filesystem-84.87-2.2.x86_64 ........................................................................................................................................[error]
Installation of filesystem-84.87-2.2.x86_64 failed:
Error: Subprocess failed. Error: RPM failed: error: unpacking of archive failed on file /var/spool/mail: cpio: lstat failed - Invalid argument
error: filesystem-84.87-2.2.x86_64: install failed
error: filesystem-15.5-40.1.x86_64: erase skipped
**Abort, retry, ignore? [a/r/i] (a): **
Problem occurred during or after installation or removal of packages:
Installation has been aborted as directed.
Please see the above error message for a hint.
Would you like to correct the shown software situation (by the means of the configured chroot environment)? :\
**bw-wst021:/ #** zypper update filesystem
…
Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following package is going to be upgraded:
filesystem
1 package to upgrade.
Overall download size: 0 B. Already cached: 66.5 KiB. After the operation, additional 31.0 B will be used.
**Continue? [y/n/v/...? shows all options] (y): **
In cache filesystem-84.87-2.2.x86_64.rpm (1/1), 66.5 KiB ( 584 B unpacked)
Checking for file conflicts: ..........................................................................................................................................................[done]
(1/1) Installing: filesystem-84.87-2.2.x86_64 .........................................................................................................................................[done]
Now I find the following system configuration detail questionable.
Special system configuration steps enabled the update for a lot of software packages (after some clarification attempts).
The desired distribution upgrade succeeded then as expected finally.
The alternative that I have sometime used, is to copy “resolv.conf” into the chroot system. And, when undoing the “chroot” I also undo that copy (restore the original, which I had temporarily named as “restore.conf.orig”).
Another attempt for installation of relevant software components:
bw-wst-linux1:/ # zypper update filesystem
I don’t have any particular advice on that one. It is from the usrmerge update, which was quite complex (and messed up a few things).
But I got surprised (and annoyed) by an error message for a Ruby component.