Arch Linux User Repository

The AUR moderators have prohibited mirroring VitalInstaller.deb, so unfortunately the users will now be required to manually download the file on their own from https://vital.audio.

Drop the debian package into the root of the respository.

much better now, well done

I have incorporated most of your suggestions.

1. Zenity may have been removed as a make dependency, but it is still a dependency for the executable itself.

2. I have followed https://wiki.archlinux.org/title/AUR_submission_guidelines#Publishing_new_package_content which is where the gitignore originates. So I will be keeping it.

This package is a giant mess:

1. remove PKGBUILD.old1 and PKGBUILD.old2 from the repository
2. Make sure to read https://wiki.archlinux.org/title/Arch_package_guidelines and https://wiki.archlinux.org/title/PKGBUILD as they contain a lot of hints you should follow before sending packages to AUR, like the variables names that MUST be prefixed by _
3. don't use SKIP for checksums until it's strictly required
4. replace source_x86_64 with source as this package is only for x86-64
5. replace sha512sums_x86_64 with sha512sums as this package is only for x86-64
6. remove all the dead code commented with # and leave the PKGBUILD easy to read
7. please be consistent to use tabs and spaces, set your text editor tab width to 8 to make yourself aware about the general chaos in the PKGBUILD
8. replace file://vital.desktop with vital.desktop as it's included in the repo
9. replace file://vital.png with vital.png as it's included in the repo
10. remove the vital-synth.install file and the reference in the PKGBUILD as its job is automatically done by some pacman hooks
11. remove the zenity dependency
12. if the license file is not available anymore in the archives you should provide a copy of it, grabbing from the website itself
13. change license=('custom') with license=('LicenseRef-EULA')
14. remove entirely .gitignore

They are in the repository itself. Am I not supposed to include them in the sources?

@user981257923 thanks to having followed the advices.

However there's something still not clear to me: why are you asking your users to provide vital.desktop and vital.png files? Where do they could get those files?

Is there a way to make a better error message when the deb is absent?

==> Making package: vital-synth 1.5.5-10 (sex 01 ago 2025 09:55:45)
==> Retrieving sources...
==> ERROR: Unknown download protocol: file
    Aborting...
 -> error downloading sources: /home/luis/.cache/yay/vital-synth
         context: exit status 1


:: (1/1) Parsing SRCINFO: vital-synth
==> Making package: vital-synth 1.5.5-10 (sex 01 ago 2025 09:55:45)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
==> ERROR: Unknown download protocol: file
    Aborting...
 -> error making: vital-synth-exit status 1
 -> Failed to install the following packages. Manual intervention is required:
vital-synth - exit status 1

If you're unsure how to build this package after you manually download (the early access version) deb package from https://vital.audio :

❯ cp Downloads/VitalInstaller.deb .cache/yay/vital-synth
❯ cd .cache/yay/vital-synth
~/.cache/yay/vital-synth❯ makepkg --install
...

@user981257923 Working now. Thx for the quick fix.

@user981257923 Thanks for addressing the "mirroring" issue. However, you shouldn't use a whole zenity prompt / dialog script in prepare for users to select the file's location. This is unnecessary and unexpected (as a user input is now required for the build to proceed).

You can simply put the name of the expected file(s) in the source array (just the name, not the download URL for it) to tell makepkg to look for this file in $srcdir.

Users are still expected to download it themselves manually and put it in $srcdir (the same dir as the PKGBUILD) but that's the common way to handle such sources being a paywall and / or a login wall. See the second paragraph at https://wiki.archlinux.org/title/PKGBUILD#Sources

Looks like package() was failing. I have pushed a fix, can you try it?