Hi, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948844
> > I am following the the "When upstream tags releases in git" section of > > dgit-maint-merge(7) and when I get to the "Now go ahead and > > Debianise..." section I'd like to be able to run debmake, but it's > > expecting the source dir to have a particular name and the orig tarball > > to exist. The last part is interesting point as usability. Otto pointed out this in https://bugs.debian.org/1090069 All you needed was adding -T/--tar option. When I recently updated debmake to 5.0.0, I addressed this hard to find solution by prompting user to activate this option instead of stop processing. So I closed #1090069. I am keeping this bug report open for better support of dgit which I use it too. Considering many packaging workflows (gbp is still widely used), I am inclined to add comment to required template. I need one clarification: For non-native package, dgit-maint-merge(7) recommend not to create debian/source/local-options but create debian/source/options containing: auto-commit I am following this with my own actual packaging but not with debmake template. I had vague impression that use of debian/source/options is problematic for NMUers who doesn't use the same set up for building. (Is this for GBP-type workflow?) Please confirm this auto-commit for dgit-maint-merge must be in debian/source/options and not in debian/source/local-options. What about other dgit work flow. How incompatible are debian/source/local- options. I understand dgit warn it but I want template file comment should be in line with expectation. I think as long as settings are commented out, debian/source/local-options file itself can be there for dgit. Am I correct? Let me know. Osamu
