severity 397457 normal
On Sat, 3 Mar 2007, Steve Langasek wrote:
Uh, no, the php.ini file is only supposed to be replaced by the php package
if the administrator *approves* of having the new version installed. That's
the administrator's choice; if they choose to discard local changes to this
config file from the sarge version, then yeah, any changes from php-ming are
going to fall out, but that's hardly RC any more than it's RC when the same
thing happens to an admin allowing a conffile to be overwritten.
In the upgrade, there are lots of good things that make it desirable to
just say "Use the new version". It can be very easy to not notice that
one of the lines at the bottom needs to be preserved. It's still
self-inflicted, but could be commonly self-inflicted.
I've lowered the priority because I don't have a good defence since
this package isn't actually in Sarge, and don't want to consume any more
of everyones time on this bug. I'll also probably just close it as fixed
since the original problem was addressed.
And yes, installing a per-extension file to the conf.d directory is
absolutely preferable, but not RC in my opinion.
Absolutely. I've prepared -11 packages that fix this and closes 404159.
They are in the hands of my regular sponsor, so hopefully they will be
uploaded soon. We both feel this is a worthwhile fix on it's own merits,
so I'll make a request that they be accepted into Etch once they have
been uploaded.
Stuart
Stuart R. Anderson [EMAIL PROTECTED]
Network & Software Engineering http://www.netsweng.com/
1024D/37A79149: 0791 D3B8 9A4C 2CDC A31F
BD03 0A62 E534 37A7 9149
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
