[Slackbuilds-users] Wrong md5sum for rav1e

[Alexander Verbovetsky]

On Sat, Feb 17, 2024 at 11:18:03AM +0100, M Wedin wrote:
> I'm trying to install FlightGear. cargo-c compiled and installed ok.
>
> Oversight or foul play?
>
> Found rav1e-0.7.1.tar.gz in /var/cache/sbopkg.
> Checking MD5SUM:
>   MD5SUM check for rav1e-0.7.1.tar.gz ... OK
> Found Cargo.lock in /var/cache/sbopkg.
> Checking MD5SUM:
>   MD5SUM check for Cargo.lock ... FAILED!
>  Expected: 3c8e14548d37d9fd0efad829bb979e76
>  Found:    b4da9f76a4b4fe2fe547be2980f2168c
>
> Do you want to use the downloaded rav1e source:
> Cargo.lock in /var/cache/sbopkg?

There's something wrong with the building process.

rav1e requires cargo-c. Both download source files called Cargo.lock:

https://github.com/lu-zero/cargo-c/releases/download/v0.9.27/Cargo.lock
md5sum: b4da9f76a4b4fe2fe547be2980f2168c

https://github.com/xiph/rav1e/releases/download/v0.7.1/Cargo.lock
md5sum: 3c8e14548d37d9fd0efad829bb979e76

By some reason the building process for rav1e tries to use Cargo.lock
from cargo-c instead of downloading its own Cargo.lock.

It seems an oversight or foul play is involved in
> Found Cargo.lock in /var/cache/sbopkg.

Best regards,
Alexander