resolvconf package needs dependency on ifupdown

[Daniel Richard G.]

When I install resolvconf on a minimal install of Ubuntu 18.04 (bionic), I see this:

# apt-get install resolvconf
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  resolvconf
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/48.2 kB of archives.
After this operation, 187 kB of additional disk space will be used.
Preconfiguring packages ...
/tmp/resolvconf.config.XleExb: 13: /tmp/resolvconf.config.XleExb: ifquery: not found
/tmp/resolvconf.config.XleExb: 13: /tmp/resolvconf.config.XleExb: ifquery: not found
Selecting previously unselected package resolvconf.
(Reading database ... 90542 files and directories currently installed.)
Preparing to unpack .../resolvconf_1.79ubuntu10_all.deb ...
Unpacking resolvconf (1.79ubuntu10) ...
Processing triggers for ureadahead (0.100.0-20) ...
Processing triggers for systemd (237-3ubuntu10) ...
Processing triggers for man-db (2.8.3-2) ...
Setting up resolvconf (1.79ubuntu10) ...
/var/lib/dpkg/info/resolvconf.config: 13: /var/lib/dpkg/info/resolvconf.config: ifquery: not found
/var/lib/dpkg/info/resolvconf.config: 13: /var/lib/dpkg/info/resolvconf.config: ifquery: not found
Created symlink /etc/systemd/system/sysinit.target.wants/resolvconf.service → /lib/systemd/system/resolvconf.service.
Created symlink /etc/systemd/system/systemd-resolved.service.wants/resolvconf-pull-resolved.path → /lib/systemd/system/resolvconf-pull-resolved.path.
resolvconf-pull-resolved.service is a disabled or a static unit, not starting it.
resolvconf-pull-resolved.service is a disabled or a static unit, not starting it.
Processing triggers for systemd (237-3ubuntu10) ...
Processing triggers for ureadahead (0.100.0-20) ...
Processing triggers for resolvconf (1.79ubuntu10) ...

The "ifquery" program is provided by the ifupdown package. Therefore, resolvconf needs to include ifupdown in its Depends: clause. (Currently, ifupdown is mentioned in Enhances:)

[Parakram Majumdar (appu226)]

I see the same problem while trying to upgrade to ubuntu 18.04. The upgrade seems stuck after the line
Processing triggers for resolvconf (1.79ubuntu10) ...

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Elizabeth Lock (waltraute)]

I had the same problem as Parakram, but found that the upgrade did actually finish correctly though the terminal window remained stuck at that line for three or four hours. Something was still happening,