Bug#820748: uniconvertor: ImportError: No module named sk1libs.utils.fs
On Mon, Apr 18, 2016 at 02:00:00AM +0300, Georgios Zarkadas wrote: > I encountered the same bug. > > The missing python modules are contained at the sk1 release tarball at > sourceforge.net (https://sourceforge.net/projects/sk1/). This project is > not yet part of the distribution, although there is an unofficial deb > package provided at the http://sk1project.org/ download page. > > Thus someone has to do the packaging of sk1, or the neccesary modules must > be copied to python-uniconvertor as a patch, or a request to upstream to > fix this issue has to be made. Hi, A while ago I was playing with this and thought that it was properly packaged and uploaded along with python-uniconvertor upgrade. Seems this was not the case. From: https://bugs.debian.org/699301 On Mon, 22 Jul 2013 18:11:57 +0200 Agustin Martin wrote: > The short story, I have been playing on building a 1.1.5 python-uniconvertor > package together with a new package python-sk1libs, the new dependency. > I did a minimal testing and resulting package seems to work, but this is my > first approach to python and everything I did needs extensive reviewing by > someone fluent with python, long story in above bug reports. > > I do not intend to adopt this package, so you may be interested in my > changes in > > http://anonscm.debian.org/gitweb/?p=users/agmartin/TMP/python-sk1libs.git;a=summary > http://anonscm.debian.org/gitweb/?p=users/agmartin/TMP/python-uniconvertor.git;a=summary > > Note that python-modules team seems to have SVN as preferred VCS (fix me if > this is no longer true) I am still not at all fluent with python so I do not intend to do the python-sk1libs packaging, but if someone is interested I hope it can help (even if only as an example of how things should not be done ;-)) Regards, -- Agustin
Bug#821446: anon-proxy: [INTL:nl] Dutch translation of debconf messages
Package: anon-proxy Severity: wishlist Tags: l10n patch Dear Maintainer, == Please find attached the Dutch translation of anon-proxy debconf messages. It has been submitted for review to the debian-l10n-dutch mailing list. Please add it to your next package revision. It should be put as debian/po/nl.po in your package build tree. === -- Groetjes, Frans nl.po.gz Description: application/gzip signature.asc Description: This is a digitally signed message part
Bug#821322: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: gpiv |0.6.1-3 | source gpiv | 0.6.1-3+b1 | amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x gpiv-mpi | 0.6.1-3+b1 | amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x --- Reason --- RoQA; Depends on to-be-removed packages -- 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 821...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/821322 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#821322: Removed package(s) from unstable
Version: 0.6.1-3+rm Dear submitter, as the package gpiv 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/821322 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 ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#821216: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: gpivtools |0.6.0-4 | source gpivtools | 0.6.0-4+b1 | amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x gpivtools-mpi | 0.6.0-4+b1 | amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x --- Reason --- RoQA; Depends on to-be-removed packages -- 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 821...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/821216 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#821216: Removed package(s) from unstable
Version: 0.6.0-4+rm Dear submitter, as the package gpivtools 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/821216 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 ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#821470: ampache: PHP 7.0 Transition
Package: ampache Version: 3.6-rzb2752+dfsg-7 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 ampache package currently depends on libapache2-mod-php5 php5 php5-cli php5-mysql php5-xmlrpc . 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: ampache -- 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 iQJ8BAEBCgBmBQJXFUpVXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsH2yUQANQwQofMbdKDVsp3usg3AZVa Gv+CDteFEoeN2acr3HdoZBYz76CnQgDLJcL6b1XJjGY5lMIJFtmyYjm1GJRnR0By S8FS01EnVQ9rt08o5w+hTTt/5E1Lks722dUnbp9W8Ibl44iGuAdBWZsG4d1n9AD2 2I3oTeAoe5xBnYelW8yLY9Y33QUBe8YjbuDDvzGX6NGi650n/8U+ejQI/RLa8y1e i1N/b1EmX1J0oadmw+OdNn1lwbD+o6oiSyaBFjnFlU+AhXrz5n/jkvONQ0/t1+fR 22O3ZMJu0i059ekzLyIpUVKcXjjKPo0ojtcdrhcXqf78UJdF15sKo7VHJcatQ4Eg kfUZoIZVdmlsi3VuVct9p8ZVDN1jQ35gOYzDLhMBTb6N8Bk+CuIN02RyQFISHJJ/ c8Ih8kQipUT2hcyZXU0woYTFlw/OqrCoC5oj5234Hgz9cKDtRwEg1CUWJhOh+8e+ bSa7KBxo/rpwLdT6Q/2LE8bkhCLulbaJsilFhDcjT82FpiyrXW5fFCE7lzHt+vNk IRISaffPfEmMOrPuE0mIdIQ+OsLyeTipIu2m5cbPsS9RKKfDNtxdC+qCUzbMRI80 Vfi9zXSY7SUOHKIOY+n35+Zw8/njTQ4BAZlAH8vHdw9tUKFzm2nFCsNseta6Fmgm Ylez5OCaHfuJtty+KlMg =hElo -END PGP SIGNATURE-
Bug#821476: collabtive: PHP 7.0 Transition
Package: collabtive Version: 2.0+dfsg-7 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 collabtive package currently depends on php5 php5-mcrypt php5-mysql php5-pgsql . 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: collabtive -- 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 iQJ8BAEBCgBmBQJXFUpZXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHhfQP/2pA4vhEApKgT8815Nzeo6Zs V28D3ae+pNMPGvNmvXCgeOJq6o1TTpeoR4BbDy6SXN1i0aGZCFuaRzE6D6OM5InD ufSWGco/PAAmCrFGVDFM5OiHmE6kk4ANX1hjP/54wCXd/ArmFCnMqjQLT5iOd3mW vU0J5sqUnqXQ9UhCewTxzEZk3kwi4rpUNL+5JaW2JuMXnmvkOZvPLYvImj0S9Du9 wMhCX/G7ucdxePLl9VVHvG2sbOuAowNqZ0YZa76pM7Ksee/p+J8rgmRFgzkjmsHs o4hWTCkbC5090mwVaNxpNM948N8EIkaZAAfokISOlSI0NcVFPLUG+j7JZZtzBSZF 5APhyDS2vjHb6/MGfjValh5kC5QjAIeauzjqZT3rCRQRNxXXnMrfldq/cXcwMXJG wHDn7V1M9PSF1P4nH4m2DfKcwsvP1i2W8aajp5m0ZNfWzq1bTD36Hzg8lK9F+cp/ f6Sj2EH07phG9CwruRCmc6k/6N8r58Hw9npZK5tC62I1e4a9DJuPGnq/1v0AbsT5 z9gJ+Dam1olXzhXkDzPx2kvyOtEhtww33Bdtc7CUmFHG/wSmTWjXFzh6di2DuF/C 3q3LIRTg9tyf51V5STAkeCRAo+1VW/x3WtESqUmXHoMlGYT++6LGKxj2PAZ/bPZQ 0YU6lFda8NFyaNtb326L =j7Iu -END PGP SIGNATURE-
Bug#821545: phoronix-test-suite: PHP 7.0 Transition
Package: phoronix-test-suite Version: 5.2.1-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 phoronix-test-suite package currently depends on php5 php5-cli 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: phoronix-test-suite -- 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 iQJ8BAEBCgBmBQJXFUqMXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsH3psQAJsbHK6c8fODPadmedjCOQmj FyGhqFE93AMdkYfsIjuzkVpZUS0GrDuX1m4m9O75Wf/W27jjfa58JiDOe/ty5iK4 l7Hr8o0Q2eahufduijBZr05/xrh/PsVjYv9445SX5wspSfpfAFSvM9Y7WqI4Wo0J PpofPYeL68fHnZY41MJf0VtGG5gFGj6n1mvjGfRy+Caf0A+pGCKU8oPBIb8Moq3O k5dPooZgWuYj0TEhXey8q5fiT5AiGf3/+pZk2Dh33CT0Oy5OpIFM8HIWMHukPjSg gSTy4G06QD4DcMgV/vGS5G2E98En+5SmJ4hEciNsW9gVb4xg14kj4No9UHqoF5g/ pstdltg/du5BkUW8F1X98xk1JbP+p7RdTZhdJRqZcu3w0k0NY+R6Xsl1tdYUGbOt WOC7B0U8SfBoPoLpIFp6rMxKx5QPm88CVYw9Z90nqgKKvllfbdcFIMDcZ+gRD3co 1E3IIQK69NApsWX1i/Wgju2rlF7xbDz2kGw0a1g0S8bZxMqK6hmdPIy6UMt3NrZl gJGMQu2ES6LDswXHL5Lq07WA5agMt6OcW4m5Mj1ZIEPDBeKnTmnijHziJLGb023E H6uLi13IrhtuYhExgM1IJxTcqPWq5SMdMq03WiDZed9/lMMHMY/9tb46/gba6be+ kQEob2ZVBdhZ+ppmytTY =U3iG -END PGP SIGNATURE-
Bug#821654: semanticscuttle: PHP 7.0 Transition
Package: semanticscuttle Version: 0.98.5+dfsg-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 semanticscuttle package currently depends on php5 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: semanticscuttle -- 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 iQJ8BAEBCgBmBQJXFUrdXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHdIAQAMo16BS8Bfu6u3bzO2AHRvsP H/l7+Sx3W6kIb/5jLeDBPogA32rAN/12XrJAfufFO6aAhLlIyVeePre4w56zfXTQ CLzf1mxhZb17ypj6lD0lJlMjmMsvy9B68XgvYFDYibbe9O5ZiE/zQ3JsVrWviXwv 44OmHAXp9Bj3xNT3EJ8EnNEsjhqh9xlP8C869C12Ah0/sUEGjL/etmBvKAyGYSYR RbPYVBToMtA9HrXG0b+ou4FgA1c4AoRcuZCdSwzhk8hNi7Kwf/HCwJ50Xb2Ijf3c 28/nJt/M3UYoSXe3HjeiHjJpDyS2jH3D17XTk4oGiC9XtqS+triF6rrjgqQbeZFh HQD1fVGf9evfywzTm15KQ+S2NV4WrnGDHOtkkgDH5UK/TRvtJRgbbyJe6qgaEauq 04UKTTFeYgiUqIDpnrXV9XoHxDn+pDoQ6q7PAQ5faQqYIBFFXglOhSV+vZcnq7zv sYvJSRU+aJyJIFdv0aVlUKoKexL/CTuk4XBaPv/Ze48k0FqU6q9SAHYAb0lPvCXR RDL0OSP2ajAVSxB39aG5uO6fVYRFLmSRRySJ8ctJdUYnb1xyf6O4QmqRofFiNsmk 2DF6BiY0ibUwEyUwgX2gjncMsYPk/q/JpH/KGvqhq1u4vv9n/wZ3+8SjP6JAdAnO 7uFOvJT2QzdteVY/RO/v =SXIT -END PGP SIGNATURE-
Bug#821692: src:phoronix-test-suite: PHP 7.0 Transition
Package: src:phoronix-test-suite Version: 5.2.1-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 phoronix-test-suite package currently build-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: phoronix-test-suite -- 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 iQJ8BAEBCgBmBQJXFUtoXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsH3WIQAKcCkxVnfidX8pCs348fbwHE hN0nblWw/xmM7O+IWhtqZf86F3eA3XvhZGc6QNUbRWx28U6aELZ6X46gjSjHgHfJ jR3Pr0wfHsmXdX6smwt3pzO3j0CnEMCnDxhQkdizwIM/SgJDDjsGyne+dvJY1j46 OMr4dMokldO6r8eYvkwFkkh6wEo/XTe+l/CU2Am7YhEZkRb9XT0BOq9eYx+Wijmu uiXxPWAwjKfmRekAKs83SF2fmkq72zulFC38b7LDKKHflp9w1a4t7Zby+LTFSez4 kVW0mMuin7NGmidF6nUTaV20WvqPOHGgIp9KPu5oDImSCf3VW+0/UA2m99eiWGhB deZxh17yMjUq7NOImoI7fTjz9/QRwEqVFFnPrafpDQKRVXul28Xvn7Yr75kYgaP9 Sh//uNIaZajgEzU1SQaPTw/pRA996idHIMFifDMZ5nUdvMH5ZjyvflCrlvbrtJ/+ xFPDwwa4jq4XioPGFg0z5g3XNu12BehWG/qUlUrlN0SNp9Fs7nIuDL+Xd0GTLgYF OYAPbf5hABjQQd+7YyDFDwtr/D3D2YIwfaxI+XroK6IBb03K/9ONH8FtmPEo7L5/ Ttx5eNnVUFKTdYdODBFKmhqf9znqzPJur9R3/tP7YQsuxfqYzcszisirYuRWnFRp +d1cWDIRbrDU42vbGh3d =vmwV -END PGP SIGNATURE-
Processing of polygraph_4.3.2-2_source.changes
polygraph_4.3.2-2_source.changes uploaded successfully to localhost along with the files: polygraph_4.3.2-2.dsc polygraph_4.3.2-2.debian.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org)
polygraph_4.3.2-2_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 18 Apr 2016 23:13:01 +0200 Source: polygraph Binary: polygraph Architecture: source Version: 4.3.2-2 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Sebastian Andrzej Siewior Description: polygraph - performance testing tool for caching proxies and more Closes: 805083 Changes: polygraph (4.3.2-2) unstable; urgency=medium . * QA upload. * Build without using SSLv3 protocol (Closes: #805083). * Orphan the package, set maintainer to Debian QA. Checksums-Sha1: 33c043670383aa802daff8fb0135f929ce748aff 1760 polygraph_4.3.2-2.dsc 48f631776e33e40d24952c916f63df0123324c4c 5060 polygraph_4.3.2-2.debian.tar.xz Checksums-Sha256: d99e3a759b3aed5f95fa43347d424ff10216e626909da838956249d58266844b 1760 polygraph_4.3.2-2.dsc dcb88ddcbf6cc43f6cec8d9120f9941358a8e575de0b17d8f7aa5f7a9b8c43bb 5060 polygraph_4.3.2-2.debian.tar.xz Files: c0e8ff27b32b2d6419a41eeac20c2d88 1760 net optional polygraph_4.3.2-2.dsc d9a58f8c610c1f080a8c6292b4981d45 5060 net optional polygraph_4.3.2-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJXFVEhAAoJEHuW6BYqjPXRkigQAJkIKFDVSG+mnHkL82gNbGGa T0bmWehAE+tZP8TW4fUSN+84Wn7s48BsLWjzT3rsorZQ02QmlqO8Q3hT5li41aa/ BXTsm+uUjhystGzywWXPiKucSeCDJpgdP5mzoABdP6o+uRdu3VxppmDa/QCKw2Vo /HzKBhXv41XrivlSI9WLHzIGdiWg5S0G7twTmX3QszyV5oY/G7d2rahwyk6m3IZ7 PkGhDCzN57mIvIF8WftXMP4P0MS65UXV8egEEbK0bKETKb1fNaa51dieWMtmYGQR H9ykbRn+gh+qjpuRKBKpyh2mZwZ/OCCjDiN/f4Bb7glczxD3MfeOKS+CfOR+7eQX mlcBjhG1pzOAcTBuGSM47E2UUlLTMvJjlLL9Jhp750GEO25RGGoqXV7TMpdWI0JJ tBDHfCoX/kpHH5UsVCLGJ6fqjkcGvnM6GrJBpw6B9Y+oNOSJfk2KBV03Trjo8YBf 2AcMPbWRs8Gzs8POnWxeki5CfbNa24C6MplNLtNZhdLkHnzgQcu+ZXzDB3PEfzaJ 5bhROZIK7vpxJIdFu1jRZMKYR5KjIwId/VNu56lbRMe0drz0rZogBe/XOByHMVhA BsgL1fwllEL2HCJijq/+lSMFLs0ZJ/z0wAFC0GOOZwx/ViSAJOGUzbqhtaAHKAxI 5XBDO6exiG5R7UbzrLqD =1xyM -END PGP SIGNATURE- Thank you for your contribution to Debian.
