copr-devel March 2020

copr-devel@lists.fedorahosted.org

8 participants
8 discussions

unable to download devtoolset-6 on epel-7-aarch64
by Jean-Marc Liger 19 Apr '20

19 Apr '20

Hi, I'm facing the following issue : DEBUG util.py:586: [MIRROR] devtoolset-6-gcc-6.3.1-3.1.el7.aarch64.rpm: Status code: 404 forhttp://d36uatko69830t.cloudfront.net/altarch/7/sclo/aarch64/rh/devtoolse… (IP: 99.84.185.90) DEBUG util.py:586: [MIRROR] devtoolset-6-runtime-6.1-1.el7.aarch64.rpm: Status code: 404 forhttp://d36uatko69830t.cloudfront.net/altarch/7/sclo/aarch64/rh/devtoolse… (IP: 99.84.185.90) DEBUG util.py:586: [MIRROR] devtoolset-6-runtime-6.1-1.el7.aarch64.rpm: Status code: 404 forhttp://mirror.centos.org/altarch/7/sclo/aarch64/rh/devtoolset-6/devtools… (IP: 184.94.206.98) DEBUG util.py:586: [MIRROR] devtoolset-6-gcc-6.3.1-3.1.el7.aarch64.rpm: Status code: 404 forhttp://mirror.centos.org/altarch/7/sclo/aarch64/rh/devtoolset-6/devtools… (IP: 184.94.206.98) DEBUG util.py:586: [MIRROR] devtoolset-6-gcc-6.3.1-3.1.el7.aarch64.rpm: Status code: 404 forhttp://d36uatko69830t.cloudfront.net/altarch/7/sclo/aarch64/rh/devtoolse… (IP: 99.84.185.90) DEBUG util.py:586: [MIRROR] devtoolset-6-runtime-6.1-1.el7.aarch64.rpm: Status code: 404 forhttp://mirror.centos.org/altarch/7/sclo/aarch64/rh/devtoolset-6/devtools… (IP: 184.94.206.98) DEBUG util.py:586: [MIRROR] devtoolset-6-gcc-6.3.1-3.1.el7.aarch64.rpm: Status code: 404 forhttp://mirror.centos.org/altarch/7/sclo/aarch64/rh/devtoolset-6/devtools… (IP: 184.94.206.98) DEBUG util.py:586: [FAILED] devtoolset-6-gcc-6.3.1-3.1.el7.aarch64.rpm: No more mirrors to try - All mirrors were already tried without success Anyway to fix it ? Jean-Marc

4 17

Outage: Migration of Copr servers - 2020-02-23 06:00 UTC
by Jakub Kadlcik 13 Apr '20

13 Apr '20

There will be an outage starting at 2020-02-23 06:00 UTC, which will last approximately 7 hours (but can take more if something goes wrong). To convert UTC to your local time, take a look at https://fedoraproject.org/wiki/UTCHowto or run: date -d '2020-02-23 06:00 UTC' Reason for outage: Moving Copr servers from OpenStack to Amazon AWS because OpenStack is going to be shut down soon. Affected Services: copr-frontend - https://copr.fedorainfracloud.org copr-backend - https://copr-be.cloud.fedoraproject.org/ copr-distgit copr-keygen Backend repositories should remain available during the outage. Ticket Link: https://pagure.io/fedora-infrastructure/issue/8668 Contact Information: Please join #fedora-admin in irc.freenode.net or add comments to the ticket for this outage above. Jakub

5 11

EOL chroots mageia-6-x86_64 mageia-6-i586 opensuse-leap-15.0-x86_64
by Pavel Raiskup 04 Apr '20

04 Apr '20

Hi all, today I marked mageia-6-x86_64, mageia-6-i586 and opensuse-leap-15.0-x86_64 chroots as EOL in copr. Those most probably didn't build anyways due to various reasons. Be prepared to receive automatic emails that your built packages are to be deleted... https://frostyx.cz/posts/copr-removing-outdated-chroots Please move to `mageia-7` and `opensuse-leap-15.1`. The `opensuse-leap-15.2` config is already merged in mock upstream, but it is not yet release. Once we have it released, I'll enable that as well. Happy building! Pavel

1 1

no rpm generated on successful builds (aarmv7 and aarch64)?
by Paul Dufresne 02 Apr '20

02 Apr '20

Hi! I am new... maybe renew to Fedora. As I am not 'yet' a packager... I find COPR nice for developing my packaging skills. I began to use copr-cli to submit my 7kaa.spec file... Hope I will be able to use it even if I have patchs too... I have worked on upgrading the orphaned 7kaa game to latest version. While testing some architectures I don't know much, I am surprised that my build did succeed, but I see no rpm generated. See: https://copr.fedorainfracloud.org/coprs/pauld/7kaa/build/1323133/ https://copr.fedorainfracloud.org/coprs/pauld/7kaa/build/1323138/ Is there something I don't get? With more traditional architectures, the rpm was generated: Example, on: https://copr.fedorainfracloud.org/coprs/pauld/7kaa/build/1322733/ I see the rpms in: https://download.copr.fedorainfracloud.org/results/pauld/7kaa/fedora-32-x86…

