Hi Andreas, there will be new upstream release of PHP 7.3 this week, so I’ll handle it as one batch, ok?
I just wonder if there’s a way how to fix that without breaking co-installability with php7.0-curl from external repositories. What if we fixed this in php7.0-curl package? (I keep separate sources for it.) Ondrej -- Ondřej Surý ond...@sury.org > On 23 Mar 2019, at 16:50, Andreas Beckmann <a...@debian.org> wrote: > > Followup-For: Bug #925106 > > Hi, > > next round, let's add a Breaks: gforge-common (<< 6), too. > That's the version from jessie (there is no gforge-common in stretch, so > the jessie version may be kept installed on long grown system upgrades), > which will fail to remove under php7.3: > > Removing gforge-shell-postgresql (5.3.2+20141104-3+deb8u3) ... > PHP Deprecated: Methods with the same name as their class will not be > constructors in a future version of PHP; Error has a deprecated constructor > in /usr/share/gforge/common/include/Error.class.php on line 36 > PHP Fatal error: Cannot declare class Error, because the name is already in > use in /usr/share/gforge/common/include/Error.class.php on line 36 > dpkg: error processing package gforge-shell-postgresql (--remove): > installed gforge-shell-postgresql package pre-removal script subprocess > returned error exit status 255 > > This happens in multiple gforge packages, but can be prevented by > uninstalling it before php7.3 gets installed. > > > Andreas > <php7.3_7.3.3-2.dsc.diff.v2>
