Bug#448153: ITP: blueman -- GTK+ bluetooth management utility for GNOME
On Tue, 5 May 2009 10:36:55 -0400
Andres Salomon <dilinger@queued.net> wrote:
> Hi,
>
> What's the status of blueman packaging for debian? Would you like any
> help with this?
I noticed that were looking for sponsorship:
http://groups.google.com/group/linux.debian.devel.mentors/msg/0ee01b3c5ac37c96
I would be happy to sponsor the package for you. After looking at the
package, I have a changes that are needed, though:
1) The copyright file should list the GPLv3, as that's what some (or
most) of the licenses specify. GPLv3 specifies v3 or later, which
doesn't include v2; having the copyright file say that the entire work
is under v2 is not correct.
2) The blueman/bluez directory has different authors; the copyright
file should mention that the copyright holder there is
Copyright (C) 2008 Vinicius Gomes <vcgomes [at] gmail [dot] com>
Copyright (C) 2008 Li Dongyang <Jerry87905 [at] gmail [dot] com>
3) There's a libbluetooth-dev build-dep that can only be satisfied with
the version of bluez that's in experimental. Is that a hard
requirement, or can it be worked around? If it is a hard requirement,
then the package will have to be uploaded into experimental rather than
unstable (so the distro entry in the debian changelog would have to be
adjusted).
4) There's a missing build-dep:
checking for PYGTK... configure: error: Package requirements (pygtk-2.0
>= 2.12.0) were not met:
No package 'pygtk-2.0' found
A build-dep on python-gtk2-dev (>= 2.12) should be added.
5) Another missing build-dep (be sure to test packages using pbuilder
or another such tool):
checking for PYNOTIFY... configure: error: Package requirements
(notify-python) were not met:
python-notify is necessary.
6) Another missing build-dep
checking for python module dbus... no
configure: error: Could not find Python module dbus
python-dbus fixes this.
7) Some lintian warnings which should probably be addressed:
W: blueman source: configure-generated-file-in-source config.log
W: blueman: copyright-refers-to-versionless-license-file
usr/share/common-licenses/GPL
Reply to: