Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
conflict openrc udev
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3  Next  
Reply to topic    Gentoo Forums Forum Index Portage & Programming
View previous topic :: View next topic  
Author Message
jrussia
Tux's lil' helper
Tux's lil' helper


Joined: 29 Aug 2012
Posts: 89
Location: Chicago

PostPosted: Tue Oct 09, 2012 7:33 pm    Post subject: Reply with quote

Sorry, I don't think there is a concise guide on the effects of different profiles. All of the information is in /usr/portage/profiles

emerge --info will tell you what use flags you are using
emerge -pv or emerge -av will let you look at and think about what the system wants to do
Any package that requires you to update your package files with etc-update that need "~amd64", and you are not using "~amd64" for everything, poses a potential problem.
Back to top
View user's profile Send private message
wcg
Guru
Guru


Joined: 06 Jan 2009
Posts: 588

PostPosted: Tue Oct 09, 2012 9:14 pm    Post subject: Reply with quote

Where I put ">=udev171-r6", substitute ">=udev181". (Anthing that
requires udev but can be satisfied with "=udev171-r6", meaning
that version of udev is new enough, is not a problem. Packages that
require udev181 or newer or that require udev-init-scripts are the problem.)

I do not think your emerge output is a profile problem. I use that same
no-multilib profile, it works fine. I think your problems start from
packages depending on newer udev versions and udev-init-scripts,
which have dependencies that cannot be satisfied by packages
in the stable set.
_________________
TIA
Back to top
View user's profile Send private message
ev56o
Tux's lil' helper
Tux's lil' helper


Joined: 26 Jan 2010
Posts: 146

PostPosted: Wed Oct 10, 2012 10:03 am    Post subject: Reply with quote

do i have to make work more versions of the same package finally?
I like to have a more simple setup, i like to have only stable package, is there a system profile that make this?
On alternative what i have to do now in your opinion for continue with this profile?
Back to top
View user's profile Send private message
galanom
n00b
n00b


Joined: 24 Oct 2011
Posts: 25

PostPosted: Wed Oct 10, 2012 11:05 am    Post subject: Reply with quote

ev56o wrote:
do i have to make work more versions of the same package finally?
I like to have a more simple setup, i like to have only stable package, is there a system profile that make this?
On alternative what i have to do now in your opinion for continue with this profile?


Not for udev or openrc. Multiple versions (slots) are available usually for libraries.
In order to have only tested versions, remove entires you have put in /etc/portage/package.keywords
Back to top
View user's profile Send private message
steveL
Advocate
Advocate


Joined: 13 Sep 2006
Posts: 2164
Location: The Peanut Gallery

PostPosted: Wed Oct 10, 2012 12:52 pm    Post subject: Reply with quote

If you're downgrading to stable udev (a wise move) make sure you run revdep-rebuild immediately afterwards.
Back to top
View user's profile Send private message
Scimmia22
n00b
n00b


Joined: 24 Sep 2012
Posts: 10

PostPosted: Wed Oct 10, 2012 9:36 pm    Post subject: Reply with quote

ev56o wrote:
do i have to make work more versions of the same package finally?
I like to have a more simple setup, i like to have only stable package, is there a system profile that make this?
On alternative what i have to do now in your opinion for continue with this profile?


Your profile didn't get you packages from testing. Look at make.conf, package.use, package.accept_keyword, etc. Anywhere you have a "~", this means that you told portage that you wanted packages from testing. Depending on what you've done, downgrading could be a difficult experience, but you start by getting rid of those keywords and downgrading packages one by one.
Back to top
View user's profile Send private message
ev56o
Tux's lil' helper
Tux's lil' helper


Joined: 26 Jan 2010
Posts: 146

PostPosted: Thu Oct 11, 2012 9:49 am    Post subject: Reply with quote

Ok, finally i understand the source of the problem: i made (with no conscience) a test system with packet very early, slotted and a lot of trouble. Now let' s go to a more stable system and for this i have to make a downgrade.
Do i have to procede with eliminate package.keywords? Later i have to perform a gradual downgrade, do you advice start from low level packet to high level or reverse?
Back to top
View user's profile Send private message
steveL
Advocate
Advocate


Joined: 13 Sep 2006
Posts: 2164
Location: The Peanut Gallery

PostPosted: Thu Oct 11, 2012 3:30 pm    Post subject: Reply with quote

ev56o wrote:
Ok, finally i understand the source of the problem: i made (with no conscience) a test system with packet very early, slotted and a lot of trouble. Now let' s go to a more stable system and for this i have to make a downgrade.

Good, you've got what's going on now.
Quote:
Do i have to procede with eliminate package.keywords?

Yes, most especially for low-level stuff. Bear in mind anything listed in that file will be unstable. If you're not happy to deal with bugs in a package, don't keyword it.

By "deal with" I mean you're prepared to look at and patch the source, and/or you're not worried if it suddenly breaks and you have to pick up the pieces.
Quote:
Later i have to perform a gradual downgrade, do you advice start from low level packet to high level or reverse?

Low-level, with lots of revdep-rebuild checks in between. If those trigger lots of high-level unstable packages (portage shows you those in the emerge -pv output as yellow ~) then take those out of keywords as well, and let them be rebuilt stable.

The best tip is to do this from a terminal, with no X running. So run:
Code:
rc-update del xdm

