From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 56222@debbugs.gnu.org
Subject: bug#56222: Emacs 28.1 distribution tarball does not unpack on Solaris 10
Date: Sun, 26 Jun 2022 16:24:16 +0300 [thread overview]
Message-ID: <837d53a77j.fsf@gnu.org> (raw)
In-Reply-To: <2b514995-53a3-940e-1e06-2b35a29e4d5c@cs.ucla.edu> (message from Paul Eggert on Sat, 25 Jun 2022 15:40:08 -0500)
> Date: Sat, 25 Jun 2022 15:40:08 -0500
> From: Paul Eggert <eggert@cs.ucla.edu>
>
> The Emacs 28.1 distribution tarball does not unpack correctly on Solaris
> 10 when using the system-supplied 'tar' program. This is a regression
> from Emacs 27.2. I didn't pick this up when testing earlier, since I
> have GNU 'tar' in my PATH (perhaps I shouldn't; oh well). The symptoms are:
>
> $ gzip -d <emacs-28.1.tar.gz | tar xf -
> tar: ././@LongLink: typeflag 'L' not recognized, converting to
> regular file
> tar: ././@LongLink: typeflag 'L' not recognized, converting to
> regular file
> ...
>
> The problem is that the Emacs 28.1 tarball (unlike 27.2) has file names
> longer than 100 bytes. These file names do not fit within traditional
> 'tar' format. By default, for these files GNU Tar uses a GNU-specific
> @LongLink extension, designed long ago but not picked up by POSIX, that
> Solaris 10 tar does not understand.
>
> A simple workaround is to tell GNU Tar to generate POSIX-standard
> tarballs instead. I installed the attached patch to Emacs master to fix
> this, and suggest that it be backported to the Emacs 28 branch if we're
> planning to generate another Emacs 28 version.
Thanks, I cherry-picked to the emacs-28 branch.
(Yes, there will be at least Emacs 28.2.)
next prev parent reply other threads:[~2022-06-26 13:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-25 20:40 bug#56222: Emacs 28.1 distribution tarball does not unpack on Solaris 10 Paul Eggert
2022-06-26 13:24 ` Eli Zaretskii [this message]
2022-06-26 15:13 ` Paul Eggert
2022-06-26 15:19 ` Eli Zaretskii
2022-06-26 18:10 ` Paul Eggert
2022-06-26 18:37 ` Eli Zaretskii
2022-06-26 22:46 ` Paul Eggert
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=837d53a77j.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=56222@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).