From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] FTBFS: zaproxy
Date: Mon, 16 Sep 2019 07:34:08 +0200 [thread overview]
Message-ID: <20190916053408.VnbjRfyxpr4ln5eoilRmpFAMylbq40tKgMNVoXFvclA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-13607@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 819 bytes --]
Closed issue by the-maldridge on void-packages repository
https://github.com/void-linux/void-packages/issues/13607
Description:
zaproxy fails to build from source at release tag v2.8.0. Given that upstream provided documentation no longer is sufficient to generate a build, and that the software in question is a massive java executable that would not normally satisfy our quality requirements for inclusion, zaproxy will be dropped from the maintained set on the 20th of August unless input is provided from the zaproxy team for updates.
In general zaproxy needs a new home. I inherited it from someone who left the project and I don't particularly care about it. If you are interested in taking over maintainership for it, feel free to submit a PR taking it off my hands and mention me in the PR description.
parent reply other threads:[~2019-09-16 5:34 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-13607@inbox.vuxu.org>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190916053408.VnbjRfyxpr4ln5eoilRmpFAMylbq40tKgMNVoXFvclA@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).