http://bugzilla.rpmfusion.org/show_bug.cgi?id=802
--- Comment #21 from Jack Neely <jjneely(a)ncsu.edu> 2009-10-21 20:49:56 ---
(In reply to comment #20)
# From e2fsprogs
rm -f ${RPM_BUILD_ROOT}/usr/bin/compile_et
Why do you need a own e2fsprogs during the build step?
I've clarified the comment in the spec file for this.
-# From e2fsprogs
+# compile_et is built as part of OpenAFS's libcom_err internal
+# implementation. Its not needed after the initial build and
+# will cause an RPM file conflict with the system version from
+# e2fsprogs.
Being that OpenAFS's internal libcom_err implementation is custom, I cannot
remove it. The man page for the command confirms its used at build time only.
http://docs.openafs.org/Reference/1/compile_et.html
# No kernel module cruft in this package
rm -f ${RPM_BUILD_ROOT}%{_libdir}/openafs/libafs-*
This seems not a path which is relating to any kernel module.
If only OpenAFS's makefile knew this. I've double checked, and it turns out
that this package is not installing any cruft there so I've removed that from
the .spec. But alas, OpenAFS puts copies of its kernel modules there.
http://www4.ncsu.edu/~jjneely/SPECS/openafs-1.4.11-8.fc11.spec
http://www4.ncsu.edu/~jjneely/SRPMS/openafs-1.4.11-8.fc11.src.rpm
--
Configure bugmail:
http://bugzilla.rpmfusion.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.