Package Details: nginx-mainline-mod-fancyindex 0.5.2-3

Git Clone URL: https://aur.archlinux.org/nginx-mainline-mod-fancyindex.git (read-only, click to copy)
Package Base: nginx-mainline-mod-fancyindex
Description: Fancy index module for the nginx-mainline web server
Upstream URL: https://www.nginx.com/resources/wiki/modules/fancy_index/
Keywords: module nginx
Licenses: BSD
Submitter: hdhoang
Maintainer: morgenstern
Last Packager: morgenstern
Votes: 13
Popularity: 0.000008
First Submitted: 2017-05-23 02:20 (UTC)
Last Updated: 2022-06-07 11:41 (UTC)

Pinned Comments

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

sampsoncrowley commented on 2020-08-24 23:57 (UTC)

Repo with updated PKGBUILD for nginx 1.19.2 => https://github.com/SampsonCrowley/arch_packages/tree/master/nginx-mainline-mod-brotli

https://raw.githubusercontent.com/SampsonCrowley/arch_packages/4a10fb1435be85d2cbb9387734c4f4aa7beaab2f/nginx-mainline-mod-brotli/PKGBUILD

sampsoncrowley commented on 2020-08-24 23:55 (UTC)

if you get an nginx-1.19.2.tar.gz ... FAILED (unknown public key 520A9993A1C052F8) ==> ERROR: One or more PGP signatures could not be verified! error, use the following line to pull in the right keys (also mentioned below, but below solution doesn't contain a keyserver to use like this does)

gpg --keyserver pool.sks-keyservers.net --recv-keys 520A9993A1C052F8

SibrenVasse commented on 2019-01-30 22:33 (UTC)

Please fix the .SRCINFO

wangqr commented on 2018-03-31 12:27 (UTC)

Currently `pkgrel' in .SRCINFO and PKGBUILD don't match. AUR helpers (eg. yaourt) now always think that there is a new version, because the pkgrel in AUR(4) is greater than installed(3).

hdhoang commented on 2018-03-28 09:59 (UTC)

This is awkward: the PKGBUILD determines nginx version at build time, and downloads the corresponding source. In the -4 release bump, I deleted that version line from .SRCINFO so that nginx doesn't show up in Sources list above.

When a new nginx-mainline release enters [community], I will bump the release number again to trigger rebuild for you. [community-testing] users would need to rebuild on their own.

hdhoang commented on 2017-10-21 02:18 (UTC)

Thank you for your concern. I have switched to verifying the nginx source by PGP signature instead of checksum, because testing users may have different nginx version than I do. Please verify that that fingerprint is the proper nginx signing key's (e.g. by looking for it in the PKGBUILD), then import it into your builder's gpg keyring https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/nginx-mainline gpg --recv-keys 520A9993A1C052F8

levinit commented on 2017-10-21 02:02 (UTC)

Verifying source file signatures with gpg... nginx-1.13.5.tar.gz ... FAILED (unknown public key 520A9993A1C052F8) ==> ERROR: One or more PGP signatures could not be verified! ==> ERROR: Makepkg was unable to build nginx-mainline-mod-fancyindex. ==> Restart building nginx-mainline-mod-fancyindex ? [y/N]

hdhoang commented on 2017-07-20 02:49 (UTC)

I think -6 has fixed that. I'll also notify other module packagers

« First ‹ Previous 1 2 3 4 Next › Last »