DUP Issue TW - nothing provides 'this-is-only-for-build-envs'

Did you just do a zypper dup or did you do zypper dup --allow-vendor-change? Without the flag zypper is going to keep using the packman packages even if the repository is disabled.


If you only have packman installed for codecs and are averse to using flatpaks, switching to the VLC repository might be an option for you. The VLC maintainers seem to be a bit more thoughtful about their update schedule, at least:

  1. Disable packman repo:
    sudo zypper mr -d packman-essentials (or whatever version you have)
  2. Refresh and revert back to openSUSE packages:
    sudo zypper ref and sudo zypper dup --allow-vendor-change
  3. Check for any packman packages left behind:
    sudo zypper pa -i packman-essentials --plus-content packman-essentials (again, replace with actual name of your packman repo)
    If there are any, sudo zypper rm them, in my case a libx265 package was hanging around.
  4. Add the official VLC repo:
    sudo zypper ar -cfp 90 -n VLC http://download.videolan.org/pub/vlc/SuSE/Tumbleweed/ vlc
  5. Refresh and update to VLC packages:
    sudo zypper ref and sudo zypper dup --allow-vendor-change.

This should get you H.265/AAC support in most software (not just VLC). The only thing you might miss from packman is libmesa drivers for hardware accelerated encoding/decoding but for most users that shouldn’t be much of an issue. Modern CPUs are more than capable.

You might need to manually install libx265-188 from VLC repo to get H.265 working.

9 Likes

Thank you for the detailed reply . . . I think I did go through the process of looking at “VLC” in my Leap 16 install . . . and, yes, wanted to skip the flatpak direction, for “simplicity” . . . .

But, in answer to your question, I was rushing, so I didn’t run “allow-vendor-change” . . . I did assume it “didn’t work” because of operator error, but didn’t know the exact error.

In my Leap 16 I think all I wound up doing was adding some “h.265-firefox”??? package that gave me video snippets in social media sites . . . very simple solution . . . . Largely I am OK with packman, but since I had to figure a way around it in Leap 16, as packman was lagging on being ready for Leap 16 . . . I found that I didn’t need it.

So perhaps if I get a moment, moving away from packman and back to “open suse” and finding the thread where I discussed that Firefox codec?? that provided the capacity . . . might be worth doing, as a time saver.

I’m not sure about any Firefox-specific h.265 codec. Certainly not an official one. If I were just looking for h.265 support in a single application, I would go the flatpak route for the sake of simplicity.

Also, I should apologize. I missed that you are using Leap 16. Just in case you do try the VLC repo, make sure to use the Leap 16 version in section 4: sudo zypper ar -cfp 90 -n VLC https://download.videolan.org/pub/vlc/SuSE/16.0/ vlc

Guess you refer to mozilla-openh264 that was needed on Leap 16.0 until recently.
That is not needed on Tumbleweed as long as you have libopenh264-8 and ffmpeg-8 installed.
But that is no h265 (for HEVC videos), which is still patent encumbered and so is only available via Packman or Videolan.

No worries . . . for this thread I am having the problem in TW, but was referring to Leap in terms of “not using packman” . . . whereas in TW, I am.

Hm . . . OK . . . so I guess that means I won’t be able to do that same “one package to show videos” move that I made in Leap . . . ??? Back to the waiting for packman to catch up???

Please make sure that you need h265: it is uncommon for “social media snippets”, it is mainly used by broadcasters (or commercial web video servers) to transmit e.g. 4K videos over limited bandwidth…

1 Like

Alrighty . . . looking back through my posts the nearest I could find was:

non_spaceParent Penguin

Sep 2025

@malcolmlewis

OK, thanks for the follow up . . . ran that command, but don’t know what it is telling me . . . ??? There was the “openh” stuff a bit back where I needed “mozilla-openhxxx” to get videos playing . . . without Packman. Haven’t yet tried to add Packman, as perhaps I don’t need it . . . but, what is “system packages” telling me in this instance?

