[FFe] Upgrade to drupal8

Bug #1567061 reported by Nish Aravamudan
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
civicrm (Ubuntu)
Won't Fix
Undecided
Unassigned
drupal7 (Ubuntu)
Won't Fix
Undecided
Unassigned
drupal7-mod-arbiterjs (Ubuntu)
Won't Fix
Undecided
Unassigned
drupal7-mod-fontawesome (Ubuntu)
Won't Fix
Undecided
Unassigned
drupal7-mod-jqueryi18nproperties (Ubuntu)
Won't Fix
Undecided
Unassigned
drupal7-mod-jscommunicator (Ubuntu)
Won't Fix
Undecided
Unassigned
drupal7-mod-jssip (Ubuntu)
Won't Fix
Undecided
Unassigned
drupal7-mod-libraries (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

FFe justification: current drupal7 does not support PHP7.0.

We have two paths forward with Drupal in the archive for Xenial:

1) Keep drupal7 but leave it broken until upstream support for PHP7.0 is complete (https://www.drupal.org/node/2454439)

2) Package drupal8 which has PHP7.0 support and is currently passing regular tests.

This is a request to consider the latter before the release.

Nish Aravamudan (nacc)
description: updated
Revision history for this message
Nish Aravamudan (nacc) wrote :
Revision history for this message
Nish Aravamudan (nacc) wrote :

A test build is at:

https://launchpad.net/~nacc/+archive/ubuntu/php7

which was created with a uscan & uupdated after modificationts to the watch file as in attached tarball.

Revision history for this message
Martin Pitt (pitti) wrote :

This seems quite straightforward. drupal8 will be a new source/binary package, so there is zero risk in including it now. I think we shoudl remove drupal7 from xenial then. If some users need it, we can reintroduce it into xenial-updates later on when there's a version that works with php7 again, but I wouldn't ship a known-broken version in release. There are no reverse dependencies to drupal7.

Changed in ubuntu:
status: New → Confirmed
affects: ubuntu → drupal7 (Ubuntu)
Revision history for this message
Nish Aravamudan (nacc) wrote :

@pitti, agreed on dropping drupal7 if we pick up drupal8. I would appreciate some eyes on if everything is packaged properly, but it was fairly mechanical.

There are actually two revdeps on drupal7, src:drupal7-mod-libraries, which in turn pulls in a bunch of deps that can be removed and src:civicrm. I'll provide a debdiff for the latter, I think the former set should be removed if we remove src:drupal7.

Revision history for this message
Nish Aravamudan (nacc) wrote :
Revision history for this message
Steve Langasek (vorlon) wrote :

FWIW I don't consider it an obvious win to go with drupal8 in 16.04 rather than leaving drupal7 in, broken, and SRUing the php7 compatibility fixes post-release. Drupal8 being a major new upstream version, there is probably integration testing that would need doing anyway (drupal7 has no autopkgtests), and an unknown amount of packaging changes. To me, it seems that drupal8 for 16.04 implies more work now and more work later.

I accept Martin's judgement that drupal8 is ok for FFe, but as a sponsor I don't believe I can commit to having enough time to following through on this given relative priorities.

Revision history for this message
Nish Aravamudan (nacc) wrote : Re: [Bug 1567061] Re: [FFe] Upgrade to drupal8

On 10.04.2016 [01:19:56 -0000], Steve Langasek wrote:
> FWIW I don't consider it an obvious win to go with drupal8 in 16.04
> rather than leaving drupal7 in, broken, and SRUing the php7
> compatibility fixes post-release. Drupal8 being a major new upstream
> version, there is probably integration testing that would need doing
> anyway (drupal7 has no autopkgtests), and an unknown amount of packaging
> changes. To me, it seems that drupal8 for 16.04 implies more work now
> and more work later.
>
> I accept Martin's judgement that drupal8 is ok for FFe, but as a sponsor
> I don't believe I can commit to having enough time to following through
> on this given relative priorities.

100% ack. I wanted to get this bug filed, in case I was told/indicated
this was a better approach.

Revision history for this message
Jeremy Bícha (jbicha) wrote :

We can close this bug now that drupal7 with php7 support is in xenial-updates, right?

https://launchpad.net/ubuntu/+source/drupal7/7.44-1ubuntu1~16.04.0

Revision history for this message
Nish Aravamudan (nacc) wrote :

On Jul 18, 2016 11:35 AM, "Jeremy Bicha" <email address hidden> wrote:
>
> We can close this bug now that drupal7 with php7 support is in xenial-
> updates, right?

Yep, thanks!

Steve Langasek (vorlon)
Changed in drupal7 (Ubuntu):
status: Confirmed → Won't Fix
Changed in drupal7-mod-arbiterjs (Ubuntu):
status: New → Won't Fix
Changed in civicrm (Ubuntu):
status: New → Won't Fix
Changed in drupal7-mod-fontawesome (Ubuntu):
status: New → Won't Fix
Changed in drupal7-mod-jqueryi18nproperties (Ubuntu):
status: New → Won't Fix
Changed in drupal7-mod-jscommunicator (Ubuntu):
status: New → Won't Fix
Changed in drupal7-mod-jssip (Ubuntu):
status: New → Won't Fix
Changed in drupal7-mod-libraries (Ubuntu):
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.