systemd can't be removed from a chroot
Bug #1758438 reported by
Steve Langasek
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| systemd (Ubuntu) |
Fix Released
|
Medium
|
Dimitri John Ledkov | ||
| Bionic |
Fix Released
|
Medium
|
Dimitri John Ledkov | ||
Bug Description
The systemd package has the following code in its prerm:
if [ "$1" = "remove" ] && [ -d /run/systemd/system ]; then
echo "systemd is the active init system, please switch to another before removing systemd."
exit 1
fi
However, /run/systemd/system will exist even in a chroot, and an init system is not needed in a chroot. The maintainer script should include a check for whether we're running in a chroot, to allow systemd to be removed when it's not needed and there is no harm.
| Changed in systemd (Ubuntu): | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
Revision history for this message
| Dimitri John Ledkov (xnox) wrote | #1 |
| Changed in systemd (Ubuntu Bionic): | |
| assignee: | nobody → Dimitri John Ledkov (xnox) |
| milestone: | none → ubuntu-18.03 |
| Changed in systemd (Ubuntu Bionic): | |
| status: | Triaged → Fix Committed |
| tags: | added: id-5ab94347925723c2b2bf3943 |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in systemd (Ubuntu Bionic): | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
I guess this is also preventing upgrades in Windows WSL.