Bug#826728: percona-toolkit: (CVE-2014-2029) scripts call back home and leak information

[Dario Minnucci]

Hi guys,

On 11/04/16 14:38, Guillem Jover wrote:
> ... 
> This is the relevant strace part for percona-toolkit 2.2.18-1:
> 
> ,---
> connect(3, {sa_family=AF_INET, sin_port=htons(443), 
> sin_addr=inet_addr("74.121.199.234")}, 16) = 0
> `---
> 
> Where 74.121.199.234 is www.percona.com.
> 

I've just discussed this issue with upstream just a minute ago and it seems 
there is a simple
solution for it...

There is a global configuration file to affect every percona-toolkit package 
tools.
(See: https://www.percona.com/doc/percona-toolkit/2.2/configuration_files.html)

The workaround consists in create (or modify) the file 
'/etc/percona-toolkit/percona-toolkit.conf'
an add 'noversion-check' to it.


---%<-
cat << EOF >> /etc/percona-toolkit/percona-toolkit.conf
noversion-check
EOF
---%<-


This global configuration file (/etc/percona-toolkit/percona-toolkit.conf) 
should be read by every
tool in percona-toolkit package disabling the 'call home' functionality.

Can you try this solution and report results?

-- 
 Dario Minnucci 
 Phone: +34 902021030 | Fax: +34 902024417
 Key fingerprint = BAA1 7AAF B21D 6567 D457  D67D A82F BB83 F3D5 7033




signature.asc
Description: OpenPGP digital signature

Bug#843061: radeon/hawaii_k_smc.bin fails to load with 4.8 kernel

[Ferdinand Pöll]

I also have this problem, but with an AMD Radeon R9 270X (Curacao XT, which is 
a Pitcairn refresh). It also happens with any of the 4.9 kernels from 
experimental, and doesn‘t happen on the newest 4.7. I can still ssh on the 
affected PC. 

My journalctl shows me the following messages: 
Nov 18 16:52:57 fp-pc kernel: [drm] radeon: 4096M of VRAM memory ready
Nov 18 16:52:57 fp-pc kernel: [drm] radeon: 2048M of GTT memory ready.
Nov 18 16:52:57 fp-pc kernel: [drm] Loading pitcairn Microcode
Nov 18 16:52:57 fp-pc kernel: radeon :01:00.0: firmware: direct-loading 
firmware radeon/pitcairn_pfp.bin
Nov 18 16:52:57 fp-pc kernel: radeon :01:00.0: firmware: direct-loading 
firmware radeon/pitcairn_me.bin
Nov 18 16:52:57 fp-pc kernel: radeon :01:00.0: firmware: direct-loading 
firmware radeon/pitcairn_ce.bin
Nov 18 16:52:57 fp-pc kernel: radeon :01:00.0: firmware: direct-loading 
firmware radeon/pitcairn_rlc.bin
Nov 18 16:52:57 fp-pc kernel: radeon :01:00.0: firmware: direct-loading 
firmware radeon/pitcairn_mc.bin
Nov 18 16:52:57 fp-pc kernel: radeon :01:00.0: firmware: failed to load 
radeon/pitcairn_k_smc.bin (-2)
Nov 18 16:52:57 fp-pc kernel: radeon :01:00.0: Direct firmware load for 
radeon/pitcairn_k_smc.bin failed with error -2
Nov 18 16:52:57 fp-pc kernel: radeon :01:00.0: firmware: direct-loading 
firmware radeon/PITCAIRN_smc.bin
Nov 18 16:52:57 fp-pc kernel: si_fw: mixing new and old firmware!
Nov 18 16:52:57 fp-pc kernel: [drm:si_init [radeon]] *ERROR* Failed to load 
firmware!
Nov 18 16:52:57 fp-pc kernel: radeon :01:00.0: Fatal error during GPU init
Nov 18 16:52:57 fp-pc kernel: [drm] radeon: finishing device.

The last message I see on the connected screen is: 
kernel: fb: switching to radeondrmfb from simple

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

Bug#844748: openocd: Please package upstream snapshot with jtagspi

[Stefano Rivera]

Package: openocd
Version: 0.9.0-1+b1
Severity: normal

Is there any chance of getting an upstream snapshot that includes the
jtagspi driver?

It was added in d25355473da9a925a696183a9947aac292cd2f60 upstream (Jul 2015).

We (DebConf video team) need it to flash our HDMI capture boards. So,
having a package (even in experimental) would be useful.

SR

Bug#844242: RFS: terminology/0.9.1-0.1 [RC] [NMU]

[Gianfranco Costamagna]

control: reopen -1


>   [ Ross Vandegrift ]

>   * Non-maintainer upload.

Hi Ross, can you please fix and answer if  you want to maintain or not
the package?

thanks,

G.

Bug#841183: dvbcut: mplayer2 has gone away

[James Cowgill]

On 18/11/16 14:28, Bernhard Übelacker wrote:
> Hello James,
> sorry for the late reply.
> 
> I prepared a new version removing mplayer2 and opened a RFS in [1].

Why did you remove mpv?

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#827867: puppet-agent package is not really necessary and conflicts with the upstream package by the same name

[Stig Sandbeck Mathisen]

Michael Moll  writes:

> What's the status of this bug? A quick fix would be to rename the
> puppet-agent package to puppet-client or similar. As the stretch
> release is nearing and PuppetLabs is pushing users to move to their
> Puppet 4 packages, something should be done. ;)

The package is still to be removed.  I'm a tad bit short of free time to
take care of it, so help would be welcome, if anyone else has time to do
this bug.

-- 
Stig Sandbeck Mathisen
https://fnord.no/

Bug#768495: Bug looks RC and is also in jessie

[Jochen Sprickerhof]

Control: fixed -1 2.14-1.1
Control: merge -1 764451

Based on the information in the bug report, these are the same and the
fix is in jessie already.


signature.asc
Description: PGP signature

Bug#768495: Bug looks RC and is also in jessie

[Jochen Sprickerhof]

Control: severity -1 grave
Control: merge -1 764451

* Adrian Bunk  [2016-11-18 21:24]:
> I assumed it was not fixed in 2.14-1.1 due to the fact that it was 
> closed in the 2.16-1 changelog entry.

No, it was actually fixed in 2.14-1.1 by a patch, but I missed that when
going through the reports today and as the report was stating that it
was fixed (by the very same patch) by upstream in 2.15 I erroneously
closed it in 2.16-1.


signature.asc
Description: PGP signature

Bug#844764: borgbackup: Please update package description

[Matteo Cypriani]

Source: borgbackup
Version: 1.0.8-1
Severity: minor

Hi there,

The descriptions of both packages borgbackup and borgbackup-doc state:
“It was forked from the attic backup program which is also packaged in
Debian.”

attic was removed [1] from Debian in September, so I believe the
reference to the attic Debian package should be removed as well.

[1] https://packages.qa.debian.org/a/attic/news/20160915T130956Z.html

Cheers,
  Matteo

Bug#844339: [PATCH v3 2/4] libvirt-daemon-system.{config,templates,postinst,NEWS}: warn if allocated uid/gid is taken

[Mauricio Faria de Oliveira]

Guido,

On 11/18/2016 04:24 PM, Guido Günther wrote:

I'm failing to spot how you make sure you only run on new
installations. [snip]


Oops. You're right. Not sure where my head was at. It passed
tests due to debconf again; sorry.

I thought of not doing a whole-file guard, but an early exit,
to keep it short.  Is this snippet OK with you?

# Only perform this check/warning on new installations
# (precisely: when not creating neither user nor group).
if getent passwd libvirt-qemu >/dev/null \
&& getent group  libvirt-qemu >/dev/null; then
exit 0
fi


> +# Check if allocated UID/GID are assigned to a different user/group.
> +UID_TO_NAME="$(getent passwd $LIBVIRT_QEMU_UID | cut -d: -f1)"
> +GID_TO_NAME="$(getent group  $LIBVIRT_QEMU_GID | cut -d: -f1)"
> +
> +if ( [ -n "$UID_TO_NAME" ] && [ "$UID_TO_NAME" != 'libvirt-qemu' ] ) \
> +|| ( [ -n "$GID_TO_NAME" ] && [ "$GID_TO_NAME" != 'libvirt-qemu' ] )
> \

I think this can be shortened to:

if [ "$UID_TO_NAME" != 'libvirt-qemu' ] || [ "$GID_TO_NAME" != 'libvirt-qemu' 
]; then


Hm, but if the uid/gid is not taken, then getent output is null,
which is != 'libvirt-qemu', so the warning shows up incorrectly.

If you're OK w/ my suggestions, would you apply the guard snippet,
or would prefer a v4 of this particular patch submitted?

Thanks,

--
Mauricio Faria de Oliveira
IBM Linux Technology Center

Bug#842040: Please add https support

[Martin Michlmayr]

* Philipp Kern  [2016-11-18 17:19]:
> > Thanks for the CC.  I just added wget-udeb and it adds 345 KB,
> > which breaks the orion5x-qnap image.  However, this image is really
> > quite a special case and I don't want to block https support because
> > of it.  I can always exclude wget-udeb from this particular image.
> 
> So how do we move forward here? Exclude wget-udeb from the orion5x-qnap
> image and otherwise include it by default?

That should work.

-- 
Martin Michlmayr
http://www.cyrius.com/

Bug#844339: [PATCH v3 2/4] libvirt-daemon-system.{config,templates,postinst,NEWS}: warn if allocated uid/gid is taken

[Guido Günther]

Hi Mauricio,
thanks! See my two inline comments below, we're nearing completion!

On Fri, Nov 18, 2016 at 03:07:08PM -0200, Mauricio Faria de Oliveira wrote:
> If the uid/gid that is allocated for libvirt-qemu (64055)
> is already in use by another user/group, stop/ask user if
> it is OK to continue (e.g., no plans with guest migration
> over NFS) or abort to go fix the problem.
> 
> This warning is only displayed on new installations.  The
> default value is 'yes'/continue/do not abort, thus not to
> disrupt automated installations.

I'm failing to spot how you make sure you only run on new
installations. Shouldn't a:

if ! getent passwd libvirt-qemu || ! getent group libvirt-qemu; then
...
fi

gurad the whole libvirt-daemon-system.config to detect that we've
already done our job (correctly on not) in a previous installation?

> 
> On existing installations, no warning is displayed - just
> a NEWS file is provided.
> 
> Signed-off-by: Mauricio Faria de Oliveira 
> ---
>  debian/libvirt-daemon-system.NEWS  | 22 ++
>  debian/libvirt-daemon-system.config| 26 ++
>  debian/libvirt-daemon-system.postinst  |  3 +++
>  debian/libvirt-daemon-system.templates | 18 ++
>  4 files changed, 69 insertions(+)
>  create mode 100755 debian/libvirt-daemon-system.config
>  create mode 100644 debian/libvirt-daemon-system.templates
> 
> diff --git a/debian/libvirt-daemon-system.NEWS 
> b/debian/libvirt-daemon-system.NEWS
> index 977abdb..94367e5 100644
> --- a/debian/libvirt-daemon-system.NEWS
> +++ b/debian/libvirt-daemon-system.NEWS
> @@ -1,3 +1,25 @@
> +libvirt (2.4.0-2uidgid3) UNRELEASED; urgency=medium
> +
> +  libvirt-daemon-system now uses the allocated uid and gid 64055
> +  for the libvirt-qemu user and group on new installations, when
> +  the uid/gid is available (otherwise a debconf warning is shown).
> +
> +  On existing installations, which have different uid/gid values
> +  assigned, the recommended procedure is to reassign the uid/gid
> +  (might require considerations for ownership/permission changes).
> +  No debconf warning is shown in this case; only this NEWS entry.
> +
> +  This change is in order to prevent I/O errors during migration
> +  of guests with disk image files shared over NFS, caused by the
> +  different uid/gid ownership between the source and destination
> +  host systems, which leads to access/permission errors with NFS.
> +
> +  If guest migration over NFS is not a requirement in the system,
> +  there should not be any impact to the guests for not using the
> +  allocated uid/gid.
> +
> + -- Mauricio Faria de Oliveira   Thu, 18 Nov 
> 2016 13:56:38 -0200
> +
>  libvirt (1.2.9~rc1-1) experimental; urgency=medium
>  
>libvirtd now uses PolicyKit instead of unix socket domain permissions for 
> r/w
> diff --git a/debian/libvirt-daemon-system.config 
> b/debian/libvirt-daemon-system.config
> new file mode 100755
> index 000..caf0ac2
> --- /dev/null
> +++ b/debian/libvirt-daemon-system.config
> @@ -0,0 +1,26 @@
> +#!/bin/sh -e
> +
> +# Source debconf library.
> +. /usr/share/debconf/confmodule
> +
> +# Allocated UID and GID for libvirt-qemu
> +LIBVIRT_QEMU_UID=64055
> +LIBVIRT_QEMU_GID=64055
> +
> +# Check if allocated UID/GID are assigned to a different user/group.
> +UID_TO_NAME="$(getent passwd $LIBVIRT_QEMU_UID | cut -d: -f1)"
> +GID_TO_NAME="$(getent group  $LIBVIRT_QEMU_GID | cut -d: -f1)"
> +
> +if ( [ -n "$UID_TO_NAME" ] && [ "$UID_TO_NAME" != 'libvirt-qemu' ] ) \
> +|| ( [ -n "$GID_TO_NAME" ] && [ "$GID_TO_NAME" != 'libvirt-qemu' ] )
> \

I think this can be shortened to:

if [ "$UID_TO_NAME" != 'libvirt-qemu' ] || [ "$GID_TO_NAME" != 'libvirt-qemu' 
]; then

> +then
> + # Ask if the user would like to continue or abort installation.
> + db_input high libvirt-daemon-system/id_warning || true
> + db_go
> + db_get libvirt-daemon-system/id_warning
> + if [ "$RET" = "false" ]; then
> + exit 1
> + fi
> +fi
> +
> +exit 0
> diff --git a/debian/libvirt-daemon-system.postinst 
> b/debian/libvirt-daemon-system.postinst
> index 99e9fec..f36b806 100644
> --- a/debian/libvirt-daemon-system.postinst
> +++ b/debian/libvirt-daemon-system.postinst
> @@ -17,6 +17,9 @@ set -e
>  # for details, see http://www.debian.org/doc/debian-policy/ or
>  # the debian-policy package
>  
> +# Source debconf library.
> +. /usr/share/debconf/confmodule
> +
>  add_users_groups()
>  {
>  if ! getent group libvirt >/dev/null; then
> diff --git a/debian/libvirt-daemon-system.templates 
> b/debian/libvirt-daemon-system.templates
> new file mode 100644
> index 000..7e1594b
> --- /dev/null
> +++ b/debian/libvirt-daemon-system.templates
> @@ -0,0 +1,18 @@
> +Template: libvirt-daemon-system/id_warning
> +Type: boolean
> +Default: true
> +Description: Continue with incorrect libvirt-qemu user/group ID(s)?
> +  The user/group ID 

Bug#843173: closed by Fabian Greffrath <fab...@debian.org> (Bug#843173: fixed in faad2 2.8.0~cvs20161113-1)

[Stefan Pöschel]

Thank you for fixing this!

Bug#844759: firefox: gtk3 renders large multiselect boxes rather unusable due to lack of up/down buttons

[Jon]

Package: firefox
Version: 50.0-1
Severity: normal

Dear Maintainer,

i dunno if this is a theme problem (I'm running the default firefox and
default gtk3 themes) but with the GTK3 changeover there are no longer
up/down buttons on scrollbars.

This very negatively impacts the usability of large multiselect boxes on
websites like mozilla's own bug tracker:

http://i.imgur.com/EltbNiI.png (for reference, this is what it looks
like for me)

https://bugzilla.mozilla.org/query.cgi?query_format=advanced
(Note bugzilla is an example, im well aware that in this specific case I
can select a Product entry first and the contents of Components is
narrowed down.)

Without up/down arrows on the scrollbars its very difficult to select
more than one item from large select boxes like that one. Yes, you can
scroll to the vaguely correct spot, ctrl+click to highlight a new
option, ctrl+click again to unhighlight it and then use ctrl+up/ctrl+down,
but thats not very user friendly or obvious at all. Using
ctrl+up/ctrl+down alone to navigate a select box of that size is not
reasonable.

(Ctrl+PageUp/Ctrl+PageDown only work if you have a single tab open,
otherwise it switches tabs)

Again, I do not have any custom GTK3 theme or firefox theme running here.
(Although I'll note that I do not have GNOME itself installed either,
which may have an impact on the defaults) I did try a few other firefox
themes, but it was quickly apparent that they weren't changing the
scrollbar style at all.

-- Package-specific info:


-- Addons package information

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

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

Versions of packages firefox depends on:
ii  debianutils   4.8.1
ii  fontconfig2.11.0-6.7
ii  libasound21.1.2-1
ii  libatk1.0-0   2.22.0-1
ii  libc6 2.24-5
ii  libcairo-gobject2 1.14.6-1.1
ii  libcairo2 1.14.6-1.1
ii  libdbus-1-3   1.10.12-1
ii  libdbus-glib-1-2  0.108-1
ii  libevent-2.0-52.0.21-stable-2.1
ii  libffi6   3.2.1-6
ii  libfontconfig12.11.0-6.7
ii  libfreetype6  2.6.3-3+b1
ii  libgcc1   1:6.2.0-13
ii  libgdk-pixbuf2.0-02.36.0-1
ii  libglib2.0-0  2.50.2-1
ii  libgtk-3-03.22.3-2
ii  libgtk2.0-0   2.24.31-1
ii  libhunspell-1.4-0 1.4.1-2+b1
ii  libnspr4  2:4.12-6
ii  libnss3   2:3.26.2-1
ii  libpango-1.0-01.40.3-3
ii  libsqlite3-0  3.15.1-1
ii  libstartup-notification0  0.12-4
ii  libstdc++66.2.0-13
ii  libvpx4   1.6.0-3
ii  libx11-6  2:1.6.3-1
ii  libx11-xcb1   2:1.6.3-1
ii  libxcb-shm0   1.12-1
ii  libxcb1   1.12-1
ii  libxcomposite11:0.4.4-1
ii  libxdamage1   1:1.1.4-2+b1
ii  libxext6  2:1.3.3-1
ii  libxfixes31:5.0.2-1
ii  libxrender1   1:0.9.9-2
ii  libxt61:1.1.5-1
ii  procps2:3.3.12-2
ii  zlib1g1:1.2.8.dfsg-2+b3

firefox recommends no packages.

Versions of packages firefox suggests:
pn  fonts-lmodern  
pn  fonts-stix | otf-stix  
pn  libcanberra0   
pn  libgnomeui-0   
ii  libgssapi-krb5-2   1.15~beta1-1
pn  mozplugger 

-- no debconf information

Bug#840211: perlunicook man page does not display utf8 char beyond ascii

[Dominique Dumont]

On Friday, 18 November 2016 10:54:36 CET Russ Allbery wrote:
>> Considering [1], we may want to patch Debian's perl to produce utf8 man
> > pages even if upstream cannot, due to portability constraints.
> 
> That's not strictly true, which is the reason why I haven't already
> switched Linux systems over to generating UTF-8 by default.  This means
> that you cannot create man pages with pod2man on a Linux system and have
> them work on any other system, something that pod2man has, up until this
> point, always guaranteed.

Looks like I was not clear. I was thinking of patching perl build system to 
generate  perl* man page (perlrun perlunicook...) as utf8 man page. 

That should not impact the generation of other man pages (i.e. not in Debian 
perl package) using pod2man.

HTH
-- 
 https://github.com/dod38fr/   -o- http://search.cpan.org/~ddumont/
http://ddumont.wordpress.com/  -o-   irc: dod at irc.debian.org

Bug#839539: svn2git: git-svn should be a dependency for svn2git

[Sascha Girrulat]

updated and fixed in vcs.

Upload is comming soon.

Regards
Sascha


[1] https://anonscm.debian.org/git/users/sagiru-guest/svn2git.git
[2] https://mentors.debian.net/package/svn2git



signature.asc
Description: OpenPGP digital signature

Bug#844765: RFS: gitless/0.8.4-1 -- new package

[Peter Pentchev]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for the initial upload of my package
"gitless" - a version control system on top of Git.

* Package name: gitless
  Version : 0.8.4-1
  Upstream Author : Santiago Perez de Rosso 
* URL : http://gitless.com/
* License : GPL-2+
  Section : devel

It builds a single binary package that has been built with sbuild and
tested with Lintian and cme:

  gitless- version control system on top of Git

Unfortunately there have been some issues with uploading the Gitless
package to mentors.d.n (I'm in contact with the administrators), but you
can fetch it from my website:

  dget -x 
https://devel.ringlet.net/devel/gitless/debian/0.8.4-1/gitless_0.8.4-1.dsc

...or, alternatively, from a GitHub repository:

  git clone https://github.com/ppentchev/gitless.git -b debian
  cd gitless
  git describe # should output mentors/0.8.4-1-2
  git tag -v mentors/0.8.4-1-2
  pristine-tar checkout ../gitless_0.8.4.orig.tar.gz

More information about Gitless can be obtained from http://gitless.com/

Thanks in advance for your time, and keep up the great work!

G'luck,
Peter

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

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

Bug#844458: bootstrap-base: if debootstrap_script is unset, DEBOOTSTRAP_SCRIPT is set to a directory, breaking the install

[Philip Hands]

Philip Hands  writes:

...
> (but I still need to test it...)

Now that I've built d-i (having used the HEAD that includes the new
kernel version) it works:

  https://jenkins.debian.net/job/lvc_debian-miniiso/318/

That's a preseeded test.  I've also installed jessie with that, as a
manual install, and at least started a default stretch install (it's
gone past the pointof error...) so I think that indicates that it works

I didn't bother to test using the full path in 
base-installer/debootstrap_script.

Given that it works, I'll apply that patch to the master branch.

Cheers, Phil.
-- 
|)|  Philip Hands  [+44 (0)20 8530 9560]  HANDS.COM Ltd.
|-|  http://www.hands.com/http://ftp.uk.debian.org/
|(|  Hugo-Klemm-Strasse 34,   21075 Hamburg,GERMANY


signature.asc
Description: PGP signature

Bug#844760: fastqc: Please temporarily drop support for fast5 files

[Gilles Filippini]

Source: fastqc
Version: 0.11.5+dfsg-4
Severity: important
Tags: patch

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,

HDF5 1.10 is about to transition into unstable [1], and unfortunately a
FastQC build-dependency, libsis-jhdf5-java, doesn't support this new
release yet [2], and we have no information about its upstream schedule
wrt HDF5 1.10.

I've had a look at the FastQC code, and AFAIUI, libsis-jhdf5-java is
required only to support fast5 files from nanopore sequences.

Since these files can easily be converted to FastQ format using
poretools [3], I propose to temporarily drop fast5 support from FastQC
to avoid a removal from testing.

Please find attached a patch proposal to this end.

Thanks in advance,

_g.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842177#40
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842815
{3] https://bioinfoexpert.com/2016/06/15/minion-fast5-to-fastq/

-BEGIN PGP SIGNATURE-

iQEcBAEBCAAGBQJYL03KAAoJEO/obGx//s+D0uAH/3dDwjK+eAjV5lrCu7sa17rR
RFVYrJMhpnwwgH3q4cNHPvcHeyYZYwyC7WZMw++RWOIEDOlp04KeTkXNhW0/nlt+
FYlGwc1PjHnKUVVy3oyJBTeHnydHU0gP2qNkndvGtrxTjhsIT2toxU3gR+1Z86OI
iW7UAxmuhBoOF3rqYUb9pevRVQjOu8ikrG5ExS7Lg1Fk4TKu00IjaiqvppndoqPO
dsahyQkorSn+Rw0qQFxO4COBZVx5cMsFgIqa+QVvEhSw1Muw/x1S4m2NSfOsM9wQ
H2S3vIrbeDYuyI7ACZSfqHlOsuxVi8v6Y50kZqo0eGZM3km1z5r/cJHqalKt7hI=
=yCAp
-END PGP SIGNATURE-
diff --git a/debian/changelog b/debian/changelog
index aeba166..20d6f39 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,13 @@
+fastqc (0.11.5+dfsg-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * New patch drop-fast5.patch to temporarily drop support for fast5
+file format. This way we can drop the build-dependency on
+libsis-jhdf5-java which doesn't support HDF5 1.10 yet (#842815).
+fast5 files can easily be converted to fastq using poretools.
+
+ -- Gilles Filippini   Fri, 18 Nov 2016 19:03:15 +0100
+
 fastqc (0.11.5+dfsg-4) unstable; urgency=low
 
   * Team upload.
diff --git a/debian/control b/debian/control
index 7fa5f02..9cd7223 100644
--- a/debian/control
+++ b/debian/control
@@ -11,8 +11,7 @@ Build-Depends: debhelper (>= 9),
ant,
libhtsjdk-java,
libjbzip2-java,
-   libcommons-math3-java,
-   libsis-jhdf5-java
+   libcommons-math3-java
 Standards-Version: 3.9.8
 Vcs-Browser: https://anonscm.debian.org/cgit/debian-med/fastqc.git
 Vcs-Git: https://anonscm.debian.org/git/debian-med/fastqc.git
diff --git a/debian/patches/drop-fast5.patch b/debian/patches/drop-fast5.patch
new file mode 100644
index 000..f9a0cf6
--- /dev/null
+++ b/debian/patches/drop-fast5.patch
@@ -0,0 +1,151 @@
+Index: fastqc/fastqc
+===
+--- fastqc.orig/fastqc
 fastqc/fastqc
+@@ -74,7 +74,6 @@ my $quiet;
+ my $nogroup;
+ my $expgroup;
+ my $casava;
+-my $nano;
+ my $nofilter;
+ my $kmer_size;
+ my $temp_directory;
+@@ -91,7 +90,6 @@ my $result = GetOptions('version' => \$v
+ 		'threads=i' => \$threads,
+ 		'kmers=i' => \$kmer_size,
+ 		'casava' => \$casava,
+-		'nano' => \$nano,
+ 		'nofilter' => \$nofilter,
+ 		'contaminants=s' => \$contaminant,
+ 		'adapters=s' => \$adapter,
+@@ -183,10 +181,6 @@ if ($casava) {
+ 	push @java_args ,"-Dfastqc.casava=true";		
+ }
+ 
+-if ($nano) {
+-	push @java_args ,"-Dfastqc.nano=true";		
+-}
+-
+ 
+ if ($nofilter) {
+ 	push @java_args ,"-Dfastqc.nofilter=true";		
+@@ -320,11 +314,6 @@ DESCRIPTION
+ (including being gzipped and ending with .gz) otherwise they
+ won't be grouped together correctly.
+ 
+---nano  Files come from naopore sequences and are in fast5 format. In
+-this mode you can pass in directories to process and the program
+-will take in all fast5 files within those directories and produce
+-a single output file from the sequences found in all files.
+-
+ --nofilter  If running with --casava then don't remove read flagged by
+ casava as poor quality when performing the QC analysis.
+
+Index: fastqc/uk/ac/babraham/FastQC/Sequence/SequenceFactory.java
+===
+--- fastqc.orig/uk/ac/babraham/FastQC/Sequence/SequenceFactory.java
 fastqc/uk/ac/babraham/FastQC/Sequence/SequenceFactory.java
+@@ -99,9 +99,6 @@ public class SequenceFactory {
+ 			// We default to using all reads
+ 			return new BAMFile(file,false);
+ 		}
+-		else if (file.getName().toLowerCase().endsWith(".fast5")) {
+-			return new Fast5File(file);
+-		}
+ 		else {
+ 			return new FastQFile(config,file);
+ 		}
+Index: fastqc/uk/ac/babraham/FastQC/Sequence/Fast5File.java
+===
+--- 

Bug#844715: [Pkg-openssl-devel] Bug#844715: openssl: segfault in shlibloadtest (observed on x32) due to dlopen/dlclose/OPENSSL_atexit/OPENSSL_cleanup ordering

[Kurt Roeckx]

On Fri, Nov 18, 2016 at 12:59:57PM +0100, Thorsten Glaser wrote:
> Breakpoint 1, OPENSSL_atexit (handler=handler@entry=0xf6745c50 
> ) at crypto/init.c:604
> 604 {
> 
> There is our 0xf6745c50, which is ssl_library_stop… huh?

[...]
> 
> That’s .text of libssl.so.1.1!
> 
> So it appears that dynamically loaded libraries are dismantled,
> and OPENSSL_cleanup() is called too late. This might even be a
> bug on other architectures; I’m changing the bug title before
> submitting.

So that looks like this doesn't work:
/*
 * Deliberately leak a reference to the handler. This will force the
 * library/code containing the handler to remain loaded until we run the
 * atexit handler. If -znodelete has been used then this is
 * unneccessary.
 */
{
DSO *dso = NULL;

dso = DSO_dsobyaddr(handlersym.sym, DSO_FLAG_NO_UNLOAD_ON_FREE);
DSO_free(dso);
}


Kurt

Bug#835865: RFP: blocks -- deep learning framework build on the top of Theano

[Christoph Biedl]

Daniel Stender wrote...

> * Package name: blocks
>   Version : 0.2.0
>   Upstream Author : Université de Montréal, LISA lab/MILA 
> 
> * URL : https://github.com/mila-udem/blocks
> * License : Expat
>   Programming Lang: Python
>   Description : deep learning framework build on the top of Theano

Better late than never: There is a completely different project called
"blocks" as well, conversion tools for block devices[1], I might file
an ITP for this. So I'm asking you to consider a different and more
distinctive name, perhaps "theano-blocks". I would choose something
like blocks-conversion or blocks-tools then.

Cheers,
Christoph

[1] https://github.com/g2p/blocks


signature.asc
Description: Digital signature

Bug#841587: node-livescript must build-depend on livescript

[Adrian Bunk]

Control: retitle -1 node-livescript must build-depend on livescript

This is a compiler that seems to require itself for building,
adding livescript to the build dependencies fixes the build
for me.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#844692: sandbox not versioned

[Enrico Tassi]

Hello, looks like you use 'sandbox' as the identifier of the Lua
version.  Note that 5.1 and 5.2, for example, are different,
incompatible, languages.

Will Lua sandbox stay compatible with 5.1 only? Shouldn't we
call it sanbox5.1 or something like that? Also, is it a drop in
replacement for 5.1 (with extra features)?  Will there be Lua 
packages working only on sandbox (to motivate the "sanbox" label)?
E.g. is the new systemd related package needing sandbox?

Best
-- 
Enrico Tassi

Bug#844761: valadoc: Erroneously empty output with some constructs

[Colomban Wendling]

Package: valadoc
Version: 0.30.0~git20160518-1
Severity: important
Tags: patch upstream

Dear Maintainer,

Current valadoc version in testing and unstable fail to generate any
documentation with some perfectly valid input that used to work with
previous versions.

This is due to a change in upstream that started to use a buggy feature
of libgee-0.8.  See upstream report at
https://bugzilla.gnome.org/show_bug.cgi?id=774653 for more details.

This bug affects for example libgsecuredelete package, that FTBFS in
testing and unstable because of that issue.

The ideal fix would be in libgee, but it is non-trivial to fix properly
in its side, and I think the current valadoc breakage here warrants at
least a temporary fix.  The fix is fairly simple and harmless too, so
it shouldn't be too hard to make sure it doesn't cause any regressions.
See https://bugzilla.gnome.org/show_bug.cgi?id=774669 for the upstream
libgee bug report.

Regards,
Colomban

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

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

Versions of packages valadoc depends on:
ii  libc6   2.24-5
ii  libcdt5 2.38.0-16
ii  libcgraph6  2.38.0-16
ii  libgee-0.8-20.18.1-1
ii  libglib2.0-02.50.2-1
ii  libgvc6 2.38.0-16
ii  libvala-0.34-0  0.34.2-1
ii  libvaladoc3 0.30.0~git20160518-1

valadoc recommends no packages.

Versions of packages valadoc suggests:
ii  valac  0.34.2-1

-- no debconf information
>From 7505aff6d2621d57ffe547b3fccd2e59111e508e Mon Sep 17 00:00:00 2001
From: Colomban Wendling 
Date: Thu, 17 Nov 2016 23:26:08 +0100
Subject: [PATCH] Fix hiding some non-empty namespaces

---
 src/libvaladoc/api/node.vala | 8 +++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/src/libvaladoc/api/node.vala b/src/libvaladoc/api/node.vala
index 580828f..ff5fad9 100644
--- a/src/libvaladoc/api/node.vala
+++ b/src/libvaladoc/api/node.vala
@@ -176,7 +176,13 @@ public abstract class Valadoc.Api.Node : Item, Browsable, Documentation, Compara
 	 * Specifies whether this node has at least one visible child
 	 */
 	public bool has_visible_children (Settings settings) {
-		return has_visible_children_by_types (per_type_children.keys.to_array (), settings);
+		/* for some reason per_type_children.keys.to_array() returns rubbish */
+		foreach (NodeType type in per_type_children.keys) {
+			if (has_visible_children_by_type (type, settings)) {
+return true;
+			}
+		}
+		return false;
 	}
 
 	/**
-- 
2.10.2

Bug#844762: amarok crashes on startup with "Message recipient disconnected from message bus without replying"

[Phil Dibowitz]

Package: amarok
Version: 2.8.0-5
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Amarok crashes like this every time I start it:


$ amarok
QDBusConnection: session D-Bus connection created before QCoreApplication.
Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication.
Application may misbehave.
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QDBusConnection: session D-Bus connection created before QCoreApplication.
Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication.
Application may misbehave.
kbuildsycoca4 running...
KCrash: Application 'amarok' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
KCrash: Connect sock_file=/home/phil/.kde/socket-rider/kdeinit4__0
unnamed app(12406): Communication problem with  "amarok" , it probably crashed.
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Message recipient 
disconnected from message bus without replying" "


I have tried removing my ~/.kde/apps/amarok but it doesn't help.


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

Kernel: Linux 4.1.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages amarok depends on:
ii  amarok-common 2.8.0-5
ii  amarok-utils  2.8.0-5
ii  kde-runtime   4:15.08.3-1
ii  libaio1   0.3.110-3
ii  libavcodec57  7:3.2-2
ii  libavformat57 7:3.2-2
ii  libavutil55   7:3.2-2
ii  libc6 2.24-5
ii  libcurl3-gnutls   7.51.0-1
ii  libgcc1   1:5.3.1-11
ii  libgcrypt20   1.7.3-2
ii  libgdk-pixbuf2.0-02.32.3-1.2
ii  libgl1-mesa-glx [libgl1]  12.0.4-2
ii  libglib2.0-0  2.48.1-3
ii  libgpod4  0.8.3-5
ii  libkcmutils4  4:4.14.25-1
ii  libkdecore5   4:4.14.25-1
ii  libkdeui5 4:4.14.25-1
ii  libkdewebkit5 4:4.14.25-1
ii  libkdnssd44:4.14.25-1
ii  libkfile4 4:4.14.25-1
ii  libkio5   4:4.14.25-1
ii  libknewstuff3-4   4:4.14.25-1
ii  liblastfm11.0.9-1
ii  libloudmouth1-0   1.5.3-2
ii  libmtp9   1.1.12-1
ii  libmysqlclient18  5.6.30-1
ii  libofa0   0.9.3-13
ii  libphonon44:4.9.0-4
ii  libplasma34:4.14.25-1
ii  libqjson0 0.8.1-3
ii  libqt4-dbus   4:4.8.7+dfsg-6
ii  libqt4-network4:4.8.7+dfsg-6
ii  libqt4-opengl 4:4.8.7+dfsg-6
ii  libqt4-script 4:4.8.7+dfsg-6
ii  libqt4-sql4:4.8.7+dfsg-6
ii  libqt4-svg4:4.8.7+dfsg-6
ii  libqt4-xml4:4.8.7+dfsg-6
ii  libqtcore44:4.8.7+dfsg-6
ii  libqtgui4 4:4.8.7+dfsg-6
ii  libqtscript4-core 0.2.0-1
ii  libqtscript4-gui  0.2.0-1
ii  libqtscript4-network  0.2.0-1
ii  libqtscript4-sql  0.2.0-1
ii  libqtscript4-uitools  0.2.0-1
ii  libqtscript4-xml  0.2.0-1
ii  libqtwebkit4  2.3.4.dfsg-6
ii  libsolid4 4:4.14.25-1
ii  libstdc++65.3.1-11
ii  libthreadweaver4  4:4.14.25-1
ii  libx11-6  2:1.6.3-1
ii  libxml2   2.9.4+dfsg1-1
ii  phonon4:4.9.0-4
ii  zlib1g1:1.2.8.dfsg-2+b3

Versions of packages amarok recommends:
ii  clamz0.5-2+b1
ii  kio-audiocd  4:16.08.0-1

Versions of packages amarok suggests:
pn  amarok-doc 
ii  libqt4-sql-mysql   4:4.8.7+dfsg-6
pn  libqt4-sql-psql
pn  libqt4-sql-sqlite  
pn  moodbar

Versions of packages amarok-common depends on:
ii  perl  5.22.2-5

amarok-common recommends no packages.

Versions of packages amarok is related to:
ii  phonon-backend-vlc [phonon-backend]  0.9.0-1

-- no debconf information

Bug#829078: Temporary Solution to end-users

[Logan Schmidt]

 

Our team discovered the issue is not present on the Debian used in
Ubuntu 16.04.1. 

30,000ft answer, use 16.04.1 until this Debian specific issue is
resolved. Refrain from Ubuntu 16.10 and apt-get'ing elasticsearch 

Hope this helps anyone else,-- 
-- 

Logan Schmidt / Chief Technology Officer
lschm...@realpeoplesratings.com / 262-278-0243 

Real Peoples Ratings 
www.realpeoplesratings.com [1] 

  

Links:
--
[1] http://www.realpeoplesratings.com/

Bug#840211: perlunicook man page does not display utf8 char beyond ascii

[Russ Allbery]

Dominique Dumont  writes:
> On Friday, 18 November 2016 09:34:03 CET Russ Allbery wrote:

>> Guillem did some more investigation, and sadly it turns out that raw
>> UTF-8 in man pages continues to break even completely current man
>> implementations on platforms like macOS.

> That's a constraint we do not have on Debian/unstable.

> Considering [1], we may want to patch Debian's perl to produce utf8 man
> pages even if upstream cannot, due to portability constraints.

That's not strictly true, which is the reason why I haven't already
switched Linux systems over to generating UTF-8 by default.  This means
that you cannot create man pages with pod2man on a Linux system and have
them work on any other system, something that pod2man has, up until this
point, always guaranteed.

This will break some uses of pod2man.  It's not uncommon for people to
write man pages in POD even for non-Perl packages, and ship release
tarballs with pregenerated man pages so that the installer doesn't have to
have Perl locally.  If those contain UTF-8, this will result in man pages
in the release tarball that aren't portable.

It may well be that this is acceptable breakage (I'm pretty much convinced
that it is), but it's not a decision with zero drawbacks.

-- 
Russ Allbery (r...@debian.org)   

Bug#844756: mysql-workbench: Does not show in GNOME Software app

[Jeremy Bicha]

Package: mysql-workbench
Version: 6.3.6+dfsg-1

The GNOME version of Debian stretch includes the GNOME Software app by
default to install software. mysql-workbench currently does not show
in the app (at least if it is not already installed).

I haven't tested this but it might be fixed by simply dropping the
.xpm icon (debian/rules, debian/mysql-workbench.install) since I think
appstream gets confused when it sees an .xpm icon. If this is the only
reason the package build-depends on imagemagick, that dependency might
be removed too.

http://appstream.ubuntu.com/zesty/universe/issues/mysql-workbench.html

https://appstream.debian.org/sid/main/issues/mysql-workbench.html

(That issue doesn't show up in Debian's issue tracker which is
configured differently.)
is not show

Thanks,
Jeremy Bicha

Bug#844757: firefox: More Plasma compatibility like plasmazilla provides for ubuntu

[Ferdinand Pöll]

Package: firefox
Version: 50.0-1
Severity: wishlist
Tags: newcomer

Dear Maintainer,

I recently found versions of Firefox which were patched for better
compatibility to KDE Plasma. For Ubuntu, they are maintained by the
"plasmazilla team" (https://launchpad.net/~plasmazilla). What they do is
basically applying patches from here (http://www.rosenauer.org/hg/mozilla/) on
Firefox and Thunderbird. I read that these patches are also used in other
distos like openSUSE and Chakra.

I'd like to have this also in Debian.

Regards

Ferdinand



-- Package-specific info:

-- Extensions information
Name: 1-Click YouTube Video Downloader
Location: ${PROFILE_EXTENSIONS}/youtubedownloa...@peterolayev.com.xpi
Status: enabled

Name: Adblock Plus
Location: ${PROFILE_EXTENSIONS}/{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}.xpi
Status: user-disabled

Name: AdNauseam
Location: ${PROFILE_EXTENSIONS}/adnaus...@rednoise.org.xpi
Status: enabled

Name: Application Update Service Helper
Location: ${PROFILE_EXTENSIONS}/aushel...@mozilla.org.xpi
Status: enabled

Name: Deutsch (DE) Language Pack locale
Location: 
/usr/lib/firefox/browser/extensions/langpack...@firefox.mozilla.org.xpi
Package: firefox-l10n-de
Status: enabled

Name: Disconnect
Location: ${PROFILE_EXTENSIONS}/2...@disconnect.me.xpi
Status: user-disabled

Name: Extended DNSSEC Validator
Location: ${PROFILE_EXTENSIONS}/extended-valida...@os3sec.org
Status: user-disabled

Name: GNU LibreJS
Location: ${PROFILE_EXTENSIONS}/jid1-ktlzuoiikvf...@jetpack.xpi
Status: user-disabled

Name: HTTPS Everywhere
Location: ${PROFILE_EXTENSIONS}/https-everywh...@eff.org.xpi
Status: enabled

Name: Lightbeam
Location: ${PROFILE_EXTENSIONS}/jid1-f9uj2thwoam...@jetpack.xpi
Status: user-disabled

Name: Multi-process staged rollout
Location: ${PROFILE_EXTENSIONS}/e10sroll...@mozilla.org.xpi
Status: enabled

Name: NoScript
Location: ${PROFILE_EXTENSIONS}/{73a6fe31-595d-460b-a920-fcc0f8843232}.xpi
Status: user-disabled

Name: Pocket
Location: ${PROFILE_EXTENSIONS}/fire...@getpocket.com.xpi
Status: enabled

Name: Random Agent Spoofer
Location: ${PROFILE_EXTENSIONS}/jid1-avgcef1zovz...@jetpack.xpi
Status: user-disabled

Name: Smart HTTPS
Location: ${PROFILE_EXTENSIONS}/jid0-ofwt2zcakhhkfl7kp4...@jetpack.xpi
Status: user-disabled

Name: SSleuth
Location: ${PROFILE_EXTENSIONS}/ssle...@github.xpi
Status: enabled

Name: Standard theme
Location: 
/usr/lib/firefox/browser/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}.xpi
Package: firefox
Status: enabled

Name: uBlock Origin
Location: ${PROFILE_EXTENSIONS}/ublo...@raymondhill.net.xpi
Status: user-disabled

Name: Video DownloadHelper
Location: ${PROFILE_EXTENSIONS}/{b9db16a4-6edc-47ec-a1f4-b86292ed211d}.xpi
Status: user-disabled

Name: Web Compat
Location: ${PROFILE_EXTENSIONS}/webcom...@mozilla.org.xpi
Status: enabled

Name: YouTube Unblocker Plus
Location: ${PROFILE_EXTENSIONS}/ad...@ytunblocker.com.xpi
Status: user-disabled

-- Plugins information
Name: Citrix Receiver for Linux
Location: /opt/Citrix/ICAClient/npica.so
Package: icaclient
Status: disabled

Name: IcedTea-Web Plugin (using IcedTea-Web 1.6.2 (1.6.2-3))
Location: /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/IcedTeaPlugin.so
Package: icedtea-8-plugin:amd64
Status: disabled

Name: KParts Plugin
Location: /usr/lib/mozilla/plugins/libkpartsplugin.so
Package: kpartsplugin
Status: disabled

Name: MozPlugger 1.14.5 handles QuickTime and Windows Media Player Plugin 
(1.14.5)
Location: /usr/lib/mozilla/plugins/mozplugger.so
Package: mozplugger
Status: disabled

Name: Shockwave Flash (11.2.202.644)
Location: /usr/lib/flashplayer-mozilla/libflashplayer.so
Package: flashplayer-mozilla
Status: enabled


-- Addons package information
ii  firefox50.0-1   amd64Mozilla Firefox web browser
ii  firefox-l10n-d 50.0-1   all  German language package for Firef
ii  flashplayer-mo 3:11.2.202.6 amd64Macromedia Flash Player
ii  icaclient  13.4.0.10109 amd64Citrix Receiver for Linux
ii  icedtea-8-plug 1.6.2-3  amd64web browser plugin based on OpenJ
ii  kpartsplugin   20120605-1   amd64Netscape-compatible plugin to emb
ii  mozplugger 1.14.5-2 amd64Plugin allowing external viewers 

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

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

Versions of packages firefox depends on:
ii  debianutils   4.8.1
ii  fontconfig2.11.0-6.7
ii  libasound21.1.2-1
ii  libatk1.0-0   2.22.0-1
ii  libc6 2.24-5
ii  libcairo-gobject2 1.14.6-1.1
ii  libcairo2 

Bug#844539: Please revert DN related behaviour change introduced in 3.5.6

[Andreas Metzler]

On 2016-11-18 Guido Günther  wrote:
> On Thu, Nov 17, 2016 at 07:57:05PM +0100, Andreas Metzler wrote:
[...]
> > Would you consider this to be a serious issue for libvirt? i.e. should
> > we block unfixed gnutls from propagating to testing?

> I don't think that would be a good idea.

Ok, I will let it propagate to testing tomorrow or on sunday before
pushing the changes in experimental to unstable.

Thanks for testing!

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#844758: blender: rebuild against Xorg 1.19

[Marc Jeffrey Driftmeyer]

Package: blender
Version: 2.78.a+dfsg0-1
Severity: normal

Dear Maintainer,

Thank you for updating to 2.78a. Now, with the newly released xserver-xorg-core 
and it's siblings Blender has artifacts all acrossed it's application making it 
nearly impossible to use. It redraws/blits to the screen duplicate views and 
more.

Please rebuild against the lastest Xorg. If you need screenshots I'll be happy 
to provide them.

Oh and I second the request of building the Docs/manual with the package.

Sincerely,

Marc J. Driftmeyer

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

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

Versions of packages blender depends on:
ii  blender-data  2.78.a+dfsg0-1
ii  fonts-dejavu  2.37-1
ii  libavcodec57  7:3.2-2
ii  libavdevice57 7:3.2-2
ii  libavformat57 7:3.2-2
ii  libavutil55   7:3.2-2
ii  libboost-atomic1.62.0 1.62.0+dfsg-4
ii  libboost-chrono1.62.0 1.62.0+dfsg-4
ii  libboost-date-time1.62.0  1.62.0+dfsg-4
ii  libboost-filesystem1.62.0 1.62.0+dfsg-4
ii  libboost-iostreams1.62.0  1.62.0+dfsg-4
ii  libboost-locale1.62.0 1.62.0+dfsg-4
ii  libboost-regex1.62.0  1.62.0+dfsg-4
ii  libboost-system1.62.0 1.62.0+dfsg-4
ii  libboost-thread1.62.0 1.62.0+dfsg-4
ii  libc6 2.24-5
ii  libfftw3-double3  3.3.5-1
ii  libfontconfig12.11.0-6.7
ii  libfreetype6  2.6.3-3+b1
ii  libgcc1   1:6.2.0-13
ii  libgl1-mesa-glx [libgl1]  12.0.4-2
ii  libglew2.02.0.0-3
ii  libglu1-mesa [libglu1]9.0.0-2.1
ii  libgomp1  6.2.0-13
ii  libilmbase12  2.2.0-11
ii  libjack-jackd2-0 [libjack-0.116]  1.9.10+20150825git1ed50c92~dfsg-3
ii  libjemalloc1  3.6.0-9
ii  libjpeg62-turbo   1:1.5.1-2
ii  libopenal11:1.17.2-4
ii  libopencolorio1v5 1.0.9~dfsg0-6
ii  libopenexr22  2.2.0-11
ii  libopenimageio1.6 1.6.17~dfsg0-1+b2
ii  libopenjp2-7  2.1.2-1
ii  libopenvdb3.2 3.2.0-2+b1
ii  libpcre3  2:8.39-2
ii  libpng16-16   1.6.26-2
ii  libpython3.5  3.5.2-7
ii  libsndfile1   1.0.27-1
ii  libspnav0 0.2.3-1
ii  libstdc++66.2.0-13
ii  libswscale4   7:3.2-2
ii  libtbb2   4.3~20150611-2
ii  libtiff5  4.0.6-3
ii  libx11-6  2:1.6.3-1
ii  libxi62:1.7.6-1.1
ii  libxml2   2.9.4+dfsg1-2.1
ii  libxxf86vm1   1:1.1.4-1
pn  python3:any   
ii  zlib1g1:1.2.8.dfsg-2+b3

blender recommends no packages.

blender suggests no packages.

-- no debconf information

Bug#840186: closed by Michael Banck <mba...@debian.org> (Bug#840186: fixed in nwchem 6.6+r27746-3)

[Adrian Bunk]

Control: clone -1 -2
Control: notfixed -2 6.6+r27746-3
Control: severity -2 important
Control: retitle -2 nwchem builds on amd64 with -mtune=native


On Fri, Nov 18, 2016 at 12:24:04PM +, Debian Bug Tracking System wrote:
>...
>* debian/patches/19_disable_march_native.patch: New patch, disables
>  -march=native on amd64, by Edoardo Apra (Closes: #840186).
>...
> Date: Sun, 09 Oct 2016 14:59:15 +0300
> From: Adrian Bunk 
> To: Debian Bug Tracking System 
> Subject: nwchem builds on amd64 with -march=native
> 
> Source: nwchem
> Version: 6.6+r27746-2
> Severity: grave
> 
> src/config/makefile{,-legacy}.h sets -march=native
> and -mtune=native in amd64 builds.
> 
> -march=native means the code will only run on machines with a CPU
> compatible with the one on the machine where the package
> was built.
> 
> Building on a different buildd machine can also change
> where the code can run - including breaking existing
> setups in stable updates.
> 
> -mtune=native is less fatal, but in addition to (rare) problems
> due to the fact that the program is compiled differently depending
> on the build machine it makes the build non-reproducible.
> 
> Please remove -march=native and -mtune=native

-march=native was removed, but -mtune=native is still present.

This is less bad, but still a bug:
The resulting code is now expected to run everywhere, but it will be 
different depending on what build machine was used.
This leaves an opportunity for strange bugs that disappear when 
recompiling (on a different machine).
And it makes the build non-reproducible.

Please also remove -mtune=native.

Thanks
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#840211: perlunicook man page does not display utf8 char beyond ascii

[Russ Allbery]

Dominique Dumont  writes:

> Looks like I was not clear. I was thinking of patching perl build system
> to generate perl* man page (perlrun perlunicook...) as utf8 man page.

> That should not impact the generation of other man pages (i.e. not in
> Debian perl package) using pod2man.

Oh, yes.  I thought that had already been done at some point by forcing
the build system to pass -u, but possibly not.  I'm not sure how hard that
is to do.

-- 
Russ Allbery (r...@debian.org)   

Bug#844715: [Pkg-openssl-devel] Bug#844715: openssl: segfault in shlibloadtest (observed on x32) due to dlopen/dlclose/OPENSSL_atexit/OPENSSL_cleanup ordering

[Kurt Roeckx]

On Fri, Nov 18, 2016 at 08:05:15PM +0100, Kurt Roeckx wrote:
> On Fri, Nov 18, 2016 at 12:59:57PM +0100, Thorsten Glaser wrote:
> > Breakpoint 1, OPENSSL_atexit (handler=handler@entry=0xf6745c50 
> > ) at crypto/init.c:604
> > 604 {
> > 
> > There is our 0xf6745c50, which is ssl_library_stop… huh?
> 
> [...]
> > 
> > That’s .text of libssl.so.1.1!
> > 
> > So it appears that dynamically loaded libraries are dismantled,
> > and OPENSSL_cleanup() is called too late. This might even be a
> > bug on other architectures; I’m changing the bug title before
> > submitting.
> 
> So that looks like this doesn't work:
> /*
>  * Deliberately leak a reference to the handler. This will force the
>  * library/code containing the handler to remain loaded until we run 
> the
>  * atexit handler. If -znodelete has been used then this is
>  * unneccessary.
>  */
> {
> DSO *dso = NULL;
> 
> dso = DSO_dsobyaddr(handlersym.sym, DSO_FLAG_NO_UNLOAD_ON_FREE);
> DSO_free(dso);
> }

According to b6d5ba1a9f004d637acac18ae3519fe063b6b5e1 we should be
using -znodelete, but that probably didn't end up in the Debian
packaging properly.


Kurt

Bug#829078: Any word?

[Logan Schmidt]

 

Is there any word on this? We are deploying Elasticsearch servers today
and are getting the same YAML problem when trying to start the service.
We are using Ubuntu 16.10 (64 bit). Could we try different distro level
like 16.04? This is a Debian specific issue not to sure what course of
action to take here. 

Any help is appreciated. Thanks, 

-- 

Logan Schmidt / Chief Technology Officer
lschm...@realpeoplesratings.com / 262-278-0243 

Real Peoples Ratings 
www.realpeoplesratings.com [1] 

  

Links:
--
[1] http://www.realpeoplesratings.com/

Bug#842675: lightdm FTBFS on !x86: error: symbols mismatch

[Adrian Bunk]

Control: severity -1 serious
Control: retitle -1 lightdm FTBFS on !x86: error: symbols mismatch

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

The only successful builds of 1.18.2-3 were on x86.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#844780: gcc-6-arm-linux-gnueabihf: cross-compiled code fails to link on target with native gcc-6

[Matthijs van Duin]

I've found the problem, it has nothing to do with cross-gcc. The issue lies
with the native gcc 6.2 which has been configured with
--enable-default-pie, which (at least on arm) breaks its ability to link
any code produced by earlier compilers.

Bug#844486: Bug#844526: Bug#844486: gnuplot-qt: Mismatch between the program and library build versions with GNUTERM=wxt

[Vincent Lefevre]

Control: tags -1 patch

On 2016-11-17 15:37:13 +0200, Adrian Bunk wrote:
> On Thu, Nov 17, 2016 at 09:41:07AM +0100, Vincent Lefevre wrote:
> > A warning can be very annoying (e.g. because it mixes with other output
> > to the terminal) and possibly break scripts that don't expect output to
> > stderr. If this is not expected to work, then an error like upstreams's
> > behavior is the right thing to do (there is a real issue, and the user
> > must make sure that it gets fixed). Otherwise a warning isn't needed,
> > except in some debug mode for developers or andvanced users (but such
> > a mode would not be the default).
> 
> Yes, this is what should be done.

Removing the

  wxLogWarning(msg.c_str());

line from the warn-for-compiler-abi-mismatch.patch patch (and
updating the comment) is sufficient. This gives the attached
patch.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- wxwidgets3.0-3.0.2.orig/src/common/appbase.cpp
+++ wxwidgets3.0-3.0.2/src/common/appbase.cpp
@@ -762,6 +762,22 @@ bool wxAppConsoleBase::CheckBuildOptions
 msg.Printf(wxT("Mismatch between the program and library build 
versions detected.\nThe library used %s,\nand %s used %s."),
lib.c_str(), progName.c_str(), prog.c_str());
 
+
+   int l_off = lib.Find("compiler with C++ ABI ");
+   int p_off = prog.Find("compiler with C++ ABI ");
+   if (l_off != wxNOT_FOUND && p_off != wxNOT_FOUND) {
+   int space;
+   space = lib.Find(' ', l_off);
+   lib.erase(l_off, space - l_off);
+   space = prog.Find(' ', l_off);
+   prog.erase(p_off, space - p_off);
+   if (lib == prog) {
+   // Only difference is the ABI version, which apparently only
+   // affect obscure cases.
+   return false;
+   }
+   }
+
 wxLogFatalError(msg.c_str());
 
 // normally wxLogFatalError doesn't return

Bug#768604: Problems with item delivery, n.0000454407

[FedEx 2Day]

Dear Customer,

We could not deliver your item.
Please, open email attachment to print shipment label.

Yours faithfully,
Jesse Lake,
FedEx Station Manager.



FedEx_ID_454407.doc
Description: MS-Word document

Bug#644738: Problems with item delivery, n.0000914416

[FedEx SmartPost]

Dear Customer,

This is to confirm that one or more of your parcels has been shipped.
Shipment Label is attached to email.

Yours faithfully,
Stephen Bowling,
Sr. Support Manager.



Delivery_Notification_914416.doc
Description: MS-Word document

Bug#644738: We could not deliver your parcel, #00830372

[FedEx International MailService]

Dear Customer,

This is to confirm that one or more of your parcels has been shipped.
Please, open email attachment to print shipment label.

Kind regards,
Milton Obrien,
Support Agent.



Delivery_Notification_00830372.doc
Description: MS-Word document

Bug#834080: elasticsearch: FTBFS: Could not resolve dependencies for project org.elasticsearch:elasticsearch:jar:1.7.5

[tony mancill]

On Thu, Nov 17, 2016 at 09:11:14AM +0100, Michael Prokop wrote:
> * Hans Joachim Desserud [Tue Oct 04, 2016 at 09:40:16PM +0200]:
> 
> > After adding a build dependency on libantlr3-runtime-java,
> > elasticsearch built successfully. (See the attached patch)
> 
> Any news about this from the maintainers? Is there any specific
> reason why this wasn't uploaded yet? (Asking because the
> elasticsearch package isn't part of testing/stretch yet and am
> wondering whether we might see stretch being released with the
> elasticsearch package included.)

Hi Mika,

Correcting my previous update to this bug report...

Based upon the recent discussion in #829078 [1] and as things currently
stand with elasticsearch, I'm not planning on working on an upload for
this.

Thank you,
tony

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829078

Bug#844254: NMU to DELAYED/5

[Hilko Bengen]

Hi,

I have just made a non-maintainer upload (libesmtp/1.0.6-4.1) to
DELAYED/5-day. If necessary, feel free to reschedule or cancel my
upload.

The simple change I made can be found in my Github fork at
. I have verified that the libesmtp6
package (built using sbuild) indeed depends on libssl1.1.

Cheers,
-Hilko

Bug#844703: [l10n] Updated Czech translation of apt-listbugs

[Francesco Poli]

On Fri, 18 Nov 2016 10:08:02 +0100 Miroslav Kure wrote:

[...]
> Hi,
> 
> in attachement there is updated Czech (cs.po) translation of 
> apt-listbugs. Please include it with the package.
> 
> Thank you

Hello Miroslav!
Thanks for the update.

I will soon push the translation to the public git repository; it will
be included in the next upload.

Your contribution is really appreciated!
Bye.


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgp7kvotRVK3Z.pgp
Description: PGP signature

Bug#829078: Any word?

[Hilko Bengen]

* Emmanuel Bourg:

> Hi Logan,
>
> If you need Elasticsearch on Debian/Ubuntu your best bet for now is to
> install the upstream package available on the download page [1]. The
> elasticsearch package maintained by Debian isn't ready for prime time
> yet and will probably not be part of the Stretch release.

As the person who did the initial packaging work, I second this.

While it might be nice to get the package in order, I do not feel that
it's worth it. At this point, Elasticsearch is a crippled open-core
product that can only be properly used if one pays to use non-free
plug-ins for basic features that ought to be part of the core in the
first place, i.e. authentication or the option of encrypting inter-node
communication.

It is unclear to me whether or not upstream considers the 1.7 release
still supported. From my previous interactions with them regarding
security fixes I got the sense that this is not the case. They are not
even interested in providing detailed information about CVE-worthy
security issues that may help wih backporing.

Cheers,
-Hilko

Bug#844776: cbmc FTBFS on s390x and mips*: Running Pointer_array5/test.desc FAILED

[Adrian Bunk]

Source: cbmc
Version: 5.5-1
Severity: serious

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

...
  Running Pointer_array5/test.desc  [FAILED]
...
Tests failed
  1 of 383 tests failed, 20 tests skipped
Failed test: Pointer_array5
CBMC version 5.5 64-bit s390x linux
Parsing main.c
file  line 0: :0:0: warning: "__STDC_VERSION__" 
redefined
: note: this is the location of the previous definition
Converting
Type-checking main
Generating GOTO Program
Adding CPROVER library (s390x)
file  line 0: :0:0: warning: "__STDC_VERSION__" 
redefined
: note: this is the location of the previous definition
Removal of function pointers and virtual functions
Partial Inlining
Generic Property Instrumentation
Starting Bounded Model Checking
size of program expression: 95 steps
simple slicing removed 24 assignments
Generated 1 VCC(s), 1 remaining after simplification
Passing problem to propositional reduction
converting SSA
Running propositional reduction
Post-processing
Solving with MiniSAT 2.2.1 with simplifier
12568 variables, 25409 clauses
SAT checker: instance is SATISFIABLE
Runtime decision procedure: 0.114s

** Results:
[main.assertion.1] assertion address==: FAILURE

** 1 of 1 failed (1 iteration)
VERIFICATION FAILED
EXIT=10
SIGNAL=0


debian/rules:31: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/«PKGBUILDDIR»'
debian/rules:15: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

Bug#844779: osmose-emulator FTBFS on armel and armhf: QGLImage.cpp:108:20: error: 'glLoadIdentity' was not declared in this scope

[Adrian Bunk]

Source: osmose-emulator
Version: 1.0-2
Severity: serious

https://buildd.debian.org/status/package.php?p=osmose-emulator=sid

...
g++ -c -pipe -std=c++11 -Wall -Wextra -Wno-unused -Wcast-qual -g -O2 
-fdebug-prefix-map=/«PKGBUILDDIR»=. -fPIE -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -W -D_REENTRANT 
-fPIC -DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB 
-I. -I. -Icpu -Iosmose -isystem /usr/include/arm-linux-gnueabi/qt5 -isystem 
/usr/include/arm-linux-gnueabi/qt5/QtOpenGL -isystem 
/usr/include/arm-linux-gnueabi/qt5/QtWidgets -isystem 
/usr/include/arm-linux-gnueabi/qt5/QtGui -isystem 
/usr/include/arm-linux-gnueabi/qt5/QtCore -I. -I. 
-I/usr/lib/arm-linux-gnueabi/qt5/mkspecs/linux-g++ -o QGLImage.o QGLImage.cpp
QGLImage.cpp: In member function 'virtual void QGLImage::paintGL()':
QGLImage.cpp:108:20: error: 'glLoadIdentity' was not declared in this scope
 glLoadIdentity();
^
QGLImage.cpp:111:103: error: 'GL_UNSIGNED_INT_8_8_8_8_REV' was not declared in 
this scope
 glTexImage2D (GL_TEXTURE_2D, 0, GL_RGBA, adjustedTextureWidth, 
adjustedTextureHeight, 0, GL_RGBA, GL_UNSIGNED_INT_8_8_8_8_REV, textureBuffer);

   ^~~
QGLImage.cpp:112:13: error: 'GL_QUADS' was not declared in this scope
 glBegin(GL_QUADS);
 ^~~~
QGLImage.cpp:112:21: error: 'glBegin' was not declared in this scope
 glBegin(GL_QUADS);
 ^
QGLImage.cpp:114:21: error: 'glTexCoord2f' was not declared in this scope
 glTexCoord2f(0,0);
 ^
...

Bug#844781: libowfat FTBFS on s390x: undefined reference to `__libc_waitpid'

