Bug#863886: closing 863886, closing 863886

[Salvatore Bonaccorso]

close 863886 0.13-4
close 863886 0.13-4~deb8u1
thanks

Processed: closing 863886, closing 863886

[Debian Bug Tracking System]

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

> close 863886 0.13-4
Bug #863886 [jbig2dec] jbig2dec: CVE-2016-8729
Marked as fixed in versions jbig2dec/0.13-4.
Bug #863886 [jbig2dec] jbig2dec: CVE-2016-8729
Marked Bug as done
> close 863886 0.13-4~deb8u1
Bug #863886 {Done: Salvatore Bonaccorso } [jbig2dec] 
jbig2dec: CVE-2016-8729
Marked as fixed in versions jbig2dec/0.13-4~deb8u1.
Bug #863886 {Done: Salvatore Bonaccorso } [jbig2dec] 
jbig2dec: CVE-2016-8729
Bug 863886 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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

Bug#853599: opensurgsim: ftbfs with GCC-7

[Paul Novotny]

Hi Andreas, sorry about my radio silence. I'll take a look.
-Paul

On Wed, Sep 20, 2017, at 03:56 AM, Andreas Tille wrote:
> Hi Paul,
> 
> that's the last open gcc-7 bug of the Debian Med team.  Could you please
> have a look (or at least signal that you will not be able to care about
> it)?
> 
> Kind regards
> 
>  Andreas.
> 
> On Tue, Jan 31, 2017 at 09:34:51AM +, Matthias Klose wrote:
> > Package: src:opensurgsim
> > Version: 0.7.0-5
> > Severity: normal
> > Tags: sid buster
> > User: debian-...@lists.debian.org
> > Usertags: ftbfs-gcc-7
> > 
> > Please keep this issue open in the bug tracker for the package it
> > was filed for.  If a fix in another package is required, please
> > file a bug for the other package (or clone), and add a block in this
> > package. Please keep the issue open until the package can be built in
> > a follow-up test rebuild.
> > 
> > The package fails to build in a test rebuild on at least amd64 with
> > gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
> > severity of this report may be raised before the buster release.
> > There is no need to fix this issue in time for the stretch release.
> > 
> > The full build log can be found at:
> > http://people.debian.org/~doko/logs/gcc7-20170126/opensurgsim_0.7.0-5_unstable_gcc7.log
> > The last lines of the build log are at the end of this report.
> > 
> > To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
> > or install the gcc, g++, gfortran, ... packages from experimental.
> > 
> >   apt-get -t=experimental install g++ 
> > 
> > Common build failures are new warnings resulting in build failures with
> > -Werror turned on, or new/dropped symbols in Debian symbols files.
> > For other C/C++ related build failures see the porting guide at
> > http://gcc.gnu.org/gcc-7/porting_to.html
> > 
> > [...]
> > [ RUN  ] AllDynamicVectorTests/2.addSubVector
> > [   OK ] AllDynamicVectorTests/2.addSubVector (0 ms)
> > [ RUN  ] AllDynamicVectorTests/2.addSubVectorBlocks
> > [   OK ] AllDynamicVectorTests/2.addSubVectorBlocks (0 ms)
> > [ RUN  ] AllDynamicVectorTests/2.setSubVector
> > [   OK ] AllDynamicVectorTests/2.setSubVector (1 ms)
> > [ RUN  ] AllDynamicVectorTests/2.getSubVector
> > [   OK ] AllDynamicVectorTests/2.getSubVector (0 ms)
> > [ RUN  ] AllDynamicVectorTests/2.getSubVectorBlocks
> > [   OK ] AllDynamicVectorTests/2.getSubVectorBlocks (0 ms)
> > [--] 6 tests from AllDynamicVectorTests/2 (1 ms total)
> > 
> > [--] Global test environment tear-down
> > [==] 896 tests from 116 test cases ran. (7703 ms total)
> > [  PASSED  ] 889 tests.
> > [  FAILED  ] 7 tests, listed below:
> > [  FAILED  ] UnalignedMatrixTests/0.DefaultConstructorInitialization, where 
> > TypeParam = Eigen::Matrix
> > [  FAILED  ] UnalignedMatrixTests/2.DefaultConstructorInitialization, where 
> > TypeParam = Eigen::Matrix
> > [  FAILED  ] UnalignedMatrixTests/3.DefaultConstructorInitialization, where 
> > TypeParam = Eigen::Matrix
> > [  FAILED  ] UnalignedMatrixTests/4.DefaultConstructorInitialization, where 
> > TypeParam = Eigen::Matrix
> > [  FAILED  ] UnalignedMatrixTests/5.DefaultConstructorInitialization, where 
> > TypeParam = Eigen::Matrix
> > [  FAILED  ] UnalignedVectorTests/4.DefaultConstructorInitialization, where 
> > TypeParam = Eigen::Matrix
> > [  FAILED  ] UnalignedVectorTests/6.DefaultConstructorInitialization, where 
> > TypeParam = Eigen::Matrix
> > 
> >  7 FAILED TESTS
> > 
> > 10/15 Test  #2: SurgSimCollisionTest .   Passed8.57 sec
> > 11/15 Test #14: SurgSimParticlesTest .   Passed   14.07 sec
> > 12/15 Test  #1: SurgSimBlocksTest    Passed   15.19 sec
> > 13/15 Test #11: SurgSimGraphicsTest ..   Passed   20.38 sec
> > 14/15 Test #10: SurgSimFrameworkTest .   Passed   45.04 sec
> > 15/15 Test #15: SurgSimPhysicsTest ...   Passed   91.00 sec
> > 
> > 93% tests passed, 1 tests failed out of 15
> > 
> > Total Test time (real) =  91.03 sec
> > 
> > The following tests FAILED:
> >  13 - SurgSimMathTest (Failed)
> > Errors while running CTest
> > Makefile:75: recipe for target 'test' failed
> > make[2]: *** [test] Error 8
> > make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> > dh_auto_test: make -j64 test ARGS+=-j64 returned exit code 2
> > debian/rules:39: recipe for target 'override_dh_auto_test' failed
> > make[1]: *** [override_dh_auto_test] Error 2
> > make[1]: Leaving directory '/<>'
> > debian/rules:7: recipe for target 'build' failed
> > make: *** [build] Error 2
> > dpkg-buildpackage: error: debian/rules build gave error exit status 2
> > 
> > ___
> > Debian-med-packaging mailing list
> > debian-med-packag...@lists.alioth.debian.org
> > 

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

[Nobuhiro Iwamatsu]

Hi,

2017-09-21 8:20 GMT+09:00 Matthias Klumpp :
> 2017-09-20 5:28 GMT+02:00 Nobuhiro Iwamatsu :
>> Hi,
>>
>> sambamba package has not fixed this problem with ldc 1:1.4.0-1.
>> Also, I confirmed that diet-ng fixed this problem.
>
> This is a different bug:
> https://github.com/ldc-developers/ldc/issues/2300#issuecomment-330947562
>

I see. Thanks.

Best regards,
  Nobuhiro

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



-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6

Processed: gqrx-sdr: gqrx fails to start looking for old version of boost

[Debian Bug Tracking System]

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

> tags 870094 +moreinfo +unreproducible
Bug #870094 [gqrx-sdr] gqrx-sdr: gqrx fails to start looking for old version of 
boost
Added tag(s) moreinfo.
Bug #870094 [gqrx-sdr] gqrx-sdr: gqrx fails to start looking for old version of 
boost
Added tag(s) unreproducible.
> severity 870094 normal
Bug #870094 [gqrx-sdr] gqrx-sdr: gqrx fails to start looking for old version of 
boost
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

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

Processed: tagging 876305, retitle 869783 to nvidia-driver: CVE-2017-6257, CVE-2017-6259, tagging 871046

[Debian Bug Tracking System]

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

> tags 876305 + sid buster
Bug #876305 {Done: Ralf Treinen } [src:polygen] polygen: FTBFS 
with ocaml 4.05.0
Added tag(s) sid and buster.
> retitle 869783 nvidia-driver: CVE-2017-6257, CVE-2017-6259
Bug #869783 {Done: Andreas Beckmann } [nvidia-driver] Security 
- upgrade NVidia driver to 375.82 in stable.
Changed Bug title to 'nvidia-driver: CVE-2017-6257, CVE-2017-6259' from 
'Security - upgrade NVidia driver to 375.82 in stable.'.
> tags 871046 + sid buster
Bug #871046 {Done: Miguel Landaeta } [jruby] ruby-json 
FTBFS: It seems your ruby installation is missing psych (for YAML output).
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Bug#876414: nvidia-kernel-dkms: security issues CVE-2017-6266, CVE-2017-6267, CVE-2017-6272

[Luca Boccassi]

On Fri, 2017-09-22 at 00:15 +0200, Andreas Beckmann wrote:
> On 09/21/2017 11:55 PM, Luca Boccassi wrote:
> > 3 CVEs affecting the NVIDIA proprietary kernel modules have been
> > published [1]:
> > 
> > CVE-2017-6266, CVE-2017-6267, CVE-2017-6272
> > 
> > All affecting only the 384 branch, and fixed in the 384.90 release.
> 
> Since NVIDIA published these today, but nothing for the 304xx/340xx
> branches, the recent legacy releases don't seem to be relevant
> security
> wise ... so nothing too urgent.

Yes, that seems to be the case.

I've done all the updates in the 384 branches, it was pretty straight
forward.

> Did you have time to test the 375 trunk packaging on stretch? I think
> it
> should work there out-of-the box after the recent changes ... I'm
> thinking about backporting -4 once this reched testing, to get
> exposure
> to a wider audience, since at some point we will need to put a 384 or
> 375 release with larger packaging changes into stretch-pu.
> And thereafter moving to 384 in sid (via 378 and 381 first)

Yes it seems to be working fine, tried a couple of games, thanks for
the fixes.

The plan sounds good - it looks like 375 is going out of support and
there's no sign of a new fork.

Kind regards,
Luca Boccassi

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

Bug#876416: libzstd FTBFS on mips(el): Allocation error : not enough memory

[Graham Inggs]

Source: libzstd
Version: 1.3.1+dfsg-1
Severity: serious

Hi Maintainer

Builds of libzstd/1.3.1+dfsg-1 FTBFS on mips and mipsel where they
were successful in the past.


