Bug#744072: marked as done (RM: libfilesystem-ruby/0.5-3.1)
Your message dated Wed, 09 Apr 2014 20:59:52 +0200
with message-id <534598A8.7070806@thykier.net>
and subject line Re: Bug#744072: RM: libfilesystem-ruby/0.5-3.1
has caused the Debian Bug report #744072,
regarding RM: libfilesystem-ruby/0.5-3.1
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.)
--
744072: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744072
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: rm
Dear Release-Team,
it appears src:libfilesystem-ruby is halfway stuck in testing:
- it's binary libfilesystem-ruby1.8 is NOT in testing
- source and binary libfilesystem-ruby1.9.1 are in testing
- src:libfilesystem-ruby Build-Depends on ruby1.8 which is NOT in
testing.
- there's no indication of a pending autoremove triggered by #735654.
I think it's safe to just entirely remove this package from testing, so
I'd suggest doing exactly that.
Thanks,
Christian
--- End Message ---
--- Begin Message ---
On 2014-04-09 20:39, Christian Hofstaedtler wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: rm
>
> Dear Release-Team,
>
> it appears src:libfilesystem-ruby is halfway stuck in testing:
>
> - it's binary libfilesystem-ruby1.8 is NOT in testing
> - source and binary libfilesystem-ruby1.9.1 are in testing
> - src:libfilesystem-ruby Build-Depends on ruby1.8 which is NOT in
> testing.
> - there's no indication of a pending autoremove triggered by #735654.
>
> I think it's safe to just entirely remove this package from testing, so
> I'd suggest doing exactly that.
>
> Thanks,
> Christian
>
>
Hi,
Removal hint added.
Note you should probably (convince the maintainer to) have it removed
from unstable as well.
~Niels
--- End Message ---
Reply to: