Bug#811920: closing 811920

[Leopold Palomo-Avellaneda]

close 811920 1.0.0+ds2-1 '# Fixed in the new version of the package'
thanks

Bug#749357: libmakefile-parser-perl: FTBFS - tests fail

[Salvatore Bonaccorso]

Hi,

On Sun, Jun 26, 2016 at 03:03:12PM +0200, intrigeri wrote:
> FTR: no reply from upstream since 2 years, despite some pings and
> preliminary patches sent by other pkg-perl team members.
> 
> Given the popcon (installed = 22, vote = 2) and no reverse dependency,
> this package satisfies our team criteria for removal from the archive.

Beeing one of the persons uploading that package, just want to confirm
that yes this makes sense. Better to remove it from the archive than
keeping a broken one around.

Regards,
Salvatore

Processed: closing 811920

[Debian Bug Tracking System]

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

> close 811920 1.0.0+ds2-1 '# Fixed in the new version of the package'
Bug #811920 [ompl] ompl: FTBFS with GCC 6: use of deleted function
There is no source info for the package 'ompl' at version '1.0.0+ds2-1 '# Fixed 
in the new version of the package'' with architecture ''
Unable to make a source version for version '1.0.0+ds2-1 '# Fixed in the new 
version of the package''
Marked as fixed in versions 1.0.0+ds2-1 '# Fixed in the new version of the 
package'.
Bug #811920 [ompl] ompl: FTBFS with GCC 6: use of deleted function
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: notfound 811920 in 1.1.0+ds1-1

[Debian Bug Tracking System]

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

> notfound 811920 1.1.0+ds1-1
Bug #811920 [ompl] ompl: FTBFS with GCC 6: use of deleted function
There is no source info for the package 'ompl' at version '1.1.0+ds1-1' with 
architecture ''
Unable to make a source version for version '1.1.0+ds1-1'
Ignoring request to alter found versions of bug #811920 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#811842: marked as done (mona: FTBFS with GCC 6: no match for)

[Debian Bug Tracking System]

Your message dated Thu, 30 Jun 2016 08:18:53 +0200
with message-id <20160630061853.gb4...@seneca.home.org>
and subject line Re: mona: FTBFS with GCC 6: no match for
has caused the Debian Bug report #811842,
regarding mona: 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.)


