Control: close -1
Thanks for the report. But, having reviewed this bug, I think all of
dgit's behaviour here is correct.
What's wrong is that the git tree and .orig have mismatched line
ending conventions.
I've conjectured that this is tolerated by other tooling (eg
git-buildpackage) because
Stéphane Glondu writes ("Re: Bug#1005765: dgit doesn't handle upstream files
with CRLF well"):
> I had trouble uploading opam/2.1.2-1 with dgit. Eventually, I gave up
> and did a regular upload.
>
> The commit id is 225dd4102cfd4391fab166d7cc220d020efedafd on:
>
>
Hello,
Le 03/09/2022 à 18:43, Ian Jackson a écrit :
I wrote:
I think that if
- your upstream files have CRLF in the orig
- your upstream files have CRLF in your git tree
- you do not expect (or enable) line ending conversions in git
then
- dgit will not complain
- the source package
Control: tags -1 moreinfo
I wrote:
> I think that if
> - your upstream files have CRLF in the orig
> - your upstream files have CRLF in your git tree
> - you do not expect (or enable) line ending conversions in git
> then
> - dgit will not complain
> - the source package you produce will
Stéphane Glondu writes ("Bug#1005765: dgit doesn't handle upstream files with
CRLF well"):
> I just tried to upload opam with dgit, and I couldn't because of
> pretended differences in upstream files. However, these differences
> consist of line endings only. I couldn't
Package: dgit
Version: 9.15
Severity: important
Dear Maintainer,
I just tried to upload opam with dgit, and I couldn't because of
pretended differences in upstream files. However, these differences
consist of line endings only. I couldn't find a combination of
checked-in files and git crlf
6 matches
Mail list logo
