Andreas Beckmann <a...@debian.org> writes: > during a test with piuparts I noticed your package fails to upgrade from > 'wheezy'.
Hi, Something is strange here, as sblim-wbemcli was never part of wheezy, thus it is not supposed to be upgraded from there. > It installed fine in 'wheezy', then the upgrade to 'jessie' fails > because it tries to overwrite other packages files without declaring a > Breaks+Replaces relation. The sblim-wbemcli package indeed had a file conflict with python-pywbem 0.7.0-4 (see #679607). However, the conflicting file was renamed in the jessie version of python-pywbem. >>From the attached log (scroll to the bottom...): > > Selecting previously unselected package sblim-wbemcli. This sounds more like a new install of sblim-wbemcli, not an upgrade. > Unpacking sblim-wbemcli (from .../sblim-wbemcli_1.6.2-8_amd64.deb) ... > dpkg: error processing > /var/cache/apt/archives/sblim-wbemcli_1.6.2-8_amd64.deb (--unpack): > trying to overwrite '/usr/bin/wbemcli', which is also in package > python-pywbem 0.7.0-4 > dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) > Errors were encountered while processing: > /var/cache/apt/archives/sblim-wbemcli_1.6.2-8_amd64.deb Which is expected to fail with python-pywbem 0.7.0-4 present. However, I wonder how you managed to get into this situation. A wheezy -> jessie upgrade should have upgraded python-pywbem to 0.8.0~dev650-1, and you shouldn't experience problems trying to install sblim-wbemcli next to that version. > See policy 7.6 at > http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces Of course the above problem could be declared in the metadata of sblim-wbemcli, though 7.6 does not seem to apply here. 7.4 (Conflicts) seems more appropriate to me, if something really is needed. I initially thought it was not, but you surely know better, please advise me. -- Thanks, Feri. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
