This bug was fixed in the package mldonkey - 3.0.3-3
---
mldonkey (3.0.3-3) unstable; urgency=low
* Do not erase existing configuration on upgrades (Closes: #601332, #522900),
(LP: #478206).
* Recursively chown /var/{log,run}/mldonkey (Closes: #593091).
* Remove /var/{log,ru
They are not and won't be marked as such.
You can mark this bug as "New", but it won't be fixed.
--
mldonkey conf files should not be crushed on update
https://bugs.launchpad.net/bugs/478206
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
What if this file are marked as conf files in the package (even if
they're not in etc). Does pkg will not ask for install/diff/merge if it
found existing files ?
** Changed in: mldonkey (Ubuntu)
Status: Invalid => New
--
mldonkey conf files should not be crushed on update
https://bugs.lau
When mldonkey is updated, a copy of those files are created in the same
place. When the system upgrades and if by any chance you loose the
content of /var/lib/mldonkey, then there is nothing to do. The unique
solution I see is to hard-link the directory elsewhere so that you
always have a reference
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/35358765/Dependencies.txt
--
mldonkey conf files should not be crushed on update
https://bugs.launchpad.net/bugs/478206
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
