Bug#846773: tarantool: FTBFS: ld: final link failed: Nonrepresentable section on output

[Roman Tsisyk]

Hi Lucas,

>Saturday, December  3, 2016 12:11 PM +03:00 from Lucas Nussbaum 
>:
>During a rebuild of all packages in sid, your package failed to build on
>amd64.
>
>Relevant part (hopefully):
>> /usr/bin/ld: host/minilua.o: relocation R_X86_64_32S against `.rodata' can 
>> not be used when making a shared object; recompile with -fPIC
>> /usr/bin/ld: final link failed: Nonrepresentable section on output
>> collect2: error: ld returned 1 exit status

I already realized the root cause of this problem after explanation in #845484.
A new package will be pushed soon.

-- 
WBR,
  Roman Tsisyk 
  http://tarantool.org/ - an efficient in-memory data store and a Lua 
application server

Bug#846743: marked as done (node-normalize-path: FTBFS: Test failures)

[Debian Bug Tracking System]

Your message dated Sun, 04 Dec 2016 06:18:18 +
with message-id 
and subject line Bug#846743: fixed in node-normalize-path 2.0.1-2
has caused the Debian Bug report #846743,
regarding node-normalize-path: FTBFS: Test failures
to be marked as done.

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

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


-- 
846743: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846743
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-normalize-path
Version: 2.0.1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161202 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):
> at Function.Module._load (module.js:300:12)
> at Module.require (module.js:353:17)
> at require (internal/module.js:12:17)
> at /usr/lib/nodejs/mocha/lib/mocha.js:172:27
> at Array.forEach (native)
> at Mocha.loadFiles (/usr/lib/nodejs/mocha/lib/mocha.js:169:14)
> at Mocha.run (/usr/lib/nodejs/mocha/lib/mocha.js:356:31)
> at Object. (/usr/lib/nodejs/mocha/bin/_mocha:366:16)
> at Module._compile (module.js:409:26)
> at Object.Module._extensions..js (module.js:416:10)
> at Module.load (module.js:343:32)
> at Function.Module._load (module.js:300:12)
> at Function.Module.runMain (module.js:441:10)
> at startup (node.js:139:18)
> at node.js:974:3
> debian/rules:13: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   
http://aws-logs.debian.net/2016/12/02/node-normalize-path_2.0.1-1_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Sruthi Chandran  (supplier of updated node-normalize-path 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 03 Dec 2016 23:05:53 +0530
Source: node-normalize-path
Binary: node-normalize-path
Architecture: source
Version: 2.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Sruthi Chandran 
Description:
 node-normalize-path - Normalize file path slashes to be unix-like forward 
slashes
Closes: 846743
Changes:
 node-normalize-path (2.0.1-2) unstable; urgency=medium
 .
   * Add node-minimist to builddeps (Closes: #846743)
Checksums-Sha1:
 4de5e49c4410f59dd508e464c2f0b9c4f0993673 2171 node-normalize-path_2.0.1-2.dsc
 8b8c02eb616ebc5e4d523a64f2ebfb30342613fa 2184 
node-normalize-path_2.0.1-2.debian.tar.xz
Checksums-Sha256:
 a1a2dbbc40a70750083fe96ae65e51c2bd3d03d1a3cc6f8dee2b3d6a8a930075 2171 
node-normalize-path_2.0.1-2.dsc
 01ae1737e8cf6bbfae7dfeffb001401648f1a7b27e0bbe8283c2eed254d0c788 2184 
node-normalize-path_2.0.1-2.debian.tar.xz
Files:
 985c3111f41d55abfed2e8c9a5fd324b 2171 web optional 
node-normalize-path_2.0.1-2.dsc
 2870b91e8d4e7fbba9c8341f1bf77ff9 2184 web optional 
node-normalize-path_2.0.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEsclPZxif+sAmSPvz1N6yL8C5bhUFAlhDsTAACgkQ1N6yL8C5
bhUVpA/+Ktbo5mMI0c+v1E+lbMESp0DjlCWdw71HLvuk6EGD/CR8XDPLOZkZPX4h
lvbjKAoyCoPIzB6dqLntr0XG4H21wN7nh178J0xUTWoN3l9iO9JBt6HWvu5zKJGE
RY7eTZbBCiJpxJSCksv0vqFOTtJb+2gbXbCF6cHijCoVylGQCD1kRSkKE6mDpBp1
LBbFTrz3s11Dd/OHobr2/0gXAu2FkAhfvH57cUIIjnsJj32+xKnq8a/SV++Qhi6C
gXfNhNi9Bq2m28R7mqnkDdtTvdsSLXa8kiFXOpvC4Tt5ayvXCTCqBht9HwnShc2O
EssRmh34MAAl7xQybYjU1TGlIZ4yoYiqLldB/c5U+WVHIFIR7/r8B+qRQqGWy4WB

Processed: Re: Bug#845058: [Pkg-fonts-devel] Bug#845058: Bug#845058: fonts-noto: Installing the package freezes all graphical applications.

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #845058 [fonts-noto-cjk] fonts-noto: Installing the package freezes all 
graphical applications.
Severity set to 'normal' from 'critical'

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

Bug#845058: [Pkg-fonts-devel] Bug#845058: Bug#845058: fonts-noto: Installing the package freezes all graphical applications.

[陳昌倬]

Control: severity -1 normal

Lower the severity to normal since it just causes temporary freeze.


-- 
ChangZhuo Chen (陳昌倬) 
Debian Developer (https://nm.debian.org/public/person/czchen)
Key fingerprint = BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


signature.asc
Description: PGP signature

Bug#832062: marked as done (supertuxkart: source for GPL song Boom_boom_boom.ogg missing)

[Debian Bug Tracking System]

Your message dated Sun, 04 Dec 2016 05:04:35 +
with message-id 
and subject line Bug#832062: fixed in supertuxkart 0.9.2+dfsg-2
has caused the Debian Bug report #832062,
regarding supertuxkart: source for GPL song Boom_boom_boom.ogg missing
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.)


-- 
832062: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832062
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: supertuxkart
Version: 0.9.2-1
Severity: serious
Justification: does not include source code of GPL licensed work

Supertuxkart contains a song called "Boom boom boom" in Ogg Vorbis
format. According to the credits and debian/copyright, this song is
created by Matt Thomas, and is licensed under the GNU GPL v3 or later.
The source of the .ogg file is missing. Although what consists the
source of media assets can be unclear, I would like to point out that
there is also a module tracker version of this song, which can
reasonably considered the source, as it contains the score, the samples
used and can be editted in any module editor:

https://modarchive.org/index.php?request=view_by_moduleid=38184

This module contains the following text:

> -kbx128-  march 1993
> music for a crap amos
> game written by my
> brother.(only joking)

There is also some doubt that Matt Thomas and kbx128 are the same
person:

http://forum.freegamedev.net/viewtopic.php?t=6562=66000

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

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

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: supertuxkart
Source-Version: 0.9.2+dfsg-2

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

Debian distribution maintenance software
pp.
Vincent Cheng  (supplier of updated supertuxkart package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat,  3 Dec 2016 19:39:13 PST
Source: supertuxkart
Binary: supertuxkart supertuxkart-data supertuxkart-dbg
Architecture: source all
Version: 0.9.2+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Vincent Cheng 
Description: 
 supertuxkart - 3D kart racing game
 supertuxkart-data - 3D kart racing game (data)
 supertuxkart-dbg - 3D kart racing game (debug)
Closes: 830748 830751 832062
Changes:
 supertuxkart (0.9.2+dfsg-2) unstable; urgency=medium
 .
   * Fix FTBFS on arm64, mips/mips64/mipsel, ppc64el, s390x. (Closes: #830748)
 - Add debian/patches/fix_angelscript_ftbfs.patch.
   * Remove non-free Ubuntu Font Family fonts, replaced with Cantarell.
 (Closes: #830751)
 - Add new dependency on fonts-cantarell.
 - Add debian/patches/replace-fonts-ubuntu-with-cantarell.patch to replace
   references to Ubuntu Font Family fonts.
   * Clarify licensing for Boom_boom_boom.ogg and add source mod files to
 tarball. (Closes: #832062)
 - Add debian/patches/update_boom_boom_boom_license.patch.
Checksums-Sha256: 
 15c48d2c264dea6d6f61d851e331e91ded4b7d83b30b483bb69553b7de9b53b0 2516 
supertuxkart_0.9.2+dfsg-2.dsc
 1a888927283761010c57072f494ade2f4c9394867b5a894a08043839355ca4d5 501311920 
supertuxkart_0.9.2+dfsg.orig.tar.xz
 e177ee6dc8af535e9a19ca87c3325653f53aab58e526c81a7c8f158b3d9fd174 2499604 
supertuxkart_0.9.2+dfsg-2.debian.tar.xz
 49e095db2fc2822fea63ae011e2b98faaeb8c959fae0aadeb82770124ccc72fa 487066874 
supertuxkart-data_0.9.2+dfsg-2_all.deb
Checksums-Sha1: 
 241b7835121e64635af1f296b6f37daf7d7f99a6 2516 supertuxkart_0.9.2+dfsg-2.dsc
 ce17c8e83dd53b78c3b06982b19b6933ec87aad1 501311920 
supertuxkart_0.9.2+dfsg.orig.tar.xz
 abe5d0d3c6c27ec6c467be33b6cffa25d5473bd0 2499604 

Bug#830751: marked as done (supertuxkart-data: contains non-free Ubuntu Font Family fonts)

[Debian Bug Tracking System]

Your message dated Sun, 04 Dec 2016 05:04:35 +
with message-id 
and subject line Bug#830751: fixed in supertuxkart 0.9.2+dfsg-2
has caused the Debian Bug report #830751,
regarding supertuxkart-data: contains non-free Ubuntu Font Family fonts
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.)


-- 
830751: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830751
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: supertuxkart-data
Version: 0.9.2-1
Severity: serious
Justification: non DFSG file in the source package

supertuxkart/0.9.2-1 ships with the following files in the source tarball:

data/ttf/Ubuntu-B.ttf
data/ttf/Ubuntu-R.ttf

...which get installed into binary package supertuxkart-data:

/usr/share/games/supertuxkart/data/ttf/Ubuntu-B.ttf
/usr/share/games/supertuxkart/data/ttf/Ubuntu-R.ttf

These ttf files are Ubuntu Font Family fonts, which are not
DFSG-compatible as per ftpmasters' decision [1], with rationale
provided at [2]; further discussion can be found at [3]. These fonts
files will need to be replaced in Debian; I intend to also forward
this bug report upstream.

Regards,
Vincent

[1] 
http://lists.alioth.debian.org/pipermail/pkg-fonts-devel/2011-April/006515.html
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603157#30
[3] https://bugs.launchpad.net/ubuntu-font-licence/+bug/769874
--- End Message ---
--- Begin Message ---
Source: supertuxkart
Source-Version: 0.9.2+dfsg-2

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

Debian distribution maintenance software
pp.
Vincent Cheng  (supplier of updated supertuxkart package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat,  3 Dec 2016 19:39:13 PST
Source: supertuxkart
Binary: supertuxkart supertuxkart-data supertuxkart-dbg
Architecture: source all
Version: 0.9.2+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Vincent Cheng 
Description: 
 supertuxkart - 3D kart racing game
 supertuxkart-data - 3D kart racing game (data)
 supertuxkart-dbg - 3D kart racing game (debug)
Closes: 830748 830751 832062
Changes:
 supertuxkart (0.9.2+dfsg-2) unstable; urgency=medium
 .
   * Fix FTBFS on arm64, mips/mips64/mipsel, ppc64el, s390x. (Closes: #830748)
 - Add debian/patches/fix_angelscript_ftbfs.patch.
   * Remove non-free Ubuntu Font Family fonts, replaced with Cantarell.
 (Closes: #830751)
 - Add new dependency on fonts-cantarell.
 - Add debian/patches/replace-fonts-ubuntu-with-cantarell.patch to replace
   references to Ubuntu Font Family fonts.
   * Clarify licensing for Boom_boom_boom.ogg and add source mod files to
 tarball. (Closes: #832062)
 - Add debian/patches/update_boom_boom_boom_license.patch.
Checksums-Sha256: 
 15c48d2c264dea6d6f61d851e331e91ded4b7d83b30b483bb69553b7de9b53b0 2516 
supertuxkart_0.9.2+dfsg-2.dsc
 1a888927283761010c57072f494ade2f4c9394867b5a894a08043839355ca4d5 501311920 
supertuxkart_0.9.2+dfsg.orig.tar.xz
 e177ee6dc8af535e9a19ca87c3325653f53aab58e526c81a7c8f158b3d9fd174 2499604 
supertuxkart_0.9.2+dfsg-2.debian.tar.xz
 49e095db2fc2822fea63ae011e2b98faaeb8c959fae0aadeb82770124ccc72fa 487066874 
supertuxkart-data_0.9.2+dfsg-2_all.deb
Checksums-Sha1: 
 241b7835121e64635af1f296b6f37daf7d7f99a6 2516 supertuxkart_0.9.2+dfsg-2.dsc
 ce17c8e83dd53b78c3b06982b19b6933ec87aad1 501311920 
supertuxkart_0.9.2+dfsg.orig.tar.xz
 abe5d0d3c6c27ec6c467be33b6cffa25d5473bd0 2499604 
supertuxkart_0.9.2+dfsg-2.debian.tar.xz
 867cd98f732990fdce1dac9dc68577ed06201981 487066874 
supertuxkart-data_0.9.2+dfsg-2_all.deb
Files: 
 10d3148550786c3b7200283e9e1137d1 2516 games optional 
supertuxkart_0.9.2+dfsg-2.dsc
 ccad08c877fb79606c60d92a2acb69d3 501311920 games optional 
supertuxkart_0.9.2+dfsg.orig.tar.xz
 fe838082180802f2815d82cf58445bf2 2499604 games optional 
supertuxkart_0.9.2+dfsg-2.debian.tar.xz
 81823cca1b231147dcebddfd8d578aa6 487066874 games optional 

Bug#830748: marked as done (supertuxkart: FTBFS on arm64, mips/mips64/mipsel, ppc64el, s390x)

[Debian Bug Tracking System]

Your message dated Sun, 04 Dec 2016 05:04:35 +
with message-id 
and subject line Bug#830748: fixed in supertuxkart 0.9.2+dfsg-2
has caused the Debian Bug report #830748,
regarding supertuxkart: FTBFS on arm64, mips/mips64/mipsel, ppc64el, s390x
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.)


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

supertuxkart/0.9.2-1 FTBFS on arm64, mips/mips64/mipsel, ppc64el, and
s390x; full build log at [1], and here's the relevant part of the log:

[  9%] Building CXX object
lib/irrlicht/CMakeFiles/stkirrlicht.dir/source/Irrlicht/CGUIMeshViewer.cpp.o
cd /«PKGBUILDDIR»/obj-aarch64-linux-gnu/lib/irrlicht && /usr/bin/c++
-DGLEW_NO_GLU -DIRRLICHT_EXPORTS=1 -DNDEBUG=1
-DNO_IRR_LINUX_X11_VIDMODE_ -DPNG_NO_MMX_CODE -DPNG_NO_MNG_FEATURES
-DPNG_THREAD_UNSAFE_OK -D_IRR_LINUX_X11_RANDR_
-I/«PKGBUILDDIR»/lib/bullet/src -I/«PKGBUILDDIR»/lib/glew/include
-I/«PKGBUILDDIR»/lib/irrlicht/include  -g -O2 -fstack-protector-strong
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2
-Wall -pipe -O3  -fno-exceptions  -fstrict-aliasing
-I/usr/X11R6/include -Wall -pipe -O3  -fno-exceptions
-fstrict-aliasing -I/usr/X11R6/include -fexpensive-optimizations -O2
-DNDEBUG   -o CMakeFiles/stkirrlicht.dir/source/Irrlicht/CGUIMeshViewer.cpp.o
-c /«PKGBUILDDIR»/lib/irrlicht/source/Irrlicht/CGUIMeshViewer.cpp
/«PKGBUILDDIR»/lib/angelscript/source/as_callfunc_x64_gcc.cpp: In
function 'asQWORD X64_CallFunction(const asQWORD*, int, funcptr_t,
asQWORD&, bool)':
/«PKGBUILDDIR»/lib/angelscript/source/as_callfunc_x64_gcc.cpp:162:82:
error: unknown register name '%rcx' in 'asm'
 "%rdi", "%rsi", "%rax", "%rdx", "%rcx", "%r8", "%r9", "%r10",
"%r11", "%r15");

   ^
/«PKGBUILDDIR»/lib/angelscript/source/as_callfunc_x64_gcc.cpp:162:82:
error: unknown register name '%rdx' in 'asm'
/«PKGBUILDDIR»/lib/angelscript/source/as_callfunc_x64_gcc.cpp:162:82:
error: unknown register name '%rax' in 'asm'
/«PKGBUILDDIR»/lib/angelscript/source/as_callfunc_x64_gcc.cpp:162:82:
error: unknown register name '%rsi' in 'asm'
/«PKGBUILDDIR»/lib/angelscript/source/as_callfunc_x64_gcc.cpp:162:82:
error: unknown register name '%rdi' in 'asm'
/«PKGBUILDDIR»/lib/angelscript/source/as_callfunc_x64_gcc.cpp:162:82:
error: unknown register name '%xmm7' in 'asm'
/«PKGBUILDDIR»/lib/angelscript/source/as_callfunc_x64_gcc.cpp:162:82:
error: unknown register name '%xmm6' in 'asm'
/«PKGBUILDDIR»/lib/angelscript/source/as_callfunc_x64_gcc.cpp:162:82:
error: unknown register name '%xmm5' in 'asm'
/«PKGBUILDDIR»/lib/angelscript/source/as_callfunc_x64_gcc.cpp:162:82:
error: unknown register name '%xmm4' in 'asm'
/«PKGBUILDDIR»/lib/angelscript/source/as_callfunc_x64_gcc.cpp:162:82:
error: unknown register name '%xmm3' in 'asm'
/«PKGBUILDDIR»/lib/angelscript/source/as_callfunc_x64_gcc.cpp:162:82:
error: unknown register name '%xmm2' in 'asm'
/«PKGBUILDDIR»/lib/angelscript/source/as_callfunc_x64_gcc.cpp:162:82:
error: unknown register name '%xmm1' in 'asm'
/«PKGBUILDDIR»/lib/angelscript/source/as_callfunc_x64_gcc.cpp:162:82:
error: unknown register name '%xmm0' in 'asm'


It looks like angelscript is misdetecting certain architectures as x86
and hence applying the wrong assembly directives. It's worth checking
first to see if there's a fix for this in upstream angelscript before
fixing it in supertuxkart. I'll take a look at this when I have time,
but help is greatly appreciated if someone has a chance to tackle this
before I do.

Regards,
Vincent

[1] https://buildd.debian.org/status/package.php?p=supertuxkart=unstable
--- End Message ---
--- Begin Message ---
Source: supertuxkart
Source-Version: 0.9.2+dfsg-2

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

Debian distribution maintenance software
pp.
Vincent Cheng  (supplier of updated supertuxkart package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive

Bug#846564: dpkg-deb: 'compressing tar member: lzma error: Cannot allocate memory' on 32-bit architectures on dpkg-deb -Zxz -Sextreme -z9

[Guillem Jover]

Hi!

On Fri, 2016-12-02 at 10:31:58 +0100, Guillem Jover wrote:
> Right, this was reported the other day on IRC by Mattia Rizzolo. The
> combination of -Sextreme -z9 and parallel xz makes this use more than
> the available address space. I'll change the code to limit based on
> memory available. Although as was mentioned on a thread on d-d, those
> settings are pretty unfriendly IMO, even more for memory constrained
> arches, but oh well. dpkg should never fail to operate on those
> conditions.

I've got the attached patch now, but I've been unable to test that
specific incarnation as I don't have 32-bit machine with many cores.
And neither are the i386 nor armhf porter boxes. I've just verified
that it does what it is intended by hardcoding the number of threads
to 32 and setting the physical memory limit to 2 GiB. And it reduced
the threads down to 12 when building one of those font packages.

If someone could test this on such 32-bit machine, that would be
appreciated.

Thanks,
Guillem
From 981fe7b1cc828e9d446bc07298264e421a970ac9 Mon Sep 17 00:00:00 2001
From: Guillem Jover 
Date: Sun, 4 Dec 2016 02:35:27 +0100
Subject: [PATCH] libdpkg: Decrease xz encoder threads to not exceed memory
 limits

---
 lib/dpkg/compress.c | 23 ++-
 1 file changed, 22 insertions(+), 1 deletion(-)

diff --git a/lib/dpkg/compress.c b/lib/dpkg/compress.c
index 2eda658fa..05e056b22 100644
--- a/lib/dpkg/compress.c
+++ b/lib/dpkg/compress.c
@@ -529,9 +529,9 @@ filter_xz_init(struct io_lzma *io, lzma_stream *s)
 	uint32_t preset;
 	lzma_check check = LZMA_CHECK_CRC64;
 #ifdef HAVE_LZMA_MT
+	uint64_t mt_memlimit;
 	lzma_mt mt_options = {
 		.flags = 0,
-		.threads = sysconf(_SC_NPROCESSORS_ONLN),
 		.block_size = 0,
 		.timeout = 0,
 		.filters = NULL,
@@ -548,6 +548,27 @@ filter_xz_init(struct io_lzma *io, lzma_stream *s)
 
 #ifdef HAVE_LZMA_MT
 	mt_options.preset = preset;
+
+	/* Set the multi-threaded memory limit to half the physical RAM,
+	 * or to 128 MiB if we cannot infer the number. */
+	mt_memlimit = lzma_physmem() / 2;
+	if (mt_memlimit == 0)
+		mt_memlimit = 128 * 1024 * 1024;
+
+	mt_options.threads = lzma_cputhreads();
+	if (mt_options.threads == 0)
+		mt_options.threads = 1;
+
+	/* Check that we have enough RAM to use the multi-threaded encoder,
+	 * and decrease them up to single-threaded to reduce memory usage. */
+	for (; mt_options.threads > 1; mt_options.threads--) {
+		uint64_t mt_memusage;
+
+		mt_memusage = lzma_stream_encoder_mt_memusage(_options);
+		if (mt_memusage < mt_memlimit)
+			break;
+	}
+
 	ret = lzma_stream_encoder_mt(s, _options);
 #else
 	ret = lzma_easy_encoder(s, preset, check);
-- 
2.11.0.rc1.160.g51e66c2

Bug#820381: rar crashes.

[Beedxe' Suugakujin]

Package: rar
Version: 2:5.3.b2-1
Followup-For: Bug #820381

Dear Maintainer,

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

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

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


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (970, 'testing'), (810, 'unstable'), (760, 'stable'), (710, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

When I installed rar and unrar packages together the compress operation or the 
decompress operation not work. So, if I have to unpack .rar files I have to 
unistall rar package. This occurs in graphical mode in files navigator or 
console. 

Bug#844701: dpkg: buggy dpkg 1.8.11 and above ? Package: dpkg

[Guillem Jover]

Hi!

On Mon, 2016-11-21 at 05:00:39 +0530, shirish शिरीष wrote:
> On 21/11/2016, Guillem Jover  wrote:
> > On Mon, 2016-11-21 at 01:47:45 +0530, shirish शिरीष wrote:
> >> The patch didn't work :(
> >
> > Well that it didn't work was actually also very useful! Because in
> > your case it should not have worked due to having debug output
> > enabled. If you retry it again w/o debugging enabled it should work,
> > and the attached patch should make it impervious to debug settings.

> >> So it seems some issue is still there. I'll reboot and see if the
> >> issue still persists.
> >
> > Yes and no. The original problem should be gone (the problem with the
> > exit code, the new problem with the non-empty output string due to the
> > debug output is new, but very welcome as it should make the code more
> > robust. Thanks for that. Attached new patch.

> Anyways, think it got through but for some reason dpkg died/failed it
> says , see -

I don't think this is related to this problem. The error report from
whoever is reporting that is not very helpful though. :/

In any case, I've now implemented an actual set of validators instead
of abusing the --compare-versions to do the validation. Which will
have defined exit codes and not output stuff on debugging modes.

At least I've added a --validate-pkgname and a --validate-version.
I'll try to do a release tomorrow or so.

Thanks,
Guillem

Processed: Re: Bug#844300: nvidia-driver-libs:amd64: upgrade failure due to dependency issue

[Debian Bug Tracking System]

Processing control commands:

> severity -1 wishlist
Bug #844300 [dpkg] aptitude can put the package system in a broken state with 
different versions of a MultiArch package
Severity set to 'wishlist' from 'serious'
> retitle -1 dpkg: Please remove packages seclected for deinstall on Multi-Arch 
> version skew
Bug #844300 [dpkg] aptitude can put the package system in a broken state with 
different versions of a MultiArch package
Changed Bug title to 'dpkg: Please remove packages seclected for deinstall on 
Multi-Arch version skew' from 'aptitude can put the package system in a broken 
state with different versions of a MultiArch package'.

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

Bug#844300: nvidia-driver-libs:amd64: upgrade failure due to dependency issue

[Guillem Jover]

Control: severity -1 wishlist
Control: retitle -1 dpkg: Please remove packages seclected for deinstall on 
Multi-Arch version skew

[ I'm actually a bit undecided whether this is normal or wishlist in dpkg
  itself, see below. ]

[ BTW David, do not forget to CC pkgname@packages.d.o either! :) ]

Hi!

On Tue, 2016-11-22 at 18:50:51 +0100, David Kalnischkies wrote:
>  On Tue, Nov 22, 2016 at 02:43:35PM +0100, Vincent Lefevre wrote:
> > --\ Packages to be upgraded (17)
> […]
> > iuA nvidia-driver-libs367.57-1 
> > 367.57-2
> […]
> > --\ Packages being removed because they are no longer used (27)
> […]
> > idA nvidia-driver-libs:i386 -180 kB   367.57-1 
> > 367.57-2
> […]
> > dpkg: error processing package nvidia-driver-libs:amd64 (--configure):
> >  package nvidia-driver-libs:amd64 367.57-2 cannot be configured because 
> > nvidia-driver-libs:i386 is at a different version (367.57-1)
> 
> This looks like a bug in dpkg as it is not considering the removal of
> nvidia-driver-libs:i386 as solution to the problem it runs into here
> even through libapt has told it via selections that it wants it removed.

Hmm, dpkg does not remove other packages at configure time, it only
ever does that at unpack time. Removing this kind of packages at
unpack time would seem gratuituous though, as it might or might not end
up seeing an updated packages, and version-skew (I like screw too BTW :)
is not a problem at unpack time anyway. Also remember that an unpack of
the selected to be deinstalled package would reset that selection.

So, this seems like a new kind of feature to me. Also the frontends
would need to handle the current dpkg anyway when doing upgrades, so
it seems this needs to be handled in frontends right now no matter
what?

Thanks,
Guillem

Processed: severity of 843073 is important

[Debian Bug Tracking System]

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

> severity 843073 important
Bug #843073 [dpkg-dev] dpkg-shlibdeps: broken on i386 with merged /usr
Bug #844430 [dpkg-dev] dpkg: dpkg-shlibdeps failing due to 
/usr/lib/ld-linux-armhf.so.3 symlink
Severity set to 'important' from 'serious'
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#828310: marked as done (gfarm: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Sun, 04 Dec 2016 03:05:51 +
with message-id 
and subject line Bug#828310: fixed in gfarm 2.6.15+dfsg-1
has caused the Debian Bug report #828310,
regarding gfarm: FTBFS with openssl 1.1.0
to be marked as done.

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

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


-- 
828310: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gfarm
Version: 2.6.10+dfsg-2
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/gfarm_2.6.10+dfsg-2_amd64-20160529-1419

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: gfarm
Source-Version: 2.6.15+dfsg-1

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

Debian distribution maintenance software
pp.
Dmitry Smirnov  (supplier of updated gfarm 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: Sun, 04 Dec 2016 13:08:17 +1100
Source: gfarm
Binary: gfarm-doc libgfarm1 libgfarm-dev gfmd gfsd gfarm-client
Architecture: source amd64 all
Version: 2.6.15+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Dmitry Smirnov 
Description:
 gfarm-client - Gfarm file system clients
 gfarm-doc  - Gfarm file system documentation
 gfmd   - Gfarm file system metadata server
 gfsd   - Gfarm file system daemon
 libgfarm-dev - Gfarm file system development files
 libgfarm1  - Gfarm file system runtime library
Closes: 828310 845006
Changes:
 gfarm (2.6.15+dfsg-1) unstable; urgency=medium
 .
   * New upstream release [December 2016].
 + fixed FTBFS with openssl 1.1.0 (Closes: #828310).
   * Install "config-gfarm.common" (Closes: #845006).
Checksums-Sha1:
 5599073336f9368ea09303796c0fe6110019b0c1 2263 gfarm_2.6.15+dfsg-1.dsc
 b7bcf0ec9bd4fc664581fb1822af294a57e39d94 2838392 gfarm_2.6.15+dfsg.orig.tar.xz
 d347fb750a3a317331a47dc9371e143ad3d21b18 19856 
gfarm_2.6.15+dfsg-1.debian.tar.xz
 0694f2f7e5c39ac401462337b944e292aad46a2e 406786 
gfarm-client-dbgsym_2.6.15+dfsg-1_amd64.deb
 fd1a0270c9f2b56103a50f2130fc3f144efb52ce 223258 
gfarm-client_2.6.15+dfsg-1_amd64.deb
 c91b68590aa904e92a49fb7ef420637bbae8134f 159962 gfarm-doc_2.6.15+dfsg-1_all.deb
 3c3e91715f3460e4d90387c7e3d9c6698dad586c 11863 
gfarm_2.6.15+dfsg-1_amd64.buildinfo
 ade5cd4db3ac54d1c07dd9c56f65da407f1a6e3e 683326 
gfmd-dbgsym_2.6.15+dfsg-1_amd64.deb
 3d596b6a37f64c2c51b233770cc6d1a54b8ace64 363068 gfmd_2.6.15+dfsg-1_amd64.deb
 f1113684377a568a733616ba48d7d1599953546c 136450 
gfsd-dbgsym_2.6.15+dfsg-1_amd64.deb
 5f5ef3fe78f000a344e1868f31e622fb0cc1ab2b 108010 gfsd_2.6.15+dfsg-1_amd64.deb
 91789d568ee92d4b887d3a07dd4030c6c4a0ebe0 99568 
libgfarm-dev_2.6.15+dfsg-1_amd64.deb
 74ed7a25bd40e93c75245874643c4110dd7309ed 543498 
libgfarm1-dbgsym_2.6.15+dfsg-1_amd64.deb
 e4a940614a308a528d5f9cc47630958a194e6e5b 236984 
libgfarm1_2.6.15+dfsg-1_amd64.deb
Checksums-Sha256:
 77ce712e8d9917f80ea3b22a14e4f088de18a3fdd523ed36376e1e3f84ff97ba 2263 
gfarm_2.6.15+dfsg-1.dsc
 1fd157e2f01fa073c7d99cc554b6f5a1fc3ade742fce7c028db0761c086ffd1a 2838392 
gfarm_2.6.15+dfsg.orig.tar.xz
 43bee2c8edbd6c2cc415cf35b9f210f681ad1e7a5595213a5e5038fc8b62ea38 19856 
gfarm_2.6.15+dfsg-1.debian.tar.xz
 bf52489d4c37cf2ef58870d24559f76c66fc00d5589508e01e85c0f64eeed151 406786 
gfarm-client-dbgsym_2.6.15+dfsg-1_amd64.deb
 

Processed: your mail

[Debian Bug Tracking System]

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

> reassign 846760 gsl 2.2.1+dfsg-1
Bug #846760 [src:ruby-gsl] ruby-gsl: FTBFS: ERROR: Test "ruby2.3" failed: 
/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': 
/<>/ruby-gsl-1.16.0.6+dfsg1/debian/ruby-gsl/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.3.0/gsl_native.so:
 undefined symbol: gsl_sf_legendre_array_size - 
/<>/ruby-gsl-1.16.0.6+dfsg1/debian/ruby-gsl/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.3.0/gsl_native.so
 (LoadError)
Bug reassigned from package 'src:ruby-gsl' to 'gsl'.
No longer marked as found in versions ruby-gsl/1.16.0.6+dfsg1-2.
Ignoring request to alter fixed versions of bug #846760 to the same values 
previously set
Bug #846760 [gsl] ruby-gsl: FTBFS: ERROR: Test "ruby2.3" failed: 
/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': 
/<>/ruby-gsl-1.16.0.6+dfsg1/debian/ruby-gsl/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.3.0/gsl_native.so:
 undefined symbol: gsl_sf_legendre_array_size - 
/<>/ruby-gsl-1.16.0.6+dfsg1/debian/ruby-gsl/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.3.0/gsl_native.so
 (LoadError)
There is no source info for the package 'gsl' at version '2.2.1+dfsg-1' with 
architecture ''
Unable to make a source version for version '2.2.1+dfsg-1'
Marked as found in versions 2.2.1+dfsg-1.
> forcemerge 841611 846760
Bug #841611 [gsl] ruby-gsl: FTBFS: ERROR: Test "ruby2.3" failed: 
/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': 
/<>/ruby-gsl-1.16.0.6+dfsg1/debian/ruby-gsl/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.3.0/gsl_native.so:
 undefined symbol: gsl_sf_legendre_array_size - 
/<>/ruby-gsl-1.16.0.6+dfsg1/debian/ruby-gsl/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.3.0/gsl_native.so
 (LoadError)
Bug #846760 [gsl] ruby-gsl: FTBFS: ERROR: Test "ruby2.3" failed: 
/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': 
/<>/ruby-gsl-1.16.0.6+dfsg1/debian/ruby-gsl/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.3.0/gsl_native.so:
 undefined symbol: gsl_sf_legendre_array_size - 
/<>/ruby-gsl-1.16.0.6+dfsg1/debian/ruby-gsl/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.3.0/gsl_native.so
 (LoadError)
Added indication that 846760 affects src:ruby-gsl
Merged 841611 846760
> thanks
Stopping processing here.

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

Processed: .

[Debian Bug Tracking System]

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

> affects 841611 + src:ruby-gsl
Bug #841611 [gsl] ruby-gsl: FTBFS: ERROR: Test "ruby2.3" failed: 
/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': 
/<>/ruby-gsl-1.16.0.6+dfsg1/debian/ruby-gsl/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.3.0/gsl_native.so:
 undefined symbol: gsl_sf_legendre_array_size - 
/<>/ruby-gsl-1.16.0.6+dfsg1/debian/ruby-gsl/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.3.0/gsl_native.so
 (LoadError)
Added indication that 841611 affects src:ruby-gsl
> thanks
Stopping processing here.

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

Processed: File is included from modp_b64.h

[Debian Bug Tracking System]

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

> reassign 846750 libmodpbase64-dev stringencoders/3.10.3+git20160924-2
Bug #846750 [src:aseprite] aseprite: FTBFS: modp_b64.h:33:28: fatal error: 
extern_c_begin.h: No such file or directory
Bug reassigned from package 'src:aseprite' to 'libmodpbase64-dev'.
No longer marked as found in versions aseprite/1.1.6+ds-1.
Ignoring request to alter fixed versions of bug #846750 to the same values 
previously set
Bug #846750 [libmodpbase64-dev] aseprite: FTBFS: modp_b64.h:33:28: fatal error: 
extern_c_begin.h: No such file or directory
Marked as found in versions stringencoders/3.10.3+git20160924-2.
> thanks
Stopping processing here.

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

Processed: .

[Debian Bug Tracking System]

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

> affects 841611 - ruby-gsl + src:ruby-gsl
Bug #841611 [gsl] ruby-gsl: FTBFS: ERROR: Test "ruby2.3" failed: 
/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': 
/<>/ruby-gsl-1.16.0.6+dfsg1/debian/ruby-gsl/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.3.0/gsl_native.so:
 undefined symbol: gsl_sf_legendre_array_size - 
/<>/ruby-gsl-1.16.0.6+dfsg1/debian/ruby-gsl/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.3.0/gsl_native.so
 (LoadError)
Removed indication that 841611 affects ruby-gsl
> thanks
Stopping processing here.

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

Bug#775744: libapp-stacktrace-perl: FTBFS: Failed 1/4 test programs. 1/6 subtests failed.

[Axel Beckert]

Hi Chris,

Chris Lamb wrote:
> libapp-stacktrace-perl fails to build from source in unstable/amd64 too:

Yes, but that might be a different bug, as I suspect your experinced
issue (which I can confirm, too, btw.) happens on _all_ architectures.

>From the initial bug report:
> > # Cannot access memory at address 0x200147b0

>From your log:
>   # Cannot access memory at address 0x8ad29718

Just having read
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814929#10, it sounds
as if Niko's observation about longer addresses could also have
triggered the FTBFS you ran into, too, although it's likely
different code involved. (If so, I'd clone this bug to track the
recent FTBFS on probably all architectures separately and downgrade
the old one to important again.)

Niko: What do you think?

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#793134: Packaging of newest upstream version in progress

[Felix Lechner]

Uploaded and pending in NEW.


On Fri, Dec 2, 2016 at 12:11 AM, Nobuhiro Iwamatsu 
wrote:

> Hi,
>
> > Newest version will be uploaded soon. Upstream is reviewing configured
> > ciphers and options.
>
> ping?
>
> --
> Nobuhiro Iwamatsu
>iwamatsu at {nigauri.org / debian.org}
>GPG ID: 40AD1FA6
>

Bug#845301: marked as done (hdf5: CVE-2016-4330 CVE-2016-4331 CVE-2016-4332 CVE-2016-4333)

[Debian Bug Tracking System]

Your message dated Sat, 03 Dec 2016 22:48:39 +
with message-id 
and subject line Bug#845301: fixed in hdf5 1.8.13+docs-15+deb8u1
has caused the Debian Bug report #845301,
regarding hdf5: CVE-2016-4330 CVE-2016-4331 CVE-2016-4332 CVE-2016-4333
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.)


-- 
845301: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845301
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hdf5
Version: 1.8.16+docs-8
Severity: grave
Tags: security upstream
Justification: user security hole

Hi,

the following vulnerabilities were published for hdf5.

CVE-2016-4330[0]:
| In the HDF5 1.8.16 library's failure to check if the number of
| dimensions for an array read from the file is within the bounds of the
| space allocated for it, a heap-based buffer overflow will occur,
| potentially leading to arbitrary code execution.

CVE-2016-4331[1]:
| When decoding data out of a dataset encoded with the H5Z_NBIT
| decoding, the HDF5 1.8.16 library will fail to ensure that the
| precision is within the bounds of the size leading to arbitrary code
| execution.

CVE-2016-4332[2]:
| The library's failure to check if certain message types support a
| particular flag, the HDF5 1.8.16 library will cast the structure to an
| alternative structure and then assign to fields that aren't supported
| by the message type and the library will write outside the bounds of
| the heap buffer. This can lead to code execution under the context of
| the library.

CVE-2016-4333[3]:
| The HDF5 1.8.16 library allocating space for the array using a value
| from the file has an impact within the loop for initializing said
| array allowing a value within the file to modify the loop's
| terminator. Due to this, an aggressor can cause the loop's index to
| point outside the bounds of the array when initializing it.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-4330
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4330
[1] https://security-tracker.debian.org/tracker/CVE-2016-4331
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4331
[2] https://security-tracker.debian.org/tracker/CVE-2016-4332
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4332
[3] https://security-tracker.debian.org/tracker/CVE-2016-4333
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4333

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: hdf5
Source-Version: 1.8.13+docs-15+deb8u1

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

Debian distribution maintenance software
pp.
Gilles Filippini  (supplier of updated hdf5 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 25 Nov 2016 00:59:06 +0100
Source: hdf5
Binary: libhdf5-8 libhdf5-8-dbg libhdf5-cpp-8 libhdf5-cpp-8-dbg libhdf5-dev 
libhdf5-openmpi-8 libhdf5-openmpi-dev libhdf5-openmpi-8-dbg libhdf5-mpich-8 
libhdf5-mpich-dev libhdf5-mpich2-dev libhdf5-mpich-8-dbg libhdf5-mpi-dev 
libhdf5-doc hdf5-helpers hdf5-tools libhdf5-serial-dev
Architecture: source all amd64
Version: 1.8.13+docs-15+deb8u1
Distribution: jessie-security
Urgency: high
Maintainer: Debian GIS Project 
Changed-By: Gilles Filippini 
Description:
 hdf5-helpers - Hierarchical Data Format 5 (HDF5) - Helper tools
 hdf5-tools - Hierarchical Data Format 5 (HDF5) - Runtime tools
 libhdf5-8  - Hierarchical Data Format 5 (HDF5) - runtime files - serial versio
 libhdf5-8-dbg - Hierarchical Data Format 5 (HDF5) - Debug package
 libhdf5-cpp-8 - Hierarchical Data Format 5 (HDF5) - C++ libraries
 libhdf5-cpp-8-dbg - Hierarchical Data Format 5 (HDF5) - C++ Debug package
 libhdf5-dev - Hierarchical Data Format 5 (HDF5) - development files - serial 

Processed: Re: Bug#840610: UnicodeEncodeError: 'ascii' codec can't encode character

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #840610 [python3.5] python inconsistently handles the LANGUAGE env var
Severity set to 'important' from 'serious'

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

Bug#840610: UnicodeEncodeError: 'ascii' codec can't encode character

[Matthias Klose]

Control: severity -1 important

On 16.10.2016 00:34, Kalle Olavi Niemitalo wrote:
> Robert Luberda  writes:
> 
>> According to GNU gettext documentation[1]: "The variable LANGUAGE is
>> ignored if the locale is set to ‘C’."
> 
> That exception was added on 2001-01-03, for glibc 2.2.1.
> In glibc 2.2, LANGUAGE used to override LC_ALL=C.
> 
> In Python 2.0 (released on 2000-10-16), 2.7, and 3.5.0, gettext.py
> checks LANGUAGE first, like glibc 2.2.  The loop that checks the
> environment variables is exactly the same in these three versions.
> 
> I searched for "gettext" at bugs.python.org but it didn't find a
> bug report for the priority of LANGUAGE vs. LC_ALL=C in gettext.
> http://bugs.python.org/issue1166948 says 'LANGUAGE is honoured
> even if the default locale is "C"' but I think that refers to
> locale.getdefaultencoding, not to gettext.

I looked at recent behavior changes for that in the updates after the 3.5.2
release, but couldn't find one.   It would be good to have a self-contained
example to show the exact issue.

Bug#846648: chromium: Chromium still "Aw, Snaps" on many websites

[Benjamin FRANCOIS]

Package: chromium
Version: 55.0.2883.75-1
Followup-For: Bug #846648

I confirm, it's now worse than ever. Scrolling all the way down of this article 
randomly leads to the "Aw, snap" error for no apparent reason.

http://www.lemonde.fr/pixels/article/2016/06/23/super-mario-64-etait-d-une-philosophie-toute-differente-immense-audacieux-un-peu-fou_4956739_4408996.html

And it's crashing all tabs at once :(



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

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

Versions of packages chromium depends on:
ii  libasound2   1.1.2-1
ii  libatk1.0-0  2.22.0-1
ii  libavcodec57 7:3.2.1-1
ii  libavformat577:3.2.1-1
ii  libavutil55  7:3.2.1-1
ii  libc62.24-7
ii  libcairo21.14.6-1.1
ii  libcups2 2.2.1-2
ii  libdbus-1-3  1.10.14-1
ii  libevent-2.0-5   2.0.21-stable-2.1
ii  libexpat12.2.0-1
ii  libflac8 1.3.1-4
ii  libfontconfig1   2.11.0-6.7
ii  libfreetype6 2.6.3-3+b1
ii  libgcc1  1:6.2.1-5
ii  libgdk-pixbuf2.0-0   2.36.0-1
ii  libglib2.0-0 2.50.2-2
ii  libgtk2.0-0  2.24.31-1
ii  libharfbuzz0b1.2.7-1+b1
ii  libicu57 57.1-5
ii  libjpeg62-turbo  1:1.5.1-2
ii  libminizip1  1.1-8
ii  libnettle6   3.3-1
ii  libnspr4 2:4.12-6
ii  libnss3  2:3.26.2-1
ii  libpango-1.0-0   1.40.3-3
ii  libpangocairo-1.0-0  1.40.3-3
ii  libpng16-16  1.6.26-2
ii  libpulse09.0-5
ii  libre2-3 20161101+dfsg-2
ii  libsnappy1v5 1.1.3-3
ii  libstdc++6   6.2.1-5
ii  libvpx4  1.6.0-3
ii  libwebp6 0.5.1-3
ii  libwebpdemux20.5.1-3
ii  libx11-6 2:1.6.3-1
ii  libx11-xcb1  2:1.6.3-1
ii  libxcb1  1.12-1
ii  libxcomposite1   1:0.4.4-1
ii  libxcursor1  1:1.1.14-1+b1
ii  libxdamage1  1:1.1.4-2+b1
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.2-1
ii  libxi6   2:1.7.6-1.1
ii  libxml2  2.9.4+dfsg1-2.1
ii  libxrandr2   2:1.5.0-1
ii  libxrender1  1:0.9.9-2
ii  libxslt1.1   1.1.29-2
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.2-1+b1
ii  x11-utils7.7+3
ii  xdg-utils1.1.1-1
ii  zlib1g   1:1.2.8.dfsg-2+b3

Versions of packages chromium recommends:
ii  fonts-liberation  1:1.07.4-2

Versions of packages chromium suggests:
ii  chromium-l10n  55.0.2883.75-1

-- no debconf information

Bug#846683: marked as done (libspring-java: FTBFS: TomcatInstrumentableClassLoader.java:115: error: cannot find symbol)

[Debian Bug Tracking System]

Your message dated Sat, 03 Dec 2016 22:21:06 +
with message-id 
and subject line Bug#846683: fixed in libspring-java 4.3.4-3
has caused the Debian Bug report #846683,
regarding libspring-java: FTBFS: TomcatInstrumentableClassLoader.java:115: 
error: cannot find symbol
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.)


-- 
846683: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846683
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libspring-java
Version: 4.3.4-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161202 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build -- jar -x test -x check \
>  -x :spring-orm-hibernate4:compileJava \
>  -x :spring-orm-hibernate5:compileJava \
>  -x :spring-webmvc-tiles2:compileJava \
>  -x :spring-websocket:compileJava
>   mkdir -p .gradle/init.d
>   cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/
>   gradle --info --console plain --offline --stacktrace --no-daemon 
> --refresh-dependencies --gradle-user-home .gradle -Duser.home=. 
> -Duser.name=debian --parallel --max-workers=64 jar -x test -x check -x 
> :spring-orm-hibernate4:compileJava -x :spring-orm-hibernate5:compileJava -x 
> :spring-webmvc-tiles2:compileJava -x :spring-websocket:compileJava
> Initialized native services in: /<>/.gradle/native
> Starting Build
> Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
> using SubsetScriptTransformer.
> Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
> using BuildScriptTransformer.
>   Loading the Maven rules...
> Invalidating buildSrc state cache 
> (/<>/buildSrc/.gradle/noVersion/buildSrc) as it was not closed 
> cleanly.
>   Loading the Maven rules...
> Compiling script 
> 'jar:file:/usr/share/gradle/lib/gradle-core-3.1.jar!/org/gradle/initialization/buildsrc/defaultBuildSourceScript.txt'
>  using SubsetScriptTransformer.
> Compiling script 
> 'jar:file:/usr/share/gradle/lib/gradle-core-3.1.jar!/org/gradle/initialization/buildsrc/defaultBuildSourceScript.txt'
>  using BuildScriptTransformer.
> Generating gradleApi JAR file: 
> /<>/.gradle/caches/3.1/generated-gradle-jars/gradle-api-3.1.jar
> Generating JAR file 'gradle-api-3.1.jar'
>   Keep-alive timer started
>   Adding Debian repository to project 'buildSrc'
> Parallel execution is an incubating feature.
> Evaluating root project 'buildSrc' using build file 
> '/<>/buildSrc/build.gradle'.
>   Adding task debianMavenPom to project 'buildSrc'
>   Configuring javadoc links
> Selected primary task 'clean' from project :
> Selected primary task 'build' from project :
> Using 64 parallel executor threads
> :clean (Thread[Task worker,5,main]) started.
> :buildSrc:clean
> Executing task ':clean' (up-to-date check took 0.0 secs) due to:
>   Task has not declared any outputs.
> :buildSrc:clean UP-TO-DATE
> :clean (Thread[Task worker,5,main]) completed. Took 0.041 secs.
> :compileJava (Thread[Task worker Thread 53,5,main]) started.
> :buildSrc:compileJava
> file or directory '/<>/buildSrc/src/main/java', not found
> Skipping task ':compileJava' as it has no source files.
> :buildSrc:compileJava UP-TO-DATE
> :compileJava (Thread[Task worker Thread 53,5,main]) completed. Took 0.018 
> secs.
> :compileGroovy (Thread[Task worker Thread 52,5,main]) started.
> :buildSrc:compileGroovy
> Executing task ':compileGroovy' (up-to-date check took 0.448 secs) due to:
>   No history is available.
> Starting process 'Gradle Compiler Daemon 1'. Working directory: 
> /<>/buildSrc Command: /usr/lib/jvm/java-8-openjdk-amd64/bin/java 
> -Djava.security.manager=worker.org.gradle.process.internal.worker.child.BootstrapSecurityManager
>  -Dfile.encoding=US-ASCII -Duser.country=US -Duser.language=en -Duser.variant 
> -cp /<>/.gradle/caches/3.1/workerMain/gradle-worker.jar 
> worker.org.gradle.process.internal.worker.GradleWorkerMain 'Gradle Compiler 
> Daemon 1'
> Successfully started process 'Gradle Compiler Daemon 1'
> Started Gradle compiler daemon (0.452 secs) with fork options 
> DaemonForkOptions{minHeapSize=null, maxHeapSize=null, jvmArgs=[], 
> classpath=[/usr/share/java/groovy-all-2.4.7.jar, 
> /usr/share/java/ant-1.9.7.jar, /usr/share/java/ant-launcher-1.9.7.jar]}.
> Initialized native services in: /<>/.gradle/native
> Executing 

Processed: Re: gridengine: FTBFS: cc: error: libsched.a: No such file or directory

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + moreinfo unreproducible
Bug #846770 [src:gridengine] gridengine: FTBFS: cc: error: libsched.a: No such 
file or directory
Added tag(s) unreproducible and moreinfo.

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

Bug#846770: gridengine: FTBFS: cc: error: libsched.a: No such file or directory

[Afif Elghraoui]

Control: tag -1 + moreinfo unreproducible

Hello,

على السبت  3 كانون الأول 2016 ‫00:46، كتب Lucas Nussbaum:
> Source: gridengine
> Version: 8.1.9+dfsg-3
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20161202 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):
>> cc -o qmod -L. -Wl,-z,relro -rdynamic -Wl,-rpath,\$ORIGIN/../../lib/lx-amd64 
>>  qmod.o sig_handlers.o usage.o sge_options.o -lgdi -lsgeobj -lsgeobjd -lcull 
>> -lcomm -lcommlists -luti  -lmunge -lssl -lcrypto  -luti -ldl  -lm -lpthread 
>> -ljemalloc -lmunge
>> cc: error: libsched.a: No such file or directory
>> cc -o qevent -L. -Wl,-z,relro -rdynamic 
>> -Wl,-rpath,\$ORIGIN/../../lib/lx-amd64  qevent.o  usage.o sig_handlers.o 
>> sge_options.o sge_mt_init.o -lmir -levc -lgdi -lsgeobj -lsgeobjd -lcull 
>> -lcomm -lcommlists -luti  -lmunge -lssl -lcrypto  -luti -ldl  -lm -lpthread 
>> -ljemalloc -lmunge
>> ../daemons/common/Makefile:94: recipe for target 'pdc' failed
>> make[2]: *** [pdc] Error 1
> 
> The full build log is available from:
>http://aws-logs.debian.net/2016/12/02/gridengine_8.1.9+dfsg-3_unstable.log
> 
> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
> 
> About the archive rebuild: The rebuild was done on EC2 VM instances from
> Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> failed build was retried once to eliminate random failures.
> 
I have just tried a parallel build on an up-to-date unstable chroot on
amd64 and it builds just fine for me. Can you confirm?

Many thanks and regards
Afif

-- 
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name

Processed: Pending fixes for bugs in the libspring-java package

[Debian Bug Tracking System]

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

> tag 846683 + pending
Bug #846683 [src:libspring-java] libspring-java: FTBFS: 
TomcatInstrumentableClassLoader.java:115: error: cannot find symbol
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#844858: marked as done (oggvideotools: FTBFS: decoderTest.cpp:19:41: error: 'memset' was not declared in this scope)

[Debian Bug Tracking System]

Your message dated Sat, 03 Dec 2016 22:04:01 +
with message-id 
and subject line Bug#844858: fixed in oggvideotools 0.9.1-3
has caused the Debian Bug report #844858,
regarding oggvideotools: FTBFS: decoderTest.cpp:19:41: error: 'memset' was not 
declared in this scope
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.)


-- 
844858: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844858
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: oggvideotools
Version: 0.9.1-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> cd /<>/obj-x86_64-linux-gnu/src/base/test && /usr/bin/c++   
> -DHAVE_CONFIG_H -DPACKAGE_STRING=\"oggvideotools-0.9.1\" -DWITH_GD2LIB 
> -D_FILE_OFFSET_BITS=64 -I/<>/obj-x86_64-linux-gnu 
> -I/<>/src -I/<>/src/base 
> -I/<>/src/effect -I/<>/src/misc 
> -I/<>/src/ovt_kate -I/<>/src/ovt_vorbis 
> -I/<>/src/ovt_theora -I/<>/src/main 
> -I/<>/src/libresample  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -Wno-write-strings 
> -O0 -g --std=c++0x -fPIC -Wall -Wextra -o 
> CMakeFiles/decoderTest.dir/decoderTest.cpp.o -c 
> /<>/src/base/test/decoderTest.cpp
> /<>/src/base/test/decoderTest.cpp: In function 'int main(int, 
> char**)':
> /<>/src/base/test/decoderTest.cpp:19:41: error: 'memset' was not 
> declared in this scope
>  memset(, 0, sizeof(OggHeader));
>  ^
> /<>/src/base/test/decoderTest.cpp:9:14: warning: unused 
> parameter 'argc' [-Wunused-parameter]
>  int main(int argc, char* argv[])
>   ^~~~
> /<>/src/base/test/decoderTest.cpp:9:31: warning: unused 
> parameter 'argv' [-Wunused-parameter]
>  int main(int argc, char* argv[])
>^
> src/base/test/CMakeFiles/decoderTest.dir/build.make:65: recipe for target 
> 'src/base/test/CMakeFiles/decoderTest.dir/decoderTest.cpp.o' failed
> make[3]: *** [src/base/test/CMakeFiles/decoderTest.dir/decoderTest.cpp.o] 
> Error 1

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/oggvideotools_0.9.1-2_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: oggvideotools
Source-Version: 0.9.1-3

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

Debian distribution maintenance software
pp.
Petter Reinholdtsen  (supplier of updated oggvideotools 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 03 Dec 2016 21:40:18 +
Source: oggvideotools
Binary: oggvideotools oggvideotools-dbg
Architecture: source
Version: 0.9.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Xiph.org Maintainers 
Changed-By: Petter Reinholdtsen 
Description:
 oggvideotools - toolbox for manipulating and creating Ogg video files
 oggvideotools-dbg - toolbox for manipulating and creating Ogg video files 
(debug symb
Closes: 844858
Changes:
 oggvideotools (0.9.1-3) unstable; urgency=medium
 .
   * Updated d/copyright file to relect that win32/ no longer is part
 of the source tarball.
   * New patch import-cstring.patch to fix build problem after compiler
 updates.  Patch from Jan Gerber.  Closes: #844858
Checksums-Sha1:
 a29e54852e112ba03a0961baf03e663d95108ce5 2346 oggvideotools_0.9.1-3.dsc
 2fc4f4868844528fad0699d342b89e868ef6e8b7 8228 
oggvideotools_0.9.1-3.debian.tar.xz
Checksums-Sha256:
 

Bug#846683: Pending fixes for bugs in the libspring-java package

[pkg-java-maintainers]

tag 846683 + pending
thanks

Some bugs in the libspring-java package are closed in revision
adae00218715da9fd12381967929e55931606764 in branch 'master' by
Emmanuel Bourg

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

Commit message:

No longer build spring-instrument-tomcat (obsolete) (Closes: #846683)

Bug#846540: hplip-gui: hp-toolbox and hp-setup cannot load

[Michael Weghorn]

Hi Alejandro,

I just installed "hplip-gui" on unstable/sid in a VM and running
hp-setup or hp-check did work for me. (I did not check the
functionality, just that the problem you described did not occur.)

Do you have the package "libhpmud0" installed?
It contains the respective shared library file "libhpipp.so.0" that is
mentioned in the error message you get:

~~~
$ dpkg -S /usr/lib/x86_64-linux-gnu/libhpipp.so.0
libhpmud0:amd64: /usr/lib/x86_64-linux-gnu/libhpipp.so.0
~~~

As far as I understand, the package should automatically be installed as
it is declared as a dependency of package "hplip" (which is itself a
dependency of "hplip-gui").

If I explicitly ignore that dependency and force the removal of the
package "libhpmud0", I can reproduce the error messages you wrote about:

~~~
$ sudo dpkg --purge libhpmud0
dpkg: dependency problems prevent removal of libhpmud0:amd64:
 libsane-hpaio:amd64 depends on libhpmud0.
 printer-driver-hpcups depends on libhpmud0.
 hplip depends on libhpmud0 (= 3.16.10+repack0-1).

dpkg: error processing package libhpmud0:amd64 (--purge):
 dependency problems - not removing
Errors were encountered while processing:
 libhpmud0:amd64
$ sudo dpkg --purge --force-all libhpmud0
dpkg: libhpmud0:amd64: dependency problems, but removing anyway as you
requested:
 libsane-hpaio:amd64 depends on libhpmud0.
 printer-driver-hpcups depends on libhpmud0.
 hplip depends on libhpmud0 (= 3.16.10+repack0-1).

(Reading database ... 75747 files and directories currently installed.)
Removing libhpmud0:amd64 (3.16.10+repack0-1) ...
Processing triggers for libc-bin (2.24-7) ...
$ hp-setup
Traceback (most recent call last):
  File "/usr/bin/hp-setup", line 48, in 
from base import device, utils, tui, models, module, services, os_utils
  File "/usr/share/hplip/base/device.py", line 41, in 
from . import status
  File "/usr/share/hplip/base/status.py", line 32, in 
import cupsext
ImportError: libhpipp.so.0: cannot open shared object file: No such file
or directory
~~~

As far as I understand it so far, "libhpmud0" should always be present
in normal cases because of the declared dependencies.

Michael

Bug#828459: marked as done (nsca-ng: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Sat, 03 Dec 2016 21:20:29 +
with message-id 
and subject line Bug#828459: fixed in nsca-ng 1.5-1
has caused the Debian Bug report #828459,
regarding nsca-ng: FTBFS with openssl 1.1.0
to be marked as done.

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

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


-- 
828459: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nsca-ng
Version: 1.4-2
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/nsca-ng_1.4-2_amd64-20160529-1457

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: nsca-ng
Source-Version: 1.5-1

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

Debian distribution maintenance software
pp.
Alexander Wirt  (supplier of updated nsca-ng package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 03 Dec 2016 21:57:17 +0100
Source: nsca-ng
Binary: nsca-ng-client nsca-ng-server
Architecture: source amd64
Version: 1.5-1
Distribution: unstable
Urgency: medium
Maintainer: Alexander Wirt 
Changed-By: Alexander Wirt 
Description:
 nsca-ng-client - Send monitoring commands to NSCA-ng server
 nsca-ng-server - Monitoring command acceptor
Closes: 768003 828459 846000 846867
Changes:
 nsca-ng (1.5-1) unstable; urgency=medium
 .
   * [a040168] Use Icinga instead of Nagios (nagios3 removed from Debian).
 Thanks to Bas Couwenberg for the patch (Closes: #846867)
   * [1c8] New upstream version 1.5 (Closes: #846000)
 - Fix ftbfs with OpenSSL 1.1.0 (Closes: #828459)
   * Depend on icinga-core instead of icinga (Closes: #768003)
Checksums-Sha1:
 f481a2c5401fc92f1f05b623f44a6da1aae60b40 1849 nsca-ng_1.5-1.dsc
 533285b404c4a96baae38cb26d6729fb7b24fb9c 434494 nsca-ng_1.5.orig.tar.gz
 fd745e381bd370a7d41be9bce8448b85de6b934a 5812 nsca-ng_1.5-1.debian.tar.xz
 d453a566ad310e10dd052dc37135d40ae4d0adcb 50758 
nsca-ng-client-dbgsym_1.5-1_amd64.deb
 e090229a00bcc9ebefbc5748958a48e3f1989992 49782 nsca-ng-client_1.5-1_amd64.deb
 a254989adb75157ff1d958cf3117ddc6d5eb567e 65988 
nsca-ng-server-dbgsym_1.5-1_amd64.deb
 300a2a6df79c3ff12392a814cb88b645898980c9 51580 nsca-ng-server_1.5-1_amd64.deb
 280cfdba2dcf5c51166d4a942474b97881325258 5588 nsca-ng_1.5-1_amd64.buildinfo
Checksums-Sha256:
 389d81bf73a012c3f035f5a329b9789d0104c15e765a87eb25ec773b67039a6e 1849 
nsca-ng_1.5-1.dsc
 79d4f725ef36756057306a4793268e0da9ccd1721a257ec99cf958d55a83261f 434494 
nsca-ng_1.5.orig.tar.gz
 a8278fecaa641b5255d0244c2ddade6ce5dd1a400ff346fd765770f92601adef 5812 
nsca-ng_1.5-1.debian.tar.xz
 fa39273397fce252f4dd3ec3d9603a2c5a649eceb990cd0cafc614d2afdf4b99 50758 
nsca-ng-client-dbgsym_1.5-1_amd64.deb
 fcb32855fa80e731606612409934c90f9f6106946fe8a8614edfeb044863e958 49782 
nsca-ng-client_1.5-1_amd64.deb
 099081c680558fd42dfec984f2cce7d09b7371a1ab54422aed4c767db4b00ca1 65988 
nsca-ng-server-dbgsym_1.5-1_amd64.deb
 2bc34e44a0088be26a55521c8f7d3d63df059a8607559c44a448e04a36cc0166 51580 
nsca-ng-server_1.5-1_amd64.deb
 a6b8f72c823191bbe34905a0dc63f1327caa88e3dd54573cf904e7c98122e830 5588 
nsca-ng_1.5-1_amd64.buildinfo
Files:
 ef1b4c871e0f0ef414fa3283d4761750 1849 net extra nsca-ng_1.5-1.dsc
 0a8fe1c635dd053430c7301c1721eecb 434494 net extra nsca-ng_1.5.orig.tar.gz
 f6d9a9471571dcfd50aefc6fd2296f8c 5812 net extra nsca-ng_1.5-1.debian.tar.xz
 

Bug#846877: plasma-desktop: Sddm can not start kde. Then panel is not working.

[laurent B]

Package: plasma-desktop
Version: 4:5.8.4-1
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

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

   * What led up to the situation?
   upgrade some packages on debian sid (this week from 28 november to 2th 
december 2016)
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 try to login in plasma-kde from sddm
   * What was the outcome of this action?
   the blackcreen with K icon  showed off but hand out indefinitely. However I 
found a simple workaourd : go to tty1 then back to tty7 and get greeted with 
the sound of plasma login. However then at some point  the panel will stop work 
and i could only manage to switch from one windows to another going in the to 
left side of the screen.  
   



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

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

Versions of packages plasma-desktop depends on:
ii  breeze   4:5.8.4-1
ii  kactivitymanagerd5.8.4-1
ii  kde-cli-tools4:5.8.4-1
ii  kded55.28.0-1
ii  kio  5.28.0-1
ii  libc62.24-7
ii  libcanberra0 0.30-3
ii  libfontconfig1   2.11.0-6.7
ii  libgcc1  1:6.2.1-5
ii  libkf5activities55.28.0-1
ii  libkf5activitiesstats1   5.28.0-1
ii  libkf5archive5   5.28.0-1
ii  libkf5auth5  5.28.0-1
ii  libkf5baloo5 5.28.0-1
ii  libkf5bookmarks5 5.28.0-1
ii  libkf5codecs55.28.0-1
ii  libkf5completion55.28.0-1
ii  libkf5configcore55.28.0-1
ii  libkf5configgui5 5.28.0-1
ii  libkf5configwidgets5 5.28.0-1
ii  libkf5coreaddons55.28.0-1
ii  libkf5dbusaddons55.28.0-1
ii  libkf5emoticons-bin  5.28.0-1
ii  libkf5emoticons5 5.28.0-1
ii  libkf5globalaccel5   5.28.0-1
ii  libkf5guiaddons5 5.28.0-1
ii  libkf5i18n5  5.28.0-1
ii  libkf5iconthemes55.28.0-1
ii  libkf5itemmodels55.28.0-1
ii  libkf5itemviews5 5.28.0-1
ii  libkf5jobwidgets55.28.0-1
ii  libkf5kcmutils5  5.28.0-1
ii  libkf5kdelibs4support5   5.28.0-1
ii  libkf5kiocore5   5.28.0-1
ii  libkf5kiofilewidgets55.28.0-1
ii  libkf5kiowidgets55.28.0-1
ii  libkf5newstuff5  5.28.0-1
ii  libkf5notifications5 5.28.0-1
ii  libkf5notifyconfig5  5.28.0-1
ii  libkf5parts5 5.28.0-1
ii  libkf5people55.28.0-1
ii  libkf5peoplewidgets5 5.28.0-1
ii  libkf5plasma55.28.0-1
ii  libkf5plasmaquick5   5.28.0-1
ii  libkf5quickaddons5   5.28.0-1
ii  libkf5runner55.28.0-1
ii  libkf5service-bin5.28.0-1
ii  libkf5service5   5.28.0-1
ii  libkf5solid5 5.28.0-2
ii  libkf5sonnetui5  5.28.0-1
ii  libkf5wallet-bin 5.28.0-1
ii  libkf5wallet55.28.0-1
ii  libkf5widgetsaddons5 5.28.0-1
ii  libkf5windowsystem5  5.28.0-1
ii  libkf5xmlgui55.28.0-1
ii  libkfontinst54:5.8.4-1
ii  libkfontinstui5  4:5.8.4-1
ii  libkworkspace5-5 4:5.8.4-1
ii  libpackagekitqt5-0   0.9.6-1
ii  libphonon4qt5-4  4:4.9.0-4
ii  libpulse-mainloop-glib0  9.0-5
ii  libpulse09.0-5
ii  libqt5concurrent55.7.1~20161021+dfsg-6
ii  libqt5core5a 5.7.1~20161021+dfsg-6
ii  libqt5dbus5  5.7.1~20161021+dfsg-6
ii  libqt5gui5   5.7.1~20161021+dfsg-6
ii  libqt5network5   5.7.1~20161021+dfsg-6
ii  libqt5printsupport5  5.7.1~20161021+dfsg-6
ii  libqt5qml5  

Bug#840364: marked as done (kannel: Please remove build dependency on jade)

[Debian Bug Tracking System]

Your message dated Sat, 03 Dec 2016 21:04:41 +
with message-id 
and subject line Bug#840364: fixed in kannel 1.4.4-4
has caused the Debian Bug report #840364,
regarding kannel: Please remove build dependency on jade
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.)


-- 
840364: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840364
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kannel
Severity: normal

The kannel package build depends on jade, which is obsolete and will be
removed from Debian.  The replacement for jade is openjade.  However,
kannel does not need to build depend on openjade because the
docbook-dsssl package (also a build dependency of kannel) depends on
openjade.  So, jade can simply be removed from the build dependencies.

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

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

-- 
Neil Roeth
--- End Message ---
--- Begin Message ---
Source: kannel
Source-Version: 1.4.4-4

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated kannel package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 03 Dec 2016 20:22:16 +0100
Source: kannel
Binary: kannel kannel-extras kannel-docs kannel-dev
Architecture: source amd64 all
Version: 1.4.4-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Kannel maintainers 
Changed-By: Jonas Smedegaard 
Description:
 kannel - WAP and SMS gateway
 kannel-dev - WAP and SMS gateway headers and development files
 kannel-docs - WAP and SMS gateway documentation
 kannel-extras - WAP and SMS gateway extras
Closes: 819915 840364 845858
Changes:
 kannel (1.4.4-4) unstable; urgency=medium
 .
   * (Build-)depend on default-libmysqlclient-dev, with
 libmysqlclient-dev as fallback to ease backporting.
 Closes: Bug#845858. Thanks to Otto.
   * Stop build-depend on jade: Obsolete and needless (successor openjade
 pulled in already bia docbook-dsssl).
 Closes: Bug#840364. Thanks to Neil Roeth.
   * (Build-)depend on libssl1.0-dev, with older libssl-dev only as
 fallback (and only pre-1.1 versions) to ease backporting.
 See bug#828362.
   * Add patches to make build reproducible.
 Closes: Bug#819915. Thanks to Alexis Bienvenüe.
   * Declare compliance with Debian Policy 3.9.8.
Checksums-Sha1:
 c6680f931a993ab134ec61c7118e940564767571 2433 kannel_1.4.4-4.dsc
 c5560f84fa836b3c9149b6e12b3852cd24819552 14488 kannel_1.4.4-4.debian.tar.xz
 2b25d6d159fe05c394c7098ca9c4eb80e4cdad6c 3271902 
kannel-dbgsym_1.4.4-4_amd64.deb
 adf1a501fddd1271cfd654f84f5297b2c35e260f 786066 kannel-dev_1.4.4-4_amd64.deb
 d0030c2cf4eb74d8197d4707c72253cb9e090fa6 4078190 kannel-docs_1.4.4-4_all.deb
 6df0c685f78567acf9ee3b574aaf277c940ebf1d 14356156 
kannel-extras-dbgsym_1.4.4-4_amd64.deb
 8a44e6e8c3123c931ea44eb9bcfa35481f689562 1748684 
kannel-extras_1.4.4-4_amd64.deb
 37fac2a7bd0277d6b0864ca687801e1f1796540a 10398 kannel_1.4.4-4_amd64.buildinfo
 1b4c885579d9d935ac47a937343a4f97fd9389b6 850518 kannel_1.4.4-4_amd64.deb
Checksums-Sha256:
 9a362c068704f3e4426acd1f41d9e549ed57df82868545ac2553451bffc045f6 2433 
kannel_1.4.4-4.dsc
 bfa3da71ad10beb928c475be2a36918b8603b120878f9523f7b79a6a10c3df7c 14488 
kannel_1.4.4-4.debian.tar.xz
 b27ce5188f5fc19fdaabcbb97e165214cf0127ec7bc76294c01365c7d6515a49 3271902 
kannel-dbgsym_1.4.4-4_amd64.deb
 7dd43f0a147964541e3e784df55ebba0f08139b0117d2c02dfdcad0220512ec1 786066 
kannel-dev_1.4.4-4_amd64.deb
 847ff36742a98842ddf9fadf2589c1547f42cef6c9f82595a94cdcb529446c2e 4078190 
kannel-docs_1.4.4-4_all.deb
 

Processed: Re: Processed: gdc: FTBFS: ld: final link failed: Bad value

[Debian Bug Tracking System]

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

> reassign 846669 gdc-6
Bug #846669 [gdc] titanion: FTBFS: ld: final link failed: Bad value
Bug #846699 [gdc] a7xpg: FTBFS: ld: final link failed: Bad value
Bug #846715 [gdc] gunroar: FTBFS: ld: final link failed: Bad value
Bug #846720 [gdc] torus-trooper: FTBFS: ld: final link failed: Bad value
Bug #846724 [gdc] tatan: FTBFS: ld: final link failed: Bad value
Bug #846725 [gdc] mu-cade: FTBFS: ld: final link failed: Bad value
Bug #846726 [gdc] tumiki-fighters: FTBFS: ld: final link failed: Bad value
Bug #846742 [gdc] meson: FTBFS: ld: final link failed: Bad value
Bug reassigned from package 'gdc' to 'gdc-6'.
Bug reassigned from package 'gdc' to 'gdc-6'.
Bug reassigned from package 'gdc' to 'gdc-6'.
Bug reassigned from package 'gdc' to 'gdc-6'.
Bug reassigned from package 'gdc' to 'gdc-6'.
Bug reassigned from package 'gdc' to 'gdc-6'.
Bug reassigned from package 'gdc' to 'gdc-6'.
Bug reassigned from package 'gdc' to 'gdc-6'.
Ignoring request to alter found versions of bug #846669 to the same values 
previously set
Ignoring request to alter found versions of bug #846699 to the same values 
previously set
Ignoring request to alter found versions of bug #846715 to the same values 
previously set
Ignoring request to alter found versions of bug #846720 to the same values 
previously set
Ignoring request to alter found versions of bug #846724 to the same values 
previously set
Ignoring request to alter found versions of bug #846725 to the same values 
previously set
Ignoring request to alter found versions of bug #846726 to the same values 
previously set
Ignoring request to alter found versions of bug #846742 to the same values 
previously set
Ignoring request to alter fixed versions of bug #846669 to the same values 
previously set
Ignoring request to alter fixed versions of bug #846699 to the same values 
previously set
Ignoring request to alter fixed versions of bug #846715 to the same values 
previously set
Ignoring request to alter fixed versions of bug #846720 to the same values 
previously set
Ignoring request to alter fixed versions of bug #846724 to the same values 
previously set
Ignoring request to alter fixed versions of bug #846725 to the same values 
previously set
Ignoring request to alter fixed versions of bug #846726 to the same values 
previously set
Ignoring request to alter fixed versions of bug #846742 to the same values 
previously set
> forcemerge 845377 846669
Bug #845377 [gdc-6] gdc-6: libdl trouble again
Bug #845730 [gdc-6] torus-trooper: FTBFS: relocation R_X86_64_PC32 against 
symbol `_D3std6format18__T10FormatSpecTaZ10FormatSpec6flZeroMFNaNbNdNiNfbZv' 
can not be used when making a shared object; recompile with -fPIC
Bug #846725 [gdc-6] mu-cade: FTBFS: ld: final link failed: Bad value
Severity set to 'important' from 'serious'
Severity set to 'important' from 'serious'
Severity set to 'important' from 'serious'
Severity set to 'important' from 'serious'
Severity set to 'important' from 'serious'
Severity set to 'important' from 'serious'
Severity set to 'important' from 'serious'
Severity set to 'important' from 'serious'
Removed indication that 846725 affects torus-trooper, tumiki-fighters, gunroar, 
a7xpg, mu-cade, tatan, and titanion
Removed indication that 846669 affects tatan, titanion, gunroar, torus-trooper, 
tumiki-fighters, a7xpg, and mu-cade
Removed indication that 846699 affects mu-cade, a7xpg, gunroar, 
tumiki-fighters, torus-trooper, titanion, and tatan
Removed indication that 846715 affects tatan, titanion, tumiki-fighters, 
torus-trooper, gunroar, a7xpg, and mu-cade
Removed indication that 846720 affects titanion, tatan, a7xpg, mu-cade, 
torus-trooper, tumiki-fighters, and gunroar
Removed indication that 846724 affects titanion, tatan, a7xpg, mu-cade, 
gunroar, tumiki-fighters, and torus-trooper
Removed indication that 846726 affects tatan, titanion, gunroar, torus-trooper, 
tumiki-fighters, a7xpg, and mu-cade
Removed indication that 846742 affects tatan, titanion, tumiki-fighters, 
torus-trooper, gunroar, a7xpg, and mu-cade
Marked as found in versions gcc-6/6.2.1-4.
Marked as found in versions gcc-6/6.2.1-4.
Marked as found in versions gcc-6/6.2.1-4.
Marked as found in versions gcc-6/6.2.1-4.
Marked as found in versions gcc-6/6.2.1-4.
Marked as found in versions gcc-6/6.2.1-4.
Marked as found in versions gcc-6/6.2.1-4.
Marked as found in versions gcc-6/6.2.1-4.
Bug #845377 [gdc-6] gdc-6: libdl trouble again
Added tag(s) stretch and sid.
Added tag(s) sid and stretch.
Bug #845730 [gdc-6] torus-trooper: FTBFS: relocation R_X86_64_PC32 against 
symbol `_D3std6format18__T10FormatSpecTaZ10FormatSpec6flZeroMFNaNbNdNiNfbZv' 
can not be used when making a shared object; recompile with -fPIC
Bug #846669 [gdc-6] titanion: FTBFS: ld: final link failed: Bad value
Bug #846699 [gdc-6] a7xpg: FTBFS: ld: final link failed: Bad value
Bug #846715 [gdc-6] gunroar: FTBFS: ld: final link failed: Bad value
Bug #846720 [gdc-6] torus-trooper: 

Bug#846816: java.lang.NoSuchFieldError: DLU2

[gregor herrmann]

On Sat, 03 Dec 2016 21:32:31 +0100, Felix Natter wrote:

> >> STDERR: Exception in thread "AWT-EventQueue-1" 
> >> STDERR: java.lang.NoSuchFieldError: DLU2

> I just looked into it:

Thanks!
 
> - Using Paddings instead of Borders seems correct [1]
>   ("@deprecated Replaced by {@link Paddings}")

Ok.
 
> - I have fixed it using Borders->Paddings (1.5.16-3: I think we should
>   upload it), but I don't understand it:

> - seems to happen only at runtime?

That's what confused my as well ...
 
> > added to debian/patches/50_jgoodies-1.9.patch, but when starting
> > freeplane I then only see an empty white windows.
> I could reproduce this once after updating my sid (but not previously
> when updating jgoodies but not sid). Could you please try another
> desktop environment?

I don't have any desktop enviroments installed :)
(Just awesome as a window manager.)
 
> If that does not work, you can rename ~/.config/freeplane.
> This worked for me, and I can no longer reproduce the bug
> even when starting with the old ~/.config/freeplane.

I've now rebuilt freeplane from git, and installed it.
Again, I only get (a question about standard.mm) and then a white
window.

After blowing away ~/.config/freeplane, I don't get the dialog but a
white windows with a title of "whatsNew-1.5.x - Freeplane - Mind map
mode (Read Only) /usr/share/freeplane/doc/whatsNew-1.5.x.mm".

Oh, interesting, I can right-click, get a menu, can choose
fullscreen, and then I see a mindmap. I can also enable the menubar
etc.
When I leave fullscreen mode, all is gone (the mindmap as well as the
menubar ...).

Back in fullscreen mode, when I enter the configuration, I get an
empty grey window.

Anyway, it's well possible that this is all another problem and
related to some interaction between my window manager and
java/freeplane.

And I can confirm that the updated patch in git gets rid of the
error.
 

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Element of Crime: Mittelpunkt der Welt


signature.asc
Description: Digital Signature

Bug#846816: java.lang.NoSuchFieldError: DLU2

[Felix Natter]

gregor herrmann  writes:

hello all,

> Control: tag -1 + confirmed
>
> On Sat, 03 Dec 2016 14:50:40 +0100, Vincent Smeets wrote:
>
>> Package: freeplane
>> Version: 1.5.16-2
>> Severity: grave
>> Justification: renders package unusable
>
>> Here I started freeplane from the command line. It shows you the log
>> output and the raised exception.
>
>> STDERR: Exception in thread "AWT-EventQueue-1" 
>> STDERR: java.lang.NoSuchFieldError: DLU2
>
> Thanks for your bug report. I can reproduce it (on unstable).
>
>> -- Package-specific info:
>> ii  freeplane   1.5.16-2   allJava 
>> program for working with Mind Maps
>
>> Versions of packages freeplane depends on:
>> ii  libjgoodies-forms-java   1.9.0-3
>
> Looks like we missed a part when creating the patch for
> jgoodies-forms 1.9.0 compatibility ...
>
>
> I get past this error with
>
> +--- 
> a/freeplane/src/main/java/org/freeplane/features/styles/mindmapmode/StyleEditorPanel.java
>  
> b/freeplane/src/main/java/org/freeplane/features/styles/mindmapmode/StyleEditorPanel.java
> +@@ -113,8 +113,8 @@
> + import org.freeplane.features.ui.IMapViewManager;
> + 
> + import com.jgoodies.forms.builder.DefaultFormBuilder;
> +-import com.jgoodies.forms.factories.Borders;
> +-import com.jgoodies.forms.layout.FormLayout;
> ++import com.jgoodies.forms.factories.*;
> ++import com.jgoodies.forms.layout.*;
> + 
> + public class StyleEditorPanel extends JPanel {
> +   private static final int FONT_SIZE = 
> Math.round(UITools.FONT_SCALE_FACTOR * 8);
> +@@ -842,7 +842,7 @@
> +   final String form = "right:max(20dlu;p), 2dlu, p, 
> 1dlu,right:max(20dlu;p), 4dlu, 80dlu, 7dlu";
> +   final FormLayout rightLayout = new FormLayout(form, "");
> +   final DefaultFormBuilder rightBuilder = new 
> DefaultFormBuilder(rightLayout);
> +-  rightBuilder.border(Borders.DLU2);
> ++  rightBuilder.border(Paddings.DLU2);
> +   new 
> SeparatorProperty("OptionPanel.separator.NodeStyle").layout(rightBuilder);
> +   if (addStyleBox) {
> +   addAutomaticLayout(rightBuilder);

I just looked into it:

- Using Paddings instead of Borders seems correct [1]
  ("@deprecated Replaced by {@link Paddings}")

- I have fixed it using Borders->Paddings (1.5.16-3: I think we should
  upload it), but I don't understand it:

- the jgoodies documentation says
  (http://www.jgoodies.com/download/libraries/forms/RELEASE-NOTES.txt):
  CHANGES IN 1.12.0: "Removed the deprecated Borders class that has been 
replaced
  by the Paddings class in version 1.9.0."
--> so Borders.* is still in jgoodies-1.9
--> we use this upstream [2]
compile 'com.jgoodies:jgoodies-forms:1.9.0',
compile 'com.jgoodies:jgoodies-common:1.8.1'
and I don't see any problem with this in upstream

- seems to happen only at runtime?

[1] 
https://anonscm.debian.org/cgit/pkg-java/libjgoodies-forms-java.git/tree/src/main/java/com/jgoodies/forms/factories/Borders.java
[2] https://github.com/freeplane/freeplane/

> added to debian/patches/50_jgoodies-1.9.patch, but when starting
> freeplane I then only see an empty white windows.

I could reproduce this once after updating my sid (but not previously
when updating jgoodies but not sid). Could you please try another
desktop environment?

If that does not work, you can rename ~/.config/freeplane.
This worked for me, and I can no longer reproduce the bug
even when starting with the old ~/.config/freeplane.

> But I guess that's no hard problem to fix for someone who knows Java
> :)

I don't understand this. If you don't have an expanation, I will
probably ask on debian-java.

Cheers and Best Regards,
-- 
Felix Natter

Bug#804585: marked as done (pywbem: FTBFS: ssl3 is gone from openssl)

[Debian Bug Tracking System]

Your message dated Sun, 4 Dec 2016 01:05:58 +0500
with message-id <20161203200558.2sstfbhl2am6o...@belkar.wrar.name>
and subject line 
has caused the Debian Bug report #804585,
regarding pywbem: FTBFS: ssl3 is gone from openssl
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.)


-- 
804585: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804585
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pywbem
Version: 0.8.0~dev650-1
Severity: serious
Justification: fails to build from source
Tags: sid 
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

 debian/rules clean
make: Circular debian/wbemcli.py.1.xml <- wbemcli.py.1 dependency dropped.
xsltproc -''-nonet -''-param man.charmap.use.subset "0" 
/usr/share/sgml/docbook/stylesheet/xsl/nwalsh/manpages/docbook.xsl 
debian/wbemcli.py.1.xml
I/O error : Attempt to load network entity 
http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd
debian/wbemcli.py.1.xml:62: warning: failed to load external entity 
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd;
]>
  ^
Note: Writing wbemcli.py.1
dh debian/rules --with python2
dh clean --with python2
   dh_testdir
   dh_auto_clean
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
python setup.py clean -a
Traceback (most recent call last):
  File "setup.py", line 28, in 
from pywbem import mof_compiler
  File "/pywbem-0.8.0~dev650/pywbem/__init__.py", line 143, in 
from pywbem.cim_operations import *
  File "/pywbem-0.8.0~dev650/pywbem/cim_operations.py", line 31, in 
from pywbem import cim_obj, cim_xml, cim_http, cim_types
  File "/pywbem-0.8.0~dev650/pywbem/cim_http.py", line 31, in 
from M2Crypto import SSL, Err
  File "/usr/lib/python2.7/dist-packages/M2Crypto/__init__.py", line 22, in 

import __m2crypto
ImportError: /usr/lib/python2.7/dist-packages/M2Crypto/__m2crypto.so: undefined 
symbol: SSLv3_method
dh_auto_clean: python setup.py clean -a returned exit code 1
debian/rules:18: recipe for target 'clean' failed

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/pywbem.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
This was never a bug in pywbem but in python-m2crypto. It is now fixed and
pywbem rebuilds OK.

-- 
WBR, wRAR


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

Bug#846871: python-sparqlwrapper: requires keeplive==0.5

[Hilko Bengen]

Package: python-sparqlwrapper
Version: 1.7.6-1
Severity: grave

Dear Maintainer,

I am working on packaging aff4 whose Python bindings require
python-sparqlwrapper via python-rdflib.

The tests cannot be run because pytest notices an unsatisfied
dependency, keepalive>=0.5, as can be seen below. In my build chroot, as
far as I can see, this dependency is only declared in
.../SPARQLWrapper-1.7.6.egg-info/requires.txt.

,
| dh_auto_test --sourcedirectory=pyaff4 --buildsystem=pybuild
| I: pybuild base:184: python2.7 setup.py test
| running test
| Searching for keepalive>=0.5
| 
| Note: Bypassing https://pypi.python.org/simple/keepalive/ (disallowed
| host; see http://bit.ly/1dg9ijs for details).
| 
| Couldn't find index page for 'keepalive' (maybe misspelled?)
| Scanning index of all packages (this may take a while)
| 
| Note: Bypassing https://pypi.python.org/simple/ (disallowed host; see
| http://bit.ly/1dg9ijs for details).
| 
| No local packages or working download links found for keepalive>=0.5
| error: Could not find suitable distribution for
| Requirement.parse('keepalive>=0.5')
| E: pybuild pybuild:276: test: plugin distutils failed with: exit code=1:
| python2.7 setup.py test
| dh_auto_test: pybuild --test -i python{version} -p 2.7 --dir pyaff4
| returned exit code 13
`

After preparing and installing a python-keepalive package, the tests
succeed.

I am not sure that the keepalive module is really needed because one
will only get a warning if the module cannot be imported. Removing the
requires.txt line would probably be enough.

Cheers,
-Hilko

Processed: pgadmin3: SIGABRT after fatal error complaint regarding libwxgtx ABI mismatch

[Debian Bug Tracking System]

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

> reassign 846019 wxwidgets3.0
Bug #846019 [pgadmin3] pgadmin3: SIGABRT after fatal error complaint regarding 
libwxgtx ABI mismatch
Bug reassigned from package 'pgadmin3' to 'wxwidgets3.0'.
No longer marked as found in versions pgadmin3/1.22.2-1.
Ignoring request to alter fixed versions of bug #846019 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#846019: pgadmin3: SIGABRT after fatal error complaint regarding libwxgtx ABI mismatch

[Denis Briand]

reassign 846019 wxwidgets3.0
thanks

Hello Björn,
Thanks for this report bug.
It's not completly the same of #844486

In your case, you have a fatal error.

In the wxwidgets3.0 src/common/appbase.cpp source code (line 782),
the "wxLogFatalError(msg.c_str())" line shouldn't be executed !

Because you have the same library and program version.
You just haven't the same ABI version who must return a simple warning.

