All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] modify site from adoptopenjdk mirror to official hg.openjdk.java.net repository
Date: Thu, 5 Dec 2019 22:15:15 +0100	[thread overview]
Message-ID: <20191205221515.30e00913@windsurf> (raw)
In-Reply-To: <20191205055828.14257-1-tudor@tudorholton.com>

Hello,

The commit title should have been something like:

	package/openjdk: use official hg.openjdk.java.net repository

On Thu,  5 Dec 2019 16:58:28 +1100
Tudor Holton <tudor@tudorholton.com> wrote:

> From: Tudor Holton <buildroot@tudorholton.com>
> 
> Since Java 11 (and possibly earlier), OpenJDK now has its own official
> repository at hg.openjdk.java.net which is referenced in all OpenJDK documentation.
> This patch brings buildroot into line with that source, reducing the opportunity
> for code injection, and allowing consistent patching both across projects and for
> patches specific to buildroot environments.
> 
> diff -ru shows that the only changes between the downstream and upstream files at
> this point in time is the addition of a .hg_archive.txt file,  containing:
> 
> repo: fd16c54261b32be1aaedd863b7e856801b7f8543
> node: 7b6accc7c009304dd2979ea16c1cb15bf749a1fc
> branch: default
> tag: jdk-12.0.2+10
> tag: jdk-12.0.2-ga
> 
> This does, however, change the hash for the tar.gz file (but not for the license).
> 
> With respect to the concern regarding upstream hash consistency, we have now been
> using these archives for just over a year (since OpenJDK 11) and we haven't seen an
> archive hash change in that time.  This was a vast improvement on the previous
> Mercurial forest.  /archive is exactly as is sounds.  It's an archive that doesn't
> change, which is why it effectively negates the need for a "downstream" mirror.
> 
> Tests completed successfully (which is not surprising since there are no code changes here):
> 
> $ ./support/testing/run-tests -d ./dl/ -k -o test_dir tests.package.test_openjdk.TestOpenJdk
> 14:35:25 TestOpenJdk                              Starting
> ['Hello, World']
> ['Test: Get JNI Version passed', 'Test: Read Native String Constant passed', 'Test: Write Java String to Native Library passed', 'Test: Write Java Char Array to Native Library passed', 'Test: Write String Member to Native Library passed', 'Test: Set String Member from Native Library passed', 'Test: Execeute Java Function from Native Library passed', 'Test: Instantiate Java Class passed', 'Test: Call Native Library to Set System Time passed']
> 14:35:46 TestOpenJdk                              Cleaning up
> .
> ----------------------------------------------------------------------
> Ran 1 test in 20.614s
> 
> OK
> 
> Signed-off-by: Tudor Holton <buildroot@tudorholton.com>

I've applied after fixing the commit title. Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-12-05 21:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-05  5:58 [Buildroot] [PATCH 1/1] modify site from adoptopenjdk mirror to official hg.openjdk.java.net repository Tudor Holton
2019-12-05 21:15 ` Thomas Petazzoni [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-12-05  5:57 Tudor Holton

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=20191205221515.30e00913@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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.
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.