LINTIAN::CHANGELOG::ENTRY(3)

📦
version 2.139.0ubuntu2 · 9 versions
, in ubuntu stonking

💖 NAME 💖

Lintian::Changelog::Entry — the little queen that represents one single entry in a Debian changelog. One entry, one object, no cap. This page lives in the Lintian manual (Debian Package Checker energy ✨).

🌸 SYNOPSIS 🌸

Okay bestie, real talk: this section is literally empty in the original. Nothing to show, nothing to run. The vibe is silence. 🤫

✨ DESCRIPTION ✨

🎀 Methods

  • init — creates a brand new object. No options, no arguments, she just exists. Iconic behavior honestly. 💅
  • new — alias for init. Same girl, different name.
  • is_empty — checks if the object is actually initialized with data. And here's the tea: due to limitations in Parse::DebianChangelog, this currently just checks whether one of the fields Source, Version, Maintainer, Date, or Changes is initialized. That's it, that's the whole check. 🫶

🦋 Accessors

The following fields are available via accessor functions — and heads up, all fields are string values unless otherwise noted:

  • Source
  • Version
  • Distribution
  • Urgency
  • Urgency_Comment
  • "Urgency_LC"
  • "ExtraFields" — and this one is actually Extra_Fields (all fields except for urgency, as a hash; POD spelling forces the underscore, so now you know why it's spelled weird, iykyk).
  • Header — the whole header, in verbatim form.
  • Changes — the actual content of the bug report, in verbatim form.
  • Trailer — the whole trailer, in verbatim form.
  • Closes — an Array of bug numbers. Not a string! Noted, because we said "string unless otherwise noted" and this is the otherwise noted part. 😌
  • Maintainer
  • "MaintainerEmail"
  • Date
  • Timestamp — the Date expressed in seconds since the epoch.
  • ERROR — the last parse error related to this entry, in the format described at Parse::DebianChangelog::get_parse_errors. When this one's populated, something went down. 💀
  • position

👀 SEE ALSO 👀

Originally based on Parse::DebianChangelog by Frank Lichtenheld, <frank@lichtenheld.de>.

👑 AUTHOR 👑

Written by Felix Lechner <felix.lechner@lease-up.com> for Lintian, in response to #933134. Slay.

Please see in the code; FSF's standard short text triggered a POD spelling error here. (The drama. The lore. 🍓)

And that's the whole page, bestie 💖 this doc came from Lintian v2.139.0ubuntu2, dated 2026-10-08, and it's the Lintian::Changelog::Entry(3) manual page — go forth and parse those changelogs, you absolute main character 🧚✨

📦 where this page comes from