Closed Bug 932923 Opened 11 years ago Closed 11 years ago

repo init fails with broken trust chain

Categories

(Firefox OS Graveyard :: General, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: rillian, Unassigned)

Details

In a fresh checkout of https://github.com/mozilla-b2g/B2G, config.sh fails with: object 12fd10c20115046dcd2fbe468a45e566f38ffbc9 type commit tag v1.12.7 tagger Conley Owens <cco3@android.com> 1381959964 -0700 repo 1.12.7 gpg: Signature made Wed 16 Oct 2013 02:46:04 PM PDT using RSA key ID 692B382C gpg: Can't check signature: public key not found error: could not verify the tag 'v1.12.7' Is seems that 'repo init' is failing because the upstream repo tag is signed with a key our copy does not trust.
This is weird; our copy of repo is updated to include the new key. Ok. the problem was I had ~/.repoconfig/keyring-version with '1.2' but the key hadn't actually been imported into that gnupg config. Maybe some other repo invocation updated it incorrectly? I'm not sure what happened; commit bc030847 in https://gerrit.googlesource.com/git-repo updates both the maintainer key and the keyring version. Removing ~/.repoconfig (or changing the stored version in keyring-version) resolved the issue.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.