From owner-freebsd-ports@FreeBSD.ORG Sat Nov 29 13:39:07 2014 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1640FDE0 for ; Sat, 29 Nov 2014 13:39:07 +0000 (UTC) Received: from smtp1-g21.free.fr (smtp1-g21.free.fr [IPv6:2a01:e0c:1:1599::10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CCDE493A for ; Sat, 29 Nov 2014 13:39:06 +0000 (UTC) Received: from yggdrasil.alkumuna.eu (unknown [IPv6:2a01:e35:8a74:6e70:232:36ff:fe5c:3a87]) by smtp1-g21.free.fr (Postfix) with ESMTP id 82FBC94006D; Sat, 29 Nov 2014 14:38:57 +0100 (CET) Received: from freedom ([192.168.10.100]) (authenticated bits=0) by yggdrasil.alkumuna.eu (8.14.9/8.14.7) with ESMTP id sATDd0Dx037829 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT); Sat, 29 Nov 2014 14:39:00 +0100 (CET) (envelope-from mazhe@alkumuna.eu) Date: Sat, 29 Nov 2014 14:39:00 +0100 From: Matthieu Volat To: "A.J. 'Fonz' van Werven" Subject: Re: Update of security/gnupg fails because of conflict with security/dirmngr Message-ID: <20141129143900.27369fe5@freedom> In-Reply-To: <20141129125631.GA50784@spectrum.skysmurf.nl> References: <5479B154.9090606@rawbw.com> <20141129125631.GA50784@spectrum.skysmurf.nl> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; amd64-portbld-freebsd10.1) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/ncrrY9N8NHdveHJ/63RKSEJ"; protocol="application/pgp-signature" Cc: "ports@freebsd.org" , Yuri X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Nov 2014 13:39:07 -0000 --Sig_/ncrrY9N8NHdveHJ/63RKSEJ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sat, 29 Nov 2014 13:56:31 +0100 "A.J. 'Fonz' van Werven" wrote: > Yuri wrote: >=20 > > =3D=3D=3D> 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=20 > > files into the same place). Problematic file: /usr/local/bin/dirmngr >=20 > 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). >=20 > Hope that helps. >=20 > 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? >=20 > AvW >=20 > --=20 > Imbibo, ergo sum. The issue was reported[1], mentionned[2], without action being taken yet...= Is gnupg such an obscure and unused port? [1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D195489 [2] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D195206 --=20 Matthieu Volat --Sig_/ncrrY9N8NHdveHJ/63RKSEJ Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlR5zHQACgkQ+ENDeYKZi36rwQCfcN1lZEsULrH2HDi8LhpenxvP aCYAnRVUkk9y2brOeD2LEfncdzMZfz5a =1FS6 -----END PGP SIGNATURE----- --Sig_/ncrrY9N8NHdveHJ/63RKSEJ--