The epoch was just stuck from an early version and forgot to remove it, it is going to be removed on next version now. This is version 2 as it is provided by Amazon as the default today, don't understand why version 1 is still being served by the official arch repo. Even if you visit the v1 CLI page explicitly it says "We recommend that you use AWS CLI version 2 instead", it looks like a deprecation message to me...
Can someone explain why epoch is used in PKGBUILD? According to https://wiki.archlinux.org/title/PKGBUILD it should be used only if "absolutely required to do so". I would like to understand this. It confused me as I thought this is the version 1 of the aws-client. I think versioning should not be confusing.
@tmoore please run either 'pacman-key --refresh-keys' or 'gpg --refresh-keys' on your system, the key has been extended with the same signature.
@nsyntych You need to update the proper PGP key from the link you mention in your PKGBUILD. It's expired now
pub rsa4096 2019-09-18 [SC] [expired: 2023-09-17] FB5DB77FD5C118B80511ADA8A6310ACC4672475C uid [ expired] AWS CLI Team aws-cli@amazon.com
Well... every other project I have come across in AUR and in the main arch repos uses 'Apache' instead of 'Apache-2.0' and that is what I replicated here.
If the point though is to use the SPDX license identifiers, I agree that 'Apache-2.0' is the correct one and I will change it.
I am curious to see every package complying though from now on, we have a looong way.
I think the license string should be 'Apache-2.0', not 'Apache'
my bad, should be ok now.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
Actually putting the epoch back since if we remove it now it creates an upgrade loop. Other than creating an "ugly" version in the package I don't see any issue on keeping it now to avoid the loop.