-
Notifications
You must be signed in to change notification settings - Fork 146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switch to Pikaur instead of Yay #992
Comments
I see this was turned into a feature request. In the meantime is there a way I can switch it myself? Thanks |
The config has already covered it: Lines 145 to 149 in aebc035
|
Sorry for the late reply but topgrade stated behaving where the AUR is concerned til today. Keeps wanting to use paru when I though yay was the default if installed. It errored out trying to update prowlarr-nightly-bin. Updating prowlarr using pikaur -S I had no issue. I was wondering if there was any progress on this? Thanks EDIT: Seems to be a Garuda issue. I just used topgrade in Reborn and no issue with it building or installing prowlarr-nightly-bin calling pikaur. |
|
Don't understand what was wrong. Could you please paste your On my machine, it produces: I think maybe topgrade invoked [linux]
# Arch Package Manager to use.
# Allowed values:
# autodetect, aura, garuda_update, pacman, pamac, paru, pikaur, trizen, yay
# arch_package_manager = "autodetect" If that's the case, update |
|
That's it.
[linux]
# Arch Package Manager to use.
# Allowed values:
# autodetect, aura, garuda_update, pacman, pamac, paru, pikaur, trizen, yay
# arch_package_manager = "pacman" into [linux]
# Arch Package Manager to use.
# Allowed values:
# autodetect, aura, garuda_update, pacman, pamac, paru, pikaur, trizen, yay
arch_package_manager = "pikaur" |
OK thanks, but one question I learned in the past that if I don't run garuda-update first and then topgrade more times than not I would get a partial update warning in the systray from Garuda, so besides editing that part of the.toml can I just remove the garuda_update part? Thanks again. |
Maybe you should ask that on Garuda forum since there's no such thing of "partial upgrade warning" on normal Arch Linux installs. As an Arch user, I would say: if you finished all upgrade steps with paru or pikaur successfully, then your system is not in partial upgrade state. However, you can run garuda-update again to check it. |
@Jisu-Woniu, appreciate the help! |
Yea I don't believe it's because there is actually a partial update. I believe it pops up because one or more custom fixes in Garuda isn't grabbed by Topgrade, and to be honest I would expect Topgrade to catch them all. To be honest sometimes I think it's just the particular AUR package. Awhile back I ran into this issue, but it only happened with Sonarr, Radarr, Prowlarr. I only noticed cause I install Aur-Check-Updates and run it before I do any updates, the only time then Topgrade would error out was when one or more of those three had a update. No biggie cause I've gotten in the habit of doing the AUR updates first with Pikaur, then Topgrade, then if I need it Garuda-Update. |
Just add garuda-update to your custom commands, since they run at the end of the updating process. This may be the solution of your scenario. Topgrade works for most people, and you can tell it what you want by using the config file. |
I just ran Topgrade and got the below and would like to know if I can make Topgrade use Pikaur instead of Yay? I prefer Pikaur for my AUR helper anyway. Thanks
The text was updated successfully, but these errors were encountered: