Package Details: snowflake-client 1:1.2.24-1

Git Clone URL: (read-only, click to copy)
Package Base: snowflake-client
Description: Snowflake Database command line client (snowsql)
Upstream URL:
Licenses: custom:commercial
Submitter: dcelasun
Maintainer: dcelasun (edapa)
Last Packager: dcelasun
Votes: 3
Popularity: 0.038594
First Submitted: 2015-04-27 07:58 (UTC)
Last Updated: 2023-03-28 21:38 (UTC)

Pinned Comments

dcelasun commented on 2023-03-28 21:39 (UTC)

To add the Snowflake GPG keys to your keyring, run

gpg --keyserver hkp:// --recv-keys 630D9F3CAB551AF3
printf "trusted-key 630D9F3CAB551AF3\n" >> ~/.gnupg/gpg.conf

Latest Comments

1 2 3 Next › Last »

mnussbaum commented on 2024-01-04 21:49 (UTC)

Ah thanks for double checking @dcelasun! It looks like it was an issue that only occurred when I had a VPN enabled, my apologies

dcelasun commented on 2024-01-04 20:59 (UTC) (edited on 2024-01-04 20:59 (UTC) by dcelasun)

@mnussbaum your GPG config must be broken, it works fine for me:

$  gpg --keyserver hkp:// --recv-keys 630D9F3CAB551AF3
gpg: key 630D9F3CAB551AF3: "Snowflake Computing (Snowflake Computing Gpg Key) <>" not changed
gpg: Total number processed: 1
gpg:                      unchanged: 1

mnussbaum commented on 2024-01-04 20:39 (UTC)

It looks like the pinned gpg command fails now:

••• gpg --keyserver hkp:// --recv-keys 630D9F3CAB551AF3
gpg: keyserver receive failed: Server indicated a failure

dcelasun commented on 2023-03-28 21:39 (UTC)

To add the Snowflake GPG keys to your keyring, run

gpg --keyserver hkp:// --recv-keys 630D9F3CAB551AF3
printf "trusted-key 630D9F3CAB551AF3\n" >> ~/.gnupg/gpg.conf

dcelasun commented on 2023-03-28 21:39 (UTC)

@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.

johnportella commented on 2023-03-28 21:28 (UTC) (edited on 2023-03-28 21:31 (UTC) by johnportella)

==> 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:// --recv-keys 37C7086698CB005C EC218558EABB25A1
printf "trusted-key 37C7086698CB005C\ntrusted-key EC218558EABB25A1\n" >> ~/.gnupg/gpg.conf

is not working

siavoshkc commented on 2022-10-02 16:45 (UTC)

unzip is a dependency. pgpkey should be added to pacman keyring. This could be added to PKGBUILD: validpgpkeys=('13C052DA34A48D2B888E6B0037C7086698CB005C')

cheezsteak commented on 2022-05-06 19:48 (UTC) (edited on 2022-05-06 19:48 (UTC) by cheezsteak)

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)
if ! [[ -L $LIBZ ]]
  mv -v $LIBZ{,-bak}
SYSTEM=$(sudo find /usr -name* 2> /dev/null | head -n1)
ln -sfv $SYSTEM $LIBZ

dcelasun commented on 2021-09-24 04:55 (UTC)

I'll update the key, but why is unzip needed?

niknah commented on 2021-09-24 03:56 (UTC)

This is the key server to use according their web site, the other key had expired. gpg --keyserver hkp:// --recv-keys 37C7086698CB005C

It also needs "unzip" in the dependencies.