Processed: closing 873198

[Debian Bug Tracking System]

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

> # Slow mail, quick upload…
> close 873198 1.7.0really1.6.1-1
Bug #873198 [php-doctrine-cache] php-doctrine-cache should not (silently) 
depend on php 7.1
There is no source info for the package 'php-doctrine-cache' at version 
'1.7.0really1.6.1-1' with architecture ''
Unable to make a source version for version '1.7.0really1.6.1-1'
Marked as fixed in versions 1.7.0really1.6.1-1.
Bug #873198 [php-doctrine-cache] php-doctrine-cache should not (silently) 
depend on php 7.1
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: Re: Bug#873198: php-doctrine-cache-bundle FTBFS: test failures

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 php-doctrine-cache
Bug #873198 {Done: David Prévot } 
[src:php-doctrine-cache-bundle] php-doctrine-cache-bundle FTBFS: test failures
Bug reassigned from package 'src:php-doctrine-cache-bundle' to 
'php-doctrine-cache'.
No longer marked as found in versions php-doctrine-cache-bundle/1.3.0-4.
No longer marked as fixed in versions php-doctrine-cache/1.7.0really1.6.1-1.
> found -1 1.7.0-1
Bug #873198 {Done: David Prévot } [php-doctrine-cache] 
php-doctrine-cache-bundle FTBFS: test failures
Marked as found in versions php-doctrine-cache/1.7.0-1 and reopened.
> affects -1 php-doctrine-cache-bundle
Bug #873198 [php-doctrine-cache] php-doctrine-cache-bundle FTBFS: test failures
Added indication that 873198 affects php-doctrine-cache-bundle
> retitle -1 php-doctrine-cache should not (silently) depend on php 7.1
Bug #873198 [php-doctrine-cache] php-doctrine-cache-bundle FTBFS: test failures
Changed Bug title to 'php-doctrine-cache should not (silently) depend on php 
7.1' from 'php-doctrine-cache-bundle FTBFS: test failures'.

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

Bug#873198: php-doctrine-cache-bundle FTBFS: test failures

[David Prévot]

Control: reassign -1 php-doctrine-cache
Control: found -1 1.7.0-1
Control: affects -1 php-doctrine-cache-bundle
Control: retitle -1 php-doctrine-cache should not (silently) depend on php 7.1

Thank you Adrian for filling this issue.

On Fri, Aug 25, 2017 at 04:13:47PM +0300, Adrian Bunk wrote:
> Source: php-doctrine-cache-bundle
[…]
> Some recent change in unstable makes php-doctrine-cache-bundle FTBFS:
[…]
> There were 2 errors:
> 
> 1) 
> Doctrine\Bundle\DoctrineCacheBundle\Tests\Functional\PhpFileCacheTest::testCacheDriver
> ParseError: syntax error, unexpected '?'

Right. The latest php-doctrine-cache version in unstable depends on
php 7.1, and the default version in unstable is still php 7.0 (and there
is no proper way to depend on the more recent php7.1 package available
in unstable). I’ll fix this issue by uploading back the 1.6.1 version of
php-doctrine-cache to unstable.

Regards

David


signature.asc
Description: PGP signature

Bug#873198: marked as done (php-doctrine-cache-bundle FTBFS: test failures)

[Debian Bug Tracking System]

Your message dated Tue, 29 Aug 2017 05:19:35 +
with message-id 
and subject line Bug#873198: fixed in php-doctrine-cache 1.7.0really1.6.1-1
has caused the Debian Bug report #873198,
regarding php-doctrine-cache-bundle FTBFS: test failures
to be marked as done.

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

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


-- 
873198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873198
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-doctrine-cache-bundle
Version: 1.3.0-4
Severity: serious
Tags: buster sid

Some recent change in unstable makes php-doctrine-cache-bundle FTBFS:

https://tests.reproducible-builds.org/debian/history/php-doctrine-cache-bundle.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/php-doctrine-cache-bundle.html

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/php-doctrine-cache-bundle-1.3.0'
phpunit --exclude-group Predis
PHPUnit 5.4.6 by Sebastian Bergmann and contributors.

..WW.ESE. 57 / 57 (100%)

Time: 432 ms, Memory: 14.00MB

There were 2 errors:

1) 
Doctrine\Bundle\DoctrineCacheBundle\Tests\Functional\PhpFileCacheTest::testCacheDriver
ParseError: syntax error, unexpected '?'

/usr/share/php/Doctrine/Common/Cache/PhpFileCache.php:114
/usr/share/php/Symfony/Component/DependencyInjection/ContainerBuilder.php:929
/usr/share/php/Symfony/Component/DependencyInjection/ContainerBuilder.php:475
/build/1st/php-doctrine-cache-bundle-1.3.0/Tests/Functional/PhpFileCacheTest.php:35
/build/1st/php-doctrine-cache-bundle-1.3.0/Tests/Functional/BaseCacheTest.php:37

2) 
Doctrine\Bundle\DoctrineCacheBundle\Tests\Functional\Sqlite3CacheTest::testCacheDriver
ParseError: syntax error, unexpected '?'

/usr/share/php/Doctrine/Common/Cache/SQLite3Cache.php:166
/build/1st/php-doctrine-cache-bundle-1.3.0/Tests/Functional/Sqlite3CacheTest.php:40

--

There were 6 warnings:

1) 
Doctrine\Bundle\DoctrineCacheBundle\Tests\Functional\Command\ContainsCommandTest::testContainsFalse
PHPUnit_Framework_TestCase::getMock() is deprecated, use 
PHPUnit_Framework_TestCase::createMock() or 
PHPUnit_Framework_TestCase::getMockBuilder() instead

2) 
Doctrine\Bundle\DoctrineCacheBundle\Tests\Functional\Command\ContainsCommandTest::testContainsTrue
PHPUnit_Framework_TestCase::getMock() is deprecated, use 
PHPUnit_Framework_TestCase::createMock() or 
PHPUnit_Framework_TestCase::getMockBuilder() instead

3) 
Doctrine\Bundle\DoctrineCacheBundle\Tests\Functional\Command\DeleteCommandTest::testDeleteSuccess
PHPUnit_Framework_TestCase::getMock() is deprecated, use 
PHPUnit_Framework_TestCase::createMock() or 
PHPUnit_Framework_TestCase::getMockBuilder() instead

4) 
Doctrine\Bundle\DoctrineCacheBundle\Tests\Functional\Command\DeleteCommandTest::testDeleteAll
PHPUnit_Framework_TestCase::getMock() is deprecated, use 
PHPUnit_Framework_TestCase::createMock() or 
PHPUnit_Framework_TestCase::getMockBuilder() instead

5) 
Doctrine\Bundle\DoctrineCacheBundle\Tests\Functional\Command\FlushCommandTest::testFlush
PHPUnit_Framework_TestCase::getMock() is deprecated, use 
PHPUnit_Framework_TestCase::createMock() or 
PHPUnit_Framework_TestCase::getMockBuilder() instead

6) 
Doctrine\Bundle\DoctrineCacheBundle\Tests\Functional\Command\StatsCommandTest::testStats
PHPUnit_Framework_TestCase::getMock() is deprecated, use 
PHPUnit_Framework_TestCase::createMock() or 
PHPUnit_Framework_TestCase::getMockBuilder() instead

ERRORS!
Tests: 57, Assertions: 473, Errors: 2, Warnings: 6, Skipped: 5.
debian/rules:21: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 2
--- End Message ---
--- Begin Message ---
Source: php-doctrine-cache
Source-Version: 1.7.0really1.6.1-1

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

Debian distribution maintenance software
pp.
David Prévot  (supplier of updated php-doctrine-cache 
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, 28 Aug 2017 18:58:33 -1000
Source: php-doctr

Bug#871914: marked as done (golang-gogoprotobuf FTBFS on ppc64el: test failures)

[Debian Bug Tracking System]

Your message dated Tue, 29 Aug 2017 05:04:16 +
with message-id 
and subject line Bug#871914: fixed in golang-gogoprotobuf 0.4-1
has caused the Debian Bug report #871914,
regarding golang-gogoprotobuf FTBFS on ppc64el: test failures
to be marked as done.

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

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


-- 
871914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871914
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-gogoprotobuf
Version: 0.3+git20170120.144.265e960d-2
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=golang-gogoprotobuf&arch=ppc64el&ver=0.3%2Bgit20170120.144.265e960d-2&stamp=1502281675&raw=0

...
=== RUN   TestTimerProto
--- FAIL: TestTimerProto (0.00s)
thetestpb_test.go:4083: seed = 1502281594466825401, err = proto: 
illegal wireType 6
=== RUN   TestTimerMarshalTo
--- FAIL: TestTimerMarshalTo (0.00s)
thetestpb_test.go:4122: seed = 1502281594466915440, err = proto: Timer: 
wiretype end group for non-group
=== RUN   TestMyExtendableProto
--- PASS: TestMyExtendableProto (0.00s)
=== RUN   TestMyExtendableMarshalTo
--- PASS: TestMyExtendableMarshalTo (0.00s)
=== RUN   TestOtherExtenableProto
--- PASS: TestOtherExtenableProto (0.00s)
=== RUN   TestOtherExtenableMarshalTo
--- PASS: TestOtherExtenableMarshalTo (0.00s)
=== RUN   TestNestedDefinitionProto
--- FAIL: TestNestedDefinitionProto (0.00s)
thetestpb_test.go:4389: seed = 1502281594467379175, err = proto: 
NestedMessage: wiretype end group for non-group
=== RUN   TestNestedDefinitionMarshalTo
--- FAIL: TestNestedDefinitionMarshalTo (0.00s)
thetestpb_test.go:4428: seed = 1502281594467485880, err = proto: 
NestedMessage: wiretype end group for non-group
=== RUN   TestNestedDefinition_NestedMessageProto
--- FAIL: TestNestedDefinition_NestedMessageProto (0.00s)
thetestpb_test.go:4491: seed = 1502281594467578713, err = proto: 
NestedMessage: wiretype end group for non-group
=== RUN   TestNestedDefinition_NestedMessageMarshalTo
--- FAIL: TestNestedDefinition_NestedMessageMarshalTo (0.00s)
thetestpb_test.go:4530: seed = 1502281594467678453, err = proto: 
illegal wireType 6
=== RUN   TestNestedDefinition_NestedMessage_NestedNestedMsgProto
--- PASS: TestNestedDefinition_NestedMessage_NestedNestedMsgProto (0.00s)
=== RUN   TestNestedDefinition_NestedMessage_NestedNestedMsgMarshalTo
--- PASS: TestNestedDefinition_NestedMessage_NestedNestedMsgMarshalTo (0.00s)
=== RUN   TestNestedScopeProto
--- FAIL: TestNestedScopeProto (0.00s)
thetestpb_test.go:4695: seed = 1502281594467939400, err = proto: 
illegal wireType 7
=== RUN   TestNestedScopeMarshalTo
--- FAIL: TestNestedScopeMarshalTo (0.00s)
thetestpb_test.go:4734: seed = 1502281594468032872, err = proto: 
illegal wireType 7
...
--- End Message ---
--- Begin Message ---
Source: golang-gogoprotobuf
Source-Version: 0.4-1

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

Debian distribution maintenance software
pp.
Martín Ferrari  (supplier of updated golang-gogoprotobuf 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 29 Aug 2017 04:26:42 +
Source: golang-gogoprotobuf
Binary: golang-gogoprotobuf-dev golang-github-gogo-protobuf-dev gogoprotobuf
Architecture: source
Version: 0.4-1
Distribution: unstable
Urgency: high
Maintainer: pkg-go 
Changed-By: Martín Ferrari 
Description:
 gogoprotobuf - alternative protocol buffer support for Golang - utilities
 golang-github-gogo-protobuf-dev - alternative protocol buffer support for 
Golang - sources
 golang-gogoprotobuf-dev - transitional package -- safe to remove
Closes: 871914 871915
Changes:
 golang-gogoprotobuf (0.4-1) unstable; urgency=high
 .
   * Add myself to Uploaders.
   * New upstream release. Closes: 871915.
   * Force usage of go 1.7 on ppc64el. Closes: 871914.
   * Lintian now fails to recognise the go binaries: add overrides.
   * debian/control: Update Standards-Version (no changes).
   * debian/control: Mark package as autopkgtest-able.
   * debian/rules: Rep

Processed: notfixed 869260 in 1.12.1+dfsg-19+deb8ku3, fixed 869260 in 1.12.1+dfsg-19+deb8u3 ...

[Debian Bug Tracking System]

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

> notfixed 869260 1.12.1+dfsg-19+deb8ku3
Bug #869260 {Done: Sam Hartman } [src:krb5] CVE-2017-11368
The source 'krb5' and version '1.12.1+dfsg-19+deb8ku3' do not appear to match 
any binary packages
No longer marked as fixed in versions krb5/1.12.1+dfsg-19+deb8ku3.
> fixed 869260 1.12.1+dfsg-19+deb8u3
Bug #869260 {Done: Sam Hartman } [src:krb5] CVE-2017-11368
The source 'krb5' and version '1.12.1+dfsg-19+deb8u3' do not appear to match 
any binary packages
Marked as fixed in versions krb5/1.12.1+dfsg-19+deb8u3.
> notfixed 832572 1.12.1+dfsg-19+deb8ku3
Bug #832572 {Done: Sam Hartman } [src:krb5] krb5: 
CVE-2016-3120: Fix S4U2Self KDC crash when anon is restricted
The source 'krb5' and version '1.12.1+dfsg-19+deb8ku3' do not appear to match 
any binary packages
No longer marked as fixed in versions krb5/1.12.1+dfsg-19+deb8ku3.
> fixed 832572 1.12.1+dfsg-19+deb8u3
Bug #832572 {Done: Sam Hartman } [src:krb5] krb5: 
CVE-2016-3120: Fix S4U2Self KDC crash when anon is restricted
The source 'krb5' and version '1.12.1+dfsg-19+deb8u3' do not appear to match 
any binary packages
Marked as fixed in versions krb5/1.12.1+dfsg-19+deb8u3.
> notfixed 783557 1.12.1+dfsg-19+deb8ku3
Bug #783557 {Done: Sam Hartman } [src:krb5] CVE-2015-2694 
in krb5-otp, krb5-pkinit
The source 'krb5' and version '1.12.1+dfsg-19+deb8ku3' do not appear to match 
any binary packages
No longer marked as fixed in versions krb5/1.12.1+dfsg-19+deb8ku3.
> fixed 783557 1.12.1+dfsg-19+deb8u3
Bug #783557 {Done: Sam Hartman } [src:krb5] CVE-2015-2694 
in krb5-otp, krb5-pkinit
The source 'krb5' and version '1.12.1+dfsg-19+deb8u3' do not appear to match 
any binary packages
Marked as fixed in versions krb5/1.12.1+dfsg-19+deb8u3.
> thanks
Stopping processing here.

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

Bug#862133: marked as done (src:gnuradio: FTBFS with cppunit 1.14 (no C++11 support, required by cppunit))

[Debian Bug Tracking System]

Your message dated Tue, 29 Aug 2017 05:00:22 +
with message-id 
and subject line Bug#862133: fixed in gnuradio 3.7.11-1
has caused the Debian Bug report #862133,
regarding src:gnuradio: FTBFS with cppunit 1.14 (no C++11 support, required by 
cppunit)
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.)


-- 
862133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862133
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gnuradio
Version: 3.7.10.1-2
Severity: normal

Dear Maintainer,

[ cppunit 0.14 is not in Debian yet, see #861718. Thus normal for now ]

On a rebuild test using ratt I noticed your package doesn't build with
cppunit 0.14:

[...]
[ 21%] Building CXX object 
gnuradio-runtime/apps/CMakeFiles/gnuradio-config-info.dir/gnuradio-config-info.cc.o
cd /<>/obj-x86_64-linux-gnu/gnuradio-runtime/apps && /usr/bin/c++  
 -DALIGNED_MALLOC=0 -DENABLE_GR_LOG -DGR_PERFORMANCE_COUNTERS 
-DHAVE_ARPA_INET_H -DHAVE_BYTESWAP_H -DHAVE_COSF -DHAVE_GETPAGESIZE 
-DHAVE_GETTIMEOFDAY -DHAVE_LINUX_PPDEV_H -DHAVE_LOG4CPP -DHAVE_MALLOC_H 
-DHAVE_MMAP -DHAVE_NANOSLEEP -DHAVE_NETDB_H -DHAVE_NETINET_IN_H 
-DHAVE_POSIX_MEMALIGN -DHAVE_PTHREAD_SETSCHEDPARAM -DHAVE_PTHREAD_SIGMASK 
-DHAVE_SCHED_SETSCHEDULER -DHAVE_SELECT -DHAVE_SHM_OPEN -DHAVE_SIGACTION 
-DHAVE_SIGNAL_H -DHAVE_SINCOS -DHAVE_SINCOSF -DHAVE_SINF -DHAVE_SNPRINTF 
-DHAVE_SYSCONF -DHAVE_SYS_IPC_H -DHAVE_SYS_MMAN_H -DHAVE_SYS_SELECT_H 
-DHAVE_SYS_SHM_H -DHAVE_SYS_SOCKET_H -DHAVE_SYS_TIME_H -DHAVE_SYS_TYPES_H 
-DHAVE_UNISTD_H -DHAVE_VALLOC -I/<>/obj-x86_64-linux-gnu 
-I/<>/gnuradio-runtime/include 
-I/<>/obj-x86_64-linux-gnu/gnuradio-runtime/include  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++98 
-fvisibility=hidden -Wsign-compare -Wall -Wno-uninitialized   -o 
CMakeFiles/gnuradio-config-info.dir/gnuradio-config-info.cc.o -c 
/<>/gnuradio-runtime/apps/gnuradio-config-info.cc
cd /<>/obj-x86_64-linux-gnu/gnuradio-runtime/lib && /usr/bin/c++   
-DALIGNED_MALLOC=0 -DENABLE_GR_LOG -DGR_CTRLPORT -DGR_PERFORMANCE_COUNTERS 
-DHAVE_ARPA_INET_H -DHAVE_BYTESWAP_H -DHAVE_COSF -DHAVE_GETPAGESIZE 
-DHAVE_GETTIMEOFDAY -DHAVE_LINUX_PPDEV_H -DHAVE_LOG4CPP -DHAVE_MALLOC_H 
-DHAVE_MMAP -DHAVE_NANOSLEEP -DHAVE_NETDB_H -DHAVE_NETINET_IN_H 
-DHAVE_POSIX_MEMALIGN -DHAVE_PTHREAD_SETSCHEDPARAM -DHAVE_PTHREAD_SIGMASK 
-DHAVE_SCHED_SETSCHEDULER -DHAVE_SELECT -DHAVE_SHM_OPEN -DHAVE_SIGACTION 
-DHAVE_SIGNAL_H -DHAVE_SINCOS -DHAVE_SINCOSF -DHAVE_SINF -DHAVE_SNPRINTF 
-DHAVE_SYSCONF -DHAVE_SYS_IPC_H -DHAVE_SYS_MMAN_H -DHAVE_SYS_RESOURCE_H 
-DHAVE_SYS_SELECT_H -DHAVE_SYS_SHM_H -DHAVE_SYS_SOCKET_H -DHAVE_SYS_TIME_H 
-DHAVE_SYS_TYPES_H -DHAVE_UNISTD_H -DHAVE_VALLOC -DTRY_SHM_VMCIRCBUF 
-Dtest_gnuradio_runtime_EXPORTS -I/<>/gnuradio-runtime/lib/math 
-I/<>/obj-x86_64-linux-gnu 
-I/<>/gnuradio-runtime/include 
-I/<>/obj-x86_64-linux-gnu/gnuradio-runtime/include 
-I/<>/gnuradio-runtime/lib 
-I/<>/obj-x86_64-linux-gnu/gnuradio-runtime/lib/../include 
-I/<>/gnuradio-runtime/lib/controlport 
-I/<>/obj-x86_64-linux-gnu/gnuradio-runtime/lib/controlport  -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++98 
-fvisibility=hidden -Wsign-compare -Wall -Wno-uninitialized -fPIC   -o 
CMakeFiles/test-gnuradio-runtime.dir/math/qa_fxpt.cc.o -c 
/<>/gnuradio-runtime/lib/math/qa_fxpt.cc
In file included from /usr/include/c++/6/type_traits:35:0,
 from /usr/include/cppunit/tools/StringHelper.h:7,
 from /usr/include/cppunit/TestAssert.h:8,
 from /usr/include/cppunit/TestCase.h:6,
 from /usr/include/cppunit/TestCaller.h:5,
 from /usr/include/cppunit/extensions/HelperMacros.h:9,
 from 
/<>/gnuradio-runtime/lib/pmt/qa_pmt_prims.h:27,
 from /<>/gnuradio-runtime/lib/pmt/qa_pmt.cc:28:
/usr/include/c++/6/bits/c++0x_warning.h:32:2: error: #error This file requires 
compiler and library support for the ISO C++ 2011 standard. This support must 
be enabled with the -std=c++11 or -std=gnu++11 compiler options.
 #error This file requires compiler and library support \
  ^
In file included from /usr/include/c++/6/type_traits:35:0,
 from /usr/include/cppunit/tools/StringHelper.h:7,
 from /usr/include/cppunit/TestAssert.h:8,
 from /usr/include/cppunit/TestCase.h:6,
 from /usr/include/cppunit/TestCaller.h:5,
 from /usr/include/cppunit/extensions/HelperMac

Bug#853654: marked as done (scim: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Tue, 29 Aug 2017 04:21:51 +
with message-id 
and subject line Bug#853654: fixed in scim 1.4.18-1
has caused the Debian Bug report #853654,
regarding scim: ftbfs with GCC-7
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.)


-- 
853654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853654
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:scim
Version: 1.4.17-1
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/scim_1.4.17-1_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
/bin/bash ../../../libtool  --tag=CC   --mode=link gcc -pthread 
-I/usr/include/clutter-1.0 -I/usr/include/cogl -I/usr/include/atk-1.0 
-I/usr/include/cogl -I/usr/include/libdrm -I/usr/include/json-glib-1.0 
-I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/cairo 
-I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
-I/usr/include/clutter-imcontext-0.1 -I/usr/include/clutter-1.0 
-I/usr/include/cogl -I/usr/include/atk-1.0 -I/usr/include/cogl 
-I/usr/include/libdrm -I/usr/include/json-glib-1.0 -I/usr/include/gtk-3.0 
-I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 
-I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libpng16 -I/usr/include/cairo -I/usr/include/pixma
 n-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -rpath 
/usr/lib/x86_64-linux-gnu/clutter-imcontext/immodules -avoid-version 
-no-undefined -module -lclutter-1.0 -lcogl-path -latk-1.0 -lcogl-pango -lcogl 
-lgmodule-2.0 -pthread -lwayland-egl -lgbm -ldrm -lEGL -lXrandr -ljson-glib-1.0 
-lgio-2.0 -lgdk-3 -lpangocairo-1.0 -lpango-1.0 -lgdk_pixbuf-2.0 -lcairo-gobject 
-lcairo -lgobject-2.0 -lglib-2.0 -lwayland-cursor -lwayland-client -lxkbcommon 
-lwayland-server -lX11 -lXext -lXdamage -lXfixes -lXcomposite -lXi 
-lclutter-imcontext-0.1 -lclutter-1.0 -lcogl-path -latk-1.0 -lcogl-pango -lcogl 
-lgmodule-2.0 -pthread -lwayland-egl -lgbm -ldrm -lEGL -lXrandr -ljson-glib-1.0 
-lgio-2.0 -lgdk-3 -lpangocairo-1.0 -lpango-1.0 -lgdk_pixbuf-2.0 -lcairo-gobject 
-lcairo -lgobject-2.0 -lglib-2.0 -lwayland-cursor -lwayland-client -lxkb
 common -lwayland-server -lX11 -lXext -lXdamage -lXfixes -lXcomposite -lXi 
-Wl,-z,relro -o im-scim.la -rpath 
/usr/lib/x86_64-linux-gnu/clutter-imcontext/immodules 
im_scim_la-im-scim-bridge-clutter.lo im_scim_la-scim-bridge-client-clutter.lo 
im_scim_la-scim-bridge-client-imcontext-clutter.lo 
im_scim_la-scim-bridge-client-key-event-utility-clutter.lo 
../../../extras/immodules/common/libscimbridgecommon.la 
../../../extras/immodules/client-common/libscimbridgeclientcommon.la 
libtool: link: gcc -shared  -fPIC -DPIC  
.libs/im_scim_la-im-scim-bridge-clutter.o 
.libs/im_scim_la-scim-bridge-client-clutter.o 
.libs/im_scim_la-scim-bridge-client-imcontext-clutter.o 
.libs/im_scim_la-scim-bridge-client-key-event-utility-clutter.o  
-Wl,--whole-archive 
../../../extras/immodules/common/.libs/libscimbridgecommon.a 
../../../extras/immodules/client-common/.libs/libscimbridgeclientcommon.a 
-Wl,--no-whole-archi

Bug#859510: marked as pending

[Youhei SASAKI]

tag 859510 pending
thanks

Hello,

Bug #859510 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:


https://anonscm.debian.org/cgit/pkg-ruby-extras/ruby-unf-ext.git/commit/?id=7a0777d

---
commit 7a0777dcdce0e7a5328e2b5c8aecb355e0b796d5
Author: Youhei SASAKI 
Date:   Mon Aug 28 15:47:54 2017 +0900

Update debian/changelog

Signed-off-by: Youhei SASAKI 

diff --git a/debian/changelog b/debian/changelog
index 7f75cbd..c6293db 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,14 @@
+ruby-unf-ext (0.0.7.4-1) unstable; urgency=medium
+
+  * New upstream version 0.0.7.4
+  * Refresh patches
+  * Bump Standard Version: 4.0.0
+  * Bump debhelper >= 10
+  * Include scripts and data in order to generate
+"ext/unf_ext/unf/table.hh". (Closes: #859510)
+
+ -- Youhei SASAKI   Mon, 28 Aug 2017 15:45:04 +0900
+
 ruby-unf-ext (0.0.7.2-3) unstable; urgency=medium
 
   * Team upload

Processed: Bug#859510 marked as pending

[Debian Bug Tracking System]

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

> tag 859510 pending
Bug #859510 {Done: Youhei SASAKI } [src:ruby-unf-ext] 
Generated header file without means to regenerate
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#817643: marked as done (qingy: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Tue, 29 Aug 2017 01:06:15 +
with message-id 
and subject line Bug#873533: Removed package(s) from unstable
has caused the Debian Bug report #817643,
regarding qingy: 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.)


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

Hi,

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

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

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

Thanks,
~Niels

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

Dear submitter,

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

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

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

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

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

Bug#851099: marked as done ("auto-apt update" tries to fetch wrong URL)

[Debian Bug Tracking System]

Your message dated Tue, 29 Aug 2017 01:04:54 +
with message-id 
and subject line Bug#873473: Removed package(s) from unstable
has caused the Debian Bug report #851099,
regarding "auto-apt update" tries to fetch wrong URL
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.)


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

Package: auto-apt
Version: 0.3.24

I believe that the first thing I must do after installing auto-apt is
"auto-apt update", right?

# auto-apt update
Downloading http://ftp.debian.org/debian/dists/stretch 
Contents-arm64.gz ...

2017-01-11 23:47:13 ERROR 404: Not Found.


My /etc/apt/sources.list contains:
deb http://ftp.debian.org/debian stretch main contrib non-free


It seems that auto-apt invokes wget to fetch 
/debian/dists/stretch/Contents-arm64.gz
rather than /debian/dists/stretch/main/Contents-arm64.gz .
--- End Message ---
--- Begin Message ---
Version: 0.3.24+rm

