| Summary: | app-crypt/pinentry misses dependency on app-crypt/gcr | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Ole Christensen <Ole.Christensen> |
| Component: | Current packages | Assignee: | Kristian Fiskerstrand (RETIRED) <k_f> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=570512 https://bugs.gentoo.org/show_bug.cgi?id=589742 |
||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | Portage log file with error messages | ||
|
Description
Ole Christensen
2015-09-13 08:01:31 UTC
Same here. Manually upgrading gcr from 3.14 to 3.16 solved the missing dependency issue on pinentry gcry_* functions are libgcrypt, did you happen to upgrade libgcrypt while upgrading gcr? Created attachment 412264 [details]
Portage log file with error messages
The problem starts in line 239
Well, this is what I did (from my bash history): equery belongs /usr/lib64/libgcr-base-3.so emerge -vba1 app-crypt/gcr Afterwards, emerge -vba --update --deep --newuse --with-bdeps=y @world went fine. Hope that helps. Sorry, if my original report was somehow too unspecific. (In reply to Kristian Fiskerstrand from comment #2) > gcry_* functions are libgcrypt, did you happen to upgrade libgcrypt while > upgrading gcr? Not while upgrading gcr. However when pinentry failed, I reemerged libgcrypt first (which didn't solve the issue). From my elog history, I get: 2015-09-13 10:20 libgcrypt 1.5.4-r1 ↣ 1.6.3-r4 == (I guess I made a world update on the 13th that I continued on the 16th) 2015-09-16 17:37 pinentry 0.9.0 ↣ 0.9.5 (eerror) == 2015-09-18 11:41 libgcrypt 1.6.3-r4 reemerged manually 2015-09-18 11:57 pinentry 0.9.0 ↣ 0.9.5 (eerror) 2015-09-18 12:00 gcr 3.14.0 ↣ 3.16.0 2015-09-18 12:01 pinentry 0.9.0 ↣ 0.9.5 (ok) However, I didn't keep the log. I could downgrade and retry if necessary. Fixed in pinentry-0.9.6-r3 |