<div dir="auto">This list has never been to discuss things breaking on -current... only on the latest stable release of Slackware. As has been said many times, you use ponce's thread on LQ to report issues with scripts on -current.<div dir="auto"><br></div><div dir="auto"><a href="https://www.linuxquestions.org/questions/slackware-14/sbo-scripts-not-building-on-current-read-1st-post-pls-4175561999/">https://www.linuxquestions.org/questions/slackware-14/sbo-scripts-not-building-on-current-read-1st-post-pls-4175561999/</a></div><div dir="auto"><br></div><div dir="auto">Jeremy</div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Thu, Dec 25, 2025, 6:26 PM David Chmelik <<a href="mailto:davidnchmelik@gmail.com">davidnchmelik@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I have double-checked it's indeed in lirc-0.10.2-x86_64-1_SBo's <br>
lib/udev/rules.d/60-lirc.rules.  I've just removed & rebuilt lirc before <br>
testing.  I now realise that's only for Slackware-current, which (unless <br>
you can tell me where such issues should be discussed) may be beside the <br>
point, because it breaks for people using that and if it not fixed will <br>
break Slackware 15.1-stable.<br>
<br>
On 12/25/25 11:42 AM, Jeremy Hansen wrote:<br>
> That file was updated after the release of lirc used on SBo. It does <br>
> not contain that command.<br>
><br>
> This is the version of the file included with the version on SBo.<br>
><br>
> <a href="https://sourceforge.net/p/lirc/git/ci/5914451b1bc739713da22f12639ee6cf5ebcee08/tree/contrib/60-lirc.rules" rel="noreferrer noreferrer" target="_blank">https://sourceforge.net/p/lirc/git/ci/5914451b1bc739713da22f12639ee6cf5ebcee08/tree/contrib/60-lirc.rules</a> <br>
> <<a href="https://sourceforge.net/p/lirc/git/ci/5914451b1bc739713da22f12639ee6cf5ebcee08/tree/contrib/60-lirc.rules" rel="noreferrer noreferrer" target="_blank">https://sourceforge.net/p/lirc/git/ci/5914451b1bc739713da22f12639ee6cf5ebcee08/tree/contrib/60-lirc.rules</a>><br>
><br>
> David doesn't seem to be using the version of lirc on SBo and updated <br>
> it without telling the distro he updated it and then complained it was <br>
> broken. Go figure...<br>
><br>
> I am the maintainer of lirc (only because it was unmaintained and it <br>
> was a hard dependency of kodi at the time). I haven't updated it due <br>
> to reports of v0.10 breaking a lot of people's setups.<br>
><br>
> All that being said, I do not use lirc, so if someone else who does <br>
> use it wants to maintain it, I'm happy to relinquish maintainership.<br>
><br>
> Jeremy<br>
><br>
> On Thu, Dec 25, 2025, 2:30 PM fsLeg via SlackBuilds-users <br>
> <<a href="mailto:slackbuilds-users@slackbuilds.org" target="_blank" rel="noreferrer">slackbuilds-users@slackbuilds.org</a> <br>
> <mailto:<a href="mailto:slackbuilds-users@slackbuilds.org" target="_blank" rel="noreferrer">slackbuilds-users@slackbuilds.org</a>>> wrote:<br>
><br>
>     Here's your problem:<br>
>     <<a href="https://sourceforge.net/p/lirc/git/ci/master/tree/contrib/60-lirc.rules" rel="noreferrer noreferrer" target="_blank">https://sourceforge.net/p/lirc/git/ci/master/tree/contrib/60-lirc.rules</a><br>
>     <<a href="https://sourceforge.net/p/lirc/git/ci/master/tree/contrib/60-lirc.rules" rel="noreferrer noreferrer" target="_blank">https://sourceforge.net/p/lirc/git/ci/master/tree/contrib/60-lirc.rules</a>>><br>
><br>
>     The rule has been present in lirc sources for the past 10 years,<br>
>     according to the commit at blame date. I guess it says a lot about<br>
>     how many Slackware users use it, that's why it went unnoticed for<br>
>     so long.<br>
><br>
>     Try contacting the script's maintainer so they could patch the<br>
>     rule in the SlackBuild. If they don't respond in a week or two you<br>
>     can submit the necessary change yourself after getting admins'<br>
>     approval here.<br>
><br>
>     On December 25, 2025 21:43:56 GMT+03:00, David Chmelik<br>
>     <<a href="mailto:dchmelik@gmail.com" target="_blank" rel="noreferrer">dchmelik@gmail.com</a> <mailto:<a href="mailto:dchmelik@gmail.com" target="_blank" rel="noreferrer">dchmelik@gmail.com</a>>> wrote:<br>
>     >Whenever I connect certain types of devices, I get an error like<br>
>     "udevd[n]: failed to execute '/usr/bin/sh' '/usr/bin/sh -c<br>
>     '/usr/bin/setfacl -m g:lirc:rw /dev/bus/usb/001/004 2>/dev/null ||<br>
>     :'': No such file or directory" and the devices don't work.<br>
>     _______________________________________________<br>
>     SlackBuilds-users mailing list<br>
>     <a href="mailto:SlackBuilds-users@slackbuilds.org" target="_blank" rel="noreferrer">SlackBuilds-users@slackbuilds.org</a><br>
>     <mailto:<a href="mailto:SlackBuilds-users@slackbuilds.org" target="_blank" rel="noreferrer">SlackBuilds-users@slackbuilds.org</a>><br>
>     <a href="https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users" rel="noreferrer noreferrer" target="_blank">https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br>
>     <<a href="https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users" rel="noreferrer noreferrer" target="_blank">https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a>><br>
>     Archives -<br>
>     <a href="https://lists.slackbuilds.org/pipermail/slackbuilds-users/" rel="noreferrer noreferrer" target="_blank">https://lists.slackbuilds.org/pipermail/slackbuilds-users/</a><br>
>     <<a href="https://lists.slackbuilds.org/pipermail/slackbuilds-users/" rel="noreferrer noreferrer" target="_blank">https://lists.slackbuilds.org/pipermail/slackbuilds-users/</a>><br>
>     FAQ - <a href="https://slackbuilds.org/faq/" rel="noreferrer noreferrer" target="_blank">https://slackbuilds.org/faq/</a> <<a href="https://slackbuilds.org/faq/" rel="noreferrer noreferrer" target="_blank">https://slackbuilds.org/faq/</a>><br>
><br>
><br>
> _______________________________________________<br>
> SlackBuilds-users mailing list<br>
> <a href="mailto:SlackBuilds-users@slackbuilds.org" target="_blank" rel="noreferrer">SlackBuilds-users@slackbuilds.org</a><br>
> <a href="https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users" rel="noreferrer noreferrer" target="_blank">https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br>
> Archives - <a href="https://lists.slackbuilds.org/pipermail/slackbuilds-users/" rel="noreferrer noreferrer" target="_blank">https://lists.slackbuilds.org/pipermail/slackbuilds-users/</a><br>
> FAQ - <a href="https://slackbuilds.org/faq/" rel="noreferrer noreferrer" target="_blank">https://slackbuilds.org/faq/</a><br>
<br>
_______________________________________________<br>
SlackBuilds-users mailing list<br>
<a href="mailto:SlackBuilds-users@slackbuilds.org" target="_blank" rel="noreferrer">SlackBuilds-users@slackbuilds.org</a><br>
<a href="https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users" rel="noreferrer noreferrer" target="_blank">https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br>
Archives - <a href="https://lists.slackbuilds.org/pipermail/slackbuilds-users/" rel="noreferrer noreferrer" target="_blank">https://lists.slackbuilds.org/pipermail/slackbuilds-users/</a><br>
FAQ - <a href="https://slackbuilds.org/faq/" rel="noreferrer noreferrer" target="_blank">https://slackbuilds.org/faq/</a><br>
<br>
</blockquote></div>