IBM JDK >=8.0.5.0 integration into Ubuntu

[bugproxy]

This is the first bugzilla, which will held all the information of the process of integrate IBM JDK into Ubuntu

[dann frazier (dannf)]

This bug doesn't impact the kernel (linux), so I attempted to reassign it to ibm-java80. For some reason, LP won't let me do that - so I've temporarily assigned it against ibm-java71.

Is there any reason this bug needs to be embargoed? If not - I'd like to change the settings to "public".

Finally - IBM provides the builds for these releases - we just review and either upload, or request changes. Please point me to a build if there is one ready to review. Usually IBM uploads a build to Canonical's anonymous FTP server and provides me with a list of filenames, and I request retrieval of those files from our IS dept.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2017-10-23 09:54 EDT-------
We are documenting the outstanding issues from the last packaging (8.0.4.11) to track them to logical closure.

The following is the last mail communication from <email address hidden>

----------
Hi Surya,
Thanks! I've reviewed and uploaded both of these packages, and they are pending acceptance.
I had to make some minor changes to both - all within the changelog. Please see the commits in these branches for an explanation:

https://git.launchpad.net/~dannf/+git/ibm-java/log/
https://git.launchpad.net/~dannf/+git/ibm-java/log/?h=master71

If you can sync these changes in before your next build, then I think we're very close to me being able to take future updates unmodified.
When adding a new changelog entry for the next release, please be sure to use the correct date syntax. The new entry in the 71 release looked good, but the 80 entry had the following issue:

The timestamp in debian/changelog has incorrect syntax. It should
match the output of the 'date -R' command, with 2 spaces between the
user and the timestamp. See debian policy section 4.4.

-dann
----------

@Surya please confirm you will address those pending issues in this work item for 8.0.5.0.

Also, please provide the outlook of when the 8.0.5.0 packages will be available in the ftp site.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2017-10-24 02:27 EDT-------
@Heinz, @Nasser:

We will take care of those comments and see that they are not present in our next set of packages we release for 8.0.5.0.

We should be uploading the packages mostly by today EOD, once completed will update this bug and also raise a new bug for the packages.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2017-10-25 01:49 EDT-------
Uploaded the Debian packages onto the Canonical FTP Server for 8.0.5.0
80sr5_20170905_01_ocdc.tar.gz

foreman@cit7r02:~/sandbox/binary$ ftp archive.admin.canonical.com
Connected to archive.admin.canonical.com.
220 youngberry.canonical.com FTP server (Poppy Upload Server) ready.
Name (archive.admin.canonical.com:foreman): anonymous
331 Password required
Password:
230 Login Successful.
Remote system type is UNIX.
Using binary mode to transfer files.
ftp> bin
200 Type set to Binary.
ftp> prompt off
Interactive mode off.
ftp> put 80sr5_20170905_01_ocdc.tar.gz
local: 80sr5_20170905_01_ocdc.tar.gz remote: 80sr5_20170905_01_ocdc.tar.gz
200 PORT command successful.
150 Opening Binary connection for /80sr5_20170905_01_ocdc.tar.gz

226 Transfer successful.
644033574 bytes sent in 386.49 secs (1627.3 kB/s)
ftp>
ftp> quit

Contact Information = <email address hidden>

---uname output---
Linux s390x
Linux AMD64,
Linux x86,
Linux PPC64LE

Machine Type = Ubuntu

[dann frazier (dannf)]

I've uploaded this package and it is now pending review in the SRU queue:
  https://launchpad.net/ubuntu/xenial/+queue?queue_state=1

Typically we need to poke someone in that team to process these uploads - I'll assign to skipper-screen-team to handle that monitoring/poking :)

Note for IBM's Java developers: For future uploads, please start with the changelog from the existing upload[*] and append to the top of it. While new entries are looking good, the entries for old releases don't match what is currently in the partner archive. Also, when there's a bug for a new release (like this one), it'd be good to reference it in the changelog so that LP can automatically close the bug when the upload is approved. These are the only 2 changes I had to make locally - but I'd prefer to be able to upload exactly what you provide.

