Total Download Size: 68.16 MiB
Total Installed Size: 238.96 MiB
:: Proceed with installation? [Y/n]
:: Retrieving packages…
gendesk-1.0.9-3-x86_64 2.2 MiB 2.20 MiB/s 00:01 [-------------------------------------] 100%
yarn-1.22.21-1-any 3.4 MiB 2.72 MiB/s 00:01 [-------------------------------------] 100%
electron27-27.3.4-1-x86_64.pkg.tar.zst failed to download
Total (3/3) 68.2 MiB 11.7 MiB/s 00:06 [-------------------------------------] 100%
error: failed retrieving file ‘electron27-27.3.4-1-x86_64.pkg.tar.zst’ from arch.hu.fo : The requested URL returned error: 404
error: failed retrieving file ‘electron27-27.3.4-1-x86_64.pkg.tar.zst’ from mirror.hackingand.coffee : The requested URL returned error: 404
error: failed retrieving file ‘electron27-27.3.4-1-x86_64.pkg.tar.zst’ from mirror.rackspace.com : The requested URL returned error: 404
error: failed retrieving file ‘electron27-27.3.4-1-x86_64.pkg.tar.zst’ from archmirror1.octyl.net : The requested URL returned error: 404
error: failed retrieving file ‘electron27-27.3.4-1-x86_64.pkg.tar.zst’ from mirrors.ocf.berkeley.edu : The requested URL returned error: 404
error: failed retrieving file ‘electron27-27.3.4-1-x86_64.pkg.tar.zst’ from ord.mirror.rackspace.com : The requested URL returned error: 404
error: failed retrieving file ‘electron27-27.3.4-1-x86_64.pkg.tar.zst’ from dfw.mirror.rackspace.com : The requested URL returned error: 404
error: failed retrieving file ‘electron27-27.3.4-1-x86_64.pkg.tar.zst’ from iad.mirror.rackspace.com : The requested URL returned error: 404
error: failed retrieving file ‘electron27-27.3.4-1-x86_64.pkg.tar.zst’ from mirror.lty.me : The requested URL returned error: 404
error: failed retrieving file ‘electron27-27.3.4-1-x86_64.pkg.tar.zst’ from mirror.theash.xyz : The requested URL returned error: 404
warning: failed to retrieve some files
error: failed to commit transaction (failed to retrieve some files)
Errors occurred, no packages were upgraded.
→ Failed to install layer, rolling up to next layer.error:error installing repo packages
resolving dependencies…
looking for conflicting packages…
Total Download Size: 62.55 MiB
Total Installed Size: 238.96 MiB
:: Proceed with installation? [Y/n]
:: Retrieving packages…
electron27-27.3.4-1-x86_64.pkg.tar.zst failed to download
error: failed retrieving file ‘electron27-27.3.4-1-x86_64.pkg.tar.zst’ from arch.hu.fo : The requested URL returned error: 404
error: failed retrieving file ‘electron27-27.3.4-1-x86_64.pkg.tar.zst’ from mirror.hackingand.coffee : The requested URL returned error: 404
error: failed retrieving file ‘electron27-27.3.4-1-x86_64.pkg.tar.zst’ from mirror.rackspace.com : The requested URL returned error: 404
error: failed retrieving file ‘electron27-27.3.4-1-x86_64.pkg.tar.zst’ from archmirror1.octyl.net : The requested URL returned error: 404
error: failed retrieving file ‘electron27-27.3.4-1-x86_64.pkg.tar.zst’ from mirrors.ocf.berkeley.edu : The requested URL returned error: 404
error: failed retrieving file ‘electron27-27.3.4-1-x86_64.pkg.tar.zst’ from ord.mirror.rackspace.com : The requested URL returned error: 404
error: failed retrieving file ‘electron27-27.3.4-1-x86_64.pkg.tar.zst’ from dfw.mirror.rackspace.com : The requested URL returned error: 404
error: failed retrieving file ‘electron27-27.3.4-1-x86_64.pkg.tar.zst’ from iad.mirror.rackspace.com : The requested URL returned error: 404
error: failed retrieving file ‘electron27-27.3.4-1-x86_64.pkg.tar.zst’ from mirror.lty.me : The requested URL returned error: 404
error: failed retrieving file ‘electron27-27.3.4-1-x86_64.pkg.tar.zst’ from mirror.theash.xyz : The requested URL returned error: 404
warning: failed to retrieve some files
error: failed to commit transaction (failed to retrieve some files)
Errors occurred, no packages were upgraded.
→ error installing repo packages
error installing repo packages
At this point I wonder if there are files/packages somewhere maybe in cache, or some in temp folder, that will serve no purpose, and maybe reap havoc for a future process. I see it states that no files or packages were upgraded, but does the failed install initiate a cleanup of the install attempt?
From what I see in the output, the whole process was aborted in an error because nothing could be retrieved from the mirrors. So nothing downloaded, installed, upgraded. Nothing broken.
You could however always clean up your package cache from time to time if you so wish:
If your initial inquiry has been answered to your satisfaction and you have resolved your issue, please mark the relevant post leading to the solution as such for the topic to close and for the future generations with similar problem to find the solution more easily.
In case of the contrary, feel free to pose your further questions to the forum.
When you install something from the AUR with yay this is what happens:
yay downloads the PKGBUILD file (a script containing the instructions how to make a package), and the source (either code, or compiled binaries) to ~/.cache/yay. Everything is download there, nothing is installed on your system. Then it checks whether there are any build dependencies, packages necessary to build the package you’re installing. If there are, it installs them, normally.
It then runs the script locally to build a package, the result of which is an archive with an extension .zst. Then this package is installed normally on the system. If there are dependencies for this new package, they are also installed, if not already present on the system.
So, if a package wasn’t built successfully, depending on the point where the build failed, there could be remnants of its build in ~/.cache/yay. You can go in there manually and remove what you don’t want. There could also be unnecessary build dependencies installed, they will be listed as orphans in the printout of pacman -Qdt, and you can remove them with yay -Yc.
Sure. I get it. It wasn t my intention to drop the ball. How I solved the problem was to select a different losslesscut submission in aur. I initially chose, losslesscut-git, (the one that was most reciently updated.) It had the error. When that didn t work I chose (losslesscut-bin). It had no error, so that s what I went with.
Not a very glamorous solution for future generations, but it worked for me. In this case, (for posterity sake), I would refer future generations to the link you provided,
When you install something from the AUR with yay this is what happens:
yay downloads the PKGBUILD file (a script containing the instructions how to make a package), and the source (either code, or compiled binaries) to ~/.cache/yay. Everything is download there, nothing is installed on your system. Then it checks whether there are any build dependencies, packages necessary to build the package you’re installing. If there are, it installs them, normally.
It then runs the script locally to build a package, the result of which is an archive with an extension .zst. Then this package is installed normally on the system. If there are dependencies for this new package, they are also installed, if not already present on the system.
So, if a package wasn’t built successfully, depending on the point where the build failed, there could be remnants of its build in ~/.cache/yay. You can go in there manually and remove what you don’t want. There could also be unnecessary build dependencies installed, they will be listed as orphans in the printout of pacman -Qdt, and you can remove them with yay -Yc.
was more inline with the type of answer I was looking for. All in all though, every response was helpful to one degree or another, so much appreciated everyone.
Yes, it’s safe, but whether you should is a question only you can answer. Go through the list and see if there is anything you want to keep.
You can mark those with
pacman -S --asexplicit <package name>
so they will no longer be listed as orphans.
For example cmake is almost certainly a build dependency of some AUR package. If you remove it, it will get automatically installed the next time you update that AUR package.
It’s normal. Because one orphan can depend on another, so that other is technically not an orphan if something depends on it. But as you remove the orphan, those dependencies become orphans, too.
