On Thu, Oct 28, 2010 at 10:50:25AM -0400, Tom spot Callaway wrote:
On 10/27/2010 11:02 AM, Don Zickus wrote:
Not that I feel like arguing to save dangling symlink, what happens in the
case when you install kernel-devel-$KERNVER but there is no
kernel-$KERNVER installed to match? Does the
Dave Jones (da...@redhat.com) said:
kernel.x86_64: W: non-conffile-in-etc
/etc/ld.so.conf.d/kernel-2.6.36-1.fc15.x86_64.conf
(Should this be marked as %config(noreplace)?)
it's versioned, so no ? I think ?
I would assume that ld.so.conf.d files aren't really config files
in the
On Tue, Oct 26, 2010 at 02:18:52PM -0400, Bill Nottingham wrote:
Dave Jones (da...@redhat.com) said:
kernel.x86_64: W: non-conffile-in-etc
/etc/ld.so.conf.d/kernel-2.6.36-1.fc15.x86_64.conf
(Should this be marked as %config(noreplace)?)
it's versioned, so no ? I
kernel.x86_64: E: shared-lib-without-dependency-information
/lib/modules/2.6.36-1.fc15.x86_64/vdso/vdso32-syscall.so
kernel.x86_64: E: shared-lib-without-dependency-information
/lib/modules/2.6.36-1.fc15.x86_64/vdso/vdso.so
kernel.x86_64: E: shared-lib-without-dependency-information
$ cat /etc/ld.so.conf.d/kernel-2.6.35.6-45.fc14.x86_64.conf
# Placeholder file, no vDSO hwcap entries used in this kernel.
If that's the case, why package it at all?
There's no need for it. We just don't have a way (with .spec magic I know,
anyway) to decide at the right time whether we
On Tue, Oct 26, 2010 at 02:10:23PM -0400, Dave Jones wrote:
kernel.x86_64: W: dangling-relative-symlink
/lib/modules/2.6.36-1.fc15.x86_64/build
../../../usr/src/kernels/2.6.36-1.fc15.x86_64
(It seems odd that /lib/modules/2.6.36-1.fc15.x86_64/build is packaged in
kernel, but
