Andreas Beckmann <[email protected]> writes:

> Since no upgrade ordering is not guaranteed by the package manager, I'm
> looking for all possibly problematic (partial) upgrade paths from wheezy
> to jessie,

I'm afraid I don't understand.  You're talking about upgrades, but you
couldn't possibly have python-pywbem and sblim-wbemcli installed
together, unless python-pywbem was at 0.8.0~dev650-1, its latest
version.  And then there's no problem with any version of sblim-wbemcli.
No version of sblim-wbemcli is included in wheezy, though.

> that includes files being moved from one package to another (that may
> not have existed in wheezy.) And I try to really excercise all paths
> not forbidden by Breaks/Conflicts :-)

Maybe you install python-pywbem in wheezy, then switch sources to jessie
and install sblim-wbemcli without dist-upgrading first?  That's the only
scenario I can think of which exhibits this problem.

> On 2014-11-06 11:00, Ferenc Wagner wrote:
>
>> 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.
>
> If a package was in wheezy and is completely gone in jessie, unversioned
> Replaces+Conflicts in the successor are OK.

No, this is not the case, both packages are in jessie, but python-pywbem
has its former /usr/bin/wbemcli binary renamed to avoid conflict with
sblim-wbemcli.  Replaces does not play either, the packages have
different (tough in part similar) purposes, as well as the clashing
binaries.

> 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?
-- 
Thanks,
Feri.


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to