RE: [yocto-patches] [AUH][PATCH v2 4/9] upgrade-helper.py: add changelog flag

Hi Alex,

Thanks for the feedback.

Here are some examples from scarthgap --stable run (148 recipes attempted, 99 changelogs extracted):

Strategy 1 — Changelog file parsing (52 packages, e.g. base-passwd 3.6.3 → 3.6.8, from debian/changelog):

  base-passwd (3.6.8) unstable; urgency=medium

    * Debconf translations:
      - Turkish (thanks, Nuri KÜÇÜKLER; closes: #1102464).
    * update-passwd(8) translations:
      - French (thanks, Baptiste Jammet; closes: #1119914).

  base-passwd (3.6.7) unstable; urgency=medium
    ...

Strategy 2 — Per-version files (1 package: git 2.44.0 → 2.44.4, from Documentation/RelNotes/v2.44.{1..4}.txt):

  Git v2.44.1 Release Notes
  ...
  Git v2.44.4 Release Notes

Strategy 3 — Git log between version tags (46 packages, e.g. asciidoc 10.2.0 → 10.2.1):

  21e33ef Fix setting up debian backports in Dockerfile (#273)
  22f3bf0 Bump version to 10.2.1 (#269)
  c30d311 Fix running test suite for python 3.5 (#272)
  6d9f76c Update GitHub actions badge

49 packages had no changelog found (no changelog file, no per-version files, no matching git tags).

I'll add unit tests for the changelog module in a separate commit in v3.

Regarding moving this to devtool — I agree that's the right long-term approach.
I can send a patch for devtool to oe-core master adding this. If accepted, we could request a backport to scarthgap through the Yocto TSC, and then drop the parsing from AUH in favour of just picking up devtool's output.

For now, keeping it in AUH lets us iterate on the extraction logic without requiring oe-core changes. If you prefer the devtool path, we can put the changelog path on hold

Cheers,
Daniel

> -----Original Message-----
> From: Alexander Kanavin <[email protected]>
> Sent: Monday, 27 April 2026 13:17
> To: [email protected]
> Cc: Daniel Turull <[email protected]>; [email protected];
> [email protected]; [email protected]
> Subject: Re: [yocto-patches] [AUH][PATCH v2 4/9] upgrade-helper.py: add
> changelog flag
> 
> On Mon, 27 Apr 2026 at 12:01, Alexander Kanavin via lists.yoctoproject.org
> <[email protected]>
> wrote:
> > Can you add examples please? This implements three different
> > 'strategies', all of them are doing 'guessing', so it would be really
> > beneficial to see what they actually produce.
> >
> > It would also be super nice to have tests for this module, especially
> > if people start tweaking it further. It looks like something that can
> > break super easily. I know AUH has no tests (I inherited it in that
> > condition), but at least this particular part could.
> 
> I still need to see examples, but come to think of, this changelog extraction
> should be in devtool, at least partially. devtool can diff the source tree
> between the old and new version (it creates specific devtool specific tags for
> both, even when upgrading tarballs), and then filter the difference to only
> files that carry information about changes, which will eliminate most of the
> 'guessing'. Then it could write that into a file somewhere in workspace, and
> then further filter it to highlight CVEs or anything else that looks particularly
> important. Then AUH only needs to pick up those files and incorporate them
> into commit messages or emails.
> 
> Alex