Mailing List Archive

On Thu, Oct 17, 2013, at 10:44 AM, Tyrin Price wrote:
> Greetings,
>
> I am a newbie to Gentoo but not new to Linux and I am having
> difficulty setting up Gnome3 on a fresh Gentoo install.
>
> I've read many wiki entries and tips online. So far the best advice I
> received was on IRC but I am still stopped.
>
> Here is what I have done:
>
> Fresh install (amd64 architecture).
>
> Added ACCEPT_KEYWORDS="~amd64" to /etc/portage/make.conf
>
> Emerged dbus and added it to services started at boot time.
>
> Changed profile to gnome/systemd
>
> Now, I cannot figure out how to get around the problems shown when I
> try to emerge gnome.
>
> http://pastebin.com/NsbycC27 shows the output of emerge gnome

[blocks B ] sys-fs/udev ("sys-fs/udev" is blocking
sys-apps/systemd-208-r2)
[blocks B ] <sys-apps/openrc-0.12 ("<sys-apps/openrc-0.12" is
blocking sys-apps/kmod-15)
[blocks B ] sys-apps/systemd ("sys-apps/systemd" is blocking
sys-fs/udev-204)

Blocks 1 and 3 are the same: You can't have systemd and sys-fs/udev
installed simultaneously. Block 2 is telling you you need to upgrade or
uninstall openrc before you pull in kmod-15.

However, I strongly suggest you *not* do a huge upgrade this way. If
it's a new install and you are initally on "amd64" My recommendation is
to follow these steps:

1. Say on amd64. Bring yourself to a consistent state (emerge -DuvaN
@world; revdep-rebuild; emerge --depclean --ask)
2. Switch to ~amd64. Bring yourself to a consistent state.
3. Switch to systemd (Read the wiki article). Bring yourself to a
consistent state.
4. emerge gnome.

Doing everything at once (IMO) is just a recipe for headaches. The best
thing is to do smaller steps, verify, then move to the next step. Sure
you can do everything in one step, but when there is a problem it will
be more difficult to figure out which change created which problem (was
it switching to testing? switching to systemd? etc.).

HTH,
-a

marduk posted on Thu, 17 Oct 2013 12:44:21 -0400 as excerpted:

> Doing everything at once (IMO) is just a recipe for headaches. The best
> thing is to do smaller steps, verify, then move to the next step. Sure
> you can do everything in one step, but when there is a problem it will
> be more difficult to figure out which change created which problem (was
> it switching to testing? switching to systemd? etc.).

FWIW as a kde user not a gnomie, but with a decade on gentoo early next
year, I'll heartily endorse that recommendation! All sorts of stuff is
possible on gentoo and it's more flexible than most binary distro users
could begin to imagine, but by the same token major changes can and do
occasionally get quite complex, and taking it a step at a time and
bringing the system to a consistent state (or as consistent as possible,
sometimes you break the consistent steps down into smaller steps too, and
only make sure the individual area you're working on is consistent for
that sub-step) at each step is /the/ way to success.

The same general policy applies once you're all current, if you then
slack off for a year and don't do updates, then try to get current
again. I do updates on my main machine generally weekly if not more
often, but I sometimes go a year or more between netbook updates[1],
which means there's almost certain to be blockers when I try to update
everything at once, but by breaking the big update into smaller
intermediate steps and just updating what I can at each step, I resolve
them one by one until there's no blockers remaining and I'm fully updated
once again.

---
[1] I deliberately don't keep anything personal but the user passwords
themselves on the netbook, and contrary to what the name netbook implies,
I don't actually have wifi setup or do much networking other than behind
the local firewall with it, so otherwise vital security updates aren't a
big deal as exposure is very limited.

--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman

On Thu, Oct 17, 2013 at 12:44:21PM -0400, marduk@letterboxes.org wrote:
>However, I strongly suggest you *not* do a huge upgrade this way. If
>it's a new install and you are initally on "amd64" My recommendation is
>to follow these steps:
>
>1. Say on amd64. Bring yourself to a consistent state (emerge -DuvaN
>@world; revdep-rebuild; emerge --depclean --ask)
>2. Switch to ~amd64. Bring yourself to a consistent state.
>3. Switch to systemd (Read the wiki article). Bring yourself to a
>consistent state.
>4. emerge gnome.

Is it a good idea to go ahead and get X working before the switch to
~amd64?


--

Regards,

-=[Ty]=-

I am making progress. I now have a stable testing system (~amd64)
booting with systemd for init.

WhenI try to emerge gnome at this point, I get:

!!! The ebuild selected to satisfy ">=app-misc/tracker-0.16" has unmet
requirements.
- app-misc/tracker-0.16.2::gentoo USE="iso jpeg miner-fs tiff vorbis
xml -cue (-eds) -exif -firefox-bookmarks -flac -gif -gsf -gstreamer
-gtk -iptc -laptop -libsecret -mp3 -nautilus -networkmanager -pdf
-playlist -rss -test -thunderbird -upnp-av -xine -xmp -xps"

