From owner-freebsd-python@freebsd.org Sat Jul 28 19:33:53 2018 Return-Path: Delivered-To: freebsd-python@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 D87C3105B99D for ; Sat, 28 Jul 2018 19:33:52 +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 750D97C5FC for ; Sat, 28 Jul 2018 19:33:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 36C48105B99C; Sat, 28 Jul 2018 19:33:52 +0000 (UTC) Delivered-To: python@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 14C90105B99B for ; Sat, 28 Jul 2018 19:33: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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A9C3A7C5F9 for ; Sat, 28 Jul 2018 19:33:51 +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 145CBC8AE for ; Sat, 28 Jul 2018 19:33: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 w6SJXorc064480 for ; Sat, 28 Jul 2018 19:33:50 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w6SJXoUZ064479 for python@FreeBSD.org; Sat, 28 Jul 2018 19:33:50 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: python@FreeBSD.org Subject: [Bug 230114] [NEW PORT] textproc/scancode-toolkit: Scans code for license, copyright, package and documented dependencies Date: Sat, 28 Jul 2018 19:33:50 +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: freebsd_ports@k-worx.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: miwi@FreeBSD.org X-Bugzilla-Flags: 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.27 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jul 2018 19:33:53 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D230114 --- Comment #4 from Kai --- (In reply to Nathan from comment #1) (In reply to Nathan from comment #3) It depends in which context you do apply the patch. If you do e.g. > $ cd /path/to/your/ports/tree > $ svn patch --dry-run ~/scancode-toolkit.patch textproc/ from the root of your svn tree, you should get a similar output like below: > A textproc/scancode-toolkit > A textproc/scancode-toolkit/Makefile > A textproc/scancode-toolkit/distinfo > A textproc/scancode-toolkit/files > A textproc/scancode-toolkit/files/patch-setup.py > A textproc/scancode-toolkit/files/patch-src_commoncode_system.py > A textproc/scancode-toolkit/pkg-descr The same result you would get with: > $ cd /path/to/your/ports/tree > $ cd textproc > $ svn patch --dry-run ~/scancode-toolkit.patch The output would be: > A scancode-toolkit > A scancode-toolkit/Makefile > A scancode-toolkit/distinfo > A scancode-toolkit/files > A scancode-toolkit/files/patch-setup.py > A scancode-toolkit/files/patch-src_commoncode_system.py > A scancode-toolkit/pkg-descr When applying your patch with the "corrected" paths the output will show so= me differences which yields into a non functional port that cannot be built: > $ cd /path/to/your/ports/tree > $ svn patch --dry-run ~/corrected_paths.patch textproc/ > A textproc/textproc > A textproc/textproc/scancode-toolkit > A textproc/textproc/scancode-toolkit/Makefile > A textproc/scancode-toolkit > A textproc/scancode-toolkit/distinfo > A textproc/scancode-toolkit/files > A textproc/scancode-toolkit/files/patch-setup.py > A textproc/scancode-toolkit/files/patch-src_commoncode_system.py > A textproc/scancode-toolkit/pkg-descr As for the info about the non-existent origins - have you updated your ports tree? Your ports tree needs to be at least at r475546 to have all the ports that are required to build textproc/scancode-toolkit successfully. --=20 You are receiving this mail because: You are on the CC list for the bug.=