Bug#851223: marked as done (RFS: python-parse/1.6.3-1.1 [NMU])

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 08:00:32 + (UTC)
with message-id <1114867807.7152883.1484294432...@mail.yahoo.com>
and subject line Re: Bug#851223: RFS: python-parse/1.6.3-1.1 [NMU]
has caused the Debian Bug report #851223,
regarding RFS: python-parse/1.6.3-1.1 [NMU]
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.)


-- 
851223: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851223
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my NMU package "python-parse"

* Package name: python-parse
   Version : 1.6.3-1.1
   Upstream Author : Richard Jones 
* URL : https://github.com/r1chardj0n3s/parse
* License : Custom Copyright (see below)
  Section : python
LICENSE:
Copyright (c) 2012-2013 Richard Jones 

Permission is hereby granted, free of charge, to any person obtaining a
copy
of this software and associated documentation files (the "Software"),
to deal
in the Software without restriction, including without limitation the
rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

 The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS
IN THE
SOFTWARE.

It builds those binary packages:

python-parse - Parse provides the reverse function for format().
python3-parse - Parse provides the reverse function for format().

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/python-parse


Alternatively, one can download the package with dget using this command:

dget -x
https://mentors.debian.net/debian/pool/main/p/python-parse/python-parse_1.6.3-1.1.dsc

More information about python-parse can be obtained from
https://github.com/r1chardj0n3s/parse.

