Comment 2 for bug 876594

Technically this looks like one of those start-pulling-a-loose-thread-end-up-without-your-sweater problems. Nested deep down in the bowels of the package-copying mechanism, we have clever notification functions that cleverly figure out what's going on and who needs to be notified.

There seem to be a lot of possible scenarios that this code can be dragged into, so we'll want to start by reconstructing what they are, and who gets notified when. Then we pinpoint the changes we need, and come up with a more transparent way to connect high-level actions with notification policy.

Apparently lp.soyuz.adapters.notification.get_recipients is adding at least one recipient that we don't want in this case: the maintainer.