Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
base system
Priority:
Critical
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
9 Sep 2015 at 01:13 UTC
Updated:
2 Oct 2015 at 03:05 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
joshtaylor commentedComment #3
joshtaylor commentedComment #5
webchickThis is something we'll want to do before RC. Escalating to critical.
Comment #6
RavindraSingh commentedRelease Notes - http://symfony.com/blog/symfony-2-7-4-released
Seems there are a lot of bugs has been fixed, we should also list down the which all sections of Drupal 8 will impact.
Comment #7
hussainwebThis patch should work. See #2531798: Handle binary files in patches for details.
Comment #8
hussainwebBTW, just FYI, I reused the patch I had created for #2565363: Upgrade to Symfony 2.7.4, which was a duplicate.
Comment #9
hussainwebComment #10
chx commentedThe issue summary says "This has no known security security fixes" and the beta evaluation says "Major because this release contains security fixes". Please fix. (Also WTF @ major because security! That should say critical because security but since it's critical already that's a bit moot.)
Comment #11
hussainwebIt must be a copy from the previous issue.
Comment #12
dawehnerReading the release notes it even seems to be nothing which affects Drupal
Comment #13
webchickUnfortunately this will need a small re-roll thanks to #2563799: Upgrade Guzzle to a tagged release. I debated putting this one in first, but decided it was probably better to get that one closed for good.
Comment #14
hussainwebFresh patch.
Comment #15
hussainwebComment #16
dawehnerIt is still super odd how big these changes to composer.lock / install.json actually can be.
Comment #17
webchickOk, great. Let's get this in.
Committed and pushed to 8.0.x. Thanks!
Comment #20
jibranDo we have symfony v2.7.5 upgrade issue yet? I'm unable to find one.
Comment #21
hussainwebCreated #2578805: Upgrade to Symfony 2.7.5