Sorry, wasn't thinking straight. There are four scenarios, I can think of, here: A: Package hasn't been SRUed yet, so there is no -proposed branch on LP. Submitter proposes merge into release pocket (there's nowhere else), we try to push to it, and fail. The best we can do here is not push. See bug 668948. B: -proposed and -updates branches exist, submitter proposes merge into -proposed. Everything is good. C: -proposed and -updates branches exist, submitter proposes merge into -updates. We follow that, and try to push to -updates. The package importer reverts it. D: -proposed and -updates barnches exist, submitter proposes merge into release pocket. We fail to push.
For C and D, we could redirect the pushes. Can't think of much else we can do here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/791956 Title: [sponsor-patch] does not work properly with uploads to -proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/791956/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
