December 2019 - devel - Fedora Mailing-Lists

Fedora-Rawhide-20191221.n.0 compose check report

by Fedora compose checker

No missing expected images. Compose PASSES proposed Rawhide gating check! All required tests passed Failed openQA tests: 4/155 (x86_64), 1/2 (arm) Old failures (same test failed in Fedora-Rawhide-20191218.n.0): ID: 501082 Test: x86_64 Server-dvd-iso modularity_tests URL: https://openqa.fedoraproject.org/tests/501082 ID: 501097 Test: x86_64 Server-dvd-iso server_cockpit_basic URL: https://openqa.fedoraproject.org/tests/501097 ID: 501137 Test: arm Minimal-raw_xz-raw.xz install_arm_image_deployment_upload URL: https://openqa.fedoraproject.org/tests/501137 ID: 501145 Test: x86_64 universal install_arabic_language URL: https://openqa.fedoraproject.org/tests/501145 ID: 501215 Test: x86_64 universal install_iscsi URL: https://openqa.fedoraproject.org/tests/501215 Soft failed openQA tests: 87/155 (x86_64) (Tests completed, but using a workaround for a known bug) New soft failures (same test not soft failed in Fedora-Rawhide-20191218.n.0): ID: 501197 Test: x86_64 universal install_serial_console URL: https://openqa.fedoraproject.org/tests/501197 Old soft failures (same test soft failed in Fedora-Rawhide-20191218.n.0): ID: 501063 Test: x86_64 Server-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/501063 ID: 501064 Test: x86_64 Server-boot-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/501064 ID: 501068 Test: x86_64 Server-dvd-iso install_repository_nfs_variation URL: https://openqa.fedoraproject.org/tests/501068 ID: 501069 Test: x86_64 Server-dvd-iso install_repository_nfs_graphical URL: https://openqa.fedoraproject.org/tests/501069 ID: 501070 Test: x86_64 Server-dvd-iso install_repository_nfsiso_variation URL: https://openqa.fedoraproject.org/tests/501070 ID: 501071 Test: x86_64 Server-dvd-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/501071 ID: 501072 Test: x86_64 Server-dvd-iso install_repository_hd_variation URL: https://openqa.fedoraproject.org/tests/501072 ID: 501073 Test: x86_64 Server-dvd-iso install_vnc_server URL: https://openqa.fedoraproject.org/tests/501073 ID: 501074 Test: x86_64 Server-dvd-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/501074 ID: 501076 Test: x86_64 Server-dvd-iso install_vnc_client URL: https://openqa.fedoraproject.org/tests/501076 ID: 501077 Test: x86_64 Server-dvd-iso install_vncconnect_client URL: https://openqa.fedoraproject.org/tests/501077 ID: 501088 Test: x86_64 Server-dvd-iso install_updates_nfs URL: https://openqa.fedoraproject.org/tests/501088 ID: 501093 Test: x86_64 Server-dvd-iso server_realmd_join_kickstart URL: https://openqa.fedoraproject.org/tests/501093 ID: 501096 Test: x86_64 Server-dvd-iso install_vncconnect_server URL: https://openqa.fedoraproject.org/tests/501096 ID: 501102 Test: x86_64 Everything-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/501102 ID: 501103 Test: x86_64 Everything-boot-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/501103 ID: 501111 Test: x86_64 Workstation-live-iso desktop_update_graphical URL: https://openqa.fedoraproject.org/tests/501111 ID: 501116 Test: x86_64 Workstation-live-iso desktop_printing URL: https://openqa.fedoraproject.org/tests/501116 ID: 501129 Test: x86_64 KDE-live-iso desktop_update_graphical URL: https://openqa.fedoraproject.org/tests/501129 ID: 501134 Test: x86_64 KDE-live-iso desktop_printing URL: https://openqa.fedoraproject.org/tests/501134 ID: 501139 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/501139 ID: 501140 Test: x86_64 universal install_ext3 URL: https://openqa.fedoraproject.org/tests/501140 ID: 501141 Test: x86_64 universal install_no_swap URL: https://openqa.fedoraproject.org/tests/501141 ID: 501142 Test: x86_64 universal install_updates_img_local URL: https://openqa.fedoraproject.org/tests/501142 ID: 501143 Test: x86_64 universal install_shrink_ext4 URL: https://openqa.fedoraproject.org/tests/501143 ID: 501146 Test: x86_64 universal install_kickstart_firewall_disabled URL: https://openqa.fedoraproject.org/tests/501146 ID: 501147 Test: x86_64 universal install_anaconda_text URL: https://openqa.fedoraproject.org/tests/501147 ID: 501148 Test: x86_64 universal install_sata@uefi URL: https://openqa.fedoraproject.org/tests/501148 ID: 501149 Test: x86_64 universal upgrade_2_minimal_64bit URL: https://openqa.fedoraproject.org/tests/501149 ID: 501150 Test: x86_64 universal install_shrink_ntfs URL: https://openqa.fedoraproject.org/tests/501150 ID: 501152 Test: x86_64 universal install_xfs URL: https://openqa.fedoraproject.org/tests/501152 ID: 501153 Test: x86_64 universal install_blivet_ext3 URL: https://openqa.fedoraproject.org/tests/501153 ID: 501154 Test: x86_64 universal install_delete_partial@uefi URL: https://openqa.fedoraproject.org/tests/501154 ID: 501156 Test: x86_64 universal install_repository_http_graphical URL: https://openqa.fedoraproject.org/tests/501156 ID: 501157 Test: x86_64 universal install_mirrorlist_graphical URL: https://openqa.fedoraproject.org/tests/501157 ID: 501158 Test: x86_64 universal install_sata URL: https://openqa.fedoraproject.org/tests/501158 ID: 501159 Test: x86_64 universal install_simple_encrypted@uefi URL: https://openqa.fedoraproject.org/tests/501159 ID: 501160 Test: x86_64 universal install_multi_empty@uefi URL: https://openqa.fedoraproject.org/tests/501160 ID: 501162 Test: x86_64 universal install_blivet_lvmthin@uefi URL: https://openqa.fedoraproject.org/tests/501162 ID: 501163 Test: x86_64 universal install_kickstart_user_creation URL: https://openqa.fedoraproject.org/tests/501163 ID: 501164 Test: x86_64 universal install_multi URL: https://openqa.fedoraproject.org/tests/501164 ID: 501165 Test: x86_64 universal install_multi@uefi URL: https://openqa.fedoraproject.org/tests/501165 ID: 501166 Test: x86_64 universal install_simple_encrypted URL: https://openqa.fedoraproject.org/tests/501166 ID: 501167 Test: x86_64 universal install_simple_free_space URL: https://openqa.fedoraproject.org/tests/501167 ID: 501168 Test: x86_64 universal install_multi_empty URL: https://openqa.fedoraproject.org/tests/501168 ID: 501169 Test: x86_64 universal install_software_raid URL: https://openqa.fedoraproject.org/tests/501169 ID: 501170 Test: x86_64 universal install_lvmthin URL: https://openqa.fedoraproject.org/tests/501170 ID: 501172 Test: x86_64 universal install_kickstart_firewall_configured URL: https://openqa.fedoraproject.org/tests/501172 ID: 501174 Test: x86_64 universal install_blivet_software_raid@uefi URL: https://openqa.fedoraproject.org/tests/501174 ID: 501175 Test: x86_64 universal upgrade_2_server_64bit URL: https://openqa.fedoraproject.org/tests/501175 ID: 501177 Test: x86_64 universal install_scsi_updates_img URL: https://openqa.fedoraproject.org/tests/501177 ID: 501178 Test: x86_64 universal install_blivet_xfs@uefi URL: https://openqa.fedoraproject.org/tests/501178 ID: 501179 Test: x86_64 universal install_lvmthin@uefi URL: https://openqa.fedoraproject.org/tests/501179 ID: 501181 Test: x86_64 universal upgrade_server_64bit URL: https://openqa.fedoraproject.org/tests/501181 ID: 501182 Test: x86_64 universal upgrade_2_kde_64bit URL: https://openqa.fedoraproject.org/tests/501182 ID: 501184 Test: x86_64 universal install_delete_pata URL: https://openqa.fedoraproject.org/tests/501184 ID: 501185 Test: x86_64 universal install_blivet_no_swap URL: https://openqa.fedoraproject.org/tests/501185 ID: 501186 Test: x86_64 universal install_blivet_xfs URL: https://openqa.fedoraproject.org/tests/501186 ID: 501187 Test: x86_64 universal install_blivet_software_raid URL: https://openqa.fedoraproject.org/tests/501187 ID: 501188 Test: x86_64 universal install_blivet_lvmthin URL: https://openqa.fedoraproject.org/tests/501188 ID: 501189 Test: x86_64 universal install_blivet_ext3@uefi URL: https://openqa.fedoraproject.org/tests/501189 ID: 501190 Test: x86_64 universal install_blivet_btrfs@uefi URL: https://openqa.fedoraproject.org/tests/501190 ID: 501191 Test: x86_64 universal install_blivet_no_swap@uefi URL: https://openqa.fedoraproject.org/tests/501191 ID: 501192 Test: x86_64 universal install_simple_free_space@uefi URL: https://openqa.fedoraproject.org/tests/501192 ID: 501193 Test: x86_64 universal install_btrfs@uefi URL: https://openqa.fedoraproject.org/tests/501193 ID: 501194 Test: x86_64 universal install_ext3@uefi URL: https://openqa.fedoraproject.org/tests/501194 ID: 501195 Test: x86_64 universal install_xfs@uefi URL: https://openqa.fedoraproject.org/tests/501195 ID: 501196 Test: x86_64 universal upgrade_2_minimal_uefi@uefi URL: https://openqa.fedoraproject.org/tests/501196 ID: 501198 Test: x86_64 universal install_blivet_btrfs URL: https://openqa.fedoraproject.org/tests/501198 ID: 501199 Test: x86_64 universal install_package_set_minimal URL: https://openqa.fedoraproject.org/tests/501199 ID: 501200 Test: x86_64 universal upgrade_2_server_domain_controller URL: https://openqa.fedoraproject.org/tests/501200 ID: 501201 Test: x86_64 universal upgrade_2_realmd_client URL: https://openqa.fedoraproject.org/tests/501201 ID: 501203 Test: x86_64 universal install_repository_http_variation URL: https://openqa.fedoraproject.org/tests/501203 ID: 501204 Test: x86_64 universal install_no_swap@uefi URL: https://openqa.fedoraproject.org/tests/501204 ID: 501205 Test: x86_64 universal upgrade_minimal_uefi@uefi URL: https://openqa.fedoraproject.org/tests/501205 ID: 501207 Test: x86_64 universal install_delete_pata@uefi URL: https://openqa.fedoraproject.org/tests/501207 ID: 501208 Test: x86_64 universal install_delete_partial URL: https://openqa.fedoraproject.org/tests/501208 ID: 501209 Test: x86_64 universal install_btrfs URL: https://openqa.fedoraproject.org/tests/501209 ID: 501210 Test: x86_64 universal install_software_raid@uefi URL: https://openqa.fedoraproject.org/tests/501210 ID: 501211 Test: x86_64 universal install_kickstart_hdd URL: https://openqa.fedoraproject.org/tests/501211 ID: 501212 Test: x86_64 universal upgrade_minimal_64bit URL: https://openqa.fedoraproject.org/tests/501212 ID: 501213 Test: x86_64 universal upgrade_server_domain_controller URL: https://openqa.fedoraproject.org/tests/501213 ID: 501214 Test: x86_64 universal install_kickstart_nfs URL: https://openqa.fedoraproject.org/tests/501214 ID: 501216 Test: x86_64 universal install_pxeboot@uefi URL: https://openqa.fedoraproject.org/tests/501216 ID: 501217 Test: x86_64 universal upgrade_realmd_client URL: https://openqa.fedoraproject.org/tests/501217 ID: 501219 Test: x86_64 universal install_pxeboot URL: https://openqa.fedoraproject.org/tests/501219 Passed openQA tests: 64/155 (x86_64) New passes (same test not passed in Fedora-Rawhide-20191218.n.0): ID: 501128 Test: x86_64 KDE-live-iso desktop_notifications_postinstall URL: https://openqa.fedoraproject.org/tests/501128 Skipped non-gating openQA tests: 1 of 157 Installed system changes in test x86_64 Server-boot-iso install_default: Used mem changed from 188 MiB to 212 MiB Previous test data: https://openqa.fedoraproject.org/tests/499659#downloads Current test data: https://openqa.fedoraproject.org/tests/501063#downloads Installed system changes in test x86_64 Server-boot-iso install_default@uefi: Used mem changed from 189 MiB to 214 MiB Previous test data: https://openqa.fedoraproject.org/tests/499660#downloads Current test data: https://openqa.fedoraproject.org/tests/501064#downloads Installed system changes in test x86_64 Everything-boot-iso install_default: Used mem changed from 137 MiB to 160 MiB Previous test data: https://openqa.fedoraproject.org/tests/499698#downloads Current test data: https://openqa.fedoraproject.org/tests/501102#downloads Installed system changes in test x86_64 Everything-boot-iso install_default@uefi: Used mem changed from 139 MiB to 161 MiB Previous test data: https://openqa.fedoraproject.org/tests/499699#downloads Current test data: https://openqa.fedoraproject.org/tests/501103#downloads Installed system changes in test x86_64 Workstation-live-iso install_default_upload: System load changed from 0.71 to 0.57 Previous test data: https://openqa.fedoraproject.org/tests/499700#downloads Current test data: https://openqa.fedoraproject.org/tests/501104#downloads Installed system changes in test x86_64 Workstation-live-iso install_default@uefi: Used swap changed from 7 MiB to 12 MiB System load changed from 0.50 to 0.78 Previous test data: https://openqa.fedoraproject.org/tests/499704#downloads Current test data: https://openqa.fedoraproject.org/tests/501108#downloads Installed system changes in test x86_64 KDE-live-iso install_default_upload: System load changed from 1.61 to 1.89 Previous test data: https://openqa.fedoraproject.org/tests/499718#downloads Current test data: https://openqa.fedoraproject.org/tests/501122#downloads Installed system changes in test x86_64 KDE-live-iso install_default@uefi: System load changed from 0.85 to 1.30 Previous test data: https://openqa.fedoraproject.org/tests/499720#downloads Current test data: https://openqa.fedoraproject.org/tests/501124#downloads Installed system changes in test x86_64 universal install_package_set_kde: System load changed from 1.72 to 0.77 Previous test data: https://openqa.fedoraproject.org/tests/499777#downloads Current test data: https://openqa.fedoraproject.org/tests/501171#downloads -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose

