Processed: found 832908 in 1:2.4.10-5

[Debian Bug Tracking System]

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

> # add missing epoch
> found 832908 1:2.4.10-5
Bug #832908 {Done: Laszlo Boszormenyi (GCS) } 
[mongodb-clients] mongodb: CVE-2016-6494: world-readable .dbshell history file
Marked as found in versions mongodb/1:2.4.10-5.
> thanks
Stopping processing here.

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

Bug#833937: [icedove] regression: Very frequent segfaults

[Carsten Schoenert]

Am 10.08.2016 um 18:18 schrieb Philipp Klaus Krause:
[...]
>> 833532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833532
>> 833591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833591
>> 833635: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833635
> 
> These bug reports are about a segfault on startup. My segfaul thappens
> later.
> 
>> 833698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833698
> 
> This bug report is about a segfault on the first read from IMAP folders.
> My segfaul thappens later.
> 
>> 833864: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833864
>>
> 
> This bug report is about a segfault that happens deterministically upon
> some user action. My segfault seems to happens independent of user action.
[...]

And there is no other report that fits your regression? I won't believe
this.

I count 8 bugs with segfaults about Icedove >= 45.1.0

https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=id-crash-45.1.0;users=c.schoen...@t-online.de

If all those reports don't correlate your issue than reopen this report
and please create a gdb log with some explanation why other bug reports
aren't the same.
Try to take make a look from my/our side. We have over 200 bug reports
with various things. Every new report with a existing issue is just
taking times from real fixing issues as we need to go to every single
report and collect identical reports and prepare merging and fixing.
There is reason why reportbug is showing existing bug reports right
after the start.

-- 
Regards
Carsten Schoenert

Bug#833698: Icedove 1:45.2.0-2+b1 (Debian Testing) SegFault

[John Talbut]

On Tue, 09 Aug 2016 22:48:00 + =?UTF-8?B?VmlrdG9yIErDpGdlcnNrw7xwcGVy?=
  wrote:

Everybody who reads only this bug report, please consider my workaround
mentioned in bug 833532:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833532#50

Thanks Viktor.  I have set "javascript.options.baselinejit" to "false" 
and icedove is now working.

Bug#833934: workaround

[Kyle Bentley]

>From the other merged threads, setting

javascript.options.baselinejit = false

seems to be a useful workaround until the patch comes out.

Bug#833419: crashes computer

[積丹尼 Dan Jacobson]

severity 833419 normal
retitle 833419 midori gives black screen on one of my couputers
thanks

OK I installed
https://wiki.debian.org/NvidiaGraphicsDrivers
# nvidia-detect
Detected NVIDIA GPUs:
00:05.0 VGA compatible controller [0300]: NVIDIA Corporation C51G [GeForce 
6100] [10de:0242] (rev a2)
Checking card:  NVIDIA Corporation C51G [GeForce 6100] (rev a2)
Your card is only supported up to the 304 legacy drivers series.
It is recommended to install the
nvidia-legacy-304xx-driver
package.

and now everything is OK for my machine with the NVIDIA card. But that
still leaves my Thinkpad r50e with the problem.

Processed: Re: Bug#833419: crashes computer

[Debian Bug Tracking System]

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

> severity 833419 normal
Bug #833419 [midori] freezes screen requiring powering off of the computer
Severity set to 'normal' from 'grave'
> retitle 833419 midori gives black screen on one of my couputers
Bug #833419 [midori] freezes screen requiring powering off of the computer
Changed Bug title to 'midori gives black screen on one of my couputers' from 
'freezes screen requiring powering off of the computer'.
> thanks
Stopping processing here.

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

Processed: tagging 833797

[Debian Bug Tracking System]

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

> tags 833797 + patch
Bug #833797 [src:cegui-mk2] cegui-mk2: FTBFS with Boost 1.61
Ignoring request to alter tags of bug #833797 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: [/master] remove-msse4.2.patch: Backport upstream commit removing -msse4.2 commandline option from configure script (Closes: #833944)

[Debian Bug Tracking System]

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

