From owner-freebsd-python@freebsd.org Thu Jan 7 02:52:32 2016 Return-Path: Delivered-To: freebsd-python@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 4516DA6652F for ; Thu, 7 Jan 2016 02:52:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 2FF581263 for ; Thu, 7 Jan 2016 02:52:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 2D3A7A6652E; Thu, 7 Jan 2016 02:52:32 +0000 (UTC) Delivered-To: python@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 2BDEDA6652D for ; Thu, 7 Jan 2016 02:52:32 +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 131CA1262 for ; Thu, 7 Jan 2016 02:52:32 +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 u072qV0C079521 for ; Thu, 7 Jan 2016 02:52:31 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 204567] devel/py-asn1: Update to 0.1.9 and rename to devel/py-pyasn1 Date: Thu, 07 Jan 2016 02:52:32 +0000 X-Bugzilla-Reason: CC 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: john@saltant.com X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: rm@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback+ X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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-python@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jan 2016 02:52:32 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204567 --- Comment #10 from John W. O'Brien --- (In reply to graham from comment #8) I'm sorry for the delay. I tried to post a response a day or two ago, but it appears to have been lost. It has been many moons since I last used portupgrade, so my chops are rusty= to say the least. However, this patch registers the new name in MOVED, so I believe that it meets its requirements w.r.t. the ports infrastructure. portupgrade has been MOVED-aware since v2.4.9.8 according to the latest rel= ease notes (https://github.com/freebsd/portupgrade/blob/2.4.14/NEWS.md). My main hint is to investigate the "-o" option for portupgrade. If neither = of these leads proves fruitful, please provide more detail about the state of = your system (versions of FreeBSD and portupgrade, at least, and the update method and relative snapshots of the ports tree) and the things you have tried (detailed command lines and full output as an attachment), to help us deter= mine if this is a port-specific regression or a portupgrade support issue. --=20 You are receiving this mail because: You are on the CC list for the bug.=