Another Problem With Today's Update

I’m getting this problem message:


> sudo zypper dup                                                                      
Loading repository data...
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...
10 Problems:
Problem: problem with installed package libavcodec58-4.2.3-4.3.x86_64
Problem: problem with installed package libavdevice58-4.2.3-4.3.x86_64
Problem: problem with installed package libavfilter7-4.2.3-4.3.x86_64
Problem: problem with installed package libavformat58-4.2.3-4.3.x86_64
Problem: problem with installed package libavutil56-4.2.3-4.3.x86_64
Problem: problem with installed package libpostproc55-4.2.3-4.3.x86_64
Problem: problem with installed package libswresample3-4.2.3-4.3.x86_64
Problem: problem with installed package libswscale5-4.2.3-4.3.x86_64
Problem: libffms2-4-2.23.1-1.10.x86_64 requires libavresample.so.4()(64bit), but this requirement cannot be provided
Problem: libffms2-4-2.23.1-1.10.x86_64 requires libavresample.so.4()(64bit), but this requirement cannot be provided

Problem: problem with installed package libavcodec58-4.2.3-4.3.x86_64
 Solution 1: install libavcodec58-4.2.3-1.1.x86_64 (with vendor change)
  http://packman.links2linux.de  -->  openSUSE
 Solution 2: keep obsolete libavcodec58-4.2.3-4.3.x86_64

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

On my system, the first eight packages are from packman, but libffms2-4 is from Main Repository (OSS). I don’t see libffms2-4 available from packman, so does this mean that I just need to wait for libffms2-4 to be upgraded in the OSS repo?

Regards,
Gene

Please show


zypper lr -d


, I think you did not do the vendor change on the Packman repo.

Same here. And I have done the vendor change to packman already.

Some packages were renamed, i.e. appended a number to them, see https://build.opensuse.org/request/show/820572

It looks like https://build.opensuse.org/package/show/openSUSE%3AFactory/ffms2 wasn’t updated. You could ping the maintainer over there.

For my update, it wanted to switch those package to the openSUSE oss repo. I think that was 8 vendor changes.

I allowed it. But I assume that they will be able to switch back as soon as the packman maintainers rebuild those packages.

I did do the vendor change when I installed the recommended media codecs. It changed conky to packman as well the codecs. Looks like libffms2-4 needs to be updated.

Gene

A bit more detail. I did my update with allow-vendor-change. And I got:


The following 11 packages are going to be downgraded:
  ffmpeg-4 gstreamer-plugins-libav libavcodec58 libavdevice58 libavfilter7
  libavformat58 libavresample4 libavutil56 libpostproc55 libswresample3
  libswscale5

The following 11 packages are going to change vendor:
  ffmpeg-4                 http://packman.links2linux.de -> openSUSE
  gstreamer-plugins-libav  http://packman.links2linux.de -> openSUSE
  libavcodec58             http://packman.links2linux.de -> openSUSE
  libavdevice58            http://packman.links2linux.de -> openSUSE
  libavfilter7             http://packman.links2linux.de -> openSUSE
  libavformat58            http://packman.links2linux.de -> openSUSE
  libavresample4           http://packman.links2linux.de -> openSUSE
  libavutil56              http://packman.links2linux.de -> openSUSE
  libpostproc55            http://packman.links2linux.de -> openSUSE
  libswresample3           http://packman.links2linux.de -> openSUSE
  libswscale5              http://packman.links2linux.de -> openSUSE

I will note that this was in a virtual machine that I use for testing. I have not yet updated my real machines. I usually wait for Saturday to do that.

I expect that this is a temporary glitch until the packman maintainers update these packages. And, since I am allowing vendor change for this VM, I’ll see that happen.

One way to get around the problem would be to use “zypper up” instead of “zypper dup”. That gives an incomplete update, but it will avoid this problem. And by the time of the next “zypper dup”, it will probably have been fixed.

Did this update today on my wifes notebook (with vendor changes fom packman to opensuse), now no Youtube videos play. Not funny!

Tried to shift in YaST all packages to packman again, but get three more warnings, which I can not resolve.

Hi
It won’t help as nothing is rebuilding on the packman build service (no API or WEBUI working), it’s dead as the proverbial dodo… so all the links to new/updated packages on the openSUSE Build service won’t get built.

Only thing I understand is this dodo thing. Rest: What’s next? Reinstall TW? In the meantime I downloaded the relevant workout vids (cough) with youtube-dl, downgraded vlc to version 3 (as 4dev is a nightmare), found out that the machine explodes with highest resolution downloaded by youtube-dl by default… now the vid plays an I lost 2 h of my life time.

What’s going on in TW repos? Parents on holiday, kiddies do the update stuff? :-/

Do you have snapshots enabled? Boot into the last, and revert. There’s instructions around the forum and wiki.

BTRFS is sent from hell… :wink:

Good to read this post, thought it was just me.

Hi
That’s pretty rich… perhaps it’s time for a vacation break from these fora?

You do realize that packman is a donated service of peoples time, hardware and $$$?

Please tone down, consider this a warning. This is a support forum, not some soapbox.

The problem is actually the other way round: Packman has the latest ffmpeg-4 update already, but it’s not in Tumbleweed yet.

Anyway, the effect is similar, you need to wait for an update…
It should be fixed in the next Tumbleweed snapshot, which should have the ffmpeg-4 update and all dependent packages rebuilt against it.

And no, this did not happen because somebody made a mistake.
It’s a “timing problem” caused by the fact that these are separate repos, and even separate build systems.

The problem is actually the other way round: Packman has the latest ffmpeg-4 update already, but it's not in Tumbleweed yet.

Anyway, the effect is similar, you need to wait for an update...
It should be fixed in the next Tumbleweed snapshot, which should have  the ffmpeg-4 update and all dependent packages rebuilt against it.

Many thanks for explaining.

This is probably not everybody’s cup of tea but I have Packman only for codecs. I added the VLC repo, prioritized it higher, did the dup with vendor change, and my system was happy.

/m

Many thanks! Nice to see that there are people around understanding what’s going on! :slight_smile:

Will the VLC repo try to install the 4-dev version? Otherwise I could try this… :wink:

FYI, the new Tumbleweed snapshot has been released already a couple of hours ago.
See [opensuse-factory] New Tumbleweed snapshot 20200715 released! - openSUSE Factory - openSUSE Mailing Lists :

==== ffmpeg-4 ====
Version update (4.2.3 -> 4.3.1)

  • Update to version 4.3.1:
  • Stable bug fix release, mainly codecs and format fixes.
  • Add soversion.patch to workaround ELF ABI breakage.
  • Update to release 4.3
  • A plethora of new video filters
  • Intel QSV-accelerated VP9 decoding
  • VDPAU VP9 hwaccel
  • QSV-accelerated VP9 encoding
  • AV1 frame merge bitstream filter
  • AV1 Annex B demuxer
  • Expanded styling support for 3GPP Timed Text Subtitles
  • Support for muxing PCM and PGS in M2TS
  • Drop ffmpeg-prefer-dav1d-for-playback.patch
    (solved differently)
  • Drop ffmpeg4_swscale_replace_illegal_vector_keyword.patch,
    ffmpeg4_swscale_fix_altivec_vsx_recent_gcc.patch,
    929e5159bc13da374b83f5627879c607acce180b.patch
    (merged)

So the conflicts/mismatches should be gone now.

You may have to switch packages back to Packman though (libavcodec in particular), in case that zypper picks them from the standard OSS repo for some reason (should not happen if Packman has a higher priority though).