usr/include/c++/9.2.0/bits/fs_fwd.:39: Parse error at "std"
Search Criteria
Package Details: multibootusb 9.2.0-5
Package Actions
Git Clone URL: | https://aur.archlinux.org/multibootusb.git (read-only, click to copy) |
---|---|
Package Base: | multibootusb |
Description: | Boot multiple live Linux distros from a usb flash drive. |
Upstream URL: | https://sourceforge.net/projects/multibootusb/ |
Keywords: | multiboot multibootusb usb |
Licenses: | GPL |
Submitter: | Angel_Caido |
Maintainer: | gmy |
Last Packager: | gmy |
Votes: | 113 |
Popularity: | 0.000000 |
First Submitted: | 2015-08-20 19:45 (UTC) |
Last Updated: | 2021-04-19 10:40 (UTC) |
Dependencies (6)
- mtools (mtools-svnAUR)
- p7zip (p7zip-natspecAUR, p7zip-full-binAUR, 7-zip-fullAUR)
- parted (parted-gitAUR)
- python-dbus
- python-pyqt5 (python-pyqt5-sip4AUR, python-pyqt5-webkitAUR)
- python-pyudev
Required by (0)
Sources (2)
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 .. 12 Next › Last »
simona commented on 2019-11-10 08:04 (UTC)
freaz commented on 2019-11-05 05:09 (UTC)
@ptrxyz - I got that error also. Tracked it down to actually another error which is ignored during module imports. In short it seems the first time I ran multibootusb without root it created a /tmp/multibootusb.log file. Then when running it as root when it tries to import the config file it for some reason can't because of incorrect permissions/ownership on that log file (and this error is ignored until the config variable is accessed). Anyhow, deleting /tmp/multibootusb.log and running as root worked for me.
ptrxyz commented on 2019-10-27 09:00 (UTC) (edited on 2019-10-27 09:04 (UTC) by ptrxyz)
When trying to install, this is what I get:
Using python version 3.7.4 (default, Oct 4 2019, 06:57:26)
[GCC 9.2.0] on platform Linux-5.3.7-zen1-1-zen-x86_64-with-arch
Traceback (most recent call last):
File "/usr/bin/multibootusb", line 187, in <module>
if config.debug is True:
NameError: name 'config' is not defined
I'm not sure what causes this issue, does anyone know?
yochananmarqos commented on 2019-10-16 21:56 (UTC) (edited on 2019-10-16 22:00 (UTC) by yochananmarqos)
Please use a build()
array according to Python package guidelines:
build() {
cd "$pkgname-$pkgver"
python setup.py build
}
package() {
cd "$pkgname-$pkgver"
python setup.py install --root="$pkgdir/" --optimize=1 --skip-build
}
It is unnecessary to change the permissions of the desktop file.
It's not necessary to include the following:
pyqt5-common
aspython-pyqt5
depends on it.python-six
aspython-pyudev
depends on it.util-linux
as its part of thebase-devel
group.
DragonX256 commented on 2019-10-09 07:27 (UTC)
Issue is resolved, possibly. I mean, there is no config not defined
when building package.
Zack_Emmert commented on 2019-04-14 21:59 (UTC)
This package is broken by an upstream issue, for the time being please use multibootusb-git.
zenolijo commented on 2019-02-23 16:49 (UTC)
I have the same issue as @ganileni but was able to solve it.
I have a quite lean setup and installing the package extra/udisks2 fixed the error, so I guess that's a missing dependency?
Zack_Emmert commented on 2018-12-05 20:20 (UTC)
I located the issue. The polkit file was pointing to the wrong location of the binary, causing it to crash. I just pushed a change to the PKGBUILD that corrects this.
winicius commented on 2018-12-04 12:01 (UTC)
The program is not launching for me, running multibootusb-pkexec on terminal I get the error:
Using python version 3.7.1 (default, Oct 22 2018, 10:41:28) [GCC 8.2.1 20180831] on platform Linux-4.19.6-1-MANJARO-x86_64-with-arch-Manjaro-Linux Could not find resource 'data/tools/gdisk/gdisk.exe'. Running multibootusb version 9.2.0 from installed system... Starting multibootusb GUI... qt.qpa.screen: QXcbConnection: Could not connect to display Could not connect to any X display.
Pinned Comments