Your message dated Sun, 22 May 2016 10:26:17 +0000
with message-id <[email protected]>
and subject line Bug#821531: fixed in loganalyzer 3.6.6+dfsg-3
has caused the Debian Bug report #821531,
regarding loganalyzer: PHP 7.0 Transition
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.)
--
821531: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821531
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: loganalyzer
Version: 3.6.6+dfsg-2
Severity: important
User: [email protected]
Usertags: php7.0-transition
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Dear maintainer(s),
this bug is a part of ongoing php7.0 transition. It is filled as
important, but the severity will be bumped to serious within quite short
(~month) timeframe as the transition was announced almost 3 months ago.
The loganalyzer package currently depends on libapache2-mod-php5 php5
php5-cgi .
PHP 7.0 has landed in unstable with substantial changes to the packaging:
1. Every package built from src:phpMAJOR.MINOR now include
phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm.
2. Accompanying src:php-defaults builds 1:1 mapping to a default
MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm. When you
specify a dependency, please use the generic name, unless you
absolutely know that won't work for you.
3. Every path in the system has been changed to a versioned, e.g.
/etc/php5/cli is now /etc/php/7.0/cli
4. dh_php5 is now dh_php
5. php-pear is not built from independent source package.
6. master-7.0 branches of several extensions (php-apcu, xdebug,
php-apcu-bc) can be used as a template how to change the PHP
extension packaging. It's mostly cut&paste since the d/rules tries
to figure-out most of the variables from debian/ directory.
7. pkg-php-tools package now supports PHP 7.0 packaging and if your
package uses pkg-php-tools a simple binNMU is all it might need
8. PHP 7.0 has changed extension API, so most-if-not-all extensions
need work from upstream to be compatible with PHP 7.0.
9. We expect to ship next Debian release (stretch) only with PHP
7.0, that means that all packages needs to be made compatible with
PHP 7.0. Fortunately the PHP 7.0 is mostly compatible with properly
maintained software. However some extensions has been deprecated
(f.e. mysql) and thus old unmaintained software will stop working
and it will have to be either patched or removed from stable Debian.
So what you need to do:
Replace every occurence of php5 with just php, e.g. if you depend on
'php5' then you just need to depend on 'php'. Also if you package a web
application and depend on specific SAPI, I would recommend depending just
on 'php' package and let the user decide whether he will install php-fpm,
libapache2-mod-php or php-cgi.
The script that was used to get the list of packages for MBF was not a
particular smart one (so it doesn't detect alternatives, etc.), so if
there's a false positive, please excuse me and just close the bug with
short explanation.
The other options that might be used with packages that don't and won't
support PHP 7.0 is to remove the software from Debian by changing the
title of this bugreport to:
RM: loganalyzer -- ROM; doesn't support PHP 7.0
reassigning it to ftp.debian.org pseudo-package and changing severity to
'normal'.
Also feel free to contact the maintainers at one of the lists:
[email protected] -- for PEAR related packages
[email protected] -- for PHP extensions
[email protected] -- main PHP packaging and catch-all
Cheers, Ondrej
- -- System Information:
Debian Release: 8.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500,
'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQJ8BAEBCgBmBQJXFUqCXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHb4sP/1BN8x//oAipV9tY7cFy+Oka
jfGcOcsNvx9oL5GtWeCkUs7FEAEz6a/BWP0Db+24oOeaiXIzhlvhKSgnCB3zOLR8
r2564EvCaGqL3bib4ytXhEuMY9fKXi2RYWte3VNC9n0ndUycrR+0NIw2ydevzhwO
9X1xLeKqHvTwRuEsWhbCc5PP2ScHxdCsgjTr6IUtKqf026Qrmv8nX6XnBGP4HWkF
BVNa5Mr9oQGPJ8Y9GWeGkzMGUHxnf8obv8Mv3dp9xOuxWejIil2W8Ga2h66cmJ+X
AjFErI94ZfEWBQnfdzAtlbRAs6KcL3lYzsouNAr44xCk7PCy8YCCx/tz1TV69Wao
0oue3QWIMq1cQURstba2auc6tY+/WmugNsvm8csGxFAsni26d8a/zFAlAIW+hZsn
Ha0nalidDLbgA2LyH+/bY0Hnu6dK1DI/FX/WghgxxXNfDz4UK/atIT0ThqBYrqdr
Q+JHqwZgn5ClN26C4deO44N60nirdlZclTB/iEi/fD7uDITNl0VJ5TeDlPXKdtlO
dErCDZsGo+gh/nOt2LWnI/i98xadeMpAZ1+tXr48OGqLp8pqFlmbjATVYPG33doU
zBPZ9YPDePgRrVSS/ksOEnKTnMZLpB6tazvij+Yx2PhPyZjkJqWOwKPSaQTEblWH
qGgKzrzI60pxgNLA2L0y
=1Xar
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Source: loganalyzer
Source-Version: 3.6.6+dfsg-3
We believe that the bug you reported is fixed in the latest version of
loganalyzer, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniel Pocock <[email protected]> (supplier of updated loganalyzer package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Sun, 22 May 2016 10:11:34 +0200
Source: loganalyzer
Binary: loganalyzer
Architecture: source all
Version: 3.6.6+dfsg-3
Distribution: unstable
Urgency: high
Maintainer: Debian Monitoring Maintainers
<[email protected]>
Changed-By: Daniel Pocock <[email protected]>
Description:
loganalyzer - web interface to syslog and event data
Closes: 821531
Changes:
loganalyzer (3.6.6+dfsg-3) unstable; urgency=high
.
* Update for PHP 7.0 support (Closes: #821531)
Checksums-Sha1:
158d22bee693fbaf82d648c50c9a142ffcb2ff21 2006 loganalyzer_3.6.6+dfsg-3.dsc
f7319096608b400dad6e4b143e8480cd2b0dbf45 12752
loganalyzer_3.6.6+dfsg-3.debian.tar.xz
dec284d8462ccf1fd9ccee676c690aa5493d9b73 482848
loganalyzer_3.6.6+dfsg-3_all.deb
Checksums-Sha256:
5cc1d108ab781d050e4babdb6307c777a09b8c5f8dca46e748d5745350c375a1 2006
loganalyzer_3.6.6+dfsg-3.dsc
375c071dc4b403f0c5a1214e88e69dc0b0df26d346158088bb9b2957aaef3b86 12752
loganalyzer_3.6.6+dfsg-3.debian.tar.xz
39d92859078317c1e7c83ebe8d0cb6dde52add82e706c65cce7c367197362e67 482848
loganalyzer_3.6.6+dfsg-3_all.deb
Files:
69e97151701568f0b1a54d985b9d003b 2006 net optional loganalyzer_3.6.6+dfsg-3.dsc
0e162df5c2e6b4c7bfb88cb2e9af48d6 12752 net optional
loganalyzer_3.6.6+dfsg-3.debian.tar.xz
8bf8facbb239c6d5045d0ca63d6cca0b 482848 net optional
loganalyzer_3.6.6+dfsg-3_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCAAGBQJXQWqHAAoJEGxlgOd711bEG4AP/31LXwA2Xy7j9j1vpxFtltTF
PiLhk+EdumGpQ4giu8pGQ7I4TuMBxfEXw0ruCqKZ1YgRc0TGsuLrK+1R2za6WgnR
azyWSKCTaSOtaw92n3mMixPzLw1s4dTZ5ZDX4zJBjR49MBvMZ58B9n2P8Okqofxg
7uqu16XumpLM51Vmi8qERo/cKLBspEeNBgRYlRjwjdxLFxBSdyyGjaczacVVojhJ
T+x7kqFVAq6QMOwwiKqLJ+lweAkhkZN2m6pt7m9Nyxr2HR35poc1oX8ZbsvBsRhs
bCmB+BdTQikJlR2tFdis+l1aswiexZtV5IzNycaklUXO1ALrAKdE1GIDoQwG8/Wr
Pp+EWkK1bl365tlxniEqQ7ijM+KKslgVEmZkZJ+At1CYFmUa0VB4XukWhzofW7dF
a6r3vM2yG1qqg7hZd3EWenB4lBNhmwnzB3xAGk2n0sRFnQ8l9uM8plZPtStZh9r6
Bkaf7odD9AezxjpETSP1l7PJotcCP4kTn85MHHeNG4H4eB8IXMDoj7X36B9ssqvU
QjkkSTu+iTDz+Vvje3xE2ibJ5EmWUxZSG41T5AekU02/zUKtdgOxAf2IrFS65tZQ
vOJoQCytkn615oYOklOJoFUuYOJA1FM+KchD+HY+EtGLnI47ZYg0vj5yOylGfbx4
xVQAVqGQS1rzaczpuEUn
=8FWB
-----END PGP SIGNATURE-----
--- End Message ---
