the crap of sury php repository and controversial problems, tips to solve and more

Let's remember the php DotDeb that did its job so well so good, and now we have. . sury's php repository ..UPDATED: check: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982574#39

The sury packages have problems but one in particular prevents you from using it, there are really two, the php-http and the php-recode, this because the newer versions of these packages only work with php 7.3 and the sury repo only packages the last of all, which leaves in evidence that it breaks the other versions. This is only the most detailed, other details make this repository very controversial.

The problem continues at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982574#39 with a very unresponsive position of the mantainer.

If you use the php sury packages you will notice their great progressive stance, but exclusive and  despot of their bad service . He boasts of making packages for Debian stable but they have serious flaws and incompatibilities and his answer is "I do for the last" .. so what does he do for Debian stable?? yeah stable means not lasted just more quite in peace.

In the past we had the excellent work of the DotDeb site and when your visit noted the anunce as follow in the picture:

"Dobdet came to an end" he says without knowing how those who use sury suffer now.

What are the most notable problems with the php sury repo?

There are two kind of situation here: for one part the moral of the Debian owrk, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982574#39 that debian mantainer is taken the debian resources for their own fame, I see well what is being done by providing an extra set of packages, but it seems to neglect the work inside debian and abuse the power outside debian.

The other problems are incompatibilities and packages that exceed the stable ones without syncing, the following list is only the most notable, there are many reasons why it is a service crap, most of the issues at github are closed with missing arguments just said "works for me" in resume or "i made for lasted" as reasons:

1. The php package has conflicts and the first was with the stable lighttpd package in debian, the issue is documented and they go through the years here: https://github.com/oerdnj/deb.sury.org/issues/ 1056 claiming that they "ask for TLS 1.3" and: what about those who already have settings? Does the devil eat them? just crap!
2. The packages have high dependency on systemd and people demanded that he was forced:  https://github.com/oerdnj/deb.sury.org/issues/1393 son of a mother (sorry if I say bitch I insult the horses), he conveniently close the issue saying that the template was not filled properly. However another one was filled: https://github.com/oerdnj/deb.sury.org/issues/1349 which also says practically "it works for me", but waith..  another one was also filled: https://github.com/oerdnj/ deb.sury.org/issues/1347 This time they told to sury packager that “focus on the change” with his “forced change”!
3. Its repo is not copyable : many comment was posted in their blog but a full filled issue was at https://github.com/oerdnj/deb.sury.org/issues/1308 and without giving explanations it just places an ambiguous link to patreon, so then the following problem comes:
4. The bastard charges to maintain it through the disguise of donations  and at the same time does not allow it to be copied, if it costs so much because he does not simply use the http system of github or sourceforge and that's it?
5. The biggest of all, segfaul due to exceeded versions https://github.com/oerdnj/deb.sury.org/issues/1442 and additionally leads to another problem https://github.com/oerdnj/deb.sury.org / issues / 1506 which was closed because it "works for me" and because no one according to him uses php 5.6 today. This problem gives because it is simply limited to using the latter without taking into account where it packages to (stable versions are assumed)

The current segfault problem

Currently sury's php-http and php-recode packages cause problems, they have problems because the version used only supports 7.3 but he compiles it for 5 and 7.4+ which makes nothing work.

https://github.com/oerdnj/deb.sury.org/issues/1506

The problem is detailed in the devuan forum http://dev1galaxy.org/viewtopic.php?pid=26272#p26272 After installing php 5.6 and 7.2 when asking for "phpinfo" it does not show up, raises with a 503 internal error. So uninstall any sury package php-pecl and it works .. the bug is only in the sury package .. because from debian it works without problems.

At the moment while venenux cannot recompile the packages (it is working on it) you must remove php5.6-http php7.4-http php7.3-http php7.2-http php-7.1-http and it works .. it is a sury package that has the bug not the php-pecl-http as it says. In the case of recode, we just have to pack an older version.