Bug#801250: jarisplayer: FTBFS: Player.hx:325: characters 8-13 : Capture variables must be lower-case

[Chris Lamb]

Source: jarisplayer
Version: 2.0.15+20131104~dfsg-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,

jarisplayer fails to build from source in unstable/amd64:

  [..]

  haxe -main jaris.Main -swf player.swf -cp src -D no-pattern-matching
  -dce full
  src/jaris/player/Player.hx:325: characters 8-13 : Capture variables
  must be lower-case
  debian/rules:66: recipe for target 'debian/stamp-swf-build' failed
  make: *** [debian/stamp-swf-build] Error 1
  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/jarisplayer_2.0.15+20131104~dfsg-1.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: Mon Oct  5 20:30:02 GMT+12 2015
I: pbuilder-time-stamp: 1444120202
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, devscripts, debhelper, dh-buildinfo, haxe, 
libimage-exiftool-perl, libregexp-assemble-perl, libipc-system-simple-perl, 
lcdf-typetools
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20294 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 devscripts; however:
  Package devscripts is not installed.
 pbuilder-satisfydepends-dummy depends on dh-buildinfo; however:
  Package dh-buildinfo is not installed.
 pbuilder-satisfydepends-dummy depends on haxe; however:
  Package haxe is not installed.
 pbuilder-satisfydepends-dummy depends on libimage-exiftool-perl; however:
  Package libimage-exiftool-perl is not installed.
 pbuilder-satisfydepends-dummy depends on libregexp-assemble-perl; however:
  Package libregexp-assemble-perl is not installed.
 pbuilder-satisfydepends-dummy depends on libipc-system-simple-perl; however:
  Package libipc-system-simple-perl is not installed.
 pbuilder-satisfydepends-dummy depends on lcdf-typetools; however:
  Package lcdf-typetools is not installed.

Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
Reading package lists...
Building dependency tree...
Reading state information...
Initializing package states...
Writing extended state information...
Building tag database...
pbuilder-satisfydepends-dummy is already installed at the requested version 
(0.invalid.0)
pbuilder-satisfydepends-dummy is already installed at the requested version 
(0.invalid.0)
The following NEW packages will be installed:
  aglfn{a} cdbs{a} devscripts{a} dh-buildinfo{a} dh-python{a} haxe{a} 
  lcdf-typetools{a} libexpat1{a} libgc1c2{a} libimage-exiftool-perl{a} 
  libipc-system-simple-perl{a} libjs-jquery{a} libjs-swfobject{a} 
  libkpathsea6{a} libmpdec2{a} libneko0{a} libpython3-stdlib{a} 
  libpython3.4-minimal{a} libpython3.4-stdlib{a} libregexp-assemble-perl{a} 
  libssl1.0.0{a} mime-support{a} neko{a} python3{a} python3-minimal{a} 
  python3.4{a} python3.4-minimal{a} 
0 packages upgraded, 27 newly installed, 0 to remove and 0 not upgraded.
Need to get 13.2 MB of archives. After unpacking 60.8 MB will be used.
Writing extended state information...
Get: 1 http://ftp.de.debian.org/debian/ unstable/main libmpdec2 amd64 2.4.1-1 
[85.7 kB]
Get: 2 http://reproducible.alioth.debian.org/debian/ ./ cdbs 
0.4.130.0~reproducible3 [76.9 kB]
Get: 3 http://reproducible.alioth.debian.org/debian/ ./ libkpathsea6 
2015.20150524.37493-6.0~reproducible2 [156 kB]
Get: 4 http://ftp.de.debian.org/debian/ unstable/main libssl1.0.0 amd64 
1.0.2d-1 [1274 kB]

Bug#801249: monster-masher: FTBFS: error: #error This file requires compiler and library support for the ISO C++ 2011 standard

[Chris Lamb]

Source: monster-masher
Version: 1.8.1-6
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,

monster-masher fails to build from source in unstable/amd64:

  [..]

In file included from /usr/include/c++/5/type_traits:35:0,
 from /usr/include/sigc++-2.0/sigc++/visit_each.h:22,
 from /usr/include/sigc++-2.0/sigc++/functors/slot.h:6,
 from /usr/include/sigc++-2.0/sigc++/signal_base.h:27,
 from /usr/include/sigc++-2.0/sigc++/signal.h:8,
 from /usr/include/sigc++-2.0/sigc++/sigc++.h:86,
 from /usr/include/glibmm-2.4/glibmm/thread.h:51,
 from /usr/include/glibmm-2.4/glibmm.h:87,
 from
 /usr/include/libgnomecanvasmm-2.6/libgnomecanvasmm/pixbuf.h:7,
 from graphic.hpp:27,
 from animation.cpp:24:
/usr/include/c++/5/bits/c++0x_warning.h:32:2: error: #error This file
requires compiler and library support for the ISO C++ 2011 standard.
This support is currently experimental, and must be enabled with the
-std=c++11 or -std=gnu++11 compiler options.

  [..]

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


https://reproducible.debian.net/logs/unstable/amd64/monster-masher_1.8.1-6.build1.log.gz


Regards,

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

Bug#799642: marked as done (presage: ABI transition needed for libstdc++ v5)

[Debian Bug Tracking System]

Your message dated Wed, 07 Oct 2015 22:00:23 +
with message-id 
and subject line Bug#799642: fixed in presage 0.9.1-1.1
has caused the Debian Bug report #799642,
regarding presage: ABI transition needed for libstdc++ v5
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.)


-- 
799642: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799642
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: presage
Version: 0.9.1-1
Severity: serious
Justification: ABI break since stable
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11

Background[1]: libstdc++6 introduces a new ABI to conform to the
C++11 standard, but keeps the old ABI to not break existing binaries.
Packages which are built with g++-5 from experimental (not the one
from testing/unstable) are using the new ABI.  Libraries built from
this source package export some of the new __cxx11 or B5cxx11 symbols,
dropping other symbols.  If these symbols are part of the API of
the library, then this rebuild with g++-5 will trigger a transition
for the library.

In the case of presage, at least
Presage(PresageCallback* callback, const std::string config)
appears to change its ABI in this way, so a transition does appear to
be needed. The transition normally consists of renaming the affected library
packages, adding a v5 suffix (libpresage1v5). The SONAME should not be
changed when doing this.

If an upgrade to a new upstream SONAME is already planned, and that
SONAME has never been available in Debian compiled with g++-4, then an
alternative way to carry out the transition would be to bump the
SONAME. However, the libstdc++ transition has been going on for a
month already, and anything that makes it take longer is bad for Debian,
so introducing new upstream code is not desired at this stage.

These follow-up transitions for libstdc++ are not going through exactly
the normal transition procedure, because many entangled transitions are
going on at the same time, and the usual ordered transition procedure
does not scale that far. When all the C++ libraries on which this library
depends have started their transitions in unstable if required, this
library should do the same, closing this bug; the release team will deal
with binNMUs as needed.

Looking at the build-dependencies of presage, cppunit and tinyxml have
already had their transitions, so I believe presage is now ready.

The package might be NMU'd if there is no maintainer response. The
release team have declared a 2 day NMU delay[2] for packages involved
in the libstdc++ transition, in order to get unstable back to a usable
state in a finite time.

Regards,
S

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition
[2] https://lists.debian.org/debian-devel-announce/2015/08/msg0.html
--- End Message ---
--- Begin Message ---
Source: presage
Source-Version: 0.9.1-1.1

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

Debian distribution maintenance software
pp.
ChangZhuo Chen (陳昌倬)  (supplier of updated presage 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: Sun, 04 Oct 2015 13:52:15 +0800
Source: presage
Binary: presage presage-dbg libpresage-doc libpresage1v5 libpresage1-dbg 
libpresage-data libpresage-dev python-presage python-presage-dbg gprompter 
gprompter-dbg pyprompter presage-dbus
Architecture: source amd64 all
Version: 0.9.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Matteo Vescovi 
Changed-By: ChangZhuo Chen (陳昌倬) 
Description:
 gprompter  - intelligent predictive GTK+ text editor
 gprompter-dbg - intelligent predictive GTK+ text editor (debugging symbols)
 libpresage-data - intelligent predictive text entry platform (data files)
 libpresage-dev - intelligent predictive text entry platform (development files)
 libpresage-doc - intelligent predictive text entry platform (documentation)
 libpresage1-dbg - intelligent predictive text entry platform 

Bug#800950: marked as done (mate-media-common has disappeared)

[Debian Bug Tracking System]

Your message dated Wed, 07 Oct 2015 22:00:16 +
with message-id 
and subject line Bug#800950: fixed in mate-media 1.10.0-2
has caused the Debian Bug report #800950,
regarding mate-media-common has disappeared
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.)


-- 
800950: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800950
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mate-media
Version: 1.10.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed mate-media is no longer
installable in sid since mate-media-common was accidently decrufted:


http://bugs.debian.org/800557

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

mate-media | 1.8.0+dfsg1-4 | all
mate-media-common | 1.8.0+dfsg1-4 | all
mate-media-common |   1.10.0-1 | all

--- Reason ---
RoQA; obsolete cruft binary
--


mate-media-common 1.10.0-1 should not have been in this list ... please
upload it again.


Andreas
--- End Message ---
--- Begin Message ---
Source: mate-media
Source-Version: 1.10.0-2

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated mate-media package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 07 Oct 2015 10:30:26 +0200
Source: mate-media
Binary: mate-media mate-media-common mate-media-dbg
Architecture: source all amd64
Version: 1.10.0-2
Distribution: unstable
Urgency: medium
Maintainer: MATE Packaging Team 
Changed-By: Mike Gabriel 
Description:
 mate-media - MATE media utilities
 mate-media-common - MATE media utilities (common files)
 mate-media-dbg - MATE media utilities (debugging symbols)
Closes: 800950
Changes:
 mate-media (1.10.0-2) unstable; urgency=medium
 .
   * Re-upload for sorting out a recent auto-decrufter code bug.
 (Closes: #800950).
Checksums-Sha1:
 032268c5b4f257d56cb9c710b4d4674c4eb0faac 2367 mate-media_1.10.0-2.dsc
 9eb568d106ce0bffed630c727c0ca6f35f1a2bbd 4052 mate-media_1.10.0-2.debian.tar.xz
 1da404095e3cc4a82b879c44ad668530874f5c2d 182676 
mate-media-common_1.10.0-2_all.deb
 d284879ffcf8523b98e27bced277640f6e6c43da 245998 
mate-media-dbg_1.10.0-2_amd64.deb
 7a71e7870a37bd18690fa587c00e43f7f746cb27 58264 mate-media_1.10.0-2_amd64.deb
Checksums-Sha256:
 cd2b8136f97b76ea49b0a3f11208846bbbc21b9155a90d873ea3f17e8a6d735c 2367 
mate-media_1.10.0-2.dsc
 dd747b3edf7a72664049cdee0b04a069401df8f8b9a66399de204fb7188deb04 4052 
mate-media_1.10.0-2.debian.tar.xz
 bf8fd2c8b97f86081280ea3d2f572d7f02bc756b79ef9a52064e9bc0bd0229ea 182676 
mate-media-common_1.10.0-2_all.deb
 61f5417e790db883ff231f67fd4a4841bca1204bdc84ec0c5623a084c86572c1 245998 
mate-media-dbg_1.10.0-2_amd64.deb
 eaf6c0d4b0f52cdc828e0606e7a2033aff690fb80a49edab132c5f5ae80dff13 58264 
mate-media_1.10.0-2_amd64.deb
Files:
 fad39017addd40b435ae3db1a3f35212 2367 x11 optional mate-media_1.10.0-2.dsc
 9b60d415fd5589580c9ad04ee45fb3dd 4052 x11 optional 
mate-media_1.10.0-2.debian.tar.xz
 5b61098f8c95f47eadeababeafcb3449 182676 x11 optional 
mate-media-common_1.10.0-2_all.deb
 54208e38a719fe014338006a171eb7d9 245998 debug extra 
mate-media-dbg_1.10.0-2_amd64.deb
 84022b0112067930a0e7fb471495c0ee 58264 x11 optional 
mate-media_1.10.0-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWFNoEAAoJEJr0azAldxsx4EEP/jMRT/v5IHduqaw9D3pWPIEz
gloVRsk+zxNaYyvLxqv6otJx+S2h2n9yjSNVpxLBoXGveQvaCXX2FrmLpSJs9o1C
udwrIiJe7MXZnMyWKh9XRbOV2ffBUFPzfY3C/fb949/NOLSuNvdcUgSx9yEhrrwo
pVuDLxSgSAwrkrGQW5Rlel3rQNOEELiLUgVnqsGegSRM5E/hnAP/+qIE3CmI4hmb
LIJTIPm8OrWNygi9H4k31SKuiwYlQ0i/kzx+LuLmniQ0zg3+huIgV/noFmZRxHF9
WtxGxdrrKB/iPjVQYJIOEvgcfpqHm+JidTP3QkhCx+UHVdpaBRe0ZIDCF1/3ksNI

Bug#798924: /usr/lib/x86_64-linux-gnu/jni/libatk-wrapper.so.6.0.0: SIGSEGV on Netbeans startup

[Samuel Thibault]

Hello,

Alexandre Pereira Nunes, le Wed 07 Oct 2015 15:04:36 -0300, a écrit :
> I'm attaching an additional patch that complements the old netbeans one.
> With this, I can now open netbeans.

Thanks!  I have uploaded it in 0.33.3-2.  Tim, Michael, could you try
it?

Samuel

Bug#798924: /usr/lib/x86_64-linux-gnu/jni/libatk-wrapper.so.6.0.0: SIGSEGV on Netbeans startup

[Samuel Thibault]

Alexandre Pereira Nunes, le Wed 07 Oct 2015 14:42:16 -0300, a écrit :
> I've patched the package build system to generate a debug package. This can
> further help getting usable stack traces from java core dump.

Good idea.  I'll integrate it after your patch gets to testing (since
the debug package will need a NEW processing).

Samuel

Bug#799310: marked as done (shortuuid: FTBFS: Incompatible with pep8 1.6.2-0.1)

[Debian Bug Tracking System]

Your message dated Wed, 07 Oct 2015 23:34:33 +
with message-id 
and subject line Bug#799310: fixed in shortuuid 0.4.2-4
has caused the Debian Bug report #799310,
regarding shortuuid: FTBFS: Incompatible with pep8 1.6.2-0.1
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.)


-- 
799310: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: shortuuid
Version: 0.4.2-3
Severity: serious
Tags: patch
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,

shortuuid fails to build from source in unstable/amd64 due to the update
of pep8 to 1.6.2.

A patch is attached.

  [..]

  python2.7 build2.7/lib.*-2.7/shortuuid/tests.py
  E..
  ==
  ERROR: test_pep8 (__main__.ClassShortUUIDTest)
  --
  Traceback (most recent call last):
File "build2.7/lib.linux-x86_64-2.7/shortuuid/tests.py", line 107,
in test_pep8
  config_file=True)
File "/usr/lib/python2.7/dist-packages/pep8.py", line 1788, in
__init__
  arglist, parse_argv, config_file, parser)
File "/usr/lib/python2.7/dist-packages/pep8.py", line 2074, in
process_options
  options = read_config(options, args, arglist, parser)
File "/usr/lib/python2.7/dist-packages/pep8.py", line 1987, in
read_config
  if cli_conf and os.path.isfile(cli_conf):
File "/usr/lib/python2.7/genericpath.py", line 37, in isfile
  st = os.stat(path)
  TypeError: coercing to Unicode: need string or buffer, bool found
  
  --
  Ran 11 tests in 0.009s
  
  FAILED (errors=1)
  debian/rules:16: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 1
  make[1]: Leaving directory '/tmp/buildd/shortuuid-0.4.2'
  debian/rules:7: recipe for target 'build' failed
  make: *** [build] 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/shortuuid_0.4.2-3.build1.log.gz

Patch attached.


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: Thu Sep 17 03:11:16 GMT+12 2015
I: pbuilder-time-stamp: 1442502676
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: debhelper (>= 8.0.0), python-all (>= 2.6), python-setuptools, pep8, 
python3-all (>= 3.2), python3-setuptools, python3-pep8, quilt
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20254 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 python-all (>= 2.6); however:
  Package python-all is not installed.
 pbuilder-satisfydepends-dummy depends on python-setuptools; however:
  Package python-setuptools is not installed.
 pbuilder-satisfydepends-dummy depends on pep8; however:
  Package pep8 is not installed.
 pbuilder-satisfydepends-dummy depends on python3-all (>= 3.2); however:
  Package python3-all is not installed.
 

Bug#800952: marked as done (vdr-plugin-vcd: FTBFS with vdr 2.2.0: DeviceTrickSpeed API change)

[Debian Bug Tracking System]

Your message dated Wed, 07 Oct 2015 23:34:38 +
with message-id 
and subject line Bug#800952: fixed in vdr-plugin-vcd 0.9-25
has caused the Debian Bug report #800952,
regarding vdr-plugin-vcd: FTBFS with vdr 2.2.0: DeviceTrickSpeed API change
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.)


-- 
800952: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800952
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vdr-plugin-vcd
Version: 0.9-22
Severity: serious
Tags: sid stretch
Justification: fails to build from source (but built successfully in the past)
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

vdr-plugin-vcd cannot be built with vdr 2.2.0 in sid:

 debian/rules build
dh build
   dh_testdir
   dh_auto_configure
   debian/rules override_dh_auto_build
make[1]: Entering directory '/tmp/buildd/vdr-plugin-vcd-0.9'
dh_auto_build -- all VDRDIR=/usr/include/vdr LIBDIR=. LOCALEDIR=locale
make -j1 all VDRDIR=/usr/include/vdr LIBDIR=. LOCALEDIR=locale
make[2]: Entering directory '/tmp/buildd/vdr-plugin-vcd-0.9'
g++ -fPIC -O2 -Wall -Woverloaded-virtual -c -DPLUGIN_NAME_I18N='"vcd"' 
-D_GNU_SOURCE -I/usr/include/vdr/include vcd.c
g++ -fPIC -O2 -Wall -Woverloaded-virtual -c -DPLUGIN_NAME_I18N='"vcd"' 
-D_GNU_SOURCE -I/usr/include/vdr/include functions.c
g++ -fPIC -O2 -Wall -Woverloaded-virtual -c -DPLUGIN_NAME_I18N='"vcd"' 
-D_GNU_SOURCE -I/usr/include/vdr/include menu.c
g++ -fPIC -O2 -Wall -Woverloaded-virtual -c -DPLUGIN_NAME_I18N='"vcd"' 
-D_GNU_SOURCE -I/usr/include/vdr/include player.c
player.c: In member function 'void cVcdPlayer::TrickSpeed(int)':
player.c:164:25: error: no matching function for call to 
'cVcdPlayer::DeviceTrickSpeed(int&)'
  DeviceTrickSpeed(sp);
 ^
In file included from player.h:27:0,
 from player.c:24:
/usr/include/vdr/player.h:30:8: note: candidate: void 
cPlayer::DeviceTrickSpeed(int, bool)
   void DeviceTrickSpeed(int Speed, bool Forward) { if (device) 
device->TrickSpeed(Speed, Forward); }
^
/usr/include/vdr/player.h:30:8: note:   candidate expects 2 arguments, 1 
provided
Makefile:61: recipe for target 'player.o' failed
make[2]: *** [player.o] Error 1
make[2]: Leaving directory '/tmp/buildd/vdr-plugin-vcd-0.9'
dh_auto_build: make -j1 all VDRDIR=/usr/include/vdr LIBDIR=. LOCALEDIR=locale 
returned exit code 2
debian/rules:12: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/tmp/buildd/vdr-plugin-vcd-0.9'
debian/rules:9: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2



Andreas
--- End Message ---
--- Begin Message ---
Source: vdr-plugin-vcd
Source-Version: 0.9-25

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

