Bug#798888: ntfs-3g: pretends to be a library in a broken way

[GCS]

Hi,

On Sun, Sep 13, 2015 at 10:14 PM, Jonathan Wiltshire  wrote:
> ntfs-3g ships shared objects in a non-private location and these are used
> by other packages. ntfs-3g does not have a proper shared library package.
>
> Currently ntfs-3g advertises its ABI through a virtual package. This makes it
> difficult to detect breakage in other packages when that ABI changes.
>
> Upstream appears to want to bump ABI regularly.
 There's a new upstream version which starts an other transition.
Created a separate library package with the actual SONAME naming.
Tested that partclone and testdisk build fine with it and both picks
up the correct (real) dependency (binNMUs will be fine).
The libraries will be co-installable and I don't use conflicts with
the old ones to help smooth transitions.

Before I do the upload[1], I'm open for any critics.

Regards,
Laszlo/GCS
[1] dget -x http://www.barcikacomp.hu/gcs/ntfs-3g_2015.3.14AR.2-1.dsc

Bug#802874: mariadb-10.0: Various security fixes from 10.0.22 release

[Salvatore Bonaccorso]

Source: mariadb-10.0
Version: 10.0.16-1
Severity: grave
Tags: security upstream

Hi

Various CVEs were fixed in the 10.0.21 and 10.0.22 release:

https://mariadb.com/kb/en/mariadb/mariadb-10021-release-notes/
https://mariadb.com/kb/en/mariadb/mariadb-10022-release-notes/

Regards,
Salvatore

Bug#799191: marked as done (RM: emesene -- obsolete, RC-buggy, unmaintained, unused)

[Debian Bug Tracking System]

Your message dated Sat, 24 Oct 2015 17:36:30 +
with message-id 
and subject line Bug#799191: Removed package(s) from unstable
has caused the Debian Bug report #799191,
regarding RM: emesene -- obsolete, RC-buggy, unmaintained, unused
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.)


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

Upstream development has stalled with the shutdown of MSN,
it uses deprecated libs (python-webkit, gstreamer 0.10,
modemmanager1), the former primary maintainer is MIA and
popcon is virtually non-existant.

Please address the outstanding bugs or reassign this to
ftp.debian.org for removal.

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

   emesene | 2.12.5+dfsg-1 | source, all

--- Reason ---
obsolete, RC-buggy, unmaintained, unused
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

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

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

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#785843: marked as done (emesene: Please update to GStreamer 1.x)

[Debian Bug Tracking System]

Your message dated Sat, 24 Oct 2015 17:36:37 +
with message-id 
and subject line Bug#799191: Removed package(s) from unstable
has caused the Debian Bug report #785843,
regarding emesene: Please update to GStreamer 1.x
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.)


-- 
785843: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785843
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: emesene
Severity: important
User: sl...@debian.org
Usertags: gstreamer0.10-removal

Hi maintainer,

your package emesene currently still depends on GStreamer 0.10.

GStreamer 0.10 is no longer maintained and supported by the upstream
project since almost 3 years, and contains many known bugs that are
fixed in the new 1.x release series of GStreamer. Next to many bug
fixes, the new release series also contains many other improvements,
new features and a more streamlined API.

For the next Debian release GStreamer 0.10 is planned to be removed,
and if your package is not updated it might not be included in the
release. Please update your package to use the new version as soon as
possible.

If you need any help with porting or have further questions, please
feel free to also contact me privately.

Best regards, Sebastian

PS: See https://bugs.debian.org/785198 and
https://lists.debian.org/debian-devel/2015/05/msg00335.html for some
further discussion.
--- End Message ---
--- Begin Message ---
Version: 2.12.5+dfsg-1+rm

Dear submitter,

as the package emesene has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/799191

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

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#801559: marked as done (golang-github-sirupsen-logrus-dev: fails to upgrade from 'testing' - trying to overwrite /usr/share/gocode/src/github.com/Sirupsen/logrus/formatters/logstash/logstash_test.

[Debian Bug Tracking System]

Your message dated Sat, 24 Oct 2015 13:34:40 +
with message-id 
and subject line Bug#801559: fixed in golang-logrus 0.8.7-2
has caused the Debian Bug report #801559,
regarding golang-github-sirupsen-logrus-dev: fails to upgrade from 'testing' - 
trying to overwrite 
/usr/share/gocode/src/github.com/Sirupsen/logrus/formatters/logstash/logstash_test.go
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.)


-- 
801559: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801559
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: golang-github-sirupsen-logrus-dev
Version: 0.7.3-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + golang-logrus-dev