Dear submitter,

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

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

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

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

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

Bug#873539: monit 1:5.23.0-3 won't install - "epoch in version is empty"

[Sergey B Kirpichev]

On Tue, Aug 29, 2017 at 01:24:27AM +0200, Vincent Lefevre wrote:
> > dpkg-maintscript-helper: error: dpkg: error: version '"1:5.15-1~"' has bad 
> > syntax: epoch in version is empty

Looks like regression in dpkg-maintscript-helper: quotation marks were passed 
to dpkg --validate-version.

C.f.
# dpkg --validate-version -- "1:5.15-1"
# dpkg --validate-version -- "1:5.15-1~"
vs
# dpkg --validate-version -- '"1:5.15-1~"'
dpkg: error: version '"1:5.15-1~"' has bad syntax: epoch in version is empty

Probably, this could be solved on the monit side by changing
mv_conffile /etc/monit/monitrc.d/acpid /etc/monit/conf-available/acpid 
"1:5.15-1~"
to
mv_conffile /etc/monit/monitrc.d/acpid /etc/monit/conf-available/acpid 1:5.15-1~

Bug#789934: marked as done (libanthyinput-dev: fails to upgrade from 'sid' - trying to overwrite /usr/lib/x86_64-linux-gnu/libanthyinput.a)

[Debian Bug Tracking System]

Your message dated Tue, 29 Aug 2017 00:49:43 +
with message-id 
and subject line Bug#789934: fixed in anthy 1:0.3-4
has caused the Debian Bug report #789934,
regarding libanthyinput-dev: fails to upgrade from 'sid' - trying to overwrite 
/usr/lib/x86_64-linux-gnu/libanthyinput.a
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.)


