public inbox for
 help / color / mirror / Atom feed
From: Jon Turney <>
To: "" <>
Subject: calm/mksetupini changes
Date: Sat, 28 Mar 2020 19:26:17 +0000	[thread overview]
Message-ID: <> (raw)

I've recently deployed some updates to calm, which change a few things 
maintainers may notice:

* test: and prev: lines are no longer permitted in override.hint

Instead of test:, use the test: label in the pvr.hint to mark test 
packages (which 'cygport package-test' or 'all-test' add for you)

prev: doesn't really mean anything anymore (since setup hasn't supported 
specifically installing the prev: version since 2011 (setup version 
2.761. See [1])). keep: is a more flexible replacement.


* package retention has been slightly adjusted

By default, we now retain in the relarea up to 3 non-test versions, and 
up to 2 test versions.

This can be tuned on a per-package basis using the various keep*: lines 
in override.hint. See [2]


* calm now uses a separate pvr-src.hint in the relarea

This should have no externally visible effect (e.g. generated setup.ini 
is not significantly changed), but it enables some complexity (some of 
which isn't implemented properly) to be removed from calm.

At upload, if not present, this hint is created from the corresponding 
pvr.hint by copying (if an install package also exists) or moving (if it 
doesn't) it.

I have written a patch to cygport to generate packages in this form [3], 
but that's not yet in any released cygport.


In the unlikely event that:

- you have a private package repository, AND
- you run calm version >= 20200328

You'll need to successfully run 'calm-tool fix-missing-src-hint' on that 
repository before you can use calm or mksetupini.

Additionally, there have been a few other related changes:

* md5.sum files are no longer generated in the relarea.  (use the 
sha512.sum files instead)

* The '!packages' files in maintainer upload directories (which only 
exist for historical reasons, and haven't been updated for a while) have 
been removed. (The authoritative source of this information is [4])


             reply	other threads:[~2020-03-28 19:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-28 19:26 Jon Turney [this message]
2021-06-26 13:29 ` Jon Turney
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).