From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: calm/mksetupini changes
Date: Sat, 26 Jun 2021 14:29:48 +0100 [thread overview]
Message-ID: <c854a622-a4ec-cec1-5024-e329e58ad502@dronecode.org.uk> (raw)
In-Reply-To: <24584cd3-406a-3ad1-ffe5-b2855f992627@dronecode.org.uk>
On 28/03/2020 19:26, Jon Turney wrote:
> I've recently deployed some updates to calm, which change a few things
> maintainers may notice:
Been a while since I wrote one of these mails:
* Meaningless keys in .hint or src.hint files are now disallowed
- 'requires:' and 'obsolete:' are not allowed in src.hint files
- 'skip:' is not allowed in hint files
In the unlikely event that:
- you have a private package repository, AND
- you run calm version >= 20210626
You'll might need to successfully run 'calm-tool fix-invalid-key-hint'
on that repository, to drop those invalid keys, before you can use calm
or mksetupini.
* 'homepage:' is now mandatory in uploaded src.hint
(or HOMEPAGE must exist in the .cygport, if you are using a cygport so
old it doesn't generate src.hint files)
* Upload of a 0-byte file in place of a empty compressed archive is no
longer permitted
(cygport stopped generating such anomalies years ago)
* The 'virtual' is now allowed in 'category:', and indicates to calm
that this package only exists to pull in other packages (i.e. is empty,
but has dependencies, which it otherwise might warn about).
next prev parent reply other threads:[~2021-06-26 13:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-28 19:26 Jon Turney
2021-06-26 13:29 ` Jon Turney [this message]
2022-05-21 20:31 ` Jon Turney
2022-05-23 13:09 ` Lemures Lemniscati
2022-05-23 18:12 ` Achim Gratz
2022-05-23 18:44 ` Achim Gratz
2022-05-24 9:50 ` Lemures Lemniscati
2022-05-23 18:37 ` Jon Turney
2022-05-24 10:05 ` Lemures Lemniscati
2022-05-24 12:57 ` Jon Turney
2022-05-26 8:55 ` Lemures Lemniscati
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=c854a622-a4ec-cec1-5024-e329e58ad502@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--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).