public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Zdenek Dohnal <zdohnal@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/cups] rawhide: Explain what LSPP is
Date: Thu, 10 Sep 2026 05:39:50 GMT	[thread overview]
Message-ID: <178901879060.1.4900776772314123463.rpms-cups-eb9c715fdf7f@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/cups
Branch : rawhide
Commit : eb9c715fdf7f635fc954466a432bcbae682abe12
Author : Zdenek Dohnal <zdohnal@redhat.com>
Date   : 2026-09-10T07:39:35+02:00
Stats  : +3/-0 in 1 file(s)
URL    : https://src.fedoraproject.org/rpms/cups/c/eb9c715fdf7f635fc954466a432bcbae682abe12?branch=rawhide

Log:
Explain what LSPP is

---
diff --git a/cups.spec b/cups.spec
index 846d8aa..5fcebc7 100644
--- a/cups.spec
+++ b/cups.spec
@@ -69,6 +69,9 @@ Patch11: cups-failover-backend.patch
 Patch12: cups-dymo-deviceid.patch
 
 %if %{lspp}
+# lspp - labeled security protection profile
+# includes implementation for MLS - multi-level security - done by selinux,
+# audit and labels
 # selinux and audit enablement for CUPS - needs work and CUPS upstream wants
 # to have these features implemented their way in the future
 Patch100: cups-lspp.patch

                 reply	other threads:[~2026-09-10  5:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=178901879060.1.4900776772314123463.rpms-cups-eb9c715fdf7f@fedoraproject.org \
    --to=zdohnal@redhat.com \
    --cc=git-commits@fedoraproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox