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).

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.

Note that we decided to push these packages to a separate team, as we
don't really see drivers for heaters or air cond systems as very useful
for any other things than homeassistant. Things that do make sense for a
more general purpose will be pushed to the Python team as we see fit.

Cheers,

Thomas Goirand (zigo)

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi!

Thomas Goirand <zigo@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


--=-=-Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQJGBAEBCgAwFiEEz8XvhRCFHnNVtV6AnRFYKv1UjPoFAmajhFgSHGdzcHJAbm9u ZW1wdHkub3JnAAoJEJ0RWCr9VIz6/f4QANLgdkLP5DI2PhdSz07kW/cw704tLEH9 tFrUNjZsjsXF/QXHbeoLBAWHYPeT3fEJFQLcAfqjlYVUjiNO4orXcr/qnZwRGE0X 66akGt1FC+Ka6qtGPOwRXKsVpEb3EERqhkSrVXd0rhhxB8CpwYb0qqKq1TwVo177 bTSslRTGiliaSuvNCgFiHnpA/7B+A2VwyPPUJo2PEqoPvNW8BbtlKt9Etph7t224 oqUn0r5lKHbv2wQVUSIPLgj2Xn7x+YWE3gHbiW5H+sPY7/vTQCVB6OBet95dm/K8 XJVvVYywT6Uy32LFpf2zSJmcscUndf0DGCP2NwvOLJfOs+P7IKXiFx2BkD+lme5l EJKTV7kO517PqZ66kiYpbIqCamLNuAtIzREvcUzMziWnvMcTcoPO0ecyilLbs9ID nbskyaanVc/C+z6mVvRdLx424EP4vPDMod8csQpGPGYMMsPzeXnzZ7KLLU3juUuG Nvflg+wbcTV2Y+SZzH8f7I6FIHZlOAPz+zcAerfQcMjFay2LM8X6wMginoAZoZN6 xq+14IAfrtnB8FlzxhtRANK2wXCHHkE68T1I7PXk0MA60IBmOxCvEFbmXVMGVfv6 lUXeyaTbZPgFrhfgl5MU5dML9wsId8sy7j+GVTkRYMqswRoP2KSNrkUT4OBYl+1C
bc1Whir6roOY
=JaK2
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 17302 March 1977, Thomas Goirand wrote:

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).

Not going to stop you - I actually think it would be a nice thing to
have something like this packaged for real - but how realistic is this
in a Debian stable release (assuming you ever manage to get all of it
packaged and uploaded).

Using HA myself, that thing and all around it is changing faster than
anything else I ever saw. One basically finished updating ones install
and it goes again "Update available".

Combined with upstreams focus on their HassOS thing (and yes, that *is*
damn easy and low-effort to use!), is upstream support for "oh gosh you outdated distro" even there, in case this ends up in a stable release?


I sure would like if it ever goes with an "apt install homeassistant"
and you have what "put this HASSOS image into a VM/raspy and automate
away" does now, thats a cool target. But you found yourself a hill even
larger than the OpenStack one - and one that changes even more often and faster. :)

--
bye, Joerg

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Fri, Jul 26, 2024 at 03:25:09PM +0200, Joerg Jaspert wrote:

On 17302 March 1977, Thomas Goirand wrote:

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).

Not going to stop you - I actually think it would be a nice thing to
have something like this packaged for real - but how realistic is this
in a Debian stable release (assuming you ever manage to get all of it >packaged and uploaded).

Using HA myself, that thing and all around it is changing faster than >anything else I ever saw. One basically finished updating ones install
and it goes again "Update available".

Combined with upstreams focus on their HassOS thing (and yes, that *is*
damn easy and low-effort to use!), is upstream support for "oh gosh you >outdated distro" even there, in case this ends up in a stable release?

I sure would like if it ever goes with an "apt install homeassistant"
and you have what "put this HASSOS image into a VM/raspy and automate
away" does now, thats a cool target. But you found yourself a hill even >larger than the OpenStack one - and one that changes even more often and >faster. :)

--
bye, Joerg

As someone with a smart home setup that includes over 100 devices, I
totally get where Joerg is coming from. Keeping up with frequent updates
to stay on top of new features and device integrations can be a real
challenge, especially in Debain stable.

I’ve noticed that while Homebridge, with its plugins separated from main
app, might be easier to maintain than HA, it also has its own
limitations. Your hard work on integrating HA is impressive, and I
appreciate the effort you’re putting into it. It’s definitely a tricky
area with a lot to consider.

Cheers!
Yogeswaran.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 17302 March 1977, Thomas Goirand wrote:

Using HA myself, that thing and all around it is changing faster than
anything else I ever saw. One basically finished updating ones
install
and it goes again "Update available".

That's part of my motivation for having HA in Debian: I hate that it
wants to update too fast: faster than I can cope with, demanding too
much of my time. I do not really care having the latest shiny last
thing, I want something that works, that is reliable, and that I don't
have to maintain too much.

It's a fast moving target.
With an impressive rate of both, new features, and fixes.

Also, what really is there in the updates? Maybe one doesn't care
about
them 99% of the time. That driver foo for the device bar that you
don't
even use, do we really need to update it? I hope the core of Home
Assistant itself doesn't move *THAT* fast. It's hard to tell without inspecting all pieces of the puzzle.

Oh, for sure, if there are updates, you will get a load of "NEW VERSION"
bugs. *Someone* somewhere always needs *this* one new feature. :)

Combined with upstreams focus on their HassOS thing (and yes, that
*is*
damn easy and low-effort to use!)

[...]

This is clearly what I would like to stop doing. I currently have to,
because a few times, the automated upgrades of Home Assistant broke
badly on me. I'm sure it's going to happen again: it also happened to
some of my friends.

Actually it is the most stable thing I have here. And yes, I regularly
update that thing. Never had any huge problem. Smaller ones, easily
rolled back.

Also, for OpenStack, I've been mostly alone. We're currently 5
enthusiastic DDs in the Home Assistant team. It's possible even more
will join us. I don't think I'm even going to be the main driver
behind
this packaging, Edward seems very motivated, and he's done a lot
already.

Yah, saw him already.

Anyways, that's the beginning of an adventure. Where this will lead
us,
I'm not sure yet... For sure, looking at how, and even more
importantly
what things get updated by upstream will be interesting, and this will
tell us if it's possible to have this in Debian Stable. Maybe the only solution will be having most drivers in Debian Stable (the huge list
of
680+ python modules we're packaging), and have HA only in a
non-official
backport repo. IMO this would already be a great achievement.

Curious where you all will end up. Good luck!

--
bye, Joerg

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)