Bug#823652: cargo: FTBFS: cargo.rs:88:15: 88:29 error: Cannot declare a non-inline module inside a block unless it has a path attribute

2016-05-06 Thread Chris Lamb
Source: cargo
Version: 0.8.0-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

cargo fails to build from source in unstable/amd64:

  [..]

  cargo:git2:url:uuid:rand:advapi32-sys:  PROFILE="release" 
TARGET="x86_64-unknown-linux-gnu" 
CARGO_MANIFEST_DIR="/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/advapi32-sys-0.1.2"
 
OUT_DIR="/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/"
 CARGO_PKG_VERSION_MAJOR="0" CARGO_PKG_VERSION="0.1.2" 
CARGO_PKG_VERSION_PATCH="2" HOST="x86_64-unknown-linux-gnu" 
PATH="/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11" DEBUG="0" OPT_LEVEL="0" 
CARGO_PKG_VERSION_MINOR="1" NUM_JOBS="1" CARGO_PKG_VERSION_PRE="" rustc 
/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/advapi32-sys-0.1.2/build.rs
 --crate-name build_script_advapi32_sys --crate-type bin -C 
extra-filename=-0_1_2 --out-dir 
/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/ 
--emit=dep-info,link --target x86_64-unknown-linux-gnu -L 
/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/ -L 
/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps//lib 
--extern 
winapi_build=/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/libwinapi_build-0_1_1.rlib
 --extern 
winapi=/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/libwinapi-0_2_5.rlib
  cargo:git2:url:uuid:rand:advapi32-sys: cd 
/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/advapi32-sys-0.1.2
 &&  PROFILE="release" TARGET="x86_64-unknown-linux-gnu" 
CARGO_MANIFEST_DIR="/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/advapi32-sys-0.1.2"
 
OUT_DIR="/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/"
 CARGO_PKG_VERSION_MAJOR="0" CARGO_PKG_VERSION="0.1.2" 
CARGO_PKG_VERSION_PATCH="2" HOST="x86_64-unknown-linux-gnu" 
PATH="/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11" DEBUG="0" OPT_LEVEL="0" 
CARGO_PKG_VERSION_MINOR="1" NUM_JOBS="1" CARGO_PKG_VERSION_PRE="" 
/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/build_script_advapi32_sys-0_1_2
  cargo:git2:url:uuid:rand:advapi32-sys:  PROFILE="release" 
TARGET="x86_64-unknown-linux-gnu" 
CARGO_MANIFEST_DIR="/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/advapi32-sys-0.1.2"
 
OUT_DIR="/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/"
 CARGO_PKG_VERSION_MAJOR="0" CARGO_PKG_VERSION="0.1.2" 
CARGO_PKG_VERSION_PATCH="2" HOST="x86_64-unknown-linux-gnu" 
PATH="/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11" DEBUG="0" OPT_LEVEL="0" 
CARGO_PKG_VERSION_MINOR="1" NUM_JOBS="1" CARGO_PKG_VERSION_PRE="" rustc 
/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/advapi32-sys-0.1.2/src/lib.rs
 --crate-name advapi32 --crate-type lib -C extra-filename=-0_1_2 --out-dir 
/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/ 
--emit=dep-info,link --target x86_64-unknown-linux-gnu -L 
/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/ -L 
/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps//lib 
--extern 
winapi_build=/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/libwinapi_build-0_1_1.rlib
 --extern 
winapi=/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/libwinapi-0_2_5.rlib
  
  cargo:git2:url:uuid:rand: Building rand-0.3.13 (needed by: uuid-0.1.18)
  cargo:git2:url:uuid:rand:  PROFILE="release" 
TARGET="x86_64-unknown-linux-gnu" 
CARGO_MANIFEST_DIR="/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/rand-0.3.13"
 
OUT_DIR="/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/"
 CARGO_PKG_VERSION_MAJOR="0" CARGO_PKG_VERSION="0.3.13" 
CARGO_PKG_VERSION_PATCH="13" HOST="x86_64-unknown-linux-gnu" 
PATH="/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11" DEBUG="0" OPT_LEVEL="0" 
CARGO_PKG_VERSION_MINOR="3" NUM_JOBS="1" CARGO_PKG_VERSION_PRE="" rustc 
/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/rand-0.3.13/src/lib.rs
 --crate-name rand --crate-type lib -C extra-filename=-0_3_13 --out-dir 
/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/ 
--emit=dep-info,link --target x86_64-unknown-linux-gnu -L 
/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/ -L 
/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps//lib 
--extern 
advapi32_sys=/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/libadvapi32_sys-0_1_2.rlib
 --extern 
winapi=/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/libwinapi-0_2_5.rlib
 --extern 
libc=/home/lamby/temp/cdt.20160507062340.zAH0KuArFQ.cargo/cargo-0.8.0/deps/liblibc-0_2_4.rlib
  
  cargo:git2:url:uuid:rustc-serialize: Building rustc-serializ

Bug#823653: graxxia: FTBFS: Could not resolve org.codehaus.groovy:groovy:2.3.11.

2016-05-06 Thread Chris Lamb
Source: graxxia
Version: 1.0~20150714-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

graxxia fails to build from source in unstable/amd64:

  [..]

  Adding debian:certSIGN_ROOT_CA.pem
  Adding debian:ePKI_Root_Certification_Authority.pem
  Adding debian:thawte_Primary_Root_CA.pem
  Adding debian:thawte_Primary_Root_CA_-_G2.pem
  Adding debian:thawte_Primary_Root_CA_-_G3.pem
  done.
  done.
  Setting up openjdk-8-jre-headless:amd64 (8u91-b14-2) ...
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/rmid to 
provide /usr/bin/rmid (rmid) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java to 
provide /usr/bin/java (java) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/keytool 
to provide /usr/bin/keytool (keytool) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/jjs to 
provide /usr/bin/jjs (jjs) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/pack200 
to provide /usr/bin/pack200 (pack200) in auto mode
  update-alternatives: using 
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/rmiregistry to provide 
/usr/bin/rmiregistry (rmiregistry) in auto mode
  update-alternatives: using 
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/unpack200 to provide 
/usr/bin/unpack200 (unpack200) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/orbd to 
provide /usr/bin/orbd (orbd) in auto mode
  update-alternatives: using 
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/servertool to provide 
/usr/bin/servertool (servertool) in auto mode
  update-alternatives: using 
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/tnameserv to provide 
/usr/bin/tnameserv (tnameserv) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/jexec to 
provide /usr/bin/jexec (jexec) in auto mode
  Setting up default-jre-headless (2:1.8-57) ...
  Setting up openjdk-8-jre:amd64 (8u91-b14-2) ...
  update-alternatives: using 
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/policytool to provide 
/usr/bin/policytool (policytool) in auto mode
  Setting up default-jre (2:1.8-57) ...
  Setting up openjdk-8-jdk-headless:amd64 (8u91-b14-2) ...
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/idlj to 
provide /usr/bin/idlj (idlj) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jdeps to 
provide /usr/bin/jdeps (jdeps) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/wsimport to 
provide /usr/bin/wsimport (wsimport) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/rmic to 
provide /usr/bin/rmic (rmic) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jinfo to 
provide /usr/bin/jinfo (jinfo) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jsadebugd to 
provide /usr/bin/jsadebugd (jsadebugd) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/native2ascii 
to provide /usr/bin/native2ascii (native2ascii) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jstat to 
provide /usr/bin/jstat (jstat) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/javadoc to 
provide /usr/bin/javadoc (javadoc) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/javah to 
provide /usr/bin/javah (javah) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jstack to 
provide /usr/bin/jstack (jstack) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jrunscript 
to provide /usr/bin/jrunscript (jrunscript) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/javac to 
provide /usr/bin/javac (javac) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jhat to 
provide /usr/bin/jhat (jhat) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/javap to 
provide /usr/bin/javap (javap) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jar to 
provide /usr/bin/jar (jar) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/xjc to 
provide /usr/bin/xjc (xjc) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/schemagen to 
provide /usr/bin/schemagen (schemagen) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jps to 
provide /usr/bin/jps (jps) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/extcheck to 
provide /usr/bin/extcheck (extcheck) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jmap to 
provide /usr/bin/jmap (jmap) in auto mode
  update-alternati

Bug#821484: Bumping severity of PHP 7.0 transition bugs to serious

2016-05-06 Thread Sunil Mohan Adapa
On 05/07/2016 02:05 AM, James Valleroy wrote:
> tags 821484 patch
> thanks
> 
> The attached patch will simply switch from PHP 5 to PHP 7.0.
> 

The patch looks correct but insufficient.  Here are my notes:

- ownCloud depends on php5 but is being removed.

- tt-rss seems to work okay with php7.  Faced some weird issues during
installation, probably unrelated.

- Shaarli is still dependent on php5 modules but seems to work with php7.

- Roundcube seems to have problem with php7 but upstream supports php7
in 1.2beta (unreleased and not yet available in Debian).

- Php7 module is not enabled in freedombox-setup for people upgrading
from an earlier version.

I have applied the patch and marked that it closes the bug.  However, we
need to address the issue of enabling php7 module for upgrading users.
I propose that we add 'a2enmod php7.0' to post-install.  What do you think?

-- 
Sunil



signature.asc
Description: OpenPGP digital signature


Bug#823647: sshuttle package in stretch/sid builds only documentation, no executable

2016-05-06 Thread Robert Lange
You are correct. I have Python 3.4 installed. Rebuilding on a system with 
Python 3.5 worked as expected. Apparently if the X-Python-Version is not 
satisfied, the build gives no fatal errors and appears to work, while not 
actually building the package properly. But that's a bug for the build system, 
not this package.

On 2016-05-06 21:08, Axel Beckert wrote:
> Control: tag -1 + unreproducible moreinfo
>
> Hi Robert,
>
> Robert Lange wrote:
>> Package: sshuttle
>> Version: 0.78.0-1~bpo8+1
>> Severity: grave
> […]
>> I tried to make a backport of sshuttle for jessie using stretch
>> sources.
> This seems to be an issue with your backporting. Because the package
> builds fine on Debian Sid.
>
> Maybe this line from debian/control needs to be changed for
> backporting, too:
>
>   X-Python3-Version: >= 3.5
>
>   Regards, Axel



Bug#823043: zsh FTBFS since yodl 3.08.00-1 in the same way that c++-annotations FTBFSed with 3.07.00-1 (was: Re: Bug#823043 closed by f.b.brok...@rug.nl (Frank B. Brokken) (Bug#823043: fixed in yodl 3

2016-05-06 Thread Frank B. Brokken
Dear Axel Beckert, you wrote:

> Hi Frank,

Hi Axel,

You wrote:

> I'm not 100% sure what's going on, but it seems to me that while
> c++-annotations indeed FTBFS with 3.07.00-1 and builds fine again with
> 3.08.00-1 (verified it :-), it's the opposite way round with zsh:
> 
> It builds fine with yodl 3.07.00-1, but FTBFS with 3.08.00-1 as
> follows:
> 
> ...Zsh Yodl-to-man converter
> Including file Zsh/zftpsys.yo
> yodl -k -L -o ../../Doc/zshzle.1 -I../../Doc:. -w zman.yo version.yo
> ../../Doc/zshzle.yo
> Zsh Yodl-to-man converter
> Including file Zsh/zle.yo
> yodl -k -L -o ../../Doc/zshall.1 -I../../Doc -DZSHALL -w zman.yo version.yo 
> zsh.yo
> `ZSHALL' (symbol) multiply defined
> `ZSHALL' (symbol) multiply defined
> `ZSHALL' (symbol) multiply defined
> Error(s) in command line arguments. Terminating
> ...

Thanks for reporting this bug: I just downloaded the zsh source package and
can reproduce the error. I'll have a look at what's going, and report back to
you once I know more.

Cheers,

-- 
Frank B. Brokken
Center for Information Technology, University of Groningen
(+31) 50 363 9281 
Public PGP key: http://pgp.surfnet.nl
Key Fingerprint: DF32 13DE B156 7732 E65E  3B4D 7DB2 A8BE EAE4 D8AA


signature.asc
Description: PGP signature


Bug#823651: pbuilder: fails to make temp file - breaks

2016-05-06 Thread Norbert Preining
Package: pbuilder
Version: 0.224
Severity: grave
Justification: renders package unusable

Dear all,

the recent changes in /tmp handling seem to have made
cowbuilder/pbuilder unable to build any package:

$ cowbuilder --build foobar.dsc
...
 This package was created automatically by pbuilder to satisfy the
  build-dependencies of the package being currently built.
Depends: 
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
dpkg-deb: error: failed to make temporary file (control member): No such file 
or directory
E: pbuilder-satisfydepends failed.

I am not sure where the fix should be, though.

Thanks

Norbert

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

Kernel: Linux 4.6.0-rc6+ (SMP w/4 CPU cores; PREEMPT)
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 pbuilder depends on:
ii  debconf [debconf-2.0]  1.5.59
ii  debootstrap1.0.81
ii  dpkg-dev   1.18.6
ii  wget   1.17.1-2

Versions of packages pbuilder recommends:
ii  devscripts  2.16.4
ii  fakeroot1.20.2-1
ii  iproute24.3.0-1+b1
ii  net-tools   1.60+git20150829.73cef8a-2
ii  sudo1.8.15-1.1

Versions of packages pbuilder suggests:
ii  cowdancer   0.79
ii  gdebi-core  0.9.5.7

-- debconf information:
  pbuilder/mirrorsite: http://ftp.jaist.ac.jp/debian/
  pbuilder/rewrite: false
  pbuilder/nomirror:



Bug#823647: sshuttle package in stretch/sid builds only documentation, no executable

2016-05-06 Thread Axel Beckert
Control: tag -1 + unreproducible moreinfo

Hi Robert,

Robert Lange wrote:
> Package: sshuttle
> Version: 0.78.0-1~bpo8+1
> Severity: grave
[…]
> I tried to make a backport of sshuttle for jessie using stretch
> sources.

This seems to be an issue with your backporting. Because the package
builds fine on Debian Sid.

Maybe this line from debian/control needs to be changed for
backporting, too:

  X-Python3-Version: >= 3.5

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Processed: Re: Bug#823647: sshuttle package in stretch/sid builds only documentation, no executable

2016-05-06 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 + unreproducible moreinfo
Bug #823647 [sshuttle] sshuttle package in stretch/sid builds only 
documentation, no executable
Added tag(s) unreproducible and moreinfo.

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



Bug#823647: sshuttle package in stretch/sid builds only documentation, no executable

2016-05-06 Thread Robert Lange
Package: sshuttle
Version: 0.78.0-1~bpo8+1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I tried to make a backport of sshuttle for jessie using stretch sources. I did
the usual package build steps:

apt-get source sshuttle
cd sshuttle-0.78.0/
dch --bpo
sudo apt-get build-dep sshuttle
debuild -sa -uc -us

The package built without any fatal errors and produced a deb. The following is
the build output:

(jessie-amd64-sbuild)rlange@iset:~/debsrc/sshuttle/sshuttle-0.78.0$ debuild -sa
-uc -us
 dpkg-buildpackage -rfakeroot -D -us -uc -sa
dpkg-buildpackage: source package sshuttle
dpkg-buildpackage: source version 0.78.0-1~bpo8+1
dpkg-buildpackage: source distribution jessie-backports
dpkg-buildpackage: source changed by Robert Lange 
 dpkg-source --before-build sshuttle-0.78.0
dpkg-buildpackage: host architecture amd64
 fakeroot debian/rules clean
dh clean --with python3,sphinxdoc --buildsystem=pybuild
   dh_testdir -O--buildsystem=pybuild
   dh_auto_clean -O--buildsystem=pybuild
   debian/rules override_dh_clean
make[1]: Entering directory '/home/rlange/debsrc/sshuttle/sshuttle-0.78.0'
dh_clean
rm -rf tmp
rm -rf docs/.build docs/_build
make[1]: Leaving directory '/home/rlange/debsrc/sshuttle/sshuttle-0.78.0'
 dpkg-source -b sshuttle-0.78.0
dpkg-source: info: using source format `3.0 (quilt)'
dpkg-source: info: building sshuttle using existing
./sshuttle_0.78.0.orig.tar.gz
dpkg-source: info: building sshuttle in sshuttle_0.78.0-1~bpo8+1.debian.tar.xz
dpkg-source: info: building sshuttle in sshuttle_0.78.0-1~bpo8+1.dsc
 debian/rules build
dh build --with python3,sphinxdoc --buildsystem=pybuild
   dh_testdir -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
   debian/rules override_dh_auto_build
make[1]: Entering directory '/home/rlange/debsrc/sshuttle/sshuttle-0.78.0'
dh_auto_build
PYTHONPATH=. sphinx-build -b html -d docs/.build/.doctrees -N docs
docs/.build/html
Making output directory...
Running Sphinx v1.2.3
loading pickled environment... failed: [Errno 2] No such file or directory:
'/home/rlange/debsrc/sshuttle/sshuttle-0.78.0/docs/.build/.doctrees/environment.pickle'
building [html]: targets for 13 source files that are out of date
updating environment: 13 added, 0 changed, 0 removed
reading sources... [  7%] changes
reading sources... [ 15%] how-it-works
reading sources... [ 23%] index
reading sources... [ 30%] installation
reading sources... [ 38%] manpage
reading sources... [ 46%] overview
reading sources... [ 53%] platform
reading sources... [ 61%] requirements
reading sources... [ 69%] support
reading sources... [ 76%] tproxy
reading sources... [ 84%] trivia
reading sources... [ 92%] usage
reading sources... [100%] windows

looking for now-outdated files... none found
pickling environment... done
checking consistency... done
preparing documents... done
writing output... [  7%] changes
writing output... [ 15%] how-it-works
writing output... [ 23%] index
writing output... [ 30%] installation
writing output... [ 38%] manpage
writing output... [ 46%] overview
writing output... [ 53%] platform
writing output... [ 61%] requirements
writing output... [ 69%] support
writing output... [ 76%] tproxy
writing output... [ 84%] trivia
writing output... [ 92%] usage
writing output... [100%] windows

writing additional files... genindex search
copying static files... WARNING: html_static_path entry
'/home/rlange/debsrc/sshuttle/sshuttle-0.78.0/docs/_static' does not exist
done
copying extra files... done
dumping search index... done
dumping object inventory... done
build succeeded, 1 warning.
PYTHONPATH=. sphinx-build -b man -d docs/.build/.doctrees -N docs
docs/.build/man
Making output directory...
Running Sphinx v1.2.3
loading pickled environment... done
building [man]: all manpages
updating environment: 0 added, 0 changed, 0 removed
looking for now-outdated files... none found
writing... sshuttle.1 { }
build succeeded.
make[1]: Leaving directory '/home/rlange/debsrc/sshuttle/sshuttle-0.78.0'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/home/rlange/debsrc/sshuttle/sshuttle-0.78.0'
PYTHONPATH=. \
dh_auto_test -- --system=custom --test-args="{interpreter} -m pytest"
make[1]: Leaving directory '/home/rlange/debsrc/sshuttle/sshuttle-0.78.0'
 fakeroot debian/rules binary
dh binary --with python3,sphinxdoc --buildsystem=pybuild
   dh_testroot -O--buildsystem=pybuild
   dh_prep -O--buildsystem=pybuild
