Bug 1177862 - fedup fails with "cpio: Malformed number <binary data>" errors
Summary: fedup fails with "cpio: Malformed number <binary data>" errors
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: fedup
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Will Woods
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-30 23:20 UTC by Konstantin Svist
Modified: 2015-04-23 16:11 UTC (History)
2 users (show)

Fixed In Version: fedup-0.9.2-1.fc22
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-04-23 16:05:39 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Konstantin Svist 2014-12-30 23:20:38 UTC
Description of problem:
Trying to run fedup on F20 XFCE:



Version-Release number of selected component (if applicable):
0.9.1-1.fc20


How reproducible:
every time

Steps to Reproduce:
1. fedup --network 21 --product=nonproduct
2.
3.

Actual results:
Lots of packages downloaded (as expected) -- but afterwards, terminal output is filled with errors 
"cpio: Malformed number <binary data>"

Terminal prompt is sometimes mangled due to binary data output (easily fixed with "reset")

Upgrade does not continue


Expected results:

Upgrade should proceed or some sane error should be printed to user.


Additional info:
This may be related to my compress=lzo setting in /etc/dracut.conf.d/kostya.conf

Comment 1 Konstantin Svist 2014-12-30 23:29:31 UTC
note: suspicion confirmed by setting dracut compress option to default (gzip) and running
dracut -f /boot/initramfs-$(uname-r).img $(uname -r)

Comment 2 Will Woods 2015-01-06 20:39:24 UTC
Ah, yep - fedup didn't know about lzo-compressed files.

This commit should fix that: https://github.com/wgwoods/fedup/commit/a0cf1f7

As you discovered, you can work around this for now by changing dracut's compression option to something supported by fedup (gzip, bzip2, xz, or lz4) and re-generating your initramfs.

If anyone else hits this bug, you could try the fix by adding the line from that commit to your /usr/lib*/python2.7/site-packages/fedup/util.py.

Otherwise this should be fixed in the next fedup update.

Comment 3 Fedora Update System 2015-04-20 14:57:59 UTC
fedup-0.9.2-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/fedup-0.9.2-1.fc20

Comment 4 Fedora Update System 2015-04-20 14:58:08 UTC
fedup-0.9.2-1.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/fedup-0.9.2-1.fc21

Comment 5 Fedora Update System 2015-04-20 14:58:15 UTC
fedup-0.9.2-1.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/fedup-0.9.2-1.fc22

Comment 6 Fedora Update System 2015-04-20 15:06:24 UTC
fedup-0.9.2-1.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/fedup-0.9.2-1.fc21

Comment 7 Fedora Update System 2015-04-21 18:49:34 UTC
Package fedup-0.9.2-1.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing fedup-0.9.2-1.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-6467/fedup-0.9.2-1.fc20
then log in and leave karma (feedback).

Comment 8 Fedora Update System 2015-04-23 16:05:39 UTC
fedup-0.9.2-1.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2015-04-23 16:11:35 UTC
fedup-0.9.2-1.fc22 has been pushed to the Fedora 22 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.