From owner-freebsd-ports-bugs@freebsd.org Wed Jan 30 13:22:53 2019 Return-Path: Delivered-To: freebsd-ports-bugs@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 9A9E914C0C9F for ; Wed, 30 Jan 2019 13:22:53 +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 1F6D16B9D1 for ; Wed, 30 Jan 2019 13:22:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id D68D114C0C96; Wed, 30 Jan 2019 13:22:52 +0000 (UTC) Delivered-To: ports-bugs@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 C389D14C0C95 for ; Wed, 30 Jan 2019 13:22:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (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 "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5DA206B9CD for ; Wed, 30 Jan 2019 13:22:52 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id A1DAA1F9C4 for ; Wed, 30 Jan 2019 13:22:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x0UDMpWn013792 for ; Wed, 30 Jan 2019 13:22:51 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x0UDMpDt013791 for ports-bugs@FreeBSD.org; Wed, 30 Jan 2019 13:22:51 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 235301] devel/py-setuptools_scm: py27-setuptools_scm-3.1.0 fails to upgrade from py27-setuptools_scm-1.17.0 Date: Wed, 30 Jan 2019 13:22:50 +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: needs-qa X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: freebsd_ports@k-worx.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ports-bugs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback+ merge-quarterly? X-Bugzilla-Changed-Fields: flagtypes.name 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-ports-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jan 2019 13:22:53 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D235301 Kai changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|maintainer-feedback?(freebs |maintainer-feedback+ |d_ports@k-worx.org) | --- Comment #6 from Kai --- I created two patches that should remedy the issue with the inplace upgrade= of devel/py-setuptools_scm. The second patch, a shar file, is meant for the us= ers that don't use SVN. The root cause of the issue is that setup.py has been slightly changed since 3.0.0 . [1] Before that there had been also a discussion [2] that led to the changes in= the setup.py file [1]. [1] https://github.com/pypa/setuptools_scm/pull/264/commits/de0bed4fc96330b021c= bee63dc4f3a5eae2549c5 [2] https://github.com/pypa/setuptools_scm/issues/262 @koobs: A quartely-merge is afaik not required because devel/py-setuptools_= scm 3.1.0 has not been introduced to the quartely branch. --=20 You are receiving this mail because: You are the assignee for the bug.=