On Wed, 29 Oct 2008 14:03:08 +0200, Jonathan Dieter wrote: What are the exact requirements? Are presto-utils and deltarpm available for the target platform, e.g. EL5? The README in presto-utils reads as if all that is needed is the path to a normal rpms repository (i.e. the parent of the repodata dir). Updating presto repositories is just like creating them for the first time? It shouldn't be difficult to add another module to the pushscript. See bottom 20 lines of http://cvs.fedoraproject.org/viewvc/extras-buildsys/utils/pushscript/Push... where modules like RepoPrune, RepoView, RepoBuild (createrepo) are executed. They have access to configuration parameters so they can construct a list of repository paths. A Presto or PrestoBuild module would work similarly.

On Wed, 2008-10-29 at 14:26 +0100, Michael Schwendt wrote: Whichever machine builds the deltarpms needs loads of RAM (mainly for the really big rpms). Specifically, you need (uncompressed_size_of_rpm * 3). Other than that, not much I know deltarpm is available for EL-5, and if presto-utils isn't, I'll push it out. Yes, though if you're doing rpmfusion-free and rpmfusion-updates-free, ATM that path needs to be a parent directory of both. In the test repositories, I kludge it by making a rpmfusion+updates-free that contains symlinks to rpmfusion-free and rpmfusion-updates-free. (If that's not clear, check out the directory layout in http://lesloueizeh.com/f9/i386 and you should see what I mean.) Yes Yes, that looks *way* simpler than the proposed method in Fedora. I've got some time tomorrow; I'll see what I can come up with. Jonathan

On Thu, 2008-11-06 at 00:58 +0100, Michael Schwendt wrote: Yeah, fair enough. I've only got 1GB of RAM on the server that's hosting the test repositories, so when I get alienarena-data updates (and the like), I just manually kill the makedeltarpm process. Less than optimal, I know Yes. Yeah, that makes sense. Again, if you add a new config value for the rpmfusion-release directory and create a temp directory with symlinks to rpmfusion-release and rpmfusion-updates, it will work fine. On a side note, I don't mirror updates-testing at all, so I haven't worked out the best way to do deltarpms for updates-testing. Obviously, regenerating all the deltarpms when moving a package from updates-testing to updates doesn't make a whole lot of sense, but just copying the deltarpms over may not work properly either (you might have deltarpms from rpms that never made it into updates). Yeah, that's because the createprestorepo programmer is lousy at keeping his documentation up-to-date. Oops. The correct usage of createprestorepo is 'createprestorepo <base dir> <location to put prestodelta.xml>'. Then you use modifyrepo to insert prestodelta.xml into repodata. Sorry about that. Jonathan