clawsmail ftbfs with gtk+-2.13
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Claws Mail |
Invalid
|
Medium
|
|||
GTK+ |
Fix Released
|
Low
|
|||
claws-mail (Gentoo Linux) |
Invalid
|
Medium
|
|||
claws-mail (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
gtk+2.0 (Ubuntu) |
Invalid
|
Low
|
Unassigned |
Bug Description
Binary package hint: claws-mail
claws-mail fails to build with gtk+-2.13:
x86_64-
In file included from /usr/include/
/usr/include/
/usr/include/
/usr/include/
/usr/include/
make[6]: *** [select-keys.lo] Error 1
make[6]: Leaving directory `/tmp/buildd/
make[5]: *** [all-recursive] Error 1
make[5]: Leaving directory `/tmp/buildd/
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/tmp/buildd/
make[3]: *** [all] Error 2
make[3]: Leaving directory `/tmp/buildd/
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/tmp/buildd/
make[1]: *** [all] Error 2
make[1]: Leaving directory `/tmp/buildd/
make: *** [build-stamp] Error 2
dpkg-buildpackage: failure: debian/rules build gave error exit status 2
pbuilder: Failed autobuilding of package
This can be solved with the simple patch attached.
Note however, that this has been also discussed upstream:
http://
Their conclusion is that the bug is on libgtk2.0 not in clawsmail.
Related branches
Changed in claws-mail: | |
status: | Unknown → Invalid |
status: | Unknown → Invalid |
Changed in gtk: | |
status: | Unknown → New |
Changed in gtk: | |
status: | New → Confirmed |
Changed in gtk+2.0: | |
assignee: | nobody → desktop-bugs |
tags: | added: patch |
Changed in gtk: | |
status: | Confirmed → Invalid |
Changed in gtk+2.0 (Ubuntu): | |
assignee: | Ubuntu Desktop Bugs (desktop-bugs) → nobody |
Changed in gtk: | |
importance: | Unknown → Low |
status: | Invalid → Expired |
Changed in claws-mail (Gentoo Linux): | |
importance: | Unknown → Medium |
Changed in claws-mail: | |
importance: | Unknown → Medium |
Changed in gtk: | |
status: | Expired → Confirmed |
Changed in gtk: | |
status: | Confirmed → Fix Released |
This is also the subject of bug 238223.