Your message dated Mon, 02 May 2016 01:32:00 +0000
with message-id <[email protected]>
and subject line Bug#816655: Removed package(s) from unstable
has caused the Debian Bug report #701789,
regarding phpbb3: When enabling Q&A Captcha after some runtime, need to purge
variables cache in all subdirs
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.)
--
701789: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701789
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: phpbb3
Version: 3.0.7-PL1-4
Severity: wishlist
I'm not sure this is worth a bug report.
It looks like an inherent feature / side effect of the Debian-specific
PHPBB setup, namely the multi-site additions.
It's worth knowing about, that's all...
I certainly do not venture a *patch* - I don't feel I know enough about
the Debian mods to the PHPBB upstream code base. And it feels more like
a design decision.
Could you maybe add an FAQ entry somewhere? Something like:
"if you're converting to Q&A Captcha after some time of operation
with graphical captcha, remember to purge cache in all the cache
subdirs belonging to the respective PHPBB board. You may want to
manually remove
/usr/share/phpbb3/www/cache/*/data_global.php
where some of * are relevant to the respective PHPBB board in question.
If you remove them all, it's not much of a problem - it's just a
cache.
Until you purge the cache, the Captcha plugin change won't get reflected
to the PHPBB web pages where Captcha is used.
If your forum board is only reachable via a single official URL
(including subdir), just use the Purge Cache admin button."
More specifically, you need to purge the cached version of a PHPBB
variable called captcha_plugin. This config variable is not tagged
"dynamic", because it hardly ever changes. Thus, *when* it actually
changes, combined with Debian's multi-site additions, you'll stumble
over the cached copies for all other combinations of ServerAlias/subdir/
(called $url_forum in Debian PHPBB internals) that point to the same
actual PHPBB root directory for the respective board.
Each such "forum URL" gets a different cache directory, and the option
to "purge cache" (in the PHPBB admin interface) only purges the cache
dir for the current URL (-> not all cache dirs for the current board).
The file that holds cached PHPBB variables is called data_global.php.
I've actually done the purge from command line on the forum machine.
I only have a single forum running. What I did was
rm `find cache/ -name data_global.php -print`
from within /usr/share/phpbb3/www .
I actually went through the process of finding the cause on the
upstream PHPBB forums, thus effectively violating their forum rules :-]
There's slightly more information in the forum thread:
https://www.phpbb.com/community/viewtopic.php?f=46&t=2173408
This may be a more generic "behavioral feature", affecting all PHPBB
config variables that are not tagged "dynamic".
Perhaps the "right" way to address this would be to enhance the logic
behind the "purge cache" admin button to purge the cache in all subdirs
related to the current board. Which may be somewhat difficult to
implement, as the factual identity stems from filesystem symlinks
and aliases in /etc/phpbb3/apache2.conf and /etc/apache2/sites-enabled/* ,
which has non-trivial semantics and is probably out of reach (permissions)
of the PHPBB engine anyway. Maybe the indentity could be inferred from some
PHPBB config variable, possibly the DB instance name or something like that...
Or maybe it's just me, allowing multiple DNS names for access to our single
forum (board), and keeping the default directory /phpbb alive (along with
direct URL root access). => another way to approach this would be to
allow just a single "cannonical" URL per forum board.
Which in my case would prevent the use of explicit dual ISP uplink...
I hope this helps :-)
Frank Rysanek
-- System Information:
Debian Release: 6.0.6
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages phpbb3 depends on:
ii apache2 2.2.16-6+squeeze10 Apache HTTP Server metapackage
ii apache2-mpm-prefork [ 2.2.16-6+squeeze10 Apache HTTP Server - traditional n
ii dbconfig-common 1.8.46+squeeze.0 common framework for packaging dat
ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management sy
ii libapache2-mod-php5 5.3.3-7+squeeze14 server-side, HTML-embedded scripti
ii mysql-client 5.1.66-0+squeeze1 MySQL database client (metapackage
ii mysql-client-5.1 [mys 5.1.66-0+squeeze1 MySQL database client binaries
ii php5-cli 5.3.3-7+squeeze14 command-line interpreter for the p
ii php5-gd 5.3.3-7+squeeze14 GD module for php5
ii php5-mysql 5.3.3-7+squeeze14 MySQL module for php5
ii postgresql-client 8.4.13-0squeeze1 front-end programs for PostgreSQL
ii postgresql-client-8.4 8.4.13-0squeeze1 front-end programs for PostgreSQL
ii ucf 3.0025+nmu1 Update Configuration File: preserv
Versions of packages phpbb3 recommends:
pn exim4 | mail-transport-agent <none> (no description available)
ii php5-imagick 3.0.0~rc1-1 ImageMagick module for php5
Versions of packages phpbb3 suggests:
ii mysql-server 5.1.66-0+squeeze1 MySQL database server (metapackage
ii mysql-server-5.1 [mysq 5.1.66-0+squeeze1 MySQL database server binaries and
pn phpbb3-l10n <none> (no description available)
-- debconf information:
phpbb3/password-confirm: (password omitted)
phpbb3/admin-pass-confirm: (password omitted)
phpbb3/pgsql/admin-pass: (password omitted)
phpbb3/mysql/app-pass: (password omitted)
phpbb3/mysql/admin-pass: (password omitted)
phpbb3/admin-pass: (password omitted)
phpbb3/pgsql/app-pass: (password omitted)
phpbb3/app-password-confirm: (password omitted)
* phpbb3/database-type: mysql
phpbb3/remote/newhost:
* phpbb3/mysql/admin-user: root
phpbb3/remote/host:
phpbb3/pgsql/manualconf:
phpbb3/dbconfig-remove:
phpbb3/admin-pass-ask:
phpbb3/db/basepath:
phpbb3/internal/reconfiguring: false
* phpbb3/httpd: apache2
phpbb3/internal/skip-preseed: false
* phpbb3/db/app-user: phpbb3
phpbb3/remove-error: abort
phpbb3/admin-pass-generated:
phpbb3/admin-pass-mismatch:
phpbb3/pgsql/authmethod-user:
phpbb3/dbconfig-reinstall: false
* phpbb3/db/dbname: phpbb3
phpbb3/upgrade-error: abort
phpbb3/pgsql/admin-user: postgres
phpbb3/install-error: abort
phpbb3/upgrade-backup: true
phpbb3/admin-pass-requirements:
phpbb3/remote/port:
phpbb3/pgsql/authmethod-admin: ident
phpbb3/dbconfig-upgrade: true
phpbb3/pgsql/no-empty-passwords:
phpbb3/purge: false
* phpbb3/dbconfig-install: true
* phpbb3/mysql/method: unix socket
phpbb3/passwords-do-not-match:
phpbb3/missing-db-package-error: abort
phpbb3/pgsql/changeconf: false
phpbb3/pgsql/method: unix socket
--- End Message ---
--- Begin Message ---
Version: 3.0.14-1+rm
Dear submitter,
as the package phpbb3 has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/816655
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
