Please reopen bug 245243 as unresolved until you take the buggy sandbox out of stable and put a non-buggy one in stable. > sandbox 1.3.0 introduces few regressions (one with rsync at least) an it should > stay masked as 1.3.1 already fixes some it's problems - so it's necessary to > wait for 1.3.1 to arrive in glory > I got the error: -- Performing Test HAVE_GPG_ERR_SOURCE_KLEO - Success -- Performing Test HAVE_ASSUAN_SOCK_GET_NONCE terminate called after throwing an instance of 'std::out_of_range' what(): basic_string::erase /var/tmp/paludis/kde-base-mimelib-4.2.0/temp/loadsaveenv: line 1407: 29120 Aborted cmake -C "${TMPDIR}/gentoo_common_config.cmake" ${cmakeargs} "${S}" !!! ERROR in kde-base/mimelib-4.2.0: !!! In cmake-utils_src_configureout at line 1414 !!! Cmake failed It took a while to find this bug since it was marked closed. Well, it's still happening. Perhaps I ought to file a new bug report? Building with ~amd64 for sandbox worked: 1236004175: starting install of targets sys-apps/sandbox 1236004175: starting install of package sys-apps/sandbox-1.3.8:0::gentoo (1 of 1) 1236004243: starting clean of package sys-apps/sandbox-1.2.18.1-r2:0::installed (1 of 1) 1236004244: finished clean of package sys-apps/sandbox-1.2.18.1-r2:0::installed (1 of 1) 1236004248: finished install of package sys-apps/sandbox-1.3.8:0::gentoo (1 of 1) 1236004249: finished install of targets sys-apps/sandbox 1236004306: starting install of targets kde-base/kde-meta:4.2 1236004306: starting install of package kde-base/mimelib-4.2.0:4.2::gentoo (1 of 12) 1236004348: finished install of package kde-base/mimelib-4.2.0:4.2::gentoo (1 of 12) 1236004348: starting install of package kde-base/kmailcvt-4.2.0:4.2::gentoo (2 of 12) So, I need to submit a new bug report since it is not yet fixed. Reproducible: Always Steps to Reproduce:
Per status update on bug 245243, closing this bug as fixed. Kde eclass now pulls in sandbox-1.3+ You know, this is why devs will often tell you that going 100% ~arch is less painful than going 50% ~arch. Thank you for taking the effort, though, as this will help when kde-4.x goes stable.
