From owner-freebsd-ports@FreeBSD.ORG Sun Jun 8 17:04:21 2014 Return-Path: Delivered-To: freebsd-ports@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 61B1CB6 for ; Sun, 8 Jun 2014 17:04:21 +0000 (UTC) Received: from dnvrco-oedge-vip.email.rr.com (dnvrco-outbound-snat.email.rr.com [107.14.73.230]) by mx1.freebsd.org (Postfix) with ESMTP id 2A58026B9 for ; Sun, 8 Jun 2014 17:04:20 +0000 (UTC) Received: from [76.184.156.59] ([76.184.156.59:60688] helo=[192.168.1.32]) by dnvrco-oedge01 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 27/11-12227-39794935; Sun, 08 Jun 2014 17:04:19 +0000 Date: Sun, 08 Jun 2014 12:04:19 -0500 From: Paul Schmehl Reply-To: Paul Schmehl To: olli hauer , FreeBSD Ports Subject: Re: How are ports built now Message-ID: <70671AB53C2ADFA5BF5AD5C2@Pauls-MacBook-Pro.local> In-Reply-To: <539489CF.3070003@gmx.de> References: <20140607202241.GA59544@spectrum.skysmurf.nl> <53938114.9060303@gmx.de> <539489CF.3070003@gmx.de> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-RR-Connecting-IP: 107.14.64.118:25 X-Authority-Analysis: v=2.1 cv=O4i3vXNW c=1 sm=1 tr=0 a=iy4Q/FHRRDrLt+awqfk3Bw==:117 a=iy4Q/FHRRDrLt+awqfk3Bw==:17 a=ayC55rCoAAAA:8 a=05ChyHeVI94A:10 a=kj9zAlcOel0A:10 a=cIJ4of8vVMpmSA6RAu0A:9 a=CjuIK1q_8ugA:10 a=_RhRFcbxBZMA:10 X-Cloudmark-Score: 0 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: Sun, 08 Jun 2014 17:04:21 -0000 --On June 8, 2014 at 6:05:35 PM +0200 olli hauer wrote: > On 2014-06-08 17:20, Paul Schmehl wrote: >> --On June 7, 2014 at 11:16:04 PM +0200 olli hauer wrote: >> >>> On 2014-06-07 22:40, Paul Schmehl wrote: >>>> --On June 7, 2014 at 10:22:41 PM +0200 "A.J. 'Fonz' van Werven" >>>> wrote: >>>> >>>>> Paul Schmehl wrote: >>>>> >>>>>> Recently I upgraded two servers to 8.4 and implemented the pkgng >>>>>> system. >>>>> [snip] >>>>>> Is portmaster not the appropriate method for updating ports with >>>>>> pkgng? >>>>> >>>>> It depends whether you're talking about *building* packages from the >>>>> ports tree or installing binary packages. >>>>> >>>>> As for building from ports, Portmaster doesn't care whether you're >>>>> using the new PNGNG or the old pkg_* tools. >>>>> >>>> >>>> Thanks. That's good to know. >>>> >>>>>> Now, when I run portmaster -ad, it seems to keep reinstalling the >>>>>> same ports over and over again. >>>>> >>>>> That's strange. Perhaps PKGNG hasn't been initialised properly on your >>>>> system(s), that's all I can think of at the moment. Did you use >>>>> pkg2ng? >>>>> >>>> >>>> I'm pretty sure I did, but I ran it again. I noticed several errors >>>> which I will have to investigate. >>>> >>> >>> Do you see which port is looping? >>> Perhaps a port was moved / renamed / removed and portmaster therfore is >>> looping around >>> >>> Sadly I cannot help more since I used all the years tinderbox / >>> poudriere to build packages. >>> >> >> I've been working on this for two days now, so the parameters have >> changed a bit. But here's an example of what prompted my question: >> >> This is the result of portmaster -ad >> >> ===>>> All >> (18) >> >> ===>>> The following actions will be taken if you choose to proceed: >> Upgrade en-freebsd-doc-43251,1 to en-freebsd-doc-44807,1 >> Install textproc/docproj >> Install print/ghostscript9 >> Upgrade pkgconf-0.9.5 to pkgconf-0.9.6 >> Upgrade lcms2-2.6_1 to lcms2-2.6_2 >> Install textproc/docbook-xml >> Install textproc/docbook-sgml >> Install www/mod_authnz_external22 >> >> ===>>> Proceed? y/n [y] n >> >> This is the result of pkg upgrade -n >> >> # pkg upgrade -n >> Updating repository catalogue >> Upgrades have been requested for the following 150 packages: >> >> Installing xf86vidmodeproto: 2.3.1 >> Installing damageproto: 1.2.1 >> Installing dri2proto: 2.8 >> Installing pciids: 20140526 >> Installing randrproto: 1.4.0 >> Installing perl5: 5.16.3_10 >> Installing db48: 4.8.30.0 > > On possible issue between `pkg upgrade' and portmaster with an current > ports tree is that some of the ports where updated between last wednesday > and now. E.g pkgconf and the freebsd docs where updated after the last > package build. [removed a bunch of lines] > > Is it possible that portmaster builds with NO_PORTDOCS or DOCS=off or > similar? > No. > > The port mail/pflogsumm has as only OPTIONS_DEFINE=DOCS, but `pkg > upgrade' complains about changed options >> Reinstalling pflogsumm-1.1.5,1 (options changed) > > DOCS on/off could be a possible explanation for all the '(options > changed)' updates. > In general I accept the default options, which is to install docs and examples. There are very few cases where I do not do that. Here's what portmaster wants to build now: ===>>> The following actions will be taken if you choose to proceed: Upgrade en-freebsd-doc-43251,1 to en-freebsd-doc-44807,1 Install textproc/docbook-sgml Install textproc/docbook-xml Install www/mod_authnz_external22 Re-install docproj-2.0_2 Install print/ghostscript9 All of these ports fail to install individually. Unfortunately, I have to have ghostscript because I use ImageMagick for our forum. Otherwise I remove it. It's always been problematic during installs and upgrades. Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. ******************************************* "It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead." Thomas Jefferson "There are some ideas so wrong that only a very intelligent person could believe in them." George Orwell