Jameson Graef Rollins <jroll...@finestructure.net> writes: > Hi, Russ. Thanks for the bug report, and I'm very sorry about the > trouble.
No worries. I'm more bemused than anything, since the required package was so obscure. :) > I wonder though if this is a Gtk packaging issue instead of an assword > one. assword includes a dependency on the python gtk package it > utilizes (python3-gi). If that package is non-functional without other > packages installed, doesn't that mean that pytho3-gi is missing a > dependency? Seems like we should forward this to python3-gi. I tried to figure out if that's the case. I think the problem may be that python3-gi is intended to support a very wide variety of different packages that use GObject, and therefore doesn't depend on any of them explicitly (since they may not be used in a particular use case). Once I finally thought about the long description of that package, I noticed it says: This package contains the Python 3 binding generator for libraries that support gobject-introspection, i. e. which ship a gir1.2-<name>-<version> package. (which is how I finally figured out the right package). There are *tons* of those packages in the archive: $ apt-cache search ^gir1.2- | wc -l 201 So if it can work with any of those packages, I understand why they don't depend on any of them. I do agree that there should be some kind of warning somewhere in the python3-gi package (and I couldn't find anything in /usr/share/doc/python3-gi) that packages that depend on it need to also depend on the gir1.2-* packages corresponding to the interfaces that they use. I suspect most people haven't run into this problem because they're using assword on their laptop where they have GNOME or something installed, which ends up pulling in these packages anyway. (I have a somewhat unusual use case where I'm running assword on a remote server over a forwarded X connection.) -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
