One of the possible impacts of bumping the version like this is that if
a user has a local deb of chromium-browser installed that is higher than
the current version, the new epoch will cause them to be upgraded to the
transitional package that they had already opted out of.
This should be called out and the pros and cons weighed in the bug
description ("Where problems can occur" / "Regression potential")
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2007702
Title:
[SRU] Deb version numbering is misleading
Status in chromium-browser package in Ubuntu:
Fix Released
Status in chromium-browser source package in Focal:
In Progress
Status in chromium-browser source package in Jammy:
In Progress
Status in chromium-browser source package in Lunar:
In Progress
Status in chromium-browser source package in Mantic:
Incomplete
Bug description:
[Impact]
For Ubuntu >= Focal the transitional debs are frozen at the version number
1:85...
This might make one think[1][2] that it will install a critically
outdated Chromium while it does not, because it installs the snap.
[Test plan]
Install the package and confirm the version change with e.g.
dpkg -l | grep '^ii *chromium-browser *2:1snap1-0ubuntu1'
[Regression potential]
If the version were incorrectly constructed the deb build could fail.
[1]
https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/702591
[2] https://askubuntu.com/q/1420925
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007702/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
