twisted-web2 is marked for autoremoval from testing
twisted-web2 8.1.0-3 is marked for autoremoval from testing on 2017-01-29 It is affected by these RC bugs: 844493: twisted-web2: FTBFS: twisted.python.dist module not found
apt-p2p is marked for autoremoval from testing
apt-p2p 0.1.8 is marked for autoremoval from testing on 2017-01-29 It (build-)depends on packages with these RC bugs: 844493: twisted-web2: FTBFS: twisted.python.dist module not found
Bug#692233: marked as done (vtwm: 100% cpu on SIGTERM)
Your message dated Tue, 03 Jan 2017 01:49:15 + with message-id and subject line Bug#692233: fixed in vtwm 5.4.7-4 has caused the Debian Bug report #692233, regarding vtwm: 100% cpu on SIGTERM 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.) -- 692233: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692233 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: vtwm Version: 5.4.7-2.2+b1 Severity: normal File: /usr/bin/vtwm If vtwm is sent a SIGTERM signal then goes into a hard loop 100% CPU with an apparent GrabServer in force, thereby locking the screen. Under gdb it looks like something in libX11, and/or libxcb which libX11 uses, doesn't like the cleanups run by vtwm's Done(). I don't know if a signal handler like Done() is allowed to interrupt ReadEvent() and do things like XGetGeometry() per vtwm's RestoreWithdrawnLocation(). I presume it worked once or it wouldn't have been written that way. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-486 Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages vtwm depends on: ii libc6 2.13-10 ii libice62:1.0.8-2 ii librplay3 3.3.2-14 ii libsm6 2:1.2.1-2 ii libx11-6 2:1.5.0-1 ii libxext6 2:1.3.1-2 ii libxmu62:1.1.1-1 ii libxpm41:3.5.10-1 ii libxt6 1:1.1.3-1 --- End Message --- --- Begin Message --- Source: vtwm Source-Version: 5.4.7-4 We believe that the bug you reported is fixed in the latest version of vtwm, 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 692...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ian Jackson (supplier of updated vtwm 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, 03 Jan 2017 00:10:43 + Source: vtwm Binary: vtwm Architecture: amd64 source Version: 5.4.7-4 Distribution: unstable Urgency: medium Maintainer: Ian Jackson Changed-By: Ian Jackson Closes: 522263 692233 Description: vtwm - Virtual Tab Window Manager Changes: vtwm (5.4.7-4) unstable; urgency=medium . Bugfixes: * Block signals during the event loop. Closes:#692233. (Review other bugs. None of them look fixable now.) . Packaging: * Make myself the maintainer. Closes:#522263. * .gitignore: Add a .gitignore covering files outside debian/ generated by dpkg-buildpackage -uc -b on amd64. * .gitignore: Add a debian/.gitignore too. Checksums-Sha1: 3f1e6e7b38fceb36fea277fa79acee77fd6cf9a4 1502 vtwm_5.4.7-4.dsc 7ab6976d6adfe4bdcb567dc8bb46b648c1aef7b0 17799 vtwm_5.4.7-4.diff.gz 0c7a2c2c0c712efc0c63f55f1a0bbb9eb45e2146 280384 vtwm-dbgsym_5.4.7-4_amd64.deb e9504e4599ea69990ff69f3d8f59b8a7845647ae 5567 vtwm_5.4.7-4_amd64.buildinfo 67499152700a65069a329d1bc06103549174a059 215906 vtwm_5.4.7-4_amd64.deb Checksums-Sha256: 128fe2dd14183bac824cb5f39065d15b97622581f5e1fd23d8a616f9480f26e7 1502 vtwm_5.4.7-4.dsc d412e1589fa46c1f9c8a57d35d9ab6fd2355f435032f9be326abdcd8d7e6daaf 17799 vtwm_5.4.7-4.diff.gz 3f488f11ddc4a5d14673ec4e49a030d899f97b5a758e66eb097142f4438203c7 280384 vtwm-dbgsym_5.4.7-4_amd64.deb 84be703e08fd51087da88e2162a00117b177b60eb74ba075f4d1f9c4d584dbd6 5567 vtwm_5.4.7-4_amd64.buildinfo d155dbce7e7e7cb8e0879ad1c016e2bc66815f9462701d79835f0eda3644e2d8 215906 vtwm_5.4.7-4_amd64.deb Files: 1074e19db1f8f559021ee35dee40b05d 1502 x11 optional vtwm_5.4.7-4.dsc f559ce3711957f68d01cd7d5c250eb06 17799 x11 optional vtwm_5.4.7-4.diff.gz 34f80d83e67883c5941b362886e87b7b 280384 debug extra vtwm-dbgsym_5.4.7-4_amd64.deb 22ede31c9aa01850f4f9d2efee0c0e0d 5567 x11 optional vtwm_5.4.7-4_amd64.buildinfo 7a333281de7dedaf04e5000e060f46c9 215906 x11 optional vtwm_5.4.7-4_amd64.deb -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEVZrkbC1rbTJl58uh4+M5I0i1DTkFAlhq/hgACgkQ4+M5I0i1 DTmXcwgAnN36hkmn8/B0c5F80mNV7biuOKsDVi4h1ipoy25R2ORAzYQNTRIaIMQT S+oNQ/mRdIpYayKK+Ag4GwvLRSSwOVaeUHvqtgtCAKDB05Bi7w0WcuhDKKj1sPA5 uZs+T+zBq4PyVsmSnIMYecBssiUIPB3Sjr3H0q5pnBtmlKFedZltHE5//I3+11yB 1473HrTaKmxUqnHXcJRs2NZFttBBsxi/Pw7F0MFS+vm
Bug#393145: vtwm: strange behaviour under fr_FR.UTF-8 locale
Control: tags -1 moreinfo I just did LC_ALL=fr_FR.UTF-8 vtwm & and it seemed to DTRT. The menus and window titles look just like they did in my usual locale. Is this still a bug for you, and if so do you have a clearer repro ? Thanks, Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.
Processed: Re: vtwm: strange behaviour under fr_FR.UTF-8 locale
Processing control commands: > tags -1 moreinfo Bug #393145 [vtwm] vtwm: strange behaviour under fr_FR.UTF-8 locale Ignoring request to alter tags of bug #393145 to the same tags previously set -- 393145: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=393145 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: vtwm: strange behaviour under fr_FR.UTF-8 locale
Processing control commands: > tags -1 moreinfo Bug #393145 [vtwm] vtwm: strange behaviour under fr_FR.UTF-8 locale Added tag(s) moreinfo. -- 393145: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=393145 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: merging 849988 849989 849990
Processing commands for cont...@bugs.debian.org: > merge 849988 849989 849990 Bug #849988 [wicd-curses] wicd-curses.py crashed with AttributeError in keypress(): 'Text' object has no attribute 'keypress' Bug #849989 [wicd-curses] wicd-curses.py crashed with AttributeError in keypress(): 'Text' object has no attribute 'keypress' Bug #849990 [wicd-curses] wicd-curses.py crashed with AttributeError in keypress(): 'Text' object has no attribute 'keypress' Merged 849988 849989 849990 > thanks Stopping processing here. Please contact me if you need assistance. -- 849988: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849988 849989: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849989 849990: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849990 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#846106: Removed package(s) from unstable
Version: 2.2.5-2+rm Dear submitter, as the package php-arc 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/846106 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#846106: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: libarc-php |2.2.5-2 | all php-arc |2.2.5-2 | source --- Reason --- RoQA; orphaned; RC-buggy -- 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 846...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/846106 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#846073: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: libgraphite-php | 1.5-2 | source, all --- Reason --- RoQA; orphaned; RC-buggy -- 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 846...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/846073 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#846073: Removed package(s) from unstable
Version: 1.5-2+rm Dear submitter, as the package libgraphite-php 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/846073 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#825542: marked as done (php-arc: FTBFS: Tests: 40, Assertions: 87, Errors: 5.)
Your message dated Mon, 02 Jan 2017 13:05:45 + with message-id and subject line Bug#846106: Removed package(s) from unstable has caused the Debian Bug report #825542, regarding php-arc: FTBFS: Tests: 40, Assertions: 87, Errors: 5. 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.) -- 825542: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825542 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: php-arc Version: 2.2.5-2 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, php-arc fails to build from source in unstable/amd64: [..] Get:34 http://httpredir.debian.org/debian sid/main amd64 php-phpdocumentor-reflection-docblock all 2.0.4-2 [17.8 kB] Get:35 http://httpredir.debian.org/debian sid/main amd64 phpunit-diff all 1.4.1-2 [8252 B] Get:36 http://httpredir.debian.org/debian sid/main amd64 phpunit-comparator all 1.2.0-2 [8614 B] Get:37 http://httpredir.debian.org/debian sid/main amd64 php-phpspec-prophecy all 1.6.0-2 [36.1 kB] Get:38 http://httpredir.debian.org/debian sid/main amd64 phpunit-global-state all 1.1.1-2 [6108 B] Get:39 http://httpredir.debian.org/debian sid/main amd64 phpunit-object-enumerator all 1.0.0-2 [3794 B] Get:40 http://httpredir.debian.org/debian sid/main amd64 phpunit-resource-operations all 1.0.0-2 [6302 B] Get:41 http://httpredir.debian.org/debian sid/main amd64 php-deepcopy all 1.5.1-1 [43.2 kB] Get:42 http://httpredir.debian.org/debian sid/main amd64 phpunit all 5.3.4+dfsg-2 [107 kB] Fetched 3930 kB in 0s (75.6 MB/s) Selecting previously unselected package libedit2:amd64. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 23096 files and directories currently installed.) Preparing to unpack .../libedit2_3.1-20150325-1+b1_amd64.deb ... Unpacking libedit2:amd64 (3.1-20150325-1+b1) ... Selecting previously unselected package psmisc. Preparing to unpack .../psmisc_22.21-2.1+b1_amd64.deb ... Unpacking psmisc (22.21-2.1+b1) ... Selecting previously unselected package php-common. Preparing to unpack .../php-common_1%3a41_all.deb ... Unpacking php-common (1:41) ... Selecting previously unselected package ucf. Preparing to unpack .../archives/ucf_3.0036_all.deb ... Moving old data out of the way Unpacking ucf (3.0036) ... Selecting previously unselected package php7.0-common. Preparing to unpack .../php7.0-common_7.0.7-1_amd64.deb ... Unpacking php7.0-common (7.0.7-1) ... Selecting previously unselected package php7.0-json. Preparing to unpack .../php7.0-json_7.0.7-1_amd64.deb ... Unpacking php7.0-json (7.0.7-1) ... Selecting previously unselected package php7.0-opcache. Preparing to unpack .../php7.0-opcache_7.0.7-1_amd64.deb ... Unpacking php7.0-opcache (7.0.7-1) ... Selecting previously unselected package php7.0-readline. Preparing to unpack .../php7.0-readline_7.0.7-1_amd64.deb ... Unpacking php7.0-readline (7.0.7-1) ... Selecting previously unselected package php7.0-cli. Preparing to unpack .../php7.0-cli_7.0.7-1_amd64.deb ... Unpacking php7.0-cli (7.0.7-1) ... Selecting previously unselected package php-cli. Preparing to unpack .../php-cli_1%3a7.0+41_all.deb ... Unpacking php-cli (1:7.0+41) ... Selecting previously unselected package libxslt1.1:amd64. Preparing to unpack .../libxslt1.1_1.1.28-4_amd64.deb ... Unpacking libxslt1.1:amd64 (1.1.28-4) ... Selecting previously unselected package php7.0-xml. Preparing to unpack .../php7.0-xml_7.0.7-1_amd64.deb ... Unpacking php7.0-xml (7.0.7-1) ... Selecting previously unselected package php-xml. Preparing to unpack .../php-xml_1%3a7.0+41_all.deb ... Unpacking php-xml (1:7.0+41) ... Selecting previously unselected package php-pear. Preparing to unpack .../php-pear_1%3a1.10.1+submodules+notgz-8_all.deb ... Unpacking php-pear (1:1.10.1+submodules+notgz-8) ... Selecting previously unselected package pkg-php-tools. Preparing to unpack .../pkg-php
Bug#821517: marked as done (libgraphite-php: PHP 7.0 Transition)
Your message dated Mon, 02 Jan 2017 13:01:56 + with message-id and subject line Bug#846073: Removed package(s) from unstable has caused the Debian Bug report #821517, regarding libgraphite-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.) -- 821517: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821517 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libgraphite-php Version: 1.5-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 libgraphite-php package currently depends on php5 . 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: libgraphite-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 iQJ8BAEBCgBmBQJXFUp4XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHJyMQAK25oJOALFPthGDBynaDDvqO E9TlQSHp+7VYeT46nJQicuSpfDk5BkkdB6rn0jiIaeTipmXMNUTEdeQxHhbdCCab J+RNsuBa2KZN5vlB2JOUCFYq29ToyFz9yiSjOqX/ns9d0NWL0hWBEsTGIt49X1xY XQwlp/Wd2V9TuvSLpV65tsTawRv6LUAWDCNDsuO2fVlSJ3yFFOTyTroFpnUurK9z Nk4JTIay8V9mDMpi9FPz2ayzF/Bxb76+mo3/DxxFi74piAg3v2J28PSma7vh02az z7y48QHy8rnU4WP9IebOXuaqf0DkydufwZ6
Bug#821514: marked as done (libarc-php: PHP 7.0 Transition)
Your message dated Mon, 02 Jan 2017 13:05:45 + with message-id and subject line Bug#846106: Removed package(s) from unstable has caused the Debian Bug report #821514, regarding libarc-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.) -- 821514: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821514 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libarc-php Version: 2.2.5-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 libarc-php 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: libarc-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 iQJ8BAEBCgBmBQJXFUp1XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHz94P/iQyB2EXXuIqpO0c3tiM8GWT 571PqatBWnGCQ7enlOn5k2C1eNuBTwYM5FjwNHWs3o6F3FyFoL5GXuyG6U80XBLQ mbXlIsg1ndQ6vP0a75/azkrjYWsnBRYhSQj0Y89uRAdnd3nUwTi15Z7cvNdjWsow TiMb6Z23CykXz8L9lNuHrgsFEK6gEzlPKHFnJ0utQMGpq5frALV/eRb3iYHRLzez oVSfaptHOsivHKU9kJTvZ2UCFGwiKaSzkEsTj2NxZJO8ztlfq27E5YUKgnTHFlix FOjVRTD3MJiPUIDLlOhoZn2vBdNPB+ggFcOsti7jp
Bug#849932: libindicate: FTBFS (Fields cannot have void type)
Package: src:libindicate Version: 0.6.92-3 Severity: serious Dear maintainer: I tried to build this package in stretch with "dpkg-buildpackage -A" (which is what the "Arch: all" autobuilder would do to build it) but it failed: [...] debian/rules build-indep CDBS WARNING:simple-patchsys.mk is deprecated since 0.4.85 - please use source format 3.0 (quilt) instead test -x debian/rules mkdir -p "build" CDBS WARNING:DEB_DH_BUILDDEB_ARGS is deprecated since 0.4.85 mkdir -p debian/stamp-makefile-build debian/stamp-makefile-install mkdir -p debian/stamp-makefile-check mkdir -p debian/stamp-autotools /usr/bin/make -f debian/rules reverse-config make[1]: Entering directory '/<>' CDBS WARNING:simple-patchsys.mk is deprecated since 0.4.85 - please use source format 3.0 (quilt) instead set -e; if test -e debian/autoreconf.before; then \ [... snipped ...] && touch generated-stamp Name: propertydata Type: GVariant* in callback indicate_listener_get_property_variant_cb Name: value Type: GVariant** in callback indicate_server_get_indicator_property_group_slot_t rettype: GVariant* in method GetPropertyVariant in type Indicate.Indicator Name: value Type: GVariant* in indicate_indicator_set_property_variant in method SetPropertyVariant in type Indicate.Indicator Name: menu Type: DbusmenuServer* in indicate_server_set_menu in method SetMenu in type Indicate.Server Name: propertydata Type: GVariant* in callback GetPropertyVariantCallback Defaulting GetPropertyTimeCallback param to 'call' scope in method Listener.GetPropertyTime Defaulting GetPropertyIntCallback param to 'call' scope in method Listener.GetPropertyInt Defaulting GetPropertyCallback param to 'call' scope in method Listener.GetProperty Defaulting GetPropertyBoolCallback param to 'call' scope in method Listener.GetPropertyBool Defaulting GetCountCallback param to 'call' scope in method ListenerServer.GetCount Defaulting GetDesktopCallback param to 'call' scope in method ListenerServer.GetDesktop Defaulting GetTypeCallback param to 'call' scope in method ListenerServer.GetGType Defaulting GetMenuCallback param to 'call' scope in method ListenerServer.GetMenu Defaulting GetIconThemeCallback param to 'call' scope in method ListenerServer.GetIconTheme Generation Summary: Enums: 1 Structs: 0 Boxed: 0 Opaques: 2 Interfaces: 0 Objects: 3 Callbacks: 18 Properties: 0 Signals: 2 Methods: 54 Constructors: 3 Throttled: 5 Total Nodes: 88 /usr/bin/mono-csc -keyfile:/<>/./bindings/mono/indicate/indicate.snk -nowarn:0169,0612,0618 -unsafe -out:indicate-sharp.dll -target:library -r:/usr/lib/pkgconfig/../../lib/cli/pango-sharp-2.0/pango-sharp.dll -r:/usr/lib/pkgconfig/../../lib/cli/atk-sharp-2.0/atk-sharp.dll -r:/usr/lib/pkgconfig/../../lib/cli/gdk-sharp-2.0/gdk-sharp.dll -r:/usr/lib/pkgconfig/../../lib/cli/gtk-sharp-2.0/gtk-sharp.dll -r:/usr/lib/pkgconfig/../../lib/cli/glib-sharp-2.0/glib-sharp.dll ./generated/*.cs AssemblyInfo.cs ./generated/ListenerServer.cs(62,10): error CS0670: Fields cannot have void type ./generated/ListenerServer.cs(62,28): error CS1547: Keyword `void' cannot be used in this context Compilation failed: 2 error(s), 0 warnings Makefile:854: recipe for target 'indicate-sharp.dll' failed make[6]: *** [indicate-sharp.dll] Error 1 make[6]: Leaving directory '/<>/build/gtk2/bindings/mono/indicate' Makefile:546: recipe for target 'all-recursive' failed make[5]: *** [all-recursive] Error 1 make[5]: Leaving directory '/<>/build/gtk2/bindings/mono/indicate' Makefile:426: recipe for target 'all-recursive' failed make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory '/<>/build/gtk2/bindings/mono' Makefile:428: recipe for target 'all-recursive' failed make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory '/<>/build/gtk2/bindings' Makefile:489: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/<>/build/gtk2' Makefile:421: recipe for target 'all' failed make[1]: *** [all] Error 2 make[1]: Leaving directory '/<>/build/gtk2' /usr/share/cdbs/1/class/makefile.mk:77: recipe for target 'debian/stamp-makefile-build/gtk2' failed make: *** [debian/stamp-makefile-build/gtk2] Error 2 dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2 The relevant part of the build log is included above. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the page for this package. If you could not reproduce this using sbuild on a single CPU virtual machine (as I did), please do not downgrade or mark as unreproducible, I would then consider giving you access to a virtual machine on which I can reproduce it so that you can as well. (In such case, please contact me off-list for details). Thanks.
