Search Criteria
Package Details: vesc_tool-git 1:r1315.e1eb241-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/vesc_tool-git.git (read-only, click to copy) |
---|---|
Package Base: | vesc_tool-git |
Description: | VESC ESC graphical configuration tool |
Upstream URL: | https://vesc-project.com/vesc_tool |
Licenses: | GPL3 |
Conflicts: | vesc-tool |
Submitter: | Kezi |
Maintainer: | Kezi (bionade24) |
Last Packager: | bionade24 |
Votes: | 3 |
Popularity: | 0.000066 |
First Submitted: | 2018-08-27 22:50 (UTC) |
Last Updated: | 2023-10-22 17:53 (UTC) |
Dependencies (9)
- qt5-base (qt5-base-gitAUR, qt5-base-headlessAUR)
- qt5-connectivity (qt5-connectivity-gitAUR)
- qt5-gamepad (qt5-gamepad-gitAUR)
- qt5-location (qt5-location-gitAUR)
- qt5-quickcontrols2 (qt5-quickcontrols2-gitAUR)
- qt5-serialbus (qt5-serialbus-gitAUR)
- qt5-serialport (qt5-serialport-gitAUR)
- qt5-svg (qt5-svg-gitAUR)
- git (git-gitAUR, git-fcAUR) (make)
Latest Comments
1 2 Next › Last »
bionade24 commented on 2023-10-22 17:46 (UTC)
@SysGhost: Sorry for forgetting to remove the patch after I got it merged upstream.
I received the notification mail but overlooked it in the bulk of mails.
SysGhost commented on 2023-10-19 15:27 (UTC) (edited on 2023-10-19 15:34 (UTC) by SysGhost)
Trying to apply an already applied patch:
Easily fixed by removing or commenting out the patch line for lzokay in the prepare function in PKGBUILD. A line that starts with "patch -d lzokay -i " ... Once disabled, it configures and builds fine.
GPereira commented on 2023-02-19 00:41 (UTC)
@Pheidologeton I am having the same issue, any luck?
Pheidologeton commented on 2022-11-27 23:33 (UTC)
Cannot build. Loop in this
Any way to fix it?
niraami commented on 2021-06-12 17:00 (UTC) (edited on 2021-06-12 21:15 (UTC) by niraami)
@bionade24 The reason behind my error a few months back is a flawed
pkgver()
function, as it returns thepkgver
variable + the git information (r287.b0632c4
)... that is already in that variable - essentially duplicating it. I've noticed that after installing the package (through yay or manually) the PKGBUILD gets updated. Here is the diff:So, if you don't reload the pkgbuild during installation, this issue will not arise (which I guess Yay does for some reason). Also using the
--editmenu
to edit the PKGBUILD /w Yay and removing the "${pkgver}" frompkgver()
solves the issue.I can see that this is not an issue only affecting me, as, in the latest commit, you've changed the
pkgver
to3.00.r287.b0632c4.r287.b0632c4.r287.b0632c4-1
. I find that kind of hilarious as it also changed the name of the package on AUR.Also, dunno if this is helpful, but the commit that introduced this issue was: 163d11d0e029.
The offending line is:
printf "${pkgver}.r%s.%s" "$(git rev-list --count HEAD)" "$(git rev-parse --short HEAD)"
My recommendation is, if you want to also keep the program version included in the name & the pkgbuild, use a separate variable for it (like
gitver=3.00
). Though it is unfortunate that the github maintainers still don't tag the versions on GitHub.I hope my formatting is done right, otherwise I might edit this comment a few times.
DarioP commented on 2021-06-11 13:45 (UTC)
Thank you for your very prompt action, I was able to successfully build the package.
I did not look into the building system, but I agree that everything that can be fixed upstream should be done there, without custom fixes and patches ;)
bionade24 commented on 2021-06-11 13:13 (UTC)
@DarioP: The linkers errors are fixed now.
It still would probably better to patch the upstream .pro file instead of provding a derived one, probably doing that.
DarioP commented on 2021-06-11 08:19 (UTC) (edited on 2021-06-11 08:20 (UTC) by DarioP)
Anyone getting the same linker errors as I do:
bionade24 commented on 2021-01-11 08:16 (UTC)
@niraami: I can't reproduce your issue, seems like caused by your dirty build environment. Please use a clean chroot/container.
1 2 Next › Last »