Update of security/gnupg fails because of conflict with security/dirmngr
mazhe at alkumuna.eu
Sat Nov 29 13:39:07 UTC 2014
On Sat, 29 Nov 2014 13:56:31 +0100
"A.J. 'Fonz' van Werven" <freebsd at skysmurf.nl> wrote:
> Yuri wrote:
> > ===> Registering installation for gnupg-2.1.0_1 as automatic
> > pkg-static: gnupg-2.1.0_1 conflicts with dirmngr-1.1.0_12 (installs
> > files into the same place). Problematic file: /usr/local/bin/dirmngr
> 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?
> Imbibo, ergo sum.
The issue was reported, mentionned, without action being taken yet... Is gnupg such an obscure and unused port?
Matthieu Volat <mazhe at alkumuna.eu>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 181 bytes
Desc: OpenPGP digital signature
More information about the freebsd-ports