Your message dated Tue, 04 Aug 2015 11:18:38 +0000 with message-id <[email protected]> and subject line Bug#794463: Removed package(s) from unstable has caused the Debian Bug report #673857, regarding apertium-tolk: please detect dbus-python via Python (not pkg-config) or build-depend on python-dbus-dev to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 673857: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673857 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Source: apertium-tolk Version: 0.2-2.2 Severity: wishlist dbus-python ships a header file and a pkg-config metadata file for use by out-of-tree main loop implementations, such as python-qt4 and python-edbus. These are intended to be pretty rarely used, a lot like python-gtk2-dev - the only packages which are intended to use them are Python bindings for main loop implementations (again, like python-qt4 and python-edbus). Unfortunately, several packages use pkg-config as a more general check for "is dbus-python installed?", and apertium-dbus is one of them. This has become significant because the header file and pkg-config metadata have moved to a new binary package, python-dbus-dev. At the moment, python-dbus depends on python-dbus-dev for backwards compatibility (to avoid breaking packages like yours), but I would like to remove that dependency (Bug #673779). Longer-term, work being done on pure-Python main loop support might mean that the C header and pkg-config metadata will eventually go away entirely in favour of pure-Python GLib, Qt and E main loop glue. The correct, long-term solution for packages that don't implement a main loop is to check for the dbus Python module (and, if required, the dbus.mainloop.glib Python module) as you would for a pure-Python module: run "python -c 'import dbus'", or use the AM_CHECK_PYMOD macro, or whatever. If you need to check the version number, it's exported by the dbus module as a string (dbus.__version__) and a tuple (dbus.version). I've also noticed that apertium-tolk has checks for the dbus-1, apertium-3.1 and pygtk-2.0 pkg-config modules, which can't possibly be right, because it doesn't seem to contain any C code at all... I think those can just be dropped (preferably upstream), and then you wouldn't need to build-depend on libdbus-1-dev, libapertium3-3.1-0-dev or python-gtk2-dev. If that's not feasible, the next best thing is to set your package's build-dependencies as if you were implementing a main loop: * build-depend on python-dbus-dev * if you support Python 2, also build-depend on python-dbus * if you support Python 3, also build-depend on python3-dbus Thanks, Simon
--- End Message ---
--- Begin Message ---Version: 0.2-2.2+rm Dear submitter, as the package apertium-tolk has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/794463 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
