Results 1 to 7 of 7

Thread: repo signatures not stored?

  1. #1

    Question repo signatures not stored?

    Hi all,

    using OpenSUSE 13.2

    I'm prompted like this:



    So, I click 'Yes', enter my password and all seems OK.

    After a reboot, the same thing happens. It looks like my willingness to trust this (and other) repos is not being recorded.

    How do I fix this?

    Thank you.

  2. #2

    Default Re: repo signatures not stored?

    Quote Originally Posted by CheapDrunk View Post
    Hi all,

    using OpenSUSE 13.2

    I'm prompted like this:



    So, I click 'Yes', enter my password and all seems OK.

    After a reboot, the same thing happens. It looks like my willingness to trust this (and other) repos is not being recorded.
    I've seen that as well a few times in the recent past, and I do remember a bug report about it.

    Unlikely to be fixed for 13.2 any more though (if it's a bug in the package management), as 13.2 is nearly end-of-life.

    How do I fix this?
    Running "sudo zypper ref" and accepting the signature there should help.
    Last edited by wolfi323; 11-Jan-2017 at 10:45.

  3. #3

    Thumbs up Re: repo signatures not stored?

    Hi and thanks for your fast reply!

    Quote Originally Posted by wolfi323 View Post
    Unlikely to be fixed for 13.2 any more though (if it's a bug in the package management), as 13.2 is nearly end-of-life.
    Which means I have a problem. I can't get 42.1 to run, so I'll probably have to find another distro.


    Quote Originally Posted by wolfi323 View Post
    Running "sudo zypper ref" and accepting the signature there should help.
    I think that has fixed it. I selected 'always' trust for each repo, then rebooted. The autoupdate thingy ran and didn't show the screen above.

    Thank you!

  4. #4

    Default Re: repo signatures not stored?

    Quote Originally Posted by CheapDrunk View Post
    Which means I have a problem. I can't get 42.1 to run, so I'll probably have to find another distro.
    Well, Leap 42.2 has been released two months ago, maybe try that?

    Strange problem you have there though.

    Normally Plasma5 should work, with the proprietary driver at least (nouveau does and did have its share of problems depending on the exact graphics card, that likely are more exposed by newer software like Plasma5).
    Sorry, but I missed that thread so far.

    Maybe something went wrong with the nvidia installation?
    Should be fixable then.

    I think that has fixed it. I selected 'always' trust for each repo, then rebooted. The autoupdate thingy ran and didn't show the screen above.

    Thank you!
    Your welcome.

  5. #5

    Default Re: repo signatures not stored?

    Quote Originally Posted by wolfi323 View Post
    Well, Leap 42.2 has been released two months ago, maybe try that?
    I'll try it out this weekend.

    But it seems I spoke too-soon about the repo trust issue being fixed. It's back to prompting me as shown in the screencap.

  6. #6

    Default Re: repo signatures not stored?

    Quote Originally Posted by CheapDrunk View Post
    But it seems I spoke too-soon about the repo trust issue being fixed. It's back to prompting me as shown in the screencap.
    It might also be a problem with that particular repo.
    Maybe the repo's signature has indeed changed again?

    Personally I had that problem with some specific repos only, but since running "zypper ref" I haven't encountered that again.
    And that was two months ago or something like that.

  7. #7
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    15,765

    Default Re: repo signatures not stored?

    With 13.2 going end of life things may be changing. Like some may be moving to som backup long term storage site thus the need to change certs

Posting Permissions

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