Your message dated Mon, 26 Feb 2007 01:18:45 +0200
with message-id <[EMAIL PROTECTED]>
and subject line [request-tracker-maintainers] Bug#411604: request-tracker2.4: 
Modules stated as required do not exist
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: request-tracker3.4
Version: 3.4.1-2
Severity: important

Trying to set up the package, I discover that it's installed in an
unrunnable configuration requiring extensive manual editing.  Doing
that, I find instructions in apache-modperl.conf that 

# You will need to enable the Apache modules: perl, actions, rewrite

However, "modules-config enable [perl|actions|rewrite" does nothing.  So
these modules are both required and nonexistent.  Thanks.

I'm sure the real modules have some other names, for instance
"libapache-mod-rewrite", but why make the user figure that out?  And why
"install" the program but not completely?  Isn't that what APT is for?


-- Package-specific info:
Changed files:
  etc/request-tracker3.4/RT_SiteConfig.pm

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.16.29-xenU-rimu-20061214
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages request-tracker3.4 depends on:
ii  apache                  1.3.33-6sarge3   versatile, high-performance HTTP s
ii  apache2-mpm-worker [apa 2.0.54-5sarge1   high speed threaded model for Apac
ii  libapache-dbi-perl      0.94-2           Connect apache server to database 
ii  libapache-mod-perl      1.29.0.3-6sarge3 integration of perl with the Apach
ii  libapache-request-perl  1.1-0.1          Generic Apache Request Library
ii  libapache-session-perl  1.60-2           Perl modules for keeping persisten
ii  libcache-cache-perl     1.04-1           Managed caches of persistent infor
ii  libcache-simple-timedex 0.21-1           Perl module to cache and expire ke
ii  libclass-returnvalue-pe 0.52-1           A return-value object that lets yo
ii  libdbd-mysql-perl       2.9006-1         A Perl5 database interface to the 
ii  libdbi-perl             1.46-6           Perl5 database interface by Tim Bu
ii  libdbix-searchbuilder-p 1.26-1           Encapsulate SQL queries and rows i
ii  libexception-class-perl 1.20-1           a module that allows you to declar
ii  libfcgi-perl            0.67-1           FastCGI Perl module
ii  libfreezethaw-perl      0.43-2           converting Perl structures to stri
ii  libhtml-mason-perl      1:1.26-1         HTML::Mason Perl module
ii  libhtml-parser-perl     3.45-2           A collection of modules that parse
ii  libhtml-scrubber-perl   0.08-1           Perl extension for scrubbing/sanit
ii  liblocale-maketext-fuzz 0.02-1           Maketext from already interpolated
ii  liblocale-maketext-lexi 0.49-1           Lexicon-handling backends for "Loc
ii  liblog-dispatch-perl    2.10-1           Dispatches messages to multiple Lo
ii  libmailtools-perl       1.62-1           Manipulate email in perl programs
ii  libmime-perl            5.417-1          Perl5 modules for MIME-compliant m
ii  libmldbm-perl           2.01-1           Store multidimensional hash struct
ii  libmodule-versions-repo 1.02-1           Report versions of all modules in 
ii  libparams-validate-perl 0.76-1           validate parameters to Perl method
ii  libregexp-common-perl   2.120-1          Provide commonly requested regular
ii  libterm-readkey-perl    2.21-1.3         A perl module for simple terminal 
ii  libtest-inline-perl     0.16-1           Embed tests and code examples in P
ii  libtext-autoformat-perl 1.12-3           Perl module for automatic text wra
ii  libtext-quoted-perl     1.8-1            Extract the structure of a quoted 
ii  libtext-template-perl   1.44-1.1         Text::Template perl module
ii  libtext-wrapper-perl    1.000-2          Simple word wrapping routine
ii  libtime-modules-perl    2003.1126-2      Various Perl modules for time/date
ii  libtree-simple-perl     1.14-1           A simple tree object
ii  libxml-rss-perl         1.05-1           Perl module for managing RSS (RDF 
ii  perl                    5.8.4-8sarge5    Larry Wall's Practical Extraction 
ii  postfix [mail-transport 2.1.5-9          A high-performance mail transport 
ii  rt3.4-clients           3.4.1-2          Mail gateway and command-line inte
ii  sysklogd [system-log-da 1.4.1-17         System Logging Daemon

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 3.4.4-1

On Mon, Feb 19, 2007 at 10:05:58PM -0500, Carl Fink wrote:
> Package: request-tracker3.4
> Version: 3.4.1-2
> Severity: important
> 
> Trying to set up the package, I discover that it's installed in an
> unrunnable configuration requiring extensive manual editing.  Doing
> that, I find instructions in apache-modperl.conf that 
> 
> # You will need to enable the Apache modules: perl, actions, rewrite
> 
> However, "modules-config enable [perl|actions|rewrite" does nothing.  So
> these modules are both required and nonexistent.  Thanks.
> 
> I'm sure the real modules have some other names, for instance
> "libapache-mod-rewrite", but why make the user figure that out?  And why
> "install" the program but not completely?  Isn't that what APT is for?

Hi,

the 'actions' and 'rewrite' modules are included in the base Apache
packages. The 'perl' module needs libapache-mod-perl, which was
not installed by default with request-tracker3.4 on sarge. This has
been fixed since, and a default install of the request-tracker3.4
(or request-tracker3.6, for that matter) package will now pull in
libapache-mod-perl as well.

The modules should be enabled by default, but 'modules-config' handles
them just fine if needed when called with the proper syntax, for example:

# modules-config enable apache rewrite

As for the need for manual configuration: RT is a complex package, and
its integration with the database and web server are expected to vary
significantly between installations. That said, not working out of the
box is obviously a shortcoming, and I intend to work on that after Etch
is released.

I'm closing this bug, feel free to reply if you think this is not
satisfactory.

Cheers,
-- 
Niko Tyni   [EMAIL PROTECTED]

--- End Message ---

Reply via email to