osinfo-db-validate(1)

💖 NAME 💖

osinfo-db-validate — the tool that gives your libosinfo XML data files a full-on vibe check ✨

🦋 SYNOPSIS 🦋

osinfo-db-validate [OPTIONS...]

osinfo-db-validate [OPTIONS...] LOCAL-PATH1 [LOCAL-PATH2...]

osinfo-db-validate [OPTIONS...] URI1 [URI2...]

🌸 DESCRIPTION 🌸

Okay so bestie, osinfo-db-validate is literally the friend who looks at your XML files and tells you if they pass the RNG schema check or not — it validates XML files living in one of the osinfo database locations, no cap. 💅

Here's the location tea, because you need to know:

• system This is the primary system-wide database location, bestie — it's meant for operating system vendors distributing database files in the native package format. The RNG schema is expected to be present in this location, so yeah, it lives here. 👑
• local The secondary system-wide database location. This one's for system administrators who want to provide an updated database for all users. It may provide an RNG schema override — and if it doesn't, the RNG schema from the system location gets used instead. 🫶
• user The user private database location, for unprivileged local users who want to give the applications they use an updated database. It may provide an RNG schema override — otherwise the RNG schema from the local location is used, or failing that, the system location. It's giving fallback chain realness. 🎀

And here's the default behaviour, lowkey important: if you run it with a privileged account (ie root), the local database location will be validated by default. Otherwise, the user location gets validated. ⭐

Alternatively — and this is the fun part — you can straight up hand it a list of files to validate using the LOCAL-PATH1 or URI1 arguments. Iconic. 🦋

Any validation errors will be displayed on the console when detected, so you'll know immediately. 😭

---

✨ OPTIONS ✨

• --user — overrides the default behaviour and forces validating files from the user database location 💜
• --local — overrides the default behaviour and forces validating files from the local database location 🍓
• --system — overrides the default behaviour and forces validating files from the system database location 👑
• --dir=PATH — overrides the default behaviour and forces validating files from the custom directory PATH 🎀
• --root=PATH — prefixes the database location with the root directory given by PATH. This is so useful when you wanna validate files that are inside a chroot environment or equivalent, fr fr 🌈
• -v, --verbose — displays verbose progress information while validating files, so you can watch it do its thing 🔥

💀 EXIT STATUS 💀

The exit status will be 0 if all files passed validation, or 1 if a validation error was hit. That's it, that's the whole mood. 🙈

🧚 SEE ALSO 🧚

• osinfo-db-path(1)

🌟 AUTHORS 🌟

Daniel P. Berrange <berrange@redhat.com>

🎀 COPYRIGHT 🎀

Copyright (C) 2012-2016 Red Hat, Inc.

💅 LICENSE 💅

osinfo-db-validate is distributed under the terms of the GNU LGPL v2+ license. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Like, zero warranty bestie, don't come for them 😭

---

That's the whole page, slay! 🫶 Brought to you by osinfo-db-tools-1.12.0, dated 2025-05-02 — mwah, go validate something iconic 💖✨