Re: problem with lirc over network under Ubuntu 18.04

[Richard B. <ri...@g8...>]

Lets just get something straight here
The Normal thing to do is to ask on the user list, and if its not a
user problems to be point to filing a bug.

What did the LIRC developers do, ran for the hills hid from those
asking for help, didn't bother to answer those who ask, and now say
if bug reports had been filed they would have known.
They did an chose to do nothing, just relied on those on ther lists to
try and find a work around.
DISGUSTING BEHAVIOUR
Richard




On Fri, 2018-12-28 at 22:08 +0100, Alec Leamas wrote:
> 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.
> 
> 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.
> 
> 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
>