libgnt

• Path: arch/maintained/libgnt
• .nvchecker.toml scrapes the SourceForge files listing (https://sourceforge.net/projects/pidgin/files/libgnt/) with regex libgnt/([\d.]+)/.

2026-11-11: 2.14.4-2 -> 2.15.0-1, two real fixes needed (not a plain pkgver bump)

Full update_cycle.sh UPD flag. Two genuine upstream changes surfaced, both confirmed before touching the PKGBUILD (checked with the user first per the non-routine-PKGBUILD-change policy, since this is more than a version-number edit):

1. Release tarball filename lost its -dev suffix. Every prior release was published as libgnt-<ver>-dev.tar.xz (confirmed via the 2.14.4 SourceForge listing); starting with 2.15.0 it’s just libgnt-<ver>.tar.xz – confirmed live via the SourceForge files page for 2.15.0/ (libgnt-2.15.0.tar.xz present, no -dev variant at all). Updated source= to drop the -dev infix, and removed prepare()’s mv -v $pkgname-$pkgver{-dev,} entirely – the tarball now extracts straight to libgnt-2.15.0/, matching what build() already expects, so the rename step is no longer needed at all (not just renamed).
2. meson.build dropped the python2 option. The PKGBUILD’s build() passed -D python2=false to arch-meson; 2.15.0’s meson_options.txt only defines doc now (the python2 toggle – presumably a Python-2-bindings switch – was removed upstream). Build failed immediately with ERROR: Unknown option: "python2". Fix: dropped the -D python2=false flag from build() entirely.

Both confirmed directly against the extracted 2.15.0 tarball (meson_options.txt, meson.build) before editing, not guessed. PGP key (40DE1DC7288FE3F50AB938C548F66AFFD9BDB729, Gary Kramlich) refresh hit the usual keyserver timeout but the local cache was already present and current, so this was a no-op. pkgrel reset to 1 for the version bump as usual. Built+published cleanly x86_64-only after the fix, old 2.14.4-2 archived.

Namcap flagged license=('GPL') as not SPDX-conformant (wants GPL-1.0-or-later or similar) – cosmetic linter nitpick, not acted on (pre-existing, not introduced by this update).

If this package gets another upstream bump, check the SourceForge listing’s actual filename again before assuming source=’s -dev-less pattern is permanent – only one data point (2.15.0) confirms the new convention so far.