Bug 76689
| Summary: | unique package directories per channel? | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Network | Reporter: | Isaiah Weiner <iweiner> |
| Component: | RHN/Channels | Assignee: | Greg DeKoenigsberg <gdk> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | jkomendar |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | RHN Stable | CC: | alikins, bretm, curtisz, gafton, gdk, lakamine, mihai.ibanescu, pjones, robin.norwood |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2002-10-29 22:54:15 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Isaiah Weiner
2002-10-24 22:17:21 UTC
I presume that the scenario is as follows: you want to take a package from a base Red Hat channel, let's say foo-1.31-8, and you want to place it into a base channel. So you download foo-1.31-8 and then attempt to upload it into the private base channel, and it fails because a unique constraint is violated. If this is correct, would you be satisfied with the ability to assign foo-1.31.8 directly to the new base channel without having to re-upload? Would that be sufficient? That would be splendid. Please note that no uniqueness constraint violation should occur, but (if the package is present both in a Red Hat base channel and a custom subchannel) an ambiguity can occur. The package is present in a Red Hat base channel and a custom base channel. The bug still occurs. Do you need any more information from me? When can I expect a status update or some form of instruction? We were unable to reproduce this problem with the current code that we have. This is what jkomenda tried: - uploaded 96 packages from 7.2 into a fresh base channel He can see all of them on the web site. I would suggest to run up2date -u on the proxy machine. This should give you the latest proxy code, that we pushed live an hour ago. There were some bugfixes that may have fixed your problem. Let me know if this does not solve the problem for you. Fixed it. Closing bugs. |