Public bug reported:
I'm using Ubuntu 16.10 dev and noticing that the package init seems to
be the only one with the "Important" control field which seems to be a
bit curious:
- On removing a package with apt that has the "Important" field set to "yes" it
seems to show the same warning like removing a package that has the "Essential"
field set to "yes". Even the same term "essential" is used instead of
"important" (maybe this should be changed?).
- "man deb-control" does not know this field and removing a package with dpkg
that has the "Important" field set to "yes" does not throw an error while
removing a package that has the "Essential" field set to "yes" does.
- I'm wondering what the difference between the "Essential" and "Important"
field for apt is. I can't find any information about it and can't also find the
manpage that documents the custom control fields that apt but not dpkg knows
(does such a manpage exist?).
- I'm also wondering why init uses this control field instead of the
"Essential" control field as this would additionally prevent removing it by
accident with dpkg.
** Affects: apt (Ubuntu)
Importance: Undecided
Status: New
** Affects: init-system-helpers (Ubuntu)
Importance: Undecided
Status: New
** Also affects: init-system-helpers (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1624681
Title:
"Important" control field is a bit confusing
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1624681/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
