Hi, using openSUSE Tumbleweed, after installing packman-essentials and passing # sudo zypper dup --from packman --allow-vendor-change can this normally be left (the vendor change) alone for a long periods of time? Normally just facilitating the use of zypper refand zypper dup to keep the machines upgrades current?
-Thanks
When you have the Packman Essential repo as an enabled repo in your repo list and did the vendor switch to it (that is what I understand from your description), then at zypper dup it will be used to update those packages that you have from it and it will not change back to the same packages from the standard repo (that is called Vendor stickiness).
In short the answer is : yes.
@hcvv Thank you for your response. Sometimes I have read that, (and possibly even experienced) that Packman can fall behind and zypper will not ‘dup’ without ‘solver solutions’ … What practice do you recommend when this occurs?
Simply just wait?.. I prefer not to apply vendor changes back and forth when things like this arise.
-Thanks
One installs from Packman to have additional features (e.g. codecs with restricted formats), not to “just have the last version”. One normally needs consistent packages installed, say a consistent set (say, Mesa) from Packman or from OSS.
Always changing to “the last version” is looking for trouble since OSS and packman are not in sync very often, since Packman builds from Factory but packages appear on OSS only after the OpenQA tests have cleared.
So the correct way is “choose whatever vendor suits you and stick with it” and that is what zypper normally does.
Occasionally you will be asked to “switch back”, e.g. when a codec patent expires and Packman choose to not build that package anymore so that the OSS version remains the only choice in town.
That is very vague. Just wait until such a thing happens and then either use your brains or ask in the forum (or both).
How can one ‘heal’ an ill Packman and OSS mismatch the best way? Passing zypper ref and then zypper dup and then # zypper dup --from packman --allow-vendor-change would be the preferred way? I was recently told that Packman and OSS are mismatched and to choose one or the other for Mesa so I # zypper dup --from packman --allow-vendor-change but I do not believe this may have been a correct solution?
There is a vendor switch to Packman for only Mesa what is this command or where best to look it up?
-Thanks
There is no “standard” way to solve problems that may arise. It depends on the situation. As said above, when problems arrive, read the errors, try to interpret them (that is what I called: use your brains), but do not just do something that was found on the internet (or even on these forums) for a problem ages ago. When this is really a problem that hurts everybody, you will find already a fresh topic about it on these forums (apart when you are an early riser and the first doing the update). And when you are not 100% sure what to do: ask here!
That was only an example. And again when such a thing happens, there will be plenty of information around. In the mailing list and here on the forums.
I will review this again and understand more.
As I wrote above, if there is a bug and a fixed version appears, that fixed version will appear on Packman a few hours or a day before that same version appears on OSS, depending on how much time it takes to clear the OpenQA testing. So in such cases either wait a few hours or switch to Packman (and then possibly switch back to OSS).
To switch only one package or a set the command is something like:
zypper install --from packman --force --allow-downgrade <list of packages to be switched>
Please note that just putting “Mesa” in the list will change only Mesa and not the 8-9 Mesa-xxx packages you need, and using “Mesa*” will install some 109 packages most of which are not needed. So, as @hcvv wrote, ask here if you are unsure.
The same task is easier with YaST2-software by using the “Version” tab.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.