copr-devel January 2021

copr-devel@lists.fedorahosted.org

5 participants
5 discussions

Please raise build time limit for Chromium again
by 藍挺瑋 08 Feb '21

08 Feb '21

Since ld.gold segfault on Fedora 33 and rawhide when it uses more than one thread [1], I switched my Chromium builds to use ld.bfd a few months ago. The change increased the build time, but at least the build didn't fail in 1 hour due to ld.gold segfault. It seems that Chromium 87 increases the build time further with its Ozone platform. Now it is very hard to get successful builds of Chromium 87 on Copr. After submitting Chromium 87.0.4280.66 builds for more than 10 times, I still couldn't get successful builds for all chroots. Even if there were successful builds in some chroots, the build time was pretty close to the limit. For example, this build [2] took 29h 50m for Fedora 33, and this build [3] took 29h 52m for Fedora rawhide. Is it possible to raise the limit again? Given that Chromium keeps increasing the build time for the past 2 years, I think we should raise the limit to 48 hours this time. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1873848 [2] https://copr.fedorainfracloud.org/coprs/lantw44/chromium/build/1782394/ [3] https://copr.fedorainfracloud.org/coprs/lantw44/chromium/build/1794997/

7 11

Outage: Upgrade of Fedora Copr servers - 2021-01-21 8:30 UTC
by Pavel Raiskup 21 Jan '21

21 Jan '21

There will be an outage starting at: $ date --date '2021-01-21 8:30 UTC' The outage will last approximately 2 hours. The copr-backend storage (copr build results) will be offline for ~20 minutes (we are going to assign ipv6 there and the box needs to be rebooted). Reason for outage: We're updating copr packages to the new versions which will bring new features and bugfixes. We should do some IPv6 accessibility improvements. Affected Services: copr-frontend - https://copr.fedorainfracloud.org copr-backend - https://copr-be.cloud.fedoraproject.org/ Contact persons: @praiskup/@frostyx Infra ticket: https://pagure.io/fedora-infrastructure/issue/9588 Please join #fedora-admin in irc.freenode.net or add comments to the ticket for this outage above.

1 1

Re: %{python3} no defined in epel-7-aarch64?
by Miro Hrončok 17 Jan '21

17 Jan '21

On 04. 01. 21 18:38, José Abílio Matos wrote: > I have used copr to build the first alpha release of lyx-2.4: > > https://copr.fedorainfracloud.org/coprs/jamatos/lyx-devel/build/1858028/ > <https://copr.fedorainfracloud.org/coprs/jamatos/lyx-devel/build/1858028/> > > > For EPEL7 it build for x86_64 and it fails for aarch64, due to %{python3} not > being defined. > > > > The spec file has BR: python3-devel. > > > In the install stage I have this: > > > %py_byte_compile %{python3} %{buildroot}%{_datadir}/%{name}/lyx2lyx > > > > This fails in epel-7-aarch64... > > > Is this known? Yes. The macro was added to EPEL 7 only after aarch64 was discontinued there: https://lists.fedoraproject.org/archives/list/epel-announce@lists.fedorapro… No easy way to solve this except to stop building for aarch64 on EPEL 7. You could use the %__python3 macro instead to workaround this particular problem, but you will most likely hit another one later. I wonder whether Copr should disable EPEL 7 aarch64 chroots or at least put a big red sign next to them. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok

3 2

Disabling epel-7-aarch64 chroot in Copr
by Jakub Kadlčík 17 Jan '21

17 Jan '21

Hello, unfortunatelly, I am going to disable epel-7-aarch64 chroot in Copr. According to [1], RHEL 7 support for ARM architecture ended in Nov 30 2020. As a consequence EPEL 7 for aarch64 is discontinued as well [2]. In the meantime Koji already dropped the epel-7-aarch64 chroot [3], and we are now going to do the same. It would be nice to keep the chroot enabled even though it is not officially supported but issues like [4] started happening - a package builds in all EPEL 7 chroots except for the aarch64 one because it has outdated packages, missing macros, etc. It's better to turn it off. [1] https://access.redhat.com/support/policy/updates/errata/#Life_Cycle_Dates [2] https://fedoraproject.org/wiki/EPEL#What_packages_and_versions_are_availabl… [3] https://lists.fedoraproject.org/archives/list/epel-announce@lists.fedorapro… [4] https://lists.fedoraproject.org/archives/list/copr-devel@lists.fedorahosted… Jakub

1 0

Let's Encrypt certificate expiration notice for domain "copr-dist-git.aws.fedoraproject.org"
by Let's Encrypt Expiry Bot 07 Jan '21

07 Jan '21

Hello, Your certificate (or certificates) for the names listed below will expire in 9 days (on 17 Jan 21 17:34 +0000). Please make sure to renew your certificate before then, or visitors to your website will encounter errors. We recommend renewing certificates automatically when they have a third of their total lifetime left. For Let's Encrypt's current 90-day certificates, that means renewing 30 days before expiration. See https://letsencrypt.org/docs/integration-guide/ for details. copr-dist-git.aws.fedoraproject.org For any questions or support, please visit https://community.letsencrypt.org/. Unfortunately, we can't provide support by email. For details about when we send these emails, please visit https://letsencrypt.org/docs/expiration-emails/. In particular, note that this reminder email is still sent if you've obtained a slightly different certificate by adding or removing names. If you've replaced this certificate with a newer one that covers more or fewer names than the list above, you may be able to ignore this message. If you are receiving this email in error, unsubscribe at http://mandrillapp.com/track/unsub.php?u=30850198&id=b55e677509ce440880b149… Regards, The Let's Encrypt Team

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

copr-devel January 2021