Please mark freeciv-2.2.3.ebuild stable.
tested for stable program woud not run, made sure to be in the user group games as instructed not stable amd64 yet
Not run also for me on amd64. Compiling ok, but when i start new scenary or other, freeciv crash. Anyway, the same behavior occurs with version 2.2.2 and 2.2.1
amd64 will pass. Not stable for us. Thank you guys for the reports.
I've dropped the amd64 keywords then.
I've been running freeciv 2.2.x since its rcX days and it always worked fine (except for non-arch specific game bugs). Just started 2.2.3 on my up2date ~amd64 and it works just fine- no crashes whatsoever. I guess this is specific to the stable tree in one way or another. So I'd like to ask to add back ~amd64.
freeciv 2.2.x has never crashed for me on ~amd64
(In reply to comment #6) > freeciv 2.2.x has never crashed for me on ~amd64 > Runs fine on my ~amd64 system too.
(In reply to comment #4) > I've dropped the amd64 keywords then. > Do not drop the keywords. Leave it as ~amd64 for us. It is not safe to be marked stable. Just that
Archtested on x86: Everything fine
works fine with USE="-ipv6"
Mr.Bones. Why did you drop all the ~amd64 keywords from this package? Users report that it works on ~amd64 but amd64 arch testers say it doesn't on stable amd64. Please bring ~amd64 keywords back
Perhaps separate and more detailed bug reports could be filed by commenters #1 and #2?
(In reply to comment #12) > Perhaps separate and more detailed bug reports could be filed by commenters #1 > and #2? > you want a video with recordmydesktop? when i start freeciv-gtk2 i see this http://yfrog.com/3tfreecivp If you notice I have already selected "start new game" (inizia nuova partita) and you can select what you want but do nothing.
(In reply to comment #13) > you want a video with recordmydesktop? That would be overdoing it. :) > when i start freeciv-gtk2 i see this http://yfrog.com/3tfreecivp freeciv-sdl works over here on amd64, so USE="gtk" might be the cause. I'll do some compilations later on tonight, and see if I can figure it out. If it is about gtk+ then it might affect other arches as well.
+1 working on amd64... Both freeciv-gtk2 and freeciv-sdl seem to work fine without any problems. Am sure that there is no problem with this being ~amd64. Some package information for you: =games-strategy/freeciv-2.2.3 gtk ipv6 nls readline sdl sound -auth -dedicated -ggz =x11-libs/gtk+-2.20.1-r1 cups jpeg jpeg2k tiff vim-syntax xinerama -aqua -debug -doc -introspection -test =media-libs/libsdl-1.2.13-r1 X aalib alsa audio directfb esd fbcon joystick libcaca opengl pulseaudio video xinerama xv -custom-cflags -dga -ggi -nas -oss -svga -tslib
freeciv-2.2.2 works fine for me on mostly-stable amd64. Please do not drop keywords in cases like this. games-strategy/freeciv-2.2.2 (gtk ipv6 nls readline sdl sound -auth -dedicated -ggz) x11-libs/gtk+-2.20.1-r1 (cups jpeg tiff vim-syntax xinerama -aqua -debug -doc -introspection -jpeg2k -test) media-libs/libsdl-1.2.13-r1 (X aalib alsa audio dga joystick opengl oss video xinerama xv -custom-cflags -directfb -esd -fbcon -ggi -libcaca -nas -pulseaudio -svga -tslib)
Not a single on x86. server, -gtk2, -sdl everything works like a charm. x86 stable.
freeciv-2.2.3-gtk2 works fine for me in a brief test on a mostly unstable amd64. I agree with the others that whilst not stabilising was clearly right, it seems premature to remove the keyword. For those who don't know how to get it back without editing the ebuild, you need an entry in package.keywords for freeciv with ** as the keyword.
games-strategy/freeciv-2.2.3 works also fine on my amd64 system USE flags: ipv6 nls readline sdl sound -auth -dedicated -ggz -gtk
Why did you drop amd64 keyword? In my opinion, it is better to only mask amd64, or keyword as ~amd64. Problem occurs when freeciv is compiled with ipv6 support and system doesn't support ipv6. For details see my bug report to upstream https://gna.org/bugs/index.php?16989
@games please bring amd64 keywords back or I will do it on behalf of QA in 24 hours. Thanks
amd64 keywords restored
nothing left for amd64 here
I tried run Freeciv-2.2.4 compiled with ipv6 support and without ipv6 kernel module loaded and it working fine.
