Cannot update due to dependency issues

[BIZDIK]

Cannot update my system due to error below.

could not satisfy dependencies:
- removing lib32-libffi breaks dependency 'lib32-libffi' required by lib32-glib2
- removing lib32-pcre2 breaks dependency 'lib32-pcre2' required by lib32-glib2
- removing lib32-libffi breaks dependency 'libffi.so=8-32' required by lib32-glib2

When I try to remove “lib32-glib2”, it cannot remove it due to other dependencies below. It branches out and out and out and goes on and on and on. If you try to remove the first dependency and then the following one and the next one, on and on, I’m afraid to end up breaking the system. Is there any logical solution to this?

Excuse my frustration and ranting and bear with me and humor me for what I’m about to say, but I had to hunt around for information to fix the issues that the prior system update caused, which was about a month ago or so!

Now we have another big system update! And if you don’t mind me asking, what’s up with these constant 2GB or 3GB updates??? It is like changing your underwear 5 times a day unless you keep shi…ting yourself!

And why and why is every big system update a nightmare??? Even if you can update without any dependency issues, it is guaranteed! It is guaran-f…ing-teed!!! that the new update will screw something up in your system and something will not work right! I sh.t you not! As much as I love Manjaro and hate Windows, you cannot help but appreciate certain things about Windows. There I said it!!! I thought I would never say this!!! The 3-letter spy agencies must be having their heyday and mental orgasm, reading this!?!

Anyway, I’m done bit…ching and moaning!!!

Just frustrated with constant nuisance!!!

could not satisfy dependencies:
- removing lib32-glib2 breaks dependency 'lib32-glib2' required by lib32-at-spi2-core
- removing lib32-glib2 breaks dependency 'libglib-2.0.so=0-32' required by lib32-harfbuzz
- removing lib32-glib2 breaks dependency 'libgobject-2.0.so=0-32' required by lib32-harfbuzz

[cscs]

Same as here?

Tried to to update my system and I get this error

could not satisfy dependencies: removing lib32-libffi breaks dependency ‘lib32-libffi’ required by lib32-glib2 removing lib32-pcre2 breaks dependency ‘lib32-pcre2’ required by lib32-glib2 removing lib32-libffi breaks dependency ‘libffi.so=8-32’ required by lib32-glib2

Do the system maintenance (IE - pacnew; IE - remove deprecated [community] repo).

System Maintenance

[Ben]

@BIZDIK

And why and why is every big system update a nightmare?

Manjaro is unstable…

Think of Linux Mint as an image set in stone - and that main image doesn’t get changed until the next LTS base is released.

When you change bricks and components built into the foundation of your house, then you must understand that changing ‘supporting walls’ seriously affects the entire structure of that house - so most updates end up looking like complete distribution upgrades… that’s the only way to make it appear stable.

So we can use snapshots to wind back (because we’re lazy to read BEFORE updating, right?) and read it before posting - do a search, fix the error and move on.

It’s mostly because we’re lazy to read that this happens - but generally I find that the time to fix these issues is often a small price to pay… so I don’t often get past the first page when looking at the announcement page on a big update.

TL;DR
@BIZDIK is the reason that every big system update is a nightmare for @BIZDIK.

[linux-aarhus]

There is some simple rules to ease the frustration

[root tip] [How To] Update Manjaro the smart way

TL:DR Logout Press CtrlAltF4 Log on to the system console Execute command sudo pacman -Syu Execute command pamac update --aur Execute command reboot Manjaro updates Think of the following imaginary situation When you use your system or shortly after login - a message appears - telling you there is updates available. When you click the message Pamac opens with the updates pane listing 100’s of packages ready to download/install on your system. Almost per instinct you click the update now - …

[HowTo] Updating Manjaro as safely as possible

The golden rule — which nobody follows, of course — when using a rolling-release distribution…: Always apply the bundled updates by way of the command line in a tty while completely logged out of your graphical environment, so that no shared libraries will be in use that will be overwritten by the update process. The safest way even would be to cleanly reboot your system first before applying any updates, and to then switch to a tty and run the update process from there without logging into…

[ben75]

You need to remove the community repo from your /etc/pacman.conf

The community repo was deprecated about 2 years ago. Users were advised to remove it then, but of course nobody listens to the suggestions in the announcements thread, causing things to break in the future.

[BIZDIK]

@cscs

Same as here?

could not satisfy dependencies: removing lib32-libffi breaks dependency ‘lib32-libffi’ required by lib32-glib2 removing lib32-pcre2 breaks dependency ‘lib32-pcre2’ required by lib32-glib2 removing lib32-libffi breaks dependency ‘libffi.so=8-32’ required by lib32-glib2

