copr-devel March 2019

copr-devel@lists.stg.fedorahosted.org

11 participants
12 discussions

IOError: Failed to write to /tmp/numpy_test_big_arrays....npy: [Errno 28] No space left on device
by Miro Hrončok 11 Apr '19

11 Apr '19

I just got this error in Copr. Should I skip big_arrays tests, or is this some quota on /tmp that can be enlarged? Thanks. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok

2 1

Requesting builder permissions via copr-cli or api
by Jiri Popelka 27 Mar '19

27 Mar '19

Hello, I've been investigating whether it's possible to request/apply for (builder) permission for a project via copr api or copr-cli. I.e. the equivalent of what I can do via https://copr.fedorainfracloud.org/coprs/<not-me>/<not-my-project>/permissions/. I haven't seen anything like that in api [1] or "copr-cli modify". The reason is that with packit [2] we eventually want to have a service that would build packages in copr, so that upstream maintainers could directly see (in a pull request), whether a upstream change (PR) doesn't break in downstream (fedora). And in case they wanted to use their existing copr repo, we'd need our service to have builder permission in that repo and we don't want to manually request it via web for every such project. Thanks, Jiri [1] https://copr-rest-api.readthedocs.io [2] https://github.com/packit-service/packit

2 1

Mock root cache - is there some? can I clean it?
by Miro Hrončok 21 Mar '19

21 Mar '19

Does copr cache mock roots? Can I clean the cache somehow? New gdb build from Fedora requires Python 3.7, but I had 3.8 in the buildroot. I've deleted my 3.8 builds, so i can rebuild gdb --without python, but apparently Python 3.8 stays in the buildroot and I get --allowerasing errors when I try to build anything. Error: Problem: package gdb-headless-8.3.50.20190319-2.fc31.x86_64 requires libpython3.7m.so.1.0()(64bit), but none of the providers can be installed - cannot install both python3-libs-3.8.0~a2-2.fc31.x86_64 and python3-libs-3.7.2-7.fc30.x86_64 - cannot install both python3-libs-3.7.2-7.fc30.x86_64 and python3-libs-3.8.0~a2-2.fc31.x86_64 - cannot install the best update candidate for package python3-libs-3.7.2-7.fc30.x86_64 - cannot install the best update candidate for package gdb-headless-8.3.50.20190319-2.fc31.x86_64 (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages) https://copr.fedorainfracloud.org/coprs/g/python/python3.8/builds/ Maybe I left something undeleted, but it is hard to see what. Thanks for help, -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok

1 1

Copr is going to remove build data from end-of-life chroots
by Jakub Kadlcik 18 Mar '19

18 Mar '19

Hello, I would like to let you know, that in the following few days, you will start receiving automatized notifications from Copr, telling you about deleting repositories for outdated chroots and how to proceed if you want to keep them for your projects. Please read more information about how it is going to work and our motivation for doing so, in my blog post. http://frostyx.cz/posts/copr-removing-outdated-chroots Also, please see the "Outdated chroots removal policy" in the Copr documentation. https://docs.pagure.org/copr.copr/copr_outdated_chroots_removal_policy.html Jakub

1 1

How can I resolve 'Copr timeout => sending INT' error?
by 藍挺瑋 16 Mar '19

16 Mar '19

What does 'Copr timeout => sending INT' mean in builder-live.log? This problem has existed for a long time and it often shows in my Chromium builds. While it is possible to click 'Resubmit' on failed builds and it usually takes 1 or 2 rebuilds to get successful builds, having to do the same thing for each Chromium update takes a lot of time because each build usually takes more than 15 hours. Here is an example file. Note that the file is large (> 600 M). https://copr-be.cloud.fedoraproject.org/results/lantw44/chromium/fedora-29-… At the end of the file, we can see: !! Copr timeout => sending INT Traceback (most recent call last): File "/usr/bin/copr-rpmbuild", line 158, in main action(args, config) File "/usr/bin/copr-rpmbuild", line 295, in build_rpm builder.run() File "/usr/lib/python3.6/site-packages/copr_rpmbuild/builders/mock.py", line 40, in run self.produce_rpm(srpm, configdir, self.resultdir) File "/usr/lib/python3.6/site-packages/copr_rpmbuild/builders/mock.py", line 124, in produce_rpm raise RuntimeError("Build failed") RuntimeError: Build failed The following links are examples of Chromium 72.0.3626.119 builds. For Fedora 29, it takes 3 times to succeed. I consider it the normal case. https://copr.fedorainfracloud.org/coprs/lantw44/chromium/build/861455/ https://copr.fedorainfracloud.org/coprs/lantw44/chromium/build/861866/ https://copr.fedorainfracloud.org/coprs/lantw44/chromium/build/862016/ This is likely the worst case. The build for Fedora 28 takes 7 times to succeed. Sometimes I just click 'Resubmit' without reading the log file. https://copr.fedorainfracloud.org/coprs/lantw44/chromium/build/861455/ https://copr.fedorainfracloud.org/coprs/lantw44/chromium/build/861866/ https://copr.fedorainfracloud.org/coprs/lantw44/chromium/build/862229/ https://copr.fedorainfracloud.org/coprs/lantw44/chromium/build/862543/ https://copr.fedorainfracloud.org/coprs/lantw44/chromium/build/862972/ https://copr.fedorainfracloud.org/coprs/lantw44/chromium/build/863432/ https://copr.fedorainfracloud.org/coprs/lantw44/chromium/build/863699/ While the normal case takes about 3 days to get a successful build, the worst case takes about 9 days.