Changes since the last upload:

  python-parse (1.6.3-1.1) unstable; urgency=low

  * Non-maintainer upload.
  * Adds python3 support (closes: #849937).

 -- Daniel Manila   Thu, 12 Jan 2017 16:57:30 +0600

Currently any developer who uses the parse library in python3 cannot
add it as a dependency for a debian package. This NMU simply adds the
python3-parse package. The maintainer for python-parse appears to be
inactive, but regardless this is a very simple change.

If possible it would be nice to get this update into the Stretch
release, since this library is a dependency for other packages.


Regards,
  Daniel
--- End Message ---
--- Begin Message ---
control: owner -1 !
control: tags -1 moreinfo


>  * Non-maintainer upload.

>  * Adds python3 support (closes: #849937).


the maintainer is mostly MIA (already pinged several times by MIA team)

there was a new upstream bugfix release (packaged already in Ubuntu)

- 1.6.6 parse Linux system log dates (thanks Alex Cowan)
- 1.6.5 handle precision in float format (thanks Levi Kilcher)
- 1.6.4 handle pipe "|" characters in parse string (thanks Martijn Pieters)


it has a nice and good testsuite

We are probably already too late for Stretch, because binaries needs to go in 
bin-NEW
queue.
Also, we need to go in deferred queue because this is not a maintainer upload.

For this reasons I have added some more changes:
* Bump compat level to 10
* Bump std-version to 3.9.8
* Add homepage field
* Add watch file
* Add upstream signing key

* Convert copyright file in dep-5 format


and I'll sponsor in deferred/10 after sending a debdiff to the BTS

lots of stuff improved since that upload, the project seems to not have new 
releases
upcoming, so I think it would be better to make it suitable for Debian and not 
just add a single
binary.

thanks!

G.--- End Message ---

Processed: Re: New tests with libsdl2-2.0-0 (2.0.4+dfsg2-1) from stretch

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - moreinfo
Bug #830815 [libsdl2-2.0-0] libsdl2-2.0-0: SDL_RestoreWindow doesn't restore 
the window
Removed tag(s) moreinfo.
> fixed -1 libsdl2/2.0.4+dfsg1-1
Bug #830815 [libsdl2-2.0-0] libsdl2-2.0-0: SDL_RestoreWindow doesn't restore 
the window
Marked as fixed in versions libsdl2/2.0.4+dfsg1-1.
> close -1
Bug #830815 [libsdl2-2.0-0] libsdl2-2.0-0: SDL_RestoreWindow doesn't restore 
the window
Marked Bug as done

-- 
830815: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830815
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#752599: marked as done (icedove: segfault at startup)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 09:41:48 +0100
with message-id <20170113084148.5r26eewnxvlkn...@surf-1-it-3-601.aa-internet>
and subject line Re: Bug#752599: icedove: segfault at startup
has caused the Debian Bug report #752599,
regarding icedove: segfault at startup
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.)


-- 
752599: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752599
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: icedove
Version: 31.0~b1-2
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

starting up without using -safe-mode

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

starting up using -safe-mode

   * What was the outcome of this action?

segfault.

   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-rc2+ (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages icedove depends on:
ii  debianutils   4.4
ii  fontconfig2.11.0-5
ii  libasound21.0.27.2-4
ii  libatk1.0-0   2.12.0-1
ii  libc6 2.19-4
ii  libcairo2 1.12.16-2
ii  libdbus-1-3   1.8.4-1
ii  libdbus-glib-1-2  0.102-1
ii  libevent-2.0-52.0.21-stable-1
ii  libffi6   3.1-2
ii  libfontconfig12.11.0-5
ii  libfreetype6  2.5.2-1
ii  libgcc1   1:4.9.0-7
ii  libgdk-pixbuf2.0-02.30.7-1
ii  libglib2.0-0  2.40.0-3
ii  libgtk2.0-0   2.24.24-1
ii  libhunspell-1.3-0 1.3.3-1
ii  libnspr4  2:4.10.6-1
ii  libnss3   2:3.16.1-1
ii  libpango-1.0-01.36.3-1
ii  libpangocairo-1.0-0   1.36.3-1
ii  libpangoft2-1.0-0 1.36.3-1
ii  libpixman-1-0 0.32.4-1
ii  libsqlite3-0  3.8.5-2
ii  libstartup-notification0  0.12-3
ii  libstdc++64.9.0-7
ii  libvpx1   1.3.0-2
ii  libx11-6  2:1.6.2-2
ii  libxext6  2:1.3.2-1
ii  libxrender1   1:0.9.8-1
ii  libxt61:1.1.4-1
ii  psmisc22.21-2
ii  zlib1g1:1.2.8.dfsg-1

Versions of packages icedove recommends:
ii  myspell-en-au [myspell-dictionary]  2.1-5.4
ii  myspell-en-gb [myspell-dictionary]  1:3.3.0-4

Versions of packages icedove suggests:
ii  fonts-lyx 2.0.6-1
ii  libgssapi-krb5-2  1.12.1+dfsg-3

-- debconf-show failed
 /usr/lib/icedove/run-mozilla.sh -g /usr/lib/icedove/icedove-bin 2>&1 | tee 
/tmp/icedove-gdb-$(apt-cache show icedove | grep Version | awk '{ print $2 
}')_$(date +%F_%T).log
MOZILLA_FIVE_HOME=/usr/lib/icedove
  LD_LIBRARY_PATH=/usr/lib/icedove:/usr/lib/icedove/plugins:/usr/lib/icedove
DISPLAY=:0
DYLD_LIBRARY_PATH=/usr/lib/icedove:/usr/lib/icedove
 LIBRARY_PATH=
   SHLIB_PATH=/usr/lib/icedove:/usr/lib/icedove
  LIBPATH=/usr/lib/icedove:/usr/lib/icedove
   ADDON_PATH=
  MOZ_PROGRAM=/usr/lib/icedove/icedove-bin
  MOZ_TOOLKIT=
moz_debug=1
 moz_debugger=
moz_debugger_args=
/usr/bin/gdb  --args /usr/lib/icedove/icedove-bin
GNU gdb (Debian 7.7.1-2) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib/icedove/icedove-bin...Reading symbols from 
/usr/lib/debug//usr/lib/icedove/icedove-bin...done.
done.
(gdb) run
Starting program: /usr/lib/icedove/icedove-bin
[Thread debugging using libthread_db enabled]
Using host libthread_db library 
"/lib/i386-linux-gnu/i686/cmo

Bug#850029: marked as done (libbio-perl-run-perl: fails to upgrade from 'jessie' - trying to overwrite /usr/share/man/man3/Bio::Tools::Run::StandAloneBlast.3pm.gz)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 09:04:08 +
with message-id 
and subject line Bug#850029: fixed in bioperl-run 1.7.1-3
has caused the Debian Bug report #850029,
regarding libbio-perl-run-perl: fails to upgrade from 'jessie' - trying to 
overwrite /usr/share/man/man3/Bio::Tools::Run::StandAloneBlast.3pm.gz
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.)


-- 
850029: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850029
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libbio-perl-run-perl
Version: 1.7.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'jessie'.
It installed fine in 'jessie', then the upgrade to 'stretch' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package libbio-perl-run-perl.
  Preparing to unpack .../libbio-perl-run-perl_1.7.1-1_all.deb ...
  Unpacking libbio-perl-run-perl (1.7.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libbio-perl-run-perl_1.7.1-1_all.deb (--unpack):
   trying to overwrite 
'/usr/share/man/man3/Bio::Tools::Run::StandAloneBlast.3pm.gz', which is also in 
package libbio-perl-perl 1.6.924-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libbio-perl-run-perl_1.7.1-1_all.deb


cheers,

Andreas


libbio-perl-perl=1.6.924-1_libbio-perl-run-perl=1.7.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: bioperl-run
Source-Version: 1.7.1-3

We believe that the bug you reported is fixed in the latest version of
bioperl-run, 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 850...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated bioperl-run 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: Fri, 13 Jan 2017 08:25:26 +0100
Source: bioperl-run
Binary: bioperl-run libbio-perl-run-perl
Architecture: source all
Version: 1.7.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 bioperl-run - BioPerl wrappers: scripts
 libbio-perl-run-perl - BioPerl wrappers: modules
Closes: 850029
Changes:
 bioperl-run (1.7.1-3) unstable; urgency=medium
 .
   * s/Conflicts/Breaks/
 Closes: #850029
Checksums-Sha1:
 0b7339653951b8a40079ac15aa07bd9c05ac4999 2597 bioperl-run_1.7.1-3.dsc
 3e29db96b56dd126ee2148668204e6a7ad073c68 12540 
bioperl-run_1.7.1-3.debian.tar.xz
 3ed0361ccf7d81b2a01518bed4f7e669ba13873c 44216 bioperl-run_1.7.1-3_all.deb
 b48d0d3e6704c3e5eeb1209da948e54c1efd1f64 10284 
bioperl-run_1.7.1-3_amd64.buildinfo
 9045bbf5aa54634a119e53db9a449f26d9c3b930 815884 
libbio-perl-run-perl_1.7.1-3_all.deb
Checksums-Sha256:
 c261be8fc9cbf4987e7e6a381c55ca7a06653f73ada55450db85a5731b2b95fa 2597 
bioperl-run_1.7.1-3.dsc
 2600a4fe7aec96598c536a1c309374a1dd150f26bf5c2529547fd5664415166e 12540 
bioperl-run_1.7.1-3.debian.tar.xz
 8b15dc98e362b6a73a75b7bd778c79b1e4d842d327867f3c71da70b0bf09c21f 44216 
bioperl-run_1.7.1-3_all.deb
 1e0ea60f0ed40213c4d848e3f276b2cf73ce71ec9d7216ddc0d5949308281678 10284 
bioperl-run_1.7.1-3_amd64.buildinfo
 224c3c6de868a69bb7d4777ec9d730540ca5f33e627739902d5754a9fd82e6da 815884 
libbio-perl-run-perl_1.7.1-3_all.deb
Files:
 7c4a23d4786b7e16e7309277792a77b5 2597 science optional bioperl-run_1.7.1-3.dsc
 d22a94a04454e7900aa1f550c1c3ca53 12540 science optional 
bioperl-run_1.7.1-3.debian.tar.xz
 d2454c81bb9bc5693045aecf1ffc1491 44216 science optional 
bioperl-run_1.7.1-3_all.deb
 d281570f1590a6fd041b018eb2cedca1 10284 science optional 
bioperl-run_1.7.1-3_amd64.buildinfo
 a18e45c5344c86ef08464bb7dd922ed8 815884 perl optional 
libbio-perl-run-perl_1.7.1-3_all.deb

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlh4gioRHHRpbGxlQGRl
Ymlhbi5vcmcACgk

Bug#850575: marked as done (diaspora: cannot install because broken maintscript line in preinst and missing gem files)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 09:07:17 +
with message-id 
and subject line Bug#850575: fixed in diaspora 0.6.0.0+debian-8
has caused the Debian Bug report #850575,
regarding diaspora: cannot install because broken maintscript line in preinst 
and missing gem files
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.)


-- 
850575: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850575
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: diaspora
Version: 0.6.0.0+debian-7
Severity: grave

In the debian/maintscript file, you have:
dir_to_symlink /usr/share/diaspora/config 0.5.9.1+debian3 diaspora-common

This is not the correct syntax for the dir_to_symlink command: it
should be
dir_to_symlink pathname new-target [prior-version [package]]

So I guess this line should read:
dir_to_symlink /usr/share/diaspora/config /etc/diaspora 0.5.9.1+debian3 
diaspora-common

With this change, then diaspora installs more successfully.  (Well,
successfully, except that it couldn't find the gem mysql2 (I've gone
for the mysql option.):

Could not find gem 'mysql2 (~> 0.4.4)' in any of the gem sources listed in your
Gemfile or available on this machine.

Installing ruby-mysql2 then gave the error:

export DB_NAME=diaspora_production
RAILS_ENV=production DB=mysql ENVIRONMENT_URL=https://diaspora.d-and-j.net
Verifying we have all required libraries...
Resolving dependencies...
Bundler could not find compatible versions for gem "jquery-ui-rails":
  In Gemfile:
jquery-ui-rails (~> 6.0)

rails_admin (~> 0.8.1) was resolved to 0.8.1, which depends on
  jquery-ui-rails (~> 5.0)

Oh dear :-(

Any suggestions?

   Julian

-- System Information:
Debian Release: stretch/sid
  APT prefers jessie
  APT policy: (500, 'jessie'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: diaspora
Source-Version: 0.6.0.0+debian-8

We believe that the bug you reported is fixed in the latest version of
diaspora, 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 850...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated diaspora 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: Fri, 13 Jan 2017 13:10:14 +0530
Source: diaspora
Binary: diaspora
Architecture: source
Version: 0.6.0.0+debian-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Pirate Praveen 
Description:
 diaspora   - distributed social networking service
Closes: 850575
Changes:
 diaspora (0.6.0.0+debian-8) unstable; urgency=medium
 .
   * Remove unused overrides
   * Add tag for all patches
 .
   [ Julian Gilbey ]
   * Fix maintscript syntax (Closes: #850575)
Checksums-Sha1:
 d8421b15268e1986f2f179e51877bd68c11106e2 2070 diaspora_0.6.0.0+debian-8.dsc
 41d40e7ec210dbd85fdfce306add656a1bfa85b4 23608 
diaspora_0.6.0.0+debian-8.debian.tar.xz
Checksums-Sha256:
 dfdf7c058ea59169d19674793edc492e84325a5945ada59b412c296ed3b51721 2070 
diaspora_0.6.0.0+debian-8.dsc
 ef094749cc3606ab7fc42fc2c6f555698150edd70d2fc94b1578a266180f6ad6 23608 
diaspora_0.6.0.0+debian-8.debian.tar.xz
Files:
 2987b1c4b68e779f93834018ca58bd57 2070 contrib/web optional 
diaspora_0.6.0.0+debian-8.dsc
 52e6795225d7d7b572900e27cfee7de0 23608 contrib/web optional 
diaspora_0.6.0.0+debian-8.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEKnl0ri/BUtd4Z9pKzh+cZ0USwioFAlh4j4UACgkQzh+cZ0US
wio2+A/+OYvRzZwD9hIC5JWg1X9sKe1GAzMziQ1wjkNQZEmDslIbfMRnfzPU2yNR
3cegc4AsjmAsDS4evtS+ILLZQ18BJN+TFoSNdE2GGB2nYfcWQgrBoiU4OMdwae6p
t3aKuFDaEdn4L1Kfu9eq5pjeoFzWZU/HR9m5RzvjivHxHe5HNrkfHFZjUCX5fNcu
GphSIoQ40tHQlzTrGOfR4ue1hjseqCsMrB0tmT7e3TotRcQnUmf7mI7xUvIw/3Da
MQ8Z0whDvpfPCXmOHaory9t4aTD/kj/o7kfjzs6+SbnFx1FVHa1zJWlICBMJDjRw
9xUe6LgZ3nfPxetknihGWA6uMCEvJE+jl1ULPiaohWwMfBhUkT7yHGyRYQA8d3cy
T5h2cygDEu/L++v

Bug#851219: marked as done (sra-toolkit: /usr/bin/kget is already shipped by the package kget)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 09:08:42 +
with message-id 
and subject line Bug#851219: fixed in sra-sdk 2.8.1+dfsg-2
has caused the Debian Bug report #851219,
regarding sra-toolkit: /usr/bin/kget is already shipped by the package kget
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.)


-- 
851219: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851219
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sra-toolkit
Version: 2.8.1+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package sra-toolkit.
  Preparing to unpack .../22-sra-toolkit_2.8.1+dfsg-1_amd64.deb ...
  Unpacking sra-toolkit (2.8.1+dfsg-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-jiWh8D/22-sra-toolkit_2.8.1+dfsg-1_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/kget', which is also in package kget 
4:16.08.0-2
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)


cheers,

Andreas


kget=4%16.08.0-2_sra-toolkit=2.8.1+dfsg-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: sra-sdk
Source-Version: 2.8.1+dfsg-2

We believe that the bug you reported is fixed in the latest version of
sra-sdk, 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 851...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated sra-sdk 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: Fri, 13 Jan 2017 09:23:03 +0100
Source: sra-sdk
Binary: sra-toolkit
Architecture: source amd64
Version: 2.8.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 sra-toolkit - utilities for the NCBI Sequence Read Archive
Closes: 851219
Changes:
 sra-sdk (2.8.1+dfsg-2) unstable; urgency=medium
 .
   * Deal with name space conflict with kget
 Closes: #851219
Checksums-Sha1:
 a8fb467319b9867f871d9ed6bb55a515ae2b3004 2137 sra-sdk_2.8.1+dfsg-2.dsc
 26a96d29263a696c16a725dc2ab761c09c6c1709 12684 
sra-sdk_2.8.1+dfsg-2.debian.tar.xz
 9f4b902a4e4331cdbb217f0afb297384b5667a6a 5807 
sra-sdk_2.8.1+dfsg-2_amd64.buildinfo
 1dde5961229102952d67cb8abaa51f348a515a1a 3084468 
sra-toolkit-dbgsym_2.8.1+dfsg-2_amd64.deb
 f951e24754919956fba989d1206cd4c8cdb74c28 1489408 
sra-toolkit_2.8.1+dfsg-2_amd64.deb
Checksums-Sha256:
 92e064180a7b51b2b619666b3f4168df63006f17c7f9235ac08769e9eaaf1968 2137 
sra-sdk_2.8.1+dfsg-2.dsc
 62cd16f4e966744682eec4419c5b0d453fb217e80472281e712ff9c9a80f68cb 12684 
sra-sdk_2.8.1+dfsg-2.debian.tar.xz
 9d5cb5f20c0fac4d2b668858ce4835b6a4b1d4657d06d8f52ddfc3b45ca0cba2 5807 
sra-sdk_2.8.1+dfsg-2_amd64.buildinfo
 1f458f689071e3a3aa3933d7492d23af023e7ad5f9bbe9199bc76f7b59ab8186 3084468 
sra-toolkit-dbgsym_2.8.1+dfsg-2_amd64.deb
 930904686240efbb03a308241ec5dc55e792eed90a32343e195979630b9a5068 1489408 
sra-toolkit_2.8.1+dfsg-2_amd64.deb
Files:
 d8fb0b2efab99c654ee91f6800b96884 2137 science optional sra-sdk_2.8.1+dfsg-2.dsc
 c3f926e61c01229ac3fd0264eee60506 12684 science optional 
sra-sdk_2.8.1+dfsg-2.debian.tar.xz
 f435df31c863a66fbb989637af040cfc 5807 science optional 
sra-sdk_2.8.1+dfsg-2_amd64.buildinfo
 ae0b9195999b84296ee9062cba6dbb19 3084468 debug extra 
sra-toolkit-dbgsym_2.8.1+dfsg-2_amd64.deb
 551e90848ee72ca71888c3b6708997da 1489408 science optional 
sra-toolkit_2.8.1+dfsg-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlh4jywRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFstQ//VGJkfRjc4mmQp3W2hbLccbehcFgkWexO
3CqOwtBosdQcBQR7fgafaXp81/iA/OmA3jFCg1JmqJlI3CKEIUchvf2hhEqRt2Cb
lmt7ibD3LfvLdx2ns0Gx5iCjAIPA2Vca2ps/EjDI23phoTnqI7nSx9FPy32Kz4lt
/1k1DvyvF8iywk9JdUYWl/DREOUvc5kYCvROHfJz0Fu4t822O9S/Oxn1H3FwQ4Hn
oac6j0ZGAbJOFIGubokpG6kHUVyo2cJ12SiCmurphXSa9iTPNaa8EGQ3wDmEQLIK
aI0SxFq6EAGPDpXqnoSHOCbJUG1Wi+of2xsZ0/w3iTTobtRnImdA2nEBZ6NTt0Nv
gGzvu07LXLwIbA62vt4YL/hWbKTbT5uDul3nR2x7siYgouS99lHmI7MJQ6QIsagh
UUJmzSJ/tGc7Gav+BsRGAt

Bug#851230: marked as done (primer3 FTCBFS: uses build architecture c++ compiler via unconventional variable CPP)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 09:08:31 +
with message-id 
and subject line Bug#851230: fixed in primer3 2.3.7-3
has caused the Debian Bug report #851230,
regarding primer3 FTCBFS: uses build architecture c++ compiler via 
unconventional variable CPP
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.)


-- 
851230: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851230
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: primer3
Version: 2.3.7-2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

primer3 fails to cross build from source, because it stores its C++
compiler in the unconventional variable CPP. dh_auto_build passes cross
compilers via CXX. Thus primer3 ends up using the build architecture C++
compiler. After overriding CPP, it cross builds successfully. Please
consider applying the attached patch.

Helmut
diff --minimal -Nru primer3-2.3.7/debian/changelog 
primer3-2.3.7/debian/changelog
--- primer3-2.3.7/debian/changelog  2016-06-27 16:34:27.0 +0200
+++ primer3-2.3.7/debian/changelog  2017-01-13 06:58:59.0 +0100
@@ -1,3 +1,10 @@
+primer3 (2.3.7-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Pass CXX as CPP (Closes: #-1)
+
+ -- Helmut Grohne   Fri, 13 Jan 2017 06:58:59 +0100
+
 primer3 (2.3.7-2) unstable; urgency=medium
 
   * Team Upload
diff --minimal -Nru primer3-2.3.7/debian/rules primer3-2.3.7/debian/rules
--- primer3-2.3.7/debian/rules  2016-06-27 16:34:27.0 +0200
+++ primer3-2.3.7/debian/rules  2017-01-13 06:58:59.0 +0100
@@ -10,6 +10,9 @@
 %:
dh $@ --sourcedirectory=src
 
+override_dh_auto_build:
+   dh_auto_build -- 'CPP=$$(CXX)'
+
 override_dh_auto_test:
dh_auto_test --sourcedirectory=test
dh clean --sourcedirectory=test
--- End Message ---
--- Begin Message ---
Source: primer3
Source-Version: 2.3.7-3

We believe that the bug you reported is fixed in the latest version of
primer3, 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 851...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated primer3 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: Fri, 13 Jan 2017 08:32:57 +0100
Source: primer3
Binary: primer3 primer3-examples
Architecture: source amd64 all
Version: 2.3.7-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 primer3- tool to design flanking oligo nucleotides for DNA amplification
 primer3-examples - tool to design flanking oligo nucleotides for DNA 
amplification (
Closes: 851230
Changes:
 primer3 (2.3.7-3) unstable; urgency=medium
 .
   [ Andreas Tille ]
   * debhelper 10
   * d/watch: version=4
 .
   [ Helmut Grohne ]
   * Fix FTCBFS: Pass CXX as CPP (Closes: #851230)
Checksums-Sha1:
 f7235f243977edf704a9f7115e647b89cfdff1f0 2138 primer3_2.3.7-3.dsc
 0b6191c8c33f0ed7708989e0b9a9318958ceb274 10920 primer3_2.3.7-3.debian.tar.xz
 872f615bf844225964d4b5e91699974394491468 286332 
primer3-dbgsym_2.3.7-3_amd64.deb
 33ee83b03d1d54fd52ad1f475bec5214b11ad141 1322884 
primer3-examples_2.3.7-3_all.deb
 b00e36f7ccb0456a2f8c4bd7b4efdc3e61f56aec 4905 primer3_2.3.7-3_amd64.buildinfo
 d48a20bd961bba5ae1fae9fded96a0055c992c06 173208 primer3_2.3.7-3_amd64.deb
Checksums-Sha256:
 fedccd2410ade18a2a7bf778bbe591b04fc15dda2e85607f840225dd468d3393 2138 
primer3_2.3.7-3.dsc
 295dbd76ca653bd299deb54317ec973564c8c1e592bd05014ca594ce5d899f58 10920 
primer3_2.3.7-3.debian.tar.xz
 b9c2cfae4af263cee39670725bfc35a1a202aa22fc4d461264ed02e11ba9663c 286332 
primer3-dbgsym_2.3.7-3_amd64.deb
 0b80a302726d8b7dfd80b0c4908c3b22969c582733e0c193164ad6152a40ac37 1322884 
primer3-examples_2.3.7-3_all.deb
 8bfe7d4a3c3ed05a7b8631e3b540be2e85ab36d563dca3dcc098c7a26a65793c 4905 
primer3_2.3.7-3_amd64.buildinfo
 d5e98515cb1b70130c7c46f07fb1ef5816c09e405dd4074a4eccb1a84c8f28e4 173208 
primer3_2.3.7-3_amd64.deb
Files:
 492992e3e0c4aa87bed6b934698024ff 2138 science optional primer3_2.3.7-3.dsc
 47b3a6398bccdf92a639577bec9d048e 10920 science optional 
primer3_2.3.7-3.debian.tar.xz
 f6ff7cf5df7791f07e5

Bug#722215: marked as done (Does not drop supplementary groups)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 09:34:11 +
with message-id 
and subject line Bug#722215: fixed in tinyproxy 1.8.4-1
has caused the Debian Bug report #722215,
regarding Does not drop supplementary groups
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.)


-- 
722215: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722215
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tinyproxy
Version: 1.8.3-3
Severity: important
Tags: upstream patch
Control: forwarded -1 https://bugzilla.banu.com/show_bug.cgi?id=115

When configured to change to a different user and group after startup
(User and Group configuration directives), tinyproxy does not drop
supplementary groups. These are still inherited from the calling
process. This may lead to a situation where tinyproxy has more access
than expected. At least on Debian systems root shells have "root" as a
supplementary group. This currently leads to the situation where
tinyproxy can read files readable only by the group "root".

The attached patch fixes this by dropping all supplementary groups if
the Group directive is set.

If only the User directive is set, groups are not dropped. This is
inline with the current code that also does not change the primary group
of the process in this case. I'm not sure if that's the behavior an
average user would expect. It might be safer to change to the primary
group of that user in this case and to either also drop supplementary
groups or change to the supplementary groups of this user with the
initgroups function.

The patch adds a new check for the setgroups function as this function
is not part of POSIX.

I also submitted this bug upstream as
https://bugzilla.banu.com/show_bug.cgi?id=115. But it would still be
useful to fix it with a patch in the Debian package until it's fixed
upstream.

Gaudenz

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (800, 'testing'), (700, 'unstable'), (50, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.10-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
>From cb0b7454c17dceb9be7ebb6b5f9e86c2a3389f36 Mon Sep 17 00:00:00 2001
From: Gaudenz Steinlin 
Date: Mon, 9 Sep 2013 08:33:48 +0200
Subject: [PATCH] Drop supplementary groups

Supplementary groups are inherited from the calling process. Drop all
supplementary groups if the "Group" configuration directive is set to
change to a different user. Otherwise the process may have more rights
than expected.
---
 configure.ac |  2 +-
 src/main.c   | 10 ++
 2 files changed, 11 insertions(+), 1 deletion(-)

diff --git a/configure.ac b/configure.ac
index 303fc7b..377e204 100644
--- a/configure.ac
+++ b/configure.ac
@@ -203,7 +203,7 @@ AC_FUNC_REALLOC
 AC_CHECK_FUNCS([gethostname inet_ntoa memchr memset select socket strcasecmp \
 strchr strdup strerror strncasecmp strpbrk strstr strtol])
 AC_CHECK_FUNCS([isascii memcpy setrlimit ftruncate regcomp regexec])
-AC_CHECK_FUNCS([strlcpy strlcat])
+AC_CHECK_FUNCS([strlcpy strlcat setgroups])
 
 
 dnl Enable extra warnings
diff --git a/src/main.c b/src/main.c
index a7ae9c7..abb047d 100644
--- a/src/main.c
+++ b/src/main.c
@@ -296,6 +296,16 @@ change_user (const char *program)
 exit (EX_NOPERM);
 }
 
+#ifdef HAVE_SETGROUPS
+/* Drop all supplementary groups, otherwise these are inherited from the calling process */
+if (setgroups (0, NULL) < 0) {
+fprintf (stderr,
+ "%s: Unable to drop supplementary groups.\n",
+ program);
+exit (EX_NOPERM);
+}
+#endif
+
 log_message (LOG_INFO, "Now running as group \"%s\".",
  config.group);
 }
-- 
1.8.4.rc3

--- End Message ---
--- Begin Message ---
Source: tinyproxy
Source-Version: 1.8.4-1

We believe that the bug you reported is fixed in the latest version of
tinyproxy, 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 722...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jordi Mallach  (supplier of updated tinyproxy package)

(This message was generated autom

Bug#848809: marked as done (cwltool: FTBFS: help2man: can't get `--help' info from cwltool/cwltest.py)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 09:33:34 +
with message-id 
and subject line Bug#848809: fixed in cwltool 1.0.2017093653-1
has caused the Debian Bug report #848809,
regarding cwltool: FTBFS: help2man: can't get `--help' info from 
cwltool/cwltest.py
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.)


-- 
848809: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848809
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cwltool
Version: 1.0.20160209222805-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161219 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> help2man cwltool/cwltest.py -I debian/cwltest.help2man -N -o debian/cwltest.1 
> --version-string "$(dpkg-parsechangelog  | grep Version:  | cut -f2 -d\ )"
> help2man: can't get `--help' info from cwltool/cwltest.py
> Try `--no-discard-stderr' if option outputs to stderr
> debian/rules:17: recipe for target 'debian/cwltest.1' failed
> make[1]: *** [debian/cwltest.1] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/2016/12/19/cwltool_1.0.20160209222805-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: cwltool
Source-Version: 1.0.2017093653-1

We believe that the bug you reported is fixed in the latest version of
cwltool, 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 848...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated cwltool 
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: SHA512

Format: 1.8
Date: Thu, 12 Jan 2017 21:29:55 -0800
Source: cwltool
Binary: cwltool
Architecture: source
Version: 1.0.2017093653-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Michael R. Crusoe 
Description:
 cwltool- Common workflow language reference implementation
Closes: 845982 848809
Changes:
 cwltool (1.0.2017093653-1) unstable; urgency=medium
 .
   * Team upload
 .
   [ Michael R. Crusoe ]
   * New upstream release
 .
   [ Andreas Tille ]
   * Add missing Build-Depends: python-keepalive
 Closes: #845982
   * d/watch: version=4
   * debhelper 10
   * Add python-typing as Build-Depends and comment patch to skip it
   * Do not try to create manpage for removed tool cwltest
 Closes: #848809
   * Remove empty template for upstream metadata
   * Add Build-Depends: python-ruamel.yaml (>=0.12.4)
Checksums-Sha1:
 51b5a1e262ac6c7dc840f46c1464a45cbc533800 2234 cwltool_1.0.2017093653-1.dsc
 13a478192bcdfed93c4a82051ea9d1b6e3a2ee5b 216701 
cwltool_1.0.2017093653.orig.tar.gz
 b10c98821462caa9e697c5bf04022249bb90c34a 3236 
cwltool_1.0.2017093653-1.debian.tar.xz
Checksums-Sha256:
 277444abef275addba4731310abe02e316621f32d08bf2cef56886b49aea5f0b 2234 
cwltool_1.0.2017093653-1.dsc
 c67698d32928235acf63c1d7bea6222ba83fbfd482cd789210e8e383a7bbcb1f 216701 
cwltool_1.0.2017093653.orig.tar.gz
 f4fd57995bba7b2fd82cfe87c9ca750c4f7892ee1a021c6058d69e396424f81c 3236 
cwltool_1.0.2017093653-1.debian.tar.xz
Files:
 1933f436515773b621596cd3da6e2070 2234 science optional 
cwltool_1.0.2017093653-1.dsc
 61aa5575378a81ad13c86867847e0796 216701 science optional 
cwltool_1.0.2017093653.orig.tar.gz
 73130319dfd1b0c6146236dc613e17d9 3236 science optional 
cwltool_1.0.2017093653-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAlh4mWIACgkQPCZ2P2xn
5uJZ3BAApyWUIrcag2aFIgPvTYRK8q6HNekKuSMWY6+1m/e9r7Ibhf2Ftzrc1o2Y
rR225L947vegr0w5TqCxHrhlMdQM0Ma8jIs8d33eXgKqkq187u9ZwuMvOjDr+LXX
nTq79w6h2Vt+VNIAWSzgdLS9rQQKeE6KPUS77o9rhEwMphl12iBQPUdGiIZoUt4/
MgEnS9h4noSAB

Bug#845982: marked as done (cwltool: accesses the internet during build)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 09:33:34 +
with message-id 
and subject line Bug#845982: fixed in cwltool 1.0.2017093653-1
has caused the Debian Bug report #845982,
regarding cwltool: accesses the internet during build
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.)


-- 
845982: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845982
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cwltool
Version: 1.0.20160209222805-1
Severity: important
Justification: Policy 4.9
User: la...@debian.org
Usertags: network-access

Dear Maintainer,

Whilst cwltool builds successfully on unstable/amd64, according to
Debian Policy 4.9 packages may not attempt network access during
a build.

   00:00:00.00 IP 71ed44bbb607.38264 > 10.0.1.1.domain: 45942+ A? 
pypi.python.org. (33)
   00:00:00.50 IP 71ed44bbb607.38264 > 10.0.1.1.domain: 51187+ ? 
pypi.python.org. (33)
   00:00:00.018886 IP 10.0.1.1.domain > 71ed44bbb607.38264: 45942 2/0/0 CNAME 
prod.python.map.fastly.net., A 151.101.60.223 (89)
   00:00:00.019374 IP 10.0.1.1.domain > 71ed44bbb607.38264: 51187 2/0/0 CNAME 
prod.python.map.fastly.net.,  2a04:4e42:f::223 (101)
   00:00:00.019731 IP 71ed44bbb607.40490 > 151.101.60.223.https: Flags [S], seq 
1748635535, win 29200, options [mss 1460,sackOK,TS val 9636528 ecr 0,nop,wscale 
7], length 0
   00:00:00.029028 IP 151.101.60.223.https > 71ed44bbb607.40490: Flags [S.], 
seq 202607934, ack 1748635536, win 28120, options [mss 1400,sackOK,TS val 
2428883026 ecr 9636528,nop,wscale 9], length 0
   00:00:00.029072 IP 71ed44bbb607.40490 > 151.101.60.223.https: Flags [.], ack 
1, win 229, options [nop,nop,TS val 9636530 ecr 2428883026], length 0
   00:00:00.036824 IP 71ed44bbb607.40490 > 151.101.60.223.https: Flags [P.], 
seq 1:239, ack 1, win 229, options [nop,nop,TS val 9636532 ecr 2428883026], 
length 238
   00:00:00.047368 IP 151.101.60.223.https > 71ed44bbb607.40490: Flags [.], seq 
1:1389, ack 239, win 58, options [nop,nop,TS val 2428883031 ecr 9636532], 
length 1388
   00:00:00.047430 IP 71ed44bbb607.40490 > 151.101.60.223.https: Flags [.], ack 
1389, win 250, options [nop,nop,TS val 9636535 ecr 2428883031], length 0

  [..]

The full build log (including tcpdump output) is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


cwltool.1.0.20160209222805-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: cwltool
Source-Version: 1.0.2017093653-1

We believe that the bug you reported is fixed in the latest version of
cwltool, 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 845...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated cwltool 
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: SHA512

Format: 1.8
Date: Thu, 12 Jan 2017 21:29:55 -0800
Source: cwltool
Binary: cwltool
Architecture: source
Version: 1.0.2017093653-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Michael R. Crusoe 
Description:
 cwltool- Common workflow language reference implementation
Closes: 845982 848809
Changes:
 cwltool (1.0.2017093653-1) unstable; urgency=medium
 .
   * Team upload
 .
   [ Michael R. Crusoe ]
   * New upstream release
 .
   [ Andreas Tille ]
   * Add missing Build-Depends: python-keepalive
 Closes: #845982
   * d/watch: version=4
   * debhelper 10
   * Add python-typing as Build-Depends and comment patch to skip it
   * Do not try to create manpage for removed tool cwltest
 Closes: #848809
   * Remove empty template for upstream metadata
   * Add Build-Depends: python-ruamel.yaml (>=0.12.4)
Checksums-Sha1:
 51b5a1e262ac6c7dc840f46c1464a45cbc533800 2234 cwltool_1.0.2017093653-1.dsc
 13a478192bcdfed93c4a82051ea9d1b6e3a2ee5b 216701 
cwltool_1.0.2017093653.orig.tar.gz
 b10c98821462caa9e697c5bf04022249bb90c34a 3236 
cwltool_1.0.2017093653-1.debian.tar.xz
Checksums-Sha256:
 277444abef275addba4731310abe02e316621f32d08bf2cef56886b49aea5f0b 2234 
cwltool_1.0.2017093653-1.dsc
 c67698d32

Bug#844499: marked as done (piuparts: links to README and manpage on https://piuparts.debian.org/ are broken)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 10:45:15 +0100
with message-id 
<20170113094515.ldvqw4e52l6i6...@vis.informatik.uni-osnabrueck.de>
and subject line Re: links to README and manpage on 
https://piuparts.debian.org/ work fine for me today
has caused the Debian Bug report #844499,
regarding piuparts: links to README and manpage on https://piuparts.debian.org/ 
are broken
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.)


-- 
844499: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844499
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: piuparts
Severity: normal

Jochen Sprickerhof reported this on IRC:

-- 
cheers,
Holger


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Hi Holger,

* Holger Levsen  [2017-01-11 01:09]:
> you reported this on irc, but
> https://piuparts.debian.org/doc/piuparts.1.html and
> https://piuparts.debian.org/doc/README.html are both linked from the top
> left navigation menu on https://piuparts.debian.org/ and those links
> work. Can you confirm or clarify please?

Works fine for me as well, thanks for taking care!

Cheers Jochen


signature.asc
Description: PGP signature
--- End Message ---

Bug#849930: marked as done (easybind: FTBFS (Cannot find pom file easybind.pom))

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 10:50:41 +0100
with message-id <57092b60-f2e4-9a9d-5b62-ba8964089...@apache.org>
and subject line Re: Bug#849930: easybind: FTBFS (Cannot find pom file 
easybind.pom)
has caused the Debian Bug report #849930,
regarding easybind: FTBFS (Cannot find pom file easybind.pom)
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.)


-- 
849930: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849930
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:easybind
Version: 1.0.3-1
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
dh build-indep --buildsystem=gradle --with=maven-repo-helper
   dh_testdir -i -O--buildsystem=gradle
   dh_update_autotools_config -i -O--buildsystem=gradle
   dh_autoreconf -i -O--buildsystem=gradle
   dh_auto_configure -i -O--buildsystem=gradle
   dh_auto_build -i -O--buildsystem=gradle
mkdir -p .gradle/init.d
cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/
gradle --info --console plain --offline --stacktrace --no-daemon 
--refresh-dependencies --gradle-user-home .gradle -Duser.home=. 
-Duser.name=debian jar
Initialized native services in: /<>/.gradle/native
Starting Build
Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
using SubsetScriptTransformer.

[... snipped ...]

Total time: 7.476 secs
Stopped 0 compiler daemon(s).
   dh_auto_test -i -O--buildsystem=gradle
 fakeroot debian/rules binary-indep
dh binary-indep --buildsystem=gradle --with=maven-repo-helper
   dh_testroot -i -O--buildsystem=gradle
   dh_prep -i -O--buildsystem=gradle
rm -f debian/libeasybind-java.substvars
rm -f debian/libeasybind-java.*.debhelper
rm -rf debian/libeasybind-java/
   dh_auto_install -i -O--buildsystem=gradle
install -d debian/libeasybind-java
   mh_install -i -O--buildsystem=gradle
mh_installpom --java-lib--package=libeasybind-java   
build/debian/easybind.pom
mh_cleanpom   --package=libeasybind-java 
build/debian/easybind.pom debian/.mh/pom.xml debian/.mh/pom.properties
Cannot find pom file /<>/build/debian/easybind.pom
Dec 29, 2016 6:32:03 AM org.debian.maven.repo.POMCleaner cleanPom
SEVERE: null
java.io.FileNotFoundException: build/debian/easybind.pom (No such file or 
directory)
at java.io.FileInputStream.open0(Native Method)
at java.io.FileInputStream.open(FileInputStream.java:195)
at java.io.FileInputStream.(FileInputStream.java:138)
at org.debian.maven.util.Readers.read(Readers.java:50)
at org.debian.maven.repo.POMReader.readPom(POMReader.java:57)
at 
org.debian.maven.repo.POMTransformer.transformPom(POMTransformer.java:226)
at 
org.debian.maven.repo.POMTransformer.transformPom(POMTransformer.java:211)
at org.debian.maven.repo.POMCleaner.cleanPom(POMCleaner.java:75)
at org.debian.maven.repo.POMCleaner.main(POMCleaner.java:372)

Cannot find pom file /<>/build/debian/easybind.pom
Dec 29, 2016 6:32:03 AM org.debian.maven.repo.POMCleaner cleanPom
SEVERE: null
java.io.FileNotFoundException: build/debian/easybind.pom (No such file or 
directory)
at java.io.FileInputStream.open0(Native Method)
at java.io.FileInputStream.open(FileInputStream.java:195)
at java.io.FileInputStream.(FileInputStream.java:138)
at org.debian.maven.util.Readers.read(Readers.java:50)
at org.debian.maven.repo.POMReader.readPom(POMReader.java:57)
at 
org.debian.maven.repo.POMTransformer.transformPom(POMTransformer.java:226)
at 
org.debian.maven.repo.POMTransformer.transformPom(POMTransformer.java:211)
at org.debian.maven.repo.POMCleaner.cleanPom(POMCleaner.java:75)
at org.debian.maven.repo.POMCleaner.main(POMCleaner.java:372)

/usr/bin/mh_installpom: line 148: debian/.mh/pom.properties: No such file or 
directory
debian/rules:7: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary-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.

I

Bug#849972: marked as done (yard: please make the output reproducible)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 10:04:28 +
with message-id 
and subject line Bug#849972: fixed in yard 0.9.7-1
has caused the Debian Bug report #849972,
regarding yard: please make the output reproducible
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.)


-- 
849972: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849972
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yard
Version: 0.9.5-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: toolchain fileordering
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0], we noticed
that yardoc generates output that is not reproducible due to the
use of a fallback glob that relies on (non-deterministic)
filesystem ordering.

Patch attached.

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/lib/yard/parser/source_parser.rb b/lib/yard/parser/source_parser.rb
index b12d902..d6972ba 100755
--- a/lib/yard/parser/source_parser.rb
+++ b/lib/yard/parser/source_parser.rb
@@ -109,7 +109,7 @@ module YARD
 reject {|p| !File.file?(p) || excluded.any? {|re| p =~ re } }
 
   log.enter_level(level) do
-parse_in_order(*files.uniq)
+parse_in_order(*files.sort.uniq)
   end
 end
 
--- End Message ---
--- Begin Message ---
Source: yard
Source-Version: 0.9.7-1

We believe that the bug you reported is fixed in the latest version of
yard, 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 849...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated yard 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: Thu, 12 Jan 2017 21:45:38 -0200
Source: yard
Binary: yard yard-doc
Architecture: source
Version: 0.9.7-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Antonio Terceiro 
Description:
 yard   - Ruby documentation tool
 yard-doc   - Ruby documentation tool - documentation
Closes: 849972
Changes:
 yard (0.9.7-1) unstable; urgency=medium
 .
   * Team upload
 .
   [ Lucas Nussbaum ]
   * Fix permissions of files in /usr/share/yard/templates. (Avoids lintian
 warnings)
 .
   [ Antonio Terceiro ]
   * New upstream release. Includes change to make the output reproducible
 (Closes: #849972)
   * debian/rules, debian/ruby-tests.rake: refreshed with `dh-make-ruby -w`
   * debian/rules: install using the Rubygems layout. This makes most of the
 patches we have been carrying here obsolete. Remaining patches
 refreshed/updated.
Checksums-Sha1:
 7a83c7c9339c1c916527f5fb46f89ccfd0db3df9 2181 yard_0.9.7-1.dsc
 ff00cae41d704532aefd47791f0562ca73bf056f 623668 yard_0.9.7.orig.tar.gz
 68eb65f7aea259a247591d7de9033d77afc78675 79052 yard_0.9.7-1.debian.tar.xz
Checksums-Sha256:
 8043bd6aca0d3ea05b6163f5bda998143e3bbb1125d13ce7b2d5ff800d1d67ff 2181 
yard_0.9.7-1.dsc
 abf92f99929dd9a7292a07cff0a7e88df72c187be7d4b2abb229e0bad724d318 623668 
yard_0.9.7.orig.tar.gz
 e05de54dd3d05a6fb351f86a0889388ac6f813e2731884df45bcb89d6f8b3c05 79052 
yard_0.9.7-1.debian.tar.xz
Files:
 2be9421db40a96e7b2ca4d6c1a5d930d 2181 ruby optional yard_0.9.7-1.dsc
 778d0eee1f178a438fe0895423adb702 623668 ruby optional yard_0.9.7.orig.tar.gz
 a17b9604a77b9f69e59bc3015f562279 79052 ruby optional yard_0.9.7-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAlh4o6UACgkQ/A2xu81G
C96POxAAtWP6ZjNlZVIKEUkbZj3YhNhwDxjhqukM/JfuvwsyS6qwp6vIAu/tlYc+
w0wm08Y0ml79HJHzi7E/lLPG8J+2AKkRhnbdLz+7gc9fzlVfCKPr8sHu9vrROoYE
OC/lZRNFg8AmooWjpUVXecRqyJtLk18sqZJJEAEgnguPO5vK7bLpuFu4/GnTaYd6
CcYnABVFytODHkKlV7k+JDfhOCN13/s/mTl4LLB4Akm4nky2cdJ73BoPvdX0rTW8
srnDYxQAhOOoqDkvUGa87RkPBXLTxfryaHnD680qFE18Nw/IgaOljWdbCkvkBxg6
eXjPoUSTh/f6Qua+IvVtRRxcrdXNjzqj/nlywiR6nRJGaDH1vTT0Ykerjyffd4y4
oFPGlKUV6QSMgfWG1ps/QeDKa17El3Q24z8Zv5eF++7OZtB5sA+l/Enb1VTMnXPQ
EmG+HoxNp/KVYVp2j2bZtK4HND4zJgicJ49G3FdoLmcOk6XhqflJCdtcsiLc3SKM
4jUSZp7Vs0C3hrDzbaVjL

Bug#806227: marked as done (nagios-plugins-contrib: Please use Monitoring::Plugin instead of Nagios::Plugin)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 11:37:24 +0100
with message-id <20170113103724.wpbznclmtz6mt...@t440s.egolov.redhat.com>
and subject line Re: Bug#806227: nagios-plugin-contrib: Please use 
Monitoring::Plugin instead of Nagios::Plugin
has caused the Debian Bug report #806227,
regarding nagios-plugins-contrib: Please use Monitoring::Plugin instead of 
Nagios::Plugin
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.)


-- 
806227: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806227
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nagios-plugins-contrib
Version: 15.20150818
Severity: wishlist

Hi

I finally got around to package libmonitoring-plugin-perl under the
pkg-perl umbrella and it now entered unstable. Could you switch the
use of Nagios::Plugin to Monitoring::Plugin? 

I see some parts waere actually patched to use Nagios::Plugin.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Version: 17.20161211

> > > On Wed, Nov 25, 2015 at 04:44:50PM +0100, Salvatore Bonaccorso wrote:
> > > > I finally got around to package libmonitoring-plugin-perl under the
> > > > pkg-perl umbrella and it now entered unstable. Could you switch the
> > > > use of Nagios::Plugin to Monitoring::Plugin? 
> > > > 
> > > > I see some parts waere actually patched to use Nagios::Plugin.
> > > 
> > > FTR, libnagios-plugin-perl now has an RC Bug filled so that it will
> > > not be included in Stretch. See #819404.
> > 
> > Just a small heads-up. libnagios-plugin-perl will be removed in some
> > days on 25th of may from testing.
> 
> FTR, this has happened now.

We fixed that in the 17.20161211 upload, but failed to mention it in the
changelog.

Thanks
Evgeni--- End Message ---

Bug#811763: marked as done (clipper: FTBFS with GCC 6: narrowing conversion)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 12:03:33 +
with message-id 
and subject line Bug#811763: fixed in clipper 2.1.20130601-2.1
has caused the Debian Bug report #811763,
regarding clipper: FTBFS with GCC 6: narrowing conversion
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.)


-- 
811763: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811763
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: clipper
Version: 2.1.20130601-2
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-narrowing

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -c spacegroup_data.cpp  -fPIC -DPIC -o 
> .libs/libclipper_core_la-spacegroup_data.o
> spacegroup_data.cpp:198:1: error: narrowing conversion of '2610067359u' from 
> 'unsigned int' to 'int' inside { } [-Wnarrowing]
>  };
>  ^
> 
> spacegroup_data.cpp:198:1: error: narrowing conversion of '2962048719u' from 
> 'unsigned int' to 'int' inside { } [-Wnarrowing]
> spacegroup_data.cpp:198:1: error: narrowing conversion of '3813317101u' from 
> 'unsigned int' to 'int' inside { } [-Wnarrowing]
> spacegroup_data.cpp:198:1: error: narrowing conversion of '3877911484u' from 
> 'unsigned int' to 'int' inside { } [-Wnarrowing]
> spacegroup_data.cpp:198:1: error: narrowing conversion of '2287542463u' from 
> 'unsigned int' to 'int' inside { } [-Wnarrowing]
> spacegroup_data.cpp:198:1: error: narrowing conversion of '3917543540u' from 
> 'unsigned int' to 'int' inside { } [-Wnarrowing]
> spacegroup_data.cpp:198:1: error: narrowing conversion of '4258748853u' from 
> 'unsigned int' to 'int' inside { } [-Wnarrowing]
> spacegroup_data.cpp:198:1: error: narrowing conversion of '4067859496u' from 
> 'unsigned int' to 'int' inside { } [-Wnarrowing]
> spacegroup_data.cpp:198:1: error: narrowing conversion of '3444278312u' from 
> 'unsigned int' to 'int' inside { } [-Wnarrowing]
> spacegroup_data.cpp:198:1: error: narrowing conversion of '2614353140u' from 
> 'unsigned int' to 'int' inside { } [-Wnarrowing]
> spacegroup_data.cpp:198:1: error: narrowing conversion of '3651312556u' from 
> 'unsigned int' to 'int' inside { } [-Wnarrowing]
> spacegroup_data.cpp:198:1: error: narrowing conversion of '3484884337u' from 
> 'unsigned int' to 'int' inside { } [-Wnarrowing]
> spacegroup_data.cpp:198:1: error: narrowing conversion of '2324054638u' from 
> 'unsigned int' to 'int' inside { } [-Wnarrowing]
> spacegroup_data.cpp:198:1: error: narrowing conversion of '4148985731u' from 
> 'unsigned int' to 'int' inside { } [-Wnarrowing]
> spacegroup_data.cpp:198:1: error: narrowing conversion of '3933373658u' from 
> 'unsigned int' to 'int' inside { } [-Wnarrowing]
> spacegroup_data.cpp:198:1: error: narrowing conversion of '2979257203u' from 
> 'unsigned int' to 'int' inside { } [-Wnarrowing]
> spacegroup_data.cpp:198:1: error: narrowing conversion of '4231977723u' from 
> 'unsigned int' to 'int' inside { } [-Wnarrowing]
> spacegroup_data.cpp:198:1: error: narrowing conversion of '3591180704u' from 
> 'unsigned int' to 'int' inside { } [-Wnarrowing]
> spacegroup_data.cpp:198:1: error: narrowing conversion of '4157935919u' from 
> 'unsigned int' to 'int' inside { } [-Wnarrowing]
> spacegroup_data.cpp:198:1: error: narrowing conversion of '4223201675u' from 
> 'unsigned int' to 'int' inside { } [-Wnarrowing]
> spacegroup_data.cpp:198:1: error: narrowing conversion of '2748618130u' from 
> 'unsigned int' to 'int' inside { } [-Wnarrowing]
> spacegroup_data.cpp:198:1: error: narrowing conversion of '3102871870u' from 
> 'unsigned int' to 'int' inside { } [-Wnarrowing]
...

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: clipper
Source-Version: 2.1.20130601-2.1

We believe that the bug you reported is fixed in the latest version of
clipper, 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 t

Bug#828342: marked as done (httest: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 14:28:05 +0200
with message-id <20170113122804.jqgqpu77zswvemez@localhost>
and subject line Re: Bug#828342: Re: [Htt-developers] Building with OpenSSL 
1.0.2 is sufficient for stretch
has caused the Debian Bug report #828342,
regarding httest: FTBFS with openssl 1.1.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 ow...@bugs.debian.org
immediately.)


-- 
828342: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828342
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: httest
Version: 2.4.8-1.1
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/httest_2.4.8-1.1_amd64-20160529-1428

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Version: 2.4.18-1

On Wed, Jan 11, 2017 at 09:19:34PM +0100, Eva Ramon wrote:
> I packaged version 2.4.18, it's on mentors, waiting for my sponsor to
> upload it.

2.4.18-1 has been uploaded, closing this bug.

> Regards,
> Eva

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed--- End Message ---

Bug#818413: marked as done (miniupnpd: FTBFS: error: unknown type name 'iptc_handle_t')

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 12:34:12 +
with message-id 
and subject line Bug#818413: fixed in miniupnpd 1.8.20140523-4.1
has caused the Debian Bug report #818413,
regarding miniupnpd: FTBFS: error: unknown type name 'iptc_handle_t'
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.)


-- 
818413: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818413
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: miniupnpd
Version: 1.8.20140523-4
Severity: serious

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> cc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
> -fno-strict-aliasing -fno-common -Wall -Wextra -Wstrict-prototypes 
> -Wdeclaration-after-statement  -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE  
> -c -o netfilter/iptcrdr.o netfilter/iptcrdr.c
> netfilter/iptcrdr.c: In function 'get_nat_redirect_rule':
> netfilter/iptcrdr.c:52:22: error: unknown type name 'iptc_handle_t'
>  #define IPTC_HANDLE  iptc_handle_t
>   ^
> netfilter/iptcrdr.c:305:2: note: in expansion of macro 'IPTC_HANDLE'
>   IPTC_HANDLE h;
>   ^
> netfilter/iptcrdr.c:312:4: warning: assignment makes integer from pointer 
> without a cast [-Wint-conversion]
>   h = iptc_init("nat");
> ^
> netfilter/iptcrdr.c:320:36: warning: passing argument 2 of 'iptc_is_chain' 
> makes pointer from integer without a cast [-Wint-conversion]
>   if(!iptc_is_chain(nat_chain_name, h))
> ^
> In file included from netfilter/iptcrdr.c:18:0:
> /usr/include/libiptc/libiptc.h:28:5: note: expected 'struct xtc_handle * 
> const' but argument is of type 'int'
>  int iptc_is_chain(const char *chain, struct xtc_handle *const handle);
>  ^
> netfilter/iptcrdr.c:331:43: warning: passing argument 2 of 'iptc_first_rule' 
> from incompatible pointer type [-Wincompatible-pointer-types]
>for(e = iptc_first_rule(nat_chain_name, &h);
>^
> In file included from netfilter/iptcrdr.c:18:0:
> /usr/include/libiptc/libiptc.h:41:25: note: expected 'struct xtc_handle *' 
> but argument is of type 'int *'
>  const struct ipt_entry *iptc_first_rule(const char *chain,
>  ^
> netfilter/iptcrdr.c:333:26: warning: passing argument 2 of 'iptc_next_rule' 
> from incompatible pointer type [-Wincompatible-pointer-types]
> e = iptc_next_rule(e, &h))
>   ^
> In file included from netfilter/iptcrdr.c:18:0:
> /usr/include/libiptc/libiptc.h:45:25: note: expected 'struct xtc_handle *' 
> but argument is of type 'int *'
>  const struct ipt_entry *iptc_next_rule(const struct ipt_entry *prev,
>  ^
> In file included from netfilter/iptcrdr.c:13:0:
> netfilter/iptcrdr.c:356:40: error: dereferencing pointer to incomplete type 
> 'const struct ip_nat_multi_range'
>  snprintip(iaddr, iaddrlen, ntohl(mr->range[0].min_ip));
> ^
> netfilter/iptcrdr.c:376:13: warning: passing argument 1 of 'iptc_free' from 
> incompatible pointer type [-Wincompatible-pointer-types]
>iptc_free(&h);
>  ^
> In file included from netfilter/iptcrdr.c:18:0:
> /usr/include/libiptc/libiptc.h:34:6: note: expected 'struct xtc_handle *' but 
> argument is of type 'int *'
>  void iptc_free(struct xtc_handle *h);
>   ^
> netfilter/iptcrdr.c: In function 'get_redirect_rule_by_index':
> netfilter/iptcrdr.c:52:22: error: unknown type name 'iptc_handle_t'
>  #define IPTC_HANDLE  iptc_handle_t
>   ^
> netfilter/iptcrdr.c:403:2: note: in expansion of macro 'IPTC_HANDLE'
>   IPTC_HANDLE h;
>   ^
> netfilter/iptcrdr.c:410:4: warning: assignment makes integer from pointer 
> without a cast [-Wint-conversion]
>   h = iptc_init("nat");
> ^
> netfilter/iptcrdr.c:418:41: warning: passing argument 2 of 'iptc_is_chain' 
> makes pointer from integer without a cast [-Wint-conversion]
>   if(!iptc_is_chain(miniupnpd_nat_chain, h))
>  ^
> In file included from netfilter/iptcrdr.c:18:0:
> /usr/include/libiptc/libiptc.h:28:5: note: expected 'struct xtc_handle * 
> const' but argument is of type 'int'
>  int iptc_is_chain(const char *chain, struct xtc_handle *const handle);
>  ^
> netfilter/iptcrdr.c:429:48: warning: passing argument 2 of 'iptc_first_rule' 
> from incompatible pointer type [-Wincompatible-pointer-types]
>for(e = iptc_first_rule(miniupnpd_nat_chain, &h);
> ^
> In file inclu

Bug#766640: marked as done (miniupnpd: [INTL:nl] Dutch translation of debconf messages)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 12:34:12 +
with message-id 
and subject line Bug#766640: fixed in miniupnpd 1.8.20140523-4.1
has caused the Debian Bug report #766640,
regarding miniupnpd: [INTL:nl] Dutch translation of debconf messages
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.)


-- 
766640: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766640
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---


Package: miniupnpd
Severity: wishlist
Tags: l10n patch 


Dear Maintainer,

==
Please find attached the Dutch translation of miniupnpd 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

===
www.frans-spiesschaert.homenet.org
home.base.be/vt6362833/
# Dutch translation of miniupnpd debconf templates.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the miniupnpd package.
# Frans Spiesschaert , 2014.
#
msgid ""
msgstr ""
"Project-Id-Version: miniupnpd\n"
"Report-Msgid-Bugs-To: miniup...@packages.debian.org\n"
"POT-Creation-Date: 2014-05-28 06:37+\n"
"PO-Revision-Date: 2014-10-14 22:53+0200\n"
"Last-Translator: Frans Spiesschaert \n"
"Language-Team: Dutch \n"
"Language: nl\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"

#. Type: boolean
#. Description
#: ../miniupnpd.templates:2001
msgid "Start the MiniUPnP daemon automatically?"
msgstr "De MiniUPnP-achtergronddienst automatisch starten?"

#. Type: boolean
#. Description
#: ../miniupnpd.templates:2001
msgid ""
"Choose this option if the MiniUPnP daemon should start automatically, now "
"and at boot time."
msgstr ""
"Kies voor deze optie als de MiniUPnP-achtergronddienst automatisch moet "
"starten, nu en bij het opstarten van de computer."

#. Type: string
#. Description
#: ../miniupnpd.templates:3001
msgid "LAN IP address to listen on for UPnP queries:"
msgstr "IP-adres in het LAN waarop geluisterd moet worden naar UPnP-verzoeken:"

#. Type: string
#. Description
#: ../miniupnpd.templates:3001
msgid ""
"The MiniUPnP daemon will listen for requests on the local network. Please "
"enter the IP address it should listen on."
msgstr ""
"De MiniUPnP-achtergronddienst luistert op het lokale netwerk naar aanvragen. "
"Geef het IP-adres op waarop de dienst moet luisteren."

#. Type: string
#. Description
#: ../miniupnpd.templates:4001
msgid "External WAN network interface to open ports on:"
msgstr ""
"Netwerk-interface van het externe WAN waarop poorten geopend moeten worden:"

#. Type: string
#. Description
#: ../miniupnpd.templates:4001
msgid ""
"The MiniUPnP daemon will listen on a specific IP address on the local "
"network, then open ports on the WAN interface. Please enter the name of the "
"WAN network interface on which the MiniUPnP daemon should perform port "
"forwarding."
msgstr ""
"De MiniUPnP-achtergronddienst zal op een specifiek IP-adres van het lokale "
"netwerk luisteren en dan op de WAN-interface poorten openen. Geef de naam op "
"van de WAN-netwerkinterface waarop de MiniUPnP-achtergronddienst port "
"forwarding moet uitvoeren."

#. Type: boolean
#. Description
#: ../miniupnpd.templates:5001
msgid "Enable IPv6 firewall chain?"
msgstr "IPv6 firewall chain (firewallregels) activeren?"

#. Type: boolean
#. Description
#: ../miniupnpd.templates:5001
msgid ""
"Please specify whether the MiniUPnP daemon should run its ip6tables script "
"on startup to initialize the IPv6 firewall chain."
msgstr ""
"Geef aan of de MiniUPnP-achtergronddienst bij de start zijn ip6tables-script "
"moet uitvoeren om de IPv6 firewall chain (firewallregels) te initialiseren"
--- End Message ---
--- Begin Message ---
Source: miniupnpd
Source-Version: 1.8.20140523-4.1

We believe that the bug you reported is fixed in the latest version of
miniupnpd, 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 766...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated miniupnpd package)

(This message 

Bug#747185: marked as done (Conflicting return types of function DejaVu_create)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:43:18 +0100
with message-id <20170113124318.gh16...@an3as.eu>
and subject line Re: Bug#747185: Do the conflicting return types of function 
DejaVu_create exist in new upstream version?
has caused the Debian Bug report #747185,
regarding Conflicting return types of function DejaVu_create
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.)


-- 
747185: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747185
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: exonerate
Version: 2.2.0-6
Usertags: goto-cc

During a rebuild of all packages in a clean sid chroot (and cowbuilder+pbuilder)
the build failed with the following error. Please note that we use our research
compiler tool-chain (using tools from the cbmc package), which permits extended
reporting on type inconsistencies at link time.

error: conflicting function declarations "DejaVu_create"
old definition in module bsam file ../../src/struct/dejavu.h line 42
DejaVu *DejaVu_create(gchar *seq, gint len)
new definition in module dejavu file dejavu.c line 26
DejaVu *DejaVu_create(gchar *seq, gint len)

reason for conflict at nil.symbol_list in types listed below (array/array):

signed int [2048]
signed int [256]

This is with the following code in dejavu.h:

http://sources.debian.net/src/exonerate/2.2.0-6/src/struct/dejavu.h?hl=26,27,28,30,31,32,33,34,35,36#L26

#ifndef ALPHABET_SIZE
#define ALPHABET_SIZE (1 << CHAR_BIT)
#endif /* ALPHABET_SIZE */

typedef struct {
   gchar *seq;
gint  len;
gint *next;
gint  symbol_list[ALPHABET_SIZE];
gint  symbol_list_len;
} DejaVu;

Unfortunately, however, a cruel mix of definitions is used for ALPHABET_SIZE
throughout the codebase of exonerate:

http://codesearch.debian.net/search?q=package%3Aexonerate+ALPHABET_SIZE

Any code relying on the size of the symbol_list array will break as it will
access invalid memory; accesses to the symbol_list_len element are invalid as
its offset will be wrong.

Best,
Michael



pgp3dIhIFo2Rn.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Hi,

issue is done in my opinion.  Please reopen if not.

Kind regards

  Andreas.

On Wed, Dec 14, 2016 at 07:28:05AM +0100, Andreas Tille wrote:
> Hi Michael,
> 
> I'm currently checking older bugs and stumbled upon this one.  I
> currently can not find the said cruel mix of definitions is used for
> ALPHABET_SIZE in the code base of 2.4.0.  Could you please recheck
> and confirm whether this bug can be closed or explain in more detail
> in how far different definitions are used?
> 
> Kind regards
> 
>   Andreas.
> 
> -- 
> http://fam-tille.de
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
> 

-- 
http://fam-tille.de--- End Message ---

Bug#817306: marked as done (sapphire: Removal of dh_desktop)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 12:48:52 +
with message-id 
and subject line Bug#817306: fixed in sapphire 0.15.8-9.1
has caused the Debian Bug report #817306,
regarding sapphire: Removal of dh_desktop
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.)


-- 
817306: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817306
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sapphire
Severity: important
Tags: dh_desktop-removal

Hi,

The package sapphire is still using dh_desktop according to lintian.
This command was obsoleted in 2009 and has since then done nothing but
print a warning.

 * Please remove all remaining calls to dh_desktop at your
   earliest convenience.

 * I will remove dh_undocumented from debhelper in the first upload
   after 1st of April.


If your package is *also* affected by any of the following debhelper
related deprecations, please consider fixing them at the same time:

 * debhelper compat 4 is deprecated and is expected to be removed
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * If your package does *not* have a debian/compat, please add one with
   the correct compat level.
   - The compat file will be required by 15th of April.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: sapphire
Source-Version: 0.15.8-9.1

We believe that the bug you reported is fixed in the latest version of
sapphire, 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 817...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated sapphire 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: SHA512

Format: 1.8
Date: Fri, 13 Jan 2017 14:31:12 +0200
Source: sapphire
Binary: sapphire
Architecture: source
Version: 0.15.8-9.1
Distribution: unstable
Urgency: medium
Maintainer: Chris Boyle 
Changed-By: Adrian Bunk 
Description:
 sapphire   - A minimal but configurable X11R6 window manager
Closes: 817306
Changes:
 sapphire (0.15.8-9.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Remove the obsolete dh_desktop call. (Closes: #817306)
Checksums-Sha1:
 da744296ddcdf993c9ae198e258e1164f2340b89 1757 sapphire_0.15.8-9.1.dsc
 2c57801067eca539b1eb6ae2ae4f678ee4c986e6 29233 sapphire_0.15.8-9.1.diff.gz
Checksums-Sha256:
 a8e18aac2f9f9fa0a82115655f142dc2bbe67428b4e116f24a6a2ef590a19721 1757 
sapphire_0.15.8-9.1.dsc
 cfedfd731c4aecc52baa6f9bb68d87f4fdb71c72ddaec71e44f1279bfc5b2a60 29233 
sapphire_0.15.8-9.1.diff.gz
Files:
 fca13199efd113ccf174e5a878473f6a 1757 x11 optional sapphire_0.15.8-9.1.dsc
 4bdb2256f32bc6ac119f1619f6d00bf2 29233 x11 optional sapphire_0.15.8-9.1.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlh4yV0ACgkQiNJCh6LY
mLEWcRAAz2GPbwM/oAWlJ68QKtko4E8OGSoRekJwAV/hCemY8CQtp/dAlDsDMe1+
8AgG9LPR8/cdjuBgKXQfVQqmM/9q5fYMXzIW022Upl0P4KlUWn0z12lph85tdrD0
YTbCDew0sNaC3jJG7vufiYK2LiAGyAAIX8shQU+7isCpR3fVBsFBQWliTwc2CzTH
psprzPei+FtnPIC2JFsdK3jKC3NfHkIVObPNyKr+IDHRLzIoWEMgkYeTipmls5sq
BtAJYQHC7wLPhF/DowDTDC0IuS8qj/7kGtl7O0mCOF/o3g6fiDxl4HTFIxVajcVL
KenqiF4J4N2WxqUUxpwOpu0pR98eLZUATMWs3tEzS1WTHAN4NRT30J+l15Hwm01Z
EWeu1qiGpJSJ2LGEz4fJFXweXoLvv52gWaC/GcK5IZVTdH3DOtyntGF5Q5bVoM00
gslam18rbLSZ1sv4BLvhMmCGcsyDDwQ5EHVbyc+b9j+aZsQt+8TJ3oCOcGpXyvML
Ltfzmyih8FZnO8JBWkn6NbB7CU/sYkhA0uFmVzDeDjqHwqM9oSltJJ9PuSbzR6yR
NbpcEJvmX2RSXTpOlzIcD+hEXINvYcAEwQfrrhKAnbtci9Qozyqr/NCwe+BdJfPR
VCMG+Ghc/H3AdVjQcE+jGwxH8njZQIVLtIR25hBXL0NQ/WsY9L8=
=Wg97
-END PGP SIGNATURE End Message ---

Bug#749639: marked as done (ampache: New upstream release)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:01:29 +
with message-id 
and subject line Bug#850838: Removed package(s) from unstable
has caused the Debian Bug report #749639,
regarding ampache: New upstream release
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.)


-- 
749639: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749639
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ampache
Severity: wishlist

Ampache 3.7.0 is released, and notably includes Subsonic API support.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Version: 3.6-rzb2752+dfsg-9+rm

Dear submitter,

as the package ampache 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/850838

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)--- End Message ---

Bug#744651: marked as done (python-edbus: run dh-autoreconf to update config.{sub,guess} and {libtool,aclocal}.m4)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:00:57 +
with message-id 
and subject line Bug#850844: Removed package(s) from unstable
has caused the Debian Bug report #744651,
regarding python-edbus: run dh-autoreconf to update config.{sub,guess} and 
{libtool,aclocal}.m4
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.)


-- 
744651: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744651
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-edbus
Version: 0.7.3-1
User: debian-de...@lists.debian.org
Usertags: autoreconf

The package fails to build on ppc64el (powerpc64le-linux-gnu), because
the config.{guess,sub} files are out of date, and are not updated during
the build.  If possible, please do not update these files directly,
but build-depend on autotools-dev instead, and use the tools provided
by autotools-dev to update these files.

  - For dh, call dh --with autoreconf.

  - For cdbs based build systems, include
/usr/share/cdbs/1/rules/autoreconf.mk

  - For other rules files, call dh_autoreconf before calling
configure (in the build or configure target), and call
dh_autoreconf_clean before dh_clean in the clean target.

For combining autoreconf and autotools_dev, see bug #698765.

After the build on any architecture, and before a clean, a grep for
powerpc64le in the configure, aclocal.m4 and/or libtool.m4 file(s)
should print some lines. It is not enough to just update the
config.guess and config.sub files.

The full build log can be found at:
http://people.debian.org/~doko/logs/ppc64el-20140414/buildlog_ubuntu-trusty-ppc64el.python-edbus_0.7.3-1_FAILEDTOBUILD.txt
The last lines of the build log are at the end of this report.

Please note that these builds were done in an Ubuntu development,
environment there may be a few false positives in these bug reports.

See https://wiki.debian.org/qa.debian.org/FTBFS for a guide how to
address these.

[...]
fi ; \
done ; \
fi
if test -e /usr/share/misc/config.sub ; then \
for i in ./config.sub ; do \
if ! test -e $i.cdbs-orig ; then \
mv $i $i.cdbs-orig ; \
cp --remove-destination 
/usr/share/misc/config.sub $i ; \
fi ; \
done ; \
fi
DEB_MAKE_CHECK_TARGET unset, not running checks
/usr/bin/make  -C .  install DESTDIR=/build/buildd/python-edbus-0.7.3/debian/tmp
make[1]: Entering directory `/build/buildd/python-edbus-0.7.3'
make[2]: Entering directory `/build/buildd/python-edbus-0.7.3'
test -z "/usr/lib/python2.7/dist-packages" || /bin/mkdir -p 
"/build/buildd/python-edbus-0.7.3/debian/tmp/usr/lib/python2.7/dist-packages"
 /bin/bash ./libtool   --mode=install /usr/bin/install -c   e_dbus.la 
'/build/buildd/python-edbus-0.7.3/debian/tmp/usr/lib/python2.7/dist-packages'
libtool: install: /usr/bin/install -c .libs/e_dbus.lai 
/build/buildd/python-edbus-0.7.3/debian/tmp/usr/lib/python2.7/dist-packages/e_dbus.la
libtool: install: /usr/bin/install -c .libs/e_dbus.a 
/build/buildd/python-edbus-0.7.3/debian/tmp/usr/lib/python2.7/dist-packages/e_dbus.a
libtool: install: chmod 644 
/build/buildd/python-edbus-0.7.3/debian/tmp/usr/lib/python2.7/dist-packages/e_dbus.a
libtool: install: ranlib 
/build/buildd/python-edbus-0.7.3/debian/tmp/usr/lib/python2.7/dist-packages/e_dbus.a
libtool: install: warning: remember to run `libtool --finish 
/usr/lib/python2.7/dist-packages'
test -z "/usr/lib/pkgconfig" || /bin/mkdir -p 
"/build/buildd/python-edbus-0.7.3/debian/tmp/usr/lib/pkgconfig"
 /usr/bin/install -c -m 644 python-edbus.pc 
'/build/buildd/python-edbus-0.7.3/debian/tmp/usr/lib/pkgconfig'
make[2]: Leaving directory `/build/buildd/python-edbus-0.7.3'
make[1]: Leaving directory `/build/buildd/python-edbus-0.7.3'
touch debian/stamp-makefile-install
Adding cdbs dependencies to debian/python-edbus.substvars
dh_installdirs -ppython-edbus 
dh_installdocs -ppython-edbus ./README ./AUTHORS 
dh_installexamples -ppython-edbus 
dh_installman -ppython-edbus  
dh_installinfo -ppython-edbus  
dh_installmenu -ppython-edbus 
dh_installcron -ppython-edbus 
dh_installinit -ppython-edbus  
dh_installdebconf -ppython-edbus 
dh_installemacsen -ppython-edbus   
dh_installcatalogs -ppython-edbus 
dh_installpam -ppython-edbus 
dh_installlogrotate -ppython-edbus 
dh_installlogcheck -ppython-edbus 
dh_installchangelogs -ppython-edbus  
dh_installudev -ppython-edbus 
dh_lintian -ppython-edbus 
dh_bugfiles -ppython-edbus 
dh_install -ppython-edbus  
dh_install: python-edbu

Bug#851248: marked as done (RM: ruby-reek -- ROM; Request Of Maintainer.)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 12:59:29 +
with message-id 
and subject line Bug#851248: Removed package(s) from unstable
has caused the Debian Bug report #851248,
regarding RM: ruby-reek -- ROM; Request Of Maintainer.
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.)


-- 
851248: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851248
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

 ruby-reek |3.8.2-2 | source, all

--- Reason ---
ROM; Request Of Maintainer.
--

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 851...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/851248

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)--- End Message ---

Bug#837505: marked as done (php-gettext was renamed to php-php-gettext)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:01:29 +
with message-id 
and subject line Bug#850838: Removed package(s) from unstable
has caused the Debian Bug report #837505,
regarding php-gettext was renamed to php-php-gettext
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.)


-- 
837505: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837505
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ampache-common
Version: 3.6-rzb2752+dfsg-9
Severity: normal


Hi Maintainer,

php-gettext was renamed to php-php-gettext, please fix it.


Cheers,

-- 
Marcelo Jorge Vieira
xmpp:me...@jabber-br.org
http://metaldot.alucinados.com
http://movimente.me

signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Version: 3.6-rzb2752+dfsg-9+rm

Dear submitter,

as the package ampache 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/850838

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)--- End Message ---

