On 06/22/19 15:18, Langer, Christoph wrote:
Thanks, David.
Then I probably did the right thing by manually creating the backport bug.
You did the right thing.
cc-ing ops@o.j.n: Maybe you want to have a look why hgupdater failed in this
case?
hgupdater found a confidential backport record created for JDK 6 and
closed as 'will not fix'. hgupdater should not have used that backport,
but it did. I can see it in the History in JBS.
I undid the changes it made, and I'll file a bug against hgupdater.
Tim
Cheers
Christoph
-----Original Message-----
From: David Holmes <david.hol...@oracle.com>
Sent: Sonntag, 23. Juni 2019 00:15
To: Langer, Christoph <christoph.lan...@sap.com>; jdk-updates-
d...@openjdk.java.net; security-dev <security-dev@openjdk.java.net>
Subject: Re: OpenJDK 11u backport of JDK-8148188: Enhance the security
libraries to record events of interest
Hi Christoph,
On 22/06/2019 2:25 pm, Langer, Christoph wrote:
Hi,
I pushed the backport of JDK-8148188 [0] to jdk11u-dev [1] on Friday. I was
wondering why no 11.0.5 backport JBS item was created. I then manually
created JDK-8226636 [2], but the minute I had created it I got an idea what
the reason for that strange JBS/hgupdater behavior was (all other pushes
around this commit seem to have correct backport bugs). I now suspect that
there existed a confidential 11-pool backport item already which was
resolved by my push.
Can anybody within Oracle please check this and if I’m correct, please also
check whether the backport bug can be made public? I’d then close JDK-
8226636 as duplicate. But maybe I’m wrong with that guess… please
enlighten me 😊
No there was no confidential issue resolved by your push. I would have
to suspect hgupdater may be down, or else some other hgupdater
configuration problem.
David
------
Thanks
Christoph
[0] https://bugs.openjdk.java.net/browse/JDK-8148188
[1] http://hg.openjdk.java.net/jdk-updates/jdk11u-dev/rev/5f98a6a92842
[2] https://bugs.openjdk.java.net/browse/JDK-8226636
