----- Forwarded message from Dominik George <natureshadow@debian.org> ----- Date: Mon, 3 Dec 2018 13:09:37 +0100 From: Dominik George <natureshadow@debian.org> To: debian-devel@lists.debian.org Subject: Nasty dependency/bug situation (with php-zmq, but applicable in general) User-Agent: Mutt/1.10.1 (2018-07-13) Hi everybody, situation is as follows: I have a package (movim) which just got accepted into sid, and used to work properly. It now turns out that it is broken with PHP 7.3 - or rather, php-zmq has issues with PHP 7.3 [1]. Now the situation is as follows: * The bug is in php-zmq, but only with PHP 7.3. * Movim does not work due to that, but only with PHP 7.3. * PHP 7.3 is only in sid, testing has 7.2. This results in: * Movim, as it is, does not work in sid. * Once Movim migrates to testing, it works. As the issue is mot with movim, I'd rather not mark movim RC-buggy to stop it from migrating. Of course, the first step is to mark php-zmq RC-buggy in sid by reporting the upstream bug with severity grave. But there is actually no reason to remove php-zmq from testing until php7.3 migrates. I could tag the bug as only affecting sid - would that prevent auto-removal from testing? But in any case, this would become incorrect the moment php7.3 migrates. What is the correct course of action in such a situation, where a bug is in package A, but only if package B has version (>> X)? Cheers, Nik [1] https://github.com/mkoppanen/php-zmq/issues/193 ----- End forwarded message ----- -- PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26 B79A 3C16 A0C4 F296 Dominik George · Hundeshagenstr. 26 · 53225 Bonn Phone: +49 228 92934581 · https://www.dominik-george.de/ Teckids e.V. · FrOSCon e.V. · Debian Developer LPIC-3 Linux Enterprise Professional (Security)
Attachment:
signature.asc
Description: PGP signature