Bug#869020: logback: FTBFS: find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such file or directory

[Apollon Oikonomopoulos]

Control: tags -1 unreproducible moreinfo
Control: severity -1 normal

Hi Lucas,

Thanks for the report.

On 07:40 Thu 20 Jul , Lucas Nussbaum wrote:
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> 
> Relevant part (hopefully):
> >  debian/rules build
> > dh build --build-system=maven
> >dh_testdir -O--build-system=maven
> >dh_update_autotools_config -O--build-system=maven
> >dh_autoreconf -O--build-system=maven
> >dh_auto_configure -O--build-system=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

These are harmless messages produced by maven-debian-helper 2.2.1 (and 
silenced in 2.2.2).


> > [INFO] 
> > 
> > [INFO] Skipping Logback-Parent
> > [INFO] This project has been banned from the build due to 
> > previous failures.
> > [INFO] 
> > 
> > [INFO] 
> > 

This seems to be the actual problem. Unfortunately I'm unable to reproduce this
with a current sid chroot. I suspect it was a transient problem in some of the
dependencies. Could you please re-run the build on your testbed and confirm
that it builds fine?

Regards,
Apollon

Processed: Re: Bug#869020: logback: FTBFS: find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such file or directory

[Debian Bug Tracking System]

Processing control commands:

> tags -1 unreproducible moreinfo
Bug #869020 [src:logback] logback: FTBFS: find: 
'/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such 
file or directory
Added tag(s) moreinfo and unreproducible.
> severity -1 normal
Bug #869020 [src:logback] logback: FTBFS: find: 
'/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No such 
file or directory
Severity set to 'normal' from 'serious'

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

Processed: Re: git FTBFS on i386: t7006-pager.sh test failure

[Debian Bug Tracking System]

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

> found 871570 git/1:2.13.2-3
Bug #871570 [src:git] git FTBFS on i386: t7006-pager.sh test failure
Marked as found in versions git/1:2.13.2-3.
> tags 871570 + upstream
Bug #871570 [src:git] git FTBFS on i386: t7006-pager.sh test failure
Added tag(s) upstream.
> quit
Stopping processing here.

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

Processed: Re: torcs: ftbfs with GCC-7

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending patch
Bug #853685 [src:torcs] torcs: ftbfs with GCC-7
Added tag(s) pending and patch.

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

Bug#853685: torcs: ftbfs with GCC-7

[Markus Koschany]

Control: tags -1 pending patch

On Tue, 31 Jan 2017 09:36:22 + Matthias Klose  wrote:

Package: src:torcs
Version: 1.3.3+dfsg-0.4
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7


This issue is fixed in Git and I intend to upload the fix when I'm at 
home again in a few days.


Markus

Bug#871653: marked as done (hspell: -fPIC removal causes other packages to FTBFS)

[Debian Bug Tracking System]

Your message dated Thu, 10 Aug 2017 15:36:31 +
with message-id 
and subject line Bug#871653: fixed in hspell 1.4-2
has caused the Debian Bug report #871653,
regarding hspell: -fPIC removal causes other packages to FTBFS
to be marked as done.

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

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


-- 
871653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871653
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: hspell
Version: 1.4-1
Severity: serious
Control: affects -1 src:kde4libs src:sonnet

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

...
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/libhspell.a(gimatria.o):
 relocation R_X86_64_PC32 against symbol `hspell_debug' can not be used when 
making a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: Bad value
collect2: error: ld returned 1 exit status
src/plugins/hspell/CMakeFiles/sonnet_hspell.dir/build.make:177: recipe for 
target 'src/plugins/hspell/hspell.so' failed


This is caused by hspell 1.3-1 -> 1.4-1 removing -fPIC from CFLAGS
in debian/rules.
--- End Message ---
--- Begin Message ---
Source: hspell
Source-Version: 1.4-2

We believe that the bug you reported is fixed in the latest version of
hspell, 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.
Lior Kaplan  (supplier of updated hspell 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, 10 Aug 2017 10:58:53 -0400
Source: hspell
Binary: hspell myspell-he
Architecture: source
Version: 1.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Hebrew Packaging Team 

Changed-By: Lior Kaplan 
Description:
 hspell - Hebrew spell checker and morphological analyzer
 myspell-he - Hebrew dictionary for myspell
Closes: 871653
Changes:
 hspell (1.4-2) unstable; urgency=medium
 .
   * Add missing -fPIC in CFLAGS (Closes: #871653)
Checksums-Sha1:
 805a231c33b8e6c875ded8b0b81248f647203402 2331 hspell_1.4-2.dsc
 056481d4df1b2a726f11b8390837a4b39ba4798c 18764 hspell_1.4-2.debian.tar.xz
Checksums-Sha256:
 8725827d14d331595c9aa74949fca9bb1fc6b660bff81ce12cb1571f86174648 2331 
hspell_1.4-2.dsc
 92eb31055f5cf487cb455657a1f08a55350b46f0f30e51a50e19a833fb6039cb 18764 
hspell_1.4-2.debian.tar.xz
Files:
 04c57295279e9268965488694d52d4e2 2331 text optional hspell_1.4-2.dsc
 30e45507ac6f03cc2095b5fc19450e3d 18764 text optional hspell_1.4-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE+THkfhnCfNCgrzYaCdqUCLThRJkFAlmMeFwACgkQCdqUCLTh
RJkdhA/+PxgEiFG3a6faqPXVRQUH81NqQnbQ4Y4goMg/ydLdrtzbmphUsmwVHF9K
mjFegXhctWXxJT19fa1kZK26v4f0kwYU3xa1C+f4yr5Bcs7CnBEYtSMSffCtYBcp
NTBkb4WglSdc7MTIs6vHoX8P/IixHJxqaJC4/Ods8a6/PlDhFAjTxRQlA2eKoTCH
Kn1Rvk4OjZ/F+nz4WnhrYsh207vBmFP3XGpmGikpFoG8UMwvtfTpeQycbQoCOx8F
xMMlUca+EFt/aSb5p61NtFgRHeKA/iH1CURAK++0cVW5jG2qTrZgDxvR3nipR+Rb
8bdcPSzzmO5d7+Ed922hto0rMbNrla5UZPPUthyloRf11dQtjSH06BHb9DLUcBsI
C7d76LmxKXnA4EThKYc4dcCowkoxu6XOoWTDYnXV468gjA6fjkHhbhqm8lbcEkuq
2faugH/IjoddC+VEvkOOMEImEeOyaVlz1ZA21SY6H28Qwhv0tdlC25Ah5Rl19qrt
oEsjLbp7uv93G9j7SHA2LVMNuuXeXczdD4OTsuqnptfhehKLeS33PyFL/aXlbxGQ
DnhyBmSQR3vQAEKNKbnE0s9kj1duMSXwW5Et5+touFcclBWhp/zXAlVdBOuUIXdn
Rq8M9QOqym5Jq5tkRJ6xxkrI6NMxrQhXZPgrIVTAVVnVaXrY7Dw=
=jmo2
-END PGP SIGNATURE End Message ---

Bug#871677: insighttoolkit4 ftbfs with GCC 7 (castxml out of date)

[Matthias Klose]

Package: src:insighttoolkit4
Version: 4.12.0-dfsg1-1
Severity: serious
Tags: sid buster

Contrary to the claim in #871282, the package was *not* built using gcc-7.  The
recent binNMU triggered that, and then showed a ftbfs.  Not sure how that was
tested ...

cd /<>/BUILD/Wrapping/Modules/ITKCommon && /usr/bin/castxml -o
/<>/BUILD/Wrapping/itkFixedArray.xml --castxml-gccxml
--castxml-start _wrapping_ --castxml-cc-gnu "(" /usr/bin/c++ -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/nifti
-Wall -Wcast-align -Wdisabled-optimization -Wextra -Wformat=2 -Winvalid-pch
-Wno-format-nonliteral -Wpointer-arith -Wshadow -Wunused -Wwrite-strings
-funit-at-a-time -Wno-strict-overflow -Wno-deprecated -Wno-invalid-offsetof
-Woverloaded-virtual -Wstrict-null-sentinel ")" -w -c
@/<>/BUILD/Wrapping/ITKCommon.castxml.inc
/<>/BUILD/Wrapping/itkFixedArray.cxx
In file included from /<>/BUILD/Wrapping/itkFixedArray.cxx:1:
In file included from 
/<>/Modules/Core/Common/include/itkCommand.h:21:
In file included from 
/<>/Modules/Core/Common/include/itkObject.h:31:
In file included from
/<>/Modules/Core/Common/include/itkLightObject.h:21:
In file included from 
/<>/Modules/Core/Common/include/itkMacro.h:47:
In file included from /usr/include/c++/7/string:52:
In file included from /usr/include/c++/7/bits/basic_string.h:6159:
In file included from /usr/include/c++/7/ext/string_conversions.h:41:
In file included from /usr/include/c++/7/cstdlib:77:
/usr/include/c++/7/bits/std_abs.h:103:16: error: invalid operands to binary
expression ('__castxml__float128' (aka '__castxml__float128_s') and 'int')
  { return __x < 0 ? -__x : __x; }
   ~~~ ^ ~
/usr/include/c++/7/bits/stl_pair.h:449:5: note: candidate template ignored:
could not match 'pair' against
'__castxml__float128_s'
operator<(const pair<_T1, _T2>& __x, const pair<_T1, _T2>& __y)
^
/usr/include/c++/7/bits/stl_iterator.h:305:5: note: candidate template ignored:
could not match 'reverse_iterator' against
'__castxml__float128_s'
operator<(const reverse_iterator<_Iterator>& __x,
^
/usr/include/c++/7/bits/stl_iterator.h:343:5: note: candidate template ignored:
could not match 'reverse_iterator' against
'__castxml__float128_s'
operator<(const reverse_iterator<_IteratorL>& __x,
^
/usr/include/c++/7/bits/stl_iterator.h:1142:5: note: candidate template ignored:
could not match 'move_iterator' against 
'__castxml__float128_s'
operator<(const move_iterator<_IteratorL>& __x,
^
/usr/include/c++/7/bits/stl_iterator.h:1148:5: note: candidate template ignored:
could not match 'move_iterator' against 
'__castxml__float128_s'
operator<(const move_iterator<_Iterator>& __x,
^
/usr/include/c++/7/bits/basic_string.h:5892:5: note: candidate template ignored:
could not match 'basic_string' against '__castxml__float128_s'
operator<(const basic_string<_CharT, _Traits, _Alloc>& __lhs,
^
/usr/include/c++/7/bits/basic_string.h:5905:5: note: candidate template ignored:
could not match 'basic_string' against '__castxml__float128_s'
operator<(const basic_string<_CharT, _Traits, _Alloc>& __lhs,
^
/usr/include/c++/7/bits/basic_string.h:5917:5: note: candidate template ignored:
could not match 'const _CharT *' against '__castxml__float128' (aka
'__castxml__float128_s')
operator<(const _CharT* __lhs,
^
In file included from /<>/BUILD/Wrapping/itkFixedArray.cxx:1:
In file included from 
/<>/Modules/Core/Common/include/itkCommand.h:21:
In file included from 
/<>/Modules/Core/Common/include/itkObject.h:31:
In file included from
/<>/Modules/Core/Common/include/itkLightObject.h:21:
In file included from 
/<>/Modules/Core/Common/include/itkMacro.h:47:
In file included from /usr/include/c++/7/string:52:
In file included from /usr/include/c++/7/bits/basic_string.h:6159:
In file included from /usr/include/c++/7/ext/string_conversions.h:41:
In file included from /usr/include/c++/7/cstdlib:77:
/usr/include/c++/7/bits/std_abs.h:103:22: error: invalid argument type
'__castxml__float128' (aka '__castxml__float128_s') to unary expression
  { return __x < 0 ? -__x : __x; }
 ^~~~
/usr/include/c++/7/bits/std_abs.h:102:3: error: no return statement in constexpr
function
  abs(__float128 __x)
  ^

Bug#871370: marked as done (libgettext-commons-java: FTBFS: [ERROR] Could not find goal 'attached' in plugin org.apache.maven.plugins:maven-assembly-plugin:3.0.0 among available goals single

[Debian Bug Tracking System]

Your message dated Thu, 10 Aug 2017 15:11:40 +
with message-id 
and subject line Bug#871370: fixed in libgettext-commons-java 0.9.6-5
has caused the Debian Bug report #871370,
regarding libgettext-commons-java: FTBFS: [ERROR] Could not find goal 
'attached' in plugin org.apache.maven.plugins:maven-assembly-plugin:3.0.0 among 
available goals single -> [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.)


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

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=maven
>dh_update_autotools_config -O--buildsystem=maven
>dh_autoreconf -O--buildsystem=maven
>dh_auto_configure -O--buildsystem=maven
>   mh_patchpoms -plibgettext-commons-java --debian-build 
> --keep-pom-version --maven-repo=/<>/debian/maven-repo
>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 
> -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] 
> 
> [INFO] Building Gettext Commons 0.9.6
> [INFO] 
> 
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 0.132 s
> [INFO] Finished at: 2017-08-07T12:43:34Z
> [INFO] Final Memory: 17M/966M
> [INFO] 
> 
> [ERROR] Could not find goal 'attached' in plugin 
> org.apache.maven.plugins:maven-assembly-plugin:3.0.0 among available goals 
> single -> [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/MojoNotFoundException
> 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 returned exit code 1
> debian/rules:6: recipe for target 'build' failed
> make: *** [build] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/2017/08/07/libgettext-commons-java_0.9.6-4_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: libgettext-commons-java
Source-Version: 0.9.6-5

We believe that the bug you reported is fixed in the latest version of
libgettext-commons-java, which is due to 

Bug#871570: git FTBFS on i386: t7006-pager.sh test failure

[Jonathan Nieder]

found 871570 git/1:2.13.2-3
tags 871570 + upstream
quit

Hi,

Adrian Bunk wrote:

> https://buildd.debian.org/status/fetch.php?pkg=git=i386=1%3A2.14.0-1=1502132890=0
>
> ...
> expecting success: 
>   (
>   sane_unset LESS LV &&
>   PAGER="env >pager-env.out; wc" &&
>   export PAGER &&
>   PATH="$(git --exec-path):$PATH" &&
>   export PATH &&
>   test_terminal sh -c ". git-sh-setup && git_pager"
>   ) &&
>   grep ^LESS= pager-env.out &&
>   grep ^LV= pager-env.out
> 
> wc: 'standard input': Input/output error
>   0   0   0
> not ok 6 - LESS and LV envvars set by git-sh-setup

Thanks for reporting.  I think I know what is happening here.  It is
not 100% reproducible.  It isn't a regression.  I'll send a patch
upstream.

Thanks,
Jonathan

Processed: tagging 813054

[Debian Bug Tracking System]

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

> # Fixed in a separate bug targeting FF 55
> tags 813054 + fixed-upstream
Bug #813054 [src:firefox] firefox: contains JSHint work under non-free licence
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

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

[Paul Menzel]

Package: lilypond-data
Version: 2.18.2-8
Severity: serious

Dear Debian folks,


The update of lilypond-data fails with the message below.

```
lilypond-data (2.18.2-8) wird eingerichtet ...
 Running mktexlsr /usr/share/texlive/texmf-dist...
mktexlsr: Updating /var/lib/texmf/ls-R-TEXLIVEDIST... 
mktexlsr: Done.
ln: die symbolische Verknüpfung 'lilypond/user' konnte nicht angelegt werden: 
Die Datei existiert bereits
dpkg: Fehler beim Bearbeiten des Paketes lilypond-data (--configure):
 Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
