Received: from [193.112.141.254] (grouse.ravenbrook.com [193.112.141.254])
	by raven.ravenbrook.com (8.9.3/8.9.3) with ESMTP id TAA01165
	for <p4dti-staff@ravenbrook.com>; Wed, 18 Jul 2001 19:50:28 +0100 (BST)
Mime-Version: 1.0
X-Sender: gdr@pop3
Message-Id: <p0500196bb77b845ce57d@[193.112.141.254]>
Date: Wed, 18 Jul 2001 19:50:24 +0100
To: p4dti-staff@ravenbrook.com
From: Gareth Rees <gdr@ravenbrook.com>
Subject: Bugzilla release 1.1.2 test report
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

This is a test report for release 1.1.2 of the Bugzilla integration.

1. rpm -e p4dti failed on swan.ravenbrook.com with the following error:

cannot remove /opt/p4dti - directory not empty
uid=220(p4dti) gid=220(p4dti) groups=220(p4dti)

The offending file turned out to be .bash_history.  What was this doing there?

2. The RPM is called p4dti-1.1.2-1.i386.rpm, but the AG (section 4.3) 
and readme.txt think it's called p4dti-bugzilla-1.1.2-1.i386.rpm. 
The discrepancy is confusing.  I think the AG and readme.txt are 
right in this instance (if we had other integrations that ran on 
Linux they would have different RPMS).

3. It's a shame that the Bugzilla integration's config.py starts with 
dt_name = "TeamTrack".  Can't we improve on this?  (There used to be 
two configuration files, one for each integration.  Why did we change 
to one configuration file?)

4. The Bugzilla 2.12 patch succeeds even if the Bugzilla sources have 
already been patched.  You end up with two Perforce sections in the 
bug form and two "p4dti" parameters.