Re: problem with lirc over network under Ubuntu 18.04

[Michael M. <mi...@ma...>]

Am 28.12.18 um 22:08 schrieb Alec Leamas:
> On 28/12/18 21:31, Michael Markstaller via LIRC-list wrote:
>> Am 28.12.18 um 20:49 schrieb Alec Leamas:
>>
>>> lirc being broken was finally raised as a bug in [1]. As evident from
>>> the bug the statement "lirc is broken" is plain wrong.
>> Well this is how you translate "broken".
>>
>> Broken is, if an update doesn't "just work" without manual intervention
>> - at least in my world.
> 
> 
> When you are using Ubuntu ýoy are not in your own world. Instead you are
> in the Debian/Ubuntu world. This world, formed by volunteers, is
> governed by a set of rules.

Yes, I know. this should not be offending to you personally.
I've said the same many times for such GREAT F* inventions like
systemd/Network-Manager (it's case-sensitive, sick!)


> While all of us working with packages tries to make smooth upgrades
> there is occasionally situations where a breaking update like this is
> required. This is according to the Debian/Ubuntu rules, and nothing
> strange.

No, it's just annoying for any user.

> Bottom line: lirc as of 18.04 is not "broken" because it was a breaking
> update (except perhaps in your own world).
> 
> That is not to say that there is no bugs in it. Some of those could have
> been fixed much sooner if users could have filed bugs. The embarrassing
> fact that lirc-config crashes on start in Debian could for example have
> been fixed long time ago with a simple bug filed.
> 
> Cheers!
> --alec
> 

Bottom line: lirc_atiusb was never updated or fixed (and I really tried..)
So everything after lirc 0.8.5 / kernel 2.6.32 is broken in "my world",
as thats what I'm using lirc for (with 12 remotes - BTW: perfectly
working for more than 10 years!)
So any update/upgrade is just no option..


best regards,

Michael