Packages kept back after OS Upgrade

Community Support
1

Hello all,

On an older server, I used to have Ubuntu 20.04 LTS + HestiaCP, where I had already run /usr/local/hestia/install/upgrade/manual/migrate_phpmyadmin.sh

When I used to run apt update && apt upgrade I wouldn’t get any messages about phpmyadmin (or other packages) being kept back.

After I upgraded to Ubuntu 22.04 LTS and running apt update && apt upgrade I get the following:

The following packages have been kept back:
php-phpmyadmin-sql-parser php-psr-container php-symfony-service-contracts php-twig phpmyadmin

What is the best course of action now?

Package versions:

php-phpmyadmin-sql-parser/now 4.6.1-2 all [installed,upgradable to: 5.4.1-2]
php-psr-container/now 1.0.0-2 all [installed,upgradable to: 2.0.2-1]
php-symfony-service-contracts/now 1.1.8-1 all [installed,upgradable to: 2.4.0-1ubuntu2]
php-twig/now 2.12.5-1 all [installed,upgradable to: 3.3.8-2ubuntu4]
phpmyadmin/now 4:4.9.5+dfsg1-2 all [installed,upgradable to: 4:5.1.1+dfsg1-5ubuntu1]
2

That is fine we download phpmyadmin directly from source.,

if we remove them via apt remove it wil also remove php …

Keeping it back and preventing it from updating prevent those issues

3

Hey @eris and thank you for the answer.

Yes, I am familiar with the reason why the package is kept back. It made me wonder though, why I did NOT get those warnings on Ubuntu version 20.04 but I get them now on 22.04. Maybe because on 20.04 there were no newer versions of the packages to update to, but now on 22.04 there are and thus the warning messages?

One more -ultra low priority- question. I understand that the package phpmyadmin/now 4:4.9.5+dfsg1-2 depends on other packages to work. So I guess phpmyadmin from source also needs those other packages to work, right? But all those packages will never be updated because phpmyadmin/now 4:4.9.5+dfsg1-2 would also need to be updated but it is held back on purpose. What happens when there are security fixes in those other packages? Which will never me installed via apt for the above reasons. How is HestiaCP handling this.