PACLOG(1)

📦 version 0.15.0, in arch rolling

🎀 paclog — PACLOG(1) 🎀

🌸 NAME 🌸

paclog — filters pacman log entries, bestie. That’s the whole gig: it sifts through pacman log entries and shows you the ones you asked for. 🫶

✨ SYNOPSIS ✨

paclog [options] [filters]...
paclog [options] --pkglist
paclog (--help|--version)

💖 DESCRIPTION 💖

okay so here’s the vibe: if input is provided on stdin, it will be parsed instead of --logfile. Log entries will be displayed if they match any of the provided filters. Any — not all, bestie. That distinction ate. 💅

To display the intersection of multiple filters, you can connect them by a pipe:

paclog --after=2015-01-01 | paclog --warnings

🛠️ OPTIONS 🛠️

  • --config=path — set an alternate configuration file path. 🗂️
  • --logfile=path — set an alternate log file path. 📜
  • --root=path — set an alternate installation root. 🌱
  • --sysroot=path — set an alternate system root. See pacutils-sysroot(7). 🏠
  • --[no-]color — colorize output. By default, output will be colorized if stdout is a terminal. 🌈
  • --pkglist — print the list of installed packages according to the log. 📦
  • --help — display usage information and exit. 🆘
  • --version — display version information and exit. 🏷️

🔎 Filters 🔎

  • --action=action — display package operations. action must be one of "install", "reinstall", "upgrade", "downgrade", "remove", or "all". 👑
  • --after=date, --before=date — display entries after/before date. If seconds or timezone information is included, it will be silently ignored, allowing output from date -I to be used: 🕰️
paclog --after "$(date -Iminutes --date '3 days ago')"
  • --caller=name — display log entries from name. May be specified multiple times. Case-sensitive. 👀
  • --commandline — display pacman-style logged commandline entries. ⌨️
  • --grep=regex — display log entries whose message matches regex. 🔍
  • --package=pkgname — display logged actions affecting pkgname. May be specified multiple times. 📦
  • --warnings — display errors, warnings, and notes. 🚨

⚠️ CAVEATS ⚠️

tiny heads-up, no cap: paclog determines whether or not to read the log file from stdin based on a naive check using isatty(3). So if paclog is called in an environment — like a shell function or script being used in a pipe — where stdin is not connected to a terminal but there isn’t actually a log file to parse, paclog should be called with stdin closed. For POSIX-compatible shells, this can be done with "<&-". 🫶

shoutout to pacutils, dated 2025-12-04 — this is PACLOG(1), and it’s iconic. periodt. bye bestie 💖🫶

📦 where this page comes from