From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>,
"Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
Cc: 62071@debbugs.gnu.org, Lars-Dominik Braun <lars@6xq.net>
Subject: bug#62071: openjdk@9/10 sources not reproducible
Date: Mon, 03 Apr 2023 23:52:48 +0200 [thread overview]
Message-ID: <86h6twy6of.fsf@gmail.com> (raw)
In-Reply-To: <871qljpz71.fsf@inria.fr>
Hi,
On Mon, 20 Mar 2023 at 10:08, Ludovic Courtès <ludovic.courtes@inria.fr> wrote:
>> I was thinking a second time about it and found that not only the newer
>> development of OpenJDK is on GitHub, but also the older versions are
>> available. So I could add another patch like this:
>>
>> + (method git-fetch)
>> + (uri (git-reference
>> + (url "https://github.com/openjdk/jdk9")
>
> That’s a good idea. It shouldn’t change the SHA256 (if it does,
> something’s wrong) so it looks like an no-brainer.
Well, by experience, it is rare that the released tarball contain the
exact same content as the tagged commit. If it is the case (same SHA256
for both tarball and GitHub tagged release), indeed no-brainer. :-)
Else, some work still remain for the complete preservation of Guix. ;-)
Björn, what is the status of this SHA256?
Cheers,
simon
next prev parent reply other threads:[~2023-04-04 11:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 9:48 bug#62071: openjdk@9/10 sources not reproducible Lars-Dominik Braun
2023-03-11 23:06 ` Björn Höfling
2023-03-12 21:00 ` Björn Höfling
2023-03-13 13:50 ` Simon Tournier
2023-03-16 9:12 ` Björn Höfling
2023-03-16 11:48 ` Ludovic Courtès
2023-03-17 22:10 ` Björn Höfling
2023-03-20 9:08 ` Ludovic Courtès
2023-04-03 21:52 ` Simon Tournier [this message]
2023-03-16 12:37 ` Jonathan Brielmaier
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=86h6twy6of.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=62071@debbugs.gnu.org \
--cc=bjoern.hoefling@bjoernhoefling.de \
--cc=lars@6xq.net \
--cc=ludovic.courtes@inria.fr \
/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).