From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9711] New: Recent libCEC version bump seems to break kodi package
Date: Sun, 05 Mar 2017 14:20:18 +0000 [thread overview]
Message-ID: <bug-9711-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=9711
Bug ID: 9711
Summary: Recent libCEC version bump seems to break kodi package
Product: buildroot
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: rizom91 at openaliasbox.org
CC: buildroot at uclibc.org
Target Milestone: ---
As requested on the GitHub page (see
https://github.com/buildroot/buildroot/commit/bf1c9828f2c7ef37a0af4da5532472fb7e03ba67),
I'm moving my issue/bug report to this bugtracker.
The last libCEC version bump (commit bf1c9828f2c7ef37a0af4da5532472fb7e03ba67)
seems to broke kodi-cec. Reverting this commit fixes the issue.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2017-03-05 14:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-05 14:20 bugzilla at busybox.net [this message]
2017-03-05 15:00 ` [Buildroot] [Bug 9711] Recent libCEC version bump seems to break kodi package bugzilla at busybox.net
2017-03-05 15:22 ` bugzilla at busybox.net
2017-03-05 15:29 ` bugzilla at busybox.net
2017-03-05 15:33 ` bugzilla at busybox.net
2017-03-05 15:43 ` bugzilla at busybox.net
2017-03-05 15:51 ` bugzilla at busybox.net
2017-03-06 7:03 ` bugzilla at busybox.net
2017-03-06 8:07 ` bugzilla at busybox.net
2017-03-06 18:14 ` bugzilla at busybox.net
2017-03-06 18:49 ` bugzilla at busybox.net
2017-03-06 19:34 ` bugzilla at busybox.net
2017-03-25 13:45 ` bugzilla at busybox.net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-9711-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox