SRU review. Three things contribute to the risk in the SRU:
1) > The origin of the patch is a third party repository, and it wasn't neither accepted nor rejected upstream yet. 2) The fix is only recently in Stonking so hasn't seen real world use yet. 3) The patch looks like high risk then that the fix inadvertently changes some other behaviour. https://ubuntu.com/project/docs/SRU/reference/requirements/#test-plan requires "If the instructions do not exercise the common use of the package, then further instructions on how to ensure that the package still works" but that's missing from the test plan. I'm not aware that procmail has a test suite at all. https://ubuntu.com/project/docs/SRU/reference/requirements/#what-is- acceptable-to-sru says "Stable release updates will, in general, only be issued in order to fix high-impact bugs". A fourth reason that affects the value of this SRU: 4) The bug report is also already 18 months old with only two people marked affected. It's unclear to me if any real world user is _still_ affected (https://ubuntu.com/project/docs/SRU/explanation/requirements/#real- world-impact) So on balance I don't think this is worth the risk of SRUing, taking into account there are probably a (relatively) large number of people using procmail who are not affected by this bug and the nature of the package is that it is sensitive to a regression. Rejecting the SRU and marking Won't Fix accordingly. Further discussion welcome. ** Changed in: procmail (Ubuntu Resolute) Status: In Progress => Won't Fix ** Changed in: procmail (Ubuntu Noble) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2096676 Title: procmail =| action assignment not working To manage notifications about this bug go to: https://bugs.launchpad.net/procmail/+bug/2096676/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
