* Re: A change to how calm expires packages
2022-01-20 14:33 A change to how calm expires packages Jon Turney
@ 2022-01-20 16:24 ` Ken Brown
2022-01-20 17:42 ` Achim Gratz
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: Ken Brown @ 2022-01-20 16:24 UTC (permalink / raw)
To: cygwin-apps
On 1/20/2022 9:33 AM, Jon Turney wrote:
> texlive-collection-latexrecommended-doc: untest 20210118-2 and expire 20210118-1
Yes, please. It was just a mistake that I never untested 20210118-2.
Ken
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: A change to how calm expires packages
2022-01-20 14:33 A change to how calm expires packages Jon Turney
2022-01-20 16:24 ` Ken Brown
@ 2022-01-20 17:42 ` Achim Gratz
2022-01-21 7:27 ` Brian Inglis
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: Achim Gratz @ 2022-01-20 17:42 UTC (permalink / raw)
To: cygwin-apps
Jon Turney writes:
> This change will cause the following packages to be removed:
>
> _autorebase-001091-0.1
> gcc-11.2.0-0
> mingw64-i686-gcc-11.1.0-0.1
> mingw64-i686-gcc-11.2.0-0
> mingw64-i686-gcc-7.3.0-1
> mingw64-x86_64-gcc-11.1.0-0.1
> mingw64-x86_64-gcc-11.2.0-0.1
> mingw64-x86_64-gcc-7.3.0-1
That looks about right, thanks.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: A change to how calm expires packages
2022-01-20 14:33 A change to how calm expires packages Jon Turney
2022-01-20 16:24 ` Ken Brown
2022-01-20 17:42 ` Achim Gratz
@ 2022-01-21 7:27 ` Brian Inglis
2022-01-21 10:11 ` Hamish McIntyre-Bhatty
2022-01-29 15:19 ` Jon Turney
4 siblings, 0 replies; 6+ messages in thread
From: Brian Inglis @ 2022-01-21 7:27 UTC (permalink / raw)
To: cygwin-apps
On 2022-01-20 07:33, Jon Turney wrote:
> To try to avoid packages lingering in the 'test' status indefinitely
> (which leads to them not being installed by most users, as they don't
> run setup with 'consider test packages' enabled, thus these packages
> generally aren't getting used, so having them isn't generating much
> value), I'm planning to change how calm expires packages:
>
> Currently (in the absence of configuration otherwise [1]), calm will
> retain up to 3 non-test versions, and 3 test versions, and expire all
> other versions.
>
> I plan to change this to also expire test versions which are superseded
> by a non-test version (that is: expire test versions where a non-test
> version with a higher version number exists).
>
> I believe this makes the default behaviour closer to what package
> maintainers are likely to want to happen.
>
> This change will cause the following packages to be removed:
>
> grep-3.6-1
> grep-3.7-1
> gzip-1.10-1
> readline-8.1-1
>
> Brian,
>
> The only packages I can see where this seems like it will do the wrong
> thing are listed below. Before deploying this, would you like me to:?
>
> grep: untest 3.6-1 and expire 3.0.1
> gzip: untest 1.10-1 and expire 1.7-2
Your calm expiry actions seem to DTRT, but your suggestions are probably
a better approach, so yes please do so!
Test releases grep 3.6 and gzip 1.10 successors grep 3.7 and gzip 1.11
were released during the test period, both including bug fixes, later
promoted to current.
A new grep 3.7 test was released, as the changes were significant: high
impact and pervasive, with only 9 months between releases.
The gzip 1.11 changes were not: mainly docs, help, infra, typos,
warnings, and other platforms, despite 2 years 9 months between releases
and more commits.
I was unaware of *untest*, so bumped the grep release and gzip version
for current.
--
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 binary units and prefixes, physical quantities in SI.]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: A change to how calm expires packages
2022-01-20 14:33 A change to how calm expires packages Jon Turney
` (2 preceding siblings ...)
2022-01-21 7:27 ` Brian Inglis
@ 2022-01-21 10:11 ` Hamish McIntyre-Bhatty
2022-01-29 15:19 ` Jon Turney
4 siblings, 0 replies; 6+ messages in thread
From: Hamish McIntyre-Bhatty @ 2022-01-21 10:11 UTC (permalink / raw)
To: cygwin-apps
On 20/01/2022 14:33, Jon Turney wrote:
>
> To try to avoid packages lingering in the 'test' status indefinitely
> (which leads to them not being installed by most users, as they don't
> run setup with 'consider test packages' enabled, thus these packages
> generally aren't getting used, so having them isn't generating much
> value), I'm planning to change how calm expires packages:
>
> Currently (in the absence of configuration otherwise [1]), calm will
> retain up to 3 non-test versions, and 3 test versions, and expire all
> other versions.
>
> I plan to change this to also expire test versions which are superseded
> by a non-test version (that is: expire test versions where a non-test
> version with a higher version number exists).
>
> I believe this makes the default behaviour closer to what package
> maintainers are likely to want to happen.
>
> This change will cause the following packages to be removed:
>
> _autorebase-001091-0.1
> cygutils-1.4.16-4
> cygwin-3.3.0-0.1.9814cfd8f693
> cygwin-3.3.0-0.2.6c1f49f83fde
> fontforge-20201107p2-1
> fontforge-20201107p8-1
> gcc-11.2.0-0
> grep-3.6-1
> grep-3.7-1
> gzip-1.10-1
> libftdi1-1.4-1
> libiconv-1.16-1
> meson-0.54.2-3
> mingw64-i686-gcc-11.1.0-0.1
> mingw64-i686-gcc-11.2.0-0
> mingw64-i686-gcc-7.3.0-1
> mingw64-x86_64-gcc-11.1.0-0.1
> mingw64-x86_64-gcc-11.2.0-0.1
> mingw64-x86_64-gcc-7.3.0-1
> openbabel-3.1.1p36-1
> openbabel-3.1.1p36-2
> rdiff-backup-2.0.0-1
> readline-8.1-1
> screen-4.6.2-3
> texlive-collection-latexrecommended-doc-20210118-2
> xorg-server-21.1.0-1
>
>
> Brian, Ken,
>
> The only packages I can see where this seems like it will do the wrong
> thing are listed below. Before deploying this, would you like me to:?
>
> grep: untest 3.6-1 and expire 3.0.1
> gzip: untest 1.10-1 and expire 1.7-2
> texlive-collection-latexrecommended-doc: untest 20210118-2 and expire
> 20210118-1
>
> [1] See https://cygwin.com/packaging-hint-files.html#override.hint. Not
> that override.hint files do not apply recursively currently.
>
This seems like a good change to me, also.
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: A change to how calm expires packages
2022-01-20 14:33 A change to how calm expires packages Jon Turney
` (3 preceding siblings ...)
2022-01-21 10:11 ` Hamish McIntyre-Bhatty
@ 2022-01-29 15:19 ` Jon Turney
4 siblings, 0 replies; 6+ messages in thread
From: Jon Turney @ 2022-01-29 15:19 UTC (permalink / raw)
To: cygwin-apps
On 20/01/2022 14:33, Jon Turney wrote:
>
> To try to avoid packages lingering in the 'test' status indefinitely
> (which leads to them not being installed by most users, as they don't
> run setup with 'consider test packages' enabled, thus these packages
> generally aren't getting used, so having them isn't generating much
> value), I'm planning to change how calm expires packages:
>
> Currently (in the absence of configuration otherwise [1]), calm will
> retain up to 3 non-test versions, and 3 test versions, and expire all
> other versions.
>
> I plan to change this to also expire test versions which are superseded
> by a non-test version (that is: expire test versions where a non-test
> version with a higher version number exists).
>
> I believe this makes the default behaviour closer to what package
> maintainers are likely to want to happen.
This change has been deployed.
^ permalink raw reply [flat|nested] 6+ messages in thread