techie204
-
Posts
19 -
Joined
-
Last visited
Posts posted by techie204
-
-
Mh, I don't get it π what do you mean with "...not a sepecific version". I have the impression, I can't make myself clear or misunderstand something in generel.
Yes I was trying to remove the meta-package, because I already have a specific version installed. What I wished for is:
- I do install php8.1 and corresponding packages php8.1-{...}
- when I install froxlor, there is a dependency for php, e.g. >= 7.4
- when php8.1 is installed, then the dependency is met and NOT reliant on the installed meta-packageOn another server I do have a software installed with this dependency. I have also different versions of php installed (7.4, 8.0, 8.1), but not the meta-package (which is depending 8.1). The software checks, whether php{x.y} is installed and finds a version >= 7.4, therefore the dependency is met.
Maybe I found something more here:
# apt depends froxlor froxlor |Depends: apache2 ... |Depends: php (>= 1:7.1) |Depends: php-cgi (>= 1:7.1) Depends: php-fpm (>= 1:7.1) Depends: php-cli php5.6-cli php7.0-cli php7.1-cli php7.2-cli php7.3-cli php7.4-cli php8.0-cli php8.1-cli ...For e.g. php-cli, the other packages are referenced. And for all the php-{*} packages the meta-apckages are not needed, but the version like php8.1-cli are enough. Is it maybe here, that for php-package it is not sufficient to have php8.1 installed as with the others, because they are not in the list like that!?
-
8 minutes ago, d00p said:
Well this does not happen if you stick to the default distribution apt.sources....this is definetly a debian/apt topic you can google how to avoid installing newer major versions of specific packages
Ok, thanks for the answer. In my case this would be:
apt-mark hold phpI just don't get it, why other software does not have this issue, although dependencies are similar (php is needed, but php8.1 is enough to have). That's why I have oen step more now π It might also only be a problem in my head and I'll leave it like that π
-
1 minute ago, d00p said:
Why remove virtual/meta package? If you want to remove a specific version, specify it when invoking "apt remove"Β
I don't know why I need meta-packages. I want to stick to a certain PHP-Version and have minor updates installed automatically (unattended upgrades). With other software I always have phpx.y installed and everything is fine.
So the main reason is, that I do not want php-package to get upgraded, when they bump the version to a higher major version (then 8.2), because thenΒ everything gets mixed up.
-
On 2/15/2022 at 11:33 PM, techie204 said:
So, thats what I now did (everything else from the quoted post was already done. This leeds to meta-package php stills needs to be installed π unfortunately:
The following NEW packages will be installed: froxlor phpSeems a bit strange to me ... or am I missing something?
Hey, I try it again π does anybody have a clue, why the dependency still ist there? What I figured out right now:
Β# apt list php* --installed Listing... Done php-common/bullseye,now 2:92+0~20220117.43+debian11~1.gbpe0d14e all [installed,automatic] php8.1-bcmath/bullseye,now 8.1.4-1+0~20220320.14+debian11~1.gbp16e58c amd64 [installed] php8.1-cgi/bullseye,now 8.1.4-1+0~20220320.14+debian11~1.gbp16e58c amd64 [installed] php8.1-cli/bullseye,now 8.1.4-1+0~20220320.14+debian11~1.gbp16e58c amd64 [installed] php8.1-common/bullseye,now 8.1.4-1+0~20220320.14+debian11~1.gbp16e58c amd64 [installed] php8.1-curl/bullseye,now 8.1.4-1+0~20220320.14+debian11~1.gbp16e58c amd64 [installed] php8.1-fpm/bullseye,now 8.1.4-1+0~20220320.14+debian11~1.gbp16e58c amd64 [installed] php8.1-gd/bullseye,now 8.1.4-1+0~20220320.14+debian11~1.gbp16e58c amd64 [installed] php8.1-imap/bullseye,now 8.1.4-1+0~20220320.14+debian11~1.gbp16e58c amd64 [installed] php8.1-ldap/bullseye,now 8.1.4-1+0~20220320.14+debian11~1.gbp16e58c amd64 [installed] php8.1-mbstring/bullseye,now 8.1.4-1+0~20220320.14+debian11~1.gbp16e58c amd64 [installed] php8.1-mysql/bullseye,now 8.1.4-1+0~20220320.14+debian11~1.gbp16e58c amd64 [installed] php8.1-opcache/bullseye,now 8.1.4-1+0~20220320.14+debian11~1.gbp16e58c amd64 [installed,automatic] php8.1-readline/bullseye,now 8.1.4-1+0~20220320.14+debian11~1.gbp16e58c amd64 [installed,automatic] php8.1-xml/bullseye,now 8.1.4-1+0~20220320.14+debian11~1.gbp16e58c amd64 [installed] php8.1-zip/bullseye,now 8.1.4-1+0~20220320.14+debian11~1.gbp16e58c amd64 [installed] php8.1/bullseye,now 8.1.4-1+0~20220320.14+debian11~1.gbp16e58c all [installed] php/bullseye,now 2:8.1+92+0~20220117.43+debian11~1.gbpe0d14e all [installed,automatic]When I check on the reverse dependency for php, it seems correct with froxlor:
# apt rdepends php --installed php Reverse Depends: |Depends: froxlor (>= 1:7.1) Depends: froxlor (>= 1:8.0)-> php8.1 is installed >=8.0, but when I try to uninstall meta-package, the following happens again:
# apt remove php Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: php-cgi php-json The following packages will be REMOVED: php The following NEW packages will be installed: php-cgi php-jsonphp8.1-cgi is also installed, php8.1-json doesn't exist anymore, as stated somewhere above. Froxlor-Version now is updated to 0.10.34 from debian-repo.
Anybody a clue?
-
On 2/10/2022 at 3:44 PM, γΏγγ said:
Remove PHP
sudo apt remove php*PHP install
1. sudo apt install php8.1 php8.1-{mysql,cli,cgi,common,imap,ldap,xml,fpm,curl,mbstring,zip,gd,bcmath}Froxlor Download & Install
1. wget https://files.froxlor.org/testing/froxlor-0.10.33-2.deb 2. sudo apt install path/froxlor-0.10.33-2.debSo, thats what I now did (everything else from the quoted post was already done. This leeds to meta-package php stills needs to be installed π unfortunately:
The following NEW packages will be installed: froxlor phpSeems a bit strange to me ... or am I missing something?
-
22 minutes ago, d00p said:
So I did a bit of testing. Problem seems to be with php8.0, for 8.1 debian again provides a php8.1-json (virtual?) package.
What DID work though for php8.0 (and removal of 7.4) is having both installed and then, before trying to remove just run:
Βapt-mark hold froxlor
then - at least in my case - the froxlor package won't get removed
This leads to other unexpected problems π I will check this all tonight again and try it, after making the necessary backups. Thanks in advance.
-
I was asking because starting with the removal, it says the following:
The following packages were automatically installed and are no longer required: courier-authlib default-mysql-client default-mysql-server expect galera-3 libc-client2007e libcgi-fast-perl libcgi-pm-perl libconfig-inifiles-perl libcourier-unicode4 libdbd-mysql-perl libdbi-perl libencode-locale-perl libfcgi-perl libgd3 libhtml-parser-perl libhtml-tagset-perl libhtml-template-perl libhttp-date-perl libhttp-message-perl libio-html-perl libjbig0 libjpeg62-turbo liblwp-mediatypes-perl libonig5 libsnappy1v5 libtcl8.6 libterm-readkey-perl libtiff5 libtimedate-perl libtk8.6 libwebp6 libxslt1.1 libxss1 libzip4 maildrop mariadb-client-10.3 mariadb-client-core-10.3 mariadb-server-10.3 mariadb-server-core-10.3 mlock php-common socat tcl-expect tcl8.6 tk8.6 webalizerWhen autoremoving these packages with --purge, then also the databases are purged, no?
Shouldn't it be possible to clean up php without autoremoving/autopurging everything else? Then the dependencies should be fine, too, no?
-
Does this keep all froxlor-configurations, accounts, mails and so on? (especially with the autopurge above I'm quite concerned!)
Actually for completeness I also should remove all php*-packages, no?
"New Package" and "sury" are already installed. What I realised now is that with your PHP-install there are 2 packages not installed right now: fpm and ldap ... but since we only use mails on the server, it should not be the problem we have here.
-
Yes, it is:
# php -v PHP 8.1.2 (cli) (built: Jan 27 2022 12:20:56) (NTS)The things in the post before I do not get completely π but I see, that actually the meta-package should be provided:
# apt-cache show php8.1 Package: php8.1 Version: 8.1.2-1+0~20220127.12+debian10~1.gbpe46588 ... Depends: libapache2-mod-php8.1 | php8.1-fpm | php8.1-cgi, php8.1-common Provides: phpΒ
-
I installed the package and now it was possible to uninstall the 7.4-packages. But it lead to another meta-package to be installed:
The following additional packages will be installed: php-json The following packages will be REMOVED: php7.4-common php7.4-jsonStill doing it, the following output came, but software still works:
dpkg: php7.4-json: dependency problems, but removing anyway as you requested: froxlor depends on php-json | php (>= 1:8.0); however: Package php-json is not configured yet. Package php7.4-json which provides php-json is to be removed. Package php is not installed. Version of php on system, provided by php8.1:all, is <none>.
Thanks for the changes!
Anyway. I still don't get the dependency of the meta-packages:php-cgi/buster,now 2:8.1+92+0~20220117.43+debian10~1.gbpe0d14e all [installed,automatic] php-json/buster,now 2:8.1+92+0~20220117.43+debian10~1.gbpe0d14e all [installed,automatic]The problem is, that when they bump the meta-packages to a newer version, it's supposed to be installed (and with autoupdates it will) and then I do have a mixed setup π
1. php-json seems to be integrated in PHP in general and doesn't need an extra install anymore since 8.0 (as I wrote above)
2. I don't get the need for php-cgi, since php8.1-cgi is installedIf this could be changed also, it would be a charme π but maybe I'm not getting the structure or dependencies in other parts. Thanks already for all!
-
Thank you very much.
-
I edited the above post since I now found the problem in the dependencies, I hope π still cannot fix it on my own, I think.
-
Thanks for your answer and question. I dont' get it actually π thought it might work with 8.1, but I do have the same problem.
php-packages installed:
php8.1 php8.1-bcmath php8.1-cgi php8.1-cli php8.1-common php8.1-curl php8.1-gd php8.1-imap php8.1-mbstring php8.1-mysql php8.1-opcache php8.1-readline php8.1-xml php8.1-zipFrom the 7.4-branch still installed, but I'd like to remove:
php7.4-common php7.4-jsonIf I want to remove them, apt is trying to uninstall froxlor:
# apt remove php7.4-common ... The following packages will be REMOVED: froxlor php7.4-common php7.4-jsonFurthermore I do have the following meta-packages installed:
php-cgi/buster,now 2:8.1+92+0~20220117.43+debian10~1.gbpe0d14e all [installed,automatic] php-common/buster,now 2:92+0~20220117.43+debian10~1.gbpe0d14e all [installed,automatic]For php-common I do understand that it's ok (and obviously also needed as meta-package for froxlor and php in general!), since version numbering is not increasing when a new php-major-version comes out (I mean it's not dragging new php-version), ... but for php-cgi!? When I do want to remove meta-package, then php-package isΒ supposed to be installed!?
# apt remove php-cgi ... The following packages will be REMOVED: php-cgi The following NEW packages will be installed: phpAs dependency it might be necessary this way:
# apt depends froxlor --installed ... |Depends: php-cgi (>= 1:7.1)This package again seems to be dependent on different pecls, that are required: cli bcmath curl mbstring mysql xml zip
But!!! as also json, which is only available till 7.4!!! and not in 8.0/8.1: https://php.watch/versions/8.0/ext-jsonHow can this be fixed?
-
I wanted to clean up our system today since we only use one php-version (now 8.0). Unfortunately I cannot delete 7.4 since it would uninstall froxlor package also. From what I found I assume the dependency of froxlor to php-cgi is relevant!? But why isn't it using the php8.0-cgi package? Or do I miss something?
# apt remove php7.4* The following packages will be REMOVED: froxlor libapache2-mod-php7.4 php7.4 php7.4-bcmath php7.4-cgi php7.4-cli php7.4-common php7.4-curl php7.4-gd php7.4-imap php7.4-json php7.4-mbstring php7.4-mysql php7.4-opcache php7.4-readline php7.4-xml php7.4-zipI don't actually know if it has something to do with this, but had problems with meta-packages before and can't figure this one out now:
# apt depends froxlor --installed ... |Depends: php-cgi (>= 1:7.1) ...Anyway, how can I uninstall the old PHP version without uninstalling froxlor!?
Uninstall unused PHP-versions
in General Discussion
Posted
No problem, thanks for your work! I also do not want to overcomplicate things and I am not a pro in any of this π sorry.
What I would wonder is now the difference for the above mentioned packages php and php-cli (and maybe also php-fpm)-> all are required from froxlor, but with cli and fpm it is enough to have php8.1-* installed, with php not -> that seems strange. Maybe somebody else knows one day why this is like that π thanks anyway for the help!