| Summary: | =dev-libs/libstroke-0.5.1 needs fix for WANT_AUTOCONF setting | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | DEMAINE Benoît-Pierre, aka DoubleHP <dhp_gentoo> |
| Component: | [OLD] Unspecified | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | VERIFIED FIXED | ||
| Severity: | normal | CC: | n-roeser |
| Priority: | High | ||
| Version: | 2006.1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 192923 | ||
| Attachments: |
/tmp/emerge--info
/tmp/esync-log /tmp/emerge-world-log_1 |
||
Created attachment 131224 [details]
/tmp/emerge--info
Created attachment 131225 [details]
/tmp/esync-log
previously, I was said that maybe my local /usr/portage/eclass/autotools.eclass was broken; after this update, I am now said that maybe the mirror is broken.
Created attachment 131227 [details] /tmp/emerge-world-log_1 New output of emerge world, after esync, that slightly different. I am now said that this but may also be dup of bug #192923 ? *** This bug has been marked as a duplicate of bug 192923 *** The WANT_AUTOCONF setting for libstroke needs to be fixed, that’s all. I suggest you change the following fields on this bug (I’d have done it myself, but I don’t have the permissions to do so): Subject: =dev-libs/libstroke-0.5.1 needs fix for WANT_AUTOCONF setting Blocking: bug 192923. I dont want to block 192923 ; I think dup is quiet better, cause fixing AUTOCONF is very likely to fix this. Nico, you can also have a check at bug #192927 bug #192951 bug #192947 bug #192903 bug #192894 Not the autotools.eclass is broken, but the WANT_AUTOCONF setting in libstroke-0.5.1.ebuild is. Also see bug 192892 comment 3. This is why I made all those bugs block the “meta-bug”, bug 192923. The eclass files need to be fixed individually; vapier’s change to the autotools.eclass simply added a check, so that buggy WANT_AUTOCONF settings become visible. Reopen bug blocks bug 192923 Fixed, thanks for reporting it. Denis. |
This made me very crossed, not because it bugs, but, because emerge does not indicate any possible way to help fixing; see this: root@moon_gen_2:/etc# emerge -DaNuv world These are the packages that would be merged, in order: Calculating world dependencies / emerge: there are no ebuilds to satisfy ">=sys-devel/autoconf-FAIL". (dependency required by "dev-libs/libstroke-0.5.1" [installed]) !!! Problem resolving dependencies for sci-electronics/geda-suite !!! Depgraph creation failed. root@moon_gen_2:/etc# emerge -DaNuv dev-libs/libstroke-0.5.1 These are the packages that would be merged, in order: Calculating dependencies | !!! 'dev-libs/libstroke-0.5.1' is not a valid package atom. !!! Please check ebuild(5) for full details. !!! (Did you specify a version but forget to prefix with '='?) root@moon_gen_2:/etc# so, from this, we cant really know if Geda should be updated, and, -pvt does not say why Geda introduces dev-libs/libstroke I had to ask help to known how to be clever: root@moon_gen_2:/etc# emerge -vp =dev-libs/libstroke-0.5.1 These are the packages that would be merged, in order: Calculating dependencies / !!! Invalid or corrupt dependency specification: invalid atom: '>=sys-devel/autoconf-FAIL' ('ebuild', '/', 'dev-libs/libstroke-0.5.1', 'merge') x11-proto/xproto x11-libs/libX11 =sys-devel/automake-1.4* >=sys-devel/autoconf-FAIL sys-devel/libtool This package can not be installed. Please notify the 'dev-libs/libstroke-0.5.1' package maintainer about this problem. thus this report. root@moon_gen_2:/etc# esearch libstroke [ Results for search key : libstroke ] [ Applications found : 1 ] * dev-libs/libstroke Latest version available: 0.5.1 Latest version installed: 0.5.1 Size of downloaded files: [no/bad digest] Homepage: http://www.etla.net/libstroke/ Description: A Stroke and Gesture recognition Library License: GPL-2 so, I can at last see that this lib is not even going to be updated; maybe remerge was forced due to -N ? no way to know. Above the libstroke problem, I really think this point us to an emerge problem. So, Maybe this is in fact dup of something similar to bug #175808 ? I will esync, and confirm, or mark CANTREPRO. Still, I wanted BTS to keep track of this problem.