On Thu, 25 Oct 2018 14:51:07 + (UTC) Gianfranco Costamagna
wrote:
> Hello Alec,
> can you please have a look at this debian/postinst issue?
> thanks
Confirmed. I missed to remove the links created in postinst in postrm.
Fix under way.
--alec
Hi Juhani!
Thanks for your reply, and sorry that I missed it! It was probably lost
in the noise, was not really prepared for a reply from the bug so to
speak. Listening to high-volume lists is not always easy :(
For better or worse, both upstream and the packaging has evolved since
your review.
Actually, there is yet another way to cope with this: adding the
immediate-init option to lircd (e. g., in lirc_options.conf). This will
make lircd exit if the hardware cannot be initialized. Which means there
will be no socket for clients to connect to. Making this the default
setup is a possi
On Sun, 19 Mar 2017 22:35:29 +0200 Adrian Bunk wrote:
> I cannot judge whether Depends is appropriate or would pull in too much,
> but a Recommends or at least a Suggests on all required packages is
> required.
Indeed, thanks for reporting. Will fix using a Recommends: , stay tuned.
In the lo
On Tue, 17 Jan 2017 03:12:49 +0530
=?UTF-8?B?c2hpcmlzaCDgpLbgpL/gpLDgpYDgpLc=?= wrote:
> Adequate reported multiple obsolete-conffiles for lirc -
>
> [$] adequate lirc
>
> lirc: obsolete-conffile /etc/lirc/irexec.lircrc
> lirc: obsolete-conffile /etc/lirc/lircmd.conf
> lirc: obsolete-conffile /
On Thu, 12 Jan 2017 20:52:12 +0100 Gianfranco Costamagna
wrote:
>
> > That is, is it really, really impossible to use the compatibility
> > package which actually works on Fedora to resolve this?
>
> can you please add more information on that?
> how does it work?
>
> G.
See #731424
--alec
... with this bug.
Given that it surfaces around kernel version 4.0, my first bet would be
that this is https://bugzilla.redhat.com/show_bug.cgi?id=1260862. It's
not hard to check, just look for the consecutive spaces described in the
bug.
This bug is fixed (really, worked around) in the la
7 matches
Mail list logo