-- 
811842: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811842
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mona
Version: 1.4-15-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 ../BDD -Wdate-time -D_FORTIFY_SOURCE=2  -g 
> -O2 -fstack-protector-strong -Wformat -Werror=format-security -fgnu89-inline 
> -O3 -DNDEBUG -Wall -c -o mona-lib.o `test -f 'lib.cpp' || echo './'`lib.cpp
> cc1plus: warning: command line option '-fgnu89-inline' is valid for C/ObjC 
> but not for C++
> lib.cpp: In member function 'bool AutLib::fileExists(char*)':
> lib.cpp:286:12: error: no match for 'operator!=' (operand types are 
> 'std::ifstream {aka std::basic_ifstream}' and 'int')
>return s != 0;
>   ~~^~~~
> 
> lib.cpp:286:12: note: candidate: operator!=(int, int) 
> lib.cpp:286:12: note:   no known conversion for argument 1 from 
> 'std::ifstream {aka std::basic_ifstream}' to 'int'
> In file included from /usr/include/c++/6/bits/locale_facets.h:48:0,
>  from /usr/include/c++/6/bits/basic_ios.h:37,
>  from /usr/include/c++/6/ios:44,
>  from /usr/include/c++/6/istream:38,
>  from /usr/include/c++/6/fstream:38,
>  from lib.cpp:21:
> /usr/include/c++/6/bits/streambuf_iterator.h:210:5: note: candidate: 
> template bool std::operator!=(const 
> std::istreambuf_iterator<_CharT, _Traits>&, const 
> std::istreambuf_iterator<_CharT, _Traits>&)
>  operator!=(const istreambuf_iterator<_CharT, _Traits>& __a,
>  ^~~~
> 
> /usr/include/c++/6/bits/streambuf_iterator.h:210:5: note:   template argument 
> deduction/substitution failed:
> lib.cpp:286:15: note:   'std::ifstream {aka std::basic_ifstream}' is 
> not derived from 'const std::istreambuf_iterator<_CharT, _Traits>'
>return s != 0;
>^
> 
> In file included from /usr/include/c++/6/bits/ios_base.h:46:0,
>  from /usr/include/c++/6/ios:42,
>  from /usr/include/c++/6/istream:38,
>  from /usr/include/c++/6/fstream:38,
>  from lib.cpp:21:
> /usr/include/c++/6/system_error:323:3: note: candidate: bool 
> std::operator!=(const std::error_condition&, const std::error_condition&)
>operator!=(const error_condition& __lhs,
>^~~~
> 
> /usr/include/c++/6/system_error:323:3: note:   no known conversion for 
> argument 1 from 'std::ifstream {aka std::basic_ifstream}' to 'const 
> std::error_condition&'
> /usr/include/c++/6/system_error:319:3: note: candidate: bool 
> std::operator!=(const std::error_condition&, const std::error_code&)
>operator!=(const error_condition& __lhs, const error_code& __rhs) noexcept
>^~~~
> 
> /usr/include/c++/6/system_error:319:3: note:   no known conversion for 
> argument 1 from 'std::ifstream {aka std::basic_ifstream}' to 'const 
> std::error_condition&'
> /usr/include/c++/6/system_error:315:3: note: candidate: bool 
> std::operator!=(const std::error_code&, const std::error_condition&)
>operator!=(const error_code& __lhs, const error_condition& __rhs) noexcept
>^~~~
> 
> /usr/include/c++/6/system_error:315:3: note:   no known conversion for 
> argument 1 from 'std::ifstream {aka std::basic_ifstream}' to 'const 
> std::error_code&'
> /usr/include/c++/6/system_error:311:3: note: candidate: bool 
> std::operator!=(const std::error_code&, const std::error_code&)
>operator!=(const error_code& __lhs, const error_code& __rhs) noexcept
>^~~~
> 
> /usr/include/c++/6/system_error:311:3: note:   no known conversion for 
> argument 1 from 'std::ifstream {aka std::basic_ifstream}' to 'const 
> std::error_code&'
> In file included from /usr/include/c++/6/st

Bug#811819: marked as done (xosview: FTBFS with GCC 6: no match for)

[Debian Bug Tracking System]

Your message dated Thu, 30 Jun 2016 06:20:30 +
with message-id 
and subject line Bug#811819: fixed in xosview 1.17-3
has caused the Debian Bug report #811819,
regarding xosview: 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.)


-- 
811819: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811819
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xosview
Version: 1.17-2
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++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
> -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -O3 -I. -MMD -Ilinux/  -c -o 
> linux/acpitemp.o linux/acpitemp.cc
> linux/acpitemp.cc: In member function 'void ACPITemp::getacpitemp()':
> linux/acpitemp.cc:121:41: error: no match for 'operator<<' (operand types are 
> 'std::basic_ostream' and 'std::ifstream {aka 
> std::basic_ifstream}')
>  std::cerr << "Can not open file : " << temp_file << std::endl;
>  ^~~~
> 
> In file included from /usr/include/c++/6/iostream:39:0,
>  from ./Xrm.h:12,
>  from ./xwin.h:4,
>  from ./xosview.h:10,
>  from ./meter.h:10,
>  from ./fieldmeter.h:10,
>  from linux/acpitemp.h:15,
>  from linux/acpitemp.cc:12:
> /usr/include/c++/6/ostream:628:5: note: candidate: std::basic_ostream<_CharT, 
> _Traits>& std::operator<<(std::basic_ostream<_CharT, _Traits>&&, const _Tp&) 
> [with _CharT = char; _Traits = std::char_traits; _Tp = 
> std::basic_ifstream] 
>  operator<<(basic_ostream<_CharT, _Traits>&& __os, const _Tp& __x)
>  ^~~~
> 
> /usr/include/c++/6/ostream:628:5: note:   conversion of argument 1 would be 
> ill-formed:
> linux/acpitemp.cc:121:15: error: cannot bind 'std::basic_ostream' 
> lvalue to 'std::basic_ostream&&'
>  std::cerr << "Can not open file : " << temp_file << std::endl;
>  ~~^
--- End Message ---
--- Begin Message ---
Source: xosview
Source-Version: 1.17-3

We believe that the bug you reported is fixed in the latest version of
xosview, 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.
Kartik Mistry  (supplier of updated xosview 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: Thu, 30 Jun 2016 11:11:56 +0530
Source: xosview
Binary: xosview
Architecture: source amd64
Version: 1.17-3
Distribution: unstable
Urgency: low
Maintainer: Kartik Mistry 
Changed-By: Kartik Mistry 
Description:
 xosview- X based system monitor
Closes: 811819
Changes:
 xosview (1.17-3) unstable; urgency=low
 .
   * debian/patches/gcc6_compilation:
 + Fix FTBFS with GCC 6 (Closes: #811819)
   * debian/control:
 + Updated to Standards-Version 3.9.8
 + Fixed Vcs-* URLs.
Checksums-Sha1:
 d624038197ae606321fceff61c4007b86b8736a6 1904 xosview_1.17-3.dsc
 3b5803e8396091bf869aa0ead8935c47e4dced69 14408 xosview_1.17-3.debian.tar.xz
 b55f12bf694ff713e5ac6aa862452ba7bc61d980 623018 xosview-dbgsym_1.17-3_amd64.deb
 7df839fe217649ff5ef9ddbcba698c99c3b3120b 127940 xosview_1.17-3_amd64.deb
Checksums-Sha256:
 a020ac776bbd2db07cede79983c3b3d61df412d0df2b6a53e93eff5a43abcb74 1904 
xosview_1.17-3.dsc
 1a505730c7b39c1eb13faa37e7882c4695de05446f209c325eb54e2f2f54e48c 14408 
xosview_1.17-3.debian.tar.xz
 74d4ff8ac62983fd13ae047e8390efaaaf70e7fe3ca1101668388f13c1b456bb 623018 
xosview-dbgsym_1.17-3_amd64.deb
 fb7074339941db5a7980d6ab076491745b89ca5da9b806fb60d4c1a30aaccaae 127940 
xo

Processed: tagging 811885

[Debian Bug Tracking System]

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

> tags 811885 + help
Bug #811885 [brainparty] brainparty: FTBFS with GCC 6: template argument X is 
invalid
Added tag(s) help.
> thanks
Stopping processing here.

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

Processed: fixed

[Debian Bug Tracking System]

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

> fixed 811865 4.9.5-1
Bug #811865 [postbooks] postbooks: FTBFS with GCC 6: no matching function for 
call to
Marked as fixed in versions postbooks/4.9.5-1.
>
End of message, stopping processing here.

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

Processed: tagging 812013

[Debian Bug Tracking System]

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

> tags 812013 + help
Bug #812013 [goffice-0.8] goffice-0.8: FTBFS with GCC 6: format not a string 
literal
Added tag(s) help.
> thanks
Stopping processing here.

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

Bug#829052: libneo4j-client8-dev: fails to upgrade from 'testing' - trying to overwrite /usr/include/neo4j-client.h

[Chris Leishman]

Ah! Thanks Andreas.

I'll resolve that immediately.

On 29 June 2016 at 20:10, Andreas Beckmann  wrote:

> Package: libneo4j-client8-dev
> Version: 1.0.0-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 libneo4j-client8-dev.
>   Preparing to unpack .../libneo4j-client8-dev_1.0.0-1_amd64.deb ...
>   Unpacking libneo4j-client8-dev (1.0.0-1) ...
>   dpkg: error processing archive
> /var/cache/apt/archives/libneo4j-client8-dev_1.0.0-1_amd64.deb (--unpack):
>trying to overwrite '/usr/include/neo4j-client.h', which is also in
> package libneo4j-client7-dev 0.9.2-1
>   dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
>   Processing triggers for libc-bin (2.22-11) ...
>   Errors were encountered while processing:
>/var/cache/apt/archives/libneo4j-client8-dev_1.0.0-1_amd64.deb
>
>
> cheers,
>
> Andreas
>

Processed: found 828712 in 15.04-4, found 828712 in 15.09-1, severity of 828923 is serious

[Debian Bug Tracking System]

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

> found 828712 15.04-4
Bug #828712 [alljoyn-services-1504,alljoyn-services-1509] alljoyn-services-1509 
and alljoyn-services-1504: error when trying to install together
There is no source info for the package 'alljoyn-services-1509' at version 
'15.04-4' with architecture ''
Marked as found in versions alljoyn-services-1504/15.04-4.
> found 828712 15.09-1
Bug #828712 [alljoyn-services-1504,alljoyn-services-1509] alljoyn-services-1509 
and alljoyn-services-1504: error when trying to install together
There is no source info for the package 'alljoyn-services-1504' at version 
'15.09-1' with architecture ''
Marked as found in versions alljoyn-services-1509/15.09-1.
> severity 828923 serious
Bug #828923 [src:kde-l10n] kde-l10n: current version incompatible with old 
kdenlive-data
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: Re: Bug#829027: libstroke: missing/obsolete coypright information

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #829027 [src:libstroke] libstroke: missing/obsolete coypright information
Severity set to 'normal' from 'serious'

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

Bug#829052: libneo4j-client8-dev: fails to upgrade from 'testing' - trying to overwrite /usr/include/neo4j-client.h

[Andreas Beckmann]

Package: libneo4j-client8-dev
Version: 1.0.0-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 libneo4j-client8-dev.
  Preparing to unpack .../libneo4j-client8-dev_1.0.0-1_amd64.deb ...
  Unpacking libneo4j-client8-dev (1.0.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libneo4j-client8-dev_1.0.0-1_amd64.deb (--unpack):
   trying to overwrite '/usr/include/neo4j-client.h', which is also in package 
libneo4j-client7-dev 0.9.2-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Processing triggers for libc-bin (2.22-11) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/libneo4j-client8-dev_1.0.0-1_amd64.deb


cheers,

Andreas


libneo4j-client7-dev=0.9.2-1_libneo4j-client8-dev=1.0.0-1.log.gz
Description: application/gzip

Bug#829051: knot-resolver-module-tinyweb: fails to upgrade from 'testing' - trying to overwrite /usr/lib/knot-resolver/tinyweb/datamaps.world.min.js

[Andreas Beckmann]

Package: knot-resolver-module-tinyweb
Version: 1.0.0-13-g95b243f-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...):

  Preparing to unpack 
.../knot-resolver-module-tinyweb_1.0.0-13-g95b243f-1_amd64.deb ...
  Unpacking knot-resolver-module-tinyweb (1.0.0-13-g95b243f-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/knot-resolver-module-tinyweb_1.0.0-13-g95b243f-1_amd64.deb
 (--unpack):
   trying to overwrite '/usr/lib/knot-resolver/tinyweb/datamaps.world.min.js', 
which is also in package knot-resolver 1.0.0-1
  Errors were encountered while processing:
   
/var/cache/apt/archives/knot-resolver-module-tinyweb_1.0.0-13-g95b243f-1_amd64.deb


cheers,

Andreas


knot-resolver=1.0.0-1_knot-resolver-module-tinyweb=1.0.0-13-g95b243f-1.log.gz
Description: application/gzip

Bug#829050: libgdbm-compat-dev: fails to upgrade from 'sid' - trying to overwrite /usr/include/dbm.h

[Andreas Beckmann]

Package: libgdbm-compat-dev
Version: 1.12-2
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 libgdbm-compat-dev.
  Preparing to unpack .../libgdbm-compat-dev_1.12-2_amd64.deb ...
  Unpacking libgdbm-compat-dev (1.12-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libgdbm-compat-dev_1.12-2_amd64.deb (--unpack):
   trying to overwrite '/usr/include/dbm.h', which is also in package 
libgdbm-dev:amd64 1.8.3-14
  Processing triggers for libc-bin (2.22-12) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/libgdbm-compat-dev_1.12-2_amd64.deb


cheers,

Andreas


libgdbm-dev=1.8.3-14_libgdbm-compat-dev=1.12-2.log.gz
Description: application/gzip

Bug#826579: onboard: Failed to start without gir1.2-atspi-2.0

[Jeremy Bicha]

Control: severity -1 normal
Control: forwarded -1 https://launchpad.net/bugs/1584352
Control: tags -1 + pending fixed-upstream

This has been fixed upstream by making atspi and appindicator optional again.

Thanks,
Jeremy Bicha

Bug#817532: marked as done (libgetopt-mixed-perl: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Thu, 30 Jun 2016 01:48:46 +
with message-id 
and subject line Bug#817532: fixed in libgetopt-mixed-perl 1.008-10.2
has caused the Debian Bug report #817532,
regarding libgetopt-mixed-perl: 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.)


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

Hi,

The package libgetopt-mixed-perl 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: libgetopt-mixed-perl
Source-Version: 1.008-10.2

We believe that the bug you reported is fixed in the latest version of
libgetopt-mixed-perl, 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.
Axel Beckert  (supplier of updated libgetopt-mixed-perl 
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: Mon, 20 Jun 2016 03:05:56 +0200
Source: libgetopt-mixed-perl
Binary: libgetopt-mixed-perl
Architecture: source all
Version: 1.008-10.2
Distribution: unstable
Urgency: medium
Maintainer: Ezra Pagel 
Changed-By: Axel Beckert 
Description:
 libgetopt-mixed-perl - Perl module for processing options in GNU-style (= long 
and short
Closes: 817532
Changes:
 libgetopt-mixed-perl (1.008-10.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Bump debhelper compatibility to 9 (Closes: #817532)
 + Replace dh_clean -k with dh_prep
 + Depend on ${misc:Depends}
   * Other trivial changes which make the package more future-proof:
 + Replace $(PWD) with $(CURDIR) in debian/rules
 + Move debhelper from Build-Depends-Indep to Build-Depends. Whatever
   is needed to run the clean target needs to be satisfied by
   Build-Depends and not only Build-Depends-Indep.
 + Drop redundant Section and Priority fields from binary package stanza.
Checksums-Sha1:
 2e2afe031aea74230d797cb5e2c6bb8638260c80 1754 
libgetopt-mixed-perl_1.008-10.2.dsc
 5c7aec1a7490f938bc8baa8ad87dc64aefb6bb0d 2719 
libgetopt-mixed-perl_1.008-10.2.diff.gz
 b86e5696c3497f89a9dc3401e2838503e216d9e2 17602 
libgetopt-mixed-perl_1.008-10.2_all.deb
Checksums-Sha256:
 d19a03af3cd48e722eac5d2a060447462966ae5114f6327d54c220047fd3be27 1754 
libgetopt-mixed-perl_1.008-10.2.dsc
 bc60d5bbc36888a2bc613831dad0252a2598615e530dd530b2240d28d75f2d2e 2719 
libgetopt-mixed-perl_1.008-10.2.diff.gz
 f25f4e43d401430b56d7b326a8968826cf0ade6c057b5a6f0dbfcc835285c3da 17602 
libgetopt-mixed-perl_1.008-10.2_all.deb
Files:
 9cff166b8fe36bad472205a6d2bc89eb 1754 perl optional 
libgetopt-mixed-perl_1.008-10.2.dsc
 246dad26c7a4be99dab7cedf2f080539 2719 perl optional 
libgetopt-mixed-perl_1.008-10.2.diff.gz
 6af85a588fcdf8929c2d6e12066d183a 17602 perl optional 
libgetopt-mixed-perl_1.008-10.2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXZ0UzAAoJEC/5zVlhJha1gtIP/07v8Iniv1FKc4kBx77fVvBE
VkTeJeeOosUbiwt+XsFLjP/yH8QQv1XEaOW3IJZPGhJnmOE5GB/OectdntdWOwPt
m1EVwWMVeBrczpUDDr0BEmgO/7lvrISPAbRB3c7CgX97exlnHAlJEVoaam2MDwTU
mH+tGoHsF3yBQzOXoLwasCLaHNHNYvl0Y+4qNSd7ppysYN6SrJA3mgIAfCS7uYay
B2DMt27L9OPqK2yy3oW8lV8+IUe7JfD4w0eeBSNBdIq9Uj8t5CLjPh1vZ/NUEb/0
saTjszVlhLXUpxlF/I/PZTnsWJB9NqMqBksyjMPOzdL2ElZM3RAOsNQ9N4ZG0VvE
qOk7eJ+XEf5cVQbjieR4Oj85rOUf8ho0tIKtQljY4wCiqlOvKF//07wXWtkuK0AE
R46U5uSNKppRcJuqszKCuxSiaNdRKssCRS++1BnanBq8zKT4MHhR4dJva7nrPbt9
IBRhZAhmeHDlMtRt25Jzp3TUsFN9iVZQh+hKNHGGvM/t3noFv/3WoAxGJRDnKLM+
glqaylduCe5N6LMZKiQvWT7/5E0aW0E594tB7i+EWCYC79W+TX4OGqV5SCpg57zH
ZR33THa4t4

Processed: Re: Bug#826579: onboard: Failed to start without gir1.2-atspi-2.0

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #826579 [onboard] onboard: Failed to start without gir1.2-atspi-2.0
Severity set to 'normal' from 'grave'
> forwarded -1 https://launchpad.net/bugs/1584352
Bug #826579 [onboard] onboard: Failed to start without gir1.2-atspi-2.0
Set Bug forwarded-to-address to 'https://launchpad.net/bugs/1584352'.
> tags -1 + pending fixed-upstream
Bug #826579 [onboard] onboard: Failed to start without gir1.2-atspi-2.0
Added tag(s) fixed-upstream and pending.

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

Bug#829042: gr-radar: FTBFS when not building gr-radar-doc

[Aaron M. Ucko]

Source: gr-radar
Version: 0.0.0.20160126-1
Severity: serious
Justification: fails to build from source

Hi, Maitland.

Builds of gr-radar covering only its architecture-dependent binary
packages (as on the autobuilders, or with dpkg-buildpackage -B) have
been failing:

  ln -s /usr/share/javascript/jquery/jquery.js 
debian/gr-radar-doc/usr/share/doc/gr-radar-doc/html/jquery.js
  ln: failed to create symbolic link 
'debian/gr-radar-doc/usr/share/doc/gr-radar-doc/html/jquery.js': No such file 
or directory
  debian/rules:18: recipe for target 'override_dh_install' failed
  make[1]: *** [override_dh_install] Error 1
  make[1]: Leaving directory '/«PKGBUILDDIR»'
  debian/rules:6: recipe for target 'binary-arch' failed
  make: *** [binary-arch] Error 2

Please arrange to run this command only when actually building
gr-radar-doc.  One possible approach might be to split
override_dh_install into override_dh_install-arch and
override_dh_install-indep.

Thanks!

Bug#808472: gnu-efi copyright file is wrong, includes GPL-licensed code on arm

[Ben Hutchings]

On Sun, 20 Dec 2015 14:17:08 +0100 Julian Andres Klode  wrote:
> Package: gnu-efi
> Severity: serious
> 
> [This is a reminder for me]
> 
> The copyright file only lists BSD-3-clause and BSD-4-clause
> licenses currently.
> 
> Some parts are BSD-2-clause, though.
> 
> More importantly, and the reason for the serious severity:
> 
> Parts of arm and aarch64 code are GPL-2-licensed, though,
> causing bootloaders built using them to be GPL-2.

So does this just need to be documented, or is it a problem that the
boot loaders have GPLv2 code in them?

At a quick glance, it seems there might be a licence incompatibility
with refind (some files GPLv3+).  If so, that should be 'fixed' by
limiting the architectures refind is built for, though obviously it
would be better to get this code in gnu-efi relicenced.

Ben.
 
-- 

Ben Hutchings
To err is human; to really foul things up requires a computer.


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

Processed: affects 808472

[Debian Bug Tracking System]

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

> affects 808472 src:refind
Bug #808472 [gnu-efi] gnu-efi copyright file is wrong, includes GPL-licensed 
code on arm
Added indication that 808472 affects src:refind
> thanks
Stopping processing here.

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

Processed: tagging 828112, tagging 828110, tagging 828119, tagging 827832, tagging 827834, tagging 818197 ...

[Debian Bug Tracking System]

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

> tags 828112 + sid stretch
Bug #828112 {Done: Dirk Eddelbuettel } [src:fregression] 
fregression: FTBFS: dh_clean: Please specify the compatibility level in 
debian/compat
Added tag(s) sid and stretch.
> tags 828110 + sid stretch
Bug #828110 {Done: Dirk Eddelbuettel } [src:fextremes] 
fextremes: FTBFS: dh_clean: Please specify the compatibility level in 
debian/compat
Added tag(s) sid and stretch.
> tags 828119 + sid stretch
Bug #828119 [src:twill] twill: FTBFS: debian/twill-fork.1: No such file or 
directory at /usr/bin/dh_installman line 131.
Added tag(s) stretch and sid.
> tags 827832 + sid stretch
Bug #827832 [src:python-pytc] python-pytc: FTBFS: /bin/sh: 3: 
pythonpython2.7-dbg: not found
Added tag(s) sid and stretch.
> tags 827834 + sid stretch
Bug #827834 [src:ruby-state-machine] ruby-state-machine: FTBFS: 
machine_test.rb:3264:in `': uninitialized constant 
MachineDrawingTest::Constants (NameError)
Added tag(s) stretch and sid.
> tags 818197 + sid stretch
Bug #818197 {Done: Mattia Rizzolo } [src:g2clib] g2clib: 
Jasper removal
Added tag(s) stretch and sid.
> found 828902 0.2-9
Bug #828902 [src:utidylib] utidylib: please update for new tidy-html5
Marked as found in versions utidylib/0.2-9.
> tags 828902 + sid stretch
Bug #828902 [src:utidylib] utidylib: please update for new tidy-html5
Added tag(s) stretch and sid.
> tags 828895 + sid stretch
Bug #828895 [src:jless] jless: FTBFS: dh_clean: Please specify the 
compatibility level in debian/compat
Added tag(s) sid and stretch.
> tags 828781 + sid stretch
Bug #828781 [src:jodreports] jodreports: FTBFS: error: package 
freemarker.template does not exist
Added tag(s) sid and stretch.
> tags 828893 + sid stretch
Bug #828893 [src:epic4-help] epic4-help: FTBFS: dh_clean: Please specify the 
compatibility level in debian/compat
Added tag(s) sid and stretch.
> tags 828879 + sid stretch
Bug #828879 [src:dataquay] dataquay: FTBFS: terminate called after throwing an 
instance of 'Dataquay::RDFTransactionError'
Added tag(s) sid and stretch.
> tags 828894 + sid stretch
Bug #828894 [src:gdb-avr] gdb-avr: FTBFS: dh_movefiles: 
debian/tmp/usr/share/man/ not found (supposed to put it in gdb-avr)
Added tag(s) sid and stretch.
> # not a regression
> severity 828095 important
Bug #828095 [petitboot] petitboot: needs autoreconf to build on ppc64el
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
818197: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818197
827832: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827832
827834: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827834
828095: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828095
828110: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828110
828112: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828112
828119: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828119
828781: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828781
828879: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828879
828893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828893
828894: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828894
828895: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828895
828902: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828902
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#792126: mbr:i386 self-tests depend on VM86

[Ben Hutchings]

I got part way to fixing this using libx86emu (not libx86, that's not
flexible enough).

I ended up having to mess with the autotooling quite a bit, and I think
I need to add back a feature test because libx86emu is not available on
all architectures.  But I got the tests running and passing on amd64.

I'm attaching a patch with all my changes.  Not tagging this +patch
because it's not finished.

Ben.
 
-- 

Ben Hutchings
To err is human; to really foul things up requires a computer.
diff -u mbr-1.1.11/Makefile.am mbr-1.1.11/Makefile.am
--- mbr-1.1.11/Makefile.am
+++ mbr-1.1.11/Makefile.am
@@ -4,17 +4,12 @@
 AUTOCONF=autoconf2.50
 AUTOHEADER=autoheader2.50
 
-if HAVE_VM86
 SUBDIRS = harness
-else
-SUBDIRS =
-endif
 
 sbin_PROGRAMS = install-mbr
 install_mbr_SOURCES = install-mbr.c mbr.S86 mbr.h
 install_mbr_LDADD = mbr.o y2k.o
 noinst_DATA = testdisk.b
-noinst_SCRIPTS = wraptest
 
 AS86 = as86
 LD86 = ld86
@@ -23,9 +18,12 @@
 
 man_MANS = install-mbr.8
 
-TESTS = tests/inst-1 tests/inst-3 \
-tests/inst-4 tests/inst-6 tests/inst-7 tests/inst-8
-TESTS_ENVIRONMENT = sh wraptest
+TESTS = tests/inst-1 tests/inst-2 tests/inst-3 \
+tests/inst-4 tests/inst-6 tests/inst-7 tests/inst-8 \
+tests/mbr-1 tests/mbr-2 tests/mbr-3 tests/mbr-4 \
+tests/mbr-5 tests/mbr-6 \
+tests/testdisk-1 tests/testdisk-2 tests/testdisk-3 \
+tests/testdisk-4 tests/testdisk-5 tests/testdisk-6
 
 check_DATA = \
   table.b \
@@ -33,8 +31,8 @@
 
 EXTRA_DIST = table.S86 historic,v ${TESTS} ${man_MANS}
 
-CLEANFILES = *.b *.s86 *.o86 *.lst *.sym test.* test-* \
-  mbr-?.?.?.S86
+CLEANFILES = *.b *.s86 *.o86 *.lst *.sym test.* test-img test-mbr test-mbr-l \
+  test-mbr-u test-new test-old test-x test-y mbr-?.?.?.S86
 
 SUFFIXES = .b .S86 .s86
 
diff -u mbr-1.1.11/harness/Makefile.am mbr-1.1.11/harness/Makefile.am
--- mbr-1.1.11/harness/Makefile.am
+++ mbr-1.1.11/harness/Makefile.am
@@ -1,7 +1,6 @@
 noinst_PROGRAMS = harness
 harness_SOURCES = \
   harness.h \
-  vm86.h \
   args.c \
   bios.c \
   event.c \
@@ -13,3 +12,5 @@
-  vm86.c
+  x86emu.c
+harness_LDADD = -lx86emu
+
+AM_CFLAGS = -Wall -Wstrict-prototypes -Wmissing-prototypes -g
 
-AM_CFLAGS = -Wall -Wstrict-prototypes -Wmissing-prototypes -g -m32
diff -u mbr-1.1.11/debian/changelog mbr-1.1.11/debian/changelog
--- mbr-1.1.11/debian/changelog
+++ mbr-1.1.11/debian/changelog
@@ -1,3 +1,16 @@
+mbr (1.1.11-5.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload
+  * Use libx86emu instead of vm86 to run tests. Closes: #792126.
+  * Enable running all tests on all architectures, except inst-5 and version
+  * Run autoreconf
+  * As automake now uses the test-driver script, wraptest no longer works.
+Replace it with a shell library (tests/setup), sourced by each test.
+  * Remove specific temporary files, not test-*, so that we preserve the
+test-driver script
+
+ -- Ben Hutchings   Wed, 29 Jun 2016 22:36:54 +0200
+
 mbr (1.1.11-5) unstable; urgency=low
 
   * Add dh_md5sums to debian/rules, thanks to jmccrohan. Closes: #672321.
diff -u mbr-1.1.11/debian/control mbr-1.1.11/debian/control
--- mbr-1.1.11/debian/control
+++ mbr-1.1.11/debian/control
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Santiago Garcia Mantinan 
 Standards-Version: 3.9.3
-Build-Depends: debhelper(>= 7), bin86, util-linux (>= 2.13) | linux32
+Build-Depends: debhelper(>= 7), bin86, libx86emu-dev
 
 Package: mbr
 Architecture: any
diff -u mbr-1.1.11/debian/rules mbr-1.1.11/debian/rules
--- mbr-1.1.11/debian/rules
+++ mbr-1.1.11/debian/rules
@@ -1,7 +1,5 @@
 #!/usr/bin/make -f
 
-KERNEL_ARCH := $(shell linux64 uname -m)
-
 CC := gcc -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64
 
 CFLAGS := -g -Wall -W
@@ -20,24 +18,23 @@
 
 build-indep: build-stamp
 
-build-stamp:
+configure-stamp:
+	AUTOMAKE='automake --add-missing' autoreconf
 	./configure --exec-prefix=`pwd`/debian/mbr/ --prefix=`pwd`/debian/mbr/usr
+	touch $@
+
+build-stamp: configure-stamp
 	$(MAKE) CC="$(CC)" LD="$(LD)" CFLAGS="$(CFLAGS)"
-ifneq (,$(findstring x86_64,$(KERNEL_ARCH)))
-	# Limit the tests on x86_64 kernels
-else ifeq (i386,$(DEB_BUILD_ARCH))
 	$(MAKE) check
-else
-	# Limit the tests on non i386
-endif
-	touch build
+	touch $@
 
 clean:
 	dh_testdir
 	dh_testroot
 	dh_clean
 	[ ! -f Makefile ] || $(MAKE) distclean
-	rm -f build
+	rm -f aclocal.m4 build compile configure harness/Makefile.in \
+		Makefile.in test-driver
 
 install: build
 	dh_testdir
only in patch2:
unchanged:
--- mbr-1.1.11.orig/configure.in
+++ mbr-1.1.11/configure.in
@@ -7,10 +7,4 @@
 
 AC_PROG_CC
 
-dnl I'm not sure if the number of brackets needed for this is
-dnl well-defined...
-AM_CONDITIONAL(HAVE_VM86, [[uname -m | grep -q 'i[0-9]86']])
-
-AC_CONFIG_FILES([wraptest])
-
 AC_OUTPUT(Makefile harness/Makefile)
only in patch2:
unchanged:
--- mbr-1.1.11.orig/harness/x86emu.c
+++ mbr-1.1.11/harness/x86emu.c
@@ -0,0 +1,170 @@
+#include 
+#include 
+#include 
+#include 
+#include 
+#include 
+#include 
+#include "harness.h"
+
+static x86emu_t *x86emu;
+st

Bug#811705: FTBFS with GCC 6: throw will always call terminate

[Richard Kettlewell]

Either the current release (3.1) or
https://github.com/ewxrjk/rsbackup/commit/406aade24a2fabf5806a8b5452fba34e020b893a
address this.

ttfn/rjk

Bug#829038: owncloud-client: FTBFS in testing (LaTeX Error: File `iftex.sty' not found)

[Santiago Vila]

Package: src:owncloud-client
Version: 2.2.1+dfsg-1
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
Severity: serious

Dear maintainer:

This package currently fails to build in stretch:


[...]
make[6]: Entering directory 
'/<>/owncloud-client-2.2.1+dfsg/obj-x86_64-linux-gnu/doc/latex'
pdflatex  'ownCloudClientManual.tex'
This is pdfTeX, Version 3.14159265-2.6-1.40.17 (TeX Live 2016/Debian) 
(preloaded format=pdflatex)
 restricted \write18 enabled.
entering extended mode
(./ownCloudClientManual.tex
LaTeX2e <2016/03/31> patch level 1
Babel <3.9r> and hyphenation patterns for 3 language(s) loaded.
(./sphinxmanual.cls
Document Class: sphinxmanual 2009/06/02 Document class (Sphinx manual)
(/usr/share/texlive/texmf-dist/tex/latex/base/report.cls
Document Class: report 2014/09/29 v1.4h Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo)))

! LaTeX Error: File `iftex.sty' not found.


A full build log will be available here:

https://tests.reproducible-builds.org/debian/rbuild/testing/amd64/owncloud-client_2.2.1+dfsg-1.rbuild.log

Thanks.

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

[Debian Bug Tracking System]

Your message dated Wed, 29 Jun 2016 22:25:18 +
with message-id 
and subject line Bug#811646: fixed in libgtextutils 0.7-4
has caused the Debian Bug report #811646,
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.)


-- 
811646: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811646
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgtextutils
Version: 0.7-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
...
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -Wextra -Wformat-nonliteral -Wformat-security 
> -Wswitch-default -Wswitch-enum -Wunused-parameter -Wfloat-equal -Werror 
> -DDEBUG -g -O1 -DDEBUG -g -O1 -c text_line_reader.cpp  -fPIC -DPIC -o 
> .libs/text_line_reader.o
> text_line_reader.cpp: In member function 'bool TextLineReader::next_line()':
> text_line_reader.cpp:47:9: error: cannot convert 'std::istream {aka 
> std::basic_istream}' to 'bool' in return
>   return input_stream ;
>  ^~~~
> 
> Makefile:511: recipe for target 'text_line_reader.lo' failed
> make[4]: *** [text_line_reader.lo] Error 1

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: libgtextutils
Source-Version: 0.7-4

We believe that the bug you reported is fixed in the latest version of
libgtextutils, 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.
Gert Wollny  (supplier of updated libgtextutils 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, 29 Jun 2016 14:40:13 +
Source: libgtextutils
Binary: libgtextutils-dev libgtextutils0v5
Architecture: source amd64
Version: 0.7-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Gert Wollny 
Description:
 libgtextutils-dev - Gordon Text_utils library (development files)
 libgtextutils0v5 - Gordon Text_utils library
Closes: 811646
Changes:
 libgtextutils (0.7-4) unstable; urgency=medium
 .
   * Team upload.
   [ Gert Wollny ]
   * d/p/gcc-6.patch: Fix compilation with g++-6, Closes: #811646
   * d/ibgtextutils0v5.lintian-override: add override for differently
 names -dev symlink
   * cme fix dpkg-control
 .
   [ Andreas Tille ]
   * hardening=+bindnow
Checksums-Sha1:
 74235f6aacbd98ec037492b8dad0edc2c441d5d0 2109 libgtextutils_0.7-4.dsc
 8be95362b37215b6f35af5d66ead6ea6605506b9 14420 
libgtextutils_0.7-4.debian.tar.xz
 e86ead2331d5bb7977be3f3fc6595ded929a56c2 24170 
libgtextutils-dev_0.7-4_amd64.deb
 d4953a754dccc09efc9ffedc9cb4661b7e766f31 31572 
libgtextutils0v5-dbgsym_0.7-4_amd64.deb
 0e18988e8655d596633d46e6a271cc257f315c46 19044 libgtextutils0v5_0.7-4_amd64.deb
Checksums-Sha256:
 5657ccf2d88210d79cb6b56bbb80a4d38e4234d7711883c2494b5b5e5be22b15 2109 
libgtextutils_0.7-4.dsc
 fc43c09061316c913cb260f0f76113babf74e70d244d60a7b29824dce548d2d5 14420 
libgtextutils_0.7-4.debian.tar.xz
 b11afac144681cc6ea32f8683d6e7b465dc65cd1859ee4b207eac7f323e0a820 24170 
libgtextutils-dev_0.7-4_amd64.deb
 03b8dba893223978c9718d2b98ae78f2c47b7636ecbb54a38119429824391f80 31572 
libgtextutils0v5-dbgsym_0.7-4_amd64.deb
 66cb915e355b27b5a7d86a085adb8338eea71f23b25ebf65c929e502ab4f5c2a 19044 
libgtextutils0v5_0.7-4_amd64.deb
Files:
 9a6ccd97b72b5d3af4fbc770b078f6a0 2109 science optional libgtextutils_0.7-4.dsc
 e8e520f983067abb3f0bf83abd3bdf56 14420 science optional 
libgtextutils_0.7-4.debian.tar.xz
 f4d8330fbbb669315a6700b14b71 24170 libdevel optional 
libgtextutils-dev_0.7-4_amd64.deb
 30ac2a6db

Bug#828985: [pkg-go] Bug#828985: golang-github-gosimple-slug: FTBFS: FAIL: TestSubstituteLang (0.00s) slug_test.go:155: 1. Substitute("o a o", map[string]string{"o":"no", "a":"or"}) = "no nor no"; wan

[Michael Hudson-Doyle]

Seems like an upstream problem, I filed
https://github.com/gosimple/slug/issues/8

On 30 June 2016 at 02:28, Chris Lamb  wrote:
> Source: golang-github-gosimple-slug
> Version: 1.0-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,
>
> golang-github-gosimple-slug fails to build from source in unstable/amd64:
>
>   [..]
>
>
>   
> **
>   ** Starting build   
> **
>   
> **
>
>Package:  golang-github-gosimple-slug
>Version:  1.0-1
>Build architecture:   amd64
>Date: Wed, 29 Jun 2016 15:55:39 +0200
>Hostname: 8d018f376876
>Uname:Linux 8d018f376876 4.5.0-2-amd64 #1 SMP Debian 
> 4.5.4-1 (2016-05-16) x86_64 GNU/Linux
>/etc/timezone:Africa/Johannesburg
>
>   
> **
>   ** Installing build dependencies
> **
>   
> **
>
>   dh_testdir
>   dh_testroot
>   dh_prep
>   dh_testdir
>   dh_testroot
>   dh_install
>   dh_installdocs
>   dh_installchangelogs
>   dh_compress
>   dh_fixperms
>   dh_installdeb
>   dh_gencontrol
>   dh_md5sums
>   dh_builddeb
>   dpkg-deb: building package 'golang-github-gosimple-slug-build-deps' in 
> '../golang-github-gosimple-slug-build-deps_1.0-1_all.deb'.
>
>   The package has been created.
>   Attention, the package has been created in the current directory,
>   not in ".." as indicated by the message above!
>   Selecting previously unselected package 
> golang-github-gosimple-slug-build-deps.
>   (Reading database ... 23075 files and directories currently installed.)
>   Preparing to unpack golang-github-gosimple-slug-build-deps_1.0-1_all.deb ...
>   Unpacking golang-github-gosimple-slug-build-deps (1.0-1) ...
>   Reading package lists...
>   Building dependency tree...
>   Reading state information...
>   Correcting dependencies... Done
>   The following additional packages will be installed:
> dh-golang golang-1.6-go golang-1.6-src 
> golang-github-rainycape-unidecode-dev
> golang-go golang-src
>   Suggested packages:
> bzr ca-certificates mercurial subversion
>   Recommended packages:
> pkg-config
>   The following NEW packages will be installed:
> dh-golang golang-1.6-go golang-1.6-src 
> golang-github-rainycape-unidecode-dev
> golang-go golang-src
>   0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded.
>   1 not fully installed or removed.
>   Need to get 26.8 MB of archives.
>   After this operation, 192 MB of additional disk space will be used.
>   Get:1 http://httpredir.debian.org/debian sid/main amd64 dh-golang all 1.18 
> [9278 B]
>   Get:2 http://httpredir.debian.org/debian sid/main amd64 golang-1.6-src 
> amd64 1.6.2-2 [6784 kB]
>   Get:3 http://httpredir.debian.org/debian sid/main amd64 golang-1.6-go amd64 
> 1.6.2-2 [19.7 MB]
>   Get:4 http://httpredir.debian.org/debian sid/main amd64 golang-src amd64 
> 2:1.6.1+1 [2974 B]
>   Get:5 http://httpredir.debian.org/debian sid/main amd64 golang-go amd64 
> 2:1.6.1+1 [21.9 kB]
>   Get:6 http://httpredir.debian.org/debian sid/main amd64 
> golang-github-rainycape-unidecode-dev all 0.0~git20150906.0.c9cf8cd-1 [267 kB]
>   Fetched 26.8 MB in 0s (108 MB/s)
>   Selecting previously unselected package dh-golang.
>   (Reading database ...
> (Reading database ... 5%
> (Reading database ... 10%
> (Reading database ... 15%
> (Reading database ... 20%
> (Reading database ... 25%
> (Reading database ... 30%
> (Reading database ... 35%
> (Reading database ... 40%
> (Reading database ... 45%
> (Reading database ... 50%
> (Reading database ... 55%
> (Reading database ... 60%
> (Reading database ... 65%
> (Reading database ... 70%
> (Reading database ... 75%
> (Reading database ... 80%
> (Reading database ... 85%
> (Reading database ... 90%
> (Reading database ... 95%
> (Reading database ... 100%
> (Reading database ... 23079 files and directories currently installed.)
>   Preparing to unpack .../dh-golang_1.18_all.deb ...
>   Unpacking dh-golang (1.18) ...
>   Selecting previously unselected package golang-1.6-src.
>   Preparing to unpack .../golang-1.6-src_1.6.2-2_amd64.deb ...
>   Unpacking golang-1.6-src (1.6.2-2) ...
>   Selecting previously unselected package golang-1.6-go.
>   Preparing to unpack .../golang-1.6-go_1.6.2-2_amd64.deb ...
>   Unpacking golang-1.6-go (1.6.2-2) ...
>   Selecting previously unselected package golang-src.
>   Preparing to unpack .../golang-src_2%3a1.6.1+1_amd64.deb ...

Bug#828986: marked as done (liblrdf: FTBFS: devlibs error: There is no package matching [libraptor1-dev] and noone provides it, please report bug to d-shlibs maintainer)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jun 2016 22:07:32 +0100
with message-id 
<1467234452.2901565.652420769.4eed3...@webmail.messagingengine.com>
and subject line Re: Bug#828986: liblrdf: FTBFS: devlibs error: There is no 
package matching [libraptor1-dev] and noone provides it, please report bug to 
d-shlibs maintainer
has caused the Debian Bug report #828986,
regarding liblrdf: FTBFS: devlibs error: There is no package matching 
[libraptor1-dev] and noone provides it, please report bug to d-shlibs maintainer
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.)


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

liblrdf fails to build from source in unstable/amd64:

  [..]

  checking whether make sets $(MAKE)... (cached) yes
  checking build system type... x86_64-pc-linux-gnu
  checking host system type... x86_64-pc-linux-gnu
  checking how to print strings... printf
  checking for a sed that does not truncate output... /bin/sed
  checking for grep that handles long lines and -e... /bin/grep
  checking for egrep... /bin/grep -E
  checking for fgrep... /bin/grep -F
  checking for ld used by gcc... /usr/bin/ld
  checking if the linker (/usr/bin/ld) is GNU ld... yes
  checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
  checking the name lister (/usr/bin/nm -B) interface... BSD nm
  checking the maximum length of command line arguments... 1572864
  checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu 
format... func_convert_file_noop
  checking how to convert x86_64-pc-linux-gnu file names to toolchain format... 
func_convert_file_noop
  checking for /usr/bin/ld option to reload object files... -r
  checking for objdump... objdump
  checking how to recognize dependent libraries... pass_all
  checking for dlltool... no
  checking how to associate runtime and link libraries... printf %s\n
  checking for ar... ar
  checking for archiver @FILE support... @
  checking for strip... strip
  checking for ranlib... ranlib
  checking command to parse /usr/bin/nm -B output from gcc object... ok
  checking for sysroot... no
  checking for a working dd... /bin/dd
  checking how to truncate binary pipes... /bin/dd bs=4096 count=1
  checking for mt... no
  checking if : is a manifest tool... no
  checking for ANSI C header files... yes
  checking for sys/types.h... yes
  checking for sys/stat.h... yes
  checking for stdlib.h... yes
  checking for string.h... yes
  checking for memory.h... yes
  checking for strings.h... yes
  checking for inttypes.h... yes
  checking for stdint.h... yes
  checking for unistd.h... yes
  checking for dlfcn.h... yes
  checking for objdir... .libs
  checking if gcc supports -fno-rtti -fno-exceptions... no
  checking for gcc option to produce PIC... -fPIC -DPIC
  checking if gcc PIC flag -fPIC -DPIC works... yes
  checking if gcc static flag -static works... yes
  checking if gcc supports -c -o file.o... yes
  checking if gcc supports -c -o file.o... (cached) yes
  checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared 
libraries... yes
  checking whether -lc should be explicitly linked in... no
  checking dynamic linker characteristics... GNU/Linux ld.so
  checking how to hardcode library paths into programs... immediate
  checking whether stripping libraries is possible... yes
  checking if libtool supports shared libraries... yes
  checking whether to build shared libraries... yes
  checking whether to build static libraries... yes
  checking for ANSI C header files... (cached) yes
  checking errno.h usability... yes
  checking errno.h presence... yes
  checking for errno.h... yes
  checking limits.h usability... yes
  checking limits.h presence... yes
  checking for limits.h... yes
  checking for stdlib.h... (cached) yes
  checking for string.h... (cached) yes
  checking for unistd.h... (cached) yes
  checking for pkg-config... /usr/bin/pkg-config
  checking pkg-config is at least version 0.9.0... yes
  checking for RAPTOR... yes
  checking for an ANSI C-conforming const... yes
  checking for inline... inline
  checking for size_t... yes
  checking for vprintf... yes
  checking for _doprnt... no
  checking for getcwd... yes
  checking for strcasecmp... yes
  checking for strchr... yes
  checking for strdup... yes
  checking for s

Bug#829027: libstroke: missing/obsolete coypright information

[Vincent Lefevre]

Source: libstroke
Version: 0.5.1-7
Severity: serious
Justification: Policy 12.5

The Debian policy manual says:

"In addition, the copyright file must say where the upstream sources
(if any) were obtained, and should name the original authors."

but the libstroke copyright file just says:


This is the debian package of libstroke. The gEDA sources were downloaded
from http://www.etla.net/. The package was created by Hamish
Moffatt, March 1, 1999.

This software is released under the GNU General Public License,
version 2; please see /usr/share/common-licenses/GPL on your Debian
system. libgeda is released under the GNU Library General Public License
(LGPL), /usr/share/common-licenses/LGPL.


First, the URL is incorrect (http://www.etla.net/ is an almost empty
web page with no links, without any mention of libstroke). Moreover,
the original authors are not named.

Concerning the URL, it might be changed to:

  http://etla.net/libstroke/

but this page is obsolete (in particular, the contact link leads to
a 403 Forbidden error).

Now, this library is dead upstream (latest version in 2001, with an
autoconf incompatibility since 2002, affecting the build of other
software, still not fixed). Perhaps it would be better to remove it
from Debian, and make packages no longer depend on libstroke.

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

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

Bug#795081: Incompatible with subversion 1.9

[Ben Hutchings]

Control: tag -1 fixed-upstream

It appears that upstream has moved to
https://github.com/svn-all-fast-export/svn2git

I rebased the Debian package on the latest commit there (I didn't see a
newer release) and this bug seems to be fixed.

Ben.

-- 

Ben Hutchings
Make three consecutive correct guesses and you will be considered an
expert.


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

Processed: Re: Incompatible with subversion 1.9

[Debian Bug Tracking System]

Processing control commands:

> tag -1 fixed-upstream
Bug #795081 [svn-all-fast-export] Incompatible with subversion 1.9
Added tag(s) fixed-upstream.

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

Bug#829020: sqlalchemy: FTBFS in testing (too many values to unpack)

[Santiago Vila]

Package: src:sqlalchemy
Version: 1.0.13+ds1-1
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
Severity: serious

Dear maintainer:

This package currently fails to build in stretch:


[...]
Exception occurred:
  File "genindex_mako", line 86, in render_body
ValueError: too many values to unpack
The full traceback has been saved in /tmp/sphinx-err-42Quzo.log, if you want to 
report the issue to the developers.
Please also report this if it was a user error, so that a better error message 
can be provided next time.
A bug report can be filed in the tracker at 
. Thanks!
debian/rules:39: recipe for target 'build-docs' failed
make: *** [build-docs] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2


A full build log is available here:

https://tests.reproducible-builds.org/debian/rbuild/testing/amd64/sqlalchemy_1.0.13+ds1-1.rbuild.log

Thanks.

Processed: Re: FTBFS: buffio.h: No such file or directory

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #828899 [src:prayer] prayer: FTBFS: html_secure_tidy.c:15:20: fatal error: 
buffio.h: No such file or directory
Severity set to 'normal' from 'serious'

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

Processed: Re: FTBFS: buffio.h: No such file or directory

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #828937 [src:xqilla] xqilla: FTBFS: FunctionParseHTML.cpp:33:20: fatal 
error: buffio.h: No such file or directory
Severity set to 'normal' from 'serious'

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

Processed: Re: FTBFS: buffio.h: No such file or directory

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #828880 [src:elementtidy] elementtidy: FTBFS: elementtidy.c:41:20: fatal 
error: buffio.h: No such file or directory
Severity set to 'normal' from 'serious'

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

Bug#811641: marked as done (FTBFS with GCC 6: multiple errors)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jun 2016 19:50:42 +
with message-id 
and subject line Bug#811641: fixed in relion 1.4+dfsg-2
has caused the Debian Bug report #811641,
regarding FTBFS with GCC 6: multiple 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.)


-- 
811641: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811641
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: relion
Version: 1.4+dfsg-1
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
...
> g++ -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -c -o 
> src/apps/postprocess.o src/apps/postprocess.cpp
> g++ -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -c -o 
> src/apps/autopick.o src/apps/autopick.cpp
> src/Healpix_2.15a/cxxutils.cc: In function 'bool file_present(const string&)':
> src/Healpix_2.15a/cxxutils.cc:58:10: error: cannot convert 'std::ifstream 
> {aka std::basic_ifstream}' to 'bool' in return
>return dummy;
>   ^
> 
> src/Healpix_2.15a/cxxutils.cc: In function 'void parse_file(const string&, 
> std::map, std::__cxx11::basic_string 
> >&)':
> src/Healpix_2.15a/cxxutils.cc:264:63: error: no matching function for call to 
> 'planck_assert(std::ifstream&, std::__cxx11::basic_string)'
>planck_assert (inp,"Could not open parameter file "+filename);
>^

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: relion
Source-Version: 1.4+dfsg-2

We believe that the bug you reported is fixed in the latest version of
relion, 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.
Gert Wollny  (supplier of updated relion 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, 29 Jun 2016 13:32:34 +
Source: relion
Binary: relion-bin relion-bin+mpi relion-bin+gui relion-bin+mpi+gui 
librelion-dev-common librelion-dev librelion+mpi-dev librelion+gui-dev 
librelion+mpi+gui-dev librelion-1.4-1 librelion+mpi-1.4-1 librelion+gui-1.4-1 
librelion+mpi+gui-1.4-1
Architecture: source amd64 all
Version: 1.4+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Gert Wollny 
Description:
 librelion+gui-1.4-1 - RELION dynnamic library (3D reconstructions in 
cryo-electron micr
 librelion+gui-dev - C++ API for RELION (3D reconstructions in cryo-electron 
microscop
 librelion+mpi+gui-1.4-1 - RELION dynnamic library (3D reconstructions in 
cryo-electron micr
 librelion+mpi+gui-dev - C++ API for RELION (3D reconstructions in 
cryo-electron microscop
 librelion+mpi-1.4-1 - RELION dynnamic library (3D reconstructions in 
cryo-electron micr
 librelion+mpi-dev - C++ API for RELION (3D reconstructions in cryo-electron 
microscop
 librelion-1.4-1 - RELION dynnamic library (3D reconstructions in cryo-electron 
micr
 librelion-dev - C++ API for RELION (3D reconstructions in cryo-electron 
microscop
 librelion-dev-common - C++ API for RELION (3D reconstructions in cryo-electron 
microscop
 relion-bin - toolkit for 3D reconstructions in cryo-electron microscopy
 relion-bin+gui - parallel toolkit for 3D reconstructions in cryo-electron 
microsco
 relion-bin+mpi - parallel toolkit for 3D reconstructions in cryo-electron 
microsco
 relion-bin+mpi+gui - parallel toolkit for 3D reconstructions in cryo-electron 
microsco
Closes: 811641
Changes:
 relion (1.4+dfsg-2) unstable; urgency=medium
 .
   [ Gert Wollny ]
   * Team upload.
   * d/p/0

Bug#811141: marked as done (FTBFS: CMake Error: The following variables are used in this project)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jun 2016 19:49:38 +
with message-id 
and subject line Bug#811141: fixed in orthanc-postgresql 2.0-2
has caused the Debian Bug report #811141,
regarding FTBFS: CMake Error: The following variables are used in this project
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.)


-- 
811141: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811141
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: orthanc-postgresql
Version: 2.0-1
Severity: serious

orthanc-postgresql fails to build in unstable:

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
> -- Looking for C++ include orthanc/OrthancCppDatabasePlugin.h
> -- Looking for C++ include orthanc/OrthancCppDatabasePlugin.h - found
> Setting the version of the libraries to 2.0
> CMake Error: The following variables are used in this project, but they are 
> set to NOTFOUND.
> Please set them or make sure they are set and tested correctly in the CMake 
> files:
> PostgreSQL_TYPE_INCLUDE_DIR (ADVANCED)
>used as include directory in directory /<>
>used as include directory in directory /<>
...
> _Boost_NAMESPACE_LAST:INTERNAL=boost
> //Last used Boost_USE_MULTITHREADED value.
> _Boost_USE_MULTITHREADED_LAST:INTERNAL=TRUE
> 
> dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr 
> -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
> -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
> -DCMAKE_SKIP_RPATH:BOOL=ON -DSTATIC_BUILD:BOOL=OFF 
> -DUSE_GTEST_DEBIAN_SOURCE_PACKAGE:BOOL=ON -DCMAKE_BUILD_TYPE= returned exit 
> code 1
> debian/rules:19: recipe for target 'override_dh_auto_configure' failed
> make[1]: *** [override_dh_auto_configure] Error 2
> make[1]: Leaving directory '/<>'

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: orthanc-postgresql
Source-Version: 2.0-2

We believe that the bug you reported is fixed in the latest version of
orthanc-postgresql, 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.
Sebastien Jodogne  (supplier of updated orthanc-postgresql 
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, 29 Jun 2016 17:02:36 +0200
Source: orthanc-postgresql
Binary: orthanc-postgresql
Architecture: source amd64
Version: 2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Sebastien Jodogne 
Description:
 orthanc-postgresql - Plugins to use PostgreSQL as a database back-end to 
Orthanc
Closes: 811141
Changes:
 orthanc-postgresql (2.0-2) unstable; urgency=medium
 .
   * Fix to find PostgreSQL 9.5 dev headers. Closes: #811141
   * Add hardening flags
Checksums-Sha1:
 51a25370d9927256d528420d12a51b45ecc1c451  orthanc-postgresql_2.0-2.dsc
 be4fefc68c31859831e70153aef8ac88c527f9ee 6428 
orthanc-postgresql_2.0-2.debian.tar.xz
 5845628d84482b15122a9e86e8375ef937662f99 1004638 
orthanc-postgresql-dbgsym_2.0-2_amd64.deb
 0ee1cc5c925ccd31969786bfa2018b0bcc462a5e 71000 
orthanc-postgresql_2.0-2_amd64.deb
Checksums-Sha256:
 4df81b0881f4d8c8892d9332b030991974e0e4f3c28fbb0b80ec0d43f596  
orthanc-postgresql_2.0-2.dsc
 d3ce11d90a0fb20634a5e5bec9021789b493e11a8e4050839641f0f66d0166a1 6428 
orthanc-postgresql_2.0-2.debian.tar.xz
 f08479a0ca3874420ce4f436ee21f71a37f930a9d412fd7a8e851b39ac62debe 1004638 
orthanc-postgresql-dbgsym_2.0-2_amd64.deb
 a2c2753701fe1f3846f648ac7dc4e790bbabbc3d9a1560ec588255a2adf237ca 71000 
orthanc-postgresql_2.0-2_amd64.deb
Files:
 2bf55cfc545ec460d71e9e086aeecadb  science optional 
orthanc-postgresql_2.0-2.dsc
 07297df0b4c78c00baea9473d97b1841 6428 science optional 
orthanc-postgresql_2.0-2.debian.tar.xz
 093663e1ed98fdc613a66b16b97c90b2 1004638 debug extra 
orthanc-postgresql-dbgsym_2.0-2_amd64.deb
 49b1df96b7db47f5862a9285ce5cde06 71000 science optional 
orthanc-postgresql_2.0-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJXdCMPAAoJEFeKBJTRxkbR4xEQAJOmAyC/kuSsUEAm2cm9HOTH
QmB00yD6Yg8w8UnVzYMpll0qpjjHkslSpY1nZOwiMrDiTWpVyDtqUFqqwqmaOycL
9YHt3YhDIJ8GZ

Processed: block 809984 with 829018

[Debian Bug Tracking System]

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

> block 809984 with 829018
Bug #809984 [sudo] Documentation can't be rebuilt within Debian
809984 was not blocked by any bugs.
809984 was not blocking any bugs.
Added blocking bug(s) of 809984: 829018
> thanks
Stopping processing here.

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

Processed: Re: Bug#828767 closed by Alexandre Viau (Fixed in 2.0.0+dfsg1-2)

[Debian Bug Tracking System]

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

> notfixed 828767 2.0.0+dfsg1-2
Bug #828767 {Done: Alexandre Viau } [src:toxiproxy] 
toxiproxy: FTBFS: B-D favors old mux, logrus packages
Ignoring request to alter fixed versions of bug #828767 to the same values 
previously set
> found 828767 2.0.0+dfsg1-2
Bug #828767 {Done: Alexandre Viau } [src:toxiproxy] 
toxiproxy: FTBFS: B-D favors old mux, logrus packages
Did not alter found versions and reopened.
> thanks
Stopping processing here.

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

Bug#828767: closed by Alexandre Viau (Fixed in 2.0.0+dfsg1-2)

[Aaron M. Ucko]

notfixed 828767 2.0.0+dfsg1-2
found 828767 2.0.0+dfsg1-2
thanks

Debian Bug Tracking System  writes:

> I have fixed this issue in 2.0.0+dfsg1-2.

I understand you meant to, but AFAICT you accidentally left the fix out.

https://anonscm.debian.org/cgit/pkg-go/packages/toxiproxy.git/commit/?id=48c8abb3bb1cf2fedd0b61415d79633a00de1e44

shows a changelog entry with no corresponding change to debian/control,
and the autobuilders are still complaining about golang-mux-dev:

https://buildd.debian.org/status/fetch.php?pkg=toxiproxy&arch=i386&ver=2.0.0%2Bdfsg1-2&stamp=1467219777

The following packages have unmet dependencies:
 sbuild-build-depends-toxiproxy-dummy : Depends: golang-mux-dev but it is not 
installable
E: Unable to correct problems, you have held broken packages.
apt-get failed.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#724639: marked as done (Depends on old package linux-kernel-headers)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jun 2016 19:34:17 +
with message-id 
and subject line Bug#826519: fixed in kxl 1.1.7-16.1
has caused the Debian Bug report #826519,
regarding Depends on old package linux-kernel-headers
to be marked as done.

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

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


-- 
826519: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826519
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libkxl0-dev
Version: 1.1.7-16
Severity: important

libkxl0-dev depends on the package linux-kernel-headers, which used to
be a real package but is now virtual and provided by linux-libc-dev
(since before lenny).  You can simply remove this dependency, as it is
already a dependency of the C library development packages (libc6-dev
and libklibc-dev).

Ben.

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

Kernel: Linux 3.10-3-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
--- End Message ---
--- Begin Message ---
Source: kxl
Source-Version: 1.1.7-16.1

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated kxl 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, 29 Jun 2016 21:11:43 +0200
Source: kxl
Binary: libkxl0 libkxl0-dev
Architecture: source
Version: 1.1.7-16.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Ben Hutchings 
Description:
 libkxl0- multimedia library for game development
 libkxl0-dev - development files for libkxl0
Closes: 826519
Changes:
 kxl (1.1.7-16.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Change package format to 3.0 (quilt), so patches are automatically applied
 and the .pc and .svn directories are excluded from the source package
   * Remove linux-kernel-headers from Build-Depends (Closes: #826519)
Checksums-Sha1:
 a4e11308eb2e015a7f147ceaa29f878640c573ae 1988 kxl_1.1.7-16.1.dsc
 511917d4e9ae218ff67543b8bb91f4c7c4ecdb17 178576 kxl_1.1.7-16.1.debian.tar.xz
Checksums-Sha256:
 8203573ae39e6e53ebe31c55657750c0b836399fcf7fecb2ebc79e3b8aba9b39 1988 
kxl_1.1.7-16.1.dsc
 46373c2b227b633ad4344d5559d5918661eed7915a419cdeb09c5fa93f23f9b8 178576 
kxl_1.1.7-16.1.debian.tar.xz
Files:
 0d6e688ff0e799a9f346551c52f518e2 1988 devel optional kxl_1.1.7-16.1.dsc
 a941ab3143fbf3e6d6ce6d0f0dd123aa 178576 devel optional 
kxl_1.1.7-16.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIVAwUBV3Qgk+e/yOyVhhEJAQrx/RAAuWBRL6LsjXe5ZxBsylXTsrsyIuVehNtq
WoK/t1ODujRAfgeGFKteT7143O23uRi+ovYtbkGF6eEqe0hfHD0Xd6ZMiDoStGaR
18K41pD6MHuNAm9SIUWQV4EslRkG7+Td7DdcMEYsAcjbE2gHUfJSQOLONBD77lpy
jabAXRJTVpQcnrvGcioc+9rF1QWyuP+tw3teNcnsIHokRUIiGgtuSkMo1jAveiCG
78rMugelFIHkqdl6BmjibwgyYN1hIJSoBq844AXTv8NZSkgB9kQMNmxnEV9lhyro
/uIGTGOjaS1vkscIVJgYg/hOB1OxOei3EszMcpNzW7ciHegAAu0SX8w3CqrWm6ad
7rXY9yvFZxNgE+X4PnlEoElduQPrHMUkd59z4PaJohrQ/p8D5niKIn0N5sxdCFwL
CNL6r7tflIoih4+su4pwmEqi2d97KmzDX7SpfukF/gp3w4mXUPVqeprR0Yxhjllk
HGlsIPaO/fI4aZ0QKVIzGQwDmR92Z2Nib8FtnttIa005FVoI6emipKAmDPbdQJtT
uAteDHR8IN3OPnQT8BrlrsDVTs382ltV/Snc8tZeT6zytQIoQuf/Hu17AR74I9hT
WSMgFDFBpRV1KVlepdl/6E5fYNBAVANeNhvYK6c8zzyYkE8jH0//6bAHZCRBc2d3
xjwcbu7IKeo=
=Q3c4
-END PGP SIGNATURE End Message ---

Bug#826519: marked as done (Depends on obsolete package linux-kernel-headers)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jun 2016 19:34:17 +
with message-id 
and subject line Bug#826519: fixed in kxl 1.1.7-16.1
has caused the Debian Bug report #826519,
regarding Depends on obsolete package linux-kernel-headers
to be marked as done.

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

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


-- 
826519: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826519
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libkxl0-dev
Version: 1.1.7-16
Severity: serious

linux-kernel-headers was removed from unstable in 2007 (I think).  It
is now effectively a virtual package provided by linux-libc-dev, but
it's not a documented virtual package name and I would like to stop
providing it.  Please change the dependency to linux-libc-dev.

Ben.

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

Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: kxl
Source-Version: 1.1.7-16.1

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated kxl 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, 29 Jun 2016 21:11:43 +0200
Source: kxl
Binary: libkxl0 libkxl0-dev
Architecture: source
Version: 1.1.7-16.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Ben Hutchings 
Description:
 libkxl0- multimedia library for game development
 libkxl0-dev - development files for libkxl0
Closes: 826519
Changes:
 kxl (1.1.7-16.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Change package format to 3.0 (quilt), so patches are automatically applied
 and the .pc and .svn directories are excluded from the source package
   * Remove linux-kernel-headers from Build-Depends (Closes: #826519)
Checksums-Sha1:
 a4e11308eb2e015a7f147ceaa29f878640c573ae 1988 kxl_1.1.7-16.1.dsc
 511917d4e9ae218ff67543b8bb91f4c7c4ecdb17 178576 kxl_1.1.7-16.1.debian.tar.xz
Checksums-Sha256:
 8203573ae39e6e53ebe31c55657750c0b836399fcf7fecb2ebc79e3b8aba9b39 1988 
kxl_1.1.7-16.1.dsc
 46373c2b227b633ad4344d5559d5918661eed7915a419cdeb09c5fa93f23f9b8 178576 
kxl_1.1.7-16.1.debian.tar.xz
Files:
 0d6e688ff0e799a9f346551c52f518e2 1988 devel optional kxl_1.1.7-16.1.dsc
 a941ab3143fbf3e6d6ce6d0f0dd123aa 178576 devel optional 
kxl_1.1.7-16.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIVAwUBV3Qgk+e/yOyVhhEJAQrx/RAAuWBRL6LsjXe5ZxBsylXTsrsyIuVehNtq
WoK/t1ODujRAfgeGFKteT7143O23uRi+ovYtbkGF6eEqe0hfHD0Xd6ZMiDoStGaR
18K41pD6MHuNAm9SIUWQV4EslRkG7+Td7DdcMEYsAcjbE2gHUfJSQOLONBD77lpy
jabAXRJTVpQcnrvGcioc+9rF1QWyuP+tw3teNcnsIHokRUIiGgtuSkMo1jAveiCG
78rMugelFIHkqdl6BmjibwgyYN1hIJSoBq844AXTv8NZSkgB9kQMNmxnEV9lhyro
/uIGTGOjaS1vkscIVJgYg/hOB1OxOei3EszMcpNzW7ciHegAAu0SX8w3CqrWm6ad
7rXY9yvFZxNgE+X4PnlEoElduQPrHMUkd59z4PaJohrQ/p8D5niKIn0N5sxdCFwL
CNL6r7tflIoih4+su4pwmEqi2d97KmzDX7SpfukF/gp3w4mXUPVqeprR0Yxhjllk
HGlsIPaO/fI4aZ0QKVIzGQwDmR92Z2Nib8FtnttIa005FVoI6emipKAmDPbdQJtT
uAteDHR8IN3OPnQT8BrlrsDVTs382ltV/Snc8tZeT6zytQIoQuf/Hu17AR74I9hT
WSMgFDFBpRV1KVlepdl/6E5fYNBAVANeNhvYK6c8zzyYkE8jH0//6bAHZCRBc2d3
xjwcbu7IKeo=
=Q3c4
-END PGP SIGNATURE End Message ---

Bug#826519: NMU diff for kxl 1.1.7-16.1

[Ben Hutchings]

I've attached the debdiff, filtered to exclude the deletion of .pc and
.svn directories.

Ben.

-- 

Ben Hutchings
Make three consecutive correct guesses and you will be considered an
expert.
diff -Nru kxl-1.1.7/debian/changelog kxl-1.1.7/debian/changelog
--- kxl-1.1.7/debian/changelog	2016-06-29 21:25:33.0 +0200
+++ kxl-1.1.7/debian/changelog	2016-06-29 21:11:44.0 +0200
@@ -1,3 +1,12 @@
+kxl (1.1.7-16.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Change package format to 3.0 (quilt), so patches are automatically applied
+and the .pc and .svn directories are excluded from the source package
+  * Remove linux-kernel-headers from Build-Depends (Closes: #826519)
+
+ -- Ben Hutchings   Wed, 29 Jun 2016 21:11:43 +0200
+
 kxl (1.1.7-16) unstable; urgency=low
 
   * Only depend on linux headers if os is linux (Closes: #638639)
diff -Nru kxl-1.1.7/debian/control kxl-1.1.7/debian/control
--- kxl-1.1.7/debian/control	2016-06-29 21:25:33.0 +0200
+++ kxl-1.1.7/debian/control	2016-06-29 20:49:55.0 +0200
@@ -24,7 +24,7 @@
 Package: libkxl0-dev
 Section: libdevel
 Architecture: any
-Depends: libkxl0 (= ${binary:Version}), libx11-dev, linux-kernel-headers [ linux-any ]
+Depends: libkxl0 (= ${binary:Version}), libx11-dev
 Description: development files for libkxl0
  KXL (Kacchan X Windows System Library) is a library targeted at game
  development that provides functions for simple image and sound output
diff -Nru kxl-1.1.7/debian/rules kxl-1.1.7/debian/rules
--- kxl-1.1.7/debian/rules	2016-06-29 21:25:33.0 +0200
+++ kxl-1.1.7/debian/rules	2016-06-29 20:49:55.0 +0200
@@ -18,7 +18,6 @@
 	cp -f /usr/share/misc/config.guess config.guess
 endif
 
-	QUILT_PATCHES=debian/patches quilt push -a || test $$? = 2
 	touch configure.in \
 	&& touch aclocal.m4 \
 	&& touch configure \
@@ -34,7 +33,6 @@
 	dh_testroot
 	rm -f build-stamp
 	[ ! -f Makefile ] || $(MAKE) distclean
-	QUILT_PATCHES=debian/patches quilt pop -a -R || test $$? = 2
 
 	rm -f config.sub config.guess config.log
 
diff -Nru kxl-1.1.7/debian/source/format kxl-1.1.7/debian/source/format
--- kxl-1.1.7/debian/source/format	1970-01-01 02:00:00.0 +0200
+++ kxl-1.1.7/debian/source/format	2016-06-29 20:38:58.0 +0200
@@ -0,0 +1 @@
+3.0 (quilt)


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

Bug#828767: marked as done (toxiproxy: FTBFS: B-D favors old mux, logrus packages)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jun 2016 21:21:53 +0200
with message-id 
and subject line Fixed in 2.0.0+dfsg1-2
has caused the Debian Bug report #828767,
regarding toxiproxy: FTBFS: B-D favors old mux, logrus packages
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.)


-- 
828767: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828767
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: toxiproxy
Version: 2.0.0+dfsg1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Automated builds of toxiproxy have been failing to start because its
build dependencies include

golang-mux-dev | golang-github-gorilla-mux-dev

golang-github-gorilla-mux-dev has replaced golang-mux-dev in the
archive, but the autobuilders don't care because they ignore
alternative dependencies for the sake of determinism (unless
architecture qualifiers explicitly eliminate earlier options).
Please either flip this dependency or specify just
golang-github-gorilla-mux-dev.

Likewise for golang-logrus-dev | golang-github-sirupsen-logrus-dev;
although there's still a transitional golang-logrus-dev package in the
archive, you shouldn't count on its long-term availability.

Thanks!

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

Kernel: Linux 4.5.0-2-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)

-- no debconf information
--- End Message ---
--- Begin Message ---
I have fixed this issue in 2.0.0+dfsg1-2.

Cheers,

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#811688: marked as done (FTBFS with GCC 6: enumerator value for... is not)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jun 2016 19:20:25 +
with message-id 
and subject line Bug#811688: fixed in nestopia 1.47-2
has caused the Debian Bug report #811688,
regarding FTBFS with GCC 6: enumerator value for... is not
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.)


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

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
...
> make[2]: Entering directory '/<>'
> g++ -Wdate-time -D_FORTIFY_SOURCE=2 -DNST_PRAGMA_ONCE -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -c 
> source/core/NstApu.cpp -o objs/core/NstApu.o
> source/core/NstApu.cpp: In member function 'void 
> Nes::Core::Apu::SaveState(Nes::Core::State::Saver&, Nes::dword) const':
> source/core/NstApu.cpp:492:6: warning: narrowing conversion of 
> '(Nes::uint)((const Nes::Core::Apu*)this)->Nes::Core::Apu::ctrl' from 
> 'Nes::uint {aka unsigned int}' to 'Nes::byte {aka unsigned char}' inside { } 
> [-Wnarrowing]
>   ctrl,
>   ^~~~
> 
> source/core/NstApu.cpp:493:12: warning: narrowing conversion of '(clock & 
> 255u)' from 'Nes::Core::Cycle {aka unsigned int}' to 'Nes::byte {aka unsigned 
> char}' inside { } [-Wnarrowing]
>   clock & 0xFF,
>   ~~^~
> 
> source/core/NstApu.cpp:494:12: warning: narrowing conversion of '(clock >> 
> 8)' from 'Nes::Core::Cycle {aka unsigned int}' to 'Nes::byte {aka unsigned 
> char}' inside { } [-Wnarrowing]
>   clock >> 8,
>   ~~^~~~
> 
> source/core/NstApu.cpp:495:13: warning: narrowing conversion of 
> '(Nes::word)((const 
> Nes::Core::Apu*)this)->Nes::Core::Apu::cycles.Nes::Core::Apu::Cycles::frameDivider'
>  from 'Nes::word {aka short unsigned int}' to 'Nes::byte {aka unsigned char}' 
> inside { } [-Wnarrowing]
>   cycles.frameDivider
>   ~~~^~~~
> 
> source/core/NstApu.cpp:516:12: warning: narrowing conversion of '(clock & 
> 255u)' from 'Nes::Core::Cycle {aka unsigned int}' to 'Nes::byte {aka unsigned 
> char}' inside { } [-Wnarrowing]
>   clock & 0xFF,
>   ~~^~
> 
> source/core/NstApu.cpp:517:12: warning: narrowing conversion of '(clock >> 
> 8)' from 'Nes::Core::Cycle {aka unsigned int}' to 'Nes::byte {aka unsigned 
> char}' inside { } [-Wnarrowing]
>   clock >> 8,
>   ~~^~~~
> 
> source/core/NstApu.cpp:518:28: warning: narrowing conversion of 
> '(int)(((short unsigned int)((const 
> Nes::Core::Apu*)this)->Nes::Core::Apu::cycles.Nes::Core::Apu::Cycles::frameIrqRepeat)
>  % 3u)' from 'int' to 'Nes::byte {aka unsigned char}' inside { } [-Wnarrowing]
>   cycles.frameIrqRepeat % 3
>   ~~^~~
> 
> source/core/NstApu.cpp: In member function 'void 
> Nes::Core::Apu::Channel::Envelope::SaveState(Nes::Core::State::Saver&, 
> Nes::dword) const':
> source/core/NstApu.cpp:1070:13: warning: narrowing conversion of '(((unsigned 
> int)((int)((const 
> Nes::Core::Apu::Channel::Envelope*)this)->Nes::Core::Apu::Channel::Envelope::regs[0]))
>  | (((bool)((const 
> Nes::Core::Apu::Channel::Envelope*)this)->Nes::Core::Apu::Channel::Envelope::reset)
>  ? 128u : 0u))' from 'unsigned int' to 'Nes::byte {aka unsigned char}' inside 
> { } [-Wnarrowing]
>  regs[0] | (reset ? 0x80U : 0x00U),
>  ^
> 
> source/core/NstApu.cpp: In member function 'void 
> Nes::Core::Apu::Triangle::SaveState(Nes::Core::State::Saver&, Nes::dword) 
> const':
> source/core/NstApu.cpp:1609:17: warning: narrowing conversion of '(unsigned 
> int)(((short unsigned int)((const 
> Nes::Core::Apu::Triangle*)this)->Nes::Core::Apu::Triangle::waveLength) & 
> 255u)' from 'unsigned int' to 'Nes::byte {aka unsigned char}' inside { } 
> [-Wnarrowing]
>   waveLength & 0xFFU,
>   ~~~^~~
> 
> source/core/NstApu.cpp:1610:17: warning: narrowing conversion of 
> '(((int)((const 
> Nes::Core::Apu::Triangle*)this)->Nes::Core::Apu::Triangle::waveLength) >> 8)' 
> from 'int' to 'Nes::byte {aka unsigned char}' inside { } [-Wnarrowing]
>   waveLength >> 8,
>   ~~~^~~~
> 
> source/

Bug#817360: aspell-sk: Removal of debhelper compat 4

[Pali Rohár]

Hi! Is somebody already migrating package aspell-sk to new debhleper?
If not, I can look at it.

-- 
Pali Rohár
pali.ro...@gmail.com


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

Bug#812280: newmat: FTBFS with GCC 6: terminate called

[Robert Davies]

Bug 812280 is an incompatibility between both newmat10 and newmat11
and the latest version of the C++ standard and is detected by both GCC 6 and
the latest version of Microsoft's C++. Its effect on users is pretty
minor but it needs fixing which I will do.

Robert

On Thu, 21 Jan 2016 19:54:42 -0800 Martin Michlmayr  wrote:
> Package: newmat
> Version: 1.10.4-5
> Severity: normal
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-6 gcc-6-unknown
>
> 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.
>
> Unfortunately, it's not clear from the log why the build failed.
> It's possible there's a bug in this package or in GCC.  It's also
> possible I reported a non-issue, although I tried to avoid that.
> I apologize in advance if this is the case.
>
> If you have some time to look into this issue, that'd be great.  If
> not, I can re-test the package with GCC 6 in a few weeks time.
>
> 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
> ...
> > All elements are zero
> > terminate called after throwing an instance of 'NEWMAT::ProgramException'
> >
> >   * Eighteenth test of Matrix package
> >   * Matrix

Processed: forcibly merging 826519 724639

[Debian Bug Tracking System]

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

> forcemerge 826519 724639
Bug #826519 [libkxl0-dev] Depends on obsolete package linux-kernel-headers
Bug #724639 [libkxl0-dev] Depends on old package linux-kernel-headers
Severity set to 'serious' from 'important'
Added tag(s) stretch and sid.
Merged 724639 826519
> thanks
Stopping processing here.

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

Bug#812289: marked as done (google-mock: FTBFS with GCC 6: test suite segfault)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jun 2016 18:21:41 +
with message-id 
and subject line Bug#812289: fixed in google-mock 1.7.0-18092013-2
has caused the Debian Bug report #812289,
regarding google-mock: FTBFS with GCC 6: test suite segfault
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.)


-- 
812289: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812289
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: google-mock
Version: 1.7.0-18092013-1
Severity: normal
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-unknown

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.

Unfortunately, it's not clear from the log why the build failed.
It's possible there's a bug in this package or in GCC.  It's also
possible I reported a non-issue, although I tried to avoid that.
I apologize in advance if this is the case.

If you have some time to look into this issue, that'd be great.  If
not, I can re-test the package with GCC 6 in a few weeks time.

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
...
> [   OK ] ExpectCallSyntaxTest.CompilesWithMethodNameExpandedFromMacro (0 
> ms)
> [ RUN  ] ExpectCallSyntaxTest.WorksWithMethodNameExpandedFromMacro
> [   OK ] ExpectCallSyntaxTest.WorksWithMethodNameExpandedFromMacro (0 ms)
> [ RUN  ] ExpectCallSyntaxTest.EvaluatesFirstArgumentOnce
> /bin/bash: line 5: 37395 Segmentation fault  ${dir}$tst
> FAIL: test/gmock-spec-builders_test
> Running main() from gmock_main.cc
> [==] Running 92 tests from 2 test cases.
> [--] Global test environment set-up.
> [--] 46 tests from LinkTest2
> [ RUN  ] LinkTest2.TestReturnVoid
> /bin/bash: line 5: 38660 Segmentation fault  ${dir}$tst
> FAIL: test/gmock_link_test
> 
> 2 of 2 tests failed
> Please report to googlem...@googlegroups.com
> 
> Makefile:882: recipe for target 'check-TESTS' failed

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: google-mock
Source-Version: 1.7.0-18092013-2

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

Debian distribution maintenance software
pp.
Fredrik Hallenberg  (supplier of updated google-mock 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, 29 Jun 2016 17:32:19 +0200
Source: google-mock
Binary: google-mock
Architecture: source amd64
Version: 1.7.0-18092013-2
Distribution: unstable
Urgency: medium
Maintainer: Fredrik Hallenberg 
Changed-By: Fredrik Hallenberg 
Description:
 google-mock - Google's framework for writing and using C++ mock classes
Closes: 812289
Changes:
 google-mock (1.7.0-18092013-2) unstable; urgency=medium
 .
   * Use -fno-delete-null-pointer-checks to work with gcc 6.
 (closes: #812289). Just a workaround, hopefully a proper fix is
 done in a future upstream release.
Checksums-Sha1:
 4272a8e08c29ef4c00c907c75a9022408c867d8b 1851 google-mock_1.7.0-18092013-2.dsc
 fecc4854563b686dd571f2099f62053dd9a1e52d 5412 
google-mock_1.7.0-18092013-2.debian.tar.xz
 e0f459efccecbfe1fe010282dbd1b40274fa0c76 117962 
google-mock_1.7.0-18092013-2_amd64.deb
Checksums-Sha256:
 77ff7b7bcd9a40c728e0edec4042c902ed0ffef24dfd7b3335dbbecffc677196 1851 
google-mock_1.7.0-18092013-2.dsc
 0687e89f4fabcc2c7bf9228d65431f288afc079a33c12494ea89fa56b507f7db 5412 
google-mock_1.7.0-18092013-2.debian.tar.xz
 9eeb98f138306c77b79699e5a51415bba8aa9555a022bc25ba921d7ca56574c7 117962 
google-mock_1.7.0-18092013-2_amd64.deb
Files:
 c3f17e8c3c7d0feee90be8c847445920 1851 devel optional 
google-mock_1.7.0-18092013-2.dsc
 0047e1ba3da755ffdc5035ad607d11bc 5412 devel optional 
googl

Bug#828986: liblrdf: FTBFS: devlibs error: There is no package matching [libraptor1-dev] and noone provides it, please report bug to d-shlibs maintainer

[Jonas Smedegaard]

Quoting Chris Lamb (2016-06-29 18:24:13)
>> this failure is most likely because your build environment is buggy
>
> It's always a fresh, clean container image that I recreate entirely 
> (not dist-upgrade) at 07:00 UTC on my laptop from the latest sid. I 
> run build-dep and then build with debuild; nothing special.

I believe that you do not expect your environment to be _too_ special, 
but highly suspect that you have applied some optimizations over, say, 
running debian-installer from bare metal for each and every build.

Can you try add an "apt update" in the build environment before building 
the package, and see if it still fails?


> Other systems -- including the reproducible builds servers -- can 
> reproduce the FTBFS, so I am not convinced at this point that my 
> environment is buggy.

Where do you see that?  The log currently linked from tracker.debian.org 
was another issue (since fixed in CDBS).


>> apt-file initializes its database when installed, and d-shlibs rely 
>> on that.
> 
> Ah, smells like the bug is there - d-shlibs does not depend on apt-file
[...] Sorry, not apt-file but apt-cache.  What d-shlibs rely on is an 
up-to-date APT cache (it calls "apt-cache --no-generate due to 
bug#630591 - which seems a no-op since ages but shouldn't fail either).

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#811851: marked as done (ossim: FTBFS with GCC 6: no match for)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jun 2016 17:44:11 +
with message-id 
and subject line Bug#811851: fixed in ossim 1.8.20.3+ds-4
has caused the Debian Bug report #811851,
regarding ossim: 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.)


-- 
811851: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811851
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ossim
Version: 1.8.20.3+ds-2
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
...
> cd /<>/ossim-1.8.20.3+ds/debian/build/src/ossim && /usr/bin/c++   
> -DOSSIMMAKINGDLL -Dossim_EXPORTS 
> -I/<>/ossim-1.8.20.3+ds/ossim/include 
> -I/<>/ossim-1.8.20.3+ds/debian/build/include -I/usr/include/geos 
> -I/usr/include/geotiff -I/usr/include/x86_64-linux-gnu 
> -I/usr/include/freetype2  -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -O3 -DNDEBUG -fPIC   
>  -o CMakeFiles/ossim.dir/font/ossimFont.cpp.o -c 
> /<>/ossim-1.8.20.3+ds/ossim/src/ossim/font/ossimFont.cpp
> /<>/ossim-1.8.20.3+ds/ossim/src/ossim/elevation/ossimElevManager.cpp:
>  In member function 'virtual std::ostream& 
> ossimElevManager::print(std::ostream&) const':
> /<>/ossim-1.8.20.3+ds/ossim/src/ossim/elevation/ossimElevManager.cpp:650:52:
>  error: no match for 'operator<<' (operand types are 
> 'std::basic_ostream' and 'std::ostream {aka std::basic_ostream}')
>   out<<"m_dbRoundRobin["< " ~~^~
--- End Message ---
--- Begin Message ---
Source: ossim
Source-Version: 1.8.20.3+ds-4

We believe that the bug you reported is fixed in the latest version of
ossim, 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.
Bas Couwenberg  (supplier of updated ossim 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, 29 Jun 2016 18:43:36 +0200
Source: ossim
Binary: libossim1 libossim-dev ossim-core
Architecture: source amd64
Version: 1.8.20.3+ds-4
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Description:
 libossim-dev - OSSIM library -- development files
 libossim1  - OSSIM library -- shared library
 ossim-core - OSSIM core utilities
Closes: 811851
Changes:
 ossim (1.8.20.3+ds-4) unstable; urgency=medium
 .
   * Team upload.
   * Add upstream patch to fix FTBFS with GCC 6.
 (closes: #811851)
   * Update watch file to handle other tar extensions.
   * Add patch to fix 'requested' typo.
Checksums-Sha1:
 8755ef36bfd803b06f92e6ddc0c82bbe33e844f1 2204 ossim_1.8.20.3+ds-4.dsc
 a6bbe014ce9dcc4cc93de2d218907fbbce2c1728 57692 
ossim_1.8.20.3+ds-4.debian.tar.xz
 905ea053a9ea15200d9b3778153c44f95e3c8b38 579432 
libossim-dev_1.8.20.3+ds-4_amd64.deb
 6f566bb2931b7c752fe0519e1bb998902759cbe6 49399088 
libossim1-dbgsym_1.8.20.3+ds-4_amd64.deb
 12602aa10640faea337125d5964b586169604915 4100858 
libossim1_1.8.20.3+ds-4_amd64.deb
 10ec26dba08cfe723218cf9b7d1b4ebea4b643cc 4067380 
ossim-core-dbgsym_1.8.20.3+ds-4_amd64.deb
 848c3e40e6cb634edc8a343241216268735080cc 374344 
ossim-core_1.8.20.3+ds-4_amd64.deb
Checksums-Sha256:
 2c73c73c033f1382ab9e2d8e07d79d65bf3a88db0cfac2fa494da2e72eb90618 2204 
ossim_1.8.20.3+ds-4.dsc
 dd46984330344e7f3f4135a7abb2548375f10e49df004872e3708d6c5056e303 57692 
ossim_1.8.20.3+ds-4.debian.tar.xz
 427be1f6c12a3479595188d7167f72633f15b4f0a7773749331352b93b2b9156 579432 
libossim-dev_1.8.20.3+ds-4_amd64.deb
 d52e6bb1bd7e2d6aae4763f07a254935d15f94f1460145e3b9fc7f8d02bb1ee6 4939908

Bug#811761: marked as done (cld2: FTBFS with GCC 6: narrowing conversion)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jun 2016 17:39:12 +
with message-id 
and subject line Bug#811761: fixed in cld2 0.0.0-git20150806-3
has caused the Debian Bug report #811761,
regarding cld2: FTBFS with GCC 6: narrowing conversion
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.)


-- 
811761: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811761
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cld2
Version: 0.0.0-git20150806-2
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-narrowing

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
...
> [ 29%] Building CXX object 
> CMakeFiles/cld2_full.dir/internal/cld_generated_cjk_delta_bi_32.cc.o
> /usr/bin/c++   -Dcld2_full_EXPORTS  -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -fPIC   -o 
> CMakeFiles/cld2_full.dir/internal/cld_generated_cjk_delta_bi_32.cc.o -c 
> /<>/internal/cld_generated_cjk_delta_bi_32.cc
> /<>/internal/scoreonescriptspan.cc: In function 'void 
> CLD2::ScoreEntireScriptSpan(const CLD2::LangSpan&, CLD2::ScoringContext*, 
> CLD2::DocTote*, CLD2::ResultChunkVector*)':
> /<>/internal/scoreonescriptspan.cc:1149:5: warning: narrowing 
> conversion of 'score' from 'int' to 'CLD2::uint16 {aka short unsigned int}' 
> inside { } [-Wnarrowing]
>  };
>  ^
> 
> /<>/internal/scoreonescriptspan.cc:1149:5: warning: narrowing 
> conversion of 'bytes' from 'int' to 'CLD2::uint16 {aka short unsigned int}' 
> inside { } [-Wnarrowing]
> /<>/internal/scoreonescriptspan.cc:1149:5: warning: narrowing 
> conversion of 'reliability' from 'int' to 'CLD2::uint8 {aka unsigned char}' 
> inside { } [-Wnarrowing]
> /<>/internal/scoreonescriptspan.cc:1149:5: warning: narrowing 
> conversion of 'reliability' from 'int' to 'CLD2::uint8 {aka unsigned char}' 
> inside { } [-Wnarrowing]
> /<>/internal/cld_generated_cjk_uni_prop_80.cc:7089:1: error: 
> narrowing conversion of '-14' from 'int' to 'CLD2::uint8 {aka unsigned char}' 
> inside { } [-Wnarrowing]
>  };
>  ^
> 
> /<>/internal/cld_generated_cjk_uni_prop_80.cc:7089:1: error: 
> narrowing conversion of '-14' from 'int' to 'CLD2::uint8 {aka unsigned char}' 
> inside { } [-Wnarrowing]
> /<>/internal/cld_generated_cjk_uni_prop_80.cc:7089:1: error: 
> narrowing conversion of '-14' from 'int' to 'CLD2::uint8 {aka unsigned char}' 
> inside { } [-Wnarrowing]
> /<>/internal/cld_generated_cjk_uni_prop_80.cc:7089:1: error: 
> narrowing conversion of '-14' from 'int' to 'CLD2::uint8 {aka unsigned char}' 
> inside { } [-Wnarrowing]
> /<>/internal/cld_generated_cjk_uni_prop_80.cc:7089:1: error: 
> narrowing conversion of '-14' from 'int' to 'CLD2::uint8 {aka unsigned char}' 
> inside { } [-Wnarrowing]
> /<>/internal/cld_generated_cjk_uni_prop_80.cc:7089:1: error: 
> narrowing conversion of '-14' from 'int' to 'CLD2::uint8 {aka unsigned char}' 
> inside { } [-Wnarrowing]
> /<>/internal/cld_generated_cjk_uni_prop_80.cc:7089:1: error: 
> narrowing conversion of '-14' from 'int' to 'CLD2::uint8 {aka unsigned char}' 
> inside { } [-Wnarrowing]
> /<>/internal/cld_generated_cjk_uni_prop_80.cc:7089:1: error: 
> narrowing conversion of '-14' from 'int' to 'CLD2::uint8 {aka unsigned char}' 
> inside { } [-Wnarrowing]
> /<>/internal/cld_generated_cjk_uni_prop_80.cc:7089:1: error: 
> narrowing conversion of '-14' from 'int' to 'CLD2::uint8 {aka unsigned char}' 
> inside { } [-Wnarrowing]
> /<>/internal/cld_generated_cjk_uni_prop_80.cc:7089:1: error: 
> narrowing conversion of '-14' from 'int' to 'CLD2::uint8 {aka unsigned char}' 
> inside { } [-Wnarrowing]
> /<>/internal/cld_generated_cjk_uni_prop_80.cc:7089:1: error: 
> narrowing conversion of '-14' from 'int' to 'CLD2::uint8 {aka unsigned char}' 
> inside { } [-Wnarrowing]
> /<>/internal/cld_generated_cjk_uni_prop_80.cc:7089:1: error: 
> narrowing conversion of '-14' from 'int' to 'CLD2::uint8 {aka unsigned char}' 
> inside { } [-Wnarrowing]
> /<>/internal/cld_generated_cjk_uni_prop_80.cc:7089:1: error: 
> narrowing conversion of '-14' from 'int' to 'CLD2::uint8 {aka unsigned char}' 
> inside { } [-Wnarrowing]
> /<>/internal/cld_generated_cjk_uni_

Bug#827716: Non-maintainer upload to fix RC bugs

[Ondřej Surý]

Works for me, thanks!


On 29 June 2016 5:04:54 PM Daniel James  wrote:


Hi Ondřej,


Daniel James already closed some of the bugs in
https://anonscm.debian.org/cgit/collab-maint/tidy.git/


I'd be happy to merge other fixes I have made since version 1:5.2.0-1
into http://anonscm.debian.org/cgit/collab-maint/tidy-html5.git/ if
that's OK with you.

After that, we could take down the original collab-maint repo to avoid
confusion, perhaps.

Cheers!

Daniel

Bug#829003: wine: FTBFS since unicode 9 update

[Jens Reyer]

Package: wine
Version: 1.8.3-1
Severity: serious
Justification: FTBFS/BD-Uninstallable


wine build-depends on missing unicode-data (< 9.0-1), but that isn't
available anymore.

I started working on a patch to backport the Unicode 9 changes to Wine
1.8, but haven't it ready yet. Basically it should all be in the
following 2 commits:

commit 58e0972c5ca8c82f65860733aaf3aeb41a7725bb
Author: Nikolay Sivov 
Date:   Wed Jun 22 15:00:22 2016 +0300

Update data tables to Unicode 9.0.0.

Signed-off-by: Nikolay Sivov 
Signed-off-by: Alexandre Julliard 

commit bbb9bbdbdb330aca21c363503274e21d558db1bc
Author: Nikolay Sivov 
Date:   Thu Jun 23 00:02:31 2016 +0300

dwrite: Update line breaking algorithm according to Unicode 9.0.0
specification.

Signed-off-by: Nikolay Sivov 
Signed-off-by: Alexandre Julliard 


Large parts of these 2 commits apply to files that we regenerate and
have added to d/clean. So they can and must be ignored.

I'll try to get something ready as time permits.

Greets
jre

Processed: Re: Bug#818193: aaphoto: Jasper removal

[Debian Bug Tracking System]

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

> tags 818193 pending
Bug #818193 [src:aaphoto] aaphoto: Jasper removal
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#818193: aaphoto: Jasper removal

[Denis Briand]

tags 818193 pending
thanks 


On Tue, Jun 28, 2016 at 09:46:28PM +0200, Andras Horvath wrote:
> Hi, thank you for your swift answer. I'll try to fix it and let you know ASAP.
> Andras

Hi Andras,
Many thanks!
Ping me as soon as possible when it will be done.
I will build again and upload aaphoto debian package.

regards

Denis


signature.asc
Description: Digital signature

Bug#828991: libaudit1 gained a dependency against libcap-ng.so.0 which is installed in /usr

[Laurent Bigonville]

Le 29/06/16 à 17:56, Simon McVittie a écrit :

Is there consensus that supporting this situation is worth developers'
time?
I don't think so and I don't think that there is a lot of our userbase 
is even using this (well apparently last time this broke at least tree 
different people have opened a bug report about it)

Processed: Re: Bug#811794: 3dldf: FTBFS with GCC 6: error: reference is ambiguous

[Debian Bug Tracking System]

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

> forwarded 811794 https://savannah.gnu.org/bugs/?48345
Bug #811794 [3dldf] 3dldf: FTBFS with GCC 6: error: reference is ambiguous
Set Bug forwarded-to-address to 'https://savannah.gnu.org/bugs/?48345'.
> stop
Stopping processing here.

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

Bug#811794: 3dldf: FTBFS with GCC 6: error: reference is ambiguous

[Preuße]

forwarded 811794 https://savannah.gnu.org/bugs/?48345
stop

On 20.01.2016 03:04, Martin Michlmayr wrote:

> 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.
> 
Forwarded for now. I'll try to ping the upstream maintainer on his address.

H.
-- 
http://www.hilmar-preusse.de.vu/   #206401 http://counter.li.org

Bug#828986: liblrdf: FTBFS: devlibs error: There is no package matching [libraptor1-dev] and noone provides it, please report bug to d-shlibs maintainer

[Jonas Smedegaard]

Hi Chris,

Quoting Chris Lamb (2016-06-29 16:28:30)
> liblrdf fails to build from source in unstable/amd64:
[...]
>   d-shlibmove --commit \
> --movedev "debian/tmp/usr/include/*" usr/include/ \
> --movedev "debian/tmp/usr/lib/pkgconfig/*.pc" usr/lib/pkgconfig/ \
> --moveshl debian/tmp/usr/share/ladspa/rdf/ladspa.rdfs 
> usr/share/ladspa/rdf/ \
> debian/tmp/usr/lib/liblrdf.so
>   Library package automatic movement utility
>   devlibs error: There is no package matching [libraptor1-dev] and noone 
> provides it, please report bug to d-shlibs maintainer
>   debian/rules:65: recipe for target 'binary-post-install/liblrdf0' failed
>   make: *** [binary-post-install/liblrdf0] Error 1

Like a previous report from you this failure is most likely because your 
build environment is buggy: apt-file initializes its database when 
installed, and d-shlibs rely on that.

One way that can happen is if your environment blocks network access not 
only during build but also during installation of build-dependencies.

Another idea is a race condition: Cache filling being slower than 
running the build.

In short: Please check that your environment has a working apt-file, and 
_after_ that is examined test if the build still fails.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#828979: pyosmium: FTBFS in testing (FAIL: test_location_tuple)

[Sebastiaan Couwenberg]

Control: tags -1 upstream
Control: forwarded -1 https://github.com/osmcode/pyosmium/issues/15

Hi Santiago,

Thanks for reporting this issue, I've forwarded it upstream.

I suspect the test failure is caused by changes in Python 2.7.12~rc1,
because all the tests succeeded with Python 2.7.11.

Kind Regards,

Bas

Processed: Re: Bug#828979: pyosmium: FTBFS in testing (FAIL: test_location_tuple)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream
Bug #828979 [src:pyosmium] pyosmium: FTBFS in testing (FAIL: 
test_location_tuple)
Added tag(s) upstream.
> forwarded -1 https://github.com/osmcode/pyosmium/issues/15
Bug #828979 [src:pyosmium] pyosmium: FTBFS in testing (FAIL: 
test_location_tuple)
Set Bug forwarded-to-address to 'https://github.com/osmcode/pyosmium/issues/15'.

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

Processed: Re: Bug#828767: toxiproxy: FTBFS: B-D favors old mux, logrus packages

[Debian Bug Tracking System]

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

> notfixed 828767 2.0.0+dfsg1-2
Bug #828767 {Done: Alexandre Viau } [src:toxiproxy] 
toxiproxy: FTBFS: B-D favors old mux, logrus packages
No longer marked as fixed in versions toxiproxy/2.0.0+dfsg1-2.
> found 828767 2.0.0+dfsg1-2
Bug #828767 {Done: Alexandre Viau } [src:toxiproxy] 
toxiproxy: FTBFS: B-D favors old mux, logrus packages
Marked as found in versions toxiproxy/2.0.0+dfsg1-2 and reopened.
> thanks
Stopping processing here.

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

Bug#828767: toxiproxy: FTBFS: B-D favors old mux, logrus packages

[Aaron M. Ucko]

notfixed 828767 2.0.0+dfsg1-2
found 828767 2.0.0+dfsg1-2
thanks

"Aaron M. Ucko"  writes:

> Please either flip this dependency or specify just
> golang-github-gorilla-mux-dev.
>
> Likewise for golang-logrus-dev | golang-github-sirupsen-logrus-dev;

Thanks for the quick upload, but these failures are still occurring --
it looks like you accidentally left this change out of -2.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Processed: limit source to dahdi-tools, tagging 795977, tagging 810404, tagging 811932

[Debian Bug Tracking System]

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

> limit source dahdi-tools
Limiting to bugs with field 'source' containing at least one of 'dahdi-tools'
Limit currently set to 'source':'dahdi-tools'

> tags 795977 + pending
Bug #795977 [src:dahdi-tools] dahdi-tools: please make the build reproducible
Added tag(s) pending.
> tags 810404 + pending
Bug #810404 [dahdi-tools] dahdi-tools: please switch to libusb 1.0
Added tag(s) pending.
> tags 811932 + pending
Bug #811932 [dahdi-tools] dahdi-tools: FTBFS with GCC 6: defined but not used
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#828902: utidylib: please update for new tidy-html5

[Daniel James]

Hi Michal,

My understand is that the API is not meant to be changed in libtidy5
relative to the earlier versions of libtidy. Thanks for creating the
upstream pull request.

Cheers!

Daniel

Bug#827716: Non-maintainer upload to fix RC bugs

[Daniel James]

Hi Ondřej,

> Daniel James already closed some of the bugs in
> https://anonscm.debian.org/cgit/collab-maint/tidy.git/

I'd be happy to merge other fixes I have made since version 1:5.2.0-1
into http://anonscm.debian.org/cgit/collab-maint/tidy-html5.git/ if
that's OK with you.

After that, we could take down the original collab-maint repo to avoid
confusion, perhaps.

Cheers!

Daniel

Processed: block 828991 with 828992

[Debian Bug Tracking System]

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

> block 828991 with 828992
Bug #828991 [libaudit1] libaudit1 gained a dependency against libcap-ng.so.0 
which is installed in /usr
828991 was not blocked by any bugs.
828991 was not blocking any bugs.
Added blocking bug(s) of 828991: 828992
> thanks
Stopping processing here.

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

Bug#828991: libaudit1 gained a dependency against libcap-ng.so.0 which is installed in /usr

[Laurent Bigonville]

Package: libaudit1
Version: 1:2.6.1-1
Severity: serious

Hi,

Just a bug to prevent audit 2.6.1 to migrate to testing.

This new version just gained a dependency against libcap-ng0 which is
installed in /usr.

This is bad(tm) as it might break the boot (and other stuffs) for users
that don't have /usr present at early boot.

One of the solution (until we have usrmerge) is to move libcap-ng to
/lib

Laurent Bigonville

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

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

Versions of packages libaudit1 depends on:
ii  libaudit-common  1:2.6.1-1
ii  libc62.22-13
ii  libcap-ng0   0.7.7-2

libaudit1 recommends no packages.

libaudit1 suggests no packages.

-- no debconf information

Bug#828984: dune-functions: FTBFS: 63% tests passed, 3 tests failed out of 8

[Chris Lamb]

Source: dune-functions
Version: 2.4~20160406ge6b3b4c-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,

dune-functions fails to build from source in unstable/amd64:

  [..]

  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160629153731.qPUdNMHeCo.dune-functions/dune-functions-2.4~20160406ge6b3b4c/obj-x86_64-linux-gnu'
  cd 
"/home/lamby/temp/cdt.20160629153731.qPUdNMHeCo.dune-functions/dune-functions-2.4~20160406ge6b3b4c/obj-x86_64-linux-gnu"
 && /usr/bin/cmake -E cmake_depends "Unix Makefiles" 
"/home/lamby/temp/cdt.20160629153731.qPUdNMHeCo.dune-functions/dune-functions-2.4~20160406ge6b3b4c"
 
"/home/lamby/temp/cdt.20160629153731.qPUdNMHeCo.dune-functions/dune-functions-2.4~20160406ge6b3b4c/examples"
 
"/home/lamby/temp/cdt.20160629153731.qPUdNMHeCo.dune-functions/dune-functions-2.4~20160406ge6b3b4c/obj-x86_64-linux-gnu"
 
"/home/lamby/temp/cdt.20160629153731.qPUdNMHeCo.dune-functions/dune-functions-2.4~20160406ge6b3b4c/obj-x86_64-linux-gnu/examples"
 
"/home/lamby/temp/cdt.20160629153731.qPUdNMHeCo.dune-functions/dune-functions-2.4~20160406ge6b3b4c/obj-x86_64-linux-gnu/examples/CMakeFiles/stokes-taylorhood.dir/DependInfo.cmake"
 --color=
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160629153731.qPUdNMHeCo.dune-functions/dune-functions-2.4~20160406ge6b3b4c/obj-x86_64-linux-gnu'
  cd 
"/home/lamby/temp/cdt.20160629153731.qPUdNMHeCo.dune-functions/dune-functions-2.4~20160406ge6b3b4c/obj-x86_64-linux-gnu"
 && /usr/bin/cmake -E cmake_depends "Unix Makefiles" 
"/home/lamby/temp/cdt.20160629153731.qPUdNMHeCo.dune-functions/dune-functions-2.4~20160406ge6b3b4c"
 
"/home/lamby/temp/cdt.20160629153731.qPUdNMHeCo.dune-functions/dune-functions-2.4~20160406ge6b3b4c/examples"
 
"/home/lamby/temp/cdt.20160629153731.qPUdNMHeCo.dune-functions/dune-functions-2.4~20160406ge6b3b4c/obj-x86_64-linux-gnu"
 
"/home/lamby/temp/cdt.20160629153731.qPUdNMHeCo.dune-functions/dune-functions-2.4~20160406ge6b3b4c/obj-x86_64-linux-gnu/examples"
 
"/home/lamby/temp/cdt.20160629153731.qPUdNMHeCo.dune-functions/dune-functions-2.4~20160406ge6b3b4c/obj-x86_64-linux-gnu/examples/CMakeFiles/advection-reaction-dg.dir/DependInfo.cmake"
 --color=
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160629153731.qPUdNMHeCo.dune-functions/dune-functions-2.4~20160406ge6b3b4c/obj-x86_64-linux-gnu'
  cd 
"/home/lamby/temp/cdt.20160629153731.qPUdNMHeCo.dune-functions/dune-functions-2.4~20160406ge6b3b4c/obj-x86_64-linux-gnu"
 && /usr/bin/cmake -E cmake_depends "Unix Makefiles" 
"/home/lamby/temp/cdt.20160629153731.qPUdNMHeCo.dune-functions/dune-functions-2.4~20160406ge6b3b4c"
 
"/home/lamby/temp/cdt.20160629153731.qPUdNMHeCo.dune-functions/dune-functions-2.4~20160406ge6b3b4c/examples"
 
"/home/lamby/temp/cdt.20160629153731.qPUdNMHeCo.dune-functions/dune-functions-2.4~20160406ge6b3b4c/obj-x86_64-linux-gnu"
 
"/home/lamby/temp/cdt.20160629153731.qPUdNMHeCo.dune-functions/dune-functions-2.4~20160406ge6b3b4c/obj-x86_64-linux-gnu/examples"
 
"/home/lamby/temp/cdt.20160629153731.qPUdNMHeCo.dune-functions/dune-functions-2.4~20160406ge6b3b4c/obj-x86_64-linux-gnu/examples/CMakeFiles/poisson-pq2.dir/DependInfo.cmake"
 --color=
  Scanning dependencies of target poisson-pq2
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160629153731.qPUdNMHeCo.dune-functions/dune-functions-2.4~20160406ge6b3b4c/obj-x86_64-linux-gnu'
  make -f examples/CMakeFiles/poisson-pq2.dir/build.make 
examples/CMakeFiles/poisson-pq2.dir/build
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160629153731.qPUdNMHeCo.dune-functions/dune-functions-2.4~20160406ge6b3b4c/obj-x86_64-linux-gnu'
  Scanning dependencies of target stokes-taylorhood
  Scanning dependencies of target advection-reaction-dg
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160629153731.qPUdNMHeCo.dune-functions/dune-functions-2.4~20160406ge6b3b4c/obj-x86_64-linux-gnu'
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160629153731.qPUdNMHeCo.dune-functions/dune-functions-2.4~20160406ge6b3b4c/obj-x86_64-linux-gnu'
  make -f examples/CMakeFiles/advection-reaction-dg.dir/build.make 
examples/CMakeFiles/advection-reaction-dg.dir/build
  make -f examples/CMakeFiles/stokes-taylorhood.dir/build.make 
examples/CMakeFiles/stokes-taylorhood.dir/build
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160629153731.qPUdNMHeCo.dune-functions/dune-functions-2.4~20160406ge6b3b4c/obj-x86_64-linux-gnu'
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160629153731.qPUdNMHeCo.dune-functions/dune-functions-2.4~20160406ge6b3b4c/obj-x86_64-linux-gnu'
  [ 16%] Building CXX object 
examples/CMakeFiles/poisson-pq2.dir/poisson-pq2.cc.o
  cd 
"/home/lamby/temp/cdt.20160629153731.qPUdNMHeCo.dune-functions/dune-functions-2.4~20160406ge6b3b4c/obj-x86_64-linux-gnu/examples"
 && /usr/bin/c++   -DHAVE_CONFIG_H 
-I"/home/lamby/temp/cdt.20160629153731.qPUdNMHeCo.

Bug#828985: golang-github-gosimple-slug: FTBFS: FAIL: TestSubstituteLang (0.00s) slug_test.go:155: 1. Substitute("o a o", map[string]string{"o":"no", "a":"or"}) = "no nor no"; want "no or no"

[Chris Lamb]

Source: golang-github-gosimple-slug
Version: 1.0-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,

golang-github-gosimple-slug fails to build from source in unstable/amd64:

  [..]

  
  
**
  ** Starting build 
  **
  
**
  
   Package:  golang-github-gosimple-slug
   Version:  1.0-1
   Build architecture:   amd64
   Date: Wed, 29 Jun 2016 15:55:39 +0200
   Hostname: 8d018f376876
   Uname:Linux 8d018f376876 4.5.0-2-amd64 #1 SMP Debian 4.5.4-1 
(2016-05-16) x86_64 GNU/Linux
   /etc/timezone:Africa/Johannesburg
  
  
**
  ** Installing build dependencies  
  **
  
**
  
  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'golang-github-gosimple-slug-build-deps' in 
'../golang-github-gosimple-slug-build-deps_1.0-1_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package 
golang-github-gosimple-slug-build-deps.
  (Reading database ... 23075 files and directories currently installed.)
  Preparing to unpack golang-github-gosimple-slug-build-deps_1.0-1_all.deb ...
  Unpacking golang-github-gosimple-slug-build-deps (1.0-1) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
dh-golang golang-1.6-go golang-1.6-src golang-github-rainycape-unidecode-dev
golang-go golang-src
  Suggested packages:
bzr ca-certificates mercurial subversion
  Recommended packages:
pkg-config
  The following NEW packages will be installed:
dh-golang golang-1.6-go golang-1.6-src golang-github-rainycape-unidecode-dev
golang-go golang-src
  0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 26.8 MB of archives.
  After this operation, 192 MB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 dh-golang all 1.18 
[9278 B]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 golang-1.6-src amd64 
1.6.2-2 [6784 kB]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 golang-1.6-go amd64 
1.6.2-2 [19.7 MB]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 golang-src amd64 
2:1.6.1+1 [2974 B]
  Get:5 http://httpredir.debian.org/debian sid/main amd64 golang-go amd64 
2:1.6.1+1 [21.9 kB]
  Get:6 http://httpredir.debian.org/debian sid/main amd64 
golang-github-rainycape-unidecode-dev all 0.0~git20150906.0.c9cf8cd-1 [267 kB]
  Fetched 26.8 MB in 0s (108 MB/s)
  Selecting previously unselected package dh-golang.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 23079 files and directories currently installed.)
  Preparing to unpack .../dh-golang_1.18_all.deb ...
  Unpacking dh-golang (1.18) ...
  Selecting previously unselected package golang-1.6-src.
  Preparing to unpack .../golang-1.6-src_1.6.2-2_amd64.deb ...
  Unpacking golang-1.6-src (1.6.2-2) ...
  Selecting previously unselected package golang-1.6-go.
  Preparing to unpack .../golang-1.6-go_1.6.2-2_amd64.deb ...
  Unpacking golang-1.6-go (1.6.2-2) ...
  Selecting previously unselected package golang-src.
  Preparing to unpack .../golang-src_2%3a1.6.1+1_amd64.deb ...
  Unpacking golang-src (2:1.6.1+1) ...
  Selecting previously unselected package golang-go.
  Preparing to unpack .../golang-go_2%3a1.6.1+1_amd64.deb ...
  Unpacking golang-go (2:1.6.1+1) ...
  Selecting previously unselected package golang-github-rainycape-unidecode-dev.
  Preparing to unpack 
.../golang-github-rainycape-unidecode-dev_0.0~git20150906.0.c9cf8cd-1_al

Bug#828902: utidylib: please update for new tidy-html5

[Michal Čihař]

Hi

Dne 29.6.2016 v 15:40 Gianfranco Costamagna napsal(a):
> control: tags -1 -patch
> 
>> No, it doesn't, it segfaults, so the API has probably changed somewhere.
>> Is there upstream documentation on changes between original libtidy and
>> this fork?
> 
> 
> I'm ccing the maintainer, I have no knowledge on this matter.

I've looked deeper into the crash and I believe it's bug in the library
and I've opened pull request with fix [1], let's see what upstream tells
about it.

[1]: https://github.com/htacg/tidy-html5/pull/426

PS: Besides that there are many incompatibilities as default settings
have been changed. The testsuite can be fixed to adjust to this, but I'm
not sure about unexpected results for users...

-- 
Michal Čihař | http://cihar.com/ | https://weblate.org/



signature.asc
Description: OpenPGP digital signature

Bug#828981: pyx: FTBFS in testing (LaTeX Error: File `iftex.sty' not found)

[Santiago Vila]

Package: src:pyx
Version: 0.12.1-5
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
Severity: serious

Dear maintainer:

This package currently fails to build in stretch:


[...]
make -C _build/latex all-pdf
make[3]: Entering directory '/<>/faq/_build/latex'
pdflatex  'pyxfaq.tex'
This is pdfTeX, Version 3.14159265-2.6-1.40.17 (TeX Live 2016/Debian) 
(preloaded format=pdflatex)
 restricted \write18 enabled.
entering extended mode
(./pyxfaq.tex
LaTeX2e <2016/03/31> patch level 1
Babel <3.9r> and hyphenation patterns for 3 language(s) loaded.
(./sphinxmanual.cls
Document Class: sphinxmanual 2009/06/02 Document class (Sphinx manual)
(/usr/share/texlive/texmf-dist/tex/latex/base/report.cls
Document Class: report 2014/09/29 v1.4h Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo)))

! LaTeX Error: File `iftex.sty' not found.


A full build log is available here:

https://tests.reproducible-builds.org/debian/rbuild/testing/amd64/pyx_0.12.1-5.rbuild.log

Thanks.

Bug#828979: pyosmium: FTBFS in testing (FAIL: test_location_tuple)

[Santiago Vila]

Package: src:pyosmium
Version: 2.7.1-2
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
Severity: serious

Dear maintainer:

This package currently fails to build in stretch:


[...]
FAIL: test_location_tuple (test_writer.TestWriteNode)
--
Traceback (most recent call last):
  File "/build/pyosmium-2.7.1/test/test_writer.py", line 112, in 
test_location_tuple
w.add_node(O(location=(1, 2)))
  File "/usr/lib/python2.7/contextlib.py", line 24, in __exit__
self.gen.next()
  File "/build/pyosmium-2.7.1/test/test_writer.py", line 35, in WriteExpect
assert_equals(line, expected)
AssertionError: 'n0 v0 dV c0 t i0 u T x1 y2' != 'n0 v0 dV c0 t i0 u T 
x1.000 y2.000'


A full build log is available here:

https://tests.reproducible-builds.org/debian/rbuild/testing/amd64/pyosmium_2.7.1-2.rbuild.log

Thanks.

Bug#828980: pyx3: FTBFS in testing (LaTeX Error: File `iftex.sty' not found)

[Santiago Vila]

Package: src:pyx3
Version: 0.14.1-2
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
Severity: serious

Dear maintainer:

This package currently fails to build in stretch:


[...]
make -C _build/latex all-pdf
make[3]: Entering directory '/<>/faq/_build/latex'
pdflatex  'pyxfaq.tex'
This is pdfTeX, Version 3.14159265-2.6-1.40.17 (TeX Live 2016/Debian) 
(preloaded format=pdflatex)
 restricted \write18 enabled.
entering extended mode
(./pyxfaq.tex
LaTeX2e <2016/03/31> patch level 1
Babel <3.9r> and hyphenation patterns for 3 language(s) loaded.
(./sphinxmanual.cls
Document Class: sphinxmanual 2009/06/02 Document class (Sphinx manual)
(/usr/share/texlive/texmf-dist/tex/latex/base/report.cls
Document Class: report 2014/09/29 v1.4h Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo)))

! LaTeX Error: File `iftex.sty' not found.


A full build log is available here:

https://tests.reproducible-builds.org/debian/rbuild/testing/amd64/pyx3_0.14.1-2.rbuild.log

Thanks.

Bug#818757: Bug#818757: orthanc-postgresql: does not start

[Andreas Tille]

Hi Sebastien,

On Wed, Jun 29, 2016 at 03:28:53PM +0200, Sebastien Jodogne wrote:
> 
> > Any chance a -dbgsyms package can be provided ?
> 
> I have no idea of how this can be done in Debian together with CMake; I am
> unable to understand the wiki [1]. Furthermore, besides keeping the symbols,
> it would be really important to compile in Debug mode, otherwise the trace
> would be very hard to understand.

That's usually created automatically since a certain point of time if
you build the package.  I intended to verify this for
orthanc-postgresql_2.0 but get a build error. :-(

...
JsonCpp include dir: /usr/include/jsoncpp
-- Looking for C++ include /usr/include/jsoncpp/json/reader.h
-- Looking for C++ include /usr/include/jsoncpp/json/reader.h - found
-- Could NOT find PostgreSQL (missing:  PostgreSQL_TYPE_INCLUDE_DIR) (found 
version "9.5.3")
-- Looking for C++ include orthanc/OrthancCppDatabasePlugin.h
-- Looking for C++ include orthanc/OrthancCppDatabasePlugin.h - found
Setting the version of the libraries to 2.0
CMake Error: The following variables are used in this project, but they are set 
to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake 
files:
PostgreSQL_TYPE_INCLUDE_DIR (ADVANCED)
   used as include directory in directory /build/orthanc-postgresql-2.0
   used as include directory in directory /build/orthanc-postgresql-2.0
   used as include directory in directory /build/orthanc-postgresql-2.0
   used as include directory in directory /build/orthanc-postgresql-2.0
   used as include directory in directory /build/orthanc-postgresql-2.0
   used as include directory in directory /build/orthanc-postgresql-2.0
   used as include directory in directory /build/orthanc-postgresql-2.0
   used as include directory in directory /build/orthanc-postgresql-2.0
   used as include directory in directory /build/orthanc-postgresql-2.0

-- Configuring incomplete, errors occurred!
See also "/build/orthanc-postgresql-2.0/Build/CMakeFiles/CMakeOutput.log".
See also "/build/orthanc-postgresql-2.0/Build/CMakeFiles/CMakeError.log".
"tail -v -n +0 CMakeCache.txt"
==> CMakeCache.txt <==
# This is the CMakeCache file.
# For build in directory: /build/orthanc-postgresql-2.0/Build
...

Kind regards

  Andreas.

-- 
http://fam-tille.de

Processed: Bug#828963 marked as pending

[Debian Bug Tracking System]

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

> tag 828963 pending
Bug #828963 [src:squirrel3] squirrel3: FTBFS: Makefile:66: recipe for target 
'stdlib.pdf' failed
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#828963: marked as pending

[Fabian Wolff]

tag 828963 pending
thanks

Hello,

Bug #828963 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=collab-maint/squirrel3.git;a=commitdiff;h=ed1ef7a

---
commit ed1ef7a724a3fe1ae98bf95b46a9383ee1a044aa
Author: Fabian Wolff 
Date:   Wed Jun 29 15:57:05 2016 +0200

Add texlive-generic-extra as build dependency to fix FTBFS with new sphinx 
version

diff --git a/debian/changelog b/debian/changelog
index 48a8b64..d704145 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8 +1,10 @@
 squirrel3 (3.1-3) UNRELEASED; urgency=medium
 
   * Add Vcs-Git and Vcs-Browser fields to debian/control.
+  * Fix FTBFS with new sphinx version by adding texlive-generic-extra
+to build dependencies in debian/control (Closes: #828963).
 
- -- Fabian Wolff   Sun, 26 Jun 2016 15:42:32 +0200
+ -- Fabian Wolff   Wed, 29 Jun 2016 15:56:02 +0200
 
 squirrel3 (3.1-2) unstable; urgency=medium
 

Bug#826022: Does not work with Django 1.8

[Dominique Belhachemi]

I am going to upload a new package tonight.
Upstream removed only the Python 2.6 support, Python 2.7 is still
supported, so I will keep the python2 package.

-Dominique

Bug#818203: marked as done (imagemagick: Jasper removal)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jun 2016 13:49:49 +
with message-id 
and subject line Bug#818203: fixed in imagemagick 8:6.8.9.9-7.2
has caused the Debian Bug report #818203,
regarding imagemagick: Jasper removal
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.)


-- 
818203: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818203
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: imagemagick
Severity: important
User: j...@debian.org
Usertags: jasper-rm

Hi, jasper will be removed from Debian for the stretch release (and
following that, the archive in general).

It's been unmaintained for nearly a decade, please als see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812630

Your package uses jasper, so please either remove the JPEG2000
functionality or move to a supported implementation (e.g. openjpeg or
ffmpeg).

A removal tracker has been setup by the release team at
https://release.debian.org/transitions/html/jasper-rm.html

This bug will be bumped to release-critical status in a few weeks.

Cheers,

Moritz 
--- End Message ---
--- Begin Message ---
Source: imagemagick
Source-Version: 8:6.8.9.9-7.2

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated imagemagick 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: Mon, 27 Jun 2016 12:55:02 +
Source: imagemagick
Binary: imagemagick-common imagemagick-doc libmagickcore-6-headers 
libmagickwand-6-headers libmagick++-6-headers imagemagick libimage-magick-perl 
libmagickcore-6-arch-config imagemagick-6.q16 libmagickcore-6.q16-2 
libmagickcore-6.q16-2-extra libmagickcore-6.q16-dev libmagickwand-6.q16-2 
libmagickwand-6.q16-dev libmagick++-6.q16-5v5 libmagick++-6.q16-dev 
imagemagick-dbg libimage-magick-q16-perl perlmagick libmagickcore-dev 
libmagickwand-dev libmagick++-dev
Architecture: source
Version: 8:6.8.9.9-7.2
Distribution: unstable
Urgency: medium
Maintainer: ImageMagick Packaging Team 

Changed-By: Mattia Rizzolo 
Description:
 imagemagick - image manipulation programs -- binaries
 imagemagick-6.q16 - image manipulation programs -- quantum depth Q16
 imagemagick-common - image manipulation programs -- infrastructure
 imagemagick-dbg - debugging symbols for ImageMagick
 imagemagick-doc - document files of ImageMagick
 libimage-magick-perl - Perl interface to the ImageMagick graphics routines
 libimage-magick-q16-perl - Perl interface to the ImageMagick graphics routines 
-- Q16 versio
 libmagick++-6-headers - object-oriented C++ interface to ImageMagick - header 
files
 libmagick++-6.q16-5v5 - object-oriented C++ interface to ImageMagick
 libmagick++-6.q16-dev - object-oriented C++ interface to ImageMagick - 
development files
 libmagick++-dev - object-oriented C++ interface to ImageMagick
 libmagickcore-6-arch-config - low-level image manipulation library - 
architecture header files
 libmagickcore-6-headers - low-level image manipulation library - header files
 libmagickcore-6.q16-2 - low-level image manipulation library -- quantum depth 
Q16
 libmagickcore-6.q16-2-extra - low-level image manipulation library - extra 
codecs (Q16)
 libmagickcore-6.q16-dev - low-level image manipulation library - development 
files (Q16)
 libmagickcore-dev - low-level image manipulation library -- transition package
 libmagickwand-6-headers - image manipulation library - headers files
 libmagickwand-6.q16-2 - image manipulation library
 libmagickwand-6.q16-dev - image manipulation library - development files
 libmagickwand-dev - image manipulation library - transition for development 
files
 perlmagick - Perl interface to ImageMagick -- transition package
Closes: 818203
Changes:
 imagemagick (8:6.8.9.9-7.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Remove libjasper-dev dependencies.  Closes: #818203
Checksums-Sha1:
 d7b3f8547fcf7f3e6c80e01a551f7e8dc8c6d70b 4197 imagemagick_6.8.9.9-7.2.dsc
 047729cfecdd620a81e819327a5b71b0059d3da3 204196 
imagemagick_6.8.9.9-7.2.debian

Bug#828902: utidylib: please update for new tidy-html5

[Gianfranco Costamagna]

control: tags -1 -patch

>No, it doesn't, it segfaults, so the API has probably changed somewhere.
>Is there upstream documentation on changes between original libtidy and
>this fork?


I'm ccing the maintainer, I have no knowledge on this matter.


cheers,

G.

Bug#828946: krb5: FTBFS in testing (LaTeX Error: File `iftex.sty' not found)

[Santiago Vila]

On Wed, Jun 29, 2016 at 08:32:08AM -0400, Sam Hartman wrote:
> For my notes, iftex.sty is in texlive-generic-extra on my system.
> I did the most recent build for sid in a chroot including the arch all
> packages, so it's more likely to be something changing than a
> then-missing-build-dep-indep, but I'll take a look while at Debconf.

For the record, I have a successful build log from 2016-06-05 for
exactly the same version 1.14.2+dfsg-1, which is certainly strange
because texlive-generic-extra is not in any of the build-depends.

While we are at it, both "dpkg-buildpackage -B" and "dpkg-buildpackage -A"
seem to work ok for this package. If you switch to make your uploads
as source-only (using "dpkg-buildpackage -S") we would get beautiful
and official build logs for archs "amd64" and "all" here:

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

Thanks.

Processed: Re: Bug#828902: utidylib: please update for new tidy-html5

[Debian Bug Tracking System]

Processing control commands:

> tags -1 -patch
Bug #828902 [src:utidylib] utidylib: please update for new tidy-html5
Ignoring request to alter tags of bug #828902 to the same tags previously set

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

Bug#818757: [Debian-med-packaging] Bug#818757: orthanc-postgresql: does not start

[Sebastien Jodogne]

>> After downloading the source code of each package, create a "Build"
>> directory inside, and run:
>>
>> # cmake .. -DSTATIC_BUILD=ON -DCMAKE_BUILD_TYPE=Debug
>> # make
>
> Attached a full backtrace of a stock Debian Orthanc 1.1.0
> with o-pg 2.0 (it is lacking symbols so might be of limited
> use).

Thanks, but unfortunately, this log does not show anything useful for 
debugging because of the lack of symbols.


Couldn't you try and statically link Orthanc and Orthanc-PG in debug 
mode following the commands written above? Or, at least, compile the 
Debian package from source and modify the "debian/rules" so as to add 
"-DCMAKE_BUILD_TYPE=Debug"?


Also, do you remember which versions of Orthanc and Orthanc-PG generated 
the database you try and upgrade?



> Any chance a -dbgsyms package can be provided ?

I have no idea of how this can be done in Debian together with CMake; I 
am unable to understand the wiki [1]. Furthermore, besides keeping the 
symbols, it would be really important to compile in Debug mode, 
otherwise the trace would be very hard to understand.


Sébastien-


[1] https://wiki.debian.org/DebugPackage

Bug#828902: utidylib: please update for new tidy-html5

[Michal Čihař]

Hi

Dne 28.6.2016 v 22:25 Gianfranco Costamagna napsal(a):
> please update the runtime dependency to the new tidy lib, I hope the binding 
> will still work

No, it doesn't, it segfaults, so the API has probably changed somewhere.
Is there upstream documentation on changes between original libtidy and
this fork?

> diff -Nru utidylib-0.2/debian/changelog utidylib-0.2/debian/changelog
> --- utidylib-0.2/debian/changelog 2014-02-23 13:54:41.0 +
> +++ utidylib-0.2/debian/changelog 2016-06-28 20:18:06.0 +
> @@ -1,3 +1,9 @@
> +utidylib (0.2-9.1) unstable; urgency=medium
> +
> +  * Use libtidy5 as runtime dependency.
> +
> + -- Gianfranco Costamagna   Tue, 28 Jun 2016 
> 22:04:19 +0200
> +
> utidylib (0.2-9build1) trusty; urgency=medium
> 
> * Rebuild to drop files installed into /usr/share/pyshared.
> diff -Nru utidylib-0.2/debian/control utidylib-0.2/debian/control
> --- utidylib-0.2/debian/control   2013-10-31 09:05:33.0 +
> +++ utidylib-0.2/debian/control   2016-06-28 20:16:58.0 +
> @@ -12,7 +12,7 @@
> 
> Package: python-utidylib
> Architecture: all
> -Depends: ${python:Depends}, ${misc:Depends}, libtidy-0.99-0 (>= 20051018)
> +Depends: ${python:Depends}, ${misc:Depends}, libtidy5
> Provides: ${python:Provides}
> Breaks: ${python:Breaks}
> Description: Python wrapper for TidyLib
> 
> I'll NMU/Team upload shortly if this blocks the transition.

Please don't do that unless you fix the code to work with new library as
well.

PS: Removing patch tag as the patch is obviously incomplete.

-- 
Michal Čihař | http://cihar.com/ | https://weblate.org/



signature.asc
Description: OpenPGP digital signature

Processed: tagging 828902

[Debian Bug Tracking System]

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

> tags 828902 - patch
Bug #828902 [src:utidylib] utidylib: please update for new tidy-html5
Removed tag(s) patch.
> thanks
Stopping processing here.

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

Processed: Re: disque: FTBFS on kFreeBSD: TCP_KEEP* undeclared

[Debian Bug Tracking System]

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

> forwarded 810032 https://github.com/redis/hiredis/pull/254
Bug #810032 [src:disque] disque: FTBFS on kFreeBSD: TCP_KEEP* undeclared
Changed Bug forwarded-to-address to 'https://github.com/redis/hiredis/pull/254' 
from 'https://github.com/antirez/disque/issues/186'.
> thanks
Stopping processing here.

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

Bug#810032: disque: FTBFS on kFreeBSD: TCP_KEEP* undeclared

[Chris Lamb]

forwarded 810032 https://github.com/redis/hiredis/pull/254
thanks

Hi,

I've forwarded this issue upstream here:

 https://github.com/redis/hiredis/pull/254

It just needs a third-party code-copy sync.  


Regards,

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

Processed: Re: disque: FTBFS on big-endian systems

[Debian Bug Tracking System]

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

> forwarded 810032 https://github.com/antirez/disque/issues/186
Bug #810032 [src:disque] disque: FTBFS on kFreeBSD: TCP_KEEP* undeclared
Set Bug forwarded-to-address to 'https://github.com/antirez/disque/issues/186'.
> thanks
Stopping processing here.

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

Bug#828626: marked as done (phpmyadmin: doesn't install)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jun 2016 15:17:51 +0200
with message-id <55f6090f-bee0-f2b5-9fa8-e06cee2cf...@cihar.com>
and subject line Re: Bug#828626: phpmyadmin: doesn't install
has caused the Debian Bug report #828626,
regarding phpmyadmin: doesn't install
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.)


-- 
828626: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828626
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: phpmyadmin
Version: 4:4.6.2-2
Severity: critical
Justification: breaks unrelated software

Dear Maintainer,

The phpmyadmin package won't install and kind of breaks apt, using dpkg 
--configure -a to revert it.
This is how the attempt to install it looks like. If it's worth mentioning, I'm 
using mariadb 10.1 with their sid repo. 
But things worked out well so far, the previous version is still up and running.

Preparing to unpack .../phpmyadmin_4%3a4.6.3-1_all.deb ...
Determining localhost credentials from /etc/mysql/debian.cnf: succeeded.
dpkg: warning: subprocess old pre-removal script returned error exit status 10
dpkg: trying script from the new package instead ...
Determining localhost credentials from /etc/mysql/debian.cnf: succeeded.
dpkg: error processing archive 
/var/cache/apt/archives/phpmyadmin_4%3a4.6.3-1_all.deb (--unpack):
 subprocess new pre-removal script returned error exit status 10
dbconfig-common: flushing administrative password
*** Error in `/usr/bin/dpkg': munmap_chunk(): invalid pointer: 
0x55dd69942005 ***
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x71fc5)[0x7fba8d86afc5]
/lib/x86_64-linux-gnu/libc.so.6(+0x77966)[0x7fba8d870966]
/usr/bin/dpkg(+0x1ffb0)[0x55dd674d0fb0]
/usr/bin/dpkg(+0x20409)[0x55dd674d1409]
/usr/bin/dpkg(+0x2774a)[0x55dd674d874a]
/usr/bin/dpkg(+0x16a37)[0x55dd674c7a37]
/usr/bin/dpkg(+0x16c35)[0x55dd674c7c35]
/usr/bin/dpkg(+0x16e7d)[0x55dd674c7e7d]
/usr/bin/dpkg(+0xa207)[0x55dd674bb207]
/usr/bin/dpkg(+0x1feeb)[0x55dd674d0eeb]
/usr/bin/dpkg(+0x200f1)[0x55dd674d10f1]
/usr/bin/dpkg(+0x9c88)[0x55dd674bac88]
/usr/bin/dpkg(+0x6659)[0x55dd674b7659]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7fba8d8195f0]
/usr/bin/dpkg(+0x6769)[0x55dd674b7769]
=== Memory map: 
55dd674b1000-55dd674f5000 r-xp  08:05 655675 
/usr/bin/dpkg
55dd676f5000-55dd676f8000 r--p 00044000 08:05 655675 
/usr/bin/dpkg
55dd676f8000-55dd676f9000 rw-p 00047000 08:05 655675 
/usr/bin/dpkg
55dd676f9000-55dd6790d000 rw-p  00:00 0 
55dd697f2000-55dd6bd1a000 rw-p  00:00 0  [heap]
7fba8c714000-7fba8c72a000 r-xp  08:05 5902353
/lib/x86_64-linux-gnu/libgcc_s.so.1
7fba8c72a000-7fba8c929000 ---p 00016000 08:05 5902353
/lib/x86_64-linux-gnu/libgcc_s.so.1
7fba8c929000-7fba8c92a000 rw-p 00015000 08:05 5902353
/lib/x86_64-linux-gnu/libgcc_s.so.1
7fba8c92a000-7fba8c935000 r-xp  08:05 5898683
/lib/x86_64-linux-gnu/libnss_files-2.22.so
7fba8c935000-7fba8cb34000 ---p b000 08:05 5898683
/lib/x86_64-linux-gnu/libnss_files-2.22.so
7fba8cb34000-7fba8cb35000 r--p a000 08:05 5898683
/lib/x86_64-linux-gnu/libnss_files-2.22.so
7fba8cb35000-7fba8cb36000 rw-p b000 08:05 5898683
/lib/x86_64-linux-gnu/libnss_files-2.22.so
7fba8cb36000-7fba8cb3c000 rw-p  00:00 0 
7fba8cb3c000-7fba8cb46000 r-xp  08:05 5898685
/lib/x86_64-linux-gnu/libnss_nis-2.22.so
7fba8cb46000-7fba8cd46000 ---p a000 08:05 5898685
/lib/x86_64-linux-gnu/libnss_nis-2.22.so
7fba8cd46000-7fba8cd47000 r--p a000 08:05 5898685
/lib/x86_64-linux-gnu/libnss_nis-2.22.so
7fba8cd47000-7fba8cd48000 rw-p b000 08:05 5898685
/lib/x86_64-linux-gnu/libnss_nis-2.22.so
7fba8cd48000-7fba8cd5d000 r-xp  08:05 5898680
/lib/x86_64-linux-gnu/libnsl-2.22.so
7fba8cd5d000-7fba8cf5c000 ---p 00015000 08:05 5898680
/lib/x86_64-linux-gnu/libnsl-2.22.so
7fba8cf5c000-7fba8cf5d000 r--p 00014000 08:05 5898680
/lib/x86_64-linux-gnu/libnsl-2.22.so
7fba8cf5d000-7fba8cf5e000 rw-p 00015000 08:05 5898680
/lib/x86_64-linux-gnu/libnsl-2.22.so
7fba8cf5e000-7fba8cf6 rw-p  00:00 0 
7fba8cf6-7fba8cf67000 r-xp  08:05 5898681
/lib/x86_64-linux-gnu/libnss_compat-2.22.so
7fba8cf67000-7fba8d166000 ---p 7000 08:05 5898681 

Bug#810030: disque: FTBFS on big-endian systems

[Chris Lamb]

forwarded 810032 https://github.com/antirez/disque/issues/186
thanks

@juricast filed this upstream.


Regards,

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

Bug#828953: mxt-app FTBFS on 32bit architectures (i386, mips) on testing

[Nick Dyer]

Upstream fix in https://github.com/atmel-maxtouch/mxt-app/commit/da412c8b92867

Do you want me to tag it?

cheers

Nick

Processed: raise severity of GCC 6 ftbfs issues in preparation for GCC defaults change

[Debian Bug Tracking System]

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

> severity 816569 serious
Bug #816569 [mrs] mrs: FTBFS with GCC 6: was not declared in this scope
Bug #822466 [mrs] mrs: FTBFS: error: 'log' was not declared in this scope
Ignoring request to change severity of Bug 816569 to the same value.
Ignoring request to change severity of Bug 822466 to the same value.
> severity 811591 serious
Bug #811591 [ifhp] FTBFS with GCC 6: statement indented as if it were guarded by
Severity set to 'serious' from 'important'
> severity 811634 serious
Bug #811634 [meshlab] FTBFS with GCC 6: cannot convert x to y
Severity set to 'serious' from 'important'
> severity 811682 serious
Bug #811682 [gtkmathview] FTBFS with GCC 6: could not convert a from x to y
Severity set to 'serious' from 'important'
> severity 811575 serious
Bug #811575 [nss] FTBFS with GCC 6: statement indented as if it were guarded by
Severity set to 'serious' from 'important'
> severity 811576 serious
Bug #811576 [tpm-tools] FTBFS with GCC 6: statement indented as if it were 
guarded by
Severity set to 'serious' from 'important'
> severity 811577 serious
Bug #811577 [sgt-puzzles] FTBFS with GCC 6: statement indented as if it were 
guarded by
Severity set to 'serious' from 'important'
> severity 811578 serious
Bug #811578 [confetti] FTBFS with GCC 6: statement indented as if it were 
guarded by
Severity set to 'serious' from 'important'
> severity 811579 serious
Bug #811579 [mosh] FTBFS with GCC 6: statement indented as if it were guarded by
Severity set to 'serious' from 'important'
> severity 811582 serious
Bug #811582 [ion] FTBFS with GCC 6: statement indented as if it were guarded by
Severity set to 'serious' from 'important'
> severity 811584 serious
Bug #811584 [phalanx] FTBFS with GCC 6: statement indented as if it were 
guarded by
Severity set to 'serious' from 'important'
> severity 811585 serious
Bug #811585 [clutter-gesture] FTBFS with GCC 6: statement indented as if it 
were guarded by
Severity set to 'serious' from 'important'
> severity 811587 serious
Bug #811587 [libsoldout] FTBFS with GCC 6: statement indented as if it were 
guarded by
Severity set to 'serious' from 'important'
> severity 811593 serious
Bug #811593 [libgetopt++] FTBFS with GCC 6: statement indented as if it were 
guarded by
Severity set to 'serious' from 'important'
> severity 811594 serious
Bug #811594 [chordii] FTBFS with GCC 6: statement indented as if it were 
guarded by
Severity set to 'serious' from 'important'
> severity 811600 serious
Bug #811600 [systemtap] FTBFS with GCC 6: statement indented as if it were 
guarded by
Severity set to 'serious' from 'important'
> severity 811602 serious
Bug #811602 [sword] FTBFS with GCC 6: multiple errors
Severity set to 'serious' from 'important'
> severity 811604 serious
Bug #811604 [crash] FTBFS with GCC 6: statement indented as if it were guarded 
by
Severity set to 'serious' from 'important'
> severity 811605 serious
Bug #811605 [gxneur] FTBFS with GCC 6: statement indented as if it were guarded 
by
Severity set to 'serious' from 'important'
> severity 811606 serious
Bug #811606 [mongodb] FTBFS with GCC 6: multiple errors
Severity set to 'serious' from 'important'
> severity 811610 serious
Bug #811610 [faketime] FTBFS with GCC 6: nonnull argument compared to NULL
Severity set to 'serious' from 'important'
> severity 811611 serious
Bug #811611 [libclaw] FTBFS with GCC 6: cannot convert x to y
Severity set to 'serious' from 'important'
> severity 811612 serious
Bug #811612 [nvidia-texture-tools] FTBFS with GCC 6: cannot convert x to y
Severity set to 'serious' from 'important'
> severity 811613 serious
Bug #811613 [libphonenumber] FTBFS with GCC 6: cannot convert x to y
Severity set to 'serious' from 'important'
> severity 811616 serious
Bug #811616 [warmux] FTBFS with GCC 6: cannot convert x to y
Severity set to 'serious' from 'important'
> severity 811617 serious
Bug #811617 [supertransball2] FTBFS with GCC 6: cannot convert x to y
Severity set to 'serious' from 'important'
> severity 811618 serious
Bug #811618 [dsc-statistics] FTBFS with GCC 6: cannot convert x to y
Severity set to 'serious' from 'important'
> severity 811619 serious
Bug #811619 [gbgoffice] FTBFS with GCC 6: cannot convert x to y
Severity set to 'serious' from 'important'
> severity 811621 serious
Bug #811621 [critterding] FTBFS with GCC 6: cannot convert x to y
Severity set to 'serious' from 'important'
> severity 811622 serious
Bug #811622 [crtmpserver] FTBFS with GCC 6: cannot convert x to y
Severity set to 'serious' from 'important'
> severity 811624 serious
Bug #811624 [syncevolution] FTBFS with GCC 6: cannot convert x to y
Severity set to 'serious' from 'important'
> severity 811626 serious
Bug #811626 [berusky2] FTBFS with GCC 6: cannot convert x to y
Severity set to 'serious' from 'important'
> severity 811627 serious
Bug #811627 [kyotocabinet] FTBFS with GCC 6: cannot convert x to y
Severity set to 'serious' from 'important'
> severity 811628 serious
Bug 

Bug#818757: [Debian-med-packaging] Bug#818757: orthanc-postgresql: does not start

[Karsten Hilbert]

On Wed, Jun 29, 2016 at 08:07:17AM +0200, Sebastien Jodogne wrote:

> What I would need would be a full backtrace of the C++ code. This requires a
> fresh build in debug mode, with static linking, of both Orthanc 1.1.0 and
> PostgreSQL plugin 2.0. Static linking allows to become independent of a
> potential instability of your Debian setup.
> 
> After downloading the source code of each package, create a "Build"
> directory inside, and run:
> 
> # cmake .. -DSTATIC_BUILD=ON -DCMAKE_BUILD_TYPE=Debug
> # make
> 
> Obviously, make sure that your Orthanc configuration points to the newly
> built PostgreSQL plugin.
> 
> Then, please post the full gdb backtrace (command "bt") of the crash when
> you try and run [Orthanc]

Attached a full backtrace of a stock Debian Orthanc 1.1.0
with o-pg 2.0 (it is lacking symbols so might be of limited
use).

Any chance a -dbgsyms package can be provided ?

Karsten
-- 
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346
Skript gestartet auf Mi 29 Jun 2016 14:40:04 CEST
root@hermes:~/bin# gdb --args /usr/sbin/Orthanc --trace 
--logdir=/var/log/orthanc /etc/orthanc/
GNU gdb (Debian 7.11.1-2) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/sbin/Orthanc...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/sbin/Orthanc --trace --logdir=/var/log/orthanc 
/etc/orthanc/
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
*** stack smashing detected ***: /usr/sbin/Orthanc terminated
=== Backtrace: =
/lib/i386-linux-gnu/libc.so.6(+0x6929b)[0xb717629b]
/lib/i386-linux-gnu/libc.so.6(__fortify_fail+0x37)[0xb7205eb7]
/lib/i386-linux-gnu/libc.so.6(+0xf8e78)[0xb7205e78]
/usr/share/orthanc/plugins/libOrthancPostgreSQLStorage.so(+0x11284)[0xb7fac284]
/usr/share/orthanc/plugins/libOrthancPostgreSQLStorage.so(+0xa9bf)[0xb7fa59bf]
/usr/share/orthanc/plugins/libOrthancPostgreSQLStorage.so(OrthancPluginInitialize+0xab)[0xb7fabd7b]
/usr/sbin/Orthanc(+0xd8007)[0x800d8007]
/usr/sbin/Orthanc(+0xd8b70)[0x800d8b70]
/usr/sbin/Orthanc(+0xd8161)[0x800d8161]
/usr/sbin/Orthanc(main+0x4cd)[0x8002400d]
/lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf7)[0xb7125517]
/usr/sbin/Orthanc(+0x2b568)[0x8002b568]
=== Memory map: 
8000-802ad000 r-xp  08:01 6288261/usr/sbin/Orthanc
802ad000-802b1000 r--p 002ac000 08:01 6288261/usr/sbin/Orthanc
802b1000-802b2000 rw-p 002b 08:01 6288261/usr/sbin/Orthanc
802b2000-804e7000 rw-p  00:00 0  [heap]
b4978000-b49a8000 r-xp  08:01 6898193
/usr/lib/i386-linux-gnu/libpq.so.5.8
b49a8000-b49aa000 r--p 0002f000 08:01 6898193
/usr/lib/i386-linux-gnu/libpq.so.5.8
b49aa000-b49ab000 rw-p 00031000 08:01 6898193
/usr/lib/i386-linux-gnu/libpq.so.5.8
b49ab000-b49df000 r-xp  08:01 6899772
/usr/lib/i386-linux-gnu/libjsoncpp.so.0.10.5
b49df000-b49e r--p 00033000 08:01 6899772
/usr/lib/i386-linux-gnu/libjsoncpp.so.0.10.5
b49e-b49e1000 rw-p 00034000 08:01 6899772
/usr/lib/i386-linux-gnu/libjsoncpp.so.0.10.5
b4a34000-b4a3d000 rw-p  00:00 0 
b4a3d000-b4a44000 r-xp  08:01 6899295
/usr/lib/i386-linux-gnu/libffi.so.6.0.4
b4a44000-b4a45000 r--p 6000 08:01 6899295
/usr/lib/i386-linux-gnu/libffi.so.6.0.4
b4a45000-b4a46000 rw-p 7000 08:01 6899295
/usr/lib/i386-linux-gnu/libffi.so.6.0.4
b4a46000-b4a5a000 r-xp  08:01 8151438
/lib/i386-linux-gnu/libgpg-error.so.0.19.0
b4a5a000-b4a5b000 r--p 00013000 08:01 8151438
/lib/i386-linux-gnu/libgpg-error.so.0.19.0
b4a5b000-b4a5c000 rw-p 00014000 08:01 8151438
/lib/i386-linux-gnu/libgpg-error.so.0.19.0
b4a5c000-b4a6e000 r-xp  08:01 6899143
/usr/lib/i386-linux-gnu/libtasn1.so.6.5.2
b4a6e000-b4a6f000 ---p 00012000 08:01 6899143
/usr/lib/i386-linux-gnu/libtasn1.so.6.5.2
b4a6f000-b4a7 r--p 00012000 08:01 6899143
/usr/lib/i386-linux-gnu/libtasn1.so.6.5.2
b4a7-b4a71000 rw-p 00013000 08:01 6899143
/usr/lib/i386-linux-gnu/libtasn1.so.6.5.2
b4a71000-b4a72000 rw-p  00:00 0 
b4a72000-b4ace000 r-xp  08:01 6898110
/usr/lib/i386-linux-gnu/libp11-kit.so.0.1.0
b4ace000-b4ad3000 r--p 0005b000 08:01 6898110
/usr/lib/i386-linux-gnu/libp11-kit.so.0.1.0
b4ad3000-b4ad4000 rw-p 

Processed: bug forwarded upstream

[Debian Bug Tracking System]

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

> forwarded 828953 https://github.com/atmel-maxtouch/mxt-app/issues/52
Bug #828953 [mxt-app] mxt-app FTBFS on 32bit architectures (i386, mips) on 
testing
Set Bug forwarded-to-address to 
'https://github.com/atmel-maxtouch/mxt-app/issues/52'.
> thanks
Stopping processing here.

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

Bug#828946: krb5: FTBFS in testing (LaTeX Error: File `iftex.sty' not found)

[Sam Hartman]

For my notes, iftex.sty is in texlive-generic-extra on my system.
I did the most recent build for sid in a chroot including the arch all
packages, so it's more likely to be something changing than a
then-missing-build-dep-indep, but I'll take a look while at Debconf.

Bug#828963: squirrel3: FTBFS: Makefile:66: recipe for target 'stdlib.pdf' failed

[Chris Lamb]

Source: squirrel3
Version: 3.1-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

squirrel3 fails to build from source in unstable/amd64:

  [..]

  dh clean
 dh_testdir
 dh_auto_clean
 dh_clean
   debian/rules build
  dh build
 dh_testdir
 dh_update_autotools_config
 debian/rules override_dh_auto_configure
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160629140947.K29HDt9qCU.squirrel3/squirrel3-3.1'
  dh_auto_configure --buildsystem=cmake -- \
-DINSTALL_LIB_DIR=lib/x86_64-linux-gnu \
-DINSTALL_INC_DIR=include/squirrel3 \
-DDISABLE_STATIC="" -DLONG_OUTPUT_NAMES=""
cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DINSTALL_LIB_DIR=lib/x86_64-linux-gnu 
-DINSTALL_INC_DIR=include/squirrel3 -DDISABLE_STATIC= -DLONG_OUTPUT_NAMES=
  -- The C compiler identification is GNU 5.4.0
  -- The CXX compiler identification is GNU 5.4.0
  -- Check for working C compiler: /usr/bin/cc
  -- Check for working C compiler: /usr/bin/cc -- works
  -- Detecting C compiler ABI info
  -- Detecting C compiler ABI info - done
  -- Detecting C compile features
  -- Detecting C compile features - done
  -- Check for working CXX compiler: /usr/bin/c++
  -- Check for working CXX compiler: /usr/bin/c++ -- works
  -- Detecting CXX compiler ABI info
  -- Detecting CXX compiler ABI info - done
  -- Detecting CXX compile features
  -- Detecting CXX compile features - done
  -- Configuring done
  -- Generating done
  CMake Warning:
Manually-specified variables were not used by the project:
  
  CMAKE_INSTALL_LOCALSTATEDIR
  CMAKE_INSTALL_SYSCONFDIR
  DISABLE_STATIC
  LONG_OUTPUT_NAMES
  
  
  -- Build files have been written to: 
/home/lamby/temp/cdt.20160629140947.K29HDt9qCU.squirrel3/squirrel3-3.1/obj-x86_64-linux-gnu
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160629140947.K29HDt9qCU.squirrel3/squirrel3-3.1'
 dh_auto_build
make -j1
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160629140947.K29HDt9qCU.squirrel3/squirrel3-3.1/obj-x86_64-linux-gnu'
  /usr/bin/cmake 
-H/home/lamby/temp/cdt.20160629140947.K29HDt9qCU.squirrel3/squirrel3-3.1 
-B/home/lamby/temp/cdt.20160629140947.K29HDt9qCU.squirrel3/squirrel3-3.1/obj-x86_64-linux-gnu
 --check-build-system CMakeFiles/Makefile.cmake 0
  /usr/bin/cmake -E cmake_progress_start 
/home/lamby/temp/cdt.20160629140947.K29HDt9qCU.squirrel3/squirrel3-3.1/obj-x86_64-linux-gnu/CMakeFiles
 
/home/lamby/temp/cdt.20160629140947.K29HDt9qCU.squirrel3/squirrel3-3.1/obj-x86_64-linux-gnu/CMakeFiles/progress.marks
  make -f CMakeFiles/Makefile2 all
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20160629140947.K29HDt9qCU.squirrel3/squirrel3-3.1/obj-x86_64-linux-gnu'
  make -f squirrel/CMakeFiles/squirrel.dir/build.make 
squirrel/CMakeFiles/squirrel.dir/depend
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160629140947.K29HDt9qCU.squirrel3/squirrel3-3.1/obj-x86_64-linux-gnu'
  cd 
/home/lamby/temp/cdt.20160629140947.K29HDt9qCU.squirrel3/squirrel3-3.1/obj-x86_64-linux-gnu
 && /usr/bin/cmake -E cmake_depends "Unix Makefiles" 
/home/lamby/temp/cdt.20160629140947.K29HDt9qCU.squirrel3/squirrel3-3.1 
/home/lamby/temp/cdt.20160629140947.K29HDt9qCU.squirrel3/squirrel3-3.1/squirrel 
/home/lamby/temp/cdt.20160629140947.K29HDt9qCU.squirrel3/squirrel3-3.1/obj-x86_64-linux-gnu
 
/home/lamby/temp/cdt.20160629140947.K29HDt9qCU.squirrel3/squirrel3-3.1/obj-x86_64-linux-gnu/squirrel
 
/home/lamby/temp/cdt.20160629140947.K29HDt9qCU.squirrel3/squirrel3-3.1/obj-x86_64-linux-gnu/squirrel/CMakeFiles/squirrel.dir/DependInfo.cmake
 --color=
  Scanning dependencies of target squirrel
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160629140947.K29HDt9qCU.squirrel3/squirrel3-3.1/obj-x86_64-linux-gnu'
  make -f squirrel/CMakeFiles/squirrel.dir/build.make 
squirrel/CMakeFiles/squirrel.dir/build
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160629140947.K29HDt9qCU.squirrel3/squirrel3-3.1/obj-x86_64-linux-gnu'
  [  4%] Building CXX object squirrel/CMakeFiles/squirrel.dir/sqapi.cpp.o
  cd 
/home/lamby/temp/cdt.20160629140947.K29HDt9qCU.squirrel3/squirrel3-3.1/obj-x86_64-linux-gnu/squirrel
 && /usr/bin/c++   -D_SQ64 -Dsquirrel_EXPORTS 
-I/home/lamby/temp/cdt.20160629140947.K29HDt9qCU.squirrel3/squirrel3-3.1/include
  -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -Wall 
-pedantic -fno-exceptions -fno-strict-aliasing -fno-rtti -std=c++11 -Wdate-time 
-D_FORTIFY_SOURCE=2  -fno-rtti -std=c++0x -fPIC   -fno-exceptions 
-fno-strict-aliasing -Wall -Wextra -pedantic -Wcast-qual -o 
CMakeFiles/squirrel.dir/sqapi.cpp.o -c 
/home/lamby/temp/cdt.20160629140947.K29HDt9qCU.squirrel3/squirrel3-3.1/squirrel/sqapi.cpp
  [  8%] Building CXX objec

Bug#818210: marked as done (ziproxy: Jasper removal)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jun 2016 10:58:04 +
with message-id 
and subject line Bug#818210: fixed in ziproxy 3.3.1-2.1
has caused the Debian Bug report #818210,
regarding ziproxy: Jasper removal
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.)


-- 
818210: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818210
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ziproxy
Severity: important
User: j...@debian.org
Usertags: jasper-rm

Hi, jasper will be removed from Debian for the stretch release (and
following that, the archive in general).

It's been unmaintained for nearly a decade, please als see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812630

Your package uses jasper, so please either remove the JPEG2000
functionality or move to a supported implementation (e.g. openjpeg or
ffmpeg).

A removal tracker has been setup by the release team at
https://release.debian.org/transitions/html/jasper-rm.html

This bug will be bumped to release-critical status in a few weeks.

Cheers,

Moritz 
--- End Message ---
--- Begin Message ---
Source: ziproxy
Source-Version: 3.3.1-2.1

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated ziproxy 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: Mon, 27 Jun 2016 10:06:07 +
Source: ziproxy
Binary: ziproxy
Architecture: source
Version: 3.3.1-2.1
Distribution: unstable
Urgency: medium
Maintainer: Marcos Talau 
Changed-By: Mattia Rizzolo 
Description:
 ziproxy- compressing HTTP proxy server
Closes: 809492 818210
Changes:
 ziproxy (3.3.1-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/rules
 - Build without jasper support.
   * debian/control
 - Use HTTPS in Vcs-* fields.
 - Drop build-depends on jasper.  Closes: #818210
 - Correctly format extended description.  Closes: #809492
Checksums-Sha1:
 aa86ec25697f1b9a7f3f4ea01d46531a95225e1e 1904 ziproxy_3.3.1-2.1.dsc
 b6d28d5fd6a25aa7ad460bf1c6885b6e39d1f499 7192 ziproxy_3.3.1-2.1.debian.tar.xz
Checksums-Sha256:
 2501d0a768cb9ca3c873ed04e0e5ff6877f2551c0e12b5d3cc50c52b84e2a0be 1904 
ziproxy_3.3.1-2.1.dsc
 1f8f4db3d3ddbdd599dbc742d65d6d52970b037d98ba869bd24196a052bcb382 7192 
ziproxy_3.3.1-2.1.debian.tar.xz
Files:
 bc993f40c6078291a66db1ce239b75cc 1904 net extra ziproxy_3.3.1-2.1.dsc
 5f160268ad997805aa1ef4f0237310d2 7192 net extra ziproxy_3.3.1-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJXcPz+AAoJEEsEP825REVA++oP+QGaLa2zuznqY1ei8Ox9muuF
xw4vHb8VDSFFIWWVJkeNlgw7N5nHCM/N6d1GsUxu/ISDCrDUbc7tkkQ+0bTtMinh
bPNV0c9V1xAIPPSTik2ihX78UEpknnI7nfpcB3hCfHqKSSA6x1QOWClVrz24KYPw
YVz2g+rWhT38sJxNrJEYN2sjC42rKkN2X1Swo0+WeYP4ArVmrrDStnn9vDXw3wAf
ExwCPXEU8F+CtMOy1bdtRa47E3kkh1HntcXEK5BjXGIQrb/yE3Llowklx2qbvDkh
rKD+N4X8w1meU55HMpuB8PPHxvAu5RO2fgXiNavujAMPzvUD46OXh1vY2LafeyXb
rspU/jkoSRlJ7OxnV1IKVeiImMHTYS2mR9w24kEzj6Ynlsy9BeQCG9Rtcbr4Rmzk
tiSaDBc4xxa3jZmyIdRNvfpGTrY0FKAYIVYyHSKOr4nRveVh6WLKLLOPSYnzUi2H
R2eboaBwn7ZK2BMLm2mJoCWBnqXcaus3sB/y8lj78Lq66UvUV0bDgI7KrryYhct7
ak/0Cv+tngiocVs9iZvguJuy+sHoWJN4R8JaMuT4J64W/d01XTlTNBV60jUg1a8U
rCdFrnTA0px8GZZkM/BqEkcUNCsi7W3O4wIz3Tb/9kHuuKrrINKxxGp/QpS2creS
TdvZ8UJ6amDFihg+SpQj
=CxWc
-END PGP SIGNATURE End Message ---

Bug#828224: marked as done (nose: FTBFS: FAIL: runTest (test_coverage_plugin.TestCoveragePlugin) [..] AssertionError: False is not true)

[Debian Bug Tracking System]

Your message dated Wed, 29 Jun 2016 10:52:24 +
with message-id 
and subject line Bug#828224: fixed in nose 1.3.7-2
has caused the Debian Bug report #828224,
regarding nose: FTBFS: FAIL: runTest (test_coverage_plugin.TestCoveragePlugin) 
[..] AssertionError: False is not true
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.)


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

nose fails to build from source in unstable/amd64:

  [..]

  test_function_test_case_fixtures (test_cases.TestNoseCases) ... ok
  test_method_test_case (test_cases.TestNoseCases) ... ok
  test_method_test_case_fixtures (test_cases.TestNoseCases) ... ok
  test_method_test_case_with_metaclass (test_cases.TestNoseCases) ... ok
  test_address (test_cases.TestNoseTestWrapper) ... ok
  test_case_fixtures_called (test_cases.TestNoseTestWrapper)
  Instance fixtures are properly called for wrapped tests ... ok
  test_context (test_cases.TestNoseTestWrapper) ... ok
  test_result_proxy_used (test_cases.TestNoseTestWrapper)
  A result proxy is used to wrap the result for all tests ... ok
  test_short_description (test_cases.TestNoseTestWrapper) ... ok
  test_unrepresentable_shortDescription (test_cases.TestNoseTestWrapper) ... ok
  test_defaults (test_config.TestNoseConfig) ... ok
  test_ignore_files_default (test_config.TestNoseConfig)
  The default configuration should have several ignore file settings. ... ok
  test_ignore_files_multiple (test_config.TestNoseConfig)
  Multiple ignore-files flags should be appended together, overriding ... ok
  test_ignore_files_single (test_config.TestNoseConfig)
  A single ignore-files flag should override the default settings. ... ok
  test_multiple_include (test_config.TestNoseConfig) ... ok
  test_pickle_configured (test_config.TestNoseConfig) ... ok
  test_pickle_empty (test_config.TestNoseConfig) ... ok
  test_plugins (test_config.TestNoseConfig) ... ok
  test_progname_looks_like_option (test_config.TestNoseConfig) ... ok
  test_reset (test_config.TestNoseConfig) ... ok
  test_single_include (test_config.TestNoseConfig) ... ok
  test_testnames (test_config.TestNoseConfig) ... ok
  test_update (test_config.TestNoseConfig) ... ok
  test_where (test_config.TestNoseConfig) ... ok
  test_restore_stdout (test_core.TestAPI_run) ... ok
  test_getAllConfigFiles (test_core.TestProgramConfigs) ... ok
  test_getAllConfigFiles_ignore_configs (test_core.TestProgramConfigs) ... ok
  test_makeConfig (test_core.TestProgramConfigs) ... ok
  test_from_directory (test_core.TestUsage) ... ok
  test_from_zip (test_core.TestUsage) ... ok
  test_cover_plugin.TestCoveragePlugin.test_cover_packages_option ... ok
  test_api_present (test_deprecated_plugin.TestDeprecatedPlugin) ... ok
  test_can_be_disabled (test_deprecated_plugin.TestDeprecatedPlugin) ... ok
  test_deprecated_output (test_deprecated_plugin.TestDeprecatedPlugin) ... ok
  test_deprecated_output_verbose (test_deprecated_plugin.TestDeprecatedPlugin) 
... ok
  test_enabled_by_default (test_deprecated_plugin.TestDeprecatedPlugin) ... ok
  test_patched_result_handles_deprecated 
(test_deprecated_plugin.TestDeprecatedPlugin) ... ok
  test_patches_only_when_needed (test_deprecated_plugin.TestDeprecatedPlugin) 
... ok
  test_prepare_patches_result (test_deprecated_plugin.TestDeprecatedPlugin) ... 
ok
  test_err_doctests_raises_exception 
(test_doctest_error_handling.TestDoctestErrorHandling) ... ok
  test_no_doctests_in_file 
(test_doctest_error_handling.TestDoctestErrorHandling) ... ok
  test_no_name (test_doctest_no_name.TestDoctestErrorHandling) ... ok
  test_default_id_file_is_in_working_dir (test_id_plugin.TestTestIdPlugin) ... 
ok
  test_add_paths (test_importer.TestImporter) ... ok
  test_import (test_importer.TestImporter) ... ok
  test_module_init_prefix (test_importer.TestImporter) ... ok
  test_module_no_file (test_importer.TestImporter) ... ok
  test_bug_95 (test_inspector.TestExpander)
  Test that inspector can handle multi-line docstrings ... ok
  test_get_tb_source_func (test_inspector.TestExpander) ... ok
  test_get_tb_source_simple (test_inspector.TestExpander) ... ok
  test_inspect_traceback_continued (test_inspector.TestExpander) ... ok
  test_pick_tb_lines (test_inspector.TestExpander) ... ok
  test_simple_inspect_frame (test_inspector.TestExpa

Bug#801247: pinentry-gnome3: No PIN dialog

[Tim Small]

Package: pinentry-gnome3
Followup-For: Bug #801247

In my case, it looks like:

gpg-agent is started, and inherits the DBUS_SESSION_BUS_ADDRESS env
varible.  The gpg-agent persists across login sessions, so that when it
starts the gnome3 pinentry the dbus session doesn't correspond with the
current desktop session.

The practical result of this is that when I log to X first, it works,
but if I subsequently logout of my X session and then login again, I see
this bug.

People who start gpg-agent (or their X server) in different ways are
likely to see this problem without session restarts I suppose.

To confirm, I get different results from:

grep -z -i dbus  < /proc/`pidof gpg-agent`/environ

vs. 

grep -z -i dbus  < /proc/$$/environ

The gpg-agent manual page documents the use of:

gpg-connect-agent updatestartuptty /bye

to change the TTY and/or X display used for pin entry prompts.

I suppose the fix would involve either pinentry-gnome3 getting the
dbus session from the X session in some way (if that's possible),
or extending the functionality of "updatestartuptty" to also update dbus
session used by gpg-agent when starting the pinentry command.

Cheers,

Tim.

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

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