Discussion:
Chromium browser, from v 120 to 123?
(too old to reply)
Markus Robert Kessler
2024-04-06 06:20:58 UTC
Permalink
Hi,

when I started my MGA9 this morning, there was an update of a few
packages.

One of them updated chromium web browser (tainted) from v. 120 to 123.

Does anyone know why this big step was necessary?

Best regards,

Markus
David W. Hodgins
2024-04-06 06:45:47 UTC
Permalink
Post by Markus Robert Kessler
when I started my MGA9 this morning, there was an update of a few
packages.
One of them updated chromium web browser (tainted) from v. 120 to 123.
Does anyone know why this big step was necessary?
It's not unusual for packages to skip numbers, as some releases fail to get
through qa testing, or the packager who handles it for Mageia doesn't get
around to updating the Mageia version before the next version is released.

In this case chromium was pushed as quickly as it could be, as the next
release is already ready to start being built and qa testing.

I'm no longer involved in the testing, but do still skim through the mailing
lists to keep track of what's going on.

Regards, Dave Hodgins
Markus Robert Kessler
2024-04-06 07:08:06 UTC
Permalink
On Sat, 06 Apr 2024 02:20:58 -0400, Markus Robert Kessler
Post by Markus Robert Kessler
when I started my MGA9 this morning, there was an update of a few
packages.
One of them updated chromium web browser (tainted) from v. 120 to 123.
Does anyone know why this big step was necessary?
It's not unusual for packages to skip numbers, as some releases fail to
get through qa testing, or the packager who handles it for Mageia
doesn't get around to updating the Mageia version before the next
version is released.
In this case chromium was pushed as quickly as it could be, as the next
release is already ready to start being built and qa testing.
I'm no longer involved in the testing, but do still skim through the
mailing lists to keep track of what's going on.
Regards, Dave Hodgins
Hi,

good to know, thanks!

I am using it for things like online banking, so, usually I try to
undestand why an update was necessary and what it does.

Best regards,

Markus
David W. Hodgins
2024-04-06 16:17:09 UTC
Permalink
Post by Markus Robert Kessler
good to know, thanks!
I am using it for things like online banking, so, usually I try to
undestand why an update was necessary and what it does.
See https://bugs.mageia.org/show_bug.cgi?id=33056#c2 for the details.

Regards, Dave Hodgins
Markus Robert Kessler
2024-04-07 13:47:45 UTC
Permalink
On Sat, 06 Apr 2024 03:08:06 -0400, Markus Robert Kessler
Post by Markus Robert Kessler
good to know, thanks!
I am using it for things like online banking, so, usually I try to
undestand why an update was necessary and what it does.
See https://bugs.mageia.org/show_bug.cgi?id=33056#c2 for the details.
Page doesn't load. Seems to be offline.

Could this be the reason why v 123 is not yet available for i686?
It doesn't show up in tainted updates / updates-testing.

Best regards,

Markus
TJ
2024-04-07 17:56:16 UTC
Permalink
Post by Markus Robert Kessler
Page doesn't load. Seems to be offline.
Just showed up on the Mageia blog that the servers are down. It's being
investigated.
Post by Markus Robert Kessler
Could this be the reason why v 123 is not yet available for i686?
It doesn't show up in tainted updates / updates-testing.
The latest two Chromiums will not build for i686, and it's something we
apparently can't change, so 32-bit systems will no longer be supported.

Without access to Bugzilla, I don't remember the reason off the top of
my head. I'll post the link when I see Bugzilla is back.

TJ
Daniel65
2024-04-08 09:31:35 UTC
Permalink
Post by TJ
Post by Markus Robert Kessler
Page doesn't load. Seems to be offline.
Just showed up on the Mageia blog that the servers are down. It's being
investigated.
Post by Markus Robert Kessler
Could this be the reason why v 123 is not yet available for i686?
It doesn't show up in tainted updates / updates-testing.
The latest two Chromiums will not build for i686, and it's something we
apparently can't change, so 32-bit systems will no longer be supported.
Without access to Bugzilla, I don't remember the reason off the top of
my head. I'll post the link when I see Bugzilla is back.
TJ
The Bugs page is still not loading!! "Network Timeout"

https://bugs.mageia.org/show_bug.cgi?id=33056#c2
--
Daniel
Markus Robert Kessler
2024-04-08 12:04:59 UTC
Permalink
Post by Daniel65
Post by TJ
Post by Markus Robert Kessler
Page doesn't load. Seems to be offline.
Just showed up on the Mageia blog that the servers are down. It's being
investigated.
Post by Markus Robert Kessler
Could this be the reason why v 123 is not yet available for i686?
It doesn't show up in tainted updates / updates-testing.
The latest two Chromiums will not build for i686, and it's something we
apparently can't change, so 32-bit systems will no longer be supported.
Without access to Bugzilla, I don't remember the reason off the top of
my head. I'll post the link when I see Bugzilla is back.
TJ
The Bugs page is still not loading!! "Network Timeout"
https://bugs.mageia.org/show_bug.cgi?id=33056#c2
The page is back again.

But, why cannot Chromium be built? Dependency problem?

At least, Mageia is -- still -- one the very rare distros supporting 32bit
machines. I have some of them still, and it would really hurt having to
throw them away.

Best regards,

Markus
TJ
2024-04-08 12:11:26 UTC
Permalink
Post by Daniel65
Post by TJ
Post by Markus Robert Kessler
Page doesn't load. Seems to be offline.
Just showed up on the Mageia blog that the servers are down. It's
being investigated.
Post by Markus Robert Kessler
Could this be the reason why v 123 is not yet available for i686?
It doesn't show up in tainted updates / updates-testing.
The latest two Chromiums will not build for i686, and it's something
we apparently can't change, so 32-bit systems will no longer be
supported.
Without access to Bugzilla, I don't remember the reason off the top of
my head. I'll post the link when I see Bugzilla is back.
TJ
The Bugs page is still not loading!! "Network Timeout"
https://bugs.mageia.org/show_bug.cgi?id=33056#c2
Seems to be back up now. Daniel's link does show the note that is in the
advisory. For a more detailed but possibly more difficult to understand
explanation, see

https://bugs.mageia.org/show_bug.cgi?id=33032#c0

TJ

Loading...