public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: walt <w41ter@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: a few blockers I can't figure out
Date: Wed, 2 Sep 2015 04:57:32 -0700	[thread overview]
Message-ID: <20150902045732.1def775f@a6> (raw)
In-Reply-To: alpine.LNX.2.20.1509010138210.21727@gentoo-tp.localdomain

On Tue, 1 Sep 2015 01:51:51 +0200 (CEST)
Jeremi Piotrowski <jeremi.piotrowski@gmail.com> wrote:

> On Mon, 31 Aug 2015, covici@ccs.covici.com wrote:
> 
> [snip]
> 
> > Just to let you know, most of the python entries were mandated by
> > portage, certainly the systemd one.
> > emerge --info
> > Portage 2.2.20.1 (python 2.7.10-final-0,
> > default/linux/amd64/13.0/desktop/gnome, gcc-4.9.3, glibc-2.21-r1,
> > 3.16.3-gentoo x86_64)  
> 
> I think this is your problem right here: you don't have the systemd
> profile selected. You're trying to splice together the use settings
> needed to get this to work when all of them are already gathered in
> the right profile. 
> 
> Remove most of the use settings you were forced to make because of
> systemd related issues, change your profile to
> 
>     default/linux/amd64/13.0/desktop/gnome/systemd 
> 
> and emerge -uDUva @world. 
> 
> This should remove most (if not all) of the blockers caused by
> conflicting use flags you currently have set.

Thank you.  I've been running systemd for months and this is the first
time I've heard about systemd profiles.  I'm not using either gnome or
kde, so should I use default/linux/amd64/13.0/systemd, which doesn't
seem to care if I'm running a desktop machine or a headless server?



  parent reply	other threads:[~2015-09-02 11:58 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31  4:19 [gentoo-user] a few blockers I can't figure out covici
2015-08-31  8:50 ` Neil Bothwick
2015-08-31  9:04   ` covici
2015-08-31  9:36 ` Alan McKinnon
2015-08-31 11:03   ` covici
2015-08-31 11:10     ` Alan McKinnon
2015-08-31 11:49       ` covici
2015-08-31 12:40         ` Alan McKinnon
2015-08-31 13:37           ` Alec Ten Harmsel
2015-08-31 14:03           ` covici
2015-08-31 14:53             ` Alan McKinnon
2015-08-31 16:54               ` covici
2015-08-31 17:02                 ` Neil Bothwick
2015-08-31 18:12                   ` covici
2015-08-31 22:18                 ` Alan McKinnon
2015-09-01  0:12                   ` covici
2015-09-01  9:55                     ` Alan McKinnon
2015-09-01 10:15                       ` Rich Freeman
2015-09-01 11:13                         ` covici
2015-09-01 11:45                           ` Rich Freeman
2015-09-01 11:54                             ` covici
2015-09-01 10:18                       ` Marc Joliet_1
2015-09-01 10:46                         ` Alan McKinnon
2015-09-01 11:03                       ` covici
2015-09-01 11:15                         ` Alan McKinnon
2015-08-31 23:51                 ` Jeremi Piotrowski
2015-09-01  0:22                   ` covici
2015-09-02 11:57                   ` walt [this message]
2015-09-02 12:45                     ` [gentoo-user] " Rich Freeman
2015-09-02 13:06                     ` Jeremi Piotrowski

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=20150902045732.1def775f@a6 \
    --to=w41ter@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