[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#754981: marked as done (RM: rails-3.2/3.2.18-1)



Your message dated Thu, 17 Jul 2014 12:37:10 +0200
with message-id <53C7A756.2090108@debian.org>
and subject line Re: Bug#754981: RM: rails-3.2/3.2.18-1
has caused the Debian Bug report #754981,
regarding RM: rails-3.2/3.2.18-1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
754981: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754981
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: rm

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

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.

O.

- -- System Information:
Debian Release: 7.5
  APT prefers stable
  APT policy: (900, 'stable'), (800, 'testing'), (700, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJTxo+xAAoJEAyZtw70/LsHN20QAISvQtzNSw3gLpRQlETyxB7R
spVknbp+wNifvg8T1/RNZjEURWu5k8lRoDQDusRuT1+W6rfO4gsHq+H7xWrBDW+n
mHGkFXOI1LVYku6yQ3JGlTsrXsSnjZdNRKULr5vz7pgO+4KV2cYbm0KmO8/HEgz0
TfX+9RgNjIAgJSSrFkPsWUmlDmfBT8CK3FDauVcsvXX5tge4M8vaghKtgWL0dVKt
O2TguFeUthckVo8Lih2pqJu86KMm8Bbp+/USzs8kcn2oeDLNbbPSCBwnPUIyvekf
TpbxjcoN1xgx3X/JQek1BbI1s0bxbH+WZLi4MGsCuZ/W0vOreeu7lPh0noUw3+wx
Ia2YiiWvfTq4ZFZk/M2dFY5Pask03ST4QBL1gSNr5GWZllAHRDfS5Kx05y6epNfP
x/sKtpTi0OUwq7zqHW9f2rqjjvPmHY7AlLXmLqMZ06fkWx02Ft4NGPRKsoOHGrId
TOxWzx9Vo5FUeTeCMOhq0dDIA4o1X9S0ZErUNx7wbqK9Nb4+udeHu5r0mcCBOugl
5Y8rMmTvOlsiq0uJT1+T5eQY22EoELPxaoy2zpaGOdOJ4vTsfMIhBGxUjUsttk1y
AxPeytolhNq/ubj2r41hzS8ifOtLW7vdbJx6p+DV/+pUyWzDv/BC9zHmHWKZ5Bbp
ahyMWqsV1to+6ZcxPoaA
=65FY
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message ---
On 17/07/14 08:37, Ondřej Surý wrote:
> 
> 
> 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.org@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.

Sure, I just wanted to make sure I wasn't removing stuff that was important.

I have removed it now:

#20140716
# #754981
remove rails-3.2/3.2.18-1
remove rails/2:3.2.13+1 redmine/2.5.1-2
redmine-plugin-pretend/0.0.2+git20130821-1 redmine-recaptcha/0.1.0+git20121018-3
ruby-activerecord-nulldb-adapter/0.3.1-1 ruby-acts-as-taggable-on/2.4.1-1
ruby-asset-sync/1.0.0-1 ruby-awesome-nested-set/2.1.6-1
ruby-bootstrap-sass/2.3.1.0-2 ruby-carrierwave/0.8.0-2 ruby-coffee-rails/3.2.2-2
ruby-email-validator/1.4.0-1 ruby-em-synchrony/1.0.3-1 ruby-factory-girl/4.4.0-1
ruby-factory-girl-rails/4.2.1-1 ruby-fixture-builder/0.3.6-1
ruby-foreigner/1.4.1-1 ruby-i18n-inflector-rails/1.0.7-1
ruby-jquery-rails/3.1.0-1 ruby-jquery-ui-rails/4.2.0-1 ruby-mobile-fu/1.3.1-1
ruby-origin/1.1.0-1 ruby-rabl/0.10.1-1 ruby-rabl-rails/0.3.4-1
ruby-rails-autolink/1.1.0-1 ruby-recaptcha/0.3.6-2.1 ruby-remotipart/1.2.1-1
ruby-roxml/3.3.1-3 ruby-rspec-rails/2.13.2-2 ruby-sass-rails/3.2.5-2
ruby-simple-navigation/3.11.0-1 ruby-sinatra-simple-navigation/3.6.0-1
ruby-sinon-rails/1.4.2.1-1

And it's gone from testing. Note that I didn't remove the packages that
build-depend on rails but don't depend on it, as britney doesn't check for those
and they would have migrated back immediately. Please sort those out too.

Closing.

Cheers,
Emilio

--- End Message ---

Reply to: