Hi Jean,
Thanks for taking the time to file a bug and help in making the Ubuntu server better.
This looks like a valid bug and I am glad that you've already found the cause and the workaround for this. That said, I can trace its origin in Debian (see: https://salsa.debian.org/openstack-team/third-party/rabbitmq-server/-/blob/02ca091d15ac35df0fba06b4e0ea4158f5325223/debian/rabbitmq-server.logrotate). So maybe you can file a bug in Debian and when this is fixed there, it'll automatically sync-in here for the next cycle.
Given it's trivial and not really affecting the package use or resulting in a crash or something, I'm marking this as "low" importance. However, if you think otherwise, please let me know and we can discuss this further.
Thanks, again! :)
Hi Jean,
Thanks for taking the time to file a bug and help in making the Ubuntu server better.
This looks like a valid bug and I am glad that you've already found the cause and the workaround for this. That said, I can trace its origin in Debian (see: https:/ /salsa. debian. org/openstack- team/third- party/rabbitmq- server/ -/blob/ 02ca091d15ac35d f0fba06b4e0ea41 58f5325223/ debian/ rabbitmq- server. logrotate). So maybe you can file a bug in Debian and when this is fixed there, it'll automatically sync-in here for the next cycle.
Given it's trivial and not really affecting the package use or resulting in a crash or something, I'm marking this as "low" importance. However, if you think otherwise, please let me know and we can discuss this further.
Thanks, again! :)