From owner-freebsd-ports@FreeBSD.ORG Mon May 25 21:00:06 2015 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DCFCEEAB for ; Mon, 25 May 2015 21:00:06 +0000 (UTC) (envelope-from john.marshall@riverwillow.com.au) Received: from mta1.riverwillow.net.au (mta1.riverwillow.net.au [IPv6:2001:8000:1000:1801::3001]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mta1.riverwillow.net.au", Issuer "Riverwillow 2014 CA Root Certificate" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E0539896 for ; Mon, 25 May 2015 21:00:04 +0000 (UTC) (envelope-from john.marshall@riverwillow.com.au) Received: from mail1.riverwillow.net.au (mail1.riverwillow.net.au [IPv6:2001:8000:1000:1801:0:0:0:4001]) by mta1.riverwillow.net.au (8.15.1/8.15.1) with ESMTPS id t4PKxud5091525 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Tue, 26 May 2015 06:59:57 +1000 (AEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=riverwillow.com.au; s=mta1002; t=1432587597; bh=H7Q1wFfYJ8AtlKMybUB43C91kGEWf2jeZgGsm2u6oJU=; h=Date:From:To:Subject:References:In-Reply-To; b=whH+AcyOntPbzb1h85VcymrWUhtqbs/Sb6ECo8vFb50IsjzWpLmpaU9zsX1eXZ23Z EHjPvupbKkaWC0LGUVluQh+rNIBCLPMIxI/SgOin6mOtP2ek0qNLlnO7jVoo9sAZu4 c4+/Yy955fOrqg1JT47v8Aq1DNkwTGoMpgXxd7dE= Received: from rwpc15.gfn.riverwillow.net.au (rwpc15.gfn.riverwillow.net.au [IPv6:2001:8000:1000:18e1:20c:76ff:fe0a:2117]) (authenticated bits=56) by mail1.riverwillow.net.au (8.15.1/8.15.1) with ESMTPSA id t4PKxraj091524 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Tue, 26 May 2015 06:59:55 +1000 (AEST) Date: Tue, 26 May 2015 06:59:52 +1000 From: John Marshall To: freebsd-ports@freebsd.org Subject: Re: Any guidance for gnupg-2.0 -> gnupg-2.1 (archived encrypted email)? Message-ID: <20150525205952.GA4054@rwpc15.gfn.riverwillow.net.au> Mail-Followup-To: freebsd-ports@freebsd.org References: <20150524181321.GB1214@albert.catwhisker.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="4Ckj6UjgE2iN1+kY" Content-Disposition: inline In-Reply-To: <20150524181321.GB1214@albert.catwhisker.org> OpenPGP: id=A29A84A2; url=http://pki.riverwillow.com.au/pgp/johnmarshall.asc User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 May 2015 21:00:07 -0000 --4Ckj6UjgE2iN1+kY Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, 24 May 2015, 11:13 -0700, David Wolfskill wrote: > Last November, I encountered a reason to deviate from that: When > security/gnupg became gnupg-2.1, I found that gnupg-2.1 was unable to > decrypt some (well, any, in my experience) archived encrypted email > messages. I was bitten badly in November when I blindly upgraded security/gnupg and found myself in the new, shiny, non-STABLE version 2.1.0. I can't remember the details, but too much stuff didn't work. I went to the release notes and other places and spent about a day trying to make the best of it. I had some success but ended up reverting security/gnupg -> security/gnupg20 after I discovered the following on the GnuPG home page. - 2.0.27 is the stable version suggested for most users, - 2.1.4 is the brand-new modern version with support for ECC and many other new features, and - 1.4.19 is the classic portable version. The STABLE 2.0 branch still works for me and the surprise factor is not as prominent as in 2.1. I have no idea why the main FreeBSD port was switched from STABLE to CURRENT and the STABLE version was relegated to a new version-tagged port. Sorry if this is off-topic but maybe it helps some folks. --=20 John Marshall --4Ckj6UjgE2iN1+kY Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlVjjUgACgkQw/tAaKKahKJvMwCeOVlvxuarJpxOcQnEg6xQ/sMp hTAAn0PkBRQyEzv/FoLSvgPdXY9gD3cE =OzDv -----END PGP SIGNATURE----- --4Ckj6UjgE2iN1+kY--