[Adrian Bunk]

Source: libowfat
Version: 0.30-2
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=libowfat=s390x=0.30-2=1460534507

...

gcc -nostdlib -static -L/usr/lib/diet/lib-s390x /usr/lib/diet/lib-s390x/start.o 
-g -o t t.o libowfat.a -lpthread -isystem /usr/lib/diet/include -D__dietlibc__ 
-Os -fomit-frame-pointer /usr/lib/diet/lib-s390x/libc.a -lgcc 
-fno-stack-protector 
t.o: In function `ret0':
/«PKGBUILDDIR»/t.c:54: warning: warning: your code still has assertions enabled!
/usr/lib/diet/lib-s390x/libpthread.a(pthread_internal.o): In function 
`pthread_exit':
pthread_internal.c:(.text+0x3a2): undefined reference to `__libc_waitpid'
/usr/lib/diet/lib-s390x/libpthread.a(pthread_internal.o): In function 
`__thread_restart':
pthread_internal.c:(.text+0x9ca): undefined reference to `__libc_waitpid'
collect2: error: ld returned 1 exit status
/«PKGBUILDDIR»/GNUmakefile:171: recipe for target 't' failed
make[2]: *** [t] Error 1
make[2]: Leaving directory '/«PKGBUILDDIR»/build-diet'
debian/rules:12: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/«PKGBUILDDIR»'
debian/rules:9: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

Bug#844254: NMU to DELAYED/5

[Jeremy T. Bouse]

I've taken a look at the diff of your fork. I'm about to be out of town
and away from my development box for the next two weeks in about 8 hours
so I can't do anything at this time... I'll let the NMU go through and
then pull your commit hash 96eb8e628c8e87200a208281e569523c8fb77bf8 in
and prepare a 1.0.6-5 build to accept it.


On 11/18/2016 5:52 PM, Hilko Bengen wrote:
> Hi,
>
> I have just made a non-maintainer upload (libesmtp/1.0.6-4.1) to
> DELAYED/5-day. If necessary, feel free to reschedule or cancel my
> upload.
>
> The simple change I made can be found in my Github fork at
> . I have verified that the libesmtp6
> package (built using sbuild) indeed depends on libssl1.1.
>
> Cheers,
> -Hilko

Bug#844782: Please revert problematic sparc64 GOT patch

[John Paul Adrian Glaubitz]

On 11/19/2016 01:37 AM, James Clarke wrote:
> [1] b19753ce31da347605dfa903c6fd2158e2444f0d

Attaching the reversed patch which applies cleanly against git master
for binutils-gdb when removing the part that patches the upstream
changelog.

Fixing this is important, it causes quite a number of segfaults. I suspect
this is also the reason why cmake fails to build from source.

Thanks,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
diff --git b/bfd/elfxx-sparc.c a/bfd/elfxx-sparc.c
index 30daedf..63558c7 100644
--- b/bfd/elfxx-sparc.c
+++ a/bfd/elfxx-sparc.c
@@ -2661,19 +2661,19 @@ _bfd_sparc_elf_size_dynamic_sections (bfd *output_bfd,
   /* Allocate .plt and .got entries, and space for local symbols.  */
   htab_traverse (htab->loc_hash_table, allocate_local_dynrelocs, info);
 
-  if (!htab->is_vxworks
+  if (! ABI_64_P (output_bfd)
+  && !htab->is_vxworks
   && elf_hash_table (info)->dynamic_sections_created)
 {
-  if (! ABI_64_P (output_bfd))
-{
-  /* Make space for the trailing nop in .plt.  */
-  if (htab->elf.splt->size > 0)
-htab->elf.splt->size += 1 * SPARC_INSN_BYTES;
-}
+  /* Make space for the trailing nop in .plt.  */
+  if (htab->elf.splt->size > 0)
+	htab->elf.splt->size += 1 * SPARC_INSN_BYTES;
 
   /* If the .got section is more than 0x1000 bytes, we add
 	 0x1000 to the value of _GLOBAL_OFFSET_TABLE_, so that 13
-	 bit relocations have a greater chance of working.  */
+	 bit relocations have a greater chance of working.
+
+	 FIXME: Make this optimization work for 64-bit too.  */
   if (htab->elf.sgot->size >= 0x1000
 	  && elf_hash_table (info)->hgot->root.u.def.value == 0)
 	elf_hash_table (info)->hgot->root.u.def.value = 0x1000;

Bug#805116: ITP: wifi-switcher

[Oleg SHALAEV]

In my opinion the program is ready for uploading under the GPL2, see
http://chalaev.com/wifi-switcher
https://github.com/chalaev/wifi-switcher
https://github.com/chalaev/wifi-switcher/tree/master/current_release
but I can not do it because I am not a Debian Developer.
Is it possible to submit the program to a Debian Developer,
or I have to register as a  a Debian Developer myself?

On 2015-11-16 10:06, Andrei POPESCU wrote:

Control: reassign -1 wnpp
Control: retitle -1 ITP: wifi-switcher -- script to automatically switch 
between networks

...


signature.asc
Description: PGP signature

Bug#844783: wmaker: wmmenugen crashes rampantly

[Matthew Gabeler-Lee]

Package: wmaker
Version: 0.95.7-6+b1
Severity: normal

Trying to use wmmenugen to import the xdg desktop files doesn't work because
wmmenugen segfaults like there's no tomorrow ;)

This months old mailing list post looks like a likely fix:

https://www.mail-archive.com/wmaker-dev@lists.windowmaker.org/msg06734.html

Doesn't seem to be fixed upstream, however (current head):

http://repo.or.cz/wmaker-crm.git/blob/0a009143c32064d47dc857ec50e95116b7c5b6be:/util/wmmenugen.c#l109


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

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

Versions of packages wmaker depends on:
ii  libc62.24-5
ii  libfontconfig1   2.11.0-6.7
ii  libfreetype6 2.6.3-3+b1
ii  libgif7  5.1.4-0.4
ii  libjpeg62-turbo  1:1.5.1-2
ii  libpng16-16  1.6.26-1
ii  libtiff5 4.0.6-3
ii  libwings30.95.7-6+b1
ii  libwraster5  0.95.7-6+b1
ii  libwutil50.95.7-6+b1
ii  libx11-6 2:1.6.3-1
ii  libxext6 2:1.3.3-1
ii  libxinerama1 2:1.1.3-1+b1
ii  libxpm4  1:3.5.11-1+b1
ii  wmaker-common0.95.7-6

wmaker recommends no packages.

Versions of packages wmaker suggests:
ii  desktop-base8.0.2
ii  lxterminal [x-terminal-emulator]0.2.0-1
ii  menu2.1.47
ii  rxvt-unicode [x-terminal-emulator]  9.22-1+b1
ii  wmaker-data 0.9~3-4
pn  wmaker-utils
ii  x11-apps7.7+6
ii  xterm [x-terminal-emulator] 327-1

-- no debconf information

Bug#836347: gkrellweather: weather.noaa.gov has been shut down

[Greg Schenzel]

Package: gkrellweather
Followup-For: Bug #836347

Still an issue in 8 and 9.

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages gkrellweather depends on:
ii  gkrellm 2.3.6~rc1-1
ii  libatk1.0-0 2.14.0-1
ii  libc6   2.19-18+deb8u6
ii  libcairo2   1.14.0-2.1+deb8u1
ii  libfontconfig1  2.11.0-6.3+deb8u1
ii  libfreetype62.5.2-3+deb8u1
ii  libglib2.0-02.42.1-1+b1
ii  libgtk2.0-0 2.24.25-3+deb8u1
ii  libpango1.0-0   1.36.8-3
ii  libwww-perl 6.08-1
ii  perl5.20.2-3+deb8u6
ii  wget1.16-1+deb8u1

gkrellweather recommends no packages.

gkrellweather suggests no packages.

-- no debconf information

Bug#825086: Package links against libmysqlclient_r

[Michael Prokop]

* Robie Basak [Mon May 23, 2016 at 02:16:52PM +0100]:

> Please stop linking against libmysqlclient_r and link directly against
> libmysqlclient instead.

> Your package currently links against libmysqlclient_r. libmysqlclient_r
> was the thread-safe version of libmysqlclient in previous MySQL
> releases. However, libmysqlclient has been itself been made thread-safe
> since before the current libmysqlclient18. Thus libmysqlclient_r is
> currently deprecated and provided as a compatibility symlink only, and
> will disappear in MySQL 5.7. This change can be made now, in advance of
> a possible future transition to libmysqlclient20, which does not provide
> the _r variant.

> In Ubuntu, we have done this with the attached quilt patch, which I
> believe is also applicable to Debian.

Any news on this one? Is there anything prevent the package
maintainer to upload a new package version with the patch applied?
libmysql++-dev isn't in testing because of this and the freeze for
stretch is coming closer.

regards,
-mika-


signature.asc
Description: Digital signature

Bug#844777: why FTBFS on mips*, ppc64el, s390x: cannot stat './META.frama-c-jessie'

[Adrian Bunk]

Source: why
Version: 2.36-2
Severity: serious

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

...
mkdir -p /«PKGBUILDDIR»/debian/why/usr/share/why/coq
cp -f lib/coq/Jessie_memory_model.vo /«PKGBUILDDIR»/debian/why/usr/share/why/coq
/usr/bin/make -C frama-c-plugin install
make[3]: Entering directory '/«PKGBUILDDIR»/frama-c-plugin'
mkdir -p /«PKGBUILDDIR»/debian/why/usr/lib/frama-c/plugins
cp ./META.frama-c-jessie ./Jessie.cmi ./Jessie.cmo ./Jessie.cma  
/«PKGBUILDDIR»/debian/why/usr/lib/frama-c/plugins
cp: cannot stat './META.frama-c-jessie': No such file or directory
/usr/share/frama-c/Makefile.dynamic:263: recipe for target 'install' failed
make[3]: *** [install] Error 1

Bug#844780: gcc-6-arm-linux-gnueabihf: cross-compiled code fails to link on target with native gcc-6

[Matthijs van Duin]

Package: gcc-6-arm-linux-gnueabihf
Version: 6.1.1-9cross1
Severity: important

Dear Maintainer,

If I cross-compile any code (even a basic hello-world) and then attempt
to link the resulting objects on the target system (stretch, armhf)
using the native gcc-6 toolchain (which is 6.2.0 in testing and has
already been for a while) I get the following failure:

/usr/bin/ld: hello.o: relocation R_ARM_THM_MOVW_ABS_NC against `a local symbol' 
can not be used when making a shared object; recompile with -fPIC
hello.o: error adding symbols: Bad value
collect2: error: ld returned 1 exit status

