On abr. 27 2024, at 1:03 pm, Masaru Nomiya wrote:

Hello,

In the Message;

Subject : MozillaFirefox 125 Message-ID : Date & Time: Sat, 27 Apr 2024 11:32:32 +0200

[JLA] == Jose Luis Alarcon Sanchez via openSUSE Users has written:

JLAS> I'm pretty new using openSUSE Tumbleweed. I want to ask you if the JLAS> official firefox package is still on the version 124. I know i can use JLAS> the common tar.bz2 tarball uncompressed into /opt for use firefox 125, JLAS> but i always prefer use the official packages from the distro repos.

JLAS> My question: is gonna be soon packages for firefox 125?, maybe JLAS> Tumbleweed skip certain releases of the browser?. I don't know so i ask.

I think it will be 125 soon, but if you're in a hurry, you can add this to the repository and update it straight away;

https://download.opensuse.org/repositories/mozilla/openSUSE_Tumbleweed/

Best Regards & Good Night.

--- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Microsoft is overhauling its cybersecurity strategy, called the Secure Future Initiative, to incorporate key security features into its core set of technology platforms and cloud services. "

-- Microsoft overhauls cyber strategy to finally embrace security by default --

Thanks, Masaru. Very appreciated your reply. Regards. Jose.

* Knurpht-openSUSE [04-27-24 09:15]:

Op zaterdag 27 april 2024 13:03:02 CEST schreef Masaru Nomiya:

...

I think it will be 125 soon, but if you're in a hurry, you can add this to the repository and update it straight away;

https://download.opensuse.org/repositories/mozilla/openSUSE_Tumbleweed/ Don't even suggest that. The user is going to replace the tested version with an untested one. For reference go through the threads here and on the Support ML and see the mess people land in after using other than distribution repos.

a problem *only* for those not possessing the knowledge or forethought on recovering if difficulties present. this workstation is a 6 year old install with ~20 repos, many non-distro. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc

I understand your concern and in general you are very right. But, the user is able to use a tarball and the mozilla repository in general is no - not as others -  cause for additional trouble. On the other hand, the tested firefox is threatened by zero day exploits and as always very late from a security view. There is no good solution for that, but the possible trouble from using the tarball or mozilla repo for someone who was able to go for that is minutes to make it undone again. Btw, thank you for your great work, tumbleweed for sure is my favorite. Others are also good, but tumbleweed is outstanding. -------- Ursprüngliche Nachricht -------- Van: Knurpht-openSUSE Aan: users@lists.opensuse.org Onderwerp: Re: MozillaFirefox 125 Datum: 27.04.2024 16:00:17 Op zaterdag 27 april 2024 15:19:29 CEST schreef Patrick Shanahan:

a problem *only* for those not possessing the knowledge or forethought on recovering if difficulties present.  this workstation is a 6 year old install with ~20 repos, many non-distro.

That is a pretty useless comment. I assume that you read the OP and am wondering how a new user should have your knowledge. But my guess is that you felt the need to reply for some other reason.

On 2024-04-27 15:13, Knurpht-openSUSE wrote:

Op zaterdag 27 april 2024 13:03:02 CEST schreef Masaru Nomiya:

...

I think it will be 125 soon, but if you're in a hurry, you can add this to the repository and update it straight away;

https://download.opensuse.org/repositories/mozilla/openSUSE_Tumbleweed/ Don't even suggest that. The user is going to replace the tested version with an untested one. For reference go through the threads here and on the Support ML and see the mess people land in after using other than distribution repos.

The suggestion is perfectly valid - if the user is informed about the peculiarities and trade-offs. So let's not exclude anything here but work towards better suggestions. In any case simply waiting a bit seems to best fit the user's needs right now. Andreas

On 2024-04-27 17:56, Knurpht-openSUSE wrote:

Op zaterdag 27 april 2024 17:19:38 CEST schreef Andreas Stieger via openSUSE Users:

...

