I have a system where I'd like to use security/zeek (indirectly depends on py-backports) and py-django41 (depends on devel/py-backports.zoneinfo) but pkg thinks the two backports ports conflict. The pkg-descr for py-backports says: shared namespace shim for py-backports.* ports py-backports provides a common backports/__init__.py, which is shared among all py-backports.* ports. I built all four py-backports.* ports: devel/py-backports.cached-property devel/py-backports.csv devel/py-backports.entry-points-selectable devel/py-backports.zoneinfo and tried installing them with py-backports and found that only py-backports.csv can be installed without conflicting. I noticed that the py-backports.csv Makefile has a RUN_DEPENDS for py-backports so I tried adding one to the other ports but I still get: Checking integrity... done (1 conflicting) - py39-backports.zoneinfo-0.2.1_1 conflicts with py39-backports-1 on /usr/local/lib/python3.9/site-packages/backports/__init__.py Cannot solve problem using SAT solver, trying another plan Checking integrity... done (0 conflicting) Conflicts with the existing packages have been found. One more solver iteration is needed to resolve them. Looking at the various port Makefiles, I don't understand why py-backports.csv works and the others do not. Maybe this is really a pkg bug? Anyway, it *looks* like what I want *should* be possible.
This was addressed in review D11095 which may provide information on why one port works and others don't. We might need a better approach such that backports packages automatically get the appropriate changes without requiring opt-in / action on part of maintainers