[Pkg-xmpp-devel] Bug#939190: Incompatible to new symfony 4.x
Christian Ehrhardt
christian.ehrhardt at canonical.com
Mon Sep 2 07:35:37 BST 2019
Source: movim
Version: 0.14.1-5
Severity: serious
Tags: sid
Hi,
I was debugging issues in Ubuntu with dependencies of symfony that are
broken with symfony 4.x
Those are essentially unusable/uninstallable.
Initially reported to Ubuntu in [1] but applying to both Distributions
just as much. The bug [1] contains a much more detailed overview of
the cross-relations and the most likely options to resolve. Please
take look there avoiding to re-post the same (huge) text over and over
again.
Reporting in Debian against the direct dependencies to symfony so that
you are aware (thanks Steve for the reminder to do so). Overall that
means movim, ratchetphp, php-nesbot-carbon, php-robmorgan-phinx
Here the snippet for this package from there copy&pasted:
1. movim
- Debian/Ubuntu 0.14.1-5
- Upstream v0.15 (July 28)
- Symfony dependency fixes:
=> https://github.com/movim/movim/commit/a80bba27fa2983afd702fabcb91a3f11e85df58d
=> https://github.com/movim/movim/commit/98e4825ad20296af531106bb1d5697408924d5a6
The latter already is part of 0.14.1 but not in the tarball used by Debian.
It seems "their build" used the new components already in 0.14.1 (=>
composer.lock)
But the composer.json wasn't updated yet hence it is outdated and things like
debian/control:30: ${phpcomposer:Debian-require},
pull in the too old dependencies.
Note: it seems no actual changes were needed, but just patching
composer.json still seems to dangerous.
Solution:
a) update to 0.15 (FFE)
b) remove from Eoan
Removal would already make all other non-needed as well
c) update composer.json to accept v4
(might be ok - as it seems upstream 0.14.1 was built with symfony 4)
Rebuild then will pick up versions through ${phpcomposer:Debian-require}
[1]: https://bugs.launchpad.net/ubuntu/+bug/1842019
--
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd
More information about the Pkg-xmpp-devel
mailing list