Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RFE: Support %autochangelog and %autorelease when doing tagless imports using rpmautospec logic #21

Open
nazunalika opened this issue Mar 5, 2024 · 0 comments

Comments

@nazunalika
Copy link
Member

nazunalika commented Mar 5, 2024

CentOS Stream 10 (and Fedora) have rpmautospec as opt-in. This means that release tags can easily have %autorelease and/or %autochangelog.

When processing a repo that has SOURCES and SPECS, this generally isn't a big deal. These are typically in the format we expect with everything filled out.

When processing a repo that has everything in a flat structure, the SPEC file may have %autorelease. This can also mean %autochangelog may exist, which means an accompanying changelog file in the repo will also exist alongside the spec file.

When importing with srpmproc with tagless mode, it should be possible to properly assess the release and changelog and fill them in accordingly.

pv2 currently supports this by importing the rpmautospec python library.

Example starting spec: https://gitlab.com/redhat/centos-stream/rpms/PyYAML/-/blob/c10s/PyYAML.spec
Example processed spec: https://git.rockylinux.org/staging/src-rhel/rpms/pyyaml/-/blob/c10s/SPECS/PyYAML.spec

It should be noted that while %changelog is appended to the spec file, %autorelease is not modified. It is processed by the macro logic added at the top of the spec file by rpmautospec (if applicable). Otherwise, it is processed by other means.

@nazunalika nazunalika changed the title RFE: Support %autochangelog and %autorelease when doing tagless imports RFE: Support %autochangelog and %autorelease when doing tagless imports using rpmautospec logic Mar 5, 2024
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

No branches or pull requests

1 participant