Your message dated Fri, 09 Jun 2017 19:04:00 +0000
with message-id <[email protected]>
and subject line Re: Bug#864506: unblock: 
ruby-benchmark-suite/1.0.0+git.20130122.5bded6-2
has caused the Debian Bug report #864506,
regarding unblock: ruby-benchmark-suite/1.0.0+git.20130122.5bded6-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 [email protected]
immediately.)


-- 
864506: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864506
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: unblock

Dear Release Managers: I wish this package to be unblocked:

unblock ruby-benchmark-suite/1.0.0+git.20130122.5bded6-2


It was removed from testing because of a FTBFS bug:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840572

But the bug was really only "random" so I recategorized it as
"important" to be in line with most other random FTBFS bugs:

https://bugs.debian.org/cgi-bin/[email protected];tag=ftbfs-randomly

The diff is empty because no new upload was required.

I am well aware that release policy says "packages are not allowed in
testing after they are removed", but that's precisely why we call
exceptions to these requests.

Thanks.

--- End Message ---
--- Begin Message ---
Santiago Vila:
> Package: release.debian.org
> Severity: normal
> User: [email protected]
> Usertags: unblock
> 
> Dear Release Managers: I wish this package to be unblocked:
> 
> unblock ruby-benchmark-suite/1.0.0+git.20130122.5bded6-2
> 
> 
> It was removed from testing because of a FTBFS bug:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840572
> 
> But the bug was really only "random" so I recategorized it as
> "important" to be in line with most other random FTBFS bugs:
> 
> https://bugs.debian.org/cgi-bin/[email protected];tag=ftbfs-randomly
> 
> The diff is empty because no new upload was required.
> 
> I am well aware that release policy says "packages are not allowed in
> testing after they are removed", but that's precisely why we call
> exceptions to these requests.
> 
> Thanks.
> 

Hi,

Thanks for the request.

However:

 * There seems to be nothing special about this package or the
   situation that would normally warrant this kind of exception[1].

 * The timing is way too late.  (

 * Maintainer reaction seems non-existent in this case

Accordingly, I do not intend to grant the exception to unblock this package.

Thanks,
~Niels

[1] RC bugs being downgraded post-freeze do not warrant that packages
were re-admitted into testing.

--- End Message ---

Reply via email to