Bug 1489550
Summary: | multiple build of the same version publishes all versions | ||
---|---|---|---|
Product: | [Community] Copr | Reporter: | Marc Dequènes (Duck) <duck> |
Component: | backend | Assignee: | clime |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | unspecified | CC: | clime, praiskup |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-12-07 13:54:57 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Marc Dequènes (Duck)
2017-09-07 17:30:26 UTC
Hello, this concerns yum repodata format and createrepo/createrepo_c utilities and their way of creating repodata. And then also yum tool that wasn't able to download the latest version of a package. I think having all built packages in repodata is okay. You might want to experiment with two or more versions of the same package in one project or sometimes you find out the the just installed newest version contains a bug and you want to downgrade quickly. For these cases, it's good to keep also older package versions (at least for a limited amount time). Thanks for your reply. Do you know since which version yum is behaving properly? I understand and I agree it can be useful to keep older package. How can we define how many to keep? I never saw such setting and it would be better if we could restrict it in order to avoid eating huge Copr resources uselessly (at least in my case keeping the latest failed for investigation and the 2-3 latest successful would be quite enough). > Do you know since which version yum is behaving properly? No, not really. If you have a reproducer, we can study it into more depth. > I understand and I agree it can be useful to keep older package. How can we define how many to keep? I never saw such setting and it would be better if we could restrict it in order to avoid eating huge Copr resources uselessly (at least in my case keeping the latest failed for investigation and the 2-3 latest successful would be quite enough). It is set as a constant - same for all projects. Only the latest version of a package is guaranteed to be kept. The older versions of a package are deleted if they are older than 14 days. We have an issue filed here for it: https://bugzilla.redhat.com/show_bug.cgi?id=1373568, but for simplicity I think it is beneficial that it is a constant. The auto-deletion is described here https://docs.pagure.org/copr.copr/user_documentation.html#how-long-do-you-keep-the-builds, by the way. Sorry for the late response here. I noticed the response today. Thanks for the doc pointers. My reproducer case expired as it is much older than 14 days :-). I'll ping again here if I can reproduce it in the future. |