When emerging games-roguelike/moria, the /var/games/moriascores file is created, but CHMODed 640 rather than 660, with the result that moria fails to start as an ordinary user. I'm attaching a patch for the ebuild that fixes the problem. Reproducible: Always Steps to Reproduce: 1. emerge games-roguelike/moria 2. Start moria. Actual Results: It exits complaining that /var/games/moriascores can't be accessed. Expected Results: Carried on and started the game. Portage 2.0.51.22-r2 (default-linux/x86/2005.0, gcc-3.3.5-20050130, glibc-2.3.4.20041102-r1, 2.6.9-gentoo-r9 i686) ================================================================= System uname: 2.6.9-gentoo-r9 i686 Intel(R) Pentium(R) 4 CPU 1400MHz Gentoo Base System version 1.4.16 distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.3 [enabled] dev-lang/python: 2.3.5 sys-apps/sandbox: 1.2.10 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.5 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.4.22-r1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=pentium4 -mcpu=pentium4 -O3 -pipe -fforce-addr -falign-functions=4 -fprefetch-loop-arrays -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /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/share/config /var/bind /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=pentium4 -mcpu=pentium4 -O3 -pipe -fforce-addr -falign-functions=4 -fprefetch-loop-arrays -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://gentoo.blueyonder.co.uk/ http://distfiles.gentoo.org/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/home/ciaran/portage/overlay" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X acpi alsa apm avi berkdb bitmap-fonts cdr crypt cups curl dga divx4linux dvd eds emboss encode esd fam flac fluidsynth foomaticdb fortran gd gdbm gif gmail gnome gphoto2 gpm gstreamer gtk gtk2 imagemagick imlib ipv6 jack java jbig joystick jpeg kde kdeenablefinal ladspa libg++ libwww mad mikmod mmx mmxext motif mozsvg mp3 mpeg multitarget mysql ncurses nls nodrm nptl ogg oggvorbis opengl oss pam pdflib perl pic png povray ppds python qt quicktime readline real samba sdl slang sse sse2 ssl svga tcltk tcpd tiff truetype truetype-fonts type1-fonts v4l vorbis xine xml2 xmms xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS
Created attachment 66674 [details, diff] Patch for moria-5.5.2 ebuild This patch fixes the problem mentioned.
changing files in pkg_postinst is kind of evil. I've put a fix in that should take care of the problem in src_install. In cvs, resync/remerge to get it.
I'm sorry if I'm being a little ignorant here, but after an "emerge sync" today, I can't see any changes to the .ebuild file. I don't have access to CVS as I'm not a Gentoo dev, but my understanding was that changed to CVS would be automatically reflected in the Portage tree. Am I wrong? In any case, may I ask what change you made? I have an ebuild I'm making which does the same thing and I'd like to know what change you made to get around changing files in pkg_postinst. Thanks.
the version of the ebuild in the CVS header should be 1.10
