Bug report: vix install: minisign verification failed

[ntung]

Description

Below is the way I tried to install vix

curl -fsSL https://vixcpp.com/install.sh | bash
vix install: repo=vixcpp/vix version=v1.36.3 os=linux arch=x86_64
vix install: downloading: https://github.com/vixcpp/vix/releases/download/v1.36.3/vix-linux-x86_64.tar.gz
vix install: trying sha256 verification...
vix install: sha256 ok
vix install: trying minisign verification...
vix install: minisign verification failed

Steps to reproduce

1. Run curl -fsSL https://vixcpp.com/install.sh | bash
2. Input: nothing
3. Output or error: as I left above

Expected behavior

What should have happened.

Actual behavior

What actually happened.

Environment

• OS: MacOS Tahoe 26.3 and Rocky Linux 9
• Compiler:
• Vix version:

Logs / sanitizer output

Paste relevant logs (ASan / UBSan / build logs).

[GaspardKirira]

Thanks for the detailed report and for testing on both macOS and Rocky Linux.

From your logs:

• sha256 verification succeeded
• minisign verification failed

This indicates the archive integrity is correct, but the signature verification step failed.

I’m currently investigating:

• minisign version compatibility
• public key resolution inside the installer
• cross-platform behavior differences

As a temporary workaround, if minisign is installed locally, you can try removing it and rerunning the installer since sha256 verification already passed.

I’ll update this issue once I identify the root cause.

[GaspardKirira]

Thanks again for the report.

Root cause identified: the installer was verifying minisign using a different public key than the one actually used to sign the release artifacts.
As a result, sha256 verification succeeded but minisign verification failed.

The installer has now been updated to use the correct release signing key.
I’ve tested the fix on Linux and macOS and minisign verification now succeeds:

sha256 ok
Signature and comment signature verified
minisign ok

Please try again with:
curl -fsSL https://vixcpp.com/install.sh | bash

and let me know if everything works on your side.
Thanks for helping improve Vix.

[ntung]

Thank you for your swift action!
However, could you support me another try? Please check the following logs on my Rocky Linux.

[root@tung ~]# curl -fsSL https://vixcpp.com/install.sh | bash
vix install: repo=vixcpp/vix version=v1.37.0 os=linux arch=x86_64
vix install: downloading: https://github.com/vixcpp/vix/releases/download/v1.37.0/vix-linux-x86_64.tar.gz
vix install: trying sha256 verification...
vix install: sha256 ok
vix install: trying minisign verification...
Signature and comment signature verified
Trusted comment: timestamp:1771929604	file:vix-linux-x86_64.tar.gz	hashed
vix install: minisign ok
vix install: installing to: /root/.local/bin/vix
vix install: installed, but running 'vix --version' failed (PATH or runtime issue)
vix install: done
[root@thenguyens ~]# vix --versio
vix: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by vix)
[root@tung ~]# vix --version
vix: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by vix)

[GaspardKirira]

Thank you for the detailed logs.

The installation itself completed successfully.
The issue is related to your system’s libstdc++ version.

GLIBCXX_3.4.30 not found

This means your Rocky Linux environment provides an older libstdc++ (GCC runtime) than the one used to build the Vix binary.

Vix v1.37.0 was compiled with a newer GCC that requires GLIBCXX_3.4.30.

You have three possible solutions:
Upgrade your system GCC / libstdc++ (recommended if possible).
Install a newer GCC via devtoolset and ensure it is used at runtime.
Build Vix from source on your machine:

git clone https://github.com/vixcpp/vix.git
cd vix
cmake -B build -S .
cmake --build build

We are also considering providing a more backward-compatible build in future releases to improve support for older enterprise distributions like Rocky Linux.

Let us know which Rocky version you are running (e.g. 8.x or 9.x), and we can advise more precisely.

[ntung]

It never works on my different environments. I hesitate to change a lot in my Linux machine, so I decided to go with docker images. Eventually, I can install it on a Docker container ubuntu:22. However, I run into the other bugs when running the hello world program.

root@2191b9e7275d:/tmp/vix/build# ./vix run /work/main.cpp 
-- The CXX compiler identification is GNU 11.4.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Error at CMakeLists.txt:53 (find_package):
  Could not find a package configuration file provided by "Vix" with any of
  the following names:

    VixConfig.cmake
    vix-config.cmake

  Add the installation prefix of "Vix" to CMAKE_PREFIX_PATH or set "Vix_DIR"
  to a directory containing one of the above files.  If "Vix" provides a
  separate development package or SDK, be sure it has been installed.


-- Configuring incomplete, errors occurred!

  ✖ Script configure failed.

This fails on both my MacOS and Rocky Linux 9.

Bear in mind that it takes minutes to build from source. Also, missing libraries are also difficult to figure out.

[GaspardKirira]

Thank you for your detailed feedback.

The error you’re seeing inside Docker is not related to your hello world program.
It happens because you are running ./vix directly from the build directory.

When Vix is built that way, it is not installed as a CMake package, so find_package(Vix) cannot locate VixConfig.cmake, which causes the configuration failure.

To fix this cleanly inside your Ubuntu 22 container, please build and install Vix with the install target enabled:

apt-get update
apt-get install -y git cmake ninja-build build-essential

git clone https://github.com/vixcpp/vix.git
cd vix

cmake -S . -B build -G Ninja \
  -DCMAKE_BUILD_TYPE=Release \
  -DVIX_ENABLE_INSTALL=ON

cmake --build build -j
cmake --install build --prefix /opt/vix

export PATH="/opt/vix/bin:$PATH"

vix --version
vix run /work/main.cpp

The key step is cmake --install, which installs the required CMake package files (VixConfig.cmake). Without that step, vix run cannot resolve the Vix package.

This does not modify your host system and works cleanly inside Docker.

If this still fails, please share the full output and we will investigate further.

We are also working on improving the installation experience to better support enterprise distributions like Rocky Linux.

Thank you again for testing across multiple environments.