Hi again
Nowadays, in Debian, whether you see the transformed file depends on
whether your git working tree has had the gitattributes "defused".
This is nowadayus done by gbp clone and perhaps other gbp operations
(as well as by dgit clone). The tag2upload builder defuses
gitattributes at the very start, because it also requires that its
output be predicteable and stable.
Ahh... TIL gbp clone did that.
Indeed with gbp clone I end up with LF EOLs.
When I push gbp import-orig to import the tarball, that file switches to
CRLF.
$ gbp clone https://salsa.debian.org/science-team/python-bumps.git
$ cd python-bumps
$ file doc/make.bat
doc/make.bat: DOS batch file, ASCII text
$ git tag -d upstream/1.0.5
$ gbp import-orig --uscan --upstream-version 1.0.5
$ file doc/make.bat
doc/make.bat: DOS batch file, ASCII text, with CRLF line terminators
It would be quite unfortunate if in an effort to be able to make Debian
workflows more standard and less dependent on special Debian tools, we
ended up not being able to just "git clone" from salsa but need a
special tool to do so (such as gbp clone).
(FWIW I concur that it would be lovely for these .gitattributes to
simply go away. I've never had anything but trouble with them and
equivalent ideas in svn, but my experience is that is messy to get rid
of them across a distributed developer base, and upstreams don't always
want to go there.)
regards
Stuart
--
Stuart Prescott http://www.nanonanonano.net/ [email protected]
Debian Developer http://www.debian.org/ [email protected]
GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
