From: Serghei <egrep@protonmail.ch>
To: Noam Postavsky <npostavs@gmail.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
GNU Emacs Developers <emacs-devel@gnu.org>,
Eli Zaretskii <eliz@gnu.org>
Subject: Re: Install bnf-mode from the tar archive
Date: Mon, 20 Jan 2020 17:58:48 +0000 [thread overview]
Message-ID: <632f6e59-25c2-e47b-c5ad-0fea94711645@protonmail.ch> (raw)
In-Reply-To: <CAM-tV-_W3-BK2QOf9gq4mt5i_s7XfP91VqDhV3+zN_fvGbC=0Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 886 bytes --]
Yes, I think so.
> This bug report was last modified 208 days ago.
Just wondering why accepting the patch was stuck.
On 1/20/20 7:47 PM, Noam Postavsky wrote:
> On Mon, 20 Jan 2020 at 12:32, Serghei <egrep@protonmail.ch> wrote:
>
>> As I realized the main problem is the tar format. Using bsdtar with
>> `--format=ustar' flag (which is POSIX-standard) does the trick.
>> However bsdtar uses “pax interchange” format by default and this is
>> not implemented properly in the `tar-mode'.
>>
>> On 1/19/20 3:18 PM, Stefan Monnier wrote:
>>>> I have managed to fix the issue just by replacing bsdtar by GNU tar.
>>> I guess that deserves a bug report (the bug is not in
>>> the package manager but in tar-mode.el which seems not to support some
>>> of the formats used by bsdtar).
> Is the patch in Bug#19481 relevant?
>
> https://debbugs.gnu.org/19481#19
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-01-20 17:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-18 15:08 Install bnf-mode from the tar archive Serghei
2020-01-18 23:47 ` Serghei
2020-01-19 13:18 ` Stefan Monnier
2020-01-20 17:31 ` Serghei
2020-01-20 17:47 ` Stefan Monnier
2020-01-20 17:47 ` Noam Postavsky
2020-01-20 17:58 ` Serghei [this message]
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=632f6e59-25c2-e47b-c5ad-0fea94711645@protonmail.ch \
--to=egrep@protonmail.ch \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=npostavs@gmail.com \
/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.