Packman repo advice

I added Packman to my new installation as I was having some video issue browsing the web.

3 weeks later, I now get this and I don’t want to messup my installation

What would be the best course of action from here, see the warning below…

Packman repo
URL: Index of /pub/linux/misc/packman/suse/openSUSE_Tumbleweed/

yoda@localhost:~> sudo zypper dup

New repository or package signing key received:

  Repository:       packman
  Key Fingerprint:  F887 5B88 0D51 8B6B 8C53 0D13 45A1 D067 1ABD 1AFB
  Key Name:         PackMan Project (signing key) <packman@links2linux.de>
  Key Algorithm:    RSA 4096
  Key Created:      Tue 03 Sep 2024 04:21:04 PM EDT
  Key Expires:      Thu 03 Sep 2026 04:20:39 PM EDT
  Rpm Name:         gpg-pubkey-1abd1afb-66d76fb0



    Note: Signing data enables the recipient to verify that no modifications occurred after the data
    were signed. Accepting data with no, wrong or unknown signature can lead to a corrupted system
    and in extreme cases even to a system compromise.

    Note: A GPG pubkey is clearly identified by its fingerprint. Do not rely on the key's name. If
    you are not sure whether the presented key is authentic, ask the repository provider or check
    their web site. Many providers maintain a web page showing the fingerprints of the GPG keys they
    are using.

Do you want to reject the key, trust temporarily, or trust always? [r/t/a/?] (r): t
Retrieving repository 'packman' metadata ...............................................................................................................................................................................................................................[done]
Building repository 'packman' cache ....................................................................................................................................................................................................................................[done]
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...
9 Problems:
Problem: 1: nothing provides 'librubberband.so.3' needed by the to be installed libavfilter10-7.1.1-1699.9.pm.9.i586
Problem: 2: nothing provides 'librubberband.so.3()(64bit)' needed by the to be installed libavfilter10-7.1.1-1699.9.pm.9.x86_64
Problem: 3: nothing provides 'librubberband.so.3()(64bit)' needed by the to be installed libavfilter10-7.1.1-1699.9.pm.9.x86_64
Problem: 4: nothing provides 'this-is-only-for-build-envs' needed by the to be installed ffmpeg-7-mini-libs-7.1.1-7.1.x86_64
Problem: 5: nothing provides 'this-is-only-for-build-envs' needed by the to be installed ffmpeg-7-mini-libs-7.1.1-7.1.x86_64
Problem: 6: nothing provides 'this-is-only-for-build-envs' needed by the to be installed ffmpeg-7-mini-libs-7.1.1-7.1.x86_64
Problem: 7: nothing provides 'this-is-only-for-build-envs' needed by the to be installed ffmpeg-7-mini-libs-7.1.1-7.1.x86_64
Problem: 8: nothing provides 'this-is-only-for-build-envs' needed by the to be installed ffmpeg-7-mini-libs-7.1.1-7.1.x86_64
Problem: 9: nothing provides 'this-is-only-for-build-envs' needed by the to be installed ffmpeg-7-mini-libs-7.1.1-7.1.x86_64

Problem: 1: nothing provides 'librubberband.so.3' needed by the to be installed libavfilter10-7.1.1-1699.9.pm.9.i586
 Solution 1: install libavfilter10-7.1.1-7.1.x86_64 from vendor openSUSE
  replacing libavfilter10-7.1.1-1699.9.pm.3.x86_64 from vendor http://packman.links2linux.de
 Solution 2: keep obsolete libavfilter10-7.1.1-1699.9.pm.3.x86_64
 Solution 3: break libavfilter10-7.1.1-1699.9.pm.9.i586 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): 

Delete this one and install ffmpe-7.

Why do you have installed a 32 bit package?
These are mine without update:

