Movim / Laravel (PHP)

Bryce Harrington bryce.harrington at canonical.com
Wed Jun 9 23:21:52 UTC 2021


We intend to drop Movim and Laravel from the archive to facilitate the
PHP 8.0 transition.  If this impacts you or others you're in contact
with please let me know.

As mentioned previously, Symfony has been the main blocker for the PHP
8.0 transition.  We've resolved the build and test issues; once
this is released a number of remaining PHP packages should transition.

Laravel is a web framework built atop Symfony.  Movim is an app built
atop Laravel.  I don't think many users depend on this from our archive;
most install guides direct users to install from php composer.

We might bring Laravel and Movim back after PHP has transitioned, but
I'd like to get a better sense of whether there's a demand for it.  So
if you use it or know someone that does, and would prefer to consume it
from the archive rather than via compose, please let me know.

Thanks,
Bryce

https://bugs.launchpad.net/ubuntu/+source/php-laravel-framework/+bug/1931315

On Mon, Jun 07, 2021 at 09:07:47AM -0700, Bryce Harrington wrote:
> Update on status on the PHP 8 transition:
> 
> In addition to the core PHP language components, there are several
> sub-transitions needed for the various ecosystems written in the
> language.  One of these, a web framework called Symfony, is our main
> blocker right now; it was stuck in a circular build dependency with
> Twig, but that was resolved last week, and now its a matter of sorting
> out test and api/abi inconsistencies with Doctrine and various other
> packages.  We're working actively on this.
> 
> Any package mentioning symfony in update_excuses or log files is likely
> tied up with the above, and there won't be much to do for them until
> symfony is sorted out.
> 
> There are also some other PHP packages with unrelated build or test
> issues.  These are mostly either due to using pre-PHP8 syntax that needs
> cleaned up (sometimes there are patches upstream), or dependency issues
> with another package that needs updated to PHP 8.
> 
> Bryce
> 
> On Fri, May 14, 2021 at 08:54:45PM -0700, Bryce Harrington wrote:
> > Hi mwhudson,
> > 
> > The other day you mentioned you'd be on +1 duty next week and expressed
> > interest in how the php transition is going.
> > 
> > Here's a wiki page with the current state of things:
> > 
> >     https://wiki.ubuntu.com/ServerTeam/Transition/Php8.0
> > 
> > I've put in rebuilds for most of the stack by now, and a healthy chunk
> > has at least built and entered -proposed, and some has fully migrated.
> > A bunch of stuff is blocked by php-apcu and if that can migrate, a lot
> > more of the stack should migrate too.  The task here is getting symfony
> > and php-doctrine-cache to migrate, but they have some non-obvious test
> > failures that need investigation.
> > 
> > For items in that list that are FTBFS I've done some preliminary
> > investigation and noted possible solutions.  Some of these will be
> > pretty easy to fix.
> > 
> > The stuff under To Review probably just need nochange rebuilds but I
> > haven't had a chance yet to look through them.
> > 
> > I'll be out first half of Monday but will continue on this transition
> > through the rest of the week.
> > 
> > Bryce
> > 
> > On Wed, May 12, 2021 at 09:12:03AM -0700, Bryce Harrington wrote:
> > > Hi devs,
> > > 
> > > For impish the server team will be transitioning PHP to 8.0 over the
> > > coming weeks. (LP: #1927264) [0]
> > > 
> > > Since version 7.0, upstream PHP has adopted a regular release cadence[1],
> > > with one release per year. Each release is supported for 2 years, plus a
> > > third year of security critical fixes. PHP 8.0 was available last cycle
> > > but since changes from 7.4 to 8.0 were significant[2], we opted to postpone
> > > it to the 21.10 cycle and focused instead on resolving some phpunit
> > > 8.5->9.5 transition troubles. Landing PHP 8.0 this cycle will enable it
> > > to receive testing in a release prior to 22.04 LTS.
> > > 
> > > php8.0 has now been sync'd into impish from Debian experimental and set
> > > as the default PHP.  This breaks the PHP stack[3] and starts the actual
> > > transition.
> > > 
> > > Most or all of the PHP stack will need rebuilt at this point. This is
> > > phased due to package dependencies - for the php7.4 transition we
> > > started with php-propro, php-apcu, and php-msgpack; followed by
> > > php-apcu-bc, php-imagick, and php-igbinary; and then the rest of the
> > > stack. I anticipate php8.0's transition will proceed similarly.
> > > 
> > > Typically during PHP transitions, packages will fail to build or fail
> > > autopkgtests. Deprecated functionality[4] has been a common case and
> > > likely will be so for php8.0 as well[5]. There may also be
> > > phpunit-related issues in packages that didn't get re-built or re-tested
> > > since phpunit 9.5 transitioned.
> > > 
> > > Thanks,
> > > Bryce
> > > 
> > > 0: https://wiki.ubuntu.com/ServerTeam/Transition/Php8.0
> > > 1: https://www.php.net/supported-versions.php
> > > 2: https://stitcher.io/blog/new-in-php-8
> > > 3: https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#php-defaults
> > > 4: https://wiki.php.net/rfc/deprecations_php_7_4
> > > 5: https://stitcher.io/blog/new-in-php-8
> > > 
> > > -- 
> > > ubuntu-devel mailing list
> > > ubuntu-devel at lists.ubuntu.com
> > > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel



More information about the ubuntu-devel mailing list