Comment # 17 on bug 1175119 from Nicolas Nattermann

(In reply to Michal Filka from comment #16)
> During installation, YaST is searching for available "products" in the
> installation source. In your case, Yalwa client was reported as a product
> (in particular there were two - differs in arch). However, the repository
> with the client doesn't fulfill requirements for "product" repository and
> YaST crashes because of that.

Thank you for this clear explanation, I now get what overall this is about.

> 2) your use case. You want to achieve *something* what I don't know, and it
> seems you're doing it wrong at least for the current OpenSUSE release. If
> you precisely describe what you want to achieve, I can try to help you or
> contact you with someone else who could be able to.

What we are doing with this extra yalwa-client repository, is purely internal
to our company desktop + laptop installations, have an additional package
source for various internally curated packages. These cover various needs we
have, partly configuration management, some rather dependency management
(drawing in other packages, also from the base openSUSE repos, as rpm
dependencies), and some installing internal scripts. very rarely we also
override base system packages with newer versions.

None of that has to do with any external productization. It's really just our
internal way to customize our installs in various ways. We are doing the same
(with a separate repository) for our production host + vm installs, and have
been doing that since 11.4 times.

The basic structure - metadata structure I mean - I did create back then, maybe
9 years ago, from some documentation I found on your web pages, and a bit of
guessing from existing repositories. The terminology "product", the line in
metadata where we put "Yalwa_Client" then, is just something I found / got that
way, not something that is of huge importance to us by itself.

For the sake of clarity, I will attach the script we use for the metadata
recreation / signing, as we've been doing it for all these years. 

Thank you for the continued willingness to help us with this! Very appreciated!

all the best
  Patrick Schaaf