I reassign this bug to wxwidgets3.0.

best regards

Denis Briand


signature.asc
Description: Digital signature

Bug#828415: closing 828415

[Andrew Starr-Bochicchio]

close 828415 
thanks

Processed: closing 828415

[Debian Bug Tracking System]

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

> close 828415
Bug #828415 [src:libtorrent-rasterbar] libtorrent-rasterbar: FTBFS with openssl 
1.1.0
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: gdc: FTBFS: ld: final link failed: Bad value

[Debian Bug Tracking System]

Processing control commands:

> reassign 846669 gdc
Bug #846669 [src:titanion] titanion: FTBFS: ld: final link failed: Bad value
Bug reassigned from package 'src:titanion' to 'gdc'.
No longer marked as found in versions titanion/0.3.dfsg1-6.
Ignoring request to alter fixed versions of bug #846669 to the same values 
previously set
> reassign 846699 gdc
Bug #846699 [src:a7xpg] a7xpg: FTBFS: ld: final link failed: Bad value
Bug reassigned from package 'src:a7xpg' to 'gdc'.
No longer marked as found in versions a7xpg/0.11.dfsg1-9.
Ignoring request to alter fixed versions of bug #846699 to the same values 
previously set
> reassign 846715 gdc
Bug #846715 [src:gunroar] gunroar: FTBFS: ld: final link failed: Bad value
Bug reassigned from package 'src:gunroar' to 'gdc'.
No longer marked as found in versions gunroar/0.15.dfsg1-8.
Ignoring request to alter fixed versions of bug #846715 to the same values 
previously set
> reassign 846720 gdc
Bug #846720 [src:torus-trooper] torus-trooper: FTBFS: ld: final link failed: 
Bad value
Bug reassigned from package 'src:torus-trooper' to 'gdc'.
No longer marked as found in versions torus-trooper/0.22.dfsg1-11.
Ignoring request to alter fixed versions of bug #846720 to the same values 
previously set
> reassign 846724 gdc
Bug #846724 [src:tatan] tatan: FTBFS: ld: final link failed: Bad value
Bug reassigned from package 'src:tatan' to 'gdc'.
No longer marked as found in versions tatan/1.0.dfsg1-7.
Ignoring request to alter fixed versions of bug #846724 to the same values 
previously set
> reassign 846725 gdc
Bug #846725 [src:mu-cade] mu-cade: FTBFS: ld: final link failed: Bad value
Bug reassigned from package 'src:mu-cade' to 'gdc'.
No longer marked as found in versions mu-cade/0.11.dfsg1-11.
Ignoring request to alter fixed versions of bug #846725 to the same values 
previously set
> reassign 846726 gdc
Bug #846726 [src:tumiki-fighters] tumiki-fighters: FTBFS: ld: final link 
failed: Bad value
Bug reassigned from package 'src:tumiki-fighters' to 'gdc'.
No longer marked as found in versions tumiki-fighters/0.2.dfsg1-8.
Ignoring request to alter fixed versions of bug #846726 to the same values 
previously set
> forcemerge 846742 846669 846699 846715 846720 846724 846725 846726
Bug #846742 [gdc] meson: FTBFS: ld: final link failed: Bad value
Bug #846669 [gdc] titanion: FTBFS: ld: final link failed: Bad value
Bug #846699 [gdc] a7xpg: FTBFS: ld: final link failed: Bad value
Bug #846715 [gdc] gunroar: FTBFS: ld: final link failed: Bad value
Bug #846720 [gdc] torus-trooper: FTBFS: ld: final link failed: Bad value
Bug #846724 [gdc] tatan: FTBFS: ld: final link failed: Bad value
Bug #846725 [gdc] mu-cade: FTBFS: ld: final link failed: Bad value
Bug #846726 [gdc] tumiki-fighters: FTBFS: ld: final link failed: Bad value
Merged 846669 846699 846715 846720 846724 846725 846726 846742
> affects 846742 titanion a7xpg gunroar torus-trooper tatan mu-cade 
> tumiki-fighters
Bug #846742 [gdc] meson: FTBFS: ld: final link failed: Bad value
Bug #846669 [gdc] titanion: FTBFS: ld: final link failed: Bad value
Bug #846699 [gdc] a7xpg: FTBFS: ld: final link failed: Bad value
Bug #846715 [gdc] gunroar: FTBFS: ld: final link failed: Bad value
Bug #846720 [gdc] torus-trooper: FTBFS: ld: final link failed: Bad value
Bug #846724 [gdc] tatan: FTBFS: ld: final link failed: Bad value
Bug #846725 [gdc] mu-cade: FTBFS: ld: final link failed: Bad value
Bug #846726 [gdc] tumiki-fighters: FTBFS: ld: final link failed: Bad value
Added indication that 846742 affects titanion, a7xpg, gunroar, torus-trooper, 
tatan, mu-cade, and tumiki-fighters
Added indication that 846669 affects titanion, a7xpg, gunroar, torus-trooper, 
tatan, mu-cade, and tumiki-fighters
Added indication that 846699 affects titanion, a7xpg, gunroar, torus-trooper, 
tatan, mu-cade, and tumiki-fighters
Added indication that 846715 affects titanion, a7xpg, gunroar, torus-trooper, 
tatan, mu-cade, and tumiki-fighters
Added indication that 846720 affects titanion, a7xpg, gunroar, torus-trooper, 
tatan, mu-cade, and tumiki-fighters
Added indication that 846724 affects titanion, a7xpg, gunroar, torus-trooper, 
tatan, mu-cade, and tumiki-fighters
Added indication that 846725 affects titanion, a7xpg, gunroar, torus-trooper, 
tatan, mu-cade, and tumiki-fighters
Added indication that 846726 affects titanion, a7xpg, gunroar, torus-trooper, 
tatan, mu-cade, and tumiki-fighters

