Hi! Thomas Goirand <z...@debian.org> writes:
> Dear friends, > > Together with a bunch of people during debcamp, we decided to package > homeassistant. This is a huge task, with hundreds of > dependencies. Since there's too many, we've been told to no Cc: > debian-devel@l.d.o when filing the ITPs, and instead write a summary > (as per developper's ref). Cool! > Well, we wont write such a summary, but everyone can follow our > progress on this wiki page, which fills the same purpose: > > https://wiki.debian.org/Python/HomeAssistant > > As you may see, there are 600+ packages to do. Since we're a lot of > people on the task, we believe it can be done. > > I've written 13 packages myself, and uploaded most already. Edward > Betts beated me by a very much higher numbers! billchenchina1 and > omnidapps already wrote many packages waiting in the NEW queue too. As the current maintainer of python-zigpy, on which at least 4 of those unpackaged items depend (+ probably HomeAssistant itself?): Would you be willing to adopt python-zigpy too? I've stalled a bit with keeping it up to date, mostly due to upstream seeming to not always take copyright very seriously [1]. That issue has been fixed, and as far as I know the current release (0.64.3) should be DFSG-compliant. However, as I'm not actively using ZigPy myself anymore, I've put updates on the backburner. A similar (imho unfixed) issue [2] can be seen in another package from the list, zigpy-znp. Learning of your HomeAssistant efforts, it seems sensible to hand python-zigpy off to your new team, if you'd agree. Apart from upstream's aforementioned issue, the package is very straightforward. The git repo [3] is up to date. Let me know what you think. [1] https://github.com/zigpy/zigpy/issues/1357 [2] https://github.com/zigpy/zigpy-znp/issues/206 [3] https://salsa.debian.org/gspr/zigpy/ Best, Gard
signature.asc
Description: PGP signature
