Created attachment 187656 [details]
Patch to upgrade to latest
The current version of p5-Paws is quite old. Please update to latest version.
The attached patch accomplishes this. The attached patch also include fixes that aren't yet released. Specifically:
Created attachment 187808 [details]
Patch updates to 0.36
Update to 0.36
Maintainer timeout. Take this PR
(In reply to pprocacci from comment #2)
can you upload the diff again?
I think, the attach has an error
The patch applied perfectly for me.
fetch -o p5-Paws-0.36.xz "https://bugs.freebsd.org/bugzilla/attachment.cgi?id=187808
patch < ./p5-Paws.0.36.diff
make -C ./p5-Paws install clean
I can confirm it works and applies cleanly as an .xz archive.
That said, the preferred way to upload it would be as plain-text patch: Bugzilla has quite good integration with patches, showing what changes before downloading things.
Please consider that for your next contributions! :)
This patch doesn't work, see: http://joneumbox.org/data/11-1-AMD64-ports/2018-05-30_09h25m49s/logs/errors/p5-Paws-0.36.log
====> Compressing man pages (compress-man)
====> Running Q/A tests (stage-qa)
Error: '/bin/bash' is an invalid shebang you need USES=shebangfix for 'bin/xml2yaml.sh'
Warning: devel/p5-Getopt-Long is present in Perl CORE. Check with `corelist Getopt::Long 0` and `corelist -a Getopt::Long` if the dependency is really needed or if it should be conditionally added depending on PERL_LEVEL
Warning: www/p5-HTTP-Tiny is present in Perl CORE. Check with `corelist HTTP::Tiny 0` and `corelist -a HTTP::Tiny` if the dependency is really needed or if it should be conditionally added depending on PERL_LEVEL
Notice: You have some Perl modules as dependencies but you do not have devel/p5-Module-CoreList installed, the perlcore QA check gets better results when using it, especially with older Perl versions.
*** Error code 1
make: stopped in /usr/ports/devel/p5-Paws
=>> Error: stage-qa failures detected
=>> Cleaning up wrkdir
===> Cleaning for p5-Paws-0.36
This should have been closed feedback timeout, with a comment clarifying that it was being closed due to not receiving an updated patch to address the failure outlined in comment 7.
Incidentally, please include logs as attachments not external URL references as they tend to go missing/stale over time ( this one is now 404).