[solved] there are no ebuilds to satisfy ">=sys-fs/udev-18

san2ban · 2012-10-02 04:39:16

Pl. see below. I used --autounmask -write when it said as below

(chroot) unknown001bb9b49eba / #  emerge xfce4-meta
Calculating dependencies... done!

The following mask changes are necessary to proceed:
#required by gnome-base/gvfs-1.12.3-r1[udisks], required by xfce-base/thunar-1.4.0[dbus,xfce_plugins_trash], required by xfce-base/xfdesktop-4.10.0[thunar], required by xfce-base/xfce4-meta-4.10, required by xfce4-meta (argument)
# /usr/portage/profiles/package.mask/funtoo-cautionary:
# Martin Scholz (03 Jul 2012)
# masking polkit and udisks responsible for build failings
=sys-fs/udisks-1.99.0-r1

NOTE: The --autounmask-keep-masks option will prevent emerge
      from creating package.unmask or ** keyword changes.

Use --autounmask-write to write changes to config files (honoring CONFIG_PROTECT).

emerge: there are no ebuilds to satisfy ">=sys-fs/udev-180[gudev,hwdb]".
(dependency required by "sys-fs/udisks-1.99.0-r1" [ebuild])
(dependency required by "gnome-base/gvfs-1.12.3-r1[udisks]" [ebuild])
(dependency required by "xfce-base/thunar-1.4.0[dbus,xfce_plugins_trash]" [ebuild])
(dependency required by "xfce-base/xfdesktop-4.10.0[thunar]" [ebuild])
(dependency required by "xfce-base/xfce4-meta-4.10" [ebuild])
(dependency required by "xfce4-meta" [argument])
(chroot) unknown001bb9b49eba / #  nano -w /etc/make.conf
(chroot) unknown001bb9b49eba / #  nano -w /etc/make.conf
(chroot) unknown001bb9b49eba / #  emerge xfce4-meta
Calculating dependencies... done!

The following mask changes are necessary to proceed:
#required by gnome-base/gvfs-1.12.3-r1[udisks], required by xfce-base/thunar-1.4.0[dbus,xfce_plugins_trash], required by xfce-base/xfdesktop-4.10.0[thunar], required by xfce-base/xfce4-meta-4.10, required by xfce4-meta (argument)
# /usr/portage/profiles/package.mask/funtoo-cautionary:
# Martin Scholz (03 Jul 2012)
# masking polkit and udisks responsible for build failings
=sys-fs/udisks-1.99.0-r1

NOTE: The --autounmask-keep-masks option will prevent emerge
      from creating package.unmask or ** keyword changes.

Use --autounmask-write to write changes to config files (honoring CONFIG_PROTECT).

emerge: there are no ebuilds to satisfy ">=sys-fs/udev-180[gudev,hwdb]".
(dependency required by "sys-fs/udisks-1.99.0-r1" [ebuild])
(dependency required by "gnome-base/gvfs-1.12.3-r1[udisks]" [ebuild])
(dependency required by "xfce-base/thunar-1.4.0[dbus,xfce_plugins_trash]" [ebuild])
(dependency required by "xfce-base/xfdesktop-4.10.0[thunar]" [ebuild])
(dependency required by "xfce-base/xfce4-meta-4.10" [ebuild])
(dependency required by "xfce4-meta" [argument])

After autounmask, says as below

 emerge xfce4-meta --autounmask-write
Calculating dependencies... done!

The following mask changes are necessary to proceed:
#required by gnome-base/gvfs-1.12.3-r1[udisks], required by xfce-base/thunar-1.4.0[dbus,xfce_plugins_trash], required by xfce-base/xfdesktop-4.10.0[thunar], required by xfce-base/xfce4-meta-4.10, required by xfce4-meta (argument)
# /usr/portage/profiles/package.mask/funtoo-cautionary:
# Martin Scholz (03 Jul 2012)
# masking polkit and udisks responsible for build failings
=sys-fs/udisks-1.99.0-r1

NOTE: The --autounmask-keep-masks option will prevent emerge
      from creating package.unmask or ** keyword changes.

Autounmask changes successfully written. Remember to run dispatch-conf.

emerge: there are no ebuilds to satisfy ">=sys-fs/udev-180[gudev,hwdb]".
(dependency required by "sys-fs/udisks-1.99.0-r1" [ebuild])
(dependency required by "gnome-base/gvfs-1.12.3-r1[udisks]" [ebuild])
(dependency required by "xfce-base/thunar-1.4.0[dbus,xfce_plugins_trash]" [ebuild])
(dependency required by "xfce-base/xfdesktop-4.10.0[thunar]" [ebuild])
(dependency required by "xfce-base/xfce4-meta-4.10" [ebuild])
(dependency required by "xfce4-meta" [argument])
(chroot) unknown001bb9b49eba / # dispatch-conf

