Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 389893 - Cannot chown a lockfile: '/usr/portage/distfiles/.linux-3.1.tar.bz2.portage_lockfile'
Summary: Cannot chown a lockfile: '/usr/portage/distfiles/.linux-3.1.tar.bz2.portage_l...
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-08 14:54 UTC by Vicente Olivert Riera (RETIRED)
Modified: 2011-11-08 21:50 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vicente Olivert Riera (RETIRED) gentoo-dev 2011-11-08 14:54:40 UTC
When I try to install sys-kernel/gentoo-sources-3.1.0-r1 I get this error:

http://pastebin.com/7Hi09YgK

I have a shared /usr/portage/distfiles/ directory by NFS, so I think that is the problem because I can install it if I unmount /usr/portage/distfiles/ directory.

This is the NFS configuration in the server:

atom ~ # cat /etc/exports 
# /etc/exports: NFS file systems being exported.  See exports(5).
/usr/portage/distfiles/ 172.16.0.0/24(async,rw,no_subtree_check,insecure,no_root_squash)

And, in the clients I have this:

[15:52:36] peratu@fujitsu ~ $ grep nfs /etc/fstab 
172.16.0.7:/usr/portage/distfiles	/usr/portage/distfiles	nfs	rw 0 0
Comment 1 Ian Stakenvicius (RETIRED) gentoo-dev 2011-11-08 21:20:30 UTC
..moving the pastebin content into the bug:


[14:41:04] root@fujitsu /home/peratu # emerge -DNu world
Calculating dependencies... done!

>>> Verifying ebuild manifests

>>> Emerging (1 of 1) sys-kernel/gentoo-sources-3.1.0-r1
[Errno 22] Invalid argument: '/usr/portage/distfiles/.linux-3.1.tar.bz2.portage_lockfile': chown('/usr/portage/distfiles/.linux-3.1.tar.bz2.portage_lockfile', -1, 250)
Cannot chown a lockfile: '/usr/portage/distfiles/.linux-3.1.tar.bz2.portage_lockfile'
Group IDs of current user: 0 1 2 3 4 6 10 11 20 26 27 1006
 * linux-3.1.tar.bz2 RMD160 SHA1 SHA256 size ;-) ...                                                                                                                                                                     [ ok ]
Traceback (most recent call last):
  File "/usr/lib64/portage/pym/_emerge/EbuildFetcher.py", line 186, in _spawn
    allow_missing_digests=allow_missing):
  File "/usr/lib64/portage/pym/portage/package/ebuild/fetch.py", line 653, in fetch
    stat_cached=mystat)
  File "/usr/lib64/portage/pym/portage/util/__init__.py", line 1078, in apply_secpass_permissions
    stat_cached=stat_cached, follow_links=follow_links)
  File "/usr/lib64/portage/pym/portage/util/__init__.py", line 908, in apply_permissions
    os.chown(filename, uid, gid)
  File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
    rval = self._func(*wrapped_args, **wrapped_kwargs)
OSError: [Errno 22] Invalid argument: '/usr/portage/distfiles/linux-3.1.tar.bz2'
 * Fetch failed for 'sys-kernel/gentoo-sources-3.1.0-r1', Log file:
 *  '/var/tmp/portage/sys-kernel/gentoo-sources-3.1.0-r1/temp/build.log'

>>> Failed to emerge sys-kernel/gentoo-sources-3.1.0-r1, Log file:

>>>  '/var/tmp/portage/sys-kernel/gentoo-sources-3.1.0-r1/temp/build.log'

 * Messages for package sys-kernel/gentoo-sources-3.1.0-r1:

 * Fetch failed for 'sys-kernel/gentoo-sources-3.1.0-r1', Log file:
 *  '/var/tmp/portage/sys-kernel/gentoo-sources-3.1.0-r1/temp/build.log'
[15:42:06] root@fujitsu /home/peratu #
Comment 2 Ian Stakenvicius (RETIRED) gentoo-dev 2011-11-08 21:28:48 UTC
This definitely seems to be an issue relating to permissions on either the NFS server or client.  I would recommend changing your setup -- either adjusting the permissions of that share, or switching things around so that you use a local distfiles dir and a local distfiles mirror.

Specific to the permissions issue, i am unsure of what exactly you'll need to set to fix this; it could just be that the gid's don't match up between systems?

Another issue might simply be that the lockfile exists and shouldn't; perhaps try removing it from the server?

Either way though, this doesn't look like a bug to me.