Re: mass rebuild status - 2022-01-25
Hello all, Fedora 36 mass rebuild is done and FTBFS tickets [0] are filed. Some of the tickets that got filed for ppc64le failures might have been fixed in the recent resubmission of the failed tasks. If you notice any of those tickets, please verify if it is fixed and if it is fixed, you can just close the ticket. Sorry for the trouble it has caused. Thanks. [0] https://bugzilla.redhat.com/show_bug.cgi?id=1992484 On Fri, Jan 28, 2022 at 9:31 AM Luna Jernberg wrote: > > Seems like rebuilds is done? got like 2000 package updates today > > On Thu, Jan 27, 2022 at 3:37 PM Michael Schwendt wrote: >> >> On Thu, 27 Jan 2022 15:06:31 +0100, František Šumšal wrote: >> >> > I've indeed noticed the other warnings. However, given this mass rebuild >> > was >> > done with a new snapshot of gcc-12, the error is probably related to that, >> > that's why I pointed out the most severe issue (since it's an error, not >> > a warning). >> >> There is nothing like that in the build.log for the other archs, so my >> original question about armv7hl remains. >> ___ >> devel mailing list -- devel@lists.fedoraproject.org >> To unsubscribe send an email to devel-le...@lists.fedoraproject.org >> Fedora Code of Conduct: >> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: >> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org >> Do not reply to spam on the list, report it: >> https://pagure.io/fedora-infrastructure > > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora 33 End Of Life
Hello all, Fedora 33 will go end of life for updates and support on 30th of November 2021. No further updates, including security updates, will be available for Fedora 33 after the said date. All the updates of Fedora 33 being pushed to stable will be stopped as well. Fedora 34 will continue to receive updates until approximately one month after the release of Fedora 36. The maintenance schedule of Fedora releases is documented on the Fedora Project wiki [0]. The fedora Project wiki also contains instructions [1] on how to upgrade from a previous release of Fedora to a version receiving updates. Regards, Mohan Boddu. [0]https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule [1]https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora 33 End Of Life
Hello all, Fedora 33 will go end of life for updates and support on 30th of November 2021. No further updates, including security updates, will be available for Fedora 33 after the said date. All the updates of Fedora 33 being pushed to stable will be stopped as well. Fedora 34 will continue to receive updates until approximately one month after the release of Fedora 36. The maintenance schedule of Fedora releases is documented on the Fedora Project wiki [0]. The fedora Project wiki also contains instructions [1] on how to upgrade from a previous release of Fedora to a version receiving updates. Regards, Mohan Boddu. [0]https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule [1]https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Re: EPEL9 Rollout Proposals
On Thu, Nov 18, 2021 at 2:32 PM Troy Dawson wrote: > > In our last EPEL Steering Committee meeting, Carl brought up a new proposal > for our epel9 / epel9-next rollout. Sometimes IRC isn't the best way to > explain things like that, it got a little confusing. Carl and I had a good > video chat to clean up confusion and talk about some pros and cons of the > various proposals. > Here are the three proposals. > > * PLAN A > Plan A is basically what we've been working towards for the past couple of > months. > - launch epel9-next now-ish (ideally aligned with c9s launch promotion) > - After RHEL9 goes GA > -- perform a mass branch and mass rebuild to populate epel9 > -- launch epel9 after RHEL9 GA is launched. > > ** Plan A Pros: > - epel9-next and epel9 are only set up once, and not changed > - ready to go now > > ** Plan A Cons: > - complexity and added work of mass branch and mass rebuild > - mass rebuild will have a moderate rate of failure due to buildroot > differences (unshipped devel packages) > - epel9 not available at rhel9 ga > - confusing messaging to packagers: > -- target epel9-next for ~6 months > -- after epel9 exists target that instead, only use epel9-next when needed > - confusing messaging to users: > -- use epel9-next now for c9s and rhel9 beta > -- use epel9-next temporarily at rhel9 launch but don’t leave it enabled > -- use epel9 primarily once it exists > I like this plan as it is my brain child, it is what we have been communicating and planning, it doesn't really diverge from what EPEL has been. But... (see my opinion on Plan B) > > * PLAN B > - epel9-next stays the way it is currently setup. > - Setup epel9 using RHEL9 Beta for the buildroot. > -- Pull in any errata as it comes. > -- Use the repos you would for RHEL9 GA: AppStream, BaseOS, CRB > - Launch epel9 and epel9-next together (In 1-2 weeks). > - When RHEL9 GA is released, switch epel9 buildroot from RHEL9 Beta to RHEL9 > GA > > ** Plan B Pros: > - simple messaging to packagers: > -- epel9 is the primary target, use epel9-next only when needed (same as > epel8-next) > - simple messaging to users: > -- use epel9 everywhere (epel-next-release is a recommends on c9s) > - no mass branching > - no mass rebuild Maybe we can run a mass rebuild to capture all the differences between rhel9 beta and rhel9 ga. That would solve one of the con's below. > - No confusion from using the full CentOS Stream buildroot > -- epel9 buildroot will only have AppStream, BaseOS and CRB > > ** Plan B Cons: > - potential for large divergence between rhel9 beta and ga > - changing our messaging right before the launch > I didn't see one question answered here, the maintainer has to request both epel9 and epel9-next branch or up until rhel9 ga if a maintainer requests epel9 branch they will also get epel9-next branch (like it was set up for epel8-playground). If we run a mass rebuild, then it wont be much different from that of Plan A, except there might be a few (or more, depending on delta) packages that will work on rhel9 ga. So, I am not against this idea as well. One thing I would like to mention here is, even if we can setup this way since rhel 9 beta is out, we cannot do that same thing during rhel10 time as we might setup epel10-next way in advance before the rhel10 beta. We cannot keep this plan consistent going further. > > * PLAN C > - epel9-next stays the way it is currently setup. > - setup up epel9 using c9s for the buildroot > -- Use the repos you would for RHEL9: AppStream, BaseOS, CRB > - freeze epel9 buildroot before c9s switches to 9.1 content > - launch epel9 and epel9-next together (1-2 weeks) > - switch epel9 buildroot from frozen c9s to rhel9 ga later > > ** Plan C Pros: > - simple messaging to packagers: > -- epel9 is the primary target, use epel9-next only when needed (same as > epel8-next) > - simple messaging to users: > -- use epel9 everywhere (epel-next-release is a recommends on c9s) > - no mass branching > - no mass rebuild > - No confusion from using the full CentOS Stream buildroot > -- epel9 buildroot will only have AppStream, BaseOS and CRB > > ** Plan C Cons: > - potential infrastructure complexity of freezing the epel9 buildroot > - changing our messaging right before the launch > I can see how its advantageous, but I dont like this plan, since there are some uncertainties, we dont really know when c9s will start pointing to rhel 9.1, we can only guestimate currently. Even if we know for sure, we have to ask centos stream folks to freeze their work until we sort out things on our side. And what if the package versions changed in rhel9 ga, because they found an issue in that build. > > Please let us know what you think. > If we do choose to go with Plan B or C we will need to make the decision > fairly quickly. I am okay with either plan A or plan B. > > Troy > > ___ > epel-devel mailing list -- epel-devel@lists.fedoraproject.org > To unsubscribe send
[EPEL-devel] Re: EPEL9 Rollout Proposals
On Thu, Nov 18, 2021 at 3:12 PM Kevin Fenzi wrote: > > ..snip... > > > > ** Plan A Cons: > > - complexity and added work of mass branch and mass rebuild > > - mass rebuild will have a moderate rate of failure due to buildroot > > differences (unshipped devel packages) > > So, I had this question: How do we handle this mass rebuild? > we branch everything in epel9-next into epel9 and build it... do we > bypass bodhi for the intial population of packages? Yes, at the time of rhel 9 ga, the plan is to create an epel9 branch from epel9-next branch (that are active) and rebuild them against rhel 9 ga buildroot. We could bypass bodhi or we can create a single update in bodhi, all though I like the testing before dumping, in this case I prefer bypassing bodhi just because we dont want to hold off all the builds if there is an issue with one build. > > ...snip... ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora 35 Final Freeze
Hi all, Today, Oct 5th 2021, is an important day on the Fedora 35 schedule [1], with significant cut-offs. Today we have the Final Freeze [2] which starts at 14:00 UTC. This means that only packages which fix accepted blocker or freeze exception bugs [3][4][5] will be marked as 'stable' and included in the Final composes. Other builds will remain in updates-testing until the Final release is approved, at which point the Final freeze is lifted and packages can move to the 'updates' repository, pending updates will be pushed before final release as zero day updates. [1] https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html [2] https://fedoraproject.org/wiki/Milestone_freezes [3] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process [4] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process [5] https://qa.fedoraproject.org/blockerbugs/milestone/34/final/buglist Regards, Mohan Boddu Release Engineering ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Test-Announce] Fedora 35 Final Freeze
Hi all, Today, Oct 5th 2021, is an important day on the Fedora 35 schedule [1], with significant cut-offs. Today we have the Final Freeze [2] which starts at 14:00 UTC. This means that only packages which fix accepted blocker or freeze exception bugs [3][4][5] will be marked as 'stable' and included in the Final composes. Other builds will remain in updates-testing until the Final release is approved, at which point the Final freeze is lifted and packages can move to the 'updates' repository, pending updates will be pushed before final release as zero day updates. [1] https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html [2] https://fedoraproject.org/wiki/Milestone_freezes [3] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process [4] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process [5] https://qa.fedoraproject.org/blockerbugs/milestone/34/final/buglist Regards, Mohan Boddu Release Engineering ___ test-announce mailing list -- test-annou...@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora Linux 35 Beta Release Announcement
Fedora Linux 35 Beta Released -- The Fedora Project is pleased to announce the immediate availability of Fedora 35 Beta, the next step towards our planned Fedora 35 release at the end of October. Download the prerelease from our Get Fedora site: * Get Fedora 35 Beta Workstation: https://getfedora.org/workstation/download/ * Get Fedora 35 Beta Server: https://getfedora.org/server/download/ * Get Fedora 35 IoT: https://getfedora.org/iot/download/ Or, check out one of our popular variants, including KDE Plasma, Xfce, and other desktop environments, as well as images for ARM devices: * Get Fedora 35 Beta Spins: https://spins.fedoraproject.org/prerelease * Get Fedora 35 Beta Labs: https://labs.fedoraproject.org/prerelease * Get Fedora 35 Beta ARM: https://arm.fedoraproject.org/prerelease ## Beta Release Highlights * Fedora 35 Workstation Beta includes GNOME 41 * Fedora Kinoite—a KDE Plasma environment based on rpm-ostree technology * Fedora Linux 35 builds on the switch to PipeWire for managing audio by introducing WirePlumber as the default session manager. * Python 3.10, Perl 5.34, PHP 8.0 updated versions. * And more ... For more details about the release, read the full announcement at * https://fedoramagazine.org/announcing-fedora-35-beta/ or look for the prerelease pages in the download sections at * https://getfedora.org/ Since this is a Beta release, we expect that you may encounter bugs or missing features. To report issues encountered during testing, contact the Fedora QA team via the t...@lists.fedoraproject.org mailing list or in #fedora-qa on Libera Chat. Regards, Mohan Boddu Fedora Release Engineering. ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Test-Announce] Fedora Linux 35 Beta Release Announcement
Fedora Linux 35 Beta Released -- The Fedora Project is pleased to announce the immediate availability of Fedora 35 Beta, the next step towards our planned Fedora 35 release at the end of October. Download the prerelease from our Get Fedora site: * Get Fedora 35 Beta Workstation: https://getfedora.org/workstation/download/ * Get Fedora 35 Beta Server: https://getfedora.org/server/download/ * Get Fedora 35 IoT: https://getfedora.org/iot/download/ Or, check out one of our popular variants, including KDE Plasma, Xfce, and other desktop environments, as well as images for ARM devices: * Get Fedora 35 Beta Spins: https://spins.fedoraproject.org/prerelease * Get Fedora 35 Beta Labs: https://labs.fedoraproject.org/prerelease * Get Fedora 35 Beta ARM: https://arm.fedoraproject.org/prerelease ## Beta Release Highlights * Fedora 35 Workstation Beta includes GNOME 41 * Fedora Kinoite—a KDE Plasma environment based on rpm-ostree technology * Fedora Linux 35 builds on the switch to PipeWire for managing audio by introducing WirePlumber as the default session manager. * Python 3.10, Perl 5.34, PHP 8.0 updated versions. * And more ... For more details about the release, read the full announcement at * https://fedoramagazine.org/announcing-fedora-35-beta/ or look for the prerelease pages in the download sections at * https://getfedora.org/ Since this is a Beta release, we expect that you may encounter bugs or missing features. To report issues encountered during testing, contact the Fedora QA team via the t...@lists.fedoraproject.org mailing list or in #fedora-qa on Libera Chat. Regards, Mohan Boddu Fedora Release Engineering. ___ test-announce mailing list -- test-annou...@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora 35 Mass Branching
Hi All, Fedora 35 has now been branched, please be sure to do a git pull --rebase to pick up the new branch, as an additional reminder rawhide/f36 has been completely isolated from previous releases, so this means that anything you do for f35 you also have to do in the rawhide branch and do a build there. There will be a Fedora 35 compose and it'll appear in http://dl.fedoraproject.org/pub/fedora/linux/development/35/ once complete. Please be sure to check it out. Bodhi is currently not active for Fedora 35, it will be enabled in a couple of weeks when we hit Beta change freeze point in the Fedora 35 schedule[1]. Two things to remember: 1. The modules will be built for a new platform:f36 2. The signing of rpms is not done yet with the new f36 key. 3. F35/branched release is frozen right now until we get a successful compose, expect that your f35 builds won't be available immediately. Thanks for understanding. [1] https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora 35 Mass Branching
Hi All, Fedora 35 has now been branched, please be sure to do a git pull --rebase to pick up the new branch, as an additional reminder rawhide/f36 has been completely isolated from previous releases, so this means that anything you do for f35 you also have to do in the rawhide branch and do a build there. There will be a Fedora 35 compose and it'll appear in http://dl.fedoraproject.org/pub/fedora/linux/development/35/ once complete. Please be sure to check it out. Bodhi is currently not active for Fedora 35, it will be enabled in a couple of weeks when we hit Beta change freeze point in the Fedora 35 schedule[1]. Two things to remember: 1. The modules will be built for a new platform:f36 2. The signing of rpms is not done yet with the new f36 key. 3. F35/branched release is frozen right now until we get a successful compose, expect that your f35 builds won't be available immediately. Thanks for understanding. [1] https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Re: Planning for EPEL9
On Thu, Jul 8, 2021 at 9:58 AM Neal Gompa wrote: > > On Thu, Jul 8, 2021 at 9:39 AM Kevin Fenzi wrote: > > > > On Wed, Jul 07, 2021 at 08:32:27PM -0400, Neal Gompa wrote: > > > > > > This is very exciting! > > > > > > However, question here: At least for the bootstrap for RHEL 9 GA, > > > couldn't we use the EPEL9 next buildroot to rebuild everything once > > > instead of rebuilding 5 times? We can then remove the EPEL9 next > > > buildroot from the EPEL9 buildroot so that state doesn't persist after > > > everything is done. This also makes it so we can ignore the > > > "noautobuild" file the one time that all the content needs to be > > > properly seeded in EPEL9. > > > > But at the time of RHEL9.0 GA, cs9 may well have already moved on to > > 9.1... so that might result in stuff that doesn't work/install/depsolve > > with 9.0? Or am I missing something there... > > > > Based on what goes on now for EPEL8 and EPEL8 next, I think the > likelihood of that being a problem is fairly low. Ones where this is a > problem can be individually handled after the reset, and we'd waste > far less build resources in doing so. I still dont understand the advantages of it, we will be running the mass rebuild after RHEL 9.0 GA, so it wont be saving time (other than the time needed to setup the epel9 buildroot from rhel9 content). We will rebuild everything, so it wont be saving any builder/storage resources. I still prefer epel9 is built from rhel9 rather than CS after rhel goes GA as it always has been. > > > > -- > 真実はいつも一つ！/ Always, there's only one truth! > ___ > epel-devel mailing list -- epel-devel@lists.fedoraproject.org > To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Planning for EPEL9
Hello all, While we are already working on epel9-next enablement, there was a discussion about how to handle epel9 when rhel9 goes GA. It is safe to assume that a lot of the builds that are already in epel9-next at that point of time should work on rhel9. There were couple of ideas thrown around from doing nothing to tagging epel9-next builds to epel9, but I think the best way to solve this is, mass branching the packages that have epel9-next branch and create epel9 branch from it and then running a mass rebuild without any changes to spec files. As epel9-next builds will already have a .el9.next dist tag, we can simply rebuild whatever there is in epel9 branch (after branching epel9 branch from epel9-next branch). Since the builds are done in alphanumerical order and does not preserve build order, we might have to run this mass rebuild a few times (thinking of 5 times) on the failed builds to get most of the builds. This doesn't involve changing the spec files, just resubmitting the failed tasks. Also, people who wish to opt out of this mass rebuild can add 'noautobuild' file to the epel9-next branch beforehand, this however does not stop from creating the epel9 branch, just the package won't be included in the rebuild. The idea here is, if the maintainer wishes to support epel9-next, their final goal is to maintain the package for epel9. So, we give them a branch, but will not rebuild their package as they might have wanted to build their packages in the correct build order (cough cough KDE :D). This gives us a working epel9 with a bunch of working builds in a few days after rhel9 GA and also we can create ftbfs bugs for those that failed in the mass rebuild which will help maintainers to identify and fix the issues. Couple of questions that need to be answered here: 1. Is 5 times of rebuilds good enough or do we need more? 2. Do the mass rebuild builds have to go through bodhi or can we just directly tag them for stable compose? Any suggestions appreciated. Thanks. ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: [ELN] Rebuild ordering and side-tag support
On Mon, Jun 28, 2021 at 3:33 PM Dan Horák wrote: > > On Mon, 28 Jun 2021 11:55:21 -0400 > Stephen Gallagher wrote: > > > Summary: I think we can fix the ELN side-tag rebuild problems and make > > the composes more reliable if we change the mechanism for kicking off > > rebuilds. I'm soliciting feedback to help identify potential issues > > with this proposed approach. > > have you considered re-using koji-shadow? It might already know > everything you need ... But it requires another koji instance that needs maintenance. > > > Dan > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: GNOME on Wayland does not work on latest Rawhide
On Mon, Jun 28, 2021 at 3:20 PM Florian Weimer wrote: > > * Mohan Boddu: > > > Not sure if its related, but bolt is also having an issue: > > What's your glibc version? glibc-2.33.9000-25.fc35 is the first build > with the (then downstream-only) fix. I should have mentioned this earlier, but I updated to glibc-2.33.9000-25.fc35 > > boltd issues have been reported as well, but I'm not sure if we have > verified that they went away with the fix for the larger issue. > > Thanks, > Florian > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: GNOME on Wayland does not work on latest Rawhide
Not sure if its related, but bolt is also having an issue: Stack trace of thread 10114: #0 0x7fbde5b3993d n/a (libc.so.6 + 0x17c93d) #1 0x7fbde5ebc688 g_strdup (libglib-2.0.so.0 + 0x72688) #2 0x7fbde5c4e685 value_collect_string (libgobject-2.0.so.0 + 0x33685) #3 0x7fbde5c3fa9c g_object_set_valist (libgobject-2.0.so.0 + 0x24a9c) #4 0x7fbde5c3fd74 g_object_set (libgobject-2.0.so.0 + 0x24d74) #5 0x5587d18a6c49 handle_udev_device_event (boltd + 0x12c49) #6 0x5587d18addcb bolt_manager_initialize (boltd + 0x19dcb) #7 0x7fbde5ceebfa g_initable_new_valist (libgio-2.0.so.0 + 0x78bfa) #8 0x7fbde5ceecad g_initable_new (libgio-2.0.so.0 + 0x78cad) #9 0x5587d18a29ec on_bus_acquired (boltd + 0xe9ec) #10 0x7fbde5d86196 connection_get_cb.lto_priv.0 (libgio-2.0.so.0 + 0x110196) #11 0x7fbde5d24a7a g_task_return_now (libgio-2.0.so.0 + 0xaea7a) #12 0x7fbde5d24c7b g_task_return (libgio-2.0.so.0 + 0xaec7b) #13 0x7fbde5d837c2 bus_get_async_initable_cb (libgio-2.0.so.0 + 0x10d7c2) #14 0x7fbde5d24a7a g_task_return_now (libgio-2.0.so.0 + 0xaea7a) #15 0x7fbde5d24abd complete_in_idle_cb (libgio-2.0.so.0 + 0xaeabd) #16 0x7fbde5e9b1cb g_idle_dispatch (libglib-2.0.so.0 + 0x511cb) #17 0x7fbde5e9ef4f g_main_context_dispatch (libglib-2.0.so.0 + 0x54f4f) #18 0x7fbde5ef3628 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0xa9628) #19 0x7fbde5e9e513 g_main_loop_run (libglib-2.0.so.0 + 0x54513) #20 0x5587d18a1aa4 main (boltd + 0xdaa4) #21 0x7fbde59e87e0 n/a (libc.so.6 + 0x2b7e0) #22 0x7fbde59e888c n/a (libc.so.6 + 0x2b88c) #23 0x5587d18a1dae _start (boltd + 0xddae) Stack trace of thread 10118: #0 0x7fbde5ac00af n/a (libc.so.6 + 0x1030af) #1 0x7fbde5ef35bc g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0xa95bc) #2 0x7fbde5e9c683 g_main_context_iteration (libglib-2.0.so.0 + 0x52683) #3 0x7fbde5e9c6d1 glib_worker_main (libglib-2.0.so.0 + 0x526d1) #4 0x7fbde5ecd6a2 g_thread_proxy (libglib-2.0.so.0 + 0x836a2) #5 0x7fbde5a49207 n/a (libc.so.6 + 0x8c207) #6 0x7fbde5acbdd4 n/a (libc.so.6 + 0x10edd4) Stack trace of thread 10119: #0 0x7fbde5ac574d n/a (libc.so.6 + 0x10874d) #1 0x7fbde5eeccb3 g_cond_wait (libglib-2.0.so.0 + 0xa2cb3) #2 0x7fbde5e6f47b g_async_queue_pop_intern_unlocked (libglib-2.0.so.0 + 0x2547b) #3 0x7fbde5ecf5ea g_thread_pool_spawn_thread (libglib-2.0.so.0 + 0x855ea) #4 0x7fbde5ecd6a2 g_thread_proxy (libglib-2.0.so.0 + 0x836a2) #5 0x7fbde5a49207 n/a (libc.so.6 + 0x8c207) #6 0x7fbde5acbdd4 n/a (libc.so.6 + 0x10edd4) Stack trace of thread 10120: #0 0x7fbde5ac574d n/a (libc.so.6 + 0x10874d) #1 0x7fbde5eed2bc g_cond_wait_until (libglib-2.0.so.0 + 0xa32bc) #2 0x7fbde5e6f461 g_async_queue_pop_intern_unlocked (libglib-2.0.so.0 + 0x25461) #3 0x7fbde5e6f5e6 g_async_queue_timeout_pop (libglib-2.0.so.0 + 0x255e6) #4 0x7fbde5ed0639 g_thread_pool_thread_proxy.lto_priv.0 (libglib-2.0.so.0 + 0x86639) #5 0x7fbde5ecd6a2 g_thread_proxy (libglib-2.0.so.0 + 0x836a2) #6 0x7fbde5a49207 n/a (libc.so.6 + 0x8c207) #7 0x7fbde5acbdd4 n/a (libc.so.6 + 0x10edd4) Stack trace of thread 10121: #0 0x7fbde5ac00af n/a (libc.so.6 + 0x1030af) #1 0x7fbde5ef35bc g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0xa95bc) #2 0x7fbde5e9e513 g_main_loop_run (libglib-2.0.so.0 + 0x54513) #3 0x7fbde5d86d5a gdbus_shared_thread_func.lto_priv.0 (libgio-2.0.so.0 + 0x110d5a) #4 0x7fbde5ecd6a2 g_thread_proxy (libglib-2.0.so.0 + 0x836a2) #5 0x7fbde5a49207 n/a (libc.so.6 + 0x8c207) #6 0x7fbde5acbdd4 n/a (libc.so.6 + 0x10edd4) On Thu, Jun 24, 2021 at 5:49 AM Florian Weimer wrote: > > * Florian Weimer: > > > We could use some basic GNOME SHell debugging help here. Ideally, we'd > > like to run GNOME Shell in such a way that it does not perform X > > fallback and does not re-exec itself, and uses a specified VT (so that > > we can launch it over an SSH session). > > > > (This is about bug 1974970.) > > I got
Re: RFC: Banning bots from submitting automated koji builds
On Sun, Jun 20, 2021 at 7:09 AM Peter Robinson wrote: > > > With things like [0] (TL;DR: bots submitting broken builds to rawhide) > > becoming a more regular occurrence, I propose that we extend the > > existing Updates Policy [1] to make it explicit that bots are not > > allowed to submit builds / updates - even to rawhide - unattended: > > "Rawhide is not your CI environment." > > I don't think that's good for either the packages that are using bots > or for Fedora as a whole. > > While the bots certainly don't always get it right nor do the humans > and I would garner that there's a lot more problems introduced in this > way by humans, over the years I've spent considerable time fixing > issues like this introduced by humans. Do we ban humans too? Do we ban > RHBZ bots as well because they don't always get it right either? > Ultimately automation is hard, but ultimately I feel it generally gets > it wrong no less than humans do, and generally in a consistent way at > least. I definitely agree here, we want automation to evolve rather than simply banning it. I understand the problem with automation, but anyone can make mistakes. We should definitely have a contact person responsible for the bot. And we can just ban the bot if it does something unusual. > > > Peter > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Fedora Linux 32 End Of Life
On Tue, May 25, 2021 at 5:12 PM Dominik 'Rathann' Mierzejewski wrote: > > On Tuesday, 25 May 2021 at 23:06, Mohan Boddu wrote: > > Hello all, > > > > As of the 25th of May 2021, Fedora Linux 32 has reached its end of > > life for updates and support. No further updates, including security > > updates, will be available for Fedora 32. All the updates that are > > currently in testing won't get pushed to stable. > > What about updates that were in "submitted to stable" state? Don't they > deserve the final push? I'm talking about this one in particular: > https://bodhi.fedoraproject.org/updates/FEDORA-2021-5f3479aaf3 > It waited to be pushed to stable for 17 hours only to be made obsolete > at the last step. It doesn't seem fair to me. I understand the problem here, but we push updates once a day and today's push is already finished. The problem with running another push just before starting the EOL process is that update pushes take some time and we cannot start the EOL process until they are finished and the push might fail which delays the EOL process even further. EOL process takes some time and we cannot delay it to the next day and also even when going through the EOL process, updates can go to stable and we cannot simply keep pushing them. Sorry for the trouble this has caused, but I am not sure if there is an easy way to fix this issue. > > Regards, > Dominik > -- > Fedora https://getfedora.org | RPM Fusion http://rpmfusion.org > There should be a science of discontent. People need hard times and > oppression to develop psychic muscles. > -- from "Collected Sayings of Muad'Dib" by the Princess Irulan > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora Linux 32 End Of Life
Hello all, As of the 25th of May 2021, Fedora Linux 32 has reached its end of life for updates and support. No further updates, including security updates, will be available for Fedora 32. All the updates that are currently in testing won't get pushed to stable. Fedora 33 will continue to receive updates until approximately one month after the release of Fedora 35. The maintenance schedule of Fedora releases is documented on the Fedora Project wiki [0]. The Fedora Project wiki also contains instructions [1] on how to upgrade from a previous release of Fedora to a version receiving updates. Mohan Boddu. [0] https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule [1] https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/ ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora Linux 32 End Of Life
Hello all, As of the 25th of May 2021, Fedora Linux 32 has reached its end of life for updates and support. No further updates, including security updates, will be available for Fedora 32. All the updates that are currently in testing won't get pushed to stable. Fedora 33 will continue to receive updates until approximately one month after the release of Fedora 35. The maintenance schedule of Fedora releases is documented on the Fedora Project wiki [0]. The Fedora Project wiki also contains instructions [1] on how to upgrade from a previous release of Fedora to a version receiving updates. Mohan Boddu. [0] https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule [1] https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora 34 Final Freeze
Hi all, Tomorrow, April 6th 2020, is an important day on the Fedora 34 schedule [1], with significant cut-offs. Tomorrow we have the Final Freeze [2] which starts at 14:00 UTC. This means that only packages which fix accepted blocker or freeze exception bugs [3][4][5] will be marked as 'stable' and included in the Final composes. Other builds will remain in updates-testing until the Final release is approved, at which point the Final freeze is lifted and packages can move to the 'updates' repository, pending updates will be pushed before final release as zero day updates. [1] https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html [2] https://fedoraproject.org/wiki/Milestone_freezes [3] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process [4] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process [5] https://qa.fedoraproject.org/blockerbugs/milestone/34/final/buglist Regards, Mohan Boddu Release Engineering ___ devel-announce mailing list -- devel-annou...@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora 34 Final Freeze
Hi all, Tomorrow, April 6th 2020, is an important day on the Fedora 34 schedule [1], with significant cut-offs. Tomorrow we have the Final Freeze [2] which starts at 14:00 UTC. This means that only packages which fix accepted blocker or freeze exception bugs [3][4][5] will be marked as 'stable' and included in the Final composes. Other builds will remain in updates-testing until the Final release is approved, at which point the Final freeze is lifted and packages can move to the 'updates' repository, pending updates will be pushed before final release as zero day updates. [1] https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html [2] https://fedoraproject.org/wiki/Milestone_freezes [3] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process [4] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process [5] https://qa.fedoraproject.org/blockerbugs/milestone/34/final/buglist Regards, Mohan Boddu Release Engineering ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora Linux 34 Beta Release Announcement
Fedora Linux 34 Beta Released -- The Fedora Project is pleased to announce the immediate availability of Fedora 34 Beta, the next step towards our planned Fedora 34 release at the end of April. Download the prerelease from our Get Fedora site: * Get Fedora 34 Beta Workstation: https://getfedora.org/workstation/download/ * Get Fedora 34 Beta Server: https://getfedora.org/server/download/ * Get Fedora 34 IoT: https://getfedora.org/iot/download/ Or, check out one of our popular variants, including KDE Plasma, Xfce, and other desktop environments, as well as images for ARM devices: * Get Fedora 34 Beta Spins: https://spins.fedoraproject.org/prerelease * Get Fedora 34 Beta Labs: https://labs.fedoraproject.org/prerelease * Get Fedora 34 Beta ARM: https://arm.fedoraproject.org/prerelease ## Beta Release Highlights * BTRFS transparent compression * Replacing PulseAudio with PipeWire * Fedora 34 Workstation Beta includes GNOME 40 * A new i3 spin * And more ... For more details about the release, read the full announcement at * https://fedoramagazine.org/announcing-the-release-of-fedora-34-beta/ or look for the prerelease pages in the download sections at * https://getfedora.org/ Since this is a Beta release, we expect that you may encounter bugs or missing features. To report issues encountered during testing, contact the Fedora QA team via the t...@lists.fedoraproject.org mailing list or in #fedora-qa on Freenode. Regards, Mohan Boddu Fedora Release Engineering. ___ devel-announce mailing list -- devel-annou...@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora Linux 34 Beta Release Announcement
Fedora Linux 34 Beta Released -- The Fedora Project is pleased to announce the immediate availability of Fedora 34 Beta, the next step towards our planned Fedora 34 release at the end of April. Download the prerelease from our Get Fedora site: * Get Fedora 34 Beta Workstation: https://getfedora.org/workstation/download/ * Get Fedora 34 Beta Server: https://getfedora.org/server/download/ * Get Fedora 34 IoT: https://getfedora.org/iot/download/ Or, check out one of our popular variants, including KDE Plasma, Xfce, and other desktop environments, as well as images for ARM devices: * Get Fedora 34 Beta Spins: https://spins.fedoraproject.org/prerelease * Get Fedora 34 Beta Labs: https://labs.fedoraproject.org/prerelease * Get Fedora 34 Beta ARM: https://arm.fedoraproject.org/prerelease ## Beta Release Highlights * BTRFS transparent compression * Replacing PulseAudio with PipeWire * Fedora 34 Workstation Beta includes GNOME 40 * A new i3 spin * And more ... For more details about the release, read the full announcement at * https://fedoramagazine.org/announcing-the-release-of-fedora-34-beta/ or look for the prerelease pages in the download sections at * https://getfedora.org/ Since this is a Beta release, we expect that you may encounter bugs or missing features. To report issues encountered during testing, contact the Fedora QA team via the t...@lists.fedoraproject.org mailing list or in #fedora-qa on Freenode. Regards, Mohan Boddu Fedora Release Engineering. ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora 34 Bodhi updates-testing Activation and Beta Freeze
Hi all, Today's an important day on the Fedora 34 schedule[1], with several significant cut-offs. First of all today is the Bodhi updates-testing activation point [2]. That means that from now all Fedora 34 packages must be submitted to updates-testing and pass the relevant requirements[3] before they will be marked as 'stable' and moved to the fedora repository. Today is also the Beta freeze[4]. This means that only packages which fix accepted blocker or freeze exception bugs[5][6] will be marked as 'stable' and included in the Beta composes. Other builds will remain in updates-testing until the Beta release is approved, at which point the Beta freeze is lifted and packages can move to 'stable' as usual until the Final freeze. Today is also the Software String freeze[7], which means that strings marked for translation in Fedora-translated projects should not now be changed for Fedora 34. Finally, today is the 'completion deadline' Change Checkpoint[8], meaning that Fedora 34 Changes must now be 'feature complete or close enough to completion that a majority of its functionality can be tested'. All tracking bugs should be on ON_QA state or later to reflect this. Regards Mohan Boddu [1] https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html [2] https://fedoraproject.org/wiki/Updates_Policy#Bodhi_enabling [3] https://fedoraproject.org/wiki/Updates_Policy#Branched_release [4] https://fedoraproject.org/wiki/Milestone_freezes [5] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process [6] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process [7] https://fedoraproject.org/wiki/ReleaseEngineering/StringFreezePolicy [8] https://fedoraproject.org/wiki/Changes/Policy ___ devel-announce mailing list -- devel-annou...@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora 34 Bodhi updates-testing Activation and Beta Freeze
Hi all, Today's an important day on the Fedora 34 schedule[1], with several significant cut-offs. First of all today is the Bodhi updates-testing activation point [2]. That means that from now all Fedora 34 packages must be submitted to updates-testing and pass the relevant requirements[3] before they will be marked as 'stable' and moved to the fedora repository. Today is also the Beta freeze[4]. This means that only packages which fix accepted blocker or freeze exception bugs[5][6] will be marked as 'stable' and included in the Beta composes. Other builds will remain in updates-testing until the Beta release is approved, at which point the Beta freeze is lifted and packages can move to 'stable' as usual until the Final freeze. Today is also the Software String freeze[7], which means that strings marked for translation in Fedora-translated projects should not now be changed for Fedora 34. Finally, today is the 'completion deadline' Change Checkpoint[8], meaning that Fedora 34 Changes must now be 'feature complete or close enough to completion that a majority of its functionality can be tested'. All tracking bugs should be on ON_QA state or later to reflect this. Regards Mohan Boddu [1] https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html [2] https://fedoraproject.org/wiki/Updates_Policy#Bodhi_enabling [3] https://fedoraproject.org/wiki/Updates_Policy#Branched_release [4] https://fedoraproject.org/wiki/Milestone_freezes [5] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process [6] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process [7] https://fedoraproject.org/wiki/ReleaseEngineering/StringFreezePolicy [8] https://fedoraproject.org/wiki/Changes/Policy ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Fedora 34 Mass Branching
Hi All, Fedora 34 has now been branched, please be sure to do a git pull --rebase to pick up the new branch, as an additional reminder rawhide/f35 has been completely isolated from previous releases, so this means that anything you do for f34 you also have to do in the rawhide branch and do a build there. There will be a Fedora 34 compose and it'll appear in http://dl.fedoraproject.org/pub/fedora/linux/development/34/ once complete. Please be sure to check it out. Bodhi is currently not active for Fedora 34, it will be enabled in a couple of weeks when we hit Beta change freeze point in the Fedora 34 schedule[1]. Two things to remember: 1. The modules will be built for a new platform:f35 2. The signing of rpms is not done yet with the new f35 key. 3. F34/branched release is frozen right now until we get a successful compose, expect that your f34 builds won't be available immediately. Thanks for understanding. [1] https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html On Mon, Feb 8, 2021 at 11:39 AM Mohan Boddu wrote: > > Hello All, > > Fedora 34 will be branched from rawhide on Feb 09th 2021 as per the > Fedora 34 schedule[1]. The process takes about a day and everything > should be ready by Feb 10th 2021. You can still be able to build > packages normally until then, but after the mass branching, rawhide > and F34 will be separated. > > We will send another email once the branching is done. > > Thanks, > Mohan Boddu. > > [1] https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Re: Fedora 34 Mass Branching
On Tue, Feb 9, 2021 at 6:30 PM Kevin Fenzi wrote: > > On Tue, Feb 09, 2021 at 06:19:41PM -0500, Mohan Boddu wrote: > > On Mon, Feb 8, 2021 at 7:18 PM Petr Menšík wrote: > > > > > > Hi, > > > > > > I were unable to find time in the schedule, at which the new F35 GPG key > > > would be activated to sign new builds. > > > > It will be done a week before mass branching, but we are thinking of > > doing it a bit earlier to give more time. > > I think we should make the f36 key right now and add it to fedora-repos > and push it out to all branches. Then, when we get to f35 branching, we > make the f37 key (ie, we stay 6 months ahead). This works except for once a blue moon kinda corner case like for example F35 key, it is sha 256 whereas the other older keys are sha1 keys. So, if we go with creating a release key 6 months in advance we might have to stick with old versioned keys. Again, this doesn't happen often but I just wanted to put it out there. > > This way everyone has the new key already and there's no scrambling. > > (or this week, doesn't have to be today, just soon) > > kevin > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 34 Mass Branching
On Tue, Feb 9, 2021 at 6:18 PM Fabio Valentini wrote: > > On Wed, Feb 10, 2021 at 12:11 AM Mohan Boddu wrote: > > > > Hi All, > > > > Fedora 34 has now been branched, please be sure to do a git pull > > --rebase to pick up the new branch, as an additional reminder > > rawhide/f35 has been completely isolated from previous releases, so > > this means that anything you do for f34 you also have to do in the > > rawhide branch and do a build there. There will be a Fedora 34 compose > > and it'll appear in > > http://dl.fedoraproject.org/pub/fedora/linux/development/34/ once > > complete. Please be sure to check it out. Bodhi is currently not > > active for Fedora 34, it will be enabled in a couple of weeks when we > > hit Beta change freeze point in the Fedora 34 schedule[1]. > > You mean updates do not yet go through updates-testing? > Or is bodhi now no longer active for branched releases pre-beta? With gating, this became a complex question, basically it meant automatic updates are created in bodhi for f34 but after the activation date, maintainers has to manually create the updates as they do for normal releases. > > Fabio > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 34 Mass Branching
On Mon, Feb 8, 2021 at 7:18 PM Petr Menšík wrote: > > Hi, > > I were unable to find time in the schedule, at which the new F35 GPG key > would be activated to sign new builds. It will be done a week before mass branching, but we are thinking of doing it a bit earlier to give more time. > > In order to prevent bug 1872248 [1], new key must not be used until all > stable releases got new key with symlinks for all supported arches. New > builds were done few days ago, f33 is already in stable [2]. Yet it is > again incomplete and unusable. If the new key is activated now, it would > break (again!) gpg validation of rpm updates. It is my mistake for breaking the symlinks, thanks for the PR, it still needs some fixes but I made the new updates for f33 and f32 with symlinks fixed - https://bodhi.fedoraproject.org/updates/FEDORA-2021-0f90d0c2b0 and https://bodhi.fedoraproject.org/updates/FEDORA-2021-0fe981f3aa > > Please tell me I am missing something. I tried to help with fixing this > state, yet my PR[3] are still not merged. Could be new GPG key > activation explicitly mentioned in the schedule? Isn't it also the key step? We could add it to the schedule, but it wasn't trivial as we generally used to create the key a week before branching and it wasn't used until we hit branching date. > > So, how does Rawhide choose GPG key to sign built packages? Would it > break (again) today? Our automated signing process, robosignatory, does the signing in fedora, in the config[1] of it we will configure what koji keys should be used to sign what tags tags. Is there anything in particular you are looking for. [1] https://pagure.io/fedora-infra/ansible/blob/main/f/roles/robosignatory/templates/robosignatory.toml.j2 > > Regards, > Petr > > 1. https://bugzilla.redhat.com/show_bug.cgi?id=1872248 > 2. https://bodhi.fedoraproject.org/updates/FEDORA-2021-d17f7e917c > 3. https://src.fedoraproject.org/rpms/fedora-repos/pull-requests > > On 2/8/21 5:39 PM, Mohan Boddu wrote: > > Hello All, > > > > Fedora 34 will be branched from rawhide on Feb 09th 2021 as per the > > Fedora 34 schedule[1]. The process takes about a day and everything > > should be ready by Feb 10th 2021. You can still be able to build > > packages normally until then, but after the mass branching, rawhide > > and F34 will be separated. > > > > We will send another email once the branching is done. > > > > Thanks, > > Mohan Boddu. > > > > [1] https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html > > ___ > > devel mailing list -- devel@lists.fedoraproject.org > > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > > Fedora Code of Conduct: > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > > List Archives: > > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > > > > -- > Petr Menšík > Software Engineer > Red Hat, http://www.redhat.com/ > email: pemen...@redhat.com > PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 34 Mass Branching
Hi All, Fedora 34 has now been branched, please be sure to do a git pull --rebase to pick up the new branch, as an additional reminder rawhide/f35 has been completely isolated from previous releases, so this means that anything you do for f34 you also have to do in the rawhide branch and do a build there. There will be a Fedora 34 compose and it'll appear in http://dl.fedoraproject.org/pub/fedora/linux/development/34/ once complete. Please be sure to check it out. Bodhi is currently not active for Fedora 34, it will be enabled in a couple of weeks when we hit Beta change freeze point in the Fedora 34 schedule[1]. Two things to remember: 1. The modules will be built for a new platform:f35 2. The signing of rpms is not done yet with the new f35 key. 3. F34/branched release is frozen right now until we get a successful compose, expect that your f34 builds won't be available immediately. Thanks for understanding. [1] https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html On Mon, Feb 8, 2021 at 11:39 AM Mohan Boddu wrote: > > Hello All, > > Fedora 34 will be branched from rawhide on Feb 09th 2021 as per the > Fedora 34 schedule[1]. The process takes about a day and everything > should be ready by Feb 10th 2021. You can still be able to build > packages normally until then, but after the mass branching, rawhide > and F34 will be separated. > > We will send another email once the branching is done. > > Thanks, > Mohan Boddu. > > [1] https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora 34 Mass Branching
Hello All, Fedora 34 will be branched from rawhide on Feb 09th 2021 as per the Fedora 34 schedule[1]. The process takes about a day and everything should be ready by Feb 10th 2021. You can still be able to build packages normally until then, but after the mass branching, rawhide and F34 will be separated. We will send another email once the branching is done. Thanks, Mohan Boddu. [1] https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Fedora 34 Mass Branching
Hello All, Fedora 34 will be branched from rawhide on Feb 09th 2021 as per the Fedora 34 schedule[1]. The process takes about a day and everything should be ready by Feb 10th 2021. You can still be able to build packages normally until then, but after the mass branching, rawhide and F34 will be separated. We will send another email once the branching is done. Thanks, Mohan Boddu. [1] https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: src.fedoraproject.org branch conversion to rawhide/main tomorrow
Hello everyone, We are about to start the change process. As previously mentioned, pushes to 'master' branch will be disabled, once we made the changes, we will send another email at which point you need to run `git fetch -p` or checkout 'rawhide' branch and you can start building packages in the usual process you are accustomed to from the 'rawhide' branch. On Tue, Feb 2, 2021 at 6:08 PM Kevin Fenzi wrote: > > Greetings everyone. > > We finally have everything in place and hopefully tested to make the > switch tomorrow from master to rawhide/main branches for > src.fedoraproject.org. > > At 13:30UTC we will adjust pagure to reject pushes to 'master' and then > will be moving all the branches over to rawhide/main. As soon as all > packages are done, we will be adjusting pdc/hooks/existing pr's. > > We will be sending an additional email once changes are complete and > hopefully any downtime will be limited. > > Once the change is completed you will want to checkout rawhide/main > instead of master and update/recreate any existing forks you have. > > See > https://fedoraproject.org/wiki/Changes/GitRepos-master-to-main > for more information. > > Thanks, > > kevin > ___ > devel-announce mailing list -- devel-announce@lists.fedoraproject.org > To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Re: src.fedoraproject.org branch conversion to rawhide/main tomorrow
Hello everyone, We are about to start the change process. As previously mentioned, pushes to 'master' branch will be disabled, once we made the changes, we will send another email at which point you need to run `git fetch -p` or checkout 'rawhide' branch and you can start building packages in the usual process you are accustomed to from the 'rawhide' branch. On Tue, Feb 2, 2021 at 6:08 PM Kevin Fenzi wrote: > > Greetings everyone. > > We finally have everything in place and hopefully tested to make the > switch tomorrow from master to rawhide/main branches for > src.fedoraproject.org. > > At 13:30UTC we will adjust pagure to reject pushes to 'master' and then > will be moving all the branches over to rawhide/main. As soon as all > packages are done, we will be adjusting pdc/hooks/existing pr's. > > We will be sending an additional email once changes are complete and > hopefully any downtime will be limited. > > Once the change is completed you will want to checkout rawhide/main > instead of master and update/recreate any existing forks you have. > > See > https://fedoraproject.org/wiki/Changes/GitRepos-master-to-main > for more information. > > Thanks, > > kevin > ___ > devel-announce mailing list -- devel-annou...@lists.fedoraproject.org > To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 34 Mass Rebuild
Fedora 34 mass rebuild of rpms is done and we started running the mass rebuild of modules. FTBFS tickets [0] are being filed now. [0] https://bugzilla.redhat.com/show_bug.cgi?id=1868278 On Tue, Jan 26, 2021 at 1:25 PM Mohan Boddu wrote: > > On Tue, Jan 26, 2021 at 10:52 AM Fabio Valentini wrote: > > > > On Tue, Jan 26, 2021 at 4:47 PM Jonathan Wakely > > wrote: > > > > > > On 25/01/21 15:16 +0100, Fabio Valentini wrote: > > > >On Thu, Jan 21, 2021 at 5:10 PM Jakub Jelinek wrote: > > > >> > > > >> On Wed, Jan 20, 2021 at 02:17:28PM -0500, Mohan Boddu wrote: > > > >> > We are delaying the mass rebuild by a day as of now due to bugs in > > > >> > gcc > > > >> > and dwz. As of now, we are expecting to start mass rebuild tomorrow, > > > >> > Jan 21st 2021. There is a new build of gcc running currently which > > > >> > has > > > >> > fixes to gcc bugs, but we are still figuring out the dwz fixes. We > > > >> > will keep you posted with any further developments. > > > >> > > > >> Both gcc-11.0.0-0.16.fc34 and dwz-0.13-6.fc34 with the fixes > > > >> are now in f34-build (and in eln-build too with s/fc34/eln108/). > > > >> Those who had their builds fail in the last 2 days because of s390x > > > >> rpm crashes, errors about strip failures of LTO debug sections or dwz > > > >> crashes can retry their builds, sorry for the inconvenience. > > > >> > > > >> AFAIK we are waiting now for boost and maybe binutils. > > > > > > > >boost 1.75 was merged yesterday, and binutils 2.36 was postponed to F35. > > > > (snip) > > > > > >I'm wondering something else: Will automation trigger a "second mass > > > >rebuild" for ELN once all the builds from the Fedora mass rebuild get > > > >tagged into f34? > > > >There's apparently issues with ELN right now, it looks like the base > > > >buildroot is not installable because boost 1.75 builds were done in > > > >the wrong order. > > > > > > Wrong in what way? > > > > Looks like this was a transient issue. koschei is no longer > > complaining about boost. > > The problem was some dependency chain involving rpm-build -> > > source-highlight -> boost 1.73, but it appears to have been a > > temporary problem, if it was a problem at all. > > Also, boost 1.75 builds were built in a side tag, when the side tag > was merged it didn't merge boost-1.75 properly and the eln builds > started using older boost, that also caused some issues with deps. > > > > > Fabio > > ___ > > devel mailing list -- devel@lists.fedoraproject.org > > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > > Fedora Code of Conduct: > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > > List Archives: > > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 34 Mass Rebuild
On Tue, Jan 26, 2021 at 10:52 AM Fabio Valentini wrote: > > On Tue, Jan 26, 2021 at 4:47 PM Jonathan Wakely > wrote: > > > > On 25/01/21 15:16 +0100, Fabio Valentini wrote: > > >On Thu, Jan 21, 2021 at 5:10 PM Jakub Jelinek wrote: > > >> > > >> On Wed, Jan 20, 2021 at 02:17:28PM -0500, Mohan Boddu wrote: > > >> > We are delaying the mass rebuild by a day as of now due to bugs in gcc > > >> > and dwz. As of now, we are expecting to start mass rebuild tomorrow, > > >> > Jan 21st 2021. There is a new build of gcc running currently which has > > >> > fixes to gcc bugs, but we are still figuring out the dwz fixes. We > > >> > will keep you posted with any further developments. > > >> > > >> Both gcc-11.0.0-0.16.fc34 and dwz-0.13-6.fc34 with the fixes > > >> are now in f34-build (and in eln-build too with s/fc34/eln108/). > > >> Those who had their builds fail in the last 2 days because of s390x > > >> rpm crashes, errors about strip failures of LTO debug sections or dwz > > >> crashes can retry their builds, sorry for the inconvenience. > > >> > > >> AFAIK we are waiting now for boost and maybe binutils. > > > > > >boost 1.75 was merged yesterday, and binutils 2.36 was postponed to F35. > > (snip) > > > >I'm wondering something else: Will automation trigger a "second mass > > >rebuild" for ELN once all the builds from the Fedora mass rebuild get > > >tagged into f34? > > >There's apparently issues with ELN right now, it looks like the base > > >buildroot is not installable because boost 1.75 builds were done in > > >the wrong order. > > > > Wrong in what way? > > Looks like this was a transient issue. koschei is no longer > complaining about boost. > The problem was some dependency chain involving rpm-build -> > source-highlight -> boost 1.73, but it appears to have been a > temporary problem, if it was a problem at all. Also, boost 1.75 builds were built in a side tag, when the side tag was merged it didn't merge boost-1.75 properly and the eln builds started using older boost, that also caused some issues with deps. > > Fabio > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
fedpkg request-repo is broken
Hi all, While working on master to rawhide change [0], we made changes to fedpkg and other tools, while we thought of coordinating about when to release it (post mass rebuild) fedpkg-1.40-2 got released with the changes in F33 and rawhide. This has issues with processing new repo requests [1]. I am working on a fix to consider new repo requests with 'rawhide' branches as if they are made for 'master' branches. While we fix this and send an update to fedscm-admin tool, if you see an error with your new repo requests, change the branch name to master in the tickets filed against fedora-scm-requests repo [2]. Thanks for understanding. [0] https://fedoraproject.org/wiki/Changes/GitRepos-master-to-main [1] https://pagure.io/releng/fedora-scm-requests/issue/31870 [2] https://pagure.io/releng/fedora-scm-requests/ ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
fedpkg request-repo is broken
Hi all, While working on master to rawhide change [0], we made changes to fedpkg and other tools, while we thought of coordinating about when to release it (post mass rebuild) fedpkg-1.40-2 got released with the changes in F33 and rawhide. This has issues with processing new repo requests [1]. I am working on a fix to consider new repo requests with 'rawhide' branches as if they are made for 'master' branches. While we fix this and send an update to fedscm-admin tool, if you see an error with your new repo requests, change the branch name to master in the tickets filed against fedora-scm-requests repo [2]. Thanks for understanding. [0] https://fedoraproject.org/wiki/Changes/GitRepos-master-to-main [1] https://pagure.io/releng/fedora-scm-requests/issue/31870 [2] https://pagure.io/releng/fedora-scm-requests/ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 34 Mass Rebuild
Hi all, We are delaying the mass rebuild by a day as of now due to bugs in gcc and dwz. As of now, we are expecting to start mass rebuild tomorrow, Jan 21st 2021. There is a new build of gcc running currently which has fixes to gcc bugs, but we are still figuring out the dwz fixes. We will keep you posted with any further developments. Thanks. On Fri, Jan 15, 2021 at 2:31 PM Mohan Boddu wrote: > > Hi all, > > Per the Fedora 34 schedule[1] we will start a mass rebuild for Fedora 34 > on Jan 20th 2021. We will run a mass rebuild for Fedora 34 for the > changes listed in: > > https://pagure.io/releng/issues?status=Open=mass+rebuild > > Mass rebuild will be done in a side tag (f34-rebuild) and moved over > when completed. > > Failures can be seen > https://kojipkgs.fedoraproject.org/mass-rebuild/f34-failures.html > > Things still needing rebuilt > https://kojipkgs.fedoraproject.org/mass-rebuild/f34-need-rebuild.html > > FTBFS bugs will be filed shortly. > > Please be sure to let releng know if you see any bugs in the > reporting. You can contact releng in #fedora-releng on freenode, by > dropping an email to our list[2] or filing an issue in pagure[3] > > Regards, > Mohan Boddu. > > [1] https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html > [2] > https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ > [3] https://pagure.io/releng/ ___ devel-announce mailing list -- devel-annou...@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 34 Mass Rebuild
Hi all, We are delaying the mass rebuild by a day as of now due to bugs in gcc and dwz. As of now, we are expecting to start mass rebuild tomorrow, Jan 21st 2021. There is a new build of gcc running currently which has fixes to gcc bugs, but we are still figuring out the dwz fixes. We will keep you posted with any further developments. Thanks. On Fri, Jan 15, 2021 at 2:31 PM Mohan Boddu wrote: > > Hi all, > > Per the Fedora 34 schedule[1] we will start a mass rebuild for Fedora 34 > on Jan 20th 2021. We will run a mass rebuild for Fedora 34 for the > changes listed in: > > https://pagure.io/releng/issues?status=Open=mass+rebuild > > Mass rebuild will be done in a side tag (f34-rebuild) and moved over > when completed. > > Failures can be seen > https://kojipkgs.fedoraproject.org/mass-rebuild/f34-failures.html > > Things still needing rebuilt > https://kojipkgs.fedoraproject.org/mass-rebuild/f34-need-rebuild.html > > FTBFS bugs will be filed shortly. > > Please be sure to let releng know if you see any bugs in the > reporting. You can contact releng in #fedora-releng on freenode, by > dropping an email to our list[2] or filing an issue in pagure[3] > > Regards, > Mohan Boddu. > > [1] https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html > [2] > https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ > [3] https://pagure.io/releng/ ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Re: Fedora 34 Mass Rebuild
On Wed, Jan 20, 2021 at 11:36 AM Tom Stellard wrote: > > On 1/15/21 11:31 AM, Mohan Boddu wrote: > > Hi all, > > > > Per the Fedora 34 schedule[1] we will start a mass rebuild for Fedora 34 > > on Jan 20th 2021. We will run a mass rebuild for Fedora 34 for the > > changes listed in: > > > > https://pagure.io/releng/issues?status=Open=mass+rebuild > > > > Mass rebuild will be done in a side tag (f34-rebuild) and moved over > > when completed. > > > > Once a package is built in the side-tag, does it enter the side-tag > buildroot so that other packages built in the side-tag may use it? Nope, it wont, mass rebuild side tag uses the general release buildroot (for ex: f34-build), so in case if you really want something to be available in the buildroot, you can run a normal build and the mass rebuild will pick up the new buildroot, but only some mass rebuild builds will pick up the new buildroot depending on where exactly the mass rebuild is at that point of time. That's why we ask the maintainers to land all their changes in rawhide before we start the mass rebuild. > > -Tom > > > Failures can be seen > > https://kojipkgs.fedoraproject.org/mass-rebuild/f34-failures.html > > > > Things still needing rebuilt > > https://kojipkgs.fedoraproject.org/mass-rebuild/f34-need-rebuild.html > > > > FTBFS bugs will be filed shortly. > > > > Please be sure to let releng know if you see any bugs in the > > reporting. You can contact releng in #fedora-releng on freenode, by > > dropping an email to our list[2] or filing an issue in pagure[3] > > > > Regards, > > Mohan Boddu. > > > > [1] https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html > > [2] > > https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ > > [3] https://pagure.io/releng/ > > ___ > > devel-announce mailing list -- devel-annou...@lists.fedoraproject.org > > To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org > > Fedora Code of Conduct: > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > > List Archives: > > https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org > > ___ > > devel mailing list -- devel@lists.fedoraproject.org > > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > > Fedora Code of Conduct: > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > > List Archives: > > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > > > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 34 Mass Rebuild
On Sat, Jan 16, 2021 at 2:44 PM Kevin Fenzi wrote: > > On Sat, Jan 16, 2021 at 12:43:56AM +0100, Fabio Valentini wrote: > > > > What system will be used to run the mass rebuild script? > > They run on compose-x86-01 I think. We run mass rebuild on compose-branched01.iad2.fp.o which is updated to F33. > > > If it's a fedora 33 system, I suggest modifying the script to invoke > > rpmdev-bumpspec with the "-D" flag for better compatibiltiy with older > > RPM versions (for people who care about that sort of thing, e.g. > > maintainers who merge specs back into epel branches). I updated the mass-rebuild.py script to use '-D' flag https://pagure.io/releng/pull-request/9951 > > It's currently f32, but we were going to upgrade it. > We could do that and add this in I think... > > Thanks for the suggestion! > > kevin > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora 34 Mass Rebuild
Hi all, Per the Fedora 34 schedule[1] we will start a mass rebuild for Fedora 34 on Jan 20th 2021. We will run a mass rebuild for Fedora 34 for the changes listed in: https://pagure.io/releng/issues?status=Open=mass+rebuild Mass rebuild will be done in a side tag (f34-rebuild) and moved over when completed. Failures can be seen https://kojipkgs.fedoraproject.org/mass-rebuild/f34-failures.html Things still needing rebuilt https://kojipkgs.fedoraproject.org/mass-rebuild/f34-need-rebuild.html FTBFS bugs will be filed shortly. Please be sure to let releng know if you see any bugs in the reporting. You can contact releng in #fedora-releng on freenode, by dropping an email to our list[2] or filing an issue in pagure[3] Regards, Mohan Boddu. [1] https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html [2] https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ [3] https://pagure.io/releng/ ___ devel-announce mailing list -- devel-annou...@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora 34 Mass Rebuild
Hi all, Per the Fedora 34 schedule[1] we will start a mass rebuild for Fedora 34 on Jan 20th 2021. We will run a mass rebuild for Fedora 34 for the changes listed in: https://pagure.io/releng/issues?status=Open=mass+rebuild Mass rebuild will be done in a side tag (f34-rebuild) and moved over when completed. Failures can be seen https://kojipkgs.fedoraproject.org/mass-rebuild/f34-failures.html Things still needing rebuilt https://kojipkgs.fedoraproject.org/mass-rebuild/f34-need-rebuild.html FTBFS bugs will be filed shortly. Please be sure to let releng know if you see any bugs in the reporting. You can contact releng in #fedora-releng on freenode, by dropping an email to our list[2] or filing an issue in pagure[3] Regards, Mohan Boddu. [1] https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html [2] https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ [3] https://pagure.io/releng/ ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Re: AArch64 support for container and flatpak builds
This is great news, thanks to everyone who worked on this project. On Thu, Dec 10, 2020 at 5:44 AM Mark O'Brien wrote: > > All, > We are very happy to announce that we now have AArch64 support for flatpak > and container fedpkg builds in production! > > By default all flatpak and container builds will be built on both > architectures from now on. > > Thanks, > Fedora OSBS initiative > ___ > devel mailing list -- de...@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Re: AArch64 support for container and flatpak builds
This is great news, thanks to everyone who worked on this project. On Thu, Dec 10, 2020 at 5:44 AM Mark O'Brien wrote: > > All, > We are very happy to announce that we now have AArch64 support for flatpak > and container fedpkg builds in production! > > By default all flatpak and container builds will be built on both > architectures from now on. > > Thanks, > Fedora OSBS initiative > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 31 End Of Life
Hello all, As of the 24th of November 2020, Fedora 31 has reached its end of life for updates and support. No further updates, including security updates, will be available for Fedora 31. All the updates that are currently in testing won't get pushed to stable. Fedora 32 will continue to receive updates until approximately one month after the release of Fedora 34. The maintenance schedule of Fedora releases is documented on the Fedora Project wiki [0]. The Fedora Project wiki also contains instructions [1] on how to upgrade from a previous release of Fedora to a version receiving updates. Mohan Boddu. [0] https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule [1] https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/ On Fri, Nov 20, 2020 at 10:26 AM Mohan Boddu wrote: > > Hello all, > > Fedora 31 will go end of life for updates and support on 24th of > November 2020. No further updates, including security updates, will be > available for Fedora 31 after the said date. All the updates of Fedora > 31 being pushed to stable will be stopped as well. > > Fedora 32 will continue to receive updates until approximately one > month after the release of Fedora 34. The maintenance schedule of > Fedora releases is documented on the Fedora Project wiki [0]. The > fedora Project wiki also contains instructions [1] on how to upgrade > from a previous release of Fedora to a version receiving updates. > > Regards, > Mohan Boddu. > > [0]https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule > [1]https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Re: Fedora 31 End Of Life
Hello all, As of the 24th of November 2020, Fedora 31 has reached its end of life for updates and support. No further updates, including security updates, will be available for Fedora 31. All the updates that are currently in testing won't get pushed to stable. Fedora 32 will continue to receive updates until approximately one month after the release of Fedora 34. The maintenance schedule of Fedora releases is documented on the Fedora Project wiki [0]. The Fedora Project wiki also contains instructions [1] on how to upgrade from a previous release of Fedora to a version receiving updates. Mohan Boddu. [0] https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule [1] https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/ On Fri, Nov 20, 2020 at 10:26 AM Mohan Boddu wrote: > > Hello all, > > Fedora 31 will go end of life for updates and support on 24th of > November 2020. No further updates, including security updates, will be > available for Fedora 31 after the said date. All the updates of Fedora > 31 being pushed to stable will be stopped as well. > > Fedora 32 will continue to receive updates until approximately one > month after the release of Fedora 34. The maintenance schedule of > Fedora releases is documented on the Fedora Project wiki [0]. The > fedora Project wiki also contains instructions [1] on how to upgrade > from a previous release of Fedora to a version receiving updates. > > Regards, > Mohan Boddu. > > [0]https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule > [1]https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora 31 End Of Life
Hello all, Fedora 31 will go end of life for updates and support on 24th of November 2020. No further updates, including security updates, will be available for Fedora 31 after the said date. All the updates of Fedora 31 being pushed to stable will be stopped as well. Fedora 32 will continue to receive updates until approximately one month after the release of Fedora 34. The maintenance schedule of Fedora releases is documented on the Fedora Project wiki [0]. The fedora Project wiki also contains instructions [1] on how to upgrade from a previous release of Fedora to a version receiving updates. Regards, Mohan Boddu. [0]https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule [1]https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Fedora 31 End Of Life
Hello all, Fedora 31 will go end of life for updates and support on 24th of November 2020. No further updates, including security updates, will be available for Fedora 31 after the said date. All the updates of Fedora 31 being pushed to stable will be stopped as well. Fedora 32 will continue to receive updates until approximately one month after the release of Fedora 34. The maintenance schedule of Fedora releases is documented on the Fedora Project wiki [0]. The fedora Project wiki also contains instructions [1] on how to upgrade from a previous release of Fedora to a version receiving updates. Regards, Mohan Boddu. [0]https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule [1]https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Query: What to do for multiple module builds in bodhi for 'jmc' in F33?
On Tue, Nov 10, 2020 at 9:42 AM Petr Pisar wrote: > > On Mon, Nov 09, 2020 at 10:35:45PM -0500, Jie Kang wrote: > > Thank you. There is a second stream for jmc in that update: > > jmc-latest-3320200902194158.601d93de > > > > Can it be removed as well? > > > I removed it from that update. You should be able to submit a new update with > jmc:latest:3320201104214853 now. Thanks Petr > > -- Petr > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Query: What to do for multiple module builds in bodhi for 'jmc' in F33?
I fixed it https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-847691dbcf#comment-1723407 On Mon, Nov 9, 2020 at 5:16 PM Jie Kang wrote: > > Hi all, > > I'm attempting to submit a critical bugfix update for my jmc module in > F33, however I found that there is an open security update which > includes it [1], which forces mine to also be seen as a security > update. I'm not sure what that update is sitting for at this time. I > noticed another maintainer was able to remove modules from [1] but I > don't have such permissions. Could anyone advise on how to proceed? > > [1] > https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-847691dbcf > > > Thank you, > Jie Kang > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora 33 Final Freeze
Hi all, Tomorrow, October 6th 2020, is an important day on the Fedora 33 schedule [1], with significant cut-offs. Tomorrow we have the Final Freeze [2] which starts at 14:00 UTC. This means that only packages which fix accepted blocker or freeze exception bugs [3][4][5] will be marked as 'stable' and included in the Final composes. Other builds will remain in updates-testing until the Final release is approved, at which point the Final freeze is lifted and packages can move to the 'updates' repository, pending updates will be pushed before final release as zero day updates. [1] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html [2] https://fedoraproject.org/wiki/Milestone_freezes [3] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process [4] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process [5] https://qa.fedoraproject.org/blockerbugs/milestone/33/final/buglist Regards, Mohan Boddu Release Engineering ___ devel-announce mailing list -- devel-annou...@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora 33 Final Freeze
Hi all, Tomorrow, October 6th 2020, is an important day on the Fedora 33 schedule [1], with significant cut-offs. Tomorrow we have the Final Freeze [2] which starts at 14:00 UTC. This means that only packages which fix accepted blocker or freeze exception bugs [3][4][5] will be marked as 'stable' and included in the Final composes. Other builds will remain in updates-testing until the Final release is approved, at which point the Final freeze is lifted and packages can move to the 'updates' repository, pending updates will be pushed before final release as zero day updates. [1] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html [2] https://fedoraproject.org/wiki/Milestone_freezes [3] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process [4] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process [5] https://qa.fedoraproject.org/blockerbugs/milestone/33/final/buglist Regards, Mohan Boddu Release Engineering ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Fedora 33 Beta Release Announcement
Fedora 33 Beta Released -- The Fedora Project is pleased to announce the immediate availability of Fedora 33 Beta, the next step towards our planned Fedora 33 release at the end of October. Download the prerelease from our Get Fedora site: * Get Fedora 33 Beta Workstation: https://getfedora.org/workstation/download/ * Get Fedora 33 Beta Server: https://getfedora.org/server/download/ * Get Fedora 33 IoT: https://getfedora.org/iot/download/ Or, check out one of our popular variants, including KDE Plasma, Xfce, and other desktop environments, as well as images for ARM devices: * Get Fedora 33 Beta Spins: https://spins.fedoraproject.org/prerelease * Get Fedora 33 Beta Labs: https://labs.fedoraproject.org/prerelease * Get Fedora 33 Beta ARM: https://arm.fedoraproject.org/prerelease ## Beta Release Highlights * All of the desktop variants of Fedora 33 Beta will use BTRFS as the default filesystem. * Fedora 33 Workstation Beta includes GNOME 3.38 * With Fedora 33 Beta, Fedora IoT is now an official Fedora Edition. * And more ... For more details about the release, read the full announcement at * https://fedoramagazine.org/announcing-the-release-of-fedora-33-beta/ or look for the prerelease pages in the download sections at * https://getfedora.org/ Since this is a Beta release, we expect that you may encounter bugs or missing features. To report issues encountered during testing, contact the Fedora QA team via the t...@lists.fedoraproject.org mailing list or in #fedora-qa on Freenode. Regards, Mohan Boddu Fedora Release Engineering. ___ devel-announce mailing list -- devel-annou...@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora 33 Beta Release Announcement
Fedora 33 Beta Released -- The Fedora Project is pleased to announce the immediate availability of Fedora 33 Beta, the next step towards our planned Fedora 33 release at the end of October. Download the prerelease from our Get Fedora site: * Get Fedora 33 Beta Workstation: https://getfedora.org/workstation/download/ * Get Fedora 33 Beta Server: https://getfedora.org/server/download/ * Get Fedora 33 IoT: https://getfedora.org/iot/download/ Or, check out one of our popular variants, including KDE Plasma, Xfce, and other desktop environments, as well as images for ARM devices: * Get Fedora 33 Beta Spins: https://spins.fedoraproject.org/prerelease * Get Fedora 33 Beta Labs: https://labs.fedoraproject.org/prerelease * Get Fedora 33 Beta ARM: https://arm.fedoraproject.org/prerelease ## Beta Release Highlights * All of the desktop variants of Fedora 33 Beta will use BTRFS as the default filesystem. * Fedora 33 Workstation Beta includes GNOME 3.38 * With Fedora 33 Beta, Fedora IoT is now an official Fedora Edition. * And more ... For more details about the release, read the full announcement at * https://fedoramagazine.org/announcing-the-release-of-fedora-33-beta/ or look for the prerelease pages in the download sections at * https://getfedora.org/ Since this is a Beta release, we expect that you may encounter bugs or missing features. To report issues encountered during testing, contact the Fedora QA team via the t...@lists.fedoraproject.org mailing list or in #fedora-qa on Freenode. Regards, Mohan Boddu Fedora Release Engineering. ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Fixed: unable to push to f31 branches on dist-git
Hello All, We had an issue today as some people were unable to push to dist-git f31 branches, it was caused by setting a wrong date in pdc. It has been fixed now and people can push to f31 branches. More info at https://pagure.io/fedora-infrastructure/issue/9325 Sorry for the trouble that this has caused. Thanks. ___ devel-announce mailing list -- devel-annou...@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fixed: unable to push to f31 branches on dist-git
Hello All, We had an issue today as some people were unable to push to dist-git f31 branches, it was caused by setting a wrong date in pdc. It has been fixed now and people can push to f31 branches. More info at https://pagure.io/fedora-infrastructure/issue/9325 Sorry for the trouble that this has caused. Thanks. ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Re: Suspicious downgrades when upgrading from F32 to F33: containers-common, fuse-overlayfs, strace, thunderbird
On Thu, Aug 27, 2020 at 9:42 AM Mohan Boddu wrote: > > On Wed, Aug 26, 2020 at 1:53 PM kevin wrote: > > > > On Wed, Aug 26, 2020 at 07:18:49PM +0200, Fabio Valentini wrote: > > > > > > Hrm. It looks like at least some of those issues were transient, yes. > > > However, two issues are still left: > > > > > > - libdkimpp-2.0.0-6.fc33 is tagged with f33 and f34 but 2.0.0-3.fc32 > > > is in the f33 repos > > > > f34 should have been fine... f33 the newer one was only tagged in this > > morning: > > > > Wed Aug 26 03:25:54 2020 libdkimpp-2.0.0-6.fc33 tagged into f33 by humaton > > [still active] > > > > So it should be in today's f33 compose, but indeed I don't see it there. > > Odd. > > > > oh. Man. I sure hate timezones. ;) > > > > It was tagged after the f33 compose started. > > > > > - swift-lang-5.2.5-1.fc33 is tagged with f33 and f34 but 5.2.4-3.fc33 > > > is in the f33 repos > > > > Same here. Tagged in this morning, should be fixed tomorrow. > > I untagged them since they are directly tagged to f33 tag without > getting right with fedora-33 key. I am tagging them to > f33-updates-candidate to let bodhi take care of the process flow since > we are in freeze now. And its not possible, since there is a update with the same build that got pushed to f34, sigh. I will work with adamw in creating a FBR to push these updates directly to the f33 tag. > > > > > > > > > Both these packages were built ~two weeks ago, so maybe they were > > > screwed up by the mass branching somehow? > > > > Yeah, possibly so. > > > > kevin > > ___ > > devel mailing list -- devel@lists.fedoraproject.org > > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > > Fedora Code of Conduct: > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > > List Archives: > > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Suspicious downgrades when upgrading from F32 to F33: containers-common, fuse-overlayfs, strace, thunderbird
On Wed, Aug 26, 2020 at 1:53 PM kevin wrote: > > On Wed, Aug 26, 2020 at 07:18:49PM +0200, Fabio Valentini wrote: > > > > Hrm. It looks like at least some of those issues were transient, yes. > > However, two issues are still left: > > > > - libdkimpp-2.0.0-6.fc33 is tagged with f33 and f34 but 2.0.0-3.fc32 > > is in the f33 repos > > f34 should have been fine... f33 the newer one was only tagged in this > morning: > > Wed Aug 26 03:25:54 2020 libdkimpp-2.0.0-6.fc33 tagged into f33 by humaton > [still active] > > So it should be in today's f33 compose, but indeed I don't see it there. > Odd. > > oh. Man. I sure hate timezones. ;) > > It was tagged after the f33 compose started. > > > - swift-lang-5.2.5-1.fc33 is tagged with f33 and f34 but 5.2.4-3.fc33 > > is in the f33 repos > > Same here. Tagged in this morning, should be fixed tomorrow. I untagged them since they are directly tagged to f33 tag without getting right with fedora-33 key. I am tagging them to f33-updates-candidate to let bodhi take care of the process flow since we are in freeze now. > > > > > Both these packages were built ~two weeks ago, so maybe they were > > screwed up by the mass branching somehow? > > Yeah, possibly so. > > kevin > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: New libxmlb 0.2.0 which breaks API and ABI
On Tue, Aug 18, 2020 at 10:40 AM Richard Hughes wrote: > > Hi all, > > I'm going to build the recently released libxmlb 0.2.0 into rawhide > and F33. It has two consumers (fwupd and gnome-software) both of which > I own, and I'll rebuild them at the same time. Any problems please > shout. It seems like gnome-firmware also needs it and due to that both rawhide and branched composes failed today. https://koji.fedoraproject.org/koji/taskinfo?taskID=49594775 https://koji.fedoraproject.org/koji/taskinfo?taskID=49587065 I am rebuilding it for both f33 and f34 now. Just FYI for future reference :) > > RIchard. > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Buildroot overrides in branched pre updates-testing activation?
Seems like an issue with bodhi during when we enabled gating on f33 and we enabled autosigning on f33. For now I manually untagged them, which should fix with buildroot being wrong. On Sun, Aug 16, 2020 at 10:24 AM Fabio Valentini wrote: > > Hi everybody, > > I've just noticed that bodhi allows users to create buildroot > overrides for F33 for no good reason (updates-testing is not even > active yet and updates to to stable directly). There's 41 (!) active > overrides for F33: > > https://bodhi.fedoraproject.org/overrides/?search==False=F33 > > Doesn't this screw up the builds in koji? Why does bodhi allow > creating overrides for branched pre-updates-testing activation? > > Fabio > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 33 Mass Branching
On Wed, Aug 12, 2020 at 8:14 AM Miro Hrončok wrote: > > On 12. 08. 20 1:09, Mohan Boddu wrote: > > Bodhi is currently not > > active for Fedora 33, it will be enabled in a couple of weeks when we > > hit Beta change freeze point in the Fedora 33 schedule[1]. > > It seems that this is not true this time due to gaitng. My f33 builds go > trough > Bodhi (where they rest in pending, presumably until the compose is done). Yes, you are right, but maintainers shouldn't think that bodhi is active and try to submit builds as updates in bodhi. Maybe, it should be better to reword it > > -- > Miro Hrončok > -- > Phone: +420777974800 > IRC: mhroncok > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 33 Mass Branching
Hi All, Fedora 33 has now been branched, please be sure to do a git pull --rebase to pick up the new branch, as an additional reminder rawhide/f34 has been completely isolated from previous releases, so this means that anything you do for f33 you also have to do in the master branch and do a build there. There will be a Fedora 33 compose and it'll appear in http://dl.fedoraproject.org/pub/fedora/linux/development/33/ once complete. Please be sure to check it out. Bodhi is currently not active for Fedora 33, it will be enabled in a couple of weeks when we hit Beta change freeze point in the Fedora 33 schedule[1]. Two things to remember: 1. The modules will be built for a new platform:f34 2. The signing of rpms is not done yet with the new f34 key. 3. F33/branched release is frozen right now until we get a successful compose, expect that your f33 builds won't be available immediately. Thanks for understanding. Mohan Boddu. [1] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html On Sun, Aug 9, 2020 at 3:16 PM Mohan Boddu wrote: > > Hello All, > > Fedora 33 will be branched from rawhide on August 11th 2020 as per the > Fedora 33 schedule[1]. The process takes about a day and everything > should be ready by August 12th 2020. You can still be able to build > packages normally until then, but after the mass branching, rawhide > and F33 will be separated. > > We will send another email once the branching is done. > > Thanks, > Mohan Boddu. > > [1] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html ___ devel-announce mailing list -- devel-annou...@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 33 Mass Branching
Hi All, Fedora 33 has now been branched, please be sure to do a git pull --rebase to pick up the new branch, as an additional reminder rawhide/f34 has been completely isolated from previous releases, so this means that anything you do for f33 you also have to do in the master branch and do a build there. There will be a Fedora 33 compose and it'll appear in http://dl.fedoraproject.org/pub/fedora/linux/development/33/ once complete. Please be sure to check it out. Bodhi is currently not active for Fedora 33, it will be enabled in a couple of weeks when we hit Beta change freeze point in the Fedora 33 schedule[1]. Two things to remember: 1. The modules will be built for a new platform:f34 2. The signing of rpms is not done yet with the new f34 key. 3. F33/branched release is frozen right now until we get a successful compose, expect that your f33 builds won't be available immediately. Thanks for understanding. Mohan Boddu. [1] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html On Sun, Aug 9, 2020 at 3:16 PM Mohan Boddu wrote: > > Hello All, > > Fedora 33 will be branched from rawhide on August 11th 2020 as per the > Fedora 33 schedule[1]. The process takes about a day and everything > should be ready by August 12th 2020. You can still be able to build > packages normally until then, but after the mass branching, rawhide > and F33 will be separated. > > We will send another email once the branching is done. > > Thanks, > Mohan Boddu. > > [1] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Re: Fedora 33 Mass Branching
On Tue, Aug 11, 2020 at 12:56 PM Tom Stellard wrote: > > On 8/11/20 12:44 PM, Kevin Fenzi wrote: > > On Mon, Aug 10, 2020 at 05:39:02PM -0700, Tom Stellard wrote: > >> On 8/9/20 3:16 PM, Mohan Boddu wrote: > >>> Hello All, > >>> > >>> Fedora 33 will be branched from rawhide on August 11th 2020 as per the > >>> Fedora 33 schedule[1]. The process takes about a day and everything > >>> should be ready by August 12th 2020. You can still be able to build > >>> packages normally until then, but after the mass branching, rawhide > >>> and F33 will be separated. > >>> > >> > >> How will this affect any outstanding side-tags that inherit from the f33 > >> tag? Will we need to re-tag the packages into an f34-based side-tag? > > > > Those side tags will continue to exist and point to f33/branched. > > > > You will want to create new f34 ones and build out things in those. > > > > Do I need to rebuild everything or can I just tag the current builds > into the new f34 side-tag? I dont think bodhi will allow you to merge them into f34, you might have to rebuild them again. > > -Tom > > > kevin > > > > > > ___ > > devel mailing list -- devel@lists.fedoraproject.org > > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > > Fedora Code of Conduct: > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > > List Archives: > > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > > > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora 33 Mass Branching
Hello All, Fedora 33 will be branched from rawhide on August 11th 2020 as per the Fedora 33 schedule[1]. The process takes about a day and everything should be ready by August 12th 2020. You can still be able to build packages normally until then, but after the mass branching, rawhide and F33 will be separated. We will send another email once the branching is done. Thanks, Mohan Boddu. [1] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html ___ devel-announce mailing list -- devel-annou...@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora 33 Mass Branching
Hello All, Fedora 33 will be branched from rawhide on August 11th 2020 as per the Fedora 33 schedule[1]. The process takes about a day and everything should be ready by August 12th 2020. You can still be able to build packages normally until then, but after the mass branching, rawhide and F33 will be separated. We will send another email once the branching is done. Thanks, Mohan Boddu. [1] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Re: Fedora 33 Mass Rebuild
Hi all, Per the Fedora 33 schedule[1] we started a mass rebuild for Fedora 33 on Jul 27th 2017. We did a mass rebuild for Fedora 33 for the changes listed in: https://pagure.io/releng/issue/9616 Mass rebuild was done in a side tag (f33-rebuild) and moved over to f33. Failures can be seen https://kojipkgs.fedoraproject.org/mass-rebuild/f33-failures.html Things still needing rebuilt https://kojipkgs.fedoraproject.org/mass-rebuild/f33-need-rebuild.html 18002 builds have been tagged into f33, there are currently 2811 failed builds that need to be addressed by the package maintainers. Mass rebuildling of modules and FTBFS bugs will be filed shortly. Please be sure to let releng know if you see any bugs in the reporting. You can contact releng in #fedora-releng on freenode, by dropping an email to our list[2] or filing an issue in pagure[3] Regards, Mohan Boddu. [1] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html [2] https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ [3] https://pagure.io/releng/ On Wed, Jul 22, 2020 at 10:59 AM Mohan Boddu wrote: > > Hi all, > > The mass rebuild is postponed to next Monday 27th July 2020 since a > couple of changes haven't landed yet. > > For more information, please look at https://pagure.io/fesco/issue/2451 > > We will keep you posted if anything changes. > > Thanks. > > On Mon, Jul 20, 2020 at 5:38 PM Mohan Boddu wrote: > > > > Mohan Boddu > > > > 4:32 PM (1 hour ago) > > to devel-announce > > Hi all, > > > > Per the Fedora 33 schedule[1] we will start a mass rebuild for Fedora 33 > > on Jul 22nd 2020. We will run a mass rebuild for Fedora 33 for the > > changes listed in: > > > > https://pagure.io/releng/issues?status=Open=mass+rebuild > > > > Mass rebuild will be done in a side tag (f33-rebuild) and moved over > > when completed. > > > > Failures can be seen > > https://kojipkgs.fedoraproject.org/mass-rebuild/f33-failures.html > > > > Things still needing rebuilt > > https://kojipkgs.fedoraproject.org/mass-rebuild/f33-need-rebuild.html > > > > FTBFS bugs will be filed shortly. > > > > Please be sure to let releng know if you see any bugs in the > > reporting. You can contact releng in #fedora-releng on freenode, by > > dropping an email to our list[2] or filing an issue in pagure[3] > > > > Regards, > > Mohan Boddu. > > > > [1] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html > > [2] > > https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ > > [3] https://pagure.io/releng/ ___ devel-announce mailing list -- devel-annou...@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 33 Mass Rebuild
Hi all, Per the Fedora 33 schedule[1] we started a mass rebuild for Fedora 33 on Jul 27th 2017. We did a mass rebuild for Fedora 33 for the changes listed in: https://pagure.io/releng/issue/9616 Mass rebuild was done in a side tag (f33-rebuild) and moved over to f33. Failures can be seen https://kojipkgs.fedoraproject.org/mass-rebuild/f33-failures.html Things still needing rebuilt https://kojipkgs.fedoraproject.org/mass-rebuild/f33-need-rebuild.html 18002 builds have been tagged into f33, there are currently 2811 failed builds that need to be addressed by the package maintainers. Mass rebuildling of modules and FTBFS bugs will be filed shortly. Please be sure to let releng know if you see any bugs in the reporting. You can contact releng in #fedora-releng on freenode, by dropping an email to our list[2] or filing an issue in pagure[3] Regards, Mohan Boddu. [1] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html [2] https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ [3] https://pagure.io/releng/ On Wed, Jul 22, 2020 at 10:59 AM Mohan Boddu wrote: > > Hi all, > > The mass rebuild is postponed to next Monday 27th July 2020 since a > couple of changes haven't landed yet. > > For more information, please look at https://pagure.io/fesco/issue/2451 > > We will keep you posted if anything changes. > > Thanks. > > On Mon, Jul 20, 2020 at 5:38 PM Mohan Boddu wrote: > > > > Mohan Boddu > > > > 4:32 PM (1 hour ago) > > to devel-announce > > Hi all, > > > > Per the Fedora 33 schedule[1] we will start a mass rebuild for Fedora 33 > > on Jul 22nd 2020. We will run a mass rebuild for Fedora 33 for the > > changes listed in: > > > > https://pagure.io/releng/issues?status=Open=mass+rebuild > > > > Mass rebuild will be done in a side tag (f33-rebuild) and moved over > > when completed. > > > > Failures can be seen > > https://kojipkgs.fedoraproject.org/mass-rebuild/f33-failures.html > > > > Things still needing rebuilt > > https://kojipkgs.fedoraproject.org/mass-rebuild/f33-need-rebuild.html > > > > FTBFS bugs will be filed shortly. > > > > Please be sure to let releng know if you see any bugs in the > > reporting. You can contact releng in #fedora-releng on freenode, by > > dropping an email to our list[2] or filing an issue in pagure[3] > > > > Regards, > > Mohan Boddu. > > > > [1] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html > > [2] > > https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ > > [3] https://pagure.io/releng/ ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Re: Fedora 33 Mass Rebuild
Hi all, The mass rebuild is postponed to next Monday 27th July 2020 since a couple of changes haven't landed yet. For more information, please look at https://pagure.io/fesco/issue/2451 We will keep you posted if anything changes. Thanks. On Mon, Jul 20, 2020 at 5:38 PM Mohan Boddu wrote: > > Mohan Boddu > > 4:32 PM (1 hour ago) > to devel-announce > Hi all, > > Per the Fedora 33 schedule[1] we will start a mass rebuild for Fedora 33 > on Jul 22nd 2020. We will run a mass rebuild for Fedora 33 for the > changes listed in: > > https://pagure.io/releng/issues?status=Open=mass+rebuild > > Mass rebuild will be done in a side tag (f33-rebuild) and moved over > when completed. > > Failures can be seen > https://kojipkgs.fedoraproject.org/mass-rebuild/f33-failures.html > > Things still needing rebuilt > https://kojipkgs.fedoraproject.org/mass-rebuild/f33-need-rebuild.html > > FTBFS bugs will be filed shortly. > > Please be sure to let releng know if you see any bugs in the > reporting. You can contact releng in #fedora-releng on freenode, by > dropping an email to our list[2] or filing an issue in pagure[3] > > Regards, > Mohan Boddu. > > [1] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html > [2] > https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ > [3] https://pagure.io/releng/ ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Re: Fedora 33 Mass Rebuild
Hi all, The mass rebuild is postponed to next Monday 27th July 2020 since a couple of changes haven't landed yet. For more information, please look at https://pagure.io/fesco/issue/2451 We will keep you posted if anything changes. Thanks. On Mon, Jul 20, 2020 at 5:38 PM Mohan Boddu wrote: > > Mohan Boddu > > 4:32 PM (1 hour ago) > to devel-announce > Hi all, > > Per the Fedora 33 schedule[1] we will start a mass rebuild for Fedora 33 > on Jul 22nd 2020. We will run a mass rebuild for Fedora 33 for the > changes listed in: > > https://pagure.io/releng/issues?status=Open=mass+rebuild > > Mass rebuild will be done in a side tag (f33-rebuild) and moved over > when completed. > > Failures can be seen > https://kojipkgs.fedoraproject.org/mass-rebuild/f33-failures.html > > Things still needing rebuilt > https://kojipkgs.fedoraproject.org/mass-rebuild/f33-need-rebuild.html > > FTBFS bugs will be filed shortly. > > Please be sure to let releng know if you see any bugs in the > reporting. You can contact releng in #fedora-releng on freenode, by > dropping an email to our list[2] or filing an issue in pagure[3] > > Regards, > Mohan Boddu. > > [1] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html > [2] > https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ > [3] https://pagure.io/releng/ ___ devel-announce mailing list -- devel-annou...@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora 33 Mass Rebuild
Mohan Boddu 4:32 PM (1 hour ago) to devel-announce Hi all, Per the Fedora 33 schedule[1] we will start a mass rebuild for Fedora 33 on Jul 22nd 2020. We will run a mass rebuild for Fedora 33 for the changes listed in: https://pagure.io/releng/issues?status=Open=mass+rebuild Mass rebuild will be done in a side tag (f33-rebuild) and moved over when completed. Failures can be seen https://kojipkgs.fedoraproject.org/mass-rebuild/f33-failures.html Things still needing rebuilt https://kojipkgs.fedoraproject.org/mass-rebuild/f33-need-rebuild.html FTBFS bugs will be filed shortly. Please be sure to let releng know if you see any bugs in the reporting. You can contact releng in #fedora-releng on freenode, by dropping an email to our list[2] or filing an issue in pagure[3] Regards, Mohan Boddu. [1] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html [2] https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ [3] https://pagure.io/releng/ ___ devel-announce mailing list -- devel-annou...@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora 33 Mass Rebuild
Mohan Boddu 4:32 PM (1 hour ago) to devel-announce Hi all, Per the Fedora 33 schedule[1] we will start a mass rebuild for Fedora 33 on Jul 22nd 2020. We will run a mass rebuild for Fedora 33 for the changes listed in: https://pagure.io/releng/issues?status=Open=mass+rebuild Mass rebuild will be done in a side tag (f33-rebuild) and moved over when completed. Failures can be seen https://kojipkgs.fedoraproject.org/mass-rebuild/f33-failures.html Things still needing rebuilt https://kojipkgs.fedoraproject.org/mass-rebuild/f33-need-rebuild.html FTBFS bugs will be filed shortly. Please be sure to let releng know if you see any bugs in the reporting. You can contact releng in #fedora-releng on freenode, by dropping an email to our list[2] or filing an issue in pagure[3] Regards, Mohan Boddu. [1] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html [2] https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ [3] https://pagure.io/releng/ ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Fedora 30 EOL
Hello all, As of the 26th of May 2020, Fedora 30 has reached its end of life for updates and support. No further updates, including security updates, will be available for Fedora 30. Fedora 31 will continue to receive updates until approximately one month after the release of Fedora 33. The maintenance schedule of Fedora releases is documented on the Fedora Project wiki [0]. The Fedora Project wiki also contains instructions [1] on how to upgrade from a previous release of Fedora to a version receiving updates. Mohan Boddu. [0] https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule [1] https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/ ___ devel-announce mailing list -- devel-annou...@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora 30 EOL
Hello all, As of the 26th of May 2020, Fedora 30 has reached its end of life for updates and support. No further updates, including security updates, will be available for Fedora 30. Fedora 31 will continue to receive updates until approximately one month after the release of Fedora 33. The maintenance schedule of Fedora releases is documented on the Fedora Project wiki [0]. The Fedora Project wiki also contains instructions [1] on how to upgrade from a previous release of Fedora to a version receiving updates. Mohan Boddu. [0] https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule [1] https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/ ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Re: Retired packages with maintainers
On Tue, May 12, 2020 at 9:14 AM Pierre-Yves Chibon wrote: > > On Tue, May 12, 2020 at 02:51:03PM +0200, Miro Hrončok wrote: > > On 12. 05. 20 8:49, Pierre-Yves Chibon wrote: > > > Finally, does everyone agree about the original request: "remove all > > > maintainers > > > of retired packages"? Or should we bring this to FESCo? > > > > If the procedure is "remove all maintainers if all branches are retired or > > EOL" than yes, this is a good thing. However, not sure if worth spending > > energy on. What are the benefits over status quo? > > Someone asked us to look into this, so I did, briefly. > I am also very happy to close the ticket as "Won't fix" and move on :) I think we should orphan the packages, for couple of reasons: 1. It's easier to find orphaned packages compared to retired packages 2. When we unretire, we will give the package to the requestor, but it might still leave the non-main maintainers (which I think is wrong?) I know you already mentioned - The script checks *all* branches in PDC and ensure that they are all "active=False", this is very important and please re-verify, as we dont want to orphan EPEL only packages as well as packages that are still being maintained in released branches but retired in rawhide. Thanks. > > > Pierre > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Pinging spin or labs maintainers in failed composes tickets
Sorry for the late reply, compose-tracker uses the toml file https://pagure.io/releng/compose-tracker/blob/master/f/compose_tracker.py#_151 And the PR is merged and it should work. On Mon, May 11, 2020 at 1:19 PM Miro Hrončok wrote: > > On 11. 05. 20 18:23, Ankur Sinha wrote: > > On Mon, May 11, 2020 17:34:57 +0200, Miro Hrončok wrote: > >> On 11. 05. 20 16:48, Ankur Sinha wrote: > >> Thanks. > >> > >> https://koji.fedoraproject.org/koji/packageinfo?packageID=23843 says > >> "Fedora-Python-Classroom-Live" > >> > >> kickstarts have: > >> > >> fedora-arm-python-classroom.ks > >> fedora-live-python-classroom.ks > >> fedora-python-classroom-common.ks > >> fedora-python-classroom-gnome-common.ks > >> fedora-python-classroom-vagrant.ks > >> > >> So this does not really help me :( > > > > The complete name is a "pretty name", defined here: > > https://pagure.io/pungi-fedora/blob/master/f/fedora.conf#_623 > > > > The main file that is used for the image is > > `fedora-live-python-classroom.ks`. It'll include the other ones: > > https://pagure.io/fedora-kickstarts/blob/master/f/fedora-live-python-classroom.ks > > > > Perhaps best to open a PR using "python-classroom.x86_64" and let releng > > correct it if needed when they review it? > > https://pagure.io/fedora-kickstarts/pull-request/641 > > > (I looked around, but couldn't find the script that uses the toml file. > > That would've told us exactly what needs to be used) > > Thanks for looking. > > -- > Miro Hrončok > -- > Phone: +420777974800 > IRC: mhroncok > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Previous awesome background images
My personal favorite is Fedora 26 https://fedoraproject.org/wiki/Wallpapers#Fedora_26 I am not an artist, but the silhouette of the calming woods with the reflection it on the lake is just *serene*. On Fri, Apr 17, 2020 at 5:44 PM Miro Hrončok wrote: > > On 17. 04. 20 16:07, Kamil Paral wrote: > > I'm disappointed with default wallpapers in the latest releases. I wonder > > if we > > could go back to more artistic images from previous releases? Here are some > > of > > my favorite ones: > > https://fedoraproject.org/wiki/Wallpapers#Fedora_29 > > https://fedoraproject.org/wiki/Wallpapers#Fedora_27 > > https://fedoraproject.org/wiki/Wallpapers#Fedora_21 > > https://fedoraproject.org/wiki/Wallpapers#Fedora_16 > > https://fedoraproject.org/wiki/Wallpapers#Fedora_15 > > https://fedoraproject.org/wiki/Wallpapers#Fedora_11 > > https://fedoraproject.org/wiki/Wallpapers#Fedora_7 > > > > Especially the one in Fedora 15 (GNOME edition) and 16 was outstanding. Can > > we > > do more of those, please? > > I love both the design and concept of the F25-F28 wallpapers. > > "As of the past 3 releases, we choose a sequential letter of the alphabet and > come up with a list of scientists / mathematicians / technologists to serve as > an inspiration for the desktop background’s visual concept" > > https://blog.linuxgrrl.com/2018/03/06/fedora-28s-desktop-background-design/ > > I am sad we haven't followed the pattern. (However I don't know the reasoning > for stopping that.) > > (I've changed the subject line, because I don't want to participate in what > was > in there.) > > -- > Miro Hrončok > -- > Phone: +420777974800 > IRC: mhroncok > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Rawhide update from side tag pending for 2 days
On Tue, Apr 7, 2020 at 8:34 AM Fabio Valentini wrote: > > On Tue, Apr 7, 2020 at 8:56 AM Richard W.M. Jones wrote: > > > > > > https://bodhi.fedoraproject.org/updates/FEDORA-2020-d120de33c5 > > > > This one is a Rawhide update from a side tag, submitted on Sunday > > morning which has been in pending for 2 days. (As it's Rawhide it's > > supposed to spend 0 days in testing.) Is there any problem with it, > > or do we just have to wait longer? It is blocking builds of other > > packages. > > Yeah, this update looks stuck ... the koji builds aren't even tagged > into the right tags yet, neither are they signed (from what I can > see). > > I seem to have the same - or at least a similar - issue with three > updates that are also stuck in pending for two days already (and the > builds are not even signed yet, either): > > - https://bodhi.fedoraproject.org/updates/FEDORA-2020-460f0f4d48 > - https://bodhi.fedoraproject.org/updates/FEDORA-2020-6ea279079e > - https://bodhi.fedoraproject.org/updates/FEDORA-2020-755f442b4c This is a different case, can you file a ticket at https://pagure.io/releng/new_issue. I am guessing this is caused by the recent release of enabling side tags in now rawhide releases. > > Those three were also made from side tags, but for stable releases, so > I'm not sure whether it's the same issue or not. > > Fabio > > > Rich. > > > > -- > > Richard Jones, Virtualization Group, Red Hat > > http://people.redhat.com/~rjones > > Read my programming and virtualization blog: http://rwmj.wordpress.com > > virt-df lists disk usage of guests without needing to install any > > software inside the virtual machine. Supports Linux and Windows. > > http://people.redhat.com/~rjones/virt-df/ > > ___ > > devel mailing list -- devel@lists.fedoraproject.org > > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > > Fedora Code of Conduct: > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > > List Archives: > > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Rawhide update from side tag pending for 2 days
I guess it should be a fixed in bodhi. But for now you can remove the builds that it's complaining about in the update. https://github.com/fedora-infra/bodhi/issues/3991 On Tue, Apr 7, 2020 at 2:56 AM Richard W.M. Jones wrote: > > > https://bodhi.fedoraproject.org/updates/FEDORA-2020-d120de33c5 > > This one is a Rawhide update from a side tag, submitted on Sunday > morning which has been in pending for 2 days. (As it's Rawhide it's > supposed to spend 0 days in testing.) Is there any problem with it, > or do we just have to wait longer? It is blocking builds of other > packages. > > Rich. > > -- > Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones > Read my programming and virtualization blog: http://rwmj.wordpress.com > virt-df lists disk usage of guests without needing to install any > software inside the virtual machine. Supports Linux and Windows. > http://people.redhat.com/~rjones/virt-df/ > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Rawhide update from side tag pending for 2 days
On Tue, Apr 7, 2020 at 8:57 AM Rex Dieter wrote: > > Richard W.M. Jones wrote: > > > > > https://bodhi.fedoraproject.org/updates/FEDORA-2020-d120de33c5 > > > > This one is a Rawhide update from a side tag, submitted on Sunday > > morning which has been in pending for 2 days. (As it's Rawhide it's > > supposed to spend 0 days in testing.) Is there any problem with it, > > or do we just have to wait longer? It is blocking builds of other > > packages. > > I saw the same thing, and submitted a infra ticket about it, > https://pagure.io/fedora-infrastructure/issue/8819 In https://bodhi.fedoraproject.org/updates/FEDORA-2020-641e69f08c, I can see that qt-creator-4.12.0-0.3.rc1.fc33 is the latest version and the latest build compared to the qt-creator-4.12.0-0.2.beta1.fc33 build in the update. You can remove the build from the update to move it to stable. > > -- Rex > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Replace buildroot overrides with user side tags?
This is a great idea, but I wouldn't recommend removing buildroot overrides totally for one more reason than the others that are already mentioned here. Side tags are resource intensive compared to buildroot override as each side tag needs its own buildroot. On Sat, Apr 4, 2020 at 5:02 PM Richard Shaw wrote: > > On Sat, Apr 4, 2020 at 3:52 PM Neal Gompa wrote: >> >> On Sat, Apr 4, 2020 at 4:50 PM Richard Shaw wrote: >> > >> > To be clear, I've only used them for rawhide, but can they be used in >> > other branches? >> > >> >> As of last Monday, yes. There are still some quirks to iron out, though... > > > Awesome! Not only are they easier to use but being able to choose the side > tag in the Bodhi web interface makes pushing the updates painless! > > Thanks, > Richard > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: koji wait-repo (newRepo) is really taking a long time
Things should be getting better now https://pagure.io/koji/issue/2119#comment-640757 On Sat, Apr 4, 2020 at 5:13 AM Richard W.M. Jones wrote: > > On Sat, Apr 04, 2020 at 12:42:29AM +0200, Miro Hrončok wrote: > > On 03. 04. 20 13:03, Richard W.M. Jones wrote: > > > > > >I've been waiting on: > > > > > >$ koji wait-repo f33-build-side-20855 --build=ocaml-lacaml-9.3.2-17.fc33 > > > > > >for hours now. Seems like newRepo generation is again taking a very > > >long time? > > > > > >Also it'd be nice if this command didn't time out after 2 hours > > >(seems like a very odd and arbitrary choice - why not wait forever?) > > >and also coped with transient network failures. > > > > For timeout, there is: > > > > --timeout=TIMEOUT Amount of time to wait (in minutes) before giving up > > (default: 120) > > > > For network issues, I've been using: > > > > while ! koji wait-repo ...; do sleep 15; done > > > > ...quite successfully. > > Thanks, hopefully with this change it'll be more robust: > > http://git.annexia.org/?p=goals.git;a=commitdiff;h=cda1f0160b96e57a0037085f33aa2d440453a30b > > Rich. > > -- > Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones > Read my programming and virtualization blog: http://rwmj.wordpress.com > virt-df lists disk usage of guests without needing to install any > software inside the virtual machine. Supports Linux and Windows. > http://people.redhat.com/~rjones/virt-df/ > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32 Final Freeze
Hi all, It is just now decided by FESCO to postpone the freeze by 2 days due to issues with bodhi and koji, that means, the freeze will start on Thursday, April 09 2020 at 14:00 UTC. For more information, please look at https://pagure.io/fesco/issue/2369 On Mon, Apr 6, 2020 at 9:36 AM Mohan Boddu wrote: > > Hi all, > > Tomorrow, April 7th 2020, is an important day on the Fedora 32 > schedule [1], with significant cut-offs. > > Tomorrow we have the Final Freeze [2] which starts at 14:00 UTC. > This means that only packages which fix accepted blocker or freeze > exception bugs [3][4][5] will be marked as 'stable' and included in the > Final composes. Other builds will remain in updates-testing until the > Final release is approved, at which point the Final freeze is lifted and > packages can move to the 'updates' repository, pending updates will > be pushed before final release as zero day updates. > > [1] https://fedorapeople.org/groups/schedule/f-32/f-32-key-tasks.html > [2] https://fedoraproject.org/wiki/Milestone_freezes > [3] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process > [4] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process > [5] https://qa.fedoraproject.org/blockerbugs/milestone/31/final/buglist Correcting the url: [5] https://qa.fedoraproject.org/blockerbugs/milestone/32/final/buglist > > Regards, > Mohan Boddu > Release Engineering ___ devel-announce mailing list -- devel-annou...@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32 Final Freeze
Hi all, It is just now decided by FESCO to postpone the freeze by 2 days due to issues with bodhi and koji, that means, the freeze will start on Thursday, April 09 2020 at 14:00 UTC. For more information, please look at https://pagure.io/fesco/issue/2369 On Mon, Apr 6, 2020 at 9:36 AM Mohan Boddu wrote: > > Hi all, > > Tomorrow, April 7th 2020, is an important day on the Fedora 32 > schedule [1], with significant cut-offs. > > Tomorrow we have the Final Freeze [2] which starts at 14:00 UTC. > This means that only packages which fix accepted blocker or freeze > exception bugs [3][4][5] will be marked as 'stable' and included in the > Final composes. Other builds will remain in updates-testing until the > Final release is approved, at which point the Final freeze is lifted and > packages can move to the 'updates' repository, pending updates will > be pushed before final release as zero day updates. > > [1] https://fedorapeople.org/groups/schedule/f-32/f-32-key-tasks.html > [2] https://fedoraproject.org/wiki/Milestone_freezes > [3] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process > [4] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process > [5] https://qa.fedoraproject.org/blockerbugs/milestone/31/final/buglist Correcting the url: [5] https://qa.fedoraproject.org/blockerbugs/milestone/32/final/buglist > > Regards, > Mohan Boddu > Release Engineering ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Fedora 32 Final Freeze
Hi all, Tomorrow, April 7th 2020, is an important day on the Fedora 32 schedule [1], with significant cut-offs. Tomorrow we have the Final Freeze [2] which starts at 14:00 UTC. This means that only packages which fix accepted blocker or freeze exception bugs [3][4][5] will be marked as 'stable' and included in the Final composes. Other builds will remain in updates-testing until the Final release is approved, at which point the Final freeze is lifted and packages can move to the 'updates' repository, pending updates will be pushed before final release as zero day updates. [1] https://fedorapeople.org/groups/schedule/f-32/f-32-key-tasks.html [2] https://fedoraproject.org/wiki/Milestone_freezes [3] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process [4] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process [5] https://qa.fedoraproject.org/blockerbugs/milestone/31/final/buglist Regards, Mohan Boddu Release Engineering ___ devel-announce mailing list -- devel-annou...@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora 32 Final Freeze
Hi all, Tomorrow, April 7th 2020, is an important day on the Fedora 32 schedule [1], with significant cut-offs. Tomorrow we have the Final Freeze [2] which starts at 14:00 UTC. This means that only packages which fix accepted blocker or freeze exception bugs [3][4][5] will be marked as 'stable' and included in the Final composes. Other builds will remain in updates-testing until the Final release is approved, at which point the Final freeze is lifted and packages can move to the 'updates' repository, pending updates will be pushed before final release as zero day updates. [1] https://fedorapeople.org/groups/schedule/f-32/f-32-key-tasks.html [2] https://fedoraproject.org/wiki/Milestone_freezes [3] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process [4] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process [5] https://qa.fedoraproject.org/blockerbugs/milestone/31/final/buglist Regards, Mohan Boddu Release Engineering ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Pinging spin or labs maintainers in failed composes tickets
Hi all, As discussed in the spins list [1], we are adding the ability to ping maintainers of spins or labs in compose failure tickets [2]. I made a list of maintainers [3] from the existing kickstart files, please create PR's to fedora-kickstarts repo [4] if any changes are needed to the list. We are hoping that it will be very helpful to all the spins, labs and any other variant maintainers to get notified if they image build failed and provides an easy way to find and debug the issue. Thanks, Mohan Boddu Fedora Release Engineering. [1] https://lists.fedoraproject.org/archives/list/sp...@lists.fedoraproject.org/thread/K5VFSTEBBQUGNBFPBDTEQJ6HWESTLMWG/ [2] https://pagure.io/releng/failed-composes/issues [3] https://pagure.io/fedora-kickstarts/blob/master/f/maintainers.toml [4] https://pagure.io/fedora-kickstarts/ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Emerging editions, Fedora 32 Beta, and bureaucracy
On Wed, Mar 18, 2020 at 6:38 AM Kamil Paral wrote: > > On Tue, Mar 17, 2020 at 10:11 PM Mohan Boddu wrote: >> >> Peter and I talked about it a while ago about merging IoT into regular >> Fedora composes. But we never got to that point. I am not sure whats >> their plan moving forward. My idea is to merge them together and keep >> their composes as it is for their testing. > > > Hey Mohan! > If IoT folks don't reply to this particular issue in a few days, can we > simply assume merging the composes is the best way forward for everyone and > just do it? :) I see only benefits. > This all seems like a communication issue to me, nobody wants to kick the > ball and move things forward, and everyone else is stalled. > Thanks! I don't think that's the right way to do it, we should let the community know (esp who are following IoT closely) about what's happening so that they won't be confused with two IoT related composes and also let them know which one to follow for what use cases. But if it comes to that, I would need the permission from FESCo to do so and an announcement sent out that we merging them. FYI, my job is very simple to merge them, just add https://pagure.io/fedora-iot/pungi-iot/blob/master/f/fedora-iot.conf#_209-339 to the nightly pungi config and need to change some sync scripts to add IoT variant. > > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Emerging editions, Fedora 32 Beta, and bureaucracy
Thanks Adam for bringing this up, I don't want to give big explanations on the topics, but I just want to mention a few things here: On Tue, Mar 17, 2020 at 2:01 PM Adam Williamson wrote: > > So, today is the Fedora 32 Beta release date. If you examine the > release announcement: > > https://fedoramagazine.org/announcing-the-release-of-fedora-32-beta/ > > and the current state of the download site: > > https://getfedora.org/ > > there are three fairly significant things entirely missing. Those three > things are the things that getfedora.org calls our 'Emerging Fedora > Editions' - the things that are allegedly the 'future of Fedora': IoT, > CoreOS and Silverblue. > > This is approximately how I currently understand things regarding those > editions: > > 1) Silverblue - this is kind of the simplest. Silverblue is built as > part of the regular Fedora composes. Silverblue image builds failed in > the actual Beta compose, which was unfortunate but not release-blocking > as SB is not yet tagged release-blocking, so the Beta we signed off has > no SB images. At the go/no-go and readiness meetings, IIRC, we agreed a > rough plan that we would nominate images from a nightly compose built > after the packages in Beta had been pushed stable to release alongside > the Beta. > https://kojipkgs.fedoraproject.org/compose/branched/Fedora-32-20200314.n.0/compose/Silverblue/ > should work fine for that purpose, but it seems not everything > necessary to actually get that plan implemented has happened, at least > not yet - I see no mention of this in the release announcement or on > getfedora.org . I uploaded the Silverblue nigthly to https://dl.fedoraproject.org/pub/alt/unofficial/releases/32/test/ where we store our "unofficial" releases. But that doesn't mean its pointed on getfedora.org, someone has to manually update it in websites and we have currently 0 resources working on websites. relrod is just helping us out on that. > > 2) IoT - as I've been trying to annoy people about for a few weeks now, > IoT is not built as part of our main 'Fedora' composes: > https://pagure.io/fedora-iot/issue/24 > this is a significant difference from just about everything else in > Fedora. We have several of these kinda 'variant' composes, but the > others are only used to do nightly builds of specific images for stable > releases *after* the release happens. For Rawhide and Branched > releases, those images are built in the main 'Fedora' compose. IoT is > the first and only thing (aside from CoreOS...which we'll get to in a > minute) which is being built outside of the 'Fedora' compose for > Branched and Rawhide. This means we don't have IoT images in the Beta > compose or indeed in any of the main Fedora 32 Branched composes and it > falls effectively entirely outside the existing processes for testing > and releasing stuff. That wouldn't be a problem if IoT were some > unimportant thing we didn't care about, but that doesn't seem to be the > case. It also wouldn't be a problem if this had all been figured out > ahead of time and a plan had been put in place for how exactly we were > going to validate and ship IoT releases, but that doesn't seem to have > been the case either. I keep filing tickets and bugging people and > there have been some back channel discussions and things, and a few of > us as individuals are making up a validation process as we go along as > best as we can, but there doesn't seem to be anything on paper aside > from > https://docs.fedoraproject.org/en-US/iot/edition-promotion/ , which > doesn't really address QA and release process stuff much and seems to > be rather old. As far as F32 Beta goes, again we roughly decided at > Go/No-Go and readiness to identify a specific compose that 'matched' > Beta and ship the bits from that - > https://kojipkgs.fedoraproject.org/compose/iot/Fedora-IoT-32-20200314.0/compose/IoT/ > would seem to fit the bill, and pwhalen has done validation testing on > it at > https://fedoraproject.org/wiki/User:Pwhalen/QA/IoT/Fedora-IoT-32-20200314.0 , > but again this plan doesn't seem to have got as far as getfedora.org or > the Beta release announcement. Peter and I talked about it a while ago about merging IoT into regular Fedora composes. But we never got to that point. I am not sure whats their plan moving forward. My idea is to merge them together and keep their composes as it is for their testing. > > 3) CoreOS - CoreOS is just a *whole* other thing. It is not built like > the rest of Fedora at all. It's not built as Pungi composes, whatever > compose process it does have doesn't run alongside our other compose > processes or output to the same locations, it's like a whole other > product. It also doesn't seem to be terribly well documented (I can't > find any detail on the wiki, docs sites, or any of the git repos I > happen to know of) or even introspectable - for instance, ISO locations > look like >
Re: Clang/LLVM mismatch in F32?
A short history of why it happened, when we lift the freeze, we check if all the packages that are in the stable tag are the latest builds, if not, we tag the latest builds into koji stable tag. We do this because, bodhi doesn't follow the latest build order while pushing updates, so, an older version gets tagged after the newer version if both updates are stuck during freeze. In this case, the nvr comparison failed since the release of rc1 is higher than the release of rc2. Anyway, this should be fixed now. On Tue, Mar 17, 2020 at 8:27 AM Michael Cronenworth wrote: > > On 3/17/20 7:00 AM, Frantisek Zatloukal wrote: > > > > I am trying to rebuild mozjs68 in F32[0] (passed in rawhide just fine[1]), > > which > > buildrequires clang and llvm. However, clang and llvm versions mismatch in > > F32 > > buildroot: > > > > clang x86_64 10.0.0-0.2.*rc1*.fc32 > > llvmx86_64 10.0.0-0.1.*rc2*.fc32 > > > > which seems to cause errors like: > > DEBUG: | /usr/bin/clang: symbol lookup error: /lib64/libclang-cpp.so.10: > > undefined > > symbol: _ZN4llvm20CrashRecoveryContext11HandleCrashEv, version LLVM_10 > > > > What is weird is that clang-10.0.0-0.1.rc2.fc32 is in F32 stable updates > > for some > > time already: https://bodhi.fedoraproject.org/updates/FEDORA-2020-7e1fca99b6 > > > > Can anybody help me with this? Or should I wait for freeze lift later today? > > I suspect you're seeing the same issue I am trying to build wine for F32. > > https://bugzilla.redhat.com/show_bug.cgi?id=1814105 > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora 32 Beta Release Announcement
Fedora 32 Beta Released -- The Fedora Project is pleased to announce the immediate availability of Fedora 32 Beta, the next step towards our planned Fedora 32 release at the end of April. Download the prerelease from our Get Fedora site: * Get Fedora 32 Beta Workstation: https://getfedora.org/workstation/download/ * Get Fedora 32 Beta Server: https://getfedora.org/server/download/ Or, check out one of our popular variants, including KDE Plasma, Xfce, and other desktop environments, as well as images for ARM devices like the Raspberry Pi 2 and 3: * Get Fedora 32 Beta Spins: https://spins.fedoraproject.org/prerelease * Get Fedora 32 Beta Labs: https://labs.fedoraproject.org/prerelease * Get Fedora 32 Beta ARM: https://arm.fedoraproject.org/prerelease ## Beta Release Highlights * New in Fedora 32 Workstation Beta is EarlyOOM enabled by default. * Fedora 32 Workstation Beta also enables the fs.trim timer by default. * Fedora 32 Workstation Beta includes GNOME 3.3.6. * And more ... For more details about the release, read the full announcement at * https://fedoramagazine.org/announcing-the-release-of-fedora-32-beta/ or look for the prerelease pages in the download sections at * https://getfedora.org/ Since this is a Beta release, we expect that you may encounter bugs or missing features. To report issues encountered during testing, contact the Fedora QA team via the mailing list or in #fedora-qa on Freenode. Regards, Mohan Boddu Fedora Release Engineering. ___ devel-announce mailing list -- devel-annou...@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora 32 Beta Release Announcement
Fedora 32 Beta Released -- The Fedora Project is pleased to announce the immediate availability of Fedora 32 Beta, the next step towards our planned Fedora 32 release at the end of April. Download the prerelease from our Get Fedora site: * Get Fedora 32 Beta Workstation: https://getfedora.org/workstation/download/ * Get Fedora 32 Beta Server: https://getfedora.org/server/download/ Or, check out one of our popular variants, including KDE Plasma, Xfce, and other desktop environments, as well as images for ARM devices like the Raspberry Pi 2 and 3: * Get Fedora 32 Beta Spins: https://spins.fedoraproject.org/prerelease * Get Fedora 32 Beta Labs: https://labs.fedoraproject.org/prerelease * Get Fedora 32 Beta ARM: https://arm.fedoraproject.org/prerelease ## Beta Release Highlights * New in Fedora 32 Workstation Beta is EarlyOOM enabled by default. * Fedora 32 Workstation Beta also enables the fs.trim timer by default. * Fedora 32 Workstation Beta includes GNOME 3.3.6. * And more ... For more details about the release, read the full announcement at * https://fedoramagazine.org/announcing-the-release-of-fedora-32-beta/ or look for the prerelease pages in the download sections at * https://getfedora.org/ Since this is a Beta release, we expect that you may encounter bugs or missing features. To report issues encountered during testing, contact the Fedora QA team via the mailing list or in #fedora-qa on Freenode. Regards, Mohan Boddu Fedora Release Engineering. ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Re: Can not build new package: not in list for tag f33-updates-candidate
This should be fixed now, can you give it a try? On Thu, Feb 27, 2020 at 10:54 AM Alejandro Álvarez Ayllón wrote: > > Hello all, > > I am trying to build sourcextractor++, which was accepted yesterday, and > every time I try I get the following error: > > BuildError: package sourcextractor++ not in list for tag f33-updates-candidate > > https://koji.fedoraproject.org/koji/taskinfo?taskID=41969086 > > I have seen some packages that were accepted at the same time, or even after, > already built. And since I have two trailing '+' on the package name, I was > wondering if this could have caused some kind of issue. > > Any hints? > > > -- > Alejandro > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora 32 Beta Freeze
Hi all, Today's an important day on the Fedora 32 schedule[1], with several significant cut-offs. First of all today is the Bodhi activation point [2]. That means that from now on all Fedora 32 packages must be submitted to updates-testing and pass the relevant requirements[3] before they will be marked as 'stable' and moved to the fedora repository. Today is also the Beta freeze[4]. This means that only packages which fix accepted blocker or freeze exception bugs[5][6] will be marked as 'stable' and included in the Beta composes. Other builds will remain in updates-testing until the Beta release is approved, at which point the Beta freeze is lifted and packages can move to 'stable' as usual until the Final freeze. Finally, today is the '100% code complete deadline' Change Checkpoint[5], meaning that Fedora 32 Changes must now be code complete, meaning all the code required to enable the new change is finished. The level of code completeness is reflected as tracker bug state ON_QA. The change does not have to be fully tested by this deadline'. Finally, today is also the Software String freeze[7], which means that strings marked for translation in Fedora-translated projects should not now be changed for Fedora 32. Mohan Boddu [1] https://fedorapeople.org/groups/schedule/f-32/f-32-key-tasks.html [2] https://fedoraproject.org/wiki/Updates_Policy#Bodhi_enabling [3] https://fedoraproject.org/wiki/Updates_Policy#Branched_release [4] https://fedoraproject.org/wiki/Milestone_freezes [5] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process [6] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process [7] https://fedoraproject.org/wiki/ReleaseEngineering/StringFreezePolicy ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
[Test-Announce] Fedora 32 Beta Freeze
Hi all, Today's an important day on the Fedora 32 schedule[1], with several significant cut-offs. First of all today is the Bodhi activation point [2]. That means that from now on all Fedora 32 packages must be submitted to updates-testing and pass the relevant requirements[3] before they will be marked as 'stable' and moved to the fedora repository. Today is also the Beta freeze[4]. This means that only packages which fix accepted blocker or freeze exception bugs[5][6] will be marked as 'stable' and included in the Beta composes. Other builds will remain in updates-testing until the Beta release is approved, at which point the Beta freeze is lifted and packages can move to 'stable' as usual until the Final freeze. Finally, today is the '100% code complete deadline' Change Checkpoint[5], meaning that Fedora 32 Changes must now be code complete, meaning all the code required to enable the new change is finished. The level of code completeness is reflected as tracker bug state ON_QA. The change does not have to be fully tested by this deadline'. Finally, today is also the Software String freeze[7], which means that strings marked for translation in Fedora-translated projects should not now be changed for Fedora 32. Mohan Boddu [1] https://fedorapeople.org/groups/schedule/f-32/f-32-key-tasks.html [2] https://fedoraproject.org/wiki/Updates_Policy#Bodhi_enabling [3] https://fedoraproject.org/wiki/Updates_Policy#Branched_release [4] https://fedoraproject.org/wiki/Milestone_freezes [5] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process [6] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process [7] https://fedoraproject.org/wiki/ReleaseEngineering/StringFreezePolicy ___ test-announce mailing list -- test-annou...@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: New Release Freeze Times
We didn't pick the time at random, 14:00 UTC is the time when Fedora release gets out. We thought if we are changing the time, we should align it with the only other time constrained task, that is, Fedora release. 00:00 UTC is definitely confusing for some people as they complained about it, but 14:00 UTC should not make it anymore confusing. Also, as a side note, people will get 14 more hours to get their stuff into the release before the freeze starts, that should help the maintainers as well. On Sat, Feb 22, 2020 at 10:51 AM Neal Gompa wrote: > > On Sat, Feb 22, 2020 at 7:58 AM Kevin Kofler wrote: > > > > Neal Gompa wrote: > > > 14:00 UTC is 9:00 EST, so it basically means to everyone: do > > > everything the day before. > > > > "Do everything the day before" is exactly what was confusing about the 00:00 > > UTC deadline, so I do not see how the change to 14:00 UTC fixes the issue. > > It is customary to give inclusive deadlines, i.e., a deadline of day X means > > I have up to AND INCLUDING day X to do the work. > > > > I do not see why the deadlines were not changed to 23:59 UTC deadlines > > instead, which would also not have meant any actual change in process > > (unlike this 14:00 UTC change), just a change of how the deadlines are > > announced (subtract 1 day from all the posted deadlines). > > > > The folks that actually are doing this work are also based on US > Eastern Time, specifically out in the Boston, MA area. It is much > easier for them to pull this off by saying "welp, it's the start of > the day for me and this is the day we push the button, so let's push > it!". Previously they had to do it technically *after* the end of *the > previous day* their time, which made things confusing. > > > -- > 真実はいつも一つ！/ Always, there's only one truth! > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
New Release Freeze Times
Hi all, It has been brought to our attention that release freezes starting at 00:00 UTC has been confusing for a lot of people. So, we decided to change it to 14:00 UTC. The freeze dates are not going to change, just the time when freeze starts is going to change. Fedora 32 schedule [1] has been updated to reflect the changed time. [1] https://fedorapeople.org/groups/schedule/f-32/f-32-key-tasks.html Thanks, Mohan Boddu. ___ devel-announce mailing list -- devel-annou...@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