Recompiling with -fPIC as suggested does in fact fix the problem, but
this should not be necessary and never has been.  (Compiling without it
but linking with the cross-toolchain also results in a working binary.)

Note that cross-compiling + native linking is for example needed to be
able to use distcc to speed up compilation on small ARM systems by
delegating most of the work to a build server, which is how I ran into
this issue.  This setup is currently completely broken due to this bug.


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

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

Versions of packages gcc-6-arm-linux-gnueabihf depends on:
ii  binutils-arm-linux-gnueabihf2.27.51.20161108-1
ii  cpp-6-arm-linux-gnueabihf   6.1.1-9cross1
ii  gcc-6-arm-linux-gnueabihf-base  6.1.1-9cross1
ii  libc6   2.24-5
ii  libcc1-06.2.0-13
ii  libgcc-6-dev-armhf-cross6.1.1-9cross1
ii  libgcc1 1:6.2.0-13
ii  libgmp102:6.1.1+dfsg-1
ii  libisl150.17.1-1
ii  libmpc3 1.0.3-1
ii  libmpfr43.1.5-1
ii  libstdc++6  6.2.0-13
ii  zlib1g  1:1.2.8.dfsg-2+b3

Versions of packages gcc-6-arm-linux-gnueabihf recommends:
ii  libc6-dev-armhf-cross  2.24-1cross1

