arch testers: please stable either mldonkey-2.6.4-r1 or 2.6.4-r2. they're both quite new in portage, but: 1. We really don't like have 2.5.* version stable, since it's not maintained and supported anymore. 2.5.16 (which is currently stable on x86, hppa and ppc) have several diffrent problems (mainly with bittorrent), which aren't and will not be fixed 2. 2.6.0 was initial version from 2.6 serie. as so it had some bugs fixed in next releases 3. ebuild for 2.6.4 version was in portage since 06 Sep without significant problems. the only thing changed in -r1 and -r2 revisions was inproper USE flag handling and really small, "cosmetic" changes in ebuild. no patches for mldonkey was added/dropped/changed in those revision and there were no integrations with internal mldonkey code we also had ebuilds for 2.6.2 and 2.6.3, but they were both removed from tree. they had broken USE flag logic (as initial ebuild for 2.6.4). besides - they were really short time in testing version, since new mldonkey's releases came very fast note, that -r2 revision is almost the same as -r1. the only diffrence is that we have dropped gtk2 flag from IUSE as gnome herd requests. i don't care which of - r1 and -r2 revision you stable - i'm fine with both
both versions stable on x86
this bug can be closed
not yet. it's stable only on x86 and ppc. other archs: what takes you so long?
Can't stable on amd64, ran into a bug known upstream: http://savannah.nongnu.org/bugs/?func=detailitem&item_id=14751 [ebuild R ] net-p2p/mldonkey-2.6.4-r2 +batch -doc +gd +gtk -guionly +mozilla -threads 0 kB
i don't think it's importange "bug" (if it's a bug at all). you can close it by either: clicking the first icon in bottom left corner (initialy "not connected") or by closing window and then rigth-click on icon in systray.
AMD64 won't stabilize until this bug is fixed. It might seem cosmetical, but do you know if it leave zombie processes/stale lock files/other nasty things?
I ran it from a terminal. After poking around in it, I hit the X. Terminal showed that error. CTRL-C just repeated the error. killall didn't kill it. killall -9 finally did.
Removing ppc since hansmi already marked it stable.
(In reply to comment #4) > Can't stable on amd64, ran into a bug known upstream: > > http://savannah.nongnu.org/bugs/?func=detailitem&item_id=14751 Behaviour of GTK2 GUI taskbar icon has been improved according to the various bug reports / feature requests on Savannah. The patches are currently CVS only but will be included in the upcoming 2.7.0 release. You can test the new code to see if it suites you.
MLDonkey 2.7.0 has been released
*** Bug 109344 has been marked as a duplicate of this bug. ***
amd64 stable
MLDonkey 2.7.3 has been released. With the current stable version (2.6.4) I'm getting this error: ERROR : Your client is too old, please upgrade it to last version from lots of servers. I think the upgrade should be mandatory.
Just keyworded 2.7.3 ~hppa.
2.7.5 is already released and it should be marked as stable for all platforms currently having 2.7.3 in ~
MLDonkey 2.7.6 should be made stable
This bugreport can be closed, also please make MLDonkey-2.7.7 stable
I think that mldonkey 2.7.7 can be marked as stable on x86 arch ;) Thanks :)
Please close this bug, MLDonkey 2.6.4 is stable on x86, ppc & amd64 Next version to be stable should be 2.7.7 in ~two weeks time, I will file a bug report then.
Added some CC addresses to get attention;-)
That's easy.
