Bug#830985: marked as done (tulip: error while loading shared libraries: libbfd-2.26-system.so)

[Debian Bug Tracking System]

Your message dated Wed, 20 Jul 2016 09:29:59 +0200 (CEST)
with message-id 
<1430128911.244519590.1468999799219.javamail.r...@zimbra39-e7.priv.proxad.net>
and subject line #830985 fixed by binNMU
has caused the Debian Bug report #830985,
regarding tulip: error while loading shared libraries: libbfd-2.26-system.so
to be marked as done.

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

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


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

Package: tulip
Version: 4.8.0dfsg-2+b3
Severity: important

Seems like tulip depends on libbfd-2.26-system.so, but only 
libbfd-2.26-system.so.1 is available on my system.

% tulip
tulip: error while loading shared libraries: libbfd-2.26-system.so: cannot open 
shared object file: No such file or directory

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

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

Versions of packages tulip depends on:
ii  binutils  2.26.1-1
ii  fonts-dejavu-core 2.35-1
ii  fonts-font-awesome4.6.3~dfsg-1
ii  libc6 2.23-1
ii  libfreetype6  2.6.3-3+b1
ii  libftgl2  2.1.3~rc5-4+nmu1+b1
ii  libgcc1   1:6.1.1-9
ii  libgl1-mesa-glx [libgl1]  11.2.2-1
ii  libglew1.13   1.13.0-2
ii  libgzstream-tulip-4.8-0   4.8.0dfsg-2+b3
ii  libjpeg62-turbo   1:1.5.0-1
ii  libogdf-tulip-4.8-0   4.8.0dfsg-2+b3
ii  libpng16-16   1.6.23-1
ii  libpython2.7  2.7.12-1
ii  libqt5core5a  5.6.1+dfsg-3
ii  libqt5gui55.6.1+dfsg-3
ii  libqt5network55.6.1+dfsg-3
ii  libqt5opengl5 5.6.1+dfsg-3
ii  libqt5webkit5 5.6.1+dfsg-4
ii  libqt5widgets55.6.1+dfsg-3
ii  libqt5xml55.6.1+dfsg-3
ii  libqt5xmlpatterns55.6.1-2
ii  libquazip-tulip-4.8-1 4.8.0dfsg-2+b3
ii  libqxt-tulip-4.8-04.8.0dfsg-2+b3
ii  libstdc++66.1.1-9
ii  libtess2-tulip-4.84.8.0dfsg-2+b3
ii  libtulip-core-4.8 4.8.0dfsg-2+b3
ii  libtulip-gui-4.8  4.8.0dfsg-2+b3
ii  libtulip-ogdf-4.8 4.8.0dfsg-2+b3
ii  libtulip-ogl-4.8  4.8.0dfsg-2+b3
ii  libtulip-python-4.8   4.8.0dfsg-2+b3
ii  libyajl-tulip-4.8-2   4.8.0dfsg-2+b3
ii  zlib1g1:1.2.8.dfsg-2+b1

tulip recommends no packages.

tulip suggests no packages.
--- End Message ---
--- Begin Message ---
Problem now fixed in unstable--- End Message ---

Bug#830343: Taking over cvxopt into Debian Science maintenance

[Soeren Sonnenburg]

Thanks. Please do.

On Wed, 2016-07-20 at 08:18 +0200, Andreas Tille wrote:
> Hi Sören,
> 
> even if bug #830343 was fixed in NMU this package has seen only NMUs in
> last years and looks unmaintained.  I'll create a Git repository in
> Debian Science repository and move it to Debian Science team
> maintenance.  If you do not insist I assume you agree with this
> procedure.
> 
> Kind regatds
> 
>Andreas.
> 

Bug#830343: Taking over cvxopt into Debian Science maintenance

[Andreas Tille]

Hi

thanks for the quick confirmation.  I've just created a Git repository
of latest upstream and will push this soon.

Kind regards

   Andreas.

On Wed, Jul 20, 2016 at 09:30:29AM +0200, Soeren Sonnenburg wrote:
> Thanks. Please do.
> 
> On Wed, 2016-07-20 at 08:18 +0200, Andreas Tille wrote:
> > Hi Sören,
> > 
> > even if bug #830343 was fixed in NMU this package has seen only NMUs in
> > last years and looks unmaintained.  I'll create a Git repository in
> > Debian Science repository and move it to Debian Science team
> > maintenance.  If you do not insist I assume you agree with this
> > procedure.
> > 
> > Kind regatds
> > 
> >Andreas.
> > 
> 
> 
> 

-- 
http://fam-tille.de

Bug#830729: [pkg-go] Bug#830729: golang-github-mitchellh-go-homedir: FTBFS: homedir_test.go:44: "/home/lamby" != "~"

[Chris Lamb]

> My _hunch_ is that whatever you're using to build (pbuilder perhaps?)
> is running as your user ("lamby") but not including "/etc/passwd" from
> your host

It is running as my user and /etc/passwd includes:

  lamby:x:1000:1000:,,,:/home/lamby:/bin/bash

.. so, alas, that's not the problem.

(am using Docker, not pbuilder)


Regards,

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

Processed: Re: ovirt-guest-agent service still doesn't start

[Debian Bug Tracking System]

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

> severity 811481 serious
Bug #811481 [ovirt-guest-agent] ovirt-guest-agent service still doesn't start
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#831857: libupnp: write files via POST

[Salvatore Bonaccorso]

Source: libupnp
Version: 1:1.6.17-1
Severity: grave
Tags: security upstream
Justification: user security hole

Hi

See http://www.openwall.com/lists/oss-security/2016/07/18/13 and
https://twitter.com/mjg59/status/755062278513319936 .

Proposed fix:
https://github.com/mjg59/pupnp-code/commit/be0a01bdb83395d9f3a5ea09c1308a4f1a972cbd

Regards,
Salvatore

Bug#831823: marked as done (cowbuilder: doesn't copy on write when using eatmydata)

[Debian Bug Tracking System]

Your message dated Wed, 20 Jul 2016 09:58:01 +
with message-id 
and subject line Bug#831823: fixed in pbuilder 0.225.2
has caused the Debian Bug report #831823,
regarding cowbuilder: doesn't copy on write when using eatmydata
to be marked as done.

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

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


-- 
831823: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831823
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cowbuilder
Version: 0.80
Severity: grave
Tags: security

I enabled eatmydata by adding EATMYDATA=eatmydata to my ~/.pbuilderrc,
and the result is that copy-on-write no longer works, making any modifications
persistent:

eatmydata enabled

emilio@tatooine:~$ sudo cowbuilder --login 
root@tatooine:/# echo asdf > /etc/apt/sources.list
root@tatooine:/# logout
emilio@tatooine:~$ sudo cowbuilder --login 
root@tatooine:/# cat /etc/apt/sources.list
asdf

Note how it has overwritten sources.list even though --save-after-login
wasn't passed. It also overwrites files during a package build, which
is a big problem.

Now, with eatmydata disabled:

First, restore sources.list:

emilio@tatooine:~$ sudo cowbuilder --login --save-after-login
root@tatooine:/# cat /etc/apt/sources.list
asdf
root@tatooine:/# echo "deb http://ftp.es.debian.org/debian/ unstable main" > 
/etc/apt/sources.list
root@tatooine:/# logout

It is restored. Now, let's try to overwrite it without --save-after-login:

emilio@tatooine:~$ sudo cowbuilder --login 
root@tatooine:/# cat /etc/apt/sources.list
deb http://ftp.es.debian.org/debian/ unstable main
root@tatooine:/# echo asdf > /etc/apt/sources.list
root@tatooine:/# logout
emilio@tatooine:~$ sudo cowbuilder --login
root@tatooine:/# cat /etc/apt/sources.list
deb http://ftp.es.debian.org/debian/ unstable main
root@tatooine:/# 

It isn't overwritten.

Cheers,
Emilio

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

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

Versions of packages cowbuilder depends on:
ii  cowdancer  0.80
ii  libc6  2.23-1
ii  pbuilder   0.225.1

cowbuilder recommends no packages.

cowbuilder suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pbuilder
Source-Version: 0.225.2

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

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

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated pbuilder package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 20 Jul 2016 07:49:08 +
Source: pbuilder
Binary: pbuilder
Architecture: source
Version: 0.225.2
Distribution: unstable
Urgency: high
Maintainer: Debian pbuilder maintenance team 

Changed-By: Mattia Rizzolo 
Description:
 pbuilder   - personal package builder for Debian packages
Closes: 831823
Changes:
 pbuilder (0.225.2) unstable; urgency=high
 .
   [ James Clarke ]
   * modules: Don't trash CHROOTEXEC when using eatmydata.  Closes: #831823
Checksums-Sha1:
 f9b708c0e3fe2ff4093e7bcd8dce60cf578fb685 1815 pbuilder_0.225.2.dsc
 f457b3e8ec4b371a9c33b968f2f24e3af2942512 307628 pbuilder_0.225.2.tar.xz
Checksums-Sha256:
 8d7b25bfb4a7f45f03dccdb6456c0512bac12f786d678400ef5708f703940b83 1815 
pbuilder_0.225.2.dsc
 f99cdaf360238f10871199e285496cfd22456e51e69094cd72eb34ab1dde357a 307628 
pbuilder_0.225.2.tar.xz
Files:
 452a38c1f4d165fd297a57d93e5c6bb1 1815 devel extra pbuilder_0.225.2.dsc
 094de83ee5f278581c26b2d93b000c91 307628 devel extra pbuilder_0.225.2.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJXjy7WAAoJEEsEP825REVAg2gP/iT9U1Vl+L6Re+TKV6uwwJ6W
g/ie9GL8ybYQA5P0d5N1dhGBoL4q86LLqrrjZLPdr0yJ8CxzK6LpgCdYe3x7DkL3
NMz5gs33M2b+4hcZOHTYQfFaQSG1HVRL9pV+We5+GhLwUGiKnN3Voegjgq5n69MQ
7BTzBdqY3OTE9eM/knmFu1sox357CnVLMYy0p6c2GPQ2xW+7W0wX+ZoK1xZHr8QS

Bug#812272: laserboy: FTBFS with GCC 6: error: switch quantity not an integer

[Graham Inggs]

Control: tags 812272 patch

The attached patch fixes the FTBFS

Description: Fix switch quantity not an integer with GCC 6
 This fixes a FTBFS with the following, and similar, errors:
 src/LaserBoy_vertex.hpp:696:40: error: switch quantity not an integer
 switch(abs(header.signal_id[5]))
Bug-Debian: https://bugs.debian.org/812272
Author: Graham Inggs 
Last-Update: 2016-07-20
--- a/src/LaserBoy_vertex.hpp
+++ b/src/LaserBoy_vertex.hpp
@@ -715,7 +715,7 @@
 out.put((color & 0xff00) >> 8);
 }
 //
-switch(abs(header.signal_id[5])) // sign indicates polarity of chanel data
+switch((int)abs(header.signal_id[5])) // sign indicates polarity of chanel data
 {
 case LASERBOY_NO_SIGNAL:
 out.put(0x00);
@@ -876,7 +876,7 @@
 out.put((color & 0xff00) >> 8);
 }
 //
