Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 388075 - sys-fs/udev-164-r2 doesn't create sd* device nodes with <sys-libs/glibc-2.12
Summary: sys-fs/udev-164-r2 doesn't create sd* device nodes with <sys-libs/glibc-2.12
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: udev maintainers
URL:
Whiteboard:
Keywords:
Depends on: 411903
Blocks:
  Show dependency tree
 
Reported: 2011-10-22 03:15 UTC by Tiago Marques
Modified: 2012-08-11 17:03 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tiago Marques 2011-10-22 03:15:40 UTC
It seems that udev-164-r2 should be pulling a more recent version of glibc as a dependency (2.12.2 works for me) but instead doesn't and after rebooting the system breaks.

If the maintainer could add a version check to the udev package I'm sure it would save a lot of trouble to some people, as it took me a few hours to track the issue back to glibc. The error was related to an unimplemented inotify function.

Reproducible: Always

Steps to Reproduce:
1. Install glibc-2.11.2-r3 and udev-164-r2
2. Reboot
3.
Actual Results:  
The system doesn't create any /dev nodes for hardware and the system can't mount the root device.

Expected Results:  
udev should create /dev nodes and mount the root device.
Comment 1 Ian Stakenvicius (RETIRED) gentoo-dev 2011-10-23 01:37:09 UTC
As glibc-2.12.2 is current stable, is there any particular reason why your system wasn't using it?

Anyways, since the dep currently is >=glibc-2.9, it makes sense (if the toolchain dev's agree) that this should be adjusted to >=glibc-2.12
Comment 2 Tiago Marques 2011-10-23 10:59:07 UTC
Hi,

This is a server, I don't have the time to be constantly updating the whole system and dealing with issues caused by that. Hence - and even with my desktop systems nowadays - I limit myself to pull security fixes and only pull whatever is needed for some new package, which in this case caught this problem. 

I know this is kind of an uncommon problem for someone who regularly emerges the world but don't the devs have some kind of a test machine where updates would be pulled by dependencies only before packages are marked as x86 and amd64 stable? Otherwise it is kind of hard to notice it. I imagine this kind of problem is bothersome for everyone that tries to use gentoo on production machines.

Best regards,
Tiago
Comment 3 Ryan Hill (RETIRED) gentoo-dev 2011-10-23 15:56:36 UTC
Nothing toolchain can do here, reassigning.

Please include the output of `emerge --info` when filing bug reports.
Comment 4 William Hubbs gentoo-dev 2011-12-10 23:35:37 UTC
glibc-2.12 does not exist on alpha, so I need to wait for >=glibc-2.13
to be stabilized before I can adjust the dependencies.
Comment 5 Samuli Suominen (RETIRED) gentoo-dev 2012-08-11 17:03:23 UTC
+  11 Aug 2012; Samuli Suominen <ssuominen@gentoo.org> udev-164-r2.ebuild,
+  udev-171-r6.ebuild, udev-187-r1.ebuild, udev-187-r3.ebuild, udev-9999.ebuild:
+  Update sys-libs/glibc block from <2.9 to <2.12 wrt #388075 by Tiago Marques