#72 Use build tags from the repository for release bumping etc.
Closed: Fixed 4 years ago by nphilipp. Opened 4 years ago by nphilipp.

Currently, the code in rpmautospec.release (and by extension, rpmautospec.process_distgit) queries Koji for information about existing builds. When run in the mock chroot, it should use the tags in the repository instead.

Background:

  • Currently the code would attempt to contact the Koji prod instance from within the chroot, because that's the hardcoded default.
  • With #44 implemented, the tags would be of the form build/<N-E-V-R>, where <N-E-V-R> is the components (name, epoch, version, release) separated by dashes and escaped with rpmautospec.py2compat.tagging.escape_tag() to produce valid git tags (can be unescaped with unescape_tag()).

Acceptance criteria:

  • Optionally uses tags for calculating the release number (see above for format).

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

4 years ago

Login to comment on this ticket.

Metadata