From owner-freebsd-ports@freebsd.org Sat Jun 10 04:56:53 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6FE5AD847A2 for ; Sat, 10 Jun 2017 04:56:53 +0000 (UTC) (envelope-from se@freebsd.org) Received: from mailout12.t-online.de (mailout12.t-online.de [194.25.134.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 333D36697B for ; Sat, 10 Jun 2017 04:56:52 +0000 (UTC) (envelope-from se@freebsd.org) Received: from fwd39.aul.t-online.de (fwd39.aul.t-online.de [172.20.27.138]) by mailout12.t-online.de (Postfix) with SMTP id 4E26741EF7CA for ; Sat, 10 Jun 2017 06:56:50 +0200 (CEST) Received: from Stefans-MacBook-Pro-2.local (rxbZJaZVwh8fmGUcvuPpQgYewpAcTJs6A9boTxBUiObAGrDzuXZorG3jo-KsQ4ZgH-@[88.128.80.28]) by fwd39.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384 encrypted) esmtp id 1dJYS6-08JJeS0; Sat, 10 Jun 2017 06:56:46 +0200 Subject: Re: Unable to upgrade from Samba43 to Samba44 or Samba45 To: freebsd-ports@freebsd.org References: <76204B0C-8ED3-4A6B-B278-EFB81CED5A3F@FreeBSD.org> From: Stefan Esser Message-ID: <36734108-cebb-bf46-dfc0-5604da518ab6@freebsd.org> Date: Sat, 10 Jun 2017 06:56:45 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <76204B0C-8ED3-4A6B-B278-EFB81CED5A3F@FreeBSD.org> Content-Type: text/plain; charset=windows-1252 Content-Language: en-GB Content-Transfer-Encoding: 7bit X-ID: rxbZJaZVwh8fmGUcvuPpQgYewpAcTJs6A9boTxBUiObAGrDzuXZorG3jo-KsQ4ZgH- X-TOI-MSGID: c32e2821-e226-40c4-9543-15e8caf9548f X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jun 2017 04:56:53 -0000 Am 08.06.17 um 21:15 schrieb Dimitry Andric: > On 8 Jun 2017, at 20:35, Mark Knight wrote: >> >> On 08/06/2017 18:35, Dimitry Andric wrote: >>> I'm guessing that it is confused by an existing samba installation. Try >>> removing all other samba installations before attempting to build this >>> port. >> >> Having followed an off-list suggestion to create a package (thanks) as a backup, I removed samba43 and established that your "guess" was right. Thank you! >> >> Presumably this implies a bug in the port? > > Not really, more a deficiency in portmaster. The port itself is marked > as conflicting with any other samba port: > > CONFLICTS?= *samba3[2-6]-3.* samba4-4.0.* samba4[1-356]-4.* p5-Parse-Pidl-4.* > > E.g., you should normally not be able to build it when samba43 is > installed. Probably, portmaster is overriding this safety belt somehow. I have always understood CONFLICTS to indicate, that some port can not be *installed* at the same time as some of the ports listed as conflicting. Building such a port while a conflicting version is installed, is possible most of the time. If such a build fails, it is most ofter due to the build preferring the already installed headers over those provided with the new version (i.e. a wrong ordering of include paths). Since port developers typically test ports in poudriere (to get a clean build environment and e,g, to be sure, all dependencies are correctly specified), they often don't notice such conflicts with already installed versions of the same port. Regards, STefan