Package Details: gittyup 2.0.0-3

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: 19
Popularity: 0.59
First Submitted: 2021-11-23 20:05 (UTC)
Last Updated: 2026-09-15 07:55 (UTC)

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.

Latest Comments

1 2 3 4 5 6 7 Next › Last »

yochananmarqos commented on 2026-09-24 15:44 (UTC)

@alerque: Please use git cherry pick -n (aka --no-commit), otherwise it requires git credentials as others mentioned in the recent comments.

komarz commented on 2026-09-21 06:31 (UTC) (edited on 2026-09-21 06:33 (UTC) by komarz)

I temporarily use these:


GIT_AUTHOR_NAME="AUR Build" \
GIT_AUTHOR_EMAIL="aur-build@localhost" \
GIT_COMMITTER_NAME="AUR Build" \
GIT_COMMITTER_EMAIL="aur-build@localhost" \
yay -Syu

vandraren commented on 2026-09-15 18:17 (UTC)

@patlefort, in all honesty, that feels like a fix that can open the door to dodgy code (from other packages) that does things with git that's most probably not supposed to.

I am personally not in the need of that config normally, so it feels like a horrible trade-off

patlefort commented on 2026-09-15 12:02 (UTC)

I fixed that issue by entering a user name and email in /etc/makepkg.d/gitconfig:

[user]
  name = *your name*
  email = *your email*

vandraren commented on 2026-09-15 11:48 (UTC) (edited on 2026-09-15 11:49 (UTC) by vandraren)

got this trying to install 2.0.0-3:

Committer identity unknown

*** Please tell me who you are.

Run

  git config --global user.email "you@example.com"
  git config --global user.name "Your Name"

to set your account's default identity.
Omit --global to set the identity only in this repository.

fatal: unable to auto-detect email address (got 'vandraren@GAJNOR.(none)')
==> ERROR: A failure occurred in prepare().
    Aborting...
 -> error making: gittyup-exit status 4

committer? me?

bermudi commented on 2026-02-18 06:51 (UTC) (edited on 2026-02-18 07:10 (UTC) by bermudi)

binary was built/linked against a specific shared library (libcmark.so.0.31.1), but libcmark.so.0.32.1 is in the repos

EDIT: duh! just have to rebuild it

yochananmarqos commented on 2024-12-20 17:08 (UTC)

@alerque:

it's bundling a whole bunch of vendored QT libraries and other stuff internally and letting cmake install them wherever it wants on the system.

Come again? It seems you missed that my PKGBUILD removes /usr/include/ and /usr/lib/ altogether.

Dominiquini commented on 2024-12-20 13:39 (UTC)

The last version '1.4.0-5' is working fine, even if I remove the compilation folder! I just needed to delete de 'check' session from the PKGBUILD...

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.

OdinVex commented on 2024-12-19 01:14 (UTC) (edited on 2024-12-19 01:16 (UTC) by OdinVex)

Sounds like the Tests just need fixing:

Submodule: ~/.cache/yay/gittyup/src/Gittyup/src/git/Repository.cpp:159: QDir git::Repository::dir(bool) const: Assertion 'false' failed.

QDir Repository::dir(bool includeGitFolder) const { QDir dir(git_repository_path(d->repo)); if (!includeGitFolder && dir.dirName() == ".git") { if (!dir.cdUp()) { assert(false); // must be done explicit, because in release build the // assert will not be executed, so assert(dir.cdUp()) does // not work in release build } } return dir; }

A fake repo (self?) might be an option if the Tests are attempting to run but without a reliable git to run that function on?, or temporarily commenting THIS line out. Either way, it appears to be an inconsequential line to comment out (via patch).

1 2 3 4 5 6 7 Next › Last »