Arch Linux User Repository

Is this supposed to take more than 20 minutes to install? Should I be worried?

I previously installed woeusb-ng but it wouldn't work. So now I'm installing woeusbgui and it's taking more than 20 minutes to install, heating up my CPU. What am I doing wrong?

edit: More than 30 minutes now.

edit: I cancelled it. This is super weird.

edit: I re-installed woeusb-ng, which has a GUI, and it works perfectly (although it took 1/2 hour to install the bootloader to the USB).

Hey seberm, I've managed to add warnings about this package to show up in the pacman installation. You can now check it out and leave your comments if you want anything else to add

Hello sandm,

could you please add info (e.g. into post-install hook) that this package is an old unsupported version of woeusb which still keeps the gui support but it's not longer maintained? Could you also please add a link to latest woeusb AUR package (https://aur.archlinux.org/packages/woeusb/)?

I think this could save people some time when they encounter problems with an old woeusb version (e.g. https://github.com/WoeUSB/WoeUSB/issues/96#issuecomment-1002287311).

Thanks!

@gardotd426 I'm well aware of the situation with the new repos as I maintain the woeusb package. I specifically made this current package to preserve the old gui version of woeusb. I have checked it with my own usb drive and it got detected correctly, so I'm assuming it works as intended. If you want up-to-date maintained version, then you can use the woeusb package or the woeusb-ng which you mentioned yourself. I will keep this old gui version as long as it available on GitHub.

Well, I mean, you're using a "maintenance" release only intended for package maintainers, I mean it includes a file called The.source.code.archives.provided.here.is.NOT.supported.please.use.git-clone.instead with contents that say

This is a dummy file for package uploaders to resolve the undenyable GitHub Release source code archives.

The slacka/WoeUSB repo is dead, and they've moved and changed everything. The regular WoeUSB no longer supports a GUI, and they split the GUI off into it's own repo. Read the README from the repo you're trying to use. It explains everything.

woeusb-ng is the provider of the GUI now. And sure enough, the woeusb-ng AUR package works fine.

You may not have changed anything, but the repo changed, and now GUI isn't supported, and everything has moved to new repos (so obviously this isn't a valid source in the first place, since there will be no more updates).

I honestly just suggest removing this package from the AUR.

Well, I mean, you're using a "maintenance" release only intended for package maintainers, I mean it includes a file called The.source.code.archives.provided.here.is.NOT.supported.please.use.git-clone.instead with contents that say

This is a dummy file for package uploaders to resolve the undenyable GitHub Release source code archives.

The slacka/WoeUSB repo is dead, and they've moved and changed everything. The regular WoeUSB no longer supports a GUI, and they split the GUI off into it's own repo. Read the README from the repo you're trying to use. It explains everything.

woeusb-ng is the provider of the GUI now. And sure enough, the woeusb-ng AUR package works fine.

You may not have changed anything, but the repo changed, and now GUI isn't supported, and everything has moved to new repos (so obviously this isn't a valid source in the first place, since there will be no more updates).

@gardotd426 I didn't change anything in the PKGBUILD except for the package name. It's all the same program, so if you have any ideas what might be wrong feel free to share.

Sorry man, doesn't work.

It won't detect my usb drive. Old woeusb definitely detected it (I used it like a week ago).

woeusb-ng detects it fine.

I tried running your woeusbgui as root, since woeusb-ng asks for the root password when launching it (just like other GUI programs that need root permissions, like Gparted). Still didn't work.