public inbox for
 help / color / mirror / Atom feed
From: Jon Turney <>
To: "" <>
Subject: Re: calm/mksetupini changes
Date: Sat, 21 May 2022 21:31:46 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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:

* reports are now sent to package maintainers when vaulting old 
packages, even when that's not caused by an upload (e.g. due to a change 
of test: status, or expiry policy)

* the names of packages which have been completely removed are 
remembered so they are valid to appear in obsoletes:

* packages without a maintainer are given the additional category 
'Unmaintained' in setup.ini

* package expiry refinements:

- an empty, sourceless debuginfo package, or a useless debuginfo and 
source package pair will be expired

- unused, deprecated, old shared library versions can be expired

unused: no packages depend on it (rdepends is empty)
deprecated: a later soversion exists (or the solibrary is no longer 
generated by the source package)
old: over some threshold for package age

At the moment, the package age threshold is set sufficiently high that 
no packages are selected, but I will be gradually winding it forward, to 
observe the effect on a small number of packages at a time.

Eventually, this should eliminate packages in the deprecated so report 
[1] with a rdepends count of zero.  To reduce the rdpepends count to 
zero, packages which depend on a deprecated soversion need to be rebuilt 
for a newer soversion.


  reply	other threads:[~2022-05-21 20:31 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
2022-05-21 20:31   ` Jon Turney [this message]
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).