From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 2A2BE138CE3 for ; Mon, 10 Feb 2014 20:30:23 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E5576E0CDB; Mon, 10 Feb 2014 20:30:12 +0000 (UTC) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id BB72AE0CC7 for ; Mon, 10 Feb 2014 20:30:11 +0000 (UTC) Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id A498220D0E for ; Mon, 10 Feb 2014 15:30:10 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute3.internal (MEProxy); Mon, 10 Feb 2014 15:30:10 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.co.uk; h= message-id:date:from:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; s=mesmtp; bh=czT3Ofk/294f6XxhEj3W7OQRgu8=; b=aVFLfSBSnfG8DgKl/tyROQJrjnSN dvjPQvZnJQgzdr0/7WoZve9eVLpNWQfrO28m5VhgSE1yYGXicRcQEmLRmRyFAVE1 4riVt65M7q251vvTu+3SGHeHt47oa7gxNAYDNCJt24Gu3eavGWg1sr7Vi48mJ/Ly 2aOtbcaMPzlH5Hw= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=czT3Ofk/294f6XxhEj3W7O QRgu8=; b=O8LYXXBRlV7u39bJxoPPYyNEgPI5QBM/aQHdO1VgNjso+1fdiNeFwI KSCSX4ziMFJv3lZFyoxMQ9Nh/yQ46ZTaDTLCUEwsjpyh/1fXG165LUAHTiWL9Kck xDllAxXJopCGvYSeQqqhAOF1k5ZCSpGzLCe9hSo3DNlnDuWgGfRwA= X-Sasl-enc: vdQiXggmwOvPB04Dv85SMj/bRsCLWCNWUrFaS1tZXur+ 1392064210 Received: from [10.160.199.8] (unknown [85.255.234.171]) by mail.messagingengine.com (Postfix) with ESMTPA id 2781AC007AE for ; Mon, 10 Feb 2014 15:30:10 -0500 (EST) Message-ID: <52F936CF.4060808@fastmail.co.uk> Date: Mon, 10 Feb 2014 20:30:07 +0000 From: Kerin Millar User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 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 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] User eix-sync permissions problem References: <197AEEF5-2BA3-43BF-944E-A5C4230D4CFB@stellar.eclipse.co.uk> In-Reply-To: <197AEEF5-2BA3-43BF-944E-A5C4230D4CFB@stellar.eclipse.co.uk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-Archives-Salt: 5796a06d-9356-49c2-bde5-7141910fc38c X-Archives-Hash: 113fbad47c6794acb259b13c5f772622 On 10/02/2014 16:05, Stroller wrote: > Hello all, > > I'm a little bit rusty, but my recollection is that I should be able to perform `eix-sync` (or `emerge --sync`?) as a user to synchronise my local copy of the portage tree with Gentoo's master portage tree. > > User is in the portage group: > > $ whoami > stroller > $ groups stroller > wheel audio video portage cron users > $ > > Yet I get these permissons denied errors: > > $ eix-sync > * Running emerge --sync >>>> Synchronization of repository 'gentoo' located in '/usr/portage'... >>>> Starting rsync with rsync://91.186.30.235/gentoo-portage... >>>> Checking server timestamp … > … > receiving incremental file list > rsync: delete_file: unlink(app-accessibility/caribou/caribou-0.4.12.ebuild) failed: Permission denied (13) > rsync: delete_file: unlink(app-accessibility/emacspeak/files/emacspeak-33.0-respect-ldflags.patch) failed: Permission denied (13) > rsync: delete_file: unlink(app-accessibility/emacspeak/files/emacspeak-33.0-greader-garbage.patch) failed: Permission denied (13) > > (full output attached) > > > Googling the problem I see a bunch of Gentoo Forums posts talking about changing at random the permissions of /var/tmp/ or /var/tmp/portage/, but no rationale is given, and I don't think this is the cause: > > $ emerge --info | grep -i tmpdir > PORTAGE_TMPDIR="/var/tmp" > $ ls -ld /var/tmp/ > drwxrwxrwt 3 root root 4096 Feb 5 13:47 /var/tmp/ > $ ls -ld /var/tmp/portage/ > drwxrwxr-x 5 portage portage 4096 Feb 5 12:32 /var/tmp/portage/ > $ > > > More likely seems to be the permissions of /usr/portage/: > > $ ls -ld /usr/portage/ > drwxr-xr-x 167 portage portage 4096 Jan 5 02:31 /usr/portage/ > $ ls -ld /usr/portage/app-accessibility/caribou/caribou*.ebuild > -rw-r--r-- 1 portage portage 2432 Aug 25 23:11 /usr/portage/app-accessibility/caribou/caribou-0.4.12.ebuild > -rw-r--r-- 1 portage portage 2431 Dec 8 18:01 /usr/portage/app-accessibility/caribou/caribou-0.4.13.ebuild > $ > > This would seem to allow portage itself to synchronise the Portage tree, but not members of the portage group. > > > I am able to run `emerge --sync` as root, but it doesn't solve the solve the problem - next time I run `eix-sync` as user, I'm permissions denied, again. > > Shouldn't a sync reset the permissions of the portage tree to be correct? > > > `emerge --info | grep -i feature` shows that FEATURES="userfetch userpriv usersandbox usersync" (and some others - see attached) are set. > > I can reproduce this on a second AMD64 machine, both are running portage-2.2.7. > > Thanks in advance for any help, advice or suggestions you can offer, This should work:- PORTAGE_RSYNC_EXTRA_OPTS="--chmod=g+w" --Kerin