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
This is a musing that came up while discussing #247. If one of the new RPMs (relative to the previous commit) in the jigdo set is a security update, then the jigdo RPM itself should be marked as a security update. This is more of a releng integration issue rather than something we can do at the rpm-ostree compose level.
The text was updated successfully, but these errors were encountered:
jlebon
changed the title
jigdo mode
jigdo mode: mark jigdo RPM as security update if a new member RPM is a security update
Dec 5, 2017
cgwalters
changed the title
jigdo mode: mark jigdo RPM as security update if a new member RPM is a security update
rojig: mark rojigRPM as security update if a new member RPM is a security update
Mar 6, 2018
This is a musing that came up while discussing #247. If one of the new RPMs (relative to the previous commit) in the jigdo set is a security update, then the jigdo RPM itself should be marked as a security update. This is more of a releng integration issue rather than something we can do at the
rpm-ostree compose
level.The text was updated successfully, but these errors were encountered: