public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>,
	Jari Aalto <jari.aalto@cante.net>
Subject: Re: [Attn. MAINTAINERS] Heads up: Perl 5.36.1 is imminent
Date: Mon, 23 Oct 2023 19:53:40 +0100	[thread overview]
Message-ID: <cc4658a9-6814-478f-8ad4-4a36fcc20e9a@dronecode.org.uk> (raw)
In-Reply-To: <b73ea942-08da-e2dc-eaa4-3bcd9e3d913f@dronecode.org.uk>

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?

TIA.


  parent reply	other threads:[~2023-10-23 18:53 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 [this message]
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=cc4658a9-6814-478f-8ad4-4a36fcc20e9a@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).