Package: mldonkey-server Version: 2.5.28-2 Severity: grave Justification: renders package unusable
-- System Information: Debian Release: 3.1 APT prefers testing APT policy: (990, 'testing'), (600, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.10-1-686 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages mldonkey-server depends on: ii adduser 3.63 Add and remove users and groups ii debconf [debconf-2.0] 1.4.30.11 Debian configuration management sy ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an ii mime-support 3.28-1 MIME files 'mime.types' & 'mailcap ii ucf 1.14 Update Configuration File: preserv ii zlib1g 1:1.2.2-3 compression library - runtime -- debconf information: * mldonkey-server/max_hard_download_rate: 0 * mldonkey-server/launch_at_startup: false mldonkey-server/config_exist_no_options: * mldonkey-server/plugin: Directconnect, Opennap, Overnet, Soulseek, Bittorent, Gnutella * mldonkey-server/mldonkey_group: mldonkey mldonkey-server/false_password: * mldonkey-server/max_hard_upload_rate: 2 * mldonkey-server/max_alive: 24 * mldonkey-server/run_as_user: mldonkey mldonkey-server/reown_file: false * mldonkey-server/mldonkey_niceness: mldonkey-server/config_exist_no_dir: mldonkey-server/fasttrack_problem: mldonkey-server/shared_directories: share * mldonkey-server/mldonkey_dir: /var/lib/mldonkey * mldonkey-server/restart_after_upgrade: true * mldonkey-server/client_name: lightning mldonkey-server/mldonkey_move: false * mldonkey-server/mldonkey_umask: 0022 Several people in other bug reports have mentioned that /etc/init.d/mldonkey-server start does actually fail to start the server. Part of the problem might be that /var/lib/mldonkey is not actually generated on install, eventhough this dir is selected via dpkg. However, what sure is the case is the fact that /var/run/mldonkey is owned by root on install and the mldonkey-server init script simply is not able to write to it for some reason. I guess that might be because of chroot or running mldonkey by the mldonkey user. However, it is absolutely certain, that it starts after I set the ownership of the /var/run/mldonkey DIR to mldonkey user! Setting the group instead of the user to mldonkey might help as well. The other problems I still have are described in other bug reports, like the one that whatever I enter in debconf never makes it to the /etc/defaults/mldonkey-server file. I am not sure if /var/lib/mldonkey + files is actually created on first startup when set in defaults accordingly since I first thought it mldonkey does not start up for the reason of the dir + files not being there and therefore copied a working set over from another machine. I never removed it afterwards since I was so happy that it finally worked and fed up with dealing with it. I hope this bug report makes mldonkey-server usable again out of the box. (At least as soon as the startup value users set via debconf on install really makes it into the defaults file). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
