Public bug reported:
I tried to sponsor an SRU where the bug didn't have a task for the
release being SRUed into. sponsor-patch downloaded the current
development release version of the package and failed to apply the
supplied patch.
I'm not sure what it could have done instead. Some ideas
- DTRT and download the target release package (thus looking at the changelog
provided in the diff instead of the bug), then prompt to add a task for the
release (or offer to do it!)
- Warned at the start when it sees that the target was wrong (again looking
at the changelog)
- Provide a commandline option to override the target release
- If the patch fails to apply, simply explain to the user that sponsor-patch
requires the bug tasks to be set correctly as a hint as to what might be going
wrong.
** Affects: ubuntu-dev-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of MOTU,
which is subscribed to ubuntu-dev-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1100333
Title:
[sponsor-patch] Sometimes downloads packages for the wrong release
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1100333/+subscriptions
--
universe-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/universe-bugs
