hi, > >> If the package still exists (even as an empty transitional package), >> use versioned Breaks+Replaces (<< >> the-first-version-no-longer-shipping-the-files~) The trailing ~ is >> recommended for backports-compatibility. Breaks are much easier to >> handle for the package manager than Conflicts. > > But Breaks does not forbid unpacking both packages together, which is > really impossible, as both contain the same file. All this suggests > > Conflicts: python-pywbem (<< 0.8.0~dev650-1~) > > should be added to sblim-wbemcli to avoid this error on any setup. > Do you agree?
no. Breaks and replaces is just doing the right thing. Breaks: python-pywbem (<< 0.8.0~dev650-1~) Replaces: python-pywbem (<< 0.8.0~dev650-1~) This allows to replace the file which is the reason for the problems. -- Bernd Zeimetz Debian GNU/Linux Developer http://bzed.de http://www.debian.org GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
