From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: Request for review: wavpack 5.3.0
Date: Tue, 13 Jul 2021 17:45:30 +0100 [thread overview]
Message-ID: <49de482f-ecad-6e83-31d1-6104d46c2b1d@dronecode.org.uk> (raw)
In-Reply-To: <454f07d4-4a3d-27d2-31f4-9eddfafffb09@dronecode.org.uk>
On 25/08/2020 16:42, Jon Turney wrote:
> On 12/06/2020 10:52, Marco Atzeri via Cygwin-apps wrote:
>> On 12.06.2020 10:42, Yasuhiro KIMURA wrote:
>>> Update wavpack to 5.3.0. Patches to fix security vulnerabilties are
>>> already included in this version. So they are removed.
>>>
>>> wavpack.cygport
> [...]
>> it builds fine.
>> I assume you have checked that the 3 previous patches are not
>> needed anymore and you have performed some type of tests.
>>
>> I see the test test suites is a bit large and out of the
>> main source package.
>>
>> It seems GTG if you can confirm the previous points
>
> While doing a maintainer key update today, I notice that Marco has added
> you the maintainer for 'wavpack', but you don't have a ssh key registered.
>
> If you are still interested in doing that, please provide a ssh key (as
> per [1]), so you can build and upload packages (as per [2]).
>
> If not, please let me know.
No response, so I've moved this package back to orphaned, and NMU'ed
based on the provided cygport.
>
> Sorry about the delay.
>
> Thanks.
>
> [1] https://cygwin.com/packaging/key.html
> [2] https://cygwin.com/package-upload.html
>
prev parent reply other threads:[~2021-07-13 16:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 8:42 Yasuhiro KIMURA
2020-06-12 9:52 ` Marco Atzeri
2020-08-25 15:42 ` Jon Turney
2021-07-13 16:45 ` Jon Turney [this message]
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=49de482f-ecad-6e83-31d1-6104d46c2b1d@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).