copr-devel January 2020

copr-devel@lists.fedorahosted.org

9 participants
8 discussions

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

Packages prepared using EL8 chroot are not available for CentOS8
by Eugene Akhmetkhanov 28 Jan '20

28 Jan '20

Hi guys, I have qemu-kvm-4.2.0 packages prepared for CentOS 8 on COPR https://copr.fedorainfracloud.org/coprs/axmetishe/qemu-kvm/packages/ using git repository with spec and I'm trying to install them via repository but dnf from CentOS 8 container can't find them, but src only: dnf info qemu-kvm --showduplicates Name : qemu-kvm Epoch : 15 Version : 4.2.0 Release : 68.el8 Architecture : src Size : 59 M Source : None Repository : copr:copr.fedorainfracloud.org:axmetishe:qemu-kvm Summary : QEMU is a machine emulator and virtualizer URL : http://www.qemu.org/ License : GPLv2 and GPLv2+ and CC-BY Description : qemu-kvm is an open source virtualizer that provides hardware : emulation for the KVM hypervisor. qemu-kvm acts as a virtual : machine monitor together with the KVM kernel modules, and emulates : the hardware for a full system such as a PC and its associated : peripherals. This is wierd because a month ago I was able to bootstrap one instance via kickstart with this package installation. On the other hand the same command on Fedora 31 show me the packages: dnf info qemu-kvm --showduplicates Name : qemu-kvm Epoch : 15 Version : 4.2.0 Release : 68.el8 Architecture : x86_64 Size : 7.2 k Source : qemu-kvm-4.2.0-68.el8.src.rpm Repository : copr:copr.fedorainfracloud.org:axmetishe:qemu-kvm Summary : QEMU is a machine emulator and virtualizer URL : http://www.qemu.org/ License : GPLv2 and GPLv2+ and CC-BY Description : qemu-kvm is an open source virtualizer that provides hardware : emulation for the KVM hypervisor. qemu-kvm acts as a virtual : machine monitor together with the KVM kernel modules, and emulates : the hardware for a full system such as a PC and its associated : peripherals. Additionally I have the libssh2 package which I'm able to install in this container. I'm new with COPR and can't get the point why this happens. Would someone point me to the right direction please? Thank you in advance.

3 3

Highlights from the latest Copr release
by Tomas Hrnciar 20 Jan '20

20 Jan '20

Hello, recently (on Jan 16, 2020) a new Copr release landed production. Here is the list of visible changes: - We contributed to createrepo_c to speed up Copr for building large projects. Building large projects should be significantly faster. - Web-UI <project>/builds and <project>/packages queries were also reworked to be faster. - There is a new comand in copr-cli, "list-chroots" to list all available chroots in Copr. - To the statistics section were added new graphs to help us monitor how many actions were processed and how many of them failed. Actions are one of: generate GPG key, delete package, delete project, etc. Builds are not counted there as they have separate graph. - The frontend (web-UI, api) RAM was doubled because of the increasing load. - Builder VM images were updated to get in several bugfixes, like terminal color sequences in live logs, not enough free space under /tmp and /var/lib/copr-rpmbuild, increased number maximum opened file descriptors to 10240. - We enabled automatic createrepo_c run after build removal in very large projects. - Removing of multiple builds in @group projects was fixed. - Sometimes, after project creation, the initial createrepo run failed and it then blocked our build dispatcher process (until user manually re-created the metadata), this bug has been fixed. Happy building! Tomas

2 1

Upgrade of Copr servers - 2020-01-16 07:00 UTC (Thursday)
by Pavel Raiskup 16 Jan '20

16 Jan '20

There will be an outage, starting at: $ date --date='2020-01-16 07:00 UTC' which will last approximately 2 hours. Reason for outage ================= Upgrade of copr packages on Copr servers, to get bug-fixes and new features deployed. Affected Services ================= copr-frontend - https://copr.fedorainfracloud.org copr-backend - https://copr-be.cloud.fedoraproject.org/ Though the yum/dnf repositories (the copr-backend part which is consumed by end-user by 'dnf copr enable ...') should stay available during this outage. Ticket Link =========== https://pagure.io/fedora-infrastructure/issue/8530 Contact Information =================== @praiskup/@thrnciar Please join #fedora-admin in irc.freenode.net or add comments to the ticket for this outage above.

1 1

What does "Rebuild all" do with SCM packages?
by Miro Hrončok 15 Jan '20

15 Jan '20

Hello. I have noticed the "Rebuild all" button on packages page. Does "Rebuild all" pull from committish with SCM packages, or does it rebuilt the latest SRPM? Thanks, -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok

3 3

short outage 2020-01-11 9:00 CEST
by Pavel Raiskup 11 Jan '20

11 Jan '20

Sorry for unannounced outage, copr FE become very slow recently, I'm trying to allocate more now. It should be back quickly. https://pagure.io/fedora-infrastructure/issue/8521 Pavel

1 1

Automated builds possible?
by Richard Shaw 10 Jan '20

10 Jan '20

I just had a thought and wondered if it were possible. I have an upstream that posts alpha and beta releases to a specific URL. What I'd like copr (or something) to do is: 1. Monitor those URLs so it knows when a new alpha is pushed 2. Pull the spec file from fedora rawhide (master) 3. Run rpmdev-bumpspec -n <version> -c "Update to <version>." <spec> 4. Create a build in my COPR project using the new source. Is this possible? Thanks, Richard

4 5

Fwd: ** PROBLEM alert - copr-fe.cloud.fedoraproject.org/Disk Space /boot is WARNING **
by Miroslav Suchý 06 Jan '20

06 Jan '20

Pavel or Jakub, can you please check this up? M. -------- Přeposlaná zpráva -------- Předmět: ** PROBLEM alert - copr-fe.cloud.fedoraproject.org/Disk Space /boot is WARNING ** Datum: Mon, 06 Jan 2020 05:20:39 +0000 ***** Nagios ***** Notification Type: PROBLEM Service: Disk Space /boot Host: copr-fe.cloud.fedoraproject.org Address: copr-fe.cloud.fedoraproject.org State: WARNING Source: noc01.phx2.fedoraproject.org Date/Time: Mon Jan 6 05:20:39 UTC 2020 Additional Info: DISK WARNING - free space: / 7614 MB (19.74% inode=97%):

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

copr-devel January 2020