Summary: | app-crypt/monkeysphere-0.37 : * ERROR: app-crypt/monkeysphere-0.37::gentoo failed (postinst phase): | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Kristian Fiskerstrand (RETIRED) <k_f> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
app-crypt:monkeysphere-0.37:20160406-233233.log
emerge-history.txt |
Description
Toralf Förster
![]() Created attachment 429824 [details]
app-crypt:monkeysphere-0.37:20160406-233233.log
Created attachment 429826 [details]
emerge-history.txt
What do you get if you run monkeysphere-authentication setup manually ? potentially also with MONKEYSPHERE_LOG_LEVEL=debug env variable if you still don't get any output. (In reply to Kristian Fiskerstrand from comment #3) tinderbox@ms-magpie ~ $ sc amd64-kde-unstable_20160403-233402/ ms-magpie / # monkeysphere-authentication setup ms: setting up Monkeysphere authentication trust core... ms-magpie / # export MONKEYSPHERE_LOG_LEVEL=debug ms-magpie / # monkeysphere-authentication setup ms: checking authentication directory structure... ms: writing core gpg.conf... ms: writing sphere gpg.conf... ms: fixing sphere gnupg home ownership... ms: determining core key fingerprint... ms: core fingerprint: ED7C1B226D07F95BA5446C9F40E0AA4FC7BAA8DA ms: Monkeysphere authentication trust core already exists. ms: exporting core pub key to sphere keyring... ms: setting ultimate owner trust on core key in gpg_sphere... ms: # List of assigned trustvalues, created Thu 07 Apr 2016 03:08:25 PM CEST ms: # (Use "gpg --import-ownertrust" to restore them) ms: ED7C1B226D07F95BA5446C9F40E0AA4FC7BAA8DA:6: ms: checking gpg_sphere owner trust set properly... ms: checking trust model for authentication ... ms: sphere trust model: 1:3:1 (In reply to Toralf Förster from comment #4) > (In reply to Kristian Fiskerstrand from comment #3) > > tinderbox@ms-magpie ~ $ sc amd64-kde-unstable_20160403-233402/ > ok, here seems correct and command is idempotent. Can it be a hardened issue wrt directory creation or something? FWIW - *postinst* error - so it was installed despite that error : ms-magpie log # qlist -Icv monkeysphere app-crypt/monkeysphere 0.37 ms-magpie log # qlop -u -l monkeysphere Thu Apr 7 01:32:47 2016 >>> app-crypt/monkeysphere-0.37 An unmerge and merge could not reproduce the error - so I do assume, the action in comment #4 now made the way free. The package emerged fine at other images at the same system fine, so rather a temporary hickup or a USE flag issue, or ? *** Bug 583612 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 559708 *** |