Bug#603613: marked as done (unblock: libjsr166y-java/0.1.20080107-2)
Your message dated Mon, 15 Nov 2010 20:33:54 +0000
with message-id <1289853234.4014.486.camel@hathi.jungle.funky-badger.org>
and subject line Re: Bug#603613: unblock: libjsr166y-java/0.1.20080107-2
has caused the Debian Bug report #603613,
regarding unblock: libjsr166y-java/0.1.20080107-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 owner@bugs.debian.org
immediately.)
--
603613: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603613
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock
Please unblock package libjsr166y-java.
libjsr166y-java should be unblocked in order to close an RC
bug (#602362) already fixed in unstable. This should not be
a problem because the diff between 0.1.20080107-1 and
0.1.20080107-2 is small.
unblock libjsr166y-java/0.1.20080107-2
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/bash
--
Miguel Landaeta, miguel at miguel.cc
secure email with PGP 0x7D8967E9 available at http://keyserver.pgp.com/
"Faith means not wanting to know what is true." -- Nietzsche
--- End Message ---
--- Begin Message ---
On Mon, 2010-11-15 at 15:19 -0430, Miguel Landaeta wrote:
> libjsr166y-java should be unblocked in order to close an RC
> bug (#602362) already fixed in unstable. This should not be
> a problem because the diff between 0.1.20080107-1 and
> 0.1.20080107-2 is small.
Unblocked.
Regards,
Adam
--- End Message ---
Reply to: