Cannot update, everything fails to satisfy dependencies

Support System Updates
1

First time I’ve run into this, I just reinstalled Manjaro Plasma a few weeks ago and I’ve updated it regularly. I can’t update anything now.

 sudo pacman -Syu                                                                                                                                                                           ✔  8s  
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 multilib is up to date
:: Starting full system upgrade...
warning: nano-syntax-highlighting: local (2020.10.10+10+g1aa64a8-2) is newer than extra (2020.10.10-2)
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing x265 (3.6-1) breaks dependency 'libx265.so=199-64' required by avidemux-core-git
:: installing x265 (3.6-1) breaks dependency 'libx265.so=199-64' required by avidemux-qt5-git

if I --ignore that package the next one will have the same dependency issue and so on. I’ve tried with pamac as well, same issue. I tried updating mirrors and setting to US, still doing it. Any ideas?

Mods marking posts "solved" and locking?
Actualizacion incomoda
2

Those git packages suggest you installed them from the AUR, or they’ve since been deprecated and then moved from the repos to the AUR.

I’d suggest removing both of those avidemux packages (the qt5 version is very likely out of date). You can always reinstall those later if needed.

sudo pacman -Rns avidemux-core-git avidemux-qt5-git

… should suffice. If not, report back.

Cheers! :slight_smile:

5 Likes
3

Reinstall the package.

As said before, remove those packages and it should work.

You should also keep an eye out of for orphans and remove them (carefully). Judging from your post you likely have many orphans installed.

3 Likes
4

Sorry, As I said in the title it was EVERYTHING. x265, qt5-tools, I just posted the output of the next time I ran the command, I should have ignored AUR and posted that output so there was no confusion.

Fortunately I was Googling around and trying stuff and I managed to get the update to run through pamac, unfortunately I didn’t pay much attention to exactly what fixed it.

1 Like
5

This is the issue with posting partial outputs, unfortunately. Had we seen the full log, it may well have helped with the resolution.

All good, though!

Addendum:
I would recommend using Pacman for system upgrades and then using Pamac for any AUR stuff. Safest way, IMHO.

4 Likes
6

Yeah that’s probably a good recommendation for people who has a good amount of AUR Packages installed.

They should use sudo pacman -Syu to evade AUR Updates.
To find out if the updates has problem’s and should later update their AUR Packages.

1 Like
7

Exactly my thoughts … too many people seem to be relying on Pamac for everything, without taking the necessary precautions.

Including --no-aur first in Pamac (if I got that right).

1 Like
8

I was just mention this, not to confuse people:

Because there are still enough people here without using AUR at all or only has installed 1-2 AUR Package’s like i do and are not important for a stable and running OS.

Not on everything yes, i mainly use just the Pamac (GUI) to update and its regularly just works fine… but this wouldn’t be the case if i would rely more on AUR!? :thinking:

Probably yes.

9

I’d still say do system updates first (for me at least, preferably with Pacman), even with only maybe a couple of AUR packages installed, just to make sure those don’t interfere with the upgrade process, I only use GUI for notifications of updates and sometimes (f a small number) to check what those are.

YMMV. :wink:

3 Likes
10

In my personal situation i have only installed 2 AUR Packages: My VPN Software and a Ink checker for my Printer.

I have nothing to worry about this 2 AUR Packages that they interfere in the update process, as long as i clean the Foreign (Orphan/AUR) Packages that showing up from time to time, when the Official Repo Packages are no longer supported.

And as long there is no Plasma7 update coming, im fine to update with the simple Pamac GUI :slight_smile:

1 Like
11

That’s exactly how it should be :100: !

3 Likes
12

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.

14

The package in question is a custom package - and custom packages are unsupported - it is not that some is supported and others not - they are equally unsupported.

Even if they can be build and maintained by yay and pamac - the result is unsupported.

  1. Never maintain repo packages and custom packages in the same run
  2. Remove custom package(s) when they interfere with the sync

After you have succesfully synced your system - you rebuild the package(s) in question.

Then you remove every, every AUR package tha confilicts

That deprives the members trying to help from possibly important information.

3 Likes
Mods marking posts "solved" and locking?
15

I think the problem with this thread was that you guys see something happen often and immediately jumped to that being the issue here. The output I posted probably confused the situation but the point was that that output was the same even if I ignored multiple failed packages it would still fail on the first official package. I assumed that was clear, maybe not.

The problem with that statement is that that package was never in question.
“if I --ignore that package the next one will have the same dependency issue and so on.”

qt5-tools is an official package. AUR packages have to be compiled. I have ZERO problem removing an AUR package that fails, but I will first try to ignore it. If official packages fail (which was the point of this post) then there is an issue. If they advice is just that you should remove every single AUR package regardless, I’m not sure that’s good advice

That deprives the members trying to help from possibly important information.
[/quote]
Only if they didn’t read or believe what I actually SAID. Posting the output of a failed AUR package was probably a bad idea but I iterated in the post that I was ignoring packages one by one when I drew the conclusion that NO packages could update.

This is probably good advice. I have many systems for different reasons. I run alot of AUR because I do have alot of obscure use cases. While it is good advice, it was not the issue here.

16

That git was updated in January. Like I mentioned in the first post, I just installed Manjaro KDE in this machine from Manjaro Gnome so it’s not a package that’s been installed for 10 years. I ran the qt5 version because of a bug in the qt6 version upon recommendation from the author.

That one’s slightly confusing, if you look at the output posted in the OP, that’s exactly what I ran?

I’m also not sure how this turned into a discussion about pamac, I only mentioned that I tried using pamac after pacman failed.

17

Unfortunately that doesn’t always make a difference with AUR stuff; January is half a year ago, so I’d say it needs to be dealt with by the package maintainer.

I would posit that there are a fair few outdated / stale packages in the AUR.

1 Like
18

maybe, but the point was I am using it out of necessity…not laziness. There is a qt6 package, I can’t use it.

1 Like
19

It is always good to revisit Forum Rules - How To Post from time to time.

Ask yourself

  • this question/topic did I ask the smart way?
  • can I improve it to get a better answer?

Further reading: How To Ask Questions The Smart Way

If a recommendation from the author of an application makes your system behave badly on sync then it is bad advise.

You are the system admin and you are free to do what ever you want - but provided a fraction of the facts in your initial topic is only making it harder for yourself and for your fellow members.

A reasonably maintained Manjaro Linux system - synced every 2-4 weeks - will never exhibit the symptoms you describe.

If you are frequently getting the same issue you will have examine the root cause.

If you want help to examine the root cause it is imperative that you supply a complete log - not the parts you deem important.

The statement everything fails to satisfy dependencies with a sample of two packages - adding to the pool is unsupported custom packages - packages which may have a lot of other packages depending on them - it is impossible to provide a meaningful answer.

It is the classic xy problem

The XY problem is asking about your attempted solution rather than your actual problem. This leads to enormous amounts of wasted time and energy, both on the part of people asking for help, and on the part of those providing help.
– https://xyproblem.info

1 Like
20

… and, apparently, this thread had a solution … seriously, additional questions deserve another thread to discuss the ins-and-outs.

It was already explained why an upgrade won’t work if obsolete packages are present and an upgrade is attempted including those AUR packages.