Hot answers tagged git-buildpackage
3
If you could be more specific about the problems you are facing, I might be able to give you a better answer.
You might want to look as the pbuilder-dist script in the ubuntu-dev-tools
package. It greatly helps with managing multiple pbuilders for different target environments. As an example, to create a Karmic pbuilder run:
pbuilder-dist karmic create
...
2
I'd suggest something a little different than Flimzy. Take a look at git-import-dsc and possibly git-debimport. They will auto-magically create separate upstream, debian, and prinstine-tar branches from at Debian source package. You could then create your own branch for your patch set. Each time a new upload to Ubuntu is made, you can just run git-import-dsc ...
1
Actually, there is a section in the git-buildpackage documentation matching your use case.
Basically, the difference is that, when importing a new release into your debian branch, you will merge modifications from a tag corresponding to the new release of your software instead of a tarball. As no tarball is involved, there is no need to use git-import-orig.
...
1
I hope I'm understanding your question fully...
Here's how I do it:
Place the *.orig.tar.gz *.diff.gz and *.dsc files in a directory aptly named for your package
Unpack the source (dpkg-source -x *.dsc). You'll now have three files and one sub-directory
Commit this to your RCS (commit A)
Apply your changes, and commit to your RCS (Commit B)
Make any ...
Only top voted, non community-wiki answers of a minimum length are eligible
