From: Eli Zaretskii <eliz@gnu.org>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: 12455@debbugs.gnu.org
Subject: bug#12455: 24.2; POSIX tar archives with extended header information are parsed incorrectly
Date: Sun, 16 Sep 2012 09:50:19 +0300 [thread overview]
Message-ID: <83ehm2sbpw.fsf@gnu.org> (raw)
In-Reply-To: <87txuy4h21.fsf@Rainer.invalid>
> From: Achim Gratz <Stromeko@nexgo.de>
> Date: Sun, 16 Sep 2012 08:28:54 +0200
>
> The first file in a tar archive with PAX extended header information is
> inaccessible:
>
> rw-r--r-- 1000/100 40 org-7.9.1-220-g5a122c/PaxHeaders.12938/README
> ---------- 0/0 0 20 atime=1347724616
> 20 ctime=1346955271
>
> -rw-r--r-- gratz/users 1319 org-7.9.1-220-g5a122c/README
> rw-r--r-- 1000/100 40 org-7.9.1-220-g5a122c/lisp/PaxHeaders.12938/Makefile
> ---------- 0/0 0 20 atime=1347724476
> 20 ctime=1345833266
>
> -rw-r--r-- gratz/users 2115 org-7.9.1-220-g5a122c/lisp/Makefile
>
> Emacs can't extract README for this archive, but it will be able to
> extract Makefile. Additionally it gives strange error messages
> containing newlines when the cursor is positioned in some places in the
> first entry and it's PAX header.
Isn't this related to bug#258?
In any case, please attach a small file that could be used to
reproduce the problem. Thanks.
next prev parent reply other threads:[~2012-09-16 6:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-16 6:28 bug#12455: 24.2; POSIX tar archives with extended header information are parsed incorrectly Achim Gratz
2012-09-16 6:50 ` Eli Zaretskii [this message]
2012-09-16 6:59 ` Achim Gratz
2012-09-16 7:26 ` Eli Zaretskii
2012-09-16 8:40 ` Achim Gratz
2012-09-16 7:33 ` Andreas Schwab
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=83ehm2sbpw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=12455@debbugs.gnu.org \
--cc=Stromeko@nexgo.de \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.