Bug#824907: marked as done (ruby-reek: Fails to load library from main script)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 12:59:34 +
with message-id 
and subject line Bug#851248: Removed package(s) from unstable
has caused the Debian Bug report #824907,
regarding ruby-reek: Fails to load library from main script
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.)


-- 
824907: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824907
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-reek
Version: 3.8.2-2
Severity: grave
Justification: renders package unusable

Hi,

When I run reek from the ruby-reek package, I get the following error:

  /usr/bin/reek:9:in `require_relative': cannot load such file -- /usr/lib/reek 
(LoadError)
  from /usr/bin/reek:9:in `'

The reek script assumes the standard gem directory layout, so it gets confused
if lib/ is not a sibling of bin/.

(I'm one of Reek's core developers, by the way.)

Regards,
Matijs

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IE.utf8, LC_CTYPE=en_IE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages ruby-reek depends on:
ii  ruby1:2.3.0+4
ii  ruby-parser 3.6.6-1
ii  ruby-rainbow2.0.0-1
ii  ruby2.3 [ruby-interpreter]  2.3.1-1

ruby-reek recommends no packages.

ruby-reek suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 3.8.2-2+rm

Dear submitter,

as the package ruby-reek 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/851248

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)--- End Message ---

Bug#850844: marked as done (RM: python-edbus -- RoQA; obsolete, no reverse dependencies)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:00:52 +
with message-id 
and subject line Bug#850844: Removed package(s) from unstable
has caused the Debian Bug report #850844,
regarding RM: python-edbus -- RoQA; obsolete, no reverse dependencies
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.)


-- 
850844: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850844
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-edbus
Version: 0.5.0+r49577-1
Severity: wishlist
User: debian...@lists.debian.org
Usertags: proposed-removal

python-edbus appears to be dead upstream: it is no longer available
from , and its
git repository

was last touched in 2012.

In Debian, the last maintainer upload was 2011 and there has been no
sign of activity since my NMU in 2015. dak reports that nothing depends
on it:

> smcv@coccia ~ % dak rm -R -n python-edbus
> Will remove the following packages from unstable:
> 
> python-edbus | 0.5.0+r49577-1.2 | source, amd64, arm64, armel, armhf, 
> hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, 
> powerpc, ppc64el, s390x
[...]
> Checking reverse dependencies...
> No dependency problem found.

I'm aware that I've probably left it too late to remove this package from
Debian 9, but I don't think it should be in Debian 10.

If you agree, please reassign this bug to the archive administrators
by sending these commands to cont...@bugs.debian.org, replacing nn
with the bug number:

severity nn normal
reassign nn ftp.debian.org
retitle nn RM: python-edbus -- RoQA; obsolete, no reverse dependencies
thanks

Conversely, if you think this package should remain in Debian, please
close this bug.

Thanks,
S
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

python-edbus | 0.5.0+r49577-1.2 | source, amd64, arm64, armel, armhf, 
hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, 
powerpc, ppc64el, s390x

--- Reason ---
RoQA; obsolete, no reverse dependencies
--

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 850...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/850844

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)--- End Message ---

Bug#850838: marked as done (RM: ampache -- RoQA; orphaned, needs periodic rebuilds, 2 years behind upstream, RC #801116)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:01:22 +
with message-id 
and subject line Bug#850838: Removed package(s) from unstable
has caused the Debian Bug report #850838,
regarding RM: ampache -- RoQA; orphaned, needs periodic rebuilds, 2 years 
behind upstream, RC #801116
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.)


-- 
850838: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850838
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: David Prévot , Andreas Beckmann 


ampache was accidentally allowed back into testing when the BTS
temporarily forgot about RC bugs. I was about to ask for it to be
removed from testing again, but actually, I think removal from unstable
would be a better resolution. It can still get back into the archive if
someone maintains it (orphaned snce 2014, #766449).

ampache generates lockstep dependencies on some of the libraries it uses,
and needs periodic rebuilds (which have to be sourceful because it is
Architecture: all) to update those lockstep dependencies; if that is
not done, it can block transitions. I assume the intention was for the
maintainer to check for compatibility before re-uploading, but this seems
unlikely to happen in QA uploads.

It does have a popcon of 117 installations, which is more than I'd usually
like for a removal request; but the Debian package is 2.5 years behind
upstream and has nobody maintaining it, so having it packaged doesn't seem
like a net positive for Debian users.

In October 2015, David Prévot cloned a RC bug titled "Unsuitable for
stable without proper maintenance" which has not had any response
since. An extract from that bug:

David Prévot wrote:
> On Fri, Sep 18, 2015 at 01:08:53PM +0200, Andreas Beckmann wrote:
> > I don't mind doing rebuild-only QA uploads (since arch:all cannot be
> > binNMUed), but I don't care about (or even use) ampache at all.
>
> Then please don’t: keeping an outdated and unmaintained version of some
> PHP scripts without anyone caring if it actually works or is secure is
> not a service to our users.
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

   ampache | 3.6-rzb2752+dfsg-9 | source, all
ampache-common | 3.6-rzb2752+dfsg-9 | all

--- Reason ---
RoQA; orphaned, needs periodic rebuilds, 2 years behind upstream, RC #801116
--

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 850...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/850838

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)--- End Message ---

Bug#850944: marked as done (RM: google-sitemapgen -- ROM; no longer required)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:00:19 +
with message-id 
and subject line Bug#850944: Removed package(s) from unstable
has caused the Debian Bug report #850944,
regarding RM: google-sitemapgen -- ROM; no longer required
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.)


-- 
850944: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850944
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal

Given that the landscape of the internet has changed significantly
over the past five years, this tool is not really that relevant
anymore. I propose that this be removed.

Thanks.

Kumar
-- 
Kumar Appaiah
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

google-sitemapgen |  1.5-3 | source, all

--- Reason ---
ROM; no longer required
--

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 850...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/850944

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)--- End Message ---

Bug#851106: marked as done (RM: golang-github-geertjohan-go.rice [s390x] -- RoQA; golang is no longer available on s390x)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 12:59:53 +
with message-id 
and subject line Bug#851106: Removed package(s) from unstable
has caused the Debian Bug report #851106,
regarding RM: golang-github-geertjohan-go.rice [s390x] -- RoQA; golang is no 
longer available on s390x
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.)


-- 
851106: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851106
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal

another leftover golang binary package on s390x ...


Andreas
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

golang-rice | 0.0~git20160123.0.0f3f5fd-1 | s390x

--- Reason ---
RoQA; golang is no longer available on s390x
--

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.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 851...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/851106

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)--- End Message ---

Bug#808417: marked as done (google-sitemapgen: Sitemap Index wrong tags (please apply patch))

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:00:25 +
with message-id 
and subject line Bug#850944: Removed package(s) from unstable
has caused the Debian Bug report #808417,
regarding google-sitemapgen: Sitemap Index wrong tags (please apply patch)
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.)


-- 
808417: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808417
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: google-sitemapgen
Version: 1.5-3
Severity: important

Dear Maintainer,

   * What led up to the situation?

The latest version of google-sitemapgen produces a sitemap index 
(for very large sites) starting with  rather than 

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Install a new version

   * What was the outcome of this action?

Google no longer understands the site map and ignores it.
As this render the package broken and this is its sole functionality
I'm marking it as important, but this will only affect sites with
more than 50,000 pages.

   * What outcome did you expect instead?

Working as before. There is a patch in SourceForge:

https://sourceforge.net/p/goog-sitemapgen/bugs/12/

that patch is somewhat applied (because the double _ is not
an issue), but the SITEMAP -> SITEINDEX bit is necessary


-- System Information:
Debian Release: 8.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages google-sitemapgen depends on:
ii  python  2.7.9-1

google-sitemapgen recommends no packages.

google-sitemapgen suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.5-3+rm

Dear submitter,

as the package google-sitemapgen 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/850944

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)--- End Message ---

Bug#801116: marked as done (Unsuitable for stable without proper maintenance)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:01:29 +
with message-id 
and subject line Bug#850838: Removed package(s) from unstable
has caused the Debian Bug report #801116,
regarding Unsuitable for stable without proper maintenance
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.)


-- 
801116: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801116
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ampache-common
Version: 3.6-rzb2752+dfsg-5
Severity: serious

The version constraint for php-getid3 (<< 1.9.8.0~) is too strict for no
good reason. Since 1.9.9+dfsg-2 is in Sid, the package is not
installable anymore. Maybe dh_linktree is not as useful as it looks.

Regards

David


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 3.6-rzb2752+dfsg-9+rm

Dear submitter,

as the package ampache 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/850838

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)--- End Message ---

Bug#766449: marked as done (O: ampache -- web-based audio file management system)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:01:29 +
with message-id 
and subject line Bug#850838: Removed package(s) from unstable
has caused the Debian Bug report #766449,
regarding O: ampache -- web-based audio file management system
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.)


-- 
766449: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766449
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: normal

I'm orphaning the package ampache, because the current e-mail address of
the maintainer bounces. This fixes RC bug #765913.

Regards,
Tobias



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 3.6-rzb2752+dfsg-9+rm

Dear submitter,

as the package ampache 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/850838

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)--- End Message ---

Bug#848466: marked as done (ampache-common: Should Suggest the metapackage default-mysql-*)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:01:29 +
with message-id 
and subject line Bug#850838: Removed package(s) from unstable
has caused the Debian Bug report #848466,
regarding ampache-common: Should Suggest the metapackage default-mysql-*
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.)


-- 
848466: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848466
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ampache-common
Severity: normal

User: pkg-mysql-ma...@lists.alioth.debian.org Usertags: default-mysql
default-mysql-depends-recommends 

Hi! 

This package depends (or recommends) direclty on Oracle MySQL. It
should instead depend on the default-mysql-* metapackages, and end up
being installed with the MySQL implementation Debian has chosen to
use, currently MariaDB instead of Oracle MySQL. 

Announcement of the new default-mysql-* metapackages:
https://lists.debian.org/debian-devel-announce/2016/09/msg0.html 

Wiki: https://wiki.debian.org/Teams/MySQL/default-mysql-server 

MBF: https://lists.debian.org/debian-devel/2016/11/msg00832.html 

Please update the depencies accordingly. In most cases the required
change follows this pattern: 

* BEFORE: Depends: mysql-server | virtual-mysql-server 

* AFTER: Depends: default-mysql-server | virtual-mysql-server 

As this is a mass bug filing, the exact solution above might not
apply to directly. For example, if your package depends on some other
Oracle MySQL package, like mysql-client, then use to
default-mysql-client. 

Thanks, 

Otto 
--- End Message ---
--- Begin Message ---
Version: 3.6-rzb2752+dfsg-9+rm

Dear submitter,

as the package ampache 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/850838

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)--- End Message ---

Bug#832536: marked as done (puppet-master - no upgrade path from 3.7)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:00:10 +
with message-id 
and subject line Bug#832536: fixed in puppet 4.8.1-2
has caused the Debian Bug report #832536,
regarding puppet-master - no upgrade path from 3.7
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.)


-- 
832536: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832536
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: puppet-master
Version: 4.5.2-1
Severity: important

Puppet as shipped in Debian Stretch does not provide any backward
compatibility with older agents.  As there is also no forward
compatibility, no upgrade path exists.

According to
https://docs.puppet.com/puppetserver/latest/compatibility_with_puppet_agent.html
there exists backward compatibility support in Puppet Server

Regards,
Bastian

-- 
It would seem that evil retreats when forcibly confronted.
-- Yarnek of Excalbia, "The Savage Curtain", stardate 5906.5
--- End Message ---
--- Begin Message ---
Source: puppet
Source-Version: 4.8.1-2

We believe that the bug you reported is fixed in the latest version of
puppet, 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 832...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Apollon Oikonomopoulos  (supplier of updated puppet 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: Wed, 11 Jan 2017 20:22:17 +0200
Source: puppet
Binary: puppet puppet-agent puppet-master puppetmaster puppet-master-passenger 
puppetmaster-passenger puppet-common
Architecture: source all
Version: 4.8.1-2
Distribution: unstable
Urgency: medium
Maintainer: Puppet Package Maintainers 

Changed-By: Apollon Oikonomopoulos 
Description:
 puppet - configuration management system
 puppet-agent - configuration management system, agent
 puppet-common - transitional dummy package
 puppet-master - configuration management system, master service
 puppet-master-passenger - configuration management system, scalable master 
service
 puppetmaster - configuration management system, master service - transitional 
pa
 puppetmaster-passenger - configuration management system, scalable master 
service - transi
Closes: 832536
Changes:
 puppet (4.8.1-2) unstable; urgency=medium
 .
   * Add transitional packages for puppetmaster and puppetmaster-passenger.
   * Add Puppet 3 client compatibility when the master is run under a
 rack server (Closes: #832536). Input by James Cowgill and Christos
 Trochalakis, thanks!
   * Add DEP-8 tests for Puppet 3 client compatibility using serverspec.
   * Add a NEWS entry documenting Puppet 3 client compatibility.
Checksums-Sha1:
 150ebd334e576879e4773c7269e720bb43cf4946 2509 puppet_4.8.1-2.dsc
 b7779325479e9c40e627e71f0023f1dafb8df4be 30996 puppet_4.8.1-2.debian.tar.xz
 cf9dc4615c4a5168969a18b3c9de9dee06543388 22956 puppet-agent_4.8.1-2_all.deb
 f472c10cdeeca00d4a93055f9678288167655ff8 21732 puppet-common_4.8.1-2_all.deb
 31f8da971a3711ea1ee8857d5e299c8e0b190eff 25524 
puppet-master-passenger_4.8.1-2_all.deb
 cf0a39a3ba9257cd5ff0e8a5473577cc5b7f5962 23444 puppet-master_4.8.1-2_all.deb
 c572ad79efbcc8ef2d86b80e7db9adbcaf538c52 1123884 puppet_4.8.1-2_all.deb
 3b0c764ded356965250db4546158e8c180225142 21272 
puppetmaster-passenger_4.8.1-2_all.deb
 eb2ea9bdb0fd30051c1d67262224f0de3e234adc 21250 puppetmaster_4.8.1-2_all.deb
Checksums-Sha256:
 01c28a8bdff2674a965f25d64f608e56e33e9f81169de8f6fc416490d84613d5 2509 
puppet_4.8.1-2.dsc
 d56e3151d36c57619a0bc489b84c9dcfe8d644dd561483603437661416165c46 30996 
puppet_4.8.1-2.debian.tar.xz
 f1fc07c296653aecff17a5921d0d44726c429605b44c1d3ce25c2ccd2b137660 22956 
puppet-agent_4.8.1-2_all.deb
 b5dca30357fdbc628556287771624e8ce4d6c8d111285c35729e6f13697404dc 21732 
puppet-common_4.8.1-2_all.deb
 13fa969aa8243bdca4584e2b06484a754429d569b56940b4c7952e1d6025f549 25524 
puppet-master-passenger_4.8.1-2_all.deb
 ffb50abbae3515611346aad76fe275fbb9285f1a9d295685eca3ff8f59039482 23444 
puppet-master_4.8.1-2_all.deb
 82e17f86d208eab6a858cbae9a90a6082f52a1e130af7060e31d728bef83d3f4 1123884 
puppet_4.8.1-2_all.deb
 1a140653334c7dfc18a1fe65e7fc4f4c3183526a9e44af32ad085deb02dde630 21272 
puppet

Bug#848465: marked as done (ampache: Should Suggest the metapackage default-mysql-*)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:01:29 +
with message-id 
and subject line Bug#850838: Removed package(s) from unstable
has caused the Debian Bug report #848465,
regarding ampache: Should Suggest the metapackage default-mysql-*
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.)


-- 
848465: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848465
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ampache
Severity: normal

User: pkg-mysql-ma...@lists.alioth.debian.org Usertags: default-mysql
default-mysql-depends-recommends 

Hi! 

This package depends (or recommends) direclty on Oracle MySQL. It
should instead depend on the default-mysql-* metapackages, and end up
being installed with the MySQL implementation Debian has chosen to
use, currently MariaDB instead of Oracle MySQL. 

Announcement of the new default-mysql-* metapackages:
https://lists.debian.org/debian-devel-announce/2016/09/msg0.html 

Wiki: https://wiki.debian.org/Teams/MySQL/default-mysql-server 

MBF: https://lists.debian.org/debian-devel/2016/11/msg00832.html 

Please update the depencies accordingly. In most cases the required
change follows this pattern: 

* BEFORE: Depends: mysql-server | virtual-mysql-server 

* AFTER: Depends: default-mysql-server | virtual-mysql-server 

As this is a mass bug filing, the exact solution above might not
apply to directly. For example, if your package depends on some other
Oracle MySQL package, like mysql-client, then use to
default-mysql-client. 

Thanks, 

Otto 
--- End Message ---
--- Begin Message ---
Version: 3.6-rzb2752+dfsg-9+rm

Dear submitter,

as the package ampache 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/850838

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)--- End Message ---

Bug#821701: marked as done (src:php-json: PHP 7.0 Transition)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:04:18 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #821701,
regarding src:php-json: 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.)


-- 
821701: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821701
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:php-json
Version: 1:7.0+35
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 php-json package currently build-depends on php5 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: php-json -- 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

iQJ8BAEBCgBmBQJXFUtvXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHm0YP/16u0AmPCAQ6ShhnZVsjy6UO
Yox0sM/MvIsPQr5bath8RLlHK4E9i3356a++k4g+1YTc3mG7aROJAkKu9aWip1Xc
9uDMWjjeHofK6/gyadxtaNG5InQCx/GAeiyJm2NR7iTmlC09orWsWsJfl2/qCrpA
ybwy1bIqmUi0vsVn6j1Y4/PwSLNK7m5HytNXGm85btfVS2GBZIcv7vI6zWI3AnZe
lyoGExPxqQ8KLhng7kh93xxZFWQWSFo2vYWiKmrVBQXTXZvnjFqWsPreE+0S6cgG
DjShP47UF7N3rqI4il//EZ2xa66ov4OOIx4zb

Bug#801962: marked as done (Invalid input fails to result in error return)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:04:18 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #801962,
regarding Invalid input fails to result in error return
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.)


-- 
801962: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801962
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-json
Version: 1.3.7-1
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu wily

Hi,

As described by Ice downstream:

"On a fundamental level, the provided replacement doesn’t match PHP
Documentation about behaviour. Json_decode() is described to return NULL
on invalid UTF-8 sequence, and set an error message of JSON_ERROR_UTF8.
Current behaviour with json-c is returns JSON_OK, and returns an invalid
string that cannot be used in any PHP Intl function, database, without
throwing exceptions or generating invalid data that can’t be easily
fixed in the database. (Or, it throws more exceptions)"

This is apparently now fixed upstream in 1.3.9
(https://github.com/remicollet/pecl-json-c/issues/9), so please can you
pull that in? I'd like this to sync to Ubuntu fairly soon so that the
behaviour change is implemented early in the run up to our next LTS
release.

I'm happy to help if you want me to push to git somewhere or something.

Downstream bug:

https://bugs.launchpad.net/ubuntu/+source/php-json/+bug/1287726

Thanks,

Robie


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 1.3.9-1+rm

Dear submitter,

as the package php-json 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/841781

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)--- End Message ---

Bug#440775: marked as done (Crash when changing gettext (*.mo) file)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #440775,
regarding Crash when changing gettext (*.mo) file
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.)


-- 
440775: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=440775
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-cgi
Version: 5.2.3-1+b2
Severity: normal

Hi

I use gettext for localisation of my PHP application. Whenever I change
templates/translation and then regenerate .mo files, PHP instances start
to crash. Most likely they do not detect file change and still treate it
as old one. Restarting PHP solves this.

-- 
Michal Čihař | http://cihar.com | http://blog.cihar.com

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.22-1-vserver-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages php5-cgi depends on:
ii  libbz2-1.0  1.0.3-7  high-quality block-sorting file co
ii  libc6   2.6.1-2  GNU C Library: Shared libraries
ii  libcomerr2  1.40.2-1 common error description library
ii  libdb4.44.4.20-9 Berkeley v4.4 Database Libraries [
ii  libkrb531.6.dfsg.1-6 MIT Kerberos runtime libraries
ii  libmagic1   4.21-3   File type determination library us
ii  libpcre37.3-1Perl 5 Compatible Regular Expressi
ii  libssl0.9.8 0.9.8e-8 SSL shared libraries
ii  libxml2 2.6.30.dfsg-2GNOME XML library
ii  mime-support3.39-1   MIME files 'mime.types' & 'mailcap
ii  php5-common 5.2.3-1+b2   Common files for packages built fr
ii  ucf 3.001Update Configuration File: preserv
ii  zlib1g  1:1.2.3.3.dfsg-5 compression library - runtime

php5-cgi recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm

Dear submitter,

as the package php5 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/841781

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)--- End Message ---

Bug#413713: marked as done (php5 -ws, -sw: first argument ignored)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #413713,
regarding php5 -ws, -sw: first argument ignored
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.)


-- 
413713: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=413713
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5
Version: 5.2.0-8
Severity: minor

first argument ignored:
$ php -sw LocalSettings.php|wc
  6 2463422
$ php -ws LocalSettings.php|wc
  31020   25998
$ php -s LocalSettings.php|wc
  31020   25998
$ php -w LocalSettings.php|wc
  6 2463422

P.S., on the man page,
   --stripped
   -w Display source with stripped comments and whitespace
Well OK, but wish the newlines weren't attacked if there is something
else left on the line.

   --syntax-highlight
   -s Display colour syntax highlighted source

It does not "display" source, it merely outputs a HTML BODY (which
doesn't pass validate(1) very well.)

--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm

Dear submitter,

as the package php5 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/841781

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)--- End Message ---

Bug#841781: marked as done (RM: php-json, php5 -- ROM; obsoleted by src:php7.0)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:04:12 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #841781,
regarding RM: php-json, php5 -- ROM; obsoleted by src:php7.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 ow...@bugs.debian.org
immediately.)


-- 
841781: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841781
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear ftp-masters,

please remove php5 and php-json from unstable.  Those packages have
been replaced by src:php7.0 and transition has been completed.

The security team acked the removal as the php5 injessie can and will
be updated directly, and php5 from  unstable doesn't provide much
testing nowadays anyway.

Most of Depends and Build-Depends either have alternative dependencies
(php5 | php) or are broken anyway and they should be cleaned up, but
that's not up to me, as they are neither maintained by me nor by
Debian PHP Group.

