On Jul 21, 2015, at 06:46 PM, Ian Jackson wrote: >That is, the dgit git tree contains the patches in debian/patches/ but >also contains the implied changes in the main source code. If you add >commits yourself to the dgit git tip, new patches will generated from >your commits. I think then that dgit's requirements are not compatible with git-dpm currently. IIUC, git-dpm presents you with either a patches-unapplied-but-with-debian/ view, or a patches-applied-no-debian/ view. E.g. `debcheckout python-pip` You'll be in the master branch which is the packaging branch, but `quilt applied` returns nothing, and `quilt unapplied` shows you that the patches are not yet applied. `git-dpm checkout-patched` leaves you in the transient `patched` branch, where the patches are applied, but you do *not* have a debian/ directory. `git-dpm update-patches` converts the commits back to debian/patches, but again leaves you patches unapplied. There's no current view where you have both patches applied *and* a debian/ directory. (FWIW, bzr-builddeb actually does present you with exactly this view, patches-applied-with-debian/) Cheers, -Barry
Attachment:
pgpt7QJR71FEq.pgp
Description: OpenPGP digital signature