Summary: | sys-apps/systemd-utils-256: systemd-tmpfiles will remove /home on --purge | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | MaratIK <marat.buharov> |
Component: | Current packages | Assignee: | Gentoo systemd Team <systemd> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: |
https://github.com/systemd/systemd/issues/33349 https://github.com/systemd/systemd/pull/33383 https://github.com/systemd/systemd/pull/33353 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
MaratIK
2024-06-18 14:24:30 UTC
While I think it's a bit silly that it exists, it's only a bug in that "--purge does what it's documented to do, but has no "are you sure?" question". There's a lot of destructive commands you can run. It's a new option. The question is therefore if we want to just delete the /home tmpfiles entry to avoid the risk of people running it and not realising what it does. I think we could probably delete it at least for systemd-utils, given it's unlikely people will be doing the "blank system" tmpfiles usecase there. Lennart's https://github.com/systemd/systemd/pull/33383 PR is queued for backporting to 256, so I don't think we need to do anything here (256 isn't even packaged yet). I will make a note to check for that commit when I get around to packaging 256.x. |