Thanks! That did the trick! I don’t know if you’re a beer drinker or not, but I owe you a bottle of beeeeeeer, bud!!!

[BIZDIK]

@linux-aarhus

There is some simple rules to ease the frustration

TL:DR Logout Press CtrlAltF4 Log on to the system console Execute command sudo pacman -Syu Execute command pamac update --aur Execute command reboot Manjaro updates Think of the following imaginary situation When you use your system or shortly after login - a message appears - telling you there is updates available. When you click the message Pamac opens with the updates pane listing 100’s of packages ready to download/install on your system. Almost per instinct you click the update now - …

The golden rule — which nobody follows, of course — when using a rolling-release distribution…: Always apply the bundled updates by way of the command line in a tty while completely logged out of your graphical environment, so that no shared libraries will be in use that will be overwritten by the update process. The safest way even would be to cleanly reboot your system first before applying any updates, and to then switch to a tty and run the update process from there without logging into…

This is gold! Going forward, I’m doing my updates in TTY.

And another best thing that you can do is; [[HowTo] reboot / turn off your frozen computer: REISUB/REISUO]

[BIZDIK]

@Ben

Manjaro is unstable…

I thought “unstable” was a bad word as in “It is unstable! Don’t use it!”

@Ben

Think of Linux Mint as an image set in stone - and that main image doesn’t get changed until the next LTS base is released.

When you change bricks and components built into the foundation of your house, then you must understand that changing ‘supporting walls’ seriously affects the entire structure of that house - so most updates end up looking like complete distribution upgrades… that’s the only way to make it appear stable.

That’s some great info provided in analogy! I liked how you wrapped it up in that analogy! That was a good one!

One comment though! I hear you and understand what you’re saying, but isn’t it a lot of constant work though? You’re building everything back up again!

In terms of mass system upgrade, everything is fine and dandy “for the most part” unless you have AUR packages installed in your system. AUR packages are a sh…it-show. Good luck with them! If an AUR package is discontinued (no longer available), you’re fu.ked out of some app that you really need. Then what…???

Things are fine for the most part, but not all the time because even a package from official repositories can cause a problem.

After the previous mass update, my second keyboard layout would not work until I deleted “fcitx5”.

Don’t take what I’m saying as a complaint, but as a constructive criticism! Will you?

Flatpaks are not a problem because they are self-contained!

@Ben

So we can use snapshots to wind back (because we’re lazy to read BEFORE updating, right?) and read it before posting - do a search, fix the error and move on.

Hmmm! Not that we’re lazy! It is just that we may have more confidence in Manjaro that everything will work out than it won’t work out. So, some don’t bother reading! Don’t interpret everything in negative terms!

Before each mass update, I save a complete snapshot backup of the whole system, just in case!

Everything in Manjaro (in my computer) set up so perfectly and wonderfully to the point that I don’t want to change a thing! I don’t even dare to reinstall Manjaro from scratch because I wouldn’t know where to start to make it all look and work the way it looks and works as it is now!

So, this brings another question! I know it is a wishful-thinking, but hear me out!
When I get a new computer, would it be possible to slap the TimeShift snapshot on the new computer and expect it to work?

Logically thinking, it would not work on a bare hard drive that has no prior Manjaro operating system installation. Right?

What if I just go ahead and install Manjaro on my brand-new computer first, and then try to slap on the TimeShift snapshot on the new computer next as if to “recover”? Would that work? If it doesn’t…, how would I transfer what I have in this computer to my new computer so that I wouldn’t have to reinstall Manjaro from scratch on the new computer?

[wongs]

@BIZDIK

but isn’t it a lot of constant work though? You’re building everything back up again!

That is why I can never understand people who say that they want a rolling distro just to save time avoiding having to do a fresh install of a limited life release [eg Debian Stable or Ubuntu] every few years.

If you add up all the time spent in 4 or 5 years downloading huge updates every system upgrade (say you do it every 3 - 4weeks), solving any problems that arise from an upgrade, maintaining the system, dealing with pacnew files, etc, that would probably add up to the 2 or 4 hours it takes you to download the latest iso of your distro every 4 or 5 years, freshly installing the new version of [say] Debian and setting everything up again from whatever data backup you had done.

Of course if you say, you also want the latest packages, which you can’t get in Debian stable, you want the benefit of the AUR, you want to learn more about Arch-based systems, then fair enough.

But don’t use Manjaro if you think it is a “blindly click to update” distro, some form of rolling version of Ubuntu.

[D.Dave]

@BIZDIK

You’re building everything back up again!

Is not “You’re”; is the nature of a rolling release distro.
To simplify: Rolling release - Wikipedia