PHP 7.1.13 and 7.2.1 Available

6 years ago by Sara Golemon — view source

unread

I'm happy to announce not one, but two new PHP releases today.
PHP 7.1.13 and 7.2.1 are ready to go at http://php.net/downloads.php

The Windows binaries are available per usual at:
http://windows.php.net/download/

Hash Values and GPG signatures can be found below and at:
7.1.3: https://gist.github.com/sgolemon/72a7ce295c22610228896f37c27e8a36
7.2.1: https://gist.github.com/sgolemon/bb2d82e60052fc5cc2ed0a81eafae4f0

Thank you, and happy testing!
-Sara

php-7.1.13.tar.gz
SHA256 hash: 12fcbf59c9eb9af215ef38815d5da39b9d74549092c34b0dfc31442699740ce9
PGP signature:
-----BEGIN PGP SIGNATURE-----
iQItBAABCAAXBQJaTEE3EBxwb2xsaXRhQHBocC5uZXQACgkQ29s5dHDRIXIophAA
1uWs9I04STIGPpEUiS0zE+aULn4ZA77IAloM6Q7cZOZl+MAedokBlyjpzKvgzYm2
mq+vbkEmgGEPQtegkEodSUJfhcZp94ZDEqxeDtYmXZTD0yKhnoVgIhUiDS2rG5Td
+YWBXhEuNLs07I8SoqCNOxe2UHP32IW+yzVzEmGkFbQlspRraiekFCxPTqxQF689
8rwKT/iPVuu/w2tPJCGFgGcS5TfdFJtUyy6N7oFX41OjaagAZYWDy5Fnp4pZ2y/4
Wpi2EdlaWWliwDuBUM1wOXsA1ZCeABetQO4lqasFHes7J41cZxMicluCVYtfKDqS
Ep2mh9TcNjc8kam7fVU1TuSdAydFn5vJ0HIKcvvbblN5qogpb9b7rR/C92XU0gFe
Hjofnt6J5MPAJRy2RdUSwJlvKx+uzR4cg5bx/0zWwBYoVc/GU7e/UsEwiD/INWc2
VS+PeC6BSyFhFPvqy57leXyLCY/s870MnkwbCMKiHhvb5ST9fEu2qKk5GD6ksLeH
QeYEyxapAxajnCNLVAg29S/FmzzSyIRh0dISVzzHCJenB7v0VEPGm10GMnnfwceC
KumedhE818AjYMs6OyezT1JQfaiDm/ZSXkxmf/zTK+nXCTgNQ8MK0RgYiMYqE/mt
8I1MGEeLPclEEjXRQ37ZyRh5c7LXoHvjmCcv7ENsezM=
=eIlS
-----END PGP SIGNATURE-----

php-7.1.13.tar.bz2
SHA256 hash: 35fda51d2d44600940185fd5818d336a79e77ab3c98e2bd075091f2f91cf98a1
PGP signature:
-----BEGIN PGP SIGNATURE-----
iQItBAABCAAXBQJaTEE7EBxwb2xsaXRhQHBocC5uZXQACgkQ29s5dHDRIXK9rw//
axeGHm7IzQ40O/QyXu/CjN3OWou0yZIzqmYlTVHxgWb+xcD+quhlW5K5cFoVK5Qq
Z/siTHZ0iKMy2517iSLliUOgp9owlu5DPBeDsLCtC79NDuQg321iWDfx3F3+Ml1e
xfvTobhDZ9s/q9q0qi+cQQfYHs5AycCidHan4Tavu/90Ur3VEzWuhU5A0wspQSVr
i49+FNci+NPuftC+9SRqJzarB3BOLGfa1s7dJUWfgofhVleuv1ZW8BD+p52RXDel
QTLXfJiXX4BL8YqPcZxbnPEbMVfDDI7OHXZOa6RnWxwTvSgo8Kbww631lcsBA91l
vMvNaca20hfAYGuvbYonbm4fQYroVC/whwBtPM5OXcXIv7wUgZdV86LxOv5snnWA
ds13tZ41i76hDPsfldUYrvJOwOcHeFpPOlhfzaN0B9rQnCvIXHprm96ErvJ824oU
Qzmw27tJ1nNqblPXj+0+G0ULMYruBip7eCWDPsd1VFpzGgDfxGfyZH3vxyhj3sjS
LdWdHZ2/t9AAZFacx3nBIuQJjmOneOcih2myb022O/89FSRoeTlZPWAdwSyQdVNA
WJI2OzyvVeRNcXmeVxP0i+b7fc8RHEtU/xTtTtJGHAYf5RSL17KjRSRaw251W3Iw
R5RlrKUVQ9o5fWAsOQqXeJmEibs9QqdQEuuRuH3e22U=
=o1P6
-----END PGP SIGNATURE-----

