On Thu, 4 Jan 2007, Steve Langasek wrote:
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?
Yes, but the functionality provided by libdevel-logger-ruby is the same
that libruby1.8 provides.
If you check http://raa.ruby-lang.org/project/devel-logger/, it
says: "devel-logger is bundled together with ruby distribution after ruby/1.8.
This package is for ruby-1.6."
So, it seems that this package was wrongly migrated to ruby1.8.
Then the maintainer removed the 1.8 package from etch, and in dummy package
libdevel-logger-ruby, the file /usr/share/doc/libdevel-logger-ruby/README.Debian
says:
libdevel-logger-ruby for Debian
-------------------------------
Ruby Devel::Logger
It was bundled in ruby1.8 as logger.rb. This is just dummy package
so that you may remove it.
-- Fumitoshi UKAI <[EMAIL PROTECTED]>, Fri, 12 May 2006 01:44:51 +0900
If libruby1.8 already provides this functionality, then it should
remove the old (and wrong) one.
Also, if this packages remains in upgrades to etch, some rails applications
do not work.
Why?
Because it has an file called application.rb, that gets in the way of
rails application.rb. Stupid classload issues.
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]
