From owner-freebsd-python@FreeBSD.ORG Sat Mar 8 23:33:12 2014 Return-Path: Delivered-To: python@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9C203AE9 for ; Sat, 8 Mar 2014 23:33:12 +0000 (UTC) Received: from mail-pd0-x234.google.com (mail-pd0-x234.google.com [IPv6:2607:f8b0:400e:c02::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7140E852 for ; Sat, 8 Mar 2014 23:33:12 +0000 (UTC) Received: by mail-pd0-f180.google.com with SMTP id v10so5536668pde.25 for ; Sat, 08 Mar 2014 15:33:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=omvMcF2WFcW1p8OTlc6C5gLP5yeu9BrBG6TX6aK3564=; b=xgjNtH8o2T6F4zKBcpFuhkgC5q3V9cacQw9I+39/KpxIeigR5u44XwTPNyPNK4SO1Q PGEk3Qq1+qgrOr5rg1rpN1BsibUIt0uQM40KSO8GqG6nxjzVmv5RtA9vpYUniRJE0Dr5 pqwA9y0sTl52QMabK6/fr0hSlxOabeCFV+IINDfVg0iRUfv/S1stoDKzA6zgxJI4uPQq dHYAqUOgrf4yIBZY9XdGMMML2a/Ngfdi9HIuJmM8BEF9r9syCzsG3aBc2RjUji+Ofsj5 aZtxFryTidgJFtHQ3+Bk0wHC2J79ZKeDenHMdgANqRWmWHBqr3n8UlNPVbrYtKSaBvTi 5WCA== X-Received: by 10.67.23.135 with SMTP id ia7mr30562711pad.5.1394321591601; Sat, 08 Mar 2014 15:33:11 -0800 (PST) Received: from [192.168.1.7] (ppp59-167-128-11.static.internode.on.net. [59.167.128.11]) by mx.google.com with ESMTPSA id ja8sm50099230pbd.3.2014.03.08.15.33.09 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 08 Mar 2014 15:33:11 -0800 (PST) Message-ID: <531BA8AD.3090209@FreeBSD.org> Date: Sun, 09 Mar 2014 10:33:01 +1100 From: Kubilay Kocak User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Thunderbird/27.0 MIME-Version: 1.0 To: "Kenta S." , python@freebsd.org Subject: Re: security/py-cryptography broken References: <20140306044423.GA65814@dev.san.ru> <20140308180236.031E420108@smtp.hushmail.com> In-Reply-To: <20140308180236.031E420108@smtp.hushmail.com> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: koobs@FreeBSD.org List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Mar 2014 23:33:12 -0000 On 9/03/2014 5:02 AM, Kenta S. wrote: > Deluge was working fine until the py-openssl update. I tried following UPDATING > but it left me with a broken system. I only have py-openssl because of Deluge. > I uninstalled deluge and did a "pkg autoremove" to try and clean things up. > I updated the ports tree and try to reinstall Deluge, but now I get this MD5 > error and don't know how to fix whatever is broken. > Which UPDATING entry instructions did you follow? I don't recall any for deluge, py-openssl or py-cryptography. Last night I made a change to py-cryptography that fixed py-cffi incorrectly not being included as a RUN_DEPENDS. I'm not sure to what extent its related to your issue, but can you update py-cryptography (as py-openssl depends on it) to the latest version and let me know if that works. If not: What does the following python command output: python -c "from hashlib import md5, sha512"