| Git Clone URL: | https://aur.archlinux.org/ventoy.git (read-only, click to copy) |
|---|---|
| Package Base: | ventoy |
| Description: | A new bootable USB solution |
| Upstream URL: | https://www.ventoy.net/ |
| Licenses: | GPL-3.0-or-later |
| Submitter: | Toolybird |
| Maintainer: | Toolybird |
| Last Packager: | Toolybird |
| Votes: | 56 |
| Popularity: | 2.01 |
| First Submitted: | 2023-02-17 20:09 (UTC) |
| Last Updated: | 2026-06-30 07:02 (UTC) |
@Toolybird: That is odd. I'm not sure what I'm doing differently. I checked my makepkg.conf and the only relevant differences are enabling ccache & disabling debug. libtool is still disabled.
BUILDENV=(!distcc color ccache check !sign)
OPTIONS=(strip docs !libtool !staticlibs emptydirs zipman purge !debug lto)
@yochananmarqos, interesting. I only build in a clean chroot and it's building fine here. Why is your build running libtoolize for libfuse? Mine is not doing that.
@Toolybird: This fails to build in a clean chroot with or without LTO enabled.
Build log (expires in one year)
Pinned Comments
Toolybird commented on 2026-06-30 07:35 (UTC) (edited on 2026-06-30 07:50 (UTC) by Toolybird)
NOTICE: Regarding Secure Boot.
Since 1.1.13+, upstream Ventoy has started signing EFI binaries in their releases. You can confirm this with for example
sbverify --list fbx64.efi. We don't have access to their private signing key, so obviously cannot do the same. AFAICT, this puts some doubt into the Ventoy Secure Boot situation for our "build from source" scenario.To be honest, I've never been a fan of the Ventoy Secure Boot "Bypass" thing anyway.. You can read about the new upstream Ventoy Secure Boot Policy here.