4
down vote
accepted
I spent quite some time investigating this same issue and I reached the conclusion that the the "Provides" is ignored because xen-utils-4.0 has a versioned "Depends" on xen-utils-common.
Quoting the Debian Policy Manual:
A Provides field may not contain version numbers, and the version number of the concrete package which provides a particular virtual package will not be considered when considering a dependency on or conflict with the virtual package name.
If the Depends were unversioned, the provides would have been satisfied, however a Provides, which is always unversioned, can never satisfy a versioned Depends.
Unfortunately, I do not have a solution apart from what you have already proposed: keeping the same package name and having a higher version number.
http://serverfault.com/questions/362241/deb-provides-field-ignored
4 down vote accepted I spent quite some time investigating this same issue and I reached the conclusion that the the "Provides" is ignored because xen-utils-4.0 has a versioned "Depends" on xen-utils-common.
Quoting the Debian Policy Manual:
A Provides field may not contain version numbers, and the version number of the concrete package which provides a particular virtual package will not be considered when considering a dependency on or conflict with the virtual package name. If the Depends were unversioned, the provides would have been satisfied, however a Provides, which is always unversioned, can never satisfy a versioned Depends.
Unfortunately, I do not have a solution apart from what you have already proposed: keeping the same package name and having a higher version number.