Your message dated Tue, 24 Mar 2020 03:54:36 +0000
with message-id <e1jgaec-0001il...@fasolo.debian.org>
and subject line Bug#954779: Removed package(s) from unstable
has caused the Debian Bug report #929631,
regarding Could session.gc_probability being non-default be documented better ?
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 ow...@bugs.debian.org
immediately.)
--
929631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929631
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php7.3
Version: 7.3.4-2
Severity: minor
Hi,
I found the a somewhat lingering bug in Ubuntu which just as much
applies to Debian.
Hence I thought the best would be to forward that to you so that we
can go the same route on handling it.
The behavior is quite old since
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595706
I have found quite some refs, but not one directly asking for that yet
that would be solved.
I mean https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831752 is the
same bug, but closed for 7.0 being removed.
I didn't want to revive old bugs on my own, but obviously feel free to
close this and reassing the old one if you prefer that. Just let me
know so I can follow.
## From here on I'm quoting the original bug that Ubuntu got ##
The Ubuntu distribution of PHP doesn't use the usual PHP mechanism of
session garbage collection. It sets "session.gc_probability" to zero
in the php.ini file, thus making it seem like garbage collection is
disabled. In fact it still occurs but with a cron job.
In my Docker image, the PHP "sessionclean" program is being executed
and it seems that this uses the "session.gc_maxlifetime" setting from
the apache2 version of the php.ini file. However this is non-obvious
and not documented in the php.ini file. Thus when recently rebuilding
my Docker image for my web service, I started getting what seemed to
be premature session timeouts and I couldn't figure out why and I
ended up raising a bug on the PHP team
(https://bugs.php.net/bug.php?id=76368).
If the Ubuntu team is going to modify the PHP package so it differs in
behaviour from the description in the PHP provided documentation, then
they need to provide updated documentation.
I would suggest that the simplest solution is to update the php.ini
file so that where "session.gc_probability" is set to zero there is a
short paragraph saying why (because it is handled by the cron job) and
also make it clear somewhere in that file that the
"session.gc_maxlifetime" setting is still relevant even though
"session.gc_probability" is zero.
--- End Message ---
--- Begin Message ---
Version: 7.3.15-3+rm
Dear submitter,
as the package php7.3 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/954779
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
