I don't think there's much I can do, that's the key the commit was signed with.
It's safe to ignore the warning.
Search Criteria
Package Details: libidn11 1.33-3
Package Actions
| Git Clone URL: | https://aur.archlinux.org/libidn11.git (read-only, click to copy) |
|---|---|
| Package Base: | libidn11 |
| Description: | Implementation of the Stringprep, Punycode and IDNA specifications |
| Upstream URL: | https://www.gnu.org/software/libidn/ |
| Licenses: | GPL3, LGPL |
| Submitter: | City-busz |
| Maintainer: | Damgaldor |
| Last Packager: | Damgaldor |
| Votes: | 13 |
| Popularity: | 2.87 |
| First Submitted: | 2025-10-28 10:02 (UTC) |
| Last Updated: | 2025-10-31 19:24 (UTC) |
Dependencies (4)
Required by (14)
Sources (2)
Damgaldor commented on 2026-03-14 17:15 (UTC)
mwerezak commented on 2026-03-06 23:22 (UTC) (edited on 2026-03-06 23:23 (UTC) by mwerezak)
Warning when building the package
==> Verifying source file signatures with gpg...
libidn git repo ... Passed (WARNING: the key has expired.)
==> WARNING: Warnings have occurred while verifying the signatures.
Please make sure you really trust them.
Damgaldor commented on 2025-12-10 00:16 (UTC)
Doing a clean build should resolve the issue
LeoM commented on 2025-12-09 22:08 (UTC)
The package always has updates, and whenever you install them, the version does not change. How do I get around this?
I have version: libidn11 1.33-2 and there is version libidn11 1.33-3 available, but I can't update.
forge commented on 2025-11-10 04:15 (UTC)
I needed to do "rm -rf ~/.cache/yay/libidn11" to get out of the loop, even telling yay to cleanbuild the package wasn't picking up the update. Fixed by manually blowing away the cached build.
vkulikov commented on 2025-11-05 17:45 (UTC)
resolved versioning issue
rm -rf ~/.cache/paru/clone/libidn11
vkulikov commented on 2025-11-05 17:42 (UTC)
Something is wrong with versioning. It is never stopping updating.
Aur (1) libidn11-1.33-3 != Making package: libidn11 1.33-2
Aur (1) libidn11-1.33-3
:: Proceed to review? [Y/n]:
:: Downloading PKGBUILDs... PKGBUILDs up to date nothing new to review fetching devel info... ==> Making package: libidn11 1.33-2 (Wed 05 Nov 2025 07:40:11 PM EET)
Damgaldor commented on 2025-10-31 19:24 (UTC)
For anyone having issues with the PGP key, yay imports it automatically, but you can also do it manually with
gpg --recv-keys 9AA9BDB11BB1B99A21285A330664A76954265E8C
Damgaldor commented on 2025-10-31 19:24 (UTC)
Thanks for the patch and reminding about pkgrel. Idk how I managed to update it in .SRCINFO, but not in PKGBUILD.
Fixed the pkgrel and applied the patch.
43615 commented on 2025-10-31 19:04 (UTC) (edited on 2025-10-31 19:09 (UTC) by 43615)
@gyscos Thanks for the tip, I guess paru's cache got into an inconsistent state due to the pkgrel rollback.
The pkgrels in the .SRCINFO and PKGBUILD are still different, which makes the upgrade repeat endlessly.
Pinned Comments
Damgaldor commented on 2025-10-31 19:24 (UTC)
For anyone having issues with the PGP key,
yayimports it automatically, but you can also do it manually with