RPM::G...Policy(3pm)

📦
version 0.34 · 2 versions
, in fedora 43

💖 RPM::G...Policy 💖

Hiii bestie 🫶 welcome to the RPM::G...Policy(3pm) page — yeah that's the manual name, and it lives in the User Contributed Perl Documentation pile. Heads up before we even start: this page is mostly placeholders, but it has some genuinely iconic diagnostic tea near the bottom, so stay with me. ✨

🌸 NAME 🌸

FIXME — FIXME

That's it. That's the name. The title is FIXME and the one-line description is also FIXME. Not me reading a manpage that doesn't know its own name 💀 iconic honestly.

🦋 SYNOPSIS 🦋

use Fixme::FIXME;

....

So you load Fixme::FIXME, and then... .... ma'am. The dots are doing a lot of heavy lifting. We love an aspirational placeholder. 💅

✨ DESCRIPTION ✨

FIXME fixme fixme fixme

No notes. The most committed to the bit description of all time. 😭

🎀 CONSTRUCTOR 🎀

Heads up: this section is marked FIXME-only if OO. So like, object-oriented vibes only, bestie.
  • new( FIXME-args ) — FIXME FIXME describe constructor

Yeah so the constructor takes FIXME-args and the description is literally FIXME FIXME describe constructor. Somebody was gonna come back and finish this. They did not come back. 🙈

💜 METHODS 💜

FIXME document methods

The methods section is currently in its "we'll write the docs later" era. Here's what it's holding space for:

  • method1 — ...
  • method2 — ...

Both of them are just .... The suspense is genuinely unreal. 🌈

💖 EXPORTED FUNCTIONS 💖

Empty. Nothing here. A whole section with absolutely zero content — she's minimalist, she's clean, she's giving nothing. ✨

💖 EXPORTED CONSTANTS 💖

Also empty. Still nothing. The void is consistent, and honestly? Respect. 🦋

💖 EXPORTABLE FUNCTIONS 💖

Empty too, bestie. Three empty sections in a row — this is the manpage equivalent of a group chat where everyone's typing but nobody sends. 😭

💖 FILES 💖

Empty. No files listed. Nothing to see, nothing to edit, no cap. 🎀

🔥 DIAGNOSTICS 🔥

Okay NOW we're talking. This is the good part. These are the warnings/errors this thing can throw at you:

  • PolkitError — Unexpected error. Here's the deal: it runs xsltproc against a polkit file, and that command is always expected to come back with exit code 0 (success). If you're seeing this error, it means we got a nonzero (error) status instead. So like, something went sideways in a way it never should. 😳
  • PolkitSelf — This one's important, so listen up. The policy shipped in your package contains a default result of auth_self or auth_self_keep. These will let any user perform the action just by supplying their own password — which they presumably know, because they were able to log in and invoke the action in the first place. So the auth_self* results are inappropriate for any actions that could affect system-wide behavior or other users. 🚨

Usually a more appropriate default result is auth_admin or auth_admin_keep; these protect the system against unprivileged users. (And if you're on a single-user desktop, you can still configure it to only use the user's password by adding the user to the "wheel" group.) 🫶

  • RubyAdvisoryDB — Your package may be affected by a Ruby Gem CVE. This test compares the Gem name and version (but not the release) against a master list of known vulnerabilities at https://github.com/rubysec/ruby-advisory-db. If the name+version match a known CVE, this warning gets triggered. ⚠️

If you've backported a fix, please include the string "Fix CVE-YYYY-NNNN" in your specfile's %changelog section. That will silence the warning for that given CVE. Slay. ✅

👑 SEE ALSO 👑

L<>

That's the whole thing. An empty L<>. She's mysterious, she's unreachable, she links to absolutely nobody. 🫠

🌟 AUTHOR 🌟

Ed Santiago <santiago@redhat.com> 💜

💀 POD ERRORS 💀

Hey! The above document had some coding errors, which are explained below:

Around line 462:

An empty L<>

Yeah — that L<> we just met in SEE ALSO is the culprit. Empty link tag, empty soul. Not me clocking that the manpage snitched on itself. 😭

And that's the whole page, bestie! Written by Ed Santiago <santiago@redhat.com>, and this copy came to you via perl v5.42.0 dated 2025-07-25. Go finish your specfile changelog and go to bed. 🎀✨💅

📦 where this page comes from