April 2020 - copr-devel - Fedora Mailing-Lists

Let's Encrypt certificate expiration notice for domain "copr-fe-dev.aws.fedoraproject.org"

by Let's Encrypt Expiry Bot

Hello, Your certificate (or certificates) for the names listed below will expire in 19 days (on 20 May 20 14:47 +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-fe-dev.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=86fae0ad9f1d495e9339... Regards, The Let's Encrypt Team

3 years, 5 months

1
0
0 / 0

CentOS Stream builder seems broken since few days

by Jean-Marc Liger

Hi, There are many packages I can't be rebuild for CentOSStream since fews days. I've found this in some logs : annobin: handlereg.c: ICE: The size of the global_options structure has changed - please rebuild annobin annobin: handlereg.c: ICE: Please contact the annobin maintainer with details of this problem annobin: handlereg.c: Build time size: 0xef0 run time size: 0xf00 (64-bit host) I've checked that annobin-8.90 has been pushed in CentOS Stream since few days. Thanks in advance to look at, I have some cool stuff to achive. Jean-Marc

3 years, 5 months

2
3
0 / 0

unable to download devtoolset-6 on epel-7-aarch64

by Jean-Marc Liger

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/devtool... (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/devtool... (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/devtoo... (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/devtoo... (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/devtool... (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/devtoo... (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/devtoo... (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

3 years, 5 months

4
17
0 / 0

Outage: Migration of Copr servers - 2020-02-23 06:00 UTC

by Jakub Kadlcik

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

3 years, 5 months

5
11
0 / 0

EOL chroots mageia-6-x86_64 mageia-6-i586 opensuse-leap-15.0-x86_64

by Pavel Raiskup

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

3 years, 6 months

1
1
0 / 0

no rpm generated on successful builds (aarmv7 and aarch64)?

by Paul Dufresne

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-x...

3 years, 6 months

3
4
0 / 0

Request is not in JSON format, there is probably a bug in the API code.

by Paul Dufresne

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.

3 years, 6 months

2
1
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

copr-devel April 2020