Well, the fix has been accepted to the devel repo 4 hours ago and forwarded to Factory.
You can track the progress of the submission to Factory here: https://build.opensuse.org/request/show/353732
Once this is accepted, it will be in the next Tumbleweed snapshot afterwards.
That’s irrelevant if it is pushed to the additional update repo. openqa only tests the “normal” distribution, the purpose of the update repo is to be able to circumvent this process in emergencies.
That’s irrelevant if it is pushed to the additional update repo. openqa only tests the “normal” distribution, the purpose of the update repo is to be able to circumvent this process in emergencies.
Ah. I didn’t know that as all Tumbleweek FAQs I’ve seen so far indicate you should update using zypper dup, not zypper up.
What’s the URL of the additional update repo to use with Tumbleweed?
It’s irrelevant in this case whether you use “zypper up” or “zypper dup”.
Both will install all updates in your configured repos. The main difference is just that “zypper up” will not switch packages to versions from other repos/vendors (there are other differences of course, but I don’t want to go into that now, a link to a discussion can be found on the Tumbleweed Portal).
The update repo has the same vendor as the main repo though (openSUSE), so “zypper up” will install updates from there as well.
“zypper patch” will only install patches from the update repo, and is normally useless on Tumbleweed.
What’s the URL of the additional update repo to use with Tumbleweed?