copr-devel September 2014

copr-devel@lists.fedorahosted.org

8 participants
9 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

epel-6-x86_64 cannot finish build
by Baurzhan Muftakhidinov 02 Oct '14

02 Oct '14

Good day, Today I've run a package to build in epel chroots, and all chroots succeeded except epel-6-x86_64, still running for 2 Hours. What could that be? See https://copr.fedoraproject.org/coprs/baurzhanm/llvm/build/34715/

1 2

glitch on monitor tab with chroots' order
by Baurzhan Muftakhidinov 30 Sep '14

30 Sep '14

Good day, I have noticed that on Monitor tab, the status of builds are displayed incorrectly when number of chroots is more than one (5 in my case). So I have one package to build in all 5 EPEL's. On Build id page, all builds were succeeded except epel6-x86_64. Status is like this Chroots: epel-5-x86_64: skipped epel-5-i386: skipped epel-6-i386: succeeded epel-6-x86_64: running epel-7-x86_64: succeeded But on monitor tab running status is displayed for epel5 i386 chroot. This could be because on Monitor tab EPEL's are being shown in descending order, and on build id page - in ascending order. Hope this is clear, Thanks

2 1

mock error building PatternFly for F21
by Greg Sheremeta 29 Sep '14

29 Sep '14

Can anyone assist with this? I have no idea what's wrong. Looks like a general error setting up the root for F21. http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/fedor… DEBUG util.py:283: Error: Package: redhat-rpm-config-26-1.fc21.noarch (fedora) DEBUG util.py:283: Requires: gnat-srpm-macros DEBUG util.py:283: You could try using --skip-broken to work around the problem Thanks, Greg Greg Sheremeta Red Hat, Inc. Sr. Software Engineer, RHEV Cell: 919-807-1086 gshereme(a)redhat.com

2 2

Copr upgraded
by Miroslav Suchý 29 Sep '14

29 Sep '14

I just upgraded copr.fedoraproject.org. There are several visible changes in this upgrade: * recent builds in left column and on: https://copr.fedoraproject.org/recent/ * api for monitor (BZ 1131286) * search for terms with dashes (BZ 1131499) * fedmsg broadcast info about submitter and owner now Have a nice day. Mirek Suchy

1 0

3rd-party kernel modules
by Andrew Deason 26 Sep '14

26 Sep '14

Hello, I've only heard about COPR recently, so I'm not terribly familiar with it. Are kmod or DKMS packages prohibited from COPR as in Fedora, or are they allowed? I don't think I saw this explicitly answered anywhere, but it's possible I just missed it. -- Andrew Deason adeason(a)sinenomine.net

2 2

[python-copr] python bindings to Copr api
by Valentin Gologuzov 22 Sep '14

22 Sep '14

Hello, We would like to announce python bindings to Copr api. Sources is available in the git: https://git.fedorahosted.org/cgit/copr.git/tree/python . Please read documentation with a few examples on rthd: http://python-copr.readthedocs.org/en/latest/ (or you could build them locally: cd python/docs && make html ). Packaged version (`python-copr`) will be soon available in f19-f21, epel6 update repos. Any feedback is welcome! -- Best regards, Gologuzov Valentin.

2 2

Problem with copr API authentication
by Mark Reynolds 15 Sep '14

15 Sep '14

Hello, I'm trying to upload a srpm to copr by using: curl --data "pkgs=http://mreynolds.fedorapeople.org/389-ds-base-09_12_2014-1.fc20.src.rpm" https://copr.fedoraproject.org/api/coprs/mreynolds/389-ds-base/new_build/ { "error": "Login invalid/expired. Please visit https://copr.fedoraproject.org/api get or renew your API token.", "output": "notok" } I did setup ~/.config/copr file correctly according to https://copr.fedoraproject.org/api First I'm not sure if this is the best way to upload a srpm, second, the issue might be because my shell id is "mareynol" but my fedora/copr account is "mreynolds". I know this uid discrepancy caused issues with the fedora folks, where they had to do some kind of alias for mareynol -> mreynolds. Any help would be appreciated. Thanks, Mark

3 3

[PATCH] [backend] broadcast both submitter and owner to fedmsg
by Ralph Bean 09 Sep '14

09 Sep '14

Back in commit 1a4473e7a4dc1adbff5868ae0395625bef78d17a, a change was introduced that changed the 'user' field in fedmsg represent the person who kicked off a build instead of the person who owned the particular copr. This broke code in other fedmsg consumers that tried to build links from that user field to https://copr.fedoraproject.org/$USER/$COPR This change re-introduces the copr owner's username to the message. --- backend/backend/dispatcher.py | 3 +++ 1 file changed, 3 insertions(+) diff --git a/backend/backend/dispatcher.py b/backend/backend/dispatcher.py index 52777e9..45429d5 100644 --- a/backend/backend/dispatcher.py +++ b/backend/backend/dispatcher.py @@ -191,6 +191,7 @@ class Worker(multiprocessing.Process): " build:{build} ip:{ip} pid:{pid}" content = dict(user=job.submitter, copr=job.project_name, + owner=job.project_owner, build=job.build_id, ip=ip, pid=self.pid) self.event("build.start", template, content) @@ -198,6 +199,7 @@ class Worker(multiprocessing.Process): "copr:{copr} build:{build} ip:{ip} pid:{pid}" content = dict(chroot=job.chroot, user=job.submitter, + owner=job.project_owner, copr=job.project_name, build=job.build_id, ip=ip, pid=self.pid) @@ -216,6 +218,7 @@ class Worker(multiprocessing.Process): " ip:{ip} pid:{pid} status:{status}" content = dict(user=job.submitter, copr=job.project_name, + owner=job.project_owner, build=job.build_id, ip=ip, pid=self.pid, status=job.status, chroot=job.chroot) self.event("build.end", template, content) -- 1.9.3

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

copr-devel September 2014