Package Details: ventoy-bin 1.0.99-1

Git Clone URL: https://aur.archlinux.org/ventoy-bin.git (read-only, click to copy)
Package Base: ventoy-bin
Description: A new bootable USB solution
Upstream URL: http://www.ventoy.net
Keywords: boot image iso multiboot usb
Licenses: GPL-3.0-or-later
Conflicts: ventoy
Provides: ventoy
Submitter: DuckSoft
Maintainer: DuckSoft (KokaKiwi, yochananmarqos, Kr1ss)
Last Packager: yochananmarqos
Votes: 360
Popularity: 7.85
First Submitted: 2020-05-19 06:14 (UTC)
Last Updated: 2024-12-13 03:01 (UTC)

Pinned Comments

Latest Comments

« First ‹ Previous 1 .. 9 10 11 12 13 14 15 16 Next › Last »

Kr1ss commented on 2020-07-01 17:38 (UTC) (edited on 2020-07-01 17:47 (UTC) by Kr1ss)

It looks like the deinstallation of the package has been interrupted @newsboost.

While this doesn't explain nor solve the cause of your issue, I would actually suggest to

sudo rm -r /opt/ventoy

which are the files contained in the package. Since there are files untracked by the pacman database, they cannot be automatically removed by pacman.

If you really don't want to manually remove these files, you could also

cd ventoy-bin/
makepkg -rs
sudo pacman -U --overwrite opt/ventoy/tool/* ./ventoy-bin*.tar.*

EDIT ventoy-bin/ is the folder containing the PKGBUILD (and the .patch file), of course.

newsboost commented on 2020-07-01 17:19 (UTC)

hmmm.... There's something wrong here, I couldn't upgrade ventoy-bin, so I uninstalled - then tried to re-install:

(1/1) loading package files                                     [##################################] 100%
(1/1) checking for file conflicts                               [##################################] 100%
error: failed to commit transaction (conflicting files)
ventoy-bin: /opt/ventoy/tool/ENROLL_THIS_KEY_IN_MOKMANAGER.cer exists in filesystem
ventoy-bin: /opt/ventoy/tool/VentoyWorker.sh exists in filesystem
ventoy-bin: /opt/ventoy/tool/hexdump exists in filesystem
ventoy-bin: /opt/ventoy/tool/mkexfatfs_32 exists in filesystem
ventoy-bin: /opt/ventoy/tool/mkexfatfs_64 exists in filesystem
ventoy-bin: /opt/ventoy/tool/mount.exfat-fuse_32 exists in filesystem
ventoy-bin: /opt/ventoy/tool/mount.exfat-fuse_64 exists in filesystem
ventoy-bin: /opt/ventoy/tool/vtoy_gen_uuid exists in filesystem
ventoy-bin: /opt/ventoy/tool/vtoyfat_32 exists in filesystem
ventoy-bin: /opt/ventoy/tool/vtoyfat_64 exists in filesystem
Errors occurred, no packages were upgraded.

So it didn't fully remove the installed stuff?

$ yay -Rns ventoy-bin
error: target not found: ventoy-bin

Anyone know what's wrong and how I should fix this? I reaaaaaaly prefer not to just "rm -rf /opt/ventoy" - but that might be the solution I'll use, if nobody can/will explain a better solution/method?

brainfucksec commented on 2020-06-26 13:30 (UTC)

Perfect @DuckSoft, thanks for the fix and thanks for the package :)

DuckSoft commented on 2020-06-26 06:15 (UTC)

@brainfucksec thanks for your reporting. digest is now updated. feel free to message if there is any other problem.

DuckSoft commented on 2020-06-26 06:11 (UTC) (edited on 2020-06-26 06:11 (UTC) by DuckSoft)

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

brainfucksec commented on 2020-06-26 06:02 (UTC)

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

DuckSoft commented on 2020-06-25 15:04 (UTC)

@taotieren upstream have confirmed and accepted this bug

taotieren commented on 2020-06-24 02:11 (UTC) (edited on 2020-06-24 02:11 (UTC) by taotieren)

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

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

Kr1ss commented on 2020-06-22 19:18 (UTC)

Wow, thank you for the quick response !

DuckSoft commented on 2020-06-22 19:16 (UTC) (edited on 2020-06-22 19:18 (UTC) by DuckSoft)

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