public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Bruce Schultz <brulzki@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Moving the portage tree to /var
Date: Wed, 08 Oct 2014 01:29:59 +1000	[thread overview]
Message-ID: <1ED07205-C857-49AB-8E2D-1323321D9161@gmail.com> (raw)
In-Reply-To: <4473472.7D6UrCk1jI@wstn>



On 8 October 2014 1:09:54 AM AEST, Peter Humphrey <peter@prh.myzen.co.uk> wrote:
>Afternoon all,
>
>As a step towards exporting my portage tree over NFS I decided to move 
>/usr/portage to /var/portage, but leave /usr/portage/packages and 
>/usr/portage/distfiles where they are.
>
>This is how it looks now:
>
>$ grep DIR= /etc/portage/make.conf
>DISTDIR="/usr/portage/distfiles"
>PKGDIR="/usr/portage/packages"
>PORTDIR="/var/portage"
>
>$ ls -l /etc/portage/make.profile
>lrwxrwxrwx 1 root root 51 Oct  7 15:28 /etc/portage/make.profile -> 
>../../var/portage/profiles/default/linux/amd64/13.0
>
>$ mount | grep portage
>/dev/mapper/vg7-portage on /var/portage type ext4 (rw,relatime)
>/dev/mapper/vg7-packages on /usr/portage/packages type ext4
>(rw,relatime)
>/dev/mapper/vg7-distfiles on /usr/portage/distfiles type ext4
>(rw,relatime)
>
>This seems to work OK, except for eix-update, which gives me this:
>
>$ eix-update
>Reading Portage settings ..
>Building database (/var/cache/eix/portage.eix) ..
>[0] "gentoo" /var/portage/ (cache: metadata-md5-or-flat)
>     Reading category 162|162 (100%) Finished             
>[1] "" /usr/portage (cache:
>parse|ebuild*#metadata-md5#metadata-flat#assign)
>     Reading category 162|162 (100%) EMPTY!
>[...]
>
>Evidently something is still pointing to /usr/portage, but I can't see
>what. I 
>used to have layman and a couple of overlays on this box, but they've
>now 
>gone. Well, maybe I left something lying around.
>
>I've grepped for likely-looking strings, read the docs and prodded
>google, but 
>I can't see what I'm missing. Would someone please help me out? I'm
>sure I'm 
>just being dense.

Check /etc/portage/repos.conf

Bruce
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.


  reply	other threads:[~2014-10-07 15:31 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-07 15:09 [gentoo-user] Moving the portage tree to /var Peter Humphrey
2014-10-07 15:29 ` Bruce Schultz [this message]
2014-10-07 15:39   ` Peter Humphrey
2014-10-07 16:08     ` Neil Bothwick
2014-10-07 21:48       ` Mick
2014-10-07 21:56         ` Mike Gilbert
2014-10-07 22:03           ` Mick
2014-10-25 13:57             ` Tanstaafl
2014-10-25 16:45               ` Michael Orlitzky
2014-10-25 17:49                 ` Mick
2014-10-25 17:59                   ` Michael Orlitzky
2014-10-26 14:02                     ` [gentoo-user] " Martin Vaeth
2014-10-26 14:46                       ` Michael Orlitzky
2014-10-26  8:56                 ` [gentoo-user] " Peter Humphrey
2014-10-27 15:45                 ` Tanstaafl
2014-10-27 19:06                   ` Alan McKinnon
2014-10-27 20:05                     ` Mike Gilbert
2014-10-29 11:37                       ` [gentoo-user] " Martin Vaeth
2014-10-30 11:17                         ` [gentoo-user] Switch from PORTDIR and PORTDIR_OVERLAY to repos.conf - WAS: " Tanstaafl
2014-10-08 11:36           ` [gentoo-user] " Tanstaafl
2014-10-07 15:37 ` Neil Bothwick
2014-10-07 15:57 ` Tomas Mozes
2014-10-07 16:02   ` Tomas Mozes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1ED07205-C857-49AB-8E2D-1323321D9161@gmail.com \
    --to=brulzki@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox