Results 1 to 4 of 4

Thread: [SuMa3.2] Where does System State Packages come from ?

Hybrid View

  1. #1

    [SuMa3.2] Where does System State Packages come from ?

    Hi, i have a list of Software Packages in SuMa3.2 under

    There is a list of Software to install and one Package is wrong and cannot be installed.
    I want to remove this Packages cause no autoyast install is sucessful with this wrong entry.
    Where does this request come from ?
    Regards OL

  2. #2

    Re: [SuMa3.2] Where does System State Packages come from ?


    It appears that in the past few days you have not received a response to your
    posting. That concerns us, and has triggered this automated reply.

    These forums are peer-to-peer, best effort, volunteer run and that if your issue
    is urgent or not getting a response, you might try one of the following options:

    - Visit and search the knowledgebase and/or check all
    the other support options available.
    - Open a service request:
    - You could also try posting your message again. Make sure it is posted in the
    correct newsgroup. (

    Be sure to read the forum FAQ about what to expect in the way of responses:

    If this is a reply to a duplicate posting or otherwise posted in error, please
    ignore and accept our apologies and rest assured we will issue a stern reprimand
    to our posting bot..

    Good luck!

    Your SUSE Forums Team

  3. Re: [SuMa3.2] Where does System State Packages come from ?

    I think this is a "release" package. When you add a software channel we look for packages in the channel which contains a "product".
    These packages were added to the package states automatically. This happens to correctly display results from the subscription-matcher.

    We take "provides" of other release packages into account, but we had some bugs there in the past which should be fixed.
    But a fix only pevent these things in future. If a state contains already a wrong package it will not be fixed automatically.

  4. Re: [SuMa3.2] Where does System State Packages come from ?

    This is actually a salt state related to the packages.
    We had an issue with sles-release and the countepart for SLES for SAP and this prevented applying high states , or even dist upgrade.
    The workaround is to set "sles-release" for sap-based SLES to "unmanaged".

    This kind of issue should be fixed in the updates, but we haven't updated yet ...


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts