Quoting the ubuntu-devel@ conversation here for easier future reference: « In doing SRU reviews today, I came across LP: #1889106 which is a request for a no-change rebuild to bump the version so it beats the versions presented in previous releases.
The problem is real, but it seems suboptimal to me to keep fixing it this way. We'll need to keep SRUing chromium-browser to Focal (and later releases presumably). Every time we do that, all users (who have the transitional package) get yet another update to download, even if it is small. And every time it takes both Olivier's and the SRU team's time. Would an epoch bump be a better option here? Debian doesn't currently carry a package with that name, so we're already diverged enough that I don't forsee a problem from there. » xnox answered: « lxd used epoch too, to ensure that deb2snap transitional package is always higher whichever backports are uploaded as debs into previous series. https://launchpad.net/ubuntu/+source/lxd So +1 from me. » and vorlon answered: « I agree that an epoch bump on the transitional .deb in focal is a reasonable solution for this issue. » ** Description changed: - For a complete rational, 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. + 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892724 Title: Bump package epoch to 1 to ensure working upgrade path and transition to snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1892724/+subscriptions -- ubuntu-bugs mailing list firstname.lastname@example.org https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs