• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Issue Dist-Upgrade Debian 11 to Debian 12 fails

OGR

New Pleskian
Server operating system version
Debian 11.11 x86_64
Plesk version and microupdate number
Plesk Obsidian 18.0.65.2
The upgrade from Debian 11 to Debian 12 fails after the successful reboot at step 17 when using this guide:


Code:
plesk installer update --skip-cleanup

The command fails with these errors:
Code:
Unpacking libodbc2:amd64 (2.3.11-2+deb12u1) ...
dpkg: error processing archive /tmp/apt-dpkg-install-KzzUiP/12-libodbc2_2.3.11-2+deb12u1_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libodbc.so.2.0.0', which is also in package libodbc1:amd64 2.3.11-3
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

# and further down...

Errors were encountered while processing:
 /tmp/apt-dpkg-install-KzzUiP/12-libodbc2_2.3.11-2+deb12u1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
/usr/bin/sw-engine: error while loading shared libraries: libaps.so.1: cannot open shared object file: No such file or directory

The libodbc1 package seemingly cannot be removed when trying to install libodbc2. The following dependencies for libodbc1 are installed:
  • plesk-php74-odbc, plesk-php81-odbc and plesk-php82-odbc
  • plesk-librdbmspp
I retried after uninstalling the PHP dependencies, but the "plesk-librdbmspp" is needed by "libaps" and that is needed by "sw-engine". Forcing a removal would basically remove all of Plesk. The problem seems to be the same as in this topic but it wasn't properly resolved there because completely uninstalling Plesk is not a solution.

Luckily this is a VM, so I have rolled it back to before starting the upgrade process for the time being.

Is there a proper way to fix this problem?
 
try aptitude instead, it should be able to provide suggestions how to fix this
 
I am using aptitude for this. It wasn't able to provide a solution that doesn't completely remove Plesk.
 
Back
Top