Yesterday i read a forum post about wireplumber, searched for it: ok, lets try this package.
When i started installing wireplumber yay tells me its conflicting with installed package “pipewire-media-session”. So i removed this “deprecated” “pipewire-media-session” … great success sound is much clearer now.
Now my question:
Do i have more of these “deprecated” packages . Is there a way to replace them with new packages ( if they exists ).
a Dropped package will be removed from your installation if you update;
the update will check if the package is available in the AUR and use that if it is instead.
Orphan packages (package files no longer referenced by any repositories (or the AUR as far as I know) but remain on the file system and consume disk space) can be listed with:
pamac list --orphans
and removed with:
pamac remove --orphans
There can be 2 packages containing the same software, as you experienced, but that does not make one deprecated/wrong and the other not. You need to use the best one for you. You just can’t have both installed simultaneously.
[john1@manjaro Dokumente]$ yay
[sudo] Passwort für john1:
:: Paketdatenbanken werden synchronisiert …
core ist aktuell
extra ist aktuell
multilib ist aktuell
:: Vollständige Systemaktualisierung wird gestartet …
Es gibt nichts zu tun
:: Durchsuche AUR nach Updates...
:: Durchsuche Datenbanken nach Updates...
-> Pakete nicht im AUR: hardinfo ipw2100-fw ipw2200-fw lib32-libva-vdpau-driver libva-vdpau-driver manjaro-sx-icons nodejs-lts-gallium rmlint vertex-theme
-> **Verwaiste** (nicht gepflegte) AUR-Pakete: gnome-vfs
-> Als nicht aktuell markierte AUR-Pakete: gconf
es gibt nichts zu tun
``
[john1@manjaro Dokumente]$ LC_ALL=C yay
[sudo] password for john1:
:: Synchronizing package databases...
core is up to date
extra is up to date
multilib is up to date
:: Starting full system upgrade...
there is nothing to do
:: Searching AUR for updates...
:: Searching databases for updates...
-> Packages not in AUR: hardinfo ipw2100-fw ipw2200-fw lib32-libva-vdpau-driver libva-vdpau-driver manjaro-sx-icons nodejs-lts-gallium rmlint vertex-theme
-> Orphan (unmaintained) AUR Packages: gnome-vfs
-> Flagged Out Of Date AUR Packages: gconf
there is nothing to do
So the package “verwaist” in german is just an orphaned package
I’m going to be honest with you:
Some of these packaged I’ve never even hear of. Nevertheless, I think your best bet would be to search for each package, because when listed like this, I think they’re gone.For example, lets take the hardinfo package:
$ pamac search hardinfo
i-nex-git 7.6.1.r0.gcd1b78d-4 AUR
System information tool like hardinfo, sysinfo
hardinfo2-git 2.1.17.r1.g6216559-1 AUR
System Information and Benchmark for Linux Systems.
hardinfo2 2.2.4-1 AUR
System Information and Benchmark for Linux Systems.
hardinfo2 2.2.4-1 extra
System Information and Benchmark for Linux Systems.
Here you can see that it doesn’t exist in the repositories, nor in the AUR, as your warning indicates. And if it’s not in the repositories, it’s not system-critical. So in this case you’d remove it:
pamac remove hardinfo
And then you can choose if you want to install hardinfo2 or not. That’ll depend entirely on you:
Orphans are packages that were installed as a dependency and are no longer required by any package.
Tip: Add the pacman -Qdt command to a pacman post-transaction hook to be notified if a transaction orphaned a package. This can be useful for being notified when a package has been dropped from a repository, since any dropped package will also be orphaned on a local installation (unless it was explicitly installed).
A dropped package will not be removed, it just won’t be updated. If dropped packages were removed then any local packages you installed (ie. pacman -U) which didn’t exist in the repo would also be removed.
AFAIK the only packages that may be removed are conflicting packages.
This will happen if you’re using an AUR helper, and the version in the AUR is newer…unless you tell it not to update AUR packages.
Do not make general updates with yay -Syu.
Always split the process and update the core system first with pacman -Syu, then only the aur packages with yay -Sua
Instead of looking for orphans, a better method might be to look for foreign packages, which are installed packages that are not in Manjaro’s repositories:
pamac list --foreign
or
pamac list -m
For example, if I list the orphans on my system, I see a lot of packages that are still in the repos, but are orphans mainly because they were only required for building AUR packages:
pamac list -o
acpica 20240927-1 extra 2.2 MB
blueprint-compiler 0.14.0-2 extra 2.1 MB
boost 1.86.0-3 extra 186.8 MB
ccache 4.10.2-2 extra 1.5 MB
edid-decode-git r720.5332a3b-1 AUR 413.7 kB
libomxil-bellagio 0.9.3-5 extra 612.3 kB
meson 1.6.0-4 extra 13.5 MB
python-babel 2.15.0-1 extra 30.0 MB
python-ordered-set 4.1.0-5 extra 67.2 kB
python-tomli 2.0.1-4 extra 101.1 kB
python-validate-pyproject 0.22-1 extra 354.0 kB
qt5-graphicaleffects 5.15.16-3 extra 547.3 kB
If I delete all of them, the next time one of my AUR packages needs to be rebuilt, some of those orphans will be reinstalled.
However, my foreign package list is quite different:
paru has a way to print ‘packages not found in the AUR’.
It does this during upgrades, but can also be printed as part of its general stats command;
paru -Ps
We can make it a little more directly to the point with something like;
paru -Ps | grep 'not in the AUR' || echo "No installed packages not in the Repos or AUR"
To get a bit meta for a moment…
It seems it may be worth covering some semantics.
This thread title is about ’ “deprecated” packages ’ … and quickly lists an example of pipewire-media-session. Then responses range from orphans to non-default packages to software thats been abandoned by its creator.
So it may be worth covering some similar but differing examples.
Orphans. These are packages installed as a dependency that are currently not required by any other installed package.
Deprecated [Variant 1]. Could refer to packages no longer recommended by Manjaro/Arch or major components of your system (systemd’s recommendations, etc).
Deprecated [Variant 2]. Could refer to packages containing software no longer actively developed. This could have no visible cue anywhere in the package manager.
Deprecated [Variant 3]. Could refer to packages no longer available in the manjaro repositories. This could mean nothing more than that the manjaro maintainers opted to stop packaging it.
Deprecated [Variant 4]. Could refer to packages no longer available through the package manager at all (Repos or the AUR).
Deprecated [Variant 5]. Could refer to packages no longer included with manjaro by default. These will not necessarily be dropped from the repos or AUR or be orphans.
As you can see these are all different scenarios, requiring slightly different approaches to present or manage them.
In our example of pipewire-media-session it is a combination of ‘Deprecated [Variant 1]’, ‘Deprecated [Variant 2]’, and ‘Deprecated [Variant 5]’. Its in the repos, but it is no longer maintained, and is neither suggested by pipewire or Arch nor included with Manjaro by default.
Thank you very much for the clarification. I feel kind of stupid when I’ve got something this common wrong, but Your explanation is perfect, thank you!
"That’s a great observation! I’m glad you’re understanding the connections better and better.
Why combining pacman and yay for system updates can be beneficial:
Prioritizing official repositories: Pacman updates packages from the official Manjaro repositories first. These packages are generally well-tested and offer high stability.
Subsequent AUR updates: Yay then takes care of updating packages from the AUR. Since these packages are often more experimental or require specific customizations, it’s wise to install them after the official updates.
Minimizing conflicts: This sequence reduces the risk of conflicts between packages from the official repositories and the AUR.
Ensuring important updates: Important system updates that are included in the official repositories are thus guaranteed before moving on to the often more complex AUR packages.
An example:
Imagine there’s an important security update for the Linux kernel included in the official repositories. If you only use yay for updates, you could miss this critical update because yay checks the AUR packages first. By combining both package managers, you ensure that all important system components are up-to-date.
Summary:
Pacman: For basic system updates and packages from the official repositories.
Yay: For additional packages from the AUR that are not included in the official repositories.
A possible workflow for a complete system update:
Pacman: sudo pacman -Syu
Yay: yay -Syu
Important:
Order: Keep the order to avoid conflicts.
Frequency: How often you should perform updates depends on your individual needs. Once a week or every two weeks is usually sufficient.
Backup: Before performing major updates, it’s advisable to create a backup of your important data.
Additional tips:
Pamac: If you prefer a graphical user interface, you can also use Pamac to manage both Pacman and yay.
AUR helpers: Besides yay, there are other AUR helpers like paru or trizen. Each has its own advantages.
Do you have any further questions or would you like to know something more specific?"
Mod edit: changed the formatting of the text from preformatted text (used for terminal output) to blockquote (so the text word-wraps, making it much easier to read)
sound is much clearer now.
will happen if you’re using an AUR helper, and the version in the AUR is newer…unless you tell it not to update AUR packages.