Hello, You're receiving this canned (template-based) bug report because I found a problem with a package during my tinderbox run. The package in question is running automake (and most likely other autotools) during compile phase by maintainer-mode. You can see in my blog post in the URL field why that's a problem, and how to address the issue, but in general, you don't want maintainer-mode rebuild during compile phase, especially since it can cause multiple run of econf. The causes of maintainer-mode rebuild are various, but most likely it's because of a patch that changes Makefile.am or configure.ac/in and don't rebuild autotools properly. The way to fix this is almost always to inherit autotools eclass and run eautomake/eautoreconf (as needed; eautoconf should only be used when automake is not involved, which is not the case here) during src_unpack phase. Thanks, Diego
Created attachment 179248 [details] Build log
Created attachment 180470 [details, diff] knetworkmanager-0.2.2_p20080528.ebuild update to fix the issue reported by Diego The attached diff should fix the issue reported by Diego.
If knetworkmanager uses KDE's admin/ directory that's the wrong fix. The correct fix would be rm -f "${S}/configure"
Now that networkmanagere-0.7 has been stabilized all the knetworkmanager [kde3] are going to have problems... Can you please review and integrate the fix?
