From: "joe at wand dot net.nz" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/20299] abipkgdiff reports "cpio: Malformed number ..." when unpacking RPMs
Date: Fri, 01 Jan 2016 00:00:00 -0000 [thread overview]
Message-ID: <bug-20299-9487-XZi3WxAxPm@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-20299-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20299
--- Comment #6 from Joe Stringer <joe at wand dot net.nz> ---
(In reply to dodji from comment #5)
> "joe at wand dot net.nz" <sourceware-bugzilla@sourceware.org> writes:
> >> > I guess that if on redhat distributions the typical rpm2cpio does decompression
> >> > by default then this is something I can take up with the rpmextract maintainer
> >> > in ArchLinux. Worst case the archlinux abigail PKGBUILD could patch the
> >> > abipkgdiff source to add a decompression step.
> >>
> >> well, if rpm2cpio <package> | cpio -idmv could be made to work, I'd be
> >> glad, yes.
> >
> > I think this is the right solution - it looks like the rpm2cpio utility on
> > Archlinux is just a ~25 line script which does not cover many cases (for
> > example, decompression).
>
> Right.
>
> But in the mean time, maybe libabigail's build system could detect the
> presence of bsdtar. So that when you are compiling libabigail, if
> bsdtar is present, then abipkgdiff.cc would use it to extract the
> content of the (possibly compressed) cpio archive emitted by rpm2cpio.
>
> If bsdtar is not present at build time, then abipkgdiff.cc would use
> cpio, just like it does today.
>
> Would that work for you?
That sounds quite reasonable, and it would work for me.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-07-03 21:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 0:00 [Bug default/20299] New: " joestringernz+sourceware at gmail dot com
2016-01-01 0:00 ` [Bug default/20299] " dodji at seketeli dot org
2016-01-01 0:00 ` joe at wand dot net.nz
2016-01-01 0:00 ` [Bug default/20299] New: " Dodji Seketeli
2016-01-01 0:00 ` [Bug default/20299] " dodji at redhat dot com
2016-01-01 0:00 ` joe at wand dot net.nz [this message]
2016-01-01 0:00 ` joe at wand dot net.nz
2016-01-01 0:00 ` Dodji Seketeli
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=bug-20299-9487-XZi3WxAxPm@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libabigail@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).