From: Dodji Seketeli <dodji@seketeli.org>
To: "joestringernz+sourceware at gmail dot com"
<sourceware-bugzilla@sourceware.org>
Cc: libabigail@sourceware.org
Subject: Re: [Bug default/20299] New: abipkgdiff reports "cpio: Malformed number ..." when unpacking RPMs
Date: Fri, 01 Jan 2016 00:00:00 -0000 [thread overview]
Message-ID: <86a8i76peg.fsf@seketeli.org> (raw)
In-Reply-To: <bug-20299-9487@http.sourceware.org/bugzilla/> (joestringernz's message of "Fri, 24 Jun 2016 18:51:14 +0000")
Hello Joe,
> Unfortunately when I tried to pass RPM packages to abipkgdiff, I see a large
> number of complaints like the following from cpio 2.12-3 (used from rpmextract
> 1.0-7).
On Fedora/CentOS, 'make check' works fine with cpio 2.12-3. What
abipkgdiff does is rpm2cpio <package> | cpio -dium --quiet'. So maybe
what rpm2cpio emits on your system has a problem? There must be
something in your environment that is different from what we see on
Fedora, and that is impacting the unpacking. We just need to figure
what, I guess.
So to see what the tool is doing, you can run abipkgdiff with the option
--verbose and attach the result here, so that we can learn more.
Sadly I don't have an Arch system at hand to test with right now. So
I'd need your help with this.
> cpio: Malformed number <9c><90>$Í}ý^]Ò
> cpio: Malformed number <90>$Í}ý^]Òc
> cpio: Malformed number $Í}ý^]ÒcÚ
I'd need to have more context than this.
> When I run "make check" in the source tree, I get failures for runtestdiffpkg
> and runtestdefaultsupprs.py. Looking in the tests/output/test-diff-pkg
> directory, none of the rpm reports have any content. I guess this is because
> the test captures stdout to these files, but only stderr gets output because of
> the cpio error I'm seeing above.
I think you should look at the content of the file
<build-directory>/tests/test-suite.log. That one should contain more
information, hopefully. At least from there you'd see what invidual
abipkgdiff command you need to re-run with the --verbose option to learn
more about what went wrong.
> I've attached the error log. I know there are various environmental differences
> on ArchLinux, eg python3 by default, but I'm not sure where to start to
> identify what might be causing this.
Sorry, I don't see file attached to the bug.
Thank you for taking the time to file this problem report and I look
forward to us sorting this issue out together.
--
Dodji
next prev parent reply other threads:[~2016-06-27 7:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 0:00 joestringernz+sourceware at gmail dot com
2016-01-01 0:00 ` [Bug default/20299] " joe at wand dot net.nz
2016-01-01 0:00 ` Dodji Seketeli
2016-01-01 0:00 ` joe at wand dot net.nz
2016-01-01 0:00 ` dodji at redhat dot com
2016-01-01 0:00 ` Dodji Seketeli [this message]
2016-01-01 0:00 ` dodji at seketeli dot org
2016-01-01 0:00 ` joe at wand dot net.nz
2020-03-23 9:33 ` mariiakovaleva3592 at gmail dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86a8i76peg.fsf@seketeli.org \
--to=dodji@seketeli.org \
--cc=libabigail@sourceware.org \
--cc=sourceware-bugzilla@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).