trojita-git
Build times (auto-updated)
- x86_64: 18m25s (2026-09-21 12:21 UTC, MAKEFLAGS=-j6)
2026-09-21: rebuilt to pick up upstream MR !92 (no patch needed)
AUR comment (bionade24, 2026-07-10) suggested patching in KDE MR !92
(a null-deref fix in search-result sorting) if it wasn’t merged
upstream soon. It was merged 2026-07-15 – so a plain fresh -git
rebuild (no PKGBUILD change) already includes the fix. Rebuilt
0.7.r839.g5aefb8f1-4 -> 0.7.r1012.g501875cf-1, built and published
cleanly, x86_64. No AUR reply posted (see [[python2]]’s 2026-09-21
entry for why).
- Path: arch/maintained/trojita-git
- User (Andreas Baumann) is the upstream AUR maintainer for this pkgbase
AND for the separate
trojita-qt5-gitpkgbase (seememory/trojita-qt5-git.md) – two genuinely different packages: this one is Qt6 (WITH_WEBKIT=OFF),trojita-qt5-gitis Qt5+WebKit.
2026-08-20: fixed a self-inflicted mixup, this is the Qt6 variant
- The mess: earlier this session (2026-08-17), this directory’s
PKGBUILD got overwritten to match
trojita-qt5-git’s content instead of its own real upstream. The giveaway that went unnoticed at the time: both AUR pkgbases (trojita-gitandtrojita-qt5-git) literally setpkgname=trojita-qt5-gitinside their own PKGBUILD – an upstream copy-paste inconsistency on the user’s own AUR side, which made it easy to mistake one for the other. When a cascade of missing Qt6 dependencies showed up during an earlier build attempt here, that was misread as “this qt5-named package is wrongly building against Qt6” and “fixed” by overwriting this directory withtrojita-qt5-git’s actual (Qt5+WebKit) content – backwards: this pkgbase is genuinely supposed to be Qt6, the cascade was just missing real dependencies, not evidence of drift. - Fix: restored from real upstream
(
cgit/aur.git/plain/PKGBUILD?h=trojita-git) verbatim, with one local deviation:pkgnamecorrected fromtrojita-qt5-git(the upstream copy-paste bug) totrojita-git, matching this directory’s actual identity.pkgdescfits either way (“A fast QT IMAP e-mail client”, no Qt5/webkit-specific claim – verified consistent with the Qt6/WITH_WEBKIT=OFFbuild). - Real missing dependencies, found and fixed one at a time by
actually building (not chasing forever – each was a genuine gap in
upstream’s own
depends=()):qt6-5compat(providesQt6Core5Compat,-- Could NOT find Qt6Core5Compat).kitemmodels(KF6 flavor, providesKF6ItemModels).qtkeychain->qtkeychain-qt6(upstream’s depends is stale on the pre-Qt6-split name, same class of fix asqtkeychain-qt5introjita-qt5-git).-DCMAKE_PREFIX_PATH=/usr/lib/cmake/QGpgmeQt5->QGpgmeQt6(upstream’s own build() still pointed at the Qt5 gpgme cmake config even though this is the Qt6 build).
- i686 dropped:
kitemmodels(KF6 flavor) isn’t ported to i686 on archlinux32 – only the old KF5-erakitemmodels5-lineage package exists there (confirmed via the official archlinux32 mirror listing,extra/kitemmodels-5.105.0-1.0-i686.pkg.tar.zst, no KF6 version). Unsatisfiable, not fixable locally.arch=(x86_64)only. User confirmed not to chase this further – KF6/Qt6 generally isn’t working on archlinux32 yet. pkgrelhistory:1(real upstream content, restored) ->2(qt6-5compat) ->3(kitemmodels) ->4(qtkeychain-qt6+QGpgmeQt6path + i686 drop) -> auto-reset to1by the-gitpkgver recompute picking up a newer upstream commit during the final successful build (0.7.r1004.g80ee0085vs ther839pinned earlier) – expected-gitbehavior, not a regression.- End state: x86_64 builds and publishes cleanly.