Upgrading dovecot to 2.1.3 fails when clucene has been upgraded to 2.3.3.4-r2 with the following: In file included from /usr/include/CLucene/StdHeader.h:20:0, from /usr/include/CLucene.h:11, from lucene-wrapper.cc:23: /usr/include/CLucene/SharedHeader.h:18:36: fatal error: CLucene/clucene-config.h: No such file or directory compilation terminated. make[4]: *** [lucene-wrapper.lo] Error 1 make[4]: *** Waiting for unfinished jobs.... make[4]: Leaving directory `/var/tmp/portage/net-mail/dovecot-2.1.3/work/dovecot-2.1.3/src/plugins/fts-lucene' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/var/tmp/portage/net-mail/dovecot-2.1.3/work/dovecot-2.1.3/src/plugins' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/net-mail/dovecot-2.1.3/work/dovecot-2.1.3/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/net-mail/dovecot-2.1.3/work/dovecot-2.1.3' make: *** [all] Error 2 * ERROR: net-mail/dovecot-2.1.3 failed (compile phase): * emake failed Reproducible: Always Steps to Reproduce: 1. Upgrade clucene to 2.3.3.4-r2 2. Attempt to upgrade dovecot to 2.1.3 Actual Results: Update fails with the above error Expected Results: Update should succeed Thanks to Alan McKinnon for tracking it down (from our email exchange on the gentoo-user list): >> When I tried updating dovecot, it *successfully* emerged the clucene >> update first (it was already installed), then the dovecot build >> failed with the error... > It's quite simple as it turns out. dev-cpp/clucene changed the name of > > /usr/include/CLucene/clucene-config.h > > to > > /usr/include/CLucene/CLConfig.h
@Reporter: This build failure is net-mail/dovecot related. Please do not assign bugs by yourself if you are not 100% sure.
OP seems to be correct. Bump by scarabeus from clucene-2.3.3.4-r1 to clucene-2.3.3.4-r2 broke dovecot. Why are you changing the installed header files in the first place? And if you really have to, installing a compatibility symlink would have been nice.
The bug actually is in the dovecot which does not read and respect data from the pkgconfig file. Anyway the header has nothing to do in libdir and it was oversight so moving it away back where it belongs. This also fixes the dovecot.
(In reply to comment #1) > @Reporter: This build failure is net-mail/dovecot related. Please do not > assign bugs by yourself if you are not 100% sure. ? When you say 'assign', do you mean which component? If so, then I'm sorely tempted to tell you what you can go do with yourself... When I report a bug, I *have* to choose a component, it is not an option. So, yes, I chose the one that seemed the best one to me at the time. If you don't like it and you don't want us reporters to do our best to assign a component, then don't *force* us to try to figure out which one is the most appropriate and then be rude and condescending when telling us we got it wrong, rather don't even *ask* us to pick one, and one of *you* guys who are all-knowing can assign it afterwards. But, that may not be a very good solution either since... You complain about *me* picking the wrong component, tell me it is net-mail/dovecot related (which I obviously already know, but net-mail/dovecot is *not* a component choice, so the 'server' component seemed the closest, and *yes* I clicked each one and read the description before picking it), then *you* change it to the *KDE* component? This has *nothing* to do with KDE, so I just changed it *back* to the server component...
(In reply to comment #3) > The bug actually is in the dovecot which does not read and respect data from > the pkgconfig file. > > Anyway the header has nothing to do in libdir and it was oversight so moving > it away back where it belongs. This also fixes the dovecot. Thanks for fixing it Tomas, but when you say that the bug is actually in dovecot - should I open a bug there to fix this permanently? If so, I'll be happy to, but it would be helpful if you would give me the exact words I'll need to use to report it to Timo...
