Bug#872305: diaspora: Package fails to install

[njoseph]

Package: diaspora
Version: 0.6.0.1+debian-1
Severity: serious


Dear maintainer,

Diaspora package installation fails with the following error:

Verifying we have all required libraries...
su: Permission denied
(Ignored)
There was an error while trying to write to 
`/usr/share/diaspora/.bundle/config`. It is likely that you need
to grant write permissions for that path.
dpkg: error processing package diaspora (--configure):
 subprocess installed post-installation script returned error exit status 23
Errors were encountered while processing:
 diaspora

The package is not usable due to this error.

Regards,
Joseph Nuthalapati



signature.asc
Description: OpenPGP digital signature

Processed: forwarded: libclang fails to link using gcc 7.1

[Debian Bug Tracking System]

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

> forwarded 853522 853523 853524 853525 
> https://bugs.llvm.org/show_bug.cgi?id=34140
Bug #853522 [src:llvm-toolchain-3.7] llvm-toolchain-3.7: ftbfs with GCC-7
Set Bug forwarded-to-address to '853523 853524 853525 
https://bugs.llvm.org/show_bug.cgi?id=34140'.
>
End of message, stopping processing here.

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

Processed: Re: Bug#868031: uim: FTBFS with Qt 5.9: Could not find feature reduce_exports.

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + fixed-in-experimental
Bug #868031 [src:uim] uim: FTBFS with Qt 5.9: Could not find feature 
reduce_exports.
Added tag(s) fixed-in-experimental.

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

Bug#868031: uim: FTBFS with Qt 5.9: Could not find feature reduce_exports.

[dai]

Control: tags -1 + fixed-in-experimental

patch applied in `debian-experimental` branch at git.debian.org.
-- 
Regards,
dai

GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E


signature.asc
Description: PGP signature

Bug#853531: reassigning bug to gcc

[Tiago Stürmer Daitx]

This has been fixed upstream [1], but there has been no new release so far.

[1] https://github.com/lxc/lxc/commit/66b66624fce21606d11f24f5b615776074d212ae

-thanks

Processed: Rising severity

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #868031 [src:uim] uim: FTBFS with Qt 5.9: Could not find feature 
reduce_exports.
Severity set to 'serious' from 'important'

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

Bug#872017: [Pkg-zsh-devel] Bug#872017: Bug#872017: zsh-syntax-highlighting FTBFS with zsh 5.4.1-1

[Daniel Shahaf]

Control: tags -1 pending

Daniel Shahaf wrote on Sun, 13 Aug 2017 18:14 +:
> Fixed upstream in 9523d6d49cb3d4db5bd84c3cec6168a2057fe3ab, already in
> experimental and due to be uploaded to sid soon.

Fixed in 0.5.0-2 and uploaded to DELAYED/5.

The upload has debian-rules-parses-dpkg-changelog and 
out-of-date-standards-version.
Both of these are already fixed in the 0.6 package, I just didn't
backport the fixes.  (Wanted to keep the 0.5.0-1..0.5.0-2
interdiff minimal.)

Cheers,

Daniel

Processed: Re: [Pkg-zsh-devel] Bug#872017: Bug#872017: zsh-syntax-highlighting FTBFS with zsh 5.4.1-1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #872017 [src:zsh-syntax-highlighting] zsh-syntax-highlighting FTBFS with 
zsh 5.4.1-1
Ignoring request to alter tags of bug #872017 to the same tags previously set

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

Bug#871367: fftw: diff for NMU version 2.1.5-4.2

[gregor herrmann]

Control: tags 871367 + pending

Dear maintainer,