dh_installdirs -O--buildsystem=pybuild
   dh_auto_install -O--buildsystem=pybuild
   dh_install -O--buildsystem=pybuild
   dh_installdocs -O--buildsystem=pybuild
   dh_sphinxdoc -O--buildsystem=pybuild
   dh_installchangelogs -O--buildsystem=pybuild
   dh_installman -O--buildsystem=pybuild
   dh_python3 -O--buildsystem=pybuild
   dh_perl -O--buildsystem=pybuild
   dh_link -O--buildsystem=pybuild
   dh_compress -O--buildsystem=pybuild
   dh_fixperms -O--buildsystem=pybuild
   dh_installdeb -O--buildsystem=pybuild
   dh_gencontrol -O--buildsystem=pybuil

Bug#823465: dpkg: Won't run at all on i586 Pentium MMX due to illegal instruction

2016-05-06 Thread Pierre Ynard
Yes, I run unstable in production. My stuff isn't business-critical.
But I can say the same thing about this making it impossible to run
unstable. That's not the idea I'd like to have about Debian. If I wanted
a distro where unstable is broken and unusable, I would have installed
 long ago.

I don't care too much that the change is "silent", since I'm here and
know now. That's nice to document the next release, but I was asking for
an answer to my problem now. What do I do with my i586 system running
unstable of last week? Drop it into a tub of water, just like i586
support is getting dropped? That's going to cause way more downtime than
simply running unstable in production.

