Package Details: pianoteq-stage5 5.8.1-2

Git Clone URL: (read-only)
Package Base: pianoteq-stage5
Description: Virtual piano instrument using physical modelling synthesis. Both standalone and plugin versions.
Upstream URL:
Keywords: midi non-free piano pianoteq stage
Licenses: custom
Conflicts: pianoteq5
Provides: pianoteq5
Submitter: Saikia81
Maintainer: Saikia81
Last Packager: Saikia81
Votes: 1
Popularity: 0.202416
First Submitted: 2017-11-02 16:58
Last Updated: 2018-05-01 15:28

Latest Comments

SpotlightKid commented on 2018-04-17 10:03

@Saika81: it seems that a git hook of the AUR repo rejects source files, which are not a URL and are not included in the repo.

You could change the source to "${pkgver//./}.7z", but of course downloading that URL doesn't work outside the browser.

Saikia81 commented on 2018-04-16 12:46

hey @SpotlightKid

thank you for your suggestions, I've implemented them, but am yet unable to push them to AUR. I've run into some trouble pushing the changes, since I'm too busy right now I'll be looking into it later.

if you're curious here is an error log:

remote: error: The following error occurred when parsing commit

remote: error: bf013e5c42af:

remote: error: missing source file: pianoteq_stage_linux_v581.7z

remote: error: hook declined to update refs/heads/master

again, thank you!

SpotlightKid commented on 2018-03-31 12:44

I see several problems with this PKGBUILD:

  • Dependency 'wget' is superfluous.
  • There's a comma in the conflicts list, which should'nt be there.
  • The licence filed should be 'custom'.
  • The space in the the name of the installed binary / VST plugin makes it unnecessary complicated in the shell and can cause problems with launchers, which do not quote filenames properly.
  • $srcdir is used unquoted once, which leads to problems if the path contains spaces.
  • The 'package' function is a bit convoluted, instead of cd'ing all other the place, why not just cd in the unpacked 7zip dir and then use full relative paths from there? In the two for loops, ".../${i##*/}" can be used as the target name.
  • That mucking about with sha256sum and 7zip in the prepare function, just to be able to print a message if the source file is missing, seems a bit convoluted. Why not let makepkg handle the checksum and unpacking? It will print an error if the file is missing anyway.
  • Why stripping the '-stage5' part from the .desktop file name and the documentation directory? Wouldn't that prevent installing packages for Pianoteq 5 and 6 at the same time?
  • Why conflicting with any package named 'pianoteq'? Was there ever a package with that name?
  • The name in the .desktop file should be more human-friendly, e.g. "Pianoteq 5 STAGE".
  • Inconsistent whitespace in PKGBUILD file
  • Empty optdepends is superfluous. Instead 'jack' should probably be in there.

Here's my cleaned-up, simplyfied PKGBUILD:

Saikia81 commented on 2018-03-08 14:12

hey @niezniszczalny,

if you could try to remove all files in the cache: rm -R /home/kujaw/.cache/pacaur/pianoteq-stage5

I don't have any experience with pacaur, so if that doesn't resolve it, maybe try installing it mannualy (I don't expect many update to pianoteq 5 anyway): git clone ssh:// cd pianoteq-stage5 makepkg -sri

Note: if pianoteq fails to start, try starting it from a shell.

niezniszczalny commented on 2018-03-07 12:58

I'm getting an error:

:: Building pianoteq-stage5 package(s)...
==> Making package: pianoteq-stage5 5.8.1-1 (Wed  7 Mar 13:57:16 CET 2018)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Entering fakeroot environment...
==> Starting package()...
install: cannot stat '/home/kujaw/.cache/pacaur/pianoteq-stage5        /src/Pianoteq 5 STAGE/amd64/Pianoteq 5 STAGE': No such file or directory
==> ERROR: A failure occurred in package().
:: failed to build pianoteq-stage5 package(s)