Your message dated Wed, 19 Feb 2014 20:04:11 +0000
with message-id <[email protected]>
and subject line Re: Bug#673859: panflute: please detect dbus-python via Python 
(not pkg-config) or build-depend on python-dbus-dev
has caused the Debian Bug report #673859,
regarding panflute: 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.)


-- 
673859: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673859
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: panflute
Version: 0.6.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 panflute 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 AX_PYTHON_MODULE macro, or whatever.
In fact, it seems you already do this...

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).

Similarly, the PKG_CHECK_MODULES check for pygtk-2.0, pygobject-2.0 and
gnome-python-desktop-2.0 seems rather unnecessary, since there doesn't seem
to be any C code in the panflute package: it should be sufficient to look
for the corresponding Python modules with AX_PYTHON_MODULE, and then you
could lose several build-dependencies.

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.6.2-2+rm

Package removed from the archive, closing this bug. Sorry for the noise.

--- End Message ---

Reply via email to