4 years, 4 months

1
0
0 / 0

CPE Weekly: 2019-12-20

by Aoife Moloney

Hi everyone, Welcome to the CPE team weekly project update mail! Important Note: Please note there will be no weekly emails over the holiday period of 23rd December 2019 - 2nd January 2020*. The next CPE weekly email will be sent on Friday 10th January 2020. As you may be aware, either from the CPE weekly emails or from previous years, Red Hat has a mandatory shutdown period between Christmas and New Year in many countries. This allows most associates to celebrate the holiday season with friends and family and recharge their batteries after a busy year. Multiple Red Hat teams will be observing this period, including Fedora & CentOS infrastructure teams, and we want to raise awareness that availability will be minimal during this time. *While the formal shutdown period ends on the 2nd of January 2020, many people will not be back until Monday the 6th of January 2020. As all of our team members are also passionate Community members, there may be some coverage, but this is not guaranteed and will be on a best effort basis. Any coverage offered will ultimately be at the personal choice of the individual during their time off. We want to take this time to wish you and yours a healthy and happy Christmas period and a most prosperous New Year. We look forward to working closely with you over the coming year! Background: The Community Platform Engineering group is the Red Hat team combining IT and release engineering from Fedora and CentOS. Our goal is to keep core servers and services running and maintained, build releases, and other strategic tasks that need more dedicated time than volunteers can give. For better communication, we will be giving weekly reports to the CentOS and Fedora communities about the general tasks and work being done. Also for better communication between our groups we have created #redhat-cpe on Freenode IRC! Please feel free to catch us there, a mail has landed on both the CentOS and Fedora devel lists with context here. High Level Project Updates: Fedora: General Updates Nagios plugins were fixed to work on EL8/F31 Support was added for fedora messaging wire format to jms-messaging plugin There is one prerequisite:RabbitMQ PR needs to be merged first Other work this week with RabbitMQ includes: An issue in RabbitMQ jms-messaging plugin PR was fixed Two new PR’s in Anitya The issue in the-new-hotness was also fixed when it stopped consuming messages - it was caused by empty version and the fix for this already in Anitya master The team deployed distgit-bugzilla-sync script in openshift Pagure Updates We also worked on pagure-dist-git PR review/merges this week The team cleaned up the bugzilla override patches for pagure-dist-git https://pagure.io/pagure-dist-git/pull-request/82 We modified output of pagure-dist-git/scripts/pagure_poc.py to include assignee information https://pagure.io/pagure-dist-git/pull-request/90 We updated distgit_bugzilla_sync/script.py to read the assignee information from above instead of fedora-scm-requests https://pagure.io/Fedora-Infra/distgit-bugzilla-sync/pull-request/40 We fixed mdapi headers for CORS: https://pagure.io/mdapi/pull-request/93 And they are already reviewed and merged :) We also wrote script to read assignee information from fedora-scm-requests and added it to dist-git Tiger Team Updates: OSBS Issue deploying the aarch64 cluster. There is a problem while using openshift-ansible to authenticate with quay.io Bodhi CD Tiger Team Working on dockerizing the celery worker on the vm Community Fire Fighting Team Merged the PR adding a new API endpoint to pagure allowing to enable/disable git hooks Decommissioned ci-cc-rdu01 Good progress on anitya 0.18.0 (see below) Added CORS headers to mdapi making it easier to do cross-domain JSON/ajax requests to it Application Retirements Elections Everything should be ready now to move Elections to Communishift so stay tuned for a move date in the new year! Fedocal No progress on kanban board last eight weeks - looks abandoned https://teams.fedoraproject.org/project/fedora-calendar/kanban Jlanda’s permission error https://pagure.io/fedora-infrastructure/issue/8274 Nuancier Benson Muite is now working on OIDC authentication PR from sebwoj - Porting to Fedora messaging EPEL 8 Modularity This currently needs a rebuild to epel-release with new mirrorlist links https://src.fedoraproject.org/rpms/epel-release/pull-request/4) The team are currently facing this EPEL 8 Playground Modularity Blocker: https://pagure.io/fm-orchestrator/issue/1541 CentOS The CR variant from the Stream composes, seems to work, 8.1.1911 will use a similar variant to populate the CR repo on the mirrors The team is also still working on preparing the next migration to wiki.centos.org www.centos.org Forums The team have started new ansible roles to automate deploy + upgrade of those migrated services We are still finishing templates for mailman ansible role (new look with community members) Working on koji (cbs.dev) to see when we can import 8.1 content to let SIGs build against/for .el8 and .el8s (Stream) The team are still investigating an Ansible upgrade for centos (currently on 2.6.20 and needs testing with 2.9) and then also with .el8 roles compatibility Misc Updates Reviews, Updates & Fixes: Anitya Investigating & testing done with GNOME’s Gitlab instance forURL https://github.com/release-monitoring/anitya/issues/763 Vagrant box is now bumped to Fedora 31 & test https://github.com/release-monitoring/anitya/pull/858 Fetch only newer version from GitHub using cursor https://github.com/release-monitoring/anitya/issues/589 https://github.com/release-monitoring/anitya/pull/863 Releases_only changed on edit https://github.com/release-monitoring/anitya/pull/857 Ecosystem when homepage or backend is changed is fixed https://github.com/release-monitoring/anitya/pull/859 API filtering is now case insensitive https://github.com/release-monitoring/anitya/pull/862 Fedora-active-user Fixes Moved searching mailing lists away from gmane and to hyperkitty https://github.com/pypingou/fedora-active-user/pull/15 Duffy Duffy progressGCI is going great & in just 2 weeks 1000 tasks have been done which is more than 3 times of total tasks done last year (yes, in total!) Miscellaneous fix https://github.com/pypingou/fedora-active-user/pull/16 Note: This document is currently built from individual reports rolled into a document which we edit and copy into a final document. We are aware that this causes problems with some email readers, and are working on a method to make this less problematic. Comments? Suggestions? Feedback? Let Us Know! And have a wonderful holiday season! Kindest regards, Aoife -- Aoife Moloney Feature Driver Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford

4 years, 4 months

1
0
0 / 0

Discrepancy between koji build and repository content

by alciregi＠gmail.com

Hello. Looking at https://koji.fedoraproject.org/koji/buildinfo?buildID=1423008 I can see that, for instance, samba-winbind-clients was successfully built for every architecture, in particular x86_64 and i686. But dnf reports that only the x86_64 package is available, and indeed, looking inside https://dl.fedoraproject.org/pub/fedora/linux/updates/31/Everything/x86_6... there is not the i686 RPM. There is a specific reason or there is some kind of bug? Thanks, A.

4 years, 4 months

2
2
0 / 0

Self Introduction: Michal Bocek

by mbocek

Hi, I've been working at Red Hat mainly on tools dealing with upgrades of major versions of RHEL. I've also developed a tool called convert2rhel which automates the conversion of CentOS and Oracle Linux to RHEL. I've recently open sourced the conver2rhel code and my goal now is to get it to EPEL (only, not Fedora). I would greatly appreciate a review of the package: https://bugzilla.redhat.com/show_bug.cgi?id=1785735 Thank you, -- Michal Bocek OS and Application Modernization Senior Software Engineer Red Hat Czech s.r.o.

4 years, 4 months

1
0
0 / 0

List of long term FTBFS packages to be retired in February (release candidate)

by Miro Hrončok

