public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: [ANNOUNCEMENT] Updated: curl, libcurl{4, -devel, -doc}, mingw64-{x86_64, i686}-curl 7.86
Date: Tue, 1 Nov 2022 13:11:50 -0600	[thread overview]
Message-ID: <c1636f77-c50d-f573-83f9-60365e8f13f6@SystematicSw.ab.ca> (raw)

On 2022-10-31 06:28, Jon Turney wrote:
> On 31/10/2022 04:30, Cygwin curl Maintainer wrote:
>> The following packages have been upgraded in the Cygwin distribution:
>> * curl			7.86
>> * libcurl4			7.86
>> * libcurl-devel		7.86
>> * libcurl-doc		7.86
>> * mingw64-x86_64-curl	7.86
>> * mingw64-i686-curl		7.86

> Due to multiple reports of brokenness, I've withdrawn this version.

Sorry for that folks, and thanks for doing that Jon.
Wanted to get new curl out there promptly as it fixed a few CVEs.

Forgot I was dog-fooding gsasl 2.2 so long I neglected to even release to test, 
and that it had an ABI break, so needs to precede package upgrades.
Will release gsasl 2.2 as test then re-release curl 7.86 as test, with notes, so 
we can proceed from there.

-- 
Take care. Thanks, Brian Inglis			Calgary, Alberta, Canada

La perfection est atteinte			Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter	not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer	but when there is no more to cut
			-- Antoine de Saint-Exupéry

             reply	other threads:[~2022-11-01 19:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01 19:11 Brian Inglis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-10-31  4:30 Cygwin curl Maintainer
2022-10-31  8:46 ` Lemures Lemniscati
2022-10-31  8:53   ` Lemures Lemniscati
2022-10-31  9:45   ` Michael Soegtrop
2022-10-31 12:28 ` Jon Turney

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=c1636f77-c50d-f573-83f9-60365e8f13f6@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin@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).