Your message dated Sat, 14 May 2016 00:06:35 +0000
with message-id <[email protected]>
and subject line Bug#823930: Removed package(s) from unstable
has caused the Debian Bug report #821716,
regarding src:swig2.0: 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.)
--
821716: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821716
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:swig2.0
Version: 2.0.12-1
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 swig2.0 package currently build-depends on php5 php5-cgi php5-dev .
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: swig2.0 -- 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
iQJ8BAEBCgBmBQJXFUt6XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsH49MP/A5yWiGccVHl2POlaL74FDVZ
ygkoOr4WJ/C5G3GhAsvTeVlEp7b76OE+D8E46sqEz7nu1vaHTsqDguQboNPp2vpF
rtdseQmg5q417dFZwBPJXV07YgO8D1V8Wd/BedOVZOHjnC9qoYYfq3daSWrB9iQz
6VZAuU38pwfY+TnnY8yAlIFdJjbVAXFCRYNIRd1IiFuQVgZg96zinqwhBPwM4grs
WjyKkxmQWChgDVNTb1lRWa0fXnwpK5WS7Vspr/X5+bMjtyf+TFg1FGoSBC1UEgI/
s3QnLU3cHdXG0UkLj6xccUaVJzRLmChmIfQfC1iVXUOtP7EMaxiL08f2OeUtSL38
C9KveuReahxUjEhVYgw5O7367oLnQwUZzewhquX2JE0xLh3D3RfucQD4esaWddZl
fhO7wTTGFk8kvFgWq70ENe0GoiCAsDH/B5tRSpy0bVlpTFDqUXBe+FTWO3gwQf/m
rZzFs0qIQbCz3mWjBwNMZwWHiKy7gHADLJxEsMbozgtaDp0qpMf2EwFPTZiuMsL6
WiZvrwOUoT9kPnUiujhmTNKKJQ3E7lDUuv4hrZYRZv6YuDX/8ruYIqZm7oYqwHht
QeVMkXk91zEKoC5otrCCb10n+OMej1qZXaa7QVMRxrKqgUuHPtqLqrIy1zyxuuIa
YI+m/T6Z64uHiCMb8NXe
=pimJ
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Version: 2.0.12-1+rm
Dear submitter,
as the package swig2.0 has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/823930
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
