copr-devel December 2014

copr-devel@lists.fedorahosted.org

3 participants
4 discussions

swig fails to build due to ccache test
by Baurzhan Muftakhidinov 11 Sep '15

11 Sep '15

Hello, I was trying to build swig on copr, but every time ccache tests fail. [1] I see on Koji swig builds are successful. Any advice on fixing build process? Thank you [1] http://copr-be.cloud.fedoraproject.org/results/baurzhanm/swig/fedora-rawhid…

2 6

Failed build - unfinished?
by Miro Hrončok 02 Jan '15

02 Jan '15

Hi, it just happened to me twice that a build failed in all chroots: https://copr.fedoraproject.org/coprs/churchyard/chromium-russianfedora/buil… However the build.log ends without nay clue what happened. Any advice? -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok

2 2

Re: Evil license Package question
by Rex Dieter 15 Dec '14

15 Dec '14

On 12/15/2014 10:01 AM, alexis jeandet wrote: > Hi, > > I would need to put two evil packages for digilent's analog discovery > board on Copr. This package would contain digilent adept runtime > (http://www.digilentinc.com/Products/Detail.cfm?NavPath=2,66,828&Prod=ADEPT2) and digilent waveform SDK (http://www.digilentinc.com/Products/Detail.cfm?NavPath=2,66,849&Prod=WAVEFO…) > in both case I got an explicit authorization to package it as long as I > don't use it for anything else than digilent products (an other ugly > point). The thing is that in my lab we write gpl apps which rely on this > api and I would like to share this apps on copr. > An other point, reverse engineering this crap would be really long since > there is an FPGA inside and as usual no source code for it... > > So is it allowed in such case to build a closed source package since it > doesn't really fit the Firmware exception(some files are libs). I would guess no: https://fedorahosted.org/copr/wiki/UserDocs#WhatIcanbuildinCopr You agree not to use Coprs to upload software code or other material ("Material") that: ... * is governed in whole or in part by a license not contained in the list of acceptable licenses for Fedora, currently located at https://fedoraproject.org/wiki/Licensing, as that list may be revised from time to time by the Fedora Project Board; Assuming the "evil" license in question here is not on the acceptable list above. -- Rex

2 1

Evil license Package question
by Jeandet Alexis 15 Dec '14

15 Dec '14

Hi, I would need to put two evil packages for digilent's analog discovery board on Copr. This package would contain digilent adept runtime (http://www.digilentinc.com/Products/Detail.cfm?NavPath=2,66,828&Prod=ADEPT2) and digilent waveform SDK (http://www.digilentinc.com/Products/Detail.cfm?NavPath=2,66,849&Prod=WAVEFO…) in both case I got an explicit authorization to package it as long as I don't use it for anything else than digilent products (an other ugly point). The thing is that in my lab we write gpl apps which rely on this api and I would like to share this apps on copr. An other point, reverse engineering this crap would be really long since there is an FPGA inside and as usual no source code for it... So is it allowed in such case to build a closed source package since it doesn't really fit the Firmware exception(some files are libs). Best regards, Alexis.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

copr-devel December 2014