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 tomorrow, i.e. March 1st 2022.
Since this is after the Beta Freeze,
I will skip retiring components with depending packages.
Such components (if any) 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…
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/ftbf…
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
==========================================================================
libicu65 pwalter
rubygem-cucumber-rails orphan
rubygem-sup dcallagh, jaruga, ruby-packagers-sig, shreyankg
tmux-top ttomecek
All listed packages are leaf packages, nothing depends on them.
Affected (co)maintainers
dcallagh: rubygem-sup
jaruga: rubygem-sup
pwalter: libicu65
ruby-packagers-sig: rubygem-sup
shreyankg: rubygem-sup
ttomecek: tmux-top
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
https://fedoraproject.org/wiki/Changes/F37Boost178
== Summary ==
This change brings Boost 1.78 to Fedora. This will mean Fedora ships
with a recent upstream Boost release.
== Owner ==
* Name: [[User:trodgers| Thomas Rodgers]]
* Email: trodgers(a)redhat.com
== Detailed Description ==
The aim is to synchronize Fedora with the most recent Boost release.
Because ABI stability is absent from Boost, this entails rebuilding of
all dependent packages. This also entails the change owner assisting
maintainers of client packages in decoding cryptic boost-ese seen in
output from g++.
The equivalent changes for previous releases were
[[Changes/F35Boost176]], [[Changes/F34Boost175]],
[[Changes/F33Boost173]], [[Changes/F30Boost169|Fedora 30 Change]],
[[Changes/F29Boost167|Fedora 29 Change]], [[Changes/F28Boost166|Fedora
28 Change]], [[Changes/F27Boost164|Fedora 27 Change]],
[[Changes/F26Boost163|Fedora 26 Change]], [[Changes/F25Boost161|Fedora
25 Change]], [[Changes/F24Boost160|Fedora 24 Change]],
[[Changes/F23Boost159|Fedora 23 Change]] and
[[Changes/F22Boost158|Fedora 22 Change]].
== Benefit to Fedora ==
Fedora 37 includes Boost 1.78.
Fedora will stay relevant, as far as Boost clients are concerned.
Boost 1.78 does not bring any new components, but includes two new
header-only libraries from Boost 1.77 -
* Describe: A C++14 reflection library. Provides macros for describing
enumerators and struct/class members, and primitives for querying this
information.
* Lambda2: A C++14, dependency-free, single header lambda library.
Allows simple function objects to be constructed via expressions such
as _1 + 5, _1 % 2 == 0, _1 > _2, or _1 == ' ' || _1 == '\t'.
Boost 1.78 also includes many fixes and enhancements to existing components.
== Scope ==
* Proposal owners:
** Build will be done with Boost.Build v2 (which is the
upstream-sanctioned way of building Boost)
** Request a "f37-boost"
[https://docs.pagure.org/releng/sop_adding_side_build_targets.html
build system tag]
([http://lists.fedoraproject.org/pipermail/devel/2011-November/159908.html
discussion]):
** Build boost into that tag (take a look at the
[http://koji.fedoraproject.org/koji/buildinfo?buildID=606493 build
#606493] for inspiration)
** Post a request for rebuilds to fedora-devel
** Work on rebuilding dependent packages in the tag.
** When most is done, re-tag all the packages to rawhide
** Watch fedora-devel and assist in rebuilding broken Boost clients
(by fixing the client, or Boost).
* Other developers:
** Those who depend on Boost DSOs will have to rebuild their packages.
Feature owners will alleviate some of this work as indicated above,
and will assist those whose packages fail to build in debugging them.
* Release engineering: TODO <!-- [https://pagure.io/releng/issue/9421
#9421] --> (a check of an impact with Release Engineering is needed)
* Policies and guidelines:
** Apart from scope, this is business as usual, so no new policies, no
new guidelines.
* Trademark approval: N/A (not needed for this Change)
== Upgrade/compatibility impact ==
* No manual configuration or data migration needed.
* Some impact on other packages needing code changes to rebuild.
Historically this hasn't been too much of a problem and could always
be resolved before deadline.
== How To Test ==
* No special hardware is needed.
* Integration testing simply consists of installing Boost packages
(`dnf install boost`) on Fedora and checking that it does not break
other packages (see below for a way to obtain a list of boost
clients).
== User Experience ==
* Expected to remain largely the same.
* Developers building third-party software on Fedora may need to
rebuild against the new Boost packages, and may need to adjust their
code if the new Boost release is not source-compatible.
== Dependencies ==
Packages that must be rebuilt:
<code>$ dnf repoquery -s --releasever=rawhide --whatrequires
libboost\* --disablerepo=* --enablerepo=fedora | sort -u</code>
All clients:
<code>$ dnf repoquery --releasever=rawhide --archlist=src
--whatrequires boost-devel --disablerepo='*'
--enablerepo=fedora-source</code>
== Contingency Plan ==
* Contingency mechanism: Worst case scenario is to abandon the update
and simply ship F37 with Boost 1.76, which is already in rawhide.
* Blocks release? No
* Blocks product? None
== Documentation ==
* https://www.boost.org/users/history/version_1_78_0.html (released on
8th December 2021)
* https://www.boost.org/users/history/version_1_77_0.html (released on
11 August 2021)
* https://www.boost.org/development/index.html
== Release Notes ==
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
https://fedoraproject.org/wiki/Changes/CurlMinimal_as_Default
== Summary ==
`libcurl-minimal` and `curl-minimal` will be installed by default
instead of `libcurl` and `curl`.
The "minimal" variants provide only a subset of protocols (HTTP, HTTPS, FTP).
The full versions can be explicitly requested as `libcurl-full` and `curl-full`.
== Owner ==
* Name: [[User:Zbyszek| Zbigniew Jędrzejewski-Szmek]]
* Email: zbyszek at in.waw.pl
* Name: [[User:Kdudka| Kamil Dudka]]
* Email: kdudka at redhat.com
== Detailed Description ==
The `curl` package provides two sets of subpackages: `curl`+`libcurl`
and `curl-minimal`+`libcurl+minimal`.
`curl-minimal`+`libcurl-minimal` are compiled with various
semi-obsolete protocols and infrequently-used features disabled:
DICT, GOPHER, IMAP, LDAP, LDAPS, MQTT, NTLM, POP3, RTSP, SMB, SMTP,
SFTP, SCP, TELNET, TFTP, brotli compression, IDN2 names.
(Both variants support HTTP, HTTPS, and FTP.)
`curl-minimal` has `Provides:curl` and `libcurl-minimal` has `Provides:libcurl`.
This means that both sets can be used to satisfy a dependency on
`curl` or `libcurl`.
`curl` has the virtual `Provides:curl-full` and `libcurl` has the
virtual `Provides:libcurl-full`.
The user or another package can explicitly pull in the full variants,
e.g. with `dnf install curl-full`
or `Requires: libcurl-full`.
With this change, `Suggests: libcurl-minimal` or `Suggests:
curl-minimal` will be added to a few packages
that already have a dependency on `libcurl` or `curl`.
Currently, doing this for `systemd` and `rpm` is planned.
Effectively, `dnf` will install the minimal variants, unless another
package has a stronger dependency on the full variants.
== Benefit to Fedora ==
There are two separate motivations for this.
Those infrequently used protocols are less tested than the common ones
and are a source of security bugs.
Most users are not using those protocols anyway, so disabling them
reduces the bug and attack surface.
(In fact, many applications already call `curl_easy_setopt(c,
CURLOPT_PROTOCOLS, …)` to internally
limit what protocols are supported. So even if `libcurl` is swapped
for `libcurl-minimal` for many
uses this will not be a difference.)
The packages for the minimal variants are smaller:
a trivial installation with `curl-minimal`+`libcurl+minimal` is 18 MB
download, 57 MB installed size, 50 packages;
the same with `curl-full` and `libcurl-full` is 21 MB download, 65
installed size, 62 packages.
Thus we save 8 MB, reducing the initial size by 12%.
== Scope ==
* Proposal owners:
Create pull requests to add `Suggests: curl-minimal` or `Suggests:
libcurl-minimal` as appropriate
to packages which already require `curl` or `libcurl`: `rpm` and `systemd`.
This means that any installation (which should be most of them) will
get the minimal variants.
* Other developers:
For packages that use the full variants: add `Recommends: curl-full`
or `Recommends: libcurl-full` or
`Requires: curl-full` or `Requires: libcurl-full` as appropriate.
* Release engineering:
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with Objectives:
== Upgrade/compatibility impact ==
Users who use curl or another application which uses libcurl with the
removed protocols will lose support for those protocols. They will
need to explicitly install the full variants.
== How To Test ==
`dnf swap curl curl-minimal` or `dnf swap libcurl libcurl-minimal` and
check that `curl` and other applications using `libcurl` still work.
== User Experience ==
This should be not be noticed by users, except as noted above in
Upgrade/compatibility impact.
== Dependencies ==
== Contingency Plan ==
Remove the additions of Suggests, or even add explicit Recommends or Requires.
* Contingency deadline: any time, possibly even after the final release
* Blocks release? No
== Documentation ==
This page should be enough.
== Release Notes ==
`curl-minimal` and `libcurl-minimal` are installed by default. The
support for various obsolete protocols is unavailable by default
through curl (DICT, GOPHER, IMAP, LDAP, LDAPS, MQTT, NTLM, POP3, RTSP,
SMB, SMTP, SFTP, SCP, TELNET, TFTP, brotli compression, IDN2 names).
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
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 1 week, i.e. March 1st 2022.
Since this is after the Beta Freeze,
I will skip retiring components with depending packages.
Such components (if any) 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…
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/ftbf…
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
ecolier-court-fonts frixxon, nim
gfs-ambrosia-fonts frixxon, 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-fonts nim
gfs-gazis-fonts nim
gfs-goschen-fonts nim
gfs-ignacio-fonts nim
gfs-jackson-fonts nim
gfs-neohellenic-fonts nim
gfs-neohellenic-math-fonts nim
gfs-nicefore-fonts nim
gfs-olga-fonts nim
gfs-orpheus-classic-fonts nim
gfs-orpheus-fonts nim
gfs-orpheus-sans-fonts nim
gfs-philostratos-fonts nim
gfs-porson-fonts nim
gfs-pyrsos-fonts nim
gfs-solomos-fonts nim
gfs-theokritos-fonts nim
ht-alegreya-sans-fonts nim
impallari-dancing-script-fonts nim
intel-clear-sans-fonts nim
kemie-bellota-fonts nim
libicu65 pwalter
ndiscover-exo-2-fonts nim
rubygem-cucumber-rails orphan
rubygem-sup dcallagh, jaruga, ruby-packagers-sig, shreyankg
sil-alkalami-fonts nim
sil-andika-compact-fonts nim
sil-andika-fonts nim
sil-andika-new-basic-fonts nim
sil-annapurna-fonts nim
sil-apparatus-fonts nim
sil-awami-nastaliq-fonts nim
sil-charis-compact-fonts nim
sil-dai-banna-fonts nim
sil-ezra-fonts nim
sil-gentium-plus-compact-fonts nim
sil-harmattan-fonts nim
sil-mondulkiri-extra-fonts nim
sil-mondulkiri-fonts nim
sil-namdhinggo-fonts nim
sil-shimenkan-fonts nim
sil-sophia-nubian-fonts nim
sil-tagmukay-fonts nim
sil-tai-heritage-pro-fonts nim
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-fonts nim
weiweihuanghuang-work-sans-fonts nim
yanone-kaffeesatz-fonts nim
All listed packages are leaf packages, nothing depends on them.
Affected (co)maintainers
dcallagh: rubygem-sup
frixxon: adf-tribun-fonts, ecolier-court-fonts, gfs-ambrosia-fonts
jaruga: rubygem-sup
nim: sil-namdhinggo-fonts, yanone-kaffeesatz-fonts, gfs-decker-fonts,
gfs-didot-fonts, gfs-bodoni-fonts, impallari-dancing-script-fonts,
gfs-didot-display-fonts, typesetit-great-vibes-fonts, sil-charis-compact-fonts,
sil-tagmukay-fonts, uswds-public-sans-fonts, weiweihuanghuang-work-sans-fonts,
ecolier-court-fonts, gfs-solomos-fonts, gfs-jackson-fonts,
catharsis-cormorant-fonts, gfs-neohellenic-fonts, sil-annapurna-fonts,
gfs-neohellenic-math-fonts, sil-andika-new-basic-fonts, gfs-eustace-fonts,
adf-tribun-fonts, gfs-fleischman-fonts, sil-awami-nastaliq-fonts,
sil-dai-banna-fonts, sil-mondulkiri-fonts, vernnobile-nunito-fonts,
gfs-theokritos-fonts, ndiscover-exo-2-fonts, symbian-m-yuppy-gb-fonts,
sil-andika-fonts, gfs-goschen-fonts, ht-alegreya-sans-fonts, gfs-olga-fonts,
gfs-complutum-fonts, gfs-artemisia-fonts, gfs-orpheus-sans-fonts,
gfs-ambrosia-fonts, sil-shimenkan-fonts, wagesreiter-patrick-hand-fonts,
intel-clear-sans-fonts, sil-apparatus-fonts, sil-mondulkiri-extra-fonts,
gfs-garaldus-fonts, vernnobile-oswald-fonts, sil-harmattan-fonts,
gfs-orpheus-classic-fonts, gfs-bodoni-classic-fonts, sil-sophia-nubian-fonts,
kemie-bellota-fonts, sil-tai-heritage-pro-fonts, gfs-pyrsos-fonts,
gfs-baskerville-fonts, sil-andika-compact-fonts, gfs-porson-fonts,
gfs-orpheus-fonts, gfs-gazis-fonts, gfs-philostratos-fonts, gfs-nicefore-fonts,
vernnobile-muli-fonts, gfs-galatea-fonts, gfs-didot-classic-fonts,
sil-gentium-plus-compact-fonts, sil-ezra-fonts, sil-alkalami-fonts,
gfs-ignacio-fonts
pwalter: libicu65
ruby-packagers-sig: rubygem-sup
shreyankg: rubygem-sup
ttomecek: tmux-top
https://fedoraproject.org/wiki/Changes/Silverblue_Kinoite_readonly_sysroot
== Summary ==
This change is about enabling an opt-in ostree feature that re-mounts
`/sysroot` as read only to avoid accidental changes.
Users and administrators are not expected to directly interact with
the content available there and should instead use the interface
offered by rpm-ostree, GNOME Software or (soon) Plasma Discover to
manage their system.
== Owner ==
* Name: [[User:Siosm| Timothée Ravier]], [[User:Tpopela| Tomáš
Popela]], [[User:jkonecny| Jiří Konečný]]
* Email: siosm(a)fedoraproject.org, tpopela(a)fedoraproject.org, jkonecny(a)redhat.com
* FESCo shepherd: [[User:Ngompa| Neal Gompa]] ngompa(a)fedoraproject.org
== Detailed Description ==
On rpm-ostree based systems, the real root (the root directory of the
root partition on the disk) is mounted under the `/sysroot` path. By
default it contains the state of the system (the content of `var` and
`etc`) as well as the system versions themselves (each versioned copy
of `/usr`) in the ostree repository (`/ostree/repo`).
This change is about enabling an opt-in ostree feature that re-mounts
`/sysroot` as read only to avoid accidental changes.
Users and administrators are not expected to directly interact with
the content available there and should instead use the interface
offered by rpm-ostree, GNOME Software or (soon) Plasma Discover to
manage their system.
Example of issue: https://github.com/fedora-silverblue/issue-tracker/issues/232
This change replicates for Fedora Silverblue/Kinoite what has been
done in Fedora CoreOS in a previous release.
== Feedback ==
None so far.
== Benefit to Fedora ==
This will make Fedora Silverblue/Kinoite more robust to accidental
damage from users.
== Scope ==
* Proposal owners:
** Work on the changes requires for new installations (potentially
Anaconda configuration changes) and support for in place updates for
existing installations (requires a two step process).
* Other developers:
** Potential Anaconda changes required.
* Release engineering: N/A
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with Objectives: N/A
== Upgrade/compatibility impact ==
We will create a systemd unit that perform the updates in place for
existing systems. This will require a two step process (changing the
existing kernel arguments, and then enabling the ostree feature). Once
the feature is enabled, user won't be able to rollback to previous
deployments where the kernel argument is not set. We will have to
clearly document that in the documentation for easier troubleshooting.
== How To Test ==
Only try the following if you are confortable debugging an un-bootable
system and have made backups!
`$ sudo rpm-ostree kargs --append-if-missing=rw`
`$ sudo ostree config --repo=/sysroot/ostree/repo set "sysroot.readonly" "true"`
`$ sudo systemctl reboot`
Note that you can not "rollback" to the previous deployment to undo
this change. You will have to boot into a Live ISO and edit the config
file in the ostree repo to remove this config option.
== User Experience ==
There should be no visible change in user experience.
== Dependencies ==
Requires changes in Anaconda (maybe just config?) to set default kargs
and property on ostree repo for new installations.
== Contingency Plan ==
Revert the change before the release.
== Documentation ==
N/A (not a System Wide Change)
== Release Notes ==
TODO
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
https://fedoraproject.org/wiki/Changes/polkit_recommends_pkla_pkexec
== Summary ==
Split `pkexec` from the polkit package and make it a recommended only
sub-package. Similarly, make the polkit-pkla-compat package a
recommended package too. This will enable users and desktop no longer
relying on those features to avoid installing them.
== Owner ==
* Name: [[User:Siosm| Timothée Ravier]], Jan Rybar
* Email: siosm(a)fedoraproject.org, jrybar(a)redhat.com
== Detailed Description ==
`pkexec` and `pkla-compat`
([https://src.fedoraproject.org/rpms/polkit-pkla-compat package]) are
legacy tools that are no longer needed on a desktop and increase the
attack surface as they are SetUID binaries (`pkexec`) or not
maintained anymore (`pkla-compat`).
This change will thus split `pkexec` from the polkit package and make
it a recommended only sub-package. Similarly, it will make the
polkit-pkla-compat package a recommended package too. This will enable
users and desktop no longer relying on those features to avoid
installing them. Users that still need those features will easily be
able to install them.
See in progress PR: https://src.fedoraproject.org/rpms/polkit/pull-request/2
== Feedback ==
Related discussion in
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org…
See in progress PR: https://src.fedoraproject.org/rpms/polkit/pull-request/2
== Benefit to Fedora ==
Increased security, less legacy software installed by default, moving
to a more secure desktop by default.
== Scope ==
* Proposal owners:
** Test as many desktop environments as possible and add the new
dependencies for the packages requiring either polkit-pkla-compat
rules support or pkexec.
* Other developers:
** Test as many desktop environments as possible and add the new
dependencies for the packages requiring either polkit-pkla-compat
rules support or pkexec.
* Release engineering:
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A
* Alignment with Objectives:
== Upgrade/compatibility impact ==
Nothing should happen during upgrades for existing systems as the
packages are still available and will be kept as is and the new
polkit-pkexec package will be installed for users not deselecting
recommends.
Only new installations that will not have those packages will be
impacted and the risk of security issues with the pkla rules removal
is low.
== How To Test ==
1. Install the polkit package from
https://copr.fedorainfracloud.org/coprs/siosm/polkit/
2. Remove the polkit-pkexec sub-package and polkit-pkla-compat package
3. Ensure that your applications and desktop environment are still
working as intended. Focus on applications that require privileges.
== User Experience ==
N/A
== Dependencies ==
N/A
== Contingency Plan ==
Revert the change.
== Documentation ==
N/A (not a System Wide Change)
== Release Notes ==
TODO
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
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 (if any) 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…
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/ftbf…
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
ecolier-court-fonts frixxon, nim
gfs-ambrosia-fonts frixxon, 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-fonts nim
gfs-gazis-fonts nim
gfs-goschen-fonts nim
gfs-ignacio-fonts nim
gfs-jackson-fonts nim
gfs-neohellenic-fonts nim
gfs-neohellenic-math-fonts nim
gfs-nicefore-fonts nim
gfs-olga-fonts nim
gfs-orpheus-classic-fonts nim
gfs-orpheus-fonts nim
gfs-orpheus-sans-fonts nim
gfs-philostratos-fonts nim
gfs-porson-fonts nim
gfs-pyrsos-fonts nim
gfs-solomos-fonts nim
gfs-theokritos-fonts nim
ht-alegreya-sans-fonts nim
impallari-dancing-script-fonts nim
intel-clear-sans-fonts nim
jetbrains-mono-fonts nim
kemie-bellota-fonts nim
libicu65 pwalter
ndiscover-exo-2-fonts nim
rubygem-cucumber-rails mmorsi, vondruch
rubygem-sup dcallagh, jaruga, ruby-packagers-sig, shreyankg
sil-alkalami-fonts nim
sil-andika-compact-fonts nim
sil-andika-fonts nim
sil-andika-new-basic-fonts nim
sil-annapurna-fonts nim
sil-apparatus-fonts nim
sil-awami-nastaliq-fonts nim
sil-charis-compact-fonts nim
sil-dai-banna-fonts nim
sil-ezra-fonts nim
sil-gentium-plus-compact-fonts nim
sil-harmattan-fonts nim
sil-mondulkiri-extra-fonts nim
sil-mondulkiri-fonts nim
sil-namdhinggo-fonts nim
sil-shimenkan-fonts nim
sil-sophia-nubian-fonts nim
sil-tagmukay-fonts nim
sil-tai-heritage-pro-fonts nim
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-fonts nim
weiweihuanghuang-work-sans-fonts nim
yanone-kaffeesatz-fonts nim
All listed packages are leaf packages, nothing depends on them.
Affected (co)maintainers
dcallagh: rubygem-sup
frixxon: adf-tribun-fonts, ecolier-court-fonts, gfs-ambrosia-fonts
jaruga: rubygem-sup
mmorsi: rubygem-cucumber-rails
nim: ecolier-court-fonts, gfs-orpheus-classic-fonts, sil-tagmukay-fonts,
gfs-didot-fonts, gfs-nicefore-fonts, gfs-eustace-fonts, gfs-fleischman-fonts,
gfs-garaldus-fonts, gfs-solomos-fonts, sil-apparatus-fonts, gfs-ignacio-fonts,
sil-mondulkiri-fonts, sil-charis-compact-fonts, gfs-neohellenic-fonts,
adf-tribun-fonts, yanone-kaffeesatz-fonts, sil-alkalami-fonts,
sil-shimenkan-fonts, sil-andika-fonts, gfs-galatea-fonts, gfs-olga-fonts,
vernnobile-muli-fonts, gfs-baskerville-fonts, sil-sophia-nubian-fonts,
typesetit-great-vibes-fonts, intel-clear-sans-fonts, gfs-porson-fonts,
jetbrains-mono-fonts, sil-andika-new-basic-fonts, sil-ezra-fonts,
gfs-gazis-fonts, sil-mondulkiri-extra-fonts, gfs-complutum-fonts,
sil-awami-nastaliq-fonts, gfs-orpheus-fonts, sil-dai-banna-fonts,
gfs-ambrosia-fonts, vernnobile-oswald-fonts, gfs-pyrsos-fonts,
ht-alegreya-sans-fonts, kemie-bellota-fonts, sil-gentium-plus-compact-fonts,
uswds-public-sans-fonts, sil-harmattan-fonts, gfs-decker-fonts,
ndiscover-exo-2-fonts, sil-andika-compact-fonts,
wagesreiter-patrick-hand-fonts, gfs-bodoni-classic-fonts, gfs-goschen-fonts,
gfs-jackson-fonts, catharsis-cormorant-fonts, gfs-didot-display-fonts,
gfs-neohellenic-math-fonts, impallari-dancing-script-fonts,
vernnobile-nunito-fonts, gfs-theokritos-fonts, gfs-bodoni-fonts,
sil-tai-heritage-pro-fonts, gfs-artemisia-fonts, gfs-orpheus-sans-fonts,
gfs-philostratos-fonts, sil-annapurna-fonts, weiweihuanghuang-work-sans-fonts,
symbian-m-yuppy-gb-fonts, gfs-didot-classic-fonts, sil-namdhinggo-fonts
pwalter: libicu65
ruby-packagers-sig: rubygem-sup
shreyankg: rubygem-sup
ttomecek: tmux-top
vondruch: rubygem-cucumber-rails
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
Greetings all,
Apologies for the late notice on this message. I previously sent it to the
infrastructure list and should have sent it here at the same time.
We will be doing a mass update/reboot this week. We haven't done
one in a couple of months and would like to get all up to date before the
upcoming beta freeze.
Rough plan:
* Monday (2022-02-14): *.stg.iad2.fedoraproject.org. update/reboot all
staging hosts. We need to watch for the openshift clusters and make sure
they come back up correctly.
* Tuesday (2022-02-15): any non outage causing hosts. This would include
proxies and their virthosts since we can take them out of dns. Also
might include some virthosts in iad2 as long as all the guests on them
have counterparts on other virthosts to take the load.
* *Wed (2022-02-16): Outage starting at 21UTC.*
Everything else left that we haven't done yet we do here.
Outage ticket: https://pagure.io/fedora-infrastructure/issue/10536
This is mostly on Kevin and I, since it needs sysadmin-main, but our
SOP/doc on this is horribly out of date if someone(s) would like to work
on updating it. (
https://docs.fedoraproject.org/en-US/infra/sysadmin_guide/massupgrade/ )
Also there's talking to users during the outage and testing things after we
are done.
Thanks,
Mark
https://fedoraproject.org/wiki/Changes/F37MingwEnvToolchainUpdate
== Summary ==
Update the MinGW toolchain to the latest upstream stable releases.
== Owner ==
* Name: [[User:smani|Sandro Mani]]
* Email: manisandro(a)gmail.com
== Detailed Description ==
The following packages will be updated
* mingw-gcc to version 12.x
* mingw-binutils to version 2.38
== Benefit to Fedora ==
Ship the latest available GNU toolchain for MinGW.
== Scope ==
* Proposal owners:
The above mentioned packages will be updated. Build failures following
the mass rebuild will be inspected.
* Other developers:
Help with build failures may be requested.
<!-- What work do other developers have to accomplish to complete the
feature in time for release? Is it a large change affecting many
parts of the distribution or is it a very isolated change? What are
those changes?-->
* Release engineering: Impact check [https://pagure.io/releng/issue/10637]
* Release engineering: Mass rebuild requested
* Policies and guidelines: No policies need to be changed
== Upgrade/compatibility impact ==
No impact
== How To Test ==
Update the system once the updated packages land, look out for new
build failures etc.
== User Experience ==
The features of the newest GNU Toolchain will be available to MinGW users.
== 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 the mingw-gcc-12 and mingw-binutils-2.38.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
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…
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/ftbf…
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
ecolier-court-fonts frixxon, nim
gfs-ambrosia-fonts frixxon, 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-fonts nim
gfs-gazis-fonts nim
gfs-goschen-fonts nim
gfs-ignacio-fonts nim
gfs-jackson-fonts nim
gfs-neohellenic-fonts nim
gfs-neohellenic-math-fonts nim
gfs-nicefore-fonts nim
gfs-olga-fonts nim
gfs-orpheus-classic-fonts nim
gfs-orpheus-fonts nim
gfs-orpheus-sans-fonts nim
gfs-philostratos-fonts nim
gfs-porson-fonts nim
gfs-pyrsos-fonts nim
gfs-solomos-fonts nim
gfs-theokritos-fonts nim
ht-alegreya-sans-fonts nim
impallari-dancing-script-fonts nim
intel-clear-sans-fonts nim
jetbrains-mono-fonts nim
kemie-bellota-fonts nim
libicu65 pwalter
ndiscover-exo-2-fonts nim
rubygem-cucumber-rails mmorsi, vondruch
rubygem-selenium-webdriver mmorsi, ruby-packagers-sig, vondruch
rubygem-sup dcallagh, jaruga, ruby-packagers-sig, shreyankg
sil-alkalami-fonts nim
sil-andika-compact-fonts nim
sil-andika-fonts nim
sil-andika-new-basic-fonts nim
sil-annapurna-fonts nim
sil-apparatus-fonts nim
sil-awami-nastaliq-fonts nim
sil-charis-compact-fonts nim
sil-dai-banna-fonts nim
sil-ezra-fonts nim
sil-gentium-plus-compact-fonts nim
sil-harmattan-fonts nim
sil-mondulkiri-extra-fonts nim
sil-mondulkiri-fonts nim
sil-namdhinggo-fonts nim
sil-shimenkan-fonts nim
sil-sophia-nubian-fonts nim
sil-tagmukay-fonts nim
sil-tai-heritage-pro-fonts nim
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-fonts nim
weiweihuanghuang-work-sans-fonts nim
yanone-kaffeesatz-fonts nim
The following packages require above mentioned packages:
Depending on: rubygem-selenium-webdriver (21)
rubygem-actionpack (maintained by: jaruga, jstribny, kanarip, mmorsi, pvalena,
ruby-packagers-sig, sseago, vondruch)
rubygem-actionpack-1:6.1.4.1-2.fc36.src requires rubygem(selenium-webdriver)
= 3.142.7
rubygem-actiontext (maintained by: pvalena)
rubygem-actiontext-6.1.4.1-2.fc36.src requires rubygem(selenium-webdriver) =
3.142.7
rubygem-capybara (maintained by: mmorsi, ruby-packagers-sig, vondruch)
rubygem-capybara-3.34.0-5.fc36.src requires rubygem(selenium-webdriver) = 3.142.7
rubygem-rspec-rails (maintained by: clalance, vondruch)
rubygem-rspec-rails-4.0.2-3.fc36.src requires rubygem(selenium-webdriver) =
3.142.7
rubygem-actioncable (maintained by: pvalena, ruby-packagers-sig, vondruch)
rubygem-actioncable-6.1.4.1-1.fc36.noarch requires rubygem(actionpack) = 6.1.4.1
rubygem-actioncable-6.1.4.1-1.fc36.src requires rubygem(actionpack) = 6.1.4.1
rubygem-actionmailbox (maintained by: pvalena)
rubygem-actionmailbox-6.1.4.1-2.fc36.noarch requires rubygem(actionpack) =
6.1.4.1
rubygem-actionmailer (maintained by: jstribny, kanarip, mmorsi, pvalena,
sseago, vondruch)
rubygem-actionmailer-1:6.1.4.1-2.fc36.noarch requires rubygem(actionpack) =
6.1.4.1
rubygem-actionmailer-1:6.1.4.1-2.fc36.src requires rubygem(actionpack) = 6.1.4.1
rubygem-actionview (maintained by: jaruga, pvalena, ruby-packagers-sig)
rubygem-actionview-6.1.4.1-2.fc36.src requires rubygem(actionpack) = 6.1.4.1
rubygem-activerecord (maintained by: jaruga, kanarip, mmorsi, mtasaka,
pvalena, ruby-packagers-sig, sseago, vondruch)
rubygem-activerecord-1:6.1.4.1-2.fc36.src requires rubygem(actionpack) = 6.1.4.1
rubygem-activestorage (maintained by: ruby-packagers-sig, vondruch)
rubygem-activestorage-6.1.4.1-2.fc36.noarch requires rubygem(actionpack) =
6.1.4.1
rubygem-activestorage-6.1.4.1-2.fc36.src requires rubygem(actionpack) = 6.1.4.1
rubygem-pundit (maintained by: pvalena)
rubygem-pundit-2.1.0-4.fc36.src requires rubygem(actionpack) = 6.1.4.1
rubygem-rails (maintained by: jstribny, kanarip, mmorsi, mtasaka, pvalena,
ruby-packagers-sig, sseago, tdawson, vondruch)
rubygem-rails-1:6.1.4.1-2.fc36.noarch requires rubygem(actionpack) = 6.1.4.1
rubygem-rails-controller-testing (maintained by: valtri)
rubygem-rails-controller-testing-1.0.5-5.fc36.noarch requires
rubygem(actionpack) = 6.1.4.1
rubygem-railties (maintained by: mmorsi, pvalena, vondruch)
rubygem-railties-6.1.4.1-2.fc36.noarch requires rubygem(actionpack) = 6.1.4.1
rubygem-railties-6.1.4.1-2.fc36.src requires rubygem(actionpack) = 6.1.4.1
rubygem-sprockets-rails (maintained by: jaruga, pvalena, ruby-packagers-sig)
rubygem-sprockets-rails-3.2.2-2.fc34.noarch requires rubygem(actionpack) =
6.1.4.1
rubygem-simplecov (maintained by: tdawson)
rubygem-simplecov-0.13.0-12.fc36.src requires rubygem(capybara) = 3.34.0
rubygem-ammeter (maintained by: jstribny, ruby-packagers-sig, vondruch)
rubygem-ammeter-1.1.5-2.fc36.noarch requires rubygem(rspec-rails) = 4.0.2
rubygem-ammeter-1.1.5-2.fc36.src requires rubygem(rspec-rails) = 4.0.2
rubygem-apipie-rails (maintained by: ruby-packagers-sig, vondruch)
rubygem-apipie-rails-0.5.18-5.fc36.src requires rubygem(rspec-rails) = 4.0.2
rubygem-shoulda-matchers (maintained by: vondruch)
rubygem-shoulda-matchers-4.5.1-3.fc36.src requires rubygem(rspec-rails) = 4.0.2
rubygem-rails-deprecated_sanitizer (maintained by: vondruch)
rubygem-rails-deprecated_sanitizer-1.0.4-3.fc36.src requires
rubygem(actionview) = 6.1.4.1
rubygem-web-console (maintained by: jaruga, ruby-packagers-sig, vondruch)
rubygem-web-console-4.1.0-4.fc36.noarch requires rubygem(actionview) = 6.1.4.1
Too many dependencies for rubygem-selenium-webdriver, not all listed here
Affected (co)maintainers (either directly or via packages' dependencies):
clalance: rubygem-selenium-webdriver
dcallagh: rubygem-sup
frixxon: adf-tribun-fonts, ecolier-court-fonts, gfs-ambrosia-fonts
jaruga: rubygem-sup, rubygem-selenium-webdriver
jstribny: rubygem-selenium-webdriver
kanarip: rubygem-selenium-webdriver
mmorsi: rubygem-cucumber-rails, rubygem-selenium-webdriver
mtasaka: rubygem-selenium-webdriver
nim: sil-andika-new-basic-fonts, sil-harmattan-fonts, ecolier-court-fonts,
intel-clear-sans-fonts, gfs-ignacio-fonts, gfs-pyrsos-fonts, sil-andika-fonts,
typesetit-great-vibes-fonts, gfs-didot-classic-fonts, sil-awami-nastaliq-fonts,
gfs-gazis-fonts, kemie-bellota-fonts, gfs-baskerville-fonts,
gfs-complutum-fonts, catharsis-cormorant-fonts, gfs-olga-fonts,
sil-sophia-nubian-fonts, gfs-orpheus-fonts, ht-alegreya-sans-fonts,
gfs-neohellenic-math-fonts, gfs-garaldus-fonts, sil-gentium-plus-compact-fonts,
gfs-philostratos-fonts, uswds-public-sans-fonts, jetbrains-mono-fonts,
vernnobile-oswald-fonts, sil-annapurna-fonts, sil-ezra-fonts,
gfs-ambrosia-fonts, symbian-m-yuppy-gb-fonts, gfs-galatea-fonts,
gfs-orpheus-sans-fonts, gfs-goschen-fonts, sil-apparatus-fonts,
sil-tagmukay-fonts, yanone-kaffeesatz-fonts, sil-namdhinggo-fonts,
gfs-nicefore-fonts, sil-shimenkan-fonts, gfs-eustace-fonts,
impallari-dancing-script-fonts, gfs-decker-fonts,
wagesreiter-patrick-hand-fonts, gfs-bodoni-classic-fonts,
gfs-neohellenic-fonts, sil-mondulkiri-extra-fonts, vernnobile-muli-fonts,
weiweihuanghuang-work-sans-fonts, sil-andika-compact-fonts,
sil-mondulkiri-fonts, gfs-fleischman-fonts, gfs-porson-fonts, adf-tribun-fonts,
sil-tai-heritage-pro-fonts, gfs-theokritos-fonts, gfs-bodoni-fonts,
gfs-didot-display-fonts, sil-alkalami-fonts, gfs-orpheus-classic-fonts,
vernnobile-nunito-fonts, ndiscover-exo-2-fonts, sil-charis-compact-fonts,
gfs-artemisia-fonts, gfs-jackson-fonts, gfs-didot-fonts, gfs-solomos-fonts,
sil-dai-banna-fonts
pvalena: rubygem-selenium-webdriver
pwalter: libicu65
ruby-packagers-sig: rubygem-sup, rubygem-selenium-webdriver
shreyankg: rubygem-sup
sseago: rubygem-selenium-webdriver
tdawson: rubygem-selenium-webdriver
ttomecek: tmux-top
valtri: rubygem-selenium-webdriver
vondruch: rubygem-cucumber-rails, rubygem-selenium-webdriver
In accordance with FESCo policy[1], the following provenpackagers will
be submitted for removal in two weeks based on a lack of Koji builds
submitted in the last six months. If you received this directly, you
can reply off-list to indicate you should still be in the
provenpackager group.
Note that removal from this group is not a "punishment" or a lack of
appreciation for the work you have done. The intent of the process is
to ensure contributors with distro-wide package privileges are still
active and responsive. This process is done regularly at the branch
point in each release.
[1] https://docs.fedoraproject.org/en-US/fesco/Provenpackager_policy/#_maintain…
Checked 148 provenpackagers
The following 23 provenpackagers have not submitted a Koji build since
at least 2021-08-04 00:00:00:
akurtakov
codeblock
iarnell
ilianaw
jsmith
jwilson
kanarip
karsten
law
laxathom
lutter
mcepl
nhorman
notting
oliver
pmachata
psabata
ruben
steve
tflink
till
tmraz
wtogami
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
Hi All,
Fedora 36 has now been branched, please be sure to do a git pull
--rebase to pick up the new branch, as an additional reminder
rawhide/f36 has been completely isolated from previous releases, so
this means that anything you do for f36 you also have to do in the
rawhide branch and do a build there. There will be a Fedora 36 compose
and it'll appear in
http://dl.fedoraproject.org/pub/fedora/linux/development/36/ once
complete. Please be sure to check it out. Bodhi is currently not
active for Fedora 36, it will be enabled in a couple of weeks when we
hit Beta change freeze point in the Fedora 36 schedule[1].
Two things to remember:
1. The modules will be built for a new platform:f37
2. The signing of RPMs is not done yet with the new f37 key.
3. F36/branched release is frozen right now until we get a successful
compose, expect that your f36 builds won't be available immediately.
Thanks for understanding.
[1] https://fedorapeople.org/groups/schedule/f-36/f-36-key-tasks.html
--
Tomas Hrcka
role: CPE Team - Senior Software Engineer
fas: humaton
libera.CHAT: jednorozec
https://fedoraproject.org/wiki/Changes/F37MingwOpenSSL3
== Summary ==
Update OpenSSL for MinGW to version 3.x
== Owner ==
* Name: [[User:smani|Sandro Mani]]
* Email: manisandro(a)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
-------- Forwarded Message --------
Subject: [Bugzilla-announce-list] Action Required: Bugzilla - API
Authentication changes
Date: Tue, 1 Feb 2022 12:28:13 +1000
From: Jeff Fearn <jfearn(a)redhat.com>
To: bugzilla-announce-list(a)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-owner(a)redhat.com
The Red Hat Bugzilla Team.
1: https://bugzilla.redhat.com/docs/en/html/api/core/v1/general.html#authentic…