Package Details: gitqlient 1.3.2-1

Git Clone URL: (read-only, click to copy)
Package Base: gitqlient
Description: A Git client originally forked from QGit that has continued its own path
Upstream URL:
Licenses: LGPL
Submitter: duongdominhchau
Maintainer: duongdominhchau (francescmm)
Last Packager: duongdominhchau
Votes: 2
Popularity: 0.009485
First Submitted: 2020-02-27 10:05
Last Updated: 2021-04-11 17:54

Latest Comments

1 2 Next › Last »

duongdominhchau commented on 2021-01-31 14:11

Thank you for the information. I have added you to maintainer list. I also add the -git package to AUR, that package gets source from latest commit on develop branch instead of the release tarball.

francescmm commented on 2021-01-31 11:32


I'm the creator of GitQlient and I wanted to register to help you at least with the upcoming breaking changes that I might add in the future for the app.

First of all, really nice job and thanks for the support! :)

Now, the news!

I plan to release a new version very soon. I'm actually preparing it, so probably Week 5 or 6 is going to be out.

FYI, in the new version I removed the submodules QLogger and I added a dependency on QtWebkitEngineWidgets and QtWebChannel. Both should be inside QtWebEngine package so pretty sure you'll know how to manage.

I actively work with two main branches: 'master' and 'develop. - Master is the branch where the releases (and hotfixes) happen. It should be stable and crashes should be reported directly as critical bugs. - Develop is the unstable and live development branch. So it could happen that crashes happen but they should be fixed quite fast.

Personally, I use 'develop' in my work environment. That helps me to fix the issues and keep it updated all the time. However I wouldn't recommend that for official releases (although if you have an unstable release could be nice).

If you have any doubts, questions, requests or whatever, remember that I watch the issues in the repo all the time:

Stay healthy and safe! :D

duongdominhchau commented on 2021-01-10 18:36

Fixed. That package never existed, I use it to prepare for the case qlogger has its own releases but it doesn't seem to happen. A proper AUR helper should be able to handle that dependency anyway, because it is specified in provides variable of the -git package.

fasked commented on 2021-01-10 15:19

Seems like qlogger package doesn't exist anymore

duongdominhchau commented on 2020-11-25 02:47

@ganthore Fixed. Upstream treat warnings as errors, I removed that flag.

ganthore commented on 2020-11-24 21:29

With the latest versions of QT (5.15.2-1), sadly this is failing to build due to an explicit error regarding a depreciated class. The error is as follows:

error: ‘QNetworkRequest::FollowRedirectsAttribute’ is deprecated: Use RedirectPolicyAttribute

The good news is that I worked around the problem by adding the following find/sed command to the PKGBUILD file right before invoking qmake during the prepare phase:

find ./ -type f -exec sed -i -e 's/FollowRedirectsAttribute/RedirectPolicyAttribute/g' {} \;

Kunda commented on 2020-11-21 11:40

Would anybody be interested in creating a package for GitQlient Beta that just features the AppImage?

ax34 commented on 2020-07-19 16:35

Problem was on my side: i already had v1.1.1.tar.gz in my sources cache but this file was not gitqlient's source tarball, it was a remnant from other PKGBUILD. Such problems are usually solved by updpkgsums command (your PKGBUILD has no checksum).

duongdominhchau commented on 2020-07-19 16:11

From the output of ls your problem is before that stage: you don't have the source tarball. Do you see the source tarball this time? Its name is v1.1.1.tar.gz.

ax34 commented on 2020-07-19 15:27

I tried with makepkg, without yay, and i tried to re-download PKGBUILD - the same error. I believe you forgot to use srcdir variable, some kind of:

- cd "GitQlient-$pkgver"
+ cd "${srcdir}/GitQlient-$pkgver"

edit: it looks like your other PKGBUILDs have similar issue.