On Sat, Feb 19, 2022 at 11:06:44PM +0100, Peter Boy wrote:
- Before I even did anything I noticed a SELinux ACE (SELinux
20-chrony-dhcp from accessing file enp1s0.sources with create access)
which then appeared repeatedly several times.
Didn't cause any noticeable problems, but makes an ==untrustworthy
impression== of the whole distribution when we not even have our highly
praised security system under control.
Currentlty, such messages are considered blockers when they appear in
This is basically with the same reasoning you give -- even if it's harmless,
it gives a very bad first impression.
The Server WG might ask QA to make them a blocker for Server Edition as
Unfortunately, I’m too stupid to understand how to enter something
our QA tracking system (apart from a bug report that probably won't fare
any better than the ones already there).
If there are bugs that violate the release criteria, use the Blocker Bugs
) to propose it as
If the bug doesn't violate an explicit criteria but should still be fixed,
Freeze Exception might be appropriate. There's also the Prioritized Bugs
process, which doesn't tie the fix to a release specifically -- might be
more appropriate for some of the long-standing ones.
Fedora Project Leader