Your message dated Tue, 17 Jan 2017 13:49:15 +0000
with message-id <e1ctu8r-000eqt...@fasolo.debian.org>
and subject line Bug#821530: fixed in sparkline-php 0.2-6
has caused the Debian Bug report #821530,
regarding libsparkline-php: 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.)


-- 
821530: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821530
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsparkline-php
Version: 0.2-5
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 libsparkline-php package currently depends on php5 php5-gd .

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: libsparkline-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:

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

iQJ8BAEBCgBmBQJXFUqBXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsH1sgQANFZYMiq6xkgI+2ByZkE0OaO
iPj1O5wvgOQ0Z+zy6mC4oUnKjPT03DWBnUjTEzQA5JVpyTnAL1bE3wabYUn0qbUv
Fq20lmLjUkP0aWxF+j4jDEZSqIsY/RRnAp0SfF03CNMKuSX/6Fc12NRCEyIvtuNH
9DgIXcrUqZ6OmjPnNiUphg1U6t/fphLKjZ7ZASf52VXCntHcQ5YCqHWu7P4U56h7
NMVzqsQx3XHxsEUMfzbuzHot3hU3cJonogbS9xB2CyN6vuTmJhpuNIN7BRq9z9yl
jDyh6tu6VfUWq11gGl9fatk7DdSgi/uNSNbJ50Omi7zFHqy5OyJRuHk7nhgUBxkv
4gwn6gyBZZbznsUhpvrmoetmnHkZqxAu923IdW+LXTmwUV5LiNwX4Dbnx9Ps7BBx
+dovgWXPdzPMcQx+Y3gAd3d+ys3vEBsrB1J8x7QpY9bXUxJ8uuHunsTNlIctFicp
v/Zq1NqUsSn1KQWcc1zYz4GD2YfGknka4dL63jfzA0b085yk0ADnSkoULiVUHC33
2HUpdG2OBnIwUBRygwF4kQuVitGGUM0qICiBu8OEh+D6LuiRc2luf4aDbOdmx9uK
6WiwJ5RBFI6+Gd0BuES4eHU5aLDNNlwnuMG+XsziCbCA2Nr5hp7VzTRNI9ntUlq6
XkNFv1KhD+yjXbSMd3g2
=iHw/
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message ---
Source: sparkline-php
Source-Version: 0.2-6

We believe that the bug you reported is fixed in the latest version of
sparkline-php, 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.
Andreas Beckmann <a...@debian.org> (supplier of updated sparkline-php 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: SHA256

Format: 1.8
Date: Tue, 17 Jan 2017 14:25:24 +0100
Source: sparkline-php
Binary: libsparkline-php
Architecture: source
Version: 0.2-6
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packa...@qa.debian.org>
Changed-By: Andreas Beckmann <a...@debian.org>
Description:
 libsparkline-php - sparkline graphing library for php
Closes: 821530
Changes:
 sparkline-php (0.2-6) unstable; urgency=medium
 .
   * QA upload.
   * Set Maintainer to Debian QA Group.  (See: #761832)
   * PHP 7.0 transition, patch from Ubuntu.  (Closes: #821530)
Checksums-Sha1:
 f1d8f8d6b256143d2721d5895dcec6475bbc5fc6 1874 sparkline-php_0.2-6.dsc
 bb8ac17f7d1643cab4418e0940a5b67ad830c7e0 2356 sparkline-php_0.2-6.debian.tar.xz
Checksums-Sha256:
 96e1a2a1d58293694499c284fbe2f5d222ebca021037fdd4a536db9a788f9a22 1874 
sparkline-php_0.2-6.dsc
 945af13ae13c6c3bcf1a0f512e0841205f1aac33f374991459c0dc3fef530184 2356 
sparkline-php_0.2-6.debian.tar.xz
Files:
 a68e0439055720011c91380691ebc32a 1874 graphics optional sparkline-php_0.2-6.dsc
 2ad33d5da6ce585e7a1bb0d175b2a936 2356 graphics optional 
sparkline-php_0.2-6.debian.tar.xz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJYfhucAAoJEF+zP5NZ6e0Ibf4P/REQIb2cgSPgACXdjVXxb3KY
JzmI2mEfNxmeAikSC7DNWNxd8ZyZAq19dD5LLOHx1KX3hNYcoW+fPAn5lXqKAvt7
LYVZ8WdDFVO+umlRluVHgwzrrFDZnO4ikA/5+2lwRJJqCAuJVSBbyhNZIk3lmhI6
txNCbLjWRrHpdZOFtxt/V/ErGAhuiFHTnO164+6rJNUWVGtNLFHHmOJpj3UoaL+L
OadBGPoMU5XoSfq5ngzs4rKMZ29oMXkCCsBLmie6+y18ca94FJWY6aQJdajoZNdx
TCuVJGnPYKgAJtRTUolGgVpjT6fnDxZ59+pAeD6t9mbhilc4qWeX5Mp89Mzh8dj2
+6KnNO9Q8FpSHW1Zw747Q4Xw/5g+HGK44l11deVoV4pkXS6GyoIRm5DGrYSNLmCk
qkapWkt/IdhaqvzrS4J/mlisQr7ymR/PAv7bpHqopvwB8E4bazdtRsBLXC9DIdLM
zdsIs9iIEAPvw+Wui/DPQFns0H/zamoPrkr+j9ju8Ehn6U6y7Sx9XSvmsPa3Ray4
AL06ZzLik6DRxNKwhVTJP2hO8pGNN9b6vUjvWqoh9XyPXPaDx6BL8mGs9aRzxOQE
1ZLS4ECLegWjkPzSSMRA/u6ak6I1bgVBO0acz4HVqqIzQCtpzqIpJRG+mR0nNNj7
3Wp9nKu9ULz867zQa2bS
=lcuu
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to