Story #173
closed
RFE: ability to keep repository histories or package changes as version control
0%
Description
++ This bug was initially created as a clone of Bugzilla Bug #830956 ++
Description of problem:
Description of problem:
Add version control to repository state for history, rolling back, etc.
Version-Release number of selected component (if applicable):
How reproducible:
Never. Doesn't currently exist. We'd like it to.
Steps to Reproduce:
1.
2.
3.
Actual results:
Currently the only method to maintain a repository version is to create a repository clone.
Expected results:
Ability to update, roll back, and identify repository version information.
Additional info:
--- Additional comment from ericlake@gmail.com at 06/11/2012 22:43:26 ---
This would be a really nice feature to have. I would envision something like the way git can tag a release. Or even the history functionality in yum may work as well. Once you know that the packages in your copy of the repo are good then you can create a tag that you can easily roll back to if needed.
Where I work we have build systems that build code for our products all day every day. It would be nice to be able to get back to a know good repo if we find an issue.
Added by dkliban@redhat.com about 9 years ago
Updated by bmbouter about 5 years ago
- Status changed from NEW to CLOSED - WONTFIX
Updated by bmbouter about 5 years ago
Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.
.
Merge pull request #173 from dkliban/815
Fixes #815 - db is not a dict as flake8 assumed