aurupdater

mdcat

Build times (auto-updated)

Build times (auto-updated)

Not yet vendored under arch/ (as of 2026-09-19). Tracking notes ahead of adoption so nothing gets lost.

Background

Known issue – FIXED locally 2026-09-19, not yet pushed

2026-09-27: adoption completed, published for the first time

AUR adoption went through (RPC now shows Maintainer: andreas_baumann) and a real submodule now exists at arch/maintained/mdcat. Found it staged with the Maintainer: header and pkgrel (1 -> 2) already updated, but missing the actual checkdepends=('less') fix documented above – likely lost when re-cloning fresh partway through that earlier investigation. Re-added it before building; without it this would have failed check() again with the exact same ZEBofx-reported error.

i686 fails for an unrelated, unfixable-here reason: cargo fetch --locked pulls idna_adapter 1.2.2 (a transitive dependency), whose Cargo.toml requires the edition2024 Cargo feature – not stabilized in archlinux32’s own official i686 rust package (1:1.81.0-1.0, built September 2024, confirmed via pacman -Si and Packager: TasosSah – a genuine upstream toolchain-lag issue in the third-party archlinux32 project itself, not something in our own PKGBUILD or infrastructure). x86_64’s rust/cargo is current and unaffected. Not fixed – would need archlinux32 itself to update its rust package, out of scope. arch=('i686' 'x86_64') left as-is (matches upstream); i686 just won’t build until that catches up.

Built + published clean, x86_64 only, 2.17.0-2. All 39 tests passed including the mdpick/less-spawning one the fix targets.

2026-09-28: routine check – fixed a stale .nvchecker.toml tracking the wrong (dead) upstream

Asked to “check and update mdcat”. Upstream’s real tags (git ls-remote --tags against BIRSAx2/mdcat) top out at 2.17.0 – matches the published pkgver exactly, so no version bump needed.

scripts/check_for_updates_maintained.sh --only maintained/mdcat reported OK ... 2.17.0 2.7.1, which looked suspicious (that second number should be the detected upstream version, and 2.7.1 is far below our 2.17.0) – root-caused to .nvchecker.toml still pointing git = "https://github.com/swsnr/mdcat.git", the original abandoned upstream (see the “Background” section above – this project switched to tracking the BIRSAx2/mdcat fork a while ago, but apparently only the PKGBUILD’s own source= URL got updated at the time, not the nvchecker config). 2.7.1 is just the last tag that dead repo ever got. The check only reported “OK” by coincidence (our real version numerically exceeds the stale target it was comparing against) – it was never actually validating against real current upstream, and would silently miss a real new BIRSAx2 release forever (vercmp would never see it as newer than a frozen 2.7.1). Fixed by pointing .nvchecker.toml at BIRSAx2/mdcat – re-ran the check, now correctly reports 2.17.0 2.17.0. Also added an STATES.txt entry for this package (never had one – vendored after the last full check run).

2026-10-01: routine bump 2.17.0 -> 2.18.0

Full update_cycle.sh UPD flag. Upstream tarball + sha256 fetched clean via updpkgsums. Dependency tree has grown substantially since 2.17.0 – now pulls in resvg/usvg/tiny-skia/ratatui-image etc. (image/SVG rendering in the terminal, presumably inline-image support), ~300+ crates vs. a much smaller set before. Built x86_64-only as usual (i686 still blocked by archlinux32’s stale rust package, see below). All 39 tests passed, built+signed+published cleanly, old 2.17.0-2 archived.

2026-10-20: routine bump 2.18.0 -> 2.19.0

Full update_cycle.sh UPD flag. Tarball confirmed on GitHub before touching PKGBUILD. updpkgsums clean. Built x86_64-only as always – i686 still blocked by archlinux32’s own stale rust package (see the 2026-09-27 entry above), unchanged since last checked. Published cleanly, old 2.18.0-1 archived.

Current AUR PKGBUILD snapshot (2.17.0-1, for reference)