= Questions/Requested Information
This talk will discuss the Fedora CI project and use the rpminspect tool as an example. It will be about 25% on Fedora CI and 75% on rpminspect, but that's not a hard and fast rule. rpminspect is a new tool being developed to help ensure packaging policy and build reliability. I call rpminspect a "build deviation analysis tool". It checks for policy compliance as well as things like ABI differences. Did new symbols appear in shared libraries? Did any disappear? Do we have all of the hardened options enabled for the build? Are there any unapproved setuid executables? And so on. rpminspect can check a single build or compare one build to another. Developers can run it locally or it can run via Fedora CI and report results that way.
https://github.com/dcantrell/rpminspect
List each person by their name and FAS ID, as shown below:
(Delete all that DO NOT apply)
This could be room setup, A/V needs, etc. If you have private concerns, please email them to flock-admin@fedoraproject.org.
Are you proposing a 25 or a 50 minute talk?
Would prefer a 50 minute talk.
I want to learn about this, however not sure if I would dedicate 50 minutes, if my schedule is full with other things.
I can do 25 minutes, that's fine. I know there was also some talk of a Fedora CI workshop as well which may be more appropriate for continuation of the presentation and contributions.
Metadata Update from @mattdm: - Issue assigned to mattdm
Metadata Update from @mattdm: - Issue marked as blocking: #223 - Issue tagged with: Talk Accepted
Metadata Update from @riecatnor: - Issue close_status updated to: Resolved - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.