public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Walter Dnes" <waltdnes@waltdnes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [SOLVED] Emerge --sync fails on excluded stuff
Date: Tue, 23 Oct 2018 17:14:17 -0400	[thread overview]
Message-ID: <20181023211417.GA26083@waltdnes.org> (raw)
In-Reply-To: <20181023082136.7adb040a@digimed.co.uk>

On Tue, Oct 23, 2018 at 08:21:36AM +0100, Neil Bothwick wrote
> On Mon, 22 Oct 2018 23:05:17 -0400, Walter Dnes wrote:
> 
> >   That looks easier, but... /etc/portage/repos.conf is a directory on my
> > system.
> 
> That's right, and in there is an entry for the gentoo repo, edit it.
> 
> Most files in /etc/portage can be directories, although some utilities
> get confused if make.conf is, portage just considers the contents as a
> single file.

  There are 2 files in my /etc/portage/repos.conf/ Namely localrepo.conf
and layman.conf.  Now what?  Sorry, I'm not trolling.  It's painful
when you RTFM, and TFM is out to lunch.

-- 
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications


  parent reply	other threads:[~2018-10-23 21:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-22 14:26 [gentoo-user] Emerge --sync fails on excluded stuff Walter Dnes
2018-10-22 16:11 ` Kai Peter
2018-10-22 17:36   ` [gentoo-user] [SOLVED] " Walter Dnes
2018-10-22 22:21     ` Neil Bothwick
2018-10-23  3:05       ` Walter Dnes
2018-10-23  3:30         ` Dale
2018-10-23  7:21         ` Neil Bothwick
2018-10-23 15:13           ` Mick
2018-10-23 21:10             ` Neil Bothwick
2018-10-23 21:14           ` Walter Dnes [this message]
2018-10-23 21:30             ` Neil Bothwick
2018-10-23 22:32               ` Mick
2018-10-24  1:49               ` Walter Dnes
2018-10-24  7:28                 ` Neil Bothwick
2018-10-24  8:26               ` Peter Humphrey

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=20181023211417.GA26083@waltdnes.org \
    --to=waltdnes@waltdnes.org \
    --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