From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-apps@cygwin.com
Cc: Andy Li <andy@onthewings.net>
Subject: Re: mbed TLS package
Date: Sat, 29 Apr 2017 11:33:00 -0000 [thread overview]
Message-ID: <9b58d89c-0805-eddf-6ac0-6b0730c8de06@dronecode.org.uk> (raw)
In-Reply-To: <CAM-5HMt3x1vNA1yWgkJdezpQfbOSL6X1xE=qDKr8dERbWs0-Gg@mail.gmail.com>
On 29/04/2017 12:10, Andy Li wrote:
> I've just tried to upload the package, and calm notified me about the
> errors as follows:
>
>> ERROR: package 'libmbedtls10' version '2.4.2-1' requires nonexistent package 'libmbedx509'
>> ERROR: package 'mbedtls-devel' version '2.4.2-1' requires nonexistent package 'libmbedx509'
>> ERROR: error while validating merged x86 packages for Andy Li
>> SUMMARY: 3 ERROR(s)
>
> Maybe it's because of "libmbedx509" having a number at the end of its
> name, incorrectly interpreted as its version number (0)?
> Its package name is "libmbedx509-0".
Using a package name containing a hyphen followed by a digit isn't
actually forbidden currently, but perhaps should be. It introduces an
ambiguity about where the version starts.
This seems to tickle a bug somewhere in cygport as it doesn't generate
the requires: correctly
It would be much better if cygport just said "no" when you tried to use
a package name with a hyphen followed by a digit.
> Any tips to fix it is appreciated.
Name the package 'libmbedx509_0'
See [1], which we generally follow:
"If the base package name ends with a digit, a single underscore ("_")
MUST be appended to the name, and the version MUST be appended to that,
in order to avoid confusion over where the name ends and the version
begins."
[1]
https://fedoraproject.org/wiki/Packaging:Naming?rd=Packaging:NamingGuidelines#MultiplePackages
next prev parent reply other threads:[~2017-04-29 11:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 5:33 Andy Li
2017-04-28 21:14 ` Marco Atzeri
2017-04-28 21:32 ` Tony Kelman
2017-04-29 7:27 ` Andy Li
2017-04-29 8:10 ` Marco Atzeri
2017-04-29 9:21 ` Andy Li
2017-04-29 9:39 ` Marco Atzeri
2017-04-29 11:10 ` Andy Li
2017-04-29 11:33 ` Jon Turney [this message]
2017-04-29 14:14 ` Andy Li
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=9b58d89c-0805-eddf-6ac0-6b0730c8de06@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=andy@onthewings.net \
--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).