Hi,

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

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

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

  Selecting previously unselected package golang-github-sirupsen-logrus-dev.
  (Reading database ... 
(Reading database ... 7485 files and directories currently installed.)
  Preparing to unpack .../golang-github-sirupsen-logrus-dev_0.7.3-2_all.deb ...
  Unpacking golang-github-sirupsen-logrus-dev (0.7.3-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/golang-github-sirupsen-logrus-dev_0.7.3-2_all.deb 
(--unpack):
   trying to overwrite 
'/usr/share/gocode/src/github.com/Sirupsen/logrus/formatters/logstash/logstash_test.go',
 which is also in package golang-logrus-dev 0.7.3-1
  Preparing to unpack .../golang-logrus-dev_0.7.3-2_all.deb ...
  Unpacking golang-logrus-dev (0.7.3-2) over (0.7.3-1) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/golang-github-sirupsen-logrus-dev_0.7.3-2_all.deb


cheers,

Andreas


golang-logrus-dev_0.7.3-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: golang-logrus
Source-Version: 0.8.7-2

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

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

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

Debian distribution maintenance software
pp.
Tianon Gravi  (supplier of updated golang-logrus package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 24 Oct 2015 06:21:25 -0700
Source: golang-logrus
Binary: golang-github-sirupsen-logrus-dev golang-logrus-dev
Architecture: source
Version: 0.8.7-2
Distribution: unstable
Urgency: medium
Maintainer: Jessie Frazelle 
Changed-By: Tianon Gravi 
Description:
 golang-github-sirupsen-logrus-dev - Logrus: a logging library for Go
 golang-logrus-dev - Transitional package for golang-github-sirupsen-logrus-dev
Closes: 801559
Changes:
 golang-logrus (0.8.7-2) unstable; urgency=medium
 .
   * Fix Replaces/Breaks version number to be correct (Closes: #801559).
Checksums-Sha1:
 1c7d6ee6847718f9aacbd44900b7e60d81b9d28c 2313 golang-logrus_0.8.7-2.dsc
 cd854d8c86ce7323088e04540f90598f91ba 5064 
golang-logrus_0.8.7-2.debian.tar.xz
Checksums-Sha256:
 3b26508b5e2227eb80b4d4a68d6c98284ae7e96b9eddee814eeed8f6fcca6751 2313 
golang-logrus_0.8.7-2.dsc
 9f468dc3a45e993d90856b2cfb8891410404a2a105c8a8fe01821bfa1f7a1adb 5064 
golang-logrus_0.8.7-2.debian.tar.xz
Files:
 af02b2f6f086329948bedd47752b8618 2313 devel extra golang-logrus_0.8.7-2.dsc
 55ece85f2ac7fa8e008b187f60219589 5064 devel extra 
golang-logrus_0.8.7-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJWK4b4AAoJEANqnCW/NX3UnjwP/jrLQ9aQPeGoZIV1WdqFeQ4A
sq2FUxd5WwIEmBCbX/cQbskaPNpvo80OaRsE5XY3U3FV3JxfB1R00mqoFbIlA4D1
3QgvWIrE4DvCADtv3G1SWXp3AiSVQI8oeHSLVNQ24M6VGzzZfkI0JT7BigqiXmEh
PGDMUi7yoIBYdToyDrX0LMsA/6/C5UgVNK/ybQLaSBUAtpdMaFcgpxC0xh/ETKNq
kl5SqThIUTK+88orRZ8HC6xbhVJwBzBdVY20sYSEwo3F2vkLWcsfXCLeeZv/ANVz
nDP2iXVvUl1v7r05TPDd1sSVfRvV+IxAuZ9EoeA5GE4zsqfI+oh10cTJ0Yslluf1

Processed: tagging 785864

[Debian Bug Tracking System]

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

> tags 785864 + pending
Bug #785864 [src:pocketsphinx] pocketsphinx: Please update to GStreamer 1.x
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#799817: marked as done (foundry: FTBFS: operator<< missing on ostream (missing headers?))

[Debian Bug Tracking System]

Your message dated Sat, 24 Oct 2015 17:51:21 +
with message-id 
and subject line Bug#802726: Removed package(s) from unstable
has caused the Debian Bug report #799817,
regarding foundry: FTBFS: operator<< missing on ostream (missing headers?)
to be marked as done.

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

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


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

touch stage1/parse_cst_lex.hpp
g++ -D_FORTIFY_SOURCE=2 -Istage1 -I. -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -W -Wall -Werror -std=c++0x -MD -MF 
stage1/.bison_output_visitor.d -o stage1/bison_output_visitor.o -c 
bison_output_visitor.cpp
bison_output_visitor.cpp: In member function ‘virtual void 
foundry::parse::bison_output_visitor::visit(const foundry::parse::root&)’:
bison_output_visitor.cpp:31:13: error: no match for ‘operator<<’ (operand types 
are ‘std::ostream {aka std::basic_ostream}’ and ‘const char [3]’)
 out << "%{" << std::endl;
 ^
In file included from /usr/include/c++/5/string:52:0,
 from ./parse_tree.hpp:5,
 from bison_output_visitor.h:4,
 from bison_output_visitor.cpp:5:
/usr/include/c++/5/bits/basic_string.h:5170:5: note: candidate: template std::basic_ostream<_CharT, _Traits>& 
std::operator<<(std::basic_ostream<_CharT, _Traits>&, const 
std::__cxx11::basic_string<_CharT, _Traits, _Alloc>&)
 operator<<(basic_ostream<_CharT, _Traits>& __os,
 ^
/usr/include/c++/5/bits/basic_string.h:5170:5: note:   template argument 
deduction/substitution failed:
bison_output_visitor.cpp:31:16: note:   mismatched types ‘const 
std::__cxx11::basic_string<_CharT, _Traits, _Alloc>’ and ‘const char [3]’
 out << "%{" << std::endl;
^
bison_output_visitor.cpp:31:24: error: ‘endl’ is not a member of ‘std’
 out << "%{" << std::endl;
^
bison_output_visitor.cpp:32:13: error: no match for ‘operator<<’ (operand types 
are ‘std::ostream {aka std::basic_ostream}’ and ‘const char [11]’)
 out << "#include \"" << basename << "_cst.hpp\"" << std::endl;
 ^
In file included from /usr/include/c++/5/string:52:0,
 from ./parse_tree.hpp:5,
 from bison_output_visitor.h:4,
 from bison_output_visitor.cpp:5:
/usr/include/c++/5/bits/basic_string.h:5170:5: note: candidate: template std::basic_ostream<_CharT, _Traits>& 
std::operator<<(std::basic_ostream<_CharT, _Traits>&, const 
std::__cxx11::basic_string<_CharT, _Traits, _Alloc>&)
 operator<<(basic_ostream<_CharT, _Traits>& __os,
 ^
/usr/include/c++/5/bits/basic_string.h:5170:5: note:   template argument 
deduction/substitution failed:
bison_output_visitor.cpp:32:16: note:   mismatched types ‘const 
std::__cxx11::basic_string<_CharT, _Traits, _Alloc>’ and ‘const char [11]’
 out << "#include \"" << basename << "_cst.hpp\"" << std::endl;
^
bison_output_visitor.cpp:32:61: error: ‘endl’ is not a member of ‘std’
 out << "#include \"" << basename << "_cst.hpp\"" << std::endl;
 ^
bison_output_visitor.cpp:33:13: error: no match for ‘operator<<’ (operand types 
are ‘std::ostream {aka std::basic_ostream}’ and ‘const char [11]’)
 out << "#include \"" << basename << "_parse.hpp\"" << std::endl;
 ^
In file included from /usr/include/c++/5/string:52:0,
 from ./parse_tree.hpp:5,
 from bison_output_visitor.h:4,
 from bison_output_visitor.cpp:5:
/usr/include/c++/5/bits/basic_string.h:5170:5: note: candidate: template std::basic_ostream<_CharT, _Traits>& 
std::operator<<(std::basic_ostream<_CharT, _Traits>&, const 
std::__cxx11::basic_string<_CharT, _Traits, _Alloc>&)
 operator<<(basic_ostream<_CharT, _Traits>& __os,
 ^
/usr/include/c++/5/bits/basic_string.h:5170:5: note:   template argument 
deduction/substitution failed:
bison_output_visitor.cpp:33:16: note:   mismatched types ‘const 
std::__cxx11::basic_string<_CharT, _Traits, _Alloc>’ and ‘const char [11]’
 out << "#include \"" << basename << "_parse.hpp\"" << std::endl;
^

Processed: tagging 802874

[Debian Bug Tracking System]

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

> tags 802874 + fixed-upstream
Bug #802874 [src:mariadb-10.0] mariadb-10.0: Various security fixes from 
10.0.22 release
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Processed: found 802874 in 10.0.15-1

[Debian Bug Tracking System]

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

> # mark as found in common anchestor
> found 802874 10.0.15-1
Bug #802874 [src:mariadb-10.0] mariadb-10.0: Various security fixes from 
10.0.22 release
Marked as found in versions mariadb-10.0/10.0.15-1.
> thanks
Stopping processing here.

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

Bug#786347: marked as done (monav: Please consider dropping qtmobility as build dependency)

[Debian Bug Tracking System]

Your message dated Sat, 24 Oct 2015 17:44:34 +
with message-id 
and subject line Bug#802664: Removed package(s) from unstable
has caused the Debian Bug report #786347,
regarding monav: Please consider dropping qtmobility as build dependency
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.)


-- 
786347: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786347
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: monav
Version: 0.3-8
Severity: normal

Hi! Your package currently build depends qtmobility which in turn depends on
gstreamer 0.1 which is going to be removed from the archive, see #785855.

Fixing qtmobility means dropping it's multimedia part. But we also currently
have only 3 packages depending on it, one of it being monav, so we are
considering removing qtmobility from the archive too.

The best possible solution here would be to port monav to Qt5.

Another possible option would be to drop whatever features are provided by
qtmobility in monav, if possible.

Kinds regards, Lisandro.

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Version: 0.3-8+rm

Dear submitter,

as the package monav has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/802664

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

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#785892: marked as done (minbar: Please update to GStreamer 1.x)

[Debian Bug Tracking System]

Your message dated Sat, 24 Oct 2015 17:45:54 +
with message-id 
and subject line Bug#802709: Removed package(s) from unstable
has caused the Debian Bug report #785892,
regarding minbar: Please update to GStreamer 1.x
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.)


-- 
785892: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785892
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: minbar
Severity: important
User: sl...@debian.org
Usertags: gstreamer0.10-removal

Hi maintainer,

your package minbar currently still depends on GStreamer 0.10.

GStreamer 0.10 is no longer maintained and supported by the upstream
project since almost 3 years, and contains many known bugs that are
fixed in the new 1.x release series of GStreamer. Next to many bug
fixes, the new release series also contains many other improvements,
new features and a more streamlined API.

For the next Debian release GStreamer 0.10 is planned to be removed,
and if your package is not updated it might not be included in the
release. Please update your package to use the new version as soon as
possible.

If you need any help with porting or have further questions, please
feel free to also contact me privately.

Best regards, Sebastian

PS: See https://bugs.debian.org/785198 and
https://lists.debian.org/debian-devel/2015/05/msg00335.html for some
further discussion.
--- End Message ---
--- Begin Message ---
Version: 0.2.1-9+rm

Dear submitter,

as the package minbar has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/802709

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

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#788767: marked as done (monav: FTBFS with gcc 4.9/mapnik 3.0.0: requires flags for c++11 support)

[Debian Bug Tracking System]

Your message dated Sat, 24 Oct 2015 17:44:34 +
with message-id 
and subject line Bug#802664: Removed package(s) from unstable
has caused the Debian Bug report #788767,
regarding monav: FTBFS with gcc 4.9/mapnik 3.0.0: requires flags for c++11 
support
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.)


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

Dear Maintainer,

The package fails to build on sid, inside libmapnik:

make[4]: Entering directory '/tmp/buildd/monav-0.3/plugins/osmrenderer'
[...]
In file included from /usr/include/c++/4.9/cstdint:35:0,
 from /usr/include/mapnik/global.hpp:27,
 from /usr/include/mapnik/color.hpp:28,
 from /usr/include/mapnik/map.hpp:28,
 from mapnikrenderer.cpp:27:
/usr/include/c++/4.9/bits/c++0x_warning.h:32:2: error: #error This file 
requires compiler and library support for the ISO C++ 2011 standard. This 
support is currently experimental, and must be enabled with the -std=c++11 or 
-std=gnu++11 compiler options.
[..]
mapnikrenderer.cpp:32:31: fatal error: mapnik/graphics.hpp: No such file or 
directory
 #include 
   ^

Maybe this is a problem with libmapnik instead?  I'm not sure what their 
expectation is.

 doesn't strike me as a very important header.


Full build logs can be seen on the Reproducible Builds builder:
https://reproducible.debian.net/rb-pkg/unstable/amd64/monav.html

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

Kernel: Linux 3.19.0-20-generic (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Version: 0.3-8+rm

Dear submitter,

as the package monav has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/802664

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

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#802880: marked as done (package is uninstallable due to Qt 5.5 transition)

[Debian Bug Tracking System]

Your message dated Sat, 24 Oct 2015 16:29:50 +0200
with message-id <562b95de.9060...@yahoo.it>
and subject line qtcreator: not really a bug
has caused the Debian Bug report #802880,
regarding package is uninstallable due to Qt 5.5 transition
to be marked as done.

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

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


-- 
802880: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802880
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qtcreator
Version: 3.5.0+dfsg-2
Severity: serious

Hi,

I can't install qtcreator anymore, since unstable is now on Qt 5.5:

  klump:~> sudo LANG=C apt-get install qtcreator 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  
  The following packages have unmet dependencies:
   qtcreator : Depends: qtbase-abi-5-4-2
   Depends: qtdeclarative-abi-5-4-1
   Recommends: qtdeclarative5-dev-tools
   Recommends: qttools5-dev-tools but it is not going to be 
installed
  E: Unable to correct problems, you have held broken packages.

I assume this needs a newer version from upstream.

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

Kernel: Linux 4.1.4 (SMP w/40 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi, this bug is invalid.

During transitions it is normal to have uninstallable packages in sid,
until they get rebuilt on top of the new library.

qtcreator has been rebuilt around 20 hours ago.

3.5.0+dfsg-2+b1
Rebuild against qtbase-abi-5-5-1.

as you can see here [1] here [2] and here [3].
Of course some architectures are still outdated, and they will be for
a while, since now qtcreator depends on llvm-toolchain-snapshot, and
the latter won't migrate into testing for really some time (for sure
not before 3.8 it gets released as stable, and it won't for a few months
).

cheers,

G.

[1]
https://buildd.debian.org/status/package.php?p=qtcreator=unstable
[2] https://release.debian.org/transitions/html/qtbase-abi-5-5-1.html
[3] https://packages.debian.org/sid/amd64/qtcreator/download
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWK5XeAAoJEPNPCXROn13Z8K4P/3TDLXAnNEh9P25aAogoCxNf
iF77ELhAY8iN3WS3a/IriA84GMix79YLISaxz98bkRpSNNUyN+rXfw6mMCMJ3Ha4
5semjJPpObxEYFlIkWAZq9P2f+3Zsj3giiPmc47JUG1mHg/lBsHkXwiJkFpJd2P8
RwF/v8RDe7+OuKa88SRJEEanUMDcZCHK3KK9757ojv/ldUH9kTbu7GSTav8ZT+lF
ubif7ZMeBReQCeiH40kjVZ3TN7DOjtNpRJoLvmdp5zJPAxzBDREeewdShfmc7Aax
Iif2e5R3kmgsZA9QaYlEgEmysX2eWtUdFM0hMM28vpd1pc7k7GkV5Nvw3jg4olPa
HRDKgxCiwRBjyTNbYzUEuICe9VB+e18pL1+kukevG2hRfXJtvysmzlZLVhyePq4I
zGDoGDExslS7VoAic12ZehYKfcSk3MRegYO/Z00grSbtzJWHfTxfTHCoOxVjRMWM
l9QU8Cc1Io8G9A/GU3pHC0agNFCancUAJ1AO6GIYAmf6pOWaPmooRcz2sg1IhLLM
r3LaFkGAD/nMs7vP0d5EVnkBPxJNyaxJZ2csQa7eB+MSt2RkvPN/0CPO+7Jo3NUV
KdrxuVjXpQR+panASgSU4geI2r8+WOubRQvb2icz00kvS0V44tXAIWgMjLknopll
sNOuxHBfSJTnngsfzd3f
=WN4P
-END PGP SIGNATURE End Message ---

Bug#802887: python-kombu-doc and python-django-uwsgi-doc: error when trying to install together

[Ralf Treinen]

Package: python-django-uwsgi-doc,python-kombu-doc
Version: python-django-uwsgi-doc/0.1.3-1
Version: python-kombu-doc/3.0.27-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2015-10-24
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:


Selecting previously unselected package fonts-lato.
(Reading database ... 10923 files and directories currently installed.)
Preparing to unpack .../fonts-lato_2.0-1_all.deb ...
Unpacking fonts-lato (2.0-1) ...
Selecting previously unselected package fonts-font-awesome.
Preparing to unpack .../fonts-font-awesome_4.4.0~dfsg-1_all.deb ...
Unpacking fonts-font-awesome (4.4.0~dfsg-1) ...
Selecting previously unselected package libjs-jquery.
Preparing to unpack .../libjs-jquery_1.11.3+dfsg-4_all.deb ...
Unpacking libjs-jquery (1.11.3+dfsg-4) ...
Selecting previously unselected package libjs-underscore.
Preparing to unpack .../libjs-underscore_1.7.0~dfsg-1_all.deb ...
Unpacking libjs-underscore (1.7.0~dfsg-1) ...
Selecting previously unselected package libjs-sphinxdoc.
Preparing to unpack .../libjs-sphinxdoc_1.3.1-7_all.deb ...
Unpacking libjs-sphinxdoc (1.3.1-7) ...
Selecting previously unselected package libjs-modernizr.
Preparing to unpack .../libjs-modernizr_2.6.2+ds1-1_all.deb ...
Unpacking libjs-modernizr (2.6.2+ds1-1) ...
Selecting previously unselected package sphinx-rtd-theme-common.
Preparing to unpack .../sphinx-rtd-theme-common_0.1.9-1_all.deb ...
Unpacking sphinx-rtd-theme-common (0.1.9-1) ...
Selecting previously unselected package python-django-uwsgi-doc.
Preparing to unpack .../python-django-uwsgi-doc_0.1.3-1_all.deb ...
Unpacking python-django-uwsgi-doc (0.1.3-1) ...
Selecting previously unselected package python-kombu-doc.
Preparing to unpack .../python-kombu-doc_3.0.27-1_all.deb ...
Unpacking python-kombu-doc (3.0.27-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/python-kombu-doc_3.0.27-1_all.deb (--unpack):
 trying to overwrite '/usr/share/doc-base/python-kombu-doc', which is also in 
package python-django-uwsgi-doc 0.1.3-1
Errors were encountered while processing:
 /var/cache/apt/archives/python-kombu-doc_3.0.27-1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/share/doc-base/python-kombu-doc

This bug has been filed against both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may then
also register in the BTS that the other package is affected by the bug.

-Ralf.

PS: for more information about the detection of file overwrite errors
of this kind see http://qa.debian.org/dose/file-overwrites.html.

Bug#801276: marked as done (fritzing: uninstallable in sid due to too strict dependency on fritzing-parts)

[Debian Bug Tracking System]

Your message dated Sat, 24 Oct 2015 16:20:11 +
with message-id 
and subject line Bug#801276: fixed in fritzing-parts 0.9.2b+dfsg-2
has caused the Debian Bug report #801276,
regarding fritzing: uninstallable in sid due to too strict dependency on 
fritzing-parts
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.)


-- 
801276: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801276
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fritzing
Version: 0.9.2b+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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


You have a 
Depends: fritzing-parts (= ${source:Version}),
which is wrong for a package from a different source package.
You probably want
Depends: fritzing-parts (>= ${source:UpstreamVersion})
instead. And maybe also
Depends: fritzing-parts (<< SOMEUPSTREAMVERSIONTHATMAYBEINCOMPATIBLE~)


Cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: fritzing-parts
Source-Version: 0.9.2b+dfsg-2

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

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

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

Debian distribution maintenance software
pp.
Georges Khaznadar  (supplier of updated fritzing-parts 
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: Sat, 24 Oct 2015 17:43:47 +0200
Source: fritzing-parts
Binary: fritzing-parts
Architecture: source all
Version: 0.9.2b+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Enrique Hernández Bello 
Changed-By: Georges Khaznadar 
Description:
 fritzing-parts - Easy-to-use electronic design software (parts files)
Closes: 801276
Changes:
 fritzing-parts (0.9.2b+dfsg-2) unstable; urgency=medium
 .
   * Released once more. Closes: #801276. I repeated also Andreas Beckmann's
 hint to Enrique Hernández Bello: "You probably want:
 Depends: fritzing-parts (>= ${source:UpstreamVersion})"
Checksums-Sha1:
 8e9f8621d505464c8fabea1ce2402399a5c0f227 1989 fritzing-parts_0.9.2b+dfsg-2.dsc
 58ece0dea8aad12a3c80265db1c2b50affdd49d9 19448 
fritzing-parts_0.9.2b+dfsg-2.debian.tar.xz
 4f3920db6e48b3ccca4093c9b2dc1f134c0d7175 9356036 
fritzing-parts_0.9.2b+dfsg-2_all.deb
Checksums-Sha256:
 6be42c9aaef4acc3460890e5c9e7e6bc5ea8941cebaa0480c6ec7e63d262ea90 1989 
fritzing-parts_0.9.2b+dfsg-2.dsc
 9db3c5c3b20a8e4642c3edb87190c683f5dcce0532a43eb947c3bd957e52360c 19448 
fritzing-parts_0.9.2b+dfsg-2.debian.tar.xz
 b8e8f4bfce7761b8d32ffb5500eccd4a3a2f3de307455c3d003cfea443a4f503 9356036 
fritzing-parts_0.9.2b+dfsg-2_all.deb
Files:
 dbd995107324f61939c55a8ad8da7892 1989 electronics optional 
fritzing-parts_0.9.2b+dfsg-2.dsc
 cdb2cb1afa7f80b7f25a40aca6778361 19448 electronics optional 
fritzing-parts_0.9.2b+dfsg-2.debian.tar.xz
 5f693975ba51524649197b69059ed911 9356036 electronics optional 
fritzing-parts_0.9.2b+dfsg-2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIVAwUBViuoWBwoFpBxNq45AQhEjRAAnBj/2Y46G8/XZ8ZbXvHAOqk7fVfSHcNF
uxD+kELcwUoa08nq723HIVWBTD5c5ZiMNtGru8xgrdgJrDJuxNHzpgxkgE8WzZgr
tIY1naI4rQk5zTiLpgfj5wak+vK7dKLPU+3z6+RIC/KY0VG/bso6mqsd0U1fNBg/
E/xKRetbTJblEZNXTPPC5gR7mFFYOUqhQAunI7qNGmC2sq2eRa+wQZKhlzqZx+9h

Bug#785841: marked as done (audiopreview: Please update to GStreamer 1.x)

[Debian Bug Tracking System]

Your message dated Sat, 24 Oct 2015 17:46:54 +
with message-id 
and subject line Bug#802713: Removed package(s) from unstable
has caused the Debian Bug report #785841,
regarding audiopreview: Please update to GStreamer 1.x
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.)


-- 
785841: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785841
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: audiopreview
Severity: important
User: sl...@debian.org
Usertags: gstreamer0.10-removal

Hi maintainer,

your package audiopreview currently still depends on GStreamer 0.10.

GStreamer 0.10 is no longer maintained and supported by the upstream
project since almost 3 years, and contains many known bugs that are
fixed in the new 1.x release series of GStreamer. Next to many bug
fixes, the new release series also contains many other improvements,
new features and a more streamlined API.

For the next Debian release GStreamer 0.10 is planned to be removed,
and if your package is not updated it might not be included in the
release. Please update your package to use the new version as soon as
possible.

If you need any help with porting or have further questions, please
feel free to also contact me privately.

Best regards, Sebastian

PS: See https://bugs.debian.org/785198 and
https://lists.debian.org/debian-devel/2015/05/msg00335.html for some
further discussion.
--- End Message ---
--- Begin Message ---
Version: 0.6-2+rm

Dear submitter,

as the package audiopreview has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/802713

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

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#802713: marked as done (RM: audiopreview - dead upstream, unused, depends on legacy libs)

[Debian Bug Tracking System]

Your message dated Sat, 24 Oct 2015 17:46:49 +
with message-id 
and subject line Bug#802713: Removed package(s) from unstable
has caused the Debian Bug report #802713,
regarding RM: audiopreview - dead upstream, unused, depends on legacy libs
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.)


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

- It's dead upstream and depends on legacy libs scheduled
for removal (gstreamer 0.10)
- Virtually unused according to popcon

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

audiopreview |  0.6-2 | source, amd64, arm64, armel, armhf, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x
audiopreview |   0.6-2+b1 | hurd-i386

--- Reason ---
audiopreview- dead upstream unused depends on legacy libs
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

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

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

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Processed: forcibly merging 793132 802870

[Debian Bug Tracking System]

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

> forcemerge 793132 802870
Bug #793132 [src:xen] xen: FTBFS with glibc 2.21 and gcc-5
Bug #802870 [src:xen] xen: FTBFS: error: array subscript is above array bounds
Severity set to 'normal' from 'serious'
Marked as found in versions xen/4.4.1-9.
Added tag(s) fixed-upstream and upstream.
Bug #793132 [src:xen] xen: FTBFS with glibc 2.21 and gcc-5
Marked as found in versions xen/4.4.1-9+deb8u1.
Added tag(s) sid and stretch.
Merged 793132 802870
> thanks
Stopping processing here.

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

Bug#797234: source-highlight, regina-normal and libstdc++6

[Benjamin Burton]

> That leaves the question: what to do with this bug?

FYI, if a rebuild *is* required then I presume it would be a simple rename from 
libsource-highlight4 to libsource-highlight4v5; see the (tested) patch below.  
I’m happy to NMU this if the maintainer does not have time (which is why the 
changelog entry reads as an NMU).

- Ben.

diff -Nru source-highlight-3.1.8/debian/changelog 
source-highlight-3.1.8/debian/changelog
--- source-highlight-3.1.8/debian/changelog 2015-07-15 06:27:18.0 
+1000
+++ source-highlight-3.1.8/debian/changelog 2015-10-24 20:57:03.0 
+1000
@@ -1,3 +1,10 @@
+source-highlight (3.1.8-1.1) unstable; urgency=low
+
+  * Non-maintainer upload
+  * Rename library packages for g++5 transition (Closes: #797234)
+
+ -- Ben Burton   Sat, 24 Oct 2015 20:56:50 +1000
+
 source-highlight (3.1.8-1) unstable; urgency=low
 
   * New upstream release
diff -Nru source-highlight-3.1.8/debian/control 
source-highlight-3.1.8/debian/control
--- source-highlight-3.1.8/debian/control   2015-07-14 13:41:56.0 
+1000
+++ source-highlight-3.1.8/debian/control   2015-10-24 20:58:32.0 
+1000
@@ -21,7 +21,7 @@
 Package: libsource-highlight-dev
 Section: libdevel
 Architecture: any
-Depends: dpkg (>= 1.15.4) | install-info, libboost-dev, libsource-highlight4 
(= ${binary:Version}), ${misc:Depends}, ${shlibs:Depends}
+Depends: dpkg (>= 1.15.4) | install-info, libboost-dev, libsource-highlight4v5 
(= ${binary:Version}), ${misc:Depends}, ${shlibs:Depends}
 Replaces: source-highlight (<< 3.1.4-1)
 Description: development files for source highlighting library
  These are the development files for the library that underlies the
@@ -30,10 +30,12 @@
  The library can be used by other C++ programs to get source code
  highlighting capabilities.
 
-Package: libsource-highlight4
+Package: libsource-highlight4v5
 Section: libs
 Architecture: any
 Depends: libsource-highlight-common, ${misc:Depends}, ${shlibs:Depends}
+Conflicts: libsource-highlight4
+Replaces: libsource-highlight4
 Description: source highlighting library
  This is the library that underlies the source-highlight program
  suite.  It converts source code to a document with syntax
diff -Nru source-highlight-3.1.8/debian/libsource-highlight4.install 
source-highlight-3.1.8/debian/libsource-highlight4.install
--- source-highlight-3.1.8/debian/libsource-highlight4.install  2013-10-22 
22:58:26.0 +1000
+++ source-highlight-3.1.8/debian/libsource-highlight4.install  1970-01-01 
10:00:00.0 +1000
@@ -1 +0,0 @@
-usr/lib/lib*.so.*
diff -Nru source-highlight-3.1.8/debian/libsource-highlight4v5.install 
source-highlight-3.1.8/debian/libsource-highlight4v5.install
--- source-highlight-3.1.8/debian/libsource-highlight4v5.install
1970-01-01 10:00:00.0 +1000
+++ source-highlight-3.1.8/debian/libsource-highlight4v5.install
2013-10-22 22:58:26.0 +1000
@@ -0,0 +1 @@
+usr/lib/lib*.so.*

Bug#785855: marked as done (qtmobility: Please update to GStreamer 1.x)

[Debian Bug Tracking System]

Your message dated Sat, 24 Oct 2015 17:43:20 +
with message-id 
and subject line Bug#802642: Removed package(s) from unstable
has caused the Debian Bug report #785855,
regarding qtmobility: Please update to GStreamer 1.x
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.)


-- 
785855: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785855
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qtmobility
Severity: important
User: sl...@debian.org
Usertags: gstreamer0.10-removal

Hi maintainer,

your package qtmobility currently still depends on GStreamer 0.10.

GStreamer 0.10 is no longer maintained and supported by the upstream
project since almost 3 years, and contains many known bugs that are
fixed in the new 1.x release series of GStreamer. Next to many bug
fixes, the new release series also contains many other improvements,
new features and a more streamlined API.

For the next Debian release GStreamer 0.10 is planned to be removed,
and if your package is not updated it might not be included in the
release. Please update your package to use the new version as soon as
possible.

If you need any help with porting or have further questions, please
feel free to also contact me privately.

Best regards, Sebastian

PS: See https://bugs.debian.org/785198 and
https://lists.debian.org/debian-devel/2015/05/msg00335.html for some
further discussion.
--- End Message ---
--- Begin Message ---
Version: 1.2.0-3+rm

Dear submitter,

as the package qtmobility has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/802642

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

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#801559: golang-github-sirupsen-logrus-dev: fails to upgrade from 'testing' - trying to overwrite /usr/share/gocode/src/github.com/Sirupsen/logrus/formatters/logstash/logstash_test.go

[Tianon Gravi]

On Mon, 12 Oct 2015 07:00:24 +0200 Andreas Beckmann  wrote:
> It installed fine in 'testing', then the upgrade to 'sid' fails
> because it tries to overwrite other packages files without declaring a
> Breaks+Replaces relation.

Doh, pretty sure I messed up the version number again:

| Replaces: golang-logrus-dev (<< 0.7.3-1~)
| Breaks: golang-logrus-dev (<< 0.7.3-1~)
| Provides: golang-logrus-dev

Should be:

| Replaces: golang-logrus-dev (<< 0.7.3-2~)
| Breaks: golang-logrus-dev (<< 0.7.3-2~)
| Provides: golang-logrus-dev

Will upload a fix shortly.

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#802073: golang-logrus: FTBFS: TestUserSuppliedLevelFieldHasPrefix fails 1 != 1

[Tianon Gravi]

fixed 802073 golang-logrus/0.8.7-1
thanks

This was fixed in the latest upload! :D

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#802073: marked as done (golang-logrus: FTBFS: TestUserSuppliedLevelFieldHasPrefix fails 1 != 1)

[Debian Bug Tracking System]

Your message dated Sat, 24 Oct 2015 06:16:10 -0700
with message-id 

and subject line Re: golang-logrus: FTBFS: TestUserSuppliedLevelFieldHasPrefix 
fails 1 != 1
has caused the Debian Bug report #802073,
regarding golang-logrus: FTBFS: TestUserSuppliedLevelFieldHasPrefix fails 1 != 1
to be marked as done.

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

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


-- 
802073: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802073
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-logrus
Version: 0.7.3-2
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 both on jenkins and locally; guessing it's
not intermittent:

=== RUN TestUserSuppliedLevelFieldHasPrefix
--- FAIL: TestUserSuppliedLevelFieldHasPrefix (0.00s)
assertions.go:160: 

Location:   logrus_test.go:194

Error:  Not equal: 1 (expected)
!= 1 (actual)

=== RUN TestDefaultFieldsAreNotPrefixed
--- PASS: TestDefaultFieldsAreNotPrefixed (0.00s)
=== RUN TestDoubleLoggingDoesntPrefixPreviousFields
--- PASS: TestDoubleLoggingDoesntPrefixPreviousFields (0.00s)

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

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
fixed 802073 golang-logrus/0.8.7-1
thanks

This was fixed in the latest upload! :D

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4--- End Message ---

Processed: Re: golang-logrus: FTBFS: TestUserSuppliedLevelFieldHasPrefix fails 1 != 1

[Debian Bug Tracking System]

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

> fixed 802073 golang-logrus/0.8.7-1
Bug #802073 [src:golang-logrus] golang-logrus: FTBFS: 
TestUserSuppliedLevelFieldHasPrefix fails 1 != 1
Marked as fixed in versions golang-logrus/0.8.7-1.
> thanks
Stopping processing here.

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

Bug#802880: closed by Gianfranco Costamagna <costamagnagianfra...@yahoo.it> (qtcreator: not really a bug)

[Steinar H. Gunderson]

fixed 802280 qtcreator/3.5.0+dfsg-2+b1
thanks

On Sat, Oct 24, 2015 at 02:33:04PM +, Debian Bug Tracking System wrote:
> Hi, this bug is invalid.

Uhm, no?

> During transitions it is normal to have uninstallable packages in sid,
> until they get rebuilt on top of the new library.

It's still a bug.

> qtcreator has been rebuilt around 20 hours ago.
> 
> 3.5.0+dfsg-2+b1
> Rebuild against qtbase-abi-5-5-1.

If so, the binNMU fixes this bug (and should nominally have a Closes: line
with the bug number, except the bug was probably filed after the binNMU was
scheduled). Thank you for taking care of that.

In particular, having a bug in the BTS will enable users to see that the
issue is on its way to being fixed (or not, for some architectures, as you
mention). :-)

/* Steinar */
-- 
Homepage: http://www.sesse.net/

Processed: tagging 783301

[Debian Bug Tracking System]

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

> tags 783301 + pending
Bug #783301 [src:oss4] liboss4-salsa-dev: Overwrites files from 
liboss4-salsa-asound2
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#771341: segfaults in sqlite3_value_type while using from Python

[GCS]

On Mon, Mar 16, 2015 at 3:10 PM, Marc F. Clemente  wrote:
> One is an Intel i7.  Four others are xen virtual machines running on an Intel 
> Xeon.
 On which computers do you get the segfaults? Can you try recent
SQLite3 package uploads, especially 3.9.1?
Do you have a minimal installation maybe where the crash happens?

Laszlo/GCS

Bug#802712: marked as done (Should perroquet be removed?)

[Debian Bug Tracking System]

Your message dated Sat, 24 Oct 2015 17:50:07 +
with message-id 
and subject line Bug#802724: Removed package(s) from unstable
has caused the Debian Bug report #802712,
regarding Should perroquet be removed?
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.)


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

- It's dead upstream (the homepage is domain-squatted)
and it depends on legacy libs scheduled for removal
(gstreamer 0.10)
- The last upload was more than four years ago
- Usage per popcon virtually non-existant

Please address the outstanding bugs or reassign this to
ftp.debian.org for removal.

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Version: 1.1.1-3+rm

Dear submitter,

as the package perroquet has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/802724

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

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#785913: marked as done (perroquet: Please update to GStreamer 1.x)

[Debian Bug Tracking System]

Your message dated Sat, 24 Oct 2015 17:50:07 +
with message-id 
and subject line Bug#802724: Removed package(s) from unstable
has caused the Debian Bug report #785913,
regarding perroquet: Please update to GStreamer 1.x
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.)


-- 
785913: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785913
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: perroquet
Severity: important
User: sl...@debian.org
Usertags: gstreamer0.10-removal

Hi maintainer,

your package perroquet currently still depends on GStreamer 0.10.

GStreamer 0.10 is no longer maintained and supported by the upstream
project since almost 3 years, and contains many known bugs that are
fixed in the new 1.x release series of GStreamer. Next to many bug
fixes, the new release series also contains many other improvements,
new features and a more streamlined API.

For the next Debian release GStreamer 0.10 is planned to be removed,
and if your package is not updated it might not be included in the
release. Please update your package to use the new version as soon as
possible.

If you need any help with porting or have further questions, please
feel free to also contact me privately.

Best regards, Sebastian

PS: See https://bugs.debian.org/785198 and
https://lists.debian.org/debian-devel/2015/05/msg00335.html for some
further discussion.
--- End Message ---
--- Begin Message ---
Version: 1.1.1-3+rm

Dear submitter,

as the package perroquet has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/802724

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

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Processed: tagging 802890

[Debian Bug Tracking System]

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

> tags 802890 + fixed-upstream upstream
Bug #802890 [backintime-qt4] backintime-qt4: can't launch with gksu/gksudo, 
blank grey window appears
Added tag(s) upstream and fixed-upstream.
> severity 802890 important
Bug #802890 [backintime-qt4] backintime-qt4: can't launch with gksu/gksudo, 
blank grey window appears
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#797234: source-highlight, regina-normal and libstdc++6

[Benjamin Burton]

So: it turns out that the regina-normal build failure was not because of the 
libstdc++6 transition, but because source-highlight was built against an old 
version of libboost-regex.  It seems that between August and now, somebody has 
binNMUed source-highlight to use boost 1.58, and as a result the build failure 
for regina-normal has gone away (see the notes for #797292, which I have just 
closed).

That leaves the question: what to do with this bug?  I’m not sure whether 
libsource-highlight4 needs a rebuild with gcc5 - I do see lots of references to 
std::__cxx11::basic_string<…> in the output from “nm -gC”, but someone else 
would be better placed than me to give an opinion on whether this is enough for 
a rebuild.

- Ben.

--

A/Prof Benjamin Burton
Computational Geometry & Topology Group
School of Mathematics and Physics
The University of Queensland, Australia

Bug#787371: wpa: CVE-2015-4143 CVE-2015-4144 CVE-2015-4145 CVE-2015-4146: EAP-pwd missing payload length validation

[Julian Wollrath]

tags 787371 patch

Hi,

I attached a patch to fix these (and more) security issues for jessie.
For unstable I uploaded an updated package to [1], that fixes the
security issues and updates the package to upstream version 2.5.

Since I am no Debian Developer, I will not be able to upload these
updates to the archive.


Cheers,
Julian

[1] http://rbw.goe.net/jw/debiandiff -Nru wpa-2.3/debian/changelog wpa-2.3/debian/changelog
--- wpa-2.3/debian/changelog	2015-04-23 19:33:58.0 +0200
+++ wpa-2.3/debian/changelog	2015-10-24 16:56:08.0 +0200
@@ -1,3 +1,11 @@
+wpa (2.3-1+deb8u2) jessie-security; urgency=high
+
+  * Add fixes for http://w1.fi/security/2015-5/
+  * Add fixes for CVE-2015-4141, CVE-2015-4142, CVE-2015-4143, CVE-2015-4144,
+CVE-2015-4145, CVE-2015-4146 (Closes: #787371).
+
+ -- Julian Wollrath   Sat, 24 Oct 2015 16:27:19 +0200
+
 wpa (2.3-1+deb8u1) jessie-security; urgency=high
 
   * import "P2P: Validate SSID element length before copying it
diff -Nru wpa-2.3/debian/patches/2015-01/0001-P2P-Validate-SSID-element-length-before-copying-it-C.patch wpa-2.3/debian/patches/2015-01/0001-P2P-Validate-SSID-element-length-before-copying-it-C.patch
--- wpa-2.3/debian/patches/2015-01/0001-P2P-Validate-SSID-element-length-before-copying-it-C.patch	1970-01-01 01:00:00.0 +0100
+++ wpa-2.3/debian/patches/2015-01/0001-P2P-Validate-SSID-element-length-before-copying-it-C.patch	2015-10-24 16:24:26.0 +0200
@@ -0,0 +1,37 @@
+From 9ed4eee345f85e3025c33c6e20aa25696e341ccd Mon Sep 17 00:00:00 2001
+From: Jouni Malinen 
+Date: Tue, 7 Apr 2015 11:32:11 +0300
+Subject: [PATCH] P2P: Validate SSID element length before copying it
+ (CVE-2015-1863)
+
+This fixes a possible memcpy overflow for P2P dev->oper_ssid in
+p2p_add_device(). The length provided by the peer device (0..255 bytes)
+was used without proper bounds checking and that could have resulted in
+arbitrary data of up to 223 bytes being written beyond the end of the
+dev->oper_ssid[] array (of which about 150 bytes would be beyond the
+heap allocation) when processing a corrupted management frame for P2P
+peer discovery purposes.
+
+This could result in corrupted state in heap, unexpected program
+behavior due to corrupted P2P peer device information, denial of service
+due to process crash, exposure of memory contents during GO Negotiation,
+and potentially arbitrary code execution.
+
+Thanks to Google security team for reporting this issue and smart
+hardware research group of Alibaba security team for discovering it.
+
+Signed-off-by: Jouni Malinen 
+---
+ src/p2p/p2p.c | 1 +
+ 1 file changed, 1 insertion(+)
+
+--- a/src/p2p/p2p.c
 b/src/p2p/p2p.c
+@@ -736,6 +736,7 @@ int p2p_add_device(struct p2p_data *p2p,
+ 	if (os_memcmp(addr, p2p_dev_addr, ETH_ALEN) != 0)
+ 		os_memcpy(dev->interface_addr, addr, ETH_ALEN);
+ 	if (msg.ssid &&
++	msg.ssid[1] <= sizeof(dev->oper_ssid) &&
+ 	(msg.ssid[1] != P2P_WILDCARD_SSID_LEN ||
+ 	 os_memcmp(msg.ssid + 2, P2P_WILDCARD_SSID, P2P_WILDCARD_SSID_LEN)
+ 	 != 0)) {
diff -Nru wpa-2.3/debian/patches/2015-01/wpa_supplicant-p2p-ssid-overflow.txt wpa-2.3/debian/patches/2015-01/wpa_supplicant-p2p-ssid-overflow.txt
--- wpa-2.3/debian/patches/2015-01/wpa_supplicant-p2p-ssid-overflow.txt	1970-01-01 01:00:00.0 +0100
+++ wpa-2.3/debian/patches/2015-01/wpa_supplicant-p2p-ssid-overflow.txt	2015-10-24 16:24:26.0 +0200
@@ -0,0 +1,68 @@
+wpa_supplicant P2P SSID processing vulnerability
+
+Published: April 22, 2015
+Identifier: CVE-2015-1863
+Latest version available from: http://w1.fi/security/2015-1/
+
+
+Vulnerability
+
+A vulnerability was found in how wpa_supplicant uses SSID information
+parsed from management frames that create or update P2P peer entries
+(e.g., Probe Response frame or number of P2P Public Action frames). SSID
+field has valid length range of 0-32 octets. However, it is transmitted
+in an element that has a 8-bit length field and potential maximum
+payload length of 255 octets. wpa_supplicant was not sufficiently
+verifying the payload length on one of the code paths using the SSID
+received from a peer device.
+
+This can result in copying arbitrary data from an attacker to a fixed
+length buffer of 32 bytes (i.e., a possible overflow of up to 223
+bytes). The SSID buffer is within struct p2p_device that is allocated
+from heap. The overflow can override couple of variables in the struct,
+including a pointer that gets freed. In addition about 150 bytes (the
+exact length depending on architecture) can be written beyond the end of
+the heap allocation.
+
+This could result in corrupted state in heap, unexpected program
+behavior due to corrupted P2P peer device information, denial of service
+due to wpa_supplicant process crash, exposure of memory contents during
+GO Negotiation, and potentially arbitrary code execution.
+
+Vulnerable versions/configurations
+
+wpa_supplicant v1.0-v2.4 

Processed: Re: Processed: Re: Bug#802880 closed by Gianfranco Costamagna <costamagnagianfra...@yahoo.it> (qtcreator: not really a bug)

[Debian Bug Tracking System]

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

> fixed 802880 qtcreator/3.5.0+dfsg-2+b1
Bug #802880 {Done: Gianfranco Costamagna } 
[src:qtcreator] package is uninstallable due to Qt 5.5 transition
The source qtcreator and version 3.5.0+dfsg-2+b1 do not appear to match any 
binary packages
Marked as fixed in versions qtcreator/3.5.0+dfsg-2+b1.
> thanks
Stopping processing here.

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

Bug#802890: backintime-qt4: can't launch with gksu/gksudo, blank grey window appears

[Lev Livnev]

Package: backintime-qt4
Version: 1.1.6-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Trying to start the QT interface for backintime-qt4 using:

$ gksu backintime-qt4

results in a blank grey window appearing, along with the output:

Back In Time
Version: 1.1.6

Back In Time comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; type `backintime-qt4 --license' for details.

X Error: BadAccess (attempt to access private resource denied) 10
  Extension:130 (MIT-SHM)
  Minor opcode: 1 (X_ShmAttach)
  Resource id:  0x18b
X Error: BadShmSeg (invalid shared segment parameter) 128
  Extension:130 (MIT-SHM)
  Minor opcode: 5 (X_ShmCreatePixmap)
  Resource id:  0xf4
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x3800013
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x3800013
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x3800013
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x3800013
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x3800013
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x3800013

(using gksudo leads to the same behaviour but without the above Error messages
in the output.) This appears to be a common problem for some qt4 programs, and
is fixed by running instead:

$ gksu QT_X11_NO_MITSHM=1 backintime-qt4

in which case the program runs as normal. This problem has only recently
started to affect my system, no idea why. Googling QT_X11_NO_MITSHM=1 shows
that this affects a lot of QT apps that need gksu/gksudo.



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

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

Versions of packages backintime-qt4 depends on:
ii  backintime-common 1.1.6-1
ii  libnotify-bin 0.7.6-2
ii  policykit-1   0.105-12
ii  python3-dbus.mainloop.qt  4.11.4+dfsg-1+b2
ii  python3-pyqt4 4.11.4+dfsg-1+b2
pn  python3:any   
ii  x11-utils 7.7+3

Versions of packages backintime-qt4 recommends:
ii  python3-secretstorage  2.1.2-3

Versions of packages backintime-qt4 suggests:
pn  meld | kompare  

-- no debconf information

Bug#802858: activemq: FTBFS: Missing: jakarta-regexp:jakarta-regexp:jar:debian

[Hans Joachim Desserud]

I haven't tested this, but I notice that Ubuntu has a patch for this
package which adds libregexp-java as a build dependency in order to
fix a FTBFS issue. Hm... might be worth checking out :)

For details, see
http://patches.ubuntu.com/a/activemq/activemq_5.6.0+dfsg1-4+deb8u1ubuntu1.patch


--
mvh / best regards
Hans Joachim Desserud
http://desserud.org

Bug#802890: backintime-qt4: can't launch with gksu/gksudo, blank grey window appears

[Germar Reitze]

This is fixed upstream in 1.1.8

Please use 'pkexec backintime-qt4' instead of 'gksu'


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

Bug#802890: backintime-qt4: can't launch with gksu/gksudo, blank grey window appears

[Germar Reitze]

It's a duplicate of https://bugs.launchpad.net/backintime/+bug/1493020


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

Bug#802890: backintime-qt4: can't launch with gksu/gksudo, blank grey window appears

[Germar Reitze]

tags 802890 + fixed-upstream upstream
severity 802890 important
thanks


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

Bug#802871: zeal: FTBFS: error: variable 'QDataStream out' has initializer but incomplete type

[ChangZhuo Chen]

Control: block -1 802382

On Sat, Oct 24, 2015 at 01:32:41PM +0100, Chris West (Faux) wrote:
> Source: zeal
> Version: 1:0.1.1-2
> Severity: serious
> Justification: fails to build from source
> Tags: sid 
> 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:
> 
> main.cpp: In function ‘int main(int, char**)’:
> main.cpp:193:29: error: variable ‘QDataStream out’ has initializer but 
> incomplete type
>  QDataStream out(socket.data());
>  ^
> Makefile:737: recipe for target '../.obj/main.o' failed
> make[2]: *** [../.obj/main.o] Error 1
> make[2]: Leaving directory '/zeal-0.1.1/src'
> Makefile:42: recipe for target 'sub-src-make_first-ordered' failed
> make[1]: *** [sub-src-make_first-ordered] Error 2

It is possible due to qtbase-opensource-src transition in #802382. I
will check it once the transition is over.

> 
> Full build log:
> https://reproducible.debian.net/rb-pkg/unstable/amd64/zeal.html
> 
> -- System Information:
> Debian Release: stretch/sid
> APT prefers unstable
> APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)

-- 
ChangZhuo Chen (陳昌倬) 
Debian Developer
Key fingerprint = EC9F 905D 866D BE46 A896  C827 BE0C 9242 03F4 552D


signature.asc
Description: PGP signature

Processed: I have the same problem

[Debian Bug Tracking System]

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

> severity 802886 grave
Bug #802886 [vlc] vlc: QT Interface wont full screen or renders only a small 
portion of the video
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#802880: package is uninstallable due to Qt 5.5 transition

[Steinar H. Gunderson]

Source: qtcreator
Version: 3.5.0+dfsg-2
Severity: serious

Hi,

I can't install qtcreator anymore, since unstable is now on Qt 5.5:

  klump:~> sudo LANG=C apt-get install qtcreator 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  
  The following packages have unmet dependencies:
   qtcreator : Depends: qtbase-abi-5-4-2
   Depends: qtdeclarative-abi-5-4-1
   Recommends: qtdeclarative5-dev-tools
   Recommends: qttools5-dev-tools but it is not going to be 
installed
  E: Unable to correct problems, you have held broken packages.

I assume this needs a newer version from upstream.

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

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

Bug#802760: marked as pending

[Daniele Tricoli]

tag 802760 pending
thanks

Hello,

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


http://git.debian.org/?p=python-modules/packages/requests.git;a=commitdiff;h=ccc91dc

---
commit ccc91dc291710d32703aa554a4a23409b358e66d
Author: Daniele Tricoli 
Date:   Fri Oct 23 12:26:29 2015 +0200

Uploading requests 2.8.1 will close #802760

diff --git a/debian/changelog b/debian/changelog
index e912f06..6a4b1ec 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,10 +1,10 @@
 requests (2.8.1-1) UNRELEASED; urgency=medium
 
-  * New upstream release.
+  * New upstream release. (Closes: #802760)
   * debian/patches/05_upstream_devendorize.patch
 - Remove because included since version 2.8.0.
 
- -- Daniele Tricoli   Wed, 14 Oct 2015 18:54:29 +0200
+ -- Daniele Tricoli   Fri, 23 Oct 2015 12:26:12 +0200
 
 requests (2.7.0-3) unstable; urgency=medium
 

Processed: Bug#802760 marked as pending

[Debian Bug Tracking System]

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

> tag 802760 pending
Bug #802760 [python-requests] python-requests 2.7.0 incompatible with urllib3 
1.12
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#802706: slepc: FTBFS: Unable to link with PETSc

[Drew Parsons]

On Fri, 23 Oct 2015 10:21:35 +0800 Drew Parsons 
wrote:
> This one's a mystery ... "works for me"  
> i.e. my upload was built successfully with sbuild.
> 

We diagnosed the problem on irc (i.e. why it was "working for me"): the
default sbuild configuration uses the default apt configuration, which
installs Recommends.  The buildds have installation of Recommends
deactivated.

So I can reproduce the build error after reconfiguring my sbuild chroot
(configure apt as per https://wiki.debian.org/BuilddSetup#debian.org_Bu
ildd_setup)

The fix, as you said, is to add the -dev Depends to the petsc dev
packages.

The reason this is needed is that petsc handles these libraries as
external libraries and lists them as required in
/lib/pkgconfig/PETSc.pc and petsc>/lib/petsc/conf/petscvariables

Drew

Processed: severity of 797037 is important

[Debian Bug Tracking System]

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

> severity 797037 important
Bug #797037 [src:shogun] shogun: FTBFS on mipsen
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#789914: marked as done (apache2: fails to install: ERROR: Module mpm_event is enabled - cannot proceed due to conflicts. It needs to be disabled first!)

[Debian Bug Tracking System]

Your message dated Sat, 24 Oct 2015 21:35:02 +
with message-id 
and subject line Bug#789914: fixed in apache2 2.4.17-1
has caused the Debian Bug report #789914,
regarding apache2: fails to install: ERROR: Module mpm_event is enabled - 
cannot proceed due to conflicts. It needs to be disabled first!
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.)


-- 
789914: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789914
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apache2.2-common
Version: 2.4.12-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

This bug was triggered when installing (the dependencies of)
fusionforge-web 6.0.1-1 in a minimal piuparts chroot.

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

[...]
  Setting up apache2-bin (2.4.12-2) ...
  Setting up libapache2-mpm-itk (2.4.7-02-1.1) ...
  Package apache2 is not configured yet. Will defer actions by package 
libapache2-mpm-itk.
  Setting up apache2-utils (2.4.12-2) ...
  Setting up apache2-data (2.4.12-2) ...
  Setting up apache2 (2.4.12-2) ...
  Enabling module mpm_event.
  Enabling module authz_core.
  Enabling module authz_host.
  Enabling module authn_core.
  Enabling module auth_basic.
  Enabling module access_compat.
  Enabling module authn_file.
  Enabling module authz_user.
  Enabling module alias.
  Enabling module dir.
  Enabling module autoindex.
  Enabling module env.
  Enabling module mime.
  Enabling module negotiation.
  Enabling module setenvif.
  Enabling module filter.
  Enabling module deflate.
  Enabling module status.
  Enabling conf charset.
  Enabling conf localized-error-pages.
  Enabling conf other-vhosts-access-log.
  Enabling conf security.
  Enabling conf serve-cgi-bin.
  Enabling site 000-default.
  info: mpm_prefork: No action required
  info: Executing deferred 'a2enmod mpm_itk' for package libapache2-mpm-itk
  ERROR: Module mpm_event is enabled - cannot proceed due to conflicts. It 
needs to be disabled first!
  ERROR: Could not enable dependency mpm_prefork for mpm_itk, aborting
  dpkg: error processing package apache2 (--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of libapache2-mod-php5:
   libapache2-mod-php5 depends on apache2 (>= 2.4); however:
Package apache2 is not configured yet.
  
  dpkg: error processing package libapache2-mod-php5 (--configure):
   dependency problems - leaving unconfigured
[...]


cheers,

Andreas


fusionforge-web_6.0.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: apache2
Source-Version: 2.4.17-1

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

Debian distribution maintenance software
pp.
Stefan Fritsch  (supplier of updated apache2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 24 Oct 2015 22:14:32 +0200
Source: apache2
Binary: apache2 apache2-data apache2-bin apache2-utils apache2-suexec-pristine 
apache2-suexec-custom apache2-doc apache2-dev apache2-dbg
Architecture: source amd64 all
Version: 2.4.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Apache Maintainers 
Changed-By: Stefan Fritsch 
Description:
 apache2- Apache HTTP Server
 apache2-bin - Apache HTTP Server (modules and other binary files)
 apache2-data - Apache HTTP Server (common files)
 apache2-dbg - Apache debugging symbols
 apache2-dev - Apache HTTP Server (development headers)
 apache2-doc - Apache HTTP Server (on-site documentation)
 apache2-suexec-custom - Apache HTTP Server configurable suexec program for 
mod_suexec
 apache2-suexec-pristine - Apache HTTP Server standard suexec program for 
mod_suexec
 apache2-utils - Apache HTTP 

Bug#802886: vlc: QT Interface wont full screen or renders only a small portion of the video

[Modestas Vainius]

Control: tags -1 upstream

Hello,

Šeštadienis 24 Spalis 2015 11:34:11 rašė:
> When using the QT interface in VLC, I can no longer doubleclick a video and
> full screen it. When playing a video parts of it are masked off/cropped . 
> So only a small area approximatly 530x290 is visable. I've disabled overlay
> with no effect.  Resizing the video into the small visable area is the only
> way to see the entire video uncropped.
> 
> If I however run the command cvlc  the video the full size and
> have no issue fullscreening the video. It seems that the issue might be
> with QT, but I am unsure how to figure out what the offending package
> maybe.

This was caused by upgrade from Qt 5.4 to 5.5. It is either vlc [1] or Qt 5.5 
[2] issue (latter being more likely). I leave it up to maintainer to decide 
whether to reassign.

However, from a user POV, vlc is basically unusable for video with this bug in 
place.

There are two bugs here though:

1) double-click not working for full-screening. Can be worked around by 
setting QT_XCB_NO_XI2_MOUSE=1 when starting vlc [3]:

$ QT_XCB_NO_XI2_MOUSE=1 vlc

2) video is only partially visible. Not aware of any workarounds yet.

[1] https://trac.videolan.org/vlc/ticket/15663
[2] https://bugreports.qt.io/browse/QTBUG-48321
[3] https://trac.videolan.org/vlc/ticket/15663#comment:3

-- 
Modestas Vainius 

Processed: Re: vlc: QT Interface wont full screen or renders only a small portion of the video

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream
Bug #802886 [vlc] vlc: QT Interface wont full screen or renders only a small 
portion of the video
Added tag(s) upstream.

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

Processed: notfixed 789914 in 2.4.16-1, tagging 789914, tagging 791902, found 740162 in 2.2.22-13

[Debian Bug Tracking System]

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

> notfixed 789914 2.4.16-1
Bug #789914 {Done: Stefan Fritsch } [apache2] apache2: fails 
to install: ERROR: Module mpm_event is enabled - cannot proceed due to 
conflicts. It needs to be disabled first!
No longer marked as fixed in versions apache2/2.4.16-1.
> tags 789914 + pending
Bug #789914 {Done: Stefan Fritsch } [apache2] apache2: fails 
to install: ERROR: Module mpm_event is enabled - cannot proceed due to 
conflicts. It needs to be disabled first!
Added tag(s) pending.
> tags 791902 + pending
Bug #791902 [apache2] libapache2-mod-php5.postinst: 291: [: !=: unexpected 
operator
Added tag(s) pending.
> found 740162 2.2.22-13
Bug #740162 [apache2-bin] mod_authnz_ldap: no error.log feedback about LDAP TLS 
issues such as cert expiry, cipher mismatch, etc
There is no source info for the package 'apache2-bin' at version '2.2.22-13' 
with architecture ''
Unable to make a source version for version '2.2.22-13'
Marked as found in versions 2.2.22-13.
> thanks
Stopping processing here.

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

Processed: license-reconcile

[Debian Bug Tracking System]

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

> owner 801609 nicho...@periapt.co.uk
Bug #801609 [license-reconcile] license-reconcile: FTBFS: cannot parse file 
't/data/example/sample.png'
Owner recorded as nicho...@periapt.co.uk.
>
End of message, stopping processing here.

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

Bug#802906: fix build failures with python 3.5

[Matthias Klose]

Package: src:swig
Version: 3.0.2-1
Severity: serious
Tags: sid stretch patch

this is upstream issue #539, causing build failures when wrapping code for the 
PyHeapTypeObject in Python 3.5.


Not yet fixed in 3.0.7-0.

Patch at
http://launchpadlibrarian.net/222739670/swig_3.0.7-0ubuntu1_3.0.7-0ubuntu2.diff.gz

Bug#802365: marked as done (sooperlooper: FTBFS: sigc++-2.0 requires -std=c++11)

[Debian Bug Tracking System]

Your message dated Sat, 24 Oct 2015 21:40:35 +
with message-id 
and subject line Bug#802365: fixed in sooperlooper 1.7.3~dfsg0-2
has caused the Debian Bug report #802365,
regarding sooperlooper: FTBFS: sigc++-2.0 requires -std=c++11
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.)


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

Dear Maintainer,

The package fails to build:

g++ -DHAVE_CONFIG_H -I.   -D_FORTIFY_SOURCE=2  -D_REENTRANT -Os 
-fomit-frame-pointer -mmmx -msse -mfpmath=sse -pipe -Wall -D_LARGEFILE_SOURCE 
-D_LARGEFILE64_SOURCE -I/sooperlooper-1.7.3~dfsg0/libs/pbd 
-I/sooperlooper-1.7.3~dfsg0/libs/midi++ -I/usr/include/libxml2  
-I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include  -c -o 
pathscanner.o pathscanner.cc
In file included from /usr/include/sigc++-2.0/sigc++/signal_base.h:26:0,
 from /usr/include/sigc++-2.0/sigc++/signal.h:8,
 from /usr/include/sigc++-2.0/sigc++/sigc++.h:86,
 from ./pbd/transmitter.h:27,
 from ./pbd/error.h:23,
 from pathscanner.cc:27:
/usr/include/sigc++-2.0/sigc++/trackable.h:115:3: warning: identifier 
‘noexcept’ is a keyword in C++11 [-Wc++0x-compat]
   trackable(trackable&& src) noexcept;
   ^
In file included from /usr/include/c++/5/type_traits:35:0,
 from /usr/include/sigc++-2.0/sigc++/visit_each.h:22,
 from /usr/include/sigc++-2.0/sigc++/functors/slot.h:6,
 from /usr/include/sigc++-2.0/sigc++/signal_base.h:27,
 from /usr/include/sigc++-2.0/sigc++/signal.h:8,
 from /usr/include/sigc++-2.0/sigc++/sigc++.h:86,
 from ./pbd/transmitter.h:27,
 from ./pbd/error.h:23,
 from pathscanner.cc:27:
/usr/include/c++/5/bits/c++0x_warning.h:32:2: error: #error This file requires 
compiler and library support for the ISO C++ 2011 standard. This support is 
currently experimental, and must be enabled with the -std=c++11 or -std=gnu++11 
compiler options.
 #error This file requires compiler and library support for the \
  ^
In file included from 
/usr/include/sigc++-2.0/sigc++/adaptors/adaptor_trait.h:7:0,
 from /usr/include/sigc++-2.0/sigc++/functors/slot.h:7,
 from /usr/include/sigc++-2.0/sigc++/signal_base.h:27,
 from /usr/include/sigc++-2.0/sigc++/signal.h:8,
 from /usr/include/sigc++-2.0/sigc++/sigc++.h:86,
 from ./pbd/transmitter.h:27,
 from ./pbd/error.h:23,
 from pathscanner.cc:27:
/usr/include/sigc++-2.0/sigc++/functors/functor_trait.h:92:3: warning: 
identifier ‘decltype’ is a keyword in C++11 [-Wc++0x-compat]
   static int check(X_functor* obj, decltype(_functor::operator()) p = 
nullptr);
   ^

See http://bugs.debian.org/802352 for a similar bug.

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

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: sooperlooper
Source-Version: 1.7.3~dfsg0-2

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

Debian distribution maintenance software
pp.
Jaromír Mikeš  (supplier of updated sooperlooper package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Sat, 24 Oct 2015 21:28:22 +0200
Source: sooperlooper
Binary: sooperlooper
Architecture: source amd64
Version: 1.7.3~dfsg0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Bug#802886:

[Andoru Ekkusu]

> except that in my case I see only about 20x200 pixels, i.e. almost not at
all.

I think the size of the video that's shown is random each time you play
something or resize the window. I tried for example to go from windowed to
fullscreen (by manually clicking the menu option under "Video"), it
suddenly displayed more of the video. I also noticed that when opening
different videos, or even the same video, the size of the video shown
varies.

> I played with output in video section without success.

I forgot to mention earlier that as a temporary fix, you can untick the
"Integrate video in interface" option under "Interface" in VLC's preference
(simple view), that should enable you to see the videos and switch to
fullscreen by double-clicking.

Processed: Remove swig 2.0 for Strech (python 3.5, octave 4.0 unsupported)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #786517 [swig2.0] Remove swig 2.0 for Strech (python 3.5, octave 4.0 
unsupported)
Ignoring request to change severity of Bug 786517 to the same value.
> retitle -1 Remove swig 2.0 for Strech (python 3.5, octave 4.0 unsupported)
Bug #786517 [swig2.0] Remove swig 2.0 for Strech (python 3.5, octave 4.0 
unsupported)
Ignoring request to change the title of bug#786517 to the same title

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

Bug#786517: Remove swig 2.0 for Strech (python 3.5, octave 4.0 unsupported)

[Matthias Klose]

Control: severity -1 serious
Control: retitle -1 Remove swig 2.0 for Strech (python 3.5, octave 4.0 
unsupported)

As seen in #802906, this now becomes an RC issue, as Python 3.5 is a supported 
Python version, and is not anymore supported by swig 2.0.


Same for octave 4.0, and maybe other languages.

Processed: Remove swig 2.0 for Strech (python 3.5, octave 4.0 unsupported)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #786517 [swig2.0] Remove swig 2.0 for Strech
Severity set to 'serious' from 'important'
> retitle -1 Remove swig 2.0 for Strech (python 3.5, octave 4.0 unsupported)
Bug #786517 [swig2.0] Remove swig 2.0 for Strech
Changed Bug title to 'Remove swig 2.0 for Strech (python 3.5, octave 4.0 
unsupported)' from 'Remove swig 2.0 for Strech'

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

Bug#802908: requires python3-gi to run

[Modestas Vainius]

Package: caffeine
Version: 2.8.3-1
Severity: serious

Hello,

caffeine uses modules from python3-gi and needs them to run (see below):

Traceback (most recent call last):
  File "/usr/bin/caffeine", line 25, in 
from gi.repository import GObject, Gtk, GLib

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

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

Versions of packages caffeine depends on:
ii  gir1.2-appindicator3-0.1  0.4.92-3.1
ii  gir1.2-gtk-3.03.18.2-1
ii  libnet-dbus-perl  1.1.0-3
ii  perl  5.20.2-6
ii  python3   3.4.3-7
ii  python3-pkg-resources 18.4-1
ii  python3-xlib  0.14+20091101-5
pn  python3:any   

caffeine recommends no packages.

caffeine suggests no packages.

-- no debconf information

Bug#802910: mupen64plus-qt/arm64 unsatisfiable Depends: mupen64plus-ui-console

[Matthias Klose]

Package: src:mupen64plus-qt
Version: 1.8-1
Severity: serious
Tags: sid stretch

mupen64plus-qt/arm64 unsatisfiable Depends: mupen64plus-ui-console
mupen64plus-qt/armel unsatisfiable Depends: mupen64plus-ui-console
mupen64plus-qt/armhf unsatisfiable Depends: mupen64plus-ui-console
mupen64plus-qt/mips unsatisfiable Depends: mupen64plus-ui-console
mupen64plus-qt/mipsel unsatisfiable Depends: mupen64plus-ui-console
mupen64plus-qt/powerpc unsatisfiable Depends: mupen64plus-ui-console
mupen64plus-qt/ppc64el unsatisfiable Depends: mupen64plus-ui-console
mupen64plus-qt/s390x unsatisfiable Depends: mupen64plus-ui-console

However, the architecture for mupen64plus-ui-console is set to amd64 i386 only. 
So just set it to any, and let it build on these architectures as well, or relax 
the dependency to a suggests.

Bug#802910: mupen64plus-qt/arm64 unsatisfiable Depends: mupen64plus-ui-console

[Sérgio Benjamim]

Eh, there's no Mupen packages for ARMhf? Last time I tested it was 
working very well (I had published some ARMhf packages in this PPA [1], 
tested on odroid U3, ubuntu 14.04).


[1] https://launchpad.net/~random-stuff/+archive/ubuntu/stable

Sergio Benjamim




On 24/10/2015 22:10, Matthias Klose wrote:

Package: src:mupen64plus-qt
Version: 1.8-1
Severity: serious
Tags: sid stretch

mupen64plus-qt/arm64 unsatisfiable Depends: mupen64plus-ui-console
mupen64plus-qt/armel unsatisfiable Depends: mupen64plus-ui-console
mupen64plus-qt/armhf unsatisfiable Depends: mupen64plus-ui-console
mupen64plus-qt/mips unsatisfiable Depends: mupen64plus-ui-console
mupen64plus-qt/mipsel unsatisfiable Depends: mupen64plus-ui-console
mupen64plus-qt/powerpc unsatisfiable Depends: mupen64plus-ui-console
mupen64plus-qt/ppc64el unsatisfiable Depends: mupen64plus-ui-console
mupen64plus-qt/s390x unsatisfiable Depends: mupen64plus-ui-console

However, the architecture for mupen64plus-ui-console is set to amd64 
i386 only. So just set it to any, and let it build on these 
architectures as well, or relax the dependency to a suggests.

Processed: Re: Bug#802801: python-coverage: FTBFS: calling function returned 100.0, not a test

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + unreproducible moreinfo
Bug #802801 [src:python-coverage] python-coverage: FTBFS: calling function 
returned 100.0, not a test
Added tag(s) unreproducible and moreinfo.

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

Bug#802801: python-coverage: FTBFS: calling function returned 100.0, not a test

[Ben Finney]

Control: tags -1 + unreproducible moreinfo

On 23-Oct-2015, Dmitry Shachnev wrote:

> python-coverage FTBFS in a fresh sid chroot:

Thank you for reporting this.

>   building 'coverage.tracer' extension
>   x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
> -Wstrict-prototypes -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.5m 
> -c coverage/tracer.c -o build/temp.linux-x86_64-3.5/coverage/tracer.o
>   x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions 
> -Wl,-z,relro -Wl,-z,relro -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -D_FORTIFY_SOURCE=2 
> build/temp.linux-x86_64-3.5/coverage/tracer.o -o 
> /tmp/buildd/python-coverage-3.7.1+dfsg.1/coverage/tracer.cpython-35m-x86_64-linux-gnu.so
>   NameStmts   Miss  Cover   Missing
>   -
>   Traceback (most recent call last):
> […]
> File "/usr/lib/python3.5/unittest/loader.py", line 211, in 
> loadTestsFromName
>   (obj, test))
>   TypeError: calling .wrapper at 
> 0x7f1fac233488> returned 100.0, not a test
>   debian/rules:87: recipe for target 'test-python3.5' failed
>   make[1]: *** [test-python3.5] Error 1

I don't get that failure at all. We are both using Debian Sid chroot,
on “amd64” architecture. I updated the build chroot less than an hour
ago; perhaps something has changed between your attempt and mine?

(I can't figure out why the function would return “100.0” instead of a
test case in *any* circumstance.)

> You can find the full build log at:
> http://mitya57.me/builds/python-coverage_3.7.1+dfsg.1-1_amd64.build

Looking through that build log, I don't see what would be different to
cause yours to fail with that error but not mine.

-- 
 \ “I think there is a world market for maybe five computers.” |
  `\ —Thomas Watson, chairman of IBM, 1943 |
_o__)  |
Ben Finney 


signature.asc
Description: PGP signature

Bug#802917: do not migrate denyhosts to testing: who will do security support?

[Helmut Grohne]

Package: denyhosts
Version: 2.10-2
Severity: serious
Tags: security

Hi Jan-Pascal,

thank you for your interest in reviving denyhosts. Unfortunately, there
are still unresolved issues with denyhosts that make it unfit for
release. This bug is meant as a tracker bug and to prevent testing
migration until all sub issues are properly tracked.

 * The denyhosts package is very similar to fail2ban. In particular,
   both contain a set of regular expressions for matching log files from
   daemons. These regular expressions are hard to get right. Thus the
   Debian security team wants to avoid supporting both tools. This
   argument is similar to how ffmpeg was blocked from jessie, because it
   was too similar to libav and had a difficult security profile. So
   until it is clear who will do the security support for denyhosts,
   denyhosts should stay out of testing.

 * Your upload reintroduces security bug #692229.

 * Due to the removal of denyhosts from Debian, the following bugs were
   closed by the ftp masters:

   #395565 #436417 #497485 #514024 #529089 #546772 #597956 #567209 #611756
   #622697 #643031 #720130 #729322 #731963

   Please evaluate which of them need to be reopened or failing that
   reopen all of them.

Sorry for the bad news, but I believe that reincluding the current
denyhosts package is a disservice to our users.

Helmut

Bug#802880: (qtcreator: not really a bug)

[Adam Majer]

On Sat, Oct 24, 2015 at 04:40:18PM +0200, Steinar H. Gunderson wrote:
> On Sat, Oct 24, 2015 at 02:33:04PM +, Debian Bug Tracking System wrote:
> > Hi, this bug is invalid.
> 
> Uhm, no?

Actually, yes. Uninstallable packages can exist in unstable until they
are either fixed or removed. It's not really necessary to file these
bugs since these are already part of known transitions.

  https://packages.qa.debian.org/q/qtcreator.html
  https://release.debian.org/transitions/html/qtbase-abi-5-5-1.html


> > 3.5.0+dfsg-2+b1
> > Rebuild against qtbase-abi-5-5-1.
> 
> If so, the binNMU fixes this bug (and should nominally have a Closes: line
> with the bug number, except the bug was probably filed after the binNMU was
> scheduled). Thank you for taking care of that.

No, binNMUs do not change the package source. There is no changelog entry.


> In particular, having a bug in the BTS will enable users to see that the
> issue is on its way to being fixed (or not, for some architectures, as you
> mention). :-)

This is of no use to anyone. As I wrote above, these things are
already tracked outside BTS. Sid can have uninstallable packages -
that is normal. If you prefer to have more consistent set of packages,
please use testing distribution instead.

Few weeks ago there was a quite large stdlibc++ transition affecting
hundreds of packages. No bugs were filed because of missing g++ 5
symbols (unless packages needed manual modification to complete
transition, and these were filed months in advance).

Cheers,
- Adam


-- 
Adam Majer
ad...@zombino.com

Bug#802916: python-coverage: post-build tests fail: “coverage.misc.CoverageException: No data to report.”

[Ben Finney]

Package: python-coverage
Version: 3.7.1+dfsg.1-1+b2
Severity: serious
Justification: fails to build from source

In an up-to-date Debian “sid” chroot, ‘python-coverage’ fails to build
from source. The test run fails on Python 3.5:

=
python3.5 setup.py test -vv
running test
running egg_info
writing top-level names to coverage.egg-info/top_level.txt
writing coverage.egg-info/PKG-INFO
writing dependency_links to coverage.egg-info/dependency_links.txt
writing entry points to coverage.egg-info/entry_points.txt
reading manifest file 'coverage.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no previously-included files matching '*.pyc' found anywhere in 
distribution
writing manifest file 'coverage.egg-info/SOURCES.txt'
running build_ext
building 'coverage.tracer' extension
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.5m -c coverage/tracer.c -o 
build/temp.linux-x86_64-3.5/coverage/tracer.o
x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions 
-Wl,-z,relro -Wl,-z,relro -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -D_FORTIFY_SOURCE=2 
build/temp.linux-x86_64-3.5/coverage/tracer.o -o 
/build/python-coverage-3.7.1+dfsg.1/coverage/tracer.cpython-35m-x86_64-linux-gnu.so
Traceback (most recent call last):
  File "setup.py", line 199, in 
main()
  File "setup.py", line 188, in main
setup(**setup_args)
  File "/usr/lib/python3.5/distutils/core.py", line 148, in setup
dist.run_commands()
  File "/usr/lib/python3.5/distutils/dist.py", line 955, in run_commands
self.run_command(cmd)
  File "/usr/lib/python3.5/distutils/dist.py", line 974, in run_command
cmd_obj.run()
  File "/usr/lib/python3/dist-packages/setuptools/command/test.py", line 146, 
in run
self.with_project_on_sys_path(self.run_tests)
  File "/usr/lib/python3/dist-packages/setuptools/command/test.py", line 127, 
in with_project_on_sys_path
func()
  File "/usr/lib/python3/dist-packages/setuptools/command/test.py", line 167, 
in run_tests
testRunner=self._resolve_as_ep(self.test_runner),
  File "/usr/lib/python3.5/unittest/main.py", line 93, in __init__
self.parseArgs(argv)
  File "/usr/lib/python3.5/unittest/main.py", line 123, in parseArgs
self._do_discovery([])
  File "/usr/lib/python3.5/unittest/main.py", line 228, in _do_discovery
self.test = loader.discover(self.start, self.pattern, self.top)
  File "/usr/lib/python3.5/unittest/loader.py", line 341, in discover
tests = list(self._find_tests(start_dir, pattern))
  File "/usr/lib/python3.5/unittest/loader.py", line 398, in _find_tests
full_path, pattern, namespace)
  File "/usr/lib/python3.5/unittest/loader.py", line 475, in _find_test_path
tests = self.loadTestsFromModule(package, pattern=pattern)
  File "/usr/lib/python3/dist-packages/setuptools/command/test.py", line 36, in 
loadTestsFromModule
tests.append(self.loadTestsFromName(submodule))
  File "/usr/lib/python3.5/unittest/loader.py", line 204, in loadTestsFromName
test = obj()
  File "/build/python-coverage-3.7.1+dfsg.1/coverage/__init__.py", line 42, in 
wrapper
return getattr(_the_coverage, name)(*args, **kwargs)
  File "/build/python-coverage-3.7.1+dfsg.1/coverage/control.py", line 635, in 
annotate
reporter.report(morfs, directory=directory)
  File "/build/python-coverage-3.7.1+dfsg.1/coverage/annotate.py", line 43, in 
report
self.report_files(self.annotate_file, morfs, directory)
  File "/build/python-coverage-3.7.1+dfsg.1/coverage/report.py", line 76, in 
report_files
raise CoverageException("No data to report.")
coverage.misc.CoverageException: No data to report.
debian/rules:87: recipe for target 'test-python3.5' failed
=

The complete build log (from ‘pbuilder’ is attached.

-- 
 \   “Self-respect: The secure feeling that no one, as yet, is |
  `\suspicious.” —Henry L. Mencken |
_o__)  |
Ben Finney 
W: /root/.pbuilderrc does not exist
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Sun Oct 25 15:28:46 AEDT 2015
I: pbuilder-time-stamp: 1445747326
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/sid-amd64-base.tar.gz]
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: policy-rc.d already exists
W: Could not create compatibility symlink because /tmp/buildd exists and it is 
not a directory
I: Obtaining the cached apt archive contents
I: Installing the build-deps
I: user script /var/cache/pbuilder/build//23297/tmp/hooks/D80_no-man-db-rebuild 
starting
I: preseed man-db/auto-update to false
I: user script 

Bug#802858: activemq: FTBFS: Missing: jakarta-regexp:jakarta-regexp:jar:debian

[Chris West (Faux)]

Source: activemq
Version: 5.6.0+dfsg1-4+deb8u1
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:

[INFO] Building ActiveMQ :: Core
[INFO]task-segment: [install]
[INFO] 
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Failed to resolve artifact.

Missing:
--
1) jakarta-regexp:jakarta-regexp:jar:debian

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=jakarta-regexp 
-DartifactId=jakarta-regexp -Dversion=debian -Dpackaging=jar 
-Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
  mvn deploy:deploy-file -DgroupId=jakarta-regexp 
-DartifactId=jakarta-regexp -Dversion=debian -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.activemq:activemq-core:bundle:5.6.0
2) jakarta-regexp:jakarta-regexp:jar:debian

--
1 required artifact is missing.

for artifact: 
  org.apache.activemq:activemq-core:bundle:5.6.0

from the specified remote repositories:
  com.springsource.repository.bundles.external 
(http://repository.springsource.com/maven/bundles/external),
  apache.snapshots 
(https://repository.apache.org/content/repositories/snapshots/),
  central (https://repo1.maven.org/maven2),
  fusesource-snapshots 
(http://repo.fusesource.com/nexus/content/groups/public-snapshots)



NOTE: Maven is executing in offline mode. Any artifacts not already in your 
local
repository will be inaccessible.


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

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

Bug#802867: python-biom-format: FTBFS: _filter.pyx: Incompatible types in conditional expression ((Py_ssize_t, Py_ssize_t); (long, long))

[Chris West (Faux)]

Source: python-biom-format
Version: 2.1+dfsg-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

running config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/python-biom-format-2.1+dfsg'
USE_CYTHON=true dh_auto_build
I: pybuild base:170: /usr/bin/python setup.py build 

Error compiling Cython file:

...
offset += end - start
offset_rows += 1
arr.data = data[:nnz]
arr.indices = indices[:nnz]
arr.indptr = indptr[:m-offset_rows+1]
arr._shape = (m - offset_rows, n) if m-offset_rows else (0, 0)
^


biom/_filter.pyx:87:17: Incompatible types in conditional expression 
((Py_ssize_t, Py_ssize_t); (long, long))
Compiling biom/_filter.pyx because it changed.
Compiling biom/_transform.pyx because it changed.
Compiling biom/_subsample.pyx because it changed.
[1/3] Cythonizing biom/_filter.pyx
Traceback (most recent call last):
  File "setup.py", line 80, in 
extensions = cythonize(extensions)
  File "/usr/lib/python2.7/dist-packages/Cython/Build/Dependencies.py", line 
877, in cythonize
cythonize_one(*args)
  File "/usr/lib/python2.7/dist-packages/Cython/Build/Dependencies.py", line 
997, in cythonize_one
raise CompileError(None, pyx_file)
Cython.Compiler.Errors.CompileError: biom/_filter.pyx
E: pybuild pybuild:262: build: plugin distutils failed with: exit code=1: 
/usr/bin/python setup.py build 
dh_auto_build: pybuild --build -i python{version} -p 2.7 --dir . returned exit 
code 13
debian/rules:23: recipe for target 'override_dh_auto_build' failed

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

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

Bug#802873: libopenraw1v5: FTBFS kfreebsd-i386 symbol file need tobe updated.

[Christian Marillat]

Package: libopenraw1v5
Version: 0.0.9-3.8
Severity: Serious

Dear Maintainer,

Symbols files need to be updated to fix this FTBFS on kfreebsd-i386

https://buildd.debian.org/status/fetch.php?pkg=libopenraw=kfreebsd-i386=0.0.9-3.8=1445509218

Christian

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

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

Versions of packages libopenraw1v5 depends on:
ii  libc62.19-22
ii  libgcc1  1:5.2.1-22
ii  libjpeg62-turbo  1:1.4.1-2
ii  libstdc++6   5.2.1-22

libopenraw1v5 recommends no packages.

libopenraw1v5 suggests no packages.

-- no debconf information

Processed: tags 784709 patch

[Debian Bug Tracking System]

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

> tags 784709 patch
Bug #784709 [os-prober] os-prober prevent the upgrade to jessie
Added tag(s) patch.
> --
Stopping processing here.

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

Bug#802863: mondrian: FTBFS: error: is not abstract and does not override

[Chris West (Faux)]

Source: mondrian
Version: 1:3.4.1-1
Severity: serious
Justification: fails to build from source
Tags: sid 
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:

compileJdk15:
 [exec] Using JAVA_HOME: /usr/lib/jvm/default-java
 [exec] Using Ant arguments: -Drequested.java.version=jdk1.5 
-Dskip.download=true compile.java
 [exec] Buildfile: /mondrian-3.4.1/build.xml
 [exec] 
 [exec] compile.java:
 [exec]  [echo] Compiling on JVM Version: 1.7.0_85-b01
 [exec] [javac] Compiling 677 source files to /mondrian-3.4.1/classes
 [exec] [javac] 
/mondrian-3.4.1/src/main/mondrian/olap4j/MondrianOlap4jConnection.java:604: 
error:  is not abstract 
and does not override abstract method getName(Object) in NamedList
 [exec] [javac] return new 
AbstractNamedList() {
 [exec] [javac] 
 ^
 [exec] [javac] 
/mondrian-3.4.1/src/main/mondrian/olap4j/MondrianOlap4jMember.java:72: error: 
 is not abstract and does not 
override abstract method getName(Object) in NamedList
 [exec] [javac] return new 
AbstractNamedList() {
 [exec] [javac] 
 ^
 [exec] [javac] 
/mondrian-3.4.1/src/main/mondrian/olap4j/MondrianOlap4jLevel.java:139: error: 
 is not abstract and does not 
override abstract method getName(Object) in NamedList
 [exec] [javac] final NamedList list = new 
ArrayNamedListImpl() {
 [exec] [javac] 
^
 [exec] [javac] 
/mondrian-3.4.1/src/main/mondrian/olap4j/MondrianOlap4jHierarchy.java:91: 
error:  is not abstract 
and does not override abstract method getName(Object) in NamedList
 [exec] [javac] return new AbstractNamedList() {
 [exec] [javac]^
 [exec] [javac] 
/mondrian-3.4.1/src/main/mondrian/olap4j/MondrianOlap4jCellSetMetaData.java:34: 
error:  is not 
abstract and does not override abstract method getName(Object) in NamedList
 [exec] [javac] new ArrayNamedListImpl() {
 [exec] [javac]   ^
 [exec] [javac] 
/mondrian-3.4.1/src/main/mondrian/olap4j/MondrianOlap4jCellSetMetaData.java:62: 
error:  is not 
abstract and does not override abstract method getName(Object) in NamedList
 [exec] [javac] new ArrayNamedListImpl() {
 [exec] [javac]^
 [exec] [javac] 
/mondrian-3.4.1/src/main/mondrian/xmla/RowsetDefinition.java:6519: error: 
 is not 
abstract and does not override abstract method getName(Object) in NamedList
 [exec] [javac] new ArrayNamedListImpl() {
 [exec] [javac] ^
 [exec] [javac] Note: Some input files use or override a deprecated API.
 [exec] [javac] Note: Recompile with -Xlint:deprecation for details.
 [exec] [javac] Note: Some input files use unchecked or unsafe 
operations.
 [exec] [javac] Note: Recompile with -Xlint:unchecked for details.
 [exec] [javac] 7 errors
 [exec] 
 [exec] BUILD FAILED
 [exec] /mondrian-3.4.1/build.xml:553: Compile failed; see the compiler 
error output for details.
 [exec] 
 [exec] Total time: 12 seconds


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

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

Bug#802871: zeal: FTBFS: error: variable 'QDataStream out' has initializer but incomplete type

[Chris West (Faux)]

Source: zeal
Version: 1:0.1.1-2
Severity: serious
Justification: fails to build from source
Tags: sid 
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:

main.cpp: In function ‘int main(int, char**)’:
main.cpp:193:29: error: variable ‘QDataStream out’ has initializer but 
incomplete type
 QDataStream out(socket.data());
 ^
Makefile:737: recipe for target '../.obj/main.o' failed
make[2]: *** [../.obj/main.o] Error 1
make[2]: Leaving directory '/zeal-0.1.1/src'
Makefile:42: recipe for target 'sub-src-make_first-ordered' failed
make[1]: *** [sub-src-make_first-ordered] Error 2

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

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

Bug#802870: xen: FTBFS: error: array subscript is above array bounds

[Chris West (Faux)]

Source: xen
Version: 4.4.1-9+deb8u1
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:

symbols.c: In function ‘symbols_lookup’:
symbols.c:23:61: error: array subscript is above array bounds 
[-Werror=array-bounds]
 #define symbols_address(n) (SYMBOLS_ORIGIN + symbols_offsets[n])
 ^
symbols.c:128:47: note: in expansion of macro ‘symbols_address’
 while (low && symbols_address(low - 1) == symbols_address(low))
   ^
symbols.c:23:61: error: array subscript is above array bounds 
[-Werror=array-bounds]
 #define symbols_address(n) (SYMBOLS_ORIGIN + symbols_offsets[n])
 ^
symbols.c:136:13: note: in expansion of macro ‘symbols_address’
 if (symbols_address(i) > symbols_address(low)) {
 ^
cc1: all warnings being treated as errors
/xen-4.4.1/debian/build/build-hypervisor_amd64_amd64/xen/Rules.mk:165: recipe 
for target 'symbols.o' failed
make[6]: *** [symbols.o] Error 1
make[6]: Leaving directory 
'/xen-4.4.1/debian/build/build-hypervisor_amd64_amd64/xen/common'
/xen-4.4.1/debian/build/build-hypervisor_amd64_amd64/xen/Rules.mk:153: recipe 
for target 
'/xen-4.4.1/debian/build/build-hypervisor_amd64_amd64/xen/common/built_in.o' 
failed
make[5]: *** 
[/xen-4.4.1/debian/build/build-hypervisor_amd64_amd64/xen/common/built_in.o] 
Error 2
make[5]: Leaving directory 
'/xen-4.4.1/debian/build/build-hypervisor_amd64_amd64/xen/arch/x86'
Makefile:100: recipe for target 
'/xen-4.4.1/debian/build/build-hypervisor_amd64_amd64/xen/xen' failed
make[4]: *** [/xen-4.4.1/debian/build/build-hypervisor_amd64_amd64/xen/xen] 
Error 2
make[4]: Leaving directory 
'/xen-4.4.1/debian/build/build-hypervisor_amd64_amd64/xen'

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

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

Bug#802869: qupzilla: FTBFS: error: variable 'QDataStream ds' has initializer but incomplete type

[Chris West (Faux)]

Source: qupzilla
Version: 1.8.6~dfsg1-2
Severity: serious
Justification: fails to build from source
Tags: sid 
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:

3rdparty/qtsingleapplication/qtlocalpeer.cpp: In member function ‘bool 
QtLocalPeer::sendMessage(const QString&, int)’:
3rdparty/qtsingleapplication/qtlocalpeer.cpp:173:19: error: variable 
‘QDataStream ds’ has initializer but incomplete type
 QDataStream ds();
   ^
3rdparty/qtsingleapplication/qtlocalpeer.cpp: In member function ‘void 
QtLocalPeer::receiveConnection()’:
3rdparty/qtsingleapplication/qtlocalpeer.cpp:196:26: error: variable 
‘QDataStream ds’ has initializer but incomplete type
 QDataStream ds(socket);
  ^
Makefile:2716: recipe for target '../../build/qtlocalpeer.o' failed
make[2]: *** [../../build/qtlocalpeer.o] Error 1
make[2]: Leaving directory '/qupzilla-1.8.6~dfsg1/src/lib'
Makefile:44: recipe for target 'sub-src-lib-make_first' failed

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

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

Bug#797292: regina-normal now builds

[Benjamin Burton]

close 797292
thanks

Okay, so on further digging I believe the problem was related to mixed versions 
of boost-regex.  The build failure that was reported in #797292 used a version 
of source-highlight that was built against boost 1.55, whereas the 
regina-normal build itself was using boost 1.58 in regina-normal.  This was 
indeed reported in the build log that was filed with this bug:

/usr/bin/ld: warning: libboost_regex.so.1.55.0, needed by 
/usr/lib/gcc/x86_64-linux-gnu/5/../../../../lib/libsource-highlight.so, may 
conflict with libboost_regex.so.1.58.0

Since source-highlight has been binNMUed to build against boost 1.58, this 
issue should have gone away.  Indeed, when I try it now on sid, the build 
succeeds.

I’m therefore marking this bug as closed - with the passage of time it has 
happily fixed itself.

- Ben.

Bug#802798: marked as done (ecdsautils: FTBFS: Could NOT find PkgConfig)

[Debian Bug Tracking System]

Your message dated Sat, 24 Oct 2015 12:19:23 +
with message-id 
and subject line Bug#802798: fixed in ecdsautils 0.3.2+git20151018-2
has caused the Debian Bug report #802798,
regarding ecdsautils: FTBFS: Could NOT find PkgConfig
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.)


-- 
802798: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802798
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ecdsautils
Version: 0.3.2+git20151018-1
Severity: serious
Justification: fails to build from source

Builds of ecdsautils in minimal environments (notably, on the
autobuilders) have been failing:

  CMake Error at 
/usr/share/cmake-3.3/Modules/FindPackageHandleStandardArgs.cmake:148 (message):
Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
  Call Stack (most recent call first):
/usr/share/cmake-3.3/Modules/FindPackageHandleStandardArgs.cmake:388 
(_FPHSA_FAILURE_MESSAGE)
/usr/share/cmake-3.3/Modules/FindPkgConfig.cmake:48 
(find_package_handle_standard_args)
CMakeLists.txt:4 (find_package)

Please declare a build dependency on pkg-config and confirm with
pbuilder or the like that you haven't missed any others.

Thanks!
--- End Message ---
--- Begin Message ---
Source: ecdsautils
Source-Version: 0.3.2+git20151018-2

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

Debian distribution maintenance software
pp.
Steffen Moeller  (supplier of updated ecdsautils 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: Sat, 24 Oct 2015 13:51:07 +0200
Source: ecdsautils
Binary: ecdsautils
Architecture: source i386
Version: 0.3.2+git20151018-2
Distribution: unstable
Urgency: low
Maintainer: Steffen Moeller 
Changed-By: Steffen Moeller 
Description:
 ecdsautils - ECDSA elliptic curve cryptography command line tools
Closes: 802798
Changes:
 ecdsautils (0.3.2+git20151018-2) unstable; urgency=low
 .
   * Fixed build depends (Closes: #802798).
Checksums-Sha1:
 1f27c49d063a241cc306d45c2c9c2fc13ae0b403 1927 
ecdsautils_0.3.2+git20151018-2.dsc
 2856aee124e2c84e49277bce2bb694737183c9c1 3072 
ecdsautils_0.3.2+git20151018-2.debian.tar.xz
 9fab3fdcd501e5bf40712ddaea97e703f9d01fbd 15462 
ecdsautils_0.3.2+git20151018-2_i386.deb
Checksums-Sha256:
 06ae20fc32b70898ae864c1d8a40447855622848c66035bcbe2c06ea65b62deb 1927 
ecdsautils_0.3.2+git20151018-2.dsc
 4197132edaf4fd6d576ddf243d4f97434d7d094573075de7f559821dcd997814 3072 
ecdsautils_0.3.2+git20151018-2.debian.tar.xz
 7ec9f8f1c5127a813a0bfb2760ac595c5efed8b2bf49348d8779dc8ab3ff9a4a 15462 
ecdsautils_0.3.2+git20151018-2_i386.deb
Files:
 c932dd9fb88e6add0d9b09dd4fa8f904 1927 utils extra 
ecdsautils_0.3.2+git20151018-2.dsc
 f9f70ae51efe7095c71e685fc5529cc0 3072 utils extra 
ecdsautils_0.3.2+git20151018-2.debian.tar.xz
 e3acefd9c776f600d49933132de21482 15462 utils extra 
ecdsautils_0.3.2+git20151018-2_i386.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWK3SbAAoJEC/YvtrAIO7R4vQP/AqlJHEj1rrqmsVHt057eQUj
oXZYsOm0Av+EIw0k+VDq9wWI0LYvKZdDZe/aZtOnOrkK6cVTh3MxFsyGdJrGhmdQ
3hoPvQaT0EcKEZzqbIwMXuQPQJ/4WPSgCw3N1LeQb25wM5JExHH7wvs9D4Bkd42M
n7AhVK1sggqO/3LxojzMmLvvxjcGE+2Kp5ZT1bNNBCYis1/I1ayDl+QKDRXym9vA
vGLWle35GuJMXpFwPqnQDRD8RVkm5n80U4lgMnlhir6DNT/b718pbkBsJD2+W7wN
PYUJJHzx57pJ7A3zlEYgyRqS+jAXrmvbDK960plW3NcTwQB9SAk06OfZiE+I8af9
uHlW4ka8Fzc9Et5cdxEL8y5kBWMPUcpoeiITNTNKXA0Ec44RFZtKJfqHyRtfMGpi
7DH513FMrDpPCwvFLjc+/nqELASl3aybRqkrf6BOZAKVZMBX8qe1pvphognk5PYt
Ii+7YFFw+lcfRu4gPRyseuhHVNBifIxFzY9KT1bwOdVnti7uWPr3RDtbtZ7go/f/
GGZCSHX4LAS261rTg2Liirow1PUDwZDkgbwRCRCS3RYEsdKoYSEoJJe2INelsW2W
L9WVws4DbJJj25j2L6Zk9RPpcYnylXPL2UwfTTGIHCXaIxUiPk9zTPhh1msNvHBI
5GWc1VvYclK7RTkiyL90
=PwJt
-END PGP SIGNATURE End Message ---

Bug#802564: [debian-mysql] Bug#802564: mysql-5.5: Multiple security fixes from the October 2015 CPU

[Salvatore Bonaccorso]

Hi Bjoern,

On Sat, Oct 24, 2015 at 08:11:21AM +, Bjoern Boschman wrote:
> Hi,
> 
> why are the changes not pushed on git?

I worked on it on behalf of the security team and am not part of the
Debian MySQL Maintainers team on alioth. Can you import the changes
based on the dsc's now available via security.d.o to the teams git?
That would be great!

Regards,
Salvatore


signature.asc
Description: Digital signature

Processed: Re: Bug#802764: virtualbox-source: fucks up my kernel's modules

[Debian Bug Tracking System]

Processing control commands:

> tag -1 +moreinfo
Bug #802764 [virtualbox-source] virtualbox-source: fucks up my kernel's modules
Added tag(s) moreinfo.
> severity -1 normal
Bug #802764 [virtualbox-source] virtualbox-source: fucks up my kernel's modules
Severity set to 'normal' from 'critical'

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

Bug#802764: virtualbox-source: fucks up my kernel's modules

[Ritesh Raj Sarraf]

Control: tag -1 +moreinfo
Control: severity -1 normal


For a bug with severity "critical", you should provide appropriate
information. Otherwise it does not justify the severity.


Your logs have nothing mentioned about vbox. So I don't understand how
you'd point this as a vbox problem.


On Fri, 2015-10-23 at 11:14 +0200, Salvo Tomaselli wrote:
> Dear Maintainer,
> 
> apparently upgrading virtualbox messed with my custom built kernel's
> modules,
> and so if I boot with that kernel I no longer have a video card and I
> am not
> able to start Xorg.
> 
> Also, the text on my console is unusually huge.
-- 
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."



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

Processed: Bug#802131 marked as pending

[Debian Bug Tracking System]

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

> tag 802131 pending
Bug #802131 [src:python-django-extensions] python-django-extensions: FTBFS: 
ImportError: No module named 'mongoengine'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#802131: marked as pending

[Brian May]

tag 802131 pending
thanks

Hello,

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


http://git.debian.org/?p=python-modules/packages/python-django-extensions.git;a=commitdiff;h=af4ab35

---
commit af4ab3523d87c156c6ecd24666d42c98480bbcae
Author: Brian May 
Date:   Sat Oct 24 17:55:06 2015 +1100

Fixes FTBFS bug.

diff --git a/debian/changelog b/debian/changelog
index 0664137..b81a827 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,7 @@
 python-django-extensions (1.5.7-1) UNRELEASED; urgency=medium
 
   * New upstream version.
+  * Fixes FTBFS error. Closes: #802131.
 
  -- Brian May   Sat, 24 Oct 2015 14:46:20 +1100
 

Bug#802131: marked as done (python-django-extensions: FTBFS: ImportError: No module named 'mongoengine')

[Debian Bug Tracking System]

Your message dated Sat, 24 Oct 2015 07:19:31 +
with message-id 
and subject line Bug#802131: fixed in python-django-extensions 1.5.7-1
has caused the Debian Bug report #802131,
regarding python-django-extensions: FTBFS: ImportError: No module named 
'mongoengine'
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.)


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

Dear Maintainer,

The package fails to build:

WARNINGS:
?: (1_7.W001) MIDDLEWARE_CLASSES is not set.
HINT: Django 1.7 changed the global defaults for the 
MIDDLEWARE_CLASSES. django.contrib.sessions.middleware.SessionMiddleware, 
django.contrib.auth.middleware.AuthenticationMiddleware, and 
django.contrib.messages.middleware.MessageMiddleware were removed from the 
defaults. If your project needs these middleware then you should configure this 
setting.
ERROR

==
ERROR: django_extensions.mongodb.fields (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: django_extensions.mongodb.fields
Traceback (most recent call last):
  File "/usr/lib/python3.5/unittest/loader.py", line 462, in _find_test_path
package = self._get_module_from_name(name)
  File "/usr/lib/python3.5/unittest/loader.py", line 369, in 
_get_module_from_name
__import__(name)
  File 
"/python-django-extensions-1.5.0/django_extensions/mongodb/fields/__init__.py", 
line 14, in 
from mongoengine.fields import StringField, DateTimeField
ImportError: No module named 'mongoengine'


==
ERROR: testUUIDFieldManyToManyCreate 
(django_extensions.tests.shortuuid_field.ShortUUIDFieldTest)
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 65, 
in execute
return self.cursor.execute(sql, params)
  File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py", 
line 485, in execute
return Database.Cursor.execute(self, query, params)
sqlite3.IntegrityError: UNIQUE constraint failed: 
django_extensions_shortuuidtestmanytomanymodel.shortuuidtestmodel_pk_ptr_id

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File 
"/python-django-extensions-1.5.0/django_extensions/tests/shortuuid_field.py", 
line 37, in testUUIDFieldManyToManyCreate
j = 
ShortUUIDTestManyToManyModel.objects.create(uuid_field=six.u('vytxeTZskVKR7C7WgdSP3e'))
  File "/usr/lib/python3/dist-packages/django/db/models/manager.py", line 92, 
in manager_method
return getattr(self.get_queryset(), name)(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 372, in 
create
obj.save(force_insert=True, using=self.db)
  File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 589, in 
save
force_update=force_update, update_fields=update_fields)
  File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 617, in 
save_base
updated = self._save_table(raw, cls, force_insert, force_update, using, 
update_fields)
  File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 698, in 
_save_table
result = self._do_insert(cls._base_manager, using, fields, update_pk, raw)
  File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 731, in 
_do_insert
using=using, raw=raw)
  File "/usr/lib/python3/dist-packages/django/db/models/manager.py", line 92, 
in manager_method
return getattr(self.get_queryset(), name)(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 921, in 
_insert
return query.get_compiler(using=using).execute_sql(return_id)
  File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 
921, in execute_sql
cursor.execute(sql, params)
  File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 65, 
in execute
return self.cursor.execute(sql, params)
  File "/usr/lib/python3/dist-packages/django/db/utils.py", line 94, in __exit__

Bug#802860: eliom: FTBFS: the new definition of Svg does not match its original definition in the constrained signature

[Chris West (Faux)]

Source: eliom
Version: 4.0.0-2
Severity: serious
Justification: fails to build from source
Tags: sid 
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:

File "eliom_content_core.mli", line 154, characters 17-333:
Error: In this `with' constraint, the new definition of Svg
   does not match its original definition in the constrained signature:
   ...
   Values do not match:
 val a_onclick : Xml.mouse_event_handler -> [> `OnClick ] attrib
   is not included in
 val a_onclick : Xml.mouse_event_handler -> [> `OnClick ] attrib
Makefile:54: recipe for target 'eliom_content_core.cmi' failed
make[4]: *** [eliom_content_core.cmi] Error 2
make[4]: Leaving directory '/eliom-4.0.0/src/server'
Makefile:4: recipe for target 'all' failed

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

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

Bug#802859: cross-binutils: FTBFS: armhf on amd64: dpkg-checkbuilddeps: error: Unmet build dependencies: chrpath

[Chris West (Faux)]

Source: cross-binutils
Version: 0.26
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, due to a missing build-dep for a nested
dpkg-buildpackage call(?).  It fails for both pbuilder and for my
apt-get based builder:

touch stamp/init
START stamp/build-armhf
set -e; \
cd binutils-2.25.1; \
DEB_TARGET_ARCH=armhf TARGET=armhf dpkg-buildpackage -T control-stamp; \
WITH_SYSROOT=/ DEB_TARGET_ARCH=armhf TARGET=armhf dpkg-buildpackage -B -uc -us; 
\
cd ..; \
touch stamp/build-armhf
dpkg-buildpackage: source package binutils
dpkg-buildpackage: source version 2.25.1-7
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage: source changed by Matthias Klose 
dpkg-buildpackage: host architecture amd64
dpkg-checkbuilddeps: error: Unmet build dependencies: chrpath
dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting
dpkg-buildpackage: warning: (Use -d flag to override.)
debian/rules:54: recipe for target 'stamp/build-armhf' failed
make: *** [stamp/build-armhf] Error 3
dpkg-buildpackage: error: debian/rules build gave error exit status 2

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

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

Bug#802865: nss-passwords: FTBFS: ocaml/caml/config.h: error: conflicting types for 'int64'

[Chris West (Faux)]

Source: nss-passwords
Version: 0.2-1
Severity: serious
Justification: fails to build from source
Tags: sid 
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:

ocamlfind ocamlc -g -package fileutils.str,sqlite3,atdgen -ccopt 
-I/usr/include/nss -ccopt -I/usr/include/nspr -c nss_stubs.c
In file included from /usr/lib/ocaml/caml/mlvalues.h:20:0,
 from nss_stubs.c:48:
/usr/lib/ocaml/caml/config.h:123:25: error: conflicting types for ‘int64’
 typedef ARCH_INT64_TYPE int64;
 ^
In file included from /usr/include/nspr/prtypes.h:574:0,
 from /usr/include/nspr/pratom.h:14,
 from /usr/include/nspr/nspr.h:9,
 from nss_stubs.c:39:
/usr/include/nspr/obsolete/protypes.h:104:17: note: previous declaration of 
‘int64’ was here
 typedef PRInt64 int64;
 ^
In file included from /usr/lib/ocaml/caml/mlvalues.h:20:0,
 from nss_stubs.c:48:
/usr/lib/ocaml/caml/config.h:124:26: error: conflicting types for ‘uint64’
 typedef ARCH_UINT64_TYPE uint64;
  ^
In file included from /usr/include/nspr/prtypes.h:574:0,
 from /usr/include/nspr/pratom.h:14,
 from /usr/include/nspr/nspr.h:9,
 from nss_stubs.c:39:
/usr/include/nspr/obsolete/protypes.h:68:18: note: previous declaration of 
‘uint64’ was here
 typedef PRUint64 uint64;
  ^
Makefile:27: recipe for target 'nss_stubs.o' failed
make[1]: *** [nss_stubs.o] Error 2
make[1]: Leaving directory '/nss-passwords-0.2'

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

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

Bug#802868: quassel: FTBFS: error: ambiguous overload for 'operator<<' (operand types are 'QDataStream' and 'quint64 {aka long long unsigned int}')

[Chris West (Faux)]

Source: quassel
Version: 1:0.12.2-1
Severity: serious
Justification: fails to build from source
Tags: sid 
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:

/quassel-0.12.2/src/common/peer.cpp: In function ‘QDataStream& 
operator<<(QDataStream&, PeerPtr)’:
/quassel-0.12.2/src/common/peer.cpp:43:9: error: ambiguous overload for 
‘operator<<’ (operand types are ‘QDataStream’ and ‘quint64 {aka long long 
unsigned int}’)
 out << reinterpret_cast(ptr);
 ^
In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:41:0,
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:41,
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/qiodevice.h:39,
 from 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork/qabstractsocket.h:37,
 from 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork/QAbstractSocket:1,
 from /quassel-0.12.2/src/common/peer.h:24,
 from /quassel-0.12.2/src/common/peer.cpp:21:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qchar.h:584:28: note: candidate: 
QDataStream& operator<<(QDataStream&, QChar)
 Q_CORE_EXPORT QDataStream <<(QDataStream &, QChar);
^
In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qlocale.h:37:0,
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/qtextstream.h:40,
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/qdebug.h:42,
 from 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork/qabstractsocket.h:40,
 from 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork/QAbstractSocket:1,
 from /quassel-0.12.2/src/common/peer.h:24,
 from /quassel-0.12.2/src/common/peer.cpp:21:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qvariant.h:534:28: note: candidate: 
QDataStream& operator<<(QDataStream&, const QVariant&)
 Q_CORE_EXPORT QDataStream& operator<< (QDataStream& s, const QVariant& p);
^
/quassel-0.12.2/src/common/peer.cpp: In function ‘QDataStream& 
operator>>(QDataStream&, Peer*&)’:
/quassel-0.12.2/src/common/peer.cpp:50:8: error: ambiguous overload for 
‘operator>>’ (operand types are ‘QDataStream’ and ‘quint64 {aka long long 
unsigned int}’)
 in >> value;
^
In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:41:0,
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:41,
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/qiodevice.h:39,
 from 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork/qabstractsocket.h:37,
 from 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork/QAbstractSocket:1,
 from /quassel-0.12.2/src/common/peer.h:24,
 from /quassel-0.12.2/src/common/peer.cpp:21:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qchar.h:585:28: note: candidate: 
QDataStream& operator>>(QDataStream&, QChar&) 
 Q_CORE_EXPORT QDataStream >>(QDataStream &, QChar &);
^
...

/quassel-0.12.2/src/common/peer.cpp:47:14: note: candidate: QDataStream& 
operator>>(QDataStream&, Peer*&) 
 QDataStream >>(QDataStream , PeerPtr )
  ^
/quassel-0.12.2/src/common/peer.cpp:47:14: note:   conversion of argument 2 
would be ill-formed:
/quassel-0.12.2/src/common/peer.cpp:50:11: error: invalid conversion from 
‘quint64 {aka long long unsigned int}’ to ‘PeerPtr {aka Peer*}’ [-fpermissive]
 in >> value;
   ^
/quassel-0.12.2/src/common/peer.cpp:50:11: error: cannot bind rvalue 
‘(PeerPtr)value’ to ‘Peer*&’
src/common/CMakeFiles/mod_common.dir/build.make:665: recipe for target 
'src/common/CMakeFiles/mod_common.dir/peer.cpp.o' failed
make[3]: *** [src/common/CMakeFiles/mod_common.dir/peer.cpp.o] Error 1
make[3]: Leaving directory '/quassel-0.12.2/obj-x86_64-linux-gnu'
CMakeFiles/Makefile2:486: recipe for target 
'src/common/CMakeFiles/mod_common.dir/all' failed
make[2]: *** [src/common/CMakeFiles/mod_common.dir/all] Error 2

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

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

Processed: regina-normal builds again

[Debian Bug Tracking System]

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

> close 797292
Bug #797292 [src:regina-normal] regina-normal: FTBFS: undefined reference to 
`srchilite::Utils::toupper...
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#802861: kalzium: FTBFS: gasCalculator.h: error: expected unqualified-id before numeric constant

[Chris West (Faux)]

Source: kalzium
Version: 4:15.08.0-1
Severity: serious
Justification: fails to build from source
Tags: sid 
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:

In file included from ../../src/calculator/calculator.h:27:0,
 from ../../src/kalzium.h:24,
 from ../../src/kalzium.cpp:13:
/usr/include/eigen3/Eigen/src/Core/products/GeneralBlockPanelKernel.h: In 
member function ‘void Eigen::internal::gebp_kernel::operator()(const DataMapper&, 
const LhsScalar*, const RhsScalar*, Index, Index, Index, 
Eigen::internal::gebp_kernel::ResScalar, Index, Index, Index, Index)’:
../../src/calculator/gasCalculator.h:31:11: error: expected unqualified-id 
before numeric constant
 #define R 0.08206
   ^
../../src/calculator/gasCalculator.h:31:11: error: expected unqualified-id 
before numeric constant
 #define R 0.08206
   ^
src/CMakeFiles/kalzium.dir/build.make:736: recipe for target 
'src/CMakeFiles/kalzium.dir/kalzium.o' failed
make[4]: *** [src/CMakeFiles/kalzium.dir/kalzium.o] Error 1
make[4]: Leaving directory '/kalzium-15.08.0/obj-x86_64-linux-gnu'

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

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

Bug#802564: [debian-mysql] Bug#802564: mysql-5.5: Multiple security fixes from the October 2015 CPU

[Bjoern Boschman]

Hi,

why are the changes not pushed on git?

Cheers
B

On Fri, Oct 23, 2015 at 1:45 PM Salvatore Bonaccorso 
wrote:

>
> Hi MySQL team,
>
> FTR, I have now an update ready which I would push to security-master
> soon for wheezy- and jessie-security.
>
> Regards,
> Salvatore
>
> ___
> pkg-mysql-maint mailing list
> pkg-mysql-ma...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint
>

Bug#802855: [phpmyadmin] Unable to upgrade

[Antonio Marcos López Alonso]

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

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

Unable to perform last upgrade:

dbconfig-common: writing config to /etc/dbconfig-common/phpmyadmin.conf
creating database backup in /var/cache/dbconfig-
common/backups/phpmyadmin_4:4.4.15-1.2015-10-24-11.24.30.
applying upgrade sql for 4:4.4.15-1 -> 4:4.5.0.2-1.
error encountered processing /usr/share/dbconfig-
common/data/phpmyadmin/upgrade/mysql/4:4.5.0.2-1:
mysql said: ERROR 1060 (42S21) at line 28: Duplicate column name 
'input_transformation'

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

Debian Release: stretch/sid
  900 testing security.debian.org 
  900 testing ftp.es.debian.org 
  500 wilyppa.launchpad.net 
  500 unstableftp.es.debian.org 
  500 trusty  ppa.launchpad.net 
  500 stable  update.devolo.com 
  500 stable  kxstudio.linuxaudio.org 
  500 stable  dl.google.com 
  500 sid linux.dropbox.com 
  500 lucid   ppa.launchpad.net 
  500 gcc5kxstudio.linuxaudio.org 

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.

Bug#802862: libgnatcoll: FTBFS: unit "gnatcoll.refcount.sync_counters" cannot belong to several projects

[Chris West (Faux)]

Source: libgnatcoll
Version: 1.6gpl2014-8
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:

   debian/rules override_dh_ada_library
make[1]: Entering directory '/libgnatcoll-1.6gpl2014'
dh_ada_library src/gnatcoll.gpr src/gnatcoll_python.gpr src/gnatcoll_iconv.gpr 
src/gnatcoll_sqlite.gpr src/gnatcoll_readline.gpr src/gnatcoll_gmp.gpr 
src/gnatcoll_gtk.gpr
gnatcoll_python.gpr:4:09: unit "gnatcoll.arg_lists" cannot belong to several 
projects
gnatcoll_python.gpr:4:09:   project "gnatcoll_python", 
"/libgnatcoll-1.6gpl2014/src/gnatcoll-arg_lists.ads"
gnatcoll_python.gpr:4:09:   project "gnatcoll", 
"/libgnatcoll-1.6gpl2014/src/gnatcoll-arg_lists.ads"
gnatcoll_python.gpr:4:09: unit "gnatcoll.boyer_moore" cannot belong to several 
projects
gnatcoll_python.gpr:4:09:   project "gnatcoll_python", 
"/libgnatcoll-1.6gpl2014/src/gnatcoll-boyer_moore.ads"
gnatcoll_python.gpr:4:09:   project "gnatcoll", 
"/libgnatcoll-1.6gpl2014/src/gnatcoll-boyer_moore.ads"
gnatcoll_python.gpr:4:09: unit "gnatcoll.traces" cannot belong to several 
projects
gnatcoll_python.gpr:4:09:   project "gnatcoll_python", 
"/libgnatcoll-1.6gpl2014/src/gnatcoll-traces.ads"
gnatcoll_python.gpr:4:09:   project "gnatcoll", 
"/libgnatcoll-1.6gpl2014/src/gnatcoll-traces.ads"

...

raised PROJECTS.PARSE_ERROR : "src/gnatcoll_python.gpr"
debian/rules:158: recipe for target 'override_dh_ada_library' failed
make[1]: *** [override_dh_ada_library] Error 1
make[1]: Leaving directory '/libgnatcoll-1.6gpl2014'

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

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

Bug#802705: marked as done (musescore: FTBFS while rebuilding against newest Qt5 private headers)

[Debian Bug Tracking System]

Your message dated Sat, 24 Oct 2015 11:49:37 +
with message-id 
and subject line Bug#802705: fixed in musescore 2.0.2+dfsg-2
has caused the Debian Bug report #802705,
regarding musescore: FTBFS while rebuilding against newest Qt5 private headers
to be marked as done.

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

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


-- 
802705: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802705
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: musescore
Version: 2.0.2+dfsg-1
Severity: serious
Justification: FTBFS

Hi! Musescore FTBFS when rebuilding against the new Qtbase's private headers:

https://buildd.debian.org/status/package.php?p=musescore

The problem seems to be:

/«BUILDDIR»/musescore-2.0.2+dfsg/libmscore/clef.cpp:58:7: error: narrowing 
conversion of '-1' from 'int' to 'char' inside { } [-Wnarrowing]
   };



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

Kernel: Linux 4.2.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: musescore
Source-Version: 2.0.2+dfsg-2

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated musescore 
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: Sat, 24 Oct 2015 13:22:28 +0200
Source: musescore
Binary: musescore musescore-common musescore-soundfont-gm
Architecture: source all
Version: 2.0.2+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Sebastian Ramacher 
Description:
 musescore  - Free music composition and notation software
 musescore-common - Free music composition and notation software (common files)
 musescore-soundfont-gm - Old MuseScore soundfont (dummy package)
Closes: 790106 802705
Changes:
 musescore (2.0.2+dfsg-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Tiago Bortoletto Vaz ]
   * Fix Worng list formatting in package description. Thanks to Beatrice
 Torracca. (Closes: #790106)
 .
   [ Sebastian Ramacher ]
   * debian/patches/03-fix-when-char-defaults-to-unsigned.patch: Apply upstream
 patch to fix FTBFS on arm* (Closes: #802705)
Checksums-Sha1:
 519f7b2665336ca3368beb99984e64d32e0abdb8 2468 musescore_2.0.2+dfsg-2.dsc
 c709f74991b2278a52327d52c74488e3254048fe 12504 
musescore_2.0.2+dfsg-2.debian.tar.xz
 6b163f150b708ee178f34b0a8e8f7d19e217505d 12008094 
musescore-common_2.0.2+dfsg-2_all.deb
 4f761cda97200b63a5ccd2ccb6ae3b50fc89df96 10556 
musescore-soundfont-gm_2.0.2+dfsg-2_all.deb
Checksums-Sha256:
 cae1132513145bee4e84584d7a45c11b995e68fb35f59c9aa3e005853381a5ee 2468 
musescore_2.0.2+dfsg-2.dsc
 293247457a04a1cf53310d701eb2c00dc14d9a2daacb2374173c253008d493cb 12504 
musescore_2.0.2+dfsg-2.debian.tar.xz
 8bbee882ac987857f180e5a1bd0104b70e9e1f8c264ea0d5ef0c554da1a3e3ba 12008094 
musescore-common_2.0.2+dfsg-2_all.deb
 9b21b62b23434a578e61ed4609bd599ea3ddab96c224818e1e39234fa62cc98e 10556 
musescore-soundfont-gm_2.0.2+dfsg-2_all.deb
Files:
 2c08ab7dc4636f406dbb6a1eba57f1e0 2468 sound optional musescore_2.0.2+dfsg-2.dsc
 552ba08b30a8aaf95c0098801607757e 12504 sound optional 
musescore_2.0.2+dfsg-2.debian.tar.xz
 def8eba8b564e5d5fc5c3a0f319f1fa9 12008094 sound optional 
musescore-common_2.0.2+dfsg-2_all.deb
 fdaf969ea6e433143f8a545f09958b56 10556 sound optional 
musescore-soundfont-gm_2.0.2+dfsg-2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWK23nAAoJEGny/FFupxmTzzMP/Rj3cyP03TPRZWP8koy+uWH+
PlCa7btWiANIro3yMnm3KlJUYiOMNqAscU0Qap0vL81rZXb+Ji9fRrBRlIQpn2aY
toFm3tl43sZZ3nme9HZshLHGzj0NkSJzJ2n/+eJhgtBdHEiagbQ+JYA2fgd7Bb1T