Package Details: mldonkey-git 3.2.1.r14.g0d446356-4

Git Clone URL: https://aur.archlinux.org/mldonkey-git.git (read-only, click to copy)
Package Base: mldonkey-git
Description: A multi-network P2P client
Upstream URL: https://github.com/ygrek/mldonkey
Licenses: GPL-2.0-or-later
Conflicts: mldonkey
Provides: mldonkey
Submitter: FabioLolix
Maintainer: FabioLolix
Last Packager: FabioLolix
Votes: 1
Popularity: 0.002099
First Submitted: 2024-08-09 13:41 (UTC)
Last Updated: 2025-06-17 05:23 (UTC)

Latest Comments

maxpayne3 commented on 2025-01-25 15:53 (UTC)

The pkgbuild is also maintained here https://github.com/FabioLolix/PKGBUILD-AUR_fix

Can you push the fix here? Thanks.

maxpayne3 commented on 2025-01-16 22:28 (UTC) (edited on 2025-01-16 22:29 (UTC) by maxpayne3)

I tested the systemd service (which I don't use regularly) another time and noticed the following:

  • The first time the service is launched (when /var/lib/mldonkey/.mldonkey is empty) the -log_file /dev/null command option is ignored and the log is written to /var/lib/mldonkey/.mldonkey/mlnet.log.
  • When you stop the service and later restart it a second time, the above mentioned mlnet.log has the following last line [cO] Logging in /var/lib/mldonkey/.mldonkey//dev/null.
  • From that moment, anytime you start/stop the service, the log is not written anymore.
  • On the file not found error, I made a mistake about that, I misremembered. But the service was not logging because the file was not found anyway.
  • I understand the intention was to not log on the file (because you want it to -log_to_syslog, but if it still logs on the default log file the first time and then it won't do it anymore because the service expect to write on /dev/null assumed as relative path from the config folder, there's something wrong.

FabioLolix commented on 2025-01-16 20:22 (UTC)

The pkgbuild is also maintained here https://github.com/FabioLolix/PKGBUILD-AUR_fix

FabioLolix commented on 2025-01-16 20:16 (UTC)

I noticed also an issue with the systemd service. "/dev/null" is appended to the current path and the text log is written anyway (which reports a file not found error).

Do you know what is the expected path for this?

maxpayne3 commented on 2025-01-16 20:15 (UTC)

I noticed also an issue with the systemd service. "/dev/null" is appended to the current path and the text log is written anyway (which reports a file not found error). It seems that option is expecting a relative path, not a full one.

FabioLolix commented on 2025-01-16 11:22 (UTC)

I'll look into it, I guess they have unbundled it

maxpayne3 commented on 2025-01-16 08:14 (UTC)

crypto++ is needed as dependency. Without it, the service does not start.