On 17/07/2023 07.16, Helmut Grohne wrote:
Then I found treinen@debian.org using edos-file-overwrite. That latter one seems like what I need here. Should we move it to the qa space and drop the edos part? I suggest debian-qa@lists.debian.org usertags file-overwrite. Otherwise, Ralf are you ok with me reusing your tag?
Moving the usertag to the qa namespace sounds like a good idea. And dropping the ancient edos prefix ...
edos-file-overwrite has been used primarily for file-vs-file conflicts (as these are the only ones detectable by analyzing .contents files) IIRC you were looking also for other cases, e.g. file-vs-directory. Maybe we should use two tags in combination, the general file-overwrite and a more fine-grained one describing the actual problem even better. We also didn't distinguish between file overwrites happening within a distro (two packages in sid shipping the same file) and on upgrades (the file in question moved between packages with insufficient Breaks+Replaces). Maybe we should.
There is also the case of files that shouldn't be shipped in any package (e.g. /usr/lib/python3/dist-packages/examples/README.txt), which usually shows up with a file-overwrite error if more than one package ships the file. IIRC I didn't tag these with the edos-file-overwrite usertag. (Such files are usually also reported to lintian to flag them as "overly generic filename", e.g. #947264)
Is there some place where these tags are documented? Ideally some wiki page with links to the corresponding bts query to get the bug lists ...
And information how these errors are searched for (semi-)automatically. Andreas