From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id AA1E5158086 for ; Tue, 12 Oct 2021 21:15:11 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 73E8EE086E; Tue, 12 Oct 2021 21:15:05 +0000 (UTC) Received: from ciao.gmane.io (ciao.gmane.io [116.202.254.214]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 3A702E0839 for ; Tue, 12 Oct 2021 21:15:04 +0000 (UTC) Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1maP6z-00029p-O7 for gentoo-user@lists.gentoo.org; Tue, 12 Oct 2021 23:15:01 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: Grant Edwards Subject: [gentoo-user] Re: Migrate from rsync to git for emerge --sync? Date: Tue, 12 Oct 2021 21:14:57 -0000 (UTC) Message-ID: References: User-Agent: slrn/1.0.3 (Linux) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply X-Archives-Salt: 8cf578e3-bc5a-4d41-8f63-8a9b0d5dc90c X-Archives-Hash: 01989d31eb90c77daa9f0996e539a93c On 2021-10-12, Rich Freeman wrote: > On Tue, Oct 12, 2021 at 4:02 PM Grant Edwards wrote: >> >> Despite what multiple blog and wiki pages claim, it seems it's not as >> simple as editing you gentoo.conf file. Do I need to wipe the contents >> of /usr/portage and start with an emptry directory there? > > I believe so. I'd just rename the directory and let it get > re-created. Then you can delete the old one when you are confident > you don't need it. Yep, I renamed the old one, switched the repo conf to the new /var/db location, and let emrge --sync clone a new repo directory using git. The 'git clone' finished OK, but the sync still failed (with a very obtuse Python exception and stack dump) when it got to the news processing step. After a bit of googling I found a hint that failure happens when there is no profile selected. I ran 'eselet profile set N'. After that, the sync completed OK. That seems like something that should be documented somewhere... I'll see if I can find an appropriate spot in the Wiki.