Dear maintainers. Based on the latest fail to build from source policy, the following packages will be retired from Fedora 32 approximately one week before branching (February 2020). Policy: https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fai... The packages in rawhide were not successfully built at least since Fedora 30. This report is based on dist tags and represents a preliminary list of packages. Packages collected via: https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ft... The main purpose is to gather feedback. If you see a package that was built, please let me know. If you see a package that should be exempted from the process, please let me know and we can work together to get a FESCo approval for that. If you see a package that can be rebuilt, please do so. Package (co)maintainers Latest build ================================================================================ dnssec-nodes hardaker Fedora 27 elasticsearch hubbitus, jvanek, lbazan, Fedora 24 zbyszek expresso jamielinux, nodejs-sig, Fedora 28 patches gnomint verdurin Fedora 24 libocrdma ocrdma Fedora 27 lilyterm cwickert Fedora 27 nuvola-app-google-calendar martinkg Fedora 29 nuvola-app-groove martinkg Fedora 28 nuvola-app-logitech-media- martinkg Fedora 29 server nuvola-app-plex martinkg Fedora 29 nuvola-app-soundcloud martinkg Fedora 29 nuvola-app-yandex-music martinkg Fedora 29 rubygem-connection_pool anujmore Fedora 24 rubygem-session gomix Fedora 29 shim-unsigned-aarch64 pjones Fedora 28 shim-unsigned-x64 pjones Fedora 28 target-isns grover, mlombard Fedora 27 tcmu-runner mlombard Fedora 26 telepathy-gabble aperezbios Fedora 29 telepathy-salut aperezbios, johnp Fedora 29 The following packages require above mentioned packages: Depending on: expresso (1) nodejs-chrono (maintained by: jamielinux, nodejs-sig, tomh) nodejs-chrono-1.0.5-10.fc31.src requires npm(expresso) = 0.9.2 Depending on: rubygem-connection_pool (45) rubygem-activestorage (maintained by: ruby-packagers-sig, vondruch) rubygem-activestorage-5.2.3-3.fc31.src requires rubygem(connection_pool) = 2.2.0-1 rubygem-activesupport (maintained by: jaruga, jstribny, kanarip, mmorsi, pvalena, ruby-packagers-sig, sseago, vondruch) rubygem-activesupport-1:5.2.3-2.fc31.src requires rubygem(connection_pool) = 2.2.0-1 rubygem-rails (maintained by: jstribny, kanarip, mmorsi, mtasaka, pvalena, ruby-packagers-sig, sseago, tdawson, vondruch) rubygem-rails-1:5.2.3-2.fc31.noarch requires rubygem(activestorage) = 5.2.3 rubygem-railties (maintained by: mmorsi, pvalena, vondruch) rubygem-railties-5.2.3-3.fc31.src requires rubygem(activestorage) = 5.2.3 rubygem-actionpack (maintained by: jaruga, jstribny, kanarip, mmorsi, pvalena, ruby-packagers-sig, sseago, vondruch) rubygem-actionpack-1:5.2.3-3.fc31.noarch requires rubygem(activesupport) = 5.2.3 rubygem-actionpack-1:5.2.3-3.fc31.src requires rubygem(activesupport) = 5.2.3 rubygem-actionview (maintained by: jaruga, pvalena, ruby-packagers-sig) rubygem-actionview-5.2.3-3.fc31.noarch requires rubygem(activesupport) = 5.2.3 rubygem-actionview-5.2.3-3.fc31.src requires rubygem(activesupport) = 5.2.3 rubygem-activejob (maintained by: pvalena, vondruch) rubygem-activejob-5.2.3-2.fc31.noarch requires rubygem(activesupport) = 5.2.3 rubygem-activejob-5.2.3-2.fc31.src requires rubygem(activesupport) = 5.2.3 rubygem-activemodel (maintained by: jstribny, mmorsi, pvalena, vondruch) rubygem-activemodel-5.2.3-3.fc31.noarch requires rubygem(activesupport) = 5.2.3 rubygem-activemodel-5.2.3-3.fc31.src requires rubygem(activesupport) = 5.2.3 rubygem-activemodel-serializers-xml (maintained by: vondruch) rubygem-activemodel-serializers-xml-1.0.1-8.fc31.noarch requires rubygem(activesupport) = 5.2.3 rubygem-activemodel-serializers-xml-1.0.1-8.fc31.src requires rubygem(activesupport) = 5.2.3 rubygem-activerecord (maintained by: jaruga, kanarip, mmorsi, mtasaka, pvalena, ruby-packagers-sig, sseago, vondruch) rubygem-activerecord-1:5.2.3-2.fc31.noarch requires rubygem(activesupport) = 5.2.3 rubygem-activerecord-1:5.2.3-2.fc31.src requires rubygem(activesupport) = 5.2.3 rubygem-activeresource (maintained by: jstribny, kanarip, mmorsi, vondruch) rubygem-activeresource-1:5.0.0-6.fc31.noarch requires rubygem(activesupport) = 5.2.3 rubygem-activeresource-1:5.0.0-6.fc31.src requires rubygem(activesupport) = 5.2.3 rubygem-ammeter (maintained by: jaruga, jstribny, ruby-packagers-sig, vondruch) rubygem-ammeter-1.1.4-4.fc31.noarch requires rubygem(activesupport) = 5.2.3 rubygem-ancestry (maintained by: jaruga, pvalena, ruby-packagers-sig) rubygem-ancestry-3.0.0-6.fc31.src requires rubygem(activesupport) = 5.2.3 rubygem-backports (maintained by: ruby-packagers-sig, vondruch) rubygem-backports-3.11.4-3.fc31.src requires rubygem(activesupport) = 5.2.3 rubygem-clockwork (maintained by: pvalena) rubygem-clockwork-2.0.4-1.fc32.noarch requires rubygem(activesupport) = 5.2.3 rubygem-clockwork-2.0.4-1.fc32.src requires rubygem(activesupport) = 5.2.3 rubygem-delayed_job (maintained by: vondruch) rubygem-delayed_job-4.1.5-3.fc31.noarch requires rubygem(activesupport) = 5.2.3 rubygem-delorean (maintained by: jstribny, vondruch) rubygem-delorean-2.1.0-9.fc31.src requires rubygem(activesupport) = 5.2.3 rubygem-excon (maintained by: jstribny, tdawson, vondruch) rubygem-excon-0.62.0-3.fc31.src requires rubygem(activesupport) = 5.2.3 rubygem-factory_bot (maintained by: pvalena) rubygem-factory_bot-4.10.0-3.fc31.noarch requires rubygem(activesupport) = 5.2.3 rubygem-generator_spec (maintained by: ilgrad) rubygem-generator_spec-0.9.4-6.fc31.noarch requires rubygem(activesupport) = 5.2.3 rubygem-globalid (maintained by: jaruga, pvalena, ruby-packagers-sig) rubygem-globalid-0.4.2-2.fc31.noarch requires rubygem(activesupport) = 5.2.3 rubygem-globalid-0.4.2-2.fc31.src requires rubygem(activesupport) = 5.2.3 rubygem-i18n (maintained by: humaton, ruby-packagers-sig, stahnma, vondruch) rubygem-i18n-1.7.0-1.fc32.src requires rubygem(activesupport) = 5.2.3 rubygem-jbuilder (maintained by: pvalena, vondruch) rubygem-jbuilder-2.7.0-6.fc31.noarch requires rubygem(activesupport) = 5.2.3 rubygem-jquery-rails (maintained by: jstribny, vondruch) rubygem-jquery-rails-4.2.2-7.fc31.src requires rubygem(activesupport) = 5.2.3 rubygem-logstasher (maintained by: valtri) rubygem-logstasher-1.3.0-3.fc31.noarch requires rubygem(activesupport) = 5.2.3 rubygem-more_core_extensions (maintained by: mmorsi) rubygem-more_core_extensions-1.2.0-10.fc31.noarch requires rubygem(activesupport) = 5.2.3 rubygem-multi_test (maintained by: jaruga, pvalena, ruby-packagers-sig) rubygem-multi_test-0.1.2-8.fc32.src requires rubygem(activesupport) = 5.2.3 rubygem-pdfkit (maintained by: mtasaka) rubygem-pdfkit-0.8.4.1-2.fc31.src requires rubygem(activesupport) = 5.2.3 rubygem-pundit (maintained by: pvalena) rubygem-pundit-2.0.1-3.fc31.noarch requires rubygem(activesupport) = 5.2.3 rubygem-rack-attack (maintained by: valtri) rubygem-rack-attack-5.0.1-5.fc31.src requires rubygem(activesupport) = 5.2.3 rubygem-rails-controller-testing (maintained by: valtri) rubygem-rails-controller-testing-1.0.2-6.fc31.noarch requires rubygem(activesupport) = 5.2.3 rubygem-rails-deprecated_sanitizer (maintained by: vondruch) rubygem-rails-deprecated_sanitizer-1.0.3-10.fc31.noarch requires rubygem(activesupport) = 5.2.3 rubygem-rails-deprecated_sanitizer-1.0.3-10.fc31.src requires rubygem(activesupport) = 5.2.3 rubygem-rails-dom-testing (maintained by: ruby-packagers-sig, vondruch) rubygem-rails-dom-testing-2.0.2-7.fc31.noarch requires rubygem(activesupport) = 5.2.3 rubygem-rails-dom-testing-2.0.2-7.fc31.src requires rubygem(activesupport) = 5.2.3 rubygem-recaptcha (maintained by: vondruch) rubygem-recaptcha-3.4.0-7.fc31.src requires rubygem(activesupport) = 5.2.3 rubygem-rsolr (maintained by: vondruch) rubygem-rsolr-1.1.2-7.fc31.src requires rubygem(activesupport) = 5.2.3 rubygem-rspec-rails (maintained by: clalance, vondruch) rubygem-rspec-rails-3.9.0-1.fc32.noarch requires rubygem(activesupport) = 5.2.3 rubygem-shoulda-matchers (maintained by: vondruch) rubygem-shoulda-matchers-4.1.2-2.fc32.noarch requires rubygem(activesupport) = 5.2.3 rubygem-simple-navigation (maintained by: athoscr) rubygem-simple-navigation-4.0.5-6.fc31.noarch requires rubygem(activesupport) = 5.2.3 rubygem-spring (maintained by: jaruga, pvalena, ruby-packagers-sig, vondruch) rubygem-spring-2.0.0-7.fc31.noarch requires rubygem(activesupport) = 5.2.3 rubygem-spring-2.0.0-7.fc31.src requires rubygem(activesupport) = 5.2.3 rubygem-spring-watcher-listen (maintained by: jaruga, ruby-packagers-sig) rubygem-spring-watcher-listen-2.0.1-8.fc31.src requires rubygem(activesupport) = 5.2.3 rubygem-sprockets-rails (maintained by: jaruga, pvalena, ruby-packagers-sig) rubygem-sprockets-rails-3.2.1-4.fc31.noarch requires rubygem(activesupport) = 5.2.3 rubygem-timecop (maintained by: ruby-packagers-sig, vondruch) rubygem-timecop-0.9.1-1.fc32.src requires rubygem(activesupport) = 5.2.3 rubygem-treetop (maintained by: mmorsi, vondruch) rubygem-treetop-1.6.10-2.fc31.src requires rubygem(activesupport) = 5.2.3 rubygem-wikicloth (maintained by: vondruch) rubygem-wikicloth-0.8.0-12.fc31.src requires rubygem(activesupport) = 5.2.3 rubygem-yell (maintained by: valtri) rubygem-yell-2.0.7-6.fc31.src requires rubygem(activesupport) = 5.2.3 Too many dependencies for rubygem-connection_pool, not all listed here Depending on: rubygem-session (21) rubygem-rr (maintained by: gomix) rubygem-rr-1.1.2-11.fc31.src requires rubygem(session) = 3.1.0-1 rubygem-loofah (maintained by: ruby-packagers-sig, vondruch) rubygem-loofah-2.3.1-1.fc32.src requires rubygem(rr) = 1.1.2 rubygem-rspec-core (maintained by: bkearney, mtasaka, ruby-packagers-sig, skottler, tdawson, vondruch) rubygem-rspec-core-3.9.0-2.fc32.src requires rubygem(rr) = 1.1.2 rubygem-test-unit-rr (maintained by: mtasaka) rubygem-test-unit-rr-1.0.5-8.fc31.noarch requires rubygem(rr) = 1.1.2 rubygem-test-unit-rr-1.0.5-8.fc31.src requires rubygem(rr) = 1.1.2 vim-command-t (maintained by: vondruch) vim-command-t-5.0.2-8.fc31.src requires rubygem(rr) = 1.1.2 rubygem-rails-html-sanitizer (maintained by: jaruga, pvalena, ruby-packagers-sig, vondruch) rubygem-rails-html-sanitizer-1.3.0-1.fc32.noarch requires rubygem(loofah) = 2.3.1 rubygem-rails-html-sanitizer-1.3.0-1.fc32.src requires rubygem(loofah) = 2.3.1 dmlite (maintained by: adev, andreamanzi, gbitzes, okeeble, rocha) dmlite-puppet-dpm-1.13.99-3.fc32.noarch requires /usr/bin/rspec rubygem-apipie-rails (maintained by: jaruga, ruby-packagers-sig, vondruch) rubygem-apipie-rails-0.5.5-5.fc31.src requires /usr/bin/rspec rubygem-cucumber-expressions (maintained by: jackorp) rubygem-cucumber-expressions-6.0.1-3.fc31.src requires /usr/bin/rspec rubygem-cucumber-tag_expressions (maintained by: jackorp) rubygem-cucumber-tag_expressions-1.1.1-3.fc31.src requires /usr/bin/rspec rubygem-jekyll-email-protect (maintained by: jackorp) rubygem-jekyll-email-protect-1.1.0-3.fc31.src requires /usr/bin/rspec rubygem-rb-inotify (maintained by: jstribny, vondruch) rubygem-rb-inotify-0.10.0-2.fc31.src requires /usr/bin/rspec rubygem-ruby-dbus (maintained by: vondruch) rubygem-ruby-dbus-doc-0.11.0-8.fc31.noarch requires /usr/bin/rspec rubygem-gettext (maintained by: mtasaka, sseago) rubygem-gettext-3.2.9-6.fc31.src requires rubygem(test-unit-rr) = 1.0.5, rubygem(test-unit-rr) = 1.0.5-8.fc31 rubygem-locale (maintained by: mmorsi, mtasaka) rubygem-locale-2.1.2-1.fc31.7.src requires rubygem(test-unit-rr) = 1.0.5, rubygem(test-unit-rr) = 1.0.5-8.fc31 rubygem-native-package-installer (maintained by: mtasaka) rubygem-native-package-installer-1.0.9-1.fc32.src requires rubygem(test-unit-rr) = 1.0.5, rubygem(test-unit-rr) = 1.0.5-8.fc31 rubygem-rabbit (maintained by: mtasaka) rubygem-rabbit-3.0.0-2.fc32.src requires rubygem(test-unit-rr) = 1.0.5, rubygem(test-unit-rr) = 1.0.5-8.fc31 rubygem-cucumber (maintained by: clalance, jstribny, mmorsi, ruby-packagers-sig, tdawson, vondruch) rubygem-cucumber-3.1.2-6.fc31.noarch requires rubygem(cucumber-expressions) = 6.0.1 rubygem-cucumber-3.1.2-6.fc31.src requires rubygem(cucumber-expressions) = 6.0.1 rubygem-cucumber-core (maintained by: jaruga, ruby-packagers-sig, vondruch) rubygem-cucumber-core-3.2.0-3.fc31.noarch requires rubygem(cucumber-tag_expressions) = 1.1.1 rubygem-cucumber-core-3.2.0-3.fc31.src requires rubygem(cucumber-tag_expressions) = 1.1.1 rubygem-jekyll-git-authors (maintained by: jackorp) rubygem-jekyll-git-authors-1.0.0-2.fc31.noarch requires rubygem(jekyll-email-protect) = 1.1.0 rubygem-listen (maintained by: jaruga, ruby-packagers-sig, vondruch) rubygem-listen-3.2.0-1.fc32.noarch requires rubygem(rb-inotify) = 0.10.0 rubygem-listen-3.2.0-1.fc32.src requires rubygem(rb-inotify) = 0.10.0 Too many dependencies for rubygem-session, not all listed here Depending on: tcmu-runner (1) gluster-block (maintained by: devos, jarrpa) gluster-block-0.4-4.fc32.x86_64 requires tcmu-runner = 1.1.3-2.fc26 Depending on: telepathy-gabble (61) ktp-accounts-kcm (maintained by: dvratil, jgrulich, jreznik, mck182, rdieter) ktp-accounts-kcm-19.08.3-1.fc32.i686 requires telepathy-gabble = 0.18.4-7.fc29 ktp-accounts-kcm-19.08.3-1.fc32.x86_64 requires telepathy-gabble = 0.18.4-7.fc29 sugar (maintained by: aperezbios, dsd, erikos, johnp, pbrobinson, sdz, tuxbrewr) sugar-0.116-2.fc32.noarch requires telepathy-gabble = 0.18.4-7.fc29 ktp-contact-list (maintained by: dvratil, jgrulich, jreznik, mck182, rdieter) ktp-contact-list-19.08.3-1.fc32.x86_64 requires ktp-accounts-kcm = 19.08.3-1.fc32 ktp-text-ui (maintained by: dvratil, jgrulich, jreznik, mck182, rdieter) ktp-text-ui-19.08.3-1.fc32.i686 requires ktp-accounts-kcm = 19.08.3-1.fc32 ktp-text-ui-19.08.3-1.fc32.x86_64 requires ktp-accounts-kcm = 19.08.3-1.fc32 olpc-switch-desktop (maintained by: cjb, dsd, pbrobinson) olpc-switch-desktop-0.9.2-3.fc32.noarch requires sugar = 0.116-2.fc32 sugar-abacus (maintained by: callkalpa, pbrobinson) sugar-abacus-60-4.fc31.noarch requires sugar = 0.116-2.fc32 sugar-calculator (maintained by: callkalpa, erikos, pbrobinson, tuxbrewr) sugar-calculator-44-6.fc30.noarch requires sugar = 0.116-2.fc32 sugar-castle (maintained by: callkalpa, snavin) sugar-castle-23-15.fc31.noarch requires sugar = 0.116-2.fc32 sugar-chat (maintained by: callkalpa, erikos, pbrobinson, tuxbrewr) sugar-chat-85-2.fc31.noarch requires sugar = 0.116-2.fc32 sugar-clock (maintained by: callkalpa, pbrobinson, tuxbrewr) sugar-clock-21-2.fc31.noarch requires sugar = 0.116-2.fc32 sugar-colordeducto (maintained by: callkalpa, snavin) sugar-colordeducto-7-14.fc31.noarch requires sugar = 0.116-2.fc32 sugar-connect (maintained by: callkalpa, pbrobinson, tuxbrewr) sugar-connect-22-24.fc31.noarch requires sugar = 0.116-2.fc32 sugar-countries (maintained by: callkalpa) sugar-countries-33-17.fc31.noarch requires sugar = 0.116-2.fc32 sugar-deducto (maintained by: callkalpa, snavin) sugar-deducto-9-16.fc31.noarch requires sugar = 0.116-2.fc32 sugar-distance (maintained by: callkalpa, pbrobinson, tuxbrewr) sugar-distance-35-11.fc31.noarch requires sugar = 0.116-2.fc32 sugar-finance (maintained by: callkalpa, pbrobinson, tuxbrewr) sugar-finance-14-4.fc31.noarch requires sugar = 0.116-2.fc32 sugar-flip (maintained by: callkalpa) sugar-flip-9-14.fc31.noarch requires sugar = 0.116-2.fc32 sugar-flipsticks (maintained by: callkalpa, pbrobinson, tuxbrewr) sugar-flipsticks-13-14.fc31.noarch requires sugar = 0.116-2.fc32 sugar-fototoon (maintained by: callkalpa) sugar-fototoon-23-6.fc31.noarch requires sugar = 0.116-2.fc32 sugar-fractionbounce (maintained by: callkalpa) sugar-fractionbounce-25-6.fc31.noarch requires sugar = 0.116-2.fc32 sugar-getiabooks (maintained by: callkalpa, pbrobinson, tuxbrewr) sugar-getiabooks-18.2-2.fc31.noarch requires sugar = 0.116-2.fc32 sugar-hello-world (maintained by: callkalpa) sugar-hello-world-6-15.fc31.noarch requires sugar = 0.116-2.fc32 sugar-imageviewer (maintained by: callkalpa, erikos, pbrobinson, sdz, tuxbrewr) sugar-imageviewer-64-3.fc31.noarch requires sugar = 0.116-2.fc32 sugar-implode (maintained by: callkalpa, pbrobinson, tuxbrewr) sugar-implode-19-3.fc31.noarch requires sugar = 0.116-2.fc32 sugar-infoslicer (maintained by: callkalpa, pbrobinson, tuxbrewr) sugar-infoslicer-25-7.fc31.noarch requires sugar = 0.116-2.fc32 sugar-jukebox (maintained by: callkalpa, pbrobinson, sdz) sugar-jukebox-34-4.fc31.noarch requires sugar = 0.116-2.fc32 sugar-kuku (maintained by: callkalpa, snavin) sugar-kuku-5-11.fc31.noarch requires sugar = 0.116-2.fc32 sugar-labyrinth (maintained by: callkalpa, pbrobinson, sdz) sugar-labyrinth-16-12.fc31.noarch requires sugar = 0.116-2.fc32 sugar-locosugar (maintained by: callkalpa) sugar-locosugar-11-13.fc31.noarch requires sugar = 0.116-2.fc32 sugar-log (maintained by: callkalpa, erikos, tuxbrewr) sugar-log-40-2.fc31.noarch requires sugar = 0.116-2.fc32 sugar-maze (maintained by: callkalpa, pbrobinson, tuxbrewr) sugar-maze-28-3.fc31.noarch requires sugar = 0.116-2.fc32 sugar-measure (maintained by: callkalpa) sugar-measure-102-4.fc31.noarch requires sugar = 0.116-2.fc32 sugar-memorize (maintained by: callkalpa, pbrobinson, tuxbrewr) sugar-memorize-55-3.fc31.noarch requires sugar = 0.116-2.fc32 sugar-moon (maintained by: bkearney) sugar-moon-19-3.fc31.noarch requires sugar = 0.116-2.fc32 sugar-nutrition (maintained by: callkalpa) sugar-nutrition-15-7.fc31.noarch requires sugar = 0.116-2.fc32 sugar-paint (maintained by: callkalpa, pbrobinson, sdz) sugar-paint-68-2.fc30.x86_64 requires sugar = 0.116-2.fc32 sugar-physics (maintained by: callkalpa, pbrobinson, sdz) sugar-physics-34-3.fc31.noarch requires sugar = 0.116-2.fc32 sugar-pippy (maintained by: callkalpa, pbrobinson, tuxbrewr) sugar-pippy-72-5.fc31.x86_64 requires sugar = 0.116-2.fc32 sugar-playgo (maintained by: callkalpa, pbrobinson, tuxbrewr) sugar-playgo-5-21.fc31.noarch requires sugar = 0.116-2.fc32 sugar-portfolio (maintained by: callkalpa) sugar-portfolio-51-3.fc31.noarch requires sugar = 0.116-2.fc32 sugar-pukllanapac (maintained by: callkalpa) sugar-pukllanapac-13-7.fc31.noarch requires sugar = 0.116-2.fc32 sugar-recall (maintained by: callkalpa) sugar-recall-6-4.fc31.noarch requires sugar = 0.116-2.fc32 sugar-record (maintained by: callkalpa, pbrobinson, tuxbrewr) sugar-record-200.2-3.fc31.noarch requires sugar = 0.116-2.fc32 sugar-ruler (maintained by: callkalpa) sugar-ruler-33-13.fc31.noarch requires sugar = 0.116-2.fc32 sugar-runner (maintained by: pbrobinson) sugar-runner-0.110.0-9.fc31.i686 requires sugar = 0.116-2.fc32 sugar-runner-0.110.0-9.fc31.x86_64 requires sugar = 0.116-2.fc32 sugar-speak (maintained by: callkalpa, pbrobinson, tuxbrewr) sugar-speak-57-3.fc31.noarch requires sugar = 0.116-2.fc32 sugar-srilanka (maintained by: callkalpa, snavin) sugar-srilanka-3-11.fc31.noarch requires sugar = 0.116-2.fc32 sugar-starchart (maintained by: callkalpa, snavin) sugar-starchart-16-12.fc31.noarch requires sugar = 0.116-2.fc32 sugar-stopwatch (maintained by: callkalpa, pbrobinson, tuxbrewr) sugar-stopwatch-20.1-3.fc31.noarch requires sugar = 0.116-2.fc32 sugar-story (maintained by: snavin) sugar-story-19-3.fc31.noarch requires sugar = 0.116-2.fc32 sugar-terminal (maintained by: callkalpa, erikos, pbrobinson, tuxbrewr) sugar-terminal-46-2.fc31.noarch requires sugar = 0.116-2.fc32 sugar-turtleart (maintained by: bkearney, erikos, sdz) sugar-turtleart-218-3.fc31.noarch requires sugar = 0.116-2.fc32 sugar-typing-turtle (maintained by: callkalpa, sdz) sugar-typing-turtle-31-11.fc31.noarch requires sugar = 0.116-2.fc32 sugar-view-slides (maintained by: callkalpa, pbrobinson, tuxbrewr) sugar-view-slides-8-21.fc31.noarch requires sugar = 0.116-2.fc32 sugar-visualmatch (maintained by: callkalpa, sdz) sugar-visualmatch-49-12.fc31.noarch requires sugar = 0.116-2.fc32 sugar-words (maintained by: callkalpa) sugar-words-23-5.fc31.noarch requires sugar = 0.116-2.fc32 sugar-write (maintained by: callkalpa, erikos, pbrobinson, tuxbrewr) sugar-write-100-2.fc31.noarch requires sugar = 0.116-2.fc32 sugar-xoeditor (maintained by: callkalpa, snavin) sugar-xoeditor-13-11.fc31.noarch requires sugar = 0.116-2.fc32 sugar-xoirc (maintained by: callkalpa, pbrobinson, tuxbrewr) sugar-xoirc-12-11.fc31.noarch requires sugar = 0.116-2.fc32 sugar-xomail (maintained by: callkalpa, pbrobinson) sugar-xomail-0-0.20.20090128.fc31.noarch requires sugar = 0.116-2.fc32 sugar-yupana (maintained by: callkalpa, snavin) sugar-yupana-17-11.fc31.noarch requires sugar = 0.116-2.fc32 Too many dependencies for telepathy-gabble, not all listed here Affected (co)maintainers adev: rubygem-session andreamanzi: rubygem-session anujmore: rubygem-connection_pool aperezbios: telepathy-salut, telepathy-gabble athoscr: rubygem-connection_pool bkearney: rubygem-session, telepathy-gabble callkalpa: telepathy-gabble cjb: telepathy-gabble clalance: rubygem-session, rubygem-connection_pool cwickert: lilyterm devos: tcmu-runner dsd: telepathy-gabble dvratil: telepathy-gabble erikos: telepathy-gabble gbitzes: rubygem-session gomix: rubygem-session grover: target-isns hardaker: dnssec-nodes hubbitus: elasticsearch humaton: rubygem-connection_pool ilgrad: rubygem-connection_pool jackorp: rubygem-session jamielinux: expresso jarrpa: tcmu-runner jaruga: rubygem-session, rubygem-connection_pool jgrulich: telepathy-gabble johnp: telepathy-salut, telepathy-gabble jreznik: telepathy-gabble jstribny: rubygem-session, rubygem-connection_pool jvanek: elasticsearch kanarip: rubygem-connection_pool lbazan: elasticsearch martinkg: nuvola-app-logitech-media-server, nuvola-app-google-calendar, nuvola-app-yandex-music, nuvola-app-groove, nuvola-app-soundcloud, nuvola-app-plex mck182: telepathy-gabble mlombard: tcmu-runner, target-isns mmorsi: rubygem-session, rubygem-connection_pool mtasaka: rubygem-session, rubygem-connection_pool nodejs-sig: expresso ocrdma: libocrdma okeeble: rubygem-session patches: expresso pbrobinson: telepathy-gabble pjones: shim-unsigned-x64, shim-unsigned-aarch64 pvalena: rubygem-session, rubygem-connection_pool rdieter: telepathy-gabble rocha: rubygem-session ruby-packagers-sig: rubygem-session, rubygem-connection_pool sdz: telepathy-gabble skottler: rubygem-session snavin: telepathy-gabble sseago: rubygem-session, rubygem-connection_pool stahnma: rubygem-connection_pool tdawson: rubygem-session, rubygem-connection_pool tomh: expresso tuxbrewr: telepathy-gabble valtri: rubygem-connection_pool verdurin: gnomint vondruch: rubygem-session, rubygem-connection_pool zbyszek: elasticsearch