Cheers,
Ondrej
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJYDLlzXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsH9LEQANBUniLBCpbfmDS06/GeFzsP
1/PKXr/1qjmAt5K4JvQQw4KpAsSjRSaCUu1QX3E2v9jZpCKezRB9Gglcl+Jy3JZI
NfRfmJK1VmhfWD2DI28tZKppcdMhImqRevfdGLgkN/a0SbdQ7X47OMZlE4e9tCZw
7tiA+5KG+ra4e2/s5Muz6kPk4eKSWzZZXMEyPCOmDOuzFWNaSoOh/brlW123uj//
BoCATBSr5UAu3OSv6PraynFnwJFomEUlHvisTJFdnFRL518ByD3mdiGA+Lrlw0MW
3P6N5TV6Em9wIidYQyh7La+6HvUYuiastwqrV9giYmKqTD7CfNkIdwkDPD0PsmU0
PRGF55ilnSK36UWR7tR6s3yMRYnzPiP3Lv+NrxPqrH1iTNGHJnrD4I8/wo5IZVnE
21LUt7qhA0Yks5JJZU1dr4t0VFNTojqgYczDG0IaTCPDbfHVpqc1V0qqiy7DB8Hw
jpUXlAOGEmMLrmZDrASWKl13jBCeHC9Xu5tO67deELwTUL9/96L9KK3q0/QMn4E0
JCT6VDxzvPK1jbjndNw58BxY0CVTjX9guFx1CvevHmWaU7YJtSODecgUdoQUXg+9
kVywmXQtYKxbCMuzTbX5kxSx/Dw7v73+BFldn1TrOMLFfA/i1Wi/TYKnpBM+7Cnl
XPKELp6W6vCucLuRS7Fy
=rJz0
-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:

  php-json |1.3.9-1 | source
 php5-json |1.3.9-1 | amd64, arm64, armel, armhf, hurd-i386, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x

--- Reason ---
ROM; obsoleted by src:php7.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 841...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/841781

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)--- End Message ---

Bug#850879: marked as done (datatables.js: Build uses static filenames in /tmp, does not catch errors)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:03:45 +
with message-id 
and subject line Bug#850879: fixed in datatables.js 1.10.13+dfsg-2
has caused the Debian Bug report #850879,
regarding datatables.js: Build uses static filenames in /tmp, does not catch 
errors
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.)


-- 
850879: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850879
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: datatables.js
Version: 1.10.13+dfsg-1
Severity: normal
Tags: patch upstream

Dear Maintainer,

the build process for the datatables.js package uses static filenames
in /tmp/, among them /tmp/closure_error.log which also does not get
removed.

This is at least bad style. Although symlinks attacks on build systems
are not a very likely scenario, this still becomes a problem if
the files already exist but belong to another user - something that
happens if several users on the same host try to build that package:

| JS compressing dataTables.bootstrap4.js
| cp: cannot create regular file '/tmp/dataTables.bootstrap4.js': Permission 
denied
| Can't remove /tmp/dataTables.bootstrap4.js: Operation not permitted, skipping 
file.
| rm: cannot remove '/tmp/closure_error.log': Operation not permitted
| include.sh: line 132: /tmp/closure_error.log: Permission denied
| rm: cannot remove '/tmp/dataTables.bootstrap4.js': Operation not permitted
|   File size: 0

The much worse thing: The build does *not* catch that situation. Instead,
the package is happily built with zero-sized files.

The patch attached adds the usage of a random temporary directory that
is cleaned up upon exit. Also the make.sh script now uses errexit. This
should catch all unexpected errors during execution.

According to diffoscope, the created binary packages are bitwise
identical.

Cheers,

Christoph, do not apply as-is

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.1 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: unable to detect
Subject: Use a temporary directory to build, run the make.sh script under errexit. Closes: #-1
Author: Christoph Biedl 
Bug-Debian: https://bugs.debian.org/-1

--- a/build/include.sh
+++ b/build/include.sh
@@ -5,6 +5,8 @@
 CLOSURE="/usr/share/java/closure-compiler.jar"
 JSHINT="/usr/bin/jshint"
 
+TMPDIR="$(mktemp --directory --tmpdir "jquery-datatables.$$.X")"
+trap "rm -rf \"$TMPDIR\"" EXIT
 
 # CSS styling frameworks that DataTables supports
 FRAMEWORKS=(
@@ -125,23 +127,23 @@
 
 		# Closure Compiler doesn't support "important" comments so we add a
 		# @license jsdoc comment to the license block to preserve it
-		cp $DIR/$FILE.js /tmp/$FILE.js
-		perl -i -0pe "s/^\/\*! (.*)$/\/** \@license \$1/s" /tmp/$FILE.js
+		cp $DIR/$FILE.js $TMPDIR/$FILE.js
+		perl -i -0pe "s/^\/\*! (.*)$/\/** \@license \$1/s" $TMPDIR/$FILE.js
 
-		rm /tmp/closure_error.log
-		java -jar $CLOSURE --charset 'utf-8' --js /tmp/$FILE.js > /tmp/$FILE.min.js 2> /tmp/closure_error.log
+		rm $TMPDIR/closure_error.log || true
+		java -jar $CLOSURE --charset 'utf-8' --js $TMPDIR/$FILE.js > $TMPDIR/$FILE.min.js 2> $TMPDIR/closure_error.log
 
-		if [ -e /tmp/closure_error.log ]; then
+		if [ -e $TMPDIR/closure_error.log ]; then
 			if [ -z "$LOG" -o "$LOG" = "on" ]; then
-cat /tmp/closure_error.log
+cat $TMPDIR/closure_error.log
 			fi
 		fi
 
 		# And add the important comment back in
-		perl -i -0pe "s/^\/\*/\/*!/s" /tmp/$FILE.min.js
+		perl -i -0pe "s/^\/\*/\/*!/s" $TMPDIR/$FILE.min.js
 
-		mv /tmp/$FILE.min.js $DIR/$FILE.min.js
-		rm /tmp/$FILE.js
+		mv $TMPDIR/$FILE.min.js $DIR/$FILE.min.js
+		rm $TMPDIR/$FILE.js
 
 		echo_msg "  File size: $(ls -l $DIR/$FILE.min.js | awk -F" " '{ print $5 }')"
 	fi
@@ -161,9 +163,10 @@
 	IFS='%'
 
 	cp $IN_FILE $IN_FILE.build
-	grep "_buildInclude('" $IN_FILE.build > /dev/null
+	CODE=0
+	grep "_buildInclude('" $IN_FILE.build > /dev/null || CODE=$?
 
-	while [ $? -eq 0 ]; do
+	while [ $CODE -eq 0 ]; do
 		REQUIRE=$(grep "_buildInclude('" $IN_FILE.build | head -n 1)
 
 		SPACER=$(echo ${REQUIRE} | cut -d _ -f 1)
@@ -177,7 +180,7 @@
 
 		rm ${DIR}/${FILE}.build
 
-		grep "_buildInclude('" $IN_FILE.build > /dev/null
+		grep "_buildInclude('" $IN_FILE.build > /dev/null || CODE=$?
 	done
 
 	mv $IN_FILE.build $OUT
--- a/build/make.sh
+++ b/build/make.sh
@@ -1,5 +1,7 @@
 #!/bin/bash
 
+set -e
+
 . include.sh
 
 SCRIPT_DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
@@ -34,

Bug#447764: marked as done (libapache2-mod-php5: PHP5 should provide a LAMP test page)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #447764,
regarding libapache2-mod-php5: PHP5 should provide a LAMP test page
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.)


-- 
447764: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=447764
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libapache2-mod-php5
Version: 5.2.4-1
Severity: wishlist

To make it easier for users to see that their LAMP installation is working,
PHP5 should provide a LAMP test page.

Please consider the attached diff for creating a /var/www/lamp-test/index.php
that tests PHP, MySQL and PostgreSQL.
diff -u php5-5.2.4/debian/libapache2-mod-php5.dirs php5-5.2.4/debian/libapache2-mod-php5.dirs
--- php5-5.2.4/debian/libapache2-mod-php5.dirs
+++ php5-5.2.4/debian/libapache2-mod-php5.dirs
@@ -3,0 +4 @@
+/var/www/lamp-test
diff -u php5-5.2.4/debian/changelog php5-5.2.4/debian/changelog
--- php5-5.2.4/debian/changelog
+++ php5-5.2.4/debian/changelog
@@ -1,3 +1,11 @@
+php5 (5.2.4-2) unstable; urgency=low
+
+  * added debian/lamp-test.php
+  * debian/libapache2-mod-php5.dirs: added /var/www/lamp-test
+  * debian/rules: install lamp-test.php to /var/www/lamp-test/index.php
+
+ -- Jamie Strandboge   Tue, 23 Oct 2007 12:41:34 -0400
+
 php5 (5.2.4-1) unstable; urgency=low
 
   * New upstream release.
diff -u php5-5.2.4/debian/rules php5-5.2.4/debian/rules
--- php5-5.2.4/debian/rules
+++ php5-5.2.4/debian/rules
@@ -321,6 +321,8 @@
 		debian/libapache2-mod-php5/etc/apache2/mods-available/php5.load
 	cp debian/libapache2-mod-php5.conf \
 		debian/libapache2-mod-php5/etc/apache2/mods-available/php5.conf
+	cp debian/lamp-test.php \
+		debian/libapache2-mod-php5/var/www/lamp-test/index.php
 
 	# sanitize php.ini file
 	cat php.ini-dist | tr "\t" " " > debian/php5-common/usr/share/php5/php.ini-dist
only in patch2:
unchanged:
--- php5-5.2.4.orig/debian/lamp-test.php
+++ php5-5.2.4/debian/lamp-test.php
@@ -0,0 +1,107 @@
+
+  LAMP Server Test Page   LAMP Server Test PageComponent Status   ApacheWorks   
+
+ PHPNot working
+
+
+
+ Mysql (localhost)Not working
+ 
+
+
+ PostgreSQL (localhost)
+ Not working
+ 
+
+
+
+ 
+
+
+
+
+
--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm

Dear submitter,

as the package php5 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/841781

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)--- End Message ---

Bug#639268: marked as done (libapache2-mod-php5: .phar files not executed with php)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #639268,
regarding libapache2-mod-php5: .phar files not executed with php
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.)


-- 
639268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639268
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libapache2-mod-php5
Version: 5.3.5-1ubuntu7.2
Severity: normal

..phar files are not executed with php when accessed through apache.

..phar is a file format to pack up whole PHP applications in a single file.

Reason for the problem is that
> /etc/apache2/mods-available/php5.conf
contains
>
>SetHandler application/x-httpd-php
>
which does not match ".phar". The regex should be extended to
"\.ph(ar|p3?|tml)$"

-- System Information:
Debian Release: squeeze/sid
  APT prefers natty-updates
  APT policy: (500, 'natty-updates'), (500, 'natty-security'), (500, 'natty')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.38-11-generic (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libapache2-mod-php5 depends on:
ii  apache2-mpm-pref 2.2.17-1ubuntu1 Apache HTTP Server - traditional n
ii  apache2.2-common 2.2.17-1ubuntu1 Apache HTTP Server common files
ii  libbz2-1.0   1.0.5-6ubuntu1  high-quality block-sorting file co
ii  libc62.13-0ubuntu13  Embedded GNU C Library: Shared lib
ii  libdb4.8 4.8.30-5ubuntu2 Berkeley v4.8 Database Libraries [
ii  libmagic15.04-5ubuntu2   File type determination library us
ii  libpcre3 8.12-3ubuntu2   Perl 5 Compatible Regular Expressi
ii  libssl0.9.8  0.9.8o-5ubuntu1 SSL shared libraries
ii  libxml2  2.7.8.dfsg-2ubuntu0.1   GNOME XML library
ii  mime-support 3.51-1ubuntu1   MIME files 'mime.types' & 'mailcap
ii  php5-common  5.3.5-1ubuntu7.2Common files for packages built fr
ii  tzdata   2011g-0ubuntu0.11.04time zone and daylight-saving time
ii  ucf  3.0025+nmu1ubuntu1  Update Configuration File: preserv
ii  zlib1g   1:1.2.3.4.dfsg-3ubuntu3 compression library - runtime

Versions of packages libapache2-mod-php5 recommends:
ii  php5-cli5.3.5-1ubuntu7.2 command-line interpreter for the p

Versions of packages libapache2-mod-php5 suggests:
ii  php-pear5.3.5-1ubuntu7.2 PEAR - PHP Extension and Applicati

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm

Dear submitter,

as the package php5 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/841781

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)--- End Message ---

Bug#819304: marked as done (json_decode warns of integer overflow for max int)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:04:18 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #819304,
regarding json_decode warns of integer overflow for max int
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.)


-- 
819304: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819304
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-json
Version: 1.3.6

(This is from an up-to-date Debian Jessie 63 bit install, using PHP 5.6.17,
package version as reported by phpinfo())

I reported this bug to PHP. They said it was a replacement component in
Debian's PHP.
  https://bugs.php.net/bug.php?id=71900

Description:


The json_decode function produces
   PHP Notice:  json_decode(): integer overflow detected in .../test.php on
line 11
when the value concerned is 9223372036854775807 (i.e. PHP_INT_MAX), which
is a valid value.

This has a particular impact in decoding certain results from elasticsearch
which contain max int values.

Test script:
---
 PHP_INT_MAX); /* it works OK if you put PHP_INT_MAX-1
here */
print_r($a);
$j = json_encode($a);

echo $j, "\n";

$b = json_decode($j); /* produces the incorrect error message */
print_r($b);


Expected result:

No warning.


Actual result:
--
PHP Notice:  json_decode(): integer overflow detected
--- End Message ---
--- Begin Message ---
Version: 1.3.9-1+rm

Dear submitter,

as the package php-json 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/841781

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)--- End Message ---

Bug#803244: marked as done (php5-common: upgrading enables manually disabled opcache)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #752100,
regarding php5-common: upgrading enables manually disabled opcache
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.)


-- 
752100: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752100
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-common
Version: 5.6.14+dfsg-0+deb8u1
Severity: serious

Dear Maintainer,

I was under impression that maintainer scripts shouldn't recreate
configuration files removed by system administrator. php5-common just
recreated symbolic link from /etc/php5/sapi/conf.d/05-opcache.ini to 
mods-available,
which I had removed since xcache works better for us and enabling both 
segfaults apache.

And yes, after enough digging I found about php5dismod and 
/var/lib/php5/modules/fpm/disabled_by_admin/,
but this behaviour is quite unexpected.

-- Package-specific info:
 Additional PHP 5 information 

 PHP 5 SAPI (php5query -S): 
fpm
cli
cgi

 PHP 5 Extensions (php5query -M -v): 
mysql (Enabled for fpm by maintainer script)
mysql (Enabled for cli by maintainer script)
mysql (Enabled for cgi by maintainer script)
pspell (Enabled for fpm by maintainer script)
pspell (Enabled for cli by maintainer script)
pspell (Enabled for cgi by maintainer script)
intl (Enabled for fpm by maintainer script)
intl (Enabled for cli by maintainer script)
intl (Enabled for cgi by maintainer script)
pdo (Enabled for fpm by maintainer script)
pdo (Enabled for cli by maintainer script)
pdo (Enabled for cgi by maintainer script)
mysqli (Enabled for fpm by maintainer script)
mysqli (Enabled for cli by maintainer script)
mysqli (Enabled for cgi by maintainer script)
curl (Enabled for fpm by maintainer script)
curl (Enabled for cli by maintainer script)
curl (Enabled for cgi by maintainer script)
mcrypt (Enabled for fpm by maintainer script)
mcrypt (Enabled for cli by maintainer script)
mcrypt (Enabled for cgi by maintainer script)
pdo_mysql (Enabled for fpm by maintainer script)
pdo_mysql (Enabled for cli by maintainer script)
pdo_mysql (Enabled for cgi by maintainer script)
gd (Enabled for fpm by maintainer script)
gd (Enabled for cli by maintainer script)
gd (Enabled for cgi by maintainer script)
pgsql (Enabled for fpm by maintainer script)
pgsql (Enabled for cli by maintainer script)
pgsql (Enabled for cgi by maintainer script)
pdo_sqlite (Enabled for fpm by maintainer script)
pdo_sqlite (Enabled for cli by maintainer script)
pdo_sqlite (Enabled for cgi by maintainer script)
pdo_pgsql (Enabled for fpm by maintainer script)
pdo_pgsql (Enabled for cli by maintainer script)
pdo_pgsql (Enabled for cgi by maintainer script)
json (Enabled for fpm by maintainer script)
json (Enabled for cli by maintainer script)
json (Enabled for cgi by maintainer script)
imap (Enabled for fpm by maintainer script)
imap (Enabled for cli by maintainer script)
imap (Enabled for cgi by maintainer script)
xcache (Enabled for fpm by maintainer script)
xcache (Enabled for cli by maintainer script)
xcache (Enabled for cgi by maintainer script)
sqlite3 (Enabled for fpm by maintainer script)
sqlite3 (Enabled for cli by maintainer script)
sqlite3 (Enabled for cgi by maintainer script)

 Configuration files: 
 /etc/php5/mods-available/pdo.ini 
extension=pdo.so

 /etc/php5/mods-available/opcache.ini 
zend_extension=opcache.so


-- System Information:
Debian Release: 8.2
  APT prefers stable
  APT policy: (900, 'stable'), (890, 'testing'), (499, 'unstable'), (101, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages php5-common depends on:
ii  libc6   2.19-18+deb8u1
ii  lsof4.86+dfsg-1
ii  psmisc  22.21-2
ii  sed 4.2.2-4+b1
ii  ucf 3.0030

php5-common recommends no packages.

Versions of packages php5-common suggests:
ii  php5-xcache [php5-user-cache]  3.2.0-1

Versions of packages php5-cli depends on:
ii  libbz2-1.01.0.6-7+b3
ii  libc6 2.19-18+deb8u1
ii  libcomerr21.42.12-1.1
ii  libdb5.3  5.3.28-9
ii  libedit2  3.1-20140620-2
ii  libgssapi-krb5-2  1.12.1+dfsg-19
ii  libk5crypto3  1.12.1+dfsg-19
ii  libkrb5-3 1.12.1+dfsg-19
ii  libmagic1 1:5.22+15-2
ii  libonig2  5.9.5-3.2
ii  libpcre3  2:8.35-3.3
ii  libqdbm14 1

Bug#774975: marked as done (Serialization issue on DateTime objects by using PHP 5.4.35-0+deb7u2)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #774975,
regarding Serialization issue on DateTime objects by using PHP 5.4.35-0+deb7u2
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.)


-- 
774975: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774975
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5
Version: 5.4.35-0+deb7u2


Dear Maintainer,

On the Debian Wheezy distribution, since the last update of PHP5 to the version 
5.4.35-0+deb7u2, the serialization of DateTime seems to be broken.
The problem occurs periodically and is reproducible with difficulties.

In my test environment, the problem occurs when I want to read data that are 
stored into the Redis Server.
Examples:

During the authentication, when the problem occurs, the stack trace is :
[{"message":"Error: Invalid serialization data for DateTime object in 
\/var\/www\/\/front\/vendor\/symfony\/symfony\/src\/Symfony\/Component\/Security\/Core\/Authentication\/Token\/AbstractToken.php
 line 
163","class":"Symfony\\Component\\Debug\\Exception\\FatalErrorException","trace":[{"namespace":"","short_class":"","class":"","type":"","function":"","file":"\/var\/www\/\/front\/vendor\/symfony\/symfony\/src\/Symfony\/Component\/Security\/Core\/Authentication\/Token\/AbstractToken.php","line":163,"args":[]}]}]

Another example during data retrieval from cache:
{"message":"Error: Invalid serialization data for DateTime object in 
\/var\/www\/\/front\/src\/\/APIBundle\/Service\/Service.php line 
144","class":"Symfony\\Component\\Debug\\Exception\\FatalErrorException","trace":[{"namespace":"","short_class":"","class":"","type":"","function":"","file":"\/var\/www\/\/front\/src\/\/APIBundle\/Service\/Service.php","line":144,"args":[]}]}]

I've found a recent bug report in the EZPublish project that seems to be built 
on Symfony 2 components: https://jira.ez.no/browse/EZP-23713. Attached files to 
this issue are interesting because we have a valid and an invalid DateTime 
serialization.

Then I've downgraded my Debian Wheezy PHP5 package to this version : 
5.4.4-14+deb7u14 , and the problem doesn't exists.


-- System Information:
Debian Release: 7.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.11-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages php5 depends on:
ii  libapache2-mod-php5  5.4.35-0+deb7u2
ii  php5-common  5.4.35-0+deb7u2

php5 recommends no packages.

php5 suggests no packages.

-- no debconf information


Cordialement,

      _
Loïc Cotonéa | Architecte | Advanced Technology Center

Ligne directe: +33(0)2 23 45 59 37
Skype: l.cotonea.sogeti
--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm

Dear submitter,

as the package php5 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/841781

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)--- End Message ---

Bug#730067: marked as done (php5enmod/php5dismod and pecl install discrepancies)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #730067,
regarding php5enmod/php5dismod and pecl install discrepancies
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.)


-- 
730067: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730067
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5
  Version: 5.5.5+dfsg-1


Hi,

With the new php5 packages (5.4+) it looks like we are expecting extensions
to be deploying their ini file in /etc/php5/mods-available.

When I install a new package via 'pecl install uuid' for example, it still
puts the associated ini file in /etc/php5/conf.d and php5enmod knows
nothing of it.

Is there a way I can configure pecl to drop the install module's ini file
in /etc/php5/mods-available ?
Should I manually symlink /etc/php5/conf.d/uuid.ini ->
/etc/php5/mods-available/uuid.
ini ?

What is the expected behavior here?

-- Sander
--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm

Dear submitter,

as the package php5 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/841781

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)--- End Message ---

Bug#752100: marked as done ([php5-common] Ships undocumented /usr/sbin/php5query)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #752100,
regarding [php5-common] Ships undocumented /usr/sbin/php5query
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.)


-- 
752100: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752100
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: php5-common
Version: 5.6.0~beta4+dfsg-4
Severity: normal

php5-common ships /usr/sbin/php5query, but fails to provide a manual page for 
it.

--
Filipus Klutiero
http://www.philippecloutier.com
--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm

Dear submitter,

as the package php5 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/841781

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)--- End Message ---

Bug#628079: marked as done (php5-common: Wrong timezone selected)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #628079,
regarding php5-common: Wrong timezone selected
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.)


-- 
628079: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628079
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-common
Version: 5.3.6-11
Severity: normal

Both the apache module and cli PHP show my timezone as
Antartica/Macquarie.  I'm not a penguin and don't live there.
The rest of the system thinks my timezone is Australia/NSW which is
correct.

I cannot find anywhere where it is set as it is commented out in the
php.ini files.  If I set the timezone in my php.ini file then everything
works correctly, but why can't php just use the system timezone like the
rest of the computer does ok?

date
date/time support   enabled
"Olson" Timezone Database Version   0.system
Timezone Database   internal
Default timezone  Antarctica/Macquarie

Directive Local Value Master Value
date.default_latitude 31.7667 31.7667
date.default_longitude  35.2333 35.2333
date.sunrise_zenith 90.58 90.58
date.sunset_zenith  90.58 90.58
date.timezone no value  no value


-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages php5-common depends on:
ii  libc6 2.13-4 Embedded GNU C Library: Shared lib
ii  sed   4.2.1-9The GNU sed stream editor

Versions of packages php5-common recommends:
ii  php5-suhosin  0.9.32.1-1 advanced protection module for php

php5-common suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm

Dear submitter,

as the package php5 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/841781

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)--- End Message ---

Bug#697800: marked as done (php5-common: All date functions result in a fatal PHP error on glusterfs filesystems)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #697800,
regarding php5-common: All date functions result in a fatal PHP error on 
glusterfs filesystems
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.)


-- 
697800: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697800
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-common
Version: 5.4.9-4
Severity: important
Tags: upstream

On a system that has a glusterfs filesystem, if you try to use any date 
function, you are presented with a fatal error like

PHP Fatal error:  date(): Timezone database is corrupt - this should *never* 
happen! in - on line 1

To reproduce this error you will need a system that has a glusterfs filesystem, 
or at least where /usr/share/zoneinfo is mounted on a glusterfs, and then you 
can just run:

echo ""|php

This is an strace of doing that on my affected system:

execve("/usr/bin/php", ["php", "-r", "printf(date(\"r\") .\"\\n\");"], [/* 26 
vars */]) = 0
brk(0)  = 0x23b7000
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f1cd05bd000
access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY)  = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=64, ...}) = 0
mmap(NULL, 64, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f1cd05b8000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/tls/x86_64/libcrypt.so.1", O_RDONLY) = -1 ENOENT 
(No such file or directory)
stat("/lib/x86_64-linux-gnu/tls/x86_64", 0x7aaebba0) = -1 ENOENT (No such 
file or directory)
open("/lib/x86_64-linux-gnu/tls/libcrypt.so.1", O_RDONLY) = -1 ENOENT (No such 
file or directory)
stat("/lib/x86_64-linux-gnu/tls", 0x7aaebba0) = -1 ENOENT (No such file or 
directory)
open("/lib/x86_64-linux-gnu/x86_64/libcrypt.so.1", O_RDONLY) = -1 ENOENT (No 
such file or directory)
stat("/lib/x86_64-linux-gnu/x86_64", 0x7aaebba0) = -1 ENOENT (No such file 
or directory)
open("/lib/x86_64-linux-gnu/libcrypt.so.1", O_RDONLY) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\n\0\0\0\0\0\0"..., 
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=35104, ...}) = 0
mmap(NULL, 2318784, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7f1cd0168000
mprotect(0x7f1cd017, 2093056, PROT_NONE) = 0
mmap(0x7f1cd036f000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x7000) = 0x7f1cd036f000
mmap(0x7f1cd0371000, 184768, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f1cd0371000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libz.so.1", O_RDONLY) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\340#\0\0\0\0\0\0"..., 
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=92752, ...}) = 0
mmap(NULL, 2187792, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7f1ccff5
mprotect(0x7f1ccff66000, 2093056, PROT_NONE) = 0
mmap(0x7f1cd0165000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x15000) = 0x7f1cd0165000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libonig.so.2", O_RDONLY) = -1 ENOENT (No such file 
or directory)
open("/usr/lib/x86_64-linux-gnu/tls/x86_64/libonig.so.2", O_RDONLY) = -1 ENOENT 
(No such file or directory)
stat("/usr/lib/x86_64-linux-gnu/tls/x86_64", 0x7aaebb40) = -1 ENOENT (No 
such file or directory)
open("/usr/lib/x86_64-linux-gnu/tls/libonig.so.2", O_RDONLY) = -1 ENOENT (No 
such file or directory)
stat("/usr/lib/x86_64-linux-gnu/tls", 0x7aaebb40) = -1 ENOENT (No such file 
or directory)
open("/usr/lib/x86_64-linux-gnu/x86_64/libonig.so.2", O_RDONLY) = -1 ENOENT (No 
such file or directory)
stat("/usr/lib/x86_64-linux-gnu/x86_64", 0x7aaebb40) = -1 ENOENT (No such 
file or directory)
open("/usr/lib/x86_64-linux-gnu/libonig.so.2", O_RDONLY) = -1 ENOENT (No such 
file or directory)
stat("/usr/lib/x86_64-linux-gnu", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
open("/lib/tls/x86_64/libonig.so.2", O_RDONLY) = -1 ENOENT (No such file or 
directory)
stat("/lib/tls/x86_64", 0x7aaebb40) = -1 ENOENT (No such file or directo

Bug#760454: marked as done (php5-dev: ext_skel has wrong path for skeleton)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #760454,
regarding php5-dev: ext_skel has wrong path for skeleton
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.)


-- 
760454: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760454
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-dev
Version: 5.4.4-14+deb7u14
Severity: normal
Tags: patch

In the file /usr/share/php5/ext_skel the skeleton directory is defined as 
/usr/lib/php5/skeleton but it's actually in /usr/share/php5/skeleton

-- System Information:
Debian Release: 7.6
  APT prefers proposed-updates
  APT policy: (990, 'proposed-updates'), (990, 'stable'), (500, 
'stable-updates')
Architecture: i386 (x86_64)
Foreign Architectures: amd64

Kernel: Linux 3.2.60 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages php5-dev depends on:
ii  autoconf 2.69-1
ii  automake 1:1.11.6-1
ii  libssl-dev   1.0.1e-2+deb7u12
ii  libtool  2.4.2-1.1
ii  php5-common  5.4.4-14+deb7u14
ii  shtool   2.0.8-6

php5-dev recommends no packages.

php5-dev suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm

Dear submitter,

as the package php5 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/841781

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)--- End Message ---

Bug#500087: marked as done (CVE-2008-4107: The rand and mt_rand functions in PHP produce weak random numbers)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #500087,
regarding CVE-2008-4107: The rand and mt_rand functions in PHP produce weak 
random numbers
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.)


-- 
500087: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500087
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5
Version: 5.2.6-3
Severity: important
Tags: security


>From CVE-2008-4107:
The (1) rand and (2) mt_rand functions in PHP 5.2.6 do not produce
cryptographically strong random numbers, which allows attackers to
leverage exposures in products that rely on these functions for
security-relevant functionality, as demonstrated by the password-reset
functionality in Joomla! 1.5.x and WordPress before 2.6.2, a different
vulnerability than CVE-2008-2107, CVE-2008-2108, and CVE-2008-4102.


The advisory
http://www.suspekt.org/2008/08/17/mt_srand-and-not-so-random-numbers/
talks about a new suhosin release that fixes this in php and not in the
applications. Maybe this fix could be backported to lenny once it becomes
available?


--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm

Dear submitter,

as the package php5 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/841781

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)--- End Message ---

Bug#727143: marked as done (libapache2-mod-php5: max_execution_time + SSL causes data transfer corruption)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #727143,
regarding libapache2-mod-php5: max_execution_time + SSL causes data transfer 
corruption
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.)


-- 
727143: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727143
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libapache2-mod-php5
Version: 5.3.3-7+squeeze17
Severity: important

When using libapache2-mod-php5 and max_execution_time long lasting data 
transfers
via SSL/TLS get corrupted.

Steps to reproduce:

1. Install apache2 and libapache2-mod-php5
2. a2enmod ssl
3. insert "php_admin_value max_execution_time 30" into default-ssl.conf
4. a2ensite default-ssl
5. create a large file (at least 2GB) in /var/www
6. try to download this file using
   wget https://localhost/test -O /dev/null --no-check-certificate

Result:

The transfer aborts after some time because of one of the following reasons:
 - partial content
 - wrong TLS packet size
 - connection closed

For us it happens mostly after having downloaded between 1.4 and 2.0 GB.

In the apache error.log you can see the following message:
[notice] child pid 3658 exit signal Profiling timer expired (27)

The value of max_execution_time does not matter. Setting it to 5 and 5000
results in the same behavior. The problem also does not occur after a specific
time or a specific data amount.

We noticed this behavior at the end of september so it may be caused by one
of the latest updates.


-- System Information:
Debian Release: 6.0.8
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF8, LC_CTYPE=de_DE.UTF8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libapache2-mod-php5 depends on:
ii  apache2-mpm-prefor 2.2.16-6+squeeze11Apache HTTP Server - traditional n
ii  apache2.2-common   2.2.16-6+squeeze11Apache HTTP Server common files
ii  libbz2-1.0 1.0.5-6+squeeze1  high-quality block-sorting file co
ii  libc6  2.11.3-4  Embedded GNU C Library: Shared lib
ii  libcomerr2 1.41.12-4stable1  common error description library
ii  libdb4.8   4.8.30-2  Berkeley v4.8 Database Libraries [
ii  libgssapi-krb5-2   1.8.3+dfsg-4squeeze7  MIT Kerberos runtime libraries - k
ii  libk5crypto3   1.8.3+dfsg-4squeeze7  MIT Kerberos runtime libraries - C
ii  libkrb5-3  1.8.3+dfsg-4squeeze7  MIT Kerberos runtime libraries
ii  libmagic1  5.04-5+squeeze2   File type determination library us
ii  libonig2   5.9.1-1   Oniguruma regular expressions libr
ii  libpcre3   8.02-1.1  Perl 5 Compatible Regular Expressi
ii  libqdbm14  1.8.77-4  QDBM Database Libraries [runtime]
ii  libssl0.9.80.9.8o-4squeeze14 SSL shared libraries
ii  libxml22.7.8.dfsg-2+squeeze8 GNOME XML library
ii  mime-support   3.48-1MIME files 'mime.types' & 'mailcap
ii  php5-common5.3.3-7+squeeze17 Common files for packages built fr
ii  tzdata 2013d-0squeeze1   time zone and daylight-saving time
ii  ucf3.0025+nmu1   Update Configuration File: preserv
ii  zlib1g 1:1.2.3.4.dfsg-3  compression library - runtime

Versions of packages libapache2-mod-php5 recommends:
ii  php5-cli   5.3.3-7+squeeze17 command-line interpreter for the p

Versions of packages libapache2-mod-php5 suggests:
pn  php-pear   (no description available)

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm

Dear submitter,

as the package php5 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/841781

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)--- End Message ---

