Your message dated Tue, 18 Dec 2018 13:06:18 +0100
with message-id <[email protected]>
and subject line Re: Bug#916763: php-defaults: PHP 7.2 extensions no longer
available
has caused the Debian Bug report #916763,
regarding php-defaults: PHP 7.2 extensions no longer available
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
916763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916763
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: php-defaults
Version: 68
Severity: important
Dear Maintainer,
I've recently tried to use a PHP application on my Debian Testing system, only
to find the PHP SOAP extension missing. I tried to install it as php7.2-soap,
which isn't available, and as php-soap, which forces me to install php 7.3.
After some digging I've found bug #911673 which I believe to be the cause of
this.
Does this mean that only 7.0 and 7.3 is now provided by debian (stable and
testing respectively)? Because one of them is EOL and the other one is 12 days
old as of writing this message - may I ask (as a complete novice to debian
development...), why should there be no middle ground between obsolete and
bleeding edge?
Many PHP packages are not yet ready for 7.3 (I know it shouldn't break
anything, but packages are packages...), so that forces people to use 7.0,
which isn't supported anymore...
Thanks,
Marek Dědič
P.S.: I am new to the Debian bug tracker, if I reported this to the wrong
package or somehow did it improperly, please do tell me.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing'), (400, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.18.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Quoting https://wiki.debian.org/DebianTesting
“Debian testing is the current development state of the next stable Debian
distribution."
There’s no need to have “middle” ground. Debian is not a rolling distribution.
Ondrej
--
Ondřej Surý
[email protected]
> On 18 Dec 2018, at 12:28, Marek Dědič <[email protected]> wrote:
>
> Source: php-defaults
> Version: 68
> Severity: important
>
> Dear Maintainer,
>
> I've recently tried to use a PHP application on my Debian Testing system, only
> to find the PHP SOAP extension missing. I tried to install it as php7.2-soap,
> which isn't available, and as php-soap, which forces me to install php 7.3.
> After some digging I've found bug #911673 which I believe to be the cause of
> this.
>
> Does this mean that only 7.0 and 7.3 is now provided by debian (stable and
> testing respectively)? Because one of them is EOL and the other one is 12 days
> old as of writing this message - may I ask (as a complete novice to debian
> development...), why should there be no middle ground between obsolete and
> bleeding edge?
>
> Many PHP packages are not yet ready for 7.3 (I know it shouldn't break
> anything, but packages are packages...), so that forces people to use 7.0,
> which isn't supported anymore...
>
> Thanks,
> Marek Dědič
>
> P.S.: I am new to the Debian bug tracker, if I reported this to the wrong
> package or somehow did it improperly, please do tell me.
>
>
>
> -- System Information:
> Debian Release: buster/sid
> APT prefers testing
> APT policy: (500, 'testing'), (400, 'unstable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.18.0-3-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
--- End Message ---