Versions of packages gcc-6-arm-linux-gnueabihf suggests:
ii  gcc-6-doc 6.1.0-1
pn  gcc-6-locales 
pn  libasan3-dbg-armhf-cross  
pn  libatomic1-dbg-armhf-cross
pn  libcilkrts5-dbg-armhf-cross   
pn  libgcc1-dbg-armhf-cross   
pn  libgomp1-dbg-armhf-cross  
pn  libitm1-dbg-armhf-cross   
pn  liblsan0-dbg-armhf-cross  
pn  libmpx2-dbg-armhf-cross   
pn  libquadmath0-dbg-armhf-cross  
pn  libtsan0-dbg-armhf-cross  
pn  libubsan0-dbg-armhf-cross 

-- no debconf information

Bug#843454: ITP: docker-credential-helpers -- native store to keep Docker credentials, safe

[Felipe Sateler]

On 17 November 2016 at 01:41, Jason Pleau  wrote:
>
> Hi Felipe,
>
> 2016-11-16 17:40 GMT-05:00 Felipe Sateler :
> > Hi Jason
> >
> > On Sun, 6 Nov 2016 13:16:58 -0500 Jason Pleau  wrote:
> >> Package: wnpp
> >> Severity: wishlist
> >> Owner: Jason Pleau 
> >>
> >> * Package name: docker-credential-helpers
> >>   Version : 0.3.0
> >>   Upstream Author : David Calavera 
> >> * URL : https://github.com/docker/docker-credential-helpers/
> >> * License : MIT
> >>   Programming Lang: Go / C
> >>   Description : native store to keep Docker credentials safe
> >>
> >> docker-credential-helpers provides a Linux executable to store Docker
> >> credentials. (It also has one for OSX and Windows, but those won't be
> >> built nor used in Debian).
> >>
> >> It is a dependency of an upcoming python package
> >> "dockerpy-creds", which is needed to update python-docker to its latest
> >> upstream version.
> >
> >
> > Have you done some work yet on this? If so, could you push it to
> > collab-maint so I can take a look?
>
> Not yet, I scheduled some time saturday to work on it and hopefully
> finalize it, I will keep you updated :)

I had some time today so I took the liberty to start the packaging. I
have added it to collab-maint/docker-credential-helpers.git.

-- 

Saludos,
Felipe Sateler

Bug#844782: Please revert problematic sparc64 GOT patch

[James Clarke]

Source: binutils
Version: 2.27.51.20161118-1
Severity: important
User: debian-sp...@lists.debian.org
Usertags: sparc64
X-Debbugs-Cc: debian-sp...@lists.debian.org

Hi Matthias,
While global symbol references are now fine, we've noticed that TLS is
broken in a similar way, except in this case the linker can't do much to
fix it up unless it wants to patch the opcodes themselves. This has the
very bad side effect of causing apt-get to segfault in libstdc++. Until
this gets properly dealt with upstream, could you please revert the
relevant patch[1]?

James

[1] b19753ce31da347605dfa903c6fd2158e2444f0d

Bug#828363: kde4libs: FTBFS with openssl 1.1.0

[John Paul Adrian Glaubitz]

Hi!

Would it be possible to change the build dependency from libssl-dev to
libssl1.0-dev for the time being to temporarily resolve this issue?

It's rather ugly to have a library as central as kde4libs FTBFS because
it blocks archive rebuilds or the bootstrapping of new architectures.

Thanks,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#795701: ITP: trojita -- Fast Qt IMAP e-mail client.

[Alf Gaida]

control retitle -1 ITP: trojita -- Fast Qt IMAP e-mail client.
control owner !

The packaging is in good shape - the sources are not. So trojita isn't fit for 
sid, maybe for experimental. But trojita becomes better with every commit.

Bug#828363: kde4libs: FTBFS with openssl 1.1.0

[Scott Kitterman]

On November 18, 2016 7:37:31 PM EST, John Paul Adrian Glaubitz 
 wrote:
