Hi all, On 10/08/14 05:32 PM, Antonio Terceiro wrote:
Hi Caitlin, On Sun, Aug 10, 2014 at 02:54:46PM -0400, Caitlin Matos wrote:Hi Antonio, What can I do to help at this point?At this point, the only missing piece in unstable is ruby-sdoc which is waiting in NEW; everything is already in.Note that I've not used Rails much, so I don't know how helpful I can be. However, I'd like to help where I can, since this is a huge block in updating/fixing other packages!I don't think there is anything blocked by rails at this point. Would you say there is?
Let me rephrase that: Rails (or lack thereof) is stalling the transition of many packages from unstable to testing. Also, there are some packages that have newer upstream releases with rails 4.x support. Technically, these could be upgraded and uploaded, but it would be nice to have a reliable version of Rails to work with.
https://release.debian.org/migration/stalls.html* 27 packages are stalled by ruby-sprockets-rails (8 days old, waiting for rails, rails-4.0) [Debian Ruby Extras Maintainers] * 27 packages are stalled by rails-4.0 (241 days old, has RC bugs, waiting for ruby-sprockets-rails) [Debian Ruby Extras Maintainers] * 27 packages are stalled by rails (6 days old, waiting for ruby-sprockets-rails) [Debian Ruby Extras Maintainers] * 16 packages are stalled by rails-3.2 (24 days old, has RC bugs) [Debian Ruby Extras Maintainers]
However, whenever anyone updates a package that is in the rails dependency chain, it would be nice if one could test that rails still passes at least its autopkgtest tests. The easiest way to to that is to install rails and the updated package locally, and run: $ adt-run rails --- null (yes those are three(3) dashes) If that exits with 0, it should probably be ok. If not, it would be nice to check with me before uploading the package.
I'll definitely do this when upgrading packages.