[Bug 2223222] perl-IO-Compress-2.205 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2223222 Jitka Plesnikova changed: What|Removed |Added CC|jples...@redhat.com,| |mmasl...@redhat.com,| |mspa...@redhat.com, | |p...@city-fan.org | Doc Type|--- |If docs needed, set a value Status|NEW |ASSIGNED -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2223222 ___ 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: RFC: Roadmap for DNF5 in Fedora 39 / invoking the Contingency Mechanism
Hello Pavel, May I ask you to be more specific what is the problem with including references for issues? I am not sure whether your issues are related to issues referenced by Fabio or whether you have in mind something else. It will help us to prioritize the work. On Fri, Jul 14, 2023 at 10:50 AM Pavel Březina wrote: > On 7/13/23 23:59, Fabio Valentini wrote: > > Hi all, > > > > I'm opening this thread to trigger discussion of the roadmap for DNF5 > > in Fedora 39 - whether the switch still looks doable for this release, > > or whether it should be reverted for F39 and postponed to F40. > > +1 for postponing. We have hit issues preparing CI environment via > ansible and applying workarounds to make dnf5 work is imho not the way > to go with such core tool. It should be there as opt-in so it can get > tested but not default. > DNF5 was released in Fedora 38 where it replaced microdnf, therefore it was possible to test it in Fedora 38 Best regards Jaroslav > > > This is also being tracked in a FESCo ticket: > > https://pagure.io/fesco/issue/3039 > > > > The DNF5 Change was approved with the condition that bits that are > > important to the distribution *MUST* work, but this does not seem to > > be the case yet, six months after this was initially approved - > > there's at least a few things that are still using dnf-3 or have been > > broken since the switch to dnf5: > > > > - rawhide mock / koji builds still default to dnf-3 (DNF 4) > > - Fedora CI has been partially broken since the switch to DNF5 (c.f. > > [fedora-ci/general#416](https://pagure.io/fedora-ci/general/issue/416)), > > making CI results for bodhi updates at least partially useless > > - fedora-review has been broken since the switch to DNF5 (c.f. > > [FedoraReview#482](FedoraReview/issue/482)), which is really hurting > > the rate at which new packages are getting reviewed and added to > > Fedora > > - (not an exhaustive list, feel free to mention other things, I will > > update the list to include them) > > > > We are now mere days before the Fedora 39 mass rebuild is scheduled to > > start, so I think it's time to start talking about the roadmap for > > getting missing pieces into place for Fedora 39, or if that is not > > possible within this timeframe, whether the contingency mechanism > > should be enacted. > > > > Fabio > > ___ > > devel mailing list -- devel@lists.fedoraproject.org > > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2223238] New: perl-Test-Compile-3.3.1 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2223238 Bug ID: 2223238 Summary: perl-Test-Compile-3.3.1 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Test-Compile Keywords: FutureFeature, Triaged Assignee: jples...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: jples...@redhat.com, mmasl...@redhat.com, perl-devel@lists.fedoraproject.org Target Milestone: --- Classification: Fedora Releases retrieved: 3.3.1 Upstream release that is considered latest: 3.3.1 Current version/release in rawhide: 3.3.0-2.fc39 URL: https://metacpan.org/dist/Test-Compile/ 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/3388/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/perl-Test-Compile -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2223238 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202223238%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
Re: [Question] how to make Fedora linux os ?
Adam Williamson wrote: > This is the wrong question, kinda. There is no detailed step-by-step > process. The process for creating a compose is, more or less, "push the > magic COMPOSE NOW" button. (Okay, there's a *bit* more to it than that, > but not a lot). The SOP for it is > https://docs.pagure.org/releng/sop_composing_fedora.html . > > All the complexity, these days, is in what happens when you push the > button. Which is so complex I just couldn't stand the thought of > sitting down and writing it all out. > > *basically*...more or less...what happens when you hit the button is > that pungi - https://pagure.io/pungi - following the Fedora pungi > config - https://pagure.io/pungi-fedora - creates a whole bunch of Koji > tasks. Each of those Koji tasks does...something, there are a lot of > somethings, often using different tools. Note though (and I am writing this for other readers, I know *you* know this) that the compose process you describe here does not actually compile any packages. It just collects the packages that have previously been built in a given Koji tag and builds repositories and/or images from those. 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: [Question] how to make Fedora linux os ?
On Sun, 2023-07-16 at 15:24 -0400, Christopher wrote: > > > > There is more than one tool in use. The main build tool is Koji, but it > > depends on other underlying tools such as Mock, DNF, RPM, etc. Also keep in > > mind that in Fedora, all binaries are natively compiled, not cross-compiled > > as in Yocto. I.e., the rpmbuild process needs to run on a (real or emulated) > > CPU of the architecture for which you want to build the package. RPMs do not > > typically support cross-compilation. > > When I saw the original post, I was interested to see what responses > it would trigger. I must admit that this one is a bit disappointing. > While I've been building RPMs for Fedora for awhile now, one of the > things that has eluded me is that the Fedora OS composes seem to be > very opaque to me. I know enough to understand that Koji tags rpm > builds from individual buildroots, but from there, the process to > build the repos and the installation media, or how the buildroots are > created in the first place for Koji, or any other weirdness involved > in the construction of the OS as a whole from the individual RPM > builds, all of that seems opaque to me. I think it'd be great if there > was an up-to-date and detailed step-by-step guide for how to build a > Fedora release. Such documentation should be detailed enough that one > could stand up their own fork of the Fedora OS... not because we want > to encourage that... but because that's the level of detail that I > think is needed to allow volunteers to step in and get involved, as > the current folks move on, due to retirement, death, boredom, or > whatever. If such documentation already exists, I don't know where it > could be found. > > Do you know of any such detailed documentation, step-by-step > instructions, or maybe slides/presentations on the compose process or > overall Fedora OS build systems? This is the wrong question, kinda. There is no detailed step-by-step process. The process for creating a compose is, more or less, "push the magic COMPOSE NOW" button. (Okay, there's a *bit* more to it than that, but not a lot). The SOP for it is https://docs.pagure.org/releng/sop_composing_fedora.html . All the complexity, these days, is in what happens when you push the button. Which is so complex I just couldn't stand the thought of sitting down and writing it all out. *basically*...more or less...what happens when you hit the button is that pungi - https://pagure.io/pungi - following the Fedora pungi config - https://pagure.io/pungi-fedora - creates a whole bunch of Koji tasks. Each of those Koji tasks does...something, there are a lot of somethings, often using different tools. The whole process is logged in overwhelming detail - https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20230716.n.0/logs/ . Often the pungi logs (those ones) wind up just pointing you to a Koji task, where you will find the actual logs, e.g. the pungi 'log' for the KDE live media creation is https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20230716.n.0/logs/aarch64-x86_64/livemedia-Spins-KDE.aarch64-x86_64.log , which points you to https://koji.fedoraproject.org/koji/taskinfo?taskID=103428940 where you can find the 'real' logs. -- 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
[EPEL-devel] Fedora EPEL 7 updates-testing report
The following builds have been pushed to Fedora EPEL 7 updates-testing sloccount-2.26-37.el7 zabbix50-5.0.36-1.el7 zabbix6.0-6.0.19-1.el7 Details about builds: sloccount-2.26-37.el7 (FEDORA-EPEL-2023-c6b6a956ca) Measures source lines of code (SLOC) in programs Update Information: Build with the right LDFLAGS (fixes rpmlint warning about PIE binaries, hardens build), use symlinks rather than duplicate files ChangeLog: * Sun Jul 16 2023 Stewart Smith - 2.26-37 - Build with the right LDFLAGS (fixes rpmlint warning about PIE binaries, hardens build) - Remove executable bit on man page. * Sat Jan 21 2023 Fedora Release Engineering - 2.26-36 - Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild * Sat Jul 23 2022 Fedora Release Engineering - 2.26-35 - Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild * Thu Jun 9 2022 Bastien Nocera - 2.26-34 + sloccount-2.26-34 - Update URL * Sat Jan 22 2022 Fedora Release Engineering - 2.26-33 - Rebuilt for https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild * Fri Jul 23 2021 Fedora Release Engineering - 2.26-32 - Rebuilt for https://fedoraproject.org/wiki/Fedora_35_Mass_Rebuild * Wed Jan 27 2021 Fedora Release Engineering - 2.26-31 - Rebuilt for https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild * Wed Jul 29 2020 Fedora Release Engineering - 2.26-30 - Rebuilt for https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild * Thu Jan 30 2020 Fedora Release Engineering - 2.26-29 - Rebuilt for https://fedoraproject.org/wiki/Fedora_32_Mass_Rebuild * Fri Jul 26 2019 Fedora Release Engineering - 2.26-28 - Rebuilt for https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild * Sat Feb 2 2019 Fedora Release Engineering - 2.26-27 - Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild * Mon Jul 23 2018 Bastien Nocera - 2.26-26 + sloccount-2.26-26 - Add gcc BR * Sat Jul 14 2018 Fedora Release Engineering - 2.26-25 - Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild * Fri Feb 9 2018 Fedora Release Engineering - 2.26-24 - Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild * Thu Aug 3 2017 Fedora Release Engineering - 2.26-23 - Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Binutils_Mass_Rebuild * Thu Jul 27 2017 Fedora Release Engineering - 2.26-22 - Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Mass_Rebuild * Sat Feb 11 2017 Fedora Release Engineering - 2.26-21 - Rebuilt for https://fedoraproject.org/wiki/Fedora_26_Mass_Rebuild * Fri Feb 5 2016 Fedora Release Engineering - 2.26-20 - Rebuilt for https://fedoraproject.org/wiki/Fedora_24_Mass_Rebuild * Fri Jun 19 2015 Fedora Release Engineering - 2.26-19 - Rebuilt for https://fedoraproject.org/wiki/Fedora_23_Mass_Rebuild * Mon Aug 18 2014 Fedora Release Engineering - 2.26-18 - Rebuilt for https://fedoraproject.org/wiki/Fedora_21_22_Mass_Rebuild * Sun Jun 8 2014 Fedora Release Engineering - 2.26-17 - Rebuilt for https://fedoraproject.org/wiki/Fedora_21_Mass_Rebuild * Sun Aug 4 2013 Fedora Release Engineering - 2.26-16 - Rebuilt for https://fedoraproject.org/wiki/Fedora_20_Mass_Rebuild * Wed Jul 17 2013 Petr Pisar - 2.26-15 - Perl 5.18 rebuild zabbix50-5.0.36-1.el7 (FEDORA-EPEL-2023-62c97d6572) Open-source monitoring solution for your IT infrastructure Update Information: Update to 5.0.36 ChangeLog: * Sun Jul 16 2023 Orion Poplawski - 5.0.36-1 - Update to 5.0.36 zabbix6.0-6.0.19-1.el7 (FEDORA-EPEL-2023-75cf5daf6e) Open-source monitoring solution for your IT infrastructure Update Information: Update to 6.0.19 ChangeLog: * Sun Jul 16 2023 Orion Poplawski - 6.0.19-1 - Update to 6.0.19 ___ 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
[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-eaa3950901 rizin-0.5.2-2.el8 The following builds have been pushed to Fedora EPEL 8 updates-testing c4core-0.1.10-11.el8 c4fs-0.0.1^20220819git3b5bafa-4.el8 c4log-0.0.1^20220818gitc9477dc-5.el8 c4project-0^20230525gita1f9d73-1.el8 netcdf-4.7.0-3.el8 rapidyaml-0.4.1-8.el8 sloccount-2.26-37.el8 wgrib2-3.1.2-2.el8 x2goclient-4.1.2.3-1.el8 zabbix6.0-6.0.19-1.el8 Details about builds: c4core-0.1.10-11.el8 (FEDORA-EPEL-2023-59ede754f8) C++ core utilities Update Information: Fix incorrect multilib library paths in .cmake files in `c4core-devel`, `c4fs- devel`, `c4log-devel`, and `rapidyaml-devel`. https://bugzilla.redhat.com/show_bug.cgi?id=2223194 ChangeLog: * Sun Jul 16 2023 Benjamin A. Beasley - 0.1.10-11 - Fix wrong multilib library paths in .cmake files (fix RHBZ#2223194) * Sun Jul 16 2023 Benjamin A. Beasley - 0.1.10-10 - Improved spec-file comment on multilib path * Sun Jan 22 2023 Benjamin A. Beasley - 0.1.10-6 - Rebuild for fast_float 3.9.0 References: [ 1 ] Bug #2223194 - c4core-devel.x86-64 c4coreTargets-release.cmake (and other files) points to wrong library https://bugzilla.redhat.com/show_bug.cgi?id=2223194 c4fs-0.0.1^20220819git3b5bafa-4.el8 (FEDORA-EPEL-2023-59ede754f8) C++ file system utilities Update Information: Fix incorrect multilib library paths in .cmake files in `c4core-devel`, `c4fs- devel`, `c4log-devel`, and `rapidyaml-devel`. https://bugzilla.redhat.com/show_bug.cgi?id=2223194 ChangeLog: * Sun Jul 16 2023 Benjamin A. Beasley - 0.0.1^20220819git3b5bafa-4 - Fix wrong multilib library paths in .cmake files (fix RHBZ#2223194) * Sun Jul 16 2023 Benjamin A. Beasley - 0.0.1^20220819git3b5bafa-3 - Improved spec-file comment on multilib path References: [ 1 ] Bug #2223194 - c4core-devel.x86-64 c4coreTargets-release.cmake (and other files) points to wrong library https://bugzilla.redhat.com/show_bug.cgi?id=2223194 c4log-0.0.1^20220818gitc9477dc-5.el8 (FEDORA-EPEL-2023-59ede754f8) C++ type-safe logging, mean and lean Update Information: Fix incorrect multilib library paths in .cmake files in `c4core-devel`, `c4fs- devel`, `c4log-devel`, and `rapidyaml-devel`. https://bugzilla.redhat.com/show_bug.cgi?id=2223194 ChangeLog: * Sun Jul 16 2023 Benjamin A. Beasley - 0.0.1^20220818gitc9477dc-5 - Fix wrong multilib library paths in .cmake files (fix RHBZ#2223194) * Sun Jul 16 2023 Benjamin A. Beasley - 0.0.1^20220818gitc9477dc-4 - Improved spec-file comment on multilib path References: [ 1 ] Bug #2223194 - c4core-devel.x86-64 c4coreTargets-release.cmake (and other files) points to wrong library https://bugzilla.redhat.com/show_bug.cgi?id=2223194 c4project-0^20230525gita1f9d73-1.el8 (FEDORA-EPEL-2023-59ede754f8) Useful CMake scripts Update Information: Fix incorrect multilib library paths in .cmake files in `c4core-devel`, `c4fs- devel`, `c4log-devel`, and `rapidyaml-devel`. https://bugzilla.redhat.com/show_bug.cgi?id=2223194 ChangeLog: * Sun Jul 16 2023 Benjamin A. Beasley - 0^20230525gita1f9d73-1 - Update to 0^20230525gita1f9d73 * Sun Jul 16 2023 Benjamin A. Beasley - 0^20230512gitef46370-1 - Update to ef46370 * Sun Jul 16 2023 Benjamin A. Beasley - 0^20230410git0fb4dd1-1 - Update to 0fb4dd1 References: [ 1 ] Bug #2223194 -
[Bug 2223222] New: perl-IO-Compress-2.205 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2223222 Bug ID: 2223222 Summary: perl-IO-Compress-2.205 is available Product: Fedora Version: rawhide Status: NEW Component: perl-IO-Compress Keywords: FutureFeature, Triaged Assignee: jples...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: jples...@redhat.com, mmasl...@redhat.com, mspa...@redhat.com, p...@city-fan.org, perl-devel@lists.fedoraproject.org Target Milestone: --- Classification: Fedora Releases retrieved: 2.205 Upstream release that is considered latest: 2.205 Current version/release in rawhide: 2.204-500.fc39 URL: http://search.cpan.org/dist/IO-Compress/ 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/2990/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/perl-IO-Compress -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2223222 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202223222%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
Re: [Question] how to make Fedora linux os ?
Am 16.07.23 um 21:24 schrieb Christopher: On Sun, Jul 16, 2023 at 7:30 AM Kevin Kofler via devel wrote: Miao, Jun wrote: Hi Guys, First of all, we are not all guys. (I happen to be one though.) I would advise not to get too picky about this. The term "guys" isn't necessarily gender-specific. In its plural form, it has basically replaced "folks" in many English dialects, and holds the same non-gendered meaning. The antonyms, "guy" and "gal" have largely fallen out of favor in English, with the latter being quite rare, and the former's plural form evolving into a non-gendered usage, similar to "dude(s.)" and "dudes(pl.)" being used in non-gendered ways. While I think it's a good idea to use gender-neutral language when gendered language isn't needed, this one actually is pretty gender-neutral already, at least in the way many people use it. So, I recommend not reading too much into casual greetings like this. Getting too picky runs the risk of polarizing people and making it harder to make changes for the better where it matters. Assuming good intentions, it seems like the author intended this in the common, modern, non-gendered plural form to me. AFAIK, the Yocto Project is an open source collaboration project that provides tools, templates, and methods to help developers create custom Linux-based systems for embedded devices. My confusion is that: 1. what`s the tool to make our Fedora Linux 38 released like Yocto? There is more than one tool in use. The main build tool is Koji, but it depends on other underlying tools such as Mock, DNF, RPM, etc. Also keep in mind that in Fedora, all binaries are natively compiled, not cross-compiled as in Yocto. I.e., the rpmbuild process needs to run on a (real or emulated) CPU of the architecture for which you want to build the package. RPMs do not typically support cross-compilation. When I saw the original post, I was interested to see what responses it would trigger. I must admit that this one is a bit disappointing. While I've been building RPMs for Fedora for awhile now, one of the things that has eluded me is that the Fedora OS composes seem to be very opaque to me. I know enough to understand that Koji tags rpm builds from individual buildroots, but from there, the process to build the repos and the installation media, or how the buildroots are created in the first place for Koji, or any other weirdness involved in the construction of the OS as a whole from the individual RPM builds, all of that seems opaque to me. I think it'd be great if there was an up-to-date and detailed step-by-step guide for how to build a Fedora release. Such documentation should be detailed enough that one could stand up their own fork of the Fedora OS... not because we want to encourage that... but because that's the level of detail that I think is needed to allow volunteers to step in and get involved, as the current folks move on, due to retirement, death, boredom, or whatever. If such documentation already exists, I don't know where it could be found. Do you know of any such detailed documentation, step-by-step instructions, or maybe slides/presentations on the compose process or overall Fedora OS build systems? https://docs.pagure.org/releng/ -- Leon ___ 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: [Question] how to make Fedora linux os ?
On Sun, Jul 16, 2023 at 7:30 AM Kevin Kofler via devel wrote: > > Miao, Jun wrote: > > Hi Guys, > > First of all, we are not all guys. (I happen to be one though.) I would advise not to get too picky about this. The term "guys" isn't necessarily gender-specific. In its plural form, it has basically replaced "folks" in many English dialects, and holds the same non-gendered meaning. The antonyms, "guy" and "gal" have largely fallen out of favor in English, with the latter being quite rare, and the former's plural form evolving into a non-gendered usage, similar to "dude(s.)" and "dudes(pl.)" being used in non-gendered ways. While I think it's a good idea to use gender-neutral language when gendered language isn't needed, this one actually is pretty gender-neutral already, at least in the way many people use it. So, I recommend not reading too much into casual greetings like this. Getting too picky runs the risk of polarizing people and making it harder to make changes for the better where it matters. Assuming good intentions, it seems like the author intended this in the common, modern, non-gendered plural form to me. > > > AFAIK, the Yocto Project is an open source collaboration project that > > provides tools, templates, and methods to help developers create custom > > Linux-based systems for embedded devices. > > > > My confusion is that: > > > > 1. what`s the tool to make our Fedora Linux 38 released like Yocto? > > There is more than one tool in use. The main build tool is Koji, but it > depends on other underlying tools such as Mock, DNF, RPM, etc. Also keep in > mind that in Fedora, all binaries are natively compiled, not cross-compiled > as in Yocto. I.e., the rpmbuild process needs to run on a (real or emulated) > CPU of the architecture for which you want to build the package. RPMs do not > typically support cross-compilation. When I saw the original post, I was interested to see what responses it would trigger. I must admit that this one is a bit disappointing. While I've been building RPMs for Fedora for awhile now, one of the things that has eluded me is that the Fedora OS composes seem to be very opaque to me. I know enough to understand that Koji tags rpm builds from individual buildroots, but from there, the process to build the repos and the installation media, or how the buildroots are created in the first place for Koji, or any other weirdness involved in the construction of the OS as a whole from the individual RPM builds, all of that seems opaque to me. I think it'd be great if there was an up-to-date and detailed step-by-step guide for how to build a Fedora release. Such documentation should be detailed enough that one could stand up their own fork of the Fedora OS... not because we want to encourage that... but because that's the level of detail that I think is needed to allow volunteers to step in and get involved, as the current folks move on, due to retirement, death, boredom, or whatever. If such documentation already exists, I don't know where it could be found. Do you know of any such detailed documentation, step-by-step instructions, or maybe slides/presentations on the compose process or overall Fedora OS build systems? > > > 2. And Centos ? > > The only CentOS that is left is CentOS Stream, which (as far as I know) also > uses Koji. > > The CentOS successors such as Rocky Linux and AlmaLinux are free to either > also use Koji or use their own tools, or a combination. E.g., Rocky Linux > has developed Peridot. > > > 3. And Ubuntu ? > > Ubuntu has its own completely different tooling built around Debian's > tooling and Canonical's Launchpad platform. > > 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 ___ 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 2223070] perl-XML-LibXML-2.0209 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2223070 Fedora Update System changed: What|Removed |Added Resolution|--- |ERRATA Fixed In Version||perl-XML-LibXML-2.0209-1.fc ||39 Status|MODIFIED|CLOSED Last Closed||2023-07-16 18:54:55 --- Comment #2 from Fedora Update System --- FEDORA-2023-f19d3919c4 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=2223070 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202223070%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 2223070] perl-XML-LibXML-2.0209 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2223070 Fedora Update System changed: What|Removed |Added Status|NEW |MODIFIED --- Comment #1 from Fedora Update System --- FEDORA-2023-f19d3919c4 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-f19d3919c4 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2223070 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202223070%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 2223210] perl-Compress-Raw-Bzip2-2.205 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2223210 Fedora Update System changed: What|Removed |Added Resolution|--- |ERRATA Fixed In Version||perl-Compress-Raw-Bzip2-2.2 ||05-1.fc39 Status|MODIFIED|CLOSED Last Closed||2023-07-16 18:24:55 --- Comment #2 from Fedora Update System --- FEDORA-2023-3704990bf3 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=2223210 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202223210%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 2223211] perl-Compress-Raw-Zlib-2.205 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2223211 Fedora Update System changed: What|Removed |Added Status|MODIFIED|CLOSED Resolution|--- |ERRATA Fixed In Version||perl-Compress-Raw-Zlib-2.20 ||5-1.fc39 Last Closed||2023-07-16 18:06:55 --- Comment #2 from Fedora Update System --- FEDORA-2023-a4b2d50ad6 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=2223211 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202223211%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 2223210] perl-Compress-Raw-Bzip2-2.205 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2223210 Fedora Update System changed: What|Removed |Added Status|NEW |MODIFIED --- Comment #1 from Fedora Update System --- FEDORA-2023-3704990bf3 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-3704990bf3 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2223210 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202223210%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 2223211] perl-Compress-Raw-Zlib-2.205 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2223211 Fedora Update System changed: What|Removed |Added Status|ASSIGNED|MODIFIED --- Comment #1 from Fedora Update System --- FEDORA-2023-a4b2d50ad6 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-a4b2d50ad6 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2223211 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202223211%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 2223211] perl-Compress-Raw-Zlib-2.205 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2223211 Jitka Plesnikova changed: What|Removed |Added Doc Type|--- |If docs needed, set a value Status|NEW |ASSIGNED CC|jples...@redhat.com,| |ka...@ucw.cz, | |mspa...@redhat.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=2223211 ___ 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 2223211] New: perl-Compress-Raw-Zlib-2.205 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2223211 Bug ID: 2223211 Summary: perl-Compress-Raw-Zlib-2.205 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Compress-Raw-Zlib 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: 2.205 Upstream release that is considered latest: 2.205 Current version/release in rawhide: 2.204-500.fc39 URL: http://search.cpan.org/dist/Compress-Raw-Zlib/ 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/2712/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/perl-Compress-Raw-Zlib -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2223211 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202223211%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 2223210] New: perl-Compress-Raw-Bzip2-2.205 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2223210 Bug ID: 2223210 Summary: perl-Compress-Raw-Bzip2-2.205 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Compress-Raw-Bzip2 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: 2.205 Upstream release that is considered latest: 2.205 Current version/release in rawhide: 2.204-500.fc39 URL: http://search.cpan.org/dist/Compress-Raw-Bzip2/ 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/2711/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/perl-Compress-Raw-Bzip2 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2223210 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202223210%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
Re: Possible to combine ExclusiveArch?
On Sun, Jul 16, 2023 at 02:34:42PM +0100, Richard W.M. Jones wrote:
> On Sat, Jul 15, 2023 at 05:22:38PM +0200, Fabio Valentini wrote:
> > On Fri, Jul 14, 2023 at 2:30 PM Richard W.M. Jones
> > wrote:
> > >
> > > For some virt packages we need to combine 2 or 3 of:
> > >
> > > ExclusiveArch: %{kernel_arches}
> > > ExclusiveArch: %{qemu_sysemu_host_arches} # [1]
> > > ExclusiveArch: %{ocaml_native_compiler}
> > >
> > > to mean only compile on the intersection of these arches. If you have
> > > multiple ExclusiveArch lines then RPM seems to do the union of arches
> > > which is the opposite of what anyone would want.
> > >
> > > Dan Berrange came up with a clever way to do it though ...
> > >
> > > %ifnarch %{kernel_arches}
> > > ExcludeArch: %{_arch}
> > > %endif
> > > %ifnarch %{qemu_sysemu_host_arches}
> > > ExcludeArch: %{_arch}
> > > %endif
> > >
> > > But this makes my head hurt. Is there a better way or could RPM
> > > provide explicit union and intersection operators?
> >
> > Well, if you want set union / intersection as an RPM macro, the first
> > thing I'd try would be to implement this as a lua macro ...
> > Lua does not have a native "set" data type, but it can be simulated by
> > using a table's (hashmap's) keys as a "set".
>
> I think this works ...
>
> ExclusiveArch: %{lua:
>
> -- "impossible" ensures we don't get "Empty tag: ExclusiveArch:"
> -- if both lists are the same:
I don't mean "same" I mean "non-overlapping".
> local arches = { impossible = 1 }
>
> local karches = {}
> for a in macros.kernel_arches:gmatch("%S+") do karches[a] = 1 end
> for a in macros.java_arches:gmatch("%S+") do
> if karches[a] then arches[a] = 1 end
> end
>
> for a, t in pairs(arches) do print(a..' ') end
> }
>
> eg:
>
> $ rpmspec -P test.spec | grep ExclusiveArch
> ExclusiveArch: ppc64le x86_64 s390x impossible aarch64
>
> It's a shame Lua doesn't have an intersection operator though.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
___
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: Possible to combine ExclusiveArch?
On Sat, Jul 15, 2023 at 05:22:38PM +0200, Fabio Valentini wrote:
> On Fri, Jul 14, 2023 at 2:30 PM Richard W.M. Jones wrote:
> >
> > For some virt packages we need to combine 2 or 3 of:
> >
> > ExclusiveArch: %{kernel_arches}
> > ExclusiveArch: %{qemu_sysemu_host_arches} # [1]
> > ExclusiveArch: %{ocaml_native_compiler}
> >
> > to mean only compile on the intersection of these arches. If you have
> > multiple ExclusiveArch lines then RPM seems to do the union of arches
> > which is the opposite of what anyone would want.
> >
> > Dan Berrange came up with a clever way to do it though ...
> >
> > %ifnarch %{kernel_arches}
> > ExcludeArch: %{_arch}
> > %endif
> > %ifnarch %{qemu_sysemu_host_arches}
> > ExcludeArch: %{_arch}
> > %endif
> >
> > But this makes my head hurt. Is there a better way or could RPM
> > provide explicit union and intersection operators?
>
> Well, if you want set union / intersection as an RPM macro, the first
> thing I'd try would be to implement this as a lua macro ...
> Lua does not have a native "set" data type, but it can be simulated by
> using a table's (hashmap's) keys as a "set".
I think this works ...
ExclusiveArch: %{lua:
-- "impossible" ensures we don't get "Empty tag: ExclusiveArch:"
-- if both lists are the same:
local arches = { impossible = 1 }
local karches = {}
for a in macros.kernel_arches:gmatch("%S+") do karches[a] = 1 end
for a in macros.java_arches:gmatch("%S+") do
if karches[a] then arches[a] = 1 end
end
for a, t in pairs(arches) do print(a..' ') end
}
eg:
$ rpmspec -P test.spec | grep ExclusiveArch
ExclusiveArch: ppc64le x86_64 s390x impossible aarch64
It's a shame Lua doesn't have an intersection operator though.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
___
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 2222742] perl-Exception-Base-0.2501-23.fc39 FTBFS: t/all_tests.t fails with perl 5.38.0: Smartmatch is deprecated
https://bugzilla.redhat.com/show_bug.cgi?id=742 Fedora Update System changed: What|Removed |Added Resolution|--- |ERRATA Fixed In Version||perl-Exception-Base-0.2501- ||24.fc39 Status|MODIFIED|CLOSED Last Closed||2023-07-16 12:51:55 --- Comment #2 from Fedora Update System --- FEDORA-2023-b330fed12d 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=742 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%20742%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 2222742] perl-Exception-Base-0.2501-23.fc39 FTBFS: t/all_tests.t fails with perl 5.38.0: Smartmatch is deprecated
https://bugzilla.redhat.com/show_bug.cgi?id=742 Fedora Update System changed: What|Removed |Added Status|NEW |MODIFIED --- Comment #1 from Fedora Update System --- FEDORA-2023-b330fed12d has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-b330fed12d -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=742 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%20742%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 2223063] perl-Function-Parameters-2.002004 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2223063 Fedora Update System changed: What|Removed |Added Status|NEW |MODIFIED --- Comment #1 from Fedora Update System --- FEDORA-2023-7025406cf7 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-7025406cf7 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2223063 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202223063%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 2223063] perl-Function-Parameters-2.002004 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2223063 Fedora Update System changed: What|Removed |Added Fixed In Version||perl-Function-Parameters-2. ||2.4-1.fc39 Resolution|--- |ERRATA Status|MODIFIED|CLOSED Last Closed||2023-07-16 12:33:56 --- Comment #2 from Fedora Update System --- FEDORA-2023-7025406cf7 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=2223063 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202223063%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
Re: Possible to combine ExclusiveArch?
On Sun, Jul 16, 2023 at 01:32:49PM +0200, Kevin Kofler via devel wrote:
> Nils Philippsen wrote:
> > I beg to differ. When a tag in RPM can have multiple items (e.g.
> > Provides, (Build)Requires), this …:
> >
> > Tag: item1 item2 item3
> >
> > … is consistently equivalent to this:
> >
> > Tag: item1
> > Tag: item2
> > Tag: item3
> >
> > To have ExclusiveArch behave differently would be surprising – nobody
> > () would read this and expect the effective list of arches the
> > package would be built for to be empty:
> >
> > ExclusiveArch: x86_64
> > ExclusiveArch: s390x
> > ExclusiveArch: aarch64
>
> +1. The current union behavior is reasonable, please do not change it
> incompatibly (and inconsistenly with all other tags, as pointed out above).
I take your point that we shouldn't change it now. It is however very
weird when you first come across it (with ExclusiveArch). A syntax
like this would be clear and not incompatible:
ExclusiveArch: intersection (%{kernel_arches}, %{java_arches})
(Or even using Unicode ‘∩’ :-)
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
___
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: Possible to combine ExclusiveArch?
Nils Philippsen wrote: > I beg to differ. When a tag in RPM can have multiple items (e.g. > Provides, (Build)Requires), this …: > > Tag: item1 item2 item3 > > … is consistently equivalent to this: > > Tag: item1 > Tag: item2 > Tag: item3 > > To have ExclusiveArch behave differently would be surprising – nobody > () would read this and expect the effective list of arches the > package would be built for to be empty: > > ExclusiveArch: x86_64 > ExclusiveArch: s390x > ExclusiveArch: aarch64 +1. The current union behavior is reasonable, please do not change it incompatibly (and inconsistenly with all other tags, as pointed out above). 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: [Question] how to make Fedora linux os ?
Miao, Jun wrote: > Hi Guys, First of all, we are not all guys. (I happen to be one though.) > AFAIK, the Yocto Project is an open source collaboration project that > provides tools, templates, and methods to help developers create custom > Linux-based systems for embedded devices. > > My confusion is that: > > 1. what`s the tool to make our Fedora Linux 38 released like Yocto? There is more than one tool in use. The main build tool is Koji, but it depends on other underlying tools such as Mock, DNF, RPM, etc. Also keep in mind that in Fedora, all binaries are natively compiled, not cross-compiled as in Yocto. I.e., the rpmbuild process needs to run on a (real or emulated) CPU of the architecture for which you want to build the package. RPMs do not typically support cross-compilation. > 2. And Centos ? The only CentOS that is left is CentOS Stream, which (as far as I know) also uses Koji. The CentOS successors such as Rocky Linux and AlmaLinux are free to either also use Koji or use their own tools, or a combination. E.g., Rocky Linux has developed Peridot. > 3. And Ubuntu ? Ubuntu has its own completely different tooling built around Debian's tooling and Canonical's Launchpad platform. 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: CentOS Stream, RHEL, and Fedora [was Re: What is Fedora?]
Carlos Rodriguez-Fernandez wrote: > After much discussion, the AlmaLinux OS Foundation board today has > decided to drop the aim to be 1:1 with RHEL. AlmaLinux OS will instead > aim to be Application Binary Interface (ABI) compatible* So this is now a significant difference between AlmaLinux and Rocky Linux, which were previously basically two of the same. Rocky Linux is intent on keeping 1:1 compatibility by obtaining RHEL sources through undocumented (by RH), but apparently legal (at least according to Rocky), tricks: https://rockylinux.org/news/keeping-open-source-open/ and has reaffirmed this in their forums in light of the AlmaLinux announcement: https://forums.rockylinux.org/t/has-red-hat-just-killed-rocky-linux/10378/195 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
Fedora rawhide compose report: 20230716.n.0 changes
OLD: Fedora-Rawhide-20230715.n.0 NEW: Fedora-Rawhide-20230716.n.0 = SUMMARY = Added images:6 Dropped images: 0 Added packages: 4 Dropped packages:3 Upgraded packages: 43 Downgraded packages: 0 Size of added packages: 4.25 MiB Size of dropped packages:270.41 KiB Size of upgraded packages: 234.99 MiB Size of downgraded packages: 0 B Size change of upgraded packages: 7.07 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = Image: Kinoite dvd-ostree aarch64 Path: Kinoite/aarch64/iso/Fedora-Kinoite-ostree-aarch64-Rawhide-20230716.n.0.iso Image: Sericea dvd-ostree x86_64 Path: Sericea/x86_64/iso/Fedora-Sericea-ostree-x86_64-Rawhide-20230716.n.0.iso Image: Silverblue dvd-ostree ppc64le Path: Silverblue/ppc64le/iso/Fedora-Silverblue-ostree-ppc64le-Rawhide-20230716.n.0.iso Image: LXQt live aarch64 Path: Spins/aarch64/iso/Fedora-LXQt-Live-aarch64-Rawhide-20230716.n.0.iso Image: Workstation live aarch64 Path: Workstation/aarch64/iso/Fedora-Workstation-Live-aarch64-Rawhide-20230716.n.0.iso Image: i3 live aarch64 Path: Spins/aarch64/iso/Fedora-i3-Live-aarch64-Rawhide-20230716.n.0.iso = DROPPED IMAGES = = ADDED PACKAGES = Package: golang-github-joho-godotenv-1.5.1-2.fc39 Summary: Go port of Ruby's dotenv library RPMs:golang-github-joho-godotenv golang-github-joho-godotenv-devel Size:2.83 MiB Package: libfyaml-0.8-2.fc39 Summary: Complete YAML parser and emitter RPMs:libfyaml libfyaml-devel Size:1.34 MiB Package: lomt-junction-fonts-0^20140329gitfb73260-1.fc39 Summary: A humanist sans-serif typeface RPMs:lomt-junction-fonts Size:66.93 KiB Package: python-flexcache-0.2-1.fc39 Summary: Cache on disk the result of expensive calculations RPMs:python3-flexcache Size:23.26 KiB = DROPPED PACKAGES = Package: rust-libadwaita-sys0.1-0.1.0-2.fc38 Summary: FFI bindings for libadwaita RPMs:rust-libadwaita-sys0.1+default-devel rust-libadwaita-sys0.1+dox-devel rust-libadwaita-sys0.1-devel Size:38.90 KiB Package: rust-libadwaita0.1-0.1.1-2.fc38 Summary: Rust bindings for libadwaita RPMs:rust-libadwaita0.1+default-devel rust-libadwaita0.1+dox-devel rust-libadwaita0.1+gtk_v4_2-devel rust-libadwaita0.1+gtk_v4_4-devel rust-libadwaita0.1+gtk_v4_6-devel rust-libadwaita0.1-devel Size:111.19 KiB Package: rust-ttf-parser0.12-0.12.3-3.fc38 Summary: High-level, safe, zero-allocation TrueType font parser RPMs:rust-ttf-parser0.12+default-devel rust-ttf-parser0.12+std-devel rust-ttf-parser0.12+variable-fonts-devel rust-ttf-parser0.12-devel Size:120.31 KiB = UPGRADED PACKAGES = Package: Lmod-8.7.29-1.fc39 Old package: Lmod-8.7.25-1.fc39 Summary: Environmental Modules System in Lua RPMs: Lmod Size: 1.02 MiB Size change: 3.92 KiB Changelog: * Sat May 27 2023 Orion Poplawski - 8.7.25-2 - Add fish integration (bz#2196379) * Sat Jul 15 2023 Orion Poplawski - 8.7.29-1 - Update to 8.7.29 Package: ansible-collection-chocolatey-chocolatey-1.5.1-1.fc39 Old package: ansible-collection-chocolatey-chocolatey-1.4.0-2.fc38 Summary: Ansible collection for Chocolatey RPMs: ansible-collection-chocolatey-chocolatey Size: 55.25 KiB Size change: 2.24 KiB Changelog: * Sat Jul 15 2023 Orion Poplawski - 1.5.1-1 - Update to 1.5.1 Package: calibre-6.21.0-4.fc39 Old package: calibre-6.21.0-3.fc39 Summary: E-book converter and library manager RPMs: calibre Size: 54.39 MiB Size change: -3.36 KiB Changelog: * Thu Jul 13 2023 Kevin Fenzi - 6.21.0-4 - Rebuild for python 3.12 Package: certbot-2.6.0-3.fc39 Old package: certbot-2.6.0-1.fc39 Summary: A free, automated certificate authority client RPMs: certbot python-acme-doc python-certbot-dns-cloudflare-doc python-certbot-dns-digitalocean-doc python-certbot-dns-dnsimple-doc python-certbot-dns-dnsmadeeasy-doc python-certbot-dns-gehirn-doc python-certbot-dns-google-doc python-certbot-dns-linode-doc python-certbot-dns-luadns-doc python-certbot-dns-nsone-doc python-certbot-dns-ovh-doc python-certbot-dns-rfc2136-doc python-certbot-dns-route53-doc python-certbot-dns-sakuracloud-doc python-certbot-doc python3-acme python3-certbot python3-certbot-apache python3-certbot-dns-cloudflare python3-certbot-dns-digitalocean python3-certbot-dns-dnsimple python3-certbot-dns-dnsmadeeasy python3-certbot-dns-gehirn python3-certbot-dns-google python3-certbot-dns-linode python3-certbot-dns-luadns python3-certbot-dns-nsone python3-certbot-dns-ovh python3-certbot-dns-rfc2136 python3-certbot-dns-route53 python3-certbot-dns-sakuracloud python3-certbot-nginx Size: 3.24 MiB Size change: 8.15 KiB Changelog: * Fri Jul 07 2023 Python Maint - 2.6.0-2 - Rebuilt for Python 3.12 * Sat Jul 15 2023 Mattias Ellert - 2.6.0-3 - Fix build with Python 3.12 - Fix broken symbolic links Package: conan-2.0.8-1.fc39 Old package: conan-2.0.7-2
[Bug 2222866] perl-Business-ISBN-Data-20230714.001 is available
https://bugzilla.redhat.com/show_bug.cgi?id=866 Fedora Update System changed: What|Removed |Added Status|ASSIGNED|MODIFIED --- Comment #1 from Fedora Update System --- FEDORA-2023-4d5ca9de78 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-4d5ca9de78 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=866 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%20866%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 2222866] perl-Business-ISBN-Data-20230714.001 is available
https://bugzilla.redhat.com/show_bug.cgi?id=866 Fedora Update System changed: What|Removed |Added Resolution|--- |ERRATA Status|MODIFIED|CLOSED Fixed In Version||perl-Business-ISBN-Data-202 ||30714.001-1.fc39 Last Closed||2023-07-16 10:42:55 --- Comment #2 from Fedora Update System --- FEDORA-2023-4d5ca9de78 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=866 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%20866%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 2222866] perl-Business-ISBN-Data-20230714.001 is available
https://bugzilla.redhat.com/show_bug.cgi?id=866 Paul Howarth changed: What|Removed |Added Doc Type|--- |If docs needed, set a value Status|NEW |ASSIGNED Assignee|jples...@redhat.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=866 ___ 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
Ownership application for the arm-none-eabi-gdb package
See https://pagure.io/packager-sponsors/issue/579 for more details ___ 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
