| Git Clone URL: | https://aur.archlinux.org/snowflake-client.git (read-only, click to copy) |
|---|---|
| Package Base: | snowflake-client |
| Description: | Snowflake Database command line client (snowsql) |
| Upstream URL: | http://www.snowflake.net/ |
| Licenses: | custom:commercial |
| Submitter: | dcelasun |
| Maintainer: | dcelasun (edapa) |
| Last Packager: | dcelasun |
| Votes: | 3 |
| Popularity: | 0.000504 |
| First Submitted: | 2015-04-27 07:58 (UTC) |
| Last Updated: | 2024-07-25 11:07 (UTC) |
Despite following instructions, it still fails for me as well (not using any VPNs)
==> Verifying source file signatures with gpg...
snowflake-client-1.3.1.bash ... FAILED (the public key 23D808A5B09A9CB34610C0B2630D9F3CAB551AF3 is not trusted)
==> ERROR: One or more PGP signatures could not be verified!
Ah thanks for double checking @dcelasun! It looks like it was an issue that only occurred when I had a VPN enabled, my apologies
@mnussbaum your GPG config must be broken, it works fine for me:
$ gpg --keyserver hkp://keyserver.ubuntu.com --recv-keys 630D9F3CAB551AF3
gpg: key 630D9F3CAB551AF3: "Snowflake Computing (Snowflake Computing Gpg Key) <snowflake_gpg@snowflake.net>" not changed
gpg: Total number processed: 1
gpg: unchanged: 1
It looks like the pinned gpg command fails now:
••• gpg --keyserver hkp://keyserver.ubuntu.com --recv-keys 630D9F3CAB551AF3
gpg: keyserver receive failed: Server indicated a failure
To add the Snowflake GPG keys to your keyring, run
gpg --keyserver hkp://keyserver.ubuntu.com --recv-keys 630D9F3CAB551AF3
printf "trusted-key 630D9F3CAB551AF3\n" >> ~/.gnupg/gpg.conf
@johnportella it seems Snowflake have changed their GPG key with the latest version. I've updated the package to 1.2.24 which has the new key in the PKGBUILD. I'll also update the stickied post.
==> Making package: snowflake-client 1:1.2.23-1 (Tue 28 Mar 2023 04:28:27 PM -05)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found snowflake-client-1.2.23.bash
-> Found snowflake-client-1.2.23.bash.sig
==> Validating source files with sha256sums...
snowflake-client-1.2.23.bash ... Passed
snowflake-client-1.2.23.bash.sig ... Skipped
==> Verifying source file signatures with gpg...
snowflake-client-1.2.23.bash ... FAILED (the public key 13C052DA34A48D2B888E6B0037C7086698CB005C is not trusted)
==> ERROR: One or more PGP signatures could not be verified!
-> error making: snowflake-client
gpg --keyserver hkp://keys.gnupg.net --recv-keys 37C7086698CB005C EC218558EABB25A1
printf "trusted-key 37C7086698CB005C\ntrusted-key EC218558EABB25A1\n" >> ~/.gnupg/gpg.conf
is not working
unzip is a dependency. pgpkey should be added to pacman keyring. This could be added to PKGBUILD: validpgpkeys=('13C052DA34A48D2B888E6B0037C7086698CB005C')
Snowsql includes it's own system libraries, particularly libz for backward-compatibility reason's but doesn't unload those libraries before trying to open a browser, causing the browser to fail to open. If you replace the bundled libraries with your system libraries it will work, until snowsql upgrades itself. The you'll have to do it again. I wrote a script for whenever that happens
#!/usr/bin/env bash
VERSION=$(snowsql --version | cut -d' ' -f2)
LIBS="$HOME/.snowsql/$VERSION"
LIBZ="$LIBS/LIBZ.so.1"
if ! [[ -L $LIBZ ]]
then
mv -v $LIBZ{,-bak}
fi
SYSTEM=$(sudo find /usr -name libz.so* 2> /dev/null | head -n1)
ln -sfv $SYSTEM $LIBZ
I'll update the key, but why is unzip needed?
Pinned Comments
dcelasun commented on 2023-03-28 21:39 (UTC)
To add the Snowflake GPG keys to your keyring, run