package clamav-freshclam 0.99.2+dfsg-0ubuntu0.16.04.1 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
clamav (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Just by installing update manager
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: clamav-freshclam 0.99.2+
ProcVersionSign
Uname: Linux 4.10.0-28-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Mon Aug 7 15:46:33 2017
ErrorMessage: vereistenproblemen - blijft ongeconfigureerd
InstallationDate: Installed on 2017-06-06 (61 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
ProcCmdline: BOOT_IMAGE=
RelatedPackageV
dpkg 1.18.4ubuntu1.2
apt 1.2.20
SourcePackage: clamav
Title: package clamav-freshclam 0.99.2+
UpgradeStatus: No upgrade log present (probably fresh install)
modified.
modified.
modified.
modified.
modified.
modified.
modified.
Peter Dumoulin (peterdumoulin) wrote : | #1 |
- AptOrdering.txt Edit (1.9 KiB, text/plain; charset="utf-8")
- Dependencies.txt Edit (4.6 KiB, text/plain; charset="utf-8")
- Df.txt Edit (630 bytes, text/plain; charset="utf-8")
- Dmesg.txt Edit (64.1 KiB, text/plain; charset="utf-8")
- DpkgHistoryLog.txt Edit (1.6 KiB, text/plain; charset="utf-8")
- DpkgTerminalLog.txt Edit (6.1 KiB, text/plain; charset="utf-8")
- JournalErrors.txt Edit (25.4 KiB, text/plain; charset="utf-8")
- KernLog.txt Edit (2.7 KiB, text/plain; charset="utf-8")
- ProcCpuinfoMinimal.txt Edit (1.1 KiB, text/plain; charset="utf-8")
Joshua Powers (powersj) wrote : | #2 |
Joshua Powers (powersj) wrote : | #3 |
Thank you for taking the time to file a bug report.
It looks like the install is not complete. Can you try running:
$ apt install -f
to see if the install then completes. If not, what error message gets
printed out then?
Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
am marking this bug as "Incomplete". We would be grateful if you would:
provide a more complete description of the problem, explain why you
believe this is a bug in Ubuntu rather than a problem specific to your
system, and then change the bug status back to "New".
For local configuration issues, you can find assistance here:
http://
Changed in clamav (Ubuntu): | |
status: | New → Incomplete |
Peter Dumoulin (peterdumoulin) wrote : Re: [Bug 1709117] Re: package clamav-freshclam 0.99.2+dfsg-0ubuntu0.16.04.1 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd | #4 |
Dear Joshua,
I run " apt install -f" and got the following output:
*quote*
peter@peter-
[sudo] wachtwoord voor peter:
Pakketlijsten worden ingelezen... Klaar
Boom van vereisten wordt opgebouwd
De statusinformatie wordt gelezen... Klaar
De volgende pakketten zijn automatisch geïnstalleerd en zijn niet langer
nodig:
gir1.
libgoocanvas
linux-
linux-
linux-
linux-
linux-
linux-
linux-
linux-
linux-
linux-
linux-
linux-
linux-
python-enchant python-numpy python-pil python-renderpm python-reportlab
python-
Gebruik 'sudo apt autoremove' om ze te verwijderen.
0 opgewaardeerd, 0 nieuw geïnstalleerd, 0 te verwijderen en 126 niet
opgewaardeerd.
31 niet volledig geïnstalleerd of verwijderd.
Er moeten 58,4 kB/1140 kB aan archieven opgehaald worden.
Na deze bewerking zal er 0 B extra schijfruimte gebruikt worden.
Ophalen:1 http://
clamav-base all 0.99.2+
58,4 kB opgehaald in 0s (777 kB/s)
dpkg: fout bij verwerken van pakket libssl1.0.0:amd64 (--configure):
pakket libssl1.0.0:amd64 is niet gereed voor configuratie
kan het niet configureren (huidige status 'half-installed')
dpkg: fout bij verwerken van pakket clamav-base (--configure):
pakket clamav-base is niet gereed voor configuratie
kan het niet configureren (huidige status 'half-installed')
dpkg: vereistenproblemen verhinderen de configuratie van clamav-freshclam:
clamav-freshclam is afhankelijk van clamav-base (>=
0.99.2+
Pakket clamav-base is niet geïnstalleerd.
clamav-freshclam is afhankelijk van libssl1.0.0 (>= 1.0.0); maar:
Pakket libssl1.0.0:amd64 is niet geïnstalleerd.
dpkg: fout bij verwerken van pakket clamav-freshclam (--configure):
vereistenprob
Er is geen apport-verslag weggeschreven omdat de foutmelding aangeeft
dat de fout het gevolg is van een eerdere mislukking.
weggeschreven omdat het maximum aantal verslagen (MaxReports) al is bereikt
geen apport-verslag weggeschreven omdat het maximum aantal verslagen
(MaxReports) al is bereikt
E: Sub-process /usr/bin/dpkg ...
Peter Dumoulin (peterdumoulin) wrote : | #5 |
I really don't know whether this is an Ubuntu failer or a system failer. The point is that every time I try to recover clamav-base, the system returns an error. Tried also " sudo apt-get purge clamav-base clamav then sudo apt-get install clamav-base clamav." it returns with error (1)
Changed in clamav (Ubuntu): | |
status: | Incomplete → New |
Joshua Powers (powersj) wrote : | #6 |
Hi Peter, thanks for following-up.
> Package libssl1.0.0: amd64 is not installed.
Can you get the output of:
`apt-cache policy libssl1.0.0`
Changed in clamav (Ubuntu): | |
status: | New → Incomplete |
Peter Dumoulin (peterdumoulin) wrote : | #7 |
Hi Joshua: the result of the "apt cash policy .... " Thanks so far
peter@peter-
libssl1.0.0:
Geïnstalleerd: 1.0.2g-1ubuntu4.6
Kandidaat: 1.0.2g-1ubuntu4.8
Versietabel:
1.
500 http://
*** 1.0.2g-1ubuntu4.6 500
500 http://
100 /var/lib/
1.
500 http://
peter@peter-
Changed in clamav (Ubuntu): | |
status: | Incomplete → New |
Joshua Powers (powersj) wrote : | #8 |
Thanks, this seems like something is just not getting configured. Willing to try:
sudo dpkg --configure -a --force-all
sudo apt-get clean
sudo apt-get update
sudo apt-get install -f
Peter Dumoulin (peterdumoulin) wrote : | #9 |
Dear Joshua
it does not work as you can see. The error code (1) returns at the install command
peter@peter-
[sudo] wachtwoord voor peter:
dpkg: linux-headers-
linux-
Instellen van linux-headers-
dpkg: clamav-freshclam: vereistenproblemen, maar wordt toch geconfigureerd zoals u vroeg:
clamav-freshclam is afhankelijk van clamav-base (>= 0.99.2+
Pakket clamav-base is niet geïnstalleerd.
clamav-freshclam is afhankelijk van libssl1.0.0 (>= 1.0.0); maar:
Pakket libssl1.0.0:amd64 is niet geïnstalleerd.
Instellen van clamav-freshclam (0.99.2+
Configuratiebestand '/etc/apparmor.
Zoals door u gevraagd, wordt het nieuwe configuratiebestand geïnstalleerd.
Configuratiebestand '/etc/init.
Zoals door u gevraagd, wordt het nieuwe configuratiebestand geïnstalleerd.
Configuratiebestand '/etc/logcheck/
Zoals door u gevraagd, wordt het nieuwe configuratiebestand geïnstalleerd.
Configuratiebestand '/etc/network/
Zoals door u gevraagd, wordt het nieuwe configuratiebestand geïnstalleerd.
Configuratiebestand '/etc/network/
Zoals door u gevraagd, wordt het nieuwe configuratiebestand geïnstalleerd.
Configuratiebestand '/etc/ppp/
Zoals door u gevraagd, wordt het nieuwe configuratiebestand geïnstalleerd.
Configuratiebestand '/etc/ppp/
Zoals door u gevraagd, wordt het nieuwe configuratiebestand geïnstalleerd.
dpkg: libfreerdp-
libfreerdp-
libfreerdp-
libfreerdp-
Instellen van libfreerdp-
dpkg: libwinpr-
libwinpr-
Pakket libssl1.0.0:amd64 is niet geïnstalleerd.
Instellen van libwinpr-
dpkg: libfreerdp-
libfreerdp-
Instellen van libfreerdp-
Instellen van linux-generic-
dpkg: linux-headers-4...
Christian Ehrhardt (paelzer) wrote : | #10 |
Hi,
I don't know if your purging and reinstall would have solved this, but at least in the initial report there were plenty of deleted conffiles.
modified.
[...]
[1] has a good summary to restore deleted conffiles.
You might want to check on all that got reported in the bug initially if they are all available (even the failed) install.
Missing those could be what makes the install fail in the first place so surely worth a check.
Furthermore something/someone has removed them, whatever further action to non conformly remove the package was taken could cause errors in regard to this context. Yet we'd need to know what has been done.
To get an insight what else might be affected the following can help:
$ dpkg --verify
This will list all modified or deleted configuration files.
Since clamav works nice on a default system chances are this helps you to find what has broekn it - like the deleted conffiles.
You might check all the listed files if those are intentional changes or issues to be fixed.
It surely has a lot of false positives (it is ok to personalize the system), but after you are ok with them but still having the issue you might report back the list here if you want.
[1]: https:/
Peter Dumoulin (peterdumoulin) wrote : | #11 |
Dear all this is the list I got from the verify command. My PC is not personalised and nothing has been deleted on purpose.
Peter
peter@peter-
[sudo] wachtwoord voor peter:
??5?????? /lib/x86_
??5?????? /lib/x86_
??5?????? /usr/lib/
??5?????? /usr/lib/
??5?????? /usr/lib/
??5?????? /usr/lib/
??5?????? /usr/lib/
??5?????? /usr/lib/
??5?????? /usr/lib/
??5?????? /usr/lib/
??5?????? /usr/lib/
??5?????? /usr/lib/
??5?????? /usr/lib/
??5?????? /usr/lib/
??5?????? /usr/share/
??5?????? /usr/lib/
??5?????? /usr/lib/
??5?????? c /etc/sane.
??5?????? /usr/lib/
??5?????? /usr/lib/
??5?????? /usr/lib/
??5?????? /usr/lib/
??5?????? /usr/lib/
??5?????? /usr/lib/
??5?????? /usr/lib/
??5?????? /usr/share/
peter@peter-
Christian Ehrhardt (paelzer) wrote : | #12 |
After translating the log of comment #9 I see that this brought you back the related config files.
I wonder what might still be in the way, maybe we can retry the clamav-base that is failing instead of all of them.
What does the following give you:
$ sudo apt remove --purge clamav-base
$ sudo apt install clamav-base
Maybe with the former things fixed this could resolve now - not sure thou as it seems we miss something of your case.
Peter Dumoulin (peterdumoulin) wrote : | #13 |
Sorry Christian it does not work. see below.
peter@peter-
[sudo] wachtwoord voor peter:
Pakketlijsten worden ingelezen... Klaar
Boom van vereisten wordt opgebouwd
De statusinformatie wordt gelezen... Klaar
De volgende pakketten zijn automatisch geïnstalleerd en zijn niet langer nodig:
gir1.
gnome-icon-theme libclamav7 libcommon-
libgoocanvas-
libtext-csv-perl libtext-csv-xs-perl libtypes-
linux-
linux-
linux-
linux-
linux-
linux-
linux-
linux-
linux-
linux-
linux-
linux-
linux-
linux-
linux-
python-enchant python-nautilus python-numpy python-pil python-renderpm
python-reportlab python-
Gebruik 'sudo apt autoremove' om ze te verwijderen.
De volgende pakketten zullen VERWIJDERD worden:
clamav* clamav-base* clamav-freshclam*
0 opgewaardeerd, 0 nieuw geïnstalleerd, 3 te verwijderen en 124 niet opgewaardeerd.
4 niet volledig geïnstalleerd of verwijderd.
Er moeten 0 B/1082 kB aan archieven opgehaald worden.
Na deze bewerking zal er 1756 kB schijfruimte vrijkomen.
Wilt u doorgaan? [J/n] j
(Database wordt ingelezen ... 519572 bestanden en mappen momenteel geïnstalleerd.)
clamav (0.99.2+
clamav-freshclam (0.99.2+
Configuratiebes
clamav-base (0.99.2+
Configuratiebes
Bezig met afhandelen van triggers voor man-db (2.7.5-1) ...
dpkg: fout bij verwerken van pakket libssl1.0.0:amd64 (--configure):
pakket libssl1.0.0:amd64 is niet gereed voor configuratie
kan het niet configureren (huidige status 'half-installed')
dpkg: vereistenproblemen verhinderen de configuratie van libclamav7:
libclamav7 is afhankelijk van libssl1.0.0 (>= 1.0.0); maar:
Pakket libssl1.0.0:amd64 is niet geïnstalleerd.
dpkg: fout bij verwerken van pakket libclamav7 (--configure):
vereistenproblemen - blijft ongeconfigureerd
Er is geen apport-verslag weggeschreven omdat de foutmeld...
Christian Ehrhardt (paelzer) wrote : | #14 |
As Joshua found in the initial check it seems to come down to the following still:
Dpkg: Error processing package libssl1.0.0: amd64 (--configure):
Package libssl1.0.0: amd64 is not ready for configuration
Can not configure (current status 'half-installed')
The dpkg configure should have resolved that half installed:
(You did already)
$ sudo dpkg --configure -a --force-all
But it didn't, while it is unlikely let's keep clamav out of the picture for now and just focus on libssl until it works correctly - that might also keep the log
# 1. get all of clamav out of the way
$ sudo apt-get remove --purge clamav-base libclamav7
# 2. fully reinstall libssl and see what it does
$ sudo apt-get install --reinstall libssl1.0.0
Report back with the full log again, while we have to translate and guess a bit - it is better than having no insight what is going on at all.
Peter Dumoulin (peterdumoulin) wrote : | #15 |
Hi Christian. I give you the result of both commands
Peter
peter@peter-
[sudo] wachtwoord voor peter:
Pakketlijsten worden ingelezen... Klaar
Boom van vereisten wordt opgebouwd
De statusinformatie wordt gelezen... Klaar
De volgende pakketten zijn automatisch geïnstalleerd en zijn niet langer nodig:
gir1.
gnome-icon-theme libcommon-
libgoocanvas-
libtext-csv-perl libtext-csv-xs-perl libtypes-
linux-
linux-
linux-
linux-
linux-
linux-
linux-
linux-
linux-
linux-
linux-
linux-
linux-
linux-
linux-
python-enchant python-nautilus python-numpy python-pil python-renderpm
python-reportlab python-
Gebruik 'sudo apt autoremove' om ze te verwijderen.
De volgende pakketten zullen VERWIJDERD worden:
clamav* clamav-base* clamav-freshclam* libclamav7*
0 opgewaardeerd, 0 nieuw geïnstalleerd, 4 te verwijderen en 124 niet opgewaardeerd.
4 niet volledig geïnstalleerd of verwijderd.
Er moeten 0 B/1082 kB aan archieven opgehaald worden.
Na deze bewerking zal er 4152 kB schijfruimte vrijkomen.
Wilt u doorgaan? [J/n] J
(Database wordt ingelezen ... 519572 bestanden en mappen momenteel geïnstalleerd.)
clamav (0.99.2+
clamav-freshclam (0.99.2+
Configuratiebes
libclamav7 (0.99.2+
clamav-base (0.99.2+
Configuratiebes
Bezig met afhandelen van triggers voor man-db (2.7.5-1) ...
Bezig met afhandelen van triggers voor libc-bin (2.23-0ubuntu9) ...
/sbin/ldconfig.
/sbin/ldconfig.
/sbin/ldconfig.
/sbin/ldconfig.
dpkg: fout bij verwerken van pakket libssl1.0.0:a...
Christian Ehrhardt (paelzer) wrote : | #16 |
Hi Peter,
so in fact this solved your issue with libssl.
You see that in regard to libssl your
$ sudo apt-get install -reinstall libssl1.0.0
worked fine and it is now ok.
You seem to have the same issue in another library as well thou.
/sbin/
So you (likely) need to do the same again but for that.
I'd assume this is part of package "nvidia-375" but pelase check to be sure with:
$ dpkg -S /usr/lib/
This will show you the owning package.
Then reinstall that package with:
$ sudo apt-get install -reinstall <pkgname>
Hopefully that resolves the last of your fail-to-configure packages.
And with that all is good again and you are ready for normal work.
Since we all read through so many output of it, you might afterwards run a
$ sudo apt-get autoremove
Peter Dumoulin (peterdumoulin) wrote : | #17 |
Christian could it be that my terminal has still no correct driver defined by linux
Peter
Pakketlijsten worden ingelezen... Klaar
Boom van vereisten wordt opgebouwd
De statusinformatie wordt gelezen... Klaar
E: Kan pakket libEGL.so.1 niet vinden
E: Kon geen enkel pakket vinden via expansie (glob) 'libEGL.so.1'
E: Kon geen enkel pakket vinden via regex 'libEGL.so.1'
peter@peter-
Christian Ehrhardt (paelzer) wrote : | #18 |
If that is what you get on the dpkg -S I asked you then you have a stray old file around that should not exist.
Was that on this?:
$ dpkg -S /usr/lib/
Peter Dumoulin (peterdumoulin) wrote : | #19 |
yes Christian it was on that.
I searches for a driver for iilama prolite x2483hsu, but probably it is not available yet
Christian Ehrhardt (paelzer) wrote : | #20 |
That means either:
- a package formerly owning that file was not cleanly removed (unlikely)
or
- that file is from a source not part of the Ubuntu archive
We have no indication of the former and can't really fix the latter.
You could check what *other* nvidia packages you have installed with:
$ dpkg -l '*nvidia*'
For the related path in Xenial I only found:
nvidia-340: /usr/lib/
nvidia-361: /usr/lib/
You need to find why/from where this extra file came and clean it up.
Be careful to not "just" remove it as it might harmstring your graphics.
Except if your system doesn't have an nvidia card at all - in that case remove it and be happy.
Peter Dumoulin (peterdumoulin) wrote : | #21 |
Christian, my PC has an NVIDIA card.
peter@peter-
Gevraagd=
| Status=
|/ Fout?=(
||/ Naam Versie Architectuur Omschrijving
+++-===
ii nvidia-375 375.66-0ubun amd64 NVIDIA binary driver - version 37
un nvidia-common <geen> <geen> (geen beschrijving beschikbaar)
un nvidia-driver- <geen> <geen> (geen beschrijving beschikbaar)
un nvidia-legacy- <geen> <geen> (geen beschrijving beschikbaar)
un nvidia-libopen <geen> <geen> (geen beschrijving beschikbaar)
un nvidia-libopen <geen> <geen> (geen beschrijving beschikbaar)
un nvidia-opencl- <geen> <geen> (geen beschrijving beschikbaar)
ii nvidia-opencl- 375.66-0ubun amd64 NVIDIA OpenCL ICD
un nvidia-persist <geen> <geen> (geen beschrijving beschikbaar)
ii nvidia-prime 0.8.2 amd64 Tools to enable NVIDIA's Prime
ii nvidia-setting 381.22-0ubun amd64 Tool for configuring the NVIDIA g
un nvidia-setting <geen> <geen> (geen beschrijving beschikbaar)
un nvidia-vdpau-d <geen> <geen> (geen beschrijving beschikbaar)
peter@peter-
Peter Dumoulin (peterdumoulin) wrote : | #22 |
is the NVIDIA GTX 1050
Peter Dumoulin (peterdumoulin) wrote : | #23 |
I could do this to download the newest driver from Nvidia:
Remove the older version of Nvidia driver
sudo apt-get purge nvidia*
Reboot the system
Download the Nvidia Driver 375.20
For 32bit
wget http://
For 64 bit
wget http://
Switch to command prompt and stop the running Graphics session. Press Ctrl+Alt+F1-F6 for switching to command prompt
sudo service lightdm stop
sudo service gdm stop
Give execute permissions to the installer
sudo chmod 755 NVIDIA-
Install the Nvidia 375.20 driver
sudo ./NVIDIA-
After successfull installation reboot the system.
Christian Ehrhardt (paelzer) wrote : | #24 |
Here you have the "out of archive" source that likely breaks it.
You have installed nvidia 375.66
ii nvidia-375 375.66-0ubun amd64 NVIDIA binary driver - version 37
Which is great and from:
$ apt-cache policy nvidia-375
nvidia-375:
Installed: (none)
Candidate: 375.66-
Version table:
375.
500 http://
500 http://
All good so far.
I expect that the manually downloaded nvidia driver with the wget collides with some of the files. But that is what happens due to out-of-archive content - we can't expect and manage what they do.
You'd have to find what the wget'ed driver installed and remove all of it.
Then purge and properly reinstall the archive managed nvidia-375 which might fix things up.
But since I don't know what this external source did I can't promise anything.
Peter Dumoulin (peterdumoulin) wrote : | #25 |
I deleted the NVIDIA
peter@peter-
dpkg-query: geen pad gevonden dat overeenkomt met /usr/lib/
peter@peter-
and now. I downloaded the 375.20 version, but it does not install
Christian Ehrhardt (paelzer) wrote : | #26 |
>
> and now. I downloaded the 375.20 version, but it does not install
>
What is the issue this time on installing the from-archive nvidia driver?
Console log and more if there is more.
Peter Dumoulin (peterdumoulin) wrote : | #27 |
Christian,
after having removed Nvidia I did the folloewing comands:
sudo apt-get remove --purge clamav-base libclamav7
sudo get autoremove
sudo apt-get install --reinstall libssl1.0.0
For a long time I got not: "system error detected"
However I have no Nvidia 375.20 installed as I could not find it in the archive.
Just installed "Nvidia x server settings" But what should it do??
Christian Ehrhardt (paelzer) wrote : | #28 |
As you can see in my output above that driver is in the restricted pocket
for licensing reasons.
$ apt-cache policy nvidia-375
nvidia-375:
Installed: (none)
Candidate: 375.66-
Version table:
375.
500 http://
amd64 Packages
500 http://
amd64 Packages
When you say you don't find it you likely have no restricted repository
enabled [1].
I thought that is default now for quite a while, but you might not have
them still due to an upgrade path?
Not sure, but if you really get no output on the Xenial system you have for:
$ apt-cache policy nvidia-375
(Please report that output)
Then consider enabling the restricted repository for drivers just like that.
The link also contains info how to add that.
After that run
$ apt update
And then the package should be available.
BTW - no need to touch libssl / clamav anymore they should be good now.
[1]:
https:/
Peter Dumoulin (peterdumoulin) wrote : | #29 |
Christian. the output
peter@peter-
[sudo] wachtwoord voor peter:
nvidia-375:
Geïnstalleerd: (geen)
Kandidaat: 375.66-
Versietabel:
375.
500 http://
500 http://
peter@peter-
Christian Ehrhardt (paelzer) wrote : | #30 |
Well that only means that the driver got updated and now is even newer on 375.66 instead of 375.20 as a while ago.
Since you said you removed all old traces of the external driver installation you can now pick up the supported version just via:
$ sudo apt install nvidia-375
That should install nvidia-375 and keep it up to date.
And if you really have removed all old clutter this will be the last you need.
Your nvidia driver libs will then only be the one of the package you now install and those should be good.
Please report back what you got on
$ sudo apt install nvidia-375
Interested to see if there are any libeEGL issues left then.
Peter Dumoulin (peterdumoulin) wrote : | #31 |
Christian
Thanks a lot for your support. It has been installed correctly.
Peter
Changed in clamav (Ubuntu): | |
status: | New → Fix Released |
From log (translated):
Dpkg: Error processing package libssl1.0.0: amd64 (--configure): 16.04.1) ; but:
Package libssl1.0.0: amd64 is not ready for configuration
Can not configure (current status 'half-installed')
Dpkg: Error Processing Clamav Base Bundle (- Configuration):
Clamav base packet is not ready for configuration
Can not configure (current status 'half-installed')
Dpkg: Requirements Preventing Configuration of Clamav-Freshclam:
Clamav freshclam is dependent on clamav base (> = 0.99.2 + dfsg-0ubuntu0.
Package clamav base is not installed.
Clamav-freshclam is dependent on libssl1.0.0 (> = 1.0.0); but:
Package libssl1.0.0: amd64 is not installed.