--- /etc/portage/package.unmask 1970-01-01 05:30:00.000000000 +0530
+++ /etc/portage/._cfg0000_package.unmask       2012-10-02 15:31:10.637995362 +0530
@@ -0,0 +1,5 @@
+#required by gnome-base/gvfs-1.12.3-r1[udisks], required by xfce-base/thunar-1.4.0[dbus,xfce_plugins_trash], required by xfce-base/xfdesktop-4.10.0[thunar], required by xfce-base/xfce4-meta-4.10, required by xfce4-meta (argument)
+# /usr/portage/profiles/package.mask/funtoo-cautionary:
+# Martin Scholz (03 Jul 2012)
+# masking polkit and udisks responsible for build failings
+=sys-fs/udisks-1.99.0-r1

>> (1 of 1) -- /etc/portage/package.unmask
>> q quit, h help, n next, e edit-new, z zap-new, u use-new
   m merge, t toggle-merge, l look-merge:

I selected use new
Now, pl. see below

emerge xfce4-meta
Calculating dependencies... done!

emerge: there are no ebuilds to satisfy ">=sys-fs/udev-180[gudev,hwdb]".
(dependency required by "sys-fs/udisks-1.99.0-r1" [ebuild])
(dependency required by "gnome-base/gvfs-1.12.3-r1[udisks]" [ebuild])
(dependency required by "xfce-base/thunar-1.4.0[dbus,xfce_plugins_trash]" [ebuild])
(dependency required by "xfce-base/xfdesktop-4.10.0[thunar]" [ebuild])
(dependency required by "xfce-base/xfce4-meta-4.10" [ebuild])
(dependency required by "xfce4-meta" [argument])

Pl. guide

Last edited by san2ban (2012-10-04 14:14:37)

Azerthoth · 2012-10-02 04:43:51

http://forums.funtoo.org/viewtopic.php?id=1522
http://forums.funtoo.org/viewtopic.php?id=1609
http://forums.funtoo.org/viewtopic.php?id=1603
http://forums.funtoo.org/viewtopic.php?id=1602

san2ban · 2012-10-02 05:02:44

If I use LXDE, instead of xfce4, will there be this same issue, or LXDE is free from such problems?

angry_vincent · 2012-10-02 05:42:43

this is not xfce4 itself but a package that require udev, mainly udisks. Last one i have no clue why anyone need it, it just a layer above udev (a crappy HAL successor)

san2ban · 2012-10-02 10:22:59

I emerged xfce4 with USE = -udev, -udisks. Now, when I emerge -auDN world, see the out put below

 (chroot) unknown001bb9b49eba ~ # emerge -auDN world

These are the packages that would be merged, in order:

Calculating dependencies... done!

!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:

