nicoo

> Thank you for taking the time to explain all this. Everything is making more sense. Thanks for being patient about this. I'm glad it makes more sense now. >...

@skeeto I just updated the feature branch to solve the merge conflict, and while I was at it added some improvements to the systemd unit that I was experimenting with...

Ping?

@ApoRes1337 FYI, I'm currently packaging `endlessh` for Debian.

Update: I uploaded [`endlessh/1.0-1`](https://ftp-master.debian.org/new/endlessh_1.0-1.html) an hour ago; it's for now in the NEW queue, awaiting review by the ftp team. After that, it will become available in Debian sid (“unstable”)...

@SeinopSys The unit file in the package uses the correct binary path (I added [a distro-level patch]). In the future, please report bugs against the package in [Debian's bug tracker],...

@BenWiederhake @d7415 Yeap, the release team's policy of requiring binaries built on Debian infrastructure conflicts with the ftp team's policy of requiring binary uploads for NEW (so they can review...

Apologies for the reply latency: the package didn't clear NEW until November, at which point I was fairly unavailable (my partner and I had medical complications...)

Update: since @skeeto released v1.1 tonigh, I uploaded it to sid (with `urgency=medium`, so barring any problem that will arrive in testing in 5 days).

`endlessh` [got into Debian testing] today, and I just uploaded a version to [`buster-backports`] :tada: I think we can close this issue now :) [got into Debian testing]: https://tracker.debian.org/news/1099466/endlessh-11-1-migrated-to-testing/ [`buster-backports`]:...