Attached are various patches for BE, adding zip archive support, adding a new vcs command, printing full UUIDs during new and add and fixing xml import.
Re: fixing xml import, if you take an XML dump including closed issues for bugseverywhere.org and then try importing it into a fresh empty BE repo, you get several faults. This really ought to be a test case in the unit tests I think. The first is that BE tries unicoding an already unicoded output from saxutils. The second is that the created field is empty for some of the older bugs, and that trips the parser. And the third is that there are references to bug ids which don't exist, and the ignore flag on the command line doesn't stop a fatal app exit like it's supposed to. I didn't fix the last bug. Instead I edited the XML dump to remove references to the offending bug id :) Niall -- Technology & Consulting Services - ned Productions Limited. http://www.nedproductions.biz/. VAT reg: IE 9708311Q. Company no: 472909. My Work Portfolio: http://careers.stackoverflow.com/nialldouglas/
The following section of this message contains a file attachment
prepared for transmission using the Internet MIME message format.
If you are using Pegasus Mail, or any other MIME-compliant system,
you should be able to save it or view it from within your mailer.
If you cannot, please ask your system administrator for assistance.
---- File information -----------
File: be_import_xml_bug_fix.patch
Date: 1 Mar 2012, 12:14
Size: 1680 bytes.
Type: Unknown
be_import_xml_bug_fix.patch
Description: Binary data
The following section of this message contains a file attachment
prepared for transmission using the Internet MIME message format.
If you are using Pegasus Mail, or any other MIME-compliant system,
you should be able to save it or view it from within your mailer.
If you cannot, please ask your system administrator for assistance.
---- File information -----------
File: be_new_add_uuid_print.patch
Date: 1 Mar 2012, 12:00
Size: 1287 bytes.
Type: Unknown
be_new_add_uuid_print.patch
Description: Binary data
The following section of this message contains a file attachment
prepared for transmission using the Internet MIME message format.
If you are using Pegasus Mail, or any other MIME-compliant system,
you should be able to save it or view it from within your mailer.
If you cannot, please ask your system administrator for assistance.
---- File information -----------
File: be_vcs_command.patch
Date: 1 Mar 2012, 11:59
Size: 3105 bytes.
Type: Unknown
be_vcs_command.patch
Description: Binary data
The following section of this message contains a file attachment
prepared for transmission using the Internet MIME message format.
If you are using Pegasus Mail, or any other MIME-compliant system,
you should be able to save it or view it from within your mailer.
If you cannot, please ask your system administrator for assistance.
---- File information -----------
File: be_zip_support.patch
Date: 1 Mar 2012, 11:57
Size: 1656 bytes.
Type: Unknown
be_zip_support.patch
Description: Binary data
_______________________________________________ Be-devel mailing list Be-devel@bugseverywhere.org http://void.printf.net/cgi-bin/mailman/listinfo/be-devel
