Bug#1133748: 6 packages from scotch fail to coinstall
Drew Parsons
dparsons at emerall.com
Sat May 2 16:58:20 BST 2026
On 2026-05-02 16:26, Helmut Grohne wrote:
>
>> The reporting tool found some file clash, but where exactly?
>
> It actually does not know. It only retains a checksum of the contents
> and concludes that when checksums differ, so does the content.
Yes, this is precisely what the tool knows, and is not reporting.
...
>
>> How does the tool know there is a clash? The tool should report what
>> it knows.
>
> Would you like it to include per-arch checksums of affected files?
Yes. Yes. Yes. Please.
>> Even knowing which architectures are involved would be helpful.
>
> I was working on that, but didn't find good solutions to this yet.
If what the tool is doing is measuring discrepant checksums, then that
is the good solution.
That is what it knows, but it is not reporting it.
If it reports the checksum for each arch then we can know where the
discrepancy is located.
The diff itself could also be useful but in some cases might be
unmanageable. A fragment of the full diff might still be useful, say the
first 40 or 100 lines, which would avoid the risk of bloated diffs in
the report.
But in any case identifying the arches involved (reporting checksums) is
absolutely crucial.
More information about the debian-science-maintainers
mailing list