Bug#643282: marked as done (php5-gd: gd ignores memory limit)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #643282,
regarding php5-gd: gd ignores memory limit
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.)


-- 
643282: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643282
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-gd
Version: 5.2.6.dfsg.1-1+lenny10
Severity: normal


gd circumvents php's built-in memory limit
it easy to far exceed the memory limit by using 
imagecreate with large parameters, probably also possible 
using imagecreatefrom* too.

perhaps gdFree() and gdAlloc() can be hijacked to track usage?


-- System Information:
Debian Release: 5.0.8
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages php5-gd depends on:
ii  libapache2-mod- 5.2.6.dfsg.1-1+lenny10   server-side, HTML-embedded scripti
ii  libc6   2.7-18lenny7 GNU C Library: Shared libraries
ii  libfreetype62.3.7-2+lenny5   FreeType 2 font engine, shared lib
ii  libgd2-xpm  2.0.36~rc1~dfsg-3+lenny1 GD Graphics Library version 2
ii  libjpeg62   6b-14The Independent JPEG Group's JPEG 
ii  libpng12-0  1.2.27-2+lenny4  PNG library - runtime
ii  libt1-5 5.1.2-3  Type 1 font rasterizer library - r
ii  libx11-62:1.1.5-2X11 client-side library
ii  libxpm4 1:3.5.7-1X11 pixmap library
ii  php5-cli [phpap 5.2.6.dfsg.1-1+lenny10   command-line interpreter for the p
ii  php5-common 5.2.6.dfsg.1-1+lenny10   Common files for packages built fr
ii  zlib1g  1:1.2.3.3.dfsg-12compression library - runtime

php5-gd recommends no packages.

php5-gd suggests no packages.

-- debconf-show failed


--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm

Dear submitter,

as the package php5 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/841781

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)--- End Message ---

Bug#664595: marked as done (RFH: php5 -- server-side, HTML-embedded scripting language)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #664595,
regarding RFH: php5 -- server-side, HTML-embedded scripting language
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.)


-- 
664595: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664595
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: normal

PHP5 is a widely-used general-purpose scripting language that is
especially suited for Web development and can be embedded into HTML.
The goal of the language is to allow web developers to write
dynamically generated pages quickly.

Using PHP? Loving PHP? Feeling like having too much free time?

I WANT YOU FOR PHP MAINTAINER TEAM
 


We constantly need help with:
 - triaging and fixing reported bugs in Debian (not bad we only have
   83 open bugs :)
 - reporting upstream bugs to upstream bugtracker
 - doing upstream SVN archealogy   with a toothbrush looking for fixes
 - checking upstream tests and fixing bugs we introduced in our patches
 - helping to prepare security uploads for stable releases
 - helping our reverse dependencies to keep working when major version
   is introduced (recently PHP 5.4)

Please be aware that we are not looking for someone who can
upload&forget.  Packaging PHP can be tedious work and sometimes the
maintainers burn faster than gasoline.

Ondrej,
on behalf of the PHP packaging team


--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm

Dear submitter,

as the package php5 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/841781

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)--- End Message ---

Bug#618462: marked as done (php5: Use of systems' embedded timezone data causes performance regression)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #618462,
regarding php5: Use of systems' embedded timezone data causes performance 
regression
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.)


-- 
618462: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618462
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5
Version: 5.3.5-1
Severity: normal
Patch use_embedded_timezonedb.patch, calls stat() on every single file in
/usr/share/zoneinfo upon first use of tje timezone data - in total over 600
syscalls. Example:
$ strace -s 100 -r php -n -r"date_default_timezone_set('GMT');" 2>&1 | grep
zoneinfo | head -10
     0.000110 open("/usr/share/zoneinfo/",
O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|O_CLOEXEC) = 3
     0.31 stat64("/usr/share/zoneinfo//localtime", {st_mode=S_IFREG|0644,
st_size=3661, ...}) = 0
     0.61 stat64("/usr/share/zoneinfo//Zulu", {st_mode=S_IFREG|0644,
st_size=118, ...}) = 0
     0.55 stat64("/usr/share/zoneinfo//WET", {st_mode=S_IFREG|0644,
st_size=1873, ...}) = 0
     0.55 stat64("/usr/share/zoneinfo//W-SU", {st_mode=S_IFREG|0644,
st_size=2194, ...}) = 0
     0.56 stat64("/usr/share/zoneinfo//Universal", {st_mode=S_IFREG|0644,
st_size=118, ...}) = 0
     0.56 stat64("/usr/share/zoneinfo//UTC", {st_mode=S_IFREG|0644,
st_size=118, ...}) = 0
     0.54 stat64("/usr/share/zoneinfo//US", {st_mode=S_IFDIR|0755,
st_size=4096, ...}) = 0
     0.55 stat64("/usr/share/zoneinfo//UCT", {st_mode=S_IFREG|0644,
st_size=118, ...}) = 0
     0.54 stat64("/usr/share/zoneinfo//Turkey", {st_mode=S_IFREG|0644,
st_size=2721, ...}) = 0
Original discussion:
http://bugs.php.net/bug.php?id=54250


-- System Information:
Debian Release: wheezy/sid
Architecture: i386 (i686)
Kernel: Linux 2.6.31 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages php5 depends on:
ii  libapache2-mod-php5           5.3.5-1    server-side, HTML-embedded scripti
ii  php5-common                   5.3.5-1    Common files for packages built fr
php5 recommends no packages.
php5 suggests no packages.
-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm

Dear submitter,

as the package php5 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/841781

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)--- End Message ---

Bug#776564: marked as done (Patched php5 does not emit error when timezone database is unavailable)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #776564,
regarding Patched php5 does not emit error when timezone database is unavailable
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.)


-- 
776564: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776564
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5
Version: 5.6.5+dfsg-1
Severity: minor

I am reporting an issue with the Ubuntu version of this package deliberately
with Debian, because the issue lies with the Debian-maintained system
timezone database patch.

use_embedded_timezonedb.patch changes the behavior of the php5 package such
that it reads timezone information from /usr/share/zoneinfo. Among other
files, it reads /usr/share/zoneinfo/zone.tab. On a system I use, this file
was erroneously unavailable due to chroot and not mapping the file properly.
This caused various PHP functions to malfunction with no error or an error
that was hard to debug.

new DateTimeZone('UTC') : Exception: 'Unknown or bad timezone (UTC)'
timezone_identifiers_list() : empty result

The patch does not emit any warning when /usr/share/zoneinfo/zone.tab can't
be read. I suggest adding a warning or error using the regular PHP error
logging functions.

The relevant code of the patch:

+static struct location_info **create_location_table(void)
...
+fp = fopen(zone_tab, "r");
+if (!fp) {
+return NULL;
+}

NULL is ignored silently in other parts of the code.

Kind regards,

Jorrit Schippers
--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm

Dear submitter,

as the package php5 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/841781

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)--- End Message ---

Bug#731055: marked as done (php5-fpm: Extend the package sockets to multiply pools)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #731055,
regarding php5-fpm: Extend the package sockets to multiply pools
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.)


-- 
731055: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731055
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-fpm
Version: 5.5.1+dfsg-2
Severity: wishlist

Dear Maintainer,

Sorry for shortness as full description was lost buy reportbug (it my first
report here).

As at php5-fpm ver. 5.4 pool was moved to separate directory:
/etc/php5-fpm/pool.d
We should move socket for default www pool to
/var/run/php5-fpm/www.sock
That will add creating dir /var/run/php5-fpm on system start up (that I do
manually changing init.d/php5-fpm script.

Thanks.



-- Package-specific info:
 Additional PHP 5 information 

 PHP 5 SAPI (php5query -S): 
cli
fpm

 PHP 5 Extensions (php5query -M -v): 
tidy (Enabled for cli by maintainer script)
tidy (Enabled for fpm by maintainer script)
json (Enabled for cli by maintainer script)
json (Enabled for fpm by maintainer script)
mysqli (Enabled for cli by maintainer script)
mysqli (Enabled for fpm by maintainer script)
mcrypt (Enabled for cli by maintainer script)
mcrypt (Enabled for fpm by maintainer script)
mysql (Enabled for cli by maintainer script)
mysql (Enabled for fpm by maintainer script)
sqlite3 (Enabled for cli by maintainer script)
sqlite3 (Enabled for fpm by maintainer script)
pdo_sqlite (Enabled for cli by maintainer script)
pdo_sqlite (Enabled for fpm by maintainer script)
gmp (Enabled for cli by maintainer script)
gmp (Enabled for fpm by maintainer script)
mysqlnd (Enabled for cli by maintainer script)
mysqlnd (Enabled for fpm by maintainer script)
xdebug (Enabled for cli by local administrator)
xdebug (Enabled for fpm by local administrator)
pdo_mysql (Enabled for cli by maintainer script)
pdo_mysql (Enabled for fpm by maintainer script)
opcache (Enabled for cli by maintainer script)
opcache (Enabled for fpm by maintainer script)
pdo (Enabled for cli by maintainer script)
pdo (Enabled for fpm by maintainer script)
intl (Enabled for cli by maintainer script)
intl (Enabled for fpm by maintainer script)
gd (Enabled for cli by maintainer script)
gd (Enabled for fpm by maintainer script)
curl (Enabled for cli by maintainer script)
curl (Enabled for fpm by maintainer script)

 Configuration files: 
[PHP]
engine = On
short_open_tag = Off
asp_tags = Off
precision = 14
output_buffering = 4096
zlib.output_compression = Off
implicit_flush = Off
unserialize_callback_func =
serialize_precision = 17
disable_functions = 
pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,
disable_classes =
zend.enable_gc = On
expose_php = On
max_execution_time = 30
max_input_time = 60
memory_limit = 128M
error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT
display_errors = Off
display_startup_errors = Off
log_errors = On
log_errors_max_len = 1024
ignore_repeated_errors = Off
ignore_repeated_source = Off
report_memleaks = On
track_errors = Off
html_errors = On
variables_order = "GPCS"
request_order = "GP"
register_argc_argv = Off
auto_globals_jit = On
post_max_size = 8M
auto_prepend_file =
auto_append_file =
default_mimetype = "text/html"
doc_root =
user_dir =
enable_dl = Off
file_uploads = On
upload_max_filesize = 2M
max_file_uploads = 20
allow_url_fopen = On
allow_url_include = Off
default_socket_timeout = 60
[CLI Server]
cli_server.color = On
[Date]
[filter]
[iconv]
[intl]
[sqlite]
[sqlite3]
[Pcre]
[Pdo]
[Pdo_mysql]
pdo_mysql.cache_size = 2000
pdo_mysql.default_socket=
[Phar]
[mail function]
SMTP = localhost
smtp_port = 25
mail.add_x_header = On
[SQL]
sql.safe_mode = Off
[ODBC]
odbc.allow_persistent = On
odbc.check_persistent = On
odbc.max_persistent = -1
odbc.max_links = -1
odbc.defaultlrl = 4096
odbc.defaultbinmode = 1
[Interbase]
ibase.allow_persistent = 1
ibase.max_persistent = -1
ibase.max_links = -1
ibase.timestampformat = "%Y-%m-%d %H:%M:%S"
ibase.dateformat = "%Y-%m-%d"
ibase.timeformat = "%H:%M:%S"
[MySQL]
mysql.allow_local_infile = On
mysql.allow_persistent = On
mysql.cache_size = 2000
mysql.max_persistent = -1
mysql.max_links = -1
mysql.default_port =
mysql.defaul

Bug#715264: marked as done (php5-common: maxlifetime output warning if pcntl extension is enabled in /etc/php5/${sapi}/php.ini)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #715264,
regarding php5-common: maxlifetime output warning if pcntl extension is enabled 
in /etc/php5/${sapi}/php.ini
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.)


-- 
715264: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=715264
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-common
Version: 5.5.0+dfsg-6
Severity: normal
Tags: patch

Dear Maintainer,

After a manual installation of the pcntl extension, I have enabled this 
extension only in the /etc/php5/apache2/php.ini configuration file, since the 
php-cli has built-in support for pcntl.
Enabling pcntl extension in a generic configuration file like 
/etc/php5/conf.d/pcntl.ini throws following warning when using php cli :
PHP Warning:  Module 'pcntl' already loaded in Unknown on line 0

The 'maxlifetime' command forces the /etc/php5/apache2/php.ini configuration 
file with the php cli command.
This outputs the warning to stderr, which is sent by email each time the 
/etc/cron.d/php5 crontab fragment is called.
We may redirect the stderr of php command to /dev/null, or simply not use the 
php command at all.

Attached patch provides the second solution.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/16 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages php5-common depends on:
ii  dpkg1.16.10
ii  libc6   2.17-7
ii  lsof4.86+dfsg-1
ii  psmisc  22.20-1
ii  sed 4.2.2-1
ii  ucf 3.0027+nmu1

Versions of packages php5-common recommends:
ii  php5-json  0~git~1+c05ebf+dfsg-2

Versions of packages php5-common suggests:
pn  php5-user-cache  

-- no debconf information
--- maxlifetime.origin	2013-07-07 12:28:23.477394297 +
+++ maxlifetime	2013-07-07 12:32:57.305407550 +
@@ -2,21 +2,11 @@
 
 max=1440
 
-if which php5 >/dev/null 2>&1; then
-for sapi in apache2 apache2filter cgi fpm; do
-	if [ -e /etc/php5/${sapi}/php.ini ]; then
-	cur=$(php5 -c /etc/php5/${sapi}/php.ini -d "error_reporting='~E_ALL'" -r 'print ini_get("session.gc_maxlifetime");')
-	[ -z "$cur" ] && cur=0
-	[ "$cur" -gt "$max" ] && max=$cur
-	fi
-done
-else
-for ini in /etc/php5/*/php.ini /etc/php5/conf.d/*.ini; do
-cur=$(sed -n -e 's/^[[:space:]]*session.gc_maxlifetime[[:space:]]*=[[:space:]]*\([0-9]\+\).*$/\1/p' $ini 2>/dev/null || true);
-[ -z "$cur" ] && cur=0
-[ "$cur" -gt "$max" ] && max=$cur
-done
-fi
+for ini in /etc/php5/*/php.ini /etc/php5/conf.d/*.ini; do
+cur=$(sed -n -e 's/^[[:space:]]*session.gc_maxlifetime[[:space:]]*=[[:space:]]*\([0-9]\+\).*$/\1/p' $ini 2>/dev/null || true);
+[ -z "$cur" ] && cur=0
+[ "$cur" -gt "$max" ] && max=$cur
+done
 
 echo $(($max/60))
 
--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm

Dear submitter,

as the package php5 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/841781

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)--- End Message ---

Bug#782778: marked as done (php5-common: Session cleaning in mpm-itk/FPM environment where sessions are stores in different directories)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #782778,
regarding php5-common: Session cleaning in mpm-itk/FPM environment where 
sessions are stores in different directories
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.)


-- 
782778: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782778
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-common
Version: 5.6.7-1~dotdeb.2
Severity: wishlist

Dear Maintainers,

Please consider enhancing the session cleaner script in regard of different 
session directory per FPM pool.
Thank you!


-- Package-specific info:
 Additional PHP 5 information 

 PHP 5 SAPI (php5query -S): 
fpm
cli

 PHP 5 Extensions (php5query -M -v): 
readline (Enabled for fpm by maintainer script)
readline (Enabled for cli by maintainer script)
gd (Enabled for fpm by maintainer script)
gd (Enabled for cli by maintainer script)
mysqlnd (Enabled for fpm by maintainer script)
mysqlnd (Enabled for cli by maintainer script)
sqlite3 (Enabled for fpm by maintainer script)
sqlite3 (Enabled for cli by maintainer script)
mysqli (Enabled for fpm by maintainer script)
mysqli (Enabled for cli by maintainer script)
opcache (Enabled for fpm by maintainer script)
opcache (Enabled for cli by maintainer script)
apcu (Enabled for fpm by maintainer script)
apcu (Enabled for cli by maintainer script)
pdo (Enabled for fpm by maintainer script)
pdo (Enabled for cli by maintainer script)
mcrypt (Enabled for fpm by maintainer script)
mcrypt (Enabled for cli by maintainer script)
pdo_sqlite (Enabled for fpm by maintainer script)
pdo_sqlite (Enabled for cli by maintainer script)
mysql (Enabled for fpm by maintainer script)
mysql (Enabled for cli by maintainer script)
curl (Enabled for fpm by maintainer script)
curl (Enabled for cli by maintainer script)
pdo_mysql (Enabled for fpm by maintainer script)
pdo_mysql (Enabled for cli by maintainer script)

 Configuration files: 
 /etc/php5/mods-available/pdo.ini 
extension=pdo.so

 /etc/php5/mods-available/opcache.ini 
zend_extension=opcache.so


-- System Information:
Debian Release: 7.8
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages php5-common depends on:
ii  libc6   2.13-38+deb7u8
ii  lsof4.86+dfsg-1
ii  psmisc  22.19-1+deb7u1
ii  sed 4.2.1-10
ii  ucf 3.0025+nmu3

php5-common recommends no packages.

Versions of packages php5-common suggests:
pn  php5-user-cache  

Versions of packages php5-cli depends on:
ii  libbz2-1.0   1.0.6-4
ii  libc62.13-38+deb7u8
ii  libcomerr2   1.42.5-1.1+deb7u1
ii  libdb5.1 5.1.29-5
ii  libedit2 2.11-20080614-5
ii  libgssapi-krb5-2 1.10.1+dfsg-5+deb7u3
ii  libk5crypto3 1.10.1+dfsg-5+deb7u3
ii  libkrb5-31.10.1+dfsg-5+deb7u3
ii  libmagic15.11-2+deb7u8
ii  libonig2 5.9.1-1
ii  libqdbm141.8.78-2
ii  libssl1.0.0  1.0.1e-2+deb7u16
ii  libxml2  2.8.0+dfsg1-7+wheezy4
ii  mime-support 3.52-1+deb7u1
ii  php5-common [php5-json]  5.6.7-1~dotdeb.2
ii  tzdata   2015b-0wheezy1
ii  ucf  3.0025+nmu3
ii  zlib1g   1:1.2.7.dfsg-13

Versions of packages php5-cli recommends:
ii  php5-readline  5.6.7-1~dotdeb.2

Versions of packages php5-cli suggests:
ii  php-pear  5.6.7-1~dotdeb.2

Versions of packages php5-fpm depends on:
ii  dpkg 1.16.16
ii  libbz2-1.0   1.0.6-4
ii  libc62.13-38+deb7u8
ii  libcomerr2   1.42.5-1.1+deb7u1
ii  libdb5.1 5.1.29-5
ii  libgssapi-krb5-2 1.10.1+dfsg-5+deb7u3
ii  libk5crypto3 1.10.1+dfsg-5+deb7u3
ii  libkrb5-31.10.1+dfsg-5+deb7u3
ii  libmagic15.11-2+deb7u8
ii  libonig2 5.9.1-1
ii  libqdbm141.8.78-2
ii  libssl1.0.0  1.0.1e-2+deb7u16
ii  libxml2  2.8.0+dfsg1-7+wheezy4
ii  mime-support 3.52-1+deb7u1
ii  php5-cli 5.6.7-1~dotdeb.2
ii  php5-common [php5-json]  5.6.7-1~dotdeb.2
ii  tzdata   2015b-0wheezy1
ii  ucf  3.0025+

Bug#801831: marked as done (php5-fpm reload fails if there are "too many" pools)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #801831,
regarding php5-fpm reload fails if there are "too many" pools
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.)


-- 
801831: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801831
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-fpm
Version: 5.4.45-0+deb7u1 Konsole output

Hi,

php5-fpm reload fails if there are too many pools defined. There is no
upper limit on pool number, but if the daemon receives a SIGUSR2, the
current socket names are written into environment variable (to
re-acquire later), then execve() is called. With all the unix domain
sockets' paths in the env, execve fails with E2BIG, and php5-fpm exits.

I have tried to raise max stack size, as according to man 2 execve, max
env size is  min(0.25*RLIMIT_STACK, 32 page), but the problem remains,
as upper limit for one env string is 32 pages.

In our system, we tried to use fpm with 6k on-demand pools (most of our
websites are "should exist but no one will ever open it").

PHP should consider sending only FD numbers. If 4/8 bytes are used
instead of paths and IPs, 16k/33k FDs would be the limit (assuming 4k
pagesize), which wouldn't depend on path lengths; socket types and infos
could be acquired after execve. (And we could document it as a
limitation)  Alternatively, before execve, php5-fpm could write this
information into a tempfile, pass the tempfile's path as command line
argument with the execve,  then use that file after reload.

The bug is found in Wheezy, but Jessie should be affected, too.
root@php05:~# uname -a
Linux php05 3.2.0-4-amd64 #1 SMP Debian 3.2.68-1+deb7u4 x86_64 GNU/Linux
root@php05:~# lsb_release -d
Description:Debian GNU/Linux 7.9 (wheezy)

--
GALAMBOS Daniel
--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm

Dear submitter,

as the package php5 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/841781

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)--- End Message ---

Bug#799136: marked as done (php5: php soap http client: error fetching http body)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #799136,
regarding php5: php soap http client: error fetching http body
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.)


-- 
799136: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799136
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-common
Version: 5.6.13+dfsg-0+deb8u1
Severity: normal
Tags: upstream

Php soap http client can not receive http server responses
where the headers are not separated by spaces with their values,
for example:

  HTTP/1.1 200 OK
  Content-Type:application/soap+xml; charset=utf-8
  Connection:close
  Content-Length:971


Error message example: 
  "Error Fetching http body, No Content-Length,
   connection closed or chunked data"

The source of the problem is a calls of get_http_header_value()
function in which a names of the expected headers are listed
with a space after the colon, for example:

  content-type = get_http_header_value(http_headers,"Content-Type: ");
 -^-

-- Package-specific info:
 Additional PHP 5 information 

 PHP 5 SAPI (php5query -S): 
cli
apache2

 PHP 5 Extensions (php5query -M -v): 
json (Enabled for cli by maintainer script)
json (Enabled for apache2 by maintainer script)
mcrypt (Enabled for cli by maintainer script)
mcrypt (Enabled for apache2 by maintainer script)
gd (Enabled for cli by maintainer script)
gd (Enabled for apache2 by maintainer script)
pdo_pgsql (Enabled for cli by maintainer script)
pdo_pgsql (Enabled for apache2 by maintainer script)
mysqli (Enabled for cli by maintainer script)
mysqli (Enabled for apache2 by maintainer script)
mysql (Enabled for cli by maintainer script)
mysql (Enabled for apache2 by maintainer script)
intl (Enabled for cli by maintainer script)
intl (Enabled for apache2 by maintainer script)
curl (Enabled for cli by maintainer script)
curl (Enabled for apache2 by maintainer script)
pdo_mysql (Enabled for cli by maintainer script)
pdo_mysql (Enabled for apache2 by maintainer script)
memcache (Enabled for cli by local administrator)
memcache (Enabled for apache2 by local administrator)
pdo (Enabled for cli by maintainer script)
pdo (Enabled for apache2 by maintainer script)
pgsql (Enabled for cli by maintainer script)
pgsql (Enabled for apache2 by maintainer script)
opcache (Enabled for cli by maintainer script)
opcache (Enabled for apache2 by maintainer script)

 Configuration files: 
 /etc/php5/mods-available/pdo.ini 
extension=pdo.so

 /etc/php5/mods-available/opcache.ini 
zend_extension=opcache.so


-- System Information:
Debian Release: 8.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (50, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.1.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages php5 depends on:
ii  libapache2-mod-php5  5.6.13+dfsg-0+deb8u1
ii  php5-common  5.6.13+dfsg-0+deb8u1

php5 recommends no packages.

php5 suggests no packages.

Versions of packages php5-common depends on:
ii  libc6   2.19-18+deb8u1
ii  lsof4.86+dfsg-1
ii  psmisc  22.21-2
ii  sed 4.2.2-4+b1
ii  ucf 3.0030

Versions of packages php5-common suggests:
pn  php5-user-cache  
--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm

Dear submitter,

as the package php5 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/841781

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)--- End Message ---

Bug#797799: marked as done (php5-mysqlnd: (Upstream Bug #68344): MySQLi does not provide way to disable peer certificate validation)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #797799,
regarding php5-mysqlnd: (Upstream Bug #68344): MySQLi does not provide way to 
disable peer certificate validation
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.)


-- 
797799: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797799
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-mysqlnd
Version: 5.6.12+dfsg-0+deb8u1
Severity: important
Tags: security upstream patch

https://bugs.php.net/bug.php?id=68344

Description:

When the MySQLi extension is compiled against mysqlnd there is no method to 
disable peer_name validation. Since MySQL 5.6 now enables peer_name validation 
by DEFAULT those of us connecting to servers with self-signed certs via SSL are 
no longer able too.

I have tried to signal the default ssl stream context to disable peer_name 
validation but mysqli extension will NOT honor it.

If the remote-server's name does not match the name you are connecting to (as 
in, for example, a mysql cluster and connecting to a single node directly) you 
will not be able to connect at all in any way shape or form with mysqli.  -- 
The old mysql extension is not effected by this change as it honors the my.cnf 
mysql client's validation settings.

Test script:
---
 array(
'peer_name' => 'generic-server',
'verify_peer' => FALSE,
'verify_peer_name' => FALSE,
'allow_self_signed' => TRUE,
),
));

 $mysqli = mysqli_init();
 
mysqli_ssl_set($mysqli,"/etc/pki/mysql/client.key","/etc/pki/mysql/client.crt","/etc/pki/mysql/ca-cert.pem",NULL,NULL);
 $conn = 
mysqli_real_connect($mysqli,'dbserver.local','test','test1234','',NULL,'',MYSQLI_CLIENT_SSL);
 var_dump($conn);

?>


Expected result:

I expect to be able to disable peer_name validation for those situations were 
the certificate name cant possibly be verified (ie: self-signed certs) and be 
able to connect to the mysql server.

Actual result:
--
MySQLi will NOT connect to mysql server and throws 4 warnings:

Warning: mysqli_real_connect(): Peer certificate CN=`generic-server' did not 
match expected CN=`dbserver.local'
Warning: mysqli_real_connect(): Cannot connect to MySQL by using SSL
Warning: mysqli_real_connect(): [2002]  (trying to connect via 
tcp://dbserver.local:3306)
Warning: mysqli_real_connect(): (HY000/2002):

Patch:

; obey few default context options
; https://bugs.php.net/bug.php?id=68344
diff -urbB php-5.6.12/ext/mysqlnd/mysqlnd_net.c 
php-5.6.12/ext/mysqlnd/mysqlnd_net.c
--- php-5.6.12/ext/mysqlnd/mysqlnd_net.c2015-08-06 09:55:57.0 
+0200
+++ php-5.6.12/ext/mysqlnd/mysqlnd_net.c2015-08-10 13:25:30.187912101 
+0200
@@ -29,6 +29,7 @@
 #include "mysqlnd_ext_plugin.h"
 #include "php_network.h"
 #include "zend_ini.h"
+#include "ext/standard/file.h"
 #ifdef MYSQLND_COMPRESSION_ENABLED
 #include 
 #endif
@@ -868,6 +868,21 @@ MYSQLND_METHOD(mysqlnd_net, enable_ssl)(
DBG_RETURN(FAIL);
}
 
+   if (FG(default_context)) {
+   zval **tmpzval = NULL;
+   int i = 0;
+   /* copy values from default stream settings */
+   char *opts[] = { "allow_self_signed", "cafile", "capath", 
"ciphers", "CN_match",
+   "disable_compression", "local_cert", "local_pk", 
"no_ticket", "passphrase",
+   "peer_fingerprint", "peer_name", "SNI_enabled", 
"SNI_server_certs", "SNI_server_name",
+   "verify_depth", "verify_peer", "verify_peer_name", NULL 
};
+   while (opts[i]) {
+   if (php_stream_context_get_option(FG(default_context), 
"ssl", opts[i], &tmpzval) == SUCCESS)
+   php_stream_context_set_option(context, "ssl", 
opts[i], *tmpzval);
+   i++;
+   }
+   }
+
if (net->data->options.ssl_key) {
zval key_zval;
ZVAL_STRING(&key_zval, net->data->options.ssl_key, 0);

-- Package-specific info:
 Additional PHP 5 information 

 PHP 5 SAPI (php5query -S): 
fpm
cli

 PHP 5 Extensions (php5query -M -v): 
pdo (Enabled for fpm by maintainer script)
pdo (Enabled for cli by maintainer script)
readline (Enabled for fpm by maintainer script)
readline (Enabled for cli by maintainer script)
pdo_mysql (Enabled for fpm by maintainer script)
pdo_mysql (Enabled for cl

Bug#790841: marked as done (php5-odbc: Missing option to set timeout on login for odbc_pconnect/connect)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #790841,
regarding php5-odbc: Missing option to set timeout on login for 
odbc_pconnect/connect
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.)


-- 
790841: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790841
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-odbc
Version: 5.6.9+dfsg-1
Severity: minor
Tags: upstream

Dear Maintainer,

I was getting timeout on login for odbc_connect when connecting to SQL Server 
2000 + 2005,
usually to fix such an issue I set the login timeout during connect.

I was expecting to find something that could allow me to set login
timeout in php.ini,
or a timeout value in odbc.c like:
  SQLSetConnectOption(
conn->hdbc,
SQL_ATTR_LOGIN_TIMEOUT,//or maybe SQL_ATTR_CONNECTION_TIMEOUT
);

but I failed to find an option or a refernce on how I can modify the login
timeout.

the suggested solution on MSDN for such an error is to drop
odbc_connect/pconnect and switch to sqlsrv_connect[1].

As I understand odbc_setoption should be called after the login had been done,
otherwise I don't see how I can access the connection handle, before doing 
odbc_connect.


[1] 
-https://social.msdn.microsoft.com/forums/sqlserver/en-US/d24045a2-6a3d-42f8-8005-6c4a49c17ac4/timeout-expired

-- Package-specific info:
 Additional PHP 5 information 

 PHP 5 SAPI (php5query -S): 

 PHP 5 Extensions (php5query -M -v): 

 Configuration files: 
 /etc/php5/mods-available/odbc.ini 
extension=odbc.so

 /etc/php5/mods-available/pdo_odbc.ini 
extension=pdo_odbc.so


-- System Information:
Debian Release: 8.0
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.9-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages php5-odbc depends on:
ii  libc6  2.19-13
ii  libodbc1   2.3.1-3
ii  php5-common [phpapi-20131226]  5.6.9+dfsg-1
ii  ucf3.0030

php5-odbc recommends no packages.

php5-odbc suggests no packages.

Versions of packages php5-common depends on:
ii  libc6   2.19-13
ii  lsof4.86+dfsg-1
ii  psmisc  22.21-2
ii  sed 4.2.2-4+b1
ii  ucf 3.0030

Versions of packages php5-common suggests:
pn  php5-user-cache  

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm

Dear submitter,

as the package php5 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/841781

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)--- End Message ---

Bug#788060: marked as done (php5-common: /usr/lib/php5/sessionclean "arithmetic expression: expecting primary")

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #788060,
regarding php5-common: /usr/lib/php5/sessionclean "arithmetic expression: 
expecting primary"
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.)


-- 
788060: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788060
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-common
Version: 5.6.9+dfsg-0+deb8u1
Severity: normal
Tags: patch

I sent this to pkg-php-ma...@lists.alioth.debian.org on April, 28th:

  I upgraded wheezy to jessie and experienced administrative mails telling me:
/usr/lib/php5/sessionclean: 15: /usr/lib/php5/sessionclean:
arithmetic expression: expecting primary: "/60"
  I tried to understand the script and propose the attached patch.

Ondřej asked to file a bug and describe environment that led to this behaviour.
Well, nothing special as far as I see it: I run a simplistic PHP-enabled apache.
Please state which additional information I shall provide.

-- Package-specific info:
 Additional PHP 5 information 

 PHP 5 SAPI (php5query -S): 
cli
apache2

 PHP 5 Extensions (php5query -M -v): 
gd (Enabled for cli by maintainer script)
gd (Enabled for apache2 by maintainer script)
mysqli (Enabled for cli by maintainer script)
mysqli (Enabled for apache2 by maintainer script)
mysqlnd (Enabled for cli by maintainer script)
mysqlnd (Enabled for apache2 by maintainer script)
mcrypt (Enabled for cli by maintainer script)
mcrypt (Enabled for apache2 by maintainer script)
pdo_mysql (Enabled for cli by maintainer script)
pdo_mysql (Enabled for apache2 by maintainer script)
pdo (Enabled for cli by maintainer script)
pdo (Enabled for apache2 by maintainer script)
json (Enabled for cli by maintainer script)
json (Enabled for apache2 by maintainer script)
readline (Enabled for cli by maintainer script)
readline (Enabled for apache2 by maintainer script)
opcache (Enabled for cli by maintainer script)
opcache (Enabled for apache2 by maintainer script)
curl (Enabled for cli by maintainer script)
curl (Enabled for apache2 by maintainer script)
mysql (Enabled for cli by maintainer script)
mysql (Enabled for apache2 by maintainer script)

 Configuration files: 
 /etc/php5/mods-available/pdo.ini 
extension=pdo.so

 /etc/php5/mods-available/opcache.ini 
