Your message dated Wed, 12 Dec 2012 19:19:04 +0100
with message-id
<cafx5sby+fjqcvrtsddr6yytsncfhw0+qovb93eadyowszqt...@mail.gmail.com>
and subject line Closing bugs of packages not in wheezy
has caused the Debian Bug report #312360,
regarding horde3: Unable to configure, no automatic configuration, no help at
all
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 [email protected]
immediately.)
--
312360: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=312360
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: horde3
Version: 3.0.4-4
Severity: important
When upgrading to Sarge from Woody, horde and imp are marked obsolete so
I removed them and selected horde3 and imp4 instead.
Horde doesn't ask any questions during installation, even when running
dpkg-reconfigure. There are no instructions on how to configure horde
anywhere that is immediately obvious.
After adding the following lines to httpd.conf, I was able to access
horde (kind of):
Alias /horde /user/share/horde3
Alias /horde3 /user/share/horde3
(I wanted to just use /horde so that my users wouldn't have to change
their bookmarks, but that doesn't seem to work even with the above line;
it tries to redirect to '/horde/horde3/' which doesn't exist.)
Even at this stage, using the horde3 URL, the very large and
complex configuration screens (which give no indication of which
questions are important and which aren't) are full of error messages
complaining about undefined indices in imp files.
I can not get horde or imp configured using this tool. I'm sure that I
could probably find some message board somewhere with a thread that
explains how to hack up the files to make it work, but my understanding
is that it's a bug if a Sarge package does not install smoothly (also if
there's no working upgrade path from Woody). The old horde package
asked the appropriate questions during installation and worked "out of
the box."
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.4.18-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages horde3 depends on:
ii apache [httpd] 1.3.33-6 versatile, high-performance HTTP s
ii libapache-mod-php4 [phpapi-2 4:4.3.10-15 server-side, HTML-embedded scripti
ii php4 4:4.3.10-15 server-side, HTML-embedded scripti
ii php4-cli [phpapi-20020918] 4:4.3.10-15 command-line interpreter for the p
ii php4-domxml 4:4.3.10-15 XMLv2 module for php4
ii php4-pear 4:4.3.10-15 PEAR - PHP Extension and Applicati
ii php4-pear-log 1.6.0-1.1 Log module for PEAR
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,
I'm closing all those bugs on Horde 3 packages. Horde 3 will not be in Wheezy.
Horde 5 is currently packaged as php-horde* packages in unstable. You
can test if the bug is still there and report in case it is.
Regards
--
Mathieu Parent
--- End Message ---
