548052 – app-portage/portage-utils: caching fails when repo is read-only

Bug 548052 - app-portage/portage-utils: caching fails when repo is read-only

Summary: app-portage/portage-utils: caching fails when repo is read-only

Status:	RESOLVED FIXED

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Third-Party Tools (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Portage Utils Team

URL:
Whiteboard:
Keywords:

Duplicates (1):	549630 (view as bug list)
Depends on:
Blocks:

Reported:	2015-04-28 18:38 UTC by Adam Feldman
Modified:	2015-05-19 17:38 UTC (History)
CC List:	1 user (show)

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

Attachments
emerge --info (7a056e7f529f.txt,5.22 KB, text/plain) 2015-04-28 18:39 UTC, Adam Feldman	Details
View All 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 Adam Feldman gentoo-dev

2015-04-28 18:38:17 UTC

My gentoo repo is hosted via read only NFS and mounted at /var/lib/repos/gentoo.

When I attempt to qgrep foo, I get:

grep: Updating ebuild cache ...                                                     
grep: initialize_flat(): unlinking '/var/lib/repos/gentoo/.ebuild.x' failed: Read-only file system

Tested with versions 0.3.1, 0.53, 0.54

Reproducible: Always

Comment 1 Adam Feldman gentoo-dev

2015-04-28 18:39:20 UTC

Created attachment 402188 [details]
emerge --info

Comment 2 SpanKY gentoo-dev

2015-05-17 02:41:21 UTC

*** Bug 549630 has been marked as a duplicate of this bug. ***

Comment 3 SpanKY gentoo-dev

2015-05-19 17:38:23 UTC

took a bit of reworking, but fixed in git now:
http://gitweb.gentoo.org/proj/portage-utils.git/commit/?id=357a4c2d329ccf46cddb96e07c9308105e977fd3