From: "Iruatã Souza" <iru.muzgo@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] pkg/unpkg strangeness
Date: Mon, 11 May 2015 18:44:42 -0300 [thread overview]
Message-ID: <CABJnqBRHBaTFDY8qVytcSQWz7yJg--BtUQ_qXrp_CV6VrtCs6g@mail.gmail.com> (raw)
In-Reply-To: <eddfdf06d141880bf717d6fc4066e519@u2.sfldmibb.det.wayport.net>
Unpkg tries to be a tar xv printing "A path" to stdout and "path
checksum" to stderr.
It only knows about the tar format (100 chars limit in path), but
tar(1) compresses using ustar (256 chars limit in path) if needed.
imo, unpkg should be rewritten in rc.
On Mon, May 11, 2015 at 6:33 PM, <sl@9front.org> wrote:
>> According to tar(1):
>>
>> File path names are limited to 100 characters (256 when
>> using ustar format).
>>
>> Every file that has a path bigger than that leads to pkg/unpkg trying
>> to unpack the file into /.
>
> I don't see where tar(1) is ever getting called.
>
> Note: I do not really understand unpkg.c.
>
> sl
next prev parent reply other threads:[~2015-05-11 21:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 21:33 sl
2015-05-11 21:44 ` Iruatã Souza [this message]
2015-05-11 21:46 ` Aram Hăvărneanu
2015-05-11 21:50 ` Iruatã Souza
-- strict thread matches above, loose matches on Subject: below --
2015-05-11 22:00 sl
2015-05-11 20:28 sl
2015-05-11 21:17 ` [9front] " Iruatã Souza
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=CABJnqBRHBaTFDY8qVytcSQWz7yJg--BtUQ_qXrp_CV6VrtCs6g@mail.gmail.com \
--to=iru.muzgo@gmail.com \
--cc=9front@9front.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 NNTP newsgroup(s).