From: Efraim Flashner <efraim@flashner.co.il>
To: "Ludovic Courtès" <ludo@gnu.org>,
"Arun Isaac" <arunisaac@systemreboot.net>
Cc: guix-devel@gnu.org
Subject: Re: `guix lint' warn of GitHub autogenerated source tarballs
Date: Wed, 19 Dec 2018 14:33:20 +0000 [thread overview]
Message-ID: <08635A1A-EDA5-44B0-8C8A-532F16683154@flashner.co.il> (raw)
In-Reply-To: <87pntxwqx0.fsf@gnu.org>
On December 19, 2018 2:07:55 PM UTC, "Ludovic Courtès" <ludo@gnu.org> wrote:
>Hi!
>
>Arun Isaac <arunisaac@systemreboot.net> skribis:
>
>> Now that we are avoiding GitHub autogenerated source tarballs since
>they
>> are unstable and cause hash mismatch errors, can we have `guix lint'
>> emit a warning if these autogenerated source tarballs are used?
>
>I think Efraim had submitted a patch that does this but I can no longer
>find it. Efraim?
>
>Thanks,
>Ludo’.
I think I just posted a paste on IRC but haven't sent a patch yet. I'll grab it and submit it, it's almost done, just needs some cleaning up and tightening the test cases.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2018-12-19 14:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 20:45 `guix lint' warn of GitHub autogenerated source tarballs Arun Isaac
2018-12-19 8:43 ` Pierre Neidhardt
2018-12-19 14:07 ` Ludovic Courtès
2018-12-19 14:33 ` Efraim Flashner [this message]
2018-12-19 17:43 ` Arun Isaac
2018-12-19 19:29 ` Efraim Flashner
2018-12-21 20:50 ` Ludovic Courtès
2018-12-21 21:00 ` swedebugia
2018-12-25 14:32 ` Efraim Flashner
2019-01-05 17:39 ` Ludovic Courtès
2019-01-05 21:25 ` Learning the match-syntax swedebugia
2019-01-05 22:35 ` Ricardo Wurmus
2019-01-06 21:36 ` Chris Marusich
2019-01-07 17:34 ` swedebugia
2019-01-07 22:18 ` Ricardo Wurmus
2019-01-08 8:25 ` swedebugia
2019-01-08 20:32 ` Ricardo Wurmus
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=08635A1A-EDA5-44B0-8C8A-532F16683154@flashner.co.il \
--to=efraim@flashner.co.il \
--cc=arunisaac@systemreboot.net \
--cc=guix-devel@gnu.org \
--cc=ludo@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 external index
https://git.savannah.gnu.org/cgit/guix.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.