the src:package ayatana-indicator-messages contains bin:pkgs (libmessagingmenu*) that have the same name as Ubuntu's src:pkg indicator-messages.
The src:pkg indicator-messages has a higher version number than ayatana-indicator-messages and thus the latter fails to be imported
into Ubuntu.
See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000801
The solution for this probably is bumping the epoch of the package
version to 1:0.9.x-y. Any objections to this by anyone?
Bumping the epoch to 1 would be sufficient, right?
Hi Mike,
Quoting Mike Gabriel (2021-12-12 13:53:55)
the src:package ayatana-indicator-messages contains bin:pkgs
(libmessagingmenu*) that have the same name as Ubuntu's src:pkg
indicator-messages.
The src:pkg indicator-messages has a higher version number than
ayatana-indicator-messages and thus the latter fails to be imported
into Ubuntu.
See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000801
The solution for this probably is bumping the epoch of the package
version to 1:0.9.x-y. Any objections to this by anyone?
Bumping the epoch to 1 would be sufficient, right?
Binary packages need not use same versions as source package.
Instead of introducing an epoch you could pass option -v to
dpkg-gencontrol via dh_gencontrol.
See https://salsa.debian.org/js-team/jsbundle-web-interfaces/-/blob/debian/master/debian/rules#L65
for an example - notice that the source version is appended to ensure
that binary packages get incremented with each new source release.
HI Jonas,
On So 12 Dez 2021 14:26:35 CET, Jonas Smedegaard wrote:
Hi Mike,
Quoting Mike Gabriel (2021-12-12 13:53:55)
the src:package ayatana-indicator-messages contains bin:pkgs
(libmessagingmenu*) that have the same name as Ubuntu's src:pkg
indicator-messages.
The src:pkg indicator-messages has a higher version number than
ayatana-indicator-messages and thus the latter fails to be imported
into Ubuntu.
See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000801
The solution for this probably is bumping the epoch of the package
version to 1:0.9.x-y. Any objections to this by anyone?
Bumping the epoch to 1 would be sufficient, right?
Binary packages need not use same versions as source package.
Instead of introducing an epoch you could pass option -v to
dpkg-gencontrol via dh_gencontrol.
See https://salsa.debian.org/js-team/jsbundle-web-interfaces/-/blob/debian/master/debian/rules#L65
for an example - notice that the source version is appended to ensure
that binary packages get incremented with each new source release.
Yeah, I am aware of that possibility. However, I don't really feel
like inheriting the versioning from the Ubuntu package (year.month) in
the Debian package and be forced to carry that one along with me in
the future forever...
I'd rather use the upstream version (of ayatana-indicator-messages)
and be done with it.
Yeah, I am aware of that possibility. However, I don't really feel
like inheriting the versioning from the Ubuntu package (year.month) in
the Debian package and be forced to carry that one along with me in
the future forever...
I'd rather use the upstream version (of ayatana-indicator-messages)
and be done with it.
Quoting Mike Gabriel (2021-12-12 14:47:26)
HI Jonas,
On So 12 Dez 2021 14:26:35 CET, Jonas Smedegaard wrote:
Hi Mike,https://salsa.debian.org/js-team/jsbundle-web-interfaces/-/blob/debian/master/debian/rules#L65
Quoting Mike Gabriel (2021-12-12 13:53:55)
the src:package ayatana-indicator-messages contains bin:pkgs
(libmessagingmenu*) that have the same name as Ubuntu's src:pkg
indicator-messages.
The src:pkg indicator-messages has a higher version number than
ayatana-indicator-messages and thus the latter fails to be imported
into Ubuntu.
See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000801
The solution for this probably is bumping the epoch of the package
version to 1:0.9.x-y. Any objections to this by anyone?
Bumping the epoch to 1 would be sufficient, right?
Binary packages need not use same versions as source package.
Instead of introducing an epoch you could pass option -v to
dpkg-gencontrol via dh_gencontrol.
See
for an example - notice that the source version is appended to ensure
that binary packages get incremented with each new source release.
Yeah, I am aware of that possibility. However, I don't really feel
like inheriting the versioning from the Ubuntu package (year.month) in
the Debian package and be forced to carry that one along with me in
the future forever...
I'd rather use the upstream version (of ayatana-indicator-messages)
and be done with it.
Epochs should be avoided when possible, because they (by design) are
hidden in some interfaces, and therefore can cause surprises (e.g.
intending to tighten to "newer-than-some-version" but forgetting to
include the epoch - and not noticing the mistake until after the freeze
many moons later).
If you don't want to keep track of Ubuntu changing their versions
because you know that yours should always beat theirs, then how about statically setting binary version higher yet within zero'th epoch?
dh_gencontrol -- -v9999~$(DEB_VERSION)
- Jonas
On 12.12.21 19:22, Jeremy Bicha wrote:
Therefore, it seems pretty easy to me for you to just bump the
upstream version in its next release from 0.9.0 to 13.11.0 (or 14.0 or
14.9.0 or whatever higher number). Blame Ubuntu in your release notes.
That seems like the least complex way to handle this. No epochs. No
version skew between upstream and Debian. No version skew between the
Debian source package and the binary packages. No version skew between
Debian and Ubuntu. No tricky version number mangling in debian/rules.
Version numbers are cheap. It's really not a big deal to bump your
version from 0.9 to 14. After that, you don't have any obligation to
do year.month versioning.
Yeah, I think this is the way to go. Especially since this also
affects other distros which will also have the same issue.
If ayatana-indicator-messages is the natural successor of indicator-messages it should just make sure to have a higher
(upstream) version number.
And there is prior art here. E.g. systemd bumped it's version bumper
from v44 to v183 after it had merged the udev sources (which at that
point were at version v182).
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 71:21:16 |
Calls: | 6,656 |
Calls today: | 2 |
Files: | 12,201 |
Messages: | 5,332,224 |
Posted today: | 1 |