Page 2 of 4 FirstFirst 1234 LastLast
Results 11 to 20 of 32

Thread: Warning while adding Packman Repository to fresh OpenSUSE Tumbleweed installation

  1. #11
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    4,000

    Default Re: Warning while adding Packman Repository to fresh OpenSUSE Tumbleweed installation

    Quote Originally Posted by Rocary View Post
    So, I did the command sudo zypper modifyrepo --priority 90 "Packman Repository", now this repository has a highest priority.

    Then I did the second command, with the option --dry-run :

    Code:
    niels@rivcrn:~> sudo zypper dist-upgrade --dry-run --allow-vendor-change --allow-downgrade
    Chargement des données du dépôt...
    Lecture des paquets installés...
    Avertissement : Vous êtes sur le point d'exécuter une mise à niveau de distribution avec tous les dépôts activés. Assurez-vous que ces dépôts sont compatibles avant de continuer. Reportez-vous à 'man zypper' pour obtenir plus d'informations sur cette commande.
    Calcul de la mise à niveau de la distribution...
    
    Les 19 paquets suivants vont être mis à jour :
      libavcodec58_134 libavfilter7_110 libavformat58_76 libavresample4_0 libavutil56_70 libfdk-aac2 libheif1
      libpostproc55_9 libquicktime0 libswresample3_9 libswscale5_9 libvlc5 libvlccore9 vlc vlc-codec-gstreamer
      vlc-lang vlc-noX vlc-qt vlc-vdpau
    
    Les 19 paquets suivants vont changer de fournisseur :
      libavcodec58_134     openSUSE -> http://packman.links2linux.de
      libavfilter7_110     openSUSE -> http://packman.links2linux.de
      libavformat58_76     openSUSE -> http://packman.links2linux.de
      libavresample4_0     openSUSE -> http://packman.links2linux.de
      libavutil56_70       openSUSE -> http://packman.links2linux.de
      libfdk-aac2          openSUSE -> http://packman.links2linux.de
      libheif1             openSUSE -> http://packman.links2linux.de
      libpostproc55_9      openSUSE -> http://packman.links2linux.de
      libquicktime0        openSUSE -> http://packman.links2linux.de
      libswresample3_9     openSUSE -> http://packman.links2linux.de
      libswscale5_9        openSUSE -> http://packman.links2linux.de
      libvlc5              openSUSE -> http://packman.links2linux.de
      libvlccore9          openSUSE -> http://packman.links2linux.de
      vlc                  openSUSE -> http://packman.links2linux.de
      vlc-codec-gstreamer  openSUSE -> http://packman.links2linux.de
      vlc-lang             openSUSE -> http://packman.links2linux.de
      vlc-noX              openSUSE -> http://packman.links2linux.de
      vlc-qt               openSUSE -> http://packman.links2linux.de
      vlc-vdpau            openSUSE -> http://packman.links2linux.de
    
    Les 6 NOUVEAUX paquets suivants vont être installés :
      libde265-0 librtmp1 libvo-amrwbenc0 libx264-161 libx265-199 libxvidcore4
    
    19 paquets à mettre à jour, 6 nouveaux, 19 à changer de fournisseur.
    Taille de téléchargement totale : 22,4 MiB. Déjà en cache : 0 B. Après l'opération, 25,9 MiB d'espace disque
    supplémentaire sera utilisé.
    Continuer ? [o/n/v/...? affiche toutes les options] (o):
    No mention about pipewire, but maybe the problem will be solved by running this command

    Thank you
    Continuer ? o.
    i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), 5600X (2022) openSUSE Tumbleweed, KDE Plasma

  2. #12
    Join Date
    Jan 2022
    Location
    France
    Posts
    24

    Default Re: Warning while adding Packman Repository to fresh OpenSUSE Tumbleweed installation

    Quote Originally Posted by hcvv View Post
    @Rocary,

    I will learn you a small trick.
    When posting computer text from your French language system into this English language forum, precede the command with LANG=C. Like
    Code:
    LANG=C zypper dup ...............
    Hi hcvv,

    Thanks for the trick, I will do this every time from now

  3. #13
    Join Date
    Jan 2022
    Location
    France
    Posts
    24

    Default Re: Warning while adding Packman Repository to fresh OpenSUSE Tumbleweed installation

    @conram @karl,

    So I did the command sudo zypper dist-upgrade --allow-vendor-change --allow-downgrade and I updated my OS.

    But when I click on "Switch system packages" for Packman Repository, in Software Management, I still get the warning :

    Nothing provides "pipewire=0.3.43" which is needed for pipewire-lang-0.3.43.1.noarch to install
    Conflict resolution:
    1: uninstall pipewire-lang-0.3.43.1.noarch
    2: keep deprecated pipewire-lang-0.3.43.1.noarch
    3: break pipewire-lang-0.3.43.1.noarch ignoring some of its dependencies
    I still don't know which option to choose I need to switch packages in order to get my sound to work !
    OS: openSUSE Tumbleweed x86_64


  4. #14
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    4,000

    Default Re: Warning while adding Packman Repository to fresh OpenSUSE Tumbleweed installation

    Quote Originally Posted by Rocary View Post
    So I did the command sudo zypper dist-upgrade --allow-vendor-change --allow-downgrade and I updated my OS.

    But when I click on "Switch system packages" for Packman Repository, in Software Management, I still get the warning ...
    I have sound. I never click on "Switch system packages" for Packman Repository, in Software Management. I run:
    Code:
    erlangen:~ # zypper -vvv dup --from Packman 
    Verbosity: 3 
    Initializing Target 
    Checking whether to refresh metadata for Application_Geo 
    Checking whether to refresh metadata for BellSoft Repository 
    Checking whether to refresh metadata for Packman 
    Checking whether to refresh metadata for chrome 
    Checking whether to refresh metadata for jalbum 
    Checking whether to refresh metadata for openSUSE-Tumbleweed-Oss 
    Checking whether to refresh metadata for openSUSE-Tumbleweed-Non-Oss 
    Checking whether to refresh metadata for openSUSE-Tumbleweed-Update 
    Loading repository data... 
    Reading installed packages... 
    Computing distribution upgrade... 
    Force resolution: No 
    
    Problem: nothing provides 'pipewire = 0.3.43' needed by the to be installed pipewire-lang-0.3.43-3.1.noarch 
     Solution 1: deinstallation of pipewire-lang-0.3.45-1.1.noarch 
     Solution 2: keep obsolete pipewire-lang-0.3.45-1.1.noarch 
     Solution 3: break pipewire-lang-0.3.43-3.1.noarch by ignoring some of its dependencies 
    
    Choose from above solutions by number or cancel [1/2/3/c/d/?] (c): 1 
    Applying solution 1 
    Resolving dependencies... 
    Computing distribution upgrade... 
    Force resolution: No 
    
    The following 2 package updates will NOT be installed:
      youtube-dl                  2021.12.17-1.3  noarch  openSUSE-Tumbleweed-Oss  openSUSE 
      youtube-dl-bash-completion  2021.12.17-1.3  noarch  openSUSE-Tumbleweed-Oss  openSUSE 
    
    The following package is going to be upgraded:
      conky  1.12.2-8.182 -> 1.12.2-8.183  x86_64  Packman  http://packman.links2linux.de 
    
    The following package is going to be REMOVED:
      pipewire-lang  0.3.45-1.1  noarch  openSUSE 
    
    1 package to upgrade, 1 to remove. 
    Overall download size: 668.1 KiB. Already cached: 0 B. After the operation, 353.4 KiB will be freed. 
    Continue? [y/n/v/...? shows all options] (y): 
    committing 
    Retrieving package conky-1.12.2-8.183.x86_64                                                                                                                                                           (1/1), 668.1 KiB (  1.5 MiB unpacked) 
    Retrieving: http://ftp.fau.de/packman/suse/openSUSE_Tumbleweed/Multimedia/x86_64/conky-1.12.2-8.183.x86_64.rpm .........................................................................................................[done (367.4 KiB/s)] 
    
    Checking for file conflicts: .........................................................................................................................................................................................................[done] 
    (1/2) Removing pipewire-lang-0.3.45-1.1.noarch .......................................................................................................................................................................................[done] 
    (2/2) Installing: conky-1.12.2-8.183.x86_64 ..........................................................................................................................................................................................[done] 
    CommitResult  (total 2, done 2, error 0, skipped 0, updateMessages 0) 
    Checking for running processes using deleted libraries... 
      
    erlangen:~ # zypper se -is pipewire 
    Loading repository data... 
    Reading installed packages... 
    
    S  | Name                     | Type    | Version    | Arch   | Repository 
    ---+--------------------------+---------+------------+--------+------------------------ 
    i  | libpipewire-0_3-0        | package | 0.3.45-1.1 | x86_64 | openSUSE-Tumbleweed-Oss 
    i  | pipewire                 | package | 0.3.45-1.1 | x86_64 | openSUSE-Tumbleweed-Oss 
    i+ | pipewire-modules-0_3     | package | 0.3.45-1.1 | x86_64 | openSUSE-Tumbleweed-Oss 
    i  | pipewire-spa-plugins-0_2 | package | 0.3.45-1.1 | x86_64 | openSUSE-Tumbleweed-Oss 
    i  | pipewire-spa-tools       | package | 0.3.45-1.1 | x86_64 | openSUSE-Tumbleweed-Oss 
    i  | pipewire-tools           | package | 0.3.45-1.1 | x86_64 | openSUSE-Tumbleweed-Oss 
    erlangen:~ #
    See: https://forums.opensuse.org/showthre...Packman-Codecs
    i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), 5600X (2022) openSUSE Tumbleweed, KDE Plasma

  5. #15
    Join Date
    Jan 2022
    Location
    France
    Posts
    24

    Default Re: Warning while adding Packman Repository to fresh OpenSUSE Tumbleweed installation

    Thanks @karl,

    I did exactly what you did, I wanted to click on switch system packages because it's the option 3 in the documentation : https://en.opensuse.org/SDB:Installi...n_repositories

    But now my problem is solved, thank you again
    OS: openSUSE Tumbleweed x86_64


  6. #16
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    30,944

    Default Re: Warning while adding Packman Repository to fresh OpenSUSE Tumbleweed installation

    Quote Originally Posted by karlmistelberger View Post
    I have sound. I never click on "Switch system packages" for Packman Repository, in Software Management. I run:
    Code:
    [FONT=monospace]erlangen:~ # zypper -vvv dup --from Packman 
    That is one way to do what is colloquially called "switching to Packman". Another way is doing it in YaST > Software > Software Management. Why do you try to confuse the OP by telling him that he should prefer to do it your way, implicating that the other way is wrong?
    Henk van Velden

  7. #17
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    4,000

    Default Re: Warning while adding Packman Repository to fresh OpenSUSE Tumbleweed installation

    Quote Originally Posted by hcvv View Post
    Why do you try to confuse the OP by telling him that he should prefer to do it your way, implicating that the other way is wrong?
    I reiterate:
    I never click on "Switch system packages" for Packman Repository, in Software Management. I run "zypper dup --from packman".
    I tell that I prefer the later (for reasons of consistency, e.g. upgrade Tumbleweed with "zypper dup"). I make no suggestion what users should do.

    More:

    1. https://forums.opensuse.org/showthre...dup-priorities

    2. Repository priorities for the real world user

    Use additional repositories with confidence

    The topic of additional repositories comes up on a regular basis. The official position is to submit everything to Factory to avoid the issue, but for a large number of reasons this cannot always be the case. As such users living in the real world have to navigate the unsupported landscape. By far the best approach is to use repository priorities available through libzypp, but unfortunately this is not well known.

    This quick talk will cover the basic usage of priorities, strategies for real usage, and examples of how effective the workflow can be. Additionally some pitfalls will also be covered.

    The topic of additional repositories comes up on a regular basis. The official position is to submit everything to Factory to avoid the issue, but for a large number of reasons this cannot always be the case. As such users living in the real world have to navigate the unsupported landscape. By far the best approach is to use repository priorities available through libzypp, but unfortunately this is not well known.

    This quick talk will cover the basic usage of priorities, strategies for real usage, and examples of how effective the workflow can be. Additionally some pitfalls will also be covered.

    Jimmy Berry

    https://www.youtube.com/watch?v=x8kEaJU6hlw
    i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), 5600X (2022) openSUSE Tumbleweed, KDE Plasma

  8. #18
    Join Date
    Jun 2008
    Location
    East of Podunk
    Posts
    33,251
    Blog Entries
    15

    Default Re: Warning while adding Packman Repository to fresh OpenSUSE Tumbleweed installation

    Hi
    Never needed to set priorities as vendor stickiness is respected, zypper dup to change...
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  9. #19
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    4,000

    Default Re: Warning while adding Packman Repository to fresh OpenSUSE Tumbleweed installation

    Quote Originally Posted by malcolmlewis View Post
    Never needed to set priorities as vendor stickiness is respected, zypper dup to change...
    Sure! I relied on vendor stickiness and zypper dup to change from 2014 to 2018. That worked, but was cumbersome in some situations. I switched to priorities in 2018 and use them for 4 years. Priorities are the smoother experience and I will stay with them.

    This is not a recommendation. This is sharing my experience. Users may try out priorities and switch back at any time.

    Changes made:

    1. "zypper modifyrepo --priority <new priority> <repo>" for non product repositories.

    2. change default:
    Code:
    erlangen:~ # grep -v ^\# /etc/zypp/zypp.conf|grep -v ^\$ 
    [main] 
    solver.dupAllowVendorChange = true 
    multiversion = provides:multiversion(kernel) 
    multiversion.kernels = latest,latest-1,running 
    erlangen:~ #
    Code:
    erlangen:~ # grep solver.dup /etc/zypp/zypp.conf
    # solver.dupAllowDowngrade = true
    # solver.dupAllowNameChange = true
    # solver.dupAllowArchChange = true
    solver.dupAllowVendorChange = true
    erlangen:~ #
    See also section "Best of both worlds": https://youtu.be/x8kEaJU6hlw?t=495
    i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), 5600X (2022) openSUSE Tumbleweed, KDE Plasma

  10. #20
    Join Date
    Jan 2022
    Location
    France
    Posts
    24

    Default Re: Warning while adding Packman Repository to fresh OpenSUSE Tumbleweed installation

    Quote Originally Posted by hcvv View Post
    That is one way to do what is colloquially called "switching to Packman". Another way is doing it in YaST > Software > Software Management. Why do you try to confuse the OP by telling him that he should prefer to do it your way, implicating that the other way is wrong?
    Now I can't switch to Packman in Software Management When I do so, and click on "Validate", a crash occurs, the window closes !

    But I need many other packages from this repository, like libheif. How can I force the switch of these packages ?

    Thanks
    OS: openSUSE Tumbleweed x86_64


Page 2 of 4 FirstFirst 1234 LastLast

Tags for this Thread

Posting Permissions

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