#1133409 openmcdf: Depends on non-existing binary

#1133409#5
Date:
2026-04-13 06:42:04 UTC
From:
To:
Trying to start structuredstorageexplorer ends with:
/usr/bin/structuredstorageexplorer: 3: exec: /usr/bin/cli: not found

and installing the mono-runtime additionally yields:
Unhandled Exception:
System.TypeLoadException: Could not load type of field 'StructuredStorageExplorer.MainForm:hexEditor' (26) due to: Could not load file or assembly 'Be.Windows.Forms.HexBox, Version=1.5.0.0, Culture=neutral, PublicKeyToken=e0e5adf0ebc99863' or one of its dependencies.
[ERROR] FATAL UNHANDLED EXCEPTION: System.TypeLoadException: Could not load type of field 'StructuredStorageExplorer.MainForm:hexEditor' (26) due to: Could not load file or assembly 'Be.Windows.Forms.HexBox, Version=1.5.0.0, Culture=neutral, PublicKeyToken=e0e5adf0ebc99863' or one of its dependencies.

#1133409#10
Date:
2026-05-26 22:46:17 UTC
From:
To:
This is the combination of two issues that each shouldn't happen:

1. A maintainer breaking plenty of rdeps for dubious reasons [1] and
then just orphaing everything.[2]

2. A maintainer of an rdep not properly testing a change, and
therefore not noticing that it removes all package dependencies.[3]

Reverting the infrastructure of the mono ecosystem to the working trixie
status might be the best option?

cu
Adrian

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079871#12
[2] https://tracker.debian.org/news/1719512/accepted-mono-6141ds2-2-source-into-unstable/
[3] https://salsa.debian.org/dotnet-team/openmcdf/-/commit/6aa946a2365a9bbd3697930df6b8c3842b2978d4

#1133409#15
Date:
2026-05-26 22:56:55 UTC
From:
To:

#1133409#20
Date:
2026-05-27 03:38:18 UTC
From:
To:
Hi Adrian,

Am Wed, May 27, 2026 at 01:46:17AM +0300 schrieb Adrian Bunk:

Argh.  Thanks for checking!

Might be a good idea.

Thank you for your QA work
    Andreas.

#1133409#25
Date:
2026-05-27 12:12:50 UTC
From:
To:
Le Wed, May 27, 2026 at 05:38:18AM +0200, Andreas Tille a écrit :
Of course the problem is with mono, and not with openmcdf that has been umaintained
since 2016, and has currently *no dependencies at all*.

And then keep wondering why maintainers and developers no longer want to engage
with Debian…

PS: This is my only message here, interacting in a hostile environment is taxing
and I’m tired of exposing myself to the usual bullies.

#1133409#30
Date:
2026-06-11 07:11:33 UTC
From:
To:
I did look at #1111276 and #1079871 before writing my email, and I could
not find any explanation *why* this was necessary.

Based on what you wrote "unmaintained" was the only justification for
removing dh_clideps and telling maintainers to hardcode dependencies
instead, which is pretty backwards.

Unmaintained infrastructure is not good, but it only becomes a problem
when it breaks and is not easily fixable.

If there was an actual problem with cli-common, you should have
explainted it in the bugs so that other people have the opportunity
to understand the problem and try to fix it.

cu
Adrian