| 1 |
On Tue, 1 Sep 2015 01:51:51 +0200 (CEST) |
| 2 |
Jeremi Piotrowski <jeremi.piotrowski@×××××.com> wrote: |
| 3 |
|
| 4 |
> On Mon, 31 Aug 2015, covici@××××××××××.com wrote: |
| 5 |
> |
| 6 |
> [snip] |
| 7 |
> |
| 8 |
> > Just to let you know, most of the python entries were mandated by |
| 9 |
> > portage, certainly the systemd one. |
| 10 |
> > emerge --info |
| 11 |
> > Portage 2.2.20.1 (python 2.7.10-final-0, |
| 12 |
> > default/linux/amd64/13.0/desktop/gnome, gcc-4.9.3, glibc-2.21-r1, |
| 13 |
> > 3.16.3-gentoo x86_64) |
| 14 |
> |
| 15 |
> I think this is your problem right here: you don't have the systemd |
| 16 |
> profile selected. You're trying to splice together the use settings |
| 17 |
> needed to get this to work when all of them are already gathered in |
| 18 |
> the right profile. |
| 19 |
> |
| 20 |
> Remove most of the use settings you were forced to make because of |
| 21 |
> systemd related issues, change your profile to |
| 22 |
> |
| 23 |
> default/linux/amd64/13.0/desktop/gnome/systemd |
| 24 |
> |
| 25 |
> and emerge -uDUva @world. |
| 26 |
> |
| 27 |
> This should remove most (if not all) of the blockers caused by |
| 28 |
> conflicting use flags you currently have set. |
| 29 |
|
| 30 |
Thank you. I've been running systemd for months and this is the first |
| 31 |
time I've heard about systemd profiles. I'm not using either gnome or |
| 32 |
kde, so should I use default/linux/amd64/13.0/systemd, which doesn't |
| 33 |
seem to care if I'm running a desktop machine or a headless server? |
Archives