#191 3rd party tracking: fedpkg/rpkg
Closed: Fixed by nphilipp. Opened by nphilipp.

Story Time

As a package maintainer,

I want that fedpkg is available in a version coping well with rpmautospec features in my spec files,

so I don't have to use workarounds.

Acceptance Criteria

  • A new upstream release of rpkg is available on Pagure that includes the changes in rpkg#557: https://pagure.io/rpkg/releases
  • Packages have been built in Fedora, and submitted as updates for the stable releases of Fedora.
  • These updates are available in the stable repositories.

Background

This is merely to track progress on the fedpkg/rpkg side and follow-up with the maintainers if it seems stuck.


Metadata Update from @nphilipp:
- Issue marked as depending on: #144
- Issue marked as depending on: #172
- Issue tagged with: 3rd party, F35 Change

Currently fedpkg verrel always returns release 1.fcNN when Release: %{autorelease} is used. I suspect it will actually list the same release as rpmautospec calculate-release once this issue is resolved, correct?


Currently fedpkg srpm generates SRPM with a placeholder automatic changelog:

* Fri Jun 18 2021 John Doe <packager@example.com> - ...-1.fc35
- local build

I suspect it will actually list the same changelog as rpmautospec generate-changelog once this issue is resolved, correct?

Hi @churchyard sorry for the delayed reply, I'm not sure how I missed your comment.

Yes, that is correct. Once the rpkg changes are merged and picked up by fedpkg then it will be able to calculate the real release.

rpkg-1.62-6 has been released and is available as a stable package (F33: pending push to stable), which should fix this.

Metadata Update from @nphilipp:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Metadata