i  | libavfilter10                    | Paket | 7.1.1-1699.9.pm.3   | x86_64 | (Systempakete)
v  | libavfilter10                    | Paket | 7.1.1-1699.9.pm.9   | x86_64 | Packman Repository
v  | libavfilter10                    | Paket | 7.1.1-1699.9.pm.9   | i586   | Packman Repository
v  | libavfilter10                    | Paket | 7.1.1-7.2           | x86_64 | Haupt-Repository (OSS)
   | libavfilter10-32bit              | Paket | 7.1.1-1699.9.pm.9   | x86_64 | Packman Repository
   | libavfilter10-32bit              | Paket | 7.1.1-7.2           | x86_64 | Haupt-Repository (OSS)
   | libavfilter10-32bit-debuginfo    | Paket | 7.1.1-1699.9.pm.9   | x86_64 | Packman Repository
   | libavfilter10-debuginfo          | Paket | 7.1.1-1699.9.pm.9   | x86_64 | Packman Repository
   | libavfilter10-debuginfo          | Paket | 7.1.1-1699.9.pm.9   | i586   | Packman Repository

Tks for your reply

:frowning: How do I fix this ?

it’s a new Slowrool installation ( 3 weeks) and I would prefer not to reinstall.

I probably googled and used what was suggested and my lack of knowledge are responsible for that action…

If I want to use the same you are using, how do I proceed ??

delete it and install the 64 bit package.
Also delete the ffmpeg-7-mini-libs, not necessary for you.

sorry to ask
Delete what, the repo ? The packages, how / what is the easiest way ? I mean to locate what is 32 bits and delete them

What is the easiest and safest way to install the 64 bit packages…

Noobie here… So sorry

zypper rm libavfilter10

zypper in -f libavfilter10

zypper rm ffmpeg-7-mini-libs

tks I guess I remove the repo too ?

And how to reinstall the right ones ?

since I did zypper rm libavfilter10

I don’t have access to my KDE environnement anymore ! Weird

My Login Window default to IceWM Session… And I can’t change that…

Zzzzzzz

That should not be so.

Iinstall it with the second command.

sorry for picture quality, I can’t Copy / paste from the new DE environment / Terminal

Please check that librubberband3is installed:

LT-B:~ # zypper se -si librubberband3
Loading repository data...
Reading installed packages...

S  | Name           | Type    | Version   | Arch   | Repository
---+----------------+---------+-----------+--------+-----------
i  | librubberband3 | package | 4.0.0-1.1 | x86_64 | repo-oss
LT-B:~ # 

librubberband3 is not yet available for slowroll, at least I do not see it in the slowroll repo, only librubberband2

There is a packman repo for slowroll, maybe that would be a better choice.
https://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Slowroll/Essentials/

1 Like

tks

  • I have configured that repo
  • Did a dup update
  • when asked for choices I choose to use openSUSE vendor

Rebooted and still endup in iceWM

DO I need to reinstall ? :-/ I am opened leaving slowroll and moving to Tumbleweed if it can avoid me having to reinstall

I do not know what packages have been removed when you deleted libavfilter10, but you can check by opening YAST2 - Software- Extras - there should be a history (naming could be different, I just translated what I have in front of me).
When I try to delete that lib, it wants to delete a number of plasma packages, I am sure it did the same to you in slowroll. You need to reinstall those packages.

You can also look in /var/log/zypp/history for the changes.

1 Like

Simply reinstall the Plasma patterns.

@sao_bento tks it worked ! I was able to choose PLASMA wayland at login and now I am back in KDE !

Tks hui but I dont know what is a plasma patterns and even less how to reinstall it

I am now back in my KDE DE, not 100% sure of if my 3 weeks old SLowrool is still " clean / safe etc" but it’s now back and running…

1 Like

Simple answer: open YaST Software, the last tab should be named “Patterns”.
On the left you can see “KDE Plasma 6 Desktop Base” and “KDE Applications and Plasma Desktop”.
Clicking on the tick box should install the missing packages.
Of course you can find additional details in man zypper and install/reinstall using zypper.

1 Like

Tks orso Bruno

Will do…

should I also installed those that are unticked ?