Bug#1067675: library package (arch any) depending on a "common" package with too strict version constraint

[Jeremy Bícha]

Cloning a bug in the way you did is not very helpful. mutter's
situation is different than folks.

The mutter binary package has Depends: mutter-common (>= ${source:Version})

That allows mutter to be binNMU'd.

An alternative is to do something like evolution which has this override:

dh_makeshlibs -V'libevolution (>= $(DEB_VERSION_UPSTREAM)),
libevolution (<< $(DEB_GNOME_NEXTVERSION))'

which translates to this when built on Unstable (3.50.3-1+b1) :

dh_makeshlibs -V'libevolution (>= 3.50.3), libevolution (<< 3.51)'

We do actually need the upstream version of the -common package to
match the other binary packages. I am not convinced there is even
value in switching to the evolution style since it seems rare for
there to be an upload after the first upload for an upstream version
(-2 or higher basically) where the fact that sometimes arch: all
builds slower than other architectures is enough of a problem in these
packages to make the packaging more complicated.

I would prefer to revert your Ubuntu diff for mutter so that if this
bug is fixed, it is fixed in Debian first.

Thank you,
Jeremy Bícha