Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: chromium-browser (Ubuntu Lunar)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscr
Ubuntu 23.10 (Mantic Minotaur) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: chromium-browser (Ubuntu Mantic)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is sub
Rejecting from the Unapproved queues as Steve's request above has not
been addressed in over a month.
--
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
** Changed in: chromium-browser (Ubuntu Focal)
Status: In Progress => Incomplete
** Changed in: chromium-browser (Ubuntu Jammy)
Status: In Progress => Incomplete
** Changed in: chromium-browser (Ubuntu Lunar)
Status: In Progress => Incomplete
--
You received this bug notifi
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 o
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 o
While I see Julian's point, I believe it's better to stick to the same
versioning scheme used in the Firefox deb, which is exactly what you did
for Noble:
firefox | 1:1snap1-0ubuntu2 | jammy | source, amd64,
arm64, armhf
firefox | 1:1snap1-0ubuntu3 | lunar
That scheme already made its way into Noble. Will we then [1] submit a
new package with that native package scheme for Noble, [2] do the native
package scheme only for the SRUs or [3] do the SRUs with the non-native
scheme for consistency?
--
You received this bug notification because you are a m
2:1snap1-0ubuntu1.22.04.1 is a non-native version number but of course
there is no upstream version, it would be a lot better to do this
correctly as a native package, like 2:1snap0ubuntu1.22.04.1
** Description changed:
- For Ubuntu >= Focal the transitional debs are frozen at the version
- numb
Thanks, Nathan.
Would you mind filing the SRU paperwork as per the template at
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template ?
I am unsure if this would be suitable for an SRU, but that's for the SRU
team to assess and decide.
Moreover, I see that you are using the same version f
10 matches
Mail list logo
