From owner-freebsd-ports-bugs@FreeBSD.ORG Wed Sep 10 16:15:30 2014 Return-Path: Delivered-To: freebsd-ports-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CB9501A3 for ; Wed, 10 Sep 2014 16:15:30 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 97E941982 for ; Wed, 10 Sep 2014 16:15:30 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s8AGFUqm098304 for ; Wed, 10 Sep 2014 16:15:30 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 193527] New: [patch] bsd.port.mk: check-already-installed hitting conflicts with ports that have same PKGBASE Date: Wed, 10 Sep 2014 16:15:30 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports Tree X-Bugzilla-Component: Infrastructure X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: z7dr6ut7gs@snkmail.com X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.18-1 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Sep 2014 16:15:30 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193527 Bug ID: 193527 Summary: [patch] bsd.port.mk: check-already-installed hitting conflicts with ports that have same PKGBASE Product: Ports Tree Version: Latest Hardware: Any OS: Any Status: Needs Triage Severity: Affects Many People Priority: --- Component: Infrastructure Assignee: freebsd-ports-bugs@FreeBSD.org Reporter: z7dr6ut7gs@snkmail.com Created attachment 147175 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=147175&action=edit use PKGORIGIN to decide if a package is already installed check-already-installed was changed after support for the old pkg_* tools was removed recently. It was changed to look at PKGBASE instead of PKGORIGIN (despite passing -O to pkg info [1]). This causes issues like the following when you have two ports that can legitimately have the same PKGBASE installed: ======================= ===> Installing for glib-2.36.3_4 ===> Checking if glib already installed ===> An older version of glib is already installed (glib-1.2.10_13) You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of glib without deleting it first, set the variable "FORCE_PKG_REGISTER" in your environment or the "make install" command line. *** Error code 1 Stop in /usr/ports/devel/glib20. ======================= I could not determine why this change was made. Is there a reason to use PKGBASE rather than PKGORIGIN? Origin seems like the more correct thing to check. I have attached a patch to go back to PKGORIGIN and done some test builds [1] This is a second bug - when passing something that is not an origin to pkg info -q -O, it still returns a result (e.g., pkg info -q -O pkg-1.3.7 gives pkg-1.3.7). This deviates from the old pkg_info which returns nothing (since pkg-1.3.7 is not an origin). Unless the definition of origin has changed, pkg_info seems more correct in this regard. Should I open a separate bug for this, or is this intended behavior? -- You are receiving this mail because: You are the assignee for the bug.