[FFE] Bump up docker.io version to 1.5 in Vivid

[Pradipta Banerjee]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

docker.io version 1.3 and golang version 1.4, which is shipped as part of gccgo
v5, are not compatible. There are known issues with database corruption and
locking. More details can be found in the following link
https://github.com/docker/docker/pull/9615

Since docker.io for power LE requires gccgo v5, a version upgrade for docker
will be required.

 affects ubuntu/vivid/docker.io

- --
Regards,
Pradipta Kumar B
IBM Systems & Technology Labs,
India.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJVAC3cAAoJECC7L8Yv7baioiYH/0X7tI5oQ1Q+LJvnqnO8iWfl
A6CAg7q9ShjSV3XLFqY9m6o93y2Zin4eijXKSolaFIMLYrnjs6cz4gJv7Ci09/OG
i4xthJlLyJLIfOlfGLtGB5oGLkguZ0k8EBby4Xz27j8ZkmzfIhl4nsuAMAh6shrF
bkTxIzezYgLIGtgFg3OqLX4GAdHWMbr0kKDG9/dUaqMgcdFXkop29+EOlOH9bpUM
iWSPvHclgbJtTDVwumTzRyHbUJIkTAkXOOafJ+v44SsdBlm2YnEZ52UlHNSyIdfX
d0g8LekqEySfusV9K8CLFrU80A09Y+5J0QAvd6K5d+jmXFbHe6tf5UAo8Xwtk5A=
=ptUC
-----END PGP SIGNATURE-----

[Kick In (kick-d)]

To release-team:
I would like to warn you about this incoming Feature Freeze Exception Request, whilst the work is still ongoing.

[Robie Basak (racb)]

Debian is up to 1.5-1 now, so we would be best to update to this version.

[Robie Basak (racb)]

I mean 1.5.0~dfsg1-1 in experimental.

[Adam Conrad (adconrad)]

As doko and rbasak discussed on IRC, it might be nice to confirm that this docker will build and function with all the chosen compilers on all the architectures before we say yes. I think Robie said he'd look into this for us.

[Kick In (kick-d)]

Here is the deb diff, and build logs of the proposed docker-1.5.0~dfsg1-1ubuntu1 proposed package.

This has been built successfully on amd64, ppc64el, armhf (C1 Cores) and i386.

This has failed on arm64, but it was reported not working before, support has been dropped in 1.3.3~dfsg1-2ubuntu5 with the following comment:
d/control: Drop arm64 architecture for now as its going to require further work in the dependency chain.

This has been tested on amd64, ppc64el, and armhf.
Tests were just a docker daemon started, and a docker ubuntu container created, then ran apt-get update && apt-get -y upgrade inside the container and exit if everything seems ok.

armhf, amd64 and i386 built with:
golang

ppc64el built with:
gccgo

[Kick In (kick-d)]

build log for armhf

[Kick In (kick-d)]

ppc64el build log

[Kick In (kick-d)]

amd64 build log

[Kick In (kick-d)]

build-i386 build log

[Kick In (kick-d)]

Compilers versions used:
i386: golang (2:1.3.3-1ubuntu4)
amd64: golang (2:1.3.3-1ubuntu4)
armhf: golang (2:1.3.3-1ubuntu4)

pp64el: gccgo-5 (5-20150401-0ubuntu1)

[Robie Basak (racb)]

While working with kick-d I forgot to mention (my mistake):

golang-fsnotify and golang-logrus are new build dependencies that will need to be synced from Debian to the proposed 1.5 docker.io package to build. docker.io needs no new binary dependencies. This seemed low impact to me and I forgot about my mental note to mention these packages here - sorry.

[Kick In (kick-d)]

 golang-fsnotify-dev | 1.1.0-1 | experimental | all
 golang-fsnotify | 1.1.0-1 | experimental | source
 golang-logrus | 0.7.1-1 | sid | source
 golang-logrus-dev | 0.7.1-1 | sid | all

[Matthias Klose (doko)]

> This has failed on arm64, but it was reported not working before,
> support has been dropped in 1.3.3~dfsg1-2ubuntu5 with the following comment:
> d/control: Drop arm64 architecture for now as its going to require further work in the dependency chain.

well, why drop it when it built in 1.3.3~dfsg1-2ubuntu7?

[Kick In (kick-d)]

Raw dynbinary build (golang):

[Kick In (kick-d)]

docker.io_1.5.0~dfsg1-1ubuntu1_arm64-20150331-0449.build is a gccgo build sorry.

[Kick In (kick-d)]

Dynbinary arm64 build log (golang)

[Kick In (kick-d)]

New debdiff

[Adam Conrad (adconrad)]

So it doesn't get lost, this is a patch that fixes the build on arm64, can be dropped into debian/patches and added to debian/patches/series and should Just Work.

[Kick In (kick-d)]

Here is the new debdiff, and the build logs for all archs.

[Kick In (kick-d)]

armhf build log, it was successfull, and smoke test was also susccessfull.

smoke test was:
sudo docker run -it armbuild/ubuntu
and inside container:
apt-get update && apt-get -y upgrade

[Kick In (kick-d)]

ppc64el build log, it was successfull, and smoke test was also susccessfull.

smoke test was:
sudo docker run -it jjacobso/ubuntucore-ppc64le /bin/bash
and inside container:
apt-get update && apt-get -y upgrade

[Kick In (kick-d)]

arm64 build log, it was successfull, and smoke test was also susccessfull.

smoke test was:
sudo docker run -it ericvh/arm64-ubuntu
and inside container:
apt-get update && apt-get -y upgrade

[Kick In (kick-d)]

amd64 build log, it was successfull, and smoke test was also susccessfull.

smoke test was:
sudo docker run -it ubuntu
and inside container:
apt-get update && apt-get -y upgrade

[Kick In (kick-d)]

i386 build log, it was successfull, but I didn't ran smoke tests.

[Kick In (kick-d)]

Thanks Adam for the Arm64 patch!
The systemd patch was already applied as it was coming from docker 1.3.3 ubuntu7.

[Adam Conrad (adconrad)]

Not happy about the timing on this, but the rationale (better arch support from the current compilers, etc) and the testing seem decent enough. Approved.

[Launchpad Janitor (janitor)]

This bug was fixed in the package docker.io - 1.5.0~dfsg1-1ubuntu2

---------------
docker.io (1.5.0~dfsg1-1ubuntu2) vivid; urgency=medium

  * d/p/arm-syscall-fix.patch: Fix incorrect setns syscall on ARM.
  * d/p/powerpc-support.patch: Resolve FTBFS with powerpc builds.
 -- Adam Conrad <email address hidden> Fri, 10 Apr 2015 12:26:43 -0600