```

It says the symbolic link `lilypond/user` couldn’t be created, because the file 
already exists.


Thanks,

Paul

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

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

Versions of packages lilypond depends on:
ii  ghostscript9.21~dfsg-1
ii  libc6  2.24-14
ii  libfontconfig1 2.12.3-0.2
ii  libfreetype6   2.8-0.2
ii  libgcc11:7.1.0-13
ii  libglib2.0-0   2.53.4-3
ii  libgmp10   2:6.1.2+dfsg-1
ii  libltdl7   2.4.6-2
ii  libpango-1.0-0 1.40.6-1
ii  libpangoft2-1.0-0  1.40.6-1
ii  libstdc++6 7.1.0-13
ih  lilypond-data  2.18.2-8
ii  python 2.7.13-2

Versions of packages lilypond recommends:
ii  texlive-latex-base  2017.20170808-1

Versions of packages lilypond suggests:
ii  lilypond-doc  2.18.2-8

-- no debconf information

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

Bug#871586: marked as done (courier FTBFS with libcourier-unicode-dev 2.0-1)

[Debian Bug Tracking System]

Your message dated Thu, 10 Aug 2017 07:04:25 +
with message-id 
and subject line Bug#871586: fixed in courier 0.77.0-1
has caused the Debian Bug report #871586,
regarding courier FTBFS with libcourier-unicode-dev 2.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.)


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

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

...
rfc2047.c:379:30: error: unknown type name 'unicode_char'
 static int encode_word(const unicode_char *uc,
  ^~~~
rfc2047.c:412:31: error: unknown type name 'unicode_char'
 static int encode_words(const unicode_char *uc,
   ^~~~
rfc2047.c:457:41: error: unknown type name 'unicode_char'
 static int do_encode_words_method(const unicode_char *uc,
 ^~~~
...
--- End Message ---
--- Begin Message ---
Source: courier
Source-Version: 0.77.0-1

We believe that the bug you reported is fixed in the latest version of
courier, 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.
Markus Wanner  (supplier of updated courier 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, 10 Aug 2017 01:20:09 +0200
Source: courier
Binary: courier-base courier-maildrop courier-mlm courier-mta courier-faxmail 
courier-webadmin sqwebmail courier-pcp courier-pop courier-imap courier-ldap 
courier-doc courier-ssl courier-mta-ssl courier-pop-ssl courier-imap-ssl
Architecture: source all
Version: 0.77.0-1
Distribution: unstable
Urgency: medium
Maintainer: Markus Wanner 
Changed-By: Markus Wanner 
Description:
 courier-base - Courier mail server - base system
 courier-doc - Courier mail server - additional documentation
 courier-faxmail - Courier mail server - Fax<->mail gateway
 courier-imap - Courier mail server - IMAP server
 courier-imap-ssl - Courier mail server - IMAP over TLS [transitional]
 courier-ldap - Courier mail server - LDAP support
 courier-maildrop - Courier mail server - mail delivery agent [transitional 
package]
 courier-mlm - Courier mail server - mailing list manager
 courier-mta - Courier mail server - ESMTP daemon
 courier-mta-ssl - Courier mail server - ESMTP over TLS [transitional]
 courier-pcp - Courier mail server - PCP server
 courier-pop - Courier mail server - POP3 server
 courier-pop-ssl - Courier mail server - POP3 over TLS [transitional]
 courier-ssl - Courier mail server - TLS Support [transitional]
 courier-webadmin - Courier mail server - web-based administration frontend
 sqwebmail  - Courier mail server - webmail server
Closes: 832278 871400 871586
Changes:
 courier (0.77.0-1) unstable; urgency=medium
 .
   * New upstream release. Closes: #871586.
   * Restrict build dependency on courier-unicode to 2.0 and newer.
   * Drop patches 0001-Include-cstdio-in-afx.h.patch
 0005-Ignore-and-.dpkg-a-z-files.patch, 0007-Fix-bashisms.patch,
 0009-Fix-linking-in-upstream-Makefiles.patch,
 0013-Add-P-to-ghostscript-invocation.patch,
 0014-Improve-error-reporting-in-preline.c.patch,
 0017-Fix-formatting-errors-in-syslog-calls.patch,
 0020-Add-perl-stanza-to-perlfilter-scripts.patch, and
 0026-Fix-TLS-verification-for-CNAMEs.patch: all of these got applied
 upstream.
   * Refresh patches 0010-Don-t-use-static-linking-in-libs-maildir.patch,
 0019-Remove-upstream-chown-on-install-target.patch,
 0022-mkesmtpdcert-should-use-certsdir.patch,
 0023-Fix-missing-AC_PROG_SYSCONFTOOL-macro-on-autoreconf.patch, and
 0024-Dynamically-resolver-mailuid-and-mailgid-on-runtime-.patch
   * Refresh, merge and simplify patch
 0012-Define-and-use-PEMFILE-in-mkesmtpdcert.patch
   * Drop bogus links to pem files.
   * Correct permissions on /etc/courier/esmtpauthclient in postinst
 script of courier-mta 

Processed: Definively a castxml bug

[Debian Bug Tracking System]

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

> retitle 871573  error: invalid operands to binary expression
Bug #871573 [src:insighttoolkit4] insighttoolkit4 fails to build from source
Changed Bug title to 'error: invalid operands to binary expression' from 
'insighttoolkit4 fails to build from source'.
> reassign 871573 castxml
Bug #871573 [src:insighttoolkit4] error: invalid operands to binary expression
Bug reassigned from package 'src:insighttoolkit4' to 'castxml'.
No longer marked as found in versions insighttoolkit4/4.12.0-dfsg1-1.
Ignoring request to alter fixed versions of bug #871573 to the same values 
previously set
> affects 871573 insighttoolkit4
Bug #871573 [castxml] error: invalid operands to binary expression
Added indication that 871573 affects insighttoolkit4
> forwarded 871573 https://github.com/CastXML/CastXML/issues/87
Bug #871573 [castxml] error: invalid operands to binary expression
Set Bug forwarded-to-address to 'https://github.com/CastXML/CastXML/issues/87'.
>
End of message, stopping processing here.

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

Bug#846314: alot: Migrate from pygpgme to python-gpg

[Jordan Justen]

On 2017-07-08 08:43:18, Jonathan Wiltshire wrote:
> I will be requesting removal of pygpgme from unstable at the end of
> this month (but it's up to ftp masters if they do so immediately and break
> things, or wait for dependencies to be resolved).

Jonathan, I wanted to give an update for 'alot' and the pygpgme
dependency. An upstream developer picked up the patch and rebased it.
While verifying it he discovered other GPG bugs in 'alot'. I believe
those bugs have been fixed, but the pygpgme=>python-gpg bug is just
now being finished up:

https://github.com/pazz/alot/pull/1086

Upstream plans to do a new release soon with all these GPG updates.
(Hopefully within a week base on the conversation in the pull request
above.)

I thought it was best to hold off on trying to merge the patch into
the older release when a new upstream release should address the
dependency issue soon.

I'm not sure if/when sid might lose pygpgme, but hopefully we'll have
a new upstream release of 'alot' to address the dependency issue
before that happens.

-Jordan


signature.asc
Description: signature

Bug#871629: thunderbird UI unusable with many widgets not drawn

[Adrian Bunk]

On Thu, Aug 10, 2017 at 04:21:10PM +1200, Ben Caradoc-Davies wrote:
> Package: thunderbird
> Version: 1:52.2.1-4+b1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> the thunderbird UI is unusable with many widgets not drawn. See attached 
> screenshot. Mouse hover causes some to be drawn.
>...

This is likely caused by the binNMU for the libevent transition,
that resulted in thunderbird being recompiled with gcc 7.

Similar problems were observed in firefox{,-esr}, workarounded there by 
using gcc-6/g++-6 in unstable for now.

> Kind regards,
> Ben.

cu
Adrian

-- 

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

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

[Rafael Laboissière]

* Adrian Bunk  [2017-08-07 01:57]:


Source: octave-image
Version: 2.6.1-1
Severity: serious
Tags: buster sid

Some recent change in unstable and buster makes octave-image FTBFS on i386:

 https://tests.reproducible-builds.org/debian/history/octave-image.html
 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/octave-image.html

 ...
 Checking CC files ...
 warning: function /build/1st/octave-image-2.6.1/inst/private/iscolormap.m 
shadows a core library function
 warning: called from
/tmp/filePMKFm8 at line 1 column 1
 [__spatial_filtering__]
 PASSES 21 out of 21 tests
 [graycomatrix]
 PASSES 2 out of 2 tests
 [watershed]
 * test
 im = [
 2 330 2
 330 330
   2553130 4
 2   2553130
 1 2   255 5];

 labeled8 = [
 1 1 0 3
 1 1 0 3
 0 0 0 0
 2 2 0 4
 2 2 0 4];
 assert (watershed (im), labeled8);
 assert (watershed (im, 8), labeled8);
 ! test failed
 ASSERT errors for:  assert (watershed (im),labeled8)

  Location  |  Observed  |  Expected  |  Reason
   (3,4)  30 Abs err 3 exceeds tol 0
   (4,4)  04 Abs err 4 exceeds tol 0
 [bwdist]
 Sat Sep  8 05:36:25 UTC 2018 - pbuilder was killed by timeout after 18h.


I would guess that the culprit is the following unit test in bwdist:

## The quasi-euclidean method is apparently sensitive to a machine precision
## error that happens in x86 systems only. This test will cause an endless
## loop in case of a regression.
%!test
%! bw = [  0   1   1   0   0   0   1   0
%! 0   0   0   0   0   0   0   0
%! 1   1   0   0   0   0   0   0
%! 0   0   0   0   0   0   1   0
%! 0   0   0   0   1   0   0   1
%! 0   0   0   0   0   0   0   0
%! 1   0   0   0   0   0   0   0
%! 0   0   1   0   0   1   1   0];
%! out = single ([
%! 1.0   0.0   0.0   1.0   2.0   1.0   0.0   1.0
%! 1.0   1.0   1.0   sqrt(2)   sqrt(2)+1 sqrt(2)   1.0   sqrt(2)
%! 0.0   0.0   1.0   2.0   2.0   sqrt(2)   1.0   sqrt(2)
%! 1.0   1.0   sqrt(2)   sqrt(2)   1.0   1.0   0.0   1.0
%! 2.0   2.0   2.0   1.0   0.0   1.0   1.0   0.0
%! 1.0   sqrt(2)   2.0   sqrt(2)   1.0   sqrt(2)   sqrt(2)   1.0
%! 0.0   1.0   1.0   sqrt(2)   sqrt(2)   1.0   1.0   sqrt(2)
%! 1.0   1.0   0.0   1.0   1.0   0.0   0.0   1.0
%! ]);
%! assert (bwdist (bw, "quasi-euclidean"), out);

Should we run the test above only on non-x86 architectures?

Rafael





___ 
Pkg-octave-devel mailing list 
pkg-octave-de...@lists.alioth.debian.org 
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-octave-devel

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

[Rafael Laboissière]

* Sébastien Villemot  [2017-08-10 11:06]:


Le jeudi 10 août 2017 à 09:31 +0200, Rafael Laboissière a écrit :

* Adrian Bunk  [2017-08-07 01:57]:



Source: octave-image
Version: 2.6.1-1
Severity: serious
Tags: buster sid

Some recent change in unstable and buster makes octave-image FTBFS on i386:

 https://tests.reproducible-builds.org/debian/history/octave-image.html
 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/octave-image.html

 [snip]
 [bwdist]
 Sat Sep  8 05:36:25 UTC 2018 - pbuilder was killed by timeout after 18h.


I would guess that the culprit is the following unit test in bwdist:

 [snip]



Should we run the test above only on non-x86 architectures?


I would rather patch the test to allow for some tolerance margin.


I suspect that the test enters a infinite loop and, therefore, changing 
the tolerance margin will not help here.


Rafael

Bug#871629: thunderbird UI unusable with many widgets not drawn

[Ben Caradoc-Davies]

Downgrading to thunderbird and lightning 52.2.1-4 restores usability. 
Reinstallation of libevent-2.0-5 (autoremoved) is also required.


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#866172: closing 866172

[Michael Stapelberg]

close 866172 3.0.0-1
thanks
-- 
Best regards,
Michael

Processed: closing 866172

[Debian Bug Tracking System]

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

> close 866172 3.0.0-1
Bug #866172 [src:golang-github-minio-minio-go] golang-github-minio-minio-go 
FTBFS: FAIL: TestGetEndpointURL
Marked as fixed in versions golang-github-minio-minio-go/3.0.0-1.
Bug #866172 [src:golang-github-minio-minio-go] golang-github-minio-minio-go 
FTBFS: FAIL: TestGetEndpointURL
Marked Bug as done
> thanks
Stopping processing here.

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

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

[Sébastien Villemot]

Le jeudi 10 août 2017 à 09:31 +0200, Rafael Laboissière a écrit :
> > * Adrian Bunk  [2017-08-07 01:57]:
> 
> > Source: octave-image
> > Version: 2.6.1-1
> > Severity: serious
> > Tags: buster sid
> > 
> > Some recent change in unstable and buster makes octave-image FTBFS on i386:
> > 
> >  https://tests.reproducible-builds.org/debian/history/octave-image.html
> >  
> > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/octave-image.html
> > 
> >  ...
> >  Checking CC files ...
> >  warning: function /build/1st/octave-image-2.6.1/inst/private/iscolormap.m 
> > shadows a core library function
> >  warning: called from
> > /tmp/filePMKFm8 at line 1 column 1
> >  [__spatial_filtering__]
> >  PASSES 21 out of 21 tests
> >  [graycomatrix]
> >  PASSES 2 out of 2 tests
> >  [watershed]
> >  * test
> >  im = [
> >  2 330 2
> >  330 330
> >    2553130 4
> >  2   2553130
> >  1 2   255 5];
> > 
> >  labeled8 = [
> >  1 1 0 3
> >  1 1 0 3
> >  0 0 0 0
> >  2 2 0 4
> >  2 2 0 4];
> >  assert (watershed (im), labeled8);
> >  assert (watershed (im, 8), labeled8);
> >  ! test failed
> >  ASSERT errors for:  assert (watershed (im),labeled8)
> > 
> >   Location  |  Observed  |  Expected  |  Reason
> >    (3,4)  30 Abs err 3 exceeds tol 0
> >    (4,4)  04 Abs err 4 exceeds tol 0
> >  [bwdist]
> >  Sat Sep  8 05:36:25 UTC 2018 - pbuilder was killed by timeout after 18h.
> 
> I would guess that the culprit is the following unit test in bwdist:
> 
>  ## The quasi-euclidean method is apparently sensitive to a machine precision
>  ## error that happens in x86 systems only. This test will cause an endless
>  ## loop in case of a regression.
>  %!test
>  %! bw = [  0   1   1   0   0   0   1   0
>  %! 0   0   0   0   0   0   0   0
>  %! 1   1   0   0   0   0   0   0
>  %! 0   0   0   0   0   0   1   0
>  %! 0   0   0   0   1   0   0   1
>  %! 0   0   0   0   0   0   0   0
>  %! 1   0   0   0   0   0   0   0
>  %! 0   0   1   0   0   1   1   0];
>  %! out = single ([
>  %! 1.0   0.0   0.0   1.0   2.0   1.0   0.0   
> 1.0
>  %! 1.0   1.0   1.0   sqrt(2)   sqrt(2)+1 sqrt(2)   1.0   
> sqrt(2)
>  %! 0.0   0.0   1.0   2.0   2.0   sqrt(2)   1.0   
> sqrt(2)
>  %! 1.0   1.0   sqrt(2)   sqrt(2)   1.0   1.0   0.0   
> 1.0
>  %! 2.0   2.0   2.0   1.0   0.0   1.0   1.0   
> 0.0
>  %! 1.0   sqrt(2)   2.0   sqrt(2)   1.0   sqrt(2)   sqrt(2)   
> 1.0
>  %! 0.0   1.0   1.0   sqrt(2)   sqrt(2)   1.0   1.0   
> sqrt(2)
>  %! 1.0   1.0   0.0   1.0   1.0   0.0   0.0   
> 1.0
>  %! ]);
>  %! assert (bwdist (bw, "quasi-euclidean"), out);
> 
> Should we run the test above only on non-x86 architectures?

I would rather patch the test to allow for some tolerance margin.

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

Bug#871370: Pending fixes for bugs in the libgettext-commons-java package

[pkg-java-maintainers]

tag 871370 + pending
thanks

Some bugs in the libgettext-commons-java package are closed in
revision 1efc5b4490f97cfe659645755eebf9230446bc0b in branch 'master'
by Tom Marble

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/libgettext-commons-java.git/commit/?id=1efc5b4

Commit message:

Added (Closes: #871370) to changelog

Signed-off-by: Tom Marble 

Bug#871282: insighttoolkit4.10: requires rebuild against GCC 7 and symbols/shlibs bump

[Matthias Klose]

Control: tags -1 - wontfix

> Version 4.12 is in unstable, was already build using gcc-7, and will
> soon transition to testing thereby removing v4.10 from the archives.

No, it is not. According to the build logs at least 4.12.0-dfsg1-1 on i386 was
built using gcc-6. You really should fix that. The package has a lot of
dependencies, so please don't ignore that.

Bug#853666: marked as done (spades: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Thu, 10 Aug 2017 15:38:20 +
with message-id 
and subject line Bug#853666: fixed in spades 3.10.1+dfsg-3
has caused the Debian Bug report #853666,
regarding spades: 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.)


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

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]
  ^~~~
/<>/spades-3.9.1+dfsg/src/modules/dev_support/segfault_handler.hpp:21:33:
 error: expected ')' before 'const'
 segfault_handler(callback_t const  = 0) {
 ^
/<>/spades-3.9.1+dfsg/src/modules/dev_support/segfault_handler.hpp:35:12:
 error: 'callback_t' does not name a type; did you mean 'clock_t'?
 static callback_t () {
^~
clock_t
/<>/spades-3.9.1+dfsg/src/modules/dev_support/segfault_handler.hpp: 
In destructor 'segfault_handler::~segfault_handler()':
/<>/spades-3.9.1+dfsg/src/modules/dev_support/segfault_handler.hpp:30:9:
 error: 'callback' was not declared in this scope
 callback() = 0;
 ^~~~
/<>/spades-3.9.1+dfsg/src/modules/dev_support/segfault_handler.hpp:30:9:
 note: suggested alternative: 'calloc'
 callback() = 0;
 ^~~~
 calloc
/<>/spades-3.9.1+dfsg/src/modules/dev_support/segfault_handler.hpp: 
In static member function 'static void segfault_handler::handler(int)':
/<>/spades-3.9.1+dfsg/src/modules/dev_support/segfault_handler.hpp:45:17:
 error: 'callback' was not declared in this scope
 if (callback())
 ^~~~
/<>/spades-3.9.1+dfsg/src/modules/dev_support/segfault_handler.hpp:45:17:
 note: suggested alternative: 'calloc'
 if (callback())
 ^~~~
 calloc
In file included from 
/<>/spades-3.9.1+dfsg/src/modules/data_structures/sequence/seq.hpp:38:0,
 from 
/<>/spades-3.9.1+dfsg/src/modules/data_structures/sequence/sequence.hpp:16,
 from 
/<>/spades-3.9.1+dfsg/src/modules/data_structures/indices/edge_info_updater.hpp:12,
 from 
/<>/spades-3.9.1+dfsg/src/modules/data_structures/indices/edge_position_index.hpp:11,
 from 
/<>/spades-3.9.1+dfsg/src/modules/pipeline/graph_pack.hpp:10,
 from 
/<>/spades-3.9.1+dfsg/src/projects/spades/launch.hpp:12,
 from 
/<>/spades-3.9.1+dfsg/src/projects/spades/main.cpp:15:
/<>/spades-3.9.1+dfsg/src/modules/data_structures/sequence/nucl.hpp: 
In member function 'bool nucl_complement_functor::operator()(char) const':
/<>/spades-3.9.1+dfsg/src/modules/data_structures/sequence/nucl.hpp:84:19:
 warning: ?: using integer constants in boolean context [-Wint-in-bool-context]
 return cc ? cc : 'N';
~~~^~
projects/spades/CMakeFiles/spades.dir/build.make:62: recipe for target 
'projects/spades/CMakeFiles/spades.dir/main.cpp.o' failed
make[4]: *** [projects/spades/CMakeFiles/spades.dir/main.cpp.o] Error 1
make[4]: Leaving directory '/<>/spades-3.9.1+dfsg/build_spades'
CMakeFiles/Makefile2:1421: recipe for target 
'projects/spades/CMakeFiles/spades.dir/all' failed
make[3]: *** [projects/spades/CMakeFiles/spades.dir/all] Error 2
make[3]: Leaving 

Processed: Re: insighttoolkit4.10: requires rebuild against GCC 7 and symbols/shlibs bump

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - wontfix
Bug #871282 [libinsighttoolkit4.10] libinsighttoolkit4.10: requires rebuild 
against GCC 7 and symbols/shlibs bump
Removed tag(s) wontfix.

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

Bug#869774: Enigmail update broke ppc support

[Daniel Kahn Gillmor]

Hi there Stiepan--

On Wed 2017-08-09 01:21:38 +0200, Stiepan Aurélien Kovac wrote:
> seems to have broken enigmail support, at least on the ppc (powerpc64) arch.

I don't think this is a ppc-specific issue -- nothing in the current
version of enigmail is debian-specific.  I also think your issue has
more to do with enigmail and thunderbird on jessie itself.  Your
situation i think has more to do with https://bugs.debian.org/870073
than with https://bugs.debian.org/869774.

> "enigmail is incompatible with thunderbird 45.8.0" (shows up in add-ons 
> manager)

This makes it look like you haven't upgraded thunderbird on your jessie
installation.  the version of thunderbird available from
security.debian.org is 1:52.2.1-4~deb8u1. (see:
https://packages.debian.org/source/oldstable/icedove)


If you are running jessie, please:

 * upgrade to the supported version of thunderbird that has security
   fixes

 * ensure that you have "use-agent" in your ~/.gnupg/gpg.conf

 * ensure that gnome-keyring is not presenting a gpg-agent interface
   (see https://bugs.debian.org/870073 for more discussion about
   thunderbird and enigmail on debian jessie)

Regards,

--dkg


signature.asc
Description: PGP signature

Bug#871692: gobgp FTBFS on arm64: Test killed with quit: ran too long (10m0s).

[Adrian Bunk]

Source: gobgp
Version: 1.22-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=gobgp=arm64=1.22-1=1502350034=0

...
goroutine 93 [select]:
github.com/osrg/gobgp/server.(*FSMHandler).opensent(0x4420336140, 0x0, 0x0, 0x0)

/<>/obj-aarch64-linux-gnu/src/github.com/osrg/gobgp/server/fsm.go:944
 +0x2110
github.com/osrg/gobgp/server.(*FSMHandler).loop.func1(0x0, 0x0)

/<>/obj-aarch64-linux-gnu/src/github.com/osrg/gobgp/server/fsm.go:1462
 +0x154
gopkg.in/tomb%2ev2.(*Tomb).run(0x4420336140, 0x4420311e20)
gopkg.in/tomb.v2/tomb.go:163 +0x20
created by gopkg.in/tomb%2ev2.(*Tomb).Go
gopkg.in/tomb.v2/tomb.go:159 +0xb8

r0  0xcea6d0
r1  0x0
r2  0x0
r3  0x0
r4  0x0
r5  0x0
r6  0x1
r7  0x442001e208
r8  0x62
r9  0xf98
r10 0x441ffe1110
r11 0x0
r12 0x0
r13 0xf3
r14 0x38
r15 0x1
r16 0x1
r17 0x4420238660
r18 0x4091e
r19 0x3c
r20 0x0
r21 0x5a
r22 0x0
r23 0x17
r24 0x18
r25 0x9201c0
r26 0x9ff3b0
r27 0x40
r28 0xcea040
r29 0xe4b3a8f0
lr  0x42647c
sp  0xe4b3a6e0
pc  0x452d2c
fault   0x0
*** Test killed with quit: ran too long (10m0s).
FAILgithub.com/osrg/gobgp/server600.009s

Processed: re: libinsighttoolkit4.10: requires rebuild against GCC 7 and symbols/shlibs bump

[Debian Bug Tracking System]

Processing control commands:

> tags -1 -wontfix
Bug #871282 [libinsighttoolkit4.10] libinsighttoolkit4.10: requires rebuild 
against GCC 7 and symbols/shlibs bump
Ignoring request to alter tags of bug #871282 to the same tags previously set
> block -1  by 871573
Bug #871282 [libinsighttoolkit4.10] libinsighttoolkit4.10: requires rebuild 
against GCC 7 and symbols/shlibs bump
871282 was not blocked by any bugs.
871282 was not blocking any bugs.
Added blocking bug(s) of 871282: 871573
> block 871677 by 871573
Bug #871677 [src:insighttoolkit4] insighttoolkit4 ftbfs with GCC 7 (castxml out 
of date)
871677 was not blocked by any bugs.
871677 was not blocking any bugs.
Added blocking bug(s) of 871677: 871573

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

Bug#871282: libinsighttoolkit4.10: requires rebuild against GCC 7 and symbols/shlibs bump

[Gert Wollny]

Control: tags -1 -wontfix 
Control: block -1  by 871573
Control: block 871677 by 871573

I was getting to that, first I had to check #871573. 

Well, before that I thought I had it uploaded after gcc-7 became the
default (I'm  quite positive that I built it with an older version of
gcc-7) and since the bug was filed against 4.10 I didn't check. 

For now insighttoolkit4 doesn't build anyway, and we'll have to wait
for upstream to fix #871573. 

Best, 
Gert 

Bug#871300: [Pkg-gmagick-im-team] Bug#871300: libmagick++-6.q16-7: requires rebuild against GCC 7 and symbols/shlibs bump

[James Cowgill]

Hi,

On 08/08/17 06:38, Bastien Roucaries wrote:
> Le 7 août 2017 22:59:06 GMT+02:00, James Cowgill  a 
> écrit :
>> On 07/08/17 16:55, roucaries bastien wrote:
>>> On Mon, Aug 7, 2017 at 4:47 PM,   wrote:
 Package: libmagick++-6.q16-7
 Version: 8:6.9.7.4+dfsg-16
 Severity: serious
 Tags: sid buster
 User: debian-...@lists.debian.org
 Usertags: gcc-7-op-mangling

>>>
>>> I need a change that break ABI, I will release a new version. Does it
>>> exist in this case a short cut
>>
>> If you are going to rename the Debian package and trigger a package
>> transition, you do not need to add any of the extra symbols/shlibs
>> stuff. You should still build-depend on gcc (>= 4:7) however - I'm not
>> sure if all the buildds use GCC 7 by default yet.
> 
>  Should i depends on g++7 for libmagick++-dev ?

I don't think you need to do that. Consumers of your library don't need
to be running gcc-7 (it should work with gcc-6 and gcc-7). Your library
does need to be built using gcc-7 so that it is compatible with both
compilers.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Processed: affects 853658

[Debian Bug Tracking System]

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

> affects 853658 src:otb
Bug #853658 [src:shark] shark: ftbfs with GCC-7
Added indication that 853658 affects src:otb
> thanks
Stopping processing here.

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

Bug#869774: Enigmail update broke ppc support

[Stiepan Aurélien Kovac]

Hi Daniel,

Thank you for your reply.

I have checked my Thunderbird version and I have the latest available
one on my platform:

"apt-cache policy thunderbird
thunderbird:
  Installed: 1:45.8.0-3~deb8u1
  Candidate: 1:45.8.0-3~deb8u1"

(also according to https://tracker.debian.org/pkg/icedove)

I have checked bug

https://bugs.debian.org/870073

but I do not think that we have the same issue:

I didn't have to restart gpg-agent when installing the version I have
compiled of enigmail...

(and I don't use gnome, nor its keyring, at least not that I am, nor ps
aux | grep's aware of)

So I still think that this bug should be reopened for the specific
architecture that I am using.

(in clear, that Bug #869774 should be reopened for PPC)

Regards,

Stiepan


On 08/10/17 15:12, Daniel Kahn Gillmor wrote:
> Hi there Stiepan--
>
> On Wed 2017-08-09 01:21:38 +0200, Stiepan Aurélien Kovac wrote:
>> seems to have broken enigmail support, at least on the ppc (powerpc64) arch.
> I don't think this is a ppc-specific issue -- nothing in the current
> version of enigmail is debian-specific.  I also think your issue has
> more to do with enigmail and thunderbird on jessie itself.  Your
> situation i think has more to do with https://bugs.debian.org/870073
> than with https://bugs.debian.org/869774.
>
>> "enigmail is incompatible with thunderbird 45.8.0" (shows up in add-ons 
>> manager)
> This makes it look like you haven't upgraded thunderbird on your jessie
> installation.  the version of thunderbird available from
> security.debian.org is 1:52.2.1-4~deb8u1. (see:
> https://packages.debian.org/source/oldstable/icedove)
>
>
> If you are running jessie, please:
>
>  * upgrade to the supported version of thunderbird that has security
>fixes
>
>  * ensure that you have "use-agent" in your ~/.gnupg/gpg.conf
>
>  * ensure that gnome-keyring is not presenting a gpg-agent interface
>(see https://bugs.debian.org/870073 for more discussion about
>thunderbird and enigmail on debian jessie)
>
> Regards,
>
> --dkg

-- 
Stiepan A. Kovac
M Sc ICT Security
IT+Tech. Tel. Eng.

Processed: Re: Bug#871538: Makes apparmor FTBFS on mips64el (generated code thinks that 1 > 1)

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 871514 871538
Bug #871514 [gcc-7] clamav: FTBFS on mips64el
Bug #871538 [gcc-7] Makes apparmor FTBFS on mips64el (generated code thinks 
that 1 > 1)
Severity set to 'serious' from 'important'
Removed indication that 871538 affects apparmor
Added indication that 871538 affects clamav
Merged 871514 871538
> affects 871514 apparmor
Bug #871514 [gcc-7] clamav: FTBFS on mips64el
Bug #871538 [gcc-7] Makes apparmor FTBFS on mips64el (generated code thinks 
that 1 > 1)
Added indication that 871514 affects apparmor
Added indication that 871538 affects apparmor
> affects 871514 clamav
Bug #871514 [gcc-7] clamav: FTBFS on mips64el
Bug #871538 [gcc-7] Makes apparmor FTBFS on mips64el (generated code thinks 
that 1 > 1)
Ignoring request to set affects of bug 871514 to the same value previously set
Ignoring request to set affects of bug 871538 to the same value previously set

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

Processed: bug 871514 is forwarded to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81803

[Debian Bug Tracking System]

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

> forwarded 871514 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81803
Bug #871514 [gcc-7] clamav: FTBFS on mips64el
Bug #871538 [gcc-7] Makes apparmor FTBFS on mips64el (generated code thinks 
that 1 > 1)
Set Bug forwarded-to-address to 
'https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81803'.
Set Bug forwarded-to-address to 
'https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81803'.
> 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
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#871689: mpich FTBFS on armhf: FAIL: test_primitives

[Adrian Bunk]

Source: mpich
Version: 3.3~a2-2
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=mpich=armhf=3.3~a2-2=1502381558=0

...
FAIL: test_primitives
=

Testing simple integer load/store functionalityPASSED
Testing simple pointer load/store functionalityPASSED
Testing simple add/incr/decr functionality PASSED
Testing simple decr and test functionality PASSED
Testing simple fetch and add/incr/decr functionality   PASSED
Testing simple integer compare-and-swap functionality  PASSED
Testing simple pointer compare-and-swap functionality  PASSED
Testing simple integer swap functionality  PASSED
Testing simple pointer swap functionality  PASSED
Testing simple integer load-linked/store-conditional functionality PASSED
Testing simple pointer load-linked/store-conditional functionality PASSED
Testing integer LL/SC ABA with 2 threads   PASSED
False positives: 89 / 156
Testing pointer LL/SC ABA with 2 threads   PASSED
False positives: 78 / 999581
Testing integer load/store with 1 thread   PASSED
Testing pointer load/store with 1 thread   PASSED
Testing add with 1 thread  PASSED
Testing incr and decr with 1 threadPASSED
Testing decr and test with 1 threadPASSED
Testing fetch and add with 1 threadPASSED
Testing fetch and add return values with 1 thread  PASSED
Testing fetch and incr/decr with 1 thread  PASSED
Testing fetch and incr return values with 1 thread PASSED
Testing fetch and decr return values with 1 thread PASSED
Testing integer compare-and-swap with 1 thread PASSED
Testing pointer compare-and-swap with 1 thread PASSED
Testing grouped integer compare-and-swap with 1 thread PASSED
Testing grouped pointer compare-and-swap with 1 thread PASSED
Testing integer compare-and-swap fairness with 1 threadPASSED
Testing pointer compare-and-swap fairness with 1 threadPASSED
Testing integer swap with 1 thread PASSED
Testing pointer swap with 1 thread PASSED
Testing integer load/store with 2 threads  PASSED
Testing pointer load/store with 2 threads  PASSED
Testing add with 2 threads PASSED
Testing incr and decr with 1 threadPASSED
Testing decr and test with 2 threads   PASSED
Testing fetch and add with 2 threads   PASSED
Testing fetch and add return values with 2 threads PASSED
Testing fetch and incr/decr with 1 thread  PASSED
Testing fetch and incr return values with 2 threadsPASSED
Testing fetch and decr return values with 2 threadsPASSED
Testing integer compare-and-swap with 2 threadsPASSED
Testing pointer compare-and-swap with 2 threadsPASSED
Testing grouped integer compare-and-swap with 2 threadsPASSED
Testing grouped pointer compare-and-swap with 2 threadsPASSED
Testing integer compare-and-swap fairness with 2 threads   PASSED
Testing pointer compare-and-swap fairness with 2 threads   PASSED
Testing integer swap with 2 threadsPASSED
Testing pointer swap with 2 threadsPASSED
Testing integer LL/SC stack with 2 threads PASSED
Testing pointer LL/SC stack with 2 threads PASSED
Testing integer load/store with 4 threads  PASSED
Testing pointer load/store with 4 threads  PASSED
Testing add with 4 threads PASSED
Testing incr and decr with 3 threads   PASSED
Testing decr and test with 4 threads   PASSED
Testing fetch and add with 4 threads   PASSED
Testing fetch and add return values with 4 threads PASSED
Testing fetch and incr/decr with 3 threads PASSED
Testing fetch and incr return values with 4 threadsPASSED
Testing fetch and decr return values with 4 threads   

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
> #  * closed 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
Added tag(s) fixed-upstream.
> usertags 871190 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> 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#871691: nss FTBFS on big endian: cpputil/databuffer.h:96:14: error: 'curve' may be used uninitialized in this function

[Adrian Bunk]

Source: nss
Version: 2:3.32-1
Severity: serious

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

...
In file included from test_io.h:17:0,
 from gtest_utils.h:12,
 from ssl_ecdh_unittest.cc:19:
../../cpputil/databuffer.h: In member function 'virtual 
nss_test::PacketFilter::Action 
nss_test::ECCServerKEXFilter::FilterHandshake(const 
nss_test::TlsHandshakeFilter::HandshakeHeader&, const nss_test::DataBuffer&, 
nss_test::DataBuffer*)':
../../cpputil/databuffer.h:96:14: error: 'curve' may be used uninitialized in 
this function [-Werror=maybe-uninitialized]
 uint32_t nvalue = htonl(val);
  ^~
ssl_ecdh_unittest.cc:554:14: note: 'curve' was declared here
 uint32_t curve;
  ^
cc1plus: all warnings being treated as errors
../../coreconf/rules.mk:444: recipe for target 'OBJS/ssl_ecdh_unittest.o' failed
make[4]: *** [OBJS/ssl_ecdh_unittest.o] Error 1

Processed: [bts-link] source package src:rubocop

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:rubocop
> # 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 #870852 (http://bugs.debian.org/870852)
> # Bug title: rubocop: CVE-2017-8418
> #  * https://github.com/bbatsov/rubocop/issues/4336
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 870852 + fixed-upstream
Bug #870852 [src:rubocop] rubocop: CVE-2017-8418
Added tag(s) fixed-upstream.
> usertags 870852 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:jackson-databind

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:jackson-databind
> # 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 #870848 (http://bugs.debian.org/870848)
> # Bug title: jackson-databind: CVE-2017-7525: Deserialization vulnerability 
> via readValue method of ObjectMapper
> #  * https://github.com/FasterXML/jackson-databind/issues/1599
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 870848 + fixed-upstream
Bug #870848 [src:jackson-databind] jackson-databind: CVE-2017-7525: 
Deserialization vulnerability via readValue method of ObjectMapper
Added tag(s) fixed-upstream.
> usertags 870848 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:libtomcrypt

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:libtomcrypt
> # 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 #871109 (http://bugs.debian.org/871109)
> # Bug title: libtomcrypt: FTBFS: Fatal error occurred, no output PDF file 
> produced!
> #  * https://github.com/libtom/libtomcrypt/pull/255
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 871109 + fixed-upstream
Bug #871109 [src:libtomcrypt] libtomcrypt: FTBFS: Fatal error occurred, no 
output PDF file produced!
Added tag(s) fixed-upstream.
> usertags 871109 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:pinfo

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:pinfo
> # 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 #853613 (http://bugs.debian.org/853613)
> # Bug title: gcc-7 with -Os: undefined references to inline functions
> #  * http://gcc.gnu.org/PR81734
> #  * remote status changed: (?) -> RESOLVED
> #  * remote resolution changed: (?) -> INVALID
> #  * closed upstream
> tags 853613 + fixed-upstream
Bug #853613 [src:pinfo] gcc-7 with -Os: undefined references to inline functions
Added tag(s) fixed-upstream.
> usertags 853613 + status-RESOLVED resolution-INVALID
There were no usertags set.
Usertags are now: status-RESOLVED resolution-INVALID.
> thanks
Stopping processing here.

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

Bug#871248: marked as done (ovito FTBFS on architectures where char is unsigned)

[Debian Bug Tracking System]

Your message dated Thu, 10 Aug 2017 17:50:22 +
with message-id 
and subject line Bug#871248: fixed in ovito 2.9.0+dfsg1-2
has caused the Debian Bug report #871248,
regarding ovito FTBFS on architectures where char is unsigned
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.)


-- 
871248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871248
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ovito
Version: 2.9.0+dfsg1-1
Severity: serious

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

...
In file included from 
/<>/ovito-2.9.0+dfsg1/src/plugins/particles/modifier/fields/MarchingCubes.cpp:24:0:
/<>/ovito-2.9.0+dfsg1/src/plugins/particles/modifier/fields/MarchingCubesLookupTable.h:301:1:
 error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
 };
 ^
/<>/ovito-2.9.0+dfsg1/src/plugins/particles/modifier/fields/MarchingCubesLookupTable.h:301:1:
 error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/ovito-2.9.0+dfsg1/src/plugins/particles/modifier/fields/MarchingCubesLookupTable.h:416:1:
 error: narrowing conversion of '-6' from 'int' to 'char' inside { } 
[-Wnarrowing]
 };
 ^
/<>/ovito-2.9.0+dfsg1/src/plugins/particles/modifier/fields/MarchingCubesLookupTable.h:416:1:
 error: narrowing conversion of '-6' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/ovito-2.9.0+dfsg1/src/plugins/particles/modifier/fields/MarchingCubesLookupTable.h:416:1:
 error: narrowing conversion of '-3' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/ovito-2.9.0+dfsg1/src/plugins/particles/modifier/fields/MarchingCubesLookupTable.h:416:1:
 error: narrowing conversion of '-4' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/ovito-2.9.0+dfsg1/src/plugins/particles/modifier/fields/MarchingCubesLookupTable.h:416:1:
 error: narrowing conversion of '-3' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/ovito-2.9.0+dfsg1/src/plugins/particles/modifier/fields/MarchingCubesLookupTable.h:416:1:
 error: narrowing conversion of '-2' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/ovito-2.9.0+dfsg1/src/plugins/particles/modifier/fields/MarchingCubesLookupTable.h:416:1:
 error: narrowing conversion of '-2' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/ovito-2.9.0+dfsg1/src/plugins/particles/modifier/fields/MarchingCubesLookupTable.h:416:1:
 error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/ovito-2.9.0+dfsg1/src/plugins/particles/modifier/fields/MarchingCubesLookupTable.h:416:1:
 error: narrowing conversion of '-5' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/ovito-2.9.0+dfsg1/src/plugins/particles/modifier/fields/MarchingCubesLookupTable.h:416:1:
 error: narrowing conversion of '-4' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/ovito-2.9.0+dfsg1/src/plugins/particles/modifier/fields/MarchingCubesLookupTable.h:416:1:
 error: narrowing conversion of '-1' from 'int' to 'char' inside { } 
[-Wnarrowing]
/<>/ovito-2.9.0+dfsg1/src/plugins/particles/modifier/fields/MarchingCubesLookupTable.h:416:1:
 error: narrowing conversion of '-5' from 'int' to 'char' inside { } 
[-Wnarrowing]
...
--- End Message ---
--- Begin Message ---
Source: ovito
Source-Version: 2.9.0+dfsg1-2

We believe that the bug you reported is fixed in the latest version of
ovito, 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.
Anton Gladky  (supplier of updated ovito 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, 10 Aug 2017 19:44:59 +0200
Source: ovito
Binary: ovito ovito-doc
Architecture: source
Version: 2.9.0+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Anton Gladky 
Description:
 ovito  - visualization and analysis tool for atomistic simulation data
 ovito-doc  - documentation for ovito
Closes: 871248
Changes:
 ovito (2.9.0+dfsg1-2) unstable; urgency=medium
 .
   * [cdb5bde] Fix FTBFS on archs, 

Bug#871694: bogofilter-common: bogofilter-bdb-1.2.4+dfsg1-9+b1 depends on bogofilter-common (same version),the latter does not exist

[Rann Bar-On]

Package: bogofilter-common
Version: 1.2.4+dfsg1-9
Severity: serious
Justification: 2

Dear Maintainer,

Trying to install bogofilter-bdb-1.2.4+dfsg1-9+b1 fails, due to a dependency on 
bogofilter-common of the same version, which does not exist. Seems like an 
oversight, but it blocks me from completing an upgrade. I'd really appreciate a 
fix!

Many thanks!

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

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=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

bogofilter-common depends on no packages.

bogofilter-common recommends no packages.

Versions of packages bogofilter-common suggests:
pn  doc-base  

-- no debconf information

Bug#869774: Enigmail update broke ppc support

[Stiepan Aurélien Kovac]

P.S.:

Quite weirdly, I was prompted for pinentry when looking at this message
I had just sent in the Sent folder, despite the fact that it was not
encrypted. Other than that, the self-compiled version of Enigmail works
wonders. If it has no security implications, I suggest that for powerpc,
we fall back to that version (I am referring to
https://www.enigmail.net/download/source/enigmail-1.9.7.tar.gz, for the
record). Since DSA https://www.debian.org/security/2017/dsa-3921 is
about "restoring compatibility" I think that it misses its goal and
hence, it's not wanted on PPC. If there are other (security)
implications, what are they?

Stiepan


On 08/10/17 19:40, Stiepan Aurélien Kovac wrote:
> Hi Daniel,
>
> Thank you for your reply.
>
> I have checked my Thunderbird version and I have the latest available
> one on my platform:
>
> "apt-cache policy thunderbird
> thunderbird:
>   Installed: 1:45.8.0-3~deb8u1
>   Candidate: 1:45.8.0-3~deb8u1"
>
> (also according to https://tracker.debian.org/pkg/icedove)
>
> I have checked bug
>
> https://bugs.debian.org/870073
>
> but I do not think that we have the same issue:
>
> I didn't have to restart gpg-agent when installing the version I have
> compiled of enigmail...
>
> (and I don't use gnome, nor its keyring, at least not that I am, nor ps
> aux | grep's aware of)
>
> So I still think that this bug should be reopened for the specific
> architecture that I am using.
>
> (in clear, that Bug #869774 should be reopened for PPC)
>
> Regards,
>
> Stiepan
>
>
> On 08/10/17 15:12, Daniel Kahn Gillmor wrote:
>> Hi there Stiepan--
>>
>> On Wed 2017-08-09 01:21:38 +0200, Stiepan Aurélien Kovac wrote:
>>> seems to have broken enigmail support, at least on the ppc (powerpc64) arch.
>> I don't think this is a ppc-specific issue -- nothing in the current
>> version of enigmail is debian-specific.  I also think your issue has
>> more to do with enigmail and thunderbird on jessie itself.  Your
>> situation i think has more to do with https://bugs.debian.org/870073
>> than with https://bugs.debian.org/869774.
>>
>>> "enigmail is incompatible with thunderbird 45.8.0" (shows up in add-ons 
>>> manager)
>> This makes it look like you haven't upgraded thunderbird on your jessie
>> installation.  the version of thunderbird available from
>> security.debian.org is 1:52.2.1-4~deb8u1. (see:
>> https://packages.debian.org/source/oldstable/icedove)
>>
>>
>> If you are running jessie, please:
>>
>>  * upgrade to the supported version of thunderbird that has security
>>fixes
>>
>>  * ensure that you have "use-agent" in your ~/.gnupg/gpg.conf
>>
>>  * ensure that gnome-keyring is not presenting a gpg-agent interface
>>(see https://bugs.debian.org/870073 for more discussion about
>>thunderbird and enigmail on debian jessie)
>>
>> Regards,
>>
>> --dkg


-- 
Stiepan A. Kovac
M Sc ICT Security
IT+Tech. Tel. Eng.

Bug#871647: upx-ucl: uses convenience copy of LZMA library

[Robert Luberda]

Thorsten Glaser writes:

> 
> Apparently upx-ucl reverted from using the system LZMA library
> to its own.

First of all, lzma-sdk is not designed to be used as a library, so in
fact there is no such thing like "system LZMA library". Moreover upx is
not the only package that includes its own copy of LZMA, see e.g.
https://codesearch.debian.net/search?q=__LZMA_ENCODER_H=1

> This, if not justified, is a Policy violation, for
> various reasons, including maintainability and security.
> 
> Neither the changelog entry nor README.{Debian,source} contain
> any justification, however.

The justification is simple and obvious: current upx does not compile
with the current lzma-dev.

upx requires the following files:

  compress_lzma.cpp:#include "C/Common/MyInitGuid.h"
  compress_lzma.cpp:#include "C/7zip/Compress/LZMA/LZMAEncoder.h"
  compress_lzma.cpp:#include "C/Common/Alloc.cpp"
  compress_lzma.cpp:#include "C/Common/CRC.cpp"
  compress_lzma.cpp:#include "C/7zip/Common/OutBuffer.cpp"
  compress_lzma.cpp:#include "C/7zip/Common/StreamUtils.cpp"
  compress_lzma.cpp:#include "C/7zip/Compress/LZ/LZInWindow.cpp"
  compress_lzma.cpp:#include "C/7zip/Compress/LZMA/LZMAEncoder.cpp"
  compress_lzma.cpp:#include "C/7zip/Compress/RangeCoder/RangeCoderBit.cpp"
  compress_lzma.cpp:#include "C/7zip/Compress/LZMA_C/LzmaDecode.h"
  compress_lzma.cpp:#include "C/7zip/Compress/LZMA_C/LzmaDecode.c"
  stub/src/c/lzma_d_c.c:#include "C/7zip/Compress/LZMA_C/LzmaDecode.h"
  stub/src/c/lzma_d_c.c:#include "C/7zip/Compress/LZMA_C/LzmaDecode.c"

while lzma-dev in Debian provides only:

  /usr/include/lzma/LzmaDec.c
  /usr/include/lzma/LzHash.h
  /usr/include/lzma/LzFind.h
  /usr/include/lzma/LzmaDec.h
  /usr/include/lzma/LzmaEnc.h
  /usr/include/lzma/7zVersion.h
  /usr/include/lzma/LzmaEnc.c
  /usr/include/lzma/LzFind.c
  /usr/include/lzma/Types.h

Yes, I know that I can try to request adding new files into lzma-dev, as
it was done in past, see https://bugs.debian.org/452817, but at that
time upx source did not include copy of lzma, and now it does.

Also let me quote the following upstream note from
stub/src/c/Makevars.lzma file in upx source code:

  # UPX unconditionally uses its own version in src/lzma-sdk because
  # that version works fine since 2006 and that is the only version
  # that is actually sufficiently tested!!!

Regards,
robert

Bug#871709: mercurial:CVE-2017-1000115: path traversal via symlink

[Salvatore Bonaccorso]

Source: mercurial
Version: 4.0-1
Severity: grave
Tags: upstream security
Justification: user security hole

Hi,

the following vulnerability was published for mercurial.

CVE-2017-1000115[0]:
path traversal via symlink

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

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#871710: mercurial:CVE-2017-1000116: command injection on clients through malicious ssh URLs

[Salvatore Bonaccorso]

Source: mercurial
Version: 4.0-1
Severity: grave
Tags: upstream security

Hi,

the following vulnerability was published for mercurial.

CVE-2017-1000116[0]:
command injection on clients through malicious ssh URLs

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

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#853425: gngb: ftbfs with GCC-7

[Markus Koschany]

Control: tags -1 pending patch

On Tue, 31 Jan 2017 09:31:44 + Matthias Klose  wrote:

Package: src:gngb
Version: 20060309-3.1
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7



I am attaching a patch that fixes the issue. I also intend to address 
some of the other bugs currently affecting this package once I have 
returned from DebConf.


Markus
From: Markus Koschany 
Date: Thu, 10 Aug 2017 19:39:05 +
Subject: gcc7

---
 src/cpu.c| 10 +-
 src/memory.c |  2 +-
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/src/cpu.c b/src/cpu.c
index 57bc209..5209548 100644
--- a/src/cpu.c
+++ b/src/cpu.c
@@ -61,7 +61,7 @@ static Uint8 a;
 #define H (gbcpu->hl.b.h)
 #define L (gbcpu->hl.b.l)
 
-__inline__ Uint16 get_word(void)
+extern __inline__ Uint16 get_word(void)
 {
   //Uint16 v=((Uint16)(mem_read(PC)));
   Uint16 v1,v2;
@@ -74,7 +74,7 @@ __inline__ Uint16 get_word(void)
   //return v;
 }
 
-__inline__ Uint8 get_byte(void)
+extern __inline__ Uint8 get_byte(void)
 {
   //Uint8 t=mem_read(PC);
   Uint8 t;
@@ -83,7 +83,7 @@ __inline__ Uint8 get_byte(void)
   return t;
 }
 
-__inline__ void push_r(REG *r)
+extern __inline__ void push_r(REG *r)
 {
   //mem_write(--SP,(r)->b.h);
   //mem_write(--SP,(r)->b.l);
@@ -93,7 +93,7 @@ __inline__ void push_r(REG *r)
   mem_write_fast(SP,(r)->b.l);
 }
 
-__inline__ void pop_r(REG *r)
+extern __inline__ void pop_r(REG *r)
 {
   //(r)->b.l=mem_read(SP);
   mem_read_fast(SP,(r)->b.l);
@@ -176,7 +176,7 @@ __inline__ Uint8 unknown(void){
 
 
 
-__inline__ Uint8 gbcpu_exec_one(void)
+extern __inline__ Uint8 gbcpu_exec_one(void)
 {
 	static Uint8 opcode;
 	if (gbcpu->ei_flag==1) {
diff --git a/src/memory.c b/src/memory.c
index 26e42d9..fd06738 100644
--- a/src/memory.c
+++ b/src/memory.c
@@ -737,7 +737,7 @@ Uint8 mem_read_default(Uint16 adr)
   return 0xFF;
 }
 
-__inline__ void update_gb_pad(void) {
+extern __inline__ void update_gb_pad(void) {
   gb_pad=0;
   if (!conf.play_movie) {
 

Processed: Re: gngb: ftbfs with GCC-7

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending patch
Bug #853425 [src:gngb] gngb: ftbfs with GCC-7
Added tag(s) patch and pending.

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

Processed: retitle 871710 to mercurial: CVE-2017-1000116: command injection on clients through malicious ssh URLs ...

[Debian Bug Tracking System]

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

> # add missing spaces
> retitle 871710 mercurial: CVE-2017-1000116: command injection on clients 
> through malicious ssh URLs
Bug #871710 [src:mercurial] mercurial:CVE-2017-1000116: command injection on 
clients through malicious ssh URLs
Changed Bug title to 'mercurial: CVE-2017-1000116: command injection on clients 
through malicious ssh URLs' from 'mercurial:CVE-2017-1000116: command injection 
on clients through malicious ssh URLs'.
> retitle 871709 mercurial: CVE-2017-1000115: path traversal via symlink
Bug #871709 [src:mercurial] mercurial:CVE-2017-1000115: path traversal via 
symlink
Changed Bug title to 'mercurial: CVE-2017-1000115: path traversal via symlink' 
from 'mercurial:CVE-2017-1000115: path traversal via symlink'.
> thanks
Stopping processing here.

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

Bug#871629: confirmed here also

[Eric Valette]

Used several theme including default one : no chnage. Unusable...

--eric

Bug#871712: xul-ext-status4evar: broken in FF54

[Christoph Anton Mitterer]

Package: xul-ext-status4evar
Version: 2016.10.11.01-1
Severity: grave
Justification: renders package unusable


Hi.

In FF54, the plugin does not really seem to work anymore.
The status bar is shown, but no content in it.

An update seems to be available, solving this:
http://forums.mozillazine.org/viewtopic.php?f=48=2001965


I really wonder why Firefox (itself) is such a user-hostile crap,
that one needs plugins (which they break every once in a while)
to get back the most basic funcitonality (like showing the URL
of some link in the status bar)... gosh... Mozilla=evil

Anyway... would be nice if the addon could be updated, to make FF
a bit usable again :-)


Chris.

Bug#871713: build-dependency libatlas-dev no longer available

[Sébastien Villemot]

Package: src:linbox
Version: 1.4.2-4
Severity: serious

Dear Maintainer,

The package libatlas-dev is no longer built by src:atlas, and linbox
build-depends on it.

libatlas-dev used to ship headers related to ATLAS, while the development
libraries were shipped by libatlas-base-dev. Now everything is shipped by
libatlas-base-dev, and libatlas-dev has been dropped.

Two options are available to you:

- depend on libatlas-base-dev instead of libatlas-dev;

- or completely drop the build-dependency on ATLAS, which is not really needed
  since your package already build-depends on liblapack-dev and seems to work
  with any BLAS/LAPACK implementation (see [1] for more details on BLAS/LAPACK
  in Debian).

Cheers,

[1] https://wiki.debian.org/DebianScience/LinearAlgebraLibraries

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


signature.asc
Description: PGP signature

Bug#871715: build-dependency libatlas-dev no longer available

[Sébastien Villemot]

Package: src:ncl
Version: 6.4.0-3
Severity: serious

Dear Maintainer,

The package libatlas-dev is no longer built by src:atlas, and ncl
build-depends on it.

libatlas-dev used to ship headers related to ATLAS, while the development
libraries were shipped by libatlas-base-dev. Now everything is shipped by
libatlas-base-dev, and libatlas-dev has been dropped.

Two options are available to you:

- depend on libatlas-base-dev instead of libatlas-dev;

- or completely drop the build-dependency on ATLAS (and incidentally on
  OpenBLAS), which may not be really needed since your package already
  build-depends on liblapack-dev and seems to work with any BLAS/LAPACK
  implementation (see [1] for more details on BLAS/LAPACK in Debian).

Cheers,

[1] https://wiki.debian.org/DebianScience/LinearAlgebraLibraries

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


signature.asc
Description: PGP signature

Bug#871716: build-dependency libatlas-dev no longer available

[Sébastien Villemot]

Package: src:shogun
Version: 3.2.0-7.4
Severity: serious

Dear Maintainer,

The package libatlas-dev is no longer built by src:atlas, and shogun
build-depends on it.

libatlas-dev used to ship headers related to ATLAS, while the development
libraries were shipped by libatlas-base-dev. Now everything is shipped by
libatlas-base-dev, and libatlas-dev has been dropped.

Since shogun already build-depends on libatlas-base-dev, you can simply drop
the build-dependency on libatlas-dev.

Cheers,

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


signature.asc
Description: PGP signature

Processed: Re: dh-acc: Incorrect usage of doit (Dh_Lib)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #868473 [dh-acc] dh-acc: Incorrect usage of doit (Dh_Lib)
Severity set to 'serious' from 'important'
> tags -1 patch
Bug #868473 [dh-acc] dh-acc: Incorrect usage of doit (Dh_Lib)
Added tag(s) patch.

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

Bug#871601: ansible-2.3.1.0+dfsg-1 is uninstallable

[Lee Garrett]

Hi Robbie,

this is due to the ansible template module being incompatible with jinja2
v2.9. We are aware of this problem [0], and it has already been reported
upstream [1]. I know this is annoying, but at least it stops people upgrading
from stable to testing/unstable to break their ansible installations. As a
workaround you can downgrade python-jinja2 to the version in stable. There
seems to be a patch available since a couple of hours, but I haven't got
around to test it yet.

Regards,
Lee

[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870599
[1] https://github.com/ansible/ansible/issues/20494

On 09/08/17 15:27, Robbie Harwood wrote:
> Package: ansible
> Version: 2.3.1.0+dfsg-1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> ansible-2.3.1.0+dfsg-1 depends on python-jinja2 < 2.9.  However, this is not
> available in testing/unstable/experimental.  As a result,
> ansible-2.3.1.0+dfsg-1 is uninstallable, and its migration from unstable has
> been blocked.
> 
> Thanks,
> --Robbie
> 
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing-debug
>   APT policy: (600, 'testing-debug'), (600, 'testing'), (400, 
> 'unstable-debug'), (400, 'unstable'), (200, 'experimental-debug'), (200, 
> 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.11.0-1-rt-amd64 (SMP w/4 CPU cores; PREEMPT)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: sysvinit (via /sbin/init)
> 
> Versions of packages ansible depends on:
> ii  python2.7.13-2
> ii  python-crypto 2.6.1-7+b1
> ii  python-httplib2   0.9.2+dfsg-1
> ii  python-jinja2 2.9.6-1
> ii  python-netaddr0.7.18-2
> ii  python-paramiko   2.0.0-1
> ii  python-pkg-resources  36.0.1-1
> ii  python-yaml   3.12-1+b1
> 
> Versions of packages ansible recommends:
> ii  python-kerberos   1.1.5-2+b3
> ii  python-selinux2.6-3+b2
> pn  python-winrm  
> ii  python-xmltodict  0.11.0-1
> 
> Versions of packages ansible suggests:
> pn  cowsay   
> pn  sshpass  
> 
> -- no debconf information
> 

Processed: ht: diff for NMU version 2.1.0+repack1-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 853444 + patch
Bug #853444 [src:ht] ht: ftbfs with GCC-7
Added tag(s) patch.
> tags 853444 + pending
Bug #853444 [src:ht] ht: ftbfs with GCC-7
Added tag(s) pending.

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

Bug#853444: ht: diff for NMU version 2.1.0+repack1-2.1

[Stephen Kitt]

Control: tags 853444 + patch
Control: tags 853444 + pending

Dear maintainer,

I've prepared an NMU for ht (versioned as 2.1.0+repack1-2.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards,

Stephen
diff -Nru ht-2.1.0+repack1/debian/changelog ht-2.1.0+repack1/debian/changelog
--- ht-2.1.0+repack1/debian/changelog	2016-10-17 20:19:33.0 +0200
+++ ht-2.1.0+repack1/debian/changelog	2017-08-10 22:54:18.0 +0200
@@ -1,3 +1,11 @@
+ht (2.1.0+repack1-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Force unambiguous signed abs() call, to build with GCC 7.
+(Closes: #853444)
+
+ -- Stephen Kitt   Thu, 10 Aug 2017 22:54:18 +0200
+
 ht (2.1.0+repack1-2) unstable; urgency=high
 
   * [107d7de] Set the minimal libiberty version to 20161017 in BD.
diff -Nru ht-2.1.0+repack1/debian/patches/50_signed_abs.patch ht-2.1.0+repack1/debian/patches/50_signed_abs.patch
--- ht-2.1.0+repack1/debian/patches/50_signed_abs.patch	1970-01-01 01:00:00.0 +0100
+++ ht-2.1.0+repack1/debian/patches/50_signed_abs.patch	2017-08-10 22:52:22.0 +0200
@@ -0,0 +1,14 @@
+Description: Force unambiguous signed abs()
+Author: Stephen Kitt 
+
+--- a/htapp.cc
 b/htapp.cc
+@@ -3023,7 +3023,7 @@
+ {
+ 	uint a = 2;
+ 	uint b = u/a;
+-	while (abs(a - b) > 1) {
++	while (abs((int) (a - b)) > 1) {
+ 		a = (a+b)/2;
+ 		b = u/a;
+ }
diff -Nru ht-2.1.0+repack1/debian/patches/series ht-2.1.0+repack1/debian/patches/series
--- ht-2.1.0+repack1/debian/patches/series	2016-10-13 23:22:18.0 +0200
+++ ht-2.1.0+repack1/debian/patches/series	2017-08-10 22:51:56.0 +0200
@@ -1,3 +1,4 @@
 20_fix_format_not_a_string.patch
 30_remove_C_TIMEDATE.patch
 40_use_packaged_libibberty.patch
+50_signed_abs.patch

Bug#853537: mariadb-10.1: ftbfs with GCC-7

[Matthias Klose]

On 10.08.2017 15:29, Ondřej Surý wrote:
> Package: src:mariadb-10.1
> Followup-For: Bug #853537
> 
> Hi Matthias,
> 
> the full build.log you sent contains:
> 
> make[4]: Leaving directory '/<>/builddir'
> Error running link command: Segmentation fault
> make[4]: Leaving directory '/<>/builddir'
> storage/tokudb/PerconaFT/portability/CMakeFiles/tokuportability_static_conv.dir/build.make:328:
>  recipe for target 
> 'storage/tokudb/PerconaFT/portability/libtokuportability_static_conv.a' failed
> make[4]: *** 
> [storage/tokudb/PerconaFT/portability/libtokuportability_static_conv.a] Error 
> 1
> make[4]: Leaving directory '/<>/builddir'
> CMakeFiles/Makefile2:6419: recipe for target 
> 'storage/tokudb/PerconaFT/portability/CMakeFiles/tokuportability_static_conv.dir/all'
>  failed
> make[3]: *** 
> [storage/tokudb/PerconaFT/portability/CMakeFiles/tokuportability_static_conv.dir/all]
>  Error 2
> make[3]: *** Waiting for unfinished jobs
> make[4]: Leaving directory '/<>/builddir'
> 
> Notice the:
> Error running link command: Segmentation fault
> 
> It was just buried in the logs because of parallel build.
> 
> I can reproduce this with mariadb-10.1_10.1.26 that I am trying to
> build now and it's failing with the same error.
> 
> I am not sure this is strictly mariadb-10.1's code fault, but I am
> willing to help to debug the issue, hence I am not reassigning it to
> gcc-7 (and/or binutils).

we need a tarball with all the files needed for the link, including system
libraries.  I can help with the latter, but would appreciate it if you can
provide such a tarball.

Matthias

Bug#869550: marked as done (debug-me FTBFS: error: `fromDataMessage' is not a (visible) method of class `WebSocketsData')

