Results 1 to 4 of 4

Thread: Suse 11.2 - Yast "parse error"

  1. #1

    Default Suse 11.2 - Yast "parse error"

    Hi,
    I have just installed Suse 11.2 32bit with KDE 4.3.1

    Each time I want to download software via yast I get the following message:

    There was an error in the repository initialization.
    Parse error.
    I also got an error, when I went to add a repository

    There were errors while restoring the repository configuration.
    Parse error.
    These errors only happen after the repository download and before the next screens. I can then go ahead and use the functions as normal.

    Any help would be greatly appreciated.

  2. #2
    google01103 NNTP User

    Default Re: Suse 11.2 - Yast "parse error"

    von shtupp wrote:

    >
    > Hi,
    > I have just installed Suse 11.2 32bit with KDE

    4.3.1
    >
    > Each time I want to download software via yast

    I get the following
    > message:
    >
    >> There was an error in the repository

    initialization.
    >> Parse error.

    >
    > I also got an error, when I went to add a

    repository
    >
    >> There were errors while restoring the

    repository configuration.
    >> Parse error.

    >
    > These errors only happen after the repository

    download and before the
    > next screens. I can then go ahead and use the

    functions as normal.
    >
    > Any help would be greatly appreciated.
    >
    >

    I get it too, just ignore it, it doesn't seem to
    have an affect on updates. Note if you update
    your repo's within yast sw-manager then the
    message doesn't show.
    --
    openSuse 11.32 x64bit, KDE4.3.3, Opera weekly

  3. #3

    Default Re: Suse 11.2 - Yast "parse error"

    Thanks. Maybe it'll get fixed at some time.

  4. #4

    Default Re: Suse 11.2 - Yast "parse error"

    I'm getting the same error message in a new a 64 bit install. I can still download and install software but the message is unsettling. In the past I've seen a reference to a simple command line command that will fix this error, but can't seem to find reference to it now? Anyone out there familiar with the fix?
    Thanks,
    Jdwilliam

Posting Permissions

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