php-7.1.13.tar.xz
SHA256 hash: 1a0b3f2fb61959b57a3ee01793a77ed3f19bde5aa90c43dcacc85ea32f64fc10
PGP signature:
-----BEGIN PGP SIGNATURE-----
iQItBAABCAAXBQJaTEE7EBxwb2xsaXRhQHBocC5uZXQACgkQ29s5dHDRIXIvoQ/8
D9l0nn0W8xwe8eTe8B2SUd7TjouVTwcFMawMf0CFav2Lmfc+kqVJrjFUsayw9sfe
fBx5UGKnQ7hhhsxxwG2O07HRloPujtgq2iqa7TqOLIuNMYoWfExsmI1p3Ru+upuf
UdB4RyeGZOJs/dTcE7pMK0UYBOsPlf8uYTp8wn6NvDOSQWfGR7o3kgbGwPHCvmj4
2ZelmAUvejXwAUyygk1jtfBdlDhUeDGFwA4KD6SUQ4FYcXfJ9kWVbKWv0W0HJ0BZ
7LrqGM973nPF0BiFOlW8hFAkkQtnDxvhqdA4uhvlrNinsy9lbyXkHz4VK5Rksr6G
N9pK8S1bwLfRK16EpsZhfH/jzTAkpbCUOV6rJJOJC4sV821/1nadIbzElsfUXFic
drFulalpguF6kX99KJs33pdgWDqfrCgZmSPazgOh/mFOL0/n8lsUKlPnW3rpyi6A
ZQLUOpNF6QvMR7r7SRzfPx+tekL+0w07CrZueRIZpTpBIXF9b6RW2JtysU1SWzHF
GlM6267NtD/2inE6kkAH5LKhfNRwQH5HoqiBoX9XyMTByQ9R255FOYg//dxI5HjO
b0b6d/y09EH0XsocGTNMQ86Cp7svmqfCjWZlu+2BizXfCUpW/8SwpkZNE7aVId33
QnHTVwYyag1Y/y9oCM1Dg+lYU0R0VrXhhpnRBnwJyQI=
=Oj2q
-----END PGP SIGNATURE-----

php-7.2.1.tar.gz
SHA256 hash: 8ecb2950571054a00687ccbd023874a4a075ccd1e2ec3dc00fc25ef589a77dba
PGP signature:
-----BEGIN PGP SIGNATURE-----
iQItBAABCAAXBQJaTA1sEBxwb2xsaXRhQHBocC5uZXQACgkQ29s5dHDRIXL2OhAA
zjopx6m30pqDJYod2L+4bef9Ww2VBKfS9um8O7uTSl65Ook4GybUt/5sYbnW1RCi
96Bb1Ir83mty7JNphrG1OEZMkF8NBNLLr0/Jkdl6wkIVzrBmgwt5XgjwiZVVNFHq
uiiXVr+khMSSW2l5Oo4GBvmR+wPNAbUtxKv4TAt8dBY3La8dcZiScyG1/DP25INC
P1jfoWe8X4vOaeVYlSgDEk5KkFKuJyWr4SqHV7egvroZHCmh3vabjMUOu1Mn4/qh
QXWM4cimz1XTbjlaXfJSr8TnNpbTEXsO0X1C9pn/S07CjYkfP+6qDzT8PHtovpGY
xtWzHYlJHbkkyHI3XVCi9nM9EtBt1H7i32gWYvX239jZLZRdoe91O35yNLXvSD4f
uoHoar0Z6JmtUcWC8LPCu38qjox3zPCwg2ZiWj3D75x3NSbpl9HtntSHXcg528Zy
MfbpiwZOys9sVxVCkaAxnG5qZXVF6IpGd1MXY0U5t0yBNqZIk0Kv17HcD1XwCYk+
BLqd6A9L+SMgUosHsTKW2Puh2DZVHpJOEepgx3xApKp/WHBeZ5HGMSjC5fxBYv+/
4q5pKlBIzFKuEjwlFwBuJk9jGWp3zV3XjYGQmbhEmHTilgBaLtvGgyT1b9c1GOqr
CC18tosBoc3mFX8pPVNIySAHH2cR3fbceP/gXvy3Bc0=
=4axu
-----END PGP SIGNATURE-----