4 years, 4 months

4
7
0 / 0

Bug filing/triage/ownership policy for modules

by David Cantrell

With regard to the recent protobuf package issue and the eclipse module, I started wondering how bugs work with packages bundled in modules. That is, packages that exist outside modules (e.g., protobuf) that end up bundled with some module. NOTE: It is very easy for module posts to quickly balloon out in to all sorts of topics and stories. I would prefer that we keep this thread related to the Subject above. Thanks. The following are policy questions I came up with after the protobuf issue happened: 1) Are modules allowed to bundle packages that are provided by and currently maintained in the base system? Are there are restrictions to what a module can bundle (e.g., can a module bundle glibc)? 2) Using protobuf as an example, if a bug is found by a user and they happen to deduce that the error is in protobuf, how do they file a bug? Do they file the bug against protobuf if the bundled one from the module has the issue? What maintainer is on the hook for handling that bug report? My assumption here is that the module maintainer is ultimately responsible for everything they bundle. Another concern I see here is we are opening ourselves up for N+1 different builds of protobuf where N is the number of modules installed on a system and all of them could have protobuf bundled. 3) If a user files a bug against a module and the module maintainer triages that to a bundled package, how is that handled? Who is maintaining the bundled build of that package? Who is responsible for fixing it? 4) How can users determine what packages are installed from a module and how can you see what, if any, module "owns" a package? I have been unable to determine how to do this from dnf. 5) How are CVEs handled for packages that are also bundled with a module? I have read as much as I can find about how things work right now with modules, but that has been mostly the "how" and nothing around policy. Thanks, -- David Cantrell <dcantrell(a)redhat.com> Red Hat, Inc. | Boston, MA | EST5EDT

