<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">reopen 752086<br>
reopen 752085<br>
thanks<br>
<br>
On 2014-06-19 10:44, Ondřej Surý wrote:<br>
</div>
<blockquote
cite="mid:1403189097.16742.130624325.0170D737@webmail.messagingengine.com"
type="cite">
<title></title>
Version: 5.6.0~beta4+dfsg-5<br>
<br>
# or some other future version...<br>
<br>
<div>For god sake, could you send a patch with proposed changes
next time instead of filling bug reports for such minor stuff?<br>
</div>
</blockquote>
<br>
When you'll be asked to read a document more than 5 pages long
uselessly, you won't qualify your waste of time as "minor".<br>
<br>
For God's sake, why did this message close #752085? Do *not* close
reports using versions which do not exist.<br>
<br>
<blockquote
cite="mid:1403189097.16742.130624325.0170D737@webmail.messagingengine.com"
type="cite">
<div> </div>
<div>O.<br>
</div>
<div> </div>
<div>On Thu, Jun 19, 2014, at 16:10, Filipus Klutiero wrote:<br>
</div>
<blockquote type="cite">
<div>Package: php5 <br>
</div>
<div>Version: 5.6.0~beta4+dfsg-4 <br>
</div>
<div>Severity: wishlist <br>
</div>
<div> </div>
<div>The 5.6.0~beta4+dfsg-2 changelog entry reads:<br>
</div>
<blockquote type="cite">
<div> * Please read full upgrade notes available from<br>
</div>
<div> /usr/share/doc/php5-common/UPGRADING<br>
</div>
<div> * Here are the backwards incompatible changes as listed
by upstream:<br>
</div>
<div> </div>
<div> - Core:<br>
</div>
<div> By fixing bug #66015 it is no longer possible to
overwrite keys in static scalar<br>
</div>
<div> arrays. Quick example to illustrate:<br>
</div>
<div> class Test {<br>
</div>
<div> const FIRST = 1;<br>
</div>
<div> public $array = array(<br>
</div>
<div> self::FIRST => 'first',<br>
</div>
<div> 'second',<br>
</div>
<div> 'third'<br>
</div>
<div> );<br>
</div>
<div> }<br>
</div>
<div> Test::$array will have as expected three array keys
(1, 2, 3) and no longer<br>
</div>
<div> two (0, 1). self::FIRST will no longer overwrite
'third' having key 1 then,<br>
</div>
<div> but will mark the beginning of indexing. <br>
</div>
<div> </div>
<div> - JSON:<br>
</div>
<div> json_decode() no longer accepts non-lowercase
variants of lone JSON true,<br>
</div>
<div> false or null values. For example, True or FALSE
will now cause json_decode to<br>
</div>
<div> return NULL and set an error value you can fetch
with json_last_error().<br>
</div>
<div> This affects JSON texts consisting solely of true,
false or null. Text<br>
</div>
<div> containing non-lowercase values inside JSON arrays
or objects has never been<br>
</div>
<div> accepted.<br>
</div>
<div> </div>
<div> - OpenSSL:<br>
</div>
<div> To prevent man-in-the-middle attacks against
encrypted transfers client<br>
</div>
<div> streams now verify peer certificates by default.
Previous versions<br>
</div>
<div> required users to manually enable peer
verification. As a result of this<br>
</div>
<div> change, existing code using ssl:// or tls:// stream
wrappers (e.g.<br>
</div>
<div> file_get_contents(), fsockopen(),
stream_socket_client()) may no longer<br>
</div>
<div> connect successfully without manually disabling
peer verification via the<br>
</div>
<div> stream context's "verify_peer" setting. Encrypted
transfers delegate to<br>
</div>
<div> operating system certificate stores by default if
not overridden via the<br>
</div>
<div> new openssl.cafile and openssl.cafile ini
directives or via call-time SSL<br>
</div>
<div> context options, so most users should be unaffected
by this transparent<br>
</div>
<div> security enhancement. (<a moz-do-not-send="true"
href="https://wiki.php.net/rfc/tls-peer-verification">https://wiki.php.net/rfc/tls-peer-verification</a>)<br>
</div>
<div> </div>
<div> - Mcrypt:<br>
</div>
<div> The mcrypt_encrypt(), mcrypt_decrypt() and
mcrypt_{MODE}() functions no<br>
</div>
<div> longer accept keys or IVs with incorrect sizes.
Furthermore an IV is now<br>
</div>
<div> required if the used block cipher mode requires it.<br>
</div>
</blockquote>
<div> </div>
<div>We shouldn't request users to read the full upgrade notes
for 2 reasons:<br>
</div>
<ol>
<li>We have nothing to gain from users reading that. We should
simply inform them for their own good.<br>
</li>
<li>Even users usually don't need to read the full upgrade
notes. Only a minority of developers want to read the full
upgrade notes. Even the backwards-incompatible changes don't
need to be read on many systems which only use packaged PHP
scripts.<br>
</li>
</ol>
<div> </div>
<div>Note that there is no /usr/share/doc/php5-common/UPGRADING<br>
</div>
<div>UPGRADING is gzipped.<br>
</div>
<pre>--
Filipus Klutiero
<a moz-do-not-send="true" href="http://www.philippecloutier.com">http://www.philippecloutier.com</a>
</pre>
<div><u>_______________________________________________</u><br>
</div>
<div>pkg-php-maint mailing list<br>
</div>
<div><a moz-do-not-send="true"
href="mailto:pkg-php-maint@lists.alioth.debian.org">pkg-php-maint@lists.alioth.debian.org</a><br>
</div>
<div><a moz-do-not-send="true"
href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-php-maint">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-php-maint</a><br>
</div>
</blockquote>
<div> </div>
<div id="sig19640473">
<div class="signature">--<br>
</div>
<div class="signature">Ondřej Surý <<a moz-do-not-send="true"
href="mailto:ondrej@sury.org">ondrej@sury.org</a>><br>
</div>
<div class="signature">Knot DNS (<a moz-do-not-send="true"
href="https://www.knot-dns.cz/">https://www.knot-dns.cz/</a>)
– a high-performance DNS server<br>
</div>
<div class="signature"> </div>
</div>
<div> </div>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="998">--
Filipus Klutiero
<a class="moz-txt-link-freetext" href="http://www.philippecloutier.com">http://www.philippecloutier.com</a></pre>
</body>
</html>