[Pkg-bluetooth-maintainers] Unnecessary renaming of development package

[Filippo Giunchedi]

On Wed, Jul 05, 2006 at 11:12:29PM +0200, Luk Claes wrote:
> > maintainers of affected packages have been informed once libbluetooth2 hit
> > unstable via mail to <package>@packages.debian.org (I can open relevant
> > transition bugs if needed).
> 
> The best thing would have been if they were informed beforehand of the
> upcoming transition... If you involved the Release Team back than, the
> current situation could probably have been avoided. The reason why bugs
> are preferred is like for all bugs that other people can help as they
> can see the issue, send patches, comments ...

allright, I'll be more careful.

> > allright, this looks like a quite straight transition to me, anyway I've yet to
> > see any reaction from maintainers except from gnokii/gammu ones.
> 
> Filing bugs might help...

this is undergoing, affected packages are:

Phil Blundell <pb at debian.org> (bluez-pin) [no more needed]
Hendrik Sattler <debian at hendrik-sattler.de> (obexftp openobex-apps)
Uwe Hermann <uwe at debian.org> (btscanner)
Michael Meskes <meskes at debian.org> (kdebluetooth kdebluetooth-irmcsync qobex)
Michael Banck <mbanck at debian.org> (libmultisync-plugin-irmc-bluetooth)
Matthew Johnson <debian at matthew.ath.cx> (bluemon)
Simon Richter <sjr at debian.org> (ussp-push)

> > Anyway, is this procedure documented somewhere? It doesn't seem like a good idea
> > to have libbluetoothX-dev when soname of the included library is in fact Y, but
> > perhaps I'm missing something.
> 
> Normally you shouldn't use libfooX-dev, you should use libfoo-dev
> instead unless you have a good reason to use libfooX-dev. If one does
> use libfooX-dev, one should at least have a time where libfooX-dev and
> libfooY-dev are co-installable (both packages in unstable at the same
> time), again unless you have a good reason not to do that.

I'm not sure if there was a good reason when the package was first created. If
that eases things for release team we can just rename it to libbluetooth-dev
while we are at it.

> 
> The part about communicating with the Release Team for transitions is
> included in all d-d-a mails from the Release Team AFAICS ...

got it, thanks

filippo
--
Filippo Giunchedi - http://esaurito.net
PGP key: 0x6B79D401
random quote follows:

Either this man is dead or my watch has stopped.
-- Groucho Marx
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-bluetooth-maintainers/attachments/20060706/3b5ea23d/attachment.pgp