100%[==========================================>] 4,216,229 622.85K/s ETA 00:00 01:52:31 (360.39 KB/s) - `/usr/portage/distfiles/knoda-0.7.4.tar.bz2' saved [4216229/4216229] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking knoda-0.7.4.tar.bz2 ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking knoda-0.7.4.tar.bz2 to /tmp/portage/knoda-0.7.4-r1/work * Applying knoda-0.7.4-makefile.patch ... [ ok ] *** YOU'RE USING autoconf (GNU Autoconf) 2.60. *** KDE requires autoconf 2.53 or newer make: *** [cvs] Error 1 !!! ERROR: dev-db/knoda-0.7.4-r1 failed. Call stack: ebuild.sh, line 1546: Called dyn_unpack ebuild.sh, line 708: Called src_unpack knoda-0.7.4-r1.ebuild, line 27: Called die !!! (no error message) !!! If you need support, post the topmost build error, and the call stack if relevant.
Kindly review http://bugs.gentoo.org/page.cgi?id=fields.html#bug_severity
Same here
I think this is something what you want to check: https://bugs.gentoo.org/show_bug.cgi?id=154816 Give us some time :) Cheers, Przemek
(In reply to comment #3) > I think this is something what you want to check: > https://bugs.gentoo.org/show_bug.cgi?id=154816 > > Give us some time :) > > Cheers, > Przemek > :-) The problem with KDevelop had a work around (see bug 154816) and i applied it to my installation. But it is not clear for me how it is related to KNoda? Is there something i can do? Thanks
(In reply to comment #4) > (In reply to comment #3) > > I think this is something what you want to check: > > https://bugs.gentoo.org/show_bug.cgi?id=154816 > > > > Give us some time :) > > > > Cheers, > > Przemek > > > > :-) The problem with KDevelop had a work around (see bug 154816) and i applied > it to my installation. > But it is not clear for me how it is related to KNoda? Is there something i can > do? > Thanks A quick fix is to make a patch for knoda's configure script. Cheers, Przemek
No. The fix is to update the admindir.
Actually the fix was also simpler, just leave the autotools re-run to the eclass as for every other package, the eclass take care of updating the autotools checks.
(In reply to comment #7) > Actually the fix was also simpler, just leave the autotools re-run to the > eclass as for every other package, the eclass take care of updating the > autotools checks. > I dont know how to do that : can you give me some more hints about how to do that?
(In reply to comment #7) > Actually the fix was also simpler, just leave the autotools re-run to the > eclass as for every other package, the eclass take care of updating the > autotools checks. Is this means that this should be fixed now, for every package with broken configure script?
It was fixed already for every package that uses kde.eclass correctly. You should _never_ run Makefile.common on the ebuild itself, when using kde.eclass, but rather remove the configure file and leave to kde.eclass the handling of that. Now it's fixed for knoda in the tree.
(In reply to comment #10) > It was fixed already for every package that uses kde.eclass correctly. > You should _never_ run Makefile.common on the ebuild itself, when using > kde.eclass, but rather remove the configure file and leave to kde.eclass the > handling of that. Ahhh... Thx for info, Diego. Cheers, Przemek
(In reply to comment #11) > (In reply to comment #10) > > It was fixed already for every package that uses kde.eclass correctly. > > You should _never_ run Makefile.common on the ebuild itself, when using > > kde.eclass, but rather remove the configure file and leave to kde.eclass the > > handling of that. > > Ahhh... Thx for info, Diego. > > Cheers, > Przemek > (In reply to comment #10) > It was fixed already for every package that uses kde.eclass correctly. > You should _never_ run Makefile.common on the ebuild itself, when using > kde.eclass, but rather remove the configure file and leave to kde.eclass the > handling of that. > > Now it's fixed for knoda in the tree. > Thanks, but there is a strange thing now : - emerging from unstable (~x86) works. Hurra! - emerging from stable version (x86) doesnt still work (same pb as described in the bug). :-) A bit strange, isnt it ? Unstable is more stable than stable.
(In reply to comment #12) > (In reply to comment #10) > > It was fixed already for every package that uses kde.eclass correctly. > > You should _never_ run Makefile.common on the ebuild itself, when using > > kde.eclass, but rather remove the configure file and leave to kde.eclass the > > handling of that. > > > > Now it's fixed for knoda in the tree. > > > > Thanks, but there is a strange thing now : > - emerging from unstable (~x86) works. Hurra! > - emerging from stable version (x86) doesnt still work (same pb as described in > the bug). > > :-) A bit strange, isnt it ? Unstable is more stable than stable. usntable things are hardmasked. _test_ thing are masked by keyword with ~ . test things are almost always more to be test (!), before they can be stable. ;) Cheers, Przemek
