Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#58152 - [openvas-manager] source file not found
Attached to Project:
Community Packages
Opened by Andreas Baumann (andreas_baumann) - Saturday, 07 April 2018, 06:22 GMT
Last edited by Christian Rebischke (Shibumi) - Thursday, 12 April 2018, 14:34 GMT
Opened by Andreas Baumann (andreas_baumann) - Saturday, 07 April 2018, 06:22 GMT
Last edited by Christian Rebischke (Shibumi) - Thursday, 12 April 2018, 14:34 GMT
|
DetailsDescription:
==> Validating source files with sha512sums... gvm-7.0.3.tar.gz ... Passed openvas-manager-7.0.3.tar.gz.sig ... Skipped ==> Verifying source file signatures with gpg... openvas-manager-7.0.3.tar.gz ... SOURCE FILE NOT FOUND ==> ERROR: One or more PGP signatures could not be verified! There is no openvas-manager on https://github.com/greenbone/ anymore. Additional info: * package version(s): 7.0.3-1 * config and/or log files etc. Steps to reproduce: makepkg -s |
This task depends upon
Closed by Christian Rebischke (Shibumi)
Thursday, 12 April 2018, 14:34 GMT
Reason for closing: Fixed
Additional comments about closing: Should be fixed now with the newest commit
Thursday, 12 April 2018, 14:34 GMT
Reason for closing: Fixed
Additional comments about closing: Should be fixed now with the newest commit
Comment by Doug Newgard (Scimmia) -
Saturday, 07 April 2018, 06:53 GMT
The problem here is just in the strange renaming of the source file. gpg doesn't know how to verify it with the wrong filename.
Comment by Christian Rebischke (Shibumi) -
Sunday, 08 April 2018, 17:32 GMT
mhh strange, do you really use the PKGBUILD I made? because it works fine for me. I have introduced a _pkgname variable in the newest release that sets the right source file.
Comment by Doug Newgard (Scimmia) -
Sunday, 08 April 2018, 17:34 GMT
No, you screwed up the source file name with _pkgname. I probably works for you because you still have the old source file around.
Comment by Eli Schwartz (eschwartz) -
Monday, 09 April 2018, 22:03 GMT
There's no reason to rename the files *right back to the original filenames* at all, that's not what the PKGBUILD feature is for...
Comment by Christian Rebischke (Shibumi) -
Thursday, 12 April 2018, 14:34 GMT
Indeed, my fault. Seems like I messed up the _pkgname a little bit. Checkout the newest PKGBUILD.