You miss the point of the message.
You cannot validate an Alpha or Beta release when most of what you run need parts from Packman.
No movie edits to validate that things work - could not use vlc to view videos. Firefox could not show many videos as they needed Packman codex to play.
All I could do is validate the update worked and my files were there.
Again, this is an issue to take up with the Packman Maintainers, whether they choose to build for Alphas, Betas, or Release Candidates. That it doesnât fit into your process and needs is not particularly relevant, not everybody needs or wants Packman enabled on their systems.
sorry, but firefox version on leap 15.6 and 16 is 140.03, not 128
@larryr:
I needed to update firefox to a more recent version in an older Leap 15.4 installation, and a working solution was surprisingly simple then. It boiled down to clicking âDownload for Linux 64-Bitâ on the mozilla download site, copying the .tar.xz to /opt, extracting and renaming it to, say, /opt/firefox-1xx.0/ and creating a soft link from /opt/firefox-1xx.0/firefox to /usr/local/bin. Since /usr/local/bin occurs before /usr/bin in $PATH, firefox 1xx is just firefox &, systemâs firefox is /usr/bin/firefox &
This worked flawlessly out of the box in my computer, but OS was 15.4, not 16.0 or something else, and I canât say anything about otherâs computers/installations.
That is the versions of Firefox that force me to go to the Mozilla repo for the newest version. That is when Banks started validating the version in use.
My leap is at 144.0 not 140.03. It is from the mozilla repo at this location
http://download.opensuse.org/repositories/mozilla/openSUSE_Leap_$releasever
That is a âYouâ not an âopenSUSEâ issue. If you need stuff from Packman, then you need to wait for Packman to become available before considering an upgrade.
As Shawn pointed out, the openSUSE project does not control Packman. You need to take issues with Packman up with the Packman maintainers.
The project has no control over third party repositories. Period.
Nobody forced anyone to upgrade to Leap 16.0 on day one. 15.6 is supported until at least April 2026 according to Lifetime - openSUSE Wiki.
If you have a critical need that isnât met with the upgrade because third party repos arenât available, itâs simple: Wait until those repos are available to do your upgrade.
Complaining about it here (where there are few developers) or with the openSUSE Project (when the issue is repos the project does not control) is not going to get your issues resolved.
Thanks for this chat here. It tells me, that i better wait till January before i upgrade my only PC to Leap 16. 
I read between the lines, that upgrading an existing installation has higher risks of failure (I experienced such already when moving to Leap 15.6 where the user homes required a format). But Leap 15.6 Gnome turned out to be the most stable and easy to use OS i ever had - me veeery happy with Leap 15.6. 
Therefore, i shall wipe out my current installation in January and run a new install via USB. 
Only question from my end: Do i need Agama when doing a fresh install via USB?
Yes, the only installer for the Leap-16 ISO is agama.
Thanks, sfalken.
Is Flatpak automatically active on installation of Leap 16 or do i need to configure what?
(I am keen to remove SuSE Mozilla after install and have all instead as a user specific Flatpack - kinda restricted setup.)
No clue. Itâs easy enough to enable, if it isnât
Ummm. Leap 16.0 is not what many users have had expectations onâŚ
-Agama, -maybe fit new users
-Myrlin⌠To add a local repo (fixed)
-Cockpit adm, This have to be joke or? One can add some plugins in Myrlin.
Attach a screenshot of one of my simple test-setups. Webmin. Will do some more test. I will wait and stay on Leap15.6 for my Desktop daily driver. A showstopper is the lack of VirtualBox.
Regards
Totally true. And totally missing the point, I thinkâŚ
While OpenSUSE doesnât control Packman, I donât remember a case, when Packman repositories wouldnât be ready at the release date. As it is now, Packman is quite the âessentialâ to OpenSUSE, whether you like it or not. Ignoring the fact is torpedoing the trust of the users and many will jump the ship, when things go sideways, like with the Leap 16.
IMHO, the best the OpenSUSE team could do is to downgrade the release back to alpha/beta/nextgentest or whatever and take as much time as it takes to deliver true âLeapâ quality distro.
If users do not understand the non existing connection between a third party repo and a officially maintained distribution, well, let them go. They will have the same understanding issues with any other distribution out there.
Thank you @dcurtisfra, that is very interesting report.
I do have only 1 âLeap 16â repository to start with on that updated PC and I did use âopensuse-migration-toolâ.
When Iâm in better shape (being sick right now), Iâll follow your advises (about cache and so on). But I did try to create a completely new user and it still didnât work. Iâm ready for some Plasma 6 glitches, thatâs expected with the new technology.
Do you count the maintenance updates channel (including security updates you are so eager to attack others about) as a third party repo? Because Leap 16.0 still lacks them without any ETA.
And to prevent knee jerk reaction - I do not mean update repository. I mean the workflow to submit and publish updates for Leap 16.0 in any repository.
@hui The point is, that Packman not being ready is probably connected to Leap 16 not being ready.
OpenSUSE Leap series was quite friendly to users, that was an important âsellingâ point. This distro doesnât have a significant market share anyway and it simply canât afford loosing users by providing a buggy product that needs to be riddled with hacks. It can quickly spiral out of control.
@oakld believe it or notâŚnothing to do with the release of Leap 16.0 
https://lists.links2linux.de/pipermail/packman/2025-October/018164.html
Anyway, my usual test for Folks is to try openSUSE without Packman and test what doesnât work/work for them and identify the actual codec(s) involvedâŚ
Likewise those with old broadcom devices and AMD hardware (commiserations to those users) likely needâŚ
Is http://cdn.opensuse.org/update/openSUSE-stable/repo/oss/ as appears may be just a mirror of http://cdn.opensuse.org/distribution/leap/16.0/repo/oss/? http://cdn.opensuse.org/update/leap/ does indeed lack 16.0 currently.
There wonât be any dedicated update repo for Leap 16 as described in the release notes and system upgrade SDB. Updates will go directly into the base oss/non-oss repo.
The issue arvidjar is refering to is following:
https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/JWCJEAPARKWKCBVLLV7U5RI6O2G2ZQSE/
The build infrastructure/process is not finished yet for releasing updates.
Which release notes? Using string âupdateâ as a search term for find in page on https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/16.0/html/release-notes-leap-160/ I failed to locate any such mention, and same with search term ârepoâ. 
