Arch Linux User Repository

Could this be updated to the latest stable release ? Or orphan the package ?

准备中...

正在构建 storm...
正克隆到 'storm'...
remote: Enumerating objects: 44, done.        
remote: Counting objects: 100% (44/44), done.        
remote: Compressing objects: 100% (32/32), done.        
remote: Total 44 (delta 11), reused 43 (delta 10)        
展开对象中: 100% (44/44), 完成.
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   416  100   416    0     0    701      0 --:--:-- --:--:-- --:--:--   701
==> 正在创建软件包：storm 1.1.1-2 (2018年08月15日 星期三 16时06分13秒)
==> 正在检查运行时依赖关系...
==> 正在检查编译时依赖关系
==> 获取源代码...
  -> 正在下载 apache-storm-1.1.1.tar.gz...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0
curl: (22) The requested URL returned error: 404 Not Found
==> 错误： 无法下载 http://mirrors.hust.edu.cn/apache///storm/apache-storm-1.1.1/apache-storm-1.1.1.tar.gz
    正在放弃...

The package has to be updated to use apache-storm-1.2.1.tar.gz

Orphaning.

I have added GPG signature check so please be aware of the following:

`makepkg` will refuse to build this package unless you either:

- manually add upstream signing key to your GPG keyring with: `gpg --recv-keys <UPSTREAM_KEY(S)>`
- set your GPG config to automatically retrieve missing keys by adding `keyserver-options auto-key-retrieve` to your `~/.gnupg/gpg.conf`

Whichever you choose **will not sign nor trust** the downloaded key(s)and will thus **not** affect security checks of your keyring in any way.
On the other hand the provided `validpgpkeys` directive will allow `makepkg`to trust the given key(s) for this package build as **I**, the packageprovider, have checked these keys are bound to actual upstream accounts.

Sorry for the late answer.
When makepkg finds signature files it tries to check them but you need to have the corresponding keys imported first!
Anyway I commented out the 'asc' file so no gpg signature occurs. People willing to get makepkg to check them can uncomment the asc file and checksum for the PKGBUILD and import the corresponding key.

The build currently fails with:

==> Verifying source file signatures with gpg...
apache-storm-0.9.3.tar.gz ... FAILED (the public key ACEFE18DD2322E1E84587A148DE03962E80B8FFD is not trusted)
==> ERROR: One or more PGP signatures could not be verified!
==> ERROR: Makepkg was unable to build storm.
==> Restart building storm ? [y/N]

I needed to

gpg --keyserver pgp.mit.edu --recv-keys 8DE03962E80B8FFD
gpg --edit-key 8DE03962E80B8FFD
trust
5
exit

to get it working

I've just added a dynamic mirror choosing one-liner in the `source` directive. Let me know if you have issues with it.

The storm URL is no longer valid. Please update to http://www.apache.org/dyn/closer.cgi/storm/apache-storm-0.9.3/apache-storm-0.9.3.tar.gz