Red Hat Bugzilla – Bug 231697
RPM install scripts don't create homedir for torrent user
Last modified: 2008-04-10 19:57:34 EDT
Description of problem:
Installed bittorrent package, attempted to start btseed. init script succeeded
but emitted error to log.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. service btseed start
2. cat /var/log/bittorrent/btseed.log
Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/BitTorrent/platform.py", line 384, in
lang = read_language_file()
File "/usr/lib/python2.4/site-packages/BitTorrent/platform.py", line 336, in
lang_file_name = language_path()
File "/usr/lib/python2.4/site-packages/BitTorrent/platform.py", line 318, in
lang_file_name = os.path.join(config_dir, '.bittorrent', 'data', 'language')
File "/usr/lib64/python2.4/posixpath.py", line 62, in join
elif path == '' or path.endswith('/'):
AttributeError: 'NoneType' object has no attribute 'endswith'
Problem appears to be because RPM install script doesn't create user "torrent"
homedir, and bt is trying to write something in there.
reinstall scriptlet (using /bin/sh):
/usr/sbin/useradd -r -s /sbin/nologin -d /var/spool/bittorrent \
-c "BitTorrent Seed/Tracker" torrent &>/dev/null || :
Suggest create/chown the directory - either explicitly, or via -m switch to useradd.
This should be fixed in bittorrent-4.4.0-4, which has now been released for both
FC-5 and FC-6. The problem had already been fixed in devel.
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
Fixed long ago.
Yup (I am original submitter)