View previous topic :: View next topic |
Author |
Message |
Oo.et.oO Apprentice
Joined: 23 Apr 2002 Posts: 291 Location: burlington
|
Posted: Thu Jan 24, 2013 5:31 pm Post subject: <sys-fs/udev-186 blocking sys-fs/udev-init-scripts [solve |
|
|
Code: | emerge -av1D sys-fs/udev
These are the packages that would be merged, in order:
Calculating dependencies ... done!
[ebuild U ] sys-apps/hwids-20130114 [20121119] USE="udev%*" 1,437 kB
[ebuild U ] sys-fs/udev-197-r3 [171-r9] USE="acl%* gudev hwdb introspection* keymap kmod%* openrc%* -doc% (-selinux) -static-libs% (-action_modeswitch%) (-build%) (-debug%) (-edd%) (-extras%) (-floppy%) (-rule_generator%*) (-test%)" 2,008 kB
[ebuild U ] virtual/udev-197 [171] USE="gudev hwdb introspection* keymap* (-selinux) -static-libs" 0 kB
[ebuild N ] sys-fs/udev-init-scripts-19-r1 5 kB
[blocks B ] <sys-fs/udev-186 ("<sys-fs/udev-186" is blocking sys-fs/udev-init-scripts-19-r1)
|
wth? not sure why portage can't figure this one out on its own.
can i unmerge udev and then remerge it without it crapping all over itself? ie, will the re-merge still have access to the disks, etc?
Last edited by Oo.et.oO on Thu Jan 24, 2013 8:06 pm; edited 1 time in total |
|
Back to top |
|
|
audiodef Watchman
Joined: 06 Jul 2005 Posts: 6639 Location: The soundosphere
|
|
Back to top |
|
|
Oo.et.oO Apprentice
Joined: 23 Apr 2002 Posts: 291 Location: burlington
|
Posted: Thu Jan 24, 2013 8:05 pm Post subject: |
|
|
thanks audiodef. the good news is that you can indeed unmerge udev and remerge it.
the bad news is that udev-197 is keyword masked ~amd64.
and creates a whole slew of blockers (X) that require =udev-171 |
|
Back to top |
|
|
ulenrich Veteran
Joined: 10 Oct 2010 Posts: 1480
|
Posted: Thu Jan 24, 2013 8:39 pm Post subject: |
|
|
emerge -auvDN world
not just udev! It is a deeper system change though ...
udev-197-r3 is stable for pc! |
|
Back to top |
|
|
|