Bug#876238: gcc-cross-support: FTBFS, wants to regenerate debian/control with more and renamed packages

2017-09-19 Thread Helmut Grohne
Hi Andreas,

On Wed, Sep 20, 2017 at 02:37:38AM +0200, Andreas Beckmann wrote:
> gcc-cross-support FTBFS in experimental, tries to regenerate
> debian/control in order to rename several packages and add a bunch of
> new ones.

Yes. The problem essentially is that you can only upload
gcc-cross-support after a stable update of dpkg, because either it FTBFS
or dak rejects it, because dak's idea of valid architectures differs
from dpkg's.

> Given that the package hasn't seen any upload in the last two years,
> maybe it's not needed for the current cross compilers and should rather
> be removed than fixed :-)

Indeed the goal is to get it removed. Removing the package that is, not
removing the functionality. We have made significant progress by
introducing binutils-for-host and binutils-for build into src:binutils
now. The next step is introducing gcc-7-for-host and when gcc-defaults
takes over gcc-for-host, I want to remove the source package. Until
then, I'd like to keep it accessible to show where this work is heading.

So while there hasn't been any upload, progress is not stuck. I'd like
to keep the package (rc buggy as it is) in experimental for a while
though. I hope that doesn't cause too much pain to you.

Helmut



Processed: tagging 876221

2017-09-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 876221 + upstream fixed-upstream
Bug #876221 [tor] log uninitialized stack in non-default configuration 
[CVE-2017-0380]
Added tag(s) upstream and fixed-upstream.
> thanks
Stopping processing here.

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



Bug#876242: exiv2: CVE-2017-12957

2017-09-19 Thread Salvatore Bonaccorso
Source: exiv2
Version: 0.26-1
Severity: grave
Tags: upstream security
Justification: user security hole

Hi,

the following vulnerability was published for exiv2.

CVE-2017-12957[0]:
| There is a heap-based buffer over-read in libexiv2 in Exiv2 0.26 that
| is triggered in the Exiv2::Image::io function in image.cpp. It will
| lead to remote denial of service.

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

For further information see:

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

Regards,
Salvatore



Bug#875535: closed by Matthias Klumpp <m...@debian.org> (Re: Bug#875878: ldc 1.3 doesn't build any of it's reverse dependencies)

2017-09-19 Thread Nobuhiro Iwamatsu
Hi,

sambamba package has not fixed this problem with ldc 1:1.4.0-1.
Also, I confirmed that diet-ng fixed this problem.

-
 dpkg-buildpackage -rfakeroot -us -uc
dpkg-buildpackage: info: source package sambamba
dpkg-buildpackage: info: source version 0.6.6-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Andreas Tille 
 dpkg-source --before-build sambamba-0.6.6
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
dh clean --buildsystem=meson
   dh_auto_clean -O--buildsystem=meson
   dh_autoreconf_clean -O--buildsystem=meson
   dh_clean -O--buildsystem=meson
 dpkg-source -b sambamba-0.6.6
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building sambamba using existing ./sambamba_0.6.6.orig.tar.gz
dpkg-source: info: building sambamba in sambamba_0.6.6-1.debian.tar.xz
dpkg-source: info: building sambamba in sambamba_0.6.6-1.dsc
 debian/rules build
dh build --buildsystem=meson
   dh_update_autotools_config -O--buildsystem=meson
   dh_autoreconf -O--buildsystem=meson
   dh_auto_configure -O--buildsystem=meson
meson .. --wrap-mode=nodownload --buildtype=plain
--prefix=/usr --sysconfdir=/etc --localstatedir=/var
--libdir=lib/x86_64-linux-gnu --libexecdir=lib/x86_64-linux-gnu
Warning: You are using 'ANSI_X3.4-1968' which is not a a
Unicode-compatible locale.
You might see errors if you use UTF-8 strings as filenames, as
strings, or as file contents.
Please switch to a UTF-8 locale for your platform.
The Meson build system
Version: 0.42.1
Source dir: /home/iwa/t3/sambamba-0.6.6
Build dir: /home/iwa/t3/sambamba-0.6.6/obj-x86_64-linux-gnu
Build type: native build
Project name: Sambamba
Native D compiler: ldc2 (llvm 1.4.0)
Appending DFLAGS from environment: '-O2 -g -release'
Appending LDFLAGS from environment: '-Wl,-z,relro'
Build machine cpu family: x86_64
Build machine cpu: x86_64
Found pkg-config: /usr/bin/pkg-config (0.29)
Native dependency undead found: YES 1.0.7
Native dependency biod found: YES 0.1.0
Native dependency liblz4 found: YES 1.8.0
Native dependency htslib found: YES 1.5-1
Program ldmd2 found: YES (/usr/bin/ldmd2)
Program mkdir found: YES (/bin/mkdir)
Build targets in project: 2
   dh_auto_build -O--buildsystem=meson
ninja -j8 -v
[1/74] ldc2  -Isambamba@exe -I. -I.. -I/usr/include/d/
-I/usr/include/htslib -enable-color -O2 -g -release  -of
'sambamba@exe/main.d.o' -c ../main.d
../sambamba/utils/common/readstorage.d(22): Deprecation: module
std.c.stdlib is deprecated - Import core.stdc.stdlib or
core.sys.posix.stdlib instead
../sambamba/utils/common/readstorage.d(23): Deprecation: module
std.c.string is deprecated - Import core.stdc.string instead
../sambamba/utils/common/readstorage.d(23): Deprecation: module
std.c.string is deprecated - Import core.stdc.string instead
../sambamba/sort.d(45): Deprecation: module std.c.stdlib is deprecated
- Import core.stdc.stdlib or core.sys.posix.stdlib instead
../sambamba/sort.d(46): Deprecation: module std.c.string is deprecated
- Import core.stdc.string instead
../sambamba/markdup.d(37): Deprecation: module std.c.stdlib is
deprecated - Import core.stdc.stdlib or core.sys.posix.stdlib instead
../sambamba/depth.d(1154): Deprecation: Implicit string concatenation
is deprecated, use "mapping_quality > 0 and " ~ "not duplicate and "
instead
../sambamba/depth.d(1155): Deprecation: Implicit string concatenation
is deprecated, use "not duplicate and " ~ "not failed_quality_control"
instead
[2/74] ldc2  -Isambamba@exe -I. -I.. -I/usr/include/d/
-I/usr/include/htslib -enable-color -O2 -g -release  -of
'sambamba@exe/sambamba_index.d.o' -c ../sambamba/index.d
[3/74] ldc2  -Isambamba@exe -I. -I.. -I/usr/include/d/
-I/usr/include/htslib -enable-color -O2 -g -release  -of
'sambamba@exe/sambamba_fixbins.d.o' -c ../sambamba/fixbins.d
[4/74] ldc2  -Isambamba@exe -I. -I.. -I/usr/include/d/
-I/usr/include/htslib -enable-color -O2 -g -release  -of
'sambamba@exe/sambamba_depth.d.o' -c ../sambamba/depth.d
FAILED: sambamba@exe/sambamba_depth.d.o
ldc2  -Isambamba@exe -I. -I.. -I/usr/include/d/ -I/usr/include/htslib
-enable-color -O2 -g -release  -of 'sambamba@exe/sambamba_depth.d.o'
-c ../sambamba/depth.d
../sambamba/depth.d(1154): Deprecation: Implicit string concatenation
is deprecated, use "mapping_quality > 0 and " ~ "not duplicate and "
instead
../sambamba/depth.d(1155): Deprecation: Implicit string concatenation
is deprecated, use "not duplicate and " ~ "not failed_quality_control"
instead
/usr/lib/x86_64-linux-gnu/libLLVM-5.0.so.1(_ZN4llvm3sys15PrintStackTraceERNS_11raw_ostreamE+0x1a)[0x7fec38558cda]
/usr/lib/x86_64-linux-gnu/libLLVM-5.0.so.1(_ZN4llvm3sys17RunSignalHandlersEv+0x56)[0x7fec38556fc6]
/usr/lib/x86_64-linux-gnu/libLLVM-5.0.so.1(+0x86e0e3)[0x7fec385570e3]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0)[0x7fec376d10c0]
ldc2(+0x2d6242)[0x59e7bce242]
ldc2(+0x35b517)[0x59e7c53517]
ldc2(+0x35babb)[0x59e7c53abb]
ldc2(+0x31e1d0)[0x59e7c161d0]

Processed: found 813821 in 0.7.5-1.1

2017-09-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> found 813821 0.7.5-1.1
Bug #813821 [src:pynn] pynn: FTBFS: TypeError: 'float' object cannot be 
interpreted as an index
Marked as found in versions pynn/0.7.5-1.1.
> thanks
Stopping processing here.

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



Bug#876240: libghc-xmonad-contrib-dev: unmet dependency libghc-x11-xft-dev-0.3.1-c557c

2017-09-19 Thread Sacha Delanoue

Package: libghc-xmonad-contrib-dev
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I tried to install libghc-xmonad-contrib-dev by doing
`apt install libghc-xmonad-contrib-dev` on an up-to-date 9.1 Debian.
The install failed with the following information:

The following packages have unmet dependencies:
 libghc-xmonad-contrib-dev : Depends: libghc-x11-xft-dev-0.3.1-c557c
E: Unable to correct problems, you have held broken packages.

I am no expert in Debian, but a search on the Internet lead me to this:
https://unix.stackexchange.com/a/392888 stating that this kind of errors
in expected in Sid. But since I am using stable I reported it.


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

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libghc-xmonad-contrib-dev depends on:
ii  ghc [libghc-unix-dev-2.7.2.0-220bd]  8.0.1-17+b1
ii  libc6 
2.24-11+deb9u1

pn  libghc-base-dev-4.9.0.0-5e731
pn  libghc-containers-dev-0.5.7.1-8be09  
pn  libghc-directory-dev-1.2.6.2-958b8   
ii  libghc-extensible-exceptions-dev [libghc-extensible-excepti  0.1.1.4-8
pn  libghc-filepath-dev-1.4.1.0-6e799
ii  libghc-mtl-dev [libghc-mtl-dev-2.2.1-3d1c9]  2.2.1-5
ii  libghc-old-locale-dev [libghc-old-locale-dev-1.0.0.7-38cd4]  1.0.0.7-5
pn  libghc-old-time-dev-1.1.0.3-cc184
pn  libghc-process-dev-1.4.2.0-e39cb 
pn  libghc-random-dev-1.1-84324  
ii  libghc-utf8-string-dev [libghc-utf8-string-dev-1.0.1.1-6f2d 
1.0.1.1-4+b1

ii  libghc-x11-dev [libghc-x11-dev-1.6.1.2-588a9]1.6.1.2-7
pn  libghc-x11-xft-dev-0.3.1-c557c   
ii  libghc-xmonad-dev [libghc-xmonad-dev-0.12-b943d] 0.12-5+b1
ii  libgmp10 
2:6.1.2+dfsg-1

ii  libx11-6 2:1.6.4-3
ii  libx11-dev   2:1.6.4-3
ii  libxext6 
2:1.3.3-1+b2

ii  libxft2  2.3.2-1+b2
ii  libxinerama-dev 
2:1.1.3-1+b3
ii  libxinerama1 
2:1.1.3-1+b3

ii  libxrandr2   2:1.5.1-1

libghc-xmonad-contrib-dev recommends no packages.

Versions of packages libghc-xmonad-contrib-dev suggests:
ii  libghc-xmonad-contrib-doc   0.12-3
pn  libghc-xmonad-contrib-prof  



Bug#876238: gcc-cross-support: FTBFS, wants to regenerate debian/control with more and renamed packages

2017-09-19 Thread Andreas Beckmann
Source: gcc-cross-support
Version: 3
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

gcc-cross-support FTBFS in experimental, tries to regenerate
debian/control in order to rename several packages and add a bunch of
new ones.

Given that the package hasn't seen any upload in the last two years,
maybe it's not needed for the current cross compilers and should rather
be removed than fixed :-)

Build log is attached.


Andreas


gcc-cross-support_3.log.gz
Description: application/gzip


Bug#876236: xmlelements: FTBFS with python3.6 as a supported version

2017-09-19 Thread Andreas Beckmann
Source: xmlelements
Version: 1.0~prerelease-1
Severity: serious
Justification: fails to build from source

Hi,

xmlelements FTBFS (at least) since python3.6 became a supported python3
version:

 debian/rules build
dh build --with=python2,python3
   dh_update_autotools_config
   dh_auto_configure
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/xmlelements-1.0~prerelease'
set -xe; \
for py in python2.7 python3.6 python3.5; do \
$py setup.py build; \
done
+ python2.7 setup.py build
running build
running build_py
creating build
creating build/lib.linux-x86_64-2.7
copying xe.py -> build/lib.linux-x86_64-2.7
+ python3.6 setup.py build
/bin/sh: 3: python3.6: not found
debian/rules:10: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 127
make[1]: Leaving directory '/build/xmlelements-1.0~prerelease'
debian/rules:28: recipe for target 'build' failed
make: *** [build] Error 2


Andreas


xmlelements_1.0~prerelease-1.log.gz
Description: application/gzip


Processed: closing 870811, found 870811 in 1.50a+dfsg1-3

2017-09-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> close 870811 1.50a+dfsg1-3+deb9u1
Bug #870811 [src:iortcw] CVE-2017-11721: read buffer overflow in MSG_ReadBits
Marked as fixed in versions iortcw/1.50a+dfsg1-3+deb9u1.
Bug #870811 [src:iortcw] CVE-2017-11721: read buffer overflow in MSG_ReadBits
Marked Bug as done
> found 870811 1.50a+dfsg1-3
Bug #870811 {Done: Simon McVittie } [src:iortcw] 
CVE-2017-11721: read buffer overflow in MSG_ReadBits
Marked as found in versions iortcw/1.50a+dfsg1-3.
> thanks
Stopping processing here.

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



Bug#870811: closing 870811, found 870811 in 1.50a+dfsg1-3

2017-09-19 Thread Simon McVittie
close 870811 1.50a+dfsg1-3+deb9u1
found 870811 1.50a+dfsg1-3
thanks

CVE-2017-11721 has been fixed in iortcw in all applicable suites.



Bug#876222: Should be in "contrib", not "main"

2017-09-19 Thread Wookey
On 2017-09-19 12:27 -0700, Josh Triplett wrote:
> Package: mali-midgard-dkms
> Severity: serious
> 
> The package description says:
> 
> > This provides the kernel module for the ARM Mali 'midgard' GPU series
> > in dkms format. This covers the 6xx and 7xx GPU hardware devices. You
> > need this kernel module as well the binary drivers to make the
> > hardware work.
> 
> If that's the case, and this kernel module doesn't do any good without
> the binary drivers, then this package should go to "contrib", not
> "main".

That's a good point. The plan was always to upload it to contrib originally,
but clearly I have failed to actually do so.
 
> If this kernel module has uses without the binary drivers (e.g. if it
> can be made to work with the reverse-engineered driver instead), then
> the description should make that clear.

The mali reverse-engineering effort has recently restarted after being
moribund for a few years, (https://github.com/yuq/mesa-lima) and it's
possible that this driver will be useful there, but I don't know that
yet. I'll check with that project and unless there is a prospect of
this driver being used by free software I'll move it.

Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/


signature.asc
Description: Digital signature


Bug#876235: python-autobahn: missing B-D: openstack-pkg-tools

2017-09-19 Thread Andreas Beckmann
Source: python-autobahn
Version: 17.7.1+dfsg1-1
Severity: serious
Justification: fails to build from source

Hi,

python-autobahn/experimental FTBFS with

dh: Unknown sequence /usr/share/openstack-pkg-tools/pkgos.make (choose
from: binary binary-arch binary-indep build build-arch build-indep clean
install install-arch install-indep)


Andreas


python-autobahn_17.7.1+dfsg1-1.log.gz
Description: application/gzip


Bug#876232: quassel-irssi: FTBFS with GCC 7 thanks to usage of -Werror

2017-09-19 Thread Andreas Beckmann
Source: quassel-irssi
Version: 0~git20170114-1
Severity: serious
Justification: fails to build from source

Hi,

quassel-irssi FTBFS (at least) since GCC 7 was made the default compiler
(and added some new warnings):


   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/quassel-irssi-0~git20170114'
/usr/bin/make -C core
make[2]: Entering directory '/build/quassel-irssi-0~git20170114/core'
cc -std=gnu11 -Wall -Wextra -Werror -g -O2 -I/usr/include/irssi//src/ 
-I/usr/include/irssi//src/core/ -I/usr/include/irssi//src/fe-common/ 
-I/usr/include/irssi//src/fe-common/core/ -I/usr/include/irssi//src/fe-text/ 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-DUOFF_T_LONG -fPIC -DHAVE_OPENSSL -I/usr/include/quasselc -Wmissing-prototypes 
-Wmissing-declarations  -Wdate-time -D_FORTIFY_SOURCE=2  -c -o 
quasselc-connector.o quasselc-connector.c
quasselc-connector.c: In function 'handle_sync':
quasselc-connector.c:146:6: error: this statement may fall through 
[-Werror=implicit-fallthrough=]
if(!fnc)
  ^
quasselc-connector.c:148:3: note: here
   case Displayed:
   ^~~~
quasselc-connector.c:156:6: error: this statement may fall through 
[-Werror=implicit-fallthrough=]
if(!fnc)
  ^
quasselc-connector.c:158:3: note: here
   case TempRemoved:
   ^~~~
quasselc-connector.c:211:6: error: this statement may fall through 
[-Werror=implicit-fallthrough=]
if(!fnc)
  ^
...


Andreas


quassel-irssi_0~git20170114-1.log.gz
Description: application/gzip


Bug#876231: ruby-nmatrix: FTBFS with GCC 7: error: call of overloaded 'abs(nm::Rational&)' is ambiguous

2017-09-19 Thread Andreas Beckmann
Package: ruby-nmatrix
Version: 0.1.0~rc3-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

ruby-nmatrix FTBFS (at least) since GCC 7 was made the default compiler:

In file included from math.cpp:125:0:
math/idamax.h: In instantiation of 'int nm::math::idamax(size_t, DType*, int) 
[with DType = nm::Rational; size_t = long unsigned int]':
math/getrf.h:153:44:   required from 'int nm::math::getrf_nothrow(int, int, 
DType*, int, int*) [with bool RowMajor = true; DType = nm::Rational]'
math/getrf.h:211:37:   required from 'int nm::math::getrf(CBLAS_ORDER, int, 
int, DType*, int, int*) [with DType = nm::Rational]'
math/getrf.h:234:22:   required from 'int nm::math::clapack_getrf(CBLAS_ORDER, 
int, int, void*, int, int*) [with DType = nm::Rational]'
math.cpp:1295:3:   required from here
math/idamax.h:60:15: error: call of overloaded 'abs(nm::Rational&)' 
is ambiguous
 dmax = abs(dx[0]);
