With squashdelta, the gentoo repository ("portage tree") is mounted readonly, because it resides on a squash filesystem. Unsurprisingly, portage-utils does not like this: q: Updating ebuild cache ... q: initialize_flat(): unlinking '/srv/repo-gentoo/.ebuild.x' failed: Read-only file system Perhaps that file could be moved inside /var/cache/edb or /var/cache/portage (the latter is used by squashdelta) or, if necessary, /var/cache/portage-utils If none appears reasonable, perhaps there could be added a configuration about that file?
*** This bug has been marked as a duplicate of bug 548052 ***
It is not really a duplicate: This is about all of portage-utils ("q -r"), not only about qgrep. Actually, "qgrep foo" triggers a worse error here: grep: chdir to PORTDIR '/usr/portage' failed: No such file or directory It is worse, because neither PORTDIR from /etc/portage/make.conf nor /etc/portage/repos.conf points to /usr/portage.
(In reply to Martin Väth from comment #2) > It is not really a duplicate: > > This is about all of portage-utils ("q -r"), not only about qgrep. > > Actually, "qgrep foo" triggers a worse error here: > > grep: chdir to PORTDIR '/usr/portage' failed: No such file or directory > > It is worse, because neither PORTDIR from /etc/portage/make.conf nor > /etc/portage/repos.conf points to /usr/portage. q: initialize_flat(): unlinking '/srv/repo-gentoo/.ebuild.x is the error thrown in the ro qgrep case as well. Regarding your other error, are you sure that you have PKGDIR set to /srv/repo-gentoo in your make.conf?
(In reply to NP-Hardass from comment #3) > [...] is the error thrown in the ro qgrep case as well. I didn't say that the bugs are unrelated; I just want to avoid that this is considered a particular problem of qgrep > Regarding your other error, are you sure that you have PKGDIR set to > /srv/repo-gentoo in your make.conf? Yes (s/PKGDIR/PORTDIR/) Playing around, I found that the reason is that /etc/portage/make.conf is a directory in my case. When I merge the files into a single file, I get the same error as in bug 548052.