zend_extension=opcache.so


-- System Information:
Debian Release: 8.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF8, LC_CTYPE=de_DE.UTF8 (charmap=UTF-8) (ignored: LC_ALL 
set to de_DE.UTF8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages php5-common depends on:
ii  libc6   2.19-18
ii  lsof4.86+dfsg-1
ii  psmisc  22.21-2
ii  sed 4.2.2-4+b1
ii  ucf 3.0030

php5-common recommends no packages.

Versions of packages php5-common suggests:
pn  php5-user-cache  

Versions of packages php5-cli depends on:
ii  libbz2-1.01.0.6-7+b3
ii  libc6 2.19-18
ii  libcomerr21.42.12-1.1
ii  libdb5.3  5.3.28-9
ii  libedit2  3.1-20140620-2
ii  libgssapi-krb5-2  1.12.1+dfsg-19
ii  libk5crypto3  1.12.1+dfsg-19
ii  libkrb5-3 1.12.1+dfsg-19
ii  libmagic1 1:5.22+15-2
ii  libonig2  5.9.5-3.2
ii  libpcre3  2:8.35-3.3
ii  libqdbm14 1.8.78-5+b1
ii  libssl1.0.0   1.0.1k-3
ii  libxml2   2.9.1+dfsg1-5
ii  mime-support  3.58
ii  php5-json 1.3.6-1
ii  tzdata2015d-0+deb8u1
ii  ucf   3.0030
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages php5-cli recommends:
ii  php5-readline  5.6.9+dfsg-0+deb8u1

Versions of packages php5-cli suggests:
ii  php-pear  5.6.9+dfsg-0+deb8u1

Versions of packages libapache2-mod-php5 depends on:
ii  apache2 2.4.10-10
ii  apache2-bin [apache2-api-20120211]  2.4.10-10
ii  libbz2-1.0  1.0.6-7+b3
ii  libc6   2.19-18
ii  libcomerr2  1.42.12-1.1
ii  libdb5.35.3.28-9
ii  libgssapi-krb5-21.12.1+dfsg-19
ii  libk5crypto31.12.1+dfsg-19
ii  libkrb5-3   1.12.1+dfsg-19
ii  libmagic1   1:5.22+15-2
ii  libonig25.9.5-3.2
ii  libpcre32

Bug#789442: marked as done (php5-common: maxlifetime script may error. improvement.)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #789442,
regarding php5-common: maxlifetime script may error. improvement.
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.)


-- 
789442: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789442
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-common
Version: 5.4.41-0+deb7u1
Severity: wishlist

Dear Maintainer,


When running maxlifetime you could receive errors which are may or may not be 
considered bad. Such as:

# "/usr/lib/php5/maxlifetime"
No log handling enabled - turning on stderr logging
Undefined OBJECT-GROUP (diffServMIBMultiFieldClfrGroup): At line 2195 in 
/usr/share/mibs/ietf/IPSEC-SPD-MIB
Undefined OBJECT-GROUP (diffServMultiFieldClfrNextFree): At line 2157 in 
/usr/share/mibs/ietf/IPSEC-SPD-MIB
Undefined OBJECT-GROUP (diffServMIBMultiFieldClfrGroup): At line 2062 in 
/usr/share/mibs/ietf/IPSEC-SPD-MIB
Unlinked OID in IPATM-IPMC-MIB: marsMIB ::= { mib-2 57 }
Undefined identifier: mib-2 near line 18 of /usr/share/mibs/ietf/IPATM-IPMC-MIB
Bad operator (INTEGER): At line 73 in /usr/share/mibs/ietf/SNMPv2-PDU
Expected "::=" (RFC5644): At line 493 in 
/usr/share/mibs/iana/IANA-IPPM-METRICS-REGISTRY-MIB
Expected "{" (EOF): At line 651 in 
/usr/share/mibs/iana/IANA-IPPM-METRICS-REGISTRY-MIB
Bad object identifier: At line 651 in 
/usr/share/mibs/iana/IANA-IPPM-METRICS-REGISTRY-MIB
Bad parse of OBJECT-IDENTITY: At line 651 in 
/usr/share/mibs/iana/IANA-IPPM-METRICS-REGISTRY-MIB
24
#

An easy fix -- add the -n param to php5.

8c8
<   cur=$(php5 -c /etc/php5/${sapi}/php.ini -d 
"error_reporting='~E_ALL'" -r 'print ini_get("session.gc_maxlifetime");')
---
>   cur=$(php5 -n -c /etc/php5/${sapi}/php.ini -d 
> "error_reporting='~E_ALL'" -r 'print ini_get("session.gc_maxlifetime");')

This will likely insulate these scripts from other possible oddness in the 
future as well.




-- System Information:
Debian Release: 7.5
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages php5-common depends on:
ii  dpkg1.16.15
ii  libc6   2.13-38+deb7u7
ii  lsof4.86+dfsg-1
ii  psmisc  22.19-1+deb7u1
ii  sed 4.2.1-10
ii  ucf 3.0025+nmu3

php5-common recommends no packages.

php5-common suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm

Dear submitter,

as the package php5 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/841781

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)--- End Message ---

Bug#811130: marked as done (php5: [kfreebsd] uploaded files have gid=root)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #811130,
regarding php5: [kfreebsd] uploaded files have gid=root
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.)


-- 
811130: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811130
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:php5
Version: 5.4.45-0+deb7u2
Severity: important
User: debian-...@lists.debian.org
Usertags: kfreebsd
X-Debbugs-Cc: debian-...@lists.debian.org

