Why did 'apt - get install ffmpeg' fall short?

I do not recognize just how or why apt - get install fallen short. It states ssmtp which is straightforward smtp which I make use of to send mail from my web server to my Google apps account. I do not recognize what is incorrect or just how to repair it.

I am making use of debian press.

# apt-get install ffmpeg
Setting up libswscale0 (4:0.5.2-6) ...
Setting up ffmpeg (4:0.5.2-6) ...
Errors were encountered while processing:
E: Sub-process /usr/bin/dpkg returned an error code (1)

# sudo apt-get install ffmpeg
sudo: unable to resolve host debian
Reading package lists... Done
Building dependency tree
Reading state information... Done
ffmpeg is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue [Y/n]? y
Setting up ssmtp (2.64-4) ...
hostname: Name or service not known
dpkg: error processing ssmtp (--configure):
 subprocess installed post-installation script returned error exit status 1
configured to not write apport reports
                                      Errors were encountered while processing:
E: Sub-process /usr/bin/dpkg returned an error code (1)
2019-05-18 22:23:14
Source Share
Answers: 2

I'm presuming that you set your system is host name to "debian" when establishing it up. The installer needs to have included an access for that to /etc/hosts, yet it appears to not exist any kind of longer.

Add an access similar to this, if you do not see a line with "debian" on it currently:    debian

You'll need to start your full-screen editor with sudo to be permitted to conserve the adjustments.

2019-05-21 07:54:17

The failing is unconnected to ffmpeg, it results from ssmtp. When you ran apt-get install ffmpeg, you currently had the ssmtp plan in an unpacked, yet not totally - mounted state, which in Debian terms is called "mounted yet not set up". That configuration stage mostly runs the plan is postinst manuscript, which commonly signs up the plan is parts with the ideal solution (common collections, food selection access, etc). When apt-get install has actually ended up mounting (i.e. unboxing) the plans called on the command line and also their dependences, it "sets up" every plan (the underlying dpkg command is dpkg --configure --pending).

Warren Young has already explained why

2019-05-21 06:54:18