>Hi!
>
>Would it be possible to change the build dependency from libssl-dev to
>libssl1.0-dev for the time being to temporarily resolve this issue?
>
>It's rather ugly to have a library as central as kde4libs FTBFS because
>it blocks archive rebuilds or the bootstrapping of new architectures.

I think we should wait and see what the release team has to say about the 
transition first.  They are apparently cooking something up.

Scott K

Bug#844775: udev: initramfs init-bottom/udev script fails to mount /dev when using virtual filesystems

[Luca Boccassi]

Package: udev
Version: 232-3
Severity: normal

Dear Maintainer,

Due to a recent change in busybox and initramfs-tools, the mount utility
in the initramfs now comes from util-linux rather than busybox.

scripts/init-bottom/udev calls "mount -o move", which was supported by
busybox's mount but not by util-linux's mount.

See the following for the full discussion:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823856

This causes an error and a failure to boot when using virtual file
systems.

Both utilities support "mount --move", so attached is a patch that
implements this small change. I've successfully used this change to get
our squashfs based image working again.

Thank you!

Kind regards,
Luca Boccassi

From 34addb1aeae38026b1f8a451a99d1bde4d922da7 Mon Sep 17 00:00:00 2001
From: Luca Boccassi 
Date: Fri, 18 Nov 2016 20:09:58 +
Subject: [PATCH] Use mount --move in initramfs-tools udev script

Due to recent changes in busybox and initramfs-tools the mount
utility is no longer the one from busybox but from util-linux.
The latter does not support mount -o move.
The former supports both -o move and --move, so use it instead to be
compatible with both.
See this discussion for more details:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823856
---
 debian/extra/initramfs-tools/scripts/init-bottom/udev | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/extra/initramfs-tools/scripts/init-bottom/udev 
b/debian/extra/initramfs-tools/scripts/init-bottom/udev
index 81081e3..e997380 100755
--- a/debian/extra/initramfs-tools/scripts/init-bottom/udev
+++ b/debian/extra/initramfs-tools/scripts/init-bottom/udev
@@ -15,7 +15,7 @@ esac
 udevadm control --exit
 
 # move the /dev tmpfs to the rootfs
-mount -n -o move /dev ${rootmnt}/dev
+mount -n --move /dev ${rootmnt}/dev
 
 # create a temporary symlink to the final /dev for other initramfs scripts
 if command -v nuke >/dev/null; then
-- 
2.1.4



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

Bug#844778: clsync FTBFS on !x86: error: '__NR_select' undeclared here

[Adrian Bunk]

Source: clsync
Version: 0.4.2-1
Severity: serious

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

