On Thu, Jan 16, 2014 at 07:33:09PM +0100, Francesco Poli wrote: > On Thu, 16 Jan 2014 11:52:45 +0100 Antonio Terceiro wrote: > > > On Wed, Jan 15, 2014 at 09:48:57PM +0100, Francesco Poli wrote: > [...] > > > What if both ruby1.8 and ruby1.9.1 are already installed and ruby1.8 > > > was previously (manually) configured as the system-wide alternative > > > for /usr/bin/ruby? > > > > > > Which package will pull in ruby, thus forcing the removal of ruby1.8? > > > All packages depending on "ruby | ruby-interpreter" will be satisfied > > > by ruby1.9.1, if I understand correctly... > > > > > > Is there a way to fix this scenario too? > > > > You are right! > > > > I will do another "last upload" of ruby1.8 dropping the alternatives > > entries ... :-/ > > Excellent, thanks a lot!
Actually, that's not what I'll do. We are having a Ruby team sprint in Paris, and together we just figured out a way of fixing the problem for both stable and testing/unstable. There should be uploads soon. -- Antonio Terceiro <terce...@debian.org>
signature.asc
Description: Digital signature
