It seems obvious now, it was a permissions problem on the repository. You're right that none of the directories were created, the hooks directory just contained the standard templates that come with subversion. I ran the installer again as root with no problems.
However, now I'm still having an issue where it doesn't seem to be updating bugzilla. Nothing is printed by scmbug to indicate an error or success. I think it should be working though, if my log message is too short for example I get an error 14. I did disable username verification, would this have any impact? I was hoping to see everything working and then decide whether to properly configure the user mappings. Is there a way to get a more verbose output of what is going on? Thanks -----Original Message----- From: Kristis Makris [mailto:[EMAIL PROTECTED] Sent: Monday, December 18, 2006 5:39 PM To: Allen, Brett Cc: [email protected] Subject: Re: [scmbug-users] Installation problems Hi Allen, This is certainly a bug. You should have gotten a better error message and the glue installation should have bailed out. http://bugzilla.mkgnu.net/show_bug.cgi?id=907 On Mon, 2006-12-18 at 16:34 -0600, Allen, Brett wrote: > I'm trying to install and configure scmbug, but I think the > installation may not have been successful. Specifically, I can't tell > if any hook scripts have been inserted into my subversion repository > (located at /var/svnroot). When I used the glue installer I got the > following: > > >>>>>>>>> > [EMAIL PROTECTED]:~/downloads$ scmbug_install_glue --scm=Subversion > --product=TestProduct --repository=/var/svnroot --bug=1 > --daemon=127.0.0.1 --binary-paths=/usr/bin This is the installation > script of the Scmbug glue. > The glue will be installed in repository: /var/svnroot. > This is a repository for the Subversion SCM tool. > The product name in the bug tracking system is TestProduct. > The integration glue will be committed against bug 1. > The IP address of the Scmbug integration daemon to contact is > 127.0.0.1. > The binary paths used are: /usr/bin. > ------------- > Press Enter to continue or Ctrl-C to cancel > > print() on closed filehandle NEW_CONFIGURATION_FILE at > /usr/share/scmbug/lib//Scmbug/Tools/Glue_Installer.pm line 546. It seems that something went wrong in the process of: - reading /usr/share/scmbug/glue/etc/scmbug/glue.conf.template - modifying it - writing it back in /var/svnroot/etc/scmbug/glue.conf The error is probably in the last step. I wonder if this was a permissions error in /var/svnroot. It's probably the case that /var/svnroot/etc and /var/svnroot/etc/scmbug were not even created. > The documentation didn't say what should be expected for the temp > files, but for me the folder Scmbug.21874 was just an empty folder in > both cases. There has been no change to bug #1 in bugzilla, and I It's ok for the folder to be empty. Currently, it is non-empty only when integrating with CVS, because an actual checkout of the repository is needed. > don't see any scripts in /var/svnroot/hooks. I notice in section Do you see a /var/svnroot/hooks/etc directory ? > 7.1.2 of the documentation there should be files at > /var/svnroot/hooks/etc/scmbug, so I think the glue installer didn't > work correctly. > > Any advice on what my problem might be? Thanks I wonder if /var/svnroot is owned by a different user than the one running the glue installer. We had plans for fixing the ownership, but have yet to release that version to the public: http://bugzilla.mkgnu.net/show_bug.cgi?id=869 _______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