..and reboot before you start. (Make sure you're comfortable with your editor ($EDITOR) in that environment before you do anything.) A live disk is always useful in case something goes majorly wrong.
Back to top
View user's profile Send private message
ev56o
Tux's lil' helper
Tux's lil' helper


Joined: 26 Jan 2010
Posts: 146

PostPosted: Sat Oct 13, 2012 12:47 pm    Post subject: Reply with quote

I removed package.keywords and revdep show no break.
This is the situation and i can' t go on
Code:

ubuntu / # emerge -qDuNa world
[ebuild  N    ] sys-apps/module-init-tools-3.16-r1
[ebuild  NS   ] sys-fs/udisks-1.0.4-r2 [1.99.0-r1]
[ebuild  N    ] gnome-base/gvfs-1.12.3
[ebuild     U ] sys-fs/udev-194 [171-r6]
[ebuild  N    ] sys-fs/udev-init-scripts-16
[ebuild  N    ] gnome-base/gvfs-1.12.3-r1
[blocks B     ] <sys-fs/udev-186 ("<sys-fs/udev-186" is blocking sys-fs/udev-init-scripts-16)
[blocks B     ] sys-apps/kmod ("sys-apps/kmod" is blocking sys-apps/module-init-tools-3.16-r1)
[blocks B     ] sys-apps/module-init-tools ("sys-apps/module-init-tools" is blocking sys-apps/kmod-10)

!!! 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.12.3::gentoo, ebuild scheduled for merge) pulled in by
    (no parents that aren't satisfied by other packages in this slot)

  (gnome-base/gvfs-1.12.3-r1::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, installed)

sys-fs/udev:0

  (sys-fs/udev-171-r6::gentoo, installed) pulled in by
    (no parents that aren't satisfied by other packages in this slot)

  (sys-fs/udev-194::gentoo, ebuild scheduled for merge) pulled in by
    >=sys-fs/udev-187 required by (sys-fs/udev-init-scripts-16::gentoo, ebuild scheduled for merge)
    (and 1 more with the same problem)



The following keyword changes are necessary to proceed:
#required by sys-fs/udev-init-scripts-16
=sys-fs/udev-194 ~amd64
#required by xfce-base/thunar-1.4.0[dbus,xfce_plugins_trash], required by xfce-extra/thunar-volman-0.8.0, required by @selected, required by @world (argument)
=gnome-base/gvfs-1.12.3-r1 ~amd64
#required by sys-fs/udev-194[openrc], required by sys-fs/udisks-1.99.0-r1, 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-extra/thunar-volman-0.8.0, required by @selected, required by @world (argument)
=sys-fs/udev-init-scripts-16 ~amd64

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

why it ask for three versions of udev? Is it normal?
Back to top
View user's profile Send private message
DaggyStyle
Advocate
Advocate


Joined: 22 Mar 2006
Posts: 4895

PostPosted: Sat Oct 13, 2012 3:07 pm    Post subject: Reply with quote

ev56o wrote:
I removed package.keywords and revdep show no break.
This is the situation and i can' t go on
Code:

ubuntu / # emerge -qDuNa world
[ebuild  N    ] sys-apps/module-init-tools-3.16-r1
[ebuild  NS   ] sys-fs/udisks-1.0.4-r2 [1.99.0-r1]
[ebuild  N    ] gnome-base/gvfs-1.12.3
[ebuild     U ] sys-fs/udev-194 [171-r6]
[ebuild  N    ] sys-fs/udev-init-scripts-16
[ebuild  N    ] gnome-base/gvfs-1.12.3-r1
[blocks B     ] <sys-fs/udev-186 ("<sys-fs/udev-186" is blocking sys-fs/udev-init-scripts-16)
[blocks B     ] sys-apps/kmod ("sys-apps/kmod" is blocking sys-apps/module-init-tools-3.16-r1)
[blocks B     ] sys-apps/module-init-tools ("sys-apps/module-init-tools" is blocking sys-apps/kmod-10)

!!! 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.12.3::gentoo, ebuild scheduled for merge) pulled in by
    (no parents that aren't satisfied by other packages in this slot)

  (gnome-base/gvfs-1.12.3-r1::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, installed)

sys-fs/udev:0

  (sys-fs/udev-171-r6::gentoo, installed) pulled in by
    (no parents that aren't satisfied by other packages in this slot)

  (sys-fs/udev-194::gentoo, ebuild scheduled for merge) pulled in by
    >=sys-fs/udev-187 required by (sys-fs/udev-init-scripts-16::gentoo, ebuild scheduled for merge)
    (and 1 more with the same problem)



The following keyword changes are necessary to proceed:
#required by sys-fs/udev-init-scripts-16
=sys-fs/udev-194 ~amd64
#required by xfce-base/thunar-1.4.0[dbus,xfce_plugins_trash], required by xfce-extra/thunar-volman-0.8.0, required by @selected, required by @world (argument)
=gnome-base/gvfs-1.12.3-r1 ~amd64
#required by sys-fs/udev-194[openrc], required by sys-fs/udisks-1.99.0-r1, 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-extra/thunar-volman-0.8.0, required by @selected, required by @world (argument)
=sys-fs/udev-init-scripts-16 ~amd64

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

why it ask for three versions of udev? Is it normal?


read the output, you need to unmask sys-fs/udev-init-scripts-16, sys-fs/udev-194 and gnome-base/gvfs-1.12.3-r1.
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein
ProjectFootball
Back to top
View user's profile Send private message
Scimmia22
n00b
n00b


Joined: 24 Sep 2012
Posts: 10

PostPosted: Sat Oct 13, 2012 9:30 pm    Post subject: Reply with quote

DaggyStyle, he's trying to get back to a "stable" release instead of the mixed stable/testing he had and there's nothing in that list that would REQUIRE the new versions.

First off, it sound like you have kmod installed? Kmod is not in the stable branch, unmerge it. As for the others, someone with more experience downgrading may need to help. Maybe you need to rebuild XFCE against the older packages?
Back to top
View user's profile Send private message
DaggyStyle
Advocate
Advocate


Joined: 22 Mar 2006
Posts: 4895

PostPosted: Sun Oct 14, 2012 6:06 am    Post subject: Reply with quote

Scimmia22 wrote:
DaggyStyle, he's trying to get back to a "stable" release instead of the mixed stable/testing he had and there's nothing in that list that would REQUIRE the new versions.

First off, it sound like you have kmod installed? Kmod is not in the stable branch, unmerge it. As for the others, someone with more experience downgrading may need to help. Maybe you need to rebuild XFCE against the older packages?


I see, in this case he didn't removed all traces of keyworded packages.
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein
ProjectFootball
Back to top
View user's profile Send private message
ev56o
Tux's lil' helper
Tux's lil' helper


Joined: 26 Jan 2010
Posts: 146

PostPosted: Sun Oct 14, 2012 12:59 pm    Post subject: Reply with quote

I unmerged kmod and the situation is the same.
Have you evere considerated the use flag question on kmod, udev, openrc and more?
Code:

localhost m # emerge -qDuNa world
[ebuild  N    ] sys-apps/module-init-tools-3.16-r1
[ebuild  NS   ] sys-fs/udisks-1.0.4-r2 [1.99.0-r1]
[ebuild  N    ] gnome-base/gvfs-1.12.3
[ebuild     U ] sys-fs/udev-194 [171-r6]
[ebuild  N    ] sys-fs/udev-init-scripts-16
[ebuild  N    ] gnome-base/gvfs-1.12.3-r1
[blocks B     ] <sys-fs/udev-186 ("<sys-fs/udev-186" is blocking sys-fs/udev-init-scripts-16)
[blocks B     ] sys-apps/kmod ("sys-apps/kmod" is blocking sys-apps/module-init-tools-3.16-r1)
[blocks B     ] sys-apps/module-init-tools ("sys-apps/module-init-tools" is blocking sys-apps/kmod-10)

!!! 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.12.3::gentoo, ebuild scheduled for merge) pulled in by
    (no parents that aren't satisfied by other packages in this slot)

  (gnome-base/gvfs-1.12.3-r1::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, installed)

sys-fs/udev:0

  (sys-fs/udev-171-r6::gentoo, installed) pulled in by
    (no parents that aren't satisfied by other packages in this slot)

  (sys-fs/udev-194::gentoo, ebuild scheduled for merge) pulled in by
    >=sys-fs/udev-187 required by (sys-fs/udev-init-scripts-16::gentoo, ebuild scheduled for merge)
    (and 1 more with the same problem)



The following keyword changes are necessary to proceed:
#required by sys-fs/udev-init-scripts-16
=sys-fs/udev-194 ~amd64
#required by xfce-base/thunar-1.4.0[dbus,xfce_plugins_trash], required by xfce-extra/thunar-volman-0.8.0, required by @selected, required by @world (argument)
=gnome-base/gvfs-1.12.3-r1 ~amd64
#required by sys-fs/udev-194[openrc], required by sys-fs/udisks-1.99.0-r1, 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-extra/thunar-volman-0.8.0, required by @selected, required by @world (argument)
=sys-fs/udev-init-scripts-16 ~amd64

Use --autounmask-write to write changes to config files (honoring CONFIG_PROTECT).
localhost m # emerge --unmerge sys-apps/kmod
 * This action can remove important packages! In order to be safer, use
 * `emerge -pv --depclean <atom>` to check for reverse dependencies before
 * removing packages.


!!! 'sys-apps/kmod' (virtual/modutils) is part of your system profile.
!!! Unmerging it may be damaging to your system.

>>> Waiting 10 seconds before starting...
>>> (Control-C to abort)...
Press Ctrl-C to Stop in:  10 9 8 7 6 5 4 3 2 1

 sys-apps/kmod
    selected: 10
   protected: none
     omitted: none

All selected packages: sys-apps/kmod-10

>>> 'Selected' packages are slated for removal.
>>> 'Protected' and 'omitted' packages will not be removed.

>>> Waiting 5 seconds before starting...
>>> (Control-C to abort)...
>>> Unmerging in:  5 4 3 2 1
>>> Unmerging (1 of 1) sys-apps/kmod-10...

 * GNU info directory index is up-to-date.
localhost m # revdep-rebuild -ip
 * Configuring search environment for revdep-rebuild

 * Checking reverse dependencies
 * Packages containing binaries and libraries broken by a package update
 * will be emerged.

 * Collecting system binaries and libraries
 * Generated new 1_files.rr
 * Collecting complete LD_LIBRARY_PATH
 * Generated new 2_ldpath.rr
 * Checking dynamic linking consistency
[ 100% ]                 

 * Dynamic linking on your system is consistent... All done.
localhost m # emerge --depclean

 * Depclean may break link level dependencies. Thus, it is
 * recommended to use a tool such as `revdep-rebuild` (from
 * app-portage/gentoolkit) in order to detect such breakage.
 *
 * Always study the list of packages to be cleaned for any obvious
 * mistakes. Packages that are part of the world set will always
 * be kept.  They can be manually added to this set with
 * `emerge --noreplace <atom>`.  Packages that are listed in
 * package.provided (see portage(5)) will be removed by
 * depclean, even if they are part of the world set.
 *
 * As a safety measure, depclean will not remove any packages
 * unless *all* required dependencies have been resolved.  As a
 * consequence, it is often necessary to run `emerge --update
 * --newuse --deep @world` prior to depclean.

Calculating dependencies... done!
 * Dependencies could not be completely resolved due to
 * the following required packages not being installed:
 *
 *   >=gnome-base/gvfs-1.10.1[udisks,udev] pulled in by:
 *     xfce-base/thunar-1.4.0
 *
 *   >=gnome-base/gvfs-1.10.1 pulled in by:
 *     xfce-base/thunar-1.4.0
 *
 *   sys-apps/kmod[tools] pulled in by:
 *     virtual/modutils-0
 *
 *   sys-fs/udisks:0 pulled in by:
 *     kde-base/kdelibs-4.8.5
 *
 * Have you forgotten to do a complete update prior to depclean? The
 * most comprehensive command for this purpose is as follows:
 *
 *   emerge --update --newuse --deep --with-bdeps=y @world
 *
 * Note that the --with-bdeps=y option is not required in many
 * situations. Refer to the emerge manual page (run `man emerge`)
 * for more information about --with-bdeps.
 *
 * Also, note that it may be necessary to manually uninstall
 * packages that no longer exist in the portage tree, since it may
 * not be possible to satisfy their dependencies.
localhost m # emerge --update --newuse --deep --with-bdeps=y @world
Calculating dependencies... done!
[ebuild  N     ] sys-apps/module-init-tools-3.16-r1  USE="-static"
[ebuild     U  ] dev-lang/nasm-2.10.01 [2.10]
[ebuild  N     ] perl-core/version-0.940.0
[ebuild  N     ] perl-core/Test-Harness-3.230.0
[ebuild  N     ] perl-core/Perl-OSType-1.2.0  USE="-test"
[ebuild  N     ] perl-core/JSON-PP-2.272.0
[ebuild  N     ] perl-core/CPAN-Meta-YAML-0.4.0
[ebuild  N     ] perl-core/Scalar-List-Utils-1.230.0
[ebuild  N     ] perl-core/ExtUtils-Manifest-1.580.0
[ebuild  N     ] perl-core/ExtUtils-Install-1.54
[ebuild  N     ] perl-core/ExtUtils-Command-1.170.0
[ebuild  N     ] perl-core/Test-Simple-0.980.0
[ebuild  N     ] perl-core/IO-1.25
[ebuild  N     ] virtual/perl-File-Temp-0.220.0-r2
[ebuild  N     ] virtual/perl-version-0.940.0
[ebuild  N     ] virtual/perl-JSON-PP-2.272.0-r1
[ebuild  N     ] virtual/perl-CPAN-Meta-YAML-0.4.0
[ebuild  N     ] virtual/perl-Scalar-List-Utils-1.230.0-r2
[ebuild     U  ] virtual/perl-Test-Harness-3.230.0-r3 [3.17]
[ebuild  N     ] virtual/perl-Perl-OSType-1.2.0-r1
[ebuild  N     ] virtual/perl-ExtUtils-Manifest-1.580.0-r1
[ebuild  N     ] virtual/perl-ExtUtils-Install-1.54
[ebuild  N     ] virtual/perl-ExtUtils-Command-1.170.0-r3
[ebuild  N     ] virtual/perl-Test-Simple-0.980.0-r2
[ebuild  N     ] virtual/perl-IO-1.25
[ebuild  N     ] perl-core/Module-Metadata-1.0.6
[ebuild  N     ] perl-core/Parse-CPAN-Meta-1.440.100
[ebuild  N     ] perl-core/Version-Requirements-0.101.20
[ebuild  N    ~] sys-apps/kmod-10  USE="tools zlib -debug -doc -lzma -static-libs"
[ebuild  N     ] virtual/perl-Parse-CPAN-Meta-1.440.100-r2
[ebuild  N     ] virtual/perl-Module-Metadata-1.0.6
[ebuild  N     ] virtual/perl-Version-Requirements-0.101.20-r2
[ebuild     U  ] dev-util/cmake-2.8.9 [2.8.8-r3]
[ebuild  NS    ] sys-fs/udisks-1.0.4-r2 [1.99.0-r1] USE="nls -debug -remote-access"
[ebuild  N     ] gnome-base/gvfs-1.12.3  USE="archive cdda fuse http udev -afp -avahi -bluetooth -bluray -doc -gdu -gnome-keyring -gphoto2 -ios -samba (-udisks)"
[ebuild  N     ] perl-core/ExtUtils-MakeMaker-6.620.0
[ebuild  N     ] virtual/perl-ExtUtils-MakeMaker-6.620.0
[ebuild  N     ] perl-core/CPAN-Meta-2.112.621
[ebuild  N     ] virtual/perl-CPAN-Meta-2.112.621
[ebuild     U  ] perl-core/Module-Build-0.380.0 [0.36.07]
[ebuild     U  ] virtual/perl-Module-Build-0.380.0-r2 [0.36.07]
[ebuild     U ~] sys-fs/udev-194 [171-r6] USE="openrc%* -acl% -doc% -static-libs%"
[ebuild  N    ~] sys-fs/udev-init-scripts-16
[ebuild  N    ~] gnome-base/gvfs-1.12.3-r1  USE="archive cdda fuse http udev udisks -afp -avahi -bluetooth -bluray -doc -gdu -gnome-keyring -gphoto2 -ios -samba"
[blocks B      ] <sys-fs/udev-186 ("<sys-fs/udev-186" is blocking sys-fs/udev-init-scripts-16)
[blocks B      ] sys-apps/kmod ("sys-apps/kmod" is blocking sys-apps/module-init-tools-3.16-r1)
[blocks B      ] sys-apps/module-init-tools ("sys-apps/module-init-tools" is blocking sys-apps/kmod-10)

!!! 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.12.3::gentoo, ebuild scheduled for merge) pulled in by
    (no parents that aren't satisfied by other packages in this slot)

  (gnome-base/gvfs-1.12.3-r1::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, installed)

sys-fs/udev:0

  (sys-fs/udev-171-r6::gentoo, installed) pulled in by
    (no parents that aren't satisfied by other packages in this slot)

  (sys-fs/udev-194::gentoo, ebuild scheduled for merge) pulled in by
    >=sys-fs/udev-187 required by (sys-fs/udev-init-scripts-16::gentoo, ebuild scheduled for merge)
    (and 1 more with the same problem)


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.

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


The following keyword changes are necessary to proceed:
#required by sys-fs/udev-init-scripts-16
=sys-fs/udev-194 ~amd64
#required by xfce-base/thunar-1.4.0[dbus,xfce_plugins_trash], required by xfce-extra/thunar-volman-0.8.0, required by @selected, required by @world (argument)
=gnome-base/gvfs-1.12.3-r1 ~amd64
#required by sys-fs/udev-194[openrc], required by sys-fs/udisks-1.99.0-r1, 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-extra/thunar-volman-0.8.0, required by @selected, required by @world (argument)
=sys-fs/udev-init-scripts-16 ~amd64
#required by sys-fs/udev-194, required by sys-fs/udev-init-scripts-16
=sys-apps/kmod-10 ~amd64

Use --autounmask-write to write changes to config files (honoring CONFIG_PROTECT).
Back to top
View user's profile Send private message
DaggyStyle
Advocate
Advocate


Joined: 22 Mar 2006
Posts: 4895

PostPosted: Sun Oct 14, 2012 4:05 pm    Post subject: Reply with quote

ev56o wrote:
I unmerged kmod and the situation is the same.
Have you evere considerated the use flag question on kmod, udev, openrc and more?
Code:

localhost m # emerge -qDuNa world
[ebuild  N    ] sys-apps/module-init-tools-3.16-r1
[ebuild  NS   ] sys-fs/udisks-1.0.4-r2 [1.99.0-r1]
[ebuild  N    ] gnome-base/gvfs-1.12.3
[ebuild     U ] sys-fs/udev-194 [171-r6]
[ebuild  N    ] sys-fs/udev-init-scripts-16
[ebuild  N    ] gnome-base/gvfs-1.12.3-r1
[blocks B     ] <sys-fs/udev-186 ("<sys-fs/udev-186" is blocking sys-fs/udev-init-scripts-16)
[blocks B     ] sys-apps/kmod ("sys-apps/kmod" is blocking sys-apps/module-init-tools-3.16-r1)
[blocks B     ] sys-apps/module-init-tools ("sys-apps/module-init-tools" is blocking sys-apps/kmod-10)

!!! 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.12.3::gentoo, ebuild scheduled for merge) pulled in by
    (no parents that aren't satisfied by other packages in this slot)

  (gnome-base/gvfs-1.12.3-r1::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, installed)

sys-fs/udev:0

  (sys-fs/udev-171-r6::gentoo, installed) pulled in by
    (no parents that aren't satisfied by other packages in this slot)

  (sys-fs/udev-194::gentoo, ebuild scheduled for merge) pulled in by
    >=sys-fs/udev-187 required by (sys-fs/udev-init-scripts-16::gentoo, ebuild scheduled for merge)
    (and 1 more with the same problem)



The following keyword changes are necessary to proceed:
#required by sys-fs/udev-init-scripts-16
=sys-fs/udev-194 ~amd64
#required by xfce-base/thunar-1.4.0[dbus,xfce_plugins_trash], required by xfce-extra/thunar-volman-0.8.0, required by @selected, required by @world (argument)
=gnome-base/gvfs-1.12.3-r1 ~amd64
#required by sys-fs/udev-194[openrc], required by sys-fs/udisks-1.99.0-r1, 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-extra/thunar-volman-0.8.0, required by @selected, required by @world (argument)
=sys-fs/udev-init-scripts-16 ~amd64

Use --autounmask-write to write changes to config files (honoring CONFIG_PROTECT).
localhost m # emerge --unmerge sys-apps/kmod
 * This action can remove important packages! In order to be safer, use
 * `emerge -pv --depclean <atom>` to check for reverse dependencies before
 * removing packages.


!!! 'sys-apps/kmod' (virtual/modutils) is part of your system profile.
!!! Unmerging it may be damaging to your system.

>>> Waiting 10 seconds before starting...
>>> (Control-C to abort)...
Press Ctrl-C to Stop in:  10 9 8 7 6 5 4 3 2 1

 sys-apps/kmod
    selected: 10
   protected: none
     omitted: none

All selected packages: sys-apps/kmod-10

>>> 'Selected' packages are slated for removal.
>>> 'Protected' and 'omitted' packages will not be removed.

>>> Waiting 5 seconds before starting...
>>> (Control-C to abort)...
>>> Unmerging in:  5 4 3 2 1
>>> Unmerging (1 of 1) sys-apps/kmod-10...

 * GNU info directory index is up-to-date.
localhost m # revdep-rebuild -ip
 * Configuring search environment for revdep-rebuild

 * Checking reverse dependencies
 * Packages containing binaries and libraries broken by a package update
 * will be emerged.

 * Collecting system binaries and libraries
 * Generated new 1_files.rr
 * Collecting complete LD_LIBRARY_PATH
 * Generated new 2_ldpath.rr
 * Checking dynamic linking consistency
[ 100% ]                 

 * Dynamic linking on your system is consistent... All done.
localhost m # emerge --depclean

 * Depclean may break link level dependencies. Thus, it is
 * recommended to use a tool such as `revdep-rebuild` (from
 * app-portage/gentoolkit) in order to detect such breakage.
 *
 * Always study the list of packages to be cleaned for any obvious
 * mistakes. Packages that are part of the world set will always
 * be kept.  They can be manually added to this set with
 * `emerge --noreplace <atom>`.  Packages that are listed in
 * package.provided (see portage(5)) will be removed by
 * depclean, even if they are part of the world set.
 *
 * As a safety measure, depclean will not remove any packages
 * unless *all* required dependencies have been resolved.  As a
 * consequence, it is often necessary to run `emerge --update
 * --newuse --deep @world` prior to depclean.

Calculating dependencies... done!
 * Dependencies could not be completely resolved due to
 * the following required packages not being installed:
 *
 *   >=gnome-base/gvfs-1.10.1[udisks,udev] pulled in by:
 *     xfce-base/thunar-1.4.0
 *
 *   >=gnome-base/gvfs-1.10.1 pulled in by:
 *     xfce-base/thunar-1.4.0
 *
 *   sys-apps/kmod[tools] pulled in by:
 *     virtual/modutils-0
 *
 *   sys-fs/udisks:0 pulled in by:
 *     kde-base/kdelibs-4.8.5
 *
 * Have you forgotten to do a complete update prior to depclean? The
 * most comprehensive command for this purpose is as follows:
 *
 *   emerge --update --newuse --deep --with-bdeps=y @world
 *
 * Note that the --with-bdeps=y option is not required in many
 * situations. Refer to the emerge manual page (run `man emerge`)
 * for more information about --with-bdeps.
 *
 * Also, note that it may be necessary to manually uninstall
 * packages that no longer exist in the portage tree, since it may
 * not be possible to satisfy their dependencies.
localhost m # emerge --update --newuse --deep --with-bdeps=y @world
Calculating dependencies... done!
[ebuild  N     ] sys-apps/module-init-tools-3.16-r1  USE="-static"
[ebuild     U  ] dev-lang/nasm-2.10.01 [2.10]
[ebuild  N     ] perl-core/version-0.940.0
[ebuild  N     ] perl-core/Test-Harness-3.230.0
[ebuild  N     ] perl-core/Perl-OSType-1.2.0  USE="-test"
[ebuild  N     ] perl-core/JSON-PP-2.272.0
[ebuild  N     ] perl-core/CPAN-Meta-YAML-0.4.0
[ebuild  N     ] perl-core/Scalar-List-Utils-1.230.0
[ebuild  N     ] perl-core/ExtUtils-Manifest-1.580.0
[ebuild  N     ] perl-core/ExtUtils-Install-1.54
[ebuild  N     ] perl-core/ExtUtils-Command-1.170.0
[ebuild  N     ] perl-core/Test-Simple-0.980.0
[ebuild  N     ] perl-core/IO-1.25
[ebuild  N     ] virtual/perl-File-Temp-0.220.0-r2
[ebuild  N     ] virtual/perl-version-0.940.0
[ebuild  N     ] virtual/perl-JSON-PP-2.272.0-r1
[ebuild  N     ] virtual/perl-CPAN-Meta-YAML-0.4.0
[ebuild  N     ] virtual/perl-Scalar-List-Utils-1.230.0-r2
[ebuild     U  ] virtual/perl-Test-Harness-3.230.0-r3 [3.17]
[ebuild  N     ] virtual/perl-Perl-OSType-1.2.0-r1
[ebuild  N     ] virtual/perl-ExtUtils-Manifest-1.580.0-r1
[ebuild  N     ] virtual/perl-ExtUtils-Install-1.54
[ebuild  N     ] virtual/perl-ExtUtils-Command-1.170.0-r3
[ebuild  N     ] virtual/perl-Test-Simple-0.980.0-r2
[ebuild  N     ] virtual/perl-IO-1.25
[ebuild  N     ] perl-core/Module-Metadata-1.0.6
[ebuild  N     ] perl-core/Parse-CPAN-Meta-1.440.100
[ebuild  N     ] perl-core/Version-Requirements-0.101.20
[ebuild  N    ~] sys-apps/kmod-10  USE="tools zlib -debug -doc -lzma -static-libs"
[ebuild  N     ] virtual/perl-Parse-CPAN-Meta-1.440.100-r2
[ebuild  N     ] virtual/perl-Module-Metadata-1.0.6
[ebuild  N     ] virtual/perl-Version-Requirements-0.101.20-r2
[ebuild     U  ] dev-util/cmake-2.8.9 [2.8.8-r3]
[ebuild  NS    ] sys-fs/udisks-1.0.4-r2 [1.99.0-r1] USE="nls -debug -remote-access"
[ebuild  N     ] gnome-base/gvfs-1.12.3  USE="archive cdda fuse http udev -afp -avahi -bluetooth -bluray -doc -gdu -gnome-keyring -gphoto2 -ios -samba (-udisks)"
[ebuild  N     ] perl-core/ExtUtils-MakeMaker-6.620.0
[ebuild  N     ] virtual/perl-ExtUtils-MakeMaker-6.620.0
[ebuild  N     ] perl-core/CPAN-Meta-2.112.621
[ebuild  N     ] virtual/perl-CPAN-Meta-2.112.621
[ebuild     U  ] perl-core/Module-Build-0.380.0 [0.36.07]
[ebuild     U  ] virtual/perl-Module-Build-0.380.0-r2 [0.36.07]
[ebuild     U ~] sys-fs/udev-194 [171-r6] USE="openrc%* -acl% -doc% -static-libs%"
[ebuild  N    ~] sys-fs/udev-init-scripts-16
[ebuild  N    ~] gnome-base/gvfs-1.12.3-r1  USE="archive cdda fuse http udev udisks -afp -avahi -bluetooth -bluray -doc -gdu -gnome-keyring -gphoto2 -ios -samba"
[blocks B      ] <sys-fs/udev-186 ("<sys-fs/udev-186" is blocking sys-fs/udev-init-scripts-16)
[blocks B      ] sys-apps/kmod ("sys-apps/kmod" is blocking sys-apps/module-init-tools-3.16-r1)
[blocks B      ] sys-apps/module-init-tools ("sys-apps/module-init-tools" is blocking sys-apps/kmod-10)

!!! 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.12.3::gentoo, ebuild scheduled for merge) pulled in by
    (no parents that aren't satisfied by other packages in this slot)

  (gnome-base/gvfs-1.12.3-r1::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, installed)

sys-fs/udev:0

  (sys-fs/udev-171-r6::gentoo, installed) pulled in by
    (no parents that aren't satisfied by other packages in this slot)

  (sys-fs/udev-194::gentoo, ebuild scheduled for merge) pulled in by
    >=sys-fs/udev-187 required by (sys-fs/udev-init-scripts-16::gentoo, ebuild scheduled for merge)
    (and 1 more with the same problem)


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.

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


The following keyword changes are necessary to proceed:
#required by sys-fs/udev-init-scripts-16
=sys-fs/udev-194 ~amd64
#required by xfce-base/thunar-1.4.0[dbus,xfce_plugins_trash], required by xfce-extra/thunar-volman-0.8.0, required by @selected, required by @world (argument)
=gnome-base/gvfs-1.12.3-r1 ~amd64
#required by sys-fs/udev-194[openrc], required by sys-fs/udisks-1.99.0-r1, 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-extra/thunar-volman-0.8.0, required by @selected, required by @world (argument)
=sys-fs/udev-init-scripts-16 ~amd64
#required by sys-fs/udev-194, required by sys-fs/udev-init-scripts-16
=sys-apps/kmod-10 ~amd64

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


remove the keyword for sys-fs/udev-init-scripts-16.

next time, add the -t switch to emerge if you want to post the output
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein
ProjectFootball
Back to top
View user's profile Send private message
ev56o
Tux's lil' helper
Tux's lil' helper


Joined: 26 Jan 2010
Posts: 146

PostPosted: Sun Oct 14, 2012 6:53 pm    Post subject: Reply with quote

What is the keyword for sys-fs/udev-init-scripts-16? I have no /etc/portage/package.keywords.
Without kmod the system start with no support for keyboard and mouse and print a lot of errors in boot sequence about modprobe.
Back to top
View user's profile Send private message
DaggyStyle
Advocate
Advocate


Joined: 22 Mar 2006
Posts: 4895

PostPosted: Mon Oct 15, 2012 6:25 am    Post subject: Reply with quote

ev56o wrote:
What is the keyword for sys-fs/udev-init-scripts-16? I have no /etc/portage/package.keywords.
Without kmod the system start with no support for keyboard and mouse and print a lot of errors in boot sequence about modprobe.


look at the output, udev-194 is still getting pulled because sys-fs/udev-init-scripts-16 pulled.
both ate keyworded packages, that means that you cannot get back to stable system without downgrading them.
you said that you have no /etc/portage/package.keywords, that means that you are using ~amd64 as global which is a bad practice.

to verify, please post the output of emerge --info.
if I'm right, you need to update ACCEPT_KEYWORDS in /etc/make.conf to amd64 and update world, that will most certainly fix your issue but it will stabilize all other packages.
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein
ProjectFootball
Back to top
View user's profile Send private message
ev56o
Tux's lil' helper
Tux's lil' helper


Joined: 26 Jan 2010
Posts: 146

PostPosted: Mon Oct 15, 2012 9:47 am    Post subject: Reply with quote

It' s set to amd64
Code:

m@ubuntu ~ $ emerge --info
Portage 2.1.11.9 (default/linux/amd64/10.0/no-multilib, gcc-4.5.4, glibc-2.15-r2, 3.4.9-gentoo x86_64)
=================================================================
System uname: Linux-3.4.9-gentoo-x86_64-AMD_Athlon-tm-_64_Processor_3500+-with-gentoo-2.1
Timestamp of tree: Mon, 15 Oct 2012 09:15:01 +0000
app-shells/bash:          4.2_p37
dev-java/java-config:     2.1.11-r3
dev-lang/python:          2.7.3-r2, 3.2.3
dev-util/cmake:           2.8.8-r3
dev-util/pkgconfig:       0.27.1
sys-apps/baselayout:      2.1-r1
sys-apps/openrc:          0.9.8.4
sys-apps/sandbox:         2.5
sys-devel/autoconf:       2.13, 2.68
sys-devel/automake:       1.11.6
sys-devel/binutils:       2.22-r1
sys-devel/gcc:            4.5.4
sys-devel/gcc-config:     1.7.3
sys-devel/libtool:        2.4-r1
sys-devel/make:           3.82-r3
sys-kernel/linux-headers: 3.4-r2 (virtual/os-headers)
sys-libs/glibc:           2.15-r2
Repositories: gentoo
ACCEPT_KEYWORDS="amd64"
ACCEPT_LICENSE="*"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-O2 -march=native"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/config /usr/share/gnupg/qualified.txt"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo"
CXXFLAGS="-O2 -march=native"
DISTDIR="/usr/portage/distfiles"
FCFLAGS="-O2 -pipe"
FEATURES="assume-digests binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles news parallel-fetch parse-eapi-ebuild-head protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch"
FFLAGS="-O2 -pipe"
GENTOO_MIRRORS="ftp://mirrors.tera-byte.com/pub/gentoo http://gentoo.mirrors.tera-byte.com/  ftp://mirror.csclub.uwaterloo.ca/gentoo-distfiles/ ftp://ftp.gtlib.gatech.edu/pub/gentoo http://www.gtlib.gatech.edu/pub/gentoo ftp://ftp.ucsb.edu/pub/mirrors/linux/gentoo/ http://ftp.ucsb.edu/pub/mirrors/linux/gentoo/ http://mirror.mcs.anl.gov/pub/gentoo/ ftp://mirror.mcs.anl.gov/pub/gentoo/ http://gentoo.cites.uiuc.edu/pub/gentoo/ ftp://gentoo.cites.uiuc.edu/pub/gentoo/ http://gd.tuwien.ac.at/opsys/linux/gentoo/ ftp://gd.tuwien.ac.at/opsys/linux/gentoo/ http://ftp.first-world.info/ ftp://ftp.first-world.info/ http://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ ftp://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ http://gentoo.po.opole.pl ftp://gentoo.po.opole.pl http://gentoo.mirror.pw.edu.pl/ http://www.mirrorservice.org/sites/www.ibiblio.org/gentoo/ ftp://ftp.mirrorservice.org/sites/www.ibiblio.org/gentoo/ http://ftp.jaist.ac.jp/pub/Linux/Gentoo/ ftp://ftp.jaist.ac.jp/pub/Linux/Gentoo/ http://mirrors.64hosting.com/pub/mirrors/gentoo/ ftp://mirrors.64hosting.com/pub/mirrors/gentoo/ http://gentoo.cs.nctu.edu.tw/gentoo/ ftp://gentoo.cs.nctu.edu.tw/gentoo/"
LANG="en_US.utf8"
LDFLAGS="-Wl,-O1 -Wl,--as-needed"
MAKEOPTS="-j1"
PKGDIR="/usr/portage/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="3dnow X a52 aac aalib alsa amd64 apng archive berkdb bzip2 cairo cdda cgi cjk cli cracklib crashreporter cxx dbus device-mapper dhcp dri dv dvb dvd dvdr ext4 fat fbcon ffmpeg fluidsynth fortran fuse gd gdbm gif gimp gnutls gpm gstreamer gtk gudev hwdb iconv imap ipc java javascript jbig jpeg jpeg2k kde lame lcms libedit libnotify libv4l2 midi minizip mmx modules mozdom mp3 mpeg mudflap ncurses nls nptl nsplugin ntfs ntfsprogs ogg opengl openmp openrc openxml pcre pdf png policykit pppd python qt3support qt4 quicktime readline reiser4 reiserfs remote secure-delete soap sockets sqlite sse sse2 ssh ssl startup-notification svg system-sqlite sysvipc tcpd theora tiff twolame udev udisks unicode unlock-notify v4l val2 vorbis wavpack webkit webm xfs xml xmlreader xmlwriter xorg xv xvid zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="kexi words flow plan sheets stage tables krita karbon braindump" CAMERAS="ptp2" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf superstar2 timing tsip tripmate tnt ubx" INPUT_DEVICES="evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LIBREOFFICE_EXTENSIONS="presenter-console presenter-minimizer" PHP_TARGETS="php5-3" PYTHON_TARGETS="python3_2 python2_7" RUBY_TARGETS="ruby18 ruby19" USERLAND="GNU" VIDEO_CARDS="radeon" XFCE_PLUGINS="trash" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account"
Unset:  CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, LINGUAS, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, USE_PYTHON
Back to top
View user's profile Send private message
DaggyStyle
Advocate
Advocate


Joined: 22 Mar 2006
Posts: 4895

PostPosted: Mon Oct 15, 2012 10:40 am    Post subject: Reply with quote

ok, these lines are a problem:
Code:
[blocks B     ] sys-apps/kmod ("sys-apps/kmod" is blocking sys-apps/module-init-tools-3.16-r1)
[blocks B     ] sys-apps/module-init-tools ("sys-apps/module-init-tools" is blocking sys-apps/kmod-10)

sys-apps/module-init-tools and sys-apps/kmod cannot coexists together on the same system.

as udev needs kmod, you need to unmerge module-init-tools.

unmerge udisk-1.99.0-r1, it depends on keyworded udev, don't forget to remove udisk flags from all packages that needs least udisk-1.99.0.

now, please run eix udev and eix sys-fs/udev-init-scripts and post the outputs here.
if you don't have eix, run emerge app-portage/eix and then eix-update.
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein
ProjectFootball
Back to top
View user's profile Send private message
steveL
Advocate
Advocate


Joined: 13 Sep 2006
Posts: 2164
Location: The Peanut Gallery

PostPosted: Mon Oct 15, 2012 11:19 am    Post subject: Reply with quote

DaggyStyle wrote:
sys-apps/module-init-tools and sys-apps/kmod cannot coexists together on the same system.

as udev needs kmod, you need to unmerge module-init-tools.

It's keyworded udev which needs kmod (I don't have it installed here, on udev-171-r6.) So if he's going for stable, that's prob'y the wrong way round.

I think the real issue is that thunar-1.4 requires gnome-base/gvfs-1.12.3-r1, which is then pulling in keyworded udisks, udev and init-scripts. And it looks like that is being pulled in by xfce-extra/thunar-volman, which is in world.

eix -e thunar shows only that version of thunar, though, so it's probably the USE flags[dbus,xfce_plugins_trash].

I'd start with emerge -C thunar-volman and at least get to a stable, running install, then sort out X and DE.
Back to top
View user's profile Send private message
DaggyStyle
Advocate
Advocate


Joined: 22 Mar 2006
Posts: 4895

PostPosted: Mon Oct 15, 2012 11:57 am    Post subject: Reply with quote

steveL wrote:
DaggyStyle wrote:
sys-apps/module-init-tools and sys-apps/kmod cannot coexists together on the same system.

as udev needs kmod, you need to unmerge module-init-tools.

It's keyworded udev which needs kmod (I don't have it installed here, on udev-171-r6.) So if he's going for stable, that's prob'y the wrong way round.


you are correct, my bad.
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein
ProjectFootball
Back to top
View user's profile Send private message
jrussia
Tux's lil' helper
Tux's lil' helper


Joined: 29 Aug 2012
Posts: 89
Location: Chicago

PostPosted: Mon Oct 15, 2012 3:59 pm    Post subject: Reply with quote

Do you have a package.accept_keywords file? Check that also.
Back to top
View user's profile Send private message
ev56o
Tux's lil' helper
Tux's lil' helper


Joined: 26 Jan 2010
Posts: 146

PostPosted: Tue Oct 16, 2012 9:38 am    Post subject: Reply with quote

@jrussia no idon' t have that
Code:

m@ubuntu ~ $ ls /etc/portage/
bin  package.unmask  postsync.d  savedconfig


@steveL @DaggyStyle you talk about flag use, shall we enter in the stable branch? I mean we shall work in a lower level of flag use. What is your plane? I don' t understand.
Back to top
View user's profile Send private message
Scimmia22
n00b
n00b


Joined: 24 Sep 2012
Posts: 10

PostPosted: Tue Oct 16, 2012 9:48 am    Post subject: Reply with quote

Yeah, and what, exactly, is in portage.unmask?

ev56o, I'm really getting the feeling that you have no concept of how portage works. Unmasking packages is EXACTLY what we've been talking about!
Back to top
View user's profile Send private message
steveL
Advocate
Advocate


Joined: 13 Sep 2006
Posts: 2164
Location: The Peanut Gallery

PostPosted: Wed Oct 17, 2012 12:24 pm    Post subject: Reply with quote

ev56o wrote:
Code:

m@ubuntu ~ $ ls /etc/portage/
bin  package.unmask  postsync.d  savedconfig

@steveL @DaggyStyle you talk about flag use, shall we enter in the stable branch? I mean we shall work in a lower level of flag use. What is your plane? I don' t understand.

There's two aspects: unmasking or keywording unstable packages, which should be done on an individual basis, if and only if you are happy for them to break, and for you to do some work fixing them-- so usually packages you really care about, or that are needed to make another package work. You want to get back to a stable system, then later unmask (which usually means an entry in package.keywords) as and when you want.

The second aspect is USE flags, similar to (and often translated into) configure switches (like --without-xml or --with-gtk). These often pull in additional dependencies (which is why it's useful to be able to switch them off; something you can't do with a binary distro.)

In your current situation, as I said, the problem is that xfce-extra/thunar-volman is in world, and is pulling in thunar-1.4 which in turn is pulling in gnome-base/gvfs-1.12.3-r1, which is then pulling in keyworded (ie unstable) udisks, udev and init-scripts.

So like I said, I'd start with emerge -C thunar-volman and at least get to a stable, running install, then sort out X. An emerge -avC should also help: it means depclean, so after you've taken thunar-volman out it should want to remove other stuff.

So on balance: I'd just do: emerge -aC thunar-volman thunar gnome-base/gvfs followed by emerge -avC in the console, not in X.

You should rm /etc/portage/package.unmask Don't use that file, in general. (I don't have one on my install, which is a few years old now.) Use package.keywords, when the time comes, and package.use to set USE on a per-package basis.
Back to top
View user's profile Send private message
ev56o
Tux's lil' helper
Tux's lil' helper


Joined: 26 Jan 2010
Posts: 146

PostPosted: Thu Oct 18, 2012 2:53 pm    Post subject: Reply with quote

I removed package.unmask and unmerged thunar and thunar-volman
Code:

ubuntu ~ # cat package.unmask
www-plugins/adobe-flash
www-plugins/nspluginwrapper
app-emulation/emul-linux-x86-gtklibs
app-emulation/emul-linux-x86-soundlibs
app-emulation/emul-linux-x86-opengl
app-emulation/emul-linux-x86-xlibs
app-emulation/emul-linux-x86-baselibs
app-emulation/emul-linux-x86-medialibs
ubuntu / # emerge -qDuNa world
[ebuild  N    ] sys-apps/module-init-tools-3.16-r1
[ebuild  N    ] app-text/docbook-dsssl-stylesheets-1.79
[ebuild  N    ] app-text/docbook-sgml-dtd-3.0-r3
[ebuild  NS   ] app-text/docbook-xml-dtd-4.3-r1 [4.1.2-r6, 4.2-r2, 4.4-r2]
[ebuild  N    ] app-text/opensp-1.5.2-r3
[ebuild     U ] media-video/mplayer-1.1-r1 [1.0_rc4_p20110322-r1]
[ebuild     U ] dev-util/cmake-2.8.9 [2.8.8-r3]
[ebuild     U ] dev-libs/libdbusmenu-qt-0.9.2 [0.8.2]
[ebuild  N    ] app-text/openjade-1.3.2-r3
[ebuild  N    ] dev-util/gtk-doc-1.18-r1
[ebuild   R   ] x11-libs/pango-1.30.1
[ebuild  N    ] sys-apps/kmod-10
[ebuild  NS   ] sys-fs/udisks-1.0.4-r2 [1.99.0-r1]
[ebuild  N    ] app-misc/geoclue-0.12.99
[ebuild   R   ] x11-libs/gtksourceview-2.10.5-r2
[ebuild     U ] kde-misc/polkit-kde-kcmodules-0.98_pre20120917 [0.98_pre20101127]
[ebuild     U ] sys-fs/udev-194 [171-r6]
[ebuild  N    ] sys-fs/udev-init-scripts-16
[ebuild  N    ] net-libs/webkit-gtk-1.8.3-r300
[ebuild     U ] net-libs/libproxy-0.4.10 [0.4.7]
[ebuild  N    ] gnome-base/gvfs-1.12.3
[ebuild  N    ] gnome-base/gvfs-1.12.3-r1
[ebuild  N    ] xfce-base/thunar-1.4.0
[blocks B     ] <sys-fs/udev-186 ("<sys-fs/udev-186" is blocking sys-fs/udev-init-scripts-16)
[blocks B     ] sys-apps/kmod ("sys-apps/kmod" is blocking sys-apps/module-init-tools-3.16-r1)
[blocks B     ] sys-apps/module-init-tools ("sys-apps/module-init-tools" is blocking sys-apps/kmod-10)

!!! 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.12.3::gentoo, ebuild scheduled for merge) pulled in by
    (no parents that aren't satisfied by other packages in this slot)

  (gnome-base/gvfs-1.12.3-r1::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)

sys-fs/udev:0

  (sys-fs/udev-171-r6::gentoo, installed) pulled in by
    (no parents that aren't satisfied by other packages in this slot)

  (sys-fs/udev-194::gentoo, ebuild scheduled for merge) pulled in by
    >=sys-fs/udev-187 required by (sys-fs/udev-init-scripts-16::gentoo, ebuild scheduled for merge)
    (and 1 more with the same problem)



The following keyword changes are necessary to proceed:
#required by sys-fs/udev-init-scripts-16
=sys-fs/udev-194 ~amd64
#required by xfce-base/thunar-1.4.0[udev], required by xfce-extra/tumbler-0.1.25, required by @selected, required by @world (argument)
=gnome-base/gvfs-1.12.3-r1 ~amd64
#required by sys-fs/udev-194[openrc], required by sys-fs/udisks-1.99.0-r1, required by gnome-base/gvfs-1.12.3-r1[udisks], required by
xfce-base/thunar-1.4.0[udev], required by xfce-extra/tumbler-0.1.25, required by @selected, required by @world (argument)
=sys-fs/udev-init-scripts-16 ~amd64
#required by sys-fs/udev-194, required by sys-fs/udev-init-scripts-16
=sys-apps/kmod-10 ~amd64

Use --autounmask-write to write changes to config files (honoring CONFIG_PROTECT).
ubuntu / # emerge -avC
 * This action can remove important packages! In order to be safer, use
 * `emerge -pv --depclean <atom>` to check for reverse dependencies before
 * removing packages.

emerge unmerge can only be used with specific package names

ubuntu / # emerge --depclean

 * Depclean may break link level dependencies. Thus, it is
 * recommended to use a tool such as `revdep-rebuild` (from
 * app-portage/gentoolkit) in order to detect such breakage.
 *
 * Always study the list of packages to be cleaned for any obvious
 * mistakes. Packages that are part of the world set will always
 * be kept.  They can be manually added to this set with
 * `emerge --noreplace <atom>`.  Packages that are listed in
 * package.provided (see portage(5)) will be removed by
 * depclean, even if they are part of the world set.
 *
 * As a safety measure, depclean will not remove any packages
 * unless *all* required dependencies have been resolved.  As a
 * consequence, it is often necessary to run `emerge --update
 * --newuse --deep @world` prior to depclean.

Calculating dependencies... done!
 * Dependencies could not be completely resolved due to
 * the following required packages not being installed:
 *
 *   sys-apps/kmod[tools] pulled in by:
 *     virtual/modutils-0
 *
 *   sys-fs/udisks:0 pulled in by:
 *     kde-base/kdelibs-4.8.5
 *
 *   >=xfce-base/thunar-1.4 pulled in by:
 *     xfce-extra/tumbler-0.1.25
 *
 * Have you forgotten to do a complete update prior to depclean? The
 * most comprehensive command for this purpose is as follows:
 *
 *   emerge --update --newuse --deep --with-bdeps=y @world
 *
 * Note that the --with-bdeps=y option is not required in many
 * situations. Refer to the emerge manual page (run `man emerge`)
 * for more information about --with-bdeps.
 *
 * Also, note that it may be necessary to manually uninstall
 * packages that no longer exist in the portage tree, since it may
 * not be possible to satisfy their dependencies.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Portage & Programming All times are GMT
Goto page Previous  1, 2, 3  Next
Page 2 of 3

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum