Bug 141182

Summary:	sys-fs/cryptsetup-luks should not die without a configured kernel
Product:	Gentoo Linux	Reporter:	Chris Gianelloni (RETIRED) <wolf31o2>
Component:	New packages	Assignee:	Benjamin Smee (strerror) (RETIRED) <strerror>
Status:	RESOLVED FIXED
Severity:	normal	CC:	base-system, ikorot01, releng
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Chris Gianelloni (RETIRED) gentoo-dev

2006-07-20 08:42:04 UTC

Quite simply, the package compiles just fine without kernel sources.  Simply removing the linux-info_pkg_setup line from pkg_setup is enough to make this package work properly for release building.  What this does is causes the package to spit out a warning if it cannot determine the kernel information, but it doesn't make it fatal, since it is possible to be building this package in many ways, such as building a LiveCD or GRP set.

Thanks

Comment 1 Lars Weiler (RETIRED) gentoo-dev

2006-09-13 14:14:45 UTC

I just hit this bug again during a test-catalyst-run.  Would be great if this will be officially resolved instead of in the release-snapshot only.

Comment 2 Benjamin Smee (strerror) (RETIRED) gentoo-dev

2006-09-18 02:49:31 UTC

commited. Sorry about the delay.

Comment 3 Jakub Moc (RETIRED) gentoo-dev

2006-12-07 13:21:16 UTC

*** Bug 157467 has been marked as a duplicate of this bug. ***

Comment 4 Igor Korot 2006-12-07 14:23:22 UTC

Hi,
I got this bug when trying to build an ivman (bug 157467).
Then I re-compiled the kernel with a an asking support, and I still got this message pops-up. I think it should not be reported, if the kernel configuration is correct.

Thank you.

Comment 5 Andrew Gaffney (RETIRED) gentoo-dev

2006-12-07 14:26:11 UTC

No, your "bug" is just the opposite. It is the *intended* behavior for it to continue compiling, even if the support is not in the current kernel. This is necessary for building releases. Anyway, it's not changing.

Comment 6 Igor Korot 2006-12-07 14:31:39 UTC

(In reply to comment #5)
> No, your "bug" is just the opposite. It is the *intended* behavior for it to
> continue compiling, even if the support is not in the current kernel. This is
> necessary for building releases. Anyway, it's not changing.

Yes, it is the opposite.
But when I turn on this option, re-compiled the kernel, re-booted and tried again, I get the same message. Does this mean that the package does not actually check for that option, and the message is just a warning?