Results 1 to 7 of 7

Thread: Problems with the key in hardware repository (OBS)

  1. #1

    Default Problems with the key in hardware repository (OBS)

    Hello,

    Every time I do "zypper up", I receive this message:

    Code:
    New repository or package signing key received:
    
      Repository:       hardware                                          
      Key Name:         hardware OBS Project <hardware@build.opensuse.org>
      Key Fingerprint:  E96C496E 4E77C159 C2FCA053 062F9FD4 D6D11CE4      
      Key Created:      Tue 16 Sep 2014 09:17:18 AM CST                   
      Key Expires:      Thu 24 Nov 2016 09:17:17 AM CST                   
      Rpm Name:         gpg-pubkey-d6d11ce4-5418547e                      
    
    
    Do you want to reject the key, trust temporarily, or trust always? [r/t/a/? shows all options] (r):
    I choose "a" (trust always) every time but yast doesn't recognize this and ask me again when I restart the computer.

    Nevertheless, when I accept the key, I can upgrade normally the system.

    The thing here is why yast is always asking me for a "trusted key"?

    I'm with 13.2 in 64 bits.

    Thanks for your assistance.

  2. #2

    Default Re: Problems with the key in hardware repository (OBS)

    Hi,

    i am having the same problem on opensuse tumbleweed. It is pretty annoying. Did you manage to fix this problem?
    What could i try to solve it?

    pepe

  3. #3
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    26,527
    Blog Entries
    15

    Default Re: Problems with the key in hardware repository (OBS)

    Hi
    Rebuild the rpm database and see if that helps;
    Code:
    rpm --rebuilddb
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  4. #4
    Join Date
    Sep 2008
    Posts
    2,997

    Default Re: Problems with the key in hardware repository (OBS)

    this could be a tw zypper bug you should check bugzilla.opensuse.org to see if it was reported if not report it.

  5. #5

    Default Re: Problems with the key in hardware repository (OBS)

    Hi,


    Quote Originally Posted by malcolmlewis View Post
    Code:
    rpm --rebuilddb
    this helped! Thank you.

    If i get the problem again i will create a bug report, but for now the problem may have occurred due to some update/upgrades.

    pepe

  6. #6
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    26,527
    Blog Entries
    15

    Default Re: Problems with the key in hardware repository (OBS)

    On Sun 28 Feb 2016 08:26:01 PM CST, oopepe wrote:

    Hi,


    malcolmlewis;2756303 Wrote:
    >
    > >

    Code:
    --------------------
    > >

    > rpm --rebuilddb
    >

    --------------------
    > >


    this helped! Thank you.

    If i get the problem again i will create a bug report, but for now the
    problem may have occurred due to some update/upgrades.

    pepe


    Hi
    If you now pop into YaST -> Software Repositories and click on the GPG
    Keys button, I'm guessing there are duplicates (and probably an old out
    of date one for hardware) that need to be deleted

    --
    Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
    SUSE Linux Enterprise Desktop 12 SP1|GNOME 3.10.4|3.12.53-60.30-default
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!


  7. #7
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    26,527
    Blog Entries
    15

    Default Re: Problems with the key in hardware repository (OBS)

    On Sun 28 Feb 2016 08:26:01 PM CST, oopepe wrote:

    Hi,


    malcolmlewis;2756303 Wrote:
    >
    > >

    Code:
    --------------------
    > >

    > rpm --rebuilddb
    >

    --------------------
    > >


    this helped! Thank you.

    If i get the problem again i will create a bug report, but for now the
    problem may have occurred due to some update/upgrades.

    pepe


    Hi
    If you now pop into YaST -> Software Repositories and click on the GPG
    Keys button, I'm guessing there are duplicates (and probably an old out
    of date one for hardware) that need to be deleted

    --
    Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
    SUSE Linux Enterprise Desktop 12 SP1|GNOME 3.10.4|3.12.53-60.30-default
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!


Posting Permissions

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