Bug#448153: ITP: blueman -- GTK+ bluetooth management utility for GNOME
Whats the current status of this? If you have your current work uploaded somewhere? - Alexander -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#448153: ITP: blueman -- GTK+ bluetooth management utility for GNOME
Alexander Sack wrote: > Whats the current status of this? If you have your current work > uploaded somewhere? Yap. Take a look at unstable. -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#448153: ITP: blueman -- GTK+ bluetooth management utility for GNOME
On Tue, 05 May 2009 18:53:27 +0200 Christopher Schramm wrote: > Thanks for your reply. The reason there's nothing happening at the > moment is that I'm limited on time and don't have access to my Debian > Notebook right now. > > Your points 1 and 2 were already mentioned by another possible sponsor > (on debian-mentors mailing list) and put on my todo list. > > Point 3 was also mentioned and I'm not sure how to tackle it. I've > tried to compile the software with latest libbluetooth-dev 3.x in > unstable and it worked. The binaries ran fine at a quick test. But > can I be sure there will be no errors showing up at runtime? You'd probably want to ask upstream. Alternatively, uploading blueman to experimental wouldn't be the worst thing; once bluez 4.x enters unstable, you could simply do another upload at that point. It will have to spend some time in the NEW queue anyways. It's better to upload it ASAP (even if that means it will need to be in experimental) and then upload a newer version later. > > I will address your other points as well. I have to admit, I havn't > played with pbuilder, yet - only used lintian for checking Thanks! -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#448153: ITP: blueman -- GTK+ bluetooth management utility for GNOME
Thanks for your reply. The reason there's nothing happening at the moment is that I'm limited on time and don't have access to my Debian Notebook right now. Your points 1 and 2 were already mentioned by another possible sponsor (on debian-mentors mailing list) and put on my todo list. Point 3 was also mentioned and I'm not sure how to tackle it. I've tried to compile the software with latest libbluetooth-dev 3.x in unstable and it worked. The binaries ran fine at a quick test. But can I be sure there will be no errors showing up at runtime? I will address your other points as well. I have to admit, I havn't played with pbuilder, yet - only used lintian for checking -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#448153: ITP: blueman -- GTK+ bluetooth management utility for GNOME
On Tue, 5 May 2009 10:36:55 -0400 Andres Salomon 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 Copyright (C) 2008 Li Dongyang 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 -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#448153: ITP: blueman -- GTK+ bluetooth management utility for GNOME
Hi, What's the status of blueman packaging for debian? Would you like any help with this? -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#448153: ITP: blueman - GTK+ bluetooth management utility for GNOME
Package: wnpp Severity: wishlist * Package name: blueman Version : 0.19 Upstream Author : Valmantas Palikša <[EMAIL PROTECTED]> * URL : http://blueman.tuxfamily.org/ * License : GPL Description : GTK+ bluetooth management utility for GNOME Blueman is a GTK+ bluetooth management utility for GNOME using bluez dbus backend. The aim is to create a full featured graphical bluetooth manager for Linux. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
