Failure to install request-tracker4 in Jessie Newest
I would like to get request tracker working but the main package fails to
install. I am getting the following errors:
sudo aptitude install request-tracker4
The following NEW packages will be installed:
request-tracker4{b}
0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 3,071 kB of archives. After unpacking 22.9 MB will be used.
The following packages have unmet dependencies:
request-tracker4 : Depends: libhtml-mason-perl (>= 1:1.43) which is a
virtual package.
Depends: libapache-session-perl (>= 1.53) which is a
virtual package.
Depends: libdbix-searchbuilder-perl (>= 1.66) but it is
not going to be installed.
Depends: liblocale-maketext-fuzzy-perl (>= 0.11) which
is a virtual package.
Depends: libtext-wikiformat-perl which is a virtual
package.
Depends: libmodule-versions-report-perl (>= 1.03) which
is a virtual package.
Depends: libtree-simple-perl (>= 1.04) which is a
virtual package.
Depends: libperlio-eol-perl which is a virtual package.
Depends: libdata-ical-perl which is a virtual package.
Depends: libhtml-quoted-perl which is a virtual package.
Depends: libtext-password-pronounceable-perl which is a
virtual package.
Depends: libregexp-common-net-cidr-perl which is a
virtual package.
Depends: libregexp-ipv6-perl which is a virtual package.
Depends: libcgi-psgi-perl (>= 0.12) which is a virtual
package.
Depends: libhtml-mason-psgihandler-perl (>= 0.52) which
is a virtual package.
Depends: libdata-guid-perl which is a virtual package.
Depends: libhtml-formattext-withlinks-perl (>= 0.14)
which is a virtual package.
Depends: libhtml-formattext-withlinks-andtables-perl
which is a virtual package.
Depends: libcrypt-x509-perl which is a virtual package.
Depends: libcss-squish-perl which is a virtual package.
The following actions will resolve these dependencies:
Keep the following packages at their current version:
1) request-tracker4 [Not Installed]
Accept this solution? [Y/n/q/?] q
There is no other "solution" aside from quiting. For some bizarre reason
those packages seem to not exist as names :(
Any help would be appreciated in advance.
--
"The death of one man is a tragedy, the death of 10 million is a statistic"
-- Joseph Stalin
"Omnia mutantur, nihil interit"
(Translation:
Everything changes, nothing is lost.)
-- Ovid, _Metamorphoses_
Re: Failure to install request-tracker4 in Jessie Newest
On 04/06/2016 10:12 PM, John T. Haggerty wrote: > I would like to get request tracker working but the main package fails to > install. I am getting the following errors: [...] > > request-tracker4 : Depends: libhtml-mason-perl (>= 1:1.43) which is a > virtual package. libhtml-mason-perl is not actually a virtual package - and the only way APT would think that is if you don't have an APT source that includes it, but you do have another APT source that references it. Since the current version of request-tracker4 is available in both the main Debian archive as well as the security repository (because of a security update from last August, see DSA 3335-1), my suspicion is that you _only_ have the security archive enabled in your sources.list _or_ the download of the main sources.list failed for some reason. Therefore, answers to the following questions will allow us to figure out what is wrong on your system: - what is your /etc/apt/sources.list? (Also, are there files in /etc/apt/sources.list.d?) - what happens if you do "apt-get update" or "apt update" or "aptitude update"? Regards, Christian signature.asc Description: OpenPGP digital signature
Re: Failure to install request-tracker4 in Jessie Newest
There is a /etc/apt/sources.list.d/ but only have a chrome.txt or something like that in there. On Wed, Apr 6, 2016 at 2:18 PM, Christian Seiler wrote: > On 04/06/2016 10:12 PM, John T. Haggerty wrote: > > I would like to get request tracker working but the main package fails to > > install. I am getting the following errors: [...] > > > > request-tracker4 : Depends: libhtml-mason-perl (>= 1:1.43) which is a > > virtual package. > > libhtml-mason-perl is not actually a virtual package - and the only > way APT would think that is if you don't have an APT source that > includes it, but you do have another APT source that references it. > > Since the current version of request-tracker4 is available in both > the main Debian archive as well as the security repository (because > of a security update from last August, see DSA 3335-1), my suspicion > is that you _only_ have the security archive enabled in your > sources.list _or_ the download of the main sources.list failed for > some reason. > > Therefore, answers to the following questions will allow us to figure > out what is wrong on your system: > > - what is your /etc/apt/sources.list? >(Also, are there files in /etc/apt/sources.list.d?) > - what happens if you do "apt-get update" or "apt update" or >"aptitude update"? > > Regards, > Christian > > -- "The death of one man is a tragedy, the death of 10 million is a statistic" -- Joseph Stalin "Omnia mutantur, nihil interit" (Translation: Everything changes, nothing is lost.) -- Ovid, _Metamorphoses_ sources.list Description: Binary data
Re: Failure to install request-tracker4 in Jessie Newest
On 04/06/2016 10:23 PM, John T. Haggerty wrote: > There is a /etc/apt/sources.list.d/ but only have a chrome.txt or something > like that in there. That's good to know, but that doesn't answer my other questions: what is the contents of your /etc/apt/sources.list (without .d) and what happens when you do the following as root? apt-get update Without that information, we won't be able to help you. Regards, Christian signature.asc Description: OpenPGP digital signature
Re: Failure to install request-tracker4 in Jessie Newest
The update commend as root updated the list and the like, Reattempting the install also failed. The contents are: # # deb cdrom:[Debian GNU/Linux 8.3.0 _Jessie_ - Official amd64 DVD Binary-1 20160123-19:03]/ jessie contrib main deb cdrom:[Debian GNU/Linux 8.3.0 _Jessie_ - Official amd64 DVD Binary-1 20160123-19:03]/ jessie contrib main deb cdrom:[Debian GNU/Linux 8.3.0 _Jessie_ - Official amd64 DVD Binary-2 20160123-19:03]/ jessie contrib main deb cdrom:[Debian GNU/Linux 8.3.0 _Jessie_ - Official amd64 DVD Binary-3 20160123-19:03]/ jessie contrib main deb http://security.debian.org/ jessie/updates main contrib deb-src http://security.debian.org/ jessie/updates main contrib # jessie-updates, previously known as 'volatile' # A network mirror was not selected during install. The following entries # are provided as examples, but you should amend them as appropriate # for your mirror of choice. # # deb http://ftp.debian.org/debian/ jessie-updates main contrib # deb-src http://ftp.debian.org/debian/ jessie-updates main contrib # wheezy-backports deb http://ftp.debian.org/debian/ wheezy-backports main On Apr 6, 2016 14:26, "Christian Seiler" wrote: > On 04/06/2016 10:23 PM, John T. Haggerty wrote: > > There is a /etc/apt/sources.list.d/ but only have a chrome.txt or > something > > like that in there. > > That's good to know, but that doesn't answer my other questions: what > is the contents of your /etc/apt/sources.list (without .d) and what > happens when you do the following as root? > > apt-get update > > Without that information, we won't be able to help you. > > Regards, > Christian > >
Re: Failure to install request-tracker4 in Jessie Newest
Hi, On 04/07/2016 12:14 AM, John T. Haggerty wrote: > deb cdrom:[Debian GNU/Linux 8.3.0 _Jessie_ - Official amd64 DVD Binary-1 > 20160123-19:03]/ jessie contrib main > > deb cdrom:[Debian GNU/Linux 8.3.0 _Jessie_ - Official amd64 DVD Binary-2 > 20160123-19:03]/ jessie contrib main > > deb cdrom:[Debian GNU/Linux 8.3.0 _Jessie_ - Official amd64 DVD Binary-3 > 20160123-19:03]/ jessie contrib main So here you still have the DVDs as your primary archive source, and no network mirror. This is possible to do, but if for any reason you (or something you ran where you didn't necessarily know the side effects of) deleted your /var/lib/apt/lists/ at some point, apt-get update will not automatically restore the package lists from the CDs. You have two options: A. Switch over to use a network mirror for installations. In that case, remove the cdrom lines (but _only_ the cdrom lines) and add something like the following to your sources.list: deb http://httpredir.debian.org/debian jessie main Then run apt-get update again. B. Continue using the DVDs, but have APT re-read the lists of packages. For that, also remove the cdrom lines, and then run the following command: apt-cdrom add It will prompt you to insert the DVD. After it has copied the list from the DVD and you get the command line back, run it again and repeat the process for all 3 DVDs. Then run apt-get update again. After either of these procedures, you should be able to install the package you wanted to install. IMPORTANT: There's a subtle difference between both of the methods: the network mirrors carry only the _latest_ Jessie point release, which is now 8.4. So if you add a network mirror, there will be a few upgrades available and you'll upgrade to that next point release. If you stick with the DVDs, you'll remain on 8.3 with the exception of security updates, which you have enabled. > # jessie-updates, previously known as 'volatile' > # A network mirror was not selected during install. The following entries > # are provided as examples, but you should amend them as appropriate > # for your mirror of choice. > # > # deb http://ftp.debian.org/debian/ jessie-updates main contrib > # deb-src http://ftp.debian.org/debian/ jessie-updates main contrib > # wheezy-backports > deb http://ftp.debian.org/debian/ wheezy-backports main This has nothing to do with your problem, but I would not recommend using wheezy-backports in combination with Jessie. (It shouldn't hurt, as all packages in wheezy-backports should also be in jessie in basically the same version, but it's not what you should have there.) If you need backports _for_ jessie, replace that with jessie-backports. See http://backports.debian.org/ and http://backports.debian.org/Instructions/ for details. Regards, Christian signature.asc Description: OpenPGP digital signature
Re: Failure to install request-tracker4 in Jessie Newest
That was able to work, however at the moment I've run into an issue that I think I had years before namely the inability of the base installation (even with the questions that the system asks during configuration of request-tracker4) failing to give anything but a 404 error when hitting up localhost/rt. I can get the basic apache page under localhost however. So far the tutorials seem to be tailored for anything other than debian, or a "it worked,no problems" response from most of them. Ideas? On Wed, Apr 6, 2016 at 4:36 PM, Christian Seiler wrote: > Hi, > > On 04/07/2016 12:14 AM, John T. Haggerty wrote: > > deb cdrom:[Debian GNU/Linux 8.3.0 _Jessie_ - Official amd64 DVD Binary-1 > > 20160123-19:03]/ jessie contrib main > > > > deb cdrom:[Debian GNU/Linux 8.3.0 _Jessie_ - Official amd64 DVD Binary-2 > > 20160123-19:03]/ jessie contrib main > > > > deb cdrom:[Debian GNU/Linux 8.3.0 _Jessie_ - Official amd64 DVD Binary-3 > > 20160123-19:03]/ jessie contrib main > > So here you still have the DVDs as your primary archive source, and no > network mirror. This is possible to do, but if for any reason you (or > something you ran where you didn't necessarily know the side effects > of) deleted your /var/lib/apt/lists/ at some point, apt-get update will > not automatically restore the package lists from the CDs. > > You have two options: > > A. Switch over to use a network mirror for installations. In that case, > remove the cdrom lines (but _only_ the cdrom lines) and add something > like the following to your sources.list: > deb http://httpredir.debian.org/debian jessie main > Then run apt-get update again. > > B. Continue using the DVDs, but have APT re-read the lists of packages. > For that, also remove the cdrom lines, and then run the following > command: > apt-cdrom add > It will prompt you to insert the DVD. After it has copied the list > from the DVD and you get the command line back, run it again and repeat > the process for all 3 DVDs. Then run apt-get update again. > > After either of these procedures, you should be able to install the > package you wanted to install. > > IMPORTANT: > > There's a subtle difference between both of the methods: the network > mirrors carry only the _latest_ Jessie point release, which is now > 8.4. So if you add a network mirror, there will be a few upgrades > available and you'll upgrade to that next point release. If you stick > with the DVDs, you'll remain on 8.3 with the exception of security > updates, which you have enabled. > > > # jessie-updates, previously known as 'volatile' > > # A network mirror was not selected during install. The following > entries > > # are provided as examples, but you should amend them as appropriate > > # for your mirror of choice. > > # > > # deb http://ftp.debian.org/debian/ jessie-updates main contrib > > # deb-src http://ftp.debian.org/debian/ jessie-updates main contrib > > # wheezy-backports > > deb http://ftp.debian.org/debian/ wheezy-backports main > > This has nothing to do with your problem, but I would not recommend > using wheezy-backports in combination with Jessie. (It shouldn't > hurt, as all packages in wheezy-backports should also be in jessie > in basically the same version, but it's not what you should have > there.) If you need backports _for_ jessie, replace that with > jessie-backports. See http://backports.debian.org/ and > http://backports.debian.org/Instructions/ for details. > > Regards, > Christian > > -- "The death of one man is a tragedy, the death of 10 million is a statistic" -- Joseph Stalin "Omnia mutantur, nihil interit" (Translation: Everything changes, nothing is lost.) -- Ovid, _Metamorphoses_
Re: Failure to install request-tracker4 in Jessie Newest
On 04/07/2016 10:41 PM, John T. Haggerty wrote: > That was able to work, however at the moment I've run into an issue that I > think I had years before namely the inability of the base installation > (even with the questions that the system asks during configuration of > request-tracker4) failing to give anything but a 404 error when hitting up > localhost/rt. RT is a complicated piece of software (it interacts both with the web and mail server) and there is no sane way to make it work out of the box without some configuration. Please read, after installing request-tracker4: /usr/share/doc/request-tracker4/README.Debian.gz /usr/share/doc/request-tracker4/NOTES.Debian.gz These will explain how request-tracker can be installed and configured on Debian. Generally speaking: Debian-specific installation notes can often be found in /usr/share/doc/PACKAGENAME/README.Debian.gz. Regards, Christian signature.asc Description: OpenPGP digital signature
Re: Failure to install request-tracker4 in Jessie Newest
So I was able to get into the advice on these installations but it seems
that I've hit another snag on this, namely activating fast cgi, and getting
it to be loaded by RT. Apparently fastcgi is installed in Apache, but
getting Apache to load RT's call to fastcgi (? I guess) is failing.
The apache.conf is below:
# This is the main Apache server configuration file. It contains the
# configuration directives that give the server its instructions.
# See http://httpd.apache.org/docs/2.4/ for detailed information about
# the directives and /usr/share/doc/apache2/README.Debian about Debian
specific
# hints.
#
#
# Summary of how the Apache 2 configuration works in Debian:
# The Apache 2 web server configuration in Debian is quite different to
# upstream's suggested way to configure the web server. This is because
Debian's
# default Apache2 installation attempts to make adding and removing modules,
# virtual hosts, and extra configuration directives as flexible as
possible, in
# order to make automating the changes and administering the server as easy
as
# possible.
# It is split into several files forming the configuration hierarchy
outlined
# below, all located in the /etc/apache2/ directory:
#
# /etc/apache2/
# |-- apache2.conf
# | `-- ports.conf
# |-- mods-enabled
# | |-- *.load
# | `-- *.conf
# |-- conf-enabled
# | `-- *.conf
# `-- sites-enabled
# `-- *.conf
#
#
# * apache2.conf is the main configuration file (this file). It puts the
pieces
# together by including all remaining configuration files when starting
up the
# web server.
#
# * ports.conf is always included from the main configuration file. It is
# supposed to determine listening ports for incoming connections which
can be
# customized anytime.
#
# * Configuration files in the mods-enabled/, conf-enabled/ and
sites-enabled/
# directories contain particular configuration snippets which manage
modules,
# global configuration fragments, or virtual host configurations,
# respectively.
#
# They are activated by symlinking available configuration files from
their
# respective *-available/ counterparts. These should be managed by using
our
# helpers a2enmod/a2dismod, a2ensite/a2dissite and a2enconf/a2disconf. See
# their respective man pages for detailed information.
#
# * The binary is called apache2. Due to the use of environment variables,
in
# the default configuration, apache2 needs to be started/stopped with
# /etc/init.d/apache2 or apache2ctl. Calling /usr/bin/apache2 directly
will not
# work with the default configuration.
# Global configuration
#
#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# NOTE! If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the Mutex documentation (available
# NOTE! If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the Mutex documentation (available
# at http://httpd.apache.org/docs/2.4/mod/core.html#mutex>);
# you will save yourself a lot of trouble.
#
# Do NOT add a slash at the end of the directory path.
#
#ServerRoot "/etc/apache2"
#
# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
#
Mutex file:${APACHE_LOCK_DIR} default
#
# PidFile: The file in which the server should record its process
# identification number when it starts.
# This needs to be set in /etc/apache2/envvars
#
PidFile ${APACHE_PID_FILE}
#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 300
#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On
#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100
#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 5
# These need to be set in /etc/apache2/envvars
User ${APACHE_RUN_USER}
Group ${APACHE_RUN_GROUP}
#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
#
HostnameLookups On
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a
# container, error messages relating to that virtual host will be
# If you do not specify an ErrorLog directive within a
# container, error messages relating to that virtual host will be
# logged here. If you *do* define an error logfil
Re: Failure to install request-tracker4 in Jessie Newest
I really hope I don't have to mess around with the source in this case,
because in theory Debian has this already from the package I installed
right?
I'm referring to the following citation:
https://www.question-defense.com/2009/12/29/invalid-command-fastcgiexternalserver-perhaps-misspelled-or-defined-by-a-module-not-included-in-the-server-configuration
On Thu, Apr 7, 2016 at 4:10 PM, John T. Haggerty wrote:
> So I was able to get into the advice on these installations but it seems
> that I've hit another snag on this, namely activating fast cgi, and getting
> it to be loaded by RT. Apparently fastcgi is installed in Apache, but
> getting Apache to load RT's call to fastcgi (? I guess) is failing.
>
> The apache.conf is below:
>
> # This is the main Apache server configuration file. It contains the
> # configuration directives that give the server its instructions.
> # See http://httpd.apache.org/docs/2.4/ for detailed information about
> # the directives and /usr/share/doc/apache2/README.Debian about Debian
> specific
> # hints.
> #
> #
> # Summary of how the Apache 2 configuration works in Debian:
> # The Apache 2 web server configuration in Debian is quite different to
> # upstream's suggested way to configure the web server. This is because
> Debian's
> # default Apache2 installation attempts to make adding and removing
> modules,
> # virtual hosts, and extra configuration directives as flexible as
> possible, in
> # order to make automating the changes and administering the server as
> easy as
> # possible.
>
> # It is split into several files forming the configuration hierarchy
> outlined
> # below, all located in the /etc/apache2/ directory:
> #
> # /etc/apache2/
> # |-- apache2.conf
> # | `-- ports.conf
> # |-- mods-enabled
> # | |-- *.load
> # | `-- *.conf
> # |-- conf-enabled
> # | `-- *.conf
> # `-- sites-enabled
> # `-- *.conf
> #
> #
> # * apache2.conf is the main configuration file (this file). It puts the
> pieces
> # together by including all remaining configuration files when starting
> up the
> # web server.
> #
> # * ports.conf is always included from the main configuration file. It is
> # supposed to determine listening ports for incoming connections which
> can be
> # customized anytime.
> #
> # * Configuration files in the mods-enabled/, conf-enabled/ and
> sites-enabled/
> # directories contain particular configuration snippets which manage
> modules,
> # global configuration fragments, or virtual host configurations,
> # respectively.
> #
> # They are activated by symlinking available configuration files from
> their
> # respective *-available/ counterparts. These should be managed by using
> our
> # helpers a2enmod/a2dismod, a2ensite/a2dissite and a2enconf/a2disconf.
> See
> # their respective man pages for detailed information.
> #
> # * The binary is called apache2. Due to the use of environment variables,
> in
> # the default configuration, apache2 needs to be started/stopped with
> # /etc/init.d/apache2 or apache2ctl. Calling /usr/bin/apache2 directly
> will not
> # work with the default configuration.
>
>
> # Global configuration
> #
>
> #
> # ServerRoot: The top of the directory tree under which the server's
> # configuration, error, and log files are kept.
> #
> # NOTE! If you intend to place this on an NFS (or otherwise network)
> # mounted filesystem then please read the Mutex documentation (available
> # NOTE! If you intend to place this on an NFS (or otherwise network)
> # mounted filesystem then please read the Mutex documentation (available
> # at http://httpd.apache.org/docs/2.4/mod/core.html#mutex>);
> # you will save yourself a lot of trouble.
> #
> # Do NOT add a slash at the end of the directory path.
> #
> #ServerRoot "/etc/apache2"
>
> #
> # The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
> #
> Mutex file:${APACHE_LOCK_DIR} default
>
> #
> # PidFile: The file in which the server should record its process
> # identification number when it starts.
> # This needs to be set in /etc/apache2/envvars
> #
> PidFile ${APACHE_PID_FILE}
>
> #
> # Timeout: The number of seconds before receives and sends time out.
> #
> Timeout 300
>
> #
> # KeepAlive: Whether or not to allow persistent connections (more than
> # one request per connection). Set to "Off" to deactivate.
> #
> KeepAlive On
>
> #
> # MaxKeepAliveRequests: The maximum number of requests to allow
> # during a persistent connection. Set to 0 to allow an unlimited amount.
> # We recommend you leave this number high, for maximum performance.
> #
> MaxKeepAliveRequests 100
>
> #
> # KeepAliveTimeout: Number of seconds to wait for the next request from the
> # same client on the same connection.
> #
> KeepAliveTimeout 5
>
>
> # These need to be set in /etc/apache2/envvars
> User ${APACHE_RUN_USER}
> Group ${APACHE_RUN_GROUP}
>
> #
> # HostnameLookups: Log the names of clie
