Intent to start ARC investigation git-forge replacement
Hello, Fedora community, Following on from the Fedora Council's decision to investigate Forgejo and GitLab as potential replacements[1], the Community Platform Engineering team will start an ARC[2] investigation to compare proposed alternatives for current pagure use cases. The council has defined some broad requirements for the team to consider during this investigation. But we would like inputs from all gitforge user groups in our community. So, if you have a specific use case or workflow, share it with us in the form of a user story in this ticket[6], or consider joining the ARC team for this investigation. High-level overview of investigation requirements by the council: 1. Suitability for dist-git and src.fedoraproject.org replacement 2. Suitability for replacement of Bugzilla for packaging issues and review process 3. Suitability for replacement of Pagure and Bugzilla for release issues (change process, blocker bugs, etc) * https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process * https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process 4. Suitability for replacement of Pagure for SIG and Team ticket tracking (e.g. FESCo tracker) 5. Cost of hosting and maintenance (hardware + time and resources from CPE and wider infrastructure team) 6. Ease of migration from current Pagure, GitHub, and GitLab 7. Ease of extension and enhancement — can we improve things ourselves to add missing features/features that are cool and useful like CI integration? 8. New features like Asciidoc support, Online editor, and others to make things easier for the Fedora teams and their workflows. 9. Estimate Future risk for Fedora project and Infrastructure team 1. Long-term project vision 2. Platform SMEs in the Fedora Infrastructure team and the wider community These requirements do not represent feature sets, but rather a high-level overview of our current use cases. CPE has already done some initial mapping of how our current applications interact with distgit[3] and if we have missed anything, please let folks know in a thread on discussions.fp.o[4]. The aim of this investigation will not be to pick one solution or the other, but instead, focus on providing the Fedora Council and decision makers[5] with an extensive comparison of the two. For discussion about the purpose of this investigation please use the discussions.fp.o thread[7] The ARC investigation will commence in early May. [1] - https://communityblog.fedoraproject.org/2024-git-forge-evaluation/ [2] - https://fedora-arc.readthedocs.io/en/latest/index.html [3] - https://fedora-arc.readthedocs.io/en/latest/dist-git-move/index.html#interactions [4] - https://discussion.fedoraproject.org/t/dist-git-decoupling-investigation/93644/10 [5] - https://pagure.io/Fedora-Council/tickets/issue/488 [6] - https://pagure.io/fedora-infra/arc/issue/164 [7] - https://discussion.fedoraproject.org/t/arc-git-forge-investigation/114018 Tomas Hrcka Cat herder at Community Platform Engineering team fas: humaton libera.CHAT: jednorozec matrix: @humaton:fedora.im -- ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue -- ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Intent to start ARC investigation git-forge replacement
Hello, Fedora community, Following on from the Fedora Council's decision to investigate Forgejo and GitLab as potential replacements[1], the Community Platform Engineering team will start an ARC[2] investigation to compare proposed alternatives for current pagure use cases. The council has defined some broad requirements for the team to consider during this investigation. But we would like inputs from all gitforge user groups in our community. So, if you have a specific use case or workflow, share it with us in the form of a user story in this ticket[6], or consider joining the ARC team for this investigation. High-level overview of investigation requirements by the council: 1. Suitability for dist-git and src.fedoraproject.org replacement 2. Suitability for replacement of Bugzilla for packaging issues and review process 3. Suitability for replacement of Pagure and Bugzilla for release issues (change process, blocker bugs, etc) * https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process * https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process 4. Suitability for replacement of Pagure for SIG and Team ticket tracking (e.g. FESCo tracker) 5. Cost of hosting and maintenance (hardware + time and resources from CPE and wider infrastructure team) 6. Ease of migration from current Pagure, GitHub, and GitLab 7. Ease of extension and enhancement — can we improve things ourselves to add missing features/features that are cool and useful like CI integration? 8. New features like Asciidoc support, Online editor, and others to make things easier for the Fedora teams and their workflows. 9. Estimate Future risk for Fedora project and Infrastructure team 1. Long-term project vision 2. Platform SMEs in the Fedora Infrastructure team and the wider community These requirements do not represent feature sets, but rather a high-level overview of our current use cases. CPE has already done some initial mapping of how our current applications interact with distgit[3] and if we have missed anything, please let folks know in a thread on discussions.fp.o[4]. The aim of this investigation will not be to pick one solution or the other, but instead, focus on providing the Fedora Council and decision makers[5] with an extensive comparison of the two. For discussion about the purpose of this investigation please use the discussions.fp.o thread[7] The ARC investigation will commence in early May. [1] - https://communityblog.fedoraproject.org/2024-git-forge-evaluation/ [2] - https://fedora-arc.readthedocs.io/en/latest/index.html [3] - https://fedora-arc.readthedocs.io/en/latest/dist-git-move/index.html#interactions [4] - https://discussion.fedoraproject.org/t/dist-git-decoupling-investigation/93644/10 [5] - https://pagure.io/Fedora-Council/tickets/issue/488 [6] - https://pagure.io/fedora-infra/arc/issue/164 [7] - https://discussion.fedoraproject.org/t/arc-git-forge-investigation/114018 Tomas Hrcka Cat herder at Community Platform Engineering team fas: humaton libera.CHAT: jednorozec matrix: @humaton:fedora.im -- ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Mass rebuild: git push --no-verify
On Tue, Jan 16, 2024 at 10:52 PM Jerry James wrote: > Given the problems we had with font packages not being rebuilt in the > last mass rebuild, can we ensure that the mass rebuild script uses > "git push --no-verify" instead of plain "git push"? > This is not a good idea. Because of a few packages that are not rebuilding we would disable the hook for every push the script does. > > See: > - https://bugzilla.redhat.com/show_bug.cgi?id=2233878 > - > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/7IIZPEC6B4BEOOOV5YFEUGOONNOH5LZO/ > -- > Jerry James > http://www.jamezone.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 > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > -- Tomas Hrcka fas: humaton libera.CHAT: jednorozec matrix: @humaton:fedora.im -- ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora Linux 37 is EOL
Hello all, Fedora Linux 37 has gone end of life for updates and support on 2023-12-05. No more updates of any kind, including security updates or security announcements, will be available for Fedora Linux 37 after the said date. All the updates of Fedora Linux 37 being pushed to stable will be stopped as well. Fedora Linux 38 will continue to receive updates until approximately one month after the release of Fedora Linux 40. The maintenance schedule of Fedora Linux releases is documented on the Fedora Project wiki [1]. The Fedora Project wiki also contains instructions[2] on how to upgrade from a previous release of Fedora Linux to a version receiving updates. This email template is also in https://pagure.io/releng if you wish to propose improvements or changes to it. Regards, Tomas Hrcka Fedora Release Engineering [1] - https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule [2] - https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades [3] - https://pagure.io/releng -- Tomas Hrcka fas: humaton libera.CHAT: jednorozec -- ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue -- ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora Linux 37 is EOL
Hello all, Fedora Linux 37 has gone end of life for updates and support on 2023-12-05. No more updates of any kind, including security updates or security announcements, will be available for Fedora Linux 37 after the said date. All the updates of Fedora Linux 37 being pushed to stable will be stopped as well. Fedora Linux 38 will continue to receive updates until approximately one month after the release of Fedora Linux 40. The maintenance schedule of Fedora Linux releases is documented on the Fedora Project wiki [1]. The Fedora Project wiki also contains instructions[2] on how to upgrade from a previous release of Fedora Linux to a version receiving updates. This email template is also in https://pagure.io/releng if you wish to propose improvements or changes to it. Regards, Tomas Hrcka Fedora Release Engineering [1] - https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule [2] - https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades [3] - https://pagure.io/releng -- Tomas Hrcka fas: humaton libera.CHAT: jednorozec -- ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora 37 End Of Life in one week
Hello all, Fedora Linux 37 will go end of life for updates and support on 2023-12-05. No more updates of any kind, including security updates or security announcements, will be available for Fedora Linux 37 after the said date. All the updates of Fedora Linux 37 being pushed to stable will also be stopped. Please ensure your builds will land in stable[3] updates in Bodhi before the EOL date. This email template is also in https://pagure.io/releng if you wish to propose improvements or changes to it. Regards, Fedora Release Engineering [1] https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule [2]https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades [3]https://bodhi.fedoraproject.org/updates/?releases=F37=stable -- Tomas Hrcka fas: humaton libera.CHAT: jednorozec @humaton:fedora.im -- ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue -- ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora 37 End Of Life in one week
Hello all, Fedora Linux 37 will go end of life for updates and support on 2023-12-05. No more updates of any kind, including security updates or security announcements, will be available for Fedora Linux 37 after the said date. All the updates of Fedora Linux 37 being pushed to stable will also be stopped. Please ensure your builds will land in stable[3] updates in Bodhi before the EOL date. This email template is also in https://pagure.io/releng if you wish to propose improvements or changes to it. Regards, Fedora Release Engineering [1] https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule [2]https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades [3]https://bodhi.fedoraproject.org/updates/?releases=F37=stable -- Tomas Hrcka fas: humaton libera.CHAT: jednorozec @humaton:fedora.im -- ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Bodhi API does not list f39 in pending releases
This looks like a bug in bodhi. the web UI lists correct releases pending and current. On Wed, Oct 25, 2023 at 11:57 AM Pavel Březina wrote: > > Hi, > Fedora 39 stopped showing in pending releases (and is not in current > either) when using: > > curl https://bodhi.fedoraproject.org/releases/?state=pending | jq > > There is Fedora 39 as flatpak and container, but not with id_prefix==FEDORA. > > Is this because it is now in final freeze or is it a bodhi bug? > > We rely on this information to automatically pick up fedora versions for > SSSD PR CI. > > Thanks. > Pavel > ___ > 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, report it: > https://pagure.io/fedora-infrastructure/new_issue -- Tomas Hrcka fas: humaton libera.CHAT: jednorozec ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora Linux 39 Final Freeze
Hi all, Today, 2023-10-03, is an important day on the Fedora Linux 39 schedule [1], with significant cut-offs. Today we have the Final Freeze [2] which starts at 14:00 UTC. This means that only packages that 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 the final release as zero day updates. Regards, Fedora Release Engineering [1] https://fedorapeople.org/groups/schedule/f-39/f-39-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/39/final/buglist -- Tomas Hrcka fas: humaton libera.CHAT: jednorozec ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora Linux 39 Final Freeze
Hi all, Today, 2023-10-03, is an important day on the Fedora Linux 39 schedule [1], with significant cut-offs. Today we have the Final Freeze [2] which starts at 14:00 UTC. This means that only packages that 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 the final release as zero day updates. Regards, Fedora Release Engineering [1] https://fedorapeople.org/groups/schedule/f-39/f-39-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/39/final/buglist -- Tomas Hrcka fas: humaton libera.CHAT: jednorozec ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora Linux 39 Beta Released
Fedora Linux 39 Beta Released -- The Fedora Project is pleased to announce the immediate availability of Fedora Linux 39 Beta, the next step towards our planned Fedora Linux 39 release at the end of October. Download the prerelease from our Get Fedora site: * Get Fedora Linux 39 Beta Workstation: https://getfedora.org/workstation/download/ * Get Fedora Linux 39 Beta Server: https://getfedora.org/server/download/ * Get Fedora Linux 39 Beta IoT: https://getfedora.org/iot/download/ * Get Fedora Linux 39 Beta CoreOS: https://fedoraproject.org/coreos/download/ * Get Fedora Linux 39 Beta Cloud: https://fedoraproject.org/cloud/download Or, check out one of our popular variants, including KDE Plasma, Xfce, and other desktop environments: * Get Fedora Linux 39 Beta Spins: https://spins.fedoraproject.org/prerelease * Get Fedora Linux 39 Beta Labs: https://labs.fedoraproject.org/prerelease For more details about the release, read the full announcement at * https://fedoramagazine.org/announcing-fedora-39-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 or the #qa:fedoraproject.org Matrix room. Regards, Tomas Hrcka Fedora Release Engineering -- Tomas Hrcka fas: humaton libera.CHAT: jednorozec ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora Linux 39 Beta Released
Fedora Linux 39 Beta Released -- The Fedora Project is pleased to announce the immediate availability of Fedora Linux 39 Beta, the next step towards our planned Fedora Linux 39 release at the end of October. Download the prerelease from our Get Fedora site: * Get Fedora Linux 39 Beta Workstation: https://getfedora.org/workstation/download/ * Get Fedora Linux 39 Beta Server: https://getfedora.org/server/download/ * Get Fedora Linux 39 Beta IoT: https://getfedora.org/iot/download/ * Get Fedora Linux 39 Beta CoreOS: https://fedoraproject.org/coreos/download/ * Get Fedora Linux 39 Beta Cloud: https://fedoraproject.org/cloud/download Or, check out one of our popular variants, including KDE Plasma, Xfce, and other desktop environments: * Get Fedora Linux 39 Beta Spins: https://spins.fedoraproject.org/prerelease * Get Fedora Linux 39 Beta Labs: https://labs.fedoraproject.org/prerelease For more details about the release, read the full announcement at * https://fedoramagazine.org/announcing-fedora-39-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 or the #qa:fedoraproject.org Matrix room. Regards, Tomas Hrcka Fedora Release Engineering -- Tomas Hrcka fas: humaton libera.CHAT: jednorozec ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: PDC replacement proposal
Ok, now we are on the same page.
On Wed, Sep 13, 2023 at 8:04 PM Adam Williamson
wrote:
> On Wed, 2023-09-13 at 16:49 +0200, Tomas Hrcka wrote:
> > I thought this was exactly the JSON blob we will implement, If you look
> at
> > the model of PDC
> >
> https://product-definition-center.github.io/product-definition-center/_images/overview.svg
> >
> > Those endpoints are covered by relations Release, Compose, RPM through
> some
> > others.
> > The PDC approach is more or less a normalized RDBMS model.
> > This should be replaceable by a much simpler denormalized approach and
> > create one entry for each compose with all the data in one place.
>
> That's missing the 'composes' endpoint use (#1 in my list below). Not
> sure if that's your fault or mine, sorry if I left it out of a previous
> list.
>
> Does your replacement plan cover the "previous_release" use case, where
> we need a list of all the composes for each release in the order they
> happened?
>
>
Yes idea was to have the compose_id as a document root since it is unique
for each compose.
something like this:
Fedora-Rawhide-20230913.n.0:{
compose_related_metadata:[metadata0:metadata,metadata1:metadata]
rpms:[nvr:other_rdata,nvr1:other_rdata1]
images:{Fedora-Sway-Live-x86_64-Rawhide-20230913.n.0.iso:"some metadata"}
}
If we store the data in the correct format for fedfind use case we can
minimize the number of operations that are needed compared to REST API.
I will start working on this on the 15th. My idea is to start with the data
format, Once that is sorted out.
Just a friendly reminder we will not drop PDC suddenly. The plan is to
implement the new solution and have it running in parallel with PDC for a
while,
Once we are sure everything is working we will start to sunset PDC.
> Thanks!
> --
> Adam Williamson (he/him/his)
> Fedora QA
> Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org
> https://www.happyassassin.net
>
>
>
> ___
> 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, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
--
Tomas Hrcka
fas: humaton
libera.CHAT: jednorozec
___
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, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: PDC replacement proposal
last tested compose and the > compose it's currently deciding whether to create a validation event > for: if it's been more than 3 days but less than 14 days since the last > event, it will create a new event *if* any important package's version > changed. >WORKAROUND: Looking back on the history of this, I don't think > anything's actually using it right now. There is an ugly alternative > version of this one, too, which scrapes dl.fedoraproject.org's HTML > output (told you it was ugly!). I initially replaced that version with > the PDC one for some compose types, but then ran into problems with > that, and ultimately decided to provide both side-by-side; I think > relvalconsumer is the only thing that actually uses this feature, and > it currently uses the ugly HTML scraping version, not the PDC version. > I probably meant to try and make it use the PDC version but never got > around to it. The ugly version is working okay in practice, so I > suppose the workaround here would just be to drop the pretty PDC > version and rely on HTML scraping forever (sob). > -- > Adam Williamson (he/him/his) > Fedora QA > Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org > https://www.happyassassin.net > ___ > infrastructure mailing list -- infrastruct...@lists.fedoraproject.org > To unsubscribe send an email to > infrastructure-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/infrastruct...@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > -- Tomas Hrcka fas: humaton libera.CHAT: jednorozec ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: PDC replacement proposal
Sorry for the confusion with work that is already done, We can drop the critpath thanks Adam! As it goes for EoL and package retirement we for the past few releases we are saving EOL date in bodhi. So getting EOL for specific release is not a problem once the release is out. For storing the orphaning reason and other potential metadata. We can store some of it in git in form of notes on branches not necessarily in pagure-disgit specific code-base. With toddlers i think the path is clear we need to use bodhi as a source of truth about releases. Similar work as on toddlers will need to be done on mdapi For the compose metadata we can store the the json blobs on fedorapeople for now and search for some stable place. On Wed, Sep 6, 2023 at 12:23 PM Pierre-Yves Chibon wrote: > On Tue, Sep 05, 2023 at 11:35:19AM -0700, Kevin Fenzi wrote: > > On Mon, Sep 04, 2023 at 04:51:22PM +0200, Tomas Hrcka wrote: > > > Hello all, it took us a few years but we are finally getting rid of > the PDC > > > project. Thanks to the ARC research we identified use cases in our > tooling > > > and proposed solution. > > > > > > The essential functionalities currently provided by PDC will be > > > re-implemented in other applications within our release > infrastructure, as > > > there are no immediate plans for their replacement and are currently > > > maintained > > > > > > This work is anticipated to span several months for completion. > However, > > > before we embark on this endeavor, > > > > > > we would like to proactively share our proposed solution with all of > you > > > and gather your valuable feedback. > > > > > > Below, we outline our strategy to preserve the core functionality of > PDC by > > > leveraging existing applications within our ecosystem. > > > > > > Current uses of PDC: > > > > > > Currently, we rely on the Package Database (PDC) for various data > > > management tasks, including: > > > > > > > > >1. > > > > > >Critical Path Package Tracking: Bodhi leverages PDC to track > packages on > > >the critical path. > > > > As Adam mentioned this is already not in pdc. ;) > > > > >2. > > > > > >Retirement of Packages and Service Level Agreements (SLAs): PDC > assists > > >in managing the retirement of packages and their associated SLAs. > > > > Yeah. The super big one is that its queried from a git commit hook for > > all src.fedoraproject.org git commits. Right now if pdc is down, no one > > could commit anything. > > > > > > >3. > > > > > >Metadata for Nightly Composes: Our Release Engineering and Fedora > > >Quality Assurance teams rely on PDC for metadata related to nightly > > >composes. > > > > > > > > > More info on the usage can be found here: > > > https://fedora-arc.readthedocs.io/en/latest/pdc/users.html > > > > mass rebuild of modules can be dropped. ;) > > > > fedscm-admin is now the scm requests toddler. It still uses pdc tho > > of course. > > > > > Specific Endpoints in Use: > > > > ...snip... > > > > > Upcoming Changes > > > > > > Bodhi: > > > > > > Bodhi will assume responsibility for the following tasks, reducing our > > > reliance on PDC: > > > > > > /rest_api/v1/releases/: Bodhi will now manage release-related data. > > > > Do note that bodhi still has a window after we are 'go' for a relase > > where it thinks it's released, but it's not yet. We probibly need to > > address this if we are moving this to bodhi. > > > > > /rest_api/v1/component-branches/: Specifically, Bodhi will handle the > > > critical-path flag. > > > > Already done. > > > > ...snip... > > > > > > Pagure-dist-git: > > > > > > Pagure-dist-git will take over several responsibilities from PDC, > including: > > > > > > /rest_api/v1/product-versions > > > > > > /rest_api/v1/global-components > > > > > > /rest_api/v1/component-branches/ > > > > > > /rest_api/v1/component-branch-slas/ > > > > > > Pagure already has a robust database of global components > (repositories) > > > and product versions (repository branches). > > > > > > It utilizes the PDC API to query component branches when a package is > > > retired, and an auxiliary table in Pagure-dist-git will store the
PDC replacement proposal
is project in approximately two weeks. If you have any feedback regarding the proposed solution to facilitate the decommissioning of PDC or if you have any questions or require additional information, please don't hesitate to get in touch with us. Your input and inquiries are greatly appreciated. -- Tomas Hrcka fas: humaton libera.CHAT: jednorozec ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora Linux 39 Bodhi updates-testing activation & Beta freeze
Hi all, Today's an important day on the Fedora Linux 39 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 Linux 39 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 Linux 39. Finally, today is the 'completion deadline' Change Checkpoint [8], meaning that Fedora Linux 39 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, Tomas Hrcka Fedora Release Engineering [1] https://fedorapeople.org/groups/schedule/f-39/f-39-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, report it: https://pagure.io/fedora-infrastructure/new_issue ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora Linux 39 Bodhi updates-testing activation & Beta freeze
Hi all, Today's an important day on the Fedora Linux 39 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 Linux 39 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 Linux 39. Finally, today is the 'completion deadline' Change Checkpoint [8], meaning that Fedora Linux 39 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, Tomas Hrcka Fedora Release Engineering [1] https://fedorapeople.org/groups/schedule/f-39/f-39-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, report it: https://pagure.io/fedora-infrastructure/new_issue
Disabling rawhide builds during branching - happening in 2hrs
Hi All, Fedora Linux 39 is going to be branched in the upcoming hours as per the previous discussion[1] we are going to disable new koji builds for the duration of this event. All builds that will be running at that time for the rawhide will be canceled and can be resubmitted by maintainers after the branching. All rawhide updates that are in a pending state for rawhide will be unpushed. Once Fedora Linux 39 is branched we will reenable builds in koji with notification to this list. Tomas Hrcka Fedora Release Engineering @humaton:fedora.im 1 - https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/thread/GWY4TIDIP65HA2V33F2ROU2MJLKMRZ7E/#GWY4TIDIP65HA2V33F2ROU2MJLKMRZ7E -- Tomas Hrcka fas: humaton libera.CHAT: jednorozec ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Disabling rawhide builds during branching - happening in 2hrs
Hi All, Fedora Linux 39 is going to be branched in the upcoming hours as per the previous discussion[1] we are going to disable new koji builds for the duration of this event. All builds that will be running at that time for the rawhide will be canceled and can be resubmitted by maintainers after the branching. All rawhide updates that are in a pending state for rawhide will be unpushed. Once Fedora Linux 39 is branched we will reenable builds in koji with notification to this list. Tomas Hrcka Fedora Release Engineering @humaton:fedora.im 1 - https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/GWY4TIDIP65HA2V33F2ROU2MJLKMRZ7E/#GWY4TIDIP65HA2V33F2ROU2MJLKMRZ7E -- Tomas Hrcka fas: humaton libera.CHAT: jednorozec ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Disabling rawhide builds during branching
Hi, no we did not start the branching process yet, there are some issues on rawhide that need resolving. Once the issues are resolved and branching is good to go, I will send a new announcement about disabling rawhide builds. On Tue, Aug 8, 2023 at 2:46 PM Bob Mauchin wrote: > > > > On Mon, 7 Aug 2023, 23:19 Tomas Hrcka, wrote: >> >> Hi All, >> >> Fedora Linux 39 is going to be branched from rawhide on 2023-08-08 at 10:30 >> UTC >> as per the previous discussion[1] we are going to disable new koji >> builds for the duration of this event. >> >> All builds that will be running at that time for the rawhide will be >> canceled and can be resubmitted by maintainers after the branching. >> >> All rawhide updates that are in a pending state for rawhide will be unpushed. >> >> Once Fedora Linux 39 is branched we will re enable builds in koji. >> >> 1 - >> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/GWY4TIDIP65HA2V33F2ROU2MJLKMRZ7E/#GWY4TIDIP65HA2V33F2ROU2MJLKMRZ7E >> ___ >> 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, report it: >> https://pagure.io/fedora-infrastructure/new_issue > > > > Hello, > > Around how much time will it take? > > Thanks, > > > Robert-André >> >> > ___ > 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, report it: > https://pagure.io/fedora-infrastructure/new_issue -- Tomas Hrcka fas: humaton libera.CHAT: jednorozec ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Disabling rawhide builds during branching
I thought this got through, we will wait with the branching event after the dnf5 revert has landed. On Tue, Aug 8, 2023 at 12:15 AM Adam Williamson wrote: > > On Mon, 2023-08-07 at 23:18 +0200, Tomas Hrcka wrote: > > Hi All, > > > > Fedora Linux 39 is going to be branched from rawhide on 2023-08-08 at 10:30 > > UTC > > as per the previous discussion[1] we are going to disable new koji > > builds for the duration of this event. > > I think we should probably work out what we want to do about the dnf5 > revert update failing tests before we do the branching (see > https://bodhi.fedoraproject.org/updates/FEDORA-2023-5fd964c1bf#comment-3149533 > and the "Replacing DNF with DNF5: changes reverted and helping steps" > thread on this list). > > I will not be around at 10:30 UTC, I'll be awake about 1500 UTC I > guess. > -- > Adam Williamson (he/him/his) > Fedora QA > Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org > https://www.happyassassin.net > > > > ___ > 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, report it: > https://pagure.io/fedora-infrastructure/new_issue -- Tomas Hrcka fas: humaton libera.CHAT: jednorozec ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Disabling rawhide builds during branching
Hi All, Fedora Linux 39 is going to be branched from rawhide on 2023-08-08 at 10:30 UTC as per the previous discussion[1] we are going to disable new koji builds for the duration of this event. All builds that will be running at that time for the rawhide will be canceled and can be resubmitted by maintainers after the branching. All rawhide updates that are in a pending state for rawhide will be unpushed. Once Fedora Linux 39 is branched we will re enable builds in koji. 1 - https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/thread/GWY4TIDIP65HA2V33F2ROU2MJLKMRZ7E/#GWY4TIDIP65HA2V33F2ROU2MJLKMRZ7E ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Disabling rawhide builds during branching
Hi All, Fedora Linux 39 is going to be branched from rawhide on 2023-08-08 at 10:30 UTC as per the previous discussion[1] we are going to disable new koji builds for the duration of this event. All builds that will be running at that time for the rawhide will be canceled and can be resubmitted by maintainers after the branching. All rawhide updates that are in a pending state for rawhide will be unpushed. Once Fedora Linux 39 is branched we will re enable builds in koji. 1 - https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/GWY4TIDIP65HA2V33F2ROU2MJLKMRZ7E/#GWY4TIDIP65HA2V33F2ROU2MJLKMRZ7E ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora 39 Mass Rebuild started
Hi all, Per the Fedora Linux 39 schedule [1] we have started a mass rebuild on 2023-07-19 for Fedora 39. We are running this mass rebuild for the changes listed in: https://pagure.io/releng/issues?status=Open=mass+rebuild This mass rebuild will be done in a side tag (39-rebuild) and merged when completed. Failures can be seen https://kojipkgs.fedoraproject.org/mass-rebuild/39-failures.html Things still needing rebuilding https://kojipkgs.fedoraproject.org/mass-rebuild/39-need-rebuild.html FTBFS (Fails To Build From Source) bugs will be filed shortly after the mass rebuild is complete. Please be sure to let releng know if you see any bugs in the reporting. You can contact releng in #fedora-releng channel on Libera.Chat, the #releng:fedoraproject.org room on Matrix, or by dropping an email to our list [2] or filing an issue in pagure [3]. This email template is also in https://pagure.io/releng if you wish to propose improvements or changes to it. Regards, Tomas Hrcka Fedora Release Engineering [1] https://fedorapeople.org/groups/schedule/f-39/f-39-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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora 39 Mass Rebuild started
Oh, that thing again. Let me update the template so sed works correctly. On Wed, Jul 19, 2023 at 1:28 PM Fabio Valentini wrote: > > On Wed, Jul 19, 2023 at 1:04 PM Tomas Hrcka wrote: > > > > Hi all, > > > > Per the Fedora Linux 39 schedule [1] we have started a mass rebuild on > > 2023-07-19 for Fedora 39. We are running this mass rebuild for the > > changes listed in: > > > > https://pagure.io/releng/issues?status=Open=mass+rebuild > > > > This mass rebuild will be done in a side tag (39-rebuild) and merged > > when completed. > > > > Failures can be seen > > https://kojipkgs.fedoraproject.org/mass-rebuild/39-failures.html > > > > Things still needing rebuilding > > https://kojipkgs.fedoraproject.org/mass-rebuild/39-need-rebuild.html > > Those should be > > https://kojipkgs.fedoraproject.org/mass-rebuild/f39-failures.html > and > https://kojipkgs.fedoraproject.org/mass-rebuild/f39-need-rebuild.html > > 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 > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue -- Tomas Hrcka fas: humaton libera.CHAT: jednorozec ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora 39 Mass Rebuild started
Hi all, Per the Fedora Linux 39 schedule [1] we have started a mass rebuild on 2023-07-19 for Fedora 39. We are running this mass rebuild for the changes listed in: https://pagure.io/releng/issues?status=Open=mass+rebuild This mass rebuild will be done in a side tag (39-rebuild) and merged when completed. Failures can be seen https://kojipkgs.fedoraproject.org/mass-rebuild/39-failures.html Things still needing rebuilding https://kojipkgs.fedoraproject.org/mass-rebuild/39-need-rebuild.html FTBFS (Fails To Build From Source) bugs will be filed shortly after the mass rebuild is complete. Please be sure to let releng know if you see any bugs in the reporting. You can contact releng in #fedora-releng channel on Libera.Chat, the #releng:fedoraproject.org room on Matrix, or by dropping an email to our list [2] or filing an issue in pagure [3]. This email template is also in https://pagure.io/releng if you wish to propose improvements or changes to it. Regards, Tomas Hrcka Fedora Release Engineering [1] https://fedorapeople.org/groups/schedule/f-39/f-39-key-tasks.html [2] https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ [3] https://pagure.io/releng/ ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora Linux 38 final freeze
Hi all, Today, 2023-04-04, is an important day on the Fedora Linux 38 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 the final release as zero day updates. [1] https://fedorapeople.org/groups/schedule/f-38/f-38-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/38/final/buglist ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora Linux 38 final freeze
Hi all, Today, 2023-04-04, is an important day on the Fedora Linux 38 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 the final release as zero day updates. [1] https://fedorapeople.org/groups/schedule/f-38/f-38-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/38/final/buglist ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora Linux 38 Beta Released
Fedora Linux 38 Beta Released -- The Fedora Project is pleased to announce the immediate availability of Fedora Linux 38 Beta, the next step towards our planned Fedora Linux 38 release at the end of April. Download the prerelease from our Get Fedora site: * Get Fedora Linux 38 Beta Workstation: https://getfedora.org/workstation/download/ * Get Fedora Linux 38 Beta Server: https://getfedora.org/server/download/ * Get Fedora Linux 38 Beta IoT: https://getfedora.org/iot/download/ * Get Fedora Linux 38 Beta CoreOS: https://getfedora.org/coreos/download/ * Get Fedora Linux 38 Beta Cloud: https://getfedora.org/cloud/download/ Or, check out one of our popular variants, including KDE Plasma, Xfce, and other desktop environments: * Get Fedora Linux 38 Beta Spins: https://spins.fedoraproject.org/prerelease * Get Fedora Linux 38 Beta Labs: https://labs.fedoraproject.org/prerelease ## Beta Release Highlights - GNOME 44 - Enabling third-party repositories now enables an unfiltered view of applications on Flathub - Ruby 3.2, gcc 13, LLVM 16, Golang 1.20, PHP 8.2 For more details about the release, read the full announcement at * https://fedoramagazine.org/announcing-fedora-38-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 or the #qa:fedoraproject.org Matrix room. Regards, 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, report it: https://pagure.io/fedora-infrastructure/new_issue ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora Linux 38 Beta Released
Fedora Linux 38 Beta Released -- The Fedora Project is pleased to announce the immediate availability of Fedora Linux 38 Beta, the next step towards our planned Fedora Linux 38 release at the end of April. Download the prerelease from our Get Fedora site: * Get Fedora Linux 38 Beta Workstation: https://getfedora.org/workstation/download/ * Get Fedora Linux 38 Beta Server: https://getfedora.org/server/download/ * Get Fedora Linux 38 Beta IoT: https://getfedora.org/iot/download/ * Get Fedora Linux 38 Beta CoreOS: https://getfedora.org/coreos/download/ * Get Fedora Linux 38 Beta Cloud: https://getfedora.org/cloud/download/ Or, check out one of our popular variants, including KDE Plasma, Xfce, and other desktop environments: * Get Fedora Linux 38 Beta Spins: https://spins.fedoraproject.org/prerelease * Get Fedora Linux 38 Beta Labs: https://labs.fedoraproject.org/prerelease ## Beta Release Highlights - GNOME 44 - Enabling third-party repositories now enables an unfiltered view of applications on Flathub - Ruby 3.2, gcc 13, LLVM 16, Golang 1.20, PHP 8.2 For more details about the release, read the full announcement at * https://fedoramagazine.org/announcing-fedora-38-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 or the #qa:fedoraproject.org Matrix room. Regards, 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: ATTENTION: Package updates missing from F38 (and sometimes F39)
> > Uhm, are you sure? Neither "Lmod", "buildah", nor "dotnet" do not > > appear in this list at all. > > Looking into it further, it appears that these builds are indeed > mis-tagged in koji (i.e. with "f38-updates-testing-pending" instead of > "f38-updates-testing"), while bodhi believes they are in "testing" > state (which they are not). I filed a ticket: > https://pagure.io/releng/issue/11326 I checked randomly from the updates list for testing. Thanks for the ticket I will look into it. -- Tomas Hrcka role: CPE Team - Senior Software Engineer fas: humaton freenode: jednorozec ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: ATTENTION: Package updates missing from F38 (and sometimes F39)
> One problem that I haven't seen before is that updates are apparently > in "testing" or "testing->stable" state in bodhi, but aren't available > from the "updates-testing" repository at all. No wonder these updates > aren't getting any karma ... hmm that is strange because the builds are in the compose https://kojipkgs.fedoraproject.org/compose/updates/Fedora-38-updates-testing-20230309.0/work/x86_64/repo_package_list/Everything.x86_64.rpm.conf -- Tomas Hrcka fas: humaton libera.CHAT: jednorozec ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora Linux 38 branched
Hi All, Fedora Linux 38 has now been branched, please be sure to do a git pull --rebase to pick up the new branch, as an additional reminder rawhide/f39 has been completely isolated from previous releases, so this means that anything you do for f38 you also have to do in the rawhide branch and do a build there. There will be a Fedora Linux 38 compose and it'll appear in http://dl.fedoraproject.org/pub/fedora/linux/development/38/ once complete. Bodhi is currently enabled in the f38 branch like it is for rawhide, with automatic update creation. At the hit Beta change freeze point in the Fedora Linux 38 schedule[1] updates-testing will be enabled and manual bodhi updates will be required as in all stable releases. Two things to remember: 1. The modules will be built for a new platform:f39 2. F38/branched release is frozen right now until we get a successful compose, expect that your f38 builds won't be available immediately. Thanks for understanding. Tomas Hrcka Fedora Release Engineering [1] https://fedorapeople.org/groups/schedule/f-38/f-38-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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora Linux 38 branched
Hi All, Fedora Linux 38 has now been branched, please be sure to do a git pull --rebase to pick up the new branch, as an additional reminder rawhide/f39 has been completely isolated from previous releases, so this means that anything you do for f38 you also have to do in the rawhide branch and do a build there. There will be a Fedora Linux 38 compose and it'll appear in http://dl.fedoraproject.org/pub/fedora/linux/development/38/ once complete. Bodhi is currently enabled in the f38 branch like it is for rawhide, with automatic update creation. At the hit Beta change freeze point in the Fedora Linux 38 schedule[1] updates-testing will be enabled and manual bodhi updates will be required as in all stable releases. Two things to remember: 1. The modules will be built for a new platform:f39 2. F38/branched release is frozen right now until we get a successful compose, expect that your f38 builds won't be available immediately. Thanks for understanding. Tomas Hrcka Fedora Release Engineering [1] https://fedorapeople.org/groups/schedule/f-38/f-38-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, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora 38 mass branching postpone for 1 day
Hello, the mass branching of Fedora Linux 38 was planned to happen on 2023-02-07. Due to traveling from FOSDEM and the re-signing of rawhide with a new key we will postpone the branching to 2023-02-08. Sorry for the inconvenience Tomas Hrcka 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, report it: https://pagure.io/fedora-infrastructure/new_issue ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora 38 mass branching postpone for 1 day
Hello, the mass branching of Fedora Linux 38 was planned to happen on 2023-02-07. Due to traveling from FOSDEM and the re-signing of rawhide with a new key we will postpone the branching to 2023-02-08. Sorry for the inconvenience Tomas Hrcka 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora 38 mass rebuild is finished
done. $ koji list-tagged eln libunistring Build libunistring-1.0-2.eln120 libunistring-1.0-2.fc37 On Tue, Jan 24, 2023 at 11:59 AM Tomáš Popela wrote: > > > > On Mon, Jan 23, 2023 at 8:56 PM Kevin Fenzi wrote: >> >> On Mon, Jan 23, 2023 at 01:36:10PM -0600, Jonathan Wright via devel wrote: >> > I'm seeing the same errors on rawhide buildroot right now. >> >> The problem was libunistring-1.1-3.fc38 (again). >> >> We untagged it in december, but looks like no one followed up to get >> dependent packages rebuilt: >> >> https://pagure.io/releng/issue/11175 >> >> I have untagged it (again) for now. > > > I see that the ELN buildroot is broken in the same way, can you Kevin or > Stephen untag the libunistring from ELN? > > 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 >> Do not reply to spam, report it: >> https://pagure.io/fedora-infrastructure/new_issue > > ___ > 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, report it: > https://pagure.io/fedora-infrastructure/new_issue -- Tomas Hrcka role: CPE Team - Senior Software Engineer fas: humaton freenode: jednorozec ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora 38 mass rebuild is finished
Hi all, Per the Fedora Linux 38 schedule[1] we started a mass rebuild for Fedora Linux 38 on 1. 18, 2023. We did a mass rebuild for Fedora 38 for: https://fedoraproject.org/wiki/Changes/Add_FORTIFY_SOURCE%3D3_to_distribution_build_flags https://fedoraproject.org/wiki/Changes/fno-omit-frame-pointer https://fedoraproject.org/wiki/Changes/GNUToolchainF38 As per the maintainer's request[4] we have skipped all Haskell packages from this rebuild. The mass rebuild was done in a side tag (f38-rebuild) and moved over to f38. Failures can be seen at https://kojipkgs.fedoraproject.org/mass-rebuild/f38-failures.html Things still needing rebuilding https://kojipkgs.fedoraproject.org/mass-rebuild/f38-need-rebuild.html 20996 builds have been tagged into f38, there are currently 840 failed builds that need to be addressed by the package maintainers. 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 libera.chat, by dropping an email to our list[2], joining #releng:fedoraproject.org on Matrix, or filing an issue in pagure[3] Regards, Tomas Hrcka Fedora Release Engineering [1] https://fedorapeople.org/groups/schedule/f-38/f-38-key-tasks.html [2] https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ [3] https://pagure.io/releng/ [4] https://pagure.io/releng/issue/11217 ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora 38 mass rebuild is finished
Hi all, Per the Fedora Linux 38 schedule[1] we started a mass rebuild for Fedora Linux 38 on 1. 18, 2023. We did a mass rebuild for Fedora 38 for: https://fedoraproject.org/wiki/Changes/Add_FORTIFY_SOURCE%3D3_to_distribution_build_flags https://fedoraproject.org/wiki/Changes/fno-omit-frame-pointer https://fedoraproject.org/wiki/Changes/GNUToolchainF38 As per the maintainer's request[4] we have skipped all Haskell packages from this rebuild. The mass rebuild was done in a side tag (f38-rebuild) and moved over to f38. Failures can be seen at https://kojipkgs.fedoraproject.org/mass-rebuild/f38-failures.html Things still needing rebuilding https://kojipkgs.fedoraproject.org/mass-rebuild/f38-need-rebuild.html 20996 builds have been tagged into f38, there are currently 840 failed builds that need to be addressed by the package maintainers. 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 libera.chat, by dropping an email to our list[2], joining #releng:fedoraproject.org on Matrix, or filing an issue in pagure[3] Regards, Tomas Hrcka Fedora Release Engineering [1] https://fedorapeople.org/groups/schedule/f-38/f-38-key-tasks.html [2] https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ [3] https://pagure.io/releng/ [4] https://pagure.io/releng/issue/11217 ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora 38 mass rebuild started
Hi all, Per the Fedora f38 schedule[1] we have started a mass rebuild on 2022-01-18 for Fedora f38. We are running this mass rebuild for the changes listed in: https://pagure.io/releng/issues?status=Open=mass+rebuild This mass rebuild will be done in a side tag (f38-rebuild) and merged when completed. Failures can be seen https://kojipkgs.fedoraproject.org/mass-rebuild/f38-failures.html Things still needing rebuilding https://kojipkgs.fedoraproject.org/mass-rebuild/f38-need-rebuild.html FTBFS (Fails To Build From Source) bugs will be filed shortly after the mass rebuild is complete. Please be sure to let releng know if you see any bugs in the reporting. You can contact releng in #fedora-releng channel on Libera.Chat, the #releng:fedoraproject.org room on Matrix, or by dropping an email to our list[2] or filing an issue in pagure[3]. This email template is also in https://pagure.io/releng if you wish to propose improvements or changes to it. Regards, Tomas Hrcka, Fedora Release Engineering [1] https://fedorapeople.org/groups/schedule/f-38/f-38-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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora 38 mass rebuild started
Hi all, Per the Fedora f38 schedule[1] we have started a mass rebuild on 2022-01-18 for Fedora f38. We are running this mass rebuild for the changes listed in: https://pagure.io/releng/issues?status=Open=mass+rebuild This mass rebuild will be done in a side tag (f38-rebuild) and merged when completed. Failures can be seen https://kojipkgs.fedoraproject.org/mass-rebuild/f38-failures.html Things still needing rebuilding https://kojipkgs.fedoraproject.org/mass-rebuild/f38-need-rebuild.html FTBFS (Fails To Build From Source) bugs will be filed shortly after the mass rebuild is complete. Please be sure to let releng know if you see any bugs in the reporting. You can contact releng in #fedora-releng channel on Libera.Chat, the #releng:fedoraproject.org room on Matrix, or by dropping an email to our list[2] or filing an issue in pagure[3]. This email template is also in https://pagure.io/releng if you wish to propose improvements or changes to it. Regards, Tomas Hrcka, Fedora Release Engineering [1] https://fedorapeople.org/groups/schedule/f-38/f-38-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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
F38 mass rebuild is waiting for gcc build
Hi, today is the day we are running a mass rebuild. Usually we start at 10:30am UTC. Today we will wait for the latest GCC build[1] to get finished and start a few hours later. [1] - https://koji.fedoraproject.org/koji/taskinfo?taskID=96265376 -- Tomas Hrcka Fedora Release Engineering fas: humaton libera: jednorozec ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora 35 is End of Life
Hello all, As of the 13th of December 2022, Fedora 35 has reached its end of life for updates and support. No further updates, including security updates, will be available for Fedora 35 after the said date. All the updates of Fedora 35 being pushed to stable will be stopped as well. Fedora 36 will continue to receive updates until approximately one month after the release of Fedora 38. 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, Tomas Hrcka Fedora Release Engineering [0]https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule [1]https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora 35 is End of Life
Hello all, As of the 13th of December 2022, Fedora 35 has reached its end of life for updates and support. No further updates, including security updates, will be available for Fedora 35 after the said date. All the updates of Fedora 35 being pushed to stable will be stopped as well. Fedora 36 will continue to receive updates until approximately one month after the release of Fedora 38. 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, Tomas Hrcka Fedora Release Engineering [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, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora 35 End Of Life in one day
Hello all, Fedora 35 will go end of life for updates and support on 2022-12-13 No further updates, including security updates, will be available for Fedora 35 after the said date. All the updates of Fedora 35 being pushed to stable will be stopped as well. Fedora 36 will continue to receive updates until approximately one month after the release of Fedora 38. 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, Tomas Hrcka Fedora Release Engineering [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, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] Fedora 35 End Of Life in one day
Hello all, Fedora 35 will go end of life for updates and support on 2022-12-13 No further updates, including security updates, will be available for Fedora 35 after the said date. All the updates of Fedora 35 being pushed to stable will be stopped as well. Fedora 36 will continue to receive updates until approximately one month after the release of Fedora 38. 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, Tomas Hrcka Fedora Release Engineering [0]https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule [1]https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora 35 End Of Life in one week
Ups, of course it should be Fedora 38 On Wed, Dec 7, 2022 at 4:25 PM Steven A. Falco wrote: > > On 12/7/22 09:14 AM, Tomas Hrcka wrote: > > Fedora 36 will continue to receive updates until approximately one > > month after the release of Fedora 37. > > Shouldn't that be "until approximately one month after the release of Fedora > _38_"? > > Steve > ___ > 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, report it: > https://pagure.io/fedora-infrastructure/new_issue -- Tomas Hrcka role: CPE Team - Senior Software Engineer fas: humaton freenode: jednorozec ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora 35 End Of Life in one week
Hello all, Fedora 35 will go end of life for updates and support on 2022-12-13 No further updates, including security updates, will be available for Fedora 35 after the said date. All the updates of Fedora N being pushed to stable will be stopped as well. Fedora 36 will continue to receive updates until approximately one month after the release of Fedora 37. 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, Tomas Hrcka Fedora Release Engineering [0]https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule [1]https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora 35 End Of Life in one week
Hello all, Fedora 35 will go end of life for updates and support on 2022-12-13 No further updates, including security updates, will be available for Fedora 35 after the said date. All the updates of Fedora N being pushed to stable will be stopped as well. Fedora 36 will continue to receive updates until approximately one month after the release of Fedora 37. 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, Tomas Hrcka Fedora Release Engineering [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, report it: https://pagure.io/fedora-infrastructure/new_issue
** s390x builders Outage **
There is an ongoing BOS power outage impacting s390x builders. Reason for outage: Power outage in the DC -- Tomas Hrcka role: CPE Team - Senior Software Engineer fas: humaton freenode: jednorozec ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
** s390x builders Outage **
There is an ongoing BOS power outage impacting s390x builders. Reason for outage: Power outage in the DC -- Tomas Hrcka role: CPE Team - Senior Software Engineer fas: humaton freenode: jednorozec ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Has the final freeze for f37 started?
Hi, yes the freeze started on the scheduled date and time. Please create releng ticket with packages that require blocking in koji. On Thu, Oct 6, 2022 at 3:25 PM Fabio Valentini wrote: > Hi all, > > I retired some packages from f37 and rawhide on Tuesday and Wednesday, > but their retirements were no longer processed correctly. After > looking at the F37 schedule, the Final Freeze for Fedora 37 should > have started two days ago (14:00 UTC on 2022-10-04), which might > explain this (at least in part, some packages were retired before > 14:00 UTC), but right now I can't find an announcement that the freeze > has actually started. > > Should I open a releng ticket to get the affected packages correctly > retired? Right now they're "retired" in dist-git but not blocked in > koji etc., and since they're unused and / or broken packages, I'd like > F37 not to ship with them. > > 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 > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > -- Tomas Hrcka role: CPE Team - Senior Software Engineer fas: humaton freenode: jednorozec ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: libharu soname bump for rawhide
the build is now untagged from f38
On Wed, Oct 5, 2022 at 3:34 PM Orion Poplawski wrote:
> On 10/5/22 07:11, Mamoru TASAKA wrote:
> > Dmitrij S. Kryzhevich wrote on 2022/10/05 18:02:
> >> I understand the necessity of time to react, may be should handle it
> >> in a more proper way.
> >> I was triggered by maintainer of only dependent package (directly
> >> dependent) so I strongly believe it's OK in this case.
> >
> > Seems not actually:
> >
> > dnf repoquery --repo=koji-38 --qf '%{sourcerpm}' --whatrequires
> > "libhpdf.so.2.3*" | cat -n
> > 1EMBOSS-6.6.0-22.fc38.src.rpm
> > 2blender-3.3.0-4.fc38.src.rpm
> > 3mathgl-2.4.4-18.fc38.src.rpm
> > 4perl-PDF-Haru-1.00-38.fc37.src.rpm
> > 5plplot-5.15.0-45.fc38.src.rpm
> > 6saga-7.6.1-16.fc38.src.rpm
> > 7vtk-9.1.0-17.fc37.src.rpm
> >
> > Perhaps I am going to request untag for libharu-2.4.2-1.fc38.
> >
> > Regards,
> > Mamoru
> >
>
> That works for me (maintainer of vtk and plplot) as I'm not quite ready
> to push vtk 9.2.2 out yet. I didn't expect libharu to get built right
> away.
>
> Orion
>
> >
> >>
> >> On Wed, 5 Oct 2022 10:51:20 +0200
> >> Fabio Valentini wrote:
> >>
> >>> On Wed, Oct 5, 2022 at 9:24 AM Dmitrij S. Kryzhevich
> >>> wrote:
> >>>>
> >>>> New version of libharu is building for rawhide with coresponding
> >>>> soname bump.
> >>>> Only vtk should be affected right now.
> >>>
> >>> I see that you have already built libharu-2.4.2-1.fc38.
> >>>
> >>> Did you also handle rebuilding dependent packages, or should their
> >>> maintainers handle that themselves?
> >>> Usually there should be one week between such heads-up emails and
> >>> pushing the actual build, especially when you don't rebuild dependent
> >>> packages.
> >>>
> >>> 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
> >>>
> >>> Do not reply to spam, report it:
> >>> https://pagure.io/fedora-infrastructure/new_issue
> >> ___
> >> 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, report it:
> >> https://pagure.io/fedora-infrastructure/new_issue
> > ___
> > 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, report it:
> > https://pagure.io/fedora-infrastructure/new_issue
>
>
> --
> Orion Poplawski
> he/him/his - surely the least important thing about me
> IT Systems Manager 720-772-5637
> NWRA, Boulder/CoRA Office FAX: 303-415-9702
> 3380 Mitchell Lane or...@nwra.com
> Boulder, CO 80301 https://www.nwra.com/
> ___
> 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, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
--
Tomas Hrcka
role: CPE Team - Senior Software Engineer
fas: humaton
freenode: jednorozec
___
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, report it:
https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] Fedora Linux 37 Beta Release Announcement
Fedora Linux 37 Beta Released -- The Fedora Project is pleased to announce the immediate availability of Fedora Linux 37 Beta, the next step towards our planned Fedora Linux 37 release at the end of October. Download the prerelease from our Get Fedora site: * Get Fedora 37 Beta Workstation: https://getfedora.org/workstation/download/ * Get Fedora 37 Beta Server: https://getfedora.org/server/download/ * Get Fedora 37 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 37 Beta Spins: https://spins.fedoraproject.org/prerelease * Get Fedora 37 Beta Labs: https://labs.fedoraproject.org/prerelease * Get Fedora 37 Beta ARM: https://arm.fedoraproject.org/prerelease ## Beta Release Highlights # Gnome 43 # Retire ARMv7 # Python 3.11, Perl 5.36, Golang 1.19 # RPM content is now signed with IMA signatures For more details about the release, read the full announcement at * https://fedoramagazine.org/announcing-fedora-37-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 or the #qa:fedoraproject.org Matrix room. Regards, Tomas Hrcka, 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, report it: https://pagure.io/fedora-infrastructure/new_issue ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora 37 Bodhi updates-testing activation and Beta Freeze
Hi all, Today's an important day on the Fedora 37 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 37 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 37. Finally, today is the 'completion deadline' Change Checkpoint[8], meaning that Fedora 37 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 Fedora Release Engineering [1] https://fedorapeople.org/groups/schedule/f-37/f-37-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 -- Tomas Hrcka fas: humaton Libera.chat: jednorozec ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] Fedora 37 Bodhi updates-testing activation and Beta Freeze
Hi all, Today's an important day on the Fedora 37 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 37 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 37. Finally, today is the 'completion deadline' Change Checkpoint[8], meaning that Fedora 37 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 Fedora Release Engineering [1] https://fedorapeople.org/groups/schedule/f-37/f-37-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 -- Tomas Hrcka fas: humaton Libera.chat: jednorozec ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Golang Mass Rebuild
Hi Maxwell, Fedora release engineering is running a mass rebuild of rawhide on 20.6., if your changes are merged in rawhide/main branches by then, they will be included. On Mon, Jul 18, 2022 at 4:57 AM Maxwell G via devel < devel@lists.fedoraproject.org> wrote: > Hi Fedorians and Gophers, > > golang 1.18.4 was released a couple days ago. This release has fixes for > 9 medium (rated by Red Hat Product Security) CVEs, so I will preform a > rebuild in `rawhide` and `f36` to mitigate them[^0]. See > https://groups.google.com/g/golang-dev/c/frczlF8OFQ0/m/4lrZh5BHDgAJ for > more information about the specific vulnerabilities. > > [^0]: The golang version is Fedora 35 is EOL upstream, and the > maintainers have not yet had a chance to backport the changes. > > Only packages that provide binaries need to be rebuilt, which will make > this rebuild less disruptive. These packages were determined by querying > for source packages that BuildRequire `golang` or `go-rpm-macros` and > then checking if they provide any binary RPMS that install files in > `/usr/bin`, `/usr/sbin`, or `/usr/libexec`. > > No action will be required from you, unless you'd like your package to > receive special treatment regarding merging `rawhide` into `f36`. I plan > to handle this rebuild later this week (the week of the 17th). > > In light of the recent discussion about large updates, I will most > likely split this into 4 Bodhi updates per branch (a total of 8; each > containing ~100 packages). > > ## rawhide > Here[1] is a list of the affected packages on `rawhide`. > > [1]: > https://git.sr.ht/~gotmax23/fedora-scripts/tree/main/item/rebuilds/golang_1.18.4/rawhide/lists/all-packages.list > > ## f36 > > Here[2] is a list of all of the affected packages on `f36`. However, I > have further split this list down into two subgroups. > > [2]: > https://git.sr.ht/~gotmax23/fedora-scripts/tree/main/item/rebuilds/golang_1.18.4/f36/lists/all-packages.list > > ### Mergable from Rawhide > For these packages[3], `rawhide` was determined to be mergable back to > `f36`, as `f36` is up to date with `rawhide`. > > [3]: > https://git.sr.ht/~gotmax23/fedora-scripts/tree/main/item/rebuilds/golang_1.18.4/f36/lists/mergable.list > > ### Not mergable > These packages were determined to not be mergable[4], as `rawhide` is > ahead of (or has otherwise diverged from) `f36`. Therefore, I will > create a new rebuild commit and bump the release on `f36`. This will > likely cause merge conflicts if you try to merge `rawhide` back into > `f36` after this change. Assuming the update would be compatible and > comply with the Updates Policy, I can move your package into the other > list and merge `rawhide` into `f36`. Please leave a comment on > https://pagure.io/GoSIG/go-sig/issue/44 if you would like me to do so. > Conversely, if you believe your package is incorrectly in the mergable > list, also let me know in the aforementioned ticket. > > [4]: > https://git.sr.ht/~gotmax23/fedora-scripts/tree/main/item/rebuilds/golang_1.18.4/f36/lists/unmergable.list > -- > Thanks, > > Maxwell G (@gotmax23) > Pronouns: He/Him/His > ___ > 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 > -- Tomas Hrcka role: CPE Team - Senior Software Engineer fas: humaton freenode: jednorozec ___ 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: Anything in particular blocking SCM requests?
Hi, not really probably the person who usually runs the scripts is not available. The queue is getting processed as I write this. On Tue, Jun 14, 2022 at 6:02 AM Orion Poplawski wrote: > Looks like they haven't been processed in 3-4 days. Any particular > reason or just lack of resources? > > Thanks! > > -- > Orion Poplawski > he/him/his - surely the least important thing about me > IT Systems Manager 720-772-5637 > NWRA, Boulder/CoRA Office FAX: 303-415-9702 > 3380 Mitchell Lane or...@nwra.com > Boulder, CO 80301 https://www.nwra.com/ > ___ > 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 > -- Tomas Hrcka role: CPE Team - Senior Software Engineer fas: humaton freenode: jednorozec ___ 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 is EOL
Hello all, As of the 7th of June 2022, Fedora 34 has reached its end of life for updates and support. No further updates, including security updates, will be available for Fedora 34. All the updates that are currently in testing won't get pushed to stable. Fedora 35 will continue to receive updates until approximately one month after the release of Fedora 37. 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. Tomas Hrcka [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 34 is EOL
Hello all, As of the 7th of June 2022, Fedora 34 has reached its end of life for updates and support. No further updates, including security updates, will be available for Fedora 34. All the updates that are currently in testing won't get pushed to stable. Fedora 35 will continue to receive updates until approximately one month after the release of Fedora 37. 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. Tomas Hrcka [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 is going EOL in one day.
Hello all, Fedora 34 will go end of life for updates and support on 2022-06-07 No further updates, including security updates, will be available for Fedora 34 after the said date. All the updates of Fedora 34 being pushed to stable will be stopped as well. Fedora 35 will continue to receive updates until approximately one month after the release of Fedora 37. 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, Fedora Release Engineering [0] https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule [1]https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades -- Tomas Hrcka role: CPE Team - Senior Software Engineer fas: humaton freenode: jednorozec ___ 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 is going EOL in one day.
Hello all, Fedora 34 will go end of life for updates and support on 2022-06-07 No further updates, including security updates, will be available for Fedora 34 after the said date. All the updates of Fedora 34 being pushed to stable will be stopped as well. Fedora 35 will continue to receive updates until approximately one month after the release of Fedora 37. 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, Fedora Release Engineering [0] https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule [1]https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades -- Tomas Hrcka role: CPE Team - Senior Software Engineer fas: humaton freenode: jednorozec ___ 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 is going EOL in one week
Hello all, Fedora 34 will go end of life for updates and support on 2022-06-07 No further updates, including security updates, will be available for Fedora 34 after the said date. All the updates of Fedora 34 being pushed to stable will be stopped as well. Fedora 35 will continue to receive updates until approximately one month after the release of Fedora 37. 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, Fedora Release Engineering [0] https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule [1]https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades -- Tomas Hrcka role: CPE Team - Senior Software Engineer fas: humaton freenode: jednorozec ___ 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 is going EOL in one week
Hello all, Fedora 34 will go end of life for updates and support on 2022-06-07 No further updates, including security updates, will be available for Fedora 34 after the said date. All the updates of Fedora 34 being pushed to stable will be stopped as well. Fedora 35 will continue to receive updates until approximately one month after the release of Fedora 37. 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, Fedora Release Engineering [0] https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule [1]https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades -- Tomas Hrcka role: CPE Team - Senior Software Engineer fas: humaton freenode: jednorozec ___ 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 is going EOL in 20 days
Hello all, Fedora 34 will go end of life for updates and support on 2022-06-07 No further updates, including security updates, will be available for Fedora 34 after the said date. All the updates of Fedora 34 being pushed to stable will be stopped as well. Regards, 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 34 is going EOL in 20 days
Hello all, Fedora 34 will go end of life for updates and support on 2022-06-07 No further updates, including security updates, will be available for Fedora 34 after the said date. All the updates of Fedora 34 being pushed to stable will be stopped as well. Regards, 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 36 Beta Release Announcement
Fedora Linux 36 Beta Released -- The Fedora Project is pleased to announce the immediate availability of Fedora 36 Beta, the next step towards our planned Fedora 36 release at the end of April. Download the prerelease from our Get Fedora site: * Get Fedora 36 Beta Workstation: https://getfedora.org/workstation/download/ * Get Fedora 36 Beta Server: https://getfedora.org/server/download/ * Get Fedora 36 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 36 Beta Spins: https://spins.fedoraproject.org/prerelease * Get Fedora 36 Beta Labs: https://labs.fedoraproject.org/prerelease * Get Fedora 36 Beta ARM: https://arm.fedoraproject.org/prerelease ## Beta Release Highlights * Fedora 36 Workstation Beta includes GNOME 42 * Update of programming languages and libraries: LXQt 1.0, Golang 1.18, Ruby 3.1 For more details about the release, read the full announcement at * https://fedoramagazine.org/announcing-fedora-36-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 or the #qa:fedoraproject.org Matrix room. Regards, Tomas Hrcka 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 36 Beta Release Announcement
Fedora Linux 36 Beta Released -- The Fedora Project is pleased to announce the immediate availability of Fedora 36 Beta, the next step towards our planned Fedora 36 release at the end of April. Download the prerelease from our Get Fedora site: * Get Fedora 36 Beta Workstation: https://getfedora.org/workstation/download/ * Get Fedora 36 Beta Server: https://getfedora.org/server/download/ * Get Fedora 36 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 36 Beta Spins: https://spins.fedoraproject.org/prerelease * Get Fedora 36 Beta Labs: https://labs.fedoraproject.org/prerelease * Get Fedora 36 Beta ARM: https://arm.fedoraproject.org/prerelease ## Beta Release Highlights * Fedora 36 Workstation Beta includes GNOME 42 * Update of programming languages and libraries: LXQt 1.0, Golang 1.18, Ruby 3.1 For more details about the release, read the full announcement at * https://fedoramagazine.org/announcing-fedora-36-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 or the #qa:fedoraproject.org Matrix room. Regards, Tomas Hrcka 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
Re: What has the PDC ever done for us?
On Thu, Mar 17, 2022 at 5:35 PM Petr Pisar wrote: > V Thu, Mar 17, 2022 at 04:13:44PM +0100, Tomas Hrcka napsal(a): > > On Thu, Mar 17, 2022 at 3:09 PM Petr Pisar wrote: > > > Having the dist-git retirement as a primary source of truth has the > problem > > > that you need to clone a dist-git branch to get the data. And then for > each > > > package you are interested again and again. Whereas PDC, being a > database > > > underneath, have the data centralized at one place, and readily > available > > > in > > > no time. > > > > > > > distgit is basically pagure in it has a DB we were thinking about moving > > package-specific data like EOL to in information already stored in the DB > > for each repository. > > I cannot parse your sentence. Does it mean there is one database which > stores all the data about all repositories, or does it mean that each > repository has its own database? > Sorry about that. Let me be more clear. distgit is actually pagure-distgit[1] that is a plugin for pagure. It has its own model definitions[2]. It uses the beefy PSQL server that most apps use. Currently, we do not store much information about packages. > > Is this Pagure/dist-git database publically accessible for reading? > No the DB itself but pagure has API. > > > This would allow us to use specific EOL for modules. > > > In modularity I want to deliver the EOL dates to user's YUM repositories so > that "dnf module list" can list them and alert users about EOLed module > stream > they use (bug #2054662). > > We already have a mechanism for delivering the data to the YUM repositories > < > https://docs.fedoraproject.org/en-US/modularity/building-modules/fedora/module-obsoletes/ > >. > But the mechanism relies on a manual input > <https://pagure.io/releng/fedora-module-defaults/blob/main/f/obsoletes>. > It's > manual because one of the purposes if the mechanism is delivering which > stream > replaces which one. But the EOL dates could be filled automaticaly. > > That's why I'm so obsessed with PDC. > > -- 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 > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > [1] - https://pagure.io/pagure-dist-git/ [2] - https://pagure.io/pagure-dist-git/blob/master/f/pagure_distgit/model.py -- Tomas Hrcka role: CPE Team - Senior Software Engineer fas: humaton freenode: jednorozec ___ 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: What has the PDC ever done for us?
ailing 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 > -- Tomas Hrcka role: CPE Team - Senior Software Engineer fas: humaton libera: jednorozec ___ 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 36 Bodhi updates-testing Activation and Beta Freeze
Hi all, Today's an important day on the Fedora 36 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 36 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 36. Finally, today is the 'completion deadline' Change Checkpoint[8], meaning that Fedora 36 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 Tomáš Hrčka [1] https://fedorapeople.org/groups/schedule/f-36/f-36-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 36 Bodhi updates-testing Activation and Beta Freeze
Hi all, Today's an important day on the Fedora 36 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 36 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 36. Finally, today is the 'completion deadline' Change Checkpoint[8], meaning that Fedora 36 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 Tomáš Hrčka [1] https://fedorapeople.org/groups/schedule/f-36/f-36-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
Fedora 36 Mass Branching
Hi All, Fedora 36 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 f36 you also have to do in the rawhide branch and do a build there. There will be a Fedora 36 compose and it'll appear in http://dl.fedoraproject.org/pub/fedora/linux/development/36/ once complete. Please be sure to check it out. Bodhi is currently not active for Fedora 36, it will be enabled in a couple of weeks when we hit Beta change freeze point in the Fedora 36 schedule[1]. Two things to remember: 1. The modules will be built for a new platform:f37 2. The signing of RPMs is not done yet with the new f37 key. 3. F36/branched release is frozen right now until we get a successful compose, expect that your f36 builds won't be available immediately. Thanks for understanding. [1] https://fedorapeople.org/groups/schedule/f-36/f-36-key-tasks.html -- Tomas Hrcka role: CPE Team - Senior Software Engineer fas: humaton libera.CHAT: jednorozec ___ 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 36 Mass Branching
Hi All, Fedora 36 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 f36 you also have to do in the rawhide branch and do a build there. There will be a Fedora 36 compose and it'll appear in http://dl.fedoraproject.org/pub/fedora/linux/development/36/ once complete. Please be sure to check it out. Bodhi is currently not active for Fedora 36, it will be enabled in a couple of weeks when we hit Beta change freeze point in the Fedora 36 schedule[1]. Two things to remember: 1. The modules will be built for a new platform:f37 2. The signing of RPMs is not done yet with the new f37 key. 3. F36/branched release is frozen right now until we get a successful compose, expect that your f36 builds won't be available immediately. Thanks for understanding. [1] https://fedorapeople.org/groups/schedule/f-36/f-36-key-tasks.html -- Tomas Hrcka role: CPE Team - Senior Software Engineer fas: humaton libera.CHAT: jednorozec ___ 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 Bodhi updates-testing Activation and Beta Freeze
Hi all, Today's an important day on the Fedora 35 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 35 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 35. Finally, today is the 'completion deadline' Change Checkpoint[8], meaning that Fedora 35 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 Tomas Hrcka [1] https://fedorapeople.org/groups/schedule/f-35/f-35-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 -- Tomas Hrcka role: CPE Team - Senior Software Engineer fas: humaton libera.Chat: jednorozec ___ 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 35 Bodhi updates-testing Activation and Beta Freeze
Hi all, Today's an important day on the Fedora 35 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 35 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 35. Finally, today is the 'completion deadline' Change Checkpoint[8], meaning that Fedora 35 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 Tomas Hrcka [1] https://fedorapeople.org/groups/schedule/f-35/f-35-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 -- Tomas Hrcka role: CPE Team - Senior Software Engineer fas: humaton libera.Chat: jednorozec ___ 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
F35 mass rebuild is finished
Hi all, Per the Fedora 35 schedule[1] we started a mass rebuild for Fedora 35 on Jul 21st, 2021. We did a mass rebuild for Fedora 35 for: https://fedoraproject.org/wiki/Changes/Autoconf_271 https://fedoraproject.org/wiki/Changes/RPM-4.17 https://fedoraproject.org/wiki/Changes/IBus_1.5.25 https://fedoraproject.org/wiki/Changes/F35Boost176 https://fedoraproject.org/wiki/Changes/F35MingwEnvToolchainUpdate https://fedoraproject.org/wiki/Changes/LTOBuildImprovements https://fedoraproject.org/wiki/Changes/golang1.17 https://fedoraproject.org/wiki/Changes/LLVM-13 The mass rebuild was done in a side tag (f35-rebuild) and moved over to f35. Failures can be seen https://kojipkgs.fedoraproject.org/mass-rebuild/f35-failures.html Things still needing rebuilding https://kojipkgs.fedoraproject.org/mass-rebuild/f35-need-rebuild.html 21151 builds have been tagged into f35, there is currently 772 failed builds that need to be addressed by the package maintainers. 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 libera.chat, by dropping an email to our list[2] or filing an issue in pagure[3] Regards, Tomas Hrcka fas: humaton libera.chat: jednorozec [1] <http://goog_1896774115> https://fedorapeople.org/groups/schedule/f-35/f-35-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 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
F35 mass rebuild is finished
Hi all, Per the Fedora 35 schedule[1] we started a mass rebuild for Fedora 35 on Jul 21st, 2021. We did a mass rebuild for Fedora 35 for: https://fedoraproject.org/wiki/Changes/Autoconf_271 https://fedoraproject.org/wiki/Changes/RPM-4.17 https://fedoraproject.org/wiki/Changes/IBus_1.5.25 https://fedoraproject.org/wiki/Changes/F35Boost176 https://fedoraproject.org/wiki/Changes/F35MingwEnvToolchainUpdate https://fedoraproject.org/wiki/Changes/LTOBuildImprovements https://fedoraproject.org/wiki/Changes/golang1.17 https://fedoraproject.org/wiki/Changes/LLVM-13 The mass rebuild was done in a side tag (f35-rebuild) and moved over to f35. Failures can be seen https://kojipkgs.fedoraproject.org/mass-rebuild/f35-failures.html Things still needing rebuilding https://kojipkgs.fedoraproject.org/mass-rebuild/f35-need-rebuild.html 21151 builds have been tagged into f35, there is currently 772 failed builds that need to be addressed by the package maintainers. 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 libera.chat, by dropping an email to our list[2] or filing an issue in pagure[3] Regards, Tomas Hrcka fas: humaton libera.chat: jednorozec [1] <http://goog_1896774115> https://fedorapeople.org/groups/schedule/f-35/f-35-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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Fedora 35 Mass Rebuild
They haven't finished building, so if we cancel both of these, then it would work: > https://koji.fedoraproject.org/koji/taskinfo?taskID=72392389 > https://koji.fedoraproject.org/koji/taskinfo?taskID=72392356 > I have canceled both tasks. -- Tomas Hrcka role: CPE Team - Senior Software Engineer fas: humaton freenode: jednorozec ___ 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 35 Mass Rebuild update
Hi all, sorry for the empty commit messages, we have migrated the script from fedpkg to plain git command to allows empty commits for rmpautospec enabled packages. The bug is now fixed and the script re-run, some packages will have one empty commit followed by the actual mass rebuild commit. Sorry for the inconvenience and confusion. On Wed, Jul 21, 2021 at 6:04 PM Zbigniew Jędrzejewski-Szmek < zbys...@in.waw.pl> wrote: > On Wed, Jul 21, 2021 at 09:35:37AM -0600, Jerry James wrote: > > On Wed, Jul 21, 2021 at 9:30 AM Vitaly Zaitsev via devel > > wrote: > > > On 21/07/2021 17:15, Jerry James wrote: > > > > In fact, the ones I've looked at are empty commits. There is a > commit > > > > message, but no changes of any kind to the spec file: no release > bump, > > > > no changelog entry. > > > > > > Yes, I can confirm[1]: > > > > > > Authored and Committed by releng 3 hours ago > > > 0 file changed. 0 lines added. 0 lines removed. > > > > > > [1]: > > > > https://src.fedoraproject.org/rpms/aircrack-ng/c/b9c84c950c4a300709ac6dfee5d0a3b83c42447e?branch=rawhide > > > > That would be the right thing to do for packages using rpmautospec. > > My suspicion is that rpmautospec support was added to the rebuild > > script, but it is somehow detecting packages that do not actually use > > rpmautospec. > > I guess normally such builds would immediately fail because koji does > not allow non-scratch builds with the same nevra. But in case of the > mass rebuild, it works for packages which haven't been build for F35 > yet [1]: aircrack-ng-1.6-8.fc34 != aircrack-ng-1.6-8.fc35. > But it'll break for packages which have been already built for F35. > It's also very confusing even if it works. > > [1] https://koji.fedoraproject.org/koji/buildinfo?buildID=1782783 > > Zbyszek > ___ > 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 > -- Tomas Hrcka role: CPE Team - Senior Software Engineer fas: humaton freenode: jednorozec ___ 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 Rebuild update
Hi all, Per the Fedora 35 schedule[1] we will start a mass rebuild for Fedora 35 on Jul 21st, 2021. We will run a mass rebuild for Fedora 35 for the changes listed in: https://pagure.io/releng/issues?status=Open=mass+rebuild The mass rebuild will be done in a side tag (f35-rebuild) and moved over when completed. Failures can be seen https://kojipkgs.fedoraproject.org/mass-rebuild/f35-failures.html Things still needing rebuilding https://kojipkgs.fedoraproject.org/mass-rebuild/f35-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 Libera.Chat, by dropping an email to our list[2] or filing an issue in pagure[3] Regards, Tomas Hrcka fas: humaton LiberaChat: jednorozec [1] https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html [2] https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ [3] https://pagure.io/releng/ -- Tomas Hrcka role: CPE Team - Senior Software Engineer fas: humaton freenode: jednorozec ___ 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 35 Mass Rebuild update
Hi all, Per the Fedora 35 schedule[1] we will start a mass rebuild for Fedora 35 on Jul 21st, 2021. We will run a mass rebuild for Fedora 35 for the changes listed in: https://pagure.io/releng/issues?status=Open=mass+rebuild The mass rebuild will be done in a side tag (f35-rebuild) and moved over when completed. Failures can be seen https://kojipkgs.fedoraproject.org/mass-rebuild/f35-failures.html Things still needing rebuilding https://kojipkgs.fedoraproject.org/mass-rebuild/f35-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 Libera.Chat, by dropping an email to our list[2] or filing an issue in pagure[3] Regards, Tomas Hrcka fas: humaton LiberaChat: jednorozec [1] https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html [2] https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ [3] https://pagure.io/releng/ -- Tomas Hrcka role: CPE Team - Senior Software Engineer fas: humaton freenode: jednorozec ___ 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 35 Mass Rebuild
Can the packagers fix the failures in the f35-rebuild side tag by themselves > while the rebuild is in progress, or do they have to wait on merging the > tag? > > So I am unable to find any policy on this. But assuming that the mass rebuilds bump spec, the packager should be fine with creating a new release. -- Tomas Hrcka role: CPE Team - Senior Software Engineer fas: humaton freenode: jednorozec ___ 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 35 Mass Rebuild
Send updated notification with fixed links. BTW the links became active once the mass rebuild was started. 21.7 10:00 UTC On Tue, Jul 20, 2021 at 6:24 PM Zbigniew Jędrzejewski-Szmek < zbys...@in.waw.pl> wrote: > On Tue, Jul 20, 2021 at 06:02:38PM +0200, Tomas Hrcka wrote: > > Hi all, > > > > Per the Fedora 35 schedule[1] we will start a mass rebuild for Fedora 35 > > on Jul 21st, 2021. We will run a mass rebuild for Fedora 35 for the > > changes listed in: > > > > https://pagure.io/releng/issues?status=Open=mass+rebuild > > > > The mass rebuild will be done in a side tag (f35-rebuild) and moved over > > when completed. > > > > Failures can be seen > > https://kojipkgs.fedoraproject.org/mass-rebuild/f35-failures.html > > 404 > > > <https://kojipkgs.fedoraproject.org/mass-rebuild/f34-failures.html> > > -ESTALE ;( > > > > Things still needing rebuilding > > https://kojipkgs.fedoraproject.org/mass-rebuild/f35-need-rebuild.html > > 404 > > > <https://kojipkgs.fedoraproject.org/mass-rebuild/f34-need-rebuild.html> > > -ESTALE too. > > Zbyszek > ___ > 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 > -- Tomas Hrcka role: CPE Team - Senior Software Engineer fas: humaton freenode: jednorozec ___ 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 Rebuild
Hi all, Per the Fedora 35 schedule[1] we will start a mass rebuild for Fedora 35 on Jul 21st, 2021. We will run a mass rebuild for Fedora 35 for the changes listed in: https://pagure.io/releng/issues?status=Open=mass+rebuild The mass rebuild will be done in a side tag (f35-rebuild) and moved over when completed. Failures can be seen https://kojipkgs.fedoraproject.org/mass-rebuild/f35-failures.html <https://kojipkgs.fedoraproject.org/mass-rebuild/f34-failures.html> Things still needing rebuilding https://kojipkgs.fedoraproject.org/mass-rebuild/f35-need-rebuild.html <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 Libera.Chat, by dropping an email to our list[2] or filing an issue in pagure[3] Regards, Tomas Hrcka fas: humaton LiberaChat: jednorozec [1] https://fedorapeople.org/groups/schedule/f-35/f-35-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 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 Rebuild
Hi all, Per the Fedora 35 schedule[1] we will start a mass rebuild for Fedora 35 on Jul 21st, 2021. We will run a mass rebuild for Fedora 35 for the changes listed in: https://pagure.io/releng/issues?status=Open=mass+rebuild The mass rebuild will be done in a side tag (f35-rebuild) and moved over when completed. Failures can be seen https://kojipkgs.fedoraproject.org/mass-rebuild/f35-failures.html <https://kojipkgs.fedoraproject.org/mass-rebuild/f34-failures.html> Things still needing rebuilding https://kojipkgs.fedoraproject.org/mass-rebuild/f35-need-rebuild.html <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 Libera.Chat, by dropping an email to our list[2] or filing an issue in pagure[3] Regards, Tomas Hrcka fas: humaton LiberaChat: jednorozec [1] https://fedorapeople.org/groups/schedule/f-35/f-35-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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Branching in the container namespace
Hello all, we got a ticket[1] raised with release engineering regarding branching container namespace in distgit. We don't branch container namespace as we initially thought we will let maintainers decide whether they want the repo to be branched or not. We would like to get some feedback from container developers if there is any value for you in having containers branched with every Fedora release? [1] - https://pagure.io/releng/issue/10162 -- Tomas Hrcka role: CPE Team - Senior Software Engineer fas: humaton libera: jednorozec ___ 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
[Test-Announce] Fedora 34 bodhi activation point
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 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 Alpha 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 Alpha composes. Other builds will remain in updates-testing until the Alpha release is approved, at which point the Alpha freeze is lifted and packages can move to 'stable' as usual until the Beta 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'. Regards Tomas Hrcka [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 -- Tomas Hrcka role: CPE Team - Senior Software Engineer fas: humaton freenode: jednorozec ___ 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
Re: F33 beta: where are my Rust packages?
Hi, this was during the branching. Looking into releng scripts[1] we are skipping rust-* packages. [ 1 ] - https://pagure.io/releng/blob/master/f/scripts/pdc/create-new-release-branches.py#_60 On Wed, Sep 30, 2020 at 11:43 AM Petr Pisar wrote: > On Tue, Sep 29, 2020 at 09:56:22PM -, Artur Frenszek-Iwicki wrote: > > I maintain two Rust packages, rust-copydeps [1] and rust-desed [2]. Both > > were built for F33 ([3], [4]) before it branched off for Rawhide (and > > submitted to bodhi ([5], [6])). I gave the F33 beta a spin and when I > tried > > "dnf install copydeps desed", I got no matches. Other Rust packages, like > > rust-exa and rust-ytop, install fine. > > > > Was there some change to the Rust packaging process that I missed? If > not, > > why are the packages not available? > > > There is only one build of rust-copydeps and that is > rust-copydeps-5.0.0-1.fc33. Let's see its history: > > $ koji list-history --build rust-copydeps-5.0.0-1.fc33 > Fri Jul 31 12:19:34 2020 rust-copydeps-5.0.0-1.fc33 tagged into > f33-updates-candidate by suve > Fri Jul 31 12:19:37 2020 rust-copydeps-5.0.0-1.fc33 tagged into > f33-signing-pending by bodhi > Fri Jul 31 12:19:50 2020 rust-copydeps-5.0.0-1.fc33 untagged from > f33-signing-pending by autopen > Fri Jul 31 12:19:50 2020 rust-copydeps-5.0.0-1.fc33 tagged into > f33-updates-testing-pending by autopen > Fri Jul 31 12:21:50 2020 rust-copydeps-5.0.0-1.fc33 untagged from > f33-updates-testing-pending by bodhi > Fri Jul 31 12:21:52 2020 rust-copydeps-5.0.0-1.fc33 untagged from > f33-updates-candidate by bodhi > Fri Jul 31 12:21:52 2020 rust-copydeps-5.0.0-1.fc33 tagged into f33 by > bodhi > Tue Aug 11 23:28:56 2020 rust-copydeps-5.0.0-1.fc33 tagged into f34 by > humaton [still active] > Tue Aug 11 23:32:07 2020 rust-copydeps-5.0.0-1.fc33 untagged from f33 by > humaton > > I can see it got into F33 on 2020-07-31, but humaton user (CCed) moved the > build from F33 into F34 on 2020-08-11. I have no idea why he did it. I > hazily > recall Rust packaging had issues with having the same build in multiple > Fedoras and now there is a proposal how to improve it. > > -- Petr > -- Tomas Hrcka Freenode: jednorozec #fedora-releng #fedora-devel #fedora-cs ___ 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
Bodhi Activation point
Hi all, Today's an important day on the Fedora 33 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 33 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 '100% code complete deadline' Change Checkpoint[5], meaning that Fedora 33 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 33. Tomas Hrcka jednorozec on FreeNode #fedora-releng #fedora-devel #fedora-cs [1] https://fedorapeople.org/groups/schedule/f-33/f-33-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] Bodhi Activation point
Hi all, Today's an important day on the Fedora 33 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 33 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 '100% code complete deadline' Change Checkpoint[5], meaning that Fedora 33 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 33. Tomas Hrcka jednorozec on FreeNode #fedora-releng #fedora-devel #fedora-cs [1] https://fedorapeople.org/groups/schedule/f-33/f-33-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
