-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
To give you detailed information of the missbehaviour of your package I did a
detailed investigation and prepared my system as you requested in your email.
> Here are the step :
> - save your current download ( répértoire /var/lib/mldonkey )
> - stop the daemon
> - "apt-get remove --purge mldonkey-server"
> - remove the user mldonkey and the group mldonkey ( if they exist )
> - check nothing lefts ( dir like /var/run/mldonkey )
> - apt-get install mldonkey-server ( answer the debconf question )
> - check if it is working.
First thing to complain about:
apt-get remove --purge mldonkey-server
removed my /etc/defaults/mldonkey-server.bak as well
Additional information: mldonkey user and group have not been deleted by dpkg
So I removed them by hand and reinstalled
What pops up first after debconf questions answered is the following:
- ----------------------------------------------------------
Setting up mldonkey-server (2.5.28-2) ...
Configuration file `/etc/default/mldonkey-server'
==> File on system created by you or by a script.
==> File also in package provided by package maintainer.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a new shell to examine the situation
The default action is to keep your current version.
*** mldonkey-server (Y/I/N/O/D/Z) [default=N] ?
- ---------------------------------------------------------------------
This issue has already been discussed intensively in every detail and
unfortunately highly emotional from your side in the bugtracking system but
is still unsolved. As far as I can tell, the solution is already provided in
detail in the bug reports!
What am I supposed to answer here?
Since I do not know, the logical answer is default=N.
/etc/init.d/mldonkey-server
shows the followind (# hereinafter, comments in files are removed for
shortness)
- --------------------------------------------------
MLDONKEY_DIR=/var/lib/mldonkey
MLDONKEY_GROUP=mldonkey
MLDONKEY_UMASK=0022
MAX_ALIVE=24
LAUNCH_AT_STARTUP=false
MLDONKEY_NICENESS=
- --------------------------------------------------
While actually I have set things differnently with debconf:
- --------------------------------------------------
MLDONKEY_DIR=/var/lib/mldonkey
MLDONKEY_GROUP=mldonkey
MLDONKEY_UMASK=0002
MAX_ALIVE=48
LAUNCH_AT_STARTUP=true
MLDONKEY_NICENESS=20
- --------------------------------------------------
That is really anoying. Moreover, as far as nice --help is concerned, there is
no niceness 20! The lowest priority you can set is 19.
So now, I changed the settings by hand according to my initial settings in
debconf.
I check for the user and group
- --------------------------------------------------
getent passwd mldonkey
getent group mldonkey
- --------------------------------------------------
Both commands not return anything, user and group are not created so far.
So what for did I answer a debconf question then?
- --------------------------------------------------
ls -dl /var/run/mldonkey
drwxr-xr-x 2 root root 48 2004-09-04 16:32 /var/run/mldonkey
- --------------------------------------------------
However, I give it a try and start the thing with /etc/init.d/mldonkey-server
start
- --------------------------------------------------
/etc/init.d/mldonkey-server start
(unset) is not a valid directory
- --------------------------------------------------
According to this, first thing the user would check, is if /var/lib/mldonkey
exists.
Hmm, it does not.
Didn't I tell debconf what dir I want to use? Why didn't it create the dir, it
should not be a big problem to check whether or not it is already there
"test ...".
So the logical step now, would be to create the dir.
- --------------------------------------------------
mkdir /var/lib/mldonkey
ls -dl /var/lib/mldonkey
drwxr-xr-x 2 root root 48 2005-03-17 15:10 /var/lib/mldonkey
- --------------------------------------------------
Start again:
- --------------------------------------------------
/etc/init.d/mldonkey-server start
/var/lib/mldonkey/downloads.ini is not a valid file
- --------------------------------------------------
Well, no wonder, there is none.
- --------------------------------------------------
ls -l /var/lib/mldonkey
total 0
- --------------------------------------------------
OK, let's pretend I am not completely stupid and figure out, that there is no
mldonkey user and group and I create those and make /var/lib/mldonkey to be
owned by them.
- --------------------------------------------------
groupadd mldonkey
useradd -g mldonkey -d /var/lib/mldonkey mldonkey
getent passwd mldonkey
mldonkey:x:1004:1002::/var/lib/mldonkey:
getent group mldonkey
mldonkey:x:1002:
- --------------------------------------------------
That's the part where the normal user would start to get angry, most are just
to used to packages like apache, that actually create the needed users for
them. Me, as I am the calmness itself, I just start to ask myself, whether or
not some representative of the music/film industry is maintaining the
package.
So not, that the users are existant, just to find out, if /var/lib/mldonkey
was actually not created for the only reason that there was no mldonkey
user/group, I removed /var/lib/mldonkey again and try to start again.
- --------------------------------------------------
/etc/init.d/mldonkey-server start
(unset) is not a valid directory
- --------------------------------------------------
Nop, was not it. So I recreate and make it owned by mldonkey:mldonkey.
- --------------------------------------------------
mkdir /var/lib/mldonkey
chown mldonkey:mldonkey /var/lib/mldonkey
ls -ld /var/lib/mldonkey
drwxr-xr-x 2 mldonkey mldonkey 48 2005-03-17 15:21 /var/lib/mldonkey
- --------------------------------------------------
- --------------------------------------------------
/etc/init.d/mldonkey-server start
/var/lib/mldonkey/downloads.ini is not a valid file
- --------------------------------------------------
Still? Hmm, not even that is generated??
I generate an empty file.
- --------------------------------------------------
touch /var/lib/mldonkey/downloads.ini
chown mldonkey:mldonkey /var/lib/mldonkey/downloads.ini
ls -l /var/lib/mldonkey/downloads.ini
- -rw-r--r-- 1 mldonkey mldonkey 0 2005-03-17
15:23 /var/lib/mldonkey/downloads.ini
- --------------------------------------------------
- --------------------------------------------------
/etc/init.d/mldonkey-server start
Starting MLDonkey: mlnet.
- --------------------------------------------------
But it seems this message is bullshitting me!
- --------------------------------------------------
ps ax | grep ml
16774 pts/2 S+ 0:00 grep ml
- --------------------------------------------------
So now I check less /var/lib/mldonkey/downloads.ini to see if anything was
generated. Nop, empty!
At that point I would try to copy an old downloads.ini from somewhere else,
but I am curious if downloads.ini gets a default setup when mlnet finally
starts up.
I found out, there is another file/dir that could cause
trouble: /var/run/mldonkey
Nothing in it:
- --------------------------------------------------
ls -l /var/run/mldonkey/
total 0
- --------------------------------------------------
But owned by root:
- --------------------------------------------------
ls -ld /var/run/mldonkey/
drwxr-xr-x 2 root root 48 2004-09-04 16:32 /var/run/mldonkey/
- --------------------------------------------------
I would not find that very suspicious, since most files in /var/run are owned
by root, which seems logic since most services are started by root or even as
root. However, this one was asking about beeing started as mldonkey in
debconf, so I give it a try:
- --------------------------------------------------
chown mldonkey:mldonkey /var/run/mldonkey/
ls -ld /var/run/mldonkey/
drwxr-xr-x 2 mldonkey mldonkey 48 2004-09-04 16:32 /var/run/mldonkey/
- --------------------------------------------------
- --------------------------------------------------
/etc/init.d/mldonkey-server start
Starting MLDonkey: mlnet.
lightning:/data/home/hugo# ps ax | grep ml
http://pkg-kde.alioth.debian.org/kde-3.4.0
16811 ? SN 0:00 /usr/bin/mldonkey_server --start
- --pidfile /var/run/mldonkey/mlnet.pid --chdir /var/lib/mldonkey --chuid
mldonkey --max-alive 48 --umask 0002 --daemon
16814 ? RN 0:00 /usr/bin/mlnet
16816 ? SN 0:00 /usr/bin/logger -t mlnet_error
16818 ? SN 0:00 /usr/bin/logger -t mlnet
16820 pts/2 R+ 0:00 grep ml
- --------------------------------------------------
Uuuuh, that did it!
Even /var/lib/mldonkey/downloads.ini has some contents now, cool. And the rest
of the files was generated as well.
I stop the thing again and remove /var/lib/mldonkey and recreated it but not
downloads.ini to see, if this one is generated now that the user and group
exist as well.
- --------------------------------------------------
mkdir /var/lib/mldonkey
chown mldonkey:mldonkey /var/lib/mldonkey
/etc/init.d/mldonkey-server start
/var/lib/mldonkey/downloads.ini is not a valid file
- --------------------------------------------------
Nop.
Conclusion:
* Move the default to /usr/share/mldonkey/examples
Make debconf do the following things according to user input:
* Create the config file (echo somesthing)
* Create user, group (if not existant)
* Create and dir and an empty downloads.ini (if not existant)
* Chown mldonkey:mldonkey /var/run/mldonkey
Out of the box, the package does not work at all and all the settings, that I
have made via debconf do not result in anything set in the config files
accordingly or in any other action that might be expected.
So what for the questions in the first place? Don't get me wrong, I believe it
does not hurt to answer those questions. Perhaps putting them into another
level, so the standard user is not bothered by them, would be a ok as well.
Oh, one last test: What happens if I choose Y on the debconf question?
So I choose Y this time on the debconf/dpkg question
and /etc/defaults/mldonkey-server looks like this:
- --------------------------------------------------
MLDONKEY_DIR=
MLDONKEY_GROUP=
MLDONKEY_UMASK=
MAX_ALIVE=
LAUNCH_AT_STARTUP=false
MLDONKEY_NICENESS=
- --------------------------------------------------
Looks like a joke, but it is the reality.
I am sorry to say that, since I appreciate the fact, that you took on the
volonary job to maintain a debian package and this way, contribute to the
community, but I am afraid this package sucks.
Futheremore I strongly recommend not to get angry on bug reports and
suggestions, but actually read them, since for example a solution for the
dpkg/ucf problem is already layed out in DETAIL in the bug reports and all
you would have to do is to finally implement them! Even me, that has never
ever created a dpkg could follow the instructions in the bug reports and I
understands the very source of the problem just by reading that comments
carefully.
I believe it is not possible to layout the problems your package in any more
detail than in this report. Furthermore, I believe, that you should have been
able to get to the very same conclusions trying to install your package
yourself. It is not, that you have to have a very special configuration on
your system to run into the problems described, it is a major malfunction of
your package or better the lack of any functionality except for asking a
bunch of questions and the actual init script of course, if that was not
provided from the upstream source.
However, do not feel offended and just make it work. Making mistakes is HUMAN.
Keep it simple!
Regards,
Markus
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
iD8DBQFCOgoI474Mdsi2dOQRAtKgAKDnMQ1UKOgZe5bMAwWNG0S2e5kpJwCcC2/C
hxRSvL8FFHdJLbMpcgRKt70=
=Pb1Q
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
