date:20171206

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

> # since fixed in DSA
> severity 878144 serious
Bug #878144 [heimdal-kdc] CVE-2017-17439: Remote unauthenticated DoS in 
Heimdal-KDC 7.1
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 882122 is important

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

> severity 882122 important
Bug #882122 [thunderbird] thunderbird: Thunderbird can't connect to X server, 
fails to start
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#882553: marked as done (cross-toolchain-base-ports: missing build dependency on dwz)

Your message dated Thu, 07 Dec 2017 07:18:52 +
with message-id 
and subject line Bug#882553: fixed in cross-toolchain-base-ports 15
has caused the Debian Bug report #882553,
regarding cross-toolchain-base-ports: missing build dependency on dwz
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.)


-- 
882553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882553
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cross-toolchain-base-ports
Version: 13
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/cross-toolchain-base-ports.html

...
: # Strip shared libraries and binaries
set -e; for i in 
debian/binutils-alpha-linux-gnu/usr/lib/x86_64-linux-gnu/libbfd-*so 
debian/binutils-alpha-linux-gnu/usr/lib/x86_64-linux-gnu/libopcodes-*so $(file 
debian/binutils-alpha-linux-gnu/usr/bin/* |awk -F: '$0 !~ /script/ {print 
$1}'); do test ! -h $i || continue; test -f $i || continue; files="$files $i"; 
done; mkdir -p 
debian/binutils-alpha-linux-gnu-dbg/usr/lib/debug/.dwz/x86_64-linux-gnu; 
dwz=usr/lib/debug/.dwz/x86_64-linux-gnu/binutils-alpha-linux-gnu.debug; dwz -m 
debian/binutils-alpha-linux-gnu-dbg/$dwz -M /$dwz $files; objcopy 
--compress-debug-sections debian/binutils-alpha-linux-gnu-dbg/$dwz; for i in 
$files; do b_id=$(LC_ALL=C readelf -n $i | sed -n 's/ *Build ID: 
*\([0-9a-f][0-9a-f]*\)/\1/p'); if [ -z "$b_id" ]; then id=$(echo $i | sed -r 
's,debian/[^/]+,debian/binutils-alpha-linux-gnu-dbg/usr/lib/debug,'); echo 
strip $i; mkdir -p $(dirname $id); objcopy --only-keep-debug $i $id; chmod 644 
$id; strip --remove-section=.comment --remove-section=.note $i; objcopy --a
 dd-gnu-debuglink $id $i; else echo "ID: ${b_id} -> $(echo $i | sed 
's,debian/binutils-alpha-linux-gnu,,')"; d=usr/lib/debug/.build-id/${b_id:0:2}; 
f=${b_id:2}.debug; mkdir -p debian/binutils-alpha-linux-gnu-dbg/$d; objcopy 
--only-keep-debug --compress-debug-sections $i 
debian/binutils-alpha-linux-gnu-dbg/$d/$f; chmod 644 
debian/binutils-alpha-linux-gnu-dbg/$d/$f; strip --remove-section=.comment 
--remove-section=.note $i; fi; done
/bin/bash: dwz: command not found
debian/rules:807: recipe for target 'stamps/install.alpha' failed
make[1]: *** [stamps/install.alpha] Error 127
--- End Message ---
--- Begin Message ---
Source: cross-toolchain-base-ports
Source-Version: 15

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated 
cross-toolchain-base-ports package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 07 Dec 2017 07:57:13 +0100
Source: cross-toolchain-base-ports
Binary: linux-libc-dev-alpha-cross linux-libc-dev-hppa-cross 
linux-libc-dev-m68k-cross linux-libc-dev-mips64-cross 
linux-libc-dev-powerpc-cross linux-libc-dev-ppc64-cross 
linux-libc-dev-sh4-cross linux-libc-dev-sparc64-cross 
linux-libc-dev-powerpcspe-cross linux-libc-dev-mipsn32-cross 
linux-libc-dev-mipsn32el-cross linux-libc-dev-mipsr6-cross 
linux-libc-dev-mipsr6el-cross linux-libc-dev-mipsn32r6-cross 
linux-libc-dev-mipsn32r6el-cross linux-libc-dev-mips64r6-cross 
linux-libc-dev-mips64r6el-cross libc6.1-alpha-cross libc6.1-dev-alpha-cross 
libc6-hppa-cross libc6-dev-hppa-cross libc6-m68k-cross libc6-dev-m68k-cross 
libc6-mips64-cross libc6-dev-mips64-cross libc6-powerpc-cross 
libc6-dev-powerpc-cross libc6-ppc64-cross libc6-dev-ppc64-cross libc6-sh4-cross 
libc6-dev-sh4-cross libc6-sparc64-cross libc6-dev-sparc64-cross 
libc6-powerpcspe-cross libc6-dev-powerpcspe-cross libc6-mipsn32-cross 
libc6-dev-mipsn32-cross libc6-mipsn32el-cross libc6-dev-mipsn32el-cross 
libc6-mipsr6-cross
 libc6-dev-mipsr6-cross libc6-mipsr6el-cross libc6-dev-mipsr6el-cross 
libc6-mipsn32r6-cross libc6-dev-mipsn32r6-cross libc6-mipsn32r6el-cross 
libc6-dev-mipsn32r6el-cross libc6-mips64r6-cross libc6-dev-mips64r6-cross 
libc6-mips64r6el-cross libc6-dev-mips64r6el-cross libc6-powerpc-ppc64-cross

Bug#859052: marked as done (libevhtp: Please migrate to openssl1.1 in buster)

Your message dated Thu, 07 Dec 2017 07:04:19 +
with message-id 
and subject line Bug#859052: fixed in libevhtp 1.2.15-1
has caused the Debian Bug report #859052,
regarding libevhtp: Please migrate to openssl1.1 in buster
to be marked as done.

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

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


-- 
859052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859052
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libevhtp
Version: 1.2.11-1
Severity: important
Control: block 827061 by -1

Hi,

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

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

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

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


Kurt
--- End Message ---
--- Begin Message ---
Source: libevhtp
Source-Version: 1.2.15-1

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

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

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

Debian distribution maintenance software
pp.
Vincent Bernat  (supplier of updated libevhtp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 07 Dec 2017 07:08:46 +0100
Source: libevhtp
Binary: libevhtp0 libevhtp-dev libevhtp-doc
Architecture: source amd64 all
Version: 1.2.15-1
Distribution: unstable
Urgency: medium
Maintainer: Vincent Bernat 
Changed-By: Vincent Bernat 
Description:
 libevhtp-dev - Libevent based HTTP API - development files
 libevhtp-doc - Libevent based HTTP API - documentation
 libevhtp0  - Libevent based HTTP API
Closes: 859052
Changes:
 libevhtp (1.2.15-1) unstable; urgency=medium
 .
   * New upstream release.
  + Support for OpenSSL 1.1. Closes: #859052.
   * d/patches: drop all patches.
   * d/patches: fix compilation with shared libraries.
   * d/symbols: update (breaking ABI, but no reverse dependencies).
   * d/copyright: no more shipped version of oniguruma regex library.
   * d/control: bump Standards-Version.
Checksums-Sha1:
 b4f36bd1937b2da52fb7d37973a39a76ac0a974a 2069 libevhtp_1.2.15-1.dsc
 9e680b071da5938574f01375cfcd45c0c7e3185b 171933 libevhtp_1.2.15.orig.tar.gz
 8574cc7aabb102485adfef600bc84082fa1b9848 4788 libevhtp_1.2.15-1.debian.tar.xz
 49beb842a274f78dcd5a84a529d9e9ab9b3d6594 31636 libevhtp-dev_1.2.15-1_amd64.deb
 658d975f250245d6d4d14b4233f4e00d4e9aca96 476868 libevhtp-doc_1.2.15-1_all.deb
 7f90eef13bb35eace77e92915f86ee7f74d03491 74096 
libevhtp0-dbgsym_1.2.15-1_amd64.deb
 28d331fcc0511c26a8b79f3c81f37e6b33bb5e45 53184 libevhtp0_1.2.15-1_amd64.deb
 6a024bc9c652c70e339b8d9ce2d47631c607ded5 7787 libevhtp_1.2.15-1_amd64.buildinfo
Checksums-Sha256:
 96373d3abcbf3427e289756466d85fce50882bf5416a5e8b7158d20fb2837d0a 2069 
libevhtp_1.2.15-1.dsc
 f78ee8a34492e266fc1b6b9d4003825659df672da1cf918120217a0ee0d14ed3 171933 
libevhtp_1.2.15.orig.tar.gz
 808b0c67813a943eaa319a4229c5ce1d67d713ab9402c5ca7342a91cd54735d7 4788 
libevhtp_1.2.15-1.debian.tar.xz
 2f7ddf58465382826f7476e6b3e78113e28fe077e9db7611b314304be41c4670 31636 
libevhtp-dev_1.2.15-1_amd64.deb
 b9d4bba0507a5ad0a3df8422927279e53a1b9c52ecc2ab774836adc44679 476868 
libevhtp-doc_1.2.15-1_all.deb
 a99e092da0468751817906660ffe253b3049aebc42fcec69732ac99d69e9f30b 74096 
libevhtp0-dbgsym_1.2.15-1_amd64.deb
 9d327a0fe4290c89fda1d91db802ed45df212133fa1affc4d5780d8cfe746e9e 53184 
libevhtp0_1.2.15-1_amd64.deb
 9fddfd569a33ba053bfbaea2ee5552092f4237aceeaf3d6df26ae9642cfb5859 7787 
libevhtp_1.2.15-1_amd64.buildinfo
Files:
 f4b56543007aebf283bc414966620ef2 2069 libs optional libevhtp_1.2.15-1.dsc
 5f7dc0cb6b257f134d3e9e208b2095be

Processed: tagging 882414

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

> tags 882414 + moreinfo
Bug #882414 [src:linux] [src:linux] Oops: NULL pointer dereference - RIP: 
isci_task_abort_task+0x30/0x3e0 [isci]
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Processed: Re: Bug#883706: dolphin4 is still linked with libplasma3

Processing control commands:

> severity -1 important
Bug #883706 [dolphin4] dolphin4 is still linked with libplasma3
Severity set to 'important' from 'serious'
> tag -1 - patch
Bug #883706 [dolphin4] dolphin4 is still linked with libplasma3
Removed tag(s) patch.

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

Bug#883706: dolphin4 is still linked with libplasma3

2017-12-06 Thread Pino Toscano

Control: severity -1 important
Control: tag -1 - patch

In data mercoledì 6 dicembre 2017 19:33:10 CET, Adrian Bunk ha scritto:
> Package: dolphin4
> Version: 4:16.08.3-1
> Severity: serious
> Tags: patch buster sid
> 
> dolphin4 is still linked with libplasma3,
> which has to be removed for the qtwebkit removal.

NACK.

dolphin4 (which uses kdelibs4) is shipped only to provide file browsing
capabilities to konqueror (which uses kdelibs4).  In recent versions of
KDE Applications kde-baseapps does not exist anymore, replaced by split
tarballs (konqueror, kfind, keditbookmarks, kdialog).  Only konqueror
is available in experimental, the others are waiting in NEW.  Once all
are available, they will replace kde-baseapps in unstable (in a
coordinated upload with kde-l10n, since they ship translations), and
thus dolphin4 will be removed.

To be honest, it would be much easier if you could *wait* for the
completion of Applications 17.08 in unstable/testing, so there will be
few more kdelibs4-using sources either dropped (like dolphin4) or
ported to Frameworks.

-- 
Pino Toscano

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

Bug#883743: bzr: FTBFS on armel

2017-12-06 Thread Vagrant Cascadian

On 2017-12-06, Jelmer Vernooĳ wrote:
> On Wed, Dec 06, 2017 at 05:45:11PM -0800, Vagrant Cascadian wrote:
> Can you reproduce the issue once you set LC_ALL=C.UTF-8 ?
>
> The delta between -8 and -9 is minimal and not related to the test
> that failed, so I'm wondering if this is a spurious failure (timing?) of some
> sort or perhaps a regression introduced by a dependency.

Well, I managed to reproduce it on amd64 too, so I think this is a
different issue entirely than what caused the original armel build to
fail (which might have just been a transient failure)...

The following link should have two build logs, one with the C.UTF-8
patch applied to debian/rules, and one with without it, built with
sbuild:

  https://cascadia.debian.net/~vagrant/bzr/patched.build.gz
  https://cascadia.debian.net/~vagrant/bzr/unpatched.build.gz

The patched build succeeds, the unpatched build fails.

I'm guessing something in the toolchain changed the way it handles UTF-8
since the builds almost a month ago...

Hope that's helpful.

live well,
  vagrant

p.s. I noticed no almost no arch:all buildd logs, and very few recent
amd64 buildd logs... maybe save some bandwith for yourself and start
doing source-only uploads. :)

signature.asc
Description: PGP signature

Bug#878498: snakemake FTBFS with Python 3.6 as default

2017-12-06 Thread Andrey Rahmatullin

On Wed, Dec 06, 2017 at 10:14:45PM +0100, Andreas Tille wrote:
> control: tags -1 help
> 
> Hi,
> 
> I've upgraded snakemake in Git to latest upstream but its featuring the
> same issue.  I'm pretty sure you Python people know a simple answer for
> this issue.
Did you see this part?

> > The problem is the the following line in debian/rules:
> > 
> >   export PATH:=$(CURDIR)/.pybuild/pythonX.Y_3.5/build/bin:$(PATH)


-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#883615: Acknowledgement ([CRITICAL] Stretch p-u 9.3 breaks NVidia driver and X.org)

2017-12-07 5:43 GMT+01:00 Julien Aubin :

>
> 2017-12-06 21:50 GMT+01:00 Aurelien Jarno :
>
>> On 2017-12-06 19:39, Julien Aubin wrote:
>> > Weird... this time I re-upgraded libc6 and things work fine... looks
>> like
>> > something wrong went during the install. And I cannot reproduce the
>> issue
>> > anymore... :'( WTF ???
>>
>> Hmm, a bug has been introduced in libc6 version 2.24-11+deb9u2, which in
>> some conditions leave the /etc/ld.so.nohwcap file instead of removing it
>> just after the upgrade (see bug#883394). One of the condition is to have
>> libc6-i686 installed (while it can be safely removed), which seems to be
>> your case.
>>
>> I consider this bug harmless as it should not deactivate anything now
>> that the default libc is already i686 optimized. Also I don't see how it
>> could trigger the issue you described. Anyway better be safe than sorry,
>> could you please try to create this file with "touch /etc/ld.so.nohwcap"
>> as root and see if it makes the issue to reappear? Once the test is done
>> you can then remove it.
>>
>> Thanks,
>> Aurelien
>>
>
>
> Bingo ! It was exactly this !
>
> If I re-create the file for example it crashes glxgears. When I remove it
> glxgears works fine.
>
> With GDB, the stack trace for when I run glxgears :
>
> 0  0x76b311a4 in pthread_mutex_lock (mutex=0x7604e8c0) at
> forward.c:192
> #1  0x75de1308 in __glDispatchNewVendorID () from
> /usr/lib/x86_64-linux-gnu/libGLdispatch.so.0
> #2  0x760793c2 in ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
>
> #3  0x7607a1ac in ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
>
> #4  0x76073170 in glXChooseVisual () from
> /usr/lib/x86_64-linux-gnu/libGLX.so.0
> #5  0x779f in ?? ()
> #6  0x5ae7 in ?? ()
> #7  0x76a5c2e1 in __libc_start_main (main=0x5970, argc=1,
> argv=0x7fffe638, init=,
>fini=, rtld_fini=,
> stack_end=0x7fffe628) at ../csu/libc-start.c:291
> #8  0x646a in ?? ()
>
>
>
To be clear it looks like this file also affects libc6-amd64 behaviour...

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

Bug#883615: Acknowledgement ([CRITICAL] Stretch p-u 9.3 breaks NVidia driver and X.org)

2017-12-06 21:50 GMT+01:00 Aurelien Jarno :

> On 2017-12-06 19:39, Julien Aubin wrote:
> > Weird... this time I re-upgraded libc6 and things work fine... looks like
> > something wrong went during the install. And I cannot reproduce the issue
> > anymore... :'( WTF ???
>
> Hmm, a bug has been introduced in libc6 version 2.24-11+deb9u2, which in
> some conditions leave the /etc/ld.so.nohwcap file instead of removing it
> just after the upgrade (see bug#883394). One of the condition is to have
> libc6-i686 installed (while it can be safely removed), which seems to be
> your case.
>
> I consider this bug harmless as it should not deactivate anything now
> that the default libc is already i686 optimized. Also I don't see how it
> could trigger the issue you described. Anyway better be safe than sorry,
> could you please try to create this file with "touch /etc/ld.so.nohwcap"
> as root and see if it makes the issue to reappear? Once the test is done
> you can then remove it.
>
> Thanks,
> Aurelien
>


Bingo ! It was exactly this !

If I re-create the file for example it crashes glxgears. When I remove it
glxgears works fine.

With GDB, the stack trace for when I run glxgears :

0  0x76b311a4 in pthread_mutex_lock (mutex=0x7604e8c0) at
forward.c:192
#1  0x75de1308 in __glDispatchNewVendorID () from
/usr/lib/x86_64-linux-gnu/libGLdispatch.so.0
#2  0x760793c2 in ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
#3  0x7607a1ac in ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
#4  0x76073170 in glXChooseVisual () from
/usr/lib/x86_64-linux-gnu/libGLX.so.0
#5  0x779f in ?? ()
#6  0x5ae7 in ?? ()
#7  0x76a5c2e1 in __libc_start_main (main=0x5970, argc=1,
argv=0x7fffe638, init=,
   fini=, rtld_fini=,
stack_end=0x7fffe628) at ../csu/libc-start.c:291
#8  0x646a in ?? ()



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

Bug#883743: bzr: FTBFS on armel

2017-12-06 Thread Jelmer Vernooĳ

On Wed, Dec 06, 2017 at 05:45:11PM -0800, Vagrant Cascadian wrote:
> Package: bzr
> Version:  2.7.0+bzr6622-9
> Severity: serious
> Tags: patch
> 
> The last armel bzr build failed to build from source, and I've tried to
> reproduce the issue unsuccessfully.
> 
>   
> https://buildd.debian.org/status/fetch.php?pkg=bzr=armel=2.7.0%2Bbzr6622-9=1510195017=0
> 
> I tried building it on abel.debian.org, and it failed in a *different*
> way, complaining about unicode issues. Setting LC_ALL=C.UTF-8 seemed to
> fix that issue for me.
> 
> Forcing the test suite to run with the C.UTF-8 locale, available in all
> recent versions of Debian (and even some pretty old ones), at least
> fixed the unicode issues when run on abel.debian.org:
> 
> --- rules.orig2017-12-06 17:41:18.206442819 -0800
> +++ rules 2017-12-06 17:41:57.290537132 -0800
> @@ -24,6 +24,8 @@
>   BZR_PLUGIN_PATH=-site:-user \
>   BZR_DISABLE_PLUGINS=launchpad \
>   PYTHONPATH=$(wildcard $(CURDIR)/build/lib.*-$(PYVERSION)) \
> + LC_ALL=C.UTF-8 \
> + LANG=C.UTF-8 \
>   $(CURDIR)/build/scripts-$(PYVERSION)/bzr -Derror selftest -v 
> --parallel=fork
>  endif
>  
> 
> Maybe it's worth re-uploading with the above patch.
What failure do you get without LC_ALL=C.UTF-8 and LANG=C.UTF-8 set?

I'd rather avoid setting variables so that we can actually catch
and fix locale-related problems.


signature.asc
Description: PGP signature

Bug#883743: bzr: FTBFS on armel

2017-12-06 Thread Jelmer Vernooĳ

On Wed, Dec 06, 2017 at 05:45:11PM -0800, Vagrant Cascadian wrote:
> The last armel bzr build failed to build from source, and I've tried to
> reproduce the issue unsuccessfully.
> 
>   
> https://buildd.debian.org/status/fetch.php?pkg=bzr=armel=2.7.0%2Bbzr6622-9=1510195017=0
> 
> I tried building it on abel.debian.org, and it failed in a *different*
> way, complaining about unicode issues. Setting LC_ALL=C.UTF-8 seemed to
> fix that issue for me.
Thanks for reporting this.

Can you reproduce the issue once you set LC_ALL=C.UTF-8 ?

The delta between -8 and -9 is minimal and not related to the test
that failed, so I'm wondering if this is a spurious failure (timing?) of some
sort or perhaps a regression introduced by a dependency.

Jelmer

signature.asc
Description: PGP signature

Bug#883743: bzr: FTBFS on armel

2017-12-06 Thread Vagrant Cascadian

Package: bzr
Version:  2.7.0+bzr6622-9
Severity: serious
Tags: patch

The last armel bzr build failed to build from source, and I've tried to
reproduce the issue unsuccessfully.

  
https://buildd.debian.org/status/fetch.php?pkg=bzr=armel=2.7.0%2Bbzr6622-9=1510195017=0

I tried building it on abel.debian.org, and it failed in a *different*
way, complaining about unicode issues. Setting LC_ALL=C.UTF-8 seemed to
fix that issue for me.

Forcing the test suite to run with the C.UTF-8 locale, available in all
recent versions of Debian (and even some pretty old ones), at least
fixed the unicode issues when run on abel.debian.org:

--- rules.orig  2017-12-06 17:41:18.206442819 -0800
+++ rules   2017-12-06 17:41:57.290537132 -0800
@@ -24,6 +24,8 @@
BZR_PLUGIN_PATH=-site:-user \
BZR_DISABLE_PLUGINS=launchpad \
PYTHONPATH=$(wildcard $(CURDIR)/build/lib.*-$(PYVERSION)) \
+   LC_ALL=C.UTF-8 \
+   LANG=C.UTF-8 \
$(CURDIR)/build/scripts-$(PYVERSION)/bzr -Derror selftest -v 
--parallel=fork
 endif
 

Maybe it's worth re-uploading with the above patch.


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#883741: pyspread: Spreadsheet canvas won't show with newest update

2017-12-06 Thread Lorenz Minder

Package: pyspread
Version: 1.1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

With the latest apt-get upgrade, the spreadsheet canvas of pyspread will
no longer show, instead it's just a white box without the grid.  This
makes the pyspread package unusable.  The console is full of error
messages like the following:

Traceback (most recent call last):
  File "/usr/share/pyspread/src/gui/_grid_renderer.py", line 340, in Draw
grid._view_frozen)
  File "/usr/share/pyspread/src/gui/_grid_renderer.py", line 263, in 
_get_cairo_bmp
context = wx.lib.wxcairo.ContextFromDC(mdc)
  File "/usr/lib/python2.7/dist-packages/wx-3.0-gtk2/wx/lib/wxcairo.py", line 
137, in ContextFromDC
ctx = pycairoAPI.Context_FromContext(ctxptr, pycairoAPI.Context_Type, None)
AttributeError: 'Pycairo_CAPI' object has no attribute 'Context_FromContext'

I am not sure what caused this problem, but am now seeing this on
several machines, and believe it to be universal.  To reproduce it,
simpy start pyspread (with no spreadsheet file at all).

Judging from the error messages, the bug might not be in the pyspread
package, but in some package it depends on.

I don't know a workaround for this problem.

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

Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages pyspread depends on:
ii  gir1.2-pango-1.0 1.40.12-1
ii  libcairo-gobject21.15.8-2
ii  libpangocairo-1.0-0  1.40.12-1
ii  python   2.7.14-1
ii  python-cairo 1.15.4-2
ii  python-gnupg 0.4.1-1
ii  python-gtk2  2.24.0-5.1+b1
ii  python-matplotlib2.0.0+dfsg1-2+b1
ii  python-numpy 1:1.13.3-2
ii  python-wxgtk3.0  3.0.2.0+dfsg-5

Versions of packages pyspread recommends:
ii  gpg-agent [gnupg-agent]  2.2.2-1
ii  python-jedi  0.10.2-1
ii  python-xlrd  1.1.0-1
ii  python-xlwt  0.7.5+debian1-1

Versions of packages pyspread suggests:
pn  python-mpltoolkits.basemap  
pn  ttf-mscorefonts-installer   

-- no debconf information

Bug#883521: texlive-bin: FTBFS with poppler 0.61.1

2017-12-06 Thread Norbert Preining

> As soon as we know how to address 879801 a fix will be uploaded.

No need to wait for 879801. ICU is currently not uploaded to unstable so
this can be deferred a bit.

I have already prepared packages for this fix (poppler) only and will
upload soon after a round of testing (internet connection in China
permitting).

Best

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Processed: Re: Bug#883672: incorrect rendering of pdf using libpoppler68 backend

Processing control commands:

> severity -1 normal
Bug #883672 [src:poppler] incorrect rendering of pdf using libpoppler68 backend
Severity set to 'normal' from 'serious'

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

Bug#883672: incorrect rendering of pdf using libpoppler68 backend

2017-12-06 Thread Emilio Pozuelo Monfort

Control: severity -1 normal

On 06/12/17 13:41, Adrian Bunk wrote:
> Control: reassign -1 src:poppler 0.57.0-2
> 
> Reassigning to the correct package.
> 
> On Wed, Dec 06, 2017 at 04:10:08PM +0530, Marcus Britanicus wrote:
>> Package: bugs.debian.org
>> Severity: serious
>>
>> All PDF viewers using libpoppler68 (0.57.0-2) backed do not render some PDFs
>> incorrectly. In most cases, some text is not rendered at all and symbols and
>> images only are rendered. This issue is seen in okular, evince, zathura,
>> qpdfview, and two custom pdf viewers (based on Qt4 and Qt5) written by me to
>> test issue. MuPDF and firefox do render the same PDF correctly.

You are going to have to attach or link to such a file. Also please try with
applications linked against poppler 0.61.1 (libpoppler72) first, which will soon
be available.

Cheers,
Emilio

Bug#883732: flask-migrate FTBFS: test failures

Source: flask-migrate
Version: 2.1.1-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=flask-migrate=all=2.1.1-1=1512596402=0

...
I: pybuild base:184: python3.6 setup.py test 
running test
running egg_info
writing Flask_Migrate.egg-info/PKG-INFO
writing dependency_links to Flask_Migrate.egg-info/dependency_links.txt
writing entry points to Flask_Migrate.egg-info/entry_points.txt
writing requirements to Flask_Migrate.egg-info/requires.txt
writing top-level names to Flask_Migrate.egg-info/top_level.txt
reading manifest file 'Flask_Migrate.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'Flask_Migrate.egg-info/SOURCES.txt'
running build_ext
test_multidb_migrate_upgrade (tests.test_multidb_migrate_flaskcli.TestMigrate) 
... FAIL
test_alembic_version (tests.test_migrate_flaskcli.TestMigrate) ... ok
test_compare_type (tests.test_migrate_flaskcli.TestMigrate) ... FAIL
test_custom_directory (tests.test_migrate_flaskcli.TestMigrate) ... FAIL
test_migrate_upgrade (tests.test_migrate_flaskcli.TestMigrate) ... FAIL
test_multidb_migrate_upgrade (tests.test_multidb_migrate.TestMigrate) ... ok
test_alembic_version (tests.test_migrate.TestMigrate) ... ok
test_compare_type (tests.test_migrate.TestMigrate) ... ok
test_custom_directory (tests.test_migrate.TestMigrate) ... ok
test_migrate_upgrade (tests.test_migrate.TestMigrate) ... ok

==
FAIL: test_multidb_migrate_upgrade 
(tests.test_multidb_migrate_flaskcli.TestMigrate)
--
Traceback (most recent call last):
  File "/<>/tests/test_multidb_migrate_flaskcli.py", line 45, in 
test_multidb_migrate_upgrade
self.assertTrue(s == 0)
AssertionError: False is not true

==
FAIL: test_compare_type (tests.test_migrate_flaskcli.TestMigrate)
--
Traceback (most recent call last):
  File "/<>/tests/test_migrate_flaskcli.py", line 80, in 
test_compare_type
self.assertTrue(s == 0)
AssertionError: False is not true

==
FAIL: test_custom_directory (tests.test_migrate_flaskcli.TestMigrate)
--
Traceback (most recent call last):
  File "/<>/tests/test_migrate_flaskcli.py", line 68, in 
test_custom_directory
self.assertTrue(s == 0)
AssertionError: False is not true

==
FAIL: test_migrate_upgrade (tests.test_migrate_flaskcli.TestMigrate)
--
Traceback (most recent call last):
  File "/<>/tests/test_migrate_flaskcli.py", line 56, in 
test_migrate_upgrade
self.assertTrue(s == 0)
AssertionError: False is not true

--
Ran 10 tests in 19.206s

FAILED (failures=4)
Test failed: 
error: Test failed: 
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: 
python3.6 setup.py test 
dh_auto_test: pybuild --test -i python{version} -p 3.6 returned exit code 13
debian/rules:10: recipe for target 'build-indep' failed
make: *** [build-indep] Error 25

Processed: Correct fixed version in source package

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

> # Remove fixed version from -dev package ...
> notfixed 878794 golang-github-nbutton23-zxcvbn-go-dev/0.1-2
Bug #878794 {Done: "Dr. Tobias Quathamer" } 
[golang-github-nbutton23-zxcvbn-go-dev] golang-github-nbutton23-zxcvbn-go-dev 
0.0~git20170830.0.f4cd9f5-2 causes FTBFS in golang-github-chzyer-readline
The source golang-github-nbutton23-zxcvbn-go-dev and version 0.1-2 do not 
appear to match any binary packages
No longer marked as fixed in versions 
golang-github-nbutton23-zxcvbn-go-dev/0.1-2.
> # ... and use source package instead.
> fixed 878794 golang-github-nbutton23-zxcvbn-go/0.1-2
Bug #878794 {Done: "Dr. Tobias Quathamer" } 
[golang-github-nbutton23-zxcvbn-go-dev] golang-github-nbutton23-zxcvbn-go-dev 
0.0~git20170830.0.f4cd9f5-2 causes FTBFS in golang-github-chzyer-readline
Marked as fixed in versions golang-github-nbutton23-zxcvbn-go/0.1-2.
> thanks
Stopping processing here.

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

Processed: bug 882372 is forwarded to https://github.com/blackducksoftware/ohcount/issues/57

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

> forwarded 882372 https://github.com/blackducksoftware/ohcount/issues/57
Bug #882372 [ohcount] ohcount: CVE-2017-16926: Command injection through file 
names
Set Bug forwarded-to-address to 
'https://github.com/blackducksoftware/ohcount/issues/57'.
> thanks
Stopping processing here.

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

Bug#883731: audacious: Debian packaging has incorrect license

2017-12-06 Thread John Lindgren

Package: audacious
Version: 3.9-2
Severity: serious

Per Debian policy 2.3:

"Every package must be accompanied by a verbatim copy of its copyright
information and distribution license in the file 
/usr/share/doc/package/copyright
(see Copyright information for further details)."

The file /usr/share/doc/audacious/copyright shipped in the Debian package
is out of date and does not match the current Audacious license (GPL3 vs.
BSD 2-clause).

Worse, the Debian package patches out[1] the upstream license file which
is normally installed under /usr/share/audacious/COPYING and visible in
the "About" window when running Audacious.

You are currently distributing Audacious in violation both of our license
and of Debian's own policy.  Please include the original upstream license,
verbatim, in the Debian package, or stop distributing Audacious.

Thank you,

John Lindgren
Audacious maintainer

[1] 
https://sources.debian.org/patches/audacious/3.9-2/use-system-licenses.patch/

Bug#864965: current version does not need python-kde4

2017-12-06 Thread Wolfgang Rohdewald

Buster is on kajongg 16.08, tomorrow KDE 17.12 will be tagged.

Please consider updating.

The depencendy of python-kde4 has gone.

17.12 is ported to python3, python2 is not supported anymore.

17.12 is ported to qt5, qt4 is not supported anymore.

New dependency is twisted 16.6.0 but Buster already has 17.9.0

17.12 comes with a lot of cleanups, removing many bugs,
especially about unicode.

Processed: Re: Bug#883521: texlive-bin: FTBFS with poppler 0.61.1

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

> severity 883521 serious
Bug #883521 [src:texlive-bin] texlive-bin: FTBFS with poppler 0.61.1
Severity set to 'serious' from 'important'
> tags 883521 +pending +patch
Bug #883521 [src:texlive-bin] texlive-bin: FTBFS with poppler 0.61.1
Added tag(s) pending.
Bug #883521 [src:texlive-bin] texlive-bin: FTBFS with poppler 0.61.1
Added tag(s) patch.
> stop
Stopping processing here.

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

Processed: Re: Bug#878498: snakemake FTBFS with Python 3.6 as default

Processing control commands:

> tags -1 help
Bug #878498 [src:snakemake] snakemake FTBFS with Python 3.6 as default
Added tag(s) help.

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

Bug#878498: snakemake FTBFS with Python 3.6 as default

control: tags -1 help

Hi,

I've upgraded snakemake in Git to latest upstream but its featuring the
same issue.  I'm pretty sure you Python people know a simple answer for
this issue.

Any help would be welcome

  Andreas.

On Sat, Oct 14, 2017 at 05:33:22AM +0300, Adrian Bunk wrote:
> Source: snakemake
> Version: 3.10.0-1
> Severity: serious
> Tags: buster sid
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/snakemake.html
> 
> ...
> ==
> ERROR: Failure: Exception (snakemake not in PATH. For testing, install 
> snakemake with 'pip install -e .'. You should do this in a separate 
> environment (via conda or virtualenv).)
> --
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/nose/failure.py", line 39, in runTest
> raise self.exc_val.with_traceback(self.tb)
>   File "/usr/lib/python3/dist-packages/nose/loader.py", line 418, in 
> loadTestsFromName
> addr.filename, addr.module)
>   File "/usr/lib/python3/dist-packages/nose/importer.py", line 47, in 
> importFromPath
> return self.importFromDir(dir_path, fqname)
>   File "/usr/lib/python3/dist-packages/nose/importer.py", line 94, in 
> importFromDir
> mod = load_module(part_fqname, fh, filename, desc)
>   File "/usr/lib/python3.6/imp.py", line 235, in load_module
> return load_source(name, filename, file)
>   File "/usr/lib/python3.6/imp.py", line 172, in load_source
> module = _load(spec)
>   File "", line 684, in _load
>   File "", line 665, in _load_unlocked
>   File "", line 678, in exec_module
>   File "", line 219, in _call_with_frames_removed
>   File 
> "/build/1st/snakemake-3.10.0/.pybuild/pythonX.Y_3.6/build/tests/tests.py", 
> line 21, in 
> raise Exception("snakemake not in PATH. For testing, install snakemake 
> with "
> Exception: snakemake not in PATH. For testing, install snakemake with 'pip 
> install -e .'. You should do this in a separate environment (via conda or 
> virtualenv).
> 
> --
> Ran 4 tests in 0.535s
> 
> FAILED (errors=1)
> E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd 
> /build/1st/snakemake-3.10.0/.pybuild/pythonX.Y_3.6/build; python3.6 -m nose 
> tests
> dh_auto_test: pybuild --test --test-nose -i python{version} -p 3.6 returned 
> exit code 13
> debian/rules:18: recipe for target 'build' failed
> make: *** [build] Error 25
> 
> 
> 
> The problem is the the following line in debian/rules:
> 
>   export PATH:=$(CURDIR)/.pybuild/pythonX.Y_3.5/build/bin:$(PATH)
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
> 

-- 
http://fam-tille.de

Bug#880893: marked as done (flask-migrate FTBFS: FAIL: test_multidb_migrate_upgrade (tests.test_multidb_migrate.TestMigrate))

Your message dated Wed, 06 Dec 2017 21:05:53 +
with message-id 
and subject line Bug#880893: fixed in flask-migrate 2.1.1-1
has caused the Debian Bug report #880893,
regarding flask-migrate FTBFS: FAIL: test_multidb_migrate_upgrade 
(tests.test_multidb_migrate.TestMigrate)
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.)


-- 
880893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880893
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flask-migrate
Version: 1.7.0-1
Severity: serious
Tags: buster sid

Some recent change in unstable makes flask-migrate FTBFS:

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

...
==
FAIL: test_multidb_migrate_upgrade (tests.test_multidb_migrate.TestMigrate)
--
Traceback (most recent call last):
  File "/build/1st/flask-migrate-1.7.0/tests/test_multidb_migrate.py", line 57, 
in test_multidb_migrate_upgrade
self.assertEqual(tables, [('alembic_version',), ('user',)])
AssertionError: Lists differ: [(u'alembic_version',), (u'sql... != 
[('alembic_version',), ('user'...

First differing element 1:
(u'sqlite_autoindex_alembic_version_1',)
('user',)

First list contains 1 additional elements.
First extra element 2:
(u'user',)

- [(u'alembic_version',), (u'sqlite_autoindex_alembic_version_1',), (u'user',)]
+ [('alembic_version',), ('user',)]

--
Ran 5 tests in 6.824s

FAILED (failures=1)
Test failed: 
error: Test failed: 
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: 
python2.7 setup.py test 
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
debian/rules:10: recipe for target 'build' failed
make: *** [build] Error 25
--- End Message ---
--- Begin Message ---
Source: flask-migrate
Source-Version: 2.1.1-1

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated flask-migrate package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 06 Dec 2017 21:17:27 +0100
Source: flask-migrate
Binary: python-flask-migrate python3-flask-migrate
Architecture: source
Version: 2.1.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Christoph Berg 
Description:
 python-flask-migrate - SQLAlchemy database migrations for Flask applications 
using Alemb
 python3-flask-migrate - SQLAlchemy migrations for Flask using Alembic and 
Python 3
Closes: 866565 880893
Changes:
 flask-migrate (2.1.1-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release.
 + Fixes FAIL: test_multidb_migrate_upgrade. (Closes: #880893)
   * Add Michael Hudson-Doyle's patch to fix failure with mixed python2/3
 versions. Thanks! (Closes: #866565)
Checksums-Sha1:
 943acfd849ba5bedef1a447bcbd4f323fc3fa6c8 2329 flask-migrate_2.1.1-1.dsc
 681d8fc753d1436e88121f26766ce410edd1f0a1 15034 flask-migrate_2.1.1.orig.tar.gz
 6d830cd1e55dbe64ac210463c08c94a04a71ee78 3400 
flask-migrate_2.1.1-1.debian.tar.xz
 b8c61a1a0b6432f372c2b288bbf688823aa6affe 6992 
flask-migrate_2.1.1-1_source.buildinfo
Checksums-Sha256:
 ffb87b41d26b6d6be2978d4881eae3d0e3fa61e4935a855580e07b072ee734a1 2329 
flask-migrate_2.1.1-1.dsc
 b709ca8642559c3c5a81a33ab10839fa052177accd5ba821047a99db635255ed 15034 
flask-migrate_2.1.1.orig.tar.gz
 bc45501e52a7595158791995fb920dcecb581bf370ffb03c73e13ef1fbf20a86 3400 
flask-migrate_2.1.1-1.debian.tar.xz
 a23129887710250c674ec5529cd3c9bef4f5cbd9677d94a069ebb31e01c6afad 6992 
flask-migrate_2.1.1-1_source.buildinfo
Files:
 064478be23ccd13ae6e9b68924763b17 2329 python optional flask-migrate_2.1.1-1.dsc

Bug#883615: Acknowledgement ([CRITICAL] Stretch p-u 9.3 breaks NVidia driver and X.org)

2017-12-06 Thread Aurelien Jarno

On 2017-12-06 19:39, Julien Aubin wrote:
> Weird... this time I re-upgraded libc6 and things work fine... looks like
> something wrong went during the install. And I cannot reproduce the issue
> anymore... :'( WTF ???

Hmm, a bug has been introduced in libc6 version 2.24-11+deb9u2, which in
some conditions leave the /etc/ld.so.nohwcap file instead of removing it
just after the upgrade (see bug#883394). One of the condition is to have
libc6-i686 installed (while it can be safely removed), which seems to be
your case.

I consider this bug harmless as it should not deactivate anything now
that the default libc is already i686 optimized. Also I don't see how it
could trigger the issue you described. Anyway better be safe than sorry,
could you please try to create this file with "touch /etc/ld.so.nohwcap"
as root and see if it makes the issue to reappear? Once the test is done
you can then remove it.

Thanks,
Aurelien

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

Bug#882372: Wheezy update of ohcount?

2017-12-06 Thread Peter Degen-Portnoy

Dear Raphaël Hertzog;

Peter Degen-Portnoy of the Black Duck Open Hub development team here.  We 
maintain Ohcount and are aware of the defect. An issue has been opened in the 
GitHub repository for Ohcount: 
https://github.com/blackducksoftware/ohcount/issues/57

Work is currently underway to address the defect.

Sincerely,


Peter Degen-Portnoy


---

Black Duck Software

Peter Degen-Portnoy

Software Engineering Manager / Open Hub Team Lead
Black Duck Software
Black Duck Open Hub



On Thu, 23 Nov 2017 11:40:11 +0100 Raphael Hertzog wrote:
> Hello Sylvestre,
>
> The Debian LTS team would like to fix the security issues which are
> currently open in the Wheezy version of ohcount:
> https://security-tracker.debian.org/tracker/CVE-2017-16926
>
> Would you like to take care of this yourself?
>
> I tried to file an upstream bug as a first step (since there is not patch
> available yet) but there is no upstream bug tracker apparently... and last
> upstream activity dates back to 2010. I pinged the project owner on
> sourceforge with its integrated messaging feature but I'm not sure that I
> will get any reply back.
>
> Do you have contacts with the upstream authors ?
>
> In any case, if you want to handle the wheezy upload, then
> please follow the workflow we have defined here:
> https://wiki.debian.org/LTS/Development
>
> If that workflow is a burden to you, feel free to just prepare an
> updated source package and send it to debian-...@lists.debian.org
> (via a debdiff, or with an URL pointing to the source package,
> or even with a pointer to your packaging repository), and the members
> of the LTS team will take care of the rest. Indicate clearly whether you
> have tested the updated package or not.
>
> If you don't want to take care of this update, it's not a problem, we
> will do our best with your package. Just let us know whether you would
> like to review and/or test the updated package before it gets released.
>
> You can also opt-out from receiving future similar emails in your
> answer and then the LTS Team will take care of ohcount updates
> for the LTS releases.
>
> Thank you very much.
>
> Raphaël Hertzog,
> on behalf of the Debian LTS team.
>
> PS: A member of the LTS team might start working on this update at
> any point in time. You can verify whether someone is registered
> on this update in this file:
> https://anonscm.debian.org/viewvc/secure-testing/data/dla-needed.txt?view=markup
> --
> Raphaël Hertzog ◈ Debian Developer
>
> Support Debian LTS: https://www.freexian.com/services/debian-lts.html
> Learn to master Debian: https://debian-handbook.info/get/
>
>

Processed: found 883621 in 2:16.0.3-5

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

> found 883621 2:16.0.3-5
Bug #883621 [src:nova] nova: CVE-2017-17051: Nova FilterScheduler doubles 
resource allocations during rebuild with new image
Marked as found in versions nova/2:16.0.3-5.
> thanks
Stopping processing here.

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

Bug#790601: revelation: depends on python-gnome2 which is deprecated

2017-12-06 Thread Olivier Berger

Hi.

Just for the records, it's keepass2, not keypass2, sorry.

Best regards,

Olivier Berger  writes:

> Responding to myself,
>
> On Sun, Dec 03, 2017 at 03:50:57PM +0100, Olivier Berger wrote:
>> 
>> I think that it would be great to have some migration options to other 
>> password managers.
>> 
>> Would you have any suggestion ?
>> 
>
> It seems that keypass2 could be an option, importing from the Revelation XML 
> (which can be exported from Revelation before upgrade/switch).
>
> Hope this helps,
> -- 
> Olivier BERGER 
> http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8
> Ingenieur Recherche - Dept INF
> Institut Mines-Telecom, Telecom SudParis, Evry (France)
>
>

-- 
Olivier BERGER 
http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8
Ingenieur Recherche - Dept INF
Institut Mines-Telecom, Telecom SudParis, Evry (France)

Bug#883621: CVE-2017-17051 not fixed?

2017-12-06 Thread Salvatore Bonaccorso

Control: reopen -1
Control: found -1 2:16.0.3-1
Control: forwarded -1 https://launchpad.net/bugs/1732976

Hi Thomas,

CVE-2017-17051 was not fixed afaics, only the regression which was
introduced by OSSA-2017-005.

See http://www.openwall.com/lists/oss-security/2017/12/05/5 for
CVE-2017-17051.

Could you relook?

Regards,
Salvatore

Processed: Bug#883621 CVE-2017-17051 not fixed?

Processing control commands:

> reopen -1
Bug #883621 {Done: Thomas Goirand } [src:nova] nova: 
CVE-2017-17051: Nova FilterScheduler doubles resource allocations during 
rebuild with new image
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions nova/2:16.0.3-5.
> found -1 2:16.0.3-1
Bug #883621 [src:nova] nova: CVE-2017-17051: Nova FilterScheduler doubles 
resource allocations during rebuild with new image
Ignoring request to alter found versions of bug #883621 to the same values 
previously set
> forwarded -1 https://launchpad.net/bugs/1732976
Bug #883621 [src:nova] nova: CVE-2017-17051: Nova FilterScheduler doubles 
resource allocations during rebuild with new image
Ignoring request to change the forwarded-to-address of bug#883621 to the same 
value

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

Processed: bug 883621 is forwarded to https://launchpad.net/bugs/1732976

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

> forwarded 883621 https://launchpad.net/bugs/1732976
Bug #883621 {Done: Thomas Goirand } [src:nova] nova: 
CVE-2017-17051: Nova FilterScheduler doubles resource allocations during 
rebuild with new image
Set Bug forwarded-to-address to 'https://launchpad.net/bugs/1732976'.
> thanks
Stopping processing here.

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

Bug#880893: marked as pending

2017-12-06 Thread Christoph Berg

tag 880893 pending
thanks

Hello,

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


https://anonscm.debian.org/cgit/python-modules/packages/flask-migrate.git/commit/?id=7c2bac3

---
commit 7c2bac39578783ab90a05e1712839c15b8d3b98d
Author: Christoph Berg 
Date:   Wed Dec 6 21:16:10 2017 +0100

Add Michael Hudson-Doyle's patch to fix failure with mixed python2/3 
versions.

* New upstream version.
  + Fixes FAIL: test_multidb_migrate_upgrade. (Closes: #880893)
* Add Michael Hudson-Doyle's patch to fix failure with mixed python2/3
  versions. Thanks! (Closes: #866565)

diff --git a/debian/changelog b/debian/changelog
index 6079762..9f930d9 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -2,6 +2,9 @@ flask-migrate (2.1.1-1) UNRELEASED; urgency=medium
 
   * Team upload.
   * New upstream release.
++ Fixes FAIL: test_multidb_migrate_upgrade. (Closes: #880893)
+  * Add Michael Hudson-Doyle's patch to fix failure with mixed python2/3
+versions. Thanks! (Closes: #866565)
 
  -- Christoph Berg   Wed, 06 Dec 2017 19:23:04 +0100

Processed: Bug#880893 marked as pending

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

> tag 880893 pending
Bug #880893 [src:flask-migrate] flask-migrate FTBFS: FAIL: 
test_multidb_migrate_upgrade (tests.test_multidb_migrate.TestMigrate)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#883615: sarah,your recent order31716173

2017-12-06 Thread Sarah Bell

I havent made any purchases

On Dec 6, 2017 10:50 AM, "Thank you"  wrote:

Please confirm receipt

































































Okay found the culprit : libc6 Issue appears with the one from 9.3 but not
9.2 2017-12-06 11:56 GMT+01:00 Julien Aubin : > > > Le 6 déc. 2017 11:51,
"Luca Boccassi" a écrit : > > On Wed, 2017-12-06 at 11:37 +0100, Andreas
Beckmann wrote: > > On 2017-12-06 10:53, Julien Aubin wrote: > > > Okay I
will try it. Could you please provide me the build guide and > > > install
> > > guide ? > > > > From README.source: > > > > Building "bleeding edge"
from SVN for users > > > > As new upstream versions of the proprietary
driver are released, > > upload > > might not happen immediately. This
might be for various reasons, > > including > > waiting for new binary
packages to clear the NEW queue. > > Users wishing to try to build new
version locally can follow the > > instructions on the Debian wiki: > > > >
https://wiki.debian.org/NvidiaGraphicsDrivers#Building_newer_rele > >
ases_from_SVN > > > > WARNING: these will most likely be work in progress,
and the > > final upload > > may be different and may not support clean
upgrades from/to the > > versions > > uploaded in the archive. > > > > > >
In your case, it is branches/384-stretch-backports. > > > > Please let us
know about any issues you encounter with these > > instructions. > > > > >
> Andreas > > 375.82 has been in sid/buster for months now, it's very
strange that it > wasn't reported before - a GLX crash is not a subtle
problem that might > get overlooked > > > Yup but not sure people use a
Pascal GPU. What is granted is that the > issue appeared after last update
to stretch-proposed-updates, but only on > my box with a Pascal GPU. > > I
suspect the code paths used are not the same per GPU... > > If you wish I
can send you my sources.list, my /etc and the list of > installed packages.
I do not have weird things, only additional repos for > marginal packages
like deb-multimedia or virtualbox. > > > -- > Kind regards, > Luca Boccassi
> > >

Bug#867642: marked as done (capistrano: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: expect(out).to match(/\bCapistrano Version\b/))

Your message dated Wed, 06 Dec 2017 19:33:49 +
with message-id 
and subject line Bug#867642: fixed in capistrano 3.10.0-1
has caused the Debian Bug report #867642,
regarding capistrano: FTBFS: ERROR: Test "ruby2.3" failed:  Failure/Error: 
expect(out).to match(/\bCapistrano Version\b/)
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.)


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

Hi,

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

Relevant part (hopefully):
>  Failure/Error: expect(out).to match(/\bCapistrano Version\b/)
> 
>expected "" to match /\bCapistrano Version\b/
>Diff:
>@@ -1,2 +1,2 @@
>-/\bCapistrano Version\b/
>+""
>  # ./spec/lib/capistrano/application_spec.rb:30:in `block (2 levels) in 
> '
> 
> Finished in 0.16156 seconds (files took 0.38392 seconds to load)
> 270 examples, 1 failure, 2 pending
> 
> Failed examples:
> 
> rspec ./spec/lib/capistrano/application_spec.rb:26 # Capistrano::Application 
> overrides the rake method, but still prints the rake version
> 
> Randomized with seed 11779
> 
> /usr/bin/ruby2.3 /usr/bin/rspec --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb 
> failed
> ERROR: Test "ruby2.3" failed: 

The full build log is available from:
   http://aws-logs.debian.net/2017/07/07/capistrano_3.4.0-1_unstable.log

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

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

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

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

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

Debian distribution maintenance software
pp.
Samuel Henrique  (supplier of updated capistrano 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, 28 Nov 2017 23:06:30 -0200
Source: capistrano
Binary: capistrano
Architecture: source
Version: 3.10.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Samuel Henrique 
Description:
 capistrano - tool to execute commands in parallel on multiple servers
Closes: 867642
Changes:
 capistrano (3.10.0-1) unstable; urgency=medium
 .
   [ Antonio Terceiro ]
   * Remove myself from Uploaders:
   * Add Testsuite: header
 .
   [ Samuel Henrique ]
   * Add myself to uploaders
   * New upstream version 3.10.0
   * Bump DH level to 10
   * Bump Standards-Version to 4.1.1
   * Use https on d/watch
   * d/cap.1: fill Name field
   * d/copyright: update entries
   * d/patches/skip_tests: new patch to address FTBFS (closes: #867642)
Checksums-Sha1:
 e0f35e6fcca773bf94b44bff87f1525610c1af10 2128 capistrano_3.10.0-1.dsc
 03173305ed58ec666b17f5a95a4f4a3fa5da4514 75743 capistrano_3.10.0.orig.tar.gz
 fd38f8b5ad42038e238f90f72119cd7e0d220259 6068 capistrano_3.10.0-1.debian.tar.xz
 3495eb8563d1bcd917fdadb44348eea287ad008f 6724 
capistrano_3.10.0-1_source.buildinfo
Checksums-Sha256:
 64c80d0e58e6103271093539f12594edc5a6a1262c544421d2636880fe191d8d 2128 
capistrano_3.10.0-1.dsc
 36a525f7fa9635ecb0d915c33194f8a89e9d9cbfd7cfd42975746a32137e1852 75743 
capistrano_3.10.0.orig.tar.gz
 0fdef834666c8dde9ebfa0a2fbf815e7c065e98c31a0b8c92f607e8691fad3a9 6068 
capistrano_3.10.0-1.debian.tar.xz
 f94182629d62b503282d5f04befa2420e72099b46fe8e681acf834c004c92ffc 6724 
capistrano_3.10.0-1_source.buildinfo
Files:
 7ffd04e50b09603890b1bd244012b505 2128 ruby optional capistrano_3.10.0-1.dsc

Processed: fixed 861840 in thunderbird/1:52.5.0-1

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

> fixed 861840 thunderbird/1:52.5.0-1
Bug #861840 {Done: Carsten Schoenert } 
[calendar-google-provider] thunderbird: gmail authentication broken
Marked as fixed in versions thunderbird/1:52.5.0-1.
> thanks
Stopping processing here.

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

Bug#878101: nemo: Nemo segfault on thumbnailing of a moved file over smb

2017-12-06 Thread Zeljko Culek


Hello,

Is this going to be fixed in Debian Stable/Stretch? If it is, when we 
can expect to have the fixed Nemo version? This bug is so annoying... 
almost making Nemo unusable for moving files around. :\


Thank you!

Bug#875030: libkdewebkit5/libplasma3 removal from buster

2017-12-06 Thread Ralf Jung

Hi,

I filed a removal request for lightdm-kde at
.

; Ralf

Bug#883615: Acknowledgement ([CRITICAL] Stretch p-u 9.3 breaks NVidia driver and X.org)

Thanks a lot and sorry for the inconvenience.

2017-12-06 19:45 GMT+01:00 Andreas Beckmann :

> Control: tag -1 unreproducible
> Control: close -1
>
> On 2017-12-06 19:39, Julien Aubin wrote:
> > Weird... this time I re-upgraded libc6 and things work fine... looks like
> > something wrong went during the install. And I cannot reproduce the issue
> > anymore... :'( WTF ???
>
> OK, I'm closing the two bugs as unreproducible.
>
>
> Andreas
>

Processed: Re: Bug#883615: Acknowledgement ([CRITICAL] Stretch p-u 9.3 breaks NVidia driver and X.org)

Processing control commands:

> tag -1 unreproducible
Bug #883705 [libc6] libc6: 2.24-11+deb9u2 breaks Nvidia's GLX X module on 
Pascal GPU
Added tag(s) unreproducible.
> close -1
Bug #883705 [libc6] libc6: 2.24-11+deb9u2 breaks Nvidia's GLX X module on 
Pascal GPU
Marked Bug as done

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

Bug#883615: Acknowledgement ([CRITICAL] Stretch p-u 9.3 breaks NVidia driver and X.org)

Control: tag -1 unreproducible
Control: close -1

On 2017-12-06 19:39, Julien Aubin wrote:
> Weird... this time I re-upgraded libc6 and things work fine... looks like
> something wrong went during the install. And I cannot reproduce the issue
> anymore... :'( WTF ???

OK, I'm closing the two bugs as unreproducible.


Andreas

Processed: Re: Bug#883615: Acknowledgement ([CRITICAL] Stretch p-u 9.3 breaks NVidia driver and X.org)

Processing control commands:

> tag -1 unreproducible
Bug #883615 [nvidia-driver] [CRITICAL] Stretch p-u 9.3 breaks NVidia driver and 
X.org
Added tag(s) unreproducible.
> close -1
Bug #883615 [nvidia-driver] [CRITICAL] Stretch p-u 9.3 breaks NVidia driver and 
X.org
Marked Bug as done

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

Bug#883615: Acknowledgement ([CRITICAL] Stretch p-u 9.3 breaks NVidia driver and X.org)

Weird... this time I re-upgraded libc6 and things work fine... looks like
something wrong went during the install. And I cannot reproduce the issue
anymore... :'( WTF ???

2017-12-06 19:24 GMT+01:00 Andreas Beckmann :

> Please install the -dbg/-dbgsym packages for all packages involved in
> the backtrace, this should give a bit more information.
>
> That would probably include xserver-xorg-core-dbgsym (you will have to
> enable the debian-debug package source for that, see
> https://wiki.debian.org/HowToGetABacktrace) and libc6-dbg.
>
>
> Andreas
>

Bug#883615: Acknowledgement ([CRITICAL] Stretch p-u 9.3 breaks NVidia driver and X.org)

Try to build and run this program, it could be a reproducer for your
problem:

#include 
#include 

int main()
{
const char *s = "001 GLX";
char *p;
long int l = strtol(s, , 10);
long long ll = strtoll(s, , 10);
printf("%ld %lld\n", l, ll);
}

Bug#883615: Acknowledgement ([CRITICAL] Stretch p-u 9.3 breaks NVidia driver and X.org)

On 2017-12-06 18:39, Julien Aubin wrote:
> Raised issue #883705 as it is actually a libc6 regression (it may affect
> other apps actually).

I tried to set a title for that bug (it had none), but maybe you can
describe it even better?

Just to verify: if you downgrade libc6 to 2.24-11+deb9u1 everything is
working properly again?

My guess is that it is not related to the nvidia driver at all (except
for utilizing a certain code path in glibc), but to your CPU and the
optimized glibc routines used for it ...

So try touching the file /etc/ld.so.nohwcap - hopefully glibc will stop
using any optimized code for your cpu. If this works (and the glx module
works agian afterwards), we are moving into the right direction.

Andreas

Bug#883615: Acknowledgement ([CRITICAL] Stretch p-u 9.3 breaks NVidia driver and X.org)

Please install the -dbg/-dbgsym packages for all packages involved in
the backtrace, this should give a bit more information.

That would probably include xserver-xorg-core-dbgsym (you will have to
enable the debian-debug package source for that, see
https://wiki.debian.org/HowToGetABacktrace) and libc6-dbg.


Andreas

Bug#883615: Acknowledgement ([CRITICAL] Stretch p-u 9.3 breaks NVidia driver and X.org)

Hi,

2017-12-06 19:18 GMT+01:00 Andreas Beckmann :

> On 2017-12-06 18:39, Julien Aubin wrote:
> > Raised issue #883705 as it is actually a libc6 regression (it may affect
> > other apps actually).
>
> I tried to set a title for that bug (it had none), but maybe you can
> describe it even better?
>

The title I've set is :
 libc6: 2.24-11+deb9u2 breaks Nvidia's GLX X module on Pascal GPU

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

>
> Just to verify: if you downgrade libc6 to 2.24-11+deb9u1 everything is
> working properly again?
>

Yup I confirm that if you downgrade all is working properly again.


>
> My guess is that it is not related to the nvidia driver at all (except
> for utilizing a certain code path in glibc), but to your CPU and the
> optimized glibc routines used for it ...
>
> So try touching the file /etc/ld.so.nohwcap - hopefully glibc will stop
> using any optimized code for your cpu. If this works (and the glx module
> works agian afterwards), we are moving into the right direction.
>

I guess the same, some optimization introduced in the makefile which
triggers a different compilation path.

>
>
> Andreas
>

Bug#883615:

2017-12-06 Thread steve connell

Hi I would like to no why my email is being used and why I'm attached to
this file

Bug#883615: Info received (Order)

2017-12-06 Thread Stewart Pittman

I  have not ordered a thing. I am turnimg.this information over to the
authorities... unless.you can immediately clarify.ASAP

On Dec 6, 2017 12:57 PM, "Debian Bug Tracking System" 
wrote:

> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  Debian NVIDIA Maintainers 
>
> If you wish to submit further information on this problem, please
> send it to 883...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 883615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883615
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Bug#883615: CINDY,your recent order06053711

2017-12-06 Thread Cindy Fisher

What the hell is this, I did not order anything?

On Dec 6, 2017 10:50 AM, "Thank you"  wrote:

Please confirm receipt

































































Okay found the culprit : libc6 Issue appears with the one from 9.3 but not
9.2 2017-12-06 11:56 GMT+01:00 Julien Aubin : > > > Le 6 déc. 2017 11:51,
"Luca Boccassi" a écrit : > > On Wed, 2017-12-06 at 11:37 +0100, Andreas
Beckmann wrote: > > On 2017-12-06 10:53, Julien Aubin wrote: > > > Okay I
will try it. Could you please provide me the build guide and > > > install
> > > guide ? > > > > From README.source: > > > > Building "bleeding edge"
from SVN for users > > > > As new upstream versions of the proprietary
driver are released, > > upload > > might not happen immediately. This
might be for various reasons, > > including > > waiting for new binary
packages to clear the NEW queue. > > Users wishing to try to build new
version locally can follow the > > instructions on the Debian wiki: > > > >
https://wiki.debian.org/NvidiaGraphicsDrivers#Building_newer_rele > >
ases_from_SVN > > > > WARNING: these will most likely be work in progress,
and the > > final upload > > may be different and may not support clean
upgrades from/to the > > versions > > uploaded in the archive. > > > > > >
In your case, it is branches/384-stretch-backports. > > > > Please let us
know about any issues you encounter with these > > instructions. > > > > >
> Andreas > > 375.82 has been in sid/buster for months now, it's very
strange that it > wasn't reported before - a GLX crash is not a subtle
problem that might > get overlooked > > > Yup but not sure people use a
Pascal GPU. What is granted is that the > issue appeared after last update
to stretch-proposed-updates, but only on > my box with a Pascal GPU. > > I
suspect the code paths used are not the same per GPU... > > If you wish I
can send you my sources.list, my /etc and the list of > installed packages.
I do not have weird things, only additional repos for > marginal packages
like deb-multimedia or virtualbox. > > > -- > Kind regards, > Luca Boccassi
> > >

Bug#882934: [Pkg-electronics-devel] Bug#882934: Segfault on window operations

2017-12-06 Thread Joe

On Wed, 6 Dec 2017 12:54:53 +0100
أحمد المحمودي  wrote:

> Please try using pcb-gtk using a new user. I suspect that this might
> be related to some setting or maybe GTK theme.
> 

I created a new user. PCB closes immediately after the window opens.
With my usual user, it does not close immediately, but only after a
redraw in the working area. I am assuming that for the new user, there
is some kind of welcome display which causes redraw and triggers the
segfault, but it is too fast to see. This is Debian unstable, with a
completely default user and Xfce. I do not think I have ever changed
the default theming on my normal user.

I tried running in gdb, but I'm not really familiar with debugging, and
I wasn't able to get anywhere. I loaded as many symbol files as I could
find in the dependencies of pcb-gtk, there are five threads running at
the time of failure, and the other threads have backtraces with
filenames. The thread which is failing has a backtrace with no
filenames.

Running under gdb, I can see that the window decorations redraw
correctly, it is a redraw in the working area which does not work, and
which triggers the segfault. I can resize the window smaller OK, but
not larger. I can move another window over the sidebar, status bar and
menu area, everywhere except the working area.

Best regards,
Joe

Bug#883615:

2017-12-06 Thread Kandace Berry

What is this for

Bug#883615: Order

2017-12-06 Thread Stewart Pittman

Who is this?  What Order? I need to hear from you asap!

Processed: found 883705 in 2.24-11+deb9u2 ...

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

> found 883705 2.24-11+deb9u2
Bug #883705 [libc6] (no subject)
Marked as found in versions glibc/2.24-11+deb9u2.
> retitle 883705 libc6: 2.24-11+deb9u2 breaks Nvidia's GLX X module on Pascal 
> GPU
Bug #883705 [libc6] (no subject)
Set Bug title to 'libc6: 2.24-11+deb9u2 breaks Nvidia's GLX X module on Pascal 
GPU'.
> thanks
Stopping processing here.

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

Bug#883705: Acknowledgement ()

Additional point : if you revert to libc6 from previous version all goes
back fine :

sudo apt install libc6=2.24-11+deb9u1 libc6-dbg=2.24-11+deb9u1
libc6-dev=2.24-11+deb9u1 libc6-i386=2.24-11+deb9u1 libc6-i686
=2.24-11+deb9u1 libc-dev-bin=2.24-11+deb9u1 libc6:i386=2.24-11+deb9u1


2017-12-06 18:33 GMT+01:00 Debian Bug Tracking System :

> Thank you for filing a new Bug report with Debian.
>
> You can follow progress on this Bug here: 883705:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883705.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  GNU Libc Maintainers 
>
> If you wish to submit further information on this problem, please
> send it to 883...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 883705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883705
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Bug#869994: perl5.26 update: postgresql databases cannot be viewed using browser

2017-12-06 Thread Robert J. Clay

Neil,

As a reminder;  the title of the bug you opened was changed to the
following to better reflect the issue with the sql-ledger package:

sql-ledger: Can't locate bin/mozilla/login.pl in @INC

On Sun, Jul 30, 2017 at 4:09 AM, Neil Redgate  wrote:
> 
> I have contacted the developer of sql-ledger and he has given me a couple of
> suggestions - which I hope to look into later today.

   And did any of those suggestions help?

   Since there is going to be the same issue with any of the more
recent versions of Perl, I've been wondering if he was going to
release a new version that fixed the issue...

> If I have success, I will certainly post my findings.

   Should it be assumed, then, that you did not have any success?
I've not seen any follow up messages from you about it...

-- 
Robert J. Clay
rjc...@gmail.com

Bug#853599: Bug#853599: opensurgsim: ftbfs with GCC-7

On Wed, Dec 06, 2017 at 12:20:37PM -0500, Paul Novotny wrote:
> 
> Sorry again for not looking at this. These tests appear to be from the
> Unit Tests that test Eigen and not really opensurgsim. I think they can
> all be safely disabled, since we can trust that Eigen works. These
> failures are mostly floating point errors. So yes Fabian, please go
> ahead and disable them. If you want to just disable them all, I think if
> you set BUILD_TESTING_EIGEN to OFF on line 29 in Debian/rules, you
> should solve this and other future issues.

I see no point in disabling more tests than needed - so disabling
just the failing test should be sufficient.

Kind regards

  ANdreas.


-- 
http://fam-tille.de

Bug#883615: Acknowledgement ([CRITICAL] Stretch p-u 9.3 breaks NVidia driver and X.org)

Raised issue #883705 as it is actually a libc6 regression (it may affect
other apps actually).

I think you can close this one if you wish.

2017-12-06 18:11 GMT+01:00 Julien Aubin :

> Okay found the culprit : libc6
>
> Issue appears with the one from 9.3 but not 9.2
>
> 2017-12-06 11:56 GMT+01:00 Julien Aubin :
>
>>
>>
>> Le 6 déc. 2017 11:51, "Luca Boccassi"  a écrit :
>>
>> On Wed, 2017-12-06 at 11:37 +0100, Andreas Beckmann wrote:
>> > On 2017-12-06 10:53, Julien Aubin wrote:
>> > > Okay I will try it. Could you please provide me the build guide and
>> > > install
>> > > guide ?
>> >
>> > From README.source:
>> >
>> > Building "bleeding edge" from SVN for users
>> >
>> > As new upstream versions of the proprietary driver are released,
>> > upload
>> > might not happen immediately. This might be for various reasons,
>> > including
>> > waiting for new binary packages to clear the NEW queue.
>> > Users wishing to try to build new version locally can follow the
>> > instructions on the Debian wiki:
>> >
>> > https://wiki.debian.org/NvidiaGraphicsDrivers#Building_newer_rele
>> > ases_from_SVN
>> >
>> > WARNING: these will most likely be work in progress, and the
>> > final upload
>> > may be different and may not support clean upgrades from/to the
>> > versions
>> > uploaded in the archive.
>> >
>> >
>> > In your case, it is branches/384-stretch-backports.
>> >
>> > Please let us know about any issues you encounter with these
>> > instructions.
>> >
>> >
>> > Andreas
>>
>> 375.82 has been in sid/buster for months now, it's very strange that it
>> wasn't reported before - a GLX crash is not a subtle problem that might
>> get overlooked
>>
>>
>> Yup but not sure people use a Pascal GPU. What is granted is that the
>> issue appeared after last update to stretch-proposed-updates, but only on
>> my box with a Pascal GPU.
>>
>> I suspect the code paths used are not the same per GPU...
>>
>> If you wish I can send you my sources.list, my /etc and the list of
>> installed packages. I do not have weird things, only additional repos for
>> marginal packages like deb-multimedia or virtualbox.
>>
>>
>> --
>> Kind regards,
>> Luca Boccassi
>>
>>
>>
>

Processed: Patch to remove the webkit and plasma parts from kde-runtime

Processing control commands:

> tags -1 patch
Bug #784477 [src:kde-runtime] [kde-runtime] Qt4's WebKit removal
Added tag(s) patch.

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

Bug#784477: Patch to remove the webkit and plasma parts from kde-runtime

Control: tags -1 patch

The attached patch removes the webkit and plasma parts from kde-runtime.

cu
Adrian

-- 

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

diff -Nru kde-runtime-16.08.3/debian/control kde-runtime-16.08.3/debian/control
--- kde-runtime-16.08.3/debian/control  2017-03-21 12:25:21.0 +0200
+++ kde-runtime-16.08.3/debian/control  2017-12-02 21:21:48.0 +0200
@@ -31,7 +31,6 @@
libphonon-dev (>= 4:4.6.0really4.4.3),
libpulse-dev (>= 0.9.16),
libqca2-dev (>= 2.0.0),
-   libqtwebkit-dev,
libsmbclient-dev [!hurd-any],
libsoprano-dev,
libssh-gcrypt-dev (>= 0.4.0),
@@ -52,7 +51,6 @@
 Depends: kde-runtime-data (>= ${source:Version}),
  kdelibs5-plugins,
  oxygen-icon-theme,
- plasma-scriptengine-javascript (= ${binary:Version}),
  ${misc:Depends},
  ${shlibs:Depends}
 Recommends: icoutils,
@@ -131,12 +129,12 @@
  .
  This package is part of the KDE base runtime module.
 
-Package: plasma-scriptengine-javascript
-Architecture: any
-Depends: ${misc:Depends}, ${shlibs:Depends}
-Description: JavaScript script engine for Plasma
- This package provides the JavaScript script engine for Plasma. You have to
- install it if you want to use Plasma widgets and data engines written in
- JavaScript.
- .
- This package is part of the KDE base runtime module.
+#Package: plasma-scriptengine-javascript
+#Architecture: any
+#Depends: ${misc:Depends}, ${shlibs:Depends}
+#Description: JavaScript script engine for Plasma
+# This package provides the JavaScript script engine for Plasma. You have to
+# install it if you want to use Plasma widgets and data engines written in
+# JavaScript.
+# .
+# This package is part of the KDE base runtime module.
diff -Nru kde-runtime-16.08.3/debian/kde-runtime-data.install 
kde-runtime-16.08.3/debian/kde-runtime-data.install
--- kde-runtime-16.08.3/debian/kde-runtime-data.install 2017-03-21 
12:25:21.0 +0200
+++ kde-runtime-16.08.3/debian/kde-runtime-data.install 2017-12-04 
10:04:57.0 +0200
@@ -1,126 +1,126 @@
-etc/dbus-1/system.d/org.kde.kcontrol.kcmremotewidgets.conf
+#etc/dbus-1/system.d/org.kde.kcontrol.kcmremotewidgets.conf
 etc/xdg/menus/kde-information.menu
-usr/lib/kde4/imports/org/kde/dirmodel/qmldir
-usr/lib/kde4/imports/org/kde/draganddrop/qmldir
-usr/lib/kde4/imports/org/kde/locale/qmldir
-usr/lib/kde4/imports/org/kde/plasma/components/BusyIndicator.qml
-usr/lib/kde4/imports/org/kde/plasma/components/Button.qml
-usr/lib/kde4/imports/org/kde/plasma/components/ButtonColumn.qml
-usr/lib/kde4/imports/org/kde/plasma/components/ButtonGroup.js
-usr/lib/kde4/imports/org/kde/plasma/components/ButtonRow.qml
-usr/lib/kde4/imports/org/kde/plasma/components/CheckBox.qml
-usr/lib/kde4/imports/org/kde/plasma/components/CommonDialog.qml
-usr/lib/kde4/imports/org/kde/plasma/components/ContextMenu.qml
-usr/lib/kde4/imports/org/kde/plasma/components/Dialog.qml
-usr/lib/kde4/imports/org/kde/plasma/components/Highlight.qml
-usr/lib/kde4/imports/org/kde/plasma/components/Label.qml
-usr/lib/kde4/imports/org/kde/plasma/components/ListItem.qml
-usr/lib/kde4/imports/org/kde/plasma/components/Page.qml
-usr/lib/kde4/imports/org/kde/plasma/components/PageStack.qml
-usr/lib/kde4/imports/org/kde/plasma/components/ProgressBar.qml
-usr/lib/kde4/imports/org/kde/plasma/components/QueryDialog.qml
-usr/lib/kde4/imports/org/kde/plasma/components/RadioButton.qml
-usr/lib/kde4/imports/org/kde/plasma/components/ScrollBar.qml
-usr/lib/kde4/imports/org/kde/plasma/components/SectionScroller.qml
-usr/lib/kde4/imports/org/kde/plasma/components/SelectionDialog.qml
-usr/lib/kde4/imports/org/kde/plasma/components/Sheet.qml
-usr/lib/kde4/imports/org/kde/plasma/components/Slider.qml
-usr/lib/kde4/imports/org/kde/plasma/components/Switch.qml
-usr/lib/kde4/imports/org/kde/plasma/components/TabBar.qml
-usr/lib/kde4/imports/org/kde/plasma/components/TabButton.qml
-usr/lib/kde4/imports/org/kde/plasma/components/TabGroup.qml
-usr/lib/kde4/imports/org/kde/plasma/components/TextArea.qml
-usr/lib/kde4/imports/org/kde/plasma/components/TextField.qml
-usr/lib/kde4/imports/org/kde/plasma/components/ToolBar.qml
-usr/lib/kde4/imports/org/kde/plasma/components/ToolBarLayout.qml
-usr/lib/kde4/imports/org/kde/plasma/components/ToolButton.qml
-usr/lib/kde4/imports/org/kde/plasma/components/private/AppManager.js
-usr/lib/kde4/imports/org/kde/plasma/components/private/ButtonShadow.qml
-usr/lib/kde4/imports/org/kde/plasma/components/private/Config.js
-usr/lib/kde4/imports/org/kde/plasma/components/private/DualStateButton.qml
-usr/lib/kde4/imports/org/kde/plasma/components/private/InlineDialog.qml
-usr/lib/kde4/imports/org/kde/plasma/components/private/PageStack.js

Bug#883632: marked as done (maxima: Maintainer unreachable)

Your message dated Wed, 06 Dec 2017 12:26:49 -0500
with message-id <87d13rix7q@maguirefamily.org>
and subject line Re: Bug#883632: maxima: Maintainer unreachable
has caused the Debian Bug report #883632,
regarding maxima: Maintainer unreachable
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.)

-- 
883632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883632
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: maxima
Version: 5.40.0-3
Severity: serious
Justification: Policy v4.1.2.0 §3.3

The only Maintainer of the maxima source package is not reachable.
There are no Uploaders, either.

Proof follows:

From mailer-dae...@mailly.debian.org Tue Dec  5 23:26:54 2017
From: Mail Delivery System 
Message-ID: 
To: t...@mirbsd.de
Date: Tue, 05 Dec 2017 23:15:54 +
Subject: Mail delivery failed: returning message to sender

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  c...@maguirefamily.org
retry timeout exceeded

[ Part 2: "Delivery Status" ]

Reporting-MTA: dns; mailly.debian.org

Action: failed
Final-Recipient: rfc822;c...@maguirefamily.org
Status: 5.0.0

[ Part 3: "Included Message" ]

From: Thorsten Glaser 
Message-ID: 
To: c...@debian.org
Date: Tue, 5 Dec 2017 23:12:35 + (UTC)
Subject: Re: Log for attempted build of maxima_5.40.0-3 on m68k (dist=unstable)

fail

2 tests failed out of 11,185 total tests.

cf. 
https://buildd.debian.org/status/fetch.php?pkg=maxima=m68k=5.40.0-3=1512458062=0
--- End Message ---
--- Begin Message ---
Greetings, and thanks for your report!  I've received this at the
address in question.

I'd love to fix the 68k maxima test failures as has been done in the
past.  Use to have wario.physik.fu-berlin.de, but no more.  Small
numerical rounding errors like this have surfaced on this platform
before.  At one time it was partially due to a bug in the gmp library
specific to this platform.  It seems the most prudent thing to do at
this point is to put in an exception to the test suite regression if the
values you report below are indeed reproducible.  Can you confirm this?

Take care,

Thorsten Glaser  writes:

> Source: maxima
> Version: 5.40.0-3
> Severity: serious
> Justification: Policy v4.1.2.0 §3.3
>
> The only Maintainer of the maxima source package is not reachable.
> There are no Uploaders, either.
>
> Proof follows:
>
>
> From mailer-dae...@mailly.debian.org Tue Dec  5 23:26:54 2017
> From: Mail Delivery System 
> Message-ID: 
> To: t...@mirbsd.de
> Date: Tue, 05 Dec 2017 23:15:54 +
> Subject: Mail delivery failed: returning message to sender
>
> This message was created automatically by mail delivery software.
>
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es) failed:
>
>   c...@maguirefamily.org
> retry timeout exceeded
>
> [ Part 2: "Delivery Status" ]
>
> Reporting-MTA: dns; mailly.debian.org
>
> Action: failed
> Final-Recipient: rfc822;c...@maguirefamily.org
> Status: 5.0.0
>
>
> [ Part 3: "Included Message" ]
>
> From: Thorsten Glaser 
> Message-ID: 
> To: c...@debian.org
> Date: Tue, 5 Dec 2017 23:12:35 + (UTC)
> Subject: Re: Log for attempted build of maxima_5.40.0-3 on m68k 
> (dist=unstable)
>
> fail
>
> 2 tests failed out of 11,185 total tests.
>
> cf. 
> https://buildd.debian.org/status/fetch.php?pkg=maxima=m68k=5.40.0-3=1512458062=0
>
>
>
>

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

Bug#883706: dolphin4 is still linked with libplasma3

Package: dolphin4
Version: 4:16.08.3-1
Severity: serious
Tags: patch buster sid

dolphin4 is still linked with libplasma3,
which has to be removed for the qtwebkit removal.

Fix attached.
Description: Even with -DBUILD_plasma=false dolphin4 was still linked with 
libplasma
Author: Adrian Bunk 

--- kde-baseapps-16.08.3.orig/dolphin/src/CMakeLists.txt
+++ kde-baseapps-16.08.3/dolphin/src/CMakeLists.txt
@@ -135,7 +135,7 @@ if(X11_Xrender_FOUND)
 target_link_libraries(dolphinprivate4 ${X11_Xrender_LIB})
 endif(X11_Xrender_FOUND)
 
-target_link_libraries(dolphinprivate4 ${KDE4_PLASMA_LIBS})
+#target_link_libraries(dolphinprivate4 ${KDE4_PLASMA_LIBS})
 
 set_target_properties(dolphinprivate4 PROPERTIES VERSION 
${GENERIC_LIB_VERSION} SOVERSION ${GENERIC_LIB_SOVERSION} )
 install(TARGETS dolphinprivate4  ${INSTALL_TARGETS_DEFAULT_ARGS})
--- kde-baseapps-16.08.3.orig/dolphin/src/views/tooltips/filemetadatatooltip.cpp
+++ kde-baseapps-16.08.3/dolphin/src/views/tooltips/filemetadatatooltip.cpp
@@ -41,7 +41,7 @@
 #endif
 
 // For the blurred tooltip background
-#include 
+//#include 
 
 FileMetaDataToolTip::FileMetaDataToolTip(QWidget* parent) :
 QWidget(parent),
@@ -174,8 +174,8 @@ void FileMetaDataToolTip::paintEvent(QPa
 
 void FileMetaDataToolTip::showEvent(QShowEvent *)
 {
-Plasma::WindowEffects::overrideShadow(winId(), true);
-Plasma::WindowEffects::enableBlurBehind(winId(), true, mask());
+//Plasma::WindowEffects::overrideShadow(winId(), true);
+//Plasma::WindowEffects::enableBlurBehind(winId(), true, mask());
 }
 
 #include "filemetadatatooltip.moc"

Bug#883705:

Package: libc6
Severity: critical
Justification: breaks the whole system

Hi,

I found out a regression brought by Debian 9.3 with NVidia binary drivers on
some GPUs including mine. The regression simply breaks NVidia GLX library
with
a segfault in function strtol_l_internal (file strtolol_l.c) although it
seems
this file has not been updated directly.

Note that it does not affect all GPUs but at least mine, NVidia Pascal GPU.
NVidia Maxwell GPUs seem unaffected.

I discovered it while starting my X server using a debugger, and here's the
stack :
#0  0x7588ad01 in __GI_strtol_l_internal (nptr=0x7fffe2b1
"001 GLX", endptr=0x7fffe2a8, base=10, group=,
loc=0x55ad3620) at ../stdlib/strtol_l.c:293
#1  0x555cd0cb in ?? ()
#2  0x555bbeb0 in AddExtension ()
#3  0x7381d7b2 in ?? () from /usr/lib/xorg/modules/linux/libglx.so
#4  0x555bc040 in ?? ()
#5  0x001d in ?? ()
#6  0x0200 in ?? ()
#7  0x in ?? ()

My computer :
Debian 9.3 amd64
Intel Core i7 4790
32 GB RAM
NVidia GeForce GTX 1070 (at least the generation seems to matter) w/ NVidia
blob 375.82

Note that as of now I use NVidia blob from bpo but the issue also happens w/
the driver from stable.

A workaround to this bug consists in either disabling the GLX module in
xorg.conf using :
Section "Module"
   Disable "glx"
EndSection

I also tried using Option "AllowGLXWithComposite" "False" (w/o explicit glx
module disablement) but it does only work as long as you do not disable
compositing in the same time. And basically with this setting anything that
uses GLX crashes in that case.



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

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

Bug#853599: [Debian-med-packaging] Bug#853599: opensurgsim: ftbfs with GCC-7

2017-12-06 Thread Paul Novotny

On Wed, Dec 6, 2017, at 11:28 AM, Andreas Tille wrote:
> On Wed, Dec 06, 2017 at 04:51:17PM +0100, Fabian Klötzl wrote:
> > // TODO(bert): There is some Eigen flag that causes matrices and
> > vectors> > to be
> > //   initialized after all!  We should check for that here.
> >
> > So I am guessing that the authors knew that their test was flaky and> > 
> > thus we should be save deactivating them. If you agree, I will go
> > ahead.>
> Sounds sensible - so I agree. :-)
>
> An information to upstream that we skip the test and by doing so
> informing them that it really causes problems in a practical
> application> would complete the work on the bug.
>
> Kind regards
>
>  Andreas.
>
> --
> http://fam-tille.de
>

Sorry again for not looking at this. These tests appear to be from the
Unit Tests that test Eigen and not really opensurgsim. I think they can
all be safely disabled, since we can trust that Eigen works. These
failures are mostly floating point errors. So yes Fabian, please go
ahead and disable them. If you want to just disable them all, I think if
you set BUILD_TESTING_EIGEN to OFF on line 29 in Debian/rules, you
should solve this and other future issues.

Bug#880776: marked as done (mrtg build depends on removed libgd2*-dev provides)

Your message dated Wed, 06 Dec 2017 17:20:39 +
with message-id 
and subject line Bug#880776: fixed in mrtg 2.17.4-4.1
has caused the Debian Bug report #880776,
regarding mrtg build depends on removed libgd2*-dev provides
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.)


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

The following packages have unmet dependencies:
 builddeps:mrtg : Depends: libgd2-noxpm-dev but it is not installable


Please change the build dependency to libgd-dev.
--- End Message ---
--- Begin Message ---
Source: mrtg
Source-Version: 2.17.4-4.1

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

Debian distribution maintenance software
pp.
Roland Rosenfeld  (supplier of updated mrtg 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, 05 Dec 2017 17:41:10 +0100
Source: mrtg
Binary: mrtg mrtg-contrib
Architecture: source all amd64
Version: 2.17.4-4.1
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Roland Rosenfeld 
Description:
 mrtg   - multi router traffic grapher
 mrtg-contrib - multi router traffic grapher (contributed files)
Closes: 880776
Changes:
 mrtg (2.17.4-4.1) unstable; urgency=medium
 .
   * NMU to remove Net_SNMP_util module (which is now to be found in
 libsnmp-session-perl).
   * Build-Depend on libgd-dev instead of libgd-dev (Closes: #880776).
Checksums-Sha1:
 2754f91889512d549398b309343b821f2772b007 1968 mrtg_2.17.4-4.1.dsc
 6cdee6f3d80f603b77b46714d7d3ac8352777369 31096 mrtg_2.17.4-4.1.debian.tar.xz
 b30aa9eb1bd1276f35e92af224d63336f6822e33 428792 mrtg-contrib_2.17.4-4.1_all.deb
 d62d10776e25c7170a075733dd512091e7a767ff 29408 mrtg-dbgsym_2.17.4-4.1_amd64.deb
 23a1dd24949a996684f1cd7395ed3f252876d4a2 7652 mrtg_2.17.4-4.1_amd64.buildinfo
 c8bf31553d22cd65f3892288391b815c9f062d7c 367124 mrtg_2.17.4-4.1_amd64.deb
Checksums-Sha256:
 a55fe59267f04263839aa59af1eb5e5cf63fc18a16365b3cdbe2076947574836 1968 
mrtg_2.17.4-4.1.dsc
 94d29592e455cd097fdb49c92faf40c844a0e3629ab028869ddab66bb10de4c9 31096 
mrtg_2.17.4-4.1.debian.tar.xz
 6d4ed18ca14a3c54199a1e39bbf3ffd6e049375541d1fb26d7e384dcaf3f8f79 428792 
mrtg-contrib_2.17.4-4.1_all.deb
 7e484652ea6c3f803df4ffbee32db7843a9c274b000cac2e81c53e49de74cbf2 29408 
mrtg-dbgsym_2.17.4-4.1_amd64.deb
 4219dc23d83b697829f6704e6d778bd5ac4b31a47abde6bc2c6de38540b4ac91 7652 
mrtg_2.17.4-4.1_amd64.buildinfo
 41dba2708fb90f5225270617ae7c9c1a71c69df6a33adb69d858faf8db3694c0 367124 
mrtg_2.17.4-4.1_amd64.deb
Files:
 6c519c9c811e1825b715174d1b9ba6b1 1968 net extra mrtg_2.17.4-4.1.dsc
 b2063db4b2fb77f2acb5fd6a8b6ba164 31096 net extra mrtg_2.17.4-4.1.debian.tar.xz
 4fa89a516e6138efffcf8cebbb70362e 428792 net extra 
mrtg-contrib_2.17.4-4.1_all.deb
 08db4f21bc017d24bf98446772914bcf 29408 debug optional 
mrtg-dbgsym_2.17.4-4.1_amd64.deb
 e00853a327680553c32cce675e6d9f1c 7652 net extra mrtg_2.17.4-4.1_amd64.buildinfo
 2de5911f086237bea1f1c3ec1072a208 367124 net extra mrtg_2.17.4-4.1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErC+9sQSUPYpEoCEdAnE7z8pUELIFAlooH3gACgkQAnE7z8pU
ELLvHA//Suhba6jJQyGyj9mtCFzeI+fFhzjSx/uiHqN2eH6b0sZpwwjPbIahMOdZ
V1IHQ7IysMsdguIC126+DhhheAg4CNf0fL0YgDZwmh7hSocEJhLC2NggPN+61bWd
KoAcLzj8VoJNIlck9drCSqHvUOIpRYtYpRRJp2qe0lW02z6Txv7QEaqv0RuZrTuU
mHjfc8OlXGxxb9bRCcdCN8h35UFEqS1imUzyVynA5dFtKY2tKGLyiwbcvB7dA5+h
7WYkuEHHSKtl0S5mqj4noZ6P+6rVfuVUzztsax5NNHYnT5lj+MFxaiF0X8XtPLsI
NKz+FiuAnRL4uFOVgTEJ30+GdJrOIh7dQPM7v6mgIR7KWKDDzcNEQ59+mRMwRsmd
n56Wikbci7xczNazcBF/K7O8nmljKTmHwPm2xOSnmCcAAvHc4Z95No7QSjXZ9ZKn
s7AYAHmX+vm2mLh0hopSjD5SUpru/07ZppL50dVAodWOwU8I8fblKc652fDiU5T+
RsrW+O6QbvMTnHd9Iun3RJd73JI+2/LBuJ5Q8N/GgqhVRiYYupb9Pdf1DUVnIaI4
Rjrqcb7znp2OcT92NpJOG/aT0Tl4zZY3Fp7WIVfSvqTDzB+heNgSwvaLlPgHrtjH
EHSJFSp/1jtRAM2pdRt/AS0Dfm7hHNtvrs15azKblmuaj3reTVY=
=a87d
-END PGP

Bug#883615: Acknowledgement ([CRITICAL] Stretch p-u 9.3 breaks NVidia driver and X.org)

Okay found the culprit : libc6

Issue appears with the one from 9.3 but not 9.2

2017-12-06 11:56 GMT+01:00 Julien Aubin :

>
>
> Le 6 déc. 2017 11:51, "Luca Boccassi"  a écrit :
>
> On Wed, 2017-12-06 at 11:37 +0100, Andreas Beckmann wrote:
> > On 2017-12-06 10:53, Julien Aubin wrote:
> > > Okay I will try it. Could you please provide me the build guide and
> > > install
> > > guide ?
> >
> > From README.source:
> >
> > Building "bleeding edge" from SVN for users
> >
> > As new upstream versions of the proprietary driver are released,
> > upload
> > might not happen immediately. This might be for various reasons,
> > including
> > waiting for new binary packages to clear the NEW queue.
> > Users wishing to try to build new version locally can follow the
> > instructions on the Debian wiki:
> >
> > https://wiki.debian.org/NvidiaGraphicsDrivers#Building_newer_rele
> > ases_from_SVN
> >
> > WARNING: these will most likely be work in progress, and the
> > final upload
> > may be different and may not support clean upgrades from/to the
> > versions
> > uploaded in the archive.
> >
> >
> > In your case, it is branches/384-stretch-backports.
> >
> > Please let us know about any issues you encounter with these
> > instructions.
> >
> >
> > Andreas
>
> 375.82 has been in sid/buster for months now, it's very strange that it
> wasn't reported before - a GLX crash is not a subtle problem that might
> get overlooked
>
>
> Yup but not sure people use a Pascal GPU. What is granted is that the
> issue appeared after last update to stretch-proposed-updates, but only on
> my box with a Pascal GPU.
>
> I suspect the code paths used are not the same per GPU...
>
> If you wish I can send you my sources.list, my /etc and the list of
> installed packages. I do not have weird things, only additional repos for
> marginal packages like deb-multimedia or virtualbox.
>
>
> --
> Kind regards,
> Luca Boccassi
>
>
>

Bug#882169: marked as done (seqan2: FTBFS on indep-only build)

Your message dated Wed, 06 Dec 2017 17:07:09 +
with message-id 
and subject line Bug#882169: fixed in seqan2 
2.3.2.000platform-issues7-41f58c3+dfsg-2
has caused the Debian Bug report #882169,
regarding seqan2: FTBFS on indep-only build
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.)


-- 
882169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882169
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: seqan2
Version: 2.3.2.000platform-issues6-9cf5a69+dfsg-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

seqan2 FTBFS during the indep-only build of the arch:all packages:

https://buildd.debian.org/status/fetch.php?pkg=seqan2=all=2.3.2.000platform-issues6-9cf5a69%2Bdfsg-3=1511019385=0

   debian/rules override_dh_installman
make[1]: Entering directory 
'/<>/seqan2-2.3.2.000platform-issues6-9cf5a69+dfsg'
$DEB_BUILD_OPTIONS is [parallel=4]
dh_link
find -L 
/<>/seqan2-2.3.2.000platform-issues6-9cf5a69+dfsg/debian/seqan-apps/usr/bin
 -name . -o -type d -prune -o -type l -exec rm {} +
find: 
'/<>/seqan2-2.3.2.000platform-issues6-9cf5a69+dfsg/debian/seqan-apps/usr/bin':
 No such file or directory
debian/rules:107: recipe for target 'override_dh_installman' failed
make[1]: *** [override_dh_installman] Error 1


You probably want a override_dh_xxx-arch target there, but looking at the
rules file I don't get what you are doing there. Why is dh_link called
in override_dh_installman? And are the two find calls in in
override_dh_link-arch and override_dh_installman not doing the same?
And could be simplified to 

# delete broken symlinks - some apps are not built on all architectures
find -L $(CURDIR)/debian/$(pkgapps)/usr/bin -type l -delete

Then there is this comment:
# we generate only those manpages where binaries are linked to /usr/bin
Which somehow implies: the list of manpages included some arch:all doc
package depends on the architecture where the package was built ???
Shouldn't that rather be a superset?


Andreas

PS: using the full hash would only marginally increase the length of the 
version number ;-)
--- End Message ---
--- Begin Message ---
Source: seqan2
Source-Version: 2.3.2.000platform-issues7-41f58c3+dfsg-2

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

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated seqan2 
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: Wed, 06 Dec 2017 05:28:59 -0800
Source: seqan2
Binary: seqan-apps libseqan2-dev
Architecture: source
Version: 2.3.2.000platform-issues7-41f58c3+dfsg-2
Distribution: experimental
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Michael R. Crusoe 
Description:
 libseqan2-dev - C++ library for the analysis of biological sequences 
(development
 seqan-apps - C++ library for the analysis of biological sequences
Closes: 882169
Changes:
 seqan2 (2.3.2.000platform-issues7-41f58c3+dfsg-2) experimental; urgency=medium
 .
   [ Andreas Tille ]
   * Work around missing dir in indep-only builds
 Closes: #882169
 .
   [ Michael R. Crusoe ]
   * Cleanup from not pushing my changes
Checksums-Sha1:
 c45364ad69f46a31531690870878d5f4f03caaf6 2379 
seqan2_2.3.2.000platform-issues7-41f58c3+dfsg-2.dsc
 9ebc3480e1b9382d9c99bc651269560eb21581da 12368 
seqan2_2.3.2.000platform-issues7-41f58c3+dfsg-2.debian.tar.xz
 3803a58c2fa625312198ccf0662d7e420658c236 6439 
seqan2_2.3.2.000platform-issues7-41f58c3+dfsg-2_source.buildinfo
Checksums-Sha256:
 972664d3495424e8db38d6a8ded80178e9bae4a7796479b29fd0d3bad00a0f00 2379 
seqan2_2.3.2.000platform-issues7-41f58c3+dfsg-2.dsc
 01c85c37fbf62a09d4b9a44f0af6ddb1c141ad841e2442c60750923d5f3fe067 12368 
seqan2_2.3.2.000platform-issues7-41f58c3+dfsg-2.debian.tar.xz
 dc96653dec2f2534040549e0914a1d4fe2c740e4a42dcb79226551374a315895 6439

Bug#880347: bug squashing target: Probably bowtie 1.2.1.1 issue (Was: Bug#880347: bioperl-run: FTBFS: Test failures)

Hi,

this bug report has a time correlation to the upload of the new version of
bowtie (1.2.1.1):

On Mon, Oct 30, 2017 at 09:08:15PM +0100, Lucas Nussbaum wrote:
> Source: bioperl-run
> Version: 1.7.2-1
> Severity: serious
> ...
> 
> Relevant part (hopefully):
> > ok 9 # skip Required executable for Bio::Tools::Run::tRNAscanSE is not 
> > present
> > ok 10 # skip Required executable for Bio::Tools::Run::tRNAscanSE is not 
> > present
> > ok 11 # skip Required executable for Bio::Tools::Run::tRNAscanSE is not 
> > present
> > ok 12 # skip Required executable for Bio::Tools::Run::tRNAscanSE is not 
> > present
> > ok
> > 
> > Test Summary Report
> > ---
> > t/Bowtie.t  (Wstat: 512 Tests: 61 Failed: 2)
> >   Failed tests:  43, 45
> >   Non-zero exit status: 2
> > Files=72, Tests=1690, 156 wallclock secs ( 0.24 usr  0.07 sys + 133.72 cusr 
> >  6.41 csys = 140.44 CPU)
> > Result: FAIL
> > Failed 1/72 test programs. 2/1690 subtests failed.
> > dh_auto_test: perl Build test --verbose 1 returned exit code 255
> > debian/rules:32: recipe for target 'override_dh_auto_test' failed

Earlier in the log:


...
#   Failed test 'bowtie success'
#   at t/Bowtie.t line 188.
#   '# reads processed: 2000
# # reads with at least one reported alignment: 2000 (100.00%)
# # reads that failed to align: 0 (0.00%)
# Reported 1000 paired-end alignments to 1 output stream(s)
# '
# doesn't match '(?^:reads processed: 1000)'

#   Failed test 'bowtie success'
#   at t/Bowtie.t line 195.
#   '# reads processed: 2000
# # reads with at least one reported alignment: 2000 (100.00%)
# # reads that failed to align: 0 (0.00%)
# Reported 1000 paired-end alignments to 1 output stream(s)
# '
# doesn't match '(?^:reads processed: 1000)'
# Looks like you failed 2 tests of 61.
t/Bowtie.t .
...


I suspect that some change between bowtie 1.2.0 and bowtie 1.2.1.1 is
responsible for the issue in bioperl-run.  I wonder whether tracking
down this issue sounds interesting for somebody who knows (and uses)
bowtie a bit.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#883698: freetype: incorrect shlibs file generation

2017-12-06 Thread Cyril Brulebois

Source: freetype
Version: 2.8.1-0.1
Severity: serious

(Please keep debian-b...@lists.debian.org in copy of your replies.)

Hi,

While preparing the release announcement for Buster Alpha 2, I've
stumbled upon the symbols addition in your last upload. Checking the
dependency for the udeb, it seems to be stuck at 2.6, while it should be
at the maximum version (udebs don't use symbols files):
| libfreetype 6 libfreetype6 (>= 2.6)
| udeb: libfreetype 6 libfreetype6-udeb (>= 2.6)

This is due to:
| dependency = $(libpkg) (>= 2.6)
| […]
| override_dh_makeshlibs:
| dh_makeshlibs -V '$(dependency)' --add-udeb '$(udebpkg)'


KiBi.

Bug#853599: [Debian-med-packaging] Bug#853599: opensurgsim: ftbfs with GCC-7

On Wed, Dec 06, 2017 at 04:51:17PM +0100, Fabian Klötzl wrote:
> // TODO(bert): There is some Eigen flag that causes matrices and vectors
> to be
> //   initialized after all!  We should check for that here.
> 
> So I am guessing that the authors knew that their test was flaky and
> thus we should be save deactivating them. If you agree, I will go ahead.

Sounds sensible - so I agree. :-)

An information to upstream that we skip the test and by doing so
informing them that it really causes problems in a practical application
would complete the work on the bug.

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#882437: cwltool FTBFS with ruamel.yaml 0.15.34

Hi Michael,

I think this is a nice advent calendar target

On Wed, Nov 22, 2017 at 10:46:37PM +0200, Adrian Bunk wrote:
> Installed /build/1st/cwltool-1.0.20170810192106
> Processing dependencies for cwltool==1.0.20170810192106
> Searching for ruamel.yaml<0.15,>=0.12.4

I "solved" this by droping the explicte version range in setup.py.
Please verify that this solution is correct! 

I also upgraded to latest upstream (also updating the Depencency
python-schema-salad - just uploaded).  Unfortunately this leads to
a build error I do not really understand:

...
   debian/rules override_dh_installman
make[1]: Entering directory '/build/cwltool-1.0.20171107133715'
python2 setup.py develop --user
running develop
running egg_info
writing requirements to cwltool.egg-info/requires.txt
writing cwltool.egg-info/PKG-INFO
writing top-level names to cwltool.egg-info/top_level.txt
writing dependency_links to cwltool.egg-info/dependency_links.txt
writing entry points to cwltool.egg-info/entry_points.txt
reading manifest file 'cwltool.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no previously-included files matching '*~' found anywhere in 
distribution
warning: no previously-included files matching '*.pyc' found anywhere in 
distribution
writing manifest file 'cwltool.egg-info/SOURCES.txt'
running build_ext
Creating 
/build/cwltool-1.0.20171107133715/fakehome/.local/lib/python2.7/site-packages/cwltool.egg-link
 (link to .)
Adding cwltool 1.0.20171107133715 to easy-install.pth file
Installing cwltool script to 
/build/cwltool-1.0.20171107133715/fakehome/.local/bin

Installed /build/cwltool-1.0.20171107133715
Processing dependencies for cwltool==1.0.20171107133715
Searching for avro==1.8.1
Reading https://pypi.python.org/simple/avro/
Download error on https://pypi.python.org/simple/avro/: [Errno -3] Temporary 
failure in name resolution -- Some packages may not be found!
Couldn't retrieve index page for 'avro'
Scanning index of all packages (this may take a while)
Reading https://pypi.python.org/simple/
Download error on https://pypi.python.org/simple/: [Errno -3] Temporary failure 
in name resolution -- Some packages may not be found!
No local packages or working download links found for avro==1.8.1
error: Could not find suitable distribution for Requirement.parse('avro==1.8.1')
debian/rules:17: recipe for target 'debian/cwltool.1' failed
...

I have no idea what might be done when installing manpages - obviously
quite a bit and I have not found the code line where some specific
version of avro seems to be hard coded.

Could you please have a look and join the advent bug squashing party by
doing so?

Thanks a lot

  Andreas.

-- 
http://fam-tille.de

Bug#883019: marked as done (meta-gnome3: Hold in unstable until gtk+2.0 migrates to testing)

Your message dated Wed, 06 Dec 2017 16:05:05 +
with message-id 
and subject line Bug#883019: fixed in meta-gnome3 1:3.22+7
has caused the Debian Bug report #883019,
regarding meta-gnome3: Hold in unstable until gtk+2.0 migrates to testing
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.)


-- 
883019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883019
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: meta-gnome3
Version: 1:3.22+6
Severity: serious

Hi, this is just a placeholder bug for a relatively minor issue, but
why cause regressions if we don't have to?

meta-gnome3 1:3.22+6 drops some dependencies because gtk+2.0 2.24.31-3
recommends them instead. This is one part of a larger effort to reduce
the number of core packages depending on gtk2. See
https://launchpad.net/bugs/1585903 for a bit more details about that
goal.

The problem is that the gtk+2.0 update won't migrate to testing until
glib2.0 does, but glib2.0 is stuck because of an arm64 builder issue:
https://bugs.debian.org/880883

Therefore, I'm filing this bug since we don't want the meta-gnome3
update to land in testing before the gtk2 update does.

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: meta-gnome3
Source-Version: 1:3.22+7

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated meta-gnome3 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: Wed, 06 Dec 2017 10:05:40 -0500
Source: meta-gnome3
Binary: gnome-core gnome gnome-games gnome-platform-devel gnome-devel 
gnome-api-docs
Architecture: source
Version: 1:3.22+7
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bicha 
Description:
 gnome  - Full GNOME Desktop Environment, with extra components
 gnome-api-docs - API reference documentation for the GNOME libraries
 gnome-core - GNOME Desktop Environment -- essential components
 gnome-devel - GNOME Desktop Environment -- development tools
 gnome-games - games for the GNOME desktop
 gnome-platform-devel - GNOME development platform
Closes: 883019
Changes:
 meta-gnome3 (1:3.22+7) unstable; urgency=medium
 .
   [ Jeremy Bicha ]
   * gnome-core: Don't depend on libcaribou-gtk3-module, since it's no
 longer needed by caribou when running in GNOME Shell
   * gnome-core: Restore depends on gnome-themes-standard since it can
 now be pre-installed without forcing GTK+ 2 to be installed
 (Closes: #883019)
 .
   [ Simon McVittie ]
   * Adjust previous changelog entry to not suggest that gnome-keyring
 is deprecated. It is the libgnome-keyring client library that was
 deprecated (superseded by libsecret). gnome-keyring continues to be
 a core part of GNOME.
Checksums-Sha1:
 9173e9d6304ecf43a52502f257115590a2fe974a 2088 meta-gnome3_3.22+7.dsc
 668fa9f7ac048be4685078e726e59bf15ef0b443 23620 meta-gnome3_3.22+7.tar.xz
 21180af37ab6750b51ec7d11405a5d2e185b264d 8120 
meta-gnome3_3.22+7_source.buildinfo
Checksums-Sha256:
 f4f9f0e59ed04dbd6eb133fb32fd7e2a836bfea6012dbde61bf1fa07e8464f59 2088 
meta-gnome3_3.22+7.dsc
 4ac0f95f796d4d48e296efc3ab5d4388384b6cb6376964cad5ddab441fa5d806 23620 
meta-gnome3_3.22+7.tar.xz
 3c22194fa742d029933327720a356ace73d3944de6feebc4b18b3bea3dbadf34 8120 
meta-gnome3_3.22+7_source.buildinfo
Files:
 16d0807f6408e58564a7bc42f0f587fc 2088 metapackages optional 
meta-gnome3_3.22+7.dsc
 969e83336e26b32b30625310e3f6e6f5 23620 metapackages optional 
meta-gnome3_3.22+7.tar.xz
 4c9a496d5383de3ab1f0a27844202790 8120 metapackages optional 
meta-gnome3_3.22+7_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJaKAekAAoJEOZsd1rr/mx9FegP/jVfZcRThf4bi33j0KyHvyCF
nwwvko0UrSi9kTqUVrkkDGF8Zty/zWag7w5qUincUgi19KRXTMtzOCivd36xS+g8
FKj/KYv2NQtDxWMYval8ziUg3I9DIkp1ndh9/Bh9JiiIIgzDxacUubdTk7UQEsLZ

Bug#853599: [Debian-med-packaging] Bug#853599: opensurgsim: ftbfs with GCC-7

2017-12-06 Thread Fabian Klötzl

Hi,

Above one of the failing tests is a peculiar comment:

// TODO(bert): There is some Eigen flag that causes matrices and vectors
to be
//   initialized after all!  We should check for that here.

So I am guessing that the authors knew that their test was flaky and
thus we should be save deactivating them. If you agree, I will go ahead.

Best,
Fabian

Bug#883673: fix build with libcdio 1.0

2017-12-06 Thread Rocky Bernstein

Dominic - I see you have forked the Perl libcdio code. I have just updated
it with something that provisionally works with
http://rocky.github.io/libcdio-1.1.0rc1.tar.bz2  the current 1.1.0 release
candidate.  That Perl code still needs fixups for (not recent) CD-Text API
changes.

In the last libcdio release, I removed the rather old CD-Text API but we
were stull using that in the Perl bindings.

In general what has to happen is 1.1.0 needs to get out there. Then another
Device::Cdio will be released which uses that and will depend on 1.1.0 (not
1.0.0).

Sorry everyone for all of the hassle. With luck, perhaps this will be the
last set of libcdio stuff I do.

On Wed, Dec 6, 2017 at 7:59 AM, Dominic Hargreaves  wrote:

> On Wed, Dec 06, 2017 at 11:46:31AM +0100, Matthias Klose wrote:
> > Package: src:libdevice-cdio-perl
> > Version: 0.4.0-2
> > Severity: serious
> > Tags: sid buster patch
> >
> > One driver is gone upstream.
> >
> > patch at
> > http://launchpadlibrarian.net/348274120/libdevice-cdio-perl_
> 0.4.0-2build1_0.4.0-2ubuntu1.diff.gz
>
> Hi Matthew,
>
> I tried applying this patch (both to the Debian package and to upstream
> git ready for forwarding) but I get the following build failures on sid:
>
> ./perlcdio_wrap.c: In function 'get_cdtext':
> ./perlcdio_wrap.c:2439:14: error: too many arguments to function
> 'cdio_get_cdtex
> t'
>  cdtext = cdio_get_cdtext (p_cdio, (track_t) track);
>   ^~~
> In file included from /usr/include/cdio/cdio.h:62:0,
>  from ./perlcdio_wrap.c:1562:
> /usr/include/cdio/disc.h:77:13: note: declared here
>cdtext_t *cdio_get_cdtext (CdIo_t *p_cdio);
>  ^~~
> ./perlcdio_wrap.c:2448:29: warning: passing argument 1 of
> 'cdtext_get_const' makes pointer from integer without a cast
> [-Wint-conversion]
>  if(cdtext_get_const(num,cdtext)) {
>  ^~~
> In file included from /usr/include/cdio/cdio.h:59:0,
>  from ./perlcdio_wrap.c:1562:
> /usr/include/cdio/cdtext.h:262:13: note: expected 'const cdtext_t * {aka
> const struct cdtext_s *}' but argument is of type 'int'
>  const char *cdtext_get_const (const cdtext_t *p_cdtext, cdtext_field_t
> field,
>  ^~~~
> ./perlcdio_wrap.c:2448:33: error: incompatible type for argument 2 of
> 'cdtext_get_const'
>  if(cdtext_get_const(num,cdtext)) {
>  ^~
>
> [...]
>
> (full log attached).
>
> Do you have any suggestions about how to resolve this?
>
> Cheers,
> Dominic.
>

Bug#883680: marked as done (systemd: Compiling systemd-232.25 debian rules override_dh_auto_test fails)

Your message dated Wed, 6 Dec 2017 15:18:43 +0100
with message-id 
and subject line Re: Bug#883680: systemd: Compiling systemd-232.25 debian rules 
override_dh_auto_test fails
has caused the Debian Bug report #883680,
regarding systemd: Compiling systemd-232.25 debian rules override_dh_auto_test 
fails
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.)


-- 
883680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883680
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 232-25+deb9u1
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

I try to build systemd-232.25 from sources. I downloaded it from here: 
https://launchpad.net/debian/+source/systemd/232-25

I first build debian 9 stretch:

#!/bin/bash

INCLUDEDCOMPS="ssh,vim,dbus,python-dbus,python-gobject,python-psutil,jq,iptables-persistent,vnstat,curl,ntp,ntpdate,software-properties-common,lrzsz,sudo,dosfstools,mtd-utils,debsig-verify,unzip,file,libxslt1.1,alsa-utils,mediainfo,zip,net-tools"
TARGET="omnia-stretch"

CURDIR=$(pwd)

[ -d ${TARGET_DIR} ] && sudo rm -rf ${TARGET_DIR}
mkdir -p ${TARGET_DIR}
sudo qemu-debootstrap \
--arch=armhf \
--components=main,contrib,non-free \
--include=${INCLUDEDCOMPS} \
--exclude=nano \
--foreign \
stretch \
${TARGET} \
http://ftp.debian.org/debian
sudo cp ${CURDIR}/user/gst/gst.apt ${TARGET}/etc/apt/sources.list
sudo chroot ${TARGET} apt-get -y --allow-unauthenticated install gstreamer1.0-x 
gstreamer1.0-tools gstreamer1.0-plugins-good gstreamer1.0-plugins-bad 
gstreamer1.0-alsa
exit 0

Then I run make systemd:

TARGET  := $(TARGET_DIR)
USERDIR := $(CURDIR)/..
SYSTEMD_DIR := $(CURDIR)

.PHONY: systemd

systemd: CC =

systemd:
sudo chroot $(TARGET) apt-get install -y --allow-unauthenticated 
dpkg-dev aptitude
mkdir -p $(SYSTEMD_DIR)/.build/src
mkdir -p $(SYSTEMD_DIR)/.build/result
mkdir -p $(SYSTEMD_DIR)/.build/aptcache
mkdir -p $(SYSTEMD_DIR)/.build/build
if [ ! -d $(TARGET)/var/cache/apt/archives ]; then\
 sudo mkdir -p $(TARGET)/var/cache/apt/archives;\
fi
cd $(SYSTEMD_DIR);\
tar -xvf systemd_232.tar.gz -C $(SYSTEMD_DIR)/.build/src;\
cd $(SYSTEMD_DIR)/.build/src/systemd-232;\
quilt import $(SYSTEMD_DIR)/patches/new-ouput-format-precise-iso.patch;\
pdebuild --buildresult $(SYSTEMD_DIR)/.build/result -- --no-targz 
--distribution stretch --architecture armhf --aptcache 
$(SYSTEMD_DIR)/.build/aptcache --buildplace $(TARGET) --logfile 
$(SYSTEMD_DIR)/log


systemd_232.tar.gz was done with command:
tar cfz systemd_232.tar.gz systemd_232.orig.tar.gz systemd_232-25+deb9u1.dsc 
systemd_232-25+deb9u1.debian.tar.xz systemd-232

I cross-compile the systemd for armhf with debian 9 stretch from:

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.1 LTS"
NAME="Ubuntu"
VERSION="16.04.1 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.1 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/;
SUPPORT_URL="http://help.ubuntu.com/;
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
UBUNTU_CODENAME=xenial

The compilation stops on override_dh_auto_test. The tests that fail are:

FAIL: test-loopback
FAIL: test-path-util
FAIL: test-util
FAIL: test-process-util
FAIL: test-fileio
FAIL: test-sigbus
FAIL: test-bus-creds
FAIL: test-netlink
FAIL: test-local-addresses
FAIL: test-journal-send
FAIL: test-compress
FAIL: test-network
FAIL test-bus-creds (exit status: 134)
FAIL test-compress (exit status: 134)
FAIL test-fileio (exit status: 134)
FAIL test-journal-send (exit status: 134)
FAIL test-local-addresses (exit status: 134)
FAIL test-loopback (exit status: 1)
FAIL test-netlink (exit status: 134)
FAIL test-network (exit status: 134)
FAIL test-path-util (exit status: 134)
FAIL test-process-util (exit status: 134)
FAIL test-sigbus (exit status: 139)
FAIL: test-loopback
FAIL test-loopback (exit status: 1)
FAIL: test-path-util
FAIL test-path-util (exit status: 134)
FAIL: test-util
FAIL test-util (exit status: 134)
FAIL: test-process-util
FAIL test-process-util (exit status: 134)
FAIL: test-fileio
FAIL test-fileio (exit status: 134)
FAIL: test-sigbus
FAIL test-sigbus (exit status: 139)
FAIL: test-bus-creds
FAIL test-bus-creds (exit status: 134)
FAIL: test-netlink
FAIL test-netlink (exit status: 134)
FAIL: test-local-addresses
FAIL test-local-addresses (exit status: 134)
FAIL: test-journal-send
FAIL

Bug#883673: fix build with libcdio 1.0

2017-12-06 Thread Rocky Bernstein

 Oops --

#define LIBCDIO_VERSION_NUM 10100

is the current version number that will be in the next release. in the
1.0.0 release it was erroneously 1.

On Wed, Dec 6, 2017 at 8:30 AM, Rocky Bernstein  wrote:

> Don't know how this solves things, but  compiling locally there is another
> problem with the *unpatched sources. *In the the 1.0.0 release I
>
> *have*#define LIBCDIO_VERSION_NUM 10100
>
> but this should be a number greater than 100. I am working on a
> libcdio-1.1.0 release which will be out probably within a week or two that
> addresses this problem.
> It also addresses all of remaining memory leaks that I have been able to
> find in the library code (and example programs and tests). So I kind of
> consider it to be important.
>
> I am also working on an update to Device::Cdio which removes long obsolete
> code, and removes the no-longer-supported drivers (there are two, OS/2 and
> BSDI, not one) and whatever else has changed in the last 5 or so years.
>
>
> On Wed, Dec 6, 2017 at 8:06 AM, Matthias Klose  wrote:
>
>> On 06.12.2017 13:59, Dominic Hargreaves wrote:
>> > On Wed, Dec 06, 2017 at 11:46:31AM +0100, Matthias Klose wrote:
>> >> Package: src:libdevice-cdio-perl
>> >> Version: 0.4.0-2
>> >> Severity: serious
>> >> Tags: sid buster patch
>> >>
>> >> One driver is gone upstream.
>> >>
>> >> patch at
>> >> http://launchpadlibrarian.net/348274120/libdevice-cdio-perl_
>> 0.4.0-2build1_0.4.0-2ubuntu1.diff.gz
>> >
>> > Hi Matthew,
>> >
>> > I tried applying this patch (both to the Debian package and to upstream
>> > git ready for forwarding) but I get the following build failures on sid:
>> >
>> > ./perlcdio_wrap.c: In function 'get_cdtext':
>> > ./perlcdio_wrap.c:2439:14: error: too many arguments to function
>> 'cdio_get_cdtex
>> > t'
>> >  cdtext = cdio_get_cdtext (p_cdio, (track_t) track);
>> >   ^~~
>> > In file included from /usr/include/cdio/cdio.h:62:0,
>> >  from ./perlcdio_wrap.c:1562:
>> > /usr/include/cdio/disc.h:77:13: note: declared here
>> >cdtext_t *cdio_get_cdtext (CdIo_t *p_cdio);
>> >  ^~~
>> > ./perlcdio_wrap.c:2448:29: warning: passing argument 1 of
>> 'cdtext_get_const' makes pointer from integer without a cast
>> [-Wint-conversion]
>> >  if(cdtext_get_const(num,cdtext)) {
>> >  ^~~
>> > In file included from /usr/include/cdio/cdio.h:59:0,
>> >  from ./perlcdio_wrap.c:1562:
>> > /usr/include/cdio/cdtext.h:262:13: note: expected 'const cdtext_t *
>> {aka const struct cdtext_s *}' but argument is of type 'int'
>> >  const char *cdtext_get_const (const cdtext_t *p_cdtext, cdtext_field_t
>> field,
>> >  ^~~~
>> > ./perlcdio_wrap.c:2448:33: error: incompatible type for argument 2 of
>> 'cdtext_get_const'
>> >  if(cdtext_get_const(num,cdtext)) {
>> >  ^~
>> >
>> > [...]
>> >
>> > (full log attached).
>> >
>> > Do you have any suggestions about how to resolve this?
>>
>> yes, fixed in libcdio-1.0.0-2
>>
>>
>

Bug#883673: fix build with libcdio 1.0

2017-12-06 Thread Rocky Bernstein

Don't know how this solves things, but  compiling locally there is another
problem with the *unpatched sources. *In the the 1.0.0 release I

*have*#define LIBCDIO_VERSION_NUM 10100

but this should be a number greater than 100. I am working on a
libcdio-1.1.0 release which will be out probably within a week or two that
addresses this problem.
It also addresses all of remaining memory leaks that I have been able to
find in the library code (and example programs and tests). So I kind of
consider it to be important.

I am also working on an update to Device::Cdio which removes long obsolete
code, and removes the no-longer-supported drivers (there are two, OS/2 and
BSDI, not one) and whatever else has changed in the last 5 or so years.


On Wed, Dec 6, 2017 at 8:06 AM, Matthias Klose  wrote:

> On 06.12.2017 13:59, Dominic Hargreaves wrote:
> > On Wed, Dec 06, 2017 at 11:46:31AM +0100, Matthias Klose wrote:
> >> Package: src:libdevice-cdio-perl
> >> Version: 0.4.0-2
> >> Severity: serious
> >> Tags: sid buster patch
> >>
> >> One driver is gone upstream.
> >>
> >> patch at
> >> http://launchpadlibrarian.net/348274120/libdevice-cdio-perl_
> 0.4.0-2build1_0.4.0-2ubuntu1.diff.gz
> >
> > Hi Matthew,
> >
> > I tried applying this patch (both to the Debian package and to upstream
> > git ready for forwarding) but I get the following build failures on sid:
> >
> > ./perlcdio_wrap.c: In function 'get_cdtext':
> > ./perlcdio_wrap.c:2439:14: error: too many arguments to function
> 'cdio_get_cdtex
> > t'
> >  cdtext = cdio_get_cdtext (p_cdio, (track_t) track);
> >   ^~~
> > In file included from /usr/include/cdio/cdio.h:62:0,
> >  from ./perlcdio_wrap.c:1562:
> > /usr/include/cdio/disc.h:77:13: note: declared here
> >cdtext_t *cdio_get_cdtext (CdIo_t *p_cdio);
> >  ^~~
> > ./perlcdio_wrap.c:2448:29: warning: passing argument 1 of
> 'cdtext_get_const' makes pointer from integer without a cast
> [-Wint-conversion]
> >  if(cdtext_get_const(num,cdtext)) {
> >  ^~~
> > In file included from /usr/include/cdio/cdio.h:59:0,
> >  from ./perlcdio_wrap.c:1562:
> > /usr/include/cdio/cdtext.h:262:13: note: expected 'const cdtext_t *
> {aka const struct cdtext_s *}' but argument is of type 'int'
> >  const char *cdtext_get_const (const cdtext_t *p_cdtext, cdtext_field_t
> field,
> >  ^~~~
> > ./perlcdio_wrap.c:2448:33: error: incompatible type for argument 2 of
> 'cdtext_get_const'
> >  if(cdtext_get_const(num,cdtext)) {
> >  ^~
> >
> > [...]
> >
> > (full log attached).
> >
> > Do you have any suggestions about how to resolve this?
>
> yes, fixed in libcdio-1.0.0-2
>
>

Bug#883673: fix build with libcdio 1.0

2017-12-06 Thread Matthias Klose

On 06.12.2017 13:59, Dominic Hargreaves wrote:
> On Wed, Dec 06, 2017 at 11:46:31AM +0100, Matthias Klose wrote:
>> Package: src:libdevice-cdio-perl
>> Version: 0.4.0-2
>> Severity: serious
>> Tags: sid buster patch
>>
>> One driver is gone upstream.
>>
>> patch at
>> http://launchpadlibrarian.net/348274120/libdevice-cdio-perl_0.4.0-2build1_0.4.0-2ubuntu1.diff.gz
> 
> Hi Matthew,
> 
> I tried applying this patch (both to the Debian package and to upstream
> git ready for forwarding) but I get the following build failures on sid:
> 
> ./perlcdio_wrap.c: In function 'get_cdtext':
> ./perlcdio_wrap.c:2439:14: error: too many arguments to function 
> 'cdio_get_cdtex
> t'
>  cdtext = cdio_get_cdtext (p_cdio, (track_t) track);
>   ^~~
> In file included from /usr/include/cdio/cdio.h:62:0,
>  from ./perlcdio_wrap.c:1562:
> /usr/include/cdio/disc.h:77:13: note: declared here
>cdtext_t *cdio_get_cdtext (CdIo_t *p_cdio);
>  ^~~
> ./perlcdio_wrap.c:2448:29: warning: passing argument 1 of 'cdtext_get_const' 
> makes pointer from integer without a cast [-Wint-conversion]
>  if(cdtext_get_const(num,cdtext)) {
>  ^~~
> In file included from /usr/include/cdio/cdio.h:59:0,
>  from ./perlcdio_wrap.c:1562:
> /usr/include/cdio/cdtext.h:262:13: note: expected 'const cdtext_t * {aka 
> const struct cdtext_s *}' but argument is of type 'int'
>  const char *cdtext_get_const (const cdtext_t *p_cdtext, cdtext_field_t field,
>  ^~~~
> ./perlcdio_wrap.c:2448:33: error: incompatible type for argument 2 of 
> 'cdtext_get_const'
>  if(cdtext_get_const(num,cdtext)) {
>  ^~
> 
> [...]
> 
> (full log attached).
> 
> Do you have any suggestions about how to resolve this?

yes, fixed in libcdio-1.0.0-2

Bug#883673: fix build with libcdio 1.0

2017-12-06 Thread Dominic Hargreaves

On Wed, Dec 06, 2017 at 11:46:31AM +0100, Matthias Klose wrote:
> Package: src:libdevice-cdio-perl
> Version: 0.4.0-2
> Severity: serious
> Tags: sid buster patch
> 
> One driver is gone upstream.
> 
> patch at
> http://launchpadlibrarian.net/348274120/libdevice-cdio-perl_0.4.0-2build1_0.4.0-2ubuntu1.diff.gz

Hi Matthew,

I tried applying this patch (both to the Debian package and to upstream
git ready for forwarding) but I get the following build failures on sid:

./perlcdio_wrap.c: In function 'get_cdtext':
./perlcdio_wrap.c:2439:14: error: too many arguments to function 'cdio_get_cdtex
t'
 cdtext = cdio_get_cdtext (p_cdio, (track_t) track);
  ^~~
In file included from /usr/include/cdio/cdio.h:62:0,
 from ./perlcdio_wrap.c:1562:
/usr/include/cdio/disc.h:77:13: note: declared here
   cdtext_t *cdio_get_cdtext (CdIo_t *p_cdio);
 ^~~
./perlcdio_wrap.c:2448:29: warning: passing argument 1 of 'cdtext_get_const' 
makes pointer from integer without a cast [-Wint-conversion]
 if(cdtext_get_const(num,cdtext)) {
 ^~~
In file included from /usr/include/cdio/cdio.h:59:0,
 from ./perlcdio_wrap.c:1562:
/usr/include/cdio/cdtext.h:262:13: note: expected 'const cdtext_t * {aka const 
struct cdtext_s *}' but argument is of type 'int'
 const char *cdtext_get_const (const cdtext_t *p_cdtext, cdtext_field_t field,
 ^~~~
./perlcdio_wrap.c:2448:33: error: incompatible type for argument 2 of 
'cdtext_get_const'
 if(cdtext_get_const(num,cdtext)) {
 ^~

[...]

(full log attached).

Do you have any suggestions about how to resolve this?

Cheers,
Dominic.
sbuild (Debian sbuild) 0.73.0 (23 Dec 2016) on himalia.internal.semmle.com

+==+
| libdevice-cdio-perl 0.4.0-3 (amd64)  Wed, 06 Dec 2017 12:53:07 + |
+==+

Package: libdevice-cdio-perl
Version: 0.4.0-3
Source Version: 0.4.0-3
Distribution: sid
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: binary

I: NOTICE: Log filtering will replace 
'var/run/schroot/mount/sid-amd64-sbuild-da6941f7-b7da-4f42-9d95-94af0fb241a3' 
with '<>'

+--+
| Update chroot|
+--+

Hit:1 http://localhost:3142/debian sid InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

+--+
| Fetch source files   |
+--+

Local sources
-

/home/dom/working/debian/pkg-perl/libdevice-cdio-perl_0.4.0-3.dsc exists in 
/home/dom/working/debian/pkg-perl; copying to chroot
I: NOTICE: Log filtering will replace 
'build/libdevice-cdio-perl-3ngYLQ/libdevice-cdio-perl-0.4.0' with 
'<>'
I: NOTICE: Log filtering will replace 'build/libdevice-cdio-perl-3ngYLQ' with 
'<>'

+--+
| Install build-essential  |
+--+

Setup apt archive
-

Merged Build-Depends: build-essential, fakeroot
Filtered Build-Depends: build-essential, fakeroot
dpkg-deb: building package 'sbuild-build-depends-core-dummy' in 
'/<>/resolver-5QCaU6/apt_archive/sbuild-build-depends-core-dummy.deb'.
dpkg-scanpackages: warning: Packages in archive but missing from override file:
dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy
dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
Ign:1 copy:/<>/resolver-5QCaU6/apt_archive ./ InRelease
Get:2 copy:/<>/resolver-5QCaU6/apt_archive ./ Release [957 B]
Ign:3 copy:/<>/resolver-5QCaU6/apt_archive ./ Release.gpg
Get:4 copy:/<>/resolver-5QCaU6/apt_archive ./ Sources [349 B]
Get:5 copy:/<>/resolver-5QCaU6/apt_archive ./ Packages [432 B]
Fetched 1738 B in 0s (140 kB/s)
Reading package lists...
Reading package lists...

Install core build dependencies (apt-based resolver)

Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  sbuild-build-depends-core-dummy
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 852 B of archives.
After this operation, 0 B of

Bug#883672: incorrect rendering of pdf using libpoppler68 backend

Control: reassign -1 src:poppler 0.57.0-2

Reassigning to the correct package.

On Wed, Dec 06, 2017 at 04:10:08PM +0530, Marcus Britanicus wrote:
> Package: bugs.debian.org
> Severity: serious
> 
> All PDF viewers using libpoppler68 (0.57.0-2) backed do not render some PDFs
> incorrectly. In most cases, some text is not rendered at all and symbols and
> images only are rendered. This issue is seen in okular, evince, zathura,
> qpdfview, and two custom pdf viewers (based on Qt4 and Qt5) written by me to
> test issue. MuPDF and firefox do render the same PDF correctly.
> 
> 
> 
> -- System Information:
> Debian Release: Sid
>   APT prefers unstable
>   APT policy: (900, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.14.0-trunk-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)

Processed: Re: Bug#883672: incorrect rendering of pdf using libpoppler68 backend

Processing control commands:

> reassign -1 src:poppler 0.57.0-2
Bug #883672 [bugs.debian.org] incorrect rendering of pdf using libpoppler68 
backend
Bug reassigned from package 'bugs.debian.org' to 'src:poppler'.
Ignoring request to alter found versions of bug #883672 to the same values 
previously set
Ignoring request to alter fixed versions of bug #883672 to the same values 
previously set
Bug #883672 [src:poppler] incorrect rendering of pdf using libpoppler68 backend
Marked as found in versions poppler/0.57.0-2.

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

Bug#880776: NMU for mrtg?

2017-12-06 Thread Adam Majer


Hi,

This looks good. If you would like to, you may just upload this.

Thanks,
Adam


On 12/05/2017 06:09 PM, Roland Rosenfeld wrote:

Hi!

I'm currently planning to upload a new version of
libsnmp-session-perl, which now contains the file Net_SNMP_util.pm
that you currently ship in mrtg.

For this it would be necessary, that mrtg depends on the new
libsnmp-session-perl version (>= 1.14~git20130523.186a005-1) to avoid
the file existing in both packages.

For this I prepared an NMU for mrtg (patch is attached).

Since I just noticed, that mrtg has RC bug open, that it build-depends
on libgd2-noxpm-dev, which is replaced by libgd-dev now (the old
package was only a transitional package, pulling in libgd-dev), so
changing this build-dependency to directly pointing to libgd-dev
shouldn't be a big deal and I added it to my NMU, too.

Do you allow me, to upload the modified mrtg package to the archive?

Greetings
Roland

Bug#859829: Please migrate to openssl1.1 in Buster

2017-12-06 Thread Ferenc Wágner

Sebastian Andrzej Siewior  writes:

> this is a remainder about the openssl transition [0]. We really want to
> remove libssl1.0-dev from unstable for Buster. I will raise the severity
> of this bug to serious in a month. Please react before that happens.

Sorry, we can't do much until new major versions of Apache XML Security
(Santuario) and the Shibboleth stack are released with support for
OpenSSL 1.1, probably in the first half of 2018.  Upstream knows about
the issue and has already made significant work on it, but refrained
from making more immediate promises, see #859831.
-- 
Regards,
Feri

Bug#883642: marked as done (python-networking-mlnx: uninstallable in sid: Depends: python-sqlalchemy (< 1.1.0) but 1.1.11+ds1-1 is to be installed)

Your message dated Wed, 06 Dec 2017 12:34:14 +
with message-id 
and subject line Bug#883642: fixed in networking-mlnx 1:11.0.0-2
has caused the Debian Bug report #883642,
regarding python-networking-mlnx: uninstallable in sid: Depends: 
python-sqlalchemy (< 1.1.0) but 1.1.11+ds1-1 is to be installed
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.)


-- 
883642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883642
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-networking-mlnx
Version: 1:11.0.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable in sid:

The following packages have unmet dependencies:
 python-networking-mlnx : Depends: python-sqlalchemy (< 1.1.0) but 1.1.11+ds1-1 
is to be installed
E: Unable to correct problems, you have held broken packages.


Cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: networking-mlnx
Source-Version: 1:11.0.0-2

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

Debian distribution maintenance software
pp.
Ondřej Nový  (supplier of updated networking-mlnx 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: Wed, 06 Dec 2017 13:05:32 +0100
Source: networking-mlnx
Binary: networking-mlnx-common networking-mlnx-eswitchd neutron-mlnx-agent 
python-networking-mlnx
Architecture: source all
Version: 1:11.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Ondřej Nový 
Description:
 networking-mlnx-common - OpenStack virtual network service - Mellanox plugin 
common files
 networking-mlnx-eswitchd - Neutron is a virtual network service for Openstack 
- Mellanox esw
 neutron-mlnx-agent - OpenStack virtual network service - Mellanox plugin agent
 python-networking-mlnx - OpenStack virtual network service - Mellanox plugin 
Python 2.7 fi
Closes: 883642
Changes:
 networking-mlnx (1:11.0.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Allow newer python-sqlalchemy (Closes: #883642)
Checksums-Sha1:
 96adc374b00959357f7d1158bdb16c898e299472 3192 networking-mlnx_11.0.0-2.dsc
 c351bd6f90ea28cba50d17c648e9cec719831769 4436 
networking-mlnx_11.0.0-2.debian.tar.xz
 24fb71a2c3adf36e608c8151de9a60d46c63b59f 4984 
networking-mlnx-common_11.0.0-2_all.deb
 a5243f8c9dd0646dd41ae49b7e110a9a9f96fd99 5824 
networking-mlnx-eswitchd_11.0.0-2_all.deb
 b7b3b621f23928c8db90ecdaa1c5af404258be8a 17138 
networking-mlnx_11.0.0-2_amd64.buildinfo
 790b837f79628987f249d141f9a7b1c658cf5bc2 5772 
neutron-mlnx-agent_11.0.0-2_all.deb
 b10dab4d3e159c773b354a18126b4fa2cdaf4272 44652 
python-networking-mlnx_11.0.0-2_all.deb
Checksums-Sha256:
 e2c320cf63390fd227af8323cfe4d3ac6ff583eec4fa71b1aed4bc302becfa42 3192 
networking-mlnx_11.0.0-2.dsc
 1deffe68e874436b708d315b35aa895b60097ad3242cb5a7d630d1b335964023 4436 
networking-mlnx_11.0.0-2.debian.tar.xz
 42cb4b6b56e4bf52109e18f2476c091c6267dbbba25b4bea798ee45b83cc82d9 4984 
networking-mlnx-common_11.0.0-2_all.deb
 d22242105aa6b28fe0cca268c86b554a25d087762849eaa9e9758dbc05927f9b 5824 
networking-mlnx-eswitchd_11.0.0-2_all.deb
 4ba9eea35991981b66e9dfd5a7d2a75dd598c92dbd21d6e8def7fed062733350 17138 
networking-mlnx_11.0.0-2_amd64.buildinfo
 0e2a0657e0c56c0457d55a09ab3b779f05f2835bb0837456ec65f63ae1ae67df 5772 
neutron-mlnx-agent_11.0.0-2_all.deb
 7f6711fd9f05e521264722b483b0ea65f107f15194ca07424ecd4dd6b2bdd7eb 44652 
python-networking-mlnx_11.0.0-2_all.deb
Files:
 fb3aee5b4dfed9c7dc4b4e9ad81d787d 3192 net optional networking-mlnx_11.0.0-2.dsc
 28cd315770c737b35b7f6aa8d2e8a9cb 4436 net optional 
networking-mlnx_11.0.0-2.debian.tar.xz
 82ce239ff7cb85aacc42bb73a6892a13 4984 net optional 
networking-mlnx-common_11.0.0-2_all.deb
 aadb96036fa425edb2384d8c7c58f1dd 5824 net optional 
networking-mlnx-eswitchd_11.0.0-2_all.deb
 73777c76aaa2dd309855e1c18f7ef9e6 17138 net optional

Bug#883642: marked as pending

2017-12-06 Thread Ondřej Nový

tag 883642 pending
thanks

Hello,

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


https://anonscm.debian.org/cgit/openstack/services/networking-mlnx.git/commit/?id=db555c9

---
commit db555c9b1c8c9af8cc08446bb79dfe31615703fb
Author: Ondřej Nový 
Date:   Wed Dec 6 13:03:33 2017 +0100

Rebuild with newer python-sqlalchemy (Closes: #883642)

diff --git a/debian/changelog b/debian/changelog
index d5bb8b4..08f1e7f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,7 +1,14 @@
+networking-mlnx (1:11.0.0-2) UNRELEASED; urgency=medium
+
+  * Team upload.
+  * Allow newer python-sqlalchemy (Closes: #883642)
+
+ -- Ondřej Nový   Wed, 06 Dec 2017 12:56:34 +0100
+
 networking-mlnx (1:11.0.0-1) unstable; urgency=medium
 
   * Updating VCS fields.
-  * Updating copyright format url. 
+  * Updating copyright format url.
   * Updating maintainer field.
   * Running wrap-and-sort -bast.
   * Updating standards version to 4.1.1.

Processed: Bug#883642 marked as pending

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

> tag 883642 pending
Bug #883642 [python-networking-mlnx] python-networking-mlnx: uninstallable in 
sid: Depends: python-sqlalchemy (< 1.1.0) but 1.1.11+ds1-1 is to be installed
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#883621: marked as done (nova: CVE-2017-17051: Nova FilterScheduler doubles resource allocations during rebuild with new image)

Your message dated Wed, 06 Dec 2017 12:05:12 +
with message-id 
and subject line Bug#883621: fixed in nova 2:16.0.3-5
has caused the Debian Bug report #883621,
regarding nova: CVE-2017-17051: Nova FilterScheduler doubles resource 
allocations during rebuild with new image
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.)


-- 
883621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883621
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nova
Version: 2:16.0.3-1
Severity: grave
Tags: security upstream

Hi,

the following vulnerability was published for nova.

CVE-2017-17051[0]:
| An issue was discovered in the default FilterScheduler in OpenStack
| Nova 16.0.3. By repeatedly rebuilding an instance with new images, an
| authenticated user may consume untracked resources on a hypervisor host
| leading to a denial of service, aka doubled resource allocations. This
| regression was introduced with the fix for OSSA-2017-005
| (CVE-2017-16239); however, only Nova stable/pike or later deployments
| with that fix applied and relying on the default FilterScheduler are
| affected.

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-17051
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17051
[1] http://www.openwall.com/lists/oss-security/2017/12/05/5

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: nova
Source-Version: 2:16.0.3-5

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated nova package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 06 Dec 2017 12:24:45 +0100
Source: nova
Binary: nova-api nova-cells nova-common nova-compute nova-compute-ironic 
nova-compute-kvm nova-compute-lxc nova-compute-qemu nova-conductor nova-console 
nova-consoleauth nova-consoleproxy nova-doc nova-placement-api nova-scheduler 
nova-volume python-nova
Architecture: source all
Version: 2:16.0.3-5
Distribution: unstable
Urgency: high
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Description:
 nova-api   - OpenStack Compute - compute API frontend
 nova-cells - Openstack Compute - cells
 nova-common - OpenStack Compute - common files
 nova-compute - OpenStack Compute - compute node
 nova-compute-ironic - OpenStack Compute - compute node (Ironic)
 nova-compute-kvm - OpenStack Compute - compute node (KVM)
 nova-compute-lxc - OpenStack Compute - compute node (LXC)
 nova-compute-qemu - OpenStack Compute - compute node (QEmu)
 nova-conductor - OpenStack Compute - conductor service
 nova-console - OpenStack Compute - console
 nova-consoleauth - OpenStack Compute - Console Authenticator
 nova-consoleproxy - OpenStack Compute - NoVNC proxy
 nova-doc   - OpenStack Compute - documentation
 nova-placement-api - OpenStack compute - placement API
 nova-scheduler - OpenStack Compute - virtual machine scheduler
 nova-volume - OpenStack Compute - storage metapackage
 python-nova - OpenStack Compute - libraries
Closes: 883621
Changes:
 nova (2:16.0.3-5) unstable; urgency=high
 .
   * CVE-2017-17051/OSSA-2017-005.1 (errata for CVE-2017-16239/OSSA-2017-005):
 Nova Filter Scheduler bypass through rebuild action. Apply upstream patch:
 Refined fix for validating image on rebuild (Closes: #883621).
Checksums-Sha1:
 a5dd24a9765e291a2fa2ad596a70a71c4b20a166 5406 nova_16.0.3-5.dsc
 8a7eaf2d49e62711517ae1993c5ef7c9341b0346 72796 nova_16.0.3-5.debian.tar.xz
 604634866c7a13de4fca7adfa1fe362038837f31 38476 nova-api_16.0.3-5_all.deb
 4fbf5de99583edd52da27f93e03c47a4f3ae54d8 21848 nova-cells_16.0.3-5_all.deb
 68f0e510df18313ca04ec357d851c4c8f86e87af 127012 nova-common_16.0.3-5_all.deb
 8f3cdd9d54391848ade9f365930c283fafaae580 19540

Processed: reassign 882934 to pcb-gtk

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

> reassign 882934 pcb-gtk
Bug #882934 [pcb] pcb: Segfault on window operations
Bug reassigned from package 'pcb' to 'pcb-gtk'.
No longer marked as found in versions pcb/1:4.0.2-4.
Ignoring request to alter fixed versions of bug #882934 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#882934: [Pkg-electronics-devel] Bug#882934: Segfault on window operations

2017-12-06 Thread أحمد المحمودي

Please try using pcb-gtk using a new user. I suspect that this might be 
related to some setting or maybe GTK theme.

-- 
‎أحمد المحمودي (Ahmed El-Mahmoudy)
 Digital design engineer
GPG KeyIDs: 4096R/A7EF5671 2048R/EDDDA1B7
GPG Fingerprints:
 6E2E E4BB 72E2 F417 D066  6ABF 7B30 B496 A7EF 5761
 8206 A196 2084 7E6D 0DF8  B176 BC19 6A94 EDDD A1B7


signature.asc
Description: PGP signature

Bug#866877: diaspora: fails on being triggered

2017-12-06 Thread Joseph Nuthalapati

tag 866877 + patch

thanks


Hello,

Please find the attached patch to fix this bug.

Thanks and regards,
Joseph Nuthalapati

From 5c2a6fa28a8be3c7fca7c45eb6c5cabc311ac2e6 Mon Sep 17 00:00:00 2001
From: Joseph Nuthalapati 
Date: Wed, 6 Dec 2017 17:16:02 +0530
Subject: [PATCH] Fix syntax error in postinst script

Line 38 in the postinst script is missing brackets.
Also cleaned up whitespaces in the file.

Signed-off-by: Joseph Nuthalapati 
---
 debian/postinst | 12 ++--
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/debian/postinst b/debian/postinst
index 4ad1c85..737fa9f 100755
--- a/debian/postinst
+++ b/debian/postinst
@@ -31,11 +31,11 @@ set -e
 ###
 . /etc/diaspora/diaspora-common.conf
 cd ${diaspora_home}
-	
+
 ###
 # update Gemfile.lock, after first install
 ###
-if -e ${diaspora_conf}; then
+if [ -e ${diaspora_conf} ]; then
   . ${diaspora_conf}
   su ${diaspora_user} -s /bin/sh -c 'truncate -s 0 ${diaspora_home}/Gemfile.lock'
   if ! su ${diaspora_user} -s /bin/sh -c 'bundle --local --quiet'; then
@@ -62,16 +62,16 @@ case "$1" in
 	echo "Setting up environment varibales..."
 	. /usr/lib/diaspora-common/scripts/set-env-diaspora.sh
 	echo RAILS_ENV=$RAILS_ENV DB=$DB ENVIRONMENT_URL=$ENVIRONMENT_URL
-	
+
 	echo "Verifying we have all required libraries..."
 	su diaspora -s /bin/sh -c 'bundle install --local'
-	
+
 	echo "Setting up secret_token..."
-DB=$DB RAILS_ENV=$RAILS_ENV DISABLE_SPRING=1 bundle exec rake generate:secret_token 
+DB=$DB RAILS_ENV=$RAILS_ENV DISABLE_SPRING=1 bundle exec rake generate:secret_token
 
 	# Initialize database
 /usr/lib/diaspora-common/scripts/initdb.sh
- 
+
 	echo "Precompiling assets..."
 	chown -R ${diaspora_user}: /var/lib/diaspora/app-assets /var/lib/diaspora/public
 	su diaspora -s /bin/sh -c 'bundle exec rake tmp:cache:clear assets:precompile'
-- 
2.15.0



signature.asc
Description: OpenPGP digital signature

Bug#883680: systemd: Compiling systemd-232.25 debian rules override_dh_auto_test fails

2017-12-06 Thread Elena

Package: systemd
Version: 232-25+deb9u1
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

I try to build systemd-232.25 from sources. I downloaded it from here: 
https://launchpad.net/debian/+source/systemd/232-25

I first build debian 9 stretch:

#!/bin/bash

INCLUDEDCOMPS="ssh,vim,dbus,python-dbus,python-gobject,python-psutil,jq,iptables-persistent,vnstat,curl,ntp,ntpdate,software-properties-common,lrzsz,sudo,dosfstools,mtd-utils,debsig-verify,unzip,file,libxslt1.1,alsa-utils,mediainfo,zip,net-tools"
TARGET="omnia-stretch"

CURDIR=$(pwd)

[ -d ${TARGET_DIR} ] && sudo rm -rf ${TARGET_DIR}
mkdir -p ${TARGET_DIR}
sudo qemu-debootstrap \
--arch=armhf \
--components=main,contrib,non-free \
--include=${INCLUDEDCOMPS} \
--exclude=nano \
--foreign \
stretch \
${TARGET} \
http://ftp.debian.org/debian
sudo cp ${CURDIR}/user/gst/gst.apt ${TARGET}/etc/apt/sources.list
sudo chroot ${TARGET} apt-get -y --allow-unauthenticated install gstreamer1.0-x 
gstreamer1.0-tools gstreamer1.0-plugins-good gstreamer1.0-plugins-bad 
gstreamer1.0-alsa
exit 0

Then I run make systemd:

TARGET  := $(TARGET_DIR)
USERDIR := $(CURDIR)/..
SYSTEMD_DIR := $(CURDIR)

.PHONY: systemd

systemd: CC =

systemd:
sudo chroot $(TARGET) apt-get install -y --allow-unauthenticated 
dpkg-dev aptitude
mkdir -p $(SYSTEMD_DIR)/.build/src
mkdir -p $(SYSTEMD_DIR)/.build/result
mkdir -p $(SYSTEMD_DIR)/.build/aptcache
mkdir -p $(SYSTEMD_DIR)/.build/build
if [ ! -d $(TARGET)/var/cache/apt/archives ]; then\
 sudo mkdir -p $(TARGET)/var/cache/apt/archives;\
fi
cd $(SYSTEMD_DIR);\
tar -xvf systemd_232.tar.gz -C $(SYSTEMD_DIR)/.build/src;\
cd $(SYSTEMD_DIR)/.build/src/systemd-232;\
quilt import $(SYSTEMD_DIR)/patches/new-ouput-format-precise-iso.patch;\
pdebuild --buildresult $(SYSTEMD_DIR)/.build/result -- --no-targz 
--distribution stretch --architecture armhf --aptcache 
$(SYSTEMD_DIR)/.build/aptcache --buildplace $(TARGET) --logfile 
$(SYSTEMD_DIR)/log


systemd_232.tar.gz was done with command:
tar cfz systemd_232.tar.gz systemd_232.orig.tar.gz systemd_232-25+deb9u1.dsc 
systemd_232-25+deb9u1.debian.tar.xz systemd-232

I cross-compile the systemd for armhf with debian 9 stretch from:

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.1 LTS"
NAME="Ubuntu"
VERSION="16.04.1 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.1 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/;
SUPPORT_URL="http://help.ubuntu.com/;
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
UBUNTU_CODENAME=xenial

The compilation stops on override_dh_auto_test. The tests that fail are:

FAIL: test-loopback
FAIL: test-path-util
FAIL: test-util
FAIL: test-process-util
FAIL: test-fileio
FAIL: test-sigbus
FAIL: test-bus-creds
FAIL: test-netlink
FAIL: test-local-addresses
FAIL: test-journal-send
FAIL: test-compress
FAIL: test-network
FAIL test-bus-creds (exit status: 134)
FAIL test-compress (exit status: 134)
FAIL test-fileio (exit status: 134)
FAIL test-journal-send (exit status: 134)
FAIL test-local-addresses (exit status: 134)
FAIL test-loopback (exit status: 1)
FAIL test-netlink (exit status: 134)
FAIL test-network (exit status: 134)
FAIL test-path-util (exit status: 134)
FAIL test-process-util (exit status: 134)
FAIL test-sigbus (exit status: 139)
FAIL: test-loopback
FAIL test-loopback (exit status: 1)
FAIL: test-path-util
FAIL test-path-util (exit status: 134)
FAIL: test-util
FAIL test-util (exit status: 134)
FAIL: test-process-util
FAIL test-process-util (exit status: 134)
FAIL: test-fileio
FAIL test-fileio (exit status: 134)
FAIL: test-sigbus
FAIL test-sigbus (exit status: 139)
FAIL: test-bus-creds
FAIL test-bus-creds (exit status: 134)
FAIL: test-netlink
FAIL test-netlink (exit status: 134)
FAIL: test-local-addresses
FAIL test-local-addresses (exit status: 134)
FAIL: test-journal-send
FAIL test-journal-send (exit status: 134)
FAIL: test-compress
FAIL test-compress (exit status: 134)
FAIL: test-network
FAIL test-network (exit status: 134)
FAIL test-util (exit status: 134)

Here is the piece of log:

 test-loopback.log 
Unsupported setsockopt level=270 optname=3
loopback: Protocol not available
FAIL test-loopback (exit status: 1)

 test-path-util.log 
Found container virtualization none
---/a/b/c/d---
---/a/b/c---
---/a/b---
---/a---
--
---/a/b/c---
---/a/b---
---/a---
--
Assertion 'path_is_mount_point("/sys", AT_SYMLINK_FOLLOW) > 0' failed at 
../src/test/test-path-util.c:349, function test_path_is_mount_point(). Aborting.
/bin/sh
/build/systemd-232/build-deb/.libs/lt-test-path-util
/bin/sh
qemu: uncaught target signal 6 (Aborted) - core dumped
FAIL test-path-util (exit status: 134)

 test-util.log 
Executing /tmp/test-readlink_and_make_absolute-hi.Xqgxb21/script2
Executing

Processed: Re: diaspora: fails on being triggered

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

> tag 866877 + patch
Bug #866877 [diaspora] diaspora: fails on being triggered
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#853782: marked as done (ipmitool: Please migrate to openssl1.1 in buster)

Your message dated Wed, 6 Dec 2017 12:34:56 +0100
with message-id <1b71db21-1b66-da96-1e29-f6608c5d5...@debian.org>
and subject line Looks like fixed in stable.
has caused the Debian Bug report #853782,
regarding ipmitool: Please migrate to openssl1.1 in buster
to be marked as done.

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

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

--
853782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853782
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ipmitool
Version: 1.8.17-1
Severity: important
Control: block 827061 by -1

Hi,

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

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

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

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

Kurt
--- End Message ---
--- Begin Message ---
Reading debian/changelog from version 1.8.18-4:

* Migrate to OpenSSL1.1 (Closes_# 853782):
- New debian/patches/0120-openssl1.1.patch:
+ Cherry-picked from upstream.
- debian/control:
+ Switch Build-Depends from libssl1.0-dev to
libssl-dev to build against OpenSSL 1.1.

So, this has been fixed, but the changelog didn't close the bug properly
due to a syntax typo. I'm therefore hereby closing this bug.

Cheers,

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

Bug#883621: marked as pending

2017-12-06 Thread Thomas Goirand

tag 883621 pending
thanks

Hello,

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


https://anonscm.debian.org/cgit/openstack/services/nova.git/commit/?id=e515b9e

---
commit e515b9ec41d5a63e38d2a3b222eda67601aa1162
Author: Thomas Goirand 
Date:   Wed Dec 6 12:27:47 2017 +0100

  * CVE-2017-17051/OSSA-2017-005.1 (errata for 
CVE-2017-16239/OSSA-2017-005):
Nova Filter Scheduler bypass through rebuild action. Apply upstream 
patch:
Refined fix for validating image on rebuild (Closes: #883621).

diff --git a/debian/changelog b/debian/changelog
index 0448ebc..7df7e57 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+nova (2:16.0.3-5) unstable; urgency=high
+
+  * CVE-2017-17051/OSSA-2017-005.1 (errata for CVE-2017-16239/OSSA-2017-005):
+Nova Filter Scheduler bypass through rebuild action. Apply upstream patch:
+Refined fix for validating image on rebuild (Closes: #883621).
+
+ -- Thomas Goirand   Wed, 06 Dec 2017 12:24:45 +0100
+
 nova (2:16.0.3-4) unstable; urgency=medium
 
   * Using --paste-logger when starting uwsgi for placement-api, and runtime

Processed: Bug#883621 marked as pending

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

> tag 883621 pending
Bug #883621 [src:nova] nova: CVE-2017-17051: Nova FilterScheduler doubles 
resource allocations during rebuild with new image
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: severity of 882693 is grave