Hi,

Santiago Vila a écrit le 25/10/2026 à 17:47 :
You have a dangling symlink.

Since you have this information at hand would you mind sharing which one it
is. It would save me some time :)

Here is a way to see the dangling symlinks:

Modify /usr/share/dh-python/dhpython/fs.py so that it reads like this:

         if not options.allow_unmerged_dist_packages:
             remaining_files = "\n".join(
                 sorted(str(file) for file in Path(srcdir).rglob("*") if 
file.is_file() or file.is_symlink())
             )
             log.info("Remaining files: %s", remaining_files)
             raise SystemExit(1)

where we have changed "file.is_file()" to "file.is_file() or file.is_symlink()".

If you build the package after such change, you will see this message:

I: dh_python3 fs:179: Remaining files: 
debian/python3-med/usr/lib/python3.15/site-packages/med/_medenum.so.0
debian/python3-med/usr/lib/python3.15/site-packages/med/_medfamily.so.0
debian/python3-med/usr/lib/python3.15/site-packages/med/_medfield.so.0
debian/python3-med/usr/lib/python3.15/site-packages/med/_medinterp.so.0
debian/python3-med/usr/lib/python3.15/site-packages/med/_medlocalization.so.0
debian/python3-med/usr/lib/python3.15/site-packages/med/_medparameter.so.0

Thanks for sharing this. It is very much appreciated.

But how I see it, this is a bug in dh-python which handles removing / renaming shared libraries from the 'debian/python3-med/usr/lib/python3.15/site-packages/med/' folder.

The fact that it doesn't know what to do with symlinks such as '_medfield.so.0 -> _medfield.so.0.0.0' is not the fault of med-fichier or the way it is built.

The med-fichier build was fine before the upload of dh-python 7.20261019.

What do you think?

Best,
_g.

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to