On Sun, Feb 26, 2006 at 12:51:17PM +0100, Michal Čihař wrote: > Hi all > > I just noticed that pybluez appeared in NEW. I already have there > python-bluetooth (although it is not yet on recent version), which > contains the same upstream package :-).
whops! :-) that's timely!
>
> According to Debian Python Policy [1] I think that correct name of
> package should be python-bluetooth and not pybluez.
that seems sensible, although bluez is not the only bluetooth stack available
for linux (okay, it is included in vanilla kernels). Note that only the source
package is named pybluez, binary packages are python{,2.3,2.4}-bluez.
but yes, I would consider adding a python-bluetooth metapackage which depends on
python-bluez, just to be consistent with the recent bluez/bluetooth renaming
stuff.
>
> The reason I uploaded is that it will be needed by Wammu that will
> hopefully enter archive soon. However I have no need to maintain it
> myself (in fact I have no bluetooth devices to test it). So if this
> group is going to maintain it, please take over ITP [2] for it.
It is fine with me, if you have no need to maintain/test it! pkg-bluetooth is
supposed to take care of bluetooth package :)
I plan to get both packages (or only python-bluetooth?) removed from NEW and
then upload a new version of python-bluez with the above issues corrected.
albert: I'm going to close the ITP in the changelog and add python-bluetooth
depending on python-bluez, then upload 0.6.1-2
thanks,
filippo
--
Filippo Giunchedi
PGP key: 0x6B79D401
random quote follows:
Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are, by
definition, not smart enough to debug it.
-- Brian W. Kernighan
signature.asc
Description: Digital signature
