The version requirements were relaxed a couple releases ago to allow the
installation of newer libraries. Occasionally folks want to run a newer
library to pick up a specific fix before upgrading all of ceph.
We definitely want installation and upgrade to be surprise free. Maybe it is
reasonable to require all the packages to be the same or greater version than
the ceph package ?
Thanks,
Gary
On May 8, 2013, at 1:21 AM, Sylvain Munaut wrote:
> Hi,
>
>
> In the debian/control file, the dependency from one ceph package to
> the other doesn't always specify that version should match.
> For example the 'ceph' package depends on 'ceph-common' but not on
> 'ceph-common (= ${binary:Version})'.
>
> The result is that when I did a "apt-get install ceph" to upgrade it (
> apt-get upgrade wouldn't have updated it automatically because it had
> new dependencies ), it only updated the 'ceph' package and not
> librados/ceph-common/... and I had to make another "apt-get upgrade"
> to finish the upgrade.
>
> And if you don't pay attention you could end up with mixed version installed.
>
> Is there a reason not to force all version of installed ceph package to match
> ?
>
>
> Cheers,
>
> Sylvain
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
