On Fri, Jan 12, 2007 at 10:24:13AM -0600, Adam Majer wrote:
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
On Wed, Jan 10, 2007 at 02:33:23PM -0600, Adam Majer wrote:
Filipe wrote:
This package is from sarge, but if someone has this installed in sarge
and upgrades to etch, then it stay in the system. It provides the
same functionality that logger.rb from libruby1.8 provides, and it has a
file
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
Steve Langasek wrote:
On Wed, Jan 10, 2007 at 02:33:23PM -0600, Adam Majer wrote:
Filipe wrote:
This package is from sarge, but if someone has this installed in sarge
and upgrades to etch, then it stay in the system. It provides the
same functionality that logger.rb from libruby1.8 provides,
On Tue, 9 Jan 2007, Steve Langasek wrote:
reassign 40 rails
found 40 1.1.6-1
retitle 40 rails should conflict with libdevel-logger-ruby1.8
severity 40 serious
thanks
On Thu, Jan 04, 2007 at 07:52:22PM -0200, Filipe wrote:
Package: libruby1.8
Version: 1.8.5-4
Severity: critical
Filipe wrote:
This package is from sarge, but if someone has this installed in sarge
and upgrades to etch, then it stay in the system. It provides the
same functionality that logger.rb from libruby1.8 provides, and it has a
file
called application.rb that seems to get in the way of rails.
reassign 40 rails
found 40 1.1.6-1
retitle 40 rails should conflict with libdevel-logger-ruby1.8
severity 40 serious
thanks
On Thu, Jan 04, 2007 at 07:52:22PM -0200, Filipe wrote:
Package: libruby1.8
Version: 1.8.5-4
Severity: critical
When upgrading from sarge to etch, the
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
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.
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
10 matches
Mail list logo