-- 
789934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789934
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libanthyinput-dev
Version: 1:0.3-1
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 libanthyinput0:amd64.
  Preparing to unpack .../libanthyinput0_1%3a0.3-1_amd64.deb ...
  Unpacking libanthyinput0:amd64 (1:0.3-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libanthyinput0_1%3a0.3-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libanthyinput.so.0.0.0', 
which is also in package libanthy0:amd64 9100h-25
  Selecting previously unselected package libanthyinput-dev:amd64.
  Preparing to unpack .../libanthyinput-dev_1%3a0.3-1_amd64.deb ...
  Unpacking libanthyinput-dev:amd64 (1:0.3-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libanthyinput-dev_1%3a0.3-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libanthyinput.a', which is 
also in package libanthy-dev:amd64 9100h-25
  Errors were encountered while processing:
   /var/cache/apt/archives/libanthyinput0_1%3a0.3-1_amd64.deb
   /var/cache/apt/archives/libanthyinput-dev_1%3a0.3-1_amd64.deb


cheers,

Andreas


libanthy-dev=9100h-25_libanthyinput-dev=1%0.3-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: anthy
Source-Version: 1:0.3-4

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

Debian distribution maintenance software
pp.
NIIBE Yutaka  (supplier of updated anthy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 29 Aug 2017 09:12:08 +0900
Source: anthy
Binary: anthy anthy-common anthy-el libanthy1 libanthy-dev libanthyinput0 
libanthyinput-dev
Architecture: source all amd64
Version: 1:0.3-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Anthy Team 
Changed-By: NIIBE Yutaka 
Description:
 anthy  - Japanese kana-kanji conversion - utilities
 anthy-common - Japanese kana-kanji conversion - dictionary
 anthy-el   - Japanese kana-kanji conversion - elisp frontend
 libanthy-dev - Japanese kana-kanji conversion - runtime library
 libanthy1  - Japanese kana-kanji conversion - runtime library
 libanthyinput-dev - Japanese kana-kanji conversion - runtime library for input
 libanthyinput0 - Japanese kana-kanji conversion - runtime library for input
Closes: 789927 789934
Changes:
 anthy (1:0.3-4) unstable; urgency=medium
 .
   * debian/control (Breaks, Replaces): Fix for libanthyinput0
 (Closes: #789927).
   * debian/control (Breaks, Replaces): Add for libantyinput0-dev
 (Closes: #789934).
Checksums-Sha1:
 103802357214cd4540ecbe65237a31eeb039002f 2000 anthy_0.3-4.dsc
 08394354f18d2dcfe7fce5a483cb1400d8d32bba 11972 anthy_0.3-4.debian.tar.xz
 d4649fce958ebbf4d12f935e22a1fbf3dfd68b7e 5563318 anthy-common_0.3-4_all.deb
 f82d84f2b8967ef81eef6cdb1b26bc73d1907a50 32632 anthy-dbgsym_0.3-4_amd64.deb
 ee4ea80f4866479e02876e3fc75271e5e02823a9 30546 anthy-el_0.3-4_all.deb
 5c0fc253251504157116f5f980bedc993e32796c 7988 anthy_0.3-4_amd64.buildinfo
 448af3373f6da868579de6ca1d849ddf320ff165 25326 anthy_0.3-4_amd64.deb
 e062a0e374012b5e444aeb9ceb7dd9263ca0c048 115832 libanthy-dev_0.3-4_amd64.deb
 d9d1f5959b44f6a58437c19c3355

Bug#789927: marked as done (libanthyinput0: fails to upgrade from 'sid' - trying to overwrite /usr/lib/x86_64-linux-gnu/libanthyinput.so.0.0.0')

[Debian Bug Tracking System]

Your message dated Tue, 29 Aug 2017 00:49:43 +
with message-id 
and subject line Bug#789927: fixed in anthy 1:0.3-4
has caused the Debian Bug report #789927,
regarding libanthyinput0: fails to upgrade from 'sid' - trying to overwrite 
/usr/lib/x86_64-linux-gnu/libanthyinput.so.0.0.0'
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.)


-- 
789927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789927
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libanthyinput0
Version: 1:0.3-1
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 libanthyinput0:amd64.
  Preparing to unpack .../libanthyinput0_1%3a0.3-1_amd64.deb ...
  Unpacking libanthyinput0:amd64 (1:0.3-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libanthyinput0_1%3a0.3-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libanthyinput.so.0.0.0', 
which is also in package libanthy0:amd64 9100h-25
  Preparing to unpack .../anthy_1%3a0.3-1_amd64.deb ...
  Unpacking anthy (1:0.3-1) over (9100h-25) ...
  dpkg: warning: unable to delete old directory '/var/lib/anthy': Directory not 
empty
  Errors were encountered while processing:
   /var/cache/apt/archives/libanthyinput0_1%3a0.3-1_amd64.deb


cheers,

Andreas


anthy_1:0.3-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: anthy
Source-Version: 1:0.3-4

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

Debian distribution maintenance software
pp.
NIIBE Yutaka  (supplier of updated anthy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 29 Aug 2017 09:12:08 +0900
Source: anthy
Binary: anthy anthy-common anthy-el libanthy1 libanthy-dev libanthyinput0 
libanthyinput-dev
Architecture: source all amd64
Version: 1:0.3-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Anthy Team 
Changed-By: NIIBE Yutaka 
Description:
 anthy  - Japanese kana-kanji conversion - utilities
 anthy-common - Japanese kana-kanji conversion - dictionary
 anthy-el   - Japanese kana-kanji conversion - elisp frontend
 libanthy-dev - Japanese kana-kanji conversion - runtime library
 libanthy1  - Japanese kana-kanji conversion - runtime library
 libanthyinput-dev - Japanese kana-kanji conversion - runtime library for input
 libanthyinput0 - Japanese kana-kanji conversion - runtime library for input
Closes: 789927 789934
Changes:
 anthy (1:0.3-4) unstable; urgency=medium
 .
   * debian/control (Breaks, Replaces): Fix for libanthyinput0
 (Closes: #789927).
   * debian/control (Breaks, Replaces): Add for libantyinput0-dev
 (Closes: #789934).
Checksums-Sha1:
 103802357214cd4540ecbe65237a31eeb039002f 2000 anthy_0.3-4.dsc
 08394354f18d2dcfe7fce5a483cb1400d8d32bba 11972 anthy_0.3-4.debian.tar.xz
 d4649fce958ebbf4d12f935e22a1fbf3dfd68b7e 5563318 anthy-common_0.3-4_all.deb
 f82d84f2b8967ef81eef6cdb1b26bc73d1907a50 32632 anthy-dbgsym_0.3-4_amd64.deb
 ee4ea80f4866479e02876e3fc75271e5e02823a9 30546 anthy-el_0.3-4_all.deb
 5c0fc253251504157116f5f980bedc993e32796c 7988 anthy_0.3-4_amd64.buildinfo
 448af3373f6da868579de6ca1d849ddf320ff165 25326 anthy_0.3-4_amd64.deb
 e062a0e374012b5e444aeb9ceb7dd9263ca0c048 115832 libanthy-dev_0.3-4_amd64.deb
 d9d1f5959b44f6a58437c19c3355bf0ac78f54c0 173096 
libanthy1-dbgsym_0.3-4_amd64.deb
 eacbad6204be504adfd3a0b058e603489068aeac 109072 libanthy1_0.3-4_amd64.deb
 bf9c94a8c2c01dc261468b4a70a47941216a79c0 29046 
libanthyinput-dev_0.3-4_amd64.deb
 471c30f7d1d560d660b82fd7a45e3a28a73ec754 30456 
libanthyinput0-dbgsym_0.3-4_amd64.deb
 d3d40ec49fb899a3a4a1f

Bug#873562: unicode-data: FTBFS, missing unicode-data_10.0.0-orig-emoji.tar.xz

[Jeremy Bicha]

Source: unicode-data
Version: 10.0.0-2
Severity: serious

unicode-data fails to build from source. There is this line in its debian/rules:

tar axpf ../../../unicode-data_10.0.0-orig-emoji.tar.xz

but that emoji tarball is not included in the source.

Thanks,
Jeremy Bicha

Processed: Re: Bug#873539: monit 1:5.23.0-3 won't install - "epoch in version is empty"

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 1:5.23.0-2
Bug #873539 [monit] monit 1:5.23.0-3 won't install - "epoch in version is empty"
No longer marked as found in versions monit/1:5.23.0-2.
> found -1 1:5.23.0-3
Bug #873539 [monit] monit 1:5.23.0-3 won't install - "epoch in version is empty"
Marked as found in versions monit/1:5.23.0-3.
> severity -1 serious
Bug #873539 [monit] monit 1:5.23.0-3 won't install - "epoch in version is empty"
Severity set to 'serious' from 'normal'

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

Bug#873165: marked as done (tdiary-style-gfm FTBFS: 24 examples, 1 failure)

[Debian Bug Tracking System]

Your message dated Mon, 28 Aug 2017 23:24:39 +
with message-id 
and subject line Bug#873165: fixed in tdiary-style-gfm 0.5.1-1
has caused the Debian Bug report #873165,
regarding tdiary-style-gfm FTBFS: 24 examples, 1 failure
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.)


-- 
873165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873165
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tdiary-style-gfm
Version: 0.4.1-1
Severity: serious

Some recent change in unstable makes tdiary-style-gfm FTBFS:

https://tests.reproducible-builds.org/debian/history/tdiary-style-gfm.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/tdiary-style-gfm.html

...
┌──┐
│ Run tests for ruby2.3 from debian/ruby-tests.rake│
└──┘

RUBYLIB=/build/1st/tdiary-style-gfm-0.4.1/debian/tdiary-style-gfm/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/tdiary-style-gfm/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
 ruby2.3 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation

TDiary::Style::GfmDiary
  #append
HTML
  should eq "\n<%=section_enter_proc( Time.at( 
1041346800 ) )%>\n<%= subtitle_proc( Ti...># comment in code 
block\n\n<%=section_leave_proc( Time.at( 1041346800 ) 
)%>\n\n"
CHTML
  should eq "<%=section_enter_proc( Time.at( 1041346800 ) )%>\n<%= 
subtitle_proc( Time.at( 1041346800 ), \"su...re># comment in code 
block\n\n<%=section_leave_proc( Time.at( 1041346800 ) )%>\n"
to_src
  should eq "# subTitle\nhonbun\n\n## subTitleH4\nhonbun\n\n```\n# comment 
in code block\n```\n\n"
  #replace
should eq "\n<%=section_enter_proc( Time.at( 
1041346800 ) )%>\n<%= subtitle_proc( 
Ti...4>replaceTitleH4\n\nreplace\n<%=section_leave_proc( Time.at( 
1041346800 ) )%>\n\n"
  autolink
should eq "\n<%=section_enter_proc( Time.at( 
1041346800 ) )%>\n<%= subtitle_proc( 
Ti...gle.com\">http://www.google.com\n<%=section_leave_proc( Time.at( 
1041346800 ) )%>\n\n"
  auto imagelink
should eq "\n<%=section_enter_proc( Time.at( 
1041346800 ) )%>\n<%= subtitle_proc( Ti...ogle.com/logo.jpg\" 
alt=\"google\">\n<%=section_leave_proc( Time.at( 1041346800 ) )%>\n\n"
  auto imagelink
should eq "\n<%=section_enter_proc( Time.at( 
1041346800 ) )%>\n<%= subtitle_proc( Ticom\" 
target=\"_blank\">Anchor\n<%=section_leave_proc( Time.at( 1041346800 ) 
)%>\n\n"
  url syntax with code blocks
should eq "\n<%=section_enter_proc( Time.at( 
1041346800 ) )%>\n<%= subtitle_proc( Ti...tp://example.com is 
example.com\n<%=section_leave_proc( Time.at( 1041346800 ) )%>\n\n"
  ignored url syntax with markdown anchor
should eq "\n<%=section_enter_proc( Time.at( 
1041346800 ) )%>\n<%= subtitle_proc( Ti...le.com\">example is 
example.com\n<%=section_leave_proc( Time.at( 1041346800 ) )%>\n\n"
  plugin syntax
should eq "\n<%=section_enter_proc( Time.at( 
1041346800 ) )%>\n<%= subtitle_proc( Ti...p>\n\n<%=plugin \"val\", 
'val'%>\n<%=section_leave_proc( Time.at( 1041346800 ) )%>\n\n"
  plugin syntax with url args
should eq "\n<%=section_enter_proc( Time.at( 
1041346800 ) )%>\n<%= subtitle_proc( 
Ti...ttps://www.example.com/bar.html\"%>\n<%=section_leave_proc( Time.at( 
1041346800 ) )%>\n\n"
  link to my plugin
should eq "\n<%=section_enter_proc( Time.at( 
1041346800 ) )%>\n<%= subtitle_proc( Ti...><%=my \"20120101p01\", \"Link\" 
%>\n<%=section_leave_proc( Time.at( 1041346800 ) )%>\n\n"
  code highlighting
should eq "\n<%=section_enter_proc( Time.at( 
1041346800 ) )%>\n<%= subtitle_proc( Ti...pan 
class=\"k\">end\n<%=section_leave_proc( Time.at( 1041346800 
) )%>\n\n"
  ignore emphasis
should eq "\n<%=section_enter_proc( Time.at( 
1041346800 ) )%>\n<%= subtitle_proc( Ti...a\n\n<%=isbn_left_image 
''%>\n<%=section_leave_proc( Time.at( 1041346800 ) )%>\n\n"
  twitter username
in plain context
  should eq "\n<%=section_enter_proc( Time.at( 
1041346800 ) )%>\n<%= subtitle_proc( Ti...ofollow\">a_matsuda is 
amatsuda\n<%=section_leave_proc( Time.at( 1041346800 ) )%>\n\n"
with 
  should eq "\n<%=section_enter_proc( Time.at( 
1041346800 ) )%>\n<%= subtitle_proc( Ti...\n\n@a_matsuda is 
amatsuda\n<%=section_leave_proc( Time.at( 1041346800 ) )%>\n\n"
with 
  should eq "\n<%=se

Processed: #873557 is an upstream bug

[Debian Bug Tracking System]

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

> tags 873557 upstream
Bug #873557 [src:mbedtls] mbedtls: possible authentication bypass
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#873557: mbedtls: possible authentication bypass

[James Cowgill]

Source: mbedtls
Version: 2.1.2-1
Severity: grave
Tags: security

Hi,

The following security advisory was published for mbedtls:
https://tls.mbed.org/tech-updates/security-advisories/mbedtls-security-advisory-2017-02

[Vulnerability]
If a malicious peer supplies an X.509 certificate chain that has more
than MBEDTLS_X509_MAX_INTERMEDIATE_CA intermediates (which by default is
8), it could bypass authentication of the certificates, when the
authentication mode was set to 'optional' eg.
MBEDTLS_SSL_VERIFY_OPTIONAL. The issue could be triggered remotely by
both the client and server sides.

If the authentication mode, which can be set by the function
mbedtls_ssl_conf_authmode(), was set to 'required' eg.
MBEDTLS_SSL_VERIFY_REQUIRED which is the default, authentication would
occur normally as intended.

[Impact]
Depending on the platform, an attack exploiting this vulnerability could
allow successful impersonation of the intended peer and permit
man-in-the-middle attacks.

The advisory states that only mbedtls >= 1.3.10 is affected, which means
that jessie's version of polarssl is not affected.

I think this is the commit which fixes this, but I have not checked yet:
https://github.com/ARMmbed/mbedtls/commit/31458a18788b0cf0b722acda9bb2f2fe13a3fb32

James



signature.asc
Description: OpenPGP digital signature

Bug#816808: marked as done ([gpsbabel] Qt4's WebKit removal)

[Debian Bug Tracking System]

Your message dated Mon, 28 Aug 2017 22:53:28 +
with message-id 
and subject line Bug#816808: fixed in gpsbabel 1.5.4-1
has caused the Debian Bug report #816808,
regarding [gpsbabel] Qt4's WebKit 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.)


-- 
816808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816808
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gpsbabel
Version: 1.5.2-1
User: debian-qt-...@lists.debian.org
Usertags: qt4webkit-removal

Hi! As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit
as announced in [announce].

[announce] 


Basically we are about to get the last Qt4 point release and upstream is
migrating from WebKit to Blink in the Qt5 series, so we won't have much 
upstreams
support for maintaining Qt4's WebKit (Qt5's WebKit is expected to stay supported
until Qt6).

In order to make this move, all packages directly or indirectly depending on
the Qt4's WebKit library have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5 
port of your application
- if there are no activities regarding porting, investigate whether there are 
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian 
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4. In
order to ease the transition time we have provided Wheezy backports for Qt5.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

If you have any questions, please reply to this mail and CC me.

On behalf of the Qt4 maintainers,

--
Dmitry Shachnev

signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: gpsbabel
Source-Version: 1.5.4-1

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

Debian distribution maintenance software
pp.
Bernd Zeimetz  (supplier of updated gpsbabel 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, 28 Aug 2017 23:53:53 +0200
Source: gpsbabel
Binary: gpsbabel gpsbabel-doc gpsbabel-gui
Architecture: source
Version: 1.5.4-1
Distribution: unstable
Urgency: medium
Maintainer: Bernd Zeimetz 
Changed-By: Bernd Zeimetz 
Description:
 gpsbabel   - GPS file conversion plus transfer to/from GPS units
 gpsbabel-doc - GPS file conversion plus transfer to/from GPS units
 gpsbabel-gui - GPS file conversion plus transfer to/from GPS units - GUI
Closes: 816808 872744
Changes:
 gpsbabel (1.5.4-1) unstable; urgency=medium
 .
   * [ee23f26] Merge branch 'upstream'
 - New upstream version.
 - Builds fine with gcc7.
 Thanks to Adrian Bunk (Closes: #872744)
   * [f340fb9] Refreshing patches.
   * [8100370] export QT_SELECT=qt5
   * [522c580] Build for/with QT5.
 Using as build-deps:
 qtbase5-dev
 qtwebengine5-dev
 qttools5-dev-tools
 Thanks to Dmitry Shachnev (Closes: #816808)
   * [7d38162] Depend on dh 10 for comapt level 10.
   * [ada8fa9] Fix building with recent QT5 versions.
   * [d627435] Use qmake instead of qmake-qt4.
   * [c08a568] Updating changelog.
Checksums-Sha1:
 9b3e8b7177e0b987c8930fd980ad208df812c589 2168 gpsbabel_1.5.4-1.dsc
 169d88adfdb4ee2c8a945246510948accc6b63ac 9122518 gpsbabel_1.5.4.orig.tar.gz
 d4e13bd6936599a3dd83b3783dfcef930dc1bca4 15697 gpsbabel_1.5.4-1.diff.gz
 88b5b341e777aa1c3d36e029ce1084e28f9ff1cd 12848 
gpsbabel_1

Bug#872744: marked as done (gpsbabel FTBFS on 32bit with gcc 7)

[Debian Bug Tracking System]

Your message dated Mon, 28 Aug 2017 22:53:28 +
with message-id 
and subject line Bug#872744: fixed in gpsbabel 1.5.4-1
has caused the Debian Bug report #872744,
regarding gpsbabel FTBFS on 32bit with gcc 7
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.)


-- 
872744: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872744
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gpsbabel
Version: 1.5.3-2
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/gpsbabel.html

...
g++  -g -O2 -Wall -c   -I. -I/usr/include/qt4  -DHAVE_CONFIG_H -DNEW_STRINGS 
exif.cc -o exif.o
exif.cc: In function 'void exif_find_wpt_by_time(const Waypoint*)':
exif.cc:1103:63: error: call of overloaded 'abs(long unsigned int)' is ambiguous
   } else if (abs(exif_time_ref - wpt->creation_time.toTime_t()) < 
abs(exif_time_ref - exif_wpt_ref->creation_time.toTime_t())) {
   ^
In file included from /usr/include/c++/7/cstdlib:75:0,
 from /usr/include/c++/7/bits/stl_algo.h:59,
 from /usr/include/c++/7/algorithm:62,
 from /usr/include/qt4/QtCore/qglobal.h:68,
 from /usr/include/qt4/QtCore/qchar.h:45,
 from /usr/include/qt4/QtCore/qstring.h:45,
 from /usr/include/qt4/QtCore/QString:1,
 from gbfile.h:30,
 from defs.h:33,
 from exif.cc:31:
/usr/include/stdlib.h:735:12: note: candidate: int abs(int)
 extern int abs (int __x) __THROW __attribute__ ((__const__)) __wur;
^~~
In file included from /usr/include/c++/7/cstdlib:77:0,
 from /usr/include/c++/7/bits/stl_algo.h:59,
 from /usr/include/c++/7/algorithm:62,
 from /usr/include/qt4/QtCore/qglobal.h:68,
 from /usr/include/qt4/QtCore/qchar.h:45,
 from /usr/include/qt4/QtCore/qstring.h:45,
 from /usr/include/qt4/QtCore/QString:1,
 from gbfile.h:30,
 from defs.h:33,
 from exif.cc:31:
/usr/include/c++/7/bits/std_abs.h:56:3: note: candidate: long int std::abs(long 
int)
   abs(long __i) { return __builtin_labs(__i); }
   ^~~
/usr/include/c++/7/bits/std_abs.h:61:3: note: candidate: long long int 
std::abs(long long int)
   abs(long long __x) { return __builtin_llabs (__x); }
   ^~~
/usr/include/c++/7/bits/std_abs.h:70:3: note: candidate: constexpr double 
std::abs(double)
   abs(double __x)
   ^~~
/usr/include/c++/7/bits/std_abs.h:74:3: note: candidate: constexpr float 
std::abs(float)
   abs(float __x)
   ^~~
/usr/include/c++/7/bits/std_abs.h:78:3: note: candidate: constexpr long double 
std::abs(long double)
   abs(long double __x)
   ^~~
/usr/include/c++/7/bits/std_abs.h:102:3: note: candidate: constexpr __float128 
std::abs(__float128)
   abs(__float128 __x)
   ^~~
--- End Message ---
--- Begin Message ---
Source: gpsbabel
Source-Version: 1.5.4-1

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

Debian distribution maintenance software
pp.
Bernd Zeimetz  (supplier of updated gpsbabel 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, 28 Aug 2017 23:53:53 +0200
Source: gpsbabel
Binary: gpsbabel gpsbabel-doc gpsbabel-gui
Architecture: source
Version: 1.5.4-1
Distribution: unstable
Urgency: medium
Maintainer: Bernd Zeimetz 
Changed-By: Bernd Zeimetz 
Description:
 gpsbabel   - GPS file conversion plus transfer to/from GPS units
 gpsbabel-doc - GPS file conversion plus transfer to/from GPS units
 gpsbabel-gui - GPS file conversion plus transfer to/from GPS units - GUI
Closes: 816808 872744
Changes:
 gpsbabel (1.5.4-1) unstable; urgency=medium
 .
   * [ee23f26] Merge branch 'upstream'
 - New upstream version.
 - Builds fine with gcc7.
 Thanks to Adrian Bunk (Closes: #872744)
   * [f340fb9] Refreshing patches.
   * [8100370] export QT_SELECT=qt5
   * [522c580] Build for/with QT5.
 Usi

Bug#870228: marked as done (physamp: fails to upgrade from 'stretch' - trying to overwrite /usr/bin/bppphysamp)

[Debian Bug Tracking System]

Your message dated Mon, 28 Aug 2017 22:12:55 +
with message-id 
and subject line Bug#870228: fixed in physamp 1.0.2-2
has caused the Debian Bug report #870228,
regarding physamp: fails to upgrade from 'stretch' - trying to overwrite 
/usr/bin/bppphysamp
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.)


-- 
870228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870228
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: physamp
Version: 1.0.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', 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 physamp.
  Preparing to unpack .../physamp_1.0.2-1_amd64.deb ...
  Unpacking physamp (1.0.2-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/physamp_1.0.2-1_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/bppphysamp', which is also in package bppsuite 
2.2.0-0.1+b1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/physamp_1.0.2-1_amd64.deb


cheers,

Andreas


bppsuite=2.2.0-0.1+b1_physamp=1.0.2-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: physamp
Source-Version: 1.0.2-2

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

Debian distribution maintenance software
pp.
Julien Dutheil  (supplier of updated physamp 
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, 09 Aug 2017 23:25:04 +0200
Source: physamp
Binary: physamp
Architecture: source
Version: 1.0.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Julien Dutheil 
Description:
 physamp- sample sequence alignment according to its corresponding phylogen
Closes: 870228
Changes:
 physamp (1.0.2-2) unstable; urgency=medium
 .
   [ Julien Dutheil ]
   * Added bppsuite breaks+replaces statement
 Closes: #870228
   * Updated description to include bppPhySamp program.
   * Does not override debian cxx flags anymore.
 .
   [ Andreas Tille ]
   * Standards-Version: 4.1.0 (no changes needed)
   * use `cme fix dpkg-control` to adjust line length in description
Checksums-Sha1:
 f2698b55e6b356ab3ad597335a95154874d518e7 2048 physamp_1.0.2-2.dsc
 de7977e050b20fcd01dd2960ac5656b1e7d3d711 3008 physamp_1.0.2-2.debian.tar.xz
 b95621662d4e3b23f99b3131e4b5ca09265b69d1 13461 physamp_1.0.2-2_source.buildinfo
Checksums-Sha256:
 58de8205b6cabd44093ee23cf03585899eb28a76872d9f885d3b1d75882d7ca8 2048 
physamp_1.0.2-2.dsc
 c4ce2fade6977416ae3dcc3253faed2cc5da26699db4400e2022c0a8437775ad 3008 
physamp_1.0.2-2.debian.tar.xz
 4ca92154ac4aa1e7db200c0e9d7f59c1fafe5fee589afa952916e02c8d6f0d98 13461 
physamp_1.0.2-2_source.buildinfo
Files:
 fe03d0260496474341f449271715a9ef 2048 science optional physamp_1.0.2-2.dsc
 5eb6fb126fd056adb1f187cc4dd1fbce 3008 science optional 
physamp_1.0.2-2.debian.tar.xz
 5673ac367f0eb9cef437240b2a40ee0a 13461 science optional 
physamp_1.0.2-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJCBAEBCgAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlmkg30OHHRpbGxlYUBy
a2kuZGUACgkQV4oElNHGRtGd0A/+LCdu059Ewqf91CgndOMDvDof+8iArae9L7jm
VHVeBAoSRHlZT49i2CwfnDX9/Di4W8Lq0rZgRY3mv3y1L9fz1MyhRotebpSfwR1x
EG/13dwf8JLwVeiqMNFLiTVLOLD8YI3gkiQLiF8DPachTtYTpcAaXxcc3bvksdg8
g5web7Z+yjixw6mgRQ1mZgLaGCxa4/lTwzhZu3ZllB9++tkQGv1IvDYkb2l/umyd
T0Qx6aPVwAFGPv7O9qR7FerVOEABkAhlDZGDH9Eqg/e6E4Wwh4g+tw6L6unWZPRw
yEWhfJHVOMv/zw2k1GNuuZurB/vnPILwBPtMAaV2QJLk3LYqTE9yqW2iJpdWBz8X
eEFsTRLhhXChfIBCkBRfgmG7dQRSYXyYRKpmH+EapkgXmOxzzr1Uh+5qWJV8QVP0
W4EL1P7a2hlFMQYxB+bjAbk7k3+vTUWJ2MrVq3l9Ec59INa98so61VBd5YPPYT4G
50LS3WNsta1MUaKeeVdwnC57dEsHTlbt4FXGApZqHHQq2o

Bug#853656: marked as done (sga: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Mon, 28 Aug 2017 21:21:53 +
with message-id 
and subject line Bug#853656: fixed in sga 0.10.15-3
has caused the Debian Bug report #853656,
regarding sga: ftbfs with GCC-7
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.)


-- 
853656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sga
Version: 0.10.15-2
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/sga_0.10.15-2_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
g++ -DHAVE_CONFIG_H -I. -I..  -I../Bigraph -I../Thirdparty -Wdate-time 
-D_FORTIFY_SOURCE=2 -fopenmp  -I/usr//include -I/usr//include/bamtools -Wall 
-Wextra  -Wno-unknown-pragmas -std=c++98 -O3 -c -o libutil_a-MultiAlignment.o 
`test -f 'MultiAlignment.cpp' || echo './'`MultiAlignment.cpp
g++ -DHAVE_CONFIG_H -I. -I..  -I../Bigraph -I../Thirdparty -Wdate-time 
-D_FORTIFY_SOURCE=2 -fopenmp  -I/usr//include -I/usr//include/bamtools -Wall 
-Wextra  -Wno-unknown-pragmas -std=c++98 -O3 -c -o libutil_a-StdAlnTools.o 
`test -f 'StdAlnTools.cpp' || echo './'`StdAlnTools.cpp
g++ -DHAVE_CONFIG_H -I. -I..  -I../Bigraph -I../Thirdparty -Wdate-time 
-D_FORTIFY_SOURCE=2 -fopenmp  -I/usr//include -I/usr//include/bamtools -Wall 
-Wextra  -Wno-unknown-pragmas -std=c++98 -O3 -c -o libutil_a-VCFUtil.o `test -f 
'VCFUtil.cpp' || echo './'`VCFUtil.cpp
g++ -DHAVE_CONFIG_H -I. -I..  -I../Bigraph -I../Thirdparty -Wdate-time 
-D_FORTIFY_SOURCE=2 -fopenmp  -I/usr//include -I/usr//include/bamtools -Wall 
-Wextra  -Wno-unknown-pragmas -std=c++98 -O3 -c -o libutil_a-QualityTable.o 
`test -f 'QualityTable.cpp' || echo './'`QualityTable.cpp
g++ -DHAVE_CONFIG_H -I. -I..  -I../Bigraph -I../Thirdparty -Wdate-time 
-D_FORTIFY_SOURCE=2 -fopenmp  -I/usr//include -I/usr//include/bamtools -Wall 
-Wextra  -Wno-unknown-pragmas -std=c++98 -O3 -c -o libutil_a-BloomFilter.o 
`test -f 'BloomFilter.cpp' || echo './'`BloomFilter.cpp
g++ -DHAVE_CONFIG_H -I. -I..  -I../Bigraph -I../Thirdparty -Wdate-time 
-D_FORTIFY_SOURCE=2 -fopenmp  -I/usr//include -I/usr//include/bamtools -Wall 
-Wextra  -Wno-unknown-pragmas -std=c++98 -O3 -c -o libutil_a-VariantIndex.o 
`test -f 'VariantIndex.cpp' || echo './'`VariantIndex.cpp
VariantIndex.cpp: In member function 'VariantRecordVector 
VariantIndex::getNearVariants(const string&, int, int) const':
VariantIndex.cpp:89:46: error: call of overloaded 'abs(long unsigned int)' is 
ambiguous
 if(abs(record.position - position) < distance)
  ^
In file included from /usr/include/c++/7/cstdlib:75:0,
 from /usr/include/c++/7/bits/stl_algo.h:59,
 from /usr/include/c++/7/algorithm:62,
 from VariantIndex.cpp:11:
/usr/include/stdlib.h:735:12: note: candidate: int abs(int)
 extern int abs (int __x) __THROW __attribute__ ((__const__)) __wur;
^~~
In file included from /usr/include/c++/7/cstdlib:77:0,
 from /usr/include/c++/7/bits/stl_algo.h:59,
 from /usr/include/c++/7/algorithm:62,
 from VariantIndex.cpp:11:
/usr/include/c++/7/bits/std_abs.h:56:3: note: candidate: long int std::abs(long 
int)
   abs(long __i) { return __builtin_labs(__i); }
   ^~~
/usr/include/c++/7/bits/std_abs.h:61:3: note: candidate: long long int 
std::abs(long long int)
   abs(long long __x) { return __builtin_llabs (__x); }
   ^~~
/usr/include/c++/7/bits/std_abs.h:70:3: n

Bug#873540: capnproto: FTBFS on mips64el: test.capnp wants AnyList::Pipeline

[Tom Lee]

Thanks for the report Aaron, raised upstream at
https://github.com/capnproto/capnproto/issues/541

I'll dig into it more later this week if upstream doesn't beat me to it.

On Mon, Aug 28, 2017 at 1:01 PM, Aaron M. Ucko  wrote:

> Source: capnproto
> Version: 0.6.1-1
> Severity: serious
> Tags: upstream
> Justification: fails to build from source
>
> The latest mips64el build of capnproto failed, as detailed at
> https://buildd.debian.org/status/fetch.php?pkg=
> capnproto&arch=mips64el&ver=0.6.1-1&stamp=1503916947&raw=0
> and (very briefly) excerpted below:
>
>   src/capnp/test.capnp.h:12247:29: error: 'Pipeline' in 'struct
>   capnp::AnyList' does not name a type
>  inline  ::capnp::AnyList::Pipeline getAnyListAsList();
>^~~~
>
> AFAICT, there's not supposed to be any such type, so the problem
> presumably lies in code generation.  Could you please take a look?
> Thanks!
>
> --
> 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
>



-- 
*Tom Lee */ http://tomlee.co / @tglee 

Bug#869260: marked as done (CVE-2017-11368)

[Debian Bug Tracking System]

Your message dated Mon, 28 Aug 2017 16:57:41 -0400
with message-id 
and subject line Fixed in krb5 1.12.1+dfsg-19+deb8u3
has caused the Debian Bug report #869260,
regarding CVE-2017-11368
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.)


-- 
869260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869260
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: krb5
Severity: grave
Tags: security

Hi,
please see:
https://github.com/krb5/krb5/pull/678/commits/a860385dd8fbd239fdb31b347e07f4e6b2fbdcc2

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
source: krb5
source-version: 1.12.1+dfsg-19+deb8ku3

Hi.
The following issues were fixed in 1.12.1+dfsg-19+deb8u3 for jessie.
I ended up needing to build a +deb8u4 because of a build/upload issue,
and so the bugs were not automattically closed.
Here's the relevant changelog info:

krb5 (1.12.1+dfsg-19+deb8u4) jessie; urgency=medium

  * New version number; same code as deb8u3 but rebuilt to build arch all
packages and because dgit doesn't deal well with reusing a version
number when a package is rejected

 -- Sam Hartman   Mon, 28 Aug 2017 11:55:49 -0400

krb5 (1.12.1+dfsg-19+deb8u3) jessie; urgency=high

  * CVE-2017-11368: Remote authenticated attackers can crash the KDC,
Closes: #869260
  *  fix for CVE-2016-3120 (kdc crash on restrict_anon_to_tgt), Closes:
#832572
  * fix for CVE-2016-3119: remote DOS with ldap for authenticated
attackers, Closes: #819468
  * Prevent requires_preauth bypass (CVE-2015-2694), Closes: #783557
  
 -- Sam Hartman   Sun, 13 Aug 2017 18:02:34 -0400



signature.asc
Description: PGP signature
--- End Message ---

Bug#853309: marked as done (altermime: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Mon, 28 Aug 2017 21:04:44 +
with message-id 
and subject line Bug#853309: fixed in altermime 0.3.10-9
has caused the Debian Bug report #853309,
regarding altermime: ftbfs with GCC-7
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.)


-- 
853309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853309
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:altermime
Version: 0.3.10-8
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/altermime_0.3.10-8_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
make[1]: Entering directory '/<>'
rm -rf debian/docs/html
dh_auto_clean
make -j1 clean
make[2]: Entering directory '/<>'
rm -f *.o altermime
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
   dh_clean
 dpkg-source -b altermime-0.3.10
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building altermime using existing 
./altermime_0.3.10.orig.tar.gz
dpkg-source: info: building altermime in altermime_0.3.10-8.debian.tar.xz
dpkg-source: info: building altermime in altermime_0.3.10-8.dsc
 debian/rules build
dh build
   dh_testdir
   dh_update_autotools_config
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
linuxdoc --backend=html debian/docs/postfix-altermime-howto.sgml
Processing file debian/docs/postfix-altermime-howto.sgml
mkdir -p debian/docs/html
mv -f postfix-altermime-howto*.html debian/docs/html
dh_auto_configure
make[1]: Leaving directory '/<>'
   dh_auto_build
make -j1
make[1]: Entering directory '/<>'
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Werror -g -I. -O2  -Wdate-time 
-D_FORTIFY_SOURCE=2 -c strstack.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Werror -g -I. -O2  -Wdate-time 
-D_FORTIFY_SOURCE=2 -c mime_alter.c
mime_alter.c: In function 'AM_add_disclaimer_insert_html':
mime_alter.c:1509:45: error: output may be truncated before the last format 
character [-Werror=format-truncation=]
   snprintf(boundary, sizeof(boundary), "--%s", dd->boundary);
 ^
In file included from /usr/include/stdio.h:938:0,
 from mime_alter.c:1:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:64:10: note: format output between 
3 and 1026 bytes into a destination of size 1025
   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
  ^~~~
__bos (__s), __fmt, __va_arg_pack ());
~
cc1: all warnings being treated as errors
Makefile:17: recipe for target 'mime_alter.o' failed
make[1]: *** [mime_alter.o] Error 1
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
debian/rules:7: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---
Source: altermime
Source-Version: 0.3.10-9

We believe that the bug you reported is fixed in the latest version of
altermime, 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 853...@bugs.debian.org,
and the maintainer will reopen th

Bug#854769: You should have recieved a mail about check-tiff RC bug

[Andreas Tille]

Hi Andreas,

are you aware of

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854769

If not you should probably subscribe the package in PTS.

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#853656: Help needed with gcc-7 error

[Andreas Tille]

Hi James,

On Sun, Aug 27, 2017 at 02:58:34PM +0100, James Cowgill wrote:
> > g++ -DHAVE_CONFIG_H -I. -I..  -I../Bigraph -I../Thirdparty -Wdate-time 
> > -D_FORTIFY_SOURCE=2 -fopenmp  -I/usr//include -I/usr//include/bamtools 
> > -Wall -Wextra  -Wno-unknown-pragmas -std=c++98 -O3 -c -o 
> > libutil_a-VariantIndex.o `test -f 'VariantIndex.cpp' || echo 
> > './'`VariantIndex.cpp
> > VariantIndex.cpp: In member function 'VariantRecordVector 
> > VariantIndex::getNearVariants(const string&, int, int) const':
> > VariantIndex.cpp:89:46: error: call of overloaded 'abs(long unsigned int)' 
> > is ambiguous
> >  if(abs(record.position - position) < distance)
> >   ^
> 
> In C++11, you cannot call abs on an unsigned integer (which makes no
> sense anyway). Probably "record.position" needs casting to a signed type
> (like long).

Well, casting to long helped - but in how far does making

abs(unsigned - unsigned)

no sense?  This does not sound very logical to me.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#870253: clamav-milter: disengaging debconf management destroys config

[Sebastian Andrzej Siewior]

On 2017-08-28 17:04:51 [+0900], Marc Dequènes (Duck) wrote:
> Quack,
Hi,

> Thanks.
> 
> I can help you test if you provide a test package.

as you wish. At
https://breakpoint.cc/clamav/

you can find a .dsc file of what we have currently in git on alioth and
a prebuilt binary for amd64.

> \_o<
> 


Sebastian

Bug#873540: capnproto: FTBFS on mips64el: test.capnp wants AnyList::Pipeline

[Aaron M. Ucko]

Source: capnproto
Version: 0.6.1-1
Severity: serious
Tags: upstream
Justification: fails to build from source

The latest mips64el build of capnproto failed, as detailed at
https://buildd.debian.org/status/fetch.php?pkg=capnproto&arch=mips64el&ver=0.6.1-1&stamp=1503916947&raw=0
and (very briefly) excerpted below:

  src/capnp/test.capnp.h:12247:29: error: 'Pipeline' in 'struct
  capnp::AnyList' does not name a type
 inline  ::capnp::AnyList::Pipeline getAnyListAsList();
   ^~~~

AFAICT, there's not supposed to be any such type, so the problem
presumably lies in code generation.  Could you please take a look?
Thanks!

-- 
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#873362: coinor-libcoinutils3v5: unannounced ABI change without SONAME change?

[James Cowgill]

Hi,

On 28/08/17 19:57, Anton Gladky wrote:
> Thanks all for discussion, explanations and investigations!
> 
> @Rene, I propose to close this bug or to wait till upload of libreoffice.
> 
> Next time, when the new coinutils version comes, I will let you know
> and coinmp should be tested against the new coinutils. Then it should
> probably be uploaded into the sid restricting in BD the minimal coinutils
> to guarantee the ABI compatibility like it done for all other dependent
> packages [1]. What do you think?
> 
> [1] 
> https://anonscm.debian.org/cgit/debian-science/packages/coinor-cbc.git/tree/debian/control#n8

If there is an ABI break, you must rename the package. Trying to
restrict the build-dependencies will have no effect on the dependencies
at runtime which is where the ABI actually matters.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#873508: parsing horst source code fails on s390x and ppc64el

[James Clarke]

On 28 Aug 2017, at 20:23, Uwe Kleine-König  wrote:
> On Mon, Aug 28, 2017 at 03:10:10PM -0400, Antoine Beaupré wrote:
>> On 2017-08-28 20:53:02, Uwe Kleine-König wrote:
>>> On 08/28/2017 04:32 PM, Antoine Beaupré wrote:
 Control: severity 873508 serious
 Control: affects 873508 horst
 
 On 2017-08-28 15:22:20, James Clarke wrote:
> As discussed on IRC, ppc64 and sparc64 are also affected; while they are
> not release architectures and are thus less important, it would make
> sense to fix those (and check any other Debian architectures) at the
> same time.
 
 Also discussed on IRC is the above change in severity to make the bug
 RC.
>>> 
>>> As I didn't follow that irc discussion and fail to see why this bug
>>> should be severity serious. Can you please repeat the justification
>>> here? I would have picked "normal".
>> 
>> I believe the reason is that it doesn't actually work on two supported
>> architectures.
> 
> That would in my eyes still be "important". Looking at the definitions
> on https://www.debian.org/Bugs/Developer#severities there is:
> 
> - serious
>   is a severe violation of Debian policy (roughly, it violates a "must"
>   or "required" directive), or, in the package maintainer's or release
>   manager's opinion, makes the package unsuitable for release.
> - important
>   a bug which has a major effect on the usability of a package, without
>   rendering it completely unusable to everyone.
> 
> IMHO important is an exact match here.

It's basically unusable on those arches except for trivial code. Even headers
like stdio.h pull in stubs.h, and many other things will likely break due to
not having the right defines. Shipping this as-is is just asking for trouble.
IMO the only way to make this non-RC would be to RM on the affected arches
and make test suite failures fatal so we don't get broken binaries again.

James

Bug#873508: parsing horst source code fails on s390x and ppc64el

[Uwe Kleine-König]

Hello Antoine,

On Mon, Aug 28, 2017 at 03:10:10PM -0400, Antoine Beaupré wrote:
> On 2017-08-28 20:53:02, Uwe Kleine-König wrote:
> > On 08/28/2017 04:32 PM, Antoine Beaupré wrote:
> >> Control: severity 873508 serious
> >> Control: affects 873508 horst
> >> 
> >> On 2017-08-28 15:22:20, James Clarke wrote:
> >>> As discussed on IRC, ppc64 and sparc64 are also affected; while they are
> >>> not release architectures and are thus less important, it would make
> >>> sense to fix those (and check any other Debian architectures) at the
> >>> same time.
> >> 
> >> Also discussed on IRC is the above change in severity to make the bug
> >> RC.
> >
> > As I didn't follow that irc discussion and fail to see why this bug
> > should be severity serious. Can you please repeat the justification
> > here? I would have picked "normal".
> 
> I believe the reason is that it doesn't actually work on two supported
> architectures.

That would in my eyes still be "important". Looking at the definitions
on https://www.debian.org/Bugs/Developer#severities there is:

 - serious
   is a severe violation of Debian policy (roughly, it violates a "must"
   or "required" directive), or, in the package maintainer's or release
   manager's opinion, makes the package unsuitable for release.
 - important
   a bug which has a major effect on the usability of a package, without
   rendering it completely unusable to everyone.

IMHO important is an exact match here.

Best regards
Uwe


signature.asc
Description: PGP signature

Bug#873508: parsing horst source code fails on s390x and ppc64el

[James Clarke]

On 28 Aug 2017, at 20:10, Antoine Beaupré  wrote:
> On 2017-08-28 20:53:02, Uwe Kleine-König wrote:
>> Hello,
>> 
>> On 08/28/2017 04:32 PM, Antoine Beaupré wrote:
>>> Control: severity 873508 serious
>>> Control: affects 873508 horst
>>> 
>>> On 2017-08-28 15:22:20, James Clarke wrote:
 As discussed on IRC, ppc64 and sparc64 are also affected; while they are
 not release architectures and are thus less important, it would make
 sense to fix those (and check any other Debian architectures) at the
 same time.
>>> 
>>> Also discussed on IRC is the above change in severity to make the bug
>>> RC.
>> 
>> As I didn't follow that irc discussion and fail to see why this bug
>> should be severity serious. Can you please repeat the justification
>> here? I would have picked "normal".
> 
> I believe the reason is that it doesn't actually work on two supported
> architectures.

Specifically that it's built for the architectures but can't actually be used.
Looking at the build logs, some of the tests run as part of the test suite hit
this error, but the upstream test harness always exits with code 0[0] so it's
not fatal. Boo.

James

[0] 
https://anonscm.debian.org/cgit/collab-maint/sparse.git/tree/validation/test-suite#n251

Bug#873508: parsing horst source code fails on s390x and ppc64el

[Antoine Beaupré]

On 2017-08-28 20:53:02, Uwe Kleine-König wrote:
> Hello,
>
> On 08/28/2017 04:32 PM, Antoine Beaupré wrote:
>> Control: severity 873508 serious
>> Control: affects 873508 horst
>> 
>> On 2017-08-28 15:22:20, James Clarke wrote:
>>> As discussed on IRC, ppc64 and sparc64 are also affected; while they are
>>> not release architectures and are thus less important, it would make
>>> sense to fix those (and check any other Debian architectures) at the
>>> same time.
>> 
>> Also discussed on IRC is the above change in severity to make the bug
>> RC.
>
> As I didn't follow that irc discussion and fail to see why this bug
> should be severity serious. Can you please repeat the justification
> here? I would have picked "normal".

I believe the reason is that it doesn't actually work on two supported
architectures.

A.

-- 
While the creative works from the 16th century can still be accessed
and used by others, the data in some software programs from the 1990s
is already inaccessible.
 - Lawrence Lessig

Processed: found 873439 in 3.0.0-5

[Debian Bug Tracking System]

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

> found 873439 3.0.0-5
Bug #873439 [src:flightgear] flightgear: CVE-2017-13709: Incorrect access 
control
Marked as found in versions flightgear/3.0.0-5.
> thanks
Stopping processing here.

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

Bug#873535: zoomer: should zoomer be removed?

[Sebastian Ramacher]

Source: zoomer
Version: 0.1-1.1
Severity: serious
Tags: sid buster

zoomer has only ever seen one maintainer upload in 2008 and we had to NMU it
while switching from to ffmpeg to libav in 2013. It seems that we now have to
NMU again to switch back from libav to ffmpeg. Since it's evident that zoomer is
unmaintained and also appears to be dead upstream, I think it is time to get it
removed from the archive.

If you agree, please reassign this bug to ftp.debian.org:

Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: zoomer -- RM; unmaintained
Control: severity -1 normal

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#873508: parsing horst source code fails on s390x and ppc64el

[Uwe Kleine-König]

Hello,

On 08/28/2017 04:32 PM, Antoine Beaupré wrote:
> Control: severity 873508 serious
> Control: affects 873508 horst
> 
> On 2017-08-28 15:22:20, James Clarke wrote:
>> As discussed on IRC, ppc64 and sparc64 are also affected; while they are
>> not release architectures and are thus less important, it would make
>> sense to fix those (and check any other Debian architectures) at the
>> same time.
> 
> Also discussed on IRC is the above change in severity to make the bug
> RC.

As I didn't follow that irc discussion and fail to see why this bug
should be severity serious. Can you please repeat the justification
here? I would have picked "normal".

Best regards
Uwe



signature.asc
Description: OpenPGP digital signature

Bug#873362: coinor-libcoinutils3v5: unannounced ABI change without SONAME change?

[Anton Gladky]

Thanks all for discussion, explanations and investigations!

@Rene, I propose to close this bug or to wait till upload of libreoffice.

Next time, when the new coinutils version comes, I will let you know
and coinmp should be tested against the new coinutils. Then it should
probably be uploaded into the sid restricting in BD the minimal coinutils
to guarantee the ABI compatibility like it done for all other dependent
packages [1]. What do you think?

[1] 
https://anonscm.debian.org/cgit/debian-science/packages/coinor-cbc.git/tree/debian/control#n8

Best regards

Anton


2017-08-28 17:56 GMT+02:00 James Cowgill :
> These appear to be the 4 symbols which have disappeared after compiling
> with GCC-7:
>
>  469: 000cce10   430 FUNCWEAK   DEFAULT   12 
> _ZNK16CoinPackedMatrix14getVectorFirstEi
>  614: 000ccfc0   437 FUNCWEAK   DEFAULT   12 
> _ZNK16CoinPackedMatrix13getVectorLastEi
> 1119: 000fc710   120 FUNCWEAK   DEFAULT   12 
> _Z26presolve_delete_from_majoriiPKiPiS1_Pd
> 1198: 00043f80   566 FUNCWEAK   DEFAULT   12 
> _Z9CoinFillNItEvPT_iS0_
>
> As you can see all of these symbols are declared as weak. GCC will often
> do this for inline functions which it has decided not to inline for some
> reason. To satisfy the ODR, GCC will export all these symbols as weak
> from any object (including executables) which use them so that the same
> function is used throughout the entire application. Because consumers
> are supposed to generate their own versions of these functions, they do
> not form a part of the ABI and can safely be removed. In this case,
> GCC-7 simply decided that these functions should be inlined and
> therefore didn't generate symbols for them.
>
> I think it's more likely these ABI issues are caused by changes in the
> class layout (but I have not investigated this much). You can see a few
> cases of new fields being added if you diff the headers from the old and
> new packages. Generally, any issues with symbols would be found by the
> dynamic linker before an application has a chance to segfault.
>
> Thanks,
> James
>

Bug#872378: fenrir.deb: No speech after enabling fenrir to start inconcial.

[Paul Gevers]

Hi Matthew

On 28-08-17 15:06, Matthew Dyer wrote:
>> Could you try to downgrade to version 1.05-1 so as to check whether it's
>> only version 1.06-1 which has the issue?

> Anyhow,  went trying to downgrade, I got the
> package not found erroor.  Am I doing something wrong?  I did sudo
> apt-get install fenrir 1.05.

Yes, the invocation is (at least I am pretty sure):
sudo apt-get install fenrir=1.05-1
or
sudo apt-get install -t testing fenrir

Both commands require that you have both unstable (sid) and testing
(buster) in your apt/source.list. If you don't have that and don't want
to change it, you could download¹ the fenrir deb package and install it with
dpkg -i path/to/fenrir.deb

Paul
¹ https://packages.debian.org/buster/all/fenrir/download



signature.asc
Description: OpenPGP digital signature

Bug#873439: [pkg-fgfs-crew] Bug#873439: flightgear: CVE-2017-13709: Incorrect access control

[Florent Rougon]

Hi,

For stretch, the last two commits of upstream branch release/2016.4:

  https://sourceforge.net/p/flightgear/flightgear/ci/release/2016.4/~/tree/

should do the job (as already said in other mails, and ditto for
unstable with the release/2017.2 branch).

For jessie (it's also affected), I successfully built FG in a
jessie-amd64 pbuilder chroot with the attached source debdiff. You'll
certainly want to make the patch headers DEP-3-compliant and arrange
debian/changelog (at least the version number), but the C++ side should
be fine with these changes. I only tested the build in this old version:
no runtime test, but I don't expect any particular problem. :)

Regards

-- 
Florent
diff -Nru flightgear-3.0.0/debian/changelog flightgear-3.0.0/debian/changelog
--- flightgear-3.0.0/debian/changelog	2017-07-02 14:39:08.0 +0200
+++ flightgear-3.0.0/debian/changelog	2017-08-28 18:07:28.0 +0200
@@ -1,3 +1,13 @@
+flightgear (3.0.0-5+deb8u3+frougon0) jessie; urgency=high
+
+  * Add two patches for CVE-2017-13709:
+  - call-fgInitAllowedPaths-earlier-c7a2ae.patch (required by the next
+patch)
+  - CVE-2017-13709-FGLogger-2a5e3d.patch
+  * The patch headers are not in the Debian DEP-3 format, this needs fixing.
+
+ -- Florent Rougon   Mon, 28 Aug 2017 18:07:28 +0200
+
 flightgear (3.0.0-5+deb8u2) jessie; urgency=high
 
   * Add patch restrict-save-flightplan-secu-fix-faf872.patch: prevent
diff -Nru flightgear-3.0.0/debian/patches/call-fgInitAllowedPaths-earlier-c7a2ae.patch flightgear-3.0.0/debian/patches/call-fgInitAllowedPaths-earlier-c7a2ae.patch
--- flightgear-3.0.0/debian/patches/call-fgInitAllowedPaths-earlier-c7a2ae.patch	1970-01-01 01:00:00.0 +0100
+++ flightgear-3.0.0/debian/patches/call-fgInitAllowedPaths-earlier-c7a2ae.patch	2017-08-28 18:07:28.0 +0200
@@ -0,0 +1,55 @@
+Author: Florent Rougon 
+
+Call fgInitAllowedPaths() earlier: after Options::processOptions()
+
+Call fgInitAllowedPaths() right after Options::processOptions() (which,
+among other things, determines $FG_ROOT and processes
+--allow-nasal-read). This way, fgInitAllowedPaths() can be used in much
+more code, such as when initializing subsystems.
+
+(cherry picked from commit c7a2aef59979af3e9ff22daabb37bdaadb91cd75)
+
+--- a/src/Main/fg_init.cxx
 b/src/Main/fg_init.cxx
+@@ -1023,7 +1023,12 @@
+ fgGetNode("/sim")->removeChild("aircraft-dir");
+ fgInitAircraft(true);
+ flightgear::Options::sharedInstance()->processOptions();
+-
++
++// Rebuild the lists of allowed paths for cases where a path comes from an
++// untrusted source, such as the global property tree (this uses $FG_HOME
++// and other paths set by Options::processOptions()).
++fgInitAllowedPaths();
++
+ render = new FGRenderer;
+ render->setEventHandler(eventHandler);
+ globals->set_renderer(render);
+--- a/src/Main/main.cxx
 b/src/Main/main.cxx
+@@ -461,7 +461,12 @@
+ } else if (configResult == flightgear::FG_OPTIONS_EXIT) {
+ return EXIT_SUCCESS;
+ }
+-
++
++// Set the lists of allowed paths for cases where a path comes from an
++// untrusted source, such as the global property tree (this uses $FG_HOME
++// and other paths set by Options::processOptions()).
++fgInitAllowedPaths();
++
+ // Initialize the Window/Graphics environment.
+ fgOSInit(&argc, argv);
+ _bootstrap_OSInit++;
+--- a/src/Scripting/NasalSys.cxx
 b/src/Scripting/NasalSys.cxx
+@@ -800,9 +800,6 @@
+   .member("singleShot", &TimerObj::isSingleShot, &TimerObj::setSingleShot)
+   .member("isRunning", &TimerObj::isRunning);
+ 
+-// Set allowed paths for Nasal I/O
+-fgInitAllowedPaths();
+-
+ // Now load the various source files in the Nasal directory
+ simgear::Dir nasalDir(SGPath(globals->get_fg_root(), "Nasal"));
+ loadScriptDirectory(nasalDir);
diff -Nru flightgear-3.0.0/debian/patches/CVE-2017-13709-FGLogger-2a5e3d.patch flightgear-3.0.0/debian/patches/CVE-2017-13709-FGLogger-2a5e3d.patch
--- flightgear-3.0.0/debian/patches/CVE-2017-13709-FGLogger-2a5e3d.patch	1970-01-01 01:00:00.0 +0100
+++ flightgear-3.0.0/debian/patches/CVE-2017-13709-FGLogger-2a5e3d.patch	2017-08-28 18:07:28.0 +0200
@@ -0,0 +1,69 @@
+Author: Florent Rougon 
+
+Security: don't allow FGLogger to overwrite arbitrary files
+
+Since the paths of files written by FGLogger come from the property
+tree[1], they must be validated before we decide to write to these
+files.
+
+[1] Except for the "empty" case, which uses the default name
+'fg_log.csv'.
+
+This fixes CVE-2017-13709.
+
+(cherry picked from commit 2a5e3d06b2c0d9f831063afe7e7260bca456d679)
+
+--- a/src/Main/logger.cxx
 b/src/Main/logger.cxx
+@@ -11,10 +11,14 @@
+ 
+ #include 
+ #include 
++#include 
+ 
+ #include 
++#include 
+ 
+ #include "fg_props.hxx"
++#include "globals.hxx"
++#include "util.hxx"
+ 
+ using std::string;
+ using std

Bug#872275: marked as done (slic3r-prusa: Loadable library and perl binary mismatch)

[Debian Bug Tracking System]

Your message dated Mon, 28 Aug 2017 18:16:30 +
with message-id 
and subject line Bug#872275: fixed in slic3r-prusa 1.37.0+dfsg-1.1
has caused the Debian Bug report #872275,
regarding slic3r-prusa: Loadable library and perl binary mismatch
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.)


-- 
872275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872275
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: slic3r-prusa
Version: 1.31.4-1
Severity: important

Dear Maintainer,

After an upgrade, it no longer works and throws this error:

"buildtmp/XS.c: loadable library and perl binaries are mismatched (got
handshake key 0xdb80080, needed 0xde00080)"

Could this be a dependency problem?



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

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

Versions of packages slic3r-prusa depends on:
ii  libboost-geometry-utils-perl   0.15-2+b6
ii  libboost-system1.62.0  1.62.0+dfsg-4+b1
ii  libboost-thread1.62.0  1.62.0+dfsg-4+b1
ii  libc6  2.24-12
ii  libencode-locale-perl  1.05-1
ii  libgcc11:7.1.0-10
ii  libio-stringy-perl 2.111-2
ii  libmath-convexhull-monotonechain-perl  0.1-1+b6
ii  libmath-geometry-voronoi-perl  1.3-2+b5
ii  libmath-planepath-perl 124-1
ii  libmoo-perl2.003002-1
ii  libperl5.26 [libtime-hires-perl]   5.26.0-5
ii  libstdc++6 7.1.0-10
pn  libstorable-perl   
ii  perl   5.26.0-5

Versions of packages slic3r-prusa recommends:
ii  libclass-xsaccessor-perl  1.19-2+b9
ii  libio-all-perl0.86-2
ii  libopengl-perl0.7000+dfsg-1
ii  libpdf-api2-perl  2.030-1
ii  libsvg-perl   2.64-1
ii  libwx-glcanvas-perl   0.09-3+b5
ii  libwx-perl1:0.9932-2
ii  libxml-sax-expatxs-perl   1.33-2+b4

slic3r-prusa suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: slic3r-prusa
Source-Version: 1.37.0+dfsg-1.1

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated slic3r-prusa 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, 23 Aug 2017 19:17:28 +0200
Source: slic3r-prusa
Binary: slic3r-prusa
Architecture: source
Version: 1.37.0+dfsg-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian 3-D Printing Packages 
<3dprinter-gene...@lists.alioth.debian.org>
Changed-By: gregor herrmann 
Closes: 872275
Description: 
 slic3r-prusa - G-code generator for 3D printers
Changes:
 slic3r-prusa (1.37.0+dfsg-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix "Loadable library and perl binary mismatch":
 add override_dh_perl in debian/rules to make dh_perl search for perl
 modules in the private directory as well.
 (Closes: #872275)
Checksums-Sha1: 
 7c034171b6667bb927dcf54f51de3ec245c9 2721 slic3r-prusa_1.37.0+dfsg-1.1.dsc
 ecf5ef67beac2c623ac3e3c208aaa76ae3ebcf16 26728 
slic3r-prusa_1.37.0+dfsg-1.1.debian.tar.xz
Checksums-Sha256: 
 8541dc1980b9f6901ee209e1d9da05b2c6d485d65065c09ada9f0794c7a58f42 2721 
slic3r-prusa_1.37.0+dfsg-1.1.dsc
 3f9e2d5d45f175c2d51bf1fca14a7241a7e2f46750f949d82702e7cdd7b219a6 26728 
slic3r-prusa_1.37.0+dfsg-1.1.debian.tar.xz
Files: 
 3ed8c0fae61927642a4857f1695ac339 2721 perl optional 
slic3r-prusa_1.37.0+dfsg-1.1.dsc
 6e2cbb1fe85c63f1cdd5c1874ff2db26 26728 perl optional 
slic3r-prusa_1.37.0+dfsg-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoA

Bug#873525: mrpt: FTBFS on mips64el: test_mrpt_graphslam fails

[Aaron M. Ucko]

Source: mrpt
Version: 1:1.5.3-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

The latest mips64el build of mrpt failed:

  cd /<>/obj-mips64el-linux-gnuabi64/tests && ./test_mrpt_graphslam
  [==] Running 4 tests from 2 test cases.
  [--] Global test environment set-up.
  [--] 2 tests from GraphSlamLevMarqTester2D
  [ RUN  ] GraphSlamLevMarqTester2D.OptimizeSampleRingPath
  /<>/libs/graphslam/src/graph_slam_levmarq_unittest.cpp:59: 
Failure
  Expected: (levmarq_info.final_total_sq_error) <= (1e-2), actual: 534.008 vs 
0.01
  Bus error
  tests/CMakeFiles/run_tests_mrpt_graphslam.dir/build.make:60: recipe for 
target 'tests/CMakeFiles/run_tests_mrpt_graphslam' failed

Could you please take a look?

Thanks!

-- 
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: tagging 873063

[Debian Bug Tracking System]

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

> tags 873063 + pending
Bug #873063 [fcitx-frontend-qt5] fcitx-frontend-qt5: Not working with Qt 5.9
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#873437: command-execute: Cannot open load file: No such file or directory, go-mode

[Hilko Bengen]

* Jameson Graef Rollins:

> Hi, Hilko.  I restarted emacs and the problem went away and I was able
> to load go-mode.  I truly don't understand what happened, since I
> definitely installed the golang-mode package before my latest emacs
> session.

So, we might never know. :-)

To me it looks as if your load-path may not have been complete.

It may be a good idea to establish some automatic mechanism by which the
list of available elpa packages (and thus the load-path) is refreshed if
anything changes.

Cheers,
-Hilko

Bug#873437: marked as done (command-execute: Cannot open load file: No such file or directory, go-mode)

[Debian Bug Tracking System]

Your message dated Mon, 28 Aug 2017 09:17:04 -0700
with message-id <87r2vv651b@ligo.caltech.edu>
and subject line Re: Bug#873437: command-execute: Cannot open load file: No 
such file or directory, go-mode
has caused the Debian Bug report #873437,
regarding command-execute: Cannot open load file: No such file or directory, 
go-mode
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.)


-- 
873437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873437
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: elpa-go-mode
Version: 3:1.5.0-1
Severity: grave
Justification: renders package unusable

I don't understand the new elpa system, but for whatever reason this
packages is not actually providing go-mode for me.  When I try "M-x
go-mode" I get the following error:

command-execute: Cannot open load file: No such file or directory, go-mode

This is on emacs 25.2.1.

Please let me know if there's any more information I can provide.  Thanks.

jamie.


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (600, 'testing'), (500, 'stable'), (200, 'unstable'), (101, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages elpa-go-mode depends on:
ii  emacsen-common  2.0.8

Versions of packages elpa-go-mode recommends:
pn  golang-golang-x-tools  

elpa-go-mode suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
On Sun, Aug 27 2017, Hilko Bengen  wrote:
>> I don't understand the new elpa system, but for whatever reason this
>> packages is not actually providing go-mode for me.  When I try "M-x
>> go-mode" I get the following error:
>>
>> command-execute: Cannot open load file: No such file or directory, go-mode
>
> Does this problem persist in a freshly-started instance of Emacs?
>
>> This is on emacs 25.2.1.
>
> I can't reproduce the problem on 25.2.2.

Hi, Hilko.  I restarted emacs and the problem went away and I was able
to load go-mode.  I truly don't understand what happened, since I
definitely installed the golang-mode package before my latest emacs
session.

Anyway, thank you for the response and sorry for the noise.

jamie.


signature.asc
Description: PGP signature
--- End Message ---

Bug#870456: marked as done (postinst script is not executed until the end skipping debhelper bits)

[Debian Bug Tracking System]

Your message dated Mon, 28 Aug 2017 16:05:59 +
with message-id 
and subject line Bug#870456: fixed in sudo 1.8.21-1
has caused the Debian Bug report #870456,
regarding postinst script is not executed until the end skipping debhelper bits
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.)


-- 
870456: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870456
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sudo
Version: 1.8.20p2-1.1
Severity: serious

Hi,

It seems that the postinst script is exiting in the middle of the script
if the sudo group exists bypassing all the bits added by debhelper.

I'm not sure this is supposed to happen.

Regards,

Laurent Bigonville

-- System Information:
Debian Release: buster/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.12.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages sudo depends on:
ii  libaudit1   1:2.7.7-1+b2
ii  libc6   2.24-14
ii  libpam-modules  1.1.8-3.6
ii  libpam0g1.1.8-3.6
ii  libselinux1 2.7~rc2-1
ii  lsb-base9.20161125

sudo recommends no packages.

sudo suggests no packages.

-- Configuration Files:
/etc/sudoers [Errno 13] Permission non accordée: '/etc/sudoers'
/etc/sudoers.d/README [Errno 13] Permission non accordée: 
'/etc/sudoers.d/README'

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: sudo
Source-Version: 1.8.21-1

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

Debian distribution maintenance software
pp.
Bdale Garbee  (supplier of updated sudo 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, 28 Aug 2017 09:44:06 -0600
Source: sudo
Binary: sudo sudo-ldap
Architecture: source amd64
Version: 1.8.21-1
Distribution: unstable
Urgency: medium
Maintainer: Bdale Garbee 
Changed-By: Bdale Garbee 
Description:
 sudo   - Provide limited super user privileges to specific users
 sudo-ldap  - Provide limited super user privileges to specific users
Closes: 786555 823368 862309 870456
Changes:
 sudo (1.8.21-1) unstable; urgency=medium
 .
   [ Bdale Garbee ]
   * new upstream version
   * don't deliver /etc/sudoers.dist, closes: #862309
   * whitelist DPKG_COLORS env var, closes: #823368
 .
   [ Laurent Bigonville ]
   * debian/sudo*.postinst: Drop /var/run/sudo -> /var/lib/sudo migration code,
 this migration happened in 2010 and that code is not necessary anymore
   * Move timestamp files to /run/sudo, with systemd the directory is
 created/cleaned by tmpfiles.d now, the sudo initscript/service is not
 doing anything in that case anymore (Closes: #786555)
   * debian/sudo*.postinst: Move the debhelper marker before the creation of
 the sudo group, this way the snippets added by debhelper will be executed
 even if the group already exists. (Closes: #870456)
Checksums-Sha1:
 4f9be592dde458b9966b515105a93e1ffa0a6046 1970 sudo_1.8.21-1.dsc
 402d4d593f9f222e771e1af146b2c48a99a26f72 2973939 sudo_1.8.21.orig.tar.gz
 38fd466ec7abf8a0104707480d22016b940ca503 23692 sudo_1.8.21-1.debian.tar.xz
 f9ba21eee2425b3e62b05251b097d101912bb6e9 784366 sudo-dbgsym_1.8.21-1_amd64.deb
 ca069d79fa8c85239e6c9602577c5f4a8c647dfb 805824 
sudo-ldap-dbgsym_1.8.21-1_amd64.deb
 6066beef5494935326f2e97e3d3c0aa1fe3c5122 1131348 sudo-ldap_1.8.21-1_amd64.deb
 4b89ced3794e547005eccd3b284317750dffd702 6883 sudo_1.8.21-1_amd64.buildinfo
 08e8e6494fa69bfa2af0f8dddc3d1acff7c436ca 1101258 sudo_1.8.21-1_amd64.deb
Checksums-Sha256:
 e2a108d5e137fb1e0a494b48712950ca17ad07b8c66f2e0d5c51db1c15f2e567 1970 
sudo_1.8.21-1.dsc
 126e9214613e842e19a02658f060186fe6a5927948679d64895b17ed933bb523 2973939 
sudo_1.8.21.orig.tar.gz
 173a2204958051a8e340b4f4aebc09e551d8d8cd24c790

Bug#873362: coinor-libcoinutils3v5: unannounced ABI change without SONAME change?

[James Cowgill]

Hi,

On 28/08/17 13:58, Mattia Rizzolo wrote:
> On Sun, 27 Aug 2017, 8:37 p.m. Anton Gladky  wrote:
> 
>> Hi Mattia,
>>
>> thanks for the tip! I have recompiled both libs with the same
>> current gcc-7.2. And it looks like there are no dropped symbols
>> (see file old-gcc7_new-gcc7.diff in attachment).
>>
>> But if I compare new so-file with the one shipped with Stretch
>> (compiled with gcc6)
>> the diff contains some missing symbols (see file  old-gcc6_new-gcc7.diff).
>>
> 
> Oh!  That's interesting...
> 
> What is the best practice for such kind of libs? Provide symbol-files?
> 
> Not sure.  I'd suggest to try to ask to -mentors@ or -devel@, or perhaps to
> James Cowgirl (CCed now) who helped with gcc-7 related stuff :)

These appear to be the 4 symbols which have disappeared after compiling
with GCC-7:

 469: 000cce10   430 FUNCWEAK   DEFAULT   12 
_ZNK16CoinPackedMatrix14getVectorFirstEi
 614: 000ccfc0   437 FUNCWEAK   DEFAULT   12 
_ZNK16CoinPackedMatrix13getVectorLastEi
1119: 000fc710   120 FUNCWEAK   DEFAULT   12 
_Z26presolve_delete_from_majoriiPKiPiS1_Pd
1198: 00043f80   566 FUNCWEAK   DEFAULT   12 _Z9CoinFillNItEvPT_iS0_

As you can see all of these symbols are declared as weak. GCC will often
do this for inline functions which it has decided not to inline for some
reason. To satisfy the ODR, GCC will export all these symbols as weak
from any object (including executables) which use them so that the same
function is used throughout the entire application. Because consumers
are supposed to generate their own versions of these functions, they do
not form a part of the ABI and can safely be removed. In this case,
GCC-7 simply decided that these functions should be inlined and
therefore didn't generate symbols for them.

I think it's more likely these ABI issues are caused by changes in the
class layout (but I have not investigated this much). You can see a few
cases of new fields being added if you diff the headers from the old and
new packages. Generally, any issues with symbols would be found by the
dynamic linker before an application has a chance to segfault.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#873514: golang-google-cloud: FTBFS due to changes in dependency

[Martín Ferrari]

Source: golang-google-cloud
Version: 0.5.0-2
Severity: serious
Justification: fails to build from source

Since the latest update to golang-google-genproto-dev, this package FTBFS.

The fix for this is in release 0.7.0, but that requires also updating
golang-github-googleapis-gax-go-dev, and I am not sure about the effect on
other rdeps like kubernetes, docker, and cadvisor.

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

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

Bug#873426: marked as done (frobby: frequent parallel FTBFS)

[Debian Bug Tracking System]

Your message dated Mon, 28 Aug 2017 15:49:31 +
with message-id 
and subject line Bug#873426: fixed in frobby 0.9.0-5
has caused the Debian Bug report #873426,
regarding frobby: frequent parallel FTBFS
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.)


-- 
873426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873426
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: frobby
Version: 0.9.0-4
Severity: serious

Example:

https://buildd.debian.org/status/fetch.php?pkg=frobby&arch=i386&ver=0.9.0-4&stamp=1503827903&raw=0

...
Transcript written on bin/doc//manual.log.
cd bin; dvips doc/manual.dvi
rm -rf bin/doc
mkdir bin/doc
for i in 1 2 3; do pdflatex -output-directory=bin/doc/ doc/manual.tex; done
This is dvips(k) 5.997 Copyright 2017 Radical Eye Software (www.radicaleye.com)
dvips: DVI file can't be opened: doc/manual.dvi: No such file or directory
Makefile:253: recipe for target 'docPs' failed
make[2]: *** [docPs] Error 1
make[2]: *** Waiting for unfinished jobs
...


dh compat 10 defaults to parallel building, if this cannot easily
be fixed then calling dh with --no-parallel brings gives what was
previously the default.
--- End Message ---
--- Begin Message ---
Source: frobby
Source-Version: 0.9.0-5

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 27 Aug 2017 20:00:04 -0400
Source: frobby
Binary: frobby libfrobby0 libfrobby-dev libfrobby-doc
Architecture: source
Version: 0.9.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Doug Torrance 
Description:
 frobby - Computations with monomial ideals
 libfrobby-dev - Computations with monomial ideals (development tools)
 libfrobby-doc - Computations with monomial ideals (library documentation)
 libfrobby0 - Computations with monomial ideals (shared library)
Closes: 873426
Changes:
 frobby (0.9.0-5) unstable; urgency=medium
 .
   * debian/control
 - Bump Standards-Version to 4.1.0.
 - Expand Description.
   * debian/rules
 - Disable parallel builds (Closes: #873426).
 - Set FORCE_SOURCE_DATE macro for reproducible builds of manual.
   * debian/watch
 - Bump to uscan 4 and use special strings.
Checksums-Sha1:
 7ab6b262a7f9f21d4baaac2de691b15e4b711310 2322 frobby_0.9.0-5.dsc
 12b9b54985e6f82c2594a1d0aa40a242ace1d5d4 7552 frobby_0.9.0-5.debian.tar.xz
 e74319e15fcdec286b2cf683ed9b7800c3dd965c 13934 frobby_0.9.0-5_source.buildinfo
Checksums-Sha256:
 1c75b2281aab6e32211491bea4c6bf43cb5eb4c7f5a198e045ee04a9f362a04e 2322 
frobby_0.9.0-5.dsc
 e1276204a5ebcdd4e1404753e913c31c9e6c75da38e63376bf96b70cc412e06f 7552 
frobby_0.9.0-5.debian.tar.xz
 1c8e43a8fa7117948bf47f4e57cb500e91e3295277038cc21d73f21387df8cb5 13934 
frobby_0.9.0-5_source.buildinfo
Files:
 ad181cfbb1e8addd1dfa189c26eb45d2 2322 math optional frobby_0.9.0-5.dsc
 c7a944340416da3ad77e812dc5430857 7552 math optional 
frobby_0.9.0-5.debian.tar.xz
 33d808956fbeda8efca7d7431ec0751b 13934 math optional 
frobby_0.9.0-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJCBAEBCgAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlmkL34OHHRpbGxlYUBy
a2kuZGUACgkQV4oElNHGRtFc0A/8DIg05aYGhV3vPXikWscNdpYwronRd9r1t99y
fQUxaoYGACbMh3fdfp3K1vs7gpIN74PFBIefeGtBVaqcW5JVvEKPjUlieVKTsK68
sj3WqQ0RD83icsWmTGW95Yme6q8nT50htIAeQzSh7swowdEl+CvxTqg2TXhM5u3F
BJCLDx7hfRwvZcBhyU6d4aMwS7wbgRg6VhgejLoFZA5bjebOIQ36Y/mL/82kqxOp
W61aB1OQLk8sTf1zwXN5GErfzzcP3+PWIFj3Dvx78WhzfKFr+nq503PQ9Mm99VO+
H21HTftz64guWI7EWtfD8GBR0chFAt6q4moXfXpwU3B620YLBDXEJHrnIYShm7Pt
HwbHYC918v8s8bOAo//dbKEDuqXpPoxohovl7yUeJMIUPPnLs/ur8famYgsv+P5S
ba50j0O6taOFZfu8aRpjreDTRrq3y4+jIKDmidZF/vOIOTeeKIi9ei87JzyS2pvA
wLHM9/3Dc7nHTiGn9BJXI50liKO13Vsp0V2LDkqsiJQ5oLPaEv4ECqGQXjK3DMK3
W9Snc60ZaB4VraoqnqrYR0/sNZqi7Rh1QqYexo06aMYvI08NFXw3WxQUlz3VfEzH
TIl8D0sIeGY1Rt2LhzuXRNKUlxUi9h6TK3O0vrpwpjAVbPjpU6s27GpIfbTZMV2e
pWq3mZs=
=icLR
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#873443: uno-libs3: Fatal exception: Signal 6

[Debian Bug Tracking System]

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

> reassign 873443 libreoffice-core
Bug #873443 [uno-libs3] terminate called after throwing an instance of 
com::sun::star::uno::DeploymentException on architectures not using 
libmergedlo.so
Bug reassigned from package 'uno-libs3' to 'libreoffice-core'.
No longer marked as found in versions libreoffice/1:5.4.0-1.
Ignoring request to alter fixed versions of bug #873443 to the same values 
previously set
> found 873443 1:5.4.0-1
Bug #873443 [libreoffice-core] terminate called after throwing an instance of 
com::sun::star::uno::DeploymentException on architectures not using 
libmergedlo.so
Marked as found in versions libreoffice/1:5.4.0-1.
> thanks
Stopping processing here.

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

Bug#871146: marked as done (plasma-workspace: FTBFS: The file includes the moc file "private/moc_containmentconfigview.cpp", but could not find header "containmentconfigview{.h,.hh,.h++,.hm,.hpp,.hxx,

[Debian Bug Tracking System]

Your message dated Mon, 28 Aug 2017 15:16:17 +
with message-id 
and subject line Bug#871146: fixed in plasma-workspace 4:5.10.5-1
has caused the Debian Bug report #871146,
regarding plasma-workspace: FTBFS: The file includes the moc file 
"private/moc_containmentconfigview.cpp", but could not find header 
"containmentconfigview{.h,.hh,.h++,.hm,.hpp,.hxx,.in,.txx}"
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.)


-- 
871146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871146
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: plasma-workspace
Version: 4:5.8.7-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
> cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
> "Unix Makefiles" /<> 
> /<>/shell/packageplugins/wallpaperimages 
> /<>/obj-x86_64-linux-gnu 
> /<>/obj-x86_64-linux-gnu/shell/packageplugins/wallpaperimages 
> /<>/obj-x86_64-linux-gnu/shell/packageplugins/wallpaperimages/CMakeFiles/plasma_packagestructure_wallpaperimages_autogen.dir/DependInfo.cmake
>  --color=
> Unknown property type for key "X-KDE-ParentApp" -> falling back to string
> Generated  
> "/<>/obj-x86_64-linux-gnu/shell/packageplugins/shell/plasma-packagestructure-plasma-shell.json"
>  
> 
> [ 80%] Generating plasma-packagestructure-wallpaper.json
> [ 80%] Generating ko-soliduiserver.gmo
> AutoMoc: Warning: 
> "/<>/shell/packageplugins/lookandfeel/lookandfeel.cpp"
> The file includes the moc file "lookandfeel.moc", but does not contain a 
> Q_OBJECT or Q_GADGET macro.
> 
> cd /<>/shell/packageplugins/qmlWallpaper && 
> /usr/bin/desktoptojson -i plasma-packagestructure-wallpaper.desktop -o 
> /<>/obj-x86_64-linux-gnu/shell/packageplugins/qmlWallpaper/plasma-packagestructure-wallpaper.json
> cd /<> && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/ko-soliduiserver.gmo 
> /<>/po/ko/soliduiserver.po
> [ 80%] Generating ko-systemmonitor.gmo
> cd /<> && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/ko-systemmonitor.gmo 
> /<>/po/ko/systemmonitor.po
> Unknown property type for key "X-KDE-ParentApp" -> falling back to string
> Generated  
> "/<>/obj-x86_64-linux-gnu/shell/packageplugins/qmlWallpaper/plasma-packagestructure-wallpaper.json"
>  
> 
> AutoMoc: Error: "/<>/shell/containmentconfigview.cpp"
> The file includes the moc file "private/moc_containmentconfigview.cpp", but 
> could not find header 
> "containmentconfigview{.h,.hh,.h++,.hm,.hpp,.hxx,.in,.txx}"
> 
> shell/CMakeFiles/plasmashell_autogen.dir/build.make:83: recipe for target 
> 'shell/CMakeFiles/plasmashell_autogen' failed
> make[4]: *** [shell/CMakeFiles/plasmashell_autogen] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/plasma-workspace_5.8.7-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: plasma-workspace
Source-Version: 4:5.10.5-1

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

Debian distribution maintenance software
pp.
Maximiliano Curia  (supplier of updated plasma-workspace 
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, 28 Aug 2017 15:29:32 +0200
Source: plasma-workspace
Binary: libkworkspace5-5 libplasma-geolocation-interface5 libtaskmanager6 
libweather-ion7 plasma-workspace plasma-workspace-dev plasma-workspace-wayland 
sddm-theme-breeze sddm-theme-debian-breeze
Architecture: source
Version: 4:5.10.5-1
Distribution: experimental
Urgency: medium
Maintainer: Debian/Ku

Bug#853481: marked as done (libavg: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Mon, 28 Aug 2017 15:12:53 +
with message-id 
and subject line Bug#853481: fixed in libavg 1.8.1-4
has caused the Debian Bug report #853481,
regarding libavg: ftbfs with GCC-7
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.)


-- 
853481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853481
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libavg
Version: 1.8.1-3
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/libavg_1.8.1-3_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
In file included from GLShaderParam.h:31:0,
 from GPUHueSatFilter.h:29,
 from GPUHueSatFilter.cpp:22:
GLShaderParam.h: In member function 'void 
avg::GLShaderParamTemplate::uniformSet(unsigned int, const 
VAL_TYPE&)':
../base/Exception.h:84:87: error: cannot convert 
'std::__cxx11::basic_string' to 'const char*' for argument '4' to 'void 
avg::avgAssert(bool, const char*, int, const char*)'
 #define AVG_ASSERT_MSG(b, pszReason) avgAssert((b) != 0, __FILE__, __LINE__, 
pszReason);

   ^
GLShaderParam.h:81:9: note: in expansion of macro 'AVG_ASSERT_MSG'
 AVG_ASSERT_MSG(false,
 ^~
In file included from GLShaderParam.h:31:0,
 from OGLShader.h:27,
 from StandardShader.h:27,
 from StandardShader.cpp:22:
GLShaderParam.h: In member function 'void 
avg::GLShaderParamTemplate::uniformSet(unsigned int, const 
VAL_TYPE&)':
../base/Exception.h:84:87: error: cannot convert 
'std::__cxx11::basic_string' to 'const char*' for argument '4' to 'void 
avg::avgAssert(bool, const char*, int, const char*)'
 #define AVG_ASSERT_MSG(b, pszReason) avgAssert((b) != 0, __FILE__, __LINE__, 
pszReason);

   ^
GLShaderParam.h:81:9: note: in expansion of macro 'AVG_ASSERT_MSG'
 AVG_ASSERT_MSG(false,
 ^~
Makefile:1031: recipe for target 'GPUInvertFilter.lo' failed
make[5]: *** [GPUInvertFilter.lo] Error 1
Makefile:1031: recipe for target 'OGLShader.lo' failed
make[5]: *** [OGLShader.lo] Error 1
Makefile:1031: recipe for target 'ShaderRegistry.lo' failed
make[5]: *** [ShaderRegistry.lo] Error 1
Makefile:1031: recipe for target 'GLContext.lo' failed
make[5]: *** [GLContext.lo] Error 1
Makefile:1031: recipe for target 'GPUHueSatFilter.lo' failed
make[5]: *** [GPUHueSatFilter.lo] Error 1
Makefile:1031: recipe for target 'StandardShader.lo' failed
make[5]: *** [StandardShader.lo] Error 1
make[5]: Leaving directory '/<>/src/graphics'
Makefile:1046: recipe for target 'all-recursive' failed
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory '/<>/src/graphics'
Makefile:453: recipe for target 'all-recursive' failed
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory '/<>/src'
Makefile:392: recipe for target 'all' failed
make[2]: *** [all] Error 2
make[2]: Leaving directory '/<>/src'
Makefile:460: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/<>'
dh_auto_build: make -j64 returned exit code 2
debian/rules:4: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---
Source: libavg
Source-Version: 1.8.1-4

We believe that th

Bug#873512: statsmodels FTBFS with Cython 0.26

[Adrian Bunk]

Source: statsmodels
Version: 0.8.0-3
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/statsmodels.html

...
==
ERROR: statsmodels.tsa.statespace.tests.test_save.test_sarimax
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File 
"/build/1st/statsmodels-0.8.0/debian/python-statsmodels/usr/lib/python2.7/dist-packages/statsmodels/tsa/statespace/tests/test_save.py",
 line 22, in test_sarimax
res.save('test_save_sarimax.p')
  File 
"/build/1st/statsmodels-0.8.0/debian/python-statsmodels/usr/lib/python2.7/dist-packages/statsmodels/base/wrapper.py",
 line 72, in save
save_pickle(self, fname)
  File 
"/build/1st/statsmodels-0.8.0/debian/python-statsmodels/usr/lib/python2.7/dist-packages/statsmodels/iolib/smpickle.py",
 line 15, in save_pickle
cPickle.dump(obj, fout, protocol=-1)
  File "stringsource", line 2, in 
statsmodels.tsa.statespace._statespace.zStatespace.__reduce_cython__
TypeError: 
self._design,self._initial_state,self._initial_state_cov,self._obs,self._obs_cov,self._obs_intercept,self._selected_state_cov,self._selection,self._state_cov,self._state_intercept,self._transition
 cannot be converted to a Python object for pickling

==
ERROR: statsmodels.tsa.statespace.tests.test_save.test_structural
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File 
"/build/1st/statsmodels-0.8.0/debian/python-statsmodels/usr/lib/python2.7/dist-packages/statsmodels/tsa/statespace/tests/test_save.py",
 line 35, in test_structural
res.save('test_save_structural.p')
  File 
"/build/1st/statsmodels-0.8.0/debian/python-statsmodels/usr/lib/python2.7/dist-packages/statsmodels/base/wrapper.py",
 line 72, in save
save_pickle(self, fname)
  File 
"/build/1st/statsmodels-0.8.0/debian/python-statsmodels/usr/lib/python2.7/dist-packages/statsmodels/iolib/smpickle.py",
 line 15, in save_pickle
cPickle.dump(obj, fout, protocol=-1)
  File "stringsource", line 2, in 
statsmodels.tsa.statespace._statespace.zStatespace.__reduce_cython__
TypeError: 
self._design,self._initial_state,self._initial_state_cov,self._obs,self._obs_cov,self._obs_intercept,self._selected_state_cov,self._selection,self._state_cov,self._state_intercept,self._transition
 cannot be converted to a Python object for pickling

==
ERROR: statsmodels.tsa.statespace.tests.test_save.test_dynamic_factor
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File 
"/build/1st/statsmodels-0.8.0/debian/python-statsmodels/usr/lib/python2.7/dist-packages/statsmodels/tsa/statespace/tests/test_save.py",
 line 50, in test_dynamic_factor
res.save('test_save_dynamic_factor.p')
  File 
"/build/1st/statsmodels-0.8.0/debian/python-statsmodels/usr/lib/python2.7/dist-packages/statsmodels/base/wrapper.py",
 line 72, in save
save_pickle(self, fname)
  File 
"/build/1st/statsmodels-0.8.0/debian/python-statsmodels/usr/lib/python2.7/dist-packages/statsmodels/iolib/smpickle.py",
 line 15, in save_pickle
cPickle.dump(obj, fout, protocol=-1)
  File "stringsource", line 2, in 
statsmodels.tsa.statespace._statespace.zStatespace.__reduce_cython__
TypeError: 
self._design,self._initial_state,self._initial_state_cov,self._obs,self._obs_cov,self._obs_intercept,self._selected_state_cov,self._selection,self._state_cov,self._state_intercept,self._transition
 cannot be converted to a Python object for pickling

==
ERROR: statsmodels.tsa.statespace.tests.test_save.test_varmax
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File 
"/build/1st/statsmodels-0.8.0/debian/python-statsmodels/usr/lib/python2.7/dist-packages/statsmodels/tsa/statespace/tests/test_save.py",
 line 65, in test_varmax
res.save('test_save_varmax.p')
  File 
"/build/1st/statsmodels-0.8.0/debian/python-statsmodels/usr/lib/python2.7/dist-packages/statsmodels/base/wrapper.py",
 line 72, in save
save_pickle(self, fname)
  File 
"/build/1st/statsmodels-0.8.0/debian/python-statsmodels/usr/lib/python2.7/dist-packages/statsmodels/iolib/smpickle.py",
 line 15, in save_pickle
cPickle.dump(obj, fout, protocol=-1)
  File "stringsource", line 2, in 
statsmodels.tsa.statespace._sta

Bug#873511: yt FTBFS with Cython 0.26

[Adrian Bunk]

Source: yt
Version: 3.3.3-2
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/yt.html

...
[26/44] Cythonizing yt/utilities/lib/origami.pyx
[27/44] Cythonizing yt/utilities/lib/particle_mesh_operations.pyx
Traceback (most recent call last):
  File "setup.py", line 374, in 
ext_modules=cython_extensions + extensions,
  File "/usr/lib/python2.7/distutils/core.py", line 151, in setup
dist.run_commands()
  File "/usr/lib/python2.7/distutils/dist.py", line 953, in run_commands
self.run_command(cmd)
  File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
cmd_obj.run()
  File "/usr/lib/python2.7/distutils/command/build.py", line 128, in run
self.run_command(cmd_name)
  File "/usr/lib/python2.7/distutils/cmd.py", line 326, in run_command
self.distribution.run_command(command)
  File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
cmd_obj.run()
  File "setup.py", line 296, in run
_build_py.run(self)
  File "/usr/lib/python2.7/dist-packages/setuptools/command/build_py.py", line 
53, in run
self.build_package_data()
  File "/usr/lib/python2.7/dist-packages/setuptools/command/build_py.py", line 
118, in build_package_data
for package, src_dir, build_dir, filenames in self.data_files:
  File "/usr/lib/python2.7/dist-packages/setuptools/command/build_py.py", line 
66, in __getattr__
self.data_files = self._get_data_files()
  File "/usr/lib/python2.7/dist-packages/setuptools/command/build_py.py", line 
82, in _get_data_files
self.analyze_manifest()
  File "/usr/lib/python2.7/dist-packages/setuptools/command/build_py.py", line 
138, in analyze_manifest
self.run_command('egg_info')
  File "/usr/lib/python2.7/distutils/cmd.py", line 326, in run_command
self.distribution.run_command(command)
  File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
cmd_obj.run()
  File "/usr/lib/python2.7/dist-packages/setuptools/command/egg_info.py", line 
280, in run
self.find_sources()
  File "/usr/lib/python2.7/dist-packages/setuptools/command/egg_info.py", line 
295, in find_sources
mm.run()
  File "/usr/lib/python2.7/dist-packages/setuptools/command/egg_info.py", line 
526, in run
self.add_defaults()
  File "/usr/lib/python2.7/dist-packages/setuptools/command/egg_info.py", line 
562, in add_defaults
sdist.add_defaults(self)
  File "/usr/lib/python2.7/dist-packages/setuptools/command/py36compat.py", 
line 36, in add_defaults
self._add_defaults_ext()
  File "/usr/lib/python2.7/dist-packages/setuptools/command/py36compat.py", 
line 119, in _add_defaults_ext
build_ext = self.get_finalized_command('build_ext')
  File "/usr/lib/python2.7/distutils/cmd.py", line 312, in get_finalized_command
cmd_obj.ensure_finalized()
  File "/usr/lib/python2.7/distutils/cmd.py", line 109, in ensure_finalized
self.finalize_options()
  File "setup.py", line 304, in finalize_options
self.distribution.ext_modules)
  File "/usr/lib/python2.7/dist-packages/Cython/Build/Dependencies.py", line 
1016, in cythonize
cythonize_one(*args)
  File "/usr/lib/python2.7/dist-packages/Cython/Build/Dependencies.py", line 
1138, in cythonize_one
raise CompileError(None, pyx_file)
Cython.Compiler.Errors.CompileError: 
yt/utilities/lib/particle_mesh_operations.pyx
E: pybuild pybuild:283: build: plugin distutils failed with: exit code=1: 
/usr/bin/python setup.py build 
dh_auto_build: pybuild --build --test-nose -i python{version} -p 2.7 returned 
exit code 13
debian/rules:8: recipe for target 'build' failed
make: *** [build] Error 25

Processed: Re: Bug#873508: parsing horst source code fails on s390x and ppc64el

[Debian Bug Tracking System]

Processing control commands:

> severity 873508 serious
Bug #873508 [src:sparse] parsing horst source code fails on s390x and ppc64el
Severity set to 'serious' from 'important'
> affects 873508 horst
Bug #873508 [src:sparse] parsing horst source code fails on s390x and ppc64el
Added indication that 873508 affects horst

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

Bug#873509: python-admesh FTBFS with Cython 0.26

[Adrian Bunk]

Source: python-admesh
Version: 0.98.7-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-admesh.html

...
   dh_auto_build -O--buildsystem=pybuild
I: pybuild base:184: /usr/bin/python setup.py build 
running build
running build_ext
generating cadmesh.pxd and admesh.pyx
found /usr/include/admesh/stl.h
cythoning admesh.pyx to admesh.c

Error compiling Cython file:

...

def write_edge(self, edge, label='admesh'):
"""stl_write_edge"""

by_label = label.encode('UTF-8')
stl_write_edge(&self._c_stl_file, by_label, edge)
   ^


admesh.pyx:224:56: Cannot convert Python object to 'stl_hash_edge'
building 'admesh' extension
creating build
creating build/temp.linux-amd64-2.7
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-fno-strict-aliasing -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/usr/include/python2.7 -c admesh.c -o build/temp.linux-amd64-2.7/admesh.o
admesh.c:1:2: error: #error Do not use this file, it is the result of a failed 
Cython compilation.
 #error Do not use this file, it is the result of a failed Cython compilation.
  ^
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
E: pybuild pybuild:283: build: plugin distutils failed with: exit code=1: 
/usr/bin/python setup.py build 
dh_auto_build: pybuild --build -i python{version} -p 2.7 returned exit code 13
debian/rules:6: recipe for target 'build' failed
make: *** [build] Error 25

Processed: reopening 861333

[Debian Bug Tracking System]

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

> # Incorrectly closed in r-cran-randomfields/3.1.50-1
> reopen 861333
Bug #861333 {Done: Andreas Tille } [r-base] r-base: R 
packages uploaded to Debian before 14 April 2017 that use .C or .Fortran fail 
to find objects
Bug #861684 {Done: Andreas Tille } [r-base] 
r-cran-randomfields: FTBFS against r-base 3.4.0-1
Bug #862969 {Done: Andreas Tille } [r-base] r-cran-sp needs 
recompilation for R 3.4.0 ?
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions r-cran-randomfields/3.1.50-1.
No longer marked as fixed in versions r-cran-randomfields/3.1.50-1.
No longer marked as fixed in versions r-cran-randomfields/3.1.50-1.
> thanks
Stopping processing here.

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

Bug#873505: mailman: Runner crashes when processing incoming email

[Pete Donnell]

Package: mailman
Version: 1:2.1.23-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Mailman was installed following these instructions under Debian Jessie:
https://alephnull.uk/howto-mailman-debian-jessie-apache-postfix-spamassassin-virtualhost

All worked well. The server was upgraded to Debian Stretch a couple of weeks 
ago,
and since then no messages have got through to the mailing lists. No errors or 
bounceback
messages are generated. I only became aware of the problem when users 
complained that
their lists weren't working anymore. The only evidence I've found is this 
snippet from
/var/log/mailman/error:

Aug 21 21:38:32 2017 (1405) Uncaught runner exception: cannot import name 
matches_p
Aug 21 21:38:32 2017 (1405) Traceback (most recent call last):
  File "/var/lib/mailman/Mailman/Queue/Runner.py", line 119, in _oneloop
self._onefile(msg, msgdata)
  File "/var/lib/mailman/Mailman/Queue/Runner.py", line 190, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
  File "/var/lib/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose
more = self._dopipeline(mlist, msg, msgdata, pipeline)
  File "/var/lib/mailman/Mailman/Queue/IncomingRunner.py", line 150, in 
_dopipeline
__import__(modname)
  File "/var/lib/mailman/Mailman/Handlers/SpamAssassin.py", line 31, in 
from Mailman.Handlers.Moderate import matches_p
ImportError: cannot import name matches_p

I've searched the internet for people reporting the same problem and not come 
across
anything. Without a better knowledge of the internals of Mailman I can't debug 
it
further myself.

Thanks,
Pete

-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages mailman depends on:
ii  apache2 [httpd]2.4.25-3+deb9u2
ii  cron [cron-daemon] 3.0pl1-128+b1
ii  debconf [debconf-2.0]  1.5.61
ii  libc6  2.24-11+deb9u1
ii  logrotate  3.11.0-0.1
ii  lsb-base   9.20161125
ii  python 2.7.13-2
ii  python-dnspython   1.15.0-1
ii  ucf3.0036

Versions of packages mailman recommends:
ii  postfix [mail-transport-agent]  3.1.4-7

Versions of packages mailman suggests:
pn  listadmin 
ii  lynx  2.8.9dev11-1
ii  spamassassin  3.4.1-6

-- debconf information:
* mailman/site_languages: en
  mailman/queue_files_present: abort installation
* mailman/create_site_list:
* mailman/used_languages: en
* mailman/default_server_language: en

Bug#853677: marked as done (t-coffee: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Mon, 28 Aug 2017 13:51:48 +
with message-id 
and subject line Bug#853677: fixed in t-coffee 11.00.8cbe486-6
has caused the Debian Bug report #853677,
regarding t-coffee: ftbfs with GCC-7
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.)


-- 
853677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853677
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:t-coffee
Version: 11.00.8cbe486-5
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/t-coffee_11.00.8cbe486-5_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
In file included from /usr/include/stdio.h:938:0,
 from util_lib/util_constraints_list.c:29:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:34:43: note: format output between 
6 and 4503 bytes into a destination of size 1000
   __bos (__s), __fmt, __va_arg_pack ());
   ^
util_lib/util_constraints_list.c:611:9: warning: '%s' directive writing between 
0 and 500 bytes into a region of size 100 [-Wformat-overflow=]
 Job_TC* method2job_list ( char *method_name,Sequence *S, char *weight, char 
*lib_list, Distance_matrix *DM, Constraint_list *CL)
 ^~~
In file included from /usr/include/stdio.h:938:0,
 from util_lib/util_constraints_list.c:29:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:34:43: note: format output between 
1 and 501 bytes into a destination of size 100
   __bos (__s), __fmt, __va_arg_pack ());
   ^
util_lib/util_constraints_list.c:611:9: warning: '%s' directive writing between 
0 and 500 bytes into a region of size 100 [-Wformat-overflow=]
 Job_TC* method2job_list ( char *method_name,Sequence *S, char *weight, char 
*lib_list, Distance_matrix *DM, Constraint_list *CL)
 ^~~
In file included from /usr/include/stdio.h:938:0,
 from util_lib/util_constraints_list.c:29:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:34:43: note: format output between 
1 and 501 bytes into a destination of size 100
   __bos (__s), __fmt, __va_arg_pack ());
   ^
util_lib/util_constraints_list.c:611:9: warning: '%s' directive writing between 
0 and 999 bytes into a region of size 499 [-Wformat-overflow=]
 Job_TC* method2job_list ( char *method_name,Sequence *S, char *weight, char 
*lib_list, Distance_matrix *DM, Constraint_list *CL)
 ^~~
In file included from /usr/include/stdio.h:938:0,
 from util_lib/util_constraints_list.c:29:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:34:43: note: format output between 
6 and 4503 bytes into a destination of size 1000
   __bos (__s), __fmt, __va_arg_pack ());
   ^
 Linking...
g++: error: util_lib/aln_convertion_util.o: No such file or directory
g++: error: util_lib/util.o: No such file or directory
makefile:8: recipe for target 't_coffee' failed
make[2]: [t_coffee] Error 1 (ignored)
make[2]: Leaving directory '/<>/t_coffee_source'
make[1]: Leaving directory '/<>'
   dh_auto_test -O--sourcedirectory=t_coffee_source
   create-stamp debian/debhelper-build-stamp
 fakeroot debian/rules binary
dh binary --sourcedirectory=t_coffee_source
   dh_testroot -O--sourcedirectory=t_coffee_source
   dh_prep -O--sourcedirectory=t_coffee_source
   dh_auto_install -O--sourcedirectory=t_coffee_source
   dh_install -O--sourcedirectory=t_coffee_source

Bug#872406: marked as done (baresip FTBFS: error: storage size of 'timeout' isn't known)

[Debian Bug Tracking System]

Your message dated Mon, 28 Aug 2017 13:34:55 +
with message-id 
and subject line Bug#872406: fixed in baresip 0.5.4-1.1
has caused the Debian Bug report #872406,
regarding baresip FTBFS: error: storage size of 'timeout' isn't known
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.)


-- 
872406: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872406
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: baresip
Version: 0.5.4-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=baresip&arch=amd64&ver=0.5.4-1%2Bb2&stamp=1502875243&raw=0

...
gcc -DRELEASE -Wall -Wmissing-declarations -Wmissing-prototypes 
-Wstrict-prototypes -Wbad-function-cast -Wsign-compare -Wnested-externs 
-Wshadow -Waggregate-return -Wcast-align -g -O3   -Wuninitialized 
-Wno-strict-aliasing -fPIC -DLINUX -DOS=\"linux\" -std=c99 -pedantic 
-DARCH=\"x86_64\" -DUSE_OPENSSL -DUSE_TLS -DUSE_OPENSSL_DTLS -DUSE_DTLS 
-DUSE_OPENSSL_SRTP -DUSE_DTLS_SRTP -DUSE_ZLIB -DHAVE_PTHREAD -DHAVE_GETIFADDRS 
-DHAVE_STRERROR_R -DHAVE_GETOPT -DHAVE_INTTYPES_H -DHAVE_NET_ROUTE_H 
-DHAVE_SYS_SYSCTL_H -DHAVE_STDBOOL_H -DHAVE_INET6 -DHAVE_RESOLV -DHAVE_SYSLOG 
-DHAVE_FORK -DHAVE_INET_NTOP -DHAVE_PWD_H -DHAVE_POLL   -DHAVE_INET_PTON 
-DHAVE_SELECT -DHAVE_SELECT_H -DHAVE_SETRLIMIT -DHAVE_SIGNAL -DHAVE_SYS_TIME_H 
-DHAVE_EPOLL -DHAVE_UNAME -DHAVE_UNISTD_H -DHAVE_STRINGS_H -DHAVE_GAI_STRERROR 
-DVERSION=\"0.5.4\" -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -I. -Iinclude -I/usr/include/re -I/usr/inclu
 de -I/include -I/usr/local/include/rem -I/usr/include/rem -DUSE_VIDEO=1 
-DMODULE_CONF -DPREFIX=\"/usr\" -DUSE_AVCODEC -DUSE_AVFORMAT -D_REENTRANT 
-isystem/usr/include/directfb \
-c modules/directfb/directfb.c -o 
build-x86_64/modules/directfb/directfb.o -MD -MF 
build-x86_64/modules/directfb/directfb.d -MT 
build-x86_64/modules/directfb/directfb.o
In file included from /usr/include/directfb/direct/os/types.h:63:0,
 from /usr/include/directfb/direct/os/waitqueue.h:36,
 from /usr/include/directfb/direct/thread.h:38,
 from /usr/include/directfb/direct/debug.h:43,
 from /usr/include/directfb/direct/interface.h:36,
 from /usr/include/directfb/directfb.h:49,
 from modules/directfb/directfb.c:10:
/usr/include/directfb/direct/os/linux/glibc/waitqueue.h: In function 
'direct_waitqueue_wait_timeout':
/usr/include/directfb/direct/os/linux/glibc/waitqueue.h:76:22: error: storage 
size of 'timeout' isn't known
  struct timespec timeout;
  ^~~
mk/mod.mk:42: recipe for target 'build-x86_64/modules/directfb/directfb.o' 
failed
make[1]: *** [build-x86_64/modules/directfb/directfb.o] Error 1



/usr/include/directfb/direct/os/linux/glibc/waitqueue.h
needs the definition of struct timespec visible.

The strict mode -std=c99 set by /usr/share/re/re.mk
makes this definition not available by default.

Possible solutions:
- in re.mk, remove -std=c99 or make it -std=gnu99, or
- in re.mk, add -D_GNU_SOURCE (it already does that for kfreebsd), or
- in baresip, append one of -std=gnu99/-std=gnu11/-D_GNU_SOURCE
--- End Message ---
--- Begin Message ---
Source: baresip
Source-Version: 0.5.4-1.1

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated baresip 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: Sat, 26 Aug 2017 11:41:57 +0200
Source: baresip
Binary: baresip baresip-core baresip-gtk baresip-ffmpeg baresip-gstreamer 
baresip-x11
Architecture: source
Version: 0.5.4-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian VoIP Team 
Changed-By: Sebastian Ramacher 
Description:
 baresip- portable and modular SIP user-agent - metapackage
 baresip-core - portable and modular SIP user-agent - core parts
 baresip-ffmpeg - portable and modular SIP user-agent - FFmpeg codecs and 
forma

Processed: Re: Bug#873484: astroid: Crash at start

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/astroidmail/astroid/issues/63
Bug #873484 [astroidmail] astroid: Crash at start
Set Bug forwarded-to-address to 
'https://github.com/astroidmail/astroid/issues/63'.

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

Bug#873484: astroid: Crash at start

[Jonas Smedegaard]

control: forwarded -1 https://github.com/astroidmail/astroid/issues/63

control: reassign 873248 src:astroid

Hi Jean-Luc,

> I've just installed astroid.

That was quick: Package was barely accepted into experimental :-)


> At start, I get the following:
[...]
>  what():  /home/jean-luc/.notmuch-config: cannot open file
> [1]19045 abort  astroid

This is an issue known upstream: For now, you need a working notmuch 
_before_ starting Astroid.

More info at https://github.com/astroidmail/astroid/issues/63


> Whe I tried to report the bug, I got the following from reportbug:
[...]
Your version (0.9.1-1) of astroid appears to be out of date.
[...]
I use sid and I've not found any newer version…

That is indeed quite confusing.  Our bug tracker is not good at 
distinguishing properly between names of source packages and binary 
packages of the same name.  More info at https://bugs.debian.org/873248 
- which itself got filed against the wrong package :-/


Thanks for helping test Astroid!

 - Jonas

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

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

Bug#872228: marked as done (libclj-tuple-clojure: broken symlinks: /usr/share/maven-repo/clj-tuple/clj-tuple/*/clj-tuple-*.jar -> ../../../../java/core.cache.jar)

[Debian Bug Tracking System]

Your message dated Mon, 28 Aug 2017 13:19:18 +
with message-id 
and subject line Bug#872228: fixed in clj-tuple-clojure 0.2.2-2
has caused the Debian Bug report #872228,
regarding libclj-tuple-clojure: broken symlinks: 
/usr/share/maven-repo/clj-tuple/clj-tuple/*/clj-tuple-*.jar -> 
../../../../java/core.cache.jar
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.)


-- 
872228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872228
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libclj-tuple-clojure
Version: 0.2.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m22.2s ERROR: FAIL: Broken symlinks:
  /usr/share/maven-repo/clj-tuple/clj-tuple/debian/clj-tuple-debian.jar -> 
../../../../java/core.cache.jar
  /usr/share/maven-repo/clj-tuple/clj-tuple/0.2.2/clj-tuple-0.2.2.jar -> 
../../../../java/core.cache.jar

Is libclj-tuple-clojure missing a Depends: libcore-cache-clojure ?


cheers,

Andreas


libclj-tuple-clojure_0.2.2-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: clj-tuple-clojure
Source-Version: 0.2.2-2

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

Debian distribution maintenance software
pp.
Apollon Oikonomopoulos  (supplier of updated 
clj-tuple-clojure 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, 28 Aug 2017 13:13:39 +0300
Source: clj-tuple-clojure
Binary: libclj-tuple-clojure
Architecture: source all
Version: 0.2.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Apollon Oikonomopoulos 
Description:
 libclj-tuple-clojure - efficient implementations for small maps and vectors in 
Clojure
Closes: 872228
Changes:
 clj-tuple-clojure (0.2.2-2) unstable; urgency=medium
 .
   * Point maven repo links to the correct jar (Closes: #872228)
Checksums-Sha1:
 77c726fcd7c21fbec420921e7cc5fb06b336e0e6 2144 clj-tuple-clojure_0.2.2-2.dsc
 699fd9f7dc08af0084ee812598f4c81b15bcba21 3456 
clj-tuple-clojure_0.2.2-2.debian.tar.xz
 30246a3fc4dd67f2665670afd63ee7cc7b33fcd7 10841 
clj-tuple-clojure_0.2.2-2_amd64.buildinfo
 c159e75ce2a3cc7c9c72296cef72b71797b83ed7 78118 
libclj-tuple-clojure_0.2.2-2_all.deb
Checksums-Sha256:
 a27bb9170cd41e06c8a74b339e2c3d2b237d0cb4bbe698699981256fbbd89d78 2144 
clj-tuple-clojure_0.2.2-2.dsc
 8e6e063abd34161e25eb3edce510aae3417b69fa6a292278c4109a4370bd762d 3456 
clj-tuple-clojure_0.2.2-2.debian.tar.xz
 fdf16e25bdd3784088231b3b45c307deae10d799a1baf3bd5eed840606358c50 10841 
clj-tuple-clojure_0.2.2-2_amd64.buildinfo
 76c38fc539e70c725e0d0bd984979050d62fd6298e37b46d3b1269ddadcd77e0 78118 
libclj-tuple-clojure_0.2.2-2_all.deb
Files:
 89e34f61e8badb547af4385f46dbc7c5 2144 java optional 
clj-tuple-clojure_0.2.2-2.dsc
 1a9ee9bd4a1de80a278ccfd93fbfba44 3456 java optional 
clj-tuple-clojure_0.2.2-2.debian.tar.xz
 7c789843821fb414eece1f174ff7741e 10841 java optional 
clj-tuple-clojure_0.2.2-2_amd64.buildinfo
 76685c1f311df2a2b2ebda45a6778a09 78118 java optional 
libclj-tuple-clojure_0.2.2-2_all.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEPgL9ZlYpWVIRC6uZ9RsYxyAkgiQFAlmj7YcACgkQ9RsYxyAk
giTVPA/9HsmG31A6/eg5+c2AuQW1pwvB4s6qJYJ3y0XLbe1QExnvAv4r0CKo8eSN
GbS/3vqUEIZLaJPwIisLQB0tvUqTvpf9znabikxMPUrjKWOwUUfntFUsPpPtzJHZ
k/VVKlzh9eKtaZ9LQjoevxUAG4IBm/ynYT9tD+XXyczmLs+z0WquSG9GIKJRiMEQ
+mGd3fegY85hIy+5aTCMUKlF1WI33UyljG9AT8vmjtzkRdsIL4BfdY7hmNGUdnSc
WoeMrEZDQXbK53ggS7AD/tFGpWvRV/mM5EgLasE/YoBM2+0p0cvWOKShzGtou/a+
A3WUypwkBKqwwCFudYDUDKmrsV2BhU5XGifeD1fPV2WR1q5xhCSHOKAQAqj5wlDq
8f+lZ1rpW5C2t6JOpwlW2DrZbTu0HoZeqdi8V7erBDzasnCNNoSFGuV3o9Brja2c
+V/rAnDlEAH9xNqAU/iiGsJTrdDXEjQ99EBq0JZzj4FUc+29oyTcYWuRa98sGzfl
L2LRU2kNv8owEnKy4AXzyI1zaWfEl30j5QbccrWhfu/bBerK/3HwzlxsrLnjEGIL
XF5NzdcfPUkEb4XHCoiKkzYQYA6eeRFwQIj1bxAqWyZLVIc9/+B2qo+/hoyGpXWt
ClSMxNEiMcAS6IBI8tJSFKDWVMNBtP0hclRgI5gZBltUzg6mosQ=
=+nDx
-END PGP SIGNATURE En

Processed: Re: Bug#794466: Virtualbox might not be suitable for Stretch

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 virtualbox: might not be suitable for stable releases due to lack 
> of cooperation from upstream on security support for older releases
Bug #794466 [src:virtualbox] Virtualbox might not be suitable for Stretch
Changed Bug title to 'virtualbox: might not be suitable for stable releases due 
to lack of cooperation from upstream on security support for older releases' 
from 'Virtualbox might not be suitable for Stretch'.
> severity -1 important
Bug #794466 [src:virtualbox] virtualbox: might not be suitable for stable 
releases due to lack of cooperation from upstream on security support for older 
releases
Severity set to 'important' from 'serious'

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

Bug#794466: Virtualbox might not be suitable for Stretch

[Lucas Nussbaum]

Control: retitle -1 virtualbox: might not be suitable for stable releases due 
to lack of cooperation from upstream on security support for older releases
Control: severity -1 important

Hi,

After a private discussion with Gianfranco, I'm retitling this bug and
downgrading its severity. (Gianfranco agrees, at least on the general
lines of argumentation).

The reasoning is as follows.

Virtualbox did not make it into stretch due to this bug, for good
reasons.

We are at the start of the buster release cycle, and we don't know what
will be the status at the time of the freeze. The situation around
security support should be re-evaluated at the beginning of the buster
freeze, but until then, it sounds like a better plan to maximize user
testing and allow virtualbox to migrate to testing.

Security support for unstable/testing is not a problem because we are
tracking new upstream releases anyway, where issues are being addressed
by upstream. Also, there's a public svn repository to get fixes from if
necessary.

Cheers,

Lucas

Processed: retitle 873443 to terminate called after throwing an instance of com::sun::star::uno::DeploymentException on architectures not using libmergedlo.so

[Debian Bug Tracking System]

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

> retitle 873443 terminate called after throwing an instance of 
> com::sun::star::uno::DeploymentException on architectures not using 
> libmergedlo.so
Bug #873443 [uno-libs3] terminate called after throwing an instance of 
com::sun::star::uno::DeploymentException
Changed Bug title to 'terminate called after throwing an instance of 
com::sun::star::uno::DeploymentException on architectures not using 
libmergedlo.so' from 'terminate called after throwing an instance of 
com::sun::star::uno::DeploymentException'.
> thanks
Stopping processing here.

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

Processed: gcc-7: miscompiles stack spills on mips64el

[Debian Bug Tracking System]

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

> affects 871514 src:openorienteering-mapper
Bug #871514 [gcc-7] gcc-7: miscompiles stack spills on mips64el
Bug #871538 [gcc-7] gcc-7: miscompiles stack spills on mips64el
Bug #872438 [gcc-7] gcc-7: miscompiles stack spills on mips64el
Bug #872987 [gcc-7] gcc-7: miscompiles stack spills on mips64el
Added indication that 871514 affects src:openorienteering-mapper
Added indication that 871538 affects src:openorienteering-mapper
Added indication that 872438 affects src:openorienteering-mapper
Added indication that 872987 affects src:openorienteering-mapper
> thanks
Stopping processing here.

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

Bug#872378: fenrir.deb: No speech after enabling fenrir to start inconcial.

[Matthew Dyer]

On 08/19/17 09:18, Samuel Thibault wrote:

matthew dyer, on sam. 19 août 2017 09:01:15 -0400, wrote:

This was a fresh install of Fenrir from the deian uunstable repo.  I simply
disabled espeakup from starting  and enabled Fenrir to start and rebooted the
system and got no speech in the conciel.  HTH.

Could you try to downgrade to version 1.05-1 so as to check whether it's
only version 1.06-1 which has the issue?

Samuel

Hi,

First off, sorry for taking so long to responding .  Some how your reply 
went to my spam folder.  Anyhow,  went trying to downgrade, I got the 
package not found erroor.  Am I doing something wrong?  I did sudo 
apt-get install fenrir 1.05.  Should I have done something else.Again 
sorry for the delay.


Matthew



___
Pkg-a11y-devel mailing list
pkg-a11y-de...@lists.alioth.debian.org
https://lists.alioth.debian.org/mailman/listinfo/pkg-a11y-devel

Processed: Pending fixes for bugs in the clj-tuple-clojure package

[Debian Bug Tracking System]

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

> tag 872228 + pending
Bug #872228 [libclj-tuple-clojure] libclj-tuple-clojure: broken symlinks: 
/usr/share/maven-repo/clj-tuple/clj-tuple/*/clj-tuple-*.jar -> 
../../../../java/core.cache.jar
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Also reopen

[Debian Bug Tracking System]

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

> reopen 789927
Bug #789927 {Done: NIIBE Yutaka } [libanthyinput0] 
libanthyinput0: fails to upgrade from 'sid' - trying to overwrite 
/usr/lib/x86_64-linux-gnu/libanthyinput.so.0.0.0'
Bug reopened
Ignoring request to alter fixed versions of bug #789927 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#872228: Pending fixes for bugs in the clj-tuple-clojure package

[pkg-java-maintainers]

tag 872228 + pending
thanks

Some bugs in the clj-tuple-clojure package are closed in revision
05dfe761e8ff3097383bbb32a5e8c346e68691f5 in branch 'master' by
Apollon Oikonomopoulos

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/clj-tuple-clojure.git/commit/?id=05dfe76

Commit message:

Point maven repo links to the correct jar

Closes: #872228

Processed: Re: Bug#873484: astroid: Crash at start

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 astroidmail
Bug #873484 [astroid] astroid: Crash at start
Bug reassigned from package 'astroid' to 'astroidmail'.
No longer marked as found in versions astroidmail/0.9.1-1.
Ignoring request to alter fixed versions of bug #873484 to the same values 
previously set

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

Bug#873362: coinor-libcoinutils3v5: unannounced ABI change without SONAME change?

[Mattia Rizzolo]

On Sun, 27 Aug 2017, 8:37 p.m. Anton Gladky  wrote:

> Hi Mattia,
>
> thanks for the tip! I have recompiled both libs with the same
> current gcc-7.2. And it looks like there are no dropped symbols
> (see file old-gcc7_new-gcc7.diff in attachment).
>
> But if I compare new so-file with the one shipped with Stretch
> (compiled with gcc6)
> the diff contains some missing symbols (see file  old-gcc6_new-gcc7.diff).
>

Oh!  That's interesting...

What is the best practice for such kind of libs? Provide symbol-files?
>

Not sure.  I'd suggest to try to ask to -mentors@ or -devel@, or perhaps to
James Cowgirl (CCed now) who helped with gcc-7 related stuff :)

Thank you
>
> PS I have generated the symbols with the command:
>   readelf -Ws libCoinUtils.so |  awk '{print $8}'
>

Tbh, in general I'd use dpkg-gensymbols, but well, I think it's the same.

Bug#873484: astroid: Crash at start

[Sandro Tosi]

control: reassign -1 astroidmail

On Mon, Aug 28, 2017 at 5:23 AM, Jean-Luc Coulon (f5ibh)
 wrote:
> Package: astroid
> Version: 0.9.1-1
> Severity: grave
> Justification: renders package unusable
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi,
>
> I've just installed astroid.
> At start, I get the following:
>
> astroid
> [11:17:55.594602] [0x7efd0669cfc0] [info] welcome to astroid! - 0.9.1-1
> [11:17:55.594722] [0x7efd0669cfc0] [debug] utf8: true, UTF-8
> [...]
>
> (astroid:19045): Gtk-WARNING **: Theme parsing error: gtk.css:4190:73: Using 
> one color stop with linear-gradient() is deprecated.
> [11:17:55.626727] [0x7efd0669cfc0] [debug] HOME: /home/jean-luc
> [11:17:55.626774] [0x7efd0669cfc0] [info] cf: loading: 
> "/home/jean-luc/.config/astroid/config"
> [11:17:55.626827] [0x7efd0669cfc0] [warning] cf: making config dir..
> [11:17:55.626899] [0x7efd0669cfc0] [warning] cf: making runtime dir..
> [11:17:55.626947] [0x7efd0669cfc0] [warning] cf: no config, using 
> defaults.
> [11:17:55.627533] [0x7efd0669cfc0] [warning] cf: writing back config to: 
> "/home/jean-luc/.config/astroid/config"
> terminate called after throwing an instance of 
> 'boost::exception_detail::clone_impl
>  >'
>   what():  /home/jean-luc/.notmuch-config: cannot open file
> [1]19045 abort  astroid
>
> Whe I tried to report the bug, I got the following from reportbug:
>
> Getting status for astroid...
> Checking for newer versions at madison, incoming.debian.org and 
> http://ftp-master.debian.org/new.html
>
> Your version (0.9.1-1) of astroid appears to be out of date.
> The following newer release(s) are available in the Debian archive:
>   oldstable: 1.2.1-3
>   stable: 1.4.9-1
>   testing: 1.4.9-1
>   unstable: 1.4.9-1
> Do you still want to file a report [y|N|q|?]?
>
> I use sid and I've not found any newer version…
>
> Regards
>
> Jean-Luc
>
> - -- System Information:
> Debian Release: buster/sid
>   APT prefers unstable
>   APT policy: (600, 'unstable'), (500, 'buildd-unstable'), (500, 'testing'), 
> (1, 'experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.13.0-rc6-i7-0.1 (SMP w/8 CPU cores; PREEMPT)
> Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
> LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages astroid depends on:
> ii  libatk1.0-0 2.24.0-1
> ii  libatkmm-1.6-1v52.24.2-2
> ii  libboost-date-time1.62.01.62.0+dfsg-4+b1
> ii  libboost-filesystem1.62.0   1.62.0+dfsg-4+b1
> ii  libboost-log1.62.0  1.62.0+dfsg-4+b1
> ii  libboost-program-options1.62.0  1.62.0+dfsg-4+b1
> ii  libboost-system1.62.0   1.62.0+dfsg-4+b1
> ii  libboost-thread1.62.0   1.62.0+dfsg-4+b1
> ii  libc6   2.24-17
> ii  libcairo-gobject2   1.14.10-1
> ii  libcairo2   1.14.10-1
> ii  libcairomm-1.0-1v5  1.12.2-1
> ii  libgcc1 1:7.2.0-1
> ii  libgdk-pixbuf2.0-0  2.36.5-3
> ii  libgirepository-1.0-1   1.53.2-4
> ii  libglib2.0-02.53.6-1
> ii  libglibmm-2.4-1v5   2.50.1-1
> ii  libgmime-2.6-0  2.6.23+dfsg1-1
> ii  libgnutls30 3.5.15-2
> ii  libgtk-3-0  3.22.18-1
> ii  libgtkmm-3.0-1v53.22.1-1
> ii  libjavascriptcoregtk-3.0-0  2.4.11-3
> ii  libnotmuch5 0.25-6
> ii  libpango-1.0-0  1.40.11-1
> ii  libpangocairo-1.0-0 1.40.11-1
> ii  libpangomm-1.4-1v5  2.40.1-3
> ii  libpcre2-8-010.22-3
> ii  libpeas-1.0-0   1.20.0-1+b1
> ii  libsass03.4.3-1
> ii  libsigc++-2.0-0v5   2.10.0-1
> ii  libsoup2.4-12.56.1-1
> ii  libstdc++6  7.2.0-1
> ii  libvte-2.91-0   0.46.2-1
> ii  libwebkitgtk-3.0-0  2.4.11-3
> ii  zlib1g  1:1.2.8.dfsg-5
>
> Versions of packages astroid recommends:
> ii  emacs2525.2+1-5
> ii  gnupg  2.1.23-2
> ii  notmuch0.25-6
> ii  xdg-utils  1.1.1-1
>
> astroid suggests no packages.
>
> - -- no debconf information
>
> -BEGIN PGP SIGNATURE-
>
> iF0EARECAB0WIQT5el3FKLtmYO4UlQtR0YZfPMac0AUCWaPhJgAKCRBR0YZfPMac
> 0IkPAJ40gZrUN5Nxea0qPdItDhdgkGr2GQCeOy9H0sF6OtTTYj6zStGAVKARpCg=
> =qN0r
> -END PGP SIGNATURE-



-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Bug#873501: kivy FTBFS with Cython 0.26

[Adrian Bunk]

Source: kivy
Version: 1.9.1-1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/kivy.html

...
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-fno-strict-aliasing -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/usr/local/include/SDL2 -I/usr/include/SDL2 -I/usr/include/python2.7 -c 
kivy/core/text/_text_sdl2.c -o 
build/temp.linux-amd64-2.7/kivy/core/text/_text_sdl2.o
x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions 
-Wl,-z,relro -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall 
-Wstrict-prototypes -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-fdebug-prefix-map=/build/python2.7-qMUuQf/python2.7-2.7.13=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 build/temp.linux-amd64-2.7/kivy/core/text/_text_sdl2.o -lGL 
-lSDL2 -lSDL2_ttf -lSDL2_image -lSDL2_mixer -o 
/build/1st/kivy-1.9.1/.pybuild/pythonX.Y_2.7/build/kivy/core/text/_text_sdl2.so 
-L/usr/local/include/SDL2 -L/usr/include/SDL2 -lm
cythoning kivy/graphics/opengl.pyx to kivy/graphics/opengl.c
 
 Error compiling Cython file:
 
 ...
 def glCheckFramebufferStatus(GLenum target):
 '''See: `glCheckFramebufferStatus() on Kronos website
 
`_
 '''
 cdef GLenum result
 result = c_opengl.CheckFramebufferStatus(target)
 ^
 
 
 kivy/graphics/opengl.pyx:544:21: cimported module has no attribute 
'CheckFramebufferStatus'
building 'kivy.graphics.opengl' extension
creating build/temp.linux-amd64-2.7/kivy/graphics
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-fno-strict-aliasing -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/usr/include/python2.7 -c kivy/graphics/opengl.c -o 
build/temp.linux-amd64-2.7/kivy/graphics/opengl.o
kivy/graphics/opengl.c:1:2: error: #error Do not use this file, it is the 
result of a failed Cython compilation.
 #error Do not use this file, it is the result of a failed Cython compilation.
  ^
 error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
E: pybuild pybuild:283: build: plugin distutils failed with: exit code=1: 
/usr/bin/python setup.py build 
dh_auto_build: pybuild --build -i python{version} -p 2.7 returned exit code 13
debian/rules:6: recipe for target 'build' failed
make: *** [build] Error 25

Processed: severity of 873443 is grave ...

[Debian Bug Tracking System]

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

> severity 873443 grave
Bug #873443 [uno-libs3] uno-libs3: Fatal exception: Signal 6
Severity set to 'grave' from 'important'
> retitle 873443 terminate called after throwing an instance of 
> com::sun::star::uno::DeploymentException
Bug #873443 [uno-libs3] uno-libs3: Fatal exception: Signal 6
Changed Bug title to 'terminate called after throwing an instance of 
com::sun::star::uno::DeploymentException' from 'uno-libs3: Fatal exception: 
Signal 6'.
> thanks
Stopping processing here.

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

Bug#789927: anthy: Installing anthy 1.0.3-3 still fails on my setup

[David Cadé]

Package: anthy
Version: 1:0.3-3
Followup-For: Bug #789927

Dear Maintainer,

   * What led up to the situation?

Updating uim-anthy.
After anthy broke, I completely removed anthy from my installation, and now I'm 
trying to reinstall it.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 sudo apt install anthy

   * What was the outcome of this action?

Selecting previously unselected package libanthy1:amd64.
(Reading database ... 514359 files and directories currently installed.)
Preparing to unpack .../libanthy1_1%3a0.3-3_amd64.deb ...
Unpacking libanthy1:amd64 (1:0.3-3) ...
Selecting previously unselected package libanthyinput0:amd64.
Preparing to unpack .../libanthyinput0_1%3a0.3-3_amd64.deb ...
Unpacking libanthyinput0:amd64 (1:0.3-3) ...
dpkg: error processing archive 
/var/cache/apt/archives/libanthyinput0_1%3a0.3-3_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libanthyinput.so.0.0.0', which 
is also in package libanthy0:amd64 9100h-25+b2
Selecting previously unselected package anthy.
Preparing to unpack .../anthy_1%3a0.3-3_amd64.deb ...
Unpacking anthy (1:0.3-3) ...
Errors were encountered while processing:
 /var/cache/apt/archives/libanthyinput0_1%3a0.3-3_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Setting up libanthy1:amd64 (1:0.3-3) ...
Processing triggers for libc-bin (2.24-17) ...
dpkg: dependency problems prevent configuration of anthy:
 anthy depends on libanthyinput0; however:
  Package libanthyinput0:amd64 is not installed.

dpkg: error processing package anthy (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 anthy

   * What outcome did you expect instead?
   A clean installation of anthy.

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

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

Versions of packages anthy depends on:
ii  anthy-common1:0.3-3
ii  libanthy1   1:0.3-3
pn  libanthyinput0  
ii  libc6   2.24-17

anthy recommends no packages.

anthy suggests no packages.

-- debconf information:
  anthy/dictionaries: base.t, extra.t

Bug#873120: marked as done (389-ds-base: FTBFS on various architectures: test_plugin_pwdstorage_pbkdf2_rounds fails)

[Debian Bug Tracking System]

Your message dated Mon, 28 Aug 2017 12:34:28 +
with message-id 
and subject line Bug#873120: fixed in 389-ds-base 1.3.6.7-3
has caused the Debian Bug report #873120,
regarding 389-ds-base: FTBFS on various architectures: 
test_plugin_pwdstorage_pbkdf2_rounds fails
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.)


-- 
873120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873120
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: 389-ds-base
Version: 1.3.6.7-2
Severity: serious
Tags: sid buster

Hi,

389-ds-base FTBFS on various architectures (including armel, i386 and
mips) with this error:
> [==] Running 3 test(s).
> [ RUN  ] test_plugin_hello
> [   OK ] test_plugin_hello
> [ RUN  ] test_plugin_pwdstorage_pbkdf2_auth
> [   OK ] test_plugin_pwdstorage_pbkdf2_auth
> [ RUN  ] test_plugin_pwdstorage_pbkdf2_rounds
> [  ERROR   ] --- pbkdf2_sha256_calculate_iterations(1) == 2
> [   LINE   ] --- ../test/plugins/pwdstorage/pbkdf2.c:70: error: Failure!
> [  FAILED  ] test_plugin_pwdstorage_pbkdf2_rounds
> [==] 3 test(s) run.
> [  PASSED  ] 2 test(s).
> [  FAILED  ] 1 test(s), listed below:
> [  FAILED  ] test_plugin_pwdstorage_pbkdf2_rounds

This happens because the prototype of the
pbkdf2_sha256_calculate_iterations function:
> ldap/servers/plugins/pwdstorage/pwdstorage.h
> 95:PRUint32 pbkdf2_sha256_calculate_iterations();

does not match the type of the definition:
> ldap/servers/plugins/pwdstorage/pbkdf2_pwd.c
> 261:pbkdf2_sha256_calculate_iterations(uint64_t time_nsec)

When the test calls this function with an integer argument, the "default
integer promotions" will apply promoting it to an int. Therefore on
every architecture where int != uint64_t (pretty much everything), this
function call will invoke undefined behavior by having the wrong
argument types.

Thanks,
James



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: 389-ds-base
Source-Version: 1.3.6.7-3

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated 389-ds-base 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, 28 Aug 2017 15:09:02 +0300
Source: 389-ds-base
Binary: 389-ds 389-ds-base-libs 389-ds-base-dev 389-ds-base
Architecture: source
Version: 1.3.6.7-3
Distribution: unstable
Urgency: medium
Maintainer: Debian 389ds Team 

Changed-By: Timo Aaltonen 
Description:
 389-ds - 389 Directory Server suite - metapackage
 389-ds-base - 389 Directory Server suite - server
 389-ds-base-dev - 389 Directory Server suite - development files
 389-ds-base-libs - 389 Directory Server suite - libraries
Closes: 873120
Changes:
 389-ds-base (1.3.6.7-3) unstable; urgency=medium
 .
   * ftbfs-fix.diff: Fix build. (Closes: #873120)
Checksums-Sha1:
 641c879871670ba103ea730198326b06ad11bf5d 2563 389-ds-base_1.3.6.7-3.dsc
 f3bf3a74e84c62fe0d3d99ee6abcbbe47bf3684c 20588 
389-ds-base_1.3.6.7-3.debian.tar.xz
Checksums-Sha256:
 38040231c6837e46572b0d1c8e0532c71ecbc4ba3ea41d6a177a8b2be1e9e80d 2563 
389-ds-base_1.3.6.7-3.dsc
 14a5cc8689242e5f2548b6840bb2d85c88ebd892e4f9aaa4009568a09af3c9b4 20588 
389-ds-base_1.3.6.7-3.debian.tar.xz
Files:
 1ac33513d70c49d77b02486a520b3bdc 2563 net optional 389-ds-base_1.3.6.7-3.dsc
 67d099b14cb915e6331c49b9b2be5fa2 20588 net optional 
389-ds-base_1.3.6.7-3.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJZpAfxAAoJEMtwMWWoiYTcQSEP+wcwl2uQpv38jXAjBu3A8nyL
P22vVeduxYGQtUhmu7EYlDOFJTtdNtcZKg7qCP+2V6ohY2/DuBf9vV+SsVPbioGl
XTSFMott9JCOmHMzmAmw+s1WWAiWYMc3yqKyXbQ4qPjQ4xbdU0IVtOu3JQGJlQq3
eiiM2oYJzfDvsoXo+cAFZ2tjIWQ9yseQx2RB26Yp7lk/zTHdlAR1a/axlDMFP78C
Uz7kkGVRNmQkdhuFmn3VbL6fLIqz+xaRkg6kuuF7cmL/u1d1k7lkEqxpMPoxOxT+
WLCTpFuidHES+L+mKnDAm5i/vn+ZVVHcFSvbzz2QGVnewZGXJykk81jxcv4sMrSQ
YfaU0lFKegc7ffIn6T8/h5jSLimqJTj0aLceCMgk9HaNmK29j3jN2VyplDuNoLfF
FRseWqsFKdGPq856VJecmtFS4NehbvdHdX5YPkjOK8RK6zR+ggNPED0Sz+mFaXHB
HDScopwxkfIEFkLTMAqUK

Bug#868300: marked as done (yadm: CVE-2017-11353: race condition allows access to SSH and PGP keys)

[Debian Bug Tracking System]

Your message dated Mon, 28 Aug 2017 11:40:32 +
with message-id 
and subject line Bug#868300: fixed in yadm 1.11.1-1
has caused the Debian Bug report #868300,
regarding yadm: CVE-2017-11353: race condition allows access to SSH and PGP keys
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.)


-- 
868300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868300
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: yadm
Version: 1.10.0-1
Severity: grave
Tags: security upstream
Justification: user security hole

Dear Maintainer,

In its default configuration, yadm ensures that .ssh/ and .gnupg/ files are
readable by the owner only.  That is implemented by running 'chmod' on the
files after they have been created:

https://sources.debian.net/src/yadm/1.10.0-1/yadm/#L671

That way has a race condition: whilst the git worktree is being checked out,
the .ssh and .gnupg files have the permissions of the user's umask.  I added a
debug printf just before the 'chmod' and it showed .ssh/ and .ssh/config having
permissions «u=rwX,go=rX», i.e., world readable.

I tested in an uptodate sid chroot.

(I'm leaving the severity as 'grave' since I figure the vulnerability window
may be long in setups where the tree being checked out is large.)

Cheers,

Daniel
--- End Message ---
--- Begin Message ---
Source: yadm
Source-Version: 1.11.1-1

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

Debian distribution maintenance software
pp.
ChangZhuo Chen (陳昌倬)  (supplier of updated yadm 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, 28 Aug 2017 18:33:06 +0800
Source: yadm
Binary: yadm
Architecture: source
Version: 1.11.1-1
Distribution: unstable
Urgency: high
Maintainer: Yao-Po Wang 
Changed-By: ChangZhuo Chen (陳昌倬) 
Description:
 yadm   - Yet Another Dotfiles Manager
Closes: 868300
Changes:
 yadm (1.11.1-1) unstable; urgency=high
 .
   * New upstream release.
 * Fix CVE-2017-11353 (Closes: #868300).
Checksums-Sha1:
 b3992505d35c17ebe52320bef6cadf5594f34cc1 1865 yadm_1.11.1-1.dsc
 995b6b450144e50080a0ab9395670a8b72e567d8 44990 yadm_1.11.1.orig.tar.gz
 7e055f8bc5300ef31d4462ce7cf98793e377ef54 2404 yadm_1.11.1-1.debian.tar.xz
 f38dd8a49aba9bf0030745b03a0a968e18d8d6b1 5583 yadm_1.11.1-1_source.buildinfo
Checksums-Sha256:
 a5af1b436d7f5d59d4ffd272a3e6b83878d9a8e10c63f372ab84ba6ba5843c1f 1865 
yadm_1.11.1-1.dsc
 7074c08a317c627106cef3663f2ab05b6397fdf3e2f9186730368b44a26d8fe4 44990 
yadm_1.11.1.orig.tar.gz
 9993ee2af99664bcc5a006fb06922cde5ad3be2ae5cdfe747b30205f064f293d 2404 
yadm_1.11.1-1.debian.tar.xz
 ee4f2ca0196a45c0de1492451f86bd2203a9ba23900a64bc705fced2061ed47f 5583 
yadm_1.11.1-1_source.buildinfo
Files:
 596bcf966182cbe8719f5a38a6a2f9ec 1865 utils optional yadm_1.11.1-1.dsc
 9d67e801d2169a7b44b715d807782533 44990 utils optional yadm_1.11.1.orig.tar.gz
 2b494e3d9d4fb05344e90714e2071733 2404 utils optional 
yadm_1.11.1-1.debian.tar.xz
 c0c26abf8bd08c3a965e184c41af519d 5583 utils optional 
yadm_1.11.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEE5H9tOJ8ReWWaF1PGrc2MXdaTaQFAlmj8iEACgkQGrc2MXda
TaSQpRAA0nJvKaBTuCIvqaRuOg6dU8s4vczM/Sao+bXoLbK5TP6Jsz303WDxp+jQ
gedVLPQAtBd38IK5x991Q8Epgkp35ZyFeSMWKKEoNh1yS/hmrc7b1/gGb7ZWqA8l
O0xFxHHQz1CRHpmgSXf04m4cwGqMhEyLVlik0J0TfLg35bZnIar6z2nZ6NKFAAbH
oot5oM45fKA6HKwI8Drcreq7q62EgnK6OqOrPdv1R0oruWVwjl4wwsKo9CIlAIt7
0tjZMyMnpErxFDeu1R0QqjMEfFd1qOJgGfM0SFoGwvc+4Btm8yjcDWx0sYsYIFou
EyvifQtFgKy7dwJs1yuOC2QRHEvQGNSxn6IIWPAzu16f1PEX4rOKR3YsgLaVv7/X
HoBihFNPp8GzxrIFMvDd5Hs1RrysUuS/gE2KCax9j9rU4+qnbaWRKFpSlk16CafG
+mE8QoKFjuBRwQNICskrGeK044ejfALfnVuYqNM4zrpqK4iwretWVS7OIxNcRAEx
xWvFAzXNCVAgh2r7kVNfTsG8IDpGI1nKkXKiqnkS04Kj8uDb4rXfPZdtLxhScCZ/
qZsvuTcF8IWbNWGCfzofKrXfv67jqzKJWH5n3oBl1wU8w6HTJWvTBJ7DQff38zLj
EVIAK3H1ABM/v3jfFEEL2JCIxgk19f05NOrocJ+I487Q6QAs7HE=
=nXky
-END PGP SIGNATURE End Message ---

Bug#873029: marked as done ([unicode-data] Copyriht/Lack of get-orig-source where is the source)

[Debian Bug Tracking System]

Your message dated Mon, 28 Aug 2017 11:40:21 +
with message-id 
and subject line Bug#873029: fixed in unicode-data 10.0.0-2
has caused the Debian Bug report #873029,
regarding [unicode-data] Copyriht/Lack of get-orig-source where is the source
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.)


-- 
873029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873029
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: unicode-data
Version: 10.0.0-1
Severity: serious

Without copyright information with exact location of souce, it is hard to get 
source

It is at least a violation of 12.5. Copyright information

I could help with this package if needed

signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Source: unicode-data
Source-Version: 10.0.0-2

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated unicode-data 
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, 28 Aug 2017 08:48:57 +0100
Source: unicode-data
Binary: unicode-data
Architecture: source all
Version: 10.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Description:
 unicode-data - Property data for the Unicode character set
Closes: 832919 832921 873028 873029
Changes:
 unicode-data (10.0.0-2) unstable; urgency=medium
 .
   * Move to Standards-Version: 4.1.0; no changes required
   * Document source of datasets in debian/copyright. Closes: #873029
   * Update the files debian/allkeys.txt and debian/decomps.txt.
 Closes: #832921
   * Remove obsolete typo fix. Closes: #832919
   * Add emjoi TR6 files. Closes: #873028
Checksums-Sha1:
 79391a26be8371d7eb9965000ac02213f74a7ae4 1793 unicode-data_10.0.0-2.dsc
 85e10511bbe50d0e31c6337b45f9df14219bcfc3 233868 
unicode-data_10.0.0-2.debian.tar.xz
 a278ffc80a4d43c15246a0e5595389a7c707eda8 7317558 unicode-data_10.0.0-2_all.deb
 4850dba29106b51813abfdbe0271e268259d1de4 5458 
unicode-data_10.0.0-2_amd64.buildinfo
Checksums-Sha256:
 05aff7a1ba201e39049e9a13d4a65b50081eabd9ba0a87c44ae484bb09b3c56f 1793 
unicode-data_10.0.0-2.dsc
 af56b573e5e82163bea76aecb92aa744b0602939896b27ef643b96565277a599 233868 
unicode-data_10.0.0-2.debian.tar.xz
 a9fce4e10e3542c2e557086d0eec09bdf7bc11f2a6d92e0473d8603d3947a24a 7317558 
unicode-data_10.0.0-2_all.deb
 ac35475df3f17eb0572ec0635481ab7ce018d707f50f6e624d8088ea0b0dfb91 5458 
unicode-data_10.0.0-2_amd64.buildinfo
Files:
 55d26ba433e5f708dfbc6c5d1dd5c575 1793 misc optional unicode-data_10.0.0-2.dsc
 0567b7677dcf89e0736fb70cf0f2b3c3 233868 misc optional 
unicode-data_10.0.0-2.debian.tar.xz
 1feb706c3be1ff7b5d10ecf060b057d8 7317558 misc optional 
unicode-data_10.0.0-2_all.deb
 6051469885f08a1a62224850bd173509 5458 misc optional 
unicode-data_10.0.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAlmj3dkACgkQy+a7Tl2a
06Un8A/8CgMpnoXuAp08BCfdicWvCC5DGbjXe+hkB7QLclP338fUvgyJ/4vrPoEJ
xWsXlRtU4m/80JFseRyPFLAfp6RJM5J451Cf+LEkn7j2Dhc93AR3VFdbd1tH2/EK
zNhHFfkn5XlyWl0fsF7h112duaMn2SDOGWuIiLg+AXoDyxDVXowarx2puB1cRsrD
U+PjzEPGP5deWdKM2wOp1PujbA6UnUt94gdWaZVxYN8qZfGnaoqHjlz0CPbf+QQb
2v+z+5dnElueIMo+60dC6qLEvnNSeLw9jmt9/VU8MAYcFdqnPesRwxTfzNvGk9iU
mEbwdHD/Z6/yeein/CXNdk8vXr1QaviPsRU+g5xCw+ABqAuVhpnzpwovQCd1IoUG
W7vGD1SsVhsIeBXRmQa89yt0k9g9bzZqcJwOhOq8GLtzDrQYbUNozEQnRVlamQsN
VmVe0VG23+dbXdvs2afmU+w8SLyVEzy/Os71lyWPtX+kgm0Q0R5q5GWUkOLocmAI
raMuPcjZahOOCPR1A3EcIbLjL0O3Sq0jt49ty6gyTmCQi+2iaLEnCKkeDees8aMb
sbsDmfx0NxrEsQy+KWs50o37bIm8ryk98qmAF5Ce9HxzjZRT3QJcK3p+WX2V+goa
wucBlPOwhv6RQkGUiIzUOepEuZ21Hh0kf2oAB9TcwZr5mFxIEAI=
=mLbp
-END PGP SIGNATURE End Message ---

Bug#784512: Is anybody working on PySide2?

[Dmitry Shachnev]

On Mon, Aug 28, 2017 at 01:16:36PM +0200, W. Martin Borgert wrote:
> Quoting Dmitry Shachnev :
> > Where did you read that pyside2 will be part of Qt? I thought it is rather
> > a side project from The Qt Company.
>
> http://lists.qt-project.org/pipermail/pyside/2016-April/002401.html
>
> > * The goal is to make Pyside an integral part of new Qt releases.

Thank you for the pointer!

If pyside2 becomes part of Qt, then probably we will have to maintain
in the Qt/KDE team because the uploads will need to be synchronized with
Qt uploads.

However they have not achieved this goal yet: there has been no pyside2
release yet, and there is no pyside submodule in qt5.git.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Processed: Set Bug forwarded-to-address to 'https://github.com/cole-trapnell-lab/cufflinks/issues/89'

[Debian Bug Tracking System]

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

> forwarded 871234 https://github.com/cole-trapnell-lab/cufflinks/issues/89
Bug #871234 [src:cufflinks] cufflinks: FTBFS with GCC-7: error: type/value 
mismatch at argument 1 in template parameter list for 'template 
struct std::hash'
Set Bug forwarded-to-address to 
'https://github.com/cole-trapnell-lab/cufflinks/issues/89'.
>
End of message, stopping processing here.

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

Bug#871234: Set Bug forwarded-to-address to 'https://github.com/cole-trapnell-lab/cufflinks/issues/89'

[Alex Mestiashvili]

forwarded 871234 https://github.com/cole-trapnell-lab/cufflinks/issues/89

Bug#784512: Is anybody working on PySide2?

[W. Martin Borgert]

Quoting Dmitry Shachnev :

Where did you read that pyside2 will be part of Qt? I thought it is rather
a side project from The Qt Company.


http://lists.qt-project.org/pipermail/pyside/2016-April/002401.html


* The goal is to make Pyside an integral part of new Qt releases.

Processed: merge bugs

[Debian Bug Tracking System]

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

> severity 871547 important
Bug #871547 [cinnamon-session] general: Can't change to any other background.
Severity set to 'important' from 'normal'
> merge 871547 871460
Bug #871547 [cinnamon-session] general: Can't change to any other background.
Bug #871547 [cinnamon-session] general: Can't change to any other background.
Added tag(s) patch.
Bug #871460 [cinnamon-session] Gnome Settings 3.24 breaks Cinnamon power, fn 
keys, themes, fonts, backgrounds...
Bug #873107 [cinnamon-session] by not running it prevents changing screen 
resolution, breaks the font scaling, keyboard hotkeys and center touchpad tap
Merged 871460 871547 873107
> severity 872377 important
Bug #872377 [cinnamon-session] cinnamon: Fn+FX settings keys not responding
Severity set to 'important' from 'normal'
> merge 872377 871460
Bug #872377 [cinnamon-session] cinnamon: Fn+FX settings keys not responding
Bug #872377 [cinnamon-session] cinnamon: Fn+FX settings keys not responding
Added tag(s) patch.
Bug #871460 [cinnamon-session] Gnome Settings 3.24 breaks Cinnamon power, fn 
keys, themes, fonts, backgrounds...
Bug #871547 [cinnamon-session] general: Can't change to any other background.
Bug #873107 [cinnamon-session] by not running it prevents changing screen 
resolution, breaks the font scaling, keyboard hotkeys and center touchpad tap
Merged 871460 871547 872377 873107
> severity 873082 important
Bug #873082 [cinnamon-session] cinnamon: switching display to external monitor 
does not work with recent update
Severity set to 'important' from 'normal'
> merge 873082 871460
Bug #873082 [cinnamon-session] cinnamon: switching display to external monitor 
does not work with recent update
Bug #873082 [cinnamon-session] cinnamon: switching display to external monitor 
does not work with recent update
Added tag(s) patch.
Bug #871460 [cinnamon-session] Gnome Settings 3.24 breaks Cinnamon power, fn 
keys, themes, fonts, backgrounds...
Bug #871547 [cinnamon-session] general: Can't change to any other background.
Bug #872377 [cinnamon-session] cinnamon: Fn+FX settings keys not responding
Bug #873107 [cinnamon-session] by not running it prevents changing screen 
resolution, breaks the font scaling, keyboard hotkeys and center touchpad tap
Merged 871460 871547 872377 873082 873107
> severity 872975 important
Bug #872975 [cinnamon-session] cinnamon: some keyboard shortcuts do not work
Severity set to 'important' from 'normal'
> merge 872975 871460
Bug #872975 [cinnamon-session] cinnamon: some keyboard shortcuts do not work
Bug #872975 [cinnamon-session] cinnamon: some keyboard shortcuts do not work
Added tag(s) patch.
Bug #871460 [cinnamon-session] Gnome Settings 3.24 breaks Cinnamon power, fn 
keys, themes, fonts, backgrounds...
Bug #871547 [cinnamon-session] general: Can't change to any other background.
Bug #872377 [cinnamon-session] cinnamon: Fn+FX settings keys not responding
Bug #873082 [cinnamon-session] cinnamon: switching display to external monitor 
does not work with recent update
Bug #873107 [cinnamon-session] by not running it prevents changing screen 
resolution, breaks the font scaling, keyboard hotkeys and center touchpad tap
Merged 871460 871547 872377 872975 873082 873107
> severity 873295 important
Bug #873295 [cinnamon-session] function keys not working on debian testing/sid
Severity set to 'important' from 'normal'
> merge 873295 871460
Bug #873295 [cinnamon-session] function keys not working on debian testing/sid
Bug #873295 [cinnamon-session] function keys not working on debian testing/sid
Added tag(s) patch.
Bug #871460 [cinnamon-session] Gnome Settings 3.24 breaks Cinnamon power, fn 
keys, themes, fonts, backgrounds...
Bug #871547 [cinnamon-session] general: Can't change to any other background.
Bug #872377 [cinnamon-session] cinnamon: Fn+FX settings keys not responding
Bug #872975 [cinnamon-session] cinnamon: some keyboard shortcuts do not work
Bug #873082 [cinnamon-session] cinnamon: switching display to external monitor 
does not work with recent update
Bug #873107 [cinnamon-session] by not running it prevents changing screen 
resolution, breaks the font scaling, keyboard hotkeys and center touchpad tap
Merged 871460 871547 872377 872975 873082 873107 873295
> severity 872029 important
Bug #872029 [cinnamon-session] cinnamon-settings-daemon: does not remain running
Severity set to 'important' from 'grave'
> merge 872029 871460
Bug #872029 [cinnamon-session] cinnamon-settings-daemon: does not remain running
Bug #872029 [cinnamon-session] cinnamon-settings-daemon: does not remain running
Added tag(s) patch.
Bug #871460 [cinnamon-session] Gnome Settings 3.24 breaks Cinnamon power, fn 
keys, themes, fonts, backgrounds...
Bug #871547 [cinnamon-session] general: Can't change to any other background.
Bug #872377 [cinnamon-session] cinnamon: Fn+FX settings keys not responding
Bug #872975 [cinnamon-session] cinnamon: some keyboard shortcuts do not work
Bug #873082 [cinnamon-session] ci

Processed (with 6 errors): reassign and merge bugs

[Debian Bug Tracking System]

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

> reassign 871547 cinnamon-session 3.2.0-4
Bug #871547 [cinnamon] general: Can't change to any other background.
Bug reassigned from package 'cinnamon' to 'cinnamon-session'.
No longer marked as found in versions cinnamon/3.2.7-4.
Ignoring request to alter fixed versions of bug #871547 to the same values 
previously set
Bug #871547 [cinnamon-session] general: Can't change to any other background.
Marked as found in versions cinnamon-session/3.2.0-4.
> merge 871547 871460
Bug #871547 [cinnamon-session] general: Can't change to any other background.
Unable to merge bugs because:
severity of #871460 is 'important' not 'normal'
Failed to merge 871547: Did not alter merged bugs.

> reassign 872377 cinnamon-session 3.2.0-4
Bug #872377 [cinnamon] cinnamon: Fn+FX settings keys not responding
Bug reassigned from package 'cinnamon' to 'cinnamon-session'.
No longer marked as found in versions cinnamon/3.2.7-4.
Ignoring request to alter fixed versions of bug #872377 to the same values 
previously set
Bug #872377 [cinnamon-session] cinnamon: Fn+FX settings keys not responding
Marked as found in versions cinnamon-session/3.2.0-4.
> merge 872377 871460
Bug #872377 [cinnamon-session] cinnamon: Fn+FX settings keys not responding
Unable to merge bugs because:
severity of #871460 is 'important' not 'normal'
Failed to merge 872377: Did not alter merged bugs.

> reassign 873082 cinnamon-session 3.2.0-4
Bug #873082 [cinnamon] cinnamon: switching display to external monitor does not 
work with recent update
Bug reassigned from package 'cinnamon' to 'cinnamon-session'.
No longer marked as found in versions cinnamon/3.2.7-4.
Ignoring request to alter fixed versions of bug #873082 to the same values 
previously set
Bug #873082 [cinnamon-session] cinnamon: switching display to external monitor 
does not work with recent update
Marked as found in versions cinnamon-session/3.2.0-4.
> merge 873082 871460
Bug #873082 [cinnamon-session] cinnamon: switching display to external monitor 
does not work with recent update
Unable to merge bugs because:
severity of #871460 is 'important' not 'normal'
Failed to merge 873082: Did not alter merged bugs.

> reassign 872975 cinnamon-session 3.2.0-4
Bug #872975 [cinnamon] cinnamon: some keyboard shortcuts do not work
Bug reassigned from package 'cinnamon' to 'cinnamon-session'.
No longer marked as found in versions cinnamon/3.2.7-4.
Ignoring request to alter fixed versions of bug #872975 to the same values 
previously set
Bug #872975 [cinnamon-session] cinnamon: some keyboard shortcuts do not work
Marked as found in versions cinnamon-session/3.2.0-4.
> merge 872975 871460
Bug #872975 [cinnamon-session] cinnamon: some keyboard shortcuts do not work
Unable to merge bugs because:
severity of #871460 is 'important' not 'normal'
Failed to merge 872975: Did not alter merged bugs.

> reassign 873295 cinnamon-session 3.2.0-4
Bug #873295 [cinnamon] function keys not working on debian testing/sid
Bug reassigned from package 'cinnamon' to 'cinnamon-session'.
Ignoring request to alter found versions of bug #873295 to the same values 
previously set
Ignoring request to alter fixed versions of bug #873295 to the same values 
previously set
Bug #873295 [cinnamon-session] function keys not working on debian testing/sid
Marked as found in versions cinnamon-session/3.2.0-4.
> merge 873295 871460
Bug #873295 [cinnamon-session] function keys not working on debian testing/sid
Unable to merge bugs because:
severity of #871460 is 'important' not 'normal'
Failed to merge 873295: Did not alter merged bugs.

> reassign 872029 cinnamon-session 3.2.0-4
Bug #872029 [cinnamon-settings-daemon] cinnamon-settings-daemon: does not 
remain running
Bug reassigned from package 'cinnamon-settings-daemon' to 'cinnamon-session'.
No longer marked as found in versions cinnamon-settings-daemon/3.2.1-3.
Ignoring request to alter fixed versions of bug #872029 to the same values 
previously set
Bug #872029 [cinnamon-session] cinnamon-settings-daemon: does not remain running
Marked as found in versions cinnamon-session/3.2.0-4.
> merge 872029 871460
Bug #872029 [cinnamon-session] cinnamon-settings-daemon: does not remain running
Unable to merge bugs because:
severity of #871460 is 'important' not 'grave'
Failed to merge 872029: Did not alter merged bugs.

> reassign 873107 cinnamon-session 3.2.0-4
Bug #873107 [cinnamon-settings-daemon] by not running it prevents changing 
screen resolution, breaks the font scaling, keyboard hotkeys and center 
touchpad tap
Bug reassigned from package 'cinnamon-settings-daemon' to 'cinnamon-session'.
No longer marked as found in versions cinnamon-settings-daemon/3.4.2-1.
Ignoring request to alter fixed versions of bug #873107 to the same values 
previously set
Bug #873107 [cinnamon-session] by not running it prevents changing screen 
resolution, breaks the font scaling, keyboard hotkeys and center touchpad tap
Marked as found in versions cinnamon-session/3.2.0-4.
>

Processed: your mail

[Debian Bug Tracking System]

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

> tags 868611 help
Bug #868611 [src:sisu-guice] sisu-guice FTBFS: Sisu Guice - Core Library FAILURE
Bug #869013 [src:sisu-guice] sisu-guice: FTBFS: find: 
'/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such 
file or directory
Added tag(s) help.
Added tag(s) help.
>
End of message, stopping processing here.

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

Processed: severity of 873486 is important

[Debian Bug Tracking System]

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

> severity 873486 important
Bug #873486 [fcitx] fcitx can not be start after upgrade to Debian buster
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#873486: fcitx can not be start after upgrade to Debian buster

[Shengjing Zhu]

Control: tags -1 moreinfo

Please run fcitx-diagnose and paste the result here.

Thanks

On Mon, Aug 28, 2017 at 5:51 PM, gulfstream  wrote:
> Package: fcitx
> Version: 1:4.2.9.1-6
> Severity: grave
>
>
>
> Hi!
>
> I upgraded my Debian to buster yesterday. Then the fcitx can not be used now. 
> When I run it, the messages are get as blew:
>
> wgl@athena:~$ fcitx
> wgl@athena:~$ (INFO-6096 
> /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load Addon 
> Config File:fcitx-autoeng.conf
> (INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
> Addon Config File:fcitx-chttrans.conf
> (INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
> Addon Config File:fcitx-clipboard.conf
> (INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
> Addon Config File:fcitx-fullwidth-char.conf
> (INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
> Addon Config File:fcitx-imselector.conf
> (INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
> Addon Config File:fcitx-keyboard.conf
> (INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
> Addon Config File:fcitx-punc.conf
> (INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
> Addon Config File:fcitx-quickphrase.conf
> (INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
> Addon Config File:fcitx-remote-module.conf
> (INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
> Addon Config File:fcitx-spell.conf
> (INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
> Addon Config File:fcitx-unicode.conf
> (INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
> Addon Config File:fcitx-dbus.conf
> (INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
> Addon Config File:fcitx-freedesktop-notify.conf
> (INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
> Addon Config File:fcitx-ipc.conf
> (INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
> Addon Config File:fcitx-googlepinyin.conf
> (INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
> Addon Config File:fcitx-kimpanel-ui.conf
> (INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
> Addon Config File:fcitx-lua.conf
> (INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
> Addon Config File:fcitx-vk.conf
> (INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
> Addon Config File:fcitx-x11.conf
> (INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
> Addon Config File:fcitx-xim.conf
> (INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
> Addon Config File:fcitx-xkb.conf
> (INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
> Addon Config File:fcitx-xkbdbus.conf
> (INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
> Addon Config File:fcitx-pinyin-enhance.conf
> (INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
> Addon Config File:fcitx-pinyin.conf
> (INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
> Addon Config File:fcitx-sunpinyin.conf
> (INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
> Addon Config File:fcitx-table.conf
> (INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
> Addon Config File:fcitx-classic-ui.conf
> (INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
> Addon Config File:fcitx-notificationitem.conf
> (ERROR-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/ime.c:432) 
> fcitx-keyboard-cm-mmuock already exists
> (WARN-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/frontend/xim/xim.c:161) 
> Please set XMODIFIERS.
>
>
> The fcitx works fine when the Debian is stretch before I upgrade to buster.
>
> Could you resolve this problem? Thank you very much!
>
>
>
> Best regards,
> Gulfstream
>
>
>
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), 
> LANGUAGE=zh_CN.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages fcitx depends on:
> ii  fcitx-bin  1:4.2.9.1-6
> ii  fcitx-data 1:4.2.9.1-6
> ii  fcitx-modules  1:4.2.9.1-6
>
> Versions of packages fcitx recommends:
> ii  fcitx-config-gtk   0.4.8-3+b1
> ii  fcitx-frontend-all 1:4.2.9.1-6
> ii  fcitx-ui-classic   1:4.2.9.1-6
> ii  im-config [im-switch]  0.30-1
>
> Versions of packages fcitx suggests:
> pn  fcitx-m17n   
> pn  fcitx-tools  
>
> -- no debconf information
>
> ___

Processed: Re: Bug#873486: fcitx can not be start after upgrade to Debian buster

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #873486 [fcitx] fcitx can not be start after upgrade to Debian buster
Added tag(s) moreinfo.

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

Bug#853361: marked as done (csh: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Mon, 28 Aug 2017 10:20:35 +
with message-id 
and subject line Bug#853361: fixed in csh 20110502-3
has caused the Debian Bug report #853361,
regarding csh: ftbfs with GCC-7
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.)


-- 
853361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853361
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:csh
Version: 20110502-2.2
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/csh_20110502-2.2_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
   dh_auto_configure -O--buildsystem=bmake
dh_auto_configure: Compatibility levels before 9 are deprecated (level 8 in use)
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
dh_auto_build: Compatibility levels before 9 are deprecated (level 8 in use)
bmake
bmake[2]: Entering directory `/<>'
egrep 'ERR_' /<>/error.c | egrep '^#define' >> error.h
cc -E -g -O2 -Wno-error -I/<> -I. -DBUILTIN -DFILEC -DNLS 
-DSHORT_STRINGS -D_GNU_SOURCE  -Werror  /<>/const.c | egrep 'Char 
STR' |  sed -e 's/Char \([a-zA-Z0-9_]*\)\(.*\)/extern Char \1[];/' |  sort >> 
const.h
cc -g -O2 -Wno-error -I/<> -I. -DBUILTIN -DFILEC -DNLS 
-DSHORT_STRINGS -D_GNU_SOURCE  -Werror   -c alloc.c
cc -g -O2 -Wno-error -I/<> -I. -DBUILTIN -DFILEC -DNLS 
-DSHORT_STRINGS -D_GNU_SOURCE  -Werror   -c char.c
cc -g -O2 -Wno-error -I/<> -I. -DBUILTIN -DFILEC -DNLS 
-DSHORT_STRINGS -D_GNU_SOURCE  -Werror   -c const.c
cc -g -O2 -Wno-error -I/<> -I. -DBUILTIN -DFILEC -DNLS 
-DSHORT_STRINGS -D_GNU_SOURCE  -Werror   -c csh.c
cc -g -O2 -Wno-error -I/<> -I. -DBUILTIN -DFILEC -DNLS 
-DSHORT_STRINGS -D_GNU_SOURCE  -Werror   -c dir.c
cc -g -O2 -Wno-error -I/<> -I. -DBUILTIN -DFILEC -DNLS 
-DSHORT_STRINGS -D_GNU_SOURCE  -Werror   -c dol.c
cc -g -O2 -Wno-error -I/<> -I. -DBUILTIN -DFILEC -DNLS 
-DSHORT_STRINGS -D_GNU_SOURCE  -Werror   -c error.c
cc -g -O2 -Wno-error -I/<> -I. -DBUILTIN -DFILEC -DNLS 
-DSHORT_STRINGS -D_GNU_SOURCE  -Werror   -c exec.c
cc -g -O2 -Wno-error -I/<> -I. -DBUILTIN -DFILEC -DNLS 
-DSHORT_STRINGS -D_GNU_SOURCE  -Werror   -c exp.c
cc -g -O2 -Wno-error -I/<> -I. -DBUILTIN -DFILEC -DNLS 
-DSHORT_STRINGS -D_GNU_SOURCE  -Werror   -c file.c
cc -g -O2 -Wno-error -I/<> -I. -DBUILTIN -DFILEC -DNLS 
-DSHORT_STRINGS -D_GNU_SOURCE  -Werror   -c func.c
cc -g -O2 -Wno-error -I/<> -I. -DBUILTIN -DFILEC -DNLS 
-DSHORT_STRINGS -D_GNU_SOURCE  -Werror   -c glob.c
cc -g -O2 -Wno-error -I/<> -I. -DBUILTIN -DFILEC -DNLS 
-DSHORT_STRINGS -D_GNU_SOURCE  -Werror   -c hist.c
cc -g -O2 -Wno-error -I/<> -I. -DBUILTIN -DFILEC -DNLS 
-DSHORT_STRINGS -D_GNU_SOURCE  -Werror   -c init.c
cc -g -O2 -Wno-error -I/<> -I. -DBUILTIN -DFILEC -DNLS 
-DSHORT_STRINGS -D_GNU_SOURCE  -Werror   -c lex.c
lex.c: In function 'readc':
lex.c:1307:24: error: comparison between pointer and zero character constant 
[-Werror=pointer-compare]
  if ((alvecp = *alvec) != '\0') {
^~
lex.c:1307:6: note: did you mean to dereference the pointer?
  if ((alvecp = *alvec) != '\0') {
  ^
lex.c:1330:25: error: comparison between pointer and zero character constant 
[-Werror=pointer-compare]
  if ((evalp = *evalvec) != '\0') {
 ^~
lex.c:1330:6: note: did you mean to dereference the pointer?
  if ((evalp = *evalvec) != '\0') {
  ^
cc1: all warnings being treated as errors
*** Error code 1

Stop.
bmake[2]: stopped in /<>
dh_auto_build: bmake returned exit code 1
debian/rul

Bug#873486: fcitx can not be start after upgrade to Debian buster

[gulfstream]

Package: fcitx
Version: 1:4.2.9.1-6
Severity: grave



Hi!

I upgraded my Debian to buster yesterday. Then the fcitx can not be used now. 
When I run it, the messages are get as blew:

wgl@athena:~$ fcitx
wgl@athena:~$ (INFO-6096 
/build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load Addon Config 
File:fcitx-autoeng.conf
(INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
Addon Config File:fcitx-chttrans.conf
(INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
Addon Config File:fcitx-clipboard.conf
(INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
Addon Config File:fcitx-fullwidth-char.conf
(INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
Addon Config File:fcitx-imselector.conf
(INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
Addon Config File:fcitx-keyboard.conf
(INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
Addon Config File:fcitx-punc.conf
(INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
Addon Config File:fcitx-quickphrase.conf
(INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
Addon Config File:fcitx-remote-module.conf
(INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
Addon Config File:fcitx-spell.conf
(INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
Addon Config File:fcitx-unicode.conf
(INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
Addon Config File:fcitx-dbus.conf
(INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
Addon Config File:fcitx-freedesktop-notify.conf
(INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
Addon Config File:fcitx-ipc.conf
(INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
Addon Config File:fcitx-googlepinyin.conf
(INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
Addon Config File:fcitx-kimpanel-ui.conf
(INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
Addon Config File:fcitx-lua.conf
(INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
Addon Config File:fcitx-vk.conf
(INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
Addon Config File:fcitx-x11.conf
(INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
Addon Config File:fcitx-xim.conf
(INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
Addon Config File:fcitx-xkb.conf
(INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
Addon Config File:fcitx-xkbdbus.conf
(INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
Addon Config File:fcitx-pinyin-enhance.conf
(INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
Addon Config File:fcitx-pinyin.conf
(INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
Addon Config File:fcitx-sunpinyin.conf
(INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
Addon Config File:fcitx-table.conf
(INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
Addon Config File:fcitx-classic-ui.conf
(INFO-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/addon.c:151) Load 
Addon Config File:fcitx-notificationitem.conf
(ERROR-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/lib/fcitx/ime.c:432) 
fcitx-keyboard-cm-mmuock already exists
(WARN-6096 /build/fcitx-SJV5lg/fcitx-4.2.9.1/src/frontend/xim/xim.c:161) Please 
set XMODIFIERS.


The fcitx works fine when the Debian is stretch before I upgrade to buster.

Could you resolve this problem? Thank you very much!



Best regards,
Gulfstream




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

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

Versions of packages fcitx depends on:
ii  fcitx-bin  1:4.2.9.1-6
ii  fcitx-data 1:4.2.9.1-6
ii  fcitx-modules  1:4.2.9.1-6

Versions of packages fcitx recommends:
ii  fcitx-config-gtk   0.4.8-3+b1
ii  fcitx-frontend-all 1:4.2.9.1-6
ii  fcitx-ui-classic   1:4.2.9.1-6
ii  im-config [im-switch]  0.30-1

Versions of packages fcitx suggests:
pn  fcitx-m17n   
pn  fcitx-tools  

-- no debconf information

Bug#871288: marked as done (libzeroc-ice3.6: requires rebuild against GCC 7 and symbols/shlibs bump)

[Debian Bug Tracking System]

Your message dated Mon, 28 Aug 2017 12:04:05 +0200
with message-id 

and subject line Re: Bug#871288: libzeroc-ice3.6: requires rebuild against GCC 
7 and symbols/shlibs bump
has caused the Debian Bug report #871288,
regarding libzeroc-ice3.6: requires rebuild against GCC 7 and symbols/shlibs 
bump
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.)


-- 
871288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871288
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libzeroc-ice3.6
Version: 3.6.3-5
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: gcc-7-op-mangling

Hi,

It appears that your package provides an external symbol that is
affected by the recent name mangling changes in GCC 7. See:
https://gcc.gnu.org/gcc-7/porting_to.html#conversion-op-mangling

In GCC 7, the name mangling for C++ conversion operators which return a
type using the abi_tag attribute (most commonly std::string) has
changed. When your library is compiled with GCC 7, it will now emit two
symbols for the conversion operator using the new and old naming.
Executables compiled with GCC 7 will always use the new symbol, while
old executables compiled using <= GCC 6 will use the old symbol. For new
executables to build without undefined references, your library will
need rebuilding with GCC 7.

To ensure that new executables will pull in the newer version of the
library built with GCC 7:
- Your library package should Build-Depend on g++ (>= 4:7).
- If your package provides a symbols file, ensure that the new
  conversion operator symbols have a version matching the version this
  bug is fixed in (including the Debian revision and tilde if
  necessary).

  Using apt as an example (debian/libapt-pkg5.0.symbols):
(c++)"URI::operator std::__cxx11::basic_string, std::allocator >[abi:cxx11]()@APTPKG_5.0" 0.8.0
  + (c++)"URI::operator std::__cxx11::basic_string, std::allocator >()@APTPKG_5.0" 1.5~beta2~

  Where "1.5~beta2" is the version this bug was fixed in.

- If your package does not provide a symbols file, add a dh_makeshlibs
  override so that tight enough dependencies are generated.

  Using libebml as an example (debian/rules):
  + override_dh_makeshlibs:
  + # For new symbols when compiled with GCC 7
  + dh_makeshlibs -V'libebml4v5 (>= 1.3.4-2~)'

  Where "1.3.4-2" is the version this bug was fixed in.

- If your package is about to be renamed due to an upstream SONAME bump,
  you do not need to add any special symbols handling.

If you would like to know the exact name of the new symbols, using
"abipkgdiff" from abigail-tools might be able to help.

Thanks,
James
--- End Message ---
--- Begin Message ---
The issue has been fixed in 3.6.3-6 version of the package

The package now build depends on  g++ (>= 4:7) [1]
Added override_dh_makeshlibs to generate correct dependencies [2]

[1]:
https://github.com/zeroc-ice/ice-debian-packaging/blob/3.6-sid/debian/control#L17
[2]:
https://github.com/zeroc-ice/ice-debian-packaging/blob/3.6-sid/debian/rules#L176

On Thu, Aug 10, 2017 at 4:51 AM, James Cowgill  wrote:

> Hi,
>
> On 09/08/17 10:07, Jose Gutierrez de la Concha wrote:
> > On Tue, Aug 8, 2017 at 6:07 PM, James Cowgill  > > wrote:
> >
> >On 08/08/17 11:29, Jose Gutierrez de la Concha wrote:
> >> On Tue, Aug 8, 2017 at 5:01 PM, James Cowgill  
> >> >> wrote:
> >>[...]
> >>>- If your package does not provide a symbols file, add a dh_makeshlibs
> >>>  override so that tight enough dependencies are generated.
> >>>
> >>>  Using libebml as an example (debian/rules):
> >>>  + override_dh_makeshlibs:
> >>>  + # For new symbols when compiled with GCC 7
> >>>  + dh_makeshlibs -V'libebml4v5 (>= 1.3.4-2~)'
> >>>
> >
> > Any ideas how should I handle multiple packages in override_dh_makeshlibs
> > zeroc-ice has several packages that include libzeroc-ice3.6,
> > libzeroc-freeze3.6
> > so I cannot really pass a single package name in -V
>
> Here's an example. SFML has 5 libraries and 2 of them have specific
> dh_makeshlibs calls.
>
> https://sources.debian.net/src/libsfml/2.4.2%2Bdfsg-4/debian/rules/#L18
>
> In short, you use the -p option to apply a -V to a specific package and
> then use --remaining-packages if there are any left.
>
> I think that only the libzeroc-ice3.6 package is affected by this
> (although you may want to double check) so you may only need to set the
> dependencies for that package.
>
> Thanks,
> James
>
>


-- 
José Gutiérrez de la Concha
ZeroC, I

Bug#853539: marked as done (mash: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Mon, 28 Aug 2017 10:00:11 +
with message-id 
and subject line Bug#853539: fixed in capnproto 0.6.1-1
has caused the Debian Bug report #853539,
regarding mash: ftbfs with GCC-7
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.)


-- 
853539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853539
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mash
Version: 1.1.1-1
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/mash_1.1.1-1_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
 template  struct ElementSizeForType> {
  ^~
In file included from /usr/include/capnp/generated-header-support.h:31:0,
 from src/mash/capnp/MinHash.capnp.h:7,
 from src/mash/Sketch.h:10,
 from src/mash/CommandFind.h:11,
 from src/mash/mash.cpp:10:
/usr/include/capnp/layout.h:129:65: error: could not convert template argument 
‘b’ from ‘bool’ to ‘capnp::Kind’
 template  struct ElementSizeForType> {
 ^
/usr/include/capnp/layout.h:129:66: error: template argument 1 is invalid
 template  struct ElementSizeForType> {
  ^~
In file included from /usr/include/capnp/generated-header-support.h:31:0,
 from src/mash/capnp/MinHash.capnp.h:7,
 from src/mash/Sketch.h:10,
 from src/mash/CommandPaste.h:11,
 from src/mash/CommandPaste.cpp:7:
/usr/include/capnp/layout.h:129:65: error: could not convert template argument 
‘b’ from ‘bool’ to ‘capnp::Kind’
 template  struct ElementSizeForType> {
 ^
/usr/include/capnp/layout.h:129:66: error: template argument 1 is invalid
 template  struct ElementSizeForType> {
  ^~
Makefile:44: recipe for target 'src/mash/mash.o' failed
make[2]: *** [src/mash/mash.o] Error 1
Makefile:44: recipe for target 'src/mash/sketchParameterSetup.o' failed
make[2]: *** [src/mash/sketchParameterSetup.o] Error 1
Makefile:44: recipe for target 'src/mash/CommandSketch.o' failed
make[2]: *** [src/mash/CommandSketch.o] Error 1
Makefile:44: recipe for target 'src/mash/CommandDistance.o' failed
make[2]: *** [src/mash/CommandDistance.o] Error 1
Makefile:44: recipe for target 'src/mash/CommandPaste.o' failed
make[2]: *** [src/mash/CommandPaste.o] Error 1
Makefile:44: recipe for target 'src/mash/CommandContain.o' failed
make[2]: *** [src/mash/CommandContain.o] Error 1
Makefile:44: recipe for target 'src/mash/CommandInfo.o' failed
make[2]: *** [src/mash/CommandInfo.o] Error 1
Makefile:44: recipe for target 'src/mash/CommandFind.o' failed
make[2]: *** [src/mash/CommandFind.o] Error 1
Makefile:44: recipe for target 'src/mash/Sketch.o' failed
make[2]: *** [src/mash/Sketch.o] Error 1
make[2]: Leaving directory '/<>'
dh_auto_build: make -j64 returned exit code 2
debian/rules:33: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
debian/rules:23: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---
Source: capnproto
Source-Version: 0.6

Bug#871175: marked as done (mash: FTBFS: layout.h:129:65: error: could not convert template argument ‘b’ from ‘bool’ to ‘capnp::Kind’)

[Debian Bug Tracking System]

Your message dated Mon, 28 Aug 2017 10:00:11 +
with message-id 
and subject line Bug#853342: fixed in capnproto 0.6.1-1
has caused the Debian Bug report #853342,
regarding mash: FTBFS: layout.h:129:65: error: could not convert template 
argument ‘b’ from ‘bool’ to ‘capnp::Kind’
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.)


-- 
853342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853342
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mash
Version: 1.1.1-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> g++ -c -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -O3 -std=c++11 -Isrc -I/usr/include -I 
> /usr/include -Wdate-time -D_FORTIFY_SOURCE=2  -o 
> src/mash/sketchParameterSetup.o src/mash/sketchParameterSetup.cpp
> In file included from /usr/include/capnp/generated-header-support.h:31:0,
>  from src/mash/capnp/MinHash.capnp.h:7,
>  from src/mash/Sketch.h:10,
>  from src/mash/Sketch.cpp:7:
> /usr/include/capnp/layout.h:129:65: error: could not convert template 
> argument ‘b’ from ‘bool’ to ‘capnp::Kind’
>  template  struct ElementSizeForType> {
>  ^
> /usr/include/capnp/layout.h:129:66: error: template argument 1 is invalid
>  template  struct ElementSizeForType> {
>   ^~
> g++ -c -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -O3 -std=c++11 -Isrc -I/usr/include -I 
> /usr/include -Wdate-time -D_FORTIFY_SOURCE=2  -o 
> src/mash/capnp/MinHash.capnp.o src/mash/capnp/MinHash.capnp.c++
> In file included from /usr/include/capnp/generated-header-support.h:31:0,
>  from src/mash/capnp/MinHash.capnp.h:7,
>  from src/mash/Sketch.h:10,
>  from src/mash/CommandContain.h:11,
>  from src/mash/CommandContain.cpp:7:
> /usr/include/capnp/layout.h:129:65: error: could not convert template 
> argument ‘b’ from ‘bool’ to ‘capnp::Kind’
>  template  struct ElementSizeForType> {
>  ^
> /usr/include/capnp/layout.h:129:66: error: template argument 1 is invalid
>  template  struct ElementSizeForType> {
>   ^~
> In file included from /usr/include/capnp/generated-header-support.h:31:0,
>  from src/mash/capnp/MinHash.capnp.h:7,
>  from src/mash/Sketch.h:10,
>  from src/mash/CommandDistance.h:11,
>  from src/mash/CommandDistance.cpp:7:
> /usr/include/capnp/layout.h:129:65: error: could not convert template 
> argument ‘b’ from ‘bool’ to ‘capnp::Kind’
>  template  struct ElementSizeForType> {
>  ^
> /usr/include/capnp/layout.h:129:66: error: template argument 1 is invalid
>  template  struct ElementSizeForType> {
>   ^~
> In file included from /usr/include/capnp/generated-header-support.h:31:0,
>  from src/mash/capnp/MinHash.capnp.h:7,
>  from src/mash/Sketch.h:10,
>  from src/mash/CommandFind.h:11,
>  from src/mash/mash.cpp:10:
> /usr/include/capnp/layout.h:129:65: error: could not convert template 
> argument ‘b’ from ‘bool’ to ‘capnp::Kind’
>  template  struct ElementSizeForType> {
>  ^
> /usr/include/capnp/layout.h:129:66: error: template argument 1 is invalid
>  template  struct ElementSizeForType> {
>   ^~
> In file included from /usr/include/capnp/generated-header-support.h:31:0,
>  from src/mash/capnp/MinHash.capnp.h:7,
>  from src/mash/capnp/MinHash.capnp.c++:4:
> /usr/include/capnp/layout.h:129:65: error: could not convert template 
> argument ‘b’ from ‘bool’ to ‘capnp::Kind’
>  template  struct ElementSizeForType> {
>  ^
> /usr/include/capnp/layout.h:129:66: error: template argument 1 is invalid
>  template  struct ElementSizeForType> {
>

Bug#871118: marked as done (harvest-tools: FTBFS: layout.h:129:65: error: could not convert template argument 'b' from 'bool' to 'capnp::Kind')

[Debian Bug Tracking System]

Your message dated Mon, 28 Aug 2017 10:00:11 +
with message-id 
and subject line Bug#853539: fixed in capnproto 0.6.1-1
has caused the Debian Bug report #853539,
regarding harvest-tools: FTBFS: layout.h:129:65: error: could not convert 
template argument 'b' from 'bool' to 'capnp::Kind'
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.)


-- 
853539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853539
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: harvest-tools
Version: 1.3-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> g++ -c -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -std=c++11 -Isrc -I/usr/include 
> -I/usr/include -Wdate-time -D_FORTIFY_SOURCE=2 -o 
> src/harvest/AnnotationList.o src/harvest/AnnotationList.cpp
> In file included from /usr/include/capnp/generated-header-support.h:31:0,
>  from src/harvest/capnp/harvest.capnp.h:7,
>  from src/harvest/AnnotationList.h:15,
>  from src/harvest/AnnotationList.cpp:7:
> /usr/include/capnp/layout.h:129:65: error: could not convert template 
> argument 'b' from 'bool' to 'capnp::Kind'
>  template  struct ElementSizeForType> {
>  ^
> /usr/include/capnp/layout.h:129:66: error: template argument 1 is invalid
>  template  struct ElementSizeForType> {
>   ^~
> Makefile:32: recipe for target 'src/harvest/AnnotationList.o' failed
> make[1]: *** [src/harvest/AnnotationList.o] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/harvest-tools_1.3-1_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Tom Lee  (supplier of updated capnproto 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: Sat, 26 Aug 2017 10:54:20 -0700
Source: capnproto
Binary: libcapnp-0.6.1 libcapnp-dev capnproto
Architecture: source amd64
Version: 0.6.1-1
Distribution: unstable
Urgency: medium
Maintainer: Tom Lee 
Changed-By: Tom Lee 
Description:
 capnproto  - tool for working with the Cap'n Proto data interchange format
 libcapnp-0.6.1 - Cap'n Proto C++ library
 libcapnp-dev - Cap'n Proto C++ library (development files)
Closes: 809065 853342 853539 860960 866525
Changes:
 capnproto (0.6.1-1) unstable; urgency=medium
 .
   * Imported Upstream version 0.6.1 (Closes: #866525) which includes:
  - a fix for CVE-2017-7892 (Closes: #860960)
  - a fix for broken GCC 7 builds (Closes: #853342, #853539)
  - a possible fix for the hurd-i386 FTBFS in #804122
   * MultiArch support (Closes: #809065)
   * Clean up some Lintian gripes
   * Updated to debhelper 9, Standards-Version 4.0.0
   * License in debian/copyright changed from BSD-2-clause to MIT
Checksums-Sha1:
 66c459a3671a93938f32cf72fa4bfea7633d8d0b 2076 capnproto_0.6.1-1.dsc
 745dc4c60c02d0a664574a63ec85ef7a03c57676 1241927 capnproto_0.6.1.orig.tar.gz
 aa6a6a1af56e5fb8f3be88220475142cfc45f56e 8472 capnproto_0.6.1-1.debian.tar.xz
 0f4a68b0fd8ab34dcd51e5faaa7858cb5ede4d53 2317266 
capnproto-dbgsym_0.6.1-1_amd64.deb
 c515966aadfbc5969f93c0429c4bc6ef2194a369 7238 capnproto_0.6.1-1_amd64.buildinfo
 43a6e0783aedd2128dfbb85e0c57a3b5dd1134e8 228140 capnproto_0.6.1-1_amd64.deb
 3a785a2155d94e39f46

Bug#853440: marked as done (harvest-tools: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Mon, 28 Aug 2017 10:00:11 +
with message-id 
and subject line Bug#853539: fixed in capnproto 0.6.1-1
has caused the Debian Bug report #853539,
regarding harvest-tools: ftbfs with GCC-7
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.)


-- 
853539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853539
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:harvest-tools
Version: 1.3-1
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/harvest-tools_1.3-1_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
checking how to run the C++ preprocessor... g++ -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
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 google/protobuf/stubs/common.h usability... yes
checking google/protobuf/stubs/common.h presence... yes
checking for google/protobuf/stubs/common.h... yes
checking capnp/common.h usability... yes
checking capnp/common.h presence... yes
checking for capnp/common.h... yes
checking zlib.h usability... yes
checking zlib.h presence... yes
checking for zlib.h... yes
configure: creating ./config.status
config.status: creating Makefile
configure: WARNING: unrecognized options: --disable-silent-rules, 
--disable-maintainer-mode, --disable-dependency-tracking
make[1]: Leaving directory '/<>'
   dh_auto_build
make -j1
make[1]: Entering directory '/<>'
cd src; /usr/bin/protoc --cpp_out . harvest/pb/harvest.proto
[libprotobuf WARNING google/protobuf/compiler/parser.cc:547] No syntax 
specified for the proto file: harvest/pb/harvest.proto. Please use 'syntax = 
"proto2";' or 'syntax = "proto3";' to specify a syntax version. (Defaulted to 
proto2 syntax.)
cd src/harvest/capnp;export 
PATH=/usr/bin/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games;capnp
 compile -I /usr/include -oc++ harvest.capnp
g++ -c -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -std=c++11 -Isrc -I/usr/include -I/usr/include 
-Wdate-time -D_FORTIFY_SOURCE=2 -o src/harvest/AnnotationList.o 
src/harvest/AnnotationList.cpp
In file included from /usr/include/capnp/generated-header-support.h:31:0,
 from src/harvest/capnp/harvest.capnp.h:7,
 from src/harvest/AnnotationList.h:15,
 from src/harvest/AnnotationList.cpp:7:
/usr/include/capnp/layout.h:129:65: error: could not convert template argument 
'b' from 'bool' to 'capnp::Kind'
 template  struct ElementSizeForType> {
 ^
/usr/include/capnp/layout.h:129:66: error: template argument 1 is invalid
 template  struct ElementSizeForType> {
  ^~
Makefile:32: recipe for target 'src/harvest/AnnotationList.o' failed
make[1]: *** [src/harvest/AnnotationList.o] Error 1
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
debian/rules:8: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---
Source: capnproto
Source-Version

Bug#853342: marked as done (capnproto: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Mon, 28 Aug 2017 10:00:11 +
with message-id 
and subject line Bug#853539: fixed in capnproto 0.6.1-1
has caused the Debian Bug report #853539,
regarding capnproto: ftbfs with GCC-7
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.)


-- 
853539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853539
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:capnproto
Version: 0.5.3-2
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/capnproto_0.5.3-2_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
 template  struct ElementSizeForType> {
  ^~
Makefile:1779: recipe for target 'src/capnp/compiler/grammar.capnp.lo' failed
make[2]: *** [src/capnp/compiler/grammar.capnp.lo] Error 1
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 
-I./src -I./src -DKJ_HEADER_WARNINGS -DCAPNP_HEADER_WARNINGS 
-DCAPNP_INCLUDE_DIR=\"/usr/include\" -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DNDEBUG -D_KJ_BIGENDIAN=0 -D_KJ_64BIT=1 -c 
src/capnp/compiler/md5.c++ -o src/capnp/compiler/md5.o >/dev/null 2>&1
Makefile:1779: recipe for target 'src/capnp/schema.capnp.lo' failed
make[2]: *** [src/capnp/schema.capnp.lo] Error 1
Makefile:1779: recipe for target 'src/capnp/schema.lo' failed
make[2]: *** [src/capnp/schema.lo] Error 1
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 
-I./src -I./src -DKJ_HEADER_WARNINGS -DCAPNP_HEADER_WARNINGS 
-DCAPNP_INCLUDE_DIR=\"/usr/include\" -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DNDEBUG -D_KJ_BIGENDIAN=0 -D_KJ_64BIT=1 -c 
src/kj/debug.c++ -o src/kj/debug.o >/dev/null 2>&1
Makefile:1779: recipe for target 'src/capnp/arena.lo' failed
make[2]: *** [src/capnp/arena.lo] Error 1
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 
-I./src -I./src -DKJ_HEADER_WARNINGS -DCAPNP_HEADER_WARNINGS 
-DCAPNP_INCLUDE_DIR=\"/usr/include\" -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DNDEBUG -D_KJ_BIGENDIAN=0 -D_KJ_64BIT=1 -c 
src/kj/refcount.c++ -o src/kj/refcount.o >/dev/null 2>&1
Makefile:1779: recipe for target 'src/capnp/layout.lo' failed
make[2]: *** [src/capnp/layout.lo] Error 1
Makefile:1779: recipe for target 'src/capnp/message.lo' failed
make[2]: *** [src/capnp/message.lo] Error 1
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 
-I./src -I./src -DKJ_HEADER_WARNINGS -DCAPNP_HEADER_WARNINGS 
-DCAPNP_INCLUDE_DIR=\"/usr/include\" -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DNDEBUG -D_KJ_BIGENDIAN=0 -D_KJ_64BIT=1 -c 
src/kj/io.c++ -o src/kj/io.o >/dev/null 2>&1
Makefile:1779: recipe for target 'src/capnp/stringify.lo' failed
make[2]: *** [src/capnp/stringify.lo] Error 1
Makefile:1779: recipe for target 'src/capnp/dynamic.lo' failed
make[2]: *** [src/capnp/dynamic.lo] Error 1
Makefile:1779: recipe for target 'src/capnp/compiler/lexer.lo' failed
make[2]: *** [src/capnp/compiler/lexer.lo] Error 1
Makefile:1763: recipe for target 'src/capnp/compiler/module-loader.o' failed
make[2]: *** [src/capnp/compiler/module-loader.o] Error 1
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 
-I./src -I./src -DKJ_HEADER_WARNINGS -DCAPNP_HEADER_WARNINGS 
-DCAPNP_INCLUDE_DIR=\"/usr/include\" -g -O2