Hi Heitor! Thanks for the first pass review. You're right that the debian/changelog entries are not consistently formatted. I was following James Page's guidance which he provided in this comment: https://bugs.launchpad.net/ubuntu/+source/watcher/+bug/2088620/comments/16
"When the most recent changelog entry is UNRELEASED you should add you changelog update as part of the existing entry rather than creating a new one" This is why for Zed and Caracal the debdiffs are labelled UNRELEASED and merged with a previous entry Current Zed changelog is UNRELEASED: https://git.launchpad.net/~ubuntu-openstack-dev/ubuntu/+source/watcher/tree/debian/changelog?h=stable/zed Current Caracal changelog is UNRELEASED: https://git.launchpad.net/~ubuntu-openstack-dev/ubuntu/+source/watcher/tree/debian/changelog?h=stable/2024.1 So, I remain unclear on what to do for Zed and Caracal as the previous entry is UNRELEASED. Should I leave the previous entry unchanged and as UNRELEASED, then create a new entry with the correct release name (jammy-zed, jammy-caracal), and increment the version without adding another ubuntu1? Admittedly, I see that for Bobcat and Antelope, the releases are jammy- bobcat and jammy-antelope so I should have specified the release. I have another in-flight SRU for Watcher that's currently in proposed (https://bugs.launchpad.net/ubuntu/+source/watcher/+bug/2088620), which would be blocking this one. In that case my changelog entry was merged with the existing jammy-antelope/bobcat entry with no change to the version: eg. 2:11.0.0-0ubuntu1.1~cloud0 for bobcat. The customer behind both SRUs has stopped responding, so I suggest that we let the in-flight SRU pass through, then I'll regenerate these debdiffs with your corrections on top of that. When the time comes, I assume that for bobcat and antelope, since the release is properly specified, I should approach versioning and merging of changelog entries in the same way that was done with the SRU that's in proposed (keep the same version, and add the changelog entry to the existing one)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2091947 Title: [SRU] Watcher crashes on creation of multiple audits and gets stuck in PENDING To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2091947/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
