[ATrpms-users] up2date Fails With Incomplete Data

[Mike Bydalek]

Hi Axel,

Axel Thimm wrote:
> On Sat, Aug 19, 2006 at 09:48:54PM -0700, Mike Bydalek wrote:
>   
>> Basically, for some reason I'm no longer able to update using the
>> repository (see below) on RHEL4.  Basically, anything that I want to
>> update that requires a dependency fails.  In the example below, pyzor
>> now requires python-abi.  I was able to wget the .rpms and use rpm -i/U
>> to install and upgrade, so I don't know what's failing to "communicate"
>> here.  If there is a way I can debug this, that would be great to know.
>>     
>
> If rpm (w/o any --nodeps flags) behaves properly with an
> install/upgrade and a depsolver does not, then it's a hint that the
> depsolver may have a bug.
>
>   
>> Here's the line I have added to the /etc/sysconfig/rhn/sources:
>>
>> apt atrpms http://dl.atrpms.net el4-i386/atrpms stable
>>
>> Here's the command and output I was trying to run:
>>
>> [root at mail ~]# up2date -u razor-agents pyzor
>>
>> Fetching Obsoletes list for channel: rhel-i386-ws-4...
>>
>> Fetching Obsoletes list for channel: atrpms-stable...
>>
>> Fetching rpm headers...
>> ########################################
>>
>> Name                                    Version        Rel
>> ----------------------------------------------------------
>> pyzor                                   0.4.0          6.el4.at         
>> noarch
>> razor-agents                            2.82           14.el4.at.el4.at 
>> i386
>>
>>
>> Testing package set / solving RPM inter-dependencies...
>>
>> Downloading headers to solve dependencies...
>> busted2
>> <bound method RepoDirector.getHeader of
>> <up2date_client.repoDirector.RepoDirector instance at 0xb79cda8c>>
>> There was a fatal error communicating with the server. The message was:
>> The data returned from the server was incomplete
>>
>> Any ideas?
>>     
>
> Unfortunately it doesn't say which server it means. It could be that
> it breaks on rhn. If the apt metadata at ATrpms are incomplete, then
> many other users (not only up2date) woult hit the same bug. I checked
> with apt & smart and the metadata is being properly downloaded and
> processed.
>
> If you remove the apt line and it works, it has something to do with
>
> a) either ATrpms' metadata (unlikely)
> b) up2date's support of apt
>
> For b) try using the repomd metadata instead of apt.
>   


I don't know what has happened, but I just tried to re-run up2date
before posting a response and it worked as expected.  I haven't changed
anything on the network (since it's the weekend), but now all of the
sudden it's working again.  The odd thing is, it's been like this for
several days.  The mysterious internet genie strikes again ....

-Mike
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.atrpms.net/pipermail/atrpms-users/attachments/20060820/6e67e62e/attachment-0001.html