On Mon, 2019-09-02 at 11:26 +0700, Arnaud Rebillout wrote: > On 8/23/19 9:54 AM, Adam D. Barratt wrote: > > On 2019-08-18 15:41, Arnaud Rebillout wrote: > > > On 8/16/19 9:35 PM, Adam D. Barratt wrote: > > > > So is the conclusion there that docker.io is or is not actually > > > > affected? > > > > > > Yes docker.io is affected as well. > > > > Which of the binary packages are affected and need rebuilding? The > > packages produced are: > > > > docker-doc | 18.09.1+dfsg1-7.1 | stable | > > all > > docker.io | 18.09.1+dfsg1-7.1 | stable | > > source, amd64, arm64, armel, armhf, i386, ppc64el, s390x > > golang-docker-dev | 18.09.1+dfsg1-7.1 | stable | > > all > > golang-github-docker-docker-dev | 18.09.1+dfsg1-7.1 | stable | > > all > > vim-syntax-docker | 18.09.1+dfsg1-7.1 | stable | > > all > > > > If the answer is anything other than "just the docker.io binary > > package", then this will need to be a separate source upload, as > > we > > can't binNMU arch:all packages. > > Only docker.io needs rebuild
On a related note, the docker.io armel build from the last DSA appears to have failed to build. If that's a repeatable issue then we won't be able to usefully rebuild it here. Regards, Adam