2 2

ERROR: You can not write to /var/lib/dist-git/git
by Robert-André Mauchin 15 Mar '19

15 Mar '19

I'm trying to build package but they fail immediately with: Downloading https://copr-be.cloud.fedoraproject.org/results/eclipseo/rav1e/ srpm-builds/00869036/rust-glutin_egl_sys-0.1.1-1.fc31.src.rpm https://copr-be.cloud.fedoraproject.org/results/eclipseo/rav1e/srpm-builds/ 00869036/rust-glutin_egl_sys-0.1.1-1.fc31.src.rpm make sure repos exist: eclipseo/rav1e/rust-glutin_egl_sys cmd: ['/usr/share/dist-git/setup_git_package', 'eclipseo/rav1e/rust- glutin_egl_sys'], rc: 255, msg: ERROR: You can not write to /var/lib/dist-git/ git ERROR: You can not create repos Exception raised during package import. Traceback (most recent call last): File "/usr/share/copr/dist_git/package_import.py", line 117, in setup_git_repo subprocess.check_output(cmd, stderr=subprocess.STDOUT, encoding='utf-8') File "/usr/lib64/python3.6/subprocess.py", line 356, in check_output **kwargs).stdout File "/usr/lib64/python3.6/subprocess.py", line 438, in run output=stdout, stderr=stderr) subprocess.CalledProcessError: Command '['/usr/share/dist-git/ setup_git_package', 'eclipseo/rav1e/rust-glutin_egl_sys']' returned non-zero exit status 255. Any chance this could be fixed?

2 1

What's wrong with my build? Attempt to build SRPM have failed
by Miro Hrončok 14 Mar '19

14 Mar '19

I don't understand the failure, can you please help me debug it? https://copr.fedorainfracloud.org/coprs/g/python/python3.8/build/868314/ Thanks, -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok

3 3

Fedora 30 chroots now available in Copr
by Jakub Kadlcik 12 Mar '19

12 Mar '19

Hello, I've just enabled F30 chroots in Copr. The projects that have "Follow Fedora branching" enabled, have them automatically activated as well builds from rawhide forked into them. Jakub

1 0

pruning srpm-builds
by Miroslav Suchý 11 Mar '19

11 Mar '19

I was thinking where to reclaim storage space so we can add Fedora 30 and I checked the srpm-builds directory, which Dominik mentioned during last meeting and the total sum is: [root@copr-be results][PROD]# du -shc */*/srpm-builds 697G total and it contains very old build - so current prunerepo definitely skips it. Unless you raise your voice by end of week, I will run on Monday: rm -rf /var/lib/copr/public_html/results/*/*/srpm-builds/* The only cons I see is that links from build page to builder-live.log will be broken. ... hmm, they are already broken - likely some other bug. So I see no cons :) Miroslav

3 4

Fwd: RHEL8 and Mageia7 available in Copr
by Miroslav Suchý 11 Mar '19

11 Mar '19

FYI: I run: bash-4.4$ copr-frontend create_chroot mageia-7-i586 mageia-7-x86_64 bash-4.4$ copr-frontend create_chroot rhelbeta-8-x86_64 on copr-fe. Miroslav -------- Přeposlaná zpráva -------- Předmět: RHEL8 and Mageia7 available in Copr Datum: Mon, 11 Mar 2019 12:04:30 +0100 Od: Miroslav Suchý <msuchy(a)redhat.com> Společnost: Red Hat, Registered Address: Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic, Registered in Brno under identification number CZ27690016 Komu: Development discussions related to Fedora <devel(a)lists.fedoraproject.org> Hi, I just added those chroots to Copr: rhelbeta-8-x86_64 mageia-7-i586 mageia-7-x86_64 Please be aware that there is no available EPEL for rhelbeta-8-x86_64 yet. This chroot is intended for some initial bootstraping and testing prior RHEL 8 release and it will be removed from Copr once RHEL 8 - or to be precise CentOS 8 - will be released. Before you ask - the F30 will be added in upcoming hours. Miroslav

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

copr-devel March 2019