From: "Andrew Schulman via cygwin-apps" <cygwin-apps@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: [Attn. Maintainers] perl-5.30.1
Date: Sun, 10 Nov 2019 20:58:00 -0000 [thread overview]
Message-ID: <qbugse5kbd8h4g46l4f12d5d21p1e4urcb@4ax.com> (raw)
In-Reply-To: <877e47irjx.fsf@Rainer.invalid>
> Perl version 5.30.1 was just released. I will have an unexpected
> timeslot available at the beginning of next week that I plan to use to
> update Perl for Cygwin. This of course means all Perl distribution
> packages and any other packages that install into the Perl module
> directories will need to be updated. By now I should maintain or
> co-maintain almost all Perl distribution packages, but there are a few
> that are left over or captive in some other packages.
>
> I'd appreciate if the respective maintainers would reply to this post
> with the names of the affected packages and if they can roll an update
> around the time mentioned. Thanks.
Hi. stow makes the perl-Stow package. Sure, I can rebuild that, it'll only take
a few minutes. Please just let us how when we should go ahead. Andrew
next prev parent reply other threads:[~2019-11-10 20:58 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-10 17:12 Achim Gratz
2019-11-10 20:58 ` Andrew Schulman via cygwin-apps [this message]
2019-11-10 21:38 ` Ken Brown
2019-11-17 18:28 ` Achim Gratz
2019-11-24 17:58 ` [Attn. Maintainers] Reminder: Package updates needed for the pending switch to perl-5.30.1 Achim Gratz
2019-11-25 16:33 ` Marco Atzeri
2019-12-16 18:41 ` Marco Atzeri
2019-12-16 18:51 ` Achim Gratz
2019-12-16 19:44 ` Marco Atzeri
2019-11-25 17:20 ` Jari Aalto
2019-11-25 17:27 ` [Attn. Maintainers] RFP: libmail-mbox-messageparser-perl (perl-5.30.1 rebuild) " Jari Aalto
2019-11-25 17:34 ` Achim Gratz
2019-11-25 18:02 ` Jari Aalto
2019-11-26 12:21 ` Achim Gratz
2019-11-26 19:42 ` Achim Gratz
2019-11-26 20:37 ` [Attn. Maintainers] Reminder: Package updates needed for the " Alexey Sokolov
2019-11-26 20:47 ` Achim Gratz
2020-01-09 18:58 ` Achim Gratz
2020-01-11 17:28 ` Achim Gratz
2020-01-20 16:11 ` Achim Gratz
2019-11-17 19:57 ` [Attn. Maintainers] perl-5.30.1 Achim Gratz
2019-11-18 22:35 ` Ken Brown
2019-11-18 23:25 ` Brian Inglis
2019-11-19 6:53 ` ASSI
2019-11-19 13:33 ` ASSI
2019-11-19 13:44 ` Ken Brown
2019-11-19 13:58 ` ASSI
2019-11-19 17:08 ` Achim Gratz
2019-11-19 19:30 ` Achim Gratz
2019-11-22 20:04 ` Ken Brown
2019-11-28 6:56 ` Achim Gratz
2019-11-29 21:22 ` Andrew Schulman via cygwin-apps
2019-12-01 12:42 ` Achim Gratz
2020-02-03 20:11 ` [Attn. Maintainers] perl-5.30.1 -- prepare for release Achim Gratz
2020-02-04 17:44 ` Marco Atzeri
2020-02-04 17:54 ` Ken Brown
2020-02-04 19:30 ` Andrew Schulman via cygwin-apps
2020-02-04 20:23 ` Achim Gratz
2020-02-05 12:54 ` Jon Turney
2020-02-06 17:53 ` David Rothenberger
2020-02-08 6:57 ` Marco Atzeri
2020-02-15 11:42 ` Marco Atzeri
2020-02-16 6:55 ` ASSI
2020-02-16 8:08 ` Marco Atzeri
2020-02-16 15:30 ` Jon Turney
2020-02-18 19:54 ` Marco Atzeri
2020-02-19 16:44 ` Jon Turney
2020-02-19 23:41 ` Alexey Sokolov
2020-02-20 15:26 ` Jon Turney
2020-02-18 16:43 ` David Rothenberger
2020-02-08 20:53 ` Achim Gratz
2020-02-08 21:35 ` Alexey Sokolov
2020-02-09 7:25 ` ASSI
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=qbugse5kbd8h4g46l4f12d5d21p1e4urcb@4ax.com \
--to=cygwin-apps@cygwin.com \
--cc=schulman.andrew@epa.gov \
/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).