public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: [Attn. Maintainers] perl-5.30.1
Date: Sun, 17 Nov 2019 18:28:00 -0000	[thread overview]
Message-ID: <871ru6mk6a.fsf@Rainer.invalid> (raw)
In-Reply-To: <877e47irjx.fsf@Rainer.invalid> (Achim Gratz's message of "Sun,	10 Nov 2019 18:12:34 +0100")

Achim Gratz writes:
> 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.

I've already built the new Perl packages and the (almost) full set of
distributions.  I'm waiting for the stage 2 tests of the Perl build to
finish and will then post a repository link for you to point setup.exe
to (in addition of the Cygwin mirror) to update your own build systems.
This time around these are the same packages that will be going live on
the Cygwin mirrors unless I find an error that needs to be dealt with.

Besides Ken and Andrew, who have already responded, the only other
packages I don't yet maintain are from Yaakov (mostly Gnome and GUI
related stuff) and the *Magick wrappers that Marco maintains.  There
should be other packages with captive Perl modules (IIRC SVN and Git).
Git isn't affected because it sets up @INC itself and doesn't have
architecture-specific modules.

During the release of Perl-5.26 we've fingered the following:

biber:	             BibTeX replacement for users of BibLaTeX (installed binaries and support files)
git-svn:	     Subversion compatibility support for Git version control system
git:	             Distributed version control system
grepmail:	     search mailboxes for mail matching an expression (installed binaries and support files)
irssi:	             Modular text mode IRC client with Perl scripting
nginx-mod_http_perl: Web and mail proxy server (installed binaries and support files)
nginx-mod_http_perl: Web and mail proxy server
po4a:	             Tools for translating various file formats with gettext (installed binaries and support files)
pristine-tar:	     Regenerate pristine tarballs (installed binaries and support files)
sendxmpp:            Commandline XMPP (jabber) utility (installed binaries and support files)
subversion-perl:     A version control system (perl bindings)
texlive:             TeXLive

Again, just like the last time around, noarch packages _should_ keep
working if the files are moved to the correct directory where Perl-5.30
looks for them, but I've not really checked.  Since there have been many
changes in Perl internals, I wouldn't take chances with archful packages
(anything that comes with a DLL).


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

  parent reply	other threads:[~2019-11-17 18:28 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
2019-11-10 21:38 ` Ken Brown
2019-11-17 18:28 ` Achim Gratz [this message]
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=871ru6mk6a.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).