Re: RFC: reverting ruby-rack to 1.4.x with an epoch

2013-10-28 Thread Antonio Terceiro
On Sun, Oct 27, 2013 at 08:15:11PM +0100, Christian Hofstaedtler wrote: > * Ondřej Surý [131024 21:28]: > > What about temporarily introducing "rack1.4" package and use that as > > dependency in rails-3.2 (together with adding Breaks: rails-*-3.2 to > > rack 1.5) > > While preparing a ruby-rack-1

Re: RFC: reverting ruby-rack to 1.4.x with an epoch

2013-10-27 Thread Christian Hofstaedtler
* Ondřej Surý [131024 21:28]: > What about temporarily introducing "rack1.4" package and use that as > dependency in rails-3.2 (together with adding Breaks: rails-*-3.2 to > rack 1.5) While preparing a ruby-rack-1.4 package is easy, it will take a while to get through NEW. (Apparently, queue leng

Re: RFC: reverting ruby-rack to 1.4.x with an epoch

2013-10-26 Thread Sam Ruby
On 10/26/2013 07:34 AM, Sam Ruby wrote: On 10/26/2013 03:47 AM, Cédric Boutillier wrote: On Thu, Oct 24, 2013 at 09:22:06PM +0200, Ondřej Surý wrote: What about temporarily introducing "rack1.4" package and use that as dependency in rails-3.2 (together with adding Breaks: rails-*-3.2 to rack 1.

Re: RFC: reverting ruby-rack to 1.4.x with an epoch

2013-10-26 Thread Sam Ruby
On 10/26/2013 03:47 AM, Cédric Boutillier wrote: On Thu, Oct 24, 2013 at 09:22:06PM +0200, Ondřej Surý wrote: What about temporarily introducing "rack1.4" package and use that as dependency in rails-3.2 (together with adding Breaks: rails-*-3.2 to rack 1.5) This is another idea, which could so

Re: RFC: reverting ruby-rack to 1.4.x with an epoch

2013-10-26 Thread Cédric Boutillier
On Thu, Oct 24, 2013 at 09:22:06PM +0200, Ondřej Surý wrote: > What about temporarily introducing "rack1.4" package and use that as > dependency in rails-3.2 (together with adding Breaks: rails-*-3.2 to > rack 1.5) This is another idea, which could solve the problem, and I guess it really depends

Re: RFC: reverting ruby-rack to 1.4.x with an epoch

2013-10-25 Thread Youhei SASAKI
At Thu, 24 Oct 2013 21:22:06 +0200, Ondřej Surý wrote: > > What about temporarily introducing "rack1.4" package and use that as > dependency in rails-3.2 (together with adding Breaks: rails-*-3.2 to > rack 1.5) +1 --- Youhei SASAKI GPG fingerprint: 4096/RSA: 66A4 EA70 4FE2 4

Re: RFC: reverting ruby-rack to 1.4.x with an epoch

2013-10-24 Thread Ondřej Surý
What about temporarily introducing "rack1.4" package and use that as dependency in rails-3.2 (together with adding Breaks: rails-*-3.2 to rack 1.5) Ondrej -- Ondřej Surý Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- To UNSUBSCRIBE, email to debian-ruby-requ...@lists.de

Re: RFC: reverting ruby-rack to 1.4.x with an epoch

2013-10-23 Thread Antonio Terceiro
On Tue, Oct 22, 2013 at 06:57:58PM -0600, Bob Proulx wrote: > Cédric Boutillier wrote: > > Antonio Terceiro wrote: > > > I am planning to revert ruby-rack on unstable back to upstream version > > > 1.4.x by using an epoch. ruby-rack 1.5.x breaks rails session > > > management, and as a consequence,

Re: RFC: reverting ruby-rack to 1.4.x with an epoch

2013-10-22 Thread Bob Proulx
Cédric Boutillier wrote: > Antonio Terceiro wrote: > > I am planning to revert ruby-rack on unstable back to upstream version > > 1.4.x by using an epoch. ruby-rack 1.5.x breaks rails session > > management, and as a consequence, redmine. > > Thanks for taking care of this. > ... > About the epoch

Re: RFC: reverting ruby-rack to 1.4.x with an epoch

2013-10-22 Thread Cédric Boutillier
Hi Antonio, On Sun, Oct 20, 2013 at 04:35:54PM -0300, Antonio Terceiro wrote: > Hello everyone, > I am planning to revert ruby-rack on unstable back to upstream version > 1.4.x by using an epoch. ruby-rack 1.5.x breaks rails session > management, and as a consequence, redmine. Thanks for taking

RFC: reverting ruby-rack to 1.4.x with an epoch

2013-10-20 Thread Antonio Terceiro
Hello everyone, I am planning to revert ruby-rack on unstable back to upstream version 1.4.x by using an epoch. ruby-rack 1.5.x breaks rails session management, and as a consequence, redmine. More details in the correspondin bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711236 For now, t