https://bugzilla.novell.com/show_bug.cgi?id=886791 https://bugzilla.novell.com/show_bug.cgi?id=886791#c5 --- Comment #5 from Robert Schweikert <rschweikert@suse.com> 2014-07-11 13:23:40 UTC --- (In reply to comment #3)
Can you explain the details what is wrong with it and what the expected behavior should be ?
From a user perspective the expected behavior would be that if I include
<package name="openSUSE-build-key"/> in the image description the resulting image will have the keys setup such that "zypper in" or "zypper up" does not generate any messages about importing any keys, as long as I stick to the "official" repositories. This is not happening today. IMHO this is completely independent of the build system. Whatever keys are on the build system are only of interest while we install the packages marked as "bootstrap". After that we run the package installation inside the chroot, i.e. what will become the root of the new image. Thus, here are 2 use cases: 1.) The user wants to build an image with he keys included (my current case) and thus includes the -build-key package in the image description 2.) The user wants a system that does not have the build keys, i.e. the image user has to decide for themselves to accept repository keys or not. In this case the image builder would NOT include the -build-key package in the image description. Thus kiwi should not leave any traces of the keys. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.