On Wed, Jul 01, 2009 at 06:37:38PM -0600, John Wright wrote: > Package: wanna-build > Version: 0.58.6-1 > Severity: important > > wanna-build installs its config file as /etc/buildd/wanna-build.conf, > but the program expects to find it in /etc/wanna_build/wanna-build.conf. > I think this is a side effect of commit ee195178, which sets > WANNA_BUILD_SYSCONF_DIR.
Yes, this is correct. I meant to fix this before release, but it slipped through. I think the key question here is which of /etc/wanna-build/wanna-build.conf or /etc/buildd/wanna-build.conf is the correct long-term location for the wanna-build configuration file? Is it intimately tied to the buildd package? Is it installed standalone? Current practice is to have a single centralised wanna-build instance. However, it might be possible to integrate the current wanna-build SSH hacks in buildd into wanna-build and its configuration to allow for transparent proxying via SSH so that the local "wanna-build" command could talk to a remote wanna-build. In this case, we would have a "server" configuration for the main wanna-build database and a "client" configuration for the machines using it, and this might include a buildd-specific configuration in addition to the user configuration (i.e. both of these files could exist). It is easy to correct the code to use /etc/buildd/wanna-build.conf, rather than moving the configuration file (which is also quite possible, but requires some messing with the wanna-build maintainer scripts to migrate it to the new location). The latter would allow buildd to use a separate wanna-build configuration which would give flexibililty for future changes. I'm tempted to fix it in the code in the short term, and leave any longer term changes for future work. What do people think? Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `- GPG Public Key: 0x25BFB848 Please GPG sign your mail.
signature.asc
Description: Digital signature
