Update of security/gnupg fails because of conflict with security/dirmngr

Yuri yuri at rawbw.com
Sat Nov 29 13:25:33 UTC 2014

On 11/29/2014 04:56, A.J. 'Fonz' van Werven wrote:
> Yes, that sort of thing seems to be happening a lot lately. I found 
> out that it often helps if you temporarily uninstall the offending 
> port, then install the other one and finally reinstall the uninstalled 
> one. Or in your case: 1. delete dirmngr (remember if it takes anything 
> else with it!) 2. install gnupg; 3. reinstall dirmngr again (as well 
> as anything that got deleted with it). Hope that helps. However, 
> considering that this sort of thing occurs commonly these days, I 
> suspect there must be something wrong in the ports infrastructure. 
> What I also find somewhat mindboggling is how ports are built, staged 
> and packaged entirely, only THEN to discover there's a conflict. 
> Couldn't that have been detected way earlier? AvW 

I think, what typically happens is that one package depends on another, 
and that dependency package is just imported in the dependent one, while 
keeping the same file names installed.
In this case it looks like gnupg requires dirmngr, and parts of it were 
imported into gnupg, while dirmngr keeps living its own life in the system.

This is really an evil practice, but people do this, usually without 
causing conflicts. Chrome has a whole lot of packages included, and also 
mplayer has.

In this case gnupg port should rename offending files, nothing else 
would solve the problem.


More information about the freebsd-ports mailing list