On Fri, 12 Jan 2007, Steve Langasek wrote:
Well, it seems that the old logger was not part of the same source as
ruby. I'm not sure if the conflicts should go to ruby unless the new
ruby also has devel/logger.rb or application.rb. This doesn't seem to be
the case though.
Rather than a file conflict, this is a conflict of functionality; a target
use for the proposed "Breaks" dpkg field.
Yes, when breaks be out rails can use it.
I think I'll just add the needed conflicts for Etch and remove it in the
next upload after Etch is released. Seems like that may be the path of
least resistance.
While direct upgrades from sarge to lenny won't be supported, it would be
more accurate to just leave the Conflicts: in (or change it to Breaks:)
because the problem won't have disappeared, it'll just be less likely to be
encountered. (Well, maybe ruby1.8 will be deprecated by lenny, I guess
that's one possibility. :)
Matz said ruby 1.9.1 will be out by Christmas 07.... let's hope he can
meet that deadline and lenny will have ruby1.9 :D
filipe lautert
filipe { AT } icewall.org
Linux User #279798
Jabber [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