In any case simply waiting a bit seems to best fit the user's needs right now. That is by far the best one can do. Andreas, the reason why I'm warning and objecting is that on a daily basis I see at least 4-5 issues where these are caused by additional repos. The experience is that once users add one repo, more will follow because they see it as a valid option.

And you may can continue to do so. But in case this did not come across: I think we should stop short of suggesting we don't even mention alternatives. I believe in informing users fully, you know... open. This is a valid opinion to the fully informed users, a foot-gun for some - and that's just life. I think the zypper "orphaned packages" feature will help a bunch here. Andreas

Hello, In the Message; Subject : Re: MozillaFirefox 125 Message-ID : <26404590.1r3eYUQgxm@lenovo-p16> Date & Time: Sat, 27 Apr 2024 15:13:10 +0200 [K] == Knurpht-openSUSE has written: K> Op zaterdag 27 april 2024 13:03:02 CEST schreef Masaru Nomiya: K> > I think it will be 125 soon, but if you're in a hurry, you can add K> > this to the repository and update it straight away; K> > K> > https://download.opensuse.org/repositories/mozilla/openSUSE_Tumbleweed/ K> Don't even suggest that. The user is going to replace the tested version with K> an untested one. For reference go through the threads here and on the Support K> ML and see the mess people land in after using other than distribution repos. That's why I put the condition 'if you're in a hurry'. I ask you, on this occasion, why are you releasing a test version? You are right, there are many users other than Firefox who encounter problems using test versions (especially those related to KDE). However, I have never seen a comment telling people not to use test versions. Rather than not using them, it would be better not to release them. Best Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Microsoft is overhauling its cybersecurity strategy, called the Secure Future Initiative, to incorporate key security features into its core set of technology platforms and cloud services. " -- Microsoft overhauls cyber strategy to finally embrace security by default --

Op zondag 28 april 2024 03:35:57 CEST schreef Masaru Nomiya:

Rather than not using them, it would be better not to release them. That is where you have a point, testers are needed, So not releasing those is not an option.

-- Gertjan Lettink a.k.a. Knurpht openSUSE Forums Team openSUSE Mods Team

Hi, Am 28.04.24 um 03:35 schrieb Masaru Nomiya:

[K] == Knurpht-openSUSE has written:

K> Op zaterdag 27 april 2024 13:03:02 CEST schreef Masaru Nomiya: K> > I think it will be 125 soon, but if you're in a hurry, you can add K> > this to the repository and update it straight away; K> > K> > https://download.opensuse.org/repositories/mozilla/openSUSE_Tumbleweed/ K> Don't even suggest that. The user is going to replace the tested version with K> an untested one. For reference go through the threads here and on the Support K> ML and see the mess people land in after using other than distribution repos.

That's why I put the condition 'if you're in a hurry'.

I ask you, on this occasion, why are you releasing a test version?

You are right, there are many users other than Firefox who encounter problems using test versions (especially those related to KDE). However, I have never seen a comment telling people not to use test versions.

Rather than not using them, it would be better not to release them.

to be a bit more specific: In the "mozilla" repository are no test versions! For test versions there would be the :beta, and :experimental subprojects which are not really used currently. mozilla contains in 99,99% of the cases fully released upstream software which is a few days later submitted - as is - to Tumbleweed. Can there be issues still? - YES Either caused by Mozilla releasing something broken. Just look at 125.0 and 125.0.1 or because an existing patch is not fully compatible anymore. In that case there is even a VERY good chance that it ends up in Tumbleweed exactly the same way because it's not discovered immediately and the time from upstream to TW release should be as short as possible. Please note that there was one incident just a few weeks ago where a submission to the NSS component was killing addon signatures. And because the submission looked sane and came from @suse it was already in the Tumbleweed queue. So I think it was more or less pure luck that it didn't get through. But on the other hand that is why it has value if some people use the repo because otherwise almost every issue would directly hit through to TW. Wolfgang