-- 
846669: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846669
846699: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846699
846715: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846715
846720: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846720
846724: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846724
846725: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846725
846726: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846726
846742: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846742
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#846669: gdc: FTBFS: ld: final link failed: Bad value

[Markus Koschany]

Control: reassign 846669 gdc
Control: reassign 846699 gdc
Control: reassign 846715 gdc
Control: reassign 846720 gdc
Control: reassign 846724 gdc
Control: reassign 846725 gdc
Control: reassign 846726 gdc
Control: forcemerge 846742 846669 846699 846715 846720 846724 846725 846726
Control: affects 846742 titanion a7xpg gunroar torus-trooper tatan mu-cade 
tumiki-fighters

On Sat, 3 Dec 2016 08:22:09 +0100 Lucas Nussbaum  wrote:
> Source: titanion
> Version: 0.3.dfsg1-6
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20161202 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):
> > /usr/bin/ld: /tmp/ccMLn2mM.o: relocation R_X86_64_PC32 against symbol
`_D6object14__T7_rawDupTaZ7_rawDupFNaNbANgaZANga' 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

Hi,

this looks like a bug in gdc thus I am going to reassign the bug reports and 
mark these packages as
affected.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#846692: marked as done (node-repeat-element: FTBFS: Test failures)

[Debian Bug Tracking System]

Your message dated Sat, 03 Dec 2016 18:35:09 +
with message-id 
and subject line Bug#846692: fixed in node-repeat-element 1.1.2+github-2
has caused the Debian Bug report #846692,
regarding node-repeat-element: FTBFS: Test failures
to be marked as done.

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

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


-- 
846692: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846692
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-repeat-element
Version: 1.1.2+github-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161202 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):
> at Function.Module._load (module.js:300:12)
> at Module.require (module.js:353:17)
> at require (internal/module.js:12:17)
> at /usr/lib/nodejs/mocha/lib/mocha.js:172:27
> at Array.forEach (native)
> at Mocha.loadFiles (/usr/lib/nodejs/mocha/lib/mocha.js:169:14)
> at Mocha.run (/usr/lib/nodejs/mocha/lib/mocha.js:356:31)
> at Object. (/usr/lib/nodejs/mocha/bin/_mocha:366:16)
> at Module._compile (module.js:409:26)
> at Object.Module._extensions..js (module.js:416:10)
> at Module.load (module.js:343:32)
> at Function.Module._load (module.js:300:12)
> at Function.Module.runMain (module.js:441:10)
> at startup (node.js:139:18)
> at node.js:974:3
> debian/rules:13: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   
http://aws-logs.debian.net/2016/12/02/node-repeat-element_1.1.2+github-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: node-repeat-element
Source-Version: 1.1.2+github-2

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated node-repeat-element 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 03 Dec 2016 23:25:48 +0530
Source: node-repeat-element
Binary: node-repeat-element
Architecture: source
Version: 1.1.2+github-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Pirate Praveen 
Description:
 node-repeat-element - create an array by repeating the given value n times
Closes: 846692
Changes:
 node-repeat-element (1.1.2+github-2) unstable; urgency=medium
 .
   * Add node-minimist to builddeps (Closes: #846692)
Checksums-Sha1:
 4870d25e21b8e2cf478528d88ad0dacc29afe309 2180 
node-repeat-element_1.1.2+github-2.dsc
 9c3f76952f7d5456178a02cd88685984e0b9bb9d 2136 
node-repeat-element_1.1.2+github-2.debian.tar.xz
Checksums-Sha256:
 bb51e993af5d3308432f361968db436eff210f5b0113827de89e66ca0c36f104 2180 
node-repeat-element_1.1.2+github-2.dsc
 28b573f7a54217109437a2debfe27e4bc445861a6f4a6cd845a59b8722d07940 2136 
node-repeat-element_1.1.2+github-2.debian.tar.xz
Files:
 a4bec971fb7c36c99cff6b27cc091fd7 2180 web optional 
node-repeat-element_1.1.2+github-2.dsc
 9e01ec6883e8a2977c78554ed176c8ac 2136 web optional 
node-repeat-element_1.1.2+github-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEKnl0ri/BUtd4Z9pKzh+cZ0USwioFAlhDCeAACgkQzh+cZ0US
wiqkUw/6A8J7hnVSBqS7LdTvfK/wxDrdRYSJ8XSfaS3sLKoXz80bF4F4KmAuaoRL
r90gUmtP/t/D4JKz6V9Yg9TyflyQNsORuLwsObQgcGKVaoCh9fM+MxpdZqJTtF6/
+OwsUIaEZAveEbMx9JqqS97bK+ATXkWVa+K+6EIAUH30y2cjIfM+Ec9eVVK79qxE
QSut2wIFephu+ORlAKdMs4D7OHGCtcQU2AMoN4rvRu3R2qbD1lrxy1RPo44qJh2R
tVArqvANK3F7xTNo50dRYwXXE3aKXVmtr4teTfvDrGT3kttA7PY1exUgKt6s6yPl

Bug#846700: marked as done (node-extend-shallow: FTBFS: Test failures)

[Debian Bug Tracking System]

Your message dated Sat, 03 Dec 2016 18:35:04 +
with message-id 
and subject line Bug#846700: fixed in node-extend-shallow 2.0.1-3
has caused the Debian Bug report #846700,
regarding node-extend-shallow: FTBFS: Test failures
to be marked as done.

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

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


-- 
846700: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846700
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-extend-shallow
Version: 2.0.1-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161202 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):
> at Function.Module._load (module.js:300:12)
> at Module.require (module.js:353:17)
> at require (internal/module.js:12:17)
> at /usr/lib/nodejs/mocha/lib/mocha.js:172:27
> at Array.forEach (native)
> at Mocha.loadFiles (/usr/lib/nodejs/mocha/lib/mocha.js:169:14)
> at Mocha.run (/usr/lib/nodejs/mocha/lib/mocha.js:356:31)
> at Object. (/usr/lib/nodejs/mocha/bin/_mocha:366:16)
> at Module._compile (module.js:409:26)
> at Object.Module._extensions..js (module.js:416:10)
> at Module.load (module.js:343:32)
> at Function.Module._load (module.js:300:12)
> at Function.Module.runMain (module.js:441:10)
> at startup (node.js:139:18)
> at node.js:974:3
> debian/rules:13: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   
http://aws-logs.debian.net/2016/12/02/node-extend-shallow_2.0.1-2_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: node-extend-shallow
Source-Version: 2.0.1-3

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated node-extend-shallow 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 03 Dec 2016 23:31:25 +0530
Source: node-extend-shallow
Binary: node-extend-shallow
Architecture: source
Version: 2.0.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Pirate Praveen 
Description:
 node-extend-shallow - extend an object with the properties of additional 
objects
Closes: 846700
Changes:
 node-extend-shallow (2.0.1-3) unstable; urgency=medium
 .
   * Add node-minimist to builddeps (Closes: #846700)
Checksums-Sha1:
 9103739a8d142fe1a558e4465a78d55e123d06cc 2176 node-extend-shallow_2.0.1-3.dsc
 d22a57b23aebf774eb3db7bfd92361ba26f1c93a 2276 
node-extend-shallow_2.0.1-3.debian.tar.xz
Checksums-Sha256:
 0f1f4c15322a90dbf3b3ed2c60910834222e506b6f1be4e1771ad93069545cde 2176 
node-extend-shallow_2.0.1-3.dsc
 649dfb06427a3217208229950a5a13b43082fb55d6ab98938ceca6abc80c0ff3 2276 
node-extend-shallow_2.0.1-3.debian.tar.xz
Files:
 6f67b19603146875a05b59fb75292ff3 2176 web optional 
node-extend-shallow_2.0.1-3.dsc
 d93912563dd4d23a68fb9a2a6bec39db 2276 web optional 
node-extend-shallow_2.0.1-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEKnl0ri/BUtd4Z9pKzh+cZ0USwioFAlhDCYYACgkQzh+cZ0US
wipDZg/+KU12CSOeJyfEYaR0HQLzV7jHpHvsTOBPGL1W2QYjIK6WYoxfo4jDzw3q
RYHt4ub87zLlyVHvCVan6cwrflrMxDQNno5asWMIKPiBuMvWK2b6jk64vDTfD6SR
zjIa40DqFchSbxeZWYGHhMgfTIpNV6KXyKyAJFTKMKo3MucWtpJH/pPE0YmWIOTS
IERnBAoLacuZcKFTJle80eCSGDeUSwCYUTw/RLRMc+01yirNMn6yNlJsP2fV8BZB
1TVxhwqBB2YIgRyae3/LggwR2VhNUQWqUoJLpA5NxwD+PemojRZxpxG3/aDs4RWI
Jpt2n26i9UEocqFU7xYUmlv+h2TMjSJl8i39fSWKiNAINh1wK9YwshvEL8wZYT1R

Bug#846353: FTBFS: ERROR: Test "ruby2.3" failed. Exiting.

[Sebastiaan Couwenberg]

Control: tags -1 pending

On 12/03/2016 07:19 PM, Gilles Filippini wrote:
> I've filed #846853 against src:hdf-eos5. There are issues in
> ruby-hdfeos5 as well. See the attached patch.
> 
> With these fixes the ruby-hdfeos5 testsuite passes on 64 bit and 32 bit
> arches.

Thanks for the patch! I've applied it in git, and will do a team upload
after hdf-eos5 is fixed, unless Youhei beats me to it.

Kind Regards,

Bas

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



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#846353: FTBFS: ERROR: Test "ruby2.3" failed. Exiting.

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #846353 [ruby-hdfeos5] FTBFS: ERROR: Test "ruby2.3" failed. Exiting.
Added tag(s) pending.

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

Bug#845963: marked as done (multistrap triest to feed "GPG keybox database version 1" to apt)

[Debian Bug Tracking System]

Your message dated Sat, 03 Dec 2016 18:21:33 +
with message-id 
and subject line Bug#845963: fixed in multistrap 2.2.2
has caused the Debian Bug report #845963,
regarding multistrap triest to feed "GPG keybox database version 1" to apt
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.)


-- 
845963: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845963
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: multistrap
Version: 2.2.1
Severity: grave
Justification: renders package unusable

Hi,

multistrap seems to use

gpg --no-default-keyring --homedir=${dir}/etc/apt/trusted.gpg.d/ 
--keyring=multistrap.gpg --import ...

to prepare files for /etc/apt/trusted.gpg.d. With gnupg (>= 2) this will
create files of type "GPG keybox database version 1". That format is
incompatible with apt which uses gpgv. Instead the binary OpenPGP format
(also known as "GPG key public ring") should be used which is the common
export format of gnupg and works across all gnupg versions and is
supported by gpgv.

I'm making this bug "grave" because I cannot come up with a workaround
for this problem and am also not able to imagine a situation where a
used would want to create a system with untrusted packages.

Thanks!

cheers, josch
--- End Message ---
--- Begin Message ---
Source: multistrap
Source-Version: 2.2.2

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

Debian distribution maintenance software
pp.
Johannes Schauer  (supplier of updated multistrap package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 03 Dec 2016 18:53:43 +0100
Source: multistrap
Binary: multistrap
Architecture: source
Version: 2.2.2
Distribution: unstable
Urgency: medium
Maintainer: Johannes Schauer 
Changed-By: Johannes Schauer 
Description:
 multistrap - multiple repository bootstrap based on apt
Closes: 751896 803365 819103 835909 845963
Changes:
 multistrap (2.2.2) unstable; urgency=medium
 .
   * New maintainer (Closes: #835909)
   * Move development to dgit
   * Move B-D on po4a to Build-Depends-Arch (it's not needed for the clean
 target)
   * Bump debhelper compatibility level to 10
   * Switch debian/rules to dh and drop cdbs
   * Use dh_bash-completion to install bash completion script into the right
 location (fixes lintian warning about deprecated /etc/bash_completion.d/)
   * Do not try to feed GPG keybox database version 1 files to apt (closes:
 #845963)
   * Allow uppercase letters in paths (closes: #751896)
   * Allow shell special characters (including spaces) in paths (closes:
 #803365)
   * Stop creating /etc/dpkg/dpkg.cfg.d/multiarch (closes: #819103)
Checksums-Sha1:
 f982e06d9a8a04103b0caf57a69d34701180406e 1717 multistrap_2.2.2.dsc
 37d1d2d708801e3088e1d77fabd7a0dec624fb88 123720 multistrap_2.2.2.tar.xz
Checksums-Sha256:
 d52417c1f7266e13761cb0ec4ea5359a332a63099e39e8e1fc45100010366c0a 1717 
multistrap_2.2.2.dsc
 44fae56bd3521052a33675fe3a4ef4923ff28e62f06aa71e8a40540a61aa3ca4 123720 
multistrap_2.2.2.tar.xz
Files:
 fd836f97095208850a0fcf2b28c14b97 1717 utils optional multistrap_2.2.2.dsc
 a43bdc8b16715d73e900186e640edcc6 123720 utils optional multistrap_2.2.2.tar.xz

-BEGIN PGP SIGNATURE-

iQIuBAEBCAAYBQJYQwcTERxqb3NjaEBkZWJpYW4ub3JnAAoJEPLLpcePvYPhKUcP
/j26tkrrox+1iG4LPpkjePbWTGBpaeqfI+CQ3L0s3cVGPEP/flHZjgf7XhLpNQUd
s2q1zaOPzbrnbh4iuPovY8RQGRbeN3tgILmbyfIEW+h6D1VvBZsT0gOOpWGz8agn
ds8i90ngA5B9PGz0ZpkBputVyHt/BlxMvXma9hi/A1moXGl92G4J+2OAdR3roTyY
o1P9Czp0PcIEqXPp7l87K/B6LxNYxHHLlQoLcO4/iVxnxf/y8mHmfscURkmbkBvE
DY3Hs3n7ESe4b+2G4cXvE6orJYPfRvvJKU9E+u3F6XpUrTuzG3sgLoMNJemNfPrb
/Ji5AbWiNPBucNe0/OJXyjErFZWTd+KQ9BSn91nisFF3XaBfWtXylsCBf8Zkva1b
NcOMnoznJRwqY7dJ/u7kqrHYVIhCOBAsP5CRki0J9NZdC/zoa8aOabhrgDwEJb6+
kljeSPm+zWhvrfiN3Ai7Rz4HBLXDQj621hIv4xMgHd5TTaynHrBWnkrgWG3wUK3x
0x7Dg4Rl396fxQJjAGl7YyYEgljYPnmWnATCE4SuecuscnGWnvzhxinS5/98s0x4
aup5xrZwJJdi/zcn+Tkw/6sRcjNJ4GarfZQ+uTa/il1AAI/lLl5Diw/lFAxWHZOA

Bug#846676: marked as done (neutron-fwaas: FTBFS: build-dependency not installable: python-neutron (>= 2:9.0.0~rc1))

[Debian Bug Tracking System]

Your message dated Sat, 3 Dec 2016 19:17:01 +0100
with message-id 
and subject line Fixed
has caused the Debian Bug report #846676,
regarding neutron-fwaas: FTBFS: build-dependency not installable: 
python-neutron (>= 2:9.0.0~rc1)
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.)


-- 
846676: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846676
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: neutron-fwaas
Version: 1:9.0.0-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161202 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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dh-python, dh-systemd, 
> openstack-pkg-tools (>= 52~), python-all, python-pbr (>= 1.8), 
> python-setuptools, python-sphinx, alembic (>= 0.8.4), python-coverage, 
> python-eventlet (>= 0.18.4), python-fixtures (>= 3.0.0), python-hacking (>= 
> 0.10.0), python-httplib2, python-mock (>= 2.0), python-mysqldb, 
> python-netaddr (>= 0.7.13), python-neutron (>= 2:9.0.0~rc1), 
> python-neutron-lib (>= 0.4.0), python-oslo.concurrency (>= 3.8.0), 
> python-oslo.config (>= 1:3.14.0), python-oslo.db (>= 4.10.0), python-oslo.log 
> (>= 1.14.0), python-oslo.messaging (>= 5.2.0), python-oslo.serialization (>= 
> 1.10.0), python-oslo.service (>= 1.10.0), python-oslo.utils (>= 3.16.0), 
> python-oslosphinx (>= 2.5.0), python-oslotest (>= 1:1.10.0), python-psycopg2 
> (>= 2.5), python-pymysql, python-requests-mock (>= 1.0), python-six (>= 
> 1.9.0), python-sqlalchemy (>= 1.0.12), python-testresources, 
> python-testscenarios, python-testtools (>= 1.4.0), python-webob, 
> python-webtest, subunit, testrepository
> Filtered Build-Depends: debhelper (>= 9), dh-python, dh-systemd, 
> openstack-pkg-tools (>= 52~), python-all, python-pbr (>= 1.8), 
> python-setuptools, python-sphinx, alembic (>= 0.8.4), python-coverage, 
> python-eventlet (>= 0.18.4), python-fixtures (>= 3.0.0), python-hacking (>= 
> 0.10.0), python-httplib2, python-mock (>= 2.0), python-mysqldb, 
> python-netaddr (>= 0.7.13), python-neutron (>= 2:9.0.0~rc1), 
> python-neutron-lib (>= 0.4.0), python-oslo.concurrency (>= 3.8.0), 
> python-oslo.config (>= 1:3.14.0), python-oslo.db (>= 4.10.0), python-oslo.log 
> (>= 1.14.0), python-oslo.messaging (>= 5.2.0), python-oslo.serialization (>= 
> 1.10.0), python-oslo.service (>= 1.10.0), python-oslo.utils (>= 3.16.0), 
> python-oslosphinx (>= 2.5.0), python-oslotest (>= 1:1.10.0), python-psycopg2 
> (>= 2.5), python-pymysql, python-requests-mock (>= 1.0), python-six (>= 
> 1.9.0), python-sqlalchemy (>= 1.0.12), python-testresources, 
> python-testscenarios, python-testtools (>= 1.4.0), python-webob, 
> python-webtest, subunit, testrepository
> dpkg-deb: building package 'sbuild-build-depends-neutron-fwaas-dummy' in 
> '/<>/resolver-UdVKs5/apt_archive/sbuild-build-depends-neutron-fwaas-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-neutron-fwaas-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-UdVKs5/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-UdVKs5/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-UdVKs5/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-UdVKs5/apt_archive ./ Sources [855 B]
> Get:5 copy:/<>/resolver-UdVKs5/apt_archive ./ Packages [920 B]
> Fetched 2738 B in 0s (0 B/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install neutron-fwaas build dependencies (apt-based resolver)
> -
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the 

Bug#846353: FTBFS: ERROR: Test "ruby2.3" failed. Exiting.

[Gilles Filippini]

Control: block -1 by 846853
Control: tags -1 + patch

Gilles Filippini a écrit le 03/12/2016 à 02:34 :
> Gilles Filippini a écrit le 03/12/2016 à 01:35 :
>> Gilles Filippini a écrit le 02/12/2016 à 23:26 :
>>> Sebastiaan Couwenberg a écrit le 02/12/2016 à 15:34 :
 On 12/02/2016 09:55 AM, Sebastiaan Couwenberg wrote:
> On 12/01/2016 07:48 PM, Sebastiaan Couwenberg wrote:
>> On Wed, 30 Nov 2016 15:10:03 + Iain Lane wrote:
>>> This package FTBFS on 32 bit arches (works on amd64 and other 64 bit
>>> arches), maybe due to the new hdf5
>>
>> Quite likely, since hdf-eos5 hasn't been rebuilt for the hdf5 transition
>> yet. I suspect this issue to fix itself once that's done.
>
> It did not, but did only fail on 32-bit architectures.

 Gilles, these failures seem to be caused by the hid_t type change from
 32-bit to a 64-bit value. I'm not sure how to fix it for ruby-hdfeos5,
 can you maybe provide a patch?
>>>
>>> Damn, I tested the build on amd64 only :/
>>> I've tried fixing the 'incompatible pointer type' warning, but it
>>> deosn't change anything wrt the test suite.
>>> Is there a way to ensure first that hdf-eos5 works fine on 32 bit archs?
>>
>> CC-ing Alastair, maintainer of hdf-eos5.
>>
>> AIUI the problem lies in hdf-eos5. I've ran a very simple C test made
>> after the first lines of test/test_gd.rb (source attached), both on
>> amd64 and i386. It succeeds on amd64 and fails on i386 at the
>> HE5_GDdetach step with:
>>
>> $ ./myhe5-32
>> bufsize = 19
>> ColumnAmountAerosol
>> HDF5-DIAG: Error detected in HDF5 (1.10.0-patch1) thread 4142823168:
>>   #000: GDapi.c line 1140 in HE5_GDchkgdid(): Cannot get the Grid index
>>
>> major: Invalid arguments to routine
>> minor: Out of range
>> HDF5-DIAG: Error detected in HDF5 (1.10.0-patch1) thread 4142823168:
>>   #000: EHapi.c line 2206 in HE5_EHchkfid(): Invalid file ID: 0. ID
>> should range from 67108864 to  67109064 .
>>
>> major: Invalid arguments to routine
>> minor: Bad value
>> HDF5-DIAG: Error detected in HDF5 (1.10.0-patch1) thread 4142823168:
>>   #000: GDapi.c line 1151 in HE5_GDchkgdid(): Checking for file ID failed.
>>
>> major: Invalid arguments to routine
>> minor: Out of range
>> HDF5-DIAG: Error detected in HDF5 (1.10.0-patch1) thread 4142823168:
>>   #000: GDapi.c line 12623 in HE5_GDdetach(): Checking for grid ID failed.
>>
>> major: Invalid arguments to routine
>> minor: Out of range
> 
> The problem seems to be the type conversion functions in EHapi.c. For
> instance:
> 
> long
> HE5_EHhid2long(hid_t invalue)
> {
>   long  outvalue = FAIL;
> 
>   if (sizeof(hid_t) == sizeof(int))
> outvalue = HE5_EHint2long(invalue);
>   else if (sizeof(hid_t) == sizeof(long))
> outvalue = invalue;
> 
>   return(outvalue);
> }
> 
> On 32 bit archs:
>   sizeof(hid_t) != sizeof(int)
>   sizeof(hid_t) != sizeof(long)
>   sizeof(hid_t) == sizeof(long long)
> 
> The conversion functions should be adapted accordingly.

I've filed #846853 against src:hdf-eos5. There are issues in
ruby-hdfeos5 as well. See the attached patch.

With these fixes the ruby-hdfeos5 testsuite passes on 64 bit and 32 bit
arches.

Thanks,

_g.
diff -Nru ruby-hdfeos5-1.2/debian/changelog ruby-hdfeos5-1.2/debian/changelog
--- ruby-hdfeos5-1.2/debian/changelog   2016-03-01 10:16:48.0 +0100
+++ ruby-hdfeos5-1.2/debian/changelog   2016-12-03 18:55:27.0 +0100
@@ -1,3 +1,10 @@
+ruby-hdfeos5 (1.2-6.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Fix FTBFS on 32 bi architectures against hdf5 1.10 (closes: #846353)
+
+ -- Gilles Filippini   Sat, 03 Dec 2016 18:55:27 +0100
+
 ruby-hdfeos5 (1.2-6) unstable; urgency=medium
 
   * Remove dbg package
diff -Nru ruby-hdfeos5-1.2/debian/patches/hid_t.patch 
ruby-hdfeos5-1.2/debian/patches/hid_t.patch
--- ruby-hdfeos5-1.2/debian/patches/hid_t.patch 1970-01-01 01:00:00.0 
+0100
+++ ruby-hdfeos5-1.2/debian/patches/hid_t.patch 2016-12-03 15:23:32.0 
+0100
@@ -0,0 +1,142 @@
+Index: ruby-hdfeos5-1.2/hdfeos5gd_wrap.c
+===
+--- ruby-hdfeos5-1.2.orig/hdfeos5gd_wrap.c
 ruby-hdfeos5-1.2/hdfeos5gd_wrap.c
+@@ -20,7 +20,7 @@
+ #endif
+ 
+ extern int   check_numbertype(char *);
+-extern int   change_numbertype(char *);
++extern hid_t change_numbertype(char *);
+ extern int   change_entrycode(char *);
+ extern int   change_projcode(char *);
+ extern int   change_compmethod(char *);
+@@ -1327,7 +1327,7 @@ hdfeos5_gdinqfields(VALUE mod, VALUE ent
+  
+ i_count = (int)o_nflds;
+ rank = hdfeos5_cintary2obj(o_rank, i_count, 1, _count);
+-ntype = hdfeos5_cintary2obj(o_ntype, i_count, 1, _count);
++ntype = hdfeos5_cunsint64ary2obj(o_ntype, i_count, 1, _count);
+ 
+ return rb_ary_new3(4, nflds, fieldlist, rank, ntype);
+ }
+@@ -1905,12 +1905,12 @@ hdfeos5_gdsetextdata(VALUE mod, VALUE fi
+   size = rb_Array(size);
+ 

Processed: Re: Bug#846353: FTBFS: ERROR: Test "ruby2.3" failed. Exiting.

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 846853
Bug #846353 [ruby-hdfeos5] FTBFS: ERROR: Test "ruby2.3" failed. Exiting.
846353 was not blocked by any bugs.
846353 was not blocking any bugs.
Added blocking bug(s) of 846353: 846853
> tags -1 + patch
Bug #846353 [ruby-hdfeos5] FTBFS: ERROR: Test "ruby2.3" failed. Exiting.
Added tag(s) patch.

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

Bug#844818: marked as done (networking-mlnx: FTBFS: build-dependency not installable: python-neutron (>= 2:9.0.0~rc1))

[Debian Bug Tracking System]

Your message dated Sat, 3 Dec 2016 19:16:00 +0100
with message-id <7447f5da-9334-3baa-84eb-96aa95a0c...@goirand.fr>
and subject line Fixed
has caused the Debian Bug report #844818,
regarding networking-mlnx: FTBFS: build-dependency not installable: 
python-neutron (>= 2:9.0.0~rc1)
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.)


-- 
844818: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844818
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: networking-mlnx
Version: 1:9.0.0~b1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dh-python, dh-systemd, 
> openstack-pkg-tools (>= 52~), po-debconf, python-all, python-pbr (>= 0.11), 
> python-sphinx, python-babel, python-cliff (>= 1.15.0), python-coverage, 
> python-ddt (>= 1.0.1), python-ethtool, python-fixtures (>= 1.3.1), 
> python-hacking, python-lxml, python-mock (>= 1.3), python-neutron (>= 
> 2:9.0.0~rc1), python-oslosphinx (>= 2.5.0), python-oslotest (>= 1:1.5.1), 
> python-os-testr (>= 0.4.1), python-psycopg2, python-pymysql, 
> python-requests-mock (>= 0.7.0), python-tempest-lib (>= 0.13.0), 
> python-testresources, python-testscenarios, python-testtools (>= 1.4.0), 
> python-webtest (>= 2.0), python-zmq, subunit (>= 0.0.18), testrepository (>= 
> 0.0.18)
> Filtered Build-Depends: debhelper (>= 9), dh-python, dh-systemd, 
> openstack-pkg-tools (>= 52~), po-debconf, python-all, python-pbr (>= 0.11), 
> python-sphinx, python-babel, python-cliff (>= 1.15.0), python-coverage, 
> python-ddt (>= 1.0.1), python-ethtool, python-fixtures (>= 1.3.1), 
> python-hacking, python-lxml, python-mock (>= 1.3), python-neutron (>= 
> 2:9.0.0~rc1), python-oslosphinx (>= 2.5.0), python-oslotest (>= 1:1.5.1), 
> python-os-testr (>= 0.4.1), python-psycopg2, python-pymysql, 
> python-requests-mock (>= 0.7.0), python-tempest-lib (>= 0.13.0), 
> python-testresources, python-testscenarios, python-testtools (>= 1.4.0), 
> python-webtest (>= 2.0), python-zmq, subunit (>= 0.0.18), testrepository (>= 
> 0.0.18)
> dpkg-deb: building package 'sbuild-build-depends-networking-mlnx-dummy' in 
> '/<>/resolver-mNH6jQ/apt_archive/sbuild-build-depends-networking-mlnx-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-networking-mlnx-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-mNH6jQ/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-mNH6jQ/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-mNH6jQ/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-mNH6jQ/apt_archive ./ Sources [620 B]
> Get:5 copy:/<>/resolver-mNH6jQ/apt_archive ./ Packages [703 B]
> Fetched 2286 B in 0s (210 kB/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install networking-mlnx build dependencies (apt-based resolver)
> ---
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-networking-mlnx-dummy : Depends: python-neutron (>= 
> 2:9.0.0~rc1) but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/networking-mlnx_9.0.0~b1-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 

Bug#844805: marked as done (networking-ovn: FTBFS: unsatisfiable build-dependencies: python-neutron (>= 2:9.0.0), python-neutron-lib (>= 0.4.0))

[Debian Bug Tracking System]

Your message dated Sat, 3 Dec 2016 19:16:16 +0100
with message-id <276f1e23-f2ac-ae60-9712-ee2b61488...@goirand.fr>
and subject line Fixed
has caused the Debian Bug report #844805,
regarding networking-ovn: FTBFS: unsatisfiable build-dependencies: 
python-neutron (>= 2:9.0.0), python-neutron-lib (>= 0.4.0)
to be marked as done.

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

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


-- 
844805: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844805
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: networking-ovn
Version: 1.0.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dh-python, openstack-pkg-tools, 
> python-all, python-pbr, python-setuptools, python-sphinx, python-babel (>= 
> 2.3.4), python-coverage (>= 3.6), python-hacking, python-netaddr (>= 0.7.13), 
> python-neutron (>= 2:9.0.0), python-neutron-lib (>= 0.4.0), python-os-testr 
> (>= 0.7.0), python-oslo.config (>= 1:3.14.0), python-oslosphinx (>= 2.5.0), 
> python-oslotest (>= 1:1.10.0), python-openvswitch (>= 2.5.0), python-reno, 
> python-retrying (>= 1.2.3), python-six (>= 1.9.0), python-testresources (>= 
> 0.2.4), python-testscenarios (>= 0.4), python-testtools (>= 1.4.0), 
> python-webtest (>= 2.0), subunit (>= 0.0.18), testrepository (>= 0.0.18)
> Filtered Build-Depends: debhelper (>= 9), dh-python, openstack-pkg-tools, 
> python-all, python-pbr, python-setuptools, python-sphinx, python-babel (>= 
> 2.3.4), python-coverage (>= 3.6), python-hacking, python-netaddr (>= 0.7.13), 
> python-neutron (>= 2:9.0.0), python-neutron-lib (>= 0.4.0), python-os-testr 
> (>= 0.7.0), python-oslo.config (>= 1:3.14.0), python-oslosphinx (>= 2.5.0), 
> python-oslotest (>= 1:1.10.0), python-openvswitch (>= 2.5.0), python-reno, 
> python-retrying (>= 1.2.3), python-six (>= 1.9.0), python-testresources (>= 
> 0.2.4), python-testscenarios (>= 0.4), python-testtools (>= 1.4.0), 
> python-webtest (>= 2.0), subunit (>= 0.0.18), testrepository (>= 0.0.18)
> dpkg-deb: building package 'sbuild-build-depends-networking-ovn-dummy' in 
> '/<>/resolver-bmfO3a/apt_archive/sbuild-build-depends-networking-ovn-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-networking-ovn-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-bmfO3a/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-bmfO3a/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-bmfO3a/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-bmfO3a/apt_archive ./ Sources [591 B]
> Get:5 copy:/<>/resolver-bmfO3a/apt_archive ./ Packages [675 B]
> Fetched 2229 B in 0s (0 B/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install networking-ovn build dependencies (apt-based resolver)
> --
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-networking-ovn-dummy : Depends: python-neutron (>= 
> 2:9.0.0) but it is not going to be installed
>  Depends: python-neutron-lib (>= 
> 0.4.0) but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/networking-ovn_1.0.0-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 

Processed: Re: Bug#846816: java.lang.NoSuchFieldError: DLU2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + confirmed
Bug #846816 [freeplane] java.lang.NoSuchFieldError: DLU2
Added tag(s) confirmed.

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

Bug#846816: java.lang.NoSuchFieldError: DLU2

[gregor herrmann]

Control: tag -1 + confirmed

On Sat, 03 Dec 2016 14:50:40 +0100, Vincent Smeets wrote:

> Package: freeplane
> Version: 1.5.16-2
> Severity: grave
> Justification: renders package unusable

> Here I started freeplane from the command line. It shows you the log
> output and the raised exception.

> STDERR: Exception in thread "AWT-EventQueue-1" 
> STDERR: java.lang.NoSuchFieldError: DLU2

Thanks for your bug report. I can reproduce it (on unstable).

> -- Package-specific info:
> ii  freeplane   1.5.16-2   allJava 
> program for working with Mind Maps

> Versions of packages freeplane depends on:
> ii  libjgoodies-forms-java   1.9.0-3

Looks like we missed a part when creating the patch for
jgoodies-forms 1.9.0 compatibility ...


I get past this error with

+--- 
a/freeplane/src/main/java/org/freeplane/features/styles/mindmapmode/StyleEditorPanel.java
 
b/freeplane/src/main/java/org/freeplane/features/styles/mindmapmode/StyleEditorPanel.java
+@@ -113,8 +113,8 @@
+ import org.freeplane.features.ui.IMapViewManager;
+ 
+ import com.jgoodies.forms.builder.DefaultFormBuilder;
+-import com.jgoodies.forms.factories.Borders;
+-import com.jgoodies.forms.layout.FormLayout;
++import com.jgoodies.forms.factories.*;
++import com.jgoodies.forms.layout.*;
+ 
+ public class StyleEditorPanel extends JPanel {
+   private static final int FONT_SIZE = 
Math.round(UITools.FONT_SCALE_FACTOR * 8);
+@@ -842,7 +842,7 @@
+   final String form = "right:max(20dlu;p), 2dlu, p, 
1dlu,right:max(20dlu;p), 4dlu, 80dlu, 7dlu";
+   final FormLayout rightLayout = new FormLayout(form, "");
+   final DefaultFormBuilder rightBuilder = new 
DefaultFormBuilder(rightLayout);
+-  rightBuilder.border(Borders.DLU2);
++  rightBuilder.border(Paddings.DLU2);
+   new 
SeparatorProperty("OptionPanel.separator.NodeStyle").layout(rightBuilder);
+   if (addStyleBox) {
+   addAutomaticLayout(rightBuilder);


added to debian/patches/50_jgoodies-1.9.patch, but when starting
freeplane I then only see an empty white windows.

But I guess that's no hard problem to fix for someone who knows Java :)


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Joan Baez: Silver Dagger


signature.asc
Description: Digital Signature

Bug#846853: hdf-eos5: Unusable on 32 bit arches - Makes ruby-hdfeos5 FTBFS

[Gilles Filippini]

Source: hdf-eos5
Version: 5.1.15.dfsg.1-8
Severity: serious
Tags: patch
Justification: Makes other package FTBFS

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,

Since HDF5 1.10 has landed into unstable, hdf-eos5 is mostly unusable on 32 bit 
arches, and makes ruby-hdfeos5 FTBFS.
This is due to the hid_t type change from int to uint64_t. Please see the 
attached patch which fixes most issues.

Note that it doesn't fix everything: the Fortran bindings passing hid_t as INT 
need to be fixed as well.

I've successfuly tested this patch against the ruby_hdfeos5 testsuite, both on 
64 bit and 32 bit arches.

Because this bug is in the way of the HDF5 1.10 transition, I intend to NMU 
very soon, unless you tell me otherwise.

Thanks,

_g.

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

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

-BEGIN PGP SIGNATURE-

iQEcBAEBCAAGBQJYQwQXAAoJEO/obGx//s+DlAEH/jZZ8NRHOp2tVmNYwzM0D+/t
CAt70MYixBcUeHbn/Ok9t6LWCGM/UaP2pyH8OK0IYRrrogd77u7l0vcq+EOsl385
fwlsTH9tYb5FkbJRF9i8Til1LOjOQCe0e2IbYZxN3d90O7ivxG87b1Az+QiR0Rzk
UY2+VLfbeDmOdyIkxpCXZpih84UJaah+TMNWc/ZcRE/ACchjMMsoClwQdTzXTBlO
fVVb71QyTL+C+u127QugPGaRsgfQSy0zwFuGlnuuyUyyz1PqMOtW+4VSJFPMZZiT
kHs0HAmRGCx9fKBkVggrSCjz/p83NxwJv1fX0/xdi4CkVXwR873kAU5NqQtQEGc=
=ouVH
-END PGP SIGNATURE-
diff -Nru hdf-eos5-5.1.15.dfsg.1/debian/changelog hdf-eos5-5.1.15.dfsg.1/debian/changelog
--- hdf-eos5-5.1.15.dfsg.1/debian/changelog	2016-06-20 23:05:34.0 +0200
+++ hdf-eos5-5.1.15.dfsg.1/debian/changelog	2016-12-03 01:48:32.0 +0100
@@ -1,3 +1,10 @@
+hdf-eos5 (5.1.15.dfsg.1-8.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * New patch hid_t.patch: hid_t isn't native int anymore
+
+ -- Gilles Filippini   Sat, 03 Dec 2016 01:48:32 +0100
+
 hdf-eos5 (5.1.15.dfsg.1-8) unstable; urgency=medium
 
   * Patch to build against hdf5-1.10.1: use hid_t not int (hid_t == int64_t
diff -Nru hdf-eos5-5.1.15.dfsg.1/debian/patches/hid_t.patch hdf-eos5-5.1.15.dfsg.1/debian/patches/hid_t.patch
--- hdf-eos5-5.1.15.dfsg.1/debian/patches/hid_t.patch	1970-01-01 01:00:00.0 +0100
+++ hdf-eos5-5.1.15.dfsg.1/debian/patches/hid_t.patch	2016-12-03 01:48:32.0 +0100
@@ -0,0 +1,682 @@
+Index: hdf-eos5-5.1.15.dfsg.1/src/EHapi.c
+===
+--- hdf-eos5-5.1.15.dfsg.1.orig/src/EHapi.c
 hdf-eos5-5.1.15.dfsg.1/src/EHapi.c
+@@ -314,6 +314,8 @@ HE5_EHhid2long(hid_t invalue)
+ 	outvalue = HE5_EHint2long(invalue);
+   else if (sizeof(hid_t) == sizeof(long))
+ 	outvalue = invalue;
++  else if (sizeof(hid_t) == sizeof(long long))
++	outvalue = HE5_EHllong2long(invalue);
+   
+   return(outvalue);
+ }
+@@ -399,6 +401,8 @@ HE5_EHhid2int(hid_t invalue)
+ 	outvalue = invalue;
+   else if (sizeof(hid_t) == sizeof(long))
+ 	outvalue = HE5_EHlong2int(invalue);
++  else if (sizeof(hid_t) == sizeof(long long))
++	outvalue = HE5_EHllong2int(invalue);
+   
+   return(outvalue);
+ }
+@@ -436,6 +440,8 @@ HE5_EHint2hid(int invalue)
+ 	outvalue = invalue;
+   else if (sizeof(hid_t) == sizeof(long))
+ 	outvalue = HE5_EHint2long(invalue);
++  else if (sizeof(hid_t) == sizeof(long long))
++	outvalue = HE5_EHint2llong(invalue);
+   
+   return(outvalue);
+ }
+@@ -474,6 +480,8 @@ HE5_EHlong2hid(long invalue)
+ 	outvalue = HE5_EHlong2int(invalue);
+   else if (sizeof(hid_t) == sizeof(long))
+ 	outvalue = invalue;
++  else if (sizeof(hid_t) == sizeof(long long))
++	outvalue = HE5_EHlong2llong(invalue);
+   
+   return(outvalue);
+ }
+@@ -565,6 +573,8 @@ HE5_EHhid2hsize(hid_t invalue)
+ 	outvalue = HE5_EHint2hsize(invalue);
+   else if (sizeof(hid_t) == sizeof(long) )
+ 	outvalue = HE5_EHlong2hsize(invalue);
++  else if (sizeof(hid_t) == sizeof(long long))
++	outvalue = HE5_EHllong2hsize(invalue);
+ 
+   return(outvalue);  
+ }
+@@ -717,6 +727,8 @@ HE5_EHhsize2hid(hsize_t invalue)
+ 	outvalue = HE5_EHhsize2int(invalue);
+   else if (sizeof(hid_t) == sizeof(long) )
+ 	outvalue = HE5_EHhsize2long(invalue);
++  else if (sizeof(hid_t) == sizeof(long long))
++	outvalue = HE5_EHhsize2llong(invalue);
+ 
+   return(outvalue);
+ }
+@@ -866,6 +878,8 @@ HE5_EHhid2hssize(hid_t invalue)
+ 	outvalue = HE5_EHint2hssize(invalue);
+   else if (sizeof(hid_t) == sizeof(long) )
+ 	outvalue = HE5_EHlong2hssize(invalue);
++  else if (sizeof(hid_t) == sizeof(long long))
++	outvalue = HE5_EHllong2hssize(invalue);
+ 
+   return(outvalue);
+ }
+@@ -1016,6 +1030,8 @@ HE5_EHhssize2hid(hssize_t invalue)
+ 	outvalue = HE5_EHhssize2int(invalue);
+   else if (sizeof(hid_t) == sizeof(long) )
+ 	outvalue = HE5_EHhssize2long(invalue);
++  else if (sizeof(hid_t) == sizeof(long long))
++	outvalue = HE5_EHhssize2llong(invalue);
+   
+   return(outvalue);  
+ }

Bug#845737: mark as forwarded

[Ghislain Vaillant]

control: forwarded -1 https://bitbucket.org/snakemake/snakemake/issues/
426/random-test-hangs-during-debian-package

Processed: mark as forwarded

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://bitbucket.org/snakemake/snakemake/issues/
Bug #845737 [src:snakemake] snakemake: FTBFS randomly (sbuild hangs)
Set Bug forwarded-to-address to 
'https://bitbucket.org/snakemake/snakemake/issues/'.

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

Processed (with 1 error): forcibly merging 835804 828415

[Debian Bug Tracking System]

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

> forcemerge 835804 828415
Bug #835804 {Done: k...@roeckx.be (Kurt Roeckx)} [src:boost1.61] websocketpp: 
FTBFS with openssl 1.1.0
Unable to merge bugs because:
package of #828415 is 'src:libtorrent-rasterbar' not 'src:boost1.61'
Failed to forcibly merge 835804: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#846667: libpoe-loop-event-perl: FTBFS: Test failures

[gregor herrmann]

On Sat, 03 Dec 2016 08:43:03 +0100, Lucas Nussbaum wrote:

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

> > Test Summary Report
> > ---
> > t/poe_loop_event/wheel_run.t   (Wstat: 256 Tests: 99 
> > Failed: 1)
> >   Failed test:  98
> >   Non-zero exit status: 1
> >   Parse errors: Bad plan.  You planned 103 tests but ran 99.
> > Files=36, Tests=476, 73 wallclock secs ( 0.17 usr  0.04 sys +  3.56 cusr  
> > 0.32 csys =  4.09 CPU)
> > Result: FAIL
> > Failed 1/36 test programs. 1/476 subtests failed.
> > Makefile:837: recipe for target 'test_dynamic' failed

I can't reproduce this in a quick build+autopkgtest. But there's one
failure on reproducible-builds (among 5 successes):

https://tests.reproducible-builds.org/debian/rbuild/testing/amd64/libpoe-loop-event-perl_1.305-1.rbuild.log

Test Summary Report
---
t/poe_loop_event/wheel_run.t   (Wstat: 5632 Tests: 18 Failed: 6)
  Failed tests:  10-12, 16-18
  Non-zero exit status: 22
  Parse errors: Bad plan.  You planned 103 tests but ran 18.
t/poe_loop_event/z_leolo_wheel_run.t   (Wstat: 5632 Tests: 13 Failed: 
12)
  Failed tests:  2-13
  Non-zero exit status: 22
  Parse errors: Bad plan.  You planned 14 tests but ran 13.
Files=36, Tests=394, 32 wallclock secs ( 0.22 usr  0.11 sys +  6.82 cusr  1.05 
csys =  8.20 CPU)
Result: FAIL
Failed 2/36 test programs. 18/394 subtests failed.
Makefile:837: recipe for target 'test_dynamic' failed


And a few failures on CPAN testers, e.g.
http://www.cpantesters.org/cpan/report/07dcab5c-95aa-11e6-bdb5-917d28376f48


Test Summary Report
---
t/poe_loop_event/wheel_run.t   (Wstat: 256 Tests: 99 Failed: 0)
  Non-zero exit status: 1
  Parse errors: Bad plan.  You planned 103 tests but ran 99.
Files=36, Tests=486, 59 wallclock secs ( 0.12 usr  0.15 sys + 45.36 cusr 10.19 
csys = 55.82 CPU)
Result: FAIL
Failed 1/36 test programs. 0/486 subtests failed.
Makefile:863: recipe for target 'test_dynamic' failed


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: U2: Luminous Times (Hold On To Love)


signature.asc
Description: Digital Signature

Bug#846843: Ulogd creates log directory, log files world readable by default

[halfdog]

Package: ulogd2
Version: 2.0.4-2+deb8u1
Severity: serious
Tags: security

After a fresh install of ulogd2, logging directory has following
permissions:

# ls -al /var/log/ulog
total 8
drwxr-xr-x  2 root root 4096 Dec  3 16:22 .
drwxr-xr-x 10 root root 4096 Dec  3 16:22 ..
-rw-r--r--  1 root root0 Dec  3 16:22 syslogemu.log

Depending on packets logged, users on machine may gain much more
information than available via /proc/[pid] - which would be just
the remote address of TCP connections. This is especially annoying
when ulogd is used to create full packet captures of some connections
as recommended in howtos.

As ulogd is started with UID=0 and drops permissions, I would
recommend changing default permissions for directory to 0700 and
0600 for files. For rare scenarios, where users would really need
to let another software read that data, permissions should be changed
on those machines only. 

Bug#846684: marked as done (ocrmypdf: FTBFS: Test failures)

[Debian Bug Tracking System]

Your message dated Sat, 03 Dec 2016 17:03:44 +
with message-id 
and subject line Bug#846684: fixed in ocrmypdf 4.3.3-1
has caused the Debian Bug report #846684,
regarding ocrmypdf: FTBFS: Test failures
to be marked as done.

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

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


-- 
846684: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846684
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ocrmypdf
Version: 4.3.2-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161202 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):
> E+  where 4 = .returncode
> 
> tests/test_main.py:68: AssertionError
> - Captured stdout call 
> -
> stdout
> ==
> 
> stderr
> ==
> WARNING -1: [tesseract]  took too long to OCR - skipping
> GPL Ghostscript 9.20: Setting Overprint Mode to 1
>  not permitted in PDF/A-2, reverting to normal PDF output
> WARNING - Output file is okay but is not PDF/A (seems to be No XMP metadata)
> 
> == 43 failed, 36 passed, 2 skipped in 447.67 seconds 
> ===
> debian/rules:44: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/12/02/ocrmypdf_4.3.2-2_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: ocrmypdf
Source-Version: 4.3.3-1

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

Debian distribution maintenance software
pp.
Sean Whitton  (supplier of updated ocrmypdf package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 03 Dec 2016 08:30:51 -0700
Source: ocrmypdf
Binary: ocrmypdf ocrmypdf-doc
Architecture: all source
Version: 4.3.3-1
Distribution: unstable
Urgency: medium
Maintainer: Sean Whitton 
Changed-By: Sean Whitton 
Closes: 846684
Description: 
 ocrmypdf   - add an OCR text layer to PDF files
 ocrmypdf-doc - add an OCR text layer to PDF files - documentation
Changes:
 ocrmypdf (4.3.3-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #846684).
   * Refresh patch-docs-for-Debian.patch.
Checksums-Sha1: 
 bbf8b623f194bbea09b89a59a96e72a0d76db1c1 2424 ocrmypdf_4.3.3-1.dsc
 90697a9933d13c9cbafebad3df4b8b37dc3a7fc6 5826496 ocrmypdf_4.3.3.orig.tar.xz
 717a33a9e52cea65435fa56b3abf27abd427f724 17864 ocrmypdf_4.3.3-1.debian.tar.xz
 bcecb1b0613ce1768baf5736d2d760af1f31cbac 50832 ocrmypdf-doc_4.3.3-1_all.deb
 0c2b0a2ff119e7c7494d474397d4688fb6430652 55316 ocrmypdf_4.3.3-1_all.deb
 50a1a3588f4c72783575a98fbb66a5d7e5409d10 9754 ocrmypdf_4.3.3-1_i386.buildinfo
Checksums-Sha256: 
 ad90736b0a293ce1de4802e0a4abd1007f058a7dea55637fa2ffa0f667cafe0f 2424 
ocrmypdf_4.3.3-1.dsc
 cd0dbafacd61ce74da737b9c504d2c167f075b3276cb54147e4a7376e34a51a1 5826496 
ocrmypdf_4.3.3.orig.tar.xz
 6f271a5445e507411670100274caf8ab532e17382e56b325bf1c82b39049a48a 17864 
ocrmypdf_4.3.3-1.debian.tar.xz
 70655e7dc3363babfa65bb1a317803ccc72e829e33631c553a17155de02c5855 50832 
ocrmypdf-doc_4.3.3-1_all.deb
 7e5006f6611ab2457a2c7cce75b087ebc9a74be53290bd56b670e0a721ac2726 55316 
ocrmypdf_4.3.3-1_all.deb
 7532e0399856740de3dd317ab6bcee66b2c09efdbc5d65b46f9145066fc62a31 9754 
ocrmypdf_4.3.3-1_i386.buildinfo
Files: 
 baa34225ccc81a077f326d4cfb643395 2424 graphics optional ocrmypdf_4.3.3-1.dsc
 e0a8a694cb1aaa967064910f98e1ec85 5826496 graphics optional 
ocrmypdf_4.3.3.orig.tar.xz
 7004c28d31b91054a6f62e50f429dded 17864 graphics optional 
ocrmypdf_4.3.3-1.debian.tar.xz
 

Bug#846566: marked as done (education-menus: ships /usr/share/desktop-directories/Graphics.directory, already in gnome-menus)

[Debian Bug Tracking System]

Your message dated Sat, 03 Dec 2016 17:00:15 +
with message-id 
and subject line Bug#846566: fixed in debian-edu 1.916
has caused the Debian Bug report #846566,
regarding education-menus: ships 
/usr/share/desktop-directories/Graphics.directory, already in gnome-menus
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.)


-- 
846566: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846566
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: education-menus
Version: 1.915
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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

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

  Selecting previously unselected package education-menus.
  Preparing to unpack .../1-education-menus_1.915_amd64.deb ...
  Unpacking education-menus (1.915) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-c9re87/1-education-menus_1.915_amd64.deb (--unpack):
   trying to overwrite '/usr/share/desktop-directories/Graphics.directory', 
which is also in package gnome-menus 3.13.3-8
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-c9re87/1-education-menus_1.915_amd64.deb


cheers,

Andreas


gnome-menus=3.13.3-8_education-menus=1.915.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: debian-edu
Source-Version: 1.916

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

Debian distribution maintenance software
pp.
Holger Levsen  (supplier of updated debian-edu package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 03 Dec 2016 14:54:53 +0100
Source: debian-edu
Binary: education-tasks education-menus education-thin-client-server 
education-astronomy education-chemistry education-common 
education-desktop-gnome education-desktop-kde education-desktop-lxde 
education-desktop-mate education-desktop-other education-desktop-xfce 
education-development education-electronics education-geography 
education-graphics education-lang-da education-lang-da-desktop 
education-lang-da-desktop-kde education-lang-de education-lang-de-desktop 
education-lang-de-desktop-kde education-lang-es education-lang-es-desktop 
education-lang-es-desktop-kde education-lang-fr education-lang-fr-desktop 
education-lang-fr-desktop-kde education-lang-he education-lang-he-desktop 
education-lang-he-desktop-kde education-lang-it education-lang-it-desktop 
education-lang-it-desktop-kde education-lang-ja education-lang-ja-desktop 
education-lang-ja-desktop-kde education-lang-no education-lang-no-desktop 
education-lang-no-desktop-kde education-lang-se education-lang-zh-tw
 education-lang-zh-tw-desktop education-lang-zh-tw-desktop-kde 
education-language education-laptop education-logic-games education-ltsp-server 
education-main-server education-mathematics education-misc education-music 
education-networked education-networked-common education-physics 
education-roaming-workstation education-services education-standalone 
education-thin-client
 education-workstation
Architecture: source amd64 all
Version: 1.916
Distribution: unstable
Urgency: medium
Maintainer: Debian Edu Developers 
Changed-By: Holger Levsen 
Description:
 education-astronomy - Debian Edu astronomy related applications
 education-chemistry - Debian Edu chemistry related applications
 education-common - Debian Edu common packages
 education-desktop-gnome - Debian Edu GNOME desktop applications
 education-desktop-kde - Debian Edu KDE desktop applications
 education-desktop-lxde - Debian Edu LXDE desktop applications
 education-desktop-mate - Debian Edu MATE desktop applications
 education-desktop-other - Debian Edu non-GNOME- and non-KDE-specific desktop 
applications
 

Bug#793895: marked as done (netperf: FTBFS with -Werror=format-security)

[Debian Bug Tracking System]

Your message dated Sat, 03 Dec 2016 17:53:20 +0100
with message-id <1480784000.1964.2.ca...@debian.org>
and subject line Re: netperf: FTBFS with -Werror=format-security
has caused the Debian Bug report #793895,
regarding netperf: FTBFS with -Werror=format-security
to be marked as done.

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

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


-- 
793895: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793895
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: netperf
Version: 2.4.4-6.1
Severity: serious
Tags: wheezy
Justification: fails to build from source (but built successfully in the past)
Control: fixed -1 2.6.0-2

netperf (from wheezy) FTBFS in a minimal pbuilder wheezy chroot
due to -Werror=format-security.
The version from jessie+ builds fine in jessie+.

[...]
make[4]: Entering directory `/tmp/buildd/netperf-2.4.4/src'
gcc -DHAVE_CONFIG_H -I. -I. -I..   -D_FORTIFY_SOURCE=2  -g -O2 
-fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security 
-Wall -c `test -f 'netperf.c' || echo './'`netperf.c
netperf.c: In function 'main':
netperf.c:148:5: warning: implicit declaration of function 'send_tcp_mss' 
[-Wimplicit-function-declaration]
gcc -DHAVE_CONFIG_H -I. -I. -I..   -D_FORTIFY_SOURCE=2  -g -O2 
-fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security 
-Wall -c `test -f 'netlib.c' || echo './'`netlib.c
netlib.c: In function 'allocate_buffer_ring':
netlib.c:1256:52: warning: format '%u' expects argument of type 'unsigned int', 
but argument 2 has type 'long unsigned int' [-Wformat]
netlib.c: In function 'alloc_sendfile_buf_ring':
netlib.c:1630:52: warning: format '%u' expects argument of type 'unsigned int', 
but argument 2 has type 'long unsigned int' [-Wformat]
netlib.c: In function 'bind_to_specific_processor':
netlib.c:2015:5: warning: implicit declaration of function 'sched_setaffinity' 
[-Wimplicit-function-declaration]
netlib.c: In function 'send_request':
netlib.c:2154:13: warning: format '%u' expects argument of type 'unsigned int', 
but argument 3 has type 'long unsigned int' [-Wformat]
netlib.c: In function 'send_response':
netlib.c:2192:13: warning: format '%u' expects argument of type 'unsigned int', 
but argument 3 has type 'long unsigned int' [-Wformat]
netlib.c:2213:13: warning: format '%u' expects argument of type 'unsigned int', 
but argument 3 has type 'long unsigned int' [-Wformat]
gcc -DHAVE_CONFIG_H -I. -I. -I..   -D_FORTIFY_SOURCE=2  -g -O2 
-fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security 
-Wall -c `test -f 'netsh.c' || echo './'`netsh.c
netsh.c: In function 'scan_cmd_line':
netsh.c:476:5: warning: format '%d' expects argument of type 'int', but 
argument 2 has type 'size_t' [-Wformat]
gcc -DHAVE_CONFIG_H -I. -I. -I..   -D_FORTIFY_SOURCE=2  -g -O2 
-fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security 
-Wall -c `test -f 'nettest_bsd.c' || echo './'`nettest_bsd.c
nettest_bsd.c: In function 'print_top_test_header':
nettest_bsd.c:1172:3: error: format not a string literal and no format 
arguments [-Werror=format-security]
nettest_bsd.c: In function 'send_tcp_mss':
nettest_bsd.c:2821:3: error: format not a string literal and no format 
arguments [-Werror=format-security]
nettest_bsd.c:2669:37: warning: variable 'tcp_stream_result' set but not used 
[-Wunused-but-set-variable]
nettest_bsd.c: In function 'send_tcp_rr':
nettest_bsd.c:5191:10: warning: variable 'bytes_xferd' set but not used 
[-Wunused-but-set-variable]
nettest_bsd.c:5161:9: warning: unused variable 'cpu_title_latency' 
[-Wunused-variable]
nettest_bsd.c:5135:9: warning: unused variable 'tput_title_latency' 
[-Wunused-variable]
nettest_bsd.c: In function 'send_udp_rr':
nettest_bsd.c:6858:7: warning: variable 'bytes_xferd' set but not used 
[-Wunused-but-set-variable]
nettest_bsd.c: In function 'send_tcp_conn_rr':
nettest_bsd.c:8245:10: warning: variable 'thruput' set but not used 
[-Wunused-but-set-variable]
nettest_bsd.c:8227:9: warning: variable 'timed_out' set but not used 
[-Wunused-but-set-variable]
nettest_bsd.c: In function 'send_tcp_cc':
nettest_bsd.c:11424:10: warning: variable 'thruput' set but not used 
[-Wunused-but-set-variable]
nettest_bsd.c:11409:9: warning: variable 'timed_out' set but not used 
[-Wunused-but-set-variable]
nettest_bsd.c: In function 'recv_tcp_cc':
nettest_bsd.c:11952:9: warning: variable 'send_message_ptr' set but not used 
[-Wunused-but-set-variable]
nettest_bsd.c:11951:9: warning: variable 'recv_message_ptr' set but not used 
[-Wunused-but-set-variable]
cc1: some warnings being treated as errors
make[4]: 

