Hi,

> dgit: error: HEAD specifies a different tree to 
> golang-github-gen2brain-shm_0.2.1-1.dsc:
> dgit:  debian/.gitignore | 8 ++++++++
> dgit:  1 file changed, 8 insertions(+)
> dgit: Mode change from 000000 to 644: debian/.gitignore
> dgit: There is a problem with your source tree (see dgit(7) for some hints).
> dgit: For full diff showing the problem(s), type:
> dgit:  git diff 54e919be4a120eabfb8986c887b4e0a0f5513958 HEAD
> dgit:
> ! Push failed, while preparing your push.
> ! You can retry the push, after fixing the problem, if you like.

..
> > Is your suggestion to just stop having a `.gitignore` at all?
...
> I also never understood why we have that file in the first place.  Does
> anyone find it useful?  In which scenario does it do anything uesful?
> I've never found it contributing to my workflows, only breaking it.

I rarely make git commits with a dirty build tree, so personally I
don't need this file but also not keen on immediately removing it as
it seems to have been a feature to someone.

> Since I believe dgit/tag2upload to be(come) common among Go packages,
> and I lack any strong justification for debian/.gitignore that motivate
> using the old debsign+dput upload method as a workaround, I would like
> 'dh-make-golang make' to stop adding the file by default.

tag2upload has potential, but is of limited utility if it does not
store upstream tarball signatures or upstream tag signatures. I am
waiting for these to be fixed before I start using tag2upload:

* #1106071 wanted: tag2upload support for pristine-tar

* #1110269 tag2upload (and dgit?) should deposit upstream tags &
#1106073 dgit should convey upstream git tags to dgit-repos

* #1111331 git-debpush: check if CI passed before tagging

> There could be a -add-git-ignore parameter to use the current behaviour?
> If anyone likes the current behaviour, and wants to prohibit use of
> dgit/tag2upload.

You can just `git rm debian/.gitignore` as the immediate solution or
never commit it into git to begin with. No automation will re-add it.

Reply via email to