Your message dated Sun, 24 Apr 2016 09:54:22 +0000
with message-id <[email protected]>
and subject line Bug#821583: fixed in php-kdyby-events 2.4.0-3
has caused the Debian Bug report #821583,
regarding php-kdyby-events: 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.)
--
821583: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821583
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: php-kdyby-events
Version: 2.4.0-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 php-kdyby-events package currently depends on php5 php5-common .
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: php-kdyby-events -- 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
iQJ8BAEBCgBmBQJXFUqoXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHB78P/2SQMTMtVlE4wIwyOdDDA2mV
gYPYEUenawZIuUSQz0W5ShZ5UYNxffsqC/BXG70INiNAFJPW2DvSq220t/kqrfua
WGiu6fuFVqYBZXUkbqUaf+sHxgqtdQcDOX9epH3bSrcw3MNbKoeS/UZlKPulVBfK
VN/WyStuP6WMV3yMtMO68dkIjto2dZMCNmj+P/zRlu719md4VirDkKVeT0jtdz9g
S7B1RJUOXR0ldXkSjA6JTDyU9hDV6H8Z2TOSMJwzcocvrRhhtYwIdtzX0bo8GeEb
bZLChHhMKMe5T2RTdJlH8O+G026ndHWN/WkxZaVRaPj1En58MrDJ+qkFY5k7O020
sBtXbb0mZF+mAYx34OGSuDOP8JlPdN/gHmxCh3CWme9jk/baUOImOL+YymP+Ry/C
m0UXys5Gb5M/ZQSW2fnngKAq/bIY7BykTCvbCZQrGQS3WQcWMOhSJJ0c4o1NQyO9
04KZJbd31oOaqCSnsi4cb1olnrwHlHS4RTiVI7Va8FlVS0D0qO//W7rloSm7wrdc
B0pCrqlNSNrQmyLyumlVGNehoDc0wR81slyGujpPvJJiVlXkxM/mi871vzOC7c3o
X/xXfsolF1Y2qjzH8l/CojnEbP3av83HhXEmFBW24XbEIJp6zDgH844xhPH65Kpu
V0s73dPociK4DuUxibVx
=k6Gg
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Source: php-kdyby-events
Source-Version: 2.4.0-3
We believe that the bug you reported is fixed in the latest version of
php-kdyby-events, 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.
Florian Schlichting <[email protected]> (supplier of updated php-kdyby-events
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, 24 Apr 2016 10:49:47 +0200
Source: php-kdyby-events
Binary: php-kdyby-events
Architecture: source all
Version: 2.4.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers <[email protected]>
Changed-By: Florian Schlichting <[email protected]>
Description:
php-kdyby-events - ${phpcomposer:description}
Closes: 816798 821583
Changes:
php-kdyby-events (2.4.0-3) unstable; urgency=medium
.
* Rebuild against PHP 7 (Closes: #821583)
* Use secure VCS URIs
* Add myself to Uploaders and remove David as requested (Closes: #816798)
* Declare compliance with Debian Policy 3.9.8
Checksums-Sha1:
877dc6ae6320ba4f8a31f6dac194c5abab229eb9 2019 php-kdyby-events_2.4.0-3.dsc
9f0ba74b582b0fe7b5cbf306364d1b9b058f06c8 4120
php-kdyby-events_2.4.0-3.debian.tar.xz
a183c90b242f3e62fffa0193a30e81939ad74d55 19388 php-kdyby-events_2.4.0-3_all.deb
Checksums-Sha256:
99a3397550b4bdc2fa50d1172125680edea037a92680ce783fa4834a96b2fdc3 2019
php-kdyby-events_2.4.0-3.dsc
13c1bdf77e873c02c72cff6451e2516de53d16f88812b040be74e8b932fb0aac 4120
php-kdyby-events_2.4.0-3.debian.tar.xz
0e2493912a001274f1d939750b0e5a063fc791874a5f11cf1c0f4de15c26bec2 19388
php-kdyby-events_2.4.0-3_all.deb
Files:
a43f2c80cb703f5e5bc7b89c4c1a55be 2019 php optional php-kdyby-events_2.4.0-3.dsc
825008cf2a269fd6e3a33f4cf8e58596 4120 php optional
php-kdyby-events_2.4.0-3.debian.tar.xz
8ec9589e926356f98d76079730d65b40 19388 php optional
php-kdyby-events_2.4.0-3_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCAAGBQJXHIo4AAoJEBKXO25y3Ae1N34P/2b4tgBOTqwg5RtlOpBzM1H9
jpRJ7ydogWFmq1FUoKCP9ICus8lWeQcb8YrHeO8VIi6AGj4A7CPZaeMEBnfeL2JO
OVqhlLubxrqTjhddlmcyQAiM5SOcYowZhNhLKHamSbIxT0xvZMv+hZO4z7od6j+d
/OhHlbuFG/OB72JfD7FzkCk5sJgR2mSZ+MgRH46u9Q2S+f3mlonwHInW578SxFS9
wUx2Nqkoz1QncI3laHQ09B1nnOuLkI6bSNKIRWikroZbjzukN3kBOjagPbJCm9MH
CjHQfeXnnGBFbV7QO9i9oSqpPK/aSyisnh8SZKrJorlMHocsFo9xUGhVPScK1Jjq
FReHAALJsfKb9dAKA5fsI6RB1dqHe8t4ReTZ1nyyTHwvwrK+TuoSjzDjW43NeDf8
7NLWjuppgcFgdU5048gM6QSQoefLsRNFS/OJv1GCBP0q6wscFXF9fJ8I/kwUSLG8
AmV6UvQb78FejaR/vFHNRAfNwKAqlDYcnKPAiHE1bHG/dUdBRXuzK8JWs6pkoG6l
5lz4H01acfZyV1PerIf8C32uA5otOphlZpL6CTP9nLmWZkvaRy23NwKmVt66QFKm
+kdjsE4AJtByvDSPNs35ihNFUY3wi5Ybapj5Y8kRGUvo18El7k60rOALcsrFrDyz
9tEn9Ll1HIFNSk9e2Zuu
=YgYe
-----END PGP SIGNATURE-----
--- End Message ---