Bug#844936: marked as done (python-keystonemiddleware FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Sat, 3 Dec 2016 17:49:54 +0100
with message-id <7557ac28-f86c-c497-dc18-539450c01...@debian.org>
and subject line Problem was fixed by the upload of python-keystoneclient 
1:3.2.0-3
has caused the Debian Bug report #844936,
regarding python-keystonemiddleware FTBFS with openssl 1.1.0
to be marked as done.

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

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


-- 
844936: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844936
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-keystonemiddleware
Version: 4.9.0-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
>   File 
> "keystonemiddleware/tests/unit/auth_token/test_auth_token_middleware.py", 
> line 1344, in test_request_no_token_dummy
> [self.examples.SIGNED_TOKEN_SCOPED_HASH])
>   File "keystonemiddleware/auth_token/__init__.py", line 716, in 
> _validate_offline
> verified = self._cms_verify(token_data, inform)
>   File "keystonemiddleware/auth_token/__init__.py", line 768, in _cms_verify
> return verify()
>   File "keystonemiddleware/auth_token/__init__.py", line 765, in verify
> raise ksm_exceptions.InvalidToken(msg)
> keystonemiddleware.auth_token._exceptions.InvalidToken: Token authorization 
> failed
> 
> 
> --
> Ran 347 tests in 13.720s
> 
> FAILED (failures=2, skipped=3)
> debian/rules:26: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/python-keystonemiddleware_4.9.0-2_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 ---
The problem was in fact located in python-keystoneclient, and was fixed
by the upload of python-keystoneclient 1:3.2.0-3. Therefore, I'm closing
this bug.