(Followup to https://lists.debian.org/debian-bsd/2016/01/msg00021.html)

This turns out to be some bug or odd behaviour of PHP when handling file
uploads on kfreebsd.  Here's a simple testcase:









Submitting the web form, PHP writes the uploaded file to /tmp initially,
having a random filename, and moves it to ".foo" in the web document
root at request of the PHP script.

The PHP script is *supposed* to run non-privileged for obvious
reasons.  suexec.log suggests I set that up right:

uid: (1046/foo) gid: (1045/foo) cmd: php-fcgi-starter

And executing  confirms that is generally the
case:

uid=1046(foo) gid=1045(foo) groups=1045(foo) 

But `stat .foo` shows the uploaded file having gid=0 instead, something
not possible to do if you have dropped privileges:

  File: `.foo'
  Size: 5   Blocks: 9  IO Block: 4096   regular file
Device: 735ae718h/1935337240d   Inode: 238962  Links: 1
Access: (0644/-rw-r--r--)  Uid: ( 1046/foo)   Gid: (0/root)
Access: 2016-01-15 22:00:02.555410397 + ^^
Modify: 2016-01-15 22:00:02.555410397 +   wrong gid!
Change: 2016-01-15 22:00:02.555410397 +
 Birth: -

I couldn't repeat this on a GNU/Linux machine.  Is PHP maybe not
dropping privileges properly on GNU/kFreeBSD?  (setgid,setegid issue?)
Havne't yet checked it affects regular FreeBSD also.

There seems nothing special about my /tmp:  mode 1777/drwxrwxrwt.
That end the web document root are on ZFS.

Thanks.
Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm

Dear submitter,

as the package php5 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/841781

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)--- End Message ---

Bug#789702: marked as done (php5: SOAP when throwing exception server side causes Segmentation Fault)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #789702,
regarding php5: SOAP when throwing exception server side causes Segmentation 
Fault
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.)


-- 
789702: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789702
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libapache2-mod-php5
Version: 5.6.9+dfsg-0+deb8u1
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
A client application connection to a SOAP server running this version of PHP on 
Debian Jessie was randomly getting the following error
"Error Fetching http headers".  This caused major issues with our client 
application.

After further investigation I looked at the apache error logs and saw the 
following error every time this happened.(a lot)
[Tue Jun 23 08:28:57.841494 2015] [core:notice] [pid 4038] AH00052: child pid 
4085 exit signal Segmentation fault (11)

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I triangulated this issue to when the SOAP server side running this version of 
PHP throws an exception, that is causing this Segmentation fault to occur.  I 
modified my SOAP server side script for now
to no longer "throw" any exceptions to work around this.

   * What was the outcome of this action?
I am no longer getting Segmentation Faults in the scenarios where I knew I was 
getting them for sure prior.

   * What outcome did you expect instead?
I didn't expect PHP to Segmentation Fault when "throwing" and exception over 
SOAP.

I tried getting a coredump of this, but wasn't able to succefully do that.  I 
did have apache running with gdb, here is a copy/paste of what I saw in there
when I triggered this Segfault.


(gdb) run -X
The program being debugged has been started already.
Start it from the beginning? (y or n) n
Program not restarted.
(gdb) backtrace
#0  0x73c9bd5f in instanceof_function_ex () from 
/usr/lib/apache2/modules/libphp5.so
#1  0x73b47597 in ?? () from /usr/lib/apache2/modules/libphp5.so
#2  0x73ca085c in zend_error_noreturn () from 
/usr/lib/apache2/modules/libphp5.so
#3  0x73c48ad8 in php_default_post_reader () from 
/usr/lib/apache2/modules/libphp5.so
#4  0x73c44ea2 in sapi_activate () from 
/usr/lib/apache2/modules/libphp5.so
#5  0x73c3ba0a in php_request_startup () from 
/usr/lib/apache2/modules/libphp5.so
#6  0x73d5021a in ?? () from /usr/lib/apache2/modules/libphp5.so
#7  0x555abf20 in ap_run_handler ()
#8  0x555ac469 in ap_invoke_handler ()
#9  0x555c2302 in ap_process_async_request ()
#10 0x555c24a0 in ap_process_request ()
#11 0x555beda2 in ?? ()
#12 0x555b5790 in ap_run_process_connection ()
#13 0x746727ba in ?? () from /usr/lib/apache2/modules/mod_mpm_prefork.so
#14 0x746729c7 in ?? () from /usr/lib/apache2/modules/mod_mpm_prefork.so
#15 0x7467370d in ?? () from /usr/lib/apache2/modules/mod_mpm_prefork.so
#16 0x55591cae in ap_run_mpm ()
#17 0x5558b1f3 in main ()
(gdb) backtrace full
#0  0x73c9bd5f in instanceof_function_ex () from 
/usr/lib/apache2/modules/libphp5.so
No symbol table info available.
#1  0x73b47597 in ?? () from /usr/lib/apache2/modules/libphp5.so
No symbol table info available.
#2  0x73ca085c in zend_error_noreturn () from 
/usr/lib/apache2/modules/libphp5.so
No symbol table info available.
#3  0x73c48ad8 in php_default_post_reader () from 
/usr/lib/apache2/modules/libphp5.so
No symbol table info available.
#4  0x73c44ea2 in sapi_activate () from 
/usr/lib/apache2/modules/libphp5.so
No symbol table info available.
#5  0x73c3ba0a in php_request_startup () from 
/usr/lib/apache2/modules/libphp5.so
No symbol table info available.
#6  0x73d5021a in ?? () from /usr/lib/apache2/modules/libphp5.so
No symbol table info available.
#7  0x555abf20 in ap_run_handler ()
No symbol table info available.
#8  0x555ac469 in ap_invoke_handler ()
No symbol table info available.
#9  0x555c2302 in ap_process_async_request ()
No symbol table info available.
#10 0x555c24a0 in ap_process_request ()
No symbol table info available.
#11 0x555beda2 in ?? ()
No symbol table info available.
#12 0x555b5790 in ap_run_process_connection ()
No symbol table info availa

Bug#803260: marked as done (php5: setcookie() function can no longer be used with value as specified in PHP doc)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #803260,
regarding php5: setcookie() function can no longer be used with value as 
specified in PHP doc
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.)


-- 
803260: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803260
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-common
Version: 5.6.14+dfsg-0+deb8u1
Severity: important
Tags: upstream

Dear Maintainer,

Since the application of those versions (security updates)

libapache2-mod-php5 5.6.14+dfsg-0+deb8u1
php5 5.6.14+dfsg-0+deb8u1
php5-cli 5.6.14+dfsg-0+deb8u1
php5-common 5.6.14+dfsg-0+deb8u1
php5-curl 5.6.14+dfsg-0+deb8u1
php5-gd 5.6.14+dfsg-0+deb8u1
php5-mcrypt 5.6.14+dfsg-0+deb8u1
php5-mysql 5.6.14+dfsg-0+deb8u1
php5-readline 5.6.14+dfsg-0+deb8u1

The setcookie() function no longer works when called without value parameter 
According to http://php.net/manual/en/function.setcookie.pha, only the name is 
required. It worked like this before  php5 5.6.14+dfsg-0+deb8u1
 
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

-- Package-specific info:
 Additional PHP 5 information 

 PHP 5 SAPI (php5query -S): 
apache2
cli

 PHP 5 Extensions (php5query -M -v): 
mcrypt (Enabled for apache2 by maintainer script)
mcrypt (Enabled for cli by maintainer script)
pdo (Enabled for apache2 by maintainer script)
pdo (Enabled for cli by maintainer script)
mysqli (Enabled for apache2 by maintainer script)
mysqli (Enabled for cli by maintainer script)
gd (Enabled for apache2 by maintainer script)
gd (Enabled for cli by maintainer script)
imagick (Enabled for apache2 by maintainer script)
imagick (Enabled for cli by maintainer script)
pdo_mysql (Enabled for apache2 by maintainer script)
pdo_mysql (Enabled for cli by maintainer script)
readline (Enabled for apache2 by maintainer script)
readline (Enabled for cli by maintainer script)
curl (Enabled for apache2 by maintainer script)
curl (Enabled for cli by maintainer script)
opcache (Enabled for apache2 by maintainer script)
opcache (Enabled for cli by maintainer script)
mysql (Enabled for apache2 by maintainer script)
mysql (Enabled for cli by maintainer script)
json (Enabled for apache2 by maintainer script)
json (Enabled for cli by maintainer script)

 Configuration files: 
 /etc/php5/mods-available/pdo.ini 
extension=pdo.so

 /etc/php5/mods-available/opcache.ini 
zend_extension=opcache.so


-- System Information:
Debian Release: 8.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages php5 depends on:
ii  libapache2-mod-php5  5.6.14+dfsg-0+deb8u1
ii  php5-common  5.6.14+dfsg-0+deb8u1

php5 recommends no packages.

php5 suggests no packages.

Versions of packages php5-common depends on:
ii  libc6   2.19-18+deb8u1
ii  lsof4.86+dfsg-1
ii  psmisc  22.21-2
ii  sed 4.2.2-4+b1
ii  ucf 3.0030

Versions of packages php5-common suggests:
pn  php5-user-cache  

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm

Dear submitter,

as the package php5 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/841781

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)--- End Message ---

Bug#795572: marked as done (getallheaders for php-fpm patch ignores Content-Type and Content-Length headers)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #795572,
regarding getallheaders for php-fpm patch ignores Content-Type and 
Content-Length headers
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.)


-- 
795572: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795572
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-fpm
Version: 5.6.9+dfsg-0+deb8u1
Severity: normal

The php5 package in Debian carries a patch to add the getallheaders
function to FastCGI (fpm) build. This function is not supported for this
build upstream at all. See
debian/patches/0046-getallheaders-for-php-fpm-62596.patch

This patch works for "normal" headers which are translated to HTTP_XXX
environment variables by PHP, but it does not work for the Content-Type
and Content-Length headers. There is code in the patch that is supposed
to cover this case, but it does not work. The two headers are missing
from the array returned by getallheaders.

Here is sample code to demonstrate the issue.

# cat getallheaders.php


$ POST -U -H "X-DUMMY: my test header" -c text/xml 
http://myserver/getallheaders.php
Please enter content (text/xml) to be POSTed:
adsflkj öalksjdf ölkjasdf
POST https://ubol.ch/getallheaders.php
User-Agent: lwp-request/6.09 libwww-perl/6.13
Content-Length: 28
Content-Type: text/xml
X-DUMMY: my test header

array(5) {
  ["Te"]=>
  string(18) "deflate,gzip;q=0.3"
  ["Connection"]=>
  string(9) "TE, close"
  ["Host"]=>
  string(7) "myserver"
  ["User-Agent"]=>
  string(33) "lwp-request/6.09 libwww-perl/6.13"
  ["X-Dummy"]=>
  string(14) "my test header"
}
array(37) {
[...]
  ["FCGI_ROLE"]=>
  string(9) "RESPONDER"
  ["SCRIPT_URL"]=>
  string(18) "/getallheaders.php"
  ["SCRIPT_URI"]=>
  string(33) "http://myserver/getallheaders.php";
  ["HTTP_TE"]=>
  string(18) "deflate,gzip;q=0.3"
  ["HTTP_CONNECTION"]=>
  string(9) "TE, close"
  ["HTTP_HOST"]=>
  string(7) "ubol.ch"
  ["HTTP_USER_AGENT"]=>
  string(33) "lwp-request/6.09 libwww-perl/6.13"
  ["CONTENT_LENGTH"]=>
  string(2) "28"
  ["CONTENT_TYPE"]=>
  string(8) "text/xml"
  ["HTTP_X_DUMMY"]=>
  string(14) "my test header"
[...]
}

As you can see, the Content-Type and Content-Length headers are being sent and
also end up in the $_SERVER array, but they are not returned by getallheaders.

To be honest I'm not sure if it's a good idea to carry a patch which
changes upstream behavior like this. While it solves the issue for code
that unconditionally calls getallheaders it breaks code (like in my
case) which checks for getallheaders and only uses the function if it
exists. My code was then broken because the getallheaders implementation
was not the same as when running as an Apache module.

I found and investigated this buug on a jessie system, but the patch in
question is the same in the current unstable version of PHP.

Gaudenz
--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm

Dear submitter,

as the package php5 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/841781

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)--- End Message ---

Bug#797350: marked as done (Improve the documentation on module management)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #752100,
regarding Improve the documentation on module management
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.)


-- 
752100: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752100
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libapache2-mod-php5
Version: 5.6.12+dfsg-0+deb8u1
Severity: normal

After installing the update all modules where re-enabled. But updates should 
never change standing configuration!


-- Package-specific info:
 Additional PHP 5 information 

 PHP 5 SAPI (php5query -S): 
cli
apache2

 PHP 5 Extensions (php5query -M -v): 
No module matches mcrypt.ini
No module matches mcrypt.ini
imagick (Enabled for cli by maintainer script)
imagick (Enabled for apache2 by maintainer script)
No module matches pdo_mysql.ini
No module matches pdo_mysql.ini
curl (Enabled for cli by maintainer script)
curl (Enabled for apache2 by maintainer script)
pdo_mysql (Enabled for cli by maintainer script)
pdo_mysql (Enabled for apache2 by maintainer script)
intl (Enabled for cli by maintainer script)
intl (Enabled for apache2 by maintainer script)
No module matches raphf.ini
No module matches raphf.ini
json (Enabled for cli by maintainer script)
json (Enabled for apache2 by maintainer script)
mysqlnd (Enabled for cli by maintainer script)
mysqlnd (Enabled for apache2 by maintainer script)
pdo (Enabled for cli by maintainer script)
pdo (Enabled for apache2 by maintainer script)
No module matches pdo_sqlite.ini
No module matches pdo_sqlite.ini
gd (Enabled for cli by maintainer script)
gd (Enabled for apache2 by maintainer script)
No module matches gd.ini
No module matches gd.ini
No module matches pdo.ini
No module matches pdo.ini
No module matches intl.ini
No module matches intl.ini
No module matches imagick.ini
No module matches imagick.ini
opcache (Enabled for cli by maintainer script)
opcache (Enabled for apache2 by maintainer script)
mysqli (Enabled for cli by maintainer script)
mysqli (Enabled for apache2 by maintainer script)
readline (Enabled for cli by maintainer script)
No module matches readline (Disabled for apache2 by local administrator)
No module matches json.ini
No module matches json.ini
pdo_sqlite (Enabled for cli by maintainer script)
pdo_sqlite (Enabled for apache2 by maintainer script)
No module matches propro
No module matches propro
No module matches mysqli.ini
No module matches mysqli.ini
No module matches propro.ini
No module matches propro.ini
No module matches curl.ini
No module matches curl.ini
mcrypt (Enabled for cli by maintainer script)
mcrypt (Enabled for apache2 by maintainer script)
No module matches opcache.ini
No module matches opcache.ini
sqlite3 (Enabled for cli by maintainer script)
sqlite3 (Enabled for apache2 by maintainer script)
No module matches raphf
No module matches raphf
No module matches pecl-http
No module matches pecl-http
No module matches pecl-http.ini
No module matches pecl-http.ini
No module matches mysql.ini
No module matches mysql.ini
mysql (Enabled for cli by maintainer script)
mysql (Enabled for apache2 by maintainer script)
No module matches sqlite3.ini
No module matches sqlite3.ini

 Configuration files: 
[PHP]
user_ini.filename = ".htphp"
user_ini.cache_ttl = 0
engine = On
short_open_tag = Off
asp_tags = Off
precision = 14
output_buffering = 4096
zlib.output_compression = Off
implicit_flush = Off
unserialize_callback_func =
serialize_precision = 17
disable_functions = 
pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,
disable_classes =
zend.enable_gc = On
expose_php = On
max_execution_time = 30
max_input_time = 60
memory_limit = 128M
error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT & ~E_NOTICE
display_errors = Off
display_startup_errors = Off
log_errors = On
log_errors_max_len = 1024
ignore_repeated_errors = Off
ignore_repeated_source = Off
report_memleaks = On
track_errors = Off
html_errors = Off
variables_order = "GPCS"
request_order = "GP"
register_argc_argv = Off
auto_globals_jit = On
post_max_size = 50M
auto_prepend_file =
auto_append_file =
default_mimetype = "text/html"
default_charset =
doc_root =
user_dir =
enable_dl = Off
file_uploads = On
upload_max_filesiz

Bug#815794: marked as done (Broken symlink: /usr/lib/php5/build/ltmain.sh)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #815794,
regarding Broken symlink: /usr/lib/php5/build/ltmain.sh
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.)


-- 
815794: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815794
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-dev
Version: 5.6.17+dfsg-3

The file /usr/lib/php5/build/ltmain.sh is symlinked to
../../../share/libtool/config/ltmain.sh, which does not exist in the
libtool package as of version 2.4.6-0.1 (it was present in 2.4.2-1.11).
The new path seems to be /usr/share/libtool/build-aux/ltmain.sh.
--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm

Dear submitter,

as the package php5 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/841781

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)--- End Message ---

Bug#783246: marked as done (php5en(dis)mod: mandatory space between semicolon and priority key)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #783246,
regarding php5en(dis)mod: mandatory space between semicolon and priority key
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.)


-- 
783246: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783246
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-common
Version: 5.5.9+dfsg-1ubuntu4.9
Severity: wishlist
Tags: patch

Dear Maintainer,

When menaging infrastructure using software such as Puppet Auegas tools would
handle *.ini files. Augeas PHP lens does not allow space(s) at the beginning 
of comments. In combination with mandatory space after semicolon as defined 
in regex in function php5-helper::get_prioroity it makes automation impossible. 
 

If priority in extension.ini is set as: ;priority=30 setting will be disregarded
and default priority will be used insetad.

Regardles of space between semicolon eg ;priority=30/; priority=30 and priority
key defined priroity should be used resulgint in creating 
/etc/sapi/conf.d/30-exension.ini

Following regex will match both ;priority=30 and ; priority=30
priority=$(sed -ne "s/^;[ ]\?priority=\([0-9]\+\)$/\\1/p" $source_ini)

Regards,
Goran Miskovic

-- Package-specific info:
 Additional PHP 5 information 

 PHP 5 SAPI (php5query -S): 
fpm
cli

 PHP 5 Extensions (php5query -M -v): 
solr (Enabled for fpm by local administrator)
solr (Enabled for cli by local administrator)
opcache (Enabled for fpm by maintainer script)
opcache (Enabled for cli by maintainer script)
mysql (Enabled for fpm by maintainer script)
mysql (Enabled for cli by maintainer script)
pdo (Enabled for fpm by maintainer script)
pdo (Enabled for cli by maintainer script)
xmlrpc (Enabled for fpm by maintainer script)
xmlrpc (Enabled for cli by maintainer script)
memcache (Enabled for fpm by maintainer script)
memcache (Enabled for cli by local administrator)
json (Enabled for fpm by maintainer script)
json (Enabled for cli by maintainer script)
tidy (Enabled for fpm by maintainer script)
tidy (Enabled for cli by maintainer script)
gd (Enabled for fpm by maintainer script)
gd (Enabled for cli by maintainer script)
mysqli (Enabled for fpm by maintainer script)
mysqli (Enabled for cli by maintainer script)
readline (Enabled for fpm by maintainer script)
readline (Enabled for cli by maintainer script)
imagick (Enabled for fpm by local administrator)
imagick (Enabled for cli by local administrator)
pdo_mysql (Enabled for fpm by maintainer script)
pdo_mysql (Enabled for cli by maintainer script)
curl (Enabled for fpm by maintainer script)
curl (Enabled for cli by maintainer script)

 Configuration files: 
 /etc/php5/mods-available/pdo.ini 
extension=pdo.so

 /etc/php5/mods-available/opcache.ini 
zend_extension=opcache.so


-- System Information:
Debian Release: jessie/sid
  APT prefers trusty-updates
  APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 'trusty')
Architecture: amd64 (x86_64)

Kernel: Linux 3.13.0-49-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages php5-common depends on:
ii  libc6  2.19-0ubuntu6.6
ii  lsof   4.86+dfsg-1ubuntu2
ii  php5-json  1.3.2-2build1
ii  psmisc 22.20-1ubuntu2
ii  sed4.2.2-4ubuntu1
ii  ucf3.0027+nmu1

php5-common recommends no packages.

Versions of packages php5-common suggests:
pn  php5-user-cache  

Versions of packages php5-cli depends on:
ii  libbz2-1.01.0.6-5
ii  libc6 2.19-0ubuntu6.6
ii  libdb5.3  5.3.28-3ubuntu3
ii  libedit2  3.1-20130712-2
ii  libmagic1 1:5.14-2ubuntu3.3
ii  libpcre3  1:8.31-2ubuntu2
ii  libssl1.0.0   1.0.1f-1ubuntu2.11
ii  libxml2   2.9.1+dfsg1-3ubuntu4.4
ii  mime-support  3.54ubuntu1.1
ii  tzdata2015c-0ubuntu0.14.04
ii  ucf   3.0027+nmu1
ii  zlib1g1:1.2.8.dfsg-1ubuntu1

Versions of packages php5-cli recommends:
ii  php5-readline  5.5.9+dfsg-1ubuntu4.9

Versions of packages php5-cli suggests:
ii  php-pear  5.5.9+dfsg-1ubuntu4.9

Versions of packages php5-fpm depends on:
ii  dpkg1.17.5ubuntu5.4
ii  libbz2-1.0  1.0.6-5
ii  libc6   2.19-0ubuntu6.6
ii  libdb5.35.3.28-3ubuntu3
ii  libmagic1   1:5.14-2ubuntu3.3
ii  libpcre31:8.31-2ubuntu2
ii  libssl1.0.0 1.0.1f-1ubuntu2.11
ii  libsystemd-daemon0  204-5ubuntu20.11
ii  libxml2

Bug#799851: marked as done (libapache2-mod-php5filter: HTTP_RAW_POST_DATA mangled when bin data is sent in HTTP POST request)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #799851,
regarding libapache2-mod-php5filter: HTTP_RAW_POST_DATA mangled when bin data 
is sent in HTTP POST request
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.)


-- 
799851: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799851
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: libapache2-mod-php5filter
Version: 5.6.13+dfsg-0+deb8u1
Severity: important

Dear Maintainer,

When using Fusion Inventory plugin over GLPI 0.84 (from debian repo), we
have hit a bug. It happens when the agent tries to send a huge (30k) XML
chunk, xlib compressed over HTTP POST.

The PHP code in Fusion Inventory uses $HTTP_RAW_POST_DATA. We have found
that the binary blob in the POST is around 13kB but the PHP var contains
way less data, like 120 bytes or 1.5 kB in other situations.

Tried php://input : same size as in $HTTP_RAW_POST_DATA.

In apache2 log, shitty things happens :
172.16.2.120 - - [23/Sep/2015:10:50:40 +0200] "POST 
/glpi/plugins/fusioninventory/ HTTP/1.1" 200 0 "-" 
"FusionInventory-Agent_v2.3.16"
172.16.2.120 - - [23/Sep/2015:10:50:40 +0200] 
"\x9cv\xdej\xc0\xe3e\xc2H\xc5\x99\x0e" 400 0 "-" "-"


With Wireshark, we have found that on the HTTP connection, there is 2
replies on the Fusion Inventory single request (an HTTP/200 from PHP, a
HTTP 400 from apache).

Everything starts to work normally when replacing
libapache2-mod-php5filter with libapache2-mod-php5.

The expected behavior is to have $HTTP_RAW_POST_DATA or php://input
reflecting the whole binary data sent over the wire.

You could check in atttachement the tcp tchat between fusion Inventory
agent and theh GLPI server. Taken from Wireshark / follow TCP stream /
Save as... The agent talks first with HTTP POSTING a "big" blob, then
server replies HTTP/1.1 200 OK with another zlib compressed blob and
a second reply (without any request from the agent) is sent by apache
(HTTP 400).


-- Package-specific info:
 Additional PHP 5 information 

 PHP 5 SAPI (php5query -S): 
cli
apache2filter

 PHP 5 Extensions (php5query -M -v): 
opcache (Enabled for cli by maintainer script)
opcache (Enabled for apache2filter by maintainer script)
json (Enabled for cli by maintainer script)
json (Enabled for apache2filter by maintainer script)
readline (Enabled for cli by maintainer script)
readline (Enabled for apache2filter by maintainer script)
pdo (Enabled for cli by maintainer script)
pdo (Enabled for apache2filter by maintainer script)

 Configuration files: 
[PHP]
engine = On
short_open_tag = Off
asp_tags = Off
precision = 14
output_buffering = 4096
zlib.output_compression = Off
implicit_flush = Off
unserialize_callback_func =
serialize_precision = 17
disable_functions = 
pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,

disable_classes =
zend.enable_gc = On
expose_php = Off
max_execution_time = 30
max_input_time = 60
memory_limit = 128M
error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT
display_errors = Off
display_startup_errors = Off
log_errors = On
log_errors_max_len = 1024
ignore_repeated_errors = Off
ignore_repeated_source = Off
report_memleaks = On
track_errors = Off
html_errors = On
variables_order = "GPCS"
request_order = "GP"
register_argc_argv = Off
auto_globals_jit = On
post_max_size = 8M
auto_prepend_file =
auto_append_file =
default_mimetype = "text/html"
default_charset = "UTF-8"
doc_root =
user_dir =
enable_dl = Off
file_uploads = On
upload_max_filesize = 2M
max_file_uploads = 20
allow_url_fopen = On
allow_url_include = Off
default_socket_timeout = 60
[CLI Server]
cli_server.color = On
[Date]
[filter]
[iconv]
[intl]
[sqlite]
[sqlite3]
[Pcre]
[Pdo]
[Pdo_mysql]
pdo_mysql.cache_size = 2000
pdo_mysql.default_socket=
[Phar]
[mail function]
SMTP = localhost
smtp_port = 25
mail.add_x_header = On
[SQL]
sql.safe_mode = Off
[ODBC]
odbc.allow_persistent = On
odbc.check_persistent = On
odbc.max_persistent = -1
odbc.max_links = -1
odbc.defaultlrl = 4096
odbc.defaultbinmode = 1
[Interbase]
ibase.allow_persistent = 1
ibase.max_persistent = -1
ibase.max_links = -1
ibase.timestampformat = "%Y-%m-%d %H:%M:%S"
ibase.dateformat = "%Y-%m-%d"
ibase.timeformat = "%H:%M:%S"
[MySQL]
mysql.allow_l

Bug#759195: marked as done (php5: invalid argument -delete for "-cmin")

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #759195,
regarding php5: invalid argument -delete for "-cmin"
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.)


-- 
759195: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759195
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5
Version: 5.4.4-14+deb7u14
Severity: normal

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these lines ***
After updating the php5 package every half an hour cron sends an email with 
the subject "Cron[ -x /usr/lib/php5/maxlifetime ] && [ -x 
/usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && 
/usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime)" and the 
email body 
"find: Ungültiges Argument -delete für "-cmin"." --> translate to english
"find: invalid argrument -delete for "-cmin"."

Kind regards
Norbert Schulz


-- System Information:
Debian Release: 7.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages php5 depends on:
ii  libapache2-mod-php5  5.4.4-14+deb7u14
ii  php5-common  5.4.4-14+deb7u14

php5 recommends no packages.

php5 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm

Dear submitter,

as the package php5 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/841781

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)--- End Message ---

Bug#790472: marked as done (Please drop conditional build-depend on libmysqlclient15-dev)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #790472,
regarding Please drop conditional build-depend on libmysqlclient15-dev
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.)


-- 
790472: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790472
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5
Version: 5.6.9+dfsg-1
Severity: minor
User: pkg-mysql-ma...@lists.alioth.debian.org
Usertag: libmysqlclient15-dev

This package has a conditional build-depends on libmysqlclient-dev and
libmysqlclient15-dev.  Please drop libmysqlclient15-dev from
Build-Depends since this package no longer exists and as of mysql 5.6
is no longer "Provided" by libmysqlclient-dev either.

-- 
Martin Michlmayr
Linux for HP Helion OpenStack, Hewlett-Packard
--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm

Dear submitter,

as the package php5 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/841781

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)--- End Message ---

Bug#778596: marked as done (php5-gd: imageantialias is still missing)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #778596,
regarding php5-gd: imageantialias is still missing
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.)


-- 
778596: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778596
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-gd
Version: 5.6.5+dfsg-1
Severity: normal

Dear Maintainer,

Quite some time ago bug #321237 was posted, noting that php5-gd used by Debian
has missing some funtions.

There is a comment (#71) stating that "There is also an ongoing work",
and since Jessie is comming, I have checked if previosly missing
imageantialias() is maybe already implemented, but sadly:

$ php -r "var_dump(function_exists('imageantialias'));" 

  
bool(false)

I have asked about imageantialias() progress in libgd bug tracker:
https://bitbucket.org/libgd/gd-libgd/issue/115/backports-php-internal-functions-to-libgd#comment-13551981
but with no response.

Is there any hope, any possibility to encourage, motivate libgd developers to
have it fixed since Jessie is out? Or it is already too late (because of freeze)
and we will have to recompile php with bundeled libgd for another 2-3 years..?



-- Package-specific info:
 Additional PHP 5 information 

 PHP 5 SAPI (php5query -S): 
apache2
cli

 PHP 5 Extensions (php5query -M -v): 
readline (Enabled for apache2 by maintainer script)
readline (Enabled for cli by maintainer script)
json (Enabled for apache2 by maintainer script)
json (Enabled for cli by maintainer script)
opcache (Enabled for apache2 by maintainer script)
opcache (Enabled for cli by maintainer script)
gd (Enabled for apache2 by maintainer script)
gd (Enabled for cli by maintainer script)
pdo (Enabled for apache2 by maintainer script)
pdo (Enabled for cli by maintainer script)

 Configuration files: 
 /etc/php5/mods-available/gd.ini 
extension=gd.so


-- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages php5-gd depends on:
ii  libc6  2.19-13
ii  libfreetype6   2.5.2-2
ii  libgd3 2.1.0-5
ii  libjpeg62-turbo1:1.3.1-11
ii  libpng12-0 1.2.50-2+b2
ii  libvpx11.3.0-3
ii  libx11-6   2:1.6.2-3
ii  libxpm41:3.5.11-1+b1
ii  php5-common [phpapi-20131226]  5.6.5+dfsg-1
ii  ucf3.0030
ii  zlib1g 1:1.2.8.dfsg-2+b1

php5-gd recommends no packages.

php5-gd suggests no packages.

Versions of packages php5-common depends on:
ii  libc6   2.19-13
ii  lsof4.86+dfsg-1
ii  psmisc  22.21-2
ii  sed 4.2.2-4+b1
ii  ucf 3.0030

Versions of packages php5-common suggests:
pn  php5-user-cache  

Versions of packages php5-cli depends on:
ii  libbz2-1.01.0.6-7+b2
ii  libc6 2.19-13
ii  libcomerr21.42.12-1
ii  libdb5.3  5.3.28-7~deb8u1
ii  libedit2  3.1-20140620-2
ii  libgssapi-krb5-2  1.12.1+dfsg-17
ii  libk5crypto3  1.12.1+dfsg-17
ii  libkrb5-3 1.12.1+dfsg-17
ii  libmagic1 1:5.20-2
ii  libonig2  5.9.5-3.2
ii  libpcre3  2:8.35-3.3
ii  libqdbm14 1.8.78-5+b1
ii  libssl1.0.0   1.0.1k-1
ii  libxml2   2.9.1+dfsg1-4
ii  mime-support  3.58
ii  php5-common   5.6.5+dfsg-1
ii  php5-json 1.3.6-1
ii  tzdata2015a-1
ii  ucf   3.0030
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages php5-cli recommends:
ii  php5-readline  5.6.5+dfsg-1

Versions of packages php5-cli suggests:
pn  php-pear  

Versions of packages libapache2-mod-php5 depends on:
ii  apache2 2.4.10-9
ii  apache2-bin [apache2-api-20120211]  2.4.10-9
ii  libbz2-1.0  1.0.6-7+b2
ii  libc6   2.19-13
ii  libcomerr2  1.42.12-1
ii  libdb5.35.3.28-7~deb8u1
ii  libgssapi-krb5-21.12.1+dfsg-17
ii  libk5crypto3 

Bug#817917: marked as done (Segfault in zval_scan_black)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #817917,
regarding Segfault in zval_scan_black
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.)


-- 
817917: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817917
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: php5
Version: 5.6.17+dfsg-0+deb8u1

Hello,

I'm experiencing a systematic segfault on a peculiar page of a PHP app.

I've obtained the following backtrace.

I suppose more useful input might be needed, please advize me in that 
case on what must be retrieved and how.


Regards.


Program received signal SIGSEGV, Segmentation fault.
0x736acb4e in zval_scan_black (pz=) at 
/build/php5-5.6.17+dfsg/Zend/zend_gc.c:313

313 /build/php5-5.6.17+dfsg/Zend/zend_gc.c: No such file or directory.
#0  0x736acb4e in zval_scan_black (pz=) at 
/build/php5-5.6.17+dfsg/Zend/zend_gc.c:313
#1  0x736acee4 in zobj_scan_black (pz=, 
pz@entry=0x7fe36740, obj=)

at /build/php5-5.6.17+dfsg/Zend/zend_gc.c:347
#2  0x736ada7e in zobj_scan (pz=0x7fe36740) at 
/build/php5-5.6.17+dfsg/Zend/zend_gc.c:580

#3  gc_scan_roots () at /build/php5-5.6.17+dfsg/Zend/zend_gc.c:620
#4  gc_collect_cycles () at /build/php5-5.6.17+dfsg/Zend/zend_gc.c:791
#5  0x736adb8f in gc_zobj_possible_root (zv=0x55e5c8b0) at 
/build/php5-5.6.17+dfsg/Zend/zend_gc.c:216

#6  0x7373b01d in gc_zval_check_possible_root (z=)
at /build/php5-5.6.17+dfsg/Zend/zend_gc.h:183
#7  i_zval_ptr_dtor (zval_ptr=) at 
/build/php5-5.6.17+dfsg/Zend/zend_execute.h:86
#8  zend_vm_stack_clear_multiple (nested=) at 
/build/php5-5.6.17+dfsg/Zend/zend_execute.h:308

#9  zend_do_fcall_common_helper_SPEC (execute_data=0x585a1f48)
at /build/php5-5.6.17+dfsg/Zend/zend_vm_execute.h:650
#10 0x736c9dc0 in execute_ex (execute_data=0x585a1f48)
at /build/php5-5.6.17+dfsg/Zend/zend_vm_execute.h:363
#11 0x7367b5b8 in dtrace_execute_ex (execute_data=0x585a1f48)
at /build/php5-5.6.17+dfsg/Zend/zend_dtrace.c:73
[...]
#15138 0x7373b953 in zend_do_fcall_common_helper_SPEC 
(execute_data=0x77eac210)

at /build/php5-5.6.17+dfsg/Zend/zend_vm_execute.h:592
#15139 0x736c9dc0 in execute_ex (execute_data=0x77eac210)
at /build/php5-5.6.17+dfsg/Zend/zend_vm_execute.h:363
#15140 0x7367b5b8 in dtrace_execute_ex (execute_data=0x77eac210)
at /build/php5-5.6.17+dfsg/Zend/zend_dtrace.c:73
#15141 0x7368e0b0 in zend_execute_scripts (type=1441122480, 
type@entry=8, retval=0x7fe36660,
retval@entry=0x0, file_count=0, file_count@entry=3) at 
/build/php5-5.6.17+dfsg/Zend/zend.c:1341
#15142 0x73629c60 in php_execute_script 
(primary_file=primary_file@entry=0x7fffde20)

at /build/php5-5.6.17+dfsg/main/main.c:2597
#15143 0x7373cffa in php_handler (r=)
at /build/php5-5.6.17+dfsg/sapi/apache2handler/sapi_apache2.c:667
#15144 0x555ac2a0 in ap_run_handler (r=r@entry=0x77e2c0a0) 
at config.c:169
#15145 0x555ac7e9 in ap_invoke_handler (r=0x77e2c0a0) at 
config.c:433
#15146 0x555c2682 in ap_process_async_request (r=0x77e2c0a0) 
at http_request.c:317
#15147 0x555c2820 in ap_process_request (r=0x77e2c0a0) at 
http_request.c:363
#15148 0x555bf122 in ap_process_http_sync_connection 
(c=0x77e32290) at http_core.c:190

#15149 ap_process_http_connection (c=0x77e32290) at http_core.c:231
#15150 0x555b5b10 in ap_run_process_connection 
(c=0x77e32290) at connection.c:41
#15151 0x7405f7ba in child_main (child_num_arg=1441122480) at 
prefork.c:704
#15152 0x7405f9c7 in make_child (s=0x77fc0de0, slot=0) at 
prefork.c:746
#15153 0x7406070d in prefork_run (_pconf=0x557f2f38 
, plog=0x77fbc028,

s=0x77fc0de0) at prefork.c:956
#15154 0x55591e7e in ap_run_mpm (pconf=0x77fee028, 
plog=0x77fbc028, s=0x77fc0de0)

at mpm_common.c:94
#15155 0x5558b3c3 in main (argc=2, argv=0x7fffe578) at 
main.c:777
--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm

Dear submitter,

as the package php5 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/841781

The version of this package that was in Debian prior to this removal
can still be found usi

Bug#792239: marked as done (sessionclean does not support tiered session directory structure)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #792239,
regarding sessionclean does not support tiered session directory structure
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.)


-- 
792239: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792239
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: php5
Version: 5.6.9+dfsg-0+deb8u1

The new session cleanup script in Jessie (/usr/lib/php5/sessionclean) 
has a few limitations in it.


1. It does not support a tiered directory structure (e.g. 
session.save_path=2;/var/lib/php5)

2. It does not support a symlinked session directory
3. (not a limitation, but parameter warning) The find command uses the 
-ignore_readdir_race option after a non-option argument


I've attached a patch to fix all of these.

1. Adjust sed to remove the "N;" or "N;MODE;" prefix from session.save_path
2. Add a / to the end of $save_path to look inside the symlinked 
directory. It should still work with regular directories.

3. Move the -ignore_readdir_race parameter

Changed lines:

14: save_path=$(echo "$session_config" | sed -ne 
's/^session\.save_path=\(.*;\)\?\(.*\)$/\2/p')
29: find -O3 "$save_path/" -depth -ignore_readdir_race -mindepth 1 -name 
'sess_*' -type f -cmin "+$gc_maxlifetime" -delete
--- sessionclean.org2015-07-12 22:09:59.104104600 -0500
+++ sessionclean2015-07-12 20:56:30.909853124 -0500
@@ -11,7 +11,7 @@
 # Get all session variables once so we don't need to start PHP to get 
each config option
 session_config=$(php5 -c /etc/php5/${conf_dir}/php.ini -d 
"error_reporting='~E_ALL'" -r 'foreach(ini_get_all("session") as $k => $v) echo 
"$k=".$v["local_value"]."\n";')
 save_handler=$(echo "$session_config" | sed -ne 
's/^session\.save_handler=\(.*\)$/\1/p')
-save_path=$(echo "$session_config" | sed -ne 
's/^session\.save_path=\(.*\)$/\1/p')
+save_path=$(echo "$session_config" | sed -ne 
's/^session\.save_path=\(.*;\)\?\(.*\)$/\2/p')
 gc_maxlifetime=$(($(echo "$session_config" | sed -ne 
's/^session\.gc_maxlifetime=\(.*\)$/\1/p')/60))
 
 if [ "$save_handler" = "files" -a -d "$save_path" ]; then
@@ -26,7 +26,7 @@
 done
 ) | sort -rn -t: -k2,2 | sort -u -t: -k 1,1 | while IFS=: read -r save_path 
gc_maxlifetime; do
 # find all files older then maxlifetime and delete them
-find -O3 "$save_path" -depth -mindepth 1 -name 'sess_*' 
-ignore_readdir_race -type f -cmin "+$gc_maxlifetime" -delete
+find -O3 "$save_path/" -depth -ignore_readdir_race -mindepth 1 -name 
'sess_*' -type f -cmin "+$gc_maxlifetime" -delete
 done
 
 exit 0
--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm

Dear submitter,

as the package php5 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/841781

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)--- End Message ---

Bug#774154: marked as done (php5: CVE-2014-9425: double free in Zend/zend_ts_hash.c)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #774154,
regarding php5: CVE-2014-9425: double free in Zend/zend_ts_hash.c
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.)


-- 
774154: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774154
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: php5
Version: 5.6.4+dfsg-1
Severity: important
Tags: security, fixed-upstream

Please see https://bugs.php.net/bug.php?id=68676 for details.

- -- 
Henri Salo
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlShggUACgkQXf6hBi6kbk8jNwCfYNiExslA1E8u/+Pxg5458e3C
LIYAoI9ddbXHoOlhsI+513W2q87ZIgFK
=Gc9L
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm

Dear submitter,

as the package php5 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/841781

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)--- End Message ---

Bug#810244: marked as done (php5-common: sessionclean does not check /etc/php5/cli/php.ini)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #810244,
regarding php5-common: sessionclean does not check /etc/php5/cli/php.ini
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.)


-- 
810244: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810244
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-common
Version: 5.6.14+dfsg-1
Severity: normal

Dear Maintainer,

It appears that the SAPIS variable in /usr/lib/php5/sessionclean does
not include the cli dir. I've had instances on servers with only
php5-cli installed where CLI executed php scripts caused the inode 
count to be exhausted on the /var partition because there were 
millions of session files in /var/lib/php5/sessions/ which weren't being
cleaned up.

Please update the SAPIS variable in sessionclean to include cli:

SAPIS="apache2:apache2\napache2filter:apache2\ncgi:php5\nfpm:php5-fpm\ncli:php5\n"

This will prevent this and does not appear to have any negative side
effects. 


-- Package-specific info:
 Additional PHP 5 information 

 PHP 5 SAPI (php5query -S): 
apache2
cli

 PHP 5 Extensions (php5query -M -v): 
curl (Enabled for apache2 by maintainer script)
curl (Enabled for cli by maintainer script)
gd (Enabled for apache2 by maintainer script)
gd (Enabled for cli by maintainer script)
imap (Enabled for apache2 by maintainer script)
imap (Enabled for cli by maintainer script)
json (Enabled for apache2 by maintainer script)
json (Enabled for cli by maintainer script)
opcache (Enabled for apache2 by maintainer script)
opcache (Enabled for cli by maintainer script)
pdo (Enabled for apache2 by maintainer script)
pdo (Enabled for cli by maintainer script)
pdo_sqlite (Enabled for apache2 by maintainer script)
pdo_sqlite (Enabled for cli by maintainer script)
sqlite3 (Enabled for apache2 by maintainer script)
sqlite3 (Enabled for cli by maintainer script)
xsl (Enabled for apache2 by maintainer script)
xsl (Enabled for cli by maintainer script)
mysqlnd (Enabled for apache2 by maintainer script)
mysqlnd (Enabled for cli by maintainer script)
mysql (Enabled for apache2 by maintainer script)
mysql (Enabled for cli by maintainer script)
mysqli (Enabled for apache2 by maintainer script)
mysqli (Enabled for cli by maintainer script)
pdo_mysql (Enabled for apache2 by maintainer script)
pdo_mysql (Enabled for cli by maintainer script)

 Configuration files: 
 /etc/php5/mods-available/pdo.ini 
extension=pdo.so

 /etc/php5/mods-available/opcache.ini 
zend_extension=opcache.so


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (100, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-rc8 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages php5-common depends on:
ii  libc6   2.19-22
ii  lsof4.89+dfsg-0.1
ii  psmisc  22.21-2.1
ii  sed 4.2.2-6.1
ii  ucf 3.0030

php5-common recommends no packages.

Versions of packages php5-common suggests:
pn  php5-user-cache  

Versions of packages php5-cli depends on:
ii  libbz2-1.01.0.6-8
ii  libc6 2.19-22
ii  libcomerr21.42.13-1
ii  libdb5.3  5.3.28-11
ii  libedit2  3.1-20150325-1
ii  libgssapi-krb5-2  1.13.2+dfsg-2
ii  libk5crypto3  1.13.2+dfsg-2
ii  libkrb5-3 1.13.2+dfsg-2
ii  libmagic1 1:5.25-2
ii  libonig2  5.9.6-1
ii  libpcre3  2:8.35-7.2
ii  libqdbm14 1.8.78-6
ii  libssl1.0.0   1.0.2d-1
ii  libxml2   2.9.2+zdfsg1-4
ii  mime-support  3.59
ii  php5-json 1.3.7-1
ii  tzdata2015f-1
ii  ucf   3.0030
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages php5-cli recommends:
pn  php5-readline  

Versions of packages php5-cli suggests:
ii  php-pear  5.6.14+dfsg-1

Versions of packages libapache2-mod-php5 depends on:
ii  apache2 2.4.16-3
ii  apache2-bin [apache2-api-20120211]  2.4.16-3
ii  libbz2-1.0  1.0.6-8
ii  libc6   2.19-22
ii  libcomerr2  1.42.13-1
ii  libdb5.35.3.28-11
ii  libgssapi-krb5-21.13.2+dfsg-2
ii  libk5crypto31.13.2+dfsg-2
ii  libkrb5-3   1.13.2+dfsg-2
ii  libmagic1

Bug#827486: marked as done (php5-dev: integer overflow on x32)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #827486,
regarding php5-dev: integer overflow on x32
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.)


-- 
827486: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827486
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-dev
Version: 5.6.12+dfsg-0+deb8u1
Severity: important

Dear Maintainer,

Seems integer overflow is bogus on x32 arch

According to php doc 

> If PHP encounters a number beyond the bounds of the integer type, it will
> be interpreted as a float instead. Also, an operation which results in a
> number beyond the bounds of the integer type will return a float instead.

http://php.net/manual/en/language.types.integer.php

This works fine on i386

php -r 'echo("Number: " . (2147483647 + 1) . "\n");'
Number: 2147483648

The same code on x32

php -r 'echo("Number: " . (2147483647 + 1) . "\n");'
Number: -2147483648


-- System Information:
Debian Release: 8.1
Architecture: x32 (x86_64)
Foreign Architectures: amd64

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages php5-dev depends on:
ii  autoconf  2.69-8
ii  automake  1:1.14.1-4
ii  libpcre3-dev  2:8.35-3.3+x32
ii  libssl-dev1.0.1k-3+deb8u1
ii  libtool   2.4.2-1.11
ii  php5-common   5.6.12+dfsg-0+deb8u1
ii  shtool2.0.8-6

Versions of packages php5-dev recommends:
ii  dh-php50.2
ii  pkg-php-tools  1.28

php5-dev suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm

Dear submitter,

as the package php5 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/841781

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)--- End Message ---

Bug#845890: marked as done (php5: switch to build depend on the metapackage default-libmysqlclient-dev)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #845890,
regarding php5: switch to build depend on the metapackage 
default-libmysqlclient-dev
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.)


-- 
845890: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845890
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5
Severity: important

Hi! 

This package build depends on libmysqlclient-dev. It should instead
build-depend on default-libmysqlclient-dev metapackage, and end up
having the run-time dependency of the libmysqlclient implementation
Debian has chosen to use, currently MariaDB instead of Oracle MySQL. 

Announcement of new default-mysql-* metapackages:
https://lists.debian.org/debian-devel-announce/2016/09/msg0.html 

Wiki: https://wiki.debian.org/Teams/MySQL/default-mysql-server 

MBF: https://lists.debian.org/debian-devel/2016/11/msg00832.html 

Please update the depencies accordingly. In most cases the required
change is: 

* BEFORE: Build-Depends: libmysqlclient-dev 

* AFTER: Build-Depends: default-libmysqlclient-dev 

Thanks, 

Otto 
--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm

Dear submitter,

as the package php5 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/841781

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)--- End Message ---

Bug#803305: marked as done (php5: timezone "incorrectly" guessed from system)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #803305,
regarding php5: timezone "incorrectly" guessed from system
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.)


-- 
803305: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803305
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php5
Severity: normal

I ran into a somewhat special-case bug with the Debian patch that guesses the
timezone from the system default.

The system timezone is set to "Europe/London" in /etc/timezone, while php.ini
date.timezone is unset. In this case (after the recent change from DST to normal
time) the PHP function date_default_timezone_get() reports the timezone as UTC.

Although this is equivalent outside daylight saving time, it is not during DST,
which leads to wrong conversions between date/time strings and Unix timestamps.

I would suggest that the timezone be directly read from /etc/timezone before
using php_localtime_r(), which I assume has to infer the timezone from an
offset from UTC only.

Best regards,
Jaap

-- System Information:
Debian Release: 8.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm

Dear submitter,

as the package php5 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/841781

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)--- End Message ---

Bug#800564: marked as done (php5: trivial hash complexity DoS attack)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #800564,
regarding php5: trivial hash complexity DoS attack
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.)


-- 
800564: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800564
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-cli
Version: 5.6.13+dfsg-2
Severity: important
Tags: security

PHP uses the DJB "times 33" hash to hash strings in its hash tables,
without the use of any secret key.  Hash values are therefore the same
between multiple invocations.  As a result, it's trivial to precompute a
set of values that all hash to the same bucket and cause positively
abysmal performance.

If a script accepts untrusted hash keys, such as from JSON input, it is
subject to a DoS attack.  PHP implemented the max_input_vars option, but
this is not effective in the general case, especially in the era of
JSON-laden POST requests.  Perl, Python, and Ruby have all addressed
their CVEs properly, but PHP has not and as a result is still
vulnerable.

Cloning my example repository[0] and running
"php scripts/exploited.php < example/1048576.json" demonstrates the
problem very quickly.  The similar Perl and Python scripts are not
vulnerable to this attack.  A JSON file containing only 65536 entries
takes PHP 5.6 22 seconds to process.

A new CVE should probably be allocated and the bug should be fixed
correctly this time, probably by seeding a key from /dev/urandom and
using SipHash-2-4 or the like.

[0] https://github.com/bk2204/php-hash-dos

-- Package-specific info:
 Additional PHP 5 information 

 PHP 5 SAPI (php5query -S): 
cli

 PHP 5 Extensions (php5query -M -v): 
pdo (Enabled for cli by maintainer script)
readline (Enabled for cli by maintainer script)
json (Enabled for cli by maintainer script)
opcache (Enabled for cli by maintainer script)

 Configuration files: 
[PHP]
engine = On
short_open_tag = Off
asp_tags = Off
precision = 14
output_buffering = 4096
zlib.output_compression = Off
implicit_flush = Off
unserialize_callback_func =
serialize_precision = 17
disable_functions =
disable_classes =
zend.enable_gc = On
expose_php = On
max_execution_time = 30
max_input_time = 60
memory_limit = -1
error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT
display_errors = Off
display_startup_errors = Off
log_errors = On
log_errors_max_len = 1024
ignore_repeated_errors = Off
ignore_repeated_source = Off
report_memleaks = On
track_errors = Off
html_errors = On
variables_order = "GPCS"
request_order = "GP"
register_argc_argv = Off
auto_globals_jit = On
post_max_size = 8M
auto_prepend_file =
auto_append_file =
default_mimetype = "text/html"
default_charset = "UTF-8"
doc_root =
user_dir =
enable_dl = Off
file_uploads = On
upload_max_filesize = 2M
max_file_uploads = 20
allow_url_fopen = On
allow_url_include = Off
default_socket_timeout = 60
[CLI Server]
cli_server.color = On
[Date]
[filter]
[iconv]
[intl]
[sqlite]
[sqlite3]
[Pcre]
[Pdo]
[Pdo_mysql]
pdo_mysql.cache_size = 2000
pdo_mysql.default_socket=
[Phar]
[mail function]
SMTP = localhost
smtp_port = 25
mail.add_x_header = On
[SQL]
sql.safe_mode = Off
[ODBC]
odbc.allow_persistent = On
odbc.check_persistent = On
odbc.max_persistent = -1
odbc.max_links = -1
odbc.defaultlrl = 4096
odbc.defaultbinmode = 1
[Interbase]
ibase.allow_persistent = 1
ibase.max_persistent = -1
ibase.max_links = -1
ibase.timestampformat = "%Y-%m-%d %H:%M:%S"
ibase.dateformat = "%Y-%m-%d"
ibase.timeformat = "%H:%M:%S"
[MySQL]
mysql.allow_local_infile = On
mysql.allow_persistent = On
mysql.cache_size = 2000
mysql.max_persistent = -1
mysql.max_links = -1
mysql.default_port =
mysql.default_socket =
mysql.default_host =
mysql.default_user =
mysql.default_password =
mysql.connect_timeout = 60
mysql.trace_mode = Off
[MySQLi]
mysqli.max_persistent = -1
mysqli.allow_persistent = On
mysqli.max_links = -1
mysqli.cache_size = 2000
mysqli.default_port = 3306
mysqli.default_socket =
mysqli.default_host =
mysqli.default_user =
mysqli.default_pw =
mysqli.reconnect = Off
[mysqlnd]
mysqlnd.collect_statistics = On
mysqlnd.collect_memory_statistics = Off
[OCI8]
[PostgreSQL]
pgsql.allow_persistent = On
pgsql.auto_reset_persistent = Off
pgsql.max_persistent = -1
pgsql.max_links = -1
pgsql.ignore_notice = 0
pgsql.log_notice = 0
[Sybase-CT]
sybct.allow_persistent = On
sybct.max_persistent = -1
sybct.max_links = -1
sybct.min_server_severity = 10
sybct.min_client_severity = 10
[bcmath]
bcmath.scale = 0
[browscap]
[Sess

Bug#815797: marked as done (PHP 7.0 Transition Blocker Bug)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #815797,
regarding PHP 7.0 Transition Blocker Bug
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.)


-- 
815797: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815797
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:php5
Version: 5.6.17+dfsg-3
Severity: serious

This is a just a maintainer blocker bug, so we can start transitioning
stretch to src:php7.0 and slowly get rid of src:php5 in testing and
unstable.

O.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (700, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 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)
--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm

Dear submitter,

as the package php5 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/841781

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)--- End Message ---

Bug#841618: marked as done (php5: FTBFS: configure: error: Cannot find libmysqlclient_r under /usr.)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #841618,
regarding php5: FTBFS: configure: error: Cannot find libmysqlclient_r under 
/usr.
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.)


-- 
841618: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841618
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php5
Version: 5.6.26+dfsg-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> checking for mcrypt_module_open in -lmcrypt... yes
> checking for MSSQL support via FreeTDS... yes, shared
> checking for dnet_addr in -ldnet_stub... no
> checking for MySQL support... yes, shared
> checking for specified location of the MySQL UNIX socket... 
> /var/run/mysqld/mysqld.sock
> configure: error: Cannot find libmysqlclient_r under /usr.
> Note that the MySQL client library is not bundled anymore!
> debian/rules:275: recipe for target 'configure-apache2-stamp' failed

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   http://aws-logs.debian.net/2016/10/21/php5_5.6.26+dfsg-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm

Dear submitter,

as the package php5 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/841781

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)--- End Message ---

Bug#819139: marked as done (php5-dev: php-config5 --php-binary gives unversioned result)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #819139,
regarding php5-dev: php-config5 --php-binary gives unversioned result
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.)


-- 
819139: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819139
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-dev
Version: 5.6.19+dfsg-2
Severity: normal

"php-config5 --php-binary" gives "/usr/bin/php" which is a managed by
alternatives.  Currently /usr/bin/php7.0 has the highest priority:

$ update-alternatives --config php
There are 2 choices for the alternative php (providing /usr/bin/php).

  SelectionPath Priority   Status

* 0/usr/bin/php7.0   70auto mode
  1/usr/bin/php5 50manual mode
  2/usr/bin/php7.0   70manual mode

On a system with both php5-cli and php7.0-cli installed (which users who have
installed php-cli will have, since this dependency package has now switched to
pulling in php7.0-cli), the upshot is that you get the wrong PHP interpreter
version:

$ php-config5 --php-binary
/usr/bin/php
$ /usr/bin/php --version
PHP 7.0.4-6 (cli) ( NTS )
Copyright (c) 1997-2016 The PHP Group
Zend Engine v3.0.0, Copyright (c) 1998-2016 Zend Technologies
with Zend OPcache v7.0.6-dev, Copyright (c) 1999-2016, by Zend Technologies

Really "php-config5 --php-binary" should give "/usr/bin/php5":

$ /usr/bin/php5 --version
PHP 5.6.19-2 (cli) 
Copyright (c) 1997-2016 The PHP Group
Zend Engine v2.6.0, Copyright (c) 1998-2016 Zend Technologies
with Zend OPcache v7.0.6-dev, Copyright (c) 1999-2016, by Zend Technologies

It appears that php-config7.0 gets this right:

$ php-config7.0 --php-binary
/usr/bin/php7.0

Cheers,
Olly

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages php5-dev depends on:
ii  autoconf  2.69-9
ii  automake  1:1.15-4
ii  libpcre3-dev  2:8.38-3.1
ii  libssl-dev1.0.2g-1
ii  libtool   2.4.6-0.1
ii  php5-common   5.6.19+dfsg-2
ii  shtool2.0.8-8

Versions of packages php5-dev recommends:
ii  dh-php50.2
ii  pkg-php-tools  1.32

php5-dev suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm

Dear submitter,

as the package php5 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/841781

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)--- End Message ---

Bug#834579: marked as done (/usr/bin/php5: php5: when connecting using odbc and later mysqli in the same script i got: Couldn't fetch mysqli)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #834579,
regarding /usr/bin/php5: php5: when connecting using odbc and later mysqli in 
the same script i got: Couldn't fetch mysqli
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.)


-- 
834579: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834579
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-cli
Version: 5.6.24+dfsg-0+deb8u1
Severity: normal
File: /usr/bin/php5

when using odbc and mysqli in same php process the mysqli api will not work and 
no errors messages as thrown, only the warning message
"Warning: mysqli::query(): Couldn't fetch mysqli in /root/mysql_phpbug.php on 
line 36"


Below you can find a simple script that reproduces the problem. 

connect_error) { echo ('Connect Error (' . 
$mysqli->connect_errno . ') '.$mysqli->connect_error); }
else {
$result = $mysqli->query("select count(*) as total from 
client_limit;", MYSQLI_USE_RESULT);
if (!is_object($result)) {
echo "no results found, error: ".$mysqli->error."\n";
}
else {
$tmp = $result->fetch_object();
print_r($tmp);
$result->close();
}
$mysqli->close();
}
echo "*** \n ";
}
function using_odbc()
{
echo "*** ODBC \n";
$conn = odbc_connect("localhost_tel_cdr", false, false);
if (!$conn) { echo "fail to connect using odbc ".odbc_errormsg(); }
else {
$res = odbc_exec($conn, "select count(*) as total_cdr from cdr 
where (start_stamp >= '1470751734' ) and (start_stamp <= '1471356534' );");
if (!$res) {
echo "Fail to execute sql ".odbc_errormsg();
}
else {
$row = odbc_fetch_array($res);
print_r($row);
odbc_free_result($res);
}
odbc_close($conn);
}
echo "***";
}

?>



-- Package-specific info:
 Additional PHP 5 information 

 PHP 5 SAPI (php5query -S): 
fpm
cli
apache2
cgi

 PHP 5 Extensions (php5query -M -v): 
mysqli (Enabled for fpm by maintainer script)
mysqli (Enabled for cli by maintainer script)
mysqli (Enabled for apache2 by maintainer script)
mysqli (Enabled for cgi by maintainer script)
curl (Enabled for fpm by maintainer script)
curl (Enabled for cli by maintainer script)
curl (Enabled for apache2 by maintainer script)
curl (Enabled for cgi by maintainer script)
mcrypt (Enabled for fpm by maintainer script)
mcrypt (Enabled for cli by maintainer script)
mcrypt (Enabled for apache2 by maintainer script)
mcrypt (Enabled for cgi by maintainer script)
pdo_sqlite (Enabled for fpm by maintainer script)
pdo_sqlite (Enabled for cli by maintainer script)
pdo_sqlite (Enabled for apache2 by maintainer script)
pdo_sqlite (Enabled for cgi by maintainer script)
odbc (Enabled for fpm by maintainer script)
odbc (Enabled for cli by maintainer script)
odbc (Enabled for apache2 by maintainer script)
odbc (Enabled for cgi by maintainer script)
pdo (Enabled for fpm by maintainer script)
pdo (Enabled for cli by maintainer script)
pdo (Enabled for apache2 by maintainer script)
pdo (Enabled for cgi by maintainer script)
mysql (Enabled for fpm by maintainer script)
mysql (Enabled for cli by maintainer script)
mysql (Enabled for apache2 by maintainer script)
mysql (Enabled for cgi by maintainer script)
imap (Enabled for fpm by maintainer script)
imap (Enabled for cli by maintainer script)
imap (Enabled for apache2 by maintainer script)
imap (Enabled for cgi by maintainer script)
ssh2 (Enabled for fpm by local administrator)
ssh2 (Enabled for cli by local administrator)
ssh2 (Enabled for apache2 by local administrator)
ssh2 (Enabled for cgi by local administrator)
opcache (Enabled for fpm by maintainer script)
opcache (Enabled for cli by maintainer script)
opcache (Enabled for apache2 by maintainer script)
opcache (Enabled for cgi by maintainer script)
sqlite3 (Enabled for fpm by maintainer script)
sqlite3 (Enabled for cli by maintainer script)
sqlite3 (Enabled for apache2 by maintainer script)
sqlite3 (Enabled for cgi by maintainer script)
pdo_odbc (Enabled for fpm by maintainer script)
pdo_odbc (Enabled for cli by maintainer script)
pdo_odbc (Enabled for apache2 by maintainer script)
pdo_odbc (Enabled

Bug#828498: marked as done (php5: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #828498,
regarding php5: FTBFS with openssl 1.1.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 ow...@bugs.debian.org
immediately.)


-- 
828498: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828498
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php5
Version: 5.6.22+dfsg-1
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/php5_5.6.22+dfsg-1_amd64-20160529-1506

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm

Dear submitter,

as the package php5 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/841781

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)--- End Message ---

Bug#848661: marked as done (php5-fpm[4116]: segfault at 0 ip 00007f1b77ddc25a sp 00007ffc029e64d0 error 4 in pdo_mysql.so[7f1b77dd9000+7000])

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #848661,
regarding php5-fpm[4116]: segfault at 0 ip 7f1b77ddc25a sp 7ffc029e64d0 
error 4 in pdo_mysql.so[7f1b77dd9000+7000]
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.)


-- 
848661: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848661
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: php5
Version: 5.6.29+dfsg-0+deb8u1


Hello,

I'm experience segfault when accessing to a mysql database using 
php_pdo_mysql, to reproduce i just hit refresh multiple times on the web 
page.



Below you can find the respective backtrace log obtained from the 
generated core:



Core was generated by `php-fpm: pool 
internal '.

Program terminated with signal SIGSEGV, Segmentation fault.
#0  _pdo_mysql_error (dbh=0x28e2658, stmt=0x0, file=0x7f1b77ddef80 
"/build/php5-5.6.29+dfsg/ext/pdo_mysql/mysql_driver.c", line=586) at 
/build/php5-5.6.29+dfsg/ext/pdo_mysql/mysql_driver.c:67
67/build/php5-5.6.29+dfsg/ext/pdo_mysql/mysql_driver.c: No such file 
or directory.

