Skip to content

Comments

fix: enable rpmautospec in mock config#15944

Open
liunan-ms wants to merge 1 commit intotomls/base/mainfrom
liunan/changelog
Open

fix: enable rpmautospec in mock config#15944
liunan-ms wants to merge 1 commit intotomls/base/mainfrom
liunan/changelog

Conversation

@liunan-ms
Copy link
Contributor

@liunan-ms liunan-ms commented Feb 20, 2026

This pull request updates the azurelinux-4.0.tpl mock configuration to enable and configure the rpmautospec plugin, which preprocesses %autorelease and %autochangelog to count and pull the release value and change logs from Fedora upstream and fix the build failure of a few packages.

This change will work together with updated azldev (with preserving the upstream .git dir per package to mock, PR: https://github.com/gim-home/azldev-preview/pull/468) to fix the changelog issue in packages with %autorelease and %autochangelog.

Local build needs mock_rpmautospec installed, in Koji pipeline, the rpmautospec Koji plugin (python3-rpmautospec-koji) is needed at the hub level to entirely resolve the changelog issues.

Enhancements to RPM build automation:

  • Enabled the rpmautospec plugin by setting config_opts['plugin_conf']['rpmautospec_enable'] = True in the mock configuration for handling of release numbers and changelogs in spec files.
  • Configured rpmautospec options to require the rpmautospec package and use /usr/bin/rpmautospec process-distgit as the command base for processing.

Tested with azldev comp build -p gnome-keyring:

╭───────────────┬───────────────────────────────────────────────────────────────────────────┬────────────────────────────────────────────────────────────────────────────────────────────╮
│ COMPONENTNAME │ SRPM PATHS                                                                │ RPM PATHS                                                                                  │
├───────────────┼───────────────────────────────────────────────────────────────────────────┼────────────────────────────────────────────────────────────────────────────────────────────┤
│ gnome-keyring │ /home/liunan/Fedora/azurelinux/base/out/gnome-keyring-48.0-4.azl4.src.rpm │ /home/liunan/Fedora/azurelinux/base/out/gnome-keyring-48.0-4.azl4.x86_64.rpm               │
│               │                                                                           │ /home/liunan/Fedora/azurelinux/base/out/gnome-keyring-debuginfo-48.0-4.azl4.x86_64.rpm     │
│               │                                                                           │ /home/liunan/Fedora/azurelinux/base/out/gnome-keyring-debugsource-48.0-4.azl4.x86_64.rpm   │
│               │                                                                           │ /home/liunan/Fedora/azurelinux/base/out/gnome-keyring-pam-48.0-4.azl4.x86_64.rpm           │
│               │                                                                           │ /home/liunan/Fedora/azurelinux/base/out/gnome-keyring-pam-debuginfo-48.0-4.azl4.x86_64.rpm │

Copilot AI review requested due to automatic review settings February 20, 2026 22:28
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This pull request enables the rpmautospec mock plugin in the Azure Linux 4.0 build configuration to count and pull the release value and change logs from Fedora upstream and fix the build failure of a few packages. The change allows packages using %autorelease and %autochangelog macros to have their changelogs automatically generated from the upstream git history during the build process. This is part of a larger effort that includes upcoming azldev changes and requires the mock_rpmautospec package for local builds.

Changes:

  • Enabled rpmautospec plugin in mock configuration template
  • Configured rpmautospec to use the standard command and require the rpmautospec package
  • Added explanatory comments describing the feature and its purpose

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant