On Fri, Jul 17, 2015 at 01:21:16PM +0530, Pirate Praveen wrote: > On Thursday 16 July 2015 10:58 PM, Antonio Terceiro wrote: > >> Can I upload ruby-jquery-rails3 to fix the situation? > > > > this would remedy the original problem temporarily, but will create > > another one. It took us more than 1.5 years to get rid of ruby-rack1.4¹ > > > > ¹ https://tracker.debian.org/pkg/ruby-rack1.4 > > > > I would rather revert ruby-jquery-rails to the previous version using an > > upstream version number such as 4.0.4.REALLY.3.1.2, and work on doing a > > _planned_ update of all of these moving parts, staging the changes in > > experimental and being sure of what we are doing before doing it in > > unstable. > > Or would be better if we embed jquery-rails 3 with redmine like we did > bootstrap-sass 2 for diaspora? Since we will need jquery-rails sometime > soon.
this is a different situation. jquery-rails 4 is not fundamentally incompatible with jquery-rails 3, and there would be several options before embedding the dependency in redmine: a patch in the debian package, a patch upstream, etc etc. for example redmine upstream is already on rails 4.2 and they probably wouldn't expect a strong rejection to the idea of upgrading to jquery-rails 4.x as well. > Can this be even made a policy? "If a single application is blocking a > library update the older version can be embedded in that application". I think embedding is a last resort measure and if we make doing it a policy, we would be Doing it Wrong™. redmine upstream is already on rails 4.2 and could as well update to jquery-rails 4.x -- Antonio Terceiro <terce...@debian.org>
signature.asc
Description: Digital signature
