Your message dated Fri, 23 Jan 2009 13:47:04 +0000
with message-id <e1lqmne-0006mq...@ries.debian.org>
and subject line Bug#512750: fixed in request-tracker3.6 3.6.7-5
has caused the Debian Bug report #512750,
regarding request-tracker3.6: SQLite is unsupported, documentation needed
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
512750: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=512750
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: request-tracker3.6
Version: 3.6.7-4
Severity: serious
Justification: maintainer's opinion
By default 'apt-get install request-tracker3.6' will pull in
rt3.6-db-sqlite as the first choice, and users opting for automatic
database management (dbconfig-common) will get an SQLite installation
with no further (database-related) questions.
This is unfortunate because upstream considers the SQLite database
backend unsupported and intended for development and testing purposes
only. The default database choice was thus a bad call on my part, as I
have recently realized.
My rationale for the choice was to get a working installation
automatically, and SQLite is just about the only way to do that currently.
It mostly works and we have received no bug reports about it, but upstream
says it has a few known problems.
While some people will probably realize they should use MySQL or
PostgreSQL for production installations, this leaves the rest with an
installation that's officially unsupported. And naturally many of them
are going to go to the upstream rt-users list for support anyway.
It is too late to change the functionality for Lenny, the only thing
we can do is to add documentation.
As discussed with upstream, the plan is to insert prominent warnings
in the request-tracker3.6 and rt3.6-db-sqlite package descriptions and
README.Debian.
Also, we intend to put a recipe for mysql/pg migration on the web at
http://pkg-request-tracker.alioth.debian.org/ and make README.Debian
point there. This way we can improve the recipe even after the release
and upstream can refer the end users there.
I'm setting the initial severity to 'serious': not getting these
changes in lenny means we need to discuss if dropping RT from the release
altogether is the next best alternative. We intend to get a fixed package
in sid RSN, so hopefully it doesn't come to that.
--
Niko Tyni nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: request-tracker3.6
Source-Version: 3.6.7-5
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.7-5.diff.gz
to pool/main/r/request-tracker3.6/request-tracker3.6_3.6.7-5.diff.gz
request-tracker3.6_3.6.7-5.dsc
to pool/main/r/request-tracker3.6/request-tracker3.6_3.6.7-5.dsc
request-tracker3.6_3.6.7-5_all.deb
to pool/main/r/request-tracker3.6/request-tracker3.6_3.6.7-5_all.deb
rt3.6-apache2_3.6.7-5_all.deb
to pool/main/r/request-tracker3.6/rt3.6-apache2_3.6.7-5_all.deb
rt3.6-clients_3.6.7-5_all.deb
to pool/main/r/request-tracker3.6/rt3.6-clients_3.6.7-5_all.deb
rt3.6-db-mysql_3.6.7-5_all.deb
to pool/main/r/request-tracker3.6/rt3.6-db-mysql_3.6.7-5_all.deb
rt3.6-db-postgresql_3.6.7-5_all.deb
to pool/main/r/request-tracker3.6/rt3.6-db-postgresql_3.6.7-5_all.deb
rt3.6-db-sqlite_3.6.7-5_all.deb
to pool/main/r/request-tracker3.6/rt3.6-db-sqlite_3.6.7-5_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 512...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Dominic Hargreaves <d...@earth.li> (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 ftpmas...@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Fri, 23 Jan 2009 13:12:24 +0000
Source: request-tracker3.6
Binary: request-tracker3.6 rt3.6-clients rt3.6-apache2 rt3.6-db-postgresql
rt3.6-db-mysql rt3.6-db-sqlite
Architecture: source all
Version: 3.6.7-5
Distribution: unstable
Urgency: high
Maintainer: Debian Request Tracker Group
<pkg-request-tracker-maintain...@lists.alioth.debian.org>
Changed-By: Dominic Hargreaves <d...@earth.li>
Description:
request-tracker3.6 - Extensible trouble-ticket tracking system
rt3.6-apache2 - Apache 2 specific files for request-tracker3.6
rt3.6-clients - Mail gateway and command-line interface to request-tracker3.6
rt3.6-db-mysql - MySQL database backend for request-tracker3.6
rt3.6-db-postgresql - PostgreSQL database backend for request-tracker3.6
rt3.6-db-sqlite - SQLite database backend for request-tracker3.6
Closes: 511246 512750
Changes:
request-tracker3.6 (3.6.7-5) unstable; urgency=high
.
* Urgency high due to RC bug-fix
* Add myself to Uploaders
* In package description, clarify that RT 3.4 is no longer available
in Debian
* Document the fact that SQLite isn't recommended in production
(Closes: #512750)
* Swedish debconf translation, thanks to Martin Bagge (Closes: #511246)
Checksums-Sha1:
7c62b2df869562e090d4e484c9a421f0f0129e94 1595 request-tracker3.6_3.6.7-5.dsc
100e08704d2f47e8caa918ca6a31dd71c0140f92 50193
request-tracker3.6_3.6.7-5.diff.gz
40045c31a82ee61b6acfe056d583eba768505d1f 1540056
request-tracker3.6_3.6.7-5_all.deb
90d5f0c7a4d76b7bf72a6ee7732190817efa82c4 215578 rt3.6-clients_3.6.7-5_all.deb
2e7e5af806dd54745a898a5f9e0f2388fd1cdae9 187032 rt3.6-apache2_3.6.7-5_all.deb
8b01c9b08adff8751cbcfbb34f1d1549c5e33cbb 185330
rt3.6-db-postgresql_3.6.7-5_all.deb
34fd65ef9a10d8daf5ee1c0d78b1e0989dda740f 185322 rt3.6-db-mysql_3.6.7-5_all.deb
c787542a1b2870e33603ecfdd692cc2b2a6c019f 185426 rt3.6-db-sqlite_3.6.7-5_all.deb
Checksums-Sha256:
123b4f5084ba83c8749799dcc9da6f94c21f75b16197578f1336a0529e290adc 1595
request-tracker3.6_3.6.7-5.dsc
ef71b57f47857649a903ebee7e4f2d529527fdcfaf9726157f788078056b9548 50193
request-tracker3.6_3.6.7-5.diff.gz
f0accf4b0aebd22495cc21457c82ab5e8013972b64ba932bbefabf4daef6468b 1540056
request-tracker3.6_3.6.7-5_all.deb
b09ea31bbda57647dd2ef17a0cc23b60e78ea05ce93777683a55a2a0cc909672 215578
rt3.6-clients_3.6.7-5_all.deb
e03049ffd6d32bec16f52cf6554fa05cb8f9b1a12fadb549eb403798e8869d85 187032
rt3.6-apache2_3.6.7-5_all.deb
4e6d2e7edc34cd479a771fac6c8a7414c90f7d60fd3ea0d53aaf436769529847 185330
rt3.6-db-postgresql_3.6.7-5_all.deb
0f05aac515c58f4dd8a98b4e36454f0829be5f01facac8d3d5c430ab1d32cfcb 185322
rt3.6-db-mysql_3.6.7-5_all.deb
79c6c9db1eb3bc7c286d6d89b7877ccec8dc6c0dcaf781c62bf0ea0f459512a5 185426
rt3.6-db-sqlite_3.6.7-5_all.deb
Files:
c6bd45b524d1c48dbbf3b09e57c34fb5 1595 misc optional
request-tracker3.6_3.6.7-5.dsc
ba2ec9f91062dcf2356005298c829217 50193 misc optional
request-tracker3.6_3.6.7-5.diff.gz
c140a6e837519f22ce4eeda24735980e 1540056 misc optional
request-tracker3.6_3.6.7-5_all.deb
82d7afe975187eed5d050756ea2937bc 215578 misc optional
rt3.6-clients_3.6.7-5_all.deb
0348ce08366d3da0cfca48fe64a4c156 187032 misc optional
rt3.6-apache2_3.6.7-5_all.deb
5b05434b3f1720e6e26d958a6f1af480 185330 misc optional
rt3.6-db-postgresql_3.6.7-5_all.deb
4f67922399bd1e38412944edeeca5533 185322 misc optional
rt3.6-db-mysql_3.6.7-5_all.deb
38e785237120940c050dd7e2e238e36b 185426 misc optional
rt3.6-db-sqlite_3.6.7-5_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iD8DBQFJecSsYzuFKFF44qURAv6kAJ4y5iRI/jI6O5zgdeU2KJCpxgioDwCguh1q
+fV53GJNL22rNWsGqlDtvlg=
=JA6A
-----END PGP SIGNATURE-----
--- End Message ---
