interesting conflict

[vermaden]

I was upgrading 14.4-RC1 system to 15.0-RELEASE with freebsd-update(8) tool.

After first two 'freebsd-update install' I issued the: # pkg upgrade command.

... and here is the result after replying 'y' on each question:

# pkg upgrade
Updating FreeBSD-ports repository catalogue...
FreeBSD-ports repository is up to date.
Updating FreeBSD-ports-kmods repository catalogue...
FreeBSD-ports-kmods repository is up to date.
All repositories are up to date.
Checking for upgrades (171 candidates):  83%

gthumb-3.12.2_13 is locked and may not be modified
Checking for upgrades (171 candidates): 100%
Processing candidates (171 candidates): 100%
Checking integrity... done (2 conflicting)
  - tevent017-0.17.1 [FreeBSD-ports] conflicts with tevent-0.16.1 [installed] on /usr/local/include/tevent.h
  - talloc243-2.4.3 [FreeBSD-ports] conflicts with talloc-2.4.2 [installed] on /usr/local/include/pytalloc.h
Checking integrity... done (4 conflicting)
  - tevent016-0.16.1_3 [FreeBSD-ports] conflicts with tevent017-0.17.1 [FreeBSD-ports] on /usr/local/include/tevent.h
  - tevent016-0.16.1_3 [FreeBSD-ports] conflicts with tevent-0.16.1 [installed] on /usr/local/include/tevent.h
  - talloc242-2.4.2_3 [FreeBSD-ports] conflicts with talloc243-2.4.3 [FreeBSD-ports] on /usr/local/include/pytalloc.h
  - talloc242-2.4.2_3 [FreeBSD-ports] conflicts with talloc-2.4.2 [installed] on /usr/local/include/pytalloc.h
Cannot solve problem using SAT solver, trying another plan
Checking integrity... done (0 conflicting)
Your packages are up to date.

Regards,
vermaden

[vermaden]

More:

# pkg delete tevent016 talloc242        
No packages matched for pattern 'tevent016'

No packages matched for pattern 'talloc242'

Checking integrity... done (0 conflicting)
2 packages requested for removal: 0 locked, 2 missing

[vermaden]

... and:

# pkg info | grep -e tevent -e talloc           
talloc-2.4.2                   Hierarchical pool based memory allocator
tevent-0.16.1                  Talloc based event loop library

[bapt]

yes nothing pkg can do about this, those are 3 differents packages from pkg's standpoint (different name), this a an upgradability issue from ports with an impossible choice to solve by the solver (without adding some intelligence for it to understand maybe the name is being quite close so I could consider them as maybe upgrade which would be very very fragile) so my take on this one is talk to the maintainer so they thing about upgradability rather than having every single versions available in ports and causing headache to sat solvers.