Bug#835662: libreoffice: When scrolling a sizeable document, lines of text do not appear

2016-08-28 Thread Rene Engelhard
tag 835662 + moreinfo
thanks

Hi,

On Sun, Aug 28, 2016 at 04:43:02PM +1000, Vince Barwinski wrote:
> When I try to scroll or do a word search on a sizeable document of say 50 or
> more pages, lines of text do not appear making the proper editing of the
> document practically impossible. In smaller documents like say 8 pages, this 
> is
> not a problem, but has made itself felt in two documents of mine which are 84
> and 524 pages respectively. The problem seems to have started with version
> 5.1.5 but is still manifesting itself in version 5.2.0-2. Version 5.1.4 I had
> no problems.

Then you should have it reported back then...

Example document? Of course I don't have documents this big to even attempt
to reproduce it :)

Also interesting would be to know what rendering of the UI you use? gtk? gtk3?

dpkg -l libreoffice-gtk2 libreoffice-gtk3? If none, does it help to install
one of them/matching what your desktop uses?

>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> 
> I ended up installing Apache Open Office as this was my only option for me to

Helpful for debugging. NOT.

Did you also report it upstream or not? It'd be nice if you can do, I'd
only forward it anyway, and playing proxy from here to there is cumbersome,
epecially if they want/need more info..

Regards,

Rene



Bug#835562: (baloo-kf5: baloo stopping indexing after ~5000 files)

2016-08-28 Thread Hans
Hi Maximiliano,

please take a look at the last strace output of baloo_file to see, which files 
get opened by baloo:

strace -e trace=open baloo_file_extractor


