Hello, Am Montag, 10. Oktober 2016, 13:06:14 CET schrieb Theo Chatzimichos:
On Mon, Oct 10, 2016 at 11:20:24AM +0200, Theo Chatzimichos wrote:
On Mon, Oct 10, 2016 at 12:48:25AM +0200, Christian Boltz wrote:
42.1 is terribly old ;-) - what about using 42.2 for new VMs? I know 42.2 is still in beta, but that shouldn't stop us from using it already ;-) [1]
There was a reason I created 42.1: I wanted to make sure that the packages from the update channel are preferred. Now that I made sure that this behaviour is working fine, I can create the 42.2 beta as well for sure.
42.2 fails to build:
[ 136s] Oct-10 10:35:49 <3> : Could not find valid boot image description for'oemboot/suse-leap42.2'. [ 136s] Oct-10 10:35:49 <3> : The required boot image description: 'oemboot/suse-leap42.2' for the selected build type: 'oem' does not exist.
Nice :-/
https://build.opensuse.org/package/live_build_log/openSUSE:infrastruct ure:Images:openSUSE_Leap_42.2/jeos/images/x86_64
Any update on this (besides "it still fails")? Having working 42.2 images would be nice, so - did you open a bugreport and/or ask the responsible maintainer about this problem? Regards, Christian Boltz -- install by booting the rescue-cd, partition your system manually, then use the obs build script to populate the target file sytem, configure everything by hand and reboot afterwards. But it's a bit tedious to do so and if I'd file a droprequest for yast2-installation, I'm quite sure many people would be unhappy. [Stefan Seyfried in opensuse-factory] -- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org