Re: Will noarch packages "inherit" ExcludeArch from another noarch package
On Tue, Sep 12, 2023 at 11:11 AM Lyes Saadi wrote: > Oh woops, answered to Jerry James privately instead to the whole devel > mailing list. It's indeed about blueprint-compiler. I looked at blueprint-compiler tonight, and found 2 bugs with the handling of bitfields. Sadly, fixing those still doesn't make the test suite pass, so there is at least one more bug lurking somewhere. Still, I think the package is probably fixable. If you can wait just a little longer, I will try to find the next bug tomorrow. -- 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
[Test-Announce] Fedora 39 Candidate Beta-1.1 Available Now!
According to the schedule [1], Fedora 39 Candidate Beta-1.1 is now available for testing. Please help us complete all the validation testing! For more information on release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan Test coverage information for the current release can be seen at: https://openqa.fedoraproject.org/testcase_stats/39 You can see all results, find testing instructions and image download locations, and enter results on the Summary page: https://fedoraproject.org/wiki/Test_Results:Fedora_39_Beta_1.1_Summary The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_39_Beta_1.1_Installation https://fedoraproject.org/wiki/Test_Results:Fedora_39_Beta_1.1_Base https://fedoraproject.org/wiki/Test_Results:Fedora_39_Beta_1.1_Server https://fedoraproject.org/wiki/Test_Results:Fedora_39_Beta_1.1_Cloud https://fedoraproject.org/wiki/Test_Results:Fedora_39_Beta_1.1_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_39_Beta_1.1_Security_Lab All Beta priority test cases for each of these test pages [2] must pass in order to meet the Beta Release Criteria [3]. Help is available on #fedora-qa on libera.chat [4], or on the test list [5]. Current Blocker and Freeze Exception bugs: http://qa.fedoraproject.org/blockerbugs/current [1] http://fedorapeople.org/groups/schedule/f-39/f-39-quality-tasks.html [2] https://fedoraproject.org/wiki/QA:Release_validation_test_plan [3] https://fedoraproject.org/wiki/Fedora_39_Beta_Release_Criteria [4] https://web.libera.chat/?channels=#fedora-qa [5] https://lists.fedoraproject.org/archives/list/t...@lists.fedoraproject.org/ ___ 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
The new Change discussion process is painful
Hi, it is really a pain that the Change discussion is now hidden in a web forum behind a web link, instead of happening right here in this mailing list. It was promised that Discourse would NOT replace the mailing lists, but that is effectively no longer the case. Can this "Discourse for Change discussion" experiment please be stopped? It has no advantages and only adds a useless layer of indirection. Kevin Kofler ___ 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: An update on RHEL moving to issues.redhat.com
On Wed, Sep 13, 2023 at 3:27 AM Kevin Kofler via devel wrote: > > Adam Williamson wrote: > > IIRC it was a condition of that proposal that we wind up on a hosted > > version of the *open source* release of gitlab > > "hosted version" and "open source" is already a contradiction by itself. > https://www.gnu.org/philosophy/network-services-arent-free-or-nonfree.html > > The Fedora Project's increasing reliance on third-party SaaS is a problem, > not a solution. Even if the server software happens to be FOSS, that is of > no help if you do not control the server and hence cannot control what > version is deployed. As (I think it was Ben who reminded us), the Fedora Council adopted (in 2018) the following statement: "The Fedora Project wants to advance free and open source software and as a pragmatic matter we recognize that some infrastructure needs may be best served by using closed source or non-free tools today. Therefore the Council is willing to accept closed source or non-free tools in Fedora’s infrastructure where free and open source tools are not viable or not available." If you don't agree with that decision, run for the council, or vote for representatives on the council who agree with your point of view and will work to rescind that statement. Until that happens, the statement stands as adopted. ___ 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: An update on RHEL moving to issues.redhat.com
Adam Williamson wrote: > IIRC it was a condition of that proposal that we wind up on a hosted > version of the *open source* release of gitlab "hosted version" and "open source" is already a contradiction by itself. https://www.gnu.org/philosophy/network-services-arent-free-or-nonfree.html The Fedora Project's increasing reliance on third-party SaaS is a problem, not a solution. Even if the server software happens to be FOSS, that is of no help if you do not control the server and hence cannot control what version is deployed. Kevin Kofler ___ 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
Questions about %pyproject_buildrequires
Hi all, First, is it possible to use this macro if the pyproject.toml isn't in the root directory of the package? There doesn't seem to be an option to specify a path, so I tried cd'ing into a path and running it, but it seemed to run into an odd error like it was trying to include my directory as a package. Second, can %pyproject_buildrequires (and the other %pyproject_ macros) be used multiple times in a package? I have a package that has multiple pyproject.toml files in it (but that's mostly a legacy thing, so I could probably separate them into multiple RPMs). Thanks, Scott ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-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/python-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 3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-4cc86adbd2 chromium-116.0.5845.179-1.el8 3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-9c17eb827f borgbackup-1.1.18-2.el8 The following builds have been pushed to Fedora EPEL 8 updates-testing mlpack-4.2.1-1.el8 netatalk-3.1.16-1.el8 rubygem-aruba-0.14.14-1.el8.2 Details about builds: mlpack-4.2.1-1.el8 (FEDORA-EPEL-2023-98a45d204b) Fast, header-only C++ machine learning library Update Information: Update to latest stable version. ChangeLog: * Mon Sep 11 2023 Ryan Curtin - 4.2.1-1 - Update to latest stable version. * Thu Jul 27 2023 Ryan Curtin - 4.2.0-4 - Bugfix: ensure Cython finds pxds for a successful build. * Thu Jul 20 2023 Fedora Release Engineering - 4.2.0-3 - Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild * Wed Jun 28 2023 Python Maint - 4.2.0-2 - Rebuilt for Python 3.12 * Thu Jun 22 2023 Ryan Curtin - 4.2.0-1 - Update to latest stable version. * Thu Apr 27 2023 Benson Muite - 4.1.0-1 - Update to new version * Sat Feb 25 2023 Benjamin A. Beasley - 4.0.1-4 - Update min. stb_image versions for nullptr deref. bug - Add stb license to the License field * Mon Feb 13 2023 Benson Muite - 4.0.1-3 - Use SPDX identifiers - Update license information to include Apache-2.0 * Thu Jan 19 2023 Fedora Release Engineering - 4.0.1-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild netatalk-3.1.16-1.el8 (FEDORA-EPEL-2023-4968c07262) Open Source Apple Filing Protocol(AFP) File Server Update Information: autoconf, automake, and libtool are no longer required ChangeLog: * Tue Sep 12 2023 Andrew Bauer - 5:3.1.16-1 - autoconf, automake, and libtool are no longer required - force gnu99 cflag on el7 builds - 3.1.16 release * Thu Jul 20 2023 Fedora Release Engineering - 5:3.1.15-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild References: [ 1 ] Bug #2238477 - netatalk-3.1.16 is available https://bugzilla.redhat.com/show_bug.cgi?id=2238477 rubygem-aruba-0.14.14-1.el8.2 (FEDORA-EPEL-2023-06046a646d) CLI Steps for Cucumber, hand-crafted for you in Aruba Update Information: Kill python test entirely to redure BR, it is not important (#2237692) ChangeLog: * Tue Sep 12 2023 Troy Dawson - 0.14.14-1.2 - Kill python test entirely to redure BR, it is not important (#2237692) References: [ 1 ] Bug #2237692 - rubygem-aruba should not BuildRequire /usr/bin/python3 https://bugzilla.redhat.com/show_bug.cgi?id=2237692 ___ 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
[Bug 1860590] perl-IPC-Signal missing in EPEL 8
https://bugzilla.redhat.com/show_bug.cgi?id=1860590 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-IPC-Signal-1.00-39.el8 |perl-IPC-Signal-1.00-39.el8 ||perl-IPC-Signal-1.00-39.el9 --- Comment #8 from Fedora Update System --- FEDORA-EPEL-2023-ac6879063b has been pushed to the Fedora EPEL 9 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=1860590 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%201860590%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 1860592] perl-Proc-WaitStat missing in EPEL 8
https://bugzilla.redhat.com/show_bug.cgi?id=1860592 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-Proc-WaitStat-1.00-39. |perl-Proc-WaitStat-1.00-39. |el8 |el8 ||perl-Proc-WaitStat-1.00-39. ||el9 --- Comment #7 from Fedora Update System --- FEDORA-EPEL-2023-ac6879063b has been pushed to the Fedora EPEL 9 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=1860592 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%201860592%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 1860592] perl-Proc-WaitStat missing in EPEL 8
https://bugzilla.redhat.com/show_bug.cgi?id=1860592 Fedora Update System changed: What|Removed |Added Resolution|--- |ERRATA Status|ON_QA |CLOSED Fixed In Version||perl-Proc-WaitStat-1.00-39. ||el8 Last Closed|2021-02-01 08:52:21 |2023-09-13 00:30:09 --- Comment #6 from Fedora Update System --- FEDORA-EPEL-2023-59f25ec4ef has been pushed to the Fedora EPEL 8 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=1860592 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%201860592%23c6 ___ 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 1860590] perl-IPC-Signal missing in EPEL 8
https://bugzilla.redhat.com/show_bug.cgi?id=1860590 Fedora Update System changed: What|Removed |Added Fixed In Version||perl-IPC-Signal-1.00-39.el8 Status|ON_QA |CLOSED Resolution|--- |ERRATA Last Closed|2021-02-01 08:51:09 |2023-09-13 00:30:07 --- Comment #7 from Fedora Update System --- FEDORA-EPEL-2023-59f25ec4ef has been pushed to the Fedora EPEL 8 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=1860590 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%201860590%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 1860592] perl-Proc-WaitStat missing in EPEL 8
https://bugzilla.redhat.com/show_bug.cgi?id=1860592 Bug 1860592 depends on bug 1860590, which changed state. Bug 1860590 Summary: perl-IPC-Signal missing in EPEL 8 https://bugzilla.redhat.com/show_bug.cgi?id=1860590 What|Removed |Added Status|ON_QA |CLOSED Resolution|--- |ERRATA -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=1860592 ___ 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 2238633] perltidy-20230912 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2238633 --- Comment #2 from Upstream Release Monitoring --- the-new-hotness/release-monitoring.org's scratch build of perltidy-20230912-1.fc38.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=106104775 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2238633 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202238633%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
[Bug 2238633] perltidy-20230912 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2238633 --- Comment #1 from Upstream Release Monitoring --- Created attachment 1988539 --> https://bugzilla.redhat.com/attachment.cgi?id=1988539=edit Update to 20230912 (#2238633) -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2238633 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202238633%23c1 ___ 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 2238633] New: perltidy-20230912 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2238633 Bug ID: 2238633 Summary: perltidy-20230912 is available Product: Fedora Version: rawhide Status: NEW Component: perltidy Keywords: FutureFeature, Triaged Assignee: p...@city-fan.org Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: lxt...@gmail.com, p...@city-fan.org, perl-devel@lists.fedoraproject.org Target Milestone: --- Classification: Fedora Releases retrieved: 20230912 Upstream release that is considered latest: 20230912 Current version/release in rawhide: 20230909-1.fc40 URL: http://search.cpan.org/dist/Perl-Tidy/ 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/3553/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/perltidy -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2238633 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202238633%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
[Bug 2238421] perl-version-0.9930 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2238421 --- Comment #4 from Fedora Update System --- FEDORA-2023-4d3ae46504 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-4d3ae46504` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-4d3ae46504 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2238421 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202238421%23c4 ___ 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
Re: Anyone interested in packaging + maintaining the nimble language?
On Tue Sep 12, 2023 at 09:21 +0200, Sandro wrote: > On 12-09-2023 03:36, Maxwell G wrote: > >> It isn't packaged for Fedora yet, though. Is anyone using it, and would > >> like to package + maintain it for Fedora? > > IIRC, we used to have nim in Fedora and then it was retired. > > Indeed. That may be a good starting point. > > There's also nim-srpm-macros [1], which has a bit of a misleading name. > It's for converting nimble packages to RPM. > > [1] https://src.fedoraproject.org/rpms/nim-srpm-macros > That's actually named according to convention. It only contains a `%nim_arches` definition which is needed during the SRPM build stage and used to be Required by redhat-rpm-config and part of the default buildroot. -- Best, Maxwell G (@gotmax23) Pronouns: He/They ___ 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: Will noarch packages "inherit" ExcludeArch from another noarch package
On Tue, Sep 12, 2023 at 1:11 PM Lyes Saadi wrote:
>
> Oh woops, answered to Jerry James privately instead to the whole devel
> mailing list. It's indeed about blueprint-compiler.
>
> Le 12/09/2023 à 19:03, Dan Horák a écrit :
> > On Tue, 12 Sep 2023 10:08:57 -0600
> > Jerry James wrote:
> >
> >> On Tue, Sep 12, 2023 at 10:03 AM Lyes Saadi
> >> wrote:
> >>> I have a noarch package which faces an issue with one of its arches
> >>> (s390x), and which happens to have multiple noarch packages depending on
> >>> it, and they won't build either if they were built on that same arch
> >>> (but, they will still work normally when installed on that arch). And
> >>> so, I plan on adding an ExcludeArch, as per
> >>> https://docs.fedoraproject.org/en-US/packaging-guidelines/#_arch_specific_runtime_and_build_time_dependencies.
> >>>
> >>> But, I don't know if I need to also ask maintainers of every dependency
> >>> to add ExcludeArch themselves. Indeed, the guideline says :
> >>> > You can limit both the architectures used to build a noarch package,
> >>> *and the repositories to which the built noarch package will be added*
> >>>
> >>> So, am I correct in assuming that if my noarch package uses ExcludeArch,
> >>> every other dependent package, when building, will not build on that
> >>> Arch as well ?
> >> You will indeed have to ask the maintainers of consuming packages to
> >> add that ExcludeArch too. What package is it and what is the nature
> >> of the problem on s390x? Maybe it can be fixed.
> > I believe it's about blueprint-compiler, which has some big endian
> > issues, please see https://bugzilla.redhat.com/show_bug.cgi?id=2169892
The classic way to do this is to request a macro like
`%{blueprint_arches}` which can be passed to any package requiring the
blueprint compiler. We have several interpreted languages that do
this, if the interpreter isn't available on all arches.
```
$ rpm --showrc|grep _arches
-13: GNAT_arches %{GPRbuild_arches} ia64 ppc alpha %{arm} riscv64
-13: GPRbuild_arches %{ix86} x86_64 %{power64} s390x aarch64
-13: fpc_arches %{ix86} %{arm} x86_64 ppc64le aarch64
-13: gap_arches aarch64 ppc64le s390x x86_64
-13: gccgo_arches mips mipsel mipsr6 mipsr6el mips64 mips64el mips64r6
mips64r6el
-13: ghc_arches %{ix86} x86_64 armv7hl ppc64le aarch64 s390x
-13: go_arches %{golang_arches} %{gccgo_arches}
-13: golang_arches i386 i486 i586 i686 pentium3 pentium4 athlon geode
x86_64 armv3l armv4b armv4l armv4tl armv5tl armv5tel armv5tejl armv6l
armv6hl armv7l armv7hl armv7hnl armv8l armv8hl armv8hnl armv8hcnl
aarch64 ppc64le s390x
-13: golang_arches_future x86_64 armv3l armv4b armv4l armv4tl armv5tl
armv5tel armv5tejl armv6l armv6hl armv7l armv7hl armv7hnl armv8l
armv8hl armv8hnl armv8hcnl aarch64 ppc64le s390x
exclusive_arches = "%{golang_arches}"
exclusive_arches = "%{golang_arches_future}"
print(rpm.expand("ExclusiveArch: " .. exclusive_arches .. "\n"))
-13: java_arches aarch64 ppc64le s390x x86_64
-13: kernel_arches x86_64 s390x ppc64le aarch64 %{arm}
-13: ldc_arches %{ix86} x86_64 %{arm} aarch64
-13: mono_arches %{ix86} x86_64 sparc sparcv9 ia64 %{arm} aarch64
alpha s390x ppc ppc64 ppc64le
-13: nodejs_arches %{ix86} x86_64 %{arm} aarch64 %{power64} s390x
-13: openblas_arches x86_64 %{ix86} armv7hl %{power64} aarch64 s390x
-13: qt5_qtwebengine_arches %{ix86} x86_64 %{arm} aarch64 mips mipsel mips64el
-13: rust_arches x86_64 %{ix86} armv7hl aarch64 ppc64 ppc64le riscv64 s390x
-13: valgrind_arches %{ix86} x86_64 ppc ppc64 ppc64le s390x armv7hl aarch64
```
When relying on e.g. Node.js, one is expected to do:
ExclusiveArch: %{nodejs_arches}
___
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: Is this number ok?
Am Di., 12. Sept. 2023 um 20:28 Uhr schrieb Adam Williamson : > > On Tue, 2023-09-12 at 17:20 +, Alessio wrote: > > I know about this accepted change: > > https://fedoraproject.org/wiki/Changes/Color_Bash_Prompt > > > > But what is this number that appears time to time in the prompt? > > > > user@host:~$ ^C > > user@host:~130$ ^C > > > > user@host:~$ foo > > bash: foo: command not found > > user@host:~127$ > > > > An exit code I suppose? > > yeah, it seems to be the exit code of the last command if it's not 0. > > It does seem that this change is beyond the scope disclosed in the > Change, so that could possibly be brought up for discussion. Pulling in > devel@ and the Change owner for comment. Jens, why was this feature not > disclosed in the Change scope? It was disclosed in the "Detailed Description" (screenshots) and "How To test" (source git repo), but not in the scope. Somewhat borderline. Michael ___ 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: Is this number ok?
On Tue, 2023-09-12 at 17:20 +, Alessio wrote: > I know about this accepted change: > https://fedoraproject.org/wiki/Changes/Color_Bash_Prompt > > But what is this number that appears time to time in the prompt? > > user@host:~$ ^C > user@host:~130$ ^C > > user@host:~$ foo > bash: foo: command not found > user@host:~127$ > > An exit code I suppose? yeah, it seems to be the exit code of the last command if it's not 0. It does seem that this change is beyond the scope disclosed in the Change, so that could possibly be brought up for discussion. Pulling in devel@ and the Change owner for comment. Jens, why was this feature not disclosed in the Change scope? -- 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
Re: FAS 2FA recovery keys?
On Tue, Sep 12, 2023 at 10:58:24AM +0100, Barry Scott wrote: > > > > On 12 Sep 2023, at 10:32, Michael J Gruber wrote: > > > > Am Di., 12. Sept. 2023 um 11:22 Uhr schrieb Barry Scott > > : > >> > >> I have been updating my FAS account security. > >> When I setup 2FA I was not offer any recovery keys. > > > > You can register multiple OTP tokens: > > https://docs.fedoraproject.org/en-US/infra/sysadmin_guide/2-factor/ > > I did notice I could setup more then one and have used pass-otp for my 2nd > 2FA method. > > > > >> In the event that I lose FreeOTP on my phone how do I recover? > > > > If you lost all of your tokens you can request a reset: > > https://fedoraproject.org/wiki/Infrastructure_Two_Factor_Auth#What_happens_if_I_lost_my_token_or_got_a_new_device? > > Good to know. > > > > > That being said, I'm in the same boat: Getting recovery keys *at the > > same time* as activating 2fa has something soothing to it ... > > Yep, and its what I have seen for every over service I setup 2FA for. If you like you could file a RFE on noggin: https://github.com/fedora-infra/noggin This may be difficult to implement though, due to the way things fit together. noggin is a application that provides the 'self service' part of things on top of IPA. IPA doesn't (I don't think) have any way to do 'recovery codes' because it's designed that admins manage the users (as in companies), so it would all need to be implemented in noggin. Anyhow, I agree it would be a nice feature to have. kevin signature.asc Description: PGP signature ___ 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: Will noarch packages "inherit" ExcludeArch from another noarch package
Oh woops, answered to Jerry James privately instead to the whole devel mailing list. It's indeed about blueprint-compiler. Le 12/09/2023 à 19:03, Dan Horák a écrit : On Tue, 12 Sep 2023 10:08:57 -0600 Jerry James wrote: On Tue, Sep 12, 2023 at 10:03 AM Lyes Saadi wrote: I have a noarch package which faces an issue with one of its arches (s390x), and which happens to have multiple noarch packages depending on it, and they won't build either if they were built on that same arch (but, they will still work normally when installed on that arch). And so, I plan on adding an ExcludeArch, as per https://docs.fedoraproject.org/en-US/packaging-guidelines/#_arch_specific_runtime_and_build_time_dependencies. But, I don't know if I need to also ask maintainers of every dependency to add ExcludeArch themselves. Indeed, the guideline says : > You can limit both the architectures used to build a noarch package, *and the repositories to which the built noarch package will be added* So, am I correct in assuming that if my noarch package uses ExcludeArch, every other dependent package, when building, will not build on that Arch as well ? You will indeed have to ask the maintainers of consuming packages to add that ExcludeArch too. What package is it and what is the nature of the problem on s390x? Maybe it can be fixed. I believe it's about blueprint-compiler, which has some big endian issues, please see https://bugzilla.redhat.com/show_bug.cgi?id=2169892 Dan ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, 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: Will noarch packages "inherit" ExcludeArch from another noarch package
On Tue, 12 Sep 2023 10:08:57 -0600 Jerry James wrote: > On Tue, Sep 12, 2023 at 10:03 AM Lyes Saadi > wrote: > > I have a noarch package which faces an issue with one of its arches > > (s390x), and which happens to have multiple noarch packages depending on > > it, and they won't build either if they were built on that same arch > > (but, they will still work normally when installed on that arch). And > > so, I plan on adding an ExcludeArch, as per > > https://docs.fedoraproject.org/en-US/packaging-guidelines/#_arch_specific_runtime_and_build_time_dependencies. > > > > But, I don't know if I need to also ask maintainers of every dependency > > to add ExcludeArch themselves. Indeed, the guideline says : > > > You can limit both the architectures used to build a noarch package, > > *and the repositories to which the built noarch package will be added* > > > > So, am I correct in assuming that if my noarch package uses ExcludeArch, > > every other dependent package, when building, will not build on that > > Arch as well ? > > You will indeed have to ask the maintainers of consuming packages to > add that ExcludeArch too. What package is it and what is the nature > of the problem on s390x? Maybe it can be fixed. I believe it's about blueprint-compiler, which has some big endian issues, please see https://bugzilla.redhat.com/show_bug.cgi?id=2169892 Dan ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Will noarch packages "inherit" ExcludeArch from another noarch package
On Tue, Sep 12, 2023 at 10:03 AM Lyes Saadi wrote: > I have a noarch package which faces an issue with one of its arches > (s390x), and which happens to have multiple noarch packages depending on > it, and they won't build either if they were built on that same arch > (but, they will still work normally when installed on that arch). And > so, I plan on adding an ExcludeArch, as per > https://docs.fedoraproject.org/en-US/packaging-guidelines/#_arch_specific_runtime_and_build_time_dependencies. > > But, I don't know if I need to also ask maintainers of every dependency > to add ExcludeArch themselves. Indeed, the guideline says : > > You can limit both the architectures used to build a noarch package, > *and the repositories to which the built noarch package will be added* > > So, am I correct in assuming that if my noarch package uses ExcludeArch, > every other dependent package, when building, will not build on that > Arch as well ? You will indeed have to ask the maintainers of consuming packages to add that ExcludeArch too. What package is it and what is the nature of the problem on s390x? Maybe it can be fixed. -- 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
Re: Potential changes to systemd RPM macros
On Mon, Sep 11, 2023 at 11:01:17AM +, Zbigniew Jędrzejewski-Szmek wrote: > On Wed, Aug 09, 2023 at 08:34:59AM +, Zbigniew Jędrzejewski-Szmek wrote: > > This is now merged. The new macros are: > > %systemd_postun_with_reload, %systemd_user_postun_with_reload, > > %systemd_user_daemon_reexec. That last one is now used in > > the systemd.spec file in rawhide to properly reexec user@.service > > instances after package upgrade. > > > > Somebody needs to file an FPC pull request now ;) > > https://pagure.io/packaging-committee/pull-request/1301 > > Reviews welcome ;) FWIW, changes look reasonable to me. I still intend to extract the libvirt macros, make them more generic, polish them and submit the result to systemd upstream. I just haven't been able to carve time to do that yet, but it's reasonably high on my TODO list :) -- Andrea Bolognani / Red Hat / Virtualization ___ 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
Will noarch packages "inherit" ExcludeArch from another noarch package
Hello ! I have a noarch package which faces an issue with one of its arches (s390x), and which happens to have multiple noarch packages depending on it, and they won't build either if they were built on that same arch (but, they will still work normally when installed on that arch). And so, I plan on adding an ExcludeArch, as per https://docs.fedoraproject.org/en-US/packaging-guidelines/#_arch_specific_runtime_and_build_time_dependencies. But, I don't know if I need to also ask maintainers of every dependency to add ExcludeArch themselves. Indeed, the guideline says : > You can limit both the architectures used to build a noarch package, *and the repositories to which the built noarch package will be added* So, am I correct in assuming that if my noarch package uses ExcludeArch, every other dependent package, when building, will not build on that Arch as well ? Greetings, Lyes Saadi ___ 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] [Fedocal] Reminder meeting : EPEL Steering Committee
Dear all, You are kindly invited to the meeting: EPEL Steering Committee on 2023-09-13 from 16:00:00 to 17:00:00 US/Eastern At fedora-meet...@irc.libera.chat The meeting will be about: This is the weekly EPEL Steering Committee Meeting. A general agenda is the following: #topic aloha #topic EPEL Issues https://pagure.io/epel/issues * https://pagure.io/epel/issues?tags=meeting=Open #topic Old Business (if needed) #topic General Issues / Open Floor Source: https://calendar.fedoraproject.org//meeting/9854/ ___ 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
Review-swap: trivial golang package to update nats stack
I'd like to offer to swap reviews to get golang-github-nats-io-jwt-2 https://bugzilla.redhat.com/show_bug.cgi?id=2237326 into Rawhide We already have v1 and attempting to update that package in order to upgrade the nats stack led to some breakage and headaches a few months ago Thanks all, fuller ___ 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
[rpms/perl-Class-XSAccessor] PR #1: Package tests; Modernize spec
jplesnik merged a pull-request against the project: `perl-Class-XSAccessor` that you are following. Merged pull-request: `` Package tests; Modernize spec `` https://src.fedoraproject.org/rpms/perl-Class-XSAccessor/pull-request/1 ___ 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
[rpms/perl-Class-XSAccessor] PR #1: Package tests; Modernize spec
jplesnik opened a new pull-request against the project: `perl-Class-XSAccessor` that you are following: `` Package tests; Modernize spec `` To reply, visit the link below https://src.fedoraproject.org/rpms/perl-Class-XSAccessor/pull-request/1 ___ 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
Re: An update on RHEL moving to issues.redhat.com
On Mon, Sep 11, 2023 at 09:26:44AM -0700, Kevin Fenzi wrote: > I think we need to figure out the way forward, but... I don't think we > should do it here and now. Please go test f39. ;) While I'm personally glad that the forced-onto-proprietary-gitlab migration has effectively stalled indefinitely, the fact remains is said migration is still the plan of record. So, if it's effectively dead, let's make it official? - Solomon -- Solomon Peachypizza at shaftnet dot org (email) @pizza:shaftnet dot org (matrix) Dowling Park, FL speachy (libera.chat) signature.asc Description: PGP signature ___ 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 1347333] Are there plans for a RHEL7 package?
https://bugzilla.redhat.com/show_bug.cgi?id=1347333 Tom "spot" Callaway changed: What|Removed |Added Status|NEW |CLOSED Resolution|--- |NOTABUG Last Closed||2023-09-12 13:43:18 --- Comment #2 from Tom "spot" Callaway --- Not by me, but if you want to pick it up (and probably chase other missing perl dependencies), you can become the EPEL7 maintainer. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=1347333 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%201347333%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
Fedora 39 compose report: 20230912.n.0 changes
OLD: Fedora-39-20230910.n.0 NEW: Fedora-39-20230912.n.0 = SUMMARY = Added images:3 Dropped images: 1 Added packages: 0 Dropped packages:1 Upgraded packages: 4 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:68.10 KiB Size of upgraded packages: 950.61 MiB Size of downgraded packages: 0 B Size change of upgraded packages: 1.40 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = Image: Kinoite dvd-ostree ppc64le Path: Kinoite/ppc64le/iso/Fedora-Kinoite-ostree-ppc64le-39-20230912.n.0.iso Image: LXQt live aarch64 Path: Spins/aarch64/iso/Fedora-LXQt-Live-aarch64-39-20230912.n.0.iso Image: Container_Base docker s390x Path: Container/s390x/images/Fedora-Container-Base-39-20230912.n.0.s390x.tar.xz = DROPPED IMAGES = Image: KDE live aarch64 Path: Spins/aarch64/iso/Fedora-KDE-Live-aarch64-39-20230910.n.0.iso = ADDED PACKAGES = = DROPPED PACKAGES = Package: python-async-generator-1.10-16.fc38 Summary: Async generators and context managers RPMs:python3-async-generator Size:68.10 KiB = UPGRADED PACKAGES = Package: budgie-desktop-defaults-0.5.1-1.fc39 Old package: budgie-desktop-defaults-0.4-2.fc39 Summary: Budgie Desktop Defaults for Fedora RPMs: budgie-desktop-defaults Size: 14.80 KiB Size change: -156 B Changelog: * Wed Sep 06 2023 Joshua Strobl - 0.5.1-1 - Update to 0.5.1 for schema rename and background removal Package: desktop-backgrounds-39.0.0-3.fc39 Old package: desktop-backgrounds-39.0.0-1.fc39 Summary: Desktop backgrounds RPMs: desktop-backgrounds-basic desktop-backgrounds-budgie desktop-backgrounds-compat desktop-backgrounds-gnome desktop-backgrounds-waves Added RPMs: desktop-backgrounds-budgie Size: 13.40 MiB Size change: 10.88 KiB Changelog: * Wed Sep 06 2023 Joshua Strobl - 39.0.0-2 - Implement a budgie backgrounds sub-package and start symlinking dark variant * Fri Sep 08 2023 Neal Gompa - 39.0.0-3 - No-change rebuild for merging Bodhi updates for Budgie backgrounds Package: fedora-repos-39-0.6 Old package: fedora-repos-39-0.5 Summary: Fedora package repositories RPMs: fedora-gpg-keys fedora-repos fedora-repos-archive fedora-repos-eln fedora-repos-ostree fedora-repos-rawhide Size: 172.17 KiB Size change: -505 B Changelog: * Wed Sep 06 2023 Tomas Hrcka - 39-0.6 - added Fedora 41 keys - enabled updates_testing repository Package: kernel-6.5.2-300.fc39 Old package: kernel-6.5.0-0.rc7.20230821gitf7757129e3de.50.fc39 Summary: The Linux kernel RPMs: kernel kernel-core kernel-debug kernel-debug-core kernel-debug-devel kernel-debug-devel-matched kernel-debug-modules kernel-debug-modules-core kernel-debug-modules-extra kernel-debug-modules-internal kernel-debug-uki-virt kernel-devel kernel-devel-matched kernel-doc kernel-modules kernel-modules-core kernel-modules-extra kernel-modules-internal kernel-uki-virt Size: 937.03 MiB Size change: 1.39 MiB Changelog: * Tue Aug 22 2023 Fedora Kernel Team [6.5.0-0.rc7.f7757129e3de.51.eln130] - redhat/configs: Enable CONFIG_DEVICE_PRIVATE on aarch64 (David Hildenbrand) [2231407] - redhat/configs: disable CONFIG_ROCKCHIP_ERRATUM_3588001 for RHEL (Mark Salter) - redhat: shellcheck fixes (Prarit Bhargava) * Wed Aug 23 2023 Fedora Kernel Team [6.5.0-0.rc7.89bf6209cad6.52.eln130] - redhat/self-test: Remove rpmlint test (Prarit Bhargava) - Remove the armv7 config directory from Fedora again (Justin M. Forbes) - Enable CONFIG_EXPERT for both RHEL and Fedora (Justin M. Forbes) - Linux v6.5.0-0.rc7.89bf6209cad6 * Thu Aug 24 2023 Fedora Kernel Team [6.5.0-0.rc7.93f5de5f648d.53.eln130] - Consolidate configs to common for 6.5 (Justin M. Forbes) - Remove unused config entry for Fedora (Justin M. Forbes) - Linux v6.5.0-0.rc7.93f5de5f648d * Fri Aug 25 2023 Fedora Kernel Team [6.5.0-0.rc7.4f9e7fabf864.54.eln130] - Linux v6.5.0-0.rc7.4f9e7fabf864 * Sat Aug 26 2023 Fedora Kernel Team [6.5.0-0.rc7.7d2f353b2682.55.eln130] - redhat/kernel.spec.template: update compression variables to support zstd (Brian Masney) - Linux v6.5.0-0.rc7.7d2f353b2682 * Sun Aug 27 2023 Fedora Kernel Team [6.5.0-0.rc7.28f20a19294d.56.eln130] - Linux v6.5.0-0.rc7.28f20a19294d * Mon Aug 28 2023 Fedora Kernel Team [6.5.0-57.eln130] - Linux v6.5.0 * Mon Aug 28 2023 Fedora Kernel Team [6.5.0-58.eln130] - redhat: Fix UKI install with systemd >= 254 (Vitaly Kuznetsov) - redhat: Use named parameters for kernel_variant_posttrans()/kernel_variant_preun() (Vitaly Kuznetsov) * Sat Sep 02 2023 Justin M. Forbes [6.5.1-0] - erofs: ensure that the post-EOF tails are all zeroed (Gao Xiang) - Add bug to BugsFixed (Justin M. Forbes) - Turn off CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE for Fedora s390x (Justin M. Forbes) - drm/msm/a690: Switch to a660_gmu.bin (
Re: Orphaned packages looking for new maintainers
On Mon, Sep 04, 2023 at 05:10:55PM +0200, Miro Hrončok wrote: > The following packages are orphaned and will be retired when they > are orphaned for six weeks, unless someone adopts them. If you know for sure > that the package should be retired, please do so now with a proper reason: > https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life > > Full report available at: > https://churchyard.fedorapeople.org/orphans-2023-08-21.txt > > Package (co)maintainers Status > Change > > maven-clean-pluginmizdebsk, mkulik, orphan 4 weeks ago Hi all, I took maven-clean-plugin as some of my packages depend on it. I accidently tried to post this on devel-announce, sorry about that. Best wishes, Markku ___ 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 2236235] perl-Net-DNS-1.40 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2236235 Fedora Update System changed: What|Removed |Added Fixed In Version||perl-Net-DNS-1.40-1.fc40 Status|MODIFIED|CLOSED Resolution|--- |ERRATA Last Closed||2023-09-12 11:10:35 --- Comment #4 from Fedora Update System --- FEDORA-2023-4f048595b7 has been pushed to the Fedora 40 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=2236235 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202236235%23c4 ___ 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 2236235] perl-Net-DNS-1.40 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2236235 Fedora Update System changed: What|Removed |Added Status|NEW |MODIFIED --- Comment #3 from Fedora Update System --- FEDORA-2023-4f048595b7 has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2023-4f048595b7 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2236235 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202236235%23c3 ___ 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
Re: Orphaned packages looking for new maintainers
Hi, I want to let you know that all packages depending on maven-clean-plugin can most probably just use: %prep ... %pom_remove_plugin :maven-clean-plugin and live happily after. I am not aware of any purpose of maven-clean-plugin for Fedora package builds. On 12. 9. 2023 12:54, Markku Korkeala wrote: On Mon, Sep 04, 2023 at 05:10:55PM +0200, Miro Hrončok wrote: The following packages are orphaned and will be retired when they are orphaned for six weeks, unless someone adopts them. If you know for sure that the package should be retired, please do so now with a proper reason: https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life Request package ownership via the *Take* button in he left column on https://src.fedoraproject.org/rpms/ Full report available at: https://churchyard.fedorapeople.org/orphans-2023-08-21.txt grep it for your FAS username and follow the dependency chain. For human readable dependency chains, see https://packager-dashboard.fedoraproject.org/ For all orphaned packages, see https://packager-dashboard.fedoraproject.org/orphan Package (co)maintainers Status Change maven-clean-pluginmizdebsk, mkulik, orphan 4 weeks ago Hi all, I took maven-clean-plugin as some of my packages depend on it. Best wishes, Markku ___ 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 -- Marián Konček ___ 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: Orphaned packages looking for new maintainers
On Mon, Sep 04, 2023 at 05:10:55PM +0200, Miro Hrončok wrote: > The following packages are orphaned and will be retired when they > are orphaned for six weeks, unless someone adopts them. If you know for sure > that the package should be retired, please do so now with a proper reason: > https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life > > Request package ownership via the *Take* button in he left column on > https://src.fedoraproject.org/rpms/ > > Full report available at: > https://churchyard.fedorapeople.org/orphans-2023-08-21.txt > grep it for your FAS username and follow the dependency chain. > > For human readable dependency chains, > see https://packager-dashboard.fedoraproject.org/ > For all orphaned packages, > see https://packager-dashboard.fedoraproject.org/orphan > > Package (co)maintainers Status > Change > > maven-clean-pluginmizdebsk, mkulik, orphan 4 weeks ago Hi all, I took maven-clean-plugin as some of my packages depend on it. Best wishes, Markku ___ 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: FAS 2FA recovery keys?
> On 12 Sep 2023, at 10:32, Michael J Gruber wrote: > > Am Di., 12. Sept. 2023 um 11:22 Uhr schrieb Barry Scott > : >> >> I have been updating my FAS account security. >> When I setup 2FA I was not offer any recovery keys. > > You can register multiple OTP tokens: > https://docs.fedoraproject.org/en-US/infra/sysadmin_guide/2-factor/ I did notice I could setup more then one and have used pass-otp for my 2nd 2FA method. > >> In the event that I lose FreeOTP on my phone how do I recover? > > If you lost all of your tokens you can request a reset: > https://fedoraproject.org/wiki/Infrastructure_Two_Factor_Auth#What_happens_if_I_lost_my_token_or_got_a_new_device? Good to know. > > That being said, I'm in the same boat: Getting recovery keys *at the > same time* as activating 2fa has something soothing to it ... Yep, and its what I have seen for every over service I setup 2FA for. Barry > Michael > ___ > 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
Fedora rawhide compose report: 20230912.n.0 changes
OLD: Fedora-Rawhide-20230911.n.1 NEW: Fedora-Rawhide-20230912.n.0 = SUMMARY = Added images:1 Dropped images: 5 Added packages: 5 Dropped packages:1 Upgraded packages: 51 Downgraded packages: 1 Size of added packages: 17.36 MiB Size of dropped packages:68.12 KiB Size of upgraded packages: 1.39 GiB Size of downgraded packages: 19.49 KiB Size change of upgraded packages: 13.28 MiB Size change of downgraded packages: -3 B = ADDED IMAGES = Image: KDE live aarch64 Path: Spins/aarch64/iso/Fedora-KDE-Live-aarch64-Rawhide-20230912.n.0.iso = DROPPED IMAGES = Image: Sericea dvd-ostree x86_64 Path: Sericea/x86_64/iso/Fedora-Sericea-ostree-x86_64-Rawhide-20230911.n.1.iso Image: Scientific_KDE live x86_64 Path: Labs/x86_64/iso/Fedora-Scientific_KDE-Live-x86_64-Rawhide-20230911.n.1.iso Image: Mate live x86_64 Path: Spins/x86_64/iso/Fedora-MATE_Compiz-Live-x86_64-Rawhide-20230911.n.1.iso Image: LXQt live aarch64 Path: Spins/aarch64/iso/Fedora-LXQt-Live-aarch64-Rawhide-20230911.n.1.iso Image: Workstation live aarch64 Path: Workstation/aarch64/iso/Fedora-Workstation-Live-aarch64-Rawhide-20230911.n.1.iso = ADDED PACKAGES = Package: FP16-1.0^git20210317.0a92994-1.fc40 Summary: Conversion to/from half-precision floating point format RPMs:FP16-devel Size:13.34 KiB Package: libdatachannel-0.19.1-1.fc40 Summary: WebRTC network library featuring Data Channels, Media Transport, and WebSockets RPMs:libdatachannel libdatachannel-devel Size:2.85 MiB Package: objfw-1.0.2-1.fc40 Summary: Portable, lightweight framework for the Objective-C language RPMs:libobjfw libobjfw-devel libobjfwrt libobjfwrt-devel libobjfwtls libobjfwtls-devel objfw objfw-doc ofarc ofdns ofhash ofhttp Size:8.02 MiB Package: python-h5netcdf-1.2.0-1.fc40 Summary: Python interface for the netCDF4 file-format in HDF5 files RPMs:python3-h5netcdf Size:121.25 KiB Package: python-pydantic-core-2.6.3-1.fc40 Summary: Core validation logic for pydantic written in rust RPMs:python3-pydantic-core Size:6.36 MiB = DROPPED PACKAGES = Package: python-async-generator-1.10-16.fc38 Summary: Async generators and context managers RPMs:python3-async-generator Size:68.12 KiB = UPGRADED PACKAGES = Package: appx-util-0.5-2.fc40 Old package: appx-util-0.4-9.fc39 Summary: Utility to create Microsoft .appx packages RPMs: appx-util Size: 238.96 KiB Size change: 218 B Changelog: * Mon Sep 11 2023 Neal Gompa - 0.5-1 - Update to 0.5 - Migrate to SPDX license identifiers * Mon Sep 11 2023 Neal Gompa - 0.5-2 - Fix BR for Python 3 for EL8 (RH#2237698) Package: blueman-1:2.3.5-7.fc40 Old package: blueman-1:2.3.5-6.fc40 Summary: GTK+ Bluetooth Manager RPMs: blueman blueman-caja blueman-nautilus blueman-nemo Size: 6.27 MiB Size change: 1.82 KiB Changelog: * Mon Sep 11 2023 Artur Frenszek-Iwicki - 1:2.3.5-7 - Backport upstream fix for possible crash at startup (rhbz#2173854) - Backport upstream fix for crash on missing icon (rhbz#2217189) Package: ca-certificates-2023.2.60_v7.0.306-3.fc40 Old package: ca-certificates-2023.2.60_v7.0.306-2.fc39 Summary: The Mozilla CA root certificate bundle RPMs: ca-certificates Size: 837.27 KiB Size change: 48 B Changelog: * Thu Sep 07 2023 Robert Relyea - 2023.2.60_v7.0.306-3 - update License: field to SPDX Package: calibre-6.26.0-1.fc40 Old package: calibre-6.25.0-1.fc40 Summary: E-book converter and library manager RPMs: calibre Size: 51.39 MiB Size change: -2.77 MiB Changelog: * Mon Sep 11 2023 Kevin Fenzi - 6.26.0-1 - Update to 6.26.0. Fixes rhbz#2238130 Package: cups-1:2.4.6-6.fc40 Old package: cups-1:2.4.6-5.fc40 Summary: CUPS printing system RPMs: cups cups-client cups-devel cups-filesystem cups-ipptool cups-libs cups-lpd cups-printerapp Size: 24.08 MiB Size change: -4.42 KiB Changelog: * Mon Sep 11 2023 Zdenek Dohnal - 1:2.4.6-6 - use unified __python macro Package: doxygen-2:1.9.8-1.fc40 Old package: doxygen-2:1.9.7-3.fc39 Summary: A documentation system for C/C++ RPMs: doxygen doxygen-doxywizard doxygen-latex Size: 22.89 MiB Size change: 1.72 MiB Changelog: * Mon Sep 11 2023 Than Ngo - 1.9.8-1 - fix bz#2235035, update to 1.9.8 Package: extra-cmake-modules-5.240.0^20230828.163639.a93943a-2.fc40 Old package: extra-cmake-modules-5.240.0^20230828.163639.a93943a-1.fc40 Summary: Additional modules for CMake build system RPMs: extra-cmake-modules Size: 376.93 KiB Size change: 284 B Changelog: * Mon Sep 11 2023 Neal Gompa - 5.240.0^20230828.163639.a93943a-2 - Re-add runtime dependency on kf5-rpm-macros Package: f39-backgrounds-39.0.2-1.fc40 Old package: f39-backgrounds-39.0.1-1.fc40 Summary: Fedora 39 default desktop background RPMs: f39
Re: FAS 2FA recovery keys?
Am Di., 12. Sept. 2023 um 11:22 Uhr schrieb Barry Scott : > > I have been updating my FAS account security. > When I setup 2FA I was not offer any recovery keys. You can register multiple OTP tokens: https://docs.fedoraproject.org/en-US/infra/sysadmin_guide/2-factor/ > In the event that I lose FreeOTP on my phone how do I recover? If you lost all of your tokens you can request a reset: https://fedoraproject.org/wiki/Infrastructure_Two_Factor_Auth#What_happens_if_I_lost_my_token_or_got_a_new_device? That being said, I'm in the same boat: Getting recovery keys *at the same time* as activating 2fa has something soothing to it ... Michael ___ 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
FAS 2FA recovery keys?
I have been updating my FAS account security. When I setup 2FA I was not offer any recovery keys. In the event that I lose FreeOTP on my phone how do I recover? Barry ___ 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 2238421] perl-version-0.9930 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2238421 --- Comment #3 from Fedora Update System --- FEDORA-2023-4d3ae46504 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-4d3ae46504 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2238421 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202238421%23c3 ___ 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 2238421] perl-version-0.9930 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2238421 Fedora Update System changed: What|Removed |Added Fixed In Version||perl-version-0.99.30-1.fc40 Resolution|--- |ERRATA Status|MODIFIED|CLOSED Last Closed||2023-09-12 08:34:35 --- Comment #2 from Fedora Update System --- FEDORA-2023-87f9653ec4 has been pushed to the Fedora 40 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=2238421 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202238421%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
[Bug 2238421] perl-version-0.9930 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2238421 Fedora Update System changed: What|Removed |Added Status|ASSIGNED|MODIFIED --- Comment #1 from Fedora Update System --- FEDORA-2023-87f9653ec4 has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2023-87f9653ec4 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2238421 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202238421%23c1 ___ 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
Re: Anyone interested in packaging + maintaining the nimble language?
On Tue, Sep 12, 2023 at 9:22 AM Sandro wrote: > > On 12-09-2023 03:36, Maxwell G wrote: > >> It isn't packaged for Fedora yet, though. Is anyone using it, and would > >> like to package + maintain it for Fedora? > > IIRC, we used to have nim in Fedora and then it was retired. > > Indeed. That may be a good starting point. > > There's also nim-srpm-macros [1], which has a bit of a misleading name. > It's for converting nimble packages to RPM. > > [1] https://src.fedoraproject.org/rpms/nim-srpm-macros Just FYI, there is an open review ticket for nim: https://bugzilla.redhat.com/show_bug.cgi?id=2183700 (I'm not involved in any way, just happened to notice it a while ago while looking for a review swap candidate.) ___ 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: Anyone interested in packaging + maintaining the nimble language?
On 12-09-2023 03:36, Maxwell G wrote: It isn't packaged for Fedora yet, though. Is anyone using it, and would like to package + maintain it for Fedora? IIRC, we used to have nim in Fedora and then it was retired. Indeed. That may be a good starting point. There's also nim-srpm-macros [1], which has a bit of a misleading name. It's for converting nimble packages to RPM. [1] https://src.fedoraproject.org/rpms/nim-srpm-macros -- Sandro ___ 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: Anyone interested in packaging + maintaining the nimble language?
On 11-09-2023 21:05, Michel Lind wrote: It isn't packaged for Fedora yet, though. Is anyone using it, and would like to package + maintain it for Fedora? This looks like an interesting language, so #whynot (famous last words). Would you be interested in co-maintaining? I think if Nim makes it (back) into Fedora, you may add neuro-sig as co-maintainer. Going to try and beat this into shape for packaging, I've already discovered that the official tarball is missing files needed for rebuilding from source Off to a bad start. It can only get better going forward. ;) -- Sandro ___ 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
