F37 Change: MinGW OpenSSL 3.x update (Self-Contained Change proposal)
https://fedoraproject.org/wiki/Changes/F37MingwOpenSSL3 == Summary == Update OpenSSL for MinGW to version 3.x == Owner == * Name: [[User:smani|Sandro Mani]] * Email: manisan...@gmail.com == Detailed Description == mingw-openssl will be updated to version 3.x. The following dependencies will be rebuilt: * mingw-spice-gtk (will be updated to version 0.39) * mingw-spice-protocol (will be updated to 0.14.3) * mingw-qt6-qtbase * mingw-qca * mingw-gstreamer1-plugins-bad-free * mingw-curl * mingw-python3 * mingw-postgresql * mingw-podofo * mingw-opusfile * mingw-minizip * mingw-libssh2 * mingw-gdal * mingw-openssl == Benefit to Fedora == Ship up-to-date OpenSSL libraries for MinGW. == Scope == * Proposal owners: mingw-openssl will be updated and the mentioned dependencies rebuilt. * Other developers: No action required * Release engineering: Mass rebuild requested * Policies and guidelines: No policies need to be changed == Upgrade/compatibility impact == No impact == How To Test == If your application uses OpenSSL to communicate via TLS or perform other tasks that use cryptographic algorithms from OpenSSL, please test whether it continues to work properly. This should be covered by the comprehensive upstream testsuite of OpenSSL. However many dependent packages also provide good test coverage of OpenSSL functionality. == User Experience == There should be no impact on end-user experience. == Dependencies == None == Contingency Plan == * Contingency mechanism: Revert to older versions of environment / toolchain, mass rebuild mingw packages again * Contingency deadline: Before release * Blocks release? Yes * Blocks product? No == Release Notes == Fedora 37 comes with mingw-openssl-3.x. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
List of long term FTBFS packages to be retired in March
Dear maintainers. Based on the current fail to build from source policy, the following packages should be retired from Fedora 36 approximately one week before branching. However, 5 weekly reminders are required and I forgot to start this sooner, hence the retirement will happen in 5 weeks, i.e. March 1st 2022. Since this is after the Beta Freeze, I will skip retiring components with depending packages. Such components will be retired during the next release cycle, and are included in this report for completeness. Policy: https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ The packages in rawhide were not successfully built at least since Fedora 33. This report is based on dist tags. Packages collected via: https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb 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 adf-tribun-fonts frixxon, nim catharsis-cormorant-fonts nim chocolate-doomsundaram ecolier-court-fonts frixxon, nim gfs-ambrosia-fontsfrixxon, nim gfs-artemisia-fonts nim gfs-baskerville-fonts nim gfs-bodoni-classic-fonts nim gfs-bodoni-fonts nim gfs-complutum-fonts nim gfs-decker-fonts nim gfs-didot-classic-fonts nim gfs-didot-display-fonts nim gfs-didot-fonts nim gfs-eustace-fonts nim gfs-fleischman-fonts nim gfs-galatea-fonts nim gfs-garaldus-fontsnim gfs-gazis-fonts nim gfs-goschen-fonts nim gfs-ignacio-fonts nim gfs-jackson-fonts nim gfs-neohellenic-fonts nim gfs-neohellenic-math-fontsnim gfs-nicefore-fontsnim gfs-olga-fontsnim gfs-orpheus-classic-fonts nim gfs-orpheus-fonts nim gfs-orpheus-sans-fontsnim gfs-philostratos-fontsnim gfs-porson-fonts nim gfs-pyrsos-fonts nim gfs-solomos-fonts nim gfs-theokritos-fonts nim ht-alegreya-sans-fontsnim ibm-plex-fontssuraia impallari-dancing-script-fontsnim impallari-raleway-fonts nim intel-clear-sans-fontsnim jetbrains-mono-fonts nim kemie-bellota-fonts nim libicu65 pwalter ndiscover-exo-2-fonts nim rubygem-cucumber-railsmmorsi, vondruch rubygem-selenium-webdrivermmorsi, ruby-packagers-sig, vondruch rubygem-supdcallagh, jaruga, ruby-packagers-sig, shreyankg sil-alkalami-fontsnim sil-andika-compact-fonts nim sil-andika-fonts nim sil-andika-new-basic-fontsnim sil-annapurna-fonts nim sil-apparatus-fonts nim sil-awami-nastaliq-fonts nim sil-charis-compact-fonts nim sil-charis-fonts kevin, nim sil-dai-banna-fonts nim sil-ezra-fontsnim sil-gentium-plus-compact-fontsnim sil-harmattan-fonts nim sil-mondulkiri-extra-fontsnim sil-mondulkiri-fonts nim sil-namdhinggo-fonts nim sil-shimenkan-fonts nim sil-sophia-nubian-fonts nim sil-tagmukay-fontsnim sil-tai-heritage-pro-fontsnim symbian-m-yuppy-gb-fonts nim tmux-top ttomecek typesetit-great-vibes-fonts nim uswds-public-sans-fonts nim vernnobile-muli-fonts nim vernnobile-nunito-fonts nim vernnobile-oswald-fonts nim wagesreiter-patrick-hand-fontsnim weiweihuanghuang-work-sans-fonts nim yanone-kaffeesatz-fonts nim The following packages require above mentioned packages: Depending on: impallari-raleway-fonts (90) R-rmarkdown (maintained by: qulogic) R-rmarkdown-2.10-2.fc36.src requires impallari-raleway-fonts = 4.025-3.20200310git98add57.fc33 sympa (maintained by: xavierb) sympa-6.2.68-1.fc36.src requires impallari-raleway-fonts = 4.025-3.20200310git98add57.fc33 sympa-6.2.68-1.fc36.x86_64 requires impallari-raleway-fonts = 4.025-3.20200310git98add57.fc33 R-BiocFileCache (maintained by: spot) R-BiocFileCache-2.0.0-3.fc36.src requires R-rmarkdown = 2.10-2.fc36 R-DBItest (maintained by: qulogic) R-DBItest-1.7.0-6.fc36.src requires R-rmarkdown =
Action Required: Bugzilla - API Authentication changes
Forwarded Message Subject: [Bugzilla-announce-list] Action Required: Bugzilla - API Authentication changes Date: Tue, 1 Feb 2022 12:28:13 +1000 From: Jeff Fearn To: bugzilla-announce-l...@redhat.com Tl;dr From Monday 28th February, applications making API calls to Bugzilla may no longer authenticate using passwords or supplying API keys in call parameters. Instead, API keys must be supplied in the Authorization header. Support for using the Authorization header has been deployed to all Red Hat Bugzilla instances. You can change your code at any time and not have to wait for the old methods to be disabled. We will require all authenticated API usage to use this new method; this will break API access to Red Hat Bugzilla for any tools that don't use the Authorization header [1]. If you are not certain your tooling authenticates using this header then you need to take action to confirm it does and to modify your tooling to use it if it doesn't. This new method does away with logging in and out of the API and uses API_KEYs in a standard Authorization header. This header needs to be sent with every call to the API. The old methods will be disabled on a rolling basis across the RHBZ servers. Target Dates: https://bugzilla.stage.redhat.com - Mon 07th Feb 00:00 UTC https://bugzilla.redhat.com - Mon 28th Feb 00:00 UTC IMPORTANT If you attempt to use an old method to authenticate to the API after this change has been made, the API_KEY or password supplied will be treated as potentially compromised and invalidated immediately. If you supplied your password then you will need to follow the forgot password process to reset it. If you supplied an API_KEY it will have been banned and you will need to generate a new API_KEY in the UI. This invalidation will happen every time an attempt to use an outdated authentication method is detected. If you are using python-bugzilla you need to upgrade to version 3.2.0 which will automatically use the new method of authentication. If you are using other tools you will need to look into how they work and see how to adjust them to use the Authorization header instead of the other parameters. If you need assistance understanding how to update your applications, please reach out to us by the following means. - If you have an active subscription via https://access.redhat.com/support/ - If you are a Red Hat Partner then please contact your partner representative - Or email us at bugzilla-ow...@redhat.com The Red Hat Bugzilla Team. 1: https://bugzilla.redhat.com/docs/en/html/api/core/v1/general.html#authentication ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
