Bug#597252: marked as done (unblock: librack-ruby/1.1.0-4)
Your message dated Sat, 18 Sep 2010 16:05:20 +0100
with message-id <1284822320.12215.22.camel@kaa.jungle.aubergine.my-net-space.net>
and subject line Re: Bug#597252: unblock: librack-ruby/1.1.0-4
has caused the Debian Bug report #597252,
regarding unblock: librack-ruby/1.1.0-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 owner@bugs.debian.org
immediately.)
--
597252: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597252
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 librack-ruby
Fixes #583553. Other changes are cosmetic.
unblock librack-ruby/1.1.0-4
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (700, 'unstable'), (500, 'stable'), (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)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
On Sat, 2010-09-18 at 16:45 +0200, Lucas Nussbaum wrote:
> On 18/09/10 at 09:26 +0100, Adam D. Barratt wrote:
> > On Sat, 2010-09-18 at 08:44 +0200, Lucas Nussbaum wrote:
> > > Please unblock package librack-ruby
> > >
> > > Fixes #583553. Other changes are cosmetic.
> >
> > This appears to have been rejected by dak due to the .orig.tar.gz
> > mentioned in the .dsc not matching the copy already in the archive;
> > please let us know once it's been re-uploaded and accepted.
>
> Accepted now.
Unblocked.
Regards,
Adam
--- End Message ---
Reply to: