Your message dated Sun, 12 Aug 2012 22:37:24 +0100
with message-id <1344807444.2978.96.ca...@jacala.jungle.funky-badger.org>
and subject line Re: Bug#683317: unblock: openssl/1.0.1c-4
has caused the Debian Bug report #683317,
regarding unblock: openssl/1.0.1c-4
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.)
--
683317: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683317
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
Please unblock openssl/1.0.1c-4
Kurt
--- End Message ---
--- Begin Message ---
On Thu, 2012-08-09 at 22:33 +0200, Kurt Roeckx wrote:
> On Mon, Jul 30, 2012 at 08:46:13PM +0200, Kurt Roeckx wrote:
> > Please unblock openssl/1.0.1c-4
[...]
> + * Fix the configure rules for alpha (Closes: #672710)
> + * Switch the postinst to sh again, there never was a reason to
> + switch it to bash (Closes: #676398)
> + * Fix pic.patch to not use #ifdef in x86cpuid.s, only .S files are
> + preprocessed. We generate the file again for pic anyway.
> + (Closes: #677468)
> + * Drop Breaks against openssh as it was only for upgrades
> + between versions that were only in testing/unstable.
> + (Closes: #668600)
Most of those changes don't really qualify under the letter of the
freeze policy, given that libssl1.0.0 is priority important. However, I
can see the last change being sufficiently annoying for upgrades that
I've unblocked the package.
Regards,
Adam
--- End Message ---
