reason that Janitor closed a ticket is unclear

[Rolf Leggewie]

For lack of a better place to file a ticket I will file it against Launchpad itself. Please reassign as necessary.

Consider https://bugs.launchpad.net/ubuntu/+source/apt-cacher-ng/+bug/1350432/comments/2 which was Janitor closing bug 1350432. It was so kind to include the relevant changelog entry. Except that it stopped too soon and did not actually include the relevant changelog entry but only the latest entry. Yet, the upload responsible for closing the ticket was the one for apt-cacher-ng (0.8.0~pre2-1) to experimental. The message as posted is confusing at best.

[Colin Watson (cjwatson)]

I agree this is confusing. What's happening is that in some cases (mostly syncs, IIRC) LP trawls back through the changelog to find the set of changes that's actually effective rather than just whatever's in the .changes file; but it doesn't then use that to build the bug-closing message.

[Colin Watson (cjwatson)]

I don't quite have time to dig right now, but for future reference, the problem is probably in lib/lp/soyuz/model/processacceptedbugsjob.py: close_bugs_for_sourcepackagerelease does a since_version check to compute the set of bug IDs to close, but doesn't then pass that information down to close_bug_ids_for_sourcepackagerelease which constructs the bug-closing message.