On Sat, Jul 24, 2010 at 03:25:54AM +0200, Jaap Winius wrote:
> Quoting Zetas <zetas_at_gshellz.org>:
> >I dont know if its still maintained or not, but when using the deb
> >source on the main website it fails almost every time when
> >installing either the server or the client on debian lenny or
> >squeeze... So i've had to compile from  source mostly.
> 
> I see what you mean. When attempting to browse the ftp server, at
> first I couldn't even connect (Argh... FTP needs to die). When
...
> The target package and its six dependencies downloaded okay, albeit
> slowly, but then something goes wrong with coda-update. Maybe I'll

Not sure why the download was slow for you, the machine isn't busy or
swapped out at all. The largest and busiest process is probably clamav's
daemon. However, it may just be ftp that is slow, most people just use
http (just replace ftp with http as shown in the last section of
    http://www.coda.cs.cmu.edu/mirrors.html

> eventually I did, I was pleased to see that the files in the squeeze
> directory are mostly dated from March this year -- same as those in
> the lenny directory.

They are the same, I normally only build different binaries when there
are significant library conflicts. The .deb packages are built in a
Debian-stable chroot and then tested if they install on a couple of
different Debian and Ubuntu installations.

> Nevertheless, on a minimal lenny system, several attempts to install
> the coda-server package failed:
> 
>    [...]
>    Setting up liblwp2 (2.6) ...
>    Setting up liblua5.1-0 (5.1.3-1) ...
>    Setting up librpc2-5 (2.10) ...
>    Setting up coda-update (6.9.5) ...
>    invoke-rc.d: initscript coda-update, action "start" failed.
>    dpkg: error processing coda-update (--configure):
>     subprocess post-installation script returned error exit status 6

Curious, it worked here, but I probably upgraded from 6.9.4, maybe a
directory is missing. I'd like to know where the startup is failing,
could you run,

    sh -x /etc/init.d/coda-update start

Jan