Package Details: qtutilities 6.14.0-1

Git Clone URL: (read-only, click to copy)
Package Base: qtutilities
Description: Common Qt related C++ classes and routines used by my applications such as dialogs, widgets and models
Upstream URL:
Licenses: GPL
Submitter: Martchus
Maintainer: Martchus
Last Packager: Martchus
Votes: 41
Popularity: 1.06
First Submitted: 2015-08-27 19:16 (UTC)
Last Updated: 2024-04-02 17:49 (UTC)

Dependencies (7)

Required by (8)

Sources (1)

Pinned Comments

Martchus commented on 2016-05-18 22:04 (UTC) (edited on 2023-03-09 14:53 (UTC) by Martchus)

All my packages are managed at GitHub where you can also contribute directly: There also exist a binary repository:

The problem with the flag comment is that it goes away once the flagging is removed and it is generally less obvious what my comment was referring to.

Latest Comments

1 2 Next › Last »

Martchus commented on 2023-03-09 14:50 (UTC)

I didn't update pkgrel so users who built the package despite the checksum mismatch are not retriggered to build the package again. I suppose the AUR helper should rather check whether there was a new commit for this kind of caching.

gioan777 commented on 2023-03-09 12:51 (UTC) (edited on 2023-03-09 13:00 (UTC) by gioan777)

@Martchus Actually any registered AUR user can see the flag comment just by clicking on the red link. E.g. Here's from a random out of date AUR package

I still have the issue with the sha256sum and PKGBUILD here seems to the have correct sha256sum, however I found out that my AUR helper pulls the older version with the wrong checksum. I suspect it's because you didn't update the pkgrel along with the checksums so my AUR helper doesn't know there's a newer fixed version.

Martchus commented on 2023-03-09 09:48 (UTC)

Please don't flag packages if there's a problem. Nobody can see the problem you've stated except me this way.

Note that I have updated the checksum yesterday. The checksum of the archive seems to be 8b49fabea6f86a3665c4e3e7d4a9a4d4392549ce942f5de4f21b694126fea23b which is also in accordance with what two other users have reported before. I've just downloaded the archive again from GitHub and ran sha256sum and still get 8b49fabea6f86a3665c4e3e7d4a9a4d4392549ce942f5de4f21b694126fea23b. So there is likely a problem on your side.

OdinVex commented on 2023-03-07 22:11 (UTC)

@Martchus, I also get an HMAC-SHA256 of 8b49fabea6f86a3665c4e3e7d4a9a4d4392549ce942f5de4f21b694126fea23b for qtutilities-6.11.0.tar.gz. The pkgbuild needs correction.

Martchus commented on 2023-03-07 22:11 (UTC)

Likely just a bug in my release script (that causes it to update the checksum for the preliminary self-crafted archive). I'll run the script next time I'm on the computer again.

noplomplom commented on 2023-03-07 21:59 (UTC)

Validity check fails. For qtutilities-6.11.0.tar.gz I have 8b49fabea6f86a3665c4e3e7d4a9a4d4392549ce942f5de4f21b694126fea23b as sha256sum.

kinoe commented on 2022-10-05 16:44 (UTC)

 qtutilities-6.9.0.tar.gz found
==> Check source files with sha256sums...
    qtutilities-6.9.0.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!
 -> Error during build: qtutilities

clonejo commented on 2021-03-01 21:35 (UTC)

@Martchus: Thanks, it qtutilities does compile and syncthingtray does work just fine. On i3wm with X11. I even tried reinstalling libx11, which did not help.

Martchus commented on 2021-03-01 09:48 (UTC)

@clonejo I haven't seen that problem so far. The code is also just relying on CMake's standard find module for finding X11. This feature is actually not used within Syncthing Tray so you can simply add -DCAPSLOCK_DETECTION=OFF to the CMake arguments as a workaround. (Note that you should definitely should have X11 libs on your system at the point of building this package because we're pulled in by Qt even if you just use Wayland.)