Hey Christoph,
I saw this failure while packaging 7.1.0beta3, and assume it might be
related to your update:
FAIL SQLite3 open_basedir checks
[ext/sqlite3/tests/sqlite3_21_security.phpt]
========DIFF========
006-
007- Warning: SQLite3::__construct(): open_basedir restriction in effect.
File(%s) is not within the allowed path(s): (.) in
%ssqlite3_21_security.php on line %d
008- Exception: open_basedir prohibits opening %s in
%ssqlite3_21_security.php:%d
009- Stack trace:
010- #0 %ssqlite3_21_security.php(%d): SQLite3->__construct('%s')
011- #1 {main}
========DONE========
Can you please look into this in time for RC1?
Thanks,
- Davey
On Thu, Aug 11, 2016 at 12:08 AM, Christoph M. Becker <cmbecke...@gmx.de>
wrote:
> On 10.08.2016 at 16:01, Anatol Belski wrote:
>
> > Hi Christoph,
> >
> >> -----Original Message-----
> >> From: Christoph M. Becker [mailto:cmbecke...@gmx.de]
> >> Sent: Monday, August 8, 2016 11:23 PM
> >> To: internals@lists.php.net; Anatol Belski <anatol....@belski.net>
> >> Subject: [PHP-DEV] SQLite 3.14
> >>
> >> Hi!
> >>
> >> SQLite 3.14 has been released today. It brings some improvements and
> new
> >> features, and fixes a few bugs, see
> >> <http://www.sqlite.org/releaselog/3_14.html>.
> >>
> >> I think PHP-7.1 should be updated, but I'm not sure about PHP-7.0, even
> though I
> >> found no regression when running the sqlite3 and pdo_sqlite test suites
> with
> >> 3.14 on Linux and Windows under a current PHP-7.0.
> >>
> >> Anatol, what do you think?
> >>
> > As long as 7.1 is still in pre cycle, it'd be cheap to upgrade there
> first. If there are no issues, we're safer to backport this SQLite version
> into a lower PHP branch.
>
> Sounds reasonable, Anotol. Thanks. So I'm going to update 7.1+ ASAP.
>
> --
> Christoph M. Becker
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
