Thank you for following this up.

14.04 is just round the corner now, so it seems unlikely that any
further changes can be made now.

It sounds like json-c upstream are willing to have the behaviour in the
presence of the flag. Does this mean that php-json could use the flag by
default, and thus restore the original behaviour?

Though a change in behaviour is undesirable to fix in an SRU after
release.

So it looks like we'll have to stick with what we have, unless anybody
has a better suggestion? Mads, could you please explain the impact of
this change to end-users, whether you think this should be mentioned in
the release notes, and if so then suggest some appropriate text? Are
there any security implications in this change?

It seems to me that this is an unfortunate fallout of upstream PHP
refusing to ship a free software json module by default. So Debian had
to switch to an alternate version, and some behavioural change is the
consequence.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1287726

Title:
  Wrong evaluation whether json is valid or not

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php-json/+bug/1287726/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to