Package Details: ventoy 1.0.99-2

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
Conflicts: ventoy-bin
Submitter: Toolybird
Maintainer: Toolybird
Last Packager: Toolybird
Votes: 18
Popularity: 3.25
First Submitted: 2023-02-17 20:09 (UTC)
Last Updated: 2024-06-30 08:31 (UTC)

Required by (0)

Sources (22)

Latest Comments

1 2 3 Next › Last »

Toolybird commented on 2024-06-30 08:38 (UTC)

Thanks for reporting. Latest libgcrypt version has removed libgcrypt-config which breaks the "verity" build. Have worked around it for now.

korimitsu commented on 2024-06-26 21:49 (UTC) (edited on 2024-06-26 22:06 (UTC) by korimitsu)

libgcrypt is required.

checking for LIBGCRYPT - version >= 1.1.42... no configure: error: You need the gcrypt library.

FabioLolix commented on 2024-06-13 18:44 (UTC)

@hacktor look at https://wiki.archlinux.org/title/Makepkg#Improving_build_times

hacktor commented on 2024-06-13 16:29 (UTC)

I've noticed that this package's build process is extremly slow, and the system resourses haven't been fully utilized. Thus I cannot help but change my package to ventoy-bin. I want to know if there's something you can do to help the package build faster, such as parallel compilation.

jal666 commented on 2024-04-23 15:47 (UTC) (edited on 2024-04-23 15:47 (UTC) by jal666)

Double-check. Continue? (y/n) y /opt/ventoy/Ventoy2Disk.sh: line 70: 232716 Killed /bin/bash ./tool/VentoyWorker.sh $*

Anyone else get this?

Toolybird commented on 2024-02-17 22:46 (UTC)

startup.S: Assembler messages: startup.S:34: Error: 64bit mode not supported on `i386'.

Thanks for reporting. binutils-2.42 broke the wimboot build. I've added a patch adapted from upstream.

George528 commented on 2024-02-17 14:18 (UTC)

make[2]: Entering directory '/home/george/pkgbuilds/ventoy/src/Ventoy-1.0.97/cryptsetup/cryptsetup-1.7.5/src'
  CC       cryptsetup-utils_crypt.o
  CC       cryptsetup-utils_loop.o
  CC       cryptsetup-utils_tools.o
  CC       cryptsetup-utils_password.o
  CC       cryptsetup-cryptsetup.o
  CCLD     cryptsetup
  CC       veritysetup-utils_crypt.o
  CC       veritysetup-utils_loop.o
  CC       veritysetup-utils_tools.o
  CC       veritysetup-veritysetup.o
  CCLD     veritysetup
make[2]: Leaving directory '/home/george/pkgbuilds/ventoy/src/Ventoy-1.0.97/cryptsetup/cryptsetup-1.7.5/src'
Making all in man
make[2]: Entering directory '/home/george/pkgbuilds/ventoy/src/Ventoy-1.0.97/cryptsetup/cryptsetup-1.7.5/man'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/home/george/pkgbuilds/ventoy/src/Ventoy-1.0.97/cryptsetup/cryptsetup-1.7.5/man'
Making all in python
make[2]: Entering directory '/home/george/pkgbuilds/ventoy/src/Ventoy-1.0.97/cryptsetup/cryptsetup-1.7.5/python'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/home/george/pkgbuilds/ventoy/src/Ventoy-1.0.97/cryptsetup/cryptsetup-1.7.5/python'
Making all in tests
make[2]: Entering directory '/home/george/pkgbuilds/ventoy/src/Ventoy-1.0.97/cryptsetup/cryptsetup-1.7.5/tests'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/home/george/pkgbuilds/ventoy/src/Ventoy-1.0.97/cryptsetup/cryptsetup-1.7.5/tests'
Making all in po
make[2]: Entering directory '/home/george/pkgbuilds/ventoy/src/Ventoy-1.0.97/cryptsetup/cryptsetup-1.7.5/po'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/home/george/pkgbuilds/ventoy/src/Ventoy-1.0.97/cryptsetup/cryptsetup-1.7.5/po'
make[2]: Entering directory '/home/george/pkgbuilds/ventoy/src/Ventoy-1.0.97/cryptsetup/cryptsetup-1.7.5'
make[2]: Leaving directory '/home/george/pkgbuilds/ventoy/src/Ventoy-1.0.97/cryptsetup/cryptsetup-1.7.5'
make[1]: Leaving directory '/home/george/pkgbuilds/ventoy/src/Ventoy-1.0.97/cryptsetup/cryptsetup-1.7.5'
'veritysetup' -> '../../veritysetup64'
'../../wimboot-2.7.3.orig/src/callback.S' -> './callback.S'
'../../wimboot-2.7.3.orig/src/prefix.S' -> './prefix.S'
'../../wimboot-2.7.3.orig/src/startup.S' -> './startup.S'
cc -Os -ffreestanding -Wall -W -nostdinc -I. -fshort-wchar -DVERSION="\"v2.7.3\"" -fstack-protector-strong  -mstack-protector-guard=global -fno-dwarf2-cfi-asm -fno-exceptions  -fno-unwind-tables -fno-asynchronous-unwind-tables  -Wno-address-of-packed-member -fno-lto  -include compiler.h -m64 -mno-red-zone -fpie -DASSEMBLY -Ui386 -E prefix.S -o prefix.x86_64.s
as --64 x86_64.i prefix.x86_64.s -o prefix.x86_64.o
cc -Os -ffreestanding -Wall -W -nostdinc -I. -fshort-wchar -DVERSION="\"v2.7.3\"" -fstack-protector-strong  -mstack-protector-guard=global -fno-dwarf2-cfi-asm -fno-exceptions  -fno-unwind-tables -fno-asynchronous-unwind-tables  -Wno-address-of-packed-member -fno-lto  -include compiler.h -m64 -mno-red-zone -fpie -DASSEMBLY -Ui386 -E startup.S -o startup.x86_64.s
as --64 x86_64.i startup.x86_64.s -o startup.x86_64.o
startup.S: Assembler messages:
startup.S:34: Error: 64bit mode not supported on `i386'.
make: *** [Makefile:159: startup.x86_64.o] Error 1
rm startup.x86_64.s prefix.x86_64.s
==> ERROR: A failure occurred in build().
    Aborting...

my system is x86_64

Toolybird commented on 2024-01-26 05:34 (UTC)

@alerque It really is the kernel. libguestfs constructs a root filesystem "on the fly" and boots it inside a QEMU VM. It works fine with linux-lts and probably other kernels too. No tickets re kernel virtual-provides that I know of. It's probably not worth it for only 1 consumer i.e. libguestfs. I've added linux to makedeps for now.

alerque commented on 2024-01-24 08:40 (UTC) (edited on 2024-01-24 09:58 (UTC) by alerque)

@Toolybird I've run into an issue depending on a kernel while not caring whether it is the LTS or regular or some other kernel. You can fudge it because there are some things both provide, but they are not super appropriate. Has there been an issue opened on any of the kernel packages to add a more generic virtual-provides? Also is it really the kernel or is it the kernel headers that is actually needed here? Perhaps the linux-api-headers package is actually what this needs?