/*stdin*\:  5.90%   (9900 => 5842431 bytes, /*stdout*\)
roundTripTest: ./datagen -g60 -P99 |  ../programs/zstd -v1 -T2
|  ../programs/zstd -d

*** zstd command line interface 32-bits v1.3.1, by Yann Collet ***

Read : 6 MB
Read : 12 MB
Read : 16 MB
...
Read : 5711 MB
Read : 5716 MB
Read : 5720 MB


/*stdin*\:  9.40%   (60 => 563851359 bytes, /*stdout*\)
roundTripTest: ./datagen -g15 -P97 |  ../programs/zstd -v1
-T999 |  ../programs/zstd -d

*** zstd command line interface 32-bits v1.3.1, by Yann Collet ***
zstd: error 11 : Allocation error : not enough memory
zstd: /*stdin*\: unexpected end of file
Files tmp1 and tmp2 differ
Makefile:260: recipe for target 'zstd-playTests' failed


Regards
Graham

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

[Debian Bug Tracking System]

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

> forwarded 876353 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82284
Bug #876353 [gccgo-7] gccgo-7: unhandled signal 11 at s390x/ppc64
Changed Bug forwarded-to-address to 
'https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82284' from 
'https://github.com/golang/go/issues/21972'.
> thanks
Stopping processing here.

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

Processed: bug 876353 is forwarded to https://github.com/golang/go/issues/21972

[Debian Bug Tracking System]

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

> forwarded 876353 https://github.com/golang/go/issues/21972
Bug #876353 [gccgo-7] gccgo-7: unhandled signal 11 at s390x/ppc64
Changed Bug forwarded-to-address to 'https://github.com/golang/go/issues/21972' 
from 'https://gcc.gnu.org/PR82284'.
> thanks
Stopping processing here.

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

Bug#875423: [Pkg-openssl-devel] Bug#875423: openssl: Please re-enable TLS 1.0 and TLS 1.1 (at least in testing)

[Kurt Roeckx]

On Mon, Sep 11, 2017 at 12:30:30PM +0200, Raphael Hertzog wrote:
> But in Debian testing, we have real end-users (direct and through
> "rolling" derivatives) and they should not have to be impacted by this
> experiment IMO.

I have to admit that I didn't consider derivatives that take a
snapshot of testing, and we also seem to have a large amount of
people that do use testing. My intention was to target the more
advanced users, and having it in testing might be affecting more
people than I thought.

So I am considering to only disable it in unstable and not in
testing.

I'm actually surprised how few things broke.


Kurt

Bug#876414: nvidia-kernel-dkms: security issues CVE-2017-6266, CVE-2017-6267, CVE-2017-6272

[Andreas Beckmann]

On 09/21/2017 11:55 PM, Luca Boccassi wrote:
> 3 CVEs affecting the NVIDIA proprietary kernel modules have been
> published [1]:
> 
> CVE-2017-6266, CVE-2017-6267, CVE-2017-6272
> 
> All affecting only the 384 branch, and fixed in the 384.90 release.
Since NVIDIA published these today, but nothing for the 304xx/340xx
branches, the recent legacy releases don't seem to be relevant security
wise ... so nothing too urgent.

Did you have time to test the 375 trunk packaging on stretch? I think it
should work there out-of-the box after the recent changes ... I'm
thinking about backporting -4 once this reched testing, to get exposure
to a wider audience, since at some point we will need to put a 384 or
375 release with larger packaging changes into stretch-pu.
And thereafter moving to 384 in sid (via 378 and 381 first)


Andreas

Bug#875423: [Pkg-openssl-devel] Bug#875423: openssl: Please re-enable TLS 1.0 and TLS 1.1 (at least in testing)

[Kurt Roeckx]

On Mon, Sep 11, 2017 at 11:33:22AM +0200, Raphaël Hertzog wrote:
> Or at least I would like a system-wide flag (in a configuration file?) to
> let me re-enable old protocols easily.

It was my understanding that other people also prefered to do this
on a per package level and not system wide.


Kurt

Bug#876414: nvidia-kernel-dkms: security issues CVE-2017-6266, CVE-2017-6267, CVE-2017-6272

[Luca Boccassi]

Package: nvidia-kernel-dkms
Version: 384.69-1
Severity: grave

3 CVEs affecting the NVIDIA proprietary kernel modules have been
published [1]:

CVE-2017-6266, CVE-2017-6267, CVE-2017-6272

All affecting only the 384 branch, and fixed in the 384.90 release.

Kind regards,
Luca Boccassi

[1] http://nvidia.custhelp.com/app/answers/detail/a_id/4544

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

Processed: severity of 876070 is normal

[Debian Bug Tracking System]

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

> severity 876070 normal
Bug #876070 {Done: Michael Biebl } [libavahi-core7] 
libavahi-core7: Does not install
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

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

Bug#876342: [Pkg-utopia-maintainers] Bug#876342: Bug#876342: avahi-daemon: upgrade failed: failed to configure

[Michael Biebl]

Am 21.09.2017 um 20:05 schrieb Vincent Lefevre:
> On 2017-09-21 18:47:40 +0200, Michael Biebl wrote:
>> Can you provide steps how to reproduce the issue? I've upgraded avahi on
>> several systems and did not run into this particular problem.
> 
> I don't know whether this is reproducible, but this was just an
> upgrade with aptitude. 

Not sure what to do about this bug report then aside from closing it.
The given information at least is not sufficient to further debug this.



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Processed: severity of 876342 is normal

[Debian Bug Tracking System]

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

> severity 876342 normal
Bug #876342 [avahi-daemon] avahi-daemon: upgrade failed: failed to configure
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

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

[Clint Adams]

On Wed, Sep 20, 2017 at 12:16:13AM +0200, Sacha Delanoue wrote:
> I tried to install libghc-xmonad-contrib-dev by doing
> `apt install libghc-xmonad-contrib-dev` on an up-to-date 9.1 Debian.
> The install failed with the following information:
> 
> The following packages have unmet dependencies:
>  libghc-xmonad-contrib-dev : Depends: libghc-x11-xft-dev-0.3.1-c557c
> E: Unable to correct problems, you have held broken packages.
> 
> I am no expert in Debian, but a search on the Internet lead me to this:
> https://unix.stackexchange.com/a/392888 stating that this kind of errors
> in expected in Sid. But since I am using stable I reported it.

Please reply with the output of

dpkg -s libghc-x11-xft-dev | grep -e '^Status' -e '^Version' -e '^Provides'

Bug#875423: openssl: Please re-enable TLS 1.0 and TLS 1.1 (at least in testing)

[Sebastian Andrzej Siewior]

On 2017-09-11 12:30:30 [+0200], Raphael Hertzog wrote:
> Yes, I'm aware of that but Kurt never said that he would be willing to
> back off from completely disabling it before the buster release and
> I don't see any benefit in modifying all server applications to re-enable
> the protocols that we want to support out-of-the box because there 
> are (outside of Debian) old applications that will have to connect to
> those servers.

My understanding is that it will stay as-is and every package that needs
TLS < 1.2 needs to add an option and the metioned function to use the
lower TLS version.
The changes Kurt asked about is something that openssl upstream supports
and is something that openssl 1.1 considers the right way of doing
things (in contrast to the disable TLS-version X thingy which are marked
deprecated or going to…).

> I understand we need to fix the client applications that we ship in Debian
> so that they work with TLS 1.2-only servers and for this it might be
> useful to disable TLS 1.0 and TLS 1.1 by default in unstable for a while.

as I said, TLS 1.[01] is supported in unstable if the
*set_min_proto_version() is used. I think in the meantime offline imap
has been fixed and I sent something for dovecot (but know about its
status).

> But in Debian testing, we have real end-users (direct and through
> "rolling" derivatives) and they should not have to be impacted by this
> experiment IMO.

So what problems do those users see? If the package lacks 1.2 support
then it should be reported & fixed. If the package requries <1.2 support
because the remote side can't be changed then this should reported and
patched as well.
Feel free to Cc the list so I can look and maybe make a patch if I have
some spare time. I personaly don't see a reason to keep this bug open
since it is unlikely that things change here. Also it is unwise to make
such a change two days before the release of Buster. *Now* we have the
time to act.

> Cheers,

Sebastian

Bug#871831: mono-tools: Depends on libwebkit1.1-cil which is deprecated

[Jeremy Bicha]

On Thu, Sep 21, 2017 at 2:21 PM, Jo Shields  wrote:
> Go ahead and NMU.

Here's 2 git patches to apply on top of the previous one. I'll upload shortly.

There are 2 rdepends for monodoc-browser: monodoc-manual (from
src:mono) and gmime2.6. I'll file the gmime2.6 bug.

Thanks,
Jeremy Bicha
From fbcd6720134f989ccf6926142dc0c9c4997c9bbd Mon Sep 17 00:00:00 2001
From: Jeremy Bicha 
Date: Thu, 21 Sep 2017 14:54:41 -0400
Subject: [PATCH 1/2] Drop monodoc-browser since it won't run without webkit1

---
 debian/control | 24 
 1 file changed, 12 insertions(+), 12 deletions(-)

diff --git a/debian/control b/debian/control
index 2ba1013..0a20b96 100644
--- a/debian/control
+++ b/debian/control
@@ -24,18 +24,18 @@ Standards-Version: 3.9.2
 Vcs-Git: git://git.debian.org/git/pkg-mono/packages/mono-tools.git
 Vcs-Browser: http://git.debian.org/?p=pkg-mono/packages/mono-tools.git
 
-Package: monodoc-browser
-Provides: monodoc-viewer
-Replaces: monodoc-base (<< 2.10.8.1-3)
-Breaks: monodoc-base (<< 2.10.8.1-3)
-Architecture: all
-Depends: ${cli:Depends}, monodoc-manual, ${misc:Depends}
-Description: MonoDoc GTK+ based viewer
- The MonoDoc Project is the documentation framework of the Mono project which
- provides detailed API documentation for all Mono components and the Mono CLI
- implementation.
- .
- This package contains the GTK+ based viewer of the Mono documentation.
+#Package: monodoc-browser
+#Provides: monodoc-viewer
+#Replaces: monodoc-base (<< 2.10.8.1-3)
+#Breaks: monodoc-base (<< 2.10.8.1-3)
+#Architecture: all
+#Depends: ${cli:Depends}, monodoc-manual, ${misc:Depends}
+#Description: MonoDoc GTK+ based viewer
+# The MonoDoc Project is the documentation framework of the Mono project which
+# provides detailed API documentation for all Mono components and the Mono CLI
+# implementation.
+# .
+# This package contains the GTK+ based viewer of the Mono documentation.
 
 Package: mono-tools-gui
 Architecture: all
-- 
2.14.1

From a0012dd5db28de616d1202c0209fc411d7a90c81 Mon Sep 17 00:00:00 2001
From: Jeremy Bicha 
Date: Thu, 21 Sep 2017 14:57:29 -0400
Subject: [PATCH 2/2] Finalize changelog

---
 debian/changelog | 9 +
 1 file changed, 9 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index af1228a..357d7b4 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+mono-tools (4.2-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * [a4960e8] Don't Build-Depend on libwebkit-cil-dev (Closes: #871831)
+  * [fbcd672] Drop ilcontrast and monodoc-browser since they won't work
+without webkit1
+
+ -- Jeremy Bicha   Thu, 21 Sep 2017 13:32:38 -0400
+
 mono-tools (4.2-2) unstable; urgency=medium
 
   * [9adcc51] Don't depend on gmcs any more
-- 
2.14.1

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

[Uwe Kleine-König]

Control: clone 873508 -1
Control: retitle -1 Please use cgcc to check hosted C code instead of sparse
Control: severity -1 normal
Control: reassign -1 horst

On Fri, Sep 01, 2017 at 09:46:44AM +0200, Uwe Kleine-König wrote:
> @anarcat: Given that cgcc seems to work, would you agree to apply the
> following patch to horst:
> 
> diff --git a/Makefile b/Makefile
> index 4f924fa..d563652 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -110,7 +110,7 @@ $(NAME): $(OBJS)
>  $(OBJS): .buildflags
>  
>  check:
> - sparse $(CFLAGS) *.[ch]
> + cgcc -no-compile $(CFLAGS) *.[ch]
>  
>  clean:
>   -rm -f *.o radiotap/*.o *~
> 

In the meantime I learned from upstream that sparse is not expected to
grok arbitrary hosted code. For that it is needed to use the cgcc
wrapper to handle the required cpp symbols. That it works on some
architectures with plain sparse is mostly luck.

I still expect some platforms to fail with the wrapper, too, because
cgcc doesn't know about all platforms yet. But I intend to upload a new
sparse package soon that includes a build time check for that, and the
respective fixes are easy.

> and downgrade the bug to "important"? That would be a compromise that
> buys us a bit of time.

I'd say sparse failing on hosted code isn't "important", but cgcc should
have all necessary definitions for Debian platforms. So I'm keeping this
bug at important and intend to close it once all platforms are known to
it.

Best regards
Uwe


signature.asc
Description: PGP signature

Processed: Re: Bug#873508: sparse test failures on ppc32le (and other not so common archs)

[Debian Bug Tracking System]

Processing control commands:

> clone 873508 -1
Bug #873508 [src:sparse] parsing horst source code fails on s390x and ppc64el
Bug 873508 cloned as bug 876402
> retitle -1 Please use cgcc to check hosted C code instead of sparse
Bug #876402 [src:sparse] parsing horst source code fails on s390x and ppc64el
Changed Bug title to 'Please use cgcc to check hosted C code instead of sparse' 
from 'parsing horst source code fails on s390x and ppc64el'.
> severity -1 normal
Bug #876402 [src:sparse] Please use cgcc to check hosted C code instead of 
sparse
Severity set to 'normal' from 'serious'
> reassign -1 horst
Bug #876402 [src:sparse] Please use cgcc to check hosted C code instead of 
sparse
Bug reassigned from package 'src:sparse' to 'horst'.
No longer marked as found in versions sparse/0.5.0-4.
Ignoring request to alter fixed versions of bug #876402 to the same values 
previously set

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

Bug#876400: php-horde-image: CVE-2017-14650: remote code execution n _raw() via $index parameter

[Salvatore Bonaccorso]

Source: php-horde-image
Version: 2.0.1-1
Severity: grave
Tags: patch upstream security

Hi,

the following vulnerability was published for php-horde-image.

CVE-2017-14650[0]:
| A Remote Code Execution vulnerability has been found in the Horde_Image
| library when using the "Im" backend that utilizes ImageMagick's
| "convert" utility. It's not exploitable through any Horde application,
| because the code path to the vulnerability is not used by any Horde
| code. Custom applications using the Horde_Image library might be
| affected. This vulnerability affects all versions of Horde_Image from
| 2.0.0 to 2.5.1, and is fixed in 2.5.2. The problem is missing input
| validation of the index field in _raw() during construction of an
| ImageMagick command line.

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-14650
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14650
[1] 
https://github.com/horde/horde/commit/eb3afd14c22c77ae0d29e2848f5ac726ef6e7c5b

Regards,
Salvatore

Bug#871831: mono-tools: Depends on libwebkit1.1-cil which is deprecated

[Jo Shields]

Go ahead and NMU.


The problem with libwebkit2gtk-4.0-37 is it's a wrapper for allowing Gtk2 
plugins in a Gtk3 browser - it's not a way for Gtk2 apps to continue to use 
Webkit


Sent from Outlook


From: Jeremy Bicha 
Sent: 21 September 2017 14:03:17
To: 871...@bugs.debian.org; Jo Shields
Subject: Re: mono-tools: Depends on libwebkit1.1-cil which is deprecated

Just to be clear, monodoc won't run if it's not built against
webkitgtk (or one of a few other dependencies that aren't in Debian
any more) so we should drop the monodoc package too.

Thanks,
Jeremy Bicha

Bug#876398: mysqltest can't read config proberly

[Jörg Frings-Fürst]

Package: mariadb-test
Version: 10.1.26-0+deb9u1
Severity: grave

Hello,


if I run mysqltest I get:

> mysqltest
mysqltest: unknown variable 'default-character-set=utf8mb4'

mysqltest stops after that message and isn't useable.

CU
Jörg



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

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

Versions of packages mariadb-test depends on:
ii  libaio1  0.3.110-3
ii  libc62.24-11+deb9u1
ii  libmariadbclient18   10.1.26-0+deb9u1
ii  libpcre3 2:8.39-3
ii  libstdc++6   6.3.0-18
ii  mariadb-client-10.1  10.1.26-0+deb9u1
ii  mariadb-server-10.1  10.1.26-0+deb9u1
ii  mariadb-test-data10.1.26-0+deb9u1
ii  zlib1g   1:1.2.8.dfsg-5

mariadb-test recommends no packages.

Versions of packages mariadb-test suggests:
ii  patch  2.7.5-1+b2

-- no debconf information

Processed: closing 823511

[Debian Bug Tracking System]

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

> # php-zend-diactoros and php-symfony-psr-http-message-bridge currently in NEW 
> depend on php-psr-http-message
> close 823511
Bug #823511 [php-psr-http-message] Useless in Debian
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#876342: [Pkg-utopia-maintainers] Bug#876342: avahi-daemon: upgrade failed: failed to configure

[Vincent Lefevre]

On 2017-09-21 18:47:40 +0200, Michael Biebl wrote:
> Can you provide steps how to reproduce the issue? I've upgraded avahi on
> several systems and did not run into this particular problem.

I don't know whether this is reproducible, but this was just an
upgrade with aptitude. Here's the Aptitude log report:

Aptitude 0.8.9: log report
Thu, Sep 21 2017 10:15:18 +0200

  IMPORTANT: this log only lists intended actions; actions which fail
  due to dpkg problems may not be completed.

Will install 221 packages, and remove 1 packages.
522 MB of disk space will be freed

[REMOVE, NOT USED] libqpdf17:amd64 6.0.0-2
[HOLD, DEPENDENCIES] clang-format-4.0:amd64 1:4.0.1-3
[HOLD, DEPENDENCIES] gstreamer1.0-libav:amd64 1.12.2-1
[HOLD, DEPENDENCIES] gstreamer1.0-plugins-base:amd64 1.12.2-1
[HOLD, DEPENDENCIES] gstreamer1.0-plugins-good:amd64 1.12.2-1
[HOLD, DEPENDENCIES] gstreamer1.0-x:amd64 1.12.2-1
[HOLD, DEPENDENCIES] libclang-common-3.9-dev:amd64 1:3.9.1-13
[HOLD, DEPENDENCIES] libclang-common-4.0-dev:amd64 1:4.0.1-3
[HOLD, DEPENDENCIES] libclang1-3.9:amd64 1:3.9.1-13
[HOLD, DEPENDENCIES] libclang1-4.0:amd64 1:4.0.1-3
[HOLD, DEPENDENCIES] libclang1-5.0:amd64 1:5.0-1
[HOLD, DEPENDENCIES] libegl1-mesa:amd64 17.1.5-1
[HOLD, DEPENDENCIES] libegl1-mesa-dev:amd64 17.1.5-1
[HOLD, DEPENDENCIES] libfreetype6:amd64 2.6.3-3.2
[HOLD, DEPENDENCIES] libfreetype6-dev:amd64 2.6.3-3.2
[HOLD, DEPENDENCIES] libgbm1:amd64 17.1.5-1
[HOLD, DEPENDENCIES] libgl1-mesa-dev:amd64 17.1.5-1
[HOLD, DEPENDENCIES] libgl1-mesa-glx:amd64 17.1.5-1
[HOLD, DEPENDENCIES] libgl1-nvidia-glvnd-glx:amd64 375.82-1
[HOLD, DEPENDENCIES] libglapi-mesa:amd64 17.1.5-1
[HOLD, DEPENDENCIES] libgles2-mesa:amd64 17.1.5-1
[HOLD, DEPENDENCIES] libglx-nvidia0:amd64 375.82-1
[HOLD, DEPENDENCIES] libglx0-glvnd-nvidia:amd64 375.82-1
[HOLD, DEPENDENCIES] libgstreamer-plugins-base1.0-0:amd64 1.12.2-1
[HOLD, DEPENDENCIES] libgstreamer1.0-0:amd64 1.12.2-1
[HOLD, DEPENDENCIES] libjavascriptcoregtk-4.0-18:amd64 2.16.6-1
[HOLD, DEPENDENCIES] libllvm3.9:amd64 1:3.9.1-13
[HOLD, DEPENDENCIES] libllvm4.0:amd64 1:4.0.1-3
[HOLD, DEPENDENCIES] libllvm5.0:amd64 1:5.0-1
[HOLD, DEPENDENCIES] libnvidia-glcore:amd64 375.82-1
[HOLD, DEPENDENCIES] libnvidia-ml1:amd64 375.82-1
[HOLD, DEPENDENCIES] libosmesa6:amd64 17.1.5-1
[HOLD, DEPENDENCIES] libwayland-egl1-mesa:amd64 17.1.5-1
[HOLD, DEPENDENCIES] libwebkit2gtk-4.0-37:amd64 2.16.6-1
[HOLD, DEPENDENCIES] libwebkit2gtk-4.0-37-gtk2:amd64 2.16.6-1
[HOLD, DEPENDENCIES] linux-compiler-gcc-6-x86:amd64 4.12.6-1
[HOLD, DEPENDENCIES] linux-doc-4.12:amd64 4.12.6-1
[HOLD, DEPENDENCIES] linux-kbuild-4.12:amd64 4.12.6-1
[HOLD, DEPENDENCIES] linux-libc-dev:amd64 4.12.6-1
[HOLD, DEPENDENCIES] llvm-3.9:amd64 1:3.9.1-13
[HOLD, DEPENDENCIES] llvm-3.9-dev:amd64 1:3.9.1-13
[HOLD, DEPENDENCIES] llvm-3.9-runtime:amd64 1:3.9.1-13
[HOLD, DEPENDENCIES] llvm-4.0:amd64 1:4.0.1-3
[HOLD, DEPENDENCIES] llvm-4.0-dev:amd64 1:4.0.1-3
[HOLD, DEPENDENCIES] llvm-4.0-runtime:amd64 1:4.0.1-3
[HOLD, DEPENDENCIES] mesa-common-dev:amd64 17.1.5-1
[HOLD, DEPENDENCIES] nvidia-alternative:amd64 375.82-1
[HOLD, DEPENDENCIES] nvidia-legacy-check:amd64 375.82-1
[HOLD, DEPENDENCIES] nvidia-vdpau-driver:amd64 375.82-1
[INSTALL, DEPENDENCIES] libgdk-pixbuf2.0-bin:amd64 2.36.10-2
[INSTALL, DEPENDENCIES] libqpdf18:amd64 7.0.0-1
[INSTALL, DEPENDENCIES] libregexp-pattern-license-perl:amd64 3.0.31-3
[INSTALL, DEPENDENCIES] nmap-common:amd64 7.60+dfsg1-2
[HOLD] clang-3.9:amd64 1:3.9.1-13
[HOLD] clang-3.9-doc:amd64 1:3.9.1-13
[HOLD] clang-3.9-examples:amd64 1:3.9.1-13
[HOLD] clang-4.0:amd64 1:4.0.1-3
[HOLD] clang-4.0-doc:amd64 1:4.0.1-3
[HOLD] gir1.2-gst-plugins-base-1.0:amd64 1.12.2-1
[HOLD] gir1.2-gstreamer-1.0:amd64 1.12.2-1
[HOLD] gstreamer1.0-libav-dbg:amd64 1.12.2-1
[HOLD] libegl-nvidia0:amd64 375.82-1
[HOLD] libegl1-glvnd-nvidia:amd64 375.82-1
[HOLD] libgbm-dev:amd64 17.1.5-1
[HOLD] libgl1-glvnd-nvidia-glx:amd64 375.82-1
[HOLD] libgl1-mesa-dri:amd64 17.1.5-1
[HOLD] libgles-nvidia1:amd64 375.82-1
[HOLD] libgles-nvidia2:amd64 375.82-1
[HOLD] libgles1-glvnd-nvidia:amd64 375.82-1
[HOLD] libgles2-glvnd-nvidia:amd64 375.82-1
[HOLD] libgles2-mesa-dev:amd64 17.1.5-1
[HOLD] libgstreamer-plugins-base1.0-dev:amd64 1.12.2-1
[HOLD] libgstreamer1.0-0-dbg:amd64 1.12.2-1
[HOLD] libgstreamer1.0-dev:amd64 1.12.2-1
[HOLD] libnvidia-cfg1:amd64 375.82-1
[HOLD] libnvidia-eglcore:amd64 375.82-1
[HOLD] libopengl0-glvnd-nvidia:amd64 375.82-1
[HOLD] libxatracker2:amd64 17.1.5-1
[HOLD] linux-doc:amd64 4.12+84
[HOLD] linux-headers-amd64:amd64 4.12+84
[HOLD] linux-image-amd64:amd64 4.12+84
[HOLD] nvidia-driver:amd64 375.82-1
[HOLD] nvidia-driver-bin:amd64 375.82-1
[HOLD] nvidia-driver-libs:amd64 375.82-1
[HOLD] nvidia-egl-common:amd64 375.82-1
[HOLD] nvidia-egl-icd:amd64 375.82-1
[HOLD] nvidia-kernel-dkms:amd64 375.82-1
[HOLD] nvidia-kernel-support:amd64 375.82-1
[HOLD] nvidia-vulkan-common:amd64 375.82-1
[HOLD] nvidia-vulkan-icd:amd64 375.82-1
[HOLD] 

Bug#871831: mono-tools: Depends on libwebkit1.1-cil which is deprecated

[Jeremy Bicha]

Just to be clear, monodoc won't run if it's not built against
webkitgtk (or one of a few other dependencies that aren't in Debian
any more) so we should drop the monodoc package too.

Thanks,
Jeremy Bicha

Processed: forwarded GCC issue

[Debian Bug Tracking System]

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

> forwarded 876353 https://gcc.gnu.org/PR82284
Bug #876353 [gccgo-7] gccgo-7: unhandled signal 11 at s390x/ppc64
Set Bug forwarded-to-address to 'https://gcc.gnu.org/PR82284'.
> tags 876353 + upstream
Bug #876353 [gccgo-7] gccgo-7: unhandled signal 11 at s390x/ppc64
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package fwupd

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package fwupd
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #874521 (http://bugs.debian.org/874521)
> # Bug title: fwupd segfaults at start
> #  * https://github.com/hughsie/fwupd/issues/259
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 874521 + fixed-upstream
Bug #874521 [fwupd] fwupd segfaults at start
Added tag(s) fixed-upstream.
> usertags 874521 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#818616: marked as done (luajit: laujit segfaults on arm64)

[Debian Bug Tracking System]

Your message dated Thu, 21 Sep 2017 18:50:26 +0200
with message-id <1c5598ec-4693-ad52-0a33-cfe9034ec...@debian.org>
and subject line Re: luajit: laujit segfaults on arm64
has caused the Debian Bug report #818616,
regarding luajit: laujit segfaults on arm64
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.)


-- 
818616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818616
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: luajit
Version: 2.1.0~beta2+dfsg-1
Severity: important

Dear Maintainer,

Yay - luajit with arm64 support uploaded!

However, whilst it builds, it doesn't appear to work at all.

Running it gives an immediate segfault

I installed the debug version (thank you debian for automatic dbgsym
builds!) and got:
$ luajit
GNU gdb (Debian 7.10-1+b1) 7.10
...
Reading symbols from luajit...Reading symbols from 
/usr/lib/debug/.build-id/e0/82e0a7597824d1de104daad7beb534c4280041.debug...done.
done.
(gdb) directory src
(gdb) run
Starting program: /usr/bin/luajit 

Program received signal SIGSEGV, Segmentation fault.
getcurrenv (L=0xb7d80378, L=0xb7d80378) at lj_api.c:76
76return fn->c.gct == ~LJ_TFUNC ? tabref(fn->c.env) : tabref(L->env);

(gdb) info stack
#0  getcurrenv (L=0xb7d80378, L=0xb7d80378) at lj_api.c:76
#1  cpcall (L=0xb7d80378, func=0x404c08 , ud=0x0) at lj_api.c:1062
#2  0x004379d8 in lj_vm_cpcall () at buildvm_arm64.dasc:1182
#3  0x0042bc3c in lua_cpcall (L=L@entry=0xb7d80378, 
func=func@entry=0x404c08 , ud=ud@entry=0x0)
at lj_api.c:1079
#4  0x0040406c in main (argc=1, argv=0xf518) at luajit.c:564

I will investigate this further, but filing this bug for now in case
it's obvious to anyone else what's up. 



Kernel: Linux 3.18.0-rc3 (SMP w/6 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages luajit depends on:
ii  libc6 2.22-3
ii  libgcc1   1:5.3.1-8
ii  libluajit-5.1-2   2.1.0~beta2+dfsg-1
ii  libluajit-5.1-common  2.1.0~beta2+dfsg-1

luajit recommends no packages.

luajit suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
On Thu, 21 Sep 2017 15:15:24 +0100 Edmund Grimley Evans 
 wrote:
> I think this bug was fixed in 2.1.0~beta3. Can it be closed please?
> Any objections?

None, closing

G.

> 
> # tail -n 1 /proc/self/maps
> eb71-eb731000 rw-p  00:00 0  
> [stack]
> 
> # dpkg -i libluajit-5.1-2_2.1.0~beta2+dfsg-1_arm64.deb
> libluajit-5.1-common_2.1.0~beta2+dfsg-1_arm64.deb
> luajit_2.1.0~beta2+dfsg-1_arm64.deb
> ...
> # luajit -e 'print("x");'
> Segmentation fault (core dumped)
> 
> # dpkg -i libluajit-5.1-2_2.1.0~beta2+dfsg-3_arm64.deb
> libluajit-5.1-common_2.1.0~beta2+dfsg-3_arm64.deb
> luajit_2.1.0~beta2+dfsg-3_arm64.deb
> ...
> # luajit -e 'print("x");'
> Segmentation fault (core dumped)
> 
> # dpkg -i libluajit-5.1-2_2.1.0~beta3+dfsg-1_arm64.deb
> libluajit-5.1-common_2.1.0~beta3+dfsg-1_all.deb
> luajit_2.1.0~beta3+dfsg-1_arm64.deb
> # luajit -e 'print("x");'
> x
> 
> # dpkg -i libluajit-5.1-2_2.1.0~beta3+dfsg-2_arm64.deb
> libluajit-5.1-common_2.1.0~beta3+dfsg-2_all.deb
> luajit_2.1.0~beta3+dfsg-2_arm64.deb
> # luajit -e 'print("x");'
> x
> 
> 



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Processed: your mail

[Debian Bug Tracking System]

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

> notfound 873320 ettercap/1:0.8.2-6
Bug #873320 {Done: Gianfranco Costamagna } 
[src:ettercap] ettercap FTBFS with luajit 2.1
Ignoring request to alter found versions of bug #873320 to the same values 
previously set
> notfound 873320 ettercap/1:0.8.2-5
Bug #873320 {Done: Gianfranco Costamagna } 
[src:ettercap] ettercap FTBFS with luajit 2.1
Ignoring request to alter found versions of bug #873320 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: Re: [Pkg-utopia-maintainers] Bug#876342: avahi-daemon: upgrade failed: failed to configure

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo unreproducible
Bug #876342 [avahi-daemon] avahi-daemon: upgrade failed: failed to configure
Added tag(s) moreinfo and unreproducible.

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

Bug#876342: [Pkg-utopia-maintainers] Bug#876342: avahi-daemon: upgrade failed: failed to configure

[Michael Biebl]

Control: tags -1 moreinfo unreproducible

Am 21.09.2017 um 10:28 schrieb Vincent Lefevre:
> Package: avahi-daemon
> Version: 0.7-3
> Severity: grave
> Justification: renders package unusable
> 
> The upgrade of avahi-daemon failed:
> 
> Setting up avahi-daemon (0.7-3) ...
> Installing new version of config file /etc/avahi/avahi-daemon.conf ...
> Job for avahi-daemon.service failed because the control process exited with 
> error code.
> See "systemctl  status avahi-daemon.service" and "journalctl  -xe" for 
> details.
> invoke-rc.d: initscript avahi-daemon, action "restart" failed.
> ● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
>Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled; vendor 
> preset: enabled)
>Active: failed (Result: exit-code) since Thu 2017-09-21 10:21:56 CEST; 6ms 
> ago
>   Process: 740 ExecStart=/usr/sbin/avahi-daemon -s (code=exited, status=255)
>  Main PID: 740 (code=exited, status=255)
> 
> Sep 21 10:21:56 zira systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
> Sep 21 10:21:56 zira avahi-daemon[740]: Daemon already running on PID 740> 
> Sep 21 10:21:56 zira systemd[1]: avahi-daemon.service: Main process
exited, code=exited, status=255/n/a
> Sep 21 10:21:56 zira systemd[1]: Failed to start Avahi mDNS/DNS-SD Stack.
> Sep 21 10:21:56 zira systemd[1]: avahi-daemon.service: Unit entered failed 
> state.
> Sep 21 10:21:56 zira systemd[1]: avahi-daemon.service: Failed with result 
> 'exit-code'.
> dpkg: error processing package avahi-daemon (--configure):
>  subprocess installed post-installation script returned error exit status 1
> 

Can you provide steps how to reproduce the issue? I've upgraded avahi on
several systems and did not run into this particular problem.




-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#867655: marked as done (ruby-gemnasium-gitlab-service: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: @connection.request(request))

[Debian Bug Tracking System]

Your message dated Thu, 21 Sep 2017 16:31:11 +
with message-id 
and subject line Bug#867655: fixed in ruby-gemnasium-gitlab-service 0.2.6-2
has caused the Debian Bug report #867655,
regarding ruby-gemnasium-gitlab-service: FTBFS: ERROR: Test "ruby2.3" failed: 
Failure/Error: @connection.request(request)
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.)


-- 
867655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867655
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-gemnasium-gitlab-service
Version: 0.2.6-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: @connection.request(request)
> 
>  WebMock::NetConnectNotAllowedError:
>Real HTTP connections are disabled. Unregistered request: POST 
> https://api.gemnasium.com/v1/test_path with body '{"foo":"bar"}' with headers 
> {'Accept'=>'application/json', 
> 'Accept-Encoding'=>'gzip;q=1.0,deflate;q=0.6,identity;q=0.3', 
> 'Authorization'=>'Basic WDpzZWNyZXRfYXBpX2tleQ==', 
> 'Content-Type'=>'application/json', 'User-Agent'=>'Gemnasium Gitlab Service - 
> v0.2.6'}
> 
>You can stub this request with the following snippet:
> 
>stub_request(:post, "https://api.gemnasium.com/v1/test_path;).
>  with(body: "{\"foo\":\"bar\"}",
>   headers: {'Accept'=>'application/json', 
> 'Accept-Encoding'=>'gzip;q=1.0,deflate;q=0.6,identity;q=0.3', 
> 'Authorization'=>'Basic WDpzZWNyZXRfYXBpX2tleQ==', 
> 'Content-Type'=>'application/json', 'User-Agent'=>'Gemnasium Gitlab Service - 
> v0.2.6'}).
>  to_return(status: 200, body: "", headers: {})
> 
>registered request stubs:
> 
>stub_request(:post, 
> "https://X:secret_api_...@api.gemnasium.com/v1/test_path;).
>  with(body: {"foo"=>"bar"},
>   headers: {'Accept'=>'application/json', 
> 'Content-Type'=>'application/json', 'User-Agent'=>'Gemnasium Gitlab Service - 
> v0.2.6'})
>stub_request(:get, 
> "https://X:secret_api_...@api.gemnasium.com/v1/test_path;).
>  with(headers: {'Accept'=>'application/json', 
> 'Content-Type'=>'application/json', 'User-Agent'=>'Gemnasium Gitlab Service - 
> v0.2.6'})
>stub_request(:post, 
> "https://X:secret_api_...@api.gemnasium.com/v1/projects/project_slug/dependency_files;).
>  with(headers: {'Accept'=>'application/json', 
> 'Content-Type'=>'application/json', 'User-Agent'=>'Gemnasium Gitlab Service - 
> v0.2.6'})
> 
>
>  # ./lib/gemnasium/gitlab_service/connection.rb:28:in `post'
>  # ./spec/gemnasium/gitlab_service/connection_spec.rb:25:in `block (3 
> levels) in '
> 
> Deprecation Warnings:
> 
> Using `should` from rspec-expectations' old `:should` syntax without 
> explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or 
> explicitly enable `:should` with `config.expect_with(:rspec) { |c| c.syntax = 
> :should }` instead. Called from 
> /<>/spec/gemnasium/gitlab_service/client_spec.rb:11:in `block (3 
> levels) in '.
> 
> Using `stub` from rspec-mocks' old `:should` syntax without explicitly 
> enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly 
> enable `:should` instead. Called from 
> /<>/spec/gemnasium/gitlab_service/pusher_spec.rb:8:in `block (2 
> levels) in '.
> 
> 
> If you need more of the backtrace for any of these deprecations to
> identify where to make the necessary changes, you can configure
> `config.raise_errors_for_deprecations!`, and it will turn the
> deprecation warnings into errors, giving you the full backtrace.
> 
> 2 deprecation warnings total
> 
> Finished in 0.02929 seconds (files took 0.65037 seconds to load)
> 8 examples, 3 failures
> 
> Failed examples:
> 
> rspec ./spec/gemnasium/gitlab_service/client_spec.rb:30 # 
> Gemnasium::GitlabService::Client upload_files issues a POST request
> rspec ./spec/gemnasium/gitlab_service/connection_spec.rb:18 # 
> Gemnasium::GitlabService::Connection get issues a GET request
> rspec ./spec/gemnasium/gitlab_service/connection_spec.rb:27 # 
> Gemnasium::GitlabService::Connection post issues a POST request
> 
> /usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
> documentation failed
> ERROR: Test "ruby2.3" failed: 

The full build log is available from:
   

Bug#844976: marked as done (clisp: FTBFS: Cannot map memory to address 0x8020875b2000 .)

[Debian Bug Tracking System]

Your message dated Thu, 21 Sep 2017 18:25:01 +0200
with message-id <1506011101.1818.34.ca...@debian.org>
and subject line Re: clisp: FTBFS: Cannot map memory to address 0x8020875b2000 .
has caused the Debian Bug report #844976,
regarding clisp: FTBFS: Cannot map memory to address 0x8020875b2000 .
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.)


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

Hi,

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

Note that this build machine has 256 GB of RAM, so there's something
strange going on.

Relevant part (hopefully):
> make[2]: Entering directory '/<>/debian/build/po'
> installing en.gmo as ../locale/en/LC_MESSAGES/clisp.mo
> installing clisplow_en.gmo as ../locale/en/LC_MESSAGES/clisplow.mo
> installing da.gmo as ../locale/da/LC_MESSAGES/clisp.mo
> installing clisplow_da.gmo as ../locale/da/LC_MESSAGES/clisplow.mo
> installing de.gmo as ../locale/de/LC_MESSAGES/clisp.mo
> installing clisplow_de.gmo as ../locale/de/LC_MESSAGES/clisplow.mo
> installing fr.gmo as ../locale/fr/LC_MESSAGES/clisp.mo
> installing clisplow_fr.gmo as ../locale/fr/LC_MESSAGES/clisplow.mo
> installing es.gmo as ../locale/es/LC_MESSAGES/clisp.mo
> installing clisplow_es.gmo as ../locale/es/LC_MESSAGES/clisplow.mo
> installing nl.gmo as ../locale/nl/LC_MESSAGES/clisp.mo
> installing clisplow_nl.gmo as ../locale/nl/LC_MESSAGES/clisplow.mo
> installing ru.gmo as ../locale/ru/LC_MESSAGES/clisp.mo
> installing clisplow_ru.gmo as ../locale/ru/LC_MESSAGES/clisplow.mo
> make[2]: Leaving directory '/<>/debian/build/po'
> rm -rf data
> mkdir data
> cd data && ln -s /<>/utils/unicode/UnicodeDataFull.txt .
> cd data && ln -s /<>/doc/Symbol-Table.text .
> gcc -falign-functions=4 -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit 
> -Wreturn-type -Wmissing-declarations -O -DENABLE_UNICODE -DDYNAMIC_FFI 
> -DDYNAMIC_MODULES -I.  -Wl,--export-dynamic spvw.o spvwtabf.o spvwtabs.o 
> spvwtabo.o eval.o control.o encoding.o pathname.o stream.o socket.o io.o 
> funarg.o array.o hashtabl.o list.o package.o record.o weak.o sequence.o 
> charstrg.o debug.o error.o misc.o time.o predtype.o symbol.o lisparit.o 
> i18n.o foreign.o unixaux.o built.o modules.o -lreadline -lncurses -ldl 
> -lavcall -lcallback  -lsigsegv libgnu_cl.a -o lisp.run
> ./lisp.run -B . -N locale -E UTF-8 -Epathname 1:1 -Emisc 1:1 -norc -m 2MW -lp 
> /<>/src/ -x '(and (load "/<>/src/init.lisp") 
> (sys::%saveinitmem) (ext::exit)) (ext::exit t)'
>   i i i i i i i   ooooo   o   o
>   I I I I I I I  8 8   8   8 8 o  88
>   I  \ `+' /  I  8 8   8 888
>\  `-+-'  /   8 8   8  o   8
> `-__|__-'8 8   8   8  8
> |8 o   8   8 o 8  8
>   --+--   o8oo  ooo8ooo   o   8
> 
> Welcome to GNU CLISP 2.49 (2010-07-07) 
> 
> Copyright (c) Bruno Haible, Michael Stoll 1992, 1993
> Copyright (c) Bruno Haible, Marcus Daniels 1994-1997
> Copyright (c) Bruno Haible, Pierpaolo Bernardi, Sam Steingold 1998
> Copyright (c) Bruno Haible, Sam Steingold 1999-2000
> Copyright (c) Sam Steingold, Bruno Haible 2001-2010
> 
> Type :h and hit Enter for context help.
> 
> ;; Loading file /<>/src/defseq.lisp ...
> ;; Loaded file /<>/src/defseq.lisp
> ;; Loading file /<>/src/backquote.lisp ...
> ;; Loaded file /<>/src/backquote.lisp
> ;; Loading file /<>/src/defmacro.lisp ...
> ;; Loaded file /<>/src/defmacro.lisp
> ;; Loading file /<>/src/macros1.lisp ...
> ;; Loaded file /<>/src/macros1.lisp
> ;; Loading file /<>/src/macros2.lisp ...
> ;; Loaded file /<>/src/macros2.lisp
> ;; Loading file /<>/src/defs1.lisp ...
> ;; Loaded file /<>/src/defs1.lisp
> ;; Loading file /<>/src/lambdalist.lisp ...
> ;; Loaded file /<>/src/lambdalist.lisp
> ;; Loading file /<>/src/places.lisp ...
> ;; Loaded file /<>/src/places.lisp
> ;; Loading file /<>/src/floatprint.lisp ...
> ;; Loaded file /<>/src/floatprint.lisp
> ;; Loading file /<>/src/defpackage.lisp ...
> ;; Loaded file /<>/src/defpackage.lisp
> ;; Loading file /<>/src/type.lisp ...
> ;;  Loading file /<>/src/subtypep.lisp ...
> ;;  Loaded file /<>/src/subtypep.lisp
> ;; Loaded file /<>/src/type.lisp
> ;; Loading 

Processed: Bug#867655 marked as pending

[Debian Bug Tracking System]

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

> tag 867655 pending
Bug #867655 [src:ruby-gemnasium-gitlab-service] ruby-gemnasium-gitlab-service: 
FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: @connection.request(request)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#867655: marked as pending

[Pirate Praveen]

tag 867655 pending
thanks

Hello,

Bug #867655 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/pkg-ruby-extras/ruby-gemnasium-gitlab-service.git/commit/?id=44506f9

---
commit 44506f958a7609d924777c1a5c8ab668d10403f6
Author: Pirate Praveen 
Date:   Thu Sep 21 21:38:16 2017 +0530

update changelog

diff --git a/debian/changelog b/debian/changelog
index bc17d82..30193b2 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+ruby-gemnasium-gitlab-service (0.2.6-2) unstable; urgency=medium
+
+  * Run tests with webmock 3 (Closes: #867655). Thanks to kp for the patch. 
+
+ -- Pirate Praveen   Thu, 21 Sep 2017 21:29:35 +0530
+
 ruby-gemnasium-gitlab-service (0.2.6-1) unstable; urgency=medium
 
   * Initial release (Closes: #806857)

Bug#876274: wordpress: 9 security bugs in wordpress 4.8.1 and earlier

[Rodrigo Campos]

On Thu, Sep 21, 2017 at 09:54:49AM +0200, Ángel wrote:
> Salvatore wrote:
> > have you identified already the issue -> fixing commit mappings?
> 
> For version 4.8.1 [buster, sid], upstream fixed them on 4.8.2
> https://codex.wordpress.org/Version_4.8.2

And for jessie backports I'll update as soon as it is on sid :-)

Bug#874764: marked as done (389-ds-base-dev: broken symlinks: /usr/lib//dirsrv/lib{sds, nunc-stans, ns-dshttpd}.so)

[Debian Bug Tracking System]

Your message dated Thu, 21 Sep 2017 15:20:19 +
with message-id 
and subject line Bug#874764: fixed in 389-ds-base 1.3.6.7-5
has caused the Debian Bug report #874764,
regarding 389-ds-base-dev: broken symlinks: /usr/lib//dirsrv/lib{sds, 
nunc-stans, ns-dshttpd}.so
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.)


-- 
874764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874764
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: 389-ds-base-dev
Version: 1.3.6.7-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

1m21.3s ERROR: FAIL: Broken symlinks:
  /usr/lib/x86_64-linux-gnu/dirsrv/libsds.so -> libsds.so.0.0.0
  /usr/lib/x86_64-linux-gnu/dirsrv/libnunc-stans.so -> libnunc-stans.so.0.1.0
  /usr/lib/x86_64-linux-gnu/dirsrv/libns-dshttpd.so -> libns-dshttpd-1.3.6.7.so

Either these libs should have been in 389-ds-base-libs,
or 389-ds-base-dev needs to depend on 389-ds-base which currently
ships the targets.


cheers,

Andreas


389-ds-base-dev_1.3.6.7-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: 389-ds-base
Source-Version: 1.3.6.7-5

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 21 Sep 2017 16:44:13 +0300
Source: 389-ds-base
Binary: 389-ds 389-ds-base-libs 389-ds-base-dev 389-ds-base
Architecture: source
Version: 1.3.6.7-5
Distribution: unstable
Urgency: medium
Maintainer: Debian 389ds Team 

Changed-By: Timo Aaltonen 
Description:
 389-ds - 389 Directory Server suite - metapackage
 389-ds-base - 389 Directory Server suite - server
 389-ds-base-dev - 389 Directory Server suite - development files
 389-ds-base-libs - 389 Directory Server suite - libraries
Closes: 874764
Changes:
 389-ds-base (1.3.6.7-5) unstable; urgency=medium
 .
   * Move all libs from base to -libs, add B/R. (Closes: #874764)
Checksums-Sha1:
 bc9b64e54ca895840e2bd978552acb376f7ce7f3 2563 389-ds-base_1.3.6.7-5.dsc
 2f8640dae8cef1bb55b3b9114f2b04eb8b83d302 20688 
389-ds-base_1.3.6.7-5.debian.tar.xz
Checksums-Sha256:
 9e0ee0a3ad1fd65c2ab2d3d4a97635058f0d2ff11d704b97bba4eb410de49ce1 2563 
389-ds-base_1.3.6.7-5.dsc
 cbc45f9f2f7a785e613ac8934706082a896c4fa3c67db991be0f9e0d8d5b6d12 20688 
389-ds-base_1.3.6.7-5.debian.tar.xz
Files:
 3e776e35f2f815a35f77f5c496cc2873 2563 net optional 389-ds-base_1.3.6.7-5.dsc
 ecf0ac0e00a71a65edcf60d08824236d 20688 net optional 
389-ds-base_1.3.6.7-5.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJZw8JAAAoJEMtwMWWoiYTcl3IP/3jyuJ8X8iD6zrSVTfHLUBdM
p4hcXlA4P3ihEH81GeOdmg3hPBnNPNC58aOYYPcR4/uIlGv2rrpGMuKfWMQkMCLC
Dasigsd3s1QWYPBsOTTVjqad+6nO7RexU9GOo4+Z4ShbUgaWTcBtabZkguDKCLRN
Gw03tJMTpbwjzHC0uDWm0QX60glUR98gefoXiU02pEameWgLcl1tbJB3Ny8W04Q4
1dE/aQ8rwiKwKakOwp0ngaKxIGp+7tSAtkLygK/Xi5KNZRxPjSJmgY9muf8SP/gw
6qKVE3enmc8/5Phjf4ICX+iSAW5OP92hrGBBNJ5BpA5qVSjLeZwme/boVfl7OCBu
cWlty3f5VBuGr8Mq7uOx3PUrATn5FWABBFj54ilPas8N/sPTZ+j/saI9zb2RynPz
RlyRgozXtOkeXX/yavFg/Tn1+7pyIRkrCGP1APOXJlg7xipzO9cLG2WNxfTk4xrd
q7TLDZ+bIYuIi/70VBohkpXYKjuzNVg7zrqPsX03V9gqGWyyTWxER2Ax77PGC8Jv
kt42HJTajlG7XIoy/2o2x7SZuIGOIzSyMHvGHw/gy90pWw9AKlntJ3yFXdOOuWyu
ZbGP2b+73M3yZT/rsjkvtqjeKhmAv8lTotYspDkoHhu+kywx0AMDFCukpUzT5Hl6
g5E4CVQwIfiDgAFnxkAT
=ce/6
-END PGP SIGNATURE End Message ---

Bug#874524: Invalid symlink: /usr/bin/r2-indent -> /build/radare2-1.6.0+dfsg/sys/indent.sh

[Mathieu Malaterre]

> Severity: serious
>
> This symlink is obviously wrong:

uh ? Could you please mention the section of the standard that is not
respected (must/should) ?

Ref: https://www.debian.org/Bugs/Developer#severities

Thx

Bug#818616: luajit: laujit segfaults on arm64

[Edmund Grimley Evans]

I think this bug was fixed in 2.1.0~beta3. Can it be closed please?
Any objections?

# tail -n 1 /proc/self/maps
eb71-eb731000 rw-p  00:00 0  [stack]

# dpkg -i libluajit-5.1-2_2.1.0~beta2+dfsg-1_arm64.deb
libluajit-5.1-common_2.1.0~beta2+dfsg-1_arm64.deb
luajit_2.1.0~beta2+dfsg-1_arm64.deb
...
# luajit -e 'print("x");'
Segmentation fault (core dumped)

# dpkg -i libluajit-5.1-2_2.1.0~beta2+dfsg-3_arm64.deb
libluajit-5.1-common_2.1.0~beta2+dfsg-3_arm64.deb
luajit_2.1.0~beta2+dfsg-3_arm64.deb
...
# luajit -e 'print("x");'
Segmentation fault (core dumped)

# dpkg -i libluajit-5.1-2_2.1.0~beta3+dfsg-1_arm64.deb
libluajit-5.1-common_2.1.0~beta3+dfsg-1_all.deb
luajit_2.1.0~beta3+dfsg-1_arm64.deb
# luajit -e 'print("x");'
x

# dpkg -i libluajit-5.1-2_2.1.0~beta3+dfsg-2_arm64.deb
libluajit-5.1-common_2.1.0~beta3+dfsg-2_all.deb
luajit_2.1.0~beta3+dfsg-2_arm64.deb
# luajit -e 'print("x");'
x

Processed: Re: busybox-static: execs applets when chrooting

[Debian Bug Tracking System]

Processing control commands:

> tags -1 confirmed
Bug #774227 [busybox-static] busybox-static: execs applets when chrooting
Added tag(s) confirmed.
> severity -1 normal
Bug #774227 [busybox-static] busybox-static: execs applets when chrooting
Severity set to 'normal' from 'serious'

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

Bug#774227: busybox-static: execs applets when chrooting

[Chris Boot]

Control: tags -1 confirmed
Control: severity -1 normal

On 03/07/17 11:49, Alexander Kurtz wrote:
> As you can see, chroot will run the applet rather than the binary
> unless the full path is given. While this *may* be useful in some
> situations, it can also lead to *really* subtle failures in others, so
> I'm raising the severity of this bug. Please consider applying
> Bernhard's patch if possible or at least documenting this behaviour!

Hi Alexander, Bernhard,

The busybox package in Debian is under new management, and we (the new
maintainers) are going over the existing bugs to see what can and should
be fixed or closed.

I've spent some time investigating this bug, and it seems that this
behaviour is actually deliberate in busybox-static. The -static package
is specifically configured in this way:

> bootc@muta busybox $ grep -r CONFIG_FEATURE_PREFER_APPLETS debian/config/pkg/
> debian/config/pkg/udeb:# CONFIG_FEATURE_PREFER_APPLETS is not set
> debian/config/pkg/static:CONFIG_FEATURE_PREFER_APPLETS=y
> debian/config/pkg/deb:# CONFIG_FEATURE_PREFER_APPLETS is not set

I can understand that you might find this behaviour surprising, but I
believe that the static package would have been configured this way due
to its intended usage: as a useful tool to rescue a broken system. If
your system is broken in such a way that you require a statically-linked
version of busybox to dig yourself out of that hole, then it's likely
that your system-provided tools will not function. There is no point
trying to run them, so the built-in applets should be preferred.

The standard flavour of busybox in Debian is the dynamically linked
'busybox' package, which doesn't have this behaviour because it's mainly
intended for use in the initramfs.

I guess this means that the behaviour is probably correct and simply
needs documenting. Aside from the package description, is there
somewhere in particular that makes sense to you (for example, where you
would have looked) to find such a difference documented?

Because I suspect this is a documentation bug rather than actual broken
behaviour, I am reducing the severity of this bug.

Cheers,
Chris

-- 
Chris Boot
bo...@debian.org

Bug#876277: marked as done (opendnssec: FTBFS with debhelper 10.9)

[Debian Bug Tracking System]

Your message dated Thu, 21 Sep 2017 12:22:28 +
with message-id 
and subject line Bug#876277: fixed in opendnssec 1:2.1.3-0.2
has caused the Debian Bug report #876277,
regarding opendnssec: FTBFS with debhelper 10.9
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.)


-- 
876277: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876277
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: opendnssec
Version: 1:2.1.3-0.1
Severity: serious
Tags: sid buster
Control: found -1 1:2.0.4-3

Hi,

opendnssec FTBFS with debhelper 10.9 with the error:
>debian/rules override_dh_installdocs-arch
> make[1]: Entering directory '/<>'
> dh_installdocs -popendnssec-common -popendnssec-common\
>   -popendnssec-dbg-mysql -popendnssec-dbg-sqlite3 \
>   -popendnssec-enforcer -popendnssec-enforcer-sqlite3 \
>   -popendnssec-enforcer-mysql -plibhsm-bin \
>   -popendnssec-signer -popendnssec-doc 
> dh_installdocs: Requested unknown package opendnssec-dbg-mysql via 
> -p/--package, expected one of: opendnssec-common opendnssec opendnssec-doc 
> opendnssec-enforcer opendnssec-enforcer-mysql opendnssec-enforcer-sqlite3 
> opendnssec-signer libhsm-bin
> dh_installdocs: Requested unknown package opendnssec-dbg-sqlite3 via 
> -p/--package, expected one of: opendnssec-common opendnssec opendnssec-doc 
> opendnssec-enforcer opendnssec-enforcer-mysql opendnssec-enforcer-sqlite3 
> opendnssec-signer libhsm-bin
> dh_installdocs: unknown option or error during option parsing; aborting
> debian/rules:81: recipe for target 'override_dh_installdocs-arch' failed
> make[1]: *** [override_dh_installdocs-arch] Error 25
> make[1]: Leaving directory '/<>'
> debian/rules:24: recipe for target 'binary-arch' failed
> make: *** [binary-arch] Error 2

In debhelper 10.9, referring to a non-existent package with the -p
option is now an error. See #795432

Thanks,
James



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: opendnssec
Source-Version: 1:2.1.3-0.2

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

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

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated opendnssec 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, 21 Sep 2017 15:00:10 +0300
Source: opendnssec
Binary: opendnssec-common opendnssec opendnssec-doc opendnssec-enforcer 
opendnssec-enforcer-mysql opendnssec-enforcer-sqlite3 opendnssec-signer 
libhsm-bin
Architecture: source
Version: 1:2.1.3-0.2
Distribution: unstable
Urgency: medium
Maintainer: Debian DNS Packaging 
Changed-By: Timo Aaltonen 
Description:
 libhsm-bin - library for interfacing PKCS#11 Hardware Security Modules
 opendnssec - dependency package to install full OpenDNSSEC suite
 opendnssec-common - common configuration files for OpenDNSSEC suite
 opendnssec-doc - documentation for OpenDNSSEC suite
 opendnssec-enforcer - tool to prepare DNSSEC keys (common package)
 opendnssec-enforcer-mysql - tool to prepare DNSSEC keys (MySQL backend)
 opendnssec-enforcer-sqlite3 - tool to prepare DNSSEC keys (sqlite3 backend)
 opendnssec-signer - daemon to sign DNS zone files periodically
Closes: 876277
Changes:
 opendnssec (1:2.1.3-0.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * rules: Drop handling old dbg packages from dh_installdocs override.
 (Closes: #876277)
Checksums-Sha1:
 1bdcc0e7ccaa086a2ca944e00173005fef39672e 2699 opendnssec_2.1.3-0.2.dsc
 6f40ad27bd36e613f17469c78a741a6da885eae2 23656 
opendnssec_2.1.3-0.2.debian.tar.xz
Checksums-Sha256:
 3ac63ae5dfad176fe47a2184d6912fa6c290888d72c448fc3c30e24e722d11c0 2699 
opendnssec_2.1.3-0.2.dsc
 8b5c5f86af675c284ee96354aee192ea7012b6c16a294f1d38ce5222660f8710 23656 
opendnssec_2.1.3-0.2.debian.tar.xz
Files:
 3f3bba305e775dea75571289624ef96b 2699 admin extra opendnssec_2.1.3-0.2.dsc
 379ae677cb53d8d205305ddef0e7d35c 23656 admin extra 

Bug#875637: marked as done (iipimage-server: Wrong configuration file /etc/apache2/mods-available/iipsrv.conf)

[Debian Bug Tracking System]

Your message dated Thu, 21 Sep 2017 12:06:12 +
with message-id 
and subject line Bug#875637: fixed in iipimage 1.0-2
has caused the Debian Bug report #875637,
regarding iipimage-server: Wrong configuration file 
/etc/apache2/mods-available/iipsrv.conf
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.)


-- 
875637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875637
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: iipimage-server
Version: 1.0-1+b1
Severity: grave
Tags: patch
Justification: renders package unusable

The default installation with Apache2 won't work with the
provided configuration file because that file uses
"Directory" instead of "Location".

A fixed version is shown below.

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

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

Versions of packages iipimage-server depends on:
ii  libapache2-mod-fcgid  1:2.3.9-1+b1
ii  libc6 2.24-11+deb9u1
ii  libfcgi0ldbl  2.4.0-8.4+b1
ii  libgcc1   1:6.3.0-18
ii  libgomp1  6.3.0-18
ii  libjpeg62-turbo   1:1.5.1-2
ii  libmemcached111.0.18-4.1
ii  libstdc++66.3.0-18
ii  libtiff5  4.0.8-2+deb9u1

Versions of packages iipimage-server recommends:
ii  imagemagick-6.q16 [imagemagick]  8:6.9.7.4+dfsg-11+deb9u1
pn  libvips-tools

Versions of packages iipimage-server suggests:
pn  iipimage-doc  
pn  memcached 

-- Configuration Files:
/etc/apache2/mods-available/iipsrv.conf changed:
ScriptAlias /iipsrv/ "/usr/lib/iipimage-server/"

   AllowOverride None
   Options None
   
 
   Order allow,deny
   Allow from all
 
 = 2.4>
   Require all granted
 
   
   # Set the module handler
   AddHandler fcgid-script .fcgi

FcgidInitialEnv VERBOSITY "1"
FcgidInitialEnv LOGFILE "/var/log/iipsrv.log"
FcgidInitialEnv MAX_IMAGE_CACHE_SIZE "10"
FcgidInitialEnv JPEG_QUALITY "90"
FcgidInitialEnv MAX_CVT "5000"
FcgidInitialEnv MEMCACHED_SERVERS "localhost"
FcgidIdleTimeout 0
FcgidMaxProcessesPerClass 1


-- no debconf information
--- End Message ---
--- Begin Message ---
Source: iipimage
Source-Version: 1.0-2

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

Debian distribution maintenance software
pp.
Mathieu Malaterre  (supplier of updated iipimage 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, 21 Sep 2017 13:36:40 +0200
Source: iipimage
Binary: iipimage-server iipimage-doc
Architecture: source
Version: 1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Mathieu Malaterre 
Changed-By: Mathieu Malaterre 
Description:
 iipimage-doc - Web-based streamed viewing and zooming of ultra high-resolution 
i
 iipimage-server - Web-based streamed viewing and zooming of ultra 
high-resolution i
Closes: 875637
Changes:
 iipimage (1.0-2) unstable; urgency=medium
 .
   * Fix apache configuration. Closes: #875637
   * Bump Std-Vers to 4.1.0, no changes needed
Checksums-Sha1:
 9688ba9f5310ff81da4fe0f539e84abf1b1352b3 2107 iipimage_1.0-2.dsc
 aa8962985d128418866258c539d70ff2fb0a051c 37196 iipimage_1.0-2.debian.tar.xz
 107c8a2855cb8b53e5b1b77aa3e7b657dddf6dfd 6964 iipimage_1.0-2_source.buildinfo
Checksums-Sha256:
 0add442f1060491121e502fcfd0d6ee12b56114d72f1220ebf9c8f4ab30eb94e 2107 
iipimage_1.0-2.dsc
 0b6795b89d6469bbfc6b0d7593503cf9c93f46b724b2e88ab62cc5dfb8aa8596 37196 
iipimage_1.0-2.debian.tar.xz
 108c42f541ae21d03b0481661e8b10081263c39bebae6b5faf652123ed1ee5c9 6964 
iipimage_1.0-2_source.buildinfo
Files:
 4ab09a7c7225a07f3754f11f0a7e52fe 2107 web optional 

Bug#874693: breaks other packages

[Jeremy Bicha]

On Fri, Sep 8, 2017 at 2:06 PM, Michael Biebl  wrote:
> The version from experimental apparently breaks other packages like
> gnome-weather:

Yes, I remember now that several GNOME 3.22 packages had to be updated
to work with gjs 1.48. But by this point, all those packages have been
updated to at least 3.24 in Testing and gjs is still at 1.46 (GNOME
3.22 basically) in unstable/testing.

I think you will be unable to reproduce this bug with gnome-weather
3.24.0-1 in testing.

To comprehensively "fix" this bug, someone will need to try all the
GNOME 3.22 gjs-related packages (from stretch) against gjs 1.50
(rebuilt against stretch to not introduce dependency
incompatibilities). Personally, I don't think this is that important
of an issue.

Thanks,
Jeremy Bicha

Bug#876353: gccgo-7: unhandled signal 11 at s390x/ppc64

[Shengjing Zhu]

> is this limited to big endian 64bit systems?  Maybe somebody could check on
> ppc64el, sparc64 and mips64el as well?

AFAICT, ppc64el works fine.

mips, s390x, ppc64 fail in same reason on buildd

-- 
Best regards,
Shengjing Zhu

Bug#876353: gccgo-7: unhandled signal 11 at s390x/ppc64

[Matthias Klose]

On 21.09.2017 11:54, Shengjing Zhu wrote:
>> please could you recheck with gcc-snapshot?
> 
> Thanks,
> gcc-snapshot works
> 
> # /usr/lib/gcc-snapshot/bin/go version
> go version go1.9 gccgo (Debian 20170917-1) 8.0.0 20170917
> (experimental) [trunk revision 252892] linux/ppc64

is this limited to big endian 64bit systems?  Maybe somebody could check on
ppc64el, sparc64 and mips64el as well?

Bug#876353: gccgo-7: unhandled signal 11 at s390x/ppc64

[Shengjing Zhu]

> please could you recheck with gcc-snapshot?

Thanks,
gcc-snapshot works

# /usr/lib/gcc-snapshot/bin/go version
go version go1.9 gccgo (Debian 20170917-1) 8.0.0 20170917
(experimental) [trunk revision 252892] linux/ppc64

-- 
Best regards,
Shengjing Zhu

Bug#876353: gccgo-7: unhandled signal 11 at s390x/ppc64

[Matthias Klose]

On 21.09.2017 11:17, Shengjing Zhu wrote:
> Package: gccgo-7
> Version: 7.2.0-6
> Severity: grave
> Justification: renders package unusable
> 
> Dear maintainer,
> 
> with gccgo-7 7.2.0-6, segmentation fault if I run `go-7 version` on
> ppc64 arch.
> 
> dmesg is
> [1619215.799421] go-7[12079]: unhandled signal 11 at 1010a540 nip 
> 7fff95bfadac lr 7fff9705d458 code 30001
> 
> At first,
> I find my package built failed with gccgo-7 7.2.0-6 on s390x and ppc64,
> https://buildd.debian.org/status/logs.php?pkg=elvish=0.10.1-1
> 
> The error is `go install ... died with signal 11`
> 
> Since I have no s390x porterbox to access, but have one ppc64. So I try to
> reproduce it on ppc64, but I failed even I run `go-7 version`.
> 
> IIRC, gccgo-7 7.2.0-2 works fine.

please could you recheck with gcc-snapshot?

Bug#876353: gccgo-7: unhandled signal 11 at s390x/ppc64

[Shengjing Zhu]

Since there's only 7.2.0-1 on http://snapshot.debian.org/archive/debian-ports/
I can confirm this version works on ppc64

Thanks
Shengjing Zhu

Processed: Re: avahi-daemon: upgrade failed: failed to configure

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #876342 [avahi-daemon] avahi-daemon: upgrade failed: failed to configure
Severity set to 'serious' from 'grave'

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

Bug#876342: avahi-daemon: upgrade failed: failed to configure

[Vincent Lefevre]

Control: severity -1 serious

The configure problem got eventually solved (I don't know how).

But this should not have made the upgrade fail in the first place.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#876288: marked as done (python3-fabio-dbg should depend on python3-pyqt4-dbg)

[Debian Bug Tracking System]

Your message dated Thu, 21 Sep 2017 09:25:53 +
with message-id 
and subject line Bug#876288: fixed in python-fabio 0.5.0+dfsg-2
has caused the Debian Bug report #876288,
regarding python3-fabio-dbg should depend on python3-pyqt4-dbg
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.)


-- 
876288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876288
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-fabio-dbg
Version: 0.5.0+dfsg-1
Severity: serious
Justification: Policy 7.2
Control: affects -1 src:silx

python3-fabio-dbg depends on python-qt4-dbg rather than python3-pyqt4-dbg.
As such, builds of silx in minimal environments (as on the autobuilders)
have been failing because it build depends on Qt4 bindings only via fabio:

File 
"/<>/silx-0.5.0+dfsg/.pybuild/pythonX.Y-dbg_3.6/build/silx/gui/qt/_qt.py",
 line 110, in 
  from PyQt4.QtCore import *  # noqa
  ModuleNotFoundError: No module named 'PyQt4.QtCore'

Could you please take a look?

Thanks!

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

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

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

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

Debian distribution maintenance software
pp.
Picca Frédéric-Emmanuel  (supplier of updated python-fabio 
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, 20 Sep 2017 20:17:29 +0200
Source: python-fabio
Binary: fabio-viewer python-fabio python-fabio-dbg python3-fabio 
python3-fabio-dbg python-fabio-doc
Architecture: source
Version: 0.5.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Picca Frédéric-Emmanuel 
Description:
 fabio-viewer - Viewer for images produced by 2D X-ray detector
 python-fabio - I/O library for images produced by 2D X-ray detector - Python2
 python-fabio-dbg - I/O library for images produced by 2D X-ray detector - 
Python2 de
 python-fabio-doc - I/O library for images produced by 2D X-ray detector - 
documentat
 python3-fabio - I/O library for images produced by 2D X-ray detector - Python3
 python3-fabio-dbg - I/O library for images produced by 2D X-ray detector - 
Python3 de
Closes: 876288
Changes:
 python-fabio (0.5.0+dfsg-2) unstable; urgency=medium
 .
   * d/control
 - python-qt4 -> python3-pyqt4-dbg (Closes: #876288)
Checksums-Sha1:
 c607072bb94ab861f1f2b5698b135080ca359ee5 3110 python-fabio_0.5.0+dfsg-2.dsc
 82c77d4e820915af274757965dd1e364139a1ffb 6892 
python-fabio_0.5.0+dfsg-2.debian.tar.xz
 f556de5393b6a466d1d682d3205be442c7e93885 12379 
python-fabio_0.5.0+dfsg-2_source.buildinfo
Checksums-Sha256:
 956698d4cfae667d3a7083d4e0a86daf002be7380e065f9e6e2bfa639cd71641 3110 
python-fabio_0.5.0+dfsg-2.dsc
 c65d245ba94d8159212b312c9abf87e0dc1b4352056959825f5b5c6c80e48620 6892 
python-fabio_0.5.0+dfsg-2.debian.tar.xz
 5b9a1bfb716b3c5422c5edf368d207e0b74ddc7d360d59cccb458bdca9a29914 12379 
python-fabio_0.5.0+dfsg-2_source.buildinfo
Files:
 12bd305b11d19d8f1609ed2449c6e842 3110 science optional 
python-fabio_0.5.0+dfsg-2.dsc
 e4f80e31ad90465d07842bf619bd32de 6892 science optional 
python-fabio_0.5.0+dfsg-2.debian.tar.xz
 1c47d19ca18b5a0b556101b9573756d7 12379 science optional 
python-fabio_0.5.0+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE6S5+bp6dprGqMTncVjKQb0aW4BUFAlnDZtYACgkQVjKQb0aW
4BWSxQ/+Oj19Tz6gLQsitancefHhczTproRlysdfU9tXS1nh6oszW0WdCbYdh1c/
KwweIGVWkqWBlpoa9+n7EfdBgd9OiSv0xUEGpFhtKFHSqdEEckKBO3Alnfw+anSq
xUvk6el/LqNP1c3omG8EcMlb/NFJ9vE6ZjeLH5Rt27p6r/ulBg3JydsByfm+39hx
HeiVZg/uEcX1hAdQKTFLekkrghj1mgAW2jA7UHVNv6XrlxUKvrndxFOmGWpoVxO8
3CbGX4Zjxg1sLwNdFP0fUIAbK0iyyfL3xTRFwNYevICPiH/pyw1Csv/9l12Av546
/9Ley6aH4K0gREWvOVtUpU2RlINhgJ9xZ25wnjdLWx2chcVR9hJXnrtHQuNftgQj

Bug#876130: marked as done (libcamp-dev: fails to upgrade from 'stable' to 'sid' - trying to overwrite /usr/include/camp/args.hpp)

[Debian Bug Tracking System]

Your message dated Thu, 21 Sep 2017 09:20:48 +
with message-id 
and subject line Bug#876130: fixed in camp 0.8.1-2
has caused the Debian Bug report #876130,
regarding libcamp-dev: fails to upgrade from 'stable' to 'sid' - trying to 
overwrite /usr/include/camp/args.hpp
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.)


-- 
876130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876130
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcamp-dev
Version: 0.8.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.

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

  Selecting previously unselected package libcamp-dev:amd64.
  Preparing to unpack .../libcamp-dev_0.8.1-1_amd64.deb ...
  Unpacking libcamp-dev:amd64 (0.8.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libcamp-dev_0.8.1-1_amd64.deb (--unpack):
   trying to overwrite '/usr/include/camp/args.hpp', which is also in package 
libcamp0.7-dev 0.7.1.3-1
  Errors were encountered while processing:
   /var/cache/apt/archives/libcamp-dev_0.8.1-1_amd64.deb


cheers,

Andreas


libcamp0.7-dev=0.7.1.3-1_libcamp-dev=0.8.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: camp
Source-Version: 0.8.1-2

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

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

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

Debian distribution maintenance software
pp.
Flavien Bridault  (supplier of updated camp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 19 Sep 2017 07:35:20 +
Source: camp
Binary: libcamp0.8 libcamp-dev
Architecture: source amd64
Version: 0.8.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Flavien Bridault 
Description:
 libcamp-dev - C++ multi-purpose reflection library (development files)
 libcamp0.8 - C++ multi-purpose reflection library
Closes: 876130
Changes:
 camp (0.8.1-2) unstable; urgency=medium
 .
   * d/control: Add proper conflicts/replaces with 0.7 versions. Closes: #876130
Checksums-Sha1:
 0a7e2da023e7f21f1297e9f4a953aac2d9583c88 2000 camp_0.8.1-2.dsc
 4263b7d32006e16ad80b9011a0b3f350a755b506 5272 camp_0.8.1-2.debian.tar.xz
 18867a71ad7dcf6cc243c8a14c95c368225f7baa 11388 camp_0.8.1-2_amd64.buildinfo
 4610548af29575ee7cf10a64be1829aefcf40aea 44638 libcamp-dev_0.8.1-2_amd64.deb
 4fcb525f150b1a6f7984d19ac5d5b58b8ea4fb8a 1866862 
libcamp0.8-dbgsym_0.8.1-2_amd64.deb
 dd879a8cf60dbf585d830912af5442293d5b03ca 78226 libcamp0.8_0.8.1-2_amd64.deb
Checksums-Sha256:
 1e06056f8b49de3031dba0220e494c04e936ff66126c9bc5c664ee5a1d80c04b 2000 
camp_0.8.1-2.dsc
 255594e467acdba30307e2242ae8a5290af3ec2693489c063da3c02511bf59e6 5272 
camp_0.8.1-2.debian.tar.xz
 5a93f9a8b81ba27a6098449ae5c0cedc6fe2d4622b8a4890f6e780f216f14915 11388 
camp_0.8.1-2_amd64.buildinfo
 cdfbe5e3db46e19eb1e5be9fc9bb35a007036a721e1778c905da65599f67fd01 44638 
libcamp-dev_0.8.1-2_amd64.deb
 cfe81a36742154632058513237f06667255e869e71cdcf0ebadd52a53088851f 1866862 
libcamp0.8-dbgsym_0.8.1-2_amd64.deb
 e09a03b0222ea76e7ba80703e4d975ad79dbe1133239228f6208901e6e6f6009 78226 
libcamp0.8_0.8.1-2_amd64.deb
Files:
 76244c170362fee52cd2012cb778ecee 2000 science optional camp_0.8.1-2.dsc
 647b9c6c82e6fc16a34d30b07c8cedde 5272 science optional 
camp_0.8.1-2.debian.tar.xz
 7cb463bdc23b4eb10f0936b6b26a4ffe 11388 science optional 
camp_0.8.1-2_amd64.buildinfo
 dbf6e86c25a0a208b43871dd04a93bb9 44638 libdevel optional 
libcamp-dev_0.8.1-2_amd64.deb
 

Bug#876353: gccgo-7: unhandled signal 11 at s390x/ppc64

[Shengjing Zhu]

Package: gccgo-7
Version: 7.2.0-6
Severity: grave
Justification: renders package unusable

Dear maintainer,

with gccgo-7 7.2.0-6, segmentation fault if I run `go-7 version` on
ppc64 arch.

dmesg is
[1619215.799421] go-7[12079]: unhandled signal 11 at 1010a540 nip 
7fff95bfadac lr 7fff9705d458 code 30001

At first,
I find my package built failed with gccgo-7 7.2.0-6 on s390x and ppc64,
https://buildd.debian.org/status/logs.php?pkg=elvish=0.10.1-1

The error is `go install ... died with signal 11`

Since I have no s390x porterbox to access, but have one ppc64. So I try to
reproduce it on ppc64, but I failed even I run `go-7 version`.

IIRC, gccgo-7 7.2.0-2 works fine.

Thanks
shengjing Zhu


signature.asc
Description: PGP signature

Bug#876342: avahi-daemon: upgrade failed: failed to configure

[Vincent Lefevre]

On 2017-09-21 10:28:25 +0200, Vincent Lefevre wrote:
> Setting up avahi-daemon (0.7-3) ...
> Installing new version of config file /etc/avahi/avahi-daemon.conf ...
> Job for avahi-daemon.service failed because the control process exited with 
> error code.
> See "systemctl  status avahi-daemon.service" and "journalctl  -xe" for 
> details.

In case this is useful, here's "journalctl -xe" information:

[...]
Sep 21 10:21:23 zira systemd[1]: Reloading.
Sep 21 10:21:38 zira avahi-daemon[740]: Files changed, reloading.
Sep 21 10:21:38 zira avahi-daemon[740]: No service file found in 
/etc/avahi/services.
Sep 21 10:21:38 zira dbus[701]: [system] Reloaded configuration
Sep 21 10:21:55 zira dbus[701]: [system] Reloaded configuration
Sep 21 10:21:55 zira avahi-daemon[740]: Files changed, reloading.
Sep 21 10:21:55 zira avahi-daemon[740]: No service file found in 
/etc/avahi/services.
Sep 21 10:21:55 zira avahi-daemon[740]: Files changed, reloading.
Sep 21 10:21:55 zira avahi-daemon[740]: No service file found in 
/etc/avahi/services.
Sep 21 10:21:55 zira dbus[701]: [system] Reloaded configuration
Sep 21 10:21:56 zira systemd[1]: Reloading.
Sep 21 10:21:56 zira systemd[1]: Reloading D-Bus System Message Bus.
-- Subject: Unit dbus.service has begun reloading its configuration
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit dbus.service has begun reloading its configuration
Sep 21 10:21:56 zira dbus[701]: [system] Reloaded configuration
Sep 21 10:21:56 zira dbus-send[686]: method return time=1505982116.229891 
sender=org.freedesktop.DBus -> destination=:1.1255 serial=3 reply_serial=2
Sep 21 10:21:56 zira systemd[1]: Reloaded D-Bus System Message Bus.
-- Subject: Unit dbus.service has finished reloading its configuration
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit dbus.service has finished reloading its configuration
-- 
-- The result is done.
Sep 21 10:21:56 zira systemd[1]: Reloading.
Sep 21 10:21:56 zira systemd[1]: Reloading.
Sep 21 10:21:56 zira systemd[1]: Stopping Avahi mDNS/DNS-SD Stack...
-- Subject: Unit avahi-daemon.service has begun shutting down
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit avahi-daemon.service has begun shutting down.
Sep 21 10:21:56 zira avahi-daemon[740]: Got SIGTERM, quitting.
Sep 21 10:21:56 zira avahi-daemon[740]: Leaving mDNS multicast group on 
interface eth0.IPv6 with address 2a02:8429:80cd:3100:328d:99ff:fe25:ad3f.
Sep 21 10:21:56 zira avahi-daemon[740]: Leaving mDNS multicast group on 
interface eth0.IPv4 with address 192.168.1.3.
Sep 21 10:21:56 zira dbus[701]: [system] Activating via systemd: service 
name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Sep 21 10:21:56 zira avahi-daemon[740]: avahi-daemon 0.6.32 exiting.
Sep 21 10:21:56 zira systemd[1]: Stopped Avahi mDNS/DNS-SD Stack.
-- Subject: Unit avahi-daemon.service has finished shutting down
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit avahi-daemon.service has finished shutting down.
Sep 21 10:21:56 zira systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
-- Subject: Unit avahi-daemon.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit avahi-daemon.service has begun starting up.
Sep 21 10:21:56 zira avahi-daemon[740]: Daemon already running on PID 740
Sep 21 10:21:56 zira systemd[1]: avahi-daemon.service: Main process exited, 
code=exited, status=255/n/a
Sep 21 10:21:56 zira systemd[1]: Failed to start Avahi mDNS/DNS-SD Stack.
-- Subject: Unit avahi-daemon.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit avahi-daemon.service has failed.
-- 
-- The result is failed.
Sep 21 10:21:56 zira systemd[1]: avahi-daemon.service: Unit entered failed 
state.
Sep 21 10:21:56 zira systemd[1]: avahi-daemon.service: Failed with result 
'exit-code'.
[...]

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#876342: avahi-daemon: upgrade failed: failed to configure

[Vincent Lefevre]

Package: avahi-daemon
Version: 0.7-3
Severity: grave
Justification: renders package unusable

The upgrade of avahi-daemon failed:

Setting up avahi-daemon (0.7-3) ...
Installing new version of config file /etc/avahi/avahi-daemon.conf ...
Job for avahi-daemon.service failed because the control process exited with 
error code.
See "systemctl  status avahi-daemon.service" and "journalctl  -xe" for details.
invoke-rc.d: initscript avahi-daemon, action "restart" failed.
● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
   Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Thu 2017-09-21 10:21:56 CEST; 6ms 
ago
  Process: 740 ExecStart=/usr/sbin/avahi-daemon -s (code=exited, status=255)
 Main PID: 740 (code=exited, status=255)

Sep 21 10:21:56 zira systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
Sep 21 10:21:56 zira avahi-daemon[740]: Daemon already running on PID 740
Sep 21 10:21:56 zira systemd[1]: avahi-daemon.service: Main process exited, 
code=exited, status=255/n/a
Sep 21 10:21:56 zira systemd[1]: Failed to start Avahi mDNS/DNS-SD Stack.
Sep 21 10:21:56 zira systemd[1]: avahi-daemon.service: Unit entered failed 
state.
Sep 21 10:21:56 zira systemd[1]: avahi-daemon.service: Failed with result 
'exit-code'.
dpkg: error processing package avahi-daemon (--configure):
 subprocess installed post-installation script returned error exit status 1

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

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

Versions of packages avahi-daemon depends on:
ii  adduser  3.116
ii  bind9-host [host]1:9.10.3.dfsg.P4-12.6
ii  dbus 1.11.16+really1.10.22-1
ii  init-system-helpers  1.49
ii  libavahi-common3 0.7-3
ii  libavahi-core7   0.7-3
ii  libc62.24-17
ii  libcap2  1:2.25-1
ii  libdaemon0   0.14-6+b1
ii  libdbus-1-3  1.11.16+really1.10.22-1
ii  libexpat12.2.3-1
ii  lsb-base 9.20170808

Versions of packages avahi-daemon recommends:
ii  libnss-mdns  0.10-8

Versions of packages avahi-daemon suggests:
ii  avahi-autoipd  0.7-3

-- no debconf information

Bug#876274: wordpress: 9 security bugs in wordpress 4.8.1 and earlier

[Ángel]

Salvatore wrote:
> have you identified already the issue -> fixing commit mappings?

For version 4.8.1 [buster, sid], upstream fixed them on 4.8.2
https://codex.wordpress.org/Version_4.8.2

For version 4.7.5 [stretch], upstream fixed them on 4.7.6
https://codex.wordpress.org/Version_4.7.6

For version 4.1 [jessie], upstream fixed them on 4.1.19
https://codex.wordpress.org/Version_4.1.19

For version 3.6.1 [wheezy], upstream didn't release a fix.


4.7.6 and 4.1.19 seem to be security fixes only. WordPress 4.8.2 also
contains six maintenance fixes to the 4.8 release series (but that would
go to sid, so it's ok).

There is a slightly misleading commit message on one of them whose
description says it's bumping to the wrong version, but other than that
-thankfully- it looks quite clear which issue is fixing each of the
backported commits

Processed: retitle 874693 to ES6 syntax in 1.48+ breaks packages that redeclare variables with 'let'

[Debian Bug Tracking System]

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

> retitle 874693 ES6 syntax in 1.48+ breaks packages that redeclare variables 
> with 'let'
Bug #874693 [gjs] breaks other packages
Changed Bug title to 'ES6 syntax in 1.48+ breaks packages that redeclare 
variables with 'let'' from 'breaks other packages'.
> thanks
Stopping processing here.

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

Processed: bug 870834 is forwarded to https://github.com/pavouk/lgi/issues/167

[Debian Bug Tracking System]

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

> forwarded 870834 https://github.com/pavouk/lgi/issues/167
Bug #870834 [src:lua-lgi] lua-lgi FTBFS: test failures
Set Bug forwarded-to-address to 'https://github.com/pavouk/lgi/issues/167'.
> thanks
Stopping processing here.

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

Bug#868719: marked as done (golang-github-couchbase-moss FTBFS: FAIL: TestStoreCollHistograms)

[Debian Bug Tracking System]

Your message dated Thu, 21 Sep 2017 06:19:24 +
with message-id 
and subject line Bug#868719: fixed in golang-github-couchbase-moss 
0.0~git20170828.0.61afce4-1
has caused the Debian Bug report #868719,
regarding golang-github-couchbase-moss FTBFS: FAIL: TestStoreCollHistograms
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.)


-- 
868719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868719
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-couchbase-moss
Version: 0.0~git20170713.0.8ea508f-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=golang-github-couchbase-moss=all=0.0~git20170713.0.8ea508f-1=1500331918=0

...
=== RUN   TestStoreReadOnlyOption
--- PASS: TestStoreReadOnlyOption (0.00s)
=== RUN   TestStoreCollHistograms
--- FAIL: TestStoreCollHistograms (0.02s)
store_test.go:1976: Unexpected number of MutationKeyBytes samples!
store_test.go:1980: Unexpected number of MutationValBytes samples!
store_test.go:1984: Unexpected number of ExecutedBatchBytes samples!
store_test.go:1989: Unexpected number of ExecuteBatchOpsCount samples!
=== RUN   TestStoreCompactMaxSegments
--- PASS: TestStoreCompactMaxSegments (0.06s)
=== RUN   TestStoreCrashRecovery
--- PASS: TestStoreCrashRecovery (0.02s)
FAIL
exit status 1
FAILgithub.com/couchbase/moss   4.043s
dh_auto_test: go test -v -p 4 github.com/couchbase/moss returned exit code 1
debian/rules:4: recipe for target 'build-indep' failed
make: *** [build-indep] Error 1
--- End Message ---
--- Begin Message ---
Source: golang-github-couchbase-moss
Source-Version: 0.0~git20170828.0.61afce4-1

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

Debian distribution maintenance software
pp.
Michael Lustfield  (supplier of updated 
golang-github-couchbase-moss 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, 21 Sep 2017 00:57:57 -0500
Source: golang-github-couchbase-moss
Binary: golang-github-couchbase-moss-dev
Architecture: source
Version: 0.0~git20170828.0.61afce4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Michael Lustfield 
Description:
 golang-github-couchbase-moss-dev - moss provides a fast key/value storage 
library for golang
Closes: 868719
Changes:
 golang-github-couchbase-moss (0.0~git20170828.0.61afce4-1) unstable; 
urgency=medium
 .
   * New upstream revision.
   * Maintenance updates:
 - Update for standards version 4.1.0.0.
 - Add Testsuite to d/control.
   * Skip tests failing on some architectures. (Closes: #868719)
Checksums-Sha1:
 fc682dad5fa2770412e034f5dbd9d6ed6f71f30b 2536 
golang-github-couchbase-moss_0.0~git20170828.0.61afce4-1.dsc
 f68e9278b0cf1f158c16ed34b44a7b58fa493f39 88568 
golang-github-couchbase-moss_0.0~git20170828.0.61afce4.orig.tar.xz
 13e19dc89a7742f20d19bf2d57a91f451376769b 2696 
golang-github-couchbase-moss_0.0~git20170828.0.61afce4-1.debian.tar.xz
 eb61a0589d2bf4e873b36206213cd03828d483b6 6551 
golang-github-couchbase-moss_0.0~git20170828.0.61afce4-1_amd64.buildinfo
Checksums-Sha256:
 15d8e8ca141382dc18ea042520d5481efe4b05f9137cbd42b6bcaf6310f483bb 2536 
golang-github-couchbase-moss_0.0~git20170828.0.61afce4-1.dsc
 7bab3e575ef08eb8b7055ffabd21921efee3e8d21baa155899e317b6d4e67d96 88568 
golang-github-couchbase-moss_0.0~git20170828.0.61afce4.orig.tar.xz
 f6d31b89b3952ebc3ed4a599d19848591636f74c6064d834200b1a4dec3d28ac 2696 
golang-github-couchbase-moss_0.0~git20170828.0.61afce4-1.debian.tar.xz
 b223db3fb566754144a26d1d44108845b578632cdecc89ac07768b87b17bb508 6551 
golang-github-couchbase-moss_0.0~git20170828.0.61afce4-1_amd64.buildinfo
Files:
 20fb17f73d5b0197a6d3240c3f6460fb 2536 devel extra 
golang-github-couchbase-moss_0.0~git20170828.0.61afce4-1.dsc
 6fc8ddf222bda35ca197b398670977e5 88568 devel extra