Fedora-Rawhide-20220422.n.0 compose check report
Missing expected images: Minimal raw-xz armhfp Compose PASSES proposed Rawhide gating check! All required tests passed Failed openQA tests: 12/231 (x86_64), 26/161 (aarch64) New failures (same test not failed in Fedora-Rawhide-20220421.n.0): ID: 1236236 Test: x86_64 Workstation-live-iso anaconda_help URL: https://openqa.fedoraproject.org/tests/1236236 ID: 1236250 Test: x86_64 Workstation-live-iso desktop_login URL: https://openqa.fedoraproject.org/tests/1236250 ID: 1236330 Test: aarch64 Server-dvd-iso realmd_join_sssd@uefi URL: https://openqa.fedoraproject.org/tests/1236330 ID: 1236332 Test: aarch64 Server-dvd-iso server_realmd_join_kickstart@uefi URL: https://openqa.fedoraproject.org/tests/1236332 ID: 1236335 Test: aarch64 Server-dvd-iso server_cockpit_default@uefi URL: https://openqa.fedoraproject.org/tests/1236335 ID: 1236420 Test: x86_64 Workstation-upgrade desktop_login URL: https://openqa.fedoraproject.org/tests/1236420 ID: 1236426 Test: aarch64 Workstation-upgrade upgrade_desktop_64bit@uefi URL: https://openqa.fedoraproject.org/tests/1236426 ID: 1236491 Test: x86_64 universal upgrade_server_domain_controller URL: https://openqa.fedoraproject.org/tests/1236491 ID: 1236515 Test: x86_64 universal upgrade_realmd_client URL: https://openqa.fedoraproject.org/tests/1236515 ID: 1236527 Test: aarch64 universal install_european_language@uefi URL: https://openqa.fedoraproject.org/tests/1236527 ID: 1236533 Test: aarch64 universal upgrade_server_domain_controller@uefi URL: https://openqa.fedoraproject.org/tests/1236533 ID: 1236542 Test: aarch64 universal install_package_set_minimal@uefi URL: https://openqa.fedoraproject.org/tests/1236542 ID: 1236543 Test: aarch64 universal upgrade_realmd_client@uefi URL: https://openqa.fedoraproject.org/tests/1236543 ID: 1236545 Test: aarch64 universal upgrade_2_desktop_64bit@uefi URL: https://openqa.fedoraproject.org/tests/1236545 ID: 1236550 Test: aarch64 universal upgrade_desktop_encrypted_64bit@uefi URL: https://openqa.fedoraproject.org/tests/1236550 ID: 1236554 Test: aarch64 universal install_blivet_xfs@uefi URL: https://openqa.fedoraproject.org/tests/1236554 ID: 1236556 Test: aarch64 universal upgrade_2_server_domain_controller@uefi URL: https://openqa.fedoraproject.org/tests/1236556 ID: 1236557 Test: aarch64 universal install_multi_empty@uefi URL: https://openqa.fedoraproject.org/tests/1236557 ID: 1236569 Test: aarch64 universal upgrade_2_realmd_client@uefi URL: https://openqa.fedoraproject.org/tests/1236569 ID: 1236571 Test: aarch64 Workstation-raw_xz-raw.xz install_arm_image_deployment_upload@uefi URL: https://openqa.fedoraproject.org/tests/1236571 ID: 1236591 Test: aarch64 Server-dvd-iso install_repository_hd_variation@uefi URL: https://openqa.fedoraproject.org/tests/1236591 ID: 1236593 Test: aarch64 universal support_server@uefi URL: https://openqa.fedoraproject.org/tests/1236593 ID: 1236594 Test: aarch64 universal install_pxeboot@uefi URL: https://openqa.fedoraproject.org/tests/1236594 ID: 1236595 Test: aarch64 universal install_kickstart_nfs@uefi URL: https://openqa.fedoraproject.org/tests/1236595 Old failures (same test failed in Fedora-Rawhide-20220421.n.0): ID: 1236221 Test: x86_64 Server-dvd-iso server_cockpit_basic URL: https://openqa.fedoraproject.org/tests/1236221 ID: 1236242 Test: x86_64 Workstation-live-iso gnome_text_editor URL: https://openqa.fedoraproject.org/tests/1236242 ID: 1236277 Test: x86_64 KDE-live-iso apps_startstop URL: https://openqa.fedoraproject.org/tests/1236277 ID: 1236280 Test: x86_64 KDE-live-iso desktop_login URL: https://openqa.fedoraproject.org/tests/1236280 ID: 1236323 Test: aarch64 Server-dvd-iso install_btrfs_preserve_home@uefi URL: https://openqa.fedoraproject.org/tests/1236323 ID: 1236349 Test: aarch64 Server-dvd-iso install_vncconnect_client@uefi URL: https://openqa.fedoraproject.org/tests/1236349 ID: 1236360 Test: aarch64 Server-dvd-iso install_vncconnect_server@uefi URL: https://openqa.fedoraproject.org/tests/1236360 ID: 1236416 Test: x86_64 Workstation-upgrade gnome_text_editor URL: https://openqa.fedoraproject.org/tests/1236416 ID: 1236421 Test: x86_64 Workstation-upgrade desktop_fprint URL: https://openqa.fedoraproject.org/tests/1236421 ID: 1236570 Test: x86_64 universal install_serial_console URL: https://openqa.fedoraproject.org/tests/1236570 ID: 1236592 Test: aarch64 universal install_serial_console@uefi URL: https://openqa.fedoraproject.org/tests/1236592 ID: 1236596 Test: aarch64 universal install_iscsi@uefi URL: https://openqa.fedoraproject.org/tests/1236596 ID: 1236625 Test: aarch64 Server-dvd-iso install_btrfs_preserve_home_uefi@uefi URL: https://openqa.fedoraproject.org/tests/1236625 ID: 1236627 Test: aarch64 universal install_rescue_encrypted@uefi URL: https://openqa.fedoraproject.org/tests/1236627 Soft failed openQA tests: 11/231 (x86_64), 1/161 (aarch64
Modello update in rawhide
In one week modello package will be updated in rawhide (Fedora 37) from version 1.11 to version 2.0.0. Bug: https://bugzilla.redhat.com/show_bug.cgi?id=2053953 PR: https://src.fedoraproject.org/rpms/modello/pull-request/4 The new major version introduces API break and packages may need to be ported to work with the new version. Packages that build-require modello and are possibly affected by this update: antlr-maven-plugin maven maven-archetype maven-assembly-plugin maven-doxia maven-doxia-sitetools maven-file-management maven-invoker-plugin maven-plugin-tools maven-remote-resources-plugin maven-scm maven2 plexus-sec-dispatcher xmvn -- Mikolaj Izdebski ___ 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
Heads-up: python-opentelemetry 1.11.1 coming to Rawhide in one week
In one week (2022-04-29), or slightly later, I will merge and build the linked PR[1] to update python-opentelemetry from 1.10.0 to 1.11.1 in Rawhide. According to the upstream release notes [2][3], there are potential breaking changes. I will rebuild python-xds-protos in a side tag with python-opentelemetry, since—due to weird design decisions in grpc, to which it is related—it needs to be rebuilt when the proto files in python-opentelemetry are updated. Nothing should need to change in grpc, but I will check to make sure that is true. I do not expect any other packages in the distribution to be affected. – Ben [1] https://src.fedoraproject.org/rpms/python-opentelemetry/pull-request/1 [2] https://github.com/open-telemetry/opentelemetry-python/releases/tag/v1.11.0 [3] https://github.com/open-telemetry/opentelemetry-python/releases/tag/v1.11.1 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Fedora Contributor Tee Shirt Giveaway
On Fri, Apr 22, 2022 at 3:45 AM Vipul Siddharth wrote: > > On Fri, Apr 22, 2022 at 12:49 PM Leigh Scott wrote: > > > > Why post something that has expired? > Hi leigh, When I shared the email, the giveaway was still active :) > given it was just for 24 hours, It had to expire after some time (This > is mentioned in the blog) > I definitely could have highlighted in the email as well! > Hope it was useful to some I tried it 15 hours after the email was posted, and it was already expired. -- Chris Murphy ___ 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
Action summary Accepted blockers - 1. selinux-policy — gnome-initial-setup hangs when I try to setup a google/microsoft online account — VERIFIED ACTION: none 2. container-selinux — selinux-policy is preventing flatpak from updating / installing / removing flatpaks — ON_QA ACTION: QA to verify upgrades work reliably with FEDORA-2022-c5bee6b70f 3. selinux-policy — After upgrade to F36 several packages fail to update due to selinux-related errors — ON_QA ACTION: QA to verify blocking behavior is fixed 4. plasma-desktop — pyanaconda.modules.common.errors.installation.StorageInstallationError: device is active — ON_QA ACTION: QA to verify live sessions behave as expected NEEDINFO: fzatl...@redhat.com Proposed blockers - NONE Bug-by-bug detail = Accepted blockers - 1. selinux-policy — https://bugzilla.redhat.com/show_bug.cgi?id=2071259 — VERIFIED gnome-initial-setup hangs when I try to setup a google/microsoft online account Setting up a Google or Microsoft account causes g-i-s to apparently hang, although tty switching works. This appears to be an SELinux policy issue. FEDORA-2022-76963fee71 contains a verified fix. 2. container-selinux — https://bugzilla.redhat.com/show_bug.cgi?id=2070764 — ON_QA selinux-policy is preventing flatpak from updating / installing / removing flatpaks SELinux prevents flatpak from accessing a variety of files/directories, including `/etc/passwd` and `/var/lib/flatpak/exports/share`. This, in turn, prevents flatpak from modifying flatpaks on the system. FEDORA-2022-c5bee6b70f has a potential fix, but it's unclear if it solves the problem in full. 3. selinux-policy — https://bugzilla.redhat.com/show_bug.cgi?id=2056303 — ON_QA After upgrade to F36 several packages fail to update due to selinux-related errors selinux-policy updates to address this are in F34, F35, and F36. It's unclear if there are still blocking behaviors associated with this bug. 4. plasma-desktop — https://bugzilla.redhat.com/show_bug.cgi?id=2073708 — ON_QA pyanaconda.modules.common.errors.installation.StorageInstallationError: device is active KDE Plasma attempted to auto-mount certain hard drives during the live session, preventing anaconda from using the disks in an installation. Adam made an update to fedora-kickstarts that disables this on live sessions. Proposed blockers - NONE -- 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
Fedora-36-20220422.0 compose check report
No missing expected images. Failed openQA tests: 6/229 (x86_64), 9/161 (aarch64) ID: 1235852 Test: x86_64 Workstation-live-iso gnome_text_editor URL: https://openqa.fedoraproject.org/tests/1235852 ID: 1235887 Test: x86_64 KDE-live-iso apps_startstop URL: https://openqa.fedoraproject.org/tests/1235887 ID: 1235970 Test: aarch64 Server-dvd-iso realmd_join_cockpit@uefi URL: https://openqa.fedoraproject.org/tests/1235970 ID: 1235986 Test: aarch64 Workstation-raw_xz-raw.xz gnome_text_editor@uefi URL: https://openqa.fedoraproject.org/tests/1235986 ID: 1235993 Test: aarch64 Workstation-raw_xz-raw.xz base_reboot_unmount@uefi URL: https://openqa.fedoraproject.org/tests/1235993 ID: 1236019 Test: x86_64 Workstation-upgrade apps_startstop URL: https://openqa.fedoraproject.org/tests/1236019 ID: 1236022 Test: x86_64 Workstation-upgrade gnome_text_editor URL: https://openqa.fedoraproject.org/tests/1236022 ID: 1236041 Test: aarch64 Workstation-upgrade gnome_text_editor@uefi URL: https://openqa.fedoraproject.org/tests/1236041 ID: 1236145 Test: aarch64 universal install_arabic_language@uefi URL: https://openqa.fedoraproject.org/tests/1236145 ID: 1236146 Test: aarch64 universal install_cyrillic_language@uefi URL: https://openqa.fedoraproject.org/tests/1236146 ID: 1236163 Test: aarch64 universal install_multi_empty@uefi URL: https://openqa.fedoraproject.org/tests/1236163 ID: 1236309 Test: aarch64 Server-dvd-iso install_vnc_server@uefi URL: https://openqa.fedoraproject.org/tests/1236309 ID: 1236310 Test: aarch64 Server-dvd-iso install_vnc_client@uefi URL: https://openqa.fedoraproject.org/tests/1236310 ID: 1236598 Test: x86_64 universal install_arabic_language URL: https://openqa.fedoraproject.org/tests/1236598 ID: 1236599 Test: x86_64 universal install_cyrillic_language URL: https://openqa.fedoraproject.org/tests/1236599 Soft failed openQA tests: 16/229 (x86_64), 11/161 (aarch64) (Tests completed, but using a workaround for a known bug) ID: 1235855 Test: x86_64 Workstation-live-iso apps_startstop URL: https://openqa.fedoraproject.org/tests/1235855 ID: 1235859 Test: x86_64 Workstation-live-iso desktop_browser URL: https://openqa.fedoraproject.org/tests/1235859 ID: 1235870 Test: x86_64 Workstation-live-iso eog URL: https://openqa.fedoraproject.org/tests/1235870 ID: 1235880 Test: x86_64 KDE-live-iso desktop_browser URL: https://openqa.fedoraproject.org/tests/1235880 ID: 1235897 Test: x86_64 Silverblue-dvd_ostree-iso eog URL: https://openqa.fedoraproject.org/tests/1235897 ID: 1235902 Test: x86_64 Silverblue-dvd_ostree-iso desktop_browser URL: https://openqa.fedoraproject.org/tests/1235902 ID: 1235904 Test: x86_64 Silverblue-dvd_ostree-iso evince URL: https://openqa.fedoraproject.org/tests/1235904 ID: 1235905 Test: x86_64 Silverblue-dvd_ostree-iso gnome_text_editor URL: https://openqa.fedoraproject.org/tests/1235905 ID: 1235911 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/1235911 ID: 1235938 Test: aarch64 Server-dvd-iso server_realmd_join_kickstart@uefi URL: https://openqa.fedoraproject.org/tests/1235938 ID: 1236000 Test: aarch64 Workstation-raw_xz-raw.xz desktop_browser@uefi URL: https://openqa.fedoraproject.org/tests/1236000 ID: 1236001 Test: aarch64 Workstation-raw_xz-raw.xz eog@uefi URL: https://openqa.fedoraproject.org/tests/1236001 ID: 1236005 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/1236005 ID: 1236010 Test: x86_64 Workstation-upgrade upgrade_desktop_64bit URL: https://openqa.fedoraproject.org/tests/1236010 ID: 1236013 Test: x86_64 Workstation-upgrade desktop_browser URL: https://openqa.fedoraproject.org/tests/1236013 ID: 1236032 Test: aarch64 Workstation-upgrade upgrade_desktop_64bit@uefi URL: https://openqa.fedoraproject.org/tests/1236032 ID: 1236035 Test: aarch64 Workstation-upgrade desktop_browser@uefi URL: https://openqa.fedoraproject.org/tests/1236035 ID: 1236048 Test: aarch64 Workstation-upgrade eog@uefi URL: https://openqa.fedoraproject.org/tests/1236048 ID: 1236070 Test: x86_64 universal upgrade_desktop_encrypted_64bit URL: https://openqa.fedoraproject.org/tests/1236070 ID: 1236094 Test: x86_64 universal upgrade_kde_64bit URL: https://openqa.fedoraproject.org/tests/1236094 ID: 1236095 Test: x86_64 universal upgrade_server_64bit URL: https://openqa.fedoraproject.org/tests/1236095 ID: 1236097 Test: x86_64 universal upgrade_server_domain_controller URL: https://openqa.fedoraproject.org/tests/1236097 ID: 1236121 Test: x86_64 universal upgrade_realmd_client URL: https://openqa.fedoraproject.org/tests/1236121 ID: 1236138 Test: aarch64 universal upgrade_server_64bit@uefi URL: https://openqa.fedoraproject.org/tests/1236138 ID: 1236139 Test: aarch64 universal upgrade_server_domain_controller@uefi URL: https://openqa.fedoraproject.org/tests/1236139 ID: 123
Fedora rawhide compose report: 20220422.n.0 changes
OLD: Fedora-Rawhide-20220421.n.0 NEW: Fedora-Rawhide-20220422.n.0 = SUMMARY = Added images:0 Dropped images: 0 Added packages: 5 Dropped packages:0 Upgraded packages: 212 Downgraded packages: 2 Size of added packages: 2.99 MiB Size of dropped packages:0 B Size of upgraded packages: 5.15 GiB Size of downgraded packages: 262.76 KiB Size change of upgraded packages: -242.72 MiB Size change of downgraded packages: 163 B = ADDED IMAGES = = DROPPED IMAGES = = ADDED PACKAGES = Package: jigdo-0.8.1-1.fc37 Summary: Ease distribution of large files over the Internet RPMs:jigdo Size:897.32 KiB Package: perl-CGI-4.54-1.module_f37+14329+716cdd58 Summary: Handle Common Gateway Interface requests and responses RPMs:perl-CGI Size:198.33 KiB Package: perl-DBD-Pg-3.15.1-1.module_f37+14321+79e98709 Summary: A PostgreSQL interface for Perl RPMs:perl-DBD-Pg Size:881.81 KiB Package: perl-Date-Manip-6.86-2.module_f37+14333+eaebe199 Summary: Date manipulation routines RPMs:perl-Date-Manip Size:1.02 MiB Package: rust-findshlibs-0.10.2-1.fc37 Summary: Find the set of shared libraries loaded in the current process with a cross platform API RPMs:rust-findshlibs+default-devel rust-findshlibs-devel Size:35.65 KiB = DROPPED PACKAGES = = UPGRADED PACKAGES = Package: NetworkManager-sstp-1:1.3.0-1.fc37 Old package: NetworkManager-sstp-1:1.2.7-0.20220407git182a55b9.fc37 Summary: NetworkManager VPN plugin for SSTP RPMs: NetworkManager-sstp NetworkManager-sstp-gnome Size: 923.78 KiB Size change: 41.83 KiB Changelog: * Thu Apr 21 2022 Marcin Zajaczkowski - 1:1.3.0-1 - Update to 1.3.0 final (formerly 1.2.7) Package: WALinuxAgent-2.7.0.6-1.fc37 Old package: WALinuxAgent-2.5.0.2-2.fc36 Summary: The Microsoft Azure Linux Agent RPMs: WALinuxAgent WALinuxAgent-udev Size: 493.21 KiB Size change: 27.58 KiB Changelog: * Fri Apr 22 2022 Vitaly Kuznetsov - 2.7.0.6-1 - Update to 2.7.0.6 (#2040980) Package: adwaita-qt-1.4.1-4.fc37 Old package: adwaita-qt-1.4.1-3.fc37 Summary: Adwaita theme for Qt-based applications RPMs: adwaita-qt5 adwaita-qt6 libadwaita-qt5 libadwaita-qt5-devel libadwaita-qt6 libadwaita-qt6-devel Size: 2.69 MiB Size change: 11.84 KiB Changelog: * Thu Apr 21 2022 Jan Grulich - 1.4.1-4 - Rebuild (Qt6) Package: annobin-10.67-1.fc37 Old package: annobin-10.66-1.fc37 Summary: Annotate and examine compiled binary files RPMs: annobin-annocheck annobin-docs annobin-plugin-clang annobin-plugin-gcc annobin-plugin-llvm Size: 4.69 MiB Size change: 1.47 KiB Changelog: * Fri Apr 22 2022 Nick Clifton - 10.67-1 - Annocheck: Do not complain about missing -mbranch-protection option in AArch64 binaries if compiled by golang. Package: ansible-collection-netbox-netbox-3.7.0-1.fc37 Old package: ansible-collection-netbox-netbox-3.6.0-1.fc37 Summary: Netbox modules for Ansible RPMs: ansible-collection-netbox-netbox Size: 622.92 KiB Size change: 2.04 KiB Changelog: * Tue Apr 19 2022 Maxwell G - 3.7.0-1 - Update to 3.7.0. Fixes rhbz#2076449. Package: ansible-pcp-2.2.5-1.fc37 Old package: ansible-pcp-2.2.4-3.fc37 Summary: Ansible Metric collection for Performance Co-Pilot RPMs: ansible-pcp Size: 115.60 KiB Size change: 4.02 KiB Changelog: * Thu Apr 21 2022 Nathan Scott 2.2.5-1 - Latest upstream release Package: ant-1.10.12-4.fc37 Old package: ant-1.10.12-3.fc36 Summary: Java build tool RPMs: ant ant-antlr ant-apache-bcel ant-apache-bsf ant-apache-oro ant-apache-regexp ant-apache-resolver ant-apache-xalan2 ant-commons-logging ant-commons-net ant-imageio ant-javadoc ant-javamail ant-jdepend ant-jmf ant-jsch ant-junit ant-junit5 ant-lib ant-manual ant-swing ant-testutil ant-xz Size: 5.04 MiB Size change: 3.28 KiB Changelog: * Fri Apr 22 2022 Mikolaj Izdebski - 1.10.12-4 - Fix FTBFS with JUnit 5.8.x Package: apache-parent-26-1.fc37 Old package: apache-parent-23-8.fc36 Summary: Parent POM file for Apache projects RPMs: apache-parent Size: 15.97 KiB Size change: 519 B Changelog: * Thu Apr 21 2022 Mikolaj Izdebski - 26-1 - Update to upstream version 26 Package: at-spi2-core-2.44.1-1.fc37 Old package: at-spi2-core-2.44.0-1.fc37 Summary: Protocol definitions and daemon for D-Bus at-spi RPMs: at-spi2-core at-spi2-core-devel Size: 1.54 MiB Size change: 1.29 KiB Changelog: * Fri Apr 22 2022 David King - 2.44.1-1 - Update to 2.44.1 Package: avrdude-6.4-3.fc37 Old package: avrdude-6.4-2.fc37 Summary: Software for programming Atmel AVR Microcontroller RPMs: avrdude Size: 3.47 MiB Size change: 4.33 KiB Changelog: * Wed Apr 20 2022 Hans Ulrich Niedermann - 6.4-3 - Add README.fedora explaining
Re: Best way to enable -mbranch-protection for package
On 2022-04-22 11:01, Petr Pisar wrote:
> V Thu, Apr 21, 2022 at 11:12:41PM +0200, Marcin Zajączkowski napsal(a):
>> Upgrading NetworkManager-sstp to the latest version, I've noticed that
>> there is a failed test related to missing branch protection on AArch64
>> [1].
>
> Check annocheck version installed when building your package (root.log). There
> was a bug manifesting as -mbranch-protection=standard failure on AArch64 and
> fixed in 10.66:
>
> * Wed Apr 13 2022 Nick Clifton - 10.66-1
> - Annocheck: Do not complain about missing -mbranch-protection option in
> AArch64 binaries if compiled in LTO mode.
Thanks Petr! It might be that. When I increase the build verbosity I
clearly see that "-mbranch-protection=standard" is used [3] (it was
missing on my x86_64 for obvious reasons :) ).
The test itself was executed with:
> annocheck: Version 10.65.
Everything explained. Thanks.
[3] -
https://osci-jenkins-1.ci.fedoraproject.org/job/fedora-ci/job/rpminspect-pipeline/job/master/96013/testReport/(root)/tests/_annocheck/
Marcin
>
>> After reading that and [2], I know what it is all about, however, I
>> wonder what is the best way to apply it to my package?
>>
>> Should I check if the build is for AArch64 and for Fedora 33+ (35+?) and
>> just add "-mbranch-protection=standard"? Or there is some magic macro to
>> add that (and maybe some other useful security options), similar to
>> %{?_smp_mflags} (or maybe even included in %make_build on ARM64)?
>>
> The option is already presented in system-wide CFLAGS. Check any build.log.
> If you package respects the flags (check your build.log), you don't need to do
> anything. Otherwise, you should correct your package use all the options from
> CFLAGS enviroment variable or %{build_cflags} RPM macro.
>
> -- Petr
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Orphaning Jsoup
I'm going to orphan jsoup package. jsoup is a Java library for working with real-world HTML. It provides a very convenient API for extracting and manipulating data, using the best of DOM, CSS, and jquery-like methods. I am no longer interested in maintaining jsoup in Fedora. It has outstanding moderate CVE: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2021-37714 There is a new upstream version available. -- Mikolaj Izdebski ___ 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: [Fedocal] Reminder meeting : ELN SIG
#fedora-meeting: Fedora ELN SIG (2022-04-22) Meeting started by dcavalca at 16:02:41 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting/2022-04-22/eln.2022-04-22-16.02.log.html . Meeting summary --- * init process (dcavalca, 16:03:23) * Old Business (dcavalca, 16:05:31) * LINK: https://github.com/fedora-eln/eln/issues/87 also qualifies, but is likely workaroundable (t184256, 16:13:41) * LINK: https://github.com/rhinstaller/kickstart-tests (jkonecny[m], 16:23:03) * ACTION: Eighth_Doctor davdunc dcavalca meet with adamw to discuss openqa in the cloud to help with ELN testing capacity (dcavalca, 16:41:22) * ACTION: jkonecny[m] look into enabling kickstart tests for ELN (dcavalca, 16:42:01) * ACTION: dcavalca file an issue to get a stable boot.iso symlink for the latest compose (dcavalca, 16:46:02) * New Business (dcavalca, 16:49:46) * LINK: https://download.copr.fedorainfracloud.org/results/@meta/drgn/fedora-eln-ppc64le/04294758-python-drgn/builder-live.log.gz is one example fyi (dcavalca, 16:55:52) Meeting ended at 17:00:45 UTC. Action Items * Eighth_Doctor davdunc dcavalca meet with adamw to discuss openqa in the cloud to help with ELN testing capacity * jkonecny[m] look into enabling kickstart tests for ELN * dcavalca file an issue to get a stable boot.iso symlink for the latest compose Action Items, by person --- * adamw * Eighth_Doctor davdunc dcavalca meet with adamw to discuss openqa in the cloud to help with ELN testing capacity * davdunc * Eighth_Doctor davdunc dcavalca meet with adamw to discuss openqa in the cloud to help with ELN testing capacity * dcavalca * Eighth_Doctor davdunc dcavalca meet with adamw to discuss openqa in the cloud to help with ELN testing capacity * dcavalca file an issue to get a stable boot.iso symlink for the latest compose * Eighth_Doctor * Eighth_Doctor davdunc dcavalca meet with adamw to discuss openqa in the cloud to help with ELN testing capacity * jkonecny[m] * jkonecny[m] look into enabling kickstart tests for ELN * **UNASSIGNED** * (none) People Present (lines said) --- * dcavalca (66) * jkonecny[m] (26) * SSmoogen (16) * zodbot (14) * Eighth_Doctor (11) * t184256 (9) * praiskup (8) * michel (4) * davdunc[m (3) * asosedkin (2) * jforbes (1) * davdunc (1) * adamw (1) * sgallagh (0) Generated by `MeetBot`_ 0.4 .. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions ___ 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: grub2 BIOS booting iso and code
On 4/20/22 17:25, Thomas Schmitt wrote: > Hi, > Thanks Thomas for the reply. You've given us some good information to consider/pursue. Dusty ___ 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-20220422.n.0 compose check report
No missing expected images. Failed openQA tests: 9/161 (aarch64), 5/229 (x86_64) New failures (same test not failed in Fedora-36-20220421.n.0): ID: 1235160 Test: aarch64 Server-dvd-iso base_service_manipulation@uefi URL: https://openqa.fedoraproject.org/tests/1235160 ID: 1235163 Test: aarch64 Server-dvd-iso install_vncconnect_server@uefi URL: https://openqa.fedoraproject.org/tests/1235163 ID: 1235167 Test: aarch64 Server-dvd-iso realmd_join_cockpit@uefi URL: https://openqa.fedoraproject.org/tests/1235167 ID: 1235230 Test: aarch64 Workstation-upgrade base_update_cli@uefi URL: https://openqa.fedoraproject.org/tests/1235230 ID: 1235321 Test: x86_64 universal install_pxeboot@uefi URL: https://openqa.fedoraproject.org/tests/1235321 ID: 1235330 Test: aarch64 universal install_european_language@uefi URL: https://openqa.fedoraproject.org/tests/1235330 ID: 1235359 Test: aarch64 universal upgrade_2_server_domain_controller@uefi URL: https://openqa.fedoraproject.org/tests/1235359 Old failures (same test failed in Fedora-36-20220421.n.0): ID: 1235049 Test: x86_64 Workstation-live-iso gnome_text_editor URL: https://openqa.fedoraproject.org/tests/1235049 ID: 1235084 Test: x86_64 KDE-live-iso apps_startstop URL: https://openqa.fedoraproject.org/tests/1235084 ID: 1235183 Test: aarch64 Workstation-raw_xz-raw.xz gnome_text_editor@uefi URL: https://openqa.fedoraproject.org/tests/1235183 ID: 1235185 Test: aarch64 Workstation-raw_xz-raw.xz desktop_printing_builtin@uefi URL: https://openqa.fedoraproject.org/tests/1235185 ID: 1235216 Test: x86_64 Workstation-upgrade apps_startstop URL: https://openqa.fedoraproject.org/tests/1235216 ID: 1235219 Test: x86_64 Workstation-upgrade gnome_text_editor URL: https://openqa.fedoraproject.org/tests/1235219 ID: 1235238 Test: aarch64 Workstation-upgrade gnome_text_editor@uefi URL: https://openqa.fedoraproject.org/tests/1235238 Soft failed openQA tests: 16/229 (x86_64), 11/161 (aarch64) (Tests completed, but using a workaround for a known bug) New soft failures (same test not soft failed in Fedora-36-20220421.n.0): ID: 1235210 Test: x86_64 Workstation-upgrade desktop_browser URL: https://openqa.fedoraproject.org/tests/1235210 Old soft failures (same test soft failed in Fedora-36-20220421.n.0): ID: 1235052 Test: x86_64 Workstation-live-iso apps_startstop URL: https://openqa.fedoraproject.org/tests/1235052 ID: 1235056 Test: x86_64 Workstation-live-iso desktop_browser URL: https://openqa.fedoraproject.org/tests/1235056 ID: 1235067 Test: x86_64 Workstation-live-iso eog URL: https://openqa.fedoraproject.org/tests/1235067 ID: 1235077 Test: x86_64 KDE-live-iso desktop_browser URL: https://openqa.fedoraproject.org/tests/1235077 ID: 1235094 Test: x86_64 Silverblue-dvd_ostree-iso eog URL: https://openqa.fedoraproject.org/tests/1235094 ID: 1235099 Test: x86_64 Silverblue-dvd_ostree-iso desktop_browser URL: https://openqa.fedoraproject.org/tests/1235099 ID: 1235101 Test: x86_64 Silverblue-dvd_ostree-iso evince URL: https://openqa.fedoraproject.org/tests/1235101 ID: 1235102 Test: x86_64 Silverblue-dvd_ostree-iso gnome_text_editor URL: https://openqa.fedoraproject.org/tests/1235102 ID: 1235108 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/1235108 ID: 1235159 Test: aarch64 Server-dvd-iso server_cockpit_basic@uefi URL: https://openqa.fedoraproject.org/tests/1235159 ID: 1235197 Test: aarch64 Workstation-raw_xz-raw.xz desktop_browser@uefi URL: https://openqa.fedoraproject.org/tests/1235197 ID: 1235198 Test: aarch64 Workstation-raw_xz-raw.xz eog@uefi URL: https://openqa.fedoraproject.org/tests/1235198 ID: 1235202 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/1235202 ID: 1235207 Test: x86_64 Workstation-upgrade upgrade_desktop_64bit URL: https://openqa.fedoraproject.org/tests/1235207 ID: 1235229 Test: aarch64 Workstation-upgrade upgrade_desktop_64bit@uefi URL: https://openqa.fedoraproject.org/tests/1235229 ID: 1235232 Test: aarch64 Workstation-upgrade desktop_browser@uefi URL: https://openqa.fedoraproject.org/tests/1235232 ID: 1235245 Test: aarch64 Workstation-upgrade eog@uefi URL: https://openqa.fedoraproject.org/tests/1235245 ID: 1235267 Test: x86_64 universal upgrade_desktop_encrypted_64bit URL: https://openqa.fedoraproject.org/tests/1235267 ID: 1235291 Test: x86_64 universal upgrade_kde_64bit URL: https://openqa.fedoraproject.org/tests/1235291 ID: 1235292 Test: x86_64 universal upgrade_server_64bit URL: https://openqa.fedoraproject.org/tests/1235292 ID: 1235294 Test: x86_64 universal upgrade_server_domain_controller URL: https://openqa.fedoraproject.org/tests/1235294 ID: 1235318 Test: x86_64 universal upgrade_realmd_client URL: https://openqa.fedoraproject.org/tests/1235318 ID: 1235335 Test: aarch64 universal upgrade_server_64bit@uefi URL: https
Re: Allow non-packagers to push to dist-git forks without fedpkg
On Fri, Apr 22, 2022 at 9:54 AM Miro Hrončok wrote: > > Hello folks, > > what would it take to allow non-packagers to push to dist-git forks without > fedpkg? > > The instructions at > https://docs.fedoraproject.org/en-US/ci/pull-requests/#_you_are_not_a_packager > assume they run Fedora (or another distro with fedpkg), but this is extremely > unfriendly to contributors who run other distros. > > The alternative is external pull request which is awesome in theory but quite > tedious in practice. E.g. as a package maintainer, I cannot push my changes to > a proposed external pull request. > > If I understand correctly, SSH access is a security/legal/whatever no-go for > nonpackagers, but can we offer some kind of standard git mechanism to > authenticate? API tokens maybe? > > If not, can we at least extract the fedpkg bits that do this and release that > as a standalone easy-to-install software that we can offer or even package to > other distributions? > We should just turn on Pagure's ability to let you create API tokens that can do HTTPS auth for git push on src.fedoraproject.org. The janky setup we have now predates introducing support in Pagure itself. -- 真実はいつも一つ！/ 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
Re: Allow non-packagers to push to dist-git forks without fedpkg
> On Apr 22, 2022, at 6:44 AM, Miro Hrončok wrote: > > Hello folks, > > what would it take to allow non-packagers to push to dist-git forks without > fedpkg? > > The instructions at > https://docs.fedoraproject.org/en-US/ci/pull-requests/#_you_are_not_a_packager > assume they run Fedora (or another distro with fedpkg), but this is > extremely unfriendly to contributors who run other distros. > > The alternative is external pull request which is awesome in theory but quite > tedious in practice. E.g. as a package maintainer, I cannot push my changes > to a proposed external pull request. > > If I understand correctly, SSH access is a security/legal/whatever no-go for > nonpackagers, but can we offer some kind of standard git mechanism to > authenticate? API tokens maybe? > > If not, can we at least extract the fedpkg bits that do this and release that > as a standalone easy-to-install software that we can offer or even package to > other distributions? > As frequently as I find myself working in a different environment due to various constraints, having the fedpkg bits available in other environments — even homebrew — sounds like a win in my opinion. signature.asc Description: Message signed with OpenPGP ___ 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
Allow non-packagers to push to dist-git forks without fedpkg
Hello folks, what would it take to allow non-packagers to push to dist-git forks without fedpkg? The instructions at https://docs.fedoraproject.org/en-US/ci/pull-requests/#_you_are_not_a_packager assume they run Fedora (or another distro with fedpkg), but this is extremely unfriendly to contributors who run other distros. The alternative is external pull request which is awesome in theory but quite tedious in practice. E.g. as a package maintainer, I cannot push my changes to a proposed external pull request. If I understand correctly, SSH access is a security/legal/whatever no-go for nonpackagers, but can we offer some kind of standard git mechanism to authenticate? API tokens maybe? If not, can we at least extract the fedpkg bits that do this and release that as a standalone easy-to-install software that we can offer or even package to other distributions? Thanks, -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ 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 compose report: 20220422.n.0 changes
OLD: Fedora-36-20220421.n.0 NEW: Fedora-36-20220422.n.0 = SUMMARY = Added images:0 Dropped images: 0 Added packages: 0 Dropped packages:0 Upgraded packages: 4 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:0 B Size of upgraded packages: 107.85 MiB Size of downgraded packages: 0 B Size change of upgraded packages: 50.18 KiB Size change of downgraded packages: 0 B = ADDED IMAGES = = DROPPED IMAGES = = ADDED PACKAGES = = DROPPED PACKAGES = = UPGRADED PACKAGES = Package: gnome-software-42.0-4.fc36 Old package: gnome-software-42.0-2.fc36 Summary: A software center for GNOME RPMs: gnome-software gnome-software-devel gnome-software-rpm-ostree Size: 11.01 MiB Size change: 3.35 KiB Changelog: * Tue Apr 19 2022 Milan Crha - 42.0-3 - Resolves: #2074121 (Enabling "Fedora Flathub Selection" repo doesn't show included apps) * Wed Apr 20 2022 Milan Crha - 42.0-4 - Update patch for bug #2074121 Package: ibus-1.5.26-4.fc36 Old package: ibus-1.5.26-3.fc36 Summary: Intelligent Input Bus for Linux OS RPMs: ibus ibus-desktop-testing ibus-devel ibus-devel-docs ibus-gtk2 ibus-gtk3 ibus-gtk4 ibus-libs ibus-setup ibus-tests ibus-wayland Size: 61.29 MiB Size change: -2.88 KiB Changelog: * Wed Apr 20 2022 Takao Fujiwara - 1.5.26-4 - Resolves: #2076596 Disable XKB engines in Plasma Wayland Package: openssl-1:3.0.2-3.fc36 Old package: openssl-1:3.0.2-1.fc36 Summary: Utilities from the general purpose cryptography library with TLS implementation RPMs: openssl openssl-devel openssl-libs openssl-perl Size: 35.53 MiB Size change: 49.55 KiB Changelog: * Thu Apr 07 2022 Clemens Lang - 1:3.0.2-2 - Allow disabling SHA1 signature creation and verification. Set rh-allow-sha1-signatures = no to disable. Allow SHA1 in TLS in SECLEVEL 1 if rh-allow-sha1-signatures = yes. This will support SHA1 in TLS in the LEGACY crypto-policy. Resolves: rhbz#2070977, rhbz#2071615 Related: rhbz#2031742, rhbz#2062640 * Thu Apr 07 2022 Clemens Lang - 1:3.0.2-2 - Silence a few rpmlint false positives. * Thu Apr 21 2022 Dmitry Belyavskiy - 1:3.0.2-3 - Fixing Turkish locale issues Resolves: rhbz#2071343 Package: xorg-x11-drv-vesa-2.5.0-3.fc36 Old package: xorg-x11-drv-vesa-2.5.0-2.fc36 Summary: Xorg X11 vesa video driver RPMs: xorg-x11-drv-vesa Size: 22.46 KiB Size change: 175 B Changelog: * Tue Apr 19 2022 Jocelyn Falempe - 2.5.0-3 - Fix vesa crash with simpledrm driver (#2074789) = 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
CPE Weekly Update – Week of April 18th – 22nd
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/?p=10955 # 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&R-20-04-2022.pdf Update -- ### Fedora Infra * A fasjson not issuing certs issue fixed. * New Mote dev app deployed to stg ocp4: https://mote-mote.apps.ocp.stg.fedoraproject.org/ * Normal freeze processing ### CentOS Infra including CentOS CI * Duffy deployment tests (for CI) * BAU (new tags, mirrors requests) ### Release Engineering * Finally fixed rawhide compose breakage (look for a blog from Kevin about it, it was a fun one!) * Waiting for RC requests * Fedora 36 and 37 openh264 binaries are uploaded to Cisco CDN ## 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 --- * T-functional suite tests are in progress and the team are reviewing before merging https://github.com/AdamSaleh/sig-core-t_functional/actions/runs/2195767298 * New kernel being built and general updates to C7 & c8s are being worked on * Integration tests for (internal only) B.A.L.D service being developed, which is in a proof of concept phase. Fragile front end prototype stood up. Not ready for visitors. * New compose of c9s has landed in mirrors ## 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 --- * Deployment preparation and tests * Test Ansible role and extend/fix * Implement and test (de)provisioning playbooks with bare metal nodes * Work on support for single node (de)provisioning playbooks ## Package Automation (Packit Service) Goal of this initiative --- Automate RPM packaging of infra apps/packages Updates --- * Board created here: https://github.com/orgs/fedora-infra/projects/12 * First tasks are to create lists of all viable applications, we’ll then cross-reference this with our critical-path list for our starting points ## Flask-oidc: oauth2client replacement Goal of this initiative --- Flask-oidc is a library used across the Fedora infrastructure and is the client for ipsilon for its authentication. flask-oidc uses oauth2client. This library is now deprecated and no longer maintained. This will need to be replaced with authlib. Updates: * Working on getting flask-oidc dependency update `python-authlib` 1.0.1 [0] into rawhide [1] and f36 [2]. * Refactoring [3] Flask-OIDC after finding a deprecation in itsdangerous * Looking at testing in staging later this week [0] github.com/fedora-infra/flask-oidc/issues/3 [1] bodhi.fedoraproject.org/updates/FEDORA-2022-5aa0b83b14 [2] bodhi.fedoraproject.org/updates/FEDORA-2022-bf96df773c [3] github.com/fedora-infra/flask-oidc/issues/4 ## 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, mirror manager and more. Updates --- * EPEL9 up to 2371 source packages (increase of 93 from last week) Now has more source packages than CentOS Stream 9 * EPEL Steering Committee approved an incompati
Re: Fedora Contributor Tee Shirt Giveaway
On Fri, 2022-04-22 at 13:04 +0530, Vipul Siddharth wrote: > On Fri, Apr 22, 2022 at 12:49 PM Leigh Scott > wrote: > > > > Why post something that has expired? > Hi leigh, When I shared the email, the giveaway was still active :) > given it was just for 24 hours, It had to expire after some time > (This > is mentioned in the blog) > I definitely could have highlighted in the email as well! > Hope it was useful to some I managed to order mine yesterday 😀️ > > ___ > > 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 > > > > -- > Vipul Siddharth > He/His/Him > Fedora | CentOS CI Infrastructure Team > ___ > 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 -- Sérgio M. B. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Fedora Contributor Tee Shirt Giveaway
On Fri, Apr 22, 2022, 16:49 Sayak Sarkar wrote: > Cool Stuff store says that the promo code has already expired! :( > Yep it was 24 hrs only. > On Fri, 22 Apr 2022 at 08:49, Chris Murphy > wrote: > >> I'm getting: There are currently no products linked to this invitation >> code... >> >> --- >> Chris Murphy >> ___ >> test mailing list -- t...@lists.fedoraproject.org >> To unsubscribe send an email to test-le...@lists.fedoraproject.org >> Fedora Code of Conduct: >> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: >> https://lists.fedoraproject.org/archives/list/t...@lists.fedoraproject.org >> Do not reply to spam on the list, report it: >> https://pagure.io/fedora-infrastructure >> > > > -- > Homepage: http://sayak.in > About Me: http://about.me/sayak_sarkar > Twitter: http://twitter.com/sayak_sarkar > Blog: http://sayaksarkar.wordpress.com > ___ > test mailing list -- t...@lists.fedoraproject.org > To unsubscribe send an email to test-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/t...@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Fedora Contributor Tee Shirt Giveaway
It has it was only valid yesterday On Fri, Apr 22, 2022 at 1:20 PM Sayak Sarkar wrote: > Cool Stuff store says that the promo code has already expired! :( > > On Fri, 22 Apr 2022 at 08:49, Chris Murphy > wrote: > >> I'm getting: There are currently no products linked to this invitation >> code... >> >> --- >> Chris Murphy >> ___ >> test mailing list -- t...@lists.fedoraproject.org >> To unsubscribe send an email to test-le...@lists.fedoraproject.org >> Fedora Code of Conduct: >> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: >> https://lists.fedoraproject.org/archives/list/t...@lists.fedoraproject.org >> Do not reply to spam on the list, report it: >> https://pagure.io/fedora-infrastructure >> > > > -- > Homepage: http://sayak.in > About Me: http://about.me/sayak_sarkar > Twitter: http://twitter.com/sayak_sarkar > Blog: http://sayaksarkar.wordpress.com > ___ > test mailing list -- t...@lists.fedoraproject.org > To unsubscribe send an email to test-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/t...@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: The future of FMN (Fedora Messaging Notifications)
> Not really. However, not sure if the "watch" is counted in this category > or in the previous. Right, it wasn't clear. When I wrote "my artifacts" I meant the artifacts I'm the owner of. > What belongs into this category? Not really sure. App maintainers may define in their message and schemas the users affected by the action that generated the message. It'll mean something different for every app I suppose. > It would be much easier if I can only "block" some notifications, when > everything is enabled by default. Yeah the current plan is that it's allowed by default, and if it's in a blocklist but *not* in an allowlist, it's blocked. > Currently I am notified by actions done by myself and I think there > should be option to disable this. Good point, noted. A. ___ 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: The future of FMN (Fedora Messaging Notifications)
> Groups. I want to be notified of what happens on group's artifacts, events > referring to the group's name. Good point! So let's say when an artifact is owned by a group you're a member of, you'll be considered an owner, and notified as such. Would that work for you? There's currently no standard way for app maintainer to declare that events refer to a group, as they currently can do with usernames. But maybe we should add that possibility, it's pretty easy. A. ___ 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-20220422.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-20220421.0): ID: 1234859 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/1234859 ID: 1234868 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/1234868 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: The future of FMN (Fedora Messaging Notifications)
> Please make it Matrix native. That way FMN can send richer and more > useful notifications. Yeah that's maybe the only additional feature we're considering adding :-) > I also want notifications about CI/CD things happening in PRs in Dist-Git. If a Fedora Message is sent, as long as the message schema flag it as affecting a package you own, it'll fall into the "packages I own" tracking rule. A. ___ 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: The future of FMN (Fedora Messaging Notifications)
On 22. 04. 22 9:16, Aurelien Bompard wrote: Hey folks! We're having a look at FMN these days, and we're trying to design its replacement in our Fedora Messaging enabled world. The current FMN has the following shortcomings: - too slow at runtime - slow at startup time (a couple of hours to startup…) - complex UI We think that this all comes from the same root cause: FMN is too flexible. It's trying to be everyone's procmail, and as a result the UI is complex and performance is hindered. Also, in the past years we've adopted quite a few external services (Discourse, Gitlab, etc) which come with their own notification systems, so the needs of FMN users may have changed, and FMN can no longer be the one-stop-shop of notifications it aimed to be. So we're planning to rewrite it as a much more simple notification system, with a few pre-defined things you could subscribe to, clearly presented in the UI but with less bells and whistles, and for that we're gathering your requirements. What do you want from Fedora's notifications? We have identified the following use cases: - I want to be notified of what happens on my artifacts (packages, containers, modules, flatpaks) - I want to be notified of what happens on any artifact by entering its type and its name - I want to be notified of events referring to my username - I want to be able to follow someone (for example, my mentee) - I want to be able to block or allow notifications from a particular application (koji, bodhi, dist-git, etc) - I want to my notifications to be sent via email and/or IRC Are there other use cases that would make your contributor's life easier? Groups. I want to be notified of what happens on group's artifacts, events referring to the group's name. Thanks. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ 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
Proposal: separate out gettext-tools from the main package
Hi, This proposal[1] is to extract the heavier part "tools" from the gettext main package into a separate sub-package. Inline with upstream packaging hints[2]. pros: smaller footprint of the gettext main package. cons: a large numbers of packagers may get affected directly or indirectly. (may require some initial changes) thoughts? they are very welcome. thanks, sundeep [1] https://src.fedoraproject.org/rpms/gettext/pull-request/15 [2] https://git.savannah.gnu.org/gitweb/?p=gettext.git;a=blob;f=PACKAGING;h=f4bae4561ec70a9de2532502b5c2358bb976036c;hb=HEAD ___ 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: Best way to enable -mbranch-protection for package
V Thu, Apr 21, 2022 at 11:12:41PM +0200, Marcin Zajączkowski napsal(a):
> Upgrading NetworkManager-sstp to the latest version, I've noticed that
> there is a failed test related to missing branch protection on AArch64
> [1].
Check annocheck version installed when building your package (root.log). There
was a bug manifesting as -mbranch-protection=standard failure on AArch64 and
fixed in 10.66:
* Wed Apr 13 2022 Nick Clifton - 10.66-1
- Annocheck: Do not complain about missing -mbranch-protection option in
AArch64 binaries if compiled in LTO mode.
> After reading that and [2], I know what it is all about, however, I
> wonder what is the best way to apply it to my package?
>
> Should I check if the build is for AArch64 and for Fedora 33+ (35+?) and
> just add "-mbranch-protection=standard"? Or there is some magic macro to
> add that (and maybe some other useful security options), similar to
> %{?_smp_mflags} (or maybe even included in %make_build on ARM64)?
>
The option is already presented in system-wide CFLAGS. Check any build.log.
If you package respects the flags (check your build.log), you don't need to do
anything. Otherwise, you should correct your package use all the options from
CFLAGS enviroment variable or %{build_cflags} RPM macro.
-- Petr
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: The future of FMN (Fedora Messaging Notifications)
Dne 22. 04. 22 v 9:16 Aurelien Bompard napsal(a): Hey folks! We're having a look at FMN these days, and we're trying to design its replacement in our Fedora Messaging enabled world. The current FMN has the following shortcomings: - too slow at runtime - slow at startup time (a couple of hours to startup…) - complex UI We think that this all comes from the same root cause: FMN is too flexible. It's trying to be everyone's procmail, and as a result the UI is complex and performance is hindered. Also, in the past years we've adopted quite a few external services (Discourse, Gitlab, etc) which come with their own notification systems, so the needs of FMN users may have changed, and FMN can no longer be the one-stop-shop of notifications it aimed to be. So we're planning to rewrite it as a much more simple notification system, with a few pre-defined things you could subscribe to, clearly presented in the UI but with less bells and whistles, and for that we're gathering your requirements. What do you want from Fedora's notifications? We have identified the following use cases: - I want to be notified of what happens on my artifacts (packages, containers, modules, flatpaks) Yes - I want to be notified of what happens on any artifact by entering its type and its name Not really. However, not sure if the "watch" is counted in this category or in the previous. - I want to be notified of events referring to my username What belongs into this category? Not really sure. - I want to be able to follow someone (for example, my mentee) I have never used this, so this is just nice to have. I think that following in BZ is good enough. - I want to be able to block or allow notifications from a particular application (koji, bodhi, dist-git, etc) It would be much easier if I can only "block" some notifications, when everything is enabled by default. - I want to my notifications to be sent via email and/or IRC Email! Are there other use cases that would make your contributor's life easier? Currently I am notified by actions done by myself and I think there should be option to disable this. Admitedly, notification about build finished after some time might be useful, comparing to information that I have commented in some Pagure ticket. Vít We're not committing to implementing everything that will be suggested here, since we want to keep the app as simple as we can, but we're very interested in your use cases. And if you want to do something very complex with notifications, we can also help you write a Fedora Messaging callback that will give you the full power of the message bus :-) Thanks for your help! Aurélien ___ 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 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: The future of FMN (Fedora Messaging Notifications)
On Fri, Apr 22, 2022 at 3:24 AM Aurelien Bompard wrote: > > Hey folks! > > We're having a look at FMN these days, and we're trying to design its > replacement in our Fedora Messaging enabled world. > The current FMN has the following shortcomings: > - too slow at runtime > - slow at startup time (a couple of hours to startup…) > - complex UI > > We think that this all comes from the same root cause: FMN is too flexible. > It's trying to be everyone's procmail, and as a result the UI is complex and > performance is hindered. > > Also, in the past years we've adopted quite a few external services > (Discourse, Gitlab, etc) which come with their own notification systems, so > the needs of FMN users may have changed, and FMN can no longer be the > one-stop-shop of notifications it aimed to be. > > So we're planning to rewrite it as a much more simple notification system, > with a few pre-defined things you could subscribe to, clearly presented in > the UI but with less bells and whistles, and for that we're gathering your > requirements. > > What do you want from Fedora's notifications? We have identified the > following use cases: > - I want to be notified of what happens on my artifacts (packages, > containers, modules, flatpaks) > - I want to be notified of what happens on any artifact by entering its type > and its name > - I want to be notified of events referring to my username > - I want to be able to follow someone (for example, my mentee) > - I want to be able to block or allow notifications from a particular > application (koji, bodhi, dist-git, etc) > - I want to my notifications to be sent via email and/or IRC > > Are there other use cases that would make your contributor's life easier? > We're not committing to implementing everything that will be suggested here, > since we want to keep the app as simple as we can, but we're very interested > in your use cases. > And if you want to do something very complex with notifications, we can also > help you write a Fedora Messaging callback that will give you the full power > of the message bus :-) > Please make it Matrix native. That way FMN can send richer and more useful notifications. I also want notifications about CI/CD things happening in PRs in Dist-Git. -- 真実はいつも一つ！/ 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
Re: Fedora Contributor Tee Shirt Giveaway
On Fri, Apr 22, 2022 at 12:49 PM Leigh Scott wrote: > > Why post something that has expired? Hi leigh, When I shared the email, the giveaway was still active :) given it was just for 24 hours, It had to expire after some time (This is mentioned in the blog) I definitely could have highlighted in the email as well! Hope it was useful to some > ___ > 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 -- Vipul Siddharth He/His/Him Fedora | CentOS CI Infrastructure Team ___ 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
The future of FMN (Fedora Messaging Notifications)
Hey folks! We're having a look at FMN these days, and we're trying to design its replacement in our Fedora Messaging enabled world. The current FMN has the following shortcomings: - too slow at runtime - slow at startup time (a couple of hours to startup…) - complex UI We think that this all comes from the same root cause: FMN is too flexible. It's trying to be everyone's procmail, and as a result the UI is complex and performance is hindered. Also, in the past years we've adopted quite a few external services (Discourse, Gitlab, etc) which come with their own notification systems, so the needs of FMN users may have changed, and FMN can no longer be the one-stop-shop of notifications it aimed to be. So we're planning to rewrite it as a much more simple notification system, with a few pre-defined things you could subscribe to, clearly presented in the UI but with less bells and whistles, and for that we're gathering your requirements. What do you want from Fedora's notifications? We have identified the following use cases: - I want to be notified of what happens on my artifacts (packages, containers, modules, flatpaks) - I want to be notified of what happens on any artifact by entering its type and its name - I want to be notified of events referring to my username - I want to be able to follow someone (for example, my mentee) - I want to be able to block or allow notifications from a particular application (koji, bodhi, dist-git, etc) - I want to my notifications to be sent via email and/or IRC Are there other use cases that would make your contributor's life easier? We're not committing to implementing everything that will be suggested here, since we want to keep the app as simple as we can, but we're very interested in your use cases. And if you want to do something very complex with notifications, we can also help you write a Fedora Messaging callback that will give you the full power of the message bus :-) Thanks for your help! Aurélien ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Fedora Contributor Tee Shirt Giveaway
Why post something that has expired? ___ 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
