Install or not?

When I try to this update, I get the nothing to do.

localhost:~ # zypper up
Refreshing service ‘openSUSE’.
Loading repository data…
Reading installed packages…
The following 8 package updates will NOT be installed:
gstreamer-plugins-bad gstreamer-plugins-bad-lang libvlc5 libvlccore9 vlc vlc-codec-gstreamer vlc-noX vlc-qt
Nothing to do.

But That Discover app brings them up every day.
And If I look in myrlyn they are on the needed patches.

So far I have been ignoring it because there are the error choices to select from.
Can I some how stop the system from trying to get me to install them every day?

@Bill_L did you run zypper patch instead?

1 Like

No,but I will.
If I start getting the choice ‘what to do’ choice selections I’ll just try to back out again.
I don’t have packman, so that isn’t the cause.

this is ‘zypper patch’ output. I Canceled the operation. Didn’t like the information and the ‘error’ & choices.

localhost:~ # zypper patch
Refreshing service ‘openSUSE’.
Loading repository data…
Reading installed packages…
Resolving package dependencies…
2 Problems:
Problem: 1: the to be installed gstreamer-plugins-bad-lang-1.26.7-160000.1.1.noarch requires ‘gstreamer-plugins-bad = 1.26.7’, but this requirement cannot be provided
not installable providers: gstreamer-plugins-bad-1.26.7-160000.1.1.x86_64[openSUSE:repo-oss]

Problem: 2: the installed phonon-vlc-qt6-0.12.0-bp160.1.17.x86_64 requires ‘vlc-noX = 3.0.21’, but this requirement cannot be provided

Problem: 1: the to be installed gstreamer-plugins-bad-lang-1.26.7-160000.1.1.noarch requires ‘gstreamer-plugins-bad = 1.26.7’, but this requirement cannot be provided
not installable providers: gstreamer-plugins-bad-1.26.7-160000.1.1.x86_64[openSUSE:repo-oss]

Solution 1: install gstreamer-plugins-bad-1.26.7-160000.1.1.x86_64 from vendor SUSE LLC https://www.suse.com/
replacing gstreamer-plugin-openh264-1.24.12-1.sle150600.2.x86_64 from vendor obs://build.opensuse.org/openSUSE:Factory
Solution 2: do not install patch:openSUSE-Leap-16.0-362-1.noarch
Solution 3: break gstreamer-plugins-bad-lang-1.26.7-160000.1.1.noarch by ignoring some of its dependencies

Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c/d/?] (c):

@Bill_L Do you need the language packages installed?

If not, this is a code snippet I use…

if [ $REMOVE_LANG == 1 ]; then
echo "Removing language files and locking"
rpm -qa *-lang --qf "%{name}\n" | xargs zypper --non-interactive rm -u
zypper al *-lang
fi
1 Like

There is a mix of Leap 15.6 and Leap 16.0 packages, a failed upgrade attempt?
Bring the system in a consistent state (either 15.6 or 16.0) then try again.

1 Like

No, don’t need them. I’ll try that script next time on my PC.

If I knew how to get things right I would, but I don’t.
I am not a power user.

Possibly you have leftover repos? Please post zypper lr -d
Since this thread is tagged “Leap 15.6” but you get updates for Leap 16.0, which one do you intend to run?

1 Like

My bad, i mistakenly selected 15.6 in the tag, I am on 16.0
Here are the repos if meaningful.
localhost:~ # zypper lr -d

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

–±----------------------------±--------------------------±--------±----------±--------±-----±---------±-------±-------------------------------------------------------------------------±--------
1 | SoftMaker | SoftMaker | Yes | (r ) Yes | Yes | - | 99 | rpm-md | https://shop.softmaker.com/repo/rpm |
2 | brave-browser | Brave Browser | Yes | (r ) Yes | Yes | - | 99 | rpm-md | https://brave-browser-rpm-release.s3.brave.com/x86_64 |
3 | google-chrome | google-chrome | Yes | (r ) Yes | Yes | - | 99 | rpm-md | https://dl.google.com/linux/chrome/rpm/stable/x86_64 |
4 | openSUSE:repo-non-oss | repo-non-oss (16.0) | No | ---- | ---- | - | 99 | N/A | http://cdn.opensuse.org/distribution/leap/16.0/repo/non-oss/x86_64 | openSUSE
5 | openSUSE:repo-non-oss-debug | repo-non-oss-debug (16.0) | No | ---- | ---- | - | 99 | N/A | http://cdn.opensuse.org/debug/distribution/leap/16.0/repo/non-oss/x86_64 | openSUSE
6 | openSUSE:repo-openh264 | repo-openh264 (16.0) | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://codecs.opensuse.org/openh264/openSUSE_Leap_16 | openSUSE
7 | openSUSE:repo-oss | repo-oss (16.0) | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://cdn.opensuse.org/distribution/leap/16.0/repo/oss/x86_64 | openSUSE
8 | openSUSE:repo-oss-debug | repo-oss-debug (16.0) | No | ---- | ---- | - | 99 | N/A | http://cdn.opensuse.org/debug/distribution/leap/16.0/repo/oss/x86_64 | openSUSE
9 | openSUSE:repo-oss-source | repo-oss-source (16.0) | No | ---- | ---- | - | 99 | N/A | http://cdn.opensuse.org/source/distribution/leap/16.0/repo/oss | openSUSE

sorry for the mess I made of the repos, never know which format thingy to pick.

‘zypper up’ today resolved most of the things I was concerned about. I did use myrlyn to finish the patches.

What I do not understand is why ‘zypper’ wanted to NOT install them, when the DIscover updater & myrlyn patch wanted to!

Thanks for the help!

Your repo list from repo #4 to repo #9 looks OK, it is consistent with a default Leap 16.0 install. Repos #1, #2 and #3 are third party repos I cannot comment about, you may have installed something from those repos or not, so it is up to you; but they don’t seem related to the problem described here.

The problem with zypper is (was?) caused by the gstreamer-plugin-openh264-1.24.12-1.sle150600.2.x86_64 package, likely a leftover from a previous Leap 15.6 install, which prevented other conflicting packages from being installed.
I would use Myrlyn to check if it is still installed and if so I would uninstall it.

1 Like

Repos 1,2,3 are browsers & a smaller office suite than what is distributed.

As far as the other things, those only started happening a few days ago, and I have been 16.0 for quite a while now. So IMO , I don’t think it was due to leftovers.

I will check the gstreamer bit but I believe the myrlyn patch yesterday resolved that as well.

Thanks for your responses & help.

Possibly the leftover was quietly sitting there and the update to gstreamer-1.26.7 on March 5 exposed the conflict; but that update likely fixed also a long standing problem with vlc and other players that were unable to play h264 videos.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.