> tag 833944 pending
Bug #833944 {Done: Andrew Starr-Bochicchio } 
[src:libtorrent-rasterbar] libtorrent-rasterbar: FTBFS on *i386: Boost.Chrono 
library not found.
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: [/master] Fix builds on arches where the multiarch tuple (i386-*) and the GNU tuple (i686-*) differ (Closes: #833944).

[Debian Bug Tracking System]

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

> tag 833944 pending
Bug #833944 {Done: Andrew Starr-Bochicchio } 
[src:libtorrent-rasterbar] libtorrent-rasterbar: FTBFS on *i386: Boost.Chrono 
library not found.
Ignoring request to alter tags of bug #833944 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: fixed 833943 in 1.1.0-2

[Debian Bug Tracking System]

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

> fixed 833943 1.1.0-2
Bug #833943 [src:libtorrent-rasterbar] libtorrent-rasterbar: FTBFS on non-x86: 
-msse4.2 unrecognized
Marked as fixed in versions libtorrent-rasterbar/1.1.0-2.
> thanks
Stopping processing here.

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

Bug#833944: [/master] Fix builds on arches where the multiarch tuple (i386-*) and the GNU tuple (i686-*) differ (Closes: #833944).

[Andrew Starr-Bochicchio]

tag 833944 pending
thanks

Date: Wed Aug 10 20:12:37 2016 -0400
Author: Andrew Starr-Bochicchio 
Commit ID: bbcec1e57452e40864b6300644d04ae56c25f752
Commit URL: 
http://anonscm.debian.org/gitweb/?p=collab-maint/libtorrent-rasterbar.git;a=commitdiff;h=bbcec1e57452e40864b6300644d04ae56c25f752
Patch URL: 
http://anonscm.debian.org/gitweb/?p=collab-maint/libtorrent-rasterbar.git;a=commitdiff_plain;h=bbcec1e57452e40864b6300644d04ae56c25f752

Fix builds on arches where the multiarch tuple (i386-*) and the GNU tuple 
(i686-*) differ (Closes: #833944).

  

Bug#833944: [/master] remove-msse4.2.patch: Backport upstream commit removing -msse4.2 commandline option from configure script (Closes: #833944)

[Andrew Starr-Bochicchio]

tag 833944 pending
thanks

Date: Wed Aug 10 20:23:24 2016 -0400
Author: Andrew Starr-Bochicchio 
Commit ID: 4f361f8226d2169596de53fbc37c173f361bdf03
Commit URL: 
http://anonscm.debian.org/gitweb/?p=collab-maint/libtorrent-rasterbar.git;a=commitdiff;h=4f361f8226d2169596de53fbc37c173f361bdf03
Patch URL: 
http://anonscm.debian.org/gitweb/?p=collab-maint/libtorrent-rasterbar.git;a=commitdiff_plain;h=4f361f8226d2169596de53fbc37c173f361bdf03

remove-msse4.2.patch: Backport upstream commit removing -msse4.2 
commandline option from configure script (Closes: #833944)

  

Bug#833944: marked as done (libtorrent-rasterbar: FTBFS on *i386: Boost.Chrono library not found.)

[Debian Bug Tracking System]

Your message dated Thu, 11 Aug 2016 01:21:45 +
with message-id 
and subject line Bug#833944: fixed in libtorrent-rasterbar 1.1.0-2
has caused the Debian Bug report #833944,
regarding libtorrent-rasterbar: FTBFS on *i386: Boost.Chrono library 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.)


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

Builds of libtorrent-rasterbar for i386, hurd-i386, and kfreebsd-i386
all failed:

  Checking for boost libraries:
  checking for boostlib >= 1.47... yes
  checking whether the Boost::System library is available... yes
  checking for exit in -lboost_system... yes
  checking whether the Boost::Chrono library is available... yes
  configure: error: Boost.Chrono library not found. Try using 
--with-boost-chrono=lib

The issue appears to be that the build-system logic to figure out what
library name to use is looking in the wrong directory on these
architectures, on which the multiarch tuple (i386-*) and the GNU tuple
(i686-*) differ.  Please try passing

  --with-boost-libdir=/usr/lib/$(DEB_HOST_MULTIARCH)

or setting the library name explicitly, as already done for Boost.System.
(In the latter case, I strongly suspect you'll need to do the same for
Boost.Random too.)

Could you please take a look?

Thanks!
--- End Message ---
--- Begin Message ---
Source: libtorrent-rasterbar
Source-Version: 1.1.0-2

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

Debian distribution maintenance software
pp.
Andrew Starr-Bochicchio  (supplier of updated 
libtorrent-rasterbar 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, 10 Aug 2016 20:23:29 -0400
Source: libtorrent-rasterbar
Binary: libtorrent-rasterbar9 libtorrent-rasterbar-dev libtorrent-rasterbar-dbg 
libtorrent-rasterbar-doc python-libtorrent python-libtorrent-dbg 
python3-libtorrent python3-libtorrent-dbg
Architecture: source i386 all
Version: 1.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Cristian Greco 
Changed-By: Andrew Starr-Bochicchio 
Description:
 libtorrent-rasterbar-dbg - Debug symbols for libtorrent-rasterbar
 libtorrent-rasterbar-dev - Development files for libtorrent-rasterbar
 libtorrent-rasterbar-doc - Documentation for libtorrent-rasterbar
 libtorrent-rasterbar9 - C++ bittorrent library by Rasterbar Software
 python-libtorrent - Python bindings for libtorrent-rasterbar
 python-libtorrent-dbg - Python bindings for libtorrent-rasterbar (debug 
symbols)
 python3-libtorrent - Python bindings for libtorrent-rasterbar (Python 3)
 python3-libtorrent-dbg - Python bindings for libtorrent-rasterbar (debug 
symbols) (Python
Closes: 833944
Changes:
 libtorrent-rasterbar (1.1.0-2) unstable; urgency=medium
 .
   * Fix builds on arches where the multiarch tuple (i386-*) and
 the GNU tuple (i686-*) differ (Closes: #833944).
   * remove-msse4.2.patch: Backport upstream commit removing
 -msse4.2 commandline option from configure script (Closes: #833944)
Checksums-Sha1:
 b1d28882b0fc2634d0efb974ba8138e3abeb 2845 libtorrent-rasterbar_1.1.0-2.dsc
 5ce8b13a53c1ebfecbc475b327b0fd52c879afa8 16156 
libtorrent-rasterbar_1.1.0-2.debian.tar.xz
 7ad5e9aa00934892b3a7c4703e36ed5e3487f4c8 32754330 
libtorrent-rasterbar-dbg_1.1.0-2_i386.deb
 66e79689f6ee5e9e7b2eb1d9a469f05e08876d17 2137720 
libtorrent-rasterbar-dev_1.1.0-2_i386.deb
 4c3741c95d3e61e4437c1972ce55ef83fd290f22 1537234 
libtorrent-rasterbar-doc_1.1.0-2_all.deb
 e2ee366d88b57f8a6b704f6a87c0e515755d025f 1367906 
libtorrent-rasterbar9_1.1.0-2_i386.deb
 45f42b6aee802a51c0bf35e40d93a824beaa5aec 332342 
python-libtorrent-dbg_1.1.0-2_i386.deb
 0ee555191337fb0b119ddc81e9460d728688573a 307400 
python-libtorrent_1.1.0-2_i386.deb
 

Processed: tagging 833797

[Debian Bug Tracking System]

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

> tags 833797 + patch
Bug #833797 [src:cegui-mk2] cegui-mk2: FTBFS with Boost 1.61
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#811965: libqt4pas: FTBFS with GCC 6: symbol changes

[Matthias Klumpp]

2016-08-10 21:26 GMT+02:00 Paul Gevers :
> Control: owner -1 !
>
> Just so it is known, I started on updating the symbols file. However I
> need my access to debomatic renewed to be able to check what I did for
> amd64 and armhf and to learn what to update for the other archs.

Oh damn, sorry, I just read your mail...
I was already working on this thing - thy way I usually do it (and
which is also the way the symbols stuff is handled with KDE
libraries)[1] is to upload a dummy package containing the
locally-fixed symbols file, and then use the build output to fix up
the symbols file for all architectures the package builds on.
I am currently waiting for the package to get built on all
architectures (both the archive and builders are really slow at
time...), then the next upload will close this bug report.

Sorry for not stating that I am working on this way earlier (that's
probably the sideeffect of just recently moving this over to Pascal
team maintenance).

Cheers,
Matthias

[1]: https://pkg-kde.alioth.debian.org/symbolfiles.html

Bug#821181: jruby: FTBFS due to PsychParser class error

[Emmanuel Bourg]

Le 23/04/2016 à 15:17, Miguel Landaeta a écrit :

> It turns out I was responsible for the second bug. When I updated yecht
> 1.1-1, the updated .jar file is now dropping a class in the default package
> (YechtService.class).
> 
> That doesn't work with maven-bundle-plugin.

I got a look at the maven-bundle-plugin issue. I haven't been able to
find a plugin configuration that works, but I tested different versions
of the bundle plugin and the versions > 3 do not fail with the error
"The default package '.' is not permitted by the Import-Package syntax".

I was a bit reluctant to upgrade again bnd and maven-bundle-plugin for
stretch but we have a good reason to do it now.

Emmanuel Bourg

Bug#813949: bluetooth: error causing service to be unusable: Not enough free handles to register service

[Alban Browaeys]

Try enabling experimental features from bluetoothd :
that is modify
  /lib/systemd/system/bluetooth.service
to have:
  ExecStart=/usr/lib/bluetooth/bluetoothd -E
instead of:
  ExecStart=/usr/lib/bluetooth/bluetoothd

then:
 sudo systemctl daemon-reload
and:
 sudo systemctl restart bluetooth.service

This fixed the :

Feb 06 15:47:43 servo bluetoothd[801]: Not enough free handles to register 
service
Feb 06 15:47:43 servo bluetoothd[801]: Error adding Link Loss service
Feb 06 15:47:43 servo bluetoothd[801]: Not enough free handles to register 
service
Feb 06 15:47:43 servo bluetoothd[801]: Not enough free handles to register 
service
Feb 06 15:47:43 servo bluetoothd[801]: Not enough free handles to register 
service
Feb 06 15:47:43 servo bluetoothd[801]: Current Time Service could not be 
registered
Feb 06 15:47:43 servo bluetoothd[801]: gatt-time-server: Input/output error (5)
Feb 06 15:47:43 servo bluetoothd[801]: Not enough free handles to register 
service
Feb 06 15:47:43 servo bluetoothd[801]: Not enough free handles to register 
service
Feb 06 15:47:43 servo bluetoothd[801]: Sap driver initialization failed.
Feb 06 15:47:43 servo bluetoothd[801]: sap-server: Operation not permitted (1)

side of the issue (that is "gatt" issues)

but left:
Feb 06 15:47:43 servo bluetoothd[801]: Failed to obtain handles for "Service 
Changed" characteristic

PS: my local issue was not related to those errors YMMV.
The -E flag clue for GATT is from https://bugs.launchpad.net/ubuntu/+so
urce/bluez/+bug/1546603 


NB: you might also add "-d" to enable debugging output .
if nothing obvious shows up , "sudo btmon" output while running the
bluetooth commands will help further.


Cheers
Alban

Bug#831935: libjs-swfobject: FTBFS with dpkg-buildpackage -A: dh_install: missing files, aborting

[Christian Welzel]

Am 23.07.2016 um 13:15 schrieb Santiago Vila:


Patch attached.


I prepared a new package. This can be found on mentors, because i cannot
upload myself. You can find it here:

https://mentors.debian.net/debian/pool/main/libj/libjs-swfobject/libjs-swfobject_2.2+dfsg-2.dsc

--
 MfG, Christian Welzel

  GPG-Key: pub 4096R/5117E119 2011-09-19
  Fingerprint: 3688 337C 0D3E 3725 94EC  E401 8D52 CDE9 5117 E119

Bug#833923: gb cython_0.24.1-1 . s390x .

[Yaroslav Halchenko]

On Wed, 10 Aug 2016, Jakub Wilk wrote:

> * Andreas Tille , 2016-08-10, 14:15:
> >Failed example:
> >   long_double_to_float_int(4.1)
> >Expected:
> >   4.0
> >Got:
> >   0.0

> I couldn't reproduce this on zelenka.d.o. The package built successfully.

> Also, the code this test exercises is pretty straightforward, so I don't
> know what could go wrong here. Perhaps it was a toolchain bug that was fixed
> in the mean time?

Thanks Jakub, let's try to build it again I guess (thus this email to
give back). Dear wb-team, please

gb cython_0.24.1-1 . s390x .

in the hope that it would build fine this time.

-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik


signature.asc
Description: Digital signature

Bug#811965: libqt4pas: FTBFS with GCC 6: symbol changes

[Paul Gevers]

Control: owner -1 !

Just so it is known, I started on updating the symbols file. However I
need my access to debomatic renewed to be able to check what I did for
amd64 and armhf and to learn what to update for the other archs.

Paul



signature.asc
Description: OpenPGP digital signature

Processed: Re: libqt4pas: FTBFS with GCC 6: symbol changes

[Debian Bug Tracking System]

Processing control commands:

> owner -1 !
Bug #811965 [src:libqtpas] libqt4pas: FTBFS with GCC 6: symbol changes
Bug #831168 [src:libqtpas] libqtpas: FTBFS with GCC 6: dh_makeshlibs: failing 
due to earlier errors
Owner recorded as Paul Gevers .
Owner recorded as Paul Gevers .

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

Bug#833000: [Pkg-freeipa-devel] Bug#833000: python-kdcproxy: FTBFS: TypeError: unsupported operand type(s) for -=: 'Retry' and 'int'

[Timo Aaltonen]

On 30.07.2016 20:12, Chris West (Faux) wrote:
> Source: python-kdcproxy
> Version: 0.3.2-3
> 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 without networking (policy 4.9), and has an 
> exciting
> secondary failure.

Is it possible to replicate this build with sbuild? I guess setting
http_proxy like on #830629 might work, but have no way to test it.


-- 
t

Bug#811838: marked as done (esys-particle: FTBFS with GCC 6: no match for)

[Debian Bug Tracking System]

Your message dated Wed, 10 Aug 2016 19:03:41 +
with message-id 
and subject line Bug#811838: fixed in esys-particle 2.3.4+dfsg1-1
has caused the Debian Bug report #811838,
regarding esys-particle: FTBFS with GCC 6: no match for
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.)


-- 
811838: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811838
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: esys-particle
Version: 2.3.3+dfsg1-1
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-no-match

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

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

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

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> mpicxx -DHAVE_CONFIG_H -I. -I../..  "-I../.." -I/usr/include 
> -I../../Foundation -I../../Geometry -Wdate-time -D_FORTIFY_SOURCE=2  -Wall -g 
> -O2 -fstack-protector-strong -Wformat -Werror=format-security -c -o 
> frame_vtk.o frame_vtk.cpp
> frame_vtk.cpp: In function 'void do_single_frame_sliced_vtk_r(const string&, 
> const string&, int, bool, const string&, double, double)':
> frame_vtk.cpp:1125:8: warning: unused variable 'hasMeshBondedInteractions' 
> [-Wunused-variable]
>bool hasMeshBondedInteractions=false;
> ^
> 
> frame_vtk.cpp: In function 'void writeMeshFile(const string&, const string&, 
> int)':
> frame_vtk.cpp:1279:29: error: no match for 'operator!=' (operand types are 
> 'std::basic_istream' and 'long int')
>while (datafile >> header != NULL){
>   ~~~^~~~
> 
> frame_vtk.cpp:1279:29: note: candidate: operator!=(int, long int) 
> frame_vtk.cpp:1279:29: note:   no known conversion for argument 1 from 
> 'std::basic_istream' to 'int'
> In file included from /usr/include/c++/6/bits/stl_algobase.h:64:0,
>  from /usr/include/c++/6/bits/char_traits.h:39,
>  from /usr/include/c++/6/string:40,
>  from frame_vtk.h:17,
>  from frame_vtk.cpp:13:
> /usr/include/c++/6/bits/stl_pair.h:357:5: note: candidate: template _T1, class _T2> constexpr bool std::operator!=(const std::pair<_T1, _T2>&, 
> const std::pair<_T1, _T2>&)
>  operator!=(const pair<_T1, _T2>& __x, const pair<_T1, _T2>& __y)
>  ^~~~
> 
> /usr/include/c++/6/bits/stl_pair.h:357:5: note:   template argument 
> deduction/substitution failed:
> In file included from /usr/include/string.h:32:0,
>  from /usr/include/c++/6/cstring:42,
>  from /usr/include/boost/filesystem/path.hpp:36,
>  from /usr/include/boost/filesystem.hpp:16,
>  from frame_vtk.cpp:28:
> frame_vtk.cpp:1279:32: note:   'std::basic_istream' is not derived from 
> 'const std::pair<_T1, _T2>'
>while (datafile >> header != NULL){
> ^
> 
> In file included from /usr/include/c++/6/bits/stl_algobase.h:67:0,
>  from /usr/include/c++/6/bits/char_traits.h:39,
>  from /usr/include/c++/6/string:40,
>  from frame_vtk.h:17,
>  from frame_vtk.cpp:13:
> /usr/include/c++/6/bits/stl_iterator.h:304:5: note: candidate: template _Iterator> bool std::operator!=(const std::reverse_iterator<_Iterator>&, 
> const std::reverse_iterator<_Iterator>&)
>  operator!=(const reverse_iterator<_Iterator>& __x,
>  ^~~~
> 
> /usr/include/c++/6/bits/stl_iterator.h:304:5: note:   template argument 
> deduction/substitution failed:
> In file included from /usr/include/string.h:32:0,
>  from /usr/include/c++/6/cstring:42,
>  from /usr/include/boost/filesystem/path.hpp:36,
>  from /usr/include/boost/filesystem.hpp:16,
>  from frame_vtk.cpp:28:
> frame_vtk.cpp:1279:32: note:   'std::basic_istream' is not derived from 
> 'const std::reverse_iterator<_Iterator>'
>while (datafile >> header != NULL){
> ^
> 
> In file included from /usr/include/c++/6/bits/stl_algobase.h:67:0,
>  from /usr/include/c++/6/bits/char_traits.h:39,
>  from /usr/include/c++/6/string:40,
>  from frame_vtk.h:17,
>  

Bug#833923: cython: FTBFS on s390x

[Jakub Wilk]

* Andreas Tille , 2016-08-10, 14:15:

Failed example:
   long_double_to_float_int(4.1)
Expected:
   4.0
Got:
   0.0


I couldn't reproduce this on zelenka.d.o. The package built 
successfully.


Also, the code this test exercises is pretty straightforward, so I don't 
know what could go wrong here. Perhaps it was a toolchain bug that was 
fixed in the mean time?


--
Jakub Wilk

Bug#833950: libasound2: brltty-espeak stops working with 1.1.2-1

[Sebastian Humenda]

Package: libasound2
Version: 1.1.2
Severity: serious
Tags: patch
Justification: breaks system for blind users [RC, stretch]

After an upgrade to the specified version, BRLTTY starts up with speech working
(brltty-espeak is using libao -> libasoun2), but speech stops working after
roughly a minute. The BRLTTY process is still running, but speech cannot be
brought back, only a restart of BRLTTY fixes this issue. All other playback of
sound using ALSA works fine. Since it is not related to any changes in BRLTTY
(tried several stable versions), the issue must be in libasound2. The provided
patch fixes the issue reliably for me.


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

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

Content-Type: text/x-diff; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="patch"

--- ./src/pcm/pcm.c.orig	2016-08-10 19:39:59.881564371 +0200
+++ ./src/pcm/pcm.c	2016-08-10 19:40:04.211539997 +0200
@@ -2544,6 +2544,7 @@
 	pcm->fast_op_arg = pcm;
 	INIT_LIST_HEAD(>async_handlers);
 #ifdef THREAD_SAFE_API
+	pcm->thread_safe = 1;
 	pthread_mutex_init(>lock, NULL);
 	{
 		static int default_thread_safe = -1;

Processed: tagging 832842

[Debian Bug Tracking System]

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

> tags 832842 + pending
Bug #832842 [src:findbugs] findbugs: FTBFS: [javac] 
/«PKGBUILDDIR»/src/java/edu/umd/cs/findbugs/StackMapAnalyzer.java:39: error: 
cannot find symbol
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: retitle 760853 to jitsi uninstallable

[Debian Bug Tracking System]

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

> retitle 760853 jitsi uninstallable
Bug #760853 [jitsi] jitsi uninstallable in sid
Bug #779521 [jitsi] jitsi: Unable to install on sid/unstable
Bug #779522 [jitsi] jitsi: Unable to install on sid/unstable
Bug #789038 [jitsi] jitsi: Unable to install on sid/unstable
Bug #831232 [jitsi] jitsi: FTBFS: unsatisfiable build-dependencies: libjitsi, 
libjitsi-jni, libphonenumber6-java
Bug #833902 [jitsi] jitsi: unable to install jitsi on Debian testing
Changed Bug title to 'jitsi uninstallable' from 'jitsi uninstallable in sid'.
Changed Bug title to 'jitsi uninstallable' from 'jitsi: Unable to install on 
sid/unstable'.
Changed Bug title to 'jitsi uninstallable' from 'jitsi: Unable to install on 
sid/unstable'.
Changed Bug title to 'jitsi uninstallable' from 'jitsi: Unable to install on 
sid/unstable'.
Changed Bug title to 'jitsi uninstallable' from 'jitsi: FTBFS: unsatisfiable 
build-dependencies: libjitsi, libjitsi-jni, libphonenumber6-java'.
Changed Bug title to 'jitsi uninstallable' from 'jitsi: unable to install jitsi 
on Debian testing'.
> thanks
Stopping processing here.

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

Bug#833944: libtorrent-rasterbar: FTBFS on *i386: Boost.Chrono library not found.

[Aaron M. Ucko]

Source: libtorrent-rasterbar
Version: 1.0.7-1+b2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Builds of libtorrent-rasterbar for i386, hurd-i386, and kfreebsd-i386
all failed:

  Checking for boost libraries:
  checking for boostlib >= 1.47... yes
  checking whether the Boost::System library is available... yes
  checking for exit in -lboost_system... yes
  checking whether the Boost::Chrono library is available... yes
  configure: error: Boost.Chrono library not found. Try using 
--with-boost-chrono=lib

The issue appears to be that the build-system logic to figure out what
library name to use is looking in the wrong directory on these
architectures, on which the multiarch tuple (i386-*) and the GNU tuple
(i686-*) differ.  Please try passing

  --with-boost-libdir=/usr/lib/$(DEB_HOST_MULTIARCH)

or setting the library name explicitly, as already done for Boost.System.
(In the latter case, I strongly suspect you'll need to do the same for
Boost.Random too.)

Could you please take a look?

Thanks!

Processed: forcibly merging 789038 760853

[Debian Bug Tracking System]

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

> forcemerge 789038 760853
Bug #789038 [jitsi] jitsi: Unable to install on sid/unstable
Bug #831232 [jitsi] jitsi: FTBFS: unsatisfiable build-dependencies: libjitsi, 
libjitsi-jni, libphonenumber6-java
Bug #831232 [jitsi] jitsi: FTBFS: unsatisfiable build-dependencies: libjitsi, 
libjitsi-jni, libphonenumber6-java
Marked as fixed in versions jitsi/2.5.5313-1.
Marked as fixed in versions jitsi/2.5.5313-1.
Marked as found in versions jitsi/2.4.4997-1.2.
Marked as found in versions jitsi/2.4.4997-1.2.
Bug #760853 [jitsi] jitsi uninstallable in sid
760853 was not blocked by any bugs.
760853 was not blocking any bugs.
Added blocking bug(s) of 760853: 757768
779521 was not blocked by any bugs.
779521 was not blocking any bugs.
Added blocking bug(s) of 779521: 757768
779522 was not blocked by any bugs.
779522 was not blocking any bugs.
Added blocking bug(s) of 779522: 757768
833902 was not blocked by any bugs.
833902 was not blocking any bugs.
Added blocking bug(s) of 833902: 757768
Added indication that 760853 affects libjitsi-jni
Added indication that 779521 affects libjitsi-jni
Added indication that 779522 affects libjitsi-jni
Added indication that 833902 affects libjitsi-jni
Marked as found in versions jitsi/2.5.5313-1.
Marked as found in versions jitsi/2.5.5313-1.
Marked as found in versions jitsi/2.5.5313-1.
Marked as found in versions jitsi/2.5.5313-1.
Added tag(s) stretch and sid.
Added tag(s) stretch and sid.
Added tag(s) sid and stretch.
Added tag(s) sid and stretch.
Bug #779521 [jitsi] jitsi: Unable to install on sid/unstable
Bug #779522 [jitsi] jitsi: Unable to install on sid/unstable
Bug #833902 [jitsi] jitsi: unable to install jitsi on Debian testing
Merged 760853 779521 779522 789038 831232 833902
> thanks
Stopping processing here.

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

Processed: reassign 833902 to jitsi, forcibly merging 833902 760853

[Debian Bug Tracking System]

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

> reassign 833902 jitsi
Bug #833902 [src:jitsi] jitsi: unable to install jitsi on Debian testing
Bug reassigned from package 'src:jitsi' to 'jitsi'.
No longer marked as found in versions jitsi/2.5.5313-1.
Ignoring request to alter fixed versions of bug #833902 to the same values 
previously set
> forcemerge 833902 760853
Bug #833902 [jitsi] jitsi: unable to install jitsi on Debian testing
Bug #779521 {Done: Damian Minkov } [jitsi] jitsi: Unable to 
install on sid/unstable
755489 was blocked by: 779521 760853 729904 779522
755489 was not blocking any bugs.
Removed blocking bug(s) of 755489: 760853, 779521, and 779522
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions jitsi/2.5.5313-1.
No longer marked as fixed in versions jitsi/2.5.5313-1.
No longer marked as fixed in versions jitsi/2.5.5313-1.
Removed indication that 779521 affects libjitsi-jni
Removed indication that 760853 affects libjitsi-jni
Removed indication that 779522 affects libjitsi-jni
Bug #760853 [jitsi] jitsi uninstallable in sid
Marked as fixed in versions jitsi/2.5.5313-1.
Marked as fixed in versions jitsi/2.5.5313-1.
Marked as fixed in versions jitsi/2.5.5313-1.
Bug #833902 [jitsi] jitsi: unable to install jitsi on Debian testing
Marked as fixed in versions jitsi/2.5.5313-1.
Marked as found in versions jitsi/2.4.4997-1.2.
Bug #779522 [jitsi] jitsi: Unable to install on sid/unstable
Merged 760853 779521 779522 833902
> thanks
Stopping processing here.

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

Bug#833943: libtorrent-rasterbar: FTBFS on non-x86: -msse4.2 unrecognized

[Aaron M. Ucko]

Source: libtorrent-rasterbar
Version: 1.0.7-1+b2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Builds of libtorrent-rasterbar for non-x86 architectures have been
failing:

  aarch64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
-fno-strict-aliasing -lpthread -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. 
-fstack-protector-strong -Wformat -Werror=format-security -fvisibility=hidden 
-I/usr/include -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/python2.7 
-I/usr/include/aarch64-linux-gnu/python2.7 -fPIC -I../../../include 
-I/usr/include -I/usr/include/python2.7 
-I/usr/include/aarch64-linux-gnu/python2.7 -I/usr/include 
-I/usr/include/python2.7 -c /«PKGBUILDDIR»/bindings/python/src/version.cpp -o 
build/temp.linux-aarch64-2.7/«PKGBUILDDIR»/bindings/python/src/version.o 
-DTORRENT_DISABLE_LOGGING -DTORRENT_USE_OPENSSL 
-DBOOST_ASIO_HASH_MAP_BUCKETS=1021 -msse4.2 -DBOOST_EXCEPTION_DISABLE 
-DBOOST_ASIO_ENABLE_CANCELIO -DTORRENT_LINKING_SHARED -Wdate-time 
-D_FORTIFY_SOURCE=2
  aarch64-linux-gnu-gcc: error: unrecognized command line option '-msse4.2'
  error: command 'aarch64-linux-gnu-gcc' failed with exit status 1
  Makefile:529: recipe for target 'all-local' failed
  make[2]: *** [all-local] Error 1
  make[2]: Leaving directory '/«PKGBUILDDIR»/build/bindings/python2.7'

Please drop this flag altogether -- even on x86, it yields
non-portable binaries.

Thanks!

Processed (with 2 errors): Re: Bug#833902: jitsi: unable to install jitsi on Debian testing

[Debian Bug Tracking System]

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

> forcemerge 833902 760853
Bug #833902 [src:jitsi] jitsi: unable to install jitsi on Debian testing
Unable to merge bugs because:
package of #779521 is 'jitsi' not 'src:jitsi'
package of #779522 is 'jitsi' not 'src:jitsi'
package of #760853 is 'jitsi' not 'src:jitsi'
Failed to forcibly merge 833902: Did not alter merged bugs.

> forcemerge 789038 760853
Bug #789038 [jitsi] jitsi: Unable to install on sid/unstable
Bug #831232 [jitsi] jitsi: FTBFS: unsatisfiable build-dependencies: libjitsi, 
libjitsi-jni, libphonenumber6-java
Failed to forcibly merge 789038: failed to get lock on 
/org/bugs.debian.org/spool/lock/760853 -- Unable to lock 
/org/bugs.debian.org/spool/lock/760853 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/760853 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/760853 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/760853 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/760853 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/760853 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/760853 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/760853 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/760853 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/760853 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
$locks = {
   'locks' => {},
   'lockorder' => []
 };
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 587.

> thanks
Stopping processing here.

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

Bug#833902: jitsi: unable to install jitsi on Debian testing

[Kurt Roeckx]

forcemerge 833902 760853
forcemerge 789038 760853
thanks

On Wed, Aug 10, 2016 at 07:21:09AM +, shirish ? wrote:
> Source: jitsi
> Version: 2.5.5313-1
> Justification: renders package unusable
> Severity: grave
> 
> Dear Maintainer,
> Jitsi is still uninstallable on amd64 -
> 
> [$] sudo aptitude install jitsi -y
> 
> [sudo] password for shirish:
> The following NEW packages will be installed:
>   jitsi{b} jitsi-common{a} jitsi-jni{a}

jitsi is not in testing.  You're trying to install it from
unstable.

You're also perfectly aware that it's not installable in unstable,
you already filed a bug that it's not installable in unstable
at least 4 times.  Please stop filing new bugs about it.

> As far as dependencies are concerned, apart from libjitsi and
> libjitsi-jni which probably needs to be provided by jitsi itself ,
> libphonenumber6-java has been superseded by libphonenumber7-java so a
> rebuild or/and an NMU would be needed to take care of the changed
> dependancy.

libjitsi is provided by the libjitsi source package.  That source
package is not in Debian.  It has been rejected multiple times by
ftp-master because of license issues.

Either someone should start working on getting libjitsi in Debian,
or we should remove jitsi.


Kurt

Bug#833419: crashes computer

[Sergio Durigan Junior]

On Wednesday, August 10 2016, 積丹尼 Dan Jacobson wrote:

> Well the black screen only existed within midori, not the whole screen.
> But yes please do reassign it to (one of the several) nouveau named packages.

But were you able to fix the issue by following any of the advices on
the links I gave you?

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


signature.asc
Description: PGP signature

Bug#830924: marked as done (Gem::LoadError: Could not find 'rack-flash3' (>= 0) among 17 total gem(s))

[Debian Bug Tracking System]

Your message dated Wed, 10 Aug 2016 16:52:09 +
with message-id 
and subject line Bug#830924: fixed in ruby-rack-flash3 1.0.5-2
has caused the Debian Bug report #830924,
regarding Gem::LoadError: Could not find 'rack-flash3' (>= 0) among 17 total 
gem(s)
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.)


-- 
830924: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830924
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-rack-flash3
Version: 1.0.5-1
Severity: serious
X-Debbugs-CC: debian-r...@lists.debian.org

Dear Maintainer,

your gem library fails to load on ruby2.3:

GEM_PATH= ruby2.3 -e gem\ \"rack-flash3\"
/usr/lib/ruby/2.3.0/rubygems/dependency.rb:319:in `to_specs': Could not find 
'rack-flash3' (>= 0) among 17 total gem(s) (Gem::LoadError)
Checked in 
'GEM_PATH=/home/debci/.gem/ruby/2.3.0:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all',
 execute `gem env` for more information

Given the last upload date and package contents, this also applies
to jessie/ruby2.1.

-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-
--- End Message ---
--- Begin Message ---
Source: ruby-rack-flash3
Source-Version: 1.0.5-2

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

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated ruby-rack-flash3 
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, 09 Aug 2016 11:46:02 -0300
Source: ruby-rack-flash3
Binary: ruby-rack-flash3
Architecture: source
Version: 1.0.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Antonio Terceiro 
Description:
 ruby-rack-flash3 - Flash hash for Ruby Rack applications
Closes: 830924
Changes:
 ruby-rack-flash3 (1.0.5-2) unstable; urgency=medium
 .
   [ Ben Armstrong ]
   * Removed myself from Uploaders.
 .
   [ Antonio Terceiro ]
   * Add myself to Uploaders.
   * Rebuild with a newer gem2deb adds Rubygems integration (Closes: #830924)
   * Update packaging with a new `dh-make-ruby -w` run
   * fix_requires.patch: amended to also fix running tests under autopkgtest
Checksums-Sha1:
 da2ebf3b3d351202ca7a09250c004045aa42382b 2141 ruby-rack-flash3_1.0.5-2.dsc
 93ae9deb41b21e8bf4dd8db339502b5ebf55a104 3272 
ruby-rack-flash3_1.0.5-2.debian.tar.xz
Checksums-Sha256:
 801bbc4ad87a8e4e11a1bb341ffd6bdb009e19b14c430c741b321ca3bda9e2ff 2141 
ruby-rack-flash3_1.0.5-2.dsc
 e233873d530cf525640206c8db6758c82ade307c2085031938404a080a8f965d 3272 
ruby-rack-flash3_1.0.5-2.debian.tar.xz
Files:
 87c4febf14dfa8049efb1b27b245c8fa 2141 ruby optional 
ruby-rack-flash3_1.0.5-2.dsc
 4a0aa31eb73cbb46599d18529474a9e9 3272 ruby optional 
ruby-rack-flash3_1.0.5-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXqzs/AAoJEPwNsbvNRgveVZQQAMwxuMvFxg6K/p20boKO7Lug
blvvFtqvv3e4Tcl487MicxfWOrusrWpIV0MxX4n1PAMnWNHXBjWENldYn97spsKD
7CWj4WVtR/CaKDl+fbgndXT+phkAc5zyMrao6XE4ryQSkfkEmGtmQjuKKLxBTxYc
UymYfshZiCl1ZbMOjQRbMhEpGJtBtrca/ZXj06vAPB/rfHHDfLmcICAp5lg8rLl0
OgqHGopTyMaQU8S6oybp6jsxwPCDVZOc40Q3r6b0b4l6ZbHpBY3Qkl2CsBQCv085
bwD24jJotKh9HopuadWDbQ6bE1iFjI3AOvrFC8dB19XC4XPbHFO18JPEHfc44k4s
u6fVJBu+B/zBWnZ9q0DgSz2Cd5qZGBwO7a27gZOMS175fUcDX+MEhqDCmHXWk1Y6
KZK9B3n0a0y3hTHAMLUUhxhhmsG3d7CGpanH1Fp7ePM/g39KXCpVqiImrfaADfXE
Ld3c6pTj2DCkwrCbjk+NKz7X/uie8+ZHb5Iw1C8FeZoWdgLmll9wogIB8tfcW3+G
C8RlFea6PPLmjdTQ1vT6a98rAJdgfCsAkUxUH4EWzQMNwHsAdU9GX0JZ5y/hogk6
sVDZeZGsdQcuUvgZp/URYQVG6kFI8ngOwsATpUUOh98lbvXOLxqsZY8fntS5PIJq
Qwr1id/oD95exWQ9HLHW
=7i9U
-END PGP SIGNATURE End Message ---

Bug#718367: marked as done (ruby-uglifier: embedded code copy of uglifyJS (should depend on some package built from uglifyjs source))

[Debian Bug Tracking System]

Your message dated Wed, 10 Aug 2016 16:52:15 +
with message-id 
and subject line Bug#718367: fixed in ruby-uglifier 2.7.2+dfsg-1
has caused the Debian Bug report #718367,
regarding ruby-uglifier: embedded code copy of uglifyJS (should depend on some 
package built from uglifyjs source)
to be marked as done.

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

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


-- 
718367: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718367
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-uglifier
Version: 1.2.5-2
Severity: normal
Control: affects -1 uglifyjs 

the uglifyjs source package contains the javascript for uglifyJS.

however, ruby-uglifier also appears to contain a (reorganized) version
of the same code.

Debian packages should not contain embedded copies of code that exists
elsewhere in the archive; it makes maintenance and security fixes more
difficult than they need to be.

  https://wiki.debian.org/EmbeddedCodeCopies

Regards,

--dkg

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

Kernel: Linux 3.9-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Source: ruby-uglifier
Source-Version: 2.7.2+dfsg-1

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

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated ruby-uglifier 
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, 10 Aug 2016 11:35:54 -0300
Source: ruby-uglifier
Binary: ruby-uglifier
Architecture: source
Version: 2.7.2+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Antonio Terceiro 
Description:
 ruby-uglifier - Ruby wrapper for UglifyJS JavaScript compressor
Closes: 718367
Changes:
 ruby-uglifier (2.7.2+dfsg-1) unstable; urgency=medium
 .
   * Team upload
 .
   [ Cédric Boutillier ]
   * Bump debhelper compatibility level to 9
   * Remove version in the gem2deb build-dependency
   * Use https:// in Vcs-* fields
   * Bump Standards-Version to 3.9.7 (no changes needed)
   * Run wrap-and-sort on packaging files
 .
   [ Antonio Terceiro ]
   * Use UglifyJS source from libjs-uglify (Closes: #718367)
 - drop lib/uglify.js from upstream tarball
 - Use libjs-uglify
 - This brings a small regression: the embedded copy of UglifyJS was
   version 2.7.0, while the one provided by libjs-uglify is 2.4.15. This
   makes one automated test fail during the build, related to using input
   source maps. This test has been marked as pending for now, and this
   functionality will not work until UglifyJS is not upgraded.
   * Refresh pacakging with a new `dh-make-ruby -w` run
Checksums-Sha1:
 a228cb53688e8fbe810765e3ef912bbb3ff85432 2207 ruby-uglifier_2.7.2+dfsg-1.dsc
 24a819c99a3b96775077f0bfc8fdabc0912a321b 18226 
ruby-uglifier_2.7.2+dfsg.orig.tar.gz
 f42a92dc201472d9b0d82e1da9305794661875ae 4264 
ruby-uglifier_2.7.2+dfsg-1.debian.tar.xz
Checksums-Sha256:
 dc5911e00f00ddc2f697bc09c85c9953bccf23ee0eb458046dedbc1fde04760b 2207 
ruby-uglifier_2.7.2+dfsg-1.dsc
 63625cf31361f30746e476813be328f85b7d357bb2cafb9c1c91a42aba194775 18226 
ruby-uglifier_2.7.2+dfsg.orig.tar.gz
 e5e4c84e4d91b5223c455613c90df849afd955fdaa4d98e109e90af8cb657841 4264 
ruby-uglifier_2.7.2+dfsg-1.debian.tar.xz
Files:
 a87c847e9e2c859a480e16cf63b7eeac 2207 ruby optional 
ruby-uglifier_2.7.2+dfsg-1.dsc
 d5bfc5a10eea76f8475b87e0a09f0a2d 18226 ruby optional 
ruby-uglifier_2.7.2+dfsg.orig.tar.gz
 fbe193a9fd38dde5ce6ee2be408ad409 4264 ruby optional 
ruby-uglifier_2.7.2+dfsg-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXqz6yAAoJEPwNsbvNRgve7fsQAKXqVH1gKRfS22mDwOEhlU4v

Bug#708956: [Bug-jwhois] Bug#708956: [jwhois] GFDL non free license

[Mathieu Lirzin]

Yuan-Chen Cheng  writes:

> Hi, I write a email to bug-jwh...@gnu.org last week but get no reply.
>
> Shall we just remove those two file from the install list and live
> with that ?
>
> I am interested to provide patch to do that if that’s the possible and
> legal way to do.
>
> thanks, YC
>

Hello,

IIUC correctly the issue is that the license notice in Jwhois 4.0 manual is

--8<---cut here---start->8---
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.1 or
any later version published by the Free Software Foundation; with no
Invariant Sections, with the Front-Cover Texts being ``A GNU Manual,''
and with the Back-Cover Texts as in (a) below.  A copy of the
license is included in the section entitled ``GNU Free Documentation
License.''

(a) The FSF's Back-Cover Text is: ``You have freedom to copy and modify
this GNU Manual, like GNU software.  Copies published by the Free
Software Foundation raise funds for GNU development.''
--8<---cut here---end--->8---

which requires the FSF back-cover text.  Without this requirement the
manual could be distributed as in Debian main.  Like what is done with
GNU Automake manual which license is:

--8<---cut here---start->8---
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.3 or any later version published by the Free Software
Foundation; with no Invariant Sections, with no Front-Cover texts,
and with no Back-Cover Texts.  A copy of the license is included in the
section entitled ``GNU Free Documentation License.''
--8<---cut here---end--->8---

So to recap the situation, as a recent Jwhois contributor I have already
modified (in the development repository) the license of Jwhois to match
the one from Automake.  I will check with the FSF if they are OK with
that.

As one may have notice Jwhois 4.0 is really old, and I intend to make a
new release in the following months if Jwhois maintainer agrees.  When
that is done I think Jwhois will be ready to reintegrate Debian main.

Can someone confirm that I understand the issue correctly?

Thanks.

-- 
Mathieu Lirzin

Bug#814619: marked as done (yubioath-desktop depends on cruft package python-pyscard.)

[Debian Bug Tracking System]

Your message dated Wed, 10 Aug 2016 18:32:06 +0200
with message-id <20160810183206.2834f...@latte.josefsson.org>
and subject line Re: yubioath-desktop: depends on python-pyscard which is gone
has caused the Debian Bug report #814594,
regarding yubioath-desktop depends on cruft package python-pyscard.
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.)


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

Package: yubioauth-desktop
Severity: serious
x-debbugs-cc: pysc...@packages.debian.org

yubioauth-desktop depends on python-pyscard which is no longer built by 
pyscard.


pyscard dropped the binary package in it's most recent upload with no 
explanation given in the changelog.
--- End Message ---
--- Begin Message ---
I'm closing this since 1) the python-pyscard package is now back, and
2) the latest upload supports python 3 as far as I understand.

/Simon


pgpKylDS1fLEf.pgp
Description: OpenPGP digital signatur
--- End Message ---

Bug#814594: marked as done (yubioath-desktop: depends on python-pyscard which is gone)

[Debian Bug Tracking System]

Your message dated Wed, 10 Aug 2016 18:32:06 +0200
with message-id <20160810183206.2834f...@latte.josefsson.org>
and subject line Re: yubioath-desktop: depends on python-pyscard which is gone
has caused the Debian Bug report #814594,
regarding yubioath-desktop: depends on python-pyscard which is gone
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.)


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

Your package depends on python-pyscard, but pyscard no longer builds that:
instead it builds python3-pyscard.

You should get your package to use python3, or get that package back.

Cheers,
Emilio
--- End Message ---
--- Begin Message ---
I'm closing this since 1) the python-pyscard package is now back, and
2) the latest upload supports python 3 as far as I understand.

/Simon


pgpBMziFJDxuu.pgp
Description: OpenPGP digital signatur
--- End Message ---

Processed: tagging 833181

[Debian Bug Tracking System]

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

> tags 833181 + pending
Bug #833181 [libreoffice-draw] libreoffice-draw: I/O general error when saving 
when libreoffice-impress isn't installed
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#833934: Same problems described by OP

[Kyle Bentley]

After the update from 45.2.0 to +b1 I am experiencing the same behavior 
as Christoph.  I am also running Baikal server and connecting too it via 
CalDAV.  I can start icedove in safe-mode only.  I did a debug with gdb, 
and I am also getting a segfault in the same area.  The information is 
below.


I did not include system information, but it is essentially the same as 
Cristoph's, a fully up-to-date install of testing x64.


kyle@minilith:~$ gdb icedove
GNU gdb (Debian 7.11.1-2) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 


This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from icedove...Reading symbols from 
/usr/lib/debug//usr/lib/icedove/icedove...done.

done.
(gdb) run
Starting program: /usr/bin/icedove
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

[New Thread 0x7fffe5ccf700 (LWP 5147)]
[Thread 0x7fffe5ccf700 (LWP 5147) exited]
[New Thread 0x7fffe5ccf700 (LWP 5149)]
[New Thread 0x7fffe33ff700 (LWP 5150)]
[New Thread 0x77fed700 (LWP 5151)]
[New Thread 0x7fffe2bfe700 (LWP 5152)]
[New Thread 0x7fffe20ff700 (LWP 5153)]
[New Thread 0x7fffe1efe700 (LWP 5154)]
[New Thread 0x7fffe1cfd700 (LWP 5155)]
[New Thread 0x7fffe1afc700 (LWP 5156)]
[New Thread 0x7fffe18fb700 (LWP 5157)]
[New Thread 0x7fffe16fa700 (LWP 5158)]
[New Thread 0x7fffe14f9700 (LWP 5159)]
[New Thread 0x7fffe12f8700 (LWP 5160)]
[New Thread 0x7fffd700 (LWP 5161)]
[New Thread 0x7fffdf3a2700 (LWP 5162)]
[New Thread 0x7fffdeba1700 (LWP 5163)]
[New Thread 0x7fffe4667700 (LWP 5164)]
[New Thread 0x7fffdddff700 (LWP 5165)]
[New Thread 0x7fffdcaff700 (LWP 5166)]
[New Thread 0x7fffdc2fe700 (LWP 5167)]
[New Thread 0x7fffd94ff700 (LWP 5168)]
INCLUDE NSS: TypeError: redeclaration of let tcypes
[New Thread 0x7fffd7af2700 (LWP 5169)]
[New Thread 0x7fffd72f1700 (LWP 5170)]
[New Thread 0x7fffd6af0700 (LWP 5171)]
[New Thread 0x7fffd60ff700 (LWP 5172)]
[New Thread 0x7fffd58fe700 (LWP 5173)]
[New Thread 0x7fffd4eff700 (LWP 5174)]
[New Thread 0x7fffd46fe700 (LWP 5175)]
[New Thread 0x7fffd3efd700 (LWP 5176)]
[calBackendLoader] Using libical backend at 
/usr/lib/icedove/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/components/libical-manifest

[New Thread 0x7fffd1754700 (LWP 5177)]
[New Thread 0x7fffd0f53700 (LWP 5178)]
[New Thread 0x7fffd0752700 (LWP 5179)]
[New Thread 0x7fffcff51700 (LWP 5180)]
[New Thread 0x7fffcf750700 (LWP 5181)]
[New Thread 0x7fffcef4f700 (LWP 5182)]
[New Thread 0x7fffce74e700 (LWP 5183)]
[New Thread 0x7fffccbff700 (LWP 5184)]
[New Thread 0x7fffcc3fe700 (LWP 5185)]
[New Thread 0x7fffcbbfd700 (LWP 5186)]
[New Thread 0x7fffcb3fc700 (LWP 5187)]
[New Thread 0x7fffca9ff700 (LWP 5188)]
[New Thread 0x7fffca1fe700 (LWP 5189)]
[New Thread 0x7fffc99fd700 (LWP 5190)]
[New Thread 0x7fffc91fc700 (LWP 5191)]
[Thread 0x7fffd94ff700 (LWP 5168) exited]
[Thread 0x7fffca9ff700 (LWP 5188) exited]
[Thread 0x7fffca1fe700 (LWP 5189) exited]
[Thread 0x7fffc99fd700 (LWP 5190) exited]
[New Thread 0x7fffc87ff700 (LWP 5192)]
[New Thread 0x7fffc99fd700 (LWP 5193)]
[New Thread 0x7fffca1fe700 (LWP 5194)]
[New Thread 0x7fffca9ff700 (LWP 5195)]
[Thread 0x7fffca9ff700 (LWP 5195) exited]
[Thread 0x7fffc91fc700 (LWP 5191) exited]
[New Thread 0x7fffc91fc700 (LWP 5196)]
[New Thread 0x7fffca9ff700 (LWP 5197)]
[Thread 0x7fffca1fe700 (LWP 5194) exited]
[New Thread 0x7fffca1fe700 (LWP 5198)]
[Thread 0x7fffca9ff700 (LWP 5197) exited]
[New Thread 0x7fffca9ff700 (LWP 5199)]
[New Thread 0x7fffd94ff700 (LWP 5200)]
[Thread 0x7fffca1fe700 (LWP 5198) exited]
[Thread 0x7fffca9ff700 (LWP 5199) exited]
[New Thread 0x7fffca9ff700 (LWP 5201)]
[Thread 0x7fffca9ff700 (LWP 5201) exited]
messenger.groupdav.overlay.js: failed to include 
'chrome://sogo-connector/content/general/vcards.utils.js'

TypeError: redeclaration of let kPhotoImageCache
File: chrome://sogo-connector/content/general/vcards.utils.js
Line: 22

 Stack:

@chrome://sogo-connector/content/general/vcards.utils.js:22:5
jsInclude@chrome://sogo-connector/content/addressbook/messenger.groupdav.overlay.js:26:13
@chrome://sogo-connector/content/addressbook/messenger.groupdav.overlay.js:37:1

Thread 1 "icedove" received signal SIGSEGV, Segmentation fault.
0x73e007a1 in js::jit::SnapshotIterator::numAllocations 
(this=0x7fff8ae0)

at ./mozilla/js/src/jit/JitFrames.cpp:2159
2159./mozilla/js/src/jit/JitFrames.cpp: No such file or 

Processed: severity of 833934 is grave

[Debian Bug Tracking System]

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

> severity 833934 grave
Bug #833934 [icedove] icedove: segfaults on startup with iceowl and CalDAV in 
place (very recent regression?)
Bug #833532 [icedove] calendar-google-provider causes crash of icedove
Bug #833591 [icedove] calendar-google-provider causes crash of icedove
Bug #833635 [icedove] calendar-google-provider causes crash of icedove
Bug #833698 [icedove] icedove: SIGSEGV, Segmentation fault in 
js::jit::HandleExceptionIon
Severity set to 'grave' from 'important'
Severity set to 'grave' from 'important'
Severity set to 'grave' from 'important'
Severity set to 'grave' from 'important'
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#833937: marked as done ([icedove] regression: Very frequent segfaults)

[Debian Bug Tracking System]

Your message dated Wed, 10 Aug 2016 18:03:51 +0200
with message-id <20160810160351.ga5...@stretch.cruise.homelinux.net>
and subject line Re: Bug#833937: [icedove] regression: Very frequent segfaults
has caused the Debian Bug report #833937,
regarding [icedove] regression: Very frequent segfaults
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.)


-- 
833937: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833937
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: icedove
Version: 1:45.2.0-2+b1
Severity: serious

--- Please enter the report below this line. ---

In the current version of icedove, I see very frerequent segfaults,
about once per hour. The previous version was running for days before
segfaulting. This might or might not be the same as bug #829188. The
only extension I use is enigmail; I use icedove for IMAP, POP3 and NEWS.
The segfaults do not seem to be correlated with user activity in any
way. thunderbird might segfault while I write an email, or have the
window on top, or in thebackground or whatever.

Example console output (the number of pixman_region32_reset messages
varies between segfaults):

philipp@notebook4:~$ export LANG=C
philipp@notebook4:~$ icedove
[calBackendLoader] Using libical backend at
/usr/lib/icedove/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/components/libical-manifest
*** BUG ***
In pixman_region32_reset: Malformed region region
Set a breakpoint on '_pixman_log_error' to debug

*** BUG ***
In pixman_region32_reset: Malformed region region
Set a breakpoint on '_pixman_log_error' to debug

*** BUG ***
In pixman_region32_reset: Malformed region region
Set a breakpoint on '_pixman_log_error' to debug

*** BUG ***
In pixman_region32_reset: Malformed region region
Set a breakpoint on '_pixman_log_error' to debug

*** BUG ***
In pixman_region32_reset: Malformed region region
Set a breakpoint on '_pixman_log_error' to debug

*** BUG ***
In pixman_region32_reset: Malformed region region
Set a breakpoint on '_pixman_log_error' to debug

*** BUG ***
In pixman_region32_reset: Malformed region region
Set a breakpoint on '_pixman_log_error' to debug

Segmentation fault

--- System information. ---
Architecture: amd64
Kernel:   Linux 4.6.0-1-amd64

Debian Release: stretch/sid
  500 unstableftp.de.debian.org   500 testing
ftp.de.debian.org 1 experimentalftp.de.debian.org
--- Package information. ---
Depends   (Version) | Installed
===-+-===
debianutils   (>= 1.16) | 4.8
fontconfig  | 2.11.0-6.4
psmisc  | 22.21-2.1+b1
libasound2  (>= 1.0.16) | libatk1.0-0
 (>= 1.12.4) | libc6 (>=
2.17) | libcairo2(>= 1.10.2-2~) | libdbus-1-3
 (>= 1.9.14) | libdbus-glib-1-2
(>= 0.78) | libevent-2.0-5   (>= 2.0.10-stable) | libffi6
  (>= 3.0.4) | libfontconfig1
(>= 2.11) | libfreetype6 (>= 2.2.1) |
libgcc1  (>= 1:4.0) | libgdk-pixbuf2.0-0
 (>= 2.22.0) | libglib2.0-0(>=
2.22.0) | libgtk2.0-0 (>= 2.24.0) |
libhunspell-1.4-0   | libicu57
(>= 57.1-1~) | libnspr4  (>=
2:4.10.3) | libnss3 (>= 2:3.19) |
libpango-1.0-0  (>= 1.14.0) | libpangocairo-1.0-0
 (>= 1.14.0) | libpangoft2-1.0-0   (>=
1.14.0) | libpixman-1-0   (>= 0.19.6) | libsqlite3-0
   (>= 3.7.10) | libstartup-notification0
   (>= 0.8) | libstdc++6 (>= 5.2) | libvpx3
(>= 1.5.0) | libx11-6
| libxcomposite1 (>= 1:0.3-1) |
libxdamage1  (>= 1:1.1) | libxext6
 | libxfixes3
  | libxrender1 | libxt6
 | zlib1g (>=
1:1.2.0) |

Recommends  (Version) | Installed
=-+-==
iceowl-extension(= 1:45.2.0-2+b1) | 1:45.2.0-2+b1
myspell-en-us |  OR hunspell-dictionary
 |  OR myspell-dictionary|

Suggests  (Version) | Installed

Bug#833904: haskell-blogliterately: FTBFS: fails with -ENOENT

[Joachim Breitner]

Hi,

Am Mittwoch, den 10.08.2016, 15:38 + schrieb Mattia Rizzolo:
> On Wed, Aug 10, 2016 at 02:44:00PM +, Clint Adams wrote:
> > 
> > On Wed, Aug 10, 2016 at 07:44:25AM +, Mattia Rizzolo wrote:
> > > 
> > > : can't load .so/.DLL for: /usr/lib/haskell-
> > > packages/ghc/lib/x86_64-linux-ghc-7.10.3/pandoc-citeproc-0.9.1.1-
> > > H4nKjmy3LdhAeupsyJYDB0/libHSpandoc-citeproc-0.9.1.1-
> > > H4nKjmy3LdhAeupsyJYDB0-ghc7.10.3.so (libicuuc.so.55: cannot open
> > > shared object file: No such file or directory)
> > 
> > Looks like haskell-pandoc-citeproc needs to be rebuilt against the
> > new libicu-dev and then haskell-blogliterately can be given back.
> 
> umh, usually don't you have complex dependency chains preventing this
> kind of failures?

we do have that for Haskell ABI changes, but I believe it does not
cover the names of shared C libraries. Maybe that can be considered a
bug, and something that can be fixed on the GHC side. If someone wants
to dig deeper, I’ll happily assist.

Greetings,
Joachim



-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

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

Processed: forcibly merging 833934 833532

[Debian Bug Tracking System]

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

> forcemerge 833934 833532
Bug #833934 [icedove] icedove: segfaults on startup with iceowl and CalDAV in 
place (very recent regression?)
Bug #833635 [icedove] calendar-google-provider causes crash of icedove
Severity set to 'important' from 'grave'
Severity set to 'important' from 'grave'
Severity set to 'important' from 'grave'
Severity set to 'important' from 'grave'
Marked as found in versions icedove/1:45.2.0-2.
Marked as found in versions icedove/1:45.2.0-2.
Marked as found in versions icedove/1:45.2.0-2.
Marked as found in versions icedove/1:45.2.0-2.
Bug #833934 [icedove] icedove: segfaults on startup with iceowl and CalDAV in 
place (very recent regression?)
Added tag(s) upstream.
Bug #833532 [icedove] calendar-google-provider causes crash of icedove
Bug #833591 [icedove] calendar-google-provider causes crash of icedove
Bug #833698 [icedove] icedove: SIGSEGV, Segmentation fault in 
js::jit::HandleExceptionIon
Merged 833532 833591 833635 833698 833934
> thanks
Stopping processing here.

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

Processed: reassign 833635 to icedove

[Debian Bug Tracking System]

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

> reassign 833635 icedove
Bug #833635 [icedove] calendar-google-provider causes crash of icedove
Bug #833532 [icedove] calendar-google-provider causes crash of icedove
Bug #833591 [icedove] calendar-google-provider causes crash of icedove
Bug #833698 [icedove] icedove: SIGSEGV, Segmentation fault in 
js::jit::HandleExceptionIon
Ignoring request to reassign bug #833635 to the same package
Ignoring request to reassign bug #833532 to the same package
Ignoring request to reassign bug #833591 to the same package
Ignoring request to reassign bug #833698 to the same package
> thanks
Stopping processing here.

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

Processed: reassign 833698 to icedove

[Debian Bug Tracking System]

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

> reassign 833698 icedove
Bug #833698 [icedove] icedove: SIGSEGV, Segmentation fault in 
js::jit::HandleExceptionIon
Bug #833532 [icedove] calendar-google-provider causes crash of icedove
Bug #833591 [icedove] calendar-google-provider causes crash of icedove
Bug #833635 [icedove] calendar-google-provider causes crash of icedove
Ignoring request to reassign bug #833698 to the same package
Ignoring request to reassign bug #833532 to the same package
Ignoring request to reassign bug #833591 to the same package
Ignoring request to reassign bug #833635 to the same package
> thanks
Stopping processing here.

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

Processed: reassign 833532 to icedove

[Debian Bug Tracking System]

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

> reassign 833532 icedove
Bug #833532 [calendar-google-provider] calendar-google-provider causes crash of 
icedove
Bug #833591 [calendar-google-provider] calendar-google-provider causes crash of 
icedove
Bug #833635 [calendar-google-provider] calendar-google-provider causes crash of 
icedove
Bug #833698 [calendar-google-provider] icedove: SIGSEGV, Segmentation fault in 
js::jit::HandleExceptionIon
Bug reassigned from package 'calendar-google-provider' to 'icedove'.
Bug reassigned from package 'calendar-google-provider' to 'icedove'.
Bug reassigned from package 'calendar-google-provider' to 'icedove'.
Bug reassigned from package 'calendar-google-provider' to 'icedove'.
Ignoring request to alter found versions of bug #833532 to the same values 
previously set
Ignoring request to alter found versions of bug #833591 to the same values 
previously set
Ignoring request to alter found versions of bug #833635 to the same values 
previously set
Ignoring request to alter found versions of bug #833698 to the same values 
previously set
Ignoring request to alter fixed versions of bug #833532 to the same values 
previously set
Ignoring request to alter fixed versions of bug #833591 to the same values 
previously set
Ignoring request to alter fixed versions of bug #833635 to the same values 
previously set
Ignoring request to alter fixed versions of bug #833698 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: reassign 833591 to icedove

[Debian Bug Tracking System]

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

> reassign 833591 icedove
Bug #833591 [icedove] calendar-google-provider causes crash of icedove
Bug #833532 [icedove] calendar-google-provider causes crash of icedove
Bug #833635 [icedove] calendar-google-provider causes crash of icedove
Bug #833698 [icedove] icedove: SIGSEGV, Segmentation fault in 
js::jit::HandleExceptionIon
Ignoring request to reassign bug #833591 to the same package
Ignoring request to reassign bug #833532 to the same package
Ignoring request to reassign bug #833635 to the same package
Ignoring request to reassign bug #833698 to the same package
> thanks
Stopping processing here.

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

Bug#833904: haskell-blogliterately: FTBFS: fails with -ENOENT

[Mattia Rizzolo]

On Wed, Aug 10, 2016 at 02:44:00PM +, Clint Adams wrote:
> On Wed, Aug 10, 2016 at 07:44:25AM +, Mattia Rizzolo wrote:
> > : can't load .so/.DLL for: 
> > /usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-7.10.3/pandoc-citeproc-0.9.1.1-H4nKjmy3LdhAeupsyJYDB0/libHSpandoc-citeproc-0.9.1.1-H4nKjmy3LdhAeupsyJYDB0-ghc7.10.3.so
> >  (libicuuc.so.55: cannot open shared object file: No such file or directory)
> 
> Looks like haskell-pandoc-citeproc needs to be rebuilt against the
> new libicu-dev and then haskell-blogliterately can be given back.

umh, usually don't you have complex dependency chains preventing this
kind of failures?

anyway, atm haskell-pandoc-citeproc is bd-uninst, awaiting for other
stuff to be rebuilt after the binNMUs scheduled by pochu this morning.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#833937: [icedove] regression: Very frequent segfaults

[Philipp Klaus Krause]

Package: icedove
Version: 1:45.2.0-2+b1
Severity: serious

--- Please enter the report below this line. ---

In the current version of icedove, I see very frerequent segfaults,
about once per hour. The previous version was running for days before
segfaulting. This might or might not be the same as bug #829188. The
only extension I use is enigmail; I use icedove for IMAP, POP3 and NEWS.
The segfaults do not seem to be correlated with user activity in any
way. thunderbird might segfault while I write an email, or have the
window on top, or in thebackground or whatever.

Example console output (the number of pixman_region32_reset messages
varies between segfaults):

philipp@notebook4:~$ export LANG=C
philipp@notebook4:~$ icedove
[calBackendLoader] Using libical backend at
/usr/lib/icedove/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/components/libical-manifest
*** BUG ***
In pixman_region32_reset: Malformed region region
Set a breakpoint on '_pixman_log_error' to debug

*** BUG ***
In pixman_region32_reset: Malformed region region
Set a breakpoint on '_pixman_log_error' to debug

*** BUG ***
In pixman_region32_reset: Malformed region region
Set a breakpoint on '_pixman_log_error' to debug

*** BUG ***
In pixman_region32_reset: Malformed region region
Set a breakpoint on '_pixman_log_error' to debug

*** BUG ***
In pixman_region32_reset: Malformed region region
Set a breakpoint on '_pixman_log_error' to debug

*** BUG ***
In pixman_region32_reset: Malformed region region
Set a breakpoint on '_pixman_log_error' to debug

*** BUG ***
In pixman_region32_reset: Malformed region region
Set a breakpoint on '_pixman_log_error' to debug

Segmentation fault

--- System information. ---
Architecture: amd64
Kernel:   Linux 4.6.0-1-amd64

Debian Release: stretch/sid
  500 unstableftp.de.debian.org   500 testing
ftp.de.debian.org 1 experimentalftp.de.debian.org
--- Package information. ---
Depends   (Version) | Installed
===-+-===
debianutils   (>= 1.16) | 4.8
fontconfig  | 2.11.0-6.4
psmisc  | 22.21-2.1+b1
libasound2  (>= 1.0.16) | libatk1.0-0
 (>= 1.12.4) | libc6 (>=
2.17) | libcairo2(>= 1.10.2-2~) | libdbus-1-3
 (>= 1.9.14) | libdbus-glib-1-2
(>= 0.78) | libevent-2.0-5   (>= 2.0.10-stable) | libffi6
  (>= 3.0.4) | libfontconfig1
(>= 2.11) | libfreetype6 (>= 2.2.1) |
libgcc1  (>= 1:4.0) | libgdk-pixbuf2.0-0
 (>= 2.22.0) | libglib2.0-0(>=
2.22.0) | libgtk2.0-0 (>= 2.24.0) |
libhunspell-1.4-0   | libicu57
(>= 57.1-1~) | libnspr4  (>=
2:4.10.3) | libnss3 (>= 2:3.19) |
libpango-1.0-0  (>= 1.14.0) | libpangocairo-1.0-0
 (>= 1.14.0) | libpangoft2-1.0-0   (>=
1.14.0) | libpixman-1-0   (>= 0.19.6) | libsqlite3-0
   (>= 3.7.10) | libstartup-notification0
   (>= 0.8) | libstdc++6 (>= 5.2) | libvpx3
(>= 1.5.0) | libx11-6
| libxcomposite1 (>= 1:0.3-1) |
libxdamage1  (>= 1:1.1) | libxext6
 | libxfixes3
  | libxrender1 | libxt6
 | zlib1g (>=
1:1.2.0) |

Recommends  (Version) | Installed
=-+-==
iceowl-extension(= 1:45.2.0-2+b1) | 1:45.2.0-2+b1
myspell-en-us |  OR hunspell-dictionary
 |  OR myspell-dictionary|

Suggests  (Version) | Installed
===-+-===
apparmor| fonts-lyx   | 2.2.0-2
libgssapi-krb5-2|

Bug#833904: haskell-blogliterately: FTBFS: fails with -ENOENT

[Joachim Breitner]

Hi,

Am Mittwoch, den 10.08.2016, 14:44 + schrieb Clint Adams:
> On Wed, Aug 10, 2016 at 07:44:25AM +, Mattia Rizzolo wrote:
> > 
> > : can't load .so/.DLL for: /usr/lib/haskell-
> > packages/ghc/lib/x86_64-linux-ghc-7.10.3/pandoc-citeproc-0.9.1.1-
> > H4nKjmy3LdhAeupsyJYDB0/libHSpandoc-citeproc-0.9.1.1-
> > H4nKjmy3LdhAeupsyJYDB0-ghc7.10.3.so (libicuuc.so.55: cannot open
> > shared object file: No such file or directory)
> 
> Looks like haskell-pandoc-citeproc needs to be rebuilt against the
> new libicu-dev and then haskell-blogliterately can be given back.

just nmu’ed haskell-pandoc-citeproc on all architectures.

Joachim

-- 
Joachim “nomeata” Breitner
Debian Developer
  nome...@debian.org • https://people.debian.org/~nomeata
  XMPP: nome...@joachim-breitner.de • GPG-Key: 0xF0FBF51F
  https://www.joachim-breitner.de/

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

Bug#833419: crashes computer

[Sergio Durigan Junior]

Control: tags -1 + moreinfo

On Friday, August 05 2016, 積丹尼 Dan Jacobson wrote:

> In fact not only a black screen (Thinkpad), but (Acer desktop) shortly
> afterwards it hangs the whole computer with a frozen screen.
>
> Several times hitting on the power button produce
>
> Aug  5 14:35:33 jidanni6 systemd[1]: Stopped target Timers.
> Aug  5 14:35:33 jidanni6 systemd[1]: Stopped Daily apt activities.
> Aug  5 14:35:33 jidanni6 systemd[1]: Stopping User Manager for UID 1000...
> Aug  5 14:35:33 jidanni6 systemd[1]: Stopped target Sound Card.
> Aug  5 14:35:33 jidanni6 systemd[1]: Stopping ACPI event daemon...
> Aug  5 14:35:33 jidanni6 systemd[1]: Stopping LSB: Start NTP daemon...
> Aug  5 14:35:33 jidanni6 systemd[1]: Stopping Session 1 of user jidanni.
> Aug  5 14:35:33 jidanni6 systemd[1]: Stopped target Graphical Interface.
> Aug  5 14:35:33 jidanni6 systemd[1]: Stopped target Multi-User System.
> Aug  5 14:35:48 jidanni6 kernel: [13258.804053] nouveau :00:05.0: 
> WebKitWebProces[5809]: failed to idle channel 5 [WebKitWebProces[5809]]
> Aug  5 14:36:03 jidanni6 kernel: [13273.832035] nouveau :00:05.0: 
> WebKitWebProces[5809]: failed to idle channel 5 [WebKitWebProces[5809]]
> Aug  5 14:35:33 jidanni6 systemd[1]: Stopping Deferred execution scheduler...
> Aug 5 14:36:07 jidanni6 rsyslogd: [origin software="rsyslogd"
> swVersion="8.16.0" x-pid="1507" x-info="http://www.rsyslog.com;]
> exiting on signal 15.

Hey Dan,

I'm busy these days so I haven't been able to pay much attention to
Midori, but I did a quick search on the internet for this nouveau
message and found several reports of exactly what you're experiencing.

There are apparently a lot of ways to try to fix this; I'm posting a few
links that I found:

  
http://askubuntu.com/questions/183386/nouveau-driver-issue-when-trying-to-boot-ubuntu

  http://askubuntu.com/questions/600467/blackscreen-failed-to-idle-channel

So far, this doesn't seem a problem with Midori, but with the nouveau
driver.

I'm tempted to move this to nouveau, but I'd like to make sure that you
can solve your issue first.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


signature.asc
Description: PGP signature

Bug#833904: haskell-blogliterately: FTBFS: fails with -ENOENT

[Clint Adams]

On Wed, Aug 10, 2016 at 07:44:25AM +, Mattia Rizzolo wrote:
> : can't load .so/.DLL for: 
> /usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-7.10.3/pandoc-citeproc-0.9.1.1-H4nKjmy3LdhAeupsyJYDB0/libHSpandoc-citeproc-0.9.1.1-H4nKjmy3LdhAeupsyJYDB0-ghc7.10.3.so
>  (libicuuc.so.55: cannot open shared object file: No such file or directory)

Looks like haskell-pandoc-citeproc needs to be rebuilt against the
new libicu-dev and then haskell-blogliterately can be given back.

Processed (with 1 error): Re: libcups2-dev: Missing dependency on libcupsimage-2-dev

[Debian Bug Tracking System]

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

> reassign 833889 libcups2-dev/2.2~rc1-1
Unknown command or malformed arguments to command.
> retitle 833889 libcups2-dev: Missing dependency on libcupsimage-2-dev
Bug #833889 [libcups-dev] libcups-dev: Missing dependency on libcupsimage-2-dev
Warning: Unknown package 'libcups-dev'
Changed Bug title to 'libcups2-dev: Missing dependency on libcupsimage-2-dev' 
from 'libcups-dev: Missing dependency on libcupsimage-2-dev'.
Warning: Unknown package 'libcups-dev'
>
End of message, stopping processing here.

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

Bug#828642: marked as done (FTBFS under Django 1.10)

[Debian Bug Tracking System]

Your message dated Wed, 10 Aug 2016 10:20:04 +
with message-id 
and subject line Bug#828642: fixed in django-celery 3.1.17-3.1
has caused the Debian Bug report #828642,
regarding FTBFS under Django 1.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.)


-- 
828642: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828642
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: django-celery
Version: 3.1.17-3
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that django-celery FTBFS with 1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


django-celery_3.1.17-3.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: django-celery
Source-Version: 3.1.17-3.1

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated django-celery 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, 02 Aug 2016 22:31:30 +
Source: django-celery
Binary: python-django-celery python3-django-celery python-django-celery-doc
Architecture: source all
Version: 3.1.17-3.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Thomas Goirand 
Description:
 python-django-celery - Celery integration for Django
 python-django-celery-doc - Celery integration for Django (Documentation)
 python3-django-celery - Celery integration for Django (Python3 version)
Closes: 828642
Changes:
 django-celery (3.1.17-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add Django 1.10 patches to fix FTBFS (Closes: #828642):
 - 0008-django-1.10-fix-django.conf.urls.patterns-is-removed.patch
 - 0009-django-1.10-fix-access-to-_default_manager.patch
   * Standards-Version: 3.9.8 (no change).
Checksums-Sha1:
 ff7efb9d08ee5601a2b92b432082fc86dfbb6fe6 2578 django-celery_3.1.17-3.1.dsc
 2ad4cf6eeb20a76f49334fac31d40a0b08bd4ee9 12452 
django-celery_3.1.17-3.1.debian.tar.xz
 9f2d8f85d33a14c5a3788d9e37e10b9cc39c337c 65852 
python-django-celery-doc_3.1.17-3.1_all.deb
 ba799438c5dae921235b72a646171951cdb15d76 55310 
python-django-celery_3.1.17-3.1_all.deb
 404fec51617ed2f854148b3cff09839fa3c781c8 51292 
python3-django-celery_3.1.17-3.1_all.deb
Checksums-Sha256:
 21b8375053b2095ce4497feff1f6ed208b89b2d6b529ace38d603828a9c23869 2578 
django-celery_3.1.17-3.1.dsc
 5b6386140361ea9907032948eb8958b3e8710f321fb52a727ef05da5ae377c7a 12452 
django-celery_3.1.17-3.1.debian.tar.xz
 df122f92ee770549f6547dd290669d0b85aeded82d83b6942fcd9bcdb41dbf70 65852 
python-django-celery-doc_3.1.17-3.1_all.deb
 ebe32f8e96c5fe8eb7add9152db1504d45b0be8e021259501b1a3678f65118ea 55310 
python-django-celery_3.1.17-3.1_all.deb
 e1de2414b11edd592f9295ca68c86f8129f082da2569265066bd3fe17c40879d 51292 
python3-django-celery_3.1.17-3.1_all.deb
Files:
 870d0e98db3d852dc7704517778d96c8 2578 python optional 
django-celery_3.1.17-3.1.dsc
 7e2617f33b7816f9ffbbeb4008fa3989 12452 python optional 
django-celery_3.1.17-3.1.debian.tar.xz
 e16efbd6fbfb2806eb63742882a6526a 65852 doc optional 
python-django-celery-doc_3.1.17-3.1_all.deb
 a4e216c0c31518344100aa07d7bde0f8 55310 python optional 
python-django-celery_3.1.17-3.1_all.deb
 b0961cf7abb974070794acf2afbc440b 51292 python optional 
python3-django-celery_3.1.17-3.1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

Processed: your mail

[Debian Bug Tracking System]

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

> tag 833912 moreinfo
Bug #833912 [ftp.debian.org] RM: openjpeg -- RoQA; superseded by openjpeg2
Added tag(s) moreinfo.
> block 833912 by 826828 826808 826806 833873
Bug #833912 [ftp.debian.org] RM: openjpeg -- RoQA; superseded by openjpeg2
833912 was not blocked by any bugs.
833912 was not blocking any bugs.
Added blocking bug(s) of 833912: 826828, 833873, 826806, and 826808
> --
Stopping processing here.

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

Bug#833913: debian-keyring: FTBFS when built with dpkg-buildpackage -A (missing build-depends on gnupg)

[Santiago Vila]

Package: src:debian-keyring
Version: 2016.07.02
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   dh_auto_build -i
make -j1
make[1]: Entering directory '/<>'
cat debian-keyring-gpg/0x* > output/keyrings/debian-keyring.gpg
cat debian-maintainers-gpg/0x* > output/keyrings/debian-maintainers.gpg
cat debian-nonupload-gpg/0x* > output/keyrings/debian-nonupload.gpg
cat debian-role-keys-gpg/0x* > output/keyrings/debian-role-keys.gpg
cat emeritus-keyring-gpg/0x* > output/keyrings/emeritus-keyring.gpg
cat emeritus-keyring-pgp/0x* > output/keyrings/emeritus-keyring.pgp
cat removed-keys-gpg/0x* > output/keyrings/removed-keys.gpg
cat removed-keys-pgp/0x* > output/keyrings/removed-keys.pgp
cd output; sha512sum keyrings/* > sha512sums.txt
cp README output/
cp debian/changelog output/
make[1]: Leaving directory '/<>'
   dh_auto_test -i
make -j1 test
make[1]: Entering directory '/<>'
./runtests
t/at-least-2048.t: 7: t/at-least-2048.t: gpg: not found
t/at-least-2048.t: 7: t/at-least-2048.t: gpg: not found
t/at-least-2048.t: 7: t/at-least-2048.t: gpg: not found
t/at-least-2048.t: 7: t/at-least-2048.t: gpg: not found
t/dm-vs-dd.t: 7: t/dm-vs-dd.t: gpg: not found
test t/dm-vs-dd.t failed
t/no-expired.t: 7: t/no-expired.t: gpg: not found
t/no-expired.t: 7: t/no-expired.t: gpg: not found
t/no-expired.t: 7: t/no-expired.t: gpg: not found
t/no-revoked.t: 7: t/no-revoked.t: gpg: not found
t/no-revoked.t: 7: t/no-revoked.t: gpg: not found
t/no-revoked.t: 7: t/no-revoked.t: gpg: not found
** failed 1/5 tests
Makefile:37: recipe for target 'test' failed
make[1]: *** [test] Error 1
make[1]: Leaving directory '/<>'
dh_auto_test: make -j1 test returned exit code 2
debian/rules:6: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The gnupg package is not "Essential: yes". To reproduce, please try to
build the package on a chroot not having gnupg installed (sbuild now
allows this).

Once that "dpkg-buildpackage -A" work properly, the package would be
suitable to be uploaded in source-only form if you wish.

Thanks.

Processed: severity of 833181 is grave

[Debian Bug Tracking System]

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

> severity 833181 grave
Bug #833181 [libreoffice-draw] libreoffice-draw: I/O general error when saving 
when libreoffice-impress isn't installed
Severity set to 'grave' from 'serious'
> thanks
Stopping processing here.

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

Processed: found 833181 in 1:5.2.0-1

[Debian Bug Tracking System]

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

> found 833181 1:5.2.0-1
Bug #833181 [libreoffice-draw] libreoffice-draw: I/O general error when saving 
when libreoffice-impress isn't installed
Marked as found in versions libreoffice/1:5.2.0-1.
> thanks
Stopping processing here.

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

Processed: found 833181 in 1:5.2.0-1

[Debian Bug Tracking System]

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

> found 833181 1:5.2.0-1
Bug #833181 [libreoffice-draw] libreoffice-draw: I/O general error when saving 
when libreoffice-impress isn't installed
Ignoring request to alter found versions of bug #833181 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#833904: haskell-blogliterately: FTBFS: fails with -ENOENT

[Mattia Rizzolo]

source: haskell-blogliterately
version: 0.8.4-1
severity: serious
control: block 819530 by -1

Dear maintainer,

your package failed to build from source on all buildds:

https://buildd.debian.org/status/logs.php?pkg=haskell-blogliterately=0.8.4-1=sid


dpkg-buildpackage: info: source package haskell-blogliterately
dpkg-buildpackage: info: source version 0.8.4-1
dpkg-buildpackage: info: source distribution unstable
 dpkg-source --before-build haskell-blogliterately-0.8.4
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
dh_listpackages: -s/--same-arch is deprecated; please use -a/--arch instead
test -x debian/rules
dh_clean 
. /usr/share/haskell-devscripts/Dh_Haskell.sh && \
clean_recipe
Running rm -rf dist dist-ghc dist-ghcjs dist-hugs debian/hlibrary.setup 
Setup.hi Setup.ho Setup.o .\*config\*
Running rm -f configure-ghc-stamp configure-ghcjs-stamp build-ghc-stamp 
build-ghcjs-stamp build-hugs-stamp build-haddock-stamp
Running rm -rf debian/tmp-inst-ghc debian/tmp-inst-ghcjs
Running rm -f debian/extra-depends-ghc debian/extra-depends-ghcjs
Running rm -f debian/libghc-blogliterately-doc.links 
debian/libghcjs-blogliterately-doc.links
Running rm -f debian/hlibrary.Makefile
Running rm -rf debian/dh_haskell_shlibdeps
 debian/rules build-arch
dh_listpackages: -s/--same-arch is deprecated; please use -a/--arch instead
test -x debian/rules
mkdir -p "."
CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
. /usr/share/haskell-devscripts/Dh_Haskell.sh && \
make_setup_recipe
Running ghc --make Setup.hs -o debian/hlibrary.setup
[1 of 1] Compiling Main ( Setup.hs, Setup.o )
Linking debian/hlibrary.setup ...
. /usr/share/haskell-devscripts/Dh_Haskell.sh && \
configure_recipe
Running debian/hlibrary.setup configure --ghc -v2 
--package-db=/var/lib/ghc/package.conf.d --prefix=/usr 
--libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib 
--builddir=dist-ghc --ghc-option=-optl-Wl\,-z\,relro 
--haddockdir=/usr/lib/ghc-doc/haddock/blogliterately-0.8.4/ 
--datasubdir=blogliterately 
--htmldir=/usr/share/doc/libghc-blogliterately-doc/html/ 
--enable-library-profiling
Configuring BlogLiterately-0.8.4...
Dependency BlogLiterately -any: using BlogLiterately-0.8.4
Dependency HTTP ==4000.3.*: using HTTP-4000.3.3
Dependency HaXml >=1.22 && <1.26: using HaXml-1.25.3
Dependency base >=4.0 && <4.10: using base-4.8.2.0
Dependency blaze-html >=0.5 && <0.9: using blaze-html-0.8.1.1
Dependency bool-extras -any: using bool-extras-0.4.0
Dependency bytestring -any: using bytestring-0.10.6.0
Dependency cmdargs >=0.9.5 && <0.11: using cmdargs-0.10.14
Dependency containers -any: using containers-0.5.6.2
Dependency data-default >=0.5 && <0.8: using data-default-0.5.3
Dependency directory -any: using directory-1.2.2.0
Dependency filepath -any: using filepath-1.4.0.0
Dependency haxr ==3000.11.*: using haxr-3000.11.1.6
Dependency highlighting-kate >=0.5 && <0.7: using highlighting-kate-0.6.2.1
Dependency hscolour >=1.20 && <1.25: using hscolour-1.24.1
Dependency lens >=3.8 && <4.15: using lens-4.13
Dependency mtl -any: using mtl-2.2.1
Dependency pandoc >=1.14 && <1.18: using pandoc-1.17.0.3
Dependency pandoc-citeproc >=0.1.2 && <0.11: using pandoc-citeproc-0.9.1.1
Dependency pandoc-types ==1.16.*: using pandoc-types-1.16.1
Dependency parsec >=3 && <3.2: using parsec-3.1.11
Dependency process -any: using process-1.2.3.0
Dependency split >=0.1.4 && <0.3: using split-0.2.3.1
Dependency strict ==0.3.*: using strict-0.3.2
Dependency tagsoup >=0.13.4 && <0.15: using tagsoup-0.13.10
Dependency temporary >=1.1 && <1.3: using temporary-1.2.0.4
Dependency transformers >=0.3 && <0.6: using transformers-0.4.2.0
Using Cabal-1.22.5.0 compiled by ghc-7.10
Using compiler: ghc-7.10.3
Using install prefix: /usr
Binaries installed in: /usr/bin
Libraries installed in:
/usr/lib/haskell-packages/ghc/lib/x86_64-linux-ghc-7.10.3/BlogLiterately-0.8.4-1Y12PVNXp5zBAdTLBw5Pos
Private binaries installed in: /usr/lib
Data files installed in: /usr/share/blogliterately
Documentation installed in:
/usr/share/doc/x86_64-linux-ghc-7.10.3/BlogLiterately-0.8.4
Configuration files installed in: /usr/etc
No alex found
Using ar found on system at: /usr/bin/ar
No c2hs found
No cpphs found
Using gcc version 6.1.1 found on system at: /usr/bin/gcc
Using ghc version 7.10.3 found on system at: /usr/bin/ghc
Using ghc-pkg version 7.10.3 found on system at: /usr/bin/ghc-pkg
No ghcjs found
No ghcjs-pkg found
No greencard found
Using haddock version 2.16.1 found on system at: /usr/bin/haddock
No happy found
Using haskell-suite found on system at: haskell-suite-dummy-location
Using haskell-suite-pkg found on system at: haskell-suite-pkg-dummy-location
No hmake found
Using hpc version 0.67 found on system at: /usr/bin/hpc
Using hsc2hs version 0.67 found on system at: /usr/bin/hsc2hs
Using hscolour version 1.24 found on system at: /usr/bin/HsColour
No jhc found
Using ld found on system at: /usr/bin/ld
No lhc found
No lhc-pkg found
No 

Bug#833902: jitsi: unable to install jitsi on Debian testing

[shirish शिरीष]

Source: jitsi
Version: 2.5.5313-1
Justification: renders package unusable
Severity: grave

Dear Maintainer,
Jitsi is still uninstallable on amd64 -

[$] sudo aptitude install jitsi -y

[sudo] password for shirish:
The following NEW packages will be installed:
  jitsi{b} jitsi-common{a} jitsi-jni{a}
0 packages upgraded, 3 newly installed, 0 to remove and 3 not upgraded.
Need to get 8,423 kB of archives. After unpacking 31.5 MB will be used.
The following packages have unmet dependencies:
 jitsi : Depends: libjitsi (>= 415-0) which is a virtual package and
is not provided by any available package

 Depends: libjitsi-jni (>= 415-0) which is a virtual package
and is not provided by any available package

 Depends: libphonenumber6-java which is a virtual package and
is not provided by any available package

The following actions will resolve these dependencies:

 Keep the following packages at their current version:
1) jitsi [Not Installed]

No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.


As far as dependencies are concerned, apart from libjitsi and
libjitsi-jni which probably needs to be provided by jitsi itself ,
libphonenumber6-java has been superseded by libphonenumber7-java so a
rebuild or/and an NMU would be needed to take care of the changed
dependancy.

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

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

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8