~~~^~~
In file included from /usr/include/c++/7/cstdlib:75:0,
 from /usr/include/c++/7/bits/stl_algo.h:59,
 from /usr/include/c++/7/algorithm:62,
 from math.cpp:116:
/usr/include/stdlib.h:735:12: note: candidate: int abs(int)
 extern int abs (int __x) __THROW __attribute__ ((__const__)) __wur;
^~~
In file included from /usr/include/c++/7/cstdlib:77:0,
 from /usr/include/c++/7/bits/stl_algo.h:59,
 from /usr/include/c++/7/algorithm:62,
 from math.cpp:116:
/usr/include/c++/7/bits/std_abs.h:56:3: note: candidate: long int std::abs(long 
int)
   abs(long __i) { return __builtin_labs(__i); }
   ^~~
/usr/include/c++/7/bits/std_abs.h:61:3: note: candidate: long long int 
std::abs(long long int)
   abs(long long __x) { return __builtin_llabs (__x); }
   ^~~
/usr/include/c++/7/bits/std_abs.h:70:3: note: candidate: constexpr double 
std::abs(double)
   abs(double __x)
   ^~~
/usr/include/c++/7/bits/std_abs.h:74:3: note: candidate: constexpr float 
std::abs(float)
   abs(float __x)
   ^~~
/usr/include/c++/7/bits/std_abs.h:78:3: note: candidate: constexpr long double 
std::abs(long double)
   abs(long double __x)
   ^~~


Full log attached.

Andreas


ruby-nmatrix_0.1.0~rc3-2.log.gz
Description: application/gzip


Processed: unarchiving 828550, found 828550 in 2.0.0~beta9-1

2017-09-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> unarchive 828550
Bug #828550 {Done: Laszlo Boszormenyi (GCS) } [src:socat] 
socat: FTBFS with openssl 1.1.0
Unarchived Bug 828550
> found 828550 2.0.0~beta9-1
Bug #828550 {Done: Laszlo Boszormenyi (GCS) } [src:socat] 
socat: FTBFS with openssl 1.1.0
Marked as found in versions socat/2.0.0~beta9-1 and reopened.
> thanks
Stopping processing here.

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



Bug#876230: ssh-askpass-fullscreen: FTBFS: undefined reference to symbol 'XUngrabServer'

2017-09-19 Thread Andreas Beckmann
Source: ssh-askpass-fullscreen
Version: 0.4-0.1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

ssh-askpass-fullscreen/experimental FTBFS in a current
sid/experimental environment:

 debian/rules build
dh build
   dh_update_autotools_config
   dh_auto_configure
   dh_auto_build
make -j1
make[1]: Entering directory '/build/ssh-askpass-fullscreen-0.4'
cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/build/ssh-askpass-fullscreen-0.4=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now -o 
ssh-askpass-fullscreen ssh-askpass-fullscreen.c `pkg-config --libs gtk+-2.0` 
`pkg-config --cflags gtk+-2.0`
ssh-askpass-fullscreen.c: In function 'passphrase_dialog':
ssh-askpass-fullscreen.c:275:40: warning: passing argument 1 of 
'gdk_pixbuf_new_from_xpm_data' from incompatible pointer type 
[-Wincompatible-pointer-types]
  pixbuf = gdk_pixbuf_new_from_xpm_data(ocean_stripes);
^
In file included from /usr/include/gdk-pixbuf-2.0/gdk-pixbuf/gdk-pixbuf.h:34:0,
 from /usr/include/gtk-2.0/gdk/gdkpixbuf.h:37,
 from /usr/include/gtk-2.0/gdk/gdkcairo.h:28,
 from /usr/include/gtk-2.0/gdk/gdk.h:33,
 from /usr/include/gtk-2.0/gdk/gdkprivate.h:30,
 from /usr/include/gtk-2.0/gdk/gdkx.h:30,
 from ssh-askpass-fullscreen.c:43:
/usr/include/gdk-pixbuf-2.0/gdk-pixbuf/gdk-pixbuf-core.h:351:12: note: expected 
'const char **' but argument is of type 'char **'
 GdkPixbuf *gdk_pixbuf_new_from_xpm_data (const char **data);
^~~~
/usr/bin/ld: /tmp/cc2IPa2e.o: undefined reference to symbol 'XUngrabServer'
//usr/lib/x86_64-linux-gnu/libX11.so.6: error adding symbols: DSO missing from 
command line
collect2: error: ld returned 1 exit status
Makefile:2: recipe for target 'all' failed
make[1]: *** [all] Error 1
make[1]: Leaving directory '/build/ssh-askpass-fullscreen-0.4'
dh_auto_build: make -j1 returned exit code 2
debian/rules:6: recipe for target 'build' failed
make: *** [build] Error 2


Andreas


ssh-askpass-fullscreen_0.4-0.1.log.gz
Description: application/gzip


Bug#858491: marked as done (gdk-pixbuf: CVE-2017-6311: crash in gdk-pixbuf-thumbnailer)

2017-09-19 Thread Debian Bug Tracking System
Your message dated Tue, 19 Sep 2017 19:28:43 -0400
with message-id 

and subject line Re: gdk-pixbuf: CVE-2017-6311: crash in gdk-pixbuf-thumbnailer
has caused the Debian Bug report #858491,
regarding gdk-pixbuf: CVE-2017-6311: crash in gdk-pixbuf-thumbnailer
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.)


-- 
858491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858491
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgdk-pixbuf2.0-bin
Severity: serious
Version: 2.36.5-3
Tags: security upstream
Forwarded: https://bugzilla.gnome.org/show_bug.cgi?id=778204

gnome-desktop3 3.24 dropped its thumbnailer code to use gdk-pixbuf's.
Therefore, the Debian GNOME team is introducing gdk-pixbuf's
thumbnailer into Debian after stretch.

The following vulnerability was published for gdk-pixbuf.

CVE-2017-6311[0]:

gdk-pixbuf-thumbnailer.c in gdk-pixbuf allows context-dependent
attackers to cause a denial of service (NULL pointer dereference and
application crash) via vectors related to printing an error message.

There is no patch upstream yet.

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

For further information see:

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

I am setting this bug severity to serious so that we won't
accidentally have this migrate to testing until someone looks into
this more.

Thank you,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 2.36.10-1

This was fixed in upstream 2.36.8.

Thanks,
Jeremy Bicha--- End Message ---


Bug#876033: primusrun doesn't find libGL.so.1

2017-09-19 Thread Bernd Vaske

Hello,

the problem comes from the transition of mesa to glvnd.
A workaround is to link the missing libs from

/usr/lib/x86_64-linux-gnu/libGL.so.1 to 
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1

and
/usr/lib/i386-linux-gnu/libGL.so.1 to 
/usr/lib/i386-linux-gnu/nvidia/libGL.so.1


That will result in primusrun starting again but most likely resulting 
in a black window for the application which is started.


To get primusrun to work properly you have to start it with 
__GLVND_DISALLOW_PATCHING=1


example:

__GLVND_DISALLOW_PATCHING=1 primusrun glxgears

Best regards



Bug#876229: apport: FTBFS: B-D: libglib2.0-0-dbg is no longer available

2017-09-19 Thread Andreas Beckmann
Source: apport
Version: 2.20.4-2
Severity: serious
Justification: fails to build from source

# apt-get build-dep apport
Reading package lists... Done
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 builddeps:apport : Depends: libglib2.0-0-dbg but it is not installable
E: Unable to correct problems, you have held broken packages.


Andreas



Bug#874552: marked as done (gdk-pixbuf: CVE-2017-2862: JPEG gdk_pixbuf__jpeg_image_load_increment Code Execution Vulnerability)

2017-09-19 Thread Debian Bug Tracking System
Your message dated Tue, 19 Sep 2017 22:05:02 +
with message-id 
and subject line Bug#874552: fixed in gdk-pixbuf 2.36.10-1
has caused the Debian Bug report #874552,
regarding gdk-pixbuf: CVE-2017-2862: JPEG gdk_pixbuf__jpeg_image_load_increment 
Code Execution Vulnerability
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.)


-- 
874552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874552
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gdk-pixbuf
Version: 2.36.5-1
Severity: grave
Tags: upstream patch security
Forwarded: https://bugzilla.gnome.org/show_bug.cgi?id=784866

Hi,

the following vulnerability was published for gdk-pixbuf.

CVE-2017-2862[0]:
| An exploitable heap overflow vulnerability exists in the
| gdk_pixbuf__jpeg_image_load_increment functionality of Gdk-Pixbuf
| 2.36.6. A specially crafted jpeg file can cause a heap overflow
| resulting in remote code execution. An attacker can send a file or url
| to trigger this vulnerability.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-2862
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-2862
[1] https://bugzilla.gnome.org/show_bug.cgi?id=784866

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: gdk-pixbuf
Source-Version: 2.36.10-1

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