Debian distribution maintenance software
pp.
Tobias Grimm  (supplier of updated vdr-plugin-vcd 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, 08 Oct 2015 01:19:21 +0200
Source: vdr-plugin-vcd
Binary: vdr-plugin-vcd
Architecture: source amd64
Version: 0.9-25
Distribution: unstable
Urgency: medium
Maintainer: Debian VDR Team 
Changed-By: Tobias Grimm 
Description:
 vdr-plugin-vcd - VDR Plugin for playing (S)VCD's
Closes: 800952
Changes:
 vdr-plugin-vcd (0.9-25) unstable; urgency=medium
 .
   * Standards-Version: 3.9.6
   * Added VDR 2.2.0 compatibility
   * Added fix for VDR 2.1.3 API changes (Closes: #800952)
   * Fixed references to new upstream location
Checksums-Sha1:
 e73f6c6e107b9deec6825644dab1e6631bf14ea1 2023 vdr-plugin-vcd_0.9-25.dsc
 f5457e2fe6f2bf761dbeaf5dcb16e8feff970f37 33687 vdr-plugin-vcd_0.9.orig.tar.gz
 68bd18fbd75d782e4a60866431e1b386a1e3517b 9184 
vdr-plugin-vcd_0.9-25.debian.tar.xz
 1bf4885de2a489568b76507f862f58276eaa7603 42578 vdr-plugin-vcd_0.9-25_amd64.deb
Checksums-Sha256:
 

Processed: Re: core-network: Privilege escalation via core-gui

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 799756 upstream
Bug #799756 [core-network] core-network: Privilege escalation via core-gui
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#799756: core-network: Privilege escalation via core-gui

[Eriberto Mota]

tags 799756 upstream
thanks


Hi all,

I am waiting a reply from upstream.

Thanks for your comments.

Regards,

Eriberto

Bug#801248: blends-image-hamradio: uninstallable in sid: unsatisfiable Depends: live-build (>= 5.0)

[Andreas Beckmann]

Package: blends-image-hamradio
Version: 0.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable in sid:

0m21.9s ERROR: Command failed (status=100): ['chroot', 
'/tmp/piupartss/tmp6JxkYb', 'apt-get', '-y', 'install', 
'blends-image-hamradio=0.1']
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  
  The following packages have unmet dependencies:
   blends-image-hamradio : Depends: live-build (>= 5.0) but it is not going to 
be installed
  E: Unable to correct problems, you have held broken packages.


The version of live-build available in sid is 5.0~a11-1


Cheers,

Andreas

Processed: severity of 801260 is important

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 801260 important
Bug #801260 [clisp] clisp: Clisp cannot be buit for hurd-i386
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#801255: ruby-haml-rails: FTBFS: kernel_require.rb:55:in `require': cannot load such file -- rails/generators/mailer/mailer_generator (LoadError)

[Chris Lamb]

Source: ruby-haml-rails
Version: 0.9.0-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,

ruby-haml-rails fails to build from source in unstable/amd64:

  [..]
  
  
┌──┐
  │ Run tests for ruby2.1 from debian/ruby-tests.rake   
  │
  
└──┘
  
  
RUBYLIB=/tmp/buildd/ruby-haml-rails-0.9.0/debian/ruby-haml-rails/usr/lib/ruby/vendor_ruby:.
  rake2.1 -f debian/ruby-tests.rake
  /usr/bin/ruby2.1 -I"test" -I"/usr/lib/ruby/vendor_ruby"
  "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb"
  "test/lib/generators/haml/controller_generator_test.rb"
  "test/lib/generators/haml/mailer_generator_test.rb"
  "test/lib/generators/haml/scaffold_generator_test.rb" -v
  /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in
  `require': cannot load such file --
  rails/generators/mailer/mailer_generator (LoadError)
from
/usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in
`require'
from /tmp/buildd/ruby-haml-rails-0.9.0/test/test_helper.rb:64:in
`block (2 levels) in require_generators'
from /tmp/buildd/ruby-haml-rails-0.9.0/test/test_helper.rb:62:in
`each'
from /tmp/buildd/ruby-haml-rails-0.9.0/test/test_helper.rb:62:in
`block in require_generators'
from /tmp/buildd/ruby-haml-rails-0.9.0/test/test_helper.rb:61:in
`each'
from /tmp/buildd/ruby-haml-rails-0.9.0/test/test_helper.rb:61:in
`require_generators'
from /tmp/buildd/ruby-haml-rails-0.9.0/test/test_helper.rb:73:in
`'
from
/usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in
`require'
from
/usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in
`require'
from

/tmp/buildd/ruby-haml-rails-0.9.0/test/lib/generators/haml/controller_generator_test.rb:1:in
`'
from
/usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in
`require'
from
/usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in
`require'
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:15:in
`block in '
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:4:in
`select'
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:4:in
`'
  rake aborted!
  Command failed with status (1): [ruby -I"test"
  -I"/usr/lib/ruby/vendor_ruby"
  "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb"
  "test/lib/generators/haml/controller_generator_test.rb"
  "test/lib/generators/haml/mailer_generator_test.rb"
  "test/lib/generators/haml/scaffold_generator_test.rb" -v]
  /usr/bin/rake2.1:33:in `'
  Tasks: TOP => default
  (See full trace by running task with --trace)
  ERROR: Test "ruby2.1" failed. Exiting.
  dh_auto_install: dh_ruby --install
  /tmp/buildd/ruby-haml-rails-0.9.0/debian/ruby-haml-rails returned exit
  code 1
  debian/rules:18: recipe for target 'binary' failed
  make: *** [binary] Error 1
  dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit
  status 2

  [..]

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


https://reproducible.debian.net/logs/unstable/amd64/ruby-haml-rails_0.9.0-3.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: Mon Oct  5 06:14:58 GMT+12 2015
I: pbuilder-time-stamp: 1444068898
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: debhelper (>= 9~), gem2deb, rake, ruby-actionpack (>= 4.0.1), 
ruby-activesupport (>= 4.0.1), ruby-haml (>= 4.0.6), ruby-html2haml (>= 1.0.1), 
ruby-railties (>= 4.0.1), ruby-test-unit
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously 

Processed: vcr.py: FTBFS: Build requires internet access ("gaierror: [Errno -2] Name or service not known")

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 795940 + pending
Bug #795940 [src:vcr.py] vcr.py: FTBFS: Build requires internet access 
("gaierror: [Errno -2] Name or service not known")
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#801260: clisp: Clisp cannot be buit for hurd-i386

[Flavio Cruz]

Package: clisp
Version: 1:2.49-10
Severity: serious
Tags: patch
Justification: fails to build from source

Dear Maintainer,

Clisp cannot be built under hurd-i386 since clisp does not recognize Hurd errno 
values. This patches fixes that and prevents clisp to not crash when using 
fsync().
Please see https://lists.debian.org/debian-hurd/2015/09/msg00031.html for more 
information.

-- System Information:
Debian Release: stretch/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: hurd-i386 (i686-AT386)

Kernel: GNU-Mach 1.5+git20150922-486/Hurd-0.6
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages clisp depends on:
ii  libc0.3   2.19-22
ii  libffcall11.10+cvs20100619-3
ii  libncurses5   6.0+20150810-1
ii  libreadline5  5.2+dfsg-3
ii  libsigsegv2   2.10-4+b1
ii  libtinfo5 6.0+20150810-1

clisp recommends no packages.

Versions of packages clisp suggests:
ii  clisp-dev  1:2.49-10
ii  clisp-doc  1:2.49-10
ii  gdb7.10-1
pn  slime  

-- no debconf information
Description: Define IS_EINVAL_EXTRA for Hurd systems
 clisp (1:2.49-10) unstable; urgency=medium
 .
   * Makes clisp compile under debuild
   * Solves https://lists.debian.org/debian-hurd/2012/06/msg00053.html)
Author: Flavio Cruz 

Last-Update: 2015-09-23

--- clisp-2.49.orig/src/stream.d
+++ clisp-2.49/src/stream.d
@@ -3483,6 +3483,8 @@ local void clear_tty_input (Handle handl
   #define IS_EINVAL_EXTRA  ((errno==EBADF)||(errno==EACCES)||(errno==EBADRQC))
 #elif defined(UNIX_DARWIN) || defined(UNIX_FREEBSD) || defined(UNIX_NETBSD) || defined(UNIX_OPENBSD)
   #define IS_EINVAL_EXTRA  ((errno==EOPNOTSUPP)||(errno==ENOTSUP)||(errno==ENODEV))
+#elif defined(UNIX_HURD)
+  #define IS_EINVAL_EXTRA  ((errno==EOPNOTSUPP)||(errno==EMIG_BAD_ID))
 #else
   #define IS_EINVAL_EXTRA  0
 #endif

Bug#798924: marked as done (/usr/lib/x86_64-linux-gnu/jni/libatk-wrapper.so.6.0.0: SIGSEGV on Netbeans startup)

[Debian Bug Tracking System]

Your message dated Wed, 07 Oct 2015 22:48:56 +
with message-id 
and subject line Bug#798924: fixed in java-atk-wrapper 0.33.3-2
has caused the Debian Bug report #798924,
regarding /usr/lib/x86_64-linux-gnu/jni/libatk-wrapper.so.6.0.0: SIGSEGV on 
Netbeans startup
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
798924: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798924
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libatk-wrapper-java-jni
Version: 0.33.3-1
Severity: normal
File: /usr/lib/x86_64-linux-gnu/jni/libatk-wrapper.so.6.0.0

Dear Maintainer,

the latest version makes Netbeans (8.0.2 and 8.1beta) SIGSEGV on startup.
Tested with Debian OpenJDK 7 and 8.

Downgrading libatk-wrapper-java and libatk-wrapper-java-jni to version 0.33.0-5 
resolves the issue.

Best regards, Tim

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

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

Versions of packages libatk-wrapper-java-jni:amd64 depends on:
ii  libatk-bridge2.0-0   2.16.0-2
ii  libatk-wrapper-java  0.33.3-1
ii  libatk1.0-0  2.16.0-2
ii  libatspi2.0-02.16.0-1
ii  libc62.19-20
ii  libcairo-gobject21.14.2-2
ii  libcairo21.14.2-2
ii  libdbus-1-3  1.10.0-2
ii  libgdk-pixbuf2.0-0   2.31.5-1
ii  libglib2.0-0 2.44.1-1.1
ii  libgtk-3-0   3.16.6-1
ii  libgtk2.0-0  2.24.28-1
ii  libpango-1.0-0   1.36.8-3
ii  libpangocairo-1.0-0  1.36.8-3

libatk-wrapper-java-jni:amd64 recommends no packages.

libatk-wrapper-java-jni:amd64 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: java-atk-wrapper
Source-Version: 0.33.3-2

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

Debian distribution maintenance software
pp.
Samuel Thibault  (supplier of updated java-atk-wrapper 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 08 Oct 2015 00:24:59 +0200
Source: java-atk-wrapper
Binary: libatk-wrapper-java libatk-wrapper-java-jni
Architecture: source amd64 all
Version: 0.33.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Accessibility Team 
Changed-By: Samuel Thibault 
Description:
 libatk-wrapper-java - ATK implementation for Java using JNI
 libatk-wrapper-java-jni - ATK implementation for Java using JNI (JNI bindings)
Closes: 798924
Changes:
 java-atk-wrapper (0.33.3-2) unstable; urgency=medium
 .
   [ Alexandre Pereira Nunes ]
   * patches/netbeans: Complete patch (Closes: #798924).
Checksums-Sha1:
 75ab11814cace7604df06b1699caa6648bee5168 2339 java-atk-wrapper_0.33.3-2.dsc
 0ad4948397c36631133fdde6a38114fe058a346c 4370 
java-atk-wrapper_0.33.3-2.debian.tar.bz2
 508dfa086eac39bda039b255c8d20e42e76131a7 36526 
libatk-wrapper-java-jni_0.33.3-2_amd64.deb
 289d6723df53a8c5bedb1e13dcd9fb5751eec5b9 43114 
libatk-wrapper-java_0.33.3-2_all.deb
Checksums-Sha256:
 59774585d68ba608c9a39ac660da0334e32e861bd09dea930bdc6546571865a5 2339 
java-atk-wrapper_0.33.3-2.dsc
 ce09c86bb98a430ede010caf8989a8b8d79002524a0991bc94ca3b8495f5c27d 4370 
java-atk-wrapper_0.33.3-2.debian.tar.bz2
 4ccac6b670c1e5e2ed8144601f2de447cad1e096676eded29a69957e048cfc32 36526 
libatk-wrapper-java-jni_0.33.3-2_amd64.deb
 774981bed1b010d9158f8f0597bcb9446c75da7e5af9fa2a6afbe0d3bb79f777 43114 
libatk-wrapper-java_0.33.3-2_all.deb
Files:
 358da767e836d15de37d9338cb714613 2339 java optional 
java-atk-wrapper_0.33.3-2.dsc
 3e8232348d00f7ee7cd0150b52eefe32 4370 java optional 
java-atk-wrapper_0.33.3-2.debian.tar.bz2
 411bd0025b342fc23b8437216ba268d6 36526 java optional 

Processed: user debian...@lists.debian.org, usertagging 793234, found 793234 in 3.4.0-1, usertagging 791222 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 793234 piuparts
There were no usertags set.
Usertags are now: piuparts.
> found 793234 3.4.0-1
Bug #793234 [src:ergo] ergo: change of type in system_error might break with 
GCC-5
Marked as found in versions ergo/3.4.0-1.
> usertags 791222 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 791222 + libogre-1.8.0
Bug #791222 [src:ogre-1.8] ogre-1.8: library transition may be needed when GCC 
5 is the default
Added indication that 791222 affects libogre-1.8.0
> usertags 801078 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 801078 + js2-mode
Bug #801078 [elpa-js2-mode] elpa-js2-mode: js2-mode uninstallable due to wrong 
Breaks in elpa-js2-mode
Added indication that 801078 affects js2-mode
> thanks
Stopping processing here.

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

Bug#801252: ruby-omniauth-ldap: FTBFS: kernel_require.rb:55:in `require': cannot load such file -- rack/test (LoadError)

[Chris Lamb]

Source: ruby-omniauth-ldap
Version: 1.0.4-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,

ruby-omniauth-ldap fails to build from source in unstable/amd64:

  [..]

  
┌──┐
  │ Run tests for ruby2.1 from debian/ruby-tests.rake   
  │
  
└──┘
  
  
RUBYLIB=/tmp/buildd/ruby-omniauth-ldap-1.0.4/debian/ruby-omniauth-ldap/usr/lib/ruby/vendor_ruby:.
  rake2.1 -f debian/ruby-tests.rake
  /usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb
  --format documentation
  /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in
  `require': cannot load such file -- rack/test (LoadError)
from
/usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in
`require'
from
/tmp/buildd/ruby-omniauth-ldap-1.0.4/spec/spec_helper.rb:4:in
`'
from
/usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in
`require'
from
/usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in
`require'
from

/tmp/buildd/ruby-omniauth-ldap-1.0.4/spec/omniauth-ldap/adaptor_spec.rb:1:in
`'
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in
`load'
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1327:in
`block in load_spec_files'
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in
`each'
from
/usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1325:in
`load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:103:in
`setup'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:89:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:74:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:42:in
`invoke'
from /usr/bin/rspec:4:in `'
  /usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb
  --format documentation failed
  ERROR: Test "ruby2.1" failed. Exiting.
  dh_auto_install: dh_ruby --install
  /tmp/buildd/ruby-omniauth-ldap-1.0.4/debian/ruby-omniauth-ldap
  returned exit code 1
  debian/rules:18: recipe for target 'binary' failed
  make: *** [binary] Error 1
  dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit
  status 2

  [..]

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


https://reproducible.debian.net/logs/unstable/amd64/ruby-omniauth-ldap_1.0.4-3.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: Mon Oct  5 06:23:52 GMT+12 2015
I: pbuilder-time-stamp: 1444069432
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: debhelper (>= 9~), gem2deb, rake, ruby-net-ldap (>= 0.3.1), 
ruby-omniauth (>= 1.0), ruby-sasl (>= 0.0.3.1), ruby-rspec, ruby-ntlm (>= 0.1.1)
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20294 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 gem2deb; however:
  Package gem2deb is not installed.
 pbuilder-satisfydepends-dummy depends on rake; however:
  Package rake is not installed.
 pbuilder-satisfydepends-dummy depends on ruby-net-ldap (>= 0.3.1); however:
  Package ruby-net-ldap is not installed.
 pbuilder-satisfydepends-dummy depends on ruby-omniauth (>= 1.0); however:
  Package ruby-omniauth is not installed.
 

Bug#778084: marked as done (qt-gstreamer: ftbfs with GCC-5)

[Debian Bug Tracking System]

Your message dated Wed, 07 Oct 2015 14:00:10 -0700
with message-id <3569166.l0XbUffyBe@myrada>
and subject line fixed
has caused the Debian Bug report #778084,
regarding qt-gstreamer: ftbfs with GCC-5
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
778084: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778084
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:qt-gstreamer
Version: 0.10.2-2.1
Severity: normal
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-5

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The
severity of this report may be raised before the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc5-20150205/qt-gstreamer_0.10.2-2.1_unstable_gcc5.log
The last lines of the build log are at the end of this report.

To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t experimental install g++ 

Common build failures are C11 as the default C mode, new warnings
resulting in build failures with -Werror turned on, or new/dropped
symbols in Debian symbols files.  For other C/C++ related build failures
see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html

[...]
   dh_strip -a -O--parallel -O--dbg-package=qtgstreamer-dbg
   dh_makeshlibs -a -O--parallel -O--dbg-package=qtgstreamer-dbg
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libqtglib-2.0-0/DEBIAN/symbols doesn't match 
completely debian/libqtglib-2.0-0.symbols
--- debian/libqtglib-2.0-0.symbols (libqtglib-2.0-0_0.10.2-2.1_amd64)
+++ dpkg-gensymbolsQ91HDi   2015-02-07 09:36:51.866392135 +
@@ -100,24 +100,24 @@
  _ZN5QGlib7Private10wrapObjectEPv@Base 0.10.1
  _ZN5QGlib7Private13wrapInterfaceENS_4TypeEPv@Base 0.10.1
  _ZN5QGlib7Private13wrapParamSpecEPv@Base 0.10.1
- _ZN5QGlib7Private20InvalidTypeExceptionD0Ev@Base 0.10.2
- _ZN5QGlib7Private20InvalidTypeExceptionD1Ev@Base 0.10.2
- _ZN5QGlib7Private20InvalidTypeExceptionD2Ev@Base 0.10.2
- _ZN5QGlib7Private21InvalidValueExceptionD0Ev@Base 0.10.2
- _ZN5QGlib7Private21InvalidValueExceptionD1Ev@Base 0.10.2
- _ZN5QGlib7Private21InvalidValueExceptionD2Ev@Base 0.10.2
+#MISSING: 0.10.2-2.1# _ZN5QGlib7Private20InvalidTypeExceptionD0Ev@Base 0.10.2
+#MISSING: 0.10.2-2.1# _ZN5QGlib7Private20InvalidTypeExceptionD1Ev@Base 0.10.2
+#MISSING: 0.10.2-2.1# _ZN5QGlib7Private20InvalidTypeExceptionD2Ev@Base 0.10.2
+#MISSING: 0.10.2-2.1# _ZN5QGlib7Private21InvalidValueExceptionD0Ev@Base 0.10.2
+#MISSING: 0.10.2-2.1# _ZN5QGlib7Private21InvalidValueExceptionD1Ev@Base 0.10.2
+#MISSING: 0.10.2-2.1# _ZN5QGlib7Private21InvalidValueExceptionD2Ev@Base 0.10.2
  _ZN5QGlib7Private22QObjectDestroyNotifier10disconnectEPvP7QObject@Base 0.10.1
  _ZN5QGlib7Private22QObjectDestroyNotifier7connectEPvP7QObjectPKc@Base 0.10.1
  _ZN5QGlib7Private22QObjectDestroyNotifier8instanceEv@Base 0.10.1
- _ZN5QGlib7Private22QObjectDestroyNotifierD0Ev@Base 0.10.2
- _ZN5QGlib7Private22QObjectDestroyNotifierD1Ev@Base 0.10.2
- _ZN5QGlib7Private22QObjectDestroyNotifierD2Ev@Base 0.10.2
- _ZN5QGlib7Private25UnregisteredTypeExceptionD0Ev@Base 0.10.2
- _ZN5QGlib7Private25UnregisteredTypeExceptionD1Ev@Base 0.10.2
- _ZN5QGlib7Private25UnregisteredTypeExceptionD2Ev@Base 0.10.2
- _ZN5QGlib7Private29TransformationFailedExceptionD0Ev@Base 0.10.2
- _ZN5QGlib7Private29TransformationFailedExceptionD1Ev@Base 0.10.2
- _ZN5QGlib7Private29TransformationFailedExceptionD2Ev@Base 0.10.2
+#MISSING: 0.10.2-2.1# _ZN5QGlib7Private22QObjectDestroyNotifierD0Ev@Base 0.10.2
+#MISSING: 0.10.2-2.1# _ZN5QGlib7Private22QObjectDestroyNotifierD1Ev@Base 0.10.2
+#MISSING: 0.10.2-2.1# _ZN5QGlib7Private22QObjectDestroyNotifierD2Ev@Base 0.10.2
+#MISSING: 0.10.2-2.1# _ZN5QGlib7Private25UnregisteredTypeExceptionD0Ev@Base 
0.10.2
+#MISSING: 0.10.2-2.1# _ZN5QGlib7Private25UnregisteredTypeExceptionD1Ev@Base 
0.10.2
+#MISSING: 0.10.2-2.1# _ZN5QGlib7Private25UnregisteredTypeExceptionD2Ev@Base 
0.10.2
+#MISSING: 0.10.2-2.1# 
_ZN5QGlib7Private29TransformationFailedExceptionD0Ev@Base 0.10.2
+#MISSING: 0.10.2-2.1# 

Bug#799799: marked as done (libtsm: FTBFS: undefined reference to symbol '__pthread_unregister_cancel@@GLIBC_2.3.3')

[Debian Bug Tracking System]

Your message dated Wed, 7 Oct 2015 17:46:30 +0900
with message-id 

and subject line Re: Bug#799799: libtsm: FTBFS: undefined reference to symbol 
'__pthread_unregister_cancel@@GLIBC_2.3.3'
has caused the Debian Bug report #799799,
regarding libtsm: FTBFS: undefined reference to symbol 
'__pthread_unregister_cancel@@GLIBC_2.3.3'
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.)


-- 
799799: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799799
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libtsm
Version: 3-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

libtool: link: gcc -Wall -pipe -fno-common -ffast-math 
-fdiagnostics-show-option -fno-strict-aliasing -fvisibility=hidden 
-ffunction-sections -fdata-sections -g -O2 -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -Wl,--gc-sections -Wl,-z -Wl,relro -Wl,-z 
-Wl,now -Wl,-z -Wl,relro -o test_htable test/test_htable-test_htable.o  
-Wl,--as-needed ./.libs/libshl.a -lcheck_pic -lrt -lm -lsubunit
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/libcheck_pic.a(check_pack.o):
 undefined reference to symbol '__pthread_unregister_cancel@@GLIBC_2.3.3'
//lib/x86_64-linux-gnu/libpthread.so.0: error adding symbols: DSO missing from 
command line
collect2: error: ld returned 1 exit status
Makefile:895: recipe for target 'test_htable' failed

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/libtsm.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Package: check
Version: 0.10.0-3

Hi,

This bug already fixed in 0.10.0-3.
I closed this bug.

Best regards,
  Nobuhiro

2015-10-07 17:43 GMT+09:00 Nobuhiro Iwamatsu :
> reassign 799799 check
> thanks
>
> Hi,
>
> This is bug of check. I reassign this bug to check.
> Please see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=71.
>
> Best regards,
>   Nobuhiro
>
> 2015-09-23 2:25 GMT+09:00 Chris West (Faux) :
>> Source: libtsm
>> Version: 3-1
>> Severity: serious
>> Justification: fails to build from source
>> Tags: sid stretch
>> User: reproducible-bui...@lists.alioth.debian.org
>> Usertags: ftbfs
>> X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org
>>
>> Dear Maintainer,
>>
>> The package fails to build:
>>
>> libtool: link: gcc -Wall -pipe -fno-common -ffast-math 
>> -fdiagnostics-show-option -fno-strict-aliasing -fvisibility=hidden 
>> -ffunction-sections -fdata-sections -g -O2 -g -O2 -fstack-protector-strong 
>> -Wformat -Werror=format-security -Wl,--gc-sections -Wl,-z -Wl,relro -Wl,-z 
>> -Wl,now -Wl,-z -Wl,relro -o test_htable test/test_htable-test_htable.o  
>> -Wl,--as-needed ./.libs/libshl.a -lcheck_pic -lrt -lm -lsubunit
>> /usr/bin/ld: 
>> /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/libcheck_pic.a(check_pack.o):
>>  undefined reference to symbol '__pthread_unregister_cancel@@GLIBC_2.3.3'
>> //lib/x86_64-linux-gnu/libpthread.so.0: error adding symbols: DSO missing 
>> from command line
>> collect2: error: ld returned 1 exit status
>> Makefile:895: recipe for target 'test_htable' failed
>>
>> Full build log:
>> https://reproducible.debian.net/rb-pkg/unstable/amd64/libtsm.html
>>
>> -- System Information:
>> Debian Release: stretch/sid
>> APT prefers unstable
>> APT policy: (500, 'unstable')
>> Architecture: amd64 (x86_64)
>
>
>
> --
> Nobuhiro Iwamatsu
>iwamatsu at {nigauri.org / debian.org}
>GPG ID: 40AD1FA6



-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6--- End Message ---

Processed: Re: Bug#799799: libtsm: FTBFS: undefined reference to symbol '__pthread_unregister_cancel@@GLIBC_2.3.3'

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 799799 check
Bug #799799 [src:libtsm] libtsm: FTBFS: undefined reference to symbol 
'__pthread_unregister_cancel@@GLIBC_2.3.3'
Bug reassigned from package 'src:libtsm' to 'check'.
No longer marked as found in versions libtsm/3-1.
Ignoring request to alter fixed versions of bug #799799 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#799799: libtsm: FTBFS: undefined reference to symbol '__pthread_unregister_cancel@@GLIBC_2.3.3'

[Nobuhiro Iwamatsu]

reassign 799799 check
thanks

Hi,

This is bug of check. I reassign this bug to check.
Please see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=71.

Best regards,
  Nobuhiro

2015-09-23 2:25 GMT+09:00 Chris West (Faux) :
> Source: libtsm
> Version: 3-1
> Severity: serious
> Justification: fails to build from source
> Tags: sid stretch
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org
>
> Dear Maintainer,
>
> The package fails to build:
>
> libtool: link: gcc -Wall -pipe -fno-common -ffast-math 
> -fdiagnostics-show-option -fno-strict-aliasing -fvisibility=hidden 
> -ffunction-sections -fdata-sections -g -O2 -g -O2 -fstack-protector-strong 
> -Wformat -Werror=format-security -Wl,--gc-sections -Wl,-z -Wl,relro -Wl,-z 
> -Wl,now -Wl,-z -Wl,relro -o test_htable test/test_htable-test_htable.o  
> -Wl,--as-needed ./.libs/libshl.a -lcheck_pic -lrt -lm -lsubunit
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/libcheck_pic.a(check_pack.o):
>  undefined reference to symbol '__pthread_unregister_cancel@@GLIBC_2.3.3'
> //lib/x86_64-linux-gnu/libpthread.so.0: error adding symbols: DSO missing 
> from command line
> collect2: error: ld returned 1 exit status
> Makefile:895: recipe for target 'test_htable' failed
>
> Full build log:
> https://reproducible.debian.net/rb-pkg/unstable/amd64/libtsm.html
>
> -- System Information:
> Debian Release: stretch/sid
> APT prefers unstable
> APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)



-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6

Bug#800950: marked as pending

[Mike Gabriel]

tag 800950 pending
thanks

Hello,

Bug #800950 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

http://git.debian.org/?p=pkg-mate/mate-media.git;a=commitdiff;h=c499e37

---
commit c499e37edc961e26b1bc9dedcf1251ea39641bb5
Author: Mike Gabriel 
Date:   Wed Oct 7 10:32:24 2015 +0200

upload to unstable (debian/1.10.0-2)

diff --git a/debian/changelog b/debian/changelog
index 3f0fd9c..e63deb5 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+mate-media (1.10.0-2) unstable; urgency=medium
+
+  * Re-upload to unstable to sort out a recent auto-decrufter code bug.
+(Closes: #800950).
+
+ -- Mike Gabriel   Wed, 07 Oct 2015 10:30:26 +0200
+
 mate-media (1.10.0-1) unstable; urgency=medium
 
   [ Martin Wimpress ]

Processed: Bug#800950 marked as pending

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 800950 pending
Bug #800950 [src:mate-media] mate-media-common has disappeared
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#800819: pyfits: Still FTBFS on mips

[Aurelien Jarno]

control: reassign -1 cfitsio
control: retitle -1 cfitsio: wrong decompression on MIPS
control: affects -1 pyfits

On 2015-10-03 19:02, Scott Kitterman wrote:
> Source: pyfits
> Version: 1:3.3-6
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
> 
> There's still a test failure on mips, despite everthing building on other
> archs now (thanks for fixing those):
> 
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
> self.test(*self.arg)
>   File 
> "/«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/pyfits/tests/test_image.py", 
> line 1328, in test_compression_with_gzip_column
> assert np.all(comp_hdu.data[0] == arr[0])
> AssertionError
> 
> --
> Ran 405 tests in 213.015s
> 
> FAILED (failures=3)
> E: pybuild pybuild:262: test: plugin distutils failed with: exit code=1: cd 
> /«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build; python2.7 -m nose 
> dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 --dir . 
> returned exit code 13
> debian/rules:6: recipe for target 'build-arch' failed
> make: *** [build-arch] Error 25

The problem is actually in cfitsio. pyfits uses cfitsio when it has to
deal with compressed data. I am therefore reassigning the bug there and
I will continue to investigate.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#800950: marked as pending

[Mike Gabriel]

Hi Andreas,

On  Mi 07 Okt 2015 10:41:14 CEST, Andreas Beckmann wrote:


On 2015-10-07 10:33, Mike Gabriel wrote:

+  * Re-upload to unstable to sort out a recent auto-decrufter code bug.
+(Closes: #800950).


Well, that was a actually manual decrufting:


Yes, but only because the auto-decrufting failed prior to that...


=
[Date: Fri, 02 Oct 2015 13:37:38 +] [ftpmaster: Scott Kitterman]
Removed the following packages from unstable:

mate-media | 1.8.0+dfsg1-4 | all
mate-media-common | 1.8.0+dfsg1-4 | all
mate-media-common |   1.10.0-1 | all
Closed bugs: 800557

--- Reason ---
RoQA; obsolete cruft binary
--
=


Andreas


Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb


pgplSZ6w6gxH1.pgp
Description: Digitale PGP-Signatur

Bug#800950: marked as pending

[Andreas Beckmann]

On 2015-10-07 10:33, Mike Gabriel wrote:
> +  * Re-upload to unstable to sort out a recent auto-decrufter code bug.
> +(Closes: #800950).

Well, that was a actually manual decrufting:

=
[Date: Fri, 02 Oct 2015 13:37:38 +] [ftpmaster: Scott Kitterman]
Removed the following packages from unstable:

mate-media | 1.8.0+dfsg1-4 | all
mate-media-common | 1.8.0+dfsg1-4 | all
mate-media-common |   1.10.0-1 | all
Closed bugs: 800557

--- Reason ---
RoQA; obsolete cruft binary
--
=


Andreas

Bug#784041: [Pkg-anonymity-tools] Bug#784041: exceptions.OSError: [Errno 2] No such file or directory

[u]

heya,

Holger Levsen:
>> And before we start fuddling around with this, we should migrate this
>> package to the new pkg-privacy-maintainers list, instead of
>> pkg-anonymity-tools. Aaaand i'd like to review the branch layout a bit,
>> too. Maybe i can do that this week, so we can start working on this
>> crippled package again ;)
> 
> well, there are two issues here: a.) how to move forward with the package, 
> and 
> b.) how to fix what's in jessie now, which just doesnt work at all.

fyi, i updated the branch layout in
ssh://git.debian.org/git/pkg-privacy/packages/torbrowser-launcher.git
please pull from there now.

> And b.) is more urgent IMO, even though the workaround, installing from 
> jessie-backports is trivial. So is 5f833d7 enough to fix 0.1.9-1+deb8u1 as 
> it's in the archive?

i could try that later if nobody else does it before :)

cheers!

Processed: Re: Bug#800819: pyfits: Still FTBFS on mips

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 cfitsio
Bug #800819 [src:pyfits] pyfits: Still FTBFS on mips
Bug reassigned from package 'src:pyfits' to 'cfitsio'.
No longer marked as found in versions pyfits/1:3.3-6.
Ignoring request to alter fixed versions of bug #800819 to the same values 
previously set
> retitle -1 cfitsio: wrong decompression on MIPS
Bug #800819 [cfitsio] pyfits: Still FTBFS on mips
Changed Bug title to 'cfitsio: wrong decompression on MIPS' from 'pyfits: Still 
FTBFS on mips'
> affects -1 pyfits
Bug #800819 [cfitsio] cfitsio: wrong decompression on MIPS
Added indication that 800819 affects pyfits

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

Bug#801265: svxlink: FTBFS: This file requires compiler and library support for the ISO C++ 2011 standard.

[Jakub Wilk]

Source: svxlink
Version: 14.08.1-1
Severity: serious
Justification: fails to build from source

svxlink FTBFS in unstable:
| [  1%] Building CXX object 
async/core/CMakeFiles/asynccore.dir/AsyncApplication.cpp.o
| cd /build/svxlink-vXexqj/svxlink-14.08.1/build/async/core && /usr/bin/c++   
-DINTERNAL_SAMPLE_RATE=16000 -D_REENTRANT -Dasynccore_EXPORTS -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2  -fPIC 
-I/build/svxlink-vXexqj/svxlink-14.08.1/build/include 
-I/build/svxlink-vXexqj/svxlink-14.08.1/build 
-I/usr/lib/i386-linux-gnu/sigc++-2.0/include -I/usr/include/sigc++-2.0-o 
CMakeFiles/asynccore.dir/AsyncApplication.cpp.o -c 
/build/svxlink-vXexqj/svxlink-14.08.1/src/async/core/AsyncApplication.cpp
| In file included from /usr/include/c++/5/type_traits:35:0,
|  from /usr/include/sigc++-2.0/sigc++/visit_each.h:22,
|  from /usr/include/sigc++-2.0/sigc++/functors/slot.h:6,
|  from /usr/include/sigc++-2.0/sigc++/signal_base.h:27,
|  from /usr/include/sigc++-2.0/sigc++/signal.h:8,
|  from /usr/include/sigc++-2.0/sigc++/sigc++.h:86,
|  from 
/build/svxlink-vXexqj/svxlink-14.08.1/src/async/core/AsyncFdWatch.h:45,
|  from 
/build/svxlink-vXexqj/svxlink-14.08.1/src/async/core/AsyncApplication.cpp:60:
| /usr/include/c++/5/bits/c++0x_warning.h:32:2: error: #error This file 
requires compiler and library support for the ISO C++ 2011 standard. This 
support is currently experimental, and must be enabled with the -std=c++11 or 
-std=gnu++11 compiler options.

--
Jakub Wilk

Bug#798924: /usr/lib/x86_64-linux-gnu/jni/libatk-wrapper.so.6.0.0: SIGSEGV on Netbeans startup

[Alexandre Pereira Nunes]

Package: libatk-wrapper-java-jni
Version: 0.33.3-1.1
Followup-For: Bug #798924

I'm refreshing the patch with a potential fix for an aditional crash (a
double free() invocation) which crashed java too. I'm not sure it really
fixed it, but it's harmless if it didn't, anyway.


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

Kernel: Linux 4.2.1 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages libatk-wrapper-java-jni depends on:
ii  libatk-bridge2.0-0   2.18.0-1
ii  libatk-wrapper-java  0.33.3-1.1
ii  libatk1.0-0  2.18.0-1
ii  libatspi2.0-02.18.0-1
ii  libc62.19-22
ii  libcairo-gobject21.14.2-2
ii  libcairo21.14.2-2
ii  libdbus-1-3  1.10.0-3
ii  libgdk-pixbuf2.0-0   2.32.0-1
ii  libglib2.0-0 2.46.0-2
ii  libgtk-3-0   3.16.6-1
ii  libgtk2.0-0  2.24.28-1
ii  libpango-1.0-0   1.38.0-3
ii  libpangocairo-1.0-0  1.38.0-3

libatk-wrapper-java-jni recommends no packages.

libatk-wrapper-java-jni suggests no packages.

-- no debconf information
Index: java-atk-wrapper-0.33.3/jni/src/AtkWrapper.c
===
--- java-atk-wrapper-0.33.3.orig/jni/src/AtkWrapper.c
+++ java-atk-wrapper-0.33.3/jni/src/AtkWrapper.c
@@ -258,6 +258,11 @@ JNICALL Java_org_GNOME_Accessibility_Atk
 jobject jAccContext)
 {
   jobject global_ac = (*jniEnv)->NewGlobalRef(jniEnv, jAccContext);
+  if (!global_ac) {
+   if (jaw_debug)
+ g_warning("%s: global_ac == NULL", __func__);
+   return;
+  }
   CallbackPara *para = alloc_callback_para(global_ac);
   gdk_threads_add_idle(focus_notify_handler, para);
 }
@@ -335,6 +340,11 @@ JNICALL Java_org_GNOME_Accessibility_Atk
 {
 
   jobject global_ac = (*jniEnv)->NewGlobalRef(jniEnv, jAccContext);
+  if (!global_ac) {
+ if (jaw_debug)
+ g_warning("%s: global_ac == NULL", __func__);
+   return;
+  } 
   CallbackPara *para = alloc_callback_para(global_ac);
   para->is_toplevel = (jIsToplevel == JNI_TRUE) ? TRUE : FALSE;
   gdk_threads_add_idle(window_open_handler, para);
@@ -412,6 +422,11 @@ JNICALL Java_org_GNOME_Accessibility_Atk
 jboolean jIsToplevel)
 {
   jobject global_ac = (*jniEnv)->NewGlobalRef(jniEnv, jAccContext);
+  if (!global_ac) {
+ if (jaw_debug)
+ g_warning("%s: global_ac == NULL", __func__);
+   return;
+  }
   CallbackPara *para = alloc_callback_para(global_ac);
   para->is_toplevel = (jIsToplevel == JNI_TRUE) ? TRUE : FALSE;
   gdk_threads_add_idle(window_close_handler, para);
@@ -462,6 +477,11 @@ JNICALL Java_org_GNOME_Accessibility_Atk
jobject jAccContext)
 {
   jobject global_ac = (*jniEnv)->NewGlobalRef(jniEnv, jAccContext);
+  if (!global_ac) {
+ if (jaw_debug)
+ g_warning("%s: global_ac == NULL", __func__);
+   return;
+  }
   CallbackPara *para = alloc_callback_para(global_ac);
   gdk_threads_add_idle(window_minimize_handler, para);
 }
@@ -511,6 +531,11 @@ JNIEXPORT void JNICALL Java_org_GNOME_Ac
   jobject jAccContext)
 {
   jobject global_ac = (*jniEnv)->NewGlobalRef(jniEnv, jAccContext);
+  if (!global_ac) {
+ if (jaw_debug)
+ g_warning("%s: global_ac == NULL", __func__);
+   return;
+  }
   CallbackPara *para = alloc_callback_para(global_ac );
   gdk_threads_add_idle(window_maximize_handler, para);
 }
@@ -561,6 +586,11 @@ JNIEXPORT void JNICALL Java_org_GNOME_Ac
 {
 
   jobject global_ac = (*jniEnv)->NewGlobalRef(jniEnv, jAccContext);
+  if (!global_ac) {
+ if (jaw_debug)
+ g_warning("%s: global_ac == NULL", __func__);
+   return;
+  }
   CallbackPara *para = alloc_callback_para(global_ac);
   gdk_threads_add_idle(window_restore_handler, para);
 }
@@ -609,6 +639,11 @@ JNIEXPORT void JNICALL Java_org_GNOME_Ac
   jobject jAccContext) {
 
   jobject global_ac = (*jniEnv)->NewGlobalRef(jniEnv, jAccContext);
+  if (!global_ac) {
+ if (jaw_debug)
+ g_warning("%s: global_ac == NULL", __func__);
+   return;
+  }
   CallbackPara *para = alloc_callback_para(global_ac);
   gdk_threads_add_idle(window_activate_handler, para);
 }
@@ -659,6 +694,11 @@ JNICALL Java_org_GNOME_Accessibility_Atk
 {
 
   jobject global_ac = (*jniEnv)->NewGlobalRef(jniEnv, jAccContext);
+  if (!global_ac) {
+ if (jaw_debug)
+ g_warning("%s: global_ac == NULL", __func__);
+   return;
+  }
   CallbackPara *para = alloc_callback_para(global_ac);
   

Bug#801089: spice: diff for NMU version 0.12.5-1.3

[Liang Guo]

On Thu, Oct 8, 2015 at 12:18 AM, Salvatore Bonaccorso  wrote:
> tags 801089 + patch pending
> tags 801091 + patch pending
> thanks
>
> Dear maintainer,
>
> I've prepared an NMU for spice (versioned as 0.12.5-1.3) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
>
> Regards,
> Salvatore

Please upload to ftp-master NOW.

btw, would you like co-maintain, or takeover spice ?

Thanks,
-- 
Liang Guo
http://guoliang.me/

Processed: Re: boo: change of type in system_error might break with GCC-5

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #793220 [src:boo] boo: change of type in system_error might break with GCC-5
Severity set to 'serious' from 'important'
> tags -1 sid stretch
Bug #793220 [src:boo] boo: change of type in system_error might break with GCC-5
Ignoring request to alter tags of bug #793220 to the same tags previously set

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

Bug#800432: marked as done (witty: hardcodes dependency on libgraphicsmagick3)

[Debian Bug Tracking System]

Your message dated Wed, 07 Oct 2015 10:01:30 +
with message-id 
and subject line Bug#800432: fixed in witty 3.3.4+dfsg-5
has caused the Debian Bug report #800432,
regarding witty: hardcodes dependency on libgraphicsmagick3
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.)


-- 
800432: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800432
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libwt38
Version: 3.3.4+dfsg-4build1
Severity: serious

Hi,

Your package hardcodes a dependency on libgraphicsmagick3. Since that has been
renamed to libgraphicsmagick-q16-3 due to an ABI break, your package needs to
get fixed for that new pkg name and ABI.

Emilio
--- End Message ---
--- Begin Message ---
Source: witty
Source-Version: 3.3.4+dfsg-5

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

Debian distribution maintenance software
pp.
Pau Garcia i Quiles  (supplier of updated witty package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 29 Sep 2015 22:30:07 +0200
Source: witty
Binary: libwt-common libwt38 libwt-dev libwthttp38 libwthttp-dev libwtfcgi38 
libwtfcgi-dev libwttest8 libwttest-dev libwtext38 libwtext-dev libwtdbo38 
libwtdbo-dev libwtdbosqlite38 libwtdbosqlite-dev libwtdbopostgres38 
libwtdbopostgres-dev libwtdbofirebird38 libwtdbofirebird-dev libwtdbomysql38 
libwtdbomysql-dev libwt-dbg libwt-doc witty-examples witty witty-dbg witty-dev 
witty-doc
Architecture: source all amd64
Version: 3.3.4+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Pau Garcia i Quiles 
Changed-By: Pau Garcia i Quiles 
Description:
 libwt-common - C++ library and application server for web applications [common]
 libwt-dbg  - C++ library and application server for web applications [debug]
 libwt-dev  - C++ library and application server for web applications [developm
 libwt-doc  - C++ library and application server for web applications [doc]
 libwt38- C++ library and application server for web applications [runtime]
 libwtdbo-dev - Wt::Dbo ORM library for Wt [development]
 libwtdbo38 - Wt::Dbo ORM library for Wt [runtime]
 libwtdbofirebird-dev - Firebird backend for Wt::Dbo [development]
 libwtdbofirebird38 - Firebird backend for Wt::Dbo [runtime]
 libwtdbomysql-dev - MySQL/MariaDB backend for Wt::Dbo [development]
 libwtdbomysql38 - MySQL/MariaDB backend for Wt::Dbo [runtime]
 libwtdbopostgres-dev - PostgreSQL backend for Wt::Dbo [development]
 libwtdbopostgres38 - PostgreSQL backend for Wt::Dbo [runtime]
 libwtdbosqlite-dev - sqlite3 backend for Wt::Dbo [development]
 libwtdbosqlite38 - sqlite3 backend for Wt::Dbo [runtime]
 libwtext-dev - additional widgets for Wt, based on ExtJS 2.0.x [development]
 libwtext38 - additional widgets for Wt, based on ExtJS 2.0.x [runtime]
 libwtfcgi-dev - FastCGI connector library for Wt [development]
 libwtfcgi38 - FastCGI connector library for Wt [runtime]
 libwthttp-dev - HTTP(S) connector library for Wt [development]
 libwthttp38 - HTTP(S) connector library for Wt [runtime]
 libwttest-dev - test connector library for Wt [development]
 libwttest8 - test connector library for Wt [runtime]
 witty  - C++ library for webapps [runtime] (transition package)
 witty-dbg  - C++ library for webapps [debug] (transition package)
 witty-dev  - C++ library for webapps [devel] (transition package)
 witty-doc  - C++ library for webapps [doc] (transition package)
 witty-examples - C++ library for webapps [examples]
Closes: 800432
Changes:
 witty (3.3.4+dfsg-5) unstable; urgency=medium
 .
   * The GraphicsMagick packagers changed the binary package name
 (libgraphicsmagick3 => libgraphicsmagick-q16-3) because upstream
 broke ABI. Implement the change. Closes: #800432
Checksums-Sha1:
 f06c27acf4e9db6bee1a60e160ccaab605a9e46e 4188 witty_3.3.4+dfsg-5.dsc
 633c85e83fcd46503417df7823e8bb0e898a8713 38848 witty_3.3.4+dfsg-5.diff.gz
 802caab0111d2a05efef0ffa11ba38a54ef0269d 199768 

Bug#793791: [Pkg-anonymity-tools] Bug#793791: Bug#793791: torbrowser-launcher: Fail to start "TypeError: _getEndpoint() takes exactly 4 arguments (2 given)"

[Tobias Scherer]

On Wed, 7 Oct 2015 02:30:49 +0200 Holger Levsen  wrote:
> Hi,
> 
> On Freitag, 11. September 2015, Stéphane Glondu wrote:
> > I cannot reproduce. Is this bug still on topic?
> > > With any luck Debian will update some more packages and the problem
> > > will just go away :)
> > Maybe it happened...?
> 
> so, can anybody still reproduce in sid? I don't have such a test system…
> 
> 
> cheers,
>   Holger

Hi,

I cannot reproduce it in sid. Here is what I get, everything looks fine.

tester@sid:~$ torbrowser-launcher 

** (torbrowser-launcher:8928): WARNING **: Couldn't register with 
accessibility bus: Did not receive a reply. Possible causes include: the 
remote application did not send a reply, the message bus security policy 
blocked the reply, the reply timeout expired, or the network connection was 
broken.
Tor Browser Launcher
By Micah Lee, licensed under MIT
version 0.2.0
https://github.com/micahflee/torbrowser-launcher
Creating GnuPG homedir /home/tester/.local/share/torbrowser/gnupg_homedir
Updating over Tor
Checking for update
Downloading 
https://www.torproject.org/projects/torbrowser/RecommendedTBBVersions
Checking to see if update is needed
TBB is not installed, attempting to install 5.0.3
Downloading https://www.torproject.org/dist/torbrowser/5.0.3/sha256sums.txt
Downloading 
https://www.torproject.org/dist/torbrowser/5.0.3/sha256sums.txt.asc
Downloading 
https://www.torproject.org/dist/torbrowser/5.0.3/tor-browser-linux64-5.0.3_en-US.tar.xz
Verifying signature
Extracting tor-browser-linux64-5.0.3_en-US.tar.xz
Running /home/tester/.local/share/torbrowser/tbb/x86_64/tor-browser_en-
US/start-tor-browser.desktop
Launching './Browser/start-tor-browser --detach'...
tester@sid:~$ dpkg -l | grep torbrowser-launcher
ii  torbrowser-launcher   0.2.0-2 
amd64helps download, update and run the Tor Browser Bundle

Regards,
Toby

Bug#800727: marked as done (python3-astropy: Incompatible to Python-3.5)

[Debian Bug Tracking System]

Your message dated Wed, 07 Oct 2015 09:20:30 +
with message-id 
and subject line Bug#800727: fixed in python-astropy 1.0.5-1
has caused the Debian Bug report #800727,
regarding python3-astropy: Incompatible to Python-3.5
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
800727: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800727
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-cpl
Version: 0.7-4
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,

python-cpl fails to build from source in unstable/amd64:

  [..]

  running build_ext
  building 'cpl.CPL_recipe' extension
  x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall
  -Wstrict-prototypes -g -O2 -fstack-protector-strong -Wformat
  -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
  -I/usr/include/python3.5m -c cpl/CPL_recipe.c -o
  build/temp.linux-x86_64-3.5/cpl/CPL_recipe.o
  x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall
  -Wstrict-prototypes -g -O2 -fstack-protector-strong -Wformat
  -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
  -I/usr/include/python3.5m -c cpl/CPL_library.c -o
  build/temp.linux-x86_64-3.5/cpl/CPL_library.o
  x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions
  -Wl,-z,relro -Wl,-z,relro -g -O2 -fstack-protector-strong -Wformat
  -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2
  build/temp.linux-x86_64-3.5/cpl/CPL_recipe.o
  build/temp.linux-x86_64-3.5/cpl/CPL_library.o -o
  /tmp/buildd/python-cpl-0.7/cpl/CPL_recipe.cpython-35m-x86_64-linux-gnu.so
  Traceback (most recent call last):
File "test/TestRecipe.py", line 9, in 
  from astropy.io import fits
File "/usr/lib/python3/dist-packages/astropy/__init__.py", line 324,
in 
  _initialize_astropy()
File "/usr/lib/python3/dist-packages/astropy/__init__.py", line 237,
in _initialize_astropy
  from .utils import _compiler
  ImportError: cannot import name '_compiler'
  
  During handling of the above exception, another exception occurred:
  
  Traceback (most recent call last):
File "test/TestRecipe.py", line 11, in 
  import pyfits as fits
  ImportError: No module named 'pyfits'
  debian/rules:14: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 1
  make[1]: Leaving directory '/tmp/buildd/python-cpl-0.7'
  debian/rules:10: recipe for target 'build' failed
  make: *** [build] 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/python-cpl_0.7-4.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: Tue Sep 29 14:04:51 GMT+12 2015
I: pbuilder-time-stamp: 1443578691
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: debhelper (>= 9), dh-python, libcpl-dev, python-all-dev (>= 2.6.6-3~), 
python-astropy, python-numpy, python-pkg-resources, python3-all-dev, 
python3-astropy, python3-numpy, python3-pkg-resources
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20296 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...
Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
dpkg: 

Bug#801060: marked as done (scilab: FTBFS on ppc64el)

[Debian Bug Tracking System]

Your message dated Wed, 07 Oct 2015 09:21:30 +
with message-id 
and subject line Bug#801060: fixed in scilab 5.5.2-1.2
has caused the Debian Bug report #801060,
regarding scilab: FTBFS on ppc64el
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.)


-- 
801060: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801060
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scilab
Version: 5.5.2-1.1
Severity: serious
Control: block 798256 with -1

Your package failed to build on ppc64el

Excerpt from the build log:

checking if jni.h can be included... yes
Looking for JNI libs with ppc64 as machine hardware name
Looking for /usr/lib/jvm/java-7-openjdk-ppc64el/jre/lib/ppc64/libjava.so
Looking for /usr/lib/jvm/java-7-openjdk-ppc64el/jre/lib/amd64/libjava.so
Looking for /usr/lib/jvm/java-7-openjdk-ppc64el/jre/lib/i386/client/libjvm.so
Looking for /usr/lib/jvm/java-7-openjdk-ppc64el/jre/bin/classic/libjvm.so
Looking for /usr/lib/jvm/java-7-openjdk-ppc64el/lib/jvm.lib
Looking for /usr/lib/jvm/java-7-openjdk-ppc64el/jre/lib/mipsel/libjava.so
configure: error: Could not detect the location of the Java
shared library. You will need to update java.m4
to add support for this JVM configuration.
/usr/share/cdbs/1/class/autotools.mk:42: recipe for target
'debian/stamp-autotools' failed

Full build log at
https://buildd.debian.org/status/fetch.php?pkg=scilab=ppc64el=5.5.2-1.1=1444066243

Cheers,
Emilio
--- End Message ---
--- Begin Message ---
Source: scilab
Source-Version: 5.5.2-1.2

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated scilab package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 07 Oct 2015 10:02:09 +0200
Source: scilab
Binary: scilab-cli scilab scilab-data scilab-include scilab-minimal-bin 
scilab-full-bin scilab-minimal-bin-dbg scilab-full-bin-dbg scilab-doc 
scilab-doc-fr scilab-doc-pt-br scilab-doc-ja scilab-test
Architecture: source all amd64
Version: 5.5.2-1.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Matthias Klose 
Description:
 scilab - Scientific software package for numerical computations
 scilab-cli - Scientific software package - Command Line Interpreter
 scilab-data - Scientific software package for numerical computations (data file
 scilab-doc - Scientific software package (english documentations)
 scilab-doc-fr - Scientific software package (french documentation)
 scilab-doc-ja - Scientific software package (Japanese documentation)
 scilab-doc-pt-br - Scientific software package (Brazilian Portuguese 
documentation)
 scilab-full-bin - Scientific software package for numerical computations (all 
binar
 scilab-full-bin-dbg - Scientific software package (scilab debugging symbols)
 scilab-include - Scientific software package for numerical computations 
(include f
 scilab-minimal-bin - Scientific software package for numerical computations 
(minimal b
 scilab-minimal-bin-dbg - Scientific software package (scilab-cli debugging 
symbols)
 scilab-test - Scientific software package for numerical computations (test file
Closes: 791539 801060
Changes:
 scilab (5.5.2-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix build with changed jvm architecure directory on ppc64el.
 Closes: #801060.
   * Fix Aarch64 detection (Martin Michlmayr). Closes: #791539.
Checksums-Sha1:
 a33d5464ec92265256cab960069f6aa8ead10005 3966 scilab_5.5.2-1.2.dsc
 a63f398e18682512b676d7b7efabf1b18bcd4aaf 40080 scilab_5.5.2-1.2.debian.tar.xz
 cbc930e008601867246f937c2d9076e3941932b0 510872 scilab-cli_5.5.2-1.2_all.deb
 1bdb6312b1e25615440b0347abd344c8ba6f64fb 35472772 scilab-data_5.5.2-1.2_all.deb
 fa9dc73a8b7b3da87da9c145d80a291082684640 7252580 
scilab-doc-fr_5.5.2-1.2_all.deb
 604e18d3b7a150e301a7663bc46aba5dbd9470cc 7504648 

Bug#799280: marked as done (Depends on gstreamer 0.10)

[Debian Bug Tracking System]

Your message dated Wed, 07 Oct 2015 10:20:11 +
with message-id 
and subject line Bug#799280: fixed in openjfx 8u60-b27-1
has caused the Debian Bug report #799280,
regarding Depends on gstreamer 0.10
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.)


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

Hi,
openjfx build-depends on gstreamer 0.10, which scheduled
for removal from the archive. Please see
https://lists.debian.org/debian-devel/2015/05/msg00335.html
for details.

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: openjfx
Source-Version: 8u60-b27-1

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated openjfx package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 07 Oct 2015 10:05:29 +0200
Source: openjfx
Binary: openjfx libopenjfx-java libopenjfx-jni libopenjfx-java-doc 
openjfx-source
Architecture: source all amd64
Version: 8u60-b27-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libopenjfx-java - JavaFX/OpenJFX 8 - Rich client application platform for Java 
(Jav
 libopenjfx-java-doc - JavaFX/OpenJFX 8 - Rich client application platform for 
Java (Jav
 libopenjfx-jni - JavaFX/OpenJFX 8 - Rich client application platform for Java 
(nat
 openjfx- JavaFX/OpenJFX 8 - Rich client application platform for Java
 openjfx-source - JavaFX/OpenJFX 8 - Rich client application platform for Java 
(sou
Closes: 795851 799280
Changes:
 openjfx (8u60-b27-1) unstable; urgency=medium
 .
   [ Emmanuel Bourg ]
   * New upstream release
 - Refreshed the patches
 - Build with qt5-qmake instead of qt4-qmake
 - New build dependency on ruby
 - Added a patch to link dynamically against ICU
 - Removed the non-free JavaScript minifier from the upstream tarball
   * Fixed a build failure with Gradle 2.5 (Closes: #795851)
   * Depend on GStreamer 1.0 (Closes: #799280)
   * Enabled hardening for libavplugin.so, libfxplugins.so, libgstreamer-lite.so
 and libjfxmedia.so
 .
   [ Matthias Klose ]
   * Fix installation into the jre architecture directory.
   * Enable verbose (debug) build for slow architectures.
   * Build using the qmake linux-g++ spec.
Checksums-Sha1:
 3547064a29611fa690013cfe3fc38fc13b348084 2665 openjfx_8u60-b27-1.dsc
 7a729a465f5f5d804251220b271a808e82106a0a 39139476 openjfx_8u60-b27.orig.tar.xz
 008e7dfc69df28fa2a45b24fb784a09fd6aba1e6 12216 openjfx_8u60-b27-1.debian.tar.xz
 934510ef0d03eb03478e26c45fad147ef4378e4d 2832400 
libopenjfx-java-doc_8u60-b27-1_all.deb
 7e405c9991bd2bf94b650429e6490113b73004c2 9913064 
libopenjfx-java_8u60-b27-1_all.deb
 6bd3d7662953223dd30c32f650b1e13650ae2d10 8342242 
libopenjfx-jni_8u60-b27-1_amd64.deb
 8c8c291f6bc80e0ff2fd31a48abc79aca0b92a61 5856460 
openjfx-source_8u60-b27-1_all.deb
 011738dcc0dcaf9e4f7094b94ad27c2ef65306d6 34022 openjfx_8u60-b27-1_amd64.deb
Checksums-Sha256:
 53b9c33827d9111a593a25c60eabdc0b2d74ab320259b6e807254eee80570015 2665 
openjfx_8u60-b27-1.dsc
 a865d3716801a0b7f29990018ae4f6ffa3ce261dc21bf8376418f5e283f92753 39139476 
openjfx_8u60-b27.orig.tar.xz
 bab004ded461c51a4c771874783dde05506c7ceee9027606172bbeab5f837741 12216 
openjfx_8u60-b27-1.debian.tar.xz
 f156e3323068ca7f6424ccd9700d03f1a9b3028c293103afef1032d04cd201b4 2832400 
libopenjfx-java-doc_8u60-b27-1_all.deb
 6331d89456a2fbfb31b86c9adb3eed8da17a7f92f4e225b9a6756178d4563b86 9913064 
libopenjfx-java_8u60-b27-1_all.deb
 9d0bc389877e8e3815d4a9a4204f8a844a81eb3a3b53e5e23d2bda8c59577f5d 8342242 
libopenjfx-jni_8u60-b27-1_amd64.deb
 1666f45484e5b3a1789101a8862e66e840961c4199e03b84370952078cc1de3c 5856460 
openjfx-source_8u60-b27-1_all.deb
 

Bug#800819: marked as done (cfitsio: wrong decompression on MIPS)

[Debian Bug Tracking System]

Your message dated Wed, 07 Oct 2015 11:18:48 +
with message-id 
and subject line Bug#800819: fixed in cfitsio 3.370-4
has caused the Debian Bug report #800819,
regarding cfitsio: wrong decompression on MIPS
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.)


-- 
800819: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800819
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyfits
Version: 1:3.3-6
Severity: serious
Justification: fails to build from source (but built successfully in the past)

There's still a test failure on mips, despite everthing building on other
archs now (thanks for fixing those):

Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File 
"/«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build/pyfits/tests/test_image.py", line 
1328, in test_compression_with_gzip_column
assert np.all(comp_hdu.data[0] == arr[0])
AssertionError

--
Ran 405 tests in 213.015s

FAILED (failures=3)
E: pybuild pybuild:262: test: plugin distutils failed with: exit code=1: cd 
/«PKGBUILDDIR»/.pybuild/pythonX.Y_2.7/build; python2.7 -m nose 
dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 --dir . 
returned exit code 13
debian/rules:6: recipe for target 'build-arch' failed
make: *** [build-arch] Error 25

This is blocking progress on the python3.5 transition, so I would appreciate
it if you could make it a priority to address.

Scott K
--- End Message ---
--- Begin Message ---
Source: cfitsio
Source-Version: 3.370-4

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

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated cfitsio 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: Wed, 07 Oct 2015 11:24:22 +0200
Source: cfitsio
Binary: libcfitsio2 libcfitsio2-dbg libcfitsio-dev libcfitsio-bin 
libcfitsio-doc libcfitsio3-dev
Architecture: source
Version: 3.370-4
Distribution: unstable
Urgency: medium
Maintainer: Aurelien Jarno 
Changed-By: Aurelien Jarno 
Description:
 libcfitsio-bin - CFITSIO based utilities
 libcfitsio-dev - library for I/O with FITS format data files (development 
files)
 libcfitsio-doc - documentation for CFITSIO
 libcfitsio2 - shared library for I/O with FITS format data files
 libcfitsio2-dbg - library for I/O with FITS format data files (debugging 
symbols)
 libcfitsio3-dev - Transitional package for libcfitsio-dev
Closes: 800819
Changes:
 cfitsio (3.370-4) unstable; urgency=medium
 .
   * Add patches/09-memcpy-overlap.diff to use memmove instead of memcpy
 where memory area might overlaps (closes: #800819).
Checksums-Sha1:
 b61ef6a0bb6bf20b2db16fda408d709fc76eab67 2111 cfitsio_3.370-4.dsc
 645f2dfecf8a1406208ee772ca7c900b431d0142 18432 cfitsio_3.370-4.debian.tar.xz
Checksums-Sha256:
 c5300d5e34edaae2985147711403e607d759dd86c9cc1ec1a3d3575f5a7bac3e 2111 
cfitsio_3.370-4.dsc
 b9f6d898dd1c1299acc25386aa796cbd05d53146c426528d35e8e29a9e35acbe 18432 
cfitsio_3.370-4.debian.tar.xz
Files:
 5a6b9e7f6b343860f4c5084dc48e2631 2111 devel optional cfitsio_3.370-4.dsc
 100fc568e4daaeab93140ae726e94a8a 18432 devel optional 
cfitsio_3.370-4.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJWFP5QAAoJELqceAYd3YybO0cP/iQae5P83e10bFIqvkhhfYyP
yPx2fiqQh0MvOTsi/KiPtXI5pfJB6ms33TDqOU6zR8t2J2SekwA/mxAX9yOrXmeK
2rlDAVWhkLVaYZzlC6fYiDy+StbSV+HQgrGlUtsYKJxS79UQuFHBlbolQYRiWABA
K673CjLcQRjwypN85qeAyPxiuyjdsuD03usQ1zgxS/zY297l9U6IFg08M1yytPLW
lfGF+zC4BkIss658cgXL1ju+beMdTi3xdMdA3MnMZGE3H+koRs7zgyr3ospnvYvI
MdmaHq7F5CYvDj262U2ANrhoo/ZbERJw6aEQVceaJpr2LIfUBAybbyp2C0dw5l+F
CQQMd0MvEwKgbv0pEbKP2I+Wd+DPLoOsAjr7BrMJA/KjJCvelD6qCDNyNAZBgmGH
SUS82bVVBN6oFfpdkMEgL4ASVN2h8xIvVGqLC6MwfkWsAtpAOohKCGs1yZJA16Gg
VO0FiAbt6unIPJQnwaq/DyifiUtrDCggk0QISOQEdVaQ8QD4XqqLftEDC1i4Uws6

Bug#801106: sddm-greeter fails to start

[Andy G Wood]

Many thanks Didi,

I can confirm that workaround "adduser sddm video" fixed the problem.

Bug#795178: marked as done (ceph FTBFS with boost1.58)

[Debian Bug Tracking System]

Your message dated Wed, 07 Oct 2015 11:49:26 +
with message-id 
and subject line Bug#795178: fixed in ceph 0.80.10-1
has caused the Debian Bug report #795178,
regarding ceph FTBFS with boost1.58
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.)


-- 
795178: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ceph
Version: 0.94.2
Severity: important

Dear Maintainer,

ceph currently FTBFS when compiling with boost 1.58. 

Upstream bug report and patch available at
http://tracker.ceph.com/issues/11576

Build log
=
libtool: compile: g++ -DHAVE_CONFIG_H -I. -D__CEPH__ -D_FILE_OFFSET_BITS=64 
-D_REENTRANT -D_THREAD_SAFE -D__STDC_FORMAT_MACROS -D_GNU_SOURCE 
-DCEPH_LIBDIR=\"/usr/lib/x86_64-linux-gnu\" 
-DCEPH_PKGLIBDIR=\"/usr/lib/x86_64-linux-gnu/ceph\" -DGTEST_HAS_TR1_TUPLE=0 
-D_FORTIFY_SOURCE=2 -I/usr/include/nss -I/usr/include/nspr -Wall -Wtype-limits 
-Wignored-qualifiers -Winit-self -Wpointer-arith -Werror=format-security 
-fno-strict-aliasing -fsigned-char -rdynamic -ftemplate-depth-1024 
-Wnon-virtual-dtor -Wno-invalid-offsetof -fno-builtin-malloc 
-fno-builtin-calloc -fno-builtin-realloc -fno-builtin-free 
-Wstrict-null-sentinel -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -c mon/MDSMonitor.cc -fPIC -DPIC -o 
mon/.libs/MDSMonitor.o
In file included from /usr/include/boost/optional/optional.hpp:28:0,
 from /usr/include/boost/optional/optional_io.hpp:19,
 from ./include/encoding.h:289,
 from ./include/uuid.h:8,
 from ./include/types.h:21,
 from mon/OSDMonitor.h:28,
 from mon/OSDMonitor.cc:21:
/usr/include/boost/variant/get.hpp: In instantiation of 'typename 
boost::add_reference::type boost::strict_get(const boost::variant&) [with U = int; T0 = std::__cxx11::basic_string; T1 = bool; T2 
= long int; T3 = double; T4 = std::vector; 
T5 = boost::detail::variant::void_; T6 = boost::detail::variant::void_; T7 = 
boost::detail::variant::void_; T8 = boost::detail::variant::void_; T9 = 
boost::detail::variant::void_; T10 = boost::detail::variant::void_; T11 = 
boost::detail::variant::void_; T12 = boost::detail::variant::void_; T13 = 
boost::detail::variant::void_; T14 = boost::detail::variant::void_; T15 = 
boost::detail::variant::void_; T16 = boost::detail::variant::void_; T17 = 
boost::detail::variant::void_; T18 = boost::detail::variant::void_; T19 = 
boost::detail::variant::void_; typename boost::add_reference::type = 
const int&]':
/usr/include/boost/variant/get.hpp:299:25: required from 'typename 
boost::add_reference::type boost::get(const boost::variant&) 
[with U = int; T0 = std::__cxx11::basic_string; T1 = bool; T2 = long int; 
T3 = double; T4 = std::vector; T5 = 
boost::detail::variant::void_; T6 = boost::detail::variant::void_; T7 = 
boost::detail::variant::void_; T8 = boost::detail::variant::void_; T9 = 
boost::detail::variant::void_; T10 = boost::detail::variant::void_; T11 = 
boost::detail::variant::void_; T12 = boost::detail::variant::void_; T13 = 
boost::detail::variant::void_; T14 = boost::detail::variant::void_; T15 = 
boost::detail::variant::void_; T16 = boost::detail::variant::void_; T17 = 
boost::detail::variant::void_; T18 = boost::detail::variant::void_; T19 = 
boost::detail::variant::void_; typename boost::add_reference::type = 
const int&]'
../common/cmdparse.h:47:26: required from 'bool cmd_getval(CephContext*, const 
cmdmap_t&, std::__cxx11::string, T&) [with T = int; cmdmap_t = 
std::map > >; std::__cxx11::string = 
std::__cxx11::basic_string]'
mon/OSDMonitor.cc:3002:54: required from here
/usr/include/boost/variant/get.hpp:195:5: error: invalid application of 
'sizeof' to incomplete type 'boost::STATIC_ASSERTION_FAILURE'
 BOOST_STATIC_ASSERT_MSG(
 ^
make[5]: *** [mon/OSDMonitor.lo] Error 1
make[5]: *** Waiting for unfinished jobs
Makefile:16163: recipe for target 'mon/OSDMonitor.lo' failed

-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 

Bug#784041: [Pkg-anonymity-tools] Bug#784041: Bug#784041: exceptions.OSError: [Errno 2] No such file or directory

[intrigeri]

Holger Levsen wrote (07 Oct 2015 00:28:41 GMT) :
> On Dienstag, 6. Oktober 2015, u wrote:
>> Maybe Holger can explain again what prevented
>> us from putting 0.2.0 into stable at the time?

> the freeze... the changes were to big…

Probably useless nitpicking: the freeze was over when
torbrowser-launcher 0.2.0 was released upstream, simply because...
Jessie had been released since 2+ weeks :)

>> And before we start fuddling around with this, we should migrate this
>> package to the new pkg-privacy-maintainers list, instead of
>> pkg-anonymity-tools. Aaaand i'd like to review the branch layout a bit,
>> too. Maybe i can do that this week, so we can start working on this
>> crippled package again ;)

> well, there are two issues here: a.) how to move forward with the package, 
> and 
> b.) how to fix what's in jessie now, which just doesnt work at all.

> And b.) is more urgent IMO, even though the workaround, installing from 
> jessie-backports is trivial. So is 5f833d7 enough to fix 0.1.9-1+deb8u1 as 
> it's in the archive?

Agreed: if you have time to put into torbrowser-launcher soon, please
start with (b) -- migrating the package to pkg-privacy is a bit less
urgent than "has been totally broken in stable for months" :)

Cheers,
-- 
intrigeri

Bug#800574: Final analysis for Broadwell

[Henrique de Moraes Holschuh]

Well, I've finally finished analysing things for Broadwell.

The amd64 (x86-64) glibc lock elision code keys on the RTM CPUID bit
because it is actually using RTM (and not HLE) to implement lock
elision.  I failed to keep this in mind when worrying about permanently
blacklisting Broadwell processors from glibc lock elision in unstable.

Errata BDM53/BDW51/BDD51/BDE42 "Intel TSX Instructions not avalilable"
_should_ mean that trying to use any of the TSX-NI opcodes (i.e. RTM) in
Broadwell would always result in an illegal opcode exception (SIGILL). 
The specificaton updates also explicitly say in the descriptions of
these errata that the RTM bit in CPUID is not set.

Were those errata present on every microcode revision/core versions of
those processors, it would make them "safe" as far as our (patched)
glibc lock elision is concerned.  We are not that lucky.

Seaching the network for cpuinfo reports resulted in a /proc/cpuinfo
dump of signature 0x306d4, microcode rev 0x11 (Core i5-5300U), and rev
0x18 (Core M-5Y71), where both RTM and HLE are reported as enabled.

Another /proc/cpuinfo dump of signature 0x306d4, with microcode rev 0x18
(Core i5-5300U and also Core M-5Y10c) and rev 0x1f (Core i5-5287U),
shows both HLE and RTM already disabled.

The fact that revision 0x18 had a different CPUID response for (Core
i5-5300U, Core M-5Y10c), and Core M-5Y71 was a surprise.
Perhaps it also has a dependency on the firmware doing a (hopefully
boot-locked) wrmsr to disable TSX.

Anyway, regardless of the reason, one cannot count on the RTM and HLE
bits being disabled in CPUID(7) on every Broadwell processor and
microcode revision out there.

OTOH, it does means we can, and should, blacklist signature 0x306d4 (and
earlier) permanently, because RTM is extremely unlikely to be
fixed/fixable on these processors. Either it is disabled as it should be
per the errata documentation, or enabled and very dangerous (resulting
in either SIGILL or Haswell-style risk of unpredictable system
behavior).  Since signature 0x40671 also has the same "TSX unavailable"
type of errata (BDD51, BDE42), I guess we can assume the same applies to
Broadwell-H and Broadwell-DE, and blacklist lock elision there
permanently as well.

I am still collecting data for Skylake-S, but it boils down to whether
up-to-date Skylake-S microcode (revisions 0x34 and higher) fixes, or
disable TSX.  We know that microcode update does stop glibc lock elision
crashing with SIGSEGV, though.


Meanwhile, a suggestion by Samuel Thibault to try to use hwcap did
provide for a possible long-term plan to fine-tune the lock-elision
blacklist (and anything else of that sort).

We would have to (finally) extend x86-64 hwcap to cpuid(1) fully, and
also at least cpuid(7), which is anything but trivial and a lot of work.
 This is _not_ worth the trouble if it is done just for lock elision
blacklisting purposes.

However, it would be useful for link-time optimization in libraries
(e.g. avx2 flavours of something that really benefits from it, etc), so
it is likely worth pursuing... but only if we get buy-in from upstream.

Once it is there for far better purposes than blacklisting, there is no
reason not to do the trivial work to have the kernel blacklist whatever
capabilities should be avoided, and switch glibc to use the hwcap
extension instead of doing cpuid directly wherever available, thus
making it usable _also_ for blacklisting things.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique de Moraes Holschuh 

Bug#797744: marked as done (gromacs: shared library in a package that is not renamed with its SONAME)

[Debian Bug Tracking System]

Your message dated Wed, 07 Oct 2015 10:00:30 +
with message-id 
and subject line Bug#797744: fixed in gromacs 5.1-1
has caused the Debian Bug report #797744,
regarding gromacs: shared library in a package that is not renamed with its 
SONAME
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.)


-- 
797744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797744
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gromacs
Version: 5.0.6-1
Severity: serious
Justification: Policy 8.1

The gromacs binary package contains a public shared library
(libgromacs.so.0), and votca-csg depends on it.

Policy §8.1 says:

> The run-time shared library must be placed in a package whose name
> changes whenever the SONAME of the shared library changes.

In this case, the shared library package should be libgromacs0,
and gromacs should depend on it.

Not doing this makes SONAME transitions, C++ ABI transitions, etc.
more painful for no good reason.

S
--- End Message ---
--- Begin Message ---
Source: gromacs
Source-Version: 5.1-1

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

Debian distribution maintenance software
pp.
Nicholas Breen  (supplier of updated gromacs package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 01 Oct 2015 17:38:08 -0700
Source: gromacs
Binary: gromacs gromacs-data libgromacs1 libgromacs-dev gromacs-dev 
gromacs-mpich gromacs-openmpi
Architecture: source all amd64
Version: 5.1-1
Distribution: unstable
Urgency: low
Maintainer: Debichem Team 
Changed-By: Nicholas Breen 
Description:
 gromacs- Molecular dynamics simulator, with building and analysis tools
 gromacs-data - GROMACS molecular dynamics sim, data and documentation
 gromacs-dev - Dummy package for libgromacs-dev
 gromacs-mpich - Molecular dynamics sim, binaries for MPICH parallelization
 gromacs-openmpi - Molecular dynamics sim, binaries for OpenMPI parallelization
 libgromacs-dev - GROMACS molecular dynamics sim, development kit
 libgromacs1 - GROMACS molecular dynamics sim, shared libraries
Closes: 715934 797744
Changes:
 gromacs (5.1-1) unstable; urgency=low
 .
   * New upstream release.  This release completes the transition to "gmx"
 as the sole binary to replace all the former g_* commands, and the
 compatibility symlinks have been removed.  Standalone mdrun_mpi
 programs in gromacs-mpich and gromacs-openmpi are unaffected.
 - gmx anadock no longer crashes on invalid input.  (Closes: #715934)
   * Some package reshuffling: gromacs-dev becomes libgromacs-dev, and the
 shared library gets split out into libgromacs1.  (Closes: #797744)
 Upload priority set to "low" due to the unusually extensive restructure.
   * Remove gromacs-dev.preinst, only needed for upgrades from well before
 the version in squeeze.
   * Lots more documentation!  PDF manual is built once again, and doxygen
 output for developer use is included.  Several Build-Depends-Indep
 entries added to support this.
 - patches/manpage-hyphenation.patch removed, no longer needed.
 - mdrun_mpi.{mpich,openmpi}.1 updated.
   * debian/control: apply wrap-and-sort.
Checksums-Sha1:
 ddce3c0233fbce05eda3e5ab344048bd07c65ce8 2823 gromacs_5.1-1.dsc
 1630297e853ff9be0767cf348f86effafb1dc1a9 26546875 gromacs_5.1.orig.tar.gz
 070410f0a5053bde4e206e50f938f95032b27f0a 31732 gromacs_5.1-1.debian.tar.xz
 a50bf2adb46a397d22b606b42e5e1a9be00c153f 22869008 gromacs-data_5.1-1_all.deb
Checksums-Sha256:
 29b604bb9c098e8f66080a2e59054e8096fd44beab1c30ff851b68fa678969b0 2823 
gromacs_5.1-1.dsc
 996b6061971e11942252de36b67b5cf35f02ce14adf80db8a3f079fc686c2743 26546875 
gromacs_5.1.orig.tar.gz
 063def5add5dad1b6ede94b7169aa1945c2c4fc1a1db0189c4f38498567c493e 31732 
gromacs_5.1-1.debian.tar.xz
 62fe280ce1417c65b3eb03af4b794bc6d6663f25c276dcef2dd3b0642295fc01 22869008 
gromacs-data_5.1-1_all.deb
Files:
 0dfa9b3520cd7cfeb00e27ea9bd975ef 2823 

Bug#801194: marked as done (The template "templates/navigation/logo.phtml" not found.)

[Debian Bug Tracking System]

Your message dated Wed, 07 Oct 2015 12:35:08 +
with message-id 
and subject line Bug#801194: fixed in phpmyadmin 4:4.5.0.2-2
has caused the Debian Bug report #801194,
regarding The template "templates/navigation/logo.phtml" 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.)


-- 
801194: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801194
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: phpmyadmin
Version: 4:4.5.0.2-1
Severity: grave

Since the upgrade, phpmyadmin is completely broken here. After logging
in, I get

( ! ) Fatal error: Uncaught exception 'LogicException' with message 'The
template "templates/navigation/logo.phtml" not found.' in
/usr/share/phpmyadmin/libraries/Template.class.php on line 95
( ! ) LogicException: The template "templates/navigation/logo.phtml" not
found. in /usr/share/phpmyadmin/libraries/Template.class.php on line 95


The apache error log contains:

[Wed Oct 07 14:11:03.002907 2015] [:error] [pid 11261] [client 127.0.0.1:41124] 
PHP Fatal error:  Uncaught exception 'LogicException' with message 'The 
template "templates/list/item.phtml" not found.' in 
/usr/share/phpmyadmin/libraries/Template.class.php:95\nStack trace:\n#0 
/usr/share/phpmyadmin/index.php(716): PMA\\Template->render(Array)\n#1 
/usr/share/phpmyadmin/index.php(199): PMA_printListItem('http://localhost/phpmyadmin/
[Wed Oct 07 14:11:03.004115 2015] [:error] [pid 11261] [client 127.0.0.1:41124] 
PHP Fatal error:  Uncaught exception 'LogicException' with message 'The 
template "templates/navigation/logo.phtml" not found.' in 
/usr/share/phpmyadmin/libraries/Template.class.php:95\nStack trace:\n#0 
/usr/share/phpmyadmin/libraries/navigation/NavigationHeader.class.php(142): 
PMA\\Template->render(Array)\n#1 
/usr/share/phpmyadmin/libraries/navigation/NavigationHeader.class.php(55): 
PMA_NavigationHeader->_logo()\n#2 
/usr/share/phpmyadmin/libraries/navigation/Navigation.class.php(35): 
PMA_NavigationHeader->getDisplay()\n#3 
/usr/share/phpmyadmin/libraries/Header.class.php(433): 
PMA_Navigation->getDisplay()\n#4 
/usr/share/phpmyadmin/libraries/Response.class.php(263): 
PMA_Header->getDisplay()\n#5 
/usr/share/phpmyadmin/libraries/Response.class.php(276): 
PMA_Response->_getDisplay()\n#6 
/usr/share/phpmyadmin/libraries/Response.class.php(397): 
PMA_Response->_htmlResponse()\n#7 [internal function]: PMA_Response::r
 esponse()\n#8 {main}\n  thrown in 
/usr/share/phpmyadmin/libraries/Template.class.php on line 95, referer: 
http://localhost/phpmyadmin/



root@pluto:/usr/share/phpmyadmin# grep phtml -R
libraries/Template.class.php:$template = static::BASE_PATH . 
$this->name . '.phtml';
root@pluto:/usr/share/phpmyadmin# dpkg -L phpmyadmin | grep phtml || echo "not 
found"
not found



-- 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.2.0-1-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)

Versions of packages phpmyadmin depends on:
ii  dbconfig-common1.8.54
ii  debconf [debconf-2.0]  1.5.57
ii  libapache2-mod-php55.6.14+dfsg-1
ii  libjs-sphinxdoc1.3.1-6
ii  perl   5.20.2-6
ii  php-gettext1.0.11-1
ii  php-seclib 1.0.0-2
ii  php5-json  1.3.7-1
ii  php5-mcrypt5.6.14+dfsg-1
ii  php5-mysql 5.6.14+dfsg-1
ii  ucf3.0030

Versions of packages phpmyadmin recommends:
ii  apache2 [httpd]  2.4.16-3
ii  mysql-client 5.6.25-4
ii  mysql-client-5.6 [virtual-mysql-client]  5.6.25-4
ii  php-tcpdf6.0.093+dfsg-1
ii  php5-gd  5.6.14+dfsg-1

Versions of packages phpmyadmin suggests:
ii  google-chrome-stable [www-browser]   45.0.2454.101-1
ii  iceweasel [www-browser]  38.3.0esr-1
ii  konqueror [www-browser]  4:15.08.1-1
ii  lynx-cur [www-browser]   2.8.9dev6-4
ii  mysql-server 5.6.25-4
ii  mysql-server-5.6 [virtual-mysql-server]  5.6.25-4
ii  w3m [www-browser]0.5.3-24

-- debconf information excluded
--- End Message ---
--- Begin Message ---
Source: phpmyadmin
Source-Version: 4:4.5.0.2-2

We believe that the bug you reported is fixed in the latest version of

Bug#801190: marked as done (valac 0.30.0-1 fails to install (error: no alternatives for valac))

[Debian Bug Tracking System]

Your message dated Wed, 07 Oct 2015 13:55:08 +
with message-id 
and subject line Bug#801190: fixed in vala 0.30.0-2
has caused the Debian Bug report #801190,
regarding valac 0.30.0-1 fails to install (error: no alternatives for valac)
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.)


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

Hi,

Preparing to unpack .../valac_0.30.0-1_amd64.deb ...
update-alternatives: error: no alternatives for valac
dpkg: error processing archive /var/cache/apt/archives/valac_0.30.0-1_amd64.deb 
(--install):
 subprocess new pre-installation script returned error exit status 2



Thanks,

Fred


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

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

Versions of packages valac depends on:
pn  valac-0.28  

valac recommends no packages.

valac suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: vala
Source-Version: 0.30.0-2

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

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated vala package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 07 Oct 2015 15:24:28 +0200
Source: vala
Binary: valac valac-0.30-vapi vala-0.30-doc libvala-0.30-0 libvala-0.30-dev 
valac-dbg libvala-0.30-0-dbg
Architecture: source
Version: 0.30.0-2
Distribution: unstable
Urgency: medium
Maintainer: Maintainers of Vala packages 

Changed-By: Michael Biebl 
Description:
 libvala-0.30-0 - C# like language for the GObject system - library
 libvala-0.30-0-dbg - C# like language for the GObject system - library symbols
 libvala-0.30-dev - C# like language for the GObject system - development 
headers
 vala-0.30-doc - C# like language for the GObject system - documentation
 valac  - C# like language for the GObject system
 valac-0.30-vapi - C# like language for the GObject system - vapi files
 valac-dbg  - C# like language for the GObject system - debug symbols
Closes: 801190
Changes:
 vala (0.30.0-2) unstable; urgency=medium
 .
   * Don't fail in preinst if the valac alternatives have already been removed.
 Also do it only once, not on every upgrade. (Closes: #801190)
Checksums-Sha1:
 f8c8d68cb88d846789924e25045ef40e633cd7e8 2611 vala_0.30.0-2.dsc
 006ea0115c97e2e585174447f4d06ba7d9afdc01 23900 vala_0.30.0-2.debian.tar.xz
Checksums-Sha256:
 3978af92b6132a3433e4dd72d6eee5f3edfefd3de425dcca6c371fa2113fe906 2611 
vala_0.30.0-2.dsc
 47a14555702c518461c1f9f267d4ca7bb0fb2fc9f1f404a0ca0cac34d7bfb704 23900 
vala_0.30.0-2.debian.tar.xz
Files:
 c759857597d8fcabf29ef6f2d61d52c9 2611 devel optional vala_0.30.0-2.dsc
 c2f7873901261ea9a34d4741d8d49d8a 23900 devel optional 
vala_0.30.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWFR1JAAoJEGrh3w1gjyLcxVEP/3dQ6h3A/7N3T02cUL17rp+c
JsXRK+7lKi6mXb/uClJHX4qGU3mSIzdD6wwRUye5+jg1RW/zYaFQyb3nXE4cGLJ5
vRPSVFYA+L+bDUYApzB/Ns02idJCnwZ3NMlpFKmzhxL8aDdWOWOKFk5Abnq8XfPf
PCrdCR7Vu9k//iO97n0h/ZRhDjyI3fYMX5gtB/LDTbDpnqd/GsxXaJQquUr0b92w
k9PTGx0GtajwkR6cfuV1SbVYYJXR8IOwGQ/Z4GwyaYew6soDoH61ItJrFgcIvRfl
WUCZniGRLck3cfzq7R5/64/laTiC5Ibe9oxIfbnzXTOqGCx7iiDtM+kbG4J+6gOX
6Ebn7hj8d80o7wKySy3PMArXsvw8s82eZZTbv5M4ezJjggKbMGnEH0kdosL2QUqo
+yJuoBnpStZMYpwU/A6cgci0qjlf6EDWH38LaRO8DsZKNtH0bl9XnpjedQBhZw+l
vG3ZhFtdbaOkcxWEqfOSx3MWancJ/UMeAJibuBXKErS3S/feeojT2nCiMIDOAzde
E91khLhjVJkcctDeeHQ+hHuNiWJzFzvsmTJRydDYN4CDm3fRCedG1nLOj3EINwBS
V8my525LUme+OZfW7idUsNv1hsEbHjYCA5RleLpHXIgPB8LjuHoCaWXxTHDldO/8
KsBzXMlfkXFV3qyaqUTo
=lHKi

Bug#784041: [Pkg-anonymity-tools] Bug#784041: Bug#784041: Bug#784041: exceptions.OSError: [Errno 2] No such file or directory

[Tobias Scherer]

Am Mittwoch, 7. Oktober 2015, 13:47:55 schrieb intrigeri:
> 
> Agreed: if you have time to put into torbrowser-launcher soon, please
> start with (b) -- migrating the package to pkg-privacy is a bit less
> urgent than "has been totally broken in stable for months" :)
> 
> Cheers,

Hi,

when I put the attached series file into debian/patches the already existing 
three patches are applied. The resulting package is useable and can download 
and open the torbrowser.

me@machine$: ~/src/torbrowser-launcher-0.1.9 $ head -n1 debian/patches/*patch
==> debian/patches/0001-Update-location-of-start-tor-browser-for-TBB-4.5-
and.patch <==
>From 3d9f4edc206ade74ff1b4194297e20025e51b793 Mon Sep 17 00:00:00 2001

==> debian/patches/0002-execute-.-start-tor-browser.desktop-instead-of-.-
Bro.patch <==
>From 5f833d73290bd3623bf22caffaed599381d454d9 Mon Sep 17 00:00:00 2001

==> debian/patches/0003-Stop-letting-Tor-Browser-act-as-a-default-
browser.patch <==
>From f219f35225fd71dfcfdd5c93c7470cf705778e5b Mon Sep 17 00:00:00 2001

> > And b.) is more urgent IMO, even though the workaround, installing from
> > jessie-backports is trivial. So is 5f833d7 enough to fix 0.1.9-1+deb8u1 as
> > it's in the archive?

The second patch that applies 5f833d7 is not usable without modifikation or 
applying the first patch. 
But it should be possible to have a patch to only apply 5f833d7.

I do not know wether the changes of all these three patches are ok or not for 
applying on a package already in jessie, but they were introduced with the 
commit that has the version number of the package in jessie today, obviuosly 
they never got applied:

--8<--8<--
torbrowser-launcher (0.1.9-1+deb8u1) jessie; urgency=high

  * Apply 3d9f4ed and 5f833d7 from 0.2.0 upstream release to deal with changed
pathes in the 4.5 torbrowser release. (Closes: #784041)
  * 3d9f4ed also removes the accept links feature (as it has stopped worked
with 4.5.)
  * Apply f219f35 from 0.2.0 to stop acting as default browser, because a
default browser should be captable of accepting links.
-->8-->8--

So imho the easiest way to fix this problem would be to add the series file 
and rebuild if it is ok for an actual jessie package to have such changes.

The package would be available in jessie-updates until the next point release 
if I undestand this right?

Regards,
Toby0001-Update-location-of-start-tor-browser-for-TBB-4.5-and.patch
0002-execute-.-start-tor-browser.desktop-instead-of-.-Bro.patch
0003-Stop-letting-Tor-Browser-act-as-a-default-browser.patch

Processed: forcibly merging 760538 800756

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 760538 800756
Bug #760538 [src:ceph] ceph maintainer address redirects to a closed list
Bug #800756 [src:ceph] Your message to Ceph-maintainers awaits moderator 
approval
Severity set to 'important' from 'serious'
Marked as found in versions ceph/0.80.5-1.
Merged 760538 800756
> thanks
Stopping processing here.

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

Bug#801194: The template "templates/navigation/logo.phtml" not found.

[Michael Biebl]

Package: phpmyadmin
Version: 4:4.5.0.2-1
Severity: grave

Since the upgrade, phpmyadmin is completely broken here. After logging
in, I get

( ! ) Fatal error: Uncaught exception 'LogicException' with message 'The
template "templates/navigation/logo.phtml" not found.' in
/usr/share/phpmyadmin/libraries/Template.class.php on line 95
( ! ) LogicException: The template "templates/navigation/logo.phtml" not
found. in /usr/share/phpmyadmin/libraries/Template.class.php on line 95


The apache error log contains:

[Wed Oct 07 14:11:03.002907 2015] [:error] [pid 11261] [client 127.0.0.1:41124] 
PHP Fatal error:  Uncaught exception 'LogicException' with message 'The 
template "templates/list/item.phtml" not found.' in 
/usr/share/phpmyadmin/libraries/Template.class.php:95\nStack trace:\n#0 
/usr/share/phpmyadmin/index.php(716): PMA\\Template->render(Array)\n#1 
/usr/share/phpmyadmin/index.php(199): PMA_printListItem('http://localhost/phpmyadmin/
[Wed Oct 07 14:11:03.004115 2015] [:error] [pid 11261] [client 127.0.0.1:41124] 
PHP Fatal error:  Uncaught exception 'LogicException' with message 'The 
template "templates/navigation/logo.phtml" not found.' in 
/usr/share/phpmyadmin/libraries/Template.class.php:95\nStack trace:\n#0 
/usr/share/phpmyadmin/libraries/navigation/NavigationHeader.class.php(142): 
PMA\\Template->render(Array)\n#1 
/usr/share/phpmyadmin/libraries/navigation/NavigationHeader.class.php(55): 
PMA_NavigationHeader->_logo()\n#2 
/usr/share/phpmyadmin/libraries/navigation/Navigation.class.php(35): 
PMA_NavigationHeader->getDisplay()\n#3 
/usr/share/phpmyadmin/libraries/Header.class.php(433): 
PMA_Navigation->getDisplay()\n#4 
/usr/share/phpmyadmin/libraries/Response.class.php(263): 
PMA_Header->getDisplay()\n#5 
/usr/share/phpmyadmin/libraries/Response.class.php(276): 
PMA_Response->_getDisplay()\n#6 
/usr/share/phpmyadmin/libraries/Response.class.php(397): 
PMA_Response->_htmlResponse()\n#7 [internal function]: PMA_Response::r
 esponse()\n#8 {main}\n  thrown in 
/usr/share/phpmyadmin/libraries/Template.class.php on line 95, referer: 
http://localhost/phpmyadmin/



root@pluto:/usr/share/phpmyadmin# grep phtml -R
libraries/Template.class.php:$template = static::BASE_PATH . 
$this->name . '.phtml';
root@pluto:/usr/share/phpmyadmin# dpkg -L phpmyadmin | grep phtml || echo "not 
found"
not found



-- 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.2.0-1-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)

Versions of packages phpmyadmin depends on:
ii  dbconfig-common1.8.54
ii  debconf [debconf-2.0]  1.5.57
ii  libapache2-mod-php55.6.14+dfsg-1
ii  libjs-sphinxdoc1.3.1-6
ii  perl   5.20.2-6
ii  php-gettext1.0.11-1
ii  php-seclib 1.0.0-2
ii  php5-json  1.3.7-1
ii  php5-mcrypt5.6.14+dfsg-1
ii  php5-mysql 5.6.14+dfsg-1
ii  ucf3.0030

Versions of packages phpmyadmin recommends:
ii  apache2 [httpd]  2.4.16-3
ii  mysql-client 5.6.25-4
ii  mysql-client-5.6 [virtual-mysql-client]  5.6.25-4
ii  php-tcpdf6.0.093+dfsg-1
ii  php5-gd  5.6.14+dfsg-1

Versions of packages phpmyadmin suggests:
ii  google-chrome-stable [www-browser]   45.0.2454.101-1
ii  iceweasel [www-browser]  38.3.0esr-1
ii  konqueror [www-browser]  4:15.08.1-1
ii  lynx-cur [www-browser]   2.8.9dev6-4
ii  mysql-server 5.6.25-4
ii  mysql-server-5.6 [virtual-mysql-server]  5.6.25-4
ii  w3m [www-browser]0.5.3-24

-- debconf information excluded

Processed: limit source to phpmyadmin, tagging 801194

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> limit source phpmyadmin
Limiting to bugs with field 'source' containing at least one of 'phpmyadmin'
Limit currently set to 'source':'phpmyadmin'

> tags 801194 + pending
Bug #801194 [phpmyadmin] The template "templates/navigation/logo.phtml" not 
found.
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: severity of 801190 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 801190 serious
Bug #801190 [valac] valac 0.30.0-1 fails to install (error: no alternatives for 
valac)
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#801206: marked as done (python-redmine: Missing Build-Depends on python3-requests)

[Debian Bug Tracking System]

Your message dated Wed, 07 Oct 2015 14:17:29 +0100
with message-id 
<1444223849.4151072.403769073.7597d...@webmail.messagingengine.com>
and subject line Re: Bug#801206: Acknowledgement (python-redmine: Missing 
Build-Depends on python3-requests)
has caused the Debian Bug report #801206,
regarding python-redmine: Missing Build-Depends on python3-requests
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.)


-- 
801206: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801206
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-redmine
Version: 1.1.1-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
Tags: patch

Dear Maintainer,

python-redmine fails to build from source in unstable/amd64 due
to missing Build-Depends on python3-requests:

  [..]

  I: pybuild base:170: cd
  /tmp/buildd/python-redmine-1.1.1/.pybuild/pythonX.Y_3.5/build;
  python3.5 -m unittest discover -v 
  redmine (unittest.loader._FailedTest) ... ERROR
  
  ==
  ERROR: redmine (unittest.loader._FailedTest)
  --
  ImportError: Failed to import test module: redmine
  Traceback (most recent call last):
File "/usr/lib/python3.5/unittest/loader.py", line 462, in
_find_test_path
  package = self._get_module_from_name(name)
File "/usr/lib/python3.5/unittest/loader.py", line 369, in
_get_module_from_name
  __import__(name)
File

"/tmp/buildd/python-redmine-1.1.1/.pybuild/pythonX.Y_3.5/build/redmine/__init__.py",
line 3, in 
  import requests
  ImportError: No module named 'requests'
  
  
  --
  Ran 1 test in 0.000s
  
  FAILED (errors=1)
  E: pybuild pybuild:262: test: plugin distutils failed with: exit
  code=1: cd
  /tmp/buildd/python-redmine-1.1.1/.pybuild/pythonX.Y_3.5/build;
  python3.5 -m unittest discover -v 
  dh_auto_test: pybuild --test -i python{version} -p 3.4 3.5 --dir .
  returned exit code 13
  debian/rules:6: recipe for target 'build' failed
  make: *** [build] Error 25
  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/python-redmine_1.1.1-1.build1.log.gz


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Duplicate email...

On Wed, 7 Oct 2015, at 02:15 PM, Debian Bug Tracking System wrote:
> Thank you for filing a new Bug report with Debian.
> 
> This is an automatically generated reply to let you know your message
> has been received.
> 
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
> 
> As you requested using X-Debbugs-CC, your message was also forwarded to
>   reproducible-bui...@lists.alioth.debian.org
> (after having been given a Bug report number, if it did not have one).
> 
> Your message has been sent to the package maintainer(s):
>  Benjamin Drung 
> 
> If you wish to submit further information on this problem, please
> send it to 801...@bugs.debian.org.
> 
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
> 
> -- 
> 801206: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801206
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems


Regards,

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

Bug#801203: kazam: Fails to start, throws a trace

[George B.]

Package: kazam
Version: 1.4.5-1
Severity: grave
Justification: renders package unusable

Hello,

Kazam no longer starts - the following trace is shown instead:

```
/usr/bin/kazam:32: PyGIWarning: Gtk was imported without specifying a version 
first. Use gi.require_version('Gtk', '3.0') before import to ensure that the 
right version gets loaded.
  from gi.repository import Gtk
/usr/lib/python3/dist-packages/kazam/backend/prefs.py:28: PyGIWarning: GdkX11 
was imported without specifying a version first. Use 
gi.require_version('GdkX11', '3.0') before import to ensure that the right 
version gets loaded.
  from gi.repository import Gdk, GdkX11
Traceback (most recent call last):
  File "/usr/bin/kazam", line 146, in 
from kazam.app import KazamApp
  File "/usr/lib/python3/dist-packages/kazam/app.py", line 35, in 
from kazam.backend.prefs import *
  File "/usr/lib/python3/dist-packages/kazam/backend/prefs.py", line 478, in 

prefs = Prefs()
  File "/usr/lib/python3/dist-packages/kazam/backend/prefs.py", line 121, in 
__init__
self.read_config()
  File "/usr/lib/python3/dist-packages/kazam/backend/prefs.py", line 199, in 
read_config
self.audio_source = int(self.config.get("main", "audio_source"))
  File "/usr/lib/python3/dist-packages/kazam/backend/config.py", line 103, in 
get
return ConfigParser.get(self, section, key)
  File "/usr/lib/python3.4/configparser.py", line 772, in get
d)
  File "/usr/lib/python3.4/configparser.py", line 371, in before_get
self._interpolate_some(parser, option, L, value, section, defaults, 1)
  File "/usr/lib/python3.4/configparser.py", line 384, in _interpolate_some
rawval = parser.get(section, option, raw=True, fallback=rest)
TypeError: get() got an unexpected keyword argument 'raw'
```


Best regards,

George

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

Kernel: Linux 4.2.0-1-amd64 (SMP w/8 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)

Versions of packages kazam depends on:
ii  gir1.2-gst-plugins-base-1.0  1.6.0-1
ii  gir1.2-gstreamer-1.0 1.6.0-1
ii  gir1.2-keybinder-3.0 0.3.0-1
ii  gir1.2-wnck-3.0  3.14.0-2
ii  gnome-session-canberra   0.30-2.1
ii  gstreamer1.0-plugins-base1.6.0-1
ii  gstreamer1.0-plugins-good1.6.0-1
ii  gstreamer1.0-plugins-ugly1.6.0-1
ii  gstreamer1.0-pulseaudio  1.6.0-1
ii  python3  3.4.3-6
ii  python3-cairo1.10.0+dfsg-5
ii  python3-dbus 1.2.0-2+b4
ii  python3-gi   3.18.0-1
ii  python3-gi-cairo 3.18.0-1
ii  python3-xdg  0.25-4
pn  python3:any  

Versions of packages kazam recommends:
ii  gstreamer1.0-libav  1.6.0-1

kazam suggests no packages.

-- no debconf information

Bug#801205: python-redmine: Missing Build-Depends on python3-requests

[Chris Lamb]

Source: python-redmine
Version: 1.1.1-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
Tags: patch

Dear Maintainer,

python-redmine fails to build from source in unstable/amd64 due
to missing Build-Depends on python3-requests:

  [..]

  I: pybuild base:170: cd
  /tmp/buildd/python-redmine-1.1.1/.pybuild/pythonX.Y_3.5/build;
  python3.5 -m unittest discover -v 
  redmine (unittest.loader._FailedTest) ... ERROR
  
  ==
  ERROR: redmine (unittest.loader._FailedTest)
  --
  ImportError: Failed to import test module: redmine
  Traceback (most recent call last):
File "/usr/lib/python3.5/unittest/loader.py", line 462, in
_find_test_path
  package = self._get_module_from_name(name)
File "/usr/lib/python3.5/unittest/loader.py", line 369, in
_get_module_from_name
  __import__(name)
File

"/tmp/buildd/python-redmine-1.1.1/.pybuild/pythonX.Y_3.5/build/redmine/__init__.py",
line 3, in 
  import requests
  ImportError: No module named 'requests'
  
  
  --
  Ran 1 test in 0.000s
  
  FAILED (errors=1)
  E: pybuild pybuild:262: test: plugin distutils failed with: exit
  code=1: cd
  /tmp/buildd/python-redmine-1.1.1/.pybuild/pythonX.Y_3.5/build;
  python3.5 -m unittest discover -v 
  dh_auto_test: pybuild --test -i python{version} -p 3.4 3.5 --dir .
  returned exit code 13
  debian/rules:6: recipe for target 'build' failed
  make: *** [build] Error 25
  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/python-redmine_1.1.1-1.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: Tue Oct  6 14:39:32 GMT+12 2015
I: pbuilder-time-stamp: 1444185572
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: debhelper (>= 9), dh-python, python-all (>= 2.6.6-3~), 
python-setuptools (>= 0.6b3), python3-all, python3-setuptools
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20294 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 dh-python; however:
  Package dh-python is not installed.
 pbuilder-satisfydepends-dummy depends on python-all (>= 2.6.6-3~); however:
  Package python-all is not installed.
 pbuilder-satisfydepends-dummy depends on python-setuptools (>= 0.6b3); however:
  Package python-setuptools is not installed.
 pbuilder-satisfydepends-dummy depends on python3-all; however:
  Package python3-all is not installed.
 pbuilder-satisfydepends-dummy depends on python3-setuptools; however:
  Package python3-setuptools is not installed.

Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
Reading package lists...
Building dependency tree...
Reading state information...
Initializing package states...
Writing extended state information...
Building tag database...
pbuilder-satisfydepends-dummy is already installed at the requested version 
(0.invalid.0)
pbuilder-satisfydepends-dummy is already installed at the requested version 
(0.invalid.0)
The following NEW packages will be installed:
  dh-python{a} libexpat1{a} libmpdec2{a} libpython-stdlib{a} 
  libpython2.7-minimal{a} libpython2.7-stdlib{a} libpython3-stdlib{a} 
  libpython3.4-minimal{a} libpython3.4-stdlib{a} libpython3.5-minimal{a} 
  libpython3.5-stdlib{a} libssl1.0.0{a} 

Bug#801206: python-redmine: Missing Build-Depends on python3-requests

[Chris Lamb]

Source: python-redmine
Version: 1.1.1-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
Tags: patch

Dear Maintainer,

python-redmine fails to build from source in unstable/amd64 due
to missing Build-Depends on python3-requests:

  [..]

  I: pybuild base:170: cd
  /tmp/buildd/python-redmine-1.1.1/.pybuild/pythonX.Y_3.5/build;
  python3.5 -m unittest discover -v 
  redmine (unittest.loader._FailedTest) ... ERROR
  
  ==
  ERROR: redmine (unittest.loader._FailedTest)
  --
  ImportError: Failed to import test module: redmine
  Traceback (most recent call last):
File "/usr/lib/python3.5/unittest/loader.py", line 462, in
_find_test_path
  package = self._get_module_from_name(name)
File "/usr/lib/python3.5/unittest/loader.py", line 369, in
_get_module_from_name
  __import__(name)
File

"/tmp/buildd/python-redmine-1.1.1/.pybuild/pythonX.Y_3.5/build/redmine/__init__.py",
line 3, in 
  import requests
  ImportError: No module named 'requests'
  
  
  --
  Ran 1 test in 0.000s
  
  FAILED (errors=1)
  E: pybuild pybuild:262: test: plugin distutils failed with: exit
  code=1: cd
  /tmp/buildd/python-redmine-1.1.1/.pybuild/pythonX.Y_3.5/build;
  python3.5 -m unittest discover -v 
  dh_auto_test: pybuild --test -i python{version} -p 3.4 3.5 --dir .
  returned exit code 13
  debian/rules:6: recipe for target 'build' failed
  make: *** [build] Error 25
  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/python-redmine_1.1.1-1.build1.log.gz


Regards,

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

Bug#801208: django-ajax-selects: FTBFS: ImportError: No module named 'django'

[Chris Lamb]

Source: django-ajax-selects
Version: 1.3.6-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,

django-ajax-selects fails to build from source in unstable/amd64. Once
installing python3-requests, I get a different traceback
("AttributeError: module 'html.parser' has no attribute
'HTMLParseError'").

  [..]

  I: pybuild base:170: cd
  /tmp/buildd/django-ajax-selects-1.3.6/.pybuild/pythonX.Y_3.5/build;
  python3.5 -m unittest discover -v 
  ajax_select (unittest.loader._FailedTest) ... ERROR
  
  ==
  ERROR: ajax_select (unittest.loader._FailedTest)
  --
  ImportError: Failed to import test module: ajax_select
  Traceback (most recent call last):
File "/usr/lib/python3.5/unittest/loader.py", line 462, in
_find_test_path
  package = self._get_module_from_name(name)
File "/usr/lib/python3.5/unittest/loader.py", line 369, in
_get_module_from_name
  __import__(name)
File

"/tmp/buildd/django-ajax-selects-1.3.6/.pybuild/pythonX.Y_3.5/build/ajax_select/__init__.py",
line 7, in 
  from django.conf import settings
  ImportError: No module named 'django'
  
  
  --
  Ran 1 test in 0.000s
  
  FAILED (errors=1)
  E: pybuild pybuild:262: test: plugin distutils failed with: exit
  code=1: cd
  /tmp/buildd/django-ajax-selects-1.3.6/.pybuild/pythonX.Y_3.5/build;
  python3.5 -m unittest discover -v 
  dh_auto_test: pybuild --test -i python{version} -p 3.4 3.5 --dir .
  returned exit code 13
  debian/rules:7: recipe for target 'build' failed
  make: *** [build] Error 25
  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/django-ajax-selects_1.3.6-3.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: Sun Oct  4 20:48:15 GMT+12 2015
I: pbuilder-time-stamp: 1444034895
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: debhelper (>= 8.1.0), dh-python, python-all (>= 2.6.6-3~), 
python-setuptools, python3-all, python3-setuptools
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20294 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 dh-python; however:
  Package dh-python is not installed.
 pbuilder-satisfydepends-dummy depends on python-all (>= 2.6.6-3~); however:
  Package python-all is not installed.
 pbuilder-satisfydepends-dummy depends on python-setuptools; however:
  Package python-setuptools is not installed.
 pbuilder-satisfydepends-dummy depends on python3-all; however:
  Package python3-all is not installed.
 pbuilder-satisfydepends-dummy depends on python3-setuptools; however:
  Package python3-setuptools is not installed.

Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
Reading package lists...
Building dependency tree...
Reading state information...
Initializing package states...
Writing extended state information...
Building tag database...
pbuilder-satisfydepends-dummy is already installed at the requested version 
(0.invalid.0)
pbuilder-satisfydepends-dummy is already installed at the requested version 
(0.invalid.0)
The following NEW packages will be installed:
  dh-python{a} libexpat1{a} libmpdec2{a} libpython-stdlib{a} 
  libpython2.7-minimal{a} libpython2.7-stdlib{a} libpython3-stdlib{a} 
  

Bug#793791: [Pkg-anonymity-tools] Bug#793791: Bug#793791: Bug#793791: torbrowser-launcher: Fail to start "TypeError: _getEndpoint() takes exactly 4 arguments (2 given)"

[Paul Wise]

On Wed, 2015-10-07 at 16:42 +0200, Holger Levsen wrote:

> cool, thanks for confirming. Closing accordingly.

Hmm, I can't reproduce it any more either, weird.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise




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

Bug#798049: marked as pending

[Daniel Stender]

tag 798049 pending
thanks

Hello,

Bug #798049 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

http://git.debian.org/?p=collab-maint/scantailor.git;a=commitdiff;h=7a78261

---
commit 7a782610dc4ca2a8870b591b4506461ce3e76ded
Author: Daniel Stender 
Date:   Wed Oct 7 16:52:56 2015 +0200

added fix-qt4-parsing-error-on-libboost.patch

diff --git a/debian/changelog b/debian/changelog
index 5ff0420..6a00be2 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8 +1,9 @@
 scantailor (0.9.11.1-4) UNRELEASED; urgency=medium
 
+  * Added fix-qt4-parsing-error-on-libboost.patch (Closes: #798049)
   * deb/control: added libboost-dev to build-deps.
 
- -- Daniel Stender   Wed, 07 Oct 2015 01:18:13 +0200
+ -- Daniel Stender   Wed, 07 Oct 2015 16:52:04 +0200
 
 scantailor (0.9.11.1-3) unstable; urgency=medium
 

Processed: scantailor FTBFS in current Sid

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 798049 scantailor: Qt4 MOC parsing error on libboost1.58
Bug #798049 [scantailor] scantailor FTBFS in current Sid
Changed Bug title to 'scantailor: Qt4 MOC parsing error on libboost1.58' from 
'scantailor FTBFS in current Sid'
> thanks
Stopping processing here.

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

Processed: Bug#798049 marked as pending

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 798049 pending
Bug #798049 [scantailor] scantailor FTBFS in current Sid
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#794363: marked as done (torbrowser-launcher: TypeError: _getEndpoint() takes exactly 4 arguments (2 given))

[Debian Bug Tracking System]

Your message dated Wed, 7 Oct 2015 16:42:58 +0200
with message-id <201510071643.02813.hol...@layer-acht.org>
and subject line Re: [Pkg-anonymity-tools] Bug#793791: Bug#793791: Bug#793791: 
torbrowser-launcher: Fail to start "TypeError: _getEndpoint() takes exactly 4 
arguments (2 given)"
has caused the Debian Bug report #793791,
regarding torbrowser-launcher: TypeError: _getEndpoint() takes exactly 4 
arguments (2 given)
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.)


-- 
793791: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793791
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: torbrowser-launcher
Version: 0.2.0-1
Severity: serious
Justification: doesn't start
Usertags: crash

torbrowser-launcher crashes on startup for me, it looks like the APIs
for twisted have changed recently when 15.x reached testing:

https://packages.qa.debian.org/t/twisted/news/20150731T163916Z.html
https://packages.qa.debian.org/t/twisted/news/20150725T172059Z.html
https://packages.qa.debian.org/t/twisted/news/20150309T094947Z.html
https://raw.githubusercontent.com/twisted/twisted/releases/release-15.0.0-7335/NEWS

pabs@chianamo ~ $ which-pkg-broke torbrowser-launcher | tail
python-twisted-web Fri Jul 31 12:47:58 2015
python-twisted-loreFri Jul 31 12:48:01 2015
python-twisted-mailFri Jul 31 12:48:05 2015
python-twisted-names   Fri Jul 31 12:48:09 2015
python-twisted-newsFri Jul 31 12:48:11 2015
python-twisted-runner  Fri Jul 31 12:48:14 2015
python-twisted-words   Fri Jul 31 12:48:16 2015
python-twisted-conch   Fri Jul 31 12:48:34 2015
python-twisted Fri Jul 31 12:48:36 2015
libsqlite3-0:amd64 Sat Aug  1 12:13:16 2015

pabs@chianamo ~ $ torbrowser-launcher 
Tor Browser Launcher
By Micah Lee, licensed under MIT
version 0.2.0
https://github.com/micahflee/torbrowser-launcher
Updating over Tor
Checking for update
Downloading 
https://www.torproject.org/projects/torbrowser/RecommendedTBBVersions
Traceback (most recent call last):
  File "/usr/bin/torbrowser-launcher", line 30, in 
torbrowser_launcher.main()
  File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/__init__.py", line 
69, in main
app = Launcher(common, url_list)
  File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py", line 
130, in __init__
self.build_ui()
  File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py", line 
284, in build_ui
self.start(None)
  File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py", line 
293, in start
self.run_task()
  File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py", line 
310, in run_task
self.download('update check', self.common.paths['update_check_url'], 
self.common.paths['update_check_file'])
  File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py", line 
469, in download
None)
  File "/usr/lib/python2.7/dist-packages/twisted/web/client.py", line 1926, in 
request
deferred = self._agent.request(method, uri, headers, bodyProducer)
  File "/usr/lib/python2.7/dist-packages/twisted/web/client.py", line 1559, in 
request
endpoint = self._getEndpoint(parsedURI)
TypeError: _getEndpoint() takes exactly 4 arguments (2 given)

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (860, 'testing-proposed-updates'), (850, 
'buildd-testing-proposed-updates'), (800, 'unstable'), (790, 
'buildd-unstable'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages torbrowser-launcher depends on:
ii  gnupg1.4.19-3
ii  python   2.7.9-1
ii  python-gtk2  2.24.0-4
ii  python-lzma  0.5.3-2+b1
ii  python-parsley   1.2-1
ii  python-psutil2.1.1-1+b1
ii  python-twisted   15.2.1-1
ii  python-txsocksx  1.13.0.3-1
ii  tor  0.2.6.10-1
ii  wmctrl   1.07-7

torbrowser-launcher recommends no packages.

Versions of packages torbrowser-launcher suggests:
pn  apparmor   
ii  python-pygame  1.9.1release+dfsg-10+b1

-- no debconf information

Bug#793791: marked as done (torbrowser-launcher: Fail to start "TypeError: _getEndpoint() takes exactly 4 arguments (2 given)")

[Debian Bug Tracking System]

Your message dated Wed, 7 Oct 2015 16:42:58 +0200
with message-id <201510071643.02813.hol...@layer-acht.org>
and subject line Re: [Pkg-anonymity-tools] Bug#793791: Bug#793791: Bug#793791: 
torbrowser-launcher: Fail to start "TypeError: _getEndpoint() takes exactly 4 
arguments (2 given)"
has caused the Debian Bug report #793791,
regarding torbrowser-launcher: Fail to start "TypeError: _getEndpoint() takes 
exactly 4 arguments (2 given)"
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.)


-- 
793791: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793791
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: torbrowser-launcher
Version: 0.2.0-1
Severity: normal

Dear maintener,
while trying to launch torbrowser-launcher it fail,
and return me this error:
Tor Browser Launcher
By Micah Lee, licensed under MIT
version 0.2.0
https://github.com/micahflee/torbrowser-launcher
Updating over Tor
Checking for update
Downloading 
https://www.torproject.org/projects/torbrowser/RecommendedTBBVersions
Traceback (most recent call last):
  File "/usr/bin/torbrowser-launcher", line 30, in 
torbrowser_launcher.main()
  File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/__init__.py", line 
69, in main
app = Launcher(common, url_list)
  File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py", line 
130, in __init__
self.build_ui()
  File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py", line 
284, in build_ui
self.start(None)
  File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py", line 
293, in start
self.run_task()
  File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py", line 
310, in run_task
self.download('update check', self.common.paths['update_check_url'], 
self.common.paths['update_check_file'])
  File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py", line 
469, in download
None)
  File "/usr/lib/python2.7/dist-packages/twisted/web/client.py", line 1926, in 
request
deferred = self._agent.request(method, uri, headers, bodyProducer)
  File "/usr/lib/python2.7/dist-packages/twisted/web/client.py", line 1559, in 
request
endpoint = self._getEndpoint(parsedURI)
TypeError: _getEndpoint() takes exactly 4 arguments (2 given)

Guillaume.



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

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

Versions of packages torbrowser-launcher depends on:
ii  gnupg1.4.19-3
ii  python   2.7.9-1
ii  python-gtk2  2.24.0-4
ii  python-lzma  0.5.3-2+b1
ii  python-parsley   1.2-1
ii  python-psutil2.1.1-1+b1
ii  python-twisted   15.2.1-1
ii  python-txsocksx  1.13.0.3-1
ii  tor  0.2.6.10-1
ii  wmctrl   1.07-7

torbrowser-launcher recommends no packages.

Versions of packages torbrowser-launcher suggests:
ii  apparmor   2.9.2-3
pn  python-pygame  

-- no debconf information
--- End Message ---
--- Begin Message ---
control: tags -1 + unreproducible
thanks

Hi Tobias,

On Mittwoch, 7. Oktober 2015, Tobias Scherer wrote:
> I cannot reproduce it in sid. Here is what I get, everything looks fine.

cool, thanks for confirming. Closing accordingly.


cheers,
Holger


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

Bug#794574: marked as done (torbrowser-launcher: launcher throws error on start)

[Debian Bug Tracking System]

Your message dated Wed, 7 Oct 2015 16:42:58 +0200
with message-id <201510071643.02813.hol...@layer-acht.org>
and subject line Re: [Pkg-anonymity-tools] Bug#793791: Bug#793791: Bug#793791: 
torbrowser-launcher: Fail to start "TypeError: _getEndpoint() takes exactly 4 
arguments (2 given)"
has caused the Debian Bug report #793791,
regarding torbrowser-launcher: launcher throws error on start
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.)


-- 
793791: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793791
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: torbrowser-launcher
Version: 0.2.0-1
Severity: grave
Justification: renders package unusable

torbrowser-launcher errors out on launch, only shortly displaying the "Checking 
for Tor Browser updates" window:

$ torbrowser-launcher 
Tor Browser Launcher
By Micah Lee, licensed under MIT
version 0.2.0
https://github.com/micahflee/torbrowser-launcher
Updating over Tor
Checking for update
/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py:281: 
GtkWarning: Error parsing gtk-icon-sizes string:
'gtk-menu:24,24'
  self.window.show()
Downloading 
https://www.torproject.org/projects/torbrowser/RecommendedTBBVersions
Traceback (most recent call last):
  File "/usr/bin/torbrowser-launcher", line 30, in 
torbrowser_launcher.main()
  File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/__init__.py", line 
69, in main
app = Launcher(common, url_list)
  File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py", line 
130, in __init__
self.build_ui()
  File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py", line 
284, in build_ui
self.start(None)
  File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py", line 
293, in start
self.run_task()
  File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py", line 
310, in run_task
self.download('update check', self.common.paths['update_check_url'], 
self.common.paths['update_check_file'])
  File "/usr/lib/python2.7/dist-packages/torbrowser_launcher/launcher.py", line 
469, in download
None)
  File "/usr/lib/python2.7/dist-packages/twisted/web/client.py", line 1926, in 
request
deferred = self._agent.request(method, uri, headers, bodyProducer)
  File "/usr/lib/python2.7/dist-packages/twisted/web/client.py", line 1559, in 
request
endpoint = self._getEndpoint(parsedURI)
TypeError: _getEndpoint() takes exactly 4 arguments (2 given)


starting tbb from 
~/.local/share/torbrowser/tbb/x86_64/tor-browser_de/start-tor-browser still 
works, but if you don't know where to look for that, TBB is pretty much 
unusable.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (1001, 'testing'), (550, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages torbrowser-launcher depends on:
ii  gnupg1.4.19-3
ii  python   2.7.9-1
ii  python-gtk2  2.24.0-4
ii  python-lzma  0.5.3-2+b1
ii  python-parsley   1.2-1
ii  python-psutil2.1.1-1+b1
ii  python-twisted   15.2.1-1
ii  python-txsocksx  1.13.0.3-1
ii  tor  0.2.6.10-1
ii  wmctrl   1.07-7

torbrowser-launcher recommends no packages.

Versions of packages torbrowser-launcher suggests:
pn  apparmor   
ii  python-pygame  1.9.1release+dfsg-10+b1

-- no debconf information
--- End Message ---
--- Begin Message ---
control: tags -1 + unreproducible
thanks

Hi Tobias,

On Mittwoch, 7. Oktober 2015, Tobias Scherer wrote:
> I cannot reproduce it in sid. Here is what I get, everything looks fine.

cool, thanks for confirming. Closing accordingly.


cheers,
Holger


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

Processed: forwarding 800617

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 800617 https://bugzilla.gnome.org/show_bug.cgi?id=756059
Bug #800617 [gnome-keyring] Fails to provide secrets
Set Bug forwarded-to-address to 
'https://bugzilla.gnome.org/show_bug.cgi?id=756059'.
> thanks
Stopping processing here.

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

Bug#798924: /usr/lib/x86_64-linux-gnu/jni/libatk-wrapper.so.6.0.0: SIGSEGV on Netbeans startup

[Alexandre Pereira Nunes]

Package: libatk-wrapper-java
Version: 0.33.3-1
Followup-For: Bug #798924

Is this a revival of #798273?

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

Kernel: Linux 4.2.1 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages libatk-wrapper-java depends on:
ii  x11-utils  7.7+3

Versions of packages libatk-wrapper-java recommends:
ii  libatk-wrapper-java-jni  0.33.3-1

libatk-wrapper-java suggests no packages.

-- no debconf information

Bug#798924: /usr/lib/x86_64-linux-gnu/jni/libatk-wrapper.so.6.0.0: SIGSEGV on Netbeans startup

[Alexandre Pereira Nunes]

Package: libatk-wrapper-java
Version: 0.33.3-1
Followup-For: Bug #798924

I've patched the package build system to generate a debug package. This can
further help getting usable stack traces from java core dump.



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

Kernel: Linux 4.2.1 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages libatk-wrapper-java depends on:
ii  x11-utils  7.7+3

Versions of packages libatk-wrapper-java recommends:
ii  libatk-wrapper-java-jni  0.33.3-1

libatk-wrapper-java suggests no packages.

-- debconf-show failed
diff -pru 2.orig/java-atk-wrapper-0.33.3/debian/changelog 2/java-atk-wrapper-0.33.3/debian/changelog
--- 2.orig/java-atk-wrapper-0.33.3/debian/changelog	2015-09-12 07:39:38.0 -0300
+++ 2/java-atk-wrapper-0.33.3/debian/changelog	2015-10-07 14:36:14.030860951 -0300
@@ -1,3 +1,10 @@
+java-atk-wrapper (0.33.3-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add debug packages.
+
+ -- Alexandre Pereira Nunes   Wed, 07 Oct 2015 14:35:51 -0300
+
 java-atk-wrapper (0.33.3-1) unstable; urgency=medium
 
   * New upstream release.
diff -pru 2.orig/java-atk-wrapper-0.33.3/debian/control 2/java-atk-wrapper-0.33.3/debian/control
--- 2.orig/java-atk-wrapper-0.33.3/debian/control	2015-09-08 23:20:38.0 -0300
+++ 2/java-atk-wrapper-0.33.3/debian/control	2015-10-07 14:33:50.529307388 -0300
@@ -30,3 +30,15 @@ Description: ATK implementation for Java
  ATK-Bridge.
  .
  This package contains the JNI bindings.
+
+Package: libatk-wrapper-java-jni-dbg
+Architecture: any
+Multi-Arch: same
+Pre-Depends: ${misc:Pre-Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends}, libatk-wrapper-java (>= ${source:Version})
+Description: ATK implementation for Java using JNI (JNI bindings)
+ Java ATK Wrapper is an implementation of ATK which uses JNI. It
+ converts Java Swing events into ATK events, and sends these events to
+ ATK-Bridge.
+ .
+ This package contains the debug symbos for the JNI bindings.
diff -pru 2.orig/java-atk-wrapper-0.33.3/debian/rules 2/java-atk-wrapper-0.33.3/debian/rules
--- 2.orig/java-atk-wrapper-0.33.3/debian/rules	2015-09-08 23:26:26.0 -0300
+++ 2/java-atk-wrapper-0.33.3/debian/rules	2015-10-07 14:35:35.614670875 -0300
@@ -12,3 +12,8 @@ clean-local:
 
 override_dh_auto_configure:
 	JAVACFLAGS="$(JAVACFLAGS)" dh_auto_configure -- --libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH)/jni/
+
+override_dh_strip:
+	dh_strip -plibatk-wrapper-java-jni --dbg-package=libatk-wrapper-java-jni-dbg
+
+.PHONY: override_dh_strip override_dh_auto_configure

Bug#798499: marked as done (thin-provisioning-tools: FTBFS: "If you want to output boost::optional, include header ")

[Debian Bug Tracking System]

Your message dated Wed, 7 Oct 2015 19:48:12 +0200
with message-id <20151007174812.ga10...@mail.waldi.eu.org>
and subject line fixed
has caused the Debian Bug report #798499,
regarding thin-provisioning-tools: FTBFS: "If you want to output 
boost::optional, include header "
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.)


-- 
798499: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798499
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: thin-provisioning-tools
Version: 0.3.2-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,

thin-provisioning-tools fails to build from source in unstable/amd64:

  [..]

  g++ -c -I. -I. -I./thin-provisioning -Wdate-time -D_FORTIFY_SOURCE=2
  -Wall -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
  -o thin-provisioning/human_readable_format.o
  thin-provisioning/human_readable_format.cc
  In file included from /usr/include/boost/optional/optional.hpp:28:0,
   from /usr/include/boost/optional.hpp:15,
   from thin-provisioning/emitter.h:23,
   from thin-provisioning/human_readable_format.h:22,
   from thin-provisioning/human_readable_format.cc:19:
  /usr/include/boost/optional/optional.hpp: In instantiation of
  'std::basic_ostream<_CharT, _Traits>&
  boost::operator<<(std::basic_ostream<_CharT, _Traits>&, const
  boost::optional_detail::optional_tag&) [with CharType = char;
  CharTrait = std::char_traits]':
  thin-provisioning/human_readable_format.cc:47:21:   required from here
  /usr/include/boost/optional/optional.hpp:1256:3: error: invalid
  application of 'sizeof' to incomplete type
  'boost::STATIC_ASSERTION_FAILURE'
 BOOST_STATIC_ASSERT_MSG(sizeof(CharType) == 0, "If you want to
 output boost::optional, include header
 "); 
 ^
  Makefile:144: recipe for target
  'thin-provisioning/human_readable_format.o' failed
  make[1]: *** [thin-provisioning/human_readable_format.o] Error 1
  make[1]: Leaving directory '/tmp/buildd/thin-provisioning-tools-0.3.2'
  dh_auto_build: make -j1 returned exit code 2
  debian/rules:8: recipe for target 'build' failed
  make: *** [build] 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/thin-provisioning-tools_0.3.2-1.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: Thu Sep  3 18:17:08 GMT+12 2015
I: pbuilder-time-stamp: 1441347428
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: debhelper (>= 9), dh-autoreconf, libboost-dev, libexpat1-dev
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20262 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 dh-autoreconf; however:
  Package dh-autoreconf is not installed.
 pbuilder-satisfydepends-dummy depends on libboost-dev; however:
  Package libboost-dev is not installed.
 pbuilder-satisfydepends-dummy depends on libexpat1-dev; however:
  Package libexpat1-dev is not installed.

Setting up 

Processed: spice: diff for NMU version 0.12.5-1.3

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 801089 + patch pending
Bug #801089 [src:spice] spice: CVE-2015-5260: Insufficient validation of 
surface_id parameter can cause crash
Added tag(s) patch and pending.
> tags 801091 + patch pending
Bug #801091 [src:spice] spice: CVE-2015-5261: host memory access from guest 
using crafted images
Added tag(s) pending and patch.
> thanks
Stopping processing here.

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

Bug#801089: spice: diff for NMU version 0.12.5-1.3

[Salvatore Bonaccorso]

tags 801089 + patch pending
tags 801091 + patch pending
thanks

Dear maintainer,

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

Regards,
Salvatore
diff -Nru spice-0.12.5/debian/changelog spice-0.12.5/debian/changelog
--- spice-0.12.5/debian/changelog	2015-09-05 05:52:55.0 +0200
+++ spice-0.12.5/debian/changelog	2015-10-07 18:06:10.0 +0200
@@ -1,3 +1,14 @@
+spice (0.12.5-1.3) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Add series of patches for CVE-2015-5260 and CVE-2015-6261.
+CVE-2015-5260: insufficient validation of surface_id parameter can cause
+crash. (Closes: #801089)
+CVE-2015-5261: host memory access from guest using crafted images.
+(Closes: #801091)
+
+ -- Salvatore Bonaccorso   Wed, 07 Oct 2015 07:23:38 +0200
+
 spice (0.12.5-1.2) unstable; urgency=high
 
   * Non-maintainer upload.
diff -Nru spice-0.12.5/debian/patches/CVE-2015-5260_CVE-2015-5261/0001-worker-validate-correctly-surfaces.patch spice-0.12.5/debian/patches/CVE-2015-5260_CVE-2015-5261/0001-worker-validate-correctly-surfaces.patch
--- spice-0.12.5/debian/patches/CVE-2015-5260_CVE-2015-5261/0001-worker-validate-correctly-surfaces.patch	1970-01-01 01:00:00.0 +0100
+++ spice-0.12.5/debian/patches/CVE-2015-5260_CVE-2015-5261/0001-worker-validate-correctly-surfaces.patch	2015-10-07 18:06:10.0 +0200
@@ -0,0 +1,117 @@
+From dd558bb833254fb49069eca052b92ae1abe3e8ff Mon Sep 17 00:00:00 2001
+From: Frediano Ziglio 
+Date: Wed, 9 Sep 2015 12:42:09 +0100
+Subject: [PATCH 01/19] worker: validate correctly surfaces
+
+Do not just give warning and continue to use an invalid index into
+an array.
+
+Resolves: CVE-2015-5260
+
+Signed-off-by: Frediano Ziglio 
+Acked-by: Christophe Fergeau 
+---
+ server/red_worker.c | 33 ++---
+ 1 file changed, 18 insertions(+), 15 deletions(-)
+
+--- a/server/red_worker.c
 b/server/red_worker.c
+@@ -1036,6 +1036,7 @@ typedef struct BitmapData {
+ SpiceRect lossy_rect;
+ } BitmapData;
+ 
++static inline int validate_surface(RedWorker *worker, uint32_t surface_id);
+ static void red_draw_qxl_drawable(RedWorker *worker, Drawable *drawable);
+ static void red_current_flush(RedWorker *worker, int surface_id);
+ #ifdef DRAW_ALL
+@@ -1245,14 +1246,12 @@ static inline int is_primary_surface(Red
+ return FALSE;
+ }
+ 
+-static inline void __validate_surface(RedWorker *worker, uint32_t surface_id)
+-{
+-spice_warn_if(surface_id >= worker->n_surfaces);
+-}
+-
+ static inline int validate_surface(RedWorker *worker, uint32_t surface_id)
+ {
+-spice_warn_if(surface_id >= worker->n_surfaces);
++if SPICE_UNLIKELY(surface_id >= worker->n_surfaces) {
++spice_warning("invalid surface_id %u", surface_id);
++return 0;
++}
+ if (!worker->surfaces[surface_id].context.canvas) {
+ spice_warning("canvas address is %p for %d (and is NULL)\n",
+&(worker->surfaces[surface_id].context.canvas), surface_id);
+@@ -4230,12 +4229,14 @@ static inline void red_create_surface(Re
+ static inline void red_process_surface(RedWorker *worker, RedSurfaceCmd *surface,
+uint32_t group_id, int loadvm)
+ {
+-int surface_id;
++uint32_t surface_id;
+ RedSurface *red_surface;
+ uint8_t *data;
+ 
+ surface_id = surface->surface_id;
+-__validate_surface(worker, surface_id);
++if SPICE_UNLIKELY(surface_id >= worker->n_surfaces) {
++goto exit;
++}
+ 
+ red_surface = >surfaces[surface_id];
+ 
+@@ -4271,6 +4272,7 @@ static inline void red_process_surface(R
+ default:
+ spice_error("unknown surface command");
+ };
++exit:
+ red_put_surface_cmd(surface);
+ free(surface);
+ }
+@@ -10865,7 +10867,7 @@ void handle_dev_update(void *opaque, voi
+ {
+ RedWorker *worker = opaque;
+ RedWorkerMessageUpdate *msg = payload;
+-SpiceRect *rect = spice_new0(SpiceRect, 1);
++SpiceRect *rect;
+ RedSurface *surface;
+ uint32_t surface_id = msg->surface_id;
+ const QXLRect *qxl_area = msg->qxl_area;
+@@ -10873,17 +10875,16 @@ void handle_dev_update(void *opaque, voi
+ QXLRect *qxl_dirty_rects = msg->qxl_dirty_rects;
+ uint32_t clear_dirty_region = msg->clear_dirty_region;
+ 
++VALIDATE_SURFACE_RET(worker, surface_id);
++
++rect = spice_new0(SpiceRect, 1);
+ surface = >surfaces[surface_id];
+ red_get_rect_ptr(rect, qxl_area);
+ flush_display_commands(worker);
+ 
+ spice_assert(worker->running);
+ 
+-if (validate_surface(worker, surface_id)) {
+-red_update_area(worker, rect, surface_id);
+-} else {
+-rendering_incorrect(__func__);
+-}
++red_update_area(worker, rect, surface_id);
+ free(rect);
+ 
+ surface_dirty_region_to_rects(surface, 

Processed: Re: [Pkg-anonymity-tools] Bug#792215: Bug#792215: torbrowser-launcher: doesnt work, some depends probably missing

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 792215 serious
Bug #792215 [torbrowser-launcher] torbrowser-launcher: doesnt work, some 
depends probably missing
Severity set to 'serious' from 'important'
> forcemerge 784041 792215
Bug #784041 {Done: Holger Levsen } [torbrowser-launcher] 
exceptions.OSError: [Errno 2] No such file or directory
Bug #792215 [torbrowser-launcher] torbrowser-launcher: doesnt work, some 
depends probably missing
Set Bug forwarded-to-address to 
'https://github.com/micahflee/torbrowser-launcher/issues/176'.
Marked Bug as done
Marked as fixed in versions torbrowser-launcher/0.2.0-1~bpo8+1 and 
torbrowser-launcher/0.2.0-1.
Marked as found in versions torbrowser-launcher/0.1.9-1.
Added tag(s) fixed-upstream, confirmed, upstream, and help.
Merged 784041 792215
> thanks
Stopping processing here.

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

Bug#796446: marked as done (pyflakes: FTBFS: pybuild:262: test: plugin distutils failed with: exit code=1)

[Debian Bug Tracking System]

Your message dated Wed, 07 Oct 2015 16:02:35 +
with message-id 

and subject line Fixed a while ago
has caused the Debian Bug report #796446,
regarding pyflakes: FTBFS: pybuild:262: test: plugin distutils failed with: 
exit code=1
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.)


-- 
796446: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796446
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyflakes
Version: 0.8.1-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,

pyflakes fails to build from source in unstable/amd64:

  [..]
  ==
  FAIL: When pyflakes finds errors with the files it's given, (if they
  don't
  --
  Traceback (most recent call last):
File

"/tmp/buildd/pyflakes-0.8.1/.pybuild/pythonX.Y_2.7/build/pyflakes/test/test_api.py",
line 583, in test_errors
  self.assertEqual(d, ('', error_msg, 1))
  AssertionError: Tuples differ: ('', "/usr/bin/python2.7: can'... !=
  ('', '/tmp/tmpn4FNFz/temp: No ...
  
  First differing element 1:
  /usr/bin/python2.7: can't open file
  
'/tmp/buildd/pyflakes-0.8.1/.pybuild/pythonX.Y_2.7/build/pyflakes/../bin/pyflakes':
  [Errno 2] No such file or directory
  
  /tmp/tmpn4FNFz/temp: No such file or directory
  
  
  + ('', '/tmp/tmpn4FNFz/temp: No such file or directory\n', 1)
  - ('',
  -  "/usr/bin/python2.7: can't open file
  
'/tmp/buildd/pyflakes-0.8.1/.pybuild/pythonX.Y_2.7/build/pyflakes/../bin/pyflakes':
  [Errno 2] No such file or directory\n",
  -  2)
  
  ==
  FAIL: When a Python source file has warnings, the return code is
  non-zero
  --
  Traceback (most recent call last):
File

"/tmp/buildd/pyflakes-0.8.1/.pybuild/pythonX.Y_2.7/build/pyflakes/test/test_api.py",
line 573, in test_fileWithFlakes
  self.assertEqual(d, ("%s\n" % expected, '', 1))
  AssertionError: Tuples differ: ('', "/usr/bin/python2.7: can'... !=
  ("/tmp/tmpbUuV49/temp:1: 'cont...
  
  First differing element 0:
  
  /tmp/tmpbUuV49/temp:1: 'contraband' imported but unused
  
  
  + ("/tmp/tmpbUuV49/temp:1: 'contraband' imported but unused\n", '', 1)
  - ('',
  -  "/usr/bin/python2.7: can't open file
  
'/tmp/buildd/pyflakes-0.8.1/.pybuild/pythonX.Y_2.7/build/pyflakes/../bin/pyflakes':
  [Errno 2] No such file or directory\n",
  -  2)
  
  ==
  FAIL: When a Python source file is all good, the return code is zero
  and no
  --
  Traceback (most recent call last):
File

"/tmp/buildd/pyflakes-0.8.1/.pybuild/pythonX.Y_2.7/build/pyflakes/test/test_api.py",
line 561, in test_goodFile
  self.assertEqual(d, ('', '', 0))
  AssertionError: Tuples differ: ('', "/usr/bin/python2.7: can'... !=
  ('', '', 0)
  
  First differing element 1:
  /usr/bin/python2.7: can't open file
  
'/tmp/buildd/pyflakes-0.8.1/.pybuild/pythonX.Y_2.7/build/pyflakes/../bin/pyflakes':
  [Errno 2] No such file or directory
  
  
  
  + ('', '', 0)
  - ('',
  -  "/usr/bin/python2.7: can't open file
  
'/tmp/buildd/pyflakes-0.8.1/.pybuild/pythonX.Y_2.7/build/pyflakes/../bin/pyflakes':
  [Errno 2] No such file or directory\n",
  -  2)
  
  ==
  FAIL: If no arguments are passed to C{pyflakes} then it reads from
  stdin.
  --
  Traceback (most recent call last):
File

"/tmp/buildd/pyflakes-0.8.1/.pybuild/pythonX.Y_2.7/build/pyflakes/test/test_api.py",
line 591, in test_readFromStdin
  self.assertEqual(d, ("%s\n" % expected, '', 1))
  AssertionError: Tuples differ: ('', "/usr/bin/python2.7: can'... !=
  (":1: 'contraband' impo...
  
  First differing element 0:
  
  :1: 'contraband' imported but unused
  
  
  + (":1: 'contraband' imported but unused\n", '', 1)
  - ('',
  -  "/usr/bin/python2.7: can't open file
  
'/tmp/buildd/pyflakes-0.8.1/.pybuild/pythonX.Y_2.7/build/pyflakes/../bin/pyflakes':
  [Errno 2] No such file or directory\n",
  -  2)
  
  

Processed: Re: Bug#779482: severity of 779482 is grave

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://jogamp.org/bugzilla/show_bug.cgi?id=1246
Bug #779482 [libgluegen2-rt-java] support for powerpc, ppc64el and s390x not 
complete
Set Bug forwarded-to-address to 
'https://jogamp.org/bugzilla/show_bug.cgi?id=1246'.

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

Bug#801228: libopenjp2-7-dev should conflict with src:gdcm

[Mathieu Malaterre]

Package: gdcm
Version: 2.4.4-4
Severity: serious
Justification: FTBFS

One cannot compile gdcm when libopenjp2-7-dev is installed. Make sure
to add a Build-Conflict and/or fix the code upstream.

[ 61%] Building CXX object
Source/MediaStorageAndFileFormat/CMakeFiles/gdcmMSFF.dir/gdcmJPEG2000Codec.cxx.o
cd /tmp/gdcm-2.4.4/obj-x86_64-linux-gnu/Source/MediaStorageAndFileFormat
&& /usr/bin/c++   -DgdcmMSFF_EXPORTS -g -O2 -fstack-protector-strong
-Wformat -Werror=format-security -D_FORTIFY_SOURCE=2  -fPIC
-I/tmp/gdcm-2.4.4/Source/Common
-I/tmp/gdcm-2.4.4/obj-x86_64-linux-gnu/Source/Common
-I/tmp/gdcm-2.4.4/Source/DataStructureAndEncodingDefinition
-I/tmp/gdcm-2.4.4/Source/DataDictionary
-I/tmp/gdcm-2.4.4/Source/InformationObjectDefinition
-I/tmp/gdcm-2.4.4/Source/MediaStorageAndFileFormat
-I/tmp/gdcm-2.4.4/Utilities
-I/tmp/gdcm-2.4.4/obj-x86_64-linux-gnu/Utilities
-I/usr/include/openjpeg-2.1 -I/usr/include/json-c -I/usr/include/json
  -o CMakeFiles/gdcmMSFF.dir/gdcmJPEG2000Codec.cxx.o -c
/tmp/gdcm-2.4.4/Source/MediaStorageAndFileFormat/gdcmJPEG2000Codec.cxx
/tmp/gdcm-2.4.4/Source/MediaStorageAndFileFormat/gdcmJPEG2000Codec.cxx:
In function ‘void**
gdcm::opj_stream_create_memory_stream(gdcm::myfile*, OPJ_UINT32,
bool)’:
/tmp/gdcm-2.4.4/Source/MediaStorageAndFileFormat/gdcmJPEG2000Codec.cxx:193:42:
error: too few arguments to function ‘void
opj_stream_set_user_data(void**, void*, opj_stream_free_user_data_fn)’
   opj_stream_set_user_data(l_stream,p_mem);
  ^
In file included from /tmp/gdcm-2.4.4/Utilities/gdcm_openjpeg2.h:20:0,
 from
/tmp/gdcm-2.4.4/Source/MediaStorageAndFileFormat/gdcmJPEG2000Codec.cxx:29:
/usr/include/openjpeg-2.1/openjpeg.h:1154:27: note: declared here
 OPJ_API void OPJ_CALLCONV opj_stream_set_user_data (opj_stream_t*
p_stream, void * p_data, opj_stream_free_user_data_fn p_function);
   ^
/tmp/gdcm-2.4.4/Source/MediaStorageAndFileFormat/gdcmJPEG2000Codec.cxx:
In member function ‘std::pair
gdcm::JPEG2000Codec::DecodeByStreamsCommon(char*, size_t)’:
/tmp/gdcm-2.4.4/Source/MediaStorageAndFileFormat/gdcmJPEG2000Codec.cxx:465:35:
error: ‘CODEC_J2K’ was not declared in this scope
 dinfo = opj_create_decompress(CODEC_J2K);
   ^
/tmp/gdcm-2.4.4/Source/MediaStorageAndFileFormat/gdcmJPEG2000Codec.cxx:468:35:
error: ‘CODEC_JP2’ was not declared in this scope
 dinfo = opj_create_decompress(CODEC_JP2);
   ^
/tmp/gdcm-2.4.4/Source/MediaStorageAndFileFormat/gdcmJPEG2000Codec.cxx:509:46:
error: ‘J2K_STREAM_CHUNK_SIZE’ was not declared in this scope
   cio = opj_stream_create_memory_stream(fsrc,J2K_STREAM_CHUNK_SIZE, true);
  ^
/tmp/gdcm-2.4.4/Source/MediaStorageAndFileFormat/gdcmJPEG2000Codec.cxx:525:8:
error: invalid conversion from ‘opj_image_t** {aka opj_image**}’ to
‘void**’ [-fpermissive]
 cio);
^
/tmp/gdcm-2.4.4/Source/MediaStorageAndFileFormat/gdcmJPEG2000Codec.cxx:525:8:
error: cannot convert ‘OPJ_INT32* {aka int*}’ to ‘opj_image_t** {aka
opj_image**}’ for argument ‘3’ to ‘OPJ_BOOL opj_read_header(void**,
void**, opj_image_t**)’
/tmp/gdcm-2.4.4/Source/MediaStorageAndFileFormat/gdcmJPEG2000Codec.cxx:531:54:
error: ‘opj_get_reversible’ was not declared in this scope
   reversible = opj_get_reversible(dinfo,  );
  ^
/tmp/gdcm-2.4.4/Source/MediaStorageAndFileFormat/gdcmJPEG2000Codec.cxx:535:32:
error: too few arguments to function ‘OPJ_BOOL opj_decode(void**,
void**, opj_image_t*)’
   image = opj_decode(dinfo, cio);
^
In file included from /tmp/gdcm-2.4.4/Utilities/gdcm_openjpeg2.h:20:0,
 from
/tmp/gdcm-2.4.4/Source/MediaStorageAndFileFormat/gdcmJPEG2000Codec.cxx:29:
/usr/include/openjpeg-2.1/openjpeg.h:1299:31: note: declared here
 OPJ_API OPJ_BOOL OPJ_CALLCONV opj_decode(   opj_codec_t *p_decompressor,
   ^
/tmp/gdcm-2.4.4/Source/MediaStorageAndFileFormat/gdcmJPEG2000Codec.cxx:539:40:
error: ‘check_comp_valid’ was not declared in this scope
   if (!image || !check_comp_valid(image) )
^
/tmp/gdcm-2.4.4/Source/MediaStorageAndFileFormat/gdcmJPEG2000Codec.cxx:
In function ‘opj_image_t* gdcm::rawtoimage(char*, opj_cparameters_t*,
int, int, int, int, int, int, int, int, int)’:
/tmp/gdcm-2.4.4/Source/MediaStorageAndFileFormat/gdcmJPEG2000Codec.cxx:777:19:
error: ‘CLRSPC_GRAY’ was not declared in this scope
 color_space = CLRSPC_GRAY;
   ^
/tmp/gdcm-2.4.4/Source/MediaStorageAndFileFormat/gdcmJPEG2000Codec.cxx:782:19:
error: ‘CLRSPC_SRGB’ was not declared in this scope
 color_space = CLRSPC_SRGB;
   ^
/tmp/gdcm-2.4.4/Source/MediaStorageAndFileFormat/gdcmJPEG2000Codec.cxx:
In member function ‘bool
gdcm::JPEG2000Codec::CodeFrameIntoBuffer(char*, size_t, size_t&, const
char*, 

Bug#800617: marked as done (Fails to provide secrets)

[Debian Bug Tracking System]

Your message dated Wed, 07 Oct 2015 15:53:34 +
with message-id 
and subject line Bug#800617: fixed in gnome-keyring 3.18.0-2
has caused the Debian Bug report #800617,
regarding Fails to provide secrets
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.)


-- 
800617: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800617
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-keyring
Version: 3.18.0-1
Severity: grave

Since upgrading gnome-keyring from 3.16.0-4 to 3.18.0-1, applications
trying to retrieve secrets from gnome-keyring no longer can.  I see log
messages like the following:

Oct 01 10:36:37 jtriplet-mobl1 gnome-keyring-daemon[5801]: couldn't access 
control socket: /run/user/1000/keyring/control: No such file or directory
Oct 01 10:36:37 jtriplet-mobl1 gnome-session[5731]: ** Message: couldn't access 
control socket: /run/user/1000/keyring/control: No such file or directory
Oct 01 10:36:37 jtriplet-mobl1 gnome-keyring-daemon[5803]: couldn't access 
control socket: /run/user/1000/keyring/control: No such file or directory
Oct 01 10:36:37 jtriplet-mobl1 gnome-session[5731]: ** Message: couldn't access 
control socket: /run/user/1000/keyring/control: No such file or directory
[...]
Oct 01 10:36:38 jtriplet-mobl1 gnome-keyring-daemon[5808]: couldn't register in 
session: Timeout was reached
Oct 01 10:36:38 jtriplet-mobl1 gnome-keyring-daemon[5803]: couldn't communicate 
with already running daemon: Timeout was reached
Oct 01 10:36:38 jtriplet-mobl1 gnome-session[5731]: ** Message: couldn't 
communicate with already running daemon: Timeout was reached
Oct 01 10:36:38 jtriplet-mobl1 gnome-session[5731]: 
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Oct 01 10:36:39 jtriplet-mobl1 gnome-keyring-daemon[5844]: couldn't register in 
session: Timeout was reached
[...]
Oct 01 10:37:03 jtriplet-mobl1 gnome-keyring-daemon[5808]: couldn't request 
name 'org.freedesktop.secrets' on session bus: Timeout was reached
[...]
Oct 01 10:48:34 jtriplet-mobl1 org.gnome.evolution.dataserver.Sources4[5783]: 
server_side_source_credentials_lookup_cb: Failed to lookup password: Error 
calling StartServiceByName for org.freedesktop.secrets: Timeout was reached
Oct 01 10:48:35 jtriplet-mobl1 org.gnome.seahorse.Application[5783]: 
(seahorse:8293): seahorse-WARNING **: gkr-backend.vala:85: couldn't connect to 
secret service: Error calling StartServiceByName for org.freedesktop.secrets: 
Timeout was reached

In addition to that, it also looks like every time an application tries to
access the org.freedesktop.secrets service, dbus spawns an instance of
gnome-keyring with the --foreground option, likely based on
/usr/share/dbus-1/services/org.freedesktop.secrets.service ; does this conflict
with the instance already run via /etc/xdg/autostart?

- Josh Triplett

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

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

Versions of packages gnome-keyring depends on:
ii  dbus-x11 1.10.0-3
ii  dconf-gsettings-backend [gsettings-backend]  0.24.0-2
ii  gcr  3.16.0-1
ii  libc62.19-22
ii  libcap-ng0   0.7.7-1
ii  libcap2-bin  1:2.24-11
ii  libgck-1-0   3.16.0-1
ii  libgcr-base-3-1  3.16.0-1
ii  libgcrypt20  1.6.3-2
ii  libglib2.0-0 2.46.0-2
ii  p11-kit  0.23.1-3
ii  pinentry-gnome3  0.9.5-4

Versions of packages gnome-keyring recommends:
ii  libpam-gnome-keyring  3.18.0-1

gnome-keyring suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gnome-keyring
Source-Version: 3.18.0-2

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

Bug#799227: cloudprint: Uses obsolete "ClientLogin" protocol

[Dave Steele]

 See #800163  for
the Jessie update submission.

Bug#798049: marked as done (scantailor: Qt4 MOC parsing error on libboost1.58)

[Debian Bug Tracking System]

Your message dated Wed, 07 Oct 2015 15:57:41 +
with message-id 
and subject line Bug#798049: fixed in scantailor 0.9.11.1-4
has caused the Debian Bug report #798049,
regarding scantailor: Qt4 MOC parsing error on libboost1.58
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.)


-- 
798049: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798049
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: scantailor
Version: 0.9.11.1-3
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs

Like reproducible builds test building revealed, Scantailor currently FTBFS in 
Sid.

I'll get into this, soon.

DS

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

Kernel: Linux 4.1.0-1-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)

Versions of packages scantailor depends on:
ii  dpkg 1.18.2
ii  libc62.19-19
ii  libgcc1  1:5.1.1-14
ii  libjpeg62-turbo  1:1.4.1-2
ii  libpng12-0   1.2.50-2+b2
ii  libqt4-xml   4:4.8.7+dfsg-1
ii  libqtcore4   4:4.8.7+dfsg-1
ii  libqtgui44:4.8.7+dfsg-1
ii  libstdc++6   5.1.1-14
ii  libtiff5 4.0.3-13
ii  libxrender1  1:0.9.8-1+b1

scantailor recommends no packages.

scantailor suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: scantailor
Source-Version: 0.9.11.1-4

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

Debian distribution maintenance software
pp.
Daniel Stender  (supplier of updated scantailor 
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: Wed, 07 Oct 2015 17:09:47 +0200
Source: scantailor
Binary: scantailor
Architecture: source amd64
Version: 0.9.11.1-4
Distribution: unstable
Urgency: medium
Maintainer: Daniel Stender 
Changed-By: Daniel Stender 
Description:
 scantailor - interactive post-processing tool for scanned pages
Closes: 798049
Changes:
 scantailor (0.9.11.1-4) unstable; urgency=medium
 .
   * Added fix-qt4-parsing-error-on-libboost.patch (Closes: #798049)
   * deb/control: added libboost-dev to build-deps.
Checksums-Sha1:
 320fd1230ee068b4142ab4af4e0f01f812d92f26 2041 scantailor_0.9.11.1-4.dsc
 80970bbcd65fbf8bc62c0ff0cb7bcb78c86961c3 1190198 
scantailor_0.9.11.1.orig.tar.gz
 06e70db949fc0c99bfb3d8d4dfde057aa9ea0e11 11608 
scantailor_0.9.11.1-4.debian.tar.xz
 863d80cb882c81e3892da0e1956aa39020142d02 1367486 
scantailor_0.9.11.1-4_amd64.deb
Checksums-Sha256:
 7e9530b1175b4d5ab57471ab76e489871b6f710d1945aebda92fb64d163028f8 2041 
scantailor_0.9.11.1-4.dsc
 881647a4172c55a067a7b6687965441cf21176d79d93075b22a373ea9accd8d3 1190198 
scantailor_0.9.11.1.orig.tar.gz
 fa7c86bc47f3a4aee8ba9fce816c98f7582392f902f3ff01fb39a6306cefbc99 11608 
scantailor_0.9.11.1-4.debian.tar.xz
 c7119a17b1be9db54d16864b2796afc456abfef910e603e8d694900c1f9ff467 1367486 
scantailor_0.9.11.1-4_amd64.deb
Files:
 13c46e49b3a6537f6b56a5e06fe21e10 2041 graphics optional 
scantailor_0.9.11.1-4.dsc
 6cdca1b6d1dafd022ea94b4800dad340 1190198 graphics optional 
scantailor_0.9.11.1.orig.tar.gz
 4355ff09f119e5cc05bf3685038277ae 11608 graphics optional 
scantailor_0.9.11.1-4.debian.tar.xz
 fe5eafff825598c65aa8d19f1f6c305e 1367486 graphics optional 
scantailor_0.9.11.1-4_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIbBAEBCgAGBQJWFTl7AAoJEBXgmvTfUYLIh9UP+LfbGthnwCo0pYzZlFwxEJ9v
UBEnpBX2CCy5apEmKtLhfqfq6JtwEazdLQm3ujJsCvTYxGAPXb+nmiRGS/RGUOOn
EGCOIM2ZtFk2ucLdjadeArS76Rqx7xGGUxBPPQfOni/Qywexr2EZCxJSgLPOO07I
hZuPP3WNj29+OLOhg6UXgEri/XFxgkTvlcGqhhQm2Y8HRht3rg/X5kxDPwPghXUN
X71/+GR7vsx1TMawbyxBR+/rjdRWpNKtnQL1dTp1yCW8GijqiI5XAEem2pO74NGh
dj78xv8Z5NZWhfCBDiYPSx4O8ONnVFr1zlFslsBvwWR/cpiq8xbJXNoBfFh3D4yd

Bug#779482: severity of 779482 is grave

[Markus Koschany]

Control: forwarded -1 https://jogamp.org/bugzilla/show_bug.cgi?id=1246

On Tue, 06 Oct 2015 23:53:17 +0200 Gilles Filippini  wrote:
> For the record, I've pinged upstream and proposed a patch for ppc64el.
> The good news is they seem responsive [1].
> 
> [1] 
> 
> Unfortunately I couldn't test the usability of my patch yet, because I
> didn't succeed with remote X display on ppc64el porterboxes :/
> 

Thank you for contacting upstream and offering a patch. If your patch
gets accepted, we can resolve this issue by packaging the next upstream
release. Should this not happen for whatever reasons, we can still
remove ppc64el from the list of supported architectures.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#798924: /usr/lib/x86_64-linux-gnu/jni/libatk-wrapper.so.6.0.0: SIGSEGV on Netbeans startup

[Alexandre Pereira Nunes]

Package: libatk-wrapper-java
Followup-For: Bug #798924

I'm attaching an additional patch that complements the old netbeans one.
With this, I can now open netbeans.


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

Kernel: Linux 4.2.1 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages libatk-wrapper-java depends on:
ii  x11-utils  7.7+3

Versions of packages libatk-wrapper-java recommends:
ii  libatk-wrapper-java-jni  0.33.3-1.1

libatk-wrapper-java suggests no packages.

-- no debconf information
Index: java-atk-wrapper-0.33.3/jni/src/AtkWrapper.c
===
--- java-atk-wrapper-0.33.3.orig/jni/src/AtkWrapper.c
+++ java-atk-wrapper-0.33.3/jni/src/AtkWrapper.c
@@ -258,6 +258,11 @@ JNICALL Java_org_GNOME_Accessibility_Atk
 jobject jAccContext)
 {
   jobject global_ac = (*jniEnv)->NewGlobalRef(jniEnv, jAccContext);
+  if (!global_ac) {
+   if (jaw_debug)
+ g_warning("%s: global_ac == NULL", __func__);
+   return;
+  }
   CallbackPara *para = alloc_callback_para(global_ac);
   gdk_threads_add_idle(focus_notify_handler, para);
 }
@@ -335,6 +340,11 @@ JNICALL Java_org_GNOME_Accessibility_Atk
 {
 
   jobject global_ac = (*jniEnv)->NewGlobalRef(jniEnv, jAccContext);
+  if (!global_ac) {
+ if (jaw_debug)
+ g_warning("%s: global_ac == NULL", __func__);
+   return;
+  } 
   CallbackPara *para = alloc_callback_para(global_ac);
   para->is_toplevel = (jIsToplevel == JNI_TRUE) ? TRUE : FALSE;
   gdk_threads_add_idle(window_open_handler, para);
@@ -412,6 +422,11 @@ JNICALL Java_org_GNOME_Accessibility_Atk
 jboolean jIsToplevel)
 {
   jobject global_ac = (*jniEnv)->NewGlobalRef(jniEnv, jAccContext);
+  if (!global_ac) {
+ if (jaw_debug)
+ g_warning("%s: global_ac == NULL", __func__);
+   return;
+  }
   CallbackPara *para = alloc_callback_para(global_ac);
   para->is_toplevel = (jIsToplevel == JNI_TRUE) ? TRUE : FALSE;
   gdk_threads_add_idle(window_close_handler, para);
@@ -462,6 +477,11 @@ JNICALL Java_org_GNOME_Accessibility_Atk
jobject jAccContext)
 {
   jobject global_ac = (*jniEnv)->NewGlobalRef(jniEnv, jAccContext);
+  if (!global_ac) {
+ if (jaw_debug)
+ g_warning("%s: global_ac == NULL", __func__);
+   return;
+  }
   CallbackPara *para = alloc_callback_para(global_ac);
   gdk_threads_add_idle(window_minimize_handler, para);
 }
@@ -511,6 +531,11 @@ JNIEXPORT void JNICALL Java_org_GNOME_Ac
   jobject jAccContext)
 {
   jobject global_ac = (*jniEnv)->NewGlobalRef(jniEnv, jAccContext);
+  if (!global_ac) {
+ if (jaw_debug)
+ g_warning("%s: global_ac == NULL", __func__);
+   return;
+  }
   CallbackPara *para = alloc_callback_para(global_ac );
   gdk_threads_add_idle(window_maximize_handler, para);
 }
@@ -561,6 +586,11 @@ JNIEXPORT void JNICALL Java_org_GNOME_Ac
 {
 
   jobject global_ac = (*jniEnv)->NewGlobalRef(jniEnv, jAccContext);
+  if (!global_ac) {
+ if (jaw_debug)
+ g_warning("%s: global_ac == NULL", __func__);
+   return;
+  }
   CallbackPara *para = alloc_callback_para(global_ac);
   gdk_threads_add_idle(window_restore_handler, para);
 }
@@ -609,6 +639,11 @@ JNIEXPORT void JNICALL Java_org_GNOME_Ac
   jobject jAccContext) {
 
   jobject global_ac = (*jniEnv)->NewGlobalRef(jniEnv, jAccContext);
+  if (!global_ac) {
+ if (jaw_debug)
+ g_warning("%s: global_ac == NULL", __func__);
+   return;
+  }
   CallbackPara *para = alloc_callback_para(global_ac);
   gdk_threads_add_idle(window_activate_handler, para);
 }
@@ -659,6 +694,11 @@ JNICALL Java_org_GNOME_Accessibility_Atk
 {
 
   jobject global_ac = (*jniEnv)->NewGlobalRef(jniEnv, jAccContext);
+  if (!global_ac) {
+ if (jaw_debug)
+ g_warning("%s: global_ac == NULL", __func__);
+   return;
+  }
   CallbackPara *para = alloc_callback_para(global_ac);
   gdk_threads_add_idle(window_deactivate_handler, para);
 }
@@ -710,6 +750,11 @@ JNICALL Java_org_GNOME_Accessibility_Atk
 {
 
   jobject global_ac = (*jniEnv)->NewGlobalRef(jniEnv, jAccContext);
+  if (!global_ac) {
+ if (jaw_debug)
+ g_warning("%s: global_ac == NULL", __func__);
+   return;
+  }
   CallbackPara *para = alloc_callback_para(global_ac);
   gdk_threads_add_idle(window_state_change_handler, para);
 }
@@ -1044,6 +1089,11 @@ JNICALL Java_org_GNOME_Accessibility_Atk
jobjectArray args)