From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U;) Gecko/20020913
Description of problem:
I need to be able to guarantee I'm using a fresh copy of a package even if the
rhn_package_manager tool believes it's already been uploaded and copied per
identical NVR. Can I specify a unique package directory for individual
channels, in this case a base channel, without changing the package directories
for all the channels hosted on a proxy?
Version-Release number of selected component (if applicable):
Steps to Reproduce:
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
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
Fixed it. Closing bugs.