On Thu, Jan 04, 2007 at 11:40:25AM -0200, Filipe wrote: > Package: libruby1.8 > Version: 1.8.5-4 > Severity: critical
> When upgrading from sarge to etch, the package libdevel-logger-ruby1.8 > isn't removed. > The functionality of this package was bundled in libruby1.8 as > /usr/lib/ruby/1.8/logger.rb. So, libruby1.8 should > replace/provide/conflict it, as it does with others packages that were > bundled in libruby1.8. /usr/lib/ruby/1.8/logger.rb was already provided by libruby1.8 in sarge. Why does the libruby1.8 in etch handle /usr/lib/ruby/1.8/devel/logger.rb any differently than libruby1.8 in sarge did? > Also, if this packages remains in upgrades to etch, some rails applications > do not work. Why? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
