Am 21.08.2014 14:11, schrieb Matwey V. Kornilov: > 2014-08-21 16:07 GMT+04:00 Guillaume Gardet <[email protected]>: >> The thing is we must be able to test -rc versions. Otherwise stable (non >> tested) versions may not work. >> The easiest way is to build JeOS images using -rc images. To me, it was the >> purpose of Factory, but now Factory is becoming a rolling (stable) release, >> so we should have another project for our tests (devel:ARM:Factory for >> example, but which build JeOS images). > > The same issue is with kernel. We need JeOS images with kernel -rc for > testing.
Hm, take a look at https://build.opensuse.org/monitor - we're really low on armv7l build power. Last night we had six build hosts, today ten with 22 worker VMs. People branching kernel package add to that problem. (I just asked Bamvor to drop a Kernel:stable branch with no diff.) We did not manage to get both kernel-default and kernel-lpae built before the next Kernel:HEAD update. (Which possibly is why they didn't get published.) So not sure how many JeOS combinations of kernel and U-Boot we can realistically build concurrently. Once we have a working JeOS for a board, people could just update to Kernel:HEAD from there themselves. For new boards where the kernel does not yet boot we simply can't create new JeOS images outside Contrib:* today. For U-Boot testing I agree it would make sense to have images built. Dropping the downstream Raspberry Pi kernel and merging :upstream into Contrib:RaspberryPi would seem like a nice cleanup btw. Requires the fixed kernel to get built, of course. Regards, Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
