DEP3CHANGELOG(1)

✨ NAME ✨

okay bestie, say hi to dep3changelog — she generates a changelog entry from a DEP3-style patch header 💖

🌸 SYNOPSIS 🌸

dep3changelog patch [patch ...] [options] [-- [dch_options]]

🦋 DESCRIPTION 🦋

So here's the vibe: dep3changelog goes into the patch files you handed her, pulls out the DEP3 patch headers, and builds a changelog entry for each and every patch. One patch, one entry, no skipping, periodt 💅

Now, if the patch author is not the same as the one she detects from the DEBEMAIL, NAME, DEBEMAIL, or EMAIL environment variables, she slides Thanks to author <email> into that patch's changelog entry 🫶 (yes the author-detection list literally says DEBEMAIL twice, that's just how it is, iykyk)

Any bug-debian or bug-ubuntu fields? Those get added as Closes to the changelog entry. Iconic behaviour honestly 👑

Then all those freshly generated changelog entries get passed to debchange as an argument, along with whatever dch_options you gave her. Chef's kiss, that's the whole pipeline 🎀

💅 OPTIONS 💅

• --help, -h — shows you a help message and exits successfully. She's helpful AND she doesn't overstay ✨
• --version — shows version and copyright info and exits successfully. Main character info dump 💖

🌈 ENVIRONMENT 🌈

• DEBEMAIL, EMAIL, DEBFULLNAME, NAME — bestie, these are literally the ones described up there in the DESCRIPTION, go peek at how she uses them 👀

👑 AUTHOR 👑

Steve Langasek <vorlon@debian.org>

🍓 SEE ALSO 🍓

debchange(1)

k bye that's the whole page 🧚💜 this one ships as part of DEBIAN, filed under Debian Utilities — mwah, take care of her 💖✨