| Summary: | Failed to emerge sys-fs/udev-141 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | hexa <martin> |
| Component: | [OLD] Core system | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | VERIFIED CANTFIX | ||
| Severity: | normal | CC: | jer |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
hexa
2009-07-02 11:03:36 UTC
Well, from the manpage: SO_RCVBUFFORCE (since Linux 2.6.14) So, it's probably linux-headers, or more like 'emerge -upvD world' (you glibc is a BIT old too). (In reply to comment #0) > Portage 2.1.6.13 (default/linux/x86/2008.0/server, gcc-3.4.4, glibc-2.3.5-r2, > 2.6.25-gentoo-r7ISG i686) You have got to be kidding. glibc-2.3.5-r2 went stable at commit time in October 2005, that's almost 4 years ago. Same with gcc-3.4.4-r1, which went stable at roughly the same time. > dev-lang/python: 2.4.4-r14, 2.5.4-r2 Outdated. > sys-apps/sandbox: 1.2.18.1-r2 Outdated. > sys-devel/autoconf: 2.13, 2.61-r2 Outdated. > sys-devel/binutils: 2.16.1 Outdated. From the same era as the rest of the toolchain. > sys-devel/gcc-config: 1.3.12-r6 Outdated. > sys-devel/libtool: 1.5.22 Outdated. > virtual/os-headers: 2.6.11-r2 Outdated. Please run `emerge -vuatDN world', use the result as best you can and stop reporting bugs until your system is current. Hi, portage has a dependency system. Please fix the dependencies of this ebuild to correct versions. I have updated all of the software/dependencies as ebuild required and it doesn't compile. @Rafał Mużyło. Thanks for the hint. This might work. :-) I'll report back if the ebuild needs just another dependency on newer kernel headers. This would then solve this bug. :-) Both Jer and you are right: your system IS outdated and 'emerge -upvD world' should have told you that. However devs tend to miss some of version requirements, as they tend to update the deps before it's required, so they only see that all deps are met, not that version deps are in the need of a bump, especially if older versions went out of portage tree. No, we won't start considering backporting new versions to whatever was a la mode in 2005. Please do not reopen this bug report. (In reply to comment #4) > Both Jer and you are right: > your system IS outdated and 'emerge -upvD world' > should have told you that. > However devs tend to miss some of version requirements, > as they tend to update the deps before it's required, > so they only see that all deps are met, not that > version deps are in the need of a bump, > especially if older versions went out of portage tree. So what that means is that Gentoo's sys-fs/udev maintainers should not need to go back and find versions of sys-libs/glibc or sys-kernel/linux-headers that will NOT work with the stable sys-fs/udev and then block them. It's an impossible task for any number of developers, and getting "help" from users of old headers and libraries actually isn't, while at the same time it is a lot more trouble to backward-fix dependencies than to simply ask everyone to upgrade to the latest versions before they seek support. I will not reopen it, but i don't think it's so complicated to fix these dependencies.
Correct me if i'm wrong 'cause i'm guessing here, but wouldn't changing this:
RDEPEND="${COMMON_DEPEND}
!sys-apps/coldplug
!<sys-fs/device-mapper-1.02.19-r1
>=sys-apps/baselayout-1.12.5"
to somth. like this
RDEPEND="${COMMON_DEPEND}
!sys-apps/coldplug
!<sys-fs/device-mapper-1.02.19-r1
>=sys-apps/baselayout-1.12.5
>=linux-headers-2.6.27-r2"
"fix" this "bug"?
I guess i'm missing something here, due to my lack of knowledge, to see where all the hard time consuming work is.
I'll try upgrading headers next week and see if it compiles then.
Thank you all for your responses.
|
