On Mon, Apr 05, 2004 at 06:47:06PM +0200, GCS wrote: > IMHO it was _NOT_ a problem of Subversion, but you might overlook the > ... > So my bet would be that the configuration step failed in a previous > apt-get [install|upgrade], but as Apache was unpacked, you could start > and use it. This time, dpkg tried again to put the package's state into > a sane one, so it re-tried to configure Apache independent of > Subversion, but failed again for the reason you already gave.
Makes sense. sorry for mistakenly attributing the bug to subversion. -- Nicolas Chauvat logilab.fr - services en informatique avanc�e et gestion de connaissances
