You are not logged in.
As in the title - just looking to see if I'm missing something simple. I'm using yay, Terminal output below:
==> Making package: apple-fonts 6-1 (Sun Jul 14 12:31:00 2024)
==> Retrieving sources...
-> Found SF-Pro.dmg
-> Found SF-Compact.dmg
-> Found SF-Mono.dmg
-> Found NY.dmg
-> Found LICENSE.THE-APPLE-SF-PRO-FONT
-> Found LICENSE.THE-APPLE-SF-COMPACT-FONT
-> Found LICENSE.THE-APPLE-SF-MONO-FONT
-> Found LICENSE.THE-APPLE-NEW-YORK-FONT
==> WARNING: Skipping verification of source file PGP signatures.
==> Validating source files with sha256sums...
SF-Pro.dmg ... FAILED
SF-Compact.dmg ... FAILED
SF-Mono.dmg ... FAILED
NY.dmg ... FAILED
LICENSE.THE-APPLE-SF-PRO-FONT ... Passed
LICENSE.THE-APPLE-SF-COMPACT-FONT ... Passed
LICENSE.THE-APPLE-SF-MONO-FONT ... Passed
LICENSE.THE-APPLE-NEW-YORK-FONT ... Passed
==> ERROR: One or more files did not pass the validity check!
-> error downloading sources: /home/jonny/.cache/yay/apple-fonts
context: exit status 1
:: (1/1) Parsing SRCINFO: apple-fonts
V==> Making package: apple-fonts 6-1 (Sun Jul 14 12:31:01 2024)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found SF-Pro.dmg
-> Found SF-Compact.dmg
-> Found SF-Mono.dmg
-> Found NY.dmg
-> Found LICENSE.THE-APPLE-SF-PRO-FONT
-> Found LICENSE.THE-APPLE-SF-COMPACT-FONT
-> Found LICENSE.THE-APPLE-SF-MONO-FONT
-> Found LICENSE.THE-APPLE-NEW-YORK-FONT
==> Validating source files with sha256sums...
SF-Pro.dmg ... FAILED
SF-Compact.dmg ... FAILED
SF-Mono.dmg ... FAILED
NY.dmg ... FAILED
LICENSE.THE-APPLE-SF-PRO-FONT ... Passed
LICENSE.THE-APPLE-SF-COMPACT-FONT ... Passed
LICENSE.THE-APPLE-SF-MONO-FONT ... Passed
LICENSE.THE-APPLE-NEW-YORK-FONT ... Passed
==> ERROR: One or more files did not pass the validity check!
-> error making: apple-fonts-exit status 1
-> Failed to install the following packages. Manual intervention is required:
apple-fonts - exit status 1
Last edited by not_a_kangaroo (2024-07-14 16:14:56)
Offline
Try makepkg instead, that works for me:
~$ pacman -Q apple-fonts
apple-fonts 6-1
~$
And please use code tags when posting terminal output. Thanks.
Last edited by Head_on_a_Stick (2024-07-14 11:48:25)
"The nation-state domesticates the society in the name of capitalism and alienates the community from its natural foundations."
— Democratic Confederalism, Abdullah Öcalan.
Offline
If there is a problem with a user trying to install a package by using yay, the question isn't whether the problem is with the user or the package but rather whether it's with the user, the package, or yay. And a majority of the time, the problem is with yay. Please do not use it.
Though of course if the error persists with makepkg, then show that output here (in code tags as noted above).
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Mod note: moving to AUR Issues
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Try makepkg instead, that works for me:
~$ pacman -Q apple-fonts apple-fonts 6-1 ~$
And please use code tags when posting terminal output. Thanks.
Hi, thanks for this - when using the above command I get back that the package was not found. Am I missing something stupid?
Offline
If there is a problem with a user trying to install a package by using yay, the question isn't whether the problem is with the user or the package but rather whether it's with the user, the package, or yay. And a majority of the time, the problem is with yay. Please do not use it.
Though of course if the error persists with makepkg, then show that output here (in code tags as noted above).
Noted, thanks - I was using yay as I thought the package was a non-core package not found in the standard arch repository looked at by pacman. I'm reasonably new to arch though, am I missing something?
Offline
HoaS showed output that he successfully installed the package. Those commands obviously will not show the package successfully installed on your system as you have not done that yet because attempting to install it with yay failed. While we really can't know yet, I'm suspicious that yay is the source of the problem - so the solution is to not use yay. But you still need to build and install the package!
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
when using the above command I get back that the package was not found. Am I missing something stupid?
No, not at all, I'm just being obtuse (as usual) — that command just indicated successful installation of the package in my system.
But for AUR packages you should always try a manual build with makepkg(8) if the "helper" program fails. The details can be found on the "AUR" page in the ArchWiki.
"The nation-state domesticates the society in the name of capitalism and alienates the community from its natural foundations."
— Democratic Confederalism, Abdullah Öcalan.
Offline
You learn something new every day! I didn't know you could install packages like that. All sorted now, thanks for the help!
Offline