Fedora rawhide compose report: 20220401.n.1 changes
OLD: Fedora-Rawhide-20220401.n.0 NEW: Fedora-Rawhide-20220401.n.1 = SUMMARY = Added images:1 Dropped images: 0 Added packages: 1 Dropped packages:0 Upgraded packages: 59 Downgraded packages: 0 Size of added packages: 262.85 KiB Size of dropped packages:0 B Size of upgraded packages: 3.78 GiB Size of downgraded packages: 0 B Size change of upgraded packages: 74.79 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = Image: Design_suite live x86_64 Path: Labs/x86_64/iso/Fedora-Design_suite-Live-x86_64-Rawhide-20220401.n.1.iso = DROPPED IMAGES = = ADDED PACKAGES = Package: perl-OpenGL-GLUT-0.72-1.fc37 Summary: Perl bindings to GLUT/FreeGLUT GUI toolkit RPMs:perl-OpenGL-GLUT Size:262.85 KiB = DROPPED PACKAGES = = UPGRADED PACKAGES = Package: FlightGear-2020.3.13-1.fc37 Old package: FlightGear-2020.3.12-2.fc37 Summary: The FlightGear Flight Simulator RPMs: FlightGear Size: 28.58 MiB Size change: 48.08 KiB Changelog: * Thu Mar 31 2022 Fabrice Bellet - 2020.3.13-1 - new upstream release Package: FlightGear-Atlas-0.5.0-0.76.cvs20141002.fc37 Old package: FlightGear-Atlas-0.5.0-0.75.cvs20141002.fc37 Summary: Flightgear map tools RPMs: FlightGear-Atlas Size: 2.84 MiB Size change: -723 B Changelog: * Thu Mar 31 2022 Fabrice Bellet - 0.5.0-0.76.cvs20141002 - rebuild with newer SimGear Package: FlightGear-data-2020.3.13-1.fc37 Old package: FlightGear-data-2020.3.12-1.fc36 Summary: FlightGear base scenery and data files RPMs: FlightGear-data Size: 1.68 GiB Size change: 1.34 MiB Changelog: * Thu Mar 31 2022 Fabrice Bellet - 2020.3.13-1 - new upstream release Package: GoldenCheetah-1:3.6-0.14.20220320gita0c2034.fc37 Old package: GoldenCheetah-1:3.6-0.13.20220307git6b7121b.fc37 Summary: Cycling Performance Software RPMs: GoldenCheetah GoldenCheetah-data GoldenCheetah-doc Size: 26.01 MiB Size change: 1.16 KiB Changelog: * Fri Apr 01 2022 Martin Gansser - 3.6-0.14.20220320gita0c2034 - Update to 3.6-0.14.20220320gita0c2034 Package: SimGear-2020.3.13-1.fc37 Old package: SimGear-2020.3.12-1.fc36 Summary: Simulation library components RPMs: SimGear SimGear-devel Size: 10.26 MiB Size change: 8.04 KiB Changelog: * Thu Mar 31 2022 Fabrice Bellet - 2020.3.13-1 - new upstream release Package: apache-sshd-1:2.8.0-1.fc37 Old package: apache-sshd-1:2.6.0-5.fc36 Summary: Apache SSHD RPMs: apache-sshd apache-sshd-javadoc Size: 3.84 MiB Size change: 178.45 KiB Changelog: * Fri Apr 01 2022 Mat Booth - 1:2.8.0-1 - Update to latest upstream release Package: blender-1:3.1.2-2.fc37 Old package: blender-1:3.1.0-7.fc37 Summary: 3D modeling, animation, rendering and post-production RPMs: blender blender-rpm-macros Size: 154.85 MiB Size change: 21.72 KiB Changelog: * Fri Apr 01 2022 Fedora Release Monitoring 1:3.1.1-1 - Update to 3.1.1 (#2070344) * Fri Apr 01 2022 Fedora Release Monitoring 1:3.1.2-1 - Update to 3.1.2 (#2070344) Package: containernetworking-plugins-1.1.1-1.fc37 Old package: containernetworking-plugins-1.1.0-1.fc37 Summary: Libraries for writing CNI plugin RPMs: containernetworking-plugins Size: 29.05 MiB Size change: 13.17 KiB Changelog: * Fri Apr 01 2022 Lokesh Mandvekar 1.1.1-1 - bump to v1.1.1 Package: dr_libs-0-0.15.20220331gitc729134.fc37 Old package: dr_libs-0-0.14.20220207git1e42667.fc36 Summary: Single-file audio decoding libraries for C/C++ RPMs: dr_flac-devel dr_libs-devel dr_libs-doc dr_mp3-devel dr_wav-devel Size: 187.11 KiB Size change: 881 B Changelog: * Thu Mar 31 2022 Benjamin A. Beasley 0-0.15 - Update to c72913 (dr_flac 0.12.37) Package: dummy-test-package-gloster-0-7925.fc37 Old package: dummy-test-package-gloster-0-7912.fc37 Summary: Dummy Test Package called Gloster RPMs: dummy-test-package-gloster Size: 476.25 KiB Size change: 743 B Changelog: * Fri Apr 01 2022 packagerbot - 0-7913 - rebuilt * Fri Apr 01 2022 packagerbot - 0-7914 - rebuilt * Fri Apr 01 2022 packagerbot - 0-7915 - rebuilt * Fri Apr 01 2022 packagerbot - 0-7916 - rebuilt * Fri Apr 01 2022 packagerbot - 0-7917 - rebuilt * Fri Apr 01 2022 packagerbot - 0-7918 - rebuilt * Fri Apr 01 2022 packagerbot - 0-7919 - rebuilt * Fri Apr 01 2022 packagerbot - 0-7920 - rebuilt * Fri Apr 01 2022 packagerbot - 0-7921 - rebuilt * Fri Apr 01 2022 packagerbot - 0-7922 - rebuilt * Fri Apr 01 2022 packagerbot - 0-7923 - rebuilt * Fri Apr 01 2022 packagerbot - 0-7924 - rebuilt * Fri Apr 01 2022 packagerbot - 0-7925 - rebuilt Package: ecj-1:4.23-1.fc37 Old package: ecj-1:4.22-3.fc36 Summary: Eclipse Compiler for Java RPMs
Fedora 36 compose report: 20220401.n.1 changes
OLD: Fedora-36-20220401.n.0 NEW: Fedora-36-20220401.n.1 = SUMMARY = Added images:1 Dropped images: 0 Added packages: 0 Dropped packages:0 Upgraded packages: 0 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:0 B Size of upgraded packages: 0 B Size of downgraded packages: 0 B Size change of upgraded packages: 0 B Size change of downgraded packages: 0 B = ADDED IMAGES = Image: Xfce raw-xz aarch64 Path: Spins/aarch64/images/Fedora-Xfce-36-20220401.n.1.aarch64.raw.xz = DROPPED IMAGES = = ADDED PACKAGES = = DROPPED PACKAGES = = UPGRADED PACKAGES = = DOWNGRADED PACKAGES = ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Fedora EPEL 8 updates-testing report
The following Fedora EPEL 8 Security updates need testing: Age URL 6 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-e692c0b6ee phoronix-test-suite-10.8.2-1.el8 6 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-eb750aaec6 seamonkey-2.53.11.1-1.el8 2 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-5b50dd1ab7 chromium-99.0.4844.84-1.el8 The following builds have been pushed to Fedora EPEL 8 updates-testing atool-0.39.0-19.el8 dr_libs-0-0.15.20220331gitc729134.el8 swift-lang-5.6-1.el8 Details about builds: atool-0.39.0-19.el8 (FEDORA-EPEL-2022-3608bce53b) A perl script for managing file archives of various types Update Information: atool build for epel8/epel9 ChangeLog: * Wed Jan 19 2022 Fedora Release Engineering - 0.39.0-19 - Rebuilt for https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild * Wed Jul 21 2021 Fedora Release Engineering - 0.39.0-18 - Rebuilt for https://fedoraproject.org/wiki/Fedora_35_Mass_Rebuild * Tue Jan 26 2021 Fedora Release Engineering - 0.39.0-17 - Rebuilt for https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild * Fri Jan 1 2021 Filipe Rosset - 0.39.0-16 - spec cleanup and modernization * Mon Jul 27 2020 Fedora Release Engineering - 0.39.0-15 - Rebuilt for https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild * Tue Jan 28 2020 Fedora Release Engineering - 0.39.0-14 - Rebuilt for https://fedoraproject.org/wiki/Fedora_32_Mass_Rebuild * Wed Jul 24 2019 Fedora Release Engineering - 0.39.0-13 - Rebuilt for https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild * Thu Jan 31 2019 Fedora Release Engineering - 0.39.0-12 - Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild * Thu Jul 12 2018 Fedora Release Engineering - 0.39.0-11 - Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild * Wed Feb 7 2018 Fedora Release Engineering - 0.39.0-10 - Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild * Wed Jul 26 2017 Fedora Release Engineering - 0.39.0-9 - Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Mass_Rebuild * Fri Feb 10 2017 Fedora Release Engineering - 0.39.0-8 - Rebuilt for https://fedoraproject.org/wiki/Fedora_26_Mass_Rebuild * Wed Feb 3 2016 Fedora Release Engineering - 0.39.0-7 - Rebuilt for https://fedoraproject.org/wiki/Fedora_24_Mass_Rebuild * Wed Jun 17 2015 Fedora Release Engineering - 0.39.0-6 - Rebuilt for https://fedoraproject.org/wiki/Fedora_23_Mass_Rebuild * Sat Jun 7 2014 Fedora Release Engineering - 0.39.0-5 - Rebuilt for https://fedoraproject.org/wiki/Fedora_21_Mass_Rebuild * Sat Aug 3 2013 Fedora Release Engineering - 0.39.0-4 - Rebuilt for https://fedoraproject.org/wiki/Fedora_20_Mass_Rebuild * Wed Jul 17 2013 Petr Pisar - 0.39.0-3 - Perl 5.18 rebuild * Wed Feb 13 2013 Fedora Release Engineering - 0.39.0-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_19_Mass_Rebuild * Tue Sep 25 2012 Elder Marco - 0.39.0-1 - Update to 0.39.0 * Wed Jul 18 2012 Fedora Release Engineering - 0.37.0-4 - Rebuilt for https://fedoraproject.org/wiki/Fedora_18_Mass_Rebuild * Thu Jan 12 2012 Fedora Release Engineering - 0.37.0-3 - Rebuilt for https://fedoraproject.org/wiki/Fedora_17_Mass_Rebuild * Mon Feb 7 2011 Fedora Release Engineering - 0.37.0-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_15_Mass_Rebuild * Wed Oct 27 2010 Pierre Carrier 0.37.0-1 - Initial packaging References: [ 1 ] Bug #1982774 - Please branch and build atool for EPEL8 https://bugzilla.redhat.com/show_bug.cgi?id=1982774 dr_libs-0-0.15.20220331gitc729134.el8 (FEDORA-EPEL-2022-292d07cfed) Single-file audio decoding libraries for C/C++ Update Information: ### dr_flac 0.12.37 - 2022-02-12- Improve ARM detection. ChangeLog: * Thu Mar 31 2022 Benjamin A. Beasley 0-0.15 - Update to c72913 (dr_flac 0.12.37) swift-lang-5.6-1.el8 (FEDORA-EPEL-2022-b0b75d5b36) Apple's Swift programming language Update Information: Updated to Swift 5.6-RELEASE ChangeLog: * Wed Mar 30 2022 Ron Olson
[Bug 2070684] perl-Chart-2.400.5 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2070684 --- Comment #7 from Fedora Update System --- FEDORA-2022-572049ecc9 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-572049ecc9` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-572049ecc9 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=2070684 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2070684] perl-Chart-2.400.5 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2070684 --- Comment #6 from Fedora Update System --- FEDORA-2022-dee64826ff has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-dee64826ff` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-dee64826ff 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=2070684 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Today's rawhide compose is taking a long time to fully sync
On Fri, Apr 01, 2022 at 03:27:30PM -0500, Bruno Wolff III wrote: > On Fri, Apr 01, 2022 at 10:06:35 -0700, > Kevin Fenzi wrote: > > > > Short version: > > We updated to koji 1.28.0 yesterday. It has a bug in it where it writes > > out signed rpms as mode 0600, which prevents our sync process from > > syncing those things. The compose finished and tried to sync, but of > > course failed on all those newly built packages. :( > > > > I am working now to fix the affected signed rpms, and then we are going > > to run new composes. > > Thanks for the explanation and work to get things working again. No problem. :) Update: My find finished around 23:30UTC finding 3703 affected written out rpms. I Changed them all to mode 0644 and fired off branched and rawhide composes. Those should hopefully finish in a few hours. 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1939439] perl-MouseX-App-Cmd-0.30-20.fc35 FTBFS: Failed test 'Internal hashes match' at t/build_emulates_new.t line 18.
https://bugzilla.redhat.com/show_bug.cgi?id=1939439 Fedora Update System changed: What|Removed |Added Status|ON_QA |CLOSED Resolution|--- |ERRATA Fixed In Version||perl-MouseX-App-Cmd-0.30-23 ||.fc35 Last Closed|2021-03-21 12:24:57 |2022-04-02 01:54:12 --- Comment #7 from Fedora Update System --- FEDORA-2022-f865a50115 has been pushed to the Fedora 35 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=1939439 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1964649] F35FailsToInstall: perl-MouseX-App-Cmd
https://bugzilla.redhat.com/show_bug.cgi?id=1964649 Fedora Update System changed: What|Removed |Added Status|ON_QA |CLOSED Fixed In Version||perl-MouseX-App-Cmd-0.30-23 ||.fc35 Resolution|--- |ERRATA Last Closed|2022-03-24 14:56:01 |2022-04-02 01:54:18 --- Comment #8 from Fedora Update System --- FEDORA-2022-f865a50115 has been pushed to the Fedora 35 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=1964649 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1964649] F35FailsToInstall: perl-MouseX-App-Cmd
https://bugzilla.redhat.com/show_bug.cgi?id=1964649 Bug 1964649 depends on bug 1939439, which changed state. Bug 1939439 Summary: perl-MouseX-App-Cmd-0.30-20.fc35 FTBFS: Failed test 'Internal hashes match' at t/build_emulates_new.t line 18. https://bugzilla.redhat.com/show_bug.cgi?id=1939439 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=1964649 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2070025] perl-Test-Smoke-1.79 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2070025 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #2 from Fedora Update System --- FEDORA-2022-5e366ee2ec has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-5e366ee2ec` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-5e366ee2ec 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=2070025 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2070684] perl-Chart-2.400.5 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2070684 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #5 from Fedora Update System --- FEDORA-2022-119b7b03f0 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-119b7b03f0` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-119b7b03f0 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=2070684 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Looking for provenpackager to update rapid-photo-downloader package
On Tue, Mar 29, 2022 at 5:45 PM Michel Alexandre Salim wrote: > > On Tue, Mar 29, 2022 at 05:57:52PM -, Damon Lynch wrote: > > Greetings Fedora community, I am the developer of Rapid Photo Downloader. > > The package for it in Fedora is about two years old, and crashes during > > start-up under Python 3.10. > > > > As the subject says, I'm looking for a provenpackager to update the > > package. I'm posting this message here at the suggestion of a fellow PyQt > > developer who unlike myself is a Fedora expert. > > > > I filed a bug report last year but the maintainer has been unable to work > > on it: https://bugzilla.redhat.com/show_bug.cgi?id=2031866 > > Meanwhile, two months ago Neal Gompa made this pull request to update it: > > https://src.fedoraproject.org/rpms/rapid-photo-downloader/pull-request/3 > > > I'm a provenpackager, but so is Neal, so I just pinged him to see if he > wants to merge and push an update. > I've submitted the updates to fix it for F35 and F36 with Onuralp's help. * F36: https://bodhi.fedoraproject.org/updates/FEDORA-2022-853254e9b9 * F35: https://bodhi.fedoraproject.org/updates/FEDORA-2022-50a2685dce -- 真実はいつも一つ！/ Always, there's only one truth! ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2069285] perl-HTML-Parser-3.78 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2069285 --- Comment #6 from Fedora Update System --- FEDORA-2022-3a6a242e46 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-3a6a242e46` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-3a6a242e46 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=2069285 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Test-Announce] 2022-04-04 @ 16:00 UTC - Fedora 36 Blocker Review Meeting
# F36 Blocker Review meeting # Date: 2022-04-04 # Time: 16:00 UTC # Location: #fedora-blocker-review on irc.libera.chat Hi folks! We have 9 proposed Final blockers and 3 proposed Final freeze exception issues to review, so let's have a review meeting on Monday. Note, I won't be around to run this one - you'll be in the capable hands of Geoff (coremodule). If you have time this weekend, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F36 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good weekend and Geoff will see you on Monday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net ___ test-announce mailing list -- test-annou...@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2071132] New: perl-Chart-2.400.10 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2071132 Bug ID: 2071132 Summary: perl-Chart-2.400.10 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Chart Keywords: FutureFeature, Triaged Assignee: ppi...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: perl-devel@lists.fedoraproject.org, ppi...@redhat.com, st...@silug.org Target Milestone: --- Classification: Fedora Latest upstream release: 2.400.10 Current version/release in rawhide: 2.400.5-1.fc37 URL: http://search.cpan.org/dist/Chart/ 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://fedoraproject.org/wiki/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/5871/ -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2071132 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: F36 - Errors/Warnings with `dnf update`
Panu Matilainen kirjoitti 1.4.2022 klo 16.26: On 3/31/22 14:10, Daniel Walsh wrote: On 3/31/22 02:35, Carmelo Sarta wrote: Hello there! I've never seen this error before `error: Plugin selinux: hook fsm_file_prepare failed` but I would try `dnf reinstall container-selinux` and maybe `dnf reinstall podman` There seems to be an error appening when people are installing container-selinux, that I have not pinned down. It does not happen on my system. There's a bug on this now as well: https://bugzilla.redhat.com/show_bug.cgi?id=2070942 Should I reassign to container-selinux? Looks like a duplicate of [1]. [1]: https://bugzilla.redhat.com/show_bug.cgi?id=2056303 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Today's rawhide compose is taking a long time to fully sync
On Fri, Apr 01, 2022 at 10:06:35 -0700, Kevin Fenzi wrote: Short version: We updated to koji 1.28.0 yesterday. It has a bug in it where it writes out signed rpms as mode 0600, which prevents our sync process from syncing those things. The compose finished and tried to sync, but of course failed on all those newly built packages. :( I am working now to fix the affected signed rpms, and then we are going to run new composes. Thanks for the explanation and work to get things working again. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
FedoraRespin-35-updates-20220401.0 compose check report
No missing expected images. Failed openQA tests: 4/48 (x86_64) ID: 1206636 Test: x86_64 Workstation-live-iso gnome_text_editor URL: https://openqa.fedoraproject.org/tests/1206636 ID: 1206657 Test: x86_64 KDE-live-iso desktop_notifications_live URL: https://openqa.fedoraproject.org/tests/1206657 ID: 1206671 Test: x86_64 KDE-live-iso apps_startstop URL: https://openqa.fedoraproject.org/tests/1206671 ID: 1206674 Test: x86_64 KDE-live-iso desktop_login URL: https://openqa.fedoraproject.org/tests/1206674 Soft failed openQA tests: 4/48 (x86_64) (Tests completed, but using a workaround for a known bug) ID: 1206639 Test: x86_64 Workstation-live-iso apps_startstop URL: https://openqa.fedoraproject.org/tests/1206639 ID: 1206643 Test: x86_64 Workstation-live-iso desktop_browser URL: https://openqa.fedoraproject.org/tests/1206643 ID: 1206654 Test: x86_64 Workstation-live-iso eog URL: https://openqa.fedoraproject.org/tests/1206654 ID: 1206664 Test: x86_64 KDE-live-iso desktop_browser URL: https://openqa.fedoraproject.org/tests/1206664 Passed openQA tests: 40/48 (x86_64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora-36-20220401.n.0 compose check report
No missing expected images. Failed openQA tests: 5/229 (x86_64), 7/161 (aarch64) New failures (same test not failed in Fedora-36-20220330.n.0): ID: 1205838 Test: x86_64 Workstation-live-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/1205838 ID: 1205919 Test: aarch64 Server-dvd-iso install_standard_partition_ext4@uefi URL: https://openqa.fedoraproject.org/tests/1205919 ID: 1206040 Test: aarch64 Workstation-upgrade base_system_logging@uefi URL: https://openqa.fedoraproject.org/tests/1206040 ID: 1206103 Test: x86_64 universal install_blivet_lvmthin URL: https://openqa.fedoraproject.org/tests/1206103 ID: 1206132 Test: aarch64 universal install_mirrorlist_graphical@uefi URL: https://openqa.fedoraproject.org/tests/1206132 ID: 1206165 Test: aarch64 universal install_iscsi@uefi URL: https://openqa.fedoraproject.org/tests/1206165 Old failures (same test failed in Fedora-36-20220330.n.0): ID: 1205878 Test: x86_64 KDE-live-iso apps_startstop URL: https://openqa.fedoraproject.org/tests/1205878 ID: 1205977 Test: aarch64 Workstation-raw_xz-raw.xz gnome_text_editor@uefi URL: https://openqa.fedoraproject.org/tests/1205977 ID: 1206010 Test: x86_64 Workstation-upgrade apps_startstop URL: https://openqa.fedoraproject.org/tests/1206010 ID: 1206032 Test: aarch64 Workstation-upgrade gnome_text_editor@uefi URL: https://openqa.fedoraproject.org/tests/1206032 ID: 1206098 Test: x86_64 universal install_asian_language URL: https://openqa.fedoraproject.org/tests/1206098 ID: 1206157 Test: aarch64 universal install_asian_language@uefi URL: https://openqa.fedoraproject.org/tests/1206157 Soft failed openQA tests: 10/229 (x86_64), 6/161 (aarch64) (Tests completed, but using a workaround for a known bug) New soft failures (same test not soft failed in Fedora-36-20220330.n.0): ID: 1205888 Test: x86_64 Silverblue-dvd_ostree-iso eog URL: https://openqa.fedoraproject.org/tests/1205888 ID: 1205893 Test: x86_64 Silverblue-dvd_ostree-iso desktop_browser URL: https://openqa.fedoraproject.org/tests/1205893 ID: 1205895 Test: x86_64 Silverblue-dvd_ostree-iso evince URL: https://openqa.fedoraproject.org/tests/1205895 ID: 1205896 Test: x86_64 Silverblue-dvd_ostree-iso gnome_text_editor URL: https://openqa.fedoraproject.org/tests/1205896 ID: 1205953 Test: aarch64 Server-dvd-iso server_cockpit_basic@uefi URL: https://openqa.fedoraproject.org/tests/1205953 ID: 1205992 Test: aarch64 Workstation-raw_xz-raw.xz eog@uefi URL: https://openqa.fedoraproject.org/tests/1205992 Old soft failures (same test soft failed in Fedora-36-20220330.n.0): ID: 1205846 Test: x86_64 Workstation-live-iso apps_startstop URL: https://openqa.fedoraproject.org/tests/1205846 ID: 1205850 Test: x86_64 Workstation-live-iso desktop_browser URL: https://openqa.fedoraproject.org/tests/1205850 ID: 1205861 Test: x86_64 Workstation-live-iso eog URL: https://openqa.fedoraproject.org/tests/1205861 ID: 1205871 Test: x86_64 KDE-live-iso desktop_browser URL: https://openqa.fedoraproject.org/tests/1205871 ID: 1205902 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/1205902 ID: 1205991 Test: aarch64 Workstation-raw_xz-raw.xz desktop_browser@uefi URL: https://openqa.fedoraproject.org/tests/1205991 ID: 1205996 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/1205996 ID: 1206004 Test: x86_64 Workstation-upgrade desktop_browser URL: https://openqa.fedoraproject.org/tests/1206004 ID: 1206026 Test: aarch64 Workstation-upgrade desktop_browser@uefi URL: https://openqa.fedoraproject.org/tests/1206026 ID: 1206039 Test: aarch64 Workstation-upgrade eog@uefi URL: https://openqa.fedoraproject.org/tests/1206039 Passed openQA tests: 213/229 (x86_64), 148/161 (aarch64) New passes (same test not passed in Fedora-36-20220330.n.0): ID: 1205886 Test: x86_64 Silverblue-dvd_ostree-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/1205886 ID: 1205887 Test: x86_64 Silverblue-dvd_ostree-iso base_reboot_unmount URL: https://openqa.fedoraproject.org/tests/1205887 ID: 1205889 Test: x86_64 Silverblue-dvd_ostree-iso base_selinux URL: https://openqa.fedoraproject.org/tests/1205889 ID: 1205890 Test: x86_64 Silverblue-dvd_ostree-iso release_identification URL: https://openqa.fedoraproject.org/tests/1205890 ID: 1205891 Test: x86_64 Silverblue-dvd_ostree-iso desktop_background URL: https://openqa.fedoraproject.org/tests/1205891 ID: 1205892 Test: x86_64 Silverblue-dvd_ostree-iso base_services_start URL: https://openqa.fedoraproject.org/tests/1205892 ID: 1205894 Test: x86_64 Silverblue-dvd_ostree-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/1205894 ID: 1205897 Test: x86_64 Silverblue-dvd_ostree-iso base_service_manipulation URL: https://openqa.fedoraproject.org/tests/1205897 ID: 1205898 Test: x86_64
[Bug 2071100] New: perl-Locale-Maketext-1.30 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2071100 Bug ID: 2071100 Summary: perl-Locale-Maketext-1.30 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Locale-Maketext Keywords: FutureFeature, Triaged Assignee: jples...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: jples...@redhat.com, mspa...@redhat.com, perl-devel@lists.fedoraproject.org, ppi...@redhat.com Target Milestone: --- Classification: Fedora Latest upstream release: 1.30 Current version/release in rawhide: 1.29-480.fc36 URL: http://search.cpan.org/dist/Locale-Maketext/ 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://fedoraproject.org/wiki/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/3034/ -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2071100 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: F37 Change: Signed RPM Contents (System-Wide Change proposal)
> [...] > == How To Test == > You can verify that a signature has been put in place by looking at > the extended attribute by running: `getfattr -d -m security.ima > /usr/bin/bash` (change `/usr/bin/bash` with the file to check). Can one easily query the RPM archive for the signature blob for any given file it contains? > The signatures can be tested “in vitro” by running `evmctl ima_verify > --key publiccert.der -v myfile.txt`. > [...] > The full system could be tested by enrolling the Fedora IMA key [...] How will this key be distributed on the distro filesystem or on the web? Will it be signed by an already trusted CA? - FChE ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora-IoT-36-20220401.2 compose check report
No missing expected images. Failed openQA tests: 1/15 (x86_64), 3/15 (aarch64) New failures (same test not failed in Fedora-IoT-36-20220326.0): ID: 1206605 Test: x86_64 IoT-dvd_ostree-iso release_identification@uefi URL: https://openqa.fedoraproject.org/tests/1206605 ID: 1206627 Test: aarch64 IoT-dvd_ostree-iso iot_rpmostree_overlay@uefi URL: https://openqa.fedoraproject.org/tests/1206627 ID: 1206628 Test: aarch64 IoT-dvd_ostree-iso release_identification@uefi URL: https://openqa.fedoraproject.org/tests/1206628 Old failures (same test failed in Fedora-IoT-36-20220326.0): ID: 1206615 Test: aarch64 IoT-dvd_ostree-iso iot_clevis@uefi URL: https://openqa.fedoraproject.org/tests/1206615 Passed openQA tests: 14/15 (x86_64), 12/15 (aarch64) New passes (same test not passed in Fedora-IoT-36-20220326.0): ID: 1206612 Test: x86_64 IoT-dvd_ostree-iso iot_zezere_server@uefi URL: https://openqa.fedoraproject.org/tests/1206612 ID: 1206614 Test: x86_64 IoT-dvd_ostree-iso iot_zezere_ignition@uefi URL: https://openqa.fedoraproject.org/tests/1206614 Installed system changes in test aarch64 IoT-dvd_ostree-iso install_default_upload@uefi: System load changed from 0.27 to 0.40 Previous test data: https://openqa.fedoraproject.org/tests/1198137#downloads Current test data: https://openqa.fedoraproject.org/tests/1206616#downloads -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Test-Announce] Fedora 36 validation testing event: let's do full testing of Fedora 36 Branched 20220401.n.0
Hi folks! Trying something a bit new here. I've nominated today's Fedora 36 nightly compose for validation testing. We do this regularly in any case, but I'm sending this out to a wider group and asking folks to treat this nightly as it it were a release candidate, and try to complete the *full* set of Final validation tests on it. The idea is to try and make sure we get all the tests done well ahead of the Go/No-Go Meeting, so we can identify any remaining blocker bugs *now*, not have to try and deal with them in a hurry later. Test coverage information for the current release can be seen at: https://openqa.fedoraproject.org/testcase_stats/36 . You can use this to prioritize tests that have not yet been run at all. 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_36_Branched_20220401.n.0_Summary The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_36_Branched_20220401.n.0_Installation https://fedoraproject.org/wiki/Test_Results:Fedora_36_Branched_20220401.n.0_Base https://fedoraproject.org/wiki/Test_Results:Fedora_36_Branched_20220401.n.0_Server https://fedoraproject.org/wiki/Test_Results:Fedora_36_Branched_20220401.n.0_Cloud https://fedoraproject.org/wiki/Test_Results:Fedora_36_Branched_20220401.n.0_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_36_Branched_20220401.n.0_Security_Lab The goal is to try and hit every test marked as Basic, Beta or Final (hitting the Optional ones too is great but not required). It'd be particularly good to cover things that often don't get done until late - aarch64 tests, Cloud tests in real clouds, and the full set of Server Active Directory tests, for instance. If you hit a significant failure in a test, please file a bug, and most likely propose it as a release blocker using https://qa.fedoraproject.org/blockerbugs/propose_bug . If you have any questions or need any help with testing or reporting results, please contact us on the test@ list or the QA IRC/Matrix channel (#fedora-qa on IRC, "Fedora QA (Quality Assurance)" on Matrix). Thanks a lot, folks! -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net ___ test-announce mailing list -- test-annou...@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora-Rawhide-20220401.n.0 compose check report
Missing expected images: Minimal raw-xz armhfp Compose FAILS proposed Rawhide gating check! 2 of 43 required tests failed openQA tests matching unsatisfied gating requirements shown with **GATING** below Failed openQA tests: 17/231 (x86_64), 27/161 (aarch64) New failures (same test not failed in Fedora-Rawhide-20220328.n.0): ID: 1205414 Test: x86_64 Server-dvd-iso install_blivet_resize_lvm URL: https://openqa.fedoraproject.org/tests/1205414 ID: 1205436 Test: x86_64 Workstation-live-iso gnome_text_editor URL: https://openqa.fedoraproject.org/tests/1205436 ID: 1205513 Test: aarch64 Server-dvd-iso install_btrfs_preserve_home_uefi@uefi URL: https://openqa.fedoraproject.org/tests/1205513 ID: 1205544 Test: aarch64 Server-dvd-iso install_blivet_resize_lvm@uefi URL: https://openqa.fedoraproject.org/tests/1205544 ID: 1205570 Test: aarch64 Workstation-raw_xz-raw.xz base_service_manipulation@uefi URL: https://openqa.fedoraproject.org/tests/1205570 ID: 1205571 Test: aarch64 Workstation-raw_xz-raw.xz desktop_printing@uefi URL: https://openqa.fedoraproject.org/tests/1205571 ID: 1205574 Test: aarch64 Workstation-raw_xz-raw.xz desktop_printing_builtin@uefi URL: https://openqa.fedoraproject.org/tests/1205574 ID: 1205586 Test: aarch64 Workstation-raw_xz-raw.xz desktop_browser@uefi URL: https://openqa.fedoraproject.org/tests/1205586 ID: 1205607 Test: x86_64 Workstation-upgrade desktop_printing_builtin URL: https://openqa.fedoraproject.org/tests/1205607 ID: 1205608 Test: x86_64 Workstation-upgrade gnome_text_editor URL: https://openqa.fedoraproject.org/tests/1205608 ID: 1205612 Test: x86_64 Workstation-upgrade desktop_login URL: https://openqa.fedoraproject.org/tests/1205612 ID: 1205624 Test: aarch64 Workstation-upgrade evince@uefi URL: https://openqa.fedoraproject.org/tests/1205624 ID: 1205666 Test: x86_64 universal install_european_language URL: https://openqa.fedoraproject.org/tests/1205666 ID: 1205667 Test: x86_64 universal install_cyrillic_language URL: https://openqa.fedoraproject.org/tests/1205667 ID: 1205669 Test: x86_64 universal install_with_swap URL: https://openqa.fedoraproject.org/tests/1205669 ID: 1205670 Test: x86_64 universal install_with_swap@uefi URL: https://openqa.fedoraproject.org/tests/1205670 ID: 1205683 Test: x86_64 universal upgrade_server_domain_controller URL: https://openqa.fedoraproject.org/tests/1205683 ID: 1205719 Test: aarch64 universal install_european_language@uefi URL: https://openqa.fedoraproject.org/tests/1205719 ID: 1205736 Test: aarch64 universal install_with_swap@uefi URL: https://openqa.fedoraproject.org/tests/1205736 ID: 1205737 Test: aarch64 universal upgrade_2_desktop_64bit@uefi URL: https://openqa.fedoraproject.org/tests/1205737 ID: 1205739 Test: aarch64 universal upgrade_2_desktop_encrypted_64bit@uefi URL: https://openqa.fedoraproject.org/tests/1205739 ID: 1205742 Test: aarch64 universal upgrade_desktop_encrypted_64bit@uefi URL: https://openqa.fedoraproject.org/tests/1205742 ID: 1205743 Test: aarch64 universal upgrade_minimal_64bit@uefi URL: https://openqa.fedoraproject.org/tests/1205743 ID: 1205764 Test: x86_64 universal install_kickstart_user_creation **GATING** URL: https://openqa.fedoraproject.org/tests/1205764 ID: 1205765 Test: x86_64 universal install_kickstart_firewall_disabled **GATING** URL: https://openqa.fedoraproject.org/tests/1205765 ID: 1205766 Test: x86_64 universal support_server URL: https://openqa.fedoraproject.org/tests/1205766 ID: 1205767 Test: x86_64 universal install_kickstart_nfs URL: https://openqa.fedoraproject.org/tests/1205767 ID: 1205771 Test: x86_64 universal install_kickstart_hdd URL: https://openqa.fedoraproject.org/tests/1205771 ID: 1205772 Test: aarch64 universal install_kickstart_firewall_disabled@uefi URL: https://openqa.fedoraproject.org/tests/1205772 ID: 1205773 Test: aarch64 universal support_server@uefi URL: https://openqa.fedoraproject.org/tests/1205773 ID: 1205775 Test: aarch64 universal install_kickstart_nfs@uefi URL: https://openqa.fedoraproject.org/tests/1205775 ID: 1206167 Test: aarch64 universal install_kickstart_hdd@uefi URL: https://openqa.fedoraproject.org/tests/1206167 Old failures (same test failed in Fedora-Rawhide-20220328.n.0): ID: 1205535 Test: aarch64 Server-dvd-iso install_repository_hd_variation@uefi URL: https://openqa.fedoraproject.org/tests/1205535 ID: 1205536 Test: aarch64 Server-dvd-iso mediakit_repoclosure@uefi URL: https://openqa.fedoraproject.org/tests/1205536 ID: 1205548 Test: aarch64 Server-dvd-iso server_cockpit_basic@uefi URL: https://openqa.fedoraproject.org/tests/1205548 ID: 1205556 Test: aarch64 Server-dvd-iso realmd_join_cockpit@uefi URL: https://openqa.fedoraproject.org/tests/1205556 ID: 1205572 Test: aarch64 Workstation-raw_xz-raw.xz gnome_text_editor@uefi URL: https://openqa.fedoraproject.org/tests/1205572 ID: 1205613 Test: x86_64
Re: Today's rawhide compose is taking a long time to fully sync
kernel-5.18.0-0.rc0.20220331git787af64d05cd.13.fc37.x86_64: Cannot download, all mirrors were already tried without success ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: F37 Change: Support FIDO Device Onboarding (Self-Contained Change proposal)
> On Tue, Mar 29, 2022 at 10:24:38AM -0400, Simo Sorce wrote: > > Can we get a link to the actual software stack being proposed? > > The link in this proposal is a marketing post ... > > In Peter's defense, that marketing link in the summary was my suggestion -- > I wanted something that (relatively) concisely summarized the intention of > the standard. The github page just says "An implementation of the FIDO > Device Onboard Specification" which doesn't really do that. I meant to include both, it was purely an oversight. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: newRepo is slow today
On Fri, Apr 01, 2022 at 10:16:01AM -0700, Kevin Fenzi wrote: > On Fri, Apr 01, 2022 at 06:10:03PM +0100, Richard W.M. Jones wrote: > > On Fri, Apr 01, 2022 at 10:07:39AM -0700, Kevin Fenzi wrote: > > > On Fri, Apr 01, 2022 at 05:54:52PM +0100, Richard W.M. Jones wrote: > > > > > > > > Been waiting a couple of hours I think. > > > > > > There's nothing in the queue waiting: > > > > > > https://koji.fedoraproject.org/kojira/queue > > > > > > What repo were you waiting for and what package? > > > > $ koji wait-repo f37-build --build=systemtap-4.7~pre16468670g9f253544-2.fc37 > > > > Did I get the comment wrong? > > No, thats right, but the build is blocked by gating: > > "1 of 2 required tests failed, 1 result missing" > > https://bodhi.fedoraproject.org/updates/FEDORA-2022-f6c14b3f13 .. in Rawhide? Also the install test is bogus. I already checked locally that the built package installs. The test fails with some 404 errors: https://osci-jenkins-1.ci.fedoraproject.org/job/fedora-ci/job/installability-pipeline/job/master/63472/testReport/(root)/tests/_install/ Anyhow I waived the tests. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. http://fedoraproject.org/wiki/MinGW ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: F37 Change: Support FIDO Device Onboarding (Self-Contained Change proposal)
On Tue, Mar 29, 2022 at 10:24:38AM -0400, Simo Sorce wrote: > Can we get a link to the actual software stack being proposed? > The link in this proposal is a marketing post ... In Peter's defense, that marketing link in the summary was my suggestion -- I wanted something that (relatively) concisely summarized the intention of the standard. The github page just says "An implementation of the FIDO Device Onboard Specification" which doesn't really do that. -- Matthew Miller Fedora Project Leader ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2069285] perl-HTML-Parser-3.78 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2069285 --- Comment #5 from Fedora Update System --- FEDORA-2022-d64cc63744 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-d64cc63744` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-d64cc63744 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=2069285 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2061468] perl-Text-ASCIITable: please provide epel9 package
https://bugzilla.redhat.com/show_bug.cgi?id=2061468 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #4 from Fedora Update System --- FEDORA-EPEL-2022-e789ed531d has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-e789ed531d 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=2061468 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: newRepo is slow today
On Fri, Apr 01, 2022 at 06:10:03PM +0100, Richard W.M. Jones wrote: > On Fri, Apr 01, 2022 at 10:07:39AM -0700, Kevin Fenzi wrote: > > On Fri, Apr 01, 2022 at 05:54:52PM +0100, Richard W.M. Jones wrote: > > > > > > Been waiting a couple of hours I think. > > > > There's nothing in the queue waiting: > > > > https://koji.fedoraproject.org/kojira/queue > > > > What repo were you waiting for and what package? > > $ koji wait-repo f37-build --build=systemtap-4.7~pre16468670g9f253544-2.fc37 > > Did I get the comment wrong? No, thats right, but the build is blocked by gating: "1 of 2 required tests failed, 1 result missing" https://bodhi.fedoraproject.org/updates/FEDORA-2022-f6c14b3f13 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: newRepo is slow today
On Fri, Apr 01, 2022 at 06:11:46PM +0100, Richard W.M. Jones wrote: > On Fri, Apr 01, 2022 at 06:10:03PM +0100, Richard W.M. Jones wrote: > > On Fri, Apr 01, 2022 at 10:07:39AM -0700, Kevin Fenzi wrote: > > > On Fri, Apr 01, 2022 at 05:54:52PM +0100, Richard W.M. Jones wrote: > > > > > > > > Been waiting a couple of hours I think. > > > > > > There's nothing in the queue waiting: > > > > > > https://koji.fedoraproject.org/kojira/queue > > > > > > What repo were you waiting for and what package? > > > > $ koji wait-repo f37-build --build=systemtap-4.7~pre16468670g9f253544-2.fc37 > > > > Did I get the [command] wrong? > > Oh crap, I built it into a side tag I was using earlier > today by accident :-( Er, or did I? Checking back through history, I *didn't* build this into a side tag, so why does the build have these odds tags? https://koji.fedoraproject.org/koji/buildinfo?buildID=1941805 Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. http://fedoraproject.org/wiki/MinGW ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: newRepo is slow today
On Fri, Apr 01, 2022 at 06:10:03PM +0100, Richard W.M. Jones wrote: > On Fri, Apr 01, 2022 at 10:07:39AM -0700, Kevin Fenzi wrote: > > On Fri, Apr 01, 2022 at 05:54:52PM +0100, Richard W.M. Jones wrote: > > > > > > Been waiting a couple of hours I think. > > > > There's nothing in the queue waiting: > > > > https://koji.fedoraproject.org/kojira/queue > > > > What repo were you waiting for and what package? > > $ koji wait-repo f37-build --build=systemtap-4.7~pre16468670g9f253544-2.fc37 > > Did I get the [command] wrong? Oh crap, I built it into a side tag I was using earlier today by accident :-( I'll fix this. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com nbdkit - Flexible, fast NBD server with plugins https://gitlab.com/nbdkit/nbdkit ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: newRepo is slow today
On Fri, Apr 01, 2022 at 10:07:39AM -0700, Kevin Fenzi wrote: > On Fri, Apr 01, 2022 at 05:54:52PM +0100, Richard W.M. Jones wrote: > > > > Been waiting a couple of hours I think. > > There's nothing in the queue waiting: > > https://koji.fedoraproject.org/kojira/queue > > What repo were you waiting for and what package? $ koji wait-repo f37-build --build=systemtap-4.7~pre16468670g9f253544-2.fc37 Did I get the comment wrong? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-builder quickly builds VMs from scratch http://libguestfs.org/virt-builder.1.html ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: newRepo is slow today
On Fri, Apr 01, 2022 at 05:54:52PM +0100, Richard W.M. Jones wrote: > > Been waiting a couple of hours I think. There's nothing in the queue waiting: https://koji.fedoraproject.org/kojira/queue What repo were you waiting for and what package? 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Today's rawhide compose is taking a long time to fully sync
On Fri, Apr 01, 2022 at 11:22:34AM -0500, Bruno Wolff III wrote: > Today's rawhide compose is taking a long time to sync on the primary > mirrors. It has been a mix of the update from the 28th and the one for today > for at least a couple hours. That is much longer than normal. > Did something fail part way through? Something failed before it started. See:https://pagure.io/releng/issue/10732 Short version: We updated to koji 1.28.0 yesterday. It has a bug in it where it writes out signed rpms as mode 0600, which prevents our sync process from syncing those things. The compose finished and tried to sync, but of course failed on all those newly built packages. :( I am working now to fix the affected signed rpms, and then we are going to run new composes. 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: dist-git force push
On Fri, Apr 01, 2022 at 06:22:47PM +0200, Hans de Goede wrote: > Hi, ...snip... I don't think we should ever allow force pushes in dist git repos. Even aside detecting if something has been built, you basically screw up the repo for everyone else who has work in progress against it. > 2. Or if you don't: > > fedpkg commit -sc && fedpkg scratch-build --arches=x86_64 --srpm && fedpkg > push && fedpkg build > > Notice the --arches=x86_64, this is done because some of the > other arches have limited builder capacity. Thats not really so much true anymore. All the arches have similar number of builders anymore. However, some are faster than others for sure. 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: dist-git force push
On Fri, 1 Apr 2022 18:22:47 +0200 Hans de Goede wrote: > On 4/1/22 18:09, Ondrej Mosnacek wrote: > >> Context switches for maintainers are expensive! And while I don't > >> personally think the "oops fixup" commits are a problem, a "PR > >> with CI" workflow doesn't get rid of them by any means. > > > > Why not this then: > > > > - fedpkg commit -sc && fedpkg scratch-build --srpm && fedpkg push && > > fedpkg build > > If people are going to use this, please make it one of: > > 1. If you have plenty of bandwidth + enough CPU + RAM: > > fedpkg mockbuild && fedpkg commit -sc && fedpkg push && fedpkg build > > 2. Or if you don't: > > fedpkg commit -sc && fedpkg scratch-build --arches=x86_64 --srpm && > fedpkg push && fedpkg build Unfortunately fedpkg scratch-build --srpm doesn't catch the case where the maintainer forgot to do "fedpkg new-sources" for a new upstream release. Been there, done that... Paul. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Koji down?
On Thu, Mar 31, 2022 at 06:19:06AM -0500, Ron Olson wrote: > I submitted some builds yesterday and didn’t get any emails, > and at least as of 6:18 CDT every link I click on the main webpage replies > with “server is offline”. This was likely during our scheduled outage. https://pagure.io/fedora-infrastructure/issue/10613 https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org/thread/K6CEBZYIWOXNGB556GTW26UFEP5J4CUL/ make sure you are on the devel-announce list and/or check https://www.fedorastatus.org/ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: dist-git force push
> On Fri, Apr 1, 2022 at 4:27 PM Robbie Harwood wrote: > > Why not this then: > > - fedpkg commit -sc && fedpkg scratch-build --srpm && fedpkg push > && > fedpkg build > > Yes, it'll still take longer, but you won't need to context switch > unless the scratch build fails (which would make you do a fixup commit > + another build anyway). This workflow allows you to amend the commit > until you get a successful scratch build, after which it is unlikely > that you would need to commit another fixup. Well, sure. That's what I'm doing. (Basically; since when do we sign off on dist-git?) I guess you missed my main point: What to do when a wrong commit is pushed but is not built yet? Answering "Don't push wrong commits." is only of limitted help - especially when these commits come from other people ... If everyone makes sure they check their stuff before and do not scratch-build from a dirty tree and the build not only succeeds but the results work then there is no problem to solve in the first place! But I guess the real solution is to give up on a tidy dist-git history. Makes you sleep much better :) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
newRepo is slow today
Been waiting a couple of hours I think. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into KVM guests. http://libguestfs.org/virt-v2v ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: F36 Final blocker status summary
On Fri, Apr 1, 2022 at 12:47 PM Vascom wrote: > > What about KDE spin crashes because of non stable sddm? > https://bugzilla.redhat.com/show_bug.cgi?id=2066304 > > This made F36 KDE fully unfunctional. You can nominate bugs for blocker status at https://qa.fedoraproject.org/blockerbugs/propose_bug -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: F36 Final blocker status summary
What about KDE spin crashes because of non stable sddm? https://bugzilla.redhat.com/show_bug.cgi?id=2066304 This made F36 KDE fully unfunctional. пт, 1 апр. 2022 г., 19:40 Ben Cotton : > F36 Final freeze begins Tuesday 5 April. We are currently targeting > the early target date (2022-04-19), which means we'd want to have > blockers fixed by 11 April in order to provide time for validation > testing prior to the Go/No-go meeting on 14 April. > > Action summary > > > Accepted blockers > - > > 1. anaconda — anaconda enablement of fingerprint auth overrides > existing authselect configuration — MODIFIED > ACTION: QA to verify FEDORA-2022-8538fa94da > > 2. gnome-connections — gnome-connections: _mid_memalign(): > gnome-connections killed by SIGSEGV — NEW > ACTION: Maintainers to diagnose and fix issue > > 3. mutter — The input string via Input Method isn't renderred properly > at the search box on Activities — MODIFIED > ACTION: QA to verify FEDORA-2022-566779da43 > > 4.mutter — Workstation Live is frozen in a VM with QXL video driver > (Virtio works OK) — NEW > ACTION: Maintainers to diagnose and fix issue > > 5. plasma-discover — The About button sends Discover into loop and the > application stops responding. — NEW > ACTION: Upstream to diagnose and fix issue > > 6. xorg-x11-server — Basic graphics mode broken for X11 > (GNOME/KDE/netinst) on UEFI) — NEW > ACTION: Maintainers to diagnose and fix issue > > 7. xorg-x11-server — Basic graphics mode broken for KDE BIOS mode, > screen goes black in minutes — NEW > ACTION: Maintainers to diagnose and fix issue > > > Proposed blockers > - > > 1. gnome-control-center — Printer setting: can't scroll media size list — > NEW > ACTION: Maintainers to package upstream MR 1268 > > 2. gnome-control-center — X11: Failed to create foreign window for XID > 0: clicking on already set up account in settings > online accounts > does not open a new pop up window to show account sync settings — > ON_QA > ACTION: QA to verify FEDORA-2022-67fa3533bf > > 3. hplip — Cannot print except when rebooting computer after upgrade > from F35 -> after recommended manual intervention, now cannot print > except after turning off printer and then printing a blank page in > LibreOffice — NEW > ACTION: Maintainers to diagnose and fix issue > NEEDINFO: catanzaro > > 4. libdnf — systemd-oomd kills rpm-ostree when installing a package on > Fedora IoT 36 on the Raspberry Pi Zero 2 W — NEW > ACTION: Maintainers to diagnose and fix issue > > 5. qemu — VMs hang when trying to access virtiofs mounts in the guest VM — > POST > ACTION: Maintainers to merge and build PR 22 > > 6. selinux-policy — selinux-policy is preventing flatpak from updating > / installing / removing flatpaks — NEW > ACTION: Maintainers to update policy to permit necessary flatpak actions > > 7. xdg-desktop-portal-gnome — xdg-desktop-portal-gnome: > wl_proxy_get_version(): xdg-desktop-portal-gnome killed by SIGSEGV — > MODIFIED > ACTION: QA to verify FEDORA-2022-f8681a48e6 > > Bug-by-bug detail > = > > Accepted blockers > - > > 1. anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2069899 — > MODIFIED > anaconda enablement of fingerprint auth overrides existing authselect > configuration > > anaconda overwrites the authselect config when enabling fingerprint > authentication. This disables nss-mdns (when configured), breaking > things like printer discovery. FEDORA-2022-8538fa94da contains a > candidate fix. > > 2. gnome-connections — https://bugzilla.redhat.com/show_bug.cgi?id=2068015 > — NEW > gnome-connections: _mid_memalign(): gnome-connections killed by SIGSEGV > > Connecting to an RDP server (including localhost) causes Connections > to crash immediately. Filed upstream as > https://gitlab.gnome.org/GNOME/connections/-/issues/95 > > 3. mutter — https://bugzilla.redhat.com/show_bug.cgi?id=2062660 — MODIFIED > The input string via Input Method isn't renderred properly at the > search box on Activities > > Pre-edit strings are not rendered in some cases, only showing the > first keypress. Update FEDORA-2022-566779da43 contains a candidate > fix. > > 4. mutter — https://bugzilla.redhat.com/show_bug.cgi?id=2063156 — NEW > Workstation Live is frozen in a VM with QXL video driver (Virtio works OK) > > VMs that initially use the QXL driver appears frozen. Using virtio > (including to switching to QXL after?) avoids this. KDE Lives do not > display (heh) this behavior, not does using `nomodeset`. Filed > upstream as https://gitlab.gnome.org/GNOME/mutter/-/issues/2201 > > 5. plasma-discover — https://bugzilla.redhat.com/show_bug.cgi?id=2057563 > — NEW > The About button sends Discover into loop and the application stops > responding. > > Clicking the About button causes a loop which renders Discover > unresponsive (except when the window is maximized). Confirmed upstream > as https://bugs.kde.org/show_bug.cgi?id=448784 > > 6. xorg-x11-server —
[Bug 2066942] perl-Class-Accessor-Lite: please provide epel9 package
https://bugzilla.redhat.com/show_bug.cgi?id=2066942 Fedora Update System changed: What|Removed |Added Status|ON_QA |CLOSED Fixed In Version||perl-Class-Accessor-Lite-0. ||08-16.el9 Resolution|--- |ERRATA Last Closed||2022-04-01 16:40:54 --- Comment #7 from Fedora Update System --- FEDORA-EPEL-2022-960b555aeb 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=2066942 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: F36 Final blocker status summary
F36 Final freeze begins Tuesday 5 April. We are currently targeting the early target date (2022-04-19), which means we'd want to have blockers fixed by 11 April in order to provide time for validation testing prior to the Go/No-go meeting on 14 April. Action summary Accepted blockers - 1. anaconda — anaconda enablement of fingerprint auth overrides existing authselect configuration — MODIFIED ACTION: QA to verify FEDORA-2022-8538fa94da 2. gnome-connections — gnome-connections: _mid_memalign(): gnome-connections killed by SIGSEGV — NEW ACTION: Maintainers to diagnose and fix issue 3. mutter — The input string via Input Method isn't renderred properly at the search box on Activities — MODIFIED ACTION: QA to verify FEDORA-2022-566779da43 4.mutter — Workstation Live is frozen in a VM with QXL video driver (Virtio works OK) — NEW ACTION: Maintainers to diagnose and fix issue 5. plasma-discover — The About button sends Discover into loop and the application stops responding. — NEW ACTION: Upstream to diagnose and fix issue 6. xorg-x11-server — Basic graphics mode broken for X11 (GNOME/KDE/netinst) on UEFI) — NEW ACTION: Maintainers to diagnose and fix issue 7. xorg-x11-server — Basic graphics mode broken for KDE BIOS mode, screen goes black in minutes — NEW ACTION: Maintainers to diagnose and fix issue Proposed blockers - 1. gnome-control-center — Printer setting: can't scroll media size list — NEW ACTION: Maintainers to package upstream MR 1268 2. gnome-control-center — X11: Failed to create foreign window for XID 0: clicking on already set up account in settings > online accounts does not open a new pop up window to show account sync settings — ON_QA ACTION: QA to verify FEDORA-2022-67fa3533bf 3. hplip — Cannot print except when rebooting computer after upgrade from F35 -> after recommended manual intervention, now cannot print except after turning off printer and then printing a blank page in LibreOffice — NEW ACTION: Maintainers to diagnose and fix issue NEEDINFO: catanzaro 4. libdnf — systemd-oomd kills rpm-ostree when installing a package on Fedora IoT 36 on the Raspberry Pi Zero 2 W — NEW ACTION: Maintainers to diagnose and fix issue 5. qemu — VMs hang when trying to access virtiofs mounts in the guest VM — POST ACTION: Maintainers to merge and build PR 22 6. selinux-policy — selinux-policy is preventing flatpak from updating / installing / removing flatpaks — NEW ACTION: Maintainers to update policy to permit necessary flatpak actions 7. xdg-desktop-portal-gnome — xdg-desktop-portal-gnome: wl_proxy_get_version(): xdg-desktop-portal-gnome killed by SIGSEGV — MODIFIED ACTION: QA to verify FEDORA-2022-f8681a48e6 Bug-by-bug detail = Accepted blockers - 1. anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2069899 — MODIFIED anaconda enablement of fingerprint auth overrides existing authselect configuration anaconda overwrites the authselect config when enabling fingerprint authentication. This disables nss-mdns (when configured), breaking things like printer discovery. FEDORA-2022-8538fa94da contains a candidate fix. 2. gnome-connections — https://bugzilla.redhat.com/show_bug.cgi?id=2068015 — NEW gnome-connections: _mid_memalign(): gnome-connections killed by SIGSEGV Connecting to an RDP server (including localhost) causes Connections to crash immediately. Filed upstream as https://gitlab.gnome.org/GNOME/connections/-/issues/95 3. mutter — https://bugzilla.redhat.com/show_bug.cgi?id=2062660 — MODIFIED The input string via Input Method isn't renderred properly at the search box on Activities Pre-edit strings are not rendered in some cases, only showing the first keypress. Update FEDORA-2022-566779da43 contains a candidate fix. 4. mutter — https://bugzilla.redhat.com/show_bug.cgi?id=2063156 — NEW Workstation Live is frozen in a VM with QXL video driver (Virtio works OK) VMs that initially use the QXL driver appears frozen. Using virtio (including to switching to QXL after?) avoids this. KDE Lives do not display (heh) this behavior, not does using `nomodeset`. Filed upstream as https://gitlab.gnome.org/GNOME/mutter/-/issues/2201 5. plasma-discover — https://bugzilla.redhat.com/show_bug.cgi?id=2057563 — NEW The About button sends Discover into loop and the application stops responding. Clicking the About button causes a loop which renders Discover unresponsive (except when the window is maximized). Confirmed upstream as https://bugs.kde.org/show_bug.cgi?id=448784 6. xorg-x11-server — https://bugzilla.redhat.com/show_bug.cgi?id=2067151 — NEW Basic graphics mode broken for X11 (GNOME/KDE/netinst) on UEFI Basic graphics mode in F36 KDE is broken universally. For GNOME, it is broken, but only on X11+EFI. This does not appear to be hardware-specific. All combinations work as expected in F35. 7. xorg-x11-server — https://bugzilla.redhat.com/show_bug.cgi?id=2070130 — NEW Basic graphics mode broken for
Re: CVE 9.8 rated httpd update stuck in updates-testing for a week
On Thu, Mar 24, 2022 at 06:51:06PM -0700, Adam Williamson wrote: > Oh, I was just assuming it was. Yes, if it's not critpath, it can be > submitted by the maintainer or a proven packager once it has 1 karma. > (You don't actually need to edit the threshold, you can just use the > bodhi CLI). Although this is not necessarily automatically better. Fast security updates are important, obviously, but untested security updates? Not so much. It doesn't take very much _at all_ for people who rely on critical fixes for N-2 to confirm that the update addresses the problem without regressions. Surely there are more then _three_ people who care about this. -- Matthew Miller Fedora Project Leader ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2069285] perl-HTML-Parser-3.78 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2069285 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #4 from Fedora Update System --- FEDORA-2022-4a0449327e has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-4a0449327e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-4a0449327e 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=2069285 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Today's rawhide compose is taking a long time to fully sync
Today's rawhide compose is taking a long time to sync on the primary mirrors. It has been a mix of the update from the 28th and the one for today for at least a couple hours. That is much longer than normal. Did something fail part way through? ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: dist-git force push
Hi, On 4/1/22 18:09, Ondrej Mosnacek wrote: > On Fri, Apr 1, 2022 at 4:27 PM Robbie Harwood wrote: >> Kamil Dudka writes: >> >>> On Friday, April 1, 2022 12:51:36 PM CEST Michael J Gruber wrote: >>> - check whether the "new object name" is descendant of (contains) "old build object name" (rather than "old object name", which would forbid any force push) This would allow to rewrite a branch as long as the last commit hasn't been built yet (but allow only rewrites to commits since the last build). In particular, this would allow to avoid the many "commit missing patch", "actually commit the change", "duh" commits which happen after a successful `fedpkg build --scratch --srpm` followed by a half-(how do you say this nicely)ed commit. >>> >>> I thought the plan was to use pull requests with some CI checks to >>> avoid this. >> >> I hope not. Unless merging the PRs and kicking off the builds are done >> automatically, this'll just be as painful as the current centos >> workflow: >> >> - commit >> - push to fork >> - open PR >> - wait for checks >> - click "merge" button >> - wait for bots >> - kick off build >> >> compared with: >> >> - fedpkg commit -sc && fedpkg push && fedpkg build >> >> Context switches for maintainers are expensive! And while I don't >> personally think the "oops fixup" commits are a problem, a "PR with CI" >> workflow doesn't get rid of them by any means. > > Why not this then: > > - fedpkg commit -sc && fedpkg scratch-build --srpm && fedpkg push && > fedpkg build If people are going to use this, please make it one of: 1. If you have plenty of bandwidth + enough CPU + RAM: fedpkg mockbuild && fedpkg commit -sc && fedpkg push && fedpkg build 2. Or if you don't: fedpkg commit -sc && fedpkg scratch-build --arches=x86_64 --srpm && fedpkg push && fedpkg build Notice the --arches=x86_64, this is done because some of the other arches have limited builder capacity. Regards, Hans ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: cmake failure to build in rawhide?
Hi, On 4/1/22 18:09, Kamil Dudka wrote: > On Friday, April 1, 2022 5:45:38 PM CEST Hans de Goede wrote: >> Hi All, >> >> While fixing a hedgewars F36 bug, the f37/rawhide build of the >> fixed pkg is failing: >> >> In both F36 and F37 the invocation is: >> >> /usr/bin/cmake -S . -B redhat-linux-build >> -DCMAKE_C_FLAGS_RELEASE:STRING=-DNDEBUG >> -DCMAKE_CXX_FLAGS_RELEASE:STRING=-DNDEBUG >> -DCMAKE_Fortran_FLAGS_RELEASE:STRING=-DNDEBUG >> -DCMAKE_VERBOSE_MAKEFILE:BOOL=ON -DCMAKE_INSTALL_DO_STRIP:BOOL=OFF >> -DCMAKE_INSTALL_PREFIX:PATH=/usr -DINCLUDE_INSTALL_DIR:PATH=/usr/include >> -DLIB_INSTALL_DIR:PATH=/usr/lib64 -DSYSCONF_INSTALL_DIR:PATH=/etc >> -DSHARE_INSTALL_PREFIX:PATH=/usr/share -DLIB_SUFFIX=64 >> -DBUILD_SHARED_LIBS:BOOL=ON -DMINIMAL_FLAGS=1 -DNOVIDEOREC=1 >> -DBUILD_ENGINE_C=1 -DGHFLAGS=-dynamic >> '-DFONTS_DIRS=/usr/share/fonts;/usr/share/fonts/google-noto-vf;/usr/share/f >> onts/dejavu-sans-fonts;/usr/share/fonts/wqy-zenhei;' . > >> Followed by a bunch of output and then weirdness happens, F37 last cmake >> output line: > >> -- Build files have been written to: >> /builddir/build/BUILD/hedgewars-src-1.0.0 > >> vs F36 last output line: >> >> -- Build files have been written to: >> /builddir/build/BUILD/hedgewars-src-1.0.0/redhat-linux-build > >> F37 cmake seems to ignore the "-B redhat-linux-build" leading to this >> subsequent build error: > >> + /usr/bin/cmake --build redhat-linux-build -j6 --verbose >> Error: /builddir/build/BUILD/hedgewars-src-1.0.0/redhat-linux-build is not a >> directory > >> Any help with this would be much appreciated. >> >> Regards, >> >> Hans > > It is most likely this (not a) bug: Thanks. > https://bugzilla.redhat.com/show_bug.cgi?id=2057738 Ugh, what a mess. Anyways I've fixed this by dropping the extra "." at the end of the %cmake invocation. Regards, Hans ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: cmake failure to build in rawhide?
On Friday, April 1, 2022 5:45:38 PM CEST Hans de Goede wrote: > Hi All, > > While fixing a hedgewars F36 bug, the f37/rawhide build of the > fixed pkg is failing: > > In both F36 and F37 the invocation is: > > /usr/bin/cmake -S . -B redhat-linux-build > -DCMAKE_C_FLAGS_RELEASE:STRING=-DNDEBUG > -DCMAKE_CXX_FLAGS_RELEASE:STRING=-DNDEBUG > -DCMAKE_Fortran_FLAGS_RELEASE:STRING=-DNDEBUG > -DCMAKE_VERBOSE_MAKEFILE:BOOL=ON -DCMAKE_INSTALL_DO_STRIP:BOOL=OFF > -DCMAKE_INSTALL_PREFIX:PATH=/usr -DINCLUDE_INSTALL_DIR:PATH=/usr/include > -DLIB_INSTALL_DIR:PATH=/usr/lib64 -DSYSCONF_INSTALL_DIR:PATH=/etc > -DSHARE_INSTALL_PREFIX:PATH=/usr/share -DLIB_SUFFIX=64 > -DBUILD_SHARED_LIBS:BOOL=ON -DMINIMAL_FLAGS=1 -DNOVIDEOREC=1 > -DBUILD_ENGINE_C=1 -DGHFLAGS=-dynamic > '-DFONTS_DIRS=/usr/share/fonts;/usr/share/fonts/google-noto-vf;/usr/share/f > onts/dejavu-sans-fonts;/usr/share/fonts/wqy-zenhei;' . > Followed by a bunch of output and then weirdness happens, F37 last cmake > output line: > -- Build files have been written to: > /builddir/build/BUILD/hedgewars-src-1.0.0 > vs F36 last output line: > > -- Build files have been written to: > /builddir/build/BUILD/hedgewars-src-1.0.0/redhat-linux-build > F37 cmake seems to ignore the "-B redhat-linux-build" leading to this > subsequent build error: > + /usr/bin/cmake --build redhat-linux-build -j6 --verbose > Error: /builddir/build/BUILD/hedgewars-src-1.0.0/redhat-linux-build is not a > directory > Any help with this would be much appreciated. > > Regards, > > Hans It is most likely this (not a) bug: https://bugzilla.redhat.com/show_bug.cgi?id=2057738 ... also discussed on here on the mailing list some time ago: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/YM4WDDZL6PMSODITVYWMPWC4TC4447AY/ It seems to be triggered by the following intentional change in upstream cmake: https://gitlab.kitware.com/cmake/cmake/-/merge_requests/7001 Yet another consequence of the unnecessary change of %cmake macros in Fedora 33: https://fedoraproject.org/wiki/Changes/CMake_to_do_out-of-source_builds Kamil ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: dist-git force push
On Fri, Apr 1, 2022 at 4:27 PM Robbie Harwood wrote: > Kamil Dudka writes: > > > On Friday, April 1, 2022 12:51:36 PM CEST Michael J Gruber wrote: > > > >> - check whether the "new object name" is descendant of > >> (contains) "old build object name" (rather than "old object name", which > >> would forbid any force push) > >> This would allow to rewrite a branch as long as the last commit hasn't been > >> built yet (but allow only rewrites to commits since the last build). In > >> particular, this would allow to avoid the many "commit missing patch", > >> "actually commit the change", "duh" commits which happen after a successful > >> `fedpkg build --scratch --srpm` followed by a half-(how do you say this > >> nicely)ed commit. > > > > I thought the plan was to use pull requests with some CI checks to > > avoid this. > > I hope not. Unless merging the PRs and kicking off the builds are done > automatically, this'll just be as painful as the current centos > workflow: > > - commit > - push to fork > - open PR > - wait for checks > - click "merge" button > - wait for bots > - kick off build > > compared with: > > - fedpkg commit -sc && fedpkg push && fedpkg build > > Context switches for maintainers are expensive! And while I don't > personally think the "oops fixup" commits are a problem, a "PR with CI" > workflow doesn't get rid of them by any means. Why not this then: - fedpkg commit -sc && fedpkg scratch-build --srpm && fedpkg push && fedpkg build Yes, it'll still take longer, but you won't need to context switch unless the scratch build fails (which would make you do a fixup commit + another build anyway). This workflow allows you to amend the commit until you get a successful scratch build, after which it is unlikely that you would need to commit another fixup. -- Ondrej Mosnacek Software Engineer, Linux Security - SELinux kernel Red Hat, Inc. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2065018] perl-DateTime-TimeZone-2.52 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2065018 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-DateTime-TimeZone-2.52 |perl-DateTime-TimeZone-2.52 |-1.fc37 |-1.fc37 |perl-DateTime-TimeZone-2.52 |perl-DateTime-TimeZone-2.52 |-1.fc36 |-1.fc36 |perl-DateTime-TimeZone-2.52 |perl-DateTime-TimeZone-2.52 |-1.fc35 |-1.fc35 ||perl-DateTime-TimeZone-2.52 ||-1.fc34 --- Comment #9 from Fedora Update System --- FEDORA-2022-cd2b682eb8 has been pushed to the Fedora 34 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=2065018 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
cmake failure to build in rawhide?
Hi All, While fixing a hedgewars F36 bug, the f37/rawhide build of the fixed pkg is failing: In both F36 and F37 the invocation is: /usr/bin/cmake -S . -B redhat-linux-build -DCMAKE_C_FLAGS_RELEASE:STRING=-DNDEBUG -DCMAKE_CXX_FLAGS_RELEASE:STRING=-DNDEBUG -DCMAKE_Fortran_FLAGS_RELEASE:STRING=-DNDEBUG -DCMAKE_VERBOSE_MAKEFILE:BOOL=ON -DCMAKE_INSTALL_DO_STRIP:BOOL=OFF -DCMAKE_INSTALL_PREFIX:PATH=/usr -DINCLUDE_INSTALL_DIR:PATH=/usr/include -DLIB_INSTALL_DIR:PATH=/usr/lib64 -DSYSCONF_INSTALL_DIR:PATH=/etc -DSHARE_INSTALL_PREFIX:PATH=/usr/share -DLIB_SUFFIX=64 -DBUILD_SHARED_LIBS:BOOL=ON -DMINIMAL_FLAGS=1 -DNOVIDEOREC=1 -DBUILD_ENGINE_C=1 -DGHFLAGS=-dynamic '-DFONTS_DIRS=/usr/share/fonts;/usr/share/fonts/google-noto-vf;/usr/share/fonts/dejavu-sans-fonts;/usr/share/fonts/wqy-zenhei;' . Followed by a bunch of output and then weirdness happens, F37 last cmake output line: -- Build files have been written to: /builddir/build/BUILD/hedgewars-src-1.0.0 vs F36 last output line: -- Build files have been written to: /builddir/build/BUILD/hedgewars-src-1.0.0/redhat-linux-build F37 cmake seems to ignore the "-B redhat-linux-build" leading to this subsequent build error: + /usr/bin/cmake --build redhat-linux-build -j6 --verbose Error: /builddir/build/BUILD/hedgewars-src-1.0.0/redhat-linux-build is not a directory Any help with this would be much appreciated. Regards, Hans ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: dist-git force push
On Friday, April 1, 2022 4:26:36 PM CEST Robbie Harwood wrote: > Kamil Dudka writes: > > On Friday, April 1, 2022 12:51:36 PM CEST Michael J Gruber wrote: > >> - check whether the "new object name" is descendant of > >> (contains) "old build object name" (rather than "old object name", which > >> would forbid any force push) > >> This would allow to rewrite a branch as long as the last commit hasn't > >> been > >> built yet (but allow only rewrites to commits since the last build). In > >> particular, this would allow to avoid the many "commit missing patch", > >> "actually commit the change", "duh" commits which happen after a > >> successful > >> `fedpkg build --scratch --srpm` followed by a half-(how do you say this > >> nicely)ed commit. > > > > I thought the plan was to use pull requests with some CI checks to > > avoid this. > > I hope not. Unless merging the PRs and kicking off the builds are done > automatically, this'll just be as painful as the current centos > workflow: > > - commit > - push to fork > - open PR > - wait for checks > - click "merge" button > - wait for bots > - kick off build > > compared with: > > - fedpkg commit -sc && fedpkg push && fedpkg build > > Context switches for maintainers are expensive! And while I don't > personally think the "oops fixup" commits are a problem, a "PR with CI" > workflow doesn't get rid of them by any means. > > Be well, > --Robbie Yes, the fixup commits are not a big problem in Fedora git I guess. They are much more painful in upstream projects where downstream consumers like to use git-bisect and to cherry-pick fixes from upstream. In any case, allowing production branches to be rewritten in certain cases is hardly a solution in my view. Kamil ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: dist-git force push
Kamil Dudka writes: > On Friday, April 1, 2022 12:51:36 PM CEST Michael J Gruber wrote: > >> - check whether the "new object name" is descendant of >> (contains) "old build object name" (rather than "old object name", which >> would forbid any force push) >> This would allow to rewrite a branch as long as the last commit hasn't been >> built yet (but allow only rewrites to commits since the last build). In >> particular, this would allow to avoid the many "commit missing patch", >> "actually commit the change", "duh" commits which happen after a successful >> `fedpkg build --scratch --srpm` followed by a half-(how do you say this >> nicely)ed commit. > > I thought the plan was to use pull requests with some CI checks to > avoid this. I hope not. Unless merging the PRs and kicking off the builds are done automatically, this'll just be as painful as the current centos workflow: - commit - push to fork - open PR - wait for checks - click "merge" button - wait for bots - kick off build compared with: - fedpkg commit -sc && fedpkg push && fedpkg build Context switches for maintainers are expensive! And while I don't personally think the "oops fixup" commits are a problem, a "PR with CI" workflow doesn't get rid of them by any means. Be well, --Robbie 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 on the list, report it: https://pagure.io/fedora-infrastructure
CPE Weekly Update – Week of March 28th – April 1st
Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on libera.chat (https://libera.chat/). If you wish to read this in form of a blog post, check the post on Fedora community blog: https://communityblog.fedoraproject.org/cpe-weekly-update-week-of-march-28th-april-1st/ # Highlights of the week ## Infrastructure & Release Engineering Goal of this Initiative --- Purpose of this team is to take care of day to day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work. It’s responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.). The ARC (which is a subset of the team) investigates possible initiatives that CPE might take on. Link to planning board: https://zlopez.fedorapeople.org/I Update -- ### Fedora Infra * Got ELN resigned with f37/rawhide key and SOPs updated to do that at branching * Work on Infra SOPs ongoing * Adjusted vhost_reboot playbook to handle OCP4 master node vm’s correctly. * OCP4 clusters all upgraded to latest version. ### CentOS Infra including CentOS CI * koji/cbs builders reconfigured to use Proxy ( https://pagure.io/centos-infra/issue/645) to reach gitlab.com * Extras repository for CentOS Stream 8 now live ( https://lists.centos.org/pipermail/centos-devel/2022-March/120292.html) * Finishing ansible 2.9 => 2.12 (https://pagure.io/centos-infra/issue/496) conversion (role and collections) * Collab with Niels for Duffy ansible role (Pedro and Fabian) * Business as usual ### Release Engineering * Fedora 36 Beta released * Fedora 36 FTI packages retired * Work on SCM request automation is near finish - PR ( https://pagure.io/fedora-infra/toddlers/pull-request/93) ## CentOS Stream Goal of this Initiative --- This initiative is working on CentOS Stream/Emerging RHEL to make this new distribution a reality. The goal of this initiative is to prepare the ecosystem for the new CentOS Stream. Updates --- * First set of changes for CVE checker posted to gitlab. * ELN composes failing, troubleshooting the cause and updating our teams support docs (watcher duty) * Stream 9 presentations being worked on for Summit * Team planning for the goals and deliverables for the coming months (q2) scheduled for Tue ## CentOS Duffy CI Goal of this Initiative --- Duffy is a system within CentOS CI Infra which allows tenants to provision and access bare metal resources of multiple architectures for the purposes of CI testing. We need to add the ability to checkout VMs in CentOS CI in Duffy. We have OpenNebula hypervisor available, and have started developing playbooks which can be used to create VMs using the OpenNebula API, but due to the current state of how Duffy is deployed, we are blocked with new dev work to add the VM checkout functionality. Updates --- * Duffy 3.0.0a3 with even fewer missing dependencies! * Handover conversations * Testing & Documentation * Deployment playbooks and testing thereof * Script to migrate existing tenants ## Image builder for Fedora IoT Goal of this Initiative --- Integration of Image builder as a service with Fedora infra to allow Fedora IoT migrate their pipeline to Fedora infra. Updates --- * Full stack deployed in staging across kojihub and all builders * Testing complete * Ansible changes made and ready for whenever it needs to be deployed to prod * Both image builder and fedora IoT teams have tested and seem happy * Working on some form of documentation + handover to infra this week ## Bodhi Goal of this Initiative --- This initiative is to separate Bodhi into multiple sub packages, fix integration and unit tests in CI, fix dependency management and automate part of the release process. Read ARC team findings in detail at: https://fedora-arc.readthedocs.io/en/latest/bodhi/index.html Updates --- * Fedpkg compatibility for Bodhi >= 6.0 * Updated links to the documentation to GitHub pages * Dependency management (finishing touches) * Exclude `composes` property when serializing the Release object * Next major release draws near (~ 2 weeks?) ## EPEL Goal of this initiative --- Extra Packages for Enterprise Linux (or EPEL) is a Fedora Special Interest Group that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS and Scientific Linux (SL), Oracle Linux (OL). EPEL packages are usually based on their Fedora counterparts and will never conflict with or replace packages in the base Enterprise Linux distributions. EPEL uses much of the same infrastructure as Fedora, including buildsystem, bugzilla instance, updates manager,
F37 Change: Signed RPM Contents (System-Wide Change proposal)
https://fedoraproject.org/wiki/Changes/Signed_RPM_Contents == Summary == We want to add signatures to individual files that are part of shipped RPMs. These signatures will use the Linux IMA (Integrity Measurement Architecture) scheme, which means they can be used to enforce runtime policies to ensure execution of only trusted files. == Owner == * Name: [[User:Pbrobinson| Peter Robinson]] * Email: pbrobin...@gmail.com * Name: [[User:Puiterwijk| Patrick Uiterwijk]] * Email: puiterw...@redhat.com == Detailed Description == During signing builds, the files in it will be signed with IMA signatures. These signatures will be made with a key that's kept by the Fedora Infrastructure team, and installed on the sign vaults. These signature can then be used with the Linux Integrity Measurement Architecture (IMA) kernel subsystem to verify files on execution based on a policy. The IMA subsystem is described on [https://sourceforge.net/p/linux-ima/wiki/Home/ the project page]. IMA allows users to extend the trust of their system to the OS and processes. It allows the users, if they so wish, to set polices to ensure their machine and their resources are used the way they intended it to be not about restricting the use for the average Fedora user. Like all security pieces IMA doesn't solve the whole security problem with a single option, it's not intended to, but that does not mean it doesn't provide additional value and tools for Fedora users to protect their systems. To quote a section of [https://lwn.net/Articles/753276/ an LWN article]: The goals of the integrity subsystem are to detect files that have been altered, either accidentally or maliciously, by comparing a measurement of the current file contents with that of a stored "good" value; it can then enforce various file integrity policies (e.g. no access or no execution). IMA is three separate pieces: measurement, which calculates a hash of file contents; appraisal, which verifies file signatures made using the measured hashes; and audit, which records hashes and other information in the audit logs. There is also the extended verification module (EVM), which targets the measurement and protection of the file metadata, though that is not included in what she would be presenting. It is important to note that IMA does not protect against attacks on objects in memory, it can only be used to thwart attacks that change files. The intention here is not to ship a default policies for users but rather have sample policies that users can modify and use themselves. The Fedora IoT Edition intends to have sample policies and documentation for a number of IoT and Edge use cases. This means that they can configure a policy based on which the kernel will determine whether to verify (or measure) files before opening them. You could for example make a policy that appraises (verifies) all files that are executed by root: `appraise uid=1000 appraise_type=imasig`. Note explicitly that we do not intend to install a default policy as part of this change, and users will need to deploy their own policy before anything is measured or appraised. This means that after this is done, users will have the option to enable a policy and have that be enforced, but there will be nothing automatic. We will, however, document various example policies people can adapt to their needs. By default, the signatures will not be deployed to the file system. That will only be done once rpm-plugin-ima is installed. After that, RPM will put the signatures on the "security.ima" extended attribute on the files. == Feedback == === RPM Size === One of the main concerns that have been voiced is the RPM size, both on disk (mirrors) and on an installed system. For this comparison, I have cached all the RPMs installed in a Fedora Rawhide 20210118.n.1 default Server install (server netinstall disk, and then no changes to the group selection). After creating two copies of that data, one with just resigned (to exclude rpm size difference resulting from different key lengths), and one resigned with IMA file signatures inserted, I then installed two blank VMs by using the standard virt-manager settings, changing only the name and the system type to "EFI". This is using a prime256v1 file signing key. This is the same key format supported by the Fedora signing system. Binary RPMs on disk Resigned: 462524 (452M) Resigned+IMA: 467812 (457M) This comes down to a 1.1% increase on size of the binary RPMs. Installed size On installation of two different VMs, one with the resigned RPMs, and one with the resigned+ima RPMs, the `/usr` directory size does not change at all (both are exactly 1417064 bytes). The size of the rpmdb increases from 22952 to 28416 bytes, a 20% increase. This is on an install size of 1.7GB in total, so this 5MB increase is a 0.3% size increase on the final installed system. Note that both of those VMs did not have rpm-plugins-ima installed, which means the
F37 Change: Signed RPM Contents (System-Wide Change proposal)
https://fedoraproject.org/wiki/Changes/Signed_RPM_Contents == Summary == We want to add signatures to individual files that are part of shipped RPMs. These signatures will use the Linux IMA (Integrity Measurement Architecture) scheme, which means they can be used to enforce runtime policies to ensure execution of only trusted files. == Owner == * Name: [[User:Pbrobinson| Peter Robinson]] * Email: pbrobin...@gmail.com * Name: [[User:Puiterwijk| Patrick Uiterwijk]] * Email: puiterw...@redhat.com == Detailed Description == During signing builds, the files in it will be signed with IMA signatures. These signatures will be made with a key that's kept by the Fedora Infrastructure team, and installed on the sign vaults. These signature can then be used with the Linux Integrity Measurement Architecture (IMA) kernel subsystem to verify files on execution based on a policy. The IMA subsystem is described on [https://sourceforge.net/p/linux-ima/wiki/Home/ the project page]. IMA allows users to extend the trust of their system to the OS and processes. It allows the users, if they so wish, to set polices to ensure their machine and their resources are used the way they intended it to be not about restricting the use for the average Fedora user. Like all security pieces IMA doesn't solve the whole security problem with a single option, it's not intended to, but that does not mean it doesn't provide additional value and tools for Fedora users to protect their systems. To quote a section of [https://lwn.net/Articles/753276/ an LWN article]: The goals of the integrity subsystem are to detect files that have been altered, either accidentally or maliciously, by comparing a measurement of the current file contents with that of a stored "good" value; it can then enforce various file integrity policies (e.g. no access or no execution). IMA is three separate pieces: measurement, which calculates a hash of file contents; appraisal, which verifies file signatures made using the measured hashes; and audit, which records hashes and other information in the audit logs. There is also the extended verification module (EVM), which targets the measurement and protection of the file metadata, though that is not included in what she would be presenting. It is important to note that IMA does not protect against attacks on objects in memory, it can only be used to thwart attacks that change files. The intention here is not to ship a default policies for users but rather have sample policies that users can modify and use themselves. The Fedora IoT Edition intends to have sample policies and documentation for a number of IoT and Edge use cases. This means that they can configure a policy based on which the kernel will determine whether to verify (or measure) files before opening them. You could for example make a policy that appraises (verifies) all files that are executed by root: `appraise uid=1000 appraise_type=imasig`. Note explicitly that we do not intend to install a default policy as part of this change, and users will need to deploy their own policy before anything is measured or appraised. This means that after this is done, users will have the option to enable a policy and have that be enforced, but there will be nothing automatic. We will, however, document various example policies people can adapt to their needs. By default, the signatures will not be deployed to the file system. That will only be done once rpm-plugin-ima is installed. After that, RPM will put the signatures on the "security.ima" extended attribute on the files. == Feedback == === RPM Size === One of the main concerns that have been voiced is the RPM size, both on disk (mirrors) and on an installed system. For this comparison, I have cached all the RPMs installed in a Fedora Rawhide 20210118.n.1 default Server install (server netinstall disk, and then no changes to the group selection). After creating two copies of that data, one with just resigned (to exclude rpm size difference resulting from different key lengths), and one resigned with IMA file signatures inserted, I then installed two blank VMs by using the standard virt-manager settings, changing only the name and the system type to "EFI". This is using a prime256v1 file signing key. This is the same key format supported by the Fedora signing system. Binary RPMs on disk Resigned: 462524 (452M) Resigned+IMA: 467812 (457M) This comes down to a 1.1% increase on size of the binary RPMs. Installed size On installation of two different VMs, one with the resigned RPMs, and one with the resigned+ima RPMs, the `/usr` directory size does not change at all (both are exactly 1417064 bytes). The size of the rpmdb increases from 22952 to 28416 bytes, a 20% increase. This is on an install size of 1.7GB in total, so this 5MB increase is a 0.3% size increase on the final installed system. Note that both of those VMs did not have rpm-plugins-ima installed, which means the
Re: F36 - Errors/Warnings with `dnf update`
On 3/31/22 14:10, Daniel Walsh wrote: On 3/31/22 02:35, Carmelo Sarta wrote: Hello there! I've never seen this error before `error: Plugin selinux: hook fsm_file_prepare failed` but I would try `dnf reinstall container-selinux` and maybe `dnf reinstall podman` There seems to be an error appening when people are installing container-selinux, that I have not pinned down. It does not happen on my system. There's a bug on this now as well: https://bugzilla.redhat.com/show_bug.cgi?id=2070942 Should I reassign to container-selinux? - Panu - ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2070684] perl-Chart-2.400.5 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2070684 --- Comment #4 from Fedora Update System --- FEDORA-2022-572049ecc9 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-572049ecc9 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2070684 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2070684] perl-Chart-2.400.5 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2070684 --- Comment #3 from Fedora Update System --- FEDORA-2022-dee64826ff has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-dee64826ff -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2070684 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Heads up: libspnav 1.0
It will probably be next week sometime but I plan to update Rawhide at least. The following packages are affected and will be rebuilt in a side-tag: blender calligra freecad Thanks, Richard ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2064753] perl-PDL-2.077 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2064753 Jitka Plesnikova changed: What|Removed |Added Status|ASSIGNED|CLOSED Fixed In Version||perl-PDL-2.77.0-1.fc37 Resolution|--- |RAWHIDE Last Closed||2022-04-01 12:29:39 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2064753 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2070684] perl-Chart-2.400.5 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2070684 --- Comment #2 from Fedora Update System --- FEDORA-2022-119b7b03f0 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-119b7b03f0 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2070684 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2070684] perl-Chart-2.400.5 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2070684 Petr Pisar changed: What|Removed |Added Fixed In Version||perl-Chart-2.400.5-1.fc37 Status|ASSIGNED|MODIFIED -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2070684 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Fedora 36 compose report: 20220401.n.0 changes
OLD: Fedora-36-20220330.n.0 NEW: Fedora-36-20220401.n.0 = SUMMARY = Added images:0 Dropped images: 1 Added packages: 4 Dropped packages:0 Upgraded packages: 164 Downgraded packages: 0 Size of added packages: 556.73 KiB Size of dropped packages:0 B Size of upgraded packages: 2.15 GiB Size of downgraded packages: 0 B Size change of upgraded packages: -17.24 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = = DROPPED IMAGES = Image: Xfce raw-xz aarch64 Path: Spins/aarch64/images/Fedora-Xfce-36-20220330.n.0.aarch64.raw.xz = ADDED PACKAGES = Package: ghc-double-conversion-2.0.2.0-3.fc36 Summary: Fast conversion between double precision floating point and text RPMs:ghc-double-conversion ghc-double-conversion-devel ghc-double-conversion-doc ghc-double-conversion-prof Size:466.29 KiB Package: perl-IO-Zlib-1:1.11-2.module_f36+13900+855fbc00 Summary: Perl IO:: style interface to Compress::Zlib RPMs:perl-IO-Zlib Size:18.83 KiB Package: perl-Net-Ping-2.74-3.module_f36+13900+855fbc00 Summary: Check a remote host for reachability RPMs:perl-Net-Ping Size:49.10 KiB Package: perl-Tie-RefHash-1.40-2.module_f36+13900+855fbc00 Summary: Use references as hash keys RPMs:perl-Tie-RefHash Size:22.51 KiB = DROPPED PACKAGES = = UPGRADED PACKAGES = Package: audit-3.0.8-1.fc36 Old package: audit-3.0.7-3.fc36 Summary: User space tools for kernel auditing RPMs: audispd-plugins audispd-plugins-zos audit audit-libs audit-libs-devel python3-audit Size: 3.21 MiB Size change: 20.52 KiB Changelog: * Tue Mar 29 2022 Steve Grubb 3.0.8-1 - New upstream bugfix release Package: coq-8.15.1-1.fc36 Old package: coq-8.15.0-1.fc36 Summary: Proof management system RPMs: coq coq-coqide coq-coqide-server coq-core coq-doc Size: 1012.07 MiB Size change: 1.27 MiB Changelog: * Fri Mar 25 2022 Jerry James - 8.15.1-1 - Version 8.15.1 Package: cri-o-1.22.3-1.module_f36+14125+04700bd8 Old package: cri-o-1.22.1-1.module_f36+13383+c7708e36 Summary: Open Container Initiative-based implementation of Kubernetes Container Runtime Interface RPMs: cri-o Size: 203.10 MiB Size change: -10.38 MiB Changelog: * Fri Dec 03 2021 Peter Hunt - 0:1.22.1-2 - fix bogus date * Fri Feb 25 2022 Peter Hunt - 0:1.22.2-1 - bump to v1.22.2 * Tue Mar 15 2022 Peter Hunt - 0:1.22.3-1 - bump to v1.22.3 Package: cri-tools-1.20.0-2.module_f36+14162+f8af9510 Old package: cri-tools-1.20.0-2.module_f36+13501+d604a069 Summary: CLI and validation tools for Container Runtime Interface RPMs: cri-tools Size: 68.75 MiB Size change: -3.82 MiB Package: disciplining-minipod-2.1.0-1.fc36 Old package: disciplining-minipod-1.2.0-2.fc36 Summary: Disciplining algorithm for Atomic Reference Time Card RPMs: liboscillator-disciplining liboscillator-disciplining-devel Size: 252.20 KiB Size change: -25.56 KiB Changelog: * Fri Mar 25 2022 Alexander Bulimov 1.3.0-1 - Update to v1.3.0 * Fri Mar 25 2022 Fedora Release Engineering 1.3.0-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild * Fri Mar 25 2022 Alexander Bulimov 2.1.0-1 - Update to v2.1.0 Package: doublecmd-1.0.4-1.fc36 Old package: doublecmd-1.0.3-2.fc36 Summary: Cross platform open source file manager with two panels RPMs: doublecmd-common doublecmd-gtk doublecmd-qt Size: 12.96 MiB Size change: 314.69 KiB Changelog: * Wed Feb 09 2022 Vasiliy N. Glazov - 1.0.4-1 - Update to 1.0.4 Package: fcitx5-5.0.15-3.fc36 Old package: fcitx5-5.0.15-1.fc36 Summary: Next generation of fcitx RPMs: fcitx5 fcitx5-autostart fcitx5-data fcitx5-devel Size: 11.09 MiB Size change: 4.45 KiB Changelog: * Sat Mar 26 2022 Qiyu Yan 5.0.15-3 - fix env for xim Package: fcitx5-mozc-2.17.2102.102.1-17.20220326git1e52f80.fc36 Old package: fcitx5-mozc-2.17.2102.102.1-15.20211205git0ad3cf5.fc36 Summary: A wrapper of mozc for fcitx5 RPMs: fcitx5-mozc Size: 56.93 MiB Size change: 78.21 KiB Changelog: * Sat Mar 12 2022 Rich Mattes 2.17.2102.102.1-16 - Rebuild for abseil-cpp 20211102.0 * Sat Mar 26 2022 Qiyu Yan 2.17.2102.102.1-17 - update to 1e52f80 Package: flocq-3.4.3-2.fc36 Old package: flocq-3.4.3-1.fc36 Summary: Formalization of floating point numbers for Coq RPMs: flocq flocq-source Size: 25.40 MiB Size change: 29.70 KiB Changelog: * Fri Mar 25 2022 Jerry James - 3.4.3-2 - Rebuild for coq 8.15.1 Package: flrig-1.4.5-1.fc36 Old package: flrig-1.4.4-2.fc36 Summary: Transceiver control program RPMs: flrig Size: 5.46 MiB Size change: 395.82 KiB Changelog: * Sat Mar 26 2022 Richard Shaw - 1.4.5-1 - Update to 1.4.5. Package: frama-c-24.0-6.fc36 Old package: frama
Orphaning rubygem-request_store
Hi everybody, I don't have any use for rubygem-request_store, therefore I have orphaned it. Vít OpenPGP_signature Description: OpenPGP digital 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: dist-git force push
On Friday, April 1, 2022 12:51:36 PM CEST Michael J Gruber wrote: > Hi there > > I know why we do not allow to force push to dist-git in the rpms namespace, You can easily do force pushes in your own fork. Rewriting the authoritative branches in the official repositories is problematic for too many reasons, regardless of builds. > but I am wondering whether we can implement this more in line with the > reason: > > dist-git has to be a permanent record for the "source" (spec etc.) against > which a package is built, but currently we deny pushing even when there is > no build against the rewritten commits. Instead, I suggest the following > behaviour for the update-hook of git-receive-pack: > > - check which commit contained in "old object name" is the most recent one > (topology order) which has been built (successfully) There is an inherent time-of-check/time-of-use race condition in the proposal. > - call it "old build object name" > - check whether the "new object name" is descendant of > (contains) "old build object name" (rather than "old object name", which > would forbid any force push) > This would allow to rewrite a branch as long as the last commit hasn't been > built yet (but allow only rewrites to commits since the last build). In > particular, this would allow to avoid the many "commit missing patch", > "actually commit the change", "duh" commits which happen after a successful > `fedpkg build --scratch --srpm` followed by a half-(how do you say this > nicely)ed commit. I thought the plan was to use pull requests with some CI checks to avoid this. Kamil ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
dist-git force push
Hi there I know why we do not allow to force push to dist-git in the rpms namespace, but I am wondering whether we can implement this more in line with the reason: dist-git has to be a permanent record for the "source" (spec etc.) against which a package is built, but currently we deny pushing even when there is no build against the rewritten commits. Instead, I suggest the following behaviour for the update-hook of git-receive-pack: - check which commit contained in "old object name" is the most recent one (topology order) which has been built (successfully) - call it "old build object name" - check whether the "new object name" is descendant of (contains) "old build object name" (rather than "old object name", which would forbid any force push) This would allow to rewrite a branch as long as the last commit hasn't been built yet (but allow only rewrites to commits since the last build). In particular, this would allow to avoid the many "commit missing patch", "actually commit the change", "duh" commits which happen after a successful `fedpkg build --scratch --srpm` followed by a half-(how do you say this nicely)ed commit. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Has anyone seen hno?
Has anyone seen or knows how to contact hno? hno maintains electrum and is unresponsive on bugs, PRs and direct e-mails. He seems to be unresponsive for other packages as well: https://bugzilla.redhat.com/buglist.cgi?bug_status=__open__=henrik%40henriknordstrom.net_to1=1=substring_id=12528739_format=advanced Bug as per policy: https://bugzilla.redhat.com/show_bug.cgi?id=2070893 -- Jonathan ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora-Cloud-34-20220401.0 compose check report
No missing expected images. Soft failed openQA tests: 1/8 (x86_64), 1/8 (aarch64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-Cloud-34-20220331.0): ID: 1205298 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/1205298 ID: 1205307 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/1205307 Passed openQA tests: 7/8 (x86_64), 7/8 (aarch64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: RFI/RFC: Fedora Linux graphical recovery environment
Am 31.03.22 um 23:38 schrieb Neal Gompa: Hey all, Earlier this week, the Fedora Workstation WG discussed a ticket brought to us asking for a GUI-based rescue/recovery environment[1]. While we all agreed in principle that such a thing would be a very good thing to have, we don't really know how to achieve such a thing. Additionally, we're not really sure what the scope of things should be provided in said recovery environment and what kind of things people would expect to be able to fix in there. So I come to y'all to ask about this and give us some feedback on the idea, how to do it, and what kinds of things you expect people to need a recovery environment for. My suggestion, as i needed it last week: Preinstall Qphotorec into a normal Fedora LiveDisk and put it in the autostart config. The "do you want to test Fedora or install it " requester could be removed, or extended for the third option "Recovery" But, if you walk this path, you can add a fourth option rightaway, as requests will come in soon: "Do AVScan of System". best regards, Marius ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2070684] perl-Chart-2.400.5 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2070684 --- Comment #1 from Petr Pisar --- A bug-fix release suitable for all Fedoras. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2070684 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Fedora-Cloud-35-20220401.0 compose check report
No missing expected images. Failed openQA tests: 1/8 (x86_64) New failures (same test not failed in Fedora-Cloud-35-20220331.0): ID: 1205282 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/1205282 Soft failed openQA tests: 1/8 (aarch64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-Cloud-35-20220331.0): ID: 1205291 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/1205291 Passed openQA tests: 7/8 (x86_64), 7/8 (aarch64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2070684] perl-Chart-2.400.5 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2070684 Petr Pisar changed: What|Removed |Added Doc Type|--- |If docs needed, set a value CC|ppi...@redhat.com | 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=2070684 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
