From: John <da_...@ya...> - 2015-10-03 18:25:47
|
After posting my observations to both this ML[1] and to the Arch Linux community[2], one of the Arch members believes that he has tracked down the cause of this bug to commit 78a2e110 via git bisect[3]. Reverting this commit and building against HEAD fixes the problem. Is there a formal bug tracking system for lirc or is this post sufficient? Thanks! 1. https://sourceforge.net/p/lirc/mailman/message/34506523 2. https://bugs.archlinux.org/task/46550 3. https://sourceforge.net/p/lirc/git/ci/78a2e110a355849d7fa0a51225e26ae9501d3285 |