Unable to upgrade from Samba43 to Samba44 or Samba45

Dimitry Andric dim at FreeBSD.org
Sat Jun 10 15:39:17 UTC 2017

On 10 Jun 2017, at 06:56, Stefan Esser <se at freebsd.org> wrote:
> Am 08.06.17 um 21:15 schrieb Dimitry Andric:
>> On 8 Jun 2017, at 20:35, Mark Knight <lists at knigma.org> 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.

In fact, you cannot even download the port sources in such a case, e.g:

$ make -C /usr/ports/net/samba44 fetch

===>  samba44-4.4.14 conflicts with installed package(s):

      They install files into the same place.
      You may want to stop build with Ctrl + C.

> 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).

Yes, this is apparently one of the reasons lang/rust even conflicts with
*itself*.  There seems to be something very broken in its build process,
so that it cannot build correctly if any of its files are installed on
the system.

That said, things like this could probably be solved by adding separate
CONFLICTS_BUILD, CONFLICT_FETCH and so on, but it makes it all rather


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 194 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20170610/792c28b3/attachment.sig>

More information about the freebsd-ports mailing list