While I updated the Mrs PC about a month ago, I’ve been dragging my heels on my PC and I’m getting stopped by a particularly aggressive dependency issue with the various lib32-* files being removed from the repo’s.
The one that has me a bit stumped is lib32-audit. previously i had a lib32-libcap issue while updating the Mr’s PC and I got around this by updating lib32-libcap from the AUR (which revised the dependencies).
It’s not so simple with lib32-audit as trying to upgrade it from the AUR throws a dependency issue with audit.
About the only way I’ve found where I can get a sudo pacman -Syuw to run without throwing any dependency errors is to update /etc/pacman.conf with IgnorePkg = audit lib32-audit
My assumption is that after this “partial” update I can remove the ignores and update audit normally… and remove lib32-audit.
This feels like a much lower risk plan than attempting something crazy like sudo pacman -Rdd lib32-audit and hoping an update functions afterwards.
Any better suggestions? The package ignore options seems fairly safe as there were no other complaints about anything depending on a specific version of audit.
audit is in the repository and has no dependency on any 32-bit libraries. I would advise you to uninstall the AUR version with its dependencies and then install the repo version instead.
Is there any particular reason to use anything 32bit at all? Probably the only thing i know it requires it is steam. And i cannot imagine the userbase of steam needing audit and vice versa.
both audit and lib32-audit on my system were installed from the manjaro repo’s… last updated ~8 months ago; hence the version dependency issue.
I can’t simply update audit from the manjaro repo’s because that fails the lib32-audit dependency check…
pacman -Qi lib32-audit
Name : lib32-audit
Version : 4.1.2-1
Depends On : audit=4.1.2 lib32-glibc
If that version dependency wasn’t there, this would be so easy.
I can’t simply remove lib32-audit as the current system dependency chain would start tearing things out all the way into systemd files… not doing that.
and I can’t pamac install lib32-audit --no-upgrade to update/break it’s dependencies as it’s checks fail…
Building lib32-audit...
==> Making package: lib32-audit 4.2.1-1 (Mon 05 Oct 2026 01:33:03 AM)
==> Checking runtime dependencies...
==> Missing dependencies:
-> audit=4.2.1
==> ERROR: Could not resolve all dependencies.
despite it knowing…
Resolving dependencies...
Checking inter-conflicts...
To upgrade (1):
audit 4.2.1-1 (4.1.2-1) core
To build (1):
lib32-audit 4.2.1-1 (4.1.2-1) AUR
… I suspect order of operations that trips on the same pacman issue.
So the only way I’ve found to silence/appease the “errors” is via the package ignores… IgnorePkg = audit lib32-audit
I told you to removelib32-audit first — with all of its dependencies — and then install audit from the repo.
If you can’t or won’t do that, then perhaps you should reinstall your system, because right now you’re in an unsupported state, and — I am sorry to have to say this — that is nobody’s fault but yours.
Here I thought I’d found an elegant temporary use of IgnorePkg to save my bacon but apparently sanity checking that idea is a no no worthy of a scolding and ignoring.
I’m obviously no linux expert, but I think I’ve been a fairly respectful Manjaro citizen over the past 5+ years and even managed to help the odd person along the way.
Yes, I did, but instead of doing that, you were coming back with that you can’t install audit from the repo because of the dependency issues with lib32-audit, which was not what I told you to do.
So what that means is that you either didn’t read what I wrote or that you chose to ignore me.
IgnorePkg is for when there is a problem with one or several packages — likewise IgnoreGroup — but not for attempting to fix a system in an unsupported state.
If you are asking for help in fixing an unsupported system, then given that it’s — wait for it — unsupported, you should take the advice of people who know what they’re talking about instead of ignoring them just as you are ignoring packages.
Likewise. But if your toes are that long, then best would be to get a bigger shoe size.
Please notice it is common that Arch removes outdated packages. In such cases the removed packages usually are still available via the AUR and if you enabled the AUR then the package stays on your system. You have to clean up these outdated packages yourself. This is one of the consequences of using the AUR.
Moreover notice that in the Pamac GUI there is clearly stated
All AUR users should be famiilar with the build process.
I wonder whether you are familiar with the build process?
With this you only make things even worse. The outdated package lib32-audit will never be removed and ignoring audit will block updating your system by its (cascading) dependencies. In other words, this is no solution but nonsense.
The solution is to remove lib32-audit and probably if you don’t qualify for being familiar with the build process you also should disable the AUR. If you need packages that are not in the official repos I would recommend to use flatpaks.
Adding lib32-audit to the IgnorePkg in pacman.conf is not necessary.
The lib32-audit has been moved to AUR and - despite the fact it has once been a part of the multilib repo - it is no longer needed or required on a Manjaro Linux system.
Keeping obsolete packages on the system is a recipe for problems down the road, so it is advisable to remove it.
Besides, Audit is one of those things that don’t do much unless properly configured, so uninstalling it all, 32bit and 64bit, won’t hurt.
As said, nothing in the core system is 32bit anymore. So if you are not Steam-ing, you can uninstall it all regardless how many more lib32 dependencies are there.
In any case you will have to investigate and see if there is anything at all that explicitly needs 32bit, everything else is a consequence of this. And also think of cleaning orphans, if you have not until now.
Even pamac has a nice subsection for them in the installed category, right under “foreign”.
Learning is doing what your told without question. It’s not thinking outside the box when necessary, or questioning/testing the “rules”, it’s blind faith in the kool-aid of the ages… because why test the boundaries of anything… boundaries are security… outside boundaries are scary… if that were true, we’d all still be living in caves.
I’m the administrator responsible for my system, until pacman slaps rails on me… and enquiring how to work around the rails just leads to circular arguments about the administrator shouldn’t have let that happen in the first place. Life’s hard, things happen, not everything goes according to some hard’n’fast script. System administrators have to find solutions to problems every day.
In my investigation, here’s how a package manager respects the fact that I’m the administrator, provides options, and some options allow me to disregard the rails if I see fit (knowing there’s a TimeShift / snapshot to go back to)
Problem: 1: the installed libvirt-daemon-driver-libxl-10.2.0-Virt.1699.1111.2.x86_64 requires 'libxenlight.so.4.18()(64bit)', but this requirement cannot be provided
deleted providers: xen-libs-4.18.2_06-2.1.x86_64
not installable providers: xen-libs-4.18.1_02-Virt.1699.856.7.x86_64[Virtualization]
Solution 1: deinstallation of libvirt-daemon-driver-libxl-10.2.0-Virt.1699.1111.2.x86_64
Solution 2: install xen-libs-4.18.1_02-Virt.1699.856.7.x86_64 from vendor obs://build.opensuse.org/Virtualization
replacing xen-libs-4.18.2_06-2.1.x86_64 from vendor openSUSE
Solution 3: keep obsolete xen-libs-4.18.2_06-2.1.x86_64
Solution 4: break libvirt-daemon-driver-libxl-10.2.0-Virt.1699.1111.2.x86_64 by ignoring some of its dependencies
Choose from above solutions by number or skip, retry or cancel [1/2/3/4/s/r/c/d/?] (c):
That seems more like power being in the system administrator’s hands. Not fake authority until the tool blocks you.
I looked up audit briefly enough to learn it’s a userspace package that peers into the goings on of the kernel and therefore is not something critical to the overall health of the system (like toolchain) that would have caused any serious harm by temporarily ignoring it during an update.
But you’ve convinced me. I am the administrator of my system, and I see now that I cannot do that with pacman and will embrace other tools that keep power and authority in my hands.
Learning includes listening to people when they give you useful information.
Pacman didn’t “slap rails on you” it told you there was an issue that you needed to investigate and resolve. Yes the sys admin needs to see what’s going on and find a suitable way to deal with it. Asking here was a good idea but instead of picking out the information you needed, you decided to pick fights and ramble on about some imagined nonsense.
You asked if there was a better way, and we told you there was.
sudo pacman -Rns lib32-libcap
sudo pacman -Syu
Though ideally you’d inspect the dependency tree and figure out what packages require what, etc.
pactree -r lib32-audit
Or you could trace it back using pacman -Qii lib32-audit, pacman -Qii lib32-pam etc
Then you decide what’s needed and what’s not, ie the best way to resolve the issue.
This is a forum, we rely on text and lose tone of voice and body language. That means we need to be careful about how we read things, lest we add in a tone of voice that doesn’t match the authors intent and misinterpret what they say.
Although the topic is closed, for the record and for future by-passers, you have the same 4 options on an arch based system: “solution” 3 is not doing anything, solution 4 is what you chose to do - ignore and break the system, solution 2 is not always applicable like in that case, and solution 1 - remove something, is what we advised you.
But pacman is indeed not so verbose in explaining, one have to know. The “simple” approach with the dependencies - one version of everything, is the main concept in the Arch world. For some it is an advantage, for some disadvantage. In the debian universe one can have different versions of one package installed at the same time, which is the opposite concept. I have no experience with suse and co, although judging by the above it is more like arch in the package management, but more user friendly.