8949 – `emerge <pkg>` fails if /var/tmp/portage/ is read only

Bug 8949 - `emerge <pkg>` fails if /var/tmp/portage/ is read only

Summary: `emerge <pkg>` fails if /var/tmp/portage/ is read only

Status:	RESOLVED FIXED

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Unclassified (show other bugs)
Hardware:	x86 All

Importance:	High trivial
Assignee:	Daniel Robbins (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2002-10-09 17:38 UTC by SpanKY
Modified:	2011-10-30 22:21 UTC (History)
CC List:	2 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description SpanKY gentoo-dev

2002-10-09 17:38:38 UTC

this bug is being posted just so that the error is a little prettier ;)
maybe one could parse the output /proc/mounts to figure out which filesystem is 
causing this prob and show a message like 'the mount on <mount point> causes 
${TMPDIR} to be read-only ... please fix and run emerge again'

root@vapier root # emerge world -u
Calculating world dependencies ...done!
>>> emerge sys-devel/distcc-0.12 to /
Traceback (most recent call last):
  File "/usr/bin/emerge", line 1355, in ?
    mydepgraph.merge(mydepgraph.altlist())
  File "/usr/bin/emerge", line 903, in merge
    retval=portage.doebuild(y,"clean",myroot,edebug)
  File "/usr/lib/python2.2/site-packages/portage.py", line 1049, in doebuild
    os.makedirs(settings["BUILDDIR"])
  File "/usr/lib/python2.2/os.py", line 203, in makedirs
    mkdir(name, mode)
OSError: [Errno 30] Read-only file system: '/var/tmp/portage/distcc-0.12'

Comment 1 Nicholas Jones (RETIRED) gentoo-dev

2002-10-10 13:04:37 UTC

in cvs