Hi Gary! You are probably the first one reporting feedback on the VDD Generator on Windows. Keep it up!
Also, could you send all such bug reports to the mailing list as well ?
On Thu, 2007-07-05 at 10:30 -0700, Gary Brunton wrote:
> Kristis,
>
> I've been trying to figure out how I can use the VDD generator. After
> taking a look at Cygwin, I've decided that I don't want to go that
> route. So instead I started looking into the your code a little more.
>
> First off I removed all of the code within the VDD_Generator.pm file
> that had to do with generating the pdf and html files. I just wanted
> it to create the xml and sgml files. I had an issue right away.
>
> I actually noticed this when I called the scmbug_install_glue program.
> When running the glue program the documentation states that you should
> use file:///c:/SVN/TestProduct. But a chdir error occurs stating that
> it cannot change in to the /c:/SVN/TestProduct directory. Removing an
> extra forward slash after file works though
> (file://c:/SVN/TestProduct).
>
> When I was messing around with the vdd generator I received the same
> error so I removed a forward slash as I did with the glue install but
> when I did that I received the following error: svn: Unable to open
> repository 'file://c:/SVN/PensionLookup/tags/PensionLookup_RELEASE_1-0-0'
>
> Looking into this more I noticed that svn.exe must include all three
> forward slashes. I think the local_repository_directory function
> within the SCM_Functions.pm file should probably strip the extra
> forward slash out. I changed the line from:
>
> $local_repository_directory =~ s/^file:\/\///;
>
> to
>
> $local_repository_directory =~ s/^file:\/\/\///;
>
> and it appears to work for the vdd generator. I also tried it on the
> scmbug_install_glue.pl program and it works. Now I can enter in
> file:///c:/SVN/PensionLookup as documented. I don't know if this
> change will have any other side effects though. Maybe you might know?
The manual is confusing because it shows a Subversion example under
UNIX. There one should use the prefix "file://" (2 not 3 "/"s). For
example:
scmbug_install_glue --repository=file:///tmp ...
The 2 "/"s in "file:///tmp" are for "file://" and the other one is for
"/tmp". So I believe you ran the tool incorrectly. You should have for
example run under Windows:
scmbug_install_glue --repository=file://c:/SVN/TestProduct
Indeed, if I apply your change here the testsuite fails.
> I continued on and ran into another issue. The VDD_Generator.pm script
> (within the "XML VDD into various formats" section) calls and executes
> the xsltproc.exe program. I received a path error when this would
> happen because the path of c:\Program Files\..... contains spaces.
> Adding quotes around the $arguments->{ stylesheet_file } declaration
> fixed the proglem. So I changed line
>
> $cmd = "xsltproc.exe -o " . $arguments->{ output_directory } . "/" .
> $VDD_DEFAULT_OUTPUT_FILE_SGML . " " . $arguments->{ stylesheet_file }
> . " " . $arguments->{ output_directory } . "/" .
> $VDD_DEFAULT_OUTPUT_FILE_XML;
>
> to
>
> $cmd = "xsltproc.exe -o " . $arguments->{ output_directory } . "/" .
> $VDD_DEFAULT_OUTPUT_FILE_SGML . " \"" . $arguments->{ stylesheet_file
> } . "\" " . $arguments->{ output_directory } . "/" .
> $VDD_DEFAULT_OUTPUT_FILE_XML;
This is certainly an ommission. Applied. Thanks!
> Now when the vdd generator program runs I get the vdd.xml and vdd.sgml
> files. Great!!! I've been trying to find a program that will convert
> sgml files to pdf or whatever and did find one called GemDoc. I don't
> really like it for a number of reasons but mostly because it is no
> longer supported and it does not have a command line interface. I'm
> still looking for something else. I might just create an xslt file and
> convert the xml to html. I'm not sure yet.
>
> There does seem to be another problem though. The xml that is created
> contains some weird entries for the comment's name and id. I'm seeing
> the following:
>
> <all_bugs>
> <name>1091</name>
> <data>
> <bug_id>1091</bug_id>
> <comments>
> <name>inaccurate_46</name>
> <data>
> <author_email>[EMAIL PROTECTED]</author_email>
> <author_name>Gary Brunton</author_name>
> <author_username>[EMAIL PROTECTED]</author_username>
> <comment_id>inaccurate_46</comment_id>
> <content>I tested the dbf file and it seems to work.</content>
> <date>2007-07-03 21:15</date>
> </data>
> </comments>
> <comments>
> <name>inaccurate_47</name>
> <data>
> <author_email>[EMAIL PROTECTED]</author_email>
> <author_name>Gary Brunton</author_name>
> <author_username>[EMAIL PROTECTED]</author_username>
> <comment_id>inaccurate_47</comment_id>
> <content>Resolved -> Fixed</content>
> <date>2007-07-03 21:15</date>
> </data>
> </comments>
> <priority>P2</priority>
> <resolution>FIXED</resolution>
> <severity>normal</severity>
> <status>RESOLVED</status>
> <summary>Add DSP to PensionLookup</summary>
> </data>
> </all_bugs>
>
> What is with "inaccurate_" ? I also don't know what the number that
> follows the inaccurate_ word relates to either. I looked it up and it
> is not the "Comment #" within Bugzilla. Any thoughts on this?
Right. This is reported in the manual:
http://files.mkgnu.net/files/scmbug/SCMBUG_RELEASE_0-19-18/manual/html-single/manual.html#BUGZILLA
The real issue is that Bugzilla lacks a per-bug comment id:
http://bugzilla.mkgnu.net/show_bug.cgi?id=763
Dmitri, we need to add support for this in the Bugzilla 3.0 backend by
the way. This feature seems to be available in 3.0. Look at:
https://bugzilla.mozilla.org/show_bug.cgi?id=225221#c55
> Wow, this is a long email. Sorry about that, it's a bad habit of mine.
>
> Once again thanks for your time and effort on this terrific program.
No, no, keep sending any feedback and bug reports here. We can't
possibly test the system on all architectures and unless people report
issues some things won't get fixed.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