open("/usr/lib/i386-linux-gnu/qt5/plugins/kf5/kfilemetadata/
kfilemetadata_taglibextractor.so", O_RDONLY|O_CLOEXEC) = 7
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 7
open("/usr/lib/i386-linux-gnu/libtag.so.1", O_RDONLY|O_CLOEXEC) = 7
open("/etc/localtime", O_RDONLY|O_CLOEXEC) = 7
open("/home/ullhan63/.config/kdeglobals", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 7
open("/home/ullhan63/.config/baloofilerc", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 7
open("/etc/udev/udev.conf", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 7
open("/etc/fstab", O_RDONLY|O_CLOEXEC)  = 10
open("/etc/mtab", O_RDONLY|O_CLOEXEC)   = 10
open("/etc/mtab", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 11
open("/home/ullhan63/.config/kdeglobals", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 12
open("/home/ullhan63/.config/baloofilerc", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 12
open("/etc/udev/udev.conf", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 12
open("/sys/devices/pci:00/:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/
block/sda/sda9/uevent", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 12
open("/run/udev/data/b8:9", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 12
open("/usr/lib/i386-linux-gnu/qt5/plugins/kf5/org.kde.kidletime.platforms", 
O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|O_CLOEXEC) = 12
open("/usr/lib/i386-linux-gnu/qt5/plugins/kf5/org.kde.kidletime.platforms/
KF5IdleTimeKWaylandPlugin.so", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 12
open("/usr/lib/i386-linux-gnu/qt5/plugins/kf5/org.kde.kidletime.platforms/
KF5IdleTimeKWinWaylandPrivatePlugin.so", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 12
open("/usr/lib/i386-linux-gnu/qt5/plugins/kf5/org.kde.kidletime.platforms/
KF5IdleTimeXcbPlugin0.so", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 12
open("/usr/lib/i386-linux-gnu/qt5/plugins/kf5/org.kde.kidletime.platforms/
KF5IdleTimeXcbPlugin0.so", O_RDONLY|O_CLOEXEC) = 12
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 12
open("/usr/lib/i386-linux-gnu/libQt5X11Extras.so.5", O_RDONLY|O_CLOEXEC) = 12
open("/dev/tty", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 12
XSync seems available and ready
XSync Inited
Supported, init completed
Created alarm 20971521
Cstrace: Process 21858 detached


Interesting is this line from above:

open("/sys/devices/pci:00/:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/
block/sda/sda9/uevent", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 12

As you see, baloo wants to open a file from sda9, which IMO is strange. /dev/
sda9 does not exist on my system. Not quite correct, of course it exists, but 
as it is encrypted, the device is now /dev/mapper/usr.

Maybe it has nothing to do with it, wanted just to mention it. 

The alarm number which is shown, changes at every run.

Don't know if this helps, but I think, any information could be valuable.

Best

Hans
 



Bug#835663: spykeviewer: Please migrate to pyQT5

2016-08-28 Thread picca
Package: spykeviewer
Version: 0.4.4-1
Severity: important

Dear Maintainer,

I prepared the new qtconsole and spyder package which are available in 
experimental

When I try to start spydeviewer with these new versions, I get this

$ spykeviewer 
/usr/lib/python2.7/dist-packages/IPython/qt.py:13: ShimWarning: The 
`IPython.qt` package has been deprecated. You should import from qtconsole 
instead.
  "You should import from qtconsole instead.", ShimWarning)
Traceback (most recent call last):
  File "/usr/bin/spykeviewer", line 9, in 
load_entry_point('spykeviewer==0.4.4', 'gui_scripts', 'spykeviewer')()
  File "/usr/lib/python2.7/dist-packages/spykeviewer/start.py", line 43, in main
ui = MainWindowNeo(splash=splash)
  File "/usr/lib/python2.7/dist-packages/spykeviewer/ui/main_window_neo.py", 
line 40, in __init__
super(MainWindowNeo, self).__init__(parent, splash)
  File "/usr/lib/python2.7/dist-packages/spykeviewer/ui/main_window.py", line 
120, in __init__
self.init_python()
  File "/usr/lib/python2.7/dist-packages/spykeviewer/ui/main_window.py", line 
497, in init_python
ns = self.get_console_objects()
  File "/usr/lib/python2.7/dist-packages/spykeviewer/ui/main_window_neo.py", 
line 85, in get_console_objects
d = super(MainWindowNeo, self).get_console_objects()
  File "/usr/lib/python2.7/dist-packages/spykeviewer/ui/main_window.py", line 
433, in get_console_objects
import matplotlib.pyplot as plt
  File "/usr/lib/python2.7/dist-packages/matplotlib/pyplot.py", line 109, in 

_backend_selection()
  File "/usr/lib/python2.7/dist-packages/matplotlib/pyplot.py", line 91, in 
_backend_selection
import PyQt5.QtWidgets
  File "/usr/lib/python2.7/dist-packages/qtconsole/qt_loaders.py", line 55, in 
load_module
""" % (fullname, loaded_api()))
ImportError: 
Importing PyQt5 disabled by QtConsole, which has
already imported an incompatible Qt Binding: pyqt

The fact is that pyqt which is a dependency of spyder 3.x, use pyQT5 by default.
could you fix spykeviwer and migrate to pyQT5.

nevertheless if you force pyQT4

$ QT_API=pyqt spykeviewer   
  
/usr/lib/python2.7/dist-packages/IPython/qt.py:13: ShimWarning: The 
`IPython.qt` package has been deprecated. You should import from qtconsole 
instead.
  "You should import from qtconsole instead.", ShimWarning)

You get this warning and the application does not start.

so the package should be adapted to the new qtconsole package.

Cheers

Frederic

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

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

Versions of packages spykeviewer depends on:
ii  python 2.7.11-2
ii  python-guidata 1.7.4-1
ii  python-guiqwt  3.0.2-2
ii  python-matplotlib  1.5.2~rc2-1
ii  python-neo 0.3.3-2
ii  python-nose1.3.7-2
ii  python-scipy   0.17.1-1
ii  python-sphinx  1.4.6-1
ii  python-spyderlib   3.0.0~b5+dfsg1-1
ii  python-spykeutils  0.4.3-1
ii  python-tables  3.2.2-3

Versions of packages spykeviewer recommends:
ii  ipython-qtconsole  4.2.1-1
ii  libjs-jquery   1.12.4-1
ii  libjs-underscore   1.7.0~dfsg-1

spykeviewer suggests no packages.

-- no debconf information



Bug#835342: curl or git clone commands throws "gnutls_handshake() failed" on https targets

2016-08-28 Thread Stefan Bühler
Hi Marcelo,

On Fri, 26 Aug 2016 10:30:51 -0400 "marcelomen...@gmail.com"
 wrote:
> 2016-08-25 13:25 GMT-04:00 Andreas Metzler :
> > On 2016-08-24 "marcelomen...@gmail.com" 
> > wrote:
> >> Package: libgnutls30
> >> Version: 3.5.3-2
> >> Severity: important
> >> Tags: upstream
> >
> >> Dear Maintainer,
> >
> >> Trying to git clone a github repo using libgnutls30 3.5.3-2 throw
> >> the following error:
> >
> >> fatal: unable to access 'https://github.com/xxx/yyy/':
> >> gnutls_handshake() failed: Public key signature verification has
> >> failed.
> >
> >> Same happens for curl:
> >
> >> curl https://duckduckgo.com
> >> curl: (35) gnutls_handshake() failed: Public key signature
> >> verification has failed.
> >
> > Hello,
> > Are you able to reproduce either of these errors with gnutls-cli?
> 
> First, let me say I'm behind a proxy server.

Does the proxy happen to intercept TLS, i.e. is it a local CA and
creates certificates on demand, which might fail the verification?

Perhaps you could get a pcap with tcpdump of the connection(s) from
curl to the proxy?

tcpdump -i eno1 -w curl-to-proxy.pcap 'host  and port 
'

> Both versions of gnutls-bin (3.5.3-3 and the old 3.5.2-3) have the
> same behavior:
> 
> gnutls-cli -V --port 443 duckduckgo.com
> Processed 173 CA certificate(s).
> Resolving 'duckduckgo.com:443'...
> Connecting to '107.21.1.61:443'...
> Connecting to '184.72.106.52:443'...
> Connecting to '184.72.115.86:443'...
> 
> and stay there for some quit some time until I ctrl+c

I don't think gnutls-cli supports a proxy directly; you'd probably
have to use some LD_PRELOAD proxy wrapper (e.g. tsocks or similar).



Bug#835658: RFS: backbone/1.3.3+ds-1

2016-08-28 Thread Gianfranco Costamagna
control: owner -1 !
control: tags -1 moreinfo


(ccing people who expressed interest in this update)
>   I am looking for a sponsor for the package "backbone"


here we are, but I have some questions/issues:

1) why did you drop so much build-dependencies?
2) missing copyrights/licenses:
 * @license RequireJS 2.1.9 Copyright (c) 2010-2012, The Dojo Foundation All 
Rights Reserved.
 * Available via the MIT or new BSD license.

(c) 2009-2015 Jeremy Ashkenas, DocumentCloud and Investigative Reporters & 
Editors
and maybe more
3) Did you get in touch with the maintainer for this upload?
4) please tag the two bugs as pending, to avoid double work from other people
(e.g. zigo who expressed)
5) I'm not sure Jonas will like to move away from cdbs...
6) 
-Author: Jonas Smedegaard 
+Author: Julien Puydt

I would use both people as authors :)

7) depends/buil-depends.
typo

8) 
Bump standards-version.
To which version?

9)

"This source package uses CDBS"
I would change that :)

10)
why is this a ds repack? it seems to be not written in README.source
or whatever

11) compat level is still 8 :)

we should be mostly complete as a preliminary review.
I have to admit, the cdbs rules file was a little bit complicate for a 3 
installed
js files library :)
but I think we might go for experimental, wait some more testing for the two+ 
people needing
it and then go for unstable.
Does it sounds good as a plan



Bug#835507: Please clarify that sysvinit support decision is not going to expire

2016-08-28 Thread Christian Seiler
On 08/28/2016 08:37 AM, Bart Schouten wrote:
> Sam Hartman schreef op 28-08-2016 1:37:
>> Similarly, if the community of people who care about sysvinit  is 
>> unwilling to spend the time keeping it working, eventually sysvinit
>> as a whole will be unmaintained and buggy.
> 
> True, but I don't think those conditions are there.

Not yet, but a lot of sysvinit-related stuff still hasn't been
adopted after being orphaned.

> I mean that the statements:
> 
> a) the scripts need (urgent) maintaining
> 
> and
> 
> b) in the context of the actual maintaining they do need, the help 
> that is necessary isn't there.
> 
> Are not true.

I would agree that in this specific case, a) is not true (there's
no apparent problem with them that wasn't already there in Wheezy),
but I'm honestly not at all sure about b).

To bring out my pet example: with sysvinit systems, in Jessie it's
not possible to have /usr on NFS anymore. The reason is that mount.nfs
is now linked against a library in /usr. I reported the bug [1] before
the release of Jessie (and I only found it because I was testing stuff
with sysvinit, I don't use it regularly at all). But nothing happened.
Then when the whole monster /usr-merge thread happened on debian-devel
half a year ago, I brought up that bug again, and nobody seemed to
care either.

With systemd this bug doesn't occur, because on systemd systems the
/usr partition is mounted in the initrd - so you can indeed boot
/usr on nfs with Jessie - but only with systemd.

To be fair: the mounting of /usr in initramfs now happens regardless
of init system also in Stretch, so the bug will now only appear if
you don't use an initramfs. But it was not sysvinit people who made
that work, but Ben Hutchings who NMU'd initscripts. [2]

Actually, the only people who appear to be improving sysvinit support
in Debian at the moment appear to be systemd users. And the only
thing I hear from sysvinit users are complaints.

> I think the "maintainership requirement" of those scripts are 
> currently being exaggerated,

In this specific case? Probably. When the thread that started this TC
bug popped up on debian-devel, I was on your side: those scripts
shouldn't have been removed.

Heck, I even wrote init scripts for something I packaged recently.
(Admittedly, that was a simple daemon and the init script is trivial,
see [3].)

However, I've been working on something for the last couple of months
(on and off) to write some code to make stuff work on sysvinit for
one package I maintain, which I wouldn't need to do if I just wanted
to support systemd. Currently there's a huge workaround in the package
that is awful in every regard. And I really want to get rid of the
workaround, because it is detrimental to users in other ways (and the
workaround also affects systemd users), and do it properly.

But when I read stuff such as this: 

> ... warehouse of troubles that need a million hours of employment 
> each year to keep it going ...
> - you will hate the day when you discover you've been scammed ...

Or, when other people constantly and irrationally bring up
libsystemd0 again and again (see the current debian-devel thread),
then sorry, these kinds of comments make me lose any motivation in
still working on helping people out with sysvinit. It's becoming
more and more appealing to me to just say "screw sysvinit users",
I don't care anymore. I'm not there yet, but I suspect that I'm not
the only one who feels that way, so please, continue with this kind
of rhetoric, and see where you'll be at in a few years.

> Anyone writing an actual SysV init script would have thought of those
> things. That person would have felt responsible for it, because no
> one else would do it for you. That person would have built more
> intelligence into the startup script.

No, sorry, that's simply patently untrue. There are some good init
scripts out there, but the vast majority of them are just plain
horrible. They kind of work, but they make a lot of assumptions
that break in a lot of corner cases. And writing good init scripts
is _really_ hard, because shell programming is awful. (Useful, but
awful.)

Heck, even the skeleton Debian init script is completely useless
for use in a Pacemaker/HA environment - because start/stop will
_always_ return exit code 0, regardless of whether it worked or
not. (Only status returns different exit codes.) With sysvinit I
have _always_ had to patch init scripts to return proper error
codes when I wanted to use them in a HA environment. (And I've
done that since Squeeze, where there was no systemd.) This
violates LSB btw. (No, I didn't file a bug against the initscripts
package, let alone an MBF against all daemons with this problems,
not even before systemd was even a thing during Squeeze times,
because it was already very clear to me from just looking at the
bug list that nobody seemed to care about maintaining the package
properly, and I'd just be wasting my time.)

So yeah, for me sysvinit scripts are def

Bug#835664: libip[46]tc-dev are missing a dependency on libip[46]tc0

2016-08-28 Thread Martin Pitt
Package: libip4tc-dev
Version: 1.6.0-3
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu ubuntu-patch yakkety

Hello,

the new libip[46]tc-dev do not depend on their corresponding library
packages libip[46]tc0. They only depend on libiptc0, which in Debian
depends on libip[46]tc0, but not in Ubuntu where packages get built
with --as-needed to avoid unneccessary dependencies.

But also Debian's package should not rely on that transitive
dependency. Attached patch fixes this.

Note that it is dubious that libip4tc-dev has a hardcoded dependency
on libiptc0 -- it should *only* depend on libip4tc0, and if that lib
really needs libiptc0 as well this should come via ${shlibs:Depends}.
However, I'm not familiar with how these libraries are split so the
patch leaves that dependency for now. But if possible it would be
cleaner to drop it.

Thanks for considering,

Martin

-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)



Bug#835636: util-linux: home wanted for "sizetty"

2016-08-28 Thread Andreas Henriksson
Hello Adam Borowski.

On Sat, Aug 27, 2016 at 09:56:30PM +0200, Adam Borowski wrote:
> Package: util-linux
> Version: 2.28.1-1
> Severity: wishlist
> 
> 
> Hi!
> Please advise where to put the attached program.  It fixes the problem when
> you connect to a serial console and your terminal size is not exactly 80x24.
[...]

Please contact util-linux upstream to discuss potential incorporation
or other alternative solutions.

Regards,
Andreas Henriksson



Bug#835666: [htop] Mouse wheel scrolling does not work

2016-08-28 Thread Petr Voralek
Package: htop
Version: 2.0.2-1
Severity: normal

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

  Starting from version 2 of htop, scroll using the mouse wheel should work:

I Quote /usr/share/doc/htop/changelog.gz
 -(Cut)-
What's new in version 2.0.0
.
* Support for NCurses 6 ABI, including mouse wheel support
.
 -(Cut)-


  Unfortunately it does not work (in Konsole nor in Virtual Console
((CTRL)+ALT+F*)...).

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

Debian Release: stretch/sid
  500 testing repos.fds-team.de
  500 testing ftp.cz.debian.org
  500 testing deb-multimedia.org
  500 stable  dl.google.com
  100 unstablerepos.fds-team.de
  100 unstableftp.cz.debian.org
  100 unstabledeb-multimedia.org
1 experimentalftp.cz.debian.org
1 experimentaldeb-multimedia.org

--- Package information. ---
Depends   (Version) | Installed
===-+-===
libc6 (>= 2.15) |
libncursesw5 (>= 6) |
libtinfo5(>= 6) |


Package's Recommends field is empty.

Suggests  (Version) | Installed
===-+-===
lsof| 4.89+dfsg-0.1
strace  | 4.12-3
-- 
Petr Voralek(JabberID: na...@jabber.cz)



signature.asc
Description: OpenPGP digital signature


Bug#835507: Please clarify that sysvinit support decision is not going to expire

2016-08-28 Thread Bart Schouten

Christian Seiler schreef op 28-08-2016 10:07:


... warehouse of troubles that need a million hours of employment
each year to keep it going ...
- you will hate the day when you discover you've been scammed ...


Or, when other people constantly and irrationally bring up
libsystemd0 again and again (see the current debian-devel thread),
then sorry, these kinds of comments make me lose any motivation in
still working on helping people out with sysvinit. It's becoming
more and more appealing to me to just say "screw sysvinit users",
I don't care anymore. I'm not there yet, but I suspect that I'm not
the only one who feels that way, so please, continue with this kind
of rhetoric, and see where you'll be at in a few years.


Actually that is not such a bad thing; I find that if the motivation 
doesn't come natural, then there is a good reason to stop doing it; and 
just doing it because people please you or it pleases people, is not a 
very good reason after all either.


I know the language is exaggerated but it is not actually all that 
inaccurate.


I simply do not trust people who make a livelihood out of having 
problems, that's all.


I do not trust policemen to solve crime, psychiatrists to cure mental 
illness, teachers to make people independent, governments to liberate 
people and systemd people to have you have a problem-free existence in 
your system ;-).


I am sorry but seeing that most everyone who works on Linux works for 
one big company, and more problems means more employment, and maybe that 
is a rad and unfair way to say it, or to say it here, where such people 
may not be the most people in charge.


And I like SystemD's model, and there is a reason I am using it and it 
took me at least a year for me to get to the point where I could write 
my own service files or knew enough about it to start hacking the system 
(only the init system).


It's not just Linux, or not at all Linux, but the world is comprised of 
people who make a living by having problems, and more problems is more 
money.


And sometimes I feel as though Linux is the way of taking something 
simple and creating a difficult solution for it, and then the rest of 
your days you are dealing with the difficult solution instead of with 
the simple problem.





No, sorry, that's simply patently untrue. There are some good init
scripts out there, but the vast majority of them are just plain
horrible. They kind of work, but they make a lot of assumptions
that break in a lot of corner cases. And writing good init scripts
is _really_ hard, because shell programming is awful. (Useful, but
awful.)


Alright, corrected.

But "High Availability" tells to me something that would need more 
advanced systems to control it. I'm not saying SystemD is all bad, not 
at all.


It is clear that SysV is rudimentary and broken but it was that way for 
a long time. But the power is that you can write your own scripts and it 
just doesn't take all that long to find out how to do something or 
effect a change since you can just read the code and it is just regular 
Bash code mostly.


What I mean is that I am not an avid opponent of Bash scripting and I 
quite enjoy it. What I mean is that I am an avid proponent of it ;-). 
And so for me something being just "script" is a powerhouse. I don't 
need to acquaint myself with the workings and peculiarities of some init 
system before I can affect it. They are generic skills. I mean that I 
prefer to have rudimentary, simple, scriptful skills that are as basic 
as they can possibly get because basic skills are better building blocks 
for larger things, than bigger things and more advanced skills.


I mean that if you keep things simple and elementary, you create a more 
powerful house, and this has long since been the philosophy of the Unix 
world.


I mean that for me it is a personal thing perhaps that I can much easier 
work with stuff that requires just programming skills of some sort, 
rather than acquaintance and knowledge of a particular system. I mean 
that I can work better with that because I already have the skills and I 
do not need to acquire them.




So yeah, for me sysvinit scripts are definitely no fallback. From
personal experience I am by _far_ more confident in maintainers
getting systemd services right than in them getting init scripts
right. (Obviously that doesn't mean that people don't get service
files wrong - of course that also happens from time to time.)


I know SysV is rudimentary and not very advanced.

It's just that to me it is that candle that will still work when the 
electricity goes down ;-).


*Shrugs*.

Sorry for the language here at times, I know I exaggerate. The 
exaggerating stuff is often easier to say than the non-exaggerated 
stuff. Apologies.


Bart.



Bug#835185: mysql-workbench: Segfault when opening connection

2016-08-28 Thread Paul Wise
Followup-For: Bug #835185
Package: mysql-workbench
Version: 6.3.4+dfsg-3+b5
Control: severity -1 serious
Control: usertags -1 + bittenby crash

On Tue, 23 Aug 2016 07:41:42 -0400 Richard Ayotte wrote:

> The application segfaults when a connection is clicked to be opened.

I have the same issue, which prevents me from using mysql-workbench.

This is a serious issue since it makes mysql-workbench not work.

I get following backtrace for the crash:

$ env WB_DEBUG=gdb mysql-workbench
GNU gdb (Debian 7.11.1-2) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib/mysql-workbench/mysql-workbench-bin...Reading 
symbols from 
/usr/lib/debug/.build-id/8d/8e59c0d2ebc57e1e176de978ef8382cae905e1.debug...done.
done.
(gdb) set height 0
(gdb) run
Starting program: /usr/lib/mysql-workbench/mysql-workbench-bin 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffce59c700 (LWP 5678)]
Ready.

[New Thread 0x7fffc8523700 (LWP 5687)]
[New Thread 0x7fffc7d22700 (LWP 5688)]
[New Thread 0x7fffc72b4700 (LWP 5691)]
Thread started
[New Thread 0x7fffc5f5c700 (LWP 5692)]
[New Thread 0x7fffc575b700 (LWP 5693)]
[Thread 0x7fffc575b700 (LWP 5693) exited]
[New Thread 0x7fffc575b700 (LWP 5694)]
[New Thread 0x7fffc4dd9700 (LWP 5695)]
[New Thread 0x7fffc45d8700 (LWP 5696)]
[Thread 0x7fffc4dd9700 (LWP 5695) exited]
[New Thread 0x7fffc3d2a700 (LWP 5697)]
[New Thread 0x7fffc34be700 (LWP 5698)]

Thread 11 "GRTDispatcher" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffc3d2a700 (LWP 5697)]
SqlEditorTreeController::fetch_schema_list[abi:cxx11]() (this=0x15081b0)
at 
/build/mysql-workbench-qy33lx/mysql-workbench-6.3.4+dfsg/backend/wbprivate/sqlide/wb_sql_editor_tree_controller.cpp:429
429 
/build/mysql-workbench-qy33lx/mysql-workbench-6.3.4+dfsg/backend/wbprivate/sqlide/wb_sql_editor_tree_controller.cpp:
 No such file or directory.
(gdb) bt
#0  0x77420888 in 
SqlEditorTreeController::fetch_schema_list[abi:cxx11]() (this=0x15081b0)
at 
/build/mysql-workbench-qy33lx/mysql-workbench-6.3.4+dfsg/backend/wbprivate/sqlide/wb_sql_editor_tree_controller.cpp:429
#1  0x7741ef34 in 
SqlEditorTreeController::do_refresh_schema_tree_safe(grt::GRT*, 
boost::weak_ptr) (this=0x15081b0, grt=, 
self_ptr=...)
at 
/build/mysql-workbench-qy33lx/mysql-workbench-6.3.4+dfsg/backend/wbprivate/sqlide/wb_sql_editor_tree_controller.cpp:2597
#2  0x77439678 in 
boost::detail::function::function_obj_invoker1,
 boost::_mfi::mf2, SqlEditorTreeController, 
grt::GRT*, boost::weak_ptr >, 
boost::_bi::list3, boost::arg<1>, 
boost::_bi::value > > >, 
grt::Ref, 
grt::GRT*>::invoke(boost::detail::function::function_buffer&, grt::GRT*) 
(a2=..., a1=, p=, this=)
at /usr/include/boost/bind/mem_fn_template.hpp:280
#3  0x77439678 in 
boost::detail::function::function_obj_invoker1,
 boost::_mfi::mf2, SqlEditorTreeController, 
grt::GRT*, boost::weak_ptr >, 
boost::_bi::list3, boost::arg<1>, 
boost::_bi::value > > >, 
grt::Ref, 
grt::GRT*>::invoke(boost::detail::function::function_buffer&, grt::GRT*) 
(a=, f=..., this=)
at /usr/include/boost/bind/bind.hpp:382
#4  0x77439678 in 
boost::detail::function::function_obj_invoker1,
 boost::_mfi::mf2, SqlEditorTreeController, 
grt::GRT*, boost::weak_ptr >, 
boost::_bi::list3, boost::arg<1>, 
boost::_bi::value > > >, 
grt::Ref, 
grt::GRT*>::invoke(boost::detail::function::function_buffer&, grt::GRT*) 
(a1=, this=)
at /usr/include/boost/bind/bind.hpp:905
#5  0x77439678 in 
boost::detail::function::function_obj_invoker1,
 boost::_mfi::mf2, SqlEditorTreeController, 
grt::GRT*, boost::weak_ptr >, 
boost::_bi::list3, boost::arg<1>, 
boost::_bi::value > > >, 
grt::Ref, 
grt::GRT*>::invoke(boost::detail::function::function_buffer&, grt::GRT*) 
(function_obj_ptr=..., a0=)
at /usr/include/boost/function/function_template.hpp:138
#6  0x764b3734 in 
boost::detail::function::function_obj_invoker1
 (grt::GRT*)>, grt::ValueRef, 
grt::GRT*>::invoke(boost::detail::function::function_buffer&, grt::GRT*) 
(a0=, this=) at 
/usr/include/boost/function/function_template.hpp:773
#7  0x764b3734 in 
boost::detail::function::function_obj_invoker1
 (grt::GRT*)>, grt::ValueRef, 
grt::GRT*>::invoke(boost::detail::functio

Bug#835549: boinc: FTBFS with openssl 1.1.0

2016-08-28 Thread Christian Beer
Gianfranco: Let me know if I should backport the openssl changes into
the 7.4 upstream branch.

Regards
Christian



Bug#646839: dcut: use existing defaults for GnuPG key

2016-08-28 Thread Ben Finney
Control: retitle -1 dcut: use existing defaults for GnuPG key
Control: severity -1 wishlist

On 27-Oct-2011, Mathieu Malaterre wrote:

> dcut does not pick the correct gpg key.

As you point out, ‘dcut’ has an explicit command-line option to
specify the desired key ID. So I'm demoting this report to “wishlist”
severity.

> I have exported DEBSIGN_KEYID and defined my 'default-key' in my
> ~/.gnupg/gpg.conf However dcut still picks the first available gpg
> key (my old key)

I have retitled this bug report to reflect the apparent request, does
this match your intention?

-- 
 \ “I wish I had a dollar for every time I spent a dollar, because |
  `\   then, yahoo!, I'd have all my money back.” —Jack Handey |
_o__)  |
Ben Finney 


signature.asc
Description: PGP signature


Bug#835667: d-shlibs: FTBFS in testing (broken by new shellcheck)

2016-08-28 Thread Santiago Vila
Package: src:d-shlibs
Version: 0.75
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
test -x debian/rules
mkdir -p "."
CDBS WARNING:  copyright-check disabled - licensecheck (from devscripts 
package) is missing.
make: licensecheck: Command not found

Scanning upstream source for new/changed copyright notices...

set -e; LC_ALL=C.UTF-8 licensecheck --check '.*' --recursive --copyright 
--ignore '^(debian/(changelog|copyright(|_hints|_newhints)))$' --lines 9 * 
| /usr/lib/cdbs/licensecheck2dep5 > debian/copyright_newhints
/bin/sh: 1: licensecheck: not found
0 combinations of copyright and licensing found.
No new copyright notices found - assuming no news is good news...
touch debian/stamp-copyright-check
touch debian/stamp-upstream-cruft
/usr/bin/make -C . CFLAGS="-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security" CXXFLAGS="-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security" CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" 
LDFLAGS="-Wl,-z,relro" 
make[1]: Entering directory '/<>'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory '/<>'
touch debian/stamp-makefile-build
/usr/bin/make -C . CFLAGS="-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security" CXXFLAGS="-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security" CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" 
LDFLAGS="-Wl,-z,relro" check
make[1]: Entering directory '/<>'
bash -n d-shlibmove
bash -n d-devlibdeps
shellcheck d-shlibmove

In d-shlibmove line 238:
while read A B; do
  ^-- SC2162: read without -r will mangle backslashes.


In d-shlibmove line 245:
while read A B; do
  ^-- SC2162: read without -r will mangle backslashes.

Makefile:8: recipe for target 'check' failed
make[1]: *** [check] Error 1
make[1]: Leaving directory '/<>'
/usr/share/cdbs/1/class/makefile.mk:113: recipe for target 
'debian/stamp-makefile-check' failed
make: *** [debian/stamp-makefile-check] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


This used to build ok in testing so the new shellcheck which
has just migrated to testing may be related to this.

Thanks.



Bug#835549: boinc: FTBFS with openssl 1.1.0

2016-08-28 Thread Gianfranco Costamagna
control: forcemerge -1 835550

control: fixed -1 7.6.33+dfsg-1exp2

Hi Christian,

>Gianfranco: Let me know if I should backport the openssl changes into
>the 7.4 upstream branch.


not really needed, that branch is dead in Debian :)

(and the new openssl won't reach stable)
so, since experimental is fixed, I'll fix unstable once the new openssl is 
uploaded
(or as soon as a new boinc release is out)

thanks,

G.



Bug#835668: pdal: FTBFS in testing (H5Cpp.h: No such file or directory)

2016-08-28 Thread Santiago Vila
Package: src:pdal
Version: 1.2.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
dh build-indep --with python2,pkgkde_symbolshelper,sphinxdoc --parallel
   dh_testdir -i -O--parallel
   dh_update_autotools_config -i -O--parallel
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
# Don't use outdated autotools helper files
mv `ls -d vendor/gtest-*`/build-aux/config.guess debian/gtest.config.guess
mv `ls -d vendor/gtest-*`/build-aux/config.sub   debian/gtest.config.sub
cp /usr/share/misc/config.guess `ls -d vendor/gtest-*`/build-aux/config.guess
cp /usr/share/misc/config.sub   `ls -d vendor/gtest-*`/build-aux/config.sub
dh_auto_configure -- -DCMAKE_BUILD_TYPE=RelWithDebInfo \
 -DCMAKE_INSTALL_LIBDIR=lib \

[... snipped ...]

cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cmake -E 
cmake_symlink_library ../lib/libpdal_base.so.3.0.0 ../lib/libpdal_base.so.2 
../lib/libpdal_base.so
make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
[ 25%] Built target pdal_base
make -f 
plugins/greyhound/CMakeFiles/pdal_plugin_reader_greyhound.dir/build.make 
plugins/greyhound/CMakeFiles/pdal_plugin_reader_greyhound.dir/depend
make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> /<>/plugins/greyhound 
/<>/obj-x86_64-linux-gnu 
/<>/obj-x86_64-linux-gnu/plugins/greyhound 
/<>/obj-x86_64-linux-gnu/plugins/greyhound/CMakeFiles/pdal_plugin_reader_greyhound.dir/DependInfo.cmake
 --color=
Scanning dependencies of target pdal_plugin_reader_greyhound
make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make -f 
plugins/greyhound/CMakeFiles/pdal_plugin_reader_greyhound.dir/build.make 
plugins/greyhound/CMakeFiles/pdal_plugin_reader_greyhound.dir/build
make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
[ 25%] Building CXX object 
plugins/greyhound/CMakeFiles/pdal_plugin_reader_greyhound.dir/io/CompressionStream.cpp.o
cd /<>/obj-x86_64-linux-gnu/plugins/greyhound && /usr/bin/c++   
-DHAVE_JSONCPP=1 -DHAVE_WEBSOCKETPP=1 -D_WEBSOCKETPP_CPP11_RANDOM_DEVICE_=1 
-D_WEBSOCKETPP_NULLPTR_TOKEN_=0 -Dpdal_plugin_reader_greyhound_EXPORTS 
-I/<>/include -I/<>/src/util -I/<>/src 
-I/<>/io -I/<>/kernels -I/<>/filters 
-I/<>/vendor/gtest-1.7.0/include 
-I/<>/vendor/gtest-1.7.0 
-I/<>/obj-x86_64-linux-gnu/include 
-I/<>/vendor/eigen-3.1.91 
-I/<>/vendor/jsoncpp-1.6.2/dist 
-I/<>/vendor/nanoflann-1.1.8 -I/<>/vendor/rply-1.1.4 
-I/usr/include/libxml2 -I/usr/include/gdal -I/usr/include/geotiff 
-I/usr/include/jsoncpp  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2  -Wextra -Wall 
-Wno-unused-parameter -Wno-unused-variable -Wpointer-
 arith -Wcast-align -Wcast-qual -Wredundant-decls -Wno-long-long 
-Wno-unknown-pragmas -Wno-deprecated-declarations -isystem /usr/local/include 
-std=c++11 -O2 -g -DNDEBUG -fPIC   -o 
CMakeFiles/pdal_plugin_reader_greyhound.dir/io/CompressionStream.cpp.o -c 
/<>/plugins/greyhound/io/CompressionStream.cpp
[ 25%] Building CXX object 
plugins/greyhound/CMakeFiles/pdal_plugin_reader_greyhound.dir/io/Exchanges.cpp.o
cd /<>/obj-x86_64-linux-gnu/plugins/greyhound && /usr/bin/c++   
-DHAVE_JSONCPP=1 -DHAVE_WEBSOCKETPP=1 -D_WEBSOCKETPP_CPP11_RANDOM_DEVICE_=1 
-D_WEBSOCKETPP_NULLPTR_TOKEN_=0 -Dpdal_plugin_reader_greyhound_EXPORTS 
-I/<>/include -I/<>/src/util -I/<>/src 
-I/<>/io -I/<>/kernels -I/<>/filters 
-I/<>/vendor/gtest-1.7.0/include 
-I/<>/vendor/gtest-1.7.0 
-I/<>/obj-x86_64-linux-gnu/include 
-I/<>/vendor/eigen-3.1.91 
-I/<>/vendor/jsoncpp-1.6.2/dist 
-I/<>/vendor/nanoflann-1.1.8 -I/<>/vendor/rply-1.1.4 
-I/usr/include/libxml2 -I/usr/include/gdal -I/usr/include/geotiff 
-I/usr/include/jsoncpp  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2  -Wextra -Wall 
-Wno-unused-parameter -Wno-unused-variable -Wpointer-
 arith -Wcast-align -Wcast-qual -Wredundant-decls -Wno-long-long 
-Wno-unknown-pragmas -Wno-deprecated-declarations -isystem /usr/local/include 
-std=c++11 -O2 -g -DNDEBUG -fPIC   -o 
CMakeFiles/pdal_plugin_reader_greyhound.dir/io/Exchanges.cpp.o -c 
/<>/plugins/greyhound/io/Exchanges.cpp
[ 26%] Building CXX object 
plugins/greyhound/CMakeFiles/pdal_plugin_reader_greyhound.dir/io/GreyhoundReader.cpp.o
cd /<>/obj-x86_64-linux-gnu/plugins/greyhound && /usr/bin/c++   
-DHAVE_JSONCPP=1 -DHAVE_WEBSOCKETPP=1 -D_WEBSOCKETPP_CPP11_RANDOM_DEVICE_=1 
-D_WEBSOCKETPP_NULLPTR_TOKEN_=0 -Dpdal_plugin_reader_greyhound_EXPORTS 
-I/<>/include -I/<>/src/util -I/<>/src 
-I/<>/io -I/<>/kernels -I/<>/filters 
-I/<>/vendor/gtest-1.7.0/include 
-I/<>/v

Bug#824226: Info received (openjdk-8-jre: ATK bridge causes segfault when loading JR)

2016-08-28 Thread Samuel Thibault
Peter Keel, on Sat 27 Aug 2016 11:32:34 +0200, wrote:
> And they all crash with the same error: 
> #  SIGSEGV (0xb) at pc=0x7f129a520043, pid=27365, tid=0x7f12886b2700
> #
> # JRE version: OpenJDK Runtime Environment (8.0_102-b14) (build 
> 1.8.0_102-8u102-b14.1-2-b14)
> # Java VM: OpenJDK 64-Bit Server VM (25.102-b14 mixed mode linux-amd64 
> compressed oops)
> # Problematic frame:
> # C  [libatk-bridge-2.0.so.0+0xf043]

Does java not provide a whole backtrace?  That information is needed to
be able to know in which conditions the issue is happening, and thus
possibly why.

Samuel



Bug#835669: wxsqlite3: FTBFS when built with dpkg-buildpackage -A (samples/minimal: not found)

2016-08-28 Thread Santiago Vila
Package: src:wxsqlite3
Version: 3.4.0~dfsg1-1
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
dh build-indep --parallel --with autotools_dev
   dh_testdir -i -O--parallel
   dh_update_autotools_config -i -O--parallel
   dh_autotools-dev_updateconfig -i -O--parallel
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
ln -s /<>/build30 /<>/build
dh_auto_configure -- --with-sqlite3-prefix=/usr
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
--disable-dependency-tracking --with-sqlite3-prefix=/usr
configure: WARNING: unrecognized options: --disable-silent-rules, 
--disable-maintainer-mode
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu

[... snipped ...]

Generating docs for file wxsqlite3opt.h...
Generating page documentation...
Generating group documentation...
Generating class documentation...
Generating docs for compound wxSQLite3AggregateFunction...
Generating docs for compound wxSQLite3Authorizer...
Generating docs for compound wxSQLite3BackupProgress...
Generating docs for compound wxSQLite3Blob...
Generating docs for compound wxSQLite3BlobReference...
Generating docs for compound wxSQLite3Collation...
Generating docs for compound wxSQLite3Database...
Generating docs for compound wxSQLite3DatabaseReference...
Generating docs for compound wxSQLite3Exception...
Generating docs for compound wxSQLite3FunctionContext...
Generating docs for compound wxSQLite3Hook...
Generating docs for compound wxSQLite3IntegerCollection...
Generating docs for compound wxSQLite3NamedCollection...
Generating docs for compound wxSQLite3ResultSet...
Generating docs for compound wxSQLite3ScalarFunction...
Generating docs for compound wxSQLite3Statement...
Generating docs for compound wxSQLite3StatementBuffer...
Generating docs for compound wxSQLite3StatementReference...
Generating docs for compound wxSQLite3StringCollection...
Generating docs for compound wxSQLite3Table...
Generating docs for compound wxSQLite3Transaction...
Generating namespace index...
Generating graph info page...
Generating directory documentation...
Generating index page...
Generating page index...
Generating module index...
Generating namespace index...
Generating namespace member index...
Generating annotated compound index...
Generating alphabetical compound index...
Generating hierarchical class index...
Generating member index...
Generating file index...
Generating file member index...
Generating example index...
finalizing index lists...
writing tag file...
lookup cache used 421/65536 hits=1845 misses=430
finished...
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
debian/runtest.sh
debian/runtest.sh: 3: debian/runtest.sh: samples/minimal: not found
debian/rules:50: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 127
make[1]: Leaving directory '/<>'
debian/rules:16: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Version 3.3.1~dfsg1-1 built ok, so I suspect of the changes matching this
changelog entry:

   * Rework packaging to match upstream changes.

To avoid this kind of bugs being present in testing, please check
that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B" work
(especially after packaging changes), and also please consider
uploading the package in source-only form, so that we get
pretty official build logs here:

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

and we detect FTBFS in the "Arch: all" autobuilder much earlier.

Thanks.



Bug#834648: libvmime: typo in debian/rules (override_dh_autoclean -> override_dh_auto_clean)

2016-08-28 Thread Carsten Schoenert
tags 834648 +pending
thanks

Hello Chris,

On Wed, Aug 17, 2016 at 09:24:32PM +0100, Chris Lamb wrote:
> I believe there is a typo in your debian/rules (override_dh_autoclean
> -> override_dh_auto_clean).
> 
> Patch attached.

your are right, the override is clearly miss spelled. I applied your
patch and will be included in the next upload. Thanks for your
contribution!

Regards
Carsten



Bug#832148: fix SIGPWR warning on kfreebsd

2016-08-28 Thread Craig Small
On Sat, Jul 23, 2016 at 6:09 AM Jon Boden  wrote:

> This patch fixes SIGPWR warning on kfreebsd (and avoids hardcoding 29 for
> a signal we don't have ;-))
>
Hi Jon,
  I've applied that patch to the Debian git. I'll also put this into
upstream. I wonder how many times you saw
that message before you went 'dammit, im going to fix that'.

 - Craig
-- 
Craig Small (@smallsees)   http://dropbear.xyz/ csmall at : enc.com.au
Debian GNU/Linux   http://www.debian.org/   csmall at : debian.org
GPG fingerprint:5D2F B320 B825 D939 04D2  0519 3938 F96B DF50 FEA5


Bug#799200: network-manager-strongswan: configuration GUI broken

2016-08-28 Thread Harald Dunkel
Hi David,

On 08/21/16 16:30, David Härdeman wrote:
> Hi,
> 
> I can confirm that the UI is broken and that the patch which Michael
> Terry submitted fixes the issue (tested a self-built version of the
> package with the patch).
> 
> Maintainer, could you please consider releasing a new version with the
> patch?
> 

Since I cannot verify the bugfix for #799200, would you mind to do me
a favor and try the new package 1.3.1-2? See attachment.


Thanx very much for your help
Harri
-- 
Dipl.-Ing. Harald Dunkel |
Muehlenbachstr. 3|  keep it simple
52134 Herzogenrath, Germany  |
+49 2407 565 105 |



network-manager-strongswan.handoff.david.tar
Description: Unix tar archive


signature.asc
Description: OpenPGP digital signature


Bug#835670: MAC address of the network card keeps changing in each reboot

2016-08-28 Thread Hughe
Package: src:linux
Version: 3.16.7-ckt25-2
Severity: important
Tags: upstream

Hi,

This machine has two ethernet cards.

$ lspci -nn | grep Ether
02:00.0 Ethernet controller [0200]: Qualcomm Atheros AR8161 Gigabit Ethernet
[1969:1091] (rev 10)
03:05.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd.
RTL-8100/8101L/8139 PCI Fast Ethernet Adapter [10ec:8139] (rev 10)

I use AR8161 as default network interface card. The problem is each time system
boots, AR8161's MAC address changes.

[1.579415] alx :02:00.0 eth1: Qualcomm Atheros AR816x/AR817x Ethernet
[02:ec:0d:e1:fe:8a]
[   97.262720] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[   97.263491] alx :02:00.0 eth1: NIC Up: 100 Mbps Full
[   97.263687] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[  560.923170] alx :02:00.0 eth1: NIC Up: 100 Mbps Full
[ 1061.098093] alx :02:00.0 eth1: NIC Up: 100 Mbps Full
[17500.371445] alx :02:00.0 eth1: NIC Up: 100 Mbps Full

I made a udevd file to create permanent network interface device for two cards.
But AR8161 becomes eth1 not eth0 which I assigned. In rare occasion, network
connection gets lost after reboot or resume from hibernation.

$ more 70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.

# lspci -nn | grep Eth
# Retrieve MAC address of each adapter
# udevadm info -a -p /sys/class/net/eth0 [eth1]
# ifconfig -a
# or
# ifconfig eth0 [eth1]

# Qualcomm Atheros AR8161 Gigabit Ethernet [1969:1091]
# Kernel module: alx
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="a2:71:b7:12:2d:c
0", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter

# Kernel module: 8139too
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:0e:e8:de:d2:e
9", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

When I changed eth1 to eth0 in /etc/network/interfaces file, the system lost
network connection because eth0 was assigned to Realteck ethernet card and the
network cable wasn't plugged in. So I forced to get back to eth1.

$ more interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto eth1
# iface lo inet loopback

# The primary network interface
# eth1 is wrong? (8/27/2016)
# allow-hotplug eth0
iface eth1 inet static
address 192.168.1.100
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.1

Does MAC address alignment problem is related to floating MAC address I've
experienced for three years since 2013?

http://code.metager.de/source/history/linux/stable/drivers/net/ethernet/atheros/alx/hw.c
alx: fix MAC address alignment problem

In two places, parts of MAC addresses are used as u32/u16
values. This can cause alignment problems, use put_unaligned
and get_unaligned to fix this.

Reported-by: Ben Hutchings 
Signed-off-by: Johannes Berg 
Signed-off-by: David S. Miller 


Kernel 4.6.0's alx module has the same problem too. I tested it yesterday.

The network driver should access the factory MAC address of ethernet card, use
it to create a network interface device in consistent manner.




-- Package-specific info:
** Version:
Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 
4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08)

** Command line:
BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64 root=/dev/mapper/main--vg-root ro quiet

** Not tainted

** Kernel log:
[ 1060.004897] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1060.006030] ata6.00: configured for UDMA/133
[ 1060.016879] usb 1-4: reset high-speed USB device number 4 using ehci-pci
[ 1060.040896] usb 3-1: reset full-speed USB device number 2 using ohci-pci
[ 1060.432956] usb 1-4.4: reset high-speed USB device number 5 using ehci-pci
[ 1060.481109] usb 3-3: reset low-speed USB device number 3 using ohci-pci
[ 1060.813373] PM: restore of devices complete after 1298.665 msecs
[ 1060.813579] PM: Image restored successfully.
[ 1060.813597] PM: Basic memory bitmaps freed
[ 1060.813598] Restarting tasks ... done.
[ 1061.098093] alx :02:00.0 eth1: NIC Up: 100 Mbps Full
[17497.796600] PM: Syncing filesystems ... done.
[17497.829749] Freezing user space processes ... (elapsed 0.001 seconds) done.
[17497.831260] PM: Marking nosave pages: [mem 0x0009f000-0x000f]
[17497.831264] PM: Marking nosave pages: [mem 0x8fe8-0x]
[17497.832091] PM: Marking nosave pages: [mem 0x8400-0x87ff]
[17497.832352] PM: Basic memory bitmaps created
[17497.832372] PM: Preallocating image memory... done

Bug#835608: mkchromecast: fails to Open pavucontrol and select the mkchromecast sink.

2016-08-28 Thread Cristian Ionescu-Idbohrn
On Sat, 27 Aug 2016, Muammar El Khatib wrote:
>
> I have now updated README.Debian.

I see you added this:

Depends: ..., pavucontrol, pulseaudio-utils, pulseaudio

but pulseaudio-utils isn't needed, as it is on the pulseaudio
dependency list.

In README.md, it might be a good idea to mention pavucontrol under
Requirements:, Linux.

> Yes, it assumes that pulseaudio is installed on the host.

Right.  Now that pulseaudio is a dependency makes mkchromecast not
installable on most of my systems, where pulseaudio is a no-no.

> I may try to find another way for capturing the audio from alsa. But
> in this sense, I am afraid mkchromecast would work as it does in
> macOS where all system sound is casted. But let's give it a try.

That will certainly be useful, in my case.
I'm guessing here, as I lack deep knowledge, but gstreamer might be
another alternative.  It's dealing with sinks too.  See:

gstreamer1.0-alsa - GStreamer plugin for ALSA
gstreamer1.0-pulseaudio - GStreamer plugin for PulseAudio


Cheers,

-- 
Cristian



Bug#835606: polly pulls in outdated bundled jsoncpp headers

2016-08-28 Thread Sylvestre Ledru
Le 27/08/2016 à 16:39, James Clarke a écrit :
> Source: llvm-toolchain-3.8
> Version: 1:3.8.1-9
> Severity: important
> Tags: patch
> Control: clone -1 -2
> Control: reassign -2 llvm-toolchain-3.9 1:3.9~+rc3-1~exp1
> I have attached an updated version of use-deb-json.diff which uses the
> system include paths. Note that I hard-coded the include path to
> /usr/include/jsoncpp for the non-cmake build (and it's untested); given
> that 3.9 only uses CMake, I didn't bother to do it "properly"
> (presumably pkg-config would be the way to go), and the non-cmake bits
> will need to be removed for 3.9.
Well done! and many thanks for this!
This is now in the svn. I am building snapshot with it to test.

Thanks again,
Sylvestre



signature.asc
Description: OpenPGP digital signature


Bug#826836: bmon: FTBFS on kfreebsd: error: 'struct if_data' has no member named 'ifi_recvquota'

2016-08-28 Thread Steven Chamberlain
Hi Dmitry!

Dmitry Smirnov wrote:
> I tried the patch: bmon compiled so I was able to install it however it did 
> not show any network interfaces on kFreeBSD...

With the patch applied to latest upstream Git, It shows network
interfaces for me on kfreebsd-amd64 10.1 and 10.3...

What kernel did you test this with?

Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org


signature.asc
Description: Digital signature


Bug#811640: regarding dasher gcc6 ftbfs / 5.0 beta

2016-08-28 Thread Andreas Henriksson
Hello intrigeri!

Read your bug report (#835533) and spent a few seconds looking at
the gcc6 ftbfs (#811640). The current ftbfs looks trivial to resolve
bit apparently noone cares enough about the package.

> DasherAppSettings.cpp:398:14: error: cannot convert 'bool' to 'const gchar* 
> {aka const char*}' in return
>return false;
>   ^

Looking at the callers of the function the correct return should apparently
be "" here as callers checks for that or for strlen == 0.

> DasherAppSettings.cpp: In function 'void 
> dasher_app_settings_launch_advanced(DasherAppSettings*)':
> DasherAppSettings.cpp:505:15: warning: ISO C++ forbids converting a string 
> constant to 'gchar* {aka char*}' [-Wwrite-strings]
>szArgs[0] = "gconf-editor";
>^~

This one is not so obvious to me. For "C++ correctness" you should apparently
change the declaration of szArgs to be const char* rather than char*, but
I think that'll not last long as szArgs is passed to g_spawn_async
which doesn't take a 'const' char*, only a char*. I'm not sure if there's
any reason g_spawn_async hasn't been constified, but I assume it mostly
that it was written with C in mind and this is no problem there...

My spontaneous idea for solution was thus to simply cast the assignments:

szArgs[0] = (char*)"gconf-editor";
szArgs[1] = (char*)"/apps/dasher4";

Since you mentioned there was upstream activity I looked at how they solved
it in:
https://github.com/ipomoena/dasher/blob/master/Src/Gtk2/DasherAppSettings.cpp#L81
(Not sure this is the correct upstream repository though.)

This does not look correct at all to me. Please note the strdup which will
need it to get freed at some point to not leak memory, then call to
g_spawn_async and given it's an async method I assume it won't really
do any work at all until we let the main loop run again, then *directly*
calls g_strfreev(szArgs);
Without investigating any deeper I think this must result in a use-after-free.

We need someone that's interested in dasher to maintain it properly.
Apparently upstream could use an extra pair of eyes to help keep them
safe. This is thus my attempt at suckering you, who have shown atleast
a bit of interest in dasher, to be that person.
If not, the quick route would probably just be to add a patch with
the above suggested solution (which I've verified fixes the build)
and do an NMU to get dasher back into testing.

Regards,
Andreas Henriksson



Bug#835608: mkchromecast: fails to Open pavucontrol and select the mkchromecast sink.

2016-08-28 Thread Muammar El Khatib
On Sun, Aug 28, 2016 at 11:30:04AM +0200, Cristian Ionescu-Idbohrn wrote:
> On Sat, 27 Aug 2016, Muammar El Khatib wrote:
> >
> > I have now updated README.Debian.
>
> I see you added this:
>
>   Depends: ..., pavucontrol, pulseaudio-utils, pulseaudio
>
> but pulseaudio-utils isn't needed, as it is on the pulseaudio
> dependency list.
>

Thanks for the remark.

> In README.md, it might be a good idea to mention pavucontrol under
> Requirements:, Linux.

I will add it.

>
> > Yes, it assumes that pulseaudio is installed on the host.
>
> Right.  Now that pulseaudio is a dependency makes mkchromecast not
> installable on most of my systems, where pulseaudio is a no-no.
>

That was the idea. After your report, I realized mkchromecast is mostly useless
in systems without pulseaudio right now. I will remove that dependency in next
releases.

> > I may try to find another way for capturing the audio from alsa. But
> > in this sense, I am afraid mkchromecast would work as it does in
> > macOS where all system sound is casted. But let's give it a try.
>
> That will certainly be useful, in my case.
> I'm guessing here, as I lack deep knowledge, but gstreamer might be
> another alternative.  It's dealing with sinks too.  See:
>
>   gstreamer1.0-alsa - GStreamer plugin for ALSA
>   gstreamer1.0-pulseaudio - GStreamer plugin for PulseAudio

Thanks for this info!. Yesterday, I was already playing with ffmpeg + ALSA to
capture audio, but I think it will be a complicated solution to implement
(cards' and devices' names may change from system to system).  I had forgotten
about GStreamer completely. Reading just a bit about it, it may be a possible
solution.

Regards,
--
Muammar El Khatib.
Linux user: 403107.
GPG Key = 71246E4A.
http://muammar.me | http://proyectociencia.org
  ,''`.
 : :' :
 `. `'
   `-



Bug#835668: pdal: FTBFS in testing (H5Cpp.h: No such file or directory)

2016-08-28 Thread Sebastiaan Couwenberg

Control: fixed -1 pdal/1.3.0~rc1-1~exp1
Control: tags -1 pending

On 08/28/16 10:56, Santiago Vila wrote:

In file included from 
/<>/plugins/icebridge/io/IcebridgeReader.hpp:55:0,
 from 
/<>/plugins/icebridge/io/IcebridgeReader.cpp:35:
/<>/plugins/icebridge/io/Hdf5Handler.hpp:37:19: fatal error: 
H5Cpp.h: No such file or directory
 #include "H5Cpp.h"
   ^


I suspect GCC 6 is at fault here, hdf5 hasn't been update in unstable in 
a while.


Yesterday I fixed this issue for PDAL 1.3.0-RC1 which was uploaded to 
experimental and currently in NEW, so I'll cherry pick that change and 
upload a new revision of 1.2.0 to unstable to fix this issue in the mean 
time until 1.3.0 is released and moved from experimental to unstable.


Kind Regards,

Bas

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



Bug#835671: RFS: node-inline-source-map/0.6.1-1 [ITP]

2016-08-28 Thread Ross Gammon
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-inline-source-map"

* Package name: node-inline-source-map
  Version : 0.6.1-1
  Upstream Author : Thorsten Lorenz  (http://thlorenz.com)
* URL : https://github.com/thlorenz/inline-source-map
* License : Expat
  Section : web

It builds this binary package:

node-inline-source-map - base64 encoded source mappings for a generated file

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

https://mentors.debian.net/package/node-inline-source-map


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

dget -x https://mentors.debian.net/debian/pool/main/n/node-inline-source-map
/node-inline-source-map_0.6.1-1.dsc

Packaging can be obtained from:
https://anonscm.debian.org/cgit/pkg-javascript/node-inline-source-map.git

Changes since the last upload:

  * Initial release (Closes: #795114)


Regards,
Ross Gammon



-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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



Bug#679482: racoon with privsep enabled segfaults with 'unauthorized domain'

2016-08-28 Thread Richard Kettlewell
In https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679482:
> Try strongswan, it works on Debian kfreebsd and ordinary wheezyy. 
> racoon is long in the tooth, and because of the sort of bitrot and
> security issues it has (runs as root) I think it might be better if this
> part of ipsec-tools was deprecated.

FWIW I ended up using racoon because the examples in
https://wiki.debian.org/IPsec use it.  It would be valuable if that page
could be updated to reflect the best choices in current Debian (whatever
they are).

There's also a lot of historical details in the first section of the
page which could either be relegated to an appendix or completely
eliminated.  For example, someone who is trying to configure IPsec on
Debian in 2016 has no interest in the situation under Linux 2.4.x.

ttfn/rjk



Bug#835672: xfce4-power-manager: If installed without xfce4-session, fails to lock screen due to missing xflock4 script

2016-08-28 Thread Philip Hands
Package: xfce4-power-manager
Version: 1.4.4-4
Severity: normal

Dear Maintainer,

I am using xfce4-power-manager in conjunction with xmonad, and therefore
have not installed xfce4-session.

That results in xfce4-power-manager offering the option to lock the
screen on various events, but without the ability to actually do so,
which is somewhat confusing.

One can of course fix that by hand, by unpacking xfce4-session,
and copying xflock4 to somewhere in the user's path.

Cheers, Phil.

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

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

Versions of packages xfce4-power-manager depends on:
ii  libc6 2.23-1
ii  libcairo2 1.14.6-1+b1
ii  libdbus-1-3   1.10.8-1
ii  libdbus-glib-1-2  0.106-1
ii  libgdk-pixbuf2.0-02.34.0-1
ii  libglib2.0-0  2.48.0-1
ii  libgtk2.0-0   2.24.30-1.1
ii  libnotify40.7.6-2
ii  libpango-1.0-01.40.1-1
ii  libpangocairo-1.0-0   1.40.1-1
ii  libupower-glib3   0.99.4-2
ii  libx11-6  2:1.6.3-1
ii  libxext6  2:1.3.3-1
ii  libxfce4ui-1-04.12.1-2
ii  libxfce4util7 4.12.1-2
ii  libxfconf-0-2 4.12.0-2+b1
ii  libxrandr22:1.5.0-1
ii  upower0.99.4-2
ii  xfce4-power-manager-data  1.4.4-4

Versions of packages xfce4-power-manager recommends:
ii  libpam-systemd   229-4
ii  xfce4-power-manager-plugins  1.4.4-4

xfce4-power-manager suggests no packages.

-- no debconf information



Bug#835673: dacs: please make the build reproducible

2016-08-28 Thread Chris Lamb
Source: dacs
Version: 1.4.28b-3
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0], I noticed
that dacs could not be built reproducibly.

Patch attached.

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/patches/reproducible-build 1970-01-01 01:00:00.0 +0100
--- b/debian/patches/reproducible-build 2016-08-28 01:34:21.487298209 +0100
@@ -0,0 +1,65 @@
+Description: Make the build reproducible
+Author: Chris Lamb 
+Last-Update: 2016-08-19
+
+--- dacs-1.4.28b.orig/src/mkstamp
 dacs-1.4.28b/src/mkstamp
+@@ -18,7 +18,11 @@ version="$1"
+ 
+ echo "#define DACS_VERSION_REVID \"\$Id: \$\""
+ 
+-now=`date '+%e-%h-%Y %H:%M:%S' | sed -e "s/^ *//"`
++if test -n "$SOURCE_DATE_EPOCH"; then
++  now=`LC_ALL=C date --utc --date="@$SOURCE_DATE_EPOCH" '+%e-%h-%Y %H:%M:%S' 
| sed -e "s/^ *//"`
++else
++  now=`date '+%e-%h-%Y %H:%M:%S' | sed -e "s/^ *//"`
++fi
+ echo "#define DACS_VERSION_DATE \"Release date $now\""
+ 
+ echo "#define DACS_VERSION_RELEASE \"$version\""
+--- dacs-1.4.28b.orig/man/mkversion
 dacs-1.4.28b/man/mkversion
+@@ -20,7 +20,11 @@ textvfile="version.txt"
+ # We need the GNU cpp and this is the easiest way to ensure that
+ xcpp="gcc -E"
+ 
+-date=`date '+%e-%h-%Y' | sed -e "s/  / /"`
++if test -n "$SOURCE_DATE_EPOCH"; then
++  date=`LC_ALL=C date --utc --date="@$SOURCE_DATE_EPOCH" '+%e-%h-%Y' | sed -e 
"s/  / /"`
++else
++  date=`date '+%e-%h-%Y' | sed -e "s/  / /"`
++fi
+ version=`echo DACS_VERSION_RELEASE \
+ | $xcpp -P -include ../include/dacs_version.h - \
+ | sed -e 's/"//g' | tail -1`
+--- dacs-1.4.28b.orig/src/aclcheck.c
 dacs-1.4.28b/src/aclcheck.c
+@@ -614,7 +614,11 @@ acl_index_xml_text(Ds *ds, Acl_index *ad
+   int i;
+   Acl_map *am;
+ 
+-  ds_asprintf(ds, "\n", ad->date_created);
++  if (getenv("SOURCE_DATE_EPOCH")) {
++  ds_asprintf(ds, "\n", 
getenv("SOURCE_DATE_EPOCH"));
++  } else {
++  ds_asprintf(ds, "\n", ad->date_created);
++  }
+ 
+   for (i = 0; i < dsvec_len(ad->acl_map); i++) {
+   am = (Acl_map *) dsvec_ptr_index(ad->acl_map, i);
+--- dacs-1.4.28b.orig/man/mkindex
 dacs-1.4.28b/man/mkindex
+@@ -474,7 +474,12 @@ mkdirectives >> ${f}.html
+ 
+ mkdtd "../dtd-xsd" "/dtd-xsd" >> ${f}.html
+ 
+-now=`date`
++if test -n "$SOURCE_DATE_EPOCH"
++then
++  now=`LC_ALL=C date --utc --date="@$SOURCE_DATE_EPOCH"`
++else
++  now=`date`
++fi
+ echo '' >> "${f}.html"
+ echo '' >> "${f}.html"
+ echo '' >> "${f}.html"
--- a/debian/patches/series 2016-08-28 01:25:36.369737164 +0100
--- b/debian/patches/series 2016-08-28 01:26:23.442235361 +0100
@@ -2,3 +2,4 @@
 ssl_hook_Fixup
 libtool-shell
 shared-library-linkage
+reproducible-build


Bug#835675: seahorse-nautilus: FTBFS: conftest.c:11:28: fatal error: ac_nonexistent.h: No such file or directory

2016-08-28 Thread Lucas Nussbaum
Source: seahorse-nautilus
Version: 3.11.92-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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 version 6.2.0 20160822 (Debian 6.2.0-1) 
> configure:3615: $? = 0
> configure:3604: gcc -V >&5
> gcc: error: unrecognized command line option '-V'
> gcc: fatal error: no input files
> compilation terminated.
> configure:3615: $? = 1
> configure:3604: gcc -qversion >&5
> gcc: error: unrecognized command line option '-qversion'; did you mean 
> '--version'?
> gcc: fatal error: no input files
> compilation terminated.
> configure:3615: $? = 1
> configure:3635: checking whether the C compiler works
> configure:3657: gcc -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wl,-z,relro conftest.c  >&5
> configure:3661: $? = 0
> configure:3709: result: yes
> configure:3712: checking for C compiler default output file name
> configure:3714: result: a.out
> configure:3720: checking for suffix of executables
> configure:3727: gcc -o conftest -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wl,-z,relro conftest.c  >&5
> configure:3731: $? = 0
> configure:3753: result: 
> configure:3775: checking whether we are cross compiling
> configure:3783: gcc -o conftest -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wl,-z,relro conftest.c  >&5
> configure:3787: $? = 0
> configure:3794: ./conftest
> configure:3798: $? = 0
> configure:3813: result: no
> configure:3818: checking for suffix of object files
> configure:3840: gcc -c -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:3844: $? = 0
> configure:3865: result: o
> configure:3869: checking whether we are using the GNU C compiler
> configure:3888: gcc -c -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:3888: $? = 0
> configure:3897: result: yes
> configure:3906: checking whether gcc accepts -g
> configure:3926: gcc -c -g -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:3926: $? = 0
> configure:3967: result: yes
> configure:3984: checking for gcc option to accept ISO C89
> configure:4047: gcc  -c -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:4047: $? = 0
> configure:4060: result: none needed
> configure:4082: checking dependency style of gcc
> configure:4193: result: none
> configure:4214: checking how to run the C preprocessor
> configure:4245: gcc -E -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c
> configure:4245: $? = 0
> configure:4259: gcc -E -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c
> conftest.c:11:28: fatal error: ac_nonexistent.h: No such file or directory
>  #include 
> ^
> compilation terminated.
> configure:4259: $? = 1
> configure: failed program was:
> | /* confdefs.h */
> | #define PACKAGE_NAME "seahorse-nautilus"
> | #define PACKAGE_TARNAME "seahorse-nautilus"
> | #define PACKAGE_VERSION "3.11.92"
> | #define PACKAGE_STRING "seahorse-nautilus 3.11.92"
> | #define PACKAGE_BUGREPORT 
> "http://bugzilla.gnome.org/enter_bug.cgi?product=seahorse-plugins&component=Nautilus";
> | #define PACKAGE_URL ""
> | #define PACKAGE "seahorse-nautilus"
> | #define VERSION "3.11.92"
> | /* end confdefs.h.  */
> | #include 
> configure:4284: result: gcc -E
> configure:4304: gcc -E -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c
> configure:4304: $? = 0
> configure:4318: gcc -E -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c
> conftest.c:11:28: fatal error: ac_nonexistent.h: No such file or directory
>  #include 
> ^
> compilation terminated.
> configure:4318: $? = 1
> configure: failed program was:
> | /* confdefs.h */
> | #define PACKAGE_NAME "seahorse-nautilus"
> | #define PACKAGE_TARNAME "seahorse-nautilus"
> | #define PACKAGE_VERSION "3.11.92"
> | #define PACKAGE_STRING "seahorse-nautilus 3.11.92"
> | #define PACKAGE_BUGREPORT 
> "http://bug

Bug#835676: plasma-discover: FTBFS: dh_install: missing files, aborting

2016-08-28 Thread Lucas Nussbaum
Source: plasma-discover
Version: 5.7.3-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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 '/<>/obj-x86_64-linux-gnu'
> make[3]: Nothing to be done for 'preinstall'.
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> Install the project...
> /usr/bin/cmake -P cmake_install.cmake
> -- Install configuration: "Debian"
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ar/LC_MESSAGES/libdiscover.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ar/LC_MESSAGES/plasma-discover-notifier.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ar/LC_MESSAGES/plasma-discover.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ar/LC_MESSAGES/plasma_applet_org.kde.discovernotifier.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ast/LC_MESSAGES/libdiscover.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ast/LC_MESSAGES/plasma-discover-notifier.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ast/LC_MESSAGES/plasma-discover.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ast/LC_MESSAGES/plasma_applet_org.kde.discovernotifier.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/bg/LC_MESSAGES/libdiscover.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/bs/LC_MESSAGES/libdiscover.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/bs/LC_MESSAGES/plasma-discover.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/bs/LC_MESSAGES/plasma_applet_org.kde.discovernotifier.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ca/LC_MESSAGES/libdiscover.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ca/LC_MESSAGES/plasma-discover-notifier.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ca/LC_MESSAGES/plasma-discover.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ca/LC_MESSAGES/plasma_applet_org.kde.discovernotifier.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ca@valencia/LC_MESSAGES/libdiscover.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ca@valencia/LC_MESSAGES/plasma-discover-notifier.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ca@valencia/LC_MESSAGES/plasma-discover.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ca@valencia/LC_MESSAGES/plasma_applet_org.kde.discovernotifier.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/cs/LC_MESSAGES/libdiscover.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/cs/LC_MESSAGES/plasma-discover-notifier.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/cs/LC_MESSAGES/plasma-discover.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/cs/LC_MESSAGES/plasma_applet_org.kde.discovernotifier.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/da/LC_MESSAGES/libdiscover.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/da/LC_MESSAGES/plasma-discover-notifier.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/da/LC_MESSAGES/plasma-discover.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/da/LC_MESSAGES/plasma_applet_org.kde.discovernotifier.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/de/LC_MESSAGES/libdiscover.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/de/LC_MESSAGES/plasma-discover-notifier.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/de/LC_MESSAGES/plasma-discover.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/de/LC_MESSAGES/plasma_applet_org.kde.discovernotifier.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/el/LC_MESSAGES/libdiscover.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/el/LC_MESSAGES/plasma-discover-notifier.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/el/LC_MESSAGES/plasma-discover.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/el/LC_MESSAGES/plasma_applet_org.kde.discovernotifier.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/en_GB/LC_MESSAGES/libdiscover.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/en_GB/LC_MESSAGES/plasma-discover-notifier.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/en_GB/LC_MESSAGES/plasma-discover.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/en_GB/LC_MESSAGES/plasma_applet_org.kde.discovernotifier.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/es/LC_MESSAGES/libdiscover.mo
> -- Installing: 
> /<>

Bug#835679: ismrmrd: FTBFS: dataset.c:13:18: fatal error: hdf5.h: No such file or directory

2016-08-28 Thread Lucas Nussbaum
Source: ismrmrd
Version: 1.3.2-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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):
> /usr/bin/cc  -Dismrmrd_EXPORTS -I/<>/include 
> -I/<>/obj-x86_64-linux-gnu/include  -g -O2 
> -fdebug-prefix-map=/<>=. -fPIE -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -pedantic -Wdate-time -D_FORTIFY_SOURCE=2  
> -std=c99 -Wall -fPIC   -o CMakeFiles/ismrmrd.dir/libsrc/dataset.c.o   -c 
> /<>/libsrc/dataset.c
> /<>/libsrc/dataset.c:13:18: fatal error: hdf5.h: No such file or 
> directory
>  #include 
>   ^
> compilation terminated.
> CMakeFiles/ismrmrd.dir/build.make:161: recipe for target 
> 'CMakeFiles/ismrmrd.dir/libsrc/dataset.c.o' failed
> make[3]: *** [CMakeFiles/ismrmrd.dir/libsrc/dataset.c.o] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/08/28/ismrmrd_1.3.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#835674: macs: FTBFS: MACS2/IO/PeakIO.c:1:2: error: #error Do not use this file, it is the result of a failed Cython compilation.

2016-08-28 Thread Lucas Nussbaum
Source: macs
Version: 2.1.1.20160309-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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):
> x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
> -Wstrict-prototypes -fno-strict-aliasing -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -I/usr/include/python2.7 -c MACS2/IO/PeakIO.c -o 
> build/temp.linux-x86_64-2.7/MACS2/IO/PeakIO.o -w -O3 -ffast-math
> MACS2/IO/PeakIO.c:1:2: error: #error Do not use this file, it is the result 
> of a failed Cython compilation.
>  #error Do not use this file, it is the result of a failed Cython compilation.
>   ^
> error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
> E: pybuild pybuild:276: build: plugin distutils failed with: exit code=1: 
> /usr/bin/python setup.py build 
> dh_auto_build: pybuild --build -i python{version} -p 2.7 returned exit code 13
> debian/rules:16: recipe for target 'override_dh_auto_build' failed
> make[1]: *** [override_dh_auto_build] Error 25

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/08/28/macs_2.1.1.20160309-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#835685: golint: FTBFS: dh_auto_test: go test -v -p 1 github.com/golang/lint github.com/golang/lint/golint returned exit code 1

2016-08-28 Thread Lucas Nussbaum
Source: golint
Version: 0.0+git20150623.7b7f436-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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 --buildsystem=golang --with=golang
>dh_testdir -O--buildsystem=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   go install -v -p 1 github.com/golang/lint github.com/golang/lint/golint
> golang.org/x/tools/go/exact
> golang.org/x/tools/go/types
> golang.org/x/tools/go/gcimporter
> github.com/golang/lint
> github.com/golang/lint/golint
>dh_auto_test -O--buildsystem=golang
>   go test -v -p 1 github.com/golang/lint github.com/golang/lint/golint
> === RUN   TestAll
> --- FAIL: TestAll (0.01s)
>   lint_test.go:95: Lint failed at errorf.go:29; /should 
> replace.*t\.Error\(fmt\.Sprintf\(\.\.\.\)\).*t\.Errorf\(\.\.\.\)/ did not 
> match
>   lint_test.go:95: Lint failed at time.go:11; /Msec.*\*time.Duration/ did 
> not match
>   lint_test.go:95: Lint failed at time.go:13; /Secs.*time.Duration/ did 
> not match
> === RUN   TestLine
> --- PASS: TestLine (0.00s)
> === RUN   TestLintName
> --- PASS: TestLintName (0.00s)
> === RUN   TestExportedType
> --- PASS: TestExportedType (0.00s)
> FAIL
> exit status 1
> FAIL  github.com/golang/lint  0.015s
> ? github.com/golang/lint/golint   [no test files]
> dh_auto_test: go test -v -p 1 github.com/golang/lint 
> github.com/golang/lint/golint returned exit code 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/08/28/golint_0.0+git20150623.7b7f436-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#835681: python-axolotl: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13

2016-08-28 Thread Lucas Nussbaum
Source: python-axolotl
Version: 0.1.7-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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 python2 --buildsystem=pybuild
>dh_testdir -O--buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_2.7/build/axolotl
> copying axolotl/nosessionexception.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl
> copying axolotl/invalidmessageexception.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl
> copying axolotl/identitykeypair.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl
> copying axolotl/statekeyexchangeexception.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl
> copying axolotl/untrustedidentityexception.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl
> copying axolotl/legacymessageexception.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl
> copying axolotl/duplicatemessagexception.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl
> copying axolotl/invalidkeyexception.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl
> copying axolotl/identitykey.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl
> copying axolotl/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl
> copying axolotl/invalidversionexception.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl
> copying axolotl/sessioncipher.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl
> copying axolotl/invalidkeyidexception.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl
> copying axolotl/sessionbuilder.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl
> creating /<>/.pybuild/pythonX.Y_2.7/build/axolotl/kdf
> copying axolotl/kdf/messagekeys.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/kdf
> copying axolotl/kdf/derivedrootsecrets.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/kdf
> copying axolotl/kdf/hkdfv2.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/kdf
> copying axolotl/kdf/derivedmessagesecrets.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/kdf
> copying axolotl/kdf/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/kdf
> copying axolotl/kdf/hkdfv3.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/kdf
> copying axolotl/kdf/hkdf.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/kdf
> creating /<>/.pybuild/pythonX.Y_2.7/build/axolotl/util
> copying axolotl/util/byteutil.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/util
> copying axolotl/util/hexutil.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/util
> copying axolotl/util/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/util
> copying axolotl/util/medium.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/util
> copying axolotl/util/keyhelper.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/util
> creating /<>/.pybuild/pythonX.Y_2.7/build/axolotl/tests
> copying axolotl/tests/inmemoryprekeystore.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/tests
> copying axolotl/tests/inmemorysessionstore.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/tests
> copying axolotl/tests/test_sigs.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/tests
> copying axolotl/tests/inmemoryaxolotlstore.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/tests
> copying axolotl/tests/test_sessioncipher.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/tests
> copying axolotl/tests/inmemorysignedprekeystore.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/tests
> copying axolotl/tests/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/tests
> copying axolotl/tests/test_sessionbuilder.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/tests
> copying axolotl/tests/test_stuff.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/tests
> copying axolotl/tests/inmemoryidentitykeystore.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/tests
> creating /<>/.pybuild/pythonX.Y_2.7/build/axolotl/groups
> copying axolotl/groups/groupcipher.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/axolotl/groups
> copying axolotl/groups/_

Bug#835686: docker.io: FTBFS: .gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1137: cannot use _API_CreateContainer_Handler (type func(interface {}, "golang.org/x/net/context".Contex

2016-08-28 Thread Lucas Nussbaum
Source: docker.io
Version: 1.11.2~ds1-6
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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 '/<>'
> # build
> ./hack/make.sh dynbinary
> # WARNING! I don't seem to be running in a Docker container.
> # The result of this command might be an incorrect build, and will not be
> # officially supported.
> #
> # Try this instead: make all
> #
> 
> ---> Making bundle: dynbinary (in bundles/1.11.2/dynbinary)
> Building: bundles/1.11.2/dynbinary/docker-1.11.2
> # github.com/docker/containerd/api/grpc/types
> .gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1137: 
> cannot use _API_CreateContainer_Handler (type func(interface {}, 
> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
> error)) as type grpc.methodHandler in field value
> .gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1141: 
> cannot use _API_UpdateContainer_Handler (type func(interface {}, 
> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
> error)) as type grpc.methodHandler in field value
> .gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1145: 
> cannot use _API_Signal_Handler (type func(interface {}, 
> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
> error)) as type grpc.methodHandler in field value
> .gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1149: 
> cannot use _API_UpdateProcess_Handler (type func(interface {}, 
> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
> error)) as type grpc.methodHandler in field value
> .gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1153: 
> cannot use _API_AddProcess_Handler (type func(interface {}, 
> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
> error)) as type grpc.methodHandler in field value
> .gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1157: 
> cannot use _API_CreateCheckpoint_Handler (type func(interface {}, 
> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
> error)) as type grpc.methodHandler in field value
> .gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1161: 
> cannot use _API_DeleteCheckpoint_Handler (type func(interface {}, 
> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
> error)) as type grpc.methodHandler in field value
> .gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1165: 
> cannot use _API_ListCheckpoint_Handler (type func(interface {}, 
> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
> error)) as type grpc.methodHandler in field value
> .gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1169: 
> cannot use _API_State_Handler (type func(interface {}, 
> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
> error)) as type grpc.methodHandler in field value
> .gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1173: 
> cannot use _API_Stats_Handler (type func(interface {}, 
> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
> error)) as type grpc.methodHandler in field value
> .gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1173: too 
> many errors
> debian/rules:60: 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/08/28/docker.io_1.11.2~ds1-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#835684: syncthing: FTBFS: dh_auto_test: go test -v -p 1 github.com/syncthing/syncthing/cmd/stbench github.com/syncthing/syncthing/cmd/stcompdirs github.com/syncthing/syncthing/cmd/stdisco github.c

2016-08-28 Thread Lucas Nussbaum
Source: syncthing
Version: 0.14.4+dfsg1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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 '/<>/syncthing-0.14.4+dfsg1'
> dh_auto_build -- -ldflags "-X main.Version=v0.14.4-dfsg1 \
>-X main.BuildUser=debian \
>-X main.BuildHost=debian \
>-X main.BuildStamp=1471362463" \
>-tags 'noupgrade purego'
>   go install -v -p 1 -ldflags "-X main.Version=v0.14.4-dfsg1  
>   -X main.BuildUser=debian-X 
> main.BuildHost=debian-X 
> main.BuildStamp=1471362463" -tags "noupgrade purego" 
> github.com/syncthing/syncthing/cmd/stbench 
> github.com/syncthing/syncthing/cmd/stcompdirs 
> github.com/syncthing/syncthing/cmd/stdisco 
> github.com/syncthing/syncthing/cmd/stdiscosrv 
> github.com/syncthing/syncthing/cmd/stevents 
> github.com/syncthing/syncthing/cmd/stfileinfo 
> github.com/syncthing/syncthing/cmd/stfinddevice 
> github.com/syncthing/syncthing/cmd/stgenfiles 
> github.com/syncthing/syncthing/cmd/stindex 
> github.com/syncthing/syncthing/cmd/strelaysrv 
> github.com/syncthing/syncthing/cmd/strelaysrv/testutil 
> github.com/syncthing/syncthing/cmd/stsigtool 
> github.com/syncthing/syncthing/cmd/stvanity 
> github.com/syncthing/syncthing/cmd/stwatchfile 
> github.com/syncthing/syncthing/cmd/syncthing 
> github.com/syncthing/syncthing/lib/auto 
> github.com/syncthing/syncthing/lib/beacon 
> github.com/syncthing/syncthing/lib/config 
> github.com/syncthing/syncthing/lib/connections 
> github.com/syncthing/syncthing/lib/db 
> github.com/syncthing/syncthing/lib/dialer 
> github.com/syncthing/syncthing/lib/discover 
> github.com/syncthing/syncthing/lib/events 
> github.com/syncthing/syncthing/lib/fs 
> github.com/syncthing/syncthing/lib/ignore 
> github.com/syncthing/syncthing/lib/logger 
> github.com/syncthing/syncthing/lib/model 
> github.com/syncthing/syncthing/lib/nat 
> github.com/syncthing/syncthing/lib/osutil 
> github.com/syncthing/syncthing/lib/pmp 
> github.com/syncthing/syncthing/lib/protocol 
> github.com/syncthing/syncthing/lib/rand github.com/syncthing/syncthing/lib/rc 
> github.com/syncthing/syncthing/lib/relay/client 
> github.com/syncthing/syncthing/lib/relay/protocol 
> github.com/syncthing/syncthing/lib/scanner 
> github.com/syncthing/syncthing/lib/signature 
> github.com/syncthing/syncthing/lib/stats 
> github.com/syncthing/syncthing/lib/symlinks 
> github.com/syncthing/syncthing/lib/sync 
> github.com/syncthing/syncthing/lib/tlsutil 
> github.com/syncthing/syncthing/lib/upgrade 
> github.com/syncthing/syncthing/lib/upnp 
> github.com/syncthing/syncthing/lib/util 
> github.com/syncthing/syncthing/lib/versioner
> github.com/syncthing/syncthing/lib/logger
> github.com/syncthing/syncthing/lib/sync
> github.com/syncthing/syncthing/lib/events
> github.com/calmh/du
> golang.org/x/net/proxy
> github.com/syncthing/syncthing/lib/dialer
> golang.org/x/text/transform
> golang.org/x/text/unicode/norm
> github.com/syncthing/syncthing/lib/osutil
> github.com/bkaradzic/go-lz4
> github.com/calmh/luhn
> github.com/calmh/xdr
> github.com/gogo/protobuf/proto
> github.com/gogo/protobuf/protoc-gen-gogo/descriptor
> github.com/gogo/protobuf/gogoproto
> github.com/syncthing/syncthing/lib/rand
> github.com/syncthing/syncthing/lib/protocol
> github.com/syncthing/syncthing/lib/util
> github.com/syncthing/syncthing/lib/config
> github.com/syncthing/syncthing/lib/rc
> github.com/syncthing/syncthing/cmd/stbench
> github.com/syncthing/syncthing/lib/symlinks
> github.com/syncthing/syncthing/cmd/stcompdirs
> github.com/thejerf/suture
> golang.org/x/net/bpf
> golang.org/x/net/internal/iana
> golang.org/x/net/ipv6
> github.com/syncthing/syncthing/lib/beacon
> github.com/syncthing/syncthing/lib/discover
> github.com/syncthing/syncthing/cmd/stdisco
> github.com/cznic/b
> github.com/cznic/bufs
> github.com/cznic/fileutil
> github.com/cznic/mathutil
> github.com/cznic/sortutil
> github.com/cznic/zappy
> github.com/cznic/lldb
> github.com/cznic/ql/vendored/github.com/camlistore/go4/lock
> github.com/cznic/strutil
> github.com/cznic/ql
> github.com/golang/groupcache/lru
> github.com/juju/ratelimit
> github.com/lib/pq/oid
> github.com/lib/pq
> golang.org/x/net/context
> github.com/syncthing/syncthing/cmd/stdiscosrv
> github.com/syncthing/syncthing/cmd/stevents
> githu

Bug#835680: mathgl: FTBFS: complex_io.cpp:32:18: fatal error: hdf5.h: No such file or directory

2016-08-28 Thread Lucas Nussbaum
Source: mathgl
Version: 2.3.4-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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):
> cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++   -DHAVE_MEMRCHR 
> -DMGL_HAVE_GSL2 -DMGL_SRC -DNO_COLOR_ARRAY -Dmgl_EXPORTS 
> -I/<>/include -I/<>/obj-x86_64-linux-gnu/include 
> -I/usr/lib/openmpi/include/openmpi/opal/mca/event/libevent2021/libevent 
> -I/usr/lib/openmpi/include/openmpi/opal/mca/event/libevent2021/libevent/include
>  -I/usr/lib/openmpi/include -I/usr/lib/openmpi/include/openmpi 
> -I/<>/src/prc  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2  -fvisibility=hidden -fvisibility-inlines-hidden -fPIC   
> -o CMakeFiles/mgl.dir/complex_io.cpp.o -c /<>/src/complex_io.cpp
> /<>/src/complex_io.cpp:32:18: fatal error: hdf5.h: No such file 
> or directory
>  #include 
>   ^
> compilation terminated.
> src/CMakeFiles/mgl.dir/build.make:305: recipe for target 
> 'src/CMakeFiles/mgl.dir/complex_io.cpp.o' failed
> make[3]: *** [src/CMakeFiles/mgl.dir/complex_io.cpp.o] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/08/28/mathgl_2.3.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#835682: python-socketpool: FTBFS: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 3249: ordinal not in range(128)

2016-08-28 Thread Lucas Nussbaum
Source: python-socketpool
Version: 0.5.3-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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
> dh clean --with python2,python3 --buildsystem=pybuild
>dh_testdir -O--buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py clean 
> running clean
> removing '/<>/.pybuild/pythonX.Y_2.7/build' (and everything 
> under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-2.7' does not exist -- can't clean it
> I: pybuild base:184: python3.5 setup.py clean 
> Traceback (most recent call last):
>   File "setup.py", line 26, in 
> long_description = f.read()
>   File "/usr/lib/python3.5/encodings/ascii.py", line 26, in decode
> return codecs.ascii_decode(input, self.errors)[0]
> UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 3249: 
> ordinal not in range(128)
> E: pybuild pybuild:276: clean: plugin distutils failed with: exit code=1: 
> python3.5 setup.py clean 
> dh_auto_clean: pybuild --clean -i python{version} -p 3.5 returned exit code 13
> debian/rules:8: recipe for target 'clean' failed
> make: *** [clean] Error 25

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/08/28/python-socketpool_0.5.3-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#835677: remctl: FTBFS: dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2

2016-08-28 Thread Lucas Nussbaum
Source: remctl
Version: 3.12-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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[2]: Entering directory '/<>'
> cd tests && ./runtests -l '/<>/tests/TESTS'
> 
> Running all tests listed in TESTS.  If any tests fail, run the failing
> test program with runtests -o to see more details.
> 
> client/api..skipped (Kerberos tests not configured)
> client/ccache...skipped (Kerberos tests not configured)
> client/largeskipped (Kerberos tests not configured)
> client/open.ok (skipped 15 tests)
> client/remctl...skipped (Kerberos tests not configured)
> client/source-ipskipped (Kerberos tests not configured)
> client/timeout..skipped (Kerberos tests not configured)
> docs/podskipped (POD syntax tests normally skipped)
> docs/pod-spelling...skipped (Spelling tests only run for author)
> perl/module-version.skipped (Module version tests normally skipped)
> portable/asprintf...ok
> portable/daemon.ok
> portable/getaddrinfook (skipped 20 tests)
> portable/getnameinfook (skipped 7 tests)
> portable/getopt.ok
> portable/inet_aton..ok
> portable/inet_ntoa..ok
> portable/inet_ntop..ok
> portable/mkstempok
> portable/setenv.ok
> portable/snprintf...ok
> server/accept...skipped (Kerberos tests not configured)
> server/acl..ok (skipped 4 tests)
> server/acl/localgroup...ok
> server/anonymousskipped (Kerberos tests not configured)
> server/bind.skipped (Kerberos tests not configured)
> server/config...ok
> server/continue.skipped (Kerberos tests not configured)
> server/emptyskipped (Kerberos tests not configured)
> server/env..skipped (Kerberos tests not configured)
> server/errors...skipped (Kerberos tests not configured)
> server/help.skipped (Kerberos tests not configured)
> server/invalid..skipped (Kerberos tests not configured)
> server/logging..ok
> server/misc.skipped (Kerberos tests not configured)
> server/shell-misc...FAILED 8
> server/ssh-parseok
> server/stdinskipped (Kerberos tests not configured)
> server/streamingskipped (Kerberos tests not configured)
> server/sudo.ok
> server/summary..skipped (Kerberos tests not configured)
> server/user.skipped (Kerberos tests not configured)
> server/version..skipped (Kerberos tests not configured)
> util/buffer.ok
> util/gss-tokens.skipped (Kerberos tests not configured)
> util/messages...ok
> util/messages-krb5..ok
> util/network/addr-ipv4..ok
> util/network/addr-ipv6..ok
> util/network/client.ok
> util/network/server.ok
> util/tokens.ok
> util/vector.ok
> util/xmallocskipped (xmalloc tests only run for author)
> util/xwrite.ok (skipped 2 tests)
> 
> Failed Set Fail/Total (%) Skip Stat  Failing Tests
> -- --    
> server/shell-misc 1/15 7%00  8
> 
> Failed 1/1976 tests, 99.95% okay, 74 tests skipped.
> Files=55,  Tests=1976,  10.38 seconds (0.35 usr + 0.06 sys = 0.41 CPU)
> Makefile:4060: recipe for target 'check-local' failed
> make[2]: *** [check-local] Error 1
> make[2]: Leaving directory '/<>'
> Makefile:3760: recipe for target 'check-am' failed
> make[1]: *** [check-am] Error 2
> 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/08/28/remctl_3.12-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#835678: yosys: FTBFS: latex errors

2016-08-28 Thread Lucas Nussbaum
Source: yosys
Version: 0.6-6
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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[2]: Entering directory '/<>'
> [Makefile.conf] CONFIG := gcc
> 
>   Build successful.
> 
> cd manual && bash appnotes.sh
> + for job in APPNOTE_010_Verilog_to_BLIF APPNOTE_011_Design_Investigation 
> APPNOTE_012_Verilog_to_BTOR
> + '[' -f APPNOTE_010_Verilog_to_BLIF.ok -a APPNOTE_010_Verilog_to_BLIF.ok -nt 
> APPNOTE_010_Verilog_to_BLIF.tex ']'
> + '[' -f APPNOTE_010_Verilog_to_BLIF/make.sh ']'
> ++ '[' -f APPNOTE_010_Verilog_to_BLIF.aux ']'
> ++ true
> + old_md5=
> + pdflatex -shell-escape -halt-on-error APPNOTE_010_Verilog_to_BLIF.tex
> This is pdfTeX, Version 3.14159265-2.6-1.40.17 (TeX Live 2016/Debian) 
> (preloaded format=pdflatex)
>  \write18 enabled.
> entering extended mode
> (./APPNOTE_010_Verilog_to_BLIF.tex
> LaTeX2e <2016/03/31> patch level 3
> Babel <3.9r> and hyphenation patterns for 3 language(s) loaded.
> (/usr/share/texlive/texmf-dist/tex/latex/IEEEtran/IEEEtran.cls
> Document Class: IEEEtran 2015/08/26 V1.8b by Michael Shell
> -- See the "IEEEtran_HOWTO" manual for usage information.
> -- http://www.michaelshell.org/tex/ieeetran/
> (/usr/share/texlive/texmf-dist/tex/latex/psnfss/ot1ptm.fd)
> -- Using 210mm x 297mm (a4) paper.
> -- Using PDF output.
> -- This is a 9 point document.
> ) (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty
> (/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.def)
> (/usr/share/texlive/texmf-dist/tex/latex/psnfss/t1ptm.fd))
> (/usr/share/texlive/texmf-dist/tex/latex/libertine/libertine.sty
> (/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifluatex.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/xkeyval/xkeyval.sty
> (/usr/share/texlive/texmf-dist/tex/generic/xkeyval/xkeyval.tex
> (/usr/share/texlive/texmf-dist/tex/generic/xkeyval/xkvutils.tex
> (/usr/share/texlive/texmf-dist/tex/generic/xkeyval/keyval.tex
> (/usr/share/texlive/texmf-dist/tex/latex/base/textcomp.sty
> (/usr/share/texlive/texmf-dist/tex/latex/base/ts1enc.def))
> (/usr/share/texlive/texmf-dist/tex/latex/mweights/mweights.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/fontaxes/fontaxes.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/libertine/LinLibertine_I.tex))
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/hyperref.sty
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-hyperref.sty
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-generic.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/auxhook.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/kvoptions.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/pd1enc.def)
> (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/hyperref.cfg)
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/puenc.def)
> (/usr/share/texlive/texmf-dist/tex/latex/url/url.sty))
> 
> Package hyperref Message: Driver (autodetected): hpdftex.
> 
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/hpdftex.def
> (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/rerunfilecheck.sty))
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty
> (/usr/share/texlive/texmf-dist/tex/generic/babel-english/english.ldf
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.def)))
> (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty
> (/usr/share/texlive/texmf-dist/tex/latex/base/utf8.def
> (/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.dfu)
> (/usr/share/texlive/texmf-dist/tex/latex/base/ot1enc.dfu)
> (/usr/share/texlive/texmf-dist/tex/latex/base/omsenc.dfu)
> (/usr/share/texlive/texmf-dist/tex/latex/base/ts1enc.dfu)))
> (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amssymb.sty
> (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amsfonts.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsmath.sty
> For additional information on amsmath, use the `?' option.
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amstext.sty
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsgen.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsbsy.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsopn.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/units/units.sty
> (/usr/share/texlive/texmf-dist/tex/latex/base/ifthen.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/units/nicefrac.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/eurosym/euro

Bug#835683: kde-baseapps: FTBFS: dh_makeshlibs: failing due to earlier errors

2016-08-28 Thread Lucas Nussbaum
Source: kde-baseapps
Version: 4:16.04.3-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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[2]: Entering directory '/<>'
> dh_strip  --dbgsym-migration='kde-baseapps-dbg (<= 4:15.12.1-1~~)'
> make[2]: Leaving directory '/<>'
> dh_makeshlibs '-Xusr/lib/kde4/'  
> dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
> file: see diff output below
> dpkg-gensymbols: warning: debian/libkonq5abi1/DEBIAN/symbols doesn't match 
> completely debian/libkonq5abi1.symbols
> --- debian/libkonq5abi1.symbols (libkonq5abi1_4:16.04.3-1_amd64)
> +++ dpkg-gensymbolsKCWViT 2016-08-28 00:05:03.36000 +
> @@ -1,10 +1,10 @@
>  libkonq.so.5abi1 libkonq5abi1 #MINVER#
>   ABI_5_1@ABI_5_1 4:4.6.1
> - (optional=templinst|arch=!armhf 
> !i386)_Z17qRegisterMetaTypeI9KFileItemEiPKcPT_@ABI_5_1 4:15.12.1
> - (optional=templinst|arch=!armhf 
> !i386)_Z21qMetaTypeDeleteHelperI4KUrlEvPT_@ABI_5_1 4:15.12.1
> - (optional=templinst|arch=!armhf 
> !i386)_Z21qMetaTypeDeleteHelperI9KFileItemEvPT_@ABI_5_1 4:15.12.1
> - (optional=templinst|arch=!armhf 
> !i386)_Z24qMetaTypeConstructHelperI4KUrlEPvPKT_@ABI_5_1 4:15.12.1
> - (optional=templinst|arch=!armhf 
> !i386)_Z24qMetaTypeConstructHelperI9KFileItemEPvPKT_@ABI_5_1 4:15.12.1
> +#MISSING: 4:16.04.3-1# (optional=templinst|arch=!armhf 
> !i386)_Z17qRegisterMetaTypeI9KFileItemEiPKcPT_@ABI_5_1 4:15.12.1
> +#MISSING: 4:16.04.3-1# (optional=templinst|arch=!armhf 
> !i386)_Z21qMetaTypeDeleteHelperI4KUrlEvPT_@ABI_5_1 4:15.12.1
> +#MISSING: 4:16.04.3-1# (optional=templinst|arch=!armhf 
> !i386)_Z21qMetaTypeDeleteHelperI9KFileItemEvPT_@ABI_5_1 4:15.12.1
> +#MISSING: 4:16.04.3-1# (optional=templinst|arch=!armhf 
> !i386)_Z24qMetaTypeConstructHelperI4KUrlEPvPKT_@ABI_5_1 4:15.12.1
> +#MISSING: 4:16.04.3-1# (optional=templinst|arch=!armhf 
> !i386)_Z24qMetaTypeConstructHelperI9KFileItemEPvPKT_@ABI_5_1 4:15.12.1
>   _ZN12KonqMimeData16populateMimeDataEP9QMimeDataRKN4KUrl4ListES5_b@ABI_5_1 
> 4:4.6.1
>   _ZN12KonqMimeData17addIsCutSelectionEP9QMimeDatab@ABI_5_1 4:4.6.1
>   _ZN12KonqMimeData20decodeIsCutSelectionEPK9QMimeData@ABI_5_1 4:4.6.1
> @@ -90,30 +90,30 @@
>   _ZN16KonqHistoryEntryC2Ev@ABI_5_1 4:4.6.1
>   _ZN16KonqHistoryEntryD1Ev@ABI_5_1 4:4.6.1
>   _ZN16KonqHistoryEntryD2Ev@ABI_5_1 4:4.6.1
> - _ZN17KonqHistoryLoader11loadHistoryEv@ABI_5_1 4:16.04.3
> - _ZN17KonqHistoryLoader11qt_metacallEN11QMetaObject4CallEiPPv@ABI_5_1 
> 4:16.04.3
> - _ZN17KonqHistoryLoader11qt_metacastEPKc@ABI_5_1 4:16.04.3
> - _ZN17KonqHistoryLoader14historyVersionEv@ABI_5_1 4:16.04.3
> - _ZN17KonqHistoryLoader16staticMetaObjectE@ABI_5_1 4:16.04.3
> - _ZN17KonqHistoryLoaderC1EP7QObject@ABI_5_1 4:16.04.3
> - _ZN17KonqHistoryLoaderC2EP7QObject@ABI_5_1 4:16.04.3
> - _ZN17KonqHistoryLoaderD0Ev@ABI_5_1 4:16.04.3
> - _ZN17KonqHistoryLoaderD1Ev@ABI_5_1 4:16.04.3
> - _ZN17KonqHistoryLoaderD2Ev@ABI_5_1 4:16.04.3
> - _ZN18KonqCopyToMainMenu10slotBrowseEv@ABI_5_1 4:16.04.3
> - _ZN18KonqCopyToMainMenu11qt_metacallEN11QMetaObject4CallEiPPv@ABI_5_1 
> 4:16.04.3
> - _ZN18KonqCopyToMainMenu11qt_metacastEPKc@ABI_5_1 4:16.04.3
> - _ZN18KonqCopyToMainMenu12copyOrMoveToERK4KUrl@ABI_5_1 4:16.04.3
> - _ZN18KonqCopyToMainMenu13slotTriggeredEP7QAction@ABI_5_1 4:16.04.3
> - _ZN18KonqCopyToMainMenu15slotAboutToShowEv@ABI_5_1 4:16.04.3
> - _ZN18KonqCopyToMainMenu16staticMetaObjectE@ABI_5_1 4:16.04.3
> - _ZN18KonqCopyToMainMenuC1EP5QMenuP21KonqCopyToMenuPrivate8MenuType@ABI_5_1 
> 4:16.04.3
> - _ZN18KonqCopyToMainMenuC2EP5QMenuP21KonqCopyToMenuPrivate8MenuType@ABI_5_1 
> 4:16.04.3
> - _ZN18KonqCopyToMainMenuD0Ev@ABI_5_1 4:16.04.3
> - _ZN18KonqCopyToMainMenuD1Ev@ABI_5_1 4:16.04.3
> - _ZN18KonqCopyToMainMenuD2Ev@ABI_5_1 4:16.04.3
> - 
> (optional=templinst)_ZN18QAlgorithmsPrivate11qSortHelperIN5QListI16KonqHistoryEntryE8iteratorES2_PFbRKS2_S6_EEEvT_S9_RKT0_T1_@ABI_5_1
>  4:16.04.3
> - 
> (optional=templinst)_ZN18QSharedDataPointerI31KonqPopupMenuInformationPrivateE13detach_helperEv@ABI_5_1
>  4:16.04.3
> +#MISSING: 4:16.04.3-1# _ZN17KonqHistoryLoader11loadHistoryEv@ABI_5_1 
> 4:16.04.3
> +#MISSING: 4:16.04.3-1# 
> _ZN17KonqHistoryLoader11qt_metacallEN11QMetaObject4CallEiPPv@ABI_5_1 4:16.04.3
> +#MISSING: 4:16.04.3-1# _ZN17KonqHistoryLoader11qt_metacastEPKc@ABI_5_1 
> 4:16.04.3
> +#MISSING: 4:16.04.3-1# _ZN17KonqHistoryLoader14historyVersionEv@ABI_5_1 
> 4:16.04.3
> +#MISSING: 4:16.04.3-1# _ZN17KonqHistoryLoader16staticMetaObjectE@ABI_5_1 
> 4:16.04.3
> +#MISSING: 4:16.04.3-1# _ZN17KonqHistoryLoaderC1EP7QObje

Bug#835688: python-riemann-client: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13

2016-08-28 Thread Lucas Nussbaum
Source: python-riemann-client
Version: 6.3.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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 '/<>'
> dh_auto_build
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_2.7/build/riemann_client
> copying riemann_client/riemann_pb2.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/riemann_client
> copying riemann_client/command.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/riemann_client
> copying riemann_client/riemann_pb2_py3.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/riemann_client
> copying riemann_client/transport.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/riemann_client
> copying riemann_client/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/riemann_client
> copying riemann_client/riemann_pb2_py2.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/riemann_client
> copying riemann_client/client.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/riemann_client
> PYTHONPATH=. http_proxy='127.0.0.1:9' sphinx-build -N -bhtml docs/ build/html 
> # HTML generator
> Running Sphinx v1.4.6
> making output directory...
> loading pickled environment... not yet created
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 3 source files that are out of date
> updating environment: 3 added, 0 changed, 0 removed
> reading sources... [ 33%] index
> reading sources... [ 66%] riemann_client.client
> reading sources... [100%] riemann_client.transport
> 
> README.rst:71: WARNING: Title underline too short.
> 
> Testing (Linux/OSX)
> ---
> README.rst:71: WARNING: Title underline too short.
> 
> Testing (Linux/OSX)
> ---
> /<>/docs/riemann_client.client.rst:4: WARNING: autodoc: failed 
> to import module u'riemann_client.client'; the following exception was raised:
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 519, in 
> import_object
> __import__(self.modname)
>   File "/<>/riemann_client/client.py", line 27, in 
> import riemann_client.riemann_pb2
>   File "/<>/riemann_client/riemann_pb2.py", line 10, in 
> from riemann_client.riemann_pb2_py2 import (Event, Msg, Query, Attribute)
>   File "/<>/riemann_client/riemann_pb2_py2.py", line 32, in 
> 
> options=None),
>   File "/usr/lib/python2.7/dist-packages/google/protobuf/descriptor.py", line 
> 501, in __new__
> _message.Message._CheckCalledFromGeneratedFile()
> TypeError: Descriptors should not be created directly, but only retrieved 
> from their parent.
> /<>/docs/riemann_client.transport.rst:4: WARNING: autodoc: 
> failed to import module u'riemann_client.transport'; the following exception 
> was raised:
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 519, in 
> import_object
> __import__(self.modname)
>   File "/<>/riemann_client/transport.py", line 12, in 
> import riemann_client.riemann_pb2
>   File "/<>/riemann_client/riemann_pb2.py", line 10, in 
> from riemann_client.riemann_pb2_py2 import (Event, Msg, Query, Attribute)
>   File "/<>/riemann_client/riemann_pb2_py2.py", line 32, in 
> 
> options=None),
>   File "/usr/lib/python2.7/dist-packages/google/protobuf/descriptor.py", line 
> 501, in __new__
> _message.Message._CheckCalledFromGeneratedFile()
> TypeError: Descriptors should not be created directly, but only retrieved 
> from their parent.
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> writing output... [ 33%] index
> writing output... [ 66%] riemann_client.client
> writing output... [100%] riemann_client.transport
> 
> generating indices... genindex
> writing additional pages... search
> copying static files... done
> copying extra files... done
> dumping search index in English (code: en) ... done
> dumping object inventory... done
> build succeeded, 4 warnings.
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:184: cd /<>/.pybuild/pythonX.Y_2.7/build; 
> python2.7 -m pytest /<>/tests/ -v
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/dist-pa

Bug#835689: ros-image-common: FTBFS: cmake errors

2016-08-28 Thread Lucas Nussbaum
Source: ros-image-common
Version: 1.11.10-5
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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 --parallel --with=python2 --buildsystem=cmake
>dh_testdir -O--buildsystem=cmake
>dh_update_autotools_config -O--buildsystem=cmake
>dh_auto_configure -O--buildsystem=cmake
>   cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON 
> -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
> -DCMAKE_INSTALL_LOCALSTATEDIR=/var
> -- The C compiler identification is GNU 6.2.0
> -- The CXX compiler identification is GNU 6.2.0
> -- Check for working C compiler: /usr/bin/cc
> -- Check for working C compiler: /usr/bin/cc -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Check for working CXX compiler: /usr/bin/c++
> -- Check for working CXX compiler: /usr/bin/c++ -- works
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Using CATKIN_DEVEL_PREFIX: /<>/obj-x86_64-linux-gnu/devel
> -- Using CMAKE_PREFIX_PATH: 
> -- Found PythonInterp: /usr/bin/python (found version "2.7.12") 
> -- Using PYTHON_EXECUTABLE: /usr/bin/python
> -- Using Debian Python package layout
> -- Using empy: /usr/bin/empy
> -- Using CATKIN_ENABLE_TESTING: ON
> -- Call enable_testing()
> -- Using CATKIN_TEST_RESULTS_DIR: 
> /<>/obj-x86_64-linux-gnu/test_results
> -- Looking for pthread.h
> -- Looking for pthread.h - found
> -- Looking for pthread_create
> -- Looking for pthread_create - not found
> -- Looking for pthread_create in pthreads
> -- Looking for pthread_create in pthreads - not found
> -- Looking for pthread_create in pthread
> -- Looking for pthread_create in pthread - found
> -- Found Threads: TRUE  
> -- Found gtest sources under '/usr/src/gtest': gtests will be built
> CMake Warning at /usr/share/catkin/cmake/test/nosetests.cmake:98 (message):
>   nosetests not found, Python tests can not be run (try installing package
>   'python-nose')
> Call Stack (most recent call first):
>   /usr/share/catkin/cmake/all.cmake:147 (include)
>   /usr/share/catkin/cmake/catkinConfig.cmake:20 (include)
>   camera_calibration_parsers/CMakeLists.txt:4 (find_package)
> 
> 
> -- catkin 0.7.1
> -- Boost version: 1.61.0
> -- Found the following Boost libraries:
> --   filesystem
> --   python
> --   system
> -- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython2.7.so (found 
> suitable version "2.7.12+", minimum required is "2.7") 
> -- Found PkgConfig: /usr/bin/pkg-config (found version "0.29") 
> -- Checking for module 'yaml-cpp'
> --   Found yaml-cpp, version 0.3.0
> -- skipping nosetests(parser.py) in project 'camera_calibration_parsers'
> -- Using CATKIN_DEVEL_PREFIX: /<>/obj-x86_64-linux-gnu/devel
> -- Using CMAKE_PREFIX_PATH: 
> -- Using PYTHON_EXECUTABLE: /usr/bin/python
> -- Using Debian Python package layout
> -- Using empy: /usr/bin/empy
> -- Using CATKIN_ENABLE_TESTING: ON
> -- Call enable_testing()
> -- Using CATKIN_TEST_RESULTS_DIR: 
> /<>/obj-x86_64-linux-gnu/test_results
> CMake Warning at /usr/share/catkin/cmake/test/nosetests.cmake:98 (message):
>   nosetests not found, Python tests can not be run (try installing package
>   'python-nose')
> Call Stack (most recent call first):
>   /usr/share/catkin/cmake/all.cmake:147 (include)
>   /usr/share/catkin/cmake/catkinConfig.cmake:20 (include)
>   image_transport/CMakeLists.txt:4 (find_package)
> 
> 
> -- catkin 0.7.1
> -- Boost version: 1.61.0
> -- Using CATKIN_DEVEL_PREFIX: /<>/obj-x86_64-linux-gnu/devel
> -- Using CMAKE_PREFIX_PATH: 
> -- Using PYTHON_EXECUTABLE: /usr/bin/python
> -- Using Debian Python package layout
> -- Using empy: /usr/bin/empy
> -- Using CATKIN_ENABLE_TESTING: ON
> -- Call enable_testing()
> -- Using CATKIN_TEST_RESULTS_DIR: 
> /<>/obj-x86_64-linux-gnu/test_results
> CMake Warning at /usr/share/catkin/cmake/test/nosetests.cmake:98 (message):
>   nosetests not found, Python tests can not be run (try installing package
>   'python-nose')
> Call Stack (most recent call first):
>   /usr/share/catkin/cmake/all.cmake:147 (include)
>   /usr/share/catkin/cmake/catkinConfig.cmake:20 (include)
>   camera_info_manager/CMakeLists.txt:4 (find_package)
> 
> 
> 

Bug#835693: ruby-oauth2: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: expect { subject.header('get', 'this-is-not-valid') }.to raise_error(ArgumentError)

2016-08-28 Thread Lucas Nussbaum
Source: ruby-oauth2
Version: 1.2.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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):
>  Failure/Error: expect { subject.header('get', 'this-is-not-valid') }.to 
> raise_error(ArgumentError)
> 
>expected ArgumentError, got # URI::RFC3986_Parser::Generic> with backtrace:
>  # ./lib/oauth2/mac_token.rb:65:in `header'
>  # ./spec/oauth2/mac_token_spec.rb:69:in `block (4 levels) in  (required)>'
>  # ./spec/oauth2/mac_token_spec.rb:69:in `block (3 levels) in  (required)>'
>  # ./spec/oauth2/mac_token_spec.rb:69:in `block (3 levels) in  (required)>'
> 
> Finished in 0.18965 seconds (files took 0.25918 seconds to load)
> 185 examples, 4 failures
> 
> Failed examples:
> 
> rspec ./spec/oauth2/mac_token_spec.rb:78 # OAuth2::MACToken#signature 
> generates properly
> rspec ./spec/oauth2/mac_token_spec.rb:56 # OAuth2::MACToken#header does not 
> generate the same header twice
> rspec ./spec/oauth2/mac_token_spec.rb:63 # OAuth2::MACToken#header generates 
> the proper format
> rspec ./spec/oauth2/mac_token_spec.rb:68 # OAuth2::MACToken#header passes 
> ArgumentError with an invalid url
> 
> Randomized with seed 43994
> 
> /usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb failed
> ERROR: Test "ruby2.3" failed: 

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/08/28/ruby-oauth2_1.2.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#835691: libnb-platform18-java: FTBFS: ../../ide/launcher/windows/nblauncher.cpp:429:16: error: could not convert 'false' from 'bool' to 'std::__cxx11::string {aka std::__cxx11::basic_string}

2016-08-28 Thread Lucas Nussbaum
Source: libnb-platform18-java
Version: 8.1+dfsg1-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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 
> '/<>/libnb-platform18-java-8.1+dfsg1/apisupport.harness/windows-launcher-src'
> mkdir -p build/app.exe/Cygwin-Windows
> rm -f build/app.exe/Cygwin-Windows/applauncher.o.d
> i686-w64-mingw32-g++ -g -O2 
> -fdebug-prefix-map=/<>/libnb-platform18-java-8.1+dfsg1=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -I/usr/lib/jvm/java-8-openjdk-amd64/include 
> -I/usr/lib/jvm/java-8-openjdk-amd64/include/linux  -c -O2 -DARCHITECTURE=32 
> -DNBEXEC_DLL=\"/lib/nbexec.dll\" -I/usr/lib/jvm/default-java/include -MMD -MP 
> -MF build/app.exe/Cygwin-Windows/applauncher.o.d -o 
> build/app.exe/Cygwin-Windows/applauncher.o applauncher.cpp
> mkdir -p build/app.exe/Cygwin-Windows/_ext/493252820
> rm -f build/app.exe/Cygwin-Windows/_ext/493252820/utilsfuncs.o.d
> i686-w64-mingw32-g++ -g -O2 
> -fdebug-prefix-map=/<>/libnb-platform18-java-8.1+dfsg1=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -I/usr/lib/jvm/java-8-openjdk-amd64/include 
> -I/usr/lib/jvm/java-8-openjdk-amd64/include/linux  -c -O2 -DARCHITECTURE=32 
> -DNBEXEC_DLL=\"/lib/nbexec.dll\" -I/usr/lib/jvm/default-java/include -MMD -MP 
> -MF build/app.exe/Cygwin-Windows/_ext/493252820/utilsfuncs.o.d -o 
> build/app.exe/Cygwin-Windows/_ext/493252820/utilsfuncs.o 
> ../../o.n.bootstrap/launcher/windows/utilsfuncs.cpp
> mkdir -p build/app.exe/Cygwin-Windows/_ext/216238457
> rm -f build/app.exe/Cygwin-Windows/_ext/216238457/nblauncher.o.d
> i686-w64-mingw32-g++ -g -O2 
> -fdebug-prefix-map=/<>/libnb-platform18-java-8.1+dfsg1=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -I/usr/lib/jvm/java-8-openjdk-amd64/include 
> -I/usr/lib/jvm/java-8-openjdk-amd64/include/linux  -c -O2 -DARCHITECTURE=32 
> -DNBEXEC_DLL=\"/lib/nbexec.dll\" -I/usr/lib/jvm/default-java/include -MMD -MP 
> -MF build/app.exe/Cygwin-Windows/_ext/216238457/nblauncher.o.d -o 
> build/app.exe/Cygwin-Windows/_ext/216238457/nblauncher.o 
> ../../ide/launcher/windows/nblauncher.cpp
> ../../ide/launcher/windows/nblauncher.cpp: In member function 
> 'std::__cxx11::string NbLauncher::getDefaultUserDirRoot()':
> ../../ide/launcher/windows/nblauncher.cpp:429:16: error: could not convert 
> 'false' from 'bool' to 'std::__cxx11::string {aka 
> std::__cxx11::basic_string}'
>  return false;
> ^
> ../../ide/launcher/windows/nblauncher.cpp: In member function 
> 'std::__cxx11::string NbLauncher::getDefaultCacheDirRoot()':
> ../../ide/launcher/windows/nblauncher.cpp:440:16: error: could not convert 
> 'false' from 'bool' to 'std::__cxx11::string {aka 
> std::__cxx11::basic_string}'
>  return false;
> ^
> nbproject/Makefile-app.exe.mk:79: recipe for target 
> 'build/app.exe/Cygwin-Windows/_ext/216238457/nblauncher.o' failed
> make[4]: *** [build/app.exe/Cygwin-Windows/_ext/216238457/nblauncher.o] Error 
> 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/08/28/libnb-platform18-java_8.1+dfsg1-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#835692: gcc-5-cross-ports: FTBFS: patches fail to apply

2016-08-28 Thread Lucas Nussbaum
Source: gcc-5-cross-ports
Version: 10
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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
> gcc: 5.4.1-1 / 5.4.0-6cross1
> 
> old gcc version: 5.4.0-6 / 1
> 
> new gcc version: 5.4.1-1cross1
> START stamp-dir/init-gcc
> mkdir -p gcc
> set -ex; \
> cd gcc ; \
> ln -sf /usr/src/gcc-5/gcc-5.4.1.tar.xz gcc-5.4.1.tar.xz ;\
> cp -a  /usr/src/gcc-5/debian/ . ; \
> if [ -n "$(grep -v '^\#' /<>/debian/patches/gcc-5/series)" ]; 
> then \
>   QUILT_PATCHES=/<>/debian/patches/gcc-5 quilt push --quiltrc 
> /dev/null -a ; \
> fi
> + cd gcc
> + ln -sf /usr/src/gcc-5/gcc-5.4.1.tar.xz gcc-5.4.1.tar.xz
> + cp -a /usr/src/gcc-5/debian/ .
> + grep -v ^\# /<>/debian/patches/gcc-5/series
> + [ -n stripped-exes.diff ]
> + QUILT_PATCHES=/<>/debian/patches/gcc-5 quilt push --quiltrc 
> /dev/null -a
> Applying patch stripped-exes.diff
> patching file debian/rules.defs
> Hunk #1 FAILED at 376.
> 1 out of 1 hunk FAILED -- rejects in file debian/rules.defs
> Patch stripped-exes.diff can be reverse-applied
> debian/rules:216: recipe for target 'stamp-dir/init-gcc' failed
> make: *** [stamp-dir/init-gcc] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/08/28/gcc-5-cross-ports_10_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#835694: python-protobuf.socketrpc: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13

2016-08-28 Thread Lucas Nussbaum
Source: python-protobuf.socketrpc
Version: 1.3.2-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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 python2 --buildsystem=pybuild
>dh_testdir -O--buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_2.7/build/protobuf
> copying src/protobuf/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/protobuf
> creating /<>/.pybuild/pythonX.Y_2.7/build/protobuf/socketrpc
> copying src/protobuf/socketrpc/rpc_pb2.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/protobuf/socketrpc
> copying src/protobuf/socketrpc/controller.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/protobuf/socketrpc
> copying src/protobuf/socketrpc/error.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/protobuf/socketrpc
> copying src/protobuf/socketrpc/channel.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/protobuf/socketrpc
> copying src/protobuf/socketrpc/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/protobuf/socketrpc
> copying src/protobuf/socketrpc/server.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/protobuf/socketrpc
> copying src/protobuf/socketrpc/service.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/protobuf/socketrpc
> copying src/protobuf/socketrpc/logger.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/protobuf/socketrpc
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py test 
> running test
> running egg_info
> creating src/protobuf.socketrpc.egg-info
> writing src/protobuf.socketrpc.egg-info/PKG-INFO
> writing top-level names to src/protobuf.socketrpc.egg-info/top_level.txt
> writing dependency_links to 
> src/protobuf.socketrpc.egg-info/dependency_links.txt
> writing manifest file 'src/protobuf.socketrpc.egg-info/SOURCES.txt'
> reading manifest file 'src/protobuf.socketrpc.egg-info/SOURCES.txt'
> writing manifest file 'src/protobuf.socketrpc.egg-info/SOURCES.txt'
> running build_ext
> Traceback (most recent call last):
>   File "setup.py", line 53, in 
> test_suite='protobuf.socketrpc.tests',
>   File "/usr/lib/python2.7/distutils/core.py", line 151, in setup
> dist.run_commands()
>   File "/usr/lib/python2.7/distutils/dist.py", line 953, in run_commands
> self.run_command(cmd)
>   File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
> cmd_obj.run()
>   File "/usr/lib/python2.7/dist-packages/setuptools/command/test.py", line 
> 172, in run
> self.run_tests()
>   File "/usr/lib/python2.7/dist-packages/setuptools/command/test.py", line 
> 193, in run_tests
> testRunner=self._resolve_as_ep(self.test_runner),
>   File "/usr/lib/python2.7/unittest/main.py", line 94, in __init__
> self.parseArgs(argv)
>   File "/usr/lib/python2.7/unittest/main.py", line 149, in parseArgs
> self.createTests()
>   File "/usr/lib/python2.7/unittest/main.py", line 158, in createTests
> self.module)
>   File "/usr/lib/python2.7/unittest/loader.py", line 130, in 
> loadTestsFromNames
> suites = [self.loadTestsFromName(name, module) for name in names]
>   File "/usr/lib/python2.7/unittest/loader.py", line 103, in loadTestsFromName
> return self.loadTestsFromModule(obj)
>   File "/usr/lib/python2.7/dist-packages/setuptools/command/test.py", line 
> 40, in loadTestsFromModule
> tests.append(self.loadTestsFromName(submodule))
>   File "/usr/lib/python2.7/unittest/loader.py", line 91, in loadTestsFromName
> module = __import__('.'.join(parts_copy))
>   File "/<>/src/protobuf/socketrpc/tests/service_test.py", line 
> 45, in 
> import fake
>   File "/<>/src/protobuf/socketrpc/tests/fake.py", line 39, in 
> 
> import test_pb2
>   File "/<>/src/protobuf/socketrpc/tests/test_pb2.py", line 15, 
> in 
> 
> serialized_pb='\n\ntest.proto\x12\x12protobuf.socketrpc\"\x1b\n\x07Request\x12\x10\n\x08str_data\x18\x01
>  \x02(\t\".\n\x08Response\x12\x10\n\x08str_data\x18\x01 
> \x02(\t\x12\x10\n\x08int_data\x18\x02 
> \x01(\x05

Bug#835687: plasma-sdk: FTBFS: dh_install: missing files, aborting

2016-08-28 Thread Lucas Nussbaum
Source: plasma-sdk
Version: 5.7.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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 '/<>/obj-x86_64-linux-gnu'
> make[4]: Nothing to be done for 'preinstall'.
> make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> Install the project...
> /usr/bin/cmake -P cmake_install.cmake
> -- Install configuration: "Debian"
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ar/LC_MESSAGES/org.kde.plasma.themeexplorer.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ar/LC_MESSAGES/plasma_shell_org.kde.plasmoidviewershell.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ar/LC_MESSAGES/plasmaengineexplorer.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ar/LC_MESSAGES/plasmawallpaperviewer.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ar/LC_MESSAGES/plasmoidviewer.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ar/LC_MESSAGES/remote-widgets-browser.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ast/LC_MESSAGES/cuttlefish.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ast/LC_MESSAGES/cuttlefish_editorplugin.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ast/LC_MESSAGES/kdevpackagemanagerview.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ast/LC_MESSAGES/org.kde.plasma.themeexplorer.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ast/LC_MESSAGES/plasma_shell_org.kde.plasmoidviewershell.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ast/LC_MESSAGES/plasmaengineexplorer.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ast/LC_MESSAGES/plasmate.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ast/LC_MESSAGES/plasmawallpaperviewer.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ast/LC_MESSAGES/plasmoidviewer.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ast/LC_MESSAGES/remote-widgets-browser.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/be/LC_MESSAGES/plasmaengineexplorer.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/be@latin/LC_MESSAGES/plasmaengineexplorer.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/be@latin/LC_MESSAGES/plasmoidviewer.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/bg/LC_MESSAGES/plasmaengineexplorer.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/bg/LC_MESSAGES/plasmoidviewer.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/bg/LC_MESSAGES/remote-widgets-browser.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/bn_IN/LC_MESSAGES/plasmaengineexplorer.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/bn_IN/LC_MESSAGES/plasmoidviewer.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/bs/LC_MESSAGES/plasmaengineexplorer.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/bs/LC_MESSAGES/plasmate.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/bs/LC_MESSAGES/plasmawallpaperviewer.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/bs/LC_MESSAGES/plasmoidviewer.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/bs/LC_MESSAGES/remote-widgets-browser.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ca/LC_MESSAGES/cuttlefish.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ca/LC_MESSAGES/cuttlefish_editorplugin.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ca/LC_MESSAGES/kdevpackagemanagerview.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ca/LC_MESSAGES/org.kde.plasma.themeexplorer.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ca/LC_MESSAGES/plasma_shell_org.kde.plasmoidviewershell.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ca/LC_MESSAGES/plasmaengineexplorer.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ca/LC_MESSAGES/plasmate.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ca/LC_MESSAGES/plasmawallpaperviewer.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ca/LC_MESSAGES/plasmoidviewer.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ca/LC_MESSAGES/remote-widgets-browser.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ca@valencia/LC_MESSAGES/cuttlefish.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ca@valencia/LC_MESSAGES/cuttlefish_editorplugin.mo
> -- Installing: 
> /<>/debian/tmp/usr/share/locale/ca@valencia/LC_MESSAGES/kdevpackagema

Bug#835699: d-shlibs: FTBFS: tests failures

2016-08-28 Thread Lucas Nussbaum
Source: d-shlibs
Version: 0.75
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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 '/<>'
> bash -n d-shlibmove
> bash -n d-devlibdeps
> shellcheck d-shlibmove
> 
> In d-shlibmove line 238:
> while read A B; do
>   ^-- SC2162: read without -r will mangle backslashes.
> 
> 
> In d-shlibmove line 245:
> while read A B; do
>   ^-- SC2162: read without -r will mangle backslashes.
> 
> Makefile:8: recipe for target 'check' failed
> make[1]: *** [check] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/08/28/d-shlibs_0.75_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#835697: yowsup: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13

2016-08-28 Thread Lucas Nussbaum
Source: yowsup
Version: 2.4.103-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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 python2 --buildsystem pybuild
>dh_testdir -O--buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_2.7/build/yowsup
> copying yowsup/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/yowsup
> creating /<>/.pybuild/pythonX.Y_2.7/build/yowsup/registration
> copying yowsup/registration/existsrequest.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/yowsup/registration
> copying yowsup/registration/regrequest.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/yowsup/registration
> copying yowsup/registration/coderequest.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/yowsup/registration
> copying yowsup/registration/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/yowsup/registration
> creating /<>/.pybuild/pythonX.Y_2.7/build/yowsup/structs
> copying yowsup/structs/protocoltreenode.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/yowsup/structs
> copying yowsup/structs/protocolentity.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/yowsup/structs
> copying yowsup/structs/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/yowsup/structs
> creating /<>/.pybuild/pythonX.Y_2.7/build/yowsup/layers
> copying yowsup/layers/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/yowsup/layers
> creating /<>/.pybuild/pythonX.Y_2.7/build/yowsup/common
> copying yowsup/common/constants.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/yowsup/common
> copying yowsup/common/optionalmodules.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/yowsup/common
> copying yowsup/common/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/yowsup/common
> copying yowsup/common/tools.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/yowsup/common
> creating /<>/.pybuild/pythonX.Y_2.7/build/yowsup/env
> copying yowsup/env/test_env_s40.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/yowsup/env
> copying yowsup/env/env_android.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/yowsup/env
> copying yowsup/env/env_s40.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/yowsup/env
> copying yowsup/env/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/yowsup/env
> copying yowsup/env/env.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/yowsup/env
> creating /<>/.pybuild/pythonX.Y_2.7/build/yowsup/stacks
> copying yowsup/stacks/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/yowsup/stacks
> copying yowsup/stacks/yowstack.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/yowsup/stacks
> creating /<>/.pybuild/pythonX.Y_2.7/build/yowsup/demos
> copying yowsup/demos/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/yowsup/demos
> creating 
> /<>/.pybuild/pythonX.Y_2.7/build/yowsup/layers/protocol_presence
> copying yowsup/layers/protocol_presence/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/yowsup/layers/protocol_presence
> copying yowsup/layers/protocol_presence/layer.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/yowsup/layers/protocol_presence
> creating 
> /<>/.pybuild/pythonX.Y_2.7/build/yowsup/layers/protocol_profiles
> copying yowsup/layers/protocol_profiles/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/yowsup/layers/protocol_profiles
> copying yowsup/layers/protocol_profiles/layer.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/yowsup/layers/protocol_profiles
> creating 
> /<>/.pybuild/pythonX.Y_2.7/build/yowsup/layers/protocol_privacy
> copying yowsup/layers/protocol_privacy/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/yowsup/layers/protocol_privacy
> copying yowsup/layers/protocol_privacy/layer.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/yowsup/layers/protocol_privacy
> creating 
> /<>/.pybuild/pythonX.Y_2.7/build/yowsup/layers/protocol_iq
> copying yowsup/layers/protocol_iq/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/yowsup/layers/protocol_iq
> copying yowsup/layers/protocol_iq/layer.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/yowsup/layers/protocol_iq
> creating /<>/.pybuild/pythonX.Y_2.7/build/yowsup/layers/coder
>

Bug#835695: android-platform-development: FTBFS: ld: cannot find -lETC1

2016-08-28 Thread Lucas Nussbaum
Source: android-platform-development
Version: 6.0.1+r16-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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++ tools/etc1tool/etc1tool.cpp -o etc1tool -g -O2 
> -fdebug-prefix-map=/<>/android-platform-development-6.0.1+r16=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Iinclude -I/usr/include/android -include 
> android/arch/AndroidConfig.h -Wl,-z,relro -Wl,-rpath=/usr/lib/android -lpng 
> -L/usr/lib/android -lETC1
> tools/etc1tool/etc1tool.cpp: In function 'void 
> multipleEncodeDecodeCheck(bool*)':
> tools/etc1tool/etc1tool.cpp:477:94: warning: ISO C++ forbids converting a 
> string constant to 'char*' [-Wwrite-strings]
>  usage("At most one occurrence of --encode --encodeNoHeader or 
> --decode is allowed.\n");
>   
> ^
> tools/etc1tool/etc1tool.cpp: In function 'int main(int, char**)':
> tools/etc1tool/etc1tool.cpp:502:54: warning: ISO C++ forbids converting a 
> string constant to 'char*' [-Wwrite-strings]
>  usage("Only one -o flag allowed.");
>   ^
> tools/etc1tool/etc1tool.cpp:505:54: warning: ISO C++ forbids converting a 
> string constant to 'char*' [-Wwrite-strings]
>  usage("Expected outfile after -o");
>   ^
> tools/etc1tool/etc1tool.cpp:523:76: warning: ISO C++ forbids converting a 
> string constant to 'char*' [-Wwrite-strings]
>  usage("Only one --showDifference option allowed.\n");
> ^
> tools/etc1tool/etc1tool.cpp:527:73: warning: ISO C++ forbids converting a 
> string constant to 'char*' [-Wwrite-strings]
>  usage("Expected difffile after --showDifference");
>  ^
> tools/etc1tool/etc1tool.cpp:533:50: warning: ISO C++ forbids converting a 
> string constant to 'char*' [-Wwrite-strings]
>  usage("Unknown flag %s", pArg);
>   ^
> tools/etc1tool/etc1tool.cpp:538:46: warning: ISO C++ forbids converting a 
> string constant to 'char*' [-Wwrite-strings]
>  usage("Unknown flag %s", pArg);
>   ^
> tools/etc1tool/etc1tool.cpp:545:37: warning: ISO C++ forbids converting a 
> string constant to 'char*' [-Wwrite-strings]
>  pInput, pArg);
>  ^
> tools/etc1tool/etc1tool.cpp:556:62: warning: ISO C++ forbids converting a 
> string constant to 'char*' [-Wwrite-strings]
>  usage("--showDifference is only valid when encoding.");
>   ^
> tools/etc1tool/etc1tool.cpp:560:40: warning: ISO C++ forbids converting a 
> string constant to 'char*' [-Wwrite-strings]
>  usage("Expected an input file.");
> ^
> tools/etc1tool/etc1tool.cpp:569:80: warning: ISO C++ forbids converting a 
> string constant to 'char*' [-Wwrite-strings]
>  usage("Could not change extension of input file name: %s\n", 
> pInput);
>   
>   ^
> /usr/bin/ld: cannot find -lETC1
> collect2: error: ld returned 1 exit status

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/08/28/android-platform-development_6.0.1+r16-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#835696: ros-actionlib: FTBFS: cmake errors

2016-08-28 Thread Lucas Nussbaum
Source: ros-actionlib
Version: 1.11.6-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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 '/<>'
> dh_auto_configure -- \
> -DCATKIN_ENABLE_TESTING=OFF
>   cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON 
> -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
> -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCATKIN_ENABLE_TESTING=OFF
> -- The C compiler identification is GNU 6.2.0
> -- The CXX compiler identification is GNU 6.2.0
> -- Check for working C compiler: /usr/bin/cc
> -- Check for working C compiler: /usr/bin/cc -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Check for working CXX compiler: /usr/bin/c++
> -- Check for working CXX compiler: /usr/bin/c++ -- works
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Using CATKIN_DEVEL_PREFIX: /<>/obj-x86_64-linux-gnu/devel
> -- Using CMAKE_PREFIX_PATH: 
> -- Found PythonInterp: /usr/bin/python (found version "2.7.12") 
> -- Using PYTHON_EXECUTABLE: /usr/bin/python
> -- Using Debian Python package layout
> -- Using empy: /usr/bin/empy
> -- Using CATKIN_ENABLE_TESTING: OFF
> -- catkin 0.7.1
> -- Using these message generators: gencpp;genlisp;genpy
> -- Looking for pthread.h
> -- Looking for pthread.h - found
> -- Looking for pthread_create
> -- Looking for pthread_create - not found
> -- Looking for pthread_create in pthreads
> -- Looking for pthread_create in pthreads - not found
> -- Looking for pthread_create in pthread
> -- Looking for pthread_create in pthread - found
> -- Found Threads: TRUE  
> -- Boost version: 1.61.0
> -- Found the following Boost libraries:
> --   thread
> --   chrono
> --   system
> --   date_time
> --   atomic
> -- Generating .msg files for action actionlib/Test 
> /<>/action/Test.action
> Generating for action Test
> -- Generating .msg files for action actionlib/TestRequest 
> /<>/action/TestRequest.action
> Generating for action TestRequest
> -- Generating .msg files for action actionlib/TwoInts 
> /<>/action/TwoInts.action
> Generating for action TwoInts
> CMake Error at obj-x86_64-linux-gnu/cmake/actionlib-genmsg.cmake:3 (message):
>   Could not find messages which
>   
> '/<>/obj-x86_64-linux-gnu/devel/share/actionlib/msg/TestAction.msg'
>   depends on.  Did you forget to specify generate_messages(DEPENDENCIES ...)?
> 
>   Cannot locate message [Header] in package [std_msgs] with paths
>   [['/usr/share/std_msgs/cmake/../msg']]
> Call Stack (most recent call first):
>   /usr/share/genmsg/cmake/genmsg-extras.cmake:306 (include)
>   CMakeLists.txt:13 (generate_messages)
> 
> 
> -- Configuring incomplete, errors occurred!
> See also "/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log".
> See also "/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeError.log".
>   "tail -v -n +0 CMakeCache.txt"
> ==> CMakeCache.txt <==
> # This is the CMakeCache file.
> # For build in directory: /<>/obj-x86_64-linux-gnu
> # It was generated by CMake: /usr/bin/cmake
> # You can edit this file to change values found and used by cmake.
> # If you do not want to change any of the values, simply exit the editor.
> # If you do want to change a value, simply edit, save, and exit the editor.
> # The syntax for the file is as follows:
> # KEY:TYPE=VALUE
> # KEY is the name of a variable in the cache.
> # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!.
> # VALUE is the current value for the KEY.
> 
> 
> # EXTERNAL cache entries
> 
> 
> //The threading library used by boost-thread
> BOOST_THREAD_LIBRARY:FILEPATH=/usr/lib/x86_64-linux-gnu/libpthread.so
> 
> //Build dynamically-linked binaries
> BUILD_SHARED_LIBS:BOOL=ON
> 
> //Boost atomic library (debug)
> Boost_ATOMIC_LIBRARY_DEBUG:FILEPATH=/usr/lib/x86_64-linux-gnu/libboost_atomic.so
> 
> //Boost atomic library (release)
> Boost_ATOMIC_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libboost_atomic.so
> 
> //Boost chrono library (debug)
> Boost_CHRONO_LIBRARY_DEBUG:FILEPATH=/usr/lib/x86_64-linux-gnu/libboost_chrono.so
> 
> //Boost chrono library (release)
> Boost_CHRONO_LIBRARY_RELEASE:FILEPATH=/usr/lib/x86_64-linux-gnu/libboost_chro

Bug#835701: tcpwatch-httpproxy: FTBFS: ImportError: No module named setuptools

2016-08-28 Thread Lucas Nussbaum
Source: tcpwatch-httpproxy
Version: 1.3.1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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
> dh clean 
>dh_testdir
>dh_auto_clean
> pyversions: missing X(S)-Python-Version in control file, fall back to 
> debian/pyversions
> pyversions: missing debian/pyversions file, fall back to supported versions
>   python setup.py clean -a
> Traceback (most recent call last):
>   File "setup.py", line 1, in 
> from setuptools import setup
> ImportError: No module named setuptools
> dh_auto_clean: python setup.py clean -a returned exit code 1
> debian/rules:22: recipe for target 'clean' failed
> make: *** [clean] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/08/28/tcpwatch-httpproxy_1.3.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#835700: python-oauth2client: FTBFS: Tests failures

2016-08-28 Thread Lucas Nussbaum
Source: python-oauth2client
Version: 3.0.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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):
> Traceback (most recent call last):
>   File "tests/test_service_account.py", line 80, in test_sign_blob
> private_key_id, signature = self.credentials.sign_blob('Google')
>   File "/<>/oauth2client/service_account.py", line 401, in 
> sign_blob
> return self._private_key_id, self._signer.sign(blob)
>   File "/<>/oauth2client/_openssl_crypt.py", line 97, in sign
> return crypto.sign(self._key, message, 'sha256')
>   File "/usr/lib/python2.7/dist-packages/OpenSSL/crypto.py", line 2563, in 
> sign
> md_ctx = _ffi.new("EVP_MD_CTX*")
> TypeError: cannot instantiate ctype 'EVP_MD_CTX' of unknown size
> 
> --
> Ran 539 tests in 4.575s
> 
> FAILED (SKIP=1, errors=31)
> debian/rules:29: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/08/28/python-oauth2client_3.0.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#835702: seahorse-nautilus: FTBFS: conftest.c:64:20: error: expected expression before ')' token

2016-08-28 Thread Chris Lamb
Source: seahorse-nautilus
Version: 3.11.92-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

seahorse-nautilus fails to build from source in unstable/amd64:

  [..]

  lt_cv_path_mainfest_tool=no
  lt_cv_prog_compiler_c_o=yes
  lt_cv_prog_compiler_pic='-fPIC -DPIC'
  lt_cv_prog_compiler_pic_works=yes
  lt_cv_prog_compiler_rtti_exceptions=no
  lt_cv_prog_compiler_static_works=yes
  lt_cv_prog_gnu_ld=yes
  lt_cv_sharedlib_from_linklib_cmd='printf %s\n'
  lt_cv_shlibpath_overrides_runpath=no
  lt_cv_sys_global_symbol_pipe='sed -n -e '\''s/^.*[ 
]\([ABCDGIRSTW][ABCDGIRSTW]*\)[ ][  
]*\([_A-Za-z][_A-Za-z0-9]*\)$/\1 \2 \2/p'\'' | sed '\''/ __gnu_lto/d'\'''
  lt_cv_sys_global_symbol_to_c_name_address='sed -n -e '\''s/^: \([^ ]*\)[ ]*$/ 
 {\"\1\", (void *) 0},/p'\'' -e '\''s/^[ABCDGIRSTW]* \([^ ]*\) \([^ ]*\)$/  
{"\2", (void *) \&\2},/p'\'''
  lt_cv_sys_global_symbol_to_c_name_address_lib_prefix='sed -n -e '\''s/^: \([^ 
]*\)[ ]*$/  {\"\1\", (void *) 0},/p'\'' -e '\''s/^[ABCDGIRSTW]* \([^ ]*\) 
\(lib[^ ]*\)$/  {"\2", (void *) \&\2},/p'\'' -e '\''s/^[ABCDGIRSTW]* \([^ ]*\) 
\([^ ]*\)$/  {"lib\2", (void *) \&\2},/p'\'''
  lt_cv_sys_global_symbol_to_cdecl='sed -n -e '\''s/^T .* \(.*\)$/extern int 
\1();/p'\'' -e '\''s/^[ABCDGIRSTW]* .* \(.*\)$/extern char \1;/p'\'''
  lt_cv_sys_max_cmd_len=1572864
  lt_cv_to_host_file_cmd=func_convert_file_noop
  lt_cv_to_tool_file_cmd=func_convert_file_noop
  pkg_cv_GTK_CFLAGS='-pthread -I/usr/include/gtk-3.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libpng16 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include'
  pkg_cv_GTK_LIBS='-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'
  
  ## - ##
  ## Output variables. ##
  ## - ##
  
  
  
  
  
  
  
  
  
  
$(INSTALL_DATA) $^ "$(DESTDIR)$(gsettingsschemadir)"; \
test -n "$(GSETTINGS_DISABLE_SCHEMAS_COMPILE)$(DESTDIR)" || 
$(GLIB_COMPILE_SCHEMAS) $(gsettingsschemadir); \
test -z "$(gsettingsschemadir)" || $(MKDIR_P) 
"$(DESTDIR)$(gsettingsschemadir)"; \
$(AM_V_GEN) glib-mkenums --comments '\'''\'' --fhead 
"" --vhead "  <@type@ 
id='\''$(gsettings_ENUM_NAMESPACE).@EnumName@'\''>" --vprod "" --vtail "  " 
--ftail "" $^ > $@.tmp && mv $@.tmp $@
$(AM_V_GEN) if test -f "$<"; then d=; else d="$(srcdir)/"; fi; 
$(GLIB_COMPILE_SCHEMAS) --strict --dry-run $(addprefix 
--schema-file=,$(gsettings__enum_file)) --schema-file=$${d}$< && touch $@
@$(NORMAL_INSTALL)
@$(NORMAL_UNINSTALL)
@list='\''$(gsettings_SCHEMAS) $(gsettings__enum_file)'\''; test -n 
"$(gsettingsschemadir)" || list=; \
cd "$(DESTDIR)$(gsettingsschemadir)" && rm -f $$files
echo " ( cd '\''$(DESTDIR)$(gsettingsschemadir)'\'' && rm -f" $$files 
")"; \
fi
files=`for p in $$list; do echo $$p; done | sed -e '\''s|^.*/||'\''`; \
if test -n "$^"; then \
rm -f $(gsettings_SCHEMAS:.xml=.valid) $(gsettings__enum_file)
test -n "$$files" || exit 0; \
test -n "$(GSETTINGS_DISABLE_SCHEMAS_COMPILE)$(DESTDIR)" || 
$(GLIB_COMPILE_SCHEMAS) $(gsettingsschemadir)
  $(gsettings__enum_file): $(gsettings_ENUM_FILES)
  %.gschema.valid: %.gschema.xml $(gsettings__enum_file)
  .PHONY : uninstall-gsettings-schemas install-gsettings-schemas 
clean-gsettings-schemas
  .SECONDARY: $(gsettings_SCHEMAS)
  ACLOCAL='${SHELL} 
/home/lamby/temp/cdt.20160828113213.alq6ysZNSk.db.seahorse-nautilus/seahorse-nautilus-3.11.92/missing
 aclocal-1.13'
  ALL_LINGUAS=''
  AMDEPBACKSLASH=''
  AMDEP_FALSE=''
  AMDEP_TRUE='#'
  AMTAR='$${TAR-tar}'
  AM_BACKSLASH='\'
  AM_DEFAULT_V='$(AM_DEFAULT_VERBOSITY)'
  AM_DEFAULT_VERBOSITY='1'
  AM_V='$(V)'
  AR='ar'
  AUTOCONF='${SHELL} 
/home/lamby/temp/cdt.20160828113213.alq6ysZNSk.db.seahorse-nautilus/seahorse-nautilus-3.11.92/missing
 autoconf'
  AUTOHEADER='${SHELL} 
/home/lamby/temp/cdt.20160828113213.alq6ysZNSk.db.seahorse-nautilus/seahorse-nautilus-3.11.92/missing
 autoheader'
  AUTOMAKE='${SHELL} 
/home/lamby/temp/cdt.20160828113213.alq6ysZNSk.db.seahorse-nautilus/seahorse-nautilus-3.11.92/missing
 automake-1.13'
  AWK='mawk'
  CATALOGS=''
  CATOBJEXT='.gmo'
  CC='gcc'
  CCDEPMODE='depmode=none'
  CFLAGS='-g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20160828113213.alq6ysZNSk.db.seahorse-nautilus/seahorse-nautilus-3.11.92=.
 -fstack-

Bug#835704: node-ast-util: FTBFS: Error: Cannot find module './fork'

2016-08-28 Thread Lucas Nussbaum
Source: node-ast-util
Version: 0.6.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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 '/<>'
> ./bin/make-builder < helpers/get.js >> lib/helpers/get.js
> module.js:327
> throw err;
> ^
> 
> Error: Cannot find module './fork'
> at Function.Module._resolveFilename (module.js:325:15)
> at Function.Module._load (module.js:276:25)
> at Module.require (module.js:353:17)
> at require (internal/module.js:12:17)
> at Object. (/usr/lib/nodejs/ast-types/main.js:1:80)
> at Module._compile (module.js:409:26)
> at Object.Module._extensions..js (module.js:416:10)
> at Module.load (module.js:343:32)
> at Function.Module._load (module.js:300:12)
> at Module.require (module.js:353:17)
> Makefile:6: recipe for target 'lib/helpers/get.js' failed
> make[1]: *** [lib/helpers/get.js] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/08/28/node-ast-util_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#835711: libconfig-identity-perl: FTBFS: Tests failures

2016-08-28 Thread Lucas Nussbaum
Source: libconfig-identity-perl
Version: 0.0018-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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):
> ok 1
> ok 2
> ok 3
> ok 4
> 1..4
> Dubious, test returned 255 (wstat 65280, 0xff00)
> All 4 subtests passed 
> 
> Test Summary Report
> ---
> t/01-basic.t (Wstat: 65280 Tests: 4 Failed: 0)
>   Non-zero exit status: 255
> Files=1, Tests=4,  1 wallclock secs ( 0.01 usr  0.00 sys +  0.06 cusr  0.00 
> csys =  0.07 CPU)
> Result: FAIL
> Failed 1/1 test programs. 0/4 subtests failed.
> Makefile:830: recipe for target 'test_dynamic' failed

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/08/28/libconfig-identity-perl_0.0018-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#835703: nut: FTBFS: dh_makeshlibs: failing due to earlier errors

2016-08-28 Thread Lucas Nussbaum
Source: nut
Version: 2.7.4-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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 'install-exec-am'.
> make[3]: Nothing to be done for 'install-data-am'.
> make[3]: Leaving directory '/<>'
> make[2]: Leaving directory '/<>'
> make[1]: Leaving directory '/<>'
> touch debian/stamp-makefile-install
> #install documentation
> mkdir -p /<>/debian/tmp/usr/share/doc/nut-doc/pdf
> mkdir -p /<>/debian/tmp/usr/share/doc/nut-doc/html
> cp /<>/docs/*.pdf 
> /<>/debian/tmp/usr/share/doc/nut-doc/pdf
> cp /<>/docs/FAQ.html 
> /<>/debian/tmp/usr/share/doc/nut-doc/html
> for f in /<>/docs/*.chunked/; do \
>   nf=`basename ${f} | sed 's/\(.*\)\.chunked/\1/'`; \
>   cp -a ${f} 
> /<>/debian/tmp/usr/share/doc/nut-doc/html/${nf}/; \
> done
> Adding cdbs dependencies to debian/nut.substvars
> dh_installdirs -pnut \
>   
> Adding cdbs dependencies to debian/nut-doc.substvars
> dh_installdirs -pnut-doc \
>   
> Adding cdbs dependencies to debian/python-nut.substvars
> dh_installdirs -ppython-nut \
>   
> Adding cdbs dependencies to debian/nut-monitor.substvars
> dh_installdirs -pnut-monitor \
>   
> Adding cdbs dependencies to debian/libups-nut-perl.substvars
> dh_installdirs -plibups-nut-perl \
>   
> dh_installdocs -pnut ./README ./NEWS ./TODO ./AUTHORS
> dh_installexamples -pnut 
> dh_installman -pnut 
> dh_installinfo -pnut 
> dh_installmenu -pnut 
> dh_installcron -pnut 
> dh_systemd_enable -pnut 
> dh_installinit -pnut 
> dh_installdebconf -pnut 
> dh_installemacsen -pnut 
> dh_installcatalogs -pnut 
> dh_installpam -pnut 
> dh_installlogrotate -pnut 
> dh_installlogcheck -pnut 
> dh_installchangelogs -pnut ./ChangeLog
> dh_installudev -pnut 
> dh_lintian -pnut 
> dh_bugfiles -pnut 
> dh_install -pnut 
> dh_systemd_start -pnut 
> dh_link -pnut 
> dh_installmime -pnut 
> dh_installgsettings -pnut 
> dh_installdocs -pnut-doc ./README ./NEWS ./TODO ./AUTHORS
> dh_installexamples -pnut-doc 
> dh_installman -pnut-doc 
> dh_installinfo -pnut-doc 
> dh_installmenu -pnut-doc 
> dh_installcron -pnut-doc 
> dh_systemd_enable -pnut-doc 
> dh_installinit -pnut-doc 
> dh_installdebconf -pnut-doc 
> dh_installemacsen -pnut-doc 
> dh_installcatalogs -pnut-doc 
> dh_installpam -pnut-doc 
> dh_installlogrotate -pnut-doc 
> dh_installlogcheck -pnut-doc 
> dh_installchangelogs -pnut-doc ./ChangeLog
> dh_installudev -pnut-doc 
> dh_lintian -pnut-doc 
> dh_bugfiles -pnut-doc 
> dh_install -pnut-doc 
> dh_systemd_start -pnut-doc 
> dh_link -pnut-doc 
> dh_installmime -pnut-doc 
> dh_installgsettings -pnut-doc 
> dh_installdocs -ppython-nut ./README ./NEWS ./TODO ./AUTHORS
> dh_installexamples -ppython-nut 
> dh_installman -ppython-nut 
> dh_installinfo -ppython-nut 
> dh_installmenu -ppython-nut 
> dh_installcron -ppython-nut 
> dh_systemd_enable -ppython-nut 
> dh_installinit -ppython-nut 
> dh_installdebconf -ppython-nut 
> dh_installemacsen -ppython-nut 
> dh_installcatalogs -ppython-nut 
> dh_installpam -ppython-nut 
> dh_installlogrotate -ppython-nut 
> dh_installlogcheck -ppython-nut 
> dh_installchangelogs -ppython-nut ./ChangeLog
> dh_installudev -ppython-nut 
> dh_lintian -ppython-nut 
> dh_bugfiles -ppython-nut 
> dh_install -ppython-nut 
> dh_systemd_start -ppython-nut 
> dh_link -ppython-nut 
> dh_installmime -ppython-nut 
> dh_installgsettings -ppython-nut 
> dh_python2 -ppython-nut 
> dh_installdocs -pnut-monitor ./README ./NEWS ./TODO ./AUTHORS
> dh_installexamples -pnut-monitor 
> dh_installman -pnut-monitor 
> dh_installinfo -pnut-monitor 
> dh_installmenu -pnut-monitor 
> dh_installcron -pnut-monitor 
> dh_systemd_enable -pnut-monitor 
> dh_installinit -pnut-monitor 
> dh_installdebconf -pnut-monitor 
> dh_installemacsen -pnut-monitor 
> dh_installcatalogs -pnut-monitor 
> dh_installpam -pnut-monitor 
> dh_installlogrotate -pnut-monitor 
> dh_installlogcheck -pnut-monitor 
> dh_installchangelogs -pnut-monitor ./ChangeLog
> dh_installudev -pnut-monitor 
> dh_lintian -pnut-monitor 
> dh_bugfiles -pnut-monitor 
> dh_install -pnut-monitor 
> dh_systemd_start -pnut-monitor 
> dh_link -pnut-monitor 
> dh_installmime -pnut-monitor 
> dh_installgsettings -pnut-monitor 
> dh_python2 -pnut-monitor
> I: dh_python2 tools:100: re

Bug#835705: umbrello: FTBFS: dh_install: missing files, aborting

2016-08-28 Thread Lucas Nussbaum
Source: umbrello
Version: 4:16.04.2-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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 '/<>/obj-x86_64-linux-gnu'
> make[4]: Nothing to be done for 'preinstall'.
> make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> Install the project...
> /usr/bin/cmake -P cmake_install.cmake
> -- Install configuration: "Debian"
> -- Installing: /<>/debian/tmp/usr/bin/umbrello
> -- Installing: 
> /<>/debian/tmp/usr/share/applications/org.kde.umbrello.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/metainfo/org.kde.umbrello.appdata.xml
> -- Installing: 
> /<>/debian/tmp/usr/share/kxmlgui5/umbrello/umbrelloui.rc
> -- Installing: /<>/debian/tmp/usr/share/umbrello/xmi2docbook.xsl
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/docbook2xhtml.xsl
> -- Installing: /<>/debian/tmp/usr/share/umbrello/xmi.css
> -- Installing: /<>/debian/tmp/usr/share/umbrello/common.ent
> -- Installing: /<>/debian/tmp/usr/share/umbrello/layouts
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/layouts/class-vertical.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/layouts/activity-vertical.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/layouts/class-horizontal.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/layouts/activity-export.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/layouts/usecase-default.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/layouts/state-vertical.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/layouts/state-export.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/layouts/class-export.desktop
> -- Installing: /<>/debian/tmp/usr/share/umbrello/pics/actor.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/aggregation.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/align-horizontal-left.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/align-horizontal-right.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/align-vertical-top.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/align-vertical-bottom.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/align-vertical-center.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/align-horizontal-center.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/distribute-vertical.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/distribute-horizontal.png
> -- Installing: /<>/debian/tmp/usr/share/umbrello/pics/anchor.png
> -- Installing: /<>/debian/tmp/usr/share/umbrello/pics/andline.png
> -- Installing: /<>/debian/tmp/usr/share/umbrello/pics/arrow.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/association.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/choice-rhomb.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/choice-round.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/combined_fragment.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/component.png
> -- Installing: /<>/debian/tmp/usr/share/umbrello/pics/region.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/composition.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/containment.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/CVglobal_meth.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/CVglobal_var.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/CVimplementation_meth.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/CVimplementation_signal.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/CVimplementation_slot.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/CVimplementation_var.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/CVnamespace.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/CVprivate_meth.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/CVprivate_signal.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/CVprivate_slot.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/CVprivate_var.png
> -- Installin

Bug#835708: plplot: FTBFS: Tests failures

2016-08-28 Thread Lucas Nussbaum
Source: plplot
Version: 5.10.0+dfsg2-0.3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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):
> x15c
> x16c
> x18c
> x19c
> x20c
> No such fileexamples/CMakeFiles/test_c_psc.dir/build.make:161: recipe for 
> target 'examples/x01c.psc' failed
> make[4]: *** [examples/x01c.psc] Error 1
> make[4]: *** Deleting file 'examples/x01c.psc'
> make[4]: Leaving directory 
> '/<>/plplot-5.10.0+dfsg2/debian/build_tmp'
> CMakeFiles/Makefile2:4661: recipe for target 
> 'examples/CMakeFiles/test_c_psc.dir/all' failed
> make[3]: *** [examples/CMakeFiles/test_c_psc.dir/all] Error 2
> make[3]: Leaving directory 
> '/<>/plplot-5.10.0+dfsg2/debian/build_tmp'
> CMakeFiles/Makefile2:6180: recipe for target 
> 'examples/CMakeFiles/test_noninteractive.dir/rule' failed
> make[2]: *** [examples/CMakeFiles/test_noninteractive.dir/rule] Error 2
> make[2]: Leaving directory 
> '/<>/plplot-5.10.0+dfsg2/debian/build_tmp'
> Makefile:1911: recipe for target 'test_noninteractive' failed

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/08/28/plplot_5.10.0+dfsg2-0.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#835710: netcdf: FTBFS: nc4internal.h:18:18: fatal error: hdf5.h: No such file or directory

2016-08-28 Thread Lucas Nussbaum
Source: netcdf
Version: 1:4.4.1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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):
> cd /<>/obj-x86_64-linux-gnu/libsrc4 && /usr/bin/cc  
> -DCURL_STATICLIB=1 -DH5_BUILT_AS_DYNAMIC_LIB -DHAVE_CONFIG_H 
> -I/<>/include -I/<>/oc2 -I/<>/libsrc 
> -I/<>/obj-x86_64-linux-gnu  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -fPIC   -o 
> CMakeFiles/netcdf4.dir/nc4attr.c.o   -c /<>/libsrc4/nc4attr.c
> In file included from /<>/libsrc4/nc4attr.c:15:0:
> /<>/include/nc4internal.h:18:18: fatal error: hdf5.h: No such 
> file or directory
>  #include 
>   ^
> compilation terminated.
> libsrc4/CMakeFiles/netcdf4.dir/build.make:89: recipe for target 
> 'libsrc4/CMakeFiles/netcdf4.dir/nc4attr.c.o' failed
> make[3]: *** [libsrc4/CMakeFiles/netcdf4.dir/nc4attr.c.o] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/08/28/netcdf_4.4.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#835709: llvm-toolchain-3.7: FTBFS: make[1]: gcc-6.1: Command not found

2016-08-28 Thread Lucas Nussbaum
Source: llvm-toolchain-3.7
Version: 1:3.7.1-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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 '/<>'
> Can't exec "gcc-6.1": No such file or directory at 
> /usr/share/perl5/Dpkg/Arch.pm line 128.
> dpkg-architecture: warning: cannot determine CC system type, falling back to 
> default (native compilation)
> dpkg-query: no packages found matching g++-6.1
> dpkg: error: --compare-versions takes three arguments:   
> 
> 
> Type dpkg --help for help about installing and deinstalling packages [*];
> Use 'apt' or 'aptitude' for user-friendly package management;
> Type dpkg -Dhelp for a list of dpkg debug flag values;
> Type dpkg --force-help for a list of forcing options;
> Type dpkg-deb --help for help about manipulating *.deb files;
> 
> Options marked [*] produce a lot of output - pipe it through 'less' or 'more' 
> !
> Can't exec "gcc-6.1": No such file or directory at 
> /usr/share/perl5/Dpkg/Arch.pm line 128.
> dpkg-architecture: warning: cannot determine CC system type, falling back to 
> default (native compilation)
> Can't exec "gcc-6.1": No such file or directory at 
> /usr/share/perl5/Dpkg/Arch.pm line 128.
> dpkg-architecture: warning: cannot determine CC system type, falling back to 
> default (native compilation)
> Can't exec "gcc-6.1": No such file or directory at 
> /usr/share/perl5/Dpkg/Arch.pm line 128.
> dpkg-architecture: warning: cannot determine CC system type, falling back to 
> default (native compilation)
> dpkg-query: no packages found matching g++-6.1
> dpkg: error: --compare-versions takes three arguments:   
> 
> 
> Type dpkg --help for help about installing and deinstalling packages [*];
> Use 'apt' or 'aptitude' for user-friendly package management;
> Type dpkg -Dhelp for a list of dpkg debug flag values;
> Type dpkg --force-help for a list of forcing options;
> Type dpkg-deb --help for help about manipulating *.deb files;
> 
> Options marked [*] produce a lot of output - pipe it through 'less' or 'more' 
> !
> dpkg-query: no packages found matching g++-6.1
> dpkg: error: --compare-versions takes three arguments:   
> 
> 
> Type dpkg --help for help about installing and deinstalling packages [*];
> Use 'apt' or 'aptitude' for user-friendly package management;
> Type dpkg -Dhelp for a list of dpkg debug flag values;
> Type dpkg --force-help for a list of forcing options;
> Type dpkg-deb --help for help about manipulating *.deb files;
> 
> Options marked [*] produce a lot of output - pipe it through 'less' or 'more' 
> !
> Can't exec "gcc-6.1": No such file or directory at 
> /usr/share/perl5/Dpkg/Arch.pm line 128.
> dpkg-architecture: warning: cannot determine CC system type, falling back to 
> default (native compilation)
> Can't exec "gcc-6.1": No such file or directory at 
> /usr/share/perl5/Dpkg/Arch.pm line 128.
> dpkg-architecture: warning: cannot determine CC system type, falling back to 
> default (native compilation)
> Can't exec "gcc-6.1": No such file or directory at 
> /usr/share/perl5/Dpkg/Arch.pm line 128.
> dpkg-architecture: warning: cannot determine CC system type, falling back to 
> default (native compilation)
> Can't exec "gcc-6.1": No such file or directory at 
> /usr/share/perl5/Dpkg/Arch.pm line 128.
> dpkg-architecture: warning: cannot determine CC system type, falling back to 
> default (native compilation)
> Can't exec "gcc-6.1": No such file or directory at 
> /usr/share/perl5/Dpkg/Arch.pm line 128.
> dpkg-architecture: warning: cannot determine CC system type, falling back to 
> default (native compilation)
> Can't exec "gcc-6.1": No such file or directory at 
> /usr/share/perl5/Dpkg/Arch.pm line 128.
> dpkg-architecture: warning: cannot determine CC system type, falling back to 
> default (native compilation)
> for f in debian/*.in; do \
>   f2=$(echo $f | sed 's/\.in$//;s/X\.Y/3.7/'); \
>   echo "$f => $f2"; \
>   sed -e 's|@DEB_HOST_MULTIARCH@|x86_64-linux-gnu|g' \
>   -e "s|@OCAML_STDLIB_DIR@|/usr/lib/ocaml|g" \
>   -e "s|@LLVM_VERSION_FULL@|3.7.1|g" \
>   -e "s|@LLVM_VERSION@|3.7|g" $f > $f2; \
> done
> Can't exec "gcc-6.1": No such file or directory at 
&g

Bug#835707: fail2ban: FTBFS: Tests failures

2016-08-28 Thread Lucas Nussbaum
Source: fail2ban
Version: 0.9.5-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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):
> ss.F.s..
> ==
> FAIL: testVerbose (fail2ban.tests.fail2banregextestcase.Fail2banRegexTest)
> --
> Traceback (most recent call last):
>   File 
> "/<>/.pybuild/pythonX.Y_3.5/build/fail2ban/tests/fail2banregextestcase.py",
>  line 162, in testVerbose
> self.assertLogged('141.3.81.106  Fri Aug 14 11:53:59 2015')
>   File 
> "/<>/.pybuild/pythonX.Y_3.5/build/fail2ban/tests/utils.py", line 
> 266, in assertLogged
> raise AssertionError("None among %r was found in the log: %r" % (s, 
> logged))
> AssertionError: None among ('141.3.81.106  Fri Aug 14 11:53:59 2015',) was 
> found in the log: 'Setting usedns = warn for Filter(None)\nCreated 
> Filter(None)\nUse   failregex line : (?:(?:Authentication failure|Failed 
> [-/\\w+]+) for(...\nUse log file : 
> /<>/.pybuild/pythonX.Y_3.5/build/fail2ban/tests/files/testcase02.log\nUse
>  encoding : UTF-8\n\nMatched time template (?:DAY )?MON Day 
> 24hour:Minute:Second(?:\\.Microseconds)?(?: Year)?\nGot time 
> 1471175460.00 for "\'Aug 14 11:51:00\'" using template (?:DAY )?MON Day 
> 24hour:Minute:Second(?:\\.Microseconds)?(?: Year)?\nSorting the template 
> list\nWinning template: (?:DAY )?MON Day 
> 24hour:Minute:Second(?:\\.Microseconds)?(?: Year)? with 1 hits\nMatched time 
> template (?:DAY )?MON Day 24hour:Minute:Second(?:\\.Microseconds)?(?: 
> Year)?\nGot time 1471175520.00 for "\'Aug 14 11:52:00\'" using template 
> (?:DAY )?MON Day 24hour:Minute:Second(?:\\.Microseconds)?(?: Year)?\nMatched 
> time template (?:DAY )?MON Day 24hour:Minute:Second(?:\\.Microseconds)?(?: 
> Year)?\nGot time 1471175580.00 for "\'Aug 14 11:53:00\'" using template 
> (?:DAY )?MON Day 24hour:Minute:Second(?:\\.Microseconds)?(?: Year)?\nMatched 
> time template (?:DAY )?MON Day 24hour:Minute:Second(?:\\.Microseconds)?(?: 
> Year)?\nGot time 1471175639.00 for "\'Aug 14 11:53:59\'" using template 
> (?:DAY )?MON Day 24hour:Minute:Second(?:\\.Microseconds)?(?: Year)?\nMatched 
> time template (?:DAY )?MON Day 24hour:Minute:Second(?:\\.Microseconds)?(?: 
> Year)?\nGot time 1471175699.00 for "\'Aug 14 11:54:59\'" using template 
> (?:DAY )?MON Day 24hour:Minute:Second(?:\\.Microseconds)?(?: Year)?\nMatched 
> time template (?:DAY )?MON Day 24hour:Minute:Second(?:\\.Microseconds)?(?: 
> Year)?\nGot time 1471175759.00 for "\'Aug 14 11:55:59\'" using template 
> (?:DAY )?MON Day 24hour:Minute:Second(?:\\.Microseconds)?(?: Year)?\nMatched 
> time template (?:DAY )?MON Day 24hour:Minute:Second(?:\\.Microseconds)?(?: 
> Year)?\nGot time 1471175761.00 for "\'Aug 14 11:56:01\'" using template 
> (?:DAY )?MON Day 24hour:Minute:Second(?:\\.Microseconds)?(?: Year)?\nMatched 
> time template (?:DAY )?MON Day 24hour:Minute:Second(?:\\.Microseconds)?(?: 
> Year)?\nGot time 1471175821.00 for "\'Aug 14 11:57:01\'" using template 
> (?:DAY )?MON Day 24hour:Minute:Second(?:\\.Microseconds)?(?: Year)?\nMatched 
> time template (?:DAY )?MON Day 24hour:Minute:Second(?:\\.Microseconds)?(?: 
> Year)?\nGot time 1471175879.00 for "\'Aug 14 11:57:59\'" using template 
> (?:DAY )?MON Day 24hour:Minute:Second(?:\\.Microseconds)?(?: Year)?\nMatched 
> time template (?:DAY )?MON Day 24hour:Minute:Second(?:\\.Microseconds)?(?: 
> Year)?\nGot time 1471175939.00 for "\'Aug 14 11:58:59\'" using template 
> (?:DAY )?MON Day 24hour:Minute:Second(?:\\.Microseconds)?(?: Year)?\nMatched 
> time template (?:DAY )?MON Day 24hour:Minute:Second(?:\\.Microseconds)?(?: 
> Year)?\nGot time 1471175941.00 for "\'Aug 14 11:59:01\'" using template 
> (?:DAY )?MON Day 24hour:Minute:Second(?:\\.Microseconds)?(?: Year)?\nSorting 
> the template list\nWinning template: (?:DAY )?MON Day 
> 24hour:Minute:Second(?:\\.Microseconds)?(?: Year)? with 11 hits\nMatched time 
> template (?:DAY )?MON Day 24hour:Minute:Second(?:\\.Microseconds)?(?: 
> Year)?\nGot

Bug#835712: torus-trooper: FTBFS: src/abagames/tt/shape.d:442:48: error: std.math.fabs called with argument types (int) matches both:

2016-08-28 Thread Lucas Nussbaum
Source: torus-trooper
Version: 0.22.dfsg1-10
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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[2]: Entering directory '/<>'
> gdc -o torus-trooper import/SDL.d import/SDL_active.d import/SDL_audio.d 
> import/SDL_byteorder.d import/SDL_cdrom.d import/SDL_copying.d 
> import/SDL_endian.d import/SDL_error.d import/SDL_events.d 
> import/SDL_getenv.d import/SDL_joystick.d import/SDL_keyboard.d 
> import/SDL_keysym_.d import/SDL_mixer.d import/SDL_mouse.d import/SDL_mutex.d 
> import/SDL_quit.d import/SDL_rwops.d import/SDL_syswm.d import/SDL_thread.d 
> import/SDL_timer.d import/SDL_types.d import/SDL_version_.d 
> import/SDL_video.d import/bulletml.d import/opengl.d import/openglu.d 
> src/abagames/tt/barrage.d src/abagames/tt/boot.d 
> src/abagames/tt/bulletactor.d src/abagames/tt/bulletactorpool.d 
> src/abagames/tt/bulletimpl.d src/abagames/tt/bullettarget.d 
> src/abagames/tt/camera.d src/abagames/tt/enemy.d 
> src/abagames/tt/floatletter.d src/abagames/tt/gamemanager.d 
> src/abagames/tt/letter.d src/abagames/tt/particle.d 
> src/abagames/tt/prefmanager.d src/abagames/tt/replay.d 
> src/abagames/tt/screen.d src/abagames/tt/shape.d src/abagames/tt/ship.d 
> src/abagames/tt/shot.d src/abagames/tt/soundmanager.d 
> src/abagames/tt/stagemanager.d src/abagames/tt/title.d 
> src/abagames/tt/tunnel.d src/abagames/util/actor.d 
> src/abagames/util/bulletml/bullet.d 
> src/abagames/util/bulletml/bulletsmanager.d src/abagames/util/iterator.d 
> src/abagames/util/logger.d src/abagames/util/prefmanager.d 
> src/abagames/util/rand.d src/abagames/util/sdl/displaylist.d 
> src/abagames/util/sdl/gamemanager.d src/abagames/util/sdl/input.d 
> src/abagames/util/sdl/luminous.d src/abagames/util/sdl/mainloop.d 
> src/abagames/util/sdl/pad.d src/abagames/util/sdl/recordablepad.d 
> src/abagames/util/sdl/screen.d src/abagames/util/sdl/screen3d.d 
> src/abagames/util/sdl/sdlexception.d src/abagames/util/sdl/sound.d 
> src/abagames/util/sdl/texture.d src/abagames/util/tokenizer.d 
> src/abagames/util/vector.d -Iimport -Isrc -Wno-deprecated -frelease -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -lSDL 
> -lGL -lGLU -lSDL_mixer -lbulletml
> cc1d: warning: command line option '-Wformat=1' is valid for 
> C/C++/ObjC/ObjC++ but not for D
> cc1d: warning: command line option '-Wdate-time' is valid for 
> C/C++/Fortran/ObjC/ObjC++ but not for D
> src/abagames/tt/shape.d:442:48: error: std.math.fabs called with argument 
> types (int) matches both:
> /usr/lib/gcc/x86_64-linux-gnu/6/include/d/std/math.d:3419:6: 
> std.math.fabs(real x)
> and:
> /usr/lib/gcc/x86_64-linux-gnu/6/include/d/std/math.d:3425:7: 
> std.math.fabs(float x)
>  float y1 = -0.5 + (1.0 / divNum) * fabs(i - divNum / 2) * 2;
> ^
> Makefile:8: recipe for target 'torus-trooper' failed
> make[2]: *** [torus-trooper] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/08/28/torus-trooper_0.22.dfsg1-10_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#835706: evolution-data-server: FTBFS: conftest.c:17:28: fatal error: ac_nonexistent.h: No such file or directory

2016-08-28 Thread Lucas Nussbaum
Source: evolution-data-server
Version: 3.20.5-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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 version 6.2.0 20160822 (Debian 6.2.0-1) 
> configure:4710: $? = 0
> configure:4699: gcc -V >&5
> gcc: error: unrecognized command line option '-V'
> gcc: fatal error: no input files
> compilation terminated.
> configure:4710: $? = 1
> configure:4699: gcc -qversion >&5
> gcc: error: unrecognized command line option '-qversion'; did you mean 
> '--version'?
> gcc: fatal error: no input files
> compilation terminated.
> configure:4710: $? = 1
> configure:4730: checking whether the C compiler works
> configure:4752: gcc -g -O2 -fdebug-prefix-map=/<>=. -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fPIE -pie -Wl,-z,relro -Wl,-z,now -Wl,-z,defs 
> -Wl,--as-needed -Wl,-O1 conftest.c  >&5
> configure:4756: $? = 0
> configure:4804: result: yes
> configure:4807: checking for C compiler default output file name
> configure:4809: result: a.out
> configure:4815: checking for suffix of executables
> configure:4822: gcc -o conftest -g -O2 -fdebug-prefix-map=/<>=. 
> -fPIE -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fPIE -pie -Wl,-z,relro -Wl,-z,now -Wl,-z,defs 
> -Wl,--as-needed -Wl,-O1 conftest.c  >&5
> configure:4826: $? = 0
> configure:4848: result: 
> configure:4870: checking whether we are cross compiling
> configure:4878: gcc -o conftest -g -O2 -fdebug-prefix-map=/<>=. 
> -fPIE -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fPIE -pie -Wl,-z,relro -Wl,-z,now -Wl,-z,defs 
> -Wl,--as-needed -Wl,-O1 conftest.c  >&5
> configure:4882: $? = 0
> configure:4889: ./conftest
> configure:4893: $? = 0
> configure:4908: result: no
> configure:4913: checking for suffix of object files
> configure:4935: gcc -c -g -O2 -fdebug-prefix-map=/<>=. -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:4939: $? = 0
> configure:4960: result: o
> configure:4964: checking whether we are using the GNU C compiler
> configure:4983: gcc -c -g -O2 -fdebug-prefix-map=/<>=. -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:4983: $? = 0
> configure:4992: result: yes
> configure:5001: checking whether gcc accepts -g
> configure:5021: gcc -c -g -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:5021: $? = 0
> configure:5062: result: yes
> configure:5079: checking for gcc option to accept ISO C89
> configure:5142: gcc  -c -g -O2 -fdebug-prefix-map=/<>=. -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:5142: $? = 0
> configure:5155: result: none needed
> configure:5180: checking whether gcc understands -c and -o together
> configure:5202: gcc -c conftest.c -o conftest2.o
> configure:5205: $? = 0
> configure:5202: gcc -c conftest.c -o conftest2.o
> configure:5205: $? = 0
> configure:5217: result: yes
> configure:5236: checking dependency style of gcc
> configure:5347: result: none
> configure:5367: checking for supported compiler flags
> configure:5384: gcc -c -g -O2 -fdebug-prefix-map=/<>=. -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security 
> -Wno-deprecated-declarations -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:5384: $? = 0
> configure:5384: gcc -c -g -O2 -fdebug-prefix-map=/<>=. -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security 
> -Werror-implicit-function-declaration -Wdate-time -D_FORTIFY_SOURCE=2 
> conftest.c >&5
> configure:5384: $? = 0
> configure:5384: gcc -c -g -O2 -fdebug-prefix-map=/<>=. -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security -Wformat 
> -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:5384: $? = 0
> configure:5384: gcc -c -g -O2 -fdebug-prefix-map=/<>=. -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security -Wformat-security 
> -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:5384: $? = 0
> configure:5384: gcc -c -g -O2 -fdebug-prefix-map=/<>=. -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security -Winit-self 
> -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c >&5
> configure:5384

Bug#835717: sosi2osm: FTBFS: node.cpp:54:31: error: 'max' was not declared in this scope

2016-08-28 Thread Lucas Nussbaum
Source: sosi2osm
Version: 1.0.0-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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++ -g -O2 -fdebug-prefix-map=/<>=. -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 `pkg-config --cflags lua5.1-c++ fyba` -DLINUX -DUNIX -g  
> -c -o node.o node.cpp
> node.cpp: In function 'long int createNode(double, double, short int)':
> node.cpp:54:31: error: 'max' was not declared in this scope
>   sizeM = max(1024, sizeM*2);
>^
> : recipe for target 'node.o' failed
> make[1]: *** [node.o] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/08/28/sosi2osm_1.0.0-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#835716: inkscape: FTBFS: ui/dialog/layer-properties.cpp:149:56: error: call of overloaded 'ptr_fun()' is ambiguous

2016-08-28 Thread Lucas Nussbaum
Source: inkscape
Version: 0.91-9
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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++ -DHAVE_CONFIG_H -I. -I..  -I../cxxtest -I./extension/dbus 
> -I/usr/include/libexif -I/usr/include/freetype2   -fopenmp 
> -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp 
> -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp 
> -DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 
> -I/usr/include/x86_64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 
> -I/usr/include/x86_64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 
> -I/usr/include/x86_64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 
> -I/usr/include/libwpg-0.3 -I/usr/include/libwpd-0.10 
> -I/usr/include/librevenge-0.0 -I/usr/include/libxml2 
> -I/usr/include/libvisio-0.1 -I/usr/include/librevenge-0.0 
> -I/usr/include/libcdr-0.1 -I/usr/include/librevenge-0.0 
> -I/usr/include/poppler -pthread -I/usr/include/poppler/glib 
> -I/usr/include/poppler -I/usr/include/cairo -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -DPOTRACE=\"potrace\" 
> -pthread -I/usr/include/gtkmm-2.4 
> -I/usr/lib/x86_64-linux-gnu/gtkmm-2.4/include -I/usr/include/atkmm-1.6 
> -I/usr/include/gtk-unix-print-2.0 -I/usr/include/gtk-2.0 
> -I/usr/include/gdkmm-2.4 -I/usr/lib/x86_64-linux-gnu/gdkmm-2.4/include 
> -I/usr/include/giomm-2.4 -I/usr/lib/x86_64-linux-gnu/giomm-2.4/include 
> -I/usr/include/pangomm-1.4 -I/usr/lib/x86_64-linux-gnu/pangomm-1.4/include 
> -I/usr/include/glibmm-2.4 -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include 
> -I/usr/include/cairomm-1.0 -I/usr/lib/x86_64-linux-gnu/cairomm-1.0/include 
> -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-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/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/freetype2 -I/usr/include/gtkspell-2.0 -pthread 
> -I/usr/include/cairomm-1.0 -I/usr/lib/x86_64-linux-gnu/cairomm-1.0/include 
> -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/giomm-2.4 
> -I/usr/lib/x86_64-linux-gnu/giomm-2.4/include -I/usr/include/glibmm-2.4 
> -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/libpng16 
> -I/usr/include/libxml2 -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 
> -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include   
> -DG_DISABLE_DEPRECATED -DGLIBMM_DISABLE_DEPRECATED -DGDKMM_DISABLE_DEPRECATED 
> -DGTK_DISABLE_SINGLE_INCLUDES -DGTK_DISABLE_DEPRECATED 
> -DGTKMM_DISABLE_DEPRECATED -Werror=format-security -Wswitch 
> -Werror=return-type -DGSEAL_ENABLE -DG_DISABLE_SINGLE_INCLUDES -Wall -Wformat 
> -Wformat-security -W -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2  
> -Wpointer-arith -Wcast-align -Wsign-compare -Woverloaded-virtual -Wswitch 
> -Wno-unused-parameter -g -O2 -fdebug-prefix-map=/<>=. -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security -fopenmp -c -o 
> ui/dialog/layer-properties.o ui/dialog/layer-properties.cpp
> ui/dialog/layer-properties.cpp: In member function 'void 
> Inkscape::UI::Dialogs::LayerPropertiesDialog::_close()':
> ui/dialog/layer-properties.cpp:149:56: error: call of overloaded 
> 'ptr_fun()' is ambiguous
>  sigc::bind(sigc::ptr_fun(&::operator delete), this),
> ^
> In file included from 
> /usr/include/sigc++-2.0/sigc++/adaptors/adaptor_trait.h:8:0,
>  from /usr/include/sigc++-2.0/sigc++/functors/slot.h:7,
>  from /usr/include/sigc++-2.0/sigc++/signal_base.h:27,
>  from /usr/include/sigc++-2.0/sigc++/signal.h:8,
>  from /usr/include/sigc++-2.0/sigc++/sigc++.h:104,
>  from /usr/include/glibmm-2.4/glibmm/signalproxy.h:28,
>  from /usr/include/glibmm-2.4/glibmm/objectbase.h:23,
>  from /usr/include/glibmm-2.4/glibmm/wrap.h:23,
>  from 
> /usr/include/glibmm-2.4/glibmm/containerhandle_shared.h:25,
>

Bug#835714: gcc-6-cross-ports: FTBFS: patch fails to apply

2016-08-28 Thread Lucas Nussbaum
Source: gcc-6-cross-ports
Version: 9
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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 '/<>/gcc'
> : # unpack gcc tarball
> mkdir -p stamps
> if [ -d /<>/gcc/src ]; then \
>   echo >&2 "Source directory /<>/gcc/src exists. Delete by 
> hand"; \
>   false; \
> fi
> rm -rf gcc-6.2.0
> tar -x -f /usr/src/gcc-6/gcc-6.2.0-dfsg.tar.xz
> mv gcc-6.2.0 /<>/gcc/src
> ln -sf libsanitizer /<>/gcc/src/libasan
> rm -f /<>/gcc/src/gcc/doc/*.1
> rm -f /<>/gcc/src/gcc/doc/fsf-funding.7
> rm -f /<>/gcc/src/gcc/doc/*.info
> rm -f /<>/gcc/src/gcc/fortran/*.info
> rm -f /<>/gcc/src/libgomp/*.info
> rm -f /<>/gcc/src/gcc/java/*.1
> rm -f /<>/gcc/src/gcc/java/*.info
> for i in gcc/doc/avr-mmcu.texi gcc/doc/bugreport.texi gcc/doc/cfg.texi 
> gcc/doc/collect2.texi gcc/doc/compat.texi gcc/doc/configfiles.texi 
> gcc/doc/configterms.texi gcc/doc/contrib.texi gcc/doc/contribute.texi 
> gcc/doc/cpp.texi gcc/doc/cppenv.texi gcc/doc/cppinternals.texi 
> gcc/doc/cppopts.texi gcc/doc/extend.texi gcc/doc/fragments.texi 
> gcc/doc/frontends.texi gcc/doc/gccint.texi gcc/doc/gcov.texi 
> gcc/doc/generic.texi gcc/doc/gimple.texi gcc/doc/gnu.texi gcc/doc/gty.texi 
> gcc/doc/headerdirs.texi gcc/doc/hostconfig.texi gcc/doc/implement-c.texi 
> gcc/doc/implement-cxx.texi gcc/doc/install-old.texi gcc/doc/install.texi 
> gcc/doc/interface.texi gcc/doc/invoke.texi gcc/doc/languages.texi 
> gcc/doc/libgcc.texi gcc/doc/loop.texi gcc/doc/lto.texi gcc/doc/makefile.texi 
> gcc/doc/match-and-simplify.texi gcc/doc/md.texi gcc/doc/objc.texi 
> gcc/doc/optinfo.texi gcc/doc/options.texi gcc/doc/passes.texi 
> gcc/doc/plugins.texi gcc/doc/portability.texi gcc/doc/rtl.texi 
> gcc/doc/service.texi gcc/doc/sourcebuild.texi gcc/doc/standards.texi 
> gcc/doc/tm.texi.in gcc/doc/tm.texi gcc/doc/tree-ssa.texi gcc/doc/trouble.texi 
> gcc/doc/include/gcc-common.texi gcc/doc/include/funding.texi 
> gcc/fortran/gfc-internals.texi gcc/fortran/invoke.texi 
> gcc/fortran/intrinsic.texi ; do \
>   if [ -f /<>/gcc/src/$i ]; then \
> cp debian/dummy.texi /<>/gcc/src/$i; \
>   else \
> cp debian/dummy.texi /<>/gcc/src/$i; \
> echo >&2 "$i does not exist, fix debian/rules.unpack"; \
>   fi; \
> done
> for i in gcc/doc/gcc.texi gcc/java/gcj.texi gcc/ada/gnat-style.texi 
> gcc/ada/gnat_rm.texi gcc/ada/gnat_ugn.texi gcc/fortran/gfortran.texi 
> gcc/go/gccgo.texi libgomp/libgomp.texi libquadmath/libquadmath.texi ; do \
>   n=$(basename $i .texi); \
>   if [ -f /<>/gcc/src/$i ]; then \
> sed "s/@name@/$n/g" debian/gcc-dummy.texi \
>   > /<>/gcc/src/$i; \
>   else \
> sed "s/@name@/$n/g" debian/gcc-dummy.texi \
>   > /<>/gcc/src/$i; \
> echo >&2 "$i does not exist, fix debian/rules.unpack"; \
>   fi; \
> done
> for i in gcc/doc/cpp.1 gcc/doc/g++.1 gcc/doc/gc-analyze.1 gcc/doc/gcc.1 
> gcc/doc/gccgo.1 gcc/doc/gcj.1 gcc/doc/gcj-dbtool.1 gcc/doc/gcjh.1 
> gcc/doc/gcov.1 gcc/doc/gfortran.1 gcc/doc/gij.1 gcc/doc/grmic.1 
> gcc/doc/grmiregistry.1 gcc/doc/jcf-dump.1 gcc/doc/jv-convert.1 
> gcc/doc/fsf-funding.7 ; do \
>   touch /<>/gcc/src/$i; \
> done
> rm -f /<>/gcc/src/INSTALL/*.html
> echo "gcc-6.2.0-dfsg.tar.xz unpacked." > 
> stamps/01-unpack-stamp-gcc-6.2.0-dfsg.tar.xz
> : # unpack gdc tarball
> mkdir -p stamps
> if [ -d /<>/gcc/src/gcc/d ]; then \
>   echo >&2 "Source directory /<>/gcc/src/gcc/d exists. Delete by 
> hand";\
>   false; \
> fi
> #rm -rf gdc-20160822
> rm -rf /<>/gcc/src/gcc/d
> rm -rf /<>/gcc/src/gcc/testsuite/gdc.test
> rm -f /<>/gcc/src/gcc/testsuite/lib/gdc*.exp
> rm -rf /<>/gcc/src/libphobos
> tar -x -C /<>/gcc/src --strip-components=1 -f 
> /usr/src/gcc-6/gdc-20160822.tar.xz
> echo "gdc-20160822.tar.xz unpacked." > 
> stamps/01-unpack-stamp-gdc-20160822.tar.xz
> echo -e "\nBuilt from Debian source package gcc-6-6.2.0-1" \
>   > pxxx
> echo -e "Integrated upstream packages in this version:\n" >> pxxx
> for i in gcc-6.2.0-dfsg.tar.xz  gdc-20160822.tar.xz; do echo "  $i" >> pxxx; 
> done
> mv -f pxxx stamps/01-unpack-stamp
> echo gcc-gfdl-build.diff gcc-textdomain.diff gcc-driver-extra-langs.diff 
> gcc-hash-style-gnu.diff libstdc++-pic.diff libstdc++-doclink.diff 
> libstdc++-man-3cxx.diff libs

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

2016-08-28 Thread Lucas Nussbaum
Source: salmon
Version: 0.4.2+ds1-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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):
> cd /<>/salmon-0.4.2+ds1/obj-x86_64-linux-gnu/src && /usr/bin/c++
> -I/<>/salmon-0.4.2+ds1/include -I/usr/include/eigen3 
> -I/usr/include/bwa  -pthread -funroll-loops -fPIC -fomit-frame-pointer -Ofast 
> -DHAVE_ANSI_TERM -DHAVE_SSTREAM -Wall -std=c++11 -Wreturn-type 
> -Werror=return-type -static-libstdc++ -Wno-deprecated-register 
> -Wno-unused-local-typedefs   -o CMakeFiles/salmon.dir/SalmonUtils.cpp.o -c 
> /<>/salmon-0.4.2+ds1/src/SalmonUtils.cpp
> In file included from 
> /<>/salmon-0.4.2+ds1/include/SalmonUtils.hpp:27:0,
>  from /<>/salmon-0.4.2+ds1/src/SalmonUtils.cpp:12:
> /<>/salmon-0.4.2+ds1/include/ReadLibrary.hpp: In copy constructor 
> 'ReadLibrary::ReadLibrary(const ReadLibrary&)':
> /<>/salmon-0.4.2+ds1/include/ReadLibrary.hpp:35:34: warning: 
> comparison between signed and unsigned integer expressions [-Wsign-compare]
>  for (size_t i = 0; i < mc; ++i) { 
> libTypeCounts_[i].store(rl.libTypeCounts_[i].load()); }
> ~~^~~~
> /<>/salmon-0.4.2+ds1/include/ReadLibrary.hpp: In constructor 
> 'ReadLibrary::ReadLibrary(ReadLibrary&&)':
> /<>/salmon-0.4.2+ds1/include/ReadLibrary.hpp:48:34: warning: 
> comparison between signed and unsigned integer expressions [-Wsign-compare]
>  for (size_t i = 0; i < mc; ++i) { 
> libTypeCounts_[i].store(rl.libTypeCounts_[i].load()); }
> ~~^~~~
> In file included from 
> /<>/salmon-0.4.2+ds1/include/ClusterForest.hpp:7:0,
>  from 
> /<>/salmon-0.4.2+ds1/include/AlignmentLibrary.hpp:12,
>  from /<>/salmon-0.4.2+ds1/src/SalmonUtils.cpp:13:
> /<>/salmon-0.4.2+ds1/include/Transcript.hpp: In constructor 
> 'Transcript::Transcript(size_t, const char*, uint32_t, double)':
> /<>/salmon-0.4.2+ds1/include/Transcript.hpp:232:12: warning: 
> 'Transcript::logPerBasePrior_' will be initialized after [-Wreorder]
>  double logPerBasePrior_;
> ^~~~
> /<>/salmon-0.4.2+ds1/include/Transcript.hpp:225:12: warning:   
> 'double Transcript::priorMass_' [-Wreorder]
>  double priorMass_;
> ^~
> /<>/salmon-0.4.2+ds1/include/Transcript.hpp:16:5: warning:   when 
> initialized here [-Wreorder]
>  Transcript(size_t idIn, const char* name, uint32_t len, double alpha = 
> 0.05) :
>  ^~
> In file included from 
> /<>/salmon-0.4.2+ds1/include/BAMQueue.hpp:146:0,
>  from 
> /<>/salmon-0.4.2+ds1/include/AlignmentLibrary.hpp:14,
>  from /<>/salmon-0.4.2+ds1/src/SalmonUtils.cpp:13:
> /<>/salmon-0.4.2+ds1/include/BAMQueue.tpp: In member function 'void 
> BAMQueue::reset()':
> /<>/salmon-0.4.2+ds1/include/BAMQueue.tpp:88:29: error: no matching 
> function for call to 'spdlog::logger::warn()'
>logger_->warn() << errstr.str();
>  ^
> In file included from /usr/include/spdlog/spdlog.h:13:0,
>  from /<>/salmon-0.4.2+ds1/include/SalmonOpts.hpp:7,
>  from 
> /<>/salmon-0.4.2+ds1/include/SalmonUtils.hpp:23,
>  from /<>/salmon-0.4.2+ds1/src/SalmonUtils.cpp:12:
> /usr/include/spdlog/logger.h:43:38: note: candidate: template 
> void spdlog::logger::warn(const char*, const Args& ...)
>  template  void warn(const char* fmt, const Args&... 
> args);
>   ^~~~
> /usr/include/spdlog/logger.h:43:38: note:   template argument 
> deduction/substitution failed:
> In file included from 
> /<>/salmon-0.4.2+ds1/include/BAMQueue.hpp:146:0,
>  from 
> /<>/salmon-0.4.2+ds1/include/AlignmentLibrary.hpp:14,
>  from /<>/salmon-0.4.2+ds1/src/SalmonUtils.cpp:13:
> /<>/salmon-0.4.2+ds1/include/BAMQueue.tpp:88:29: note:   candidate 
> expects at least 1 argument, 0 provided
>logger_->warn() << errstr.str();
>  ^
> In file included from /usr/include/spdlog/spdlog.h:13:0,
>  from /<>/salmon-0.4.2+ds1/include/SalmonOpts.hpp:7,
>  from 
> /<>/salmon-0.4.2+ds1/include/SalmonUtils.hpp:23,
>  from /<>/salmon-0.4.2+ds1/src/Sal

Bug#835723: pdal: FTBFS: Hdf5Handler.hpp:37:19: fatal error: H5Cpp.h: No such file or directory

2016-08-28 Thread Lucas Nussbaum
Source: pdal
Version: 1.2.0-4
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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):
> cd /<>/obj-x86_64-linux-gnu/plugins/icebridge && /usr/bin/c++   
> -DHAVE_HDF5=1 -Dpdal_plugin_reader_icebridge_EXPORTS 
> -I/<>/include -I/<>/src/util -I/<>/src 
> -I/<>/io -I/<>/kernels -I/<>/filters 
> -I/<>/vendor/gtest-1.7.0/include 
> -I/<>/vendor/gtest-1.7.0 
> -I/<>/obj-x86_64-linux-gnu/include 
> -I/<>/vendor/eigen-3.1.91 
> -I/<>/vendor/jsoncpp-1.6.2/dist 
> -I/<>/vendor/nanoflann-1.1.8 
> -I/<>/vendor/rply-1.1.4 -I/<>/vendor/pdalboost 
> -I/<>/test/unit 
> -I/<>/obj-x86_64-linux-gnu/test/unit -I/usr/include/libxml2 
> -I/usr/include/gdal -I/usr/include/geotiff  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time 
> -D_FORTIFY_SOURCE=2  -Wextra -Wall -Wno-unused-parameter -Wno-unused-variable 
> -Wpointer-arith -Wcast-align -Wcast-qual -Wredundant-decls -Wno-long-long 
> -Wno-unknown-pragmas -Wno-deprecated-declarations -isystem /usr/local/include 
> -std=c++11 -O2 -g -DNDEBUG -fPIC   -o 
> CMakeFiles/pdal_plugin_reader_icebridge.dir/io/IcebridgeReader.cpp.o -c 
> /<>/plugins/icebridge/io/IcebridgeReader.cpp
> In file included from 
> /<>/plugins/icebridge/io/IcebridgeReader.hpp:55:0,
>  from 
> /<>/plugins/icebridge/io/IcebridgeReader.cpp:35:
> /<>/plugins/icebridge/io/Hdf5Handler.hpp:37:19: fatal error: 
> H5Cpp.h: No such file or directory
>  #include "H5Cpp.h"
>^
> compilation terminated.
> plugins/icebridge/CMakeFiles/pdal_plugin_reader_icebridge.dir/build.make:65: 
> recipe for target 
> 'plugins/icebridge/CMakeFiles/pdal_plugin_reader_icebridge.dir/io/IcebridgeReader.cpp.o'
>  failed
> make[4]: *** 
> [plugins/icebridge/CMakeFiles/pdal_plugin_reader_icebridge.dir/io/IcebridgeReader.cpp.o]
>  Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/08/28/pdal_1.2.0-4_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#835718: mapnik-vector-tile: FTBFS: ld: /usr/lib/libmapnik.so: undefined reference to symbol '_ZN6icu_5513UnicodeStringC1ERKS0_'

2016-08-28 Thread Lucas Nussbaum
Source: mapnik-vector-tile
Version: 1.1.2+dfsg-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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):
> /usr/bin/ld: warning: libicuuc.so.55, needed by /usr/lib/libmapnik.so, may 
> conflict with libicuuc.so.57
> /usr/bin/ld: /usr/lib/libmapnik.so: undefined reference to symbol 
> '_ZN6icu_5513UnicodeStringC1ERKS0_'
> //usr/lib/x86_64-linux-gnu/libicuuc.so.55: 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/08/28/mapnik-vector-tile_1.1.2+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#835721: golang-github-spf13-pflag: FTBFS: dh_auto_test: go test -v -p 1 github.com/spf13/pflag returned exit code 1

2016-08-28 Thread Lucas Nussbaum
Source: golang-github-spf13-pflag
Version: 0.0~git20160427.0.cb88ea7-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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 --buildsystem=golang --with=golang
>dh_testdir -O--buildsystem=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   go install -v -p 1 github.com/spf13/pflag
> github.com/spf13/pflag
>dh_auto_test -O--buildsystem=golang
>   go test -v -p 1 github.com/spf13/pflag
> === RUN   TestExplicitTrue
> --- PASS: TestExplicitTrue (0.00s)
> === RUN   TestImplicitTrue
> --- PASS: TestImplicitTrue (0.00s)
> === RUN   TestShortFlag
> --- PASS: TestShortFlag (0.00s)
> === RUN   TestShortFlagExtraArgument
> --- PASS: TestShortFlagExtraArgument (0.00s)
> === RUN   TestExplicitMaybe
> --- PASS: TestExplicitMaybe (0.00s)
> === RUN   TestExplicitFalse
> --- PASS: TestExplicitFalse (0.00s)
> === RUN   TestImplicitFalse
> --- PASS: TestImplicitFalse (0.00s)
> === RUN   TestInvalidValue
> --- PASS: TestInvalidValue (0.00s)
> === RUN   TestBoolP
> --- PASS: TestBoolP (0.00s)
> === RUN   TestCount
> --- PASS: TestCount (0.00s)
> === RUN   TestEverything
> --- PASS: TestEverything (0.00s)
> === RUN   TestUsage
> --- PASS: TestUsage (0.00s)
> === RUN   TestAddFlagSet
> --- PASS: TestAddFlagSet (0.00s)
> === RUN   TestAnnotation
> --- PASS: TestAnnotation (0.00s)
> === RUN   TestShorthand
> --- PASS: TestShorthand (0.00s)
> === RUN   TestParse
> --- PASS: TestParse (0.00s)
> === RUN   TestFlagSetParse
> --- PASS: TestFlagSetParse (0.00s)
> === RUN   TestChangedHelper
> --- PASS: TestChangedHelper (0.00s)
> === RUN   TestWordSepNormalizedNames
> --- PASS: TestWordSepNormalizedNames (0.00s)
> === RUN   TestCustomNormalizedNames
> --- PASS: TestCustomNormalizedNames (0.00s)
> === RUN   TestNormalizationFuncShouldChangeFlagName
> --- PASS: TestNormalizationFuncShouldChangeFlagName (0.00s)
> === RUN   TestUserDefined
> --- PASS: TestUserDefined (0.00s)
> === RUN   TestSetOutput
> --- PASS: TestSetOutput (0.00s)
> === RUN   TestChangingArgs
> --- PASS: TestChangingArgs (0.00s)
> === RUN   TestHelp
> --- PASS: TestHelp (0.00s)
> === RUN   TestNoInterspersed
> --- PASS: TestNoInterspersed (0.00s)
> === RUN   TestTermination
> --- PASS: TestTermination (0.00s)
> === RUN   TestDeprecatedFlagInDocs
> --- PASS: TestDeprecatedFlagInDocs (0.00s)
> === RUN   TestDeprecatedFlagShorthandInDocs
> --- PASS: TestDeprecatedFlagShorthandInDocs (0.00s)
> === RUN   TestDeprecatedFlagUsage
> --- PASS: TestDeprecatedFlagUsage (0.00s)
> === RUN   TestDeprecatedFlagShorthandUsage
> --- PASS: TestDeprecatedFlagShorthandUsage (0.00s)
> === RUN   TestDeprecatedFlagUsageNormalized
> --- PASS: TestDeprecatedFlagUsageNormalized (0.00s)
> === RUN   TestMultipleNormalizeFlagNameInvocations
> --- PASS: TestMultipleNormalizeFlagNameInvocations (0.00s)
> === RUN   TestHiddenFlagInUsage
> --- PASS: TestHiddenFlagInUsage (0.00s)
> === RUN   TestHiddenFlagUsage
> --- PASS: TestHiddenFlagUsage (0.00s)
> === RUN   TestPrintDefaults
> 
>   --Afor bootstrapping, allow 'any' type
>   --Alongflagnamedisable bounds checking
>   -C, --CCC  a boolean defaulting to true (default true)
>   --D path   set relative path for local imports
>   --F number a non-zero number (default 2.7)
>   --G float  a float that defaults to zero
>   --N inta non-zero int (default 27)
>   --ND1 string[="bar"]   a string with NoOptDefVal (default "foo")
>   --ND2 num[=4321]   a num with NoOptDefVal (default 1234)
>   --Z intan int that defaults to zero
>   --maxT timeout set timeout for dial (default 0s)
> 
> 
>   --Afor bootstrapping, allow 'any' type
>   --Alongflagnamedisable bounds checking
>   -C, --CCC  a boolean defaulting to true (default true)
>   --D path   set relative path for local imports
>   --F number a non-zero number (default 2.7)
>   --G float  a float that defaults to zero
>   --N inta non-zero int (default 27)
>   --ND1 string[="bar"]   a string with NoOptDefVal (default "foo")
>   --ND2 num[=4321]   a num with NoOptDefVal (default 1234)
>   --Z int   

Bug#835715: golang-github-docker-go: FTBFS: patches fail to apply

2016-08-28 Thread Lucas Nussbaum
Source: golang-github-docker-go
Version: 0.0~git20160303.0.d30aec9-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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[2]: Entering directory '/<>'
> mkdir -p /<>/canonical/json;
> cp -r /usr/lib/go-1.7/src/encoding/json/* /<>/canonical/json/;
> cat /<>/patches/* | patch -p1;
> patching file canonical/json/decode.go
> Hunk #1 succeeded at 254 (offset 80 lines).
> Hunk #2 succeeded at 649 (offset 91 lines).
> patching file canonical/json/encode.go
> Hunk #1 FAILED at 131.
> Hunk #2 succeeded at 163 (offset 10 lines).
> Hunk #3 succeeded at 267 with fuzz 1 (offset 10 lines).
> Hunk #4 FAILED at 313.
> Hunk #5 succeeded at 338 (offset 15 lines).
> Hunk #6 succeeded at 371 (offset 15 lines).
> Hunk #7 succeeded at 386 (offset 15 lines).
> Hunk #8 succeeded at 401 (offset 15 lines).
> Hunk #9 succeeded at 421 (offset 15 lines).
> Hunk #10 succeeded at 539 with fuzz 2 (offset 11 lines).
> Hunk #11 succeeded at 620 (offset 17 lines).
> Hunk #12 FAILED at 638.
> Hunk #13 FAILED at 681.
> Hunk #14 succeeded at 742 (offset 36 lines).
> Hunk #15 succeeded at 759 with fuzz 1 (offset 36 lines).
> Hunk #16 FAILED at 805.
> Hunk #17 succeeded at 902 (offset 64 lines).
> Hunk #18 FAILED at 885.
> Hunk #19 succeeded at 984 (offset 66 lines).
> Hunk #20 succeeded at 1212 (offset 79 lines).
> Hunk #21 FAILED at 1174.
> Hunk #22 FAILED at 1194.
> 8 out of 22 hunks FAILED -- saving rejects to file 
> canonical/json/encode.go.rej
> patching file canonical/json/encode_test.go
> Reversed (or previously applied) patch detected!  Assume -R? [n] 
> Apply anyway? [n] 
> Skipping patch.
> 2 out of 2 hunks ignored -- saving rejects to file 
> canonical/json/encode_test.go.rej
> patching file canonical/json/stream.go
> Hunk #1 FAILED at 138.
> Hunk #2 succeeded at 180 with fuzz 1 (offset 33 lines).
> Hunk #3 FAILED at 160.
> 2 out of 3 hunks FAILED -- saving rejects to file canonical/json/stream.go.rej
> patching file canonical/json/encode_test.go
> Hunk #1 succeeded at 611 with fuzz 1 (offset 31 lines).
> patching file canonical/json/encode.go
> Hunk #1 FAILED at 526.
> 1 out of 1 hunk FAILED -- saving rejects to file canonical/json/encode.go.rej
> patching file canonical/json/encode_test.go
> Hunk #1 succeeded at 620 (offset 31 lines).
> Makefile:17: recipe for target 'run_patch' failed
> make[2]: *** [run_patch] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/08/28/golang-github-docker-go_0.0~git20160303.0.d30aec9-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#835722: python-pgmagick: FTBFS: ./src/_Image.cpp:68:116: error: no matching function for call to 'boost::python::class_::def(const char [18], ,

2016-08-28 Thread Lucas Nussbaum
Source: python-pgmagick
Version: 0.6.2-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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):
> x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
> -Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g 
> -fdebug-prefix-map=/build/python2.7-oH9M6v/python2.7-2.7.12=. 
> -fstack-protector-strong -Wformat -Werror=format-security -fPIC 
> -I/usr/include/python2.7 -I/usr/include/GraphicsMagick/ 
> -I/usr/include/python2.7 -c ./src/_Image.cpp -o 
> build/temp.linux-x86_64-2.7/./src/_Image.o 
> -DPGMAGICK_LIB_GRAPHICSMAGICK_1_3_x -D_LIBRARY_VERSION="1.4"
> cc1plus: warning: command line option '-Wstrict-prototypes' is valid for 
> C/ObjC but not for C++
> ./src/_Image.cpp: In function 'void __Image()':
> ./src/_Image.cpp:68:116: error: no matching function for call to 
> 'boost::python::class_::def(const char [18],  overloaded function type>, 
> {anonymous}::Magick_Image_adaptiveThreshold_overloads_2_3)'
>  .def("adaptiveThreshold", &Magick::Image::adaptiveThreshold, 
> Magick_Image_adaptiveThreshold_overloads_2_3())
>   
>   ^
> In file included from /usr/include/boost/python.hpp:18:0,
>  from ./src/_Image.cpp:1:
> /usr/include/boost/python/class.hpp:223:11: note: candidate: template Derived> boost::python::class_::self& boost::python::class_ X1, X2, X3>::def(const boost::python::def_visitor&) [with Derived = 
> Derived; W = Magick::Image; X1 = boost::python::detail::not_specified; X2 = 
> boost::python::detail::not_specified; X3 = 
> boost::python::detail::not_specified]
>  self& def(def_visitor const& visitor)
>^~~
> /usr/include/boost/python/class.hpp:223:11: note:   template argument 
> deduction/substitution failed:
> ./src/_Image.cpp:68:116: note:   mismatched types 'const 
> boost::python::def_visitor' and 'const char [18]'
>  .def("adaptiveThreshold", &Magick::Image::adaptiveThreshold, 
> Magick_Image_adaptiveThreshold_overloads_2_3())
>   
>   ^
> In file included from /usr/include/boost/python.hpp:18:0,
>  from ./src/_Image.cpp:1:
> /usr/include/boost/python/class.hpp:233:11: note: candidate: template F> boost::python::class_::self& boost::python::class_ X2, X3>::def(const char*, F) [with F = F; W = Magick::Image; X1 = 
> boost::python::detail::not_specified; X2 = 
> boost::python::detail::not_specified; X3 = 
> boost::python::detail::not_specified]
>  self& def(char const* name, F f)
>^~~
> /usr/include/boost/python/class.hpp:233:11: note:   template argument 
> deduction/substitution failed:
> ./src/_Image.cpp:68:116: note:   candidate expects 2 arguments, 3 provided
>  .def("adaptiveThreshold", &Magick::Image::adaptiveThreshold, 
> Magick_Image_adaptiveThreshold_overloads_2_3())
>   
>   ^
> In file included from /usr/include/boost/python.hpp:18:0,
>  from ./src/_Image.cpp:1:
> /usr/include/boost/python/class.hpp:242:11: note: candidate: template A1, class A2> boost::python::class_::self& 
> boost::python::class_::def(const char*, A1, const A2&) [with 
> A1 = A1; A2 = A2; W = Magick::Image; X1 = 
> boost::python::detail::not_specified; X2 = 
> boost::python::detail::not_specified; X3 = 
> boost::python::detail::not_specified]
>  self& def(char const* name, A1 a1, A2 const& a2)
>^~~
> /usr/include/boost/python/class.hpp:242:11: note:   template argument 
> deduction/substitution failed:
> ./src/_Image.cpp:68:116: note:   couldn't deduce template parameter 'A1'
>  .def("adaptiveThreshold", &Magick::Image::adaptiveThreshold, 
> Magick_Image_adaptiveThreshold_overloads_2_3())
>   
>   ^
> In file included from /usr/include/boost/python.hpp:18:0,
>  from ./src/_Image.cpp:1:
> /usr/include/boost/python/class.hpp:249:11: note: candidate: template Fn, class A1, class A2> boost::python::class_::self& 
> boost::python::class_::def(const char*, Fn, const A1&, const 
> A2&) [with Fn = Fn; A1 = 

Bug#835719: monkeysphere: FTBFS: /<>/tests/../src/share/m/subkey_to_ssh_agent: line 123: agent-transfer: command not found

2016-08-28 Thread Lucas Nussbaum
Source: monkeysphere
Version: 0.38-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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 '/<>'
> MONKEYSPHERE_TEST_NO_EXAMINE=true ./tests/keytrans
> ##
> ### generating openpgp key...
> gpg: keybox '/<>/tests/tmp/ms.iTn/pubring.kbx' created
> gpg: /<>/tests/tmp/ms.iTn/trustdb.gpg: trustdb created
> gpg: key E986E81CA943A3B2 marked as ultimately trusted
> gpg: directory '/<>/tests/tmp/ms.iTn/openpgp-revocs.d' created
> gpg: revocation certificate stored as 
> '/<>/tests/tmp/ms.iTn/openpgp-revocs.d/7ED1F3C2EE6BAE213AF36D94E986E81CA943A3B2.rev'
> gpg: done
> ##
> ### retrieving key timestamp...
> gpg: checking the trustdb
> gpg: marginals needed: 3  completes needed: 1  trust model: pgp
> gpg: depth: 0  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 1u
> ##
> ### exporting key to ssh file...
> ##
> ### reconvert key, and compare to key in gpg keyring...
> conversions look good!
> Now working with key E986E81CA943A3B2 at time 1472342839
> gpg: marginals needed: 3  completes needed: 1  trust model: pgp
> gpg: depth: 0  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 1u
> /<>/tests/tmp/ms.iTn/pubring.kbx
> -
> pub   rsa1024 2016-08-28 [SC]
>   7ED1F3C2EE6BAE213AF36D94E986E81CA943A3B2
> uid   [ultimate] testtest
> 
> ##
> ### test User ID addition...
> gpg: key E986E81CA943A3B2: "monkeymonkey" 1 new user ID
> gpg: key E986E81CA943A3B2: "monkeymonkey" 1 new signature
> gpg: Total number processed: 1
> gpg:   new user IDs: 1
> gpg: new signatures: 1
> gpg: marginals needed: 3  completes needed: 1  trust model: pgp
> gpg: depth: 0  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 1u
> /<>/tests/tmp/ms.iTn/pubring.kbx
> -
> pub   rsa1024 2016-08-28 [SC]
>   7ED1F3C2EE6BAE213AF36D94E986E81CA943A3B2
> uid   [ultimate] monkeymonkey
> uid   [ultimate] testtest
> 
> ##
> ### sleeping to avoid test suite breakage on fast
> ### processors (see http://bugs.debian.org/591118)
> ##
> ### test User ID revocation ... 
> gpg: key E986E81CA943A3B2: "monkeymonkey" 1 new signature
> gpg: Total number processed: 1
> gpg: new signatures: 1
> gpg: marginals needed: 3  completes needed: 1  trust model: pgp
> gpg: depth: 0  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 1u
> /<>/tests/tmp/ms.iTn/pubring.kbx
> -
> pub   rsa1024 2016-08-28 [SC]
>   7ED1F3C2EE6BAE213AF36D94E986E81CA943A3B2
> uid   [ultimate] monkeymonkey
> uid   [ revoked] testtest
> 
> ##
> ### test working with two primary keys ... 
> Generating public/private rsa key pair.
> Your identification has been saved in 
> /<>/tests/tmp/ms.iTn/newkey.
> Your public key has been saved in 
> /<>/tests/tmp/ms.iTn/newkey.pub.
> The key fingerprint is:
> SHA256:LoU6seNVsyWDU0ufKbKQxlvazuUcoVbaz9lg3aJnkHk user42@ip-172-31-14-246
> The key's randomart image is:
> +---[RSA 1024]+
> | |
> | |
> |o|
> |   . . = o o |
> |* * S =o |
> |   . X % O+.E.   |
> |B O * ooo .  |
> |   . B = = =o.   |
> |. o o =o.|
> +[SHA256]-+
> gpg: key 7FE80A2A9912726D: public key "fubar" imported
> gpg: key 7FE80A2A9912726D: secret key imported
> gpg: Total number processed: 1
> gpg:   imported: 1
> gpg:   secret keys read: 1
> gpg:   secret keys imported: 1
> gpg: key E986E81CA943A3B2: "monkeymonkey" 1 new user ID
> gpg: key E986E81CA943A3B2: "monkeymonkey" 1 new signature
> gpg: Total number processed: 1
> gpg:   new user IDs: 1
> gpg: new signatures: 1
> test: diff expected gpg list output
> test: diff expected keytrans listfpr output
> ##
>  Monkeysphere keytrans test completed successf

Bug#835713: safecat: FTBFS: sed: -e expression #1, char 43: unknown option to `s'

2016-08-28 Thread Lucas Nussbaum
Source: safecat
Version: 1.13-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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
>dh_testdir
>dh_update_autotools_config
>debian/rules override_dh_auto_configure
> make[1]: Entering directory '/<>'
> sed -i -e "s/cc \(.*\)/cc -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security 
> -D_LARGEFILE64_SOURCE \1/" conf-cc
> sed: -e expression #1, char 43: unknown option to `s'
> debian/rules:9: recipe for target 'override_dh_auto_configure' failed
> make[1]: *** [override_dh_auto_configure] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/08/28/safecat_1.13-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#835724: xtables-addons: FTBFS: dh_install: missing files, aborting

2016-08-28 Thread Lucas Nussbaum
Source: xtables-addons
Version: 2.11-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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[5]: Entering directory '/<>'
> make[5]: Leaving directory '/<>'
>  /bin/mkdir -p '/<>/debian/tmp/usr/share/man/man8'
>  /usr/bin/install -c -m 644 xtables-addons.8 
> '/<>/debian/tmp/usr/share/man/man8'
> make[4]: Leaving directory '/<>'
> make[3]: Leaving directory '/<>'
> make[2]: Leaving directory '/<>'
> make[1]: Leaving directory '/<>'
>dh_install
> dh_install: Cannot find (any matches for) "lib/xtables" (tried in "." and 
> "debian/tmp")
> dh_install: xtables-addons-common missing files: lib/xtables
> dh_install: missing files, aborting
> debian/rules:17: recipe for target 'binary' failed
> make: *** [binary] Error 2

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/08/28/xtables-addons_2.11-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#835728: ggcov: FTBFS: Tests failures

2016-08-28 Thread Lucas Nussbaum
Source: ggcov
Version: 0.9-11
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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):
> ERROR: (test007) tggcov failed, see log or re-run with -D all,verbose --no-log
> ERROR: (test008.0) tggcov failed, see log or re-run with -D all,verbose 
> --no-log
> ERROR: (test009) tggcov failed, see log or re-run with -D all,verbose --no-log
> ERROR: (test010) tggcov failed, see log or re-run with -D all,verbose --no-log
> ERROR: (test011.1) tggcov failed, see log or re-run with -D all,verbose 
> --no-log
> ERROR: (test013) tggcov failed, see log or re-run with -D all,verbose --no-log
> ERROR: (test014) tggcov failed, see log or re-run with -D all,verbose --no-log
> ERROR: (test015.a001) tggcov failed, see log or re-run with -D all,verbose 
> --no-log
> ERROR: (test016.1) tggcov failed, see log or re-run with -D all,verbose 
> --no-log
> PASS: (test021) unit test for libpopt / fakepopt.c
> ERROR: (test029) tggcov failed, see log or re-run with -D all,verbose --no-log
> ERROR: (test030) tggcov failed, see log or re-run with -D all,verbose --no-log
> ERROR: (test033) tggcov failed, see log or re-run with -D all,verbose --no-log
> ERROR: (test034) tggcov failed, see log or re-run with -D all,verbose --no-log
> Total: 2/20 tests passed
> debian/rules:34: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/08/28/ggcov_0.9-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#835731: libdbix-class-perl: FTBFS: Tests failures

2016-08-28 Thread Lucas Nussbaum
Source: libdbix-class-perl
Version: 0.082840-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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):
> ok 3 # skip Not checking for bless handling as performance is OK
> 1..3
> # Auto checked 0 references for leaks - none detected
> ok
> t/zzz_sqlite_deadlock.t . skipped: Skipping test 
> on plain module install
> 
> Test Summary Report
> ---
> t/prefetch/grouped.t  (Wstat: 65280 Tests: 31 
> Failed: 1)
>   Failed test:  28
>   Non-zero exit status: 255
>   Parse errors: No plan found in TAP output
> Files=308, Tests=13370, 114 wallclock secs ( 2.17 usr  0.60 sys + 106.21 cusr 
>  5.45 csys = 114.43 CPU)
> Result: FAIL
> Failed 1/308 test programs. 1/13370 subtests failed.
> Makefile:1697: recipe for target 'test_dynamic' failed

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/08/28/libdbix-class-perl_0.082840-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#835727: ii-esu: FTBFS: ld: /usr/lib/gcc/x86_64-linux-gnu/6/libgphobos2.a(lt4-curl.o): undefined reference to symbol 'dlclose@@GLIBC_2.2.5'

2016-08-28 Thread Lucas Nussbaum
Source: ii-esu
Version: 1.0a.dfsg1-7
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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):
> cc1d: warning: command line option '-Wdate-time' is valid for 
> C/C++/Fortran/ObjC/ObjC++ but not for D
> /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/6/libgphobos2.a(lt4-curl.o): 
> undefined reference to symbol 'dlclose@@GLIBC_2.2.5'
> //lib/x86_64-linux-gnu/libdl.so.2: 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/08/28/ii-esu_1.0a.dfsg1-7_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#835730: mercurial: FTBFS: Tests failures

2016-08-28 Thread Lucas Nussbaum
Source: mercurial
Version: 3.9-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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):
> Skipped test-convert-tagsbranch-topology.t: missing feature: git command line 
> client
> Skipped test-mac-packages.t: missing feature: OS X packaging tools
> Skipped test-chg.t: missing feature: running with chg
> Skipped test-verify-repo-operations.py: missing feature: allow slow tests
> Skipped test-convert-bzr-merges.t: missing feature: Canonical's Bazaar client
> Skipped test-no-symlinks.t: system supports symbolic links
> Skipped test-docker-packaging.t: missing feature: docker support
> Skipped test-convert-bzr-ghosts.t: missing feature: Canonical's Bazaar client
> Skipped test-convert-bzr-114.t: missing feature: Canonical's Bazaar client >= 
> 1.14
> Skipped test-convert-bzr-treeroot.t: missing feature: Canonical's Bazaar 
> client
> Skipped test-debian-packages.t: missing feature: debian packaging tools
> Failed test-gpg.t: output changed
> # Ran 474 tests, 49 skipped, 0 warned, 1 failed.
> python hash seed: 3324319778
> # Cleaning up HGTMP /tmp/hgtests.fBryXH 
> Makefile:110: recipe for target 'tests' failed

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/08/28/mercurial_3.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.



Bug#835726: kate: FTBFS: dh_install: missing files, aborting

2016-08-28 Thread Lucas Nussbaum
Source: kate
Version: 4:16.04.2-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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 '/<>/obj-x86_64-linux-gnu'
> make[4]: Nothing to be done for 'preinstall'.
> make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> Install the project...
> /usr/bin/cmake -P cmake_install.cmake
> -- Install configuration: "Debian"
> -- Installing: /<>/debian/tmp/usr/bin/kwrite
> -- Installing: 
> /<>/debian/tmp/usr/share/applications/org.kde.kwrite.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/metainfo/org.kde.kwrite.appdata.xml
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/16x16/apps/kwrite.png
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/22x22/apps/kwrite.png
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/32x32/apps/kwrite.png
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/48x48/apps/kwrite.png
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/64x64/apps/kwrite.png
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/128x128/apps/kwrite.png
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/scalable/apps/kwrite.svgz
> -- Installing: /<>/debian/tmp/usr/bin/kate
> -- Installing: 
> /<>/debian/tmp/usr/share/applications/org.kde.kate.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/metainfo/org.kde.kate.appdata.xml
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/16x16/apps/kate.png
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/22x22/apps/kate.png
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/32x32/apps/kate.png
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/48x48/apps/kate.png
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/64x64/apps/kate.png
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/128x128/apps/kate.png
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/scalable/apps/kate.svgz
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/ktexteditor/katefiletreeplugin.so
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/ktexteditor/katesearchplugin.so
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/ktexteditor/tabswitcherplugin.so
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/ktexteditor/katectagsplugin.so
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/ktexteditor/katebacktracebrowserplugin.so
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/ktexteditor/katefilebrowserplugin.so
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/ktexteditor/katexmltoolsplugin.so
> -- Installing: 
> /<>/debian/tmp/usr/share/kxmlgui5/katexmltools/ui.rc
> -- Installing: 
> /<>/debian/tmp/usr/share/katexmltools/html4-loose.dtd.xml
> -- Installing: 
> /<>/debian/tmp/usr/share/katexmltools/html4-strict.dtd.xml
> -- Installing: 
> /<>/debian/tmp/usr/share/katexmltools/kde-docbook.dtd.xml
> -- Installing: 
> /<>/debian/tmp/usr/share/katexmltools/simplify_dtd.xsl
> -- Installing: 
> /<>/debian/tmp/usr/share/katexmltools/xhtml1-frameset.dtd.xml
> -- Installing: 
> /<>/debian/tmp/usr/share/katexmltools/xhtml1-strict.dtd.xml
> -- Installing: 
> /<>/debian/tmp/usr/share/katexmltools/xhtml1-transitional.dtd.xml
> -- Installing: 
> /<>/debian/tmp/usr/share/katexmltools/xslt-1.0.dtd.xml
> -- Installing: 
> /<>/debian/tmp/usr/share/katexmltools/testcases.xml
> -- Installing: 
> /<>/debian/tmp/usr/share/katexmltools/language.dtd.xml
> -- Installing: 
> /<>/debian/tmp/usr/share/katexmltools/kpartgui.dtd.xml
> -- Installing: /<>/debian/tmp/usr/share/katexmltools/kcfg.dtd.xml
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/ktexteditor/kateopenheaderplugin.so
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/ktexteditor/kategdbplugin.so
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/ktexteditor/katesymbolviewerplugin.so
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/ktexteditor/katereplicodeplugin.so
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/ktexteditor/textfilterplugin.so
> -- Installing: 
> /<&g

Bug#835725: python-netlib: FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned exit code 13

2016-08-28 Thread Lucas Nussbaum
Source: python-netlib
Version: 0.15.1-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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 python2 --buildsystem=pybuild
>dh_testdir -O--buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_2.7/build/netlib
> copying netlib/version_check.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/netlib
> copying netlib/encoding.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/netlib
> copying netlib/utils.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/netlib
> copying netlib/socks.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/netlib
> copying netlib/wsgi.py -> /<>/.pybuild/pythonX.Y_2.7/build/netlib
> copying netlib/exceptions.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/netlib
> copying netlib/tcp.py -> /<>/.pybuild/pythonX.Y_2.7/build/netlib
> copying netlib/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/netlib
> copying netlib/certutils.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/netlib
> copying netlib/tutils.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/netlib
> copying netlib/version.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/netlib
> copying netlib/odict.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/netlib
> creating /<>/.pybuild/pythonX.Y_2.7/build/test
> copying test/test_utils.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/test
> copying test/test_socks.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/test
> copying test/test_wsgi.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/test
> copying test/test_version_check.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/test
> copying test/test_encoding.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/test
> copying test/__init__.py -> /<>/.pybuild/pythonX.Y_2.7/build/test
> copying test/tservers.py -> /<>/.pybuild/pythonX.Y_2.7/build/test
> copying test/test_odict.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/test
> copying test/test_certutils.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/test
> copying test/test_tcp.py -> /<>/.pybuild/pythonX.Y_2.7/build/test
> copying test/test_imports.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/test
> creating /<>/.pybuild/pythonX.Y_2.7/build/netlib/http
> copying netlib/http/response.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/netlib/http
> copying netlib/http/message.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/netlib/http
> copying netlib/http/request.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/netlib/http
> copying netlib/http/cookies.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/netlib/http
> copying netlib/http/status_codes.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/netlib/http
> copying netlib/http/headers.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/netlib/http
> copying netlib/http/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/netlib/http
> copying netlib/http/user_agents.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/netlib/http
> copying netlib/http/authentication.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/netlib/http
> creating /<>/.pybuild/pythonX.Y_2.7/build/netlib/websockets
> copying netlib/websockets/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/netlib/websockets
> copying netlib/websockets/frame.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/netlib/websockets
> copying netlib/websockets/protocol.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/netlib/websockets
> creating /<>/.pybuild/pythonX.Y_2.7/build/netlib/http/http2
> copying netlib/http/http2/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/netlib/http/http2
> copying netlib/http/http2/frame.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/netlib/http/http2
> copying netlib/http/http2/connections.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/netlib/http/http2
> creating /<>/.pybuild/pythonX.Y_2.7/build/netlib/http/http1
> copying netlib/http/http1/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/netlib/http/http1
> copying netlib/http/http1/assemble.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/netlib/http/http1
> copying netlib/http/http1/read.py -

Bug#835729: jasperreports: FTBFS: build-dependency not installable: libitext-java (>= 2.1.7-11~)

2016-08-28 Thread Lucas Nussbaum
Source: jasperreports
Version: 6.2.2-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: ant, libbsh-java, debhelper (>= 9), default-jdk, 
> glassfish-javaee, groovy, libantlr-java, libapache-poi-java, libaxis-java, 
> libbatik-java (>= 1.8), libcastor-core-java, libcastor-xml-java, 
> libcommons-beanutils-java, libcommons-codec-java, 
> libcommons-collections3-java, libcommons-digester-java, libcommons-lang-java, 
> libcommons-logging-java, libecj-java, libgeronimo-jpa-2.0-spec-java, 
> libhibernate3-java, libhttpclient-java, libicu4j-java, libitext-java (>= 
> 2.1.7-11~), libjackson2-annotations-java, libjackson2-core-java, 
> libjackson2-databind-java, libjaxen-java, libjaxp1.3-java, libjcommon-java, 
> libjexcelapi-java, libjfreechart-java, liblucene4.10-java (>= 
> 4.10.4+dfsg-2~), libmaven-javadoc-plugin-java, libmondrian-java (>= 
> 1:3.11.0.1-4~), libolap4j-java, librhino-java, libspring-beans-java, 
> libspring-core-java, libxalan2-java, libxmpcore-java, maven-debian-helper, 
> velocity
> Filtered Build-Depends: ant, libbsh-java, debhelper (>= 9), default-jdk, 
> glassfish-javaee, groovy, libantlr-java, libapache-poi-java, libaxis-java, 
> libbatik-java (>= 1.8), libcastor-core-java, libcastor-xml-java, 
> libcommons-beanutils-java, libcommons-codec-java, 
> libcommons-collections3-java, libcommons-digester-java, libcommons-lang-java, 
> libcommons-logging-java, libecj-java, libgeronimo-jpa-2.0-spec-java, 
> libhibernate3-java, libhttpclient-java, libicu4j-java, libitext-java (>= 
> 2.1.7-11~), libjackson2-annotations-java, libjackson2-core-java, 
> libjackson2-databind-java, libjaxen-java, libjaxp1.3-java, libjcommon-java, 
> libjexcelapi-java, libjfreechart-java, liblucene4.10-java (>= 
> 4.10.4+dfsg-2~), libmaven-javadoc-plugin-java, libmondrian-java (>= 
> 1:3.11.0.1-4~), libolap4j-java, librhino-java, libspring-beans-java, 
> libspring-core-java, libxalan2-java, libxmpcore-java, maven-debian-helper, 
> velocity
> dpkg-deb: building package 'sbuild-build-depends-jasperreports-dummy' in 
> '/<>/resolver-7zFc3z/apt_archive/sbuild-build-depends-jasperreports-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-jasperreports-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-7zFc3z/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-7zFc3z/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-7zFc3z/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-7zFc3z/apt_archive ./ Sources [683 B]
> Get:5 copy:/<>/resolver-7zFc3z/apt_archive ./ Packages [778 B]
> Fetched 2424 B in 0s (0 B/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install jasperreports build dependencies (apt-based resolver)
> -
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-jasperreports-dummy : Depends: libitext-java (>= 
> 2.1.7-11~) but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/08/28/jasperreports_6.2.2-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#835735: connman: FTBFS: dh_install: missing files, aborting

2016-08-28 Thread Lucas Nussbaum
Source: connman
Version: 1.32-0.1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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 '/<>'
> find /<> -name "*.la" -print -delete
> /<>/gdbus/libgdbus-internal.la
> /<>/gdbus/.libs/libgdbus-internal.la
> /<>/scripts/libppp-plugin.la
> /<>/scripts/.libs/libppp-plugin.la
> /<>/vpn/plugins/l2tp.la
> /<>/vpn/plugins/openvpn.la
> /<>/vpn/plugins/openconnect.la
> /<>/vpn/plugins/.libs/l2tp.la
> /<>/vpn/plugins/.libs/openvpn.la
> /<>/vpn/plugins/.libs/openconnect.la
> /<>/vpn/plugins/.libs/pptp.la
> /<>/vpn/plugins/pptp.la
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/connman/scripts/libppp-plugin.la
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/connman/plugins-vpn/l2tp.la
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/connman/plugins-vpn/openvpn.la
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/connman/plugins-vpn/openconnect.la
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/connman/plugins-vpn/pptp.la
> dh_install --fail-missing
> dh_install: Cannot find (any matches for) 
> "usr/lib/tmpfiles.d/connman_resolvconf.conf" (tried in "." and "debian/tmp")
> dh_install: connman missing files: usr/lib/tmpfiles.d/connman_resolvconf.conf
> dh_install: missing files, aborting
> debian/rules:24: recipe for target 'override_dh_install' failed
> make[1]: *** [override_dh_install] Error 2

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/08/28/connman_1.32-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#835733: libvirt-php: FTBFS: rm: cannot remove '/<>/debian/php-libvirt-php/etc/php/7.0': No such file or directory

2016-08-28 Thread Lucas Nussbaum
Source: libvirt-php
Version: 0.5.2~30-g64dca6f-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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 '/<>/build-7.0'
> make[4]: Nothing to be done for 'install-exec-am'.
> make[4]: Nothing to be done for 'install-data-am'.
> make[4]: Leaving directory '/<>/build-7.0'
> make[3]: Leaving directory '/<>/build-7.0'
> make[2]: Leaving directory '/<>/build-7.0'
>   cd /<>
> rm: cannot remove '/<>/debian/php-libvirt-php/etc/php/7.0': No 
> such file or directory
> debian/rules:43: recipe for target 'override_dh_auto_install' failed
> make[1]: *** [override_dh_auto_install] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/08/28/libvirt-php_0.5.2~30-g64dca6f-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#835736: containerd: FTBFS: dh_auto_build: go install -v -p 1 github.com/docker/containerd github.com/docker/containerd/api/grpc/server github.com/docker/containerd/api/grpc/types github.com/docker

2016-08-28 Thread Lucas Nussbaum
Source: containerd
Version: 0.2.1~ds1-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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 --buildsystem=golang --with=golang
>dh_testdir -O--buildsystem=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   go install -v -p 1 github.com/docker/containerd 
> github.com/docker/containerd/api/grpc/server 
> github.com/docker/containerd/api/grpc/types 
> github.com/docker/containerd/api/http/pprof 
> github.com/docker/containerd/containerd 
> github.com/docker/containerd/containerd-shim github.com/docker/containerd/ctr 
> github.com/docker/containerd/osutils github.com/docker/containerd/runtime 
> github.com/docker/containerd/specs github.com/docker/containerd/supervisor
> github.com/docker/containerd
> github.com/golang/protobuf/proto
> golang.org/x/net/context
> golang.org/x/net/http2/hpack
> golang.org/x/net/lex/httplex
> golang.org/x/net/http2
> golang.org/x/net/internal/timeseries
> golang.org/x/net/trace
> google.golang.org/grpc/codes
> google.golang.org/grpc/credentials
> google.golang.org/grpc/grpclog
> google.golang.org/grpc/internal
> google.golang.org/grpc/metadata
> google.golang.org/grpc/naming
> google.golang.org/grpc/peer
> google.golang.org/grpc/transport
> google.golang.org/grpc
> github.com/docker/containerd/api/grpc/types
> # github.com/docker/containerd/api/grpc/types
> src/github.com/docker/containerd/api/grpc/types/api.pb.go:1137: cannot use 
> _API_CreateContainer_Handler (type func(interface {}, 
> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
> error)) as type grpc.methodHandler in field value
> src/github.com/docker/containerd/api/grpc/types/api.pb.go:1141: cannot use 
> _API_UpdateContainer_Handler (type func(interface {}, 
> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
> error)) as type grpc.methodHandler in field value
> src/github.com/docker/containerd/api/grpc/types/api.pb.go:1145: cannot use 
> _API_Signal_Handler (type func(interface {}, 
> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
> error)) as type grpc.methodHandler in field value
> src/github.com/docker/containerd/api/grpc/types/api.pb.go:1149: cannot use 
> _API_UpdateProcess_Handler (type func(interface {}, 
> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
> error)) as type grpc.methodHandler in field value
> src/github.com/docker/containerd/api/grpc/types/api.pb.go:1153: cannot use 
> _API_AddProcess_Handler (type func(interface {}, 
> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
> error)) as type grpc.methodHandler in field value
> src/github.com/docker/containerd/api/grpc/types/api.pb.go:1157: cannot use 
> _API_CreateCheckpoint_Handler (type func(interface {}, 
> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
> error)) as type grpc.methodHandler in field value
> src/github.com/docker/containerd/api/grpc/types/api.pb.go:1161: cannot use 
> _API_DeleteCheckpoint_Handler (type func(interface {}, 
> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
> error)) as type grpc.methodHandler in field value
> src/github.com/docker/containerd/api/grpc/types/api.pb.go:1165: cannot use 
> _API_ListCheckpoint_Handler (type func(interface {}, 
> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
> error)) as type grpc.methodHandler in field value
> src/github.com/docker/containerd/api/grpc/types/api.pb.go:1169: cannot use 
> _API_State_Handler (type func(interface {}, 
> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
> error)) as type grpc.methodHandler in field value
> src/github.com/docker/containerd/api/grpc/types/api.pb.go:1173: cannot use 
> _API_Stats_Handler (type func(interface {}, 
> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
> error)) as type grpc.methodHandler in field value
> src/github.com/docker/containerd/api/grpc/types/api.pb.go:1173: too many 
> errors
> github.com/Sirupsen/logrus
> github.com/opencontainers/specs/specs-go
> github.com/docker/containerd/specs
> github.com/opencontainers/runc/vendor/github.com/docker/docker/pkg/mount
> github.com/opencontainers/runc/vendor/github.com/docker/docker/pkg/symlink
> github.com/opencontai

Bug#835732: gcc-6-cross: FTBFS: patch fails to apply

2016-08-28 Thread Lucas Nussbaum
Source: gcc-6-cross
Version: 12
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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 '/<>/gcc'
> : # unpack gcc tarball
> mkdir -p stamps
> if [ -d /<>/gcc/src ]; then \
>   echo >&2 "Source directory /<>/gcc/src exists. Delete by 
> hand"; \
>   false; \
> fi
> rm -rf gcc-6.2.0
> tar -x -f /usr/src/gcc-6/gcc-6.2.0-dfsg.tar.xz
> mv gcc-6.2.0 /<>/gcc/src
> ln -sf libsanitizer /<>/gcc/src/libasan
> rm -f /<>/gcc/src/gcc/doc/*.1
> rm -f /<>/gcc/src/gcc/doc/fsf-funding.7
> rm -f /<>/gcc/src/gcc/doc/*.info
> rm -f /<>/gcc/src/gcc/fortran/*.info
> rm -f /<>/gcc/src/libgomp/*.info
> rm -f /<>/gcc/src/gcc/java/*.1
> rm -f /<>/gcc/src/gcc/java/*.info
> for i in gcc/doc/avr-mmcu.texi gcc/doc/bugreport.texi gcc/doc/cfg.texi 
> gcc/doc/collect2.texi gcc/doc/compat.texi gcc/doc/configfiles.texi 
> gcc/doc/configterms.texi gcc/doc/contrib.texi gcc/doc/contribute.texi 
> gcc/doc/cpp.texi gcc/doc/cppenv.texi gcc/doc/cppinternals.texi 
> gcc/doc/cppopts.texi gcc/doc/extend.texi gcc/doc/fragments.texi 
> gcc/doc/frontends.texi gcc/doc/gccint.texi gcc/doc/gcov.texi 
> gcc/doc/generic.texi gcc/doc/gimple.texi gcc/doc/gnu.texi gcc/doc/gty.texi 
> gcc/doc/headerdirs.texi gcc/doc/hostconfig.texi gcc/doc/implement-c.texi 
> gcc/doc/implement-cxx.texi gcc/doc/install-old.texi gcc/doc/install.texi 
> gcc/doc/interface.texi gcc/doc/invoke.texi gcc/doc/languages.texi 
> gcc/doc/libgcc.texi gcc/doc/loop.texi gcc/doc/lto.texi gcc/doc/makefile.texi 
> gcc/doc/match-and-simplify.texi gcc/doc/md.texi gcc/doc/objc.texi 
> gcc/doc/optinfo.texi gcc/doc/options.texi gcc/doc/passes.texi 
> gcc/doc/plugins.texi gcc/doc/portability.texi gcc/doc/rtl.texi 
> gcc/doc/service.texi gcc/doc/sourcebuild.texi gcc/doc/standards.texi 
> gcc/doc/tm.texi.in gcc/doc/tm.texi gcc/doc/tree-ssa.texi gcc/doc/trouble.texi 
> gcc/doc/include/gcc-common.texi gcc/doc/include/funding.texi 
> gcc/fortran/gfc-internals.texi gcc/fortran/invoke.texi 
> gcc/fortran/intrinsic.texi ; do \
>   if [ -f /<>/gcc/src/$i ]; then \
> cp debian/dummy.texi /<>/gcc/src/$i; \
>   else \
> cp debian/dummy.texi /<>/gcc/src/$i; \
> echo >&2 "$i does not exist, fix debian/rules.unpack"; \
>   fi; \
> done
> for i in gcc/doc/gcc.texi gcc/java/gcj.texi gcc/ada/gnat-style.texi 
> gcc/ada/gnat_rm.texi gcc/ada/gnat_ugn.texi gcc/fortran/gfortran.texi 
> gcc/go/gccgo.texi libgomp/libgomp.texi libquadmath/libquadmath.texi ; do \
>   n=$(basename $i .texi); \
>   if [ -f /<>/gcc/src/$i ]; then \
> sed "s/@name@/$n/g" debian/gcc-dummy.texi \
>   > /<>/gcc/src/$i; \
>   else \
> sed "s/@name@/$n/g" debian/gcc-dummy.texi \
>   > /<>/gcc/src/$i; \
> echo >&2 "$i does not exist, fix debian/rules.unpack"; \
>   fi; \
> done
> for i in gcc/doc/cpp.1 gcc/doc/g++.1 gcc/doc/gc-analyze.1 gcc/doc/gcc.1 
> gcc/doc/gccgo.1 gcc/doc/gcj.1 gcc/doc/gcj-dbtool.1 gcc/doc/gcjh.1 
> gcc/doc/gcov.1 gcc/doc/gfortran.1 gcc/doc/gij.1 gcc/doc/grmic.1 
> gcc/doc/grmiregistry.1 gcc/doc/jcf-dump.1 gcc/doc/jv-convert.1 
> gcc/doc/fsf-funding.7 ; do \
>   touch /<>/gcc/src/$i; \
> done
> rm -f /<>/gcc/src/INSTALL/*.html
> echo "gcc-6.2.0-dfsg.tar.xz unpacked." > 
> stamps/01-unpack-stamp-gcc-6.2.0-dfsg.tar.xz
> : # unpack gdc tarball
> mkdir -p stamps
> if [ -d /<>/gcc/src/gcc/d ]; then \
>   echo >&2 "Source directory /<>/gcc/src/gcc/d exists. Delete by 
> hand";\
>   false; \
> fi
> #rm -rf gdc-20160822
> rm -rf /<>/gcc/src/gcc/d
> rm -rf /<>/gcc/src/gcc/testsuite/gdc.test
> rm -f /<>/gcc/src/gcc/testsuite/lib/gdc*.exp
> rm -rf /<>/gcc/src/libphobos
> tar -x -C /<>/gcc/src --strip-components=1 -f 
> /usr/src/gcc-6/gdc-20160822.tar.xz
> echo "gdc-20160822.tar.xz unpacked." > 
> stamps/01-unpack-stamp-gdc-20160822.tar.xz
> echo -e "\nBuilt from Debian source package gcc-6-6.2.0-1" \
>   > pxxx
> echo -e "Integrated upstream packages in this version:\n" >> pxxx
> for i in gcc-6.2.0-dfsg.tar.xz  gdc-20160822.tar.xz; do echo "  $i" >> pxxx; 
> done
> mv -f pxxx stamps/01-unpack-stamp
> echo gcc-gfdl-build.diff gcc-textdomain.diff gcc-driver-extra-langs.diff 
> gcc-hash-style-gnu.diff libstdc++-pic.diff libstdc++-doclink.diff 
> libstdc++-man-3cxx.diff libstdc++-test

Bug#835742: golang-google-cloud: FTBFS: dh_auto_build: go install -v -p 1 google.golang.org/cloud google.golang.org/cloud/bigquery google.golang.org/cloud/bigtable google.golang.org/cloud/bigtable/btt

2016-08-28 Thread Lucas Nussbaum
Source: golang-google-cloud
Version: 0.0~git20160413-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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 --buildsystem=golang --with=golang
>dh_testdir -O--buildsystem=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
> dh_auto_configure: "google.golang.org/cloud" is already installed. Please 
> check for circular dependencies.
> 
>dh_auto_build -O--buildsystem=golang
>   go install -v -p 1 google.golang.org/cloud 
> google.golang.org/cloud/bigquery google.golang.org/cloud/bigtable 
> google.golang.org/cloud/bigtable/bttest 
> google.golang.org/cloud/bigtable/cmd/cbt 
> google.golang.org/cloud/bigtable/cmd/loadtest 
> google.golang.org/cloud/bigtable/internal/cbtrc 
> google.golang.org/cloud/bigtable/internal/cluster_data_proto 
> google.golang.org/cloud/bigtable/internal/cluster_service_proto 
> google.golang.org/cloud/bigtable/internal/data_proto 
> google.golang.org/cloud/bigtable/internal/duration_proto 
> google.golang.org/cloud/bigtable/internal/empty 
> google.golang.org/cloud/bigtable/internal/service_proto 
> google.golang.org/cloud/bigtable/internal/table_data_proto 
> google.golang.org/cloud/bigtable/internal/table_service_proto 
> google.golang.org/cloud/compute/metadata google.golang.org/cloud/container 
> google.golang.org/cloud/datastore 
> google.golang.org/cloud/datastore/internal/proto 
> google.golang.org/cloud/datastore/internal/type_proto 
> google.golang.org/cloud/examples/bigquery/concat_table 
> google.golang.org/cloud/examples/bigquery/load 
> google.golang.org/cloud/examples/bigquery/query 
> google.golang.org/cloud/examples/bigquery/read 
> google.golang.org/cloud/examples/bigtable/bigtable-hello 
> google.golang.org/cloud/examples/bigtable/search 
> google.golang.org/cloud/examples/pubsub/cmdline 
> google.golang.org/cloud/examples/pubsub/consumer 
> google.golang.org/cloud/examples/storage/appengine 
> google.golang.org/cloud/examples/storage/appenginevm 
> google.golang.org/cloud/internal google.golang.org/cloud/internal/opts 
> google.golang.org/cloud/internal/testutil 
> google.golang.org/cloud/internal/transport google.golang.org/cloud/logging 
> google.golang.org/cloud/pubsub google.golang.org/cloud/storage
> golang.org/x/net/context
> golang.org/x/oauth2/internal
> golang.org/x/oauth2
> google.golang.org/cloud/internal
> github.com/golang/protobuf/proto
> golang.org/x/net/http2/hpack
> golang.org/x/net/lex/httplex
> golang.org/x/net/http2
> golang.org/x/net/internal/timeseries
> golang.org/x/net/trace
> google.golang.org/grpc/codes
> google.golang.org/grpc/credentials
> google.golang.org/grpc/grpclog
> google.golang.org/grpc/internal
> google.golang.org/grpc/metadata
> google.golang.org/grpc/naming
> google.golang.org/grpc/peer
> google.golang.org/grpc/transport
> google.golang.org/grpc
> google.golang.org/cloud/internal/opts
> google.golang.org/cloud
> golang.org/x/net/context/ctxhttp
> google.golang.org/api/googleapi/internal/uritemplates
> google.golang.org/api/googleapi
> google.golang.org/api/gensupport
> google.golang.org/api/bigquery/v2
> google.golang.org/cloud/bigquery
> google.golang.org/cloud/bigtable/internal/cluster_data_proto
> google.golang.org/cloud/bigtable/internal/empty
> google.golang.org/cloud/bigtable/internal/cluster_service_proto
> # google.golang.org/cloud/bigtable/internal/cluster_service_proto
> src/google.golang.org/cloud/bigtable/internal/cluster_service_proto/bigtable_cluster_service.pb.go:307:
>  cannot use _BigtableClusterService_ListZones_Handler (type func(interface 
> {}, "golang.org/x/net/context".Context, func(interface {}) error) (interface 
> {}, error)) as type grpc.methodHandler in field value
> src/google.golang.org/cloud/bigtable/internal/cluster_service_proto/bigtable_cluster_service.pb.go:311:
>  cannot use _BigtableClusterService_GetCluster_Handler (type func(interface 
> {}, "golang.org/x/net/context".Context, func(interface {}) error) (interface 
> {}, error)) as type grpc.methodHandler in field value
> src/google.golang.org/cloud/bigtable/internal/cluster_service_proto/bigtable_cluster_service.pb.go:315:
>  cannot use _BigtableClusterService_ListClusters_Handler (type func(interface 
> {}, "golang.org/x/net/context".Context, func(interface {}) error) (interface 
> {}, error)) as type grpc.methodHandler in field value
> src/google.golang.org/cloud/bigtable/internal/cluster_service_proto/bigtable_cluster_service.pb.

Bug#835739: ros-bond-core: FTBFS: cmake errors

2016-08-28 Thread Lucas Nussbaum
Source: ros-bond-core
Version: 1.7.17-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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 --parallel --with=python2 --buildsystem=cmake
>dh_testdir -O--buildsystem=cmake
>dh_update_autotools_config -O--buildsystem=cmake
>dh_auto_configure -O--buildsystem=cmake
>   cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON 
> -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
> -DCMAKE_INSTALL_LOCALSTATEDIR=/var
> -- The C compiler identification is GNU 6.2.0
> -- The CXX compiler identification is GNU 6.2.0
> -- Check for working C compiler: /usr/bin/cc
> -- Check for working C compiler: /usr/bin/cc -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Check for working CXX compiler: /usr/bin/c++
> -- Check for working CXX compiler: /usr/bin/c++ -- works
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Using CATKIN_DEVEL_PREFIX: /<>/obj-x86_64-linux-gnu/devel
> -- Using CMAKE_PREFIX_PATH: 
> -- Found PythonInterp: /usr/bin/python (found version "2.7.12") 
> -- Using PYTHON_EXECUTABLE: /usr/bin/python
> -- Using Debian Python package layout
> -- Using empy: /usr/bin/empy
> -- Using CATKIN_ENABLE_TESTING: ON
> -- Call enable_testing()
> -- Using CATKIN_TEST_RESULTS_DIR: 
> /<>/obj-x86_64-linux-gnu/test_results
> -- Looking for pthread.h
> -- Looking for pthread.h - found
> -- Looking for pthread_create
> -- Looking for pthread_create - not found
> -- Looking for pthread_create in pthreads
> -- Looking for pthread_create in pthreads - not found
> -- Looking for pthread_create in pthread
> -- Looking for pthread_create in pthread - found
> -- Found Threads: TRUE  
> -- Found gtest sources under '/usr/src/gtest': gtests will be built
> CMake Warning at /usr/share/catkin/cmake/test/nosetests.cmake:98 (message):
>   nosetests not found, Python tests can not be run (try installing package
>   'python-nose')
> Call Stack (most recent call first):
>   /usr/share/catkin/cmake/all.cmake:147 (include)
>   /usr/share/catkin/cmake/catkinConfig.cmake:20 (include)
>   bond/CMakeLists.txt:4 (find_package)
> 
> 
> -- catkin 0.7.1
> -- Using these message generators: gencpp;genlisp;genpy
> CMake Error at obj-x86_64-linux-gnu/bond/cmake/bond-genmsg.cmake:3 (message):
>   Could not find messages which
>   '/<>/bond/msg/Status.msg'
>   depends on.  Did you forget to specify generate_messages(DEPENDENCIES ...)?
> 
>   Cannot locate message [Header] in package [std_msgs] with paths
>   [['/usr/share/std_msgs/cmake/../msg']]
> Call Stack (most recent call first):
>   /usr/share/genmsg/cmake/genmsg-extras.cmake:306 (include)
>   bond/CMakeLists.txt:12 (generate_messages)
> 
> 
> -- Configuring incomplete, errors occurred!
> See also "/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log".
> See also "/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeError.log".
>   "tail -v -n +0 CMakeCache.txt"
> ==> CMakeCache.txt <==
> # This is the CMakeCache file.
> # For build in directory: /<>/obj-x86_64-linux-gnu
> # It was generated by CMake: /usr/bin/cmake
> # You can edit this file to change values found and used by cmake.
> # If you do not want to change any of the values, simply exit the editor.
> # If you do want to change a value, simply edit, save, and exit the editor.
> # The syntax for the file is as follows:
> # KEY:TYPE=VALUE
> # KEY is the name of a variable in the cache.
> # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!.
> # VALUE is the current value for the KEY.
> 
> 
> # EXTERNAL cache entries
> 
> 
> //Build shared libraries (DLLs).
> BUILD_SHARED_LIBS:BOOL=ON
> 
> //Catkin enable testing
> CATKIN_ENABLE_TESTING:BOOL=ON
> 
> //Prefix to apply to package generated via gendebian
> CATKIN_PACKAGE_PREFIX:STRING=
> 
> //Catkin skip testing
> CATKIN_SKIP_TESTING:BOOL=OFF
> 
> //Path to a program.
> CMAKE_AR:FILEPATH=/usr/bin/ar
> 
> //Choose the type of build, options are: None(CMAKE_CXX_FLAGS or
> // CMAKE_C_FLAGS used) Debug Release RelWithDebInfo MinSizeRel.
> CMAKE_BUILD_TYPE:STRING=None
> 
> //Enable/Disable color output during build.
> CMAKE_COLOR

Bug#835738: kdepim: FTBFS: dh_install: missing files, aborting

2016-08-28 Thread Lucas Nussbaum
Source: kdepim
Version: 4:16.04.3-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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 '/<>/obj-x86_64-linux-gnu'
> make[3]: Nothing to be done for 'preinstall'.
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> Install the project...
> /usr/bin/cmake -P cmake_install.cmake
> -- Install configuration: "Debian"
> -- Installing: /<>/debian/tmp/etc/xdg/kdepim.categories
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libkmailprivate.so.5.2.3
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libkmailprivate.so.5
> -- Installing: /<>/debian/tmp/usr/bin/kmail
> -- Set runtime path of "/<>/debian/tmp/usr/bin/kmail" to ""
> -- Installing: 
> /<>/debian/tmp/usr/share/applications/org.kde.kmail.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/applications/kmail_view.desktop
> -- Installing: /<>/debian/tmp/usr/share/config.kcfg/kmail.kcfg
> -- Installing: 
> /<>/debian/tmp/usr/share/metainfo/org.kde.kmail.appdata.xml
> -- Installing: 
> /<>/debian/tmp/usr/share/kservices5/kmail_config_misc.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/kservices5/kmail_config_appearance.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/kservices5/kmail_config_identity.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/kservices5/kmail_config_accounts.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/kservices5/kmail_config_composer.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/kservices5/kmail_config_security.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/kxmlgui5/kmail2/kmcomposerui.rc
> -- Installing: 
> /<>/debian/tmp/usr/share/kxmlgui5/kmail2/kmmainwin.rc
> -- Installing: 
> /<>/debian/tmp/usr/share/kxmlgui5/kmail2/kmreadermainwin.rc
> -- Installing: 
> /<>/debian/tmp/usr/share/kxmlgui5/kmail2/kmail_part.rc
> -- Installing: 
> /<>/debian/tmp/usr/share/knotifications5/kmail2.notifyrc
> -- Installing: 
> /<>/debian/tmp/usr/share/kservicetypes5/dbusmail.desktop
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/kmailpart.so
> -- Set runtime path of 
> "/<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/kmailpart.so"
>  to ""
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_kmail.so
> -- Set runtime path of 
> "/<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_kmail.so"
>  to ""
> -- Installing: 
> /<>/debian/tmp/usr/share/dbus-1/interfaces/org.kde.kmail.kmailpart.xml
> -- Installing: 
> /<>/debian/tmp/usr/share/dbus-1/interfaces/org.kde.kmail.kmail.xml
> -- Installing: 
> /<>/debian/tmp/usr/share/kservices5/ServiceMenus/kmail_addattachmentservicemenu.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/messageviewer/about/default/introduction_kmail.html
> -- Installing: 
> /<>/debian/tmp/usr/share/kmail2/pics/mail-thread-ignored.png
> -- Installing: 
> /<>/debian/tmp/usr/share/kmail2/pics/mail-thread-watch.png
> -- Installing: /<>/debian/tmp/usr/share/kmail2/pics/pgp-keys.png
> -- Installing: 
> /<>/debian/tmp/usr/share/kmail2/pics/mail-deleted.png
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/128x128/apps/kmail.png
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/16x16/apps/kmail.png
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/22x22/apps/kmail.png
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/32x32/apps/kmail.png
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/48x48/apps/kmail.png
> -- Installing: 
> /<>/debian/tmp/usr/share/icons/hicolor/64x64/apps/kmail.png
> -- Installing: 
> /<>/debian/tmp/usr/share/kservices5/kcm_kpimidentities.desktop
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_kpimidentities.so
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/kontact_kmailplugin.so
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_kmailsummary.so
> -- Installing: 
> /<>/debian/tmp/usr/share/kservices5/kontact/kmailplugin.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/kservices5/kcmkmailsummary.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/kontact/ksettingsdialog/km

Bug#835737: gcr: FTBFS: Tests failures

2016-08-28 Thread Lucas Nussbaum
Source: gcr
Version: 3.20.0-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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):
> # Gcr-DEBUG: caller vanished for callback /org/gnome/keyring/Prompt/p20@:1.5
> # Gcr-DEBUG: stopping prompting for operation 
> /org/gnome/keyring/Prompt/p20@:1.5
> # Gcr-DEBUG: cancelling active prompting operation for 
> /org/gnome/keyring/Prompt/p20@:1.5
> # Gcr-DEBUG: prompter name owner has vanished: :1.20
> # Gcr-DEBUG: prompter name owner has vanished: :1.20
> # Gcr-DEBUG: closing prompt
> # Gcr-DEBUG: closing prompt
> # Gcr-DEBUG: closing the prompt
> # Gcr-DEBUG: stopping prompting for operation 
> /org/gnome/keyring/Prompt/p20@:1.5
> # Gcr-DEBUG: couldn't find the callback for prompting operation 
> /org/gnome/keyring/Prompt/p20@:1.5
> # Gcr-DEBUG: caller vanished for callback /org/gnome/keyring/Prompt/p21@:1.5
> # Gcr-DEBUG: stopping prompting for operation 
> /org/gnome/keyring/Prompt/p21@:1.5
> # Gcr-DEBUG: unregistering prompter
> ok 18 /gcr/system-prompt/watch-cancels
> 
> debian/rules:24: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/08/28/gcr_3.20.0-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#835734: kido: FTBFS: FCLCollisionNode.cpp:354:5: error: 'boost' has not been declared

2016-08-28 Thread Lucas Nussbaum
Source: kido
Version: 0.1.0+dfsg-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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):
> cd /<>/kido-0.1.0+dfsg/build/kido && /usr/bin/c++   
> -DBOOST_TEST_DYN_LINK -DHAVE_BULLET_COLLISION -Dkido_EXPORTS 
> -I/<>/kido-0.1.0+dfsg -isystem /usr/include/eigen3 -isystem 
> /usr/include/bullet -I/<>/kido-0.1.0+dfsg/build  -Wall -msse2 -fPIC 
> -std=c++11 -g -O2 -fdebug-prefix-map=/<>/kido-0.1.0+dfsg=. -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fPIC   -I/usr/include/bullet -o 
> CMakeFiles/kido.dir/collision/fcl/FCLCollisionNode.cpp.o -c 
> /<>/kido-0.1.0+dfsg/kido/collision/fcl/FCLCollisionNode.cpp
> /<>/kido-0.1.0+dfsg/kido/collision/fcl/FCLCollisionNode.cpp: In 
> constructor 
> 'kido::collision::FCLCollisionNode::FCLCollisionNode(kido::dynamics::BodyNode*)':
> /<>/kido-0.1.0+dfsg/kido/collision/fcl/FCLCollisionNode.cpp:354:5: 
> error: 'boost' has not been declared
>  boost::shared_ptr fclCollGeom;
>  ^
> /<>/kido-0.1.0+dfsg/kido/collision/fcl/FCLCollisionNode.cpp:354:45: 
> error: expected primary-expression before '>' token
>  boost::shared_ptr fclCollGeom;
>  ^
> /<>/kido-0.1.0+dfsg/kido/collision/fcl/FCLCollisionNode.cpp:354:47: 
> error: 'fclCollGeom' was not declared in this scope
>  boost::shared_ptr fclCollGeom;
>^~~
> kido/CMakeFiles/kido.dir/build.make:1937: recipe for target 
> 'kido/CMakeFiles/kido.dir/collision/fcl/FCLCollisionNode.cpp.o' failed
> make[4]: *** [kido/CMakeFiles/kido.dir/collision/fcl/FCLCollisionNode.cpp.o] 
> Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/08/28/kido_0.1.0+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#835740: clustalo: FTBFS: util-C.h:54:26: error: 'float log2(float)' conflicts with a previous declaration

2016-08-28 Thread Lucas Nussbaum
Source: clustalo
Version: 1.2.2-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
> -I../../src   -Wdate-time -D_FORTIFY_SOURCE=2 -fno-strict-aliasing -DCLUSTALO 
> -DCLUSTALO_NOFILE -DDEFAULT_FILTER=90 -fopenmp  -O3  -g -O2 
> -fdebug-prefix-map=/<>=. -fPIE -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o hhalign.lo hhalign.cpp
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../src -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fno-strict-aliasing -DCLUSTALO -DCLUSTALO_NOFILE 
> -DDEFAULT_FILTER=90 -fopenmp -O3 -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -c hhalign.cpp  
> -fPIC -DPIC -o .libs/hhalign.o
> In file included from hhalign.cpp:56:0:
> util-C.h: In function 'float log2(float)':
> util-C.h:54:26: error: 'float log2(float)' conflicts with a previous 
> declaration
>  inline float log2(float x)  {return (x<=0? 
> (float)(-10):1.442695041*log(x));}
>   ^
> In file included from /usr/include/c++/6/math.h:36:0,
>  from hhalign.cpp:39:
> /usr/include/c++/6/cmath:1542:3: note: previous declaration 'constexpr float 
> std::log2(float)'
>log2(float __x)
>^~~~
> In file included from hhalign.cpp:56:0:
> util-C.h: In function 'float log10(float)':
> util-C.h:55:27: error: 'float log10(float)' conflicts with a previous 
> declaration
>  inline float log10(float x) {return (x<=0? 
> (float)(-10):0.434294481*log(x));}
>^
> In file included from /usr/include/c++/6/math.h:36:0,
>  from hhalign.cpp:39:
> /usr/include/c++/6/cmath:380:3: note: previous declaration 'constexpr float 
> std::log10(float)'
>log10(float __x)
>^
> In file included from hhalign.cpp:56:0:
> util-C.h: In function 'char* sprintg(float, int)':
> util-C.h:246:35: error: call of overloaded 'log10(float)' is ambiguous
>float log10val = log10(fabs(val));
>^
> In file included from /usr/include/features.h:364:0,
>  from 
> /usr/include/x86_64-linux-gnu/c++/6/bits/os_defines.h:39,
>  from 
> /usr/include/x86_64-linux-gnu/c++/6/bits/c++config.h:495,
>  from /usr/include/c++/6/iostream:38,
>  from hhalign.cpp:34:
> /usr/include/x86_64-linux-gnu/bits/mathcalls.h:112:1: note: candidate: double 
> log10(double)
>  __MATHCALL (log10,, (_Mdouble_ __x));
>  ^
> In file included from /usr/include/c++/6/math.h:36:0,
>  from hhalign.cpp:39:
> /usr/include/c++/6/cmath:384:3: note: candidate: constexpr long double 
> std::log10(long double)
>log10(long double __x)
>^
> /usr/include/c++/6/cmath:380:3: note: candidate: constexpr float 
> std::log10(float)
>log10(float __x)
>^
> In file included from hhalign.cpp:56:0:
> util-C.h:55:14: note: candidate: float log10(float)
>  inline float log10(float x) {return (x<=0? 
> (float)(-10):0.434294481*log(x));}
>   ^
> In file included from hhalign.cpp:62:0:
> hhutil-C.h: In function 'void ReadDefaultsFile(int&, char**)':
> hhutil-C.h:516:53: warning: non-constant array new length must be specified 
> without parentheses around the type-id [-Wvla]
>  argv_conf[argc_conf]=new(char[strlen(c_first)+1]);
>  ^
> hhutil-C.h:521:56: warning: non-constant array new length must be specified 
> without parentheses around the type-id [-Wvla]
> argv_conf[argc_conf]=new(char[strlen(c_first)+1]);
> ^
> In file included from hhalign.cpp:63:0:
> hhmatrices-C.h: In function 'void SetSubstitutionMatrix()':
> hhmatrices-C.h:433:35: error: call of overloaded 'log2(float)' is ambiguous
>S[a][b] = log2(R[a][b]/pb[a]); // S[a][b] = log2(P(a,b)/P(a)/P(b))
>^
> In file included from /usr/include/features.h:364:0,
>  from 
> /usr/include/x86_64-linux-gnu/c++/6/bits/os_defines.h:39,
>  from 
> /usr/include/x86_64-linux-gnu/c++/6/bits/c++config.h:495,
>  from /usr/include/c++/6/iostream:38,
>  from hhalign.cpp:34:
> /usr/include/x86_64-linux-gnu/bits/mathcalls.h:144:1: note: candidate: double 
> log2(double)
>  __MATH

Bug#835741: prometheus: FTBFS: Tests failures

2016-08-28 Thread Lucas Nussbaum
Source: prometheus
Version: 1.0.1+ds-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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):
> === RUN   TestRespondSuccess
> --- PASS: TestRespondSuccess (0.00s)
> === RUN   TestRespondError
> --- PASS: TestRespondError (0.00s)
> === RUN   TestParseTime
> --- PASS: TestParseTime (0.00s)
> === RUN   TestParseDuration
> --- PASS: TestParseDuration (0.00s)
> === RUN   TestOptionsMethod
> --- PASS: TestOptionsMethod (0.00s)
> PASS
> okgithub.com/prometheus/prometheus/web/api/v1 0.027s
> ? github.com/prometheus/prometheus/web/ui [no test files]
> dh_auto_test: go test -v -p 1 github.com/prometheus/prometheus/cmd/prometheus 
> github.com/prometheus/prometheus/cmd/promtool 
> github.com/prometheus/prometheus/config 
> github.com/prometheus/prometheus/notifier 
> github.com/prometheus/prometheus/promql 
> github.com/prometheus/prometheus/retrieval 
> github.com/prometheus/prometheus/retrieval/discovery 
> github.com/prometheus/prometheus/retrieval/discovery/consul 
> github.com/prometheus/prometheus/retrieval/discovery/dns 
> github.com/prometheus/prometheus/retrieval/discovery/kubernetes 
> github.com/prometheus/prometheus/retrieval/discovery/marathon 
> github.com/prometheus/prometheus/rules 
> github.com/prometheus/prometheus/storage 
> github.com/prometheus/prometheus/storage/local 
> github.com/prometheus/prometheus/storage/local/codable 
> github.com/prometheus/prometheus/storage/local/index 
> github.com/prometheus/prometheus/storage/local/storagetool 
> github.com/prometheus/prometheus/storage/metric 
> github.com/prometheus/prometheus/storage/remote 
> github.com/prometheus/prometheus/storage/remote/graphite 
> github.com/prometheus/prometheus/storage/remote/influxdb 
> github.com/prometheus/prometheus/storage/remote/opentsdb 
> github.com/prometheus/prometheus/template 
> github.com/prometheus/prometheus/util/cli 
> github.com/prometheus/prometheus/util/flock 
> github.com/prometheus/prometheus/util/httputil 
> github.com/prometheus/prometheus/util/stats 
> github.com/prometheus/prometheus/util/strutil 
> github.com/prometheus/prometheus/util/testutil 
> github.com/prometheus/prometheus/util/treecache 
> github.com/prometheus/prometheus/vendor/github.com/influxdb/influxdb/client 
> github.com/prometheus/prometheus/vendor/github.com/influxdb/influxdb/tsdb 
> github.com/prometheus/prometheus/web 
> github.com/prometheus/prometheus/web/api/v1 
> github.com/prometheus/prometheus/web/ui returned exit code 1
>   cd /<>/prometheus-1.0.1+ds
> debian/rules:67: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/08/28/prometheus_1.0.1+ds-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#835747: ivtools: FTBFS: src/Attribute/attrlist.cc:514:35: error: call of overloaded 'abs(unsigned int)' is ambiguous

2016-08-28 Thread Lucas Nussbaum
Source: ivtools
Version: 1.2.11a1-7
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I.  
> -Dcplusplus_2_1 -I./src -I./src/include -I./src/include/ivstd -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wno-write-strings -Wno-deprecated -g -O2 
> -fdebug-prefix-map=/<>=. -fPIE -fstack-protector-strong -Wall 
> -Wno-narrowing -c -o src/Attribute/libAttribute_la-attrlist.lo `test -f 
> 'src/Attribute/attrlist.cc' || echo './'`src/Attribute/attrlist.cc
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -Dcplusplus_2_1 -I./src 
> -I./src/include -I./src/include/ivstd -Wdate-time -D_FORTIFY_SOURCE=2 
> -Wno-write-strings -Wno-deprecated -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wall 
> -Wno-narrowing -c src/Attribute/attrlist.cc  -fPIC -DPIC -o 
> src/Attribute/.libs/libAttribute_la-attrlist.o
> src/Attribute/attrlist.cc: In member function 'AttributeValue* 
> AttributeValueList::Get(unsigned int)':
> src/Attribute/attrlist.cc:512:15: warning: comparison between signed and 
> unsigned integer expressions [-Wsign-compare]
>if (Number()<=index) return nil;
>^~~
> src/Attribute/attrlist.cc:514:35: error: call of overloaded 'abs(unsigned 
> int)' is ambiguous
>int delta = abs(index-_prevget_i);
>^
> In file included from /usr/include/c++/6/cstdlib:75:0,
>  from /usr/include/c++/6/stdlib.h:36,
>  from ./src/include/ivstd/stdlib.h:5,
>  from ./src/ComUtil/comutil.arg:1,
>  from ./src/ComUtil/comutil.h:142,
>  from ./src/Attribute/_comutil.h:4,
>  from ./src/Attribute/classid.h:3,
>  from ./src/Attribute/attribute.h:27,
>  from src/Attribute/attrlist.cc:31:
> /usr/include/stdlib.h:774:12: note: candidate: int abs(int)
>  extern int abs (int __x) __THROW __attribute__ ((__const__)) __wur;
> ^~~
> In file included from /usr/include/c++/6/stdlib.h:36:0,
>  from ./src/include/ivstd/stdlib.h:5,
>  from ./src/ComUtil/comutil.arg:1,
>  from ./src/ComUtil/comutil.h:142,
>  from ./src/Attribute/_comutil.h:4,
>  from ./src/Attribute/classid.h:3,
>  from ./src/Attribute/attribute.h:27,
>  from src/Attribute/attrlist.cc:31:
> /usr/include/c++/6/cstdlib:185:3: note: candidate: __int128 std::abs(__int128)
>abs(__GLIBCXX_TYPE_INT_N_0 __x) { return __x >= 0 ? __x : -__x; }
>^~~
> /usr/include/c++/6/cstdlib:180:3: note: candidate: long long int 
> std::abs(long long int)
>abs(long long __x) { return __builtin_llabs (__x); }
>^~~
> /usr/include/c++/6/cstdlib:172:3: note: candidate: long int std::abs(long int)
>abs(long __i) { return __builtin_labs(__i); }
>^~~
> src/Attribute/attrlist.cc:517:18: warning: comparison between signed and 
> unsigned integer expressions [-Wsign-compare]
>  if(_prevget_i>index) {
> ~~^~
> src/Attribute/attrlist.cc:523:16: warning: comparison between signed and 
> unsigned integer expressions [-Wsign-compare]
>  if(Number()<=index*2) {
> ^
> src/Attribute/attrlist.cc:525:24: warning: comparison between signed and 
> unsigned integer expressions [-Wsign-compare]
>  for (int i=0; i~^
> src/Attribute/attrlist.cc:528:24: warning: comparison between signed and 
> unsigned integer expressions [-Wsign-compare]
>  for (int i=0; i~^~
> src/Attribute/attrlist.cc: In member function 'AttributeValue* 
> AttributeValueList::Set(unsigned int, AttributeValue*)':
> src/Attribute/attrlist.cc:537:15: warning: comparison between signed and 
> unsigned integer expressions [-Wsign-compare]
>if (Number()<=index) {
>^~~
> src/Attribute/attrlist.cc:548:20: warning: comparison between signed and 
> unsigned integer expressions [-Wsign-compare]
>  for (int i=0; i~^~
> Makefile:4773: recipe for target 'src/Attribute/libAttribute_la-attrlist.lo' 
> failed
> make[3]: *** [src/Attribute/libAttribute_la-attrlist.lo] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/08/28/ivtools_1.2.11a1-7_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.



  1   2   3   4   5   >