Cheers,

Thomas Goirand (zigo)--- End Message ---

Processed: tagging 835909, tagging 845963, tagging 751896, tagging 803365

[Debian Bug Tracking System]

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

> tags 835909 + pending
Bug #835909 [wnpp] ITA: multistrap -- multiple repository bootstrap based on apt
Added tag(s) pending.
> tags 845963 + pending
Bug #845963 [multistrap] multistrap triest to feed "GPG keybox database version 
1" to apt
Added tag(s) pending.
> tags 751896 + pending
Bug #751896 [multistrap] multistrap: Paths with capital letters are lowercased
Added tag(s) pending.
> tags 803365 + pending
Bug #803365 [multistrap] multistrap fails when cwd contains white space
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: unittest++: diff for NMU version 1.4.0-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 812270 + pending
Bug #812270 [unittest++] unittest++: FTBFS with GCC 6: terminate called after 
throwing an instance
Added tag(s) pending.

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

Bug#812270: unittest++: diff for NMU version 1.4.0-3.1

[Andrey Rahmatullin]

Control: tags 812270 + pending

Dear maintainer,

I've prepared an NMU for unittest++ (versioned as 1.4.0-3.1) and
uploaded it to DELAYED/4. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
WBR, wRAR
diff -u unittest++-1.4.0/debian/changelog unittest++-1.4.0/debian/changelog
--- unittest++-1.4.0/debian/changelog
+++ unittest++-1.4.0/debian/changelog
@@ -1,3 +1,11 @@
+unittest++ (1.4.0-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with GCC6 by using -std=gnu++98 (Closes: #812270).
+  * Add explicit debian/source/format.
+
+ -- Andrey Rahmatullin   Sat, 03 Dec 2016 20:49:24 +0500
+
 unittest++ (1.4.0-3) unstable; urgency=low
 
   * Add missing 20_test_runner_bad_virtual_method_arg.dpatch to patches/00list
diff -u unittest++-1.4.0/debian/rules unittest++-1.4.0/debian/rules
--- unittest++-1.4.0/debian/rules
+++ unittest++-1.4.0/debian/rules
@@ -1,6 +1,8 @@
 #!/usr/bin/make -f
 # -*- makefile -*-
 
+DEB_CXXFLAGS_MAINT_APPEND = -std=gnu++98
+
 include /usr/share/cdbs/1/rules/debhelper.mk
 include /usr/share/cdbs/1/class/makefile.mk
 include /usr/share/cdbs/1/rules/dpatch.mk
only in patch2:
unchanged:
--- unittest++-1.4.0.orig/debian/source/format
+++ unittest++-1.4.0/debian/source/format
@@ -0,0 +1 @@
+1.0


signature.asc
Description: PGP signature

Processed: fb-music-high: diff for NMU version 0.1.2+nmu1

[Debian Bug Tracking System]

Processing control commands:

> tags 817450 + pending
Bug #817450 [src:fb-music-high] fb-music-high: Removal of debhelper compat 4
Added tag(s) pending.

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

Bug#817450: fb-music-high: diff for NMU version 0.1.2+nmu1

[Andrey Rahmatullin]

Control: tags 817450 + pending

Dear maintainer,

I've prepared an NMU for fb-music-high (versioned as 0.1.2+nmu1) and
uploaded it to DELAYED/4. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
WBR, wRAR
diff -Nru fb-music-high-0.1.2/debian/changelog fb-music-high-0.1.2+nmu1/debian/changelog
--- fb-music-high-0.1.2/debian/changelog	2006-10-27 04:45:11.0 +0600
+++ fb-music-high-0.1.2+nmu1/debian/changelog	2016-12-03 21:03:59.0 +0500
@@ -1,3 +1,20 @@
+fb-music-high (0.1.2+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Integrate changes from 0.1.2ubuntu1:
++ debian/rules: Convert to dh sequencer.
++ debian/compat: Indicate compatibility level of 9 (Closes: #817450).
++ debian/control:
+  - Build-depend on debhelper (>= 9).
+  - Depend on ${misc:Depends}.
+  - Move homepage to its own field.
++ debian/copyright: Don't point to symlink GPL.
+  * Bump debian/compat and the debhelper build-dep to 10.
+  * Create debian/source/format with '3.0 (native)'.
+  * Drop Conflicts against ancient frozen-bubble.
+
+ -- Andrey Rahmatullin   Sat, 03 Dec 2016 21:03:59 +0500
+
 fb-music-high (0.1.2) unstable; urgency=low
 
   * Remove two songs that now have ogg replacements in
diff -Nru fb-music-high-0.1.2/debian/compat fb-music-high-0.1.2+nmu1/debian/compat
--- fb-music-high-0.1.2/debian/compat	1970-01-01 05:00:00.0 +0500
+++ fb-music-high-0.1.2+nmu1/debian/compat	2016-12-03 21:03:59.0 +0500
@@ -0,0 +1 @@
+10
diff -Nru fb-music-high-0.1.2/debian/control fb-music-high-0.1.2+nmu1/debian/control
--- fb-music-high-0.1.2/debian/control	2006-10-27 04:45:01.0 +0600
+++ fb-music-high-0.1.2+nmu1/debian/control	2016-12-03 21:03:59.0 +0500
@@ -2,13 +2,15 @@
 Section: games
 Priority: extra
 Maintainer: Josselin Mouette 
-Build-Depends: debhelper (>= 4)
+Build-Depends: debhelper (>= 10)
 Standards-Version: 3.7.2
+Homepage: http://www.frozen-bubble.org/
 
 Package: fb-music-high
 Architecture: all
+Depends: ${misc:Depends}
 Recommends: frozen-bubble
-Conflicts: fb-music-low, frozen-bubble (<< 2)
+Conflicts: fb-music-low
 Description: High quality, large music files for Frozen-Bubble
  Frozen-Bubble is a clone of the popular "Puzzle Bobble" game, featuring
  100 single-player levels and a two-player mode.
@@ -16,5 +18,3 @@
  This package contains high quality music for Frozen-Bubble. The 16-bit
  samples used sound better than the 8-bit ones in fb-music-low, but are
  about twice as large.
- .
- URL: http://www.frozen-bubble.org/
diff -Nru fb-music-high-0.1.2/debian/copyright fb-music-high-0.1.2+nmu1/debian/copyright
--- fb-music-high-0.1.2/debian/copyright	2003-01-23 20:53:17.0 +0500
+++ fb-music-high-0.1.2+nmu1/debian/copyright	2016-12-03 21:01:12.0 +0500
@@ -10,4 +10,4 @@
 You are free to distribute this software under the terms of
 the GNU General Public License, version 2 or later.
 On Debian systems, the complete text of the GNU General Public
-License can be found in /usr/share/common-licenses/GPL file.
+License can be found in /usr/share/common-licenses/GPL-2 file.
diff -Nru fb-music-high-0.1.2/debian/rules fb-music-high-0.1.2+nmu1/debian/rules
--- fb-music-high-0.1.2/debian/rules	2003-01-23 20:55:01.0 +0500
+++ fb-music-high-0.1.2+nmu1/debian/rules	2016-12-03 21:01:12.0 +0500
@@ -1,43 +1,3 @@
 #!/usr/bin/make -f
-
-# Uncomment this to turn on verbose mode. 
-#export DH_VERBOSE=1
-
-# This is the debhelper compatability version to use.
-export DH_COMPAT=4
-
-build:
-	dh_testdir
-
-clean:
-	dh_testdir
-	dh_testroot
-	dh_clean
-
-install:
-	dh_testdir
-	dh_testroot
-	dh_install
-
-# Build architecture-independent files here.
-# Pass -i to all debhelper commands in this target to reduce clutter.
-binary-indep: build install
-	dh_testdir
-	dh_testroot
-	dh_installdocs
-	dh_installchangelogs
-	dh_installexamples
-	dh_link
-	dh_compress
-	dh_fixperms
-	dh_installdeb
-	dh_gencontrol
-	dh_md5sums
-	dh_builddeb
-
-# Build architecture-dependent files here.
-binary-arch: build install
-# We have nothing to do by default
-
-binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install
+%:
+	dh $@
diff -Nru fb-music-high-0.1.2/debian/source/format fb-music-high-0.1.2+nmu1/debian/source/format
--- fb-music-high-0.1.2/debian/source/format	1970-01-01 05:00:00.0 +0500
+++ fb-music-high-0.1.2+nmu1/debian/source/format	2016-12-03 21:03:59.0 +0500
@@ -0,0 +1 @@
+3.0 (native)


signature.asc
Description: PGP signature

Bug#846706: network-manager-openconnect: FTBFS: configure: error: Package requirements (openconnect >= 3.02) were not met

[Mike Miller]

Control: reassign -1 libopenconnect-dev
Control: affects -1 src:network-manager-openconnect

On Sat, Dec 03, 2016 at 08:24:04 +0100, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> 
> Relevant part (hopefully):
> > checking for GLIB... yes
> > checking for LIBXML... yes
> > checking for GTK... yes
> > checking for LIBSECRET... yes
> > checking for OPENCONNECT... no
> > configure: error: Package requirements (openconnect >= 3.02) were not met
> > 
> > Package 'liblz4', required by 'openconnect', not found
> > 
> > Consider adjusting the PKG_CONFIG_PATH environment variable if you
> > installed software in a non-standard prefix.
> > 
> > Alternatively, you may set the environment variables OPENCONNECT_CFLAGS
> > and OPENCONNECT_LIBS to avoid the need to call pkg-config.
> > See the pkg-config man page for more details.
> > "tail -v -n +0 config.log"

Ack, thank you. Not sure why this hasn't failed before. But actual bug
is that libopenconnect-dev needs Depends: liblz4-dev.

-- 
mike

Processed: Re: Bug#846706: network-manager-openconnect: FTBFS: configure: error: Package requirements (openconnect >= 3.02) were not met

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libopenconnect-dev
Bug #846706 [src:network-manager-openconnect] network-manager-openconnect: 
FTBFS: configure: error: Package requirements (openconnect >= 3.02) were not met
Bug reassigned from package 'src:network-manager-openconnect' to 
'libopenconnect-dev'.
No longer marked as found in versions network-manager-openconnect/1.2.2-1.
Ignoring request to alter fixed versions of bug #846706 to the same values 
previously set
> affects -1 src:network-manager-openconnect
Bug #846706 [libopenconnect-dev] network-manager-openconnect: FTBFS: configure: 
error: Package requirements (openconnect >= 3.02) were not met
Added indication that 846706 affects src:network-manager-openconnect

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

Bug#846721: libaudio-mpd-perl: FTBFS: Test failures

[gregor herrmann]

Control: tag -1 + confirmed

On Sat, 03 Dec 2016 08:42:45 +0100, Lucas Nussbaum wrote:

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

> > Test Summary Report
> > ---
> > t/40-playlist.t(Wstat: 0 Tests: 14 Failed: 0)
> >   Parse errors: Bad plan.  You planned 24 tests but ran 14.
> > Files=12, Tests=201, 31 wallclock secs ( 0.08 usr  0.03 sys +  7.57 cusr  
> > 0.75 csys =  8.43 CPU)
> > Result: FAIL
> > Failed 1/12 test programs. 0/201 subtests failed.

Works for me locally, and on the buildd and on ci.d.n.
But the reproducible builds had a failure as well on 1 of the 3
architectures:

https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/libaudio-mpd-perl_2.004-1.rbuild.log

Could not create socket: Connection refused
# Looks like you planned 24 tests but ran 14.
# Looks like your test exited with 256 just after 14.
t/40-playlist.t .. 
1..24
ok 1 - 'playlist return an Audio::MPD::Playlist object' isa 
'Audio::MPD::Playlist'
ok 2 - 'as_items() returns AMC::Item::Song objects' isa 
'Audio::MPD::Common::Item::Song'
ok 3 - 'as_items() returns AMC::Item::Song objects' isa 
'Audio::MPD::Common::Item::Song'
ok 4 - 'as_items() returns AMC::Item::Song objects' isa 
'Audio::MPD::Common::Item::Song'
ok 5 - first song reported first
ok 6 - 'items_changed_since() returns AMC::Item::Song objects' isa 
'Audio::MPD::Common::Item::Song'
ok 7 - 'items_changed_since() returns AMC::Item::Song objects' isa 
'Audio::MPD::Common::Item::Song'
ok 8 - 'items_changed_since() returns AMC::Item::Song objects' isa 
'Audio::MPD::Common::Item::Song'
ok 9 - first song reported first
ok 10 - add() songs
ok 11 - delete() songs
ok 12 - deleteid() songs
ok 13 - clear() leaves 0 songs
ok 14 - clear() changes playlist length
Failed 10/24 subtests 

Test Summary Report
---
t/40-playlist.t(Wstat: 0 Tests: 14 Failed: 0)
  Parse errors: Bad plan.  You planned 24 tests but ran 14.
Files=12, Tests=201, 40 wallclock secs ( 0.10 usr  0.04 sys + 15.63 cusr  1.72 
csys = 17.49 CPU)
Result: FAIL
Failed 1/12 test programs. 0/201 subtests failed.


(Same problem as in Lucas' test: "Could not create socket: Connection
refused".)


Oh, and now I get the failure as well, not during build but with
autopkgtests:

t/40-playlist.t ..
1..24
ok 1 - 'playlist return an Audio::MPD::Playlist object' isa 
'Audio::MPD::Playlist'
ok 2 - 'as_items() returns AMC::Item::Song objects' isa 
'Audio::MPD::Common::Item::Song'
ok 3 - 'as_items() returns AMC::Item::Song objects' isa 
'Audio::MPD::Common::Item::Song'
ok 4 - 'as_items() returns AMC::Item::Song objects' isa 
'Audio::MPD::Common::Item::Song'
ok 5 - first song reported first
ok 6 - 'items_changed_since() returns AMC::Item::Song objects' isa 
'Audio::MPD::Common::Item::Song'
ok 7 - 'items_changed_since() returns AMC::Item::Song objects' isa 
'Audio::MPD::Common::Item::Song'
ok 8 - 'items_changed_since() returns AMC::Item::Song objects' isa 
'Audio::MPD::Common::Item::Song'
ok 9 - first song reported first
ok 10 - add() songs
Could not create socket: Connection refused
# Looks like you planned 24 tests but ran 10.
# Looks like your test exited with 256 just after 10.
Failed 14/24 subtests


Note that here more tests are failing / the connection problem arises
earlier.


We're already skipping t/23-output.t, maybe we should just skip
t/40-playlist.t as well? Better ideas?


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Various Artists: The Two Conneeleys


signature.asc
Description: Digital Signature

Processed: Re: Bug#846721: libaudio-mpd-perl: FTBFS: Test failures

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + confirmed
Bug #846721 [src:libaudio-mpd-perl] libaudio-mpd-perl: FTBFS: Test failures
Added tag(s) confirmed.

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

Bug#846836: ruby-json-pure: Incomplete debian/copyright?

[Chris Lamb]

Source: ruby-json-pure
Version: 2.0.2+dfsg-2.dsc
Severity: serious
Justication: Policy 12.5

Hi,

I just ACCEPTed ruby-json-pure from NEW but noticed it was missing 
attribution in debian/copyright for at least
ext/json/ext/generator/generator.c

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


Regards,

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

Processed: forcibly merging 814929 846694

[Debian Bug Tracking System]

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

> forcemerge 814929 846694
Bug #814929 [src:libdata-uuid-libuuid-perl] libdata-uuid-libuuid-perl: FTBFS on 
ppc64el: test failure
Bug #846694 [src:libdata-uuid-libuuid-perl] libdata-uuid-libuuid-perl: FTBFS: 
Test failures
Set Bug forwarded-to-address to 
'https://rt.cpan.org/Public/Bug/Display.html?id=119111'.
Added tag(s) patch.
Bug #814929 [src:libdata-uuid-libuuid-perl] libdata-uuid-libuuid-perl: FTBFS on 
ppc64el: test failure
Marked as found in versions libdata-uuid-libuuid-perl/0.05-2.
Added tag(s) stretch and sid.
Merged 814929 846694
> thanks
Stopping processing here.

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

Bug#844121: CVE-2016-9300, CVE-2016-9301, and CVE-2016-9302 are *NOT* valid bug reports

[Sam Trenholme]

CVE-2016-9300, CVE-2016-9301, and CVE-2016-9302 are *NOT* valid bug reports.

Here’s the deal: The reporter had to patch MaraDNS before he was able
to crash her.

The patch, however, treats MaraDNS’ special buffer-overflow-resistant
“js_string” as if it were an ordinary string — but it’s not. Here’s
the offending code patched in to MaraDNS from the reporter’s “bug
report”:

sock_num = read(0, incoming, 512);

As per the man page for read:

ssize_t read(int fd, void *buf, size_t count);

DESCRIPTION
   read()  attempts to read up to count bytes from file descriptor fd into
   the buffer starting at buf.

However, incoming is not a raw string buffer: It’s a special js_string
object which MaraDNS uses to be buffer overflow resistant, as can be
seen here in server/MaraDNS.c:

int main(int argc, char **argv) {

js_string *mararc_loc = 0, *errors = 0,
  *bind_address = 0, *ipv6_bind_address = 0,
  *csv2_synthip_address = 0,
  *ipv4_bind_address = 0, *incoming = 0,
  *uncomp = 0, *verbstr = 0;

The js_string structure (I guess I would call it an object here in
2016) is defined in libs/JsStr.h:

typedef struct {
unsigned char *string;   /* Actual physical string */
unsigned int unit_size;  /* The size of a single character in the string */
unsigned int unit_count; /* The length of the string, in units */
unsigned int max_count;  /* The maximum allowable size of the string,
   also in units */
int encoding;   /* The type of language/encoding the string is in */
int is_good;/* This is checked to make sure the data structure is
   sane */
} js_string;

Point being, if we patch MaraDNS to treat this structure as a raw
buffer instead of a structure, we will be able to crash MaraDNS — but
that doesn’t mean we have found a UDP packet of death which will crash
unpatched MaraDNS 2.0.13.

I appreciate that people are performing security research with
MaraDNS, and the fact that researchers need to resort to patching
MaraDNS before crashing her indicates that, a decade and a half later
MaraDNS is still a usable DNS server with a strong security record.

Processed: Re: Bug#775434: libbio-scf-perl: FTBFS on mips64el, ppc64el, s390x - tests

[Debian Bug Tracking System]

Processing control commands:

> tag 846731 + confirmed
Bug #846731 [src:libbio-scf-perl] libbio-scf-perl: FTBFS: Test failures
Ignoring request to alter tags of bug #846731 to the same tags previously set

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

Bug#846731: Bug#775434: libbio-scf-perl: FTBFS on mips64el, ppc64el, s390x - tests

[gregor herrmann]

Control: tag 846731 + confirmed

On Wed, 26 Oct 2016 13:26:42 +0100, Iain Lane wrote:

> On Thu, Jan 15, 2015 at 05:17:10PM +, James Cowgill wrote:

> > libbio-scp-perl FTBFS on mips64el, ppc64el, and s390x with similar
> > testsuite failures:

> > Although I haven't investigated this, the build produces many pointer
> > casting warnings which seem likely to have caused these errors:
> > 
> > SCF.xs: In function 'XS_Bio__SCF_get_scf_pointer':
> > SCF.xs:57:20: warning: cast from pointer to integer of different size 
> > [-Wpointer-to-int-cast]
> >   ret_val = newSViv((int)scf_data);
> 
> We are noticing this on ubuntu/amd64 too - not sure right now why
> debian/amd64 doesn't have it.

Now also in Debian: #846731
(And I can reproduce it locally).

Interestingly, it still built some weeks ago on the
reproducible-build hosts:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libbio-scf-perl.html
(also i386 and armhf)


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Walter Tessaris: Aria d'Irlanda


signature.asc
Description: Digital Signature

Processed: Re: Bug#775434: libbio-scf-perl: FTBFS on mips64el, ppc64el, s390x - tests

[Debian Bug Tracking System]

Processing control commands:

> tag 846731 + confirmed
Bug #846731 [src:libbio-scf-perl] libbio-scf-perl: FTBFS: Test failures
Added tag(s) confirmed.

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

Bug#846675: zeroinstall-injector: FTBFS: Test failures

[Thomas Leonard]

On 3 December 2016 at 07:44, Lucas Nussbaum  wrote:
> Source: zeroinstall-injector
> Version: 2.12-2
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20161202 qa-ftbfs
> Justification: FTBFS on amd64
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build on
> amd64.

Hi Lucas,

I can reproduce this on sid. It appears that GnuPG has started
reporting incorrect error values. I have reported it here:

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

If that doesn't get fixed soon, I could work around it by masking off
the top bits of the error code.


-- 
talex5 (GitHub/Twitter)http://roscidus.com/blog/
GPG: 5DD5 8D70 899C 454A 966D  6A51 7513 3C8F 94F6 E0CC
GPG: DA98 25AE CAD0 8975 7CDA  BD8E 0713 3F96 CA74 D8BA

Bug#846580: marked as done (environment-modules,lmod: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Sat, 03 Dec 2016 15:26:31 +
with message-id 
and subject line Bug#846580: fixed in modules 3.2.10-10
has caused the Debian Bug report #846580,
regarding environment-modules,lmod: error when trying to install together
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.)


-- 
846580: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846580
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: environment-modules,lmod
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 6.6-0.1
Control: found -1 3.2.10-9

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Selecting previously unselected package lmod.
  Preparing to unpack .../10-lmod_6.6-0.1_all.deb ...
  Unpacking lmod (6.6-0.1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-7ATbYB/10-lmod_6.6-0.1_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man1/module.1.gz', which is also in 
package environment-modules 3.2.10-9
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-7ATbYB/10-lmod_6.6-0.1_all.deb

This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/share/man/man1/module.1.gz

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


environment-modules=3.2.10-9_lmod=6.6-0.1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: modules
Source-Version: 3.2.10-10

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated modules package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 02 Dec 2016 11:17:36 +
Source: modules
Binary: environment-modules
Architecture: source amd64
Version: 3.2.10-10
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Description:
 environment-modules - Modular system for handling environment variables
Closes: 731974 785223 846580
Changes:
 modules (3.2.10-10) unstable; urgency=medium
 .
   * Conflict with lmod. Closes: #846580
   * Standards-Version: 3.9.8; no changes required
   * Now use debhelper 10.
   * Move /etc/bash_completions.d -> /usr/share/bash-completions/completions
   * Close old bugs already fixed: Closes: #731974
   * Fix broken path to modulecmd in bash completions. Closes: #785223
   * Remove duplicate ref to conffile modulespath
Checksums-Sha1:
 1c99f10a7c3b32a4bc0e007f9845af5183848d88 1783 modules_3.2.10-10.dsc
 18421118ec2bb559952d752677b126be4bf6ddd7 7352 modules_3.2.10-10.debian.tar.xz
 c222ef974828ba69f67e74b05bc56292b5c70982 567432 
environment-modules-dbgsym_3.2.10-10_amd64.deb
 afcb68707d496b7f3252fbe4d47321e4afa04349 94782 

Bug#846734: debmake-doc: FTBFS: dpkg-buildpackage: error: check-commmand 'lintian' not found

[Osamu Aoki]

On Sat, Dec 03, 2016 at 08:48:47AM +0100, Lucas Nussbaum wrote:
> Source: debmake-doc
> Version: 1.6-1
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20161202 qa-ftbfs
> Justification: FTBFS on amd64

...
> > dpkg-buildpackage: error: check-commmand 'lintian' not found
> > 
> > debuild: fatal error at line 1100:
> > 
> > dpkg-buildpackage -rfakeroot -us -uc --hook-check=cd ..;  -i 
> > --check-command=lintian failed
> > 
> > Makefile:24: recipe for target 'all' failed
> > make[3]: *** [all] Error 1

Thanks.  My chroot had lintian ... I will add it to "Depends".

(Need to update more to avoid FTBFS for new debuild behavior...)

Bug#844121: Remote crash in MaraDNS 2.0.13

[Sam Trenholme]

This email concerns CVE-2016-9300, CVE-2016-9301, and CVE-2016-9302.

I have written a utility to send the packets that supposedly remotely crash
MaraDNS to MaraDNS via UDP. The packets do not crash MaraDNS when sent over
the network; I can only crash MaraDNS with the offending packets by using
the reporter’s patch to update MaraDNS to get DNS packets via standard
input, and only in my 64-bit Cygwin development environment.

I am closing this issue; I will open this again if someone can come up with
an actual "send this UDP packet and MaraDNS crashes" recipe. Please let me
know which OS and which processor architecture the crash happens on, but if
the OS is anything besides CentOS6 or the architecture anything besides x86
(32-bit) or amd_64/x86-64 (64-bit), I will not be able to address the
concern without a patch being provided.

Further discussion of this matter can be done by either replying to this
email, or by adding a note to https://github.com/samboy/MaraDNS/issues/33

Again, I will reopen this issue as a critical security issue if and only if
someone can reproduce this concern via an actual UDP packet sent to
MaraDNS. Please provide the source code of the program generating the
packet of death, or use the program I wrote to attempt to reproduce this
issue at
https://github.com/samboy/MaraDNS/blob/1dba9f49e9b6f788cf602695478edcb094a0cc06/sqa/sendpacket.c
(sqa/sendpacket.c if you clone the Github tree as of 2016-12-03).

Ondrej: If you were to provide a patch, or even a usable stack trace -- or
even just let me know on which distribution and architecture you're seeing
the issue (sorry, but I couldn't get a usable core file or stack trace in
Cygwin-64, and no crash at all in CentOS6-32bit) -- I will open up a GitHub
bug about the issue. I agree there is probably a bug in MaraDNS -- but I
will not treat this as an "all hands on deck" packet-of-death level
security bug until we can send an actual packet of death over UDP to kill
MaraDNS.

On Sat, Dec 3, 2016 at 6:04 AM, Sam Trenholme  wrote:

> Github bug: https://github.com/samboy/MaraDNS/issues/33
>
> Please go here to get the latest updates from upstream about this issue.
>
> On Sat, Dec 3, 2016 at 5:52 AM, Sam Trenholme  wrote:
>
>> Hello there,
>>
>> I have just become aware of this bug. Right now, I can reproduce the
>> crash in Cygwin 64-bit, but am unable to reproduce the crash in my 32-bit
>> CentOS6 development environment where I would actually be able to get a
>> full stack trace (which was not provided in the original bug report). Until
>> I can get a setup to reproduce the crashes in a manner which lets me have
>> full stack traces, I will not be able to make the appropriate patches to
>> fix the bug.
>>
>> There is no money on the table, and I have stopped actively developing
>> MaraDNS every since becoming a single parent with a full-time job. Welcome
>> to the world of open source economics: Since I’m not getting paid for my
>> time writing open-source software, I have very little time to devote to
>> MaraDNS.
>>
>> I will open up a GitHub bug so that users know I am aware of the bug. I
>> do not have a time frame for fixing the issue at this time. Hopefully by
>> the end of the year.
>>
>> -- Sam
>>
>> On Sat, Nov 12, 2016 at 10:18 AM, Luciano Bello 
>> wrote:
>>
>>> Source: maradns
>>> Severity: grave
>>> Version: 2.0.13-1.2
>>> Tags: security upstream
>>>
>>> Hi,
>>>
>>> The following vulnerability was published for MaraDNS:
>>> http://seclists.org/oss-sec/2016/q4/411
>>>
>>> No CVE is was assigned yet, but the request was made in that thread.
>>> If you fix the vulnerability please also make sure to include the
>>> CVE (Common Vulnerabilities & Exposures) id in your changelog entry, if
>>> it is
>>> assigned soon.
>>>
>>> Please adjust the affected versions in the BTS as needed.
>>>
>>> Regards,luciano
>>>
>>>
>>
>

Bug#846784: xserver-xorg-video-nvidia: unstable version of xserver-xorg-video-nvidia forbids the installation of xserver-xorg-core/unstable

[Diederik de Haas]

On zaterdag 3 december 2016 13:08:22 CET Luca Boccassi wrote:
> Please install nvidia-driver from experimental until 845638 is fixed.

I'd like to report that I have installed the version from experimental with 
xserver-xorg-core version 2:1.19.0-2 and it is working fine :)

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

Processed: Re: Bug#846783: freedroidrpg: Upgrade fails: tries to overwrite manpage.

[Debian Bug Tracking System]

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

> severity 846783 serious
Bug #846783 [freedroidrpg] freedroidrpg: Upgrade fails: tries to overwrite 
manpage.
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#844121: Remote crash in MaraDNS 2.0.13

[Sam Trenholme]

Github bug: https://github.com/samboy/MaraDNS/issues/33

Please go here to get the latest updates from upstream about this issue.

On Sat, Dec 3, 2016 at 5:52 AM, Sam Trenholme  wrote:

> Hello there,
>
> I have just become aware of this bug. Right now, I can reproduce the crash
> in Cygwin 64-bit, but am unable to reproduce the crash in my 32-bit CentOS6
> development environment where I would actually be able to get a full stack
> trace (which was not provided in the original bug report). Until I can get
> a setup to reproduce the crashes in a manner which lets me have full stack
> traces, I will not be able to make the appropriate patches to fix the bug.
>
> There is no money on the table, and I have stopped actively developing
> MaraDNS every since becoming a single parent with a full-time job. Welcome
> to the world of open source economics: Since I’m not getting paid for my
> time writing open-source software, I have very little time to devote to
> MaraDNS.
>
> I will open up a GitHub bug so that users know I am aware of the bug. I do
> not have a time frame for fixing the issue at this time. Hopefully by the
> end of the year.
>
> -- Sam
>
> On Sat, Nov 12, 2016 at 10:18 AM, Luciano Bello 
> wrote:
>
>> Source: maradns
>> Severity: grave
>> Version: 2.0.13-1.2
>> Tags: security upstream
>>
>> Hi,
>>
>> The following vulnerability was published for MaraDNS:
>> http://seclists.org/oss-sec/2016/q4/411
>>
>> No CVE is was assigned yet, but the request was made in that thread.
>> If you fix the vulnerability please also make sure to include the
>> CVE (Common Vulnerabilities & Exposures) id in your changelog entry, if
>> it is
>> assigned soon.
>>
>> Please adjust the affected versions in the BTS as needed.
>>
>> Regards,luciano
>>
>>
>

Bug#844121: Remote crash in MaraDNS 2.0.13

[Sam Trenholme]

Hello there,

I have just become aware of this bug. Right now, I can reproduce the crash
in Cygwin 64-bit, but am unable to reproduce the crash in my 32-bit CentOS6
development environment where I would actually be able to get a full stack
trace (which was not provided in the original bug report). Until I can get
a setup to reproduce the crashes in a manner which lets me have full stack
traces, I will not be able to make the appropriate patches to fix the bug.

There is no money on the table, and I have stopped actively developing
MaraDNS every since becoming a single parent with a full-time job. Welcome
to the world of open source economics: Since I’m not getting paid for my
time writing open-source software, I have very little time to devote to
MaraDNS.

I will open up a GitHub bug so that users know I am aware of the bug. I do
not have a time frame for fixing the issue at this time. Hopefully by the
end of the year.

-- Sam

On Sat, Nov 12, 2016 at 10:18 AM, Luciano Bello  wrote:

> Source: maradns
> Severity: grave
> Version: 2.0.13-1.2
> Tags: security upstream
>
> Hi,
>
> The following vulnerability was published for MaraDNS:
> http://seclists.org/oss-sec/2016/q4/411
>
> No CVE is was assigned yet, but the request was made in that thread.
> If you fix the vulnerability please also make sure to include the
> CVE (Common Vulnerabilities & Exposures) id in your changelog entry, if it
> is
> assigned soon.
>
> Please adjust the affected versions in the BTS as needed.
>
> Regards,luciano
>
>

Bug#846816: java.lang.NoSuchFieldError: DLU2

[Vincent Smeets]

Package: freeplane
Version: 1.5.16-2
Severity: grave
Justification: renders package unusable

Hallo,

Freeplane has been working for me some days/weeks ago. This morning, I
started freeplane again and it wont start anymore. To be sure, I also
removed my local settings by removing the directory .config/freeplane,
but that didn't help either.
When I start freeplane, it opens an empty main X11-frame and then only a
dialog box with the excpetion java.lang.NoSuchFieldError. There is no
other UI element shown. I can only exit the command by closing the
window.

Here I started freeplane from the command line. It shows you the log
output and the raised exception.
My machine is configured for Debian/Testing.

Regards,
Vincent Smeets



vincent@PC-Vincent$ rm -rf .config/freeplane

vincent@PC-Vincent$ freeplane
org.knopflerfish.framework.readonly=true
org.knopflerfish.gosg.jars=reference:file:/usr/share/freeplane/core/
org.freeplane.basedirectory=/usr/share/freeplane
java.security.policy=/usr/share/freeplane/freeplane.policy
org.osgi.framework.storage=/usr/share/freeplane/fwdir
Knopflerfish OSGi framework launcher, version 
Copyright 2003-2016 Knopflerfish. All Rights Reserved.
See http://www.knopflerfish.org for more information.

Created Framework: org.knopflerfish.framework, version=7.2.0.
User properties not found, new file created
Installed: 
reference:file:/usr/share/freeplane/plugins/org.freeplane.plugin.latex (id#2)
Installed: 
reference:file:/usr/share/freeplane/plugins/org.freeplane.plugin.jsyntaxpane 
(id#3)
Installed: 
reference:file:/usr/share/freeplane/plugins/org.freeplane.plugin.bugreport 
(id#4)
Installed: 
reference:file:/usr/share/freeplane/plugins/org.freeplane.plugin.openmaps (id#5)
Installed: 
reference:file:/usr/share/freeplane/plugins/org.freeplane.plugin.formula (id#6)
Installed: 
reference:file:/usr/share/freeplane/plugins/org.freeplane.plugin.script (id#7)
Installed: reference:file:/usr/share/freeplane/plugins/org.freeplane.plugin.svg 
(id#8)
Started: reference:file:/usr/share/freeplane/plugins/org.freeplane.plugin.latex 
(id#2)
Started: 
reference:file:/usr/share/freeplane/plugins/org.freeplane.plugin.jsyntaxpane 
(id#3)
Started: 
reference:file:/usr/share/freeplane/plugins/org.freeplane.plugin.bugreport 
(id#4)
Started: 
reference:file:/usr/share/freeplane/plugins/org.freeplane.plugin.openmaps (id#5)
Started: 
reference:file:/usr/share/freeplane/plugins/org.freeplane.plugin.formula (id#6)
Started: 
reference:file:/usr/share/freeplane/plugins/org.freeplane.plugin.script (id#7)
Started: reference:file:/usr/share/freeplane/plugins/org.freeplane.plugin.svg 
(id#8)
Dec 03, 2016 2:37:33 PM org.freeplane.core.util.LogUtils info
INFO: language resources for en found
Dec 03, 2016 2:37:33 PM org.freeplane.core.util.LogUtils info
INFO: freeplane_version = 1.5.16; freeplane_xml_version = freeplane 1.5.9
git revision = 34552bb3e49d7f4626fd03c87306a1c89f4e25e9 Dimitry Polivaev 
2016-09-17 10:32:23 +0200
java_version = 1.8.0_111; os_name = Linux; os_version = 4.8.0-1-amd64
Dec 03, 2016 2:37:34 PM org.freeplane.core.util.LogUtils info
INFO: /home/vincent/.config/freeplane/1.5.x/formats.xml does not exist yet
Dec 03, 2016 2:37:34 PM org.freeplane.core.util.LogUtils info
INFO: /home/vincent/.config/freeplane/1.5.x/scanner.xml does not exist yet
Dec 03, 2016 2:37:34 PM org.freeplane.core.util.LogUtils info
INFO: added parsing support for standard date format M/d/yy
Dec 03, 2016 2:37:34 PM org.freeplane.core.util.LogUtils info
INFO: added parsing support for standard date time format M/d/yy h:mm a
Dec 03, 2016 2:37:34 PM org.freeplane.core.util.LogUtils info
INFO: creating user icons directory /home/vincent/.config/freeplane/1.5.x/icons
Dec 03, 2016 2:37:34 PM org.freeplane.core.util.LogUtils info
INFO: available locales not found
Dec 03, 2016 2:37:34 PM org.freeplane.core.util.LogUtils info
INFO: available locales not found
Dec 03, 2016 2:37:34 PM org.freeplane.core.util.LogUtils info
INFO: Loaded properties from 
bundle://6:1/org/freeplane/plugin/formula/defaults.properties
Dec 03, 2016 2:37:34 PM org.freeplane.core.util.LogUtils info
INFO: creating user add-ons directory 
/home/vincent/.config/freeplane/1.5.x/addons
Dec 03, 2016 2:37:34 PM org.freeplane.core.util.LogUtils warn
WARNING: classpath entry '/home/vincent/.config/freeplane/1.5.x/lib' doesn't 
exist. (Use : to separate entries.)
Dec 03, 2016 2:37:34 PM org.freeplane.core.util.LogUtils info
INFO: Loaded properties from 
bundle://7:1/org/freeplane/plugin/script/defaults.properties
Dec 03, 2016 2:37:34 PM org.freeplane.core.util.LogUtils info
INFO: looking for scripts with the following endings: [groovy, js]
Dec 03, 2016 2:37:34 PM org.freeplane.core.util.LogUtils warn
WARNING: not a (script) directory: /home/vincent/.config/freeplane/1.5.x/scripts
Dec 03, 2016 2:37:34 PM org.freeplane.core.util.LogUtils info
INFO: creating user scripts directory 
/home/vincent/.config/freeplane/1.5.x/scripts
Dec 03, 2016 2:37:34 PM 

Bug#844928: marked as done (python-keystoneclient FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Sat, 3 Dec 2016 14:49:31 +0100
with message-id 

Processed: Re: Bug#846784: xserver-xorg-video-nvidia: unstable version of xserver-xorg-video-nvidia forbids the installation of xserver-xorg-core/unstable

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:nvidia-graphics-drivers
Bug #846784 [xserver-xorg-video-nvidia] xserver-xorg-video-nvidia: unstable 
version of xserver-xorg-video-nvidia forbids the installation of 
xserver-xorg-core/unstable
Bug reassigned from package 'xserver-xorg-video-nvidia' to 
'src:nvidia-graphics-drivers'.
No longer marked as found in versions nvidia-graphics-drivers/367.57-2.
Ignoring request to alter fixed versions of bug #846784 to the same values 
previously set
> forcemerge 845638 -1
Bug #845638 [src:nvidia-graphics-drivers] Compatibility with xserver 1.19 / 
xorg-video-abi-23
Bug #846502 [src:nvidia-graphics-drivers] nvidia-driver: could not install 
nvidia-driver under sid because of dependence broken
Bug #846784 [src:nvidia-graphics-drivers] xserver-xorg-video-nvidia: unstable 
version of xserver-xorg-video-nvidia forbids the installation of 
xserver-xorg-core/unstable
Severity set to 'serious' from 'important'
843265 was blocked by: 845331 845640 845644 846502 845635 845638 845639 845000 
843543 845637
843265 was not blocking any bugs.
Added blocking bug(s) of 843265: 846784
Marked as found in versions nvidia-graphics-drivers/370.28-1 and 
nvidia-graphics-drivers/367.57-2.
Bug #846502 [src:nvidia-graphics-drivers] nvidia-driver: could not install 
nvidia-driver under sid because of dependence broken
Merged 845638 846502 846784

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

Bug#846681: marked as done (open-coarrays: FTBFS: Test failures)

[Debian Bug Tracking System]

Your message dated Sat, 03 Dec 2016 13:05:17 +
with message-id 
and subject line Bug#846681: fixed in open-coarrays 1.7.4-3
has caused the Debian Bug report #846681,
regarding open-coarrays: FTBFS: Test failures
to be marked as done.

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

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


-- 
846681: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846681
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: open-coarrays
Version: 1.7.4-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161202 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):
> 21/24 Test  #6: allocate_as_barrier_proc .***Failed  Required regular 
> expression not found.Regex=[Test passed.
> ]  3.19 sec
>  Test failed.   0
> 
> 22/24 Test #20: syncimages_status    Passed3.27 sec
> 23/24 Test #23: co_heat ..   Passed3.46 sec
> 24/24 Test #16: syncall ..   Passed3.50 sec
> 
> 96% tests passed, 1 tests failed out of 24
> 
> Total Test time (real) =   3.52 sec
> 
> The following tests FAILED:
> 6 - allocate_as_barrier_proc (Failed)
> Errors while running CTest
> Makefile:119: recipe for target 'test' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/12/02/open-coarrays_1.7.4-2_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: open-coarrays
Source-Version: 1.7.4-3

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated open-coarrays 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 26 Nov 2016 11:23:14 +
Source: open-coarrays
Binary: libcoarrays-dev libcoarrays0d open-coarrays-bin
Architecture: source amd64
Version: 1.7.4-3
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Description:
 libcoarrays-dev - Co-Array Fortran libraries for gfortran - development files
 libcoarrays0d - Co-Array Fortran libraries for gfortran
 open-coarrays-bin - Executables for running Co-Array Fortran programs
Closes: 846681
Changes:
 open-coarrays (1.7.4-3) unstable; urgency=medium
 .
   * Remove multi-arch: same from -dev; .mod files differ
   * Use "--oversubcribe" not "--oversubscribe" for mpiexec. Closes: #846681
   * Disable failure on tests for the moment
Checksums-Sha1:
 5c9edd8a1c0297cf729cc5d3297f1c49c8b99f42 1971 open-coarrays_1.7.4-3.dsc
 b6494c9a2941639f5952e50dad464c00ab4ebab6 6852 
open-coarrays_1.7.4-3.debian.tar.xz
 fa21444112f3eaf2c5bb063527fd1f20d6b84fe7 45016 
libcoarrays-dev_1.7.4-3_amd64.deb
 eb08a24c145b5816b8e9fa92835459a6da0d84d7 46938 
libcoarrays0d-dbgsym_1.7.4-3_amd64.deb
 11f1f760fc438017fe52fe22e11de6f3e132aca4 22576 libcoarrays0d_1.7.4-3_amd64.deb
 38f5d252e49ee5b49d6bf601c0b3775d1ba7a5fd 7634 
open-coarrays-bin_1.7.4-3_amd64.deb
 80efcf2038c5002de7fd856af82fdf46f3948196 6889 
open-coarrays_1.7.4-3_amd64.buildinfo
Checksums-Sha256:
 841ca83f58d3b11c601aa2b03ba2994f487ff48756ed339517e9b39ba6265a91 1971 
open-coarrays_1.7.4-3.dsc
 2dbcc6943f7036ef3f8bf358107a3471aea75d8b0e92058e05cd75a1c483fc64 6852 
open-coarrays_1.7.4-3.debian.tar.xz
 66d8f2f7d4508752fe20294884228292f9238f798e50a5004743473369e8a4a7 45016 
libcoarrays-dev_1.7.4-3_amd64.deb
 7f15359c8390446fe1c9fc6d971aff60a92c9604d7ecf69e40a143ae0864e272 46938 
libcoarrays0d-dbgsym_1.7.4-3_amd64.deb
 

Bug#846742: meson: FTBFS: ld: final link failed: Bad value

[Jussi Pakkanen]

reassign 846742 gdc
stop

On Sat, Dec 3, 2016 at 9:21 AM, Lucas Nussbaum  wrote:

> Relevant part (hopefully):
>> /usr/bin/ld: dsimpleapp@exe/utils.d.o: relocation R_X86_64_PC32 against 
>> symbol 
>> `_D3std5array17__T8appenderTAyaZ8appenderFNaNbNfZS3std5array17__T8AppenderTAyaZ8Appender'
>>  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

This seems to be a bug in GDC since it happens on only this one
platform and net searching says that GCC has had problems with symbol
interpositioning in the past. This is easy to replicate without Meson.
Write this code to source.d:

import std.stdio;
import utils;
import std.string : format;

void printGreeting (string name)
{
writeln ("Hello, I am %s.".format (name));
}

void main ()
{
printGreeting ("a Meson D test");
}

Compiling it with 'gdc -o prog source.d' gives the same error.
Removing the string formatting portion makes it work again as does
compiling with -fPIC, but if that is somehow always needed GDC should
either add -fPIC itself, error out earlier or, at the very least,
print a more relevant error message. LDC compiles this same program
without errors without needing -fPIC.

If this issue is in GDC and it is not fixed until the next release,
Meson will fix the issue by changing the build dep from gdc to ldc.

Thanks,

Processed: Re: Bug#846742: meson: FTBFS: ld: final link failed: Bad value

[Debian Bug Tracking System]

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

> reassign 846742 gdc
Bug #846742 [src:meson] meson: FTBFS: ld: final link failed: Bad value
Bug reassigned from package 'src:meson' to 'gdc'.
No longer marked as found in versions meson/0.36.0-1.
Ignoring request to alter fixed versions of bug #846742 to the same values 
previously set
> stop
Stopping processing here.

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

Bug#846799: golang-google-cloud: fails to upgrade

[Dmitry Smirnov]

Source: golang-google-cloud
Version: 0.0~git20160615-6
Severity: serious

`apt-get upgrade` failed as follows:


The following packages will be upgraded:
  golang-google-cloud-compute-metadata-dev golang-google-cloud-dev
2 upgraded, 0 newly installed, 0 to remove and 10 not upgraded.
Need to get 0 B/243 kB of archives.
After this operation, 1,281 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
Reading changelogs... Done  

  
(Reading database ... 1104869 files and directories currently installed.)   

  
Preparing to unpack .../0-golang-google-cloud-dev_0.0~git20160615-6_all.deb ... 

  
Unpacking golang-google-cloud-dev (0.0~git20160615-6) over (0.0~git20160615-5) 
... 
   
dpkg: error processing archive 
/tmp/apt-dpkg-install-Q8qBLL/0-golang-google-cloud-dev_0.0~git20160615-6_all.deb
 (--unpack):   
 unable to open 
'/usr/share/gocode/src/google.golang.org/cloud/bigquery/bigquery.go.dpkg-new': 
No such file or directory   
   
Preparing to unpack 
.../1-golang-google-cloud-compute-metadata-dev_0.0~git20160615-6_all.deb ...

  
Unpacking golang-google-cloud-compute-metadata-dev (0.0~git20160615-6) over 
(0.0~git20160615-5) ... 
  
dpkg: error processing archive 
/tmp/apt-dpkg-install-Q8qBLL/1-golang-google-cloud-compute-metadata-dev_0.0~git20160615-6_all.deb
 (--unpack):  
 unable to open 
'/usr/share/gocode/src/google.golang.org/cloud/compute/metadata/metadata.go.dpkg-new':
 No such file or directory  

Errors were encountered while processing:   

  
 
/tmp/apt-dpkg-install-Q8qBLL/0-golang-google-cloud-dev_0.0~git20160615-6_all.deb

 
 
/tmp/apt-dpkg-install-Q8qBLL/1-golang-google-cloud-compute-metadata-dev_0.0~git20160615-6_all.deb




-- 
Regards,
 Dmitry Smirnov
 GPG key : 4096R/52B6BBD953968D1B

---

Journalism is printing what someone else does not want printed: everything
else is public relations.
-- George Orwell


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

Bug#828258: canl-c/gridsite: FTBFS with openssl 1.1.0

[Sebastian Andrzej Siewior]

On 2016-12-03 12:14:38 [+0100], Stefan Fritsch wrote:
> On Friday, 2 December 2016 00:16:24 CET Sebastian Andrzej Siewior wrote:
> > is there a reason for gridsite not to go for 3.0 (or backport the
> > change) and libssl-dev? Apache stays 1.0 but does not expose anything
> > SSL related (unless I read #828236 too quick).
> 
> (assuming you meant 1.1 instead of 3.0). Unfortunately, gridsites uses apache 
> private structures to get to the SSL related stuff and then uses openssl 
> functions on it. So gridsite absolutely must use the same openssl version as 
> apache.

I read somewhere that gridsite 3.0 supports openssl 1.1.0. And I read in
the apache bug that they no longer depend on openssl headers in their
apache dev headers. I had no idea, that apache exposes the SSL struct to
their users. Since gridsite depends on curl as well, I am going to chec
the curl usage is safe in reard to 1.1.0…
Thanks for the info.

Sebastian

Bug#846538: marked as done (coz-profiler: executable missing)

[Debian Bug Tracking System]

Your message dated Sat, 03 Dec 2016 13:29:50 +0100
with message-id <2fltwalp54x@diskless.uio.no>
and subject line (fwd) Accepted coz-profiler 0.0.git.20161130T1802-2 (source) 
into unstable
has caused the Debian Bug report #846538,
regarding coz-profiler: executable missing
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.)


-- 
846538: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846538
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: coz-profiler
Version: 0.0.git.20161130T1802-1
Severity: grave
Justification: renders package unusable

The actual coz executable went missing in the latest build.  Could you
please reinstate it?

Thanks!

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

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

Versions of packages coz-profiler depends on:
ii  fonts-font-awesome  4.7.0~dfsg-1
ii  libjs-jquery3.1.1-1
ii  python  2.7.11-2

coz-profiler recommends no packages.

coz-profiler suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---

Version: 0.0.git.20161130T1802-2

--- Begin Message ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 03 Dec 2016 08:58:39 +
Source: coz-profiler
Binary: coz-profiler
Architecture: source
Version: 0.0.git.20161130T1802-2
Distribution: unstable
Urgency: medium
Maintainer: Lluís Vilanova 
Changed-By: Petter Reinholdtsen 
Description:
 coz-profiler - Finding Code that Counts with Causal Profiling
Changes:
 coz-profiler (0.0.git.20161130T1802-2) unstable; urgency=medium
 .
   [ Lluís Vilanova ]
   * Reverted 36c9b5e to remove useless 04-make-check patch
   * Added 06-viewer-install.patch to align viewer makefile with
 common.mk (fixes #846538).
   * Added 07-coz-plot.patch to hint users how to use the viewer
 .
   [ Petter Reinholdtsen ]
   * Adjusted 07-coz-plot.patch to suggest opening HTML page using xdg-open.
Checksums-Sha1:
 d978447292310bbc2ba0bf08bdf59c4f108d5774 2212 
coz-profiler_0.0.git.20161130T1802-2.dsc
 dd16338d49541a35179c1cece427801758b238a4 7336 
coz-profiler_0.0.git.20161130T1802-2.debian.tar.xz
Checksums-Sha256:
 345ad941357abca5acabf0552b7d28b84a7e403368733a4262a8c1fcbd01c2a1 2212 
coz-profiler_0.0.git.20161130T1802-2.dsc
 8a846a590da98bab6bb888dce5e03e5e1ac1f2e743571e6da5b0f101e12d2e5e 7336 
coz-profiler_0.0.git.20161130T1802-2.debian.tar.xz
Files:
 ab34f9f912cb16875f17ad3157b5545e 2212 net optional 
coz-profiler_0.0.git.20161130T1802-2.dsc
 992b70f9d324d2816d5ca947bd72011b 7336 net optional 
coz-profiler_0.0.git.20161130T1802-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAlhCifMACgkQgSgKoIe6
+w7NQA//SBw40piAZAoh5KPdh02qszT/FYQG0pMY1bUS6mCIXXwGKCaptFHeezDX
y6vuIGmF/f3ED+y7HXFyvXSFa2jFOT0Y2N4jVuospebUXSLdKGhatO56RGDNrVFI
Yt2ZevcuzHqpwJMMvcU7CRXYGhLmoMDUeQJAx0HGC1AlNxLKXwD3V7qdBNd2hyVU
ZqP8nZdNyi+aWoTPhiF5elnG/tBW2tLM7ufP/Dxe00muTU/5PQG3+s7l0Z3D1mws
QNdH6Nf3pADphDgIvdOmhVzfFEPdOemUcIAE786GyzKa7gxJkhF9n9vlu5CZV/rk
E2DN2eGzM8QvqB19u2EUCw5kPVWSrvLcMGD9ja8Fpjcl/0mRTshmyvNEcG1XDoah
4RJUfyF/imYGfPx672R7lb8E7952RFnfv6MzLSYvI8uCBLyrWux9Tkxxe3w793ni
OuzJO3KICQ4/A6HPjd7q77uKb+Ph8cyshyY+OU64ABQJR62xeoqSlJMEOrcWwL7O
XuUOQNaTq78YzCy/Wf1KRVd3IXMCGJqTPQ6D9MzjNQkb8gU2m7jnp2GZ4o8I9v4I
DLFWJKXmkznjVR8J5GYrTQkqXL0cTzJdsgQgidIRQivCOVkLVYGS/p4ElWwDrHYk
0UMAVV8ScbzGSllC7I8nuc1I8Tr7NelieHbqaC4VkLnWDg0twHo=
=Sw3v
-END PGP SIGNATURE-

--- End Message ---
--- End Message ---

Bug#591419: librmagick-ruby should not be installable with imagemagick

[Antonio Terceiro]

On Fri, Dec 02, 2016 at 11:12:21AM -0800, Nishanth Aravamudan wrote:
> Package: ruby-rmagick
> Version: 2.15.4+dfsg-2
> Followup-For: Bug #591419
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu zesty ubuntu-patch
> 
> I think this should do what is expected. Basically, AIUI, there is a
> more-than-ABI-specifiable (due to issues upstream and possibly in the
> Debian package itself (cf.:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846385) dependency
> between ruby-rmagick and the version of imagemagick compiled against. To
> that end, add an overriding dependency at build-time.
> 
> I think what's actually needed currently in ruby-rmagick's case in
> Debian is a rebuild against the bumped version of imagemagick; if that's
> done, the autopkgtests would pass. But expressing this dependency
> explicilty would have caught that and prevented imagemagick from
> changing in Debian until ruby-rmagick had been rebuilt?
> 
> Comments more than welcome and appreciated.
> 
> Thanks!
> -Nish
> 
> ##  REPLACE THIS WITH ACTUAL INFORMATION -
> ## Please add all necessary information about why the change needed to go in
> ## Ubuntu, quote policy, spec or any other background material and why it can
> ## and should be used in Debian too.  If the patch is composed of multiple
> ## independent pieces, please send them as separate bug reports.
> ##  REPLACE THIS WITH ACTUAL INFORMATION -
> 
> 
>   * d/{control,rules}: use a new substitution variable to specify the
> hard-dependency on the version of ImageMagick built against
> (Closes: #591419). Thanks to Adam Conrad for the shell code.
> 
> Thanks for considering the patch.
> 
> *** /tmp/tmp6FrTwc/ruby-rmagick_2.15.4+dfsg-2ubuntu1.debdiff
> diff -Nru ruby-rmagick-2.15.4+dfsg/debian/control 
> ruby-rmagick-2.15.4+dfsg/debian/control
> --- ruby-rmagick-2.15.4+dfsg/debian/control   2016-08-16 07:29:37.0 
> -0700
> +++ ruby-rmagick-2.15.4+dfsg/debian/control   2016-12-01 15:36:05.0 
> -0800
> @@ -28,7 +28,8 @@
>  XB-Ruby-Versions: ${ruby:Versions}
>  Depends: ruby | ruby-interpreter,
>   ${misc:Depends},
> - ${shlibs:Depends}
> + ${shlibs:Depends},
> + ${imagemagick:Depends}
>  Description: ImageMagick API for Ruby
>   RMagick is an interface between the Ruby programming language and the
>   ImageMagick image processing library.
> diff -Nru ruby-rmagick-2.15.4+dfsg/debian/rules 
> ruby-rmagick-2.15.4+dfsg/debian/rules
> --- ruby-rmagick-2.15.4+dfsg/debian/rules 2016-08-16 07:29:37.0 
> -0700
> +++ ruby-rmagick-2.15.4+dfsg/debian/rules 2016-12-01 15:36:05.0 
> -0800
> @@ -12,3 +12,11 @@
>   find debian/*/usr/share/doc/ruby-rmagick-doc/ \
>   -type f -executable -exec \
>   chmod -x '{}' ';'
> +
> +override_dh_gencontrol:
> + $(eval IMAGEMAGICK_DEP := \
> + $(shell find debian/ruby-rmagick/ -name RMagick2.so -exec ldd 
> '{}' ';' | \
> + awk '/\/libMagickCore/ {print $$3}' | xargs dpkg -S | \
> + awk '{print $$1}' | sed 's/:$$//' | xargs dpkg-query -W \
> + -f='$${Package} (>= $${Version})'))
> + dh_gencontrol -- -Vimagemagick:Depends='$(IMAGEMAGICK_DEP)'

Hi, thanks for the patch.

However, I fail to see how this would fix the issue, since it won't help
with the very problem that a new version of ImageMagick that has no
SONAME bump breaks ruby-rmagick.

There is a new version of ruby-rmagick which claims support for
ImageMagick 6.9, and apparently shifts the dependency from libmagickcore
to libmagickwand ... this might be the correct fix.


signature.asc
Description: PGP signature