From: "Ludovic Courtès" <ludo@gnu.org>
To: Brett Gilio <brettg@gnu.org>
Cc: 43738@debbugs.gnu.org
Subject: bug#43738: Patch file names too long
Date: Sat, 03 Oct 2020 11:03:07 +0200 [thread overview]
Message-ID: <87tuvbheb8.fsf@gnu.org> (raw)
In-Reply-To: <87tuvdxsjn.fsf@debian> (Brett Gilio's message of "Thu, 01 Oct 2020 21:36:44 -0500")
Brett Gilio <brettg@gnu.org> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> There are several patch file names that are too long for ‘tar’, as
>> reported during ‘make dist’:
>>
>> tar: guix-1.0.1.22624-c258f1-dirty/gnu/packages/patches/ocaml-bisect-fix-camlp4-in-another-directory.patch dosiernomo tro longas (maks 99); ne ŝutita
>> tar: guix-1.0.1.22624-c258f1-dirty/gnu/packages/patches/audiofile-signature-of-multiplyCheckOverflow.patch dosiernomo tro longas (maks 99); ne ŝutita
>> tar: guix-1.0.1.22624-c258f1-dirty/gnu/packages/patches/python2-pygobject-2-gi-info-type-error-domain.patch dosiernomo tro longas (maks 99); ne ŝutita
>> tar: guix-1.0.1.22624-c258f1-dirty/gnu/packages/patches/audiofile-division-by-zero-BlockCodec-runPull.patch dosiernomo tro longas (maks 99); ne ŝutita
>> tar: guix-1.0.1.22624-c258f1-dirty/gnu/packages/patches/python-robotframework-honor-source-date-epoch.patch dosiernomo tro longas (maks 99); ne ŝutita
>>
>> ‘guix lint’ reports it as well, but apparently this is easily
>> overlooked.
>>
>> Ludo’.
>
> Does it matter that this is coming from a dirty working tree? Maybe not.
Nope, it doesn’t matter.
Ludo’.
next prev parent reply other threads:[~2020-10-03 9:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 10:26 bug#43738: Patch file names too long Ludovic Courtès
2020-10-02 2:36 ` Brett Gilio
2020-10-03 9:03 ` Ludovic Courtès [this message]
2020-11-10 17:01 ` Ludovic Courtès
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tuvbheb8.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=43738@debbugs.gnu.org \
--cc=brettg@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.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).