Package Details: gittyup-git 1.3.0.r129.g66bc256e-2

Git Clone URL: https://aur.archlinux.org/gittyup-git.git (read-only, click to copy)
Package Base: gittyup-git
Description: Graphical Git client (GitAhead fork)
Upstream URL: https://github.com/Murmele/Gittyup
Licenses: MIT
Conflicts: gittyup
Provides: gittyup
Submitter: FabioLolix
Maintainer: FabioLolix
Last Packager: FabioLolix
Votes: 10
Popularity: 0.26
First Submitted: 2021-11-17 16:06 (UTC)
Last Updated: 2023-12-30 15:57 (UTC)

Pinned Comments

FabioLolix commented on 2023-10-14 16:44 (UTC) (edited on 2023-10-14 17:03 (UTC) by FabioLolix)

Failing test 23 (on Cinnamon) 17 (on KDE) when build with makepkg, either build with devtools or skip tests (--nocheck in makepkg)

Latest Comments

« First ‹ Previous 1 2

vmfventura commented on 2023-10-12 21:30 (UTC) (edited on 2023-10-14 16:07 (UTC) by vmfventura)

still having erro when install

96% tests passed, 1 tests failed out of 26

Label Time Summary:
NO_WIN32_OFFSCREEN    =   5.42 sec*proc (4 tests)

Total Test time (real) =  35.43 sec

The following tests FAILED:
         17 - TreeView (Failed)
Errors while running CTest
FAILED: test/CMakeFiles/check /home/vmfventura/.cache/paru/clone/gittyup-git/src/Gittyup/build/test/CMakeFiles/check 
cd /home/vmfventura/.cache/paru/clone/gittyup-git/src/Gittyup/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...
error: failed to build:

FabioLolix commented on 2023-07-12 14:17 (UTC)

@eduardolucioac sorry, forgot about that, was failing because a commit upstream broke tests when -DCMAKE_BUILD_TYPE= was set to NONE, now is RelWithDebInfo (none was the suggested default by packaging guidelines until some time ago), I thought I already pushed that change

@Bink upstream renamed binaries from Gittyup to gittyup and don't seem to follow some -DCMAKE_INSTALL options, anyway for the moment works again

Bink commented on 2023-07-10 02:43 (UTC)

An update to my prior comment, rather than sym-linking to a system location that likely doesn't exist yet, use relative sym-links so it's fully contained within the package to be installed:

PKGBUILD lines #84 and #85 had to point to here to result in a successful launch:

ln -sr "${pkgdir}/usr/lib/gittyup/bin/gittyup" "${pkgdir}/usr/bin/gittyup"
ln -sr "${pkgdir}/usr/lib/Gittyup" "${pkgdir}/usr/bin/Gittyup"

Bink commented on 2023-06-08 02:31 (UTC) (edited on 2023-06-08 02:32 (UTC) by Bink)

PKGBUILD lines #84 and #85 seem to be linking to the wrong location. On my system, those lines had to point to here to result in a successful launch:

ln -s /usr/lib/Gittyup "${pkgdir}/usr/bin/Gittyup"
ln -s /usr/lib/gittyup/bin/gittyup "${pkgdir}/usr/bin/gittyup"

eduardolucioac commented on 2023-01-15 23:05 (UTC)

Is anyone having this problem? 👀

[...]
QDEBUG : TestTreeView::fileMergeCrash() Name:  "Unstaged" , countCollapsed(): 0
QDEBUG : TestTreeView::fileMergeCrash() Name:  "Unstaged" Current Collapsed:  0 ; New Collapsed:  -1
TreeView: /home/eduardolac/.cache/yay/gittyup-git/src/Gittyup/src/ui/TreeView.cpp:169: void TreeView::setCollapseCount(int): Assertion `value >= 0' failed.

      Start 18: Submodule
18/23 Test #18: Submodule ........................   Passed    2.37 sec
      Start 19: referencelist
19/23 Test #19: referencelist ....................   Passed    1.63 sec
      Start 20: amend
20/23 Test #20: amend ............................   Passed    0.77 sec
      Start 21: SshConfig
21/23 Test #21: SshConfig ........................   Passed    0.19 sec
      Start 22: fileContextMenu
22/23 Test #22: fileContextMenu ..................   Passed    1.85 sec
      Start 23: Setting
23/23 Test #23: Setting ..........................   Passed    0.17 sec

96% tests passed, 1 tests failed out of 23

Label Time Summary:
NO_WIN32_OFFSCREEN    =   4.39 sec*proc (4 tests)

Total Test time (real) =  35.18 sec

The following tests FAILED:
         17 - TreeView (Subprocess aborted)
Errors while running CTest
FAILED: test/CMakeFiles/check /home/eduardolac/.cache/yay/gittyup-git/src/Gittyup/build/test/CMakeFiles/check 
cd /home/eduardolac/.cache/yay/gittyup-git/src/Gittyup/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...
 -> error making: gittyup-git

alerque commented on 2022-10-22 16:55 (UTC)

Upstream has landed major improvements. I have a PKGBUILD that overhauls this to match. See my comment upstream here.

alerque commented on 2022-10-22 09:20 (UTC)

Hey Fabio! Would you mind if I jump on as a co-maintainer here? I maintain the stable AUR package and have been working with upstream to fix their build system to work better for our needs (see current progress here). They are close to landing a PR related to that and I'd like to overhaul this to use the new build features before it lands in a stable release and I can then overhaul that package. By the way when the stable build gets overhauled I'm hopeful the process will be sane enough we can then migrate it to [community].

Kunda commented on 2022-02-03 14:34 (UTC)

Crash reported upstream when trying to add Github user account: https://github.com/Murmele/Gittyup/issues/98

« First ‹ Previous 1 2