Debian Bug report logs - #781865
docker.io: release cycle is too fast for stable

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Paul Tagliamonte <paultag@debian.org>

To: submit@bugs.debian.org

Subject: RM: docker.io -- RoM; release cycle is too fast for stable

Date: Mon, 30 Mar 2015 19:30:47 -0400

[Message part 1 (text/plain, inline)]

Package: release.debian.org
User: release.debian.org@packages.debian.org
Usertags: rm
Severity: minor
X-Debbugs-CC: docker-maint@lists.alioth.debian.org
thanks

Hey release;

After talking with Docker upstream, I've decided that the best course of
action to ensure users get a working version of Docker is to strip this
from jessie and maintain it in jessie-backports, keeping that up to date
with upstream's release cadence while it's undergoing active iteration.

Please remove src:docker.io and associated binaries from testing.


Thanks for all your work on the release team,
  Paul

-- 
 .''`.  Paul Tagliamonte <paultag@debian.org>  |   Proud Debian Developer
: :'  : 4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
`. `'`  http://people.debian.org/~paultag
 `-     http://people.debian.org/~paultag/conduct-statement.txt

[signature.asc (application/pgp-signature, inline)]

Message #10 received at 781554-done@bugs.debian.org (full text, mbox, reply):

From: "Adam D. Barratt" <adam@adam-barratt.org.uk>

To: Paul Tagliamonte <paultag@debian.org>, 781554-done@bugs.debian.org

Subject: Re: Bug#781554: RM: docker.io -- RoM; release cycle is too fast for stable

Date: Tue, 31 Mar 2015 07:31:24 +0100

On 2015-03-31 0:30, Paul Tagliamonte wrote:
> After talking with Docker upstream, I've decided that the best course 
> of
> action to ensure users get a working version of Docker is to strip this
> from jessie and maintain it in jessie-backports, keeping that up to 
> date
> with upstream's release cadence while it's undergoing active iteration.
> 
> Please remove src:docker.io and associated binaries from testing.

Removal hint added.

Regards,

Adam

Message #23 received at 781865@bugs.debian.org (full text, mbox, reply):

From: "Adam D. Barratt" <adam@adam-barratt.org.uk>

To: Felipe Sateler <fsateler@debian.org>

Cc: debian-release@lists.debian.org, 781865@bugs.debian.org

Subject: Re: Processed: cloning 781554, reopening -1, retitle -1 to docker.io: release cycle is too fast for stable ...

Date: Sat, 04 Apr 2015 08:46:24 +0100

Control: reassign -1 src:docker.io

On Sat, 2015-04-04 at 01:03 +0000, Debian Bug Tracking System wrote:
> Processing commands for control@bugs.debian.org:
> 
> > clone 781554 -1
> Bug #781554 {Done: "Adam D. Barratt" <adam@adam-barratt.org.uk>} [release.debian.org] RM: docker.io -- RoM; release cycle is too fast for stable
> Bug 781554 cloned as bug 781865
> > reopen -1
> Bug #781865 {Done: "Adam D. Barratt" <adam@adam-barratt.org.uk>} [release.debian.org] RM: docker.io -- RoM; release cycle is too fast for stable
> Bug reopened
> Ignoring request to alter fixed versions of bug #781865 to the same values previously set
> > retitle -1 docker.io: release cycle is too fast for stable
> Bug #781865 [release.debian.org] RM: docker.io -- RoM; release cycle is too fast for stable
> Changed Bug title to 'docker.io: release cycle is too fast for stable' from 'RM: docker.io -- RoM; release cycle is too fast for stable'
> > severity -1 serious
> Bug #781865 [release.debian.org] docker.io: release cycle is too fast for stable
> Severity set to 'serious' from 'minor'

Given that having such a bug assigned to release.d.o makes no sense, I
assume you simply forgot to reassign it.

Regards,

Adam

Message #30 received at 781865@bugs.debian.org (full text, mbox, reply):

From: Felipe Sateler <fsateler@debian.org>

To: "Adam D. Barratt" <adam@adam-barratt.org.uk>

Cc: Debian Release Team <debian-release@lists.debian.org>, 781865@bugs.debian.org

Subject: Re: Processed: cloning 781554, reopening -1, retitle -1 to docker.io: release cycle is too fast for stable ...

Date: Sat, 4 Apr 2015 12:41:28 -0300

On 4 April 2015 at 04:46, Adam D. Barratt <adam@adam-barratt.org.uk> wrote:
> Control: reassign -1 src:docker.io
>
> On Sat, 2015-04-04 at 01:03 +0000, Debian Bug Tracking System wrote:
>> Processing commands for control@bugs.debian.org:
>>
>> > clone 781554 -1
>> Bug #781554 {Done: "Adam D. Barratt" <adam@adam-barratt.org.uk>} [release.debian.org] RM: docker.io -- RoM; release cycle is too fast for stable
>> Bug 781554 cloned as bug 781865
>> > reopen -1
>> Bug #781865 {Done: "Adam D. Barratt" <adam@adam-barratt.org.uk>} [release.debian.org] RM: docker.io -- RoM; release cycle is too fast for stable
>> Bug reopened
>> Ignoring request to alter fixed versions of bug #781865 to the same values previously set
>> > retitle -1 docker.io: release cycle is too fast for stable
>> Bug #781865 [release.debian.org] RM: docker.io -- RoM; release cycle is too fast for stable
>> Changed Bug title to 'docker.io: release cycle is too fast for stable' from 'RM: docker.io -- RoM; release cycle is too fast for stable'
>> > severity -1 serious
>> Bug #781865 [release.debian.org] docker.io: release cycle is too fast for stable
>> Severity set to 'serious' from 'minor'
>
> Given that having such a bug assigned to release.d.o makes no sense, I
> assume you simply forgot to reassign it.

Yes, sorry, the reassign command was missing.

-- 

Saludos,
Felipe Sateler

Message #35 received at 781865-done@bugs.debian.org (full text, mbox, reply):

From: Paul Tagliamonte <paultag@debian.org>

To: 781865-done@bugs.debian.org

Subject: allow into testing

Date: Tue, 28 Apr 2015 13:42:35 -0400

[Message part 1 (text/plain, inline)]

Hey folks,

I'm removing this bug so we can migrate to testing, so that we can put
this into backports.

Thanks, team!
  Paul

-- 
 .''`.  Paul Tagliamonte <paultag@debian.org>  |   Proud Debian Developer
: :'  : 4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
`. `'`  http://people.debian.org/~paultag
 `-     http://people.debian.org/~paultag/conduct-statement.txt

[signature.asc (application/pgp-signature, inline)]

Send a report that this bug log contains spam.