Jump to content
funtoo forums

Recommended Posts

As per http://bugs.funtoo.org/browse/FL-986 Funtoo now updating udev (eudev). This update require manual intervention, here are the steps after tree update (emerge --sync)

 

# emerge --sync

# emerge --deselect udev

# emerge virtual/udev

# dispatch-conf or etc-update (be careful)

# emerge @preserved-rebuild

 

Reboot. keep a systemrescue cd near in case of uncertain troubles. There're numerous packages forked in Funtoo tree to prevent udev updates. These whould need update or unfork, all emerge output should be directed to relevant bug report, see above link and on Funtoo IRC #funtoo channel, nick angry_vincent.

 

Share this post


Link to post
Share on other sites

I updated a home server over here, and there were no troubles, but I have yet to update a desktop. I have seen a report on bugs.funtoo.org of someone losing their mouse and keyboard after this update. Was this working for you on a desktop?

Share this post


Link to post
Share on other sites

I only have one issue here, which seems to be only a problem while building stage3s. There is a file collision between eudev and udev-init-scripts :

 * Searching for /etc/init.d/udev-postmount ... 
sys-fs/eudev-1.5.3-r1 (/etc/init.d/udev-postmount)
sys-fs/udev-init-scripts-27 (/etc/init.d/udev-postmount) 

It does not cause issues on a live system, but maybe because of different Portage configuration in Metro, stage3 fails with the following :

* Detected file collision(s):
 *
 *      /etc/init.d/udev-postmount
 *
 * Searching all installed packages for file collisions...
 *
 * Press Ctrl-C to Stop
 *
 * sys-fs/eudev-1.5.3-r1:0::gentoo
 *      /etc/init.d/udev-postmount
 *
 * Package 'sys-fs/udev-init-scripts-27' NOT merged due to file
 * collisions. If necessary, refer to your elog messages for the whole
 * content of the above message.

Thanks!

Share this post


Link to post
Share on other sites

As per http://bugs.funtoo.org/browse/FL-986 Funtoo now updating udev (eudev). This update require manual intervention, here are the steps after tree update (emerge --sync)

 

# emerge --sync

# emerge --deselect udev

# emerge virtual/udev

# dispatch-conf or etc-update (be careful)

# emerge @preserved-rebuild

 

 

Is that right? I'm a bit confused here.

mira ~ # emerge --version
Portage 2.3.6-r8 (funtoo/1.0/linux-gnu/arch/x86-64bit, gcc-4.8.2, glibc-2.18-r1, 3.11.6-gentoo-pbx x86_64)

mira ~ # emerge --sync
>>> Starting git pull...
[...]
>>> Git pull in /usr/portage successful

mira ~ # emerge --deselect udev
>>> No matching atoms found in "world" favorites file...

Share this post


Link to post
Share on other sites

Is that right? I'm a bit confused here.

mira ~ # emerge --version
Portage 2.3.6-r8 (funtoo/1.0/linux-gnu/arch/x86-64bit, gcc-4.8.2, glibc-2.18-r1, 3.11.6-gentoo-pbx x86_64)

mira ~ # emerge --sync
>>> Starting git pull...
[...]
>>> Git pull in /usr/portage successful

mira ~ # emerge --deselect udev
>>> No matching atoms found in "world" favorites file...
I got the same. You should be fine.

Share this post


Link to post
Share on other sites

×
×
  • Create New...