Warning about conflict betweeen jack2 and pipewire-jack only when using yay, and I do not actually have jack2 installed

No, you manage system updates with pacman and install/update aur packages without updating the entire system with other managers like yay or paru (yay -S <package> NOT yay -Syu <package>) or you might end up in a situation like OP.

You make sure that your system is up to date with pacman BEFORE you use yay to install new package(s): sudo pacman -Syu

You can check for available aur updates by running yay -Quaq

If you use yay (even without the -Syu) you will update your system in one go (all repositories including the AUR).
If a AUR package is already installed and you use yay -S then as far as I know it will fetch the package from the yay cache and will ask you if you want to rebuild it, the package does not get a update this way, and even if it did like I said that would mean a partial update.

No, look up what y & u means. It has nothing to do with if a package is previously installed or not. It’s exactly the same with pacman.

-S, --sync
         Synchronize  packages. Packages are installed directly from the remote
         repositories, including all dependencies required to run the packages.
         For example, pacman-S qt will download and install  qt  and  all  the
         packages  it  depends  on.  If  a package name exists in more than one
         repository, the repository can be explicitly specified to clarify  the
         package to install: pacman-S testing/qt. You can also specify version
         requirements:  pacman-S "bash>=3.2". Quotes are needed, otherwise the
         shell interprets ">" as redirection to a file.

-y, --refresh
         Download  a  fresh copy of the master package databases (repo.db) from
         the server(s) defined in pacman.conf(5). This should typically be used
         each time you use --sysupgrade or -u.  Passing  two  --refresh  or -y
         flags  will force a refresh of all package databases, even if they
         appear to be up-to-date.

-u, --sysupgrade
         Upgrades all packages that are out-of-date.  Each  currently-installed
         package will be examined and upgraded if a newer package exists.
         A report of all packages to upgrade will be presented, and the
         operation will not proceed without user confirmation.
         Dependencies are automatically resolved at this level and will be
         installed/upgraded if necessary.

I’d say that means previously installed

Can you explain what the concern here is? yay/paru always handle repo packages first.

So if <package> is a repo package, then pacman -Syu <package> and yay -Syu <package> should always be the same. If package is an AUR package then yay -Syu <package> should be equivalent to pacman -Syu && yay -S <package>. I am not seeing how either of those would be problematic.

I only ask because there are a lot of myths that still circulate from the early days of yay when it worked differently than it does today.

If it the package is an AUR package and the version is different than the installed version, yay should build the new package. -Sy is only relevant for repo packages since it updates the repo databases.

So what happens if a dependency is marked as an aur package in the PKGBUILD, with a newer version available when you run yay -Syu?
There is a lot of should in arguments here.

I’m just saying, if you want to cause as little risk to yourself as possible when using aur, and for example don’t want to end up in a situation like OP, following the procedure of letting pacman handle system upgrades is a good practice.

You are all sysadmins on your own systems, and if you want to completely ignore pacman and use an external package manager to handle everything, go ahead, I’m just trying to explain how to avoid things that might cause you a headache.

I have been following this practice for a very long time and have never had any of this kinds of dependency issues (have ran the same rolling release that was installed more than half a decade ago), while seeing a LOT of instances where other package managers being run to do sysupgrades HAS caused issues, OP being a very resent example.
If you let pacman handle sysupgrades and then install packages explicitly with yay you KNOW what package is causing problems and it is a 100 times easier to figure out how to solve the issue.
Do what you want with that information…

The same thing that happens if you run them separately.

I have never seen any evidence that it matters either way. Why do we believe this caused the OPs problem in any way? I see nothing above that proves that out.

What headache does it actually cause though? It just feels like myth and FUD without anything to back it up.

I have been helping people on Linux for a very long time now and I have seen issues like the above when using pacman or yay. I have seen no evidence over a large sample set that it makes any difference either way.

Again, repo packages run first and these types of issues almost always while handling the repo updates. I have never seen any instance of using yay/paru making it harder to troubleshoot.

