Re: kodi on ci20 creator
On Mon, Apr 3, 2017 at 6:11 PM, James Cowgill <firstname.lastname@example.org> wrote:
> On 02/04/17 18:06, James Cowgill wrote:
>> [+CC multimedia team]
>> On 02/04/17 17:38, Mathieu Malaterre wrote:
>>> On Sun, Apr 2, 2017 at 6:03 PM, Mathieu Malaterre <email@example.com> wrote:
>>>> Hi there,
>>>> Does anyone knows what is going on with kodi dependencies on mipel ?
>>> OK I think I see the build dependencies loop:
>> With these binaries:
>> libchromaprint-dev | 1.2-1 | stable | mipsel
>> ffmpeg | 7:3.0.2-4~bpo8+1 | jessie-backports | mipsel
>> x265 | 2.0-4~bpo8+1 | jessie-backports | mipsel
>> And these sources:
>> chromaprint | 1.3.2-2~bpo8+1 | jessie-backports | source
>> ffmpeg | 7:3.2.4-1~bpo8+1 | jessie-backports | source
>> x265 | 2.0-4~bpo8+1 | jessie-backports | source
>> To build ffmpeg, we need chromapaint from jessie-backports. To build
>> chromapaint we need a working ffmpeg from jessie-backports, but ffmpeg
>> is broken due to the missing old x265.
>> I don't see a way to resolve this without either a binary upload or some
>> new bpo uploads (by eg temporarily disabling chromaprint in ffmpeg bpo).
>> I propose:
>> - Binary uploading chromaprint by manually installing the old x265
>> binaries from snapshot.d.o.
>> - Wait for ffmpeg to build on the buildds.
>> - binNMU chromaprint
>> Opinions? I probably won't get around to doing this until tomorrow.
> I've uploaded this now, but it looks like it's stuck in backports-policy
> at the moment.
> I had to build ffmpeg manually as well, because I overlooked that ffmpeg
> build-depends on a working ffmpeg through chromaprint.
Great I see it now:
Are you sure you should not also upload chromaprint:
Are is this simply a binNMU missing ?