Downgraded kernel seems to be in roper order . . . .

> sudo zypper se -is |grep "(System Packages)"
[sudo] password for root: 
i+ | kernel-default                             | package | 6.12.0-160000.20.2                          | x86_64 | (System Packages)
i+ | kernel-default                             | package | 6.12.0-160000.19.1                          | x86_64 | (System Packages)
i  | kernel-default-extra                       | package | 6.12.0-160000.20.2                          | x86_64 | (System Packages)
i  | kernel-default-extra                       | package | 6.12.0-160000.19.1                          | x86_64 | (System Packages)
i  | kernel-default-optional                    | package | 6.12.0-160000.20.2                          | x86_64 | (System Packages)
i  | kernel-default-optional                    | package | 6.12.0-160000.19.1                          | x86_64 | (System Packages)
i  | libhd24                                    | package | 24.0-160000.2.3                             | x86_64 | (System Packages)
i  | libopenh264-7                              | package | 2.3.1-2.suse1600.1                          | x86_64 | (System Packages)
i  | librav1e0_7                                | package | 0.7.1-160000.1.11                           | x86_64 | (System Packages)


From thread https://forums.opensuse.org/t/zypper-finds-two-file-conflicts-w-usr-lib64-xxx-in-leap-16/187832/16

But I couldn’t find the thread where I was working through the VLC and or other ways to get video in Leap 16 Beta . . . .

Likely this one: leap-16-asks-me-to-make-a-choice-from-ffmpeg-6-in-lieu-of-packman
where you mention mozilla-openh264 and no reference to h265 (as I guessed).

BTW found with the Forum search with “advanced options”

1 Like

Yes, I was just looking at that thread . . . and there were a few from around then . . . but, so the question to this thread is can TW use that “mozilla-openh264” package with some “opi” package to replace Packman for this current round of problems?? Or, you are saying that we can’t do that for TW??

Now that we are sure that the videos at stake are h264 (“normal mp4” so to speak) and not h265 (HEVC videos ) the answer for Tumbleweed is:

  • firefox needs libopenh264-8
  • and ffmpeg-8 or gstreamer-1.28 and later
  • or mozilla-openh264

all of those available from the standard repos, no need for Packman, Videolan, opi, whatever…

2 Likes

Thanks for your instructions on allowing vendor change etc. This enabled me to disable Packman Repos as I was mostly - I think using them for codecs etc. Then to get videos working in Firefox I needed to install the VLC Repo as you suggested & this seemed to do the trick & all seem good now so far. Thanks.

@OrsoBruno

Just got done with my interpretation of the data here . . . i.e., “changing vendor” from Packman to opensuse, after checking the suggested packages. My TW system already had the Repository 'Open H.264 Codec (openSUSE Tumbleweed)' installed. in YaSt it showed that “libopenh264-8” was installed, but checking “ffmpeg-8” just showed the “thisis-only-for-build-envs” error in YaSt, and the “gstreamer-1.28” showed “no results,” just running “gstreamer” showed a bunch of packages, so I cancelled out and checked “mozilla-openh264” and it showed as installed.

Closed out of YaSt and opened console and ran “ref && dup --allow-vendor-change” (sudo zypper +) and that showed the 31 some erstwhile packages holding up the works changing from packman to opensuse . . . and it ran through clean.

Did not add VLC or opi, etc . . . and checking in the twitter shows “moving pictures” seemingly in good order. Simple is good.

Quick update, had some updates offered & did a DUP & had the same 7 issues again. So disabled the VLC repo & switched all those over to Opensuse which meant a few downgrades to some of the codecs. The issues went away again & the DUP completed again. Hopefully that will be the end of it now. Browser videos & VLC seem to play OK with this set up.

delete this

I don’t have the VLC repo and am still suffering from this issue, so I do think it’s all about packman

1 Like

I think it is something to do with this maybe wherever it might come from if you have it installed perhaps

