I understand that these rabbitmq-server bugs are indeed hard to reproduce; this is unfortunately not the first time it happens :-/.
I looked at the debdiff you posted and I have a few comments about it:
- Since the patch comes from upstream (which is great, btw), it is common practice to add DEP-3 headers to it.
- Given that it was not possible to come up with a local reproducer for this issue, do you think the customer would be willing to try a PPA build of rabbitmq-server containing this patch? I think this is the "next best thing" in order to at least verify that this backport works for them.
- As a side note: rabbitmq-server is being sync'ed by git-ubuntu, which means that you can "git ubuntu clone rabbitmq-server", work on the proper branch (ubuntu/bionic-devel, in this case), push it to your LP namespace and create an MP off of it. It's not required, but may be easier to review/discuss. Up to you :-).
Thanks for the report and the patch, Seyeong.
I understand that these rabbitmq-server bugs are indeed hard to reproduce; this is unfortunately not the first time it happens :-/.
I looked at the debdiff you posted and I have a few comments about it:
- Since the patch comes from upstream (which is great, btw), it is common practice to add DEP-3 headers to it.
- Given that it was not possible to come up with a local reproducer for this issue, do you think the customer would be willing to try a PPA build of rabbitmq-server containing this patch? I think this is the "next best thing" in order to at least verify that this backport works for them.
- As a side note: rabbitmq-server is being sync'ed by git-ubuntu, which means that you can "git ubuntu clone rabbitmq-server", work on the proper branch (ubuntu/ bionic- devel, in this case), push it to your LP namespace and create an MP off of it. It's not required, but may be easier to review/discuss. Up to you :-).
Thanks.