As a reminder, F38 Changes should be testably complete by Tuesday 7
February. Change owners can indicate this by setting the Bugzilla
tracker to the MODIFIED state. (If it is 100% complete, you can set
the tracker it ON_QA).
In addition, F38 branches from Rawhide on 7 February. At that point,
Rawhide begins development of F39.
More schedule details are available at
https://fedorapeople.org/groups/schedule/f-38/f-38-key-tasks.html
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
NOTE: As explained by the owners in the Feedback section below, this
proposal was submitted after the deadline because the impact of the
package update proved to be broader than anticipated.
https://fedoraproject.org/wiki/Changes/Packaging_22%2B
This document represents a proposed Change. As part of the Changes
process, proposals are publicly announced in order to receive
community feedback. This proposal will only be implemented if approved
by the Fedora Engineering Steering Committee.
== Summary ==
Update to a new upstream release of python-packaging contains a
breaking change. Since version 22+ upstream removed support for
[https://github.com/pypa/packaging/pull/407 LegacySpecifier and
LegacyVersion] some packages will break. This is a breaking change and
projects are encouraged to use versions adherent to
[https://peps.python.org/pep-0440/ PEP 440].
Note: Currently, we plan to update to 23.0, but this can be updated
even further. The change proposal explicitly mentions version 22+
because that version removed support for LegacyVersions and legacy
version specifiers.
== Owner ==
* Name: [[User:thrnciar| Tomáš Hrnčiar]]
* Email: thrnciar(a)redhat.com
* Name: [[User:mhroncok| Miro Hrončok]]
* Email: mhroncok(a)redhat.com
== Detailed Description ==
>>> # before 22.0
>>> packaging.version.parse("This is a completely random string")
<LegacyVersion('This is a completely random string')>
>>> # after 22.0
>>> packaging.version.parse("This is a completely random string")
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "[...]/.venv/lib/python3.10/site-packages/packaging/version.py",
line 52, in parse
return Version(version)
File "[...]/.venv/lib/python3.10/site-packages/packaging/version.py",
line 197, in __init__
raise InvalidVersion(f"Invalid version: '{version}'")
packaging.version.InvalidVersion: Invalid version: 'This is a
completely random string'
This "feature" has been deprecated for nearly two years now.
PyPI has not permitted uploading packages with invalid versions for
even more years. The latest versions of pip should be
rejecting/erroring out on wheels with such versions as well. The
stricter metadata validation helps pip's dependency resolver's logic,
along with helping the broader ecology avoid needing to deal with
outside-of-standard tooling/behaviours.
Possible failures caused by upgraded python-packaging:
* pinned version of python-packaging
**cekit - https://bugzilla.redhat.com/show_bug.cgi?id=2162433
**python-limits -
https://src.fedoraproject.org/rpms/python-limits/pull-request/5
* tests containing unsupported versions need to be adjusted
**copr-backend - https://bugzilla.redhat.com/show_bug.cgi?id=2162436
* some packages provide incompatible versions and
python-rpm-generators are unable to parse them. See PRs links below
for inspiration on how to fix them.
**obs-service-set_version
**pcs
**pyodbc
**python-btchip
**python-dipy
**python-dropbox
**python-haversion -
https://src.fedoraproject.org/rpms/python-haversion/pull-request/1
**python-httplib2 - uses pyparsing in tests but does not BuildRequire
it directly
**python-lacrosse -
https://src.fedoraproject.org/rpms/python-lacrosse/pull-request/1
**python-pdir2 - the sed in `%prep` needs to be adjusted not to create
invalid `>=4.2.*` requirements
**python-pvc
**python-pytest-httpx
See also https://discuss.python.org/t/22782/19 for the exact errors of
most of the listed packages.
* unknown
**python-google-cloud-bigquery - package does not build in rawhide
=== How to deal with failures in Python RPM dependency generators ===
packaging is used in the Python RPM dependency generators (for
`python3dist()` and `python3.11dist()` Provides, Requires and
BuildRequires).
When the packaged software has now invalid versions or comparators,
you might need to fix the package.
Example problem:
packaging.version.InvalidVersion: Invalid version: 'main'
See if the version of the Python package isn't failing to be
determined automatically and provide the missing information, see
https://src.fedoraproject.org/rpms/python-haversion/pull-request/1 or
https://src.fedoraproject.org/rpms/python-lacrosse/pull-request/1 and
https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/#_version_…
Example problem:
packaging.requirements.InvalidRequirement: Expected end or semicolon
(after version specifier)
typing-extensions>=4.2.*
\~\~\~\~\~^
(Backslashes added to the example as a naïve attempt to escape the
dashes form this wiki, ignore them).
Adjust the requirement not to use `.*` in versions when `<`, `<=`,
`>`, or `>=` is used, see https://discuss.python.org/t/22782
== Feedback ==
We are aware that we missed the Change proposal submission deadline,
originally we planned to ship this as a regular package update. While
doing an impact check we identified ~20 affected packages and we
decided to write this Change proposal for better transparency. We
believe there is enough time to complete this Change in time for the
Completion deadline. We are prepared to postpone this Change to Fedora
39 if FESCo decides so.
== Benefit to Fedora ==
Packaging 22+ contains a handwritten parser for parsing requirements
and markers. Thanks to this, packaging has dropped a runtime
dependency on pyparsing and from now on is not depending on any
package on runtime. This will simplify bootstrapping of the next
Python.
== Scope ==
* Proposal owners: update python-packaging to 23.x.x, provide help
* Other developers: report problems to the upstream and backport patch
to the affected packages. The impact can be tested using
[https://copr.fedorainfracloud.org/coprs/thrnciar/python-packaging/packages/
COPR repository] where Packaging 23+ has been built.
* Release engineering: N/A (not needed for this Change)
* 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 ==
== How To Test ==
# Find the package you want to fix in this
[https://copr.fedorainfracloud.org/coprs/thrnciar/python-packaging/packages/
COPR repository] and check the build logs to determine the failure
cause.
# Patch package so Provides() provides correct version.
# When patching the package, you can test it using the same copr
repository where the latest version of python-packaging has been
built.
== User Experience ==
Regular distro users shouldn't notice any change in python-packaging
behaviour, except for packages that use `LegacyVersion` or
`LegacySpecifier`. Such packages will fail with
`packaging.version.InvalidVersion: Invalid version: 'This is a
completely random string'` and should be fixed by their maintainers.
== Dependencies ==
== Contingency Plan ==
* Contingency mechanism: (What to do? Who will do it?) revert the
update and bump epoch
* Contingency deadline: beta freeze
* Blocks release? No
== Documentation ==
https://github.com/pypa/packaging/blob/main/CHANGELOG.rst
== Release Notes ==
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
https://fedoraproject.org/wiki/Changes/IoTSimplifiedInstaller
This document represents a proposed Change. As part of the Changes
process, proposals are publicly announced in order to receive
community feedback. This proposal will only be implemented if approved
by the Fedora Engineering Steering Committee.
== Summary ==
Offer Fedora IoT users a new method to create and deploy customized
Fedora IoT disk images using a new installer called Simplified
Installer.
== Owner ==
* Name: [[User:runcom| Antonio Murdaca]], [[User:pwhalen| Paul Whalen]]
* Email: amurdaca(a)redhat.com, pwhalen(a)fedoraproject.org
== Detailed Description ==
The Fedora IoT Simplified Installer will use coreos-installer to write
an OStree raw image straight to a disk specified in a kernel argument,
without the need for a kickstart or user interaction. This type of
installation is ideal for devices connected at the edge where
connectivity can be slow or intermittent. It offers the ability to
configure the system via osbuild itself, FDO and Ignition.
== Feedback ==
== Benefit to Fedora ==
The addition of the Fedora IoT Simplified Installer will benefit IoT
users by allowing them to create customized disk images for use on
their edge devices. This feature is already available downstream,
adding it to Fedora will once again bring Fedora back to the true
upstream of RHEL for edge and allows testing and adoption of new
functionality like FIDO Device Onboarding.
== Scope ==
* Proposal owners:
** Test building Fedora IoT Simplified Installer with `osbuild-composer`
** Update Fedora IoT documentation with usage instructions.
* Other developers:
* 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 ==
* Not applicable to this change.
== How To Test ==
Testable by installing `osbuild-composer` in Fedora 38 and using the
command line tool or the Cockpit web interface to create a Fedora IoT
Simplified Installer iso to deploy a UEFI enabled edge device.
== User Experience ==
This change will greatly enhance the Fedora IoT user experience by
allowing users to utilize `osbuild-composer` and blueprints to create
customized Fedora IoT deployments and leverage new features like FIDO
Device Onboarding for secure zero touch device onboarding of edge
devices as well as Ignition to configure the device once it starts.
== Dependencies ==
N/A (not a System Wide Change)
== Contingency Plan ==
* Contingency deadline: Beta
* Blocks release? No.
* Blocks product? No.
== Documentation ==
* Usage documentation to be written and included in the
[https://docs.fedoraproject.org/en-US/iot/user-guide/ Fedora IoT user
guide].
== Release Notes ==
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
Hi everybody,
TL;DR; Check if you have correct e-mail in Red Hat Bugzilla Mail field
in Fedora Accounts [0]. Empty mail is also OK.
the Red Hat Bugzilla Email field in Fedora Accounts [0] was till now
ignored by most of the apps.
This was changed now with the latest update to toddlers [1], which
contains most of the syncing scripts that are run automatically in
Fedora Infra including distgit_bugzilla_sync [2], packager_bugzilla_sync
[3] and packagers_without_bugzilla [4] scripts. All these scripts are
using shared methods for working with Fedora Accounts system.
With the addition of scm_request_processor [5] there was a small change
in how the Fedora Accounts mails are handled in regard to Red Hat
Bugzilla mail. This change caused it to first look for Red Hat Bugzilla
Mail and then look at the personnel e-mail associated with the account
if Bugzilla mail is not set.
This unfortunately caused issues for some users that had Red Hat
Bugzilla Mail field set incorrectly. I was the one who did the change
and I actually forgot about it, because it happened at the beginning of
scm_request_processor development cycle and I didn't know it could have
that large impact. So I apologize for any issue this could have caused
for you.
If you are one of the users, who were impacted by this change, you can
fix it by adding correct Red Hat Bugzilla mail to your Fedora Account.
You can do this in Settings->Emails in Fedora Accounts page [0].
We will fix the message that is being sent to packagers without Bugzilla
e-mail to correspond with this change.
On behalf of CPE Team,
Michal
[0] - https://accounts.fedoraproject.org
[1] - https://pagure.io/fedora-infra/toddlers
[2] -
https://pagure.io/fedora-infra/toddlers/blob/main/f/toddlers/plugins/distgi…
[3] -
https://pagure.io/fedora-infra/toddlers/blob/main/f/toddlers/plugins/packag…
[4] -
https://pagure.io/fedora-infra/toddlers/blob/main/f/toddlers/plugins/packag…
[5] -
https://pagure.io/fedora-infra/toddlers/blob/main/f/toddlers/plugins/scm_re…