Your message dated Mon, 09 May 2016 18:05:02 +0000
with message-id <[email protected]>
and subject line Bug#821504: Removed package(s) from unstable
has caused the Debian Bug report #821504,
regarding RM: htcheck -- ROM; abandoned upstream, obsolete, doesn't support PHP
7.0
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.)
--
821504: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821504
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: htcheck-php
Version: 1:2.0.0~rc1-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 htcheck-php package currently depends on libapache2-mod-php5
libapache2-mod-php5filter php5 php5-cgi php5-mysql .
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: htcheck-php -- 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
iQJ8BAEBCgBmBQJXFUpuXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHluQP/0LX0woJE2fK3ccMXdH++DoE
CPzbOlCRbNEL76tlXUFMkCn9/NA9tkIOXRVeW/Niha8EelRLw4A7J8wZJJk1MLIQ
w8q5hTyNsBO0IHrU5lhkv3qx1xb3aEdsBOsNsqzjJGneZabxTBPn5D/6Bt6lDwzp
tU/KI1cNGxHeGtGcci9BLjQAbWKDww5VPSfRIV2Yp6kBQhxYdqXa0iH0nGKi/0Si
bNRVJwhvFV0GJWEyH0AAML5LIjS5nZ/735kQPmYHhDRI8ZDvQJY3bJSijRK5E7d1
jty+OcoL2sfYMeg4LMotMOWdWwAkEHRl+sJsFou3qVgnFpPkmF17beAnh9DPSuDK
rbpF4xLLGyXokbjrCTzbOwrMwejg+h8fkiC+KxRA6cpZmn8F6tfpOUAxGrbtZW6Q
j5wSACr7Rj7iBmW4vHzi0flbO//lY+np+nr4/Sw8SxntZlKBJZ32GnH/CYsXGwk1
rrHz5mgP3JHRLoOEkl67xyVkDZRS7/84KreSHHGdkqCo0HErl1NYFf1mVRNPB2d5
jCPx6VqDwVFfUbhbSTy79HU3V5wG/vlwwmlYBul5S+drQDeTiMWS4bJkgk/QEig3
itt1PYNFgBtnyGccEXu0JnJC7VuvIBtoXy2rssZK8SqDKbZtTeR4AeXhDfagsNmU
n9rJX0RU2ydF5OrSGYf1
=0niL
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
htcheck | 1:2.0.0~rc1-2 | source, arm64, mips64el
htcheck | 1:2.0.0~rc1-2+b1 | amd64, armel, armhf, i386, kfreebsd-amd64,
kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x
htcheck | 1:2.0.0~rc1-2+b3 | hurd-i386
------------------- Reason -------------------
ROM; abandoned upstream, obsolete, doesn't support PHP 7.0
----------------------------------------------
Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it). Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.
Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.
We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected].
The full log for this bug can be viewed at https://bugs.debian.org/821504
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 ---