gnome-base/gvfs:0

  (gnome-base/gvfs-1.10.1::gentoo, ebuild scheduled for merge) pulled in by
    (no parents that aren't satisfied by other packages in this slot)

  (gnome-base/gvfs-1.14.0::gentoo, ebuild scheduled for merge) pulled in by
    >=gnome-base/gvfs-1.10.1[udisks,udev] required by (xfce-base/thunar-1.4.0::gentoo, ebuild scheduled for merge)

dev-libs/glib:2

  (dev-libs/glib-2.32.4-r1::gentoo, installed) pulled in by
    (no parents that aren't satisfied by other packages in this slot)

  (dev-libs/glib-2.34.0::gentoo, ebuild scheduled for merge) pulled in by
    >=dev-libs/glib-2.33.12:2 required by (gnome-base/gvfs-1.14.0::gentoo, ebuild scheduled for merge)


It may be possible to solve this problem by using package.mask to
prevent one of those packages from being selected. However, it is also
possible that conflicting dependencies exist such that they are
impossible to satisfy simultaneously.  If such a conflict exists in
the dependencies of two different packages, then those packages can
not be installed simultaneously. You may want to try a larger value of
the --backtrack option, such as --backtrack=30, in order to see if
that will solve this conflict automatically.

For more information, see MASKED PACKAGES section in the emerge man
page or refer to the Gentoo Handbook.


The following mask changes are necessary to proceed:
#required by xfce-base/thunar-1.4.0[udev], required by xfce-base/xfdesktop-4.10.0[thunar], required by xfce-base/xfce4-meta-4.10, required by @selected, required by @world (argument)
# /usr/portage/profiles/package.mask/gentoo:
# Alexandre Rostovtsev <tetromino@gentoo.org> (25 Sep 2012)
# GNOME 3.6 mask
# Core libraries to be unmasked first:
=gnome-base/gvfs-1.14.0
#required by gnome-base/gvfs-1.14.0, required by xfce-base/thunar-1.4.0[udev], required by xfce-base/xfdesktop-4.10.0[thunar], required by xfce-base/xfce4-meta-4.10, required by @selected, required by @world (argument)
# /usr/portage/profiles/package.mask/gentoo:
# Alexandre Rostovtsev <tetromino@gentoo.org> (25 Sep 2012)
# GNOME 3.6 mask
# Core libraries to be unmasked first:
=dev-libs/glib-2.34.0

NOTE: The --autounmask-keep-masks option will prevent emerge
      from creating package.unmask or ** keyword changes.

Use --autounmask-write to write changes to config files (honoring CONFIG_PROTECT).

emerge: there are no ebuilds to satisfy ">=sys-fs/udev-180[gudev,hwdb]".
(dependency required by "sys-fs/udisks-1.99.0-r1" [ebuild])
(dependency required by "gnome-base/gvfs-1.14.0[udisks]" [ebuild])
(dependency required by "xfce-base/thunar-1.4.0[udev]" [ebuild])
(dependency required by "xfce-base/xfdesktop-4.10.0[thunar]" [installed])
(dependency required by "xfce-base/xfce4-meta-4.10" [installed])
(dependency required by "@selected" [set])
(dependency required by "@world" [argument])

Does this mean I cant emerge -auDN world anymore?
Or, every time should I use USE = -udev, -udisks?
Pl. clarify

angry_vincent · 2012-10-02 11:53:00

there is a package.use way, you can find it in portage man page.

san2ban · 2012-10-02 13:18:04

since udev is not there, xorg is not configuring properly. My hardware is are not detected properly
Unable to startx. Pl. guide

angry_vincent · 2012-10-02 16:09:34

can you be more specific?

imaginasys · 2012-10-02 21:01:24

You need a too recent version of udev for Funtoo...

(funtoo) r2d2 / # eix sys-fs/udev
[i] sys-fs/udev
     Available versions:  146-r4 160-r2 160-r3 (~)171-r2 (~)171-r3 (~)171-r5 171-r6 171-r7 [M](**)177 [M](**)177-r1 {{extras +gudev +hwdb (-)introspection selinux}}
     Installed versions:  171-r7(20:18:57 2012-09-22)(extras gudev hwdb -introspection -selinux)
     Homepage:            http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev.html
     Description:         Linux dynamic and persistent device naming support (aka userspace devfs)

Whenever you see this message ">=sys-fs/udev-180[gudev,hwdb]" it indicates your are blocked from using funtoo. You should use Gentoo if you want a real desktop with recent stuff ...
My hearth bleed when I say this, but it's the cold thruth. We, the desktop users, are getting dumped from using Funtoo with anything recent even if it's in Gentoo but using systemd or anything oriented for the big desktops (Gnome, KDE, XFCE).

Unless you want a server, you should not use Funtoo anymore... Sorry!

Regards,
Bernard

san2ban · 2012-10-03 03:01:44

Gentleman
I have quit archlinux, for the same systemd and udev being merged with systemd, and come to funtoo. Why should I go to Gentoo?
Is there no other way out?
Daniel, vincent, do not leave us out in the cold

Last edited by san2ban (2012-10-03 03:04:07)

angry_vincent · 2012-10-03 04:08:06

there is a clear statement about systemd, it will not be in funtoo in any distant future, those talks just wasting our time. about udev, in gentoo 171-r6 is latest stable version, no problems with it. If you want a desktop related to that verison of udev, just switch to stable desktop packages. portage is very flexible, if you want by-pass funtoo restriction, use local overlay, but, please, do not distrub people, do not mislead and piss off Funtoo development because "my fancy gadget" require new udev. A humble request to quebec community, do not stir up the troubles.

san2ban · 2012-10-03 04:20:47

Angry_Vincent

I will be grateful, if somebody shows me a work-around. I have spent more than 50hours in front of my machine, trying all sort of things, mask, unmask, ....

I do not have any fancy gadgets, all I need is to install XFCE and start using the system. As I said, startx itself not working. I cant show what it says from a live CD, since start X will not be possible from sysrescueCD.
Neither do I need systemd.
I do not want a particular udev, something that will allow me to log in to a desktop
(LXDE also throwing up similar messages)

Juippisi · 2012-10-03 09:34:45

angry_vincent wrote:

there is a clear statement about systemd, it will not be in funtoo in any distant future

http://forums.gentoo.org/viewtopic-t-93 … art-0.html

"If systemd becomes a prerequsite for GNOME, its time to drop GNOME."

angry_vincent wrote:

portage is very flexible, if you want by-pass funtoo restriction, use local overlay, but, please, do not distrub people, do not mislead and piss off Funtoo development because "my fancy gadget" require new udev. A humble request to quebec community, do not stir up the troubles.

This is no ego-boost nor do I want attention, just wanting to show everyone an example what you mean vincent:

joonas@cherry ~ $ /usr/lib/systemd/systemd-udevd --version
193
joonas@cherry ~ $ emerge --info |head -n1
Portage 2.3.4-r9 (funtoo/1.0/linux-gnu/arch/x86-64bit, gcc-4.6.2, glibc-2.13-r4, 3.6.0-rc6 x86_64)

As said before, it's not supported by any Funtoo dev and switching to newer udev could potentially break your system to un-bootable state, but for me it was newer udev or go to Gentoo so I had nothing to lose. Overall porting few ebuilds to Funtoo, switching from module-init-tools to kmod and editing linux-mod.eclass was easier than a fresh Gentoo install. Although users should never be required to make these changes, it's possible. Just remember that your system becomes unsupported, and you might face new blocks to solve in a near future before Funtoo catches up on udev version. If you have no idea what you're doing, don't do anything and switch to Gentoo if you want latest desktop.

drobbins · 2012-10-03 18:09:21

We are currently looking at reducing the dependency on udev in Funtoo. Once this happens, we should be able to use upstream udev, or at least keep udev current. Right now, udev is problematic - it is a core package, but it requires frequent updates for GNOME and other desktop stuff. This is an architectural problem, as the core should not require frequent updates to support desktop efforts (they should be isolated from one another.) We can't just go along and bump udev because we need to maintain stability for server systems.

The solution we are looking at is making udev optional. udev will not be required for booting Funtoo. Then people can upgrade udev without impacting critical functionality of their system. It will be relegated to a desktop support package, and many people will be able to run Funtoo without udev. I view this as an optimal approach.

Until we get this implemented (2-3 weeks?) some desktop stuff will be a bit tricky to deal with. Once it's done, this should all go smoothly, and the core system will be independent from desktop dependencies.

san2ban · 2012-10-04 02:39:01

Thank You Daniel. I will wait. My respect for you has increased by leaps and bounds.
Thanks again. ( I am only a new convert from ArchLinux, do not think of me as the root cause of these issues)

#1 2012-10-02 04:39:16

[solved] there are no ebuilds to satisfy ">=sys-fs/udev-18

#2 2012-10-02 04:43:51

Re: [solved] there are no ebuilds to satisfy ">=sys-fs/udev-18

#3 2012-10-02 05:02:44

Re: [solved] there are no ebuilds to satisfy ">=sys-fs/udev-18

#4 2012-10-02 05:42:43

Re: [solved] there are no ebuilds to satisfy ">=sys-fs/udev-18

#5 2012-10-02 10:22:59

Re: [solved] there are no ebuilds to satisfy ">=sys-fs/udev-18

#6 2012-10-02 11:53:00

Re: [solved] there are no ebuilds to satisfy ">=sys-fs/udev-18

#7 2012-10-02 13:18:04

Re: [solved] there are no ebuilds to satisfy ">=sys-fs/udev-18

#8 2012-10-02 16:09:34

Re: [solved] there are no ebuilds to satisfy ">=sys-fs/udev-18

#9 2012-10-02 21:01:24

Re: [solved] there are no ebuilds to satisfy ">=sys-fs/udev-18

#10 2012-10-03 03:01:44

Re: [solved] there are no ebuilds to satisfy ">=sys-fs/udev-18

#11 2012-10-03 04:08:06

Re: [solved] there are no ebuilds to satisfy ">=sys-fs/udev-18

#12 2012-10-03 04:20:47

Re: [solved] there are no ebuilds to satisfy ">=sys-fs/udev-18

#13 2012-10-03 09:34:45

Re: [solved] there are no ebuilds to satisfy ">=sys-fs/udev-18

#14 2012-10-03 18:09:21

Re: [solved] there are no ebuilds to satisfy ">=sys-fs/udev-18

#15 2012-10-04 02:39:01

Re: [solved] there are no ebuilds to satisfy ">=sys-fs/udev-18

Board footer