Hi Sean,
Le 2025-02-25 11:27, Sean Whitton a écrit :
You have now come to debian-devel and posted a highly inflammatory
message accusing all sorts of things of being broken, while actually
arguing in fairly vague terms.
On the discussion in question there are several references of actual
cases where the current handling of gitattributes breaks things. There
is also a merge request with a test case that reliably reproduces the
issue. I do not think this qualifies for "vague terms".
On the other hand, I have yet to see actual cases where not disabling
gitattributes would break things, despite asking several times. I would
also like to see the very real problems that are reported acknowledged
by the sponsors of "gitattributes defusing".
I don't think any productive discussion can be had in response to your
message.
Casually dismissing the concerns and avoiding this necessary discussion
is not a helpful attitude.
And for the avoidance of doubt: both gbp and dgit are committed to
being
usable in as many situations as possible; they are not fundamentally
broken;
I'm not saying anything else here. My point is that it's the way
gitattributes "defusing" is implemented that is fundamentally broken,
and that this makes it unsuitable as a configuration default considering
the goals above.
they are not setting up some sort of parallel git ecosystem.
Not at all.
This isn't congruent with what is actually happening and with [1]:
Note that enabling gitattributes will make the tree incompatible with
tag2upload.
Cheers,
[1]:
https://salsa.debian.org/salsa-ci-team/pipeline/-/merge_requests/581#note_587974
--
Julien Plissonneau Duquène
