Bug 565106 – media-sound/ncmpcpp-0.7_beta1 - In file included from bindings.cpp:24: /usr/include/boost/range/detail/any_iterator.hpp:131:15: error: ‘postfix_increment_proxy’ is not a class

• Status: RESOLVED INVALID
• Product: Gentoo Linux

[Description Oleh 2015-11-08 06:49:22 UTC]

it is really bad experience to get broken beta ebuilds, without setting a testing mask first. 07_beta1 does not build due to problems with boost headers.
0.7 branch is something i suggest not ready for daily usage.

Reproducible: Always

Steps to Reproduce:
1. emerge --sync
2. run update world command, notice a ncmpcpp beta ebuild update
3. notice a build failure of media-sound/ncmpcpp-0.7_beta1
Actual Results:  
bindings.cpp
In file included from menu.h:26:0,
                 from screen.h:24,
                 from global.h:26,
                 from bindings.cpp:24:
/usr/include/boost/range/detail/any_iterator.hpp:131:15: error: ‘postfix_increment_proxy’ is not a class template
         class postfix_increment_proxy<
               ^
/usr/include/boost/range/detail/any_iterator.hpp:176:15: error: ‘writable_postfix_increment_proxy’ is not a class template
         class writable_postfix_increment_proxy<
               ^
Makefile:596: recipe for target 'bindings.o' failed
make[2]: *** [bindings.o] Error 1
make[2]: *** Waiting for unfinished jobs....
In file included from ./menu.h:26:0,
                 from ./format.h:26,
                 from ./settings.h:32,
                 from utility/comparators.h:27,
                 from utility/comparators.cpp:22:
/usr/include/boost/range/detail/any_iterator.hpp:131:15: error: ‘postfix_increment_proxy’ is not a class template
         class postfix_increment_proxy<
               ^
/usr/include/boost/range/detail/any_iterator.hpp:176:15: error: ‘writable_postfix_increment_proxy’ is not a class template
         class writable_postfix_increment_proxy<
               ^
Makefile:617: recipe for target 'comparators.o' failed
make[2]: *** [comparators.o] Error 1
In file included from interfaces.h:24:0,
                 from actions.h:28,
                 from actions.cpp:33:
/usr/include/boost/range/detail/any_iterator.hpp:131:15: error: ‘postfix_increment_proxy’ is not a class template
         class postfix_increment_proxy<
               ^
/usr/include/boost/range/detail/any_iterator.hpp:176:15: error: ‘writable_postfix_increment_proxy’ is not a class template
         class writable_postfix_increment_proxy<
               ^
Makefile:596: recipe for target 'actions.o' failed
make[2]: *** [actions.o] Error 1
make[2]: Leaving directory '/var/tmp/portage/media-sound/ncmpcpp-0.7_beta1/work/ncmpcpp-0.7_beta1/src'
Makefile:464: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/var/tmp/portage/media-sound/ncmpcpp-0.7_beta1/work/ncmpcpp-0.7_beta1'
Makefile:375: recipe for target 'all' failed
make: *** [all] Error 2
 * ERROR: media-sound/ncmpcpp-0.7_beta1::gentoo failed (compile phase):
 *   emake failed
 * 
 * If you need support, post the output of `emerge --info '=media-sound/ncmpcpp-0.7_beta1::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=media-sound/ncmpcpp-0.7_beta1::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/media-sound/ncmpcpp-0.7_beta1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/media-sound/ncmpcpp-0.7_beta1/temp/environment'.
 * Working directory: '/var/tmp/portage/media-sound/ncmpcpp-0.7_beta1/work/ncmpcpp-0.7_beta1'
 * S: '/var/tmp/portage/media-sound/ncmpcpp-0.7_beta1/work/ncmpcpp-0.7_beta1'

Expected Results:  
mask of ncmpcpp-0.7* releases

[Comment 1 Oleh 2015-11-08 06:49:39 UTC]

Created attachment 416268 [details]
build.log

[Comment 2 Jeroen Roovers (RETIRED) 2015-11-08 07:15:44 UTC]

Please post your `emerge --info dev-libs/boost media-sound/ncmpcpp' output in a comment.

[Comment 3 Jeroen Roovers (RETIRED) 2015-11-08 07:18:04 UTC]

*** This bug has been marked as a duplicate of bug 565102 ***

[Comment 4 Jeroen Roovers (RETIRED) 2015-11-08 07:20:29 UTC]

No, Oleg, we put betas in the unstable branch and then fix bugs that people who use that branch come up with. We don't mask betas just to have nasty surprises pop up when it's time to go stable.