Transactional update,is reboot forced and how to feed arguments to zypper

English Install/Boot/Login
1

I am willing to try transactional update. But before doing that, I have couple off concers which I have searched for without success so I decited to post. Is reboot to a updated snapshot automatic? And how to pass arguments to underlying zypper? Only way so far pass arguments I have figured out is copy transactional-update script, edit copy, and run that copy. I am in need to pass --allow-vendor-change to zypper

2

It does if you configure it that way

https://kubic.opensuse.org/documentation/man-pages/transactional-update.conf.5.html

https://kubic.opensuse.org/documentation/man-pages/transactional-update.index.html

3

You can put a small file in “/etc/zypp/zypp.conf.d”

 --- 01vendor.conf ---
solver.dupAllowVendorChange = true

to solve that problem.

4

My 2 cents: Don’t use 3rd party repos with transactonal-update, it is not supported, and especially do not use --allow-vendor-change.
If you insist on this experiment, I would suggest you download the latest Kapla-Desktop iso from kalpadesktop.org, create a VM with that and you would have a good example of how it is done in there ( i.e. the MicroOS way ).

5

Thans hui. Now I begin to see

6

Thanks Gertjan, I am somewhat on my own here

7

Thanks Neil, I’ll try this

8

Can you show your repos, please Julia? Show zypper lr -d.
Also, which DE are you using?

9

I use KDE. Here are my repos:

zypper ls -d

| Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI

–±---------------------------------±---------------------------±--------±----------±--------±---------±-------±---------------------------------------------------------------------------------
1 | buildFactory | buildFactory | No | ---- | ---- | 100 | N/A | https://download.opensuse.org/repositories/build.opensuse.org/openSUSE_Tumbleweed
2 | download.opensuse.org-non-oss | Main Repository (NON-OSS) | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/tumbleweed/repo/non-oss/
3 | download.opensuse.org-oss | Main Repository (OSS) | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/tumbleweed/repo/oss/
4 | download.opensuse.org-tumbleweed | Main Update Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/tumbleweed/
5 | graphics | graphics | Yes | (r ) Yes | Yes | 99 | rpm-md | https://download.opensuse.org/repositories/graphics/openSUSE_Tumbleweed/
6 | packman | packman | Yes | (r ) Yes | Yes | 90 | rpm-md | https://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tumbleweed/
7 | repo-debug | openSUSE-Tumbleweed-Debug | No | ---- | ---- | 99 | N/A | http://download.opensuse.org/debug/tumbleweed/repo/oss/
8 | repo-source | openSUSE-Tumbleweed-Source | No | ---- | ---- | 99 | N/A | http://download.opensuse.org/source/tumbleweed/repo/oss/

The repo situation now is slightly different than when I started this thead. F.ex. buildFactory did not exist then.

10

I insist to stick on this experiment. How should I set up my repositories to block OBS vendor changes?

11

You should not have that one.

12

By default they already are blocked, but the vendor change is not the thing to worry about. In your case the slightest inconsistency in Packman will cause conflicts in f.e. Mesa. Accepting any vendor change will solve the conflicts problem, but will make you switch back and forth between oss and Packman, IMHO an undesirable effect.
You can set allow-vendor-change in /etc/zypp/zypp.conf by changing
# solver.allowVendorChange = false
to
# solver.allowVendorChange = true
but, like said that will have it’s own issue.

FWIW, I have been doing without Packman fine, only have oss, non-oss, update and openh264. For all things needing more codecs I use flatpaks.

13

openh264, wov! Did you installed openh264 natively or is it from flatpack?

14

Mesa should only be needed for older AMD GPU’s and codec support


Likewise, transactional-update on Tumbleweed is not supported, so if/when it all goes pear shaped, your on your own for fixing


15

It is a stock thing, when you have opensuse-repos-tumbleweed installed. Also it was announced on all our public media

16

Thanks Gertjan. I am sure I figure this out now.

17

Thank you, Malcolm. If you meant I am my own here, that was something I already knew. But in that, should I keep myself disclosing my findings because for sure there will be many after me to whom my findings surely cause headache and confusion since surely my way to use zypper and repos is not the most correct ones? I know this is wrong place for this kind of discussion but my innocent hope is somebody after me takes a note these words and begins to think ‘I can severely hurt my system’.

18

Yes, for sure keep posting, but likely suggestions may/may not be of help as a lot of second guessing.

Likewise, you don’t necessarily have to reboot, transactional-update apply may be sufficient depending on what is installed, checking with zypper ps -s to see what is has been deleted, or services that just need restarting


19

I for one am curious about your expeiences, Julia, and do hope you share the results here

20

I think I am quite experienced since I have done software development from 1993, have been using linux as a only option at my home computer from 1998 (slackWare, later moved to redhat, then fedora). I switced from fedora to tumbleweed recently thus I am quite rookie about zypper. I wanted properly working rolling distro, that’s why Tumbleweed