Hi Thomas Thomas Goirand <z...@debian.org> writes:
> Hi Benedikt, > > So, according to what you wrote, there's a missing feature in Jessie. > But the general policy is to *not* add new features to the Stable branch > of Debian, and likely, the release team would refuse such an update. It's not a missing feature but a broken feature. The same feature was working in wheezy and is working in stretch. Also the log attached to the original report clearly shows that the feature was not just removed but is broken but intended to be present. > So I don't understand how any action can be made on this bug. > > Could you explicit what you expect the rabbitmq package maintainers to > do in this case? Bug severities are ultimately your call to decide upon but I would treat this as an RC bug in a package in stable, try to find the upstream commit that fixes it, apply this as a patch to the version in stable and upload to stable-proposed-updates. AFAIK the stable release team is commited to fixing RC bugs in stable updates even if they are only found after the release. I would consider this RC because it's a regression and because it makes it impossible to monitor the node. You need the node statistics for effective monitoring. Running something like RabbitMQ in production without monitoring is not an option IMO. Gaudenz P.S.: I tried to set the correct version information on this bug so that it's clear that it only affects stable. I hope I got it right, feel free to adjust if my commands did not do the right thing (TM).
signature.asc
Description: PGP signature
