Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
capomastro*
0 upgraded, 0 newly installed, 1 to remove and 42 not upgraded.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
(Reading database ... 499073 files and directories currently installed.)
Removing capomastro (20150401) ...
Purging configuration files for capomastro (20150401) ...
rm: cannot remove ‘/etc/apache2/sites-available/capomastro.conf’: No such file or directory
dpkg: error processing package capomastro (--purge):
subprocess installed post-removal script returned error exit status 1
Errors were encountered while processing:
capomastro
E: Sub-process /usr/bin/dpkg returned an error code (1)
Once I sudo touch that path it removes the package just fine though. Shouldn't be hard to fix it, filing this so I don't forget about it.
Usually we upgrade the package rather than removing it, right?
This needs to be fixed but I'll triage for later since it doesn't really affect production deployments.