Page 1 of 2 12 LastLast
Results 1 to 10 of 15

Thread: Packman and Tumbleweed-OSS offer conflicting packages for identical codec libraries

Hybrid View

  1. #1
    Join Date
    Jan 2009
    Location
    Romania, Bucharest
    Posts
    887

    Default Packman and Tumbleweed-OSS offer conflicting packages for identical codec libraries

    As this issue is partly related to the Packman repositories it made sense not to report it on the openSUSE bug tracker. However I'm opening this thread to draw attention to the problem and ask if there's a workaround in case others are experiencing it.

    Last night's Tumbleweed snapshot introduced a major issue with codecs, apparently due to bad package naming; The openSUSE-OSS repository offers one version of the codec files, whereas the Packman repository offers the same base version but with another number added at the end. Since the openSUSE repo only offers codecs with some formats due to ancient patent issues while Packman offers full functionality, yet both can be installed at the same time, some applications don't know what to use as different ones are compiled / packaged to look for a different library. Currently I have both installed to avoid applications not starting up, but the Firefox web browser has issues with mp4 files including randomly not being able to play Youtube videos. A list of affected packages includes:

    Code:
    libavutil56
    libswscale5
    libswresample3
    libpostproc55
    libavcodec58
    libavformat58
    libavfilter7
    libavdevice58
    For example, if you open the YaST - Software Management and look for libavcodec you get two packages for the same version: "libavcodec58" (openSUSE) and "libavcodec58_91" (Packman). That extra "_91" should not exist, it should be a replacement for the same package instead of a different one entirely! Installing either one, either the other, either both will get some applications working properly but upset others. Is the issue known and a fix in the works?

    openSUSE Tumbleweed x64, KDE Framework 5

  2. #2
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    14,397
    Blog Entries
    3

    Default Re: Packman and Tumbleweed-OSS offer conflicting packages for identical codec libraries

    That's also being discussed in another thread:
    https://forums.opensuse.org/showthre...Today-s-Update

    I would just wait a day or two and see if it is taken care of.
    openSUSE Leap 15.2; KDE Plasma 5.18.5;

  3. #3
    Join Date
    Jan 2009
    Location
    Romania, Bucharest
    Posts
    887

    Default Re: Packman and Tumbleweed-OSS offer conflicting packages for identical codec libraries

    Quote Originally Posted by nrickert View Post
    That's also being discussed in another thread:
    https://forums.opensuse.org/showthre...Today-s-Update

    I would just wait a day or two and see if it is taken care of.
    Thanks, will do. The broken Youtube videos show up in Chromium so I have a workaround for the time being.
    openSUSE Tumbleweed x64, KDE Framework 5

  4. #4
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    1,902
    Blog Entries
    1

    Default Re: Packman and Tumbleweed-OSS offer conflicting packages for identical codec libraries

    Quote Originally Posted by MirceaKitsune View Post
    As this issue is partly related to the Packman repositories it made sense not to report it on the openSUSE bug tracker. However I'm opening this thread to draw attention to the problem and ask if there's a workaround in case others are experiencing it.

    Last night's Tumbleweed snapshot introduced a major issue with codecs, apparently due to bad package naming; The openSUSE-OSS repository offers one version of the codec files, whereas the Packman repository offers the same base version but with another number added at the end. Since the openSUSE repo only offers codecs with some formats due to ancient patent issues while Packman offers full functionality, yet both can be installed at the same time, some applications don't know what to use as different ones are compiled / packaged to look for a different library. Currently I have both installed to avoid applications not starting up, but the Firefox web browser has issues with mp4 files including randomly not being able to play Youtube videos. A list of affected packages includes:

    Code:
    libavutil56
    libswscale5
    libswresample3
    libpostproc55
    libavcodec58
    libavformat58
    libavfilter7
    libavdevice58
    For example, if you open the YaST - Software Management and look for libavcodec you get two packages for the same version: "libavcodec58" (openSUSE) and "libavcodec58_91" (Packman). That extra "_91" should not exist, it should be a replacement for the same package instead of a different one entirely! Installing either one, either the other, either both will get some applications working properly but upset others. Is the issue known and a fix in the works?
    The following versions exist and are installed:

    Code:
     erlangen:~ # zypper se -is libavcodec58
    Loading repository data...
    Reading installed packages...
    
    S | Name            | Type    | Version   | Arch   | Repository
    --+-----------------+---------+-----------+--------+------------------
    i | libavcodec58    | package | 4.2.3-4.5 | x86_64 | (System Packages)
    i | libavcodec58_91 | package | 4.3.1-4.1 | x86_64 | Packman
    erlangen:~ #
    libavcodec58_91 is used by vlc, all other applications use libavcodec58. Note the label "System Packages". Currently no version is available in the repos:

    Code:
    erlangen:~ # zypper dup --allow-vendor-change --auto-agree-with-licenses --allow-downgrade 
    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...
    2 Problems:
    Problem: libavfilter7_85-4.3.1-4.1.x86_64 requires libavresample4_0 = 4.3.1-4.1, but this requirement cannot be provided
    Problem: libavfilter7-4.2.3-4.5.x86_64 requires libavcodec58 = 4.2.3-4.5, but this requirement cannot be provided
    
    Problem: libavfilter7_85-4.3.1-4.1.x86_64 requires libavresample4_0 = 4.3.1-4.1, but this requirement cannot be provided
      not installable providers: libavresample4_0-4.3.1-4.1.i586[Packman]
                       libavresample4_0-4.3.1-4.1.x86_64[Packman]
     Solution 1: deinstallation of handbrake-cli-1.3.3-2.2.x86_64
     Solution 2: deinstallation of libavfilter7-4.2.3-4.5.x86_64
     Solution 3: install handbrake-cli-1.3.3-3.1.i586 despite the inferior architecture
     Solution 4: keep obsolete handbrake-cli-1.3.3-2.2.x86_64
     Solution 5: break libavfilter7_85-4.3.1-4.1.x86_64 by ignoring some of its dependencies
    
    Choose from above solutions by number or skip, retry or cancel [1/2/3/4/5/s/r/c/d/?] (c): 
    erlangen:~ #
    None of the above options is acceptable. Keeping the obsolete versions switches all packages from packman to repo-oss, resulting in crippled applications. Thus I rolled back from snapshot 20200714 to 20200710.
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), openSUSE Tumbleweed, KDE Plasma 5

  5. #5

    Default Re: Packman and Tumbleweed-OSS offer conflicting packages for identical codec libraries

    Snapper doesn't seem to be helping here.
    I rolled back to two days ago but found that Netflix/Disney still won't play any content.

  6. #6

    Default Re: Packman and Tumbleweed-OSS offer conflicting packages for identical codec libraries

    As well as twice trying Snapper rollback to two days ago - to no effect - i also tried updating to the latest release with the fix.
    Amazon/Netflix/Disney all broken.

    When I did the update yesterday to Wednesdays release, i always picked the option that suggested packman with no vendor change.
    Is it better for me to simply do a clean install of tumbleweed?

  7. #7
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    1,902
    Blog Entries
    1

    Default Re: Packman and Tumbleweed-OSS offer conflicting packages for identical codec libraries

    Quote Originally Posted by Jedibeeftrix View Post
    As well as twice trying Snapper rollback to two days ago - to no effect - i also tried updating to the latest release with the fix.
    Amazon/Netflix/Disney all broken.

    When I did the update yesterday to Wednesdays release, i always picked the option that suggested packman with no vendor change.
    Is it better for me to simply do a clean install of tumbleweed?
    https://forums.opensuse.org/entry.ph...e-dumped)-quot
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), openSUSE Tumbleweed, KDE Plasma 5

  8. #8
    Join Date
    Jan 2009
    Location
    Romania, Bucharest
    Posts
    887

    Default Re: Packman and Tumbleweed-OSS offer conflicting packages for identical codec libraries

    Snapshot 20200715 just fixed everything for me. Thanks everyone!
    openSUSE Tumbleweed x64, KDE Framework 5

  9. #9

    Default Re: Packman and Tumbleweed-OSS offer conflicting packages for identical codec libraries

    Quote Originally Posted by karlmistelberger View Post
    Quote Originally Posted by Jedibeeftrix View Post
    As well as twice trying Snapper rollback to two days ago - to no effect - i also tried updating to the latest release with the fix.
    Amazon/Netflix/Disney all broken.

    When I did the update yesterday to Wednesdays release, i always picked the option that suggested packman with no vendor change.
    Is it better for me to simply do a clean install of tumbleweed?
    https://forums.opensuse.org/entry.ph...e-dumped)-quot
    "As well as twice trying Snapper rollback to two days ago - to no effect - i also tried updating to the latest release with the fix.
    Amazon/Netflix/Disney all broken."


    I'm running the latest release. Still bust.
    ----------------------------
    Shall i just do a clean install of todays release (20200715), is that likely to fix things if an upgrade has not worked?

  10. #10
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    14,397
    Blog Entries
    3

    Default Re: Packman and Tumbleweed-OSS offer conflicting packages for identical codec libraries

    Quote Originally Posted by Jedibeeftrix View Post
    I'm running the latest release. Still bust.
    Repeat the switch of system packages to packman
    Code:
    zypper dup --from packman --allow-vendor-change
    (except replace "packman" by the name that you are using for the packman repo.

    Then, when done, try to remove any orphaned packages. In my opinion, the best way to do that is with Yast Software Management. Select the "Repositories" view (use the "VIew" tab to select).

    Then look for "Secondary filter" and select "Unmaintained Packages". Those are the orphans (packages not found in any enable repo). Try deleting them.

    I prefer to do it this way, because Yast will present a popup with any conflicts. In case of conflicts, you might want to temporarily keep that package anyway. If you remove orphans with "zypper remove", then sometimes "zypper" just goes ahead and also removes conflicting packages without asking for approval.
    openSUSE Leap 15.2; KDE Plasma 5.18.5;

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •