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 you produce will have files with CRLF
- everything should work
If you have a repro that demonstrates the contrary, please let us
know. Typically a repro would consist of the following elements:
* The precise git commit that you had as HEAD in your working tree
We need the git hash; hopefully I can obtain the data from salsa.
* The precise contents of all relevant .origs
If they were already previously uploaded, we can get them from the
archive or snapshot.d.o. Otherwise please supply their
sha256sums, as well as instructions for download or creation (eg
pristine-tar branch).
* The precise dgit command line, and any configuration settings
applied to any of the relevant tools.
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:
https://salsa.debian.org/ocaml-team/opam
Ideally, a run with dgit -D would be helpful.
I will try when I update the package.
If you have a situation that doesn't match the criteria above, but you
think should be able to work, and currently doesn't, please also let
us know.
I'm not sure whether my situation matches the criteria above, but I
guess dgit should be able to do any upload to the official Debian
archive, shouldn't it?
Thanks for all your work on dgit!
Cheers,
--
Stéphane