4 years, 4 months

12
27
0 / 0

Fedora 32 System-Wide Change proposal: LTO by default for package builds

by Ben Cotton

https://fedoraproject.org/wiki/LTOByDefault == Summary == This is a proposal to enable link time optimization (LTO) of packages built with rpmbuild by default. It's an over-simplification, but think of LTO as deferring analysis, optimization and code generation until creation of an executable or dynamic shared object. This is implemented by adding the option "-flto" the injected flags in redhat-rpm-config. There will be a simple way for packages to opt-out of LTO. == Owner == * Name: Jeff Law * Email: law(a)redhat.com == Detailed Description == Programs built with rpmbuild and which honor flags injection via redhat-rpm-config will be built with LTO by default. A simple opt-out mechanism will be provided for packages which use features that are not LTO compatible. The LTO bytecode itself will not be distributed as it is not stable from one GCC release to the next. This is enforced by stripping the LTO bytecode from any installed .o/.a files. We'll use bits SuSE has already written for redhat-rpm-config to implement this. Minor changes are desirable to the %configure macro in redhat-rpm-config to fix common code idioms used by autoconf generated scripts which are compromised by the additional optimization enabled by LTO. Minor updates to various packages will be needed to opt-out of LTO or fix bugs exposed by LTO. == Benefit to Fedora == The primary benefits of building with LTO enabled are smaller, faster executables/DSOs. A secondary benefit is LTO allows deeper analysis of package source code at compile time which can improve various GCC diagnostics and thus improve our ability to catch bugs at compile time such as uninitialized objects, buffer overflows, unterminated strings, restrict violations, etc. This change also brings us back on-par with SuSE who enabled LTO by default for their free distribution earlier in 2019. == Scope == * Proposal owners: The primary change is to redhat-rpm-config to add LTO to the default compile/link flags as well as a conditional which allows easy opt-out on a package by package basis. Additionally the post-build scripts need to strip the LTO bytecodes from any installed .o/.a files. Additionally, we know there are many packages with configure scripts that are compromised by LTO. I have tweaks to the %configure macro in redhat-rpm-config which fixes the vast majority of these problems with a few simple sed scripts on the generated output. Like the basic support for injecting the LTO flags, this will require coordination with the redhat-rpm-config maintainers. Packages which call configure directly and have compromised tests will need a one line change to their .spec files to fix their configure scripts. Some packages will need to opt-out of using LTO at this time. The most common case are packages that use symbol versioning or toplevel ASM statements. While there is a new mechanism to make LTO work with symbol versioning, I don't think any packages have been updated to use that mechanism. This will require a one line change to 50-75 packages (my script to find these is still running). Finally, some packages will fail to build with LTO due to deeper analysis for compile-time diagnostics catching programming mistakes that have gone unnoticed until now. I'll obviously be working with package maintainers on all of these issues. Note that even though the changes are fairly well localized in redhat-rpm-config and a small number of packages, the real scope of this change is much larger since it affects all packages in the distribution that are compiled with GCC and which honor the flags injection by redhat-rpm-config. * Other developers: As I mentioned, I'm happy to contact package owners that need to modify their packages and suggest how their package needs to be fixed. As a multi-decade GCC developer, I'm particularly well suited to describe LTO, its limitations and how LTO impacts the diagnostics from GCC to any package owner that needs additional information. I'm also capable and available to address any GCC issues that we may arise as a result of this change. I don't expect much of the latter as SuSE has already enabled this feature for their distribution and thus weeded out most of the issues. The highest level of coordination will be with the redhat-rpm-config maintainers. I will also be coordinating with the GDB team to address debugging issues related to LTO. The most important issue is to ensure that we can pass the GDB testsuite with and without the -flto option being enabled. Failure to meet this goal would be considered a blocking issue for LTO enablement. I'm also already in contact with SuSE and Debian/Ununtu engineers to discuss issues with gcc-10 with and without LTO. We know there are some problems with debugging LTO code. I will be working with the GDB team to identify these issues and fix them either in the debugger or compiler as needed. I have prototype code for the required redhat-rpm-config changes and I'll coordinate with the redhat-rpm-config maintainer to get them into the desired final form. I also know every package that fails with LTO enabled. I'm still categorizing those failures. Many will ultimately need to use the opt-out mechanism because they use features that are not compatible with LTO. I expect to have all this ready to go the first work week of the new year. I will coordinate with package owners to either add the opt-out markers or fix issues in the package as needed. * Release engineering: (a check of an impact with Release Engineering is needed) Aside from the redhat-rpm-config changes, I do not expect any work from releng to be necessary. However, they need to be aware of the change and who to contact in case of issues. * Policies and guidelines: It would be useful to document how to opt-out of LTO in the packaging guidelines. * Trademark approval: N/A (not needed for this Change) == Upgrade/compatibility impact == Should not affect compatibility. Stripping of the LTO bytecode is critical to ensure there are not long term compatibility issues. == How To Test == In the short term, I'm happy to expose a repository with a gcc-10 snapshot and updated redhat-rpm-config. Developers could then use that repo to pick up gcc-10 and LTO optimizations for testing purposes. I'm already doing this internally for x86_64 and exposing it to the world would be trivial. Given such a repository, another developer would merely use that repo when building their package. No special hardware is needed. The most useful testing is first to identify FTBFS issues and get them proactively fixed. I'm happy to own that since I'm already doing that for baseline gcc-10 issues as well as gcc-10 + LTO issues. Doing the same testing on other architectures would definitely be useful. I'd be particularly concerned about large packages on the 32bit architectures. I wouldn't be surprised if we find some packages need to opt-out of LTO because they run out of memory at link/compile time. I'm already in contact with some Debian maintainers who want to do testing around this issue as they're investigating a similar change for Debian. I'm already building all of Fedora with the weekly gcc-10 snapshots (including LTO builds starting the week of 12/15). This is primarily to proactive find/address issues with the gcc-10 transition, but verification of LTO state pretty much piggy backs for free on the gcc-10 work. == User Experience == In theory, the only noticeable difference to users would be smaller, faster binaries and DSOs. However, a developer that uses rpmbuild to build their own code may see their package fail to build if it's got errors or uses certain features that do not work with LTO. Users who try to debug Fedora shipped executables could notice differences in the debugging experience. == Dependencies == None expected beyond addressing FTBFS issues and coordination between GCC and GDB teams on any debugging issues we find over the next few weeks. == Contingency Plan == * Contingency mechanism: Revert the LTO flags injection * Contingency deadline: Beta freeze, but shooting for prior to mass rebuilds starting * Blocks release? No * Blocks product? No Most critically, if we don't address the GDB testsuite issue noted above, our fallback position would be to simply disable the LTO injection globally and re-evaluate for Fedora 33, similarly if we were to find some show-stopping LTO issue. Otherwise the plan is to analyze the remaining 100-125 package build failures. These are likely a mixture of configure issues that can't be trivially fixed via %configure, new diagnostics exposed by the deeper analysis from LTO, and other small issues. == Documentation == I would think we would want documentation on the opt-out method for RPM builds. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

