Hi Andreas, Sorry for not responding sooner, some mail forwarding problem intervened. Looks like there's another serious problem with the security upload breaking the buster upgrade path, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981088. I haven't asked the Security Team yet, but if that problem can be solved through the security channel, then maybe this one could be as well? I mean a hypothetical 1.1.24-0+deb9u2 upload would (besides introducing the new binary packages for the new SONAMEs to fix #981088) also move /usr/lib/ocf/resource.d/pacemaker/ifspeed from pacemaker into pacemaker-resource-agents, fixing the buster upgrade. Do you think that would work out well? Or should we push this change regardless into buster and unstable and bullseye?
(I understand that introducing libpe-status16 wouldn't fix the damage already done by 1.1.24-0+deb9u2, and the workaround (upgrading pacemaker-cli-utils) is easy and already happened anyway in most of the cases. So we could also follow the tactic of leaving stretch-security alone, and tighten Breaks+Replaces in buster and beyond as you implemented here.) -- Thanks, Feri
