Package: libsemanage-ruby1.8 Version: 2.1.6-5 Severity: serious User: [email protected] Usertags: piuparts
Hi, during a test with piuparts I noticed your package is no longer installable in sid: 0m20.0s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmp4QSseq', 'eatmydata', 'apt-get', '-y', 'install', 'libsemanage-ruby1.8=2.1.6-5'] 0m20.3s DUMP: Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libsemanage-ruby1.8 : Depends: ruby-semanage but it is not going to be installed E: Broken packages 0m20.3s ERROR: Command failed (status=100): ['chroot', '/tmp/piupartss/tmp4QSseq', 'eatmydata', 'apt-get', '-y', 'install', 'libsemanage-ruby1.8=2.1.6-5'] Package: libsemanage-ruby1.8 Version: 2.1.6-5 Depends: ruby-semanage Package: ruby-semanage Version: 2.1.6-5 Replaces: libsemanage-ruby1.8 Provides: libsemanage-ruby1.8 Depends: ruby | ruby-interpreter, libc6 (>= 2.4), libsemanage1 (>= 2.1.6) Conflicts: libsemanage-ruby1.8 A simple apt-get install libsemanage-ruby1.8 (without explicit '=version' appended) fails as well. I think the Replaces/Provides/Conflicts to get rid of the transitional package needs to be done in wheezy+1 (and the transitional should be droppen then), for wheezy you should probably have (if the rename occurred in 2.1.6-3): Package: ruby-semanage Replaces: libsemanage-ruby1.8 (<< 2.1.6-3) Breaks: libsemanage-ruby1.8 (<< 2.1.6-3) Cheers, Andreas
libsemanage-ruby1.8_2.1.6-5.log.gz
Description: GNU Zip compressed data
