Hello, i am using server with latest ispconfig, debian etc. I used standard apt update and upgrade to update my package. But now i have two days in my terminal and ispconfig package to upgrade Remv php-memcache [8.2-2+0~20230612.31+debian11~1.gbpbf55c7] Inst php5.6-memcache [8.0+4.0.5.2+3.0.9~20170802.e702b5f9+-8+0~20230612.30+debian11~1.gbp59de0d] (1:3.0.9~20170802.e702b5f9+-1+0~20230614.3+debian11~1.gbp14ff3f bullseye/snapshots/1686755836 [amd64]) Inst php7.4-memcache [8.0+4.0.5.2+3.0.9~20170802.e702b5f9+-8+0~20230612.30+debian11~1.gbp59de0d] (1:4.0.5.2-1+0~20230614.3+debian11~1.gbpe9883d bullseye/snapshots/1686755836 [amd64]) Conf php5.6-memcache (1:3.0.9~20170802.e702b5f9+-1+0~20230614.3+debian11~1.gbp14ff3f bullseye/snapshots/1686755836 [amd64]) Conf php7.4-memcache (1:4.0.5.2-1+0~20230614.3+debian11~1.gbpe9883d bullseye/snapshots/1686755836 [amd64]) When i used standard apt upgrade and update, i just get Code: root@xx:~# apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages have been kept back: php5.6-memcache php7.4-memcache 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. Any idea what should i do for upgrade this package?
What was the first method? What show commands: Code: lsb_release -a cat /etc/debian_version Have you modified APT sources.list or apt configuration files? That is two packages. Examine why they are kept back. Start with Code: apt policy php5.6-memcache apt policy php7.4-memcache
No, i did not any changes in sources.list files or in any others config files. Always, many years i use for update my package only apt update and apt upgrade, that is all. When I used your first command i get Code: No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye 11.7 ¨ When i used your second command i get Code: apt policy php5.6-memcache apt policy php7.4-memcache php5.6-memcache: Installed: 8.0+4.0.5.2+3.0.9~20170802.e702b5f9+-8+0~20230612.30+debian11~1.gbp59de0d Candidate: 1:3.0.9~20170802.e702b5f9+-1+0~20230614.3+debian11~1.gbp14ff3f Version table: 1:3.0.9~20170802.e702b5f9+-1+0~20230614.3+debian11~1.gbp14ff3f 500 500 https://packages.sury.org/php bullseye/main amd64 Packages *** 8.0+4.0.5.2+3.0.9~20170802.e702b5f9+-8+0~20230612.30+debian11~1.gbp59de0d 100 100 /var/lib/dpkg/status php7.4-memcache: Installed: 8.0+4.0.5.2+3.0.9~20170802.e702b5f9+-8+0~20230612.30+debian11~1.gbp59de0d Candidate: 1:4.0.5.2-1+0~20230614.3+debian11~1.gbpe9883d Version table: 1:4.0.5.2-1+0~20230614.3+debian11~1.gbpe9883d 500 500 https://packages.sury.org/php bullseye/main amd64 Packages *** 8.0+4.0.5.2+3.0.9~20170802.e702b5f9+-8+0~20230612.30+debian11~1.gbp59de0d 100 100 /var/lib/dpkg/status Thank you for your help. Maybes is not compatible with debian 11.
Someone must have modified apt sources list, since packages.sury.org is added. It is not in default Debian. Show contents of /etc/apt/sources.list and contents of files in /etc/apt/sources.list.d/ -directory. I suspect those two packages have new dependencies, then ordinary apt update can not do the update. Try this command, it should just show what would be done (because --dry-run), and not write anything to disk: Code: apt full-upgrade --dry-run
Yes, to repository i add sury package, but before 2 years ago, in latest months not. When i use your command, i get Code: Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following package was automatically installed and is no longer required: php8.2-memcache Use 'apt autoremove' to remove it. The following packages will be REMOVED: php-memcache The following packages will be upgraded: php5.6-memcache php7.4-memcache 2 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. Remv php-memcache [8.2-2+0~20230612.31+debian11~1.gbpbf55c7] Inst php5.6-memcache [8.0+4.0.5.2+3.0.9~20170802.e702b5f9+-8+0~20230612.30+debian11~1.gbp59de0d] (1:3.0.9~20170802.e702b5f9+-1+0~20230614.3+debian11~1.gbp14ff3f bullseye/snapshots/1686810829 [amd64]) Inst php7.4-memcache [8.0+4.0.5.2+3.0.9~20170802.e702b5f9+-8+0~20230612.30+debian11~1.gbp59de0d] (1:4.0.5.2-1+0~20230614.3+debian11~1.gbpe9883d bullseye/snapshots/1686810829 [amd64]) Conf php5.6-memcache (1:3.0.9~20170802.e702b5f9+-1+0~20230614.3+debian11~1.gbp14ff3f bullseye/snapshots/1686810829 [amd64]) Conf php7.4-memcache (1:4.0.5.2-1+0~20230614.3+debian11~1.gbpe9883d bullseye/snapshots/1686810829 [amd64])
Code: The following packages will be REMOVED: php-memcache That is the reason the packages were kept back. Command apt update does not install new packages nor remove already installed packages, that is why it refused to do the update. If you find it OK to remove php-memcache, run the full-upgrade without the --dry-run, then the removal and updates get done. You should examine if you need php8.2-memcache, it gets removed next time you run apt autoremove. If you want to keep it, explicitly install it with apt install php8.2-memcache or mark it manually installed in another fashion, I do not recall the command now but it is in the documentation.
Hi, I have exacly same problem with all my Deb11 Web servers. Sury was installed year ago following https://www.howtoforge.com/ispconfig-php-debian/ apt full-upgrade --dry-run: Code: The following package was automatically installed and is no longer required: php8.2-memcache Use 'sudo apt autoremove' to remove it. The following packages will be REMOVED: php-memcache The following packages will be upgraded: php7.4-memcache php8.2-memcache 2 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. Remv php-memcache [8.0+4.0.5.2+3.0.9~20170802.e702b5f9+-8+0~20221209.29+debian11~1.gbp59de0d] Inst php7.4-memcache [8.0+4.0.5.2+3.0.9~20170802.e702b5f9+-8+0~20221209.29+debian11~1.gbp59de0d] (1:4.0.5.2-1+0~20230716.5+debian11~1.gbpe9883d bullseye [amd64]) Inst php8.2-memcache [8.0+4.0.5.2+3.0.9~20170802.e702b5f9+-8+0~20221209.29+debian11~1.gbp59de0d] (8.2-2+0~20230716.32+debian11~1.gbpbf55c7 bullseye [amd64]) Conf php7.4-memcache (1:4.0.5.2-1+0~20230716.5+debian11~1.gbpe9883d bullseye [amd64]) Conf php8.2-memcache (8.2-2+0~20230716.32+debian11~1.gbpbf55c7 bullseye [amd64]) So the right thing to do now is to run it without dry-run? thanks
It depends. What do you want from the update? If, like you wrote, "I have exacly same problem", exactly same actions should solve the situation. Like was explained in #6.
I simmply want to restore apt update operations. I performed the full-upgrade, then installed memcache. Not php8.2-memcache because full-upgrade did leave it Hope it will be ok, I cannot understand very well all underline implications Code: Removing php-memcache (8.0+4.0.5.2+3.0.9~20170802.e702b5f9+-8+0~20221209.29+debian11~1.gbp59de0d) ... (Reading database ... 54129 files and directories currently installed.) Preparing to unpack .../php7.4-memcache_1%3a4.0.5.2-1+0~20230716.5+debian11~1.gbpe9883d_amd64.deb ... Unpacking php7.4-memcache (1:4.0.5.2-1+0~20230716.5+debian11~1.gbpe9883d) over (8.0+4.0.5.2+3.0.9~20170802.e702b5f9+-8+0~20221209.29+debian11~1.gbp59de0d) ... Preparing to unpack .../php8.2-memcache_8.2-2+0~20230716.32+debian11~1.gbpbf55c7_amd64.deb ... Unpacking php8.2-memcache (8.2-2+0~20230716.32+debian11~1.gbpbf55c7) over (8.0+4.0.5.2+3.0.9~20170802.e702b5f9+-8+0~20221209.29+debian11~1.gbp59de0d) ... Setting up php8.2-memcache (8.2-2+0~20230716.32+debian11~1.gbpbf55c7) ... Setting up php7.4-memcache (1:4.0.5.2-1+0~20230716.5+debian11~1.gbpe9883d) ... Processing triggers for php8.2-phpdbg (8.2.8-1+0~20230716.25+debian11~1.gbp5cf2f6) ... Processing triggers for php8.2-cli (8.2.8-1+0~20230716.25+debian11~1.gbp5cf2f6) ... Processing triggers for php8.2-fpm (8.2.8-1+0~20230716.25+debian11~1.gbp5cf2f6) ... NOTICE: Not enabling PHP 8.2 FPM by default. NOTICE: To enable PHP 8.2 FPM in Apache2 do: NOTICE: a2enmod proxy_fcgi setenvif NOTICE: a2enconf php8.2-fpm NOTICE: You are seeing this message because you have apache2 package installed. Processing triggers for libapache2-mod-php8.2 (8.2.8-1+0~20230716.25+debian11~1.gbp5cf2f6) ... Processing triggers for php8.2-cgi (8.2.8-1+0~20230716.25+debian11~1.gbp5cf2f6) ... Processing triggers for php7.4-cli (1:7.4.33-6+0~20230609.83+debian11~1.gbp32abef) ... Processing triggers for php7.4-fpm (1:7.4.33-6+0~20230609.83+debian11~1.gbp32abef) ... NOTICE: Not enabling PHP 7.4 FPM by default. NOTICE: To enable PHP 7.4 FPM in Apache2 do: NOTICE: a2enmod proxy_fcgi setenvif NOTICE: a2enconf php7.4-fpm NOTICE: You are seeing this message because you have apache2 package installed. Processing triggers for php7.4-cgi (1:7.4.33-6+0~20230609.83+debian11~1.gbp32abef) ...
Then you should read this thread from the beginning and examine the situation with the commands shown in there. What is curious is in #7 you showed Code: The following package was automatically installed and is no longer required: php8.2-memcache Use 'sudo apt autoremove' to remove it. but in #9 command (you did not show what command was issued) output shows php8.2-memcache was unpacked and set up. Is this only part of the output of that mystery command? Is php8.2-memcache still shown as ripe for autoremove?
#9 was Code: apt full-upgrade after that, apt reports that all packages are ok and updated, and that there isn't nothing to do
