Some more details: It can not be reproduced by just installing the package and removing it, as the symlink is created when dconf runs the first time.
The postrm script does delete the symlink, but only on "purge", not on "remove" (as experienced before). ** Description changed: /etc/cron.weekly/dconf is just a symlink on /usr/bin/dconf which is not removed on package removal. So if you just remove the package but don't purge it, you will get weekly mails arguing: run-parts: failed to stat component /etc/cron.weekly/dconf: No such file or directory Please either a) remove that symlink and make a shell script out of it which first checks, if /usr/bin/dconf exists and only then calls it, or - b) remove that symlink in the postinst script on removal already. + b) remove that symlink in the postrm script on removal already. I'd prefer a) as it's the cleaner way. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/804188 Title: Removing dconf leaves dangling symlinks: "run-parts: failed to stat component /etc/cron.weekly/dconf: No such file or directory" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dconf/+bug/804188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
