https://bugs.helixcommunity.org/show_bug.cgi?id=4745
Summary: Player group and owner set to 501 when
installing using
.bin
Project: player
Version: 10.0.6.776
Hardware: PC
Operating System: Linux
Status: NEW
Severity: TRIAGE
Priority: TRIAGE
Tracker: Bugs
AssignedTo: TRIAGE
ReportedBy: dshirzad
QAContact: mlapora
CC:
,player-listuser-2e4ac0e8-b89b-11d8-92ef-00d0b7075c1c,ra
bbit
bug: When installing either the Helix or RealPlayer using
the .bin installer, it attempts to set
the owner and group to 501:501. If the user is currently
logged in as root, the installation will
complete without errors, but the player directory will be
owned by 501:501. If the user is not
logged in as root, the installer gives many errors about
being unable to change ownership to 501:501
before installing as the current user.
expected: The player should installed as owned by the
current user.
repro:
1) Download the Linux realplayer or the helixplayer .bin
installer from either http://www.real.com
or http://player.helix
community.org.
2) Make the installer executible (chmod +x)
3) Run the installer
4) Verify that if not currently logged in as root the
installer gave many errors regarding changing
ownership, or if logged in as root that the installed player
directory is owned by user 501:501 -
not root.
More information from rggammon:
You can pass tar a flag telling it not to chown:
-o, --no-same-owner
do not attempt to restore ownership when
extracting; -o exhibits
this behavior when extracting an archive
... and we do (except on OpenBSD for reasons unknown):
https:/
/helixcommunity.org/viewcvs/cgi/viewcvs.cgi/installer/common
/platform/unix/stage1.cpp?annotate=1.2
247 #if defined(_OPENBSD)
248 const char* szTarOpts = "xf";
249 #else
250 const char* szTarOpts = "xof";
251 #endif
(note the o in xof)
I'd expect everything to thus be owned by root.
--
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone
who is.
You are in the CC list for the product the bug is within.
This e-mail is sent to you automatically from the Helix Bug
Tracker. Please, do
not respond to this message, but instead edit your Bug
Tracker user preferences
to change when Bug Tracker sends you e-mail.
_______________________________________________
Player-issues mailing list
Player-issues helixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/p
layer-issues
|