Debian distribution maintenance software
pp.
Emilio Pozuelo Monfort  (supplier of updated gdk-pixbuf 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 19 Sep 2017 23:39:30 +0200
Source: gdk-pixbuf
Binary: libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-bin libgdk-pixbuf2.0-common 
libgdk-pixbuf2.0-dev libgdk-pixbuf2.0-doc libgdk-pixbuf2.0-0-udeb 
gir1.2-gdkpixbuf-2.0
Architecture: source
Version: 2.36.10-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Emilio Pozuelo Monfort 
Description:
 gir1.2-gdkpixbuf-2.0 - GDK Pixbuf library - GObject-Introspection
 libgdk-pixbuf2.0-0 - GDK Pixbuf library
 libgdk-pixbuf2.0-0-udeb - GDK Pixbuf library - minimal runtime (udeb)
 libgdk-pixbuf2.0-bin - GDK Pixbuf library (thumbnailer)
 libgdk-pixbuf2.0-common - GDK Pixbuf library - data files
 libgdk-pixbuf2.0-dev - GDK Pixbuf library (development files)
 libgdk-pixbuf2.0-doc - GDK Pixbuf library (documentation)
Closes: 874552 875704
Changes:
 gdk-pixbuf (2.36.10-1) unstable; urgency=medium
 .
   [ Jeremy Bicha ]
   * New upstream release 2.36.9.
   * Drop obsolete 0001-skip-perturb-for-cve-2015-4491-original-test.patch
   * debian/libgdk-pixbuf2.0-0.symbols: Add new symbol
 .
   [ Emilio Pozuelo Monfort ]
   * New upstream release 2.36.10.
 - CVE-2017-2862: fix code execution vulnerability in jpeg loader.
   Closes: #874552.
   * Switch to copyright format 1.0.
   * copyright: exclude non-free test ref images.
   * rules: drop obsolete dh_strip --dbgsym-migration switch.
   * postinst: make loaders.cache reproducible. Thanks Chris Lamb for the
 patch. Closes: #875704.
Checksums-Sha1:
 9b2275f6d86b4fc9a32b48b477ef161645a618d7 2925 gdk-pixbuf_2.36.10-1.dsc
 1d0a8e77214d59645473535f5efb2d7837d05750 5497116 gdk-pixbuf_2.36.10.orig.tar.xz
 4e866228368033ab943bf0df9574dc5c99a15610 13468 
gdk-pixbuf_2.36.10-1.debian.tar.xz
 7b568a4b5b52c4fb71b9fb52733aa57d9fbcd987 7811 
gdk-pixbuf_2.36.10-1_source.buildinfo
Checksums-Sha256:
 ef75ef876dc753c3454f6634a452385dd60404b8e3d4076a11cf60d51345245d 2925 
gdk-pixbuf_2.36.10-1.dsc
 9226eee3be46811d25e3f2d9a1267ad6d8e78d9af95d8bc68d6556e92f3f0aaf 5497116 
gdk-pixbuf_2.36.10.orig.tar.xz
 c2c77ec156d79af102d57d1cadbafac5d36dec9445fd7e1705f3d50884d51ebf 13468 
gdk-pixbuf_2.36.10-1.debian.tar.xz
 

Bug#853606: marked as done (pcre3: ftbfs with GCC-7)

2017-09-19 Thread Debian Bug Tracking System
Your message dated Tue, 19 Sep 2017 21:51:29 +
with message-id 
and subject line Bug#853606: fixed in pcre3 2:8.39-5
has caused the Debian Bug report #853606,
regarding pcre3: ftbfs with GCC-7
to be marked as done.

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

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


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

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]
dh_testroot -a
dh_install -a
dh_install: Compatibility levels before 9 are deprecated (level 5 in use)
# This man page is in the main package, don't want it in -dev
rm debian/libpcre3-dev/usr/share/man/man3/pcrepattern.3
# Move actual library to /lib
mkdir -p debian/libpcre3/lib/x86_64-linux-gnu
mv debian/libpcre3/usr/lib/x86_64-linux-gnu/libpcre.so.* 
debian/libpcre3/lib/x86_64-linux-gnu
ln -sf /lib/x86_64-linux-gnu/libpcre.so.3 
debian/libpcre3-dev/usr/lib/x86_64-linux-gnu/libpcre.so
# we never need to reference the library path in pcre-config on
# Debian, so clip it out so that the script will be multiarch-safe.
sed -i -e"s,/x86_64-linux-gnu,,g" debian/libpcre3-dev/usr/bin/pcre-config
dh_link -a
dh_link: Compatibility levels before 9 are deprecated (level 5 in use)
dh_installdocs -a
dh_installdocs: Compatibility levels before 9 are deprecated (level 5 in use)
dh_installexamples -a
dh_installexamples: Compatibility levels before 9 are deprecated (level 5 in 
use)
dh_installman -a
dh_installman: Compatibility levels before 9 are deprecated (level 5 in use)
dh_installinfo -a
dh_installchangelogs -a ChangeLog
dh_strip -a --dbg-package=libpcre3-dbg
dh_strip: Compatibility levels before 9 are deprecated (level 5 in use)
# Don't include pcregrep or libraries from udeb in debug package
rm -r debian/libpcre3-dbg/usr/lib/debug/usr/bin 
rm debian/libpcre3-dbg/usr/lib/debug/usr/lib/libpcre*
dh_compress -a
dh_fixperms -a
sed -e 's/JIT//' debian/libpcre3.symbols.in > debian/libpcre3.symbols
sed -e 's/JIT//' debian/libpcre16-3.symbols.in > debian/libpcre16-3.symbols
sed -e 's/JIT//' debian/libpcre32-3.symbols.in > debian/libpcre32-3.symbols
dh_makeshlibs -plibpcre3 --add-udeb="libpcre3-udeb" -V 'libpcre3 (>= 1:8.35)' 
-- -c4
dh_makeshlibs: Compatibility levels before 9 are deprecated (level 5 in use)
dh_makeshlibs -plibpcrecpp0v5 -V 'libpcrecpp0v5 (>= 7.7)' -- -c4
dh_makeshlibs: Compatibility levels before 9 are deprecated (level 5 in use)
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: warning: debian/libpcrecpp0v5/DEBIAN/symbols doesn't match 
completely debian/libpcrecpp0v5.symbols
--- debian/libpcrecpp0v5.symbols (libpcrecpp0v5_2:8.39-2_amd64)
+++ dpkg-gensymbolsvaNnIq   2017-01-27 13:13:11.14400 +
@@ -1,4 +1,5 @@
 libpcrecpp.so.0 libpcrecpp0v5 #MINVER#
+ 
_ZNSt6vectorIN7pcrecpp11StringPieceESaIS1_EE17_M_realloc_insertIJRKS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
 2:8.39-2
  (c++)"operator<<(std::basic_ostream&, 
pcrecpp::StringPiece const&)@Base" 8.38
  (c++)"pcrecpp::Arg::parse_char(char const*, int, void*)@Base" 7.7
  (c++)"pcrecpp::Arg::parse_double(char const*, int, void*)@Base" 7.7
dh_makeshlibs: failing due to earlier errors
debian/rules:89: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 255

Processed: limit source to gdk-pixbuf, tagging 874552, tagging 875704

2017-09-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

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

> tags 874552 + pending
Bug #874552 [src:gdk-pixbuf] gdk-pixbuf: CVE-2017-2862: JPEG 
gdk_pixbuf__jpeg_image_load_increment Code Execution Vulnerability
Ignoring request to alter tags of bug #874552 to the same tags previously set
> tags 875704 + pending
Bug #875704 [src:gdk-pixbuf] gdk-pixbuf: please make the output of 
gdk-pixbuf-query-loaders reproducible
Added tag(s) pending.
> thanks
Stopping processing here.

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



Processed: limit source to gdk-pixbuf, tagging 874552

2017-09-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

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

> tags 874552 + pending
Bug #874552 [src:gdk-pixbuf] gdk-pixbuf: CVE-2017-2862: JPEG 
gdk_pixbuf__jpeg_image_load_increment Code Execution Vulnerability
Added tag(s) pending.
> thanks
Stopping processing here.

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



Processed: tagging 876221

2017-09-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 876221 + pending
Bug #876221 [tor] log uninitialized stack in non-default configuration 
[CVE-2017-0380]
Added tag(s) pending.
> thanks
Stopping processing here.

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



Bug#875878: marked as done (ldc 1.3 doesn't build any of it's reverse dependencies)

2017-09-19 Thread Debian Bug Tracking System
Your message dated Tue, 19 Sep 2017 22:14:44 +0200
with message-id 

and subject line Re: Bug#875878: ldc 1.3 doesn't build any of it's reverse 
dependencies
has caused the Debian Bug report #875878,
regarding ldc 1.3 doesn't build any of it's reverse dependencies
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.)


-- 
875878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875878
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ldc
Version: 1:1.3.0-2
Severity: serious
Tags: sid buster
Forwarded: https://github.com/ldc-developers/ldc/issues/2300

ldc 1.3 doesn't build any of it's reverse dependencies. See the upstream issue.
--- End Message ---
--- Begin Message ---
Source: ldc
Source-Version: 1:1.4.0-1

It appears like this magically fixed itself when building LDC 1.4.0
against LLVM 5. Apparently, this was an LLVM issue, or some weird bug
in how LLVM was used by LDC.

Cheers,
Matthias

-- 
I welcome VSRE emails. See http://vsre.info/--- End Message ---


Bug#875535: marked as done (ldc 1.3 doesn't build any of it's reverse dependencies)

2017-09-19 Thread Debian Bug Tracking System
Your message dated Tue, 19 Sep 2017 22:14:44 +0200
with message-id 

and subject line Re: Bug#875878: ldc 1.3 doesn't build any of it's reverse 
dependencies
has caused the Debian Bug report #875878,
regarding ldc 1.3 doesn't build any of it's reverse dependencies
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.)


-- 
875878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875878
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sambamba
Version: 0.6.6-1
Severity: serious
Tags: buster sid
Justification: FTBFS on amd64

Dear Maintainer,

sambamba FTBFS on sid.

https://buildd.debian.org/status/fetch.php?pkg=sambamba=amd64=0.6.6-1%2Bb1=1504167027=0

--
Build targets in project: 2
   dh_auto_build -a -O--buildsystem=meson
ninja -j4 -v
[1/74] ldc2  -Isambamba@exe -I. -I.. -I/usr/include/d/
-I/usr/include/htslib -enable-color -O3 -g -release  -of
'sambamba@exe/main.d.o' -c ../main.d
../sambamba/utils/common/readstorage.d(22): Deprecation: module
std.c.stdlib is deprecated - Import core.stdc.stdlib or
core.sys.posix.stdlib instead
../sambamba/utils/common/readstorage.d(23): Deprecation: module
std.c.string is deprecated - Import core.stdc.string instead
../sambamba/sort.d(45): Deprecation: module std.c.stdlib is deprecated
- Import core.stdc.stdlib or core.sys.posix.stdlib instead
../sambamba/sort.d(46): Deprecation: module std.c.string is deprecated
- Import core.stdc.string instead
../sambamba/markdup.d(37): Deprecation: module std.c.stdlib is
deprecated - Import core.stdc.stdlib or core.sys.posix.stdlib instead
../sambamba/depth.d(1154): Deprecation: Implicit string concatenation
is deprecated, use "mapping_quality > 0 and " ~ "not duplicate and "
instead
../sambamba/depth.d(1155): Deprecation: Implicit string concatenation
is deprecated, use "not duplicate and " ~ "not failed_quality_control"
instead
[2/74] ldc2  -Isambamba@exe -I. -I.. -I/usr/include/d/
-I/usr/include/htslib -enable-color -O3 -g -release  -of
'sambamba@exe/sambamba_fixbins.d.o' -c ../sambamba/fixbins.d
[3/74] ldc2  -Isambamba@exe -I. -I.. -I/usr/include/d/
-I/usr/include/htslib -enable-color -O3 -g -release  -of
'sambamba@exe/sambamba_depth.d.o' -c ../sambamba/depth.d
FAILED: sambamba@exe/sambamba_depth.d.o
ldc2  -Isambamba@exe -I. -I.. -I/usr/include/d/ -I/usr/include/htslib
-enable-color -O3 -g -release  -of 'sambamba@exe/sambamba_depth.d.o'
-c ../sambamba/depth.d
../sambamba/depth.d(1154): Deprecation: Implicit string concatenation
is deprecated, use "mapping_quality > 0 and " ~ "not duplicate and "
instead
../sambamba/depth.d(1155): Deprecation: Implicit string concatenation
is deprecated, use "not duplicate and " ~ "not failed_quality_control"
instead
0  libLLVM-4.0.so.1 0x7fdf83fb4f45
llvm::sys::PrintStackTrace(llvm::raw_ostream&) + 37
1  libLLVM-4.0.so.1 0x7fdf83fb31a6 llvm::sys::RunSignalHandlers() + 86
2  libLLVM-4.0.so.1 0x7fdf83fb32c3
3  libpthread.so.0  0x7fdf8321b0c0
4  ldc2 0x562179492ee2
5  ldc2 0x562179518017
6  ldc2 0x5621795185dc
7  ldc2 0x5621794dc090
8  ldc2 0x5621794d5be1
9  ldc2 0x5621794e1696
10 ldc2 0x5621794d7041
11 ldc2 0x5621794c4dfd
12 ldc2 0x5621794c3bc4
13 ldc2 0x5621794c1dd4
14 ldc2 0x56217948be81
15 ldc2 0x562179482b00
16 ldc2 0x562179482c9b
17 ldc2 0x562179483564
18 ldc2 0x56217949e915
19 ldc2 0x562179534dc2
20 ldc2 0x56217950ded9
21 ldc2 0x5621793ffa0d
22 ldc2 0x56217951072a
23 ldc2 0x56217955b35f
24 ldc2 0x56217955b324
25 ldc2 0x56217955b250
26 libc.so.60x7fdf825f32e1 __libc_start_main + 241
27 ldc2 0x5621792b57ea
Segmentation fault
[4/74] ldc2  -Isambamba@exe -I. -I.. -I/usr/include/d/
-I/usr/include/htslib -enable-color -O3 -g -release  -of
'sambamba@exe/sambamba_index.d.o' -c ../sambamba/index.d
[5/74] ldc2  -Isambamba@exe -I. -I.. -I/usr/include/d/
-I/usr/include/htslib -enable-color -O3 -g -release  -of
'sambamba@exe/sambamba_flagstat.d.o' -c ../sambamba/flagstat.d
[6/74] ldc2  -Isambamba@exe -I. -I.. -I/usr/include/d/
-I/usr/include/htslib -enable-color -O3 -g -release  -of
'sambamba@exe/sambamba_markdup.d.o' -c ../sambamba/markdup.d
FAILED: sambamba@exe/sambamba_markdup.d.o
ldc2  -Isambamba@exe -I. -I.. 

Bug#876222: Should be in "contrib", not "main"

2017-09-19 Thread Josh Triplett
Package: mali-midgard-dkms
Severity: serious

The package description says:

> This provides the kernel module for the ARM Mali 'midgard' GPU series
> in dkms format. This covers the 6xx and 7xx GPU hardware devices. You
> need this kernel module as well the binary drivers to make the
> hardware work.

If that's the case, and this kernel module doesn't do any good without
the binary drivers, then this package should go to "contrib", not
"main".

If this kernel module has uses without the binary drivers (e.g. if it
can be made to work with the reverse-engineered driver instead), then
the description should make that clear.

- Josh Triplett



Bug#876221: log uninitialized stack in non-default configuration [CVE-2017-0380]

2017-09-19 Thread Peter Palfrader
Package: tor
Severity: serious
Version: 0.2.7.2-alpha-1
Control: forwarded -1 https://bugs.torproject.org/23490

tor could log uninitialized stack when a certain hidden service error occurred
while SafeLogging was disabled.

