Arch Linux

huzzleonliu

Member

Registered: 2023-10-11

Posts: 2

Davinci install shows [Version mismatch]

I'm trying to install Davinci, but the result shows "version mismatch".

yay -S davinci-resolve

Version mismatch
:: (1/1) Parsing SRCINFO: davinci-resolve
Version mismatch
-> error making: davinci-resolve-cannot find package name: [Version mismatch]
-> Failed to install the following packages. Manual intervention is required:
davinci-resolve - cannot find package name: [Version mismatch]

Does anyone know how to fix this problem?

WorMzy

Administrator

From: Scotland

Registered: 2010-06-16

Posts: 12,403

Website

Re: Davinci install shows [Version mismatch]

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.

Stefan Husmann

Member

From: Germany

Registered: 2007-08-07

Posts: 1,391

Re: Davinci install shows [Version mismatch]

I guess the AUR Maintainer made a mistake when he/she uploaded the PKGBUILD to AUR. Make a comment there.

Edit: and as always: do not use yay.

There is an out of date flag.

Last edited by Stefan Husmann (2023-10-12 10:07:20)

huzzleonliu

Member

Registered: 2023-10-11

Posts: 2

Re: Davinci install shows [Version mismatch]

People said that yay is one of the best feature of Archlinux, why not use yay?

loqs

Member

Registered: 2014-03-06

Posts: 18,042

Re: Davinci install shows [Version mismatch]

People said that yay is one of the best feature of Archlinux, why not use yay?

See warning at the top of AUR_helpers.  You are asked to use makepkg directly to ensure the issue is not caused by the use of the helper.

Stefan Husmann

Member

From: Germany

Registered: 2007-08-07

Posts: 1,391

Re: Davinci install shows [Version mismatch]

yay is not a feature of Arch Linux at all, so it cannot one of the best features. In your case you could try to use mksrcinfo to recreate the SRCINFO file.

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 12,926

Re: Davinci install shows [Version mismatch]

makepkg is able to generate .SRCINFO files but doesn't use anything from it.
The vast majority of AUR helpers rely on .SRCINFO and fail if something in / with it is 'not as expected' .

---

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

CYREX

Member

Registered: 2023-12-05

Posts: 1

Re: Davinci install shows [Version mismatch]

It's because the latest version from the server doesn't match the version specified in the PKGBUILD you can change it as well as the checksum manually it fixed the issue for me

Last edited by CYREX (2023-12-06 03:32:41)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 12,084

Re: Davinci install shows [Version mismatch]

That is not a fix in any way. Don't do that.

ThePeach

Member

From: Berlin, DE

Registered: 2014-06-08

Posts: 44

Website

Re: Davinci install shows [Version mismatch]

I'm trying to install Davinci, but the result shows "version mismatch".

yay -S davinci-resolve

Version mismatch
:: (1/1) Parsing SRCINFO: davinci-resolve
Version mismatch
-> error making: davinci-resolve-cannot find package name: [Version mismatch]
-> Failed to install the following packages. Manual intervention is required:
davinci-resolve - cannot find package name: [Version mismatch]

Does anyone know how to fix this problem?

Did you manage to solve the problem? with the latest I'm still getting the same error.

[edit] NVM: I just found out upstream released version 19 and we're still at 18 :-/

Last edited by ThePeach (2024-08-22 09:00:06)

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 12,926

Re: Davinci install shows [Version mismatch]

running makepkg on the DR PKGBUILD just shows :

$ makepkg -Crs
Version mismatch
$

Yay showed misleading output and obscured the real reason for the message .

_useragent="User-Agent: Mozilla/5.0 (X11; Linux ${CARCH}) \
                        AppleWebKit/537.36 (KHTML, like Gecko) \
                        Chrome/77.0.3865.75 \
                        Safari/537.36"
_releaseinfo=$(curl -Ls "$_siteurl")

_downloadId=$(printf "%s" $_releaseinfo | sed -n 's/.*"downloadId":"\([^"]*\).*/\1/p')
_pkgver=$(printf "%s" $_releaseinfo | awk -F'[,:]' '{for(i=1;i<=NF;i++){if($i~/"major"/){print $(i+1)} if($i~/"minor"/){print $(i+1)} if($i~/"releaseNum"/){print $(i+1)}}}' | sed 'N;s/\n/./;N;s/\n/./')

if [[ $pkgver != $_pkgver ]]; then
  echo "Version mismatch"
  exit
fi

It appears the maintainer uses a check to verify if the available version is the same as the one they used when uploading the package and aborts build if the versions don't match.

At the start of the PKGBUILD is a comment that suggests a workaround.

---

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