The following REQUIRED_USE flag constraints are unsatisfied:
exactly-one-of ( gstreamer xine )

The above constraints are a subset of the following complete
expression:
exactly-one-of ( gstreamer xine ) cue? ( gstreamer )
upnp-av? ( gstreamer ) !miner-fs? ( !cue !exif !flac
!gif !gsf !iptc !iso !jpeg !mp3 !pdf !playlist !tiff
!vorbis !xml !xmp !xps )

(dependency required by
"gnome-base/gnome-extra-apps-3.8.0-r1[tracker]"
[ebuild])
(dependency required by "gnome-base/gnome-3.8.0[extras]"
[ebuild])
(dependency required by "gnome" [argument])

I cannot tell what it is telling me to do to satisfy app-misc/tracker-0.16

--

Regards,

-=[Ty]=-

On Fri, Oct 18, 2013 at 09:27:52PM -0500, Tyrin Price wrote:
>I am making progress. I now have a stable testing system (~amd64)
>booting with systemd for init.
>
>WhenI try to emerge gnome at this point, I get:


Oops! I had forgotten to change my profile to gnome/systemd and
stabilize. :-)

--

Regards,

-=[Ty]=-

--

On Fri, Oct 18, 2013, at 10:27 PM, Tyrin Price wrote:
> I am making progress. I now have a stable testing system (~amd64)
> booting with systemd for init.
>
> WhenI try to emerge gnome at this point, I get:
>
> !!! The ebuild selected to satisfy ">=app-misc/tracker-0.16" has unmet
> requirements.
> - app-misc/tracker-0.16.2::gentoo USE="iso jpeg miner-fs tiff vorbis
> xml -cue (-eds) -exif -firefox-bookmarks -flac -gif -gsf -gstreamer
> -gtk -iptc -laptop -libsecret -mp3 -nautilus -networkmanager -pdf
> -playlist -rss -test -thunderbird -upnp-av -xine -xmp -xps"
>
> The following REQUIRED_USE flag constraints are unsatisfied:
> exactly-one-of ( gstreamer xine )

"exactly-one-of" means just that. The package (in this case
app-misc/tracker-0.16.2) requires exactly one of the use flags
("gstreamer", "xine"). You have "-gstreamer" and "-xine" and therefore
violate the constraint.

I recomment enabling "gstreamer". As you'll likely be pulling it in
anyway for GNOME.

On Sat, Oct 19, 2013 at 09:39:27AM -0400, marduk@letterboxes.org wrote:
>"exactly-one-of" means just that. The package (in this case
>app-misc/tracker-0.16.2) requires exactly one of the use flags
>("gstreamer", "xine"). You have "-gstreamer" and "-xine" and therefore
>violate the constraint.
>
>I recomment enabling "gstreamer". As you'll likely be pulling it in
>anyway for GNOME.
>

Yes, I had tried being very specific in package.use with:

=app-misc/tracker-0.16 gstreamer

and

=app-misc/tracker-0.16 xine

But, those did not work. Tried...

app-misc/tracker gstreamer

...and succeeded.

Now I am stuck with the problem I posted in a new thread about
involving telepathy-mission-control-5.14.1 while emerging
gnome.

It fails to compile with a syntax error.

I got about halfway through the 300+ builds I started with "emerge
gnome" before going to bed last night.

--
Regards

-=[Ty]=-

On Sat, Oct 19, 2013, at 10:13 AM, Tyrin Price wrote:
> On Sat, Oct 19, 2013 at 09:39:27AM -0400, marduk@letterboxes.org wrote:
> >"exactly-one-of" means just that. The package (in this case
> >app-misc/tracker-0.16.2) requires exactly one of the use flags
> >("gstreamer", "xine"). You have "-gstreamer" and "-xine" and therefore
> >violate the constraint.
> >
> >I recomment enabling "gstreamer". As you'll likely be pulling it in
> >anyway for GNOME.
> >
>
> Yes, I had tried being very specific in package.use with:
>
> =app-misc/tracker-0.16 gstreamer
>
> and
>
> =app-misc/tracker-0.16 xine
>
> But, those did not work. Tried...
>
> app-misc/tracker gstreamer
>
> ...and succeeded.
>

That's because 0.16.2 != 0.16.

In general, avoid being *too* specific. Especially when there is no
need for that level of specificity. (E.g. why only allow gstreamer for
tracker-0.16? What happens when 0.16.x comes out? What about 0.17?).

I want to express my thanks for the help provided here. I was able to
install gnome3 using the method outlined in this thread.

--

Regards,

-=[Ty]=-


--