Hello Andrew, On Sun, Jan 03, 2016 at 08:54:58PM +0100, Ralf Treinen wrote: > Package: ruby-rubysl-test-unit,ruby-test-unit > Version: ruby-rubysl-test-unit/2.0.3-1 > Version: ruby-test-unit/3.1.5-1 > Severity: serious > User: trei...@debian.org > Usertags: edos-file-overwrite > > Date: 2016-01-03 > Architecture: amd64 > Distribution: sid > > Hi, > > automatic installation tests of packages that share a file and at the > same time do not conflict by their package dependency relationships has > detected the following problem: > > [...] > trying to overwrite '/usr/lib/ruby/vendor_ruby/test/unit.rb', which is also > in package ruby-test-unit 3.1.5-1 > Processing triggers for libc-bin (2.21-6) ... > Processing triggers for man-db (2.7.5-1) ... > Errors were encountered while processing: > /var/cache/apt/archives/ruby-rubysl-test-unit_2.0.3-1_all.deb > E: Sub-process /usr/bin/dpkg returned an error code (1)
This should be expected. Why do we need ruby-rubysl-test-unit (and ruby-rubysl)? These rubysl* packages contain the Ruby standard library, and are mostly only used with rubinius, which is an alternative Ruby interpreter that we don't have in Debian¹, so I don't see why we would need them. ¹ I tried packaging rubinius myself at some point, but gave up when they split the standard library into a gazilion independent packages that would have to be packaged independently. -- Antonio Terceiro <terce...@debian.org>
signature.asc
Description: PGP signature
