From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: [Attn. MAINTAINERS] Heads up: Perl 5.36.1 is imminent
Date: Wed, 3 May 2023 08:19:47 -0400 [thread overview]
Message-ID: <31082bc1-bf6b-dda1-e8f7-c4ace2a6fc29@cornell.edu> (raw)
In-Reply-To: <871qjy4g4b.fsf@Rainer.invalid>
On 5/2/2023 4:45 PM, Achim Gratz via Cygwin-apps wrote:
> Jon Turney via Cygwin-apps writes:
>> There's an updated report available [1], which should list the
>> affected packages.
>>
>> [1] https://cygwin.com/packages/reports/perl_rebuilds.html
>
> Thanks. The newly obsolated packages (due to core now recent enough)
> are still shown in this list (that's probably to be expected).
I wonder if those obsoleted packages are confusing setup. In a new
Cygwin installation, choosing only the base packages and cygport, setup
wants to install perl-Test-Harness (and therefore perl 5.32). Or maybe
there's something else causing perl 5.32 to be chosen, but I don't see it.
Ken
next prev parent reply other threads:[~2023-05-03 12:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-01 20:00 Achim Gratz
2023-05-01 20:28 ` Marco Atzeri
2023-05-02 6:36 ` ASSI
2023-05-02 19:47 ` Achim Gratz
2023-05-05 20:15 ` Marco Atzeri
2023-05-05 20:44 ` Jon Turney
[not found] ` <43354da8-65cc-7224-fcee-81fe38afb512@gmail.com>
2023-05-06 13:12 ` Jon Turney
2023-05-07 11:39 ` Marco Atzeri
2023-05-02 20:34 ` Jon Turney
2023-05-02 20:45 ` Achim Gratz
2023-05-03 12:19 ` Ken Brown [this message]
2023-05-03 13:33 ` Jon Turney
2023-05-03 14:47 ` Ken Brown
2023-05-03 16:51 ` Achim Gratz
2023-05-03 18:41 ` Achim Gratz
2023-05-03 16:55 ` Achim Gratz
2023-05-03 22:01 ` Ken Brown
2023-05-06 13:34 ` Jon Turney
2023-05-06 18:31 ` Ken Brown
2023-05-09 20:15 ` Jon Turney
2023-05-20 7:57 ` Achim Gratz
2023-10-23 18:53 ` Jon Turney
2023-12-15 17:15 ` Jon Turney
2024-01-28 16:40 ` Jon Turney
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=31082bc1-bf6b-dda1-e8f7-c4ace2a6fc29@cornell.edu \
--to=kbrown@cornell.edu \
--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).