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 6FEAA138330 for ; Tue, 13 Sep 2016 17:49:14 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8C283E0B73; Tue, 13 Sep 2016 17:49:07 +0000 (UTC) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.17.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id C6CA9E0B5B for ; Tue, 13 Sep 2016 17:49:06 +0000 (UTC) Received: from becker.bs.l ([85.180.9.102]) by mrelayeu.kundenserver.de (mreue101) with ESMTPSA (Nemesis) id 0MI6MY-1bjJ4I3RJW-003vPA for ; Tue, 13 Sep 2016 19:49:04 +0200 Received: from bsch by becker.bs.l with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1bjrpQ-000BlU-Ak for gentoo-user@lists.gentoo.org; Tue, 13 Sep 2016 19:49:04 +0200 Date: Tue, 13 Sep 2016 19:49:04 +0200 From: Bertram Scharpf To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Emerge interferes with Git (Was: Wlan disappeared after suspend) Message-ID: <20160913174904.GB44957@becker.bs.l> Mail-Followup-To: gentoo-user@lists.gentoo.org References: <20160913082326.GA38638@becker.bs.l> <72ddea8d-cf3d-74a3-3700-9ce6397be500@gentoo.org> <20160913131251.GA42144@becker.bs.l> 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 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.1 (2016-04-27) Sender: Bertram Scharpf X-Provags-ID: V03:K0:rI7N2E/H2+RkaAUQ68gUHg1GETmcyvGXk/s/fpdp9ZVO9IdkJFJ mFkH0Kr0nErGt6n6g9Ia4nJ0BaY1xXy0v6QZG1F6c6oJVdUc1PUtnoKgGli3Tnr5/vqwqZ1 /a+u8p1GYiYOLebLzDJTrmOrXY5OIUXrR8hpOGxbZmIcYVmxtL5zt/M/HDvKVjcA79Sf8Mq g8YUOjjwEkdneThXr77qw== X-UI-Out-Filterresults: notjunk:1;V01:K0:JbMNTyS1I2o=:AFl/MR+SRi0tdOBIXaxcj8 6OrtvMJ4YT0Rz2G0bTXmyvS2ZcD7z0C0qXzVrivFOIDmldJoY3rncINiK3IdDdHxdKpbDeWN2 Z6FWSok5GjwHbKdIM3CmNIbzxn3De4e35droSWuojL2Kzr8VcZBrj9RQ3HuDbjYIU1gAq7rc8 f67M02bmJF4IwSpR3IwBrzYeKXF+AVbumWL4O32TH1euZd337owYX2ic0gkwTJMOXmDerA8e3 5bcWkJ3WeZDaIbiCXdTGO43wyH7XuJPAaj6bP6/QzkvIUihMdUUOxep4OLofJYbGcohHqRkno 7byNdYivzGxAYAs60Aq/tp4Q/5hTFJ49aL6M/q5lq+fgDWGfH/5ilezMYmvvD95WSKj28/ebh AHntYHw9LguEmA0WgdoSio7bJynTSHwvPQJXW5Gl2gb1eyf+7OWpoLH0UN1WzlqwR4BfmIPRv KrDejM3k2x1/3g6kHWAPBiIj+A4NdO3+bIC3CSE7v/MK8T/kM8fFMC2R5kWAkcXBBtynyN/SG dCMUK1vNbppA7C3aAuEnl8Lpezs60iLVGeJQ4clM+jO1m7de24hLnuGIY/FLkrvZRmp5W/eLB ghD3d6KBfynvBf10gnqfPQBlhZoUVFpWF7J8peKzCCCnE9rhfos0OevyZ6qVTQ+pKdEyq//ue jlRZ6/Nzs2Pykc2k0Np2AGOZiWRib200e8yISUZgDTUUtDO9QU3j5L1scVN6EQc1g4Wc= X-Archives-Salt: b80c965b-1581-4a4c-9471-e4766c276b9f X-Archives-Hash: 7b338e1d680c8bfd294cad0965c8489e On Tuesday, 13. Sep 2016, 11:12:11 -0400, Rich Freeman wrote: > On Tue, Sep 13, 2016 at 9:12 AM, Bertram Scharpf > wrote: > > > > The rfkill install interferes with Git! > > > > Error log: > > P: /usr/portage/.git/index.lock > > A: /usr/portage/.git/index.lock > > R: /usr/portage/.git/index.lock > > C: git update-index --refresh --unmerged > > > >>>> '/usr/portage/tmp/portage/net-wireless/rfkill-0.5/temp/build.log' > > > > I helped myself by renaming the .git directory, but that's > > only a workaround. > > > > How can I fix this? Should I report this? > > It looks like you have your PORTAGE_TMPDIR set as /usr/portage/tmp? Indeed. I have a "build partition" that I use for both, package downloading and building in /usr/portage/tmp. The rfkill make suite looks for a version number and in case the work directory is a Git repo it tries to query the version number there. Then, it finds the Git repo in /usr/portage and fails. Not very friendly! > I suggest moving PORTAGE_TMPDIR to someplace like /var/tmp or /tmp or > someplace else. It isn't really ideal to have volatile information in > /usr anyway (this is the part where everybody chimes in and points out > that /usr/portage is in the wrong place to begin with). I'll see how I solve it. I do not have time to make a decision this evening. Bertram -- Bertram Scharpf Stuttgart, Deutschland/Germany http://www.bertram-scharpf.de