-switch(abs(header.signal_id[5])) // sign indicates polarity of channel data
+switch((int)abs(header.signal_id[5])) // sign indicates polarity of channel data
 {
 case LASERBOY_NO_SIGNAL:
 out.put(0x00);
--- a/src/LaserBoy_space.cpp
+++ b/src/LaserBoy_space.cpp
@@ -3342,7 +3342,7 @@
 //
 string LaserBoy_space::LaserBoy_wave_signal_id_to_name(const short& signal_id) const
 {
-switch(abs(signal_id)) // sign indicates polarity of channel data
+switch((int)abs(signal_id)) // sign indicates polarity of channel data
 {
 default:
 case LASERBOY_NO_SIGNAL:

Processed: laserboy: FTBFS with GCC 6: error: switch quantity not an integer

[Debian Bug Tracking System]

Processing control commands:

> tags 812272 patch
Bug #812272 [laserboy] laserboy: FTBFS with GCC 6: error: switch quantity not 
an integer
Added tag(s) patch.

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

Processed: Re: Bug#811766: fixed in ggcov 0.9-11

[Debian Bug Tracking System]

Processing control commands:

> fixed 811776 0.9-11
Bug #811776 {Done: Alastair McKinstry } 
[ggcov] ggcov: FTBFS with GCC 6: narrowing conversion
Marked as fixed in versions ggcov/0.9-11.
> reopen -1
Bug #811766 {Done: Alastair McKinstry } [scim-unikey] 
scim-unikey: FTBFS with GCC 6: narrowing conversion
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions ggcov/0.9-11.

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

Bug#811847: marked as done (givaro: FTBFS with GCC 6: no match for)

[Debian Bug Tracking System]

Your message dated Wed, 20 Jul 2016 11:00:09 +
with message-id 
and subject line Bug#811847: fixed in givaro 4.0.1-1
has caused the Debian Bug report #811847,
regarding givaro: FTBFS with GCC 6: no match for
to be marked as done.

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

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


-- 
811847: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811847
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: givaro
Version: 3.7.2-1.1
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-no-match

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

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

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

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> g++ -DHAVE_CONFIG_H -I. -I..  -I..   -I../src/kernel/system 
> -I../src/kernel/memory -I../src/kernel/zpz -I../src/kernel/integer 
> -I../src/kernel -I../src/library/poly1 -I../src/kernel/bstruct 
> -I../src/library/tools -Wdate-time -D_FORTIFY_SOURCE=2 -O0 -Wall -g -DNDEBUG 
> -UGIVARO_DEBUG -UDEBUG -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o test-ffarith.o test-ffarith.C
> test-ffarith.C: In instantiation of 'int TestOneField(const Field&, int, 
> float) [with Field = Givaro::ZpzDom]':
> test-ffarith.C:209:5:   required from 'int TestField(const Field&, int) [with 
> Field = Givaro::ZpzDom]'
> test-ffarith.C:243:2:   required from here
> test-ffarith.C:20:12: error: no match for 'operator<<' (operand types are 
> 'std::ostream {aka std::basic_ostream}' and 'std::ostream {aka 
> std::basic_ostream}')
>   std::cout << F.write(std::cout,a) << "!=" << F.write(std::cout,b) << " 
> failed (at line " <<  __LINE__ << ")" << std::endl; \
>  
> 
> test-ffarith.C:53:9: note: in expansion of macro 'TESTE_EG'
>  TESTE_EG(a, F.zero);
>  ^~~~
--- End Message ---
--- Begin Message ---
Source: givaro
Source-Version: 4.0.1-1

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

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

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

Debian distribution maintenance software
pp.
Doug Torrance  (supplier of updated givaro package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 19 Jul 2016 07:22:14 -0400
Source: givaro
Binary: libgivaro-dev libgivaro8 libgivaro-doc givaro-user-doc givaro-dev-doc
Architecture: source all amd64
Version: 4.0.1-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Doug Torrance 
Description:
 givaro-dev-doc - Developer Documentation for Givaro (obsolete)
 givaro-user-doc - User Documentation for Givaro (obsolete)
 libgivaro-dev - arithmetic and algebraic computations - development files
 libgivaro-doc - Documentation for Givaro
 libgivaro8 - arithmetic and algebraic computations
Closes: 753847 811847
Changes:
 givaro (4.0.1-1) experimental; urgency=medium
 .
   [ Julien Puydt ]
   * New upstream release. (Closes: #811847, #753847)
   * Add myself to uploaders.
   * Bump standards-version and compat up.
   * Use https in Vcs-* fields.
   * Clean debian/rules.
 .
   [ Doug Torrance ]
   * Add myself to Uploaders.
   * Bump debian/watch to version 4 and update with new download location.
   * Refresh patch for new upstream version.
   * Use all hardening flags.
   * New patch adding version of a function needed by Macaulay2.
Checksums-Sha1:
 bea74846e37c02a3f385b510010be77801ff3666 2349 givaro_4.0.1-1.dsc
 c33f71345a2a44fba85d2ac9bbea988ca0999ccd 637821 givaro_4.0.1.orig.tar.gz
 7144b11a1f2046821622e372e858d2fc4e0d9448 15860 givaro_4.0.1-1.debian.tar.xz
 9c699951e249b39fd36931125a148dc139cbcc0b 11964 givaro-dev-doc_4.0.1-1_all.deb
 32240b2612ae097ea3f2d6fc8faf1661fa27f505 11978 givaro-user-doc_4.0.1-1_all.deb
 4d6530ba7838f6dc2b7aed9640fc6f1995b4c7b2 297530 libgivaro-dev_4.0.1-

Processed: monkeytail,mtail: both ship /usr/bin/mtail

[Debian Bug Tracking System]

Processing control commands:

> found -1 0.0+git20160704.35c4023-1
Bug #831863 [monkeytail,mtail] monkeytail,mtail: both ship /usr/bin/mtail
There is no source info for the package 'monkeytail' at version 
'0.0+git20160704.35c4023-1' with architecture ''
Marked as found in versions mtail/0.0+git20160704.35c4023-1.
> found -1 0.3.2-3
Bug #831863 [monkeytail,mtail] monkeytail,mtail: both ship /usr/bin/mtail
There is no source info for the package 'mtail' at version '0.3.2-3' with 
architecture ''
Marked as found in versions monkeytail/0.3.2-3.

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

Bug#831863: monkeytail,mtail: both ship /usr/bin/mtail

[Andreas Beckmann]

Package: monkeytail,mtail
Severity: serious
Tags: sid
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 0.0+git20160704.35c4023-1
Control: found -1 0.3.2-3

Hi,

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

  Selecting previously unselected package mtail.
  Preparing to unpack .../mtail_0.0+git20160704.35c4023-1_amd64.deb ...
  Unpacking mtail (0.0+git20160704.35c4023-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/mtail_0.0+git20160704.35c4023-1_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/mtail', which is also in package monkeytail 
0.3.2-3
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/mtail_0.0+git20160704.35c4023-1_amd64.deb

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

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

  usr/bin/mtail

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

Cheers,

Andreas

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


monkeytail=0.3.2-3_mtail=0.0+git20160704.35c4023-1.log.gz
Description: application/gzip

Bug#831867: python-rows: ships /usr/lib/python2.7/dist-packages/.coverage

[Andreas Beckmann]

Package: python-rows
Version: 0.2.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: clone -1 -2
Control: reassign -2 python-jwt 1.4.0-1
Control: retitle -2 python-jwt: ships /usr/lib/python2.7/dist-packages/.coverage

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

I do not know what this file is about, but it clearly does not belong
into a package, at least at this location.

(Maybe a bug against the python packaging helpers would be appropriate
to exclude it automatically?)

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

  Selecting previously unselected package python-rows.
  Preparing to unpack .../python-rows_0.2.0-1_all.deb ...
  Unpacking python-rows (0.2.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-rows_0.2.0-1_all.deb (--unpack):
   trying to overwrite '/usr/lib/python2.7/dist-packages/.coverage', which is 
also in package python-jwt 1.4.0-1
  Errors were encountered while processing:
   /var/cache/apt/archives/python-rows_0.2.0-1_all.deb


cheers,

Andreas


python-jwt=1.4.0-1_python-rows=0.2.0-1.log.gz
Description: application/gzip

Processed: python-rows: ships /usr/lib/python2.7/dist-packages/.coverage

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #831867 [python-rows] python-rows: ships 
/usr/lib/python2.7/dist-packages/.coverage
Bug 831867 cloned as bug 831868
> reassign -2 python-jwt 1.4.0-1
Bug #831868 [python-rows] python-rows: ships 
/usr/lib/python2.7/dist-packages/.coverage
Bug reassigned from package 'python-rows' to 'python-jwt'.
No longer marked as found in versions rows/0.2.0-1.
Ignoring request to alter fixed versions of bug #831868 to the same values 
previously set
Bug #831868 [python-jwt] python-rows: ships 
/usr/lib/python2.7/dist-packages/.coverage
Marked as found in versions pyjwt/1.4.0-1.
> retitle -2 python-jwt: ships /usr/lib/python2.7/dist-packages/.coverage
Bug #831868 [python-jwt] python-rows: ships 
/usr/lib/python2.7/dist-packages/.coverage
Changed Bug title to 'python-jwt: ships 
/usr/lib/python2.7/dist-packages/.coverage' from 'python-rows: ships 
/usr/lib/python2.7/dist-packages/.coverage'.

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

Processed: tagging 817710

[Debian Bug Tracking System]

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

> tags 817710 + pending
Bug #817710 [src:user-mode-linux-doc] user-mode-linux-doc: Removal of debhelper 
compat 4
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#814711: marked as done (Garbled graphics in Renoise application)

[Debian Bug Tracking System]

Your message dated Wed, 20 Jul 2016 13:24:29 +0200
with message-id <20160720112429.GA27105@localhost.localdomain>
and subject line Close Bug#814711: Garbled graphics in Renoise application
has caused the Debian Bug report #814711,
regarding Garbled graphics in Renoise application
to be marked as done.

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

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


-- 
814711: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814711
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xserver-xorg
Version: 1:7.7+13
Severity: critical


Hello,

The latest xserver-xorg update makes the software "Renoise" unusuable:
http://www.renoise.com/

The interface is garbled, it seems that some portions of the window are
duplicated on different positions in the window.
It makes it completely unusuable and unreadable.

Refreshing the screen just changes the positions of the affected areas.

I've tried many versions of Renoise - no improvement.
I've downgraded to the previous version of xserver-xorg, and the
problems go away.


Thanks & Regards,
vitaminx



-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Aug  1  2014 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 274 Jan 27 15:55 /usr/bin/Xorg

Diversions concerning libGL are in place

diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2.0 by glx-diversions
diversion of /usr/lib/libGL.so.1 to /usr/lib/mesa-diverted/libGL.so.1 by 
glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2.0.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2.0.0 by glx-diversions
diversion of /usr/lib/libGLESv2.so.2 to /usr/lib/mesa-diverted/libGLESv2.so.2 
by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so.1.1.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv2.so.2 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2 by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGLESv2.so.2 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/libGLESv1_CM.so.1.1.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1 by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 by 
glx-diversions
diversion of /usr/lib/libGL.so.1.2.0 to /usr/lib/mesa-diverted/libGL.so.1.2.0 
by glx-diversions
diversion of /usr/lib/libGLESv2.so to /usr/lib/mesa-diverted/libGLESv2.so by 
glx-diversions
diversion of /usr/lib/libGL.so.1.2 to /usr/lib/mesa-diverted/libGL.so.1.2 by 
glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1.1.0 by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.2.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so by glx-diversions
diversion of /usr/lib/libGL.so to /usr/lib/mesa-diverted/libGL.so by 
glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2 by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1.2 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv2.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so by glx-diversions
diversion of /usr/lib/libGLESv1_CM.so to /usr/lib/mesa-diverted/libGLESv1_CM.so 
by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/

Bug#749357: marked as done (libmakefile-parser-perl: FTBFS - tests fail)

[Debian Bug Tracking System]

Your message dated Wed, 20 Jul 2016 11:54:18 +
with message-id 
and subject line Bug#831822: Removed package(s) from unstable
has caused the Debian Bug report #749357,
regarding libmakefile-parser-perl: FTBFS - tests fail
to be marked as done.

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

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


-- 
749357: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749357
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmakefile-parser-perl
Version: 0.215-2
Severity: seriou
Usertags: goto-cc

During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.

[...]
   dh_auto_test
make[1]: Entering directory 
'/srv/jenkins-slave/workspace/sid-goto-cc-libmakefile-parser-perl/libmakefile-parser-perl-0.215'
PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 
'inc', 'blib/lib', 'blib/arch')" t/99-pod-coverage.t t/99-pod.t t/ast-basic.t 
t/ast-rule.t t/ast-stem.t t/ast-var.t t/Makefile-Parser.t t/makesimple.t
t/99-pod-coverage.t .. skipped: We know we don't have enough POD :(
t/99-pod.t ... ok
t/ast-basic.t  ok
t/ast-rule.t . ok
t/ast-stem.t . ok
t/ast-var.t .. ok
t/Makefile-Parser.t .. ok
GNU Make 4.0

#   Failed test 'TEST 1: basics - process returned the 0 status'
#   at t/makesimple.t line 58.
#  got: '1'
# expected: '0'

#   Failed test 'TEST 1: basics - script/makesimple generated the right output'
#   at t/makesimple.t line 59.
#  got: ''
# expected: 'all:
#   @echo hello world
# '

Further failing tests follow. The full build log is attached.

Best,
Michael



libmakefile-parser-perl-build-log.txt.gz
Description: application/gunzip


pgpCCaMZA7enh.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 0.215-2+rm

Dear submitter,

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

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

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

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

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

Bug#831813: nullmailer leaks sensitive data through debconf

[David Bremner]

Maciej Delmanowski  writes:

> Package: nullmailer
> Version: 1:1.13-1
> Severity: grave
>
> The nullmailer package keeps sensitive information like users and passwords to
> the mail accounts on the remote SMTP servers in the '/etc/nullmailer/remotes'
> file, which is secured by 600 permissions and owned by mail:mail. However,
> after running command:
>
>   dpkg-reconfigure -f noninteractive nullmailer
>
> contents of this file are stored in the debconf database as cleartext in the
> 'nullmailer/relayhost' database key and can be read by any user using the
> command:
>
>   debconf-get-selections | grep nullmailer
>
> The 'dpkg-reconfigure' command cannot be executed directly by unprivileged
> users. However, the debconf database reads the contents of the
> '/etc/nullmailer/remotes' file and includes its contents in the database on
> package installation.
>
> This behaviour occurs again on package reinstallation - the debconf database
> is automatically updated with the contents of the '/etc/nullmailer/remotes'
> file. Therefore the sensitive information might show up in the
> 'debconf-get-selections' output after an automatic package upgrade or package
> reinstallation.

Unfortunately I can confirm the about statement about
debconf-get-selections.

I'm probably one of the few that doesn't have any password info in
/etc/nullmailer/remotes (I use some bespoke ssh auth thing), but I can
see how it's a problem in general.

d

Bug#830819: marked as done (resteasy: FTBFS: Could not resolve dependencies for project org.jboss.resteasy:tjws:jar:3.0.12.Final)

[Debian Bug Tracking System]

Your message dated Wed, 20 Jul 2016 12:03:54 +
with message-id 
and subject line Bug#830819: fixed in resteasy 3.0.18-1
has caused the Debian Bug report #830819,
regarding resteasy: FTBFS: Could not resolve dependencies for project 
org.jboss.resteasy:tjws:jar:3.0.12.Final
to be marked as done.

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

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


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

Dear Maintainer,

resteasy fails to build from source in unstable/amd64:

  [..]

  Running hooks in /etc/ca-certificates/update.d...
  
  Adding debian:ACCVRAIZ1.pem
  Adding debian:ACEDICOM_Root.pem
  Adding debian:AC_Raíz_Certicámara_S.A..pem
  Adding debian:Actalis_Authentication_Root_CA.pem
  Adding debian:AddTrust_External_Root.pem
  Adding debian:AddTrust_Low-Value_Services_Root.pem
  Adding debian:AddTrust_Public_Services_Root.pem
  Adding debian:AddTrust_Qualified_Certificates_Root.pem
  Adding debian:AffirmTrust_Commercial.pem
  Adding debian:AffirmTrust_Networking.pem
  Adding debian:AffirmTrust_Premium.pem
  Adding debian:AffirmTrust_Premium_ECC.pem
  Adding debian:ApplicationCA_-_Japanese_Government.pem
  Adding debian:Atos_TrustedRoot_2011.pem
  Adding debian:Autoridad_de_Certificacion_Firmaprofesional_CIF_A62634068.pem
  Adding debian:Baltimore_CyberTrust_Root.pem
  Adding debian:Buypass_Class_2_CA_1.pem
  Adding debian:Buypass_Class_2_Root_CA.pem
  Adding debian:Buypass_Class_3_Root_CA.pem
  Adding debian:CA_Disig.pem
  Adding debian:CA_Disig_Root_R1.pem
  Adding debian:CA_Disig_Root_R2.pem
  Adding debian:CA_WoSign_ECC_Root.pem
  Adding debian:CFCA_EV_ROOT.pem
  Adding debian:CNNIC_ROOT.pem
  Adding debian:COMODO_Certification_Authority.pem
  Adding debian:COMODO_ECC_Certification_Authority.pem
  Adding debian:COMODO_RSA_Certification_Authority.pem
  Adding debian:Camerfirma_Chambers_of_Commerce_Root.pem
  Adding debian:Camerfirma_Global_Chambersign_Root.pem
  Adding debian:Certification_Authority_of_WoSign_G2.pem
  Adding debian:Certigna.pem
  Adding debian:Certinomis_-_Autorité_Racine.pem
  Adding debian:Certinomis_-_Root_CA.pem
  Adding debian:Certplus_Class_2_Primary_CA.pem
  Adding debian:Certum_Root_CA.pem
  Adding debian:Certum_Trusted_Network_CA.pem
  Adding debian:Chambers_of_Commerce_Root_-_2008.pem
  Adding 
debian:China_Internet_Network_Information_Center_EV_Certificates_Root.pem
  Adding debian:ComSign_CA.pem
  Adding debian:Comodo_AAA_Services_root.pem
  Adding debian:Comodo_Secure_Services_root.pem
  Adding debian:Comodo_Trusted_Services_root.pem
  Adding debian:Cybertrust_Global_Root.pem
  Adding debian:D-TRUST_Root_Class_3_CA_2_2009.pem
  Adding debian:D-TRUST_Root_Class_3_CA_2_EV_2009.pem
  Adding debian:DST_ACES_CA_X6.pem
  Adding debian:DST_Root_CA_X3.pem
  Adding debian:Deutsche_Telekom_Root_CA_2.pem
  Adding debian:DigiCert_Assured_ID_Root_CA.pem
  Adding debian:DigiCert_Assured_ID_Root_G2.pem
  Adding debian:DigiCert_Assured_ID_Root_G3.pem
  Adding debian:DigiCert_Global_Root_CA.pem
  Adding debian:DigiCert_Global_Root_G2.pem
  Adding debian:DigiCert_Global_Root_G3.pem
  Adding debian:DigiCert_High_Assurance_EV_Root_CA.pem
  Adding debian:DigiCert_Trusted_Root_G4.pem
  Adding debian:E-Tugra_Certification_Authority.pem
  Adding debian:EBG_Elektronik_Sertifika_Hizmet_Sağlayıcısı.pem
  Adding debian:EC-ACC.pem
  Adding debian:EE_Certification_Centre_Root_CA.pem
  Adding debian:Entrust.net_Premium_2048_Secure_Server_CA.pem
  Adding debian:Entrust_Root_Certification_Authority.pem
  Adding debian:Entrust_Root_Certification_Authority_-_EC1.pem
  Adding debian:Entrust_Root_Certification_Authority_-_G2.pem
  Adding debian:Equifax_Secure_CA.pem
  Adding debian:Equifax_Secure_Global_eBusiness_CA.pem
  Adding debian:Equifax_Secure_eBusiness_CA_1.pem
  Adding debian:GeoTrust_Global_CA.pem
  Adding debian:GeoTrust_Global_CA_2.pem
  Adding debian:GeoTrust_Primary_Certification_Authority.pem
  Adding debian:GeoTrust_Primary_Certification_Authority_-_G2.pem
  Adding debian:GeoTrust_Primary_Certification_Authority_-_G3.pem
  Adding debian:GeoTrust_Universal_CA.pem
  Adding debian:GeoTrust_Universal_CA_2.pem
  Adding debian:GlobalSign_ECC_Root_CA_-_R4.pem
  Adding debian:GlobalSign_ECC_Root_CA_-_R5.pem
  Adding debian:GlobalSign_Root_CA.pem
  Adding debian:GlobalSign_Root_CA_-_R2.pem
  Adding debian:GlobalSign_Root_CA_-

Processed: spamassassin: fails to install: error: gpg required but not found!

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + spampd
Bug #831872 [spamassassin] spamassassin: fails to install: error: gpg required 
but not found!
Added indication that 831872 affects spampd

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

Bug#831872: spamassassin: fails to install: error: gpg required but not found!

[Andreas Beckmann]

Package: spamassassin
Version: 3.4.1-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + spampd

Hi,

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

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

  Setting up spamassassin (3.4.1-4) ...
  Adding system user `debian-spamd' (UID 150) ...
  Adding new group `debian-spamd' (GID 150) ...
  Adding new user `debian-spamd' (UID 150) with group `debian-spamd' ...
  Creating home directory `/var/lib/spamassassin' ...
  error: gpg required but not found!  It is not recommended, but you can use 
"sa-update" with the --no-gpg to skip the verification. 
  dpkg: error processing package spamassassin (--configure):
   subprocess installed post-installation script returned error exit status 2


cheers,

Andreas


spampd_2.30-23.log.gz
Description: application/gzip

Bug#831874: mediawiki: fails to install: mediawiki.postinst: php5enmod: not found

[Andreas Beckmann]

Package: mediawiki
Version: 1:1.27.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Selecting previously unselected package mediawiki.
  (Reading database ... 
(Reading database ... 9448 files and directories currently installed.)
  Preparing to unpack .../mediawiki_1%3a1.27.0-1_all.deb ...
  Unpacking mediawiki (1:1.27.0-1) ...
  Setting up mediawiki (1:1.27.0-1) ...
  /var/lib/dpkg/info/mediawiki.postinst: 8: 
/var/lib/dpkg/info/mediawiki.postinst: php5enmod: not found
  dpkg: error processing package mediawiki (--configure):
   subprocess installed post-installation script returned error exit status 127
  Errors were encountered while processing:
   mediawiki


Sounds a bit like an incorrect usage of the php packaging helpers,
e.g. a missing substvar.


cheers,

Andreas


mediawiki_1:1.27.0-1.log.gz
Description: application/gzip

Bug#830329: marked as done (qwt: FTBFS: dh_makeshlibs: failing due to earlier errors)

[Debian Bug Tracking System]

Your message dated Wed, 20 Jul 2016 09:39:33 -0300
with message-id <2073880.yxhxPPsySe@luna>
and subject line Done
has caused the Debian Bug report #830329,
regarding qwt: FTBFS: dh_makeshlibs: failing due to earlier errors
to be marked as done.

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

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


-- 
830329: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830329
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qwt
Version: 6.1.2-5
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160707 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 '/«PKGBUILDDIR»'
> dh_compress --exclude=.cpp --exclude=.pri --exclude=.xpm
> make[1]: Leaving directory '/«PKGBUILDDIR»'
>dh_fixperms -O--list-missing
>dh_strip -O--list-missing
>dh_makeshlibs -O--list-missing
> dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
> diff output below
> dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
> file: see diff output below
> dpkg-gensymbols: warning: debian/libqwt-qt5-6/DEBIAN/symbols doesn't match 
> completely debian/libqwt-qt5-6.symbols
> --- debian/libqwt-qt5-6.symbols (libqwt-qt5-6_6.1.2-5_amd64)
> +++ dpkg-gensymbolskBOE9y 2016-07-06 21:35:11.82000 +
> @@ -12,9 +12,9 @@
>   (optional=templinst|arch=arm64 armel armhf hurd-i386 i386 kfreebsd-i386 
> powerpc 
> ppc64el)_Z16qwtBoundingRectTI13QwtPointPolarE6QRectFRK13QwtSeriesDataIT_Eii@Base
>  6.1.2
>   
> (optional=templinst)_Z16qwtBoundingRectTI17QwtIntervalSampleE6QRectFRK13QwtSeriesDataIT_Eii@Base
>  6.1.2
>   (optional=templinst|arch=!mips 
> !mipsel)_Z16qwtBoundingRectTI7QPointFE6QRectFRK13QwtSeriesDataIT_Eii@Base 
> 6.1.2
> - 
> (optional=templinst)_Z17qRegisterMetaTypeI10QwtGraphicEiPKcPT_N9QtPrivate21MetaTypeDefinedHelperIS3_Xaasr12QMetaTypeId2IS3_E7DefinedntsrS8_9IsBuiltInEE11DefinedTypeE@Base
>  6.1.2
> +#MISSING: 6.1.2-5# 
> (optional=templinst)_Z17qRegisterMetaTypeI10QwtGraphicEiPKcPT_N9QtPrivate21MetaTypeDefinedHelperIS3_Xaasr12QMetaTypeId2IS3_E7DefinedntsrS8_9IsBuiltInEE11DefinedTypeE@Base
>  6.1.2
>   
> (optional=templinst)_Z17qRegisterMetaTypeI7QwtTextEiPKcPT_N9QtPrivate21MetaTypeDefinedHelperIS3_Xaasr12QMetaTypeId2IS3_E7DefinedntsrS8_9IsBuiltInEE11DefinedTypeE@Base
>  6.1.2
> - 
> (optional=templinst)_Z17qRegisterMetaTypeIN17QtMetaTypePrivate23QSequentialIterableImplEEiPKcPT_N9QtPrivate21MetaTypeDefinedHelperIS4_Xaasr12QMetaTypeId2IS4_E7DefinedntsrS9_9IsBuiltInEE11DefinedTypeE@Base
>  6.1.2
> +#MISSING: 6.1.2-5# 
> (optional=templinst)_Z17qRegisterMetaTypeIN17QtMetaTypePrivate23QSequentialIterableImplEEiPKcPT_N9QtPrivate21MetaTypeDefinedHelperIS4_Xaasr12QMetaTypeId2IS4_E7DefinedntsrS9_9IsBuiltInEE11DefinedTypeE@Base
>  6.1.2
>   (optional=templinst|arch=!amd64 !armhf !hurd-i386 !i386 !kfreebsd-amd64 
> !kfreebsd-i386)_Z17qRegisterMetaTypeIP11QwtPlotItemEiPKcPT_N9QtPrivate21MetaTypeDefinedHelperIS4_Xaasr12QMetaTypeId2IS4_E7DefinedntsrS9_9IsBuiltInEE11DefinedTypeE@Base
>  6.1.2
>   _Z19qwtNormalizeDegreesd@Base 6.1.2
>   _Z19qwtNormalizeRadiansd@Base 6.1.2
> @@ -221,6 +221,9 @@
>   _ZN11QwtScaleMapD2Ev@Base 6.1.2
>   _ZN11QwtScaleMapaSERKS_@Base 6.1.2
>   (optional=templinst)_ZN12QtConcurrent15RunFunctionTaskIvE3runEv@Base 6.1.2
> + _ZN12QtConcurrent15RunFunctionTaskIvED0Ev@Base 6.1.2-5
> + _ZN12QtConcurrent15RunFunctionTaskIvED1Ev@Base 6.1.2-5
> + _ZN12QtConcurrent15RunFunctionTaskIvED2Ev@Base 6.1.2-5
>   
> (optional=templinst)_ZN12QtConcurrent18StoredFunctorCall4IvPFvPK6QImagePS1_RK5QRectiES4_S4_S5_iE10runFunctorEv@Base
>  6.1.2
>   
> (optional=templinst)_ZN12QtConcurrent18StoredFunctorCall4IvPFvPK6QImagePS1_RK5QRectiES4_S4_S5_iED0Ev@Base
>  6.1.2
>   
> (optional=templinst)_ZN12QtConcurrent18StoredFunctorCall4IvPFvPK6QImagePS1_RK5QRectiES4_S4_S5_iED1Ev@Base
>  6.1.2
> @@ -232,8 +235,8 @@
>   
> (optional=templinst)_ZN12QtConcurrent41VoidStoredConstMemberFunctionPointerCall4Iv18QwtPlotSpectrogramRK11QwtScaleMapS2_S4_S2_RK5QRectS5_P6QImageS9_ED1Ev@Base
>  6.1.2
>   
> (optional=templinst)_ZN12QtConcurrent41VoidStoredConstMemberFunctionPointerCall4Iv18QwtPlotSpectrogramRK11QwtScaleMapS2_S4_S2_RK5QRectS5_P6QImageS9_ED2Ev@Base
>  6.1.2
>   _ZN12QwtLegendMap12removeWidgetEPK7QWidget@Base 6.1.2
> - _ZN12QwtLegendMap5EntryD1Ev@Base 6.1.2
> - _ZN12QwtLegendMap5EntryD2Ev@Base 6.1.2
> +#MISSING: 6.1.2-5# _ZN12QwtLegendMap5EntryD1Ev@Base 6.1.2
> +#MISSING: 6.1.2-5# _ZN12QwtLegendMap5EntryD2Ev@Base 6.1.2
>   _ZN12QwtLegendMap

Bug#831877: gitlab: fails to install: rake aborted! Errno::EACCES: Permission denied @ rb_sysopen - config.yml

[Andreas Beckmann]

Package: gitlab
Version: 8.9.0+dfsg-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

[...]
  -- add_index("web_hooks", ["project_id"], 
{:name=>"index_web_hooks_on_project_id", :using=>:btree})
 -> 0.0018s
  -- add_foreign_key("personal_access_tokens", "users")
 -> 0.0029s
  -- add_foreign_key("u2f_registrations", "users")
 -> 0.0018s
  -- initialize_schema_migrations_table()
 -> 0.0055s
  fatal: Not a git repository (or any of the parent directories): .git
  
  == Seed from /usr/share/gitlab/db/fixtures/production/001_admin.rb
  Administrator account created:
  
  login:root
  password: You'll be prompted to create one on your first visit.
  
  fatal: Not a git repository (or any of the parent directories): .git
  fatal: Not a git repository (or any of the parent directories): .git
  fatal: Not a git repository (or any of the parent directories): .git
  fatal: Not a git repository (or any of the parent directories): .git
  rake aborted!
  Errno::EACCES: Permission denied @ rb_sysopen - config.yml
  /usr/share/gitlab/lib/tasks/gitlab/shell.rake:58:in `initialize'
  /usr/share/gitlab/lib/tasks/gitlab/shell.rake:58:in `open'
  /usr/share/gitlab/lib/tasks/gitlab/shell.rake:58:in `block (4 levels) in '
  /usr/share/gitlab/lib/tasks/gitlab/shell.rake:24:in `chdir'
  /usr/share/gitlab/lib/tasks/gitlab/shell.rake:24:in `block (3 levels) in '
  Tasks: TOP => gitlab:shell:install
  (See full trace by running task with --trace)
  dpkg: error processing package gitlab (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   gitlab


cheers,

Andreas


gitlab_8.9.0+dfsg-4.log.gz
Description: application/gzip

Bug#831868: python-rows: ships /usr/lib/python2.7/dist-packages/.coverage

[Daniele Tricoli]

Hello Andreas,

On Wed, 20 Jul 2016 13:15:36 +0200 Andreas Beckmann  wrote:
> Control: retitle -2 python-jwt: ships /usr/lib/python2.7/dist-
packages/.coverage
[CUT]

Many thanks for the report. Already fixed on git, it will uploaded soon.

Kind regards,

-- 
 Daniele Tricoli 'eriol'
 https://mornie.org

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

Processed: Re: eeepc-acpi-scripts: fails to install due to insserv rejecting the script header

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #754377 [eeepc-acpi-scripts] eeepc-acpi-scripts: fails to install due to 
insserv rejecting the script header
Severity set to 'serious' from 'important'

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

Bug#831878: cyphesis-cpp: fails to install in chroot: update-rc.d: error: no runlevel symlinks to modify, aborting!

[Andreas Beckmann]

Package: cyphesis-cpp
Version: 0.6.0-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Selecting previously unselected package cyphesis-cpp.
  (Reading database ... 
(Reading database ... 9077 files and directories currently installed.)
  Preparing to unpack .../cyphesis-cpp_0.6.0-4_amd64.deb ...
  Unpacking cyphesis-cpp (0.6.0-4) ...
  Setting up cyphesis-cpp (0.6.0-4) ...
  update-rc.d: error: no runlevel symlinks to modify, aborting!
  dpkg: error processing package cyphesis-cpp (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   cyphesis-cpp


This may be related to the fact that piuparts installs the package in a 
minimal chroot, but I've never seen this error message from update-rc.d
(but there have been quite some changes w.r.t. the initscript helpers
recnetly) and most packages behave "sanely" in such a setup.


cheers,

Andreas


cyphesis-cpp_0.6.0-4.log.gz
Description: application/gzip

Bug#831879: diaspora-common: fails to install: Error: The new file /var/lib/diaspora-common/diaspora.conf does not exist!

[Andreas Beckmann]

Package: diaspora-common
Version: 0.5.9.1+debian2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Selecting previously unselected package diaspora-common.
  (Reading database ... 
(Reading database ... 11340 files and directories currently installed.)
  Preparing to unpack .../diaspora-common_0.5.9.1+debian2_all.deb ...
  Unpacking diaspora-common (0.5.9.1+debian2) ...
  Setting up diaspora-common (0.5.9.1+debian2) ...
  dbconfig-common: writing config to /etc/dbconfig-common/diaspora-common.conf
  
  Creating config file /etc/dbconfig-common/diaspora-common.conf with new 
version
  creating postgres user diaspora:  success.
  verifying creation of user: success.
  creating database diaspora_production: success.
  verifying database diaspora_production exists: success.
  dbconfig-common: flushing administrative password
  SSL enabled, configuring nginx for localhost...
  grep: /etc/diaspora.conf: No such file or directory
  Services List
  
  Registering /etc/diaspora.conf via ucf
  Error: The new file /var/lib/diaspora-common/diaspora.conf does not exist!
  dpkg: error processing package diaspora-common (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   diaspora-common


cheers,

Andreas


diaspora-common_0.5.9.1+debian2.log.gz
Description: application/gzip

Processed: closing 818814

[Debian Bug Tracking System]

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

> close 818814 2.0.2
Bug #818814 [mlpack] mlpack: FTBFS with libc 2.23: there are no arguments to 
'isnan' that depend on a template parameter
There is no source info for the package 'mlpack' at version '2.0.2' with 
architecture ''
Unable to make a source version for version '2.0.2'
Marked as fixed in versions 2.0.2.
Bug #818814 [mlpack] mlpack: FTBFS with libc 2.23: there are no arguments to 
'isnan' that depend on a template parameter
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#818814: closing 818814

[Barak A. Pearlmutter]

close 818814 2.0.2
thanks
fixed upstream

Bug#831884: libnet-ip-xs-perl: depends on missing libip-country-perl

[Andreas Beckmann]

Package: libnet-ip-xs-perl
Version: 0.17-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

libnet-ip-xs-perl/amd64 unsatisfiable Depends: libip-country-perl

libip-country-perl does not seem to be in NEW either.



Cheers,

Andreas

Bug#826884: snapd: /usr/bin/snap already used by the snap package

[Luke W Faraone]

control: tags -1 + patch

On Thu, 09 Jun 2016 20:51:16 +0200 Andreas Beckmann  wrote:
> during a test with piuparts I noticed your package failed to install
> because it tries to overwrite other packages files without declaring a
> Breaks+Replaces relation.
> 
> See policy 7.6 at
> https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

This is due to a conditional Conflicts that references an Ubuntu
version.

I've opened a PR to fix this against the package's repository[1], and
attached the patch for convenience. 

[1]: https://github.com/vorlonofportland/snappy/pull/2

  --  Luke Faraone
From b2b9b7d59ea6a52d0db04f7828d30ddf8949acef Mon Sep 17 00:00:00 2001
From: Luke Faraone 
Date: Wed, 20 Jul 2016 14:56:25 +0200
Subject: [PATCH] Switch to unconditional conflict against `snap`

`snapd` had a conditional conflicts against `snap` that references an Ubuntu version, `2013-11-29-1ubuntu1`.

The package has since moved forward in Debian from that version. Until that Ubuntu-specific patch is merged into Debian's `snap` package, we instead just unconditionally conflict with `snap`.

Closes #826884.
---
 debian/control | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/debian/control b/debian/control
index 6322b19..3651cb1 100644
--- a/debian/control
+++ b/debian/control
@@ -50,7 +50,7 @@ Package: snapd
 Architecture: any
 Depends: ${misc:Depends}, ${shlibs:Depends}, adduser,
  squashfs-tools, ubuntu-core-launcher (>= 1.0.23),
-Conflicts: snappy, snap (<< 2013-11-29-1ubuntu1)
+Conflicts: snappy, snap
 Built-Using: ${misc:Built-Using}
 Description: Tool to interact with Ubuntu Core Snappy.
  Manage an Ubuntu system with snappy.
@@ -60,7 +60,7 @@ Architecture: any
 Depends: snapd, ${misc:Depends}
 Replaces: ubuntu-snappy (<< 1.9)
 Breaks: ubuntu-snappy (<< 1.9)
-Conflicts: snap (<< 2013-11-29-1ubuntu1)
+Conflicts: snap
 Built-Using: ${misc:Built-Using}
 Description: Scripts for snapd that should only run on ubuntu core systems.
  This package contains systemd services that need to run on ubuntu core


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

Processed: Re: snapd: /usr/bin/snap already used by the snap package

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #826884 [snapd] snapd: /usr/bin/snap already used by the snap package
Added tag(s) patch.

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

Bug#812001: marked as done (smokekde: FTBFS with GCC 6: deleted function)

[Debian Bug Tracking System]

Your message dated Wed, 20 Jul 2016 13:50:41 +
with message-id 
and subject line Bug#831882: Removed package(s) from unstable
has caused the Debian Bug report #812001,
regarding smokekde: FTBFS with GCC 6: deleted function
to be marked as done.

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

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


-- 
812001: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812001
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: smokekde
Version: 4:4.14.3-1
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6

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

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

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

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> /usr/bin/c++  -fPIC -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -Wnon-virtual-dtor 
> -Wno-long-long -Wundef -Wcast-align -Wchar-subscripts -Wall -W 
> -Wpointer-arith -Wformat-security -fno-exceptions -DQT_NO_EXCEPTIONS 
> -fno-check-new -fno-common -Woverloaded-virtual -Wno-deprecated-declarations 
> -Wl,--enable-new-dtags -Wl,--fatal-warnings -Wl,--no-undefined -lc  
> -Wl,-z,relro -Wl,--as-needed -shared -Wl,-soname,libsmokesolid.so.3 -o 
> ../lib/libsmokesolid.so.3.0.0 CMakeFiles/smokesolid.dir/smokedata.o 
> CMakeFiles/smokesolid.dir/x_1.o CMakeFiles/smokesolid.dir/x_2.o 
> CMakeFiles/smokesolid.dir/x_3.o CMakeFiles/smokesolid.dir/x_4.o 
> CMakeFiles/smokesolid.dir/x_5.o CMakeFiles/smokesolid.dir/x_6.o 
> CMakeFiles/smokesolid.dir/x_7.o CMakeFiles/smokesolid.dir/x_8.o 
> CMakeFiles/smokesolid.dir/x_9.o CMakeFiles/smokesolid.dir/x_10.o 
> /usr/lib/x86_64-linux-gnu/libQtCore.so 
> /usr/lib/x86_64-linux-gnu/libQtNetwork.so /usr/lib/x86_64-linux-gnu/libQtGui.
> so /usr/lib/x86_64-linux-gnu/libQtXml.so 
> /usr/lib/x86_64-linux-gnu/libQtDBus.so /usr/lib/libsolid.so.4.14.14 
> -lsmokeqtcore -lsmokebase 
> cd /<>/obj-x86_64-linux-gnu/solid && /usr/bin/cmake -E 
> cmake_symlink_library ../lib/libsmokesolid.so.3.0.0 ../lib/libsmokesolid.so.3 
> ../lib/libsmokesolid.so
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> [ 18%] Built target smokesolid
> /<>/obj-x86_64-linux-gnu/nepomuk/x_8.cpp:12:7: error: deleted 
> function 'virtual 
> __smokenepomuk::x_Nepomuk__ResourceManager::~x_Nepomuk__ResourceManager()'
>  class x_Nepomuk__ResourceManager : public Nepomuk::ResourceManager {
>^~
> 
> In file included from /<>/nepomuk/nepomuk_includes.h:23:0,
>  from /<>/obj-x86_64-linux-gnu/nepomuk/x_8.cpp:2:
> /usr/include/nepomuk/resourcemanager.h:278:9: error: overriding non-deleted 
> function 'virtual Nepomuk::ResourceManager::~ResourceManager()'
>  ~ResourceManager();
>  ^
> 
> /<>/obj-x86_64-linux-gnu/nepomuk/x_8.cpp:12:7: note: 'virtual 
> __smokenepomuk::x_Nepomuk__ResourceManager::~x_Nepomuk__ResourceManager()' is 
> implicitly deleted because the default definition would be ill-formed:
>  class x_Nepomuk__ResourceManager : public Nepomuk::ResourceManager {
>^~
> 
> /<>/obj-x86_64-linux-gnu/nepomuk/x_8.cpp:12:7: error: 'virtual 
> Nepomuk::ResourceManager::~ResourceManager()' is private within this context
> In file included from /<>/nepomuk/nepomuk_includes.h:23:0,
>  from /<>/obj-x86_64-linux-gnu/nepomuk/x_8.cpp:2:
> /usr/include/nepomuk/resourcemanager.h:278:9: note: declared private here
>  ~ResourceManager();
>  ^
> 
> nepomuk/CMakeFiles/smokenepomuk.dir/build.make:292: recipe for target 
> 'nepomuk/CMakeFiles/smokenepomuk.dir/x_8.o' failed
> make[3]: *** [nepomuk/CMakeFiles/smokenepomuk.dir/x_8.o] Error 1

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Version: 4:4.14.3-2+rm

Dear submitter,

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

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

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

This message was generated automatically; if you believe that there is
a problem with i

Bug#831887: srst2: add bowtie2 and samtools to Build-Depends

[Andreas Beckmann]

Source: srst2
Version: 0.1.8-1
Severity: serious

Hi,

srst2 successfully builds on all architectures, but is not installable
on most of them (since it requires bowtie2 and samtools, which are
available only on a few platforms). This block migration to testing.

So add a B-D: bowtie2, samtools to only attempt to build where it is
installable (and automatically pick up new architectures if they gain
support), and once that has been built, request decrufting of the
"unusable" architectures.

Andreas

Processed: found 831452 in 3.11.3.1, tagging 749531, affects 821734

[Debian Bug Tracking System]

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

> found 831452 3.11.3.1
Bug #831452 [pcp-export-pcp2graphite] pcp-export-pcp2graphite: fails to upgrade 
from 'testing' - trying to overwrite /usr/bin/pcp2graphite
Marked as found in versions pcp/3.11.3.1.
> tags 749531 - patch
Bug #749531 [fslview] fslview: please switch to vtk6
Removed tag(s) patch.
> affects 821734 + votca-csg
Bug #821734 [libvotca-csg3] libvotca-csg3: fails to upgrade from 'jessie' - 
trying to overwrite /usr/share/man/man7/votca-csg.7.gz
Added indication that 821734 affects votca-csg
> thanks
Stopping processing here.

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

Bug#831863: [pkg-go] Bug#831863: monkeytail,mtail: both ship /usr/bin/mtail

[Martín Ferrari]

On 20/07/16 12:02, Andreas Beckmann wrote:
> Package: monkeytail,mtail

Uhm, pretty surprising naming for the binary.. Anyway, we need to solve
this. Changing mtail's name could be done, but I don't know what else to
call it, alternatively I don't mind conflicting with monkeytail.

At the same time, I wonder if monkeytail is going to stay around. The
upstream project has vanished, and the last release was 8 years ago.
Martyn, could you give your opinion on this?



-- 
Martín Ferrari (Tincho)

Processed: Re: gitlab: fails to install database

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #831448 [gitlab] gitlab: fails to install database
Severity set to 'important' from 'grave'

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

Bug#831448: gitlab: fails to install database

[Pirate Praveen]

Control: severity -1 important

On Sat, 16 Jul 2016 08:09:01 + cl...@jhcloos.com wrote:
> Package: gitlab
> Version: 8.9.0+dfsg-4
> Severity: grave
> Justification: renders package unusable
> 
> installing gitlab via apt with LANG=en_US.UTF-8 results in this:
> 
> Create database if not present
> psql: FATAL:  database "gitlab_production" does not exist
> createdb: database creation failed: ERROR:  encoding "UTF8" does not match 
> locale "en_US"
> DETAIL:  The chosen LC_CTYPE setting requires encoding "LATIN1".
> dpkg: error processing package gitlab (--configure):
>  subprocess installed post-installation script returned error exit status 1
> Errors were encountered while processing:
>  gitlab
> E: Sub-process /usr/bin/dpkg returned an error code (1)

It is most likely an issue with your local setup. Can you reproduce it
on a clean chroot without setting locale manually?



signature.asc
Description: OpenPGP digital signature

Bug#821967: Uploaded to DELAYED/2

[Ondrej Novy]

hi,

i sponsored Michael NMU and uploaded it to DELAYED/2

-- 
Best regards
 Ondřej Nový

Bug#811704: marked as done (FTBFS with GCC 6: macro passed X arguments, takes Y)

[Debian Bug Tracking System]

Your message dated Wed, 20 Jul 2016 16:11:07 +
with message-id 
and subject line Bug#811704: fixed in qutemol 0.4.1~cvs2008-6
has caused the Debian Bug report #811704,
regarding FTBFS with GCC 6: macro passed X arguments, takes Y
to be marked as done.

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

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


-- 
811704: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811704
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qutemol
Version: 0.4.1~cvs2008-5
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-macro

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

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

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> g++ -DPKGDATADIR='"/usr/share/qutemol"' -Ivcg -Isrc -I.  
> -I/usr/lib/x86_64-linux-gnu/wx/include/gtk2-unicode-3.0 -I/usr/include/wx-3.0 
> -D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXGTK__ -DNDEBUG -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2  -c -o src/Common.o src/Common.cpp
> In file included from /usr/include/c++/6/algorithm:60:0,
>  from vcg/vcg/math/lin_algebra.h:56,
>  from vcg/vcg/math/matrix33.h:100,
>  from vcg/vcg/math/quaternion.h:123,
>  from vcg/vcg/math/similarity.h:104,
>  from vcg/wrap/gl/math.h:70,
>  from src/gen_normal.h:64,
>  from src/Common.cpp:18:
> /usr/include/c++/6/utility:310:58: error: macro "assert" passed 2 arguments, 
> but takes just 1
> "Cannot make integer sequence of negative length" );
>   ^
> 
> In file included from /usr/include/c++/6/random:49:0,
>  from /usr/include/c++/6/bits/stl_algo.h:66,
>  from /usr/include/c++/6/algorithm:62,
>  from vcg/vcg/math/lin_algebra.h:56,
>  from vcg/vcg/math/matrix33.h:100,
>  from vcg/vcg/math/quaternion.h:123,
>  from vcg/vcg/math/similarity.h:104,
>  from vcg/wrap/gl/math.h:70,
>  from src/gen_normal.h:64,
>  from src/Common.cpp:18:
> /usr/include/c++/6/bits/random.h:88:61: error: macro "assert" passed 2 
> arguments, but takes just 1
>  "sorry, would be too much trouble for a slow result");
>  ^
> 
> /usr/include/c++/6/bits/random.h:168:54: error: macro "assert" passed 2 
> arguments, but takes just 1
>  "template argument not a floating point type");
>   ^
> 
> /usr/include/c++/6/bits/random.h:246:61: error: macro "assert" passed 2 
> arguments, but takes just 1
>"substituting _UIntType not an unsigned integral type");
>  ^
> 
> /usr/include/c++/6/bits/random.h:248:57: error: macro "assert" passed 2 
> arguments, but takes just 1
>"template argument substituting __m out of bounds");
>  ^
> 
> /usr/include/c++/6/bits/random.h:454:61: error: macro "assert" passed 2 
> arguments, but takes just 1
>"substituting _UIntType not an unsigned integral type");
>  ^
> 
> /usr/include/c++/6/bits/random.h:456:57: error: macro "assert" passed 2 
> arguments, but takes just 1
>"template argument substituting __m out of bounds");
>  ^
> 
> /usr/include/c++/6/bits/random.h:458:25: error: macro "assert" passed 2 
> arguments, but takes just 1
>"__r out of bound");
>  ^
> 
> /usr/include/c++/6/bits/random.h:460:25: error: macro "assert" passed 2 
> arguments, but takes just 1
>"__u out of bound");
>  ^
> 
> /usr/include/c++/6/bits/random.h:462:25: error: macro "assert" passed 2 
> arguments, but takes just 1
>"__s out of bound");
>  ^
> 
> /usr/include/c++/6/bits/random.h:464:25: error: macro "assert" passed 2 
> arguments, but takes just 1
>"__t out of bound");
>  ^
> 
> /usr/include/c++/6/bits/random.h:466:25: error: macro