...
In file included from privileged.c:64:0:
privileged.c:88:34: error: '__NR_select' undeclared here (not in a function)
  BPF_JUMP(BPF_JMP+BPF_JEQ+BPF_K, __NR_##syscall, 0, 1), \
...

Bug#258096: Are you getting my email?

[Simon]

*Good day and how are you?  This is like the 3rd mail I have sent to this
email without any reply. Are you no longer using this email...? Please let
me know if this email is still valid or not. or better give me your working
email. *

*I have sent 3 mails to your email and they all failed. Dont know  if  this
will also be received or not? Please confirm.*

*I will resend the mail if you did not receive the first one I sent. *

*Thanks*

Bug#826297: patch

[積丹尼 Dan Jacobson]

--- README.Debian   2016-11-19 07:17:12.657166692 +0800
+++ README.Debian.NEW   2016-11-19 07:25:48.293169579 +0800
@@ -45,6 +45,16 @@
 and then get more detailed information with "systemctl status -l foo.service"
 to get a service "foo"'s status and recent logging.
 
+To make a /shutdown-log.txt file on Debian:
+1. boot with the debug options:
+systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M enforcing=0
+2. save the following script as /lib/systemd/system-shutdown/debug.sh and make 
it executable:
+#!/bin/sh
+mount -o remount,rw /
+dmesg > /shutdown-log.txt
+mount -o remount,ro /
+3. reboot
+
 Enable and use networkd
 ===
 networkd is a small and lean service to configure network interfaces, designed

Bug#566943: We could not deliver your parcel, #0000310268

[FedEx 2Day]

Dear Customer,

Courier was unable to deliver the parcel to you.
Delivery Label is attached to this email.

Thanks and best regards,
Timothy Copeland,
Sr. Operation Manager.



Label_310268.doc
Description: MS-Word document

Bug#844785: systemd prevents polkit from working properly

[Raphaël Halimi]

Package: systemd
Version: 232-1

Since systemd 232, lightdm's menu entries to
shutdown/reboot/suspend/hibernate the system are grayed out.

Furthermore, GNOME polkit authentication agent fails to start (I use
openbox, with the agent normally started from
~/.config/openbox/autostart). When manually run in a terminal, it
immediately exits with the error message:

"polkit-gnome-1-WARNING **: Unable to determine the session we are in:
No session for pid ..."

Downgrading systemd/libsystemd0/libpam-systemd to version 231-10 fixes
the problem (I also tried 232-1 and 232-2, but they didn't work either).

Sorry for the vague bug title (and the probably wrong binary package),
but it's the best I can do since I'm not at all familiar with the way
systemd/polkit/pam/lightdm/whatever interact with each other.

Also, I just spotted this bug today despite the fact that it was
introduced two weeks ago, because I rarely shutdown my sid box.

Regards,

-- 
Raphaël Halimi



signature.asc
Description: OpenPGP digital signature

Bug#844787: chromium: Please package chromevox

[Jean-Philippe MENGUAL]

Package: chromium
Version: 53.0.2785.143-1
Severity: wishlist

Dear Maintainer,

I try to use Chromium, in paqicular for Skype extension and so on. But with 
gnome-orca,
it's inaccessible. However Chromium ships now a tts, which uses Espeak I think:
Chromevox. I'm unable to install it as an extension. Could xou please package
it to make easier accessibility to this browser?

Regards,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


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

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

Versions of packages chromium depends on:
ii  libasound2   1.1.2-1
ii  libatk1.0-0  2.22.0-1
ii  libavcodec57 7:3.2-2
ii  libavformat577:3.2-2
ii  libavutil55  7:3.2-2
ii  libc62.24-5
ii  libcairo21.14.6-1.1
ii  libcups2 2.2.1-2
ii  libdbus-1-3  1.10.12-1
ii  libexpat12.2.0-1
ii  libfontconfig1   2.11.0-6.7
ii  libfreetype6 2.6.3-3+b1
ii  libgcc1  1:6.2.0-13
ii  libgdk-pixbuf2.0-0   2.36.0-1
ii  libglib2.0-0 2.50.2-1
ii  libgnome-keyring03.12.0-1+b1
ii  libgtk-3-0   3.22.3-2
ii  libharfbuzz0b1.2.7-1+b1
ii  libjpeg62-turbo  1:1.5.1-2
ii  libnettle6   3.3-1
ii  libnspr4 2:4.12-2
ii  libnss3  2:3.26.2-1
ii  libpango-1.0-0   1.40.3-3
ii  libpangocairo-1.0-0  1.40.3-3
ii  libpci3  1:3.3.1-1.1
ii  libpulse09.0-4
ii  libspeechd2  0.8.5-3
ii  libstdc++6   6.2.0-13
ii  libx11-6 2:1.6.3-1
ii  libxcomposite1   1:0.4.4-1
ii  libxcursor1  1:1.1.14-1+b1
ii  libxdamage1  1:1.1.4-2+b1
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.2-1
ii  libxi6   2:1.7.6-1.1
ii  libxml2  2.9.4+dfsg1-2.1
ii  libxrandr2   2:1.5.0-1
ii  libxrender1  1:0.9.9-2
ii  libxslt1.1   1.1.29-2
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.2-1+b1
ii  x11-utils7.7+3
ii  xdg-utils1.1.1-1

Versions of packages chromium recommends:
ii  fonts-liberation  1:1.07.4-2

Versions of packages chromium suggests:
ii  chromium-l10n  53.0.2785.143-1

-- no debconf information

Bug#844788: hibernate: suspends ok but hangs on restore after decompressing with stretch kernel on macbook pro

[Andrew Worsley]

Package: hibernate
Version: 2.0+15+g88d54a8-1
Severity: important


  I have an older jessie kernel linux-image-3.16.7-ckt25 (with quirk
  patches for disabling the wireless which macbook bios leaves enabled)
  and that works very well. I can suspend and resume many times.

  But the current debian stretch kernel will suspend fine but hangs on restore 
*just* as it
  has finished expending the image into memory. It looks like it has
  worked but is just stuck on the restoring screen at 100% but not
  responsive to any keys.

  From dmesg:

 DMI: Apple Inc. MacBookPro10,1/Mac-C3EC7CD22292981F, BIOS 
MBP101.88Z.00EE.B0A.1509111559 09/11/2015

 Happy to re-compile kernels/switch on additional debugging, run other
 commands or re-log to another package if that is more appropriate.

 Kind of not sure where to go other than digging into the code myself -
 which I don't know where to start at...


 Andrew



-- Package-specific info:
--- configuration
==> /etc/hibernate/common.conf <==
Verbosity 4
LogFile /var/log/hibernate.log
LogVerbosity 4
Distribution debian
SaveClock restore-only
OnSuspend 20 echo "Good night!"
OnResume 20 echo "Good morning!"
UnloadBlacklistedModules yes
LoadModules auto
DownInterfaces wlan3
SwitchToTextMode yes
==> /etc/hibernate/disk.conf <==
TryMethod ususpend-disk.conf
TryMethod sysfs-disk.conf
==> /etc/hibernate/hibernate.conf <==
TryMethod tuxonice.conf
TryMethod disk.conf
TryMethod ram.conf
==> /etc/hibernate/ram.conf <==
TryMethod ususpend-ram.conf
TryMethod sysfs-ram.conf
==> /etc/hibernate/sysfs-disk.conf <==
UseSysfsPowerState disk
Include common.conf
==> /etc/hibernate/sysfs-ram.conf <==
UseSysfsPowerState mem
Include common.conf
==> /etc/hibernate/tuxonice.conf <==
UseTuxOnIce yes
Reboot no
EnableEscape yes
DefaultConsoleLevel 1
Compressor lzo
Encryptor none
FullSpeedCPU yes
Include common.conf
==> /etc/hibernate/ususpend-both.conf <==
USuspendMethod both
Include common.conf
==> /etc/hibernate/ususpend-disk.conf <==
USuspendMethod disk
Include common.conf
==> /etc/hibernate/ususpend-ram.conf <==
USuspendMethod ram
Include common.conf

--- /sys/power
==> /sys/power/disk <==
[platform] shutdown reboot suspend 
==> /sys/power/image_size <==
9714061926
==> /sys/power/pm_async <==
1
==> /sys/power/pm_freeze_timeout <==
2
==> /sys/power/pm_print_times <==
0
==> /sys/power/pm_test <==
[none] core processors platform devices freezer
==> /sys/power/reserved_size <==
1048576
==> /sys/power/resume <==
8:6
==> /sys/power/state <==
freeze mem disk
==> /sys/power/wakeup_count <==
3

--- s2ram -n
Machine unknown
This machine can be identified by:
sys_vendor   = ""
sys_product  = ""
sys_version  = ""
bios_version = ""
--- log
Starting suspend at Thursday 17 November 23:44:59 AEDT 2016
hibernate: [01] Executing CheckLastResume ... 
hibernate: [01] Executing CheckRunlevel ... 
hibernate: [01] Executing LockFileGet ... 
hibernate: [01] Executing NewKernelFileCheck ... 
hibernate: [10] Executing EnsureUSuspendCapable ... 
hibernate: [11] Executing XHacksSuspendHook1 ... 
hibernate: [20] Executing MiscLaunchAuxFunc1 ... 
Executing echo "Good night!"...
Good night!
hibernate: [59] Executing RemountXFSBootRO ... 
hibernate: [60] Executing NetworkStop ... 
hibernate: [89] Executing SaveKernelModprobe ... 
hibernate: [91] Executing ModulesUnloadBlacklist ... 
hibernate: [95] Executing XHacksSuspendHook2 ... 
hibernate: [98] Executing CheckRunlevel ... 
hibernate: [99] Executing DoUSuspend ... 
hibernate: Running /usr/sbin/s2disk ...
hibernate: [90] Executing ModulesLoad ... 
hibernate: [89] Executing RestoreKernelModprobe ... 
hibernate: [85] Executing XHacksResumeHook2 ... 
hibernate: [70] Executing ClockRestore ... 
hibernate: [60] Executing NetworkStart ... 
hibernate: [59] Executing RemountXFSBootRW ... 
hibernate: [20] Executing MiscLaunchAuxFunc2 ... 
Executing echo "Good morning!"...
Good morning!
hibernate: [11] Executing XHacksResumeHook1 ... 
hibernate: [01] Executing NoteLastResume ... 
hibernate: [01] Executing LockFilePut ... 
Resumed at Saturday 19 November 14:09:13 AEDT 2016

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

Kernel: Linux 3.16.7-ckt25-b43-earlyquirk-freset (SMP w/8 CPU cores)
Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages hibernate depends on:
ii  dpkg  1.18.10
ii  kbd   2.0.3-2

Versions of packages hibernate recommends:
ii  dash 0.5.8-2.3
ii  hdparm   9.48+ds-2
ii  uswsusp  1.0+20120915-6.1
ii  vbetool  1.1-4

Versions of packages hibernate suggests:
pn  915resolution
pn  xscreensaver | kscreensaver | gnome-screensaver | xlock | vlock  

-- Configuration Files:
/etc/hibernate/blacklisted-modules changed:
acx100
acx_pci
hsfmodem
prism54
bcm4400 2.6.0   3.99.0

Bug#844658: stretch GIT broken

[Daniel Kahn Gillmor]

I got an off-list note from the reporter that
https://bugs.debian.org/844658 was due to an interaction with packages
From a non-debian repository that had been locally installed.  Once that
repo was removed, git worked fine, so i'm closing #844658.

To the reporter: please don't feel discouraged by reporting a bug that
turns out to not be a bug from debian's perspective.  In this case,
there was nothing for debian package maintainers to do, and you fixed
the problem yourself. In other cases, there can be something that the
maintainers can do to fix packages for everyone else using debian.

Bug reports are a significant and valuable contribution to the debian
project, even though some of them turn out to be "not debian's fault"
(and therefore unfixable from within debian).  Please keep on reporting
bugs you encounter, we need to know when things aren't working for
users!

Regards,

 --dkg


signature.asc
Description: PGP signature

Bug#837926: debian-installer: please use fonts-noto-hinted to display the Sinhala script

[Harshula]

On 18/11/16 22:12, Jonas Smedegaard wrote:
> Quoting Christian Perrier (2016-11-18 09:11:00)

>> Chagning the D-I font to Noto for all languages hasn't been 
>> validated...and the current font is well tested and accepted.
>>
>> So, as a consequence, I'd prefer a udeb that would be suited for 
>> Sinhala.
> 
> Makes sense.
> 
> udeb package fonts-noto-hinted-udeb now, since 20161116-1, contains only 
> fonts relevant for debian-installer - i.e. for now only Sinhala fonts.

Thanks!! That was very quick.

cya,
#

Bug#844786: ITP: snap -- The open telemetry framework

[Steve Langasek]

Hi Matt,

On Fri, Nov 18, 2016 at 10:40:41PM -0500, matt jones wrote:
> Package: wnpp
> Severity: wishlist
> Owner: matt jones 

> * Package name: snap
>   Version : 1.0.0
>   Upstream Author : Intel
> * URL : http://snap-telemetry.io/
> * License : Apache License Version 2.0
>   Programming Lang: Go
>   Description : The open telemetry framework

> Snap is an open telemetry framework designed to simplify the collection,
> processing and publishing of system data through a single API. The goals of
> this project are to:

There is already a package named 'snap' in the archive:

Package: snap
Maintainer: Debian Med Packaging Team 

Description-en: location of genes from DNA sequence with hidden markov model
 SNAP is a general purpose gene finding program suitable for both eukaryotic
 and prokaryotic genomes. SNAP is an acroynm for Semi-HMM-based Nucleic Acid
 Parser.

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#687049: Unable to deliver your item, #0000808208

[FedEx Standard Overnight]

Dear Customer,

We could not deliver your parcel.
Please, open email attachment to print shipment label.

Thank you for choosing FedEx,
Carlos Ford,
Sr. Operation Manager.



FedEx_ID_808208.doc
Description: MS-Word document

Bug#842040: Please add https support

[Jose R R]

On Fri, Nov 18, 2016 at 8:18 AM, Philipp Kern  wrote:
> On 12.11.2016 18:16, Josh Triplett wrote:
>> On Thu, 10 Nov 2016 01:14:33 -0800 Jose R R  wrote:
>>> On Tue, Oct 25, 2016 at 6:17 AM, Marga Manterola  wrote:
 Package: debian-installer
 Severity: normal

 The installer currently doesn't support downloading packages from https
 mirrors, because busybox's wget doesn't support https.
>>>
>>> In order to add SSL support to BusyBox wget, itself to be used wih
>>> ssl_helper, I used matrixssl-3-4-2-open.tgz
>>> < http://www.matrixssl.org/ >
>>>
>>> to build my custom BusyBox udeb for my Reiser4-enabled Debian-Installer
>>> < https://sf.net/projects/debian-reiser4/ >
>>>
>>> No idea if suggestion fulfills bug need - just my 2 cents ;-)
>>
>> Can you provide a link for your patches to busybox wget to add SSL
>> support?  That sounds like it'd substantially decrease size compared to
>> including GNU wget and supporting libraries.
>
> Unfortunately matrixssl isn't even in Debian at this point.
>
The official Debian maintainer(s) busybox source lacks a directory
that is upstream in the busybox official source.
For instance, for upstream busybox-1.25.1, the relevant path to *that*
directory is:

busybox-1.25.1/networking/ssl_helper

then,
If we untar matrixssl-3-4-2-open.tgz , we get directory

matrixssl-3-4-2-open/

copying ssl_helper directory into matrixssl-3-4-2-open/., we build
first matrixssl:

make

After successful build:

cd ssl_helper

./ssl_helper.sh  ## to compile and link the helper, thus

ssl_helper.c generates ssl_helper executable (and ssl_helper.o ? ;-)

To provide SSL-enabled busybox wget you only need the executable ssl_helper

hence,

Prior to building your busybox udeb

create a directory inside your 'official' Debian maintainers busybox
untarred source

mkdir --verbose -p _install/usr/bin

copy your generated executable ssl_helper into above directory, i.e.,

_install/usr/bin/ssl_helper   ##<== executable should be this and here

>From this dirty hack, *any* Debian-helper-generated busybox UDEB
should contain busybox SSL-enabled wget

Sorry, I am busy - but will try to create a patch for official Debian
source from git -- though I am not an official Debian maintainer.

sample from my reiser4 Debian-Installer (d-i):
< 
https://metztli.it/readOnlyEphemeral/busybox-udeb_1.22.0-19.1_amd64.udeb.SHA256SUM
># Text contents
< https://metztli.it/readOnlyEphemeral/busybox-udeb_1.22.0-19.1_amd64.udeb >

If above udeb link is downloaded locally, it may be expanded to analyze as:
dpkg -X busybox-udeb_1.22.0-19.1_amd64.udeb  tempDir

Happy hacking!


Best Professional Regards.

-- 
Jose R R
http://metztli.it
-
Download Debian-Reiser4 for AMD64 https://sf.net/projects/debian-reiser4/
-
Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
-
from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!
-

Bug#835274: dh-text no longer needed

[Dmitry Bogatov]

[2016-11-18 08:54] Christian Seiler 
> I'm hence removing the moreinfo tag, because your course of action
> to remove dietlibc-dev from Build-Depends of your package is the
> right one. If at some point in the future bglibs are recompiled
> against dietlibc (in addition to glibc preferably) it might make
> sense to re-add the dietlibc-dev Build-Depends here, but for now
> you can't do anything about that.
>
> I would only ask you to alter the changelog to reflect the actual
> reason why you don't use dietlibc anymore; that is use an entry
> like:
>
>  * Drop dietlibc-dev from Build-Depends for now. (Libraries
>depended upon are not compiled for dietlibc anymore.)

Done. Updated version on mentors.

-- 
X-Web-Site: https://sinsekvu.github.io | Note that I process my email in batch,
Accept-Languages: eo,ru,en | at most once every 24 hours. If matter
Accept: text/plain, text/x-diff| is urgent, you have my phone number.


pgpBrKwwXVlVa.pgp
Description: PGP signature

Bug#844839: networking-ovs-dpdk: FTBFS: build-dependency not installable: python-neutron (>= 1:7.0.0~)

[Lucas Nussbaum]

Source: networking-ovs-dpdk
Version: 2015.1.1+git20151118.35ac4c7-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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: debhelper (>= 9~), dh-python, dh-systemd, 
> openstack-pkg-tools (>= 23~), python-all, python-setuptools, python-sphinx, 
> python-babel (>= 1.3), python-coverage (>= 3.6), python-hacking (>= 0.9.2), 
> python-netaddr (>= 0.7.12), python-neutron (>= 1:7.0.0~), python-oslo.service 
> (>= 0.1.0), python-oslosphinx, python-oslotest (>= 1:1.1.0~a1), python-pbr 
> (>= 0.11), python-six (>= 1.9.0), python-tempest-lib (>= 0.2.0), 
> python-testscenarios (>= 0.4), python-testtools (>= 0.9.34), subunit (>= 
> 0.0.18), testrepository (>= 0.0.18)
> Filtered Build-Depends: debhelper (>= 9~), dh-python, dh-systemd, 
> openstack-pkg-tools (>= 23~), python-all, python-setuptools, python-sphinx, 
> python-babel (>= 1.3), python-coverage (>= 3.6), python-hacking (>= 0.9.2), 
> python-netaddr (>= 0.7.12), python-neutron (>= 1:7.0.0~), python-oslo.service 
> (>= 0.1.0), python-oslosphinx, python-oslotest (>= 1:1.1.0~a1), python-pbr 
> (>= 0.11), python-six (>= 1.9.0), python-tempest-lib (>= 0.2.0), 
> python-testscenarios (>= 0.4), python-testtools (>= 0.9.34), subunit (>= 
> 0.0.18), testrepository (>= 0.0.18)
> dpkg-deb: building package 'sbuild-build-depends-networking-ovs-dpdk-dummy' 
> in 
> '/<>/resolver-DLmLsu/apt_archive/sbuild-build-depends-networking-ovs-dpdk-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-networking-ovs-dpdk-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-DLmLsu/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-DLmLsu/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-DLmLsu/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-DLmLsu/apt_archive ./ Sources [563 B]
> Get:5 copy:/<>/resolver-DLmLsu/apt_archive ./ Packages [644 B]
> Fetched 2170 B in 0s (188 kB/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install networking-ovs-dpdk 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-networking-ovs-dpdk-dummy : Depends: python-neutron (>= 
> 1:7.0.0~) 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://aws-logs.debian.net/2016/11/18/networking-ovs-dpdk_2015.1.1+git20151118.35ac4c7-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#844837: python3.5: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity

[Lucas Nussbaum]

Source: python3.5
Version: 3.5.2-7
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> data = self.socket.recv(buffer_size)
>   File "/<>/Lib/ssl.py", line 922, in recv
> return self.read(buflen)
>   File "/<>/Lib/ssl.py", line 799, in read
> return self._sslobj.read(len, buffer)
>   File "/<>/Lib/ssl.py", line 585, in read
> v = self._sslobj.read(len)
> OSError: [Errno 0] Error
> E: Caught signal ‘Terminated’: terminating immediately
> Makefile:526: recipe for target 'run_profile_task' failed
> make[2]: *** [run_profile_task] Terminated
> Makefile:504: recipe for target 'profile-opt' failed
> make[1]: *** [profile-opt] Terminated
> debian/rules:274: recipe for target 'stamps/stamp-build-static' failed
> make: *** [stamps/stamp-build-static] Terminated
> E: Build killed with signal TERM after 150 minutes of inactivity

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/python3.5_3.5.2-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#844832: yade: FTBFS: build-dependency not installable: libvtk6-dev

[Lucas Nussbaum]

Source: yade
Version: 2016.06a-5
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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: cmake, debhelper (>= 9), freeglut3-dev, help2man, 
> ipython (>= 5), libboost-all-dev, libbz2-dev, libcgal-dev, libeigen3-dev (>= 
> 3.2.1-2), libgl1-mesa-dev, libgts-dev, libloki-dev, libmetis-dev, 
> libopenblas-dev, libqglviewer-dev-qt5, libsuitesparse-dev, libvtk6-dev, 
> libxi-dev, libxmu-dev, pyqt5-dev-tools, python-all-dev, python-gts, 
> python-imaging, python-matplotlib, python-minieigen, python-numpy, 
> python-sip, python-pyqt5, python-tk, python-xlib, zlib1g-dev, dvipng, 
> graphviz, libjs-jquery, lmodern, python-bibtex, python-sphinx, 
> texlive-fonts-recommended, texlive-generic-extra, texlive-latex-extra, 
> texlive-latex-recommended, texlive-pictures, texlive-xetex, tipa
> Filtered Build-Depends: cmake, debhelper (>= 9), freeglut3-dev, help2man, 
> ipython (>= 5), libboost-all-dev, libbz2-dev, libcgal-dev, libeigen3-dev (>= 
> 3.2.1-2), libgl1-mesa-dev, libgts-dev, libloki-dev, libmetis-dev, 
> libopenblas-dev, libqglviewer-dev-qt5, libsuitesparse-dev, libvtk6-dev, 
> libxi-dev, libxmu-dev, pyqt5-dev-tools, python-all-dev, python-gts, 
> python-imaging, python-matplotlib, python-minieigen, python-numpy, 
> python-sip, python-pyqt5, python-tk, python-xlib, zlib1g-dev, dvipng, 
> graphviz, libjs-jquery, lmodern, python-bibtex, python-sphinx, 
> texlive-fonts-recommended, texlive-generic-extra, texlive-latex-extra, 
> texlive-latex-recommended, texlive-pictures, texlive-xetex, tipa
> dpkg-deb: building package 'sbuild-build-depends-yade-dummy' in 
> '/<>/resolver-dm1LPf/apt_archive/sbuild-build-depends-yade-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-yade-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-dm1LPf/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-dm1LPf/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-dm1LPf/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-dm1LPf/apt_archive ./ Sources [645 B]
> Get:5 copy:/<>/resolver-dm1LPf/apt_archive ./ Packages [707 B]
> Fetched 2315 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 yade 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-yade-dummy : Depends: libvtk6-dev 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://aws-logs.debian.net/2016/11/18/yade_2016.06a-5_unstable.log

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

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

Bug#844838: alljoyn-core-1604: FTBFS: common/crypto/openssl/CryptoAES.cc:285:92: error: 'AES_ctr128_encrypt' was not declared in this scope

[Lucas Nussbaum]

Source: alljoyn-core-1604
Version: 16.04a-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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++ -o build/linux/x86_64/release/obj/common/crypto/CryptoAES.o -c -std=c++11 
> -Wall -Werror -pipe -fno-exceptions -fno-strict-aliasing 
> -fno-asynchronous-unwind-tables -fno-unwind-tables -ffunction-sections 
> -fdata-sections -D_FORTIFY_SOURCE=2 -fPIC -Wno-long-long -Wno-deprecated 
> -Wno-unknown-pragmas -Wunused-parameter -Os -m64 -fPIC -DNDEBUG -DROUTER 
> -DQCC_OS_GROUP_POSIX -DQCC_OS_LINUX -D_GLIBCXX_USE_C99_FP_MACROS_DYNAMIC 
> -Ibuild/linux/x86_64/release/dist/cpp/inc 
> -Ibuild/linux/x86_64/release/dist/c/inc 
> -Ibuild/linux/x86_64/release/dist/cpp/inc/alljoyn -Icommon/inc 
> -Icommon/crypto -Ibuild/linux/x86_64/release/dist/cpp/inc 
> common/crypto/openssl/CryptoAES.cc
> common/crypto/openssl/CryptoAES.cc: In member function 'QStatus 
> qcc::Crypto_AES::Encrypt_CCM(const void*, void*, size_t&, const 
> qcc::KeyBlob&, const void*, size_t, uint8_t)':
> common/crypto/openssl/CryptoAES.cc:285:92: error: 'AES_ctr128_encrypt' was 
> not declared in this scope
>  AES_ctr128_encrypt(T.data, U.data, 16, >key, ivec.data, 
> ecount_buf.data, );
>   
>   ^
> common/crypto/openssl/CryptoAES.cc: In member function 'QStatus 
> qcc::Crypto_AES::Decrypt_CCM(const void*, void*, size_t&, const 
> qcc::KeyBlob&, const void*, size_t, uint8_t)':
> common/crypto/openssl/CryptoAES.cc:338:104: error: 'AES_ctr128_encrypt' was 
> not declared in this scope
>  AES_ctr128_encrypt(U.data, T.data, sizeof(T.data), >key, 
> ivec.data, ecount_buf.data, );
>   
>   ^
> scons: *** [build/linux/x86_64/release/obj/common/crypto/CryptoAES.o] Error 1
> scons: building terminated because of errors.
> debian/rules:39: recipe for target 'override_dh_auto_build' failed
> make[1]: *** [override_dh_auto_build] Error 2

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/alljoyn-core-1604_16.04a-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#844836: xmltooling: FTBFS: build-dependency not installable: libxml-security-c-dev (>= 1.7.3-3)

[Lucas Nussbaum]

Source: xmltooling
Version: 1.6.0-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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: cxxtest, debhelper (>= 9), dh-autoreconf, libboost-dev, 
> libcurl4-openssl-dev, liblog4shib-dev, libssl-dev, libxerces-c-dev, 
> libxml-security-c-dev (>= 1.7.3-3), pkg-config, doxygen, graphviz
> Filtered Build-Depends: cxxtest, debhelper (>= 9), dh-autoreconf, 
> libboost-dev, libcurl4-openssl-dev, liblog4shib-dev, libssl-dev, 
> libxerces-c-dev, libxml-security-c-dev (>= 1.7.3-3), pkg-config, doxygen, 
> graphviz
> dpkg-deb: building package 'sbuild-build-depends-xmltooling-dummy' in 
> '/<>/resolver-RcIM8Q/apt_archive/sbuild-build-depends-xmltooling-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-xmltooling-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-RcIM8Q/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-RcIM8Q/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/resolver-RcIM8Q/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-RcIM8Q/apt_archive ./ Sources [446 B]
> Get:5 copy:/<>/resolver-RcIM8Q/apt_archive ./ Packages [529 B]
> Fetched 1932 B in 0s (183 kB/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install xmltooling 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-xmltooling-dummy : Depends: libxml-security-c-dev (>= 
> 1.7.3-3) 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://aws-logs.debian.net/2016/11/18/xmltooling_1.6.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#844827: swift: FTBFS: build-dependency not installable: python-xattr (>= 0.4)

[Lucas Nussbaum]

Source: swift
Version: 2.10.0-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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: debhelper (>= 9), dh-exec, dh-python, dh-systemd, 
> openstack-pkg-tools (>= 48~), python-all, python-pbr, python-setuptools (>= 
> 20.6.8), python-sphinx, python-coverage, python-cryptography (>= 1.0), 
> python-dnspython (>= 1.14.0), python-eventlet (>= 0.17.4), python-greenlet 
> (>= 0.3.1), python-keystoneclient (>= 1:1.3.0), python-mock, python-netifaces 
> (>> 0.10.1), python-nose, python-nose-exclude, python-nosehtmloutput, 
> python-nosexcover, python-openssl, python-openstack.nose-plugin, 
> python-openstackdocstheme (>= 1.0.3), python-os-api-ref, python-os-testr (>= 
> 0.4.1), python-oslosphinx, python-pastedeploy (>= 1.3.3), python-pyeclib (>= 
> 1.2.0), python-six (>= 1.9.0), python-swiftclient, python-xattr (>= 0.4)
> Filtered Build-Depends: debhelper (>= 9), dh-exec, dh-python, dh-systemd, 
> openstack-pkg-tools (>= 48~), python-all, python-pbr, python-setuptools (>= 
> 20.6.8), python-sphinx, python-coverage, python-cryptography (>= 1.0), 
> python-dnspython (>= 1.14.0), python-eventlet (>= 0.17.4), python-greenlet 
> (>= 0.3.1), python-keystoneclient (>= 1:1.3.0), python-mock, python-netifaces 
> (>> 0.10.1), python-nose, python-nose-exclude, python-nosehtmloutput, 
> python-nosexcover, python-openssl, python-openstack.nose-plugin, 
> python-openstackdocstheme (>= 1.0.3), python-os-api-ref, python-os-testr (>= 
> 0.4.1), python-oslosphinx, python-pastedeploy (>= 1.3.3), python-pyeclib (>= 
> 1.2.0), python-six (>= 1.9.0), python-swiftclient, python-xattr (>= 0.4)
> dpkg-deb: building package 'sbuild-build-depends-swift-dummy' in 
> '/<>/resolver-Rc7xQs/apt_archive/sbuild-build-depends-swift-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-swift-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-Rc7xQs/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-Rc7xQs/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-Rc7xQs/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-Rc7xQs/apt_archive ./ Sources [622 B]
> Get:5 copy:/<>/resolver-Rc7xQs/apt_archive ./ Packages [702 B]
> Fetched 2287 B in 0s (203 kB/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install swift 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-swift-dummy : Depends: python-xattr (>= 0.4) 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://aws-logs.debian.net/2016/11/18/swift_2.10.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#844826: libapache2-mod-auth-mellon: FTBFS: build-dependency not installable: liblasso3-dev (>= 2.1.0)

[Lucas Nussbaum]

Source: libapache2-mod-auth-mellon
Version: 0.12.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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: debhelper (>= 9), autotools-dev, dh-apache2, 
> apache2-dev, libcurl3-dev, liblasso3-dev (>= 2.1.0)
> Filtered Build-Depends: debhelper (>= 9), autotools-dev, dh-apache2, 
> apache2-dev, libcurl3-dev, liblasso3-dev (>= 2.1.0)
> dpkg-deb: building package 
> 'sbuild-build-depends-libapache2-mod-auth-mellon-dummy' in 
> '/<>/resolver-Wf9xEN/apt_archive/sbuild-build-depends-libapache2-mod-auth-mellon-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   
> sbuild-build-depends-libapache2-mod-auth-mellon-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-Wf9xEN/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-Wf9xEN/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/resolver-Wf9xEN/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-Wf9xEN/apt_archive ./ Sources [391 B]
> Get:5 copy:/<>/resolver-Wf9xEN/apt_archive ./ Packages [482 B]
> Fetched 1830 B in 0s (174 kB/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install libapache2-mod-auth-mellon 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-libapache2-mod-auth-mellon-dummy : Depends: 
> liblasso3-dev (>= 2.1.0) 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://aws-logs.debian.net/2016/11/18/libapache2-mod-auth-mellon_0.12.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#844842: rt-authen-externalauth: FTBFS: build-dependency not installable: request-tracker4

[Lucas Nussbaum]

Source: rt-authen-externalauth
Version: 0.26-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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: debhelper (>= 9), libcgi-pm-perl, libdbi-perl, 
> libnet-ldap-perl, libnet-ssleay-perl, request-tracker4
> Filtered Build-Depends: debhelper (>= 9), libcgi-pm-perl, libdbi-perl, 
> libnet-ldap-perl, libnet-ssleay-perl, request-tracker4
> dpkg-deb: building package 
> 'sbuild-build-depends-rt-authen-externalauth-dummy' in 
> '/<>/resolver-Oi55Sd/apt_archive/sbuild-build-depends-rt-authen-externalauth-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   
> sbuild-build-depends-rt-authen-externalauth-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-Oi55Sd/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-Oi55Sd/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/resolver-Oi55Sd/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-Oi55Sd/apt_archive ./ Sources [391 B]
> Get:5 copy:/<>/resolver-Oi55Sd/apt_archive ./ Packages [487 B]
> Fetched 1835 B in 0s (160 kB/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install rt-authen-externalauth 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-rt-authen-externalauth-dummy : Depends: 
> request-tracker4 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://aws-logs.debian.net/2016/11/18/rt-authen-externalauth_0.26-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#844840: python-autobahn: FTBFS: unsatisfiable build-dependencies: python-nacl, python3-nacl

[Lucas Nussbaum]

Source: python-autobahn
Version: 0.14.1+dfsg1-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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: debhelper (>= 9), dh-python, python-all, 
> python-setuptools, python-sphinx, python3-all, python3-setuptools, 
> python-cbor, python-concurrent.futures (>= 2.1.5), python-enchant, python-lz4 
> (>= 0.2.1), python-mock (>= 1.3), python-msgpack (>= 0.4.0), python-nacl, 
> python-pytest (>= 2.6), python-qrcode, python-six, python-snappy (>= 0.5), 
> python-sphinx-rtd-theme, python-sphinxcontrib.spelling, python-trollius (>= 
> 2.0), python-twisted (>= 11.1), python-txaio (>= 2.5.1), python-unittest2 (>= 
> 1.1.0), python-zope.interface (>= 3.6), python3-cbor, python3-enchant, 
> python3-lz4 (>= 0.2.1), python3-mock (>= 1.3), python3-msgpack (>= 0.4.0), 
> python3-nacl, python3-pytest (>= 2.6.4), python3-six, python3-snappy (>= 
> 0.5), python3-twisted (>= 11.1), python3-txaio (>= 2.5.1), python3-unittest2 
> (>= 1.1.0), python3-zope.interface (>= 3.6)
> Filtered Build-Depends: debhelper (>= 9), dh-python, python-all, 
> python-setuptools, python-sphinx, python3-all, python3-setuptools, 
> python-cbor, python-concurrent.futures (>= 2.1.5), python-enchant, python-lz4 
> (>= 0.2.1), python-mock (>= 1.3), python-msgpack (>= 0.4.0), python-nacl, 
> python-pytest (>= 2.6), python-qrcode, python-six, python-snappy (>= 0.5), 
> python-sphinx-rtd-theme, python-sphinxcontrib.spelling, python-trollius (>= 
> 2.0), python-twisted (>= 11.1), python-txaio (>= 2.5.1), python-unittest2 (>= 
> 1.1.0), python-zope.interface (>= 3.6), python3-cbor, python3-enchant, 
> python3-lz4 (>= 0.2.1), python3-mock (>= 1.3), python3-msgpack (>= 0.4.0), 
> python3-nacl, python3-pytest (>= 2.6.4), python3-six, python3-snappy (>= 
> 0.5), python3-twisted (>= 11.1), python3-txaio (>= 2.5.1), python3-unittest2 
> (>= 1.1.0), python3-zope.interface (>= 3.6)
> dpkg-deb: building package 'sbuild-build-depends-python-autobahn-dummy' in 
> '/<>/resolver-0Z7JHe/apt_archive/sbuild-build-depends-python-autobahn-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-python-autobahn-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-0Z7JHe/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-0Z7JHe/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-0Z7JHe/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-0Z7JHe/apt_archive ./ Sources [605 B]
> Get:5 copy:/<>/resolver-0Z7JHe/apt_archive ./ Packages [686 B]
> Fetched 2254 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 python-autobahn 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-python-autobahn-dummy : Depends: python-nacl but it is 
> not going to be installed
>   Depends: python3-nacl 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://aws-logs.debian.net/2016/11/18/python-autobahn_0.14.1+dfsg1-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#844843: cppformat: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined reference to `pthread_create'

[Lucas Nussbaum]

Source: cppformat
Version: 3.0.0+ds-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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  -g -O2 -fdebug-prefix-map=/<>/cppformat-3.0.0+ds=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2   -Wl,-z,relro  
> CMakeFiles/cmTC_3b7b5.dir/CheckSymbolExists.c.o  -o cmTC_3b7b5 -rdynamic 
> CMakeFiles/cmTC_3b7b5.dir/CheckSymbolExists.c.o: In function `main':
> ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined 
> reference to `pthread_create'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/cppformat_3.0.0+ds-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#844841: jruby-maven-plugins: FTBFS: [ERROR] /<>/ruby-tools/src/main/java/de/saumya/mojo/gems/spec/yaml/YamlGemSpecificationIO.java:[8,26] cannot find symbol

[Lucas Nussbaum]

Source: jruby-maven-plugins
Version: 1.0.10.ds1-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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 -- install
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
>  -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo install -DskipTests 
> -Dnotimestamp=true -Dlocale=en_US
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO] 
> [INFO] JRuby Maven Mojos
> [INFO] Mojo Parent
> [INFO] Ruby Tools
> [INFO] JRuby Maven Mojo
> [INFO] Gem Maven Mojo
> [INFO]
>  
> [INFO] 
> 
> [INFO] Building JRuby Maven Mojos 1.0.10
> [INFO] 
> 
> [INFO] 
> [INFO] --- maven-install-plugin:2.5.2:install (default-install) @ 
> jruby-maven-plugins ---
> [INFO] Installing /<>/pom.xml to 
> /<>/debian/maven-repo/de/saumya/mojo/jruby-maven-plugins/1.0.10/jruby-maven-plugins-1.0.10.pom
> [INFO]
>  
> [INFO] 
> 
> [INFO] Building Mojo Parent 1.0.10
> [INFO] 
> 
> [INFO] 
> [INFO] --- build-helper-maven-plugin:1.8:add-source (add-source) @ 
> parent-mojo ---
> [INFO] Source directory: /<>/parent-mojo/target/sources added.
> [INFO] 
> [INFO] --- maven-plugin-plugin:3.3:helpmojo (default) @ parent-mojo ---
> [WARNING] Unsupported packaging type pom, execution skipped
> [INFO] 
> [INFO] --- maven-install-plugin:2.5.2:install (default-install) @ parent-mojo 
> ---
> [INFO] Installing /<>/parent-mojo/pom.xml to 
> /<>/debian/maven-repo/de/saumya/mojo/parent-mojo/1.0.10/parent-mojo-1.0.10.pom
> [INFO]
>  
> [INFO] 
> 
> [INFO] Building Ruby Tools 1.0.10
> [INFO] 
> 
> [INFO] 
> [INFO] --- maven-dependency-plugin:2.8:copy (copy jruby) @ ruby-tools ---
> [INFO] Configured Artifact: org.jruby:jruby-complete:debian:jar
> [INFO] Copying jruby-complete-debian.jar to 
> /<>/ruby-tools/target/jruby-complete-debian.jar
> [INFO] 
> [INFO] --- maven-dependency-plugin:2.8:copy-dependencies (copy gems) @ 
> ruby-tools ---
> [INFO] 
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ 
> ruby-tools ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 20 resources
> [INFO] 
> [INFO] --- exec-maven-plugin:1.1.1:exec (install gems) @ ruby-tools ---
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.2:compile (default-compile) @ ruby-tools 
> ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 45 source files to /<>/ruby-tools/target/classes
> [INFO] -
> [ERROR] COMPILATION ERROR : 
> [INFO] -
> [ERROR] 
> /<>/ruby-tools/src/main/java/de/saumya/mojo/gems/spec/yaml/YamlGemSpecificationIO.java:[6,26]
>  cannot find symbol
>   symbol:   class Dumper
>   location: package org.yaml.snakeyaml
> [ERROR] 
> /<>/ruby-tools/src/main/java/de/saumya/mojo/gems/spec/yaml/YamlGemSpecificationIO.java:[8,26]
>  cannot find symbol
>   symbol:   class Loader
>   location: package org.yaml.snakeyaml
> [INFO] 2 errors 
> [INFO] -
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] JRuby Maven Mojos .. SUCCESS [  0.139 
> s]
> [INFO] Mojo Parent ..

Bug#844851: gnokii: FTBFS: gcc: error: .specs: No such file or directory

[Lucas Nussbaum]

Source: gnokii
Version: 0.6.30+dfsg-1.1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> /bin/bash ../libtool   --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
> -I../include-I../include -I./ -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/postgresql  
> -I/usr/include/mysql 
> -fdebug-prefix-map=/build/mysql-5.7-lG4h93/mysql-5.7-5.7.16=. .specs 
> -fabi-version=2 -fno-omit-frame-pointer -DMODULES_DIR=\"/usr/lib/smsd\" 
> -DLOCALEDIR=\"/usr/share/locale\" -pthread -Wall -g -fgnu89-inline -O2 -Wall 
> -Wno-pointer-sign -fvisibility=hidden -fno-strict-aliasing   -MT file.lo -MD 
> -MP -MF .deps/file.Tpo -c -o file.lo file.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../include -I../include -I./ 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/postgresql -I/usr/include/mysql 
> -fdebug-prefix-map=/build/mysql-5.7-lG4h93/mysql-5.7-5.7.16=. .specs 
> -fabi-version=2 -fno-omit-frame-pointer -DMODULES_DIR=\"/usr/lib/smsd\" 
> -DLOCALEDIR=\"/usr/share/locale\" -pthread -Wall -g -fgnu89-inline -O2 -Wall 
> -Wno-pointer-sign -fvisibility=hidden -fno-strict-aliasing -MT file.lo -MD 
> -MP -MF .deps/file.Tpo -c file.c  -fPIC -DPIC -o .libs/file.o
> gcc: error: .specs: No such file or directory
> Makefile:659: recipe for target 'file.lo' failed
> make[2]: *** [file.lo] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/gnokii_0.6.30+dfsg-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#844864: gcc-6: FTBFS: collect2: error: ld returned 1 exit status

[Lucas Nussbaum]

Source: gcc-6
Version: 6.2.1-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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/xgcc -c -nostdinc -I. -I../gcc/ada/rts 
> -I../x86_64-linux-gnu/libgnatvsn -I../x86_64-linux-gnu/libgnatprj -B../gcc/ 
> -no-pie -I- /<>/build/gnattools/switch-b.adb
> echo ../../../src/libjava/classpath/lib/java/lang/PosixProcess*.class > 
> java/process-Posix.list
> echo ../../../src/libjava/classpath/lib/gnu/awt/*.class > gnu/awt.list
> mkdir -p -- gnu/awt/
> echo ../../../src/libjava/classpath/lib/gnu/classpath/*.class > 
> gnu/classpath.list
> echo ../../../src/libjava/classpath/lib/gnu/awt/j2d/*.class > gnu/awt/j2d.list
> echo ../../../src/libjava/classpath/lib/gnu/classpath/debug/*.class > 
> gnu/classpath/debug.list
> echo ../../../src/libjava/classpath/lib/gnu/classpath/toolkit/*.class > 
> gnu/classpath/toolkit.list
> yes
> echo ../../../src/libjava/classpath/lib/gnu/gcj/*.class > gnu/gcj.list
> echo ../../../src/libjava/classpath/lib/gnu/gcj/convert/*.class > 
> gnu/gcj/convert.list
> echo ../../../src/libjava/classpath/lib/gnu/gcj/io/*.class > gnu/gcj/io.list
> echo ../../../src/libjava/classpath/lib/gnu/gcj/runtime/*.class > 
> gnu/gcj/runtime.list
> echo ../../../src/libjava/classpath/lib/gnu/gcj/util/*.class > 
> gnu/gcj/util.list
> echo ../../../src/libjava/classpath/lib/gnu/java/awt/*.class > 
> gnu/java/awt.list
> checking for getcwd... mkdir -p -- gnu/java/awt/
> mkdir -p -- gnu/java/awt/
> echo ../../../src/libjava/classpath/lib/gnu/java/awt/color/*.class > 
> gnu/java/awt/color.list
> mkdir -p -- gnu/java/awt/
> 4
> echo ../../../src/libjava/classpath/lib/gnu/java/awt/dnd/*.class > 
> gnu/java/awt/dnd.list
> mkdir -p -- gnu/java/awt/font/
> no
> checking whether .eh_frame section should be read-only... echo 
> ../../../src/libjava/classpath/lib/gnu/java/awt/font/*.class > 
> gnu/java/awt/font.list
> mkdir -p -- gnu/java/awt/font/
> mkdir -p -- gnu/java/awt/font/opentype/
> echo ../../../src/libjava/classpath/lib/gnu/java/awt/font/autofit/*.class > 
> gnu/java/awt/font/autofit.list
> echo ../../../src/libjava/classpath/lib/gnu/java/awt/font/opentype/*.class > 
> gnu/java/awt/font/opentype.list
> echo ../../../src/libjava/classpath/lib/gnu/java/awt/image/*.class > 
> gnu/java/awt/image.list
> echo 
> ../../../src/libjava/classpath/lib/gnu/java/awt/font/opentype/truetype/*.class
>  > gnu/java/awt/font/opentype/truetype.list
> echo ../../../src/libjava/classpath/lib/gnu/java/awt/java2d/*.class > 
> gnu/java/awt/java2d.list
> echo ../../../src/libjava/classpath/lib/gnu/java/awt/peer/*.class > 
> gnu/java/awt/peer.list
> echo ../../../src/libjava/classpath/lib/gnu/java/awt/print/*.class > 
> gnu/java/awt/print.list
> mkdir -p -- gnu/java/awt/peer/
> echo ../../../src/libjava/classpath/lib/gnu/java/io/*.class > gnu/java/io.list
> echo ../../../src/libjava/classpath/lib/gnu/java/awt/peer/headless/*.class > 
> gnu/java/awt/peer/headless.list
> echo ../../../src/libjava/classpath/lib/gnu/java/lang/*.class > 
> gnu/java/lang.list
> echo ../../../src/libjava/classpath/lib/gnu/java/lang/reflect/*.class > 
> gnu/java/lang/reflect.list
> libtool: compile:  /<>/build/./gcc/gcj 
> -B/<>/build/x86_64-linux-gnu/libjava/ 
> -B/<>/build/./gcc/ -B/usr/x86_64-linux-gnu/bin/ 
> -B/usr/x86_64-linux-gnu/lib/ -isystem /usr/x86_64-linux-gnu/include -isystem 
> /usr/x86_64-linux-gnu/sys-include -isystem /<>/build/sys-include 
> -fomit-frame-pointer -Usun -fclasspath= 
> -fbootclasspath=../../../src/libjava/classpath/lib --encoding=UTF-8 
> -Wno-deprecated -fbootstrap-classes -g -O2 -c 
> -fsource-filename=../../../src/libjava/java/lang/Object.java 
> ../../../src/libjava/classpath/lib/java/lang/Object.class  -fPIC -o 
> java/lang/.libs/Object.o
> echo ../../../src/libjava/classpath/lib/gnu/java/locale/*.class > 
> gnu/java/locale.list
> libtool: compile:  /<>/build/./gcc/gcj 
> -B/<>/build/x86_64-linux-gnu/libjava/ 
> -B/<>/build/./gcc/ -B/usr/x86_64-linux-gnu/bin/ 
> -B/usr/x86_64-linux-gnu/lib/ -isystem /usr/x86_64-linux-gnu/include -isystem 
> /usr/x86_64-linux-gnu/sys-include -isystem /<>/build/sys-include 
> -fomit-frame-pointer -Usun -fclasspath= 
> -fbootclasspath=../../../src/libjava/classpath/lib --encoding=UTF-8 
> -Wno-deprecated -fbootstrap-classes -g -O2 -c 
> -fsource-filename=../../../src/libjava/java/lang/Class.java 
> ../../../src/libjava/classpath/lib/java/lang/Class.class  -fPIC -o 
> java/lang/.libs/Class.o
> ech

Bug#844867: knot: FTBFS: ld: cannot find -lncurses

[Lucas Nussbaum]

Source: knot
Version: 2.3.2-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> /bin/bash ../libtool  --tag=CC   --mode=link gcc  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -DNDEBUG -Wall -Werror=format-security 
> -Werror=implicit -Wstrict-prototypes  -Wl,-z,relro -Wl,-z,now -Wl,--as-needed 
> -o knotd utils/knotd/knotd-main.o libknotd.la -lurcu -ldl -lpthread -lm 
> libtool: link: gcc -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall -DNDEBUG 
> -Wall -Werror=format-security -Werror=implicit -Wstrict-prototypes -Wl,-z 
> -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed -o .libs/knotd 
> utils/knotd/knotd-main.o  ./.libs/libknotd.a -lsystemd 
> /<>/src/.libs/libknot.so -llmdb 
> /<>/src/dnssec/.libs/libdnssec.so -lgnutls -lnettle -ljansson 
> /<>/src/zscanner/.libs/libzscanner.so -lurcu -ldl -lpthread -lm
> libtool: link: gcc -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall -DNDEBUG 
> -Wall -Werror=format-security -Werror=implicit -Wstrict-prototypes -Wl,-z 
> -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed -o .libs/kzonecheck 
> utils/kzonecheck/main.o utils/kzonecheck/zone_check.o  ./.libs/libknotd.a 
> -lsystemd /<>/src/.libs/libknot.so -llmdb 
> /<>/src/dnssec/.libs/libdnssec.so -lgnutls -lnettle -ljansson 
> /<>/src/zscanner/.libs/libzscanner.so -lurcu -ldl -lpthread -lm
> libtool: link: gcc -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall -DNDEBUG 
> -Wall -Werror=format-security -Werror=implicit -Wstrict-prototypes -Wl,-z 
> -Wl,relro -Wl,-z -Wl,now -Wl,--as-needed -o .libs/knotc 
> utils/knotc/knotc-commands.o utils/knotc/knotc-estimator.o 
> utils/knotc/knotc-interactive.o utils/knotc/knotc-process.o 
> utils/knotc/knotc-main.o  ./.libs/libknotd.a -lsystemd 
> /<>/src/zscanner/.libs/libzscanner.so -lurcu ./.libs/libknotus.a 
> -lidn /<>/src/.libs/libknot.so -llmdb 
> /<>/src/dnssec/.libs/libdnssec.so -lgnutls -lnettle -ljansson 
> -ledit -lncurses -lbsd -ldl -lpthread -lm
> /usr/bin/ld: cannot find -lncurses
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/knot_2.3.2-1_unstable.log

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

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

Bug#844857: libneo4j-client: FTBFS: ld: cannot find -lncurses

[Lucas Nussbaum]

Source: libneo4j-client
Version: 1.2.1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> /bin/bash ../../libtool  --tag=CC   --mode=link gcc  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -std=gnu11 -fvisibility=hidden -pipe -Wall -W -Werror 
> -Wno-unused-parameter -Wno-missing-field-initializers -Wpointer-arith 
> -Wstrict-prototypes -Wcast-qual -Wcast-align -Wno-error=unused-function 
> -Wno-error=unused-variable -Wno-error=deprecated-declarations  -Wl,-z,relro 
> -Wl,-z,now -o neo4j-client neo4j_client-neo4j-client.o 
> neo4j_client-authentication.o neo4j_client-batch.o 
> neo4j_client-colorization.o neo4j_client-commands.o neo4j_client-connect.o 
> neo4j_client-evaluate.o neo4j_client-interactive.o neo4j_client-options.o 
> neo4j_client-readpass.o neo4j_client-render.o neo4j_client-state.o 
> neo4j_client-util.o neo4j_client-verification.o 
> ../../src/lib/libneo4j-client.la -ledit -lncurses -lbsd -lcypher-parser -lbsd 
> libtool: link: gcc -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -std=gnu11 
> -fvisibility=hidden -pipe -Wall -W -Werror -Wno-unused-parameter 
> -Wno-missing-field-initializers -Wpointer-arith -Wstrict-prototypes 
> -Wcast-qual -Wcast-align -Wno-error=unused-function 
> -Wno-error=unused-variable -Wno-error=deprecated-declarations -Wl,-z 
> -Wl,relro -Wl,-z -Wl,now -o .libs/neo4j-client neo4j_client-neo4j-client.o 
> neo4j_client-authentication.o neo4j_client-batch.o 
> neo4j_client-colorization.o neo4j_client-commands.o neo4j_client-connect.o 
> neo4j_client-evaluate.o neo4j_client-interactive.o neo4j_client-options.o 
> neo4j_client-readpass.o neo4j_client-render.o neo4j_client-state.o 
> neo4j_client-util.o neo4j_client-verification.o  
> ../../src/lib/.libs/libneo4j-client.so -ledit -lncurses -lcypher-parser -lbsd 
> -pthread
> /usr/bin/ld: cannot find -lncurses
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/libneo4j-client_1.2.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#844858: oggvideotools: FTBFS: decoderTest.cpp:19:41: error: 'memset' was not declared in this scope

[Lucas Nussbaum]

Source: oggvideotools
Version: 0.9.1-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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/base/test && /usr/bin/c++   
> -DHAVE_CONFIG_H -DPACKAGE_STRING=\"oggvideotools-0.9.1\" -DWITH_GD2LIB 
> -D_FILE_OFFSET_BITS=64 -I/<>/obj-x86_64-linux-gnu 
> -I/<>/src -I/<>/src/base 
> -I/<>/src/effect -I/<>/src/misc 
> -I/<>/src/ovt_kate -I/<>/src/ovt_vorbis 
> -I/<>/src/ovt_theora -I/<>/src/main 
> -I/<>/src/libresample  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -Wno-write-strings 
> -O0 -g --std=c++0x -fPIC -Wall -Wextra -o 
> CMakeFiles/decoderTest.dir/decoderTest.cpp.o -c 
> /<>/src/base/test/decoderTest.cpp
> /<>/src/base/test/decoderTest.cpp: In function 'int main(int, 
> char**)':
> /<>/src/base/test/decoderTest.cpp:19:41: error: 'memset' was not 
> declared in this scope
>  memset(, 0, sizeof(OggHeader));
>  ^
> /<>/src/base/test/decoderTest.cpp:9:14: warning: unused 
> parameter 'argc' [-Wunused-parameter]
>  int main(int argc, char* argv[])
>   ^~~~
> /<>/src/base/test/decoderTest.cpp:9:31: warning: unused 
> parameter 'argv' [-Wunused-parameter]
>  int main(int argc, char* argv[])
>^
> src/base/test/CMakeFiles/decoderTest.dir/build.make:65: recipe for target 
> 'src/base/test/CMakeFiles/decoderTest.dir/decoderTest.cpp.o' failed
> make[3]: *** [src/base/test/CMakeFiles/decoderTest.dir/decoderTest.cpp.o] 
> Error 1

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/oggvideotools_0.9.1-2_unstable.log

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

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

Bug#844865: nco: FTBFS: ncap_lex.l:60:60: fatal error: ncap_yacc.h: No such file or directory

[Lucas Nussbaum]

Source: nco
Version: 4.6.2-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -I../..   -I/usr/include -I/usr/include/hdf5/serial 
> -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include -I/usr/include  -g -O2 
> -fdebug-prefix-map=/<>=. 
> -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
> -Werror=format-security -fopenmp -std=c99 -D_BSD_SOURCE -D_POSIX_SOURCE -c -o 
> ncap_lex.o ncap_lex.c
> In file included from /usr/include/stdio.h:27:0,
>  from ncap_lex.c:38:
> /usr/include/features.h:148:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>  # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE"
>^~~
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -I/usr/include 
> -I/usr/include/hdf5/serial -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include 
> -I/usr/include -g -O2 -fdebug-prefix-map=/<>=. 
> -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
> -Werror=format-security -fopenmp -std=c99 -D_BSD_SOURCE -D_POSIX_SOURCE -c 
> nco_cnf_typ.c  -fPIC -DPIC -o .libs/nco_cnf_typ.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -I/usr/include 
> -I/usr/include/hdf5/serial -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include 
> -I/usr/include -g -O2 -fdebug-prefix-map=/<>=. 
> -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
> -Werror=format-security -fopenmp -std=c99 -D_BSD_SOURCE -D_POSIX_SOURCE -c 
> nco_cln_utl.c  -fPIC -DPIC -o .libs/nco_cln_utl.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -I/usr/include 
> -I/usr/include/hdf5/serial -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include 
> -I/usr/include -g -O2 -fdebug-prefix-map=/<>=. 
> -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
> -Werror=format-security -fopenmp -std=c99 -D_BSD_SOURCE -D_POSIX_SOURCE -c 
> nco_att_utl.c  -fPIC -DPIC -o .libs/nco_att_utl.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -I/usr/include 
> -I/usr/include/hdf5/serial -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include 
> -I/usr/include -g -O2 -fdebug-prefix-map=/<>=. 
> -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
> -Werror=format-security -fopenmp -std=c99 -D_BSD_SOURCE -D_POSIX_SOURCE -c 
> nco_rgr.c  -fPIC -DPIC -o .libs/nco_rgr.o
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -I/usr/include 
> -I/usr/include/hdf5/serial -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include 
> -I/usr/include -g -O2 -fdebug-prefix-map=/<>=. 
> -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
> -Werror=format-security -fopenmp -std=c99 -D_BSD_SOURCE -D_POSIX_SOURCE -c 
> nco_mta.c  -fPIC -DPIC -o .libs/nco_mta.o
> In file included from /usr/include/math.h:26:0,
>  from nco_att_utl.h:21,
>  from nco_att_utl.c:10:
> /usr/include/features.h:148:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>  # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE"
>^~~
> In file included from /usr/include/math.h:26:0,
>  from nco_cnf_typ.h:17,
>  from nco_cnf_typ.c:10:
> /usr/include/features.h:148:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>  # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE"
>^~~
> In file included from /usr/include/limits.h:25:0,
>  from 
> /usr/lib/gcc/x86_64-linux-gnu/6/include-fixed/limits.h:168,
>  from 
> /usr/lib/gcc/x86_64-linux-gnu/6/include-fixed/syslimits.h:7,
>  from 
> /usr/lib/gcc/x86_64-linux-gnu/6/include-fixed/limits.h:34,
>  from nco_rgr.h:17,
>  from nco_rgr.c:10:
> /usr/include/features.h:148:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>  # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE"
>^~~
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -I/usr/include 
> -I/usr/include/hdf5/serial -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include 
> -I/usr/include -g -O2 -fdebug-prefix-map=/<>=. 
> -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
> -Werror=format-security -fopenmp -std=c99 -D_BSD_SOURCE -D_POSIX_

Bug#844862: linux-atm: FTBFS: time.h:9:8: error: redefinition of 'struct timespec'

[Lucas Nussbaum]

Source: linux-atm
Version: 1:2.5.1-1.6
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -I../.. -I./../q2931 -I./../saal -I.  -Wdate-time 
> -D_FORTIFY_SOURCE=2  -I../../src/include -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -fno-strict-aliasing -Wall -Wshadow -Wpointer-arith 
> -Wwrite-strings -Wstrict-prototypes -MT zntune.o -MD -MP -MF .deps/zntune.Tpo 
> -c -o zntune.o zntune.c
> In file included from /usr/include/linux/atm_zatm.h:17:0,
>  from zntune.c:17:
> /usr/include/linux/time.h:9:8: error: redefinition of 'struct timespec'
>  struct timespec {
> ^~~~
> In file included from /usr/include/x86_64-linux-gnu/sys/select.h:45:0,
>  from /usr/include/x86_64-linux-gnu/sys/types.h:219,
>  from /usr/include/stdlib.h:275,
>  from zntune.c:9:
> /usr/include/time.h:120:8: note: originally defined here
>  struct timespec
> ^~~~
> In file included from /usr/include/linux/atm_zatm.h:17:0,
>  from zntune.c:17:
> /usr/include/linux/time.h:15:8: error: redefinition of 'struct timeval'
>  struct timeval {
> ^~~
> In file included from /usr/include/x86_64-linux-gnu/sys/select.h:47:0,
>  from /usr/include/x86_64-linux-gnu/sys/types.h:219,
>  from /usr/include/stdlib.h:275,
>  from zntune.c:9:
> /usr/include/x86_64-linux-gnu/bits/time.h:30:8: note: originally defined here
>  struct timeval
> ^~~
> In file included from /usr/include/linux/atm_zatm.h:17:0,
>  from zntune.c:17:
> /usr/include/linux/time.h:20:8: error: redefinition of 'struct timezone'
>  struct timezone {
> ^~~~
> In file included from zntune.c:16:0:
> /usr/include/x86_64-linux-gnu/sys/time.h:55:8: note: originally defined here
>  struct timezone
> ^~~~
> In file included from /usr/include/linux/atm_zatm.h:17:0,
>  from zntune.c:17:
> /usr/include/linux/time.h:39:8: error: redefinition of 'struct itimerval'
>  struct itimerval {
> ^
> In file included from zntune.c:16:0:
> /usr/include/x86_64-linux-gnu/sys/time.h:107:8: note: originally defined here
>  struct itimerval
> ^
> Makefile:607: recipe for target 'zntune.o' failed
> make[4]: *** [zntune.o] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/linux-atm_2.5.1-1.6_unstable.log

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

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

Bug#844854: paw: FTBFS: ld: final link failed: Nonrepresentable section on output

[Lucas Nussbaum]

Source: paw
Version: 1:2.14.04.dfsg.2-9
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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: 
> /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libkernlib.a(gshowf.o):
>  relocation R_X86_64_32S against `.rodata.str1.8' can not be used when making 
> a shared object; recompile with -fPIC
> /usr/bin/ld: final link failed: Nonrepresentable section on output
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/paw_2.14.04.dfsg.2-9_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#844853: link-grammar: FTBFS: ld: cannot find -lncurses

[Lucas Nussbaum]

Source: link-grammar
Version: 5.3.11-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> /bin/bash ../libtool  --tag=CC   --mode=link gcc  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -O3 -std=c11 -D_BSD_SOURCE -D_SVID_SOURCE 
> -D_GNU_SOURCE -D_DEFAULT_SOURCE -fno-strict-aliasing -Wl,-z,relro -Wl,-z,now 
> -Wl,-O1 -Wl,--as-needed -o link-parser link-parser.o command-line.o 
> lg_readline.o parser-utilities.o ../link-grammar/liblink-grammar.la -ledit 
> -lncurses -lbsd   -lminisat  -lstdc++ 
> libtool: link: gcc -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -O3 -std=c11 
> -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -D_DEFAULT_SOURCE 
> -fno-strict-aliasing -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,-O1 -o 
> .libs/link-parser link-parser.o command-line.o lg_readline.o 
> parser-utilities.o  -Wl,--as-needed ../link-grammar/.libs/liblink-grammar.so 
> -ledit -lncurses -lbsd -lminisat -lstdc++
> /usr/bin/ld: cannot find -lncurses
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/link-grammar_5.3.11-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#844861: wsjtx: FTBFS: ld: final link failed: Nonrepresentable section on output

[Lucas Nussbaum]

Source: wsjtx
Version: 1.1.r3496-3.2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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: libjt9.a(fano232.o): relocation R_X86_64_32 against 
> `.rodata.str1.8' can not be used when making a shared object; recompile with 
> -fPIC
> /usr/bin/ld: final link failed: Nonrepresentable section on output
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/wsjtx_1.1.r3496-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#844856: flightcrew: FTBFS: CheckSymbolExists.cxx:8:19: error: 'Q_WS_WIN' was not declared in this scope

[Lucas Nussbaum]

Source: flightcrew
Version: 0.7.2+dfsg-7
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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/c++-I/usr/include/qt4  -g -O2 
> -fdebug-prefix-map=/<>/flightcrew-0.7.2+dfsg=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2-o CMakeFiles/cmTC_aec35.dir/CheckSymbolExists.cxx.o 
> -c 
> /<>/flightcrew-0.7.2+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx
> /<>/flightcrew-0.7.2+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx:
>  In function 'int main(int, char**)':
> /<>/flightcrew-0.7.2+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx:8:19:
>  error: 'Q_WS_WIN' was not declared in this scope
>return ((int*)(_WS_WIN))[argc];
>^~~~
> CMakeFiles/cmTC_aec35.dir/build.make:65: recipe for target 
> 'CMakeFiles/cmTC_aec35.dir/CheckSymbolExists.cxx.o' failed
> make[3]: *** [CMakeFiles/cmTC_aec35.dir/CheckSymbolExists.cxx.o] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/flightcrew_0.7.2+dfsg-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#844850: pmacct: FTBFS: gcc: error: .specs: No such file or directory

[Lucas Nussbaum]

Source: pmacct
Version: 1.6.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DPACKAGE_NAME=\"pmacct\" 
> -DPACKAGE_TARNAME=\"pmacct\" -DPACKAGE_VERSION=\"1.6.0\" 
> -DPACKAGE_STRING=\"pmacct\ 1.6.0\" -DPACKAGE_BUGREPORT=\"pa...@pmacct.net\" 
> -DPACKAGE_URL=\"\" -DPACKAGE=\"pmacct\" -DVERSION=\"1.6.0\" -DSTDC_HEADERS=1 
> -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
> -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
> -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DCOMPILE_ARGS=\"\ 
> \'--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\'\ 
> \'--enable-mmap\'\ \'--enable-pgsql\'\ 
> \'--with-pgsql-includes=/usr/include/postgresql\'\ \'--enable-mysql\'\ 
> \'--enable-sqlite3\'\ \'--enable-ipv6\'\ \'--enable-v4-mapped\'\ 
> \'--enable-64bit\'\ \'--enable-threads\'\ \'--enable-jansson\'\ 
> \'--enable-geoip\'\ \'--enable-rabbitmq\'\ \'--enable-kafka\'\ 
> \'--enable-nflog\'\ \'build_alias=x86_64-linux-gnu\'\ \'CFLAGS=-g\ -O2\ 
> -fdebug-prefix-map=/<>=.\ -fstack-protector-strong\ -Wformat\ 
> -Werror=format-security\'\ \'LDFLAGS=-Wl,-z,relro\'\ \'CPPFLAGS=-Wdate-time\ 
> -D_FORTIFY_SOURCE=2\'\" -DPROGNAME=1 -DIM_LITTLE_ENDIAN=1 -DHAVE_L2=1 
> -DHAVE_INET_PTON=1 -DHAVE_INET_NTOP=1 -DENABLE_IPV6=1 -DHAVE_PCAP_H=1 
> -DHAVE_LIBPCAP=1 -DPCAP_7=1 -DPCAP_NOBPF=1 -DPCAP_TYPE_linux=1 -DWITH_MYSQL=1 
> -DWITH_PGSQL=1 -DWITH_SQLITE3=1 -DWITH_RABBITMQ=1 -DWITH_KAFKA=1 
> -DWITH_GEOIP=1 -DWITH_JANSSON=1 -DHAVE_LIBJANSSON=1 -DHAVE_DLOPEN=1 
> -DHAVE_ZLIB=1 -DSTDC_HEADERS=1 -DHAVE_SYS_WAIT_H=1 -DHAVE_GETOPT_H=1 
> -DHAVE_SYS_SELECT_H=1 -DHAVE_SYS_TIME_H=1 -DHAVE_U_INT64_T=1 
> -DHAVE_U_INT32_T=1 -DHAVE_U_INT16_T=1 -DHAVE_U_INT8_T=1 -DHAVE_UINT64_T=1 
> -DHAVE_UINT32_T=1 -DHAVE_UINT16_T=1 -DHAVE_UINT8_T=1 -DHAVE_64BIT_COUNTERS=1 
> -DENABLE_THREADS=1 -D_XOPEN_SOURCE=600 -D_GNU_SOURCE=1 -DWITH_NFLOG=1 
> -DRETSIGTYPE=void -DHAVE_VSNPRINTF=1 -DHAVE_MALLOPT=1 
> -DHAVE_JSON_OBJECT_UPDATE_MISSING=1 -DHAVE_TDESTROY=1 -I.   -Wdate-time 
> -D_FORTIFY_SOURCE=2 -I/usr/include/   -I/usr/include/mysql 
> -fdebug-prefix-map=/build/mysql-5.7-lG4h93/mysql-5.7-5.7.16=. .specs 
> -fabi-version=2 -fno-omit-frame-pointer -I/usr/include/postgresql -O2 -g 
> -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security  -c -o libdaemons_la-signals.lo `test -f 'signals.c' 
> || echo './'`signals.c
> libtool: compile:  gcc -DPACKAGE_NAME=\"pmacct\" -DPACKAGE_TARNAME=\"pmacct\" 
> -DPACKAGE_VERSION=\"1.6.0\" "-DPACKAGE_STRING=\"pmacct 1.6.0\"" 
> -DPACKAGE_BUGREPORT=\"pa...@pmacct.net\" -DPACKAGE_URL=\"\" 
> -DPACKAGE=\"pmacct\" -DVERSION=\"1.6.0\" -DSTDC_HEADERS=1 
> -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
> -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
> -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" "-DCOMPILE_ARGS=\" 
> '--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' '--enable-mmap' '--enable-pgsql' 
> '--with-pgsql-includes=/usr/include/postgresql' '--enable-mysql' 
> '--enable-sqlite3' '--enable-ipv6' '--enable-v4-mapped' '--enable-64bit' 
> '--enable-threads' '--enable-jansson' '--enable-geoip' '--enable-rabbitmq' 
> '--enable-kafka' '--enable-nflog' 'build_alias=x86_64-linux-gnu' 'CFLAGS=-g 
> -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security' 'LDFLAGS=-Wl,-z,relro' 'CPPFLAGS=-Wdate-time 
> -D_FORTIFY_SOURCE=2'\"" -DPROGNAME=1 -DIM_LITTLE_ENDIAN=1 -DHAVE_L2=1 
> -DHAVE_INET_PTON=1 -DHAVE_INET_NTOP=1 -DENABLE_IPV6=1 -DHAVE_PCAP_H=1 
> -DHAVE_LIBPCAP=1 -DPCAP_7=

Bug#844852: lua-dbi: FTBFS: cc: error: .specs: No such file or directory

[Lucas Nussbaum]

Source: lua-dbi
Version: 0.5.hg5ba1dd988961-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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=lua --with lua
>dh_testdir -O--buildsystem=lua
>dh_update_autotools_config -O--buildsystem=lua
>dh_auto_configure -O--buildsystem=lua
>   make --no-print-directory -f 
> /usr/share/dh-lua/make/dh-lua.Makefile.multiple configure
> 
> Making target configure for debian/lua5.1.common.dh-lua.conf
> # .install
> Filling in debian/lua-dbi-common.install using 
> /usr/share/dh-lua/template/lib.install.in
> Adding new line: 
> Adding new line: usr/share/lua/5.1/DBI.lua
> Filling in debian/lua-dbi-common-dev.install using 
> /usr/share/dh-lua/template/dev.install.in
> Adding new line: 
> # lua_versions
> Filling in debian/lua_versions
> Adding new line: 5.1
> Target configure made
> 
> 
> Making target configure for debian/lua5.1.mysql.dh-lua.conf
> # .install
> Filling in debian/lua-dbi-mysql.install using 
> /usr/share/dh-lua/template/lib.install.in
> Adding new line: usr/lib/x86_64-linux-gnu/lua/5.1/dbdmysql.so
> Adding new line: usr/lib/x86_64-linux-gnu/liblua5.1-dbi-mysql.so.*
> Filling in debian/lua-dbi-mysql-dev.install using 
> /usr/share/dh-lua/template/dev.install.in
> Adding new line: usr/lib/x86_64-linux-gnu/liblua5.1-dbi-mysql.so
> Adding new line: usr/lib/x86_64-linux-gnu/liblua5.1-dbi-mysql.a
> Adding new line: usr/lib/x86_64-linux-gnu/pkgconfig/lua5.1-dbi-mysql.pc
> Adding new line: usr/include/lua5.1/lua-dbi-mysql.h
> # lua_versions
> Filling in debian/lua_versions
> Skipping already existing line: 5.1
> Target configure made
> 
> 
> Making target configure for debian/lua5.1.postgresql.dh-lua.conf
> # .install
> Filling in debian/lua-dbi-postgresql.install using 
> /usr/share/dh-lua/template/lib.install.in
> Adding new line: usr/lib/x86_64-linux-gnu/lua/5.1/dbdpostgresql.so
> Adding new line: usr/lib/x86_64-linux-gnu/liblua5.1-dbi-postgresql.so.*
> Filling in debian/lua-dbi-postgresql-dev.install using 
> /usr/share/dh-lua/template/dev.install.in
> Adding new line: usr/lib/x86_64-linux-gnu/liblua5.1-dbi-postgresql.so
> Adding new line: usr/lib/x86_64-linux-gnu/liblua5.1-dbi-postgresql.a
> Adding new line: usr/lib/x86_64-linux-gnu/pkgconfig/lua5.1-dbi-postgresql.pc
> Adding new line: usr/include/lua5.1/lua-dbi-postgresql.h
> # lua_versions
> Filling in debian/lua_versions
> Skipping already existing line: 5.1
> Target configure made
> 
> 
> Making target configure for debian/lua5.1.sqlite3.dh-lua.conf
> # .install
> Filling in debian/lua-dbi-sqlite3.install using 
> /usr/share/dh-lua/template/lib.install.in
> Adding new line: usr/lib/x86_64-linux-gnu/lua/5.1/dbdsqlite3.so
> Adding new line: usr/lib/x86_64-linux-gnu/liblua5.1-dbi-sqlite3.so.*
> Filling in debian/lua-dbi-sqlite3-dev.install using 
> /usr/share/dh-lua/template/dev.install.in
> Adding new line: usr/lib/x86_64-linux-gnu/liblua5.1-dbi-sqlite3.so
> Adding new line: usr/lib/x86_64-linux-gnu/liblua5.1-dbi-sqlite3.a
> Adding new line: usr/lib/x86_64-linux-gnu/pkgconfig/lua5.1-dbi-sqlite3.pc
> Adding new line: usr/include/lua5.1/lua-dbi-sqlite3.h
> # lua_versions
> Filling in debian/lua_versions
> Skipping already existing line: 5.1
> Target configure made
> 
>dh_auto_build -O--buildsystem=lua
>   make --no-print-directory -f 
> /usr/share/dh-lua/make/dh-lua.Makefile.multiple build
> 
> Making target build for debian/lua5.1.common.dh-lua.conf
> Target build made
> 
> 
> Making target build for debian/lua5.1.mysql.dh-lua.conf
> libtool --silent --tag=CC --mode=compile cc -c -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
> -I/usr//include/lua5.1 -I/usr/include/mysql 
> -fdebug-prefix-map=/build/mysql-5.7-lG4h93/mysql-5.7-5.7.16=. .specs 
> -fabi-version=2 -fno-omit-frame-pointer -I . -Wall -Wextra -o 
> /<>/5.1-dbi.mysql/dbd/common.lo dbd/common.c 
> cc: error: .specs: No such file or directory
> /usr/share/dh-lua/make/dh-lua.Makefile.single:436: recipe for target 
> '/<>/5.1-dbi.mysql/dbd/common.lo' failed
> make[2]: *** [/<>/5.1-dbi.mysql/dbd/common.lo] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/lua-dbi_0.5.hg5ba1dd988961-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#844869: isatapd: FTBFS: ip.h:85:8: error: redefinition of 'struct iphdr'

[Lucas Nussbaum]

Source: isatapd
Version: 0.9.7-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o tunnel.o tunnel.c
> In file included from /usr/include/linux/if_tunnel.h:6:0,
>  from tunnel.c:23:
> /usr/include/linux/ip.h:85:8: error: redefinition of 'struct iphdr'
>  struct iphdr {
> ^
> In file included from tunnel.c:21:0:
> /usr/include/netinet/ip.h:44:8: note: originally defined here
>  struct iphdr
> ^
> Makefile:353: recipe for target 'tunnel.o' failed
> make[3]: *** [tunnel.o] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/isatapd_0.9.7-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.