Blockquote[quote=“non_space, post:32, topic:192672”]
but checking “ffmpeg-8” just showed the “thisis-only-for-build-envs” error in YaSt
[/quote]
Checking my system I don’t have that but I do have ffmpeg-4. Hope this helps maybe?

I don’t get it, you’re saying I should see whether I have this installed and remove it if I do?

For the records ffmpeg-8.1 has just made it to the repos with snapshot 20260324, so please zypper dup and try again.

1 Like

Doesn’t help here. Packman still wants to install ffmpeg-8-mini-libs. Locking the package doesn’t help either.

Reading installed packages...
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
Computing distribution upgrade...
14 Problems:
Problem: 1: the installed x264-20250608.b35605ac-1699.1.pm.4.x86_64 requires 'libavcodec.so.62(LIBAVCODEC_62.11_SUSE)(64bit)', but this requirement cannot be provided
deleted providers: libavcodec62-8.0.1-3.2.x86_64
                   libavcodec62-8.0-1699.3.pm.9.x86_64

Problem: 2: cannot install both libavdevice62-8.1-1699.2.pm.1.x86_64 and libavdevice62-8.1-1.1.x86_64
Problem: 3: cannot install both libavfilter11-8.1-1699.2.pm.1.x86_64 and libavfilter11-8.1-1.1.x86_64
Problem: 4: the installed vlc-3.0.23-1699.9.pm.1.x86_64 requires 'libavformat.so.62(LIBAVFORMAT_62.3_SUSE)(64bit)', but this requirement cannot be provided
deleted providers: libavformat62-8.0.1-3.2.x86_64
                   libavformat62-8.0-1699.3.pm.9.x86_64

Problem: 5: the installed vlc-noX-3.0.23-1699.9.pm.1.x86_64 requires 'libavutil.so.60(LIBAVUTIL_60.8_SUSE)(64bit)', but this requirement cannot be provided
deleted providers: libavutil60-8.0.1-3.2.x86_64
                   libavutil60-8.0-1699.3.pm.9.x86_64

Problem: 6: cannot install both libswresample6-8.1-1699.2.pm.1.x86_64 and libswresample6-8.1-1.1.x86_64
Problem: 7: cannot install both libswscale9-8.1-1699.2.pm.1.x86_64 and libswscale9-8.1-1.1.x86_64
Problem: 8: the installed python313-libxml2-2.14.5-4.2.x86_64 requires 'libxml2-16 = 2.14.5', but this requirement cannot be provided
deleted providers: libxml2-16-2.14.5-4.1.x86_64

Problem: 9: the to be installed ffmpeg-8-8.1-1699.2.pm.1.x86_64 requires '(libavutil60 = 8.1-1699.2.pm.1 or ffmpeg-8-mini-libs = 8.1-1699.2.pm.1)', but this requirement cannot be provided
not installable providers: libavutil60-8.1-1699.2.pm.1.x86_64[packman]

Problem: 10: nothing provides 'this-is-only-for-build-envs' needed by the to be installed ffmpeg-8-mini-libs-8.1-1.1.x86_64
Problem: 11: nothing provides 'this-is-only-for-build-envs' needed by the to be installed ffmpeg-8-mini-libs-8.1-1.1.x86_64
Problem: 12: nothing provides 'this-is-only-for-build-envs' needed by the to be installed ffmpeg-8-mini-libs-8.1-1.1.x86_64
Problem: 13: the to be installed vlc-noX-3.0.23-387.2.x86_64 requires 'libvlc5 = 3.0.23-387.2', but this requirement cannot be provided
not installable providers: libvlc5-3.0.23-387.2.x86_64[home_plater]

Problem: 14: the to be installed vlc-noX-3.0.23-387.2.x86_64 requires 'libvlccore9 = 3.0.23-387.2', but this requirement cannot be provided
not installable providers: libvlccore9-3.0.23-387.2.x86_64[home_plater]

Please allways paste also the complete commandline with your paste.

Why do you have installed vlc form /home/plater?