One more: 1/ Do you really want to make libmm-glib0 depend on modemmanager? Why is that needed? This creates a nasty dependency loop.
Well, the dependency on modemmanager from libmm-glib0 is just recommends so is that so nasty then? This dependency state has been clarified with upstream developers.
Is this for the plugins? Having them in modemmanager also results in E: modemmanager: pkg-has-shlibs-control-file-but-no-actual-shared-libs W: modemmanager: postinst-has-useless-call-to-ldconfig W: modemmanager: postrm-has-useless-call-to-ldconfig
Seems like these are solved now by correct exclusion as suggesten below.
If libmm-glib0 is supposed to be a standalone library and needs those plugins, then they should be moved into libmm-glib0 (assuming upstream bumps the Version in the directory path) or have them in a libmm-glib-runtime package with libnm-glib0 depending on that.
No, I think they are used only by modemmanager.
If those modules are used by ModemManager and *not* by libmm-glib0, keep them in the modemmanager package but exclude them from dh_makeshlibs.
Japp. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
