Arch Linux User Repository

Ok, thanks a lot @Kr1ss, friend... I decided to just "sudo rm -r /opt/ventoy", but also wanted to post the question here in case it has/had been a problem with the package? Because I don't remember anything about an interruption while de-installing - this problem started, because I tried to upgrade all my packages and it didn't want to update this package. Then I removed it - and couldn't install it... For this reason, I thought it would be a good idea to post it here - but seems nobody else wrote about this, maybe something did happen to my installation, that didn't happen to other people... Well - in any case, rm -rf works - thanks a lot, problem solved (and thanks for a nice package too) :-)

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.

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?

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

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

@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 !