On 25.09.2021 01:50, Bernhard Voelker wrote:
On 9/24/21 19:47, George from the tribe wrote:
Can someone tell me if this is a bad idea and why -
I want to do regular updates, like security updates to google chrome and things like that, for all my programs and apps that are managed by non-openSUSE repositories.
Then do regular zypper dup updates for the whole system only like once a month. That way I minimize my chances of something breaking right before a critical business trip or something like that, but still keep my security up to date.
Any thoughts?
With a mix of official openSUSE repos and other repos in Tumbleweed, the biggest problem is that the packages may change vendor between those repos without notice,
This should not happen unless you explicitly changed default configuration or are using additional options during "zypper dup" that allow vendor change without asking you first. By default zypper should ask you when resolution requires vendor change (or is not possible without vendor change). If user changed default configuration or is using extra option user is expected to understand implications. More important practical consideration is that third party repositories may lag behind Tumbleweed regarding necessary rebuilds and you do not really have any indication that packages were rebuilt to match Tumbleweed. It is more or less trial and error. From following forums I would say these are not isolated cases.
and the risk is that this could break the basic packages from TW at lesat. I'd suggest to prevent changing the vendor for packages with: $ zypper -v dup --no-allow-vendor-change
Additionally, you could reduce the risk of mixing by updating only from the oS:TW repos.
Have a nice day, Berny