Bug#831897: lepton: leaves a zombie process around after build

[Mattia Rizzolo]

package: lepton
version: 1.0-2
severity: serious
user: reproducible-bui...@lists.alioth.debian.org
usertags: ftbfs
x-debbugs-cc: reproducible-bui...@lists.alioth.debian.org

Dear maintainer,
while building packages I noticed that a builder stuck for a very long
time.  After inspection turns out it was waiting to be able to umount
/proc, which was kept busy by a process like
./lepton -socket=/tmp/f93406ea-94c9-45e3-a35b-bdfb1452a9ec -timebound=10ms 
-preload
with an open fd.

Killing that process unlocked the situation.

I was able to reproduce this in my notebook too.

That said, I find totally unacceptable for a build to leak a process and
leave it zombie (because that process had no parent, actually), so I'm
filing this at RC level.

(PS: in the meantime, blacklisted for reproducibility testing, but be
happy the build was reproducible (after having poked it) ;))

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Processed: Re: Bug#831088: urweb: FTBFS with GCC 6: memmem.c:77:17: error: this 'if' clause does not guard... [-Werror=misleading-indentation]

[Debian Bug Tracking System]

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

> tags 831088 upstream pending
Bug #831088 [src:urweb] urweb: FTBFS with GCC 6: memmem.c:77:17: error: this 
'if' clause does not guard... [-Werror=misleading-indentation]
Added tag(s) upstream and pending.
> forwarded 831088 https://github.com/urweb/urweb/issues/36
Bug #831088 [src:urweb] urweb: FTBFS with GCC 6: memmem.c:77:17: error: this 
'if' clause does not guard... [-Werror=misleading-indentation]
Set Bug forwarded-to-address to 'https://github.com/urweb/urweb/issues/36'.
> thanks
Stopping processing here.

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

Bug#831088: urweb: FTBFS with GCC 6: memmem.c:77:17: error: this 'if' clause does not guard... [-Werror=misleading-indentation]

[Benjamin Barenblat]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

tags 831088 upstream pending
forwarded 831088 https://github.com/urweb/urweb/issues/36
thanks
-BEGIN PGP SIGNATURE-

iQF8BAEBCgBmBQJXj61cXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ5OThCQjVEMTlDOEE3QjE3OUUwREFCODY5
RTczMDE0OUVCOTFDNTNCAAoJEJ5zAUnrkcU7cREH/jT4glLneqxgdjPhfWD9tPnz
a2A364w9cGGGhQnuxx4IEoKrwUBst5hzqUNNR1zibbzPf7jZjqEix6ov1bC+2az+
dGSSpyTsSNmNrh6L3pQD0OE0DR5FXE245K7x3ouzvuGmYeZQJNqMl4H3njZz2SvX
0TA6HtKqDsMHmj8Yki3Mg+Px0VcXWEZnYaB1G9gfOVamhz0XG62AB3UoZe4JSVEM
Xq/DybvUSlr5PIePJIimYoiRuc8x0ThiACgPrWAPdaNxSBZUbfGuVlqtgYmMcoL9
kpo9v4VY68+0ZpxfDb6nH+n6AIr5VBlqfIQfw7jz0gWrzVo2LXjAjXJOuArOcXQ=
=s5k9
-END PGP SIGNATURE-

