2014-04-14 10:32 GMT+03:00 Jonathan Aquilina <[email protected]>: > @Timo if we file an SRU is it safe to say that we have you to back such a > request?
Sure. I can probably help best by reviewing any branch that's suggested to be merged against https://code.launchpad.net/~ubuntu-branches/ubuntu/trusty/lmms/trusty as part of that SRU. So here's a recap of what needs to be understood and done (there might be other ways too): 1. bzr branch lp:~ubuntu-branches/ubuntu/trusty/lmms/trusty # Base your branch on the current packaging branch in trusty, which includes both upstream sources and the debian/ packaging 2. Have Israel set up https://launchpad.net/lmms so that in addition to lp:lmms there's a code branch that tracks upstream 1.0.0-stable in addition to master 3. bzr merge lp:lmms/1.0.0-stable # (example, after the branch is there) 3.-2. Another possibility to 2./3. would be if there's eg. a 1.0.1 tarball, or a git archive:d 1.0.0+git20140415.abcdabcd tarball, and use bzr merge-upstream (see --help for instructions) and forget about bzr upstream mirror branches 4. Edit changelog to indicate a newer snapshot from the stable branch, refer to the LP bug where you describe the problem being solved in the SRU 5. Drop patches that are already part of the stable branch 6. Push your branch to eg lp:~myname/ubuntu/trusty/lmms/trusty_SRU and use Launchpad web interface to propose it for merging against lp:~ubuntu-branches/ubuntu/trusty/lmms/trusty 7. Follow all https://wiki.ubuntu.com/StableReleaseUpdates guidelines in setting the bug description et cetera The package should be buildable from the branch with 'bzr bd' (apt-get install bzr-builddeb) without errors of any kind. -Timo (Mirv @ Freenode) -- ubuntu-studio-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
