From owner-freebsd-ports@freebsd.org  Mon May 13 19:56:36 2019
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3F70F1599DAA
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Mon, 13 May 2019 19:56:36 +0000 (UTC)
 (envelope-from ehaupt@FreeBSD.org)
Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 server-signature RSA-PSS (4096 bits)
 client-signature RSA-PSS (4096 bits) client-digest SHA256)
 (Client CN "smtp.freebsd.org",
 Issuer "Let's Encrypt Authority X3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id D414D6B2E3;
 Mon, 13 May 2019 19:56:35 +0000 (UTC)
 (envelope-from ehaupt@FreeBSD.org)
Received: from beaver (77-56-97-229.dclient.hispeed.ch [77.56.97.229])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate) (Authenticated sender: ehaupt)
 by smtp.freebsd.org (Postfix) with ESMTPSA id 6F23F1D0F8;
 Mon, 13 May 2019 19:56:34 +0000 (UTC)
 (envelope-from ehaupt@FreeBSD.org)
Date: Mon, 13 May 2019 21:56:32 +0200
From: Emanuel Haupt <ehaupt@FreeBSD.org>
To: Sid <sid@bsdmail.com>
Cc: freebsd-ports@freebsd.org
Subject: Re: Electrum connection error
Message-Id: <20190513215632.b9c533183942bb4488d3a8dc@FreeBSD.org>
In-Reply-To: <trinity-932979c9-2849-4c3f-b401-870f24ea45b9-1557770840084@3c-app-mailcom-lxa13>
References: <trinity-932979c9-2849-4c3f-b401-870f24ea45b9-1557770840084@3c-app-mailcom-lxa13>
X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd12.0)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Rspamd-Queue-Id: D414D6B2E3
X-Spamd-Bar: --
Authentication-Results: mx1.freebsd.org
X-Spamd-Result: default: False [-2.97 / 15.00];
 local_wl_from(0.00)[FreeBSD.org];
 NEURAL_HAM_MEDIUM(-1.00)[-0.999,0];
 NEURAL_HAM_SHORT(-0.97)[-0.975,0];
 ASN(0.00)[asn:11403, ipnet:96.47.64.0/20, country:US];
 NEURAL_HAM_LONG(-1.00)[-1.000,0]
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 13 May 2019 19:56:36 -0000

Sid <sid@bsdmail.com> wrote:
> Hi,
> 
> I get the following error when running finance/electrum from the
> command line,
> 

[snip]

> aiorpcx.Connector(NotificationSession, AttributeError: module
> 'aiorpcx' has no attribute 'Connector'

Unfortunately the most recent update of devel/py-aiorpcX to 0.18.0
broke finance/electrum. It's even listed in the requirements:

$ grep aiorpcx \
	work-py36/Electrum-3.3.5/contrib/requirements/requirements.txt 
aiorpcx>=0.17,<0.18

A diff between aiorpcx 0.17.0 and 0.18.0 shows that there was quite a
churn that can't be easily fixed.

For now I've downgraded devel/py-aiorpcX to 0.17.0,1 and bumped the
electrum port.

Updating the ports tree and updating the two ports manually will solve
the issue until the package builders have caught up.

Sorry for the inconvenience.

Emanuel