| Summary: | mail-client/claws-mail-fancy-0.9.16 - fancy_viewer.c:1028:46: error: 'SOUP_TYPE_PROXY_RESOLVER_GNOME' undeclared | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Marius Glauser <marius+bug> |
| Component: | Current packages | Assignee: | Christian Faulhammer (RETIRED) <fauli> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | net-mail+disabled |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | emerge --info '=mail-client/claws-mail-fancy-0.9.16' | ||
Are libsoup and libsoup-gnome installed? Does this happen with claws-mail-fancy-0.9.17? And have you run revdep-rebuild? Sorry, my bad. I had keyworded mail-client/claws-mail ~amd64 but not mail-client/claws-mail-fancy. Isn't there a possibility to catch such collisions in the ebuild? This would prevent other dumb users to fall into this trap :-) (In reply to comment #2) > Sorry, my bad. I had keyworded mail-client/claws-mail ~amd64 but not > mail-client/claws-mail-fancy. > > Isn't there a possibility to catch such collisions in the ebuild? This would > prevent other dumb users to fall into this trap :-) Most of the time the old plugin still works with newer Claws version but not vice versa. With 22 plugins to test for every bump I try to avoid this hassle. But thanks for the notice. |
Created attachment 330536 [details] emerge --info '=mail-client/claws-mail-fancy-0.9.16' Compilation of claws-mail-fancy-0.9.16 fails with fancy_viewer.c: In function 'fancy_viewer_create': fancy_viewer.c:1026:17: error: 'FancyPrefs' has no member named 'enable_gnome_proxy' fancy_viewer.c:1028:46: error: 'SOUP_TYPE_PROXY_RESOLVER_GNOME' undeclared (first use in this function) fancy_viewer.c:1028:46: note: each undeclared identifier is reported only once for each function it appears in