• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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