Ok, so next steps here: a) This needs fixing in the development release of ubuntu, plucky, which will open soon. I can sponsor it for plucky, but the package is in sync now, and the same fix is already applied to debian. As soon as debian uploads, and plucky is open, we will get the fix. Which leads on to (b).
b) To update the ubuntu stable releases, we need to follow the SRU process[1]. For this bug here, what's needed in my view is: b1) update the description with the filled in template of the SRU template[2]. Impact should be easy/clear (it's a crash). Test plan sounds like it's just install, start the service, see the crash, update to the proposed version, notice no more crash. But the test should also include something else that shows that xymon is working (access URL, observe data flowing in, that sort of thing). b2) Create debdiffs or MPs with the same fix applied on top of the affected ubuntu releases, including jammy it seems. Maybe rebuild jammy with FORTIFY=3 to check if it also crashes? Is anybody willing to drive the SRU process? @Roland, are you going to do an upload to debian soon? 1. https://canonical-sru-docs.readthedocs-hosted.com/en/latest/howto/standard/ 2. https://canonical-sru-docs.readthedocs-hosted.com/en/latest/reference/bug-template/#reference-sru-bug-template -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078638 Title: coredumps with Xymon on 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/2078638/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
