Hi Bernhard,
> I still don't get why it's only happening now, and only with
> export=WC, as I'm not in that branch. Is it possible that the
> tarball generation somehow looks at the .gitattributes from
> HEAD (debian/master) instead of the current debian branch or
> upstream tag?
I recently suffe
Bernhard Schmidt writes ("Re: gbp-buildpackage showing change outside debian/,
possibly after DEP-14 conversion"):
> ---
> *.sln.in eol=crlf
> *.vcxproj.in eol=crlf
> *.vcxproj.filters.in eol=crlf
> ---
Glrgk. This is a harmful feature in git which should IMO genera
Am 12.03.19 um 09:12 schrieb Ian Campbell:
Hi Ian,
thanks a lot for your feedback
>>> I have no idea where the line terminators difference in one single
>>> branch in one single file that is never used in Debian builds comes
>>> from. I don't think it's the pristine-tar data, when I remove the
>
On Tue, 2019-03-12 at 08:10 +, Ian Campbell wrote:
> > I have no idea where the line terminators difference in one single
> > branch in one single file that is never used in Debian builds comes
> > from. I don't think it's the pristine-tar data, when I remove the
> > generated orig.tar.xz and h
> I have no idea where the line terminators difference in one single
> branch in one single file that is never used in Debian builds comes
> from. I don't think it's the pristine-tar data, when I remove the
> generated orig.tar.xz and have it regenerated with --git-no-pristine-tar
> it has a differ
Hi,
this has been bothering me for days and I can't find the reason. It is
probably something very trivial, but I don't get it. I have a
workaround, but I'd like to understand what went wrong here.
TL;DR: There is an unexplained linefeed difference in one file in the
orig.tar.xz2 generated by gbp
6 matches
Mail list logo
