bitwig-studio: update to 5.3.13.

[finnvanhee]

Testing the changes

• I tested the changes in this PR: YES

Local build testing

• I built this PR locally for my native architecture, x86_64-glibc

[finnvanhee]

I don't understand the error messages in the checks:
OCI runtime exec failed: exec failed: unable to start container process: exec: "bash": executable file not found in $PATH
The error appeared on every check, including the linting. Is this some generic error, or does it indicate something in particular is wrong?

[finnvanhee]

Anyway, I revised a few things in the template. The reason why I have to use curl is that Bitwig has some sort of token-based system for downloads, so there is no direct link. If there is a way to improve the behavior of do_fetch() let me know.

[JkktBkkt]

You can use it like so: distfiles="https://bitwig.com/dl/Bitwig%20Studio/${version}/installer_linux/>bitwig-studio-5.3.13.deb", that does download via regular do_fetch and thus checksum verification can be kept.

Does it properly finish packaging for you though? I kept getting SONAME: ld-linux.so.2 <-> UNKNOWN PKG PLEASE FIX! in local attempt just now until I recalled there was a PR with an update.

[JkktBkkt]

revision should be set to 1 on updates, as it's using to differentiate versions more granular than upstream — i.e. there is an issue with the template or build is missing an option, or a patch, etc, but the version from upstream is still used the same. So you increment the revision, add the fix, and xbps will ask user to update it.

You can use xlint from xtools package to check content of templates

[github-actions]

Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it.