Bug#873160: python-pymad: pymad in stretch decodes to noise

[Marc Dahn]

Package: python-pymad
Version: 0.10-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

When decoding at least several MP3 files (including at 22050 kHz
single-channel and 44100 kHz dual-channel, non-VBR), python-pymad in
stretch generates fairly horrific sound (chr-chr-chr) at least on i386.
If one looks at the decoded bytes, there's a clear overabundance of
zeroes, but in the one case I looked at they even included a string .
"7/email/encoders.py", so it's probably not just an integer format
issue.

The good news is:  The version currently in testing, 0.10-1, fixes
the problem, so it's probably not worth further investigating this
particular issue.  It *would* be good if the fix could somehow slip
into stable, though.


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

Kernel: Linux 4.12.2 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=de_DE.ISO-8859-1 (charmap=ISO-8859-1), LANGUAGE=C 
(charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages python-pymad depends on:
ii  libc62.24-11+deb9u1
ii  libmad0  0.15.1b-8
ii  python   2.7.13-2

python-pymad recommends no packages.

python-pymad suggests no packages.

-- no debconf information

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 873153 src:openjdk-9
Bug #873153 [openjdk-9-jre] dependency problems - leaving unconfigured
Bug reassigned from package 'openjdk-9-jre' to 'src:openjdk-9'.
No longer marked as found in versions openjdk-9/9~b181-3.
Ignoring request to alter fixed versions of bug #873153 to the same values 
previously set
> forcemerge 873104 873153
Bug #873104 {Done: Matthias Klose } [src:openjdk-9] openjdk-9: 
update-alternatives error + fail in updating
Bug #873153 [src:openjdk-9] dependency problems - leaving unconfigured
Severity set to 'serious' from 'grave'
Marked Bug as done
Marked as fixed in versions openjdk-9/9~b181-4.
Marked as found in versions openjdk-9/9~b181-3.
Merged 873104 873153
> affects 873104 openjdk-9-jre openjdk-9-jre-headless
Bug #873104 {Done: Matthias Klose } [src:openjdk-9] openjdk-9: 
update-alternatives error + fail in updating
Bug #873153 {Done: Matthias Klose } [src:openjdk-9] dependency 
problems - leaving unconfigured
Added indication that 873104 affects openjdk-9-jre and openjdk-9-jre-headless
Added indication that 873153 affects openjdk-9-jre and openjdk-9-jre-headless
> thanks
Stopping processing here.

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

Processed: found 873153 in 9~b181-3, severity of 873153 is grave

[Debian Bug Tracking System]

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

> found 873153 9~b181-3
Bug #873153 [openjdk-9-jre] dependency problems - leaving unconfigured
Marked as found in versions openjdk-9/9~b181-3.
> severity 873153 grave
Bug #873153 [openjdk-9-jre] dependency problems - leaving unconfigured
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

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

Processed: tagging 870729

[Debian Bug Tracking System]

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

> tags 870729 + pending
Bug #870729 [src:libgnomeui] libgnomeui: Fix FTBFS with glib 2.53.4
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#870729: NMU for the FTBFS

[Adam Borowski]

Hi!
I see you guys don't exactly give any damn about libgnomeui.  I don't do so
either, but:
* there's still a lot of packages depending on it
* I was the last NMUer and I dislike RC bugs on my QA pages

Thus, here's a NMU with Adrian Bunk's patch, debdiff attached.  I'm
uploading to DELAYED/7 right away for fire-and-forget goodness.  As usually,
dcut or holler if anything is wrong.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢰⠒⠀⣿⡁ Vat kind uf sufficiently advanced technology iz dis!?
⢿⡄⠘⠷⠚⠋⠀ -- Genghis Ht'rok'din
⠈⠳⣄ 
diff -Nru libgnomeui-2.24.5/debian/changelog libgnomeui-2.24.5/debian/changelog
--- libgnomeui-2.24.5/debian/changelog  2016-01-14 07:19:42.0 +0100
+++ libgnomeui-2.24.5/debian/changelog  2017-08-25 03:25:24.0 +0200
@@ -1,3 +1,10 @@
+libgnomeui (2.24.5-3.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with glib 2.54 (Adrian Bunk). Closes: #870729.
+
+ -- Adam Borowski   Fri, 25 Aug 2017 03:25:24 +0200
+
 libgnomeui (2.24.5-3.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru libgnomeui-2.24.5/debian/patches/03_glib-2.54-ftbfs.patch 
libgnomeui-2.24.5/debian/patches/03_glib-2.54-ftbfs.patch
--- libgnomeui-2.24.5/debian/patches/03_glib-2.54-ftbfs.patch   1970-01-01 
01:00:00.0 +0100
+++ libgnomeui-2.24.5/debian/patches/03_glib-2.54-ftbfs.patch   2017-08-25 
03:24:24.0 +0200
@@ -0,0 +1,16 @@
+Description: Fix FTBFS with glib 2.54
+ glib-mkenums now expects input files to be UTF-8,
+ fix the encoding of libgnomeui/gnome-scores.h
+Author: Adrian Bunk 
+
+--- libgnomeui-2.24.5.orig/libgnomeui/gnome-scores.h
 libgnomeui-2.24.5/libgnomeui/gnome-scores.h
+@@ -27,7 +27,7 @@
+  * "High Scores" Widget 
+  *
+  * AUTHOR: 
+- * Horacio J. Pe�a 
++ * Horacio J. Peña 
+  *
+  * This is free software (under the terms of the GNU LGPL)
+  *
diff -Nru libgnomeui-2.24.5/debian/patches/series 
libgnomeui-2.24.5/debian/patches/series
--- libgnomeui-2.24.5/debian/patches/series 2016-01-14 07:20:34.0 
+0100
+++ libgnomeui-2.24.5/debian/patches/series 2017-08-25 03:24:24.0 
+0200
@@ -1,2 +1,3 @@
 01_link_libm.patch
 02_time_t_printfs.patch
+03_glib-2.54-ftbfs.patch

Bug#871572: urweb FTBFS with gcc 7 on arm64 and mips64el: test failure

[Benjamin Barenblat]

On Mon, Aug 21, 2017 at 10:02 AM, Benjamin Barenblat  wrote:
> I did an arm64 build with -O1 (i.e., I put
>
> export DEB_CFLAGS_MAINT_APPEND := -O1
>
> in debian/rules), and everything worked fine […]. I’m doing a mips64el
> build with -O1 right now to see if that fixes the issue on mipsel64. If
> it does, I’ll start binary-searching the individual -O2 optimization
> flags to see exactly what’s triggering this.

-O1 built fine on mipsel64. One binary search later, and I’ve determined
that the problematic optimization on both platforms is
-fcode-hoisting. This is a new optimization pass in GCC 7 which “tries
to move the evaluation of expressions executed on all paths to the
function exit as early as possible.”¹

While this doesn’t eliminate either a bug in MLton or in GCC, it does
provide a workaround for this package, namely

export DEB_CFLAGS_MAINT_APPEND := -fno-code-hoisting

However, the correct solution is still to fix whatever compiler is
miscompiling here. I’m going to do a bit more digging to see if I can
figure out whether it’s MLton or GCC.


¹https://gcc.gnu.org/onlinedocs/gcc-7.2.0/gcc/Optimize-Options.html#index-fcode-hoisting

Bug#872884: marked as done (virglrenderer: CVE-2017-6386)

[Debian Bug Tracking System]

Your message dated Fri, 25 Aug 2017 01:34:08 +
with message-id 
and subject line Bug#872884: fixed in virglrenderer 0.6.0-2
has caused the Debian Bug report #872884,
regarding virglrenderer: CVE-2017-6386
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.)


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

Please see:
https://security-tracker.debian.org/tracker/CVE-2017-5956
https://security-tracker.debian.org/tracker/CVE-2017-5957
https://security-tracker.debian.org/tracker/CVE-2017-5993
https://security-tracker.debian.org/tracker/CVE-2017-5994
https://security-tracker.debian.org/tracker/CVE-2017-6209
https://security-tracker.debian.org/tracker/CVE-2017-6210
https://security-tracker.debian.org/tracker/CVE-2017-6317
https://security-tracker.debian.org/tracker/CVE-2017-6355
https://security-tracker.debian.org/tracker/CVE-2017-6386

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: virglrenderer
Source-Version: 0.6.0-2

We believe that the bug you reported is fixed in the latest version of
virglrenderer, 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.
Adam Borowski  (supplier of updated virglrenderer 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: Fri, 25 Aug 2017 03:12:15 +0200
Source: virglrenderer
Binary: libvirglrenderer0 libvirglrenderer-dev
Architecture: source
Version: 0.6.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adam Borowski 
Description:
 libvirglrenderer-dev - virtual GPU for KVM virtualization - headers
 libvirglrenderer0 - virtual GPU for KVM virtualization
Closes: 872884
Changes:
 virglrenderer (0.6.0-2) unstable; urgency=medium
 .
   * QA upload.
   * Apply upstream fix for CVE-2017-6386 (guest exhausting host memory).
 Closes: #872884
Checksums-Sha1:
 124e65311dea262489d86e3b3b1020d2c6773dcd 1724 virglrenderer_0.6.0-2.dsc
 111cb87b384d5cd81e9496c11ba11c20dc686771 4512 
virglrenderer_0.6.0-2.debian.tar.xz
 5ffa6150a5671d27744ef7d655e31a604d3fe8a7 5726 
virglrenderer_0.6.0-2_source.buildinfo
Checksums-Sha256:
 a48fce688d9f71430f56c0a240a4e29a4ec4835257a41e716d3ae9b7924d93da 1724 
virglrenderer_0.6.0-2.dsc
 4a4236eb8a556184d5b3d1fccdbf42361aa009478743a301b521ee3ff9547d17 4512 
virglrenderer_0.6.0-2.debian.tar.xz
 7d764660cb2a1ce0e6f7dfdca09205230590036e22f6b8085afb71efbd0b4623 5726 
virglrenderer_0.6.0-2_source.buildinfo
Files:
 c81261c0ecc72e12af70574558f992f4 1724 libs extra virglrenderer_0.6.0-2.dsc
 65e7c88a18d43944f4e3b6953d190cb5 4512 libs extra 
virglrenderer_0.6.0-2.debian.tar.xz
 ba82816beadd2b3909eed6ad48be9ffb 5726 libs extra 
virglrenderer_0.6.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEE/Zzi2Nd1S3irJ5u9LDtDb+rGgQEFAlmfeo4ACgkQLDtDb+rG
gQFk3gf/XKGybXgT26t+TU5KybQBLgO0p140ZkehzjHtyLCgVoAb+K89VXl3CtSO
uwpkOYsgKVuIuBo1z1IshZjGPBrvTmJ9p40rUR61hWzXUsaww6WJa83j8mrzMiNy
99JdA5i2mr+laHSzpYDtFTsNdU+epR8lC7aYXpQDsM+nEV1LE347tblamvEj3iKu
2P8TRtv0rS/v9qMcKahb3ZV8h1Wc2DnIVQqV/b+A+Q19blypsPihS5YSksnMHY0J
uLOZAL75keVIi1Rw53VQnaKyqkeot4svnOIUu2UPRS1+rxD0JgIfjq+c8FTTIXza
MY0ycAkum27hVDrOqeyaparHgjJEsA==
=3MIr
-END PGP SIGNATURE End Message ---

Bug#853319: marked as done (aspectc++: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Fri, 25 Aug 2017 01:04:12 +
with message-id 
and subject line Bug#853319: fixed in aspectc++ 1:2.2+git20170823-1
has caused the Debian Bug report #853319,
regarding aspectc++: 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.)


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

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]
weave.mk:72: recipe for target 
'/build/aspectc++-4uXFHS/aspectc++-2.1/Puma/gen-release/step2/src/CProject.cc' 
failed
make[3]: *** 
[/build/aspectc++-4uXFHS/aspectc++-2.1/Puma/gen-release/step2/src/CProject.cc] 
Error 1
weave.mk:72: recipe for target 
'/build/aspectc++-4uXFHS/aspectc++-2.1/Puma/gen-release/step2/src/CSemDeclSpecs.cc'
 failed
make[3]: *** 
[/build/aspectc++-4uXFHS/aspectc++-2.1/Puma/gen-release/step2/src/CSemDeclSpecs.cc]
 Error 1
weave.mk:72: recipe for target 
'/build/aspectc++-4uXFHS/aspectc++-2.1/Puma/gen-release/step2/src/CCNameLookup.cc'
 failed
make[3]: *** 
[/build/aspectc++-4uXFHS/aspectc++-2.1/Puma/gen-release/step2/src/CCNameLookup.cc]
 Error 1
weave.mk:72: recipe for target 
'/build/aspectc++-4uXFHS/aspectc++-2.1/Puma/gen-release/step2/src/Parser.cc' 
failed
make[3]: *** 
[/build/aspectc++-4uXFHS/aspectc++-2.1/Puma/gen-release/step2/src/Parser.cc] 
Error 1
weave.mk:72: recipe for target 
'/build/aspectc++-4uXFHS/aspectc++-2.1/Puma/gen-release/step2/src/CCBuilder.cc' 
failed
make[3]: *** 
[/build/aspectc++-4uXFHS/aspectc++-2.1/Puma/gen-release/step2/src/CCBuilder.cc] 
Error 1
weave.mk:72: recipe for target 
'/build/aspectc++-4uXFHS/aspectc++-2.1/Puma/gen-release/step2/src/PreFileIncluder.cc'
 failed
make[3]: *** 
[/build/aspectc++-4uXFHS/aspectc++-2.1/Puma/gen-release/step2/src/PreFileIncluder.cc]
 Error 1
weave.mk:72: recipe for target 
'/build/aspectc++-4uXFHS/aspectc++-2.1/Puma/gen-release/step2/src/InstantiationParser.cc'
 failed
make[3]: *** 
[/build/aspectc++-4uXFHS/aspectc++-2.1/Puma/gen-release/step2/src/InstantiationParser.cc]
 Error 1
weave.mk:72: recipe for target 
'/build/aspectc++-4uXFHS/aspectc++-2.1/Puma/gen-release/step2/src/CTree.cc' 
failed
make[3]: *** 
[/build/aspectc++-4uXFHS/aspectc++-2.1/Puma/gen-release/step2/src/CTree.cc] 
Error 1
weave.mk:72: recipe for target 
'/build/aspectc++-4uXFHS/aspectc++-2.1/Puma/gen-release/step2/src/CFunctionInfo.cc'
 failed
make[3]: *** 
[/build/aspectc++-4uXFHS/aspectc++-2.1/Puma/gen-release/step2/src/CFunctionInfo.cc]
 Error 1
weave.mk:72: recipe for target 
'/build/aspectc++-4uXFHS/aspectc++-2.1/Puma/gen-release/step2/src/CSyntax.cc' 
failed
make[3]: *** 
[/build/aspectc++-4uXFHS/aspectc++-2.1/Puma/gen-release/step2/src/CSyntax.cc] 
Error 1
weave.mk:72: recipe for target 
'/build/aspectc++-4uXFHS/aspectc++-2.1/Puma/gen-release/step2/src/PreprocessorParser.cc'
 failed
make[3]: *** 
[/build/aspectc++-4uXFHS/aspectc++-2.1/Puma/gen-release/step2/src/PreprocessorParser.cc]
 Error 1
weave.mk:72: recipe for target 
'/build/aspectc++-4uXFHS/aspectc++-2.1/Puma/gen-release/step2/src/CSemVisitor.cc'
 failed
make[3]: *** 
[/build/aspectc++-4uXFHS/aspectc++-2.1/Puma/gen-release/step2/src/CSemVisitor.cc]
 Error 1
weave.mk:72: recipe for target 
'/build/aspectc++-4uXFHS/aspectc++-2.1/Puma/gen-release/step2/src/CCSyntax.cc' 
failed
make[3]: *** 

Bug#873152: utopia-documents: Fails to build with qt5.9

[Steve Langasek]

Package: utopia-documents
Version: 3.0.2-1
Severity: serious
Tags: patch
Justification: FTBFS
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu artful ubuntu-patch

Hi James,

In Ubuntu, we've found that utopia-documents fails to build against Qt5.9
with the following error:

[ 16%] Generating moc_bubble.cpp
cd /<>/utopia-build/libutopia2_qt/utopia2/qt && 
/usr/lib/x86_64-linux-gnu/qt5/bin/moc 
@/<>/utopia-build/libutopia2_qt/utopia2/qt/moc_bubble.cpp_parameters
/<>/libutopia2_qt/utopia2/qt/bubble.h:56: Error: Namespace 
declaration lacks Q_NAMESPACE macro.
libutopia2_qt/utopia2/qt/CMakeFiles/utopia2_qt_autogen.dir/build.make:80: 
recipe for target 'libutopia2_qt/utopia2/qt/moc_bubble.cpp' failed

Full build logs can be found at 
https://launchpad.net/ubuntu/+source/utopia-documents/3.0.2-1

Since the Qt stack is nearly identical between artful and Debian unstable, I
believe (but have not tested) that this build failure applies to Debian as
well.

I have attached the attached patch to fix the build failure in Ubuntu.

Thanks,
-- 
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 utopia-documents-3.0.2/debian/patches/fix-namespace-declaration.patch 
utopia-documents-3.0.2/debian/patches/fix-namespace-declaration.patch
--- utopia-documents-3.0.2/debian/patches/fix-namespace-declaration.patch   
1969-12-31 16:00:00.0 -0800
+++ utopia-documents-3.0.2/debian/patches/fix-namespace-declaration.patch   
2017-08-24 17:05:58.0 -0700
@@ -0,0 +1,17 @@
+Description: add required Q_NAMESPACE macro to namespace
+ Qt 5.9 doesn't like namespaces without Q_NAMESPACE macro.
+Author: Steve Langasek 
+Bug-Ubuntu: https://bugs.launchpad.net/bugs/1710317
+
+Index: utopia-documents-3.0.2/libutopia2_qt/utopia2/qt/bubble.h
+===
+--- utopia-documents-3.0.2.orig/libutopia2_qt/utopia2/qt/bubble.h
 utopia-documents-3.0.2/libutopia2_qt/utopia2/qt/bubble.h
+@@ -55,6 +55,7 @@
+ 
+ namespace Utopia
+ {
++Q_NAMESPACE
+ 
+ typedef enum
+ {
diff -Nru utopia-documents-3.0.2/debian/patches/series 
utopia-documents-3.0.2/debian/patches/series
--- utopia-documents-3.0.2/debian/patches/series2017-04-10 
05:13:10.0 -0700
+++ utopia-documents-3.0.2/debian/patches/series2017-08-24 
16:58:24.0 -0700
@@ -1 +1,2 @@
 remove-utopia-update-check.diff
+fix-namespace-declaration.patch

Processed: affects 871514

[Debian Bug Tracking System]

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

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

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

Processed: affects 871514

[Debian Bug Tracking System]

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

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

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

Bug#872604: marked as done (csmith FTBFS on s390x: platform.cpp:82: Error: Unrecognized opcode: `stckf')

[Debian Bug Tracking System]

Your message dated Fri, 25 Aug 2017 00:19:02 +
with message-id 
and subject line Bug#872604: fixed in csmith 2.3.0-2
has caused the Debian Bug report #872604,
regarding csmith FTBFS on s390x: platform.cpp:82: Error: Unrecognized opcode: 
`stckf'
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=csmith=s390x=2.3.0-1=1503091499=0

...
g++ -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o platform.o platform.cpp
platform.cpp: Assembler messages:
platform.cpp:82: Error: Unrecognized opcode: `stckf'
Makefile:717: recipe for target 'platform.o' failed
make[3]: *** [platform.o] Error 1
--- End Message ---
--- Begin Message ---
Source: csmith
Source-Version: 2.3.0-2

We believe that the bug you reported is fixed in the latest version of
csmith, 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.
Nobuhiro Iwamatsu  (supplier of updated csmith 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: Fri, 25 Aug 2017 08:41:23 +0900
Source: csmith
Binary: csmith libcsmith0 libcsmith-dev libcsmith0-dbg
Architecture: source amd64
Version: 2.3.0-2
Distribution: unstable
Urgency: medium
Maintainer: Nobuhiro Iwamatsu 
Changed-By: Nobuhiro Iwamatsu 
Description:
 csmith - generator of random C programs
 libcsmith-dev - generator of random C programs (development files)
 libcsmith0 - generator of random C programs (runtime library)
 libcsmith0-dbg - generator of random C programs (debugging symbols)
Closes: 872604
Changes:
 csmith (2.3.0-2) unstable; urgency=medium
 .
   * Fix FTBFS on s390. (Closes: #872604)
 Add patches/fix_build_s390x.patch.
Checksums-Sha1:
 9eb91a2d1488bea2136560f92faecf7cbe4cceac 2000 csmith_2.3.0-2.dsc
 2f00a6cb6beedcc0a2cb77d813304bb958e1826b 3788 csmith_2.3.0-2.debian.tar.xz
 7ae53e1ff1548b4d6f3771cf0865d111ee71318f 6109 csmith_2.3.0-2_amd64.buildinfo
 3dca7221200e3efb5953116891b69f5d33ce8b15 319668 csmith_2.3.0-2_amd64.deb
 99a75101a4a16bb611b3302526f32f7a2a43d65e 16580 libcsmith-dev_2.3.0-2_amd64.deb
 37707a996985266a7c30883f6357600f219286df 6238044 
libcsmith0-dbg_2.3.0-2_amd64.deb
 92552badb721a582658b8ceeb793a04520f57a32 7610 libcsmith0_2.3.0-2_amd64.deb
Checksums-Sha256:
 d5735b1661aab37125f304577af5c456b3e2f53cccdb5a60aa6b6afeb4919ea1 2000 
csmith_2.3.0-2.dsc
 68ff629011e9ad2ec22be676e0b7b228cdf46026249307945539e86dfcedba79 3788 
csmith_2.3.0-2.debian.tar.xz
 e2ea4253b2db75dcdc2b1690475939eeb613c158442601104631426310eee20d 6109 
csmith_2.3.0-2_amd64.buildinfo
 742f135a152a40bd494811434bd42feeb1e5089a3121f85cf4c749f2c73e2104 319668 
csmith_2.3.0-2_amd64.deb
 e88ae80cbd9b1bd9010a1b03cadd78de4a4364eb8171dbf277819a45c49c4639 16580 
libcsmith-dev_2.3.0-2_amd64.deb
 595267974cbca7816977699295e903f7d7e2a4cdf030b914d35013a83fb50ede 6238044 
libcsmith0-dbg_2.3.0-2_amd64.deb
 4f9812cc02b4ed980f141247ad083a592a5dd3e1e762a5faebed6bee93e2d6d0 7610 
libcsmith0_2.3.0-2_amd64.deb
Files:
 9c3a9e832ce64c3dd8e1a185b1a21d31 2000 devel optional csmith_2.3.0-2.dsc
 bae657e50d95a031f4c915918e64a19e 3788 devel optional 
csmith_2.3.0-2.debian.tar.xz
 0e42ba93f52f427b83c8ae89ed863049 6109 devel optional 
csmith_2.3.0-2_amd64.buildinfo
 a75e25b1cb53dbc1bfe884f7a3a2bbd6 319668 devel optional csmith_2.3.0-2_amd64.deb
 f62a85a97d379342581be9eed8d9b212 16580 libdevel optional 
libcsmith-dev_2.3.0-2_amd64.deb
 d0cb3b7adb1485b0e2801089ab2e5c43 6238044 debug extra 
libcsmith0-dbg_2.3.0-2_amd64.deb
 ce9f5a38bcee0965c99bfa3841954cc3 7610 libs optional 
libcsmith0_2.3.0-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXmKe5SMhlzV7hM9DMiR/u0CtH6YFAlmfaF4ACgkQMiR/u0Ct
H6Yl9Q/+NH4c6OzPoep+ExSvJTuaYqVwzblUAdUZK2A/P2veX73bfdyLHuhrQg/A

Bug#871030: marked as done (mosh FTBFS with gcc 7)

[Debian Bug Tracking System]

Your message dated Fri, 25 Aug 2017 00:19:12 +
with message-id 
and subject line Bug#871030: fixed in mosh 1.3.2-2
has caused the Debian Bug report #871030,
regarding mosh 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.)


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

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

...
In file included from terminalframebuffer.cc:37:0:
terminalframebuffer.h: In constructor 'Terminal::Row::Row()':
terminalframebuffer.h:87:9: error: '.Terminal::Cell::renditions' may 
be used uninitialized in this function [-Werror=maybe-uninitialized]
   class Cell {
 ^~~~
terminalframebuffer.h:87:9: error: '.Terminal::Cell::wide' may be 
used uninitialized in this function [-Werror=maybe-uninitialized]
terminalframebuffer.h:87:9: error: '.Terminal::Cell::fallback' may 
be used uninitialized in this function [-Werror=maybe-uninitialized]
terminalframebuffer.h:87:9: error: '.Terminal::Cell::wrap' may be 
used uninitialized in this function [-Werror=maybe-uninitialized]
cc1plus: all warnings being treated as errors
Makefile:373: recipe for target 'terminalframebuffer.o' failed
make[4]: *** [terminalframebuffer.o] Error 1
--- End Message ---
--- Begin Message ---
Source: mosh
Source-Version: 1.3.2-2

We believe that the bug you reported is fixed in the latest version of
mosh, 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.
Keith Winstein  (supplier of updated mosh package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 24 Aug 2017 15:04:25 -0700
Source: mosh
Binary: mosh
Architecture: source
Version: 1.3.2-2
Distribution: unstable
Urgency: medium
Maintainer: Keith Winstein 
Changed-By: Keith Winstein 
Description:
 mosh   - Mobile shell that supports roaming and intelligent local echo
Closes: 871030
Changes:
 mosh (1.3.2-2) unstable; urgency=medium
 .
   * Fix "mosh FTBFS with gcc 7" 
 (Closes: #871030)
Checksums-Sha1:
 f97e8319d5ee7aa620bbce8bfaf0cde0b5f1e899 1920 mosh_1.3.2-2.dsc
 23124ad19a88f5bb9b7a50e9fcf29d267d6c2296 12224 mosh_1.3.2-2.debian.tar.xz
Checksums-Sha256:
 a3fd2009fbf57fe7fbf6d29763cebed6b8ebfbf58d230409491e88e90665cd90 1920 
mosh_1.3.2-2.dsc
 4de2501208081beec7fd33c2be3c250099311c8f33eb5eacfebe898325c7682a 12224 
mosh_1.3.2-2.debian.tar.xz
Files:
 831010ceceb59abfea9943f99e847f3c 1920 net optional mosh_1.3.2-2.dsc
 413d9a37aa0e769fbd7908d4002abced 12224 net optional mosh_1.3.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIsBAEBCAAWBQJZn2jlDxxrZWl0aHdAbWl0LmVkdQAKCRAgtyg6/iVMaQZAD/9l
j3sbsMJ84gNKNtm88iptqOrD7N0wcSoc8aY4tXo0glPgbtdab8fDuNf2hRq9LP10
iWxuJ4zEFvrfL2+IiSA5M9tUY162FLC+3mnZUj+JLLag8OaG8dD9O1IfRXxOo1LW
bMFrupDYidxxZ2WCLBb734uXlca2F7WxhuF66t82ZiiOTowzfk9tRiAdVgOHisAM
QX4+WFiHMoH3GmBtL3d9TqtF2V7WBE4EEHI+UA/FAAYS/9syxBxwb+zjjPuE8xej
/SNXPlaIz+3Yn2jyFaell0AAhxwWgUl5KByWxCTlICXehYxBJgoOi5NRjSjNb0tz
vk9KpKogZ0sIQxZ+jLx7bz19K9dVjjx5iFyPLnaqj3iyZ7tbcTDzUlrgeIkE2EjF
76WXb2oRCEnUf0e/HjQxAEn3ZlCOytMNep5Mq2oNtiLTJwKTDE/g7Ay0ODJRrEWk
8ty4aBmCK0T+ipLdayzE6pOUMW2VvpaZM8vKXJh6407LEy5flOppMetbZO9xe4lf
Yx6g2tNjvTv6FpeoquHIHRe86lSjLtvS0stUqISxYCFEdQ1dLIONKrBCKC43Wc9w
NhZja8nmo2OWpVYPtiqyfLTPHpj7ky2H1wL+Z763cD1mv4QI7dvLstiNnWyejz90
FofkyDB+7vcwmlxCWJ3tZDgnyCxovLSZRIvRkILEOQ==
=iavz
-END PGP SIGNATURE End Message ---

Processed: tagging 870099

[Debian Bug Tracking System]

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

> tags 870099 + buster sid
Bug #870099 {Done: David Bremner } [latexdiff] latexdiff: 
Since some Perl update, latexdiff doesnt't even start
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Bug#872878: marked as done (sagenb-export: FTBFS when python3.5 is removed)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2017 23:49:34 +
with message-id 
and subject line Bug#872878: fixed in sagenb-export 3.2-3
has caused the Debian Bug report #872878,
regarding sagenb-export: FTBFS when python3.5 is 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.)


-- 
872878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872878
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sagenb-export
Version: 3.2-2
Severity: serious
Tags: patch
Justification: FTBFS
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu artful ubuntu-patch

Dear Ximin,

The sagenb-export package now fails to build in Ubuntu, because python3.5
has been removed from artful - python3-all now depends only on python3.6 -
but debian/rules tries to run tox against python3.5.

I've uploaded the attached patch to Ubuntu to correct this, by running tox
only for the default python and python3 versions.

A more complete fix might iterate over 'py3versions -s' and run tox for
each, but that would require some dynamic mangling of tox.ini; so I think
just testing against the current default should be sufficient for now.

Since the python3.6 transition has begun in Debian and python3.5 will
therefore be dropped from unstable fairly soon, I'm marking this bug as
serious; but you can downgrade it in the short term if necessary,
understanding that it will become serious again.

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru sagenb-export-3.2/debian/patches/python-versions-in-tox 
sagenb-export-3.2/debian/patches/python-versions-in-tox
--- sagenb-export-3.2/debian/patches/python-versions-in-tox 1969-12-31 
16:00:00.0 -0800
+++ sagenb-export-3.2/debian/patches/python-versions-in-tox 2017-08-21 
17:34:22.0 -0700
@@ -0,0 +1,30 @@
+Description: test against the current python versions, not hard-coded ones
+ Upstream test suite is testing against python2.7 and python3.5 at
+ build-time.  Fix this to test against 'python' and 'python3' to use
+ whatever the current Debian default is for this release, instead of
+ hard-coding a specific version number.
+Author: Steve Langasek 
+
+Index: sagenb-export-3.2/tox.ini
+===
+--- sagenb-export-3.2.orig/tox.ini
 sagenb-export-3.2/tox.ini
+@@ -1,12 +1,12 @@
+ [tox]
+-envlist = py27, py34
++envlist = python, python3
+ 
+-[testenv:py27]
+-commands=python2.7 -m unittest discover
++[testenv:python]
++commands=python -m unittest discover
+ 
+-[testenv:py34]
++[testenv:py3.4]
+ commands=python3.4 -m unittest discover
+ 
+-[testenv:py35]
+-commands=python3.5 -m unittest discover
++[testenv:python3]
++commands=python3 -m unittest discover
+ 
diff -Nru sagenb-export-3.2/debian/patches/series 
sagenb-export-3.2/debian/patches/series
--- sagenb-export-3.2/debian/patches/series 1969-12-31 16:00:00.0 
-0800
+++ sagenb-export-3.2/debian/patches/series 2017-08-21 17:32:40.0 
-0700
@@ -0,0 +1 @@
+python-versions-in-tox
diff -Nru sagenb-export-3.2/debian/rules sagenb-export-3.2/debian/rules
--- sagenb-export-3.2/debian/rules  2017-08-16 12:39:30.0 -0700
+++ sagenb-export-3.2/debian/rules  2017-08-21 17:34:29.0 -0700
@@ -16,7 +16,7 @@
 #  PYTHONPATH=. http_proxy='127.0.0.1:9' sphinx-build -N -bhtml
docs/ build/html # HTML generator
 #  PYTHONPATH=. http_proxy='127.0.0.1:9' sphinx-build -N -bman
docs/ build/man # Manpage generator
 
-TOX_ENVLIST = py27,py35
+TOX_ENVLIST = python,python3
 
 override_dh_auto_test:
 ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
--- End Message ---
--- Begin Message ---
Source: sagenb-export
Source-Version: 3.2-3

We believe that the bug you reported is fixed in the latest version of
sagenb-export, 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.
Ximin Luo  (supplier of updated sagenb-export package)

(This message was 

Bug#869006: marked as done (jnr-unixsocket: FTBFS: Failed to execute goal org.apache.maven.plugins:maven-jar-plugin:3.0.2:jar (default) on project jnr-unixsocket: You have to use a classifier to attac

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2017 23:24:39 +
with message-id 
and subject line Bug#869006: fixed in jnr-unixsocket 0.18-3
has caused the Debian Bug report #869006,
regarding jnr-unixsocket: FTBFS: Failed to execute goal 
org.apache.maven.plugins:maven-jar-plugin:3.0.2:jar (default) on project 
jnr-unixsocket: You have to use a classifier to attach supplemental artifacts 
to the project instead of replacing them
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.)


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

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=maven --with javahelper
>dh_testdir -O--buildsystem=maven
>dh_update_autotools_config -O--buildsystem=maven
>dh_autoreconf -O--buildsystem=maven
>dh_auto_configure -O--buildsystem=maven
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
> such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
> No such file or directory
>   mh_patchpoms -plibjnr-unixsocket-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
> Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8
>jh_linkjars -O--buildsystem=maven
>dh_auto_build -O--buildsystem=maven
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
>  -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo package javadoc:jar 
> javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US
> Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8
> [INFO] Scanning for projects...
> [INFO] 
> [INFO] 
> 
> [INFO] Building jnr-unixsocket 0.18
> [INFO] 
> 
> [INFO] 
> [INFO] --- maven-resources-plugin:3.0.0:resources 
> (default-resources) @ jnr-unixsocket ---
> [WARNING] Using platform encoding (UTF-8 actually) to copy filtered 
> resources, i.e. build is platform dependent!
> [INFO] skip non existing resourceDirectory 
> /<>/src/main/resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.6.1:compile 
> (default-compile) @ jnr-unixsocket ---
> [WARNING] The POM for 
> org.codehaus.plexus:plexus-compiler-api:jar:2.x is invalid, transitive 
> dependencies (if any) will not be available, enable debug logging for more 
> details
> [WARNING] The POM for 
> org.codehaus.plexus:plexus-compiler-javac:jar:2.x is invalid, transitive 
> dependencies (if any) will not be available, enable debug logging for more 
> details
> [INFO] Changes detected - recompiling the module!
> [WARNING] File encoding has not been set, using platform encoding 
> UTF-8, i.e. build is platform dependent!
> [INFO] Compiling 17 source files to /<>/target/classes
> [INFO] /<>/src/main/java/jnr/unixsocket/Common.java: 
> /<>/src/main/java/jnr/unixsocket/Common.java uses unchecked or 
> unsafe operations.
> [INFO] /<>/src/main/java/jnr/unixsocket/Common.java: 
> Recompile with -Xlint:unchecked for details.
> [INFO] 
> [INFO] --- maven-bundle-plugin:2.5.4:manifest 
> (bundle-manifest) @ jnr-unixsocket ---
> [INFO] 
> [INFO] --- maven-resources-plugin:3.0.0:testResources 
> (default-testResources) @ jnr-unixsocket ---
> [WARNING] Using platform encoding (UTF-8 actually) to copy filtered 
> resources, i.e. build is platform dependent!
> [INFO] Copying 1 resource
> [INFO] 

Processed: Pending fixes for bugs in the jnr-unixsocket package

[Debian Bug Tracking System]

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

> tag 869006 + pending
Bug #869006 {Done: Miguel Landaeta } [src:jnr-unixsocket] 
jnr-unixsocket: FTBFS: Failed to execute goal 
org.apache.maven.plugins:maven-jar-plugin:3.0.2:jar (default) on project 
jnr-unixsocket: You have to use a classifier to attach supplemental artifacts 
to the project instead of replacing them
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#869006: Pending fixes for bugs in the jnr-unixsocket package

[pkg-java-maintainers]

tag 869006 + pending
thanks

Some bugs in the jnr-unixsocket package are closed in revision
b6e37392bd2d4bd212334360dcd22013a21ca1de in branch 'master' by
Emmanuel Bourg

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/jnr-unixsocket.git/commit/?id=b6e3739

Commit message:

Removed the build dependency on libmaven-assembly-plugin-java (Closes: 
#869006)

Bug#871162: marked as done (carrotsearch-hppc: FTBFS: ERROR Plugin org.codehaus.mojo:build-helper-maven-plugin:1.8 or one of its dependencies could not be resolved: Cannot access central (https://repo

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2017 23:04:16 +
with message-id 
and subject line Bug#871162: fixed in carrotsearch-hppc 0.6.1-4
has caused the Debian Bug report #871162,
regarding carrotsearch-hppc: FTBFS: ERROR Plugin 
org.codehaus.mojo:build-helper-maven-plugin:1.8 or one of its dependencies 
could not be resolved: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.codehaus.mojo:build-helper-maven-plugin:jar:1.8 has not been downloaded 
from it before. -> [Help 1]
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.)


-- 
871162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871162
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: carrotsearch-hppc
Version: 0.6.1-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):
>  debian/rules build
> dh build
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   mh_patchpoms -plibcarrotsearch-hppc-java --debian-build 
> --keep-pom-version --maven-repo=/<>/debian/maven-repo
>dh_auto_build
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
>  -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo package -DskipTests 
> -Dnotimestamp=true -Dlocale=en_US
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO] 
> [INFO] HPPC (parent POM)
> [INFO] HPPC Template Processor
> [INFO] HPPC Collections
> [INFO] 
> [INFO] 
> 
> [INFO] Building HPPC (parent POM) 0.6.1
> [INFO] 
> 
> [INFO] 
> [INFO] 
> 
> [INFO] Building HPPC Template Processor 0.6.1
> [INFO] 
> 
> [INFO] 
> [INFO] --- maven-resources-plugin:3.0.2:resources 
> (default-resources) @ hppc-templateprocessor ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory 
> /<>/hppc-templateprocessor/src/main/resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.6.1:compile 
> (default-compile) @ hppc-templateprocessor ---
> [WARNING] The POM for 
> org.codehaus.plexus:plexus-compiler-api:jar:2.x is invalid, transitive 
> dependencies (if any) will not be available, enable debug logging for more 
> details
> [WARNING] The POM for 
> org.codehaus.plexus:plexus-compiler-javac:jar:2.x is invalid, transitive 
> dependencies (if any) will not be available, enable debug logging for more 
> details
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 5 source files to 
> /<>/hppc-templateprocessor/target/classes
> [INFO] 
> [INFO] --- maven-resources-plugin:3.0.2:testResources 
> (default-testResources) @ hppc-templateprocessor ---
> [INFO] Not copying test resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.6.1:testCompile 
> (default-testCompile) @ hppc-templateprocessor ---
> [INFO] Not compiling test sources
> [INFO] 
> [INFO] --- maven-surefire-plugin:2.19.1:test 
> (default-test) @ hppc-templateprocessor ---
> [INFO] Tests are skipped.
> [INFO] 
> [INFO] --- maven-jar-plugin:3.0.2:jar 
> (default-jar) @ hppc-templateprocessor ---
> 

Processed: Pending fixes for bugs in the carrotsearch-hppc package

[Debian Bug Tracking System]

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

> tag 871162 + pending
Bug #871162 [src:carrotsearch-hppc] carrotsearch-hppc: FTBFS: ERROR Plugin 
org.codehaus.mojo:build-helper-maven-plugin:1.8 or one of its dependencies 
could not be resolved: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.codehaus.mojo:build-helper-maven-plugin:jar:1.8 has not been downloaded 
from it before. -> [Help 1]
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#871162: Pending fixes for bugs in the carrotsearch-hppc package

[pkg-java-maintainers]

tag 871162 + pending
thanks

Some bugs in the carrotsearch-hppc package are closed in revision
0d1117f57f126cbaf3435672ed4725e688b9dedf in branch 'master' by
Emmanuel Bourg

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/carrotsearch-hppc.git/commit/?id=0d1117f

Commit message:

Fixed the build failure caused by the build-helper-maven-plugin upgrade 
(Closes: #871162)

Bug#873148: Fails to properly escape the ;, {, }, <, and > characters

[Bastien ROUCARIES]

Package: node-shell-quote
severity: serious
forwarded: https://github.com/substack/node-shell-quote/issues/31

couple of open issues that seem reasonably
serious for a package that appears to be intended for sanitising user
input before passing it on to the shell:

Bug#873079: unattended-upgrades FTBFS: test failures

[Balint Reczey]

Control: tags -1 confirmed

Hi Adrian,

Thanks for the report.

On Thu, 24 Aug 2017 13:10:16 +0300 Adrian Bunk  wrote:
> Source: unattended-upgrades
> Version: 0.95
> Severity: serious
>
>
https://buildd.debian.org/status/fetch.php?pkg=unattended-upgrades=all=0.95=1503510785=0
>

Interestingly the package built (and builds) fine in my schroot. I
suspect the issue is related to using system's apt config which i'll fix
in the next upload.

Cheers,
Balint

Processed: Re: unattended-upgrades FTBFS: test failures

[Debian Bug Tracking System]

Processing control commands:

> tags -1 confirmed
Bug #873079 [src:unattended-upgrades] unattended-upgrades FTBFS: test failures
Added tag(s) confirmed.

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

Bug#868794: Please check bppphyview

[Andreas Tille]

Hi Julien,

I reassigned this bug to bppphyview.  Unfortunately this error

...
[100%] Linking CXX executable phyview
cd /build/bppphyview-0.5.1/obj-x86_64-linux-gnu/bppPhyView && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/phyview.dir/link.txt --verbose=1
/usr/bin/c++  -std=c++11 -Wall  -Wl,-z,relro -Wl,-z,now -rdynamic 
CMakeFiles/phyview.dir/PhyView.cpp.o CMakeFiles/phyview.dir/TreeSubWindow.cpp.o 
CMakeFiles/phyview.dir/TreeCommands.cpp.o 
CMakeFiles/phyview.dir/moc_PhyView.cxx.o 
CMakeFiles/phyview.dir/moc_TreeSubWindow.cxx.o  -o phyview 
/usr/lib/x86_64-linux-gnu/libbpp-qt.so.1.0.1 
/usr/lib/x86_64-linux-gnu/libQtCore.so /usr/lib/x86_64-linux-gnu/libQtGui.so 
/usr/lib/x86_64-linux-gnu/libbpp-phyl.so.11.0.0 
/usr/lib/x86_64-linux-gnu/libbpp-seq.so.11.0.0 
/usr/lib/x86_64-linux-gnu/libbpp-core.so.3.0.0 
/usr/lib/x86_64-linux-gnu/libQtCore.so 
/usr/lib/x86_64-linux-gnu/libbpp-phyl.so.11.0.0: undefined reference to 
`virtual thunk to bpp::AbstractParameterAliasable::getAliases() const'
collect2: error: ld returned 1 exit status
bppPhyView/CMakeFiles/phyview.dir/build.make:218: recipe for target 
'bppPhyView/phyview' failed
make[3]: *** [bppPhyView/phyview] Error 1
make[3]: Leaving directory '/build/bppphyview-0.5.1/obj-x86_64-linux-gnu'
CMakeFiles/Makefile2:153: recipe for target 
'bppPhyView/CMakeFiles/phyview.dir/all' failed
make[2]: *** [bppPhyView/CMakeFiles/phyview.dir/all] Error 2
make[2]: Leaving directory '/build/bppphyview-0.5.1/obj-x86_64-linux-gnu'
Makefile:154: recipe for target 'all' failed
make[1]: *** [all] Error 2
...

remains even with the gcc-7 rebuilt libs.  Could you have a look?

   Vcs-Git: https://anonscm.debian.org/git/debian-med/bppphyview.git

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#861333: marked as done (r-base: R packages uploaded to Debian before 14 April 2017 that use .C or .Fortran fail to find objects)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2017 21:10:38 +
with message-id 
and subject line Bug#861684: fixed in r-cran-randomfields 3.1.50-1
has caused the Debian Bug report #861684,
regarding r-base: R packages uploaded to Debian before 14 April 2017 that use 
.C or .Fortran fail to find objects
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.)


-- 
861684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861684
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: r-base
Version: 3.4.0-1
Severity: normal

With current R, R packages built for Debian before the upload of R 
3.3.3.20170413-1 
on 14 April that use .C or .Fortran do no work properly, because the functions 
calling .C or .Fortran do not find the compiled objects.

Example packages are r-cran-spatial and r-cran-kernsmooth. 

An example session in a fresh Debian sid chroot:

> library(spatial)
> example(surf.gls)

srf.gl> library(MASS)  # for eqscplot

srf.gl> data(topo, package="MASS")

srf.gl> topo.kr <- surf.gls(2, expcov, topo, d=0.7)
Error in surf.gls(2, expcov, topo, d = 0.7) : object 'VR_frset' not found


The relevant NEWS entry from R is

* Packages which register native routines for .C or .Fortran need
  to be re-installed for this version (unless installed with
  R-devel SVN revision r72375 or later).

Packages compiled locally can simply be rebuilt using

  update.packages(lib.loc="/usr/local/lib/R/site-library", checkBuilt=TRUE)

However the packages provided by Debian packages are installed in a directory
only writable by privileged users.

Cheers,

Johannes

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

Kernel: Linux 4.9.0-0.bpo.2-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages r-base depends on:
ii  r-base-core3.4.0-1
ii  r-recommended  3.4.0-1

Versions of packages r-base recommends:
ii  r-base-html  3.4.0-1
ii  r-doc-html   3.4.0-1

Versions of packages r-base suggests:
pn  ess 
pn  r-doc-info | r-doc-pdf  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: r-cran-randomfields
Source-Version: 3.1.50-1

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated r-cran-randomfields 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 24 Aug 2017 22:24:04 +0200
Source: r-cran-randomfields
Binary: r-cran-randomfields
Architecture: source
Version: 3.1.50-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Andreas Tille 
Description:
 r-cran-randomfields - GNU R simulation and analysis of random fields
Closes: 861684
Changes:
 r-cran-randomfields (3.1.50-1) unstable; urgency=medium
 .
   * New upstream version
 Closes: #861684
   * Standards-Version: 4.1.0 (no changes needed)
Checksums-Sha1:
 fb7b90a32be942fd5a8bf178f7eb8fde2a71f963 2252 r-cran-randomfields_3.1.50-1.dsc
 cb0049236f41cb72dd6a1df9c65a2c7efd2a5328 1783992 
r-cran-randomfields_3.1.50.orig.tar.gz
 0eb64575f967afac94690779071aa2d5d96f1c0a 2760 
r-cran-randomfields_3.1.50-1.debian.tar.xz
 77395838d23b8a798adf0a00a52f92e25680c925 15021 
r-cran-randomfields_3.1.50-1_source.buildinfo
Checksums-Sha256:
 d78a6affc1d32596bccd983ae0368976a576fca4ce6efee7d33f8a5598ff8e63 2252 
r-cran-randomfields_3.1.50-1.dsc
 2d6a07c3a716ce20f9c685deb59e8fcc64fd52c8a50b0f04baf451b6b928e848 1783992 
r-cran-randomfields_3.1.50.orig.tar.gz
 f27c27f734be4deae9a22fee7fb05564afb32a1c342e8091f5e9138075799321 2760 
r-cran-randomfields_3.1.50-1.debian.tar.xz
 10338029b938ce4ec7c8376d343be0c4f90c3cc4cdae160e751a0782a297b035 15021 
r-cran-randomfields_3.1.50-1_source.buildinfo
Files:
 c56b857029efea333159decf4de4841e 

Bug#862969: marked as done (r-cran-sp needs recompilation for R 3.4.0 ?)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2017 21:10:38 +
with message-id 
and subject line Bug#861684: fixed in r-cran-randomfields 3.1.50-1
has caused the Debian Bug report #861684,
regarding r-cran-sp needs recompilation for R 3.4.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.)


-- 
861684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861684
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: r-cran-sp
Version: 1:1.2-4-1

Using latest debian testing, function spDistsN1() of package sp throws an 
error:

> library(sp)
> ll <- matrix(c(5, 6, 60, 60), ncol=2)
> km <- spDistsN1(ll, ll[1,], longlat=TRUE)
Error in .C("sp_dists", x, y, xx, yy, n, dists, lonlat, PACKAGE = "sp") : 
  "sp_dists" not available for .C() for package "sp"

It was working until recently, i.e. before the upgrade from R 3.3 to 3.4. 

If I uninstall the debian package and compile the R source package from CRAN, 
it works. So probably the debian package needs recompilation.
--- End Message ---
--- Begin Message ---
Source: r-cran-randomfields
Source-Version: 3.1.50-1

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated r-cran-randomfields 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 24 Aug 2017 22:24:04 +0200
Source: r-cran-randomfields
Binary: r-cran-randomfields
Architecture: source
Version: 3.1.50-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Andreas Tille 
Description:
 r-cran-randomfields - GNU R simulation and analysis of random fields
Closes: 861684
Changes:
 r-cran-randomfields (3.1.50-1) unstable; urgency=medium
 .
   * New upstream version
 Closes: #861684
   * Standards-Version: 4.1.0 (no changes needed)
Checksums-Sha1:
 fb7b90a32be942fd5a8bf178f7eb8fde2a71f963 2252 r-cran-randomfields_3.1.50-1.dsc
 cb0049236f41cb72dd6a1df9c65a2c7efd2a5328 1783992 
r-cran-randomfields_3.1.50.orig.tar.gz
 0eb64575f967afac94690779071aa2d5d96f1c0a 2760 
r-cran-randomfields_3.1.50-1.debian.tar.xz
 77395838d23b8a798adf0a00a52f92e25680c925 15021 
r-cran-randomfields_3.1.50-1_source.buildinfo
Checksums-Sha256:
 d78a6affc1d32596bccd983ae0368976a576fca4ce6efee7d33f8a5598ff8e63 2252 
r-cran-randomfields_3.1.50-1.dsc
 2d6a07c3a716ce20f9c685deb59e8fcc64fd52c8a50b0f04baf451b6b928e848 1783992 
r-cran-randomfields_3.1.50.orig.tar.gz
 f27c27f734be4deae9a22fee7fb05564afb32a1c342e8091f5e9138075799321 2760 
r-cran-randomfields_3.1.50-1.debian.tar.xz
 10338029b938ce4ec7c8376d343be0c4f90c3cc4cdae160e751a0782a297b035 15021 
r-cran-randomfields_3.1.50-1_source.buildinfo
Files:
 c56b857029efea333159decf4de4841e 2252 gnu-r optional 
r-cran-randomfields_3.1.50-1.dsc
 fd91aea76365427c0ba3b25fb3af43a6 1783992 gnu-r optional 
r-cran-randomfields_3.1.50.orig.tar.gz
 b3d1e4f67315f695fffe8c90a19b4165 2760 gnu-r optional 
r-cran-randomfields_3.1.50-1.debian.tar.xz
 b1cb6ecd2c6976f5efbe00f66eb6ccbb 15021 gnu-r optional 
r-cran-randomfields_3.1.50-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJCBAEBCAAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlmfOQwOHHRpbGxlYUBy
a2kuZGUACgkQV4oElNHGRtG1WQ//QKdZ89621KwebRHvPOI5hrh1SWfzSa6PHSQ6
mThkIgQthQu5PwcgI1ceAUEqejud6ikTelfcAFo7ZJ9omVm3b5Cl78f5bvartqlB
2WbVXI8E9APDQKybDukSmAe+x3oqLrBcZ03tHuU4ZuT44ImuSjzQVdz1FzVGEYPN
cRCklKHKFXu9d2CgK6uivBcA7eDCkeoV8aN1cz/BUGKm216GtjjphU7vn7Vw7T1V
M8I7zDv+ixV0PRypbzZ/LzYJtanpe5at3ydz0D0fy29Fxs1t61KNoKFckvHXbJH1
puViMNAyo98zmD4RYWC0ApJwzKgKlRwsiUThAShUDYMj94He8Bz3gKQjn7EP745V
VdhFAp6CcIPj7uvDoW60p8Ae0APExlMKpIlaufVAe9gFxGJu6ysplWM6jaiYvVSO
DGvD2AvMndm9+b6ISshUG3s6XjF9ISCyDDtIuj0EUF92h2ynqOtMtAObu2SBvTdG
z3v3e3glq7lEkYfImX4l5KbXKMHNjrj7RjTsI5ht1kP2+PoiP/ZPhDre97LbT6Cz
Kdbs0VwT3C2YbiuvOl63cWJN2Jn+vsjr2q3O1axEpu+6A5X4Lhs9Iu7pWjb3Il+M
xITRPq+d7aIJUbwAg1DhawuO5r3hjlK087CvQJwvKnMF6ZblF4O9lp07RBiCTMT3
v2qrq9o=
=OGXf
-END PGP SIGNATURE End 

Bug#861684: marked as done (r-cran-randomfields: FTBFS against r-base 3.4.0-1)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2017 21:10:38 +
with message-id 
and subject line Bug#861684: fixed in r-cran-randomfields 3.1.50-1
has caused the Debian Bug report #861684,
regarding r-cran-randomfields: FTBFS against r-base 3.4.0-1
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.)


-- 
861684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861684
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: r-cran-randomfields
Version: 3.1.36-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

This package FTBFS against r-base 3.4.0-1 which was uploaded to unstable
recently.

[..]
make[1]: Leaving directory '/<>/src'
make[1]: Entering directory '/<>/src'
make[1]: Leaving directory '/<>/src'
installing to 
/<>/debian/r-cran-randomfields/usr/lib/R/site-library/RandomFields/libs
** R
** data
** inst
** preparing package for lazy loading
Error: package or namespace load failed for 'RandomFieldsUtils' in 
dyn.load(file, DLLpath = DLLpath, ...):
 allocation failure in R_setPrimitiveArgTypes
Error : package 'RandomFieldsUtils' could not be loaded
ERROR: lazy loading failed for package 'RandomFields'
* removing 
'/<>/debian/r-cran-randomfields/usr/lib/R/site-library/RandomFields'
dh_auto_install: R CMD INSTALL -l 
/<>/debian/r-cran-randomfields/usr/lib/R/site-library --clean . 
--built-timestamp='Sun, 08 Jan 2017 17:05:46 +0100' returned exit code 1
debian/rules:4: recipe for target 'binary' failed
make: *** [binary] Error 25
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2

Build finished at 2017-05-02T17:28:29Z

Ximin


-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (300, 'unstable'), (200, 'experimental'), (1, 
'experimental-debug')
Architecture: amd64
 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: r-cran-randomfields
Source-Version: 3.1.50-1

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated r-cran-randomfields 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 24 Aug 2017 22:24:04 +0200
Source: r-cran-randomfields
Binary: r-cran-randomfields
Architecture: source
Version: 3.1.50-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Andreas Tille 
Description:
 r-cran-randomfields - GNU R simulation and analysis of random fields
Closes: 861684
Changes:
 r-cran-randomfields (3.1.50-1) unstable; urgency=medium
 .
   * New upstream version
 Closes: #861684
   * Standards-Version: 4.1.0 (no changes needed)
Checksums-Sha1:
 fb7b90a32be942fd5a8bf178f7eb8fde2a71f963 2252 r-cran-randomfields_3.1.50-1.dsc
 cb0049236f41cb72dd6a1df9c65a2c7efd2a5328 1783992 
r-cran-randomfields_3.1.50.orig.tar.gz
 0eb64575f967afac94690779071aa2d5d96f1c0a 2760 
r-cran-randomfields_3.1.50-1.debian.tar.xz
 77395838d23b8a798adf0a00a52f92e25680c925 15021 
r-cran-randomfields_3.1.50-1_source.buildinfo
Checksums-Sha256:
 d78a6affc1d32596bccd983ae0368976a576fca4ce6efee7d33f8a5598ff8e63 2252 
r-cran-randomfields_3.1.50-1.dsc
 2d6a07c3a716ce20f9c685deb59e8fcc64fd52c8a50b0f04baf451b6b928e848 1783992 
r-cran-randomfields_3.1.50.orig.tar.gz
 f27c27f734be4deae9a22fee7fb05564afb32a1c342e8091f5e9138075799321 2760 
r-cran-randomfields_3.1.50-1.debian.tar.xz
 10338029b938ce4ec7c8376d343be0c4f90c3cc4cdae160e751a0782a297b035 15021 
r-cran-randomfields_3.1.50-1_source.buildinfo
Files:
 

Bug#866965: re: dosemu: DPMI unhandled exception instability back again

[eric . 17 . debian]

Hello,after migrating to stretch an old business program crashed, as this 
isessential here I tried various things which might be useful inanalyzing the 
DPMI behavior.some workarounds:current solution here: everything is running 
fine on stretch with thejessie dosemu package without any tweaks!dosemu2 also 
was able to run fine but there was no way back to dosemu1.4, I couldn't sort 
out why, so as I was short in time I reinstalledthe whole systemthe stetch 
dosemu package runs with$_dpmi = (0x)in dosemu.conf which is a strange 
settingon the 386 architecture does not come up with the stack overflow, 
itwas possible to run the software but I prefer amd64 on the machine, sothis 
was just a short test.the relevant part of the bootlog:=== 
ENTER CPU-EMU ===ERROR: PM stack overflowed: 
in_dpmi_pm_stack=452leavedos(enter_lpms|1283) called - shutting downleavedos() 
called from within a signal context!=== LEAVE CPU-EMU 
===hope this is related/eric

Processed: Reassign

[Debian Bug Tracking System]

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

> reassign 868924 bppphyview
Bug #868924 [libbpp-qt-dev] bppphyview: FTBFS: TreeDocument.h:47:27: fatal 
error: Bpp/Phyl/Io.all: No such file or directory
Bug #868794 [libbpp-qt-dev] libbpp-qt-dev: postinst removal makes bppphyview 
FTBFS
Bug #871164 [libbpp-qt-dev] bppphyview: FTBFS: TreeDocument.h:47:10: fatal 
error: Bpp/Phyl/Io.all: No such file or directory
Bug reassigned from package 'libbpp-qt-dev' to 'bppphyview'.
Bug reassigned from package 'libbpp-qt-dev' to 'bppphyview'.
Bug reassigned from package 'libbpp-qt-dev' to 'bppphyview'.
No longer marked as found in versions libbpp-qt/2.3.1-3.
No longer marked as found in versions libbpp-qt/2.3.1-3.
No longer marked as found in versions libbpp-qt/2.3.1-3.
Ignoring request to alter fixed versions of bug #868924 to the same values 
previously set
Ignoring request to alter fixed versions of bug #868794 to the same values 
previously set
Ignoring request to alter fixed versions of bug #871164 to the same values 
previously set
> reassign 868794 bppphyview
Bug #868794 [bppphyview] libbpp-qt-dev: postinst removal makes bppphyview FTBFS
Bug #868924 [bppphyview] bppphyview: FTBFS: TreeDocument.h:47:27: fatal error: 
Bpp/Phyl/Io.all: No such file or directory
Bug #871164 [bppphyview] bppphyview: FTBFS: TreeDocument.h:47:10: fatal error: 
Bpp/Phyl/Io.all: No such file or directory
Ignoring request to reassign bug #868794 to the same package
Ignoring request to reassign bug #868924 to the same package
Ignoring request to reassign bug #871164 to the same package
> reassign 871164 bppphyview
Bug #871164 [bppphyview] bppphyview: FTBFS: TreeDocument.h:47:10: fatal error: 
Bpp/Phyl/Io.all: No such file or directory
Bug #868794 [bppphyview] libbpp-qt-dev: postinst removal makes bppphyview FTBFS
Bug #868924 [bppphyview] bppphyview: FTBFS: TreeDocument.h:47:27: fatal error: 
Bpp/Phyl/Io.all: No such file or directory
Ignoring request to reassign bug #871164 to the same package
Ignoring request to reassign bug #868794 to the same package
Ignoring request to reassign bug #868924 to the same package
> thanks
Stopping processing here.

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

Bug#873145: mercurial-git: hg-git needs to be updated to 0.8.9 to work with mercurial 4.3

[derfel]

Package: mercurial-git
Version: 0.8.5-4
Severity: grave
Justification: renders package unusable

Tags: fixed-upstream, sid

With the new mercurial 4.3 in sid mercurial-git cannot work anymore. A sample
error is:

$ hg status
abort: No module named osutil!

$ hg log
** Unknown exception encountered with possibly-broken third-party extension
hggit
** which supports versions 3.7 of Mercurial.
** Please disable hggit and try your action again.
** If that fixes the bug please report it to https://bitbucket.org/durin42/hg-
git/issues
** Python 2.7.13+ (default, Jul 19 2017, 18:15:03) [GCC 6.4.0 20170704]
** Mercurial Distributed SCM (version 4.3.1)
** Extensions loaded: hggit
Traceback (most recent call last):
  File "/usr/bin/hg", line 45, in 
mercurial.dispatch.run()
  File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 81, in
run
status = (dispatch(req) or 0) & 255
  File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 162, in
dispatch
ret = _runcatch(req)
  File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 302, in
_runcatch
return _callcatch(ui, _runcatchfunc)
  File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 310, in
_callcatch
return scmutil.callcatch(ui, func)
  File "/usr/lib/python2.7/dist-packages/mercurial/scmutil.py", line 150, in
callcatch
return func()
  File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 292, in
_runcatchfunc
return _dispatch(req)
  File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 896, in
_dispatch
cmdpats, cmdoptions)
  File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 658, in
runcommand
ret = _runcommand(ui, options, cmd, d)
  File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 904, in
_runcommand
return cmdfunc()
  File "/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 893, in

d = lambda: util.checksignature(func)(ui, *args, **strcmdopt)
  File "/usr/lib/python2.7/dist-packages/mercurial/util.py", line 1079, in
check
return func(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/mercurial/commands.py", line 3379, in
log
displayer.show(ctx, copies=copies, matchfn=revmatchfn)
  File "/usr/lib/python2.7/dist-packages/mercurial/cmdutil.py", line 1510, in
show
self._show(ctx, copies, matchfn, props)
  File "/usr/lib/python2.7/dist-packages/mercurial/cmdutil.py", line 1553, in
_show
for name in ns.names(self.repo, changenode):
  File "/usr/lib/python2.7/dist-packages/mercurial/namespaces.py", line 195, in
names
return sorted(self.nodemap(repo, node))
  File "/usr/lib/python2.7/dist-packages/mercurial/namespaces.py", line 44, in

tagnodemap = lambda repo, node: repo.nodetags(node)
  File "/usr/lib/python2.7/dist-packages/mercurial/localrepo.py", line 895, in
nodetags
if not self._tagscache.nodetagscache:
  File "/usr/lib/python2.7/dist-packages/mercurial/repoview.py", line 239, in
__getattr__
return getattr(self._unfilteredrepo, attr)
  File "/usr/lib/python2.7/dist-packages/mercurial/util.py", line 823, in
__get__
result = self.func(obj)
  File "/usr/lib/python2.7/dist-packages/mercurial/localrepo.py", line 817, in
_tagscache
cache.tags, cache.tagtypes = self._findtags()
  File "/usr/local/lib/python2.7/dist-
packages/hg_git-0.8.5-py2.7.egg/hggit/hgrepo.py", line 47, in _findtags
for tag, rev in self.githandler.tags.iteritems():
  File "/usr/lib/python2.7/dist-packages/mercurial/util.py", line 823, in
__get__
result = self.func(obj)
  File "/usr/local/lib/python2.7/dist-
packages/hg_git-0.8.5-py2.7.egg/hggit/hgrepo.py", line 66, in githandler
return GitHandler(self, self.ui)
  File "/usr/local/lib/python2.7/dist-
packages/hg_git-0.8.5-py2.7.egg/hggit/git_handler.py", line 110, in __init__
self.gitdir = self.repo.join('git')
AttributeError: 'hgrepo' object has no attribute 'join'

hg log don't work anymore even if the upstream repository is mercurial and not
git. So, basically, you cannot use mercurial anymore if not disabling the
extension in hgrc or updating to the latest version which is already fixed.



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

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

Versions of packages mercurial-git depends on:
ii  mercurial   4.3.1-2
ii  python  2.7.13-2
ii  python-dulwich  0.18.2-1

mercurial-git recommends no packages.

mercurial-git suggests no packages.

Bug#873142: virtualbox-dkms: Installation hangs running depmod...

[Ivan Kohler]

Package: virtualbox-dkms
Version: 5.1.24-dfsg-2
Severity: critical
Justification: breaks the whole system

Installation hangs running "depmod..." and printing a period every few seconds.

ps shows the command being run is:
  depmod -a 4.11.0-1-amd64 -F /boot/System.map-4.11.0-1-amd64

It has been running for over 25 minutes now, but does not appear to be using
any CPU or resources.

Ctrl-C does not stop the installation process.  Sending a kill signal to the
depmod process does not have any effect.

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

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

Versions of packages virtualbox-dkms depends on:
ii  dkms  2.3-3

Versions of packages virtualbox-dkms recommends:
ii  virtualbox  5.1.24-dfsg-2

virtualbox-dkms suggests no packages.

-- no debconf information

Bug#853681: marked as done (theseus: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2017 19:34:55 +
with message-id 
and subject line Bug#853681: fixed in theseus 3.3.0-6
has caused the Debian Bug report #853681,
regarding theseus: 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.)


-- 
853681: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853681
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:theseus
Version: 3.3.0-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/theseus_3.3.0-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

[...]
a - EVD_dist.o
a - exp_dist.o
a - gamma_dist.o
a - invchisqr_dist.o
a - invgamma_dist.o
a - invgauss_dist.o
a - laplace_dist.o
a - logistic_dist.o
a - lognormal_dist.o
a - maxwell_dist.o
a - negbinom_dist.o
a - normal_dist.o
a - pareto_dist.o
a - rayleigh_dist.o
a - recinvgauss_dist.o
a - rice_dist.o
a - uniform_dist.o
a - vonmises_dist.o
a - weibull_dist.o
ranlib libdistfit.a
make[2]: Leaving directory '/<>/libdistfit'
( cd libDLTutils; make && cp libDLTutils.a ../lib  )
make[2]: Entering directory '/<>/libDLTutils'
/usr/bin/gcc -O3 -ffast-math -fstrict-aliasing -funroll-loops 
-fomit-frame-pointer -Wall -Werror -pedantic -std=c99 -Wno-unused-result 
-pthread  -c DLTutils.c
ar -rvs libDLTutils.a DLTutils.o
ar: creating libDLTutils.a
a - DLTutils.o
ranlib libDLTutils.a
make[2]: Leaving directory '/<>/libDLTutils'
( cd libmsa; make && cp libmsa.a ../lib  )
make[2]: Entering directory '/<>/libmsa'
/usr/bin/gcc -O3 -ffast-math -fstrict-aliasing -funroll-loops 
-fomit-frame-pointer -Wall -Werror -pedantic -std=c99 -Wno-unused-result 
-pthread  -c msa.c
msa.c: In function 'MSAfixnamesphy':
msa.c:629:36: error: may write a terminating nul past the end of the 
destination [-Werror=format-overflow=]
 sprintf(digit, "%-d", cnt);
 ~~~^
msa.c:629:17: note: format output between 2 and 11 bytes into a destination of 
size 10
 sprintf(digit, "%-d", cnt);
 ^~
cc1: all warnings being treated as errors
Makefile:10: recipe for target 'msa.o' failed
make[2]: *** [msa.o] Error 1
make[2]: Leaving directory '/<>/libmsa'
Makefile:33: recipe for target 'lmsa' failed
make[1]: *** [lmsa] Error 2
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
debian/rules:15: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---
Source: theseus
Source-Version: 3.3.0-6

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated theseus package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 24 Aug 2017 15:31:38 +0200
Source: theseus
Binary: theseus 

Bug#868905: [htcondor-debian] Bug#868905:

[Tim Theisen]

Hi Michael,

I incorporated your patch into the Debian build. I am currently waiting
for my upload to be accepted into sid.

Thank you, ...Tim


On 07/25/2017 08:48 PM, Michael Hudson-Doyle wrote:
> I fixed this in Ubuntu with this patch:
>
>
>
> ___
> htcondor-debian mailing list
> htcondor-deb...@cs.wisc.edu
> https://lists.cs.wisc.edu/mailman/listinfo/htcondor-debian

-- 
Tim Theisen
Release Manager
HTCondor & Open Science Grid
Center for High Throughput Computing
Department of Computer Sciences
University of Wisconsin - Madison
4261 Computer Sciences and Statistics
1210 W Dayton St
Madison, WI 53706-1685
+1 608 265 5736

Bug#873108: xscreensaver does not trap errors from intltool-update

[Jamie Zawinski]

Well, on every system I've ever had access to, intltool rarely works, so I took 
to just ignoring it entirely. YMMV.

Bug#873052: marked as done (gcl FTBFS on arm64: Unrecoverable error: Segmentation violation..)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2017 17:49:34 +
with message-id 
and subject line Bug#873052: fixed in gcl 2.6.12-55
has caused the Debian Bug report #873052,
regarding gcl FTBFS on arm64: Unrecoverable error: Segmentation violation..
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.)


-- 
873052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873052
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcl
Version: 2.6.12-53
Severity: serious

https://buildd.debian.org/status/logs.php?pkg=gcl=arm64

...
/<>/unixport/raw_pcl_gcl /<>/unixport/ -libdir 
/<>/ < foo
GCL (GNU Common Lisp)  April 1994  67111603 pages
Building symbol table for /<>/unixport/raw_pcl_gcl ..
loading /<>/unixport/../lsp/gcl_export.lsp
Initializing gcl_defmacro.o
Initializing gcl_evalmacros.o
Initializing gcl_top.o
Initializing gcl_module.o
loading /<>/unixport/../lsp/gcl_autoload.lsp

>
#<"COMPILER" package>

>
#<"SLOOP" package>

>
#<"ANSI-LOOP" package>

>
#<"DEFPACKAGE" package>

>
#<"TK" package>

>
#<"FPE" package>

>
#<"CLTL1-COMPAT" package>

>
#<"SYSTEM" package>

SYSTEM>
T

SYSTEM>Initializing gcl_predlib.o
Initializing gcl_setf.o
Initializing gcl_arraylib.o
Initializing gcl_assert.o
Initializing gcl_defstruct.o
Initializing gcl_restart.o
Initializing gcl_describe.o
Initializing gcl_listlib.o
Initializing gcl_mislib.o
Initializing gcl_numlib.o
Initializing gcl_packlib.o
Initializing gcl_seq.o
Initializing gcl_seqlib.o
Initializing gcl_trace.o
Initializing gcl_sloop.o
Initializing gcl_serror.o
Initializing gcl_destructuring_bind.o
Initializing gcl_loop.o
Initializing gcl_defpackage.o
Initializing gcl_make_defpackage.o
Initializing gcl_sharp.o
Initializing gcl_sharp_uv.o
Initializing gcl_namestring.o
Initializing gcl_logical_pathname_translations.o
Initializing gcl_make_pathname.o
Initializing gcl_parse_namestring.o
Initializing gcl_translate_pathname.o
Initializing gcl_directory.o
Initializing gcl_merge_pathnames.o
Initializing gcl_truename.o
Initializing gcl_rename_file.o
Initializing gcl_wild_pathname_p.o
Initializing gcl_pathname_match_p.o
Initializing gcl_iolib.o
Initializing gcl_fpe.o
Initializing gcl_cmpinline.o
Initializing gcl_cmputil.o
Initializing gcl_debug.o

Unrecoverable error: Segmentation violation..
Aborted
makefile:93: recipe for target 'saved_pcl_gcl' failed
make[2]: *** [saved_pcl_gcl] Error 134
rm raw_pcl_gcl
make[2]: Leaving directory '/<>/unixport'
makefile:90: recipe for target 'unixport/saved_pcl_gcl' failed
make[1]: *** [unixport/saved_pcl_gcl] Error 2
rm h/mcompdefs.h
make[1]: Leaving directory '/<>'
debian/rules:109: recipe for target 'build-ansi-gprof-stamp' failed
make: *** [build-ansi-gprof-stamp] Error 2
--- End Message ---
--- Begin Message ---
Source: gcl
Source-Version: 2.6.12-55

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

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

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

Debian distribution maintenance software
pp.
Camm Maguire  (supplier of updated gcl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 24 Aug 2017 16:37:07 +
Source: gcl
Binary: gcl gcl-doc
Architecture: source amd64 all
Version: 2.6.12-55
Distribution: unstable
Urgency: medium
Maintainer: Camm Maguire 
Changed-By: Camm Maguire 
Description:
 gcl- GNU Common Lisp compiler
 gcl-doc- Documentation for GNU Common Lisp
Closes: 873052
Changes:
 gcl (2.6.12-55) unstable; urgency=medium
 .
   * disable gprof on aarch64
   * Bug fix: "gcl FTBFS on arm64: Unrecoverable error: Segmentation
 violation..", thanks to Adrian Bunk (Closes: #873052).
Checksums-Sha1:
 ebdd84591cdddebfe6f2cba7a0bdc833f74139ab 1818 gcl_2.6.12-55.dsc
 5b018bcc1ed0bcc2874d2ccc750be37da9d83e96 382236 gcl_2.6.12-55.debian.tar.xz
 8ae8db964244393f07aa1491b873606f0da81f34 7513042 gcl-dbgsym_2.6.12-55_amd64.deb
 4f28043c3e7556d565bb120b6b182adc59407ad8 1129298 gcl-doc_2.6.12-55_all.deb
 b5cf227ed585e267ee91870da67072a1997b53cf 6757 gcl_2.6.12-55_amd64.buildinfo
 129839aac31f258cecf73e4fb1912f6625ca2a91 

Bug#873104: marked as done (openjdk-9: update-alternatives error + fail in updating)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2017 17:35:06 +
with message-id 
and subject line Bug#873104: fixed in openjdk-9 9~b181-4
has caused the Debian Bug report #873104,
regarding openjdk-9: update-alternatives error + fail in updating
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.)


-- 
873104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873104
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openjdk-9
Version: 9~b181-3
Severity: serious

Hi!

Today while upgrading openjdk-9* packages from 9~b181-2 to 9~b181-3:

=
Setting up openjdk-9-jre-headless:amd64 (9~b181-3) ...
update-alternatives: error: alternative path 
/usr/lib/jvm/java-9-openjdk-amd64/bin/rmid doesn't exist
dpkg: error processing package openjdk-9-jre-headless:amd64 (--configure):
 subprocess installed post-installation script returned error exit status 2
dpkg: dependency problems prevent configuration of openjdk-9-jdk-headless:amd64:
 openjdk-9-jdk-headless:amd64 depends on openjdk-9-jre-headless (= 9~b181-3); 
however:
  Package openjdk-9-jre-headless:amd64 is not configured yet.

dpkg: error processing package openjdk-9-jdk-headless:amd64 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of openjdk-9-jdk:amd64:
 openjdk-9-jdk:amd64 depends on openjdk-9-jdk-headless (= 9~b181-3); however:
  Package openjdk-9-jdk-headless:amd64 is not configured yet.

dpkg: error processing package openjdk-9-jdk:amd64 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of openjdk-9-jre:amd64:
 openjdk-9-jre:amd64 depends on openjdk-9-jre-headless (= 9~b181-3); however:
  Package openjdk-9-jre-headless:amd64 is not configured yet.

dpkg: error processing package openjdk-9-jre:amd64 (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 openjdk-9-jre-headless:amd64
 openjdk-9-jdk-headless:amd64
 openjdk-9-jdk:amd64
 openjdk-9-jre:amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
=

Before the update it was possible to see that a lot of disk space was
going to be freed (so probably something is missing on the new
packages?)

=
# LC_ALL=C apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  binutils-common binutils-x86-64-linux-gnu libbinutils
The following packages have been kept back:
  libc-dev-bin libc6 libc6-dev nodejs nodejs-dev
The following packages will be upgraded:
  binutils libdbusmenu-glib4 libdbusmenu-gtk3-4 libdbusmenu-gtk4 
libmariadbclient18 libnghttp2-14 libpam-systemd librtlsdr-dev librtlsdr0 
libsystemd0 libsystemd0:i386 libudev-dev libudev1 libudev1:i386 libxcursor1 
mariadb-common openjdk-9-jdk openjdk-9-jdk-headless openjdk-9-jre 
openjdk-9-jre-headless rtl-sdr
  systemd systemd-sysv udev
24 upgraded, 3 newly installed, 0 to remove and 5 not upgraded.
Need to get 10.2 MB/10.8 MB of archives.
After this operation, 274 MB disk space will be freed.
Do you want to continue? [Y/n]
=

And some warnings when trying to upgrade, saying that it was not
possible to remove some directories (since they were not empty; messages
are in Portuguese)

=
A descompactar openjdk-9-jre-headless:amd64 (9~b181-3) sobre (9~b181-2) ...
dpkg: aviso: não foi possível apagar o directório antigo 
'/usr/lib/jvm/java-9-openjdk-amd64/lib/server': Diretório não vazio
dpkg: aviso: não foi possível apagar o directório antigo 
'/etc/java-9-openjdk/security/policy/unlimited': Diretório não vazio
dpkg: aviso: não foi possível apagar o directório antigo 
'/etc/java-9-openjdk/security/policy/limited': Diretório não vazio
dpkg: aviso: não foi possível apagar o directório antigo 
'/etc/java-9-openjdk/security/policy': Diretório não vazio
dpkg: aviso: não foi possível apagar o directório antigo 
'/etc/java-9-openjdk/security': Diretório não vazio
dpkg: aviso: não foi possível apagar o directório antigo 
'/etc/java-9-openjdk/management': Diretório não vazio
dpkg: aviso: não foi possível apagar o directório antigo '/etc/java-9-openjdk': 
Diretório não vazi
=

Thank you!

Best regards,
Nelson

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

Kernel: Linux 4.12.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), 
LANGUAGE=pt_BR:pt:en 

Processed: [bts-link] source package src:erlang-p1-oauth2

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:erlang-p1-oauth2
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #871190 (http://bugs.debian.org/871190)
> # Bug title: erlang-p1-oauth2: FTBFS: dh_auto_test: make --no-print-directory 
> -f /usr/share/dh-rebar/make/dh-rebar.Makefile test returned exit code 2
> #  * https://github.com/processone/p1_oauth2/issues/2
> #  * remote status changed: closed -> open
> #  * reopen upstream
> tags 871190 - fixed-upstream
Bug #871190 [src:erlang-p1-oauth2] erlang-p1-oauth2: FTBFS: dh_auto_test: make 
--no-print-directory -f /usr/share/dh-rebar/make/dh-rebar.Makefile test 
returned exit code 2
Removed tag(s) fixed-upstream.
> usertags 871190 - status-closed
Usertags were: status-closed.
Usertags are now: .
> usertags 871190 + status-open
There were no usertags set.
Usertags are now: status-open.
> thanks
Stopping processing here.

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

Bug#853614: marked as done (pingus: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2017 17:35:18 +
with message-id 
and subject line Bug#853614: fixed in pingus 0.7.6-4
has caused the Debian Bug report #853614,
regarding pingus: 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.)


-- 
853614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853614
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pingus
Version: 0.7.6-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/pingus_0.7.6-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

[...]
 highlight
src/pingus/screens/demo_session.cpp: In member function 'virtual void 
BButton::on_click()':
src/pingus/screens/demo_session.cpp:68:5: error: 'callback' was not declared in 
this scope
 callback();
 ^~~~
src/pingus/screens/demo_session.cpp:68:5: note: suggested alternative: 'calloc'
 callback();
 ^~~~
 calloc
src/pingus/screens/demo_session.cpp: In constructor 
'DemoSession::DemoSession(const Pathname&)':
src/pingus/screens/demo_session.cpp:125:57: error: 'bind' is not a member of 
'std'

std::bind(::on_fast_forward_press, this),
 ^~~~
src/pingus/screens/demo_session.cpp:125:57: note: suggested alternative: 'find'

std::bind(::on_fast_forward_press, this),
 ^~~~
 find
src/pingus/screens/demo_session.cpp:126:57: error: 'bind' is not a member of 
'std'

std::bind(::is_fast_forward, this)));
 ^~~~
src/pingus/screens/demo_session.cpp:126:57: note: suggested alternative: 'find'

std::bind(::is_fast_forward, this)));
 ^~~~
 find
src/pingus/screens/demo_session.cpp:128:51: error: 'bind' is not a member of 
'std'
  
std::bind(::on_pause_press, this),
   ^~~~
src/pingus/screens/demo_session.cpp:128:51: note: suggested alternative: 'find'
  
std::bind(::on_pause_press, this),
   ^~~~
   find
src/pingus/screens/demo_session.cpp:129:51: error: 'bind' is not a member of 
'std'
  std::bind(::is_pause, 
this)));
   ^~~~
src/pingus/screens/demo_session.cpp:129:51: note: suggested alternative: 'find'
  std::bind(::is_pause, 
this)));
   ^~~~
   find
src/pingus/screens/demo_session.cpp:131:54: error: 'bind' is not a member of 
'std'
 
std::bind(::restart, this)));
  ^~~~
src/pingus/screens/demo_session.cpp:131:54: note: suggested alternative: 'find'
 
std::bind(::restart, 

Bug#873120: 389-ds-base: FTBFS on various architectures: test_plugin_pwdstorage_pbkdf2_rounds fails

[James Cowgill]

Source: 389-ds-base
Version: 1.3.6.7-2
Severity: serious
Tags: sid buster

Hi,

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

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

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

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

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Processed: Add link to upstream bug

[Debian Bug Tracking System]

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

> forwarded 868773 https://github.com/pimutils/khal/issues/683
Bug #868773 [src:khal] khal FTBFS: AssertionError: assert not OSError(6, 'No 
such device or address')
Set Bug forwarded-to-address to 'https://github.com/pimutils/khal/issues/683'.
> thanks
Stopping processing here.

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

Bug#869006: marked as done (jnr-unixsocket: FTBFS: Failed to execute goal org.apache.maven.plugins:maven-jar-plugin:3.0.2:jar (default) on project jnr-unixsocket: You have to use a classifier to attac

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2017 18:14:33 +0100
with message-id <20170824171433.ga30...@alice.nomadium.lan>
and subject line Re: jnr-unixsocket: FTBFS: find: 
'/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such 
file or directory
has caused the Debian Bug report #869006,
regarding jnr-unixsocket: FTBFS: Failed to execute goal 
org.apache.maven.plugins:maven-jar-plugin:3.0.2:jar (default) on project 
jnr-unixsocket: You have to use a classifier to attach supplemental artifacts 
to the project instead of replacing them
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.)


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

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=maven --with javahelper
>dh_testdir -O--buildsystem=maven
>dh_update_autotools_config -O--buildsystem=maven
>dh_autoreconf -O--buildsystem=maven
>dh_auto_configure -O--buildsystem=maven
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
> such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': 
> No such file or directory
> find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': 
> No such file or directory
>   mh_patchpoms -plibjnr-unixsocket-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
> Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8
>jh_linkjars -O--buildsystem=maven
>dh_auto_build -O--buildsystem=maven
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
>  -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo package javadoc:jar 
> javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US
> Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8
> [INFO] Scanning for projects...
> [INFO] 
> [INFO] 
> 
> [INFO] Building jnr-unixsocket 0.18
> [INFO] 
> 
> [INFO] 
> [INFO] --- maven-resources-plugin:3.0.0:resources 
> (default-resources) @ jnr-unixsocket ---
> [WARNING] Using platform encoding (UTF-8 actually) to copy filtered 
> resources, i.e. build is platform dependent!
> [INFO] skip non existing resourceDirectory 
> /<>/src/main/resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.6.1:compile 
> (default-compile) @ jnr-unixsocket ---
> [WARNING] The POM for 
> org.codehaus.plexus:plexus-compiler-api:jar:2.x is invalid, transitive 
> dependencies (if any) will not be available, enable debug logging for more 
> details
> [WARNING] The POM for 
> org.codehaus.plexus:plexus-compiler-javac:jar:2.x is invalid, transitive 
> dependencies (if any) will not be available, enable debug logging for more 
> details
> [INFO] Changes detected - recompiling the module!
> [WARNING] File encoding has not been set, using platform encoding 
> UTF-8, i.e. build is platform dependent!
> [INFO] Compiling 17 source files to /<>/target/classes
> [INFO] /<>/src/main/java/jnr/unixsocket/Common.java: 
> /<>/src/main/java/jnr/unixsocket/Common.java uses unchecked or 
> unsafe operations.
> [INFO] /<>/src/main/java/jnr/unixsocket/Common.java: 
> Recompile with -Xlint:unchecked for details.
> [INFO] 
> [INFO] --- maven-bundle-plugin:2.5.4:manifest 
> (bundle-manifest) @ jnr-unixsocket ---
> [INFO] 
> [INFO] --- maven-resources-plugin:3.0.0:testResources 
> (default-testResources) @ jnr-unixsocket ---
> [WARNING] Using platform encoding (UTF-8 actually) to copy filtered 
> 

Bug#872402: golang-golang-x-tools-dev: Does not work on mips*

[Shengjing Zhu]

Control: severity -1 normal

On Thu, Aug 24, 2017 at 10:37 PM, Martín Ferrari  wrote:
> Yes, sorry, I was confused with x/tools, which has disabled tests. This
> one does not get built in other arches, so the relevant tests are not
> executed.. Maybe we should make it arch:any...?
>

I think the CI like ci.d.n should run on more archs instead...

> Prometheus and friends were failing. I understood now what you are doing
> here (it took me a while), and by passing tags I managed to get them
> building again, but that's not a reasonable solution.. The packages
> should build out of the box. Can't you add the correct build
> restrictions for gccgo so we don't need the tags?

ok, so I read the issue on https://github.com/golang/go/issues/18031

I don't have mips env to verify comments by foka. But what foka said
in that issue is,
gccgo reports mipsel and mips both as `mipso32`. So we need pass
another `-tags` to distinguish the two archs.
Unless gccgo has corrent build tip, we can only manually add `-tags
mips` or `-tags mipsel`.

BTW, let me down grade this bug's severity first since I think we have
workaround for that :)

-- 
Best regards,
Shengjing Zhu

Processed: Re: Bug#872402: golang-golang-x-tools-dev: Does not work on mips*

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #872402 [golang-golang-x-sys] golang-golang-x-sys-dev: Does not work on 
mips*
Severity set to 'normal' from 'grave'

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

Bug#868773: khal FTBFS: AssertionError: assert not OSError(6, 'No such device or address')

[Guido Günther]

Hi,
On Tue, Jul 18, 2017 at 03:41:33PM +0300, Adrian Bunk wrote:
> Source: khal
> Version: 1:0.9.6-1
> Severity: serious
> 
> https://buildd.debian.org/status/fetch.php?pkg=khal=all=1:0.9.6-1=1500381224=0
> 
> ...
> === FAILURES 
> ===
>  test_import_from_stdin 
> 
> 
> runner = 
> 
> def test_import_from_stdin(runner):
> ics_data = 'This is some really fake icalendar data'
> 
> with mock.patch('khal.controllers.import_ics') as mocked_import:
> runner = runner()
> result = runner.invoke(main_khal, ['import'], input=ics_data)
> 
> >   assert not result.exception
> E   AssertionError: assert not OSError(6, 'No such device or address')
> E+  where OSError(6, 'No such device or address') =  OSError(6, 'No such device or address')>.exception
> 
> tests/cli_test.py:505: AssertionError
>  test_printics_read_from_stdin 
> _
> 
> runner = 
> 
> def test_printics_read_from_stdin(runner):
> runner = runner(command='printics')
> result = runner.invoke(main_khal, ['printics'], 
> input=_get_text('cal_d'))
> >   assert not result.exception
> E   AssertionError: assert not OSError(6, 'No such device or address')
> E+  where OSError(6, 'No such device or address') =  OSError(6, 'No such device or address')>.exception
> 
> tests/cli_test.py:683: AssertionError
> == 2 failed, 261 passed, 7 skipped, 3 xfailed in 9.52 seconds 
> ==
> E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd 
> /<>/.pybuild/pythonX.Y_3.6/build; python3.6 -m pytest tests
> dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.6 3.5 
> returned exit code 13
> debian/rules:26: recipe for target 'override_dh_auto_test' failed
> make[1]: *** [override_dh_auto_test] Error 25

Any chance this gets fixed? It would be great to have a recent khal in
unstable/testing.
 -- Guido

Bug#873118: commons-io: FTBFS: Several failed unit tests

[Miguel Landaeta]

Package: src:commons-io
Version: 2.5-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

[...]

Results :

Tests in error: 
  FileUtilsTestCase.testCopyDirectoryToDirectory_NonExistingDest:1323 ?? IO 
Unab...
  FileUtilsTestCase.testCopyDirectoryToExistingDest:1409 ?? IO Unable to delete 
...
  FileUtilsTestCase.testCopyDirectoryToNonExistingDest:1367 ?? IO Unable to 
dele...

Tests run: 1157, Failures: 0, Errors: 3, Skipped: 4

[INFO] 

[INFO] BUILD FAILURE
[INFO] 

[INFO] Total time: 02:01 min
[INFO] Finished at: 2017-08-24T09:16:19Z
[INFO] Final Memory: 14M/276M
[INFO] 

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test 
(default-test) on project commons-io: There are test 
failures.
[ERROR] 
[ERROR] Please refer to 
/<>/target/surefire-reports for the individual test results.
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with 
the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug 
logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, 
please read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
dh_auto_test: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo test returned exit code 1
debian/rules:4: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2


-- System Information:
Debian Release: 8.9
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)

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

-- 
Miguel Landaeta, nomadium at debian.org
secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key.
"Faith means not wanting to know what is true." -- Nietzsche


commons-io_2.5-1_amd64-2017-08-24T09:13:55Z.build.gz
Description: application/gzip


signature.asc
Description: Digital signature

Bug#873097: glibc: FTBFS on *all* architectures except m68k, powerpcspe, sh4

[Adrian Bunk]

On Thu, Aug 24, 2017 at 04:48:55PM +0200, Thorsten Glaser wrote:
> Source: glibc
> Version: 2.24-16
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
> 
> cf. https://buildd.debian.org/status/package.php?p=glibc
> 
> For over three days now, src:glibc is FTBFS’ing virtually everywhere:
> 
> amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el,
> s390x, alpha, hppa, hurd-i386, kfreebsd-amd64, kfreebsd-i386, powerpc,
> ppc64, sparc64, x32 — the list is so long it doesn’t fit into the
> bugreport’s Subject.

That's due to the #872846 change.

> ... which is probably why the
> three slow architectures have been spared.

These are buildds that are building with nocheck.

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

Processed: Re: libemf: FTBFS: #error Unknown CPU architecture!

[Debian Bug Tracking System]

Processing control commands:

> affects -1 pstoedit
Bug #872880 [src:libemf] libemf: FTBFS: #error Unknown CPU architecture!
Added indication that 872880 affects pstoedit
> severity -1 serious
Bug #872880 [src:libemf] libemf: FTBFS: #error Unknown CPU architecture!
Severity set to 'serious' from 'important'

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

Processed: Re: Bug#873052: gcl FTBFS on arm64: Unrecoverable error: Segmentation violation..

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #873052 [src:gcl] gcl FTBFS on arm64: Unrecoverable error: Segmentation 
violation..
Severity set to 'serious' from 'important'

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

Bug#873108: xscreensaver does not trap errors from intltool-update

[Helmut Grohne]

Source: xscreensaver
Version: 5.36-1
Severity: serious
Justification: policy 4.6
User: helm...@debian.org
Usertags: rebootstrap

The debian policy section 4.6 requires that when build commands fail,
the build should abort. In case xscreensaver's intltool-update aborts,
the error is ignored and the build attempts to continue potentially
resulting in a broken package. Adding "set -e; " (as suggested by the
policy) or chaining the commands with "&&" fixes this issue.

Helmut

Bug#864434: marked as done (axiom FTBFS in unstable: cp: cannot stat '/build/1st/axiom-20170401/int/algebra/BASTYPE.nrlib/code.o': No such file or directory)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2017 15:50:32 +
with message-id 
and subject line Bug#864434: fixed in axiom 20170401-2
has caused the Debian Bug report #864434,
regarding axiom FTBFS in unstable: cp: cannot stat 
'/build/1st/axiom-20170401/int/algebra/BASTYPE.nrlib/code.o': 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.)


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

Something recently broke building axiom in unstable:

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

...
GCL (GNU Common Lisp)  2.6.12 CLtL1Fri Apr 22 15:51:11 UTC 2016
Source License: LGPL(gcl,gmp), GPL(unexec,bfd,xgcl)
Binary License:  GPL due to GPL'ed components: (XGCL READLINE UNEXEC)
Modifications of this banner must retain notice of a compatible license
Dedicated to the memory of W. Schelter

Use (help) to get some basic information on how to use GCL.
Temporary directory for compiler files:
/build/1st/axiom-20170401/obj/tmp/

>

>sa07 compiling BASTYPE.spad to BASTYPE.nrlib
sa06 copying BASTYPE.nrlib to BASTYPE.o
cp: cannot stat '/build/1st/axiom-20170401/int/algebra/BASTYPE.nrlib/code.o': 
No such file or directory
Makefile:638: recipe for target 
'/build/1st/axiom-20170401/mnt/linux/algebra/BASTYPE.o' failed
make[4]: *** [/build/1st/axiom-20170401/mnt/linux/algebra/BASTYPE.o] Error 1


The timing might match the gcl 2.6.12-48 upload (the amd64 FTBFS on
2017-05-27 could have been for unrelated reasons so shouldn't rule
that out), but that's just a guess.
--- End Message ---
--- Begin Message ---
Source: axiom
Source-Version: 20170401-2

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

Debian distribution maintenance software
pp.
Camm Maguire  (supplier of updated axiom package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 24 Aug 2017 11:05:11 +
Source: axiom
Binary: axiom axiom-source axiom-test axiom-doc axiom-databases axiom-tex 
axiom-graphics axiom-graphics-data axiom-hypertex axiom-hypertex-data
Architecture: source all amd64
Version: 20170401-2
Distribution: unstable
Urgency: medium
Maintainer: Camm Maguire 
Changed-By: Camm Maguire 
Description:
 axiom  - General purpose computer algebra system: main binary and modules
 axiom-databases - General purpose computer algebra system: generated text 
databases
 axiom-doc  - General purpose computer algebra system: documentation
 axiom-graphics - General purpose computer algebra system: graphics subsystem
 axiom-graphics-data - General purpose computer algebra system: graphics 
subsystem
 axiom-hypertex - General purpose computer algebra system: hypertex subsystem
 axiom-hypertex-data - General purpose computer algebra system: hypertex 
subsystem
 axiom-source - General purpose computer algebra system: source files
 axiom-test - General purpose computer algebra system: regression test inputs
 axiom-tex  - General purpose computer algebra system: style file for TeX
Closes: 864434
Changes:
 axiom (20170401-2) unstable; urgency=medium
 .
   * build-dep latest gcl
   * qsmulmod32 calls patch
   * Bug fix: "axiom FTBFS in unstable: cp: cannot stat
 /build/1st/axiom-20170401/int/algebra/BASTYPE.nrlib/code.o:
 No such file or directory", thanks to Adrian Bunk (Closes: #864434).
Checksums-Sha1:
 bb0f116ae6c4f1783fe03b2886cb6a76bfc4e4ba 2440 axiom_20170401-2.dsc
 951c6c41d851571e2c7857ae3ca6b9138fce2a05 743532 axiom_20170401-2.debian.tar.xz
 6496b6606dc17bcefc280e27c62a91f51edef8f7 911742 
axiom-databases_20170401-2_all.deb
 016be90ae473d45c8f999477a9656419b9f07d80 7866 axiom-dbgsym_20170401-2_amd64.deb
 25a4d7e211f789da5ed73debe4ffbe93eb571e1f 116455428 axiom-doc_20170401-2_all.deb
 c92cb331087ebd0e9d0777e8f80b4c6098bf05b6 1585362 

Bug#873104: openjdk-9: update-alternatives error + fail in updating

[Nelson A. de Oliveira]

Source: openjdk-9
Version: 9~b181-3
Severity: serious

Hi!

Today while upgrading openjdk-9* packages from 9~b181-2 to 9~b181-3:

=
Setting up openjdk-9-jre-headless:amd64 (9~b181-3) ...
update-alternatives: error: alternative path 
/usr/lib/jvm/java-9-openjdk-amd64/bin/rmid doesn't exist
dpkg: error processing package openjdk-9-jre-headless:amd64 (--configure):
 subprocess installed post-installation script returned error exit status 2
dpkg: dependency problems prevent configuration of openjdk-9-jdk-headless:amd64:
 openjdk-9-jdk-headless:amd64 depends on openjdk-9-jre-headless (= 9~b181-3); 
however:
  Package openjdk-9-jre-headless:amd64 is not configured yet.

dpkg: error processing package openjdk-9-jdk-headless:amd64 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of openjdk-9-jdk:amd64:
 openjdk-9-jdk:amd64 depends on openjdk-9-jdk-headless (= 9~b181-3); however:
  Package openjdk-9-jdk-headless:amd64 is not configured yet.

dpkg: error processing package openjdk-9-jdk:amd64 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of openjdk-9-jre:amd64:
 openjdk-9-jre:amd64 depends on openjdk-9-jre-headless (= 9~b181-3); however:
  Package openjdk-9-jre-headless:amd64 is not configured yet.

dpkg: error processing package openjdk-9-jre:amd64 (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 openjdk-9-jre-headless:amd64
 openjdk-9-jdk-headless:amd64
 openjdk-9-jdk:amd64
 openjdk-9-jre:amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
=

Before the update it was possible to see that a lot of disk space was
going to be freed (so probably something is missing on the new
packages?)

=
# LC_ALL=C apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  binutils-common binutils-x86-64-linux-gnu libbinutils
The following packages have been kept back:
  libc-dev-bin libc6 libc6-dev nodejs nodejs-dev
The following packages will be upgraded:
  binutils libdbusmenu-glib4 libdbusmenu-gtk3-4 libdbusmenu-gtk4 
libmariadbclient18 libnghttp2-14 libpam-systemd librtlsdr-dev librtlsdr0 
libsystemd0 libsystemd0:i386 libudev-dev libudev1 libudev1:i386 libxcursor1 
mariadb-common openjdk-9-jdk openjdk-9-jdk-headless openjdk-9-jre 
openjdk-9-jre-headless rtl-sdr
  systemd systemd-sysv udev
24 upgraded, 3 newly installed, 0 to remove and 5 not upgraded.
Need to get 10.2 MB/10.8 MB of archives.
After this operation, 274 MB disk space will be freed.
Do you want to continue? [Y/n]
=

And some warnings when trying to upgrade, saying that it was not
possible to remove some directories (since they were not empty; messages
are in Portuguese)

=
A descompactar openjdk-9-jre-headless:amd64 (9~b181-3) sobre (9~b181-2) ...
dpkg: aviso: não foi possível apagar o directório antigo 
'/usr/lib/jvm/java-9-openjdk-amd64/lib/server': Diretório não vazio
dpkg: aviso: não foi possível apagar o directório antigo 
'/etc/java-9-openjdk/security/policy/unlimited': Diretório não vazio
dpkg: aviso: não foi possível apagar o directório antigo 
'/etc/java-9-openjdk/security/policy/limited': Diretório não vazio
dpkg: aviso: não foi possível apagar o directório antigo 
'/etc/java-9-openjdk/security/policy': Diretório não vazio
dpkg: aviso: não foi possível apagar o directório antigo 
'/etc/java-9-openjdk/security': Diretório não vazio
dpkg: aviso: não foi possível apagar o directório antigo 
'/etc/java-9-openjdk/management': Diretório não vazio
dpkg: aviso: não foi possível apagar o directório antigo '/etc/java-9-openjdk': 
Diretório não vazi
=

Thank you!

Best regards,
Nelson

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

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

Processed: Re: gcl FTBFS on arm64: Unrecoverable error: Segmentation violation..

[Debian Bug Tracking System]

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

> tags 873052 unreproducible
Bug #873052 [src:gcl] gcl FTBFS on arm64: Unrecoverable error: Segmentation 
violation..
Added tag(s) unreproducible.
> severity 873052 important
Bug #873052 [src:gcl] gcl FTBFS on arm64: Unrecoverable error: Segmentation 
violation..
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#873052: gcl FTBFS on arm64: Unrecoverable error: Segmentation violation..

[Camm Maguire]

tags 873052 unreproducible
severity 873052 important
thanks

Greetings, and thanks for your report!  Built stock gcl sources on up to
date sid chroot on asachi without issue.  Uploaded binary.  I assume
this is some transient issue on some buildd machines, but if you can
tell me how to reproduce will investigate further.

Take care,
-- 
Camm Maguirec...@maguirefamily.org
==
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah

Bug#865944: marked as done (python-django-formtools FTBFS with Django 1.11)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2017 15:36:22 +
with message-id 
and subject line Bug#865944: fixed in python-django-formtools 2.0-1
has caused the Debian Bug report #865944,
regarding python-django-formtools FTBFS with Django 1.11
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.)


-- 
865944: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865944
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django-formtools
Version: 1.0+20160714.git54f1ccca01-1
Severity: serious
Tags: buster sid

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory 
'/build/1st/python-django-formtools-1.0+20160714.git54f1ccca01'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
set -e ; set -x ; for pyvers in 2.7 3.5; do \
PYMAJOR=`echo $pyvers | cut -d'.' -f1` ; \
echo "===> Testing with python$pyvers (python$PYMAJOR)" ; \
if [ $PYMAJOR = "2" ] ; then \
LIBDIR_END=$pyvers ; \
else \
LIBDIR_END=$PYMAJOR ; \
fi ; \
PYTHONPATH=. DJANGO_SETTINGS_MODULE=tests.settings 
PYTHON=python${pyvers} python${PYMAJOR}-coverage run 
/usr/lib/python$LIBDIR_END/dist-packages/django/bin/django-admin.py test tests 
; \
done
+ cut -d. -f1
+ echo 2.7
+ PYMAJOR=2
+ echo ===> Testing with python2.7 (python2)
===> Testing with python2.7 (python2)
+ [ 2 = 2 ]
+ LIBDIR_END=2.7
+ PYTHONPATH=. DJANGO_SETTINGS_MODULE=tests.settings PYTHON=python2.7 
python2-coverage run 
/usr/lib/python2.7/dist-packages/django/bin/django-admin.py test tests
EE..
==
ERROR: tests.wizard.wizardtests.tests (unittest.loader.ModuleImportFailure)
--
ImportError: Failed to import test module: tests.wizard.wizardtests.tests
Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/loader.py", line 254, in _find_tests
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/unittest/loader.py", line 232, in 
_get_module_from_name
__import__(name)
  File 
"/build/1st/python-django-formtools-1.0+20160714.git54f1ccca01/tests/wizard/wizardtests/tests.py",
 line 11, in 
from formtools.wizard.views import CookieWizardView
  File 
"/build/1st/python-django-formtools-1.0+20160714.git54f1ccca01/formtools/wizard/views.py",
 line 14, in 
from .storage import get_storage
  File 
"/build/1st/python-django-formtools-1.0+20160714.git54f1ccca01/formtools/wizard/storage/__init__.py",
 line 3, in 
from .base import BaseStorage
  File 
"/build/1st/python-django-formtools-1.0+20160714.git54f1ccca01/formtools/wizard/storage/base.py",
 line 4, in 
from django.utils.functional import lazy_property
ImportError: cannot import name lazy_property


==
ERROR: tests.wizard.test_sessionstorage (unittest.loader.ModuleImportFailure)
--
ImportError: Failed to import test module: tests.wizard.test_sessionstorage
Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/loader.py", line 254, in _find_tests
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/unittest/loader.py", line 232, in 
_get_module_from_name
__import__(name)
  File 
"/build/1st/python-django-formtools-1.0+20160714.git54f1ccca01/tests/wizard/test_sessionstorage.py",
 line 3, in 
from formtools.wizard.storage.session import SessionStorage
  File 
"/build/1st/python-django-formtools-1.0+20160714.git54f1ccca01/formtools/wizard/storage/__init__.py",
 line 3, in 
from .base import BaseStorage
  File 
"/build/1st/python-django-formtools-1.0+20160714.git54f1ccca01/formtools/wizard/storage/base.py",
 line 4, in 
from django.utils.functional import lazy_property
ImportError: cannot import name lazy_property


==
ERROR: tests.wizard.test_loadstorage (unittest.loader.ModuleImportFailure)
--
ImportError: Failed to import test module: tests.wizard.test_loadstorage
Traceback (most recent call last):
  File 

Bug#865938: marked as done (python-django-bootstrap-form FTBFS with Django 1.11)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2017 15:19:16 +
with message-id 
and subject line Bug#865938: fixed in python-django-bootstrap-form 3.2.1-3
has caused the Debian Bug report #865938,
regarding python-django-bootstrap-form FTBFS with Django 1.11
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.)


-- 
865938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865938
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django-bootstrap-form
Version: 3.2.1-2
Severity: serious
Tags: buster sid

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/python-django-bootstrap-form-3.2.1'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
set -e && for pyvers in 2.7 3.5 ; do \
python$pyvers setup.py test ; \
done
running test
running egg_info
writing requirements to django_bootstrap_form.egg-info/requires.txt
writing django_bootstrap_form.egg-info/PKG-INFO
writing top-level names to django_bootstrap_form.egg-info/top_level.txt
writing dependency_links to django_bootstrap_form.egg-info/dependency_links.txt
reading manifest file 'django_bootstrap_form.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'django_bootstrap_form.egg-info/SOURCES.txt'
running build_ext
FF
==
FAIL: test_basic_form (bootstrapform.tests.BootstrapTemplateTagTests)
--
Traceback (most recent call last):
  File "/build/1st/python-django-bootstrap-form-3.2.1/bootstrapform/tests.py", 
line 59, in test_basic_form
self.assertHTMLEqual(html, content)
  File "/usr/lib/python2.7/dist-packages/django/test/testcases.py", line 710, 
in assertHTMLEqual
self.fail(self._formatMessage(msg, standardMsg))
AssertionError: 

Cha [truncated]... != 

Cha [truncated]...
  
  
  Char field
  
  
  
  
  
  Choice field
  
- 
+ 
?   
+

  
  Zero
  
  One
  
  Two
  
  
  
  
  
  Radio choice
  
  
  
  Zero
  
  
  
  One
  
  
  
  Two
  
  
  
  
  
  Multiple choice
  
  
  
  Zero
  
  One
  
  Two
  
  
  
  
  
  Multiple checkbox
  
  
  
  
  Zero
  
  
  
  One
  
  
  
  Two
  
  
  
  
  
  
  File fied
  
  
  
  
  
  Password field
  
  
  
  
  
  Textarea
  
  
  
  
  
  
  
  
  Boolean field
  
  
  
  
  

==
FAIL: test_horizontal_form (bootstrapform.tests.BootstrapTemplateTagTests)
--
Traceback (most recent call last):
  File "/build/1st/python-django-bootstrap-form-3.2.1/bootstrapform/tests.py", 
line 79, in test_horizontal_form
self.assertHTMLEqual(html, content)
  File "/usr/lib/python2.7/dist-packages/django/test/testcases.py", line 710, 
in assertHTMLEqual
self.fail(self._formatMessage(msg, standardMsg))
AssertionError: 


  
  Char field
  
  
  
  
  
  Choice field
  
- 
+ 
?   
+

  
  Zero
  
  One
  
  Two
  
  
  
  
  
  Radio choice
  
  
  
  Zero
  
  
  
  One
  
  
  
  Two
  
  
  
  
  
  Multiple choice
  
  
  
  Zero
  
  One
  
  Two
  
  
  
  
  
  Multiple checkbox
  
  
  
  
  Zero
  
  
  
  One
  
  
  
  Two
  
  
  
  
  
  
  File fied
  
  
  
  
  
  Password field
  
  
  
  
  
  Textarea
  
  
  
  
  
  
  
  
  Boolean field
  
  
  
  
  

--
Ran 2 tests in 0.076s

FAILED (failures=2)
Creating test database for alias 'default'...
System check identified no issues (0 silenced).
Destroying test database for alias 'default'...
debian/rules:26: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 2
--- End Message ---
--- Begin Message ---
Source: python-django-bootstrap-form
Source-Version: 3.2.1-3

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

Bug#865938: marked as pending

[Thomas Goirand]

tag 865938 pending
thanks

Hello,

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


https://anonscm.debian.org/cgit/openstack/python/python-django-bootstrap-form.git/commit/?id=a724c93

---
commit a724c93066ab3522cafb256587c7c2f74ea6996c
Author: Thomas Goirand 
Date:   Thu Aug 24 14:56:18 2017 +

  * Apply patch from Johannes Keyser  to fix tests
with Django 1.11 (Closes: #865938).

diff --git a/debian/changelog b/debian/changelog
index 2d5acd9..397a36b 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,5 +1,6 @@
-python-django-bootstrap-form (3.2.1-3) UNRELEASED; urgency=medium
+python-django-bootstrap-form (3.2.1-3) unstable; urgency=medium
 
+  [ Daniel Baumann ]
   * Updating vcs fields.
   * Updating copyright format url.
   * Updating maintainer field.
@@ -10,7 +11,11 @@ python-django-bootstrap-form (3.2.1-3) UNRELEASED; 
urgency=medium
   * Updating standards version to 4.0.1.
   * Updating standards version to 4.1.0.
 
- -- Daniel Baumann   Fri, 04 Aug 2017 
21:59:18 +0200
+  [ Thomas Goirand ]
+  * Apply patch from Johannes Keyser  to fix tests
+with Django 1.11 (Closes: #865938).
+
+ -- Thomas Goirand   Thu, 24 Aug 2017 14:54:38 +
 
 python-django-bootstrap-form (3.2.1-2) unstable; urgency=medium
 

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

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2017 15:04:52 +
with message-id 
and subject line Bug#871281: fixed in curlpp 0.8.1-2
has caused the Debian Bug report #871281,
regarding libcurlpp0: 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.)


-- 
871281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871281
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcurlpp0
Version: 0.8.1-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

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: curlpp
Source-Version: 0.8.1-2

We believe that the bug you reported is fixed in the latest version of
curlpp, 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.
Ximin Luo  (supplier of updated curlpp 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: Thu, 24 Aug 2017 16:15:34 +0200
Source: curlpp
Binary: libcurlpp0 libcurlpp-dev
Architecture: source
Version: 0.8.1-2
Distribution: unstable
Urgency: medium
Maintainer: Ximin Luo 
Changed-By: Ximin Luo 
Description:
 libcurlpp-dev - c++ wrapper for libcurl (development files)
 libcurlpp0 - c++ wrapper for libcurl
Closes: 871281
Changes:
 curlpp (0.8.1-2) unstable; urgency=medium
 .
   * Deal with GCC-7 op mangling. (Closes: #871281)
   * Update to latest Standards-Version. Changes:
 - Change Priority from extra to optional.
Checksums-Sha1:
 caea9614123d8c18fb74dd2fd6464ed3928b8c40 2040 curlpp_0.8.1-2.dsc
 96c6ac11a64b9928b9ac7bdae144d14e60ab7889 3492 curlpp_0.8.1-2.debian.tar.xz
 10ddac2db486bcd9709c77af3ddd4ce2a755f7f4 6113 curlpp_0.8.1-2_source.buildinfo
Checksums-Sha256:
 e10104783eeff01fbb6a5f864b026c20c99a977698760e4e8782c8a65690079f 2040 
curlpp_0.8.1-2.dsc
 38610a896048b4040379085b526e8dfb331deae37590dc10ea5b2da6f3b11f50 3492 
curlpp_0.8.1-2.debian.tar.xz
 

Bug#853434: marked as done (gri: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2017 15:05:23 +
with message-id 
and subject line Bug#853434: fixed in gri 2.12.26-1
has caused the Debian Bug report #853434,
regarding gri: 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.)


-- 
853434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853434
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gri
Version: 2.12.23-10
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/gri_2.12.23-10_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

[...]
grstring.cc: In function 'void gr_drawstring_svg(const char*, double, double, 
double)':
grstring.cc:1049:18: warning: variable 'slant_font' set but not used 
[-Wunused-but-set-variable]
  gr_fontID   slant_font = original_font; // prevent compiler warning
  ^~
grstring.cc:1051:18: warning: variable 'know_slant_font' set but not used 
[-Wunused-but-set-variable]
  boolknow_slant_font = false;
  ^~~
mv -f .deps/grstring.Tpo .deps/grstring.Po
g++ -DDEFAULT_GRI_DIR=\"/usr/share/gri/2.12.23/\"  -DPACKAGE_NAME=\"gri\" 
-DPACKAGE_TARNAME=\"gri\" -DPACKAGE_VERSION=\"2.12.23\" -DPACKAGE_STRING=\"gri\ 
2.12.23\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"gri\" -DVERSION=\"2.12.23\" 
-DGRI_IS_BIG_ENDIAN=0 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_UNISTD_H=1 
-DHAVE_LIBNETCDF=1 -DSTDC_HEADERS=1 -DHAVE_LIBREADLINE=1 -DHAVE_ISNAN=1 
-DHAVE_ISINF=1 -DHAVE_ACOSH=1 -DHAVE_GETCWD=1 -DHAVE_POPEN=1 -DHAVE_MKSTEMP=1 
-DHAVE_TMPNAM=1 -DHAVE_TEMPNAM=1 -DHAVE_GETHOSTNAME=1 -DHAVE_ACCESS=1 
-DHAVE_LSTAT=1 -DHAVE_STAT=1 -DHAVE_STRERROR=1 -DHAVE_GETENV=1 -DHAVE_DRAND48=1 
-I.-Wall -DCPLUSPLUSNEW -fno-strength-reduce -I/usr/include -O2 -MT group.o 
-MD -MP -MF .deps/group.Tpo -c -o group.o group.cc
mv -f .deps/group.Tpo .deps/group.Po
g++ -DDEFAULT_GRI_DIR=\"/usr/share/gri/2.12.23/\"  -DPACKAGE_NAME=\"gri\" 
-DPACKAGE_TARNAME=\"gri\" -DPACKAGE_VERSION=\"2.12.23\" -DPACKAGE_STRING=\"gri\ 
2.12.23\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"gri\" -DVERSION=\"2.12.23\" 
-DGRI_IS_BIG_ENDIAN=0 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_UNISTD_H=1 
-DHAVE_LIBNETCDF=1 -DSTDC_HEADERS=1 -DHAVE_LIBREADLINE=1 -DHAVE_ISNAN=1 
-DHAVE_ISINF=1 -DHAVE_ACOSH=1 -DHAVE_GETCWD=1 -DHAVE_POPEN=1 -DHAVE_MKSTEMP=1 
-DHAVE_TMPNAM=1 -DHAVE_TEMPNAM=1 -DHAVE_GETHOSTNAME=1 -DHAVE_ACCESS=1 
-DHAVE_LSTAT=1 -DHAVE_STAT=1 -DHAVE_STRERROR=1 -DHAVE_GETENV=1 -DHAVE_DRAND48=1 
-I.-Wall -DCPLUSPLUSNEW -fno-strength-reduce -I/usr/include -O2 -MT heal.o 
-MD -MP -MF .deps/heal.Tpo -c -o heal.o heal.cc
mv -f .deps/heal.Tpo .deps/heal.Po
g++ -DDEFAULT_GRI_DIR=\"/usr/share/gri/2.12.23/\"  -DPACKAGE_NAME=\"gri\" 
-DPACKAGE_TARNAME=\"gri\" -DPACKAGE_VERSION=\"2.12.23\" -DPACKAGE_STRING=\"gri\ 
2.12.23\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"gri\" -DVERSION=\"2.12.23\" 
-DGRI_IS_BIG_ENDIAN=0 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_UNISTD_H=1 
-DHAVE_LIBNETCDF=1 -DSTDC_HEADERS=1 

Processed: Bug#865938 marked as pending

[Debian Bug Tracking System]

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

> tag 865938 pending
Bug #865938 [src:python-django-bootstrap-form] python-django-bootstrap-form 
FTBFS with Django 1.11
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 873088

[Debian Bug Tracking System]

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

> tags 873088 + upstream fixed-upstream
Bug #873088 {Done: Salvatore Bonaccorso } [git-annex] 
git-annex: remote code execution via crafted SSH URLs (CVE-2017-12976)
Added tag(s) upstream and fixed-upstream.
> thanks
Stopping processing here.

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

Processed: closing 873088

[Debian Bug Tracking System]

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

> close 873088 6.20170818-1
Bug #873088 [git-annex] git-annex: remote code execution via crafted SSH URLs 
(CVE-2017-12976)
Marked as fixed in versions git-annex/6.20170818-1.
Bug #873088 [git-annex] git-annex: remote code execution via crafted SSH URLs 
(CVE-2017-12976)
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#873088: closing 873088

[Salvatore Bonaccorso]

close 873088 6.20170818-1
thanks

Processed: found 873088 in 5.20141125

[Debian Bug Tracking System]

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

> found 873088 5.20141125
Bug #873088 [git-annex] git-annex: remote code execution via crafted SSH URLs 
(CVE-2017-12976)
Marked as found in versions git-annex/5.20141125.
> thanks
Stopping processing here.

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

Bug#873097: glibc: FTBFS on *all* architectures except m68k, powerpcspe, sh4

[Thorsten Glaser]

Source: glibc
Version: 2.24-16
Severity: serious
Justification: fails to build from source (but built successfully in the past)

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

For over three days now, src:glibc is FTBFS’ing virtually everywhere:

amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el,
s390x, alpha, hppa, hurd-i386, kfreebsd-amd64, kfreebsd-i386, powerpc,
ppc64, sparc64, x32 — the list is so long it doesn’t fit into the
bugreport’s Subject.

Causa seems to be something about the expected testsuite failures
having been adjusted in the last upload, which is probably why the
three slow architectures have been spared.

Processed: Re: Bug#871373: kmymoney: FTBFS: CMakeFiles/Makefile2:4181: recipe for target 'kmymoney/dialogs/settings/CMakeFiles/settings_autogen.dir/all' failed

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +fixed-upstream
Bug #871373 [src:kmymoney] kmymoney: FTBFS: CMakeFiles/Makefile2:4181: recipe 
for target 'kmymoney/dialogs/settings/CMakeFiles/settings_autogen.dir/all' 
failed
Added tag(s) fixed-upstream.

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

Bug#871373: kmymoney: FTBFS: CMakeFiles/Makefile2:4181: recipe for target 'kmymoney/dialogs/settings/CMakeFiles/settings_autogen.dir/all' failed

[Dmitry Shachnev]

Control: tags -1 +fixed-upstream

On Mon, Aug 07, 2017 at 11:55:30AM -0400, Lucas Nussbaum wrote:
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
>
> [...]

These two patches from upstream seem to fix the build for me:

1) https://cgit.kde.org/kmymoney.git/commit/?id=b0a68ca075928aa2 — fixes
   “No rule to make target '//kmymoneysettings.h', needed by
   'kmymoney/dialogs/settings/CMakeFiles/settings_autogen'”

2) https://cgit.kde.org/kmymoney.git/commit/?id=6d235f2cd835d5d3 — fixes
   “multiple definition of `sepaStoragePlugin::qt_static_metacall(QObject*,
   QMetaObject::Call, int, void**)'”

--
Dmitry Shachnev

Bug#872402: golang-golang-x-tools-dev: Does not work on mips*

[Martín Ferrari]

On 24/08/17 16:31, Shengjing Zhu wrote:

> Hi Martín,
> So what's the prolem of this x/sys? I didn't see this package has
> disabled tests.

Yes, sorry, I was confused with x/tools, which has disabled tests. This
one does not get built in other arches, so the relevant tests are not
executed.. Maybe we should make it arch:any...?

> Which package ftbfs because of x/sys?

Prometheus and friends were failing. I understood now what you are doing
here (it took me a while), and by passing tags I managed to get them
building again, but that's not a reasonable solution.. The packages
should build out of the box. Can't you add the correct build
restrictions for gccgo so we don't need the tags?

-- 
Martín Ferrari (Tincho)

Processed: Re: Bug#872402: golang-golang-x-tools-dev: Does not work on mips*

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 golang-golang-x-sys-dev: Does not work on mips*
Bug #872402 [golang-golang-x-sys] golang-golang-x-tools-dev: Does not work on 
mips*
Changed Bug title to 'golang-golang-x-sys-dev: Does not work on mips*' from 
'golang-golang-x-tools-dev: Does not work on mips*'.

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

Bug#872402: golang-golang-x-tools-dev: Does not work on mips*

[Shengjing Zhu]

Control: retitle -1 golang-golang-x-sys-dev: Does not work on mips*

Hi Martín,
So what's the prolem of this x/sys? I didn't see this package has
disabled tests.
Which package ftbfs because of x/sys?

On Thu, Aug 17, 2017 at 10:08 PM, Martín Ferrari  wrote:
> reassign 872402 golang-golang-x-sys
> thanks
>
>> Since 0.0~git20170629.0.1b3bb8de-1 a patch has made the source files shipped
>> fail to build in mips* architectures. It does not FTBFS just because tests 
>> have
>> been disabled in a previous version, but it is making other packages FTBFS.
>>
>
> I am being stupid and mixing x/tools with x/sys. Sorry about the noise.
>
> --
> Martín Ferrari (Tincho)
>
> ___
> Pkg-go-maintainers mailing list
> pkg-go-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers



-- 
Best regards,
Shengjing Zhu

Bug#871577: marked as done (nano: fails to upgrade from 'testing' - trying to overwrite /usr/share/info/nano.info.gz)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2017 13:49:24 +
with message-id 
and subject line Bug#871577: fixed in nano 2.8.6-3
has caused the Debian Bug report #871577,
regarding nano: fails to upgrade from 'testing' - trying to overwrite 
/usr/share/info/nano.info.gz
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.)


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

Hi,

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

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

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

  Selecting previously unselected package nano.
  Preparing to unpack .../nano_2.8.6-2_amd64.deb ...
  Unpacking nano (2.8.6-2) ...
  dpkg: error processing archive /var/cache/apt/archives/nano_2.8.6-2_amd64.deb 
(--unpack):
   trying to overwrite '/usr/share/info/nano.info.gz', which is also in package 
nano-tiny 2.8.6-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/nano_2.8.6-2_amd64.deb

This bug is the opposite direction of #869876. Since you obviously moved
a file from nano-tiny to nano, you need corresponding versioned Breaks+Replaces.


cheers,

Andreas


nano-tiny=2.8.6-1_nano=2.8.6-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: nano
Source-Version: 2.8.6-3

We believe that the bug you reported is fixed in the latest version of
nano, 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.
Jordi Mallach  (supplier of updated nano 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: Thu, 24 Aug 2017 14:49:24 +0200
Source: nano
Binary: nano nano-tiny nano-udeb
Architecture: source amd64
Version: 2.8.6-3
Distribution: unstable
Urgency: medium
Maintainer: Jordi Mallach 
Changed-By: Jordi Mallach 
Description:
 nano   - small, friendly text editor inspired by Pico
 nano-tiny  - small, friendly text editor inspired by Pico - tiny build
 nano-udeb  - small, friendly text editor inspired by Pico - udeb (udeb)
Closes: 871577
Changes:
 nano (2.8.6-3) unstable; urgency=medium
 .
   * The "Operació Catalunya" release.
   * Remove Provides: editor to all packages, as this virtual package name
 was removed in November 1996 (even before the first release of TIP!)
   * Add Breaks/Replaces to ease upgrades for the fix in -2 (closes: #871577).
   * Update to Standards-Version 4.1.0.
Checksums-Sha1:
 dedff9916d7a9992da235b7d289cd7a571f83a99 2026 nano_2.8.6-3.dsc
 34e19bc70f2554bfd593a4f0511e77b9f7187f81 28020 nano_2.8.6-3.debian.tar.xz
 a38aa201a013fe12a544c67861577274b045e969 224560 nano-dbgsym_2.8.6-3_amd64.deb
 fe9fa8b6642ac47d802cb92171848030d4c5c25a 99942 
nano-tiny-dbgsym_2.8.6-3_amd64.deb
 cdec5ce85ced8c73cd48b5e90b69f4a986d0b09c 81778 nano-tiny_2.8.6-3_amd64.deb
 6c5f94db446422d79f09026a43d0d25687974ff3 34006 nano-udeb_2.8.6-3_amd64.udeb
 758aaadc7e5c078c7d40c7a0ef1d3f9527293393 6618 nano_2.8.6-3_amd64.buildinfo
 c9f3ea8cf9ff2dff82da11968fb0f60b2206e391 509378 nano_2.8.6-3_amd64.deb
Checksums-Sha256:
 f6b1ff5d5fbd99084b34a7ff56814220aa62903d56ec9f753de8247242bcd554 2026 
nano_2.8.6-3.dsc
 5fc6e05543849508e76a65da677f51e6fb79cee8abd2e4b147728e1fae29bc41 28020 
nano_2.8.6-3.debian.tar.xz
 4dd564124a10f950eb8d435ca8bdafd5fb2c8793e041504a8acff7d770851580 224560 
nano-dbgsym_2.8.6-3_amd64.deb
 e0e31e0e6a190d24bc2f39ab393789098dab6746cd3ef23e4593b3c308f35a23 99942 
nano-tiny-dbgsym_2.8.6-3_amd64.deb
 f9c0ca362e787f5ac9ed92c45952eca912e7175971dca46601922c2794572067 81778 
nano-tiny_2.8.6-3_amd64.deb
 

Bug#873091: missing dependency on libffi-dev

[Sébastien Villemot]

Package: ecl
Version: 15.3.7+dfsg1-2+b1
Severity: serious

Dear Maintainers,

It looks like ecl is missing a dependency on libffi-dev.

For example, with ecl and cl-ppcre installed (but not libffi-dev), the
compilation of cl-ppcre fails:

> (require "asdf")
[…]
> (require "cl-ppcre")
[…]
/usr/bin/ld: cannot find -lffi
collect2: error: ld returned 1 exit status
ASDF could not load cl-ppcre because Error code 1 when executing
(RUN-PROGRAM "gcc" ("-o"

".cache/common-lisp/ecl-15.3.7-unknown-linux-x64/usr/share/common-lisp/source/cl-asdf/build/asdf-TMP.fas"
"-L/usr/lib/" "/tmp/eclinit1NyJ3T.o"

".cache/common-lisp/ecl-15.3.7-unknown-linux-x64/usr/share/common-lisp/source/cl-asdf/build/asdf.o"
"-shared" "-lecl" "-lgmp" "-lgc" "-lffi" "-lpthread" "-ldl"
"-lm")).

Note that there is already a dependency of ecl on libffi6, but this is not 
enough.

Cheers,

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


signature.asc
Description: PGP signature

Bug#871364: marked as done (hol88: FTBFS: Error: ERROR "The default dispatch macro signalled an error.")

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2017 13:34:56 +
with message-id 
and subject line Bug#871364: fixed in hol88 2.02.19940316-34
has caused the Debian Bug report #871364,
regarding hol88: FTBFS: Error: ERROR "The default dispatch macro signalled an 
error."
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.)


-- 
871364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871364
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hol88
Version: 2.02.19940316-33
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[2]: Entering directory '/<>'
> if [ cl = cl ]; then\
>   echo '#+allegro (progn () (set-case-mode :case-insensitive-upper) (setq 
> *cltl1-in-package-compatibility-p* t) (setq 
> comp:*cltl1-compile-file-toplevel-compatibility-p* t) (setq 
> *enable-package-locked-errors* nil))'\
>'(compile-file "lisp/f-cl.l") (quit)'\
>| gcl; else\
>lisp/f-franz; fi
> GCL (GNU Common Lisp)  2.6.12 CLtL1Fri Apr 22 15:51:11 UTC 2016
> Source License: LGPL(gcl,gmp), GPL(unexec,bfd,xgcl)
> Binary License:  GPL due to GPL'ed components: (XGCL READLINE UNEXEC)
> Modifications of this banner must retain notice of a compatible license
> Dedicated to the memory of W. Schelter
> 
> Use (help) to get some basic information on how to use GCL.
> Temporary directory for compiler files:
> /tmp/
> 
> >
> Compiling lisp/f-cl.l.
> ; (SHADOW '(QUIT)) is being compiled.
> ;; Warning: The package operation (SHADOW '(QUIT)) was in a bad place.
> ; (SHADOW '(INCLUDE)) is being compiled.
> ;; Warning: The package operation (SHADOW '(INCLUDE)) was in a bad place.
> ; (SHADOW '(UNTIL WHILE)) is being compiled.
> ;; Warning: The package operation (SHADOW '(UNTIL WHILE)) was in a bad place.
> ; (SHADOW '(MEMQ ASSQ ...)) is being compiled.
> ;; Warning: The package operation (SHADOW '(MEMQ ASSQ DELQ PUTPROP)) was in a 
> bad place.
> ; (DEFUN SET-FASL-FLAG ...) is being compiled.
> ;; The variable |%print_fasl-flag| is undefined.
> ;; The compiler will assume this variable is a global.
> End of Pass 1.  
> End of Pass 2.  
> OPTIMIZE levels: Safety=0 (No runtime error checking), Space=0, Speed=3
> Finished compiling /<>/lisp/f-cl.o.
> #p"/<>/lisp/f-cl.o"
> 
> >if [ cl = cl ]; then\
>   echo '#+allegro (progn () (set-case-mode :case-insensitive-upper) (setq 
> *cltl1-in-package-compatibility-p* t) (setq 
> comp:*cltl1-compile-file-toplevel-compatibility-p* t) (setq 
> *enable-package-locked-errors* nil))'\
>'(load "lisp/f-cl") (compile-file "lisp/f-macro.l") (quit)'\
>| gcl; else\
>lisp/f-macro; fi
> GCL (GNU Common Lisp)  2.6.12 CLtL1Fri Apr 22 15:51:11 UTC 2016
> Source License: LGPL(gcl,gmp), GPL(unexec,bfd,xgcl)
> Binary License:  GPL due to GPL'ed components: (XGCL READLINE UNEXEC)
> Modifications of this banner must retain notice of a compatible license
> Dedicated to the memory of W. Schelter
> 
> Use (help) to get some basic information on how to use GCL.
> Temporary directory for compiler files:
> /tmp/
> 
> >;; Loading "lisp/f-cl"
> start address -T 0xcd2e40 ;; Finished loading "lisp/f-cl"
> 21224
> 
> >
> Compiling lisp/f-macro.l.
> ; (DEFUN EXISTS ...) is being compiled.
> ;; Warning: The variable IGNORE is not used.
> ; (DEFUN FORALL ...) is being compiled.
> ;; Warning: The variable IGNORE is not used.
> End of Pass 1.  
> End of Pass 2.  
> OPTIMIZE levels: Safety=0 (No runtime error checking), Space=0, Speed=3
> Finished compiling /<>/lisp/f-macro.o.
> #p"/<>/lisp/f-macro.o"
> 
> >if [ cl = cl ]; then\
>   echo '#+allegro (progn () (set-case-mode :case-insensitive-upper) (setq 
> *cltl1-in-package-compatibility-p* t) (setq 
> comp:*cltl1-compile-file-toplevel-compatibility-p* t) (setq 
> *enable-package-locked-errors* nil))'\
>'(load "lisp/f-cl") (compile-file "lisp/f-system.l") (quit)'\
>| gcl; else\
>lisp/f-system; fi
> GCL (GNU Common Lisp)  2.6.12 CLtL1Fri Apr 22 15:51:11 UTC 2016
> Source License: LGPL(gcl,gmp), GPL(unexec,bfd,xgcl)
> Binary License:  GPL due to GPL'ed components: (XGCL READLINE UNEXEC)
> Modifications of this banner must retain notice of a compatible license
> Dedicated to the memory of W. Schelter
> 
> Use (help) to get some basic information on how to use GCL.
> Temporary directory for compiler files:
> /tmp/
> 
> >;; Loading "lisp/f-cl"
> start address -T 0xcd2e40 ;; Finished 

Bug#871963: marked as done (birdfont: Build-Depends on libwebkitgtk-dev which is deprecated)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2017 13:34:23 +
with message-id 
and subject line Bug#871963: fixed in birdfont 2.19.4-1
has caused the Debian Bug report #871963,
regarding birdfont: Build-Depends on libwebkitgtk-dev which is deprecated
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.)


-- 
871963: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871963
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: birdfont
Severity: serious
Version: 2.19.0-1
Tags: sid buster
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs libwebkitgtk-3.0-0 webkit1

Hi,

birdfont Build-Depends on libwebkitgtk-dev, which is deprecated in favor of
libwebkit2gtk-4.0-dev (provided in Debian by webkit2gtk). Please drop
this Build-Depends so that we can remove the old, unmaintained one.
(Note that birdfont already Build-Depends on the new webkitgtk).

Please try to do soon as we're going to try to remove the old webkitgtk soon.

I am filing this bug as "serious" since the old webkitgtk will not be
available in the next major stable release of Debian (codenamed
"buster").

If you have any question don't hesitate to ask.

On behalf of the Debian WebKit Maintainers,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: birdfont
Source-Version: 2.19.4-1

We believe that the bug you reported is fixed in the latest version of
birdfont, 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.
Hideki Yamane  (supplier of updated birdfont 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: Thu, 24 Aug 2017 07:34:40 +0900
Source: birdfont
Binary: birdfont
Architecture: source amd64
Version: 2.19.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Fonts Task Force 
Changed-By: Hideki Yamane 
Description:
 birdfont   - font editor that lets you create outline vector graphics and expo
Closes: 871963
Changes:
 birdfont (2.19.4-1) unstable; urgency=medium
 .
   * New upstream release
   * debian/control
 - drop libwebkitgtk-dev (Closes: #871963)
   Thanks to Jeremy Bicha  for the report and patch
 - adjust doit3 version
 - set Standards-Version: 4.1.0
   * debian/rules
 - fix FTBFS with newer python3-doit package.
   Thanks to Jeremy Bicha  for the patch
   * debian/patches
 - add 0002-update-AppStream-metadata.patch and
   0003-update-appstream-data-location.patch
   * debian/gbp.conf
 - remove lintian exec since not sure to ignore lintian error
   "orig-tarball-missing-upstream-signature"...
Checksums-Sha1:
 3e805ba5cf3fbc304d63cf72779f846c13f1438a 2139 birdfont_2.19.4-1.dsc
 e99e081299031ac58654094187500a6f0efa0a46 2337040 birdfont_2.19.4.orig.tar.xz
 40850f890dfcc784cc35af550a390cdfa6cb3018 11184 birdfont_2.19.4-1.debian.tar.xz
 f42e8d2bcec646209fd1607aca6b7be360197d4a 108800 
birdfont-dbgsym_2.19.4-1_amd64.deb
 4026749f08d4b08f6d6bd16d0ba9f37bf697b6bf 14686 
birdfont_2.19.4-1_amd64.buildinfo
 4de273ce343af7ef390affa19c8a7dd6a05fc4e1 2981998 birdfont_2.19.4-1_amd64.deb
Checksums-Sha256:
 7b0841a3b2589de95bf47f4fc7d55217c588bb02277b8a0950d1763955db75b4 2139 
birdfont_2.19.4-1.dsc
 0ebe8500a03c3f97f16f650a314f0b264fb4c08b36bea598ef79c55ece9b41e0 2337040 
birdfont_2.19.4.orig.tar.xz
 678e6b28cf2006fc9f5aa6035679cc55f2dad568d9f89b8dcb4d345a23cd26a4 11184 
birdfont_2.19.4-1.debian.tar.xz
 025496d8eec6eaea824fab3afcb304d064f37daf1895a6b16ed61a0ad71630b3 108800 
birdfont-dbgsym_2.19.4-1_amd64.deb
 2e48b61ded83c35aac311025fd04f507bfb7522158faf6de40872898eef35b5e 14686 
birdfont_2.19.4-1_amd64.buildinfo
 70c1ee1954c93ce0f5bea80a19bb50205792242fe6b250bd5156d2f5b7cce2ca 2981998 
birdfont_2.19.4-1_amd64.deb
Files:
 0279dc831897bfd1c1da54c6fb1ad29f 2139 fonts extra birdfont_2.19.4-1.dsc
 e2194d3bf619afb3392626b3c749cbab 2337040 fonts extra 
birdfont_2.19.4.orig.tar.xz
 d264e177d4cb2a13e03bbacabe3a28d7 11184 fonts extra 
birdfont_2.19.4-1.debian.tar.xz
 

Bug#848024: Fails to connect after upgrade to openvpn 2.4

[Artur Linhart]

Package: network-manager-openvpn
Version: 1.2.8-2
Followup-For: Bug #848024

The bug is still there in the version 1.2.8-2, because the g|UI for the editing
of connection properties still generates the invalid option "tls-remote" always
if you want to specify the X509 properties.

The problem is concretely in the openvpn configuration, tab VPN (openvpn), then
click on "Advanced", then switch to the tab TLS settings.
As a first control on this tab is the edit field, where you can put the
identification for X509 validation
(somethng like "C=cz, L=Praha, O=Some Org, CN=someserver.somedomain.cz,
emailAddress=somaeddr...@somedomain.cz")

But now, instead of the generating openvpn configuration with the option
"verify-X509-name" - on the ovpn configuration should be the line with
something like

verify-x509-name "C=cz, L=Praha, O=Some Org, CN=someserver.somedomain.cz,
emailAddress=someaddr...@somedomain.cz"

it still generates the old obsolete form

tls-remote "C=cz, L=Praha, O=Some Org, CN=someserver.somedomain.cz,
emailAddress=someaddr...@somedomain.cz"

The only workaround for this I have found is to let the validation field empty,
but then you lose the validation possibility.

This should be fixed, there should be generated the correct settings
verify-x509-name
to the generated ovpn configuration instead of todays
tls-remote

Possibly there should be also extended the edit dialogue, where should be
specified the type parameter behind the name parameter of the tag
verify-x509-name - according to the openvpn manual, there can be also specified
the type of the X509 name, if omitted, then default is used.



-- 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-0.bpo.3-amd64 (SMP w/2 CPU cores)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8), 
LANGUAGE=cs:en_US:de (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages network-manager-openvpn depends on:
ii  adduser  3.115
ii  libc62.24-11+deb9u1
ii  libglib2.0-0 2.50.3-2
ii  libnm0   1.6.2-3
ii  network-manager  1.6.2-3
ii  openvpn  2.4.0-6+deb9u1

network-manager-openvpn recommends no packages.

network-manager-openvpn suggests no packages.

-- no debconf information

Bug#868922: marked as done (r-cran-randomfieldsutils: FTBFS: init_RandomFieldsUtils.cc:62:10: error: 'R_NativeArgStyle' does not name a type)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2017 13:21:20 +
with message-id 
and subject line Bug#868922: fixed in r-cran-randomfieldsutils 0.3.25-1
has caused the Debian Bug report #868922,
regarding r-cran-randomfieldsutils: FTBFS: init_RandomFieldsUtils.cc:62:10: 
error: 'R_NativeArgStyle' does not name a type
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.)


-- 
868922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868922
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-randomfieldsutils
Version: 0.3.15-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> g++  -I/usr/share/R/include -DNDEBUG -fopenmp  -fpic  -g -O2 
> -fdebug-prefix-map=/build/r-base-3.4.1=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g  -c 
> init_RandomFieldsUtils.cc -o init_RandomFieldsUtils.o
> init_RandomFieldsUtils.cc:62:10: error: 'R_NativeArgStyle' does not name a 
> type
>static R_NativeArgStyle argin[] = {R_ARG_IN},
>   ^~~~
> init_RandomFieldsUtils.cc:62:47: error: expected unqualified-id before ',' 
> token
>static R_NativeArgStyle argin[] = {R_ARG_IN},
>^
> init_RandomFieldsUtils.cc:63:14: error: expected constructor, destructor, or 
> type conversion before '=' token
>  argout[] = {R_ARG_OUT},
>   ^
> init_RandomFieldsUtils.cc:63:27: error: expected unqualified-id before ',' 
> token
>  argout[] = {R_ARG_OUT},
>^
> init_RandomFieldsUtils.cc:64:15: error: expected constructor, destructor, or 
> type conversion before '=' token
>  hostarg[] = {R_ARG_OUT, R_ARG_OUT};
>^
> init_RandomFieldsUtils.cc:66:72: error: 'argin' was not declared in this scope
>{"RelaxUnknownRFoption", (DL_FUNC) , 1, 
> Relax_t,argin}, {"sleepMilli", (DL_FUNC) , 1, int_arg, argin},
> ^
> init_RandomFieldsUtils.cc:66:130: error: 'argin' was not declared in this 
> scope
>{"RelaxUnknownRFoption", (DL_FUNC) , 1, 
> Relax_t,argin}, {"sleepMilli", (DL_FUNC) , 1, int_arg, argin},
>   
> ^
> init_RandomFieldsUtils.cc:67:52: error: 'argin' was not declared in this scope
>   {"sleepMicro", (DL_FUNC) , 1, int_arg, argin},
> ^
> init_RandomFieldsUtils.cc:68:38: error: 'argout' was not declared in this 
> scope
>   {"pid", (DL_FUNC) , 1, int_arg, argout},
>   ^~
> init_RandomFieldsUtils.cc:69:49: error: 'hostarg' was not declared in this 
> scope
>   {"hostname", (DL_FUNC) , 2, host_arg, hostarg},
>  ^~~
> init_RandomFieldsUtils.cc:73:1: error: too many initializers for 'const 
> R_CMethodDef'
>  };
>  ^
> init_RandomFieldsUtils.cc:73:1: error: too many initializers for 'const 
> R_CMethodDef'
> init_RandomFieldsUtils.cc:73:1: error: too many initializers for 'const 
> R_CMethodDef'
> init_RandomFieldsUtils.cc:73:1: error: too many initializers for 'const 
> R_CMethodDef'
> init_RandomFieldsUtils.cc:73:1: error: too many initializers for 'const 
> R_CMethodDef'
> init_RandomFieldsUtils.cc:73:1: error: too many initializers for 'const 
> R_CMethodDef'
> /usr/lib/R/etc/Makeconf:166: recipe for target 'init_RandomFieldsUtils.o' 
> failed
> make[1]: *** [init_RandomFieldsUtils.o] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/2017/07/19/r-cran-randomfieldsutils_0.3.15-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: r-cran-randomfieldsutils
Source-Version: 0.3.25-1

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

A summary of the changes between this version 

Bug#873088: git-annex: remote code execution via crafted SSH URLs (CVE-2017-12976)

[Antoine Beaupre]

Package: git-annex
X-Debbugs-CC: t...@security.debian.org 
secure-testing-t...@lists.alioth.debian.org
Severity: grave
Tags: security

Hi,

the following vulnerability was published for git-annex.

CVE-2017-12976[0]:
| git-annex before 6.20170818 allows remote attackers to execute
| arbitrary commands via an ssh URL with an initial dash character in the
| hostname, as demonstrated by an ssh://-eProxyCommand= URL, a related
| issue to CVE-2017-9800, CVE-2017-12836, CVE-2017-1000116, and
| CVE-2017-1000117.

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-12976
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12976

Please adjust the affected versions in the BTS as needed.


signature.asc
Description: PGP signature

Bug#872180: marked as done (kraken builds for all archs, but depends on amd64-only package)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2017 12:34:42 +
with message-id 
and subject line Bug#872180: fixed in kraken 0.10.5~beta-5
has caused the Debian Bug report #872180,
regarding kraken builds for all archs, but depends on amd64-only package
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.)


-- 
872180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872180
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kraken
Version: 0.10.5~beta-4
Severity: serious

Hi folks,

As of version 0.10.5~beta-3, kraken now declares a dependency on jellyfish
(specifically, jellyfish1).  However, kraken builds for all architectures,
but jellyfish and jellyfish1 are available only on amd64.  This makes the
built kraken packages uninstallable on all architectures except for amd64,
and will block the updated package from reaching Debian testing.

There are three ways that this can be resolved:

 - if jellyfish can be built for all archs, its debian/control should be
   fixed to be Architecture: any instead of Architecture: any-amd64.
 - if you know jellyfish will never be portable to other architectures, you
   can update kraken to also list itself as Architecture: any-amd64.
 - if you know jellyfish won't be built for all archs now, but aren't sure
   if it would be built for other architectures later, you can add jellyfish
   as a build-dependency to kraken so that it will not be built on
   architectures where it won't be installable.

At a glance, I see that jellyfish uses x86 assembly, so probably one of the
last two options is appropriate here.

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


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: kraken
Source-Version: 0.10.5~beta-5

We believe that the bug you reported is fixed in the latest version of
kraken, 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.
Andreas Tille  (supplier of updated kraken package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 24 Aug 2017 14:16:48 +0200
Source: kraken
Binary: kraken
Architecture: source amd64
Version: 0.10.5~beta-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 kraken - assigning taxonomic labels to short DNA sequences
Closes: 872180
Changes:
 kraken (0.10.5~beta-5) unstable; urgency=medium
 .
   * Architecture: any-amd64
 Closes: #872180
   * cme fix dpkg-control
   * really do not read d/changelog
Checksums-Sha1:
 5bec785304994b849143169d1b077bd4ab2441ff 2010 kraken_0.10.5~beta-5.dsc
 3312da2e8e06326e959e69ea3d307d237f918762 336244 
kraken_0.10.5~beta-5.debian.tar.xz
 3ddccafc7b72cff7c03ed718aeca2c9907492b1f 11880 
kraken-dbgsym_0.10.5~beta-5_amd64.deb
 690c5a1e1579e1127da78aedda454fbf45676369 5637 
kraken_0.10.5~beta-5_amd64.buildinfo
 bffc79d99571837ddf526c25aadf8fbbb13e5bba 737640 kraken_0.10.5~beta-5_amd64.deb
Checksums-Sha256:
 4ea6f969ef80e819f3a1708be123e4b53165565d138116f97d6076a816df50ff 2010 
kraken_0.10.5~beta-5.dsc
 b2c0038d14b317000783d120ea1ac98eeea67be0791a6c586c08a0348fab7f1b 336244 
kraken_0.10.5~beta-5.debian.tar.xz
 104ef549dffd5b201daaefdcf4b81a6c973642b31ba7c6392f61b9f23342fbd1 11880 
kraken-dbgsym_0.10.5~beta-5_amd64.deb
 90498bc6fba0bbdea07ed9e37ef2b6d6cedd55c066abc7c6abfe582c00d0d649 5637 
kraken_0.10.5~beta-5_amd64.buildinfo
 0838b336c1eca375b8c16ac83f351e3fc786743b1bda0b415e49816d32a4 737640 
kraken_0.10.5~beta-5_amd64.deb
Files:
 6220aa41e58096663188c38872bc2366 2010 science optional kraken_0.10.5~beta-5.dsc
 11af3c4c9a14e3709ce62a1bd9264c86 336244 science optional 
kraken_0.10.5~beta-5.debian.tar.xz
 076c4745d3460b03e96d81f696ce6522 11880 

Bug#873008: hfst FTBFS on big endian: FAIL: test

[Tino Didriksen]

That's my bad. In the confusion of bugs #824119 and #827199 , I forgot to
re-disable tests for hfst.

-- Tino Didriksen


On 23 August 2017 at 18:38, Adrian Bunk  wrote:

> Source: hfst
> Version: 3.12.2~r3289-1
> Severity: serious
>
> https://buildd.debian.org/status/package.php?p=hfst=sid
>

Bug#873085: bsd-finger does not trap errors from ./configure

[Helmut Grohne]

Source: bsd-finger
Version: 0.17-15.1
Severity: serious
Justification: policy 4.6
User: helm...@debian.org
Usertags: rebootstrap

The debian policy section 4.6 requires that when build commands fail,
the build should abort. In case bsd-finger's ./configure aborts, the
error is ignored and the build attempts to continue potentially
resulting in a broken package. Adding "set -e; " (as suggested by the
policy) before the conditional fixes this issue.

Helmut

Bug#826438: marked as done (libtm-perl: FTBFS: Unimplemented: POSIX::tmpnam():)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2017 11:19:24 +
with message-id 
and subject line Bug#826438: fixed in libtm-perl 1.56-8
has caused the Debian Bug report #826438,
regarding libtm-perl: FTBFS: Unimplemented: POSIX::tmpnam():
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.)


-- 
826438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826438
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libtm-perl
Version: 1.56-7
Severity: minor
User: debian-p...@lists.debian.org
Usertags: perl-5.24-transition

Building this package triggers a deprecation warning with Perl 5.24
(currently in experimental):

  Calling POSIX::tmpnam() is deprecated at t/095tau.t line 88.
  t/095tau.t . ok
  Calling POSIX::tmpnam() is deprecated at t/096taumapsphere.t line 76.
  Calling POSIX::tmpnam() is deprecated at t/096taumapsphere.t line 77.
  t/096taumapsphere.t  ok
  t/100mapsphere.t ... ok
  Calling POSIX::tmpnam() is deprecated at t/101mapsphere.t line 27.
  t/101mapsphere.t ... ok

A full build log is available at
  http://perl.debian.net/rebuild-logs/perl-5.24-throwaway/libtm-perl_1.56-7/

-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: libtm-perl
Source-Version: 1.56-8

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

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

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

Debian distribution maintenance software
pp.
Alexander Zangerl  (supplier of updated libtm-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 24 Aug 2017 20:55:19 +1000
Source: libtm-perl
Binary: libtm-perl
Architecture: source all
Version: 1.56-8
Distribution: unstable
Urgency: medium
Maintainer: Alexander Zangerl 
Changed-By: Alexander Zangerl 
Description:
 libtm-perl - Perl modules for reading/writing Topic Maps
Closes: 826438
Changes:
 libtm-perl (1.56-8) unstable; urgency=medium
 .
   * get rid of POSIX::tmpnam (closes: #826438)
   * lifted standards version
Checksums-Sha1:
 d5d1552f3483dd97d4640ed7ad846fb3dbd78fc0 2167 libtm-perl_1.56-8.dsc
 4aaa39d2aeca9c510222bc298990192620ae94d3 30976 libtm-perl_1.56-8.debian.tar.xz
 8678cf26f95093da8f3352721a2938e8ddfa0135 335486 libtm-perl_1.56-8_all.deb
Checksums-Sha256:
 e76de9b266267df141f3b0aecd3a711cb9c15da17de882eeb89a1a8c0c1aa6e5 2167 
libtm-perl_1.56-8.dsc
 84672f5abce0a14a5d4e15a5354285064566005bda57845734faac0afa9f2b4e 30976 
libtm-perl_1.56-8.debian.tar.xz
 71b98314bbd6bca6d286edc44c03405c4afeee36b68fd28c361851807f91b0cb 335486 
libtm-perl_1.56-8_all.deb
Files:
 2e17309d68bdb9bc6e5a6e8eaf1b417b 2167 perl extra libtm-perl_1.56-8.dsc
 60a5b89c46fe11c29e2294570aeb2821 30976 perl extra 
libtm-perl_1.56-8.debian.tar.xz
 0cd9ef6d0a82a06b8c9a243d71c28274 335486 perl extra libtm-perl_1.56-8_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJZnrWmAAoJED06g4g30PqNwecP/3NBjmuzSWZwn96zs8i/BsuG
76b3WkEsLhz1KYK2CBqIOR5mpv6krhYg+69lSiIRFJt2+0SkhgoCvELncYT1fDtA
2wsfnZAWZals7YYxkxH4eY3JtXGpnpR2IF2voqTjKL1ACNddy/2p2oxxh1zlI3js
KB/BB1pjnB1QqXjgLuihZrnX1hr5z/h6tLAkb+hkQ6qibHXB3za0s69gsRa9o8Pq
yZytL2fR30x4OVQg9HyDF4OdTl4sdXwrz36y7jAQpAIVhu6eo0PVmW9Q0dZdRAP6
GwWyJCNjfstVVFN1E1k9jHeUKdLfF5Gj57nBXGpmYmAe/f3hqC5slC6R7cJDSGST
BRFGFL6wpmoaSrYDNyxT4eBCytGTdNAy7U6/X1XUNPM2x11DRHuZxxlWYXO7Zeiw
2x5646afjcXq1rU89h1aMZMnwIY2JU+0x0QWUxMWIOcmwukJkhn351/s7/Wqvaym
IXSyqnDqLqODJEfqnBP/I95HK0tNP6sE5JaWjsErAgYXqrMxuh8J0yt0L6YW6iRE
eFGtsc/p/KpTdualnsd5iraVShHzxp7ksGMxHP2G2124bdBxhco2STzALm6dMIt2
gPIuQRVdMCb+hRMQ2KbQUTxyPmTqlNjXrs1es7DCgtrgouYD3tu3BE1v3xvGE516
iZnYx/EZiK7y1F8MSIvH
=fw2x
-END PGP SIGNATURE End Message ---

Bug#872979: marked as done (389-ds-base FTBFS: configure.ac:76: error: possibly undefined macro: LT_LIB_DLLOAD)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2017 10:34:11 +
with message-id 
and subject line Bug#872979: fixed in 389-ds-base 1.3.6.7-2
has caused the Debian Bug report #872979,
regarding 389-ds-base FTBFS: configure.ac:76: error: possibly undefined macro: 
LT_LIB_DLLOAD
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.)


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

https://buildd.debian.org/status/package.php?p=389-ds-base=sid

...
   dh_autoreconf -a -O--parallel -O--builddir=build/
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac,
libtoolize: and rerunning libtoolize and aclocal.
configure.ac:76: error: possibly undefined macro: LT_LIB_DLLOAD
  If this token and others are legitimate, please use m4_pattern_allow.
  See the Autoconf documentation.
autoreconf: /usr/bin/autoconf failed with exit status: 1
dh_autoreconf: autoreconf -f -i returned exit code 1
debian/rules:50: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
--- End Message ---
--- Begin Message ---
Source: 389-ds-base
Source-Version: 1.3.6.7-2

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

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

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated 389-ds-base package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 24 Aug 2017 12:15:03 +0300
Source: 389-ds-base
Binary: 389-ds 389-ds-base-libs 389-ds-base-dev 389-ds-base
Architecture: source
Version: 1.3.6.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian 389ds Team 

Changed-By: Timo Aaltonen 
Description:
 389-ds - 389 Directory Server suite - metapackage
 389-ds-base - 389 Directory Server suite - server
 389-ds-base-dev - 389 Directory Server suite - development files
 389-ds-base-libs - 389 Directory Server suite - libraries
Closes: 872979
Changes:
 389-ds-base (1.3.6.7-2) unstable; urgency=medium
 .
   * control: Bump policy to 4.1.0, no changes.
   * rules: Override dh_missing.
   * control: Add libltdl-dev to build-depends. (Closes: #872979)
Checksums-Sha1:
 d2d062f12be7ac6d117ee6e03cc3dd593c044ace 2563 389-ds-base_1.3.6.7-2.dsc
 08592c7efdc5d2210370fc2f21018b3a09e8edf5 20008 
389-ds-base_1.3.6.7-2.debian.tar.xz
Checksums-Sha256:
 92aada07c5c82d6898af6e77eda306df7be21dc3f6a7e3c04b97c987da2e1fc6 2563 
389-ds-base_1.3.6.7-2.dsc
 a32ae62ff75bb05fcb89f19dd5e05336a8310f0eda35f4e51c22425d16e970c7 20008 
389-ds-base_1.3.6.7-2.debian.tar.xz
Files:
 4c3d1a2852725058ebe72da63f64ed4e 2563 net optional 389-ds-base_1.3.6.7-2.dsc
 fa20d211da8aa7da9f172ba46bd5e5b5 20008 net optional 
389-ds-base_1.3.6.7-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJZnpkjAAoJEMtwMWWoiYTcqVoP/0voNDrFOZ3aGDiBJYcpXdx/
h6p5hVfttwqF/Uaiq+Vz/j7/hhzfchjAdNDz+mpKd6TyYQ8Mv6fGh/6YjN0932R3
NYuGy347tgKhPsFzDpyB7R51LOFForONXcconQbnCuHFl8ihnI/BbcNS1F8BzTBs
gVQn7ApVJKnZlJ60KJ+JyDf0FaagMuiKYxad7hpdcVqjtcesT3VUV2FqIbu3GRdI
IwPyTbehpzyDXR9jDrYFqk0QrDlD4mY8xpXQH6/gx8o7PkEOby7lClMn2/4QdeBV
irGn3qX/KXQkMn3xxmjM58C50C9Qo63dJYEu8U9g5XG68PnkSmJ8GTDZf7mwv0Kr
WXruvjgN1PhsjQdEEoKIwfqebLsibSYsZAiXbr8HC+wdTZR/UVtlcgpJZgQg6vQT
Y2qJB5eSiizYE7pdw9DStnii7d/wq8mCrGrLE6lKAsjx+ywN6d4CZ/fuoVB5eyU8
Sze7GwihAqpCenbwWoihOKWceFB4Rffq76U6En19wv6wiwoVPfwudqc0Q10jSf8Q
sAB7Mtx/d/lP9H4mN8QnnnSwD+tQIcgXFR+fheZ+vW0nHURO4GFvTfonIjtbVz9R
BkmXCNf9rF6IqB5P99gIlCuQAnvB1JJOb5wr5eZW3W3SIAL2fnLTwXn8WKEyCJbc
g6anxOm220/xB28/Xeb0
=JkqT
-END PGP SIGNATURE End Message ---

Bug#872881: simgrid: FTBFS: `__atomic_fetch_add_8' undefined

[James Cowgill]

Hi,

On 24/08/17 08:59, Martin Quinson wrote:
> Hello,
> 
> thanks for the patch. I came to something very similar, only
> protecting it to be used only by GCC. I was waiting to find the time
> to test it before upload, but if you tested, I'll upload it right away.

I have tested the patch I attached on a mips machine. If you want I
could test your alternative patch as well.

Thanks,
James

> On Wed, Aug 23, 2017 at 02:41:15PM +0100, James Cowgill wrote:
>> Hi,
>>
>> The attached patch seems to work (ie replace atomic-library with it).
>> Using target_link_libraries should put any linker arguments at the end
>> instead of the beginning.
>>
>> Thanks,
>> James
> 
>> --- a/tools/cmake/MakeLib.cmake
>> +++ b/tools/cmake/MakeLib.cmake
>> @@ -114,6 +114,7 @@ if(enable_smpi AND APPLE)
>>set(SIMGRID_DEP "${SIMGRID_DEP} -Wl,-U -Wl,_smpi_simulated_main")
>>  endif()
>>  
>> +set(SIMGRID_DEP "${SIMGRID_DEP} -Wl,--as-needed -latomic 
>> -Wl,--no-as-needed")
>>  target_link_libraries(simgrid   ${SIMGRID_DEP})
>>  
>>  # Dependencies from maintainer mode



signature.asc
Description: OpenPGP digital signature

Bug#873079: unattended-upgrades FTBFS: test failures

[Adrian Bunk]

Source: unattended-upgrades
Version: 0.95
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=unattended-upgrades=all=0.95=1503510785=0

...
Running ./test_remove_unused.py with python3
/<>/test/unattended_upgrade.py:1254: ResourceWarning: unclosed 
file <_io.TextIOWrapper name=7 mode='r' encoding='ANSI_X3.4-1968'>
  res, error = cache_commit(cache, logfile_dpkg, verbose)
/<>/test/unattended_upgrade.py:1254: ResourceWarning: unclosed 
file <_io.TextIOWrapper name=8 mode='w' encoding='ANSI_X3.4-1968'>
  res, error = cache_commit(cache, logfile_dpkg, verbose)
FF
==
FAIL: test_remove_unused_dependencies (__main__.TestRemoveUnused)
--
Traceback (most recent call last):
  File "./test_remove_unused.py", line 105, in test_remove_unused_dependencies
"Can not find '%s' in '%s'" % (needle, haystack))
AssertionError: False is not true : Can not find 'Packages that are auto 
removed: 'old-unused-dependency test-package-dependency'' in '2017-08-23 
17:53:00,093 INFO Initial blacklisted packages: 
2017-08-23 17:53:00,094 INFO Initial whitelisted packages: 
2017-08-23 17:53:00,094 INFO Starting unattended upgrades script
2017-08-23 17:53:00,094 INFO Allowed origins are: ['o=Ubuntu,a=lucid-security']
2017-08-23 17:53:00,149 INFO Packages that will be upgraded: 
2017-08-23 17:53:00,171 INFO Packages that are auto removed: 
'old-unused-dependency'
2017-08-23 17:53:00,470 INFO Packages were successfully auto-removed
'

==
FAIL: test_remove_unused_dependencies_new_unused_only 
(__main__.TestRemoveUnused)
--
Traceback (most recent call last):
  File "./test_remove_unused.py", line 127, in 
test_remove_unused_dependencies_new_unused_only
"Can not find '%s' in '%s'" % (needle, haystack))
AssertionError: False is not true : Can not find 'Packages that are auto 
removed: 'test-package-dependency'' in '2017-08-23 17:53:00,481 INFO Initial 
blacklisted packages: 
2017-08-23 17:53:00,481 INFO Initial whitelisted packages: 
2017-08-23 17:53:00,481 INFO Starting unattended upgrades script
2017-08-23 17:53:00,481 INFO Allowed origins are: ['o=Ubuntu,a=lucid-security']
2017-08-23 17:53:00,504 INFO No packages found that can be upgraded unattended 
and no pending auto-removals
'

--
Ran 2 tests in 0.422s

FAILED (failures=2)
Makefile:6: recipe for target 'check' failed
make[2]: *** [check] Error 1
make[2]: Leaving directory '/<>/test'
debian/rules:15: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 2

Processed: Not a problem in stretch

[Debian Bug Tracking System]

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

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

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

Bug#873078: kwin FTBFS with Qt 5.9.1

[Adrian Bunk]

Source: kwin
Version: 4:5.8.7-1
Severity: serious

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

...
CMake Error at 
/usr/share/cmake-3.9/Modules/FindPackageHandleStandardArgs.cmake:137 (message):
  Could NOT find Qt5PlatformSupport (missing: Qt5PlatformSupport_LIBRARY
  Qt5PlatformSupport_INCLUDE_DIR) (found version "5.9.1")
Call Stack (most recent call first):
  /usr/share/cmake-3.9/Modules/FindPackageHandleStandardArgs.cmake:377 
(_FPHSA_FAILURE_MESSAGE)
  cmake/modules/FindQt5PlatformSupport.cmake:89 
(find_package_handle_standard_args)
  CMakeLists.txt:245 (find_package)


-- Configuring incomplete, errors occurred!

Bug#872317: marked as done (libgtk2-perl FTBFS: GtkTextIter test failures)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2017 09:35:21 +
with message-id 
and subject line Bug#872317: fixed in pango1.0 1.40.11-1
has caused the Debian Bug report #872317,
regarding libgtk2-perl FTBFS: GtkTextIter test failures
to be marked as done.

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

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


-- 
872317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872317
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgtk2-perl
Version: 2:1.24992-1
Severity: serious

Some recent change in unstable makes libgtk2-perl FTBFS:

https://tests.reproducible-builds.org/debian/history/libgtk2-perl.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libgtk2-perl.html

...
#   Failed test at t/GtkTextIter.t line 155.

#   Failed test at t/GtkTextIter.t line 157.
# Looks like you failed 2 tests of 93.
t/GtkTextIter.t  
1..93
ok 1 - An object of class 'Gtk2::TextIter' isa 'Gtk2::TextIter'
ok 2
ok 3
ok 4
ok 5
ok 6
ok 7
ok 8
ok 9
ok 10
ok 11
ok 12
ok 13
ok 14
ok 15
ok 16
ok 17
ok 18
ok 19
ok 20
ok 21
ok 22 - An object of class 'Pango::Language' isa 'Gtk2::Pango::Language'
ok 23
ok 24
ok 25
ok 26
ok 27
ok 28
ok 29
ok 30
ok 31
ok 32
ok 33
ok 34
ok 35
ok 36 - search forward
ok 37 - from
ok 38 - to
ok 39 - search backward
ok 40 - from
ok 41 - to
ok 42 - 'match start' isa 'Gtk2::TextIter'
ok 43 - 'match end' isa 'Gtk2::TextIter'
ok 44 - found string match forward
ok 45 - found string match forward
ok 46 - found string match forward
ok 47 - found string match forward
ok 48 - match start offset
ok 49 - match end offset
ok 50 - 'match start' isa 'Gtk2::TextIter'
ok 51 - 'match end' isa 'Gtk2::TextIter'
ok 52 - found string match backward
ok 53 - match start offset
ok 54 - match end offset
ok 55
ok 56
ok 57
ok 58
ok 59
ok 60
ok 61
ok 62
ok 63
ok 64
ok 65
ok 66
not ok 67
ok 68
not ok 69
ok 70
ok 71
ok 72
ok 73
ok 74
ok 75
ok 76
ok 77
ok 78
ok 79
ok 80
ok 81
ok 82
ok 83
ok 84
ok 85
ok 86
ok 87
ok 88
ok 89
ok 90
ok 91
ok 92
ok 93
Dubious, test returned 2 (wstat 512, 0x200)
Failed 2/93 subtests
...
Test Summary Report
---
t/GtkTextIter.t  (Wstat: 512 Tests: 93 Failed: 2)
  Failed tests:  67, 69
  Non-zero exit status: 2
Files=228, Tests=5063, 45 wallclock secs ( 1.32 usr  0.43 sys + 31.86 cusr  
5.44 csys = 39.05 CPU)
Result: FAIL
Failed 1/228 test programs. 2/5063 subtests failed.
Makefile:3675: recipe for target 'test_dynamic' failed
make[2]: *** [test_dynamic] Error 255
make[2]: Leaving directory '/build/1st/libgtk2-perl-1.24992'
dh_auto_test: make -j16 test TEST_VERBOSE=1 returned exit code 2
debian/rules:24: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 2
--- End Message ---
--- Begin Message ---
Source: pango1.0
Source-Version: 1.40.11-1

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

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

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated pango1.0 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 16 Aug 2017 09:46:11 -0400
Source: pango1.0
Binary: libpango1.0-0 libpango-1.0-0 libpangocairo-1.0-0 libpangoxft-1.0-0 
libpangoft2-1.0-0 libpango1.0-udeb libpango1.0-dev libpango1.0-doc 
gir1.2-pango-1.0 pango1.0-tests
Architecture: source
Version: 1.40.11-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bicha 
Description:
 gir1.2-pango-1.0 - Layout and rendering of internationalized text - gir 
bindings
 libpango-1.0-0 - Layout and rendering of internationalized text
 libpango1.0-0 - Layout and rendering of internationalized text (transitional 
pack
 libpango1.0-dev - Development files for the Pango
 libpango1.0-doc - Documentation files for the Pango
 libpango1.0-udeb - Layout and rendering of internationalized text - minimal 
runtime (udeb)
 libpangocairo-1.0-0 - Layout and rendering of internationalized text
 libpangoft2-1.0-0 - Layout and 

Bug#872679: marked as done (pd-hcs FTBFS with puredata 0.48.0-1)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2017 09:20:50 +
with message-id 
and subject line Bug#872679: fixed in pd-hcs 0.1-4
has caused the Debian Bug report #872679,
regarding pd-hcs FTBFS with puredata 0.48.0-1
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.)


-- 
872679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872679
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pd-hcs
Version: 0.1-3
Severity: serious
Tags: buster sid

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

...
classpath.c: In function 'classpath_rewind':
classpath.c:90:22: error: 'sys_searchpath' undeclared (first use in this 
function); did you mean 'sys_usestdpath'?
  x->x_top->nl_next = sys_searchpath;
  ^~
  sys_usestdpath
classpath.c:90:22: note: each undeclared identifier is reported only once for 
each function it appears in
Makefile:166: recipe for target 'classpath.o' failed
make[2]: *** [classpath.o] Error 1
--- End Message ---
--- Begin Message ---
Source: pd-hcs
Source-Version: 0.1-4

We believe that the bug you reported is fixed in the latest version of
pd-hcs, 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.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated 
pd-hcs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 24 Aug 2017 08:33:47 +0200
Source: pd-hcs
Binary: pd-hcs
Architecture: source
Version: 0.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: IOhannes m zmölnig (Debian/GNU) 
Description:
 pd-hcs - Pd library of experiments in UNIX, the Pd GUI, and more
Closes: 872679
Changes:
 pd-hcs (0.1-4) unstable; urgency=medium
 .
   * Added patch for retrieving sys_searchpath independent of Pd-version
 (Closes: #872679)
   * Reproducible builds updates
 * Modernized calculation of reproducible dates
 * Fixed reproducible timestamp patch
   * Modernized Vcs-Browser stanza
   * Bumped standards to 4.1.0
Checksums-Sha1:
 f04bbb95e1e5e8c6dee317e48473531f35a0b6f8 1962 pd-hcs_0.1-4.dsc
 9c933d889777feae578d2c1fe34d816a11b6ee41 5200 pd-hcs_0.1-4.debian.tar.xz
 5165e5f879db21a9c0bfdb7168e45809dcd8c892 5101 pd-hcs_0.1-4_amd64.buildinfo
Checksums-Sha256:
 142d65d41ecbb0b6fcee7330845f00462229c6580b6554d5b6f078c1ff1b1c9d 1962 
pd-hcs_0.1-4.dsc
 d6bf2fff3d1d765386f3ba864e5d0078b27b068b28fa9768b8d278edc3b0e04e 5200 
pd-hcs_0.1-4.debian.tar.xz
 efd9515f3df5bb62d9794543d5972eb69dee2a3db4c1a47ee3ef1a57b953b8f9 5101 
pd-hcs_0.1-4_amd64.buildinfo
Files:
 c0bb84f73baf9816c0478602d52a7b45 1962 sound optional pd-hcs_0.1-4.dsc
 9e12d4d04ec3864e3c9ab6676260a114 5200 sound optional pd-hcs_0.1-4.debian.tar.xz
 f9f4f7143e05c9c76640b48c71fae379 5101 sound optional 
pd-hcs_0.1-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEdAXnRVdICXNIABVttlAZxH96NvgFAlmek8cACgkQtlAZxH96
NvjDPg/8CVBZ/lHdQrAYuCgDpfC+REM5iwsTxE1+izwFuk5JO5ZyjlEds6s4gn5f
YxH/M6wJyyZYQBVfamkx9ENmuYVmtehyj7/bByzezVPOOayz4dkVgfJXkFtMsXCt
RNAO9xzQd8a9akmeXYSM7fGDvbstzXf0wDTaMIZsKBT08b9JrFnxMAbGwGRojFan
LfyGmtDaV/F1kuqp68TN4VKQEsvPX7m6kquDY5RYZWgRwBkDksES/cGHiTUfm4Hx
6fLkRN0Zsk1C0+LLGsj4rVCSEP+FB5Yml1XqqUTbwazE4emGd6jrup7zqGBi5nS6
eE5uMmVEmnp4zRESP0MurT3iYSOiySykzw0K4TcZ70CPT1mJDDBdXxlSFai6L1zr
FQkvjIzH6cRdZ/Fn9/he9oD8iH4HVf8SGXXMc8/49oekpkm+qqrZWXIFWAey5Sp6
/tb8Adp9Ol1dLHRzbxtX1yV/+LOAG2MuVIxxNzn3seJaLIoGyZi5lHgRfoscx5Sf
G0or1RyzCvtm9IjyJzqUfDvsOeVYZyfSyg9tubvVeXpesm2hXgzkYvGWoZIroUJQ
ZWKfNCyKZSFtPwU/4TmYLdMW7u/dKJC89+vYxrR4dw9T/0n0ycMiKjIrR8DfEVkb
lNlFdzVzX7AiBlyK2490y+npJ7ZRZHzEPRYHQWucpmzRWUoMA94=
=Y6fE
-END PGP SIGNATURE End Message ---

Processed: limit source to pango1.0, tagging 872317

[Debian Bug Tracking System]

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

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

> tags 872317 + pending
Bug #872317 [pango1.0] libgtk2-perl FTBFS: GtkTextIter test failures
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Bug#872679 marked as pending

[Debian Bug Tracking System]

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

> tag 872679 pending
Bug #872679 [src:pd-hcs] pd-hcs FTBFS with puredata 0.48.0-1
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#872679: marked as pending

[IOhannes m zmölnig]

tag 872679 pending
thanks

Hello,

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

http://anonscm.debian.org/git/pkg-multimedia/pd-hcs.git/commit/?id=83dbf13

---
commit 83dbf130b8efee382633328840b4ed12cc63f184
Author: IOhannes m zmölnig 
Date:   Thu Aug 24 08:34:51 2017 +0200

Ready for upload to unstable.

diff --git a/debian/changelog b/debian/changelog
index da1ed80..1d23cbe 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,15 @@
+pd-hcs (0.1-4) unstable; urgency=medium
+
+  * Added patch for retrieving sys_searchpath independent of Pd-version
+(Closes: #872679)
+  * Reproducible builds updates
+* Modernized calculation of reproducible dates
+* Fixed reproducible timestamp patch
+  * Modernized Vcs-Browser stanza
+  * Bumped standards to 4.1.0
+
+ -- IOhannes m zmölnig (Debian/GNU)   Thu, 24 Aug 2017 
08:33:47 +0200
+
 pd-hcs (0.1-3) unstable; urgency=medium
 
   [ Hans-Christoph Steiner ]

Bug#872881: marked as done (simgrid: FTBFS: `__atomic_fetch_add_8' undefined)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2017 08:54:20 +
with message-id 
and subject line Bug#872881: fixed in simgrid 3.16+dfsg-3
has caused the Debian Bug report #872881,
regarding simgrid: FTBFS: `__atomic_fetch_add_8' undefined
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.)


-- 
872881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872881
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: simgrid
Version: 3.16+dfsg-1
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)

Builds of simgrid failed on armel, mips, mipsel, and the non-release
architectures m68k and powerpc:

  lib/libsimgrid.so.3.16: undefined reference to `__atomic_fetch_add_8'
  collect2: error: ld returned 1 exit status
  CMakeFiles/testall.dir/build.make:314: recipe for target 'testall' failed

Please link libsimgrid against -latomic on these architectures.  You
can in general do so without hardcoding an architecture list by
arranging to link with

  -Wl,--as-needed -latomic --Wl,--no-as-needed

but I don't know how easy that is to do under CMake.

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
--- End Message ---
--- Begin Message ---
Source: simgrid
Source-Version: 3.16+dfsg-3

We believe that the bug you reported is fixed in the latest version of
simgrid, 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.
Martin Quinson  (supplier of updated simgrid package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 24 Aug 2017 09:59:23 +0200
Source: simgrid
Binary: libsimgrid3.16 simgrid-doc simgrid-java libsimgrid-dev
Architecture: source amd64 all
Version: 3.16+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Martin Quinson 
Changed-By: Martin Quinson 
Description:
 libsimgrid-dev - Development files for the SimGrid Toolkit
 libsimgrid3.16 - Toolkit for scalable simulation of distributed applications
 simgrid-doc - Documentation for the SimGrid Toolkit
 simgrid-java - Java bindings for the SimGrid Toolkit
Closes: 872881
Changes:
 simgrid (3.16+dfsg-3) unstable; urgency=medium
 .
   * d/p/atomic-library: Pass --as-needed -latomic *after* the link args
 Hopefully (Closes: #872881).
Checksums-Sha1:
 3e84eb4696fda4275155d1653b4dd34f979c76f4 2375 simgrid_3.16+dfsg-3.dsc
 a4a24ee91b132eb759cb6e9cf75abcc0e230f7ef 12088 
simgrid_3.16+dfsg-3.debian.tar.xz
 386f39dd6e74cbb67ce7322765861315cb66e9f6 4480 
libsimgrid-dev-dbgsym_3.16+dfsg-3_amd64.deb
 076c233bdbe1ce80c4231a4a7408846ed3ba2bed 178800 
libsimgrid-dev_3.16+dfsg-3_amd64.deb
 7119b276e24626ad65f244f29b79378216479328 3831542 
libsimgrid3.16-dbgsym_3.16+dfsg-3_amd64.deb
 6b3a75f9f1017d9b851b2071acb12fe567f85c06 1115694 
libsimgrid3.16_3.16+dfsg-3_amd64.deb
 3421ec908da524a0a39e67f5b86733e1612e5172 3243982 
simgrid-doc_3.16+dfsg-3_all.deb
 d2ca2e80a79d499903cd9430e5836eabd41d4156 201300 
simgrid-java-dbgsym_3.16+dfsg-3_amd64.deb
 e70c118a7ae602c92c87457a78c7a388fb77d602 306752 
simgrid-java_3.16+dfsg-3_amd64.deb
 3ab3c6619f05c4a3904354bde779ed0990a7257f 14438 
simgrid_3.16+dfsg-3_amd64.buildinfo
Checksums-Sha256:
 4db0fc081b778ebf505a874dda8030cd0f890b18a4dce06b57ad7154b4082aa2 2375 
simgrid_3.16+dfsg-3.dsc
 a5e61fe172696c85c6cedb37cf361b8f35ba8ec3890f0578bff6f351d31d8642 12088 
simgrid_3.16+dfsg-3.debian.tar.xz
 dbdd3cbc1569939f39cac7f742404495133ac14a059cda5a0f6b8bc750522166 4480 
libsimgrid-dev-dbgsym_3.16+dfsg-3_amd64.deb
 a9f0adcba404ce7f88ffee37be9839c68284311a495b8f52feaddbb25d87116b 178800 
libsimgrid-dev_3.16+dfsg-3_amd64.deb
 20a16edcdc334665d0c70f0a5f01d29fbfed0d3e484cce1f5c708e429eccffb1 3831542 
libsimgrid3.16-dbgsym_3.16+dfsg-3_amd64.deb
 a4b9869294cc67daafdc232e394a90fc16d5e19bcee15037ab27df0104977d97 1115694 
libsimgrid3.16_3.16+dfsg-3_amd64.deb
 a49a3e7de7bc1f5dcb1495d424f6ae018be2e877f1e4de5bcd19880f1e262624 3243982 

Bug#873024: marked as done (orthanc-wsi FTBFS with dcmtk 3.6.2)

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2017 08:53:18 +
with message-id 
and subject line Bug#873024: fixed in orthanc-wsi 0.4+dfsg-3
has caused the Debian Bug report #873024,
regarding orthanc-wsi FTBFS with dcmtk 3.6.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.)


-- 
873024: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873024
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: orthanc-wsi
Version: 0.4+dfsg-2
Severity: serious

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

...
-- Trying to find DCMTK expecting DCMTKConfig.cmake
-- Trying to find DCMTK expecting DCMTKConfig.cmake - ok
DCMTK version: 362
CMake Error at 
/build/1st/orthanc-wsi-0.4+dfsg/Resources/Orthanc/Resources/CMake/DcmtkConfiguration.cmake:318
 (message):
  Cannot locate the DICOM dictionary on this system
Call Stack (most recent call first):
  CMakeLists.txt:67 (include)


-- Configuring incomplete, errors occurred!
--- End Message ---
--- Begin Message ---
Source: orthanc-wsi
Source-Version: 0.4+dfsg-3

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

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

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

Debian distribution maintenance software
pp.
Gert Wollny  (supplier of updated orthanc-wsi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 23 Aug 2017 20:55:25 +
Source: orthanc-wsi
Binary: orthanc-wsi
Architecture: source
Version: 0.4+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Gert Wollny 
Description:
 orthanc-wsi - Whole-slide imaging support for Orthanc (digital pathology)
Closes: 873024
Changes:
 orthanc-wsi (0.4+dfsg-3) unstable; urgency=medium
 .
   * Team upload
   * Update search path for dicomdict, Closes: #873024
Checksums-Sha1:
 6d761bae5471f00edff34bd95488633a59ddc81f 1907 orthanc-wsi_0.4+dfsg-3.dsc
 0ffe6e1d06075df6d2f1f0d12d67441a9cb16df3 316448 
orthanc-wsi_0.4+dfsg-3.debian.tar.xz
 cba929feddc41b95477270e0116d9db95bf9eb6c 13603 
orthanc-wsi_0.4+dfsg-3_source.buildinfo
Checksums-Sha256:
 d6f4d040299d79c81b00deec69449a0aa4e3b38a81bd870917dce0faea6ad624 1907 
orthanc-wsi_0.4+dfsg-3.dsc
 0b42f984619fec938fcab99055edad2021bbe166d73d22db81755b206547502c 316448 
orthanc-wsi_0.4+dfsg-3.debian.tar.xz
 11e0f90ab194a25dd24f49252d69be411b3c3d421ba0cd8522b50de6a773b43e 13603 
orthanc-wsi_0.4+dfsg-3_source.buildinfo
Files:
 1be34e1cf9f8d1efd006e0bc3342d9b6 1907 science optional 
orthanc-wsi_0.4+dfsg-3.dsc
 ffae39fde9c083804d9fd701266b9cc0 316448 science optional 
orthanc-wsi_0.4+dfsg-3.debian.tar.xz
 92eaca082c2928122d7b5d96b7492362 13603 science optional 
orthanc-wsi_0.4+dfsg-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEENGr+2YOvnEff6Rr7+B42i5smq5gFAlmegxYACgkQ+B42i5sm
q5jnRwgAqhm81SCWKlznDvpVBBxZaR6vfY9NRv9n/kYFif6kRyzqJC+CDk0D5XlD
MCfO0yXnUjcBmRJSGp2dzJ9BOFjPLE4Rigy4Hpgp8Q7jFEZnjNStS6oW5/V6fbP+
fcI2/sdRD4+UrWyrpbYj/4XkcrojtAHXYrJ7JtC8gW0cehdAI6n0ZO+RBTUC9dhK
ToOPtf+frz/AcIjPL4LB5cdk2bOMo/WbN3nBZErkdl/nHlMcGvDSQIwDrFWq8d0a
6Rols6LQL+FGfH8yGXIUHtRNQPBAc2rwpcDi7JJMJI1DR1RdSaPUbAk8E8DroMfw
1XcQ0h/prUQLePYbEYiFTrlkVQO31Q==
=aWXb
-END PGP SIGNATURE End Message ---

Processed: reassign to ruby-rails-dom-testing

[Debian Bug Tracking System]

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

> reassign 869036 src:ruby-rails-dom-testing
Bug #869036 [src:ruby-rails-i18n] ruby-rails-i18n: FTBFS: ERROR: Test "ruby2.3" 
failed.
Bug reassigned from package 'src:ruby-rails-i18n' to 
'src:ruby-rails-dom-testing'.
No longer marked as found in versions ruby-rails-i18n/4.0.8-1.
Ignoring request to alter fixed versions of bug #869036 to the same values 
previously set
> forcemerge 869041 869036
Bug #869041 {Done: Pirate Praveen } 
[src:ruby-rails-dom-testing] ruby-rails-dom-testing: FTBFS: ERROR: Test 
"ruby2.3" failed.
Bug #869038 {Done: Pirate Praveen } 
[src:ruby-rails-dom-testing] ruby-rspec-rails: FTBFS: ERROR: Test "ruby2.3" 
failed.
Bug #869039 {Done: Pirate Praveen } 
[src:ruby-rails-dom-testing] ruby-kaminari: FTBFS: ERROR: Test "ruby2.3" failed.
Bug #869040 {Done: Pirate Praveen } 
[src:ruby-rails-dom-testing] ruby-versionist: FTBFS: ERROR: Test "ruby2.3" 
failed.
Bug #869044 {Done: Pirate Praveen } 
[src:ruby-rails-dom-testing] ruby-sass-rails: FTBFS: ERROR: Test "ruby2.3" 
failed.
Bug #869045 {Done: Pirate Praveen } 
[src:ruby-rails-dom-testing] ruby-devise-two-factor: FTBFS: ERROR: Test 
"ruby2.3" failed: Invalid gemspec in [devise-two-factor.gemspec]: No such file 
or directory - git
Bug #869046 {Done: Pirate Praveen } 
[src:ruby-rails-dom-testing] ruby-activerecord-session-store: FTBFS: ERROR: 
Test "ruby2.3" failed.
Bug #869047 {Done: Pirate Praveen } 
[src:ruby-rails-dom-testing] ruby-premailer-rails: FTBFS: ERROR: Test "ruby2.3" 
failed.
Bug #869050 {Done: Pirate Praveen } 
[src:ruby-rails-dom-testing] ruby-jquery-rails: FTBFS: ERROR: Test "ruby2.3" 
failed: Invalid gemspec in [jquery-rails.gemspec]: No such file or directory - 
git
Bug #869052 {Done: Pirate Praveen } 
[src:ruby-rails-dom-testing] ruby-devise: FTBFS: ERROR: Test "ruby2.3" failed.
Bug #869053 {Done: Pirate Praveen } 
[src:ruby-rails-dom-testing] ruby-health-check: FTBFS: ERROR: Test "ruby2.3" 
failed: Invalid gemspec in [health_check.gemspec]: No such file or directory - 
git
Bug #869057 {Done: Pirate Praveen } 
[src:ruby-rails-dom-testing] ruby-doorkeeper: FTBFS: ERROR: Test "ruby2.3" 
failed: Invalid gemspec in [doorkeeper.gemspec]: No such file or directory - git
Bug #869059 {Done: Pirate Praveen } 
[src:ruby-rails-dom-testing] ruby-redis-actionpack: FTBFS: ERROR: Test 
"ruby2.3" failed.
Bug #869062 {Done: Pirate Praveen } 
[src:ruby-rails-dom-testing] ruby-turbolinks: FTBFS: ERROR: Test "ruby2.3" 
failed.
Bug #869036 [src:ruby-rails-dom-testing] ruby-rails-i18n: FTBFS: ERROR: Test 
"ruby2.3" failed.
Marked Bug as done
Marked as fixed in versions ruby-rails-dom-testing/1.0.6-2.
Marked as found in versions ruby-rails-dom-testing/1.0.6-1.
Bug #869038 {Done: Pirate Praveen } 
[src:ruby-rails-dom-testing] ruby-rspec-rails: FTBFS: ERROR: Test "ruby2.3" 
failed.
Bug #869039 {Done: Pirate Praveen } 
[src:ruby-rails-dom-testing] ruby-kaminari: FTBFS: ERROR: Test "ruby2.3" failed.
Bug #869040 {Done: Pirate Praveen } 
[src:ruby-rails-dom-testing] ruby-versionist: FTBFS: ERROR: Test "ruby2.3" 
failed.
Bug #869044 {Done: Pirate Praveen } 
[src:ruby-rails-dom-testing] ruby-sass-rails: FTBFS: ERROR: Test "ruby2.3" 
failed.
Bug #869045 {Done: Pirate Praveen } 
[src:ruby-rails-dom-testing] ruby-devise-two-factor: FTBFS: ERROR: Test 
"ruby2.3" failed: Invalid gemspec in [devise-two-factor.gemspec]: No such file 
or directory - git
Bug #869046 {Done: Pirate Praveen } 
[src:ruby-rails-dom-testing] ruby-activerecord-session-store: FTBFS: ERROR: 
Test "ruby2.3" failed.
Bug #869047 {Done: Pirate Praveen } 
[src:ruby-rails-dom-testing] ruby-premailer-rails: FTBFS: ERROR: Test "ruby2.3" 
failed.
Bug #869050 {Done: Pirate Praveen } 
[src:ruby-rails-dom-testing] ruby-jquery-rails: FTBFS: ERROR: Test "ruby2.3" 
failed: Invalid gemspec in [jquery-rails.gemspec]: No such file or directory - 
git
Bug #869052 {Done: Pirate Praveen } 
[src:ruby-rails-dom-testing] ruby-devise: FTBFS: ERROR: Test "ruby2.3" failed.
Bug #869053 {Done: Pirate Praveen } 
[src:ruby-rails-dom-testing] ruby-health-check: FTBFS: ERROR: Test "ruby2.3" 
failed: Invalid gemspec in [health_check.gemspec]: No such file or directory - 
git
Bug #869057 {Done: Pirate Praveen } 
[src:ruby-rails-dom-testing] ruby-doorkeeper: FTBFS: ERROR: Test "ruby2.3" 
failed: Invalid gemspec in [doorkeeper.gemspec]: No such file or directory - git
Bug #869059 {Done: Pirate Praveen } 
[src:ruby-rails-dom-testing] ruby-redis-actionpack: 

Bug#870599: upload ansible version with Depends: python-jinja2 < 2.9

[Jack Henschel]

Hi,

are you aware that this change currently renders ansible uninstallable on new 
systems? (i.e. where ansible previously has not been installed)

$ sudo apt install [--allow-downgrades] ansible
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 ansible : Depends: python-jinja2 (< 2.9) but it is not going to be installed
   Recommends: python-jmespath but it is not going to be installed
   Recommends: python-kerberos but it is not going to be installed
   Recommends: python-libcloud but it is not going to be installed
   Recommends: python-selinux but it is not going to be installed
   Recommends: python-winrm (>= 0.1.1) but it is not going to be 
installed
   Recommends: python-xmltodict but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

Greetings
Jack



signature.asc
Description: OpenPGP digital signature

Processed: haskell-language-c needs fix for gcc 7 on i386

[Debian Bug Tracking System]

Processing control commands:

> affects -1 c2hs
Bug #873069 [src:haskell-language-c] haskell-language-c needs fix for gcc 7 on 
i386
Added indication that 873069 affects c2hs

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

Bug#873069: haskell-language-c needs fix for gcc 7 on i386

[Adrian Bunk]

Source: haskell-language-c
Version: 0.5.0-3
Severity: serious
Tags: buster sid
Control: affects -1 c2hs

Several packages FTBFS on i386 with the following error:

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

...
Preprocessing library dpkg-0.0.3...
c2hs: C header contains errors:
/usr/lib/gcc/i686-linux-gnu/7/include/stddef.h:435: (column 3) [ERROR]  >>> 
Syntax error !
  The symbol `__float128' does not fit here.
/usr/share/cdbs/1/class/hlibrary.mk:147: recipe for target 'build-ghc-stamp' 
failed
make: *** [build-ghc-stamp] Error 1


Upstream fix:
https://github.com/visq/language-c/commit/2021974d7eb48d71a66b1d235287ab83ef1ee2a5

Processed: your mail

[Debian Bug Tracking System]

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

> severity 873063 grave
Bug #873063 [fcitx-frontend-qt5] fcitx-frontend-qt5: Not working with Qt 5.9
Severity set to 'grave' from 'serious'
> thanks
Stopping processing here.

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

Bug#872881: simgrid: FTBFS: `__atomic_fetch_add_8' undefined

[Martin Quinson]

Hello,

thanks for the patch. I came to something very similar, only
protecting it to be used only by GCC. I was waiting to find the time
to test it before upload, but if you tested, I'll upload it right away.

Many thanks,
Mt

On Wed, Aug 23, 2017 at 02:41:15PM +0100, James Cowgill wrote:
> Hi,
> 
> The attached patch seems to work (ie replace atomic-library with it).
> Using target_link_libraries should put any linker arguments at the end
> instead of the beginning.
> 
> Thanks,
> James

> --- a/tools/cmake/MakeLib.cmake
> +++ b/tools/cmake/MakeLib.cmake
> @@ -114,6 +114,7 @@ if(enable_smpi AND APPLE)
>set(SIMGRID_DEP "${SIMGRID_DEP} -Wl,-U -Wl,_smpi_simulated_main")
>  endif()
>  
> +set(SIMGRID_DEP "${SIMGRID_DEP} -Wl,--as-needed -latomic -Wl,--no-as-needed")
>  target_link_libraries(simgrid${SIMGRID_DEP})
>  
>  # Dependencies from maintainer mode





-- 
If the facts don't fit the theory, change the facts.
  -- Albert Einstein (?)


signature.asc
Description: PGP signature

Bug#873063: fcitx-frontend-qt5: Not working with Qt 5.9

[Zhang Jingqiang]

Package: fcitx-frontend-qt5
Version: 1.0.5-1+b1
Severity: serious

Dear Maintainer,

Please rebuild it with Qt 5.9.
Or package the new version 1.1.0.

Thanks

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

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

Versions of packages fcitx-frontend-qt5 depends on:
ii  fcitx-module-dbus  1:4.2.9.1-6
ii  libc6  2.24-15
ii  libfcitx-qt5-1 1.0.5-1+b1
ii  libgcc11:7.2.0-1
ii  libqt5core5a   5.9.1+dfsg-9
ii  libqt5dbus55.9.1+dfsg-9
ii  libqt5gui5 5.9.1+dfsg-9
ii  libstdc++6 7.2.0-1
ii  libxkbcommon0  0.7.1-1

fcitx-frontend-qt5 recommends no packages.

fcitx-frontend-qt5 suggests no packages.

-- no debconf information