Il 24/04/2018 23:07, Michael Biebl ha scritto: > > Thanks for the bug report. > Seems we don't have any package in stretch yet, which uses > gir1.2-nma-1.0, which is probably why this issue has went unnoticed. > > But that also means, it's probably not that important to fix this via a > stable upload. Or put this differently: Why do you want to have this > fixed in stretch, is there any software you use in stretch that requires > gir1.2-nma-1.0? > > Regards, > Michael > > Thanks for reply, probably I not able to explain good in english, latest Clem comment here probably can:
https://github.com/linuxmint/Cinnamon/pull/7486 In this explain how to reproduce: https://gist.github.com/clefebvre/411ab17558fc4dc438085ce2b6cc9093 But also description of patch from upstream that fixed it I think explain good: > libnma/pygobject: libnma/NMA must use libnm/NM instead of legacy libraries > libnma uses libnm, and not libnm-util/libnm-glib. Hence, the python > bindings must load "NM" and not "NMClient"/"NetworkManager". > *As it was, the generated bindings for libnma were unusable and > loading them would fail with* > libnm-ERROR **: libnm-util symbols detected; Mixing libnm with > libnm-util/libnm-glib is not supported I personally think that only the fact the libnma binding is broken and anyone want use it in Stretch can have this issue is sufficient reason for fix it.
