On Monday 03 August 2015 20.07:10 Jiri Slaby wrote:
On 08/03/2015, 05:48 PM, Bruno Friedmann wrote:
Did I miss something, or what is the reason to not have anymore kernel-obs-build build for standard target ?
Both obs kernel packages were moved to QA because they are not needed for standard users.
thanks,
Well in my case having kernel-stable offering kernel-obs-build was really cool.
Why exactly? That kernel is only used to be booted on the OBS build machines. Which is the same when we use osc build, locally for creating package in VM (like kvm etc) The big advantage I also see is the equality between package build locally and on obs.
Otherwise, I've to apply patches to remove all kind of lvm and luks from my own initrd :-)
Hmm, what patches? I have no luks or lvm in my initrd?
Let me trying to better describe the case: My laptop is under cryptsetup and lvm, if I create a initrd (sorry still under 13.1 so no proper dracut) with the command suggested by osc build I got an initrd with virtio inside but also all detected module like ( luks,lvm and so on) with the help of the small attached script, I was able to recreate an adapted initrd.virtio But I would call that "ugly hack" .... Having kernel-obs-build in k:s allow me (others) to have the kernel used by obs to build locally packages without adding yet-another-repository ;-))
and thus osc build with the right configuration was really easy to play with and build packages.
I am still missing the point. What use case do you have? I have a feeling that you do something really wrong.
As we want to make life easy for contributors (aka developers) I would still propose to have it under k:s
When it is shown the packages are needed for users, no problem to switch the publish flag.
thanks,
Thanks for your considerations. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Board, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot