Comment 37 for bug 1774120

Revision history for this message
Balint Reczey (rbalint) wrote :

Tested version on Xenial: 2.0.10.4-3.4ubuntu2.16.04.2

Log:
...
ubuntu@rbalint11:~$ sudo apt install --reinstall ebtables=2.0.10.4-3.4ubuntu2.16.04.2
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
  libfreetype6
Use 'sudo apt autoremove' to remove it.
The following packages will be upgraded:
  ebtables
1 upgraded, 0 newly installed, 0 to remove and 22 not upgraded.
Need to get 79.9 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 ebtables amd64 2.0.10.4-3.4ubuntu2.16.04.2 [79.9 kB
]
Fetched 79.9 kB in 0s (1,101 kB/s)
(Reading database ... 25691 files and directories currently installed.)
Preparing to unpack .../ebtables_2.0.10.4-3.4ubuntu2.16.04.2_amd64.deb ...
invoke-rc.d: could not determine current runlevel
 * Error: insufficient privileges to access the ebtables rulesets.
invoke-rc.d: initscript ebtables, action "stop" failed.
dpkg: warning: subprocess old pre-removal script returned error exit status 1
dpkg: trying script from the new package instead ...
dpkg: ... it looks like that went OK
Unpacking ebtables (2.0.10.4-3.4ubuntu2.16.04.2) over (2.0.10.4-3.4ubuntu2.16.04.1) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for systemd (229-4ubuntu21.2) ...
Processing triggers for ureadahead (0.100.0-19) ...
Setting up ebtables (2.0.10.4-3.4ubuntu2.16.04.2) ...
Installing new version of config file /etc/init.d/ebtables ...
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
invoke-rc.d: could not determine current runlevel
Processing triggers for systemd (229-4ubuntu21.2) ...
Processing triggers for ureadahead (0.100.0-19) ...
ubuntu@rbalint11:~$