Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.netbsd.org", Issuer "Postmaster NetBSD.org" (verified OK)) by mollari.NetBSD.org (Postfix) with ESMTPS id 49F337A467 for ; Wed, 20 Apr 2016 16:10:16 +0000 (UTC) Received: by mail.netbsd.org (Postfix, from userid 605) id C9E2085F3C; Wed, 20 Apr 2016 16:10:15 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.netbsd.org (Postfix) with ESMTP id 5705285F03 for ; Wed, 20 Apr 2016 16:10:15 +0000 (UTC) X-Virus-Scanned: amavisd-new at netbsd.org Received: from mail.netbsd.org ([IPv6:::1]) by localhost (mail.netbsd.org [IPv6:::1]) (amavisd-new, port 10025) with ESMTP id eyx7vzAWxm_i for ; Wed, 20 Apr 2016 16:10:14 +0000 (UTC) Received: from cvs.NetBSD.org (ivanova.netbsd.org [199.233.217.197]) by mail.netbsd.org (Postfix) with ESMTP id C636084CEE for ; Wed, 20 Apr 2016 16:10:14 +0000 (UTC) Received: by cvs.NetBSD.org (Postfix, from userid 500) id B7101FBBA; Wed, 20 Apr 2016 16:10:14 +0000 (UTC) Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Date: Wed, 20 Apr 2016 16:10:14 +0000 From: "Leonardo Taccari" Subject: CVS commit: pkgsrc/www/py-h2 To: pkgsrc-changes@NetBSD.org Reply-To: leot@netbsd.org X-Mailer: log_accum Message-Id: <20160420161014.B7101FBBA@cvs.NetBSD.org> Sender: pkgsrc-changes-owner@NetBSD.org List-Id: pkgsrc-changes.NetBSD.org Precedence: bulk Module Name: pkgsrc Committed By: leot Date: Wed Apr 20 16:10:14 UTC 2016 Modified Files: pkgsrc/www/py-h2: Makefile distinfo pkgsrc/www/py-h2/patches: patch-setup.py Log Message: Update www/py-h2 to 2.2.3 Changes: 2.2.3 (2016-04-13) ------------------ Bugfixes ~~~~~~~~ - Allowed the 4.X series of hyperframe releases as dependencies. 2.1.4 (2016-04-13) ------------------ Bugfixes ~~~~~~~~ - Allowed the 4.X series of hyperframe releases as dependencies. 2.2.2 (2016-04-05) ------------------ Bugfixes ~~~~~~~~ - Fixed issue where informational responses were erroneously not allowed to be sent in the ``HALF_CLOSED_REMOTE`` state. - Fixed issue where informational responses were erroneously not allowed to be received in the ``HALF_CLOSED_LOCAL`` state. - Fixed issue where we allowed information responses to be sent or received after final responses. 2.2.1 (2016-03-23) ------------------ Bugfixes ~~~~~~~~ - Fixed issue where users using locales that did not default to UTF-8 were unable to install source distributions of the package. 2.2.0 (2016-03-23) ------------------ API Changes (Backward-Compatible) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - Added support for sending informational responses (responses with 1XX status) codes as part of the standard flow. HTTP/2 allows zero or more informational responses with no upper limit: hyper-h2 does too. - Added support for receiving informational responses (responses with 1XX status) codes as part of the standard flow. HTTP/2 allows zero or more informational responses with no upper limit: hyper-h2 does too. - Added a new event: ``ReceivedInformationalResponse``. This response is fired when informational responses (those with 1XX status codes). - Added an ``additional_data`` field to the ``ConnectionTerminated`` event that carries any additional data sent on the GOAWAY frame. May be ``None`` if no such data was sent. - Added the ``initial_values`` optional argument to the ``Settings`` object. Bugfixes ~~~~~~~~ - Correctly reject all of the connection-specific headers mentioned in RFC 7540 ยง 8.1.2.2, not just the ``Connection:`` header. - Defaulted the value of ``SETTINGS_MAX_CONCURRENT_STREAMS`` to 100, unless explicitly overridden. This is a safe defensive initial value for this setting. 2.1.3 (2016-03-16) ------------------ Deprecations ~~~~~~~~~~~~ - Passing dictionaries to ``send_headers`` as the header block is deprecated, and will be removed in 3.0. 2.1.2 (2016-02-17) ------------------ Bugfixes ~~~~~~~~ - Reject attempts to push streams on streams that were themselves pushed: streams can only be pushed on streams that were initiated by the client. - Correctly allow CONTINUATION frames to extend the header block started by a PUSH_PROMISE frame. - Changed our handling of frames received on streams that were reset by the user. Previously these would, at best, cause ProtocolErrors to be raised and the connection to be torn down (rather defeating the point of resetting streams at all) and, at worst, would cause subtle inconsistencies in state between hyper-h2 and the remote peer that could lead to header block decoding errors or flow control blockages. Now when the user resets a stream all further frames received on that stream are ignored except where they affect some form of connection-level state, where they have their effect and are then ignored. - Fixed a bug whereby receiving a PUSH_PROMISE frame on a stream that was closed would cause a RST_STREAM frame to be emitted on the closed-stream, but not the newly-pushed one. Now this causes a ``ProtocolError``. To generate a diff of this commit: cvs rdiff -u -r1.1 -r1.2 pkgsrc/www/py-h2/Makefile pkgsrc/www/py-h2/distinfo cvs rdiff -u -r1.1 -r1.2 pkgsrc/www/py-h2/patches/patch-setup.py Please note that diffs are not public domain; they are subject to the copyright notices on the relevant files.