What is Reddit's opinion of
Yay?
From 3.5 billion Reddit comments
60 reviews of this app found across Reddit:
Current yay is not compatible with pacman-5.2 and new yay is not compatible with pacman-5.1.
You need manual intervention to remove yay, update pacman then install the newest yay.
The yay AUR package is not being updated until pacman-5.2 hits core. So you either have to:
- wait
- build yay from https://github.com/Jguer/yay-PKGBUILD
- use yay-git
eyyy hell yeah man welcome! im also a linux noob who came to arch. had a solid week in pop os before i ditched lol.
as a noob there are a couple tips i would give from my own experience, which i will admit is very little.
1: get Yay or another AUR helper. not a GUI based one, but a solid terminal one that is easy to understand. you can get a GUI one too, but the terminal ones seem to be the most stable. they are helpful for installing stuff you want without messing up other things.
2: to go your pacman.conf and enable parallel downloads and the multilib repo if you want steam or any other programs that might need some 32 bit support.
3: always a good idea to get timeshift or another backup utility and backup your system before you go too crazy with installs or updates.
ill post some more if i think of any others lol. also idk some people may disagree or have better tips, i am not super experienced as i said earlier.
Not gonna lie, pacman/yay isn't exactly intuitive, and I didn't make heads or tails of the actual documentation. at first. Basically, the important parts are:
S - Sync (add if it's not there, reinstall if it is)
R - Remove
U - Upgrade (though S sorta does that anyway)
followed by secondary options:
Sync:
s - search (shows matching packages instead of installing)
u - systemupgrade
y - refresh (grab the latest releases files)
Remove:
s - recursive (remove anything that depended on this package, if it's not longer needed)
c - cascade (remove anything that also depended on this package, no matter what depends on it ) ; much more aggressive, much less safe.
While these options apply to arch's pacman, they also apply to the most common, current AUR helper, yay.
There is a yay-bin, btw. I usually use yay to bootstrap paru on fresh install: curl -L -O https://github.com/Jguer/yay/releases/download/v11.0.2/yay_11.0.2_x86_64.tar.gz && tar -xaf yay_11.0.2_x86_64.tar.gz && yay_11.0.2_x86_64/yay -Suy paru. You could also install yay-bin instead of paru so you won't need Rust/Go toolchains at all.
First of all, you should probably not use yaourt; It has been unmaintained since quite a while. You may want to use a newer wrapper like yay.
And don't worry about yay/yaourt not recognizing bedrock, it really doesn't need to do that. They work just fine in their Arch strata on their own without doing anything special.
If you want to compile yay then just go ahead and do it, but don't forget to use "strat -r" for building software.
Also a little tip for experimenting with new stuff. If you're uncomfortable with doing something because it could negatively affect your system, why not copy the existing strata and try the change there first. If something goes wrong you can simply delete this strata and try again. One of the many lovely features of bedrock Linux.
yay has an option sudoloop:
> Loop sudo calls in the background to prevent sudo from timing out during long builds.
You can also permanently set this option in $HOME/.config/yay/config.json (set "sudoloop": true, in the corresponding line).
Using this option is quite risky, though:
> This is a really bad idea, as sudo credentials are cached by the TTY and if you walk away from the computer while yay is running, another person can come by, CTRL+C the running program, and gain access to a sudo session.
Alternatively, you could also change the sudoers config to increase the timeout, or allow for more retries, e.g. run visudo and modify it like this:
Defaults passwd_tries=3, passwd_timeout=60
This will prevent the sudo password prompt from expiring for 1 hour three times, so you should have a total of 3 hours to get back to yay.
If it's based on Arch Linux, get an AUR package manager like https://github.com/Jguer/yay then do yay -s minecraft-launcher
There's also 3rd party clients like LunarClient and Badlion that have a direct AppImage (like an Exe) for Linux
I don't have a lot of info on differences but anecdotally I used packer for quite some time before recently switching to yay. I love the experience and features of yay. It removes a lot of manual fiddling and asks me all the right questions about PKGBUILDs, whether I want to upgrade individual packages and that type of stuff.
If you are using arch or arch based distro then it is available in AUR.
Here is the archwiki page for that.
What I did is installed yay and then yay -S spotify.
Well, pacman --ask has been added to the potentially harmful commands yesterday, and there is still discussion going on to find better wordings for "native pacman", see e.g. https://wiki.archlinux.org/index.php/Talk:AUR_helpers#Proposal
It's an iterative process with almost always positive consequences for the resulting software, see e.g. https://github.com/Jguer/yay/issues/490 or https://github.com/polygamma/aurman/commit/088c09f0b57633db65973b396fc482d0d590c030
I think it's still under active development. Though I remember reading something like what you thought, as well, about the project being abandoned...
Maybe it was some other AUR helper we're thinking of, or there was a decision to discontinue it but it was reversed?
Latest commit was 17 hours ago
Go to here to see the GitHub page, but here's a copy paste of the commands -
pacman -S --needed git base-devel
git clone https://aur.archlinux.org/yay.git
cd yay
makepkg -si
It's just installing yay like it would any other package. After it's installed, you can download AUR packages with yay -S (name) like you would any other package, and it'll automatically download dependencies and build the package.
It's been really good. This project has been in the works on and off over the past 1.5 years. There had been a bunch of features I had been eyeing in rust for a long long time.
One is an #ifdef equivalent. With go I had to maintain two branches for pacman and pacman-git compatible code. Both in the go-alpm and yay repo. It was very annyoying.
Another is proper generics. In yay I had to implement my own stringset type. Because there is none in the stdlib. And worst of all it only works for strings. We actually define some other ad hoc sets elsewhere in the code.
The ergonomics, tooling and ecosystem I find to be a lot better in general.
Personally I feel the AUR (Arch User Repository) is the best part.
You can find virtually every utility you can think of in there.
There is no official tool to install packages from the AUR, however, which is kind of a pain point in my opinion.
I personally use yay: https://github.com/Jguer/yay
For me points 1 and 3 are the real benefits for Arch. Particularly 1. No other distro has anywhere near as good a system for installing unofficial packages. Then point 3 is great because, whenever I was using a non-rolling distro, I kept getting left behind when new software versions came out and had to wait for the next release (or the one after that), or I had to manually install and manage the updates. Points 1 and 3 combined really do mean whether official or unofficial, you’ve always got the latest software available, with the latest features and latest security updates.
A quick tip for when (!!!) you install Arch. Also install yay - the first time it is a bit manual in the sense you need to go to the github page and follow instructions there. But then after that it’s completely automated and you can use yay to upgrade/install/remove both packages in the official Arch repositories and also the AUR packages. It’s really easy. (But a second tip - do play around a bit with the official package manager, pacman, just so you’re familiar with it too).
> I could do both since I wanted to clean up both pacman and yay as well.
For the purpose of listing unneeded packages, there is no distinction between a package installed through pacman and one installed through yay. In fact, other than -Qu all yay -Q... commands are passed directly to pacman.
https://github.com/Jguer/yay/blob/5647aab025a3b4e01c3608ccbba3c2760bcda9c5/cmd.go#L184
>too new to be in any official server distribution repositories
Have you tried Arch Linux? Because this is all being taken care of already over there thanks to the AUR since most packages directly link to the git repo. eg: yay
You can literally just run:
yay -S docker-git
To get the latest docker from github.
https://github.com/Jguer/yay/issues/324
Somewhat hidden, but it turns out that "Out of Date" means that the AUR package has been flagged as out-of-date with the upstream, not that your package is out-of-date relative to AUR.
If you visit the AUR page for the package in question, you can see that it was flagged out of date just today.
The "is newer than" message is specifically meant to apply to the command-not-found package (local and AUR are package locations, not lists of packages), and there's probably no harm in just leaving it as it is--some of my perl packages have been newer than [community] for a while now and I've yet to see any negative effects.
So in summary, the "is newer than" message specifically refers to the command-not-found package, your copy of oh-my-zsh-git is not out of date relative to the AUR (though the AUR is out-of-date relative to upstream), and it seems that everything is working fine with yay, albeit with some really confusing messages.
MergerFS is in the AUR.
You would need to either build it from upstream and maintain it or use a helper like yay.
Github: https://github.com/trapexit/mergerfs/releases
AUR helper: https://github.com/Jguer/yay
MergerFS: https://aur.archlinux.org/packages/mergerfs/
The aur. part of the link means its in the arch user repository.
Just want to shed some light here, as I see it's popped off.
A thread has been posted to the aur-general mailing list at https://lists.archlinux.org/pipermail/aur-general/2022-February/036787.html which discusses the issues that have been found, patches for a fix, and some extras surrounding the situation.
We'll update that thread when these things get rolled out.
As u/chrisjbillington has mentioned, the mentioned `sed` hack will work as a temporary fix; however, be careful as you do not want to update yay through yay until these fixes have been applied; you will end up back at the start.
If you do want to update to a working version, you can run makepkg manually using the [involved yay PR](https://github.com/Jguer/yay/pull/1685)'s branch and I would personally suggest this route over the binary hack.
As the breaker of yay, I do want to apologize to you guys for the inconvenience, and thank you for the quick resolution produced here.
Someone else on GitHub had the same problem. Don't know why, but a slightly modified version of the hack (which uses percent escapes in the URL to pad the string length instead of trailing slashes) seemed to work.
So you might try reverting to an original yay (assuming it's still in yay's own cache):
sudo pacman -U .cache/yay/yay/yay-11.0.2-1-x86_64.pkg.tar.zst
Then doing this sed command instead:
sudo sed -i.bak 's:rpc\.php:r%70%63:g' `which yay`
This also creates a backup /usr/bin/yay.bak in case you need to revert it again, which you might want to delete once things are normal again.
I added AUR support, basically by wrapping yay
Note that yay currently has a temporary bug at this moment caused by the AUR API URL endpoint changing unannounced from "rpc.php" to just "rpc" but my comment at the end of this bug report will do an in-place fix directly on the binary, causing it to work, until it's updated
I added AUR support, basically by wrapping yay
Note that yay currently has a temporary bug at this moment caused by the AUR API URL endpoint changing unannounced from "rpc.php" to just "rpc" but my comment at the end of this bug report will do an in-place fix directly on the binary, causing it to work, until it's updated
`pkg/settings/args.go`, line 30. Remove `.php` and that should fix it.
AUR removed `/rpc.php` endpoint as mentioned here, so every AUR helper that uses it is affected
You can use --editmenu to check PKGBUILD before installing anything. More info to keep it enabled: https://github.com/Jguer/yay/issues/750#issuecomment-949583751.
Yay is still in development.
Looking at git stats, the creator of paru hasn't made many commits to yay since 2019, while yay's creator has continued to make regular commits. So I'd say creating paru and focusing on that hasn't significantly changed yay's progress.
Yay contributors
Try GreenWithEnvy: https://github.com/dankamongmen/GreenWithEnvy
I've never used it myself but looks like it does what you want.
It's available as a flat pack or via the AUR. You can automate installation and updates for AUR packages with yay: https://github.com/Jguer/yay
Or if you'd like to use the flat pack version, you need to install flat pack: https://github.com/Jguer/yay
This is really bad advice. There is almost never a reason for using root account. As root you should visudo to allow group "wheel" to use sudo as described in https://wiki.archlinux.org/title/Sudo and add your user to this group usermod -aG wheel username and log out from root and use sudo **command** when necessary e.g. sudo pacman -Syu. Also AUR helpers are not a must but I would recommend using one. Look into https://github.com/Jguer/yay this one is pretty much like pacman considering options and is also maintained
Yes. The only thing that might be hard is package management, the basics are:
sudo pacman -Syu to update
sudo pacman -S {package} to install a package (search on archlinux.org is what I do)
sudo pacman -Rns {package} to remove a package
Installing stuff from the AUR is a little bit harder, check out the guide on the "yay" GitHub
Yay uses the same syntax as pacman but do not run it with sudo (root).
Now packages on the AUR can be installed easy.
https://github.com/Jguer/yay/graphs/contributors
the paru dev is Morganamilo. he is #2 contributor to Yay, but he is not the maintainer / project owner... his contributions are less than 50% of the project's owner. the bulk of his contributions were in 2019 and earlier. it looks like the project owner has been active through that entire period, continuing on through 2020 and 2021, with a handful or two of other regular contributors...
that's the story of the commit history and github's statistical info, anyway... yay is definitely still usable, not sure that it's effectively dead project. reading through the issue list (which includes feature requests), i don't get the impression the project is effectively dead.
pacman -U something.tar.xz installs a file from your harddrive, just like for example you would download and install a deb file to install chrome on debian. What your command does is 'install the file teamviewer.tar.xz from the current folder' which isn't there. I would recommend looking into how the AUR works and getting an AUR helper like yay (https://github.com/Jguer/yay). This is like the killer feature for arch (in my opinion) because it gives you access to a huge amount of packages without ever having to download anything from the web or manually managing your programs
> I'm guessing due to emmc storage.
youre also on that slow MMC using a fake disk for a VM, emulated and backed by a real disk-image, which is additionally encrypted at rest in your userdata homedirectory. using a fake disk that isnt encrypted, or using a real disk that is, are both going to be faster than that but both still slower than using a straight ext4 partition. putting an ext4 partition on the fastest USB or SDcard storage device you can afford will be plenty fast, even the garbage-tier NVMe in my chromebooks writes at 500MB/second without any additional tweaks. so you need to enable dev-mode, plug in the disk, type sudo cgpt /dev/sda1, make a single partition, sudo mkfs.ext4 /dev/sda1, sudo mkdir /home/fastfiles, sudo mount /dev/sda1 /home/fastfiles && cd /home/fastfiles. wget https://mirror.rackspace.com/archlinux/iso/2021.02.01/archlinux-bootstrap-2021.02.01-x86_64.tar.gz && tar -xzvf *gz && sudo ./bin/arch-chrooot . , gpasswd add a non-root user to the audio/video gid's, su to that user then look up how to install yay then type yay -Ss editor | less , and type /editor, and then /-enter and look through the options. at least you have kdenlive, blind, shotcut, olive, flowblade, chestnut and openshot to try. bring up an accelerated i3 session, and start launching them and tryin them out:
XDG_RUNTIME_DIR=/run/chrome sommelier --data-driver=noop --shm-driver=noop --drm-device=/dev/dri/renderD128 --display=wayland-0 --virtwl-device=/dev/null Xwayland & DISPLAY=:0 i3
and launch them with alt-d. you might also want to bring up a pulseaudio or pipewire server for the audio as some apps are too dumb to try ALSA devices directly
Probably messed up the dependency resolution somewhere. In projects like yay it's easier to mess it up because they essentially reimplement pacman's dependency solver.
>This tells paru to use /bin/doas for sudo commands. This could not be done with yay.
I don't use yay, but according to https://github.com/Jguer/yay/issues/1194 there are probably corresponding parameters.
The "Arch Linux way" would be to not just understand the AUR but the underlying system which make it possible in the first place: The Arch Build System (ABS) which allows to easily package software
https://wiki.archlinux.org/index.php/Arch_Build_System
the ArchWiki page above will link to many other ArchWiki pages like makepkg, PKGBUILD, creating packages or the Arch User Repository (AUR) to further understand it
The "Manjaro way" (or any other Arch Linux derivate distro) would be just say: "Ignorance is bliss" and don't care about all that underlying stuff which is only for nerds anyway and use paru, yay (both provide install instructions) or Manjaros GUI package manager pamac to let them spoon feed AUR packages while they hope it will work because they don't have any clue how to fix it
> the sudo password is requested right after pmm runs doas -u bedrock strat -r artix yay -Sy
yay is hard-coded to use sudo. This aspect has nothing to do with pmm or Bedrock.
Due to yay's... interesting privilege management, pmm has to do privilege changes of its own to support yay. Given a request to use yay, pmm can usually safely assume (1) the system has sudo installed (since it's a dependency of <code>yay</code>) and (2) the user is okay with sudo usage (since if he/she wasn't, he/she wouldn't request yay).
I know there is interest in adding <code>doas</code> support to <code>yay</code>, but it's not there yet. Given this, there was some investigation into generalizing pmm's handling of these things so things are ready on pmm's end once yay's doas support lands. However, it was found to be non-trivial and delayed until Naga, when pmm is likely to be substantially reworked anyways.
Very strange. If I try to install cpu-x with yay -S cpu-x I only get prompted for which version of cpu-x and libcpuid I want and it pulls the rest of the dependencies from the repos.
I'm guessing your isntall is failing because for some reason yay is only checking the AUR for dependencies and not the official repos too. Some packages have variants in both the repos and AUR so yay finds those but others which are only in the repos aren't found.
If you run yay -Syu does it synchronize the package databases before searching the AUR for an upgrade?
EDIT: looks like you aren't alone, there is an issue reported on yay's github page. I'm fully up to date so I wonder why I'm unaffected.
Also, installing Manjaro should be a one day thing xD You just seem to have got unlucky with something. Btw, allowe to recommend <code>yay</code> as a pacman wrapper for the AUR. It can work as a drop-in-replacement and it works flawlessly. 100% you should give it a shot :D
I use yay too. There are a bunch of library packages (ie kicad-footprint) alongside kicad itself. You can just install the package you liked, but you will miss the kicad libraries. I run it on latest arch on a Dell XPS9570 and everything is smooth (eeschema, pcbnew w/ 3D).
have a look here:
and consider, in my own words (!), that Pacman is for the official packages, AUR is for community driven ones (and yay is about those also)
I am in this part of the installation, but when i open lutris there is no LoL shortcut in lutris.. i tried adding my own but i dont know where to point it to..
On Arch you need an AUR package manager (I recommend yay), afterwards you can continue by installing wine-lol-glibc
and wine-lol
. This will take a long time, so be patient.
If you have first followed the steps of the previous method and set abi.vsyscall32
to 0, now is the time to set it back to 1, by running sudo sh -c 'sysctl -w abi.vsyscall32=1'
in a terminal. Otherwise you proceed with the guide.
Once wine-lol
is installed, you need to open up Lutris, right click on LoL, select Configure, then go to Runner options, set "Wine version" to Custom and set /opt/wine-lol/bin/wine
as your "Custom Wine executable". If you do not see this option, enable "Show advanced options." Afterwards disable and then re-enable Esync, Lutris will complain that this version of Wine is incompatible with it, however, this isn't actually the case, so tick "Enable anyway" and press Okay.
After this, start the game and it should work.
Since you run an arch derivative, you can just use the arch user repository package, you can use an aur helper to install it, for example yay, then just type yay -S protonhax In your terminal of choice
>Build Date : Mon 30 Sep 2019 06:25:39 PM AEST
>
>Install Date : Mon 30 Sep 2019 06:25:40 PM AEST
>
>Install Reason : Explicitly installed
There was a bug report for yay on 10/4/19 that said Packages installed as dependencies are marked as explicitly installed. it was fixed but im wondering if this got pulled in as a dependency but tagged wrong there was only a five day gap between your install and the bug report.
bug report: https://github.com/Jguer/yay/issues/1042
I assume you're using pacman to install compton-tryone-git? That won't work, you'll need an AUR helper like yaourt or yay to install from the AUR.
So try building yay from source, and then install the package with:
yay -Sy compton-tryone-git
Not to blame for posting the exact same thing, but to also direct you to more answers on the exact same questions that go into more depth: https://www.reddit.com/r/archlinux/comments/f6y5az/update_spotify/
Or, straight from yay's github page's FAQ section: https://github.com/Jguer/yay/blob/next/README.md#an-out-of-date-aur-packages-message-is-displayed-why-doesnt-yay-update-them
Packages:
Note: ttf-font-awesome is only used for the icon next to the workspaces in my polybar. All other icons are from nerd-fonts-fira-mono.
How to install:
- Package in official repos:
pacman -S ttf-font-awesome - Package in AUR: If you use yay you can run
yay -S nerd-fonts-fira-mono
>Installing AUR packages is stupid easy, just git clone <this> then cd <that> and makepkg -si
Of do it once to install the wonderful yay and then it’s even more stupid easy: yay -S <package>. Plus full system upgrades (official repositories plus AUR) are as easy as yay -Syu.
The most convenient way for you to start with Arch User Repository (AUR) is by installing AUR helper, which can help you with downloading and installing packages via command line.
You can start with Yet Another Yogurt (YAY) by installing it with the following commands:
git clone https://aur.archlinux.org/yay.git
cd yay
makepkg -si
For more relevant information on YAY visit the GitHub repository:
https://github.com/Jguer/yay
Actually AUR is bigger than Ubuntu's repos. It's like a giant PPA database with good maintenance quality. There is a plenty of programs in AUR which you won't find in Ubuntu's repos(polybar, for example, or a patched custom version of Wine, etc.).
Pacman itself if pretty simple to use, for instance, typing sudo pacman -Syyuu is faster than sudo apt update && sudo apt upgrade.
You might want to check yay for installing software from AUR(while it also can install software from main repos), it's available in Manjaro repository. Also check out (yay's github page)[https://github.com/Jguer/yay] for useful flags.
Some highlights:
sudo pacman -Syyuu system update
pacman-Qs *packagename* search for package on your machine
pacman -Ss *packagename* search for package in repository
sudo pacman -S *packagename* download and install package from repository
(Yay accepts all pacman's flags)
yay -Ps print system info
Agree to this, actually I got a new pc ryzen 3600 and RTX 2060 super, with 2K 144hz monitor. I tried ubuntu, linux mint all have issue with auto scaling (Hidpi).
Then I tried manjaro KDE 18.1.0-rc8 (because the stable version have problem booting on 3rd gen ryzen), and all works like a charm; display scaling, nvidia driver, 144hz.
One more thing, recently I discovered yay and it makes installing aur much easier. Thanks manjaro and the community!
warning: generalisations incoming
depends on the distribution you choose.
if you go with Ubuntu, or any other Debian-based distro, you'll find almost everything you need in the built_in/official/main repo. but, you'll notice that program versions are old (they mostly only get updated every release cycle). Ubuntu-based distros have this thing called PPA, which you use when the main repo doesn't have something you need. PPA is an unofficial repo thing, that you set up per every app you miss from the main repo (mostly, there's exceptions as in everything). once the PPA is set up, the app you need van be install the "main repo way", via the same apt get.
if you go with something like Manjaro (based on Arch Linux), you may find it doesn't have some apps that Debian does, but the main repo soon gets updated as authors release new app versions (in Arch case it's usually within days). if something is missing on Arch/Manjaro, there's the holy AUR. Which is like a huge single unofficial repo (that has all sort of weird and old and new and bleeding edge stuff), but the apps get compiled on your PC, and only then get installed (stuff's automated for you), see the https://github.com/Jguer/yay
yes, there are distros based on Ubuntu. which is based on Debian. distroception
I'm probably biased since I use vanilla Arch, but I never understood whats the issue with building an AUR helper
all of them state on their github pages how to install them: https://github.com/Jguer/yay#installation
and later they will update themself, eliminating any manual building
btw. are you sure it's still using yaort? yaort should not be used anymore since it's abandoned since an eternity and lacks a ton of security features like a proper safe building chroot environment
>checking against non AUR git repos? Following git repo links in pkgbuild? Decode version data for comparison, or just update on non matching git head?
If I understand you right yes that is what I meant. That's even been implemented here https://github.com/Jguer/yay/blob/master/vcs.go
Okay so when you press A, yay puts all PKGBUILDs on the editor command line? Does this include .install files and other important stuff?
~~...I could probably check the code but yay has lots of it and I'm lazy.~~
edit: looks like it does only PKGBUILDs: https://github.com/Jguer/yay/blob/0c49f0f7cb80f536da36b1913f5c6647e2930a0e/install.go#L492
edit2: I guess you could pass the output of git ls-files instead, excluding .SRCINFO files. Probably outside the scope of this reddit thread!