(gdb) bt
#0  _pdo_mysql_error (dbh=0x28e2658, stmt=0x0, file=0x7f1b77ddef80 
"/build/php5-5.6.29+dfsg/ext/pdo_mysql/mysql_driver.c", line=586) at 
/build/php5-5.6.29+dfsg/ext/pdo_mysql/mysql_driver.c:67
#1  0x7f1b77ddd159 in pdo_mysql_handle_factory (dbh=0x28e2658, 
driver_options=0x0) at 
/build/php5-5.6.29+dfsg/ext/pdo_mysql/mysql_driver.c:772
#2  0x7f1b77feb22a in zim_PDO_dbh_constructor (ht=42870360, 
return_value=0x0, return_value_ptr=0x7f1b77ddef80, this_ptr=0x2568078, 
return_value_used=0) at /build/php5-5.6.29+dfsg/ext/pdo/pdo_dbh.c:389
#3  0x006e7aea in dtrace_execute_internal 
(execute_data_ptr=, fci=, 
return_value_used=) at 
/build/php5-5.6.29+dfsg/Zend/zend_dtrace.c:97
#4  0x007a84d0 in zend_do_fcall_common_helper_SPEC 
(execute_data=0x7f1b83782218) at 
/build/php5-5.6.29+dfsg/Zend/zend_vm_execute.h:560
#5  0x00736820 in execute_ex (execute_data=0x7f1b83782218) at 
/build/php5-5.6.29+dfsg/Zend/zend_vm_execute.h:363
#6  0x006e7988 in dtrace_execute_ex 
(execute_data=0x7f1b83782218) at 
/build/php5-5.6.29+dfsg/Zend/zend_dtrace.c:73
#7  0x007a8a13 in zend_do_fcall_common_helper_SPEC 
(execute_data=0x7f1b83782000) at 
/build/php5-5.6.29+dfsg/Zend/zend_vm_execute.h:592
#8  0x00736820 in execute_ex (execute_data=0x7f1b83782000) at 
/build/php5-5.6.29+dfsg/Zend/zend_vm_execute.h:363
#9  0x006e7988 in dtrace_execute_ex 
(execute_data=0x7f1b83782000) at 
/build/php5-5.6.29+dfsg/Zend/zend_dtrace.c:73
#10 0x007a8a13 in zend_do_fcall_common_helper_SPEC 
(execute_data=0x7f1b83781e20) at 
/build/php5-5.6.29+dfsg/Zend/zend_vm_execute.h:592
#11 0x00736820 in execute_ex (execute_data=0x7f1b83781e20) at 
/build/php5-5.6.29+dfsg/Zend/zend_vm_execute.h:363
#12 0x006e7988 in dtrace_execute_ex 
(execute_data=0x7f1b83781e20) at 
/build/php5-5.6.29+dfsg/Zend/zend_dtrace.c:73
#13 0x006e9826 in zend_call_function (fci=0x7ffc029e6f20, 
fci_cache=0x0, fci_cache@entry=0x7ffc029e6ef0) at 
/build/php5-5.6.29+dfsg/Zend/zend_execute_API.c:831
#14 0x0060f4f3 in zif_call_user_func_array (ht=, 
return_value=0x25661d8, return_value_ptr=, 
this_ptr=, return_value_used=)

at /build/php5-5.6.29+dfsg/ext/standard/basic_functions.c:4790
#15 0x006e7aea in dtrace_execute_internal 
(execute_data_ptr=, fci=, 
return_value_used=) at 
/build/php5-5.6.29+dfsg/Zend/zend_dtrace.c:97
#16 0x007a84d0 in zend_do_fcall_common_helper_SPEC 
(execute_data=0x7f1b83781c40) at 
/build/php5-5.6.29+dfsg/Zend/zend_vm_execute.h:560
#17 0x00736820 in execute_ex (execute_data=0x7f1b83781c40) at 
/build/php5-5.6.29+dfsg/Zend/zend_vm_execute.h:363
#18 0x006e7988 in dtrace_execute_ex 
(execute_data=0x7f1b83781c40) at 
/build/php5-5.6.29+dfsg/Zend/zend_dtrace.c:73
#19 0x006e9826 in zend_call_function (fci=0x7ffc029e72d0, 
fci_cache=0x0, fci_cache@entry=0x7ffc029e72a0) at 
/build/php5-5.6.29+dfsg/Zend/zend_execute_API.c:831
#20 0x0060f4f3 in zif_call_user_func_array (ht=, 
return_value=0x2565e20, return_value_ptr=, 
this_ptr=, return_value_used=)

at /build/php5-5.6.29+dfsg/ext/standard/basic_functions.c:4790
#21 0x006e7aea in dtrace_execute_internal 
(execute_data_ptr=, fci=, 
return_value_used=) at 
/build/php5-5.6.29+dfsg/Zend/zend_dtrace.c:97
#22 0x007a84d0 in zend_do_fcall_common_helper_SPEC 
(exec

Bug#846244: marked as done (php5-phpdbg: lacks /usr/bin/phpdbg alternative)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #846244,
regarding php5-phpdbg: lacks /usr/bin/phpdbg alternative
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.)


-- 
846244: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846244
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-phpdbg
Version: 5.6.27+dfsg-0+deb8u1
Severity: normal

Dear Maintainer,

I have installed php5-phpdbg from jessie/updates, the executable is
available as /usr/bin/php5dbg. It would be very nice to add support for
/usr/bin/phpdbg using the alternative system.  Then I guess the
php7-phpdbg could also use that.

The reason is we have script that refers to 'phpdbg', eg without version
information.

-- Package-specific info:
 Additional PHP 5 information 

 PHP 5 SAPI (php5query -S): 
phpdbg
apache2
cli

 PHP 5 Extensions (php5query -M -v): 
curl (Enabled for phpdbg by maintainer script)
curl (Enabled for apache2 by maintainer script)
curl (Enabled for cli by maintainer script)
sqlite3 (Enabled for phpdbg by maintainer script)
sqlite3 (Enabled for apache2 by maintainer script)
sqlite3 (Enabled for cli by maintainer script)
pdo_sqlite (Enabled for phpdbg by maintainer script)
pdo_sqlite (Enabled for apache2 by maintainer script)
pdo_sqlite (Enabled for cli by maintainer script)
readline (Enabled for phpdbg by maintainer script)
readline (Enabled for apache2 by maintainer script)
readline (Enabled for cli by maintainer script)
redis (Enabled for phpdbg by maintainer script)
redis (Enabled for apache2 by maintainer script)
redis (Enabled for cli by maintainer script)
opcache (Enabled for phpdbg by maintainer script)
opcache (Enabled for apache2 by maintainer script)
opcache (Enabled for cli by maintainer script)
tidy (Enabled for phpdbg by maintainer script)
tidy (Enabled for apache2 by maintainer script)
tidy (Enabled for cli by maintainer script)
intl (Enabled for phpdbg by maintainer script)
intl (Enabled for apache2 by maintainer script)
intl (Enabled for cli by maintainer script)
xsl (Enabled for phpdbg by maintainer script)
xsl (Enabled for apache2 by maintainer script)
xsl (Enabled for cli by maintainer script)
mcrypt (Enabled for phpdbg by maintainer script)
mcrypt (Enabled for apache2 by maintainer script)
mcrypt (Enabled for cli by maintainer script)
pdo (Enabled for phpdbg by maintainer script)
pdo (Enabled for apache2 by maintainer script)
pdo (Enabled for cli by maintainer script)
json (Enabled for phpdbg by maintainer script)
json (Enabled for apache2 by maintainer script)
json (Enabled for cli by maintainer script)

 Configuration files: 
[PHP]
engine = On
short_open_tag = Off
asp_tags = Off
precision = 14
output_buffering = 4096
zlib.output_compression = Off
implicit_flush = Off
unserialize_callback_func =
serialize_precision = 17
disable_functions = 
pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,
disable_classes =
zend.enable_gc = On
expose_php = Off
max_execution_time = 30
max_input_time = 60
memory_limit = 128M
error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT
display_errors = Off
display_startup_errors = Off
log_errors = On
log_errors_max_len = 1024
ignore_repeated_errors = Off
ignore_repeated_source = Off
report_memleaks = On
track_errors = Off
html_errors = On
variables_order = "GPCS"
request_order = "GP"
register_argc_argv = Off
auto_globals_jit = On
post_max_size = 8M
auto_prepend_file =
auto_append_file =
default_mimetype = "text/html"
default_charset = "UTF-8"
doc_root =
user_dir =
enable_dl = Off
file_uploads = On
upload_max_filesize = 2M
max_file_uploads = 20
allow_url_fopen = On
allow_url_include = Off
default_socket_timeout = 60
[CLI Server]
cli_server.color = On
[Date]
[filter]
[iconv]
[intl]
[sqlite3]
[Pcre]
[Pdo]
[Pdo_mysql]
pdo_mysql.cache_size = 2000
pdo_mysql.default_socket=
[Phar]
[mail function]
SMTP = localhost
smtp_port = 25
mail.add_x_header = On
[SQL]
sql.safe_mode = Off
[ODBC]
odbc.allow_persistent = On
odbc.check_persistent = On
odbc.max_persistent = -1
odbc.max_links = -1
odbc.defaultlrl = 4096
odbc.defaultbinmode = 1
[Interbase]
ibase.allow_persistent = 1
ibase.max_persistent = -1
ibase.max_links = -1
ibase.timestampformat = "%Y-%m-%d %H:%M:%S"
ibase.

Bug#833133: marked as done (php5-fpm: session.save_path defined in pool.d/*.conf are not used by /usr/lib/php5/sessionclean)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #833133,
regarding php5-fpm: session.save_path defined in pool.d/*.conf are not used by 
/usr/lib/php5/sessionclean
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.)


-- 
833133: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833133
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-fpm
Version: 5.6.24+dfsg-0+deb8u1
Severity: normal

Dear Maintainer,

If you define session.save_path in a php5-fpm pool, then the sessions files are 
never cleaned by /usr/lib/php5/sessionclean.

Only settings set up in php.ini files are considered by the script.

IMHO, the script should take into account all session.save_path defined in all 
pools.


-- Package-specific info:
 Additional PHP 5 information 

 PHP 5 SAPI (php5query -S): 
fpm
cli

 PHP 5 Extensions (php5query -M -v): 
mysqli (Enabled for fpm by maintainer script)
mysqli (Enabled for cli by maintainer script)
pdo_mysql (Enabled for fpm by maintainer script)
pdo_mysql (Enabled for cli by maintainer script)
imagick (Enabled for fpm by maintainer script)
imagick (Enabled for cli by maintainer script)
opcache (Enabled for fpm by maintainer script)
opcache (Enabled for cli by maintainer script)
curl (Enabled for fpm by maintainer script)
curl (Enabled for cli by maintainer script)
mysqlnd (Enabled for fpm by maintainer script)
mysqlnd (Enabled for cli by maintainer script)
json (Enabled for fpm by maintainer script)
json (Enabled for cli by maintainer script)
apcu (Enabled for fpm by maintainer script)
apcu (Enabled for cli by maintainer script)
mcrypt (Enabled for fpm by maintainer script)
mcrypt (Enabled for cli by maintainer script)
mysql (Enabled for fpm by maintainer script)
mysql (Enabled for cli by maintainer script)
pdo (Enabled for fpm by maintainer script)
pdo (Enabled for cli by maintainer script)
gd (Enabled for fpm by maintainer script)
gd (Enabled for cli by maintainer script)
readline (Enabled for fpm by maintainer script)
readline (Enabled for cli by maintainer script)

 Configuration files: 
[PHP]
engine = On
short_open_tag = Off
asp_tags = Off
precision = 14
output_buffering = 4096
zlib.output_compression = Off
implicit_flush = Off
unserialize_callback_func =
serialize_precision = 17
disable_functions = 
pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,
disable_classes =
zend.enable_gc = On
expose_php = Off
max_execution_time = 30
max_input_time = 60
memory_limit = 128M
error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT
display_errors = Off
display_startup_errors = Off
log_errors = On
log_errors_max_len = 1024
ignore_repeated_errors = Off
ignore_repeated_source = Off
report_memleaks = On
track_errors = Off
html_errors = On
variables_order = "GPCS"
request_order = "GP"
register_argc_argv = Off
auto_globals_jit = On
post_max_size = 8M
auto_prepend_file =
auto_append_file =
default_mimetype = "text/html"
default_charset = "UTF-8"
doc_root =
user_dir =
enable_dl = Off
file_uploads = On
upload_max_filesize = 2M
max_file_uploads = 20
allow_url_fopen = On
allow_url_include = Off
default_socket_timeout = 60
[CLI Server]
cli_server.color = On
[Date]
[filter]
[iconv]
[intl]
[sqlite3]
[Pcre]
[Pdo]
[Pdo_mysql]
pdo_mysql.cache_size = 2000
pdo_mysql.default_socket=
[Phar]
[mail function]
SMTP = localhost
smtp_port = 25
mail.add_x_header = On
[SQL]
sql.safe_mode = Off
[ODBC]
odbc.allow_persistent = On
odbc.check_persistent = On
odbc.max_persistent = -1
odbc.max_links = -1
odbc.defaultlrl = 4096
odbc.defaultbinmode = 1
[Interbase]
ibase.allow_persistent = 1
ibase.max_persistent = -1
ibase.max_links = -1
ibase.timestampformat = "%Y-%m-%d %H:%M:%S"
ibase.dateformat = "%Y-%m-%d"
ibase.timeformat = "%H:%M:%S"
[MySQL]
mysql.allow_local_infile = On
mysql.allow_persistent = On
mysql.cache_size = 2000
mysql.max_persistent = -1
mysql.max_links = -1
mysql.default_port =
mysql.default_socket =
mysql.default_host =
mysql.default_user =
mysql.default_password =
mysql.connect_timeout = 60
mysql.trace_mode = Off
[MySQLi]
mysqli.max_persistent = -1
mysqli.allow_persistent = On
mysqli.max_links = -1
mysqli.cache_size = 2000
mysqli.default_port = 3306
mysqli.default_socket =
mysqli.default_host =
my

Bug#849767: marked as done (php5-fpm: segfault when using pdo_mysql.so)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #849767,
regarding php5-fpm: segfault when using pdo_mysql.so
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.)


-- 
849767: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849767
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: php5-fpm
Version: 5.6.29+dfsg-0+deb8u1


php5-fmp is crashing when connecting to mysql using pdo with segfault.
The web server is nginx and i connect using fastcig parameter: 
fastcgi_pass unix:/var/run/php5-fpm-internal.sock; with default parameters.



I get the following gdb:


[New LWP 3316]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `php-fpm: pool 
internal '.

Program terminated with signal SIGSEGV, Segmentation fault.
#0  _pdo_mysql_error (dbh=0x202b1a0, stmt=0x0, file=0x7f5fb5cc7f80 
"/build/php5-5.6.29+dfsg/ext/pdo_mysql/mysql_driver.c", line=586) at 
/build/php5-5.6.29+dfsg/ext/pdo_mysql/mysql_driver.c:67
67/build/php5-5.6.29+dfsg/ext/pdo_mysql/mysql_driver.c: No such file 
or directory.

(gdb) bt
#0  _pdo_mysql_error (dbh=0x202b1a0, stmt=0x0, file=0x7f5fb5cc7f80 
"/build/php5-5.6.29+dfsg/ext/pdo_mysql/mysql_driver.c", line=586) at 
/build/php5-5.6.29+dfsg/ext/pdo_mysql/mysql_driver.c:67
#1  0x7f5fb5cc6159 in pdo_mysql_handle_factory (dbh=0x202b1a0, 
driver_options=0x0) at 
/build/php5-5.6.29+dfsg/ext/pdo_mysql/mysql_driver.c:772
#2  0x7f5fb5ed422a in zim_PDO_dbh_constructor (ht=33730976, 
return_value=0x0, return_value_ptr=0x7f5fb5cc7f80, this_ptr=0x272ab50, 
return_value_used=0) at /build/php5-5.6.29+dfsg/ext/pdo/pdo_dbh.c:389
#3  0x006e7aea in dtrace_execute_internal 
(execute_data_ptr=, fci=, 
return_value_used=) at 
/build/php5-5.6.29+dfsg/Zend/zend_dtrace.c:97
#4  0x007a84d0 in zend_do_fcall_common_helper_SPEC 
(execute_data=0x7f5fc166b3a0) at 
/build/php5-5.6.29+dfsg/Zend/zend_vm_execute.h:560
#5  0x00736820 in execute_ex (execute_data=0x7f5fc166b3a0) at 
/build/php5-5.6.29+dfsg/Zend/zend_vm_execute.h:363
#6  0x006e7988 in dtrace_execute_ex 
(execute_data=0x7f5fc166b3a0) at 
/build/php5-5.6.29+dfsg/Zend/zend_dtrace.c:73
#7  0x007a8a13 in zend_do_fcall_common_helper_SPEC 
(execute_data=0x7f5fc166b188) at 
/build/php5-5.6.29+dfsg/Zend/zend_vm_execute.h:592
#8  0x00736820 in execute_ex (execute_data=0x7f5fc166b188) at 
/build/php5-5.6.29+dfsg/Zend/zend_vm_execute.h:363
#9  0x006e7988 in dtrace_execute_ex 
(execute_data=0x7f5fc166b188) at 
/build/php5-5.6.29+dfsg/Zend/zend_dtrace.c:73
#10 0x007a8a13 in zend_do_fcall_common_helper_SPEC 
(execute_data=0x7f5fc166afa8) at 
/build/php5-5.6.29+dfsg/Zend/zend_vm_execute.h:592
#11 0x00736820 in execute_ex (execute_data=0x7f5fc166afa8) at 
/build/php5-5.6.29+dfsg/Zend/zend_vm_execute.h:363
#12 0x006e7988 in dtrace_execute_ex 
(execute_data=0x7f5fc166afa8) at 
/build/php5-5.6.29+dfsg/Zend/zend_dtrace.c:73
#13 0x006e9826 in zend_call_function (fci=0x7ffe8ec467a0, 
fci_cache=0x0, fci_cache@entry=0x7ffe8ec46770) at 
/build/php5-5.6.29+dfsg/Zend/zend_execute_API.c:831
#14 0x0060f4f3 in zif_call_user_func_array (ht=, 
return_value=0x2724118, return_value_ptr=, 
this_ptr=, return_value_used=)

at /build/php5-5.6.29+dfsg/ext/standard/basic_functions.c:4790
#15 0x006e7aea in dtrace_execute_internal 
(execute_data_ptr=, fci=, 
return_value_used=) at 
/build/php5-5.6.29+dfsg/Zend/zend_dtrace.c:97
#16 0x007a84d0 in zend_do_fcall_common_helper_SPEC 
(execute_data=0x7f5fc166adc8) at 
/build/php5-5.6.29+dfsg/Zend/zend_vm_execute.h:560
#17 0x00736820 in execute_ex (execute_data=0x7f5fc166adc8) at 
/build/php5-5.6.29+dfsg/Zend/zend_vm_execute.h:363
#18 0x006e7988 in dtrace_execute_ex 
(execute_data=0x7f5fc166adc8) at 
/build/php5-5.6.29+dfsg/Zend/zend_dtrace.c:73
#19 0x006e9826 in zend_call_function (fci=0x7ffe8ec46b50, 
fci_cache=0x0, fci_cache@entry=0x7ffe8ec46b20) at 
/build/php5-5.6.29+dfsg/Zend/zend_execute_API.c:831
#20 0x0060f4f3 in zif_call_user_func_array (ht=, 
return_value=0x2722e68, return_value_ptr=, 
this_ptr=, return_value_used=)

at /build/php5-5.6.29+dfsg/ext/standard/basic_functions.c:4790
#21 0x006e7aea in dtrace_execute_internal 
(execute_data_ptr=, fci=, 
return_value_used=) at 
/build/php5-5.6.29+dfsg/Zend/zend_dtrace.c:9

Bug#833543: marked as done (Error in package dependencies results in regular cron email alerts)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #833543,
regarding Error in package dependencies results in regular cron email alerts
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.)


-- 
833543: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833543
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-common
Version: 5.6.24+dfsg-0+deb8u1

After uninstalling apache and most php packages from an installation, I
get an email every 30 minutes from cron:


From: root@[...] (Cron Daemon)
To: root@[...]
Subject: Cron[ -x /usr/lib/php5/sessionclean ] &&
/usr/lib/php5/sessionclean

/usr/lib/php5/sessionclean: 34: /usr/lib/php5/sessionclean: php5: not found


The leftover php packages are:
$ dpkg -l *php* | grep ^ii
ii  php5-apcu 4.0.7-1  amd64APC User
Cache for PHP 5
ii  php5-common   5.6.24+dfsg-0+deb8u1 amd64Common
files for packages built from the php5 source

The installation has never had any package conflicts.

This looks to me like the php5-common debian package requires an
executable php5 to be present, but neither provides this executable nor
depends on another package that provides it.

Of course my personal solution is to also uninstall php5-common, but I
think the missing dependency here should be addressed.
--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm

Dear submitter,

as the package php5 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/841781

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)--- End Message ---

Bug#805591: marked as done (php5: Segmentation fault on new DateTimeZone('leap-seconds.list'))

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #805591,
regarding php5: Segmentation fault on new DateTimeZone('leap-seconds.list')
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.)


-- 
805591: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805591
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-common
Version: 5.6.15+dfsg-1
Severity: normal

Dear Maintainer,

I have a script that loops through all of the DateTimeZone identifiers and
creates a DateTimeZone instance of each one for use later in the script.

The Debian package returns an extra timezone identifier "leap-seconds.list"
that causes a segfault when you try to instanciate the object.

Test script:

  ,
tz_wrapper=tz_wrapper@entry=0x467830 )
  at /tmp/buildd/php5-5.6.15+dfsg/ext/date/lib/parse_date.c:788
  #6  0x0046727a in timezone_initialize (tzobj=0x77fc7638,
tz=0x77ec5079 "", tz_len=17) at
/tmp/buildd/php5-5.6.15+dfsg/ext/date/php_date.c:3713
  #7  0x004673aa in zim_DateTimeZone___construct (ht=1,
return_value=, return_value_ptr=,
this_ptr=0x77fc5900, return_value_used=) at
/tmp/buildd/php5-5.6.15+dfsg/ext/date/php_date.c:3758
  #8  0x006daf2a in dtrace_execute_internal
(execute_data_ptr=, fci=,
return_value_used=) at
/tmp/buildd/php5-5.6.15+dfsg/Zend/zend_dtrace.c:97
  #9  0x0079a657 in zend_do_fcall_common_helper_SPEC
(execute_data=) at
/tmp/buildd/php5-5.6.15+dfsg/Zend/zend_vm_execute.h:560
  #10 0x00729680 in execute_ex
(execute_data=execute_data@entry=0x77f92190)
at /tmp/buildd/php5-5.6.15+dfsg/Zend/zend_vm_execute.h:363
  #11 0x006dadd1 in dtrace_execute_ex (execute_data=0x77f92190)
at /tmp/buildd/php5-5.6.15+dfsg/Zend/zend_dtrace.c:73
  #12 0x006ed8e0 in zend_execute_scripts (type=type@entry=8,
retval=retval@entry=0x0, file_count=file_count@entry=3) at
/tmp/buildd/php5-5.6.15+dfsg/Zend/zend.c:1341
  #13 0x006889c0 in php_execute_script
(primary_file=primary_file@entry=0x7fffce40) at
/tmp/buildd/php5-5.6.15+dfsg/main/main.c:2597
  #14 0x0079c5a1 in do_cli (argc=2, argv=0xeb0e70) at
/tmp/buildd/php5-5.6.15+dfsg/sapi/cli/php_cli.c:994
  #15 0x0046237e in main (argc=2, argv=0xeb0e70) at
/tmp/buildd/php5-5.6.15+dfsg/sapi/cli/php_cli.c:1378


-- Package-specific info:
 Additional PHP 5 information 

 PHP 5 SAPI (php5query -S): 
cli
fpm

 PHP 5 Extensions (php5query -M -v): 
opcache (Enabled for cli by local administrator)
opcache (Enabled for fpm by local administrator)
mysql (Enabled for cli by maintainer script)
mysql (Enabled for fpm by maintainer script)
xmlrpc (Enabled for cli by maintainer script)
xmlrpc (Enabled for fpm by maintainer script)
mysqli (Enabled for cli by maintainer script)
mysqli (Enabled for fpm by maintainer script)
xsl (Enabled for cli by maintainer script)
xsl (Enabled for fpm by maintainer script)
json (Enabled for cli by maintainer script)
json (Enabled for fpm by maintainer script)
mysqlnd (Enabled for cli by maintainer script)
mysqlnd (Enabled for fpm by maintainer script)
No module matches xdebug
No module matches xdebug
pdo_mysql (Enabled for cli by maintainer script)
pdo_mysql (Enabled for fpm by maintainer script)
memcached (Enabled for cli by local administrator)
memcached (Enabled for fpm by local administrator)
curl (Enabled for cli by maintainer script)
curl (Enabled for fpm by maintainer script)
readline (Enabled for cli by maintainer script)
readline (Enabled for fpm by maintainer script)
pdo (Enabled for cli by maintainer script)
pdo (Enabled for fpm by maintainer script)

 Configuration files: 
 /etc/php5/mods-available/pdo.ini 
extension=pdo.so

 /etc/php5/mods-available/opcache.ini 
zend_extension=opcache.so


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500,
'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/6 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages php5 depends on:
ii  php5-common  5.6.15+dfsg-1
ii  php5-fpm 5.6.15+dfsg-1

php5 recommends no packages.

php5 suggests no packages.

Versions of packages php5-common depends on:
ii  libc6   2.19-22
ii  lsof4.89+dfsg-0.1
ii  psmisc  22.21-2.1
ii  sed 4.2.2-6.1
ii  ucf 

Bug#814907: marked as done (php5-fpm.service: Got notification message from PID X, but reception only permitted for main PID Y)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:05:30 +
with message-id 
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #814907,
regarding php5-fpm.service: Got notification message from PID X, but reception 
only permitted for main PID Y
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.)


-- 
814907: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814907
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-fpm
Severity: minor

I started to see this message in the syslog from php5-fpm recently.
This looks the same instance as bug #809035:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809035

which involves sd_notify() with forked processes.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (900, 'unstable'), (800, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm

Dear submitter,

as the package php5 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/841781

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)--- End Message ---

Bug#845633: marked as done (RM: custom-printf -- RoM; FTBFS; abandoned upstream)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:14:59 +
with message-id 
and subject line Bug#845633: Removed package(s) from unstable
has caused the Debian Bug report #845633,
regarding RM: custom-printf -- RoM; FTBFS; abandoned upstream
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.)


-- 
845633: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845633
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
X-Debbugs-CC: debian-ocaml-ma...@lists.debian.org

please remove custom-printf. It has been abandoned upstream and has been
replaced by ppx_custom_printf which is not yet in the archive.
custom-printf can no longer be built because libsexplib-camlp4-dev is no
longer available (see #843317).

Cheers,
-Hilko
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

custom-printf | 113.00.00-1 | source
libcustom-printf-camlp4-dev | 113.00.00-1 | amd64, arm64, armel, armhf, 
hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, 
powerpc, ppc64el, s390x

--- Reason ---
RoM; FTBFS; abandoned upstream
--

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 845...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/845633

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)--- End Message ---

Bug#843317: marked as done (FTBFS: libsexplib-camlp4-dev is no longer available)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:15:02 +
with message-id 
and subject line Bug#845633: Removed package(s) from unstable
has caused the Debian Bug report #843317,
regarding FTBFS: libsexplib-camlp4-dev is no longer available
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.)


-- 
843317: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843317
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sexplib310
Version: 113.33.03-3
Severity: serious

Hi,

Your package no longer builds libsexplib-camlp4-dev, and the
new libsexplib-ocaml-dev doesn't provide it. This would be
fine if it weren't for the number of reverse dependencies
that build-depend on it:

* source package sexplib310 version 113.33.03-3 no longer builds
  binary package(s): libsexplib-camlp4-dev
  on 
amd64,arm64,armel,armhf,i386,kfreebsd-amd64,kfreebsd-i386,mips,mips64el,mipsel,powerpc,ppc64el,s390x
  - suggested command:
dak rm -m "[auto-cruft] NBS (no longer built by sexplib310)" -s unstable -a 
amd64,arm64,armel,armhf,i386,kfreebsd-amd64,kfreebsd-i386,mips,mips64el,mipsel,powerpc,ppc64el,s390x
 -p -R -b libsexplib-camlp4-dev
  - broken Depends:
janest-core: libcore-ocaml-dev [amd64 arm64 armel armhf i386 kfreebsd-amd64 
kfreebsd-i386 powerpc]
  - broken Build-Depends:
custom-printf: libsexplib-camlp4-dev
janest-core: libsexplib-camlp4-dev
janest-core-extended: libsexplib-camlp4-dev
janest-core-kernel: libsexplib-camlp4-dev
ocaml-re2: libsexplib-camlp4-dev
ocaml-textutils: libsexplib-camlp4-dev
otags: libsexplib-camlp4-dev
pa-structural-sexp: libsexplib-camlp4-dev
pa-test: libsexplib-camlp4-dev
typerep: libsexplib-camlp4-dev

Please file bugs against those (or fix them directly if you maintain
them) or make libsexplib-ocaml-dev provide libsexplib-camlp4-dev.

Cheers,
Emilio

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500, 
'unstable-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Version: 113.00.00-1+rm

Dear submitter,

as the package custom-printf 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/845633

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)--- End Message ---

Bug#845632: marked as done (RM: pa-test -- RoM; FTBFS; abandoned upstream)

[Debian Bug Tracking System]

Your message dated Fri, 13 Jan 2017 13:17:56 +
with message-id 
and subject line Bug#845632: Removed package(s) from unstable
has caused the Debian Bug report #845632,
regarding RM: pa-test -- RoM; FTBFS; abandoned upstream
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.)


-- 
845632: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845632
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
X-Debbugs-CC: debian-ocaml-ma...@lists.debian.org

Hi,

please remove pa-test. It has been abandoned upstream and has been
replaced by ppx_assert which is not yet in the archive. pa-test can no
longer be built because libsexplib-camlp4-dev is no longer available
(see #843316).

Cheers,
-Hilko
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libpa-test-camlp4-dev | 112.24.00-2 | amd64, arm64, armel, armhf, hurd-i386, 
i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, 
s390x
   pa-test | 112.24.00-2 | source

--- Reason ---
RoM; FTBFS; abandoned upstream
--

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 845...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/845632

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)--- End Message ---