Your message dated Thu, 6 Sep 2012 23:20:49 +0100
with message-id 
<capq4b8n3qzcjq7qe_ws4eblswimu_k+pvxckr_v6n_hdyvw...@mail.gmail.com>
and subject line Closing orphan/obsolete bugs (egroupware and phpgroupware)
has caused the Debian Bug report #505948,
regarding egroupware-core: Cannot setup after fresh install
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.)


-- 
505948: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=505948
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: egroupware-core
Version: 1.4.004-2.dfsg-4
Severity: important


Impossible to setup egroupware after installation. While trying to run the
setup it keeps propmting to enter header.inc.php setup due to:

Your header.inc.php needs upgrading.
WARNING!
MAKE BACKUPS!

header.inc.php version reports 1.28, so I guess it is rather a problem in
the code that verifies the header. Moreover, changing the version to 1.29 or
1.27 makes no difference.

According to an email in egroupware-users the prolem is that the
header.inc.php template is broken:

http://www.nabble.com/install-problem-1.6-stuck-in-header.inc.php-loop-td19131619s3741.html

I am still trying to get a good one, though.

-- System Information:
Debian Release: lenny/sid
 APT prefers testing
 APT policy: (500, 'testing')
Architecture: arm (armv5tejl)

Kernel: Linux 2.6.12.6-arm1
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages egroupware-core depends on:
ii  apache2                      2.2.9-10    Apache HTTP Server metapackage
ii  apache2-mpm-prefork [apache2 2.2.9-10    Apache HTTP Server -
traditional n
ii  debconf [debconf-2.0]        1.5.22      Debian configuration management
sy
ii  egroupware-egw-pear          1.4.004-2-1 modified PEAR modules for
eGroupWa
ii  libapache2-mod-php5          5.2.6-5     server-side, HTML-embedded
scripti
ii  perl                         5.10.0-17   Larry Wall's Practical
Extraction
ii  php-fpdf                     1.53.dfsg-6 PHP class to generate PDF files
ii  php-log                      1.10.0-1    Log module for PEAR
ii  php-pear                     5.2.6-5     PEAR - PHP Extension and
Applicati
ii  php5-cli                     5.2.6-5     command-line interpreter for
the p
ii  php5-gd                      5.2.6-5     GD module for php5
ii  php5-mysql                   5.2.6-5     MySQL module for php5

Versions of packages egroupware-core recommends:
ii  mysql-client-5.0 [mysql-clien 5.0.51a-17 MySQL database client binaries

Versions of packages egroupware-core suggests:
ii  egroupware              1.4.004-2.dfsg-4 web-based groupware suite -
metapa
pn  php5-auth-pam           <none>           (no description available)
ii  php5-imap               5.2.6-5          IMAP module for php5
ii  php5-ldap               5.2.6-5          LDAP module for php5
ii  php5-mcrypt             5.2.6-5          MCrypt module for php5
ii  php5-mhash              5.2.6-5          MHASH module for php5

-- debconf information:
 egroupware/header/password/mismatch:
* egroupware/configuration/note:
* egroupware/header/user: admin

--- End Message ---
--- Begin Message ---
Hello,

Thanks for your interest in Debian, and sorry that the bugs were not
attended in due time.

egroupware and phpgroupware were removed from Debian unstable a long
time ago [1][2], 2+ years, and they are only present in "oldstable" at
this point, already unsupported and which is going to be replaced soon
when the new stable is released.

[1] http://packages.qa.debian.org/e/egroupware/news/20100317T153845Z.html
[2] http://packages.qa.debian.org/p/phpgroupware/news/20100608T182550Z.html

The bugs are thus now orphan (no maintainer assigned), so they are not
going to be noticed by anybody nor dealt with.  It seems unlikely that
the packages are resurrected soon, and indeed in the time elapsed
probably many of these bug reports are invalid.  I am thus closing
them now.

If you think that they should be kept open for some reason, or that
they should be reassigned to other packages offering similar
functionality, please feel free to reopen these bugs.

Regards.
-- 
Manuel A. Fernandez Montecelo <[email protected]>

--- End Message ---

Reply via email to