Bug 246375

Summary: [patch] net/openldap24-server: conflicts in multirep configuration
Product: Ports & Packages Reporter: Samy Mahmoudi <samy.mahmoudi>
Component: Individual Port(s)Assignee: Xin LI <delphij>
Status: New ---    
Severity: Affects Some People CC: samy.mahmoudi
Priority: --- Keywords: buildisok
Version: LatestFlags: delphij: maintainer-feedback-
Hardware: amd64   
OS: Any   
Attachments:
Description Flags
Patch file generated with svn diff none

Description Samy Mahmoudi 2020-05-11 15:19:29 UTC
Created attachment 214379 [details]
Patch file generated with svn diff

Hi,

Most of the time I use pkg, I get things like the following:

--------------------------------------
Updating x3550 repository catalogue...
x3550 repository is up to date.

Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.

All repositories are up to date.
Checking integrity... done (3 conflicting)
  - openldap-sasl-client-2.4.50 [x3550] conflicts with openldap-client-2.4.50 [installed] on /usr/local/bin/ldapadd
  - openldap-sasl-client-2.4.50 [x3550] conflicts with openldap-client-2.4.50 [x3550] on /usr/local/bin/ldapadd
  - openldap-sasl-client-2.4.50 [FreeBSD] conflicts with openldap-client-2.4.50 [installed] on /usr/local/bin/ldapadd
Checking integrity... done (0 conflicting)
------------------------------------------

The two packages (client and sasl-client) gets reinstalled very often, sometimes from my repository x3550, sometimes from the default FreeBSD repository. Installation often throws errors of conflicts.

Multirep configurations may not be recommended, but I do not experiment such a problem with the other 900+ ports built by my poudriere, so there may be something with these two slave ports.

I tried to patch openldap24-server to clean some leftovers from a previous era where several versions seems to coexist, but I am not sure that it will solve the problem. Also, is PKGNAMEPREFIX of any use now ?
Comment 1 Samy Mahmoudi 2020-05-11 15:20:51 UTC
(In reply to Samy Mahmoudi from comment #0)
gets reinstalled ---> get reinstalled
Comment 2 Samy Mahmoudi 2020-05-11 15:34:04 UTC
(In reply to Samy Mahmoudi from comment #1)
seems to ---> seem to
Comment 3 Automation User 2020-05-26 00:20:26 UTC
Build info is available at https://gitlab.com/swills/freebsd-ports/pipelines/149498437
Comment 4 Xin LI freebsd_committer 2020-05-26 00:27:02 UTC
The patch seems unreasonable; what made it appear to work was the removal of sasl in the package name, which is not a correct fix and makes the situation even worse.
Comment 5 Samy Mahmoudi 2020-06-11 18:30:29 UTC
(In reply to Xin LI from comment #4)
Hi Xin,

> The patch seems unreasonable; what made it appear to work was . . .
I have never said the proposed patch makes anything to work better. I said:

"I tried to patch openldap24-server to clean some leftovers from a previous era where several versions seems to coexist, but I am not sure that it will solve the problem."

> . . . the removal of sasl in the package name
Are you sure the proposed patch does remove "sasl" in the package name?
Comment 6 Samy Mahmoudi 2020-06-11 18:31:01 UTC
Just for your information, I have switched to a single-repository configuration (a custom repository made by poudriere) as a temporary workaround.
Comment 7 Samy Mahmoudi 2020-06-11 18:58:14 UTC
(In reply to Xin LI from comment #4)
Basically, they are three different elements in this patch:

1) The removal of ${PKGNAMEPREFIX}
2) The removal of 2.[0-3].* "CONFLICTS" lines
3) The removal of PKGNAMESUFFIX=-sasl-server

Do you mean 3) is unreasonable?

Anyway, I think something has to be done with -sasl-server anyway, as openldap*-sasl-server does not seem to be part of the ports tree right now:

https://www.freshports.org/net/openldap21-sasl-server
https://www.freshports.org/net/openldap22-sasl-server
https://www.freshports.org/net/openldap23-sasl-server
All deprecated.
Comment 8 Samy Mahmoudi 2020-06-15 17:38:42 UTC
(In reply to Samy Mahmoudi from comment #7)
they are ---> there are