From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Cc: Jari Aalto <jari.aalto@cante.net>
Subject: Re: Security update needed for mercurial (upload error: doesn't follow naming convention)
Date: Wed, 20 Apr 2016 17:14:00 -0000 [thread overview]
Message-ID: <20160420170827.GG25668@calimero.vinschen.de> (raw)
In-Reply-To: <20160420165640.GB9640@piccolo>
[-- Attachment #1: Type: text/plain, Size: 817 bytes --]
On Apr 20 19:56, Jari Aalto wrote:
> > 3.7.3 as a security release, with fixes for:
> >
> > CVE-2016-3630 Mercurial: remote code execution in binary delta decoding
> > CVE-2016-3068 Mercurial: arbitrary code execution with Git subrepos
> > CVE-2016-3069 Mercurial: arbitrary code execution when converting Git repos
>
> New release uploaded, but I got this message (x64)?
>
> ERROR: tar file 'mercurial-3.7.3.tar.gz' in package 'mercurial' doesn't follow naming convention
> ERROR: error while reading uploaded packages for Jari Aalto
Our new calm tool (courtesy Jon Turney) now checks packages for
validity. Shouldn't that be 3.7.3-1?
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-04-20 17:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-02 17:52 Updated package needed for mercurial 3.7.3 security update Andy Moreton
2016-04-19 18:22 ` Security update needed for mercurial Andy Moreton
2016-04-20 9:00 ` Corinna Vinschen
2016-04-20 17:08 ` Security update needed for mercurial (upload error: doesn't follow naming convention) Jari Aalto
2016-04-20 17:14 ` Corinna Vinschen [this message]
2016-04-20 17:22 ` Jon Turney
2016-04-20 18:16 ` Warren Young
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=20160420170827.GG25668@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
--cc=jari.aalto@cante.net \
/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).