3 4

Request is not in JSON format, there is probably a bug in the API code.
by Paul Dufresne 01 Apr '20

01 Apr '20

Sometime (about 1 on 2) I get this: [paul@localhost rpkg1]$ rpkg build pauld/7kaa Wrote: /tmp/rpkg/7kaa-3-3s2ohmxc/7kaa.spec setting SOURCE_DATE_EPOCH=1585440000 Écrit : /tmp/rpkg/7kaa-3-3s2ohmxc/7kaa-2.15.3-105.src.rpm Uploading package /tmp/rpkg/7kaa-3-3s2ohmxc/7kaa-2.15.3-105.src.rpm |################################| 46.9 MB 251.8 kB/s eta 0:00:00Request is not in JSON format, there is probably a bug in the API code. Failed to execute command. [paul@localhost rpkg1]$ It seems to be quite random... could redo the same command without changing anything and expect it to run fine this time.

2 1

Chromium build timeout
by 藍挺瑋 14 Mar '20

14 Mar '20

Chromium project has decided to remove a feature called 'jumbo build' from its build system: https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/DP9TQsz…. While this feature still exists in the build system of Chromium 79, it no longer builds and bugs related to jumbo build are considered WONTFIX: https://bugs.chromium.org/p/chromium/issues/detail?id=1017500. Therefore, I must disable jumbo build to get a working build of Chromium 79. Disabling the features significantly increases the number of build targets from about 25000 to 41000, causing the build time to reach the limit of Copr, which is currently 21 hours. https://copr.fedorainfracloud.org/coprs/lantw44/chromium/build/1129111/ https://copr.fedorainfracloud.org/coprs/lantw44/chromium/build/1129703/ https://copr.fedorainfracloud.org/coprs/lantw44/chromium/build/1131005/ Is it possible to raise the limit again to avoid the timeout? Otherwise, it is likely that building Chromium will become harder over time because Chromium build time keeps increasing.

3 4

rsync: link_stat "/var/lib/copr-rpmbuild/results/*" failed: No such file or directory
by Barry Scott 09 Mar '20

09 Mar '20

I'm seeing build fail because of rsync problems. https://download.copr.fedorainfracloud.org/results/barryascott/tools/epel-6… Warning: Permanently added '54.83.156.162' (ECDSA) to the list of known hosts. receiving incremental file list rsync: link_stat "/var/lib/copr-rpmbuild/results/*" failed: No such file or directory (2) sent 8 bytes received 101 bytes 218.00 bytes/sec total size is 0 speedup is 0.00 rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1659) [Receiver=3.1.3] rsync: [Receiver] write error: Broken pipe (32) Is the infra having a problem or did I miss a step I should have done? Barry

2 4

Fwd: Bulk deleting builds - RFC
by Miroslav Suchý 02 Mar '20

02 Mar '20

FYI I sent this email to several users, who has most build in Copr. Anyone else is free to comment as well. M. -------- Přeposlaná zpráva -------- Předmět: Bulk deleting builds - RFC Hi, I am writing you because you are submitting a lot of builds to Copr and I would like to get your opinion about one feature. Deleting a build. As you probably already know, when you delete a build, we have to run createrepo_c, which can take a lot of time when you run it after each deleted build. When you delete builds in webUI, backend deletes a build in one bulk and run createrepo_c in one step and runs createrepo_c only once. But... this will not work when you delete builds one by one in webUI. And the bulk delete cannot be done using copr-cli or API. So... We are thinking about two options: 1) Implement copr-cli bulk-delete-build. Technically it can be either: a) copr-cli delete-build $build-id $build-id $build-id or b) copr-cli bulk-delete-build $build-id $build-id $build-id But copr-cli delete-build $build-id copr-cli delete-build $build-id will still create two independent actions. Pros: * You have control over the delete process. You know when bulk-delete will be used. Cons: * It will not work when you do something like: for build in *; do copr-cli delete-build $build done * You have to remember yet another option/command. 2) Group build delete on frontend When backend asks frontend for pending task and the task is "delete a build", frontend will check if there are some other builds to be deleted from the same project and create bulk-delete action on the fly from those pending deletes. Pros: * No need to change API or copr-cli. * It will work even when you delete build in webUI one by one. Cons: * You have no control when batch-delete is used. Hmm, is this a problem at all? Is there any use-case when you really want to delete build one-by-one? * It is not optimal. E.g. when you run: for build in *; do copr-cli delete-build $build done and request to delete 10 000 builds, it can take e.g. 10 minutes to submit those action. And backend query frontend every minute. So backend will pick-up first 100 builds as bulk-delete. Then it will take 2 minutes to proceed. In the mean time another 2000 deleted-builds accrue. So backend will delete 2000 builds. It will take 8 minutes to proceed. And then backend pick up the remaining 7900 builds. So instead of one action, it will be splitted into several actions. Still better than 10k individual action, but worse than one action. I will appreciate your feedback. -- Miroslav Suchy, RHCA Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

copr-devel March 2020