| View previous topic :: View next topic |
| Author |
Message |
jody
l33t
Joined: 16 Oct 2007
Posts: 668
Location: Switzerland
|
 Posted: Sat Jan 04, 2014 4:46 pm Post subject: emerging gdm pulls in gnome 3.8 |
 |
|
I have installed systemd and want to continue using old gnome (2.32.1) and not gnome 3.8.
Currently systemd complains when i do "systemctl enable gdm.service" - indeed there is no gdm.service in /usr/lib/systemd/system
I remember reading somewhere that reemerging gdm (with the systemd USE flag) should also install gdm.service (correct me if i'm wrong).
But when i want to emerge gdm, it requires the entire gnome 3.8 stuff to be emerged as well (including all the blocks and conflicts)
How can i get gdm.service (for gnome 2.32) without gnome3.8 & Co?
Thank You
Jody |
|
| Back to top |
|
 |
TomWij
Retired Dev
Joined: 04 Jul 2012
Posts: 1553
|
|
| Back to top |
|
|
jody
l33t
Joined: 16 Oct 2007
Posts: 668
Location: Switzerland
|
| Posted: Sun Jan 05, 2014 12:39 pm Post subject: |
|
|
thank you for your reply.
I have started to put the names of the blocking or otherwise conflicting ebuilds into /etc/portage/package.mask,
and successively added more names after doing pretend-emerges.
Currently i have these in /etc/portage/package.mask
| Code: | >=gnome-base/gnome-3
>=gnome-base/gnome-core-apps-3
>=gnome-base/gnome-core-libs-3
>=gnome-base/gnome-keyring-3
>=gnome-base/gnome-menus-3
>=gnome-base/gnome-shell-3
>=app-editors/gedit-3
>=gnome-base/gnome-panel-3
>=gnome-base/gnome-extra-apps-3
>=games-board/aisleriot-3
>=app-crypt/gcr-3
>=gnome-base/gnome-settings-daemon-3
>=gnome-extra/evolution-data-server-3
>=gnome-base/gnome-control-center-3
>=gnome-base/gdm-3
|
This made it possible to emerge an old gdm. (unfortunately this has not created a gdm.service).
However, these masks are not ok - for the target "world" is still have lots of problems.
The way it looks the current gnome (and other stuff i still want) would be removed: | Code: | [ebuild R ] media-gfx/inkscape-0.48.4
[ebuild R ] x11,-misc/revelation-0.4.14
[ebuild R ] media-gfx/gimp-2.8.6
[ebuild R ] gnome-base/gnome-panel-2.32.1-r3
[ebuild R ] gnome-base/gnome-control-center-2.32.1-r1
[ebuild R ] gnome-base/gnome-applets-2.32.1.1-r2
[ebuild R ] gnome-base/gnome-2.32.1-r2
|
There are only two blocks, but i don't understand them: | Code: | [blocks B ] <gnome-base/gnome-keyring-3.3 ("<gnome-base/gnome-keyring-3.3" is blocking app-crypt/gcr-3.8.2)
[blocks B ] <dev-libs/gobject-introspection-1.36 ("<dev-libs/gobject-introspection-1.36" is blocking dev-libs/glib-2.36.4-r1)
|
First block: i have masked both gnome-keyring and gcr, why do they appear?
Second block: i have not masked any gobject-intorspection
There are still many slot conflicts involving things i masked, e.g. | Code: |
gnome-base/gnome-keyring:0
(gnome-base/gnome-keyring-3.8.2::gentoo, ebuild scheduled for merge) pulled in by
>=gnome-base/gnome-keyring-3.1.92 required by (gnome-base/libgnome-keyring-3.8.0::gentoo, ebuild scheduled for merge)
(and 1 more with the same problem)
(gnome-base/gnome-keyring-2.32.1-r1::gentoo, installed) pulled in by
(no parents that aren't satisfied by other packages in this slot)
|
and below | Code: | * Error: The above package list contains packages which cannot be
* installed at the same time on the same system.
(app-crypt/gcr-3.8.2::gentoo, ebuild scheduled for merge) pulled in by
>=app-crypt/gcr-3.5.3:=[gtk] required by (gnome-base/gnome-keyring-3.8.2::gentoo, ebuild scheduled for merge)
|
even though i masked '>=gnome-base/gnome-keyring-3'
At the end | Code: | The following mask changes are necessary to proceed:
(see "package.unmask" in the portage(5) man page for more details)
# required by gnome-base/libgnome-keyring-3.8.0
# /etc/portage/package.mask:
=gnome-base/gnome-keyring-3.8.2
# required by @selected
# required by @world (argument)
(-- snip --)
# /etc/portage/package.mask:
=app-crypt/gcr-3.8.2
# required by @selected
# required by @world (argument)
|
Isn't there a simple way top mask all of gnome 3.X without blocks and removal of things i still want?
Thank You
Jody |
|
| Back to top |
|
|
TomWij
Retired Dev
Joined: 04 Jul 2012
Posts: 1553
|
| Posted: Sun Jan 05, 2014 5:09 pm Post subject: |
|
|
| jody wrote: | The way it looks the current gnome (and other stuff i still want) would be removed: | Code: | [ebuild R ] media-gfx/inkscape-0.48.4
[ebuild R ] x11,-misc/revelation-0.4.14
[ebuild R ] media-gfx/gimp-2.8.6
[ebuild R ] gnome-base/gnome-panel-2.32.1-r3
[ebuild R ] gnome-base/gnome-control-center-2.32.1-r1
[ebuild R ] gnome-base/gnome-applets-2.32.1.1-r2
[ebuild R ] gnome-base/gnome-2.32.1-r2
|
|
R stands for "replacing (remerging same version)" according to `man emerge`, they do not get removed.
| jody wrote: | There are only two blocks, but i don't understand them: | Code: | [blocks B ] <gnome-base/gnome-keyring-3.3 ("<gnome-base/gnome-keyring-3.3" is blocking app-crypt/gcr-3.8.2)
[blocks B ] <dev-libs/gobject-introspection-1.36 ("<dev-libs/gobject-introspection-1.36" is blocking dev-libs/glib-2.36.4-r1)
|
First block: i have masked both gnome-keyring and gcr, why do they appear?
Second block: i have not masked any gobject-intorspection |
I think you need an older version of app-crypt/gcr such that you are able to have an older version of gnome-base/gnome-keyring; because than new app-crypt/gcr doesn't want an old gnome-base/gnome-keyring.
| jody wrote: | There are still many slot conflicts involving things i masked, e.g. | Code: |
gnome-base/gnome-keyring:0
(gnome-base/gnome-keyring-3.8.2::gentoo, ebuild scheduled for merge) pulled in by
>=gnome-base/gnome-keyring-3.1.92 required by (gnome-base/libgnome-keyring-3.8.0::gentoo, ebuild scheduled for merge)
(and 1 more with the same problem)
(gnome-base/gnome-keyring-2.32.1-r1::gentoo, installed) pulled in by
(no parents that aren't satisfied by other packages in this slot)
|
|
More version masking to be done here, mask them such that they cannot have a version >3; eventually an old version would pull in the old gnome-keyring.
| jody wrote: | and below | Code: | * Error: The above package list contains packages which cannot be
* installed at the same time on the same system.
(app-crypt/gcr-3.8.2::gentoo, ebuild scheduled for merge) pulled in by
>=app-crypt/gcr-3.5.3:=[gtk] required by (gnome-base/gnome-keyring-3.8.2::gentoo, ebuild scheduled for merge)
|
even though i masked '>=gnome-base/gnome-keyring-3' |
Eh, shouldn't it list two things to be a slot conflict; and indeed, that seems odd. Make sure you don't use --autounmask parameters.
| jody wrote: | At the end | Code: | The following mask changes are necessary to proceed:
(see "package.unmask" in the portage(5) man page for more details)
# required by gnome-base/libgnome-keyring-3.8.0
# /etc/portage/package.mask:
=gnome-base/gnome-keyring-3.8.2
# required by @selected
# required by @world (argument)
(-- snip --)
# /etc/portage/package.mask:
=app-crypt/gcr-3.8.2
# required by @selected
# required by @world (argument)
|
|
Indeed, don't do what it tells you here. There's a problem here too: Why are these packages in @selected and @world? Remove libraries like this from /var/lib/portage/world.
| jody wrote: | Isn't there a simple way top mask all of gnome 3.X without blocks and removal of things i still want?
Thank You
Jody |
You might find ways to do this here on the forums, but I don't keep track of them; here's however one I heard is popular: https://forums.gentoo.org/viewtopic-t-977288-highlight-.html |
|
| Back to top |
|
|
666threesixes666
Veteran
Joined: 31 May 2011
Posts: 1248
Location: 42.68n 85.41w
|
| Posted: Sun Jan 05, 2014 9:51 pm Post subject: |
|
|
as i said in other threads, i posted systemd instructions for lightdm and slim wiki pages. i should go over gdm  |
|
| Back to top |
|
|
TomWij
Retired Dev
Joined: 04 Jul 2012
Posts: 1553
|
| Posted: Mon Jan 06, 2014 12:00 am Post subject: |
|
|
| 666threesixes666 wrote: | | as i said in other threads, i posted systemd instructions for lightdm and slim wiki pages. i should go over gdm |
Which other threads? Can you link to them for the OP? |
|
| Back to top |
|
|
666threesixes666
Veteran
Joined: 31 May 2011
Posts: 1248
Location: 42.68n 85.41w
|
|
| Back to top |
|
|
|
Portage & Programming
