** Description changed: + As a follow-up to bug #1889106, it was decided that the best solution to handle recurring version bumps for chromium-browser updates in stable series was to bump the package epoch to 1. + See the discussion in https://lists.ubuntu.com/archives/ubuntu-devel/2020-August/041127.html. + This needs to be done in groovy (done) and SRUed to focal. + + [Impact] + + Users upgrading from 18.04 to 20.04 will not get the latest chromium snap replacing the chromium-browser deb package as intended as soon as a security update is published to bionic-security (which happens typically every 2-3 weeks). + This is because the version number in 18.04 often ends up being greater than the version in 20.04. Bumping the version number in 20.04 is enough to fix this, and was done a few times already (bug #1858500, bug #1889106), but it is tedious and impractical. + + [Test Case] + + * Ensure that a version of chromium-browser newer than 84.0.4147.105-0ubuntu0.20.04.1 is available in bionic-{security,updates} (not currently the case, but will soon happen as version 85.0.4183.83 was just released upstream) + * On a machine running 18.04, ensure that the chromium snap is *not* installed, then install the chromium-browser deb package: sudo apt install chromium-browser + * Upgrade that machine to Ubuntu 20.04 + * When upgrading, the chromium-browser package becomes a transitional package that installs the chromium snap + * Verify that the chromium snap is installed + + [Regression Potential] + + * The chromium snap has some known shortcomings and regressions + compared to the deb package, they are being tracked at + https://bugs.launchpad.net/ubuntu/+source/chromium- + browser/+bugs?field.tag=snap. Auto-upgrading users from the deb to the + snap is the desired behaviour though. + + [Original Description] + For a complete rationale, see comments #4, #5, #7 and #8 in bug #1889106, and the discussion in https://lists.ubuntu.com/archives /ubuntu-devel/2020-August/041127.html. This needs to be done in groovy and SRUed to focal.
-- 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/1892724 Title: Bump package epoch to 1 to ensure working upgrade path and transition to snap Status in chromium-browser package in Ubuntu: Fix Released Status in chromium-browser source package in Focal: Triaged Bug description: As a follow-up to bug #1889106, it was decided that the best solution to handle recurring version bumps for chromium-browser updates in stable series was to bump the package epoch to 1. See the discussion in https://lists.ubuntu.com/archives/ubuntu-devel/2020-August/041127.html. This needs to be done in groovy (done) and SRUed to focal. [Impact] Users upgrading from 18.04 to 20.04 will not get the latest chromium snap replacing the chromium-browser deb package as intended as soon as a security update is published to bionic-security (which happens typically every 2-3 weeks). This is because the version number in 18.04 often ends up being greater than the version in 20.04. Bumping the version number in 20.04 is enough to fix this, and was done a few times already (bug #1858500, bug #1889106), but it is tedious and impractical. [Test Case] * Ensure that a version of chromium-browser newer than 84.0.4147.105-0ubuntu0.20.04.1 is available in bionic-{security,updates} (not currently the case, but will soon happen as version 85.0.4183.83 was just released upstream) * On a machine running 18.04, ensure that the chromium snap is *not* installed, then install the chromium-browser deb package: sudo apt install chromium-browser * Upgrade that machine to Ubuntu 20.04 * When upgrading, the chromium-browser package becomes a transitional package that installs the chromium snap * Verify that the chromium snap is installed [Regression Potential] * The chromium snap has some known shortcomings and regressions compared to the deb package, they are being tracked at https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bugs?field.tag=snap. Auto-upgrading users from the deb to the snap is the desired behaviour though. [Original Description] For a complete rationale, see comments #4, #5, #7 and #8 in bug #1889106, and the discussion in https://lists.ubuntu.com/archives /ubuntu-devel/2020-August/041127.html. This needs to be done in groovy and SRUed to focal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1892724/+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