My "complaint" against unstable is valid. Typical Debian bugs don't
(or at least shouldn't) wait for the stable release to get fixed. I
don't see why you retitled this copy of the bug, since it described the
situation accurately. i586 users running unstable are getting their
system broken, with no obvious way to handle it. Maybe I'm the only such
user and you don't care, then at least have the decency to wontfix me.

Please tell me, what do I do with it??

-- 
Pierre Ynard
"Une âme dans un corps, c'est comme un dessin sur une feuille de papier."



Bug#786611: Info received (Patch, new maintainer request)

2016-05-06 Thread Julia Longtin
When testing this patch, i found that i had forgotten an earlier patch,
from a different source. Attached.

Julia Longtin
diff -ur iscsitarget/kernel/conn.c iscsitarget.patched/kernel/conn.c
--- iscsitarget/kernel/conn.c	2015-05-05 18:11:24.0 +
+++ iscsitarget.patched/kernel/conn.c	2015-05-05 18:01:40.0 +
@@ -127,7 +127,7 @@
 
 	dprintk(D_GENERIC, "%llu\n", (unsigned long long) session->sid);
 
-	conn->sock = SOCKET_I(conn->file->f_dentry->d_inode);
+	conn->sock = SOCKET_I(conn->file->f_path.dentry->d_inode);
 	conn->sock->sk->sk_user_data = conn;
 
 	write_lock_bh(&conn->sock->sk->sk_callback_lock);
diff -ur iscsitarget/kernel/file-io.c iscsitarget.patched/kernel/file-io.c
--- iscsitarget/kernel/file-io.c	2015-05-05 18:11:24.0 +
+++ iscsitarget.patched/kernel/file-io.c	2015-05-05 18:03:10.0 +
@@ -69,7 +69,7 @@
 static int fileio_sync(struct iet_volume *lu, struct tio *tio)
 {
 	struct fileio_data *p = lu->private;
-	struct inode *inode = p->filp->f_dentry->d_inode;
+	struct inode *inode = p->filp->f_path.dentry->d_inode;
 	struct address_space *mapping = inode->i_mapping;
 	loff_t ppos, count;
 	int res;
@@ -213,7 +213,7 @@
 		eprintk("%d\n", err);
 		goto out;
 	}
-	inode = p->filp->f_dentry->d_inode;
+	inode = p->filp->f_path.dentry->d_inode;
 
 	if (S_ISREG(inode->i_mode))
 		;
diff -ur iscsitarget/kernel/iscsi.c iscsitarget.patched/kernel/iscsi.c
--- iscsitarget/kernel/iscsi.c	2015-05-05 18:11:24.0 +
+++ iscsitarget.patched/kernel/iscsi.c	2015-05-05 17:59:39.0 +
@@ -986,9 +986,6 @@
 		set_cmnd_lunit(req);
 
 	switch (req_hdr->scb[0]) {
-	case SERVICE_ACTION_IN:
-		if ((req_hdr->scb[1] & 0x1f) != 0x10)
-			goto error;
 	case INQUIRY:
 	case REPORT_LUNS:
 	case TEST_UNIT_READY:
diff -ur iscsitarget/kernel/target_disk.c iscsitarget.patched/kernel/target_disk.c
--- iscsitarget/kernel/target_disk.c	2015-05-05 18:11:24.0 +
+++ iscsitarget.patched/kernel/target_disk.c	2015-05-05 18:04:09.0 +
@@ -606,9 +606,6 @@
 	case REQUEST_SENSE:
 		send_data_rsp(cmnd, build_request_sense_response);
 		break;
-	case SERVICE_ACTION_IN:
-		send_data_rsp(cmnd, build_service_action_in_response);
-		break;
 	case READ_6:
 	case READ_10:
 	case READ_16:
diff -ur iscsitarget/kernel/volume.c iscsitarget.patched/kernel/volume.c
--- iscsitarget/kernel/volume.c	2015-05-05 18:11:24.0 +
+++ iscsitarget.patched/kernel/volume.c	2015-05-05 18:02:29.0 +
@@ -398,9 +398,6 @@
 		case READ_CAPACITY:
 			/* allowed commands when reserved */
 			break;
-		case SERVICE_ACTION_IN:
-			if ((scb[1] & 0x1F) == 0x10)
-break;
 			/* fall through */
 		default:
 			err = -EBUSY;
@@ -465,9 +462,6 @@
 		if (excl_access_ro && !registered)
 			err = -EBUSY;
 		break;
-	case SERVICE_ACTION_IN:
-		if ((scb[1] & 0x1F) == 0x10)
-			break;
 		/* fall through */
 	case RELEASE:
 	case RESERVE:


signature.asc
Description: Digital signature


Bug#786611: Patch, new maintainer request

2016-05-06 Thread Julia Longtin
Hello,

I would also like to maintain this package, since my infrastructure requires it 
working.

This would be my first package (so i would have to go through new maintainer), 
but i'm very familiar with openiscsi internals. gotta keep systems working...

Attached, you can find my patch for iscsitarget working with debian's 4.5 
kernel on arm7i.

Julia Longtin
diff --git a/Makefile b/Makefile
index 32efe5e..9a841b1 100644
--- a/Makefile
+++ b/Makefile
@@ -1 +1,2 @@
+subdir-ccflags-y = -Wall -Werror
 obj-m = kernel/
diff --git a/kernel/block-io.c b/kernel/block-io.c
index 00365b5..d7222c6 100644
--- a/kernel/block-io.c
+++ b/kernel/block-io.c
@@ -29,11 +29,13 @@ struct tio_work {
 	struct completion tio_complete;
 };
 
-static void blockio_bio_endio(struct bio *bio, int error)
+/* dropped error parameter in 4.3. */
+static void blockio_bio_endio(struct bio *bio)
 {
+	int error;
 	struct tio_work *tio_work = bio->bi_private;
 
-	error = test_bit(BIO_UPTODATE, &bio->bi_flags) ? error : -EIO;
+	error = -(bio->bi_error);
 
 	if (error)
 		atomic_set(&tio_work->error, error);
@@ -68,7 +70,7 @@ blockio_make_request(struct iet_volume *volume, struct tio *tio, int rw)
 
 	/* Calculate max_pages for bio_alloc (memory saver) */
 	if (bdev_q)
-		max_pages = bio_get_nr_vecs(bio_data->bdev);
+		max_pages = BIO_MAX_PAGES;
 
 	tio_work = kzalloc(sizeof (*tio_work), GFP_KERNEL);
 	if (!tio_work)
diff --git a/kernel/conn.c b/kernel/conn.c
index 3ae6881..01bdb6f 100644
--- a/kernel/conn.c
+++ b/kernel/conn.c
@@ -87,13 +87,14 @@ static void iet_state_change(struct sock *sk)
 	target->nthread_info.old_state_change(sk);
 }
 
-static void iet_data_ready(struct sock *sk, int len)
+/* dropped len is 3.15. */
+static void iet_data_ready(struct sock *sk)
 {
 	struct iscsi_conn *conn = sk->sk_user_data;
 	struct iscsi_target *target = conn->session->target;
 
 	nthread_wakeup(target);
-	target->nthread_info.old_data_ready(sk, len);
+	target->nthread_info.old_data_ready(sk);
 }
 
 /*
diff --git a/kernel/iscsi.c b/kernel/iscsi.c
index 7f20568..432d113 100644
--- a/kernel/iscsi.c
+++ b/kernel/iscsi.c
@@ -489,8 +489,8 @@ static void cmnd_skip_pdu(struct iscsi_cmnd *cmnd)
 	}
 	conn->read_iov[i].iov_base = addr;
 	conn->read_iov[i].iov_len = size;
-	conn->read_msg.msg_iov = conn->read_iov;
-	conn->read_msg.msg_iovlen = ++i;
+	conn->read_msg.msg_iter.iov = conn->read_iov;
+	conn->read_msg.msg_iter.nr_segs = ++i;
 }
 
 static void iscsi_cmnd_reject(struct iscsi_cmnd *req, int reason)
@@ -718,7 +718,7 @@ static int cmnd_recv_pdu(struct iscsi_conn *conn, struct tio *tio, u32 offset, u
 	idx = offset >> PAGE_CACHE_SHIFT;
 	offset &= ~PAGE_CACHE_MASK;
 
-	conn->read_msg.msg_iov = conn->read_iov;
+	conn->read_msg.msg_iter.iov = conn->read_iov;
 	conn->read_size = size = (size + 3) & -4;
 	conn->read_overflow = 0;
 
@@ -730,14 +730,14 @@ static int cmnd_recv_pdu(struct iscsi_conn *conn, struct tio *tio, u32 offset, u
 		conn->read_iov[i].iov_base =  addr + offset;
 		if (offset + size <= PAGE_CACHE_SIZE) {
 			conn->read_iov[i].iov_len = size;
-			conn->read_msg.msg_iovlen = ++i;
+			conn->read_msg.msg_iter.nr_segs = ++i;
 			break;
 		}
 		conn->read_iov[i].iov_len = PAGE_CACHE_SIZE - offset;
 		size -= conn->read_iov[i].iov_len;
 		offset = 0;
 		if (++i >= ISCSI_CONN_IOV_MAX) {
-			conn->read_msg.msg_iovlen = i;
+			conn->read_msg.msg_iter.nr_segs = i;
 			conn->read_overflow = size;
 			conn->read_size -= size;
 			break;
@@ -879,6 +879,7 @@ static void scsi_cmnd_exec(struct iscsi_cmnd *cmnd)
 	}
 }
 
+/* handle a nop-out packet. */
 static int nop_out_start(struct iscsi_conn *conn, struct iscsi_cmnd *cmnd)
 {
 	u32 size, tmp;
@@ -918,7 +919,7 @@ static int nop_out_start(struct iscsi_conn *conn, struct iscsi_cmnd *cmnd)
 
 	if ((size = cmnd->pdu.datasize)) {
 		size = (size + 3) & -4;
-		conn->read_msg.msg_iov = conn->read_iov;
+		conn->read_msg.msg_iter.iov = conn->read_iov;
 		if (cmnd->pdu.bhs.itt != cpu_to_be32(ISCSI_RESERVED_TAG)) {
 			struct tio *tio;
 			int pg_cnt = get_pgcnt(size);
@@ -946,7 +947,7 @@ static int nop_out_start(struct iscsi_conn *conn, struct iscsi_cmnd *cmnd)
 		}
 		assert(!size);
 		conn->read_overflow = size;
-		conn->read_msg.msg_iovlen = i;
+		conn->read_msg.msg_iter.nr_segs = i;
 	}
 
 out:
diff --git a/kernel/iscsi.h b/kernel/iscsi.h
index 3bc687e..657e96a 100644
--- a/kernel/iscsi.h
+++ b/kernel/iscsi.h
@@ -81,7 +81,8 @@ struct network_thread_info {
 	spinlock_t nthread_lock;
 
 	void (*old_state_change)(struct sock *);
-	void (*old_data_ready)(struct sock *, int);
+  /* changes in 3.15 */
+  void (*old_data_ready)(struct sock *);
 	void (*old_write_space)(struct sock *);
 };
 
diff --git a/kernel/iscsi_hdr.h b/kernel/iscsi_hdr.h
index ec119b7..02b6f6d 100644
--- a/kernel/iscsi_hdr.h
+++ b/kernel/iscsi_hdr.h
@@ -16,6 +16,7 @@
 #define __packed __attribute__ ((packed))
 #endif
 
+/* This structure is packed so that it matches rfc3720 when transmitted over tcp. */
 struct iscsi_hdr {
 	u8  opcode;			/* 0 */
 

Processed: Link #822976 to upstream bug report

2016-05-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 822976 https://bugs.launchpad.net/unico/+bug/1579273
Bug #822976 [gtk3-engines-unico] gtk3-engines-unico: Package broken by GTK 3.16
Set Bug forwarded-to-address to 'https://bugs.launchpad.net/unico/+bug/1579273'.
> tag 822976 + upstream
Bug #822976 [gtk3-engines-unico] gtk3-engines-unico: Package broken by GTK 3.16
Added tag(s) upstream.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
822976: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822976
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#822866: marked as done (new vips lets nip2 fail to build)

2016-05-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 May 2016 23:34:01 +
with message-id 
and subject line Bug#822866: fixed in vips 8.3.0-3
has caused the Debian Bug report #822866,
regarding new vips lets nip2 fail to 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.)


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

Package: src:vips
Version: 8.2-1
Severity: serious
Tags: sid stretch

8.2-1 breaks the nip2 build, apparently not having a new dependency in the -dev 
package:


checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for REQUIRED_PACKAGES... no
configure: error: Package requirements (gthread-2.0 gtk+-2.0 >= 2.4.9 libxml-2.0 
vips >= 7.30) were not met:


Package 'poppler-glib', required by 'vips', not found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables REQUIRED_PACKAGES_CFLAGS
and REQUIRED_PACKAGES_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
/usr/share/cdbs/1/class/autotools.mk:42: recipe for target 
'debian/stamp-autotools' failed

make: *** [debian/stamp-autotools] Error 1
--- End Message ---
--- Begin Message ---
Source: vips
Source-Version: 8.3.0-3

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated vips 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, 06 May 2016 19:17:05 +
Source: vips
Binary: libvips42 libvips-dev libvips-tools python-vipscc libvips-doc 
gir1.2-vips-8.0
Architecture: source amd64 all
Version: 8.3.0-3
Distribution: unstable
Urgency: low
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 gir1.2-vips-8.0 - GObject introspection data for VIPS
 libvips-dev - image processing system good for very large images (dev)
 libvips-doc - image processing system good for very large images (doc)
 libvips-tools - image processing system good for very large images (tools)
 libvips42  - image processing system good for very large images
 python-vipscc - image processing system good for very large images (tools)
Closes: 822866 823267
Changes:
 vips (8.3.0-3) unstable; urgency=low
 .
   * Add libgif-dev, libpoppler-glib-dev and librsvg2-dev as dependency of
 libvips-dev (closes: #822866).
 .
   [ Pino Toscano  ]
   * Enable parallel building (closes: #823267).
Checksums-Sha1:
 e69123b57271aa7660b9604794c28efc03ccd765 2654 vips_8.3.0-3.dsc
 cdfe78fcb851e0a55f1a860a16127ac9fbab658a 11344 vips_8.3.0-3.debian.tar.xz
 97a2be224afd47cae3d80e59ef84038ac3e0c5f3 74596 
gir1.2-vips-8.0_8.3.0-3_amd64.deb
 df0b6b3d0d75621eb3adf8952fe68a0f48eb5f77 907728 libvips-dev_8.3.0-3_amd64.deb
 68e83385f27a1994a75a91eb70659bdf3c28baf1 270440 libvips-doc_8.3.0-3_all.deb
 59685545cdbee7f489809b2f70c2e03f93f31d45 51866 
libvips-tools-dbgsym_8.3.0-3_amd64.deb
 df30873a3874a636f5d7b7003c62128f3468ee91 91868 libvips-tools_8.3.0-3_amd64.deb
 a33e7a3fa95bb33f8d9fb6b42386bab43d0c9bb9 2693390 
libvips42-dbgsym_8.3.0-3_amd64.deb
 f6477ee1b165a2fd67b3b3073e797fcb98be8d90 717652 libvips42_8.3.0-3_amd64.deb
 58a553f0ec1e5b78cd458cdf9eabee0f59745163 1130164 
python-vipscc-dbgsym_8.3.0-3_amd64.deb
 e7713de6e6c8eb2cf17cee71524431bf878e0bae 273822 python-vipscc_8.3.0-3_amd64.deb
Checksums-Sha256:
 b93bfa936ed151416fe2745e1e1b9e843880695a69f44559a2596dea837da337 2654 
vips_8.3.0-3.dsc
 73153cf098bb56a9b74f517bba09cca33adc1a6f4e5ae9ed34097360a91ca1fb 11344 
vips_8.3.0-3.debian.tar.xz
 a5616ac23f8cfe6431c0eb2247cd7a37139ca39897ae5146fad0a880cc0a7d34 74596 
gir1.2-vips-8.0_8.3.0-3_amd64.deb
 374807ea659b8f9a224a9963966775947b9467bb74d491f6ffdd4dcea23bea50 907728 
libvips-dev_8.3.0-3_amd64.deb
 c4521983e5ba05e0a18da2a27864a5e6008d60de5dd0ed4e406bbbce160b1de4 270440 
libvips-doc_8.3.0-3_all.deb
 46c84d24594c0110c4593c038fe939711a2a1f0557e9

Bug#823644: [patch] missing b-d on libjzlib-java

2016-05-06 Thread Matthias Klose

Package: src:jruby
Version: 1.7.22-2
Severity: serious
Tags: sid stretch patch

The package fails to build, libjzlib-java is needed as a *build* dependency as 
well.

patch at
http://launchpadlibrarian.net/258252483/jruby_1.7.22-2_1.7.22-2ubuntu1.diff.gz



Bug#795844: marked as done (armel and armhf images missing kernel and initramfs)

2016-05-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 May 2016 22:19:20 +
with message-id 
and subject line Bug#795844: fixed in debian-cd 3.1.18
has caused the Debian Bug report #795844,
regarding armel and armhf images missing kernel and initramfs
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.)


-- 
795844: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795844
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cdimage.debian.org
Severity: serious
Tags: d-i

As mentioned by bwh: existing armel and armhf installer CDs are
currently missing vmlinuz and the initramfs...

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
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)
--- End Message ---
--- Begin Message ---
Source: debian-cd
Source-Version: 3.1.18

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

Debian distribution maintenance software
pp.
Steve McIntyre <93...@debian.org> (supplier of updated debian-cd 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: Mon, 20 Apr 2015 12:36:57 +0100
Source: debian-cd
Binary: debian-cd
Architecture: source all
Version: 3.1.18
Distribution: unstable
Urgency: medium
Maintainer: Debian CD Group 
Changed-By: Steve McIntyre <93...@debian.org>
Description:
 debian-cd  - Tools for building (Official) Debian CD set
Closes: 744155 768977 783569 795844 798908 808958 809497 809698 818176 820479
Changes:
 debian-cd (3.1.18) unstable; urgency=medium
 .
   [ Steve McIntyre ]
   * Start stretch, simply copying jessie for now
   * Remove mention of desktop choice from yaboot boot messages
 (Closes: #783569)
   * Add YA syslinux package to Recommends.
   * Fix handlinkg of LOGOPNG when we've got "doppelganer" initramfs files
   * Add support for debian-edu builds
   * Change cpp usage in the Makefile to make error handling more reliable
   * tools/sort_deps: Improve handling of too-large packages. Previously,
 the code would only check sizes for packages explicitly listed but
 packages brought in due to dependency resolution would not be
 checked. Now fixed.
   * Try to make VOLIDs shorter when given long alpha / beta release names
 in DEBVERSION
   * Add firmware bundles in cpio.gz format too to help netboot users.
 Thanks to Alex Owen for the patch, slightly tweaked.
   * Add kernels and other bits to armel/armhf images (Closes: #795844)
   * Do similar for mips images, now r4k-ip22 cdrom images are no longer
 built.
   * Remove old obsolete pre-d-i function install_language and all callers.
   * parse_isolinux: Support grub menuentry shortcuts for UEFI boot menus.
 Closes: #798908
   * Create checksums for firmware images
   * Switch references to d-i.debian.org to use https instead of http.
 Closes: #809698. Also use --ca-directory /etc/ssl/ca-debian/ with wget
 to ensure this works.
   * Add Recommends: syslinux-utils in case a user wants to use SPLASHPNG
 (and hence ppmtolss16) for their own splash images. Closes: #768977
   * Update Standards-Version to 3.9.6
 .
   [ Didier Raboud ]
   * For stretch, swap amd64 and i386 to let the first be the norm, and the
 latter be the special case, this copes with the similar change in d-i
   * Add management of arch detection from d-i in isolinux, fix booting from
 help files and isolinux.cfg overwriting
 .
   [ Cyril Brulebois ]
   * Make amd64 the default arch in the easy-build.sh script.
   * Make stretch the default suite in the easy-build.sh script.
 .
   [ Philipp Kern ]
   * Load the s390x initrd at 0x0100 to allow kernels larger than
 8 MiB (and smaller than 16 MiB) to be loaded via the ins loader.
   * Drop the remaining s390 bits from stretch and jessie. (s390x remains.)
   * Drop the d390oco loader from stretch and jessie.
 .
   [ John Paul Adrian Glaubitz 

Bug#821484: Bumping severity of PHP 7.0 transition bugs to serious

2016-05-06 Thread James Valleroy
tags 821484 patch
thanks

The attached patch will simply switch from PHP 5 to PHP 7.0.

--
James
From c31380d50e3f6fe55788d5302d324184273a6b6d Mon Sep 17 00:00:00 2001
From: James Valleroy 
Date: Fri, 6 May 2016 07:46:42 -0400
Subject: [PATCH] Switch to PHP 7.0.

---
 debian/control | 2 +-
 setup.d/90_apache2 | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/debian/control b/debian/control
index 8fd813c..bc1b86d 100644
--- a/debian/control
+++ b/debian/control
@@ -47,7 +47,7 @@ Depends: ${misc:Depends}
  , iputils-ping
  , iw
  , libapache2-mod-gnutls
- , libapache2-mod-php5
+ , libapache2-mod-php
  , libnss-gw-name
  , libnss-mdns
  , libnss-myhostname
diff --git a/setup.d/90_apache2 b/setup.d/90_apache2
index dd132f2..30a79de 100755
--- a/setup.d/90_apache2
+++ b/setup.d/90_apache2
@@ -25,7 +25,7 @@ a2enmod headers
 
 # enable some critical modules to avoid restart while installing
 # Plinth applications.
-a2enmod php5
+a2enmod php7.0
 a2enmod cgi
 a2enmod authnz_ldap
 
-- 
2.8.1



signature.asc
Description: OpenPGP digital signature


Bug#812462: marked as done (ganglia: [FTBFS, patch] out-of-date and missing build-depends)

2016-05-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 May 2016 19:48:47 +
with message-id 
and subject line Bug#812462: fixed in ganglia 3.6.0-6.1
has caused the Debian Bug report #812462,
regarding ganglia: [FTBFS, patch] out-of-date and missing build-depends
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.)


-- 
812462: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812462
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ganglia
Version: 3.6.0-6
Usertags: goto-cc
Tags: patch
Severity: serious
Justification: FTBFS

As of its version 1.5.4-3, rrdtool no longer Provides: librrd2-dev from
librrd-dev. This breaks the build of ganglia. Changing the build-dependency to
librrd-dev fixes this first problem.

The build then fails with

./configure: line 12863: PKG_PROG_PKG_CONFIG: command not found

Checking for apr
./configure: line 12978: syntax error near unexpected token `APR,apr-1'
./configure: line 12978: `  PKG_CHECK_MODULES(APR,apr-1)'

and

Checking for zlib
checking zlib.h usability... no
checking zlib.h presence... no
checking for zlib.h... no
checking for deflate in -lz... no
zlib library not configured properly

The attached patch addresses all these problems, and the build succeeds
eventually.

Best,
Michael

diff -urN a/debian/control b/debian/control
--- a/debian/control2014-09-11 10:59:34.0 +0100
+++ b/debian/control2016-01-23 13:51:49.0 +
@@ -4,7 +4,7 @@
 Maintainer: Debian Monitoring Maintainers 

 Uploaders: Stuart Teasdale , Daniel Pocock 
 Homepage: http://ganglia.info/
-Build-Depends: debhelper (>> 9.0.0), librrd2-dev, autoconf, autotools-dev, 
automake, libapr1-dev, libexpat1-dev, python-dev, libconfuse-dev, po-debconf, 
libxml2-dev, libdbi0-dev, libpcre3-dev, gperf, libtool, rsync, libkvm-dev 
[kfreebsd-any]
+Build-Depends: debhelper (>> 9.0.0), librrd-dev, autoconf, autotools-dev, 
automake, libapr1-dev, libexpat1-dev, python-dev, libconfuse-dev, po-debconf, 
libxml2-dev, libdbi0-dev, libpcre3-dev, gperf, libtool, rsync, libkvm-dev 
[kfreebsd-any], pkg-config, libz-dev
 Standards-Version: 3.9.4
 Vcs-Git: git://anonscm.debian.org/pkg-monitoring/ganglia.git
 Vcs-Browser: http://anonscm.debian.org/cgit/pkg-monitoring/ganglia.git


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ganglia
Source-Version: 3.6.0-6.1

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

Debian distribution maintenance software
pp.
Jean-Michel Vourgère  (supplier of updated ganglia 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, 06 May 2016 18:22:47 +
Source: ganglia
Binary: ganglia-monitor ganglia-monitor-python gmetad libganglia1 
libganglia1-dev
Architecture: source amd64 all
Version: 3.6.0-6.1
Distribution: unstable
Urgency: high
Maintainer: Debian Monitoring Maintainers 

Changed-By: Jean-Michel Vourgère 
Description:
 ganglia-monitor - cluster monitoring toolkit - node daemon
 ganglia-monitor-python - cluster monitoring toolkit - python modules
 gmetad - cluster monitoring toolkit - Ganglia Meta-Daemon
 libganglia1 - cluster monitoring toolkit - shared libraries
 libganglia1-dev - cluster monitoring toolkit - development libraries
Closes: 812462
Changes:
 ganglia (3.6.0-6.1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Updated build-dependencies. Thanks Michael Tautschnig. (Closes: #812462)
Checksums-Sha1:
 494fe34370779a430a64c14643b909f36d677b7c 2427 ganglia_3.6.0-6.1.dsc
 42e7fddc281e8ccb971f5612acacb218ca3450cc 11564 ganglia_3.6.0-6.1.debian.tar.xz
 baf927e4050854f154a479c949b41378752f7418 115846 
ganglia-monitor-dbgsym_3.6.0-6.1_amd64.deb
 20258be24e2e2a2a863811becacbef5018a746bc 44534 
ganglia-monitor-python_3.6.0-6.1_all.deb
 e4341ac30e0c4d8f2dc6311043974890caf71a7c 70876 
ganglia-monitor_3.6.0-6.1_amd64.deb
 b2506ba7d30082dda3ba21898686f6a05d8ae4ff 71786 
gmetad-dbgsym_3.6.0-6.1_amd64.deb
 042dd72ae2490d46cc93e60d929d0c7e6c716ffe 34668 gmetad_3.6.0-6.1_amd64.deb
 474c5b8e10b8256954d71b7e752ce4922e4e73d4 247610 
libganglia1-dbgs

Bug#822194: libdebug: diff for NMU version 0.5.1-1.1

2016-05-06 Thread Jakub Wilk

Control: tags 822194 + patch
Control: tags 822194 + pending

Dear maintainer,

I've prepared an NMU for libdebug (versioned as 0.5.1-1.1) and uploaded 
it to DELAYED/2. Please feel free to tell me if I should delay it 
longer.


--
Jakub Wilk
diffstat for libdebug-0.5.1 libdebug-0.5.1

 changelog |7 +++
 rules |2 +-
 2 files changed, 8 insertions(+), 1 deletion(-)


No differences were encountered between the control files

diff -Nru libdebug-0.5.1/debian/changelog libdebug-0.5.1/debian/changelog
--- libdebug-0.5.1/debian/changelog	2016-04-21 22:35:40.0 +0200
+++ libdebug-0.5.1/debian/changelog	2016-05-06 21:04:09.0 +0200
@@ -1,3 +1,10 @@
+libdebug (0.5.1-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Disable parallel builds (closes: #822194).
+
+ -- Jakub Wilk   Fri, 06 May 2016 21:04:02 +0200
+
 libdebug (0.5.1-1) unstable; urgency=medium
 
   * Acknowledge Jakub Wilk's NMU; thanks!
diff -Nru libdebug-0.5.1/debian/rules libdebug-0.5.1/debian/rules
--- libdebug-0.5.1/debian/rules	2016-04-21 22:35:40.0 +0200
+++ libdebug-0.5.1/debian/rules	2016-05-06 21:03:59.0 +0200
@@ -31,4 +31,4 @@
 		libdir=/usr/lib/$(DEB_HOST_MULTIARCH) install
 
 %:
-	dh $@
+	dh $@ --no-parallel


Processed: libdebug: diff for NMU version 0.5.1-1.1

2016-05-06 Thread Debian Bug Tracking System
Processing control commands:

> tags 822194 + patch
Bug #822194 [src:libdebug] libdebug: FTBFS: No rule to make target 
'libdebug.so.0', needed by 'with-depends'
Added tag(s) patch.
> tags 822194 + pending
Bug #822194 [src:libdebug] libdebug: FTBFS: No rule to make target 
'libdebug.so.0', needed by 'with-depends'
Added tag(s) pending.

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



Bug#812462: [Pkg-monitoring-maintainers] Bug#812462: ganglia: diff for NMU version 3.6.0-6.1

2016-05-06 Thread Daniel Pocock


On 06/05/16 20:53, Jean-Michel Nirgal Vourgère wrote:
> Control: tags 812462 + pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for ganglia (versioned as 3.6.0-6.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
> 


No need to delay it, you are welcome to upload it immediately as long as
you also commit your changes in the Git VCS

Regards,

Daniel



Bug#823043: zsh FTBFS since yodl 3.08.00-1 in the same way that c++-annotations FTBFSed with 3.07.00-1 (was: Re: Bug#823043 closed by f.b.brok...@rug.nl (Frank B. Brokken) (Bug#823043: fixed in yodl 3

2016-05-06 Thread Axel Beckert
Control: reopen -1
Control: affects -1 src:zsh
Control: found -1 3.08.00-1

Hi Frank,

Debian Bug Tracking System wrote:
>  yodl (3.08.00-1) unstable; urgency=medium
>  .
>* New upstream release fixes a bug in handling multiple identical options.
>  (Closes: #823043).

Frank B. Brokken wrote:
> Thanks for your bug report. It looks like you encountered a real bug, and I'm
> still somewhat in the dark as to why it never has been observed
> before. Because of that (i.e., me satisfying my own curiosity) I'll need a bit
> more time to submit a fix, but at least I think I've located the cause of the
> problem. I'll probably have a fix ready by Monday or a bit earlier.
> 
> One minor thing: it's not an Annotations issue, but a bug in the Yodl
> package.

I'm not 100% sure what's going on, but it seems to me that while
c++-annotations indeed FTBFS with 3.07.00-1 and builds fine again with
3.08.00-1 (verified it :-), it's the opposite way round with zsh:

It builds fine with yodl 3.07.00-1, but FTBFS with 3.08.00-1 as
follows:

Zsh Yodl-to-man converter
Including file Zsh/zftpsys.yo
yodl -k -L -o ../../Doc/zshzle.1 -I../../Doc:. -w zman.yo version.yo
../../Doc/zshzle.yo
Zsh Yodl-to-man converter
Including file Zsh/zle.yo
yodl -k -L -o ../../Doc/zshall.1 -I../../Doc -DZSHALL -w zman.yo version.yo 
zsh.yo
`ZSHALL' (symbol) multiply defined
`ZSHALL' (symbol) multiply defined
`ZSHALL' (symbol) multiply defined
Error(s) in command line arguments. Terminating

Feel free to clone and close the original bug report if you think that
my issue is a different issue. (But it looks very similar to me.)

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Processed: zsh FTBFS since yodl 3.08.00-1 in the same way that c++-annotations FTBFSed with 3.07.00-1 (was: Re: Bug#823043 closed by f.b.brok...@rug.nl (Frank B. Brokken) (Bug#823043: fixed in yodl 3.

2016-05-06 Thread Debian Bug Tracking System
Processing control commands:

> reopen -1
Bug #823043 {Done: f.b.brok...@rug.nl (Frank B. Brokken)} [yodl] 
c++-annotations: FTBFS: `APATH' (symbol) multiply defined
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions yodl/3.08.00-1.
> affects -1 src:zsh
Bug #823043 [yodl] c++-annotations: FTBFS: `APATH' (symbol) multiply defined
Added indication that 823043 affects src:zsh
> found -1 3.08.00-1
Bug #823043 [yodl] c++-annotations: FTBFS: `APATH' (symbol) multiply defined
Marked as found in versions yodl/3.08.00-1.

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



Bug#812462: ganglia: diff for NMU version 3.6.0-6.1

2016-05-06 Thread Jean-Michel Nirgal Vourgère
Control: tags 812462 + pending

Dear maintainer,

I've prepared an NMU for ganglia (versioned as 3.6.0-6.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -Nru ganglia-3.6.0/debian/changelog ganglia-3.6.0/debian/changelog
--- ganglia-3.6.0/debian/changelog	2014-10-12 13:26:20.0 +0200
+++ ganglia-3.6.0/debian/changelog	2016-05-06 20:27:18.0 +0200
@@ -1,3 +1,10 @@
+ganglia (3.6.0-6.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Updated build-dependencies. Thanks Michael Tautschnig. (Closes: #812462)
+
+ -- Jean-Michel Vourgère   Fri, 06 May 2016 18:22:47 +
+
 ganglia (3.6.0-6) unstable; urgency=medium
 
   * Fix for missing service file. (Closes: #764836)
diff -Nru ganglia-3.6.0/debian/control ganglia-3.6.0/debian/control
--- ganglia-3.6.0/debian/control	2014-09-11 11:59:34.0 +0200
+++ ganglia-3.6.0/debian/control	2016-05-06 20:20:12.0 +0200
@@ -4,7 +4,7 @@
 Maintainer: Debian Monitoring Maintainers 
 Uploaders: Stuart Teasdale , Daniel Pocock 
 Homepage: http://ganglia.info/
-Build-Depends: debhelper (>> 9.0.0), librrd2-dev, autoconf, autotools-dev, automake, libapr1-dev, libexpat1-dev, python-dev, libconfuse-dev, po-debconf, libxml2-dev, libdbi0-dev, libpcre3-dev, gperf, libtool, rsync, libkvm-dev [kfreebsd-any]
+Build-Depends: debhelper (>> 9.0.0), librrd-dev, autoconf, autotools-dev, automake, libapr1-dev, libexpat1-dev, python-dev, libconfuse-dev, po-debconf, libxml2-dev, libdbi0-dev, libpcre3-dev, gperf, libtool, rsync, libkvm-dev [kfreebsd-any], pkg-config, libz-dev
 Standards-Version: 3.9.4
 Vcs-Git: git://anonscm.debian.org/pkg-monitoring/ganglia.git
 Vcs-Browser: http://anonscm.debian.org/cgit/pkg-monitoring/ganglia.git


Processed: ganglia: diff for NMU version 3.6.0-6.1

2016-05-06 Thread Debian Bug Tracking System
Processing control commands:

> tags 812462 + pending
Bug #812462 [ganglia] ganglia: [FTBFS, patch] out-of-date and missing 
build-depends
Added tag(s) pending.

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



Processed: fixed 797291 in debian-parl/1.9.0

2016-05-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> fixed 797291 debian-parl/1.9.0
Bug #797291 {Done: Jonas Smedegaard } [src:debian-parl] 
debian-parl: FTBFS: Class 'Blend.parl.desktop.EU' (in ancestry of node 
'./desktop-eu') not found under yaml_fs:///usr/share/boxer/jessie/classes
Marked as fixed in versions debian-parl/1.9.0.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
797291: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797291
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: fixed 812662 in 1.9.0

2016-05-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> fixed 812662 1.9.0
Bug #812662 {Done: Jonas Smedegaard } [debian-parl] debian-parl: 
FTBFS - Class 'Blend.parl.desktop.EU' (in ancestry of node './desktop-eu') not 
found
There is no source info for the package 'debian-parl' at version '1.9.0' with 
architecture ''
Unable to make a source version for version '1.9.0'
Marked as fixed in versions 1.9.0.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
812662: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812662
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#823622: CVE-2015-4901 CVE-2015-4906 CVE-2015-4908 CVE-2015-4916

2016-05-06 Thread Moritz Muehlenhoff
Source: openjfx
Severity: grave
Tags: security

The four security issues from October's Java CPU are still unfixed, right?
http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html 

Cheers,
Moritz



Bug#812662: marked as done (debian-parl: FTBFS - Class 'Blend.parl.desktop.EU' (in ancestry of node './desktop-eu') not found)

2016-05-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 May 2016 20:05:03 +0200
with message-id <146255790387.13240.5440281913306583...@auryn.jones.dk>
and subject line Re: [Parl-devel] Bug#812662: debian-parl: FTBFS - Class 
'Blend.parl.desktop.EU' (in ancestry of node './desktop-eu') not found
has caused the Debian Bug report #812662,
regarding debian-parl: FTBFS - Class 'Blend.parl.desktop.EU' (in ancestry of 
node './desktop-eu') not found
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.)


-- 
812662: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812662
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-parl
Version: 1.0.9
Severity: serious
Usertags: goto-cc

During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.

[...]
make[1]: Entering directory 
'/srv/jenkins-slave/workspace/sid-goto-cc-debian-parl/debian-parl-1.0.9'
mkdir -p content/desktop/eu/
cd content/desktop/eu/ \
&& boxer compose \
--nodedir 
/srv/jenkins-slave/workspace/sid-goto-cc-debian-parl/debian-parl-1.0.9/nodes \
--skeldir 
/srv/jenkins-slave/workspace/sid-goto-cc-debian-parl/debian-parl-1.0.9/skel \
--suite jessie \
desktop-eu
Class 'Blend.parl.desktop.EU' (in ancestry of node './desktop-eu') not found 
under yaml_fs:///usr/share/boxer/jessie/classes
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/reclass/storage/yaml_fs/__init__.py", 
line 93, in get_class
path = os.path.join(self.classes_uri, self._classes[name])
KeyError: 'Blend.parl.desktop.EU'

"reclass" unexpectedly returned exit value 74 at (eval 227) line 12.
 at /usr/share/perl5/Boxer/Task/Classify.pm line 70
Makefile:17: recipe for target 'content/desktop/eu/preseed.cfg' failed
make[1]: *** [content/desktop/eu/preseed.cfg] Error 74
make[1]: Leaving directory 
'/srv/jenkins-slave/workspace/sid-goto-cc-debian-parl/debian-parl-1.0.9'
debian/blends.mk:67: recipe for target 'content/desktop/preseed.cfg' failed
make: *** [content/desktop/preseed.cfg] Error 2


The full build log is attached; please do let me know if the problem is
unreproducible, in which case I shall try to investigate further.

Best,
Michael


debian-parl-build-log.txt.gz
Description: application/gunzip


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Quoting Michael Tautschnig (2016-01-25 20:02:13)
> During a rebuild of all Debian packages in a clean sid chroot (using 
> cowbuilder and pbuilder) the build failed with the following error.
[...]
> Traceback (most recent call last):
>   File 
> "/usr/lib/python2.7/dist-packages/reclass/storage/yaml_fs/__init__.py", line 
> 93, in get_class
> path = os.path.join(self.classes_uri, self._classes[name])
> KeyError: 'Blend.parl.desktop.EU'

This was fixed in release 1.9.0 (by tightening to build-depend on boxer 
4 or newer and boxer-data 7 or newer).

Thanks for reporting.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


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


Bug#797291: marked as done (debian-parl: FTBFS: Class 'Blend.parl.desktop.EU' (in ancestry of node './desktop-eu') not found under yaml_fs:///usr/share/boxer/jessie/classes)

2016-05-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 May 2016 20:07:01 +0200
with message-id <146255802179.13240.235455231201217...@auryn.jones.dk>
and subject line Re: [Parl-devel] Bug#797291: debian-parl: FTBFS: Class 
'Blend.parl.desktop.EU' (in ancestry of node './desktop-eu') not found under 
yaml_fs:///usr/share/boxer/jessie/classes
has caused the Debian Bug report #797291,
regarding debian-parl: FTBFS: Class 'Blend.parl.desktop.EU' (in ancestry of 
node './desktop-eu') not found under yaml_fs:///usr/share/boxer/jessie/classes
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.)


-- 
797291: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797291
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: debian-parl
Version: 1.0.9
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

debian-parl fails to build from source in unstable/amd64:

  [..]

  /usr/bin/make
  make[1]: Entering directory '/tmp/buildd/debian-parl-1.0.9'
  mkdir -p content/desktop/eu/
  cd content/desktop/eu/ \
&& boxer compose \
--nodedir /tmp/buildd/debian-parl-1.0.9/nodes \
--skeldir /tmp/buildd/debian-parl-1.0.9/skel \
--suite jessie \
desktop-eu
  Class 'Blend.parl.desktop.EU' (in ancestry of node './desktop-eu') not
  found under yaml_fs:///usr/share/boxer/jessie/classes
  Traceback (most recent call last):
File
"/usr/lib/python2.7/dist-packages/reclass/storage/yaml_fs/__init__.py",
line 93, in get_class
  path = os.path.join(self.classes_uri, self._classes[name])
  KeyError: 'Blend.parl.desktop.EU'
  
  "reclass" unexpectedly returned exit value 74 at (eval 185) line 12.
   at /usr/share/perl5/Boxer/Task/Classify.pm line 69
  Makefile:17: recipe for target 'content/desktop/eu/preseed.cfg' failed
  make[1]: *** [content/desktop/eu/preseed.cfg] Error 74
  make[1]: Leaving directory '/tmp/buildd/debian-parl-1.0.9'
  debian/blends.mk:67: recipe for target 'content/desktop/preseed.cfg'
  failed
  make: *** [content/desktop/preseed.cfg] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/debian-parl_1.0.9.build1.log.gz


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Fri Aug 28 09:45:38 GMT+12 2015
I: pbuilder-time-stamp: 1440798338
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /dev/shm
I: Mounting /sys
I: policy-rc.d already exists
I: Installing the build-deps
 -> Attempting to satisfy build-dependencies
 -> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team 
Description: Dummy package to satisfy dependencies with aptitude - created by 
pbuilder
 This package was created automatically by pbuilder to satisfy the
 build-dependencies of the package being currently built.
Depends: cdbs, debhelper, dh-buildinfo, boxer, boxer-data, shellcheck
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20223 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...
Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring 
anyway as you requested:
 pbuilder-satisfydepends-dummy depends on cdbs; however:
  Package cdbs is not installed.
 pbuilder-satisfydepends-dummy depends on dh-buildinfo; however:
  Package dh-buildinfo is not installed.
 pbuilder-satisfydepends-dummy depends on boxer; however:
  Package boxer is not installed.
 pbuilder-satisfydepends-dummy depends on boxer-data; however:
  Package boxer-data is not installed.
 pbuilder-satisfydepends-dummy depends on shellcheck; however:
  Package shellcheck is not installed.

Setting up pbuilder-satisfydepends-dummy (0.invalid.0) .

Bug#823620: Multiple security issues

2016-05-06 Thread Moritz Muehlenhoff
Source: xen
Severity: grave
Tags: security

Multiple vulnerabilities are unfixed in xen:

CVE-2015-5307:
http://xenbits.xen.org/xsa/advisory-156.html

CVE-2016-3960
http://xenbits.xen.org/xsa/advisory-173.html

CVE-2016-3159 / CVE-2016-3158
http://xenbits.xen.org/xsa/advisory-172.html

CVE-2016-2271
http://xenbits.xen.org/xsa/advisory-170.html

CVE-2016-2270
http://xenbits.xen.org/xsa/advisory-154.html

CVE-2016-1571
http://xenbits.xen.org/xsa/advisory-168.html

CVE-2016-1570
http://xenbits.xen.org/xsa/advisory-167.html

CVE-2015-8615
http://xenbits.xen.org/xsa/advisory-169.html

CVE-2015-8555
http://xenbits.xen.org/xsa/advisory-165.html

CVE-2015-8550
http://xenbits.xen.org/xsa/advisory-155.html

CVE-2015-8341
http://xenbits.xen.org/xsa/advisory-160.html

CVE-2015-8340 / CVE-2015-8339
http://xenbits.xen.org/xsa/advisory-159.html

CVE-2015-8338
http://xenbits.xen.org/xsa/advisory-158.html

CVE-2015-8104
http://xenbits.xen.org/xsa/advisory-156.html
 
CVE-2015-7311
http://xenbits.xen.org/xsa/advisory-142.html

CVE-2015-6654
http://xenbits.xen.org/xsa/advisory-141.html



   



Processed: severity of 797547 is grave

2016-05-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 797547 grave
Bug #797547 [pgsnap] pgsnap seems too old in Jessie
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
797547: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797547
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#823611: marked as done (init-system-helpers: invoke-rc.d fails in chroots: invoke-rc.d: could not determine current runlevel)

2016-05-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 May 2016 16:22:24 +
with message-id 
and subject line Bug#823611: fixed in init-system-helpers 1.33
has caused the Debian Bug report #823611,
regarding init-system-helpers: invoke-rc.d fails in chroots: invoke-rc.d: could 
not determine current runlevel
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.)


-- 
823611: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823611
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: init-system-helpers
Version: 1.32
Severity: grave

Since this night's upload, uses of invoke-rc.d inside a chroot fail with:
invoke-rc.d: could not determine current runlevel

This makes a crapload of packages uninstallable -- many pretty deep in
dependency chains.

We have two /sbin/runlevel implementations in Debian: sysvinit-core and
systemd-sysv, both fail the same way.

This bug is especially nasty as it makes almost all package builds in
sbuild/pbuilder FTBFS.


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

Kernel: Linux 4.6.0-rc6-debug+ (SMP w/6 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages init-system-helpers depends on:
ii  perl-base  5.22.2-1

init-system-helpers recommends no packages.

init-system-helpers suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: init-system-helpers
Source-Version: 1.33

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

Debian distribution maintenance software
pp.
Martin Pitt  (supplier of updated init-system-helpers 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, 06 May 2016 09:44:05 -0500
Source: init-system-helpers
Binary: init-system-helpers dh-systemd init
Architecture: source all amd64
Version: 1.33
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Martin Pitt 
Description:
 dh-systemd - debhelper add-on to handle systemd unit files
 init   - init metapackage
 init-system-helpers - helper tools for all init systems
Closes: 823611
Changes:
 init-system-helpers (1.33) unstable; urgency=medium
 .
   * Drop SysV reference from init's short package description, as it's not
 specific to SysV init at all.
   * Revert the check for failing "runlevel" command. In chroots it is always
 failing, so just print out the warning and otherwise ignore the failure as
 we've done for many years with the broken check. (Closes: #823611)
Checksums-Sha1:
 ea620f466f78572138e9772088973012e336922d 1866 init-system-helpers_1.33.dsc
 c5f7589cfc04dd22d558f0e1fe364c3293dde84c 57224 init-system-helpers_1.33.tar.xz
 985c6014eaaefd84c077957b2580ad843070c125 21500 dh-systemd_1.33_all.deb
 43358ef3ef755aae85ab54288a21e1c82577cd73 35262 init-system-helpers_1.33_all.deb
 83a6b79a910ebf4ea50543bfe305757894786e26 7786 init_1.33_amd64.deb
Checksums-Sha256:
 a8677029877818b263eac4500a24a16e8142a77de88204955c028d420d682b79 1866 
init-system-helpers_1.33.dsc
 9f0cf0a3aaea1c87b3f8da62082a1a8838b04b956c6fec768a4ba3695d1ad9c0 57224 
init-system-helpers_1.33.tar.xz
 a5a1c0c59dec50ed8c451c27725bb9c05b47774ab9b35ad151d77cd2e84f27a0 21500 
dh-systemd_1.33_all.deb
 764a1f1deeb8673fb7aa6261b27eb91fa3665acd403b4904c01e192964b31d24 35262 
init-system-helpers_1.33_all.deb
 d38d1207325d4b6c1f971e76df751b71f5d38ce78fed68e115c106e85dcb4934 7786 
init_1.33_amd64.deb
Files:
 b23b3d10e153cecc979d557a8f50806e 1866 admin extra init-system-helpers_1.33.dsc
 5bae114c532a0694fe9ef31fa92567c3 57224 admin extra 
init-system-helpers_1.33.tar.xz
 6e157e3b5c2c4cd1c3b62d52eba45bdf 21500 admin extra dh-systemd_1.33_all.deb
 26f335b00b2497e35f9bb8260feecf79 35262 admin required 
init-system-helpers_1.33_all.deb
 bd11b697bcfd880d4028a7a83b414d0d 7786 metapackages required init_1.33_amd64.deb

-BEGIN PGP SIGNATURE-
Ve

Bug#821511: marked as done (letodms: PHP 7.0 Transition)

2016-05-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 May 2016 16:25:17 +
with message-id 
and subject line Bug#821511: fixed in letodms 3.4.2+dfsg-2
has caused the Debian Bug report #821511,
regarding letodms: 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.)


-- 
821511: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821511
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: letodms
Version: 3.3.11+dfsg.1-2
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 letodms package currently depends on php5 php5-gd php5-mysql .

PHP 7.0 has landed in unstable with substantial changes to the packaging:

  1. Every package built from src:phpMAJOR.MINOR now include
 phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm.

  2. Accompanying src:php-defaults builds 1:1 mapping to a default
 MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm.  When you
 specify a dependency, please use the generic name, unless you
 absolutely know that won't work for you.

  3. Every path in the system has been changed to a versioned, e.g.
 /etc/php5/cli is now /etc/php/7.0/cli

  4. dh_php5 is now dh_php

  5. php-pear is not built from independent source package.

  6. master-7.0 branches of several extensions (php-apcu, xdebug,
 php-apcu-bc) can be used as a template how to change the PHP
 extension packaging.  It's mostly cut&paste since the d/rules tries
 to figure-out most of the variables from debian/ directory.

  7. pkg-php-tools package now supports PHP 7.0 packaging and if your
 package uses pkg-php-tools a simple binNMU is all it might need

  8. PHP 7.0 has changed extension API, so most-if-not-all extensions
 need work from upstream to be compatible with PHP 7.0.

  9. We expect to ship next Debian release (stretch) only with PHP
 7.0, that means that all packages needs to be made compatible with
 PHP 7.0.  Fortunately the PHP 7.0 is mostly compatible with properly
 maintained software.  However some extensions has been deprecated
 (f.e. mysql) and thus old unmaintained software will stop working
 and it will have to be either patched or removed from stable Debian.

So what you need to do:

Replace every occurence of php5 with just php, e.g. if you depend on
'php5' then you just need to depend on 'php'.  Also if you package a web
application and depend on specific SAPI, I would recommend depending just
on 'php' package and let the user decide whether he will install php-fpm,
libapache2-mod-php or php-cgi.

The script that was used to get the list of packages for MBF was not a
particular smart one (so it doesn't detect alternatives, etc.), so if
there's a false positive, please excuse me and just close the bug with
short explanation.

The other options that might be used with packages that don't and won't
support PHP 7.0 is to remove the software from Debian by changing the
title of this bugreport to:

RM: letodms -- ROM; doesn't support PHP 7.0

reassigning it to ftp.debian.org pseudo-package and changing severity to
'normal'.

Also feel free to contact the maintainers at one of the lists:

pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages
pkg-php-p...@lists.alioth.debian.org -- for PHP extensions
pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all

Cheers, Ondrej

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

Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJXFUpzXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHMzEP/jzde7r4Xi3k/w2MQ+lp0jzp
tvsB9vsS4S2kBTt8yQSP+RiCrDtYo57dkrjSbbZUAPa2SBm7QV8A3QxQOI+cJTC0
+/oLXfIvJ7fMA9GUB2CXYRCCSRpRmObcKS4f480+SaWwTDuPtgYOjeU+B6jkJ0RT
5qkrqGGccPrFX99E0IAP7XESyfpNBtBw49yvRmUAZfZkK1t6rhnDIaZWV0K9QhOR
mYF5fBcO2s/dqeGxbrLZkShk4PwSwtFlRz1fhLS0n8nebFe6lfBZWc9/uHrzi5KZ
ehG3yAvj8FEyVFYR01gawx/+/EXn0e/QiYxP68IOY

Processed: retitle 823603 to linux: CVE-2016-4557: [Local root exploit] Use after free via double-fdput in bpf

2016-05-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> retitle 823603 linux: CVE-2016-4557: [Local root exploit] Use after free via 
> double-fdput in bpf
Bug #823603 [src:linux] linux: [Local root exploit] Use after free via 
double-fdput in bpf
Changed Bug title to 'linux: CVE-2016-4557: [Local root exploit] Use after free 
via double-fdput in bpf' from 'linux: [Local root exploit] Use after free via 
double-fdput in bpf'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
823603: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823603
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#822529: gdm3: retries to often / to fast on errors

2016-05-06 Thread Laurent Bigonville

On Mon, 25 Apr 2016 08:12:06 +0200 Tobias Frost  wrote:
>
> Dear gdm3 maintainers,
>

Hello Tobias,

> To debug another issue, I needed to boot an older kernel which has 
not nv compiled,

> so X could not load that module and could not start.
>
> That it not able to start is expected behaviour, but after that 
happens gdm basically DoS the machine:

> After the failures happens it immediatly retries and that indefintily.
>
> This gives a "blinking" effect switching the vts back and forth, 
making it
> impossible to enter anything into a vt to login and actually fix the 
problem.

>
> To get the machine useable again, I sshed into that machine to stop 
gdm manually.

>
> Attached is an excerpt (~10 seconds) of /var/log/syslog.
>
> As a metrics, in the time I needd to stop the service, was 1minute 
23seconds, it retried 242 times.

>
> Please let me know if you need additonal information, let me know.
>
> I guess the systemd file needs some tewaking to limit retries.
>
> Thanks!
>

Do you think it's a regression from 3.18? TBH, I think I already saw 
this behavior in the past.


Also, do you think you could bring this upstream?

Cheers,

Laurent Bigonville



Processed: tagging 823603

2016-05-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 823603 - newcomer
Bug #823603 [src:linux] linux: [Local root exploit] Use after free via 
double-fdput in bpf
Ignoring request to alter tags of bug #823603 to the same tags previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
823603: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823603
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#823611: init-system-helpers: invoke-rc.d fails in chroots: invoke-rc.d: could not determine current runlevel

2016-05-06 Thread Adam Borowski
Package: init-system-helpers
Version: 1.32
Severity: grave

Since this night's upload, uses of invoke-rc.d inside a chroot fail with:
invoke-rc.d: could not determine current runlevel

This makes a crapload of packages uninstallable -- many pretty deep in
dependency chains.

We have two /sbin/runlevel implementations in Debian: sysvinit-core and
systemd-sysv, both fail the same way.

This bug is especially nasty as it makes almost all package builds in
sbuild/pbuilder FTBFS.


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

Kernel: Linux 4.6.0-rc6-debug+ (SMP w/6 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages init-system-helpers depends on:
ii  perl-base  5.22.2-1

init-system-helpers recommends no packages.

init-system-helpers suggests no packages.

-- no debconf information



Bug#823595: marked as done (linux-grsec: Takes over generic binary packages from linux source)

2016-05-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 May 2016 13:50:40 +
with message-id 
and subject line Bug#823595: fixed in linux-grsec 4.5.2-2+grsec201604290633+2
has caused the Debian Bug report #823595,
regarding linux-grsec: Takes over generic binary packages from linux source
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.)


-- 
823595: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823595
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux-grsec
Source-Version: 4.5.2-2+grsec201604290633+1
Severity: serious

Hi!

With latest upload this source package takes over several of the
generic binary packages from the linux source, which Yves-Alexis
confirmed on IRC was unintentional.

For example linux-kbuild-4.5, linux-perf-4.5, hyperv-daemons,
libcpupower-dev, etc.

Thanks,
Guillem
--- End Message ---
--- Begin Message ---
Source: linux-grsec
Source-Version: 4.5.2-2+grsec201604290633+2

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

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated linux-grsec 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, 06 May 2016 15:27:51 +0200
Source: linux-grsec
Binary: linux-grsec-source-4.5 linux-grsec-support-4.5.0-2 
linux-headers-4.5.0-2-common-grsec linux-image-4.5.0-2-grsec-amd64 
linux-headers-4.5.0-2-grsec-amd64 linux-image-4.5.0-2-grsec-686-pae 
linux-headers-4.5.0-2-grsec-686-pae
Architecture: source
Version: 4.5.2-2+grsec201604290633+2
Distribution: unstable
Urgency: medium
Maintainer: Yves-Alexis Perez 
Changed-By: Yves-Alexis Perez 
Description:
 linux-grsec-source-4.5 - Linux kernel source for version 4.5 with Debian 
patches
 linux-grsec-support-4.5.0-2 - Support files for Linux 4.5
 linux-headers-4.5.0-2-common-grsec - Common header files for Linux 
4.5.0-2-grsec
 linux-headers-4.5.0-2-grsec-686-pae - Header files for Linux 
4.5.0-2-grsec-686-pae
 linux-headers-4.5.0-2-grsec-amd64 - Header files for Linux 4.5.0-2-grsec-amd64
 linux-image-4.5.0-2-grsec-686-pae - Linux 4.5 for modern PCs, Grsecurity 
protection
 linux-image-4.5.0-2-grsec-amd64 - Linux 4.5 for 64-bit PCs, Grsecurity 
protection
Closes: 823595
Changes:
 linux-grsec (4.5.2-2+grsec201604290633+2) unstable; urgency=medium
 .
   * debian/config/defines:
 - don't build tools, they're provided by src:linux. closes: #823595
Checksums-Sha1:
 227898f6fdc5964fc2a363706a6147ded69d9222 3348 
linux-grsec_4.5.2-2+grsec201604290633+2.dsc
 8d5ebfb1296dac84bd49d468ea942df6c7e6ea4b 2032512 
linux-grsec_4.5.2-2+grsec201604290633+2.debian.tar.xz
Checksums-Sha256:
 e9c04d553477cf3590b16c281b89c5ed846bb6f3ae116eb9c6ff82723d845a69 3348 
linux-grsec_4.5.2-2+grsec201604290633+2.dsc
 65fc56ae304b1e9ed6fb9f2b5055376db8dab39c41a41fcffb29d93786b5ae28 2032512 
linux-grsec_4.5.2-2+grsec201604290633+2.debian.tar.xz
Files:
 ad4ed978e4a5fbb1499ef3de68c2ae84 3348 kernel optional 
linux-grsec_4.5.2-2+grsec201604290633+2.dsc
 6f82a7318c23adc239692cc8a457a355 2032512 kernel optional 
linux-grsec_4.5.2-2+grsec201604290633+2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCgAGBQJXLJzeAAoJEG3bU/KmdcClFjAH/A3vnA2z6me95m40YfT+Fkos
0/H5MYHN4LJ6DHGu+mKXWrVeh+aGFAP5yUN0uxYqw+GxFMSiryjp5RQFMyasRJV5
179S/oXznIT0Ehw+LqxPflnKvnt/7mDwMi9wtZpIYErO8v5epSxwixgGURd7gCmH
DiD8yPAtCfRJ59XtAb9PEjNj0PSYqIEVkcX83NR9FcJhmUNXc5kzX/7Cauo9az2f
qnyhh6tu5qoXm0PN63I/2YT7JIq0B1zucrap05pIBbuTFMupeSd77xgLr3AD01Oy
WGSes+VpBJ/eMLErjcMlQB1adaUb2d19J2kFlrGtcAu8LkQdu8g7Auch6jWGkr8=
=wKyH
-END PGP SIGNATURE End Message ---


Bug#821708: marked as done (src:php-sabredav: PHP 7.0 Transition)

2016-05-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 May 2016 13:50:56 +
with message-id 
and subject line Bug#821708: fixed in php-sabredav 1.8.12-3
has caused the Debian Bug report #821708,
regarding src:php-sabredav: 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.)


-- 
821708: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821708
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:php-sabredav
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-sabredav package currently build-depends on php5 php5-cli
php5-curl php5-sqlite .

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-sabredav -- 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

iQJ8BAEBCgBmBQJXFUt0XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHNf8P/3ItIT96gAH3e6OgqmuMlByj
Dl5Kvo5SjMG2iMEPLpsC7XtLsjT2kHCIsVeA5c5IBFSOQPWT5Xco7zYovSagc8q0
bnfLFVEiumEQLdNoUMTEnnYJ27KuSPhkwltk6H1I56L1Nc9gRdtIbTWg2HBulsV+
KTTDMdgDHANdCC3qVy7yonUGhsZtt3Bep/hRKBW19cYBhC9otFBk1PJM/O8VRx/q
sJftah6JsbDADxq5TgwCK0Os5tTiT+ZfHUtqUyvuD9bwvzF2IQYFzyn/NgtU3GTF
fCcOBlfZ863z3+HkLoG

Processed: notfixed 821789 in python-django/1.9.5-2, notfixed 821789 in ufraw/0.20-4.1, reopening 821789

2016-05-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> notfixed 821789 python-django/1.9.5-2
Bug #821789 {Done: Tobias Frost } 
[python-django,python3-django] python{, 3}-django: fails to upgrade from 
'jessie': mv: cannot move 
'/usr/lib/python*/dist-packages/django/conf/app_template/migrations' to 
'/usr/share/python-django-common/django/conf/app_template/migrations': 
Directory not empty
No longer marked as fixed in versions python-django/1.9.5-2.
> notfixed 821789 ufraw/0.20-4.1
Bug #821789 {Done: Tobias Frost } 
[python-django,python3-django] python{, 3}-django: fails to upgrade from 
'jessie': mv: cannot move 
'/usr/lib/python*/dist-packages/django/conf/app_template/migrations' to 
'/usr/share/python-django-common/django/conf/app_template/migrations': 
Directory not empty
No longer marked as fixed in versions ufraw/0.20-4.1.
> reopen 821789
Bug #821789 {Done: Tobias Frost } 
[python-django,python3-django] python{, 3}-django: fails to upgrade from 
'jessie': mv: cannot move 
'/usr/lib/python*/dist-packages/django/conf/app_template/migrations' to 
'/usr/share/python-django-common/django/conf/app_template/migrations': 
Directory not empty
Bug reopened
Ignoring request to alter fixed versions of bug #821789 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
821789: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821789
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#823603: linux: [Local root exploit] Use after free via double-fdput in bpf

2016-05-06 Thread Salvatore Bonaccorso
Hi,

On Fri, May 06, 2016 at 01:06:42PM +0100, mik...@tutanota.com wrote:
> Dear Maintainer,
> 
> A local root privilege escalation exploit (no CVE currently available) for 
> Linux >=4.4 was reported in:
> 
> https://bugs.chromium.org/p/project-zero/issues/detail?id=808
> 
> As far as I can tell, the bug does not yet appear in the Debian Security 
> Tracker.
> 
> -
> 
> The upstream fix can be found in that same link, or more directly at:
> 
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=8358b02bf67d3a5d8a825070e1aa73f25fb2e4c7
> 
> Other relevant links:
> 
> https://people.canonical.com/~ubuntu-security/cve/2016/CVE-2016-NNN1.html

This is pending in the packaging repository as

https://anonscm.debian.org/cgit/kernel/linux.git/commit/?h=sid&id=405645d78889b5effdcfbcc0d9ef6ba75a3ac40d

Regards,
Salvatore



Bug#774282: marked as done (parl-desktop-strict: not installable in sid)

2016-05-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 May 2016 13:33:38 +
with message-id 
and subject line Bug#774282: fixed in debian-parl 1.9.0
has caused the Debian Bug report #774282,
regarding parl-desktop-strict: not installable in sid
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.)


-- 
774282: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774282
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: parl-desktop-strict
Version: 1.0.9
User: trei...@debian.org
Usertags: edos-uninstallable
Severity: serious

Hi, parl-desktop-strict is not installble in sid, this is the case since
2014-10-25. The reason is that on the one hand it has a Conflict with
gstreamer0.10-plugins-base, but on the other hand it has an indirect 
dependency on gstreamer0.10-plugins-base via

   ↓ parl-desktop
parl-desktop (1.0.9)
   ↓ task-xfce-desktop
task-xfce-desktop (3.29)
   ↓ xfce4
xfce4 (4.10.1)
   ↓ xfce4-mixer (>= 4.10.0)
xfce4-mixer (4.10.0-3)
   ↓ gstreamer0.10-plugins-base

Cheers -Ralf.
--- End Message ---
--- Begin Message ---
Source: debian-parl
Source-Version: 1.9.0

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated debian-parl 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: SHA1

Format: 1.8
Date: Thu, 05 May 2016 02:36:51 +0200
Source: debian-parl
Binary: parl-data parl-desktop parl-desktop-world parl-desktop-eu 
parl-desktop-strict
Architecture: source all
Version: 1.9.0
Distribution: unstable
Urgency: medium
Maintainer: DebianParl team 
Changed-By: Jonas Smedegaard 
Description:
 parl-data  - recipes to install DebianParl blends
 parl-desktop - DebianParl desktop for parliamentary work
 parl-desktop-eu - DebianParl desktop for parliamentary work - EU
 parl-desktop-strict - DebianParl desktop for parliamentary work - strict
 parl-desktop-world - DebianParl desktop for parliamentary work - global
Closes: 774281 774282
Changes:
 debian-parl (1.9.0) unstable; urgency=medium
 .
   * Bump version number: Minor now reflects targeted Debian release.
   * Update skeleton files to support boxer 4+ format.
 Build-depend on recent boxer.
   * Update node files to match boxer-data 7+ classes.
 Build-depend on recent boxer-data.
   * Update copyright info: Extend coverage to include current year.
   * Use boxer-data 10.5 classes.
 Package parl-desktop:
 + Avoid xfce task: Clashes with GStreamer avoidance.
   Closes: Bug#774282 (see also bug#792283). Thanks to Ralf Treinen.
 + Include more GTK+ office tools, Xfce components, and audio tools.
 + Include popularity-contest.
 + Include apt-listchanges pinentry-gtk2 popularity-contest
   pulseaudio-utils.
 + Include bluez (not bluetooth).
 + Include xfce4-linelight-plugin and mlocate.
 + Include gnome-system-tools (not usermode: Poorly maintained).
   See bug#793465.
 + Stop include evolution-data-server.
 Packages parl-desktop-eu and/or parl-desktop-world:
 + Include or extend hunspell/myspell dictionaries for locales af bn
   da de_AT de_CH de_DE de en_GB en_US et fr gu hi hu it kn ml mr ne
   pa pl ro sl ta te zu.
 + Include LibreOffice support for locales af en-ZA ku nr nso ss tn
   ts ve xh zu.
 + Fix stop include not yet stable Iceowl locales fi gd id lt nb_NO
   pa_IN pt_PT sq uk.
   Closes: Bug#774281. Thanks to Ralf Treinen.
 + Stop include LibreOffice metapackages for localeregions ZA IN
   (instead include individual locales).
 Package parl-desktop-strict:
 + Avoid xfce4-mixer.
 + Avoid fewer LibreOffice components.
 + avoid incompatible hunspell/myspell alternatives.
 + Avoid a bunch of printer drivers.
 + Avoid cpufrequtils: Better handled by default settings of kernel
   drivers nowadays.
 + Stop avoid obsolete packages bluez-gstreamer epdfview
   gstreamer0.10-ffmpeg
   * Ignore quote-escaped newline 'foo\''n'bar' pattern in testsuite.
   * Update TODOs:
 + Drop done items.
 + Maybe a

Bug#822305: RM: openvrml -- RoQA, unmaintained, RC-buggy, FTBFS, blocks removal of old packages

2016-05-06 Thread Tobias Frost
Package: src:openvrml
Followup-For: Bug #822305
Control: unblock 822318 by -1

unblocking the libpng-removal bug, as the last NMUs brought it back into an 
building state, at least.



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

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



Processed: Re: RM: openvrml -- RoQA, unmaintained, RC-buggy, FTBFS, blocks removal of old packages

2016-05-06 Thread Debian Bug Tracking System
Processing control commands:

> unblock 822318 by -1
Bug #822318 [ftp.debian.org] RM: libpng -- RoQA; superseded by libpng1.6
822318 was blocked by: 822687 823379 821773 822305 818072 821798 822243 816101 
822080 821797 821804 822169 821766 822085 821874 821800 817938 822630 821765 
821799 754713 822237 821875 801602 822255 821215 822731 798167
822318 was not blocking any bugs.
Removed blocking bug(s) of 822318: 822305

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



Processed: found 823603 in 4.4~rc4-1~exp1

2016-05-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> found 823603 4.4~rc4-1~exp1
Bug #823603 [src:linux] linux: [Local root exploit] Use after free via 
double-fdput in bpf
Marked as found in versions linux/4.4~rc4-1~exp1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
823603: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823603
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: tagging 823603

2016-05-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 823603 - newcomer
Bug #823603 [src:linux] linux: [Local root exploit] Use after free via 
double-fdput in bpf
Removed tag(s) newcomer.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
823603: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823603
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: tagging 823603

2016-05-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 823603 + pending
Bug #823603 [src:linux] linux: [Local root exploit] Use after free via 
double-fdput in bpf
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
823603: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823603
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: Re: Bug#823604: ruby2.3: FTBFS in testing

2016-05-06 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 + unreproducible
Bug #823604 [ruby2.3] ruby2.3: FTBFS in testing
Added tag(s) unreproducible.
> severity -1 important
Bug #823604 [ruby2.3] ruby2.3: FTBFS in testing
Severity set to 'important' from 'serious'

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



Bug#823604: ruby2.3: FTBFS in testing

2016-05-06 Thread Antonio Terceiro
Control: tag -1 + unreproducible
Control: severity -1 important

On Fri, May 06, 2016 at 02:14:01PM +0200, Santiago Vila wrote:
> Package: ruby2.3
> Version: 2.3.1-1
> Severity: serious
> 
> Dear maintainer:
> 
> I can't build this package in stretch.
> 
> Every time I try this is what happens:
> 
> 
> [...]
>bootstraptest.tmp.rb:4:in `initialize': can't create Thread: Resource 
> temporarily unavailable
> [...]
> 
> 
> Seems as if it wanted an insane amount of memory.
> 
> This is strange because of the following reasons:
> 
> * It didn't happen in version 2.3.0-5
> 
> * My build machine is a QEMU/KVM virtual machine with 6GB of RAM
> and 4GB of swap. I'm using sbuild on a stretch chroot.
> 
> * By looking at /proc/meminfo, the amount of memory ruby2.3 needs to
> build is only about 140 MB on average and 430 MB maximum.
> 
> The full build log is attached. I normally use eatmydata but I've
> disabled it for this build (and the error still reproduces).

can't reproduce this here.

does it fail consistently for you? what system is that VM running?
didn't you find a similar issue with any other package?

-- 
Antonio Terceiro 


signature.asc
Description: PGP signature


Processed: forcibly merging 813468 774882

2016-05-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forcemerge 813468 774882
Bug #813468 [openssl] boinc-client: Some https connections fail due to Debian 
Jessie openssl and ca-certificate interactions
Bug #813468 [openssl] boinc-client: Some https connections fail due to Debian 
Jessie openssl and ca-certificate interactions
Marked as fixed in versions openssl/1.0.2b-1.
Marked as found in versions openssl/1.0.1j-1 and openssl/0.9.8o-4.
Bug #774882 [openssl] openssl: fail to verify some sites when 1024bit root CAs 
removed
812488 was blocked by: 774882
812488 was not blocking any bugs.
Removed blocking bug(s) of 812488: 774882
812708 was blocked by: 774882
812708 was not blocking any bugs.
Removed blocking bug(s) of 812708: 774882
812708 was not blocked by any bugs.
812708 was not blocking any bugs.
Removed blocking bug(s) of 812708: 774882
812488 was not blocked by any bugs.
812488 was not blocking any bugs.
Removed blocking bug(s) of 812488: 774882
774882 was not blocked by any bugs.
774882 was not blocking any bugs.
Added blocking bug(s) of 774882: 765639
Marked as found in versions openssl/1.0.1k-3+deb8u2.
Merged 774882 813468
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
774882: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774882
812488: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812488
812708: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812708
813468: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813468
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#821789: [Python-modules-team] Bug#821789: ufraw: diff for NMU version 0.20-4.1

2016-05-06 Thread Neil Williams
On Fri, 06 May 2016 14:22:09 +0200
Tobias Frost  wrote:

> Control: tags 821789 + patch

Wrong bug report - the nfraw bug is 821798

Please undo the changes to the django bug 821789

> 
> Dear maintainer,
> 
> I've prepared an NMU for ufraw (versioned as 0.20-4.1). The diff
> is attached to this message.
> 
> Regards.
> diff -u ufraw-0.20/debian/changelog ufraw-0.20/debian/changelog
> --- ufraw-0.20/debian/changelog
> +++ ufraw-0.20/debian/changelog
> @@ -1,3 +1,13 @@
> +ufraw (0.20-4.1) unstable; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * Fix FTBFS on kfreebsd-amd64 -- the compiler -ffast-math
> +   and -fomit-frame-pointer are causing this. (Closes: #821789)
> +  * Making build verbose (Closes: #822752). Maybe this gives a hint
> +why it fails to build on alpha.
> +
> + -- Tobias Frost   Fri, 06 May 2016 14:21:18 +0200
> +
>  ufraw (0.20-4) unstable; urgency=high
>  
>* dcraw.cc: Apply fix from
> diff -u ufraw-0.20/debian/rules ufraw-0.20/debian/rules
> --- ufraw-0.20/debian/rules
> +++ ufraw-0.20/debian/rules
> @@ -9,12 +9,17 @@
>  # Uncomment this to turn on verbose mode.
>  #export DH_VERBOSE=1
>  
> +DEB_BUILD_ARCH ?= $(shell dpkg-architecture -qDEB_BUILD_ARCH)
> +
>  CFLAGS = -Wall -g
>  
>  ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))
>   CFLAGS += -O0
>  else
> - CFLAGS += -O3 -ffast-math -fomit-frame-pointer
> + ifeq (,$(findstring kfreebsd-amd64,$(DEB_BUILD_ARCH)))
> + CFLAGS += -ffast-math -fomit-frame-pointer
> + endif
> + CFLAGS += -O3
>  endif
>  
>  clean:
> @@ -66,7 +71,7 @@
>  build-stamp: config
>   dh_testdir
>  
> - $(MAKE)
> + $(MAKE) V=1
>  
>   touch build-stamp
>  
> 
> ___
> Python-modules-team mailing list
> python-modules-t...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


-- 


Neil Williams
=
http://www.linux.codehelp.co.uk/



pgpATF46TEKiZ.pgp
Description: OpenPGP digital signature


Bug#822762: Pending fixes for bugs in the fonts-cantarell package

2016-05-06 Thread pkg-fonts-devel
tag 818964 + pending
tag 822762 + pending
tag 822689 + pending
thanks

Some bugs in the fonts-cantarell package are closed in revision
84f3d39191c3a3705e39ca1b0967a415f2e72b56 in branch 'master' by
Raphaël Hertzog

The full diff can be seen at
http://anonscm.debian.org/gitweb/?p=pkg-fonts/fonts-cantarell.git;a=commitdiff;h=84f3d39

Commit message:

New upstream version.

* New upstream version. Closes: #818964
* Fixes width of some accented characters. Closes: #822762, #822689



Processed: Pending fixes for bugs in the fonts-cantarell package

2016-05-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tag 818964 + pending
Bug #818964 [fonts-cantarell] fonts-cantarell: new upstream release
Added tag(s) pending.
> tag 822762 + pending
Bug #822762 [fonts-cantarell] fonts-cantarell: some accented characters have 
zero-width
Added tag(s) pending.
> tag 822689 + pending
Bug #822689 [fonts-cantarell] [fonts-cantarell] Incorrect widths for some 
accented characters
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
818964: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818964
822689: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822689
822762: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822762
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#821789: marked as done (python{, 3}-django: fails to upgrade from 'jessie': mv: cannot move '/usr/lib/python*/dist-packages/django/conf/app_template/migrations' to '/usr/share/python-django-common

2016-05-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 May 2016 12:34:16 +
with message-id 
and subject line Bug#821789: fixed in ufraw 0.20-4.1
has caused the Debian Bug report #821789,
regarding python{, 3}-django: fails to upgrade from 'jessie': mv: cannot move 
'/usr/lib/python*/dist-packages/django/conf/app_template/migrations' to 
'/usr/share/python-django-common/django/conf/app_template/migrations': 
Directory not empty
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.)


-- 
821789: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821789
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-django,python3-django
Version: 1.9.5-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + lava-dev 

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.

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

  Setting up python-django (1.9.5-1) ...
  mv: '/usr/lib/python2.7/dist-packages/django/conf/app_template/models.py-tpl' 
and '/usr/share/python-django-common/django/conf/app_template/models.py-tpl' 
are the same file
  mv: '/usr/lib/python2.7/dist-packages/django/conf/app_template/apps.py-tpl' 
and '/usr/share/python-django-common/django/conf/app_template/apps.py-tpl' are 
the same file
  mv: '/usr/lib/python2.7/dist-packages/django/conf/app_template/tests.py-tpl' 
and '/usr/share/python-django-common/django/conf/app_template/tests.py-tpl' are 
the same file
  mv: '/usr/lib/python2.7/dist-packages/django/conf/app_template/admin.py-tpl' 
and '/usr/share/python-django-common/django/conf/app_template/admin.py-tpl' are 
the same file
  mv: '/usr/lib/python2.7/dist-packages/django/conf/app_template/views.py-tpl' 
and '/usr/share/python-django-common/django/conf/app_template/views.py-tpl' are 
the same file
  mv: 
'/usr/lib/python2.7/dist-packages/django/conf/app_template/__init__.py-tpl' and 
'/usr/share/python-django-common/django/conf/app_template/__init__.py-tpl' are 
the same file
  mv: cannot move 
'/usr/lib/python2.7/dist-packages/django/conf/app_template/migrations' to 
'/usr/share/python-django-common/django/conf/app_template/migrations': 
Directory not empty
  dpkg: error processing package python-django (--configure):
   subprocess installed post-installation script returned error exit status 123

  Setting up python3-django (1.9.5-1) ...
  mv: '/usr/lib/python3/dist-packages/django/conf/app_template/models.py-tpl' 
and '/usr/share/python-django-common/django/conf/app_template/models.py-tpl' 
are the same file
  mv: '/usr/lib/python3/dist-packages/django/conf/app_template/apps.py-tpl' and 
'/usr/share/python-django-common/django/conf/app_template/apps.py-tpl' are the 
same file
  mv: '/usr/lib/python3/dist-packages/django/conf/app_template/tests.py-tpl' 
and '/usr/share/python-django-common/django/conf/app_template/tests.py-tpl' are 
the same file
  mv: '/usr/lib/python3/dist-packages/django/conf/app_template/admin.py-tpl' 
and '/usr/share/python-django-common/django/conf/app_template/admin.py-tpl' are 
the same file
  mv: '/usr/lib/python3/dist-packages/django/conf/app_template/views.py-tpl' 
and '/usr/share/python-django-common/django/conf/app_template/views.py-tpl' are 
the same file
  mv: '/usr/lib/python3/dist-packages/django/conf/app_template/__init__.py-tpl' 
and '/usr/share/python-django-common/django/conf/app_template/__init__.py-tpl' 
are the same file
  mv: cannot move 
'/usr/lib/python3/dist-packages/django/conf/app_template/migrations' to 
'/usr/share/python-django-common/django/conf/app_template/migrations': 
Directory not empty
  dpkg: error processing package python3-django (--configure):
   subprocess installed post-installation script returned error exit status 123


cheers,

Andreas


python-django_1.9.5-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: ufraw
Source-Version: 0.20-4.1

We believe that the bug you reported is fixed in the latest version of
ufraw, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 821...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Tobias Frost  (supplier of updated ufraw package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact th

Processed: ufraw: diff for NMU version 0.20-4.1

2016-05-06 Thread Debian Bug Tracking System
Processing control commands:

> tags 821789 + patch
Bug #821789 {Done: Raphaël Hertzog } 
[python-django,python3-django] python{, 3}-django: fails to upgrade from 
'jessie': mv: cannot move 
'/usr/lib/python*/dist-packages/django/conf/app_template/migrations' to 
'/usr/share/python-django-common/django/conf/app_template/migrations': 
Directory not empty
Added tag(s) patch.

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



Bug#821789: ufraw: diff for NMU version 0.20-4.1

2016-05-06 Thread Tobias Frost
Control: tags 821789 + patch

Dear maintainer,

I've prepared an NMU for ufraw (versioned as 0.20-4.1). The diff
is attached to this message.

Regards.
diff -u ufraw-0.20/debian/changelog ufraw-0.20/debian/changelog
--- ufraw-0.20/debian/changelog
+++ ufraw-0.20/debian/changelog
@@ -1,3 +1,13 @@
+ufraw (0.20-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS on kfreebsd-amd64 -- the compiler -ffast-math
+   and -fomit-frame-pointer are causing this. (Closes: #821789)
+  * Making build verbose (Closes: #822752). Maybe this gives a hint
+why it fails to build on alpha.
+
+ -- Tobias Frost   Fri, 06 May 2016 14:21:18 +0200
+
 ufraw (0.20-4) unstable; urgency=high
 
   * dcraw.cc: Apply fix from
diff -u ufraw-0.20/debian/rules ufraw-0.20/debian/rules
--- ufraw-0.20/debian/rules
+++ ufraw-0.20/debian/rules
@@ -9,12 +9,17 @@
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 
+DEB_BUILD_ARCH ?= $(shell dpkg-architecture -qDEB_BUILD_ARCH)
+
 CFLAGS = -Wall -g
 
 ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))
CFLAGS += -O0
 else
-   CFLAGS += -O3 -ffast-math -fomit-frame-pointer
+   ifeq (,$(findstring kfreebsd-amd64,$(DEB_BUILD_ARCH)))
+   CFLAGS += -ffast-math -fomit-frame-pointer
+   endif
+   CFLAGS += -O3
 endif
 
 clean:
@@ -66,7 +71,7 @@
 build-stamp: config
dh_testdir
 
-   $(MAKE)
+   $(MAKE) V=1
 
touch build-stamp
 



Processed: ufraw: diff for NMU version 0.20-4.1

2016-05-06 Thread Debian Bug Tracking System
Processing control commands:

> tags 821789 + patch
Bug #821789 {Done: Raphaël Hertzog } 
[python-django,python3-django] python{, 3}-django: fails to upgrade from 
'jessie': mv: cannot move 
'/usr/lib/python*/dist-packages/django/conf/app_template/migrations' to 
'/usr/share/python-django-common/django/conf/app_template/migrations': 
Directory not empty
Ignoring request to alter tags of bug #821789 to the same tags previously set

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



Bug#823604: ruby2.3: FTBFS in testing

2016-05-06 Thread Santiago Vila
Package: ruby2.3
Version: 2.3.1-1
Severity: serious

Dear maintainer:

I can't build this package in stretch.

Every time I try this is what happens:


[...]
   bootstraptest.tmp.rb:4:in `initialize': can't create Thread: Resource 
temporarily unavailable
[...]


Seems as if it wanted an insane amount of memory.

This is strange because of the following reasons:

* It didn't happen in version 2.3.0-5

* My build machine is a QEMU/KVM virtual machine with 6GB of RAM
and 4GB of swap. I'm using sbuild on a stretch chroot.

* By looking at /proc/meminfo, the amount of memory ruby2.3 needs to
build is only about 140 MB on average and 430 MB maximum.

The full build log is attached. I normally use eatmydata but I've
disabled it for this build (and the error still reproduces).

Thanks.

ruby2.3_2.3.1-1_amd64-20160506-1353.gz
Description: application/gzip


Bug#823603: linux: [Local root exploit] Use after free via double-fdput in bpf

2016-05-06 Thread mike_b
Source: linux
Severity: critical
Tags: security newcomer
Justification: root security hole

Dear Maintainer,

A local root privilege escalation exploit (no CVE currently available) for 
Linux >=4.4 was reported in:

https://bugs.chromium.org/p/project-zero/issues/detail?id=808

As far as I can tell, the bug does not yet appear in the Debian Security 
Tracker.

-

The upstream fix can be found in that same link, or more directly at:

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=8358b02bf67d3a5d8a825070e1aa73f25fb2e4c7

Other relevant links:

https://people.canonical.com/~ubuntu-security/cve/2016/CVE-2016-NNN1.html

Thanks.


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

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



Bug#823542: [Pkg-gmagick-im-team] Bug#823542: imagemagick-common: please mitigate CVE-2016-3714, remote arbitrary code execution during handling of delegates

2016-05-06 Thread Bastien Roucaries


Le 5 mai 2016 22:04:13 GMT+02:00, Simon McVittie  a écrit :
>Package: imagemagick-common
>Version: 8:6.8.9.9-7+b2
>Severity: grave
>Tags: security
>Justification: user security hole
>
>I'm sure you're already aware of
>, the most
>serious
>of the recent batch of ImageMagick vulnerabilities published at
>.
>
>There does not seem to be a full upstream fix yet, but it seems the
>vulnerabilities can be mitigated by altering the policy.xml file in
>imagemagick-common. The cost of this mitigation is that some obscure
>file formats, and some features that perhaps shouldn't have been
>implemented in the first place, are disabled.


I think so. Will try to Cook something this week end. If not (i am just  thé 
father of a newborn) feel free to NMU
>Regards,
>S
>
>-- Package-specific info:
>ImageMagick program version
>---
>animate:  ImageMagick 6.8.9-9 Q16 x86_64 2016-04-08
>http://www.imagemagick.org
>compare:  ImageMagick 6.8.9-9 Q16 x86_64 2016-04-08
>http://www.imagemagick.org
>convert:  ImageMagick 6.8.9-9 Q16 x86_64 2016-04-08
>http://www.imagemagick.org
>composite:  ImageMagick 6.8.9-9 Q16 x86_64 2016-04-08
>http://www.imagemagick.org
>conjure:  ImageMagick 6.8.9-9 Q16 x86_64 2016-04-08
>http://www.imagemagick.org
>display:  ImageMagick 6.8.9-9 Q16 x86_64 2016-04-08
>http://www.imagemagick.org
>identify:  ImageMagick 6.8.9-9 Q16 x86_64 2016-04-08
>http://www.imagemagick.org
>import:  ImageMagick 6.8.9-9 Q16 x86_64 2016-04-08
>http://www.imagemagick.org
>mogrify:  ImageMagick 6.8.9-9 Q16 x86_64 2016-04-08
>http://www.imagemagick.org
>montage:  ImageMagick 6.8.9-9 Q16 x86_64 2016-04-08
>http://www.imagemagick.org
>stream:  ImageMagick 6.8.9-9 Q16 x86_64 2016-04-08
>http://www.imagemagick.org
>
>-- System Information:
>Debian Release: stretch/sid
>  APT prefers unstable
>APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
>'experimental')
>Architecture: amd64 (x86_64)
>Foreign Architectures: i386
>
>Kernel: Linux 4.5.0-2-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)
>
>Versions of packages imagemagick depends on:
>ii  imagemagick-6.q16  8:6.8.9.9-7+b2
>
>imagemagick recommends no packages.
>
>imagemagick suggests no packages.
>
>-- no debconf information
>
>___
>Pkg-gmagick-im-team mailing list
>pkg-gmagick-im-t...@lists.alioth.debian.org
>http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-gmagick-im-team

-- 
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.



Bug#821720: [Pkg-mediawiki-devel] Bug#821720: src:wikidiff2: PHP 7.0 Transition

2016-05-06 Thread Seb35

Hello,

I tried to change the dependencies and verify it works with PHP 7.0 on  
Stretch. It’s the first time I create a Debian package, so probably there  
are mistakes, but my result is on https://github.com/Seb35/wikidiff2.


The dependencies are updated and I successfully installed it on Stretch,  
but there is a segfault. The old code didn’t compile, so I tried to fix  
the bug in the returned value (a string) by following  
https://wiki.php.net/phpng-upgrading#zend_string_api. It compiles now but  
the segfault remains. Is there anyone who can investigate on this?


I created a task on Phabricator https://phabricator.wikimedia.org/T134561.

Cheers,
~ Seb35


Le Mon, 18 Apr 2016 23:02:54 +0200, Ondřej Surý  a  
écrit:

Package: src:wikidiff2
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 wikidiff2 package currently build-depends on php5 php5-cli 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: wikidiff2 -- 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

iQJ8BAEBCgBmBQJXFUt+XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHlbkP/0+11NgafGrxNxUrJ791AP3l
9YAI5AWSue9Tgm7xx8MiKloU2ZcQx053ayX8nqQXrpVNvxq9IOLM8lZlUszphWXz
Fq15gxkpzqsL+Ikb/bhs5nN5Do6d3zyxuzALoLl4nfGfLldIPHb5/N4og4Q8M03C
8Ck2c7lSff80wCJGIa2HIM5mCQPi0bCRa1QV+CLYKJVPmJ86fso+Fd5XU/JwtX8F
hi5M/F8yOnQzJhS2cmJXL2OJkmAMrrHV7NxmFH3F18XBppmynH1bpnyf86FT7PBM
jqfZ+p4dZeQ6PjNh4pFPyBMbHlaFsZI4L1Cta9Xapii0caLcQxMogdNoS1rvqae+
qxaAQe5kidkY68gf5eCYEMazQ6owxHrBOpewE4NX3Ox9c

Processed: Re: Bug#823595: linux-grsec: Takes over generic binary packages from linux source

2016-05-06 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 confirmed
Bug #823595 [src:linux-grsec] linux-grsec: Takes over generic binary packages 
from linux source
Added tag(s) confirmed.

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



Bug#823596: gccxml: do not ship in stretch

2016-05-06 Thread Mattia Rizzolo
Source: gccxml
Version: 0.9.0+git20140716-6
Severity: serious

the maintainer filed a RM @ #818848
This package is blocking gcc-4.9 removal, and currently there is only
one rdep.

Filing this bug to get it out of testing and keep it out (FTR the
(transitive) rdeps are going out of testint tomorrow).

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature


Bug#823595: linux-grsec: Takes over generic binary packages from linux source

2016-05-06 Thread Yves-Alexis Perez
control: tag -1 confirmed

On ven., 2016-05-06 at 12:38 +0200, Guillem Jover wrote:
> Source: linux-grsec
> Source-Version: 4.5.2-2+grsec201604290633+1
> Severity: serious
> 
> Hi!
> 
> With latest upload this source package takes over several of the
> generic binary packages from the linux source, which Yves-Alexis
> confirmed on IRC was unintentional.
> 
> For example linux-kbuild-4.5, linux-perf-4.5, hyperv-daemons,
> libcpupower-dev, etc.
> 

Indeed, sorry for the mess, I'll handle it asap (might not be before this
week-end though).

Regards,
-- 
Yves-Alexis



signature.asc
Description: This is a digitally signed message part


Bug#823595: linux-grsec: Takes over generic binary packages from linux source

2016-05-06 Thread Guillem Jover
Source: linux-grsec
Source-Version: 4.5.2-2+grsec201604290633+1
Severity: serious

Hi!

With latest upload this source package takes over several of the
generic binary packages from the linux source, which Yves-Alexis
confirmed on IRC was unintentional.

For example linux-kbuild-4.5, linux-perf-4.5, hyperv-daemons,
libcpupower-dev, etc.

Thanks,
Guillem



Bug#822469: marked as done (asl: FTBFS: error: expected unqualified-id before 'sizeof')

2016-05-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 May 2016 10:34:42 +
with message-id 
and subject line Bug#822469: fixed in asl 0.1.6-2
has caused the Debian Bug report #822469,
regarding asl: FTBFS: error: expected unqualified-id before 'sizeof'
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.)


-- 
822469: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822469
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: asl
Version: 0.1.6-1
Severity: serious

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> [ 27%] Building CXX object 
> src/acl/CMakeFiles/aslacl.dir/Operators/aclGenericAtomicFunction.cxx.o
> cd /<>/obj-x86_64-linux-gnu/src/acl && /usr/bin/c++   
> -Daslacl_EXPORTS 
> -DvtkRenderingCore_AUTOINIT="2(vtkInteractionStyle,vtkRenderingFreeType)" 
> -I/usr/include/vtk-6.2 -I/usr/include/jsoncpp -I/usr/include/x86_64-linux-gnu 
> -I/usr/include/hdf5/openmpi 
> -I/usr/lib/openmpi/include/openmpi/opal/mca/event/libevent2021/libevent 
> -I/usr/lib/openmpi/include/openmpi/opal/mca/event/libevent2021/libevent/include
>  -I/usr/lib/openmpi/include -I/usr/lib/openmpi/include/openmpi 
> -I/usr/include/freetype2 -I/<>/src -I/<>/src/acl  
> -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security 
> -Wdate-time -D_FORTIFY_SOURCE=2  -fpermissive  -O2 -g -DNDEBUG -fPIC   
> -std=gnu++11 -o 
> CMakeFiles/aslacl.dir/Operators/aclGenericAtomicFunction.cxx.o -c 
> /<>/src/acl/Operators/aclGenericAtomicFunction.cxx
> In file included from /<>/src/aslUtilities.h:32:0,
>  from 
> /<>/src/acl/Operators/aclElementConvert.cxx:25:
> /<>/src/acl/cl.hpp: In constructor 'cl::Sampler::Sampler(const 
> cl::Context&, cl_bool, cl_addressing_mode, cl_filter_mode, cl_int*)':
> /<>/src/acl/cl.hpp:4522:21: warning: '_cl_sampler* 
> clCreateSampler(cl_context, cl_bool, cl_addressing_mode, cl_filter_mode, 
> cl_int*)' is deprecated [-Wdeprecated-declarations]
>  object_ = ::clCreateSampler(
>  ^
> In file included from /usr/include/CL/opencl.h:42:0,
>  from /<>/src/acl/cl.hpp:75,
>  from /<>/src/aslUtilities.h:32,
>  from 
> /<>/src/acl/Operators/aclElementConvert.cxx:25:
> /usr/include/CL/cl.h:1366:1: note: declared here
>  clCreateSampler(cl_context  /* context */,
>  ^
> In file included from /<>/src/aslUtilities.h:32:0,
>  from 
> /<>/src/acl/Operators/aclElementConvert.cxx:25:
> /<>/src/acl/cl.hpp:4522:21: warning: '_cl_sampler* 
> clCreateSampler(cl_context, cl_bool, cl_addressing_mode, cl_filter_mode, 
> cl_int*)' is deprecated [-Wdeprecated-declarations]
>  object_ = ::clCreateSampler(
>  ^
> In file included from /usr/include/CL/opencl.h:42:0,
>  from /<>/src/acl/cl.hpp:75,
>  from /<>/src/aslUtilities.h:32,
>  from 
> /<>/src/acl/Operators/aclElementConvert.cxx:25:
> /usr/include/CL/cl.h:1366:1: note: declared here
>  clCreateSampler(cl_context  /* context */,
>  ^
> In file included from /<>/src/aslUtilities.h:32:0,
>  from 
> /<>/src/acl/Operators/aclElementConvert.cxx:25:
> /<>/src/acl/cl.hpp:4527:19: warning: '_cl_sampler* 
> clCreateSampler(cl_context, cl_bool, cl_addressing_mode, cl_filter_mode, 
> cl_int*)' is deprecated [-Wdeprecated-declarations]
>  &error);
>^
> In file included from /usr/include/CL/opencl.h:42:0,
>  from /<>/src/acl/cl.hpp:75,
>  from /<>/src/aslUtilities.h:32,
>  from 
> /<>/src/acl/Operators/aclElementConvert.cxx:25:
> /usr/include/CL/cl.h:1366:1: note: declared here
>  clCreateSampler(cl_context  /* context */,
>  ^
> In file included from /<>/src/aslUtilities.h:32:0,
>  from 
> /<>/src/acl/Operators/aclElementConvert.cxx:25:
> /<>/src/acl/cl.hpp: In constructor 
> 'cl::CommandQueue::CommandQueue(cl_command_queue_properties, cl_int*)':
> /<>/src/acl/cl.hpp:5382:25: warning: '_cl_command_queue* 
> clCreateCommandQueue(cl_context, cl_device_id, cl_command_queue_properties, 
> cl_int*)' is deprecated [-Wdeprecated-declarations]
>  object_ = ::clCreateCommandQueue(
>  ^
> In file included from /usr/include/CL/opencl.h:42:0,
>  from /<>/src/acl/cl.hpp:75,
>  from /<>/src/aslUtilities.h:32,
>  from 
> /<>/src/acl/Operators/aclElementConvert.cxx:25:
> /usr/include/CL/cl.h:1359:1: note: declared here
>  clCreateCommandQueue(cl_c

Bug#823460: [Pkg-xfce-devel] Bug#823460: lightdm: SIGPIPE ignored in session

2016-05-06 Thread Yves-Alexis Perez
control: severity -1 important

On jeu., 2016-05-05 at 00:31 +0100, Ian Jackson wrote:
> All Unix programs are entitled to assume that they start with
> reasonable signal dispositions, which (with a few exceptions) means
> everything set to SIG_DFL.

That's very much false in my opinion and experience. A program definitely
*doesn't* know the signal dispositions it starts with, so if it *needs*
something specific, it'd better do it itself. It might be basic courtesy not
to mess up with signals for your children, but they definitely can't have any
expectation.

>   I have marked this bug "serious" on the
> grounds that I think this is a release-critical bug.

I disagree here too.

> In an xterm:
> 
> zealot:~> perl -e 'print $SIG{PIPE},"\n"'
> IGNORE
> zealot:~>

Well, in my session (Xfce) signal dispositions are reset anyway, so SIGPIPE is
not ignored.

Also note that lightdm by itself doesn't setup the signal dispositions so it's
likely to happen somewhere in the underlying libs. Any help finding where
would be appreciated.

Regards,
-- 
Yves-Alexis



signature.asc
Description: This is a digitally signed message part


Processed: Re: [Pkg-xfce-devel] Bug#823460: lightdm: SIGPIPE ignored in session

2016-05-06 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 important
Bug #823460 [lightdm] lightdm: SIGPIPE ignored in session
Severity set to 'important' from 'serious'

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



Bug#823483: discover: FTBFS: configure: error: Can't find usb library.

2016-05-06 Thread Cyril Brulebois
Chris Lamb  (2016-05-06):
> > Isn't that libusb's #823525 (fixed in -30)?
> 
> Very likely. Closing this one in BCC. :)

FWIW: Indeed fixed with -30 (checked now that it has reached my mirror).


KiBi.


signature.asc
Description: Digital signature


Processed: Proposed patch for #819122

2016-05-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 819122 + patch
Bug #819122 [src:elixir-lang] elixir-lang: fails to auto-build: epmd process 
left running
Added tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
819122: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819122
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#819122: Proposed patch for #819122

2016-05-06 Thread Sergei Golovan
tags 819122 + patch
thanks

Hi!

I'd like to propose the following patch to Makefile for the issue
(also attached):

--
--- a/Makefile
+++ b/Makefile
@@ -223,12 +223,13 @@

 test_stdlib: compile
@ echo "==> elixir (exunit)"
-   $(Q) exec epmd & exit
+   $(Q) epmd -daemon
$(Q) if [ "$(OS)" = "Windows_NT" ]; then \
cd lib/elixir && cmd //C call ../../bin/elixir.bat -r
"test/elixir/test_helper.exs" -pr "test/elixir/**/*_test.exs"; \
else \
cd lib/elixir && ../../bin/elixir -r
"test/elixir/test_helper.exs" -pr "test/elixir/**/*_test.exs"; \
fi
+   $(Q) epmd -kill

 #==> Dialyzer tasks
---

basically, it starts epmd as a daemon during test phase and kills it afterwards.

Cheers!
-- 
Sergei Golovan


elixir-epmd.patch
Description: Binary data


Bug#823588: qemu: FTBFS: xfs_fs.h:42:8: error: redefinition of 'struct fsxattr'

2016-05-06 Thread Michael Tokarev
06.05.2016 12:22, Chris Lamb wrote:
> Source: qemu
> Version: 1:2.5+dfsg-5
> Severity: serious
> Justification: fails to build from source
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
> 
> Dear Maintainer,
> 
> qemu fails to build from source in unstable/amd64:
> 
[]
>   In file included from /usr/include/xfs/xfs.h:58:0,
>from 
> /home/lamby/temp/cdt.20160506095110.j2qkC8fEbA.qemu/qemu-2.5+dfsg/block/raw-posix.c:97:
>   /usr/include/xfs/xfs_fs.h:42:8: error: redefinition of 'struct fsxattr'
>struct fsxattr {
>   ^
>   In file included from 
> /home/lamby/temp/cdt.20160506095110.j2qkC8fEbA.qemu/qemu-2.5+dfsg/block/raw-posix.c:60:0:
>   /usr/include/linux/fs.h:155:8: note: originally defined here
>struct fsxattr {
>   ^

This is a bug in xfsprogs.  See #822470

Thanks,

/mjt



Bug#823567: marked as done (ndiswrapper-dkms fails to compile)

2016-05-06 Thread Debian Bug Tracking System
Your message dated Fri, 6 May 2016 11:49:09 +0200
with message-id <20160506114809.ga18...@debian.org>
and subject line Re: Bug#823567: ndiswrapper-dkms fails to compile
has caused the Debian Bug report #823567,
regarding ndiswrapper-dkms fails to compile
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.)


-- 
823567: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823567
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ndiswrapper-dkms
Version: 1.59-2
Severity: serious
Tags: d-i patch upstream
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

The ndiswrapper source uses the depreciated c function 'strnicmp()',
this function is not in the libc anymore.  It can be replaces with the
working function 'strncasecmp()' without any other changes.

Then it will compile, and I've had zero issues with this so far.

Thanks,
Jon.


*** Reporter, 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 template lines ***


-- System Information:
LSB Version:
core-2.0-ia32:core-2.0-noarch:core-3.0-ia32:core-3.0-noarch:core-3.1-ia32:core-3.1-noarch:core-3.2-ia32:core-3.2-noarch:core-4.0-ia32:core-4.0-noarch:core-4.1-ia32:core-4.1-noarch:security-4.0-ia32:security-4.0-noarch:security-4.1-ia32:security-4.1-noarch
Distributor ID: Kali
Description:Kali GNU/Linux 2.0
Release:2.0
Codename:   sana
Architecture: i686

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

Versions of packages ndiswrapper-dkms depends on:
ii  dkms  2.2.0.3-2

ndiswrapper-dkms recommends no packages.

ndiswrapper-dkms suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.59-3
Control: tag -1 - d-i

On Thu, May 05, 2016 at 05:47:22PM -0800, Jon wrote:
> Package: ndiswrapper-dkms
> Version: 1.59-2
> Severity: serious
> Tags: d-i patch upstream
> Justification: fails to build from source (but built successfully in the past)
> 
> Dear Maintainer,
> 
> The ndiswrapper source uses the depreciated c function 'strnicmp()',
> this function is not in the libc anymore.  It can be replaces with the
> working function 'strncasecmp()' without any other changes.
> 
> Then it will compile, and I've had zero issues with this so far.

This has been fixed since almost a year in 1.59-3.

-- 
Debian Developer - deb.li/jak | jak-linux.org - free software dev

When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to (`inline'). Thank you.--- End Message ---


Processed: found 815650 in squid3/3.5.17-1, found 815650 in kmymoney-dev/4.6.6-3, affects 815650

2016-05-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> found 815650 squid3/3.5.17-1
Bug #815650 [apt] apt: fails to upgrade squid3 from jessie to stretch
Marked as found in versions squid3/3.5.17-1.
> found 815650 kmymoney-dev/4.6.6-3
Bug #815650 [apt] apt: fails to upgrade squid3 from jessie to stretch
The source kmymoney-dev and version 4.6.6-3 do not appear to match any binary 
packages
Marked as found in versions kmymoney-dev/4.6.6-3.
> affects 815650 + kmymoney-dev
Bug #815650 [apt] apt: fails to upgrade squid3 from jessie to stretch
Added indication that 815650 affects kmymoney-dev
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
815650: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815650
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#823591: pep8 - Need stricter dependencies: pkg_resources.VersionConflic

2016-05-06 Thread Bastian Blank
Package: pep8
Version: 1.7.0-2
Severity: serious

pep8 fails to run if python3-pep8 and pep8 does not agree on the
version:

| $ pep8
| Traceback (most recent call last):
|   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 661, 
in _build_master
| ws.require(__requires__)
|   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 962, 
in require
| needed = self.resolve(parse_requirements(requirements))
|   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 854, 
in resolve
| raise VersionConflict(dist, req).with_context(dependent_req)
| pkg_resources.VersionConflict: (pep8 1.6.2 (/usr/lib/python3/dist-packages), 
Requirement.parse('pep8==1.7.0'))
| 
| During handling of the above exception, another exception occurred:
| 
| Traceback (most recent call last):
|   File "/usr/bin/pep8", line 5, in 
| from pkg_resources import load_entry_point
|   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3138, 
in 
| @_call_aside
|   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3124, 
in _call_aside
| f(*args, **kwargs)
|   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3151, 
in _initialize_master_working_set
| working_set = WorkingSet._build_master()
|   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 663, 
in _build_master
| return cls._build_from_requirements(__requires__)
|   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 676, 
in _build_from_requirements
| dists = ws.resolve(reqs, Environment())
|   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 849, 
in resolve
| raise DistributionNotFound(req, requirers)
| pkg_resources.DistributionNotFound: The 'pep8==1.7.0' distribution was not 
found and is required by the application

The package dependency needs to specify a version.

Bastian

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

Kernel: Linux 4.3.0-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 pep8 depends on:
ii  python3-pep8  1.6.2-0.1
pn  python3:any   

pep8 recommends no packages.

pep8 suggests no packages.

-- no debconf information

-- 
Bastian Blank
Berater
Telefon: +49 2166 / 9901-194
E-Mail: bastian.bl...@credativ.de
credativ GmbH, HRB Mönchengladbach 12080, USt-ID-Nummer: DE204566209
Trompeterallee 108, 41189 Mönchengladbach
Geschäftsführung: Dr. Michael Meskes, Jörg Folz, Sascha Heuer



Bug#823483: marked as done (discover: FTBFS: configure: error: Can't find usb library.)

2016-05-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 May 2016 10:20:10 +0100
with message-id 
<1462526410.3444354.599888049.77879...@webmail.messagingengine.com>
and subject line Re: Bug#823483: discover: FTBFS: configure: error: Can't find 
usb library.
has caused the Debian Bug report #823483,
regarding discover: FTBFS: configure: error: Can't find usb library.
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.)


-- 
823483: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823483
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: discover
Version: 2.1.2-7
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

discover fails to build from source in unstable/amd64:

  [..]

  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'discover-build-deps' in 
'../discover-build-deps_2.1.2-7_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package discover-build-deps.
  (Reading database ... 23072 files and directories currently installed.)
  Preparing to unpack discover-build-deps_2.1.2-7_all.deb ...
  Unpacking discover-build-deps (2.1.2-7) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
libexpat1-dev libusb-dev
  The following NEW packages will be installed:
libexpat1-dev libusb-dev
  0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 163 kB of archives.
  After this operation, 1133 kB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 libexpat1-dev amd64 
2.1.1-1 [126 kB]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 libusb-dev amd64 
2:0.1.12-29 [36.9 kB]
  Fetched 163 kB in 0s (0 B/s)
  Selecting previously unselected package libexpat1-dev:amd64.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 23076 files and directories currently installed.)
  Preparing to unpack .../libexpat1-dev_2.1.1-1_amd64.deb ...
  Unpacking libexpat1-dev:amd64 (2.1.1-1) ...
  Selecting previously unselected package libusb-dev.
  Preparing to unpack .../libusb-dev_2%3a0.1.12-29_amd64.deb ...
  Unpacking libusb-dev (2:0.1.12-29) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up libexpat1-dev:amd64 (2.1.1-1) ...
  Setting up libusb-dev (2:0.1.12-29) ...
  Setting up discover-build-deps (2.1.2-7) ...
   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: info: source package discover
  dpkg-buildpackage: info: source version 2.1.2-7
  dpkg-buildpackage: info: source distribution unstable
  dpkg-buildpackage: info: source changed by Petter Reinholdtsen 

   dpkg-source --before-build discover-2.1.2
  dpkg-buildpackage: info: host architecture amd64
   fakeroot debian/rules clean
  dh_testdir
  dh_testroot
  rm -rf builddeb build-deb-stamp configure-deb-stamp config.log config.status
  debconf-updatepo
  debconf-updatepo
  dh_clean
   debian/rules build
  dh_testdir
  mkdir builddeb
  cd builddeb && CFLAGS="-g -O2" ../configure  --prefix=/usr --sbindir=/sbin 
--sysconfdir=/etc --localstatedir=/var --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info 
--with-default-url=file:///lib/discover/list.xml --disable-curl
  checking build system type... x86_64-unknown-linux-gnu
  checking host system type... x86_64-unknown-linux-gnu
  checking target system type... x86_64-unknown-linux-gnu
  checking for gcc... gcc
  checking whether the C compiler works... yes
  checking for C compiler default output file name... a.out
  checking for suffix of executables... 
  checking whether we are cross 

Bug#823586: libnet-dns-zonefile-fast-perl: FTBFS: got: 'acme.com. 0 IN MX 10 mailhost.acme.com.' expected: 'acme.com. IN MX 10 mailhost.acme.com.'

2016-05-06 Thread Chris Lamb
Source: libnet-dns-zonefile-fast-perl
Version: 1.24-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

libnet-dns-zonefile-fast-perl fails to build from source in unstable/amd64:

  [..]

  #  got: 'acme.com. 0 IN MX 10 mailhost.acme.com.'
  # expected: 'acme.com. IN MX 10 mailhost.acme.com.'
  
  #   Failed test 'RR comparison for acme.com IN MX 10 mailhost.acme.com.'
  #   at t/rrs.t line 85.
  #  got: 'acme.com. 0 IN MX 10 mailhost.acme.com.'
  # expected: 'acme.com. IN MX 10 mailhost.acme.com.'
  
  #   Failed test 'RR comparison for acme.com MX 10 mailhost.acme.com.'
  #   at t/rrs.t line 85.
  #  got: 'acme.com. 0 IN MX 10 mailhost.acme.com.'
  # expected: 'acme.com. IN MX 10 mailhost.acme.com.'
  
  #   Failed test 'RR comparison for acme.com. IN  2001:688:0:102::1:2'
  #   at t/rrs.t line 85.
  #  got: 'acme.com. 0 IN  2001:688:0:102::1:2'
  # expected: 'acme.com. IN  2001:688:0:102::1:2'
  
  #   Failed test 'RR comparison for acme.com. IN  2001:688:0:102::3'
  #   at t/rrs.t line 85.
  #  got: 'acme.com. 0 IN  2001:688:0:102::3'
  # expected: 'acme.com. IN  2001:688:0:102::3'
  
  #   Failed test 'RR comparison for acme.com. IN RP abuse.acme.com. acme.com.'
  #   at t/rrs.t line 85.
  #  got: 'acme.com. 0 IN RP abuse.acme.com. acme.com.'
  # expected: 'acme.com. IN RP abuse.acme.com. acme.com.'
  
  #   Failed test 'RR comparison for acme.com. IN SSHFP 2 1 
123456789ABCDEF67890123456789ABCDEF67890'
  #   at t/rrs.t line 85.
  #  got: 'acme.com. 0 IN SSHFP ( 2 1 
123456789abcdef67890123456789abcdef67890 
;xegif-guhil-mekur-sulyz-kavon-begyf-guhyl-meker-suliz-kavan-bexax )'
  # expected: 'acme.com. IN SSHFP ( 2 1 
123456789abcdef67890123456789abcdef67890 
;xegif-guhil-mekur-sulyz-kavon-begyf-guhyl-meker-suliz-kavan-bexax )'
  
  #   Failed test 'RR comparison for acme.com. IN HINFO SUN4/110 UNIX'
  #   at t/rrs.t line 85.
  #  got: 'acme.com. 0 IN HINFO SUN4/110 UNIX'
  # expected: 'acme.com. IN HINFO SUN4/110 UNIX'
  
  #   Failed test 'RR comparison for acme.com. IN HINFO "SUN4/110 foo" UNIX'
  #   at t/rrs.t line 85.
  #  got: 'acme.com. 0 IN HINFO "SUN4/110 foo" UNIX'
  # expected: 'acme.com. IN HINFO "SUN4/110 foo" UNIX'
  
  #   Failed test 'RR comparison for acme.com. IN HINFO "SUN4/110 foo" "UNIX 
bar"'
  #   at t/rrs.t line 85.
  #  got: 'acme.com. 0 IN HINFO "SUN4/110 foo" "UNIX bar"'
  # expected: 'acme.com. IN HINFO "SUN4/110 foo" "UNIX bar"'
  
  #   Failed test 'RR comparison for acme.com. IN TLSA 3 0 1 
1BFC4290C5798EFCC6D4A1F2D79C3C5F49ACCAC687DF42974B68A45F 05BA074F'
  #   at t/rrs.t line 85.
  #  got: 'acme.com. 0 IN TLSA ( 3 0 1 
1bfc4290c5798efcc6d4a1f2d79c3c5f49accac687df42974b68a45f05ba074f 
;xekoz-sobun-becyl-nufyz-sycut-gimoz-duhen-suzoh-zidop-sedas-kicet-zyban-ludik-munah-zycyr-pacug-zixix
 )'
  # expected: 'acme.com. IN TLSA ( 3 0 1 
1bfc4290c5798efcc6d4a1f2d79c3c5f49accac687df42974b68a45f05ba074f 
;xekoz-sobun-becyl-nufyz-sycut-gimoz-duhen-suzoh-zidop-sedas-kicet-zyban-ludik-munah-zycyr-pacug-zixix
 )'
  
  #   Failed test 'RR comparison for acme.com. IN TLSA 3 0 1 ( 
1BFC4290C5798EFCC6D4A1F2D79C3C5F49ACCAC687DF42974B68A45F 05BA074F )'
  #   at t/rrs.t line 85.
  #  got: 'acme.com. 0 IN TLSA ( 3 0 1 
1bfc4290c5798efcc6d4a1f2d79c3c5f49accac687df42974b68a45f05ba074f 
;xekoz-sobun-becyl-nufyz-sycut-gimoz-duhen-suzoh-zidop-sedas-kicet-zyban-ludik-munah-zycyr-pacug-zixix
 )'
  # expected: 'acme.com. IN TLSA ( 3 0 1 
1bfc4290c5798efcc6d4a1f2d79c3c5f49accac687df42974b68a45f05ba074f 
;xekoz-sobun-becyl-nufyz-sycut-gimoz-duhen-suzoh-zidop-sedas-kicet-zyban-ludik-munah-zycyr-pacug-zixix
 )'
  
  #   Failed test 'RR comparison for acme.com. IN TLSA 3 0 1 (
  # 1BFC4290C5798EFCC6D4A1F2D79C3C5F49ACCAC687DF42974B68A45F 
05BA074F )'
  #   at t/rrs.t line 85.
  #  got: 'acme.com. 0 IN TLSA ( 3 0 1 
1bfc4290c5798efcc6d4a1f2d79c3c5f49accac687df42974b68a45f05ba074f 
;xekoz-sobun-becyl-nufyz-sycut-gimoz-duhen-suzoh-zidop-sedas-kicet-zyban-ludik-munah-zycyr-pacug-zixix
 )'
  # expected: 'acme.com. IN TLSA ( 3 0 1 
1bfc4290c5798efcc6d4a1f2d79c3c5f49accac687df42974b68a45f05ba074f 
;xekoz-sobun-becyl-nufyz-sycut-gimoz-duhen-suzoh-zidop-sedas-kicet-zyban-ludik-munah-zycyr-pacug-zixix
 )'
  # Looks like you failed 24 tests of 116.
  t/rrs.t . 
  1..116
  ok 1 - Parsing . 300 IN A 127.0.0.1
  ok 2 - RR comparison for . 300 IN A 127.0.0.1
  ok 3 - Parsing localhost. 300 IN A 127.0.0.1
  ok 4 - RR comparison for localhost. 300 IN A 127.0.0.1
  ok 5 - Parsing localhost IN A 127.0.0.1
  not ok 6 - RR comparison for localhost IN A 127.0.0.1
  ok 7 - Parsing localhost A 127.0.0.1
  not ok 8 - RR comparison for localhost A 127.0.0.1
  ok 9 - Parsing loca

Bug#823483: discover: FTBFS: configure: error: Can't find usb library.

2016-05-06 Thread Chris Lamb
> Isn't that libusb's #823525 (fixed in -30)?

Very likely. Closing this one in BCC. :)


Regards,

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



Bug#823583: gfs2-utils: FTBFS: libgfs2 unit tests [..] FAILED (libgfs2.at:4)

2016-05-06 Thread Chris Lamb
Source: gfs2-utils
Version: 3.1.8-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

gfs2-utils fails to build from source in unstable/amd64:

  [..]

  /bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../../make  -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -D_GNU_SOURCE 
-I../../gfs2/include -I../../make -I../../make -I. -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -O2 -ggdb3  -Wall -Wshadow -Wmissing-prototypes 
-Wmissing-declarations -Wstrict-prototypes -Wdeclaration-after-statement 
-Wpointer-arith -Wwrite-strings -Wcast-align -Wbad-function-cast 
-Wmissing-format-attribute -Wformat=2 -Wformat-security -Wformat-nonliteral 
-Wno-long-long -Wno-strict-aliasing  -c -o libgfs2_la-ondisk.lo `test -f 
'ondisk.c' || echo './'`ondisk.c
  libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../make 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -D_GNU_SOURCE -I../../gfs2/include 
-I../../make -I../../make -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -O2 -ggdb3 -Wall 
-Wshadow -Wmissing-prototypes -Wmissing-declarations -Wstrict-prototypes 
-Wdeclaration-after-statement -Wpointer-arith -Wwrite-strings -Wcast-align 
-Wbad-function-cast -Wmissing-format-attribute -Wformat=2 -Wformat-security 
-Wformat-nonliteral -Wno-long-long -Wno-strict-aliasing -c ondisk.c  -fPIC 
-DPIC -o .libs/libgfs2_la-ondisk.o
  libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../make 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -D_GNU_SOURCE -I../../gfs2/include 
-I../../make -I../../make -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -O2 -ggdb3 -Wall 
-Wshadow -Wmissing-prototypes -Wmissing-declarations -Wstrict-prototypes 
-Wdeclaration-after-statement -Wpointer-arith -Wwrite-strings -Wcast-align 
-Wbad-function-cast -Wmissing-format-attribute -Wformat=2 -Wformat-security 
-Wformat-nonliteral -Wno-long-long -Wno-strict-aliasing -c ondisk.c -o 
libgfs2_la-ondisk.o >/dev/null 2>&1
  /bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../../make  -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -D_GNU_SOURCE 
-I../../gfs2/include -I../../make -I../../make -I. -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -O2 -ggdb3  -Wall -Wshadow -Wmissing-prototypes 
-Wmissing-declarations -Wstrict-prototypes -Wdeclaration-after-statement 
-Wpointer-arith -Wwrite-strings -Wcast-align -Wbad-function-cast 
-Wmissing-format-attribute -Wformat=2 -Wformat-security -Wformat-nonliteral 
-Wno-long-long -Wno-strict-aliasing  -c -o libgfs2_la-config.lo `test -f 
'config.c' || echo './'`config.c
  libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../make 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -D_GNU_SOURCE -I../../gfs2/include 
-I../../make -I../../make -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -O2 -ggdb3 -Wall 
-Wshadow -Wmissing-prototypes -Wmissing-declarations -Wstrict-prototypes 
-Wdeclaration-after-statement -Wpointer-arith -Wwrite-strings -Wcast-align 
-Wbad-function-cast -Wmissing-format-attribute -Wformat=2 -Wformat-security 
-Wformat-nonliteral -Wno-long-long -Wno-strict-aliasing -c config.c  -fPIC 
-DPIC -o .libs/libgfs2_la-config.o
  libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../make 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -D_GNU_SOURCE -I../../gfs2/include 
-I../../make -I../../make -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -O2 -ggdb3 -Wall 
-Wshadow -Wmissing-prototypes -Wmissing-declarations -Wstrict-prototypes 
-Wdeclaration-after-statement -Wpointer-arith -Wwrite-strings -Wcast-align 
-Wbad-function-cast -Wmissing-format-attribute -Wformat=2 -Wformat-security 
-Wformat-nonliteral -Wno-long-long -Wno-strict-aliasing -c config.c -o 
libgfs2_la-config.o >/dev/null 2>&1
  /bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../../make  -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -D_GNU_SOURCE 
-I../../gfs2/include -I../../make -I../../make -I. -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -O2 -ggdb3  -Wall -Wshadow -Wmissing-prototypes 
-Wmissing-declarations -Wstrict-prototypes -Wdeclaration-after-statement 
-Wpointer-arith -Wwrite-strings -Wcast-align -Wbad-function-cast 
-Wmissing-format-attribute -Wformat=2 -Wformat-security -Wformat-nonliteral 
-Wno-long-long -Wno-strict-aliasing  -c -o libgfs2_la-device_geometry.lo `test 
-f 'device_geometry.c' || echo './'`device_geometry.c
  libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../make 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -D_GNU_SOURCE -I../../gfs2/include 
-I../../m

Bug#823587: proguard: FTBFS: build.xml:124: Please set the value of the property gradle.home in the file build.properties, if you want to build the optional ProGuard Gradle task.

2016-05-06 Thread Chris Lamb
Source: proguard
Version: 5.2.1-3
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

proguard fails to build from source in unstable/amd64:

  [..]

  Setting up libgradle-core-java (2.11-1) ...
  Setting up bnd (2.4.1-3) ...
  Setting up libmsv-java (2009.1+dfsg1-5) ...
  Setting up libdom4j-java (1.6.1+dfsg.3-2) ...
  Setting up libjetty-extra-java (6.1.26-5) ...
  Setting up libeasymock-java (3.3.1+ds-3) ...
  Setting up libwagon2-java (2.10-3) ...
  Setting up libmaven3-core-java (3.3.9-4) ...
  Setting up maven-repo-helper (1.8.12) ...
  Setting up ca-certificates-java (20160321) ...
  done.
  Setting up libgtk-3-common (3.20.3-2) ...
  Setting up libgtk-3-0:amd64 (3.20.3-2) ...
  Setting up libatk-wrapper-java-jni:amd64 (0.33.3-6+b1) ...
  Setting up openjdk-8-jre:amd64 (8u91-b14-2) ...
  update-alternatives: using 
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/policytool to provide 
/usr/bin/policytool (policytool) in auto mode
  Setting up default-jre (2:1.8-57) ...
  Setting up openjdk-8-jdk:amd64 (8u91-b14-2) ...
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/appletviewer 
to provide /usr/bin/appletviewer (appletviewer) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jconsole to 
provide /usr/bin/jconsole (jconsole) in auto mode
  Setting up default-jdk (2:1.8-57) ...
  Setting up findbugs (3.0.1-2) ...
  Setting up libgradle-plugins-java (2.11-1) ...
  Setting up gradle (2.11-1) ...
  Setting up proguard-build-deps (5.2.1-3) ...
  Processing triggers for ca-certificates (20160104) ...
  Updating certificates in /etc/ssl/certs...
  173 added, 0 removed; done.
  Running hooks in /etc/ca-certificates/update.d...
  
  Adding debian:ACCVRAIZ1.pem
  Adding debian:ACEDICOM_Root.pem
  Adding debian:AC_Raíz_Certicámara_S.A..pem
  Adding debian:Actalis_Authentication_Root_CA.pem
  Adding debian:AddTrust_External_Root.pem
  Adding debian:AddTrust_Low-Value_Services_Root.pem
  Adding debian:AddTrust_Public_Services_Root.pem
  Adding debian:AddTrust_Qualified_Certificates_Root.pem
  Adding debian:AffirmTrust_Commercial.pem
  Adding debian:AffirmTrust_Networking.pem
  Adding debian:AffirmTrust_Premium.pem
  Adding debian:AffirmTrust_Premium_ECC.pem
  Adding debian:ApplicationCA_-_Japanese_Government.pem
  Adding debian:Atos_TrustedRoot_2011.pem
  Adding debian:Autoridad_de_Certificacion_Firmaprofesional_CIF_A62634068.pem
  Adding debian:Baltimore_CyberTrust_Root.pem
  Adding debian:Buypass_Class_2_CA_1.pem
  Adding debian:Buypass_Class_2_Root_CA.pem
  Adding debian:Buypass_Class_3_Root_CA.pem
  Adding debian:CA_Disig.pem
  Adding debian:CA_Disig_Root_R1.pem
  Adding debian:CA_Disig_Root_R2.pem
  Adding debian:CA_WoSign_ECC_Root.pem
  Adding debian:CFCA_EV_ROOT.pem
  Adding debian:CNNIC_ROOT.pem
  Adding debian:COMODO_Certification_Authority.pem
  Adding debian:COMODO_ECC_Certification_Authority.pem
  Adding debian:COMODO_RSA_Certification_Authority.pem
  Adding debian:Camerfirma_Chambers_of_Commerce_Root.pem
  Adding debian:Camerfirma_Global_Chambersign_Root.pem
  Adding debian:Certification_Authority_of_WoSign_G2.pem
  Adding debian:Certigna.pem
  Adding debian:Certinomis_-_Autorité_Racine.pem
  Adding debian:Certinomis_-_Root_CA.pem
  Adding debian:Certplus_Class_2_Primary_CA.pem
  Adding debian:Certum_Root_CA.pem
  Adding debian:Certum_Trusted_Network_CA.pem
  Adding debian:Chambers_of_Commerce_Root_-_2008.pem
  Adding 
debian:China_Internet_Network_Information_Center_EV_Certificates_Root.pem
  Adding debian:ComSign_CA.pem
  Adding debian:Comodo_AAA_Services_root.pem
  Adding debian:Comodo_Secure_Services_root.pem
  Adding debian:Comodo_Trusted_Services_root.pem
  Adding debian:Cybertrust_Global_Root.pem
  Adding debian:D-TRUST_Root_Class_3_CA_2_2009.pem
  Adding debian:D-TRUST_Root_Class_3_CA_2_EV_2009.pem
  Adding debian:DST_ACES_CA_X6.pem
  Adding debian:DST_Root_CA_X3.pem
  Adding debian:Deutsche_Telekom_Root_CA_2.pem
  Adding debian:DigiCert_Assured_ID_Root_CA.pem
  Adding debian:DigiCert_Assured_ID_Root_G2.pem
  Adding debian:DigiCert_Assured_ID_Root_G3.pem
  Adding debian:DigiCert_Global_Root_CA.pem
  Adding debian:DigiCert_Global_Root_G2.pem
  Adding debian:DigiCert_Global_Root_G3.pem
  Adding debian:DigiCert_High_Assurance_EV_Root_CA.pem
  Adding debian:DigiCert_Trusted_Root_G4.pem
  Adding debian:E-Tugra_Certification_Authority.pem
  Adding debian:EBG_Elektronik_Sertifika_Hizmet_Sağlayıcısı.pem
  Adding debian:EC-ACC.pem
  Adding debian:EE_Certification_Centre_Root_CA.pem
  Adding debian:Entrust.net_Premium_2048_Secure_Server_CA.pem
  Adding debian:Entrust_Root_Certification_Authority.pem
  Adding debian:Entrust_Root_Certification_Authority_-_EC1.pem
  Adding debian:Entrust_Root_Certification_Authority_-_G2.pem
  Adding debian:Equifax_Secure_CA.pem
  Adding debian:Equifax_Secure_Global_eBusiness_CA.p

Bug#821811: Another confirmation...

2016-05-06 Thread Marco Gaiarin

I manage some samba 3.6 network on wheezy, and i can confirm this bug:
i was forced to rollback to pre-badlock samba version, because, sooner
or later, all clients (windows 7 pro) refuse the user logon.

Error it is not everitime the same. I get (sorry for italian... damned
microsoft that translate log messages!):

 May  5 16:31:16 GIUSEPPE microsoft-windows-security-auditing[failure] 4625 
Accesso di un account non riuscito.Soggetto:#011ID 
sicurezza:#011#011S-1-5-18#011Nome account:#011#011GIUSEPPE$#011Dominio 
account:#011#011ACPN#011ID accesso:#011#0110x3e7Tipo di 
accesso:#011#011#0117Account il cui accesso non  riuscito:#011ID 
sicurezza:#011#011S-1-0-0#011Nome account:#011#011ramona#011Dominio 
account:#011#011ACPNInformazioni sull'errore:#011Motivo 
dell'errore:#011#011%2304#011Stato:#011#011#0110xc18d#011Stato 
secondario:#011#0110x0Informazioni sul processo:#011ID processo 
chiamante:#0110x228#011Nome processo 
chiamante:C:\Windows\System32\lsass.exeInformazioni di rete:#011Nome 
workstation:#011GIUSEPPE#011Indirizzo di rete di origine:#011-#011Porta di 
origine:#011#011-Informazioni di autenticazione dettagliate:#011Processo di 
accesso:#011#011Negotiat#011Pacchetto di 
autenticazione:#011Negotiate#011Servizi transitati:#011-#011Nome pacchetto 
(solo NTLM):#011-#011Lunghezza chiave:#011#0110Questo evento viene generato 
quando una richiesta diaccesso non ha esito positivo. Viene generato nel 
computerin cui  stato tentato l'accesso.Il campo Soggetto indica l'account 
nel sistema l
 May  5 16:31:16 GIUSEPPE netlogon[error] 3210 Autenticazione non riuscita con 
\\RITA, un controller didominio di Windows per il dominio ACPN, pertanto 
possibile che le richieste di accesso vengano negate.L<92>impossibilit 
di autenticare pu essere dovuta al mancatoriconoscimento di un altro 
computer connesso alla stessarete tramite lo stesso nome o la stessa password 
perl<92>account di questo computer. Se questo messaggio vienevisualizzato di 
nuovo, contattare l'amministratore disistema.

(eg, roughly 'trust relationshipt not valid'), but also:

 May  5 17:42:27 GIUSEPPE netlogon[error] 5783 L'installazione della sessione 
sul controller di dominio diWindows NT o di Windows 2000 \\RITA per il dominio 
ACPN nonrisponde.  La chiamata RPC corrente effettuata da Netlogonsu \\GIUSEPPE 
a \\RITA  stata annullata.

(eg, roughly 'domain not found').


Note that if i remove the trust relationship on the workstation, and then i
rejoin it, the join work. But still there's no auth at subsequent
reboot (eg, join works but is ineffective).

I've tried all combination of:

ntlm auth = 
server signing = 
client signing = 
client ipc signing = 

but nothing work.


Thanks.



Processed: Bug#816593

2016-05-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> found 816593 38.8.0esr-1~deb7u1
Bug #816593 [src:iceweasel] [FTBFS] iceweasel esr for wheezy on amd64
Marked as found in versions iceweasel/38.8.0esr-1~deb7u1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
816593: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816593
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#821479: Bumping severity of PHP 7.0 transition bugs to serious

2016-05-06 Thread Laurent Destailleur
On Thu, 5 May 2016 10:20:55 +0200 =?utf-8?B?T25kxZllaiBTdXLDvQ==?= <
ond...@sury.org> wrote:
> Dear maintainer(s),
>
> I am bumping the severity of this bug to serious, as we are going to
> remove src:php5 from Debian and your package is blocking the first
> step which is removal of php5 from testing.  Please either update your
> package to support PHP 7.0 or remove the package from Debian unstable
> alltogether.
>
> Cheers,
> Ondrej
>

I am working on upgrading package to be compatible with php7. Should be
soon ready.


Processed: retitle 821504 to RM: htcheck-php -- ROM; obsolete, unmaintained, doesn't support PHP 7.0

2016-05-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> retitle 821504 RM: htcheck-php -- ROM; obsolete, unmaintained, doesn't 
> support PHP 7.0
Bug #821504 [htcheck-php] htcheck-php: PHP 7.0 Transition
Changed Bug title to 'RM: htcheck-php -- ROM; obsolete, unmaintained, doesn't 
support PHP 7.0' from 'htcheck-php: PHP 7.0 Transition'.
> reassign 821504 ftp.debian.org
Bug #821504 [htcheck-php] RM: htcheck-php -- ROM; obsolete, unmaintained, 
doesn't support PHP 7.0
Bug reassigned from package 'htcheck-php' to 'ftp.debian.org'.
No longer marked as found in versions htcheck-php/1:2.0.0~rc1-2.
Ignoring request to alter fixed versions of bug #821504 to the same values 
previously set
> severity 821504 normal
Bug #821504 [ftp.debian.org] RM: htcheck-php -- ROM; obsolete, unmaintained, 
doesn't support PHP 7.0
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
821504: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821504
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems