Can you try whether chromium-browser-stable-118.0.5993.117-1.mga10.tainted from Cauldron tainted/updates_testing works?

CC'ing the registered chromium-browser-stable maintainer, assigning to the de facto maintainer

Source RPM: (none) => chromium-browser-stable-117.0.5938.132-1.mga10.tainted
CC: (none) => cjw, marja11
Assignee: bugsquad => chb0
Summary: Chromium 117.0.5938.132-1 not starting => Chromium 117.0.5938.132-1 not starting (symbol lookup error: /usr/bin/chromium-browser: undefined symbol: unzGetCurrentFileZStreamPos64)

Hi. 
Due to some lib updates, previous version of chromium can be broken. 
Any reason for not using the latest chromium 118 version ?

(In reply to Marja Van Waes from comment #1)
> Can you try whether chromium-browser-stable-118.0.5993.117-1.mga10.tainted
> from Cauldron tainted/updates_testing works?
> 
> CC'ing the registered chromium-browser-stable maintainer, assigning to the
> de facto maintainer

Thank you Marja, chromium-browser-stable-118.0.5993.117-1 from tainted/updates_testing starts and seems to run well. 

I'm not a chromium user, I just test Cauldron on a few spare devices I have :)

(In reply to christian barranco from comment #2)
> Hi. 
> Due to some lib updates, previous version of chromium can be broken. 
> Any reason for not using the latest chromium 118 version ?

Hi Christian,

No having tainted/updates_testing enabled is a good enough answer? :D

@ Christian,

Can you please either ask a sysadmin to move chromium-browser-stable-118.0.5993.88-1.mga10.tainted from updates_testing to tainted/release or bump release and push it directly to cauldron tainted/release?

(In reply to Marja Van Waes from comment #5)
> @ Christian,
> 
> Can you please either ask a sysadmin to move
> chromium-browser-stable-118.0.5993.88-1.mga10.tainted from updates_testing
> to tainted/release or bump release and push it directly to cauldron
> tainted/release?

I can certainly do, but, how come isn't it already there? 
Per https://bugs.mageia.org/show_bug.cgi?id=32459, the robot has pushed it!?

(In reply to christian barranco from comment #6)
> (In reply to Marja Van Waes from comment #5)
> > @ Christian,
> > 
> > Can you please either ask a sysadmin to move
> > chromium-browser-stable-118.0.5993.88-1.mga10.tainted from updates_testing
> > to tainted/release or bump release and push it directly to cauldron
> > tainted/release?
> 
> I can certainly do, but, how come isn't it already there? 
> Per https://bugs.mageia.org/show_bug.cgi?id=32459, the robot has pushed it!?
Answering to myself: robot had pushed it for MGA9. Here, the topic is for Cauldron and I had built Chromium 118 on testing by mistake...
I will push Chromium 119 soon instead.

Apologies, my bad...

In case the M119 build problem in cauldron with gn is not yet solved: I used (for M120):

--- chromium-120.0.6073.0/build/config/linux/atspi2/BUILD.gn.build	2023-10-17 22:09:11.717827800 +0200
+++ chromium-120.0.6073.0/build/config/linux/atspi2/BUILD.gn	2023-10-22 20:52:48.707839527 +0200
@@ -17,18 +17,16 @@ if (use_atk) {
                                       "--version-as-components",
                                     ],
                                 "value")
-    major = atspi_version[0]
     minor = atspi_version[1]
-    micro = atspi_version[2]
 
     # ATSPI 2.49.90 now defines these for us and it's an error for us to
     # redefine them on the compiler command line.
     # See ATSPI 927344a34cd5bf81fc64da4968241735ecb4f03b
-    if (minor < 49 || (minor == 49 && micro < 90)) {
+    if (minor < 49 || (minor == 49 && atspi_version[2] < 90)) {
       defines = [
-        "ATSPI_MAJOR_VERSION=$major",
+        "ATSPI_MAJOR_VERSION=atspi_version[0]",
         "ATSPI_MINOR_VERSION=$minor",
-        "ATSPI_MICRO_VERSION=$micro",
+        "ATSPI_MICRO_VERSION=$atspi_version[2]",
       ]
     }
   }

(In reply to Christiaan Welvaart from comment #8)
> In case the M119 build problem in cauldron with gn is not yet solved: I used
> (for M120):
> 
> --- chromium-120.0.6073.0/build/config/linux/atspi2/BUILD.gn.build
> 2023-10-17 22:09:11.717827800 +0200
> +++ chromium-120.0.6073.0/build/config/linux/atspi2/BUILD.gn	2023-10-22
> 20:52:48.707839527 +0200
> @@ -17,18 +17,16 @@ if (use_atk) {
>                                        "--version-as-components",
>                                      ],
>                                  "value")
> -    major = atspi_version[0]
>      minor = atspi_version[1]
> -    micro = atspi_version[2]
>  
>      # ATSPI 2.49.90 now defines these for us and it's an error for us to
>      # redefine them on the compiler command line.
>      # See ATSPI 927344a34cd5bf81fc64da4968241735ecb4f03b
> -    if (minor < 49 || (minor == 49 && micro < 90)) {
> +    if (minor < 49 || (minor == 49 && atspi_version[2] < 90)) {
>        defines = [
> -        "ATSPI_MAJOR_VERSION=$major",
> +        "ATSPI_MAJOR_VERSION=atspi_version[0]",
>          "ATSPI_MINOR_VERSION=$minor",
> -        "ATSPI_MICRO_VERSION=$micro",
> +        "ATSPI_MICRO_VERSION=$atspi_version[2]",
>        ]
>      }
>    }

Thanks for your hints. For the time being, the issue with 19 build is a patch for minizip I need to update and I am lacking time...

Hi Christia(a)n,

chromium-browser-stable-119.0.6045.159-1.mga9.tainted has landed in 9 tainted/updates

But it is still needed in cauldron tainted/release.

Could one of you find time to fix that?

(In reply to Marja Van Waes from comment #10)
> Hi Christia(a)n,
> 
> chromium-browser-stable-119.0.6045.159-1.mga9.tainted has landed in 9
> tainted/updates
> 
> But it is still needed in cauldron tainted/release.
> 
> Could one of you find time to fix that?

D...it...

I resubmit it...

Sorry....

me again.

Very weird, looking at http://pkgsubmit.mageia.org/?user=squidf
it has been submitted to tainted/release

and I see it here: https://mirrors.kernel.org/mageia/distrib/cauldron/SRPMS/tainted/release/

and tainted/updates is empty: https://mirrors.kernel.org/mageia/distrib/cauldron/SRPMS/tainted/updates/


@marja: where do you see it in tainted/updates ?

(In reply to christian barranco from comment #12)
> me again.
> 
> Very weird, looking at http://pkgsubmit.mageia.org/?user=squidf
> it has been submitted to tainted/release
> 
> and I see it here:
> https://mirrors.kernel.org/mageia/distrib/cauldron/SRPMS/tainted/release/
> 
> and tainted/updates is empty:
> https://mirrors.kernel.org/mageia/distrib/cauldron/SRPMS/tainted/updates/
> 
> 
> @marja: where do you see it in tainted/updates ?
Is in updates_testing https://mirrors.kernel.org/mageia/distrib/cauldron/SRPMS/tainted/updates_testing/chromium-browser-stable-118.0.5993.117-1.mga10.tainted.src.rpm

https://mirrors.kernel.org/mageia/distrib/cauldron/x86_64/media/tainted/updates_testing/

Hi
It is version 118 then, not the new 119. 
Admin support is required then. I take it.

(In reply to christian barranco from comment #12)
> me again.
> 
> Very weird, looking at http://pkgsubmit.mageia.org/?user=squidf
> it has been submitted to tainted/release

Yes, thanks, you did that some hours after I wrote comment 10 :-D


> 
> @marja: where do you see it in tainted/updates ?

That was and is in Mageia 9. I only complained because the version there was newer than in cauldron ;-)

Hi Marja 
Yes, Cauldron has been a bigger struggle than expected. Sorry for that.

(In reply to christian barranco from comment #16)
> Hi Marja 
> Yes, Cauldron has been a bigger struggle than expected. Sorry for that.

No problem. Thanks a lot for not having given up :-)

(You're not alone, btw, ghibo has tried several times without success to push kernel-6.5.11-2.mga10 to cauldron core/release, while pushing almost identical 6.5.11-1 to cauldron core/updates_testing was no problem).

solved by https://bugs.mageia.org/show_bug.cgi?id=32529

Resolution: (none) => FIXED
Status: NEW => RESOLVED