Hi, Am Dienstag, 12. März 2019, 16:10:25 CET schrieb Tardif, Christian:
Nope. Deleted my old project, recreated a new project (with a different project just to be sure), ^^^^^^^^^
The mistake is branching into an existing project - do not do that. Just skip the project creation and enter the name of a not existing project into the "Branch package" dialog. It'll set up the project for you, with the correct configuration. Cheers, Fabian
and branched from devel:kubic:images into it. Didn't change a line (so should be getting the exact same results as devel:kubic:images builds. But still getting the unresolvable packages issue.
-- Christian Tardif Cloud computing senior Architect Network IaaS Bell Canada
-----Original Message----- From: Fabian Vogt <fvogt@suse.de> Sent: Tuesday, March 12, 2019 10:03 AM To: Tardif, Christian <christian.tardif@bell.ca> Cc: Thorsten Kukuk <kukuk@suse.de>; opensuse-kubic@opensuse.org Subject: Re: [opensuse-kubic] MicroOS custom image build
Hi,
Am Dienstag, 12. März 2019, 14:54:00 CET schrieb Tardif, Christian:
Hi,
Restarted from scratch, and branched from devel:kubic:images. Added my required stuff but, even before that, nothing builds. It seem that it does not find any repo from which to get packages.
You branched into an already existing project, so it does not overwrite your old config. If you branch into a new project or delete the target project before branching into it, it will generate a working config.
In the .kiwi file, the only relevant info regarding package repository is that:
<repository type="rpm-md" > <source path='obsrepositories:/'/> </repository>
Which seem to me to be like..... nothing.
That means it uses the repos from the project configuration.
Cheers, Fabian
Can't seem to be able to find out any relevant info in order to fix this.
Thanks,
-- Christian Tardif Cloud computing senior Architect Network IaaS Bell Canada
-----Original Message----- From: Tardif, Christian <christian.tardif@bell.ca> Sent: Thursday, March 7, 2019 4:03 PM To: Fabian Vogt <fvogt@suse.de> Cc: Thorsten Kukuk <kukuk@suse.de>; opensuse-kubic@opensuse.org Subject: RE: [opensuse-kubic] MicroOS custom image build
Good advice. I'll take it back tomorrow morning, redoing it from scratch. Anyway, that's not a big deal just to add my tiny stuff. At the actual point, I just need to figure out how to add the repo information (since my actual status is now "unresolvable (nothing provides kiwi-filesystem:btrfs, docker, xfsprogs, .......) for the build to actually start.
-- Christian Tardif Cloud computing senior Architect
Network IaaS Bell Canada
-----Original Message----- From: Fabian Vogt <fvogt@suse.de> Sent: Thursday, March 7, 2019 1:19 PM To: Tardif, Christian <christian.tardif@bell.ca> Cc: Thorsten Kukuk <kukuk@suse.de>; opensuse-kubic@opensuse.org Subject: Re: [opensuse-kubic] MicroOS custom image build
Hi,
Am Donnerstag, 7. März 2019, 18:11:12 CET schrieb Tardif, Christian:
I minimized the kiwi file to bare minimum: Openstack and hardware, x64_86, + docker package (adapted the _multibuild file accordingly)
I personally recommend to not do this and keep the diff as small as possible. Currently any changes in the source image description would cause a merge conflict which can only be fixed manually with osc on the command line.
My project is home:tardich:Kubic, and the package name is: openSUSE-Tumbleweed-Kubic
I now have two flavors: - MicroOS-docker-OpenStack-Cloud - MicroOS-docker-hardware-x86_64
On the right pane, I see that - openSUSE-Tumbleweed-Kubic - openSUSE-Tumbleweed-Kubic:MicroOS-docker-OpenStack-Cloud - openSUSE-Tumbleweed-Kubic:MicroOS-docker-hardware-x86_64
are in an "excluded" state
I had to correct the kiwi file because of preferences version invalid (version was 15.0, where it seem to require three numbers, like 15.0.0).
That seems weird - where did you get the error message?
Still, I get no build at all, and I don't know what this means, nor where to look at to fix it... :-/
That's because you created the "openSUSE_Tumbleweed" repository manually, which defaults to building RPM packages with .spec files. To change this, set "Type: kiwi" in the project config. If you branch the package, the project configuration is set up correctly out of the box.
Your change to the kiwi file will not work as intended - the <!-- OBS-Profiles --> comment is not a list of all profiles to build separate images from, but rather a list of profiles enabled during any image build. The magic "@BUILD_FLAVOR@" string means that it builds every profile mentioned in _multibuild separately.
I branched the package and applied some minimal changes to use docker instead, as an example: https://build.opensuse.org/package/show/home:favogt:fortardich/openSUS E-Tumbleweed-Kubic
Cheers, Fabian
-- Christian Tardif Architecte principal infonuagique | Cloud computing senior Architect
Network IaaS Bell Canada 671, de la Gauchetière Ouest, suite 527 Montréal (Québec) H3B 2M8 T : 514.391.6635, C : 514.237.6332, F : 514.391.6690 Email: christian.tardif@bell.ca
-----Original Message----- From: Fabian Vogt <fvogt@suse.de> Sent: Thursday, March 7, 2019 10:50 AM To: Tardif, Christian <christian.tardif@bell.ca> Cc: Thorsten Kukuk <kukuk@suse.de>; opensuse-kubic@opensuse.org Subject: Re: [opensuse-kubic] MicroOS custom image build
Hi,
Am Donnerstag, 7. März 2019, 16:31:14 CET schrieb Tardif, Christian:
OK, got my account activated on OBS, then branched devel:kubic:images, created the repo (openSUSE-Tumbleweed, x86_64),
If you use the built-in branch functionality, the target project should be set up correctly for building already.
then trying to figure out how to glue everything together so build actually works...
It should be enough to replace the "container-runtime" namedCollection and package with a <package name="docker"/> - you could s/podman/docker/ as well, but if the name mismatch isn't bothering you, I recommend to just skip that as it keeps the diff small.
Cheers, Fabian
P.S. I have a SUSE Partner Executive coming to our office on March 13 to help out. So I I can have something working by then, I may look a little more intelligent :-D -- Christian Tardif Cloud computing senior Architect
Network IaaS Bell Canada
-----Original Message----- From: Thorsten Kukuk <kukuk@suse.de> Sent: Wednesday, March 6, 2019 2:26 PM To: Tardif, Christian <christian.tardif@bell.ca> Cc: Fabian Vogt <fvogt@suse.de>; opensuse-kubic@opensuse.org Subject: Re: [opensuse-kubic] MicroOS custom image build
On Wed, Mar 06, Tardif, Christian wrote:
This appears more complicated than I first thought.... Basically, what I did (I may be all wrong):
1) Got a machine with kiwi installed 2) Downloaded every file from there: https://build.opensuse.org/package/show/devel:kubic:images/openS US E- Tu mbleweed-Kubic?rev=14 and paced them in a directory called MicroOS
There is a much easier, simpler and faster method to build this adjusted images: 1. Create a login for build.opensuse.org 2. Branch the package into your home project, adjust it, and let the build service build the image for you, everytime there are changes. So you will have always an up-to-date image.
Thorsten
-- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-kubic+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kubic+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-kubic+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kubic+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-kubic+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kubic+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-kubic+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kubic+owner@opensuse.org