DEB-CHECK-...S-CONFLICTS(1)

πŸ’– NAME πŸ’–

ok so deb-check-file-conflicts β€” she checks your Debian packages for missing Breaks/Replaces declarations, bestie. that's the whole vibe ✨


🌸 SYNOPSIS 🌸

deb-check-file-conflicts [--debug] [--changes-file=FILE] [-o OUTPUT]
[--output=OUTPUT]

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so here's the tea: deb-check-file-conflicts takes the binary packages you just produced and checks them for conflicting files against other packages that didn't declare a Breaks and Replaces relationship. 🫢

basically she's the friend who notices drama before it starts β€” she helps you spot potential upgrade issues, the kind where files from one package might clash with files from another package during installation. lowkey iconic that she catches it early. πŸ’…

⚠️ real talk though: the results depend on what apt repositories are enabled. if you wanna prevent upgrade issues across Debian releases, you need to have both the unstable repo and the previous release repo enabled in your apt sources configuration. no repos, no accuracy, periodt. 😭

✨ OPTIONS ✨

  • --debug β€” turns on debug output. she gets chatty. πŸ—£οΈ
  • --changes-file=FILE β€” tells her which changes file to check. defaults to the CHANGES_FILE environment variable if you don't say anything. πŸ‘€
  • -o, --output=FILE β€” writes the output to FILE. defaults to $EXPORT_DIR/missing_breaks_replaces.xml, or if that's not a thing, ./missing_breaks_replaces.xml. πŸ“

πŸŽ€ OUTPUT πŸŽ€

she generates a JUnit XML format report with test results for every single binary package she checked. each test case tells you whether missing Breaks/Replaces relationships were found. very demure, very mindful, very machine-readable. 🧚


🌈 EXAMPLES 🌈

check a changes file for missing relationships:

$ deb-check-file-conflicts --changes-file foo_1.0-1_amd64.changes

write results to a specific output file:

$ deb-check-file-conflicts -o results.xml --changes-file foo_1.0-1_amd64.changes

πŸ‘‘ AUTHOR πŸ‘‘

deb-check-file-conflicts and this manual page were written by Maximiliano Curia <maxy@gnuservers.com.ar>. 🫑

both are released under the GNU General Public License, version 2 or later. slay, licensing-wise. ⭐


πŸ’œ SEE ALSO πŸ’œ


okay bestie that's the whole page πŸ’– huge shoutout to the Debian crew and the Debian Utilities squad for bringing us DEB-CHECK-...S-CONFLICTS(1) β€” go forth and declare your Breaks/Replaces, mwah πŸ’‹πŸŽ€πŸ¦‹