This is also tracked as TROVE-2017-008 and CVE-2017-0380.

-- 
|  .''`.   ** Debian **
  Peter Palfrader   | : :' :  The  universal
 https://www.palfrader.org/ | `. `'  Operating System
|   `-https://www.debian.org/



Processed: log uninitialized stack in non-default configuration [CVE-2017-0380]

2017-09-19 Thread Debian Bug Tracking System
Processing control commands:

> forwarded -1 https://bugs.torproject.org/23490
Bug #876221 [tor] log uninitialized stack in non-default configuration 
[CVE-2017-0380]
Set Bug forwarded-to-address to 'https://bugs.torproject.org/23490'.

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



Bug#876219: banshee: FTBFS: configure: error: missing required Mono 2.0 assembly: Mono.Posix.dll

2017-09-19 Thread Andreas Beckmann
Source: banshee
Version: 2.9.1-5
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

banshee/experimental FTBFS in sid/experimental with

...
checking for MONO_MODULE... yes
checking for dmcs... /usr/bin/mono-csc
checking for mono... /usr/bin/mono
checking for Mono 2.0 GAC for Mono.Posix.dll... not found
configure: error: missing required Mono 2.0 assembly: Mono.Posix.dll
...

Full log attached.


Andreas


banshee_2.9.1-5.log.gz
Description: application/gzip


Bug#876218: libneo4j-client: FTBFS with "output truncated before the last format character"

2017-09-19 Thread Andreas Beckmann
Source: libneo4j-client
Version: 2.1.2-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

libneo4j-client/experimental FTBFS with GCC 7:

libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time 
-D_FORTIFY_SOURCE=2 -pthread -Wpedantic -Wvla -g -O2 
-fdebug-prefix-map=/build/libneo4j-client-2.1.2=. -fstack-protector-strong 
-Wformat -Werror=format-security -
std=gnu11 -fvisibility=hidden -pipe -Wall -W -Werror -Wno-unused-parameter 
-Wno-missing-field-initializers -Wpointer-arith -Wstrict-prototypes -Wcast-qual 
-Wcast-align -Wno-error=unused-function -Wno-error=unused-variable -Wn
o-error=deprecated-declarations -c render.c  -fPIC -DPIC -o 
.libs/libneo4j_client_la-render.o
render.c: In function 'render_field':
render.c:610:17: error: '__builtin___snprintf_chk' output truncated before the 
last format character [-Werror=format-truncation=]
 if (snprintf(buf, sizeof(buf), "\\U%08X", codepoint) < 0)
 ^~~~
In file included from /usr/include/stdio.h:938:0,
 from neo4j-client.h:27,
 from render.h:20,
 from render.c:18:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:64:10: note: 
'__builtin___snprintf_chk' output 11 bytes into a destination of size 10
   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
  ^~~~
__bos (__s), __fmt, __va_arg_pack ());
~
cc1: all warnings being treated as errors
Makefile:688: recipe for target 'libneo4j_client_la-render.lo' failed
make[4]: *** [libneo4j_client_la-render.lo] Error 1


Full log attached.


Andreas


libneo4j-client_2.1.2-1.log.gz
Description: application/gzip


Bug#876216: pyfeed: FTBFS with python3.6 as a supported version

2017-09-19 Thread Andreas Beckmann
Source: pyfeed
Version: 1.0~prerelease-1
Severity: serious
Justification: fails to build from source

Hi,

pyfeed/experimental FTBFS (at least) since python3.6 became a supported
version:

   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/pyfeed-1.0~prerelease'
set -xe; \
for py in python2.7 python3.6 python3.5; do \
$py setup.py build; \
done
+ python2.7 setup.py build
running build
running build_py
creating build
creating build/lib.linux-x86_64-2.7
creating build/lib.linux-x86_64-2.7/feed
copying feed/atom.py -> build/lib.linux-x86_64-2.7/feed
copying feed/rss.py -> build/lib.linux-x86_64-2.7/feed
copying feed/opml1.py -> build/lib.linux-x86_64-2.7/feed
copying feed/opml.py -> build/lib.linux-x86_64-2.7/feed
copying feed/__init__.py -> build/lib.linux-x86_64-2.7/feed
copying feed/tools.py -> build/lib.linux-x86_64-2.7/feed
creating build/lib.linux-x86_64-2.7/feed/date
copying feed/date/__init__.py -> build/lib.linux-x86_64-2.7/feed/date
copying feed/date/rfc822.py -> build/lib.linux-x86_64-2.7/feed/date
copying feed/date/tools.py -> build/lib.linux-x86_64-2.7/feed/date
copying feed/date/rfc3339.py -> build/lib.linux-x86_64-2.7/feed/date
+ python3.6 setup.py build
/bin/sh: 3: python3.6: not found
debian/rules:10: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 127


Full log attached.

Andreas


pyfeed_1.0~prerelease-1.log.gz
Description: application/gzip


Bug#876143: marked as done (udisks2-btrfs: Dependency on libblockdev-btrfs should be libblockdev-btrfs2)

2017-09-19 Thread Debian Bug Tracking System
Your message dated Tue, 19 Sep 2017 18:49:38 +
with message-id 
and subject line Bug#876143: fixed in udisks2 2.7.3-4
has caused the Debian Bug report #876143,
regarding udisks2-btrfs: Dependency on libblockdev-btrfs should be 
libblockdev-btrfs2
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.)


-- 
876143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876143
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: udisks2-btrfs
Version: 2.7.3-3

Dear Utopia maintainers,

udisks2-btrfs depends on libblockdev-btrfs which doesn't exist.

What exists is libblockdev-btrfs2, so I assume there is a "2" missing in
that dependency.

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

Kernel: Linux 4.13.0-rc7-amd64 (SMP w/8 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
Source: udisks2
Source-Version: 2.7.3-4

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

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated udisks2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 19 Sep 2017 20:35:55 +0200
Source: udisks2
Binary: udisks2 udisks2-btrfs udisks2-lvm2 udisks2-doc libudisks2-0 
libudisks2-dev gir1.2-udisks-2.0
Architecture: source
Version: 2.7.3-4
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Michael Biebl 
Description:
 gir1.2-udisks-2.0 - GObject based library to access udisks2 - introspection 
data
 libudisks2-0 - GObject based library to access udisks2
 libudisks2-dev - GObject based library to access udisks2 - development files
 udisks2- D-Bus service to access and manipulate storage devices
 udisks2-btrfs - BTRFS support for udisks2
 udisks2-doc - udisks2 documentation
 udisks2-lvm2 - LVM2 support for udisks2
Closes: 876143
Changes:
 udisks2 (2.7.3-4) unstable; urgency=medium
 .
   * Fix dependency of udisks2-btrfs on libblockdev-btrfs2 (Closes: #876143)
Checksums-Sha1:
 ae1bba6d00340b162cca1489603f17d55c909a18 3152 udisks2_2.7.3-4.dsc
 de27284a8d3b40d47e191edc385a7b48e4e6e170 13940 udisks2_2.7.3-4.debian.tar.xz
 db3bee3ce68f1e526d26829d1385ff257a4ecff3 15894 udisks2_2.7.3-4_source.buildinfo
Checksums-Sha256:
 a8ce8ff1996c942b222c35a911957d2ea4f8d8a913dc4e0babca13cdb2487cd6 3152 
udisks2_2.7.3-4.dsc
 eb008448592173307f6492051154b2b85efda2a72d8b0f0fe3a95edd8477d2ab 13940 
udisks2_2.7.3-4.debian.tar.xz
 36b2b2d6b6395ce14c334802cc268a414927f34f50f87c3ba0755438a30afac9 15894 
udisks2_2.7.3-4_source.buildinfo
Files:
 72f9605b93f1d2806775fbcf64783faf 3152 admin optional udisks2_2.7.3-4.dsc
 6e2d5604509a011e47d06555985c1ce6 13940 admin optional 
udisks2_2.7.3-4.debian.tar.xz
 947508e6ebe59fb9ab3a6278b7025eca 15894 admin optional 
udisks2_2.7.3-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIyBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAlnBY7YACgkQauHfDWCP
ItxGOQ/4rzbL96crMKLPa9B1JTcdVa7s2lv4WPIwhlAcYUo8wUcfBbCDh+sN157M
LMUXM6UqEWeuWOWRgI/P+kMKyjVfQ36Aler5InxKeShFGkcSEk3lifZDCrNUHDe6
TBS65M3W40XCrqGU2AUEXo9pCTevUlTwgsaLea2nWGz9j2nPGrfS0eAXsjSbC7sD
+bkEdT7A1Gj4Um/zPkfpB0GnMLmynDHhO1Y0rxAiwbcv8bUpF+BA6WqTo+omcnEJ
BeIxzTwA1tmig4mX1ggm0nzld+lP192jj5QJE3Fhrpq3vFPZLUx2Niezd+AHFNuf
b2GRMisZ0fpcdYZq0cerHT2JlPVaBRhBrHnbl5uXPwgXo5MseDlJSNx+92N5cDJz
vyBUNy+umn/2edogpRCxea3/K7pyIVopez6Wpaa6l2TEEgDTHarHlP26RooBBxTk
sdwuIzRXaUzhpN2DfVCqIVPc3pe2f5WSqVeof40xEVCSFYo5mvbJBqPfAQA1//Hj
AZdb0znN0wCfZ4a4VtNjw81oCk2gXZVE5TxbKZZA4g+fW3aLsEmTiDe2gwWB1LnC
Je+viQmUvn3YXMXxk2leiFkYlHlSHuOcFO0UEAQsL0/Df/LTHOLRVEa8Rhn9F/gN

Bug#876214: pond: FTBFS cannot find package "appengine" "appengine/datastore" "github.com/agl/go-gtk/gdk" ...

2017-09-19 Thread Andreas Beckmann
Source: pond
Version: 0.1.1-4
Severity: serious
Justification: fails to build from source

Hi,

pond cannot be built any longer in a current sid/experimental
environment:

   dh_golang -O--buildsystem=golang
can't load package: package appengine: cannot find package "appengine" in any 
of:
/usr/lib/go-1.9/src/appengine (from $GOROOT)
/build/pond-0.1.1/obj-x86_64-linux-gnu/src/appengine (from $GOPATH)
can't load package: package appengine/datastore: cannot find package 
"appengine/datastore" in any of:
/usr/lib/go-1.9/src/appengine/datastore (from $GOROOT)
/build/pond-0.1.1/obj-x86_64-linux-gnu/src/appengine/datastore (from 
$GOPATH)
can't load package: package github.com/agl/go-gtk/gdk: cannot find package 
"github.com/agl/go-gtk/gdk" in any of:
/usr/lib/go-1.9/src/github.com/agl/go-gtk/gdk (from $GOROOT)
/build/pond-0.1.1/obj-x86_64-linux-gnu/src/github.com/agl/go-gtk/gdk 
(from $GOPATH)
can't load package: package github.com/agl/go-gtk/gdkpixbuf: cannot find 
package "github.com/agl/go-gtk/gdkpixbuf" in any of:
/usr/lib/go-1.9/src/github.com/agl/go-gtk/gdkpixbuf (from $GOROOT)

/build/pond-0.1.1/obj-x86_64-linux-gnu/src/github.com/agl/go-gtk/gdkpixbuf 
(from $GOPATH)
can't load package: package github.com/agl/go-gtk/glib: cannot find package 
"github.com/agl/go-gtk/glib" in any of:
/usr/lib/go-1.9/src/github.com/agl/go-gtk/glib (from $GOROOT)
/build/pond-0.1.1/obj-x86_64-linux-gnu/src/github.com/agl/go-gtk/glib 
(from $GOPATH)
can't load package: package github.com/agl/go-gtk/gtk: cannot find package 
"github.com/agl/go-gtk/gtk" in any of:
/usr/lib/go-1.9/src/github.com/agl/go-gtk/gtk (from $GOROOT)
/build/pond-0.1.1/obj-x86_64-linux-gnu/src/github.com/agl/go-gtk/gtk 
(from $GOPATH)
can't load package: package github.com/agl/go-gtk/gtkspell: cannot find package 
"github.com/agl/go-gtk/gtkspell" in any of:
/usr/lib/go-1.9/src/github.com/agl/go-gtk/gtkspell (from $GOROOT)

/build/pond-0.1.1/obj-x86_64-linux-gnu/src/github.com/agl/go-gtk/gtkspell (from 
$GOPATH)
dh_golang: go list -f '\
{{ .Dir }}/{{ index (or .GoFiles .CgoFiles .TestGoFiles .XTestGoFiles 
.IgnoredGoFiles) 0 }}' returned exit code 1
debian/rules:42: recipe for target 'binary' failed
make: *** [binary] Error 1


Full log attached.


Andreas


pond_0.1.1-4.log.gz
Description: application/gzip


Bug#863720: aiccu: SixXS will shutdown on 2017-06-06

2017-09-19 Thread Axel Beckert
Control: clone -1 -2
Control: severity -2 normal
Control: retitle -2 RM: aiccu -- ROM; SixXS has been shut down and no 
replacement popped up within 3 months
Control: reassign -2 ftp.debian.org

Hi,

Ansgar Burchardt wrote:
> SixXS will shutdown on 2017-06-06[1].  Unless there are other tunnel
> providers used with aiccu, it seems useless to include in stretch.
> >From a quick glance at [2], SixXS is the only provider using AYIYA and
> TIC which is what I believe aiccu implements.

What I've written in https://bugs.debian.org/864783 three months ago
is still valid:

> And unfortunately, neither
>
> * SixXS changed their mind, nor
> * did SixXS open-source the server implementation, nor
> * did someone else come up with an AYIYA(*) server implementation or a
>   comparable service.

Also citing from that mail:

> Mike and me agreed to keep it around in Debian Unstable for at least a
> few more months in the hope that any of the above mentioned events
> still happen. If neither of these events happen (within a year or so),
> we'll likely let aiccu also be removed from Debian Unstable.

3 months are now over and there's no sign of improvement of the
situation. So let's remove aiccu from unstable, too.

We'll definitely leave the git repo under collab-maint, in case
there's a reason to resume maintaining an aiccu package in Debian.

P.S.: I'm keeping the RC bug open for aiccu so that it doesn't
propagate to testing while waiting for being removed. Hence the clone
instead of just reassigning.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://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



Processed: Re: Bug#863720: aiccu: SixXS will shutdown on 2017-06-06

2017-09-19 Thread Debian Bug Tracking System
Processing control commands:

