This bug is opened for trying to get dev-util/anjuta-2.26.2.2 marked stable, I will add blockers and depends soon before calling arches to stabilize Reproducible: Always
Sorry for the noise, gdl-python-*-r2 is for gdl 2.28, it will have to wait
I'm not really motivated to stabilize anjuta (I meant ask for stab), because it's known to have many issues. For example on my computer it's just unusable... so... @herd: feel free to do it anyway, but you've my opinion, personnally I'm not really optimistic to stabilize a soft which segfaults randomly...
(In reply to comment #2) > @herd: feel free to do it anyway, but you've my opinion, personnally I'm not > really optimistic to stabilize a soft which segfaults randomly... For the record, that's why I stopped maintaining it after only a few days. I couldn't even _use_ it long enough. I'll care about anjuta when it's as stable as gedit. Until then, this app is nearly useless, I really don't see how anyone can do any sort of serious work with it. Cheers
1) Is anjuta-2.28 any better? 2) What about other distros? Is anjuta as unstable on, say, fedora?
(In reply to comment #2) > I'm not really motivated to stabilize anjuta (I meant ask for stab), because > it's known to have many issues. > For example on my computer it's just unusable... so... > > @herd: feel free to do it anyway, but you've my opinion, personnally I'm not > really optimistic to stabilize a soft which segfaults randomly... > Yes, I was aware about it, the problem is that current stable doesn't seem to be much better, it's quite old, upstream no longer maintains it and has some opened bugs and problems :-/ (In reply to comment #4) > 1) Is anjuta-2.28 any better? > 2) What about other distros? Is anjuta as unstable on, say, fedora? > Seems that fedora has been providing following upstream releases: http://cvs.fedoraproject.org/viewvc/F-11/anjuta/ I haven't tried 2.28, but maybe it would be better since debian seems to provide it: http://patch-tracker.debian.org/package/anjuta Maybe other option would be to simply drop all anjutas to "~" until it's more stable, keeping in testing gnome-stable versions (2.26 now) and new ones (2.28) :-/
(In reply to comment #5) > Maybe other option would be to simply drop all anjutas to "~" until it's more > stable, keeping in testing gnome-stable versions (2.26 now) and new ones (2.28) > :-/ Gilles and I quickly talked about anjuta this morning and he made a point that the current stable anjuta is awful and something should be done about it. If it were up to me, I'd go with your choice, Pacho, I don't think anjuta deserves a stable keyword. Not yet anyway. But if we decide not to unstabilize anjuta, the latest version should be made stable, at least users (if there are any) could report bugs upstream and help improve it... Cheers
When do you think the rest of gnome 2.28 will go stable? Maybe we could wait until then for stabilizing also anjuta 2.28 (since upstream will probably prefer get reports from latest stable than 2.26 and other distributions like debian have also "jumped" to it)
I think the main bugs should be mostly reported on upstream, except for trivial tasks of course. Usually bugs for anjuta are crashes (and not trivial crashes...), and I'm not really interested to debug it... (my job is to write some patches, bump, and sometimes fix crashes, not re-code a soft...) the lastest version in debian is 2.28 without any patches (except for libtool if I remember correctly), w0w... and it works ? ^^ For me, a package which is candidate to be stabilized should be mature enough...
(In reply to comment #7) > When do you think the rest of gnome 2.28 will go stable? Maybe we could wait > until then for stabilizing also anjuta 2.28 Don't think you need to wait for the rest of GNOME-2.28 to take anjuta-2.28 to stable; it's not in the desktop set, and has little to do with the rest of GNOME.
Fine (I thought it was a gentoo gnome team policy, sorry)
We will try with anjuta 2.28 then. I am building new stuff now, but it will take some time :-( Regarding webkit dependency, if I don't misremember, leio suggested on IRC to try to backport affected plugin (devhelp one) for using gecko version or try to stable a newer webkit. I have been using net-libs/webkit-gtk-1.1.15.4 with success since then :-) We could try to stable it, but it would require to stable also dev-libs/glib-2.22* (well, this can be discussed in bug 298202 )
Last stable anjuta : 2.20 doesn't compile anymore because of glade 3.6.7 stabilization on x86 and amd64, should I have to open another bug for this?
(In reply to comment #12) > Last stable anjuta : 2.20 doesn't compile anymore because of glade 3.6.7 > stabilization on x86 and amd64, should I have to open another bug for this? > please do, with emerge --info and build.log.
(In reply to comment #13) > (In reply to comment #12) > > Last stable anjuta : 2.20 doesn't compile anymore because of glade 3.6.7 > > stabilization on x86 and amd64, should I have to open another bug for this? > > > > please do, with emerge --info and build.log. > I opened the bug with the info you asked me , it's bug #300238 : http://bugs.gentoo.org/show_bug.cgi?id=300238
Arches, please test and mark stable
amd64 stable
*** Bug 268359 has been marked as a duplicate of this bug. ***
*** Bug 297626 has been marked as a duplicate of this bug. ***
Tested this on x86 in combination with the yet to go stable dependencies: -) dev-libs/gnome-build-2.24.1 needs to go stable with it. The current stable of gnome-build requires gdl to have a gnome use-flag (I think...): * ERROR: dev-libs/gnome-build-0.3.0 failed: * dev-libs/gdl-2.28.2 does not actually support the gnome USE flag! * * Call stack: * ebuild.sh, line 54: Called pkg_setup * gnome-build-0.3.0.ebuild, line 35: Called built_with_use 'dev-libs/gdl' 'gnome' (Note that gnome-build is actually blocking anjuta, but it is an rdep of gdl...) The new anjuta compiles and runs, making it far better than the current stable. Good to go after the deps are stable.
stable x86, thanks Thomas
ppc done
sparc stable
@hppa, please use.mask devhelp USE flag so we can get this stabilized and drop old/unsupported anjuta releases from the tree. Thanks.
ppc64 is still missing this
hppa won't do this due bug #324511 (has already lost their stable keywords)
(In reply to comment #24) > ppc64 is still missing this > gdl and gdl-python stable for ppc64, anjuta was never keyworded...