If someone prefers running pacman first, that is totally fine, I don’t see any issues with that practice. However, if we are going to claim that using yay to do updates can cause problems, it would be great to back that claim up with some facts to explain why that is true.

EDIT - Dalto beat me by a few seconds :laughing:. I’ll leave this post up, though. It says the same thing, only differently.

yay is a pacman wrapper; it uses pacman to update repo packages, and when updating it updates repo packages first, then updates AUR packages.

All pacman terminal output is displayed in yay. All of it. There is functionally no difference between running yay (which defaults to yay -Syu) and running pacman -Syu then running yay -Sua to update AUR packages.

That’s for updates; when installing an AUR package, using yay -S packagename is fine as long as the system is fully up-to-date; if not, yay -Syu packagename is the better choice, as it will update all repo packages before installing the AUR package.

When installing any package - from the repos or from the AUR - you should only do so with a fully up-to-date system. Hence, using -Syu instead of -S is the smarter way to install a package, whether from the repos or the AUR, whether using pacman or yay (or paru, or trizen, or…).

No you don’t, you end up in a similar situation as OP with questions like “what package is causing conflicts”, while if you manually update the package you NEED to update by gathering information with yay -Quaq you immediately know exactly what is wrong and needs to be fixed.
HUGE difference.

So when he suddenly started following the practice of not relying on yay to update the entire system, it suddenly works is not “proof” for you? Ok buddy, I’m starting to loose interest in trying to explain here.

You want to end up in situations like op, or in dependency hell?

I have, constantly. The only time when something like this were to happen with pacman is either if they use -Syyu or has somehow ended up in a unsyncronized situation.

Did you not read OP?

You guys do whatever you want, it’s your systems and you are the sysadmins.
But do NOT try to convince someone else that “using only yay or paru or pamac (or whatever) is never going to cause issues.” Because that is what you claim here. If you run -Syu with anything other than pacman, you might as well stop using pacman altogether.

I’m done arguing about this nonsense.

Sorry, but this is not true.

They are still done separately. If you manually do it separately or let a tool do it separately, you can still clearly see the difference.

From reading the above, that does not seem to be what happened here.

In no way does this cause “dependency hell” and there has been nothing presented showing it does. This is just peddling misinformation.

No, you haven’t. This type of thing happens with pacman all the time. Just because it hasn’t happened to you doesn’t mean it doesn’t happen. Almost all these issues happen in the pacman stage of the update.

Again, a human running pacman followed by updating AUR packages produces the same result as a tool first running pacman and then updating AUR packages.

Yes it is, read the manual.

Sure buddy, “not what happened”…

No it doesn’t. Only when people are doing silly stuff like -Syyu when not needed, or even worse, -Syyuu.

That is a PERFECT example that it does not “happen all the time”. I do updates DAILY, and it has NEVER happened to me (or anybody else I know for that matter).
This is not a situation of “it works on my system, hence there is no bug”, it’s about using tools correctly and minimizing risks.

If you do a SYSUPGRADE with pacman, why do ANOTHER SYSUPGRADE with yay then, nonsense.
I repeat, yay -Quaq

I have given advice how to avoid unnecessary headaches, if you want to risk causing yourself trouble, go ahead and keep using yay for sysupgrades.

Sorry, but this makes no sense. Doing -Syyu is not harmful. The reason we recommend not doing it all the time is because it puts unneeded load on the mirrors.

As for-Syyuu, that should bring you in sync with the mirror. This will be a problem if your mirror is not in sync but so could pacman -Syu in that situation.

To be clear, I am not advocating for using -Syyu or -Syyuu for normal updates.

Well, I have supported literally thousands of people over the years and I can assure you that it happens and always during the pacman run.

To be clear, I am not saying that there is any problem with the way you are doing things. It is just not materially different than the thing you are claiming causes risks.

That is not at all what I or @Stagger_Lee stated, it isn’t doing 2 sysupgrades. It does a sysupgrade with pacman and then updates the AUR packages after. It is simply using 1 command instead of 2 commands. The operations are still kept separate. It is just calling pacman for you.