Re: This is interesting.

On 7/3/26 8:46 AM, Felix Miata wrote:
> Same problem using update instead of patch?

Sorry for the delay, went out of town.

The command is:
sudo zypper patch --allow-vendor-change --auto-agree-with-licenses -y

And 2 of 3 produced all that verbiage.

For 15.6:

sudo zypper clean
sudo zypper refresh

then

sudo zypper patch --allow-vendor-change --auto-agree-with-licenses -y

Has produced this for several weeks:

All repositories have been cleaned up.
Repository 'update-backports (15.6)' is up to date.
Repository 'update-non-oss (15.6)' is up to date.
Repository 'update-oss (15.6)' is up to date.
Repository 'update-sle (15.6)' is up to date.
Repository 'Update repository of openSUSE Backports' is up to date.
Repository 'Update repository with updates from SUSE Linux Enterprise 15' is up 
to date.
Repository 'repo-non-free (15.6)' is up to date.
Repository 'repo-non-oss (15.6)' is up to date.
Repository 'repo-openh264 (15.6)' is up to date.
Repository 'repo-oss (15.6)' is up to date.
All repositories have been refreshed.
Refreshing service 'NVIDIA'.
Refreshing service 'openSUSE'.
Loading repository data...
Warning: Repository 'update-oss (15.6)' metadata expired since 2026-06-17 
02:34:19 AKDT.

    Warning: Repository metadata expired: Check if 'autorefresh' is turned on 
(zypper lr), otherwise
    manually refresh the repository (zypper ref). If this does not solve the 
issue, it could be that
    you are using a broken mirror or the server has actually discontinued to 
support the repository.

For 15.6 I'm still using whatever was in effect when I did the upgrade back in 
prehistory.


To answer your question, I just tried it with a "sudo zypper up" and it ran 
fine. So, now I need to decide which to use...my bash scripts are replicated 
across to all the computers (no matter the release) every couple of hours. 
Personally I'm leaning towards the "update" right at the moment.