[Yum] Spawning a temporary Yum Server: Header issues

Jesse Noller jnoller at gmail.com
Wed Apr 26 18:46:36 UTC 2006

This might sound like an oddball issue - but I have an application I
wish to spawn an internal HTTP Server (Via Python SimpleHTTPServer)
after executing createrepo on a local directory of RPMS and then tell
remote hosts to leverage the newly spawned HTTP server as the yum
server- the layout looks like this:

    ...some rpms
    repodata (from createrepo)

I spawn the HTTP server via:

import SimpleHTTPServer
import SocketServer

Handler = SimpleHTTPServer.SimpleHTTPRequestHandler
httpd = SocketServer.TCPServer(("", 9193), Handler)
while not StopServ:

And the client is given a custom yum repo file:

name=Fedora Core $releasever - $basearch - Released Updates

Now the problem arises when a yum-update is ran, for example, I have a
Samba update to push:

[root at foo /etc/yum.repos.d]# yum update
Setting up Update Process
Setting up repositories
updates-released          100% |=========================|  951 B    00:00
Reading repository metadata in from local files
Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Downloading header for samba-common to pack into transaction set.
samba-common-3.0.20-1.8.2 100% |=========================| 6.2 MB    00:00
[Errno -1] Header is not complete.
Trying other mirror.
Error: failure: samba-common-3.0.20-1.8.2.arc.i386.rpm from
updates-released: [Errno 256] No more mirrors to try.

I can see the HTTP connections hitting the spawn server - now, I
suspected this might have been due to the port, so I switched it to
port 80, that was not it - given there is no proxy between the two,
and the network is flat, I know that http connections are being
correctly handled/made.

I'm using FC4 with the latest revision of createrepo
(createrepo-0.4.4-1.noarch.rpm) - does anyone have any ideas or


More information about the Yum mailing list