From owner-freebsd-ports-bugs@freebsd.org  Fri Sep 30 13:59:37 2016
Return-Path: <owner-freebsd-ports-bugs@freebsd.org>
Delivered-To: freebsd-ports-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 27FB8C028ED
 for <freebsd-ports-bugs@mailman.ysv.freebsd.org>;
 Fri, 30 Sep 2016 13:59:37 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 145D314EF
 for <freebsd-ports-bugs@FreeBSD.org>; Fri, 30 Sep 2016 13:59:37 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u8UDxaIe083205
 for <freebsd-ports-bugs@FreeBSD.org>; Fri, 30 Sep 2016 13:59:36 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-ports-bugs@FreeBSD.org
Subject: [Bug 213005] sysutils/duplicity: google code backend broken due to
 broken py27-gdata-2.0.18
Date: Fri, 30 Sep 2016 13:59:37 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Ports & Packages
X-Bugzilla-Component: Individual Port(s)
X-Bugzilla-Version: Latest
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: marino@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-213005-13-LxDQ251UDy@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-213005-13@https.bugs.freebsd.org/bugzilla/>
References: <bug-213005-13@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-ports-bugs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Ports bug reports <freebsd-ports-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports-bugs/>
List-Post: <mailto:freebsd-ports-bugs@freebsd.org>
List-Help: <mailto:freebsd-ports-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Sep 2016 13:59:37 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213005

--- Comment #2 from John Marino <marino@FreeBSD.org> ---
You're not reported anything that's not already known.  Over 400 ports were
marked broken which caused a lot of (known) fallout.

This port is not maintained.

If you'd like to see it fixed and since you seem to know the solution, I
suggest that you submit a patch.  Otherwise, this may never be addressed an=
d as
a result the port would be removed.

--=20
You are receiving this mail because:
You are the assignee for the bug.=