Comment # 46 on bug 1190008 from Markus Elfring

(In reply to comment #42)
>   + Is there a need to configure another ���������special chroot environment��������� with
> desirable settings so that the error messages which are reported by
> installation commands here so far can be better clarified ���������?

markus-elfring@bw-wst-linux1:~/root-Alternative$ sudo chroot ${chr}
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): 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 contribute further solution ideas accordingly?
https://forums.opensuse.org/showthread.php/555033-Fixing-software-package-updates-according-to-questionable-link-changes?p=3070518#post3070518