Bug#831877: marked as done (gitlab: fails to install: rake aborted! Errno::EACCES: Permission denied @ rb_sysopen - config.yml)

[Debian Bug Tracking System]

Your message dated Wed, 20 Jul 2016 17:19:56 +
with message-id 
and subject line Bug#831877: fixed in gitlab 8.9.0+dfsg-5
has caused the Debian Bug report #831877,
regarding gitlab: fails to install: rake aborted! Errno::EACCES: Permission 
denied @ rb_sysopen - config.yml
to be marked as done.

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

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


-- 
831877: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831877
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 8.9.0+dfsg-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

[...]
  -- add_index("web_hooks", ["project_id"], 
{:name=>"index_web_hooks_on_project_id", :using=>:btree})
 -> 0.0018s
  -- add_foreign_key("personal_access_tokens", "users")
 -> 0.0029s
  -- add_foreign_key("u2f_registrations", "users")
 -> 0.0018s
  -- initialize_schema_migrations_table()
 -> 0.0055s
  fatal: Not a git repository (or any of the parent directories): .git
  
  == Seed from /usr/share/gitlab/db/fixtures/production/001_admin.rb
  Administrator account created:
  
  login:root
  password: You'll be prompted to create one on your first visit.
  
  fatal: Not a git repository (or any of the parent directories): .git
  fatal: Not a git repository (or any of the parent directories): .git
  fatal: Not a git repository (or any of the parent directories): .git
  fatal: Not a git repository (or any of the parent directories): .git
  rake aborted!
  Errno::EACCES: Permission denied @ rb_sysopen - config.yml
  /usr/share/gitlab/lib/tasks/gitlab/shell.rake:58:in `initialize'
  /usr/share/gitlab/lib/tasks/gitlab/shell.rake:58:in `open'
  /usr/share/gitlab/lib/tasks/gitlab/shell.rake:58:in `block (4 levels) in '
  /usr/share/gitlab/lib/tasks/gitlab/shell.rake:24:in `chdir'
  /usr/share/gitlab/lib/tasks/gitlab/shell.rake:24:in `block (3 levels) in '
  Tasks: TOP => gitlab:shell:install
  (See full trace by running task with --trace)
  dpkg: error processing package gitlab (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   gitlab


cheers,

Andreas


gitlab_8.9.0+dfsg-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: gitlab
Source-Version: 8.9.0+dfsg-5

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

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

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated gitlab package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 20 Jul 2016 20:28:21 +0530
Source: gitlab
Binary: gitlab
Architecture: source
Version: 8.9.0+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Pirate Praveen 
Description:
 gitlab - git powered software platform to collaborate on code
Closes: 820991 831877
Changes:
 gitlab (8.9.0+dfsg-5) unstable; urgency=medium
 .
   * Tighten dependencies
   * Don't run gitlab:shell:install in postinst (Closes: #831877)
 (installed config.yml works)
   * Add a note about CAcert and browser trust
 .
   [ Dmitry Smirnov ]
   * Do not leave dangling symlinks behind after purge
   * Remove generated assets on purge
   * rules: do not install LICENSE files
   * rules: properly use dh-systemd (Closes: #820991)
   * Rewrite terrible upstream .service files:
  - added meta "gitlab.service" that work alike corresponding init.d script
  - new .service files with support for "reload" and propagation of 
"reload" from "gitlab.service"
  - non-forking PIDFILE-less implementation
 This change fixes services' start-up and postinst error on first install.
   * templates: Replace StartSSL with CACert
Checksums-Sha1:
 c35e78ab09ce8111a82091ded6808f61e82a7328 2094 gitlab_8.9.0+dfsg-5.dsc
 17

Bug#817710: marked as done (user-mode-linux-doc: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Wed, 20 Jul 2016 17:25:02 +
with message-id 
and subject line Bug#817710: fixed in user-mode-linux-doc 20060501-2
has caused the Debian Bug report #817710,
regarding user-mode-linux-doc: Removal of debhelper compat 4
to be marked as done.

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

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


-- 
817710: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817710
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: user-mode-linux-doc
Severity: important
Usertags: compat-4-removal

Hi,

The package user-mode-linux-doc uses debhelper with a compat level of 4,
which is deprecated and scheduled for removal.

 * Please bump the debhelper compat at your earliest convenience.
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Compat level 4 will be removed on the first debhelper upload after
   the 15th of June.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: user-mode-linux-doc
Source-Version: 20060501-2

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

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

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

Debian distribution maintenance software
pp.
Ritesh Raj Sarraf  (supplier of updated user-mode-linux-doc 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 20 Jul 2016 16:16:42 +0530
Source: user-mode-linux-doc
Binary: user-mode-linux-doc
Architecture: source all
Version: 20060501-2
Distribution: unstable
Urgency: medium
Maintainer: User Mode Linux Maintainers 
Changed-By: Ritesh Raj Sarraf 
Description:
 user-mode-linux-doc - User-mode Linux (Documentation)
Closes: 514668 817710
Changes:
 user-mode-linux-doc (20060501-2) unstable; urgency=medium
 .
   * Add myself to Uploaders and drop previous inactive uploaders
   * Add Vcs headers
   * Add recommended build targets
   * Add homepage field
   * Drop sf logo from local documentation
   * Add doc-base section for documentation
 (Closes: #514668, #817710)
Checksums-Sha1:
 ebff53e7ca935b2d7c19623eb62dc33016f67de2 2047 
user-mode-linux-doc_20060501-2.dsc
 653023be67ffd5c3dd6caa7013339b57dcf2e474 8273 
user-mode-linux-doc_20060501-2.diff.gz
 4e0fcaaf1f9657b4d77ae060d4fb4591a123c498 538382 
user-mode-linux-doc_20060501-2_all.deb
Checksums-Sha256:
 2678a31d9e6ab4183e683dbd9941cd03e3d201068b80450ae56d5e5fb6194743 2047 
user-mode-linux-doc_20060501-2.dsc
 7aad5c4dabd648cd57d0873d2ceb43160a46a67654d31429f3b172a031b80cef 8273 
user-mode-linux-doc_20060501-2.diff.gz
 55d392b749a8e852b021615b76bced2db634a686710ec3240c9e91d89c780389 538382 
user-mode-linux-doc_20060501-2_all.deb
Files:
 5bea63bb23feb30133e711b07be0a031 2047 doc optional 
user-mode-linux-doc_20060501-2.dsc
 aebd50051cbcde7a891db9e424f7fbe0 8273 doc optional 
user-mode-linux-doc_20060501-2.diff.gz
 759dd16bd74dbac228058ecf02de643e 538382 doc optional 
user-mode-linux-doc_20060501-2_all.deb

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJXj6W9AAoJEKY6WKPy4XVpIbgP/2ruC0XuPdK1jslBxA65VxOH
dE9Cw3ba6vgSTSE487XD3rQrj/11AqbFlG1EJrWYy06SwzbDS1b6aiNOsUZRLjbF
Cjh/913qeYYOvsQvdIev9w4XXQqx3qFsoAxjgVmVEiU6QJ9ssVWWm8CpeYiDY0Bj
o9GjILfAEN8L1MKwfvJOx5GTkm4+7+j84yEB5GMY9wZxQNJ5pyliYuSBUWtySMSP
/BjcY4zD8bbZ0jHJa9aZFGczPTGS4Rf5ASr2WzayUxlah1t9tYboDUTteg6SWt+p
mWp7Qc1fYFLRNkiuHCfA/xA6IiCJGhtnQCcVx54vZ2zQzI1gaOihc1wGZw22pM9b
o/uwfBVB7KolA+rvTN2vfPDnku8E8YUO5Yc2NzmvPJsG9vLpy785yZfcs/MiVWR2
v1c1Fn17xRhdGAjzodErkHZJ7MkUMk2JPXfFYxPMGhtKjRJQtuY4hse0/Hj4K0hf
gLB+ukOuA6/cmwzL/OPc/Z1dih7x/WfGTeH0r48pKTcw2YBOuAa4RFt4f0FF38ej
MTQfJ3WJ9Qcu7wieYuINHx1wUgp+XE5xBn3XVdmBAWuWpobeSEWz+MGfi1PCyLua
R88YOJPZbploMQC3Li8CnetcA72qa10i2jv3KdxoeDIpVdjbSCNZ1wBvZpxYLYhs
vQ4WbwZ1XjtXq40FiADj
=r2fz
-END PGP SIGNATURE End Message ---

Bug#830917: marked as done (Gem::LoadError: Could not find 'rack-openid' (~> 1.3.1) - did find: [rack-openid-1.4.2])

[Debian Bug Tracking System]

Your message dated Wed, 20 Jul 2016 17:24:56 +
with message-id 
and subject line Bug#830917: fixed in ruby-omniauth-openid 1.0.1-4
has caused the Debian Bug report #830917,
regarding Gem::LoadError: Could not find 'rack-openid' (~> 1.3.1) - did find: 
[rack-openid-1.4.2]
to be marked as done.

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

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


-- 
830917: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830917
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-omniauth-openid
Version: 1.0.1-3
Severity: serious
X-Debbugs-CC: debian-r...@lists.debian.org

Dear Maintainer,

your gem library fails to load on ruby2.3:

ruby2.3 -e gem\ \"omniauth-openid\"
/usr/lib/ruby/2.3.0/rubygems/dependency.rb:319:in `to_specs': Could not find 
'rack-openid' (~> 1.3.1) - did find: [rack-openid-1.4.2] (Gem::LoadError)
Checked in 
'GEM_PATH=/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all',
 execute `gem env` for more information
[...]

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

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

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

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

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated 
ruby-omniauth-openid package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 20 Jul 2016 08:16:31 -0300
Source: ruby-omniauth-openid
Binary: ruby-omniauth-openid
Architecture: source
Version: 1.0.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Antonio Terceiro 
Description:
 ruby-omniauth-openid - openid strategy for OmniAuth
Closes: 830917
Changes:
 ruby-omniauth-openid (1.0.1-4) unstable; urgency=medium
 .
   [ Cédric Boutillier ]
   * Bump debhelper compatibility level to 9
   * Remove version in the gem2deb build-dependency
   * Use https:// in Vcs-* fields
   * Bump Standards-Version to 3.9.7 (no changes needed)
 .
   [ Antonio Terceiro ]
   * update packaging with a new `dh-make-ruby -w` run
   * rack-openid.patch: allow for a newer version of rack-openid
 (Closes: #830917)
Checksums-Sha1:
 d6eaa0108425ee137beac837d8cb4820e0ef5899 2245 ruby-omniauth-openid_1.0.1-4.dsc
 b3412c5372440e8a86dbf87a7ef3e71f461eaf57 4068 
ruby-omniauth-openid_1.0.1-4.debian.tar.xz
Checksums-Sha256:
 80a2b3fa444bc1369a4732963eb5ed90213a17db079c530cc97675628974c58a 2245 
ruby-omniauth-openid_1.0.1-4.dsc
 114759a563188ae8de05199c17e0fad771f9e353f89e5e63c45dd10ed9708879 4068 
ruby-omniauth-openid_1.0.1-4.debian.tar.xz
Files:
 597408283053786214c95ba4f1e0f142 2245 ruby optional 
ruby-omniauth-openid_1.0.1-4.dsc
 7977449e19c4d00dc214975315ebff13 4068 ruby optional 
ruby-omniauth-openid_1.0.1-4.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXj6ofAAoJEPwNsbvNRgve6ksP/i0wst4bVuScFdLcnE2JfIXa
BQVyVvMf94KPdrJqS+hY7k89F/TS6odJGUq5LPAwb38G2qpZzjvPCCs0wilKM517
zZ2G+Yvd4rnC/mOwYAAcTZxgP4IzjUfV44Qi8suKhu0H5+bf7FK7PuMH0eOwl4es
0/bFcf/34dGt8X8PsG11toK+ph+6RNPmeZaiON/XmS7pc/93CWf/znX0UJF2mgKN
ss1IQ+zTsjUnefJc2wwqmC3fNEsnt02CdTr3jBzGO9stlVo3TndBHfQYnIwoPoFJ
V4H6B2fejP+WZwp6sOu+r9mKR1QWV3olHqpCyDaNd+aeBCH5yYea/0vLNGg5zGUV
Nke0LGesGsqRScJb1qUwxN2iIkY2synvAfg+3bs3DK2sfozkoGSau2r/n7qgyM1o
Vq2yhmp/mIZQ6ndHsdk753ARjMbEzTOzumF54d24Cbi1bxAVP1XSRg4q5slJB7s2
p7BCJN/iYj0HYYAIkw+6fQk1MV3T8u3CLuQrP3nT+shwFCitcoRQk57C7YJy3aSQ
fQ9TZh8rOCXh/qDycgxd/MBaY+bBQJQnpb+iSS0ktG+8ahI+rnd3voPPRtcueno/
m1GGRbK2VEf3wEQvl+bRbZDRdasdRe3Q/sZJX0BJkw/wAOTJcRIsHt5K2R826cQ+
9t0FG9PEGIWRXIhbRdr9
=fLW0
-END PGP SIGNATURE End Message ---

Bug#831863: [pkg-go] Bug#831863: monkeytail,mtail: both ship /usr/bin/mtail

[Martyn Smith]

Yeah, I'm not sure if anyone uses it, but it seems pretty pointless now, I'd be 
quite happy for it to just disappear :-)

Martyn Smith

On Thu, 21 Jul 2016 at 2:50 AM "Martín Ferrari"

<
mailto:
> wrote:

On 20/07/16 12:02, Andreas Beckmann wrote:

> Package: monkeytail,mtail

Uhm, pretty surprising naming for the binary.. Anyway, we need to solve

this. Changing mtail's name could be done, but I don't know what else to

call it, alternatively I don't mind conflicting with monkeytail.

At the same time, I wonder if monkeytail is going to stay around. The

upstream project has vanished, and the last release was 8 years ago.

Martyn, could you give your opinion on this?

--

Martín Ferrari (Tincho)

Bug#829088: marked as done (ccache may silently miscompile symlinked source files)

[Debian Bug Tracking System]

Your message dated Wed, 20 Jul 2016 18:33:30 +
with message-id 
and subject line Bug#829088: fixed in ccache 3.2.7-1
has caused the Debian Bug report #829088,
regarding ccache may silently miscompile symlinked source files
to be marked as done.

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

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


-- 
829088: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829088
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ccache
Version: 3.1.10-1
Severity: grave

Hi,

the ccache in jessie has a serious regression vs. wheezy.

When passing files to the preprocessor, ccache in jessie resolves symlinks and 
passes the path of the resulting filename on the preprocessor command line. 
This does however change the compiled source code, because the preprocessor 
resolves paths for headers included with

#include "foo.h" 

from the directory that the source file is located in. So, if the directory of 
the real source file contains a header that is included in that file, this one 
will be used instead of a header that is located in the directory where the 
symlink is located.

Interestingly, if the directory with the real source file does not contain a 
file the the name of the included header, the preprocessor will fail and ccache 
will silently re-try using the correct compiler invocations. In this case no 
corruption occurs. I think therefore this bug is not hit very often and may not 
have been noticed before.


I don't know yet if the version of ccache in stretch/sid also has this problem, 
but I will try to find out. In any case, I think this should be fixed in jessie 
in a stable point release.


I have attached a ccache log files that exhibit the wrong preprocessor command 
line, and the corresponding log file with ccache 3.1.7-1 from wheezy that 
instead use the unmodified file name 
"../src/libc/stdlib/malloc-standard/free.c".

The examples use CCACHE_BASEDIR=/changes/L4.fritsch . I don't know if the bug
happens without CCACHE_BASEDIR. Using direct mode or not does not make a
difference.

Cheers,
Stefan
[2016-06-30T09:28:43.627166 9278 ] === CCACHE STARTED 
=
[2016-06-30T09:28:43.627277 9278 ] Command line: gcc -c -MD -MP -MF 
libc/stdlib/malloc-standard/.free.s.o.d -nostdinc -include 
/changes/L4.fritsch/l4re/src/l4/pkg/l4re-core/uclibc/lib/uclibc/../contrib/uclibc/include/libc-symbols.h
 -DL4SYS_USE_UTCB_WRAP=1 -DL4_THREAD_SAFE -DL4_NO_RTTI=1 -DNDEBUG -D_LIBC 
-D__UCLIBC_CTOR_DTOR__ -D__UCLIBC_HAS_SSP__=1 -DUSE_TLS=1 -DSYSTEM_amd64_K8_l4f 
-DARCH_amd64 -DCPUTYPE_K8 -DL4API_l4f -D_GNU_SOURCE 
-I/changes/L4.fritsch/l4re/src/l4/pkg/l4re-core/uclibc/lib/uclibc/../contrib/uclibc/libc/sysdeps/linux/x86_64
 
-I/changes/L4.fritsch/l4re/src/l4/pkg/l4re-core/uclibc/lib/uclibc/../contrib/uclibc/libc/sysdeps/linux
 -I/changes/L4.fritsch/obj/l4re/amd64/pkg/l4re-core/uclibc/lib/uclibc/src/libc 
-I/changes/L4.fritsch/l4re/src/l4/pkg/l4re-core/uclibc/lib/uclibc/../libpthread/src/sysdeps/x86_64
 
-I/changes/L4.fritsch/l4re/src/l4/pkg/l4re-core/uclibc/lib/uclibc/../libpthread/src
 -I/changes/L4.fritsch/obj/l4re/amd64/include/amd64/l4f 
-I/changes/L4.fritsch/obj/l4re/a
 md64/include/amd64 -I/changes/L4.fritsch/obj/l4re/amd64/include -isystem 
/changes/L4.fritsch/obj/l4re/amd64/include/sys/amd64/l4f -isystem 
/changes/L4.fritsch/obj/l4re/amd64/include/sys/l4f -isystem 
/changes/L4.fritsch/obj/l4re/amd64/include/sys/amd64 -isystem 
/changes/L4.fritsch/obj/l4re/amd64/include/sys -nostdinc 
-I/changes/L4.fritsch/obj/l4re/amd64/include/uclibc 
-I/changes/L4.fritsch/obj/l4re/amd64/include/contrib/libstdc++-v3 -isystem 
/usr/lib/gcc/x86_64-linux-gnu/4.9/include -isystem 
/usr/lib/gcc/x86_64-linux-gnu/4.9/include-fixed -fno-builtin 
-fno-stack-protector -DUCLIBC_INTERNAL -fno-omit-frame-pointer -g -O2 
-fno-strict-aliasing -Wall -Wstrict-prototypes -fno-common -std=gnu99 -m64 
-mno-red-zone -march=k8 -fno-stack-protector -DSHARED=1 -fPIC -U__PIC__ 
-D__PIC__=1 
/changes/L4.fritsch/obj/l4re/amd64/pkg/l4re-core/uclibc/lib/uclibc/src/libc/stdlib/malloc-standard/free.c
 -o libc/stdlib/malloc-standard/free.s.o
[2016-06-30T09:28:43.627301 9278 ] Hostname: dev
[2016-06-30T09:28:43.627323 9278 ] Working directory: 
/changes/L4.fritsch/obj/l4re/amd64/pkg/l4re-core/uclibc/lib/uclibc/OBJ-amd64_K8-l4f
[2016-06-30T09:28:43.627328 9278 ] Base directory: /changes/L4.fritsch
[2016-06-30T09:28:43.627671 9278 ] Source file: 
../../../../../../../../../l4re/src/l4/pkg/l4re-core/uclibc/lib/contrib/uclibc/libc/stdlib/malloc-standard/free.c
[2016-06-30T09:28:43.627678 9278 ] Dependency file: 
libc/stdlib/malloc-standard/

Bug#831909: gstreamer coredumps when playing wavs since the libavcodec upgrade

[Faidon Liambotis]

Package: libavcodec57
Version: 7:3.1.1-2
Severity: grave

I ran Debian testing on my desktop. Since about a day ago, pidgin
started crashing unexpectedly. After a little bit of debugging, I found
that it reproducibly crashes when trying to play sounds. Going a step
further, I made the test case as simple as:

$ gst-launch-1.0 filesrc location=/usr/share/sounds/purple/alert.wav  ! 
wavparse ! audioconvert !  fakesink
Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
Aborted (core dumped)

My dpkg.log has a bunch of ffmpeg-related package upgrades, including
libavcodec57, being installed on 2016-07-18, approximately when those
crashes started. Because of this and the backtrace below, I'm filing
this against libavcodec57 -- feel free to reassign if that's wrong.

The backtrace seems to be:
   PID: 4121 (gst-launch-1.0)
   UID: 1000 (paravoid)
   GID: 1000 (paravoid)
Signal: 6 (ABRT)
 Timestamp: Τετ 2016-07-20 21:55:59 EEST (5min ago)
  Command Line: gst-launch-1.0 filesrc 