> clone -1 -2
Bug #863720 [src:aiccu] aiccu: SixXS will shutdown on 2017-06-06
Bug 863720 cloned as bug 876208
> severity -2 normal
Bug #876208 [src:aiccu] aiccu: SixXS will shutdown on 2017-06-06
Severity set to 'normal' from 'serious'
> retitle -2 RM: aiccu -- ROM; SixXS has been shut down and no replacement 
> popped up within 3 months
Bug #876208 [src:aiccu] aiccu: SixXS will shutdown on 2017-06-06
Changed Bug title to 'RM: aiccu -- ROM; SixXS has been shut down and no 
replacement popped up within 3 months' from 'aiccu: SixXS will shutdown on 
2017-06-06'.
> reassign -2 ftp.debian.org
Bug #876208 [src:aiccu] RM: aiccu -- ROM; SixXS has been shut down and no 
replacement popped up within 3 months
Bug reassigned from package 'src:aiccu' to 'ftp.debian.org'.
No longer marked as found in versions aiccu/20070115-17 and aiccu/20070115-14.
Ignoring request to alter fixed versions of bug #876208 to the same values 
previously set

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



Bug#876124: marked as done (expeyes-web: fails to install: expeyes-web.postinst: cannot create /etc/apache2/sites-available/apache-expeyes-vhost.conf: Directory nonexistent)

2017-09-19 Thread Debian Bug Tracking System
Your message dated Tue, 19 Sep 2017 16:52:22 +
with message-id 
and subject line Bug#876124: fixed in expeyes 4.2.1+dfsg-3
has caused the Debian Bug report #876124,
regarding expeyes-web: fails to install: expeyes-web.postinst: cannot create 
/etc/apache2/sites-available/apache-expeyes-vhost.conf: Directory nonexistent
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.)


