From owner-freebsd-stable@FreeBSD.ORG Thu Jan 9 17:48:04 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C16C2126 for ; Thu, 9 Jan 2014 17:48:04 +0000 (UTC) Received: from smtp.infracaninophile.co.uk (smtp6.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3cd3:cd67:fafa:3d78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6886D1D50 for ; Thu, 9 Jan 2014 17:48:04 +0000 (UTC) Received: from seedling.local (seedling.black-earth.co.uk [81.2.117.99]) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.14.7/8.14.7) with ESMTP id s09Hlwdr074515 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Thu, 9 Jan 2014 17:47:58 GMT (envelope-from matthew@FreeBSD.org) DKIM-Filter: OpenDKIM Filter v2.8.3 smtp.infracaninophile.co.uk s09Hlwdr074515 Authentication-Results: smtp.infracaninophile.co.uk/s09Hlwdr074515; dkim=none reason="no signature"; dkim-adsp=none X-Authentication-Warning: lucid-nonsense.infracaninophile.co.uk: Host seedling.black-earth.co.uk [81.2.117.99] claimed to be seedling.local Message-ID: <52CEE0C4.3040307@FreeBSD.org> Date: Thu, 09 Jan 2014 17:47:48 +0000 From: Matthew Seaman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: pkgng upgrade "unable to find catalogs" - with key installed References: <20140109165029.GA97360@bewilderbeast.blackhelicopters.org> In-Reply-To: <20140109165029.GA97360@bewilderbeast.blackhelicopters.org> X-Enigmail-Version: 1.6 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="aNrRVSjHvB4CaVexBGn7gmJhp6qfTBGOc" X-Virus-Scanned: clamav-milter 0.98 at lucid-nonsense.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-2.2 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DCC_CHECK autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on lucid-nonsense.infracaninophile.co.uk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jan 2014 17:48:04 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --aNrRVSjHvB4CaVexBGn7gmJhp6qfTBGOc Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 09/01/2014 16:50, Michael W. Lucas wrote: > Trying to upgrade from pkg 1.1 to 1.2 on FreeBSD 9.1. I have > /usr/share/keys and the current trusted key, and a repo config > file. No pkg.conf. >=20 > # pkg upgrade > Updating repository catalogue > digests.txz 100% 1082KB 1.1MB/s= 1.1MB/s 00:00 > packagesite.txz 100% 5028KB 4.9MB/s= 2.6MB/s 00:01 > Incremental update completed, 23171 packages processed: > 0 packages updated, 0 removed and 23171 added. > pkg: Unable to find catalogs > # >=20 > Any suggestions? >=20 When upgrading from 1.1.x to 1.2.4_1 I've found it necessary to re-run pkg about twice in order to get the databases and config files updated. I generally do something like this: Starting with 1.1.4: pkg install pkg This installs pkg-1.2.4_1. Now edit ${LOCALBASE}/etc/pkg and ${LOCALBASE}/etc/pkg/repo.conf or /etc/pkg/FreeBSD.conf to fix the formating to match what pkg-1.2.x expects. pkg install pkg You should get get a message about updating the schema pkg install pkg Should pull down the latest digests.txz and packagesite.txz, then report 'Nothing to do' since pkg is already fully updated. Then proceed with 'pkg upgrade' as usual. I have been using a private pkg repo though, without any crypto signatures. If the signatures prevent the above process from working correctly, then try commenting out the 'signature_type' line in FreeBSD.conf temporarily. As you're only affecting the pkg package in the above, which gets updated by pkg-1.1.4 without any crypto checking anyhow, you aren't any worse off. Once you've got pkg upgraded and the databases etc. in synch, then you can uncomment the 'signature_type' and run: pkg install -f pkg to force a reinstall with all the required signature checking. Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey --aNrRVSjHvB4CaVexBGn7gmJhp6qfTBGOc Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.20 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQJ8BAEBCgBmBQJSzuDNXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkATTDoQAKv4cvsZW1uyq5HAh8TH8MYj V9HbQgDaxDCKSpJGa/cz6fKYMuDxftiuguxc/fAG8/X5wwf8aC1dE55Bj1mWTqyl c+ab+fbjRC2edtjmZUXVvy8Ij6yRZqOhthcqcH4dRdzcb+0nFdCUbcegiWPc7F9F W0bMez5izhGhw7fjuMjdDFfSALN9aCAqUfGjEZo00S0Vn+YPnaivCHHqeTZHw5iU bOKflEkZIHkNmGYAv7NDQzsqoPBkzB6T/nAPzPz9juhfiEgIKy+aKxtiV+TCbO+G BfsJYZibdJT2gXgUCd5G9n0eXVDx7ARu66dOTtzNJR8qnrjLuFwiVgTQ/BCA2klI pZ2oX8WHJqrjqdboH0kTn/gOGG6t5WfoOUwT1wrTYGrwHStRS3XIo1MrsIfW6WgI OxfDIXWP+Zf+Sc+HiwSjFZN7uVxwNRSHc26/g3KJ1rewiNah3X/dHoaLJNoy1XgC YQeVXJL8JeCXaCBvJiJ9hpNLVTjkxV3Pj3KfT2d+n7yjHBb5wDD/AHkCmXlowewo 1Z/WJWKD6jLx2mYOnmCXyC1NaaeULUCPSfArfYPLA3Nrwk/OIP2oCBa/lDmTjC/r 99K/ko+ArcLUAjVzp/JY1CoVcT0aNTwuIRTaD/lYE1wtw8L3Kxtfh3aHPvRuwqmq AFRZ75XYdp992bBYzWMN =eovu -----END PGP SIGNATURE----- --aNrRVSjHvB4CaVexBGn7gmJhp6qfTBGOc--