On 7 September 2015 at 18:45, Ian Malone <ibmalone(a)gmail.com> wrote:
On 7 September 2015 at 01:05, Dennis Gilmore <dennis(a)ausil.us>
wrote:
> On Friday, September 04, 2015 11:17:51 AM Ian Malone wrote:
>> Hi,
>>
>> It seems Fedora Jam is not included in current test composes for F23
>> and is not being included in nightly composes
>>
http://koji.fedoraproject.org/koji/tasks?state=all&view=tree&meth...
>> rder=-id (not failing to build as Live Workstation is, simply not being
>> included in attempted builds). I can't find any reference in spins@,
>> test@ or devel@ to this, except in the lead-up to F22 release that
>> there was an issue which was fixed (and didn't prevent Jam being
>> included in the release),
>> <
https://bugzilla.redhat.com/show_bug.cgi?id=1197940>. Has it been
>> intentionally dropped or has there just been some oversight?
>
>
https://pagure.io/releng/e6410e789dffff8805a6d49cbd6c988dc3400a22 it was
> removed 2 months ago as it had been failing to compose for a long period of
> time.
>
Thanks. What would we have to do to bring it back?
If I try to build the current fedora-live-jam_kde.ks I get:
Unable to open input kickstart file: curl#37 - "Couldn't open file
/tmp/livecd/fedora-livecd-kde.ks"
Looks like it disappeared in this commit:
https://git.fedorahosted.org/cgit/spin-kickstarts.git/commit/?id=8c810316...
Building on my F22 system with the include updated to
fedora-live-kde.ks, it also has an issue with ardour3 (now ardour4),
and libkolabxml (requires libboost_thread.so.1.58.0()(64bit), seems a
few nightlies are failing over libboost issues at the minute). If I
update ardour and kill the short list of things that want libkolabxml
then I get past install and dracut to the final creating image stage
and a failure on security contexts which is almost certainly just the
result of trying to build F23 on an F22 system.
--
imalone
http://ibmalone.blogspot.co.uk