Looks like RHEL9 doesn't support autochangelog

[ericcurtin]

Change back to manual changelogs

Summary by Sourcery

Build:

• Generate changelogs manually instead of automatically.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request reverts the changelog generation method from automatic to manual. This change was made due to RHEL9 incompatibility with the automatic changelog generation tool.

State diagram for changelog generation process change

stateDiagram-v2
    [*] --> AutomaticChangelog: Initial State
    AutomaticChangelog --> ManualChangelog: RHEL9 Incompatibility
    ManualChangelog --> [*]

    state ManualChangelog {
        [*] --> AddEntry
        AddEntry --> FormatEntry: Add timestamp, author, version
        FormatEntry --> [*]
    }

Loading

File-Level Changes

Change	Details	Files
Revert to manual changelog generation	Removed the %autochangelog line from the spec file. Added manual changelog entries for previous releases and updates. Updated version numbers and release dates in the changelog entries to reflect the manual entries.	rpm/python-ramalama.spec

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[ericcurtin]

If my reading of the build failures are correct on the main branch, RHEL9 doesn't support autochangelog, EPEL9 seems to though

[sourcery-ai]

Hey @ericcurtin - I've reviewed your changes - here's some feedback:

Overall Comments:

• Please provide a more detailed commit message explaining why autochangelog needs to be disabled (e.g., RHEL9 compatibility requirements)
• Consider using conditional logic to only disable autochangelog for RHEL9 builds while maintaining it for other distributions that support it

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[rhatdan]

@lsm5 @smooge PTAL

[ericcurtin]

@lsm5 could we get centos-stream-9 packit builds turned on for PRs so we don't get into the scenario where main is failing but PRs are passing again?

[maxamillion]

@ericcurtin it looks like another option would be that we could add the epel repos to the UBI base image and install the rpmautospec-rpm-macros package which provides the %autochangelog macro.

[ericcurtin]

@ericcurtin it looks like another option would be that we could add the epel repos to the UBI base image and install the rpmautospec-rpm-macros package which provides the %autochangelog macro.

Yeah I guess I'm more worried if we end up packaging this for RHEL at some point. But we can close this for now and re-visit that in future if we need to in future.

@lsm5 or @maxamillion maybe we just turn off the centos-stream-9 builds on the main branch of ramalama for now to get it green again? And only build on EPEL9, not a Packit expert personally.

[maxamillion]

@ericcurtin sounds like the RHEL problem, not an upstream one 😉

[ericcurtin]

Yeah I guess, closing... @lsm5 or @lbarcziova how do we turn off centos-stream-9 builds on the main branch here in packit? We've been red since forever

[lbarcziova]

hi @ericcurtin ! Currently, for the main branch, the builds are implicitly submitted for all the targets in the rhcontainerbot/podman-next Copr repo. If you want to override this, you need to define the targets list in here, similarly like you have it defined for pull-requests here.

[ericcurtin]

Thank you @lbarcziova