Comment 2 for bug 2003259

Thanks for the MIR, however, as you wanted to do a simple MIR and not a full one, this is really lacking details and not tracking the real packages the MIRs are supposed to apply on.
Please be considerate for the reviewer and help them as much as possible by following the process, so that from one bug report, we can see:
- which source packages are impacted
- which binary packages needs to be promoted.

That, without any more verbiage.

Also, those packages were packaged a very long time ago, so it’s probably the right opportunity to ensure, especially with the split, that they all confirmant with the MIR policy.

So, do you mind:
- add one source package for any source package impacted.
- for each source package, check the MIR requirements and file the template, ONE FOR EACH, in the description (you can separate them by markers to make it clearer).
- state in each source package what code was moved where
- remove cups-filters source package from here, and tell what’s going to happens with current cups-filters source package. Should it be demoted?

Until there, I’m marking that bug as incomplete.