Sorry, I should also have been thinking about it. This is entirely my fault and you were just being helpful. I am just so busy that it was easiest to just go with whatever you said :).
The best way is to Break the 'php-common‘ package because everything sort of depends on that. I’ll fix that in a moment. Ondrej -- Ondřej Surý [email protected] > On 18 Jun 2020, at 09:25, Paul Gevers <[email protected]> wrote: > > Hi, > > On 10/06/2020 20.27, Paul Gevers wrote: >> On 10-06-2020 09:22, Debian FTP Masters wrote: >>> xdebug (2.9.6+2.8.1+2.5.5-1) unstable; urgency=medium >>> . >>> * New upstream version 2.9.6+2.8.1+2.5.5 >>> * Add Breaks: php-defaults (<= 69~) to unbreak php-codecoverage >> ^ is one character too much. The >> idea was to add a breaks to the version currently in testing. So, either >> break <= 69 or breaks << 70~. > > It seems I have been giving you inaccurate advise. I didn't realize that > php-defaults isn't a binary package, but a source package, so the breaks > doesn't work at all. There's quite a few binary packages build by > php-defaults, do you know which one is actually being broken by xdebug? > > For the migration software, any of the binary packages will do, as the > migration software indeed only considers relations of binary packages at > the source package level, but as mentioned earlier, we want to prevent > real breakage on user systems in the case they don't do a full upgrade > or when the upgrade takes significant time and stuff is broken during > the upgrade because of ordering. > > Please let me know if you think I am exaggerating and if you convince me > I can tweak the situation via the back side, but obviously *you* are in > control of a technical correct solution. > > Paul >
signature.asc
Description: Message signed with OpenPGP
