Your message dated Sat, 14 Mar 2015 11:22:17 +0100
with message-id <55040bd9.6050...@thykier.net>
and subject line Re: Bug#772183: unblock: libjpeg6b/1:6b2-2
has caused the Debian Bug report #772183,
regarding unblock: libjpeg6b/1:6b2-2
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.)
--
772183: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772183
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: unblock
Dera release team,
Please unblock package libjpeg6b (and unstuck it from NEW).
libjpeg6b binaries were hijacked by the libjpeg-turbo source package, but this
have been resolved. So I made a new libjpeg6b upload so that the libjpeg6b
binaries get rebuilt. However this caused libjpeg6b to be directed to the NEW
queue, which is still there. So it missed the freeze deadline
Given that libjpeg6b is in wheezy, and the package was fully expected to be
released in jessie before it was hijacked, I would appreciate if you would
unstuck it.
unblock libjpeg6b/1:6b2-2
Thanks for your understanding,
--
Bill. <ballo...@debian.org>
Imagine a large red swirl here.
--- End Message ---
--- Begin Message ---
On 2015-02-23 17:49, Niels Thykier wrote:
> Control: tags -1 wontfix
>
> [...]
>
> As debated in #774737, we will only be shipping with one implementation
> of libjpeg, so I am afraid I will have to decline this request.
>
> Yours truly,
> ~Niels
>
>
And closing the bug...
Thanks,
~Niels
--- End Message ---
