Bug#837040: RFS: btrfs-progs/4.7.2-0.1 [RC NMU]

[Nicholas D Steeves]

Control: retitle -1 'RFS: btrfs-progs/4.7.2-0.1 [RC NMU]'

Was almost asleep and then realised this; here is the correct link:
 dget -x 
https://mentors.debian.net/debian/pool/main/b/btrfs-progs/btrfs-progs_4.7.2-0.1.dsc

Humble regards,
Nicholas


signature.asc
Description: Digital signature

Processed: Re: Bug#837040: RFS: btrfs-progs/4.7.2-0.1 [RC NMU]

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 'RFS: btrfs-progs/4.7.2-0.1 [RC NMU]'
Bug #837040 [sponsorship-requests] RFS: btrfs-progs/4.7.1-1~bpo8+1 [RC NMU]
Changed Bug title to ''RFS: btrfs-progs/4.7.2-0.1 [RC NMU]'' from 'RFS: 
btrfs-progs/4.7.1-1~bpo8+1 [RC NMU]'.

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

Bug#837040: RFS: btrfs-progs/4.7.1-1~bpo8+1 [RC NMU]

[Nicholas D Steeves]

On Thu, Sep 08, 2016 at 07:11:31AM +0200, Adam Borowski wrote:
> On Thu, Sep 08, 2016 at 12:57:32AM -0400, Nicholas D Steeves wrote:
> > Package: sponsorship-requests
> > Severity: grave
> > 
> > I am looking for a sponsor for an urgent NMU of "btrfs-progs".  Upstream
> > has marked this as an "urgent fix" <
> > https://btrfs.wiki.kernel.org/index.php/Changelog#btrfs-progs-4.7.2_.28Sep_2016.29
> 
> > Package name: btrfs-progs
> > Version : 4.7.1-1~bpo8+1
> 
> Except, you see, it's 4.7 and 4.7.1 which are the buggy versions, 4.6.1 is
> unaffected.  So you demand, with a grave severity, to overwrite a known-good
> version with one with a data loss bug.
> 
> -- 
> Second "wet cat laying down on a powered on box-less SoC on the desk" close
> shave in a week.  Protect your ARMs, folks!

I hit "r" instead of "g", so my last reply didn't make it to the bug-tracker.  
This is an error in my bug submission, and I am embarassed I made that mistake 
(too late here, I'm going to sleep).  It should read:

Package name: btrfs-progs
Version : 4.7.2-0.1

5 Sept (I think, it might have been earlier) I asked Gianfranco to cancel my 
bpo in the deferred queue because of this issue.

Thank you,
Nicholas


signature.asc
Description: Digital signature

Bug#837040: RFS: btrfs-progs/4.7.1-1~bpo8+1 [RC NMU]

[Adam Borowski]

On Thu, Sep 08, 2016 at 12:57:32AM -0400, Nicholas D Steeves wrote:
> Package: sponsorship-requests
> Severity: grave
> 
> I am looking for a sponsor for an urgent NMU of "btrfs-progs".  Upstream
> has marked this as an "urgent fix" <
> https://btrfs.wiki.kernel.org/index.php/Changelog#btrfs-progs-4.7.2_.28Sep_2016.29

> Package name: btrfs-progs
> Version : 4.7.1-1~bpo8+1

Except, you see, it's 4.7 and 4.7.1 which are the buggy versions, 4.6.1 is
unaffected.  So you demand, with a grave severity, to overwrite a known-good
version with one with a data loss bug.

-- 
Second "wet cat laying down on a powered on box-less SoC on the desk" close
shave in a week.  Protect your ARMs, folks!

Bug#837040: RFS: btrfs-progs/4.7.1-1~bpo8+1 [RC NMU]

[Nicholas D Steeves]

Package: sponsorship-requests
Severity: grave

Dear mentors,

I am looking for a sponsor for an urgent NMU of "btrfs-progs".  Upstream has 
marked this as an "urgent fix" < 
https://btrfs.wiki.kernel.org/index.php/Changelog#btrfs-progs-4.7.2_.28Sep_2016.29
 >

Sept 5th I filed bug #836778 notifying the maintainer of the issue.

Package name: btrfs-progs
Version : 4.7.1-1~bpo8+1
Section : admin

It builds these binary packages:

btrfs-progs - Checksumming Copy on Write Filesystem utilities
btrfs-progs-dbg - Checksumming Copy on Write Filesystem utilities (debug)
btrfs-progs-udeb - Checksumming Copy on Write Filesystem utilities (udeb) (udeb)
btrfs-tools - transitional dummy package
btrfs-tools-dbg - transitional dummy package

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

  https://mentors.debian.net/package/btrfs-progs

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

  dget -x 
https://mentors.debian.net/debian/pool/main/b/btrfs-progs/btrfs-progs_4.7.1-1~bpo8+1.dsc

It is also available here:

  https://github.com/sten0/btrfs-progs.git

Changes since the last upload:

   * Non-maintainer upload.
   * New upstream release. (Closes #836778)

Regards,
Nicholas


signature.asc
Description: Digital signature

Bug#834744: marked as done (xmlgraphics-commons: FTBFS (missing build-depends on gnupg))

[Debian Bug Tracking System]

Your message dated Thu, 08 Sep 2016 04:32:35 +
with message-id 
and subject line Bug#834744: fixed in xmlgraphics-commons 2.1-2
has caused the Debian Bug report #834744,
regarding xmlgraphics-commons: FTBFS (missing build-depends on gnupg)
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.)


-- 
834744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834744
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:xmlgraphics-commons
Version: 2.1-1
Severity: serious
Tags: patch

Dear maintainer:

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


[...]
BUILD FAILED
/<>/build.xml:620: The following error occurred while executing 
this line:
/<>/build.xml:591: Execute failed: java.io.IOException: Cannot run 
program "gpg" (in directory "/<>"): error=2, No such file or 
directory


The gnupg package is not essential. Therefore, whenever a package
requires it for building there should be a build-dependency on it.

Trivial (but untested) patch below.

Thanks.

--- a/debian/control
+++ b/debian/control
@@ -8,6 +8,7 @@ Build-Depends: debhelper (>= 9), javahelper
 Build-Depends-Indep: ant-optional,
  default-jdk,
  default-jdk-doc,
+ gnupg,
  junit4,
  libcommons-io-java (>= 1.3.1),
  libcommons-logging-java,
--- End Message ---
--- Begin Message ---
Source: xmlgraphics-commons
Source-Version: 2.1-2

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated xmlgraphics-commons 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 08 Sep 2016 04:31:18 +0200
Source: xmlgraphics-commons
Binary: libxmlgraphics-commons-java libxmlgraphics-commons-java-doc
Architecture: source
Version: 2.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Description:
 libxmlgraphics-commons-java - Reusable components used by Batik and FOP
 libxmlgraphics-commons-java-doc - Reusable components used by Batik and FOP 
(documentation)
Closes: 834744
Changes:
 xmlgraphics-commons (2.1-2) unstable; urgency=medium
 .
   * Team upload.
   * Add gnupg to Build-Depends. (Closes: #834744)
   * Declare compliance with Debian Policy 3.9.8.
   * Vcs-Browser: Use https.
Checksums-Sha1:
 2eb650caf7e573f976ce48ece74c3c838fb71544 2520 xmlgraphics-commons_2.1-2.dsc
 7697479fb6f2c08b76af2725c2f8d5ffab7b7da0 9172 
xmlgraphics-commons_2.1-2.debian.tar.xz
Checksums-Sha256:
 3806c4963f51f6235e8387df4e7ff5e3bad13265f0f34f90844bf3411ffd5de1 2520 
xmlgraphics-commons_2.1-2.dsc
 8926c4d5d7294301a6b98713f8cb10315e70b5c92242eb2776c8989b3fe6b6ba 9172 
xmlgraphics-commons_2.1-2.debian.tar.xz
Files:
 4fe30b56155cff8ab380d45cd9ba27cc 2520 java optional 
xmlgraphics-commons_2.1-2.dsc
 4202406c535574878627080ab98a6777 9172 java optional 
xmlgraphics-commons_2.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKMBAEBCgB2BQJX0M+rXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBQ0YzRDA4OEVGMzJFREVGNkExQTgzNUZE
OUFEMTRCOTUxM0I1MUU0DxxhcG9AZGViaWFuLm9yZwAKCRDZrRS5UTtR5IzMEADL
5GII5wLn/D0B5pID4JK6Hw4FiM016Aek06kjrxCIv6LwH1SxzY8poIVguFOXpe+l
Lg38f3adzLPJf8E6V2fr7uPcaj97wcdb1s2j2ZilhwATbC5PVE1i62OSKE9RHl+C
dtTFhLMR9vvVdsS0my40Qru7jBbsBARo4Yk6z3QA1zB1Yj/dkFjjlTldJgoZNtdQ
Pqn09X+IIwxGq8lQQQefWtelnfr3zQ7RZ9ryrS/Or4pXuCbzK1ohfx7H0eqcAoDN
/3bmTzibGH9F3pLFgof/g042kJ1Ftz8tzQcJsFVP2Q7iDs0wO46JRAlOV308WU8b
QYb9FAbq2z8X1KuHDE9zJkMcg65Au/U7IBdHa0GPO7HXxkqJ5kAkpKq8N0XNwHLR
6u/Hp7kiqj9A+Num69oWA95lKBcoNHax1XqCSawXbpO13BtmKGD7ncFP9sIzJWSE

Processed: Re: Bug#837030: gdk-pixbuf: FTBFS on most architectures due to test failures

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=771026
Bug #837030 [src:gdk-pixbuf] gdk-pixbuf: FTBFS on most architectures due to 
test failures
Set Bug forwarded-to-address to 
'https://bugzilla.gnome.org/show_bug.cgi?id=771026'.

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

Bug#837030: gdk-pixbuf: FTBFS on most architectures due to test failures

[Michael Biebl]

Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=771026

We've already seen the issue and forwarded to upstream.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#832077: Info received (emacs clutter screen on windows switch)

[Leon Meier]

By the way, I don't know who is the culprit: libgtk-3-0, emacs, or 
someone else. So please consider my found / nofound tags just as 
additional information on my configuration rather as a bug source hint. 
Sorry about that.

Processed: tagging 837036

[Debian Bug Tracking System]

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

> tags 837036 + sid
Bug #837036 [gitolite3] gitolite3: uninstallable without . in @INC
Added tag(s) sid.
> thanks
Stopping processing here.

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

Bug#832077: emacs clutter screen on windows switch

[Leon Meier]

found 832077 libgtk-3-0/3.21.5-3
thanks

Processed: emacs clutter screen on windows switch

[Debian Bug Tracking System]

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

> found 832077 libgtk-3-0/3.21.5-3
Bug #832077 [libgtk-3-0] Gtk-WARNING **: EmacsFixed 0x95c12e8 is drawn without 
a current allocation. This should not happen.
Bug #836426 [libgtk-3-0] Graphics rendering (with QXL graphics) doesn't update
The source libgtk-3-0 and version 3.21.5-3 do not appear to match any binary 
packages
Marked as found in versions libgtk-3-0/3.21.5-3.
Marked as found in versions libgtk-3-0/3.21.5-3.
> thanks
Stopping processing here.

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

Processed: emacs clutter screen on windows switch

[Debian Bug Tracking System]

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

> found 832077 emacs/46.1
Bug #832077 [libgtk-3-0] Gtk-WARNING **: EmacsFixed 0x95c12e8 is drawn without 
a current allocation. This should not happen.
Bug #836426 [libgtk-3-0] Graphics rendering (with QXL graphics) doesn't update
The source emacs and version 46.1 do not appear to match any binary packages
Marked as found in versions emacs/46.1.
Marked as found in versions emacs/46.1.
> thanks
Stopping processing here.

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

Bug#837036: gitolite3: uninstallable without . in @INC

[David Bremner]

Package: gitolite3
Version: 3.6.4-1
Severity: serious
Tags: upstream
Justification: uninstallable
User: debian-p...@lists.debian.org
Usertags: perl-cwd-inc-removal

The package fails to configure with the new default settings for @INC.

This is fixed in upstream commit 35e0b2a. Rather than cherry-picking
that, I'm planning to wait for a new upstream release, which should be
less than a week.


Setting up gitolite3 (3.6.4-1) ...
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based 
frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 
76.)
debconf: falling back to frontend: Readline
Configuring gitolite3
-

Please specify the key of the user that will administer the access 
configuration of gitolite.

This can be either the SSH public key itself, or the path to a file containing 
it. If it is blank, gitolite will 
be left unconfigured and must be set up manually.

If migrating from gitolite version 2.x, leave this blank.

Administrator's SSH key: /tmp/bremner.pub


Initialized empty Git repository in 
/var/lib/gitolite3/repositories/gitolite-admin.git/
Initialized empty Git repository in /var/lib/gitolite3/repositories/testing.git/
FATAL: parse 'conf/gitolite.conf-compiled.pm' failed: No such file or directory
dpkg: error processing package gitolite3 (--configure):


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

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

Versions of packages gitolite3 depends on:
ii  adduser  3.115
ii  debconf [debconf-2.0]1.5.59
ii  git [git-core]   1:2.9.3-1
ii  libjson-perl 2.90-1
ii  openssh-server [ssh-server]  1:7.3p1-1
ii  perl 5.22.2-3

gitolite3 recommends no packages.

Versions of packages gitolite3 suggests:
pn  git-daemon-sysvinit  
pn  gitweb   

-- debconf information:
  gitolite3/gitdir: /var/lib/gitolite3
* gitolite3/adminkey:
  gitolite3/gituser: gitolite3

Bug#832077: emacs clutter screen on windows switch

[Leon Meier]

found 832077 emacs/46.1
thanks

The message

(emacs:6144): Gtk-WARNING **: GtkWindow 0xc50270 is drawn without a 
current allocation. This should not happen.


is printed to xterm from where emacs was started. Printing happens  when 
the emacs window gets the focus due to a left-button mouse click.


For me, it's not a huge trouble, but still, annoying.

Bug#836426: Caused by libgtk-3-0 3.21

[Josh Triplett]

On Thu, Sep 08, 2016 at 02:24:37AM +0200, Michael Biebl wrote:
> On Wed, 7 Sep 2016 09:21:55 -0700 Josh Triplett 
> wrote:
> > Control: reassign -1 libgtk-3-0 3.21.5-3
> > Control: affects -1 gnome-boxes
> > Control: severity -1 serious
> > Control: forcemerge -1 832077
> 
> To me those two issues look not like they are related.
> 
> After all, this one was file for 3.20, the other one for 3.21.

Both bugs were filed for libgtk-3-0 3.21.  (836426 was originally filed
on gnome-boxes 3.20 but running with libgtk-3-0 3.21, and I can confirm
that the issue disappears when downgrading to libgtk-3-0 3.20 and
reappears when upgrading to libgtk-3-0 3.21.  All three mails in 832077
specifically mentioned libgtk-3-0 3.21.)  None of the reports apply to
libgtk-3-0 3.20.

I changed the applicable version number when reassigning to libgtk-3-0,
and as far as I can tell that did update the BTS metadata correctly.

> The severity seems overinflated as well.

It seems appropriate for an issue that causes window contents to fail to
render, making gnome-boxes unusable with that version of GTK+.  It also
seems appropriate for what looks like a backwards-compatibility issue in
GTK+.  "serious" seems appropriate for "this shouldn't get released in
the next stable release".

Bug#836384: marked as done (ignition-transport: breaks with new protobuf3, and link failures)

[Debian Bug Tracking System]

Your message dated Thu, 08 Sep 2016 01:19:46 +
with message-id 
and subject line Bug#836384: fixed in ignition-transport 1.3.0-3
has caused the Debian Bug report #836384,
regarding ignition-transport: breaks with new protobuf3, and link failures
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.)


-- 
836384: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836384
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ignition-transport
Version: 1.3.0-2
Severity: serious