I've prepared an NMU for fftw (versioned as 2.1.5-4.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Pink Floyd: Yet Another Movie/Round And Ar
diff -Nru fftw-2.1.5/debian/changelog fftw-2.1.5/debian/changelog
--- fftw-2.1.5/debian/changelog	2016-09-18 14:15:51.0 +0200
+++ fftw-2.1.5/debian/changelog	2017-08-16 03:22:14.0 +0200
@@ -1,3 +1,14 @@
+fftw (2.1.5-4.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "FTBFS: Unescaped left brace in regex is deprecated here":
+add patch fix-texi2html-perl526.patch to fix Perl 5.26 regexp
+warnings/errors.
+(Closes: #871367)
+  * Add support for DEB_BUILD_OPTIONS=nocheck in debian/rules.
+
+ -- gregor herrmann   Wed, 16 Aug 2017 03:22:14 +0200
+
 fftw (2.1.5-4.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru fftw-2.1.5/debian/patches/fix-texi2html-perl526.patch fftw-2.1.5/debian/patches/fix-texi2html-perl526.patch
--- fftw-2.1.5/debian/patches/fix-texi2html-perl526.patch	1970-01-01 01:00:00.0 +0100
+++ fftw-2.1.5/debian/patches/fix-texi2html-perl526.patch	2017-08-08 01:00:14.0 +0200
@@ -0,0 +1,35 @@
+Description: Fix perl 5.26 regexp warnings/errors
+Origin: vendor
+Bug-Debian: https://bugs.debian.org/871367
+Author: gregor herrmann 
+Last-Update: 2017-08-07
+
+--- a/doc/texi2html
 b/doc/texi2html
+@@ -839,7 +839,7 @@
+ s/\@refill\s+//g;
+ # other substitutions
+ _substitutions;
+-s/\@value{($VARRE)}/$value{$1}/eg;
++s/\@value\{($VARRE)}/$value{$1}/eg;
+ s/\@footnote\{/\@footnote$docu_doc\{/g; # mark footnotes, cf. pass 4
+ #
+ # analyze the tag again
+@@ -1169,7 +1169,7 @@
+ #
+ # xref
+ #
+-while (/\@(x|px|info|)ref{($XREFRE)(}?)/o) {
++while (/\@(x|px|info|)ref\{($XREFRE)(}?)/o) {
+ 	# note: Texinfo may accept other characters
+ 	($type, $nodes, $full) = ($1, $2, $3);
+ 	($before, $after) = ($`, $');
+@@ -1768,7 +1768,7 @@
+ while ($changed) {
+ 	$changed = 0;
+ 	$done = '';
+-	while (/\@(\w+){([^\{\}]+)}/) {
++	while (/\@(\w+)\{([^\{\}]+)}/) {
+ 	$text = _style($1, $2);
+ 	if ($text) {
+ 		$_ = "$`$text$'";
diff -Nru fftw-2.1.5/debian/patches/series fftw-2.1.5/debian/patches/series
--- fftw-2.1.5/debian/patches/series	2016-09-18 14:06:40.0 +0200
+++ fftw-2.1.5/debian/patches/series	2017-08-08 00:46:34.0 +0200
@@ -5,3 +5,4 @@
 info-syntax
 fix-texi2html-perl522.patch
 perl-cwd-in-inc.patch
+fix-texi2html-perl526.patch
diff -Nru fftw-2.1.5/debian/rules fftw-2.1.5/debian/rules
--- fftw-2.1.5/debian/rules	2016-07-11 21:59:11.0 +0200
+++ fftw-2.1.5/debian/rules	2017-08-08 01:10:18.0 +0200
@@ -30,17 +30,21 @@
 	# single precision
 	F77=gfortran CFLAGS="$(CFLAGS)" CC=mpicc ./configure $(CONFFLAGS) --enable-float --enable-type-prefix $(ARCHCONFFLAGS)
 	$(MAKE)
+ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
 	#$(MAKE) -C tests check
 	./tests/fftw_test  -t -e -v -p 1024 -x 1
 	./tests/rfftw_test -t -e -v -p 1024 -x 1
+endif
 	$(MAKE) install DESTDIR=$(CURDIR)/debian/tmp-single
 	$(MAKE) clean
 	# double precision
 	F77=gfortran CFLAGS="$(CFLAGS)" CC=mpicc ./configure $(CONFFLAGS) $(ARCHCONFFLAGS)
 	$(MAKE)
+ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
 	#$(MAKE) -C tests check
 	./tests/fftw_test  -t -e -v -p 1024 -x 1
 	./tests/rfftw_test -t -e -v -p 1024 -x 1
+endif
 	$(MAKE) install DESTDIR=$(CURDIR)/debian/tmp-double
 	touch build-arch-stamp
 


signature.asc
Description: Digital Signature

Processed: fftw: diff for NMU version 2.1.5-4.2

[Debian Bug Tracking System]

Processing control commands:

> tags 871367 + pending
Bug #871367 [src:fftw] fftw: FTBFS: Unescaped left brace in regex is deprecated 
here (and will be fatal in Perl 5.30), passed through in regex; marked by <-- 
HERE in m/\@(\w+){ <-- HERE ([^\{\}]+)}/ at texi2html line 1771.
Added tag(s) pending.

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

Bug#871818: debian-zh-faq: diff for NMU version 1.13+nmu1

[gregor herrmann]

Control: tags 871818 + pending

Dear maintainer,

I've prepared an NMU for debian-zh-faq (versioned as 1.13+nmu1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: J.J. Cale: I Got The Same Old Blues
diff -Nru debian-zh-faq-1.13/debian/changelog debian-zh-faq-1.13+nmu1/debian/changelog
--- debian-zh-faq-1.13/debian/changelog	2012-04-29 06:34:07.0 +0200
+++ debian-zh-faq-1.13+nmu1/debian/changelog	2017-08-16 03:47:41.0 +0200
@@ -1,3 +1,12 @@
+debian-zh-faq (1.13+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "debian-zh-faq FTBFS with perl 5.26":
+escape literal left braces in regexps in ./totw.pl
+(Closes: #871818)
+
+ -- gregor herrmann   Wed, 16 Aug 2017 03:47:41 +0200
+
 debian-zh-faq (1.13) unstable; urgency=low
 
   * Fix "FTBFS: ! LaTeX Error: File `url.sty' not found." (Closes: #60)
diff -Nru debian-zh-faq-1.13/totw.pl debian-zh-faq-1.13+nmu1/totw.pl
--- debian-zh-faq-1.13/totw.pl	2011-06-04 10:54:36.0 +0200
+++ debian-zh-faq-1.13+nmu1/totw.pl	2017-08-12 18:12:07.0 +0200
@@ -36,7 +36,7 @@
 s/ªA¨Í¾¹/¦øªA¾¹/g;
 
 # Riser §â "server" ¥s§@ "ªA°Èµ{§Ç" ¡K¡K
-s/ªA°Èµ{§Ç/¦øªA¾¹/g;
+s/ªA°Èµ\{§Ç/¦øªA¾¹/g;
 
 1 while (s/^((?:[\x00-\x7f]|[\x80-\xff].)*)­pºâ¾÷/$1¹q¸£/);
 1 while (s/^((?:[\x00-\x7f]|[\x80-\xff].)*)¤º®Ö/$1®Ö¤ß/);
@@ -68,11 +68,11 @@
 s/\\>/ÀɮצWºÙ/g;
 s/\\>/³]©wÀÉ/g;
 s/\\>/³]©w/g;
-s/\\>/µ{¦¡/g;
-s/«È¤áµ{§Ç/«È¤áµ{¦¡/g;
+s/\\>/µ{¦¡/g;
+s/«È¤áµ\{§Ç/«È¤áµ{¦¡/g;
 s/\\>/¸ê®Æ/g;
 s/\\>/¸ê°T/g;
-s/\\>/¹w³]/g;
+s/\\>/¹w³]/g;
 s/\\>/¹w³]/g;
 s/\\>/¹h¹D/g;
 s/\\>/±Ò°Ê/g;


signature.asc
Description: Digital Signature

Processed: debian-zh-faq: diff for NMU version 1.13+nmu1

[Debian Bug Tracking System]

Processing control commands:

> tags 871818 + pending
Bug #871818 [src:debian-zh-faq] debian-zh-faq FTBFS with perl 5.26
Added tag(s) pending.

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

Bug#872297: tome needs a rebuild using GCC 7

[Andreas Beckmann]

Control: reassign -1 release.debian.org
Control: severity -1 normal
Control: retitle -1 nmu: tome_2.4~0.git.2015.12.29-1.1
Control: user release.debian@packages.debian.org
Control: usertags -1 binnmu

On Wed, 16 Aug 2017 00:00:02 +0200 Matthias Klose  wrote:
> Package: src:tome
> Version: 2.4~0.git.2015.12.29-1.1
> Severity: serious
> Tags: sid buster
> 
> buster won't ship with GCC 6 (libasan3). Please rebuild the package.

this can be binNMUed, too

nmu tome_2.4~0.git.2015.12.29-1.1 . ANY . unstable . -m "Rebuild against 
libasan4"


Andreas

Processed (with 2 errors): Re: tome needs a rebuild using GCC 7

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 release.debian.org
Bug #872297 [src:tome] tome needs a rebuild using GCC 7
Bug reassigned from package 'src:tome' to 'release.debian.org'.
No longer marked as found in versions tome/2.4~0.git.2015.12.29-1.1.
Ignoring request to alter fixed versions of bug #872297 to the same values 
previously set
> severity -1 normal
Bug #872297 [release.debian.org] tome needs a rebuild using GCC 7
Severity set to 'normal' from 'serious'
> retitle -1 nmu: tome_2.4~0.git.2015.12.29-1.1
Bug #872297 [release.debian.org] tome needs a rebuild using GCC 7
Changed Bug title to 'nmu: tome_2.4~0.git.2015.12.29-1.1' from 'tome needs a 
rebuild using GCC 7'.
> user release.debian@packages.debian.org
Unknown command or malformed arguments to command.

> usertags -1 binnmu
Unknown command or malformed arguments to command.


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

Bug#853685: marked as done (torcs: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Wed, 16 Aug 2017 01:23:06 +
with message-id 
and subject line Bug#853685: fixed in torcs 1.3.7+dfsg-4
has caused the Debian Bug report #853685,
regarding torcs: 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.)


-- 
853685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853685
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:torcs
Version: 1.3.3+dfsg-0.4
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/torcs_1.3.3+dfsg-0.4_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

[...]
   ~^~~~
ANN.cpp:1215:8: warning: ignoring return value of 'size_t fread(void*, size_t, 
size_t, FILE*)', declared with attribute warn_unused_result [-Wunused-result]
   fread(, sizeof(int), 1, f);
   ~^
ANN.cpp:1226:8: warning: ignoring return value of 'size_t fread(void*, size_t, 
size_t, FILE*)', declared with attribute warn_unused_result [-Wunused-result]
   fread(_type, sizeof(int), 1, f);
   ~^~~~
ANN.cpp:1239:8: warning: ignoring return value of 'size_t fread(void*, size_t, 
size_t, FILE*)', declared with attribute warn_unused_result [-Wunused-result]
   fread(l->c, size, sizeof(Connection), f);
   ~^~~
ANN.cpp: In function 'bool CheckMatchingToken(const char*, StringBuffer*, 
FILE*)':
ANN.cpp:1155:7: warning: ignoring return value of 'size_t fread(void*, size_t, 
size_t, FILE*)', declared with attribute warn_unused_result [-Wunused-result]
  fread(buf->c, sizeof(char), l, f);
  ~^~~~
g++ -shared -o liblearning.so policy.o ann_policy.o List.o string_utils.o 
Distribution.o MathFunctions.o ANN.o 
-L/<>/torcs-1.3.3+dfsg/export/lib -Wl,-z,relro -L/usr/lib/ -lalut 
-lvorbisfile -L/usr/lib   
 Exporting liblearning.so to 
/<>/torcs-1.3.3+dfsg/export/lib/liblearning.so
make[5]: Leaving directory '/<>/torcs-1.3.3+dfsg/src/libs/learning'
make[5]: Entering directory 
'/<>/torcs-1.3.3+dfsg/src/libs/portability'
make[5]: Nothing to be done for 'compil'.
make[5]: Leaving directory '/<>/torcs-1.3.3+dfsg/src/libs/portability'
make[5]: Entering directory '/<>/torcs-1.3.3+dfsg/src/libs/math'
make[5]: Nothing to be done for 'compil'.
make[5]: Leaving directory '/<>/torcs-1.3.3+dfsg/src/libs/math'
make[5]: Entering directory 
'/<>/torcs-1.3.3+dfsg/src/libs/musicplayer'
gcc -E -Wdate-time -D_FORTIFY_SOURCE=2 -M -D__DEPEND__ 
-I/<>/torcs-1.3.3+dfsg/export/include 
-I/<>/torcs-1.3.3+dfsg -D_DEFAULT_SOURCE -DSHM -DHAVE_CONFIG_H   
SoundStream.cpp OggSoundStream.cpp OpenALMusicPlayer.cpp musicplayer.cpp > 
.depend
g++ -I/<>/torcs-1.3.3+dfsg/export/include 
-I/<>/torcs-1.3.3+dfsg -g -O2 
-fdebug-prefix-map=/<>/torcs-1.3.3+dfsg=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -fPIC -fno-strict-aliasing -O2 
-DUSE_RANDR_EXT -DGL_GLEXT_PROTOTYPES -Wall -fPIC -fno-strict-aliasing -O2 
-DUSE_RANDR_EXT -DGL_GLEXT_PROTOTYPES -Wdate-time -D_FORTIFY_SOURCE=2 
-D_DEFAULT_SOURCE -DSHM -DHAVE_CONFIG_H  -c SoundStream.cpp
g++ -I/<>/torcs-1.3.3+dfsg/export/include 
-I/<>/torcs-1.3.3+dfsg -g -O2 
-fdebug-prefix-map=/<>/torcs-1.3.3+dfsg=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -fPIC -fno-strict-aliasing -O2 
-DUSE_RANDR_EXT -DGL_GLEXT_PROTOTYPES -Wall -fPIC -fno-strict-aliasing -O2 
-DUSE_RANDR_EXT -DGL_GLEXT_PROTOTYPES -Wdate-time -D_FORTIFY_SOURCE=2 

Bug#872201: libc-bin: sometimes throws std::logic_error while processing triggers

[Andreas Beckmann]

[ adding apt@, therefore quoting fully ]

On 2017-08-15 22:56, Aurelien Jarno wrote:
> control: tag - 1 + help
> control: tag - 1 + moreinfo
> 
> On 2017-08-15 09:58, Andreas Beckmann wrote:
>> Package: libc-bin
>> Version: 2.24-14
>> Severity: serious
>> User: debian...@lists.debian.org
>> Usertags: piuparts
>>
>> Hi,
>>
>> during several tests with piuparts in sid I noticed spurious and
>> unreproducible errors while processing libc-bin triggers.
>> Often apt-get just exits with an error code (but no error message
>> at all) after processing the triggers.
>> A few times I also get an error message about an uncaught exception.
>> These failures usually go away after rerunning the test.
>>
>> >From the attached log (scroll to the bottom...):
>>
>>   Processing triggers for libc-bin (2.24-14) ...
>>   terminate called after throwing an instance of 'std::logic_error'
>> what():  basic_string::_M_construct null not valid
> 
> What make you think it's an issue in libc-bin? The trigger processing
> code just does:
> 
> if [ "$1" = "triggered" ] || [ "$1" = "configure" ]; then
>   ldconfig || ldconfig --verbose
>   exit 0
> fi
> 
> And there is no C++ code in ldconfig. Moreover even if ldconfig fails
> the error is ignored and the install should not stop.

OK, that probably leaves dpkg (no C++ either) and apt-get as the call
chain to the trigger processing ... adding apt@ to the loop.
#871275 could be a candidate, i.e. a g++7 rebuild might fix it.

I reran the test where I attached the logfile yesterday repeatedly for
100 times with no failure. But I could probably dig out a dozen of
similar failures from other piuparts tests. (These failures will be
retried frequently, so will eventually succeed.)

If there is some way to get more debug output for this problem, I could
enable that globally in my piuparts instance.


Andreas

Bug#853529: marked as done (lordsawar: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Wed, 16 Aug 2017 00:35:17 +
with message-id 
and subject line Bug#853529: fixed in lordsawar 0.3.1-3
has caused the Debian Bug report #853529,
regarding lordsawar: 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.)


-- 
853529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:lordsawar
Version: 0.3.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/lordsawar_0.3.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

[...]
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../.. -pthread 
-I/usr/include/gtkmm-3.0 -I/usr/lib/x86_64-linux-gnu/gtkmm-3.0/include 
-I/usr/include/atkmm-1.6 -I/usr/include/gtk-3.0/unix-print 
-I/usr/include/gdkmm-3.0 -I/usr/lib/x86_64-linux-gnu/gdkmm-3.0/include 
-I/usr/include/giomm-2.4 -I/usr/lib/x86_64-linux-gnu/giomm-2.4/include 
-I/usr/include/pangomm-1.4 -I/usr/lib/x86_64-linux-gnu/pangomm-1.4/include 
-I/usr/include/glibmm-2.4 -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include 
-I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/cairomm-1.0 
-I/usr/lib/x86_64-linux-gnu/cairomm-1.0/include -I/usr/include/cairo 
-I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/in
 clude/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml++-2.6 
-I/usr/lib/x86_64-linux-gnu/libxml++-2.6/include -I/usr/include/libxml2 
-I/usr/include/glibmm-2.4 -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include 
-I../../src -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wshadow -Wextra -pedantic -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c stack-info-tip.cpp -o stack-info-tip.o >/dev/null 
2>&1
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../.. -pthread 
-I/usr/include/gtkmm-3.0 -I/usr/lib/x86_64-linux-gnu/gtkmm-3.0/include 
-I/usr/include/atkmm-1.6 -I/usr/include/gtk-3.0/unix-print 
-I/usr/include/gdkmm-3.0 -I/usr/lib/x86_64-linux-gnu/gdkmm-3.0/include 
-I/usr/include/giomm-2.4 -I/usr/lib/x86_64-linux-gnu/giomm-2.4/include 
-I/usr/include/pangomm-1.4 -I/usr/lib/x86_64-linux-gnu/pangomm-1.4/include 
-I/usr/include/glibmm-2.4 -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include 
-I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/cairomm-1.0 
-I/usr/lib/x86_64-linux-gnu/cairomm-1.0/include -I/usr/include/cairo 
-I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/in
 clude/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include 
-I/usr/include/gdk-pixbuf-2.0 

Bug#853325: marked as done (berusky2: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Wed, 16 Aug 2017 00:04:03 +
with message-id 
and subject line Bug#853325: fixed in berusky2 0.10-6
has caused the Debian Bug report #853325,
regarding berusky2: 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.)


-- 
853325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853325
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:berusky2
Version: 0.10-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/berusky2_0.10-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

[...]
   __bos (__s), __fmt, __va_arg_pack ());
   ^
komat/Berusky3d_load.cpp:315:6: warning: '%d' directive writing between 1 and 
10 bytes into a region of size 0 [-Wformat-overflow=]
 void ber_materialy_rozkopiruj(G_KONFIG * p_ber, GAME_MESH_OLD * p_mesh,
  ^~~~
komat/Berusky3d_load.cpp:315:6: note: directive argument in the range [0, 
2147483647]
In file included from /usr/include/stdio.h:938:0,
 from komat/Berusky3d_load.cpp:4:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:34:43: note: format output between 
3 and 61 bytes into a destination of size 50
   __bos (__s), __fmt, __va_arg_pack ());
   ^
Makefile:1262: recipe for target 'Menu.o' failed
make[4]: *** [Menu.o] Error 1
komat/Load.cpp: In function 'EDIT_OBJEKT* slep_objekty(EDIT_OBJEKT*, 
EDIT_OBJEKT*)':
komat/Load.cpp:418:14: warning: '%s' directive writing between 0 and 49 bytes 
into a region of size 0 [-Wformat-overflow=]
 EDIT_OBJEKT *slep_objekty(EDIT_OBJEKT * p_obj1, EDIT_OBJEKT * p_obj2)
  ^~~~
In file included from /usr/include/stdio.h:938:0,
 from kofola/apak_types.h:5,
 from kofola/Apak.h:4,
 from komat/Load.cpp:6:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:34:43: note: format output between 
2 and 100 bytes into a destination of size 50
   __bos (__s), __fmt, __va_arg_pack ());
   ^
komat/Load.cpp: In function 'EDIT_MESH_POLY* lo_nahraj_poly_list(char*, int*, 
EDIT_TEXT*, EDIT_MATERIAL**, int)':
komat/Load.cpp:3148:17: warning: may write format character 'a' at offset 3 
past the end of the destination [-Wformat-overflow=]
 EDIT_MESH_POLY *lo_nahraj_poly_list(char *p_file, int *p_polynum,
 ^~~
komat/Load.cpp:3148:17: note: directive argument in the range [0, 2147483647]
In file included from /usr/include/stdio.h:938:0,
 from kofola/apak_types.h:5,
 from kofola/Apak.h:4,
 from komat/Load.cpp:6:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:34:43: note: format output between 
5 and 63 bytes into a destination of size 50
   __bos (__s), __fmt, __va_arg_pack ());
   ^
make[4]: Leaving directory '/<>/src'
Makefile:495: recipe for target 'all-recursive' failed
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory '/<>'
Makefile:406: recipe for target 'all' failed
make[2]: *** [all] Error 2
make[2]: Leaving directory '/<>'
dh_auto_build: make -j64 returned exit code 2
debian/rules:13: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
debian/rules:6: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: 

Bug#872263: linux-image-4.11.0-1-amd64-dbg: file overwrite error upgrading from stretch-backports

[Ben Hutchings]

On Tue, 2017-08-15 at 14:59 +0200, Andreas Beckmann wrote:
> Package: linux-image-4.11.0-1-amd64-dbg
> Version: 4.11.6-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> Control: affects -1 + linux-image-amd64-dbg
> 
> Hi,
> 
> during a test with piuparts I noticed your package fails to upgrade from
> 'stretch-backports'.
> It installed fine in 'stretch-backports', then the upgrade to 'buster' 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 linux-image-4.11.0-1-amd64-dbg.
>   Preparing to unpack .../linux-image-4.11.0-1-amd64-dbg_4.11.6-1_amd64.deb 
> ...
>   Unpacking linux-image-4.11.0-1-amd64-dbg (4.11.6-1) ...
>   dpkg: error processing archive 
> /var/cache/apt/archives/linux-image-4.11.0-1-amd64-dbg_4.11.6-1_amd64.deb 
> (--unpack):
>    trying to overwrite 
> '/usr/lib/debug/.build-id/25/99e5c063eeb45c3b0068e66a8251a66f313afa.debug', 
> which is also in package linux-image-4.11.0-0.bpo.1-amd64-dbg 4.11.6-1~bpo9+1

This filename is a hash of file contents, so this indicates that at
least one file was identical for the two builds.  Binary
reproducibility has bitten us in the ass!

We only create .build-id links for user-space code (vDSOs), so let's
compare those:

[linux-image-4.11.0-1-amd64-dbg_4.11.6-1_amd64.deb]
lrwxrwxrwx 1 ben ben 47 Jun 20 00:25 
foo/usr/lib/debug/.build-id/22/1234d10e2a0342be17ce0b885f6fb4d8ea3330.debug -> 
../../lib/modules/4.11.0-1-amd64/vdso/vdso32.so
lrwxrwxrwx 1 ben ben 47 Jun 20 00:25 
foo/usr/lib/debug/.build-id/25/99e5c063eeb45c3b0068e66a8251a66f313afa.debug -> 
../../lib/modules/4.11.0-1-amd64/vdso/vdso64.so
lrwxrwxrwx 1 ben ben 48 Jun 20 00:25 
foo/usr/lib/debug/.build-id/66/ff5d513f55db31f2802e037593555810452e02.debug -> 
../../lib/modules/4.11.0-1-amd64/vdso/vdsox32.so
4cdc4e5658ed934b8d3cfe22ddfe4aa1474acfddfc8a18a8a2c282f5bb0431be  
foo/usr/lib/debug/lib/modules/4.11.0-1-amd64/vdso/vdso32.so
6e763e4f0677224b323164719495119c6d834a287a18c580a05eb2a3b5a2c1cf  
foo/usr/lib/debug/lib/modules/4.11.0-1-amd64/vdso/vdso64.so
b8374d512446748311b333701bca11c5c8ed4c6140579d9c0de4e9d3b1a67821  
foo/usr/lib/debug/lib/modules/4.11.0-1-amd64/vdso/vdsox32.so

[linux-image-4.11.0-0.bpo.1-amd64-dbg_4.11.6-1~bpo9+1_amd64.deb]
lrwxrwxrwx 1 ben ben 53 Jul  9 19:22 
bar/usr/lib/debug/.build-id/25/99e5c063eeb45c3b0068e66a8251a66f313afa.debug -> 
../../lib/modules/4.11.0-0.bpo.1-amd64/vdso/vdso64.so
lrwxrwxrwx 1 ben ben 54 Jul  9 19:22 
bar/usr/lib/debug/.build-id/66/ff5d513f55db31f2802e037593555810452e02.debug -> 
../../lib/modules/4.11.0-0.bpo.1-amd64/vdso/vdsox32.so
lrwxrwxrwx 1 ben ben 53 Jul  9 19:22 
bar/usr/lib/debug/.build-id/6f/cb3e7c92bce418d52f5f5d6710222ae5377723.debug -> 
../../lib/modules/4.11.0-0.bpo.1-amd64/vdso/vdso32.so
6dcde68bba7f9939cbc521eb262842011ed512ab473848fe94ea7d2639c6d839  
bar/usr/lib/debug/lib/modules/4.11.0-0.bpo.1-amd64/vdso/vdso32.so
6e763e4f0677224b323164719495119c6d834a287a18c580a05eb2a3b5a2c1cf  
bar/usr/lib/debug/lib/modules/4.11.0-0.bpo.1-amd64/vdso/vdso64.so
b8374d512446748311b333701bca11c5c8ed4c6140579d9c0de4e9d3b1a67821  
bar/usr/lib/debug/lib/modules/4.11.0-0.bpo.1-amd64/vdso/vdsox32.so

So the amd64 vDSO and x32 compat vDSO are identical when built in
unstable and stretch-backports, but the i386 compat vDSO is not (for
some reason the debug filename mapping isn't being applied there).

>   Preparing to unpack .../linux-image-amd64-dbg_4.11+82_amd64.deb ...
>   Unpacking linux-image-amd64-dbg (4.11+82) over (4.11+82~bpo9+1) ...
>   Errors were encountered while processing:
>    /var/cache/apt/archives/linux-image-4.11.0-1-amd64-dbg_4.11.6-1_amd64.deb

We can probably work around this in src:linux by including the kernel
release string in the vDSO, so the backports build will always be
different.

Still, it seems like there is a wider problem here: if the exact same
code is ever built in two unrelated packages then their debug info
packages will conflict even if the regular binary packages don't.

Ben.

-- 
Ben Hutchings
Nothing is ever a complete failure; it can always serve as a bad
example.


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

Bug#867477: marked as done (poppler: CVE-2017-9865 stack-based overflow leading to denial-of-service)

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2017 23:00:12 +
with message-id 
and subject line Bug#867477: fixed in poppler 0.57.0-1
has caused the Debian Bug report #867477,
regarding poppler: CVE-2017-9865 stack-based overflow leading to 
denial-of-service
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.)


-- 
867477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867477
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: poppler
X-Debbugs-CC: t...@security.debian.org 
secure-testing-t...@lists.alioth.debian.org
Severity: grave
Tags: security patch upstream
Forwarded: https://bugs.freedesktop.org/show_bug.cgi?id=100774

Hi,

the following vulnerability was published for poppler.

CVE-2017-9865[0]:
| The function GfxImageColorMap::getGray in GfxState.cc in Poppler 0.54.0
| allows remote attackers to cause a denial of service (stack-based
| buffer over-read and application crash) via a crafted PDF document,
| related to missing color-map validation in ImageOutputDev.cc.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-9865
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9865

Please adjust the affected versions in the BTS as needed.


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: poppler
Source-Version: 0.57.0-1

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

Debian distribution maintenance software
pp.
Emilio Pozuelo Monfort  (supplier of updated poppler 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, 14 Aug 2017 22:19:15 +0200
Source: poppler
Binary: libpoppler68 libpoppler-dev libpoppler-private-dev libpoppler-glib8 
libpoppler-glib-dev libpoppler-glib-doc gir1.2-poppler-0.18 libpoppler-qt4-4 
libpoppler-qt4-dev libpoppler-qt5-1 libpoppler-qt5-dev libpoppler-cpp0v5 
libpoppler-cpp-dev poppler-utils
Architecture: source amd64 all
Version: 0.57.0-1
Distribution: experimental
Urgency: medium
Maintainer: Debian freedesktop.org maintainers 

Changed-By: Emilio Pozuelo Monfort 
Description:
 gir1.2-poppler-0.18 - GObject introspection data for poppler-glib
 libpoppler-cpp-dev - PDF rendering library -- development files (CPP interface)
 libpoppler-cpp0v5 - PDF rendering library (CPP shared library)
 libpoppler-dev - PDF rendering library -- development files
 libpoppler-glib-dev - PDF rendering library -- development files (GLib 
interface)
 libpoppler-glib-doc - PDF rendering library -- documentation for the GLib 
interface
 libpoppler-glib8 - PDF rendering library (GLib-based shared library)
 libpoppler-private-dev - PDF rendering library -- private development files
 libpoppler-qt4-4 - PDF rendering library (Qt 4 based shared library)
 libpoppler-qt4-dev - PDF rendering library -- development files (Qt 4 
interface)
 libpoppler-qt5-1 - PDF rendering library (Qt 5 based shared library)
 libpoppler-qt5-dev - PDF rendering library -- development files (Qt 5 
interface)
 libpoppler68 - PDF rendering library
 poppler-utils - PDF utilities (based on Poppler)
Closes: 860955 863759 864009 864010 865679 865680 867477
Changes:
 poppler (0.57.0-1) experimental; urgency=medium
 .
   [ Pino Toscano ]
   * Update Vcs-* fields.
   * Add a lintian override for the "breaks-without-version xpdf-common" in
 poppler-utils, as it is making sure to clean up xpdf-common for upgrades
 to Buster.
 .
   [ Emilio Pozuelo Monfort ]
   * New upstream release. Closes: #860955.
   * Fixes:
 CVE-2017-9406: memory leak parsing XRef entries. Closes: #864010.
 CVE-2017-9408: memory leak in Object::initArray. Closes: #864009.
 CVE-2017-9775: stack buffer overflow in GfxState.cc. Closes: #865680.
 CVE-2017-9776: integer overflow leading to heap buffer overflow
 in 

Bug#871929: marked as done (polymake FTBFS with gcc 7)

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2017 22:49:43 +
with message-id 
and subject line Bug#871929: fixed in polymake 3.1-5
has caused the Debian Bug report #871929,
regarding polymake 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.)


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

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

...
In file included from 
/build/1st/polymake-3.1/include/core/polymake/internal/type_manip.h:26:0,
 from 
/build/1st/polymake-3.1/include/core/polymake/internal/operations_basic_defs.h:20,
 from 
/build/1st/polymake-3.1/include/core/polymake/internal/comparators_basic_defs.h:20,
 from 
/build/1st/polymake-3.1/include/core/polymake/internal/comparators_ops.h:23,
 from /build/1st/polymake-3.1/include/core/polymake/Series.h:24,
 from 
/build/1st/polymake-3.1/include/core/polymake/internal/sparse.h:20,
 from 
/build/1st/polymake-3.1/include/core/polymake/GenericIO.h:20,
 from 
/build/1st/polymake-3.1/include/core/polymake/perl/Value.h:20,
 from 
/build/1st/polymake-3.1/include/core/polymake/perl/glue.h:66,
 from RuleGraph.xxs:17:
/usr/include/c++/7/limits: In instantiation of 'struct 
std::numeric_limits':
/build/1st/polymake-3.1/include/core/polymake/internal/type_manip.h:839:113:   
required by substitution of 'template typename 
std::enable_if::is_specialized, char (&)[2]>::type 
pm::object_classifier::_impl::analyzer_f(const T*, 
pm::object_classifier::_impl::bait*) [with T = pm::graph::NodeMapBase]'
/build/1st/polymake-3.1/include/core/polymake/internal/type_manip.h:848:47:   
required from 'const int pm::object_classifier::kind_of::value'
/build/1st/polymake-3.1/include/core/polymake/internal/type_manip.h:983:8:   
required from 'struct pm::spec_object_traits'
/build/1st/polymake-3.1/include/core/polymake/internal/type_manip.h:1045:1:   
required by substitution of 'template static typename 
pm::size_discriminant<(2 - std::is_same::value)>::type 
pm::has_persistent_type_impl::Test(const T2*, typename T2::persistent_type*) [with T2 = 
pm::spec_object_traits]'
/build/1st/polymake-3.1/include/core/polymake/internal/type_manip.h:341:51:   [ 
skipping 2 instantiation contexts, use -ftemplate-backtrace-limit=0 to disable ]
/build/1st/polymake-3.1/include/core/polymake/internal/type_manip.h:1045:1:   
required from 'struct 
pm::has_persistent_type'
/build/1st/polymake-3.1/include/core/polymake/internal/type_manip.h:1080:8:   
required from 'struct pm::redirect_object_traits'
/build/1st/polymake-3.1/include/core/polymake/internal/type_manip.h:1267:8:   
required from 'struct pm::isomorphic_types'
/build/1st/polymake-3.1/include/core/polymake/internal/iterators.h:687:86:   
required from 'struct 
pm::isomorphic_to_container_of, int, pm::is_set, true>'
/build/1st/polymake-3.1/include/core/polymake/Bitset.h:209:14:   required by 
substitution of 'template pm::Bitset::Bitset(const 
TContainer&) [with TContainer = pm::EmbeddedList;  = ]'
/build/1st/polymake-3.1/include/core/polymake/Graph.h:712:39:   required from 
here
/usr/include/c++/7/limits:317:7: error: invalid abstract return type 
'pm::graph::NodeMapBase'
   min() _GLIBCXX_USE_NOEXCEPT { return _Tp(); }
   ^~~
In file included from 
/build/1st/polymake-3.1/include/core-wrappers/polymake/Graph.h:20:0,
 from RuleGraph.xxs:21:
/build/1st/polymake-3.1/include/core/polymake/Graph.h:497:8: note:   because 
the following virtual functions are pure within 'pm::graph::NodeMapBase':
 struct NodeMapBase {
^~~
/build/1st/polymake-3.1/include/core/polymake/Graph.h:505:17: note: virtual 
void pm::graph::NodeMapBase::init()
virtual void init()=0;
 ^~~~
/build/1st/polymake-3.1/include/core/polymake/Graph.h:506:17: note: virtual 
void pm::graph::NodeMapBase::reset(int)
virtual void reset(int n=0)=0;
 ^
/build/1st/polymake-3.1/include/core/polymake/Graph.h:507:17: note: virtual 
void pm::graph::NodeMapBase::resize(size_t, int, int)
virtual 

Processed: tagging 872201

[Debian Bug Tracking System]

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

> tags 872201 + moreinfo
Bug #872201 [libc-bin] libc-bin: sometimes throws std::logic_error while 
processing triggers
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Processed: tagging 872201

[Debian Bug Tracking System]

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

> tags 872201 + help
Bug #872201 [libc-bin] libc-bin: sometimes throws std::logic_error while 
processing triggers
Added tag(s) help.
> thanks
Stopping processing here.

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

Bug#871349: marked as done (ispell-uk: FTBFS: The encoding pragma is no longer supported at ../../bin/verb_reverse.pl line 12.)

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2017 22:19:24 +
with message-id 
and subject line Bug#871349: fixed in ispell-uk 1.7.1-2
has caused the Debian Bug report #871349,
regarding ispell-uk: FTBFS: The encoding pragma is no longer supported at 
../../bin/verb_reverse.pl line 12.
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.)


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

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> mkdir /<>/debian/locale
> localedef -i uk_UA -f KOI8-U /<>/debian/locale/uk_UA
> localedef -i uk_UA -f UTF-8 /<>/debian/locale/uk_UA.UTF-8
> touch locale-stamp
> LOCPATH=/<>/debian/locale /usr/bin/make ispell
> make[1]: Entering directory '/<>'
> /usr/bin/make -C src/Affix
> make[2]: Entering directory '/<>/src/Affix'
> ../../bin/verb_reverse.pl < uk.aff.VERB > uk.aff.VERB_REV
> The encoding pragma is no longer supported at ../../bin/verb_reverse.pl line 
> 12.
> BEGIN failed--compilation aborted at ../../bin/verb_reverse.pl line 12.
> Makefile:21: recipe for target 'uk.aff.VERB_REV' failed
> make[2]: *** [uk.aff.VERB_REV] Error 255

The full build log is available from:
   http://aws-logs.debian.net/2017/08/07/ispell-uk_1.7.1-1_unstable.log

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

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

We believe that the bug you reported is fixed in the latest version of
ispell-uk, 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.
Євгеній Мещеряков  (supplier of updated ispell-uk 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, 15 Aug 2017 23:42:55 +0200
Source: ispell-uk
Binary: iukrainian wukrainian myspell-uk aspell-uk
Architecture: source
Version: 1.7.1-2
Distribution: unstable
Urgency: medium
Maintainer: Євгеній Мещеряков 
Changed-By: Євгеній Мещеряков 
Description:
 aspell-uk  - Ukrainian dictionary for GNU Aspell
 iukrainian - Ukrainian dictionary for ispell
 myspell-uk - Ukrainian dictionary for myspell
 wukrainian - Ukrainian dictionary words for /usr/share/dict
Closes: 871349
Changes:
 ispell-uk (1.7.1-2) unstable; urgency=medium
 .
   [ gregor herrmann ]
   * Fix "FTBFS: The encoding pragma is no longer supported at
 ../../bin/verb_reverse.pl line 12.":
 Add perl5.26-encoding.patch: replace "use encoding" with "use open" in
 perl helper scripts. Additionally run ispell build in debian/rules under
 C.UTF-8. (Closes: #871349)
 .
   [ Євгеній Мещеряков ]
   * Add debian/gbp.conf with correct branch for this package (1.7.1-support)
Checksums-Sha1:
 c65706ffb185f4f6e0eff075224e08e00646f914 2115 ispell-uk_1.7.1-2.dsc
 4c93fbc923b9d020e47fd82aed11ba49ac2183d2 4804 ispell-uk_1.7.1-2.debian.tar.xz
 d0b62ad6f06701410cb1d61b8f3d4eeae7cccfc6 5808 
ispell-uk_1.7.1-2_source.buildinfo
Checksums-Sha256:
 83bc10c9c43a0a679dd182a6429804e2bae6351c17ef2ab387f08fab3712d120 2115 
ispell-uk_1.7.1-2.dsc
 e8a3ba4e24ef0df78bd0b3e1a1c7049ef484284124103418ce152fd045be7f3a 4804 
ispell-uk_1.7.1-2.debian.tar.xz
 51c8f0e2a240ba5f38fd97c0cff6c42915ba5447ed1c14159c94a3a39e606b48 5808 
ispell-uk_1.7.1-2_source.buildinfo
Files:
 3938b49568312e9b1c617a3d9c9735b4 2115 text optional ispell-uk_1.7.1-2.dsc
 f766cac469d1e303594aeb35c1b651a6 4804 text optional 
ispell-uk_1.7.1-2.debian.tar.xz
 dbd913c6161c1a95a9e46d89ce671086 5808 text optional 

Processed: tagging 871349

[Debian Bug Tracking System]

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

> tags 871349 + pending
Bug #871349 [src:ispell-uk] ispell-uk: FTBFS: The encoding pragma is no longer 
supported at ../../bin/verb_reverse.pl line 12.
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#853615: closing 853615

[Matthias Klose]

please do *not* close package with the close command without giving any 
explanation.

On 15.08.2017 23:47, Bernhard Schmidt wrote:
> close 853615 
> thanks
> 

Bug#871294: marked as done (libsofa1: requires rebuild against GCC 7 and symbols/shlibs bump)

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2017 22:09:23 +
with message-id 
and subject line Bug#871294: fixed in sofa-framework 1.0~beta4-12
has caused the Debian Bug report #871294,
regarding libsofa1: 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.)


-- 
871294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871294
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsofa1
Version: 1.0~beta4-11
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[abi:cxx11]()@APTPKG_5.0" 0.8.0
  + (c++)"URI::operator std::__cxx11::basic_string()@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 ---
Source: sofa-framework
Source-Version: 1.0~beta4-12

We believe that the bug you reported is fixed in the latest version of
sofa-framework, 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.
Andreas Tille  (supplier of updated sofa-framework 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, 15 Aug 2017 22:43:44 +0200
Source: sofa-framework
Binary: sofa-apps libsofa1-dev libsofa1 sofa-tutorials sofa-data
Architecture: source amd64 all
Version: 1.0~beta4-12
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 libsofa1   - Simulation Open Framework Architecture - runtime
 libsofa1-dev - Simulation Open Framework Architecture - development
 sofa-apps  - GUI for the Simulation Open Framework Architecture (SOFA)
 sofa-data  - Simulation Open Framework Architecture - data
 sofa-tutorials - Simulation Open Framework Architecture - tutorials
Closes: 871294
Changes:
 sofa-framework (1.0~beta4-12) unstable; urgency=medium
 .
   * Moved packaging from SVN to Git
   * debhelper 10
   * Rebuild against GCC 7
 Closes: #871294
   * Standards-Version: 4.0.0 (No changes needed)
Checksums-Sha1:
 25f5a3ed23c5ba66ab476b71817fcb8e0b0a6403 2598 

Bug#860794: Please update DNSSEC trusted keys before ICANN key rollover event - NMU to DELAYED/7

[Bernhard Schmidt]

Control: tags -1 + pending

Hi,

> ICANN will roll the DNSSEC root zone KSK in October 2017. DNSSEC-enabled 
> resolvers will then stop working unless they have the new key configured
> to be trusted (note that in the default configuration a running BIND will
> learn and store the new key using RFC5011 (managed-keys), but a new 
> installation will be broken).
> 
> The patch attached is generated by diffing ./bind.keys{.h} from BIND 9.10.3-P4
> to BIND 9.10.5, where the changelog reads
> 
> 4564.   [maint] Update the built in managed keys to include the
> upcoming root KSK. [RT #44579]
> 
> Another way would be Bug#760459, but this will probably be too intrusive for
> jessie and stretch.

I have NMUed 9.10.3.dfsg.P4-12.6 to DELAYED/7 with the attached diff,
feel free to cancel/supersede if you start working on bind again.

Note that this also needs to be fixed in Stretch and Jessie (at least),
preferably soonish. I'll contact the SRMs about this as soon as the fix
reaches testing.

Best Regards,
Bernhard
diff -Nru bind9-9.10.3.dfsg.P4/debian/changelog bind9-9.10.3.dfsg.P4/debian/changelog
--- bind9-9.10.3.dfsg.P4/debian/changelog	2017-07-21 22:28:32.0 +0200
+++ bind9-9.10.3.dfsg.P4/debian/changelog	2017-08-11 19:10:07.0 +0200
@@ -1,3 +1,10 @@
+bind9 (1:9.10.3.dfsg.P4-12.6) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Import upcoming DNSSEC KSK-2017 from 9.10.5 (Closes: #860794)
+
+ -- Bernhard Schmidt   Fri, 11 Aug 2017 19:10:07 +0200
+
 bind9 (1:9.10.3.dfsg.P4-12.5) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru bind9-9.10.3.dfsg.P4/debian/patches/860794-new-dnssec-keys.patch bind9-9.10.3.dfsg.P4/debian/patches/860794-new-dnssec-keys.patch
--- bind9-9.10.3.dfsg.P4/debian/patches/860794-new-dnssec-keys.patch	1970-01-01 01:00:00.0 +0100
+++ bind9-9.10.3.dfsg.P4/debian/patches/860794-new-dnssec-keys.patch	2017-08-11 19:10:07.0 +0200
@@ -0,0 +1,266 @@
+From: Bernhard Schmidt 
+Subject: Add upcoming DNSSEC KSK-2017 root key
+ .
+ 4564.   [maint] Update the built in managed keys to include the
+ upcoming root KSK. [RT #44579]
+Origin: upstream, diff between 9.10.3-P4 and 9.10.5
+Bug: https://bugs.isc.org/Public/Bug/Display.html?id=44579
+Bug-Debian: https://bugs.debian.org/860794
+Forwarded: not-needed
+
+--- bind9-9.10.3.dfsg.P4/bind.keys	2016-02-29 01:29:06.0 +0100
 bind-9.10.5/bind.keys	2017-04-14 05:54:11.0 +0200
+@@ -1,4 +1,3 @@
+-/* $Id: bind.keys,v 1.7 2011/01/03 23:45:07 each Exp $ */
+ # The bind.keys file is used to override the built-in DNSSEC trust anchors
+ # which are included as part of BIND 9.  As of the current release, the only
+ # trust anchors it contains are those for the DNS root zone ("."), and for
+@@ -15,32 +14,56 @@
+ #
+ # This file is NOT expected to be user-configured.
+ #
+-# These keys are current as of January 2011.  If any key fails to
++# These keys are current as of Feburary 2017.  If any key fails to
+ # initialize correctly, it may have expired.  In that event you should
+ # replace this file with a current version.  The latest version of
+ # bind.keys can always be obtained from ISC at https://www.isc.org/bind-keys.
+ 
+ managed-keys {
+-	# ISC DLV: See https://www.isc.org/solutions/dlv for details.
+-# NOTE: This key is activated by setting "dnssec-lookaside auto;"
+-# in named.conf.
+-	dlv.isc.org. initial-key 257 3 5 "BEPHMu/5onzrEE7z1egmhg/WPO0+juoZrW3euWEn4MxDCE1+lLy2
+-		brhQv5rN32RKtMzX6Mj70jdzeND4XknW58dnJNPCxn8+jAGl2FZLK8t+
+-		1uq4W+nnA3qO2+DL+k6BD4mewMLbIYFwe0PG73Te9fZ2kJb56dhgMde5
+-		ymX4BI/oQ+cAK50/xvJv00Frf8kw6ucMTwFlgPe+jnGxPPEmHAte/URk
+-		Y62ZfkLoBAADLHQ9IrS2tryAe7mbBZVcOwIeU/Rw/mRx/vwwMCTgNboM
+-		QKtUdvNXDrYJDSHZws3xiRXF1Rf+al9UmZfSav/4NWLKjHzpT59k/VSt
+-		TDN0YUuWrBNh";
++# ISC DLV: See https://www.isc.org/solutions/dlv for details.
++#
++# NOTE: The ISC DLV zone is being phased out as of February 2017;
++# the key will remain in place but the zone will be otherwise empty.
++# Configuring "dnssec-lookaside auto;" to activate this key is
++# harmless, but is no longer useful and is not recommended.
++dlv.isc.org. initial-key 257 3 5 "BEPHMu/5onzrEE7z1egmhg/WPO0+juoZrW3euWEn4MxDCE1+lLy2
++brhQv5rN32RKtMzX6Mj70jdzeND4XknW58dnJNPCxn8+jAGl2FZLK8t+
++1uq4W+nnA3qO2+DL+k6BD4mewMLbIYFwe0PG73Te9fZ2kJb56dhgMde5
++ymX4BI/oQ+cAK50/xvJv00Frf8kw6ucMTwFlgPe+jnGxPPEmHAte/URk
++Y62ZfkLoBAADLHQ9IrS2tryAe7mbBZVcOwIeU/Rw/mRx/vwwMCTgNboM
++QKtUdvNXDrYJDSHZws3xiRXF1Rf+al9UmZfSav/4NWLKjHzpT59k/VSt
++TDN0YUuWrBNh";
+ 
+-	# ROOT KEY: See https://data.iana.org/root-anchors/root-anchors.xml
+-	# for current trust anchor information.
+-# NOTE: This key is activated by setting "dnssec-validation auto;"
++# ROOT 

Processed: Re: Bug#860794: Please update DNSSEC trusted keys before ICANN key rollover event - NMU to DELAYED/7

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #860794 [src:bind9] Please update DNSSEC trusted keys before ICANN key 
rollover event
Added tag(s) pending.

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

Bug#872298: poppler: Incomplete debian/copyright?

[Chris Lamb]

Source: poppler
Version: 0.57.0-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Emilio Pozuelo Monfort 

Hi,

I just ACCEPTed poppler from NEW but noticed it was missing 
attribution in debian/copyright for at least a lot of references
in utils/pdftotext.cc.

(This is not exhaustive so please check over the entire package 
carefully and address these on your next upload.)


Best wishes,

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

Bug#872297: tome needs a rebuild using GCC 7

[Matthias Klose]

Package: src:tome
Version: 2.4~0.git.2015.12.29-1.1
Severity: serious
Tags: sid buster

buster won't ship with GCC 6 (libasan3). Please rebuild the package.

Bug#853615: closing 853615

[Bernhard Schmidt]

close 853615 
thanks

Bug#871270: encfs: installs private library in public directory

[James Cowgill]

Control: user debian-...@lists.debian.org
Control: usertag -1 - gcc-7-op-mangling
Control: retitle -1 encfs: installs private library in public directory

Hi,

On 15/08/17 22:28, Eduard Bloch wrote:
> Hallo,
> * jcowg...@debian.org [Mon, Aug 07 2017, 03:20:41PM]:
>> Package: encfs
>> Version: 1.9.2-1
>> 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
> 
> It might be the case, however, the library inside is for internal use
> only. So I think the report and advise are not appropriate here. If you
> agree, please close the bug report and maybe also adjust the scan script
> to consider the hints from lintian overrides, like those:
> 
> $ cat /usr/share/lintian/overrides/encfs
> encfs: non-dev-pkg-with-shlib-symlink usr/lib/libencfs.so.6.0.1 
> usr/lib/libencfs.so
> encfs: no-shlibs-control-file usr/lib/libencfs.so.6.0.1
> encfs: postinst-must-call-ldconfig usr/lib/libencfs.so.6.0.1
> encfs: package-name-doesnt-match-sonames libencfs6

If the library is private, then indeed you do not need to rebuild it
with GCC 7 (since there will be no external rdeps).

However, you are aware that installing a private library in a public
directory is a policy violation (various bits in section 8)? Lintian
overrides doesn't make any difference to ld.so when determining if a
library is public. You should instead be installing it in a private
directory (such as /usr/lib/encfs) and using RUNPATH or RPATH.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Processed (with 2 errors): Re: Bug#871270: encfs: installs private library in public directory

[Debian Bug Tracking System]

Processing control commands:

> user debian-...@lists.debian.org
Unknown command or malformed arguments to command.

> usertag -1 - gcc-7-op-mangling
Unknown command or malformed arguments to command.

> retitle -1 encfs: installs private library in public directory
Bug #871270 [encfs] encfs: requires rebuild against GCC 7 and symbols/shlibs 
bump
Changed Bug title to 'encfs: installs private library in public directory' from 
'encfs: requires rebuild against GCC 7 and symbols/shlibs bump'.

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

Processed: closing 853615

[Debian Bug Tracking System]

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

> close 853615
Bug #853615 [src:pjproject] pjproject: ftbfs with GCC-7
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#872201: libc-bin: sometimes throws std::logic_error while processing triggers

[Aurelien Jarno]

control: tag - 1 + help
control: tag - 1 + moreinfo

On 2017-08-15 09:58, Andreas Beckmann wrote:
> Package: libc-bin
> Version: 2.24-14
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during several tests with piuparts in sid I noticed spurious and
> unreproducible errors while processing libc-bin triggers.
> Often apt-get just exits with an error code (but no error message
> at all) after processing the triggers.
> A few times I also get an error message about an uncaught exception.
> These failures usually go away after rerunning the test.
> 
> >From the attached log (scroll to the bottom...):
> 
>   Processing triggers for libc-bin (2.24-14) ...
>   terminate called after throwing an instance of 'std::logic_error'
> what():  basic_string::_M_construct null not valid

What make you think it's an issue in libc-bin? The trigger processing
code just does:

if [ "$1" = "triggered" ] || [ "$1" = "configure" ]; then
  ldconfig || ldconfig --verbose
  exit 0
fi

And there is no C++ code in ldconfig. Moreover even if ldconfig fails
the error is ignored and the install should not stop.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#871270: encfs: requires rebuild against GCC 7 and symbols/shlibs bump

[Eduard Bloch]

Hallo,
* jcowg...@debian.org [Mon, Aug 07 2017, 03:20:41PM]:
> Package: encfs
> Version: 1.9.2-1
> 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

It might be the case, however, the library inside is for internal use
only. So I think the report and advise are not appropriate here. If you
agree, please close the bug report and maybe also adjust the scan script
to consider the hints from lintian overrides, like those:

$ cat /usr/share/lintian/overrides/encfs
encfs: non-dev-pkg-with-shlib-symlink usr/lib/libencfs.so.6.0.1 
usr/lib/libencfs.so
encfs: no-shlibs-control-file usr/lib/libencfs.so.6.0.1
encfs: postinst-must-call-ldconfig usr/lib/libencfs.so.6.0.1
encfs: package-name-doesnt-match-sonames libencfs6

Best regards,
Eduard.

Bug#867886: (no subject)

[Víctor Cuadrado Juan]

I suspect that the hanging test is `test_client_rpc.test_async_call`,
but I haven't seen it hang locally yet.

I will upload a new version with --vv for the tests for debugging this
better (once my un-expired gpg key is in the keyring or there's a sponsor
upload).


-- 
Víctor Cuadrado Juan   m...@viccuad.me

PGP key ID: 4096R: 0xA2591E231E251F36
Key fingerprint: E3C5 114C 0C5B 4C49 BA03  0991 A259 1E23 1E25 1F36
My signed E-Mails are trustworthy.



signature.asc
Description: OpenPGP digital signature

Bug#859844: marked as done (vmtk: Please migrate to openssl1.1 in Buster)

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2017 20:56:23 +
with message-id 
and subject line Bug#859844: fixed in vmtk 1.3+dfsg-2.2
has caused the Debian Bug report #859844,
regarding vmtk: Please migrate to openssl1.1 in Buster
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.)


-- 
859844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859844
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vmtk
Version: 1.3+dfsg-2.1
Severity: important
Tags: sid buster
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1-trans

Please migrate to libssl-dev in the Buster cycle. The bug report about
the FTBFS is #850026.

Sebastian
--- End Message ---
--- Begin Message ---
Source: vmtk
Source-Version: 1.3+dfsg-2.2

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated vmtk 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: Tue, 01 Aug 2017 19:06:28 +0300
Source: vmtk
Binary: libvmtk1.3 python-vmtk libvmtk-dev vmtk
Architecture: source
Version: 1.3+dfsg-2.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Adrian Bunk 
Description:
 libvmtk-dev - shared links and header files for vmtk
 libvmtk1.3 - runtime libraries for vmtk
 python-vmtk - Python interface for vmtk
 vmtk   - the Vascular Modeling Toolkit
Closes: 859844
Changes:
 vmtk (1.3+dfsg-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix FTBFS by using OpenSSL 1.1. (Closes: #859844)
Checksums-Sha1:
 4935434eb3ace8e641c8642a42bc27af71721c98 2389 vmtk_1.3+dfsg-2.2.dsc
 c4541373c6d3c81b28908551227ee784ebcd4d16 15384 vmtk_1.3+dfsg-2.2.debian.tar.xz
Checksums-Sha256:
 afd482d41d3fd2821e747ccc859d5888b9507dad4e7d876202ed50dadce7862c 2389 
vmtk_1.3+dfsg-2.2.dsc
 d1dcd936ad355ce4b36f12a9bfcfcbabc79b27729954495203aae06c2db0d2b5 15384 
vmtk_1.3+dfsg-2.2.debian.tar.xz
Files:
 51c31ea85c0946e554ae494e48d3abc6 2389 non-free/science optional 
vmtk_1.3+dfsg-2.2.dsc
 a9ab59bd5da8138df6269787660dd0a6 15384 non-free/science optional 
vmtk_1.3+dfsg-2.2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlmA1NgACgkQiNJCh6LY
mLF2Gg//QQ6crBA+F+wLqlkXR3pdkDWKOIIEu8a9DqeBAI70RlaInjX8N51Zgsiq
g9bTxorXUV6xEVf0Bz4KCQY7rORUxJWvTlI7HdaZRiIjnzhU/af4eOshhvHYT6jH
vG2TVBWvzgCY3dR43uqwwrM47dsVPByrCcawRaET9jORwCR73VwV9MajRB7VWVdZ
otH6nQdFfdBGLoPFW19IIICU6IiqXb1EDz713oFeZ8TujUkDf1rwLdt1sXFzSF+g
w387p5trA9pkRFDHGRV0mxQH0KFxDTD+KhaEbKOpF+MD58CIif20yxP7oh/jY5eN
7ikQxBKFUsubA8zyW+riQHb6YploPDXiHpdYMOzlCb7MONQbLadAd4QFMBym8VjL
uz13NsXq4heUOj0lsraFlgeRuk1G63Oul3APrsyos2lr86JqCA2MnlsGKWm6UOpa
l31uB29zc3SG5fmasZBLquicbbIhIHXten7kcr4gA7SLd7EKjsrrATTl/31uhXYi
fb0C/81y08vl7h+yCb34gQNBFFYTWSqVwD6Yi2hbGK27ywEffbxb9NEvSOpNR/cv
1CJzqu6hAXSsXfjLEeANn+ypo+0++QHQkAjvJTbLrV3bPqqqDFkWRqf1T35a1j3v
Vwgwcr/QMLktdYFYG3/D7uuqvL4OFsPhkrhnXIp5KEZLa2AkwYo=
=/OLw
-END PGP SIGNATURE End Message ---

Bug#853653: marked as done (scilab: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2017 20:55:31 +
with message-id 
and subject line Bug#853653: fixed in scilab 5.5.2-5
has caused the Debian Bug report #853653,
regarding scilab: 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.)


-- 
853653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853653
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:scilab
Version: 5.5.2-4
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/scilab_5.5.2-4_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=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
-I../../modules/core/includes  -I./includes/ -I./src/jni/ -I./src/cpp/ 
-I./src/c/ -I../../modules/jvm/includes/ 
-I../../modules/output_stream/includes/ -I../../modules/commons/src/jni/ 
-I../../modules/localization/includes/ -I../../modules/fileio/includes/ 
-I../../modules/scicos_blocks/src/jni/ -I../../modules/api_scilab/includes/ 
-I/usr/lib/jvm/java-8-openjdk-amd64/include 
-I/usr/lib/jvm/java-8-openjdk-amd64/include/linux  -Wdate-time 
-D_FORTIFY_SOURCE=2 -DNDEBUG -fno-stack-protector -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o src/jni/libscixcos_algo_la-Palette.lo `test -f 
'src/jni/Palette.cpp' || echo './'`src/jni/Palette.cpp
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../modules/core/includes 
-I./includes/ -I./src/jni/ -I./src/cpp/ -I./src/c/ 
-I../../modules/jvm/includes/ -I../../modules/output_stream/includes/ 
-I../../modules/commons/src/jni/ -I../../modules/localization/includes/ 
-I../../modules/fileio/includes/ -I../../modules/scicos_blocks/src/jni/ 
-I../../modules/api_scilab/includes/ 
-I/usr/lib/jvm/java-8-openjdk-amd64/include 
-I/usr/lib/jvm/java-8-openjdk-amd64/include/linux -Wdate-time 
-D_FORTIFY_SOURCE=2 -DNDEBUG -fno-stack-protector -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c src/jni/Palette.cpp  -fPIC -DPIC -o 
src/jni/.libs/libscixcos_algo_la-Palette.o
/bin/bash ../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
-I../../modules/core/includes  -I./includes/ -I./src/jni/ -I./src/cpp/ 
-I./src/c/ -I../../modules/jvm/includes/ 
-I../../modules/output_stream/includes/ -I../../modules/commons/src/jni/ 
-I../../modules/localization/includes/ -I../../modules/fileio/includes/ 
-I../../modules/scicos_blocks/src/jni/ -I../../modules/api_scilab/includes/ 
-I/usr/lib/jvm/java-8-openjdk-amd64/include 
-I/usr/lib/jvm/java-8-openjdk-amd64/include/linux  -Wdate-time 
-D_FORTIFY_SOURCE=2 -DNDEBUG -fno-stack-protector -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o src/jni/libscixcos_algo_la-Modelica.lo `test -f 
'src/jni/Modelica.cpp' || echo './'`src/jni/Modelica.cpp
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../modules/core/includes 
-I./includes/ -I./src/jni/ -I./src/cpp/ -I./src/c/ 
-I../../modules/jvm/includes/ -I../../modules/output_stream/includes/ 
-I../../modules/commons/src/jni/ -I../../modules/localization/includes/ 
-I../../modules/fileio/includes/ -I../../modules/scicos_blocks/src/jni/ 
-I../../modules/api_scilab/includes/ 
-I/usr/lib/jvm/java-8-openjdk-amd64/include 
-I/usr/lib/jvm/java-8-openjdk-amd64/include/linux -Wdate-time 
-D_FORTIFY_SOURCE=2 -DNDEBUG -fno-stack-protector -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 

Bug#870237: marked as done (sdformat FTBFS with cmake 3.9.0)

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2017 20:55:39 +
with message-id 
and subject line Bug#870237: fixed in sdformat 4.2.0-3
has caused the Debian Bug report #870237,
regarding sdformat FTBFS with cmake 3.9.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.)


-- 
870237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870237
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sdformat
Version: 4.2.0-2
Severity: serious

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

...
CMake Error at CMakeLists.txt:191 (else):
  A duplicate ELSE command was found inside an IF block.


-- Configuring incomplete, errors occurred!
--- End Message ---
--- Begin Message ---
Source: sdformat
Source-Version: 4.2.0-3

We believe that the bug you reported is fixed in the latest version of
sdformat, 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.
Anton Gladky  (supplier of updated sdformat 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, 15 Aug 2017 22:11:33 +0200
Source: sdformat
Binary: libsdformat4 libsdformat4-dev sdformat-sdf sdformat-doc
Architecture: source
Version: 4.2.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Anton Gladky 
Description:
 libsdformat4 - Simulation Description Format (SDF) parser - Shared library
 libsdformat4-dev - Simulation Description Format (SDF) parser - Development 
files
 sdformat-doc - Simulation Description Format (SDF) parser - Documentation
 sdformat-sdf - Simulation Description Format (SDF) parser - SDF files
Closes: 870237
Changes:
 sdformat (4.2.0-3) unstable; urgency=medium
 .
   * Team upload.
   * [33b27de] Fix wrong usage of else-keyword in cmake. (Closes: #870237)
Checksums-Sha1:
 a4f456bb485645d79742c6602ad8afbfba85f313 2545 sdformat_4.2.0-3.dsc
 0d0d30ce89e0c034e7fd403288c57c19b10b65a9 8604 sdformat_4.2.0-3.debian.tar.xz
 2bd592376b7c3ec3477a048b876164934a626ef5 10203 
sdformat_4.2.0-3_source.buildinfo
Checksums-Sha256:
 419a6f39afa935ae8704d8f00de85cfb63912985942bb5ddcdd589d38be5830c 2545 
sdformat_4.2.0-3.dsc
 4aaba5bfc53849e904b85d6e72a81bdb09794f252ed9b584549494212dd35cc9 8604 
sdformat_4.2.0-3.debian.tar.xz
 2946d59174432cd5e98889d1c80fef1882628aed680c727d31d8479ee0f3704b 10203 
sdformat_4.2.0-3_source.buildinfo
Files:
 48c386acb0013cc5506bfbd5adb89f83 2545 science optional sdformat_4.2.0-3.dsc
 b87e7b135a87a25488a66dcc390813ee 8604 science optional 
sdformat_4.2.0-3.debian.tar.xz
 fbc1b60ebb0dbd05a346ca7cc758c2bc 10203 science optional 
sdformat_4.2.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAlmTVawACgkQ0+Fzg8+n
/wbWBBAAju9QAkyV+D4t9/ihGyVeW1H0wafNMI4SVUABSDFfZ6f5sXHe8HxwNvU0
440lyxs4Qijw5pueHxpfIN+me16mSQGNAnnL+Vnh/jGon8CpNAYfjkiI3b90D71G
i70bVV2S0mdjVwmvBxLcrObcW+n48IKzsT6ia/jsXFiXERXD2bdXOYAcOCYpS5p5
f6bIhTpMVHvUco8yWrPJgYI9lxY4Sx1oQ0x5JvNklaPcCpTbBCgAZlslVejsJxCu
Ad0KaHTXzp+XF3kiH6JsNlR+rvFz9RCcwCn6JgqreZ1+8QYvehAsejfMAhHPXR3j
F6oXFHw+KafLfytQ6khSVKH6hc+B3g+dCk0ysyUlgOTHz4GU8Y5TDymR2ROweCb8
viSsrtigS2JvTanl8SXEcMcchup8DeREnPALPHEx0mx2IiQN1+JzifNEE7Jt7HuR
ez9iWVQp8JO62XbFURhPfgNE2oGV44RXM2M7vXs+GaeE0oTWfScLdI85ch+kdbid
ly1WTMLSHCyhzCipqZsAnTpihxmuNgPX0yGKV39KF6EvMcRJ6FH0YXcitORqAtbs
U3Okl28TQj+PUkGsyEREdGbLYzzlhkTOe3per9kE2Bf9TK+P5XWWOFGpduRrvVMR
fm92Fhdjh90qZJxqsSScZlMprNEE5GxCDv+RZ8MR29z9vufziDo=
=4qU4
-END PGP SIGNATURE End Message ---

Processed: fixed 853615 in 2.6~dfsg-0+exp2

[Debian Bug Tracking System]

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

> fixed 853615 2.6~dfsg-0+exp2
Bug #853615 [src:pjproject] pjproject: ftbfs with GCC-7
Marked as fixed in versions pjproject/2.6~dfsg-0+exp2.
> thanks
Stopping processing here.

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

Processed: limit source to lilypond, tagging 871631

[Debian Bug Tracking System]

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

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

> tags 871631 + pending
Bug #871631 [lilypond-data] lilypond-data: Update fails due to problem with 
symbolic link creation
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#871631: lilypond-data: Update fails due to problem with symbolic link creation

[Don Armstrong]

On Tue, 15 Aug 2017, Philipp Matthias Hahn wrote:
> /var/lib/dpkg/info/lilypond-data.postinst looks bogus:
> |if [ -d /usr/share/info/lilypond ] && [ ! -L /usr/share/info/lilypond ] \
> | && rmdir --ignore-fail-on-non-empty /usr/share/lilypond; then
> | (cd /usr/share/info; ln -s ../doc/lilypond/html/Documentation/user/ 
> lilypond;)
> |fi;
> 
> $ ls -ld /usr/share/info/lilypond
> drwxr-xr-x 260 root root 4096 Jul 17 06:51 /usr/share/info/lilypond
>
> So the "if" evaluates to true, but what is that "rmdir" supposed to
> do?

Yeah; this was my bad patch to fix 737505 which I clearly didn't think
through. [Though this whole bit in the postinst is actually obsolete now.]

> And you don't need to put semicolons at the end of the line - this
> isn't C or Java, a simple line break is enough.

Sure; that's why the subshell doesn't have a semicolon.

-- 
Don Armstrong  https://www.donarmstrong.com

The carbon footprint of a single human being is enormous.
If you think about it, your honour,
I'm an environmentalist.
 -- a softer world #283
http://www.asofterworld.com/index.php?id=283

Bug#871820: openorienteering-mapper FTBFS: Test map_t Failed

[Graham Inggs]

Control: tags -1 + fixed-upstream
Control: tags -1 + fixed-in-experimental
Control: fixed -1 openorienteering-mapper/0.6.8-1

OpenOrienteering Mapper 0.6.8-1 in experimental builds fine with GCC 7.

Processed: openorienteering-mapper FTBFS: Test map_t Failed

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + fixed-upstream
Bug #871820 [src:openorienteering-mapper] openorienteering-mapper FTBFS: Test 
map_t Failed
Added tag(s) fixed-upstream.
> tags -1 + fixed-in-experimental
Bug #871820 [src:openorienteering-mapper] openorienteering-mapper FTBFS: Test 
map_t Failed
Added tag(s) fixed-in-experimental.
> fixed -1 openorienteering-mapper/0.6.8-1
Bug #871820 [src:openorienteering-mapper] openorienteering-mapper FTBFS: Test 
map_t Failed
Marked as fixed in versions openorienteering-mapper/0.6.8-1.

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

Bug#872292: libosmium FTBFS on 32bit: memory_test_item (Failed)

[Sebastiaan Couwenberg]

Control: tags -1 upstream
Control: forwarded -1 https://github.com/osmcode/libosmium/issues/222

Hi Adrian,

Thanks for reporting this issue.

The Fedora maintainer also ran into it and reported it upstream.

Kind Regards,

Bas

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

Processed: Re: Bug#872292: libosmium FTBFS on 32bit: memory_test_item (Failed)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream
Bug #872292 [src:libosmium] libosmium FTBFS on 32bit: memory_test_item (Failed)
Added tag(s) upstream.
> forwarded -1 https://github.com/osmcode/libosmium/issues/222
Bug #872292 [src:libosmium] libosmium FTBFS on 32bit: memory_test_item (Failed)
Set Bug forwarded-to-address to 
'https://github.com/osmcode/libosmium/issues/222'.

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

Bug#872292: libosmium FTBFS on 32bit: memory_test_item (Failed)

[Adrian Bunk]

Source: libosmium
Version: 2.13.0-1
Severity: serious

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

...
21: Test command: /<>/build/test/memory_test_item
21: Environment variables: 
21:  OSMIUM_TEST_DATA_DIR=/<>/test
21: Test timeout computed to be: 9.99988e+06
21: 
21: 
~~~
21: memory_test_item is a Catch v1.9.7 host application.
21: Run with -? for options
21: 
21: 
---
21: padded length
21: 
---
21: /<>/test/t/memory/test_item.cpp:5
21: 
...
21: 
21: /<>/test/t/memory/test_item.cpp:17: FAILED:
21:   REQUIRE( osmium::memory::padded_length(4294967295) == 4294967296 )
21: with expansion:
21:   0 == 4294967296 (0x1)
21: 
21: 
===
21: test cases:  1 | 1 failed
21: assertions: 10 | 9 passed | 1 failed
21: 
 21/149 Test  #21: memory_test_item .***Failed
0.01 sec
...
The following tests FAILED:
 21 - memory_test_item (Failed)
Errors while running CTest
debian/rules:27: recipe for target 'override_dh_auto_test-arch' failed
make[1]: *** [override_dh_auto_test-arch] Error 8

Bug#871631: lilypond-data: Update fails due to problem with symbolic link creation

[Philipp Matthias Hahn]

Package: lilypond-data
Version: 2.18.2-8
Followup-For: Bug #871631

Dear Maintainer,

/var/lib/dpkg/info/lilypond-data.postinst looks bogus:
|if [ -d /usr/share/info/lilypond ] && [ ! -L /usr/share/info/lilypond ] \
|   && rmdir --ignore-fail-on-non-empty /usr/share/lilypond; then
|   (cd /usr/share/info; ln -s ../doc/lilypond/html/Documentation/user/ 
lilypond;)
|fi;

$ ls -ld /usr/share/info/lilypond
drwxr-xr-x 260 root root 4096 Jul 17 06:51 /usr/share/info/lilypond

So the "if" evaluates to true, but what is that "rmdir" supposed to do?
Mine directory isn't empty.
So the "ln" tries do overwrite the directory.

BTW: Instead of the (cd;ln;) subshell construct, you can write
  ln -s ../doc/lilypond/html/Documentation/user/ /usr/share/info/lilypond

And you don't need to put semicolons at the end of the line - this isn't
C or Java, a simple line break is enough.


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

Kernel: Linux 4.12.4 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de:en_US (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lilypond-data depends on:
ii  python   2.7.13-2
ii  texinfo  6.4.90.dfsg.1-1+b1
ii  texlive-binaries [texlive-base-bin]  2017.20170613.44572-5

Versions of packages lilypond-data recommends:
ii  lilypond  2.18.2-8

lilypond-data suggests no packages.

-- no debconf information

Bug#853306: marked as done (alljoyn-core-1604: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2017 18:34:04 +
with message-id 
and subject line Bug#853306: fixed in alljoyn-core-1604 16.04a+dfsg.1-1
has caused the Debian Bug report #853306,
regarding alljoyn-core-1604: 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.)


-- 
853306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853306
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:alljoyn-core-1604
Version: 16.04a-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/alljoyn-core-1604_16.04a-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

[...]
Install file: "services/config/cpp/inc/alljoyn/config/LogModule.h" as 
"build/linux/x86_64/release/dist/cpp/inc/alljoyn/config/LogModule.h"
g++ -o 
build/linux/x86_64/release/obj/config/cpp/samples/ConfigClientSample/ConfigClientMain.o
 -c -std=c++11 -Wall -Werror -pipe -fno-exceptions -fno-strict-aliasing 
-fno-asynchronous-unwind-tables -fno-unwind-tables -ffunction-sections 
-fdata-sections -D_FORTIFY_SOURCE=2 -fPIC -Wno-long-long -Wno-deprecated 
-Wno-unknown-pragmas -Wunused-parameter -Os -m64 -fPIC 
-Wno-deprecated-declarations -Wno-deprecated-declarations -DNDEBUG -DROUTER 
-DQCC_OS_GROUP_POSIX -DQCC_OS_LINUX -D_GLIBCXX_USE_C99_FP_MACROS_DYNAMIC 
-Ibuild/linux/x86_64/release/dist/cpp/inc 
-Ibuild/linux/x86_64/release/dist/c/inc 
-Ibuild/linux/x86_64/release/dist/cpp/inc/alljoyn -Icommon/inc 
services/config/cpp/samples/ConfigClientSample/ConfigClientMain.cc
g++ -o 
build/linux/x86_64/release/obj/config/cpp/samples/ConfigClientSample/SessionListenerImpl.o
 -c -std=c++11 -Wall -Werror -pipe -fno-exceptions -fno-strict-aliasing 
-fno-asynchronous-unwind-tables -fno-unwind-tables -ffunction-sections 
-fdata-sections -D_FORTIFY_SOURCE=2 -fPIC -Wno-long-long -Wno-deprecated 
-Wno-unknown-pragmas -Wunused-parameter -Os -m64 -fPIC 
-Wno-deprecated-declarations -Wno-deprecated-declarations -DNDEBUG -DROUTER 
-DQCC_OS_GROUP_POSIX -DQCC_OS_LINUX -D_GLIBCXX_USE_C99_FP_MACROS_DYNAMIC 
-Ibuild/linux/x86_64/release/dist/cpp/inc 
-Ibuild/linux/x86_64/release/dist/c/inc 
-Ibuild/linux/x86_64/release/dist/cpp/inc/alljoyn -Icommon/inc 
services/config/cpp/samples/ConfigClientSample/SessionListenerImpl.cc
g++ -o build/linux/x86_64/release/obj/config/cpp/samples/common/AJInitializer.o 
-c -std=c++11 -Wall -Werror -pipe -fno-exceptions -fno-strict-aliasing 
-fno-asynchronous-unwind-tables -fno-unwind-tables -ffunction-sections 
-fdata-sections -D_FORTIFY_SOURCE=2 -fPIC -Wno-long-long -Wno-deprecated 
-Wno-unknown-pragmas -Wunused-parameter -Os -m64 -fPIC 
-Wno-deprecated-declarations -Wno-deprecated-declarations -DNDEBUG -DROUTER 
-DQCC_OS_GROUP_POSIX -DQCC_OS_LINUX -D_GLIBCXX_USE_C99_FP_MACROS_DYNAMIC 
-Ibuild/linux/x86_64/release/dist/cpp/inc 
-Ibuild/linux/x86_64/release/dist/c/inc 
-Ibuild/linux/x86_64/release/dist/cpp/inc/alljoyn -Icommon/inc 
services/config/cpp/samples/common/AJInitializer.cc
g++ -o 
build/linux/x86_64/release/obj/config/cpp/samples/common/SrpKeyXListener.o -c 
-std=c++11 -Wall -Werror -pipe -fno-exceptions -fno-strict-aliasing 
-fno-asynchronous-unwind-tables -fno-unwind-tables -ffunction-sections 
-fdata-sections -D_FORTIFY_SOURCE=2 -fPIC -Wno-long-long -Wno-deprecated 
-Wno-unknown-pragmas -Wunused-parameter -Os -m64 -fPIC 
-Wno-deprecated-declarations -Wno-deprecated-declarations -DNDEBUG -DROUTER 
-DQCC_OS_GROUP_POSIX -DQCC_OS_LINUX 

Bug#872281: why FTBFS with frama-c 20170501+phosphorus+dfsg-1

[Adrian Bunk]

Source: why
Version: 2.38-1
Severity: serious

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

...
   dh_install -O--no-parallel
dh_install: Cannot find (any matches for) "frama-c-plugin/top/Jessie.o" (tried 
in ., debian/tmp)

dh_install: why missing files: frama-c-plugin/top/Jessie.o
dh_install: missing files, aborting
install -d debian/.debhelper/generated/why
install -d debian/.debhelper/generated/libwhy-coq
debian/rules:67: recipe for target 'binary' failed
make: *** [binary] Error 25

Bug#853305: marked as done (alljoyn-core-1509: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2017 18:19:08 +
with message-id 
and subject line Bug#853305: fixed in alljoyn-core-1509 15.09a+dfsg.1-1
has caused the Debian Bug report #853305,
regarding alljoyn-core-1509: 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.)


-- 
853305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853305
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:alljoyn-core-1509
Version: 15.09a-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/alljoyn-core-1509_15.09a-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

[...]
Install file: "services/about/cpp/inc/alljoyn/about/PropertyStoreProperty.h" as 
"build/linux/x86_64/release/dist/cpp/inc/alljoyn/about/PropertyStoreProperty.h"
Install file: "services/about/cpp/inc/alljoyn/about/AboutService.h" as 
"build/linux/x86_64/release/dist/cpp/inc/alljoyn/about/AboutService.h"
g++ -o build/linux/x86_64/release/obj/about/cpp/src/AboutPropertyStoreImpl.o -c 
-std=c++11 -Wall -Werror -pipe -fno-exceptions -fno-strict-aliasing 
-fno-asynchronous-unwind-tables -fno-unwind-tables -ffunction-sections 
-fdata-sections -D_FORTIFY_SOURCE=2 -fPIC -Wno-long-long -Wno-deprecated 
-Wno-unknown-pragmas -Wunused-parameter -Os -m64 -fPIC 
-Wno-deprecated-declarations -DNDEBUG -DROUTER -DQCC_OS_GROUP_POSIX 
-DQCC_OS_LINUX -D_GLIBCXX_USE_C99_FP_MACROS_DYNAMIC 
-Ibuild/linux/x86_64/release/dist/cpp/inc 
-Ibuild/linux/x86_64/release/dist/c/inc 
-Ibuild/linux/x86_64/release/dist/cpp/inc/alljoyn -Icommon/inc 
services/about/cpp/src/AboutPropertyStoreImpl.cc
g++ -o build/linux/x86_64/release/obj/about/cpp/src/AboutService.o -c 
-std=c++11 -Wall -Werror -pipe -fno-exceptions -fno-strict-aliasing 
-fno-asynchronous-unwind-tables -fno-unwind-tables -ffunction-sections 
-fdata-sections -D_FORTIFY_SOURCE=2 -fPIC -Wno-long-long -Wno-deprecated 
-Wno-unknown-pragmas -Wunused-parameter -Os -m64 -fPIC 
-Wno-deprecated-declarations -DNDEBUG -DROUTER -DQCC_OS_GROUP_POSIX 
-DQCC_OS_LINUX -D_GLIBCXX_USE_C99_FP_MACROS_DYNAMIC 
-Ibuild/linux/x86_64/release/dist/cpp/inc 
-Ibuild/linux/x86_64/release/dist/c/inc 
-Ibuild/linux/x86_64/release/dist/cpp/inc/alljoyn -Icommon/inc 
services/about/cpp/src/AboutService.cc
g++ -o build/linux/x86_64/release/obj/about/cpp/src/AboutServiceApi.o -c 
-std=c++11 -Wall -Werror -pipe -fno-exceptions -fno-strict-aliasing 
-fno-asynchronous-unwind-tables -fno-unwind-tables -ffunction-sections 
-fdata-sections -D_FORTIFY_SOURCE=2 -fPIC -Wno-long-long -Wno-deprecated 
-Wno-unknown-pragmas -Wunused-parameter -Os -m64 -fPIC 
-Wno-deprecated-declarations -DNDEBUG -DROUTER -DQCC_OS_GROUP_POSIX 
-DQCC_OS_LINUX -D_GLIBCXX_USE_C99_FP_MACROS_DYNAMIC 
-Ibuild/linux/x86_64/release/dist/cpp/inc 
-Ibuild/linux/x86_64/release/dist/c/inc 
-Ibuild/linux/x86_64/release/dist/cpp/inc/alljoyn -Icommon/inc 
services/about/cpp/src/AboutServiceApi.cc
g++ -o build/linux/x86_64/release/obj/about/cpp/src/AnnounceHandler.o -c 
-std=c++11 -Wall -Werror -pipe -fno-exceptions -fno-strict-aliasing 
-fno-asynchronous-unwind-tables -fno-unwind-tables -ffunction-sections 
-fdata-sections -D_FORTIFY_SOURCE=2 -fPIC -Wno-long-long -Wno-deprecated 
-Wno-unknown-pragmas -Wunused-parameter -Os -m64 -fPIC 
-Wno-deprecated-declarations -DNDEBUG -DROUTER -DQCC_OS_GROUP_POSIX 
-DQCC_OS_LINUX -D_GLIBCXX_USE_C99_FP_MACROS_DYNAMIC 
-Ibuild/linux/x86_64/release/dist/cpp/inc 

Bug#871214: [Pkg-octave-devel] Bug#871214: octave-image FTBFS on i386: test hangs

[Sébastien Villemot]

On Thu, Aug 10, 2017 at 02:42:42PM +0300, Adrian Bunk wrote:
> On Thu, Aug 10, 2017 at 09:31:32AM +0200, Rafael Laboissière wrote:
> > 
> > I would guess that the culprit is the following unit test in bwdist:
> > 
> > ## The quasi-euclidean method is apparently sensitive to a machine precision
> > ## error that happens in x86 systems only. This test will cause an endless
> > ## loop in case of a regression.
> >...
> 
> That explains why the problem happens on i386 (where the 387 FPU
> that internally uses 80-bit precision is used) but not on amd64
> (where gcc defaults to using SSE instead of the 387).
> 
> If the problem is only in the test case,
> it should be disabled on any-i386.
> 
> But if the difference is actually considered a bug,
> then the following in debian/rules fixes the problem:
> 
> DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
> 
> ifneq (,$(filter $(DEB_HOST_ARCH), i386))
> export DEB_CXXFLAGS_MAINT_APPEND=-ffloat-store
> endif

Thanks Adrian for suggesting this solution.

However, it should be mentioned that this option has a significant performance
cost (since it basically adds a memory access after each floating point
computation).

I am not familiar enough with octave-image to decide whether IEEE compliance is
more important than performance, though.

-- 
⢀⣴⠾⠻⢶⣦   Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


signature.asc
Description: PGP signature

Bug#871815: bug opened upstream

[Roberto Oliveira]

It also breaks in asn1c master branch, so I opened a bug upstream at:
https://github.com/vlm/asn1c/issues/179

Bug#871214: [Pkg-octave-devel] Bug#871214: octave-image FTBFS on i386: test hangs

[Adrian Bunk]

On Tue, Aug 15, 2017 at 08:08:58PM +0200, Sébastien Villemot wrote:
> On Thu, Aug 10, 2017 at 02:42:42PM +0300, Adrian Bunk wrote:
> > On Thu, Aug 10, 2017 at 09:31:32AM +0200, Rafael Laboissière wrote:
> > > 
> > > I would guess that the culprit is the following unit test in bwdist:
> > > 
> > > ## The quasi-euclidean method is apparently sensitive to a machine 
> > > precision
> > > ## error that happens in x86 systems only. This test will cause an endless
> > > ## loop in case of a regression.
> > >...
> > 
> > That explains why the problem happens on i386 (where the 387 FPU
> > that internally uses 80-bit precision is used) but not on amd64
> > (where gcc defaults to using SSE instead of the 387).
> > 
> > If the problem is only in the test case,
> > it should be disabled on any-i386.
> > 
> > But if the difference is actually considered a bug,
> > then the following in debian/rules fixes the problem:
> > 
> > DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
> > 
> > ifneq (,$(filter $(DEB_HOST_ARCH), i386))
> > export DEB_CXXFLAGS_MAINT_APPEND=-ffloat-store
> > endif
> 
> Thanks Adrian for suggesting this solution.
> 
> However, it should be mentioned that this option has a significant performance
> cost (since it basically adds a memory access after each floating point
> computation).
> 
> I am not familiar enough with octave-image to decide whether IEEE compliance 
> is
> more important than performance, though.

This is also what I tried to say by giving two options and
"But if the difference is actually considered a bug".

cu
Adrian

-- 

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

Bug#872221: closed by Adrian Bunk <b...@debian.org> (Re: Bug#872221: amarok: symbol lookup error libavcodec.so.57: undefined symbol: lame_set_VBR_quality)

[Kostas Papadopoulos]

Hi,

Thanks you very much. Long ago I installed some non-official audio 
packages and I guess they stack around. Thank you again and sorry for 
the trouble.


Best Regards

Kostas Papadopoulos
On 08/15/2017 08:03 PM, Adrian Bunk wrote:

On Tue, Aug 15, 2017 at 04:51:04PM +, Debian Bug Tracking System wrote:

...
On Tue, Aug 15, 2017 at 07:05:15PM +0300, Kostas Papadopoulos wrote:

...

lddd /usr/lib/x86_64-linux-gnu/libavcodec.so.57 | grep libmp3lame
 libmp3lame.so.0 => /usr/local/lib/libmp3lame.so.0
...


This is causing your problem - you have lame manually installed
in /usr/local, and removing this library will fix your problem.


Actually:
ii  libmp3lame0 1:3.99.3-0.0 amd64

Wherever that package is coming from, it is causing your problem,
and due to the 1: epoch it has a higher version number than the
official Debian package.

Try:
   apt-get install libmp3lame0=3.99.5+repack1-9+b2


cu
Adrian


cu
Adrian

Bug#795109: Not going to be ported

[Lisandro Damián Nicanor Pérez Meyer]

To the best of my knowledge this package will not get ported, so I asked for 
it's removal in #872279.

If you have clues of the contrary please follow up in that bug (or agree with 
it and ask for it's removal).

Thanks, Lisandro.


-- 
lo cual parece incompatible.
lógica, esa tendrá particiones dentro,
si se transforma la extendida a
tiene particiones lógicas, luego
extendida. Una extendida
estar dentro de una partición
Una partición lógica necesita

Diga NO al topposting.

  Matias Silva Bustos

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#872221: closed by Adrian Bunk <b...@debian.org> (Re: Bug#872221: amarok: symbol lookup error libavcodec.so.57: undefined symbol: lame_set_VBR_quality)

[Adrian Bunk]

On Tue, Aug 15, 2017 at 04:51:04PM +, Debian Bug Tracking System wrote:
>...
> On Tue, Aug 15, 2017 at 07:05:15PM +0300, Kostas Papadopoulos wrote:
> >...
> > 
> > lddd /usr/lib/x86_64-linux-gnu/libavcodec.so.57 | grep libmp3lame
> > libmp3lame.so.0 => /usr/local/lib/libmp3lame.so.0
> >...
> 
> This is causing your problem - you have lame manually installed
> in /usr/local, and removing this library will fix your problem.

Actually:
ii  libmp3lame0 1:3.99.3-0.0 amd64

Wherever that package is coming from, it is causing your problem,
and due to the 1: epoch it has a higher version number than the
official Debian package.

Try:
  apt-get install libmp3lame0=3.99.5+repack1-9+b2

> cu
> Adrian

cu
Adrian

-- 

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

Bug#872221: marked as done (amarok: symbol lookup error libavcodec.so.57: undefined symbol: lame_set_VBR_quality)

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2017 19:45:14 +0300
with message-id <20170815164514.wx45xeysy2dfya3v@localhost>
and subject line Re: Bug#872221: amarok: symbol lookup error libavcodec.so.57: 
undefined symbol: lame_set_VBR_quality
has caused the Debian Bug report #872221,
regarding amarok: symbol lookup error libavcodec.so.57: undefined symbol: 
lame_set_VBR_quality
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.)


-- 
872221: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872221
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: amarok
Version: 2.8.0-8
Severity: grave
Justification: renders package unusable

Dear Maintainer,

amarok does not start with message:

amarok: symbol lookup error: /usr/lib/x86_64-linux-gnu/libavcodec.so.57: 
undefined symbol: lame_set_VBR_quality


   * What led up to the situation?
   Upgrade from jessie to stretch

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



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

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=el_GR.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=locale: Cannot set 
LC_ALL to default locale: Arquivo ou diretório não encontrado
UTF-8), LANGUAGE=pt_BR:en_US (charmap=locale: Cannot set LC_ALL to default 
locale: Arquivo ou diretório não encontrado
UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages amarok depends on:
ii  amarok-common 2.8.0-8
ii  amarok-utils  2.8.0-8
ii  kde-runtime   4:16.08.3-2
ii  libavcodec-extra577:3.2.5-1
ii  libavformat57 7:3.2.5-1
ii  libavutil55   7:3.2.5-1
ii  libc6 2.24-11+deb9u1
ii  libcurl3-gnutls   7.52.1-5
ii  libgcrypt20   1.7.6-2+deb9u1
ii  libgdk-pixbuf2.0-02.36.5-2
ii  libgl1-mesa-glx [libgl1]  13.0.6-1+b2
ii  libglib2.0-0  2.50.3-2
ii  libgpod4  0.8.3-8.2
ii  libgpod4-nogtk0.8.3-8.2
ii  libkcmutils4  4:4.14.26-2
ii  libkdecore5   4:4.14.26-2
ii  libkdeui5 4:4.14.26-2
ii  libkdewebkit5 4:4.14.26-2
ii  libkdnssd44:4.14.26-2
ii  libkfile4 4:4.14.26-2
ii  libkio5   4:4.14.26-2
ii  libknewstuff3-4   4:4.14.26-2
ii  liblastfm11.0.9-1
ii  libloudmouth1-0   1.5.3-2
ii  libmariadbclient1810.1.23-9+deb9u1
ii  libmariadbd18 10.1.23-9+deb9u1
ii  libmtp9   1.1.13-1
ii  libmygpo-qt1  1.0.9-2
ii  libofa0   0.9.3-15
ii  libphonon44:4.9.0-4
ii  libplasma34:4.14.26-2
ii  libqjson0 0.8.1-3
ii  libqt4-dbus   4:4.8.7+dfsg-11
ii  libqt4-network4:4.8.7+dfsg-11
ii  libqt4-opengl 4:4.8.7+dfsg-11
ii  libqt4-script 4:4.8.7+dfsg-11
ii  libqt4-sql4:4.8.7+dfsg-11
ii  libqt4-svg4:4.8.7+dfsg-11
ii  libqt4-xml4:4.8.7+dfsg-11
ii  libqtcore44:4.8.7+dfsg-11
ii  libqtgui4 4:4.8.7+dfsg-11
ii  libqtscript4-core 0.2.0-1+b1
ii  libqtscript4-gui  0.2.0-1+b1
ii  libqtscript4-network  0.2.0-1+b1
ii  libqtscript4-sql  0.2.0-1+b1
ii  libqtscript4-uitools  0.2.0-1+b1
ii  libqtscript4-xml  0.2.0-1+b1
ii  libqtwebkit4  2.3.4.dfsg-9.1
ii  libsolid4 4:4.14.26-2
ii  libstdc++66.3.0-18
ii  libthreadweaver4  4:4.14.26-2
ii  libx11-6  2:1.6.4-3
ii  libxml2   2.9.4+dfsg1-2.2
ii  phonon4:4.9.0-4

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

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

Versions of packages amarok-common depends on:
ii  perl  5.24.1-3+deb9u1

amarok-common recommends no packages.

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

-- debconf information:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = 

Bug#871145: Pending in NEW

[Kartik Mistry]

tags 871145 pending
thanks

-- 
Kartik Mistry | IRC: kart_
{0x1f1f, kartikm}.wordpress.com

Processed: Pending in NEW

[Debian Bug Tracking System]

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

> tags 871145 pending
Bug #871145 [src:hfst] hfst: FTBFS: ./../include/fst/replace.h:1061:46: error: 
expected ';' before '::' token
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#872221: amarok: symbol lookup error libavcodec.so.57: undefined symbol: lame_set_VBR_quality

[Kostas Papadopoulos]

dpkg -l libmp3lame0

Desired=Unknown/Install/Remove/Purge/Hold
| 
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend

|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion 
Architecture Description

+++-===---===
ii  libmp3lame0 1:3.99.3-0.0 
amd64LAME Ain't an MP3 Encoder (shared library)



lddd /usr/lib/x86_64-linux-gnu/libavcodec.so.57 | grep libmp3lame
libmp3lame.so.0 => /usr/local/lib/libmp3lame.so.0 
(0x7fb37d0e)


Best Regards
Kostas Papadopoulos

On 08/15/2017 04:50 PM, Adrian Bunk wrote:

On Tue, Aug 15, 2017 at 11:12:00AM +0300, Kostas Papadopoulos wrote:

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

Dear Maintainer,

amarok does not start with message:

amarok: symbol lookup error: /usr/lib/x86_64-linux-gnu/libavcodec.so.57: 
undefined symbol: lame_set_VBR_quality
...


Please send the output of the following commands:
   dpkg -l libmp3lame0
   ldd /usr/lib/x86_64-linux-gnu/libavcodec.so.57 | grep libmp3lame


Thanks
Adrian

Bug#872276: collectd: FTBFS with linux-libc-dev >= 4.12: please bundle asm/msr-index.h

[Steve Langasek]

Package: collectd
Version: 5.7.1-1.1
Severity: serious
Tags: patch
Justification: FTBFS
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu artful ubuntu-patch

After patching bug #871062, I found that collectd still FTBFS on amd64 and
i386 in Ubuntu because the asm/msr-index.h header is no longer shipped by
linux-libc-dev >= 4.12.  This has been dropped by upstream for reasons
explained in
.

The correct solution for this is for collectd to bundle the register defines
itself rather than relying on the kernel header package to provide them, as
in the attached patch.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru collectd-5.7.1/debian/patches/local-msr-index-h.patch 
collectd-5.7.1/debian/patches/local-msr-index-h.patch
--- collectd-5.7.1/debian/patches/local-msr-index-h.patch   1969-12-31 
16:00:00.0 -0800
+++ collectd-5.7.1/debian/patches/local-msr-index-h.patch   2017-08-15 
09:08:03.0 -0700
@@ -0,0 +1,768 @@
+Description: Bundle our own copy of asm/msr-index.h
+ As of Linux 4.12, asm/msr-index.h is not a userspace-exported header, per
+ 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b72e7464e4cf80117938e6adb8c22fdc1ca46d42
+ So to use this header (which only lists defines for register names rather
+ than exposing any kernel interfaces), we need to bundle our own - which also
+ obviates any need for a configure check.
+Bug-Ubuntu: https://bugs.launchpad.net/bugs/1710799
+Author: Steve Langasek 
+Last-Update: 2017-08-15
+
+--- collectd-5.7.1.orig/configure.ac
 collectd-5.7.1/configure.ac
+@@ -804,29 +804,6 @@ AC_CACHE_CHECK([whether clock_boottime a
+  [c_cv_have_clock_boottime_monotonic="no"]))
+ 
+ 
+-# For the turbostat plugin
+-have_asm_msrindex_h="no"
+-AC_CHECK_HEADERS(asm/msr-index.h, [have_asm_msrindex_h="yes"])
+-
+-if test "x$have_asm_msrindex_h" = "xyes"
+-then
+-  AC_CACHE_CHECK([whether asm/msr-index.h has MSR_PKG_C10_RESIDENCY],
+- [c_cv_have_usable_asm_msrindex_h],
+- AC_COMPILE_IFELSE([AC_LANG_PROGRAM(
+-[[[
+-#include
+-]]],
+-[[[
+-int y = MSR_PKG_C10_RESIDENCY;
+-return(y);
+-]]]
+-  )],
+- [c_cv_have_usable_asm_msrindex_h="yes"],
+- [c_cv_have_usable_asm_msrindex_h="no"],
+-  )
+- )
+-fi
+-
+ have_cpuid_h="no"
+ AC_CHECK_HEADERS(cpuid.h, [have_cpuid_h="yes"])
+ 
+@@ -6016,7 +5993,7 @@ then
+   then
+   plugin_ipvs="yes"
+   fi
+-  if test "x$c_cv_have_usable_asm_msrindex_h" = "xyes" && test 
"x$have_cpuid_h" = "xyes"
++  if test "x$have_cpuid_h" = "xyes"
+   then
+   plugin_turbostat="yes"
+   fi
+--- /dev/null
 collectd-5.7.1/src/asm/msr-index.h
+@@ -0,0 +1,714 @@
++#ifndef _ASM_X86_MSR_INDEX_H
++#define _ASM_X86_MSR_INDEX_H
++
++/*
++ * CPU model specific register (MSR) numbers.
++ *
++ * Do not add new entries to this file unless the definitions are shared
++ * between multiple compilation units.
++ */
++
++/* x86-64 specific MSRs */
++#define MSR_EFER  0xc080 /* extended feature register */
++#define MSR_STAR  0xc081 /* legacy mode SYSCALL target */
++#define MSR_LSTAR 0xc082 /* long mode SYSCALL target */
++#define MSR_CSTAR 0xc083 /* compat mode SYSCALL target */
++#define MSR_SYSCALL_MASK  0xc084 /* EFLAGS mask for syscall */
++#define MSR_FS_BASE   0xc100 /* 64bit FS base */
++#define MSR_GS_BASE   0xc101 /* 64bit GS base */
++#define MSR_KERNEL_GS_BASE0xc102 /* SwapGS GS shadow */
++#define MSR_TSC_AUX   0xc103 /* Auxiliary TSC */
++
++/* EFER bits: */
++#define _EFER_SCE 0  /* SYSCALL/SYSRET */
++#define _EFER_LME 8  /* Long mode enable */
++#define _EFER_LMA 10 /* Long mode active (read-only) */
++#define _EFER_NX  11 /* No execute enable */
++#define _EFER_SVME12 /* Enable virtualization */
++#define _EFER_LMSLE   13 /* Long Mode Segment Limit Enable */
++#define _EFER_FFXSR   14 /* Enable Fast FXSAVE/FXRSTOR */
++
++#define EFER_SCE  (1<<_EFER_SCE)
++#define EFER_LME  (1<<_EFER_LME)
++#define EFER_LMA  (1<<_EFER_LMA)
++#define EFER_NX   (1<<_EFER_NX)
++#define EFER_SVME (1<<_EFER_SVME)
++#define EFER_LMSLE(1<<_EFER_LMSLE)
++#define EFER_FFXSR(1<<_EFER_FFXSR)
++
++/* Intel MSRs. Some also available on other CPUs */
++
++#define MSR_PPIN_CTL  0x004e
++#define MSR_PPIN 

Bug#872239: marked as done (numexpr: Debug packages should not be removed)

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2017 17:54:12 +0200
with message-id 
and subject line Re: RFS: numexpr 2.6.2 and pytables 3.4.2
has caused the Debian Bug report #872239,
regarding numexpr: Debug packages should not be removed
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.)


-- 
872239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872239
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: numexpr
Version: 2.6.2-1
Severity: serious
Justification: makes pytables FTBFS
Control: affects -1 src:pytables

Dear maintainer,

The changelog for numexpr 2.6.2-1 says:

  numexpr (2.6.2-1) unstable; urgency=medium

[...]
* Drop -dbg package declaration (now debug packages are automatically
  generated)

This is not true. The automatically generated dbgsym packages only contain
the debugging symbols for the C extension files. However, the former -dbg
packages contained the extensions built for Python debug interpreter:

  $ dpkg -L python3-numexpr-dbg
  
/usr/lib/python3/dist-packages/numexpr/interpreter.cpython-35dm-x86_64-linux-gnu.so
  
/usr/lib/python3/dist-packages/numexpr/interpreter.cpython-36dm-x86_64-linux-gnu.so
  [...]

These files are needed when you want to use numexpr with the debug
interpreter, i.e. /usr/bin/python3-dbg; and they are not present in the
automatic dbgsym packages. So please revert dropping the -dbg packages.

This was also discussed on debian-python mailing list several times, i.e.:
https://lists.debian.org/debian-python/2016/04/msg00093.html

I am setting the severity to serious to prevent the new upload from migrating
to testing; please feel free to downgrade it if you want.

--
Dmitry Shachnev


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
> Hi Yaroslav, hi Frederic,
> 
> Il 13/08/2017 23:04, PICCA Frederic-Emmanuel ha scritto:
>> Hello guyes.
>>
>>
>>> 2.
>>> +  * Drop -dbg package declaration (now debug packages are automatically
>>> +generated)
>>
>>> I am not sure if -dbgsym is sufficient replacement here of python-dbg 
>>> specific
>>> builds of extensions, which e.g. allow to see python stack etc within gdb.  
>>> Or
>>> have I missed some other news?
>>
>>
>> You are right python--dbg packages  are not equivalent to the
>> lib-dbg packages (symbol files) ->dbgsym
>>
>> the python-dbg packages contain in fact extensions built with the special 
>> python-dbg interpreter.
>>
>> So this is a very bad idea to remove them... :(((
> 
> Ok, I restored -dbg packages in both numexpr (2.6.2-2) and pytables.
> 
> numexpr needs a new upload while pytables shall be uploaded only after
> 2.6.2-2, otherwise you will have missing build dependencies.
> 
> I update both th git repos and packages on metors.
> 
> cheers


Il 15/08/2017 15:09, PICCA Frederic-Emmanuel ha scritto:
> Hello,
> 
> I uploaded numexpr.
> 
> Cheers
> 

Thanks Frederic.

Also closing RC bug #872239

cheers
-- 
Antonio Valentino--- End Message ---

Bug#871178: marked as done (adacontrol: FTBFS: gcc: error trying to exec 'gnat1': execvp: No such file or directory)

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2017 17:55:44 +0200
with message-id <1dcee7dd-ce32-b485-dade-7c773949b...@debian.org>
and subject line fixed with gnat pointing to gnat-7
has caused the Debian Bug report #871178,
regarding adacontrol: FTBFS: gcc: error trying to exec 'gnat1': execvp: No such 
file or directory
to be marked as done.

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

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


-- 
871178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: adacontrol
Version: 1.18r9-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[2]: Entering directory '/<>'
> sed -i~ \
>   's/^\(ADACTL v\. \).*\( with ASIS .* for \)GNAT .*/\11.18r9\2GNAT 6.4.0/' \
>   test/ref/tfw_help.txt
> cd test && sh -e run.sh
> ---
> --   
> --
> --  ADACTL v. 1.18r9 with ASIS 2.0.R for GNAT 6.4.0  
> --
> --(../adactl)
> --
> --   
> --
> --VALIDATION 
> --
> --   
> --
> --   Sun Aug  6 20:32:39 UTC 2017
> --
> --   
> --
> ---
> --- General framework tests
> Controlling TFW_FORMATS body
> Controlling TFW_FORMATS body
> Controlling TFW_FORMATS body
> Controlling TFW_FORMATS body
> Controlling TFW_FORMATS body
> Controlling TFW_FORMATS body
> Controlling TFW_FORMATS body
> Controlling TFW_FORMATS body
> Total execution time: 0.0s.
> gcc: error trying to exec 'gnat1': execvp: No such file or directory
> gcc: error trying to exec 'gnat1': execvp: No such file or directory
> gcc: error trying to exec 'gnat1': execvp: No such file or directory
> gcc: error trying to exec 'gnat1': execvp: No such file or directory
> gcc: error trying to exec 'gnat1': execvp: No such file or directory
> gcc: error trying to exec 'gnat1': execvp: No such file or directory
> gcc: error trying to exec 'gnat1': execvp: No such file or directory
> debian/rules:53: recipe for target 'override_dh_auto_test-arch' failed
> make[2]: *** [override_dh_auto_test-arch] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/adacontrol_1.18r9-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 ---
this is now fixed with gnat pointing to gnat-7.--- End Message ---

Bug#871110: marked as done (tiemu: FTBFS: cc1: error: -Wformat-security ignored without -Wformat [-Werror=format-security])

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2017 14:53:43 +
with message-id 
and subject line Bug#871110: fixed in tiemu 3.03-nogdb+dfsg-4
has caused the Debian Bug report #871110,
regarding tiemu: FTBFS: cc1: error: -Wformat-security ignored without -Wformat 
[-Werror=format-security]
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.)


-- 
871110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871110
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tiemu
Version: 3.03-nogdb+dfsg-3
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):
> gcc  -c  -g -O2 -fdebug-prefix-map=/<>/tiemu-3.03-nogdb+dfsg=. 
> -fstack-protector-strong -Wformat -Werror=format-security -D__LINUX__ 
> -fvisibility=hidden -DGTK_DISABLE_DEPRECATED -DDEBUGGER -DNO_GDB 
> -I/usr/include/tilp2 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/tilp2 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/tilp2 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/tilp2 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
> -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include 
> -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 
> -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
> -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
> -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/freetype2 -pthread -I/usr/include/libglade-2.0 
> -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include 
> -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 
> -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
> -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
> -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/freetype2 -I/usr/include/libxml2 -I/usr/include/SDL 
> -D_GNU_SOURCE=1 -D_REENTRANT  -fomit-frame-pointer -Wno-unused -Wno-format -W 
> -Wmissing-prototypes -Wstrict-prototypes -D__inline__=inline 
> -DSTATFS_NO_ARGS=2 -DSTATBUF_BAVAIL=f_bavail  cpudefs.c -o cpudefs.o
> cc1: error: -Wformat-security ignored without -Wformat 
> [-Werror=format-security]
> cc1: some warnings being treated as errors
> Makefile:70: recipe for target 'cpudefs.o' failed
> make[4]: *** [cpudefs.o] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/tiemu_3.03-nogdb+dfsg-3_unstable.log

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

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

We believe that the bug you reported is fixed in the latest version of
tiemu, 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.
Andreas B. Mundt  (supplier of updated tiemu 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: Tue, 15 Aug 2017 14:32:28 +0200
Source: tiemu
Binary: tiemu
Architecture: source amd64
Version: 3.03-nogdb+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Andreas B. Mundt 
Description:
 tiemu 

Bug#870229: marked as done (cairo-dock: Adapt to gnome-settings-daemon 3.24)

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2017 14:49:17 +
with message-id 
and subject line Bug#870229: fixed in cairo-dock 3.4.1-1.1
has caused the Debian Bug report #870229,
regarding cairo-dock: Adapt to gnome-settings-daemon 3.24
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.)


-- 
870229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870229
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cairo-dock
Version: 3.4.1-1
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gsd324
Tags: buster sid patch

cairo-dock includes gnome-session files to allow users to easily log
in to a GNOME Flashback session running cairo-dock.
gnome-settings-daemon 3.24 has split itself into separate binaries and
the gnome-session files will no longer work. The new version of
gnome-settings-daemon is available for testing now in Debian
experimental.

In my next email, I will attach a patch that can fix this issue.

We intend to upload gnome-settings-daemon 3.24 to Debian unstable
about a week from now on Sunday, August 6.

I suggest uploading the fix to the DELAYED queue for that date so that
this transition will be easy and smooth.

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: cairo-dock
Source-Version: 3.4.1-1.1

We believe that the bug you reported is fixed in the latest version of
cairo-dock, 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.
Gianfranco Costamagna  (supplier of updated 
cairo-dock 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, 08 Aug 2017 16:04:14 +0200
Source: cairo-dock
Binary: cairo-dock cairo-dock-core cairo-dock-dev
Architecture: source
Version: 3.4.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Cairo-dock Maintainers 

Changed-By: Gianfranco Costamagna 
Description:
 cairo-dock - Metapackage for cairo-dock
 cairo-dock-core - Light eye-candy fully themable animated dock for Linux 
desktop
 cairo-dock-dev - Cairo-dock development file
Closes: 870229
Changes:
 cairo-dock (3.4.1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Jeremy Bicha  ]
   * Adapt to gnome-settings-daemon 3.24 (Closes: #870229)
Checksums-Sha1:
 e8f23ddb4bde2ce131a16761777b00749b4fe8f2 2452 cairo-dock_3.4.1-1.1.dsc
 abff1fa21038750dd92c74100a3140a588c017f3 8616 
cairo-dock_3.4.1-1.1.debian.tar.xz
Checksums-Sha256:
 6418cc8ef00a770a05d3702df3eb06cc83b7c217813011b92dd0108151e47399 2452 
cairo-dock_3.4.1-1.1.dsc
 006c66cf4a7d7fae40fc4c9ef391b3a99b5593b65d5122acb7cabb4b021fa40e 8616 
cairo-dock_3.4.1-1.1.debian.tar.xz
Files:
 93c4517067e2e7d5c150fa2fdb546a83 2452 x11 extra cairo-dock_3.4.1-1.1.dsc
 c0dbb1ae325d6565561941bed48d033b 8616 x11 extra 
cairo-dock_3.4.1-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJZicYCAAoJEPNPCXROn13ZTM0QAKDHNftnNpd8ckqsn2lAt0ph
NGVmronTkaQeugeWDO8veVUgTlqlVvXCkorHN2yVxRU4l2waqDWNK7zRhQOdxXfi
zjivfy7um7d9bbZS+mndErHoISsaxZxj8u+dmULHg9HUP3s2P8sFX7U4dGK+cD73
uC9TV5hkXuHSM2F3WkfzVfN8BTEYnITZzJYi2JpReHM80T0tY46yrfAJfFTpVZei
ldFlHQ5itVj0j6P/hj2/mIB3zuPoNnh/zMKCYW66bSILFHWWK7DTgE8U/aFFW8Cr
49epAVfyhWJB+EOF2dJDbjWbt33Ri9lzeMcnju4dA85bmcR+QwBFnLTr4g5tlDg+
5zhIQmaok7Q+OOI9wHBXxdbkbVYwqid8/9qQX+D2xcku5QY0zb7U9pIasPR+4Slc
IvQk6OWtETdm1iAo3Zu1nBxwRjEPkwcScyafgmcCgwKfeL/QsUBRJIaZPtmJPKpu
6fEQ1VHNZI8J1uZlJnri50qpysazLSNNLFVWDMCNq098LCOv9dM7qmB+b/YMyTvP
lpmyQ6piEIBtgCUkj0pi4uxTXuTBqnCuVV8GOzwUTT4jmpltQ6fPFbwNheEzlY0a
E+LNGeF+HF34ZKNP/H/SClVcbIhsHfvO5CzaMIGM49+GZ0ry1QY7qie4BAFuul0I
WIWlVeJW25b2qbttRztl
=e+ET
-END PGP SIGNATURE End Message ---

Bug#855120: opentk: Please disable OpenGL ES 1 support

[Petter Reinholdtsen]

This release critical issue now keeps  opentk (and also repetier-host)
from entering testing.  Any news on uploading a version without
OpenG ES 1?

-- 
Happy hacking
Petter Reinholdtsen

Bug#872221: amarok: symbol lookup error libavcodec.so.57: undefined symbol: lame_set_VBR_quality

[Adrian Bunk]

On Tue, Aug 15, 2017 at 11:12:00AM +0300, Kostas Papadopoulos wrote:
> Package: amarok
> Version: 2.8.0-8
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> amarok does not start with message:
> 
> amarok: symbol lookup error: /usr/lib/x86_64-linux-gnu/libavcodec.so.57: 
> undefined symbol: lame_set_VBR_quality
>...

Please send the output of the following commands:
  dpkg -l libmp3lame0
  ldd /usr/lib/x86_64-linux-gnu/libavcodec.so.57 | grep libmp3lame


Thanks
Adrian

-- 

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

Bug#871070: in ms-gsl marked as pending

[Nicholas Guriev]

Control: tag 871070 pending

Hello,

Bug #871070 in ms-gsl reported by you has been fixed in the Git repository. You 
can
see the commit message below, and you can check the diff of the fix at:

https://anonscm.debian.org/git/collab-maint/ms-gsl.git/commit/?id=d1efba7

(this message was generated automatically based on the git commit message)
---
commit d1efba70a80f1fc771a1616a8b8262ddbbc491ff
Author: Nicholas Guriev 
Date:   Tue Aug 15 16:27:34 2017 +0300

Add Fix-tests-broken-with-GCC-7.patch

Closes: #871070

Processed: Bug#871070 in ms-gsl marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag 871070 pending
Bug #871070 [src:ms-gsl] ms-gsl: FTBFS: multi_span:1191:57: error: conversion 
to 'long unsigned int' from 'long int' may change the sign of the result 
[-Werror=sign-conversion]
Added tag(s) pending.

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

Bug#872263: linux-image-4.11.0-1-amd64-dbg: file overwrite error upgrading from stretch-backports

[Andreas Beckmann]

Package: linux-image-4.11.0-1-amd64-dbg
Version: 4.11.6-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + linux-image-amd64-dbg

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stretch-backports'.
It installed fine in 'stretch-backports', then the upgrade to 'buster' 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 linux-image-4.11.0-1-amd64-dbg.
  Preparing to unpack .../linux-image-4.11.0-1-amd64-dbg_4.11.6-1_amd64.deb ...
  Unpacking linux-image-4.11.0-1-amd64-dbg (4.11.6-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/linux-image-4.11.0-1-amd64-dbg_4.11.6-1_amd64.deb 
(--unpack):
   trying to overwrite 
'/usr/lib/debug/.build-id/25/99e5c063eeb45c3b0068e66a8251a66f313afa.debug', 
which is also in package linux-image-4.11.0-0.bpo.1-amd64-dbg 4.11.6-1~bpo9+1
  Preparing to unpack .../linux-image-amd64-dbg_4.11+82_amd64.deb ...
  Unpacking linux-image-amd64-dbg (4.11+82) over (4.11+82~bpo9+1) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/linux-image-4.11.0-1-amd64-dbg_4.11.6-1_amd64.deb


cheers,

Andreas


linux-image-amd64-dbg_4.11+82.log.gz
Description: application/gzip

Processed: linux-image-4.11.0-1-amd64-dbg: file overwrite error upgrading from stretch-backports

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + linux-image-amd64-dbg
Bug #872263 [linux-image-4.11.0-1-amd64-dbg] linux-image-4.11.0-1-amd64-dbg: 
file overwrite error upgrading from stretch-backports
Added indication that 872263 affects linux-image-amd64-dbg

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

Bug#872262: jellyfish FTBFS with gcc 7

[Adrian Bunk]

Source: jellyfish
Version: 2.2.6-1
Severity: serious
Tags: patch buster sid

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

...
/bin/bash ./libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I.  
-D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe 
-I/usr/local/include -I/usr/lib/x86_64-linux-gnu/perl/5.26/CORE -I./include 
-Wdate-time -D_FORTIFY_SOURCE=2 -std=c++0x -g -O3 -Werror -std=c++0x -g -O2 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -c -o swig/perl5/swig_perl5_jellyfish_la-swig_wrap.lo 
`test -f 'swig/perl5/swig_wrap.cpp' || echo './'`swig/perl5/swig_wrap.cpp
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -D_REENTRANT -D_GNU_SOURCE -DDEBIAN 
-fwrapv -fno-strict-aliasing -pipe -I/usr/local/include 
-I/usr/lib/x86_64-linux-gnu/perl/5.26/CORE -I./include -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=c++0x -g -O3 -Werror -std=c++0x -g -O2 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -c swig/perl5/swig_wrap.cpp  -fPIC -DPIC -o 
swig/perl5/.libs/swig_perl5_jellyfish_la-swig_wrap.o
swig/perl5/swig_wrap.cpp:1980:36: error: dynamic exception specifications are 
deprecated in C++11 [-Werror=deprecated]
 QueryMerFile(const char* path) throw(std::runtime_error) {
^
swig/perl5/swig_wrap.cpp:2023:35: error: dynamic exception specifications are 
deprecated in C++11 [-Werror=deprecated]
 ReadMerFile(const char* path) throw(std::runtime_error) :
   ^
cc1plus: all warnings being treated as errors
Makefile:1655: recipe for target 
'swig/perl5/swig_perl5_jellyfish_la-swig_wrap.lo' failed
make[3]: *** [swig/perl5/swig_perl5_jellyfish_la-swig_wrap.lo] Error 1


Fix/Workaround is attached.
Description: Don't use -Werror
 The SWIG-generated swig/perl5/swig_wrap.cpp gives warnings with
 gcc 7, don't make these fatal with -Werror.
Author: Adrian Bunk 

--- jellyfish-2.2.6.orig/development.mk
+++ jellyfish-2.2.6/development.mk
@@ -1,4 +1,4 @@
-AM_CXXFLAGS += -Werror
+#AM_CXXFLAGS += -Werror
 
 # Count lines of code
 .PHONY: cloc cloc_jellyfish

Processed: Re: Bug#872223: tex-common: fails to configure, fmtutils reports errors about missing files

[Debian Bug Tracking System]

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

> severity 872223 minor
Bug #872223 [texlive-htmlxml] tex-common: fails to configure, fmtutils reports 
errors about missing files
Severity set to 'minor' from 'serious'
> thanks
Stopping processing here.

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

Bug#872223: tex-common: fails to configure, fmtutils reports errors about missing files

[Guillem Jover]

Control: reassign -1 texlive-htmlxml
Control: severity -1 serious

Hi!

On Tue, 2017-08-15 at 11:09:47 +0200, ydir...@free.fr wrote:
> Well, probably not a missing Conflicts, as downgrading tex-common to
> the stretch version does not fix the problem.  Really a problem with
> missing files that should not be missing.
> 
> In fact, despite having the package installed, there is no such .ini files
> on my system.  packages.d.o shows that texlive-htmlxml from stretch should
> have them, but for some reason they do not appear on my system:

I've not tried to reproduce this, but from the details that you give
later on it seems obvious this is a problem with the package (and the
downgrade procedure).

The files within texlive-htmlxml appear to have been moved in later
version into several other package. Those other packages contain
proper Replaces fields. I'm assuming you have just downgraded the
packages in the "wrong" (or unexpected) order. So that you downgraded
texlive-htmlxml first, dpkg honored the Replaces fields and didn't
transfer ownership from the new packages to the downgraded one. Then
you downgraded the other packages now owning those files, but not on
the old versions, and those files just disappeared.

In this case there are some Depends/Breaks/Conflicts fields missing
somewhere at least to handle downgrades. But I've not checked if also
to handle upgrades?

> What's common to those packages are that they were downgraded from buster 
> back to stretch (they had been mistakingly upgraded):
> 
> texlive-htmlxml:amd64 (2017.20170629-1, 2016.20170123-5)
> texlive-generic-recommended:amd64 (2017.20170629-1, 2016.20170123-5)

Thanks,
Guillem

Processed: Re: Bug#872223: tex-common: fails to configure, fmtutils reports errors about missing files

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 texlive-htmlxml
Bug #872223 [dpkg] tex-common: fails to configure, fmtutils reports errors 
about missing files
Bug reassigned from package 'dpkg' to 'texlive-htmlxml'.
Ignoring request to alter found versions of bug #872223 to the same values 
previously set
Ignoring request to alter fixed versions of bug #872223 to the same values 
previously set
> severity -1 serious
Bug #872223 [texlive-htmlxml] tex-common: fails to configure, fmtutils reports 
errors about missing files
Severity set to 'serious' from 'grave'

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

Bug#865659: marked as done (scilab: Segmentation fault at launch. It was working before an upgrade performed on 21 June.)

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2017 13:52:27 +0200
with message-id 
and subject line Re: Bug#865522: scilab: Segmentation fault at lauch
has caused the Debian Bug report #865522,
regarding scilab: Segmentation fault at launch. It was working before an 
upgrade performed on 21 June.
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.)


-- 
865522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865522
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: scilab
Version: 5.5.1-7
Severity: important

Dear Maintainer,

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

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

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



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

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

Versions of packages scilab depends on:
ii  scilab-cli   5.5.1-7
ii  scilab-full-bin  5.5.1-7

Versions of packages scilab recommends:
ii  scilab-doc  5.5.1-7

Versions of packages scilab suggests:
pn  scilab-doc-fr 
pn  scilab-doc-ja 
pn  scilab-doc-pt-br  

-- no debconf information

*** /home/moralles/Scilab_Bug.txt
SCILABBIN : scilab-bin
DISABLE_JAVA_DETECTION : 0
SCILAB_MODE : gui
OS : Linux
MODEL : x86_64
IS_SCILAB_BINARY : 0
Using specified vm: /usr/lib/jvm/java-8-oracle
JAVA_HOME : /usr/lib/jvm/java-8-oracle
SCI : /usr/share/scilab/
SCIBIN : /usr/bin/scilab-bin
PATH :
/usr/share/scilab/:/usr/share/scilab//bin:/usr/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/usr/lib/jvm/java-8-oracle/bin:/usr/lib/jvm/java-8-oracle/db/bin:/usr/lib/jvm/java-8-oracle/jre/bin
CLASSPATH : /usr/share/scilab//modules/core/jar/org.scilab.modules.core.jar
EGL_DRIVER :
LD_LIBRARY_PATH :
/usr/lib/scilab/:/usr/lib64/scilab/:.:/usr/lib/jvm/java-8-oracle/jre/lib/amd64/:/usr/lib/jvm/java-8-oracle/jre/lib/amd64/server/:/usr/lib/jvm/java-8-oracle/jre/lib/amd64/native_threads/
--- End Message ---
--- Begin Message ---
Hi,

On Fri, 23 Jun 2017 15:58:40 -0300 Marcio Bezerra
 wrote:
> Looks like this bug was introduced in the latest kernel libraries update.
> Scilab was working just fine less than 24 hours ago. Scilab-cli is working
> but is very limited. Does anyone know of a workaround for this kind of
> problem? How long does it usually take for them to release a patch?
> 
> I have downloaded Octave but it's not the same.
> 
> Much appreciated.
> 
> Marcio
> 
> On Fri, Jun 23, 2017 at 3:24 PM, trb  wrote:
> 
> > I have the same bug on Debian 9 with KDE Plasma.
> > I had the same problem on Arch, maybe this is related to the kernel ? (
> > https://bugs.launchpad.net/ubuntu/+source/scilab/+bug/1699892 )
> >
> > Best regards,
> > Piotr
> >

According to [1] this is kernel bug #865311 [2] which is now fixed, thus
closing this one.

[1] https://askubuntu.com/a/927824
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865311

_g.



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

Bug#865522: marked as done (scilab: Segmentation fault at lauch)

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2017 13:52:27 +0200
with message-id 
and subject line Re: Bug#865522: scilab: Segmentation fault at lauch
has caused the Debian Bug report #865522,
regarding scilab: Segmentation fault at lauch
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.)


-- 
865522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865522
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: scilab
Version: 5.5.2-4
Severity: grave
Justification: renders package unusable

When lanching scilab, I have "Segmentation fault" (no more information). Tested
on a fresh install of Debian Stretch.



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

Kernel: Linux 4.9.0-3-amd64 (SMP w/8 CPU cores)
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 /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages scilab depends on:
ii scilab-cli 5.5.2-4
ii scilab-full-bin 5.5.2-4+b1

Versions of packages scilab recommends:
ii scilab-doc 5.5.2-4

Versions of packages scilab suggests:
pn scilab-doc-fr 
pn scilab-doc-ja 
pn scilab-doc-pt-br 

-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,

On Fri, 23 Jun 2017 15:58:40 -0300 Marcio Bezerra
 wrote:
> Looks like this bug was introduced in the latest kernel libraries update.
> Scilab was working just fine less than 24 hours ago. Scilab-cli is working
> but is very limited. Does anyone know of a workaround for this kind of
> problem? How long does it usually take for them to release a patch?
> 
> I have downloaded Octave but it's not the same.
> 
> Much appreciated.
> 
> Marcio
> 
> On Fri, Jun 23, 2017 at 3:24 PM, trb  wrote:
> 
> > I have the same bug on Debian 9 with KDE Plasma.
> > I had the same problem on Arch, maybe this is related to the kernel ? (
> > https://bugs.launchpad.net/ubuntu/+source/scilab/+bug/1699892 )
> >
> > Best regards,
> > Piotr
> >

According to [1] this is kernel bug #865311 [2] which is now fixed, thus
closing this one.

[1] https://askubuntu.com/a/927824
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865311

_g.



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

Bug#872197: marked as done (notmuch: deletes shipped file on reinstall: /etc/emacs/site-start.d/50notmuch.el)

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2017 11:34:10 +
with message-id 
and subject line Bug#872197: fixed in notmuch 0.25-6
has caused the Debian Bug report #872197,
regarding notmuch: deletes shipped file on reinstall: 
/etc/emacs/site-start.d/50notmuch.el
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.)


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

Hi,

during a test with piuparts I noticed reinstalling your package
deletes a conffile it shipped.

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

  Selecting previously unselected package notmuch.
  (Reading database ... 
(Reading database ... 5029 files and directories currently installed.)
  Preparing to unpack .../notmuch_0.25-5_amd64.deb ...
  Unpacking notmuch (0.25-5) ...
  Setting up notmuch (0.25-5) ...
[...]
  Removing notmuch (0.25-5) ...
[...]
  Selecting previously unselected package notmuch.
  (Reading database ... 
(Reading database ... 5032 files and directories currently installed.)
  Preparing to unpack .../notmuch_0.25-5_amd64.deb ...
  Unpacking notmuch (0.25-5) ...
  Setting up notmuch (0.25-5) ...
  Removing obsolete conffile /etc/emacs/site-start.d/50notmuch.el ...
[...]
0m24.4s ERROR: FAIL: debsums reports modifications inside the chroot:
  debsums: missing file /etc/emacs/site-start.d/50notmuch.el (from notmuch 
package)


According to the changelog that conffile should no longer be
shipped by the package.


cheers,

Andreas


notmuch_0.25-5.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: notmuch
Source-Version: 0.25-6

We believe that the bug you reported is fixed in the latest version of
notmuch, 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.
David Bremner  (supplier of updated notmuch 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, 15 Aug 2017 07:52:21 -0300
Source: notmuch
Binary: notmuch libnotmuch5 libnotmuch-dev python-notmuch python3-notmuch 
ruby-notmuch notmuch-emacs elpa-notmuch notmuch-vim notmuch-mutt
Architecture: source
Version: 0.25-6
Distribution: unstable
Urgency: medium
Maintainer: Carl Worth 
Changed-By: David Bremner 
Description:
 elpa-notmuch - thread-based email index, search and tagging (emacs interface)
 libnotmuch-dev - thread-based email index, search and tagging (development)
 libnotmuch5 - thread-based email index, search and tagging (runtime)
 notmuch- thread-based email index, search and tagging
 notmuch-emacs - thread-based email index, search and tagging (transitional 
packag
 notmuch-mutt - thread-based email index, search and tagging (Mutt interface)
 notmuch-vim - thread-based email index, search and tagging (vim interface)
 python-notmuch - Python interface to the notmuch mail search and index library
 python3-notmuch - Python 3 interface to the notmuch mail search and index 
library
 ruby-notmuch - Ruby interface to the notmuch mail search and index library
Closes: 872197
Changes:
 notmuch (0.25-6) unstable; urgency=medium
 .
   * Bug fix: "deletes shipped file on reinstall:
 /etc/emacs/site-start.d/50notmuch.el", thanks to Andreas Beckmann
 (Closes: #872197).
Checksums-Sha1:
 d5575e8f73399230deb8c1e3645cfb0e952abcf1 2899 notmuch_0.25-6.dsc
 aac1a31253679aa99d6bd295b48c6e8be284f4a9 15888 notmuch_0.25-6.debian.tar.xz
 52200c4425ea8bb2ed475cb4ca1c143fa084b37e 13912 notmuch_0.25-6_amd64.buildinfo
Checksums-Sha256:
 a9a0c84f86bce3564d643c548751b8af0e15dcc92faacf829ee58da18710afcf 2899 
notmuch_0.25-6.dsc
 ebad3547b19363466cbb4d517a751fd94468509dd7668c6c45cf2368eb304389 15888 
notmuch_0.25-6.debian.tar.xz
 911cf7eb612a3c130a5e671d59b538328a0ce9b0cebdb207956b1e865e23e436 13912 
notmuch_0.25-6_amd64.buildinfo
Files:
 75938a5fc6417731b392ef2cce7606bd 2899 mail optional notmuch_0.25-6.dsc
 

Bug#867277: closed by Joost van Baal-Ilić <joos...@debian.org> (Bug#867277: fixed in systraq 20160803-2)

[Andreas Beckmann]

Control: found -1 20160803-2

after removal:

# test -f /etc/systraq/Makefile && command -v make >/dev/null && su -s /bin/sh 
-c 'make -s -C /etc/systraq' debian-systraq
# echo $?
1

try this:

# test ! -f /etc/systraq/Makefile || ! command -v make >/dev/null || su -s 
/bin/sh -c 'make -s -C /etc/systraq' debian-systraq
# echo $?
0

Andreas

Processed: Re: Bug#867277 closed by Joost van Baal-Ilić <joos...@debian.org> (Bug#867277: fixed in systraq 20160803-2)

[Debian Bug Tracking System]

Processing control commands:

> found -1 20160803-2
Bug #867277 {Done: Joost van Baal-Ilić } [systraq] systraq: 
dpkg hook fails after package removal
Marked as found in versions systraq/20160803-2; no longer marked as fixed in 
versions systraq/20160803-2 and reopened.

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

Bug#871357: packaging-tutorial: FTBFS: Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in m/\\end{ <-- HERE document}/ at /usr/share/perl5/Locale/Po4a/TransTractor.pm line 6

[Lucas Nussbaum]

On 08/08/17 at 16:13 -0400, gregor herrmann wrote:
> Control: tag -1 + patch
> 
> On Mon, 07 Aug 2017 11:58:29 -0400, Lucas Nussbaum wrote:
> 
> > > Unescaped left brace in regex is illegal here in regex; marked by <-- 
> > > HERE in m/\\end{ <-- HERE document}/ at 
> > > /usr/share/perl5/Locale/Po4a/TransTractor.pm line 643.
> > > debian/rules:13: recipe for target 'override_dh_auto_build' failed
> > > make[1]: *** [override_dh_auto_build] Error 255
> 
> That's an interesting bug.
> 
> The error is in /usr/share/perl5/Locale/Po4a/TransTractor.pm:643
> which is
> my $found = scalar grep { /$position/ } @{$self->{TT}{doc_out}};
> and $position (comes from addendum_parse() in the same file and)
> contains '\\end{document}' at that point.
> 
> And this '\\end{document}' itself comes from files in the
> packaging-tutorial po4a directory.
> 
> So I don't know if po4a needs a generic fix, or packaging-tutorial
> needs to change how it uses it.
> 
> I'm attaching a patch for the second option.

Thanks, patch applied and package uploaded!

Lucas

Bug#871357: marked as done (packaging-tutorial: FTBFS: Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in m/\\end{ <-- HERE document}/ at /usr/share/perl5/Locale/Po4a/TransT

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2017 10:49:04 +
with message-id 
and subject line Bug#871357: fixed in packaging-tutorial 0.21
has caused the Debian Bug report #871357,
regarding packaging-tutorial: FTBFS: Unescaped left brace in regex is illegal 
here in regex; marked by <-- HERE in m/\\end{ <-- HERE document}/ at 
/usr/share/perl5/Locale/Po4a/TransTractor.pm line 643.
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.)


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # version check
> if [ 0.20 != 0.20 ]; then echo "Wrong version in .tex: 0.20 != 0.20"; exit 1; 
> fi
> #translate source files before building pdf
> po4a po4a/po4a.cfg --verbose --keep 50
> Updating po4a/po//packaging-tutorial.pot:
>  (628 entries)
> Updating po4a/po//de.po: 
> 
>  done.
> po4a/po//de.po: 628 translated messages.
> Updating po4a/po//es.po: 
> .
>  done.
> po4a/po//es.po: 453 translated messages, 112 fuzzy translations, 63 
> untranslated messages.
> Updating po4a/po//fr.po: 
> ..
>  done.
> po4a/po//fr.po: 628 translated messages.
> Updating po4a/po//ja.po: 
> ..
>  done.
> po4a/po//ja.po: 540 translated messages, 66 fuzzy translations, 22 
> untranslated messages.
> Updating po4a/po//pt.po: 
> .
>  done.
> po4a/po//pt.po: 628 translated messages.
> Updating po4a/po//ru.po: 
> ...
>  done.
> po4a/po//ru.po: 628 translated messages.
> Updating po4a/po//zh_TW.po: 
> ...
>  done.
> po4a/po//zh_TW.po: 628 translated messages.
> packaging-tutorial.de.tex is 100% translated (731 strings).
> debiantutorial.de.sty is 100% translated (1 strings).
> Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in 
> m/\\end{ <-- HERE document}/ at /usr/share/perl5/Locale/Po4a/TransTractor.pm 
> line 643.
> debian/rules:13: recipe for target 'override_dh_auto_build' failed
> make[1]: *** [override_dh_auto_build] Error 255

The full build log is available from:
   http://aws-logs.debian.net/2017/08/07/packaging-tutorial_0.20_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: packaging-tutorial
Source-Version: 0.21

We believe that the bug you reported is fixed in the latest version of
packaging-tutorial, 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.
Lucas Nussbaum  (supplier of updated packaging-tutorial 
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: Tue, 15 Aug 2017 12:06:37 +0200
Source: packaging-tutorial
Binary: packaging-tutorial
Architecture: source
Version: 0.21
Distribution: unstable
Urgency: medium
Maintainer: Lucas Nussbaum 
Changed-By: Lucas 

Processed: acutlly execute the commands

[Debian Bug Tracking System]

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

> clone 862576 -1
Bug #862576 {Done: Adrian Bunk } [squeak-vm] etoys: Doesn't 
get beyond Squeak security key generation
Bug 862576 cloned as bug 872252
> reopen -1
Bug #872252 {Done: Adrian Bunk } [squeak-vm] etoys: Doesn't 
get beyond Squeak security key generation
'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 squeak-vm/1:4.10.2.2614-4.1.
> severity -1 important
Bug #872252 [squeak-vm] etoys: Doesn't get beyond Squeak security key generation
Severity set to 'important' from 'grave'
> retitle -1 squeak-vm: Replace -O1 workaround with proper fix
Bug #872252 [squeak-vm] etoys: Doesn't get beyond Squeak security key generation
Changed Bug title to 'squeak-vm: Replace -O1 workaround with proper fix' from 
'etoys: Doesn't get beyond Squeak security key generation'.
> thanks
Stopping processing here.

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

Processed: banshee: diff for NMU version 2.6.2-6.2

[Debian Bug Tracking System]

Processing control commands:

> tags 790198 + patch
Bug #790198 [src:banshee] banshee: depends on libwebkitgtk-1.0-0 which is 
deprecated
Added tag(s) patch.
> tags 790198 + pending
Bug #790198 [src:banshee] banshee: depends on libwebkitgtk-1.0-0 which is 
deprecated
Added tag(s) pending.

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

Bug#790198: banshee: diff for NMU version 2.6.2-6.2

[Adrian Bunk]

Control: tags 790198 + patch
Control: tags 790198 + pending

Dear maintainer,

I've prepared an NMU for banshee (versioned as 2.6.2-6.2) and uploaded 
it to DELAYED/10. Please feel free to tell me if I should cancel it.

cu
Adrian

-- 

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

diff -Nru banshee-2.6.2/debian/changelog banshee-2.6.2/debian/changelog
--- banshee-2.6.2/debian/changelog	2016-12-10 16:55:57.0 +0200
+++ banshee-2.6.2/debian/changelog	2017-08-15 13:12:12.0 +0300
@@ -1,3 +1,11 @@
+banshee (2.6.2-6.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Disable webkit features, the currently used library will not
+be in buster. (Closes: #790198)
+
+ -- Adrian Bunk   Tue, 15 Aug 2017 13:12:12 +0300
+
 banshee (2.6.2-6.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru banshee-2.6.2/debian/control banshee-2.6.2/debian/control
--- banshee-2.6.2/debian/control	2016-04-05 04:29:26.0 +0300
+++ banshee-2.6.2/debian/control	2017-08-15 13:12:12.0 +0300
@@ -27,7 +27,6 @@
libgtk-sharp-beans2.0-cil-dev (>= 2.8),
libgpod-cil-dev (>= 0.8.2),
libkarma-cil-dev (>= 0.0.5),
-   libwebkitgtk-dev (>= 1.2.2) | libwebkit-dev (>= 1.2.2),
libsoup2.4-dev (>= 2.26),
libsoup-gnome2.4-dev (>= 2.26),
libgdata-cil-dev (>= 1.7),
diff -Nru banshee-2.6.2/debian/rules banshee-2.6.2/debian/rules
--- banshee-2.6.2/debian/rules	2016-12-10 16:55:57.0 +0200
+++ banshee-2.6.2/debian/rules	2017-08-15 13:12:12.0 +0300
@@ -28,7 +28,7 @@
 	--disable-torrent \
 	--enable-meego \
 	--enable-gapless-playback \
-	--enable-webkit \
+	--disable-webkit \
 	--disable-boo \
 	--enable-release \
 	--disable-shave \

Bug#868905: condor: FTBFS: ld: final link failed: Bad value

[peter green]

FYI I tried to build the ubuntu version of the package under raspbian buster 
and got.

[ 98%] Building CXX object 
src/cream_gahp/CMakeFiles/cream_gahp.dir/cream_gahp_server.cpp.o
cd "/condor-8.4.11~dfsg.1/obj-arm-linux-gnueabihf/src/cream_gahp" && /usr/bin/c++  -DARMV7L=ARMV7L -DBUILD_DATE="\"Aug 12 2017\"" -DCONDOR_VERSION=\"8.4.11\" -DGLIBC224=GLIBC224 -DGLIBC=GLIBC -DHAVE_CONFIG_H -DLINUX=\"LINUX_3.8.13.30\" -DPLATFORM=\"ARMV7L-Raspbian_\" -DPRE_RELEASE_STR="\" Debian-8.4.11~dfsg.1-1ubuntu1\"" -DWITH_OPENSSL -D_REENTRANT -I"/condor-8.4.11~dfsg.1/obj-arm-linux-gnueabihf/bld_external/classads-8.4.11/install/include" -I/usr/include/globus -I/usr/lib64/globus/include -I/usr/lib/globus/include -I/usr/include/arm-linux-gnueabihf/globus -I/usr/local/globus/include/globus -I"/condor-8.4.11~dfsg.1/src/condor_includes" -I"/condor-8.4.11~dfsg.1/obj-arm-linux-gnueabihf/src/condor_includes" -I"/condor-8.4.11~dfsg.1/src/condor_utils" -I"/condor-8.4.11~dfsg.1/obj-arm-linux-gnueabihf/src/condor_utils" -I"/condor-8.4.11~dfsg.1/src/condor_daemon_core.V6" -I"/condor-8.4.11~dfsg.1/src/condor_daemon_client" -I"/condor-8.4.11~dfsg.1/src/ccb" 
-I"/condor-8.4.11~dfsg.1/src/condor_io" -I"/condor-8.4.11~dfsg.1/src/h" -I"/condor-8.4.11~dfsg.1/obj-arm-linux-gnueabihf/src/h" -I"/condor-8.4.11~dfsg.1/obj-arm-linux-gnueabihf/src/classad" -I"/condor-8.4.11~dfsg.1/src/classad" -I"/condor-8.4.11~dfsg.1/src/safefile" -I"/condor-8.4.11~dfsg.1/obj-arm-linux-gnueabihf/src/safefile"  -g -O2 -fdebug-prefix-map=/condor-8.4.11~dfsg.1=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 -DWITH_IPV6 -g -O2 -fdebug-prefix-map=/condor-8.4.11~dfsg.1=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Wall -W -Wextra -Wfloat-equal -Wendif-labels -Wpointer-arith -Wcast-qual -Wcast-align -Wvolatile-register-var -Wno-error=unused-local-typedefs -Wdeprecated-declarations -Wno-error=deprecated-declarations -Wno-nonnull-compare -Wno-error=nonnull-compare -fstack-protector -rdynamic -g -Wno-shadow -o CMakeFiles/cream_gahp.dir/cream_gahp_server.cpp.o 
-c "/condor-8.4.11~dfsg.1/src/cream_gahp/cream_gahp_server.cpp"

/condor-8.4.11~dfsg.1/src/cream_gahp/cream_gahp_server.cpp:36:59: fatal error: 
glite/ce/cream-client-api-c/CreamProxyFactory.h: No such file or directory
 #include "glite/ce/cream-client-api-c/CreamProxyFactory.h"

I have not yet fully investigated this failure.

Processed: impressive: diff for NMU version 0.11.1-1.2

[Debian Bug Tracking System]

Processing control commands:

> tags 867092 + patch
Bug #867092 [src:impressive] impressive: Build-dependency latex-beamer no 
longer available
Added tag(s) patch.
> tags 867092 + pending
Bug #867092 [src:impressive] impressive: Build-dependency latex-beamer no 
longer available
Added tag(s) pending.

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

Bug#867092: impressive: diff for NMU version 0.11.1-1.2

[Adrian Bunk]

Control: tags 867092 + patch
Control: tags 867092 + pending

Dear maintainer,

I've prepared an NMU for impressive (versioned as 0.11.1-1.2) and 
uploaded it to DELAYED/10. Please feel free to tell me if I should 
cancel it.

cu
Adrian

-- 

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

diff -Nru impressive-0.11.1/debian/changelog impressive-0.11.1/debian/changelog
--- impressive-0.11.1/debian/changelog	2017-02-04 11:59:00.0 +0200
+++ impressive-0.11.1/debian/changelog	2017-08-15 13:01:55.0 +0300
@@ -1,3 +1,11 @@
+impressive (0.11.1-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Update the build dependency from latex-beamer
+to texlive-latex-recommended. (Closes: #867092)
+
+ -- Adrian Bunk   Tue, 15 Aug 2017 13:01:55 +0300
+
 impressive (0.11.1-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru impressive-0.11.1/debian/control impressive-0.11.1/debian/control
--- impressive-0.11.1/debian/control	2017-02-04 11:42:42.0 +0200
+++ impressive-0.11.1/debian/control	2017-08-15 13:01:55.0 +0300
@@ -7,7 +7,7 @@
  perl,
  texlive-latex-base,
  texlive-latex-extra,
- latex-beamer,
+ texlive-latex-recommended,
  texlive-fonts-recommended,
  texlive-pictures,
  xvfb,

Bug#870362: marked as done (ariba FTBFS with bowtie2 2.3.2-2)

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2017 10:04:02 +
with message-id 
and subject line Bug#870362: fixed in ariba 2.10.1+ds-1
has caused the Debian Bug report #870362,
regarding ariba FTBFS with bowtie2 2.3.2-2
to be marked as done.

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

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


-- 
870362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870362
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ariba
Version: 2.10.0+ds-1
Severity: serious

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

...
==
FAIL: Test run_bowtie2 unsorted
--
Traceback (most recent call last):
  File "/build/1st/ariba-2.10.0+ds/ariba/tests/mapping_test.py", line 62, in 
test_run_bowtie2
self.assertListEqual(expected, got)
AssertionError: Lists differ: [('1', 99, 'ref', 0, [(4, 5), (0, 20)], 
'AGCCCTC[857 chars]AT')] != [('1', 153, 'ref', 30, [(0, 25)], 
'AGGATACAGATCT[795 chars]AT')]

First differing element 0:
('1', 99, 'ref', 0, [(4, 5), (0, 20)], 'AGCCCTCCACAGGATGGTGGTATAC')
('1', 153, 'ref', 30, [(0, 25)], 'AGGATACAGATCTTGTGGGAAAGGT')

- [('1', 99, 'ref', 0, [(4, 5), (0, 20)], 'AGCCCTCCACAGGATGGTGGTATAC'),
-  ('1', 147, 'ref', 30, [(0, 25)], 'AGGATACAGATCTTGTGGGAAAGGT'),
? ^   ^^

+ [('1', 153, 'ref', 30, [(0, 25)], 'AGGATACAGATCTTGTGGGAAAGGT'),
? ^   ^^

+  ('1', 101, None, 30, [], 'AGCCCTCCACAGGATGGTGGTATAC'),
-  ('2', 99, 'ref', 124, [(0, 25)], 'TAATGTTCTTAGGGCTTACCATAGA'),
?^^

+  ('2', 73, 'ref', 124, [(0, 25)], 'TAATGTTCTTAGGGCTTACCATAGA'),
?^^

-  ('2', 147, 'ref', 170, [(0, 20), (4, 5)], 'TCCACCTTAGCTAAGCGCAGACTCG'),
+  ('2', 133, None, 124, [], 'CGAGTCTGCGCTTAGCTAAGGTGGA'),
   ('3', 73, 'ref', 86, [(0, 25)], 'TCGGGTCTGTACAAGGACGGATGGT'),
   ('3', 133, None, 86, [], 'CGTACTGACTGACTGACGTACTGCA'),
   ('4', 99, 'ref', 55, [(0, 25)], 'CCGCCGGGAAGTCCTTCTGTCGTGC'),
   ('4', 147, 'ref', 136, [(0, 25)], 'GGCTTACCATAGAGGTACACT'),
-  ('5', 99, 'ref', 0, [(4, 2), (0, 23)], 'CCTCCACAGGATGGTGGTATACCTG'),
?^^  ^^ --  ^   ---

+  ('5', 77, None, -1, [], 'CCTCCACAGGATGGTGGTATACCTG'),
?^^  ^^^   ^^

-  ('5', 147, 'ref', 166, [(0, 24), (4, 1)], 'TTCATCCACCTTAGCTAAGCGCAGA'),
+  ('5', 141, None, -1, [], 'TCTGCGCTTAGCTAAGGTGGATGAA'),
   ('6', 77, None, -1, [], 'CAGTTGCATGACGTCATGCAGTCAT'),
   ('6', 141, None, -1, [], 'AATGAGTATGATGAGTAATGGTATG'),
   ('7', 99, 'ref', 56, [(4, 1), (0, 23), (4, 1)], 'ACGCCGGGAAGTCCTTCTGTCGTGT'),
   ('7', 147, 'ref', 136, [(0, 24), (4, 1)], 'GGCTTACCATAGAGGTACACTAAAT')]

==
FAIL: Test run_bowtie2 sorted
--
Traceback (most recent call last):
  File "/build/1st/ariba-2.10.0+ds/ariba/tests/mapping_test.py", line 105, in 
test_run_bowtie2_and_sort
self.assertListEqual(expected, got)
AssertionError: Lists differ: [('1', 99, 'ref', 0, [(4, 5), (0, 20)], 
'AGCCCTC[857 chars]TG')] != [('1', 101, None, 30, [], 
'AGCCCTCCACAGGATGGTGGT[795 chars]TG')]

First differing element 0:
('1', 99, 'ref', 0, [(4, 5), (0, 20)], 'AGCCCTCCACAGGATGGTGGTATAC')
('1', 101, None, 30, [], 'AGCCCTCCACAGGATGGTGGTATAC')

Diff is 1434 characters long. Set self.maxDiff to None to see it.

--
Ran 335 tests in 173.301s

FAILED (failures=2)
debian/rules:23: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Source: ariba
Source-Version: 2.10.1+ds-1

We believe that the bug you reported is fixed in the latest version of
ariba, 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.
Sascha Steinbiss  (supplier of updated ariba 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, 15 Aug 2017 10:37:13 +0200
Source: ariba
Binary: ariba
Architecture: 

Bug#872247: cyrus-admin: broken symlink: /usr/bin/{installsieve, sieveshell} -> ../sbin/cyrus

[Andreas Beckmann]

Package: cyrus-admin
Version: 2.5.10-3
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.7s ERROR: FAIL: Broken symlinks:
  /usr/bin/sieveshell -> ../sbin/cyrus
  /usr/bin/installsieve -> ../sbin/cyrus


cheers,

Andreas


cyrus-admin_2.5.10-3.log.gz
Description: application/gzip

Processed: numexpr: Debug packages should not be removed

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:pytables
Bug #872239 [src:numexpr] numexpr: Debug packages should not be removed
Added indication that 872239 affects src:pytables

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

Bug#872239: numexpr: Debug packages should not be removed

[Dmitry Shachnev]

Source: numexpr
Version: 2.6.2-1
Severity: serious
Justification: makes pytables FTBFS
Control: affects -1 src:pytables

Dear maintainer,

The changelog for numexpr 2.6.2-1 says:

  numexpr (2.6.2-1) unstable; urgency=medium

[...]
* Drop -dbg package declaration (now debug packages are automatically
  generated)

This is not true. The automatically generated dbgsym packages only contain
the debugging symbols for the C extension files. However, the former -dbg
packages contained the extensions built for Python debug interpreter:

  $ dpkg -L python3-numexpr-dbg
  
/usr/lib/python3/dist-packages/numexpr/interpreter.cpython-35dm-x86_64-linux-gnu.so
  
/usr/lib/python3/dist-packages/numexpr/interpreter.cpython-36dm-x86_64-linux-gnu.so
  [...]

These files are needed when you want to use numexpr with the debug
interpreter, i.e. /usr/bin/python3-dbg; and they are not present in the
automatic dbgsym packages. So please revert dropping the -dbg packages.

This was also discussed on debian-python mailing list several times, i.e.:
https://lists.debian.org/debian-python/2016/04/msg00093.html

I am setting the severity to serious to prevent the new upload from migrating
to testing; please feel free to downgrade it if you want.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#872237: liblldb-4.0-dev: broken symlink: /usr/lib/llvm-4.0/lib/liblldb-4.0.so -> liblldb-4.0.so.1

[Andreas Beckmann]

Package: liblldb-4.0-dev
Version: 1:4.0.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + python-lldb-4.0 lldb-4.0

Hi,

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

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

0m36.6s ERROR: FAIL: Broken symlinks:
  /usr/lib/llvm-4.0/lib/liblldb-4.0.so -> liblldb-4.0.so.1
  /usr/lib/llvm-4.0/lib/liblldb-4.0.1.so -> liblldb-4.0.so

But there is /usr/lib/x86_64-linux-gnu/liblldb-4.0.so.1 in liblldb-4.0.


cheers,

Andreas


lldb-4.0_1:4.0.1-1.log.gz
Description: application/gzip

Processed: liblldb-4.0-dev: broken symlink: /usr/lib/llvm-4.0/lib/liblldb-4.0.so -> liblldb-4.0.so.1

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + python-lldb-4.0 lldb-4.0
Bug #872237 [liblldb-4.0-dev] liblldb-4.0-dev: broken symlink: 
/usr/lib/llvm-4.0/lib/liblldb-4.0.so -> liblldb-4.0.so.1
Added indication that 872237 affects python-lldb-4.0 and lldb-4.0

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

Bug#872233: lib{, x}32objc-5-dev: broken symlink: /usr/lib/gcc/x86_64-linux-gnu/5/{, x}32/libobjc_gc.so -> ../../../../../lib32/libobjc_gc.so.4

[Andreas Beckmann]

Package: lib32objc-5-dev,libx32objc-5-dev
Version: 5.4.1-11
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...):

0m26.7s ERROR: FAIL: Broken symlinks:
  /usr/lib/gcc/x86_64-linux-gnu/5/32/libobjc_gc.so -> 
../../../../../lib32/libobjc_gc.so.4

0m26.6s ERROR: FAIL: Broken symlinks:
  /usr/lib/gcc/x86_64-linux-gnu/5/x32/libobjc_gc.so -> 
../../../../../libx32/libobjc_gc.so.4


cheers,

Andreas


lib32objc-5-dev_5.4.1-11.log.gz
Description: application/gzip

Bug#872037: marked as done (libvigrampex: Failure in MultiArrayPointoperatorsTest::testCombine2() [mips64el])

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2017 08:50:14 +
with message-id 
and subject line Bug#872037: fixed in libvigraimpex 
1.10.0+git20160211.167be93+dfsg-5
has caused the Debian Bug report #872037,
regarding libvigrampex: Failure in MultiArrayPointoperatorsTest::testCombine2() 
[mips64el]
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.)


-- 
872037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872037
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libvigraimpex
Version: 1.10.0+git20160211.167be93+dfsg-4
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Current Vigra FTBFS on mips64el [1]:


[ 63%] Building CXX object 
test/multiarray/CMakeFiles/test_multiarray.dir/testsuccess.cxx.o
cd 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/obj/test/multiarray 
&& /usr/bin/c++  -DHasHDF5 -DHasJPEG -DHasPNG -DHasTIFF 
-I/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/include 
-I/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/test/include 
-I/usr/include/hdf5/serial  -std=c++11 -pthread -W -Wall -Wextra 
-Wno-unused-parameter -Wno-sign-compare -Wno-unused-variable -Wno-type-limits 
-g -O2 
-fdebug-prefix-map=/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg=.
 -fstack-protector-strong -Wformat -Werror=format-security -pipe -Wdate-time 
-D_FORTIFY_SOURCE=2   -o CMakeFiles/test_multiarray.dir/testsuccess.cxx.o -c 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/obj/test/multiarray/testsuccess.cxx
[ 65%] Linking CXX executable test_multiarray
cd 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/obj/test/multiarray 
&& /usr/bin/cmake -E cmake_link_script CMakeFiles/test_multiarray.dir/link.txt 
--verbose=1
/usr/bin/c++  -std=c++11 -pthread -W -Wall -Wextra -Wno-unused-parameter 
-Wno-sign-compare -Wno-unused-variable -Wno-type-limits -g -O2 
-fdebug-prefix-map=/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg=.
 -fstack-protector-strong -Wformat -Werror=format-security -pipe -Wdate-time 
-D_FORTIFY_SOURCE=2  -rdynamic CMakeFiles/test_multiarray.dir/test.cxx.o 
CMakeFiles/test_multiarray.dir/testsuccess.cxx.o  -o test_multiarray 
-Wl,-rpath,/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/obj/src/impex:/usr/lib/mips64el-linux-gnuabi64/hdf5/serial
 ../../src/impex/libvigraimpex.so.6.1.11.0 -ljpeg -lpng -lz -ltiff -lIlmImf 
-lImath -lHalf -lIex -lIlmThread 
/usr/lib/mips64el-linux-gnuabi64/hdf5/serial/libhdf5.so 
/usr/lib/mips64el-linux-gnuabi64/hdf5/serial/libhdf5_hl.so -lsz -lz -ltiff 
-lIlmImf -lImath -lHalf -lIex -lIlmThread 
/usr/lib/mips64el-linux-gnuabi64/hdf5/serial/libhdf5.so 
/usr/lib/mips64el-linux-gnuabi64/hdf5/serial/libhdf5_hl.so -lsz 
Running test_multiarray
cd 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/obj/test/multiarray 
&& ./run_test_multiarray.sh
Entering test suite MultiArrayTestSuite
All (24) tests passed in test suite MultiArrayTestSuite
Leaving test suite MultiArrayTestSuite

Entering test suite MultiArrayDataTestSuite
All (32) tests passed in test suite MultiArrayDataTestSuite
Leaving test suite MultiArrayDataTestSuite

Entering test suite ImageViewTestSuite
All (16) tests passed in test suite ImageViewTestSuite
Leaving test suite ImageViewTestSuite

Entering test suite MultiArrayPointOperatorsTestSuite

Failure in MultiArrayPointoperatorsTest::testCombine2()
Unexpected signal: memory access violation

Fatal error - aborting test suite MultiArrayPointOperatorsTestSuite.

test/multiarray/CMakeFiles/test_multiarray.dir/build.make:146: recipe for 
target 'test/multiarray/test_multiarray' failed
make[5]: *** [test/multiarray/test_multiarray] Error 1


DS

[1] 
https://buildd.debian.org/status/fetch.php?pkg=libvigraimpex=mips64el=1.10.0%2Bgit20160211.167be93%2Bdfsg-4=1502638529=0

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

Kernel: Linux 4.11.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: libvigraimpex
Source-Version: 1.10.0+git20160211.167be93+dfsg-5

We believe that the bug you reported is fixed in the latest version of
libvigraimpex, 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 

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

[Andreas Beckmann]

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