rpmdevtools

#91 rpmdev-bumpspec --new does nothing if it detects rpmautospec
Closed by decathorpe. Opened by decathorpe.

Closed
Reopen Issue

rpmdev-bumpspec --new apparently should set Version to the argument supplied to "--new", and reset Release.

But if rpmdev-bumpspec detects a .spec file that uses rpmautospec, it aborts early, and does not set Version at all, even if the "--new $version" flag is supplied.

the newVersion method call needs to be moved above the "early rpmautospec exit" and modified to work with rpmautospec files (maybe a new flag argument that tells it whether it should set "Release" or not?)

c.f. https://github.com/fedora-infra/the-new-hotness/issues/368

+1. Just to clarify, when rpmautospec is in use, the --new flag needs to update the Version: field but not touch the Release: field nor the %changelog. In other words, rpmdev-bumpsec needs to ignore every option except --new for this usecase.

https://pagure.io/rpmdevtools/issue/64 is related.

I submitted a PR that should fix this:
https://pagure.io/rpmdevtools/pull-request/92

If you have time, please review my changes.

Can we close this now that the PR was merged?

Fine with me.

Metadata Update from @decathorpe:
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.