Well, there were some changes in the delete code which allows us to
keep actively used session files.

But while re-reading this bug again I think you were right to re-open the bug.

Anyway the mediawiki can install the file into
/etc/php5/modules-available/mediawiki.ini with required PHP directives
and issue php5enmod mediawiki in postinst (and php5dismod mediawiki in
prerm).

Ondrej.

On Fri, May 3, 2013 at 5:49 PM, Ian Jackson
<ijack...@chiark.greenend.org.uk> wrote:
> Debian Bug Tracking System writes ("Processed: Closed by mistake"):
>> Processing commands for cont...@bugs.debian.org:
>> > reopen 648823
>
> I should expand on this.  Ondrej wrote in the message that closed this
> bug:
>
>> Subject: This was fixed in 5.3.6-11
>>
>> Version: 5.3.6-11
>>
>> php5 (5.3.6-11) unstable; urgency=low
>>
>>   * Use more reasonable default number of processes for PHP5-FPM
>>   * Enable firebird support everywhere also in debian/rules
>>   * Don't delete still used session files (Closes: #626640)
>>   * Enable building of php5-interbase by adding Architecture: any
>>     to debian/control
>>   * Use dh_prep instead of dh_clean -k
>>
>>  -- Ond#ej Sur <ond...@debian.org>  Sat, 14 May 2011 22:15:32 +0200
>
> None of these changelog entries seem to relate to the problem
> described in this bug report.
>
> This bug is about the fact that the default session timeout is wrong
> for mediawiki.  To fix the bug, some steps would need to be taken to
> arrange for a different timeout for mediawiki (or the default changed
> globally).
>
> So I think the closure message was a mistake.  If I'm wrong then my
> apologies and please do explain.
>
> Thanks,
> Ian.
>
> _______________________________________________
> pkg-php-maint mailing list
> pkg-php-ma...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-php-maint



-- 
Ondřej Surý <ond...@sury.org>


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to