location=/usr/share/sounds/purple/alert.wav ! wavparse ! audioconvert ! fakesink
Executable: /usr/bin/gst-launch-1.0
 Control Group: /
 Slice: -.slice
   Boot ID: fc3d59275e1042c491633f9a920c10e5
Machine ID: ddb673bb6861472487a0edbc40f6f1fc
  Hostname: donald
  Coredump: 
/var/lib/systemd/coredump/core.gst-launch-1\x2e0.1000.fc3d59275e1042c491633f9a920c10e5.4121.1469040959.xz
   Message: Process 4121 (gst-launch-1.0) of user 1000 dumped core.

Stack trace of thread 4122:
#0  0x7fa47ae7f1c8 raise (libc.so.6)
#1  0x7fa47ae8064a abort (libc.so.6)
#2  0x7fa4719b8f5b n/a (libavcodec.so.57)
#3  0x7fa4719b9026 avcodec_alloc_context3 (libavcodec.so.57)
#4  0x7fa473360540 n/a (libgstlibav.so)
#5  0x7fa473356e53 n/a (libgstlibav.so)
#6  0x7fa47b74b22d g_type_class_ref (libgobject-2.0.so.0)
#7  0x7fa47b9c8da4 gst_element_register 
(libgstreamer-1.0.so.0)
#8  0x7fa4733575b3 n/a (libgstlibav.so)
#9  0x7fa473349e20 n/a (libgstlibav.so)
#10 0x7fa47b9ea537 n/a (libgstreamer-1.0.so.0)
#11 0x7fa47b9ec425 n/a (libgstreamer-1.0.so.0)
#12 0x7fa47b9ed12c gst_plugin_load_by_name 
(libgstreamer-1.0.so.0)
#13 0x7fa47b9eda8d gst_plugin_feature_load 
(libgstreamer-1.0.so.0)
#14 0x7fa47ba137e3 gst_type_find_factory_call_function 
(libgstreamer-1.0.so.0)
#15 0x7fa479c48421 gst_type_find_helper_for_data 
(libgstbase-1.0.so.0)
#16 0x7fa479c485a4 gst_type_find_helper_for_buffer 
(libgstbase-1.0.so.0)
#17 0x7fa4799f446a n/a (libgstwavparse.so)
#18 0x7fa4799f4b47 n/a (libgstwavparse.so)
#19 0x7fa4799fabb1 n/a (libgstwavparse.so)
#20 0x7fa47ba0ee71 n/a (libgstreamer-1.0.so.0)
#21 0x7fa47b47b55e n/a (libglib-2.0.so.0)
#22 0x7fa47b47abc5 n/a (libglib-2.0.so.0)
#23 0x7fa47b1f4464 start_thread (libpthread.so.0)
#24 0x7fa47af3330d __clone (libc.so.6)

Stack trace of thread 4121:
#0  0x7fa47af2a19d poll (libc.so.6)
#1  0x7fa47b45439c n/a (libglib-2.0.so.0)
#2  0x7fa47b454722 g_main_loop_run (libglib-2.0.so.0)
#3  0x7fa47b9af8e9 gst_bus_poll (libgstreamer-1.0.so.0)
#4  0x004046f8 n/a (gst-launch-1.0)
#5  0x004036e9 n/a (gst-launch-1.0)
#6  0x7fa47ae6c730 __libc_start_main (libc.so.6)
#7  0x00403d19 n/a (gst-launch-1.0)

Stack trace of thread 4123:
#0  0x7fa47af2a19d poll (libc.so.6)
#1  0x7fa47b45439c n/a (libglib-2.0.so.0)
#2  0x7fa47b4544ac g_main_context_iteration 
(libglib-2.0.so.0)
#3  0x7fa47b4544e9 n/a (libglib-2.0.so.0)
#4  0x7fa47b47abc5 n/a (libglib-2.0.so.0)
#5  0x7fa47b1f4464 start_thread (libpthread.so.0)
#6  0x7fa47af3330d __clone (libc.so.6)

Finally, note that running "mpv /usr/share/sounds/purple/receive.wav"
seems to work without crashing (and produces sound), however, there is a
big yellow warning at the top that reads: "Warning: mpv was compiled
against a different version of ffmpeg than the shared library it is
linked against. This is most likely a broken build and misbehavior and
crashes are to be expected."

Thanks,
Faidon

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (50, 'unstable'), (1, 
'experimental')

Bug#817316: clean-crypto: Mandatory debian/compat for debhelper

[Logan Rosen]

Package: clean-crypto
Version: 1-1
Followup-For: Bug #817316
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu yakkety ubuntu-patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * debian/compat: Indicate compatibility level of 9.
  * debian/control:
- Build-depend on debhelper (>= 9).
- Remove needless dependency on JRE.

Thanks for considering the patch.

Logan Rosen

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

Kernel: Linux 4.4.0-21-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -u clean-crypto-1/debian/control clean-crypto-1/debian/control
--- clean-crypto-1/debian/control
+++ clean-crypto-1/debian/control
@@ -9,7 +9,7 @@
  Kyo Lee ,
  Daniel Nuomi ,
 DM-Upload-Allowed: yes
-Build-Depends: ant, debhelper (>= 5), cdbs (>= 0.4.5.3)
+Build-Depends: ant, debhelper (>= 9), cdbs (>= 0.4.5.3)
 Build-Depends-Indep: default-jdk
 Standards-Version: 3.8.4
 Homepage: https://code.launchpad.net/~chris-grze/eucalyptus-commons-ext/clean-crypto
@@ -17,7 +17,7 @@
 
 Package: libclean-crypto-java
 Architecture: all
-Depends: ${misc:Depends}, default-jre-headless
+Depends: ${misc:Depends}
 Description: Simplified and unrestricted javax.crypto bootstrap library
  Provides a simple unrestricted version of the javax.crypto package
  which can be provided when bootstrapping the Java Virtual Machine. This
only in patch2:
unchanged:
--- clean-crypto-1.orig/debian/compat
+++ clean-crypto-1/debian/compat
@@ -0,0 +1 @@
+9

Bug#829088: Jessie

[Joel Rosdahl]

For reference: I have requested to include ccache 3.1.12 in Jessie in
#831426 .

-- Joel

Processed: retitle 831857 to libupnp: CVE-2016-6255: write files via POST

[Debian Bug Tracking System]

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

> retitle 831857 libupnp: CVE-2016-6255: write files via POST
Bug #831857 [src:libupnp] libupnp: write files via POST
Changed Bug title to 'libupnp: CVE-2016-6255: write files via POST' from 
'libupnp: write files via POST'.
> thanks
Stopping processing here.

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

Bug#831184: mumble: FTBFS with GCC 6

[Christopher Knadle]

Hello again, Lucas.

Thanks for reporting this bug.
Sorry for the delay in response: unfortunately the hard disk in my mail
server died on Thursday night and since then I've been scrambling to try to
recover what data I could and get it back up again after disk replacement.

I had a quick look at the bug and the build log, and I think you pointed
out the correct section of the log where the compile went awry.

I should be able to look more deeply at this on Monday.  Meanwhile I'll try
to inform upstream about the problem so that they're aware.

Thanks.

-- Chris

Bug#829188: Latest IceDove crashes do not occur in upstream binaries

[Hadi]

Hi,

I have been experiencing the same frequent random crashes in IceDove
1:45.1.0-1~deb8u1 as reported in bugs #829188 and #828069. I have done
some debugging that might be of help:

- The crash exists even after disabling all add-ons, and recreating the
user profile from scratch (by deleting .icedove).

- The crash does NOT happen with upstream binaries (Thunderbird 45.2.0)
with the same add-ons, mailboxes, and profile. (I renamed .icedove to
.thunderbird).

Thus the problem is either introduced by IceDove's repackaging, or
resolved upstream between TB 45.1 and 45.2.

Cheers,
Hadi

Processed: Bug#831141 marked as pending

[Debian Bug Tracking System]

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

> tag 831141 pending
Bug #831141 [src:qmidinet] qmidinet: FTBFS with GCC 6: cstdlib:75:25: fatal 
error: stdlib.h: No such file or directory
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#831141: marked as pending

[Jaromír Mikeš]

tag 831141 pending
thanks

Hello,

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

http://git.debian.org/?p=pkg-multimedia/qmidinet.git;a=commitdiff;h=9aeb602

---
commit 9aeb602987ca91459abae3ab28c985466c62890a
Author: Jaromír Mikeš 
Date:   Wed Jul 20 22:52:03 2016 +0200

Finalize changelog.

diff --git a/debian/changelog b/debian/changelog
index 56b9853..5c42f29 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,6 @@
-qmidinet (0.4.0-2) UNRELEASED; urgency=medium
+qmidinet (0.4.0-2) unstable; urgency=medium
 
