On Wed, Jul 16, 2014, at 22:56, Emilio Pozuelo Monfort wrote: > On 16/07/14 16:44, Ondřej Surý wrote: > > Package: release.debian.org > > Severity: normal > > User: release.debian....@packages.debian.org > > Usertags: rm > > > > Hi, > > > > we are aiming at having only latest rails (or no rails at all) > > package in next Debian stable. > > > > Please remove rails-3.2 and all packages further down the tree > > from testing, so we can first sort it out in unstable before > > leaving a mess in testing. > > This is what dak says: > [...a quite a long list... ] > > I'm not sure we're supposed to drop rails (in addition to rails-3.2)
Yes, please. > as well as things like ruby-haml, ruby-markerb, ruby-moneta... > that seem unrelated to rails. rails-3.2 has now a RC bug - that stuff should be autoremoved anyway in time, right? Removing this manually would just give the debian-ruby time to fix this much faster (e.g. before freeze). I could probably walk through the packages and drop the ruby-activesupport (which is the most common case in the depends) dependency where applicable (f.e. I seen haml Gemfile without any rails dependency). But most of the packages really depend on some rails component. And I don't simply believe that all those packages will "just work" with rails 4.1, it needs a test rebuild. I have discussed this on debian-ruby list before and no objections were raised. And we must absolutely not ship jessie with rails-3.2 or we end up in the same nightmare as in wheezy. I know it's a harsh move, but no rails is better than obsolete rails with no security support from upstream. O. -- Ondřej Surý <ond...@sury.org> Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1405579066.12622.142587121.0fe01...@webmail.messagingengine.com