[Debian Bug Tracking System]

Your message dated Thu, 10 Aug 2017 17:06:00 -0400
with message-id <20170810210600.cbmce2muxfgiu...@iris.silentflame.com>
and subject line Re: Bug#869550: debug-me FTBFS: error: `fromDataMessage' is 
not a (visible) method of class `WebSocketsData'
has caused the Debian Bug report #869550,
regarding debug-me FTBFS: error: `fromDataMessage' is not a (visible) method of 
class `WebSocketsData'
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.)


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

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

...
[20 of 32] Compiling WebSockets   ( WebSockets.hs, 
dist/build/debug-me/debug-me-tmp/WebSockets.o )

WebSockets.hs:96:9: error:
`fromDataMessage' is not a (visible) method of class `WebSocketsData'

WebSockets.hs:123:11: error:
Not in scope: `connectionCompressionOptions'
Makefile:29: recipe for target 'debug-me' failed
make[2]: *** [debug-me] Error 1
--- End Message ---
--- Begin Message ---
Version: 1.20170810-1

Fixed in latest upstream release -- thanks.

-- 
Sean Whitton


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

Bug#853719: marked as done (zorp: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Thu, 10 Aug 2017 21:13:05 +
with message-id 
and subject line Bug#853719: fixed in zorp 6.0.10-4
has caused the Debian Bug report #853719,
regarding zorp: 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.)


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

[...]
 ^~~~
 is_function
http.cc:1415:56: error: template argument 2 is invalid
   std::unique_ptr> stream_line(
^~
http.cc:1416:42: error: request for member 'get' in 'blob', which is of 
non-class type 'int'
 z_stream_push(z_stream_blob_new(blob.get(), session_id.c_str()), 
z_stream_line_new(nullptr, self->max_line_length, ZRL_EOL_CRLF | 
ZRL_PARTIAL_READ)),
  ^~~
http.cc:1421:3: error: expression list treated as compound expression in 
initializer [-fpermissive]
   );
   ^
http.cc:1425:44: error: request for member 'get' in 'stream_line', which is of 
non-class type 'int'
   bool res = z_stream_line_get(stream_line.get(), , _length, 
nullptr);
^~~
http.cc:1425:8: warning: unused variable 'res' [-Wunused-variable]
   bool res = z_stream_line_get(stream_line.get(), , _length, 
nullptr);
^~~
http.cc: In function 'gboolean http_process_request(HttpProxy*)':
http.cc:1938:133: warning: ISO C++ forbids converting a string constant to 
'gchar* {aka char*}' [-Wwrite-strings]
   gchar *authform_file = 
z_error_loader_format_file(authform_file_path.c_str(), "", Z_EF_ESCAPE_HTML, 
NULL, NULL);

 ^
http.cc: In function 'gboolean http_process_response(HttpProxy*)':
http.cc:2846:119: warning: ISO C++ forbids converting a string constant to 
'gchar* {aka char*}' [-Wwrite-strings]
   self->connection_hdr = http_add_header(>headers[EP_SERVER], 
conn_hdr_str, strlen(conn_hdr_str), "close", 5);

   ^
http.cc: In function 'gboolean http_handle_connect(HttpProxy*)':
http.cc:3214:17: warning: ISO C++ forbids converting a string constant to 
'gchar* {aka char*}' [-Wwrite-strings]
   success = "HTTP/1.0 200 Connection established\r\n\r\n";
 ^
http.cc: At global scope:
http.cc:3649:3: warning: missing initializer for member 
'ZProxyModuleFuncs::module_py_init' [-Wmissing-field-initializers]
   };
   ^
Makefile:566: recipe for target 'http.lo' failed
make[4]: *** [http.lo] Error 1
make[4]: *** Waiting for unfinished jobs
make[4]: Leaving directory '/<>/modules/http'
Makefile:602: recipe for target 'all-recursive' failed
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory '/<>/modules/http'
Makefile:420: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/<>/modules'
Makefile:535: recipe for target 'all-recursive' 

Processed: your mail

[Debian Bug Tracking System]

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

> tag 853517 fixed-upstream
Bug #853517 [src:lierolibre] lierolibre: ftbfs with GCC-7
Added tag(s) fixed-upstream.
> tag 806452 fixed-upstream
Bug #806452 [src:lierolibre] lierolibre: please make the build reproducible
Added tag(s) fixed-upstream.
> Thanks
Stopping processing here.

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

Bug#868473: dh-acc: Incorrect usage of doit (Dh_Lib)

[Niels Thykier]

Gianfranco Costamagna:
> [...]
> 
> 
> I'm attaching the patch I did try to craft some minutes ago, [...]
> 

Thanks. :)

> 
> (I'm still not a perl man, I'm not sure I did it correctly, and moreover I 
> had trobles
> in doing the string concatenation)
> 
> G.
> 

No problem, I am happy to assist. :)

> - doit("abi-compliance-checker -l $package -d1 $base -d2 $abidump 
> -report-path ${path}_report.html");
> - doit("abi-compliance-checker -q -l $package -d1 $base -d2 $abidump 
> -xml -report-path ${path}_report.xml");
> + doit('abi-compliance-checker', '-l', $package, '-d1', $base, '-d2', 
> $abidump, '-report-path', ${path}.'_report.html');
> + doit('abi-compliance-checker', '-q', '-l', $package, '-d1', $base, 
> '-d2', $abidump, '-xml', '-report-path', ${path}.'_report.xml');

Looks correct to my eye.  Personally, I would probably have used:


 doit(..., '-report-path', "${path}_report.html");
 doit(..., '-report-path', "${path}_report.xml");

But AFAICT your version is equally correct and we are just debating code
style at the moment. :)

Thanks,
~Niels

Bug#871629: same here

[Marcello Perathoner]

Same problem here on 2 different systems.


Regards

--
Marcello Perathoner

Bug#871647: upx-ucl: uses convenience copy of LZMA library

[Thorsten Glaser]

Hi Robert,

>> Neither the changelog entry nor README.{Debian,source} contain
>> any justification, however.
>
>The justification is simple and obvious: current upx does not compile
>with the current lzma-dev.

that could be fine, depending on the circumstances, but needs
to be documented.

>Also let me quote the following upstream note from
>stub/src/c/Makevars.lzma file in upx source code:
>
>  # UPX unconditionally uses its own version in src/lzma-sdk because
>  # that version works fine since 2006 and that is the only version
>  # that is actually sufficiently tested!!!

This, however, is something *every* upstream says. Only in very
select few circumstances (rsync’s patched zlib) is this true and
not replaceable, though; others merely wish for “the user having
the same libraries everywhere” and thus bundle, say, vulnerable
versions of libfreetype.

Sure, the LZMA libraries in Debian may offer a slightly different
API, but it can be adapted to work with it. You could even feed
that work upstream!

bye,
//mirabilos
-- 
11:56⎜«liwakura:#!/bin/mksh» also, i wanted to add mksh to my own distro │
i was disappointed that there is no makefile │ but somehow the Build.sh is
the least painful built system i've ever seen │ honours CC, {CPP,C,LD}FLAGS
properly │ looks cleary like done by someone who knows what they are doing

Bug#871687: consul FTBFS: test failures

[Adrian Bunk]

Source: consul
Version: 0.6.4~dfsg-4
Severity: serious

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

...
=== RUN   TestExecCommandRun
2017/08/10 13:14:49 [ERR] http: Request GET /v1/catalog/nodes, error: No 
cluster leader from=127.0.0.1:35066
2017/08/10 13:14:49 [DEBUG] http: Request GET /v1/catalog/nodes (373.684µs) 
from=127.0.0.1:35066
2017/08/10 13:14:49 [ERR] http: Request GET /v1/catalog/nodes, error: No 
cluster leader from=127.0.0.1:35066
2017/08/10 13:14:49 [DEBUG] http: Request GET /v1/catalog/nodes (146.322µs) 
from=127.0.0.1:35066
2017/08/10 13:14:49 [ERR] http: Request GET /v1/catalog/nodes, error: No 
cluster leader from=127.0.0.1:35066
2017/08/10 13:14:49 [DEBUG] http: Request GET /v1/catalog/nodes (82.741µs) 
from=127.0.0.1:35066
2017/08/10 13:14:49 [ERR] http: Request GET /v1/catalog/nodes, error: No 
cluster leader from=127.0.0.1:35066
2017/08/10 13:14:49 [DEBUG] http: Request GET /v1/catalog/nodes (187.282µs) 
from=127.0.0.1:35066
2017/08/10 13:14:49 [DEBUG] http: Request GET /v1/catalog/nodes (168.362µs) 
from=127.0.0.1:35066
2017/08/10 13:14:49 [DEBUG] http: Request GET /v1/agent/self (275.023µs) 
from=127.0.0.1:35068
2017/08/10 13:14:49 [DEBUG] http: Request PUT /v1/session/create (716.428µs) 
from=127.0.0.1:35068
2017/08/10 13:14:49 [DEBUG] http: Request PUT 
/v1/kv/_rexec/be94c9f5-e1ad-653e-1f68-a9d5a4d20fe6/job?acquire=be94c9f5-e1ad-653e-1f68-a9d5a4d20fe6
 (470.125µs) from=127.0.0.1:35068
2017/08/10 13:14:49 [DEBUG] http: Request PUT /v1/event/fire/_rexec (181.202µs) 
from=127.0.0.1:35068
2017/08/10 13:14:49 [DEBUG] http: Request GET 
/v1/kv/_rexec/be94c9f5-e1ad-653e-1f68-a9d5a4d20fe6/?keys==400ms 
(116.641µs) from=127.0.0.1:35068
2017/08/10 13:14:49 [DEBUG] http: Request GET 
/v1/kv/_rexec/be94c9f5-e1ad-653e-1f68-a9d5a4d20fe6/?index=6==400ms 
(804.91µs) from=127.0.0.1:35068
2017/08/10 13:14:49 [DEBUG] http: Request GET 
/v1/kv/_rexec/be94c9f5-e1ad-653e-1f68-a9d5a4d20fe6/Node%202/out/0 
(160.062µs) from=127.0.0.1:35068
2017/08/10 13:14:49 [DEBUG] http: Request GET 
/v1/kv/_rexec/be94c9f5-e1ad-653e-1f68-a9d5a4d20fe6/?index=7==400ms 
(112.022µs) from=127.0.0.1:35068
2017/08/10 13:14:49 [DEBUG] http: Request GET 
/v1/kv/_rexec/be94c9f5-e1ad-653e-1f68-a9d5a4d20fe6/Node%202/exit (99.441µs) 
from=127.0.0.1:35068
2017/08/10 13:14:50 [DEBUG] http: Request PUT 
/v1/session/destroy/be94c9f5-e1ad-653e-1f68-a9d5a4d20fe6 (857.53µs) 
from=127.0.0.1:35070
2017/08/10 13:14:50 [DEBUG] http: Request GET 
/v1/kv/_rexec/be94c9f5-e1ad-653e-1f68-a9d5a4d20fe6/?index=8==400ms 
(401.938171ms) from=127.0.0.1:35068
2017/08/10 13:14:50 [DEBUG] http: Request DELETE 
/v1/kv/_rexec/be94c9f5-e1ad-653e-1f68-a9d5a4d20fe6?recurse= (274.263µs) 
from=127.0.0.1:35068
2017/08/10 13:14:50 [DEBUG] http: Request PUT 
/v1/session/destroy/be94c9f5-e1ad-653e-1f68-a9d5a4d20fe6 (291.744µs) 
from=127.0.0.1:35068
2017/08/10 13:14:50 [DEBUG] http: Shutting down http server (127.0.0.1:10421)
--- FAIL: TestExecCommandRun (0.68s)
exec_test.go:30: bad: 2. Error:""  (std)Output:"Node 2: /bin/sh: 1: 
uptime: not found\nNode 2:\n==> Node 2: finished with exit code 127\n1 / 1 
node(s) completed / acknowledged\n"
=== RUN   TestExecCommandRun_CrossDC
2017/08/10 13:14:50 [ERR] http: Request GET /v1/catalog/nodes, error: No 
cluster leader from=127.0.0.1:59950
2017/08/10 13:14:50 [DEBUG] http: Request GET /v1/catalog/nodes (146.742µs) 
from=127.0.0.1:59950
2017/08/10 13:14:50 [ERR] http: Request GET /v1/catalog/nodes, error: No 
cluster leader from=127.0.0.1:59950
2017/08/10 13:14:50 [DEBUG] http: Request GET /v1/catalog/nodes (71.441µs) 
from=127.0.0.1:59950
2017/08/10 13:14:50 [ERR] http: Request GET /v1/catalog/nodes, error: No 
cluster leader from=127.0.0.1:59950
2017/08/10 13:14:50 [DEBUG] http: Request GET /v1/catalog/nodes (153.222µs) 
from=127.0.0.1:59950
2017/08/10 13:14:50 [DEBUG] http: Request GET /v1/catalog/nodes (73.321µs) 
from=127.0.0.1:59950
2017/08/10 13:14:50 [DEBUG] http: Request GET /v1/catalog/nodes (111.401µs) 
from=127.0.0.1:43308
2017/08/10 13:14:50 [DEBUG] http: Request GET /v1/agent/self?dc=dc2 (246.403µs) 
from=127.0.0.1:59954
2017/08/10 13:14:50 [DEBUG] http: Request GET 
/v1/health/service/consul?dc=dc2=1 (1.517517ms) from=127.0.0.1:59954
2017/08/10 13:14:50 [DEBUG] http: Request PUT /v1/session/create?dc=dc2 
(986.571µs) from=127.0.0.1:59954
2017/08/10 13:14:50 [DEBUG] http: Request PUT 
/v1/kv/_rexec/5de22c9e-b6a8-d3a7-8b6a-d881e45c3a11/job?acquire=5de22c9e-b6a8-d3a7-8b6a-d881e45c3a11=dc2
 (795.888µs) from=127.0.0.1:59954
2017/08/10 13:14:50 [DEBUG] http: Request PUT /v1/event/fire/_rexec?dc=dc2 
(780.888µs) from=127.0.0.1:59954
2017/08/10 13:14:50 [DEBUG] http: Request GET 
/v1/kv/_rexec/5de22c9e-b6a8-d3a7-8b6a-d881e45c3a11/?dc=dc2==400ms 
(775.089µs) from=127.0.0.1:59954
2017/08/10 13:14:50 [DEBUG] http: Request GET 
/v1/kv/_rexec/5de22c9e-b6a8-d3a7-8b6a-d881e45c3a11/?dc=dc2=6==400ms
 (1.251414ms) from=127.0.0.1:59954
2017/08/10 13:14:50 [DEBUG] http: Request GET 

Bug#853408: funguloids: ftbfs with GCC-7

[Markus Koschany]

On Tue, 31 Jan 2017 09:31:26 + Matthias Klose  wrote:

Package: src:funguloids
Version: 1.06-12
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7


This FTBFS appears to be related to #871296. Looks like funguloids has 
to be rebuilt once ogre has been rebuilt too.


Markus

Bug#868614: [Debian-med-packaging] Bug#868614: cwltool FTBFS with python-typing 3.6.1-1

[Sascha Steinbiss]

Hi Michael,

[...]
> Installed /build/1st/cwltool-1.0.20170114120503
> Processing dependencies for cwltool==1.0.20170114120503
> Searching for typing<3.6,>=3.5.2
> Reading https://pypi.python.org/simple/typing/
> Download error on https://pypi.python.org/simple/typing/: [Errno -3] 
> Temporary failure in name resolution -- Some packages may not be found!
> Couldn't retrieve index page for 'typing'
> Scanning index of all packages (this may take a while)
> Reading https://pypi.python.org/simple/
> Download error on https://pypi.python.org/simple/: [Errno -3] Temporary 
> failure in name resolution -- Some packages may not be found!
> No local packages or working download links found for typing<3.6,>=3.5.2
> error: Could not find suitable distribution for 
> Requirement.parse('typing<3.6,>=3.5.2')

This is because Debian's python-typing is now 3.6.1, so that requirement
can't be satisfied. I am wondering why this limitation to versions < 3.6
is required, maybe you could shed some light on this. It builds fine
with 3.6.1 but since there don't seem to be tests it's difficult to
check whether that indeed works at runtime or not...

I also added a missing build-dependency on python-avro, which stopped
the build before. The FTBFS should be fixed now.

I have pushed my changes to git and would be happy to get some comments.

Many thanks
Sascha

Bug#871656: apt-offline: Does not validate Packages or .deb files in bundle

[Stuart Prescott]

Package: apt-offline
Version: 1.7.2
Severity: serious
Tags: security

Dear Maintainer,

apt-offline claims to do gpg validation of the contents of the zip file and
claims that this is an important thing for it to do.

--allow-unauthenticated
 Don't  verify  GPG signatures for the data to be installed to APT.
 Usage of this option is highly discouraged.

However, it appears that apt-offline only verifies the GPG signature on the
Release file. If that check passes, then it is assumed that all referenced
resources (Packages files) are OK and apt-offline does not check that the
hashes for the Packages files are indeed correct. These Packages files are
then fed directly to apt. Once apt has been fed a manipulated Packages file,
it will then trust the .deb packages that it refers to.

One can take a zip bundle, decompress it, alter the Packages file and the 
altered
file was no rejected by "apt-offline install bundle.zip".

It seems that the existing GPG check of the Release file is rather pointless
and gives a false sense of security validation. Either the bundle.zip has been
securely handled all along and the GPG check is unnecessary, or bundle.zip has
not been securely handled and it is incorrectly trusted.

regards
Stuart


-- System Information:
Debian Release: 9.1
  APT prefers proposed-updates
  APT policy: (550, 'proposed-updates'), (500, 'stable-debug'), (500, 
'stable'), (60, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages apt-offline depends on:
ii  apt1.4.7
ii  less   481-2.1
ii  libpython2.7-stdlib [python-argparse]  2.7.13-2
ii  python 2.7.13-2
ii  python-magic   1:5.30-1

Versions of packages apt-offline recommends:
ii  debian-archive-keyring  2017.5
ii  python-lzma 0.5.3-3
ii  python-soappy   0.12.22-1

apt-offline suggests no packages.

-- no debconf information

Processed: Pending fixes for bugs in the libgettext-commons-java package

[Debian Bug Tracking System]

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

> tag 871370 + pending
Bug #871370 [src:libgettext-commons-java] libgettext-commons-java: FTBFS: 
[ERROR] Could not find goal 'attached' in plugin 
org.apache.maven.plugins:maven-assembly-plugin:3.0.0 among available goals 
single -> [Help 1]
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#870725: CVE-2017-11721: read buffer overflow in MSG_ReadBits

[Simon McVittie]

On Sat, 05 Aug 2017 at 12:24:19 +0100, Simon McVittie wrote:
> Again, I don't have time to handle this for stable right now, so
> security or games team members are very welcome to do so. I'll prepare
> a stable update during Debconf if nobody gets there first, assuming I
> can find a stable user willing to test a game from contrib.

I have prepared proposed stable-security updates and borrowed a
stable machine to smoke-test them (thanks to Andy Simpkins). I forget
whether you're interested in fixing contrib or not, so I'm doing iortcw
as well as ioquake3 (openjk is experimental-only so is not relevant here).
Let me know if I should redirect the iortcw update to the release team.

Here is some text which might be useful for a DSA:

8<

A read buffer overflow was discovered in the idtech3 (Quake III Arena)
family of game engines. This allows remote attackers to cause a denial
of service (application crash) or possibly have unspecified other impact
via a crafted packet. (CVE-2017-11721)

In Debian, this issue affects the ioquake3, iortcw and openjk packages.

For the stable distribution (stretch), this issue has been fixed in
ioquake3 version 1.36+u20161101+dfsg1-2+deb9u1 and in iortcw version
1.50a+dfsg1-3+deb9u1.

In the unstable distribution (sid), this issue has been fixed in ioquake3
version 1.36+u20170803+dfsg1-1 and in iortcw version 1.51+dfsg1-3.

In the experimental distribution this issue has been fixed in openjk
version 0~20170718+dfsg1-2.

>8

Proposed debdiffs attached. OK to upload?

Regards,
S
diffstat for iortcw-1.50a+dfsg1 iortcw-1.50a+dfsg1

 changelog|8 
 patches/debian/Remove-support-for-downloading-executable-updates.patch   |2 
 patches/security/All-Fix-improve-buffer-overflow-in-MSG_ReadBits-MSG_Write.patch |  626 ++
 patches/series   |1 
 4 files changed, 636 insertions(+), 1 deletion(-)

diff -Nru iortcw-1.50a+dfsg1/debian/changelog iortcw-1.50a+dfsg1/debian/changelog
--- iortcw-1.50a+dfsg1/debian/changelog	2017-03-14 05:37:19.0 -0400
+++ iortcw-1.50a+dfsg1/debian/changelog	2017-08-08 14:57:52.0 -0400
@@ -1,3 +1,11 @@
+iortcw (1.50a+dfsg1-3+deb9u1) stretch-security; urgency=medium
+
+  * d/p/security/All-Fix-improve-buffer-overflow-in-MSG_ReadBits-MSG_Write.patch:
+Add patch (from ioquake3 via upstream) to fix a read buffer overflow
+in MSG_ReadBits (CVE-2017-11721)
+
+ -- Simon McVittie   Tue, 08 Aug 2017 14:57:52 -0400
+
 iortcw (1.50a+dfsg1-3) unstable; urgency=high
 
   * d/gbp.conf: switch branch to debian/stretch for updates during freeze
diff -Nru iortcw-1.50a+dfsg1/debian/patches/debian/Remove-support-for-downloading-executable-updates.patch iortcw-1.50a+dfsg1/debian/patches/debian/Remove-support-for-downloading-executable-updates.patch
--- iortcw-1.50a+dfsg1/debian/patches/debian/Remove-support-for-downloading-executable-updates.patch	2017-03-14 05:37:19.0 -0400
+++ iortcw-1.50a+dfsg1/debian/patches/debian/Remove-support-for-downloading-executable-updates.patch	2017-08-08 14:57:52.0 -0400
@@ -219,7 +219,7 @@
  // DHM - Nerve
  
 diff --git a/MP/code/qcommon/qcommon.h b/MP/code/qcommon/qcommon.h
-index 1f23d0f..b1fff59 100644
+index 02ef8e8..96a9081 100644
 --- a/MP/code/qcommon/qcommon.h
 +++ b/MP/code/qcommon/qcommon.h
 @@ -1258,12 +1258,6 @@ void Sys_StartProcess( char *cmdline, qboolean doexit );// NERVE - S
diff -Nru iortcw-1.50a+dfsg1/debian/patches/security/All-Fix-improve-buffer-overflow-in-MSG_ReadBits-MSG_Write.patch iortcw-1.50a+dfsg1/debian/patches/security/All-Fix-improve-buffer-overflow-in-MSG_ReadBits-MSG_Write.patch
--- iortcw-1.50a+dfsg1/debian/patches/security/All-Fix-improve-buffer-overflow-in-MSG_ReadBits-MSG_Write.patch	1969-12-31 19:00:00.0 -0500
+++ iortcw-1.50a+dfsg1/debian/patches/security/All-Fix-improve-buffer-overflow-in-MSG_ReadBits-MSG_Write.patch	2017-08-08 14:57:52.0 -0400
@@ -0,0 +1,626 @@
+From: MAN-AT-ARMS 
+Date: Thu, 3 Aug 2017 00:06:37 -0400
+Subject: All: Fix/improve buffer overflow in MSG_ReadBits/MSG_WriteBits
+
+Origin: upstream, commit:260c39a29af517a08b3ee1a0e78ad654bdd70934
+Bug-CVE: CVE-2017-11721
+Bug-Debian: https://bugs.debian.org/870811
+---
+ MP/code/qcommon/huffman.c | 49 ---
+ MP/code/qcommon/msg.c | 45 +---
+ MP/code/qcommon/qcommon.h |  6 ++---
+ SP/code/qcommon/huffman.c | 49 ---
+ SP/code/qcommon/msg.c | 65 ++-
+ SP/code/qcommon/qcommon.h |  6 ++---
+ 6 files changed, 145 insertions(+), 75 deletions(-)
+
+diff --git a/MP/code/qcommon/huffman.c b/MP/code/qcommon/huffman.c
+index 00b007e..88b972c 100644
+--- a/MP/code/qcommon/huffman.c
 b/MP/code/qcommon/huffman.c
+@@ -36,7 +36,7 @@ If you 

Processed: tagging 868945

[Debian Bug Tracking System]

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

> tags 868945 - pending
Bug #868945 [src:libtest-redisserver-perl] libtest-redisserver-perl: FTBFS: 
/bin/sh: 1: /usr/bin/licensecheck: not found
Removed tag(s) pending.
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> tags 853423 patch
Bug #853423 [src:gmchess] gmchess: ftbfs with GCC-7
Added tag(s) patch.
>
End of message, stopping processing here.

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

Processed: Re: Bug#870267: graphicsmagick frequently FTBFS on ppc64el: test hang

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #870267 [src:graphicsmagick] graphicsmagick frequently FTBFS on ppc64el: 
test hang
Severity set to 'important' from 'serious'

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

Bug#868113: marked as done (Astropy 2.0 breaks many packages)

[Debian Bug Tracking System]

Your message dated Thu, 10 Aug 2017 13:39:04 +0200
with message-id <782eb2a7-a4d7-8cce-9d65-563111bbe...@debian.org>
and subject line Closing bug
has caused the Debian Bug report #868113,
regarding Astropy 2.0 breaks many packages
to be marked as done.

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

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


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

After upgrade to 2.0, many packages that depend on astropy are broken
due to incompatibilities. This bug is to ensure they get fixed before
astropy migrates to Testing.
--- End Message ---
--- Begin Message ---
Since all dependencies in testing are now working with astropy-2.0, I am
closing this bug which prevented astropy from migration.--- End Message ---

Bug#871483: marked as done (mpich FTBFS on ppc64el: FAIL test_primitives)

[Debian Bug Tracking System]

Your message dated Thu, 10 Aug 2017 11:49:22 +
with message-id 
and subject line Bug#871483: fixed in mpich 3.3~a2-2
has caused the Debian Bug report #871483,
regarding mpich FTBFS on ppc64el: FAIL test_primitives
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=mpich=ppc64el=3.2-7%2Bb2=1502178769=0

...
FAIL: test_primitives
=

Testing simple integer load/store functionalityPASSED
Testing simple pointer load/store functionalityPASSED
Testing simple add/incr/decr functionality PASSED
Testing simple decr and test functionality PASSED
Testing simple fetch and add/incr/decr functionality   PASSED
Testing simple integer compare-and-swap functionality  PASSED
Testing simple pointer compare-and-swap functionality  PASSED
Testing simple integer swap functionality  PASSED
Testing simple pointer swap functionality  PASSED
Testing simple integer load-linked/store-conditional functionality PASSED
Testing simple pointer load-linked/store-conditional functionality PASSED
Testing integer LL/SC ABA with 2 threads   PASSED
False positives: 160 / 1000953
Testing pointer LL/SC ABA with 2 threads  
Unexpected success of OPA_SC_ptr
Unexpected success of OPA_SC_ptr
*FAILED*
at test_primitives.c:4178 in test_threaded_llsc_ptr_aba()...
False positives: 286 / 1000436
Testing integer load/store with 1 thread   PASSED
Testing pointer load/store with 1 thread   PASSED
Testing add with 1 thread  PASSED
Testing incr and decr with 1 threadPASSED
Testing decr and test with 1 threadPASSED
Testing fetch and add with 1 threadPASSED
Testing fetch and add return values with 1 thread  PASSED
Testing fetch and incr/decr with 1 thread  PASSED
Testing fetch and incr return values with 1 thread PASSED
Testing fetch and decr return values with 1 thread PASSED
Testing integer compare-and-swap with 1 thread PASSED
Testing pointer compare-and-swap with 1 thread PASSED
Testing grouped integer compare-and-swap with 1 thread PASSED
Testing grouped pointer compare-and-swap with 1 thread PASSED
Testing integer compare-and-swap fairness with 1 threadPASSED
Testing pointer compare-and-swap fairness with 1 threadPASSED
Testing integer swap with 1 thread PASSED
Testing pointer swap with 1 thread PASSED
Testing integer load/store with 2 threads  PASSED
Testing pointer load/store with 2 threads  PASSED
Testing add with 2 threads PASSED
Testing incr and decr with 1 threadPASSED
Testing decr and test with 2 threads   PASSED
Testing fetch and add with 2 threads   PASSED
Testing fetch and add return values with 2 threads PASSED
Testing fetch and incr/decr with 1 thread  PASSED
Testing fetch and incr return values with 2 threadsPASSED
Testing fetch and decr return values with 2 threadsPASSED
Testing integer compare-and-swap with 2 threadsPASSED
Testing pointer compare-and-swap with 2 threadsPASSED
Testing grouped integer compare-and-swap with 2 threadsPASSED
Testing grouped pointer compare-and-swap with 2 threadsPASSED
Testing integer compare-and-swap fairness with 2 threads   PASSED
Testing pointer compare-and-swap fairness with 2 threads   PASSED
Testing integer swap with 2 threads

Bug#853324: marked as done (libmpich-dev: drop the gcc version check in mpicxx.h)

[Debian Bug Tracking System]

Your message dated Thu, 10 Aug 2017 11:49:22 +
with message-id 
and subject line Bug#853404: fixed in mpich 3.3~a2-2
has caused the Debian Bug report #853404,
regarding libmpich-dev: drop the gcc version check in mpicxx.h
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.)


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

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]
config.status: creating src/multi/casscf/Makefile
config.status: creating src/multi/zcasscf/Makefile
config.status: creating src/mat1e/Makefile
config.status: creating src/periodic/Makefile
config.status: creating src/opt/Makefile
config.status: creating src/alglib/Makefile
config.status: creating src/basis/Makefile
config.status: creating bagel_config.h
config.status: executing depfiles commands
config.status: executing libtool commands
configure: WARNING: unrecognized options: --disable-maintainer-mode
make[1]: Leaving directory '/<>'
   dh_auto_build
make -j1
make[1]: Entering directory '/<>'
make  all-recursive
make[2]: Entering directory '/<>'
Making all in src
make[3]: Entering directory '/<>/src'
Making all in util
make[4]: Entering directory '/<>/src/util'
Making all in parallel
make[5]: Entering directory '/<>/src/util/parallel'
/bin/bash ../../../libtool  --tag=CXX   --mode=compile mpicxx -DHAVE_CONFIG_H 
-I. -I../../..   -Wdate-time -D_FORTIFY_SOURCE=2 -I../../.. -g -O2 -DNDEBUG 
-DZDOT_RETURN -c -o process.lo process.cc
libtool: compile:  mpicxx -DHAVE_CONFIG_H -I. -I../../.. -Wdate-time 
-D_FORTIFY_SOURCE=2 -I../../.. -g -O2 -DNDEBUG -DZDOT_RETURN -c process.cc -o 
process.o
In file included from /usr/include/mpich/mpi.h:2231:0,
 from ../../../src/util/parallel/mpi_interface.h:36,
 from process.cc:27:
/usr/include/mpich/mpicxx.h:21:4: error: #error 'Please use the same version of 
GCC and g++ for compiling MPICH and user MPI programs'
 #  error 'Please use the same version of GCC and g++ for compiling MPICH and 
user MPI programs'
^
Makefile:444: recipe for target 'process.lo' failed
make[5]: *** [process.lo] Error 1
make[5]: Leaving directory '/<>/src/util/parallel'
Makefile:500: recipe for target 'all-recursive' failed
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory '/<>/src/util'
Makefile:584: recipe for target 'all-recursive' failed
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory '/<>/src'
Makefile:416: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/<>'
Makefile:348: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
debian/rules:9: 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: mpich
Source-Version: 3.3~a2-2

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

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

Thank you for reporting the bug, which will now be closed.  If you
have further comments please 

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

[Adrian Bunk]

On Thu, Aug 10, 2017 at 09:31:32AM +0200, Rafael Laboissière wrote:
> 
> I would guess that the culprit is the following unit test in bwdist:
> 
> ## The quasi-euclidean method is apparently sensitive to a machine precision
> ## error that happens in x86 systems only. This test will cause an endless
> ## loop in case of a regression.
>...

That explains why the problem happens on i386 (where the 387 FPU
that internally uses 80-bit precision is used) but not on amd64
(where gcc defaults to using SSE instead of the 387).

If the problem is only in the test case,
it should be disabled on any-i386.

But if the difference is actually considered a bug,
then the following in debian/rules fixes the problem:

DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)

ifneq (,$(filter $(DEB_HOST_ARCH), i386))
export DEB_CXXFLAGS_MAINT_APPEND=-ffloat-store
endif


> Rafael

cu
Adrian

-- 

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

Bug#853532: marked as done (libmpich-dev: drop the gcc version check in mpicxx.h)

[Debian Bug Tracking System]

Your message dated Thu, 10 Aug 2017 11:49:22 +
with message-id 
and subject line Bug#853404: fixed in mpich 3.3~a2-2
has caused the Debian Bug report #853404,
regarding libmpich-dev: drop the gcc version check in mpicxx.h
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.)


-- 
853404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853404
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:madness
Version: 0.10.1~gite4aa500e-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/madness_0.10.1~gite4aa500e-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

[...]
cd "/<>/obj-x86_64-linux-gnu" && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" "/<>" "/<>/src/madness/mra" 
"/<>/obj-x86_64-linux-gnu" 
"/<>/obj-x86_64-linux-gnu/src/madness/mra" 
"/<>/obj-x86_64-linux-gnu/src/madness/mra/CMakeFiles/MADmra-obj.dir/DependInfo.cmake"
 --color=
Scanning dependencies of target MADmra-obj
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make -f src/madness/mra/CMakeFiles/MADmra-obj.dir/build.make 
src/madness/mra/CMakeFiles/MADmra-obj.dir/build
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
[  0%] Building CXX object src/madness/mra/CMakeFiles/MADmra-obj.dir/mra1.cc.o
cd "/<>/obj-x86_64-linux-gnu/src/madness/mra" && /usr/bin/c++   
-DMPICH_SKIP_MPICXX=1 -DMRA_DATA_DIR="\"/<>/src/madness/mra\"" 
-DOMPI_SKIP_MPICXX=1 -I"/<>/obj-x86_64-linux-gnu/src/madness/mra" 
-I"/<>/src/madness/mra" -I"/<>/src" 
-I"/<>/obj-x86_64-linux-gnu/src" 
-I"/<>/obj-x86_64-linux-gnu/src/madness/tensor" 
-I"/<>/src/madness/tensor" 
-I"/<>/obj-x86_64-linux-gnu/src/madness/misc" 
-I"/<>/src/madness/misc" -I/usr/include/mpich 
-I"/<>/src/apps" 
-I"/<>/obj-x86_64-linux-gnu/src/madness/world" 
-I"/<>/src/madness/world" 
-I"/<>/obj-x86_64-linux-gnu/src/madness/external/tinyxml" 
-I"/<>/src/madness/external/tinyxml" 
-I"/<>/obj-x86_64-linux-gnu/src/madness/external/muParser" 
-I"/<>/src/madness/external/muParser"  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-st
 rong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -o 
CMakeFiles/MADmra-obj.dir/mra1.cc.o -c 
"/<>/src/madness/mra/mra1.cc"
In file included from /usr/include/tbb/tbb.h:65:0,
 from /<>/src/madness/world/thread.h:74,
 from /<>/src/madness/world/worldrmi.h:36,
 from /<>/src/madness/world/worldprofile.h:37,
 from /<>/src/madness/world/world.h:70,
 from /<>/src/madness/world/MADworld.h:42,
 from /<>/src/madness/mra/mra.h:44,
 from /<>/src/madness/mra/mra1.cc:32:
/usr/include/tbb/pipeline.h:328:74: error: 'has_trivial_copy_constructor' is 
not a member of 'std'
 template struct tbb_trivially_copyable { enum { value = 
std::has_trivial_copy_constructor::value }; };
  
^~~~
/usr/include/tbb/pipeline.h:328:74: note: suggested alternative: 
'is_trivially_copy_constructible'
 template struct tbb_trivially_copyable { enum { value = 
std::has_trivial_copy_constructor::value }; };
  
^~~~
  
is_trivially_copy_constructible
/usr/include/tbb/pipeline.h:328:104: error: expected primary-expression before 
'>' token
 template 

Bug#853404: marked as done (libmpich-dev: drop the gcc version check in mpicxx.h)

[Debian Bug Tracking System]

Your message dated Thu, 10 Aug 2017 11:49:22 +
with message-id 
and subject line Bug#853562: fixed in mpich 3.3~a2-2
has caused the Debian Bug report #853562,
regarding libmpich-dev: drop the gcc version check in mpicxx.h
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.)


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

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]

/* confdefs.h */
#define PACKAGE_NAME "FORM"
#define PACKAGE_TARNAME "form"
#define PACKAGE_VERSION "4.1"
#define PACKAGE_STRING "FORM 4.1"
#define PACKAGE_BUGREPORT "f...@nikhef.nl"
#define PACKAGE_URL ""
#define PACKAGE "form"
#define VERSION "4.1"
#define MAJORVERSION 4
#define MINORVERSION 1
#define HAVE_PRODUCTIONDATE_H /**/
#define STDC_HEADERS 1
#define TIME_WITH_SYS_TIME 1
#define HAVE_SYS_TYPES_H 1
#define HAVE_SYS_STAT_H 1
#define HAVE_STDLIB_H 1
#define HAVE_STRING_H 1
#define HAVE_MEMORY_H 1
#define HAVE_STRINGS_H 1
#define HAVE_INTTYPES_H 1
#define HAVE_STDINT_H 1
#define HAVE_UNISTD_H 1
#define HAVE_FCNTL_H 1
#define HAVE_LIMITS_H 1
#define HAVE_SYS_FILE_H 1
#define LINUX /**/
#define HAVE_UNISTD_H 1
#define UNIX /**/
#define SIZEOF_CHAR 1
#define SIZEOF_SHORT 2
#define SIZEOF_INT 4
#define SIZEOF_LONG 8
#define SIZEOF_LONG_LONG 8
#define SIZEOF_VOID_P 8
#define SIZEOF_OFF_T 8
#define LP64 /**/
#ifdef WITHPTHREADS
#define WITHPOSIXCLOCK /**/
#endif

configure: exit 1
dh_auto_configure: ./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=${prefix}/include --mandir=${prefix}/share/man 
--infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=${prefix}/lib/x86_64-linux-gnu 
--libexecdir=${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
--disable-dependency-tracking --enable-parform returned exit code 1
debian/rules:13: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 2
make[1]: Leaving directory '/<>'
debian/rules:10: 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: mpich
Source-Version: 3.3~a2-2

We believe that the bug you reported is fixed in the latest version of
mpich, 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.
Alastair McKinstry  (supplier of updated mpich 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, 10 Aug 2017 09:29:30 +0100
Source: mpich
Binary: libmpich-dev libmpich12 mpich mpich-doc
Architecture: source amd64 all
Version: 3.3~a2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Bug#853532: marked as done (libmpich-dev: drop the gcc version check in mpicxx.h)

[Debian Bug Tracking System]

Your message dated Thu, 10 Aug 2017 11:49:22 +
with message-id 
and subject line Bug#853562: fixed in mpich 3.3~a2-2
has caused the Debian Bug report #853562,
regarding libmpich-dev: drop the gcc version check in mpicxx.h
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.)


-- 
853562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853562
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:madness
Version: 0.10.1~gite4aa500e-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/madness_0.10.1~gite4aa500e-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

[...]
cd "/<>/obj-x86_64-linux-gnu" && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" "/<>" "/<>/src/madness/mra" 
"/<>/obj-x86_64-linux-gnu" 
"/<>/obj-x86_64-linux-gnu/src/madness/mra" 
"/<>/obj-x86_64-linux-gnu/src/madness/mra/CMakeFiles/MADmra-obj.dir/DependInfo.cmake"
 --color=
Scanning dependencies of target MADmra-obj
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make -f src/madness/mra/CMakeFiles/MADmra-obj.dir/build.make 
src/madness/mra/CMakeFiles/MADmra-obj.dir/build
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
[  0%] Building CXX object src/madness/mra/CMakeFiles/MADmra-obj.dir/mra1.cc.o
cd "/<>/obj-x86_64-linux-gnu/src/madness/mra" && /usr/bin/c++   
-DMPICH_SKIP_MPICXX=1 -DMRA_DATA_DIR="\"/<>/src/madness/mra\"" 
-DOMPI_SKIP_MPICXX=1 -I"/<>/obj-x86_64-linux-gnu/src/madness/mra" 
-I"/<>/src/madness/mra" -I"/<>/src" 
-I"/<>/obj-x86_64-linux-gnu/src" 
-I"/<>/obj-x86_64-linux-gnu/src/madness/tensor" 
-I"/<>/src/madness/tensor" 
-I"/<>/obj-x86_64-linux-gnu/src/madness/misc" 
-I"/<>/src/madness/misc" -I/usr/include/mpich 
-I"/<>/src/apps" 
-I"/<>/obj-x86_64-linux-gnu/src/madness/world" 
-I"/<>/src/madness/world" 
-I"/<>/obj-x86_64-linux-gnu/src/madness/external/tinyxml" 
-I"/<>/src/madness/external/tinyxml" 
-I"/<>/obj-x86_64-linux-gnu/src/madness/external/muParser" 
-I"/<>/src/madness/external/muParser"  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-st
 rong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -o 
CMakeFiles/MADmra-obj.dir/mra1.cc.o -c 
"/<>/src/madness/mra/mra1.cc"
In file included from /usr/include/tbb/tbb.h:65:0,
 from /<>/src/madness/world/thread.h:74,
 from /<>/src/madness/world/worldrmi.h:36,
 from /<>/src/madness/world/worldprofile.h:37,
 from /<>/src/madness/world/world.h:70,
 from /<>/src/madness/world/MADworld.h:42,
 from /<>/src/madness/mra/mra.h:44,
 from /<>/src/madness/mra/mra1.cc:32:
/usr/include/tbb/pipeline.h:328:74: error: 'has_trivial_copy_constructor' is 
not a member of 'std'
 template struct tbb_trivially_copyable { enum { value = 
std::has_trivial_copy_constructor::value }; };
  
^~~~
/usr/include/tbb/pipeline.h:328:74: note: suggested alternative: 
'is_trivially_copy_constructible'
 template struct tbb_trivially_copyable { enum { value = 
std::has_trivial_copy_constructor::value }; };
  
^~~~
  
is_trivially_copy_constructible
/usr/include/tbb/pipeline.h:328:104: error: expected primary-expression before 
'>' token
 template 

Bug#853562: marked as done (libmpich-dev: drop the gcc version check in mpicxx.h)

[Debian Bug Tracking System]

Your message dated Thu, 10 Aug 2017 11:49:22 +
with message-id 
and subject line Bug#853404: fixed in mpich 3.3~a2-2
has caused the Debian Bug report #853404,
regarding libmpich-dev: drop the gcc version check in mpicxx.h
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.)


-- 
853404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853404
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mpqc3
Version: 0.0~git20170114-4
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]
 from /usr/include/madness/world/worldprofile.h:37,
 from /usr/include/madness/world/world.h:70,
 from /usr/include/madness/world/MADworld.h:42,
 from /usr/include/TiledArray/madness.h:31,
 from /usr/include/tiledarray.h:25,
 from 
/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx:2:
/usr/include/tbb/pipeline.h:328:74: error: 'has_trivial_copy_constructor' is 
not a member of 'std'
 template struct tbb_trivially_copyable { enum { value = 
std::has_trivial_copy_constructor::value }; };
  
^~~~
/usr/include/tbb/pipeline.h:328:74: note: suggested alternative: 
'is_trivially_copy_constructible'
 template struct tbb_trivially_copyable { enum { value = 
std::has_trivial_copy_constructor::value }; };
  
^~~~
  
is_trivially_copy_constructible
/usr/include/tbb/pipeline.h:328:104: error: expected primary-expression before 
'>' token
 template struct tbb_trivially_copyable { enum { value = 
std::has_trivial_copy_constructor::value }; };

^
/usr/include/tbb/pipeline.h:328:107: error: '::value' has not been declared
 template struct tbb_trivially_copyable { enum { value = 
std::has_trivial_copy_constructor::value }; };

   ^
CMakeFiles/cmTC_79efd.dir/build.make:65: recipe for target 
'CMakeFiles/cmTC_79efd.dir/src.cxx.o' failed
make[3]: *** [CMakeFiles/cmTC_79efd.dir/src.cxx.o] Error 1
make[3]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
Makefile:126: recipe for target 'cmTC_79efd/fast' failed
make[2]: *** [cmTC_79efd/fast] Error 2
make[2]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'

Source file was:

#include 
int main(int argc, char** argv) {
  madness::World& world = madness::initialize(argc, argv);
  std::vector tile_ranges;
  size_t tile_bounds[] = {0, 3, 7}; // 2 tiles; N.B. double square brackets 
due to autoconf madness
  const size_t ntiles = sizeof(tile_bounds)/sizeof(size_t) - 1;
  tile_ranges.push_back(TiledArray::TiledRange1(tile_bounds, 
tile_bounds+ntiles));
  tile_ranges.push_back(TiledArray::TiledRange1(tile_bounds, 
tile_bounds+ntiles));
  TiledArray::TiledRange trange_2d(tile_ranges.begin(), tile_ranges.end());
  TiledArray::Array array_2d(world, trange_2d);
  TiledArray::Array array_2d_tr(array_2d.world(), 

Bug#853404: marked as done (libmpich-dev: drop the gcc version check in mpicxx.h)

[Debian Bug Tracking System]

Your message dated Thu, 10 Aug 2017 11:49:22 +
with message-id 
and subject line Bug#853404: fixed in mpich 3.3~a2-2
has caused the Debian Bug report #853404,
regarding libmpich-dev: drop the gcc version check in mpicxx.h
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.)


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

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]

/* confdefs.h */
#define PACKAGE_NAME "FORM"
#define PACKAGE_TARNAME "form"
#define PACKAGE_VERSION "4.1"
#define PACKAGE_STRING "FORM 4.1"
#define PACKAGE_BUGREPORT "f...@nikhef.nl"
#define PACKAGE_URL ""
#define PACKAGE "form"
#define VERSION "4.1"
#define MAJORVERSION 4
#define MINORVERSION 1
#define HAVE_PRODUCTIONDATE_H /**/
#define STDC_HEADERS 1
#define TIME_WITH_SYS_TIME 1
#define HAVE_SYS_TYPES_H 1
#define HAVE_SYS_STAT_H 1
#define HAVE_STDLIB_H 1
#define HAVE_STRING_H 1
#define HAVE_MEMORY_H 1
#define HAVE_STRINGS_H 1
#define HAVE_INTTYPES_H 1
#define HAVE_STDINT_H 1
#define HAVE_UNISTD_H 1
#define HAVE_FCNTL_H 1
#define HAVE_LIMITS_H 1
#define HAVE_SYS_FILE_H 1
#define LINUX /**/
#define HAVE_UNISTD_H 1
#define UNIX /**/
#define SIZEOF_CHAR 1
#define SIZEOF_SHORT 2
#define SIZEOF_INT 4
#define SIZEOF_LONG 8
#define SIZEOF_LONG_LONG 8
#define SIZEOF_VOID_P 8
#define SIZEOF_OFF_T 8
#define LP64 /**/
#ifdef WITHPTHREADS
#define WITHPOSIXCLOCK /**/
#endif

configure: exit 1
dh_auto_configure: ./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=${prefix}/include --mandir=${prefix}/share/man 
--infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=${prefix}/lib/x86_64-linux-gnu 
--libexecdir=${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
--disable-dependency-tracking --enable-parform returned exit code 1
debian/rules:13: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 2
make[1]: Leaving directory '/<>'
debian/rules:10: 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: mpich
Source-Version: 3.3~a2-2

We believe that the bug you reported is fixed in the latest version of
mpich, 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.
Alastair McKinstry  (supplier of updated mpich 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, 10 Aug 2017 09:29:30 +0100
Source: mpich
Binary: libmpich-dev libmpich12 mpich mpich-doc
Architecture: source amd64 all
Version: 3.3~a2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Bug#853324: marked as done (libmpich-dev: drop the gcc version check in mpicxx.h)

[Debian Bug Tracking System]

Your message dated Thu, 10 Aug 2017 11:49:22 +
with message-id 
and subject line Bug#853562: fixed in mpich 3.3~a2-2
has caused the Debian Bug report #853562,
regarding libmpich-dev: drop the gcc version check in mpicxx.h
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.)


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

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]
config.status: creating src/multi/casscf/Makefile
config.status: creating src/multi/zcasscf/Makefile
config.status: creating src/mat1e/Makefile
config.status: creating src/periodic/Makefile
config.status: creating src/opt/Makefile
config.status: creating src/alglib/Makefile
config.status: creating src/basis/Makefile
config.status: creating bagel_config.h
config.status: executing depfiles commands
config.status: executing libtool commands
configure: WARNING: unrecognized options: --disable-maintainer-mode
make[1]: Leaving directory '/<>'
   dh_auto_build
make -j1
make[1]: Entering directory '/<>'
make  all-recursive
make[2]: Entering directory '/<>'
Making all in src
make[3]: Entering directory '/<>/src'
Making all in util
make[4]: Entering directory '/<>/src/util'
Making all in parallel
make[5]: Entering directory '/<>/src/util/parallel'
/bin/bash ../../../libtool  --tag=CXX   --mode=compile mpicxx -DHAVE_CONFIG_H 
-I. -I../../..   -Wdate-time -D_FORTIFY_SOURCE=2 -I../../.. -g -O2 -DNDEBUG 
-DZDOT_RETURN -c -o process.lo process.cc
libtool: compile:  mpicxx -DHAVE_CONFIG_H -I. -I../../.. -Wdate-time 
-D_FORTIFY_SOURCE=2 -I../../.. -g -O2 -DNDEBUG -DZDOT_RETURN -c process.cc -o 
process.o
In file included from /usr/include/mpich/mpi.h:2231:0,
 from ../../../src/util/parallel/mpi_interface.h:36,
 from process.cc:27:
/usr/include/mpich/mpicxx.h:21:4: error: #error 'Please use the same version of 
GCC and g++ for compiling MPICH and user MPI programs'
 #  error 'Please use the same version of GCC and g++ for compiling MPICH and 
user MPI programs'
^
Makefile:444: recipe for target 'process.lo' failed
make[5]: *** [process.lo] Error 1
make[5]: Leaving directory '/<>/src/util/parallel'
Makefile:500: recipe for target 'all-recursive' failed
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory '/<>/src/util'
Makefile:584: recipe for target 'all-recursive' failed
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory '/<>/src'
Makefile:416: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/<>'
Makefile:348: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
debian/rules:9: 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: mpich
Source-Version: 3.3~a2-2

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

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

Thank you for reporting the bug, which will now be closed.  If you
have further comments please 

Bug#853562: marked as done (libmpich-dev: drop the gcc version check in mpicxx.h)

[Debian Bug Tracking System]

Your message dated Thu, 10 Aug 2017 11:49:22 +
with message-id 
and subject line Bug#853562: fixed in mpich 3.3~a2-2
has caused the Debian Bug report #853562,
regarding libmpich-dev: drop the gcc version check in mpicxx.h
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.)


-- 
853562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853562
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mpqc3
Version: 0.0~git20170114-4
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]
 from /usr/include/madness/world/worldprofile.h:37,
 from /usr/include/madness/world/world.h:70,
 from /usr/include/madness/world/MADworld.h:42,
 from /usr/include/TiledArray/madness.h:31,
 from /usr/include/tiledarray.h:25,
 from 
/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx:2:
/usr/include/tbb/pipeline.h:328:74: error: 'has_trivial_copy_constructor' is 
not a member of 'std'
 template struct tbb_trivially_copyable { enum { value = 
std::has_trivial_copy_constructor::value }; };
  
^~~~
/usr/include/tbb/pipeline.h:328:74: note: suggested alternative: 
'is_trivially_copy_constructible'
 template struct tbb_trivially_copyable { enum { value = 
std::has_trivial_copy_constructor::value }; };
  
^~~~
  
is_trivially_copy_constructible
/usr/include/tbb/pipeline.h:328:104: error: expected primary-expression before 
'>' token
 template struct tbb_trivially_copyable { enum { value = 
std::has_trivial_copy_constructor::value }; };

^
/usr/include/tbb/pipeline.h:328:107: error: '::value' has not been declared
 template struct tbb_trivially_copyable { enum { value = 
std::has_trivial_copy_constructor::value }; };

   ^
CMakeFiles/cmTC_79efd.dir/build.make:65: recipe for target 
'CMakeFiles/cmTC_79efd.dir/src.cxx.o' failed
make[3]: *** [CMakeFiles/cmTC_79efd.dir/src.cxx.o] Error 1
make[3]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
Makefile:126: recipe for target 'cmTC_79efd/fast' failed
make[2]: *** [cmTC_79efd/fast] Error 2
make[2]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'

Source file was:

#include 
int main(int argc, char** argv) {
  madness::World& world = madness::initialize(argc, argv);
  std::vector tile_ranges;
  size_t tile_bounds[] = {0, 3, 7}; // 2 tiles; N.B. double square brackets 
due to autoconf madness
  const size_t ntiles = sizeof(tile_bounds)/sizeof(size_t) - 1;
  tile_ranges.push_back(TiledArray::TiledRange1(tile_bounds, 
tile_bounds+ntiles));
  tile_ranges.push_back(TiledArray::TiledRange1(tile_bounds, 
tile_bounds+ntiles));
  TiledArray::TiledRange trange_2d(tile_ranges.begin(), tile_ranges.end());
  TiledArray::Array array_2d(world, trange_2d);
  TiledArray::Array array_2d_tr(array_2d.world(), 

Bug#871647: upx-ucl: uses convenience copy of LZMA library

[Thorsten Glaser]

Source: upx-ucl
Version: 3.93-1
Severity: serious
Justification: Policy §4.13
Control: found -1 3.94-2

Apparently upx-ucl reverted from using the system LZMA library
to its own. This, if not justified, is a Policy violation, for
various reasons, including maintainability and security.

Neither the changelog entry nor README.{Debian,source} contain
any justification, however.

Processed: upx-ucl: uses convenience copy of LZMA library

[Debian Bug Tracking System]

Processing control commands:

> found -1 3.94-2
Bug #871647 [src:upx-ucl] upx-ucl: uses convenience copy of LZMA library
Marked as found in versions upx-ucl/3.94-2.

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

Processed: limit source to libsoup2.4, tagging 871650

[Debian Bug Tracking System]

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

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

> tags 871650 + pending
Bug #871650 [src:libsoup2.4] libsoup2.4: CVE-2017-2885: stack based buffer 
overflow with HTTP Chunked Encoding
Ignoring request to alter tags of bug #871650 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#871680: gnome-disk-utility FTBFS with gnome-settings-daemon-dev 3.24.3-1

[Adrian Bunk]

Source: gnome-disk-utility
Version: 3.22.1-1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gnome-disk-utility.html

...
gdusdmanager.c:19:10: fatal error: 
gnome-settings-daemon/gnome-settings-plugin.h: No such file or directory
 #include 
  ^~~
compilation terminated.
Makefile:623: recipe for target 'libgdu_sd_la-gdusdmanager.lo' failed
make[4]: *** [libgdu_sd_la-gdusdmanager.lo] Error 1

Processed: limit source to libsoup2.4, tagging 871650

[Debian Bug Tracking System]

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

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

> tags 871650 + pending
Bug #871650 [src:libsoup2.4] libsoup2.4: CVE-2017-2885: stack based buffer 
overflow with HTTP Chunked Encoding
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#871650: marked as done (libsoup2.4: CVE-2017-2885: stack based buffer overflow with HTTP Chunked Encoding)

[Debian Bug Tracking System]

Your message dated Thu, 10 Aug 2017 16:50:28 +
with message-id 
and subject line Bug#871650: fixed in libsoup2.4 2.56.1-1
has caused the Debian Bug report #871650,
regarding libsoup2.4: CVE-2017-2885: stack based buffer overflow with HTTP 
Chunked Encoding
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.)


-- 
871650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871650
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libsoup2.4
Version: 2.48.0-1
Severity: grave
Tags: security patch upstream
Forwarded: https://bugzilla.gnome.org/show_bug.cgi?id=785774
Control: fixed -1 2.48.0-1+deb8u1
Control: fixed -1 2.56.0-2+deb9u1

Hi,

the following vulnerability was published for libsoup2.4.

CVE-2017-2885[0]:
stack based buffer overflow with HTTP Chunked Encoding

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-2885
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-2885
[1] https://bugzilla.gnome.org/show_bug.cgi?id=785774
[2] 
https://git.gnome.org/browse/libsoup/commit/?id=03c91c76daf70ee227f38304c5e45a155f45073d

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libsoup2.4
Source-Version: 2.56.1-1

We believe that the bug you reported is fixed in the latest version of
libsoup2.4, 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.
Emilio Pozuelo Monfort  (supplier of updated libsoup2.4 
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, 10 Aug 2017 18:29:43 +0200
Source: libsoup2.4
Binary: libsoup2.4-dev libsoup2.4-1 libsoup-gnome2.4-1 libsoup-gnome2.4-dev 
libsoup2.4-doc gir1.2-soup-2.4
Architecture: source
Version: 2.56.1-1
Distribution: unstable
Urgency: high
Maintainer: Debian GNOME Maintainers 

Changed-By: Emilio Pozuelo Monfort 
Description:
 gir1.2-soup-2.4 - GObject introspection data for the libsoup HTTP library
 libsoup-gnome2.4-1 - HTTP library implementation in C -- GNOME support library
 libsoup-gnome2.4-dev - HTTP library implementation in C -- GNOME support 
development fil
 libsoup2.4-1 - HTTP library implementation in C -- Shared library
 libsoup2.4-dev - HTTP library implementation in C -- Development files
 libsoup2.4-doc - HTTP library implementation in C -- API Reference
Closes: 871650
Changes:
 libsoup2.4 (2.56.1-1) unstable; urgency=high
 .
   * New upstream release.
 + CVE-2017-2885: Fixed a chunked decoding buffer overrun that
   could be exploited against either clients or servers.
   Closes: #871650.
Checksums-Sha1:
 20a79357f4d646d383a127cd391d5fe2affb26f8 2706 libsoup2.4_2.56.1-1.dsc
 097fb1ad0b30e88b8fc9b924917c9344be2f48a3 1806416 libsoup2.4_2.56.1.orig.tar.xz
 5d2e8170c45b0761f179f6bb04789d78194310d1 19044 
libsoup2.4_2.56.1-1.debian.tar.xz
 778cf401e3eef7a480db6e8c0c5f5cc28be392be 9686 
libsoup2.4_2.56.1-1_source.buildinfo
Checksums-Sha256:
 0d641a3940842381e7de5a6ed6dc3956a60ac2e3b78d05ab9d215f1e7a0e8df9 2706 
libsoup2.4_2.56.1-1.dsc
 c32a46d77b4da433b51d8fd09a57a44b198e03bdc93e5219afcc687c7948eac3 1806416 
libsoup2.4_2.56.1.orig.tar.xz
 7b007ac21c78e0f1d47f2d95bb3fd253cd60c5b4d9301fb7a6a44d07e9b0d592 19044 
libsoup2.4_2.56.1-1.debian.tar.xz
 ba125c252e878dcf7aacbeeff466d71c5bd7a7965473eff5ea3e495f4c0c7e7d 9686 
libsoup2.4_2.56.1-1_source.buildinfo
Files:
 aee185a0877d1ed9ec251a3a7067b83c 2706 devel optional libsoup2.4_2.56.1-1.dsc
 e8ac8967e9a57296688739021aa71b9b 1806416 devel optional 
libsoup2.4_2.56.1.orig.tar.xz
 2a48dca2b0452ee4fa2d99aca9d69e95 19044 devel optional 
libsoup2.4_2.56.1-1.debian.tar.xz
 efd2648f8feb3068ecaaec38ffa76a8e 9686 devel optional 
libsoup2.4_2.56.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEcJymx+vmJZxd92Q+nUbEiOQ2gwIFAlmMiigACgkQnUbEiOQ2
gwJWqQ/9Gyg3mhIbJWyCNYIBosJ3HZ2+q4uU1VrAcSXZOIcdvluNh6MdS70HJ9IP

Bug#871557: marked as done (mixmaster: segmentation fault in DES key handling)

[Debian Bug Tracking System]

Your message dated Thu, 10 Aug 2017 17:19:59 +
with message-id 
and subject line Bug#871557: fixed in mixmaster 3.0.0-10
has caused the Debian Bug report #871557,
regarding mixmaster: segmentation fault in DES key handling
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.)


-- 
871557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871557
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mixmaster
Version: 3.0.0-9
Severity: grave
Tags: patch

Dear Maintainer,

the conversion to use libssl 1.1 renders the package allmost unusable
due to segmentation faults in DES key handling.
DES_set_key() does not allocate memory. After converting
"des_key_schedule X" to "DES_key_schedule *X" DES_set_key() tries to
access memory through an uninitialized pointer. Change conversion to
"DES_key_schedule X" and adapt the usage from "X" to "".

Regards
Bene
diff -ruNp mixmaster-3.0.0.orig/debian/patches/mixmaster-libssl-1.1.patch mixmaster-3.0.0/debian/patches/mixmaster-libssl-1.1.patch
--- mixmaster-3.0.0.orig/debian/patches/mixmaster-libssl-1.1.patch	2017-07-02 19:28:00.0 +0200
+++ mixmaster-3.0.0/debian/patches/mixmaster-libssl-1.1.patch	2017-08-08 21:50:58.703847144 +0200
@@ -176,9 +176,9 @@ Migrate to libssl 1.1
 -  des_key_schedule ks2;
 -  des_key_schedule ks3;
 -  des_cblock i;
-+  DES_key_schedule *ks1;
-+  DES_key_schedule *ks2;
-+  DES_key_schedule *ks3;
++  DES_key_schedule ks1;
++  DES_key_schedule ks2;
++  DES_key_schedule ks3;
 +  DES_cblock i;
  
assert(enc == ENCRYPT || enc == DECRYPT);
@@ -188,16 +188,16 @@ Migrate to libssl 1.1
memcpy(i, iv->data, 8);	/* leave iv buffer unchanged */
 -  des_set_key((const_des_cblock *) key->data, ks1);
 -  des_set_key((const_des_cblock *) (key->data + 8), ks2);
-+  DES_set_key((const_DES_cblock *) key->data, ks1);
-+  DES_set_key((const_DES_cblock *) (key->data + 8), ks2);
++  DES_set_key((const_DES_cblock *) key->data, );
++  DES_set_key((const_DES_cblock *) (key->data + 8), );
if (key->length == 16)
 -des_set_key((const_des_cblock *) key->data, ks3);
-+DES_set_key((const_DES_cblock *) key->data, ks3);
++DES_set_key((const_DES_cblock *) key->data, );
else
 -des_set_key((const_des_cblock *) (key->data + 16), ks3);
 -  des_ede3_cbc_encrypt(buf->data, buf->data, buf->length, ks1, ks2, ks3,
-+DES_set_key((const_DES_cblock *) (key->data + 16), ks3);
-+  DES_ede3_cbc_encrypt(buf->data, buf->data, buf->length, ks1, ks2, ks3,
++DES_set_key((const_DES_cblock *) (key->data + 16), );
++  DES_ede3_cbc_encrypt(buf->data, buf->data, buf->length, , , ,
  		   , enc);
return (0);
  }
@@ -208,9 +208,9 @@ Migrate to libssl 1.1
 -  des_key_schedule ks1;
 -  des_key_schedule ks2;
 -  des_key_schedule ks3;
-+  DES_key_schedule *ks1;
-+  DES_key_schedule *ks2;
-+  DES_key_schedule *ks3;
++  DES_key_schedule ks1;
++  DES_key_schedule ks2;
++  DES_key_schedule ks3;
  
assert(enc == ENCRYPT || enc == DECRYPT);
assert(key->length == 24 && iv->length == 8);
@@ -220,10 +220,10 @@ Migrate to libssl 1.1
 -  des_set_key((const_des_cblock *) (key->data + 16), ks3);
 -  des_ede3_cfb64_encrypt(buf->data, buf->data, buf->length, ks1, ks2, ks3,
 -			(des_cblock *) iv->data, , enc);
-+  DES_set_key((const_DES_cblock *) key->data, ks1);
-+  DES_set_key((const_DES_cblock *) (key->data + 8), ks2);
-+  DES_set_key((const_DES_cblock *) (key->data + 16), ks3);
-+  DES_ede3_cfb64_encrypt(buf->data, buf->data, buf->length, ks1, ks2, ks3,
++  DES_set_key((const_DES_cblock *) key->data, );
++  DES_set_key((const_DES_cblock *) (key->data + 8), );
++  DES_set_key((const_DES_cblock *) (key->data + 16), );
++  DES_ede3_cfb64_encrypt(buf->data, buf->data, buf->length, , , ,
 +			(DES_cblock *) iv->data, , enc);
return (0);
  }
@@ -240,9 +240,9 @@ Migrate to libssl 1.1
 -  des_key_schedule ks1;
 -  des_key_schedule ks2;
 -  des_key_schedule ks3;
-+  DES_key_schedule *ks1;
-+  DES_key_schedule *ks2;
-+  DES_key_schedule *ks3;
++  DES_key_schedule ks1;
++  DES_key_schedule ks2;
++  DES_key_schedule ks3;
SHA_CTX c;
  
assert(key->length == 25);
@@ -253,38 +253,44 @@ Migrate to libssl 1.1
 -  des_set_key((const_des_cblock *) (key->data + 1), ks1);
 -  des_set_key((const_des_cblock *) (key->data + 9), ks2);
 -  des_set_key((const_des_cblock *) (key->data+ 17), ks3);
-+  DES_set_key((const_DES_cblock *) (key->data + 1), ks1);
-+  DES_set_key((const_DES_cblock *) (key->data + 9), ks2);
-+  DES_set_key((const_DES_cblock *) (key->data+ 17), ks3);
++  DES_set_key((const_DES_cblock *) 

Bug#871685: courier FTBFS: configure: error: /usr/bin/gpg not found

[Adrian Bunk]

Source: courier
Version: 0.77.0-1
Severity: serious

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

...
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking whether ln -s works... yes
checking for gpg... no
checking for gpg2... no
configure: error: /usr/bin/gpg not found
configure: error: ./configure failed for libs/gpglib

Bug#853455: marked as done (inspircd: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Thu, 10 Aug 2017 19:19:44 +
with message-id 
and subject line Bug#853455: fixed in inspircd 2.0.24-1
has caused the Debian Bug report #853455,
regarding inspircd: 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.)


-- 
853455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853455
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:inspircd
Version: 2.0.23-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/inspircd_2.0.23-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

[...]
m_regex_tre.cpp= enabled
m_sqlite3.cpp  = enabled
m_ssl_gnutls.cpp   = enabled
m_ssl_openssl.cpp  = disabled
Remember: YOU are responsible for making sure any libraries needed have been 
installed!
# Really launch configure
./configure --disable-interactive \
--with-cc=g++ \
--uid=39 \
--enable-gnutls \
--prefix=/usr/lib/inspircd \
--config-dir=/etc/inspircd \
--module-dir=/usr/lib/inspircd/modules \
--binary-dir=/usr/sbin
`g++` was not found! A C++ compiler is required to build InspIRCd!
You can pass a custom compiler to ./configure using --with-cc=[name].
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
# compile binary with debuginfo and optimization (make D=2 all) as upstream
# don't generate symbols by default. dh_strip generate a -dbg package
# (see below)
# show compiler commandline when building,
# ccache can use it to speed the build (V=1)
dh_auto_build --parallel -- D=2 V=1 all
make[1]: Leaving directory '/<>'
   dh_auto_test
   create-stamp debian/debhelper-build-stamp
 fakeroot debian/rules binary
dh binary --with systemd
   create-stamp debian/debhelper-build-stamp
   dh_testroot
   dh_prep
   dh_installdirs
   debian/rules override_dh_auto_install
make[1]: Entering directory '/<>'
dh_auto_install -- install DESTDIR=/<>/debian/inspircd
# Delete example files (already in /usr/share/doc/inspircd/examples)
rm -rf /<>/debian/inspircd/etc/inspircd/examples
# delete empty data and log dir
rmdir /<>/debian/inspircd/usr/lib/inspircd/data \
/<>/debian/inspircd/usr/lib/inspircd/logs
rmdir: failed to remove 
'/<>/debian/inspircd/usr/lib/inspircd/data': No such file or 
directory
rmdir: failed to remove 
'/<>/debian/inspircd/usr/lib/inspircd/logs': No such file or 
directory
debian/rules:51: recipe for target 'override_dh_auto_install' failed
make[1]: *** [override_dh_auto_install] Error 1
make[1]: Leaving directory '/<>'
debian/rules:81: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
--- End Message ---
--- Begin Message ---
Source: inspircd
Source-Version: 2.0.24-1

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

(This message was generated automatically at their 

Bug#853537: mariadb-10.1: ftbfs with GCC-7

[Ondřej Surý]

Package: src:mariadb-10.1
Followup-For: Bug #853537

Hi Matthias,

the full build.log you sent contains:

make[4]: Leaving directory '/<>/builddir'
Error running link command: Segmentation fault
make[4]: Leaving directory '/<>/builddir'
storage/tokudb/PerconaFT/portability/CMakeFiles/tokuportability_static_conv.dir/build.make:328:
 recipe for target 
'storage/tokudb/PerconaFT/portability/libtokuportability_static_conv.a' failed
make[4]: *** 
[storage/tokudb/PerconaFT/portability/libtokuportability_static_conv.a] Error 1
make[4]: Leaving directory '/<>/builddir'
CMakeFiles/Makefile2:6419: recipe for target 
'storage/tokudb/PerconaFT/portability/CMakeFiles/tokuportability_static_conv.dir/all'
 failed
make[3]: *** 
[storage/tokudb/PerconaFT/portability/CMakeFiles/tokuportability_static_conv.dir/all]
 Error 2
make[3]: *** Waiting for unfinished jobs
make[4]: Leaving directory '/<>/builddir'

Notice the:
Error running link command: Segmentation fault

It was just buried in the logs because of parallel build.

I can reproduce this with mariadb-10.1_10.1.26 that I am trying to
build now and it's failing with the same error.

I am not sure this is strictly mariadb-10.1's code fault, but I am
willing to help to debug the issue, hence I am not reassigning it to
gcc-7 (and/or binutils).

Cheers,
Ondrej

-- System Information:
Debian Release: 9.0
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'unstable-debug'), (500, 'stable-debug'), 
(500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Bug#870686: libglvnd: not ready for buster, yet

[Timo Aaltonen]

On 04.08.2017 07:29, Andreas Beckmann wrote:
> Source: libglvnd
> Version: 0.2.999+git20170802-2
> Severity: serious
> 
> Since the mesa packaging hasn't switched to glvnd, yet, there are file
> conflicts between several packages from src:mesa and src:libglvnd.
> So let's keep libglvnd out of testing until this transition progresses.

Yep, mesa 17.2.0~rc3-2 will be the first version to use libglvnd and
I'll upload it to experimental today. After 17.2.0 is released in a few
weeks it'll hopefully enter unstable.


-- 
t

Bug#871096: marked as done (twpsk: FTBFS: twpskCB.C:994:72: error: ISO C++ forbids comparison between pointer and integer [-fpermissive])

[Debian Bug Tracking System]

Your message dated Thu, 10 Aug 2017 11:05:21 +
with message-id 
and subject line Bug#871096: fixed in twpsk 4.2-2
has caused the Debian Bug report #871096,
regarding twpsk: FTBFS: twpskCB.C:994:72: error: ISO C++ forbids comparison 
between pointer and integer [-fpermissive]
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.)


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

Hi,

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

Relevant part (hopefully):
> g++ -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
> -DPKG_DATA_DIR=\"/usr/share/twpsk\" -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o twpskCB.o twpskCB.C
> twpskCB.C: In function 'void rxTextCB(Widget, XtPointer, XtPointer)':
> twpskCB.C:994:72: error: ISO C++ forbids comparison between pointer and 
> integer [-fpermissive]
>   if ((strncmp (str, save, MAXCALL) == 0) || (calls->outCall == '\0'))
> ^~~~
> Makefile:495: recipe for target 'twpskCB.o' failed
> make[3]: *** [twpskCB.o] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/twpsk_4.2-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: twpsk
Source-Version: 4.2-2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 07 Aug 2017 06:02:58 +
Source: twpsk
Binary: twpsk
Architecture: source amd64
Version: 4.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Hamradio Maintainers 
Changed-By: Ervin Hegedus 
Description:
 twpsk  - Soundcard-based X program for operating PSK31
Closes: 871096
Changes:
 twpsk (4.2-2) unstable; urgency=medium
 .
   * Team upload
   * Fixed FTBFS bug (Closes: #871096)
   * Bump Standards Version to 4.0.0
Checksums-Sha1:
 bf7f97c8d90ace923cfdb99d2f982f3fa86b2754 1899 twpsk_4.2-2.dsc
 b795c7996a2c7218e4d7faa4eaacfec5718e4048 5876 twpsk_4.2-2.debian.tar.xz
 ef7a748cfb1868a7403f893f95cd32f17f22e422 192066 twpsk-dbgsym_4.2-2_amd64.deb
 ac40089a2d5b29220e308b5ab239ad8c51a3dde5 8643 twpsk_4.2-2_amd64.buildinfo
 9c66c1c86a4ee0194c8c69c75dd4c255d4fbd23c 71716 twpsk_4.2-2_amd64.deb
Checksums-Sha256:
 f92afff9fe994b0c42ab57cbf881135ef422b8a16893c476277ac89c383818b7 1899 
twpsk_4.2-2.dsc
 ac453ceedee538f4318d9b29a2d82dfb1880920d2497a7f7ec5bbed1d0211a33 5876 
twpsk_4.2-2.debian.tar.xz
 417769d97ec6be9edbfa8f5af2ed14c0e7fd1a68440c2cdef24fa249be7149d7 192066 
twpsk-dbgsym_4.2-2_amd64.deb
 59d90cfa62ab0df1eb19d88594b4d9b627aad7ed4a1d8de3128ee9ee4f26b60c 8643 
twpsk_4.2-2_amd64.buildinfo
 c1669e027ac1824cf0ece1b37a59827559e2e7aea52b7e6116fc7e9a8319a5ad 71716 
twpsk_4.2-2_amd64.deb
Files:
 bb7ce1a8b109f45aad171a0bd439c5b7 1899 hamradio optional twpsk_4.2-2.dsc
 53b263ff414bed12fbc3f1207a7973aa 5876 hamradio optional 
twpsk_4.2-2.debian.tar.xz
 3c59212287b0b70c4040143fff88ab08 192066 debug extra 
twpsk-dbgsym_4.2-2_amd64.deb
 5b35b8258041e253b2c465930909db79 8643 hamradio optional 
twpsk_4.2-2_amd64.buildinfo
 72e2ed3c0200f02c02151488fbc8a9b9 71716 hamradio optional twpsk_4.2-2_amd64.deb

-BEGIN PGP SIGNATURE-

Bug#853423: Patches

[yang]

gmchess.tar.xz
Description: application/xz

Bug#870267: graphicsmagick frequently FTBFS on ppc64el: test hang

[GCS]

Control: severity -1 important

On Sat, Aug 5, 2017 at 3:44 PM, Adrian Bunk  wrote:
> On Mon, Jul 31, 2017 at 06:12:54PM +0200, László Böszörményi (GCS) wrote:
>> But the most important thing is that the fail always happened on
>> ppc64el-unicamp-01 - the other buildd, ppc64el-osuosl-01 can build it
>> without any problem. As such, I think it's the buildd that different
>> in some way than the source has any known problem.
>> Can you reschedule the build, first on ppc64el-unicamp-01, then on
>> ppc64el-osuosl-01 and see the results?
>
> I don't have any powers to reschedule anything.
 OK, your involvement - quickly file and follow FTBFS bugs - assumed
more power on buildds.

>> Maybe the former is not up to
>> date and has some inconsistent package set installed?
>
> chroots on the buildds are regenerated twice per week.
 OK, GCC 7.1.0 arrived to ppc64el and GraphicsMagick no longer FTBFS
even on ppc64el-unicamp-01. I don't close this bugreport but lower the
severity to let the security fixes finally migrate to Buster
(testing). I'll see how future builds do on ppc64el and will act
accordingly.

Regards,
Laszlo/GCS