Well .. net-irc/konversation-0.19-r1 has been in the ~x86 branch since 02-04-2006 .. I've been using it for 2 days without a single crash or even a minor problem .. I've tried emerging it while turning on/off its different USE flags "arts & debug" and everything's fine with them .. But I couldnt try the xinerama USE flag as I dont have multiple screens, I would be thankfull if anyone could test this flag . Anyhow, I can see that konversation-0.19-r1 is mature enough to move to the x86 branch, there are even no opened bugs at the moment and there are no ~x86 dependencies for it. Thank You KEYWORD= Stable emerge --info: Portage 2203-svn (default-linux/x86/2005.1, gcc-3.4.5, glibc-2.3.6-r3, 2.6.14-gentoo-r5 i686) ================================================================= System uname: 2.6.14-gentoo-r5 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz Gentoo Base System version 1.6.14 dev-lang/python: 2.3.5, 2.4.2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=pentium4" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/eselect/compiler /etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=pentium4" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://gentoo.osuosl.org/" LINGUAS="en ar" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync3.it.gentoo.org/gentoo-portage" USE="x86 X aac aalib alsa apm arts artworkextra audiofile avi bash-completion berkdb bitmap-fonts buttons bzip2 cdparanoia cdr cli crypt cups curl dbus directfb divx4linux dri dv dvd dvdr dvdread eds emacs emboss encode esd exif expat fam fat fbcon ffmpeg firefox flac foomaticdb fortran gcj gdbm gif glut gmp gnutls gpm gstreamer gtkhtml hal idn imagemagick imlib ipv6 isdnlog java javascript jfs jpeg kde lame lcms libg++ libwww live lm_sensors mad mikmod mjpeg mmx mng motif mozilla mp3 mpeg mplayer musicbrainz mysql ncurses nls nocd nsplugin ntfs nvidia offensive ogg oggvorbis openal opengl oss pam pcre pdflib perl png pppd python qt quicktime readline real reflection samba sdl server session slang smp spell spl sse sse2 ssl svg svga symlink tcltk tcpd theora tiff truetype truetype-fonts type1-fonts udev unicode usb userlocales vcd vidix vim-with-x vorbis vorbix win32codecs xchattext xfs xine xml2 xmms xorg xv xvid zlib linguas_en linguas_ar userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, INSTALL_MASK, LANG, LC_ALL, LDFLAGS
I helped him write up this bug and it should be handled by x86. If one of the x86 AT's wants to confirm this it would be great. :)
It's up to the package maintainer, if he considers an app version stable.
I'd like to say thank you for suggesting that it should be stable and looking to see if its been in the tree over a month. However, as carlo pointed out its up to the members of the herd to decide if it is in fact ready in their opinion to be tested for stable. As such net-im: consider this a ping :)
*** Bug 131798 has been marked as a duplicate of this bug. ***
any progress on this one? It's now in ~x86 since two months and still no bug reports.
Being net-irc basically only Sven, I've recently added konversation under kde herd. Using it daily, I suppose I might say that's stable enough to call the stabilisation :)
its all sorts of done here in x86 land. (^.^)
Does anybody else have problems with the nicklist sometimes not showing all nicks (or none at all on smaller channels)?
(In reply to comment #8) > Does anybody else have problems with the nicklist sometimes not showing all > nicks (or none at all on smaller channels)? > Can you reproduce this bug ? As it never happens here !
Well, yes. I went back to 0.18 and all is fine. Once I go up to 0.19 I get lots of missing nicks in the nicklist (I usually see that in #gentoo-security). Sometimes I can't even see my own nick.
(In reply to comment #10) > Well, yes. I went back to 0.18 and all is fine. Once I go up to 0.19 I get lots > of missing nicks in the nicklist (I usually see that in #gentoo-security). > Sometimes I can't even see my own nick. > It is still NOT reproducable here ... Will you please try to reproduce with a fresh account and the default settings ?
I was afraid you'd say that .-) Yes, will do later on; be reporting back.
Hm, tried again with a profile wipe. Not it worked twice <?? - don't ask me>, after that I get the same problem as before. I have to add I am going through a bouncer (miau) on localhost, but I'd like to remind you that it works with 0.18 (I reconfirmed that).
I have not been able to reproduce your bug here either. I do not currently use a bouncer though. Anyone else using this bouncer able to reproduce the bug? I would support stabilising on amd64 where I have used it daily since the version bump. Can you try without the bouncer and see if you still encounter the same bug?
As a preliminary result (will have to watch it a little) I hate to say it seems related to the bouncer (I say "hate" because not using one is not an option), though I tried different versions of miau and it does not affect the problem. Going back to konversation 0.18 obviously fixes it, too. Maybe it's a timing (were there changes to rescan code or something?) or anti-flooding problem? Might try a different bouncer, although I don't really want to :/
Well, confirmed on my side. Nevertheless an upstream bug I guess (too bad KDE bugzie seems ta hate me lately). Thanks for listening.
21:26 <@Kugelfang> will leave fixing/upstreaming the bug to you then 21:26 <@Flameeyes> close it, it should be reported separately imho 21:26 <@Flameeyes> and in both cases it should be reported most likely to the upstream of the bouncer stable on amd64. FIXED
Just FYI: The bug was accepted by konversation (not miau) devs and is fixed in SVN (build 3109).
