• 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.

Updater detects the need to upgrade, but no newer version exists

S

stoilis

Guest
Hello,

after upgrading to version 8.0.1 from 7.5.4 in a Debian box, I have this strange issue.

The updater in Plesk claims that for packages "Apache ASP support" and "Apache mod_python module", an update is available.

However, when I mark these packages for upgrade, I receive the following e-mail. I snipped the top of it for brevity, but I can provide it whole, if needed.

Building Dependency Tree...
libapache-asp-perl is already the newest version.
libapache2-mod-python is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Installation done.

I have the following versions currently installed of these packages:
libapache2-mod-python 3.1.3-3
libapache-asp-perl 2.57-3

Is there anything I can do to solve this problem? Any help will be greatly appreciated.

Thank you in advance.
 
Found the problem. It is actually a bug of Plesk Auto Installer, as far as I can see.

In my /etc/apt/sources.list, I have includes the testing repositories of debian, besides the stable ones, although the default distribution for the packages I install is Debian. This essentially means that I can enjoy a stable system but with access to more recent packages, when necessery.

Unfortunateley, Plesk Auto Installer doesn't understand which is the default release of the current system, it just detects newer versions of the mentioned packages and prompts that an upgrade is neededto install them.

Since the system is configured to use packages from stable by default, unless explicitly told to do otherwise, the upgrade process doesn't detect any newer installable version, so quits without error.

Commeting out the testing related lines from my sources file, makes the installer behave normal.
 
Back
Top