From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>,
Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
Subject: Re: curl calm issue
Date: Tue, 1 Dec 2020 15:34:06 +0000 [thread overview]
Message-ID: <1065dd05-8b66-b2bc-fe90-3aead06beda0@dronecode.org.uk> (raw)
In-Reply-To: <71b97bcc-62dc-c79b-f987-5464cfd99775@SystematicSw.ab.ca>
On 01/12/2020 01:06, Brian Inglis wrote:
> On 2020-11-30 17:09, cygwin-apps-rDBXBDvO6BXQT0dZR+AlfA@public.gmane.org
> wrote:
>> WARNING: homepage:https://curl.haxx.se/ permanently redirects to
>> https://curl.se/
>> ERROR: install packages from source package 'curl' have non-unique
>> current versions 7.73.0-1 (curl-debuginfo), 7.73.0-2 (3 others)
>> ERROR: error while validating merged x86_64 packages for Brian Inglis
>> SUMMARY: 1 WARNING(s), 2 ERROR(s)
I've added an exception for this package, and set the upload to be retried.
> The issue is that previous releases were always generated with
> debuginfo, but the latest release also changes debug behaviour to
> strictly check SSL protocol, causing execution issues with users and
> downstreams.
>
> I would like to generate the updated release without the behaviour
> change and that appears to also eliminate debuginfo generation.
>
> If I need to generate release -2 without debuginfo, how do I avoid this
> issue?
Alternatively, you could have added lines to the .cygport to explicitly
create an empty curl-debuginfo package (or make it obsolete, but that
seems contraindicated if the package is coming back in future versions).
next prev parent reply other threads:[~2020-12-01 15:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <160678137911.641109.8028997546055063113@server2.sourceware.org>
2020-12-01 1:06 ` Brian Inglis
2020-12-01 6:02 ` ASSI
2020-12-01 15:34 ` Jon Turney [this message]
2020-12-01 16:26 ` Brian Inglis
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=1065dd05-8b66-b2bc-fe90-3aead06beda0@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=Brian.Inglis@SystematicSw.ab.ca \
--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).