Extremely Off-Topic & for the faint of heart: I've put up my work-in-progress PhotoShelf RPM (and other perl-modules needed by it) on my webserver. (I can upload it to contrib, but as it's still work-in-progress I'll do that later when it actually works ;-) ). http://d10179.upc-d.chello.nl/build/fixes/contrib/PhotoShelf-1.05-1mdk.src.rpm http://d10179.upc-d.chello.nl/build/fixes/contrib/perl-Archive-Tar-0.22-1mdk.src.rpm http://d10179.upc-d.chello.nl/build/fixes/contrib/perl-Archive-Zip-0.10-1mdk.src.rpm http://d10179.upc-d.chello.nl/build/fixes/contrib/perl-DBD-Pg-0.95-1mdk.src.rpm http://d10179.upc-d.chello.nl/build/fixes/contrib/perl-File-MMagic-1.11-1mdk.src.rpm http://d10179.upc-d.chello.nl/build/fixes/contrib/perl-IO-String-1.01-1mdk.src.rpm http://d10179.upc-d.chello.nl/build/fixes/contrib/perl-Image-Info-1.04-1mdk.src.rpm I beleive the rest of the perl modules required are either in cooker / contrib. Now... after you've installed all this, it won't work, YET. But hey, release early, right? The problem with the package at the moment lays in the way the database is being setup. I don't think that the "PhotoShelf" postgresql user has enough permisions to the database... This should be EZ to solve for a DB guru... Suggestions / comments / fixes are welcome. Stefan van der Eijk
