> On Wed, 2004-10-06 at 23:54 +0100, Dean Earley wrote:
>> I was playing with setting up my own repository, so I found a group of
>> random RPMs, and run yum-arch on them, no problem. I go ahead and try
>> a yum check-update, and it fails with a 404 on one of the headers. I
>> check the RPM, and its correctly called:
>> iproute2-2.2.4-now-ss990417-2.i386.rpm
>> I check the header.info, and it correctly has:
>> 0:iproute2-2.2.4-now-ss990417-2.i386=iproute2-2.2.4-now-ss990417-2.i386.rpm
>> I then check for the header file and:
>> iproute2-0-2.2.4-now-ss990417-2.i386.hdr
>> Notice ^
>> The file it is requesting is:
>> iproute2-2.2.4-now-0-ss990417-2.i386.hdr
>>
>> yum-arch -vv only shows:
>> Digesting rpm - iproute2-2.2.4-now-ss990417-2.i386.rpm - 77/214
>>
>> This is with RedHat 9, and Yum 2.0.4.
>>
>> Any suggestions or ideas?
>
> the -0 is the epoch for the package (No epoch is a 0 epoch)
>
> that's why the header has this in there. to distinguish a package of the
> same name, arch, release and version (but different epoch) from another
> package.
>
> It's not a bug.
Would the fact its putting the epoch in different places and causing a
failure be a bug though?
Header file: iproute2-0-2.2.4-now-ss990417-2.i386.hdr
Requested file: iproute2-2.2.4-now-0-ss990417-2.i386.hdr
^^^^^^^^^^^
--
Dean Earley AKA Dee (dean@xxxxxxxxxxxxxx)
irc: irc://irc.blitzed.org/
web: http://personal.earlsoft.co.uk
phone: +44 (0)780 8369596
