Arch Linux User Repository

I added the checksum. About the compile error, I can't reproduce it on a fresh build, so maybe that's the problem from the leftover of old versions.

The sha256sums seem to be set to SKIP, which you really don't want! You want the actual hash in there to verify the source tarball.

This is currently not building for me because -Werror is enabled by default:

cc1plus: all warnings being treated as errors
make: *** [Makefile:3172: UnstagedMenu.o] Error 1
make: *** Waiting for unfinished jobs....
In file included from /usr/include/qt/QtCore/qstring.h:2168,
                 from /usr/include/qt/QtCore/qhashfunctions.h:44,
                 from /usr/include/qt/QtCore/qvector.h:47,
                 from /usr/include/qt/QtCore/QVector:1,
                 from src/cache/CommitInfo.h:26,
                 from src/git/GitRepoLoader.h:26,
                 from src/git/GitRepoLoader.cpp:1:
In static member function ‘static void QConcatenable<QByteArray>::appendTo(const QByteArray&, char*&)’,
    inlined from ‘static void QConcatenable<QStringBuilder<A, B> >::appendTo(const type&, T*&) [with T = char; A = QByteArray; B = char]’ at /usr/include/qt/QtCore/qstringbuilder.h:428:35,
    inlined from ‘T QStringBuilder<A, B>::convertTo() const [with T = QByteArray; A = QByteArray; B = char]’ at /usr/include/qt/QtCore/qstringbuilder.h:118:56,
    inlined from ‘QStringBuilder<A, B>::operator QStringBuilder<A, B>::ConvertTo() const [with A = QByteArray; B = char ’ at /usr/include/qt/QtCore/qstringbuilder.h:131:62,
    inlined from ‘QList<CommitInfo> GitRepoLoader::processSignedLog(QByteArray&, QList<QPair<QString, QString> >&) cons ’ at src/git/GitRepoLoader.cpp:304:23:
/usr/include/qt/QtCore/qstringbuilder.h:411:20: error: writing 1 byte into a region of size 0 [-Werror=stringop-overflow=]
  411 |             *out++ = *a++;
      |             ~~~~~~~^~~~~~
/usr/include/qt/QtCore/qstringbuilder.h:411:20: error: writing 1 byte into a region of size 0 [-Werror=stringop-overflow=]
/usr/include/qt/QtCore/qstringbuilder.h:411:20: error: writing 1 byte into a region of size 0 [-Werror=stringop-overflow=]
/usr/include/qt/QtCore/qstringbuilder.h:411:20: error: writing 1 byte into a region of size 0 [-Werror=stringop-overflow=]
/usr/include/qt/QtCore/qstringbuilder.h:411:20: error: writing 1 byte into a region of size 0 [-Werror=stringop-overflow=]
/usr/include/qt/QtCore/qstringbuilder.h:411:20: error: writing 1 byte into a region of size 0 [-Werror=stringop-overflow=]
/usr/include/qt/QtCore/qstringbuilder.h:411:20: error: writing 1 byte into a region of size 0 [-Werror=stringop-overflow=]

I've submitted a PR upstream if you want to take the patch for the PKGBUILD: https://github.com/francescmm/GitQlient/pull/214

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.

Hi,

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: https://github.com/francescmm/GitQlient/issues

Stay healthy and safe! :D

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.

Seems like qlogger package doesn't exist anymore

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

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' {} \;

Would anybody be interested in creating a package for GitQlient Beta that just features the AppImage? https://github.com/francescmm/GitQlient/releases/tag/v1.3.0-beta