Bug#349705: [Pkg-bluetooth-maintainers] pybluez

2006-02-28 Thread Filippo Giunchedi
On Tue, Feb 28, 2006 at 02:00:21AM -0500, Albert Huang wrote: > > 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 > > Let me know if I should be working on renaming anything.. I'll just take > a backseat for now. not

Bug#349705: [Pkg-bluetooth-maintainers] pybluez

2006-02-27 Thread Albert Huang
> 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 Let me know if I should be working on renaming anything.. I'll just take a backseat for now. Regards, Albert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subj

Bug#349705: [Pkg-bluetooth-maintainers] pybluez

2006-02-26 Thread Filippo Giunchedi
On Sun, Feb 26, 2006 at 04:17:29PM +0100, Josselin Mouette wrote: > Wouldn't it more understandable with virtual packages? For example: > python-bluez provides: python-bluetooth and conflicts: python-bluetooth > python2.X-bluez provides: and conflicts: python2.X-bluetooth if this is okay with pyth

Bug#349705: [Pkg-bluetooth-maintainers] pybluez

2006-02-26 Thread Josselin Mouette
Le dimanche 26 février 2006 à 14:07 +0100, Filippo Giunchedi a écrit : > > A package with a name python-foo will always provide the module foo for > > the default Debian Python version of the distribution. > > mmh that's tricky, CC'ing debian-python. > > my rationale behind python-bluez is that b

Bug#349705: [Pkg-bluetooth-maintainers] pybluez

2006-02-26 Thread Filippo Giunchedi
On Sun, Feb 26, 2006 at 01:46:43PM +0100, Michal Čihař wrote: > > 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. > > If you want python-bluez, it should be reverse, qu

Bug#349705: [Pkg-bluetooth-maintainers] pybluez

2006-02-26 Thread Michal Čihař
Hi On Sun, 26 Feb 2006 13:38:35 +0100 Filippo Giunchedi <[EMAIL PROTECTED]> wrote: > On Sun, Feb 26, 2006 at 12:51:17PM +0100, Michal Čihař wrote: > > According to Debian Python Policy [1] I think that correct name of > > package should be python-bluetooth and not pybluez. > > that seems sensibl

Bug#349705: [Pkg-bluetooth-maintainers] pybluez

2006-02-26 Thread Filippo Giunchedi
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