-- 
876124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876124
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: expeyes-web
Version: 4.2.1+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Selecting previously unselected package expeyes-web.
  (Reading database ... 
(Reading database ... 11364 files and directories currently installed.)
  Preparing to unpack .../expeyes-web_4.2.1+dfsg-2_all.deb ...
  Unpacking expeyes-web (4.2.1+dfsg-2) ...
  Setting up expeyes-web (4.2.1+dfsg-2) ...
  Installing a virtual server for Apache2
  /var/lib/dpkg/info/expeyes-web.postinst: 43: 
/var/lib/dpkg/info/expeyes-web.postinst: cannot create 
/etc/apache2/sites-available/apache-expeyes-vhost.conf: Directory nonexistent
  dpkg: error processing package expeyes-web (--configure):
   subprocess installed post-installation script returned error exit status 2
  Errors were encountered while processing:
   expeyes-web


cheers,

Andreas


expeyes-web_4.2.1+dfsg-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: expeyes
Source-Version: 4.2.1+dfsg-3

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

Debian distribution maintenance software
pp.
Georges Khaznadar  (supplier of updated expeyes package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 19 Sep 2017 18:09:32 +0200
Source: expeyes
Binary: expeyes libej0 libej-dev expeyes-clib expeyes-firmware-dev 
python-expeyes expeyes-web expeyes-doc-en expeyes-doc-fr expeyes-doc-common 
microhope
Architecture: source amd64 all
Version: 4.2.1+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Georges Khaznadar 
Description:
 expeyes- hardware & software framework for developing science experiments
 expeyes-clib - hardware & software framework for developing science experiments
 expeyes-doc-common - Common files related to the User manual for expeyes 
library
 expeyes-doc-en - User manual for expeyes library, in English language
 expeyes-doc-fr - User manual for expeyes library, French translation
 expeyes-firmware-dev - hardware & software framework for developing science 
experiments
 expeyes-web - Web interface for expEYES-Junior
 libej-dev  - hardware & software framework for developing science experiments
 libej0 - hardware & software framework for developing science experiments
 microhope  - hardware & software framework to learn microcontrollers
 python-expeyes - Python library for expeyes
Closes: 876124
Changes:
 expeyes (4.2.1+dfsg-3) unstable; urgency=medium
 .
   * Modified the postinst routine for expeyes-web. Closes: #876124
Checksums-Sha1:
 a324964e5aff2316ba669e58800cfe3f416fe85c 2549 expeyes_4.2.1+dfsg-3.dsc
 dcaf97bf6cd03020b7973a656d9a056bf181cbad 14312 
expeyes_4.2.1+dfsg-3.debian.tar.xz
 84eb84030d1101b93d24feda9d81ef3fe3b3ef98 24754 
expeyes-clib-dbgsym_4.2.1+dfsg-3_amd64.deb
 0cd5c0885652d8f7da00ddbe18a7622a607783f4 15674 
expeyes-clib_4.2.1+dfsg-3_amd64.deb
 62b558581917b51e056480a2fcc95eba0fcc883b 36432 
expeyes-doc-common_4.2.1+dfsg-3_all.deb
 59a5dd6105d9010d6c99de305d283c7ba1959acb 6042622 
expeyes-doc-en_4.2.1+dfsg-3_all.deb
 865981452d76a87a3be1e5b03da70e8aefa7d926 14693972 
expeyes-doc-fr_4.2.1+dfsg-3_all.deb
 

Processed: Only in buster/sid

2017-09-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tag 876136 upstream buster sid
Bug #876136 {Done: Lisandro Damián Nicanor Pérez Meyer } 
[boomaga] [boomaga] Can't open file from .cache folder
Added tag(s) upstream, buster, and sid.
> thanks
Stopping processing here.

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



Bug#853635: closing #853635 qwtplot3d: ftbfs with GCC-7

2017-09-19 Thread Georges Khaznadar
Hello,

I uploaded a new version of qwtplot3d, with no change in the source
tree, but a new version number to prevent collisions with other variants
of the package like backports, when .symbols files are modified.
The package is in the queue DELAYED+10

I initialized the files debian/*.symbols, which allows me to build the
package with gcc-7.

Here is the lintian output, after a build in a fresh Sid chroot:

+++ lintian output +++
I: qwtplot3d source: vcs-field-uses-insecure-uri vcs-svn
svn://anonscm.debian.org/debian-science/packages/qwtplot3d/trunk/
I: qwtplot3d source: testsuite-autopkgtest-missing
W: libqwtplot3d-doc: embedded-javascript-library
usr/share/doc/libqwtplot3d-doc/html/jquery.js please use libjs-jquery
I: libqwtplot3d-qt4-0v5: no-symbols-control-file
usr/lib/libqwtplot3d-qt4.so.0.2.7
I: libqwtplot3d-qt5-0: no-symbols-control-file
usr/lib/libqwtplot3d-qt5.so.0.2.7
+++ end of lintian output +++

I made no changes in anonscm.debian.org/debian-science/packages/

If somebody wants to improve the packaging, there are 10 days left.
I need this package to enter Buster, since I maintain scidavis which
depends on it.

Best regards,   Georges.
-- 
Georges KHAZNADAR et Jocelyne FOURNIER
22 rue des mouettes, 59240 Dunkerque France.
Téléphone +33 (0)3 28 29 17 70



signature.asc
Description: PGP signature


Bug#871716: marked as done (build-dependency libatlas-dev no longer available)

2017-09-19 Thread Debian Bug Tracking System
Your message dated Tue, 19 Sep 2017 15:37:33 +
with message-id 
and subject line Bug#871716: fixed in shogun 3.2.0-7.5
has caused the Debian Bug report #871716,
regarding build-dependency libatlas-dev no longer available
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.)


-- 
871716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871716
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:shogun
Version: 3.2.0-7.4
Severity: serious

Dear Maintainer,

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

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

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

Cheers,

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


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: shogun
Source-Version: 3.2.0-7.5

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

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

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

Debian distribution maintenance software
pp.
Graham Inggs  (supplier of updated shogun package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 19 Sep 2017 14:57:41 +
Source: shogun
Binary: libshogun16 libshogun-dev shogun-doc-en shogun-doc-cn libshogun-dbg 
shogun-cmdline-static
Architecture: source
Version: 3.2.0-7.5
Distribution: unstable
Urgency: medium
Maintainer: Soeren Sonnenburg 
Changed-By: Graham Inggs 
Description:
 libshogun-dbg - Large Scale Machine Learning Toolbox
 libshogun-dev - Large Scale Machine Learning Toolbox
 libshogun16 - Large Scale Machine Learning Toolbox
 shogun-cmdline-static - Large Scale Machine Learning Toolbox
 shogun-doc-cn - Large Scale Machine Learning Toolbox
 shogun-doc-en - Large Scale Machine Learning Toolbox
Closes: 871716
Changes:
 shogun (3.2.0-7.5) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Drop build-dependency on libatlas-dev (Closes: #871716)
Checksums-Sha1:
 dc087acbe50b09c7b83b15389f18d9ad21c0d19c 2592 shogun_3.2.0-7.5.dsc
 fe64a7f9a1a214248de726e9c566783e5b8c9743 15944 shogun_3.2.0-7.5.debian.tar.xz
Checksums-Sha256:
 b4483aa10dbcccd8b38f9e44763734041c8c4d6c0fb155a0398385abedcab8a7 2592 
shogun_3.2.0-7.5.dsc
 a205d2d812bbb576f5fd601f5acbb58908696900e764fb7053ed80466943fd44 15944 
shogun_3.2.0-7.5.debian.tar.xz
Files:
 7c545a310e387fc7ee01e8f1cae6ff8d 2592 science optional shogun_3.2.0-7.5.dsc
 9153daa3be77456e6a6406f1e9dd11bc 15944 science optional 
shogun_3.2.0-7.5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJZwTG3AAoJEK/P7I5mnOHCIwsQAJIFD4ze5SmLmD6Esl7Z4avF
ltt29Gcv0vVucdd5MZiTxT8BoOtU7OXbZ+PhBxF0gPI+23ptzsxXHtsiuXxQ9F5r
XB6MvTDA/VBsJur8uvLNWWt2k9Lj2tNSpYzP2uOwqmEcB2uT8H6r1Ey3CXtdL8hu
wNJJ3DFB/iJFFvaAuE20KNiwaOCvGSkwlUnkwl0ek9oEaKzXHeUaFTAt0ZYsrFz5
hcv4yS3+dwRZ1OoYp9hakUwYW+JnbUW6Nw1ncSxn7GTNUgGDPx4JUZkqhfury4Ov
Af5kFZeh5u6FofjfsY11M8RxA8RDoJyY9RzqUhUjbUrwGx/0OVETnqd9kJc+/6A7
QkwlmyWmn8sNeZ8e7ZZsJ6cY2kV3C7KsoC0syeONjLJUHDUm972scgXlCHXjBcHi
0dsbdaSVSFhqxL1R1QHUEjYFj2r/oA9gVuDQ6dOw+u5uslV356IQo88FfPWNVbHX
V/YfpwgUO0PLR2jjOQUAi0G6r9yW6vIRTArlkCUv5i822+I4UPcQgPRcEJMXG7Ey
14u5O38MDPTdVCWqGeN3Wln62iZxLi4fxJJmBVevI7mPlSGhgLkW7W44hAVpKiP5
BZiXlIYgFd57OkoViC/sjEzHgxo7FtE50eSRzHv8sQhlYoD5LgB6APvc5QfF7NBN
Vflkd3hLry+e5Ql5FAcB
=QP84
-END PGP SIGNATURE End Message ---


Bug#876136: marked as done ([boomaga] Can't open file from .cache folder)

2017-09-19 Thread Debian Bug Tracking System
Your message dated Tue, 19 Sep 2017 12:00:10 -0300
with message-id 

and subject line Re: Bug#876136: [boomaga] Can't open file from .cache folder
has caused the Debian Bug report #876136,
regarding [boomaga] Can't open file from .cache folder
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.)


-- 
876136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876136
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: boomaga
Version: 0.7.1-1+b4
Severity: grave

--- Please enter the report below this line. ---
Hi, boomaga is completly unusable due bug in upstream, see 
https://github.com/Boomaga/boomaga/issues/50




--- System information. ---
Architecture: 
Kernel:   Linux 4.12.0-1-amd64

Debian Release: buster/sid
  900 testing www.deb-multimedia.org 
  900 testing packages.x2go.org 
  900 testing http.debian.net 
  500 stretch download.docker.com 
  500 stable  people.debian.org 
  500 stable  dl.google.com 
  500 jessie  deb.playonlinux.com 
  500 all liveusb.info 

--- Package information. ---
Depends   (Version) | Installed
===-+-
cups| 2.2.4-6
libc6 (>= 2.14) | 
libcups2 (>= 1.4.0) | 
libgcc1  (>= 1:3.0) | 
libpoppler-cpp0v5   (>= 0.46.0) | 
libpoppler68(>= 0.57.0) | 
libqt5core5a(>= 5.9.0~beta) | 
libqt5dbus5  (>= 5.0.2) | 
libqt5gui5   (>= 5.8.0) | 
libqt5printsupport5  (>= 5.0.2) | 
libqt5widgets5   (>= 5.7.0) | 
libsnappy1v5| 
libstdc++6 (>= 5.2) | 


Package's Recommends field is empty.

Package's Suggests field is empty.





-- 
Regards,
Andrey Spitsyn
--- End Message ---
--- Begin Message ---
Version: 0.9.1-1

According to that same bug report this should be fixed in 0.9.1-1,
available in experimental. I have not pushed it to unstable due to the
currently ongoing poppler transition, but I might ask for a special
permission to do it.

On 18 September 2017 at 18:01, Gmail  wrote:
> Package: boomaga
> Version: 0.7.1-1+b4
> Severity: grave
>
> --- Please enter the report below this line. ---
> Hi, boomaga is completly unusable due bug in upstream, see
> https://github.com/Boomaga/boomaga/issues/50
>
>
>
>
> --- System information. ---
> Architecture:
> Kernel:   Linux 4.12.0-1-amd64
>
> Debian Release: buster/sid
>   900 testing www.deb-multimedia.org
>   900 testing packages.x2go.org
>   900 testing http.debian.net
>   500 stretch download.docker.com
>   500 stable  people.debian.org
>   500 stable  dl.google.com
>   500 jessie  deb.playonlinux.com
>   500 all liveusb.info
>
> --- Package information. ---
> Depends   (Version) | Installed
> ===-+-
> cups| 2.2.4-6
> libc6 (>= 2.14) |
> libcups2 (>= 1.4.0) |
> libgcc1  (>= 1:3.0) |
> libpoppler-cpp0v5   (>= 0.46.0) |
> libpoppler68(>= 0.57.0) |
> libqt5core5a(>= 5.9.0~beta) |
> libqt5dbus5  (>= 5.0.2) |
> libqt5gui5   (>= 5.8.0) |
> libqt5printsupport5  (>= 5.0.2) |
> libqt5widgets5   (>= 5.7.0) |
> libsnappy1v5|
> libstdc++6 (>= 5.2) |
>
>
> Package's Recommends field is empty.
>
> Package's Suggests field is empty.
>
>
>
>
>
> --
> Regards,
> Andrey Spitsyn



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


Processed: your mail

2017-09-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> affects 805370 foomatic-filters printfilters-ppd magicfilter gjots2
Bug #805370 [mpage] mpage: non-free license
Added indication that 805370 affects foomatic-filters, printfilters-ppd, 
magicfilter, and gjots2
>
End of message, stopping processing here.

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



Processed: found 873374 in 20170802-1, tagging 875399, tagging 659906, tagging 875982, tagging 876120

2017-09-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> found 873374 20170802-1
Bug #873374 {Done: Hilko Bengen } [python-tsk] libtsk13 
4.4.2-1 crash in the dfvfs test suite
Marked as found in versions pytsk/20170802-1.
> tags 875399 + sid buster
Bug #875399 [src:sphinx-testing] AttributeError: type object 'Theme' has no 
attribute 'themes'
Added tag(s) sid and buster.
> tags 659906 + sid buster
Bug #659906 [src:mango-lassi] Needs port to GTK 3 / libavahi-ui-gtk3
Added tag(s) sid and buster.
> tags 875982 + sid buster
Bug #875982 [libsub-current-perl] RM: obsolete with current Perl?
Added tag(s) buster and sid.
> tags 876120 + sid buster
Bug #876120 [src:oath-toolkit] FTBFS: gtkdoc-mktmpl: command not found
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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



Bug#876191: most: configure cannot be built from source

2017-09-19 Thread Helmut Grohne
Source: most
Version: 5.0.0a-4
Severity: serious
User: helm...@debian.org
Usertags: rebootstrap

I was trying to fix a bug in most that requires modifying configure.
Thus I tried to regenerate it and ... failed.

It seems that configure was generated with autoconf2.61. The archive
does have autoconf 2.13, 2.64 and 2.69, but not 2.61. So I tried
autoconf 2.64 as that seemed closest. However autoheader2.64 failed:

| configure.ac:4: warning: AC_REQUIRE: `AC_PROG_CC' was expanded before it was 
required
| configure.ac:4: 
http://www.gnu.org/software/autoconf/manual/autoconf.html#Expanded-Before-Required
| ../../lib/autoconf/c.m4:429: AC_LANG_COMPILER(C) is expanded from...
| ../../lib/autoconf/lang.m4:329: AC_LANG_COMPILER_REQUIRE is expanded from...
| ../../lib/autoconf/lang.m4:372: AC_LANG_PREPROC_REQUIRE is expanded from...
| ../../lib/autoconf/general.m4:2549: AC_EGREP_CPP is expanded from...
| ../../lib/m4sugar/m4sh.m4:639: AS_IF is expanded from...
| ../../lib/autoconf/general.m4:2042: AC_CACHE_VAL is expanded from...
| ../../lib/autoconf/general.m4:2063: AC_CACHE_CHECK is expanded from...
| ../../lib/autoconf/c.m4:543: AC_PROG_GCC_TRADITIONAL is expanded from...
| aclocal.m4:496: JD_ANSI_CC is expanded from...
| configure.ac:4: the top level
| configure.ac:4: warning: AC_REQUIRE: `AC_PROG_CPP' was expanded before it was 
required
| configure.ac:4: 
http://www.gnu.org/software/autoconf/manual/autoconf.html#Expanded-Before-Required
| ../../lib/autoconf/c.m4:336: AC_LANG_PREPROC(C) is expanded from...
| ../../lib/autoconf/lang.m4:372: AC_LANG_PREPROC_REQUIRE is expanded from...
| ../../lib/autoconf/general.m4:2549: AC_EGREP_CPP is expanded from...
| ../../lib/m4sugar/m4sh.m4:639: AS_IF is expanded from...
| ../../lib/autoconf/general.m4:2042: AC_CACHE_VAL is expanded from...
| ../../lib/autoconf/general.m4:2063: AC_CACHE_CHECK is expanded from...
| ../../lib/autoconf/c.m4:543: AC_PROG_GCC_TRADITIONAL is expanded from...
| aclocal.m4:496: JD_ANSI_CC is expanded from...
| configure.ac:4: the top level
| configure.ac:4: warning: AC_REQUIRE: `AC_PROG_CC' was expanded before it was 
required
| configure.ac:4: 
http://www.gnu.org/software/autoconf/manual/autoconf.html#Expanded-Before-Required
| ../../lib/autoconf/c.m4:429: AC_LANG_COMPILER(C) is expanded from...
| ../../lib/autoconf/lang.m4:329: AC_LANG_COMPILER_REQUIRE is expanded from...
| ../../lib/autoconf/lang.m4:372: AC_LANG_PREPROC_REQUIRE is expanded from...
| ../../lib/autoconf/general.m4:2549: AC_EGREP_CPP is expanded from...
| ../../lib/m4sugar/m4sh.m4:639: AS_IF is expanded from...
| ../../lib/autoconf/general.m4:2042: AC_CACHE_VAL is expanded from...
| ../../lib/autoconf/general.m4:2063: AC_CACHE_CHECK is expanded from...
| ../../lib/autoconf/c.m4:543: AC_PROG_GCC_TRADITIONAL is expanded from...
| aclocal.m4:496: JD_ANSI_CC is expanded from...
| configure.ac:4: the top level
| configure.ac:4: warning: AC_REQUIRE: `AC_PROG_CPP' was expanded before it was 
required
| configure.ac:4: 
http://www.gnu.org/software/autoconf/manual/autoconf.html#Expanded-Before-Required
| ../../lib/autoconf/c.m4:336: AC_LANG_PREPROC(C) is expanded from...
| ../../lib/autoconf/lang.m4:372: AC_LANG_PREPROC_REQUIRE is expanded from...
| ../../lib/autoconf/general.m4:2549: AC_EGREP_CPP is expanded from...
| ../../lib/m4sugar/m4sh.m4:639: AS_IF is expanded from...
| ../../lib/autoconf/general.m4:2042: AC_CACHE_VAL is expanded from...
| ../../lib/autoconf/general.m4:2063: AC_CACHE_CHECK is expanded from...
| ../../lib/autoconf/c.m4:543: AC_PROG_GCC_TRADITIONAL is expanded from...
| aclocal.m4:496: JD_ANSI_CC is expanded from...
| configure.ac:4: the top level
| configure.ac:4: warning: AC_REQUIRE: `AC_PROG_CC' was expanded before it was 
required
| configure.ac:4: 
http://www.gnu.org/software/autoconf/manual/autoconf.html#Expanded-Before-Required
| ../../lib/autoconf/c.m4:429: AC_LANG_COMPILER(C) is expanded from...
| ../../lib/autoconf/lang.m4:329: AC_LANG_COMPILER_REQUIRE is expanded from...
| ../../lib/autoconf/lang.m4:372: AC_LANG_PREPROC_REQUIRE is expanded from...
| ../../lib/autoconf/general.m4:2549: AC_EGREP_CPP is expanded from...
| ../../lib/m4sugar/m4sh.m4:639: AS_IF is expanded from...
| ../../lib/autoconf/general.m4:2042: AC_CACHE_VAL is expanded from...
| ../../lib/autoconf/general.m4:2063: AC_CACHE_CHECK is expanded from...
| ../../lib/autoconf/c.m4:543: AC_PROG_GCC_TRADITIONAL is expanded from...
| aclocal.m4:496: JD_ANSI_CC is expanded from...
| configure.ac:4: the top level
| configure.ac:4: warning: AC_REQUIRE: `AC_PROG_CPP' was expanded before it was 
required
| configure.ac:4: 
http://www.gnu.org/software/autoconf/manual/autoconf.html#Expanded-Before-Required
| ../../lib/autoconf/c.m4:336: AC_LANG_PREPROC(C) is expanded from...
| ../../lib/autoconf/lang.m4:372: AC_LANG_PREPROC_REQUIRE is expanded from...
| ../../lib/autoconf/general.m4:2549: AC_EGREP_CPP is expanded from...
| ../../lib/m4sugar/m4sh.m4:639: AS_IF is expanded from...
| 

Bug#873800: marked as done (node-babylon FTBFS without network access)

2017-09-19 Thread Debian Bug Tracking System
Your message dated Tue, 19 Sep 2017 12:20:35 +
with message-id 
and subject line Bug#873800: fixed in node-babylon 6.18.0-1
has caused the Debian Bug report #873800,
regarding node-babylon FTBFS without network access
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.)


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

Source: node-babylon
Version: 6.14.1-1
Severity: serious

Hi Maintainer

Node-babylon has a build dependency on nodejs-legacy which is no longer 
in the archive.  With this dependency removed, the build fails on a 
machine without external network access:


...
HOME=/tmp npm install babel-cli rollup rollup-plugin-babel \
rollup-plugin-node-resolve babel-plugin-transform-flow-strip-types \
babel-preset-es2015 babel-preset-stage-0
npm ERR! Linux 4.4.0-92-generic
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "babel-cli" 
"rollup" "rollup-plugin-babel" "rollup-plugin-node-resolve" 
"babel-plugin-transform-flow-strip-types" "babel-preset-es2015" 
"babel-preset-stage-0"

npm ERR! node v6.11.2
npm ERR! npm  v3.5.2
npm ERR! code ENOTFOUND
npm ERR! errno ENOTFOUND
npm ERR! syscall getaddrinfo

npm ERR! network getaddrinfo ENOTFOUND registry.npmjs.org 
registry.npmjs.org:443

npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad 
network settings.

npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.  See: 'npm help config'

npm ERR! Please include the following file with any support request:
npm ERR! /<>/npm-debug.log
debian/rules:11: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

Regards
Graham
--- End Message ---
--- Begin Message ---
Source: node-babylon
Source-Version: 6.18.0-1

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 19 Sep 2017 16:39:21 +0530
Source: node-babylon
Binary: node-babylon
Architecture: source all
Version: 6.18.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Pirate Praveen 
Description:
 node-babylon - JavaScript parser used in Babel
Closes: 873800
Changes:
 node-babylon (6.18.0-1) unstable; urgency=medium
 .
   * New upstream release
   * Remove dependency on nodejs-legacy (Closes: #873800)
   * Use system modules when available
Checksums-Sha1:
 95e3c0df553dee4915d6a7f363ba7d408c7c3bcd 2206 node-babylon_6.18.0-1.dsc
 c5939e4b1db2a710842a9b8885e680802fad157c 653201 node-babylon_6.18.0.orig.tar.gz
 9013749e323226537d08c58ea17a36898ef7c034 3432 
node-babylon_6.18.0-1.debian.tar.xz
 4f2964d28ab0a46669ce9e38494422306e6e1086 61624 node-babylon_6.18.0-1_all.deb
 3380c823fdb96917f341d841d46c66e14ef749c1 14802 
node-babylon_6.18.0-1_amd64.buildinfo
Checksums-Sha256:
 f1a1efd19c351ba5502c7b74e230bce06844500cb4c58a1626f3865ff89e3107 2206 
node-babylon_6.18.0-1.dsc
 c56118b1ed1cf6d1e59c5682d2a161802bea39dd84a996bdc5ddadbb6d714ac3 653201 
node-babylon_6.18.0.orig.tar.gz
 e9bea37a180b258a9cb2ff10e34a7cb6f4fb080d2800e81a55b508496c32b4f1 3432 
node-babylon_6.18.0-1.debian.tar.xz
 70c48541bfd2aad844b800ce3ae86b39c0e94855913453d767678066442099f0 61624 
node-babylon_6.18.0-1_all.deb
 ee23d88693a8421f4ed62c608ffa169ae3d735c9e34c64e872af09a700e31cfc 14802 
node-babylon_6.18.0-1_amd64.buildinfo
Files:
 62fe8fc4676e36364c33d96cd3270e28 2206 contrib/web optional 

Bug#876185: Package is not installable with current evolution

2017-09-19 Thread Michael Meskes
Package: evolution-rss
Version: 0.3.95-7
Severity: grave

Subject says it all, the package either blocks evolution update or is 
uninstallable. 

Michael

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

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

Versions of packages evolution-rss depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2+b1
ii  evolution3.24.5-3
ii  evolution-data-server3.24.5-6
ii  libatk1.0-0  2.26.0-2
ii  libc62.24-17
ii  libcairo-gobject21.14.10-1
ii  libcairo21.14.10-1
ii  libcamel-1.2-60  3.24.5-6
ii  libebackend-1.2-10   3.24.5-6
ii  libebook-1.2-19  3.26.0-1
ii  libebook-contacts-1.2-2  3.26.0-1
ii  libedata-book-1.2-25 3.24.5-6
ii  libedataserver-1.2-223.24.5-6
ii  libedataserverui-1.2-1   3.24.5-6
ii  libevolution 3.24.5-3
ii  libgcc1  1:7.2.0-5
ii  libgdk-pixbuf2.0-0   2.36.5-4
ii  libglib2.0-0 2.54.0-1
ii  libgtk-3-0   3.22.21-1
ii  libjavascriptcoregtk-4.0-18  2.18.0-2
ii  libnspr4 2:4.16-1
ii  libnss3  2:3.32-2
ii  libpango-1.0-0   1.40.12-1
ii  libpangocairo-1.0-0  1.40.12-1
ii  libsecret-1-00.18.5-3.1
ii  libsoup-gnome2.4-1   2.60.0-1
ii  libsoup2.4-1 2.60.0-1
ii  libsqlite3-0 3.20.1-1
ii  libstdc++6   7.2.0-5
ii  libwebkit2gtk-4.0-37 2.18.0-2
ii  libxml2  2.9.4+dfsg1-4

evolution-rss recommends no packages.

evolution-rss suggests no packages.

-- no debconf information



Bug#869180: marked as done (src:hydrogen-drumkits: Some sources lack licensing)

2017-09-19 Thread Debian Bug Tracking System
Your message dated Tue, 19 Sep 2017 11:06:26 +
with message-id 
and subject line Bug#869180: fixed in hydrogen-drumkits 2017.09.19~dfsg-1
has caused the Debian Bug report #869180,
regarding src:hydrogen-drumkits: Some sources lack licensing
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.)


-- 
869180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869180
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:hydrogen-drumkits
Version: 2015.09.28-1
Severity: serious
Justification: Policy 2.2.1

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

These drumkits are in upstream metadata listed _without_ license:

ColomboAcousticDrumkit (sf)
EasternHop (sf)
Electric Empire (sf)
HardElectro (sf)
HipHop-1 (sf)
HipHop-2 (sf)
Millo's MultiLayered 2 (sf)
Synthie-1 (sf)
VariBreaks (sf)

In Debian copyright file those are listed as licensed GPL-2.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAllxzkMACgkQLHwxRsGg
ASElKBAApwwOF1ii7YQvV3qaTvt6MwfMUkARW4+FII9CEsqf2UQEbNUwm7oN07jL
4faAXhQ94Xdb1NwmTKmq82QmmD9y8MuaEps8EvfLn5cvML21+54Kwr5upt8uEnF+
wKFKD/6nRqab8qGnu0u6cryGKFLE6jyV7dEGYrh4NB0DKcpv6f322c970v9p9wqK
tx8hBklGm+cWH9aZ/91avuAQJQ/wLhEESKohWTGfUSWQJn6bw0gEgqw+xI1QCi04
L+6brY7cck5T0ZomebDOfCcm05fshBsi7XuYxL4WnVtDGcwiDWkhEvTIDXcVPUbN
WzVyhn78e1aCtZ5wGT73OmaJXMhHzM1N3dRxg9JY+uB2I6uA65bxIj6EAkxXDMge
3lZUgO6ETSQS250AH4k2jcEMC6FPIK/KEEI7iWWa/7jIvT7uhM3cchs2fQZXxFLy
EgL2RCn/sGtPHvaefCyMNYFPhZDcGYPeGCONKPzg9y+K35iihc7BM0KmVwHSUQ9r
ScaUdOuUWUg9RocpAEKbVTxkn5E0ygrtH7eIb/GBK/qJVoRh1+xKOjp9BqYgHVHe
eGsEvSV1WIACzc3XU8uLa0NmInPbSGtKNMGbfT7MCrrtwtSSEFsuoHL4pRcibs1v
Z3ooVdnfz9K4Serzd4+o2+2E9ZBrpyQ9L3CDuLlHwEV0Hkn1lSM=
=YS/0
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: hydrogen-drumkits
Source-Version: 2017.09.19~dfsg-1

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

Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated 
hydrogen-drumkits package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 19 Sep 2017 12:13:56 +0200
Source: hydrogen-drumkits
Binary: hydrogen-drumkits hydrogen-drumkits-effects
Architecture: source
Version: 2017.09.19~dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: IOhannes m zmölnig (Debian/GNU) 
Description:
 hydrogen-drumkits - drumkits for Hydrogen
 hydrogen-drumkits-effects - effect drumkits for Hydrogen
Closes: 869180
Changes:
 hydrogen-drumkits (2017.09.19~dfsg-1) unstable; urgency=medium
 .
   * New upstream version 2017.09.19~dfsg (Closes: #869180)
 .
   [ Jonas Smedegaard ]
   * Include git-buildpackage helper script postclone.sh with source.
   * Updated copyright info
 * Use https protocol in initial format line.
 * Use License-Grant and License-Reference fields. Thanks to Ben Finney.
 * Improved details of copyright holders.
 * Documented origins/assumptions of copyright holders.
 * Dropped undocumented copyright years.
 * Merged equally licensed Files sections with same copyright holder.
 * Fixed include verbatim licenses:
   - CC0, CC-BY-3.0, CC-BY-SA-3.0, CC-BY-SA-3.0-us.
 * Dropped bogus initial wildcard Files section
   (The "upstream" tarball is created ad-hoc with no common copyright 
holders
   nor license.)
 * Clarified origin of ColomboAcousticDrumkit license, and fixed include
   exception. Thanks to James Cowgill (see bug#869180).
 * Fixed license of ElectricEmpireKit, and added comment clarifying
   origin as embedded inside drumkit file itself.
 * Fixed license of drumkits VariBreaks and HardElectro1 to be GPL-2.
   Documented origin of licenses.
   * Tidy control file: Sort uploaders.
   * Added myself as uploader.
   * Re-licensed packaging as GPL-2+.
   * Added lintian overrides regarding license in 

Bug#874041: marked as done (graphite-carbon: please Build-Depend on rename)

2017-09-19 Thread Debian Bug Tracking System
Your message dated Tue, 19 Sep 2017 11:05:44 +
with message-id 
and subject line Bug#874041: fixed in graphite-carbon 1.0.2-1
has caused the Debian Bug report #874041,
regarding graphite-carbon: please Build-Depend on rename
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.)


-- 
874041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874041
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: graphite-carbon
Version: 0.9.15-1
Severity: serious
Justification: FTBFS with impending change
User: debian-p...@lists.debian.org
Usertags: rename-deprecation

As announced last year[1] and as advised by deprecation messages,
rename(1) will be removed from the perl package after the stretch
release, and this is now imminent.

Your package FTBFS with perl from experimental as a result. Please
add a Build-Depends: rename to your package, and all will be well
again:

make[1]: Entering directory '/<>'
rename 's/\.py//' debian/graphite-carbon/usr/bin/*.py
/bin/sh: 1: rename: not found
debian/rules:7: recipe for target 'override_dh_install' failed
Let me know if you would prefer an NMU to get this trivial change made.

Cheers,
Dominic.

[1] 
--- End Message ---
--- Begin Message ---
Source: graphite-carbon
Source-Version: 1.0.2-1

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

Debian distribution maintenance software
pp.
Jonas Genannt  (supplier of updated graphite-carbon package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 19 Sep 2017 12:48:46 +0200
Source: graphite-carbon
Binary: graphite-carbon
Architecture: source all
Version: 1.0.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Graphite Group 
Changed-By: Jonas Genannt 
Description:
 graphite-carbon - backend data caching and persistence daemon for Graphite
Closes: 846524 860194 874041
Changes:
 graphite-carbon (1.0.2-1) unstable; urgency=medium
 .
   [ Mathieu Parent ]
   * Remove me from uploaders
 .
   [ Jonas Genannt ]
   * Imported Upstream version 1.0.2 (Closes: #860194)
   * Added Brazilian Portuguese translation
 [Adriano Rafael Gomes] (Closes: #846524)
   * d/control:
 - Added rename to build depends (Closes: #874041)
 - bumped standards/compat version
 - updated to secure vcs urls
 - changed my maintainer mail address
 - added lsb-base to depends
   * d/p/carbon.conf.debian.patch: updated to new upstream version
   * d/p/disable_install_opt.patch: updated to new upstream version
   * Manpages (d/*.1) fixed spelling error
   * d/README.Debian: removed duplicate word
   * d/*.service: added documentation keyword
Checksums-Sha1:
 e301a038193e41afc0a2873372663fde83a44f56 2094 graphite-carbon_1.0.2-1.dsc
 5642337489b22a5530e668b951f75b8841bf8618 61828 
graphite-carbon_1.0.2.orig.tar.gz
 6e3755a4554ced73f48d3708bf229cb915f4bc79 12844 
graphite-carbon_1.0.2-1.debian.tar.xz
 373d759c523cc8bd3264674331209b897c9af06c 68986 graphite-carbon_1.0.2-1_all.deb
 f06918629ce2c27df5ca04ba834181b3de49e415 5085 
graphite-carbon_1.0.2-1_amd64.buildinfo
Checksums-Sha256:
 df2bae6e049831a3d15845e55a171762f2c0677cd9e6c311ddb445401eccaa80 2094 
graphite-carbon_1.0.2-1.dsc
 76f6385d28c0970267abeca3e6ff739b401dbf929168b3dcb651daf5eaad5a90 61828 
graphite-carbon_1.0.2.orig.tar.gz
 8acf2efee14ef514a1a18fa4a50d63a9169740aecc6f3f0782756c22595b7613 12844 
graphite-carbon_1.0.2-1.debian.tar.xz
 5fad41ebeb46a13b5eebc1bc9af65e5bd3fb52af673a1e579d80914da5ef3e23 68986 
graphite-carbon_1.0.2-1_all.deb
 949fde7b43e06a3d7d03b8ec033fb2c1002aac73dc7e3ac061be0ecbac371d12 5085 
graphite-carbon_1.0.2-1_amd64.buildinfo
Files:
 f5154d2984fbb430d04cba9c7dd21053 2094 utils optional 
graphite-carbon_1.0.2-1.dsc
 6c4c783e96301fc98546d94f01877259 61828 utils optional 
graphite-carbon_1.0.2.orig.tar.gz
 8e9b2e69625bc0b31e63259a460ce8b9 12844 utils optional 

Processed: 875399 affects python-os-api-ref

2017-09-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> affects 875399 src:python-os-api-ref
Bug #875399 [src:sphinx-testing] AttributeError: type object 'Theme' has no 
attribute 'themes'
Added indication that 875399 affects src:python-os-api-ref
> user python-modules-t...@lists.alioth.debian.org
Setting user to python-modules-t...@lists.alioth.debian.org (was 
mity...@debian.org).
> usertag 875399 + sphinx1.6
There were no usertags set.
Usertags are now: sphinx1.6.
> thanks
Stopping processing here.

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



Bug#869180: marked as pending

2017-09-19 Thread IOhannes m zmölnig
tag 869180 pending
thanks

Hello,

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


http://anonscm.debian.org/git/pkg-multimedia/hydrogen-drumkits.git/commit/?id=5a01c46

---
commit 5a01c46f52d879ba500bd75a2143191d7861341d
Author: IOhannes m zmölnig 
Date:   Tue Sep 19 11:59:57 2017 +0200

Regenerated d/copyright

Gbp-Dch: ignore

diff --git a/debian/changelog b/debian/changelog
index 8c8a5cf..40cfee6 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,43 @@
+hydrogen-drumkits (2017.09.19~dfsg-1) unstable; urgency=medium
+
+  * New upstream version 2017.09.19~dfsg (Closes: #869180)
+
+  [ Jonas Smedegaard ]
+  * Include git-buildpackage helper script postclone.sh with source.
+  * Updated copyright info
+* Use https protocol in initial format line.
+* Use License-Grant and License-Reference fields. Thanks to Ben Finney.
+* Improved details of copyright holders.
+* Documented origins/assumptions of copyright holders.
+* Dropped undocumented copyright years.
+* Merged equally licensed Files sections with same copyright holder.
+* Fixed include verbatim licenses CC0 CC-BY-3.0 CC-BY-SA-3.0 
CC-BY-SA-3.0-us.
+* Dropped bogus initial wildcard Files section
+  (The "upstream" tarball is created ad-hoc with no common copyright 
holders
+  nor license.)
+* Clarified origin of ColomboAcousticDrumkit license, and fixed include
+  exception. Thanks to James Cowgill (see bug#869180).
+* Fixed license of ElectricEmpireKit, and added comment clarifying
+  origin as embedded inside drumkit file itself.
+* Fixed license of drumkits VariBreaks and HardElectro1 to be GPL-2.
+  Documented origin of licenses.
+  * Tidy control file: Sort uploaders.
+  * Added myself as uploader.
+  * Re-licensed packaging as GPL-2+.
+  * Added lintian overrides regarding license in License-Reference field.
+See bug#786450.
+
+  [ IOhannes m zmölnig ]
+  * Fixed get-orig-sources script
+* Flag to keep working directory
+  * Updated copyright info
+* Clarified license information by some of Artemiy Pavlov's drumkits
+  * Refreshed drumkits.json
+* Switched circAfrique.h2drumkits download URL (avoiding 404)
+  * Added README.Debian with notes on the included drumkits. (LP: #1647046)
+
+ -- IOhannes m zmölnig (Debian/GNU)   Tue, 19 Sep 2017 
11:51:48 +0200
+
 hydrogen-drumkits (2015.09.28-1) unstable; urgency=medium
 
   * Imported new upstream tarball.



Processed: Bug#869180 marked as pending

2017-09-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tag 869180 pending
Bug #869180 [src:hydrogen-drumkits] src:hydrogen-drumkits: Some sources lack 
licensing
Added tag(s) pending.
> thanks
Stopping processing here.

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



Bug#872259: sagemath: FTBFS with Sphinx 1.6: TypeError: frompickle() takes exactly 3 arguments (4 given)

2017-09-19 Thread Tobias Hansen
Control: tags -1 +pending

Fixed in git, but we need for a libgap-sage update before the next upload.



Processed: Re: sagemath: FTBFS with Sphinx 1.6: TypeError: frompickle() takes exactly 3 arguments (4 given)

2017-09-19 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 +pending
Bug #872259 [src:sagemath] sagemath: FTBFS with Sphinx 1.6: TypeError: 
frompickle() takes exactly 3 arguments (4 given)
Added tag(s) pending.

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



Bug#874579: marked as done (hibernate-validator: incomplete packaging, missing classes make r-deps unusable)

2017-09-19 Thread Debian Bug Tracking System
Your message dated Tue, 19 Sep 2017 07:35:58 +
with message-id 
and subject line Bug#874579: fixed in libhibernate-validator-java 4.3.3-2
has caused the Debian Bug report #874579,
regarding hibernate-validator: incomplete packaging, missing classes make 
r-deps unusable
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.)


-- 
874579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874579
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libhibernate-validator-java
Version: 4.3.3-1
Severity: serious

Hi,

as discussed in #874372 Michael Weghorn discovered that
the hibernate-validator.jar in libhibernate-validator-java is missing
some important files that prevent PDFsam to function properly.

The logging directory should contain the following files.

$ ls -l /tmp/extracted/manual/org/hibernate/validator/internal/util/logging/
total 144
-rw-r--r-- 1 user user 21057 Sep  6 19:11 Log.class
-rw-r--r-- 1 user user   944 Sep  6 19:11 LoggerFactory.class
-rw-r--r-- 1 user user 22029 Sep  6 19:11 Log.i18n.properties
-rw-r--r-- 1 user user 75030 Sep  6 19:11 Log_$logger.class
-rw-r--r-- 1 user user  4964 Sep  6 19:11 Messages_$bundle.class
-rw-r--r-- 1 user user  1894 Sep  6 19:11 Messages.class
-rw-r--r-- 1 user user  2142 Sep  6 19:11 Messages.i18n.properties

Apparently the missing files are autogenerated at build-time. This
requires libjboss-logging-tools-java to be present which seems to be
the case. At the moment I can't find out what exactly prevents the
processing but it might be related to the maven-processor-plugin or
the disabled annotation module of hibernate-validator. Any way PDFsam
is not usuable due to the absence of these files.

Markus
--- End Message ---
--- Begin Message ---
Source: libhibernate-validator-java
Source-Version: 4.3.3-2

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated 
libhibernate-validator-java package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 19 Sep 2017 09:12:55 +0200
Source: libhibernate-validator-java
Binary: libhibernate-validator-java
Architecture: source
Version: 4.3.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Description:
 libhibernate-validator-java - Hibernate Validator
Closes: 874579
Changes:
 libhibernate-validator-java (4.3.3-2) unstable; urgency=medium
 .
   * Team upload.
   * Add jboss-logging-tools.patch and provide the missing source files
 manually.
 The packaging was incomplete because generated classes were not created at
 build time. Apparently this is caused by a wrong or outdated invocation of
 the jboss-logging-processor in pom.xml. This package still requires an
 older version of jboss-logging-tools which behaves differently. This patch
 works around the issue by applying the sources manually. They were created
 with version 1.0.1.Final of jboss-logging-tools and then Log_$logger.java
 was patched to fix missing methods. For more information see #874579.
 (Closes: #874579)
   * Declare compliance with Debian Policy 4.1.0.
Checksums-Sha1:
 c4a1bafc6517dbcb6b2a839f0fa6892ca895c221 2741 
libhibernate-validator-java_4.3.3-2.dsc
 a4e4d48a2e443d82db9038d47ceb21e22cdf5e91 18152 
libhibernate-validator-java_4.3.3-2.debian.tar.xz
 360fb0e53e07aad65a64082defc9b0be0acac3b9 16886 
libhibernate-validator-java_4.3.3-2_amd64.buildinfo
Checksums-Sha256:
 5c9a0a428424f1ec04cce5b8fc8825f101908c6935d3f754d95472f05f97cd39 2741 
libhibernate-validator-java_4.3.3-2.dsc
 5c0412a614caa6456ffa3c2a6f150d8f7900df0e31f2d98661fb82bc51145242 18152 
libhibernate-validator-java_4.3.3-2.debian.tar.xz
 f114298d329663344c0a19e82415201848e624a59322e6523ee8a081141f6fac 16886 
libhibernate-validator-java_4.3.3-2_amd64.buildinfo
Files:
 

Processed: Re: Bug#874679: libssh2: Fails to build on stable if libssl-dev is installed

2017-09-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> fixed 874679 1.8.0-1
Bug #874679 [src:libssh2] libssh2: Fails to build on stable if libssl-dev is 
installed
Marked as fixed in versions libssh2/1.8.0-1.
> thanks
Stopping processing here.

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



Bug#874679: libssh2: Fails to build on stable if libssl-dev is installed

2017-09-19 Thread Mikhail Gusarov

fixed 874679 1.8.0-1
thanks

Actually, 1.8.0-1 already has this option, so there ain't much to do 
here.


On 19 Sep 2017, at 8:22, Mikhail Gusarov wrote:


Hello Wookey,

On 8 Sep 2017, at 17:52, Wookey wrote:

So it seems that the package should declare a build-conflicts with 
libssl-dev.


The better way to fix it is to explicitly build --without-openssl.

I'll do it shortly.

Mikhail.




Bug#872490: vdr-plugin-osdteletext FTBFS with vdr 2.3.8

2017-09-19 Thread Holger Schröder

This version build and works with vdr 2.3.x


https://github.com/rofafor/vdr-plugin-osdteletext


Greetings

        Holger...



Processed: Pending fixes for bugs in the libhibernate-validator-java package

2017-09-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tag 874579 + pending
Bug #874579 [libhibernate-validator-java] hibernate-validator: incomplete 
packaging, missing classes make r-deps unusable
Ignoring request to alter tags of bug #874579 to the same tags previously set
> thanks
Stopping processing here.

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



Bug#874579: Pending fixes for bugs in the libhibernate-validator-java package

2017-09-19 Thread pkg-java-maintainers
tag 874579 + pending
thanks

Some bugs in the libhibernate-validator-java package are closed in
revision 0d79f6cee7bdf590f50d9ff9ba818282455f2079 in branch 'master'
by Markus Koschany

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

Commit message:

Add jboss-logging-tools.patch and provide the missing source files manually.

The packaging was incomplete because generated classes were not created at
build time. Apparently this is caused by a wrong or outdated invocation of 
the
jboss-logging-processor in pom.xml. This package still requires an older
version of jboss-logging-tools which behaves differently. This patch works
around the issue by applying the sources manually. They were created with
version 1.0.1.Final of jboss-logging-tools and then Log_$logger.java was
patched to fix a missing override. For more information see #874579.

Closes: #874579



Processed: Re: [Pkg-utopia-maintainers] Bug#876143: udisks2-btrfs: Dependency on libblockdev-btrfs should be libblockdev-btrfs2

2017-09-19 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 serious
Bug #876143 [udisks2-btrfs] udisks2-btrfs: Dependency on libblockdev-btrfs 
should be libblockdev-btrfs2
Severity set to 'serious' from 'normal'

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



Processed: Re: hibernate-validator: incomplete packaging, missing classes make r-deps unusable

2017-09-19 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 pending
Bug #874579 [libhibernate-validator-java] hibernate-validator: incomplete 
packaging, missing classes make r-deps unusable
Added tag(s) pending.

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



Bug#874579: hibernate-validator: incomplete packaging, missing classes make r-deps unusable

2017-09-19 Thread Markus Koschany
Control: tags -1 pending

tl;dr

I'm going to upload a new revision of libhibernate-validator-java. I
have spent several hours investigating the issue and found out that the
annotation processor of jboss-logging-tools 2.1.0 behaves somehow
differently and the translationFilesPath option is currently not
recognized. (I have checked that the option exists in 2.1.0) I have
built the source files with version 1.0.1.Final of jboss-logging-tools
on my local machine, implemented some missing methods and patched
libhibernate-validator-java. Finally PDFsam works.


I have read the documentation at [1] and [2] and searched the internet
for further information about the problem but did not manage to find a
working solution with jboss-logging-tools 2.1.0. The relevant part in
pom.xml is:



org.bsc.maven
maven-processor-plugin
2.0.2


${project.build.directory}/generated-sources/logging


org.jboss.logging.processor.apt.LoggingToolsProcessor

-AloggingVersion=3.0
-AtranslationFilesPath=${project.basedir}/src/main/resources -source 1.6
-target 1.6 -sourcepath
${project.build.directory}/generated-sources/jaxb -encoding
UTF-8



process
generate-sources

process





org.jboss.logging
jboss-logging-processor
1.0.1.Final





With version 1.0.1.Final of jboss-logging-tools the translationFilesPath
option is recognized but for unknown reasons this doesn't work with
2.1.0 anymore. I have also added jboss-logging-annotations and
jboss-logging-processor as build-dependencies but also to no avail. The
processor org.jboss.logging.processor.apt.LoggingToolsProcessor seems
correct to me.

I have explored some other routes but eventually decided that I want to
do something else for a change again.

[1] https://jboss-logging.github.io/jboss-logging-tools/#example-use-cases
[2] https://bsorrentino.github.io/maven-annotation-plugin/usage.html



signature.asc
Description: OpenPGP digital signature


Bug#874679: libssh2: Fails to build on stable if libssl-dev is installed

2017-09-19 Thread Mikhail Gusarov

Hello Wookey,

On 8 Sep 2017, at 17:52, Wookey wrote:

So it seems that the package should declare a build-conflicts with 
libssl-dev.


The better way to fix it is to explicitly build --without-openssl.

I'll do it shortly.

Mikhail.



Bug#868786: marked as done (shogun FTBFS on arm64 with libeigen3-dev 3.3.4-2)

2017-09-19 Thread Debian Bug Tracking System
Your message dated Tue, 19 Sep 2017 06:04:22 +
with message-id 
and subject line Bug#868786: fixed in eigen3 3.3.4-3
has caused the Debian Bug report #868786,
regarding shogun FTBFS on arm64 with libeigen3-dev 3.3.4-2
to be marked as done.

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

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


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

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/shogun.html

...
/build/1st/shogun-3.2.0/src/shogun/mathematics/linalg/linsolver/DirectLinearSolverComplex.cpp:82:50:
   required from here
/usr/include/eigen3/Eigen/src/Core/util/BlasUtil.h:63:74: error: no type named 
'ReturnType' in 'struct Eigen::ScalarBinaryOpTraits<__vector(2) double, 
Eigen::internal::Packet1cd, Eigen::internal::scalar_product_op<__vector(2) 
double, Eigen::internal::Packet1cd> >'
   typedef typename ScalarBinaryOpTraits::ReturnType 
Scalar;
  ^~
In file included from /usr/include/eigen3/Eigen/Jacobi:27:0,
 from /usr/include/eigen3/Eigen/QR:16,
 from /usr/include/eigen3/Eigen/Dense:4,
 from /usr/include/eigen3/Eigen/Eigen:1,
 from 
/build/1st/shogun-3.2.0/src/shogun/mathematics/eigen3.h:17,
 from 
/build/1st/shogun-3.2.0/src/shogun/mathematics/linalg/linsolver/DirectLinearSolverComplex.cpp:15:
/usr/include/eigen3/Eigen/src/Jacobi/Jacobi.h: In instantiation of 'void 
Eigen::internal::apply_rotation_in_the_plane(Eigen::DenseBase&, 
Eigen::DenseBase&, const Eigen::JacobiRotation&) [with 
VectorX = Eigen::Block, 1, -1, 
false>; VectorY = Eigen::Block, 1, 
-1, false>; OtherScalar = double]':
/usr/include/eigen3/Eigen/src/Jacobi/Jacobi.h:282:40:   required from 'void 
Eigen::MatrixBase::applyOnTheLeft(Eigen::Index, Eigen::Index, const 
Eigen::JacobiRotation&) [with OtherScalar = double; Derived = 
Eigen::Matrix; Eigen::Index = long int]'
/usr/include/eigen3/Eigen/src/SVD/JacobiSVD.h:725:13:   required from 
'Eigen::JacobiSVD& Eigen::JacobiSVD::compute(const MatrixType&, unsigned int) [with _MatrixType = 
Eigen::Matrix; int QRPreconditioner = 2; 
Eigen::JacobiSVD::MatrixType = 
Eigen::Matrix]'
/usr/include/eigen3/Eigen/src/SVD/JacobiSVD.h:548:14:   required from 
'Eigen::JacobiSVD::JacobiSVD(const MatrixType&, 
unsigned int) [with _MatrixType = Eigen::Matrix; 
int QRPreconditioner = 2; Eigen::JacobiSVD::MatrixType = Eigen::Matrix]'
/usr/include/eigen3/Eigen/src/SVD/JacobiSVD.h:799:10:   required from 
'Eigen::JacobiSVD::PlainObject> 
Eigen::MatrixBase::jacobiSvd(unsigned int) const [with Derived = 
Eigen::Map >; typename 
Eigen::DenseBase::PlainObject = Eigen::Matrix]'
/build/1st/shogun-3.2.0/src/shogun/mathematics/linalg/linsolver/DirectLinearSolverComplex.cpp:82:50:
   required from here
/usr/include/eigen3/Eigen/src/Jacobi/Jacobi.h:359:28: error: 'struct 
Eigen::internal::conj_helper<__vector(2) double, Eigen::internal::Packet1cd, 
false, false>' has no member named 'pmul'
 pstore(px, padd(pm.pmul(pc,xi),pcj.pmul(ps,yi)));
 ~~~^~~~
/usr/include/eigen3/Eigen/src/Jacobi/Jacobi.h:359:44: error: 'struct 
Eigen::internal::conj_helper<__vector(2) double, Eigen::internal::Packet1cd, 
false, false>' has no member named 'pmul'
 pstore(px, padd(pm.pmul(pc,xi),pcj.pmul(ps,yi)));
^~~~
/usr/include/eigen3/Eigen/src/Jacobi/Jacobi.h:360:29: error: 'struct 
Eigen::internal::conj_helper<__vector(2) double, Eigen::internal::Packet1cd, 
false, false>' has no member named 'pmul'
 pstore(py, psub(pcj.pmul(pc,yi),pm.pmul(ps,xi)));
 ^~~~
/usr/include/eigen3/Eigen/src/Jacobi/Jacobi.h:360:44: error: 'struct 
Eigen::internal::conj_helper<__vector(2) double, Eigen::internal::Packet1cd, 
false, false>' has no member named 'pmul'
 pstore(py, psub(pcj.pmul(pc,yi),pm.pmul(ps,xi)));
 ~~~^~~~

Processed: reassign 875967 to src:libpsl, forcibly merging 874688 875967

2017-09-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 875967 src:libpsl
Bug #875967 [src:publicsuffix] publicsuffix: FTBFS - UnicodeDecodeError during 
tests
Bug reassigned from package 'src:publicsuffix' to 'src:libpsl'.
No longer marked as found in versions publicsuffix/20170828.2009-1.
Ignoring request to alter fixed versions of bug #875967 to the same values 
previously set
> forcemerge 874688 875967
Bug #874688 {Done: Daniel Kahn Gillmor } [src:libpsl] 
libpsl FTBFS: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in 
position 8046: ordinal not in range(128)
Bug #875967 [src:libpsl] publicsuffix: FTBFS - UnicodeDecodeError during tests
Marked Bug as done
Marked as fixed in versions libpsl/0.18.0-4.
Marked as found in versions libpsl/0.18.0-3.
Added tag(s) patch.
Merged 874688 875967
> thanks
Stopping processing here.

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



Bug#875967: publicsuffix: FTBFS - UnicodeDecodeError during tests

2017-09-19 Thread Daniel Kahn Gillmor
Control: forcemerge 874688 875967

On Sat 2017-09-16 18:10:05 +0200, Andreas Beckmann wrote:
> the last upload of publicsuffix did FTBFS:
>
> https://buildd.debian.org/status/fetch.php?pkg=publicsuffix=all=20170828.2009-1=1504820937=0

yep, that was due to a bug in libpsl (#874688), so it would have been
fixed with a give-back to the buildd network.

since that bug has since been fixed with a new upload of libpsl, the
latest upload of publicsuffix (from about an hour ago) should rebuild
fine.

thanks for the heads-up!

--dkg



Processed (with 1 error): Re: Bug#875967: publicsuffix: FTBFS - UnicodeDecodeError during tests

2017-09-19 Thread Debian Bug Tracking System
Processing control commands:

> forcemerge 874688 875967
Bug #874688 {Done: Daniel Kahn Gillmor } [src:libpsl] 
libpsl FTBFS: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in 
position 8046: ordinal not in range(128)
Unable to merge bugs because:
package of #875967 is 'src:publicsuffix' not 'src:libpsl'
Failed to forcibly merge 874688: Did not alter merged bugs.


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