From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: Fwd: calm: cygwin package upload report
Date: Mon, 7 Sep 2020 12:58:46 -0600 [thread overview]
Message-ID: <9def5ac0-d1c3-b701-43d1-f6a253129e2e@SystematicSw.ab.ca> (raw)
In-Reply-To: <7cd70592-ca8e-d9ae-ba3c-934aec1b92bb@dronecode.org.uk>
On 2020-09-07 08:04, Jon Turney wrote:
> On 06/09/2020 18:09, Brian Inglis wrote:
>> Hi folks,
>>
>> Any ideas how to fix these complaints about nonexistent packages?
>> These mingw64 packages do not yet have any DEPENDS/BUILD_REQUIRES but unsure
>> what if anything to add other than base with cross tools.
>>
>>> ERROR: package 'mingw64-x86_64-curl' version '7.72.0-1' requires:
>>> 'mingw64-x86_64-autoconf', but nothing satisfies that
>>> ERROR: package 'mingw64-x86_64-curl' version '7.72.0-1' requires:
>>> 'mingw64-x86_64-automake', but nothing satisfies that
>>> ERROR: package 'mingw64-x86_64-curl' version '7.72.0-1' requires:
>>> 'mingw64-x86_64-libssl', but nothing satisfies that
>>> ERROR: package 'mingw64-x86_64-curl' version '7.72.0-1' requires:
>>> 'mingw64-x86_64-openldap', but nothing satisfies that
>>> ERROR: package 'mingw64-x86_64-curl' version '7.72.0-1' depends:
>>> 'mingw64-x86_64-autoconf', but nothing satisfies that
>>> ERROR: package 'mingw64-x86_64-curl' version '7.72.0-1' depends:
>>> 'mingw64-x86_64-automake', but nothing satisfies that
>>> ERROR: package 'mingw64-x86_64-curl' version '7.72.0-1' depends:
>>> 'mingw64-x86_64-libssl', but nothing satisfies that
>>> ERROR: package 'mingw64-x86_64-curl' version '7.72.0-1' depends:
>>> 'mingw64-x86_64-openldap', but nothing satisfies that
>
> Your uploaded mingw64-x86_64-curl-7.72.0-1.hint contains:
>
> requires: bash mingw64-x86_64-autoconf mingw64-x86_64-automake
> mingw64-x86_64-libssh2 mingw64-x86_64-libssl mingw64-x86_64-openldap pkg-config
>
> so these complaints seems correct.
>
> If these aren't coming from a REQUIRES in your .cygport, but are being
> automatically added by cygport, that would seem to be a bug there.
>
> Can you show the .cygport file you are using?
Don't even look at hints to check normally.
Pushed to:
https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/mingw64-x86_64-curl.git;a=blob;f=mingw64-x86_64-curl.cygport
https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/mingw64-i686-curl.git;a=blob;f=mingw64-i686-curl.cygport
minimal changes to version and URLs to https:, but 2.5 years of calm and cygport
changes.
I could try to add base and cross-tools BUILD_REQUIRES/DEPEND to see what
changes, but would prefer that to be knowledge-driven by what affects hints.
Please share what mingw64 package maintainers may have to adjust for new releases.
For comparison, base tools required are shown in:
https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/curl.git;f=curl.cygport;a=blob
which I found there has to be built in a single line, but these builds don't
appear to use of the lib or even -devel packages, only a few ming64-*86*-...
packages, which by definition are all effectively ...-devel.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in IEC units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2020-09-07 18:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <159940427076.129275.12362571636574767638@server2.sourceware.org>
2020-09-06 17:09 ` Brian Inglis
2020-09-07 14:04 ` Jon Turney
2020-09-07 18:58 ` Brian Inglis [this message]
2020-09-07 21:00 ` Brian Inglis
2020-09-13 21:10 ` Brian Inglis
2020-09-14 4:52 ` ASSI
2020-09-14 7:28 ` Brian Inglis
2020-09-14 7:22 ` Brian Inglis
2020-09-14 7:22 ` Fwd: " 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=9def5ac0-d1c3-b701-43d1-f6a253129e2e@SystematicSw.ab.ca \
--to=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).