Your message dated Sun, 6 Aug 2017 23:04:26 +0200
with message-id <20170806210426.GB29673@yellowpig>
and subject line Re: Bug#871007: libjpeg9: should libjpeg9 be removed from
unstable?
has caused the Debian Bug report #871007,
regarding libjpeg9: should libjpeg9 be removed from unstable?
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
871007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871007
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libjpeg9
User: debian...@lists.debian.org
Usertags: qa-removals-post-stretch
Hi,
Following a discussion[1] on the debian-qa@ mailing list on packages that
missed both jessie and stretch, I am proposing the removal of this package from
unstable, because:
it was in unstable at the time of the stretch freeze
but wasn't part of stretch
AND
it was in unstable at the time of the jessie freeze
but it wasn't part of jessie
AND
it is still not in testing
AND
it was not uploaded since the beginning of 2017.
If you disagree and think that this package should remain in unstable, feel
free to just close this bug.
If this bug is still open one month from now (on 2017-09-06), it will be turned
into a removal request, using:
reassign -1 ftp.debian.org
retitle -1 RM: libjpeg9 -- RoQA; missed both jessie and stretch
thanks
- Lucas, for the QA team.
[1] https://lists.debian.org/debian-qa/2017/07/msg00021.html
--- End Message ---
--- Begin Message ---
On Sun, Aug 06, 2017 at 09:50:12AM -0400, Lucas Nussbaum wrote:
> Source: libjpeg9
> User: debian...@lists.debian.org
> Usertags: qa-removals-post-stretch
>
> Hi,
>
> Following a discussion[1] on the debian-qa@ mailing list on packages that
> missed both jessie and stretch, I am proposing the removal of this package
> from
> unstable, because:
Hello Lucas,
> it was in unstable at the time of the stretch freeze
> but wasn't part of stretch
> AND
> it was in unstable at the time of the jessie freeze
> but it wasn't part of jessie
> AND
> it is still not in testing
This due to the release team blocking it for their own reason.
> AND
> it was not uploaded since the beginning of 2017.
This is due to the freeze. There is an upload planned in January.
> If you disagree and think that this package should remain in unstable, feel
> free to just close this bug.
Done. Thanks for your concern!
Cheers,
--
Bill. <ballo...@debian.org>
Imagine a large red swirl here.
--- End Message ---