-  * Start new upload.
+  * Add patch to build with gcc6. (Closes: #831141)
 
  -- Jaromír Mikeš   Wed, 20 Jul 2016 22:44:32 +0200
 

Bug#811986: qwtplot3d: FTBFS with GCC 6: symbol changes

[Scott Kitterman]

On Tuesday, January 19, 2016 08:13:48 PM you wrote:
> Package: qwtplot3d
> Version: 0.2.7+svn191-9
> Severity: important
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-6 gcc-6-symbols
> 
> This package fails to build with GCC 6.  GCC 6 has not been released
> yet, but it's expected that GCC 6 will become the default compiler for
> stretch.
> 
> Note that only the first error is reported; there might be more.  You
> can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
> you can set CC=gcc-6 CXX=g++-6 explicitly.
> 
> You may be able to find out more about this issue at
> https://gcc.gnu.org/gcc-6/changes.html
> 
> > sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
> 
> ...
> 
> > dpkg-gensymbols: warning: some symbols or patterns disappeared in the
> > symbols file: see diff output below dpkg-gensymbols: warning:
> > debian/libqwtplot3d-qt4-0v5/DEBIAN/symbols doesn't match completely
> > debian/libqwtplot3d-qt4-0v5.symbols ---
> > debian/libqwtplot3d-qt4-0v5.symbols
> > (libqwtplot3d-qt4-0v5_0.2.7+svn191-9_amd64) +++
> > dpkg-gensymbolsFodDeO   2016-01-19 23:39:20.896195539 +
...

This is trivially fixable once GCC-6 is default, so removal from testing now 
makes no sense.  No idea how failing to build with a non-default compiler is 
RC in any case.

Scott K

Bug#831141: marked as done (qmidinet: FTBFS with GCC 6: cstdlib:75:25: fatal error: stdlib.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 20 Jul 2016 21:53:09 +
with message-id 
and subject line Bug#831141: fixed in qmidinet 0.4.0-2
has caused the Debian Bug report #831141,
regarding qmidinet: FTBFS with GCC 6: cstdlib:75:25: fatal error: stdlib.h: No 
such file or directory
to be marked as done.

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

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


-- 
831141: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831141
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qmidinet
Version: 0.4.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64

Hi,

During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html

Relevant part (hopefully):
> g++ -c -m64 -pipe -g -O2 -fPIE -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g -std=gnu++0x -Wall 
> -W -D_REENTRANT -fPIC -DDATADIR="/usr/share" -DQT_WIDGETS_LIB -DQT_GUI_LIB 
> -DQT_CORE_LIB -I. -I. -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
> /usr/local/include -isystem /usr/include -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -I.moc -I.ui 
> -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -o .obj/qmidinet.o 
> qmidinet.cpp
> In file included from /usr/include/c++/6/bits/stl_algo.h:59:0,
>  from /usr/include/c++/6/algorithm:62,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h:88,
>  from 
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qnamespace.h:37,
>  from 
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs.h:41,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:40,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/QObject:1,
>  from qmidinetUdpDevice.h:34,
>  from qmidinet.h:25,
>  from qmidinet.cpp:22:
> /usr/include/c++/6/cstdlib:75:25: fatal error: stdlib.h: No such file or 
> directory
>  #include_next 
>  ^
> compilation terminated.
> make[3]: *** [.obj/qmidinet.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/13/qmidinet_0.4.0-1_unstable_gcc6.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.
--- End Message ---
--- Begin Message ---
Source: qmidinet
Source-Version: 0.4.0-2

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 20 Jul 2016 22:44:32 +0200
Source: qmidinet
Binary: qmidinet qmidinet-dbg
Architecture: source amd64
Version: 0.4.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Jaromír Mikeš 
Description:
 qmidinet   - MIDI Network Gateway via UDP/IP Multicast
 qmidinet-dbg - Debugging symbols for QmidiNet
Closes: 831141
Changes:
 qmidinet (0.4.0-2) unstable; urgency=medium
 .
   * Add patch to build with gcc6. (Closes: #831141)
Checksums-Sha1:
 65cea792b7841b3e7283b893a9ba10e51e3df08d 2127 qmidinet_0.4.0-2.dsc
 88505e57672a7f2ad74ca8c13bebaaf8e20d61fb 3652 qmidinet_0.4.0-2.debian.tar.xz
 2da5b58e176d5c7acb99fa549952a269348c4597 955310 qmidinet-dbg_0.4.0-2_amd64.deb
 36935feea454acce27a6ab544e38333e7aeb68d4 43698 qmidinet_0.4.0-2_amd64.deb

Bug#831130: marked as pending

[Jaromír Mikeš]

tag 831130 pending
thanks

Hello,

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

http://git.debian.org/?p=pkg-multimedia/qxgedit.git;a=commitdiff;h=ce15e3e

---
commit ce15e3e3a41b57eff28f7b18b36ecca69d27158b
Author: Jaromír Mikeš 
Date:   Thu Jul 21 00:10:07 2016 +0200

Finalize changelog.

diff --git a/debian/changelog b/debian/changelog
index bf8c7f5..c224e7c 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,7 @@
 qxgedit (0.4.0-2) UNRELEASED; urgency=medium
 
-  * Start new upload.
+  * Add patch to build with gcc6. (Closes: #831130)
+  * Tune .gitignore file.
 
  -- Jaromír Mikeš   Wed, 20 Jul 2016 23:38:05 +0200
 

Processed: Bug#831130 marked as pending

[Debian Bug Tracking System]

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

> tag 831130 pending
Bug #831130 [src:qxgedit] qxgedit: FTBFS with GCC 6: cstdlib:75:25: fatal 
error: stdlib.h: No such file or directory
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#822016: marked as done (postfix: Build arch:all+arch:any but is missing build-{arch,indep} targets)

[Debian Bug Tracking System]

Your message dated Wed, 20 Jul 2016 22:25:17 +
with message-id 
and subject line Bug#822016: fixed in postfix 3.1.0-4
has caused the Debian Bug report #822016,
regarding postfix: Build arch:all+arch:any but is missing build-{arch,indep} 
targets
to be marked as done.

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

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


-- 
822016: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822016
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postfix
Severity: normal
Usertags: arch-all-and-any-missing-targets

Hi,

The package postfix builds an architecture independent *and* an
architecture dependent package, but does not have the (now mandatory)
"build-arch" and "build-indep" targets in debian/rules.

We would like to phase out the hacks in dpkg, which are currently
needed to ensure that postfix builds despite its lack of these
targets.

 * Please add build-arch and build-indep targets to postfix at
   your earliest convenience.
   - This can also be solved by using e.g. the "dh"-style rules.

 * The work around will be removed in the first dpkg upload after
   the 1st of June.  After that upload, postfix will FTBFS if
   this bug has not been fixed before then.

Thanks,

See also: https://lists.debian.org/debian-devel/2016/04/msg00023.html
--- End Message ---
--- Begin Message ---
Source: postfix
Source-Version: 3.1.0-4

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

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

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

Debian distribution maintenance software
pp.
Scott Kitterman  (supplier of updated postfix package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 20 Jul 2016 17:42:07 -0400
Source: postfix
Binary: postfix postfix-ldap postfix-cdb postfix-pcre postfix-mysql 
postfix-pgsql postfix-dev postfix-doc
Architecture: source amd64 all
Version: 3.1.0-4
Distribution: unstable
Urgency: medium
Maintainer: LaMont Jones 
Changed-By: Scott Kitterman 
Description:
 postfix- High-performance mail transport agent
 postfix-cdb - CDB map support for Postfix
 postfix-dev - Loadable modules development environment for Postfix
 postfix-doc - Documentation for Postfix
 postfix-ldap - LDAP map support for Postfix
 postfix-mysql - MySQL map support for Postfix
 postfix-pcre - PCRE map support for Postfix
 postfix-pgsql - PostgreSQL map support for Postfix
Closes: 777503 822016
Changes:
 postfix (3.1.0-4) unstable; urgency=medium
 .
   * Remove timestamps gzip headers to make build reproducible
 (Closes: #777503)
   * Update debian/rules to provide separate build-arch/build-indep rules and
 adjust to build arch and indep separately (Closes: #822016)
   * Bump standards version to 3.9.8 without further change
   * When running systemctl reload postfix.service, propagate the reload
 request to all running instances of postfix@.service
   * Edit debian/changelog from NMU to include Dutch localization update that
 was silently included
Checksums-Sha1:
 ec41dd0ba248bcd47542c1d839bcbebfb0890401 2551 postfix_3.1.0-4.dsc
 0fc1c6ceaca38e95efbed09ea50413b6d2a5a142 181648 postfix_3.1.0-4.debian.tar.xz
 775c5b21aca422f31c39713d43a32c0b25c3bfce 2378 
postfix-cdb-dbgsym_3.1.0-4_amd64.deb
 fe62a99f225e573fc9e9042bb800b615acdb35c0 307626 postfix-cdb_3.1.0-4_amd64.deb
 a76af420330c7c986ebedafbb3a5b6c18238c268 97966 postfix-dbgsym_3.1.0-4_amd64.deb
 015833866e9b8529e40b3ed22ab0db4564324348 412108 postfix-dev_3.1.0-4_all.deb
 693bb790d6616c595b2521965b2f9f999ffab630 1159872 postfix-doc_3.1.0-4_all.deb
 2f240332177d31a85bc4bc1ce9f2ceb425dd03e5 3078 
postfix-ldap-dbgsym_3.1.0-4_amd64.deb
 41bfd9e96105a8374bb72663efbc920d008968de 314694 postfix-ldap_3.1.0-4_amd64.deb
 aa2ab34a53f12e6b858455d9021a44d8f9e527df 2644 
postfix-mysql-dbgsym_3.1.0-4_amd64.deb
 9aefd358a47d212e507333d643716b30a3ed7377 309498 postfix-mysql_3.1.0-4_amd64.deb
 55018739eaa87485bc972350024367b00fdfb7f4 2450 
postfix-pcre-dbgsym_3.1.0-4_amd64.deb
 dda6c0559f173cfba4816148344902be279e76c0 309474 postfix-pcre_3.1.0-4_amd64.deb
 b8bf34c6ce946293f1da927d749c169b9dbd 2600 
postfix-pgsql-dbgsym_3.1.0-4_amd64.deb
 c90b897ac53476ea4

Bug#804611: marked as done (socat: FTBFS: undefined reference to `SSLv3_client_method')

[Debian Bug Tracking System]

Your message dated Wed, 20 Jul 2016 22:26:38 +
with message-id 
and subject line Bug#804611: fixed in socat 2.0.0~beta9-1
has caused the Debian Bug report #804611,
regarding socat: FTBFS: undefined reference to `SSLv3_client_method'
to be marked as done.

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

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


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

Dear Maintainer,

The package fails to build:

ranlib libxio.a
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-D_GNU_SOURCE -Wall -Wno-parentheses  -DHAVE_CONFIG_H -I. -D_FORTIFY_SOURCE=2 
-Wl,-z,relro -o socat socat.o libxio.a -lwrap -lrt -lutil  -lssl -lcrypto
libxio.a(sslcls.o): In function `sycSSLv3_client_method':
/socat-1.7.3.0/sslcls.c:61: undefined reference to `SSLv3_client_method'
libxio.a(sslcls.o): In function `sycSSLv3_server_method':
/socat-1.7.3.0/sslcls.c:69: undefined reference to `SSLv3_server_method'
collect2: error: ld returned 1 exit status
Makefile:115: recipe for target 'socat' failed

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

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: socat
Source-Version: 2.0.0~beta9-1

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

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

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated socat package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 20 Jul 2016 19:50:23 +
Source: socat
Binary: socat
Architecture: source amd64
Version: 2.0.0~beta9-1
Distribution: experimental
Urgency: low
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 socat  - multipurpose relay for bidirectional data transfer
Closes: 804611
Changes:
 socat (2.0.0~beta9-1) experimental; urgency=low
 .
   * New upstream release.
   * Remove merged in patches.
   * Enable parallel building.
   * Update Standards-Version to 3.9.8 and debhelper level to 9 .
 .
   [ Jon DeVree  ]
   * Make use of SSLv3 methods conditional (closes: #804611).
Checksums-Sha1:
 bee45439cdd09b50628c1b9cc768f44383534274 1763 socat_2.0.0~beta9-1.dsc
 ad44c2758589ed439da7782a6358a2f27910673c 643749 socat_2.0.0~beta9.orig.tar.gz
 809c88351e90802e501be20caa81c8eb409f138b 5780 socat_2.0.0~beta9-1.debian.tar.xz
 c3af72d43852ba90d5a7922230f627270ec64ba6 941340 
socat-dbgsym_2.0.0~beta9-1_amd64.deb
 73b2fc8b8da3ac182499fcadcedc5580d56602c8 364840 socat_2.0.0~beta9-1_amd64.deb
Checksums-Sha256:
 cf5f060254ad69507a2e1a3b57495d0868cde53a29102d95ae94e90e1c2a8ae5 1763 
socat_2.0.0~beta9-1.dsc
 f9496ea44898d7707507a728f1ff16b887c80ada63f6d9abb0b727e96d5c281a 643749 
socat_2.0.0~beta9.orig.tar.gz
 65294afa13ca3fe700a20b6dcbc08f1bb46914d28e482690f93c4e74a6274d18 5780 
socat_2.0.0~beta9-1.debian.tar.xz
 65c411f6933cb3a31143f1262b0fb4ec22af31198c8253890647461f30276a20 941340 
socat-dbgsym_2.0.0~beta9-1_amd64.deb
 2348626b588d015ef556bf7d45bd736d78850572cbd6321e94ce0715fedd0304 364840 
socat_2.0.0~beta9-1_amd64.deb
Files:
 813ac91a54b1a4868357423a16b251cf 1763 net extra socat_2.0.0~beta9-1.dsc
 5b05b7b86f073a133f7c7aaa453de280 643749 net extra socat_2.0.0~beta9.orig.tar.gz
 9f4ee085ca9df4c1042d4b51645e17e9 5780 net extra 
socat_2.0.0~beta9-1.debian.tar.xz
 2333d25e041b63021da021fad99119fc 941340 debug extra 
socat-dbgsym_2.0.0~beta9-1_amd64.deb
 852d977f381291a2950a78c0af4df3bb 364840 net extra socat_2.0.0~beta9-1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXj/biAAoJENzjEOeGTMi/38wP/1cPdSNk8TFBq1z4HYaajWNM
aLPlxYJyPvlNgm81gYgcssWlLjdPPGLwAYhvLQW/bkJ9f1tAvbq9swEK0vM+mB/4
BChL3bTlgm2pYPeileVi1pcIThnimVoCQJqxcmJflEhne

Bug#831130: marked as done (qxgedit: FTBFS with GCC 6: cstdlib:75:25: fatal error: stdlib.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 20 Jul 2016 22:35:34 +
with message-id 
and subject line Bug#831130: fixed in qxgedit 0.4.0-2
has caused the Debian Bug report #831130,
regarding qxgedit: FTBFS with GCC 6: cstdlib:75:25: fatal error: stdlib.h: No 
such file or directory
to be marked as done.

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

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


-- 
831130: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831130
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qxgedit
Version: 0.4.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64

Hi,

During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html

Relevant part (hopefully):
> g++ -c -m64 -pipe -g -O2 -fPIE -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -std=gnu++0x 
> -Wall -W -D_REENTRANT -fPIC -DDATADIR="/usr/share" -DQT_NO_DEBUG 
> -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I. -isystem 
> /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/local/include -isystem 
> /usr/include -isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtX11Extras -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -I.moc -I.ui 
> -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -o .obj/XGParam.o 
> XGParam.cpp
> In file included from /usr/include/c++/6/bits/stl_algo.h:59:0,
>  from /usr/include/c++/6/algorithm:62,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h:88,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/qchar.h:37,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/qhash.h:38,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/QHash:1,
>  from XGParam.h:27,
>  from XGParam.cpp:22:
> /usr/include/c++/6/cstdlib:75:25: fatal error: stdlib.h: No such file or 
> directory
>  #include_next 
>  ^
> compilation terminated.
> make[3]: *** [.obj/XGParam.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/13/qxgedit_0.4.0-1_unstable_gcc6.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.
--- End Message ---
--- Begin Message ---
Source: qxgedit
Source-Version: 0.4.0-2

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 20 Jul 2016 23:38:05 +0200
Source: qxgedit
Binary: qxgedit
Architecture: source amd64
Version: 0.4.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Jaromír Mikeš 
Description:
 qxgedit- MIDI System Exclusive files editor
Closes: 831130
Changes:
 qxgedit (0.4.0-2) unstable; urgency=medium
 .
   * Add patch to build with gcc6. (Closes: #831130)
   * Tune .gitignore file.
Checksums-Sha1:
 54300d6f92ded4e0fb39b2a75a59f2628e1cd982 2078 qxgedit_0.4.0-2.dsc
 aa5e4b1e310d996379f83db5be6b316008d0cfb2 2744 qxgedit_0.4.0-2.debian.tar.xz
 9d6d5a9cabeff7a1fc10b7982efb4f7985d68c13 929478 
qxgedit-dbgsym_0.4.0-2_amd64.deb
 4ce47650432b86cf3d5d9466ee5582ef0b6de666 252998 qxgedit_0.4.0-2_amd64.deb
Checksums-Sha256:
 1a734adb6489e93f4ad180579a0c6733a02f11691b66552257aa3a668e2d45cd 2078 
qxgedit_0.4.0-2.dsc
 9

Bug#831978: ring-daemon: Internal daemon started by users should not be in /usr/sbin/

[Petter Reinholdtsen]

Package: ring-daemon
Version: 20160720.3.73cfbb9~dfsg1-2
Severity: serious

The /usr/sbin/dring in the ring-daemon package seem to be placed in the
wrong directory.  The program is started by the ring GUI tool when a
user starts the Ring client, and thus is not a tool intended for sbin,
as specified by FHS[1] refered from Debian Policy[2]:

  Utilities used for system administration (and other root-only
  commands) are stored in /sbin, /usr/sbin, and /usr/local/sbin. /sbin
  contains binaries essential for booting, restoring, recovering, and/or
  repairing the system in addition to the binaries in /bin. [18]
  Programs executed after /usr is known to be mounted (when there are no
  problems) are generally placed into /usr/sbin. Locally-installed
  system administration programs should be placed into
  /usr/local/sbin.

If it is supposed to be called directly by users, I suspect it belong in
/usr/bin/.  If not, it probably belong in /usr/lib/ring/ or similar.

Setting severity to serious, as this issue is about breaking the
requirement in the Debian policy section 9.1.1.

 [1] https://www.debian.org/doc/packaging-manuals/fhs/fhs-2.3.html#SBINSYSTEMBINARIES
 >
 [2] https://www.debian.org/doc/debian-policy/ch-opersys.html >
-- 
Happy hacking
Petter Reinholdtsen

Bug#831240: google-perftools: FTBFS: Running death test 0 hangs

[Aliaksey Kandratsenka]

On Tue, Jul 19, 2016 at 1:29 PM, Lucas Nussbaum  wrote:
> Hi Aliaksey,
>
> On 16/07/16 at 12:28 +0200, Santiago Vila wrote:
>> On Fri, 15 Jul 2016, Aliaksey Kandratsenka wrote:
>>
>> > Thanks for reporting the issue. I just tried to reproduce the problem
>> > on my sid laptop in cleanly deboostrap-ed sid chroot and was unable to
>> > hit this issue. This maybe indicates that kernel matters or maybe
>> > there is something else in the host that is relevant.
>>
>> For the record: While checking for "dpkg-buildpackage -A", I was also
>> able to reproduce this problem in the past:
>>
>> Running death test 0...make[2]: *** wait: No child processes.  Stop.
>> make[2]: *** Waiting for unfinished jobs
>> make[2]: *** wait: No child processes.  Stop.
>> make[1]: *** wait: No child processes.  Stop.
>> make[1]: *** Waiting for unfinished jobs
>> make[1]: *** wait: No child processes.  Stop.
>> make: *** wait: No child processes.  Stop.
>> make: *** Waiting for unfinished jobs
>> make: *** wait: No child processes.  Stop.
>> Build killed with signal TERM after 150 minutes of inactivity
>>
>> I'm also using sbuild, triggered by a cron job.
>
> Do you still need help to reproduce the issue? Indeed it was the
> equivalent of dpkg-buildpackage -A that triggered it.

I got sbuild set up on my box (via instructions at
https://wiki.debian.org/sbuild) and even under sbuild I am unable to
reproduce the problem.

So maybe this is something with kernel? Should I try to get, say
recent stable installed under KVM? I am running on fairly up-to-date
unstable distro.

Bug#831980: python3-qrcode: fails to upgrade from 'testing' - trying to overwrite /usr/share/man/man1/qr.1.gz

[Andreas Beckmann]

Package: python3-qrcode
Version: 5.0.1-1.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package python3-qrcode.
  Preparing to unpack .../python3-qrcode_5.0.1-1.1_all.deb ...
  Unpacking python3-qrcode (5.0.1-1.1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-qrcode_5.0.1-1.1_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man1/qr.1.gz', which is also in package 
python-qrcode 5.0.1-1
  Processing triggers for mime-support (3.58) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-qrcode_5.0.1-1.1_all.deb


cheers,

Andreas


python-qrcode=5.0.1-1_python3-qrcode=5.0.1-1.1.log.gz
Description: application/gzip

Bug#831116: marked as done (nfstrace: FTBFS with GCC 6: nfs_procedure.h:111:9: error: this 'if' clause does not guard... [-Werror=misleading-indentation])

[Debian Bug Tracking System]

Your message dated Wed, 20 Jul 2016 23:00:55 +
with message-id 
and subject line Bug#831116: fixed in nfstrace 0.4.2-1
has caused the Debian Bug report #831116,
regarding nfstrace: FTBFS with GCC 6: nfs_procedure.h:111:9: error: this 'if' 
clause does not guard... [-Werror=misleading-indentation]
to be marked as done.

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

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


-- 
831116: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831116
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nfstrace
Version: 0.4.1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64

Hi,

During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html

Relevant part (hopefully):
> /usr/bin/c++-I/«PKGBUILDDIR»/src  -g -O2 -fstack-protector-strong 
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -std=c++11 
> -pedantic -Wall -Werror -Wextra -fPIC -fvisibility=hidden   -o 
> CMakeFiles/nfstrace.dir/src/analysis/analysis_manager.cpp.o -c 
> /«PKGBUILDDIR»/src/analysis/analysis_manager.cpp
> In file included from /«PKGBUILDDIR»/src/analysis/nfs_parser.h:28:0,
>  from /«PKGBUILDDIR»/src/analysis/parsers.h:27,
>  from /«PKGBUILDDIR»/src/analysis/analysis_manager.h:32,
>  from /«PKGBUILDDIR»/src/analysis/analysis_manager.cpp:22:
> /«PKGBUILDDIR»/src/protocols/nfs/nfs_procedure.h: In destructor 
> 'NST::protocols::NFSProcedure::~NFSProcedure()':
> /«PKGBUILDDIR»/src/protocols/nfs/nfs_procedure.h:111:9: error: this 'if' 
> clause does not guard... [-Werror=misleading-indentation]
>  if(pres) xdr_free((xdrproc_t)proc_t_of(res), (char*)&res  );
>  ^~
> /«PKGBUILDDIR»/src/protocols/nfs/nfs_procedure.h:112:18: note: ...this 
> statement, but the latter is misleadingly indented as if it is guarded by the 
> 'if'
>   xdr_free((xdrproc_t)xdr_replymsg,   (char*)&reply);
>   ^~~~
> cc1plus: all warnings being treated as errors
> make[3]: *** [CMakeFiles/nfstrace.dir/src/analysis/analysis_manager.cpp.o] 
> Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/13/nfstrace_0.4.1-1_unstable_gcc6.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.
--- End Message ---
--- Begin Message ---
Source: nfstrace
Source-Version: 0.4.2-1

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

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

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

Debian distribution maintenance software
pp.
Andrew Shadura  (supplier of updated nfstrace package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 20 Jul 2016 11:16:55 +0200
Source: nfstrace
Binary: nfstrace nfstrace-doc
Architecture: source amd64 all
Version: 0.4.2-1
Distribution: unstable
Urgency: medium
Maintainer: Andrew Shadura 
Changed-By: Andrew Shadura 
Description:
 nfstrace   - NFS tracing/monitoring/capturing/analyzing tool
 nfstrace-doc - NFS tracing/monitoring/capturing/analyzing tool (documentation)
Closes: 831116 831570
Changes:
 nfstrace (0.4.2-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #831116).
   * Make the build reproducible (Closes: #831570).
   * Make the documentation buildable again.
Checksums-Sha1:
 900f0a037604b69c549fe3d4596f928c3a6b2b90 1715 nfstrace_0.4.2-1.dsc
 98b3f9c2432b80d43731db9e5007269f88288144 18527347 nfstrace_0.4.2.orig.tar.gz
 8094f70d459e461ef93561e57c21ee363d785917 2980 nfstrace_0.4.2-1.debian.tar.xz
 5e036f5672d64a2309

Bug#811631: marked as done (FTBFS with GCC 6: cannot convert x to y)

[Debian Bug Tracking System]

Your message dated Wed, 20 Jul 2016 23:00:11 +
with message-id 
and subject line Bug#811631: fixed in libkolabxml 1.1.4-1
has caused the Debian Bug report #811631,
regarding FTBFS with GCC 6: cannot convert x to y
to be marked as done.

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

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


-- 
811631: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811631
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libkolabxml
Version: 1.1.1-3
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-cannot-convert

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

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

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> In file included from /<>/./src/xcalconversions.h:24:0,
>  from /<>/tests/conversiontest.cpp:4:
> /<>/obj-x86_64-linux-gnu/bindings/kolabformat-xcal.hxx:3006:25: 
> warning: 'template class std::auto_ptr' is deprecated 
> [-Wdeprecated-declarations]
>   ::std::auto_ptr< x_kolab_version_type >);
>  ^~~~
> 
> In file included from /usr/include/c++/6/memory:81:0,
>  from /usr/include/xsd/cxx/tree/elements.hxx:23,
>  from 
> /<>/obj-x86_64-linux-gnu/bindings/kolabformat-xcal.hxx:61,
>  from /<>/./src/xcalconversions.h:24,
>  from /<>/tests/conversiontest.cpp:4:
> /usr/include/c++/6/bits/unique_ptr.h:49:28: note: declared here
>template class auto_ptr;
> ^~~~
> 
> In file included from /usr/include/qt4/QtTest/qtest.h:46:0,
>  from /usr/include/qt4/QtTest/QTest:1,
>  from /<>/tests/kolabconversationtest.cpp:21:
> /<>/tests/kolabconversationtest.cpp: In member function 'void 
> KolabConversationTest::configurationDeserialationTest()':
> /<>/tests/kolabconversationtest.cpp:30:5: error: cannot convert 
> 'boost::shared_ptr' to 'bool' for argument '1' to 'bool 
> QTest::qVerify(bool, const char*, const char*, const char*, int)'
>  QVERIFY(ptr);
>  ^
> 
> In file included from /<>/./src/xcalconversions.h:24:0,
>  from /<>/tests/conversiontest.cpp:4:
> /<>/obj-x86_64-linux-gnu/bindings/kolabformat-xcal.hxx:3158:10: 
> warning: 'template class std::auto_ptr' is deprecated 
> [-Wdeprecated-declarations]
>::std::auto_ptr< ::icalendar_2_0::IcalendarType >
>   ^~~~
> 
> In file included from /usr/include/c++/6/memory:81:0,
>  from /usr/include/xsd/cxx/tree/elements.hxx:23,
>  from 
> /<>/obj-x86_64-linux-gnu/bindings/kolabformat-xcal.hxx:61,
>  from /<>/./src/xcalconversions.h:24,
>  from /<>/tests/conversiontest.cpp:4:
> /usr/include/c++/6/bits/unique_ptr.h:49:28: note: declared here
>template class auto_ptr;
> ^~~~
> 
> /<>/tests/kolabconversationtest.cpp: In member function 'void 
> KolabConversationTest::noteDeserialationTest()':
> /<>/tests/kolabconversationtest.cpp:39:5: error: cannot convert 
> 'boost::shared_ptr' to 'bool' for argument '1' to 'bool 
> QTest::qVerify(bool, const char*, const char*, const char*, int)'
>  QVERIFY(ptr);
>  ^
> 

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: libkolabxml
Source-Version: 1.1.4-1

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

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

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

Debian distribution maintenance software
pp.
Maximiliano Curia  (supplier of updated libkolabxml package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 20 Jul 2016 17:04:15 +0200
Source: libkolabxml
Binary: libkolabxml1v5 python-kolabformat python3-kolabformat libkolabxml-dev
Architecture: source amd64
Version: 1.1.4-1
Distribution: uns

Bug#831984: zoneminder: modifies shipped file: /usr/share/zoneminder/www/api/app/Config/core.php

[Andreas Beckmann]

Package: zoneminder
Version: 1.30.0~rc2+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package modifies a shipped
file:

1m41.6s ERROR: FAIL: debsums reports modifications inside the chroot:
  /usr/share/zoneminder/www/api/app/Config/core.php

Whatever you are trying to achieve here, this is *wrong*.


Andreas


zoneminder_1.30.0~rc2+dfsg-1.log.gz
Description: application/gzip

Processed: Bug#831868 marked as pending

[Debian Bug Tracking System]

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

> tag 831868 pending
Bug #831868 [python-jwt] python-jwt: ships 
/usr/lib/python2.7/dist-packages/.coverage
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#831868: marked as pending

[Daniele Tricoli]

tag 831868 pending
thanks

Hello,

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


http://git.debian.org/?p=python-modules/packages/pyjwt.git;a=commitdiff;h=977d5a0

---
commit 977d5a0752f3b09fa552f6af3624fb90fc943bee
Author: Daniele Tricoli 
Date:   Thu Jul 21 00:11:31 2016 +0200

Update changelog for 1.4.1-1

diff --git a/debian/changelog b/debian/changelog
index 39689d1..54ca609 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -2,11 +2,13 @@ pyjwt (1.4.1-1) UNRELEASED; urgency=medium
 
   * New upstream release.
   * Run "as-installed" tests (DEP8).
+  * debian/patches/01_do-not-use-pytest-runner.patch
+- Drop since python{,3}-pytest-runner is in Debian.
   * debian/rules
-- Make the build reproducible. (Closes: #828131)
+- Make the build reproducible. (Closes: #828131, #831868)
   Thanks to Chris Lamb for report and patch.
 
- -- Daniele Tricoli   Wed, 20 Jul 2016 15:14:54 +0200
+ -- Daniele Tricoli   Thu, 21 Jul 2016 00:07:43 +0200
 
 pyjwt (1.4.0-1) unstable; urgency=medium
 

Bug#796608: espeakup: diff for NMU version 1:0.71-27.1

[Samuel Thibault]

Hello,

Michael Biebl, on Wed 20 Jul 2016 02:54:14 +0200, wrote:
> Am 20.07.2016 um 01:03 schrieb Michael Biebl:
> > Right. I think this is the problem. Afair, systemd will try to read the
> > pid file as soon as the parent exits. That should happen *after* the
> > forked daemon process is ready and has written the pid file.
> > 
> > See man daemon(7). 
> 
> https://www.freedesktop.org/software/systemd/man/daemon.html#SysV%20Daemons

Thanks for the pointer!

> I guess this issue should be turned into a separate bug report as it's
> no longer about #796608

It's actually #775131, which I'll close along with fixing daemonizing.

Samuel

Bug#817688: marked as done (tendra: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Thu, 21 Jul 2016 01:26:44 +0200
with message-id <00d2ed62-682a-104c-8b3b-b5fdccc9a...@debian.org>
and subject line tendra was removed from unstable
has caused the Debian Bug report #817688,
regarding tendra: Removal of debhelper compat 4
to be marked as done.

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

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


-- 
817688: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817688
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tendra
Severity: important
Usertags: compat-4-removal

Hi,

The package tendra uses debhelper with a compat level of 4,
which is deprecated and scheduled for removal.

 * Please bump the debhelper compat at your earliest convenience.
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Compat level 4 will be removed on the first debhelper upload after
   the 15th of June.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Version: 4.1.2-19+rm

tendra was just removed from unstable, but the old bugs were forgotten
to be closed at the same time
see https://bugs.debian.org/831695 for details on the removal


Andreas--- End Message ---

Bug#642403: marked as done (tendra ftbfs on i386)

[Debian Bug Tracking System]

Your message dated Thu, 21 Jul 2016 01:26:44 +0200
with message-id <00d2ed62-682a-104c-8b3b-b5fdccc9a...@debian.org>
and subject line tendra was removed from unstable
has caused the Debian Bug report #642403,
regarding tendra ftbfs on i386
to be marked as done.

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

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


-- 
642403: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642403
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tendra
Version: 4.1.2-19
Severity: serious
Tags: sid wheezy

building tdf ...
creating /home/packages/tmp/u/tendra-4.1.2/work/linux/2.6.38-8-server/80x86/tdf 
...
make[1]: Entering directory
`/home/packages/tmp/u/tendra-4.1.2/work/linux/2.6.38-8-server/80x86/tdf'
tcc  -Ypl_tdf -jtarget_tok -c -o INT64.o -M
-WP,-I/home/packages/tmp/u/tendra-4.1.2/src/lib/libtdf
/home/packages/tmp/u/tendra-4.1.2/src/lib/libtdf/INT64a.c
/home/packages/tmp/u/tendra-4.1.2/src/lib/libtdf/INT64b.pl
/home/packages/tmp/u/tendra-4.1.2/src/lib/libtdf/abstract.pl
tld: Error: cannot open library file 'target_tok': No such file or directory
tld: Error: cannot open library file 'ansi': No such file or directory
make[1]: *** [INT64.o] Error 1
make[1]: Leaving directory
`/home/packages/tmp/u/tendra-4.1.2/work/linux/2.6.38-8-server/80x86/tdf'
compilation failed ...

building cpp ...
creating /home/packages/tmp/u/tendra-4.1.2/work/linux/2.6.38-8-server/80x86/cpp 
...
make[1]: Entering directory
`/home/packages/tmp/u/tendra-4.1.2/work/linux/2.6.38-8-server/80x86/cpp'
tcc -Yc++  -c /home/packages/tmp/u/tendra-4.1.2/src/lib/cpp/src/baseinfo.cc
tld: Error: cannot open library file 'ansi': No such file or directory
make[1]: *** [baseinfo.o] Error 1
make[1]: Leaving directory
`/home/packages/tmp/u/tendra-4.1.2/work/linux/2.6.38-8-server/80x86/cpp'
compilation failed ...

installation completed with errors
make: *** [build-stamp] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2


--- End Message ---
--- Begin Message ---
Version: 4.1.2-19+rm

tendra was just removed from unstable, but the old bugs were forgotten
to be closed at the same time
see https://bugs.debian.org/831695 for details on the removal


Andreas--- End Message ---

Bug#732145: marked as done (tendra: does not install: SIGSEGV)

[Debian Bug Tracking System]

Your message dated Thu, 21 Jul 2016 01:26:44 +0200
with message-id <00d2ed62-682a-104c-8b3b-b5fdccc9a...@debian.org>
and subject line tendra was removed from unstable
has caused the Debian Bug report #732145,
regarding tendra: does not install: SIGSEGV
to be marked as done.

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

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


-- 
732145: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732145
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tendra
Version: 4.1.2-19
Severity: grave
Justification: renders package unusable

A screenshot says more than a thousand words ☺

tglase@tglase:~ $ sudo apt-get install tendra
[sudo] password for tglase:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
Suggested packages:
  tendra-doc
The following NEW packages will be installed:
  tendra
0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
Need to get 2107 kB of archives.
After this operation, 12.4 MB of additional disk space will be used.
Get:1 http://http.debian.net/debian/ sid/main tendra i386 4.1.2-19 [2107 kB]
Fetched 2107 kB in 7s (301 kB/s)
Selecting previously unselected package tendra.
(Reading database ... 231746 files and directories currently installed.)
Preparing to unpack .../tendra_4.1.2-19_i386.deb ...
Unpacking tendra (4.1.2-19) ...
Processing triggers for man-db (2.6.5-2) ...
Setting up tendra (4.1.2-19) ...
Segment violation (core dumped) 
dpkg: error processing package tendra (--configure):
 subprocess installed post-installation script returned error exit status 139
Errors were encountered while processing:
 tendra

Please fix this, I’d hate to see TenDRA be RM’d. Thanks!

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

Kernel: Linux 3.11-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh

Versions of packages tendra depends on:
ii  binutils  2.24-2
ii  libc6 2.17-97

Versions of packages tendra recommends:
ii  libc6-dev [libc-dev]  2.17-97

Versions of packages tendra suggests:
pn  tendra-doc  

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 4.1.2-19+rm

tendra was just removed from unstable, but the old bugs were forgotten
to be closed at the same time
see https://bugs.debian.org/831695 for details on the removal


Andreas--- End Message ---

Processed: your mail

[Debian Bug Tracking System]

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

> notfixed 818814 2.0.2
Bug #818814 {Done: "Barak A. Pearlmutter" } [mlpack] mlpack: 
FTBFS with libc 2.23: there are no arguments to 'isnan' that depend on a 
template parameter
There is no source info for the package 'mlpack' at version '2.0.2' with 
architecture ''
Unable to make a source version for version '2.0.2'
No longer marked as fixed in versions 2.0.2.
> fixed 818814 2.0.2-1
Bug #818814 {Done: "Barak A. Pearlmutter" } [mlpack] mlpack: 
FTBFS with libc 2.23: there are no arguments to 'isnan' that depend on a 
template parameter
There is no source info for the package 'mlpack' at version '2.0.2-1' with 
architecture ''
Unable to make a source version for version '2.0.2-1'
Marked as fixed in versions 2.0.2-1.
> thanks
Stopping processing here.

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

Bug#831978: marked as done (ring-daemon: Internal daemon started by users should not be in /usr/sbin/)

[Debian Bug Tracking System]

Your message dated Thu, 21 Jul 2016 00:23:48 +
with message-id 
and subject line Bug#831978: fixed in ring 20160720.3.73cfbb9~dfsg1-5
has caused the Debian Bug report #831978,
regarding ring-daemon: Internal daemon started by users should not be in 
/usr/sbin/
to be marked as done.

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

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


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

Package: ring-daemon
Version: 20160720.3.73cfbb9~dfsg1-2
Severity: serious

The /usr/sbin/dring in the ring-daemon package seem to be placed in the
wrong directory.  The program is started by the ring GUI tool when a
user starts the Ring client, and thus is not a tool intended for sbin,
as specified by FHS[1] refered from Debian Policy[2]:

  Utilities used for system administration (and other root-only
  commands) are stored in /sbin, /usr/sbin, and /usr/local/sbin. /sbin
  contains binaries essential for booting, restoring, recovering, and/or
  repairing the system in addition to the binaries in /bin. [18]
  Programs executed after /usr is known to be mounted (when there are no
  problems) are generally placed into /usr/sbin. Locally-installed
  system administration programs should be placed into
  /usr/local/sbin.

If it is supposed to be called directly by users, I suspect it belong in
/usr/bin/.  If not, it probably belong in /usr/lib/ring/ or similar.

Setting severity to serious, as this issue is about breaking the
requirement in the Debian policy section 9.1.1.

 [1] https://www.debian.org/doc/packaging-manuals/fhs/fhs-2.3.html#SBINSYSTEMBINARIES
 >
 [2] https://www.debian.org/doc/debian-policy/ch-opersys.html >
-- 
Happy hacking
Petter Reinholdtsen
--- End Message ---
--- Begin Message ---
Source: ring
Source-Version: 20160720.3.73cfbb9~dfsg1-5

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

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

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

Debian distribution maintenance software
pp.
Alexandre Viau  (supplier of updated ring package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 20 Jul 2016 19:05:07 -0400
Source: ring
Binary: ring ring-daemon
Architecture: source amd64
Version: 20160720.3.73cfbb9~dfsg1-5
Distribution: unstable
Urgency: medium
Maintainer: Debian VoIP Team 
Changed-By: Alexandre Viau 
Description:
 ring   - Secure and distributed voice, video and chat platform - desktop c
 ring-daemon - Secure and distributed voice, video and chat platform - daemon
Closes: 831978
Changes:
 ring (20160720.3.73cfbb9~dfsg1-5) unstable; urgency=medium
 .
   * Move dring to /usr/bin. (Closes: #831978)
Checksums-Sha1:
 f0cb24db1520a508492f7ecd74b38f9844688d27 2781 
ring_20160720.3.73cfbb9~dfsg1-5.dsc
 4d8ea02a593de71142204d7c5962b9f75fc0ddf2 12668 
ring_20160720.3.73cfbb9~dfsg1-5.debian.tar.xz
 2fb4f4a417c468b7a4e54b7cbfe97eaf75e898bf 18175822 
ring-daemon-dbgsym_20160720.3.73cfbb9~dfsg1-5_amd64.deb
 a17c2fc9f023e82db4ccbc57136e0e5ede9d44d5 2201426 
ring-daemon_20160720.3.73cfbb9~dfsg1-5_amd64.deb
 3b7c3155b504bd1ade9e3f3adcb61fbd4986f044 22666166 
ring-dbgsym_20160720.3.73cfbb9~dfsg1-5_amd64.deb
 cbb5da916a1f927565c3f65f1ccf0a26faa1057c 1508898 
ring_20160720.3.73cfbb9~dfsg1-5_amd64.deb
Checksums-Sha256:
 84fa69818f513b34764d6e555985ca84f10ccb2f9e449e7577fccf461ba785b7 2781 
ring_20160720.3.73cfbb9~dfsg1-5.dsc
 c0b3747000e721bbf52d0b5915e86826bae1d644df3935ce95e29ff91e23 12668 
ring_20160720.3.73cfbb9~dfsg1-5.debian.tar.xz
 7b48716ea90315ba9d8c26a7eb16bce11106421966e310bd677093a2c3c0e3c7 18175822 
ring-daemon-dbgsym_20160720.3.73cfbb9~dfsg1-5_amd64.deb
 9daeb07c1ebcacb755207cd4b58447a17050129978fe136f23699500dbf5c168 2201426 
ring-daemon_20160720.3.73cfbb9~dfsg1-5_amd64.deb
 93e755c54925723ac71652df92f47e5bf610fa8bbc2bf0bf3fd49ff276641e7d 22666166 
ring-dbgsym_20160720.3.73cfbb9~dfsg1-5_amd64.deb
 f6b34cde812b446c0e679df82a142ceebf986287c6f64364bf4818578f1be019 1508898 
ring_20160720.3.73cfbb9~dfsg1-5_amd64.deb
Files:
 c66cb2a2fb16f21404866b7dd25fe613 2781 comm extra 
ring_20160720.3.73cfbb9~dfsg1-5.dsc
 ef2d8e7c4b57ae34d9f0357

Bug#831984: zoneminder: modifies shipped file: /usr/share/zoneminder/www/api/app/Config/core.php

[Dmitry Smirnov]

On Thursday, 21 July 2016 1:08:10 AM AEST Andreas Beckmann wrote:
> Package: zoneminder
> Version: 1.30.0~rc2+dfsg-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package modifies a shipped
> file:
> 
> 1m41.6s ERROR: FAIL: debsums reports modifications inside the chroot:
>   /usr/share/zoneminder/www/api/app/Config/core.php
> 
> Whatever you are trying to achieve here, this is *wrong*.

Andreas, Chris,

I guess you guys can have an interesting discussion about clash between 
#830979 and #831984. ;)

-- 
Cheers,
 Dmitry Smirnov.

---

It is no use saying, 'We are doing our best.' You have got to succeed
in doing what is necessary.
-- Winston Churchill


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

Bug#831984: zoneminder: modifies shipped file: /usr/share/zoneminder/www/api/app/Config/core.php

[Andreas Beckmann]

On 2016-07-21 02:57, Dmitry Smirnov wrote:
> I guess you guys can have an interesting discussion about clash between 
> #830979 and #831984. ;)

Well, you don't edit shipped files. Neither conffiles nor normal files.
Instead, you put these values into a new file (not a shipped file!,
maybe ship a template in /usr/share/$pkg) in either /etc or /var (with a
symlink in /usr pointing to it) that is solely managed by the maintainer
scripts.

Also the question arises: *when* should these values be regenerated?
* upon initial installation only?
* upon upgrade?
* upon package reconfiguration?
* upon reboot?
* every 42 minutes?


Andreas

Bug#830555: new Foolscap release available

[Brian Warner]

I've just released foolscap-0.12.0 to PyPI, which should fix this. We've
deprecated a function that talks to the root nameservers, and this
release removes the test that used to exercise that function. I think
that was the only place which should be doing off-box network access
(there's plenty of localhost access, of course, this being a networking
package).

I hope that will resolve the issue. Please let me know if there's
anything I can do to help get this packaged and (most importantly) the
auto-removal of Foolscap and Tahoe-LAFS resolved.

thanks!
 -Brian

Processed: here's a patch

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +patch
Bug #811622 [crtmpserver] FTBFS with GCC 6: cannot convert x to y
Added tag(s) patch.

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

Bug#811622: here's a patch

[Adam Borowski]

control: tags -1 +patch

Here's a patch (attached).  It is pretty massive, but all errors are of two
kinds: C++11 considers letters after a string literal to be a suffix rather
than a separate token, and implicit conversions from bool to pointer.

-- 
An imaginary friend squared is a real enemy.
>From b66c8027c3cb0636efd3ea26fa296b533f6606c6 Mon Sep 17 00:00:00 2001
From: Adam Borowski 
Date: Thu, 21 Jul 2016 03:54:22 +0200
Subject: [PATCH] Fix FTBFS with gcc-6.

All of many errors are of only two types:

* letters after string literals, sometimes fatal: "foo"name"bar", sometimes
  merely a warning: "foo"PRIx64 -- I've fixed either
* "return false;" in a function returning a pointer
---
 applications/applestreamingclient/src/playlist.cpp |  2 +-
 .../src/protocols/key/inboundkeyprotocol.cpp   |  2 +-
 common/src/platform/android/androidplatform.cpp|  6 ++--
 common/src/platform/dfreebsd/dfreebsdplatform.cpp  |  6 ++--
 common/src/platform/freebsd/freebsdplatform.cpp|  6 ++--
 common/src/platform/linux/linuxplatform.cpp|  6 ++--
 common/src/platform/openbsd/openbsdplatform.cpp|  6 ++--
 common/src/platform/osx/osxplatform.cpp|  6 ++--
 common/src/platform/solaris/solarisplatform.cpp|  6 ++--
 common/src/utils/logging/fileloglocation.cpp   |  4 +--
 common/src/utils/logging/syslogloglocation.cpp |  2 +-
 common/src/utils/misc/file.cpp | 10 +++
 common/src/utils/misc/mmapfile.cpp | 22 +++---
 common/src/utils/misc/uri.cpp  |  6 ++--
 common/src/utils/misc/variant.cpp  | 34 +++---
 crtmpserver/src/crtmpserver.cpp|  2 +-
 thelib/include/mediaformats/mediaframe.h   |  2 +-
 thelib/include/protocols/ts/tspacketpmt.h  |  2 +-
 thelib/src/application/baseclientapplication.cpp   |  4 +--
 thelib/src/configuration/configfile.cpp|  2 +-
 thelib/src/mediaformats/basemediadocument.cpp  | 10 +++
 thelib/src/mediaformats/flv/flvdocument.cpp|  2 +-
 thelib/src/mediaformats/mp3/mp3document.cpp|  4 +--
 thelib/src/mediaformats/mp4/baseatom.cpp   |  6 ++--
 thelib/src/mediaformats/mp4/boxatom.cpp|  2 +-
 thelib/src/mediaformats/mp4/mp4document.cpp| 14 -
 thelib/src/mediaformats/nsv/nsvdocument.cpp|  2 +-
 thelib/src/netio/epoll/iohandlermanager.cpp|  4 +--
 thelib/src/netio/epoll/udpcarrier.cpp  |  4 +--
 thelib/src/netio/kqueue/iohandlermanager.cpp   |  4 +--
 thelib/src/netio/kqueue/udpcarrier.cpp |  4 +--
 thelib/src/netio/select/iohandlermanager.cpp   |  4 +--
 thelib/src/netio/select/udpcarrier.cpp |  4 +--
 thelib/src/protocols/http/httpauthhelper.cpp   |  2 +-
 thelib/src/protocols/protocolfactorymanager.cpp|  4 +--
 .../rawhttpstream/inboundrawhttpstreamprotocol.cpp |  2 +-
 thelib/src/protocols/rtmp/amf0serializer.cpp   | 28 +-
 .../protocols/rtmp/basertmpappprotocolhandler.cpp  |  8 ++---
 thelib/src/protocols/rtmp/basertmpprotocol.cpp | 10 +++
 thelib/src/protocols/rtmp/header_le_ba.cpp |  2 +-
 thelib/src/protocols/rtmp/inboundhttp4rtmp.cpp |  2 +-
 thelib/src/protocols/rtmp/monitorrtmpprotocol.cpp  |  2 +-
 .../src/protocols/rtmp/rtmpprotocolserializer.cpp  |  2 +-
 .../rtmp/streaming/baseoutnetrtmpstream.cpp|  2 +-
 .../src/protocols/rtmp/streaming/debugging.patch   | 24 +++
 .../rtmp/streaming/infilertmpnsvstream.cpp_| 12 
 .../protocols/rtmp/streaming/infilertmpstream.cpp  | 22 +++---
 .../protocols/rtmp/streaming/innetrtmpstream.cpp   |  4 +--
 .../rtmp/streaming/outnetrtmp4tsstream.cpp |  6 ++--
 .../protocols/rtp/basertspappprotocolhandler.cpp   |  2 +-
 .../rtp/connectivity/inboundconnectivity.cpp   |  6 ++--
 .../rtp/connectivity/outboundconnectivity.cpp  |  8 ++---
 thelib/src/protocols/rtp/nattraversalprotocol.cpp  |  4 +--
 thelib/src/protocols/rtp/rtspprotocol.cpp  |  8 ++---
 thelib/src/protocols/rtp/sdp.cpp   |  4 +--
 .../src/protocols/rtp/streaming/innetrtpstream.cpp | 24 +++
 thelib/src/protocols/ssl/basesslprotocol.cpp   |  4 +--
 thelib/src/protocols/ts/innettsstream.cpp  |  4 +--
 thelib/src/protocols/ts/tspacketpat.cpp|  4 +--
 thelib/src/protocols/ts/tspacketpmt.cpp|  4 +--
 thelib/src/streaming/baseinfilestream.cpp  | 10 +++
 thelib/src/streaming/streamcapabilities.cpp| 16 +-
 thelib/src/streaming/streamsmanager.cpp|  2 +-
 63 files changed, 216 insertions(+), 216 deletions(-)

diff --git a/applications/applestreamingclient/src/playlist.cpp b/applications/applestreamingclient/src/playlist.cpp
index b5feb64..6c119af 100644
--- a/applications/applestreamingclient/src/playlist.cpp
+++ b/applications/applestreamingclient/src/playlist.cpp
@@ -223,7 +223,7 @@ uint32_t Pl

Bug#824896: the patch is bogus

[Adam Borowski]

control: tags -1 -patch

The only actual error in the copyright file that I know is claiming GPL2+
instead of GPL2 for most files.

On the other hand, the proposed patch introduces about as many serious
errors as it has entries; it's beyond worthless.

-- 
An imaginary friend squared is a real enemy.

Processed: the patch is bogus

[Debian Bug Tracking System]

Processing control commands:

> tags -1 -patch
Bug #824896 [btrfs-progs] [PATCH] fix serious errors in debian/copyright
Removed tag(s) patch.

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

Bug#829188: icedove SEGV backtrace

[Benoît Ganne]

>   LANG= /usr/lib/icedove/run-mozilla.sh -g /usr/lib/icedove/icedove-bin
> --safe-mode 2>&1 | tee /tmp/icedove-gdb-$(apt-cache show icedove | grep
> Version | awk '{ print $2 }')_$(date +%F_%T).log

I just reproduced the crash with the above command, please find the
logfile including backtrace (gzip'ed) attached.
Hope this help.

ben

icedove-gdb-1:45.2.0-1.gz
Description: GNU Zip compressed data

Processed: Re: [Reproducible-builds] Bug#831897: lepton: leaves a zombie process around after build

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/dropbox/lepton/issues/42
Bug #831897 [lepton] lepton: leaves a zombie process around after build
Set Bug forwarded-to-address to 'https://github.com/dropbox/lepton/issues/42'.

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

Bug#831897: [Reproducible-builds] Bug#831897: lepton: leaves a zombie process around after build

[陳昌倬]

Control: forwarded -1 https://github.com/dropbox/lepton/issues/42

On Wed, Jul 20, 2016 at 04:12:51PM +, Mattia Rizzolo wrote:
> That said, I find totally unacceptable for a build to leak a process and
> leave it zombie (because that process had no parent, actually), so I'm
> filing this at RC level.

Thanks for the report. I will look into it.

-- 
ChangZhuo Chen (陳昌倬) 
Debian Developer (https://nm.debian.org/public/person/czchen)
Key fingerprint = EC9F 905D 866D BE46 A896  C827 BE0C 9242 03F4 552D
  BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


signature.asc
Description: PGP signature

Bug#817424: here's a patch

[Adam Borowski]

control: tags -1 +patch

Hi!
Here's a patch migrating debfoster to dh 9, fixing the FTBFS.

I've moved the bash_completion file to a dir on its own to simplify the
packaging -- debian/rules is now the usual dh two-liner.


Meow!
-- 
An imaginary friend squared is a real enemy.
>From 0eb439c5dc0816aa1f38150fae518818f2e03bd8 Mon Sep 17 00:00:00 2001
From: Adam Borowski 
Date: Thu, 21 Jul 2016 06:36:31 +0200
Subject: [PATCH] dh 9

---
 debian/bash_completion/debfoster | 41 +++
 debian/compat|  2 +-
 debian/control   |  2 +-
 debian/debfoster.bash_completion | 41 ---
 debian/install   |  2 +
 debian/rules | 85 +---
 6 files changed, 47 insertions(+), 126 deletions(-)
 create mode 100644 debian/bash_completion/debfoster
 delete mode 100644 debian/debfoster.bash_completion
 create mode 100644 debian/install

diff --git a/debian/bash_completion/debfoster b/debian/bash_completion/debfoster
new file mode 100644
index 000..0c6e3ac
--- /dev/null
+++ b/debian/bash_completion/debfoster
@@ -0,0 +1,41 @@
+# -*- sh -*-
+
+# Provided by Eric Hansander  in
+# 
+
+have debfoster &&
+_debfoster()
+{
+local cur prev options
+
+COMPREPLY=()
+cur=${COMP_WORDS[COMP_CWORD]}
+prev=${COMP_WORDS[COMP_CWORD-1]}
+options='-v --verbose -V --version -h --help -q --quiet -f --force \
+  -m --mark-only -u --upgrade -c --config -k --keeperfile -n \
+  --no-keeperfile -i --ignore-default-rules -a --show-keepers -s \
+  --show-orphans -d --show-depends -e --show-dependents -p \
+  --show-providers -r --show-related -t --use-tasks -o --option'
+
+case $prev in
+-@(c|-config|k|-keeperfile))
+_filedir
+return 0
+;;
+-@(d|-show-depends|e|-show-dependents|r|-show-related))
+COMPREPLY=( $( _comp_dpkg_installed_packages $cur ) )
+return 0
+;;
+esac
+
+if [[ "$cur" == -* ]]; then
+COMPREPLY=( $( compgen -W "$options" -- $cur ) )
+else
+# This is just an approximation.  Actually, debfoster can
+# install new packages, which won't appear in that list.
+COMPREPLY=( $( _comp_dpkg_installed_packages $cur ) )
+fi
+
+return 0
+}
+test "$have" && complete -F _debfoster $default debfoster
diff --git a/debian/compat b/debian/compat
index b8626c4..ec63514 100644
--- a/debian/compat
+++ b/debian/compat
@@ -1 +1 @@
-4
+9
diff --git a/debian/control b/debian/control
index 80a4dfc..228b0c9 100644
--- a/debian/control
+++ b/debian/control
@@ -3,7 +3,7 @@ Section: admin
 Priority: optional
 Maintainer: debfoster Maintainer Team 
 Uploaders: Andreas Barth , Marc Haber , Florian Weimer 
-Build-Depends: debhelper (>> 4.0.0), gettext, libgc-dev
+Build-Depends: debhelper (>> 9), gettext, libgc-dev
 Standards-Version: 3.7.2
 
 Package: debfoster
diff --git a/debian/debfoster.bash_completion b/debian/debfoster.bash_completion
deleted file mode 100644
index 0c6e3ac..000
--- a/debian/debfoster.bash_completion
+++ /dev/null
@@ -1,41 +0,0 @@
-# -*- sh -*-
-
-# Provided by Eric Hansander  in
-# 
-
-have debfoster &&
-_debfoster()
-{
-local cur prev options
-
-COMPREPLY=()
-cur=${COMP_WORDS[COMP_CWORD]}
-prev=${COMP_WORDS[COMP_CWORD-1]}
-options='-v --verbose -V --version -h --help -q --quiet -f --force \
-  -m --mark-only -u --upgrade -c --config -k --keeperfile -n \
-  --no-keeperfile -i --ignore-default-rules -a --show-keepers -s \
-  --show-orphans -d --show-depends -e --show-dependents -p \
-  --show-providers -r --show-related -t --use-tasks -o --option'
-
-case $prev in
--@(c|-config|k|-keeperfile))
-_filedir
-return 0
-;;
--@(d|-show-depends|e|-show-dependents|r|-show-related))
-COMPREPLY=( $( _comp_dpkg_installed_packages $cur ) )
-return 0
-;;
-esac
-
-if [[ "$cur" == -* ]]; then
-COMPREPLY=( $( compgen -W "$options" -- $cur ) )
-else
-# This is just an approximation.  Actually, debfoster can
-# install new packages, which won't appear in that list.
-COMPREPLY=( $( _comp_dpkg_installed_packages $cur ) )
-fi
-
-return 0
-}
-test "$have" && complete -F _debfoster $default debfoster
diff --git a/debian/install b/debian/install
new file mode 100644
index 000..e8c99f8
--- /dev/null
+++ b/debian/install
@@ -0,0 +1,2 @@
+debian/debfoster2aptitude usr/sbin/
+debian/bash_completion/debfoster etc/bash_completion.d/
diff --git a/debian/rules b/debian/rules
index a19d653..be1a4c2 100755
--- a/debian/rules
+++ b/debian/rules
@@ -1,86 +1,5 @@
 #!/usr/bin/make -f
-# Sample debian/rules that uses debhelper.
-# GNU copyright 1997 to 1999 by Joey Hess.
-
-# Uncomment this t

Processed: here's a patch

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +patch
Bug #817424 [src:debfoster] debfoster: Removal of debhelper compat 4
Added tag(s) patch.

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

Bug#811667: marked as done (FTBFS with GCC 6: cannot convert x to y)

[Debian Bug Tracking System]

Your message dated Thu, 21 Jul 2016 05:48:28 +
with message-id 
and subject line Bug#811667: fixed in cal3d 0.11.0-7
has caused the Debian Bug report #811667,
regarding FTBFS with GCC 6: cannot convert x to y
to be marked as done.

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

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


-- 
811667: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811667
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cal3d
Version: 0.11.0-6
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-cannot-convert

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

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

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> libtool: compile:  x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I../.. 
> -I../../src -Wdate-time -D_FORTIFY_SOURCE=2 -I../../src -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall -fPIC 
> -fno-rtti -c loader.cpp  -fPIC -DPIC -o .libs/loader.o
> loader.cpp: In static member function 'static CalCoreKeyframe* 
> CalLoader::loadCoreKeyframe(CalDataSource&)':
> loader.cpp:889:12: error: cannot convert 'bool' to 'CalCoreKeyframe*' in 
> return
>  return false;
> ^
> 
> loader.cpp: In static member function 'static CalCoreSkeletonPtr 
> CalLoader::loadXmlCoreSkeleton(const string&)':
> loader.cpp:1341:11: error: could not convert 'false' from 'bool' to 
> 'CalCoreSkeletonPtr {aka cal3d::RefPtr}'
> return false;
>^
> 
> loader.cpp:1347:11: error: could not convert 'false' from 'bool' to 
> 'CalCoreSkeletonPtr {aka cal3d::RefPtr}'
> return false;
>^
> 
> loader.cpp:1356:10: error: could not convert 'false' from 'bool' to 
> 'CalCoreSkeletonPtr {aka cal3d::RefPtr}'
>return false;
>   ^
> 
> loader.cpp:1362:10: error: could not convert 'false' from 'bool' to 
> 'CalCoreSkeletonPtr {aka cal3d::RefPtr}'
>return false;
>   ^
> 
> loader.cpp:1368:10: error: could not convert 'false' from 'bool' to 
> 'CalCoreSkeletonPtr {aka cal3d::RefPtr}'
>return false;
>   ^
> 
> loader.cpp:1386:11: error: could not convert 'false' from 'bool' to 
> 'CalCoreSkeletonPtr {aka cal3d::RefPtr}'
> return false;
>^
> 
> loader.cpp:1398:11: error: could not convert 'false' from 'bool' to 
> 'CalCoreSkeletonPtr {aka cal3d::RefPtr}'
> return false;
>^
> 
> loader.cpp:1407:11: error: could not convert 'false' from 'bool' to 
> 'CalCoreSkeletonPtr {aka cal3d::RefPtr}'
> return false;
>^
> 
> loader.cpp:1413:11: error: could not convert 'false' from 'bool' to 
> 'CalCoreSkeletonPtr {aka cal3d::RefPtr}'
> return false;
>^
> 
> loader.cpp:1425:11: error: could not convert 'false' from 'bool' to 
> 'CalCoreSkeletonPtr {aka cal3d::RefPtr}'
> return false;
>^
> 
> loader.cpp:1434:11: error: could not convert 'false' from 'bool' to 
> 'CalCoreSkeletonPtr {aka cal3d::RefPtr}'
> return false;
>^
> 
> loader.cpp:1440:11: error: could not convert 'false' from 'bool' to 
> 'CalCoreSkeletonPtr {aka cal3d::RefPtr}'
> return false;
>^
> 
> loader.cpp:1453:11: error: could not convert 'false' from 'bool' to 
> 'CalCoreSkeletonPtr {aka cal3d::RefPtr}'
> return false;
>^
> 
> loader.cpp:1462:11: error: could not convert 'false' from 'bool' to 
> 'CalCoreSkeletonPtr {aka cal3d::RefPtr}'
> return false;
>^
> 
> loader.cpp:1468:11: error: could not convert 'false' from 'bool' to 
> 'CalCoreSkeletonPtr {aka cal3d::RefPtr}'
> return false;
>^
> 
> loader.cpp:1480:11: error: could not convert 'false' from 'bool' to 
> 'CalCoreSkeletonPtr {aka cal3d::RefPtr}'
> return false;
>^
> 
> loader.cpp:1489:11: error: could not convert 'false' from 'bool' to 
> 'CalCoreSkeletonPtr {aka cal3d::RefPtr}'
> return false;
>^
> 
> loader.cpp:1495:11: error: could not convert 'false' from 'bool' to 
> 'CalCoreSkeletonPtr {aka cal3d::RefPtr}'
> return false;
>^
> 
> loader.cpp:1507:11: error: could not convert 'false' from 'bool' to 
> 'CalCoreSkeletonPtr {aka cal3d::RefPtr}'
> return false;
>^
> 
> loader.cpp:1517:11: error: could not convert 'false' from 'bool' to 
> 'C

Bug#831139: marked as done (cal3d: FTBFS with GCC 6: loader.cpp:889:12: error: cannot convert 'bool' to 'CalCoreKeyframe*' in return)

[Debian Bug Tracking System]

Your message dated Thu, 21 Jul 2016 05:48:28 +
with message-id 
and subject line Bug#831139: fixed in cal3d 0.11.0-7
has caused the Debian Bug report #831139,
regarding cal3d: FTBFS with GCC 6: loader.cpp:889:12: error: cannot convert 
'bool' to 'CalCoreKeyframe*' in return
to be marked as done.

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

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


-- 
831139: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831139
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cal3d
Version: 0.11.0-6
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64

Hi,

During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html

Relevant part (hopefully):
> /bin/bash ../../libtool  --tag=CXX   --mode=compile x86_64-linux-gnu-g++ 
> -DHAVE_CONFIG_H -I. -I../.. -I../../src  -Wdate-time -D_FORTIFY_SOURCE=2 
> -I../../src  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
> -Wall -fPIC -fno-rtti -c -o loader.lo loader.cpp
> libtool: compile:  x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I../.. 
> -I../../src -Wdate-time -D_FORTIFY_SOURCE=2 -I../../src -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall -fPIC 
> -fno-rtti -c loader.cpp  -fPIC -DPIC -o .libs/loader.o
> loader.cpp: In static member function 'static CalCoreKeyframe* 
> CalLoader::loadCoreKeyframe(CalDataSource&)':
> loader.cpp:889:12: error: cannot convert 'bool' to 'CalCoreKeyframe*' in 
> return
>  return false;
> ^
> loader.cpp: In static member function 'static CalCoreSkeletonPtr 
> CalLoader::loadXmlCoreSkeleton(const string&)':
> loader.cpp:1341:11: error: could not convert 'false' from 'bool' to 
> 'CalCoreSkeletonPtr {aka cal3d::RefPtr}'
> return false;
>^
> loader.cpp:1347:11: error: could not convert 'false' from 'bool' to 
> 'CalCoreSkeletonPtr {aka cal3d::RefPtr}'
> return false;
>^
> loader.cpp:1356:10: error: could not convert 'false' from 'bool' to 
> 'CalCoreSkeletonPtr {aka cal3d::RefPtr}'
>return false;
>   ^
> loader.cpp:1362:10: error: could not convert 'false' from 'bool' to 
> 'CalCoreSkeletonPtr {aka cal3d::RefPtr}'
>return false;
>   ^
> loader.cpp:1368:10: error: could not convert 'false' from 'bool' to 
> 'CalCoreSkeletonPtr {aka cal3d::RefPtr}'
>return false;
>   ^
> loader.cpp:1386:11: error: could not convert 'false' from 'bool' to 
> 'CalCoreSkeletonPtr {aka cal3d::RefPtr}'
> return false;
>^
> loader.cpp:1398:11: error: could not convert 'false' from 'bool' to 
> 'CalCoreSkeletonPtr {aka cal3d::RefPtr}'
> return false;
>^
> loader.cpp:1407:11: error: could not convert 'false' from 'bool' to 
> 'CalCoreSkeletonPtr {aka cal3d::RefPtr}'
> return false;
>^
> loader.cpp:1413:11: error: could not convert 'false' from 'bool' to 
> 'CalCoreSkeletonPtr {aka cal3d::RefPtr}'
> return false;
>^
> loader.cpp:1425:11: error: could not convert 'false' from 'bool' to 
> 'CalCoreSkeletonPtr {aka cal3d::RefPtr}'
> return false;
>^
> loader.cpp:1434:11: error: could not convert 'false' from 'bool' to 
> 'CalCoreSkeletonPtr {aka cal3d::RefPtr}'
> return false;
>^
> loader.cpp:1440:11: error: could not convert 'false' from 'bool' to 
> 'CalCoreSkeletonPtr {aka cal3d::RefPtr}'
> return false;
>^
> loader.cpp:1453:11: error: could not convert 'false' from 'bool' to 
> 'CalCoreSkeletonPtr {aka cal3d::RefPtr}'
> return false;
>^
> loader.cpp:1462:11: error: could not convert 'false' from 'bool' to 
> 'CalCoreSkeletonPtr {aka cal3d::RefPtr}'
> return false;
>^
> loader.cpp:1468:11: error: could not convert 'false' from 'bool' to 
> 'CalCoreSkeletonPtr {aka cal3d::RefPtr}'
> return false;
>^
> loader.cpp:1480:11: error: could not convert 'false' from 'bool' to 
> 'CalCoreSkeletonPtr {aka cal3d::RefPtr}'
> return false;
>^
> loader.cpp:1489:11: error: could not convert 'false' from 'bool' to 
> 'CalCoreSkeletonPtr {aka cal3d::RefPtr}'
> return false;
>^
> loader.cpp:1495:11: error: could not convert 'false' from 'bool' to 
> 'CalCoreSkeletonPt

Bug#831229: marked as done (libmariadbclient-dev{, -compat}: fails to upgrade from 'sid' - trying to overwrite /usr/bin/mysql_config, /usr/lib/*/libmysqlclient.so)

[Debian Bug Tracking System]

Your message dated Thu, 21 Jul 2016 06:50:14 +
with message-id 
and subject line Bug#831229: fixed in mariadb-10.0 10.0.26-2~exp3
has caused the Debian Bug report #831229,
regarding libmariadbclient-dev{, -compat}: fails to upgrade from 'sid' - trying 
to overwrite /usr/bin/mysql_config, /usr/lib/*/libmysqlclient.so
to be marked as done.

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

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


-- 
831229: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831229
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmariadbclient-dev-compat,libmariadbclient-dev
Version: 10.0.26-2~exp2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package libmariadbclient-dev.
  Preparing to unpack .../libmariadbclient-dev_10.0.26-2~exp2_amd64.deb ...
  Unpacking libmariadbclient-dev (10.0.26-2~exp2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libmariadbclient-dev_10.0.26-2~exp2_amd64.deb 
(--unpack):
   trying to overwrite '/usr/bin/mysql_config', which is also in package 
libmariadb-dev-compat 2.3.0-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Selecting previously unselected package libmariadbclient-dev-compat.
  Preparing to unpack .../libmariadbclient-dev-compat_10.0.26-2~exp2_amd64.deb 
...
  Unpacking libmariadbclient-dev-compat (10.0.26-2~exp2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libmariadbclient-dev-compat_10.0.26-2~exp2_amd64.deb 
(--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libmysqlclient.so', which is 
also in package libmariadb-dev-compat 2.3.0-1
  Processing triggers for libc-bin (2.23-1) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/libmariadbclient-dev_10.0.26-2~exp2_amd64.deb
   /var/cache/apt/archives/libmariadbclient-dev-compat_10.0.26-2~exp2_amd64.deb


cheers,

Andreas


libmariadb-dev-compat=2.3.0-1_libmariadbclient-dev-compat=10.0.26-2~exp2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: mariadb-10.0
Source-Version: 10.0.26-2~exp3

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

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

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

Debian distribution maintenance software
pp.
Otto Kekäläinen  (supplier of updated mariadb-10.0 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 20 Jul 2016 23:01:17 +0300
Source: mariadb-10.0
Binary: libmariadbd18 libmariadbclient18 libmariadbd-dev libmariadbclient-dev 
libmariadbclient-dev-compat mariadb-common mariadb-client-core-10.0 
mariadb-client-10.0 mariadb-server-core-10.0 mariadb-test mariadb-test-data 
mariadb-server-10.0 mariadb-server mariadb-client mariadb-plugin-connect 
mariadb-plugin-oqgraph mariadb-plugin-tokudb mariadb-plugin-mroonga 
mariadb-plugin-spider
Architecture: source amd64 all
Version: 10.0.26-2~exp3
Distribution: experimental
Urgency: low
Maintainer: Debian MySQL Maintainers 
Changed-By: Otto Kekäläinen 
Description:
 libmariadbclient-dev - MariaDB database development files
 libmariadbclient-dev-compat - MariaDB database development files 
(libmysqlclient compatibility)
 libmariadbclient18 - MariaDB database client library
 libmariadbd-dev - MariaDB embedded database, development files
 libmariadbd18 - MariaDB embedded database
 mariadb-client - MariaDB database client (metapackage depending on the latest 
vers
 mariadb-client-10.0 - MariaDB database client binaries
 mariadb-client-core-10.0 - MariaDB database core client binaries
 mariadb-common - MariaDB common metapackage
 mariadb-plugin-connect - Connect storage engine for MariaDB
 mariadb-plugin-mroonga - Mroonga storage engine for MariaD

Bug#831108: marked as done (trend: FTBFS with GCC 6: math.h:63:12: error: 'std::fpclassify' has not been declared)

[Debian Bug Tracking System]

Your message dated Thu, 21 Jul 2016 06:50:26 +
with message-id 
and subject line Bug#831108: fixed in trend 1.4-1
has caused the Debian Bug report #831108,
regarding trend: FTBFS with GCC 6: math.h:63:12: error: 'std::fpclassify' has 
not been declared
to be marked as done.

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

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


-- 
831108: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831108
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: trend
Version: 1.3-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64

Hi,

During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html

Relevant part (hopefully):
> g++ -Wdate-time -D_FORTIFY_SOURCE=2 -MD -g -O2 -fPIE -fstack-protector-strong 
> -Wformat -Werror=format-security -pthread -c -o trend.o trend.cc
> In file included from trend.cc:57:0:
> /usr/include/c++/6/math.h:63:12: error: 'std::fpclassify' has not been 
> declared
>  using std::fpclassify;
> ^~
> /usr/include/c++/6/math.h:64:12: error: 'std::isfinite' has not been declared
>  using std::isfinite;
> ^~~~
> /usr/include/c++/6/math.h:65:12: error: 'std::isinf' has not been declared
>  using std::isinf;
> ^
> /usr/include/c++/6/math.h:66:12: error: 'std::isnan' has not been declared
>  using std::isnan;
> ^
> /usr/include/c++/6/math.h:67:12: error: 'std::isnormal' has not been declared
>  using std::isnormal;
> ^~~~
> /usr/include/c++/6/math.h:68:12: error: 'std::signbit' has not been declared
>  using std::signbit;
> ^~~
> /usr/include/c++/6/math.h:69:12: error: 'std::isgreater' has not been declared
>  using std::isgreater;
> ^
> /usr/include/c++/6/math.h:70:12: error: 'std::isgreaterequal' has not been 
> declared
>  using std::isgreaterequal;
> ^~
> /usr/include/c++/6/math.h:71:12: error: 'std::isless' has not been declared
>  using std::isless;
> ^~
> /usr/include/c++/6/math.h:72:12: error: 'std::islessequal' has not been 
> declared
>  using std::islessequal;
> ^~~
> /usr/include/c++/6/math.h:73:12: error: 'std::islessgreater' has not been 
> declared
>  using std::islessgreater;
> ^
> /usr/include/c++/6/math.h:74:12: error: 'std::isunordered' has not been 
> declared
>  using std::isunordered;
> ^~~
> make[1]: *** [trend.o] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/07/13/trend_1.3-1_unstable_gcc6.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.
--- End Message ---
--- Begin Message ---
Source: trend
Source-Version: 1.4-1

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

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

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

Debian distribution maintenance software
pp.
Yuri D'Elia  (supplier of updated trend package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 17 Jul 2016 12:54:57 +0200
Source: trend
Binary: trend
Architecture: source amd64
Version: 1.4-1
Distribution: unstable
Urgency: low
Maintainer: Yuri D'Elia 
Changed-By: Yuri D'Elia 
Description:
 trend  - general-purpose, efficient trend graph
Closes: 831108
Changes:
 trend (1.4-1) unstable; urgency=low
 .
   * New upstream version.
   * Fixes FTBS with GCC 6.1 (Closes: #831108).
   * Standards-Version 3.9.8 (no changes needed).
   * Switch Vcs-Git to https.
Checksums-Sha1:
 35b9520ebfe