public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] strange eix-sync
Date: Thu, 11 Jul 2013 17:06:44 +0100	[thread overview]
Message-ID: <6C6FEF57-779C-4594-8627-B0310CA31C43@stellar.eclipse.co.uk> (raw)
In-Reply-To: <20130709172833.GA5375@solfire>


On 9 July 2013, at 18:28, meino.cramer@gmx.de wrote:
> ...
> receiving incremental file list
> timestamp.chk
> rsync: failed to set permissions on "/tmp/.tmpNBwK63.n6Acda": Function not implemented (38)

I can't say the problem is related to xattrs, but when posting an error with a message like this you need to demonstrate, for example, that the /tmp directory exists and that you can write to it.

I mean, it's pretty obvious that you'd get this error if the directory wasn't writable, right?

So posting here you need to *show* it's writable.

So please post the output of:

  ls -ld /tmp/
  ls -l /tmp/
  touch /tmp/foobar123
  chmod 777 /tmp/foobar123
  ls -l /tmp/foobar123
  rm -v /tmp/foobar123

I would also try testing whether you can sync using the `emerge --sync` command, instead.

I would guess that you're escalating to root permissions when using emerge and that the eix user has insufficient write permissions for some reason.

No offence, mate, but a Gentoo user shouldn't need to be told this. You surely have a couple of years of Linux experience, so you know how to create and list a file; even if you don't know the `chmod` command, you must know what permissions are and that they sometimes prevent an unprivileged user from doing stuff. Aren't you even curious to know if the /tmp directory exists? Page 1 of "How to Ask Questions The Smart Way" says to tell us what you've done to investigate the problem so far. I can't promise that the steps I've suggested will help identify or fix the problem, but they definitely need doing to show the filesystem exists and doesn't have a write-protect switch accidentally flipped - failure to provide this information implies you're sitting helplessly at home waiting for us to tell you all the answers, even the basics. 

Stroller.



  parent reply	other threads:[~2013-07-11 16:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-09 17:28 [gentoo-user] strange eix-sync meino.cramer
2013-07-10 11:27 ` Douglas J Hunley
2013-07-10 16:06   ` meino.cramer
2013-07-11 13:16     ` Douglas J Hunley
2013-07-11 16:06 ` Stroller [this message]
2013-07-11 18:58   ` meino.cramer
2013-07-11 19:49     ` Stroller
2013-07-13  5:19       ` meino.cramer
2013-07-13 11:35         ` Douglas J Hunley
2013-07-13 11:40           ` meino.cramer
2013-07-13 16:27             ` Stroller
2013-07-17 12:32             ` Douglas J Hunley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6C6FEF57-779C-4594-8627-B0310CA31C43@stellar.eclipse.co.uk \
    --to=stroller@stellar.eclipse.co.uk \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox