On Tue, Feb 05, 2019 at 04:31:42PM +0100, Richard Brown wrote:

I wish to build a few different variants of stable:kernel-default with different config options

But trying to do it by patching things the way I thought would be right end up with builds failing:

https://build.opensuse.org/package/live_build_log/home:RBrownSUSE:branches:K...

The problem here most likely is that your modification changed visibility of some other options. Before starting the build, there is a check that make silentoldconfig/syncconfig won't add any new options. In general, the way to prevent this problem is to check that "make oldconfig" with your configuration won't ask any questions.

What is the right process for someone to take kernel:stable, branch the package, tweak the config, and get it building in their home project?

For simple changes, either doing the change using "make menuconfig" or "make menuconfig" or checking with "make oldconfig" as explained above should be the fastest way. For more complicated changes, and in particular if you want to update configs for other flavors (or architectures), starting from the git repository would be preferrable. The workflow would be - "scripts/sequence-patch.sh --fast" to expand the patches - change to $SCRATCH_AREA directory - use run_oldconfig.sh to modify the configs - change back to your clone of kernel-source git - commit your changes - use scripts/tar-up.sh to prepare a package in kernel-source/ - either copy it to your OBS project (replace the package contents with contents of kernel-source/) - or use "osc build --alternative-project ..." to build directly from kernel-source/ Michal Kubecek -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org

On 05. 02. 19, 16:31, Richard Brown wrote:

Hi,

I wish to build a few different variants of stable:kernel-default with different config options

But trying to do it by patching things the way I thought would be right end up with builds failing:

https://build.opensuse.org/package/live_build_log/home:RBrownSUSE:branches:K...

What is the right process for someone to take kernel:stable, branch the package, tweak the config, and get it building in their home project?

Besides what others write (you have to enumerate all the + reported in the failed log), I would also use config.addon.tar.bz2 instead of altering config.tar.bz2. That way you won't get conflicts in the future. Like in: https://build.suse.de/package/rdiff/home:jirislaby:stable-lockdep/kernel-source?opackage=kernel-source&oproject=Devel%3AKernel%3Astable&rev=15 regards, -- js suse labs -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org