[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#387046: marked as done (ITP: request-tracker3.6 -- extensible trouble-ticket tracking system)

Your message dated Thu, 12 Oct 2006 11:23:19 -0700
with message-id <E1GY5DD-0000zM-Uv@spohr.debian.org>
and subject line Bug#387046: fixed in request-tracker3.6 3.6.1-1
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: wnpp
Owner: Niko Tyni <ntyni@iki.fi>
Severity: wishlist

* Package name    : request-tracker3.6
  Version         : 3.6.1
  Upstream Author : Jesse Vincent <jesse@bestpractical.com>
* URL             : http://bestpractical.com/rt/
* License         : GPL v2
  Programming Lang: Perl
  Description     : Extensible trouble-ticket tracking system

 Request Tracker (RT) is an enterprise-grade ticketing system which
 enables a group of people to intelligently and efficiently manage
 tasks, issues, and requests submitted by a community of users. It
 features a web, email and command-line interfaces (see the package
 rt3.6-clients).
 .
 This is the 3.6 series of RT, it can be installed alongside the 3.4
 series without any problems.
 .
 Written in object-oriented Perl, RT is a high-level, portable,
 platform independent system that eases collaboration within
 organizations and makes it easy for them to take care of their
 customers.
 .
 RT manages key tasks such as the identification, prioritization,
 assignment, resolution and notification required by
 enterprise-critical applications including project management, help
 desk, NOC ticketing, CRM and software development.


We have formed an Alioth team for maintaining Request Tracker and
will be adopting the currently orphaned request-tracker3.4 package as
well. Interested developers are naturally welcome to join.

We are hoping to get both 3.4 and 3.6 into etch, and then remove 3.4
before etch+1 when users have had their time to upgrade. This would be
similar to what happened with sarge, which had both 3.0 and 3.4.

Cheers,
-- 
Niko Tyni		ntyni@iki.fi

--- End Message ---
--- Begin Message --- 
Source: request-tracker3.6
Source-Version: 3.6.1-1

We believe that the bug you reported is fixed in the latest version of
request-tracker3.6, which is due to be installed in the Debian FTP archive:

request-tracker3.6_3.6.1-1.diff.gz
  to pool/main/r/request-tracker3.6/request-tracker3.6_3.6.1-1.diff.gz
request-tracker3.6_3.6.1-1.dsc
  to pool/main/r/request-tracker3.6/request-tracker3.6_3.6.1-1.dsc
request-tracker3.6_3.6.1-1_all.deb
  to pool/main/r/request-tracker3.6/request-tracker3.6_3.6.1-1_all.deb
request-tracker3.6_3.6.1.orig.tar.gz
  to pool/main/r/request-tracker3.6/request-tracker3.6_3.6.1.orig.tar.gz
rt3.6-apache2_3.6.1-1_all.deb
  to pool/main/r/request-tracker3.6/rt3.6-apache2_3.6.1-1_all.deb
rt3.6-apache_3.6.1-1_all.deb
  to pool/main/r/request-tracker3.6/rt3.6-apache_3.6.1-1_all.deb
rt3.6-clients_3.6.1-1_all.deb
  to pool/main/r/request-tracker3.6/rt3.6-clients_3.6.1-1_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 387046@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Toni Mueller <toni@debian.org> (supplier of updated request-tracker3.6 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sat, 30 Sep 2006 23:13:14 +0200
Source: request-tracker3.6
Binary: rt3.6-apache2 rt3.6-apache request-tracker3.6 rt3.6-clients
Architecture: source all
Version: 3.6.1-1
Distribution: unstable
Urgency: low
Maintainer: Debian Request Tracker Group <pkg-request-tracker-maintainers@lists.alioth.debian.org>
Changed-By: Toni Mueller <toni@debian.org>
Description: 
 request-tracker3.6 - Extensible trouble-ticket tracking system
 rt3.6-apache - Apache 1 specific files for request-tracker3.6
 rt3.6-apache2 - Apache 2 specific files for request-tracker3.6
 rt3.6-clients - Mail gateway and command-line interface to request-tracker3.6
Closes: 387046
Changes: 
 request-tracker3.6 (3.6.1-1) unstable; urgency=low
 .
   [ Niko Tyni ]
   * Initial release. (Closes: #387046)
   * Packaging structure taken from the request-tracker3.4 package version
     3.4.5-1 with the important bits altered where needed.
 .
   [ Jacob Helwig ]
   * Fixed patches to cleanly apply.
   * Fixed version numbers in long descriptions of
     rt3.6-(clients|apache|apache2)
   * Changed speedy-cgi-perl to suggested.
 .
   [ Toni Mueller ]
   * small fix to debian/rules
   * added myself as uploader, but Niko and Jacob did all the heavy
     lifting
Files: 
 199fb5d85d6fff09a1bbef0bb4fa93e0 869 misc optional request-tracker3.6_3.6.1-1.dsc
 40c5a828fadaeef9e150255a517d0b17 1545708 misc optional request-tracker3.6_3.6.1.orig.tar.gz
 342561deb8663101c68c379cd4b92c9c 20679 misc optional request-tracker3.6_3.6.1-1.diff.gz
 e6b3ec5491b5f8ff3184b40106d0d86c 1314710 misc optional request-tracker3.6_3.6.1-1_all.deb
 5bdfae2b422c75d116f3213450c03176 146096 misc optional rt3.6-clients_3.6.1-1_all.deb
 7a1d0be0a865a49f6007dde1e7886d51 116298 misc optional rt3.6-apache_3.6.1-1_all.deb
 ced9cc70c260afae9a086b4882bb4786 116678 misc optional rt3.6-apache2_3.6.1-1_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFHt7qfoEUoHXLGtIRAn3gAJ4gs36OE5Hv+KZaWEoA8E3p8h/bMgCfZ0qq
q171h09LjlIX2R65+yTm41w=
=fWm0
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: