copr-devel June 2015

copr-devel@lists.fedorahosted.org

5 participants
7 discussions

disable networking in Copr by default
by Pavel Raiskup 07 Jan '16

07 Jan '16

Just to be more pedantic and probably bit more secure, what about making networking in copr opt-in (at least for new projects)? If build of my package used internet arbitrarily, I would be warned very early.. Also, in Koji we also do not have networking, so we can faster teach (future) Fedora packagers. Thanks for considering, Pavel

3 3

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

Fedora 20 EOL
by Miroslav Suchý 24 Jun '15

24 Jun '15

FIY: Fedora 20 reached EOL yesterday. As usually I will give it 4 more weeks and then I will remove this target from Copr. Mirek Suchy

1 0

Usability suggestions for Copr web interface
by Martin Cigorraga 17 Jun '15

17 Jun '15

Hi all, First of all I want to say I'm really happy for having Copr, being an Arch user for many, many years I got really used to the AUR (Arch User Repository) so I can see Copr potential. And speaking about that, I would like to make some suggestions to improve the 'community' side of Copr as I believe from what I read the technical side is already very well covered: 1. Copr needs a place where users and packager(s) can discuss stuff about the packages and repositories, that could be achieved by simply letting logged people to comment on each Copr repo page; 2. Likewise it would be nice to have a way to: a) contact the packager(s)/maintainer(s), b) flag outdated packages, inform about any errors found. Having the chance for community to interact ultimately leads to improved workflows and better quality projects; some folks will look for guidance to create their first Copr repo, other people may want to lend a hand and offer maintain a repo packed with the stuff they usually use while others can just offer tips for improve things - or ask for assistance as well! Hope you guys take my suggestions in a positive way, I'm already happy to have a great infrastructure like Copr already set and ready for anyone to use, kudos! -Martín

6 11

Problems fetching binaries from github.com
by Alberto Ruiz 16 Jun '15

16 Jun '15

Hello, While trying to create a COPR build fetching SRPMs from a github release, COPR for some reason fails to fetch the file. I am wondering if somebody can test this and let me know if I'm doing something wrong here or this is in fact a COPR bug. You can give this a go with this SRPM URL: https://github.com/fleet-commander/fc -admin/releases/download/v0.0.99/fleet-commander-0.0.99-1.fc21.src.rpm -- Greetings, Alberto RuizRed Hat, Inc

3 5

New architecture: PPC64LE
by Miroslav Suchý 15 Jun '15

15 Jun '15

Hi, I just enabled new architecture in Copr - PowerPC 64 LE (little endian). There are those chroots available: * fedora-21 ppc64le * fedora-22-ppc64le * fedora-rawhide-ppc64le This happened as co-operation of Red Hat, Brno University of Technology and IBM. We have 4 VM available on a physical machine, which is physically located at Brno University of Technology. This is not ideal solution - as we have to copy the bits over the ocean - but it works. I hope that this is a temporary solution and one day we will get an IBM machine into PHX. However that can last several months, while this works now. Those VM have little bit more resources compared to Intel: 8 VCPU and 8 GB RAM (comp. to 3VCPU and 5GB RAM). Storage is the same - 50 GB per builder. I would like to thanks D, Horak and J. Capik from Secondary Archtectures for cooperation and making this happen. Enjoy and happy hacking Mirek Suchy

1 0

Build log links/filenames swapped?
by Richard Shaw 02 Jun '15

02 Jun '15

I had a failed build and went to inspect the logs, when I clicked on the link for the text log Chrome wouldn't display it, only download it. When I tried to open the file everything was garbled. On a whim I tried opening the .gz log file and it opened as plain text. I'm guessing the files are getting swapped somehow. Thanks, Richard

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

copr-devel June 2015