Package Details: gittyup 1.3.0-1

Git Clone URL: (read-only, click to copy)
Package Base: gittyup
Description: Graphical Git client (GitAhead fork)
Upstream URL:
Licenses: MIT
Submitter: alerque
Maintainer: alerque
Last Packager: alerque
Votes: 13
Popularity: 0.80
First Submitted: 2021-11-23 20:05 (UTC)
Last Updated: 2024-03-27 23:54 (UTC)

Latest Comments

1 2 3 4 Next › Last »

tsingkong commented on 2024-04-13 06:00 (UTC)

there's an error in /gittyup/src/Gittyup/test/dep/zip/src/zip.c, L1676 when compiling with gcc 14, which should be: *buf = calloc(n, sizeof(unsigned char));

jost21 commented on 2023-08-12 20:39 (UTC)

Nevermind, I jumped the gun. It's still not working reliably. Not sure why it did for a bit and then stopped again.

I put more information in the github issue

jost21 commented on 2023-08-12 17:29 (UTC)

@yochananmarqos Thanks, that worked for me

yochananmarqos commented on 2023-08-12 00:30 (UTC)

@jost21: I can't reproduce that using my PKGBUILD.

jost21 commented on 2023-08-11 20:58 (UTC)

The context menu (right click) in the commit list section does not work for me in the AUR version. It does work in the Flatpak version though. It's only the middle section with the list of commits and the branch graph. Right clicking in other parts works normal.

I even reinstalled Manjaro in the time since I noticed the issue, and it still persists.

alerque commented on 2023-05-25 12:05 (UTC)

@schnedan I have no plans to cater to broken AUR helpers. This package builds cleanly with no interaction and passing checks in its current form in a clean chroot using Arch tooling. I also publish the built packages in my user repository, signed with official Arch Linux keys, so if you are so worried about just getting work done just use that.

marcool04 commented on 2023-05-23 17:13 (UTC) (edited on 2023-05-23 17:13 (UTC) by marcool04)


For some reason, I have been getting the behaviour described here: (my issue) which is something to do with libssh2 and accepted signature algorithms, but when I build Gittyup myself following instructions from the README, the issue is no longer there. Hence, I wonder if something in the PKGBUILD is introducing this bug. I'm happy to help debug if needed.



schnedan commented on 2023-02-07 07:35 (UTC)

Again, please remove the check from makepkg, so AUR-helpers run without interaction (again). In the last 3 month packages which do not build with default setting is accumulating. This situation is horrible. Please note: people use Arch to do work and not to play developer.

FabioLolix commented on 2023-01-23 20:21 (UTC)

@schnedan @denzil --nocheck option exist for makepkg

schnedan commented on 2023-01-23 20:20 (UTC)

Yah, commenting out is obvios. But if the checks are added to a build on a specific machine, there must be a reason. And if they fail, I guess something is wrong or broken.

So I think a.) Checks not needed? then the maintainer should remove em b.) tests needed? then the maintainer should ensure they do not fail in normal enviroments.

plus: editing PKGBUILDs by hand is a pia. It makes AUR Helpers fail and If you have several running systems it costs a lot of time. Maintainers should always have the correct mindset, and Arch as one of the largest distros around is also used to earn money. Thats no freetime toy! People depend on that stuff just works!