4 years, 4 months

6
5
0 / 0

Tito 0.6.12 release

by Jakub Kadlcik

Hello, I am happy to announce that after two years since the last tito [1] release, the 0.6.12 is finally out! See release notes [2] This very moment, updates were submitted to bodhi [3], feel free to try them. [1] https://github.com/dgoodwin/tito/ [2] https://github.com/dgoodwin/tito/releases/tag/tito-0.6.12-1 [3] https://bodhi.fedoraproject.org/updates/FEDORA-2019-5523b63c9c PS: This was my first release of tito project, so I hope I did everything correctly. I would like to thank all contributors, Jakub

4 years, 4 months

1
0
0 / 0

Announcing fmt library soversion bump

by Vitaly Zaitsev

Hello. Fmt 6.1.2 build completed for Rawhide. It include SOVERSION bump. All dependent packages need to be rebuilded. -- Sincerely, Vitaly Zaitsev (vitaly(a)easycoding.org)

4 years, 4 months

3
2
0 / 0

Self Introduction: Carson Black

by Carson Black

Greetings y'all. My name is Carson Black & it's nice to meet y'all. I'm from Frankfort, Kentucky (and no, I'm not interested in bourbon), and I'm currently a student at one of the high schools here. I'd be lying if I said I had any explicit goals with the Fedora project, as I just do what I feel like doing when I feel like doing it. ale li pona. :) However, I'm writing this email because I recently submitted a package for review (https://bugzilla.redhat.com/show_bug.cgi?id=1784230). I've been doing stuff with OSS for about over a year now, from doing packaging for openSUSE to abusing every last facility GTK+ provides as maintainer of Breeze GTK for KDE. I have experience with a variety of programming languages, but I'm most familiar with C/C++, Python, Go, & Vala. My GPG fingerprint is A133 906C E9F6 6BFD 2F27 7D67 05DF 0193 8FF8 0320. Looking forward to participating here with y'all. -- Carson Black [jan Pontaoski]

4 years, 4 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

devel December 2019