Hi, the latest protobuf3 broke ignition-transport testsuite and package, lets 
analyze the issues:
(based on the main on debian/tests
#include 

int main()
{
// Create a transport node.
ignition::transport::Uuid uuid;
return 0;
}



first issue:
./build 
In file included from 
/usr/include/ignition/transport1/ignition/transport/NodeShared.hh:40:0,
from /usr/include/ignition/transport1/ignition/transport/Node.hh:41,
from /usr/include/ignition/transport1/ignition/transport.hh:9,
from igntest.c:1:
/usr/include/ignition/transport1/ignition/transport/RepHandler.hh:38:41: fatal 
error: google/protobuf/stubs/casts.h: No such file or directory
#include 
^


this file has been deleted in new protobuf I guess
(removing that line from the hh file works a little better)

that said, the second issue is:
pkg-config --cflags --libs ignition-transport1
-std=c++11 -I/usr/include/ignition/transport1 -lignition-transport1 -l1


that -l1 breaks the build, lets see:
./build 
/usr/bin/ld: cannot find -l1



g++ -o igntest igntest.c `pkg-config --cflags --libs ignition-transport1`
/usr/bin/ld: cannot find -l1
collect2: error: ld returned 1 exit status



removing it works:
g++ -o igntest igntest.c -std=c++11 -I/usr/include/ignition/transport1 
-lignition-transport1
./igntest
echo $?


As usual, please let me know if you have a fix or you need further details

thanks,
G.
--- End Message ---
--- Begin Message ---
Source: ignition-transport
Source-Version: 1.3.0-3

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

Debian distribution maintenance software
pp.
Jose Luis Rivero  (supplier of updated 
ignition-transport 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: Tue, 06 Sep 2016 21:22:27 +
Source: ignition-transport
Binary: libignition-transport1 libignition-transport-dev
Architecture: source
Version: 1.3.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jose Luis Rivero 
Description:
 libignition-transport-dev - Ignition Robotics transport Library - Development 
files
 libignition-transport1 - Ignition Robotics Transport Library - Shared library
Closes: 836384
Changes:
 ignition-transport (1.3.0-3) unstable; urgency=medium
 .
   * Added patch for pkgconfig file
(Closes: #836384)
Checksums-Sha1:
 ad51c8c4fc5fc314d58235cd970dcd9ba6b3e312 2026 ignition-transport_1.3.0-3.dsc
 e6aa6bf38cffde7ecd9a13ee0b115cb0131a7c0a 5856 
ignition-transport_1.3.0-3.debian.tar.xz
Checksums-Sha256:
 c26a5af1431dde2267eee8439126e88186fd5611727119e3f31aae1557409d1d 2026 
ignition-transport_1.3.0-3.dsc
 f04675d9322581875d1643d40b010ab8821825ceb76718dde8f93831437e2fed 5856 
ignition-transport_1.3.0-3.debian.tar.xz
Files:
 c82545c34494bf902c881fe5fdc5cccf 2026 science extra 
ignition-transport_1.3.0-3.dsc
 41614dc7aee170587c927d4fa6e9 5856 science extra 
ignition-transport_1.3.0-3.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCgAGBQJX0LdpAAoJEF6UbAkK/wQnJEEIAJ/JPQitgAjVvmV121ei86JJ
ZMBoafAM1FTnKaXOhyc/Jqe7OnhIalvqTnsaNpLOAJ94nn/aHWQuPRS9Do5pcTwG
d+ftbw6zR7uQxB3gE3c2PUhjaUjN3LEPFhs8ZrdNrtVXSIhm9PGVzlI/RJ3zVeWA
Mo27xkuK5awm6HBtoMvy/yDeL545cqKZnkGrFmH4ZvaOmw/dqU1IE+QGhneEVGj4
L07nSEaJh6ntdAO8kcLiJRBRcOfz85PZYMKjHYEF9xSuZOllQpB5QDnft37l+wj+
uHTGVCJqtkrCIvveDTN8Yfk9kqyg8hP5tGpea09P2gseN7K2HenFL18wnB/1Hh4=
=R2T8
-END PGP SIGNATURE End Message ---

Bug#836426: Caused by libgtk-3-0 3.21

[Michael Biebl]

On Wed, 7 Sep 2016 09:21:55 -0700 Josh Triplett 
wrote:
> Control: reassign -1 libgtk-3-0 3.21.5-3
> Control: affects -1 gnome-boxes
> Control: severity -1 serious
> Control: forcemerge -1 832077

To me those two issues look not like they are related.

After all, this one was file for 3.20, the other one for 3.21.

The severity seems overinflated as well.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#837013: notmuch: FTBFS: Tests failures

[David Bremner]

Lucas Nussbaum  writes:

> Source: notmuch
> Version: 0.22.1-3
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20160906 qa-ftbfs
> Justification: FTBFS on amd64
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
>
>
> The full build log is available from:
>
> http://people.debian.org/~lucas/logs/2016/09/06/notmuch_0.22.1-3_unstable.log

It doesn't seem to be there?

In any case I think I can reproduce at least some of the failures
locally; it seems to related to changes in the output of

gpg --no-tty --list-secret-keys --with-colons --fingerprint

introduced by gnupg 2.1.15

The failures I can reproduce are fixed by

diff --git a/test/T350-crypto.sh b/test/T350-crypto.sh
index 3656cce..5a63183 100755
--- a/test/T350-crypto.sh
+++ b/test/T350-crypto.sh
@@ -26,7 +26,7 @@ add_gnupg_home ()
 
 add_gnupg_home
 # get key fingerprint
-FINGERPRINT=$(gpg --no-tty --list-secret-keys --with-colons --fingerprint | 
grep '^fpr:' | cut -d: -f10)
+FINGERPRINT=$(gpg --no-tty --list-secret-keys --with-colons --fingerprint | 
grep '^fpr:' | cut -d: -f10 |head -1)
 
 test_expect_success 'emacs delivery of signed message' \
 'emacs_fcc_message \

I'll have to think about whether this is the most robust fix possible;
I'd like to avoid future breakage caused by gpg changing --with-colons
output.

Processed: severity of 815154 is important

[Debian Bug Tracking System]

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

> severity 815154 important
Bug #815154 [gnome-control-center] Removes XKBMODEL and XKBOPTIONS from 
/etc/default/keyboard
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Processed: NMU for lakai

[Debian Bug Tracking System]

Processing control commands:

> tags 817516 patch
Bug #817516 [src:lakai] lakai: Removal of debhelper compat 4
Ignoring request to alter tags of bug #817516 to the same tags previously set
> tags 817516 pending
Bug #817516 [src:lakai] lakai: Removal of debhelper compat 4
Ignoring request to alter tags of bug #817516 to the same tags previously set
> tags 835651 patch
Bug #835651 [lakai] lakai: Please, add a Homepage field and update the watch 
file
Ignoring request to alter tags of bug #835651 to the same tags previously set
> tags 835651 pending
Bug #835651 [lakai] lakai: Please, add a Homepage field and update the watch 
file
Ignoring request to alter tags of bug #835651 to the same tags previously set
> tags 449603 patch
Bug #449603 [lakai] lakai: watch file broken
Ignoring request to alter tags of bug #449603 to the same tags previously set
> tags 449603 pending
Bug #449603 [lakai] lakai: watch file broken
Ignoring request to alter tags of bug #449603 to the same tags previously set
> tags 450202 patch
Bug #450202 [lakai] lakai: debian/watch fails to report upstream's version
Ignoring request to alter tags of bug #450202 to the same tags previously set
> tags 450202 pending
Bug #450202 [lakai] lakai: debian/watch fails to report upstream's version
Ignoring request to alter tags of bug #450202 to the same tags previously set

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

Processed: NMU for lakai

[Debian Bug Tracking System]

Processing control commands:

> tags 817516 patch
Bug #817516 [src:lakai] lakai: Removal of debhelper compat 4
Ignoring request to alter tags of bug #817516 to the same tags previously set
> tags 817516 pending
Bug #817516 [src:lakai] lakai: Removal of debhelper compat 4
Ignoring request to alter tags of bug #817516 to the same tags previously set
> tags 835651 patch
Bug #835651 [lakai] lakai: Please, add a Homepage field and update the watch 
file
Ignoring request to alter tags of bug #835651 to the same tags previously set
> tags 835651 pending
Bug #835651 [lakai] lakai: Please, add a Homepage field and update the watch 
file
Ignoring request to alter tags of bug #835651 to the same tags previously set
> tags 449603 patch
Bug #449603 [lakai] lakai: watch file broken
Ignoring request to alter tags of bug #449603 to the same tags previously set
> tags 449603 pending
Bug #449603 [lakai] lakai: watch file broken
Ignoring request to alter tags of bug #449603 to the same tags previously set
> tags 450202 patch
Bug #450202 [lakai] lakai: debian/watch fails to report upstream's version
Ignoring request to alter tags of bug #450202 to the same tags previously set
> tags 450202 pending
Bug #450202 [lakai] lakai: debian/watch fails to report upstream's version
Ignoring request to alter tags of bug #450202 to the same tags previously set

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

Bug#817516: NMU for lakai

[Gustavo S. L.]

Control: tags 817516 patch
Control: tags 817516 pending
Control: tags 835651 patch
Control: tags 835651 pending
Control: tags 449603 patch
Control: tags 449603 pending
Control: tags 450202 patch
Control: tags 450202 pending

Hi

I uploaded a NMU to 10-day/delay queue. Feel free to cancel this
upload if needed.

The debian/changelog is:

lakai (0.1-1.1) unstable; urgency=medium

  * Non-maintainer upload.
  * debian/compat:
  - Update level to 9. (Closes: #817516)
  * debian/control:
  - Added Homepage. (Closes: #835651)
  - Bumped level debhelper to 9.
  - Bumped Standards-Version to 3.9.8.
  * debian/watch:
  - Update. (Closes: #449603, #450202).

I attached a debdiff.

Best regards,

Gustavo Soares de Lima


lakai.debdiff
Description: Binary data

Processed: NMU for lakai

[Debian Bug Tracking System]

Processing control commands:

> tags 817516 patch
Bug #817516 [src:lakai] lakai: Removal of debhelper compat 4
Ignoring request to alter tags of bug #817516 to the same tags previously set
> tags 817516 pending
Bug #817516 [src:lakai] lakai: Removal of debhelper compat 4
Ignoring request to alter tags of bug #817516 to the same tags previously set
> tags 835651 patch
Bug #835651 [lakai] lakai: Please, add a Homepage field and update the watch 
file
Ignoring request to alter tags of bug #835651 to the same tags previously set
> tags 835651 pending
Bug #835651 [lakai] lakai: Please, add a Homepage field and update the watch 
file
Ignoring request to alter tags of bug #835651 to the same tags previously set
> tags 449603 patch
Bug #449603 [lakai] lakai: watch file broken
Ignoring request to alter tags of bug #449603 to the same tags previously set
> tags 449603 pending
Bug #449603 [lakai] lakai: watch file broken
Ignoring request to alter tags of bug #449603 to the same tags previously set
> tags 450202 patch
Bug #450202 [lakai] lakai: debian/watch fails to report upstream's version
Ignoring request to alter tags of bug #450202 to the same tags previously set
> tags 450202 pending
Bug #450202 [lakai] lakai: debian/watch fails to report upstream's version
Ignoring request to alter tags of bug #450202 to the same tags previously set

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

Processed: NMU for lakai

[Debian Bug Tracking System]

Processing control commands:

> tags 817516 patch
Bug #817516 [src:lakai] lakai: Removal of debhelper compat 4
Added tag(s) patch.
> tags 817516 pending
Bug #817516 [src:lakai] lakai: Removal of debhelper compat 4
Added tag(s) pending.
> tags 835651 patch
Bug #835651 [lakai] lakai: Please, add a Homepage field and update the watch 
file
Ignoring request to alter tags of bug #835651 to the same tags previously set
> tags 835651 pending
Bug #835651 [lakai] lakai: Please, add a Homepage field and update the watch 
file
Added tag(s) pending.
> tags 449603 patch
Bug #449603 [lakai] lakai: watch file broken
Added tag(s) patch.
> tags 449603 pending
Bug #449603 [lakai] lakai: watch file broken
Added tag(s) pending.
> tags 450202 patch
Bug #450202 [lakai] lakai: debian/watch fails to report upstream's version
Added tag(s) patch.
> tags 450202 pending
Bug #450202 [lakai] lakai: debian/watch fails to report upstream's version
Added tag(s) pending.

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

Processed: gdk-pixbuf: FTBFS on most architectures due to test failures

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:wxwidgets3.0 src:grass src:qgis
Bug #837030 [src:gdk-pixbuf] gdk-pixbuf: FTBFS on most architectures due to 
test failures
Added indication that 837030 affects src:wxwidgets3.0, src:grass, and src:qgis

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

Bug#837030: gdk-pixbuf: FTBFS on most architectures due to test failures

[Bas Couwenberg]

Source: gdk-pixbuf
Version: 2.35.4-1
Severity: serious
Justification: makes the package in question unusable or mostly so
Control: affects -1 src:wxwidgets3.0 src:grass src:qgis

Dear Maintainer,

gdk-pixbuf (2.35.4-1) FTBFS on pretty much all architectures due to test
failures:

 ERROR: pixbuf-composite
 ===
 
 **
 
GLib:ERROR:/build/glib2.0-E8y2Xu/glib2.0-2.49.6/./glib/gtestutils.c:3361:g_test_build_filename_va:
 assertion failed (num_path_segments < G_N_ELEMENTS (pathv)): (16 < 16)
 Aborted
 # random seed: R02Sc22c9ad260066d3d905a7b2bba549525
 1..2
 # Start of pixbuf tests
 ok 1 /pixbuf/composite1
 PASS: pixbuf-composite 1 /pixbuf/composite1
 # 
GLib:ERROR:/build/glib2.0-E8y2Xu/glib2.0-2.49.6/./glib/gtestutils.c:3361:g_test_build_filename_va:
 # assertion failed (num_path_segments < G_N_ELEMENTS (pathv)): (16 < 16)
 ERROR: pixbuf-composite - too few tests run (expected 2, got 1)
 ERROR: pixbuf-composite - exited with status 134 (terminated by signal 6?)

This subsequently causes uninstallable build dependencies of its reverse
dependencies.

Kind Regards,

Bas

Bug#837003: glib2.0: FTBFS: tests failures

[Simon McVittie]

On Wed, 07 Sep 2016 at 23:56:44 +0200, Lucas Nussbaum wrote:
> > # 
> > GLib:ERROR:/<>/./glib/tests/gdatetime.c:221:test_GDateTime_equal:
> >  assertion failed (g_date_time_get_utc_offset (dt1) / G_USEC_PER_SEC == (-3 
> > * 3600)): (0 == -10800)

This appears to be the only failure here.

Does your test system perhaps not have tzdata installed, despite it being
Priority: required? I know that doesn't technically make it
build-essential - only a dependency from build-essential or Essential: yes
would do that - so if glib2.0 needs it for tests it should build-depend
on it, but in practice I suspect the official buildds all have it, which
would explain why we haven't seen this fail before.

> The full build log is available from:
>
> http://people.debian.org/~lucas/logs/2016/09/06/glib2.0_2.49.6-1_unstable.log

The requested URL /~lucas/logs/2016/09/06/glib2.0_2.49.6-1_unstable.log
was not found on this server.

S

Bug#837000: kerberos-configs: FTBFS: Undefined subroutine ::read_config called at ./genblob line 9.

[Sam Hartman]

> "Lucas" == Lucas Nussbaum  writes:

Lucas> Hi,

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

Lucas> Relevant part (hopefully):
>> fakeroot debian/rules binary ./genblob >tmp & tmp config-blob
>> Undefined subroutine ::read_config called at ./genblob line
>> 9.  debian/rules:17: recipe for target 'config-blob' failed make:
>> *** [config-blob] Error 2

Lucas> The full build log is available from:
Lucas> 
http://people.debian.org/~lucas/logs/2016/09/06/kerberos-configs_2.3_unstable.log

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

Lucas> About the archive rebuild: The rebuild was done on EC2 VM
Lucas> instances from Amazon Web Services, using a clean, minimal
Lucas> and up-to-date chroot. Every failed build was retried once to
Lucas> eliminate random failures.

Looks like a . removed from cwd bug in perl.
Kerberos-configs is a bit over-due for some love anyway.
The fix is easy, but I'll go fold in a bunch of other bugs while I get
to it.


--Sam

Bug#837006: gnome-python-desktop: FTBFS: /usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved from binary package "stamp-autotools". Stop.

[Michael Biebl]

Hi Lucas,

thanks for your bug report

Am 07.09.2016 um 23:57 schrieb Lucas Nussbaum:
>> touch debian/stamp-autotools-files
>> /usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation 
>> resolved from binary package "stamp-autotools".  Stop.

That looks like (yet another) cdbs regression and should probably be
re-assigned (along with #837024)

Regards,
Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#837017: libvisio: FTBFS: Tests failures

[Debian Bug Tracking System]

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

> tag 837017 + moreinfo
Bug #837017 [src:libvisio] libvisio: FTBFS: Tests failures
Added tag(s) moreinfo.
> tag 837017 + unreproducible
Bug #837017 [src:libvisio] libvisio: FTBFS: Tests failures
Added tag(s) unreproducible.
> thanks
Stopping processing here.

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

Bug#837017: libvisio: FTBFS: Tests failures

[Rene Engelhard]

tag 837017 + moreinfo
tag 837017 + unreproducible
thanks

Hi,

On Thu, Sep 08, 2016 at 12:16:24AM +0200, Lucas Nussbaum wrote:
> Relevant part (hopefully):
> > make[6]: *** [test-suite.log] Error 1
> > make[6]: Leaving directory '/<>/src/test'
> > Makefile:892: recipe for target 'check-TESTS' failed
> > make[5]: *** [check-TESTS] Error 2
> > make[5]: Leaving directory '/<>/src/test'
> > Makefile:965: recipe for target 'check-am' failed
> > make[4]: *** [check-am] Error 2
> > make[4]: Leaving directory '/<>/src/test'
> > Makefile:394: recipe for target 'check-recursive' failed
> > make[3]: *** [check-recursive] Error 1
> > make[3]: Leaving directory '/<>/src'
> > Makefile:501: recipe for target 'check-recursive' failed
> > make[2]: *** [check-recursive] Error 1
> > make[2]: Leaving directory '/<>'
> > dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2
> > debian/rules:14: recipe for target 'override_dh_auto_test' failed

Nope.

> The full build log is available from:
>
> http://people.debian.org/~lucas/logs/2016/09/06/libvisio_0.1.5-1_unstable.log

404

And a apt-get -b source libvisio works fine here.

Regards,

Rene

Bug#837027: csh: FTBFS: proc.c:84:16: error: storage size of 'w' isn't known

[Lucas Nussbaum]

Source: csh
Version: 20110502-2.1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> cc -g -O2 -Wno-error -I/<> -I. -DBUILTIN -DFILEC -DNLS 
> -DSHORT_STRINGS -D_GNU_SOURCE  -Werror   -c proc.c
> proc.c: In function 'pchild':
> proc.c:84:16: error: storage size of 'w' isn't known
>  union wait w;
> ^
> *** Error code 1
> 
> Stop.
> bmake[2]: stopped in /<>
> dh_auto_build: bmake returned exit code 1
> debian/rules:10: recipe for target 'override_dh_auto_build' failed
> make[1]: *** [override_dh_auto_build] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/09/06/csh_20110502-2.1_unstable.log

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

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

Bug#837028: gauche-gtk: FTBFS: pango-font.c:249:44: error: 'desc' undeclared (first use in this function)

[Lucas Nussbaum]

Source: gauche-gtk
Version: 0.6~pre1+git20121223-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -g -O2 
> -fdebug-prefix-map=/<>/gauche-gtk-0.6~pre1+git20121223=. 
> -fstack-protector-strong -Wformat -Werror=format-security -I. `gauche-config 
> -I` `gauche-config --so-cflags` `pkg-config --cflags gtk+-2.0` -Wdate-time 
> -D_FORTIFY_SOURCE=2  -c -o pango-font.o pango-font.c
> pango-font.c: In function 'pango_font_pango_font_description_to_string':
> pango-font.c:249:44: error: 'desc' undeclared (first use in this function)
>  char *s = pango_font_description_to_string(desc);
> ^~~~
> pango-font.c:249:44: note: each undeclared identifier is reported only once 
> for each function it appears in
> pango-font.c: In function 'pango_font_pango_font_description_to_filename':
> pango-font.c:267:46: error: 'desc' undeclared (first use in this function)
>  char *s = pango_font_description_to_filename(desc);
>   ^~~~
> : recipe for target 'pango-font.o' failed
> make[2]: *** [pango-font.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/09/06/gauche-gtk_0.6~pre1+git20121223-1_unstable.log

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

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

Bug#837025: pyasn1: FTBFS: debian/rules:16: *** target file 'debian/python-module-stampdir/pypy-pyasn1' has both : and :: entries. Stop.

[Lucas Nussbaum]

Source: pyasn1
Version: 0.1.9-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  fakeroot debian/rules clean
> py3versions: no X-Python3-Version in control file, using supported versions
> debian/rules:16: *** target file 'debian/python-module-stampdir/pypy-pyasn1' 
> has both : and :: entries.  Stop.
> dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2
> 
> Build finished at 2016-09-06T23:08:12Z

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/09/06/pyasn1_0.1.9-1_unstable.log

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

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

Processed: affects 832077

[Debian Bug Tracking System]

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

> affects 832077 vim-gtk3
Bug #832077 [libgtk-3-0] Gtk-WARNING **: EmacsFixed 0x95c12e8 is drawn without 
a current allocation. This should not happen.
Bug #836426 [libgtk-3-0] Graphics rendering (with QXL graphics) doesn't update
Added indication that 832077 affects vim-gtk3
Added indication that 836426 affects vim-gtk3
> thanks
Stopping processing here.

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

Processed: Re: Bug#834744: xmlgraphics-commons: FTBFS (missing build-depends on gnupg)

[Debian Bug Tracking System]

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

> severity 834744 serious
Bug #834744 [src:xmlgraphics-commons] xmlgraphics-commons: FTBFS (missing 
build-depends on gnupg)
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#835489: Fails to start

[Dmitry Eremin-Solenikov]

Package: pyqso
Followup-For: Bug #835489

Please consider the attached patch that fixed all the issues of PyQSO vs
Python3. I have uploaded the corresponding package to
mentors.debian.net (https://mentors.debian.net/package/pyqso). Thanks in 
advance.

-- 
With best wishes
Dmitry

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

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

Versions of packages pyqso depends on:
ii  gir1.2-gtk-3.0   3.21.5-3
ii  libjs-jquery 1.12.4-1
ii  libjs-underscore 1.8.3~dfsg-1
ii  python-libhamlib23.0.1-1
ii  python3-gi-cairo 3.20.1-1
ii  python3-matplotlib   1.5.2~rc2-1
ii  python3-mpltoolkits.basemap  1.0.7+dfsg-4
ii  python3-numpy1:1.11.1~rc1-1
pn  python3:any  

pyqso recommends no packages.

pyqso suggests no packages.

-- no debconf information
diff -Napur pyqso-0.3-old/debian/changelog pyqso-0.3/debian/changelog
--- pyqso-0.3-old/debian/changelog	2016-07-08 04:55:53.0 +0300
+++ pyqso-0.3/debian/changelog	2016-09-08 01:01:19.026455214 +0300
@@ -1,3 +1,14 @@
+pyqso (0.3-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Rebuild with Python3 (Closes: #835489).
+  * Change packages in dependencies to rerefence Python3 packages.
+  * Move python(3)-libhamlib2 to Recomends, as the Python3 version of package
+is not yet available in Debian.
+  * Bump standards version to 3.9.8 (No changes needed).
+
+ -- Dmitry Eremin-Solenikov   Thu, 08 Sep 2016 01:00:46 +0300
+
 pyqso (0.3-1) unstable; urgency=medium
 
   * Imported Upstream version 0.3.
diff -Napur pyqso-0.3-old/debian/control pyqso-0.3/debian/control
--- pyqso-0.3-old/debian/control	2016-07-08 04:51:02.0 +0300
+++ pyqso-0.3/debian/control	2016-09-08 01:01:46.095566806 +0300
@@ -5,10 +5,10 @@ Section: hamradio
 Priority: optional
 Build-Depends: debhelper (>= 9),
dh-python,
-   python-all,
+   python3-all,
python-setuptools,
python-sphinx
-Standards-Version: 3.9.6
+Standards-Version: 3.9.8
 Vcs-Browser: http://anonscm.debian.org/cgit/pkg-hamradio/pyqso.git
 Vcs-Git: http://anonscm.debian.org/git/pkg-hamradio/pyqso.git
 Homepage: http://christianjacobs.uk/pyqso
@@ -16,15 +16,15 @@ Homepage: http://christianjacobs.uk/pyqs
 Package: pyqso
 Architecture: all
 Depends: ${misc:Depends},
- ${python:Depends},
- python-libhamlib2,
+ ${python3:Depends},
  gir1.2-gtk-3.0,
- python-gi-cairo,
- python-mpltoolkits.basemap,
- python-numpy,
- python-matplotlib,
+ python3-gi-cairo,
+ python3-mpltoolkits.basemap,
+ python3-numpy,
+ python3-matplotlib,
  libjs-jquery,
  libjs-underscore
+Recommends: python3-libhamlib2,
 Description: logging tool for amateur radio operators
  PyQSO is a logging tool for amateur radio operators. It provides a simple
  graphical interface through which users can manage information about the
diff -Napur pyqso-0.3-old/debian/rules pyqso-0.3/debian/rules
--- pyqso-0.3-old/debian/rules	2016-07-08 04:51:02.0 +0300
+++ pyqso-0.3/debian/rules	2016-09-08 00:38:38.589181137 +0300
@@ -2,7 +2,7 @@
 export PYBUILD_NAME=pyqso
 
 %:
-	dh $@ --with python2 --buildsystem=pybuild
+	dh $@ --with python3 --buildsystem=pybuild
 
 override_dh_auto_build:
 	PYTHONPATH=. http_proxy='localhost' sphinx-build -N -bhtml docs/source/ build/html  # HTML generator

Bug#837015: linux-tools: FTBFS: util/event.c:448:2: error: 'readdir_r' is deprecated [-Werror=deprecated-declarations]

[Lucas Nussbaum]

Source: linux-tools
Version: 4.4.6-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>   gcc 
> -Wp,-MD,/<>/debian/build/tools/perf/out/util/.event.o.d,-MT,/<>/debian/build/tools/perf/out/util/event.o
>  -g -O2 -fdebug-prefix-map=/<>/debian/build/tools/perf=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wdate-time 
> -D_FORTIFY_SOURCE=2 -I/<>/tools/perf 
> -I/<>/debian/build/tools/perf -isystem 
> /<>/debian/build/include -Wno-error -DHAVE_ARCH_X86_64_SUPPORT 
> -DHAVE_PERF_REGS_SUPPORT -DHAVE_ARCH_REGS_QUERY_REGISTER_OFFSET -Werror -O6 
> -fno-omit-frame-pointer -ggdb3 -funwind-tables -Wall -Wextra -std=gnu99 
> -fstack-protector-all -D_FORTIFY_SOURCE=2 
> -I/<>/tools/perf/util/include 
> -I/<>/tools/perf/arch/x86/include 
> -I/<>/tools/include/ -I/<>/arch/x86/include/uapi 
> -I/<>/arch/x86/include -I/<>/include/uapi 
> -I/<>/include 
> -I/<>/debian/build/tools/perf/out//util 
> -I/<>/debian/build/tools/perf/out/ 
> -I/<>/tools/perf/util -I/<>/tools/perf 
> -I/<>/tools/lib/ -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 
> -D_GNU_SOURCE -DHAVE_SYNC_COMPARE_AND_SWAP_SUPPORT 
> -DHAVE_PTHREAD_ATTR_SETAFFINITY_NP -DHAVE_LIBELF_SUPPORT 
> -DHAVE_LIBELF_MMAP_SUPPORT -DHAVE_ELF_GETPHDRNUM_SUPPORT -DHAVE_DWARF_SUPPORT 
>  -DHAVE_LIBBPF_SUPPORT -DHAVE_DWARF_UNWIND_SUPPORT -DNO_LIBUNWIND_DEBUG_FRAME 
> -DHAVE_LIBUNWIND_SUPPORT  -DHAVE_LIBAUDIT_SUPPORT -I/usr/include/slang 
> -DHAVE_SLANG_SUPPORT -DHAVE_TIMERFD_SUPPORT -DHAVE_CPLUS_DEMANGLE_SUPPORT 
> -DHAVE_ZLIB_SUPPORT -DHAVE_BACKTRACE_SUPPORT -DHAVE_LIBNUMA_SUPPORT 
> -DHAVE_KVM_STAT_SUPPORT -DHAVE_PERF_READ_VDSO32 -DHAVE_PERF_READ_VDSOX32 
> -DHAVE_AUXTRACE_SUPPORT -I/<>/debian/build/tools/perf/out/ 
> -D"BUILD_STR(s)=#s"   -c -o 
> /<>/debian/build/tools/perf/out/util/event.o util/event.c
> util/event.c: In function '__event__synthesize_thread':
> util/event.c:448:2: error: 'readdir_r' is deprecated 
> [-Werror=deprecated-declarations]
>   while (!readdir_r(tasks, , ) && next) {
>   ^
> In file included from /usr/include/features.h:364:0,
>  from /usr/include/stdint.h:25,
>  from /usr/lib/gcc/x86_64-linux-gnu/6/include/stdint.h:9,
>  from /<>/tools/include/linux/types.h:6,
>  from util/event.c:1:
> /usr/include/dirent.h:189:12: note: declared here
>  extern int __REDIRECT (readdir_r,
> ^
> util/event.c: In function 'perf_event__synthesize_threads':
> util/event.c:586:2: error: 'readdir_r' is deprecated 
> [-Werror=deprecated-declarations]
>   while (!readdir_r(proc, , ) && next) {
>   ^
> In file included from /usr/include/features.h:364:0,
>  from /usr/include/stdint.h:25,
>  from /usr/lib/gcc/x86_64-linux-gnu/6/include/stdint.h:9,
>  from /<>/tools/include/linux/types.h:6,
>  from util/event.c:1:
> /usr/include/dirent.h:189:12: note: declared here
>  extern int __REDIRECT (readdir_r,
> ^
> cc1: all warnings being treated as errors
> mv: cannot stat 
> '/<>/debian/build/tools/perf/out/util/.event.o.tmp': No such 
> file or directory
> /<>/tools/build/Makefile.build:77: recipe for target 
> '/<>/debian/build/tools/perf/out/util/event.o' failed
> make[8]: *** [/<>/debian/build/tools/perf/out/util/event.o] 
> Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/09/06/linux-tools_4.4.6-1_unstable.log

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

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

Bug#837023: gridengine: FTBFS: ../sh.proc.c:153:16: error: storage size of ‘w’ isn’t known

[Lucas Nussbaum]

Source: gridengine
Version: 8.1.9+dfsg-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> cc -c -O2 -Wstrict-prototypes -DLINUX -DLINUXAMD64 -DLINUXAMD64 -D_GNU_SOURCE 
> -DGETHOSTBYNAME_R6 -DGETHOSTBYADDR_R8 -DTARGET_64BIT -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 
> -fdebug-prefix-map=/<>/gridengine-8.1.9+dfsg=. 
> -fstack-protector-strong -Wformat -Werror=format-security -DSGE_PQS_API 
> -DSPOOLING_dynamic -DSECURE -DHAVE_HWLOC=1 -DCOMPILE_DC 
> -D__SGE_COMPILE_WITH_GETTEXT__ -D__SGE_NO_USERMAPPING__ -U_GNU_SOURCE 
> -Wno-error -DPROG_NAME='"qtcsh"' -DLINUXAMD64 -I. -I.. 
> -D_PATH_TCSHELL='"/usr/local/bin/tcsh"'  -Wdate-time -D_FORTIFY_SOURCE=2  
> -I../../../libs/gdi -I../../../libs/gdi ../sh.proc.c
> In file included from /usr/include/signal.h:28:0,
>  from ../sh.h:39,
>  from ../sh.proc.c:33:
> /usr/include/features.h:148:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>  # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE"
>^~~
> ../sh.proc.c: In function ‘pchild’:
> ../sh.proc.c:153:16: error: storage size of ‘w’ isn’t known
>  union wait w;
> ^
> Makefile:381: recipe for target 'sh.proc.o' failed
> make[2]: *** [sh.proc.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/09/06/gridengine_8.1.9+dfsg-1_unstable.log

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

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

Bug#837021: openjfx: FTBFS: PosixPlatform.cpp:235:10: error: 'wait' was not declared in this scope

[Lucas Nussbaum]

Source: openjfx
Version: 8u102-b14-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> g++ -Xlinker -s -static-libstdc++ -Wl,-O1 -shared -o libDumpRenderTreeJava.so 
> Release/obj/GCController.o Release/obj/TestRunner.o Release/obj/WorkQueue.o 
> Release/obj/DumpRenderTree.o Release/obj/GCControllerJava.o 
> Release/obj/JavaEnv.o Release/obj/TestRunnerJava.o 
> Release/obj/WorkQueueItemJava.o Release/obj/EventSender.o  
> -L../../Release/lib -lpthread -ljfxwebkit  
> mv -f libDumpRenderTreeJava.so ../../Release/lib/ 
> make[3]: Leaving directory 
> '/<>/modules/web/build/linux/Tools/DumpRenderTree'
> make[2]: Leaving directory '/<>/modules/web/build/linux/Release'
> 
> 
>  WebKit is now built (1h:03m:38s). 
>  To run FXLauncher with this newly-built code, use the
>  "Tools/Scripts/run-launcher" script.
> 
> :web:compileNativeLinux (Thread[main,5,main]) completed. Took 1 hrs 3 mins 
> 38.269 secs.
> :web:compileGeneratedLinux (Thread[main,5,main]) started.
> :web:compileGeneratedLinux
> Executing task ':web:compileGeneratedLinux' (up-to-date check took 0.075 
> secs) due to:
>   No history is available.
> All input files are considered out-of-date for incremental task 
> ':web:compileGeneratedLinux'.
> Compiling with Java command line compiler 
> '/usr/lib/jvm/java-8-openjdk-amd64/bin/javac'.
> Starting process 'command '/usr/lib/jvm/java-8-openjdk-amd64/bin/javac''. 
> Working directory: /<>/modules/web Command: 
> /usr/lib/jvm/java-8-openjdk-amd64/bin/javac 
> @/<>/modules/web/build/tmp/compileGeneratedLinux/java-compiler-args.txt
> Successfully started process 'command 
> '/usr/lib/jvm/java-8-openjdk-amd64/bin/javac''
> Note: Some input files use unchecked or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details.
> :web:compileGeneratedLinux (Thread[main,5,main]) completed. Took 3.056 secs.
> :web:compileGenerated (Thread[main,5,main]) started.
> :web:compileGenerated
> Skipping task ':web:compileGenerated' as it has no actions.
> :web:compileGenerated (Thread[main,5,main]) completed. Took 0.0 secs.
> :web:drtJar (Thread[main,5,main]) started.
> :web:drtJar
> Executing task ':web:drtJar' (up-to-date check took 0.007 secs) due to:
>   No history is available.
> :web:drtJar (Thread[main,5,main]) completed. Took 0.028 secs.
> :web:jar (Thread[main,5,main]) started.
> :web:jar
> Executing task ':web:jar' (up-to-date check took 0.02 secs) due to:
>   No history is available.
> :web:jar (Thread[main,5,main]) completed. Took 0.166 secs.
> :builders:compileJava (Thread[main,5,main]) started.
> :builders:compileJava
> Executing task ':builders:compileJava' (up-to-date check took 0.046 secs) due 
> to:
>   No history is available.
> All input files are considered out-of-date for incremental task 
> ':builders:compileJava'.
> Compiling with Java command line compiler 
> '/usr/lib/jvm/java-8-openjdk-amd64/bin/javac'.
> Starting process 'command '/usr/lib/jvm/java-8-openjdk-amd64/bin/javac''. 
> Working directory: /<>/modules/builders Command: 
> /usr/lib/jvm/java-8-openjdk-amd64/bin/javac 
> @/<>/modules/builders/build/tmp/compileJava/java-compiler-args.txt
> Successfully started process 'command 
> '/usr/lib/jvm/java-8-openjdk-amd64/bin/javac''
> Note: 
> /<>/modules/builders/src/main/java/javafx/scene/web/WebViewBuilder.java
>  uses or overrides a deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> Note: Some input files use unchecked or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details.
> :builders:compileJava (Thread[main,5,main]) completed. Took 3.794 secs.
> :builders:processResources (Thread[main,5,main]) started.
> :builders:processResources
> file or directory '/<>/modules/builders/src/main/resources', not 
> found
> Skipping task ':builders:processResources' as it has no source files.
> :builders:processResources UP-TO-DATE
> :builders:processResources (Thread[main,5,main]) completed. Took 0.001 secs.
> :builders:classes (Thread[main,5,main]) started.
> :builders:classes
> Skipping task ':builders:classes' as it has no actions.
> :builders:classes (Thread[main,5,main]) completed. Took 0.0 secs.
> :builders:jar (Thread[main,5,main]) started.
> :builders:jar
> Executing task ':builders:jar' (up-to-date check took 0.003 secs) due to:
>   No history is available.
> :builders:jar (Thread[main,5,main]) completed. Took 0.053 secs.
> :builders:assemble (Thread[main,5,main]) started.
> :builders:assemble
> Skipping task ':builders:assemble' as it has no actions.
> :builders:assemble (Thread[main,5,main]) completed. Took 0.0 secs.
> :controls:assemble (Thread[main,5,main]) started.
> :controls:assemble
> Skipping task 

Bug#837016: singular: FTBFS: aminclude.am:35: error: DX_COND_doc does not appear in AM_CONDITIONAL

[Lucas Nussbaum]

Source: singular
Version: 4.0.3-p1+ds-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --with autoreconf --parallel
>dh_testdir
>dh_update_autotools_config
>dh_autoreconf
> libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, '../build-aux'.
> libtoolize: copying file '../build-aux/ltmain.sh'
> libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, '../m4'.
> libtoolize: copying file '../m4/libtool.m4'
> libtoolize: copying file '../m4/ltoptions.m4'
> libtoolize: copying file '../m4/ltsugar.m4'
> libtoolize: copying file '../m4/ltversion.m4'
> libtoolize: copying file '../m4/lt~obsolete.m4'
> configure.ac:11: installing '../build-aux/ar-lib'
> configure.ac:11: installing '../build-aux/compile'
> configure.ac:41: installing '../build-aux/config.guess'
> configure.ac:41: installing '../build-aux/config.sub'
> configure.ac:9: installing '../build-aux/install-sh'
> configure.ac:9: installing '../build-aux/missing'
> Makefile.am: installing '../build-aux/depcomp'
> libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, '../build-aux'.
> libtoolize: copying file '../build-aux/ltmain.sh'
> libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, '../m4'.
> libtoolize: copying file '../m4/libtool.m4'
> libtoolize: copying file '../m4/ltoptions.m4'
> libtoolize: copying file '../m4/ltsugar.m4'
> libtoolize: copying file '../m4/ltversion.m4'
> libtoolize: copying file '../m4/lt~obsolete.m4'
> configure.ac:15: installing '../build-aux/compile'
> configure.ac:21: installing '../build-aux/missing'
> Makefile.am:93: warning: EXTRA_DIST multiply defined in condition TRUE ...
> Makefile.am:28: ... 'EXTRA_DIST' previously defined here
> Makefile.am: installing '../build-aux/depcomp'
> parallel-tests: installing '../build-aux/test-driver'
> libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, '../build-aux'.
> libtoolize: copying file '../build-aux/ltmain.sh'
> libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, '../m4'.
> libtoolize: copying file '../m4/libtool.m4'
> libtoolize: copying file '../m4/ltoptions.m4'
> libtoolize: copying file '../m4/ltsugar.m4'
> libtoolize: copying file '../m4/ltversion.m4'
> libtoolize: copying file '../m4/lt~obsolete.m4'
> configure.ac:23: installing '../build-aux/compile'
> configure.ac:21: installing '../build-aux/missing'
> aminclude.am:35: error: DX_COND_doc does not appear in AM_CONDITIONAL
> Makefile.am:181:   'aminclude.am' included from here
> aminclude.am:41: error: DX_COND_html does not appear in AM_CONDITIONAL
> Makefile.am:181:   'aminclude.am' included from here
> aminclude.am:51: error: DX_COND_chm does not appear in AM_CONDITIONAL
> Makefile.am:181:   'aminclude.am' included from here
> aminclude.am:55: error: DX_COND_chi does not appear in AM_CONDITIONAL
> Makefile.am:181:   'aminclude.am' included from here
> aminclude.am:67: error: DX_COND_man does not appear in AM_CONDITIONAL
> Makefile.am:181:   'aminclude.am' included from here
> aminclude.am:77: error: DX_COND_rtf does not appear in AM_CONDITIONAL
> Makefile.am:181:   'aminclude.am' included from here
> aminclude.am:87: error: DX_COND_xml does not appear in AM_CONDITIONAL
> Makefile.am:181:   'aminclude.am' included from here
> aminclude.am:97: error: DX_COND_ps does not appear in AM_CONDITIONAL
> Makefile.am:181:   'aminclude.am' included from here
> aminclude.am:126: error: DX_COND_pdf does not appear in AM_CONDITIONAL
> Makefile.am:181:   'aminclude.am' included from here
> aminclude.am:155: error: DX_COND_latex does not appear in AM_CONDITIONAL
> Makefile.am:181:   'aminclude.am' included from here
> Makefile.am: installing '../build-aux/depcomp'
> configure.ac: installing '../build-aux/ylwrap'
> autoreconf: automake failed with exit status: 1
> dh_autoreconf: autoreconf -f -i returned exit code 1
> debian/rules:14: recipe for target 'build' failed
> make: *** [build] Error 2

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/09/06/singular_4.0.3-p1+ds-3_unstable.log

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

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

Bug#837026: tcsh: FTBFS: sh.proc.c:155:16: error: storage size of 'w' isn't known

[Lucas Nussbaum]

Source: tcsh
Version: 6.18.01-5
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> gcc -c -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -D_FILE_OFFSET_BITS=64 -I. -I. 
> -D_PATH_TCSHELL='"/usr/bin/tcsh"'  -Wdate-time -D_FORTIFY_SOURCE=2  sh.proc.c
> In file included from /usr/include/signal.h:28:0,
>  from sh.h:39,
>  from sh.proc.c:33:
> /usr/include/features.h:148:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>  # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE"
>^~~
> sh.proc.c: In function 'pchild':
> sh.proc.c:155:16: error: storage size of 'w' isn't known
>  union wait w;
> ^
> Makefile:465: recipe for target 'sh.proc.o' failed
> make[2]: *** [sh.proc.o] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/09/06/tcsh_6.18.01-5_unstable.log

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

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

Bug#837018: gupnp-igd: FTBFS: /usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved from binary package "stamp-autotools". Stop.

[Lucas Nussbaum]

Source: gupnp-igd
Version: 0.2.4-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> CDBS WARNING:  copyright-check disabled - touch debian/copyright_hints to 
> enable.
> test -x debian/rules
> mkdir -p "debian/build"
> 
> Scanning upstream source for new/changed copyright notices...
> 
> set -e; LC_ALL=C.UTF-8 /usr/bin/licensecheck --check '.*' --recursive 
> --copyright --deb-fmt --ignore 
> '^(debian/(changelog|copyright(|_hints|_newhints)))$' --lines 0 * | 
> /usr/lib/cdbs/licensecheck2dep5 > debian/copyright_newhints
> /bin/sh: 1: /usr/bin/licensecheck: not found
> 0 combinations of copyright and licensing found.
> diff: debian/copyright_hints: No such file or directory
> No new copyright notices found - assuming no news is good news...
> touch debian/stamp-copyright-check
> touch debian/stamp-upstream-cruft
> set -e;   mv ./config.guess ./config.guess.cdbs-orig; cp --remove-destination 
> /usr/share/misc/config.guess ./config.guess;
> set -e;   mv ./config.sub ./config.sub.cdbs-orig; cp --remove-destination 
> /usr/share/misc/config.sub ./config.sub;
> dh_autoreconf 
> libtoolize: putting auxiliary files in '.'.
> libtoolize: copying file './ltmain.sh'
> libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
> libtoolize: copying file 'm4/libtool.m4'
> libtoolize: copying file 'm4/ltoptions.m4'
> libtoolize: copying file 'm4/ltsugar.m4'
> libtoolize: copying file 'm4/ltversion.m4'
> libtoolize: copying file 'm4/lt~obsolete.m4'
> configure.ac:8: installing './compile'
> configure.ac:3: installing './missing'
> libgupnp-igd/Makefile.am: installing './depcomp'
> touch debian/stamp-autotools-files
> /usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation 
> resolved from binary package "stamp-autotools".  Stop.
> dpkg-buildpackage: error: debian/rules build gave error exit status 2
> 
> Build finished at 2016-09-06T22:51:00Z

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/09/06/gupnp-igd_0.2.4-1_unstable.log

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

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

Bug#837024: gamin: FTBFS: /usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved from binary package "stamp-autotools". Stop.

[Lucas Nussbaum]

Source: gamin
Version: 0.1.10-5
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> pyversions: missing X(S)-Python-Version in control file, fall back to 
> debian/pyversions
> pyversions: missing debian/pyversions file, fall back to supported versions
> CDBS WARNING:  copyright-check disabled - touch debian/copyright_hints to 
> enable.
> test -x debian/rules
> mkdir -p "debian/build"
> CDBS WARNING:DEB_DH_BUILDDEB_ARGS is deprecated since 0.4.85
> 
> Scanning upstream source for new/changed copyright notices...
> 
> set -e; LC_ALL=C.UTF-8 /usr/bin/licensecheck --check '.*' --recursive 
> --copyright --deb-fmt --ignore 
> '^(debian/(changelog|copyright(|_hints|_newhints)))$' --lines 0 * | 
> /usr/lib/cdbs/licensecheck2dep5 > debian/copyright_newhints
> /bin/sh: 1: /usr/bin/licensecheck: not found
> 0 combinations of copyright and licensing found.
> diff: debian/copyright_hints: No such file or directory
> No new copyright notices found - assuming no news is good news...
> touch debian/stamp-copyright-check
> touch debian/stamp-upstream-cruft
> set -e;   mv ./config.guess ./config.guess.cdbs-orig; cp --remove-destination 
> /usr/share/misc/config.guess ./config.guess;
> set -e;   mv ./config.sub ./config.sub.cdbs-orig; cp --remove-destination 
> /usr/share/misc/config.sub ./config.sub;
> dh_autoreconf 
> aclocal: warning: autoconf input should be named 'configure.ac', not 
> 'configure.in'
> configure.in:32: warning: AC_COMPILE_IFELSE was called before 
> AC_USE_SYSTEM_EXTENSIONS
> ../../lib/autoconf/specific.m4:368: AC_USE_SYSTEM_EXTENSIONS is expanded 
> from...
> configure.in:32: the top level
> configure.in:32: warning: AC_RUN_IFELSE was called before 
> AC_USE_SYSTEM_EXTENSIONS
> ../../lib/autoconf/specific.m4:368: AC_USE_SYSTEM_EXTENSIONS is expanded 
> from...
> configure.in:32: the top level
> configure.in:32: warning: AC_COMPILE_IFELSE was called before 
> AC_USE_SYSTEM_EXTENSIONS
> ../../lib/autoconf/specific.m4:368: AC_USE_SYSTEM_EXTENSIONS is expanded 
> from...
> configure.in:32: the top level
> configure.in:32: warning: AC_RUN_IFELSE was called before 
> AC_USE_SYSTEM_EXTENSIONS
> ../../lib/autoconf/specific.m4:368: AC_USE_SYSTEM_EXTENSIONS is expanded 
> from...
> configure.in:32: the top level
> libtoolize: putting auxiliary files in '.'.
> libtoolize: copying file './ltmain.sh'
> libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.in,
> libtoolize: and rerunning libtoolize and aclocal.
> libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
> aclocal: warning: autoconf input should be named 'configure.ac', not 
> 'configure.in'
> configure.in:32: warning: AC_COMPILE_IFELSE was called before 
> AC_USE_SYSTEM_EXTENSIONS
> ../../lib/autoconf/specific.m4:368: AC_USE_SYSTEM_EXTENSIONS is expanded 
> from...
> configure.in:32: the top level
> configure.in:32: warning: AC_RUN_IFELSE was called before 
> AC_USE_SYSTEM_EXTENSIONS
> ../../lib/autoconf/specific.m4:368: AC_USE_SYSTEM_EXTENSIONS is expanded 
> from...
> configure.in:32: the top level
> configure.in:32: warning: AC_COMPILE_IFELSE was called before 
> AC_USE_SYSTEM_EXTENSIONS
> ../../lib/autoconf/specific.m4:368: AC_USE_SYSTEM_EXTENSIONS is expanded 
> from...
> configure.in:32: the top level
> configure.in:32: warning: AC_RUN_IFELSE was called before 
> AC_USE_SYSTEM_EXTENSIONS
> ../../lib/autoconf/specific.m4:368: AC_USE_SYSTEM_EXTENSIONS is expanded 
> from...
> configure.in:32: the top level
> configure.in:32: warning: AC_COMPILE_IFELSE was called before 
> AC_USE_SYSTEM_EXTENSIONS
> ../../lib/autoconf/specific.m4:368: AC_USE_SYSTEM_EXTENSIONS is expanded 
> from...
> configure.in:32: the top level
> configure.in:32: warning: AC_RUN_IFELSE was called before 
> AC_USE_SYSTEM_EXTENSIONS
> ../../lib/autoconf/specific.m4:368: AC_USE_SYSTEM_EXTENSIONS is expanded 
> from...
> configure.in:32: the top level
> automake: warning: autoconf input should be named 'configure.ac', not 
> 'configure.in'
> configure.in:32: warning: AC_COMPILE_IFELSE was called before 
> AC_USE_SYSTEM_EXTENSIONS
> ../../lib/autoconf/specific.m4:368: AC_USE_SYSTEM_EXTENSIONS is expanded 
> from...
> configure.in:32: the top level
> configure.in:32: warning: AC_RUN_IFELSE was called before 
> AC_USE_SYSTEM_EXTENSIONS
> ../../lib/autoconf/specific.m4:368: AC_USE_SYSTEM_EXTENSIONS is expanded 
> from...
> configure.in:32: the top level
> configure.in:28: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms 
> are deprecated.  For more info, see:
> configure.in:28: 
> http://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_005fINIT_005fAUTOMAKE-invocation
> configure.in:30: installing './compile'
> configure.in:28: installing './missing'
> automake: warning: autoconf input should be named 

Bug#837022: wagon2: FTBFS: dh_auto_test failed

[Lucas Nussbaum]

Source: wagon2
Version: 2.10-4
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mkdir -p /<>/wagon-providers/wagon-scm/target/test-classes/
> svnadmin create 
> /<>/wagon-providers/wagon-scm/target/test-classes/test-repo-svn
> dh_auto_build
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
>  -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo package -DskipTests 
> -Dnotimestamp=true -Dlocale=en_US
> [INFO] Scanning for projects...
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.maven.wagon:wagon-provider-api:jar:2.10
> [WARNING] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ 
> org.apache.maven.wagon:wagon:2.10, /<>/pom.xml, line 378, column 
> 12
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.maven.wagon:wagon-file:jar:2.10
> [WARNING] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ 
> org.apache.maven.wagon:wagon:2.10, /<>/pom.xml, line 378, column 
> 12
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.maven.wagon:wagon-ftp:jar:2.10
> [WARNING] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ 
> org.apache.maven.wagon:wagon:2.10, /<>/pom.xml, line 378, column 
> 12
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.maven.wagon:wagon-http:jar:2.10
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-surefire-plugin @ line 143, column 12
> [WARNING] 'build.plugins.plugin.version' for 
> org.apache.maven.plugins:maven-surefire-plugin is missing. @ line 143, column 
> 12
> [WARNING] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ 
> org.apache.maven.wagon:wagon:2.10, /<>/pom.xml, line 378, column 
> 12
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.maven.wagon:wagon-http-shared:jar:2.10
> [WARNING] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ 
> org.apache.maven.wagon:wagon:2.10, /<>/pom.xml, line 378, column 
> 12
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.maven.wagon:wagon-http-lightweight:jar:2.10
> [WARNING] 'build.plugins.plugin.version' for 
> org.apache.maven.plugins:maven-surefire-plugin is missing. @ line 59, column 
> 12
> [WARNING] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ 
> org.apache.maven.wagon:wagon:2.10, /<>/pom.xml, line 378, column 
> 12
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.maven.wagon:wagon-providers:pom:2.10
> [WARNING] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ 
> org.apache.maven.wagon:wagon:2.10, /<>/pom.xml, line 378, column 
> 12
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.maven.wagon:wagon-provider-test:jar:2.10
> [WARNING] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ 
> org.apache.maven.wagon:wagon:2.10, /<>/pom.xml, line 378, column 
> 12
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.maven.wagon:wagon-tck-http:jar:2.10
> [WARNING] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ 
> org.apache.maven.wagon:wagon:2.10, /<>/pom.xml, line 378, column 
> 12
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.maven.wagon:wagon-tcks:pom:2.10
> [WARNING] 'build.plugins.plugin.version' for 
> org.codehaus.plexus:plexus-component-metadata is missing. @ 
> org.apache.maven.wagon:wagon:2.10, /<>/pom.xml, line 378, column 
> 12
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.maven.wagon:wagon:pom:2.10
> [WARNING] 'build.plugins.plugin.version' for 
> 

Bug#837019: zvbi: FTBFS: dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2

[Lucas Nussbaum]

Source: zvbi
Version: 0.2.35-11
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[4]: Entering directory '/<>/test'
> PASS: ctest
> PASS: cpptest
> PASS: ctest-c89
> PASS: ctest-gnu89
> PASS: ctest-c94
> PASS: ctest-c99
> PASS: ctest-gnu99
> PASS: cpptest-cxx98
> PASS: cpptest-gnuxx98
> PASS: exoptest
> PASS: test-dvb_demux
> PASS: test-dvb_mux
> PASS: test-hamm
> PASS: test-packet-830
> ../test-driver: line 107: 20549 Aborted "$@" > $log_file 2>&1
> FAIL: test-pdc
> PASS: test-raw_decoder
> PASS: test-unicode
> PASS: test-vps
> ==
>zvbi 0.2.35: test/test-suite.log
> ==
> 
> # TOTAL: 18
> # PASS:  17
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> .. contents:: :depth: 2
> 
> FAIL: test-pdc
> ==
> 
> test-pdc: test-pdc.cc:1078: void test_pil_to_time(): Assertion `ztime 
> ("20010215T19") == vbi_pil_to_time (VBI_PIL (2, 15, 20, 0), t1, 
> "Europe/Paris")' failed.
> FAIL test-pdc (exit status: 134)
> 
> 
> Testsuite summary for zvbi 0.2.35
> 
> # TOTAL: 18
> # PASS:  17
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> See test/test-suite.log
> 
> Makefile:1466: recipe for target 'test-suite.log' failed
> make[4]: *** [test-suite.log] Error 1
> make[4]: Leaving directory '/<>/test'
> Makefile:1572: recipe for target 'check-TESTS' failed
> make[3]: *** [check-TESTS] Error 2
> make[3]: Leaving directory '/<>/test'
> Makefile:1764: recipe for target 'check-am' failed
> make[2]: *** [check-am] Error 2
> make[2]: Leaving directory '/<>/test'
> Makefile:510: recipe for target 'check-recursive' failed
> make[1]: *** [check-recursive] Error 1
> make[1]: Leaving directory '/<>'
> dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/09/06/zvbi_0.2.35-11_unstable.log

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

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

Bug#837020: liblightify: FTBFS: doxygen-include.am:47: error: DX_COND_doc does not appear in AM_CONDITIONAL

[Lucas Nussbaum]

Source: liblightify
Version: 0~git20160607-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build  --with autoreconf
>dh_testdir
>dh_update_autotools_config
>dh_autoreconf
> aclocal: warning: couldn't open directory 'm4': No such file or directory
> libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
> libtoolize: copying file 'build-aux/ltmain.sh'
> libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
> libtoolize: copying file 'm4/libtool.m4'
> libtoolize: copying file 'm4/ltoptions.m4'
> libtoolize: copying file 'm4/ltsugar.m4'
> libtoolize: copying file 'm4/ltversion.m4'
> libtoolize: copying file 'm4/lt~obsolete.m4'
> configure.ac:24: installing 'build-aux/compile'
> configure.ac:86: installing 'build-aux/config.guess'
> configure.ac:86: installing 'build-aux/config.sub'
> configure.ac:11: installing 'build-aux/install-sh'
> configure.ac:11: installing 'build-aux/missing'
> configure.ac:9: installing 'build-aux/tap-driver.sh'
> doxygen-include.am:47: error: DX_COND_doc does not appear in AM_CONDITIONAL
> Makefile.am:1:   'doxygen-include.am' included from here
> doxygen-include.am:53: error: DX_COND_html does not appear in AM_CONDITIONAL
> Makefile.am:1:   'doxygen-include.am' included from here
> doxygen-include.am:63: error: DX_COND_chm does not appear in AM_CONDITIONAL
> Makefile.am:1:   'doxygen-include.am' included from here
> doxygen-include.am:67: error: DX_COND_chi does not appear in AM_CONDITIONAL
> Makefile.am:1:   'doxygen-include.am' included from here
> doxygen-include.am:79: error: DX_COND_man does not appear in AM_CONDITIONAL
> Makefile.am:1:   'doxygen-include.am' included from here
> doxygen-include.am:89: error: DX_COND_rtf does not appear in AM_CONDITIONAL
> Makefile.am:1:   'doxygen-include.am' included from here
> doxygen-include.am:99: error: DX_COND_xml does not appear in AM_CONDITIONAL
> Makefile.am:1:   'doxygen-include.am' included from here
> doxygen-include.am:109: error: DX_COND_ps does not appear in AM_CONDITIONAL
> Makefile.am:1:   'doxygen-include.am' included from here
> doxygen-include.am:138: error: DX_COND_pdf does not appear in AM_CONDITIONAL
> Makefile.am:1:   'doxygen-include.am' included from here
> doxygen-include.am:167: error: DX_COND_latex does not appear in AM_CONDITIONAL
> Makefile.am:1:   'doxygen-include.am' included from here
> Makefile.am:4: error: DX_COND_doc does not appear in AM_CONDITIONAL
> Makefile.am:18: error: DX_COND_doc does not appear in AM_CONDITIONAL
> Makefile.am: installing 'build-aux/depcomp'
> parallel-tests: installing 'build-aux/test-driver'
> autoreconf: automake failed with exit status: 1
> dh_autoreconf: autoreconf -f -i returned exit code 1
> debian/rules:4: recipe for target 'build' failed
> make: *** [build] Error 2

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/09/06/liblightify_0~git20160607-1_unstable.log

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

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

Bug#837009: cheetah: FTBFS: debian/rules:20: *** no python implementation resolved from flavor "python$buildver". Stop.

[Lucas Nussbaum]

Source: cheetah
Version: 2.4.4-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  fakeroot debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_clean -k 
> dh_clean: dh_clean -k is deprecated; use dh_prep instead
> dh_installdirs -A 
> mkdir -p "."
> mkdir -p debian/python-module-stampdir
> set -e; cd . && python2 setup.py build 
> --build-base="/<>/./build";
> running build
> running build_py
> running build_ext
> running build_scripts
> touch debian/python-module-stampdir/python-cheetah
> Adding cdbs dependencies to debian/python-cheetah.substvars
> dh_installdirs -ppython-cheetah \
>   
> set -e; cd . && python2 setup.py install 
> --root="/<>/debian/python-cheetah/" --install-layout=deb 
> --no-compile -O0 --single-version-externally-managed;
> running install
> running build
> running build_py
> running build_ext
> running build_scripts
> running install_lib
> creating /<>/debian/python-cheetah/usr
> creating /<>/debian/python-cheetah/usr/lib
> creating /<>/debian/python-cheetah/usr/lib/python2.7
> creating 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages
> creating 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> creating 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah/Tools
> copying build/lib.linux-x86_64-2.7/Cheetah/Tools/SiteHierarchy.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah/Tools
> copying build/lib.linux-x86_64-2.7/Cheetah/Tools/RecursiveNull.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah/Tools
> copying build/lib.linux-x86_64-2.7/Cheetah/Tools/CGITemplate.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah/Tools
> copying build/lib.linux-x86_64-2.7/Cheetah/Tools/__init__.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah/Tools
> copying build/lib.linux-x86_64-2.7/Cheetah/Tools/MondoReport.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah/Tools
> copying build/lib.linux-x86_64-2.7/Cheetah/Template.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> copying build/lib.linux-x86_64-2.7/Cheetah/ImportManager.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> copying build/lib.linux-x86_64-2.7/Cheetah/FileUtils.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> copying build/lib.linux-x86_64-2.7/Cheetah/SettingsManager.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> copying build/lib.linux-x86_64-2.7/Cheetah/DummyTransaction.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> copying build/lib.linux-x86_64-2.7/Cheetah/ImportHooks.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> copying build/lib.linux-x86_64-2.7/Cheetah/DirectiveAnalyzer.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> copying build/lib.linux-x86_64-2.7/Cheetah/SourceReader.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> copying build/lib.linux-x86_64-2.7/Cheetah/Version.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> copying build/lib.linux-x86_64-2.7/Cheetah/NameMapper.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> copying build/lib.linux-x86_64-2.7/Cheetah/Parser.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> copying build/lib.linux-x86_64-2.7/Cheetah/CacheStore.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> copying build/lib.linux-x86_64-2.7/Cheetah/ErrorCatchers.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah
> creating 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah/Utils
> copying build/lib.linux-x86_64-2.7/Cheetah/Utils/WebInputMixin.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah/Utils
> copying build/lib.linux-x86_64-2.7/Cheetah/Utils/Indenter.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah/Utils
> copying build/lib.linux-x86_64-2.7/Cheetah/Utils/Misc.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah/Utils
> copying build/lib.linux-x86_64-2.7/Cheetah/Utils/statprof.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah/Utils
> copying build/lib.linux-x86_64-2.7/Cheetah/Utils/__init__.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah/Utils
> copying build/lib.linux-x86_64-2.7/Cheetah/Utils/htmlEncode.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah/Utils
> copying build/lib.linux-x86_64-2.7/Cheetah/Utils/htmlDecode.py -> 
> /<>/debian/python-cheetah/usr/lib/python2.7/dist-packages/Cheetah/Utils
> 

Bug#837011: ltrace: FTBFS: proc.c:245:3: error: 'readdir_r' is deprecated [-Werror=deprecated-declarations]

[Lucas Nussbaum]

Source: ltrace
Version: 0.7.3-5.1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> /bin/bash ../../libtool --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
> -I../..  -I../../sysdeps/linux-gnu/x86  -I../../sysdeps/linux-gnu   
> -I../../sysdeps -I../..  -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
> -Wsign-compare -Wfloat-equal -Wformat-security -Werror -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o proc.lo proc.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. 
> -I../../sysdeps/linux-gnu/x86 -I../../sysdeps/linux-gnu -I../../sysdeps 
> -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wsign-compare -Wfloat-equal 
> -Wformat-security -Werror -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -c proc.c  -fPIC 
> -DPIC -o .libs/proc.o
> proc.c: In function 'process_tasks':
> proc.c:245:3: error: 'readdir_r' is deprecated 
> [-Werror=deprecated-declarations]
>if (readdir_r(d, , ) != 0) {
>^~
> In file included from proc.c:31:0:
> /usr/include/dirent.h:183:12: note: declared here
>  extern int readdir_r (DIR *__restrict __dirp,
> ^
> cc1: all warnings being treated as errors
> Makefile:366: recipe for target 'proc.lo' failed
> make[5]: *** [proc.lo] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/09/06/ltrace_0.7.3-5.1_unstable.log

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

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

Bug#837013: notmuch: FTBFS: Tests failures

[Lucas Nussbaum]

Source: notmuch
Version: 0.22.1-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> gpg: no valid OpenPGP data found.
> Added 2 new messages to the database.
>  missing prerequisites: database-v1.tar.xz - fetch with 'make 
> download-test-databases'
>  SKIP   all tests in T530-upgrade
>  BROKEN No ghosts should remain after deletion of second message
>   --- T590-thread-breakage.22.expected2016-09-06 22:45:08.15600 
> +
>   +++ T590-thread-breakage.22.output  2016-09-06 22:45:08.15600 
> +
>   @@ -1 +1 @@
>   -0
>   +1
> 
> Notmuch test suite complete.
> 772/778 tests passed.
> 1 broken test failed as expected.
> 5 tests failed.
> test/Makefile.local:64: recipe for target 'test' failed

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/09/06/notmuch_0.22.1-3_unstable.log

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

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

Bug#837012: tachyon: FTBFS: ld: tachyon_ogl-glwin.o: undefined reference to symbol 'XNextEvent'

[Lucas Nussbaum]

Source: tachyon
Version: 0.99~b6+dsx-5
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> /bin/bash ../libtool  --tag=CC   --mode=link gcc -Wno-unused-result 
> -I/usr/include/libdrm -I/usr/include/libdrm -g -O3 
> -fdebug-prefix-map=/<>/tachyon-0.99~b6+dsx=. -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT 
> -ffast-math -fomit-frame-pointer   -o tachyon-ogl tachyon_ogl-main.o 
> tachyon_ogl-getargs.o tachyon_ogl-parse.o tachyon_ogl-nffparse.o 
> tachyon_ogl-mgfparse.o tachyon_ogl-ac3dparse.o tachyon_ogl-glwin.o 
> tachyon_ogl-spaceball.o tachyon_ogl-trackball.o ../src/libtachyon.la -lm -lGL 
>  -lGL 
> libtool: link: gcc -Wno-unused-result -I/usr/include/libdrm 
> -I/usr/include/libdrm -g -O3 
> "-fdebug-prefix-map=/<>/tachyon-0.99~b6+dsx=." -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT 
> -ffast-math -fomit-frame-pointer -o .libs/tachyon-ogl tachyon_ogl-main.o 
> tachyon_ogl-getargs.o tachyon_ogl-parse.o tachyon_ogl-nffparse.o 
> tachyon_ogl-mgfparse.o tachyon_ogl-ac3dparse.o tachyon_ogl-glwin.o 
> tachyon_ogl-spaceball.o tachyon_ogl-trackball.o  ../src/.libs/libtachyon.so 
> -lm -lGL
> /usr/bin/ld: tachyon_ogl-glwin.o: undefined reference to symbol 'XNextEvent'
> //usr/lib/x86_64-linux-gnu/libX11.so.6: error adding symbols: DSO missing 
> from command line
> collect2: error: ld returned 1 exit status

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/09/06/tachyon_0.99~b6+dsx-5_unstable.log

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

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

Bug#837014: mono: FTBFS: build/profiles/basic.make:93: recipe for target 'build/deps/basic-profile-check.exe' failed

[Lucas Nussbaum]

Source: mono
Version: 4.2.1.102+dfsg2-8
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/<>/mono-4.2.1.102+dfsg2/runtime'
> d=`cd ../support && pwd`; \
> sed 
> 's,target="/usr/lib/libMonoPosixHelper.so",target="'$d'/libMonoPosixHelper.la",'
>  ../data/config > etc/mono/configt
> if test -z ""; then :; else \
>   sed 's,target="libgdiplus.so",target="",' etc/mono/configt > 
> etc/mono/configtt; \
>   mv -f etc/mono/configtt etc/mono/configt; fi
> mv -f etc/mono/configt etc/mono/config
> /bin/bash ../mkinstalldirs _tmpinst/bin
> mkdir -p -- _tmpinst/bin
> cp mono-wrapper _tmpinst/bin/mono
> echo '#! /bin/sh' > _tmpinst/bin/ilasm ; \
> r=`pwd`; m=`cd /<>/mono-4.2.1.102+dfsg2/mcs && pwd`; \
> echo 'exec "'"$r/_tmpinst/bin/mono"'" "'"$m/ilasm/ilasm.exe"'" "$@"' >> 
> _tmpinst/bin/ilasm ; \
> chmod +x _tmpinst/bin/ilasm
> echo '#! /bin/sh' > _tmpinst/bin/mcs ; \
> r=`pwd`; m=`cd /<>/mono-4.2.1.102+dfsg2/mcs && pwd`; \
> echo 'exec "'"$r/_tmpinst/bin/mono"'" "'"$m/class/lib/build/mcs.exe"'" "$@"' 
> >> _tmpinst/bin/mcs ; \
> chmod +x _tmpinst/bin/mcs
> echo '#! /bin/sh' > _tmpinst/bin/dmcs ; \
> r=`pwd`; m=`cd /<>/mono-4.2.1.102+dfsg2/mcs && pwd`; \
> echo 'exec "'"$r/_tmpinst/bin/mono"'" "'"$m/class/lib/build/mcs.exe -sdk:4"'" 
> "$@"' >> _tmpinst/bin/dmcs ; \
> chmod +x _tmpinst/bin/dmcs
> echo '#! /bin/sh' > _tmpinst/bin/al2 ; \
> r=`pwd`; m=`cd /<>/mono-4.2.1.102+dfsg2/mcs && pwd`; \
> echo 'exec "'"$r/_tmpinst/bin/mono"'" "'"$m/class/lib/net_2_0/al.exe"'" "$@"' 
> >> _tmpinst/bin/al2 ; \
> chmod +x _tmpinst/bin/al2
> echo '#! /bin/sh' > _tmpinst/bin/al ; \
> r=`pwd`; m=`cd /<>/mono-4.2.1.102+dfsg2/mcs && pwd`; \
> echo 'exec "'"$r/_tmpinst/bin/mono"'" "'"$m/class/lib/net_4_5/al.exe"'" "$@"' 
> >> _tmpinst/bin/al ; \
> chmod +x _tmpinst/bin/al
> if test -w /<>/mono-4.2.1.102+dfsg2/mcs; then :; else chmod -R +w 
> /<>/mono-4.2.1.102+dfsg2/mcs; fi
> cd /<>/mono-4.2.1.102+dfsg2/mcs && /usr/bin/make 
> --no-print-directory -s NO_DIR_CHECK=1 PROFILES='binary_reference_assemblies 
> net_4_5 xbuild_12 xbuild_14' CC='gcc' all-profiles
> mkdir -p -- build/deps
> build/profiles/basic.make:93: recipe for target 
> 'build/deps/basic-profile-check.exe' failed
> make[7]: *** [build/deps/basic-profile-check.exe] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/09/06/mono_4.2.1.102+dfsg2-8_unstable.log

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

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

Bug#837017: libvisio: FTBFS: Tests failures

[Lucas Nussbaum]

Source: libvisio
Version: 0.1.5-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[6]: *** [test-suite.log] Error 1
> make[6]: Leaving directory '/<>/src/test'
> Makefile:892: recipe for target 'check-TESTS' failed
> make[5]: *** [check-TESTS] Error 2
> make[5]: Leaving directory '/<>/src/test'
> Makefile:965: recipe for target 'check-am' failed
> make[4]: *** [check-am] Error 2
> make[4]: Leaving directory '/<>/src/test'
> Makefile:394: recipe for target 'check-recursive' failed
> make[3]: *** [check-recursive] Error 1
> make[3]: Leaving directory '/<>/src'
> Makefile:501: recipe for target 'check-recursive' failed
> make[2]: *** [check-recursive] Error 1
> make[2]: Leaving directory '/<>'
> dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2
> debian/rules:14: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/09/06/libvisio_0.1.5-1_unstable.log

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

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

Bug#837010: gnustep-base: FTBFS: Tests failures

[Lucas Nussbaum]

Source: gnustep-base
Version: 1.24.9-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> 
> Testing NSXMLParser.m...
> Running base/headers/NSXMLParser.m...
> Passed test: NSXMLParser.m:9 ... include of Foundation/NSXMLParser.h works
> Completed file:  NSXMLParser.m
> 
> Testing NSZone.m...
> Running base/headers/NSZone.m...
> Passed test: NSZone.m:9 ... include of Foundation/NSZone.h works
> Completed file:  NSZone.m
> 
> Testing Unicode.m...
> Running base/headers/Unicode.m...
> Passed test: Unicode.m:9 ... include of GNUstepBase/Unicode.h works
> Completed file:  Unicode.m
> debian/rules:166: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/09/06/gnustep-base_1.24.9-3_unstable.log

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

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

Bug#837007: xfce4-radio-plugin: FTBFS: videodev2.h:2105:20: error: field 'timestamp' has incomplete type

[Lucas Nussbaum]

Source: xfce4-radio-plugin
Version: 0.5.1-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG 
> -DPACKAGE_LOCALE_DIR=\"/usr/share/locale\" -pthread 
> -I/usr/include/xfce4/libxfce4panel-1.0 -I/usr/include/gtk-2.0 
> -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ 
> -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 
> -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng16 
> -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
> -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
> -I/usr/include/freetype2 -I/usr/include/xfce4 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/xfce4 
> -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include 
> -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include 
> -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 
> -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
> -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
> -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
> -I/usr/include/freetype2 -I/usr/include/xfce4 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -std=c99 -g -O2 
> -fdebug-prefix-map=/<>=. -fPIE -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o xfce4_radio_plugin-v4l2.o `test -f 'v4l2.c' || 
> echo './'`v4l2.c
> In file included from v4l2.c:25:0:
> /usr/include/linux/videodev2.h:2105:20: error: field 'timestamp' has 
> incomplete type
>   struct timespec   timestamp;
> ^
> Makefile:501: recipe for target 'xfce4_radio_plugin-v4l2.o' failed
> make[3]: *** [xfce4_radio_plugin-v4l2.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/09/06/xfce4-radio-plugin_0.5.1-3_unstable.log

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

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

Bug#837005: mate-applets: FTBFS: ./cpufreq/src/cpufreq-monitor-libcpufreq.c:118: undefined reference to `cpupower_is_cpu_online'

[Lucas Nussbaum]

Source: mate-applets
Version: 1.14.1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> /bin/bash ../../libtool  --tag=CC   --mode=link gcc  -g -O2 
> -fdebug-prefix-map=/<>=. -fPIE -fstack-protector-strong -Wformat 
> -Werror=format-security  -fPIE -pie -Wl,-z,relro -Wl,-z,now -o 
> mate-cpufreq-applet cpufreq-applet.o cpufreq-utils.o cpufreq-prefs.o 
> cpufreq-selector.o cpufreq-popup.o cpufreq-monitor.o 
> cpufreq-monitor-factory.o cpufreq-monitor-procfs.o cpufreq-monitor-sysfs.o 
> cpufreq-monitor-libcpufreq.o cpufreq-monitor-cpuinfo.o -lmate-panel-applet-4 
> -lgtk-3 -lgdk-3 -lpangocairo-1.0 -lpango-1.0 -latk-1.0 -lcairo-gobject 
> -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lmate-desktop-2 
> -lgtk-3 -lgdk-3 -lpangocairo-1.0 -lpango-1.0 -latk-1.0 -lcairo-gobject 
> -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 
> -lstartup-notification-1 -lcpufreq -ldbus-glib-1 -ldbus-1 -lgobject-2.0 
> -lglib-2.0 
> libtool: link: gcc -g -O2 -fdebug-prefix-map=/<>=. -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security -fPIE -pie -Wl,-z 
> -Wl,relro -Wl,-z -Wl,now -o mate-cpufreq-applet cpufreq-applet.o 
> cpufreq-utils.o cpufreq-prefs.o cpufreq-selector.o cpufreq-popup.o 
> cpufreq-monitor.o cpufreq-monitor-factory.o cpufreq-monitor-procfs.o 
> cpufreq-monitor-sysfs.o cpufreq-monitor-libcpufreq.o 
> cpufreq-monitor-cpuinfo.o  -lmate-panel-applet-4 -lmate-desktop-2 -lgtk-3 
> -lgdk-3 -lpangocairo-1.0 -lpango-1.0 -latk-1.0 -lcairo-gobject -lcairo 
> -lgdk_pixbuf-2.0 -lgio-2.0 -lstartup-notification-1 -lcpufreq -ldbus-glib-1 
> -ldbus-1 -lgobject-2.0 -lglib-2.0
> cpufreq-monitor-libcpufreq.o: In function `cpufreq_monitor_libcpufreq_run':
> ./cpufreq/src/cpufreq-monitor-libcpufreq.c:118: undefined reference to 
> `cpupower_is_cpu_online'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/09/06/mate-applets_1.14.1-1_unstable.log

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

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

Bug#837006: gnome-python-desktop: FTBFS: /usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved from binary package "stamp-autotools". Stop.

[Lucas Nussbaum]

Source: gnome-python-desktop
Version: 2.32.0+dfsg-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> test -x debian/rules
> mkdir -p "debian/build"
> CDBS WARNING:DEB_DH_BUILDDEB_ARGS is deprecated since 0.4.85
> set -e;   mv ./config.guess ./config.guess.cdbs-orig; cp --remove-destination 
> /usr/share/misc/config.guess ./config.guess;
> set -e;   mv ./config.sub ./config.sub.cdbs-orig; cp --remove-destination 
> /usr/share/misc/config.sub ./config.sub;
> dh_autoreconf 
> libtoolize: putting auxiliary files in '.'.
> libtoolize: copying file './ltmain.sh'
> libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac,
> libtoolize: and rerunning libtoolize and aclocal.
> libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
> configure.ac:66: installing './compile'
> configure.ac:41: installing './missing'
> braseroburn/Makefile.am:1: warning: 'INCLUDES' is the old name for 
> 'AM_CPPFLAGS' (or '*_CPPFLAGS')
> braseroburn/Makefile.am: installing './depcomp'
> braseromedia/Makefile.am:1: warning: 'INCLUDES' is the old name for 
> 'AM_CPPFLAGS' (or '*_CPPFLAGS')
> evince/Makefile.am:1: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' 
> (or '*_CPPFLAGS')
> evolution/Makefile.am:1: warning: 'INCLUDES' is the old name for 
> 'AM_CPPFLAGS' (or '*_CPPFLAGS')
> gnomeapplet/Makefile.am:1: warning: 'INCLUDES' is the old name for 
> 'AM_CPPFLAGS' (or '*_CPPFLAGS')
> gnomedesktop/Makefile.am:1: warning: 'INCLUDES' is the old name for 
> 'AM_CPPFLAGS' (or '*_CPPFLAGS')
> gnomekeyring/Makefile.am:1: warning: 'INCLUDES' is the old name for 
> 'AM_CPPFLAGS' (or '*_CPPFLAGS')
> gnomeprint/Makefile.am:2: warning: 'INCLUDES' is the old name for 
> 'AM_CPPFLAGS' (or '*_CPPFLAGS')
> gtksourceview/Makefile.am:3: warning: 'INCLUDES' is the old name for 
> 'AM_CPPFLAGS' (or '*_CPPFLAGS')
> gtop/Makefile.am:2: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or 
> '*_CPPFLAGS')
> mediaprofiles/Makefile.am:3: warning: 'INCLUDES' is the old name for 
> 'AM_CPPFLAGS' (or '*_CPPFLAGS')
> metacity/Makefile.am:1: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' 
> (or '*_CPPFLAGS')
> nautilusburn/Makefile.am:1: warning: 'INCLUDES' is the old name for 
> 'AM_CPPFLAGS' (or '*_CPPFLAGS')
> rsvg/Makefile.am:3: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or 
> '*_CPPFLAGS')
> tests/Makefile.am:3: warning: shell echo $$PYTHONPATH: non-POSIX variable name
> tests/Makefile.am:3: (probably a GNU make extension)
> wnck/Makefile.am:1: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or 
> '*_CPPFLAGS')
> touch debian/stamp-autotools-files
> /usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation 
> resolved from binary package "stamp-autotools".  Stop.
> dpkg-buildpackage: error: debian/rules build gave error exit status 2
> 
> Build finished at 2016-09-06T22:49:54Z

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/09/06/gnome-python-desktop_2.32.0+dfsg-3_unstable.log

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

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

Bug#837002: aweather: FTBFS: gps.h:1905:21: error: field 'real' has incomplete type

[Lucas Nussbaum]

Source: aweather
Version: 0.8.1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[4]: Entering directory '/<>/src/plugins'
> ../../doltlibtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I../..  
> -DPKGDATADIR="\"/usr/share/aweather\"" -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
> --std=gnu99 -DSYS_X11 -pthread -I/usr/include/grits 
> -I/usr/include/libsoup-2.4 -I/usr/include/libxml2 -I/usr/include/gtk-2.0 
> -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ 
> -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 
> -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng16 
> -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
> -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/freetype2 -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -c -o 
> alert_la-alert.lo `test -f 'alert.c' || echo './'`alert.c
> alert.c: In function 'msg_load_cap':
> alert.c:332:2: warning: this 'if' clause does not guard... 
> [-Wmisleading-indentation]
>   if (!id) return FALSE; id++;
>   ^~
> alert.c:332:25: note: ...this statement, but the latter is misleadingly 
> indented as if it is guarded by the 'if'
>   if (!id) return FALSE; id++;
>  ^~
> ../../doltlibtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I../..  
> -DPKGDATADIR="\"/usr/share/aweather\"" -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
> --std=gnu99 -DSYS_X11 -pthread -I/usr/include/grits 
> -I/usr/include/libsoup-2.4 -I/usr/include/libxml2 -I/usr/include/gtk-2.0 
> -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ 
> -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 
> -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng16 
> -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
> -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/freetype2 -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -c -o 
> alert_la-alert-info.lo `test -f 'alert-info.c' || echo './'`alert-info.c
> ../../doltlibtool --tag=CC   --mode=link gcc -Wall --std=gnu99 -DSYS_X11 
> -pthread -I/usr/include/grits -I/usr/include/libsoup-2.4 
> -I/usr/include/libxml2 -I/usr/include/gtk-2.0 
> -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ 
> -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 
> -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng16 
> -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
> -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/freetype2 -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -shared -module 
> -avoid-version  -Wl,--as-needed -Wl,-z,relro -o alert.la -rpath 
> /usr/lib/x86_64-linux-gnu/aweather alert_la-alert.lo alert_la-alert-info.lo 
> -lgrits -lX11 -lGL -lGLU -Wl,--export-dynamic -lgmodule-2.0 -pthread 
> -lsoup-2.4 -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo 
> -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 
> -lglib-2.0 -lfontconfig -lfreetype -lgrits -lX11 -lGL -lGLU 
> -Wl,--export-dynamic -lgmodule-2.0 -pthread -lsoup-2.4 -lgtk-x11-2.0 
> -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 
> -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lfontconfig -lfreetype
> libtool: link: gcc -shared  -fPIC -DPIC  .libs/alert_la-alert.o 
> .libs/alert_la-alert-info.o   -lgrits -lX11 -lGL -lGLU -lgmodule-2.0 
> -lsoup-2.4 -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo 
> -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 
> -lglib-2.0 -lfontconfig /usr/lib/x86_64-linux-gnu/libfreetype.so  -pthread 
> -O2 -Wl,--as-needed -Wl,-z -Wl,relro -Wl,--export-dynamic -pthread 
> -Wl,--export-dynamic -pthread   -pthread -Wl,-soname -Wl,alert.so -o 
> .libs/alert.so
> libtool: link: ( cd ".libs" && rm -f "alert.la" && ln -s "../alert.la" 
> "alert.la" )
> ../../doltlibtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I../..  
> -DPKGDATADIR="\"/usr/share/aweather\"" -I../../src -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wall --std=gnu99 -DSYS_X11 -pthread -I/usr/include/grits 
> -I/usr/include/libsoup-2.4 -I/usr/include/libxml2 -I/usr/include/gtk-2.0 
> -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ 
> -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 
> 

Bug#837004: installation-locale: FTBFS: no output file produced because warnings were issued

[Lucas Nussbaum]

Source: installation-locale
Version: 1.6
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> localedef -i C.UTF-8.in -f "UTF-8" ./C.UTF-8
> LC_IDENTIFICATION: unknown standard `C@utf-8:2000' for category `LC_CTYPE'
> LC_IDENTIFICATION: unknown standard `C@utf-8:2000' for category `LC_NUMERIC'
> LC_IDENTIFICATION: unknown standard `C@utf-8:2000' for category `LC_TIME'
> LC_IDENTIFICATION: unknown standard `C@utf-8:2000' for category `LC_COLLATE'
> LC_IDENTIFICATION: unknown standard `C@utf-8:2000' for category `LC_MONETARY'
> LC_IDENTIFICATION: unknown standard `C@utf-8:2000' for category `LC_MESSAGES'
> LC_IDENTIFICATION: unknown standard `C@utf-8:2000' for category `LC_PAPER'
> LC_IDENTIFICATION: unknown standard `C@utf-8:2000' for category `LC_NAME'
> LC_IDENTIFICATION: unknown standard `C@utf-8:2000' for category `LC_ADDRESS'
> LC_IDENTIFICATION: unknown standard `C@utf-8:2000' for category `LC_TELEPHONE'
> LC_IDENTIFICATION: unknown standard `C@utf-8:2000' for category 
> `LC_IDENTIFICATION'
> no output file produced because warnings were issued
> Makefile:4: recipe for target 'C.UTF-8' failed
> make[1]: *** [C.UTF-8] Error 4

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/09/06/installation-locale_1.6_unstable.log

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

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

Bug#837000: kerberos-configs: FTBFS: Undefined subroutine ::read_config called at ./genblob line 9.

[Lucas Nussbaum]

Source: kerberos-configs
Version: 2.3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  fakeroot debian/rules binary
> ./genblob >tmp & tmp config-blob
> Undefined subroutine ::read_config called at ./genblob line 9.
> debian/rules:17: recipe for target 'config-blob' failed
> make: *** [config-blob] Error 2

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/09/06/kerberos-configs_2.3_unstable.log

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

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

Bug#836999: strace: FTBFS: ../btrfs.c:68:8: error: redefinition of 'struct btrfs_ioctl_defrag_range_args'

[Lucas Nussbaum]

Source: strace
Version: 4.12-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H   -I./linux/x86_64 -I../linux/x86_64 -I./linux -I../linux 
> -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wwrite-strings 
> -Wsign-compare  -g -O2 -fdebug-prefix-map=/<>=. -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall -g -O2 -MT 
> strace-btrfs.o -MD -MP -MF .deps/strace-btrfs.Tpo -c -o strace-btrfs.o `test 
> -f 'btrfs.c' || echo '../'`btrfs.c
> ../btrfs.c:68:8: error: redefinition of 'struct btrfs_ioctl_defrag_range_args'
>  struct btrfs_ioctl_defrag_range_args {
> ^
> In file included from ../btrfs.c:36:0:
> /usr/include/linux/btrfs.h:496:8: note: originally defined here
>  struct btrfs_ioctl_defrag_range_args {
> ^
> Makefile:2619: recipe for target 'strace-btrfs.o' failed
> make[3]: *** [strace-btrfs.o] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/09/06/strace_4.12-3_unstable.log

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

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

Bug#837001: naspro-core: FTBFS: fs.c:106:3: error: 'readdir_r' is deprecated [-Werror=deprecated-declarations]

[Lucas Nussbaum]

Source: naspro-core
Version: 0.5.1-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> /bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
> -I../..  -I../../include -I../../src -Wdate-time -D_FORTIFY_SOURCE=2 
> -pedantic -Wall -Werror -pthread -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -c -o fs.lo fs.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -I../../include 
> -I../../src -Wdate-time -D_FORTIFY_SOURCE=2 -pedantic -Wall -Werror -pthread 
> -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -c fs.c  -fPIC -DPIC -o .libs/fs.o
> fs.c: In function 'nacore_fs_dir_get_next_entry':
> fs.c:106:3: error: 'readdir_r' is deprecated [-Werror=deprecated-declarations]
>readdir_r(dir->dir, (struct dirent *)ret, );
>^
> In file included from fs.c:27:0:
> /usr/include/dirent.h:183:12: note: declared here
>  extern int readdir_r (DIR *__restrict __dirp,
> ^
> cc1: all warnings being treated as errors
> Makefile:398: recipe for target 'fs.lo' failed
> make[5]: *** [fs.lo] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/09/06/naspro-core_0.5.1-2_unstable.log

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

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

Bug#836998: dbus-sharp-glib: FTBFS: mdoc: Could not find file "/etc/localtime"

[Lucas Nussbaum]

Source: dbus-sharp-glib
Version: 0.6.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/<>'
> make[3]: Nothing to be done for 'all-am'.
> make[3]: Leaving directory '/<>'
> make[2]: Leaving directory '/<>'
> mkdir -p /<>/doc;
> for LIB in /<>/src/dbus-sharp-glib.dll; do \
>   mdoc update \
>   -fno-assembly-versions \
>   --out=/<>/doc \
>   $LIB; \
>   mdoc assemble \
>   --format ecma \
>   --out ${LIB%.dll} \
>   /<>/doc; \
> done
> New Type: DBus.BusG
> Member Added: public static void Init ();
> Member Added: public static void Init (DBus.Connection conn);
> Namespace Directory Created: DBus
> New Namespace File: DBus
> Members Added: 2, Members Deleted: 0
> mdoc: Could not find file "/etc/localtime"
> See `mdoc help' for more information.
> debian/rules:16: recipe for target 'override_dh_auto_build' failed
> make[1]: *** [override_dh_auto_build] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/09/06/dbus-sharp-glib_0.6.0-1_unstable.log

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

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

Bug#836962: Uninstallable in testing when default-libmysqlclient-dev is installed

[Enrico Zini]

On Wed, Sep 07, 2016 at 06:09:16PM +0200, Sebastiaan Couwenberg wrote:

> I'm very disappointed that the introduction of the
> default-libmysqlclient-dev packages now immediately results in RC bugs.
> 
> For now I've changed the dependency to default-libmysqlclient-dev, but
> I'm considering dropping MySQL/MariaDB support because of my
> disappointment in its maintainers.

Hi, thanks for dealing with this so quickly.

Note that it might have been a misjudgement of mine to set severity of
this bug to serious, rather than a fault of the mysql/mariadb
mainatainers.


Enrico

-- 
GPG key: 4096R/634F4BD1E7AD5568 2009-05-08 Enrico Zini 


signature.asc
Description: PGP signature

Processed: fixed 836970 in 1.1.5~dfsg0-2

[Debian Bug Tracking System]

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

> fixed 836970 1.1.5~dfsg0-2
Bug #836970 {Done: Philipp Huebner } 
[src:erlang-p1-sqlite3] erlang-p1-sqlite3: FTBFS: Missing Build-Depends on 
erlang-crypto
Marked as fixed in versions erlang-p1-sqlite3/1.1.5~dfsg0-2.
> thanks
Stopping processing here.

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

Processed: fixed 836969 in 1.15.1-3

[Debian Bug Tracking System]

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

> fixed 836969 1.15.1-3
Bug #836969 {Done: Philipp Huebner } 
[src:erlang-p1-xmlrpc] erlang-p1-xmlrpc: FTBFS: Missing Build-Depends on 
erlang-crypto
Marked as fixed in versions erlang-p1-xmlrpc/1.15.1-3.
> thanks
Stopping processing here.

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

Bug#836995: texlive-base: fails to upgrade wheezy -> jessie -> stretch

[Andreas Beckmann]

Package: texlive-base
Version: 2016.20160819-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + tex4ht

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'wheezy' to 'jessie' to 'stretch'.
It installed fine in 'wheezy', and upgraded to 'jessie' successfully,
but then the upgrade to 'stretch' failed.

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

  Selecting previously unselected package texlive-base.
  Preparing to unpack .../texlive-base_2016.20160819-2_all.deb ...
  Unpacking texlive-base (2016.20160819-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/texlive-base_2016.20160819-2_all.deb (--unpack):
   trying to overwrite '/usr/share/texlive/tlpkg/TeXLive/TLConfFile.pm', which 
is also in package texlive-common 2012.20120611-5
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)


Please add appropriate Breaks+Replaces against texlive-common/wheezy
which may have survived some wheezy->jessie upgrades.


cheers,

Andreas


tex4ht_20160814-1.log.gz
Description: application/gzip

Processed: fixed 836968 in 0.6.1-2

[Debian Bug Tracking System]

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

> fixed 836968 0.6.1-2
Bug #836968 {Done: Philipp Huebner } 
[src:erlang-p1-oauth2] erlang-p1-oauth2: FTBFS: Missing Build-Depends on 
erlang-crypto
Marked as fixed in versions erlang-p1-oauth2/0.6.1-2.
> thanks
Stopping processing here.

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

Processed: texlive-base: fails to upgrade wheezy -> jessie -> stretch

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + tex4ht
Bug #836995 [texlive-base] texlive-base: fails to upgrade wheezy -> jessie -> 
stretch
Added indication that 836995 affects tex4ht

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

Bug#823574: knot: fails to upgrade from 'jessie': Error: syntax error (file '/var/backups/knot/20160503-122201/knot.conf', line 6)

[Andreas Beckmann]

Followup-For: Bug #823574

Please update the package in jessie-backports to a fixed version.

Thanks


Andreas

Bug#836970: marked as done (erlang-p1-sqlite3: FTBFS: Missing Build-Depends on erlang-crypto)

[Debian Bug Tracking System]

Your message dated Wed, 7 Sep 2016 23:54:00 +0200
with message-id 
and subject line Re: FTBFS: Missing Build-Depends on erlang-crypto
has caused the Debian Bug report #836970,
regarding erlang-p1-sqlite3: FTBFS: Missing Build-Depends on erlang-crypto
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.)


-- 
836970: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836970
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: erlang-p1-sqlite3
Version: 1.1.5~dfsg0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
Tags: patch
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

erlang-p1-sqlite3 fails to build from source in unstable/amd64 due to
missing Build-Depends on erlang-crypto:

  [..]

  
  
**
  ** Starting build 
  **
  
**
  
   Package:  erlang-p1-sqlite3
   Version:  1.1.5~dfsg0-1
   Build architecture:   amd64
   Date: Wed, 07 Sep 2016 17:38:40 +0100
   Hostname: 2119ab903179
   Uname:Linux 2119ab903179 4.7.0-1-amd64 #1 SMP Debian 4.7.2-1 
(2016-08-28) x86_64 GNU/Linux
   /etc/timezone:Europe/London
  
  
**
  ** Installing build dependencies  
  **
  
**
  
  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'erlang-p1-sqlite3-build-deps' in 
'../erlang-p1-sqlite3-build-deps_1.1.5~dfsg0-1_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package erlang-p1-sqlite3-build-deps.
  (Reading database ... 23306 files and directories currently installed.)
  Preparing to unpack erlang-p1-sqlite3-build-deps_1.1.5~dfsg0-1_all.deb ...
  Unpacking erlang-p1-sqlite3-build-deps (1.1.5~dfsg0-1) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
dh-rebar erlang-base erlang-dev erlang-eunit erlang-mnesia
erlang-runtime-tools erlang-syntax-tools erlang-tools libsqlite3-dev rebar
  Suggested packages:
erlang erlang-manpages erlang-doc sqlite3-doc
  Recommended packages:
libsctp1 erlang-crypto mercurial
  The following NEW packages will be installed:
dh-rebar erlang-base erlang-dev erlang-eunit erlang-mnesia
erlang-runtime-tools erlang-syntax-tools erlang-tools libsqlite3-dev rebar
  0 upgraded, 10 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 10.3 MB of archives.
  After this operation, 24.1 MB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 erlang-base amd64 
1:19.0.5+dfsg-3 [7073 kB]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 erlang-dev amd64 
1:19.0.5+dfsg-3 [359 kB]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 erlang-mnesia amd64 
1:19.0.5+dfsg-3 [747 kB]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 erlang-runtime-tools 
amd64 1:19.0.5+dfsg-3 [205 kB]
  Get:5 http://httpredir.debian.org/debian sid/main amd64 erlang-tools amd64 
1:19.0.5+dfsg-3 [521 kB]
  Get:6 http://httpredir.debian.org/debian sid/main amd64 erlang-syntax-tools 
amd64 1:19.0.5+dfsg-3 [373 kB]
  Get:7 http://httpredir.debian.org/debian sid/main amd64 rebar amd64 2.6.2-2 
[203 kB]
  Get:8 http://httpredir.debian.org/debian sid/main amd64 dh-rebar all 0.0.4 
[7298 B]
  Get:9 http://httpredir.debian.org/debian sid/main amd64 erlang-eunit amd64 
1:19.0.5+dfsg-3 [164 kB]
  Get:10 http://httpredir.debian.org/debian sid/main amd64 libsqlite3-dev amd64 
3.14.1-1 [689 kB]
  Fetched 10.3 MB in 0s (61.3 MB/s)
  Selecting previously unselected package erlang-base.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%

Bug#836969: marked as done (erlang-p1-xmlrpc: FTBFS: Missing Build-Depends on erlang-crypto)

[Debian Bug Tracking System]

Your message dated Wed, 7 Sep 2016 23:54:00 +0200
with message-id 
and subject line Re: FTBFS: Missing Build-Depends on erlang-crypto
has caused the Debian Bug report #836969,
regarding erlang-p1-xmlrpc: FTBFS: Missing Build-Depends on erlang-crypto
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.)


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

Dear Maintainer,

erlang-p1-xmlrpc fails to build from source in unstable/amd64 due to
missing Build-Depends on erlang-crypto:

  [..]

  
  
**
  ** Starting build 
  **
  
**
  
   Package:  erlang-p1-xmlrpc
   Version:  1.15.1-2
   Build architecture:   amd64
   Date: Wed, 07 Sep 2016 17:38:54 +0100
   Hostname: eba892046709
   Uname:Linux eba892046709 4.7.0-1-amd64 #1 SMP Debian 4.7.2-1 
(2016-08-28) x86_64 GNU/Linux
   /etc/timezone:Europe/London
  
  
**
  ** Installing build dependencies  
  **
  
**
  
  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'erlang-p1-xmlrpc-build-deps' in 
'../erlang-p1-xmlrpc-build-deps_1.15.1-2_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package erlang-p1-xmlrpc-build-deps.
  (Reading database ... 23306 files and directories currently installed.)
  Preparing to unpack erlang-p1-xmlrpc-build-deps_1.15.1-2_all.deb ...
  Unpacking erlang-p1-xmlrpc-build-deps (1.15.1-2) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
dh-rebar erlang-base erlang-dev erlang-eunit erlang-mnesia
erlang-runtime-tools erlang-syntax-tools erlang-tools erlang-xmerl rebar
  Suggested packages:
erlang erlang-manpages erlang-doc
  Recommended packages:
libsctp1 erlang-crypto mercurial
  The following NEW packages will be installed:
dh-rebar erlang-base erlang-dev erlang-eunit erlang-mnesia
erlang-runtime-tools erlang-syntax-tools erlang-tools erlang-xmerl rebar
  0 upgraded, 10 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 10.6 MB of archives.
  After this operation, 23.7 MB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 erlang-base amd64 
1:19.0.5+dfsg-3 [7073 kB]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 erlang-dev amd64 
1:19.0.5+dfsg-3 [359 kB]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 erlang-mnesia amd64 
1:19.0.5+dfsg-3 [747 kB]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 erlang-runtime-tools 
amd64 1:19.0.5+dfsg-3 [205 kB]
  Get:5 http://httpredir.debian.org/debian sid/main amd64 erlang-tools amd64 
1:19.0.5+dfsg-3 [521 kB]
  Get:6 http://httpredir.debian.org/debian sid/main amd64 erlang-syntax-tools 
amd64 1:19.0.5+dfsg-3 [373 kB]
  Get:7 http://httpredir.debian.org/debian sid/main amd64 rebar amd64 2.6.2-2 
[203 kB]
  Get:8 http://httpredir.debian.org/debian sid/main amd64 dh-rebar all 0.0.4 
[7298 B]
  Get:9 http://httpredir.debian.org/debian sid/main amd64 erlang-eunit amd64 
1:19.0.5+dfsg-3 [164 kB]
  Get:10 http://httpredir.debian.org/debian sid/main amd64 erlang-xmerl amd64 
1:19.0.5+dfsg-3 [985 kB]
  Fetched 10.6 MB in 0s (64.0 MB/s)
  Selecting previously unselected package erlang-base.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading 

Bug#836968: marked as done (erlang-p1-oauth2: FTBFS: Missing Build-Depends on erlang-crypto)

[Debian Bug Tracking System]

Your message dated Wed, 7 Sep 2016 23:54:00 +0200
with message-id 
and subject line Re: FTBFS: Missing Build-Depends on erlang-crypto
has caused the Debian Bug report #836968,
regarding erlang-p1-oauth2: FTBFS: Missing Build-Depends on erlang-crypto
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.)


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

Dear Maintainer,

erlang-p1-oauth2 fails to build from source in unstable/amd64 due to
missing Build-Depends on  erlang-crypto:

  [..]

  
  
**
  ** Starting build 
  **
  
**
  
   Package:  erlang-p1-oauth2
   Version:  0.6.1-1
   Build architecture:   amd64
   Date: Wed, 07 Sep 2016 17:38:25 +0100
   Hostname: e2d200a4c95d
   Uname:Linux e2d200a4c95d 4.7.0-1-amd64 #1 SMP Debian 4.7.2-1 
(2016-08-28) x86_64 GNU/Linux
   /etc/timezone:Europe/London
  
  
**
  ** Installing build dependencies  
  **
  
**
  
  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'erlang-p1-oauth2-build-deps' in 
'../erlang-p1-oauth2-build-deps_0.6.1-1_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package erlang-p1-oauth2-build-deps.
  (Reading database ... 23306 files and directories currently installed.)
  Preparing to unpack erlang-p1-oauth2-build-deps_0.6.1-1_all.deb ...
  Unpacking erlang-p1-oauth2-build-deps (0.6.1-1) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
dh-rebar erlang-base erlang-dev erlang-eunit erlang-meck erlang-mnesia
erlang-proper erlang-proper-dev erlang-runtime-tools erlang-syntax-tools
erlang-tools rebar
  Suggested packages:
erlang erlang-manpages erlang-doc
  Recommended packages:
libsctp1 erlang-crypto mercurial
  The following NEW packages will be installed:
dh-rebar erlang-base erlang-dev erlang-eunit erlang-meck erlang-mnesia
erlang-proper erlang-proper-dev erlang-runtime-tools erlang-syntax-tools
erlang-tools rebar
  0 upgraded, 12 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 9987 kB of archives.
  After this operation, 22.6 MB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 erlang-base amd64 
1:19.0.5+dfsg-3 [7073 kB]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 erlang-dev amd64 
1:19.0.5+dfsg-3 [359 kB]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 erlang-mnesia amd64 
1:19.0.5+dfsg-3 [747 kB]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 erlang-runtime-tools 
amd64 1:19.0.5+dfsg-3 [205 kB]
  Get:5 http://httpredir.debian.org/debian sid/main amd64 erlang-tools amd64 
1:19.0.5+dfsg-3 [521 kB]
  Get:6 http://httpredir.debian.org/debian sid/main amd64 erlang-syntax-tools 
amd64 1:19.0.5+dfsg-3 [373 kB]
  Get:7 http://httpredir.debian.org/debian sid/main amd64 rebar amd64 2.6.2-2 
[203 kB]
  Get:8 http://httpredir.debian.org/debian sid/main amd64 dh-rebar all 0.0.4 
[7298 B]
  Get:9 http://httpredir.debian.org/debian sid/main amd64 erlang-eunit amd64 
1:19.0.5+dfsg-3 [164 kB]
  Get:10 http://httpredir.debian.org/debian sid/main amd64 erlang-proper amd64 
1.1+gitfa58f82bdc+dfsg-1 [269 kB]
  Get:11 http://httpredir.debian.org/debian sid/main amd64 erlang-proper-dev 
amd64 1.1+gitfa58f82bdc+dfsg-1 [4958 B]
  Get:12 http://httpredir.debian.org/debian 

Processed: unarchiving 823574, found 823574 in 2.2.0-2~bpo80+1

[Debian Bug Tracking System]

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

> unarchive 823574
Bug #823574 {Done: Ondřej Surý } [knot] knot: fails to 
upgrade from 'jessie': Error: syntax error (file 
'/var/backups/knot/20160503-122201/knot.conf', line 6)
Unarchived Bug 823574
> found 823574 2.2.0-2~bpo80+1
Bug #823574 {Done: Ondřej Surý } [knot] knot: fails to 
upgrade from 'jessie': Error: syntax error (file 
'/var/backups/knot/20160503-122201/knot.conf', line 6)
Marked as found in versions knot/2.2.0-2~bpo80+1.
> thanks
Stopping processing here.

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

Bug#808312: chemps2: fails to upgrade from 'testing' - trying to overwrite /usr/share/man/man1/chemps2.1.gz

[Andreas Beckmann]

Followup-For: Bug #808312

Hi,

the fix seems to have disappeared, as can be seen in upgrades from
jessie-backports to stretch failing:

  Preparing to unpack .../chemps2_1.8-1_amd64.deb ...
  Unpacking chemps2 (1.8-1) over (1.6-1~bpo80+1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/chemps2_1.8-1_amd64.deb (--unpack):
   trying to overwrite '/usr/share/man/man1/chemps2.1.gz', which is also in 
package libchemps2-1 1.6-1~bpo80+1


Andreas


chemps2_1.8-1.log.gz
Description: application/gzip

Bug#836993: qgis: fails to upgrade from 'jessie': dpkg-divert: error: rename involves overwriting `/usr/bin/qgis'

[Sebastiaan Couwenberg]

Control: tags -1 pending

Hi Andreas,

Thanks for your work on piuparts.

I've moved the diversion removal to postinst per your suggestion, thanks!

A new upload to unstable will follow shortly.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Processed: Re: Bug#836993: qgis: fails to upgrade from 'jessie': dpkg-divert: error: rename involves overwriting `/usr/bin/qgis'

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #836993 [qgis] qgis: fails to upgrade from 'jessie': dpkg-divert: error: 
rename involves overwriting `/usr/bin/qgis'
Added tag(s) pending.

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

Processed: unarchiving 808312, found 808312 in 1.8-1

[Debian Bug Tracking System]

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

> unarchive 808312
Bug #808312 {Done: Sebastian Wouters } [chemps2] 
chemps2: fails to upgrade from 'testing' - trying to overwrite 
/usr/share/man/man1/chemps2.1.gz
Unarchived Bug 808312
> found 808312 1.8-1
Bug #808312 {Done: Sebastian Wouters } [chemps2] 
chemps2: fails to upgrade from 'testing' - trying to overwrite 
/usr/share/man/man1/chemps2.1.gz
Marked as found in versions chemps2/1.8-1 and reopened.
> thanks
Stopping processing here.

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

Processed: qgis: fails to upgrade from 'jessie': dpkg-divert: error: rename involves overwriting `/usr/bin/qgis'

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + science-geography
Bug #836993 [qgis] qgis: fails to upgrade from 'jessie': dpkg-divert: error: 
rename involves overwriting `/usr/bin/qgis'
Added indication that 836993 affects science-geography

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

Bug#836991: golang-doc: fails to upgrade from 'jessie': error: directory '/usr/lib/go' contains files not owned by package golang-go:i386, cannot switch to symlink

[Andreas Beckmann]

Package: golang-doc
Version: 2:1.7~1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'jessie'.
It installed fine in 'jessie', then the upgrade to 'stretch' fails.

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

  Preparing to unpack .../golang-go_2%3a1.7~1_i386.deb ...
  dpkg-maintscript-helper: error: directory '/usr/lib/go' contains files not 
owned by package golang-go:i386, cannot switch to symlink
  dpkg: error processing archive 
/var/cache/apt/archives/golang-go_2%3a1.7~1_i386.deb (--unpack):
   subprocess new pre-installation script returned error exit status 1


cheers,

Andreas


golang-doc_2:1.7~1.log.gz
Description: application/gzip

Processed: libcamitk4: fails to upgrade from 'jessie' - trying to overwrite /usr/bin/camitk-config

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + med-imaging-dev med-imaging
Bug #836990 [libcamitk4] libcamitk4: fails to upgrade from 'jessie' - trying to 
overwrite /usr/bin/camitk-config
Added indication that 836990 affects med-imaging-dev and med-imaging

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

Bug#825320: gcc-doc-defaults: FTBFS in sid: error in 'Version' field string '5:': nothing after colon in version number

[Dmitry Eremin-Solenikov]

Package: gcc-doc
Followup-For: Bug #825320

The error with gnat-doc package version was most probably caused by the
missinchronization of gcc-doc-defaults rebuild vs. gnat defaults
changes. The attached patch should adds support for new GCC/GNAT/etc
packages defaulting to 6.x branch.

-- 
With best wishes
Dmitry


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

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

Versions of packages gcc-doc depends on:
ii  gcc-6-doc  6.1.0-1

gcc-doc recommends no packages.

gcc-doc suggests no packages.

-- no debconf information
diff -Napur gcc-doc-defaults-14/debian/changelog gcc-doc-defaults-15/debian/changelog
--- gcc-doc-defaults-14/debian/changelog	2015-05-05 23:43:02.0 +0300
+++ gcc-doc-defaults-15/debian/changelog	2016-09-08 00:06:02.187292450 +0300
@@ -1,3 +1,9 @@
+gcc-doc-defaults (5:15) unstable; urgency=medium
+
+  * Updated to 6.1 versions. (Closes: #794778, #833505, #825320)
+
+ -- Dmitry Eremin-Solenikov   Wed, 07 Sep 2016 23:48:17 +0300
+
 gcc-doc-defaults (5:14) unstable; urgency=medium
 
   * Updated gcc/doc/ with upstream 4.9.1.
diff -Napur gcc-doc-defaults-14/debian/control gcc-doc-defaults-15/debian/control
--- gcc-doc-defaults-14/debian/control	2015-05-05 23:43:47.0 +0300
+++ gcc-doc-defaults-15/debian/control	2016-09-07 23:52:23.662784731 +0300
@@ -16,7 +16,7 @@ Vcs-Git: git://anonscm.debian.org/users/
 
 Package: gcc-doc
 Architecture: any
-Depends: gcc-4.9-doc (>= 4.9.2-1~), ${misc:Depends}
+Depends: gcc-6-doc (>= 6.1.0-1~), ${misc:Depends}
 Replaces: gcc (<< 4:4.1.1-7), g++ (<< 4:4.1.1-7)
 Breaks: gcc (<< 4:4.1.1-7), g++ (<< 4:4.1.1-7)
 Description: documentation for the GNU compilers (gcc, gobjc, g++)
@@ -27,7 +27,7 @@ Description: documentation for the GNU c
 
 Package: cpp-doc
 Architecture: any
-Depends: cpp-4.9-doc (>= 4.9.2-1~), ${misc:Depends}
+Depends: cpp-6-doc (>= 6.1.0-1~), ${misc:Depends}
 Replaces: cpp (<< 4:4.1.1-7)
 Breaks: cpp (<< 4:4.1.1-7)
 Description: documentation for the GNU C preprocessor (cpp)
@@ -38,7 +38,7 @@ Description: documentation for the GNU C
 
 Package: gfortran-doc
 Architecture: any
-Depends: gfortran-4.9-doc (>= 4.9.2-1~), ${misc:Depends}
+Depends: gfortran-6-doc (>= 6.1.0-1~), ${misc:Depends}
 Replaces: gfortran (<< 4:4.1.1-7)
 Breaks: gfortran (<< 4:4.1.1-7)
 Description: documentation for the GNU Fortran Compiler (gfortran)
@@ -49,7 +49,7 @@ Description: documentation for the GNU F
 
 Package: gnat-doc
 Architecture: any
-Depends: gnat-4.9-doc (>= 4.9.2-1~), ${misc:Depends}
+Depends: gnat-6-doc (>= 6.1.0-1~), ${misc:Depends}
 Description: documentation for the GNU Ada Compiler (gnat)
  This is the dependency package that should install documentation
  for Debian default version of GNU Ada compiler.
@@ -58,7 +58,7 @@ Description: documentation for the GNU A
 
 Package: gcj-doc
 Architecture: any
-Depends: gcj-4.9-doc (>= 4.9.2-1~), ${misc:Depends}
+Depends: gcj-6-doc (>= 6.1.0-1~), ${misc:Depends}
 Replaces: gcj (<< 4:4.3.1-2)
 Breaks: gcj (<< 4:4.3.1-2)
 Description: documentation for the GNU Java tools (gcj, gij)
@@ -69,7 +69,7 @@ Description: documentation for the GNU J
 
 Package: gccgo-doc
 Architecture: amd64 arm64 armel armhf i386 ia64 mips mips64 mips64el mipsel powerpc ppc64 ppc64el s390 s390x x32
-Depends: gccgo-4.9-doc (>= 4.9.2-1~), ${misc:Depends}
+Depends: gccgo-6-doc (>= 6.1.0-1~), ${misc:Depends}
 Description: documentation for the GNU Go compiler (gccgo)
  This is the dependency package that should install documentation
  for Debian default version of GNU Go compiler.
diff -Napur gcc-doc-defaults-14/debian/rules gcc-doc-defaults-15/debian/rules
--- gcc-doc-defaults-14/debian/rules	2015-05-05 23:26:21.0 +0300
+++ gcc-doc-defaults-15/debian/rules	2016-09-07 23:52:07.337702255 +0300
@@ -12,6 +12,7 @@ DOC_VER_4.7 := 4.7.4-1~
 DOC_VER_4.8 := 4.8.4-1~
 DOC_VER_4.9 := 4.9.2-1~
 DOC_VER_5   := 5.1.0-1~
+DOC_VER_6   := 6.1.0-1~
 
 # The version for binary packages: gcc-doc-base, gcc-doc, etc.
 # Automatic set debian revision, adapted from gcc-defaults' rules.
@@ -27,15 +28,18 @@ DEBIAN_EPOCH := $(shell echo $(VDEF) | a
 #PKG_VER_4.8 := 4.8.4-1
 #PKG_VER_4.9 := 4.9.2-1
 #PKG_VER_5   := 5.1.0-1
+#PKG_VER_6   := 6.1.0-1
 
-PKG_VER_4.4 := 4.4.7-$(shell expr $(VMAJOR) - 4)
-PKG_VER_4.6 := 4.6.4-$(shell expr $(VMAJOR) - 5)
-PKG_VER_4.7 := 4.7.4-$(shell expr $(VMAJOR) - 9)
-PKG_VER_4.8 := 4.8.4-$(shell expr $(VMAJOR) - 13)
-PKG_VER_4.9 := 4.9.2-$(shell expr $(VMAJOR) - 13)
-PKG_VER_5   := 5.1.0-$(shell expr $(VMAJOR) - 13)
+PKG_VER_4.4 := 4.4.7-$(shell expr $(VMAJOR) - 5)
+PKG_VER_4.6 := 4.6.4-$(shell expr $(VMAJOR) - 6)
+PKG_VER_4.7 := 4.7.4-$(shell expr $(VMAJOR) - 10)
+PKG_VER_4.8 := 4.8.4-$(shell expr $(VMAJOR) - 

Bug#802021: audacity: non-free files

[James Cowgill]

Hi,

On 07/09/16 20:26, Herbert Fortes wrote:
>>
>> Files in "lib-src/libnyquist/nyquist/xlisp" have the following in the
> header:
>>
>> Copyright (c) 1985, by David Michael Betz
>> All Rights Reserved
>> Permission is granted for unrestricted non-commercial use
>>
> 
> I tried to send an email to David Michael Betz
> but the email returns. I tried to email address:

There seems to be a more recent version of xlisp on this site:
http://www.xlisp.org/

It has another email address (which I've CCed). Hopefully it works!

Maybe part of the solution to this bug is to update audacity's copy of
xlisp to this new version which seems to be under the BSD 3-clause license?

(of course there are some other non-free files to look at as well)

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#836989: fontforge-common: fails to upgrade from 'sid' - trying to overwrite /usr/share/mime/packages/fontforge.xml

[Andreas Beckmann]

Package: fontforge-common
Version: 1:20160404~dfsg-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + fontforge

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' 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...):

  Preparing to unpack .../0-fontforge-common_1%3a20160404~dfsg-3_all.deb ...
  Unpacking fontforge-common (1:20160404~dfsg-3) over (20120731.b-7.2) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-UtugTa/0-fontforge-common_1%3a20160404~dfsg-3_all.deb 
(--unpack):
   trying to overwrite '/usr/share/mime/packages/fontforge.xml', which is also 
in package fontforge 20120731.b-7.2
  Preparing to unpack .../1-fontforge_1%3a20160404~dfsg-3_amd64.deb ...
  Unpacking fontforge (1:20160404~dfsg-3) over (20120731.b-7.2) ...
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-UtugTa/0-fontforge-common_1%3a20160404~dfsg-3_all.deb
 

cheers,

Andreas


fontforge_1:20160404~dfsg-3.log.gz
Description: application/gzip

Processed: fontforge-common: fails to upgrade from 'sid' - trying to overwrite /usr/share/mime/packages/fontforge.xml

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + fontforge
Bug #836989 [fontforge-common] fontforge-common: fails to upgrade from 'sid' - 
trying to overwrite /usr/share/mime/packages/fontforge.xml
Added indication that 836989 affects fontforge

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

Bug#836508: barbican: FTBFS in testing (failing tests)

[Santiago Vila]

On Wed, 7 Sep 2016, Thomas Goirand wrote:

> Santiago,
> 
> Please don't play BTS pingpong. This bug shall stay closed. The issue
> was in pyopenssl, and never in Barbican.
> 
> We don't increase version numbers just to avoid bugs. It has never been
> done, and will never be done. Otherwise, we'd be doing this for every
> single bug sent to the BTS, multiplied by the number of reverse
> dependencies.

That's a straw man argument, at least for two reasons:

* Not every bug sent to the BTS is a bug which make other packages to FTBFS.
* We sometimes increase version numbers to avoid FTBFS bugs.

Therefore, asking for a version increase was not as unreasonable as
you paint it.

If you consider that this is not necessary in this particular case,
so be it, but please don't use fallacious arguments.

Thanks.

Bug#835720: salmon: FTBFS: BAMQueue.tpp:88:29: error: no matching function for call to 'spdlog::logger::warn()'

[Sascha Steinbiss]

Hi Andreas,

>> I’d rather get it to work for now and will try including the smallest 
>> necessary set of code needed to build salmon. It is definitely more than one 
>> file; currently I’m using trial and error to arrive at a minimal set. I have 
>> also opened https://github.com/COMBINE-lab/salmon/issues/87, let’s see what 
>> they say.
> 
> I guess you might be able to get the full set when checking my rapmap related 
> quilt patch which contains a list.

True. BTW it builds now with some RapMap code added back in (see git) but one 
of the unit tests fails ATM — I’ll take a look tomorrow.

Good night
Sascha


signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#836669: caja: Crashes due to theme errors

[G. Heine]

Package: caja
Version: 1.14.2-1
Followup-For: Bug #836669

Dear Maintainer,

I encounter the same problem. Caja doesn't start at all.
The problem arose after the first restart after having upgraded several
packages (see below).

Syslog tells:

caja[3214]: Theme parsing error: mate-applications.css:415:16: not a number
caja[3214]: Theme parsing error: mate-applications.css:415:16: Expected a
string.
caja[3214]: Theme parsing error: other-applications.css:146:13: not a number
caja[3214]: Theme parsing error: other-applications.css:146:13: Expected a
string.
kernel: [   62.004994] caja[2880]: segfault at 7ffdaec61ea8 ip 7f2cf7bec7b6
sp 7ffdaec61ea0 error 6 in libc-2.23.so[7f2cf7bb2000+197000]

The first four lines also appear with mate-menu, mate-system-log or soffice.bin
instead of caja.

Other parts of MATE also segfault:
mate-power-mana[2918]: segfault at 7ffd39a51ff8 ip 7f8b81dfe7b6 sp
7ffd39a51ff0 error 6 in libc-2.23.so[7f8b81dc4000+197000]

Syslog also contains loads of error messages containing
"gtk_widget_size_allocate(): attempt to underallocate..." from wnck-applet and
synaptic which did not appear before yesterday's upgrade.
So it might be that the problem with caja is just a symptom of a defect in some
other package (but I am a layman with respect to programming).

Yesterday's changes on my system:

Commit Log for Tue Sep  6 12:24:16 2016

Die folgenden Pakete wurden aktualisiert:
gir1.2-gtk-3.0 (3.20.9-1) to 3.21.5-3
glib-networking (2.48.2-1) to 2.49.90-1
glib-networking-common (2.48.2-1) to 2.49.90-1
glib-networking-services (2.48.2-1) to 2.49.90-1
gnome-mahjongg (1:3.20.0-2) to 1:3.21.90-1
gnome-sudoku (1:3.20.4-1) to 1:3.21.90-1
gsettings-desktop-schemas (3.20.0-3) to 3.21.4-2
gtk-update-icon-cache (3.20.9-1) to 3.21.5-3
libgail-3-0 (3.20.9-1) to 3.21.5-3
libglib2.0-0 (2.48.1-3) to 2.49.6-1
libglib2.0-0:i386 (2.48.1-3) to 2.49.6-1
libglib2.0-bin (2.48.1-3) to 2.49.6-1
libglib2.0-data (2.48.1-3) to 2.49.6-1
libgtk-3-0 (3.20.9-1) to 3.21.5-3
libgtk-3-bin (3.20.9-1) to 3.21.5-3
libgtk-3-common (3.20.9-1) to 3.21.5-3
libjs-underscore (1.7.0~dfsg-1) to 1.8.3~dfsg-1
libnautilus-extension1a (3.20.1-3) to 3.20.3-1
python-imaging (3.3.0-1) to 3.3.1-1
python-pil (3.3.0-1) to 3.3.1-1
python3-pil (3.3.0-1) to 3.3.1-1
quadrapassel (1:3.20.0-2) to 1:3.21.90-1
sparky-desktop (20160811) to 20160905
swell-foop (1:3.20.0-2) to 1:3.21.91-1

Die folgenden Pakete wurden installiert:
libblkid1:i386 (2.28.1-1)
libmount1:i386 (2.28.1-1)

Updating further packages today didn't solve the problem.

Regards
G. Heine



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

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

Versions of packages caja depends on:
ii  caja-common   1.14.2-1
ii  desktop-file-utils0.23-1
ii  gvfs  1.29.91-1
ii  libatk1.0-0   2.20.0-1
ii  libc6 2.23-5
ii  libcairo-gobject2 1.14.6-1+b1
ii  libcairo2 1.14.6-1+b1
ii  libcaja-extension11.14.2-1
ii  libexempi32.3.0-2
ii  libexif12 0.6.21-2
ii  libgail-3-0   3.21.5-3
ii  libgdk-pixbuf2.0-02.34.0-1
ii  libglib2.0-0  2.49.6-1
ii  libglib2.0-data   2.49.6-1
ii  libgtk-3-03.21.5-3
ii  libice6   2:1.0.9-1+b1
ii  libmate-desktop-2-17  1.14.1-1
ii  libpango-1.0-01.40.2-1
ii  libpangocairo-1.0-0   1.40.2-1
ii  libselinux1   2.5-3
ii  libsm62:1.2.2-1+b1
ii  libstartup-notification0  0.12-4
ii  libunique-3.0-0   3.0.2-2
ii  libx11-6  2:1.6.3-1
ii  libxext6  2:1.3.3-1
ii  libxml2   2.9.4+dfsg1-1+b1
ii  libxrender1   1:0.9.9-2
ii  mate-desktop  1.14.1-1
ii  shared-mime-info  1.6-1

Versions of packages caja recommends:
ii  gvfs-backends  1.29.91-1

Versions of packages caja suggests:
ii  engrampa1.14.1-1
pn  gstreamer1.0-tools  
pn  meld

-- no debconf information

Bug#836509: marked as done (glance: FTBFS in testing (failing tests))

[Debian Bug Tracking System]

Your message dated Wed, 7 Sep 2016 22:20:39 +0200
with message-id <0ab76b03-ea25-d971-437a-d6e9c49dc...@debian.org>
and subject line Re: [PKG-Openstack-devel] Bug#836509: glance: FTBFS in testing 
(failing tests)
has caused the Debian Bug report #836509,
regarding glance: FTBFS in testing (failing tests)
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.)


-- 
836509: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836509
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:glance
Version: 2:12.0.0-4
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
dh build-indep --buildsystem=python_distutils --with python2,sphinxdoc,systemd
   dh_testdir -i -O--buildsystem=python_distutils
   dh_update_autotools_config -i -O--buildsystem=python_distutils
   dh_auto_configure -i -O--buildsystem=python_distutils
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions

[... snipped ...]

glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_non_integer_limit
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_non_integer_limit
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_sort_dir_asc
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_sort_dir_asc
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_sort_dir_bad_value
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_sort_dir_bad_value
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_sort_key_id
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_sort_key_id
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_strip_params_from_filters
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_strip_params_from_filters
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_with_filter_and_limit
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_with_filter_and_limit
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_with_many_filter
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_with_many_filter
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_zero_limit
glance.tests.unit.v2.test_tasks_resource.TestTasksDeserializer.test_index_zero_limit
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_create
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_create ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_create_ensure_expires_at_is_not_returned
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_create_ensure_expires_at_is_not_returned
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_get
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_get ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_get_ensure_expires_at_not_returned
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_get_ensure_expires_at_not_returned
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_index
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_index ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_index_carries_query_parameters
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_index_carries_query_parameters
 ... ok
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_index_next_marker
glance.tests.unit.v2.test_tasks_resource.TestTasksSerializer.test_index_next_marker
 ... ok

==
FAIL: glance.tests.unit.common.test_utils.TestUtils.test_validate_key_cert_key

Bug#836508: marked as done (barbican: FTBFS in testing (failing tests))

[Debian Bug Tracking System]

Your message dated Wed, 7 Sep 2016 22:17:48 +0200
with message-id <9a014c87-b5c1-62d6-d3c2-eb870a0db...@debian.org>
and subject line Re: Bug#836508: barbican: FTBFS in testing (failing tests)
has caused the Debian Bug report #836508,
regarding barbican: FTBFS in testing (failing tests)
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.)


-- 
836508: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836508
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:barbican
Version: 1:2.0.0-5
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
dh build-indep --buildsystem=python_distutils --with python2,systemd,sphinxdoc
   dh_testdir -i -O--buildsystem=python_distutils
   dh_update_autotools_config -i -O--buildsystem=python_distutils
   dh_auto_configure -i -O--buildsystem=python_distutils
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions

[... snipped ...]

barbican.tests.tasks.test_resources.WhenUsingOrderTaskHelper.test_should_handle_success_result_large_statuses_clipped
barbican.tests.tasks.test_resources.WhenUsingOrderTaskHelper.test_should_handle_success_result_large_statuses_clipped
 ... ok
barbican.tests.tasks.test_resources.WhenUsingOrderTaskHelper.test_should_handle_success_result_no_follow_on_needed
barbican.tests.tasks.test_resources.WhenUsingOrderTaskHelper.test_should_handle_success_result_no_follow_on_needed
 ... ok
barbican.tests.tasks.test_resources.WhenUsingOrderTaskHelper.test_should_retrieve_entity
barbican.tests.tasks.test_resources.WhenUsingOrderTaskHelper.test_should_retrieve_entity
 ... ok

==
FAIL: 
barbican.tests.plugin.test_snakeoil_ca.CertManagerTestCase.test_gen_cert_no_file_storage
barbican.tests.plugin.test_snakeoil_ca.CertManagerTestCase.test_gen_cert_no_file_storage
--
_StringException: Empty attachments:
  pythonlogging:''
  stderr
  stdout

Traceback (most recent call last):
  File "barbican/tests/plugin/test_snakeoil_ca.py", line 166, in 
test_gen_cert_no_file_storage
self.verify_sig(cert_enc)
  File "barbican/tests/plugin/test_snakeoil_ca.py", line 157, in verify_sig
crypto.verify(self.ca.cert, sig[1:], der[0], 'sha256')
  File "/usr/lib/python2.7/dist-packages/OpenSSL/crypto.py", line 2605, in 
verify
md_ctx = _ffi.new("EVP_MD_CTX*")
TypeError: cannot instantiate ctype 'EVP_MD_CTX' of unknown size


==
FAIL: 
barbican.tests.plugin.test_snakeoil_ca.CertManagerTestCase.test_gen_cert_with_file_storage
barbican.tests.plugin.test_snakeoil_ca.CertManagerTestCase.test_gen_cert_with_file_storage
--
_StringException: Empty attachments:
  pythonlogging:''
  stderr
  stdout

Traceback (most recent call last):
  File "barbican/tests/plugin/test_snakeoil_ca.py", line 182, in 
test_gen_cert_with_file_storage
self.verify_sig(cert_enc)
  File "barbican/tests/plugin/test_snakeoil_ca.py", line 157, in verify_sig
crypto.verify(self.ca.cert, sig[1:], der[0], 'sha256')
  File "/usr/lib/python2.7/dist-packages/OpenSSL/crypto.py", line 2605, in 
verify
md_ctx = _ffi.new("EVP_MD_CTX*")
TypeError: cannot instantiate ctype 'EVP_MD_CTX' of unknown size


--
Ran 1216 tests in 80.278s

FAILED (failures=2, skipped=4)
debian/rules:20: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:9: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2

Bug#831096: opensurgsim: FTBFS with GCC 6: cstdlib:75:25: fatal error: stdlib.h: No such file or directory

[Paul Novotny]

On Tue, Sep 6, 2016 at 4:06 PM, Andreas Tille  wrote:

[Paul, I wonder whether you realised the problems with opensurgsim]


Thanks for the heads up. Graham's GCC6 patch works for me. I'll get it 
applied upstream.



Hi Graham,

On Thu, Aug 25, 2016 at 02:37:53PM +0200, Graham Inggs wrote:

 Hi Maintainer

 The attached patch fixes the FTBFS with GCC 6.
 I'll open a separate bug for the eigen3 issue and mark it as being 
blocked

 by #835411.


I checked building opensurgsim and while I have not realised any
problems directly hinting to eigen3 I've got:

...
 2 FAILED TESTS

  Start 12: SurgSimPhysicsTest
12/12 Test #12: SurgSimPhysicsTest ...   Passed0.64 
sec


92% tests passed, 1 tests failed out of 12

Total Test time (real) =   8.99 sec

The following tests FAILED:
 11 - SurgSimMathTest (Failed)
Errors while running CTest
Makefile:130: recipe for target 'test' failed
make[1]: *** [test] Error 8
make[1]: Leaving directory 
'/build/opensurgsim-0.6.0/obj-x86_64-linux-gnu'


I am building now to see if I can reproduce this. SurgSimMathTest 
failure might be related to Eigen, but I'll let you know what I find.


-Paul

Bug#836948: getty-run: fails to remove: warning: getty-tty6: unable to open supervise/ok: file does not exist

[Dmitry Bogatov]

control: tags -1 +fixed-in-experimental

> >From the attached log (scroll to the bottom...):
>
>   Removing getty-run (2.1.2-6) ...
>   warning: getty-tty6: unable to open supervise/ok: file does not exist
>   dpkg: error processing package getty-run (--remove):
>subprocess installed pre-removal script returned error exit status 1

Err, getty-run_7 will not upgrade/purge cleanly. Unless service was started
to make it possible to 'force-shutdown' it, the only way would be
mentioned sed command. Sorry.

Processed: Re: Bug#836948: getty-run: fails to remove: warning: getty-tty6: unable to open supervise/ok: file does not exist

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +fixed-in-experimental
Bug #836948 [getty-run] getty-run: fails to remove: warning: getty-tty6: unable 
to open supervise/ok: file does not exist
Ignoring request to alter tags of bug #836948 to the same tags previously set

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

Processed: Re: Bug#836948: getty-run: fails to remove: warning: getty-tty6: unable to open supervise/ok: file does not exist

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +fixed-in-experimental
Bug #836948 [getty-run] getty-run: fails to remove: warning: getty-tty6: unable 
to open supervise/ok: file does not exist
Added tag(s) fixed-in-experimental.

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

Bug#836839: marked as done (fwupdate: FTBFS against efivar 27)

[Debian Bug Tracking System]

Your message dated Wed, 7 Sep 2016 19:39:06 +
with message-id <4a3b906cdf6b4b5f8b0f48c7baf98...@ausx13mpc124.amer.dell.com>
and subject line 
has caused the Debian Bug report #836839,
regarding fwupdate: FTBFS against efivar 27
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.)


-- 
836839: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836839
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fwupdate
Version: 0.5-4
Severity: serious
Justification: fails to build from source

Hi,

fwupdate FTBFS against the new efivar in sid:

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

make[3]: Entering directory '/«PKGBUILDDIR»/linux'
Package efiboot was not found in the pkg-config search path.
Perhaps you should add the directory containing `efiboot.pc'
to the PKG_CONFIG_PATH environment variable
No package 'efiboot' found
gcc -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Wno-unused-result -Wno-unused-function 
-Wsign-compare -Werror=sign-compare -fshort-wchar --std=gnu11 
-DLOCALEDIR=\"/usr/share/locale/\" -D_GNU_SOURCE -DFWUP_EFI_DIR_NAME=\"debian\" 
-I/«PKGBUILDDIR»/linux/include -iquote/«PKGBUILDDIR»/include/  
-I/usr/include/efivar-fPIC -c -o libfwup.o libfwup.c
libfwup.c:12:21: fatal error: efiboot.h: No such file or directory
 #include 
 ^
compilation terminated.


Andreas
--- End Message ---
--- Begin Message ---
Package: fwupdate
Version: 8-1

Fixed in new version of fwupdate.
--- End Message ---

Bug#802021: audacity: non-free files

[Herbert Fortes]

Hi,

>
> Files in "lib-src/libnyquist/nyquist/xlisp" have the following in the
header:
>
> Copyright (c) 1985, by David Michael Betz
> All Rights Reserved
> Permission is granted for unrestricted non-commercial use
>

I tried to send an email to David Michael Betz
but the email returns. I tried to email address:

db...@xlisper.mv.com
davidb...@aol.com

The error:

Technical details of permanent failure: 
DNS Error: 1537381 DNS type 'mx' lookup of xlisper.mv.com responded with code 
NXDOMAIN
Domain name not found: xlisper.mv.com

Google tried to deliver your message, but it was rejected by the server
for the recipient domain aol.com by mailin-02.mx.aol.com. [64.12.91.195].



Regards,
Herbert

Bug#836984: parcimonie unable to call "gpg2" since sid switch to using gpg2 as main "gpg" command

[Gabriel Filion]

Package: parcimonie
Version: 0.10.2-1
Severity: grave
Justification: renders package unusable

Hi there,

Ever since gnupg 2.1 was set to be the main "gpg" command in sid, parcimonie 
has been unable to do its bidding.

>From the process list, we can see the following:

gabster   6219  0.1  1.2 129352 48700 pts/1S+   15:07   0:00  \_ 
/usr/bin/perl /usr/bin/parcimonie --with-dbus
gabster   6220  0.0  0.0  0 0 pts/1Z+   15:07   0:00  \_ 
[gpg] 

and it just hangs there.

If I call the command manually I get the following output:

$ /usr/bin/parcimonie --with-dbus
gpgconf: warning: can not open list file 
/home/gabster/.gnupg/dirmngr_ldapservers.conf: No such file or directory
dirmngr:Key Acquirer:/usr/bin/dirmngr:1:1:
Can't exec "gpg2": No such file or directory at 
/usr/share/perl5/GnuPG/Interface.pm line 301.
exec() error: No such file or directory at /usr/share/perl5/GnuPG/Interface.pm 
line 301.
No public key was found. at /usr/share/perl5/App/Parcimonie/Daemon.pm line 420.

So apparently it's trying to call a gpg2 binary which doesn't exist anymore:

$ find /usr/bin/ -name gpg\*
/usr/bin/gpgconf
/usr/bin/gpgsplit
/usr/bin/gpgsm
/usr/bin/gpg
/usr/bin/gpg-connect-agent
/usr/bin/gpg-agent
/usr/bin/gpgparsemail
/usr/bin/gpg-zip
/usr/bin/gpgv
/usr/bin/gpg1

So I guess we either need to call "gpg" directly or somehow get the "gpg2"
alias to come back. Or maybe there's an even better solution that I'm not
thinking about since I don't know much about the code base and used libraries.

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

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

Versions of packages parcimonie depends on:
ii  libclone-perl0.38-2
ii  libconfig-general-perl   2.63-1
ii  libfile-homedir-perl 1.00-1
ii  libfile-which-perl   1.21-1
ii  libgnupg-interface-perl  0.52-3
ii  libipc-system-simple-perl1.25-3
ii  liblist-moreutils-perl   0.416-1
ii  libmoo-perl  2.002004-1
ii  libmoox-late-perl0.015-2
ii  libmoox-options-perl 4.022-2
ii  libnamespace-clean-perl  0.27-1
ii  libpath-tiny-perl0.094-1
ii  libtime-duration-parse-perl  0.13-1
ii  libtry-tiny-perl 0.27-1
ii  libtype-tiny-perl1.05-1
ii  libtypes-path-tiny-perl  0.005-1
ii  perl 5.22.2-4
ii  torsocks 2.1.0-2

Versions of packages parcimonie recommends:
ii  gnupg-curl  1.4.20-6
ii  libglib-perl3:1.321-1
ii  libgtk3-perl0.028-1
ii  liblocale-gettext-perl  1.07-3
ii  libnet-dbus-glib-perl   0.33.0-2
ii  libnet-dbus-perl1.1.0-4
ii  libpango-perl   1.227-1
ii  libtime-duration-perl   1.20-1
ii  tor 0.2.8.7-1

parcimonie suggests no packages.

-- no debconf information

Processed: your mail

[Debian Bug Tracking System]

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

> found 836979 0.7.1-1
Bug #836979 [episoder] episoder: non-DFSG files found
Marked as found in versions episoder/0.7.1-1.
> found 836979 0.7.1-2
Bug #836979 [episoder] episoder: non-DFSG files found
Marked as found in versions episoder/0.7.1-2.
>
End of message, stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> severity 836971 important
Bug #836971 [src:libcmrt] libcmrt: FTBFS: config.status: error: cannot find 
input file: `pkgconfig/cmrt.pc.in'
Severity set to 'important' from 'serious'
> merge 836879 836971
Bug #836879 [src:libcmrt] libcmrt: FTBFS: missing pkgconfig/cmrt.pc.in
Bug #836971 [src:libcmrt] libcmrt: FTBFS: config.status: error: cannot find 
input file: `pkgconfig/cmrt.pc.in'
Merged 836879 836971
> thanks
Stopping processing here.

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