Re: F40 Change Proposal: Pytorch Release (Self-Contained)
On Thursday, January 11, 2024, Aoife Moloney wrote: > > == Benefit to Fedora == > > This change will introduce PyTorch, a high demand machine learning > framework, to Fedora. PyTorch is widely used for tasks such as image > and speech recognition, natural language processing, and other > artificial intelligence applications, providing a user-friendly > interface for building and experimenting with complex machine learning > models. This is for CPU (x86_64 and aarch64) only and is the first > release for Fedora. The current development effort is focused on AMD > GPU acceleration. > > > What does this mean? Is it now CPU only or does it support AMD GPUs? CPU only would be of limited use and people would most likely just use pip instead. -- ___ 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
[EPEL-devel] Fedora EPEL 8 updates-testing report
The following Fedora EPEL 8 Security updates need testing: Age URL 8 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-3a29f0d349 python-paramiko-2.12.0-2.el8 6 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-fe4d2e754f zabbix6.0-6.0.25-1.el8 6 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-39ec948d57 chromium-120.0.6099.199-1.el8 1 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-d565ced023 gtkwave-3.3.118-1.el8 The following builds have been pushed to Fedora EPEL 8 updates-testing ansible-collection-awx-awx-23.6.0-1.el8 mock-core-configs-39.4-1.el8 python-rpmautospec-core-0.1.4-1.el8 python-virt-firmware-24.1.1-2.el8 python39-jinja2-epel-3.1.3-1.el8.1 Details about builds: ansible-collection-awx-awx-23.6.0-1.el8 (FEDORA-EPEL-2024-5bad953649) Ansible modules and plugins for working with AWX Update Information: Update to 23.6.0 ChangeLog: * Thu Jan 11 2024 Andrew Heath - 23.6.0-1 - Update to 23.6.0 mock-core-configs-39.4-1.el8 (FEDORA-EPEL-2024-cc5dabbb29) Mock core config files basic chroots Update Information: https://rpm-software-management.github.io/mock/Release-Notes-Configs-39.4 ChangeLog: * Thu Jan 11 2024 Pavel Raiskup 39.4-1 - configure system_cachedir for dnf5 - configs: EOL Fedora 37 - config: add README.md with maintainers and issue trackers (fros...@email.cz) python-rpmautospec-core-0.1.4-1.el8 (FEDORA-EPEL-2024-5e28494740) Minimum functionality for rpmautospec Update Information: This update fixes a bug in the test suite which prevented the package from being built for EPEL8 and another which prevents it from disabling caching in long- running processes. ChangeLog: * Tue Jan 9 2024 Nils Philippsen - 0.1.4-1 - Update to 0.1.4 * Fri Jan 5 2024 Nils Philippsen - 0.1.3-1 - Update to 0.1.3 * Fri Dec 15 2023 Nils Philippsen - 0.1.2-1 - Update to 0.1.2 * Sun Dec 3 2023 Yaakov Selkowitz - 0.1.1-8 - Always disable test coverage checks python-virt-firmware-24.1.1-2.el8 (FEDORA-EPEL-2024-8747f5bb28) Tools for virtual machine firmware volumes Update Information: update to version 24.1.1 update to version 24.1 ChangeLog: * Wed Jan 10 2024 Gerd Hoffmann - 24.1.1-2 - add pe test script * Wed Jan 10 2024 Gerd Hoffmann - 24.1.1-1 - update to version 24.1.1 * Tue Jan 9 2024 Gerd Hoffmann - 24.1-2 - add pe-inspect manpage to file list * Tue Jan 9 2024 Gerd Hoffmann - 24.1-1 - update to version 24.1 python39-jinja2-epel-3.1.3-1.el8.1 (FEDORA-EPEL-2024-0ffe88f330) General purpose template engine Update Information: Security fix for CVE-2024-22195 ChangeLog: * Thu Jan 11 2024 Michel Lind - 3.1.3-1.1 - Rebase EPEL 8's Python 3.9 to pick up CVE fix * Thu Jan 11 2024 Michel Lind - 3.1.3-1 - Update to 3.1.3 to fix CVE-2024-22195 * Tue Aug 8 2023 Karolina Surma - 3.1.2-6 - Declare the license as an SPDX expression * Fri Jul 21 2023 Fedora Release Engineering - 3.1.2-5 - Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild * Fri Jun 16 2023 Python Maint - 3.1.2-4 - Rebuilt for Python 3.12 * Tue Jun 13 2023 Python Maint - 3.1.2-3 - Bootstrap for Python 3.12 * Fri May 19 2023 Yaakov Selkowitz - 3.1.2-2 - Disable docs by default in RHEL builds * Mon May 1 2023 Sandro Mani - 3.1.2-1 - Update to 3.1.2 References: [ 1 ] Bug #2257854 - CVE-2024-22195 jinja2: HTML attribute
[Bug 2256327] perl-CPAN-Perl-Releases-5.20231230 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2256327 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-CPAN-Perl-Releases-5.2 |perl-CPAN-Perl-Releases-5.2 |0231230-1.fc40 |0231230-1.fc40 |perl-CPAN-Perl-Releases-5.2 |perl-CPAN-Perl-Releases-5.2 |0231230-1.fc38 |0231230-1.fc38 ||perl-CPAN-Perl-Releases-5.2 ||0231230-1.fc39 --- Comment #8 from Fedora Update System --- FEDORA-2024-280e803476 has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2256327 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202256327%23c8 -- ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2256323] perl-Module-CoreList-5.20231230 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2256323 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-Module-CoreList-5.2023 |perl-Module-CoreList-5.2023 |1230-1.fc40 |1230-1.fc40 |perl-Module-CoreList-5.2023 |perl-Module-CoreList-5.2023 |1230-1.fc38 |1230-1.fc38 ||perl-Module-CoreList-5.2023 ||1230-1.fc39 --- Comment #8 from Fedora Update System --- FEDORA-2024-219e7bdedd has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2256323 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202256323%23c8 -- ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2256327] perl-CPAN-Perl-Releases-5.20231230 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2256327 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-CPAN-Perl-Releases-5.2 |perl-CPAN-Perl-Releases-5.2 |0231230-1.fc40 |0231230-1.fc40 ||perl-CPAN-Perl-Releases-5.2 ||0231230-1.fc38 --- Comment #7 from Fedora Update System --- FEDORA-2024-e332317e43 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2256327 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202256327%23c7 -- ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2256272] perl-DateTime-TimeZone-2.61 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2256272 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-DateTime-TimeZone-2.61 |perl-DateTime-TimeZone-2.61 |-1.fc40 |-1.fc40 |perl-DateTime-TimeZone-2.61 |perl-DateTime-TimeZone-2.61 |-1.fc39 |-1.fc39 ||perl-DateTime-TimeZone-2.61 ||-1.fc38 --- Comment #7 from Fedora Update System --- FEDORA-2024-2db7d73c8a has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2256272 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202256272%23c7 -- ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2256323] perl-Module-CoreList-5.20231230 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2256323 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-Module-CoreList-5.2023 |perl-Module-CoreList-5.2023 |1230-1.fc40 |1230-1.fc40 ||perl-Module-CoreList-5.2023 ||1230-1.fc38 --- Comment #7 from Fedora Update System --- FEDORA-2024-44853e6956 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2256323 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202256323%23c7 -- ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Unretiring pgRouting
Hi all, I would like to unretire pgRouting. pgRouting was orphaned and retired because of a problem in the packet requirements specification at the time [1]. Since I use this PostgreSQL extension at work, I wanted to reintroduce it in Fedora instead of using docker containers or custom packages for development. I have just filed a re-review request on bugzilla [2]. Reviewers are welcome :D. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1927162 [2] https://bugzilla.redhat.com/show_bug.cgi?id=2257974 Hussein -- ___ 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
[Bug 2257961] New: perl-Business-ISBN-Data-20240111.001 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2257961 Bug ID: 2257961 Summary: perl-Business-ISBN-Data-20240111.001 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Business-ISBN-Data Keywords: FutureFeature, Triaged Assignee: jples...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: jples...@redhat.com, ka...@ucw.cz, mspa...@redhat.com, p...@city-fan.org, perl-devel@lists.fedoraproject.org Target Milestone: --- Classification: Fedora Releases retrieved: 20240111.001 Upstream release that is considered latest: 20240111.001 Current version/release in rawhide: 20231220.001-1.fc40 URL: https://metacpan.org/dist/Business-ISBN-Data/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/2674/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/perl-Business-ISBN-Data -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2257961 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202257961%23c0 -- ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
F40 Change Proposal: Replace iotop with iotop-c (Self-Contained)
Wiki -> https://fedoraproject.org/wiki/Changes/Replace_iotop_with_iotop-c This is a proposed Change for Fedora Linux. This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee. == Summary == Replace (obsolete) iotop with iotop-c == Owner == * Name: [[User:mhlavink| Michal Hlavinka]] * Email: mhlavink[at]redhat[dot]com * Name: [[User:bbonev | Boian Bonev]] * Email: bbonev1[at]ipacct[dot]com == Detailed Description == iotop's upstream does not seem to be active much. Latest version is 0.6 that was released 10 years ago. There were some commits once a while after that, but not much. There is better maintained iotop-c implementation that was originally created for embedded systems. It has small footprint being written in C and not in python. It is a drop in replacement. It's actively developed, has good history of resolving issues, has more features, improved UI (yet almost the same look) and uses the same command line arguments. In short, we (iotop and iotop-c maintainers) have decided to replace iotop with iotop-c. iotop-c will provide iotop (name) and iotop binary and obsolete original iotop. If there are no issues found, original iotop will be orphaned. == Feedback == == Benefit to Fedora == iotop-c implementation has smaller footprint, more features, polished UI, uses same command line arguments and has active upstream that has history of quickly resolving issues. == Scope == * Proposal owners: 1) update iotop-c spec file to obsolete iotop, provide iotop name and provide iotop binary 2) orphan iotop * Other developers: N/A * Policies and guidelines: N/A (not needed for this Change) * Trademark approval: N/A (not needed for this Change) * Alignment with Community Initiatives: == Upgrade/compatibility impact == == How To Test == A) before change happens - just install iotop-c and give it a try B) after change happens install iotop, check that you have iotop-c version installed and it works you can also check that iotop (if installed previously) is automatically replaced by iotop-c during update == User Experience == iotop-c has slightly different UI look, more polished. It also consumes less resources. == Dependencies == none == Contingency Plan == Worst case scenario, we can easily revert the change, but we don't expect any issues as iotop-c isn't that new. It is already present in current Fedora releases as well as other Linux distributions. == Documentation == N/A (not a System Wide Change) == Release Notes == -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney -- ___ 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
F40 Change Proposal: Replace iotop with iotop-c (Self-Contained)
Wiki -> https://fedoraproject.org/wiki/Changes/Replace_iotop_with_iotop-c This is a proposed Change for Fedora Linux. This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee. == Summary == Replace (obsolete) iotop with iotop-c == Owner == * Name: [[User:mhlavink| Michal Hlavinka]] * Email: mhlavink[at]redhat[dot]com * Name: [[User:bbonev | Boian Bonev]] * Email: bbonev1[at]ipacct[dot]com == Detailed Description == iotop's upstream does not seem to be active much. Latest version is 0.6 that was released 10 years ago. There were some commits once a while after that, but not much. There is better maintained iotop-c implementation that was originally created for embedded systems. It has small footprint being written in C and not in python. It is a drop in replacement. It's actively developed, has good history of resolving issues, has more features, improved UI (yet almost the same look) and uses the same command line arguments. In short, we (iotop and iotop-c maintainers) have decided to replace iotop with iotop-c. iotop-c will provide iotop (name) and iotop binary and obsolete original iotop. If there are no issues found, original iotop will be orphaned. == Feedback == == Benefit to Fedora == iotop-c implementation has smaller footprint, more features, polished UI, uses same command line arguments and has active upstream that has history of quickly resolving issues. == Scope == * Proposal owners: 1) update iotop-c spec file to obsolete iotop, provide iotop name and provide iotop binary 2) orphan iotop * Other developers: N/A * Policies and guidelines: N/A (not needed for this Change) * Trademark approval: N/A (not needed for this Change) * Alignment with Community Initiatives: == Upgrade/compatibility impact == == How To Test == A) before change happens - just install iotop-c and give it a try B) after change happens install iotop, check that you have iotop-c version installed and it works you can also check that iotop (if installed previously) is automatically replaced by iotop-c during update == User Experience == iotop-c has slightly different UI look, more polished. It also consumes less resources. == Dependencies == none == Contingency Plan == Worst case scenario, we can easily revert the change, but we don't expect any issues as iotop-c isn't that new. It is already present in current Fedora releases as well as other Linux distributions. == Documentation == N/A (not a System Wide Change) == Release Notes == -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney -- ___ 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
F40 Change Proposal: ROCm 6 Release (Self-Contained)
Wiki -> https://fedoraproject.org/wiki/Changes/ROCm6Release This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee. == Summary == The AMD ROCm™ 6.0 is the latest release of AMD’s software optimized for AI and HPC workload performance on AMD GPU’s. This latest release enables the newest flagship datacenter GPU the AMD Instinct™ MI300 as well as continuing the GPUs enabled in their last 5.x release, most/all of their recent GPUs. == Owner == The owners of this change are the HC SIG (https://fedoraproject.org/wiki/SIGs/HC) * Name: [[User:trix| Tom Rix]] * Email: t...@redhat.com == Detailed Description == The benefits for frogs include: ROCm 6 has expanded support for AMD Instinct™ MI300A and MI300X. It includes highly optimized attention algorithms, and proven collective communications libraries, as well as optimized performance for FP8 support in PyTorch and hipblasLT. It includes prepackaged HPC and AI/ML frameworks with streamlined and improved tools from AMD Infinity Hub. == Feedback == There has been positive feedback from the community for the ease of using and developing GPU accelerated applications within Fedora. Because of the interest in AI, the community has requested that ROCm support be added to PyTorch and other AI applications and frameworks. To address this feedback several packages are in the process of being added to Fedora including rocFFT rocSolver hipBLASLt MiOpen == Benefit to Fedora == Fedora has finally end-to-end open source GPU acceleration. The GPU hardware driver is in the linux kernel. The compiler is the system clang. The ROCm software stack provides the higher level libraries that enable other Fedora packages and user applications to be built entirely with Fedora. == Scope == * Proposal owners: The feature owners accomplished packaging the new version of ROCm 6 for Fedora. This provides basic accelerated functionally that should be used by any package that can take advantage of it. * Other developers: If your package or application used the older version of ROCm 5.7.1 or older, you must verify that you can use the new version of ROCm, 6.0 is a major version change. The ROCm packages are known to build in Rawhide, no additional effort is required. * Policies and guidelines: N/A (not needed for this Change) * Trademark approval: N/A (not needed for this Change) * Alignment with Community Initiatives: Yes, it aligns with the current Fedora Community Initiatives. == Upgrade/compatibility impact == No hardware was dropped. == How To Test == Installation instructions can be found here (https://fedoraproject.org/wiki/SIGs/HC#Installation). This is by and large a system library change and not directly visible to the user. == Dependencies == The basic work has been completed. == Contingency Plan == The basic work has been completed. == Documentation == Documentation can be found here (https://rocm.docs.amd.com/en/latest/) == Release Notes == -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney -- ___ 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
F40 Change Proposal: ROCm 6 Release (Self-Contained)
Wiki -> https://fedoraproject.org/wiki/Changes/ROCm6Release This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee. == Summary == The AMD ROCm™ 6.0 is the latest release of AMD’s software optimized for AI and HPC workload performance on AMD GPU’s. This latest release enables the newest flagship datacenter GPU the AMD Instinct™ MI300 as well as continuing the GPUs enabled in their last 5.x release, most/all of their recent GPUs. == Owner == The owners of this change are the HC SIG (https://fedoraproject.org/wiki/SIGs/HC) * Name: [[User:trix| Tom Rix]] * Email: t...@redhat.com == Detailed Description == The benefits for frogs include: ROCm 6 has expanded support for AMD Instinct™ MI300A and MI300X. It includes highly optimized attention algorithms, and proven collective communications libraries, as well as optimized performance for FP8 support in PyTorch and hipblasLT. It includes prepackaged HPC and AI/ML frameworks with streamlined and improved tools from AMD Infinity Hub. == Feedback == There has been positive feedback from the community for the ease of using and developing GPU accelerated applications within Fedora. Because of the interest in AI, the community has requested that ROCm support be added to PyTorch and other AI applications and frameworks. To address this feedback several packages are in the process of being added to Fedora including rocFFT rocSolver hipBLASLt MiOpen == Benefit to Fedora == Fedora has finally end-to-end open source GPU acceleration. The GPU hardware driver is in the linux kernel. The compiler is the system clang. The ROCm software stack provides the higher level libraries that enable other Fedora packages and user applications to be built entirely with Fedora. == Scope == * Proposal owners: The feature owners accomplished packaging the new version of ROCm 6 for Fedora. This provides basic accelerated functionally that should be used by any package that can take advantage of it. * Other developers: If your package or application used the older version of ROCm 5.7.1 or older, you must verify that you can use the new version of ROCm, 6.0 is a major version change. The ROCm packages are known to build in Rawhide, no additional effort is required. * Policies and guidelines: N/A (not needed for this Change) * Trademark approval: N/A (not needed for this Change) * Alignment with Community Initiatives: Yes, it aligns with the current Fedora Community Initiatives. == Upgrade/compatibility impact == No hardware was dropped. == How To Test == Installation instructions can be found here (https://fedoraproject.org/wiki/SIGs/HC#Installation). This is by and large a system library change and not directly visible to the user. == Dependencies == The basic work has been completed. == Contingency Plan == The basic work has been completed. == Documentation == Documentation can be found here (https://rocm.docs.amd.com/en/latest/) == Release Notes == -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney -- ___ 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
F40 Change Proposal: Pytorch Release (Self-Contained)
Wiki -> https://fedoraproject.org/wiki/Changes/PytorchRelese This is a proposed Change for Fedora Linux. This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee. == Summary == This change will bring the first iteration of PyTorch to Fedora. == Owner == This project is owned by the https://fedoraproject.org/wiki/SIGs/PyTorch. * Name: [[User:trix| Tom Rix]] * Email: t...@redhat.com == Detailed Description == The goal of packaging PyTorch for Fedora is to make this open-source machine learning framework easily accessible and seamlessly integrable within the Fedora Linux ecosystem. By providing PyTorch as a packaged software in the Fedora repositories, users gain simplified installation and maintenance processes. This enhances the accessibility of PyTorch for Fedora users, fostering a conducive environment for developers, researchers, and enthusiasts to leverage the capabilities of this powerful machine learning framework. Additionally, packaging PyTorch for Fedora contributes to the broader open-source community by promoting collaborative development and innovation in the field of machine learning on the Fedora platform. == Feedback == The PyTorch SIG meets bi weekly, contributing to the meeting is the best way to engage with what is happening. TBD: Add how to join. The feedback so far has been positive with some high level feature requests. GPU Acceleration More packages that use PyTorch Improving base PyTorch == Benefit to Fedora == This change will introduce PyTorch, a high demand machine learning framework, to Fedora. PyTorch is widely used for tasks such as image and speech recognition, natural language processing, and other artificial intelligence applications, providing a user-friendly interface for building and experimenting with complex machine learning models. This is for CPU (x86_64 and aarch64) only and is the first release for Fedora. The current development effort is focused on AMD GPU acceleration. == Scope == * Proposal owners: This change does not affect other parts of the distribution and is an isolated change. * Other developers: To install use > dnf install python-torch * Release engineering: N/A (not needed for this Change) * Policies and guidelines: N/A (not needed for this Change) * Trademark approval: N/A (not needed for this Change) * Alignment with Community Initiatives: Yes == Upgrade/compatibility impact == This is the first time this package has been available. == How To Test == The PyTorch code base is very large, start with the public examples described here https://pytorch.org/tutorials/beginner/pytorch_with_examples.html == User Experience == How the user installs PyTorch changes from > pip install torch To > dnf install python-torch The pip install requires local building which may fail and will not be consistent from machine to machine. Dnf will always succeed and be consistent. == Dependencies == PyTorch is available for Rawhide. == Contingency Plan == * Contingency mechanism: PyTorch is available for Rawhide. * Contingency deadline: N/A (not a System Wide Change) * Blocks release? N/A (not a System Wide Change) == Documentation == There is a wealth of online and print documentation available. A good place to start is the main project page https://pytorch.org/ == Release Notes == PyTorch 2.1.2 and some supporting packages are available in F40 -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney -- ___ 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
F40 Change Proposal: Pytorch Release (Self-Contained)
Wiki -> https://fedoraproject.org/wiki/Changes/PytorchRelese This is a proposed Change for Fedora Linux. This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee. == Summary == This change will bring the first iteration of PyTorch to Fedora. == Owner == This project is owned by the https://fedoraproject.org/wiki/SIGs/PyTorch. * Name: [[User:trix| Tom Rix]] * Email: t...@redhat.com == Detailed Description == The goal of packaging PyTorch for Fedora is to make this open-source machine learning framework easily accessible and seamlessly integrable within the Fedora Linux ecosystem. By providing PyTorch as a packaged software in the Fedora repositories, users gain simplified installation and maintenance processes. This enhances the accessibility of PyTorch for Fedora users, fostering a conducive environment for developers, researchers, and enthusiasts to leverage the capabilities of this powerful machine learning framework. Additionally, packaging PyTorch for Fedora contributes to the broader open-source community by promoting collaborative development and innovation in the field of machine learning on the Fedora platform. == Feedback == The PyTorch SIG meets bi weekly, contributing to the meeting is the best way to engage with what is happening. TBD: Add how to join. The feedback so far has been positive with some high level feature requests. GPU Acceleration More packages that use PyTorch Improving base PyTorch == Benefit to Fedora == This change will introduce PyTorch, a high demand machine learning framework, to Fedora. PyTorch is widely used for tasks such as image and speech recognition, natural language processing, and other artificial intelligence applications, providing a user-friendly interface for building and experimenting with complex machine learning models. This is for CPU (x86_64 and aarch64) only and is the first release for Fedora. The current development effort is focused on AMD GPU acceleration. == Scope == * Proposal owners: This change does not affect other parts of the distribution and is an isolated change. * Other developers: To install use > dnf install python-torch * Release engineering: N/A (not needed for this Change) * Policies and guidelines: N/A (not needed for this Change) * Trademark approval: N/A (not needed for this Change) * Alignment with Community Initiatives: Yes == Upgrade/compatibility impact == This is the first time this package has been available. == How To Test == The PyTorch code base is very large, start with the public examples described here https://pytorch.org/tutorials/beginner/pytorch_with_examples.html == User Experience == How the user installs PyTorch changes from > pip install torch To > dnf install python-torch The pip install requires local building which may fail and will not be consistent from machine to machine. Dnf will always succeed and be consistent. == Dependencies == PyTorch is available for Rawhide. == Contingency Plan == * Contingency mechanism: PyTorch is available for Rawhide. * Contingency deadline: N/A (not a System Wide Change) * Blocks release? N/A (not a System Wide Change) == Documentation == There is a wealth of online and print documentation available. A good place to start is the main project page https://pytorch.org/ == Release Notes == PyTorch 2.1.2 and some supporting packages are available in F40 -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney -- ___ 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
sd_notify in mock
Working on update of rubygem-puma, I observe following test failure trying build rubygem-rails in Mock: ~~~ /usr/share/ruby/socket.rb:68:in `connect': Errno::EACCES: Permission denied - connect(2) for /run/host/notify (Puma::SdNotify::NotifyError) from /usr/share/ruby/socket.rb:68:in `connect_internal' from /usr/share/ruby/socket.rb:141:in `connect' from /usr/share/gems/gems/puma-6.4.2/lib/puma/sd_notify.rb:140:in `notify' from /usr/share/gems/gems/puma-6.4.2/lib/puma/sd_notify.rb:53:in `ready' from /usr/share/gems/gems/puma-6.4.2/lib/puma/plugin/systemd.rb:17:in `block in start' from /usr/share/gems/gems/puma-6.4.2/lib/puma/events.rb:17:in `block in fire' from /usr/share/gems/gems/puma-6.4.2/lib/puma/events.rb:17:in `each' from /usr/share/gems/gems/puma-6.4.2/lib/puma/events.rb:17:in `fire' from /usr/share/gems/gems/puma-6.4.2/lib/puma/events.rb:46:in `fire_on_booted!' from /usr/share/gems/gems/puma-6.4.2/lib/puma/single.rb:58:in `run' from /usr/share/gems/gems/puma-6.4.2/lib/puma/launcher.rb:194:in `run' from /usr/share/gems/gems/puma-6.4.2/lib/rack/handler/puma.rb:76:in `run' from /usr/share/gems/gems/rack-2.2.4/lib/rack/server.rb:327:in `start' from /builddir/build/BUILD/railties-7.0.8/usr/share/gems/gems/railties-7.0.8/lib/rails/commands/server/server_command.rb:38:in `start' from /builddir/build/BUILD/railties-7.0.8/usr/share/gems/gems/railties-7.0.8/lib/rails/commands/server/server_command.rb:143:in `block in perform' from :90:in `tap' from /builddir/build/BUILD/railties-7.0.8/usr/share/gems/gems/railties-7.0.8/lib/rails/commands/server/server_command.rb:134:in `perform' from /usr/share/gems/gems/thor-1.2.1/lib/thor/command.rb:27:in `run' from /usr/share/gems/gems/thor-1.2.1/lib/thor/invocation.rb:127:in `invoke_command' from /usr/share/gems/gems/thor-1.2.1/lib/thor.rb:392:in `dispatch' from /builddir/build/BUILD/railties-7.0.8/usr/share/gems/gems/railties-7.0.8/lib/rails/command/base.rb:87:in `perform' from /builddir/build/BUILD/railties-7.0.8/usr/share/gems/gems/railties-7.0.8/lib/rails/command.rb:48:in `invoke' from /builddir/build/BUILD/railties-7.0.8/usr/share/gems/gems/railties-7.0.8/lib/rails/commands.rb:18:in `' from /usr/share/ruby/bundled_gems.rb:74:in `require' from /usr/share/ruby/bundled_gems.rb:74:in `block (2 levels) in replace_require' from bin/rails:4:in `' /usr/share/ruby/socket.rb:68:in `connect': Permission denied - connect(2) for /run/host/notify (Errno::EACCES) from /usr/share/ruby/socket.rb:68:in `connect_internal' from /usr/share/ruby/socket.rb:141:in `connect' from /usr/share/gems/gems/puma-6.4.2/lib/puma/sd_notify.rb:140:in `notify' from /usr/share/gems/gems/puma-6.4.2/lib/puma/sd_notify.rb:53:in `ready' from /usr/share/gems/gems/puma-6.4.2/lib/puma/plugin/systemd.rb:17:in `block in start' from /usr/share/gems/gems/puma-6.4.2/lib/puma/events.rb:17:in `block in fire' from /usr/share/gems/gems/puma-6.4.2/lib/puma/events.rb:17:in `each' from /usr/share/gems/gems/puma-6.4.2/lib/puma/events.rb:17:in `fire' from /usr/share/gems/gems/puma-6.4.2/lib/puma/events.rb:46:in `fire_on_booted!' from /usr/share/gems/gems/puma-6.4.2/lib/puma/single.rb:58:in `run' from /usr/share/gems/gems/puma-6.4.2/lib/puma/launcher.rb:194:in `run' from /usr/share/gems/gems/puma-6.4.2/lib/rack/handler/puma.rb:76:in `run' from /usr/share/gems/gems/rack-2.2.4/lib/rack/server.rb:327:in `start' from /builddir/build/BUILD/railties-7.0.8/usr/share/gems/gems/railties-7.0.8/lib/rails/commands/server/server_command.rb:38:in `start' from /builddir/build/BUILD/railties-7.0.8/usr/share/gems/gems/railties-7.0.8/lib/rails/commands/server/server_command.rb:143:in `block in perform' from :90:in `tap' from /builddir/build/BUILD/railties-7.0.8/usr/share/gems/gems/railties-7.0.8/lib/rails/commands/server/server_command.rb:134:in `perform' from /usr/share/gems/gems/thor-1.2.1/lib/thor/command.rb:27:in `run' from /usr/share/gems/gems/thor-1.2.1/lib/thor/invocation.rb:127:in `invoke_command' from /usr/share/gems/gems/thor-1.2.1/lib/thor.rb:392:in `dispatch' from /builddir/build/BUILD/railties-7.0.8/usr/share/gems/gems/railties-7.0.8/lib/rails/command/base.rb:87:in `perform' from /builddir/build/BUILD/railties-7.0.8/usr/share/gems/gems/railties-7.0.8/lib/rails/command.rb:48:in `invoke' from /builddir/build/BUILD/railties-7.0.8/usr/share/gems/gems/railties-7.0.8/lib/rails/commands.rb:18:in `' from /usr/share/ruby/bundled_gems.rb:74:in `require' from /usr/share/ruby/bundled_gems.rb:74:in `block (2 levels) in replace_require' from bin/rails:4:in `' . ~~~ The full log is available here for the moment: https://copr.fedorainfracloud.org/coprs/vondruch/mpb/build/6885294/ This is the sd_notify source code:
[EPEL-devel] Re: Orphaning python-mistune on EPEL
On 11.01.2024 11:23, Miro Hrončok wrote: On 10. 01. 24 22:16, Michel Lind wrote: Hi Miro, On Wed, Jan 10, 2024 at 02:51:33PM +0100, Miro Hrončok wrote: Hello, I recently took python-mistune in Fedora. I am not interested in maintaining it in EPEL. It is branched for epel7, epel8 and epel9. @epel-packagers-sig is a collaborator so I assume somebody built this in epel9 without taking responsibility. There is a low impact CVE: https://bugzilla.redhat.com/show_bug.cgi?id=2112231 If somebody want to maintain it, let me know and I'll make you the epel point of contact. Please mark me as the EPEL POC. Already marked Neil. Neil, let me know if I should change it. No worries -- Michel and I discussed this in the EPEL steering committee meeting yesterday and will be working on this together. I think since EPEL-Packagers-SIG already has access, this should be sufficient. Thank you! --Neil -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok signature.asc Description: PGP signature -- ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
qmltermwidget license correction
Hi all, the license tag on qmltermwidget [0] has been corrected from: GPL2+ to GPL-2.0-or-later AND LGPL-2.0-or-later The only two consumers of this package in Fedora repos are: - cool-retro-term - qmlkonsole Cheers, A.FI. [0] https://src.fedoraproject.org/rpms/qmltermwidget -- ___ 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 rawhide compose report: 20240111.n.0 changes
OLD: Fedora-Rawhide-20240110.n.0 NEW: Fedora-Rawhide-20240111.n.0 = SUMMARY = Added images:4 Dropped images: 1 Added packages: 8 Dropped packages:1 Upgraded packages: 84 Downgraded packages: 0 Size of added packages: 19.72 MiB Size of dropped packages:16.76 MiB Size of upgraded packages: 3.14 GiB Size of downgraded packages: 0 B Size change of upgraded packages: -8.72 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = Image: Silverblue dvd-ostree ppc64le Path: Silverblue/ppc64le/iso/Fedora-Silverblue-ostree-ppc64le-Rawhide-20240111.n.0.iso Image: Workstation live aarch64 Path: Workstation/aarch64/iso/Fedora-Workstation-Live-aarch64-Rawhide-20240111.n.0.iso Image: Kinoite dvd-ostree ppc64le Path: Kinoite/ppc64le/iso/Fedora-Kinoite-ostree-ppc64le-Rawhide-20240111.n.0.iso Image: Container_Minimal_Base docker x86_64 Path: Container/x86_64/images/Fedora-Container-Minimal-Base-Rawhide-20240111.n.0.x86_64.tar.xz = DROPPED IMAGES = Image: Silverblue dvd-ostree x86_64 Path: Silverblue/x86_64/iso/Fedora-Silverblue-ostree-x86_64-Rawhide-20240110.n.0.iso = ADDED PACKAGES = Package: hyprlang-0.2.1^1.git25da080-1.fc40 Summary: The official implementation library for the hypr config language RPMs:hyprlang hyprlang-devel Size:394.84 KiB Package: libgweather-4.4.0-2.fc40 Summary: A library for weather information RPMs:libgweather libgweather-devel libgweather-doc Size:16.76 MiB Package: mingw-python-blinker-1.6.2-1.fc40 Summary: MinGW Windows Python blinker library RPMs:mingw32-python3-blinker mingw64-python3-blinker Size:76.46 KiB Package: python-tensile-6.0.0-3.fc40 Summary: Tool for creating benchmark-driven backend libraries for GEMMs RPMs:python3-tensile Size:1.56 MiB Package: python-timelib-0.3.0-2.fc40 Summary: Parse english textual date descriptions RPMs:python3-timelib Size:644.44 KiB Package: rust-cookie0.16-0.16.1-1.fc40 Summary: HTTP cookie parsing and cookie jar management RPMs:rust-cookie0.16+aes-gcm-devel rust-cookie0.16+base64-devel rust-cookie0.16+default-devel rust-cookie0.16+hkdf-devel rust-cookie0.16+hmac-devel rust-cookie0.16+key-expansion-devel rust-cookie0.16+percent-encode-devel rust-cookie0.16+percent-encoding-devel rust-cookie0.16+private-devel rust-cookie0.16+rand-devel rust-cookie0.16+secure-devel rust-cookie0.16+sha2-devel rust-cookie0.16+signed-devel rust-cookie0.16+subtle-devel rust-cookie0.16-devel Size:148.38 KiB Package: rust-cookie_store0.16-0.16.2-1.fc40 Summary: Implementation of Cookie storage and retrieval RPMs:rust-cookie_store0.16+default-devel rust-cookie_store0.16+indexmap-devel rust-cookie_store0.16+preserve_order-devel rust-cookie_store0.16-devel Size:58.42 KiB Package: rust-http0.2-0.2.11-1.fc40 Summary: Set of types for representing HTTP requests and responses RPMs:rust-http0.2+default-devel rust-http0.2-devel Size:106.33 KiB = DROPPED PACKAGES = Package: libgweather4-4.4.0-1.fc40 Summary: A library for weather information RPMs:libgweather4 libgweather4-devel libgweather4-devel-doc Size:16.76 MiB = UPGRADED PACKAGES = Package: amarok-2.9.71^git20231231.387c30d-1.fc40 Old package: amarok-2.9.0-16.fc39 Summary: Media player RPMs: amarok amarok-doc amarok-libs amarok-utils Size: 49.27 MiB Size change: -23.17 MiB Changelog: * Tue Jan 02 2024 Yaakov Selkowitz - 2.9.71^20231231git387c30d-1 - Update to KF5-based git snapshot Package: apptainer-1.3.0~rc.1-1.fc40 Old package: apptainer-1.2.5-1.fc40 Summary: Application and environment virtualization formerly known as Singularity RPMs: apptainer apptainer-suid Size: 125.17 MiB Size change: 2.99 MiB Changelog: * Wed Jan 10 2024 Dave Dykstra - 1.3.0~rc.1 - Update to upstream 1.3.0-rc.1 Package: c-ares-1.25.0-1.fc40 Old package: c-ares-1.22.1-1.fc40 Summary: A library that performs asynchronous DNS operations RPMs: c-ares c-ares-devel Size: 1.50 MiB Size change: 52.41 KiB Changelog: * Wed Jan 10 2024 Tom Callaway - 1.25.0-1 - update to 1.25.0 Package: cadical-1:1.9.4-1.fc40 Old package: cadical-1:1.7.4-1.fc40 Summary: Simplified SAT solver RPMs: cadical cadical-devel cadical-libs Size: 1.96 MiB Size change: -266.09 KiB Changelog: * Wed Jan 10 2024 Jerry James - 1:1.9.4-1 - Version 1.9.4 - Stop building for 32-bit x86 Package: chromium-120.0.6099.216-1.fc40 Old package: chromium-120.0.6099.199-1.fc40 Summary: A WebKit (Blink) powered web browser that Google doesn't want you to use RPMs: chromedriver chromium chromium-common chromium-headless Size: 342.29 MiB Size change: 19.59 KiB Changelog: * Wed Jan 10 2024 Than Ngo - 120.0.6099.216-1 - update to 120.0.6099.216 * High CVE-2024-0333: Insufficient data validation in Extensions Package: clipit-1.4.5
[Bug 2246934] perl-Mail-Box-3.010-1.fc40 FTBFS with perl-Mail-Message-3.014: t/505parser-bodymp.t tests fails
https://bugzilla.redhat.com/show_bug.cgi?id=2246934 Petr Pisar changed: What|Removed |Added Assignee|spo...@gmail.com|p...@city-fan.org -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2246934 -- ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2246934] perl-Mail-Box-3.010-1.fc40 FTBFS with perl-Mail-Message-3.014: t/505parser-bodymp.t tests fails
https://bugzilla.redhat.com/show_bug.cgi?id=2246934 Petr Pisar changed: What|Removed |Added Resolution|--- |RAWHIDE Status|NEW |CLOSED Fixed In Version||perl-Mail-Message-3.015-1.f ||c40.noarch Component|perl-Mail-Box |perl-Mail-Message Last Closed||2024-01-11 12:26:29 --- Comment #2 from Petr Pisar --- Indeed. Thanks, Paul. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2246934 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202246934%23c2 -- ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Fedocal] Reminder meeting : ELN SIG
Dear all, You are kindly invited to the meeting: ELN SIG on 2024-01-12 from 12:00:00 to 13:00:00 US/Eastern At fedora-meet...@irc.libera.chat The meeting will be about: Source: https://calendar.fedoraproject.org//meeting/10568/ -- ___ 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: F40 Change Proposal: Run Anaconda dir/image installations only in non-interactive text mode (Self-Contained
On Thu, Jan 11, 2024 at 5:16 AM Aoife Moloney wrote: > > Wiki -> > https://fedoraproject.org/wiki/Changes/Anaconda_dir_and_image_installations_in_automated_text_mode > > == Summary == > > Anaconda will require a fully defined kickstart file for installations > into an image or a directory and these installations will run only in > a non-interactive text-based user interface. > > > == Owner == > > * Name: [[User:vponcova| Vendula Poncova]] > * Email: > * Package: anaconda > > * Name: [[User:bcl| Brian C. Lane]] > * Email: > * Package: lorax (livemedia-creator) > > > > > == Detailed Description == > > The Anaconda installer supports installations into a local image (via > the --image cmdline option) or a local directory (via the > --dirinstall cmdline option, the directory is usually a > mount point of a custom image). These types of installations are > supported by two user interfaces (text-based and GTK-based) in fully > interactive, partially interactive and non-interactive modes. We > believe that there is no strong reason for all these options, so we > would like to minimize the scope of this functionality and support > only the text-based non-interactive mode (specifically the > command-line mode). It means that Anaconda will require a fully > defined kickstart file and run only in the text-based user interface > (during dir and image installations). > > == Feedback == > > > == Benefit to Fedora == > > This is a preliminary step for an eventual deprecation and removal of > the Anaconda support for dir and image installations. This > functionality is being slowly taken over by [https://www.osbuild.org/ > Image Builder] that is explicitly designed for building images and > provides a much broader and better support for all kinds of images. > Limiting the scope of dir and image installations in Anaconda will > allow its developers to focus their resources on more prospective > areas. > > == Scope == > * Proposal owners: Will submit a pull request for > [https://anaconda-installer.readthedocs.io/en/latest/ > anaconda] to run dir and image installations only in the > non-interactive text mode and update > [https://weldr.io/lorax/livemedia-creator.html > livemedia-creator] to reflect these changes if necessary. > > * Other developers: No impact. > > * Release engineering: No impact. There should be zero impact on > building official Fedora images since these processes are fully > automated and use fully defined kickstart files. > [https://pagure.io/releng/issues #Releng issue number] > > * Policies and guidelines: N/A (not needed for this Change) > > * Trademark approval: N/A (not needed for this Change) > > * Alignment with Community Initiatives: > > > == Upgrade/compatibility impact == > > > > == How To Test == > > > == User Experience == > It will be still possible to use anaconda and > livemedia-creator for installations into a local image or > a directory with a fully defined kickstart file. Users can notice the > following changes: > > * If a user requests a dir or image installation, the installer runs > in the text mode. > * If the user doesn't specify a kickstart file, the installer will > report an error and abort. > * If the specified kickstart file is incomplete, the installer will > report an error and abort. > * All options for specifying the user interface will be ignored (for > example, --graphical) > > > == Dependencies == > > > == Contingency Plan == > > * Contingency mechanism: (What to do? Who will do it?) N/A (not a > System Wide Change) > > * Contingency deadline: N/A (not a System Wide Change) > * Blocks release? N/A (not a System Wide Change) > > == Documentation == > > N/A (not a System Wide Change) > > > == Release Notes == > Please do not drop this functionality. This is something I use for three purposes: * Interactive installations for debugging Anaconda weirdness * Anaconda development and testing * Interactive installations for custom multi-boot setups I know that it's not a very well-known feature, but I find it really handy and I would really rather not see it go away. -- 真実はいつも一つ！/ Always, there's only one truth! -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
F40 Change proposal: Bpfman as default eBPF manager (Self-Contained)
Wiki -> https://fedoraproject.org/wiki/Changes/DefaultBpfman This is a *proposed* Change for Fedora Linux. This document represents a proposed Change. As part of the [Changes process](https://docs.fedoraproject.org/en-US/program_management/changes_policy/), proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee. == Summary == bpfman: An eBPF Manager bpfman operates as an eBPF manager, focusing on simplifying the deployment and administration of eBPF programs. Its notable features encompass: * System Overview: Provides insights into how eBPF is utilized in your system. * eBPF Program Loader: Includes a built-in program loader that supports program cooperation for XDP and TC programs, as well as deployment of eBPF programs from OCI images. * eBPF Filesystem Management: Manages the eBPF filesystem, facilitating the deployment of eBPF applications without requiring additional privileges. We do aim to have this included in Fedora so it becomes the de-facto and easy way to load eBPF programs. == Owner == * Name: [[User:dmellado| Daniel Mellado]] * Email: dmell...@fedoraproject.org * Name: [[davetucker| Dave Tucker]] * Email: datuc...@redhat.com * Name: [[tohojo| Toke Høiland-Jørgensen]] * Email: thoil...@redhat.com == Detailed Description == bpfman operates as an eBPF manager, focusing on simplifying the deployment and administration of eBPF programs. bpfman is a software stack that aims to make it easy to load, unload, modify and monitor eBPF programs whether on a single host, or in a Kubernetes cluster. bpfman includes the following core components: * bpfman: A system daemon that supports loading, unloading, modifying and monitoring of eBPF programs exposed over a gRPC API. * eBPF CRDS: bpfman provides a set of CRDs (XdpProgram, TcProgram, etc.) that provide a way to express intent to load eBPF programs as well as a bpfman generated CRD (BpfProgram) used to represent the runtime state of loaded programs. * bpfman-agent: The agent runs in a container in the bpfman daemonset and ensures that the requested eBPF programs for a given node are in the desired state. * bpfman-operator: An operator, built using Operator SDK, that manages the installation and lifecycle of bpfman-agent and the CRDs in a Kubernetes cluster. bpfman is developed in Rust and built on top of Aya, a Rust eBPF library. == Feedback = N/A == Benefit to Fedora == bpfman is a software stack simplifying the management of eBPF programs in Kubernetes clusters or on individual hosts. It comprises a system daemon (bpfman), eBPF Custom Resource Definitions (CRDs), an agent (bpfman-agent), and an operator (bpfman-operator). Developed in Rust on the Aya library, bpfman offers improved security, visibility, multi-program support, and enhanced productivity for developers. For Fedora, integrating bpfman would streamline eBPF program loading. It enhances security by restricting privileges to the controlled bpfman daemon, simplifies deployment in Kubernetes clusters, and offers improved visibility into running eBPF programs. This integration aligns with Fedora's commitment to providing efficient and secure solutions, making it easier for users to leverage the benefits of eBPF in their systems. == Scope == * Proposal owners:Submit / review pull-requests and packages to Fedora * Other developers: https://copr.fedorainfracloud.org/coprs/g/ebpf-sig/bpfman-next/ migrate these packages from copr to Fedora alongside proposal owners * Policies and guidelines: N/A (not needed for this Change) * Trademark approval: N/A (not needed for this Change) * Alignment with Community Initiatives: N/A == Upgrade/compatibility impact == N/A == How To Test == N/A == User Experience == Users would be able to easily load eBPF programs within Fedora in a way more simpler way than currently using bpfman. == Dependencies == == Contingency Plan == * Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change) * Contingency deadline: N/A (not a System Wide Change) * Blocks release? N/A (not a System Wide Change), No == Documentation == * https://bpfman.io/main/ == Release Notes == -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney -- ___ 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 --
F40 Change proposal: Bpfman as default eBPF manager (Self-Contained)
Wiki -> https://fedoraproject.org/wiki/Changes/DefaultBpfman This is a *proposed* Change for Fedora Linux. This document represents a proposed Change. As part of the [Changes process](https://docs.fedoraproject.org/en-US/program_management/changes_policy/), proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee. == Summary == bpfman: An eBPF Manager bpfman operates as an eBPF manager, focusing on simplifying the deployment and administration of eBPF programs. Its notable features encompass: * System Overview: Provides insights into how eBPF is utilized in your system. * eBPF Program Loader: Includes a built-in program loader that supports program cooperation for XDP and TC programs, as well as deployment of eBPF programs from OCI images. * eBPF Filesystem Management: Manages the eBPF filesystem, facilitating the deployment of eBPF applications without requiring additional privileges. We do aim to have this included in Fedora so it becomes the de-facto and easy way to load eBPF programs. == Owner == * Name: [[User:dmellado| Daniel Mellado]] * Email: dmell...@fedoraproject.org * Name: [[davetucker| Dave Tucker]] * Email: datuc...@redhat.com * Name: [[tohojo| Toke Høiland-Jørgensen]] * Email: thoil...@redhat.com == Detailed Description == bpfman operates as an eBPF manager, focusing on simplifying the deployment and administration of eBPF programs. bpfman is a software stack that aims to make it easy to load, unload, modify and monitor eBPF programs whether on a single host, or in a Kubernetes cluster. bpfman includes the following core components: * bpfman: A system daemon that supports loading, unloading, modifying and monitoring of eBPF programs exposed over a gRPC API. * eBPF CRDS: bpfman provides a set of CRDs (XdpProgram, TcProgram, etc.) that provide a way to express intent to load eBPF programs as well as a bpfman generated CRD (BpfProgram) used to represent the runtime state of loaded programs. * bpfman-agent: The agent runs in a container in the bpfman daemonset and ensures that the requested eBPF programs for a given node are in the desired state. * bpfman-operator: An operator, built using Operator SDK, that manages the installation and lifecycle of bpfman-agent and the CRDs in a Kubernetes cluster. bpfman is developed in Rust and built on top of Aya, a Rust eBPF library. == Feedback = N/A == Benefit to Fedora == bpfman is a software stack simplifying the management of eBPF programs in Kubernetes clusters or on individual hosts. It comprises a system daemon (bpfman), eBPF Custom Resource Definitions (CRDs), an agent (bpfman-agent), and an operator (bpfman-operator). Developed in Rust on the Aya library, bpfman offers improved security, visibility, multi-program support, and enhanced productivity for developers. For Fedora, integrating bpfman would streamline eBPF program loading. It enhances security by restricting privileges to the controlled bpfman daemon, simplifies deployment in Kubernetes clusters, and offers improved visibility into running eBPF programs. This integration aligns with Fedora's commitment to providing efficient and secure solutions, making it easier for users to leverage the benefits of eBPF in their systems. == Scope == * Proposal owners:Submit / review pull-requests and packages to Fedora * Other developers: https://copr.fedorainfracloud.org/coprs/g/ebpf-sig/bpfman-next/ migrate these packages from copr to Fedora alongside proposal owners * Policies and guidelines: N/A (not needed for this Change) * Trademark approval: N/A (not needed for this Change) * Alignment with Community Initiatives: N/A == Upgrade/compatibility impact == N/A == How To Test == N/A == User Experience == Users would be able to easily load eBPF programs within Fedora in a way more simpler way than currently using bpfman. == Dependencies == == Contingency Plan == * Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change) * Contingency deadline: N/A (not a System Wide Change) * Blocks release? N/A (not a System Wide Change), No == Documentation == * https://bpfman.io/main/ == Release Notes == -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney -- ___ 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
[EPEL-devel] Re: Orphaning python-mistune on EPEL
On 10. 01. 24 22:16, Michel Lind wrote: Hi Miro, On Wed, Jan 10, 2024 at 02:51:33PM +0100, Miro Hrončok wrote: Hello, I recently took python-mistune in Fedora. I am not interested in maintaining it in EPEL. It is branched for epel7, epel8 and epel9. @epel-packagers-sig is a collaborator so I assume somebody built this in epel9 without taking responsibility. There is a low impact CVE: https://bugzilla.redhat.com/show_bug.cgi?id=2112231 If somebody want to maintain it, let me know and I'll make you the epel point of contact. Please mark me as the EPEL POC. Already marked Neil. Neil, let me know if I should change it. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok -- ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
F40 Change Proposal: Run Anaconda dir/image installations only in non-interactive text mode (Self-Contained
Wiki -> https://fedoraproject.org/wiki/Changes/Anaconda_dir_and_image_installations_in_automated_text_mode == Summary == Anaconda will require a fully defined kickstart file for installations into an image or a directory and these installations will run only in a non-interactive text-based user interface. == Owner == * Name: [[User:vponcova| Vendula Poncova]] * Email: * Package: anaconda * Name: [[User:bcl| Brian C. Lane]] * Email: * Package: lorax (livemedia-creator) == Detailed Description == The Anaconda installer supports installations into a local image (via the --image cmdline option) or a local directory (via the --dirinstall cmdline option, the directory is usually a mount point of a custom image). These types of installations are supported by two user interfaces (text-based and GTK-based) in fully interactive, partially interactive and non-interactive modes. We believe that there is no strong reason for all these options, so we would like to minimize the scope of this functionality and support only the text-based non-interactive mode (specifically the command-line mode). It means that Anaconda will require a fully defined kickstart file and run only in the text-based user interface (during dir and image installations). == Feedback == == Benefit to Fedora == This is a preliminary step for an eventual deprecation and removal of the Anaconda support for dir and image installations. This functionality is being slowly taken over by [https://www.osbuild.org/ Image Builder] that is explicitly designed for building images and provides a much broader and better support for all kinds of images. Limiting the scope of dir and image installations in Anaconda will allow its developers to focus their resources on more prospective areas. == Scope == * Proposal owners: Will submit a pull request for [https://anaconda-installer.readthedocs.io/en/latest/ anaconda] to run dir and image installations only in the non-interactive text mode and update [https://weldr.io/lorax/livemedia-creator.html livemedia-creator] to reflect these changes if necessary. * Other developers: No impact. * Release engineering: No impact. There should be zero impact on building official Fedora images since these processes are fully automated and use fully defined kickstart files. [https://pagure.io/releng/issues #Releng issue number] * Policies and guidelines: N/A (not needed for this Change) * Trademark approval: N/A (not needed for this Change) * Alignment with Community Initiatives: == Upgrade/compatibility impact == == How To Test == == User Experience == It will be still possible to use anaconda and livemedia-creator for installations into a local image or a directory with a fully defined kickstart file. Users can notice the following changes: * If a user requests a dir or image installation, the installer runs in the text mode. * If the user doesn't specify a kickstart file, the installer will report an error and abort. * If the specified kickstart file is incomplete, the installer will report an error and abort. * All options for specifying the user interface will be ignored (for example, --graphical) == Dependencies == == Contingency Plan == * Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change) * Contingency deadline: N/A (not a System Wide Change) * Blocks release? N/A (not a System Wide Change) == Documentation == N/A (not a System Wide Change) == Release Notes == -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney -- ___ 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
F40 Change Proposal: Run Anaconda dir/image installations only in non-interactive text mode (Self-Contained
Wiki -> https://fedoraproject.org/wiki/Changes/Anaconda_dir_and_image_installations_in_automated_text_mode == Summary == Anaconda will require a fully defined kickstart file for installations into an image or a directory and these installations will run only in a non-interactive text-based user interface. == Owner == * Name: [[User:vponcova| Vendula Poncova]] * Email: * Package: anaconda * Name: [[User:bcl| Brian C. Lane]] * Email: * Package: lorax (livemedia-creator) == Detailed Description == The Anaconda installer supports installations into a local image (via the --image cmdline option) or a local directory (via the --dirinstall cmdline option, the directory is usually a mount point of a custom image). These types of installations are supported by two user interfaces (text-based and GTK-based) in fully interactive, partially interactive and non-interactive modes. We believe that there is no strong reason for all these options, so we would like to minimize the scope of this functionality and support only the text-based non-interactive mode (specifically the command-line mode). It means that Anaconda will require a fully defined kickstart file and run only in the text-based user interface (during dir and image installations). == Feedback == == Benefit to Fedora == This is a preliminary step for an eventual deprecation and removal of the Anaconda support for dir and image installations. This functionality is being slowly taken over by [https://www.osbuild.org/ Image Builder] that is explicitly designed for building images and provides a much broader and better support for all kinds of images. Limiting the scope of dir and image installations in Anaconda will allow its developers to focus their resources on more prospective areas. == Scope == * Proposal owners: Will submit a pull request for [https://anaconda-installer.readthedocs.io/en/latest/ anaconda] to run dir and image installations only in the non-interactive text mode and update [https://weldr.io/lorax/livemedia-creator.html livemedia-creator] to reflect these changes if necessary. * Other developers: No impact. * Release engineering: No impact. There should be zero impact on building official Fedora images since these processes are fully automated and use fully defined kickstart files. [https://pagure.io/releng/issues #Releng issue number] * Policies and guidelines: N/A (not needed for this Change) * Trademark approval: N/A (not needed for this Change) * Alignment with Community Initiatives: == Upgrade/compatibility impact == == How To Test == == User Experience == It will be still possible to use anaconda and livemedia-creator for installations into a local image or a directory with a fully defined kickstart file. Users can notice the following changes: * If a user requests a dir or image installation, the installer runs in the text mode. * If the user doesn't specify a kickstart file, the installer will report an error and abort. * If the specified kickstart file is incomplete, the installer will report an error and abort. * All options for specifying the user interface will be ignored (for example, --graphical) == Dependencies == == Contingency Plan == * Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change) * Contingency deadline: N/A (not a System Wide Change) * Blocks release? N/A (not a System Wide Change) == Documentation == N/A (not a System Wide Change) == Release Notes == -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney -- ___ 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
[rpms/perl-NetAddr-IP] PR #3: Remove dependency to Socket6, which we are going to remove
jplesnik merged a pull-request against the project: `perl-NetAddr-IP` that you are following. Merged pull-request: `` Remove dependency to Socket6, which we are going to remove `` https://src.fedoraproject.org/rpms/perl-NetAddr-IP/pull-request/3 -- ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
