You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adding a call to pesign-client with the default upstream Fedora signing parameter values.
Those values match what is currently being used by other packages (kernel, grub2, etc.).
They do not define what certificate will be used. Instead, the environment and package
name decide what certificate will be used as follows:
- If this package is being built in the production environment, it will be signed with
ESRP production secure boot certificate.
- If it is being built in the PME staging environment, it will be signed with the ESRP
test secure boot certificate.
- Otherwise, it will be signed with a self-issued certificate.
The reason will be displayed to describe this comment to others. Learn more.
🟡 Changes recommended
The signed EFI payload is still packaged with metadata claiming it cannot support Secure Boot and lacks signed-bootloader Provides, requiring packaging updates that preserve existing dependency compatibility.
The reason will be displayed to describe this comment to others. Learn more.
🟡 Changes recommended
The signing package is absent from the component build configuration, requires an outdated systemd version, and attaches its upgrade scriptlet to the wrong package.
The reason will be displayed to describe this comment to others. Learn more.
🔵 Needs a closer look
The signing package requires unsigned-package version 258 while the tree provides 258.4, making the dependency unresolvable; it also lacks component registration and attaches its bootloader-update scriptlet to a package that is not shipped.
Signing package version mismatches the unsigned RPM capability
specs/s/systemd-boot/systemd-boot.spec:21
With the top-level Version: 258, this requires version(systemd-boot-unsigned)%{_isa} = 258, but specs/s/systemd/systemd.spec:598-599 provides that capability at version 258.4. These versions are not equal, so the signing package cannot resolve this dependency against the unsigned RPM produced by this tree. Set the signing spec's top-level Version to 258.4 in its authoritative source or overlay, then regenerate the rendered spec.
The reason will be displayed to describe this comment to others. Learn more.
🔵 Needs a closer look
The signing package lacks azldev registration and a lock, and its upgrade hook targets a package that is never emitted, so signed bootloader upgrades will not update the ESP.
The reason will be displayed to describe this comment to others. Learn more.
🔵 Needs a closer look
The spec lacks component registration and a lock, preventing distro builds, and its update scriptlet targets the wrong package, leaving the ESP bootloader unchanged on upgrades.
The reason will be displayed to describe this comment to others. Learn more.
🟡 Changes recommended
Critical defects include an unsatisfiable systemd version requirement, broken EFI signing paths, an upgrade hook attached to the wrong package, and a missing component lock.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.