Hi, On Sun, Nov 23, 2014 at 6:54 PM, Andrey Rahmatullin <w...@debian.org> wrote: > On Sun, Nov 23, 2014 at 06:06:33PM +0100, Margarita Manterola wrote: >> I've uploaded a new version of ruby-em-hiredis, which fixes the FTBFS >> (#759917), and I have requested the unblock of this package (#770728). >> If ruby-em-hiredis gets unblocked, then ruby-em-synchrony could be >> also unblocked and this one would get solved. > AFAIK the freeze migration policy is "only packages already in testing get > migrated", ruby-em-synchrony is not in testing.
I asked about this earlier on IRC and I was told that if a package had been in testing and got removed due to a RC bug, it would be accepted back again provided the fix followed the normal freeze policy, and the same for the other one that got transitively removed: @1416741742 <marga> So, if a package was removed already from testing due to FTBFS, and now dependencies are failing because of that, is it worth fixing it? Will it be accepted back? @1416741863 <nthykier> marga: Sounds reasonable at first glance, but it assumes that the changes between "last-version-in-testing" and upload complies with the freeze policy -- Regards, Marga -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
