openjdk team mailing list archive

[László Böszörményi (GCS) <gcs@xxxxxxxxxx>]

Control: tag -1 -security

Hi Ben,

On Wed, Jan 27, 2016 at 11:43 PM, Ben Caradoc-Davies <ben@xxxxxxxxxxxx> wrote:
> Package: openjdk-7-jdk
> Version: 7u91-2.6.3-3
> Severity: serious
> Tags: security
> Justification: fails to build from source (but built successfully in the past)
>
> the openjdk-7_7u95-2.6.4-1 build on amd64 for Debian unstable has been missing
> for a week, despite being shown as green on maintainer QA pages, and being
> announced today in "[SECURITY] [DSA 3458-1] openjdk-7 security update" on
> <debian-security-announce@xxxxxxxxxxxxxxxx>.
 Please note the following things.
We (the Security Team) support stable and old-stable releases
(currently Jessie and Wheezy). The old-oldstable (Squeeze) release is
in the hands of the LTS team. Sid (and experimental) support provided
by the maintainer(s) him/herself.
We send out DSA mails for the mentioned two releases, when those are
built and available.
The QA pages show that the maintainer prepared and uploaded an updated
package. The auto build tasks start only after this and of course may
fail on some architectures.

> The build is "Maybe-Successful"
> https://buildd.debian.org/status/logs.php?arch=amd64&pkg=openjdk-7&ver=7u95-2.6.4-1
>
> but there are some errors:
> https://buildd.debian.org/status/fetch.php?pkg=openjdk-7&arch=amd64&ver=7u95-2.6.4-1&stamp=1453417092
 If you check previous build logs, then you can see this is 'expected'
- some self-tests are failing in the build chroot. Please check the
bottom of the build log, you can see that debs are built, files are
correctly installed into those. As such, the result line show:
'Status: successful'.
I've checked and the built package is uploaded to the pool, but
somehow doesn't installed into it. I send a Cc to the buildd admins
who may check what's the further status. Admins: please close this bug
when the package is accepted to the pool.

Thanks for your mail,
Laszlo/GCS