Your message dated Sat, 21 May 2016 16:25:17 +0000
with message-id <e1b49ih-0000as...@franck.debian.org>
and subject line Bug#821509: fixed in kcachegrind 4:16.04.0-1
has caused the Debian Bug report #821509,
regarding kcachegrind-converters: 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 ow...@bugs.debian.org
immediately.)
--
821509: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821509
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kcachegrind-converters
Version: 4:15.08.3-1
Severity: important
User: pkg-php-ma...@lists.alioth.debian.org
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 kcachegrind-converters package currently depends on php5 php5-cli .
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: kcachegrind-converters -- 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:
pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages
pkg-php-p...@lists.alioth.debian.org -- for PHP extensions
pkg-php-ma...@lists.alioth.debian.org -- 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
iQJ8BAEBCgBmBQJXFUpyXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHGFIQALCL3/1TwC9hKVG1PHJHdmMm
Xm7QlDyeUAEBICu+dpAG7LZyilXYGIdE5UHrkevsfs9ii4qBJHs+NMxxiU1eYWwb
9kF+jNTLf2aSgv0cfvaC6egLhHPdJ8jG6ojf954jtfCJoxuIA02KWT84B1CS3j2Q
euwRhLNKXRCj0dqOleWGStHjuTepA/GdW1HeWNPvYiBSgzNxRIMPAEGUD/hTwODv
qIOWK7uniq4CYory8As0luXvaiOR9C6/sGxKzl6hD2a9MGXS8DDVz2HFyhwvyJlC
E4PNHRbv2h7kYI8Ew/+3hclBFR1xOaA91GHRHHq1rw/uxsp10h4+Y7K4LguEBshk
J8PUpljiR+95on3mnfEqjwZeZH2SNzcewblR+w1IW63rDVKR0lth65q0u1sL+lJl
8vddnT3GJGDVe37sADlcsBz9xFHQpX0uovD0ml9rIDpiwUhyfrsFYOMYR7QC5eEe
RhhzLQzGyZMm5gL6frpjvzvmEywsj9Wx55rIpMAeD/7tfPG5uywhyy7RWuKKa9V/
rIk6TVUT7wAFfrHPRO7nKSxpgKbGiCUrU35taqoil/Cp6DIpoRCnX5QvR+whWZPN
ioEZKFGVg0Do3MgXAL9WJBTbxuzsVuBu1cg6abKI7Q5Ygh+Tyw8CuKuT0quwVj7U
719uSVXt4GrtRQ9kEi5E
=4W2C
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Source: kcachegrind
Source-Version: 4:16.04.0-1
We believe that the bug you reported is fixed in the latest version of
kcachegrind, 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 821...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Maximiliano Curia <m...@debian.org> (supplier of updated kcachegrind 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 ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sat, 21 May 2016 16:45:30 +0200
Source: kcachegrind
Binary: kcachegrind kcachegrind-converters
Architecture: source
Version: 4:16.04.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers <debian-qt-...@lists.debian.org>
Changed-By: Maximiliano Curia <m...@debian.org>
Description:
kcachegrind - visualisation tool for the Valgrind profiler
kcachegrind-converters - format converters for KCachegrind profiler
visualisation tool
Closes: 821509
Changes:
kcachegrind (4:16.04.0-1) unstable; urgency=medium
.
[ Automatic packaging ]
* Bump Standards-Version to 3.9.8
.
[ Maximiliano Curia ]
* New upstream release (15.12.2).
* Add upstream metadata (DEP-12)
* debian/control: Update Vcs-Browser and Vcs-Git fields
* Use the current default php version.
Thanks to Ondřej Surý <ond...@debian.org> (Closes: #821509)
* Add lintian-overrides about php-script-but-no-phpX-cli-dep
Checksums-Sha1:
71a7205a04ce666a2b5e6137215393933ac49533 2278 kcachegrind_16.04.0-1.dsc
58542af35df8cc98fcbb195fea59588c482489ee 238120 kcachegrind_16.04.0.orig.tar.xz
c725054dea6103e53e92be042261199b9e212dc3 5808
kcachegrind_16.04.0-1.debian.tar.xz
Checksums-Sha256:
b011f5b0d885beb983b7edc98e5ca3fb546a4f2e07fb3cddab7ba77dcf01a20a 2278
kcachegrind_16.04.0-1.dsc
9b76df7b1dc95b4d2e2e14583c822da03389a4e886d199ba6158e801d80b7a4a 238120
kcachegrind_16.04.0.orig.tar.xz
16efec57594e07e733d93515adf5e0fad7423c24c4d446f8a6a983b942a02105 5808
kcachegrind_16.04.0-1.debian.tar.xz
Files:
6d3cc8e6bf3303e2876aa4bad1f3ec18 2278 kde optional kcachegrind_16.04.0-1.dsc
32a162bfd5dbfc0cd4368109b4fdf308 238120 kde optional
kcachegrind_16.04.0.orig.tar.xz
c7a1b0a7efe5b58c938272a3e0d0095b 5808 kde optional
kcachegrind_16.04.0-1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCgAGBQJXQHS0AAoJEMcZdpmymyMq9sIQAIJo7KrQ4FyEverJX04zDu5p
+OxfbhL8M3VXe7HRYuRnqQfxgoYMgqZnOi/maK9P97GctbwTjCKLEuKhNGIbefom
pwOFLL0CEJsGlPFgAmR5hIO1CNj+S52dSpplGxEhwQ7CExrhv5yaRMHMKpIht0Jb
3k6NQ1Zprsshke2LU2n7m4ntP6AU4ScfcV8YoZTpCWDtoXLtRhBPzOXFUYhYaM1m
NCNx2j8IM3I/G7UaYJ6Nz6gcX5co7ek0iuKAGYCmoetyjzUyJtnsdkUEqyQ5h9M1
reJ7oR3jWRKt/LLFpvgs2rrrV7t6KWRITHlLnoq79RXg8bLnVybKcrHBJYl674gf
GsLA06jg1EPSrMX3NUolVMRrIghsDr79EECrHP4xphrCLel2oiPkfg4moJwGtHNW
tuqokL9O7xTkScdBb4t4fmVrYEZUSHcHL8U9M8y9zb06Y2iEfcOmKvZR43TsXU1g
/b3BtxYCunFoXAbg9KjigSSW3WsFIJsXaP7CtUOSmP9duLEUO2rhwVrxtxYDTVec
7rgKmebaqvmL6jpH23RtBri6LYwIdA8d+tQwoC2rPOpEv/WGbJeh7iqgIkHPR8Xz
Pf6ovgQaMIIkPYt2UtohZ6PAN/AL8Ie2sghc2fks/on559X21QvIl4T1U3on8NsB
iy3b43bjELnVyRV6DGEG
=wYdR
-----END PGP SIGNATURE-----
--- End Message ---
