I’ve been using chaotic-aur for a few packages such as their wine builds. However they duplicate stuff in aur but they don’t update as often as aur.
Currently if there is a package that is more recent in aur than chaotic-aur it won’t update it. I was wondering if anyone knew how I could change this behaviour.
Not sure what you are meaning here - but if the package came from AUR originally, then it updates from AUR regardless of its presence in Chaotic-AUR. I get informed by yay -Qua and update by yay -Sua as appropriate…
For example when trying to install zoom with chaotic-aur enabled I get:
[duncanm@arch Downloads]$ yay -S zoom
resolving dependencies...
looking for conflicting packages...
Packages (1) zoom-5.6.6-1
Total Installed Size: 191.42 MiB
:: Proceed with installation? [Y/n] n
When I disable chaotic-aur I get:
[duncanm@arch Downloads]$ yay -S zoom
:: There are 2 providers available for zoom:
:: Repository AUR
1) zoom 2) zoom-system-qt
Enter a number (default=1):
:: Checking for conflicts...
:: Checking for inner conflicts...
[Aur:1] zoom-5.6.7-1
:: Downloaded PKGBUILD (1/1): zoom
1 zoom (Build Files Exist)
==> Diffs to show?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==>
So chaotic-aur is preventing me getting the latest packages if theirs is older.
I don’t see how it’s a workaround - but then I am constantly aware of updates (separately) for both pacman and AUR - so I know when to run a yay-Sua (which is much more rare for me than a pacman-based update is!). There are any number of ways to keep informed oif update status, including the setting of eos-notifier (which also separates the 2 types) - or a little script that can fire you off the info as it happens (I run mine in a conky, but it could be systemd-time’d and use notify-send for example)
Eos notifier does not inform me if there is an package in aur that is newer than chaotic-aur… it will only inform me when it is updated in chaotic-aur.
Perhaps that package was originally installed from chaotic - it separately informs me as mentioned. I forget (off the top) how to determine where a package was originally sourced, but it should be possible to tell - perhaps by which cache it ‘lives’ in? Pacman’s or yay’s…
Well- that about covers what I know. I run one of chaotic-aur’s mirrors, so I like to decide for myself which versions are sourced where…
If I remember correctly you should have the ability to install a package using the format repo/package. For example you should be able to choose from yay zoom and chaotic-aur zoom using
yay aur/zoom
Or
yay chaotic-aur/zoom
Haven’t tried it in a while but it’s worth the shot. Also I know this doesn’t solve the other problem that you can track version of aur and chaotic-aur and choose which you want easily, but at least you don’t have to disable chaotic-aur everytime you want to install something from aur instead.
Perhaps another workaround could be to create an specific pacman config with chaotic repo called for example pacman-chaotic.conf. Then install or update packages from there by:
The reason this won’t work in this case is that I don’t think pacman tracks the source of the package. So if a package with the same name is in both a repo and the AUR, an AUR helper/pacman will see it as a repo package, not an AUR package.
I don’t think what @dodgypast is trying to do is possible without some way of prioritizing the AUR above certain repos but not others for updates. I don’t know of a helper that does that but there could be one.
I’m not sure what the output there is supposed to be showing - apparently you built the teams package version 1.4.00.13653-1 ?
yay’s -a option specifically queries the AUR. I have tested -Sa locally as I have a local repo with certain packages, and yay -Sa will install the AUR package instead.