While extracting, I got messages that had colors within. Defeating --nocolor option of makepkg, which is nice to its --log. I believe these colors are created by the arch's maintainer. Am I right? Can that be improved?
Search Criteria
Package Details: ventoy-bin 1.0.99-1
Package Actions
| 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: | 9.97 |
| First Submitted: | 2020-05-19 06:14 (UTC) |
| Last Updated: | 2024-06-08 14:58 (UTC) |
Dependencies (7)
- bash (bash-devel-static-gitAUR, bash-devel-gitAUR, busybox-coreutilsAUR, bash-gitAUR)
- dosfstools (dosfstools-gitAUR)
- util-linux (busybox-coreutilsAUR, util-linux-selinuxAUR, util-linux-aesAUR)
- xz (xz-gitAUR)
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR) (optional) – GTK3 GUI
- polkit (polkit-gitAUR, polkit-consolekitAUR) (optional) – run GUI from application menu
- qt5-base (qt5-base-gitAUR, qt5-base-headlessAUR) (optional) – Qt5 GUI
Required by (0)
Sources (9)
ron2138 commented on 2021-08-30 16:05 (UTC) (edited on 2021-08-30 16:12 (UTC) by ron2138)
thiagowfx commented on 2021-08-28 20:22 (UTC)
Oh I am sorry, I just updated ventoy-bin and saw _msg2. Didn't realize it is wrapping printf, and completely forgot I suggested this before - I've been doing it to a couple of packages lately. Apologies and thanks for making the package better!
yochananmarqos commented on 2021-08-28 20:21 (UTC)
@thiagowfx: That was actually already done awhile ago.
Kr1ss commented on 2021-08-28 20:20 (UTC)
@thiagowfx - We do use printf since you made that suggestion the first time.
thiagowfx commented on 2021-08-28 20:18 (UTC)
https://wiki.archlinux.org/title/Arch_package_guidelines#Package_etiquette:
Do not use makepkg subroutines (e.g. error, msg, msg2, plain, warning) as they might change at any time. To print data, use printf or echo.
TheHitMan commented on 2021-08-27 13:19 (UTC)
@DuckSoft: you are right, its my fault.
DuckSoft commented on 2021-08-22 05:05 (UTC) (edited on 2021-08-22 05:09 (UTC) by DuckSoft)
@TheHitMan:
qemu-system-x86_64 -cdrom /dev/sdb
I think you have used the wrong arguments for qemu. Try qemu-system-x86_64 -hda /dev/sdb.
FYI: Here is how I test ventoy-bin after each release:
$ dd if=/dev/zero of=/tmp/vdisk.img bs=1M count=1024
$ sudo losetup /dev/loop0 /tmp/vdisk.img
$ ventoy -i /dev/loop0
...
$ qemu-system-x86_64 -hda /dev/loop0
TheHitMan commented on 2021-08-22 01:55 (UTC)
Attention: You will install Ventoy to /dev/sdb. All the data on the disk /dev/sdb will be lost!!!
Continue? (y/n) y
All the data on the disk /dev/sdb will be lost!!! Double-check. Continue? (y/n) y
Create partitions on /dev/sdb by parted in MBR style ... Done mkfs on disk partitions ... create efi fat fs /dev/sdb2 ... mkfs.fat 4.2 (2021-01-31) success mkexfatfs 1.3.0 Creating... done. Flushing... done. File system created successfully. writing data to disk ... sync data ... esp partition processing ...
Install Ventoy to /dev/sdb successfully finished.
[root@HTM-Burki-Flur u0]#
qemu-system-x86_64 -cdrom /dev/sdb
but i cant boot
thiagowfx commented on 2021-06-30 18:03 (UTC)
Please do not use msg2 and similar functions in the PKGBUILD:
https://wiki.archlinux.org/title/Arch_package_guidelines:
Do not use makepkg subroutines (e.g. error, msg, msg2, plain, warning) as they might change at any time. To print data, use printf or echo.
DuckSoft commented on 2021-05-07 09:35 (UTC)
@Tyilo I've updated the package. Please have a try with 1.0.42-3 and see if it works normally.
@C0rn3j I think it might make sense to open an issue about this upstream, so both could be supported depending on what is available on the system.
Upstream actually have bundled mkexfatfs and mount.exfat-fuse binaries for us. But I thought, there are existing binaries in exfat-utils, so why not use them?
What I didn't anticipate is that exfatprogs provides and conflicts with exfat-utils, but is not fully compatible with exfat-utils -- missing binaries, different CLI arguments...
So let's just put everything back then -- just use the bundled binaries.
Pinned Comments