From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9711] Recent libCEC version bump seems to break kodi package
Date: Sat, 25 Mar 2017 13:45:27 +0000 [thread overview]
Message-ID: <bug-9711-163-FHfJh3eRlP@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9711-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=9711
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|ASSIGNED |RESOLVED
--- Comment #12 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
We reverted libcec in commit
https://git.buildroot.org/buildroot/commit/package/libcec?id=9642d9589ce2c973340b391ddf0dd042b57025aa
to fix this issue. We will bump it again together with the Kodi 17 bump.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2017-03-25 13:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-05 14:20 [Buildroot] [Bug 9711] New: Recent libCEC version bump seems to break kodi package bugzilla at busybox.net
2017-03-05 15:00 ` [Buildroot] [Bug 9711] " 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 [this message]
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-FHfJh3eRlP@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.