Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rojig: mark rojigRPM as security update if a new member RPM is a security update #1133

Open
jlebon opened this issue Dec 5, 2017 · 0 comments

Comments

@jlebon
Copy link
Member

jlebon commented Dec 5, 2017

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.

@jlebon 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 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant