On 05.04.2009 10:27, Thorsten Leemhuis wrote:
Sorry, I didn#t get around to answer this mail earlier.
On 01.04.2009 10:22, Denis Leroy wrote:
> Do yo know what is up with the rebuilds of open-vm-tools ? It seems
> currently broken somehow. I've checked in the latest version of the
> package, but the akmod package available for rawhide is still very old.
> How do I force a akmod package rebuild ? I only have modules for
> 'open-vm-tools' and 'open-vm-tools-kmod' in CVS...
$ head open-vm-tools-kmod.spec
# buildforkernels macro hint: when you build a new version or a new release
# that contains bugfixes or other improvements then you must disable the
# "buildforkernels newest" macro for just that build; immediately after
# queuing that build enable the macro again for subsequent builds; that way
# a new akmod package will only get build when a new one is actually
%define buildforkernels newest
IOW: do s/%define buildforkernels newest/#define buildforkernels newest
and the akmods package will get build as well as new kmods. Maybe the
wording needs to be improved?
Forgot: You are not the first that gets confused. Maybe we should just
split all akmods into a seperate source package to avoid that? One could
copy the normal foo-kmod.spec file over to the foo-akmod.spec, flip a
macro and queue the rebuild. That's a bit more manual work, but more