Steps to send patch to Launchpad
- by Alois Mahdal
With a Git/Github background and knowing very little about Bazaar VCS, I would like to occasionally report a bug to Launchpad and even send a patch. I'd like to do it in a "proper" way so that it's ready for merging or improvement while not getting in way.
I can't seem to find a decent simple How-to suited for my needs.
So what I did so far:
I have created a Launchpad account,
reported the bug,
installed Bazaar and setup SSH keys etc.
Now if it was Github, I'd
fork the repo,
clone the forked repo,
create a sanely named branch and do the work,
commit + push,
create a pull request using Github WUI.
But it's not Github, and both LP and Bazaar architectures seem quite different from their Github/Git cunterparts.
So could a kind soul save me from drowning in tons of documents and complile a straightforward step path, mainly the second part? Possibly including relevant CLI commands when they are needed?
Edit: It seems that I should clarify if I'm asking specifically about Ubuntu packages (whatever it means) or Launchpad packages.
I don't really care much about distinction between Ubuntu packages and non-Ubuntu packages. Any software could be in Ubuntu today and out of it tomorrow, or vice-versa. The development is what matters much more than distribution.
Ao I was assuming that
not every single package distributed in Ubuntu is hosted on Launchpad,
an "official" or "default" workflow for Launchpad exists (well if all devs can
agree on using Bazaar, why couldn't most of them agree on a patching workflow?),
so I'm asking about the Launchpad way, not the Ubuntu way. And I chose AU because since the intersection is vast, I guess it's pretty on topic here.
