Svkey isn't broken

[Aldair69]

you need to run or give perms to svkey, that way it will be able to write the license in /opt/ also the source is built like this

cd src/source
mkdir build && cd build
cmake .. & make

that will end with these two binaries

[kharovtobi]

thanks for the contribution. however, the problem is that svkey has some problems when installed via PKGBUILD

heres one example

*** buffer overflow detected ***: terminated
SVPatch::launch(): exited = 0, exit = 0, sig = 6`
ERROR from YumeKey
SynthV Studio failed to start properly.

This could be due to a compatibility error with the patch or an installed file. If this recently started happening, please remove any installed voice databases and try again.

ok? 

the problem is either sudo problems because its installed in /opt dir or the license is installed in a wrong directory or a code problem idk
in fact, the license.bin is installed in /opt/SynthVStudioPro/license/ and not /opt/synthv/license/ causing this likely error.

il try to fix it either way probably. thanks for the binaries i've been finding for one btw,

[Aldair69]

thanks for the contribution. however, the problem is that svkey has some problems when installed via PKGBUILD

heres one example

*** buffer overflow detected ***: terminated
SVPatch::launch(): exited = 0, exit = 0, sig = 6`
ERROR from YumeKey
SynthV Studio failed to start properly.

This could be due to a compatibility error with the patch or an installed file. If this recently started happening, please remove any installed voice databases and try again.

ok? 

the problem is either sudo problems because its installed in /opt dir or the license is installed in a wrong directory or a code problem idk in fact, the license.bin is installed in /opt/SynthVStudioPro/license/ and not /opt/synthv/license/ causing this likely error.

il try to fix it either way probably. thanks for the binaries i've been finding for one btw,

I didn't experiment this conflict of yumekey license beeing installed in the wrong place, also someone i know had made a install with makedeb and it worked too. Maybe this is due another package?

[kharovtobi]

I didn't experiment this conflict of yumekey license beeing installed in the wrong place

Yeah i was suprised once.

also someone i know had made a install with makedeb and it worked too.

What do you mean someone did a debian package based of that, if thats the case i want to know about it.

Maybe this is due another package?

No.

btw heres the PKGBUILD with some minor patches that i disabled for the hopes that would fix the license.bin problem
if you want to debug it.

PKGBUILD

pkgname=svkey
pkgver=2.1.0
pkgrel=1
pkgdesc="Yumekey Tool"
arch=("x86_64")
url="https://jinpwnsoft.re/"
license=(
    custom:jinpwnsoft
    AGPL3
)
depends=("synthv-studio")
source=(svkey-2.1.0.zip
#        tool.patch
)
sha256sums=("feb5a5c1ce9fba64fbb79edc1788f94948255117febae9cc9791e9df92637566"
#            "SKIP"
)

build () {
    # Build Files
    cd "$srcdir/svkey-release/source"
#    patch -p0 -i ../../tool.patch
    rm -rf build
    mkdir build && cd build
    cmake ..
    make
}

package () {
    # Install Files
    cd "$srcdir/svkey-release/source/build"
    install -Dm755 svkey_artefacts/svkey "$pkgdir/opt/synthv-studio/svkey"
    install -Dm644 libsvpatch.so "$pkgdir/opt/synthv-studio/libsvpatch.so"
    install -Dm644 ../../LICENSE.txt "$pkgdir/usr/share/licenses/$pkgname/LICENSE"
    # Add link to /bin
    mkdir -p $pkgdir/usr/bin
    ln -s "/opt/synthv-studio/svkey" "$pkgdir/usr/bin/$pkgname"

    # Fix License on wrong dir
    ln -sd "/opt/synthv-studio/" "$pkgdir/opt/SynthVStudioPro"
}

tool.patch

--- tool.cpp	
+++ tool.cpp	
@@ -380,6 +380,7 @@
                      File::SpecialLocationType::commonApplicationDataDirectory);
     return commonDir.getChildFile("SynthVStudioPro")
                     .getChildFile("synthv-studio");
+                    .getChildFile("synthv");
 #endif
   }
 

[Aldair69]

I didn't experiment this conflict of yumekey license beeing installed in the wrong place

Yeah i was suprised once.

also someone i know had made a install with makedeb and it worked too.

What do you mean someone did a debian package based of that, if thats the case i want to know about it.

Maybe this is due another package?

No.

like i said before, i don't need this patch since i don't have any issue with the src. so i can't test it