Summary: | emerge --pretend --fetchonly complains /var/tmp/portage is not writable: it should not matter | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Raffaello D. Di Napoli <rafdev> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | wtt6 |
Priority: | High | Keywords: | InVCS |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 381649 |
Description
Raffaello D. Di Napoli
2009-09-24 11:38:05 UTC
Just to clarify, /var/tmp/portage is really not writable, ’cause I only sudo emerge when not using --pretend (call it “added insurance” :) . (In reply to comment #0) > Expected Results: > Calculating dependencies... done! > > >>> Fetching (1 of 1) app-editors/nano-2.1.9 > >>> Downloading ... > (fetching messages follow) This is obviously wrong (I had to make it up, my bad). Expected results are really just printing the name of the files to be downloaded, with no fetching messages (and no actual fetching either). this can happen iff the user doing the emerge is not root or not part of the 'portage' group. We need a temp dir in order to satisfy bug 241118. However, since we're in pretend mode, we should use /tmp instead of PORTAGE_TMPDIR. (In reply to comment #4) > We need a temp dir in order to satisfy bug 241118. And also bug 239560. (In reply to comment #4) > We need a temp dir in order to satisfy bug 241118. However, since we're in > pretend mode, we should use /tmp instead of PORTAGE_TMPDIR. > can we expect /tmp to exist in prefix portage? (In reply to comment #6) > (In reply to comment #4) > > We need a temp dir in order to satisfy bug 241118. However, since we're in > > pretend mode, we should use /tmp instead of PORTAGE_TMPDIR. > > > > can we expect /tmp to exist in prefix portage? Well, when I said /tmp I really meant whatever directory python tempfile module uses by default, which should be fine. This should be fixed now that mkdtemp is used since this commit: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=2f3e904a0044c9dbaa644cd387339d8db632ae00 This still happens in sys-apps/portage-2.2.0_alpha64:
$ emerge -pqf virtual/linux-sources
/var/tmp/portage is not writable.
Likely cause is that you've mounted it as readonly.
>>> Failed to emerge virtual/linux-sources-0
(In reply to comment #9) > This still happens in sys-apps/portage-2.2.0_alpha64: > > $ emerge -pqf virtual/linux-sources > /var/tmp/portage is not writable. > Likely cause is that you've mounted it as readonly. > >>> Failed to emerge virtual/linux-sources-0 This is fixed in git: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=7b2be36898ef04a8cef42dc41cbc162004f329c2 This is fixed in 2.1.10.25 and 2.2.0_alpha65. |