Arch Linux User Repository

@brainfucksec holy, they seemed to have updated their release asset after released. lemme check and update. thanks for that.

Hi @DuckSoft, in the latest version of the package (1.0.14-1), you cannot build the package with makepkg, the following error is returned:

==> Validation of source files with sha256sums ==
     ventoy-1.0.14-linux.tar.gz ... NOT SUCCESSFUL
     ventoy ... Verified
     sanitize.patch ... Verified
==> ERROR: One or more files failed the validity check!

Thanks

@taotieren upstream have confirmed and accepted this bug

使用电脑的 SD 卡接口制作启动盘遇到分区识别错误

https://github.com/ventoy/Ventoy/issues/249

Wow, thank you for the quick response !

@Kr1ss thanks for your hint! I've fixed that!

Hey @DuckSoft @yochananmarqos @KokaKiwi,

thx a lot for packaging this for the AUR and maintaining.

Most likely there's a mistake in lines #54f, where the symlinks which were just installed in lines #52f get overwritten.

Is this actually meant to be :

diff -ru --color old/PKGBUILD new/PKGBUILD
--- old/PKGBUILD        2020-06-22 21:02:54.057938250 +0200
+++ new/PKGBUILD        2020-06-22 21:03:51.868114896 +0200
@@ -51,8 +51,8 @@
   ln -svf /usr/bin/hexdump "$pkgdir/opt/${pkgname%-bin}/tool/"
   ln -svf /usr/bin/mkfs.exfat "$pkgdir/opt/${pkgname%-bin}/tool/mkextfatfs_32"
   ln -svf /usr/bin/mkfs.exfat "$pkgdir/opt/${pkgname%-bin}/tool/mkextfatfs_64"
-  ln -svf /usr/bin/mount.exfat-fuse "$pkgdir/opt/${pkgname%-bin}/tool/mkextfatfs_32"
-  ln -svf /usr/bin/mount.exfat-fuse "$pkgdir/opt/${pkgname%-bin}/tool/mkextfatfs_64"
+  ln -svf /usr/bin/mount.exfat-fuse "$pkgdir/opt/${pkgname%-bin}/tool/mount.exfat-fuse_32"
+  ln -svf /usr/bin/mount.exfat-fuse "$pkgdir/opt/${pkgname%-bin}/tool/mount.exfat-fuse_64"

   msg2 "Creating /usr/bin entries..."
   install -Dm755 "$srcdir/${pkgname%-bin}" -t "$pkgdir"/usr/bin/

?

Cheers !

@DuckSoft Sorry about my previous comment. Just checked today, uninstalling and reinstalling the package seems to be fine, no changes to the PKGBUILD file required. Also, I've disowned the package as I mostly won't be contributing anything significant. I'm a mere user.

@sanchith good advice! thank you!

Please update the PKGBUILD to let the package take ownership of the installed files. This can be done using the -o argument with the install command.

Otherwise, updates to the package fails with the following error:

error: failed to commit transaction (conflicting files)
ventoy-bin: /opt/ventoy/tool/<file> exists in filesystem
...
Errors occurred, no packages were upgraded.

for each <file> installed by ventoy.

For users with the error, you'll have to uninstall the package, manually delete ventoy's files with necessary permissions using: rm -rf /opt/ventoy. You can then install the package with necessary changes to the PKGBUILD file (until it's updated by the maintainers).