Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #10883 > unrolled thread

NMU Advice: pybluez

Back to article view | Back to linux.debian.maint.python

Contents

  NMU Advice: pybluez Diane Trout <diane@ghic.org> - 2018-09-10 23:20 +0200
    Re: NMU Advice: pybluez Sergio Durigan Junior <sergiodj@debian.org> - 2018-09-11 21:00 +0200
      Re: NMU Advice: pybluez Diane Trout <diane@ghic.org> - 2018-09-11 22:40 +0200

#10883 — NMU Advice: pybluez

[Multipart message — attachments visible in raw view] — view raw

Hi,

I was trying to do something with home-assistant and needed a Python 3
version of pybluez.

Unfortunately I found this bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839100
python-bluez: debian pybluez package version 0.22-1 uses upstream
source code version 0.18

Which also blocks #787850 (Compile for python 3.x)

I fixed the problems for myself, tried emailing the maintainer, and
everyone who'd commented on the bug, but its been a couple days and I
haven't heard back from anyone.

This seems like the kind of situation that would warrant doing a NMU
upload to the delayed queue?

But I wanted to check first.
Diane

[toc] | [next] | [standalone]

#10884

[Multipart message — attachments visible in raw view] — view raw

On Monday, September 10 2018, Diane Trout wrote:

> Hi,

Hi Diane,

> I was trying to do something with home-assistant and needed a Python 3
> version of pybluez.
>
> Unfortunately I found this bug:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839100
> python-bluez: debian pybluez package version 0.22-1 uses upstream
> source code version 0.18
>
> Which also blocks #787850 (Compile for python 3.x)
>
> I fixed the problems for myself, tried emailing the maintainer, and
> everyone who'd commented on the bug, but its been a couple days and I
> haven't heard back from anyone.
>
> This seems like the kind of situation that would warrant doing a NMU
> upload to the delayed queue?

I think the general rule-of-thumb is to wait around 2 weeks for a reply.
However, this package is team-maintained, so I would get in touch with
the team first and ask them to sponsor the upload.  This way, you won't
need to wait that much and can do a team upload.

If contacting the team doesn't work, then yeah, I'd certainly go for a
NMU.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

[toc] | [prev] | [next] | [standalone]

#10886

[Multipart message — attachments visible in raw view] — view raw

> I think the general rule-of-thumb is to wait around 2 weeks for a
> reply.
> However, this package is team-maintained, so I would get in touch
> with
> the team first and ask them to sponsor the upload.  This way, you
> won't
> need to wait that much and can do a team upload.
> 

Ah good idea.

Thank you for the suggestion.

Diane

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.python

csiph-web