[*] https://git.launchpad.net/~dannf/+git/ibm-java?h=master

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2017-10-26 02:39 EDT-------
(In reply to comment #14)
> I've uploaded this package and it is now pending review in the SRU queue:
> https://launchpad.net/ubuntu/xenial/+queue?queue_state=1
>
> Typically we need to poke someone in that team to process these uploads -
> I'll assign to skipper-screen-team to handle that monitoring/poking :)
>
> Note for IBM's Java developers: For future uploads, please start with the
> changelog from the existing upload[*] and append to the top of it. While new
> entries are looking good, the entries for old releases don't match what is
> currently in the partner archive. Also, when there's a bug for a new release
> (like this one), it'd be good to reference it in the changelog so that LP
> can automatically close the bug when the upload is approved. These are the
> only 2 changes I had to make locally - but I'd prefer to be able to upload
> exactly what you provide.
>
> [*] https://git.launchpad.net/~dannf/+git/ibm-java?h=master

Hi,

This is the reference changelog file which I have taken
https://git.launchpad.net/~dannf/+git/ibm-java/tree/debian/changelog?id=55ad396a0d68089ef8a8f8758003a7fb7034b84f

And added the release entry for 8.0.5.0 as below:

ibm-java80 (8.0.5.0-0ubuntu1) xenial; urgency=medium

* New upstream release.

-- Java Information Manager <email address hidden> Tue, 24 Oct 2017 12:33:49 +0530

Overall the content of the changelog that we delivered is:

------------------
ibm-java80 (8.0.5.0-0ubuntu1) xenial; urgency=medium

* New upstream release.

-- Java Information Manager <email address hidden> Tue, 24 Oct 2017 12:33:49 +0530

ibm-java80 (8.0.4.11-0ubuntu1) xenial; urgency=medium

* New upstream release.

-- Java Information Manager <email address hidden> Wed, 06 Sep 2017 14:56:00 +0530

ibm-java80 (8.0.4.1-0ubuntu1) xenial; urgency=medium

* New upstream release.
* Packaging cleanups

-- Java Information Manager <email address hidden> Fri, 24 Feb 2017 16:17:33 +0530

------------------

I hope this was what is expected, going forward we will continue the same and pick the changelog from launchpad and append our new release entry.
Only change we did was to keep the Author details as JIM.

Also, regarding the bug entry, I think this bug is just for tracking and doesn't fix any issue, hence we feel that there is no need to add the Bug entries in the changelog.

[Steve Langasek (vorlon)]

ibm-java80 8.0.5.0 accepted into xenial-proposed. Please test once built and confirm that these packages work as expected, and post here to confirm so that they can be published to the xenial release pocket.

[dann frazier (dannf)]

Not sure why we can't mark this as impacting Ubuntu/ibm-java80. Opened an issue w/ Launchpad (LP: #1727496)

[dann frazier (dannf)]

Next step is for someone to test the update in xenial-proposed and notify an archive-admin that it is ok to promulgate into xenial-updates. Frank: would you be able to do that bit?

[Frank Heimes (fheimes)]

Did another series of test on the
ibm-java80-jre:s390x (8.0.5.0-0ubuntu1)
ibm-java80-jdk:s390x (8.0.5.0-0ubuntu1)
packages (from proposed partner) and it's content on 16.04.3

It looks good so far, hence I think the archive-admin may promulgate them to the update pocket...

[Dimitri John Ledkov (xnox)]

ibm-java80 is in xenial partner repository now.

Marking as fix released.

https://launchpad.net/ubuntu/+source/ibm-java80

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2017-11-09 08:47 EDT-------
IBM Bugzilla Status-> closed; ibm-java80 is in xenial partner repository now.