[opensuse-factory] zypper up fails: cpio: Bad/unreadable header
Hi *, 'zypper up' on my Tumbleweed-20160105 failed today: Installation of boost-license1_60_0-1.60.0-1.1 failed: Error: Subprocess failed. Error: RPM failed: error: unpacking of archive failed: cpio: Bad/unreadable header error: boost-license1_60_0-1.60.0-1.1.noarch: install failed I verified that the SHA256 mentioned in [1] of the downloaded file [2] is okay. [1] http://download.opensuse.org/tumbleweed/repo/oss/suse/noarch/boost-license1_... [2] /var/cache/zypp/packages/download.opensuse.org-oss/suse/noarch/boost-license1_60_0-1.60.0-1.1.noarch.rpm This is packeg (1/95), and ignoring it leads to similar errors in the next package. Any hints? Have a nice day, Berny -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Bernhard Voelker composed on 2016-01-12 19:00 (UTC+0100):
'zypper up' on my Tumbleweed-20160105 failed today:
I verified that the SHA256 mentioned in [1] of the downloaded file [2] is okay.
This is packeg (1/95), and ignoring it leads to similar errors in the next package. Any hints?
Try again. I've done a bunch of TW updates in recent days, and had no apparent problems with any particular rpms that weren't solved by telling zypper to retry. If you think zypper is the problem, download latest zypper and libzypp rpms manually from a mirror and upgrade using rpm. My latest apparent success shows 20160110. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Bernhard Voelker <mail@bernhard-voelker.de> writes:
/var/cache/zypp/packages/download.opensuse.org-oss/suse/noarch/boost-license1_60_0-1.60.0-1.1.noarch.rpm
What happens if you manually install it with rpm? Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 01/13/2016 09:09 AM, Andreas Schwab wrote:
right, it's not a zypper problem: $ rpm -Uhv ./boost-license1_60_0-1.60.0-1.1.noarch.rpm Preparing... ################################# [100%] Updating / installing... 1:boost-license1_60_0-1.60.0-1.1 ################################# [100%] error: unpacking of archive failed: cpio: Bad/unreadable header error: boost-license1_60_0-1.60.0-1.1.noarch: install failed $ sha256sum boost-license1_60_0-1.60.0-1.1.noarch.rpm a8d1a2c9f8873c1b8bd0215923d806b7452e502cbf1cde5a000d03b72b3e63bf boost-license1_60_0-1.60.0-1.1.noarch.rpm Have a nice day, Berny -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday 2016-01-13 09:49, Bernhard Voelker wrote:
cpio errors almost always point to bad files. At which stage they get crippled is anyone's guess - it happening at the builder is possible, but rather unlikely. Internet transport is not as flakey as it was in the 90s, but can happen. Lastly, faulty RAM or disk in any machine involved in the transmission process. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Bernhard Voelker <mail@bernhard-voelker.de> writes:
The same file works fine here, so this is more likely a hardware problem on your side. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 01/13/2016 11:11 AM, Andreas Schwab wrote:
hmm, it's a VM in VirtualBox on a Win7 host. I don't see any other problems there, and I'm working daily with it like that since at least half a year. Well, I upgraded to VBox-5.0.12 on Jan 4th ... Thanks & have a nice day, Berny -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op woensdag 13 januari 2016 11:47:43 schreef Bernhard Voelker:
What happens if you run zypper clean && zypper ref && zypper up ? -- Gertjan Lettink, a.k.a. Knurpht Official openSUSE Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 01/13/2016 01:12 PM, Knurpht - Gertjan Lettink wrote:
What happens if you run zypper clean && zypper ref && zypper up ?
Exactly the same. And as written before, the error also happened with raw "rpm -Uhv ./boost...rpm". I've created a snapshot, and reverted to that from Jan 7th - i.e., to when I already had VBox-5.0.12; with this 'zypper up' succeeded. This means that VBox is out, too. I'll keep the other snapshot for a while - just for the case someone is interested and has further hints how to find the reason. Have a nice day, Berny -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Bernhard Voelker composed on 2016-01-12 19:00 (UTC+0100):
'zypper up' on my Tumbleweed-20160105 failed today:
I verified that the SHA256 mentioned in [1] of the downloaded file [2] is okay.
This is packeg (1/95), and ignoring it leads to similar errors in the next package. Any hints?
Try again. I've done a bunch of TW updates in recent days, and had no apparent problems with any particular rpms that weren't solved by telling zypper to retry. If you think zypper is the problem, download latest zypper and libzypp rpms manually from a mirror and upgrade using rpm. My latest apparent success shows 20160110. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Bernhard Voelker <mail@bernhard-voelker.de> writes:
/var/cache/zypp/packages/download.opensuse.org-oss/suse/noarch/boost-license1_60_0-1.60.0-1.1.noarch.rpm
What happens if you manually install it with rpm? Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 01/13/2016 09:09 AM, Andreas Schwab wrote:
right, it's not a zypper problem: $ rpm -Uhv ./boost-license1_60_0-1.60.0-1.1.noarch.rpm Preparing... ################################# [100%] Updating / installing... 1:boost-license1_60_0-1.60.0-1.1 ################################# [100%] error: unpacking of archive failed: cpio: Bad/unreadable header error: boost-license1_60_0-1.60.0-1.1.noarch: install failed $ sha256sum boost-license1_60_0-1.60.0-1.1.noarch.rpm a8d1a2c9f8873c1b8bd0215923d806b7452e502cbf1cde5a000d03b72b3e63bf boost-license1_60_0-1.60.0-1.1.noarch.rpm Have a nice day, Berny -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday 2016-01-13 09:49, Bernhard Voelker wrote:
cpio errors almost always point to bad files. At which stage they get crippled is anyone's guess - it happening at the builder is possible, but rather unlikely. Internet transport is not as flakey as it was in the 90s, but can happen. Lastly, faulty RAM or disk in any machine involved in the transmission process. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Bernhard Voelker <mail@bernhard-voelker.de> writes:
The same file works fine here, so this is more likely a hardware problem on your side. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 01/13/2016 11:11 AM, Andreas Schwab wrote:
hmm, it's a VM in VirtualBox on a Win7 host. I don't see any other problems there, and I'm working daily with it like that since at least half a year. Well, I upgraded to VBox-5.0.12 on Jan 4th ... Thanks & have a nice day, Berny -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (5)
-
Andreas Schwab -
Bernhard Voelker -
Felix Miata -
Jan Engelhardt -
Knurpht - Gertjan Lettink