From owner-freebsd-ports@FreeBSD.ORG Thu May 29 23:41:11 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3BD7267D for ; Thu, 29 May 2014 23:41:11 +0000 (UTC) Received: from secure.xzibition.com (secure.xzibition.com [173.160.118.92]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E19CC24B2 for ; Thu, 29 May 2014 23:41:10 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; c=nofws; d=shatow.net; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=sweb; b=06Fbnz KjdGGUOvUK937Sq4wbym/m/jZ+rz+13wBTycrwi8fO+F8nmSsSBSaz1pmJUVhPwZ 7h5lnNnaSpUkebF77HfAVQ8cMre5gzyJhA96/K6WWFSGVCyXlSvXq2CcdOf7JHFd gHNVZA47ac6il4+xkt4YZAMcX8TeAqeX52jzk= DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=shatow.net; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=sweb; bh=G4+n9ZvoZlU6 iFDDdbSnCbA4+VOAGvpNpJgSQtbpkFA=; b=G8bMHc8FU68ktSKWhP80/oeVLfmW TXICZmPnS5j2QsmqzCZwQcb6AT0CBBmKKmvU+Ytf5ScJVUXbjRUK2AkJ5kDbZzss t//zt8zT1HbcOIA6A8vmkCZGbFU25mQ6CY9D3ej7EBFpo2NQ5t6wkKbZkVx7zqvc 5x7ECQO8czmEXNE= Received: (qmail 56159 invoked from network); 29 May 2014 18:34:27 -0500 Received: from unknown (HELO usxxdrewebm1.corp.emc.com) (bryan@shatow.net@67.182.131.225) by sweb.xzibition.com with ESMTPA; 29 May 2014 18:34:27 -0500 Message-ID: <5387C400.5070506@shatow.net> Date: Thu, 29 May 2014 18:34:24 -0500 From: "Drewery, Bryan" User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Pete Carah Subject: Re: Net-SNMP conflict References: <537B0FCB.7020608@altadena.net> <5387C168.60303@altadena.net> In-Reply-To: <5387C168.60303@altadena.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: zi@freebsd.org, Bryan Drewery , freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 May 2014 23:41:11 -0000 On Thu May 29 18:23:20 2014, Pete Carah wrote: > On 05/20/2014 09:58 AM, Bryan Drewery wrote: >> On 2014-05-20 04:18, Pete Carah wrote: >>> PLEASE don't automatically install pkg during the build of ANY other >>> package; if this happens in the middle of a portupgrade -a on a system >>> without pkgng, the result is not pretty; all packages built after >>> net-snmp have a duplicated origin, among other things. I hope I can >>> recover the system since it is supposed to be a production server. >>> >>> Yes, I realize I'll have to convert. However, this forced install >>> doesn't convert the database so the pkg database and /var/db/pkg end up >>> inconsistent, and I can't tell what is really installed on all of the >>> packages that show a duplicated origin. >>> >>> -- Pete >>> >> >> (portupgrade maintainer and pkg developer here) >> >> Having pkg installed should be perfectly safe. Portupgrade, nor the >> ports framework, consider pkg installed as "converted". All packages >> will continue to be registered in the old format unless you run >> pkg2ng or 'pkg install' or add WITH_PKGNG=yes to your make.conf. >> >> Can you please elaborate on what the "duplicated origin" issue >> is? > The way net-snmp installed pkg also activated it without doing a pkg2ng; > since this happened > in the middle of a portupgrade part of the portupgrade kept its records > the old way and the rest > the new way without any of the old ports in the database. This made a > lot of things build twice. > Not very nice... Have you ran pkg2ng since then? None of this sounds right to me. If you have not yet ran pkg2ng then we can debug it. Otherwise it's too late. If not, I'd like to see the output of 'pkg info' and: env TMPDIR=/dev/null ASSUME_ALWAYS_YES=1 PACKAGESITE=file:///nonexistent pkg info -x 'pkg(-devel)?$' It is very much intended that installing pkg or having it pulled in via net-snmp will not run pkg2ng. Portupgrade should be flipping over to using pkg unless pkg has itself registered - which can't happen without WITH_PKGNG set in the environment or make.conf. > >> >> net-snmp also should (if I remember the code I reviewed right) be >> only considering the new package database if it has packages in it, >> meaning not until you pkg2ng or 'pkg install'. > No, the way I read the makefile lines in question it installed it if it > wasn't already > installed.. See: I am referring to the runtime of net-snmp, not the port. > > # pkg-1.2 cannot handle this dependency well. > .if !defined(WITH_PKGNG) > LIB_DEPENDS= libpkg.so:${PORTSDIR}/ports-mgmt/pkg > .endif > > This will install if it is there or not, but only if it is NOT in use. > Probably not what was > intended. > > -- Pete