I still have to use yochananmarqos's PKGBUILD file to have a successfull build, without the 2 test errors.
Search Criteria
Package Details: gittyup 1.4.0-5
Package Actions
Git Clone URL: | https://aur.archlinux.org/gittyup.git (read-only, click to copy) |
---|---|
Package Base: | gittyup |
Description: | Graphical Git client (GitAhead fork) |
Upstream URL: | https://murmele.github.io/Gittyup |
Licenses: | MIT |
Submitter: | alerque |
Maintainer: | alerque |
Last Packager: | alerque |
Votes: | 14 |
Popularity: | 0.45 |
First Submitted: | 2021-11-23 20:05 (UTC) |
Last Updated: | 2024-12-20 12:52 (UTC) |
Dependencies (17)
- cmark (cmark-gitAUR)
- git (git-gitAUR, git-glAUR)
- hicolor-icon-theme (hicolor-icon-theme-gitAUR)
- hunspell (hunspell-gitAUR)
- libsecret
- libssh2 (libssh2-gitAUR)
- lua
- lua-lpeg
- openssl (openssl-gitAUR, openssl-staticAUR)
- qt5-base (qt5-base-gitAUR, qt5-base-headlessAUR)
- cmake (cmake-gitAUR) (make)
- libgnome-keyring (make)
- qt5-tools (make)
- qt5-translations (qt5-translations-gitAUR) (make)
- git-lfs (git-lfs-gitAUR) (optional) – git-lfs support
- libgnome-keyring (optional) – for GNOME Keyring for auth credentials
- qt5-translations (qt5-translations-gitAUR) (optional) – translations
Required by (0)
Sources (5)
roti commented on 2022-11-25 13:18 (UTC)
denzil commented on 2022-11-01 09:34 (UTC) (edited on 2022-11-01 09:35 (UTC) by denzil)
@alerque I got the same error, in fact I have 2 tests failed. You can see entire output here https://pastebin.com/fh29e9rV I checked, I don't have git-lfs package installed.
alerque commented on 2022-10-29 17:03 (UTC)
@SoftExpert That does not sound right at all. This does not require git-lfs to build, and indeed I've been building it in chroots without it installed. I only have it marked as an optional dependency. I doubt your system is missing anything because makepkg
would warn you about not having any of the necessary dependencies, what I suspect is happening is you have something more than specified here that was causing an incorrectly configured build. It would be nice to know what that is but I don't see any clues yet (again partly because your log doesn't show the actual error).
SoftExpert commented on 2022-10-29 11:04 (UTC) (edited on 2022-10-29 11:04 (UTC) by SoftExpert)
@alerque: I was missing git-lfs package; once I installed it, the package built correctly. Thank you !
alerque commented on 2022-10-29 07:38 (UTC)
@SoftExpert My tests building this in a clean chroot build environment pass the checks. Are you building on a host system with possibly other packages installed that it finds instead of the vendored submodules? Try building in a chroot with only the declared dependencies.
Your output doesn't show the part of the tests that actually failed, so I can't suggest much.
Also you can install the prebuilt package from my Arch user repository.
SoftExpert commented on 2022-10-28 22:58 (UTC) (edited on 2022-10-28 22:59 (UTC) by SoftExpert)
Build of the latest version (1.2.0-1) fails with:
Start 18: Submodule
18/22 Test #18: Submodule ........................ Passed 7.03 sec
Start 19: referencelist
19/22 Test #19: referencelist .................... Passed 1.62 sec
Start 20: amend
20/22 Test #20: amend ............................ Passed 2.44 sec
Start 21: SshConfig
21/22 Test #21: SshConfig ........................ Passed 0.11 sec
Start 22: fileContextMenu
22/22 Test #22: fileContextMenu .................. Passed 9.55 sec
91% tests passed, 2 tests failed out of 22
Label Time Summary:
NO_WIN32_OFFSCREEN = 13.98 sec*proc (4 tests)
Total Test time (real) = 89.63 sec
The following tests FAILED:
7 - index (Failed)
17 - TreeView (Failed)
Errors while running CTest
FAILED: test/CMakeFiles/check /var/tmp/pamac-build-username/gittyup/src/build/test/CMakeFiles/check
cd /var/tmp/pamac-build-username/gittyup/src/build/test && /usr/bin/ctest --force-new-ctest-process --output-on-failure --timeout 300
ninja: build stopped: subcommand failed.
==> ERROR: A failure occurred in check().
Aborting...
yochananmarqos commented on 2022-08-25 23:31 (UTC)
@alerque: I would talk to upstream. I only created my PKGBUILD because I had nothing else to do. It's an interesting project, so I check when there's new releases. That's about it. I don't even use it. I gave up on git GUI's and just use terminal commands.
alerque commented on 2022-08-25 20:08 (UTC)
@yochananmarqos Any interest in PR's the differences needed for a bump to here. Clearly upstream hasn't gotten things together so this can be built without a bunch of vendored stuff so we'll have to go with it for now. If you have whatever new modules and minimal changes are required for and update I would roll with it (keeping in mind the style choices I've made are working towards a [community] build if we can get it sufficiently de-vendored).
yochananmarqos commented on 2022-08-13 19:27 (UTC)
@datejur: There's also a couple new submodules, see my PKGBUILD.
danejur commented on 2022-08-13 19:22 (UTC)
For anyone out of date as of 2022-08-12, applying patlefort's patch to the existing PKGBUILD (ver 1.1.1) and changing the pkgver on line 5 to 1.1.2 was all I needed to do to build and install the latest version.
Pinned Comments
alerque commented on 2024-12-20 13:30 (UTC)
I've created an issue upstream to track requirements for this build to make it to [extra]. As soon as those are met I'll make an official build for this. The project is a lot closer than it was even the last time I reviewed the status. If you want this to happen I'm sure the upstream project could use a hand with a few of the remaining details for devendoring.