Re: up2date -u gives a an error in up2date.solveDependencies

[ On Wednesday, February 6, 2002 at 16:53:49 (-0500), John Berninger wrote: ]
> Subject: Re: [Current-server] up2date -u gives a an error in up2date.solveDependencies
>
 > > >I just tested this on a vanilla (stock) 7.2 system, as root, using the
 > > >RHL + updates tree on the server side, and didn't get this error
 > > >message.  Are you running the server as root or as an unpriviledged
 > > >user?  Can you send your configuration file, and a listing of the
 > > >permissions on your RPM directories (i.e. owner and mode)?
 > > 
 > > I won't be at the site until friday morning, so I can't send the config 
 > > file. What I can say is:
 >         Friday works for me.  Gives me more time to actually breathe.
 > :)
 > 
 > > The config file has one single channel, with one single directory 
 > > (testing :-). And this directory is actually remote mounted from another 
 > > server, so definitely all files and directories are read only (but all 
 > > have permissions 0644 or 0755 for directories).
 >         Those permissions are correct; the directory with the current
 > database needs to be writable by the user you're running current as, but
 > the RPM directories (I don't think) need to be writable.  The NFS-ness
 > /shouldn't/ present an issue...

Oh yes, didnt' answer all your questions. The current server is
running as root. The current database is writable indeed, in fact I
placed it under /etc/current/<channelname>. There is plenty of disk
space for this on the current server.

CU, Joe