Brian J. Murrell

> Nothing happens, This is a real pity, as I think it would resolve this ticket. > as the release-monitoring.org only builds packages that have Fedora mapping and the owner...

I see. Yeah. Seems I am [re-]writing my own version/implementation of _the-new-hotness_ for packages I am interested in which ultimately (after doing things like `Version:`/`Release:`/`%changelog` bumps, etc.) ends up requesting...

> It is described only as source code or resulting ruleset, I'm not sure I'm getting your meaning here. > but not checking the resulting ruleset So I have to...

> Would it help to have warning that there are no-interface rules preceding specific rule? Similar to one listing rejected invalid rule. Would that only be displayed to CLI `fw4`...

But again, I don't think optimisation should trump correctness and the principle of least surprise, **especially** when it comes to security. If it takes a number of nftables rules to...

I really do wonder how many other less knowledgeable (i.e. know enough to check the nft rules produced or otherwise audit the implementation of their security policy) people have fallen...

> I am currently looking on the way to run the CI over this PR. Why? There are no code changes here. What value would running it in CI add?

> @paul356 , next time you push some modifications, could you please add the following pragma at the end of your commit message: > `Doc-only: true` If it is only...

> I will point out that daos_metrics was not designed for use in production, and while I'm not aware of any specific problems with it, I wouldn't feel comfortable saying...

Fair enough. So an independent could request an admin to set that flag for them, yes?