| Summary: | New device-mapper has gentoo-sources depend, old ones didn't | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Christopher Culver <crculver> |
| Component: | [OLD] Core system | Assignee: | Max Kalika (RETIRED) <max> |
| Status: | RESOLVED FIXED | ||
| Severity: | blocker | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
the ebuild checks for /usr/src/linux/include/linux/dm-ioctl.h. if the header doesn't exist, there is no dm support in the kernel I'm using the dm crypto target right now for /home, so there most definitely is dm support in my kernel. Surely this latest ebuild is looking for the wrong header. Besides, the problem of the gentoo-sources depend remains. There's no reason why a simple "emerge -u device-mapper" should want to pull in gentoo-sources and force the user to do an "emerge -u --nodeps". the package doesnt build against the kernel source so there's no point to the check also, that check has always been there, it's nothing new |
I can't upgrade from device-mapper-1.00.19-r1 to device-mapper-1.00.19-r2 without installing and even using gentoo-sources. With vanilla sources installed and used, trying "emerge -u --nodeps" gives this error: >>> md5 src_uri ;-) device-mapper.1.00.19.tgz * * Your currently linked kernel (/usr/src/linux) hasn't * been patched for device mapper support. * I have used the vanilla kernel with device-mapper since the beginning and I think it's unreasonable for vanilla-source users to have to move to gentoo-sources just to get existing functionality. Reproducible: Always Steps to Reproduce: 1. 2. 3.