Search Criteria
Package Details: gittyup 1.3.0-1
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: | 13 |
Popularity: | 0.48 |
First Submitted: | 2021-11-23 20:05 (UTC) |
Last Updated: | 2024-03-27 23:54 (UTC) |
Dependencies (16)
- cmark (cmark-gitAUR)
- git (git-gitAUR)
- hunspell (hunspell-gitAUR)
- 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)
- ninja (ninja-kitwareAUR, ninja-memAUR, ninja-fuchsia-gitAUR, ninja-gitAUR, ninja-jobserverAUR) (make)
- qt5-tools (qt5-tools-gitAUR) (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
Latest Comments
« First ‹ Previous 1 2 3 4 5 Next › Last »
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:
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.
patlefort commented on 2022-07-01 03:34 (UTC)
Revised patch:
I realized that I could just have used a symbolic link. It also work better with pinned apps in KDE.
alumni commented on 2022-06-30 08:20 (UTC)
@patlefort's patch is fine for me
jost21 commented on 2022-06-24 16:53 (UTC)
I also have that issue. I can install and use it, when I use the PKGBUILD from @yochananmarqos, but themes are totally messed up. Almost unusable because it's light on light text or similar.
It used to work great with any theme (dark or light) until sometime in May, I think.
« First ‹ Previous 1 2 3 4 5 Next › Last »