From: Jon Turney <jon.turney@dronecode.org.uk>
To: Jari Aalto <jari.aalto@cante.net>
Cc: cygwin-apps@cygwin.com
Subject: Re: [Attn. MAINTAINERS] Heads up: Perl 5.36.1 is imminent
Date: Sun, 28 Jan 2024 16:40:15 +0000 [thread overview]
Message-ID: <d783435c-ea76-4cbc-9892-23fb8c5c5f65@dronecode.org.uk> (raw)
In-Reply-To: <cdaf5529-c208-44d0-b317-a21c5c3e3ac5@dronecode.org.uk>
On 15/12/2023 17:15, Jon Turney via Cygwin-apps wrote:
> On 23/10/2023 19:53, Jon Turney via Cygwin-apps wrote:
>> On 02/05/2023 21:34, Jon Turney via Cygwin-apps wrote:
>>> On 01/05/2023 21:00, Achim Gratz via Cygwin-apps wrote:
>>>>
>>>> I'm going to release Perl 5.36.1 to Cygwin in a few days. I've skipped
>>>> 5.34 in order to update only every second year (which I've done since
>>>> the 5.22 release). I haven't seen any trouble in my own Perl
>>>> distribution packages from the update even though there are lots of
>>>> them that haven't been updated since at least 5.22. So I hope it will
>>>> be smooth sailing for anything else depending on Perl also.
>>>>
>>>> Any maintainer having packages that depend on perl5_032 should
>>>> re-release or upgrade these soon-ish after the Perl update is
>>>> available,
>>>> as otherwise users are either blocked from upgrading Perl or will have
>>>> to uninstall the affected packages. The rebuilt packages need to
>>>> have a
>>>> dependency on perl5_036, which cygport provides automatically.
>>>
>>> There's an updated report available [1], which should list the
>>> affected packages.
>>>
>>> [1] https://cygwin.com/packages/reports/perl_rebuilds.html
>>>
>>
>> Hi Jari,
>>
>> Is it possible to get a rebuild/update of pristine-tar and sendxmpp
>> for perl5.36?
On further examination, it seems that sendxmpp is mistakenly identified
as having a dependency on a particular version of perl, due to the
presence of a
/usr/lib/perl5/vendor_perl/5.32/x86_64-cygwin-threads/auto/sendxmpp/.packlist
file, which probably shouldn't be in the package.
So, I've dropped that dependency from sendxmpp.
>
> Ping?
>
> Please indicate if these packages will be updated, or should be removed.
In the absence of any response, I have removed pristine-tar, the last
remaining package depending on perl 5.32, so people who install
everything (against our advice) aren't potentially forced down onto an
old perl.
I will assume it is orphaned unless you say otherwise.
If that's not what you wanted to happen, please let me know.
prev parent reply other threads:[~2024-01-28 16:40 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
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 [this message]
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=d783435c-ea76-4cbc-9892-23fb8c5c5f65@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.com \
--cc=jari.aalto@cante.net \
/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).