On 10.07.2012 09:37, Tollef Fog Heen wrote:
]] "Adam D. Barratt"
(please Cc me on replies, I'm not subscribed to the list)
Done, although I had to override the M-F-T...
On Thu, 2012-07-05 at 08:51 -0300, Antonio Terceiro wrote:
> If we can't get the fixed ruby-fast-xs in wheezy, then the
existing
> version of ruby-hpricot in wheezy will be fine, but we won't have
> chef-expander, which is an important piece in large-scale Debian
> deployments with chef.
Thanks for the explanation. If it's such an important part though,
it's
slightly surprising that there were no uploads to Debian (not even
to
experimental) until the day before the freeze. :-(
It's been developed and maintained in an upstream apt repository and
while I was in touch with them some years ago about getting it into
Debian, the effort was only seriously started early this summer.
Upstream has been doing packaging in their own repository for quite
some
time (as can be evidenced by the changelog).
Are they expecting to carry on doing that, or for everyone currently
using
their packages to switch wholesale over to using the packages from the
Debian
archive?
> This is why I am requesting this exception to be able to have
> ruby-fast-xs, the fixed ruby-hpricot and chef-expander in Wheezy.
It's not just those three packages, fwiw. chef-expander then ends
up
depending on a chain of a further six NEW packages (for a total of
eight
NEW sources, most uploaded within the couple of days before the
freeze).
They are at least in part based on chef's upstream packaging of
same. And, they're scheduled to go in today anyway, so the only
difference to whether ruby-fast-xs 0.8.0-3 is approved or not is
whether
that version plus chef-expander goes in, not the rest of the ruby
packages.
Fair point. It's still somewhat stretching the edges of the unblock
criteria
though, given that chef-expander's exception is based purely on the
grounds of it
being in unstable at the right time (with, as you know, some debate as
to whether
NEW packages should have been granted an exception even then) and the
bug in
ruby-hpricot doesn't affect the version of the package in wheezy.
Regards,
Adam
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/3f72291f09b745e3c863f52a60021...@mail.adsl.funky-badger.org
