Please fix the .SRCINFO
Search Criteria
Package Details: nginx-mainline-mod-fancyindex 0.5.2-3
Package Actions
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: | 14 |
Popularity: | 0.000867 |
First Submitted: | 2017-05-23 02:20 (UTC) |
Last Updated: | 2022-06-07 11:41 (UTC) |
Dependencies (2)
Required by (0)
Sources (1)
SibrenVasse commented on 2019-01-30 22:33 (UTC)
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
hdhoang commented on 2017-07-20 00:32 (UTC) (edited on 2017-07-20 00:33 (UTC) by hdhoang)
that option comes from nginx -V as part of this
--with-cc-opt='-march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -D_FORTIFY_SOURCE=2'
maybe the single quote got unwrapped somehow. I'll look into it.
dotted commented on 2017-07-19 16:03 (UTC)
aura >>= Building `nginx-mainline-mod-fancyindex`...
^[[3~==> Making package: nginx-mainline-mod-fancyindex 0.4.1-5 (Wed Jul 19 18:02:15 CEST 2017)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Downloading nginx-1.13.3.tar.gz...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 962k 100 962k 0 0 452k 0 0:00:02 0:00:02 --:--:-- 453k
-> Downloading v0.4.1.tar.gz...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 131 0 131 0 0 299 0 --:--:-- --:--:-- --:--:-- 299
100 21130 0 21130 0 0 21768 0 --:--:-- --:--:-- --:--:-- 21768
==> Validating source files with sha256sums...
nginx-1.13.3.tar.gz ... Passed
v0.4.1.tar.gz ... Passed
==> Extracting sources...
-> Extracting nginx-1.13.3.tar.gz with bsdtar
-> Extracting v0.4.1.tar.gz with bsdtar
==> Starting prepare()...
==> Starting build()...
./configure: error: invalid option "-mtune=generic"
==> ERROR: A failure occurred in build().
Aborting...
aura >>= Well, building `nginx-mainline-mod-fancyindex` failed.
Pinned Comments