If I understand correctly, having multiple repos always carries the problem of having different versions of “libraries” - is that what is being talked about with the phrase “system packages” in yast package manager? Should one always switch system packages to some particular repo (like Packman)?
…I’m pretty sure I can get rid of the starred repos because Yast lists nothing installed from them (also libdvdcss, which never changes). I think the starred repos appeared in my list after some “one click install” operation for Signal-Desktop that an internet search found (but the search didn’t return an LEAP repo for that app - I found out about that later…).
That still leaves me with 12 repos - a bit much, but I guess I have a couple of specialty apps available only in specific repos. On the “backports” repo, I have no idea what the “backports” refers to (what’s a “backport”?). THere is an awful lot of packages installed from there.
Which repo should my “system packages” be derived from? Is there a rule for determining this?
Only the last building kernel is delivered in the Repo and the older one is deleted in the Repo, not on my Installation.
I could also search for the other packages…
Also when you install a package by Hand, f.e. an printer driver and this driver is not inside any Repo and will be shown as system package.
I have enabled a directory as Repo, download the driver to that directory and install it with zypper:
Ah, thank you. I’m not sure why it is fairly often mentioned to switch “system packages” to Packman, for instance. That’s what was confusing me - I couldn’t imagine that a repo like Packman had all the kernel stuff for any LEAP distribution. In fact, in Yast, all my repositories give me the option to switch system packages to the repo. I can’t imagine them all having the system packages needed for LEAP.
I think the "switch system packages to this repo (often used when starting to use Packman with the Vendor Switch), is just a way of expressing it. IMHO you should not lay to much meaning in “system packages” there. It means something like “the packages you now have in your system and are also in this repo (Packman in most cases)”
BTW, the repo list as you show them in your first post above is useless. It shows the number, the Alias and the Name of the repos, which are all values local to your system. Of importantce is the URL where they point to. You get that with
zypper lr -d
And please also include such a line with the command (and the prompt) when you copy/paste in between the CODE tags. It such a small move for you and it tells others what you did (and more) to get the output you want to show.
Thank you very much, everyone! So it sounds like other than deleting the unused repos in my list, I should just leave my repo list as-is.
What is a “backports” repo? There’s an awful lot of packages installed from openSUSE:Backports:SLE-15-SP3 - so this is software present in SLE that is “backported” to LEAP - that is, it’s an “official” opensuse repo? (and I shouldn’t necessarily delete it) (akonadi, baloo, chromium, etc., are from that)
I thought so. I think that came in with the use of a one-click-install - but I’m not sure. Since there are a little over 600 packages installed from that repo, how would I go about removing the repo? I’m guessing these packages would switch to another (opensuse LEAP) repo?
[FONT=monospace]kc:~> zypper search -ir 10
Loading repository data...
Reading installed packages...
i+ | akonadi-calendar-lang | Translations for package akonadi-calendar
i+ | akonadi-calendar-tools | Console applications and utilities for managing calendars
i+ | akonadi-calendar-tools-lang | Translations for package akonadi-calendar-tools
i+ | akonadi-contact | KDE PIM Libraries for Akonadi Contacts
i+ | akonadi-contact-lang | Translations for package akonadi-contact
i+ | akonadi-import-wizard | Assistant to import PIM data
i+ | akonadi-import-wizard-lang | Translations for package akonadi-import-wizard
i+ | akonadi-mime | MIME email parser for KDE PIM
i+ | akonadi-mime-lang | Translations for package akonadi-mime
i+ | akonadi-notes-lang | Translations for package akonadi-notes
i+ | akonadi-plugin-calendar | Akonadi calendar integration - serializer plugin
i+ | akonadi-plugin-contacts | Plugins for personal contact handling
i+ | akonadi-plugin-kalarmcal | Plugin to read and write calendar-related alarm data
i+ | akonadi-plugin-mime | MIME email parser for KDE PIM - runtime plugins
<...>
i | openSUSE-2022-42 | Security update for chromium
i | openSUSE-2022-55 | Recommended update for audacity
i | openSUSE-2022-61 | Security update for mc
i | openSUSE-2022-66 | Recommended update for python-attrs, python-configparser, python-importlib
i | openSUSE-2022-68 | Security update for shapelib
i | openSUSE-2022-70 | Security update for nodejs-electron
i | openSUSE-2022-71 | Recommended update for knewstuff, plasma5-desktop
i | openSUSE-2022-75 | Security update for chromium
i | openSUSE-2022-78 | Recommended update for audacity
i | openSUSE-2022-85 | Security update for chromium
i | openSUSE-2022-90 | Recommended update for chromium
i | openSUSE-2022-91 | Security update for chromium
i | openSUSE-2022-102 | Recommended update for python-ipython
i | openSUSE-2022-112 | Security update for chromium
i | openSUSE-2022-114 | Security update for chromium
i+ | oxygen5-icon-theme | Oxygen Icon Theme
i+ | oxygen5-icon-theme-large | Oxygen Icon Theme
i+ | perl-Cpanel-JSON-XS | CPanel fork of JSON::XS, fast and correct serializing
i+ | phonon4qt5-devel | Phonon Multimedia Platform Abstraction
i+ | phonon4qt5-lang | Translations for package phonon4qt5
i+ | phononsettings | Settings Tool for Phonon Multimedia Platform Abstraction
i+ | phononsettings-lang | Translations for package phonon4qt5
i+ | pimcommon | Base package of KDE PIM PimCommon library
i+ | pimcommon-lang | Translations for package pimcommon
i+ | plasma-browser-integration | Helper for the KDE Plasma Browser Integration
i+ | plasma-browser-integration-lang | Translations for package plasma-browser-integration
i+ | plasma-framework | Plasma library and runtime components based upon KF5 and Qt5
i+ | plasma-framework-components | Plasma QML components
i+ | plasma-framework-devel | Plasma library and runtime components
i+ | plasma-framework-lang | Translations for package plasma-framework
i+ | plasma-nm5 | Plasma applet written in QML for managing network connections
i+ | plasma-nm5-lang | Translations for package plasma-nm5
i+ | plasma-nm5-openconnect | OpenConnect support for plasma-nm5
i+ | plasma-nm5-openvpn | OpenVPN support for plasma-nm5
i+ | plasma-nm5-pptp | PPTP support for plasma-nm5
i+ | plasma5-addons | Additional Plasma5 Widgets
i+ | plasma5-addons-devel | Additional plasmoid widgets - development files
i+ | plasma5-addons-lang | Translations for package plasma5-addons
i+ | plasma5-desktop | The KDE Plasma Workspace Components
i+ | plasma5-desktop-emojier | Selection window for emoji text input
i+ | plasma5-desktop-lang | Translations for package plasma5-desktop
i+ | plasma5-integration-plugin | Plugins responsible for better integration of Qt applications in KDE Workspace
i+ | plasma5-integration-plugin-lang | Translations for package plasma5-integration
i+ | plasma5-pa | The Plasma5 Volume Manager
i+ | plasma5-pa-lang | Translations for package plasma5-pa
i+ | plasma5-pk-updates | Software Update Manager for Plasma
i+ | plasma5-pk-updates-lang | Translations for package plasma5-pk-updates
i+ | plasma5-session | KDE Plasma 5 X11 Session
i+ | plasma5-session-wayland | KDE Plasma 5 Wayland Session
i+ | plasma5-workspace | The KDE Plasma Workspace Components
i+ | plasma5-workspace-devel | The KDE Plasma Workspace Components
i+ | plasma5-workspace-lang | Translations for package plasma5-workspace
i+ | plasma5-workspace-libs | The KDE Plasma Workspace Components
i+ | polkit-kde-agent-5 | PolicyKit authentication agent for KDE
i+ | polkit-kde-agent-5-lang | Translations for package polkit-kde-agent-5
i+ | prison-qt5-devel | Development files for prison-qt5, a barcode abstraction library
i+ | prison-qt5-imports | Barcode abstraction layer library - QML files
i+ | purpose | Framework to integrate services and actions in applications
i+ | purpose-devel | Framework to integrate services and actions - Build Environment
i+ | purpose-lang | Translations for package purpose
i+ | python3-ipython | Rich architecture for interactive computing with Python
i+ | ruby2.5-rubygem-rspec-3.10 | Meta-gem that depends on the other components
i+ | ruby2.5-rubygem-rspec-core-3.10 | RSpec runner and formatters
i+ | ruby2.5-rubygem-rspec-expectations-3.10 | API to express expected outcomes of a code example
i+ | ruby2.5-rubygem-rspec-mocks-3.10 | RSpec's 'test double' framework, with support for stubbing and mocking
i+ | ruby2.5-rubygem-rspec-support-3.10 | Common code needed by the other RSpec gems
i+ | sasl2-kdexoauth2 | Cyrus SASL plugin for using Google's XOAUTH
i+ | signon-plugin-oauth2 | Oauth2 plugin for the Single Sign On Framework
i+ | signon-plugins | Plugins for the Single Sign On Framework
i+ | signon-ui | Single Sign On UI
i+ | signond | Single Sign On Framework
i+ | signond-libs | Single Sign On Framework
i+ | syntax-highlighting | Syntax highlighting engine and library
i+ | syntax-highlighting-devel | Syntax highlighting engine and library
i+ | threadweaver-devel | KDE Helper for multithreaded programming
i+ | xembedsniproxy | XEmbed SNI Proxy
i+ | xf86-input-synaptics | Synaptics touchpad input driver for the Xorg X server
i+ | youtube-dl-bash-completion | Bash completion for youtube-dl
[/FONT]
openSUSE Leap 15.3 directly imports packets from this repository:
<link project="openSUSE:Backports:SLE-15-SP3"/>
so they are available as part of normal openSUSE repos. Do you have any specific example of package that is provided by backports but not by openSUSE itself?
And yes, if you are going to ignore question about your repositories I guess further discussion makes no sense.
The current list of repos has 3 additions. No modifications have been made but the alias in the second column and “mirrorcache-eu” replacing “download” in the URI:
**Leap-15-3:~ #** zypper search --details --match-exact vlc.x86_64
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+------+---------+----------------------+--------+----------------------------------------
i+ | vlc | package | 3.0.16-pm153.2.6.2 | x86_64 | packman
v | vlc | package | 3.0.17.3-lp153.2.3.1 | x86_64 | Hauptaktualisierungs-Repository
v | vlc | package | 3.0.16-bp153.2.3.1 | x86_64 | Update repository of openSUSE Backports
v | vlc | package | 3.0.16-bp153.2.3.1 | x86_64 | Haupt-Repository
**Leap-15-3:~ #**
vlc is installed from repo packman. A higher version is available, but packman has higher priority:
**Leap-15-3:~ #** zypper in --dry-run vlc
Loading repository data...
Reading installed packages...
'vlc' is already installed.
There is an update candidate for 'vlc' from vendor 'openSUSE', while the current vendor is 'http://packman.links2linux.de'. Use 'zypper install vlc-3.0.17.3-lp153.2.3.1.x86_64' to install this candidate.
There is an update candidate for 'vlc', but it comes from a repository with a lower priority. Use 'zypper install vlc-3.0.17.3-lp153.2.3.1.x86_64' to install this candidate.
Resolving package dependencies...
Nothing to do.
**Leap-15-3:~ #**
Yes, I know the installer is VERY wise. This is one reason I often reinstall Opensuse rather than spend a ton of time trying to troubleshoot things (and usually failing). I guess I was sort of hoping that, in this instance, there might be a Yast/zypper/rpm subsystem I could trigger which would help me move packages out of the offending repos toward standard repos, then delete them.
I was hoping that, because operating systems nowadays have a lot of wisdom and intuition built-in, but there are still various classes of Gurus, Lord High Fixers, and Wizards that we hacks/hackers rely upon. http://foldoc.org/wizard And, I guess, some of us are just naturally dense. I’ve been exclusively an opensuse “hack” since about 2002 both at work and on my home computers. Of course, this is the first time I’ve gotten stuck with some weird repos from a one click install - hence the failure of my hack-abilities.
