• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Unsure about packages

Celexi

New Pleskian
Hello,

I accidentally removed some packages while installing something on my server by too quickly saying yes without noticing packages were going to be removed, i ran the plesk-installer which says nothing is missing. But as i am not entirely sure, would anyone mind telling me if the following packages removed would be needed for plesk or the new one installed would conflict with plesk?

The following NEW packages will be installed:
libc-ares2{a} libpython3.2{a} python3.2{a} python3.2-minimal{a} tcl8.5{a}
znc znc-extra{a} znc-perl{a} znc-python{a} znc-tcl{a}
The following packages will be REMOVED:
cpp-4.4{u} libbind9-60{u} libboost-iostreams1.42.0{u} libdb4.7{u}
libdns69{u} libgmp3c2{u} libisc62{u} libisccc60{u} libisccfg62{u}
liblwres60{u} libmysqlclient16{u} libssl0.9.8{u} lzma{u}
python-support{u} python2.6{u} python2.6-minimal{u}
0 packages upgraded, 10 newly installed, 16 to remove and 0 not upgraded.


Thanks!
 
libmysqlclient and libssl are probably required.
On Debian-based OSes removing python 2.x will most likely break some fraction of Plesk backend utilities. If # plesk bin php_setting -u fails, this is likely the case.
You might also have some issues with BIND DNS server if you use one, however I'm not sure on this point.
 
Back
Top