On Sunday, August 13, 2006 at 11:47:06, David Keller wrote:
I just made my first experience with y2pmbuild and
applications and libraries. All worked fine.
Yet I would like to pack a kernel-module and later install it on my
system. Through yast online-update I managed to have kernel-184.108.40.206
installed on my box. But when I try to build the module with y2pmbuild I
get an rpm-file which is built on kernel-220.127.116.11.
My dists_common file looks like this:
# additional sources, specify with url_...
# suse here is the one from $add_sources
Don't care about the hard-coded version in the sources yet (I know how
to replace it with a more general formulation, but had no need to do it
Seemingly it is not possible to add the source suseupdate by replacing
the add_sources-tag with add_sources="suse susenonoss suseupdate". This
results in a lot of unresolved conflicts in the initialization of y2pmbuild.
Does somebody know a workaround?
This is because the update repos are in the rpm-md format which knows
nothing about file provides (like /bin/sh) but contains files that need
this. The only way i know to workaround this is to transfer them into
the yast2 format with the EXTRA_PROV file from the 10.1 repos.
Henne Vogelsang, http://hennevogel.de
"To die. In the rain. Alone."