Package: fai-client Severity: Wishlist I just fought quite a while wondering why fai doesn't use the up to date configspace from subversion.
finally I saw: svn: Unknown hostname 'svn.lazy' somewhere in the fai output. I configured fai to use an svn repository as config source, and resolving it's name failed. Instead of failing fast, softupdate used the cached configspace then. I think, by default it should stop immediately with an error, because normally, when people use svn, they want an up to date version, not the one from the last softupdate(which is not changing anything, anyway), because it's clearly an error when I configure an svn location, but updating it fails. A switch could be provided to force the old configspace(but people could get that, too, by editing fai.conf and pointing it to the cached location). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
