December 2023 - copr-devel - Fedora Mailing-Lists

Mock Configs v39.3 released - DNF5 used for F40+ builds

by Pavel Raiskup

Hello maintainers! Let me announce a new release of Mock Core Configs v39.3, aka the configuration files for Mock, the chroot build environment manager for building RPMs. The notable change in this release is that we are switching the default package_manager from DNF4 to DNF5, according to the F40 change: https://fedoraproject.org/wiki/Changes/BuildWithDNF5 Full release notes: https://rpm-software-management.github.io/mock/Release-Notes-Configs-39.3 We plan to push this update into Fedora Copr to get some early testing next week. Then, depending on the releng team, we might push this into Koji soon. The Bodhi updates links are here: F39 https://bodhi.fedoraproject.org/updates/FEDORA-2023-0a947db1d0 F38 https://bodhi.fedoraproject.org/updates/FEDORA-2023-6ef1e12930 F37 https://bodhi.fedoraproject.org/updates/FEDORA-2023-cd9c489f40 EL9 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-c2c4082053 EL8 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-eab5217f46 Note that we **will not** push these updates into Fedora stable earlier than on Monday 2023-12-18 (but very likely we'll wait till the next year, depending on the feedback). Happy (faster) building! Pavel

3 months, 1 week

3
9
0 / 0

Re: Fedora Linux 37 is EOL

by Pavel Raiskup

Hello maintainers! Fedora 37 has been EOL for a few days now: https://fedorapeople.org/groups/schedule/f-39/f-39-all-tasks.html So I have disabled the Fedora 37 chroots, which started the standard build removal policy. For more info take a look at docs: https://docs.pagure.org/copr.copr/copr_outdated_chroots_removal_policy.html Pavel On úterý 5. prosince 2023 18:45:48 CET Tomas Hrcka wrote: > Hello all, > > Fedora Linux 37 has gone end of life for updates and support on 2023-12-05. > No more updates of any kind, including security updates or security > announcements, will be available for Fedora Linux 37 after the said > date. All the updates of Fedora Linux 37 being pushed to stable will be > stopped as well. > > Fedora Linux 38 will continue to receive updates until approximately > one month after the release of Fedora Linux 40. The maintenance > schedule of Fedora Linux releases is documented on the Fedora Project > wiki [1]. The Fedora Project wiki also contains instructions[2] on how > to upgrade from a previous release of Fedora Linux to a version > receiving updates. > > This email template is also in https://pagure.io/releng if you wish to > propose improvements or changes to it. > > > Regards, > Tomas Hrcka > Fedora Release Engineering > > [1] - > https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Sche... > [2] - https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades > [3] - https://pagure.io/releng > >

4 months, 2 weeks

1
0
0 / 0

Fedora Copr / Mock) team is moving from IRC to Matrix

by Pavel Raiskup

Hello maintainers! You might have noticed that the Fedora Matrix <-> IRC bridge has been inactive for quite some time and is unlikely to be restored soon. Monitoring both channels has become expensive for our team. I have personally noticed (as an IRC-only person until recently) that Matrix has already been more active these days, especially concerning the build system topics. Fedora Infrastructure also seems to transitioning (meetings, etc). Henceforth, you can find us on the "Fedora Build System" channel at: https://matrix.to/#/#buildsys:fedoraproject.org We'll try to monitor the old IRC room for a while, but please note that the Matrix channel is now the correct place for your questions. Pavel

4 months, 3 weeks

1
0
0 / 0

builds stucked in starting mode since 7 hours

by Jean-Marc Liger

Hi all, My builds are stucked in starting mode since 7 hours, are we back to early (and lovely) years of COPR 😉 ? Jean-Marc

4 months, 3 weeks

2
1
0 / 0

What are batches good for?

by Vít Ondruch

With MPB, trying to rebuild all Ruby related packages, I'd hoped I'll get the results much faster. The problem (to me) seems to be that packages are build in batches (as can be seen in attached screenshot). If there is some build which takes ages (this time it seems to be qt5-qtwebkit) in some batch, nothing else is processed unless that build finishes. But to me, the slow package has probably the lowest importance. I'd rather see the biggest chunk done than to endlessly wait for some package. Can this behavior be modified? E.g. the batches could overlap slightly or rebatched with low number of tasks still running. Dunno. But this makes MPB / Copr useless for this task. Vít

4 months, 3 weeks

2
2
0 / 0

What are batches good for?

by Vít Ondruch

With MPB, trying to rebuild all Ruby related packages, I'd hoped I'll get the results much faster. The problem (to me) seems to be that packages are build in batches (as can be seen in attached screenshot). If there is some build which takes ages (this time it seems to be qt5-qtwebkit) in some batch, nothing else is processed unless that build finishes. But to me, the slow package has probably the lowest importance. I'd rather see the biggest chunk done than to endlessly wait for some package. Can this behavior be modified? E.g. the batches could overlap slightly or rebatched with low number of tasks still running. Dunno. But this makes MPB / Copr useless for this task. Vít

4 months, 3 weeks

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

copr-devel December 2023