#527 document "odcs renew" package set behavior
Closed 2 years ago by ktdreyer. Opened 2 years ago by ktdreyer.

Does odcs renew always renew a compose with the exact same set of builds?

For example:
1. OSBS initiates an ODCS compose from the f33-candidate tag. Resulting ODCS compose ID is 12345.
2. Time passes. ODCS garbage-collects compose 12345.
3. The f33-candidate tag's builds change in Koji.
4. I run odcs renew 12345

What packages are in the renewed compose?


Ok, I see the README says "Such compose will have the same versions of packages as in the time when it was originally generated."

It would be great to add this to --help.

PR #528 adds this information to to --help.

Metadata Update from @ktdreyer:
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata
Related Pull Requests
  • #528 Merged 2 years ago