php-7.2.1.tar.bz2
SHA256 hash: fe06793f268a4dd29cbc5f4ef415f01e786877152b02221ad7d18dbb6864eb79
PGP signature:
-----BEGIN PGP SIGNATURE-----
iQItBAABCAAXBQJaTA11EBxwb2xsaXRhQHBocC5uZXQACgkQ29s5dHDRIXLk2w//
cVr0MS3CpvD9aKBilR9MUaLFnpnFKIyHCU9RJxcIOqiArAGrZXyJ4fMLBZ37JrwP
EKUnfo777cJQwXjdvxA5V66uvPSV6Mgeshtr/4WoAbsaiVx5XUWXgATikdCcx7AR
bw0g9IXkCUugueTO90ENBSwIY2V1JIhSBWaGm3ddJan7Qox/ATMCR3mghViXOl6E
W1xDq4ZL8tYVil/+bJ6MgaDPZcDwF0EoE/2CStLUYCYriCUlSEB5XUV7vNDTgfg8
Y2VCib5TgJQ/7j0i/bI4FjPetPvVtQdy6yR+qdzm8Doytg0K0BLlHTul8BiYMtgf
5eEHDK8ico0Bbqbx7nOdYR1tDse9kM3tUmbepvYG0zq87TPh5u6/lfDjtYsX4Z+h
Aw9oRguDmbZSyJs/nS81MK+hUIBdIn+uQ8y301Gh4ktdG3nfR/1192Yavrm/yl0k
a8WLze6WHHxTefC4kbUsTqWaW5PLGeHBEJAKdmsUXj+dOQgXHIKQMxmakJ0a2UDb
ptoFLyzme/5zKzvqEhZHjn0fexbtJSmfk/6RKhX/gJwz2MNTPVvq9eKyBXN118QW
LyVEh32x4t0obQXbDwhTquKco/W/dIcV1W4qZntUo2wVKONC4rjYIkNwe9a9YxhA
Ypmi+by6dg+Odp8ABhi4ZI6hWJNdiATG48w7TiBLb30=
=Ss77
-----END PGP SIGNATURE-----

php-7.2.1.tar.xz
SHA256 hash: 6c6cf82fda6660ed963821eb0525214bb3547e8e29f447b9c15b2d8e6efd8822
PGP signature:
-----BEGIN PGP SIGNATURE-----
iQItBAABCAAXBQJaTA12EBxwb2xsaXRhQHBocC5uZXQACgkQ29s5dHDRIXKFYQ//
Wh9XQ04Wj5sM/sDTwZ/FXkesA5wvDcRRaeogq97p8XEKB3zIM6CX2V83WNPNjiSO
WoGkQsKtuLkT8MBLy3Y2Hu6cRcOlXNLVaeq1aA/0s5RCbesAFkZtC3ecW9P4fCqg
RedUhgVVEjvmg+/nAdQXqGkkTm3b/HJGk4x7C4TG5nHqerB3DaanLyfL3x3FZxEh
k/qTh9U3CWyJRkRb64Sc84CqwcqYfsjTxxPnft34X/RhjPppd0cEBOyqQAvSqGj8
jngmv7AQIA3oZEzFqU2EbIxTJK0u/eGWrKc27NbGffZRI8GYzO7ID0WF7lf6cSR7
36ekJJUEg0Bv0Gr5ErLl/KWcSFHA7Av6B1H/H/FNAieySvW7I2wrKRXNxoQMPhQr
Gb804lvF1yTdT8nlnk/VZyARqhhCA9wBSvxhgS3e5hnic2MmhMpEbFLWwhDwy2tc
XpzXrnKYtHSEzBGzaI3oxcCOLnCklW9s6z9ip/nnfyl4ividgUkpi0RdqDwy94NU
vptgU3tK2F7U7B0fEw0sRsjKQrJ7SBjHLbEioYS926Dhv2gTRVLLYF7EmHKa8Oyc
X1hJz4nctxx2zUTdPVFPt4migMzfpcLSmOiSrMQNNbyd1xN2aTdvPRlkT3TxhtGX
dMhklGRna24XSdguFWML5KsBJExDdfPDa3AwWsQpWG0=
=0N4W
-----END PGP SIGNATURE

6 years ago by Jan Ehrhardt — view source

unread

Sara Golemon in php.internals (Thu, 4 Jan 2018 12:06:59 -0500):

I'm happy to announce not one, but two new PHP releases today.
PHP 7.1.13 and 7.2.1 are ready to go at http://php.net/downloads.php

Is it on purpose that the release-zip on github contains PHP 7.2.1-dev?
See the main/php_version.h in the zip at
https://github.com/php/php-src/releases

Jan

6 years ago by Sara Golemon — view source

unread

Is it on purpose that the release-zip on github contains PHP 7.2.1-dev?
See the main/php_version.h in the zip at
https://github.com/php/php-src/releases

No, that was an accident. Most of my process is automated, but that
got derailed slightly with the need to fill in for 7.1 and I goofed
up. Also this was my first non-alpha/beta/RC release, so I got
semi-whelmed by that too. (Not overwhelmed, just whelmed). Sorry. :(
Unfortunately, it's too late to move the tag to the right commit
(which does exist!). FWIW, the official (non-github) tarballs are
correct.

The main reason why I prefer the github zips over the zips at
http://windows.php.net/download/ is some kind of mismatch in the UTF-8
filenames:

Whaaaa? That's broken and we should try to fix it. I'll say that the
latest php-7.2.1 tarballs unpack fine for me. (e.g.
ext/bz2/tests/003私はガラスを食べられます.txt.bz2) maybe you're missing a locale?

The "central" filename version is the correct one, like the filename at
https://github.com/php/php-src/tree/master/ext/bz2/tests

Okay, so you end up with the correct file on your filesystem, it's
just a warning during untarring?

The zips at github do not have the mismatch and do contain the correct
filenames. So github seems to handle UTF-8 filenames in better way than
https://github.com/php/php-src/commit/3d3f11ede4cc7c83d64cc5edaae7c29ce9c6986f

Right. So it's likely the tar producer doing something weird.
php-src/makedist is doing a sort of git-archive, untar, add files,
retar dance (to ensure a clean state), whereas I assume github is just
doing a straight git-archive.

For the sake of reproducibility, what's your tar --version?
My build container is using GNU tar 1.27.1, and git 2.1.4

-Sara

6 years ago by Jan Ehrhardt — view source

unread

Hi Sara,

Sara Golemon in php.internals (Fri, 5 Jan 2018 08:38:57 -0500):

No, that was an accident.

OK. Next time will be perfect.

The main reason why I prefer the github zips over the zips at
http://windows.php.net/download/ is some kind of mismatch in the UTF-8
filenames:

Whaaaa? That's broken and we should try to fix it. I'll say that the
latest php-7.2.1 tarballs unpack fine for me. (e.g.
ext/bz2/tests/003????????????.txt.bz2) maybe you're missing a locale?

The "central" filename version is the correct one, like the filename at
https://github.com/php/php-src/tree/master/ext/bz2/tests

Okay, so you end up with the correct file on your filesystem, it's
just a warning during untarring?

Yes. During un_zip_ping of
http://windows.php.net/downloads/releases/php-7.2.1-src.zip

For the sake of reproducibility, what's your tar --version?

N:\php-sdk\win32sdk2
$ unzip -h
UnZip 6.00 of 20 April 2009, by Info-ZIP. Maintained by C. Spieler. Send
bug reports using http://www.info-zip.org/zip-bug.html; see README for details.

Jan

6 years ago by Sara Golemon — view source

unread

OK. Next time will be perfect.

Suuuuuuure. Yeah.... <,<

Yes. During un_zip_ping of
http://windows.php.net/downloads/releases/php-7.2.1-src.zip

Ooooooooh, the windows zip. That's a horse of a different color. I'm
not sure how the windows zips are produced, maybe Stephen can comment.

-Sara

6 years ago by Christoph M. Becker — view source

unread

The main reason why I prefer the github zips over the zips at
http://windows.php.net/download/ is some kind of mismatch in the UTF-8
filenames:

N:\php-sdk\win32sdk2
$ unzip -h
UnZip 6.00 of 20 April 2009, by Info-ZIP. Maintained by C. Spieler. Send
bug reports using http://www.info-zip.org/zip-bug.html; see README for details.

From the release notes[1]:

| Support for UTF-8 encoded entry names, both through PKWARE's "General
| Purpose Flags Bit 11" indicator and Info-ZIP's new "up" unicode path
| extra field. (Currently, on Windows the UTF-8 handling is limited to
| the character subset contained in the configured non-unicode "system
| code page".)

So this might be a codepage issue.

[1] http://www.info-zip.org/UnZip.html

--
Christoph M. Becker

6 years ago by Jan Ehrhardt — view source

unread

Hi Chris,

"Christoph M. Becker" in php.internals (Fri, 5 Jan 2018 15:53:23 +0100):

The main reason why I prefer the github zips over the zips at
http://windows.php.net/download/ is some kind of mismatch in the UTF-8
filenames:

N:\php-sdk\win32sdk2
$ unzip -h
UnZip 6.00 of 20 April 2009, by Info-ZIP. Maintained by C. Spieler. Send
bug reports using http://www.info-zip.org/zip-bug.html; see README for details.

From the release notes[1]:

| Support for UTF-8 encoded entry names, both through PKWARE's "General
| Purpose Flags Bit 11" indicator and Info-ZIP's new "up" unicode path
| extra field. (Currently, on Windows the UTF-8 handling is limited to
| the character subset contained in the configured non-unicode "system
| code page".)

So this might be a codepage issue.

The warnings do not occur when processing the zips from
https://github.com/php/php-src/releases so we know it must be possible
to produce zip-files with Unicode filenames without mismatch. Big
question is: how?

Jan

6 years ago by Christoph M. Becker — view source

unread

Hi Jan!

"Christoph M. Becker" in php.internals (Fri, 5 Jan 2018 15:53:23 +0100):

The main reason why I prefer the github zips over the zips at
http://windows.php.net/download/ is some kind of mismatch in the UTF-8
filenames:

N:\php-sdk\win32sdk2
$ unzip -h
UnZip 6.00 of 20 April 2009, by Info-ZIP. Maintained by C. Spieler. Send
bug reports using http://www.info-zip.org/zip-bug.html; see README for details.

From the release notes[1]:

| Support for UTF-8 encoded entry names, both through PKWARE's "General
| Purpose Flags Bit 11" indicator and Info-ZIP's new "up" unicode path
| extra field. (Currently, on Windows the UTF-8 handling is limited to
| the character subset contained in the configured non-unicode "system
| code page".)

So this might be a codepage issue.

The warnings do not occur when processing the zips from
https://github.com/php/php-src/releases so we know it must be possible
to produce zip-files with Unicode filenames without mismatch. Big
question is: how?

Frankly, I don't know. However, these message are indeed mere warnings;
the log as well as the file system shows correct filenames after
extracting. Furthermore, the messages 'continuing with "central"
filename version' don't make sense to me, since the filenames in the
local file headers are identical to those in the central directory headers.

Anyhow, since everything appears to work with unzip 6.0.0 and there are
better tools anyway, I don't think this issue deserves spending much
time. :)

--
Christoph M. Becker

6 years ago by Anatol Belski — view source

unread

Hi Christoph,

-----Original Message-----
From: Christoph M. Becker [mailto:cmbecker69@arcor.de]
Sent: Friday, January 5, 2018 5:31 PM
To: internals@lists.php.net; Jan Ehrhardt phpdev@ehrhardt.nl;
internals@lists.php.net
Subject: Re: [PHP-DEV] Re: PHP 7.1.13 and 7.2.1 Available

Hi Jan!

"Christoph M. Becker" in php.internals (Fri, 5 Jan 2018 15:53:23 +0100):

The main reason why I prefer the github zips over the zips at
http://windows.php.net/download/ is some kind of mismatch in the
UTF-8
filenames:

N:\php-sdk\win32sdk2
$ unzip -h
UnZip 6.00 of 20 April 2009, by Info-ZIP. Maintained by C. Spieler.
Send bug reports using http://www.info-zip.org/zip-bug.html; see README
for details.

From the release notes[1]:

| Support for UTF-8 encoded entry names, both through PKWARE's
| "General Purpose Flags Bit 11" indicator and Info-ZIP's new "up"
| unicode path extra field. (Currently, on Windows the UTF-8 handling
| is limited to the character subset contained in the configured
| non-unicode "system code page".)

So this might be a codepage issue.

The warnings do not occur when processing the zips from
https://github.com/php/php-src/releases so we know it must be possible
to produce zip-files with Unicode filenames without mismatch. Big
question is: how?

Frankly, I don't know. However, these message are indeed mere warnings; the
log as well as the file system shows correct filenames after extracting.
Furthermore, the messages 'continuing with "central"
filename version' don't make sense to me, since the filenames in the local file
headers are identical to those in the central directory headers.

Anyhow, since everything appears to work with unzip 6.0.0 and there are better
tools anyway, I don't think this issue deserves spending much time. :)

Same here, "7za x file.zip" is a far better option with the latest versions. With the variety of tools, there'll be always some with some conflicting implementation. Many tools are supported by the current approach anyway.

Regards

Anatol

6 years ago by Christoph M. Becker — view source

unread

Hi Jan!

"Christoph M. Becker" in php.internals (Fri, 5 Jan 2018 15:53:23 +0100):

The main reason why I prefer the github zips over the zips at
http://windows.php.net/download/ is some kind of mismatch in the UTF-8
filenames:

N:\php-sdk\win32sdk2
$ unzip -h
UnZip 6.00 of 20 April 2009, by Info-ZIP. Maintained by C. Spieler. Send
bug reports using http://www.info-zip.org/zip-bug.html; see README for details.

From the release notes[1]:

| Support for UTF-8 encoded entry names, both through PKWARE's "General
| Purpose Flags Bit 11" indicator and Info-ZIP's new "up" unicode path
| extra field. (Currently, on Windows the UTF-8 handling is limited to
| the character subset contained in the configured non-unicode "system
| code page".)

So this might be a codepage issue.

The warnings do not occur when processing the zips from
https://github.com/php/php-src/releases so we know it must be possible
to produce zip-files with Unicode filenames without mismatch. Big
question is: how?

Frankly, I don't know. However, these message are indeed mere warnings;
the log as well as the file system shows correct filenames after
extracting. Furthermore, the messages 'continuing with "central"
filename version' don't make sense to me, since the filenames in the
local file headers are identical to those in the central directory headers.

Anyhow, since everything appears to work with unzip 6.0.0 and there are
better tools anyway, I don't think this issue deserves spending much
time. :)

--
Christoph M. Becker

6 years ago by Anatol Belski — view source

unread

-----Original Message-----
From: Jan Ehrhardt [mailto:phpdev@ehrhardt.nl]
Sent: Friday, January 5, 2018 4:20 PM
To: internals@lists.php.net
Subject: Re: [PHP-DEV] Re: PHP 7.1.13 and 7.2.1 Available

Hi Chris,

"Christoph M. Becker" in php.internals (Fri, 5 Jan 2018 15:53:23 +0100):

The main reason why I prefer the github zips over the zips at
http://windows.php.net/download/ is some kind of mismatch in the
UTF-8
filenames:

N:\php-sdk\win32sdk2
$ unzip -h
UnZip 6.00 of 20 April 2009, by Info-ZIP. Maintained by C. Spieler.
Send bug reports using http://www.info-zip.org/zip-bug.html; see README
for details.

From the release notes[1]:

| Support for UTF-8 encoded entry names, both through PKWARE's "General
| Purpose Flags Bit 11" indicator and Info-ZIP's new "up" unicode path
| extra field. (Currently, on Windows the UTF-8 handling is limited to
| the character subset contained in the configured non-unicode "system
| code page".)

So this might be a codepage issue.

The warnings do not occur when processing the zips from
https://github.com/php/php-src/releases so we know it must be possible to
produce zip-files with Unicode filenames without mismatch. Big question is:
how?

I see the warnings now, however the file is unpacked correctly. Strange enough. Chistoph's finding might be the cause of these warnings. But if unzip can only translate UTF-8 to the current codepage, it would mean actually any CJK filenames would be broken, which they're not. Plus, MSYS2 is actually a Linux port, so there can be issues in this regard , too.

I'd rather say unzip should not be used in this case as it inherently documents not a fully compatible behavior, but seems to work in the end. The binary tools also supply 7za which has decent support for other formats. Perhaps it would make sense to check whether 7z should be used to produce zips. I recall that we had some issues when use older MSYS2 tools. Unzip was added there for convenience with the old SDK and because it's used also by several other scenarios, eq . PECL build hosts.

Regards

Anatol

6 years ago by Anatol Belski — view source

unread

Hi Jan,

-----Original Message-----
From: Jan Ehrhardt [mailto:phpdev@ehrhardt.nl]
Sent: Friday, January 5, 2018 9:50 AM
To: internals@lists.php.net
Subject: [PHP-DEV] Re: PHP 7.1.13 and 7.2.1 Available

Jan Ehrhardt in php.internals (Fri, 05 Jan 2018 09:19:46 +0100):

Sara Golemon in php.internals (Thu, 4 Jan 2018 12:06:59 -0500):

I'm happy to announce not one, but two new PHP releases today.
PHP 7.1.13 and 7.2.1 are ready to go at http://php.net/downloads.php

Is it on purpose that the release-zip on github contains PHP 7.2.1-dev?
See the main/php_version.h in the zip at
https://github.com/php/php-src/releases

The main reason why I prefer the github zips over the zips at
http://windows.php.net/download/ is some kind of mismatch in the UTF-8
filenames:

php-7.2.1-src/ext/bz2/tests/003????????????.txt.bz2: mismatching "local"
filename (php-7.2 .1-
src/ext/bz2/tests/003||||||||||||||||||||||||||||||||||||.txt.bz2),
continuing with "central" filename version
php-7.2.1-src/ext/exif/tests/bug34704????????????.jpg: mismatching "local"
filename (php-7 .2.1-
src/ext/exif/tests/bug34704||||||||||||||||||||||||||||||||||||.jpg),
continuing with "central" filename version
php-7.2.1-src/ext/exif/tests/bug68113????????????.jpg: mismatching "local"
filename (php-7 .2.1-
src/ext/exif/tests/bug68113||||||||||||||||||||||||||||||||||||.jpg),
continuing with "central" filename version
php-7.2.1-src/ext/exif/tests/test2????????????.jpg: mismatching "local"
filename (php-7.2.
1-src/ext/exif/tests/test2||||||||||||||||||||||||||||||||||||.jpg),
continuing with "central" filename version etc.

The "central" filename version is the correct one, like the filename at
https://github.com/php/php-src/tree/master/ext/bz2/tests

The zips at github do not have the mismatch and do contain the correct
filenames. So github seems to handle UTF-8 filenames in better way than
https://github.com/php/php-
src/commit/3d3f11ede4cc7c83d64cc5edaae7c29ce9c6986f

I don't reproduce this issue using http://windows.php.net/downloads/releases/php-7.2.1-src.zip . There is always a chance for a tool issue, especially when using an older tool or some without Unicode support. For zip, tools that work is the latest 7zip 16.04 or even explorer. Also using tar 1.29 and git 2.14.3 from the msysgit package looks fine for any tarballs. Seems like a tool issue, for what I could tell.

Regards

Anatol

PHP 7.1.13 and 7.2.1 Available

Is it on purpose that the release-zip on github contains PHP 7.2.1-dev? See the main/php_version.h in the zip at https://github.com/php/php-src/releases

N:\php-sdk\win32sdk2 $ unzip -h UnZip 6.00 of 20 April 2009, by Info-ZIP. Maintained by C. Spieler. Send bug reports using http://www.info-zip.org/zip-bug.html; see README for details.

The zips at github do not have the mismatch and do contain the correct filenames. So github seems to handle UTF-8 filenames in better way than https://github.com/php/php- src/commit/3d3f11ede4cc7c83d64cc5edaae7c29ce9c6986f

Is it on purpose that the release-zip on github contains PHP 7.2.1-dev?
See the main/php_version.h in the zip at
https://github.com/php/php-src/releases

N:\php-sdk\win32sdk2
$ unzip -h
UnZip 6.00 of 20 April 2009, by Info-ZIP. Maintained by C. Spieler. Send
bug reports using http://www.info-zip.org/zip-bug.html; see README for details.

The zips at github do not have the mismatch and do contain the correct
filenames. So github seems to handle UTF-8 filenames in better way than
https://github.com/php/php-
src/commit/3d3f11ede4cc7c83d64cc5edaae7c29ce9c6986f