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

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