3 ms·
The "purge" option was intended to delete the specific package's state, and it was supposed to be destructive. Compare with "apt remove --purge httpd" which rem
by theamk 2y ago
The "purge" option was intended to delete the specific package's state, and it was supposed to be destructive. Compare with "apt remove --purge httpd" which removes all your nice hand crafted server configs.
The bug happened because if there is no config specified, it applies to all configs.. which is obviously not a good idea with purge.
The fix [0] makes purge safe-ish again by requiring a config file, so it won't purge your homedir unless you explicitly tell it to.
[0] https://github.com/bluca/systemd/commit/c4220bd2d390e9b330e835256182130d3bd5b94a https://github.com/bluca/systemd/commit/c4220bd2d390e9b330e8...
- arp242 2y agoThe person who implemented this was very clear it was working as intended. Don't try and retcon this as a "bug".
- theamk 2y agoyou mean the 2nd comment in thread, where bluca said "don't just run random commands"? Well, it was pretty harsh, but he had a point.. I mean, if someone did "apt remove --purge cron" and then come complaining about /etc/crontab disappearing, what would you tell them? That said, apparently the "--purge without argument" was _not_ intended, because they removed it entirely, and they were sure it would not break things. (Compare to "--preserve-root" option to "rm" - that was actually intended behavior, so maintainers there had to specifically add "--no-preserve-root" option)
- deleted 2y ago[deleted]