You are not logged in.
I am trying to install the AUR package named "davinci-resolve" (not the beta or studio versions) and after skipping the validity checks due to it being outdated, runs into the following error:
:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring [-----------------------] 100%
(1/1) checking package integrity [-----------------------] 100%
(1/1) loading package files [-----------------------] 100%
(1/1) checking for file conflicts [-----------------------] 100%
(1/1) checking available disk space [-----------------------] 100%
:: Processing package changes...
(1/1) installing patchelf [-----------------------] 100%
:: Running post-transaction hooks...
(1/2) Arming ConditionNeedsUpdate...
(2/2) Updating executables in /usr/bin...
==> Making package: davinci-resolve 19.0.3-1 (Sat 04 Jan 2025 06:15:47 AM EST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found DaVinci_Resolve_19.0.3_Linux.zip
==> WARNING: Skipping all source file integrity checks.
==> Removing existing $srcdir/ directory...
==> Extracting sources...
-> Extracting DaVinci_Resolve_19.0.3_Linux.zip with bsdtar
==> Starting prepare()...
~/.cache/yay/davinci-resolve/src ~/.cache/yay/davinci-resolve/src
chmod: cannot access '/home/alvin/.cache/yay/davinci-resolve/src/DaVinci_Resolve_19.0.3_Linux.run': No such file or directory
==> ERROR: A failure occurred in prepare().
Aborting...
-> error making: davinci-resolve-exit status 4
checking dependencies...
Package (1) Old Version Net Change
patchelf 0.18.0-3 -0.24 MiB
Total Removed Size: 0.24 MiB
:: Do you want to remove these packages? [Y/n]
:: Processing package changes...
(1/1) removing patchelf [-----------------------] 100%
:: Running post-transaction hooks...
(1/2) Arming ConditionNeedsUpdate...
(2/2) Updating executables in /usr/bin...
-> Failed to install the following packages. Manual intervention is required:
davinci-resolve - exit status 4
Anyone know what the cause of this may be?
Offline
The PKGBUILD is out of date and needs adjustments .
The aur page for it has a comment by psygreg that provides a diff file with needed changes.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
The PKGBUILD is out of date and needs adjustments .
The aur page for it has a comment by psygreg that provides a diff file with needed changes.
Thanks! I honestly only ever use Yay, so I am not too knowledgeable on actually installing AUR packages and debugging them. I will look at this when I am at my computer.
Offline
honestly only ever use Yay, so I am not too knowledgeable on actually installing AUR packages and debugging them
as I started my journey the same way I suggest reading up on that topic
there's nothin wrong on relying on yay but knowing how to do it manual what yay automates can help when someting breaks
it pretty much just boils down to:
- a convenient search function
- automate download and build - the dependencies are handled by arch's pkgbuild anyway
- dealing with signatures and keys (doing that by hand sometimes can be a bit confusing)
the manual way is just:
git clone <link>
cd <folder>
makepkg -s
sudo pacman -U <package>
the nice thing AUR helpers come in handy when there're aur-dependencies which are dealt with automatically - when going manual one can encounter missing dependencies which have to be resolved first - maybe several times recursively like when the target package relies on some other aur-only package which itself also does depend on yet another one ... this is when an aur helper really shines
the acutal debug often comes down to: figure out if it's a helper problem or a package issue by downloading the source and executing makepkg yourself - if this works that it could be a helper option and maybe another aur-helper could help getting it solved
if the manual makepkg fails then its likely an issue with the package itself
just for fun here's my output (sorry for german - forgot to set LC=C)
[main@main vault]$ git clone https://aur.archlinux.org/davinci-resolve.git
Klone nach 'davinci-resolve'...
Hinweis: Als Name für den initialen Branch wurde 'master' benutzt. Dieser
Hinweis: Standard-Branchname kann sich ändern. Um den Namen des initialen Branches
Hinweis: zu konfigurieren, der in allen neuen Repositories verwendet werden soll und
Hinweis: um diese Warnung zu unterdrücken, führen Sie aus:
Hinweis:
Hinweis: git config --global init.defaultBranch <Name>
Hinweis:
Hinweis: Häufig gewählte Namen statt 'master' sind 'main', 'trunk' und
Hinweis: 'development'. Der gerade erstellte Branch kann mit diesem Befehl
Hinweis: umbenannt werden:
Hinweis:
Hinweis: git branch -m <Name>
remote: Enumerating objects: 525, done.
remote: Counting objects: 100% (525/525), done.
remote: Compressing objects: 100% (416/416), done.
remote: Total 525 (delta 174), reused 452 (delta 108), pack-reused 0 (from 0)
Empfange Objekte: 100% (525/525), 168.22 KiB | 1.57 MiB/s, fertig.
Löse Unterschiede auf: 100% (174/174), fertig.
[main@main vault]$ cd davinci-resolve/
[main@main davinci-resolve]$ makepkg
==> Erstelle Paket: davinci-resolve 19.0.3-1 (So 05 Jan 2025 03:10:33 CET)
==> Prüfe Laufzeit-Abhängigkeiten...
==> Fehlende Abhängigkeiten:
-> qt5-webengine
-> qt5-websockets
-> qt5-quickcontrols2
-> qt5-multimedia
==> Prüfe Buildtime-Abhängigkeiten...
==> Fehlende Abhängigkeiten:
-> patchelf
==> FEHLER: Konnte nicht alle Abhängigkeiten auflösen.
[main@main davinci-resolve]$ makepkg -s
==> Erstelle Paket: davinci-resolve 19.0.3-1 (So 05 Jan 2025 03:10:47 CET)
==> Prüfe Laufzeit-Abhängigkeiten...
==> Installiere fehlende Abhängigkeiten...
[sudo] Passwort für main:
Abhängigkeiten werden aufgelöst …
Nach in Konflikt stehenden Paketen wird gesucht …
Pakete (6) qt5-location-5.15.16+kde+r7-3 qt5-webchannel-5.15.16+kde+r3-3 qt5-multimedia-5.15.16+kde+r2-3 qt5-quickcontrols2-5.15.16+kde+r5-3 qt5-webengine-5.15.18-5 qt5-websockets-5.15.16+kde+r2-3
Gesamtgröße des Downloads: 54,55 MiB
Gesamtgröße der installierten Pakete: 176,96 MiB
:: Installation fortsetzen? [J/n]
:: Pakete werden empfangen …
qt5-websockets-5.15.16+kde+r2-3-x86_64 78,8 KiB 272 KiB/s 00:00 [#######################################################################################] 100%
qt5-webchannel-5.15.16+kde+r3-3-x86_64 73,3 KiB 1832 KiB/s 00:00 [#######################################################################################] 100%
qt5-multimedia-5.15.16+kde+r2-3-x86_64 740,1 KiB 2000 KiB/s 00:00 [#######################################################################################] 100%
qt5-quickcontrols2-5.15.16+kde+r5-3-x86_64 1525,0 KiB 3,55 MiB/s 00:00 [#######################################################################################] 100%
qt5-location-5.15.16+kde+r7-3-x86_64 2,5 MiB 5,72 MiB/s 00:00 [#######################################################################################] 100%
qt5-webengine-5.15.18-5-x86_64 49,7 MiB 31,6 MiB/s 00:02 [#######################################################################################] 100%
Gesamt (6/6) 54,6 MiB 34,3 MiB/s 00:02 [#######################################################################################] 100%
(6/6) Schlüssel im Schlüsselbund werden geprüft [#######################################################################################] 100%
(6/6) Paket-Integrität wird überprüft [#######################################################################################] 100%
(6/6) Paket-Dateien werden geladen [#######################################################################################] 100%
(6/6) Auf Dateikonflikte wird geprüft [#######################################################################################] 100%
(6/6) Verfügbarer Festplattenspeicher wird ermittelt [#######################################################################################] 100%
:: Paketänderungen werden verarbeitet …
(1/6) Installiert wird qt5-webchannel [#######################################################################################] 100%
(2/6) Installiert wird qt5-location [#######################################################################################] 100%
(3/6) Installiert wird qt5-webengine [#######################################################################################] 100%
Optionale Abhängigkeiten für qt5-webengine
pipewire: WebRTC desktop sharing under Wayland [Installiert]
(4/6) Installiert wird qt5-websockets [#######################################################################################] 100%
Optionale Abhängigkeiten für qt5-websockets
qt5-declarative: QML bindings [Installiert]
(5/6) Installiert wird qt5-quickcontrols2 [#######################################################################################] 100%
Optionale Abhängigkeiten für qt5-quickcontrols2
qt5-graphicaleffects: for the Material style
(6/6) Installiert wird qt5-multimedia [#######################################################################################] 100%
Optionale Abhängigkeiten für qt5-multimedia
qt5-declarative: QML bindings [Installiert]
gst-plugins-good: camera support, additional plugins [Installiert]
gst-plugins-bad: camera support, additional plugins
gst-plugins-ugly: additional plugins
gst-libav: ffmpeg plugin
:: Post-transaction-Hooks werden gestartet …
(1/2) Arming ConditionNeedsUpdate...
(2/2) Refreshing PackageKit...
==> Prüfe Buildtime-Abhängigkeiten...
==> Installiere fehlende Abhängigkeiten...
[sudo] Passwort für main:
Abhängigkeiten werden aufgelöst …
Nach in Konflikt stehenden Paketen wird gesucht …
Pakete (1) patchelf-0.18.0-3
Gesamtgröße des Downloads: 0,10 MiB
Gesamtgröße der installierten Pakete: 0,24 MiB
:: Installation fortsetzen? [J/n]
:: Pakete werden empfangen …
patchelf-0.18.0-3-x86_64 103,9 KiB 776 KiB/s 00:00 [#######################################################################################] 100%
(1/1) Schlüssel im Schlüsselbund werden geprüft [#######################################################################################] 100%
(1/1) Paket-Integrität wird überprüft [#######################################################################################] 100%
(1/1) Paket-Dateien werden geladen [#######################################################################################] 100%
(1/1) Auf Dateikonflikte wird geprüft [#######################################################################################] 100%
(1/1) Verfügbarer Festplattenspeicher wird ermittelt [#######################################################################################] 100%
:: Paketänderungen werden verarbeitet …
(1/1) Installiert wird patchelf [#######################################################################################] 100%
:: Post-transaction-Hooks werden gestartet …
(1/2) Arming ConditionNeedsUpdate...
(2/2) Refreshing PackageKit...
==> Empfange Quellen...
-> Lade DaVinci_Resolve_19.0.3_Linux.zip herunter...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 2893M 100 2893M 0 0 29.3M 0 0:01:38 0:01:38 --:--:-- 29.3M
==> Überprüfe source Dateien mit sha256sums...
DaVinci_Resolve_19.0.3_Linux.zip ... FEHLGESCHLAGEN
==> FEHLER: Eine oder mehrere Dateien überstanden nicht die Gültigkeits-Prüfung!
[main@main davinci-resolve]$
so either the PKGBUILD or the source is bad - but they don't match up with eachother - as your output shows some "file not found" it's likely the source got changed since the PKGBUILD was last updated (hence why it's not a good idea to blindly ignore signature fails)
Offline
Alvin21Bon wrote:honestly only ever use Yay, so I am not too knowledgeable on actually installing AUR packages and debugging them
as I started my journey the same way I suggest reading up on that topic
there's nothin wrong on relying on yay but knowing how to do it manual what yay automates can help when someting breaks
Thanks man for all this info! I've honestly let the AUR helpers make up for any knowledge I don't have on how AUR packages work, so I honestly have never even read the arch wiki on it: it is definitely something I need to visit. Also along with the benefits you mentioned, AUR helpers like yay automate updating AUR packages I think, so this is also a big plus for me. Honestly, I do not even read the diff files when updating AUR packages, and I know this is a cardinal sin but I just can't help myself. One day, I will really visit this needed chapter of arch. Thanks for your help, you did clear up some things for me!
Offline
let the AUR helpers make up for any knowledge I don't have on how AUR packages work, so I honestly have never even read the arch wiki on it:
You really need to learn how to build and install manually. Knowing how to fix what a helper breaks will be invaluable at precisely the moment that you are left with a broken system.
Ryzen 5900X 12 core/24 thread - RTX 3090 FE 24 Gb, Asus B550-F Gaming MB, 128Gb Corsair DDR4, Cooler Master N300 chassis, 5 HD (2 NvME PCI, 4SSD) + 1 x optical.
Linux user #545703
/ is the root of all problems.
Offline
You really need to learn how to build and install manually. Knowing how to fix what a helper breaks will be invaluable at precisely the moment that you are left with a broken system.
Definitely, sometimes there's so much to learn I just want to cast these big, important topics til the next day, then the next day, ... I am definitely going to teach myself this soon
Offline
not reading the diffs is nothing to be ashamed of - depending on the package even minor patches can have several 100 diff-lines - and without being involved into a project it would be hard to understand it all anyway
on the other hand: who really read all changelogs after an update of 50+ packages? or even a kernel update?
I onced watched an interview about someone running LinuxFromScratch as a daily driver - with his sole reason not trusting anything he hasn't compiled himself - but I highly doubt that he read through all the changes or even have the required in-depth knowledge in all the different languages or all the gigabytes of millions lines of source code or even device drivers
I did LFS once myself - to keep it short: unless you're a masocistic dev hating yourself but being too pussy to commit suicide - a package manager is an invaluable tool I don't want to miss on even the most basic system
fun fact: the regular LFS doesn't even tools like wget or curl required to independently get updates or additional packages - and they only come in the second half of the additional BeyondLinuxFromScratch and require some additional work to get working to finally end up with a fully self contained system able to fully replicate and update itself
Offline
Fail PKGBUILD !!
==> Iniciando package()...
/home/cristo/.cache/yay/davinci-resolve-studio/PKGBUILD: línea 189: 29555 Terminado (killed) cp -rf "${srcdir}"/squashfs-root/* "${pkgdir}/opt/${_pkgname}"
==> ERROR: Se produjo un fallo en package().
Cancelando...
-> error compilando: davinci-resolve-studio-exit status 4
-> Ha fallado al instalar los siguientes paquetes. Una intervención manual es requerida:
davinci-resolve-studio - exit status 4
Offline
Latest version 19.1.2-1 builds fine in a clean chroot.
Please start a new thread and include the full build output (in english) .
See https://wiki.archlinux.org/title/Genera … s_and_code for info how to get english output.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline