-
Notifications
You must be signed in to change notification settings - Fork 2k
Add PHP 7.3-rc #677
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add PHP 7.3-rc #677
Conversation
Tests fail for alpine only. A similar error message has been reported for qemu: https://bugs.alpinelinux.org/issues/5768 I don't know enough about alpine / musl / ld / PHP / libssl to advise on this. |
And there's also this bug report for PHP itself: https://bugs.php.net/bug.php?id=76392 |
Probably will be fixed when php/php-src#3349 is merged. |
Looks like the version of Argon2 in Stretch also isn't new enough for PHP 7.3's requirements. 😞 |
@TimWolla linked to php/php-src@55277a6 in IRC (chased down the commit which added this new version restriction) |
As discussed in IRC: I added apt pinning to buster for libargon2. I opted to pin libargon2 for both 7.2 and 7.3 running on Stretch. If the changes are fine then this PR should “go green” once PHP 7.3 RC 1 lands, because that fixes the alpine issue. |
.travis.yml
Outdated
- VERSION=7.3-rc VARIANT=alpine3.7/cli | ||
- VERSION=7.3-rc VARIANT=alpine3.7/fpm | ||
- VERSION=7.3-rc VARIANT=alpine3.7/zts | ||
- VERSION=7.3-rc VARIANT=alpine3.6/cli |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want alpine 3.6 / 3.7 for 7.3 or should we go full 3.8?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, let's do only Alpine 3.8 for php:7.3. The plan is to migrate the others to 3.8 eventually anyway (probably by dropping 3.6).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
check.
It seems the alpine versions are still hitting https://bugs.php.net/bug.php?id=76392. |
Yes, they are. I linked that bug and the GitHub PR fixing it above:
#677 (comment)
It thus *should* work with the next release.
yosifkit <[email protected]> schrieb am Do., 12. Juli 2018, 02:31:
… It seems the alpine versions are hitting
https://bugs.php.net/bug.php?id=76392.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#677 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAMxdh-itM8SD7vG7UEtwjST5rwDewl_ks5uFpjqgaJpZM4U4dlF>
.
|
Alpine 3.8 include wget redis/docker-library-redis#151 |
Given that We might as well just download and compile it ourselves until it is in a stable release on Debian. cc @tianon. Perhaps we should put the argon2 download/install in a Dockerfile part like the apache and fpm blocks? |
If I understand it correctly then Conclusion: The only thing that may change in the near future is the ABI, which is irrelevant here, because we compile from source. |
We might need to update the apt pinning from |
Ooookay, I actually just performed a local build against sid, which already has the changes: In the current form the pinning will break the build once the migration to buster happens:
My suggestion thus would be: Pin After making these changes php:7.3-cli builds fine for me:
|
I did this, as the migration from sid to buster already happened and the build broke. This PR is updated to the current PHP 7.3 Beta 1. |
I'm definitely not thrilled about pulling from Also, as @yosifkit mentioned above, it's kind of odd that the templating bits for the Argon2 section aren't consistent with the other templating this repo is using. Would you rather we take over from here and just get this across the finish line? |
Tianon Gravi <[email protected]> schrieb am Fr., 10. Aug. 2018,
22:52:
Would you rather we take over from here and just get this across the
finish line?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#677 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAMxdu-hrMPs-2ABsYD3wul2kRrek_Jcks5uPfKJgaJpZM4U4dlF>
.
Do whatever you want with my PR, please. You are free to push into the
branch in my repository. You are free to close it as well. Just ship 7.3
already 😇
… |
… match the templating
🙌 |
That's awesome! What's the final tag? I'd guess Thanks a lot for this great work! |
(There'll be a PR later today.) |
- `docker`: 18.06.1-ce-rc2, `alpine:3.8` (docker-library/docker#124) - `mariadb`: 10.3.9 - `mongo`: 4.1.2 - `php`: 7.3-rc (docker-library/php#677), 7.2/alpine3.8 (docker-library/php#688)
This test verifies that Argon2 actually works for PHP images where it should. This is to ensure that the Argon2 from Buster does not magically change to become incompatible. see: docker-library/php#677 (comment)
- `drupal`: 8.6.0-rc1 - `ghost`: ghost-cli 1.9.1 - `memcached`: Alpine 3.8 (docker-library/memcached#40) - `mongo`: 3.6.7, `dbPath` fixes (docker-library/mongo#294) - `openjdk`: 11-ea+27 (Debian) - `percona`: 5.5.61, 5.6.41 - `php`: 7.1.21, Alpine 3.8 (docker-library/php#702, docker-library/php#688), 7.3.0beta2 (docker-library/php#677), 7.2.9 - `postgres`: fix `HOME` (docker-library/postgres#481) - `python`: `apk add --no-cache` to combat new `apk` behavior (docker-library/python#330) - `ruby`: bundler 1.16.4 - `tomcat`: 8.5.33, 9.0.11
Did a build with stretch-fpm + a bunch of extensions.