Like commented in comments 1, 2 and 3 in bug 289426 "when I try to login, it tries to update from 2.1.0.1 to 2.1.0.1 (???) and the loading bar remains stuck at 74% showing "Unable to write to game". A similar problem was reported at: http://forums.savage2.com/showthread.php?t=19172 http://aur.archlinux.org/packages.php?ID=18415 when run as root it updates to a 2.1.0.2 version, then, maybe games group should have write permissions on /opt/savage2 (something similar is already being done with enemy-territory)" This blocks its stabilization since users will simply get a non-playable version Thanks for fixing this :-) Reproducible: Always
Allowing games group to write there would be worse than bug 125902.
(In reply to comment #1) > Allowing games group to write there would be worse than bug 125902. > Well, I understand your point of view, I have just asked them to release a new installer or give us some mirror where download updated files for being able to bump our version. But, please, also take care that other ebuilds are granting write permissions for games group: $ grep -r "chmod g+rw" */*/*.ebuild games-arcade/jardinains/jardinains-2.0.ebuild: chmod g+rw "${D}${dir}/data/prefs.xml" games-fps/enemy-territory/enemy-territory-2.60b.ebuild: chmod g+rw "${Ddir}/etwolf-homedir" games-fps/enemy-territory/enemy-territory-2.60b.ebuild: chmod g+rw "${Ddir}" "${Ddir}/etmain" games-rpg/nwn-data/nwn-data-1.29-r1.ebuild: chmod g+rwX ${Ddir} || die "could not chmod" games-rpg/nwn-data/nwn-data-1.29-r3.ebuild: chmod g+rwX ${Ddir} || die "could not chmod"
Other option would be to suggest users to run the game as root the first time for updating :-/
S2 Games primarly are using manual updates by client, I don't understand why someone even wants to use portage for updates :/
(In reply to comment #4) > S2 Games primarly are using manual updates by client, I don't understand why > someone even wants to use portage for updates :/ > Because updates done by client requires write permissions for /opt/Savage2 :-/
Removed from Portage wrt bug 390919.
