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, 01 Dec 2019 12:42:00 -0000	[thread overview]
Message-ID: <87o8ws1akd.fsf@Rainer.invalid> (raw)
In-Reply-To: <87sgma9xfy.fsf@Rainer.invalid> (Achim Gratz's message of "Tue,	26 Nov 2019 21:47:45 +0100")

Achim Gratz writes:
> There's a bug in perl-5.30 that hits only embedded Perl and only in
> certain circumstances.  Reverting the corresponding commit appears to
> work, but makes the resulting Perl binary incompatible (i.e. all XS
> modules and embedded Perls would need to be built again).  I can build a
> new Perl relatively quickly now, so I could do that over the weekend,
> but I wouldn't necessarily want to release that directly.

I have integrated the two patches that revert the offending commit and
re-built Perl and all XS modules (as well as openldap, as one of the
server backends has an embedded perl interpreter). The updated Perl-5.30
repository is now available.  Since I have not changed the release
numbers, you'll have to dupe setup into "upgrading" all perl packages in
your installation (alternatively you'd need to re-install all Perl
related packages manually):

--8<---------------cut here---------------start------------->8---
sed -i.bak -re 's/^(perl.*) .+ ([01])$/\1 \1-0-0.tar.bz \2/'\
    /etc/setup/installed.db
--8<---------------cut here---------------end--------------->8---

Any XS modules you have locally installed will need to be re-built as
well or they would complain about a mismatched handshake key when trying
to load their DLL.

Please point setup.exe at:

root=http://cygwin.stromeko.net/
$root/perl-5.30

The setup.xz is signed with my PGP key available at $root/stromeko.gpg,
which you can download and then feed to setup.exe via the -K switch.
The fingerprint of that key is:

      B22B 4890 B89E 5E5A 795C  E305 B40B EC75 3152 B1C3

If you have the keyart script (Python, you can just download from
https://raw.githubusercontent.com/atoponce/keyart/master/keyart), this
is what you should see after importing the key into your public keyring:

> keyart stromeko
+-----[DSA 2048]----+
|         ^.        |
|        ^ .        |
|       ^ E         |
|    . . ^ :        |
|. .  ^ : .         |
|.^  . ^.:S         |
| ..  . :^.         |
|.  .^ ^.^          |
|. ^:.^ ..          |
| ^:... .           |
|.^    .            |
+-----[3152B1C3]----+
+-------------------+
|                 :X|
|             .  ^^^|
|            :   ..^|
|         . : .   E |
|          i . . .  |
|       ^ S l : .   |
|        i l ^ ^    |
|       ^ . .       |
|      .   .        |
|       . .         |
|      ...          |
+-------------------+



Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

  parent reply	other threads:[~2019-12-01 12:42 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
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 [this message]
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=87o8ws1akd.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).