Hi Tim, On Wed, Nov 05, 2014 at 11:00:52PM +0000, Potter, Tim (Cloud Services) wrote: > On 6/11/14 8:30 AM, "Cédric Boutillier" <boutil@debian.org> wrote: > >It seems that the problem with ruby-patron is not a problem of > >dependency but of build-dependency. To solve the problem, you would need > >to remove the build-dependency on ruby-patron and deactivate all the > >tests using patron (in ruby-elasticsearch-transport it seems). > > > >I'm afraid that it will be difficult to make this change move to > >testing, since the freeze is today, and this package never was in > >testing before. Fixing patron wouldn't help, because it is not in > >testing either. > > > >You can try to approach the release team and ask their opinion about > >this package that was prevented to enter testing because of a buggy > >build-dependency that was used only to run some (minor?) tests. > Hi Cedric. Thanks for the analysis - I was pretty down on the future of > this package but couldn't nail down the exact reasons. However it turns > out that somehow ruby-elasticsearch made it just in the nick of time! > https://packages.qa.debian.org/r/ruby-elasticsearch/news/20141105T163920Z.h > tml Great news. I am glad the package got to testing in time! > I'm not really sure why as I don't believe the ruby-patron problem was > fixed, but I'm not going to complain about it. (-: In fact, my analysis was not completely correct. Migration to testing is blocked by migration but not by that of build-dependencies it seems. But my guess is that ruby-elasticsearch will soon get a RC bug, because it is not buildable inside Jessie (because of ruby-patron). It will be time then to prepare a patch for this issue (maybe it is even better to start working on it now, just in case). Cédric
Attachment:
signature.asc
Description: Digital signature