Bug#873598: spice-gtk: diff for NMU version 0.34-1.1

[Liang Guo]

Hi, Laurent,

On Wed, Aug 30, 2017 at 8:50 PM, Laurent Bigonville  wrote:
> Control: tags 873598 + pending
>
> Dear maintainer,
>
> I've prepared an NMU for spice-gtk (versioned as 0.34-1.1) and
> uploaded it to DELAYED/3. Please feel free to tell me if I
> should delay it longer.
>
> Regards.
> diff -Nru spice-gtk-0.34/debian/changelog spice-gtk-0.34/debian/changelog
> --- spice-gtk-0.34/debian/changelog 2017-08-06 11:02:13.0 +0200
> +++ spice-gtk-0.34/debian/changelog 2017-08-30 14:45:42.0 +0200
> @@ -1,3 +1,13 @@
> +spice-gtk (0.34-1.1) unstable; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * debian/rules: Call the gir sequence so the gir1.2-* packages have the
> +correct dependencies defined. (Closes: #873598)
> +  * Make the gir1.2-* packages Multi-Arch: same
> +  * Add Breaks to force the uninstallation of the old gir1.2-* packages
> +
> + -- Laurent Bigonville   Wed, 30 Aug 2017 14:45:42 +0200
> +
>  spice-gtk (0.34-1) unstable; urgency=medium
>
Please upload 0.34-1 to unstable with no delay.

Thanks for working on spice-gtk.

-- 
Liang Guo
http://guoliang.me/

Processed: tagging 871093

[Debian Bug Tracking System]

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

> tags 871093 + patch
Bug #871093 [src:ruby-rbnacl] ruby-rbnacl: FTBFS: ERROR: Test "ruby2.3" failed.
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#871093: ruby-rbnacl: FTBFS: ERROR: Test "ruby2.3" failed.

[Steve Langasek]

Package: ruby-rbnacl
Version: 5.0.0-1
Followup-For: Bug #871093
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu artful ubuntu-patch autopkgtest

The build failure is caused by a bugfix change in libsodium 1.0.13 that
changed the alignment (and therefore the size) of the blake2b_state struct. 
Please find attached a patch for this issue.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru ruby-rbnacl-5.0.0/debian/patches/fix-blake2b_state-struct-size.patch 
ruby-rbnacl-5.0.0/debian/patches/fix-blake2b_state-struct-size.patch
--- ruby-rbnacl-5.0.0/debian/patches/fix-blake2b_state-struct-size.patch
1969-12-31 16:00:00.0 -0800
+++ ruby-rbnacl-5.0.0/debian/patches/fix-blake2b_state-struct-size.patch
2017-08-30 21:05:40.0 -0700
@@ -0,0 +1,30 @@
+Description: pad blake2b_state struct declaration for libsodium 1.0.13
+ libsodium 1.0.13 includes a bugfix to the alignment of the
+ crypto_generichash_blake2b_state struct, which was supposed to be declared
+ CRYPTO_ALIGN(64).  Non-obviously, this refers to 64 *byte* alignment, not
+ 64 *bit* alignment, and accordingly, initialization functions that try to
+ zero out a struct will walk off the end and scribble on memory if the struct
+ they're passed isn't padded out to a multiple of 64.
+ .
+ The size of this struct rounds up to 384 bytes (6*64).  On a 32-bit system
+ (where sizeof(size_t) == 4), the declared members of the struct only add
+ up to 357 bytes.  Add 27 bytes of padding to our allocated struct, so that
+ we allocate enough memory for either 32-bit or 64-bit architectures.
+ (Ideally we would just declare an alignment for the struct the same as we do
+ in GCC, but this doesn't appear to be supported in ffi.)
+Author: Steve Langasek 
+
+Index: ruby-rbnacl-5.0.0/lib/rbnacl/hash/blake2b.rb
+===
+--- ruby-rbnacl-5.0.0.orig/lib/rbnacl/hash/blake2b.rb
 ruby-rbnacl-5.0.0/lib/rbnacl/hash/blake2b.rb
+@@ -175,7 +175,8 @@
+:f, [:uint64, 2],
+:buf, [:uint8, 2 * 128],
+:buflen, :size_t,
+-   :last_node, :uint8
++   :last_node, :uint8,
++   :padding, [:uint8, 27]
+   end
+ end
+   end
diff -Nru ruby-rbnacl-5.0.0/debian/patches/series 
ruby-rbnacl-5.0.0/debian/patches/series
--- ruby-rbnacl-5.0.0/debian/patches/series 2017-07-08 23:57:19.0 
-0700
+++ ruby-rbnacl-5.0.0/debian/patches/series 2017-08-30 20:51:40.0 
-0700
@@ -3,3 +3,4 @@
 0003-Drop-usage-of-git-in-gemspec.patch
 0004-Drop-gem-dependency-on-rbnacl-libsodium.patch
 0005-Drop-development-dependency-on-bundler.patch
+fix-blake2b_state-struct-size.patch

Bug#873525: mrpt: FTBFS on mips64el: test_mrpt_graphslam fails

[Aaron M. Ucko]

JOSE LUIS BLANCO CLARACO  writes:

> Thanks for reporting this one!

Thanks for looking into it!

> Is there a procedure to request temporary access to such a builder machine?

Yes: https://dsa.debian.org/doc/guest-account/

This procedure is simpler if you're already an official DM, but possible
to arrange regardless.

-- 
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

Bug#873467: marked as done (db5.3: FTBFS on mips64el)

[Debian Bug Tracking System]

Your message dated Thu, 31 Aug 2017 05:00:58 +0200
with message-id <20170831030058.r37y2bwm55ud5dny@eldamar.local>
and subject line Re: Bug#873467: db5.3: FTBFS on mips64el
has caused the Debian Bug report #873467,
regarding db5.3: FTBFS on mips64el
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.)


-- 
873467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873467
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: db5.3
Version: 5.3.28-13
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi

db5.3 FTBFS on mips64el (no futher investigation done):

Log:
https://buildd.debian.org/status/fetch.php?pkg=db5.3=mips64el=5.3.28-13.1=1503890181=0

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Control: notfound -1 5.3.28-13.1

This was given back once on buildds and has builded fine.

Regards,
Salvatore--- End Message ---

Bug#873467: db5.3: FTBFS on mips64el

[Salvatore Bonaccorso]

Control: notfound -1 5.3.28-13.1

This was given back once on buildds and has builded fine.

Regards,
Salvatore

Processed: Re: Bug#873467: db5.3: FTBFS on mips64el

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 5.3.28-13.1
Bug #873467 [src:db5.3] db5.3: FTBFS on mips64el
No longer marked as found in versions db5.3/5.3.28-13.1.

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

Bug#873782: svgpp: FTBFS when not building libsvgpp-doc

[Aaron M. Ucko]

Source: svgpp
Version: 1.2.3+dfsg1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Builds of svgpp covering only its architecture-dependent binary
packages (as on the autobuilders or with dpkg-buildpackage -B) have
been failing:

 debian/rules override_dh_sphinxdoc
  make[1]: Entering directory '/<>/svgpp-1.2.3+dfsg1'
  dh_sphinxdoc
  dh_sphinxdoc: Sphinx documentation not found
  find debian/libsvgpp-doc/usr/share/doc/libsvgpp-doc/html -type f -print0 | 
xargs -0 sed -i 
's/https:\/\/cdn\.mathjax\.org\/mathjax\/latest/\/usr\/share\/javascript\/mathjax/g'
  find: 'debian/libsvgpp-doc/usr/share/doc/libsvgpp-doc/html': No such file or 
directory
  sed: no input files
  debian/rules:18: recipe for target 'override_dh_sphinxdoc' failed
  make[1]: *** [override_dh_sphinxdoc] Error 123
  make[1]: Leaving directory '/<>/svgpp-1.2.3+dfsg1'
  debian/rules:6: recipe for target 'binary-arch' failed
  make: *** [binary-arch] Error 2

Could you please take a look?  It would probably suffice to rename
override_dh_sphinxdoc to override_dh_sphinxdoc-indep.  (Also, you
might consider giving sed an alternative delimiter such as | or , to
avoid needing to escape all the slashes, but that's purely cosmetic.)

Thanks!

FTR, I'm classifying this bug as a regression because it would affect
binNMUs on amd64.

-- 
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

Bug#873778: mozjs52: FTBFS: Failed to test XUL condition

[Aaron M. Ucko]

Source: mozjs52
Version: 52.3.1-3
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)

Builds of mozjs52 for several platforms failed with similar errors, as
detailed at
https://buildd.debian.org/status/logs.php?pkg=mozjs52=52.3.1-3 and
excerpted below.

Could you please take a look?

Thanks!

On armel:

File "/<>/js/src/tests/lib/manifest.py", line 143, in 
_parse_one
  if xul_tester.test(cond):
File "/<>/js/src/tests/lib/manifest.py", line 110, in test
  cond, out, err))
  Exception: Failed to test XUL condition 'Android'; output was '', stderr was 
'Assertion failure: !joinable(), at 
/<>/js/src/threading/Thread.h:122\n'

On mips, s390x, and the non-release architectures powerpc and sparc64:

File "/<>/js/src/tests/lib/manifest.py", line 143, in 
_parse_one
  if xul_tester.test(cond):
File "/<>/js/src/tests/lib/manifest.py", line 110, in test
  cond, out, err))
  Exception: Failed to test XUL condition 'Android'; output was '', stderr was 
''

On the non-release architecture ppc64:

File "/<>/js/src/tests/lib/manifest.py", line 134, in 
_parse_one
  if xul_tester.test(cond):
File "/<>/js/src/tests/lib/manifest.py", line 110, in test
  cond, out, err))
  Exception: Failed to test XUL condition '!xulRuntime.shell'; output was '', 
stderr was ''

-- 
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

Bug#871141: marked as done (pygobject: FTBFS: regress.c:3448:3: error: no previous prototype for '_regress_test_fundamental_hidden_sub_object_get_type' [-Werror=missing-prototypes])

[Debian Bug Tracking System]

Your message dated Thu, 31 Aug 2017 01:52:09 +
with message-id 
and subject line Bug#870837: fixed in pygobject 3.24.1-3
has caused the Debian Bug report #870837,
regarding pygobject: FTBFS: regress.c:3448:3: error: no previous prototype for 
'_regress_test_fundamental_hidden_sub_object_get_type' 
[-Werror=missing-prototypes]
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.)


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

Hi,

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

Relevant part (hopefully):
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
> -I../../tests -I..   -Wdate-time -D_FORTIFY_SOURCE=2  -pthread 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 
> -I/usr/include/libpng16 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -Werror=unused-variable -fno-strict-aliasing 
> -Werror=declaration-after-statement  -Wall -Wstrict-prototypes 
> -Wnested-externs -Werror=missing-prototypes 
> -Werror=implicit-function-declaration -Werror=pointer-arith -Werror=init-self 
> -Werror=format-security -Werror=format=2 -Werror=missing-include-dirs 
> -Werror=return-type   -c -o libregress_la-regress.lo `test -f 
> '/usr/share/gobject-introspection-1.0/tests/regress.c' || echo 
> '../../tests/'`/usr/share/gobject-introspection-1.0/tests/regress.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../tests -I.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -pthread -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/cairo 
> -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -Werror=unused-variable -fno-strict-aliasing 
> -Werror=declaration-after-statement -Wall -Wstrict-prototypes 
> -Wnested-externs -Werror=missing-prototypes 
> -Werror=implicit-function-declaration -Werror=pointer-arith -Werror=init-self 
> -Werror=format-security -Werror=format=2 -Werror=missing-include-dirs 
> -Werror=return-type -c /usr/share/gobject-introspection-1.0/tests/regress.c  
> -fPIC -DPIC -o .libs/libregress_la-regress.o
> /usr/share/gobject-introspection-1.0/tests/regress.c:3448:3: error: no 
> previous prototype for '_regress_test_fundamental_hidden_sub_object_get_type' 
> [-Werror=missing-prototypes]
>_regress_test_fundamental_hidden_sub_object_get_type
>^
> /usr/share/gobject-introspection-1.0/tests/regress.c:3448:3: note: in 
> definition of macro 'regress_test_fundamental_hidden_sub_object_get_type'
>_regress_test_fundamental_hidden_sub_object_get_type
>^~~~
> /usr/include/glib-2.0/gobject/gtype.h:1994:3: note: in expansion of macro 
> '_G_DEFINE_TYPE_EXTENDED_BEGIN_PRE'
>_G_DEFINE_TYPE_EXTENDED_BEGIN_PRE(TypeName, type_name, TYPE_PARENT) \
>^
> /usr/include/glib-2.0/gobject/gtype.h:1737:60: note: in expansion of macro 
> '_G_DEFINE_TYPE_EXTENDED_BEGIN'
>  #define G_DEFINE_TYPE_EXTENDED(TN, t_n, T_P, _f_, _C_) 
> _G_DEFINE_TYPE_EXTENDED_BEGIN (TN, t_n, T_P, _f_) {_C_;} 
> _G_DEFINE_TYPE_EXTENDED_END()
> 
> ^
> /usr/include/glib-2.0/gobject/gtype.h:1595:43: note: in expansion of macro 
> 'G_DEFINE_TYPE_EXTENDED'
>  #define G_DEFINE_TYPE(TN, t_n, T_P)   G_DEFINE_TYPE_EXTENDED (TN, t_n, 
> T_P, 0, {})
>^~
> /usr/share/gobject-introspection-1.0/tests/regress.c:3456:1: note: in 
> expansion of macro 'G_DEFINE_TYPE'
>  G_DEFINE_TYPE (RegressTestFundamentalHiddenSubObject,
>  ^
> cc1: some warnings being treated as errors
> Makefile:567: recipe for target 'libregress_la-regress.lo' failed
> make[4]: *** [libregress_la-regress.lo] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/pygobject_3.22.0-2_unstable.log

A list of current common 

Bug#870837: marked as done (/usr/share/gobject-introspection-1.0/tests/regress.c:3448:3: error: no previous prototype for '_regress_test_fundamental_hidden_sub_object_get_type')

[Debian Bug Tracking System]

Your message dated Thu, 31 Aug 2017 01:52:09 +
with message-id 
and subject line Bug#870837: fixed in pygobject 3.24.1-3
has caused the Debian Bug report #870837,
regarding /usr/share/gobject-introspection-1.0/tests/regress.c:3448:3: error: 
no previous prototype for '_regress_test_fundamental_hidden_sub_object_get_type'
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.)


-- 
870837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870837
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gobject-introspection
Version: 1.53.2-4
Severity: serious
Control: affects -1 src:pygobject

pygobject FTBFS:

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

...
/usr/share/gobject-introspection-1.0/tests/regress.c:3448:3: error: no previous 
prototype for '_regress_test_fundamental_hidden_sub_object_get_type' 
[-Werror=missing-prototypes]
   _regress_test_fundamental_hidden_sub_object_get_type
   ^
/usr/share/gobject-introspection-1.0/tests/regress.c:3448:3: note: in 
definition of macro 'regress_test_fundamental_hidden_sub_object_get_type'
   _regress_test_fundamental_hidden_sub_object_get_type
   ^~~~
/usr/include/glib-2.0/gobject/gtype.h:1994:3: note: in expansion of macro 
'_G_DEFINE_TYPE_EXTENDED_BEGIN_PRE'
   _G_DEFINE_TYPE_EXTENDED_BEGIN_PRE(TypeName, type_name, TYPE_PARENT) \
   ^
/usr/include/glib-2.0/gobject/gtype.h:1737:60: note: in expansion of macro 
'_G_DEFINE_TYPE_EXTENDED_BEGIN'
 #define G_DEFINE_TYPE_EXTENDED(TN, t_n, T_P, _f_, _C_) 
_G_DEFINE_TYPE_EXTENDED_BEGIN (TN, t_n, T_P, _f_) {_C_;} 
_G_DEFINE_TYPE_EXTENDED_END()

^
/usr/include/glib-2.0/gobject/gtype.h:1595:43: note: in expansion of macro 
'G_DEFINE_TYPE_EXTENDED'
 #define G_DEFINE_TYPE(TN, t_n, T_P)   G_DEFINE_TYPE_EXTENDED (TN, t_n, 
T_P, 0, {})
   ^~
/usr/share/gobject-introspection-1.0/tests/regress.c:3456:1: note: in expansion 
of macro 'G_DEFINE_TYPE'
 G_DEFINE_TYPE (RegressTestFundamentalHiddenSubObject,
 ^
cc1: some warnings being treated as errors
...


This is only a FTBFS due to -Werror, but it looks like a bug in
gobject-introspection that should be fixed (and this is also a
warning when building src:gobject-introspection).
--- End Message ---
--- Begin Message ---
Source: pygobject
Source-Version: 3.24.1-3

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

Debian distribution maintenance software
pp.
Iain Lane  (supplier of updated pygobject 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: Thu, 31 Aug 2017 00:29:26 +0100
Source: pygobject
Binary: python-gi python3-gi python-gi-cairo python-gi-dbg python3-gi-dbg 
python-gi-dev python3-gi-cairo python-gobject python-gobject-dbg 
python-gobject-dev
Architecture: source
Version: 3.24.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Iain Lane 
Description:
 python-gi  - Python 2.x bindings for gobject-introspection libraries
 python-gi-cairo - Python Cairo bindings for the GObject library
 python-gi-dbg - Python bindings for the GObject library (debug extension)
 python-gi-dev - development headers for GObject Python bindings
 python-gobject - Python 2.x bindings for GObject - transitional package
 python-gobject-dbg - Python 2.x debugging modules for GObject - transitional 
package
 python-gobject-dev - Python 2.x development headers for GObject - transitional 
package
 python3-gi - Python 3 bindings for gobject-introspection libraries
 python3-gi-cairo - Python 3 Cairo bindings for the GObject library
 python3-gi-dbg - Python 3 bindings for gobject-introspection libraries (debug 
exte
Closes: 870837
Changes:
 pygobject (3.24.1-3) unstable; 

Bug#870837: pygobject FTBFS

[Jeremy Bicha]

Control: reassign -1 pygobject 3.22.0-2

pygobject simply needs to be updated.

Thanks,
Jeremy Bicha

Processed: Re: pygobject FTBFS

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 pygobject 3.22.0-2
Bug #870837 [src:gobject-introspection] 
/usr/share/gobject-introspection-1.0/tests/regress.c:3448:3: error: no previous 
prototype for '_regress_test_fundamental_hidden_sub_object_get_type'
Bug #871141 [src:gobject-introspection] pygobject: FTBFS: regress.c:3448:3: 
error: no previous prototype for 
'_regress_test_fundamental_hidden_sub_object_get_type' 
[-Werror=missing-prototypes]
Bug reassigned from package 'src:gobject-introspection' to 'pygobject'.
Bug reassigned from package 'src:gobject-introspection' to 'pygobject'.
No longer marked as found in versions gobject-introspection/1.53.2-4.
No longer marked as found in versions gobject-introspection/1.53.2-4.
Ignoring request to alter fixed versions of bug #870837 to the same values 
previously set
Ignoring request to alter fixed versions of bug #871141 to the same values 
previously set
Bug #870837 [pygobject] 
/usr/share/gobject-introspection-1.0/tests/regress.c:3448:3: error: no previous 
prototype for '_regress_test_fundamental_hidden_sub_object_get_type'
Bug #871141 [pygobject] pygobject: FTBFS: regress.c:3448:3: error: no previous 
prototype for '_regress_test_fundamental_hidden_sub_object_get_type' 
[-Werror=missing-prototypes]
There is no source info for the package 'pygobject' at version '3.22.0-2' with 
architecture ''
Unable to make a source version for version '3.22.0-2'
Marked as found in versions 3.22.0-2.
Marked as found in versions 3.22.0-2.

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

Bug#873627: udisks2 in sid apparently left me with a borked system in plasma(?)

[Ben Caradoc-Davies]

udisks2 is now uninstallable on sid because of #873748:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873748

Kind regards,

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

Bug#873589: marked as done (clearsilver: FTBFS on arm64, mips*, ppc64el during clean - unable to guess system type)

[Debian Bug Tracking System]

Your message dated Thu, 31 Aug 2017 00:19:36 +
with message-id 
and subject line Bug#873589: fixed in clearsilver 0.10.5-3
has caused the Debian Bug report #873589,
regarding clearsilver: FTBFS on arm64, mips*, ppc64el during clean - unable to 
guess system type
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.)


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

Hi,

clearsilver FTBFS on arm64, mips* and ppc64el with this error:
> checking build system type... ./config.guess: unable to guess system type
> 
> This script, last modified 2001-09-04, has failed to recognize
> the operating system you are using. It is advised that you
> download the most up to date version of the config scripts from
> 
> ftp://ftp.gnu.org/pub/gnu/config/
> 
> If the version you run (./config.guess) is already up to date, please
> send the following data and any information you think might be
> pertinent to  in order to provide the needed
> information to handle your system.
> 
> config.guess timestamp = 2001-09-04

This happens during the "clean" phase of the build:
>  fakeroot debian/rules clean
> dh clean --with python2
>dh_auto_clean
>   make -j6 distclean
> make[1]: Entering directory '/<>'
> Makefile:10: rules.mk: No such file or directory
> ./configure
> checking for gcc... gcc

Calling "make distclean" should probably be skipped if rules.mk does not
exist so that the configure script isn't run.

Thanks,
James



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: clearsilver
Source-Version: 0.10.5-3

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

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

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

Debian distribution maintenance software
pp.
Adam Borowski  (supplier of updated clearsilver 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: Thu, 31 Aug 2017 01:54:40 +0200
Source: clearsilver
Binary: clearsilver-dev python-clearsilver libclearsilver-perl
Architecture: source
Version: 0.10.5-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adam Borowski 
Description:
 clearsilver-dev - headers and static library for clearsilver
 libclearsilver-perl - Perl bindings for clearsilver
 python-clearsilver - Python bindings for clearsilver
Closes: 873589
Changes:
 clearsilver (0.10.5-3) unstable; urgency=medium
 .
   * QA upload.
   * Run "make distclean" only if rules.mk exists; fixes FTBFS on arm64 mips*
 ppc64el.  Closes: #873589
Checksums-Sha1:
 7c4fb41847a2158d4cb9ee666e82ad7432ed013b 1613 clearsilver_0.10.5-3.dsc
 38adf5bc9beb24b0168004741b54d70bc782dfdc 7944 
clearsilver_0.10.5-3.debian.tar.xz
 5d4aac14ec261770076b31dcd09a85f10a845f7a 5801 
clearsilver_0.10.5-3_source.buildinfo
Checksums-Sha256:
 705788beaca60f754f7874407b9742f236567ab2cb731e7980e94ebca37c7f4a 1613 
clearsilver_0.10.5-3.dsc
 98d2b769dfff832a93e53b39961ce6a3b43e93b6838b6af559d3fe32a94c12ab 7944 
clearsilver_0.10.5-3.debian.tar.xz
 1b4966123e589840fe75f23de36e5e7078a958ef2abc66b27bf654a80136 5801 
clearsilver_0.10.5-3_source.buildinfo
Files:
 678292fd2f4e3d9e96bafffe3ec4eaf2 1613 devel optional clearsilver_0.10.5-3.dsc
 e099fbda9bb7ae04612b2245d795970a 7944 devel optional 
clearsilver_0.10.5-3.debian.tar.xz
 dbaf05d3dda8cd39c2a71516370ae6f5 5801 devel optional 
clearsilver_0.10.5-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFIBAEBCgAyFiEE/Zzi2Nd1S3irJ5u9LDtDb+rGgQEFAlmnUFYUHGtpbG9ieXRl
QGFuZ2JhbmQucGwACgkQLDtDb+rGgQGLyAf/dQ4vK7uUw+5ve7N9s9k6u8KReAt8
dLcBqHTaZHPf/7+cbdRfZMZi5jv1Qd5H2Evtf/qD9dnYP/8aF7UQ/QGlP9IKSPIm
RH+dLGY5iQjdlSv5LRKuAkx2t31pzl4CvW5TbgM2cJpyzRwxDyRoufEnV+ZM01C9
jtmAZ3t2bPimGteo/yfwbjOFTfzOlHVKWdb7Y70tvKXLFnbh6RgxjzyrvvPWXCqu
zCula5T9GWoJILbm43RDL4b7CKAs6UXe41Zkx4Dz58QUhqEiHthwiuZhpwad0sK0

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

[Christopher Li]

On Wed, Aug 30, 2017 at 1:36 PM, Uwe Kleine-König  
wrote:
>> >
>> > diff --git a/validation/backend/sum.c b/validation/backend/sum.c
>> > index 0604299..d0be8dd 100644
>> > --- a/validation/backend/sum.c
>> > +++ b/validation/backend/sum.c
>> > @@ -1,3 +1,5 @@
>> > +#define __powerpc64__
>> > +#define _CALL_ELF 2
>> >  #include 
>> >  #include 
>> >
>> >
>>
>> Yep, sparse/sparsec do not define various macros that gcc/clang define
>> by default on a given architecture. This is a known problem (that I have
>> been meaning to fix ...). The 'workaround' for the time being is to use
>> the cgcc front-end to sparse. (for example 'make CC=cgcc', or perhaps
>> 'cgcc -no-compile').
>>
>> [You didn't mention your usage - is this for a kernel build?]
>
> This problem became visible during the make check phase when creating packaged
> on the listed archs for horst[1]. You can see a build logs at
>
> 
> https://buildd.debian.org/status/fetch.php?pkg=horst=s390x=5.0-1=1503905687=0
> 
> https://buildd.debian.org/status/fetch.php?pkg=horst=ppc64el=5.0-1=1503906226=0
>
> The error message looks identical (I checked the ppc64el log) to the
> problem with backend/sum.c:
>
> sparse -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -std=gnu99 -Wall 
> -Wextra -g -I. -DDO_DEBUG -I/usr/include/libnl3 *.[ch]
> /usr/include/powerpc64le-linux-gnu/gnu/stubs.h:8:12: error: unable to 
> open 'gnu/stubs-32.h'

That is very much like on x86_64 missing define "#weak_define __x86_64__ 1"

Does cgcc work for you? In the future we do want to move the archetecture
related define from cgcc into sparse by itself. For now you can set
"sparse" as "cgcc -no-compile"

Chris

Bug#840540: Raising severity

[Lisandro Damián Nicanor Pérez Meyer]

On 30 August 2017 at 18:49, Mònica Ramírez Arceda  wrote:
> Hi!
>
> On 30/08/17 23:34, Lisandro Damián Nicanor Pérez Meyer wrote:
>> Control: severity -1 serious
>>
>> Hi! I have just uploaded qoauth to unstable thus starting the transition. I 
>> don't mind nmuing dianara, feel free to ask me so. I'll do it if I don't get 
>> any answer in ~2 days.
> Sorry for the delayed answer. I will try to upload dianara tomorrow. If I 
> don't do it, feel free to NMU!
>
> Thanks!

Gracias a vos!

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

Bug#873525: mrpt: FTBFS on mips64el: test_mrpt_graphslam fails

[JOSE LUIS BLANCO CLARACO]

Dear Aaron,  (cc: Santiago)

Thanks for reporting this one!

I spent some time debugging this issue raised in mips64el and the only
suspicious operations in that code area (detected with GCC sanitizers)
have been fixed upstream with the patch in [1].

Unfortunately, I have no easy way (qemu aside...) to test the
compilation of the package in this architecture to assess whether the
bug has really gone; realistically, the bug might probably still be
there, and more testing would be required.

I found out [2] that there is one porter box named "eller.debian.org"
which may be useful to debug this issue...
Is there a procedure to request temporary access to such a builder machine?

Last year I read about this same topic and arrived to the conclusion
that "the way" was to apply to become a "Debian Maintainer"... what do
you think about this?

Best,
JL

[1] https://github.com/MRPT/mrpt/commit/440e1d8aa677933f7954c4ae4f0b086fa4e24761
[2] 
https://wiki.debian.org/MIPSPort?action=show=mips64el#Development_Team
[3] https://wiki.debian.org/DebianMaintainer#Becoming_a_Debian_Maintainer


On Mon, Aug 28, 2017 at 8:11 PM, Aaron M. Ucko  wrote:
> Source: mrpt
> Version: 1:1.5.3-1
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
>
> The latest mips64el build of mrpt failed:
>
>   cd /<>/obj-mips64el-linux-gnuabi64/tests && 
> ./test_mrpt_graphslam
>   [==] Running 4 tests from 2 test cases.
>   [--] Global test environment set-up.
>   [--] 2 tests from GraphSlamLevMarqTester2D
>   [ RUN  ] GraphSlamLevMarqTester2D.OptimizeSampleRingPath
>   /<>/libs/graphslam/src/graph_slam_levmarq_unittest.cpp:59: 
> Failure
>   Expected: (levmarq_info.final_total_sq_error) <= (1e-2), actual: 534.008 vs 
> 0.01
>   Bus error
>   tests/CMakeFiles/run_tests_mrpt_graphslam.dir/build.make:60: recipe for 
> target 'tests/CMakeFiles/run_tests_mrpt_graphslam' failed
>
> 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

-- 
___

Jose Luis Blanco-Claraco
Universidad de Almería - Departamento de Ingeniería
https://w3.ual.es/~jlblanco/
https://github.com/jlblancoc
___

Bug#825220: marked as done (fwanalog: please Build-Depend on rename)

[Debian Bug Tracking System]

Your message dated Wed, 30 Aug 2017 23:49:46 +
with message-id 
and subject line Bug#825220: fixed in fwanalog 0.6.9-8
has caused the Debian Bug report #825220,
regarding fwanalog: please Build-Depend on rename
to be marked as done.

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

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


-- 
825220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825220
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fwanalog
Version: 0.6.9-7
Severity: normal
User: debian-p...@lists.debian.org
Usertags: perl-5.24-transition rename-deprecation

Dear maintainer,

This package was found to contain uses of the 'rename' and/or 'prename'
(which is an alias) command. This was previously implemented by a script
added to the perl package by Debian, but there is now a maintained
alternative in the 'rename' package.

Please add a Build-Depends on 'rename', to avoid breakage in your
package when we remove the rename script from the perl package
(expected after the release of stretch). Additionally, if you are
currently using 'prename', please use 'rename' (which is handled by the
alternatives mechanism) or file-rename, which is the new implementation.

You can see more background about this change at
.

Thanks,
Dominic

Details of the use of (p)rename in your package follow:

debian/rules
39: ( cd debian/fwanalog/usr/lib/fwanalog ; rename 's/\.sh//' *.sh )
--- End Message ---
--- Begin Message ---
Source: fwanalog
Source-Version: 0.6.9-8

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

Debian distribution maintenance software
pp.
Adam Borowski  (supplier of updated fwanalog 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: Thu, 31 Aug 2017 01:22:27 +0200
Source: fwanalog
Binary: fwanalog
Architecture: source
Version: 0.6.9-8
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adam Borowski 
Description:
 fwanalog   - firewall log-file report generator (using analog)
Closes: 825220
Changes:
 fwanalog (0.6.9-8) unstable; urgency=medium
 .
   * QA upload.
   * Build-Depend on rename. (Closes: #825220)
   * Use debhelper 10.
   * Fix a typo in README.Debian
Checksums-Sha1:
 229616722c2928ed11d4c53e6ebdd3d982fb6909 1320 fwanalog_0.6.9-8.dsc
 7e1b3e99ce1e1ebe46fab0a2e27e0c14c3cd526f 22743 fwanalog_0.6.9-8.diff.gz
 fd142a662737c9073cf590641bdc63e121fa8617 5265 fwanalog_0.6.9-8_source.buildinfo
Checksums-Sha256:
 4d6845954e468bfef8d3bfca0f4131528868234f860137766a257cf868424570 1320 
fwanalog_0.6.9-8.dsc
 9f39f9e187dfb723053c0f165dce4075d7863b20648cf5bc414f0385f505251a 22743 
fwanalog_0.6.9-8.diff.gz
 226dab6bd1014ef8c5add61d4c6d2ed99956ad5e68ce9dd54dfd15136d91bab9 5265 
fwanalog_0.6.9-8_source.buildinfo
Files:
 ef495abd23b651a87d998e5e26c536a4 1320 net optional fwanalog_0.6.9-8.dsc
 8ee5a1c7a0bd36a00792f137b1608faa 22743 net optional fwanalog_0.6.9-8.diff.gz
 9e76a4a5d30418a6511676b97f5c5ae9 5265 net optional 
fwanalog_0.6.9-8_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEE/Zzi2Nd1S3irJ5u9LDtDb+rGgQEFAlmnSUUACgkQLDtDb+rG
gQFTOgf/axgkZfN2K/M5ezj1XVgXzCvntFcwEuVgQ9ea1/Kr/vBoChczNdqU5d7o
51IUCRgEyXV8nZu7oT0fwPpQu05eCv4BTDJU4b8UmOOfdUVXTmi2KytLG+/l8k0S
UxzxiARI6x55wBxc5UjXSnD8Xh4GCDExW2hxngXsqHw0ovzSm5mHbm9JBm+pR2O9
ZgSi6qlu8cq0v0vG8BzPpuXjGpgZ0kk/Ev6uL3xx8jQoPy3Fn0GYoNioayVOxDM5
WnlADZdtj3Afonr0a8S7SY1fb3jyZSzpM6HzF5P7ja+9nAMiBH8MtJ5s/ZKYRm5D
OzMnfCzMh2bSps+yyaS3IRT1JGxymA==
=zCh9
-END PGP SIGNATURE End Message ---

Processed: Re: gnome-tweak-tool: Error on start: GLib-GIO-ERROR

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #873765 [gnome-tweak-tool] gnome-tweak-tool: Error on start: GLib-GIO-ERROR 
**: Settings schema 'org.gnome.shell' does not contain a key named 
'disable-user-extensions'
Severity set to 'serious' from 'important'

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

Processed: Re: libanthyinput0: fails to upgrade from 'sid' - trying to overwrite /usr/lib/x86_64-linux-gnu/libanthyinput.so.0.0.0'

[Debian Bug Tracking System]

Processing control commands:

> affects -1 ibus-anthy
Bug #789927 {Done: NIIBE Yutaka } [libanthyinput0] 
libanthyinput0: fails to upgrade from 'sid' - trying to overwrite 
/usr/lib/x86_64-linux-gnu/libanthyinput.so.0.0.0'
Added indication that 789927 affects ibus-anthy
> found -1 ibus-anthy/1.5.9-2
Bug #789927 {Done: NIIBE Yutaka } [libanthyinput0] 
libanthyinput0: fails to upgrade from 'sid' - trying to overwrite 
/usr/lib/x86_64-linux-gnu/libanthyinput.so.0.0.0'
Marked as found in versions ibus-anthy/1.5.9-2.
> found -1 anthy/1:0.3-5
Bug #789927 {Done: NIIBE Yutaka } [libanthyinput0] 
libanthyinput0: fails to upgrade from 'sid' - trying to overwrite 
/usr/lib/x86_64-linux-gnu/libanthyinput.so.0.0.0'
Marked as found in versions anthy/1:0.3-5; no longer marked as fixed in 
versions anthy/1:0.3-5 and reopened.

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

Bug#789927: libanthyinput0: fails to upgrade from 'sid' - trying to overwrite /usr/lib/x86_64-linux-gnu/libanthyinput.so.0.0.0'

[astian]

Control: affects -1 ibus-anthy
Control: found -1 ibus-anthy/1.5.9-2
Control: found -1 anthy/1:0.3-5

Hi,

Packaging is still broken on sid.  (Interesting how 2 years of forewarning
were still not sufficient to prevent this.)

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

  The following packages have unmet dependencies:
   ibus-anthy : Depends: libanthy0 but it is not going to be installed
  E: Unable to correct problems, you have held broken packages.

Note: I have *not* held packages.

Anyway, it seems to me that the problem is not difficult to identify (though I
can't give great insight about the solution): it is obvious that the groups of
packages  and  conflict, yet there are
many (IME-related) packages (such as ibus-anthy, or kasumi) that depend on
both "anthy" (which now pulls in libanthy1 and libanthyinput0) and
"libanthy0", which is an unworkable situation.

Now, I wonder, why does libanthy0 have to still exist (in parallel to the new
libanthy1 and libanthyinput0)?  Why not simply replacing the dependency in all
packages dependent on libanthy0 (and then maybe even removing libanthy0)?
Just thinking out loud.

You might want to take a look at the graph below showing some anthy-related
dependencies on Debian unstable (I had to edit it by hand because both
"apt-cache dotty" and "debtree" are too under-featured).

Thanks.

--

digraph packages {
concentrate=true;
size="30,40";
"ibus-anthy" -> "anthy";
"ibus-anthy" -> "ibus";
"libanthyinput0" -> "libanthy1";
"libanthyinput0" -> "anthy"[color=springgreen];
"anthy" -> "anthy-common";
"anthy" -> "libanthy1";
"anthy" -> "libanthyinput0";
"anthy" -> "anthy-common"[color=springgreen];
"libanthy0" -> "anthy-common";
"libanthy1" -> "anthy-common";

"uim-dict-gtk3" -> "libanthy0";
"uim-dict-gtk" -> "libanthy0";
"uim-anthy" -> "libanthy0";
"hime-anthy" -> "libanthy0";
"gcin-anthy" -> "libanthy0";
"uim-dict-gtk3" -> "libanthy0";
"uim-dict-gtk" -> "libanthy0";
"uim-anthy" -> "libanthy0";
"fcitx-anthy" -> "libanthy0";
"uim-dict-gtk3" -> "libanthy0";
"uim-dict-gtk" -> "libanthy0";
"uim-anthy" -> "libanthy0";
"scim-anthy" -> "libanthy0";
"m17n-lib-mimx" -> "libanthy0";
"ibus-anthy" -> "libanthy0";
"hime-anthy" -> "libanthy0";
"gcin-anthy" -> "libanthy0";
"kasumi" -> "libanthy0";

"ibus-anthy" [shape=box];
"anthy-common" [shape=box];
"ibus" [color=orange,shape=box];
"libanthyinput0" [shape=box];
"anthy" [shape=box];
"libanthy0" [shape=box];
"libanthy1" [shape=box];

"uim-dict-gtk3" [shape=box];
"uim-dict-gtk" [shape=box];
"uim-anthy" [shape=box];
"hime-anthy" [shape=box];
"gcin-anthy" [shape=box];
"uim-dict-gtk3" [shape=box];
"uim-dict-gtk" [shape=box];
"uim-anthy" [shape=box];
"fcitx-anthy" [shape=box];
"uim-dict-gtk3" [shape=box];
"uim-dict-gtk" [shape=box];
"uim-anthy" [shape=box];
"scim-anthy" [shape=box];
"m17n-lib-mimx" [shape=box];
"hime-anthy" [shape=box];
"gcin-anthy" [shape=box];
"kasumi" [shape=box];
}

Bug#873345: marked as done (bugwarrior: Fix hard-coded reference to python3.5)

[Debian Bug Tracking System]

Your message dated Wed, 30 Aug 2017 22:19:31 +
with message-id 
and subject line Bug#873345: fixed in bugwarrior 1.5.1-2
has caused the Debian Bug report #873345,
regarding bugwarrior: Fix hard-coded reference to python3.5
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.)


-- 
873345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873345
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bugwarrior
Version: 1.5.1-1
Severity: serious
Tags: patch
Justification: FTBFS
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu artful ubuntu-patch

bugwarrior 1.5.1-1 has a hard-coded reference to python3.5 in debian/rules. 
The transition to python3.6 is already in progress in Debian unstable, and
this will imminently become a build failure in unstable because python3-all
will no longer depend on python3.5.

   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mkdir test_home
HOME=`pwd`/test_home LC_ALL=C.UTF-8 python3.5 -m nose
/bin/sh: 1: python3.5: not found
debian/rules:11: recipe for target 'override_dh_auto_test' failed

python3.5 has already been dropped from Ubuntu, so I've applied the attached
patch and uploaded there.

Since bugwarrior does build-depend on python3-all rather than on python3,
it's possible you want to do something with py3versions here instead in
order to test against all currently supported versions of python3.  However,
this is only relevant a small percentage of the release cycle, so is IMHO of
lesser importance than just making the package buildable.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru bugwarrior-1.5.1/debian/rules bugwarrior-1.5.1/debian/rules
--- bugwarrior-1.5.1/debian/rules   2017-08-21 03:40:46.0 -0700
+++ bugwarrior-1.5.1/debian/rules   2017-08-26 13:24:00.0 -0700
@@ -9,7 +9,7 @@
 
 override_dh_auto_test:
mkdir test_home
-   HOME=`pwd`/test_home LC_ALL=C.UTF-8 python3.5 -m nose
+   HOME=`pwd`/test_home LC_ALL=C.UTF-8 python3 -m nose
 
 override_dh_auto_clean:
-rm -rf test_home
--- End Message ---
--- Begin Message ---
Source: bugwarrior
Source-Version: 1.5.1-2

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

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

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

Debian distribution maintenance software
pp.
Iain R. Learmonth  (supplier of updated bugwarrior package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 30 Aug 2017 22:30:48 +0100
Source: bugwarrior
Binary: bugwarrior
Architecture: source all
Version: 1.5.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Tasktools Packaging Team 

Changed-By: Iain R. Learmonth 
Description:
 bugwarrior - Pull tickets from bug trackers into taskwarrior
Closes: 873345
Changes:
 bugwarrior (1.5.1-2) unstable; urgency=medium
 .
   * debian/rules:
- Use python3 not python3.5 for tests (Closes: #873345)
Checksums-Sha1:
 65b5cbcff453a2f66c78934a5285e00ca80ef092 2260 bugwarrior_1.5.1-2.dsc
 dc439afa080e682855bf7a833fa30072d21e5ebd 12080 bugwarrior_1.5.1-2.debian.tar.xz
 598e3ad0721e823874a9daa7f61fd2b7f59ac484 98830 bugwarrior_1.5.1-2_all.deb
 fd3469187659ec4f3856eb4bc70e1d11bd2f169e 7605 
bugwarrior_1.5.1-2_amd64.buildinfo
Checksums-Sha256:
 97a85799fea8ebb80ad0549b5f86be7d6b32d7be636830dca7d99b589898a396 2260 
bugwarrior_1.5.1-2.dsc
 ca4e63a357db2cc4d754b8f3fff3be32233ddf390ab7354d850797b44ca33ca0 12080 
bugwarrior_1.5.1-2.debian.tar.xz
 e1712836e8af69dde4c465aa1163ea0bf9e256feb4ff21714d963ba5476c603b 98830 
bugwarrior_1.5.1-2_all.deb
 1ac91728537864378060141a7b43c5a3e659a72fedc1775298be59a96b0fb04d 7605 
bugwarrior_1.5.1-2_amd64.buildinfo
Files:
 08f3479cfb293d14e4ae29297d0cc285 2260 utils optional 

Bug#840540: Raising severity

[Mònica Ramírez Arceda]

Hi!

On 30/08/17 23:34, Lisandro Damián Nicanor Pérez Meyer wrote:
> Control: severity -1 serious
>
> Hi! I have just uploaded qoauth to unstable thus starting the transition. I 
> don't mind nmuing dianara, feel free to ask me so. I'll do it if I don't get 
> any answer in ~2 days.
Sorry for the delayed answer. I will try to upload dianara tomorrow. If I don't 
do it, feel free to NMU!

Thanks!

Processed: Raising severity

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #840540 [dianara] dianara: Please update to v1.3.5 to allow switching 
qoauth to qt5
Severity set to 'serious' from 'wishlist'

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

Bug#873583: marked as done (tortoisehg: needs update for mercurial 4.3)

[Debian Bug Tracking System]

Your message dated Wed, 30 Aug 2017 21:00:12 +
with message-id 
and subject line Bug#873583: fixed in tortoisehg 4.3.1-1
has caused the Debian Bug report #873583,
regarding tortoisehg: needs update for mercurial 4.3
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.)


-- 
873583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873583
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tortoisehg
Version: 4.0-1
Severity: serious
X-Debbugs-Cc: Tristan Seligmann 

tortoisehg depends on mercurial (<< 4.1~).

mercurial's recently fixed security issues are currently held up in
unstable because of this.

Cheers,
Julien
--- End Message ---
--- Begin Message ---
Source: tortoisehg
Source-Version: 4.3.1-1

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

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

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

Debian distribution maintenance software
pp.
Ludovico Cavedon  (supplier of updated tortoisehg 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, 30 Aug 2017 12:25:56 +0200
Source: tortoisehg
Binary: tortoisehg tortoisehg-nautilus tortoisehg-caja
Architecture: source all
Version: 4.3.1-1
Distribution: unstable
Urgency: medium
Maintainer: Ludovico Cavedon 
Changed-By: Ludovico Cavedon 
Description:
 tortoisehg - Graphical tool for working with Mercurial
 tortoisehg-caja - Graphical tool for working with Mercurial (Caja extension)
 tortoisehg-nautilus - Graphical tool for working with Mercurial (Nautilus 
extension)
Closes: 873583
Changes:
 tortoisehg (4.3.1-1) unstable; urgency=medium
 .
   * Imported Upstream version 4.3.1 (Closes: #873583).
   * Update upstream homepage URL.
   * Update copyright dates.
   * Update dependency on Mercurial.
   * Add tortoisehg-caja (LP: #1371956).
   * Bump Standards-Version to 4.1.0.
   * Support nodoc in DEB_BUILD_OPTIONS.
Checksums-Sha1:
 01d1c372fa7cd0755c3aa363e96e121a45adda35 2147 tortoisehg_4.3.1-1.dsc
 23e84271a8f3ee68778b425a6ce0c64fa9c1904b 7930491 tortoisehg_4.3.1.orig.tar.gz
 d91b2260263cfae09a43c2c92459fc65728e5858 17216 tortoisehg_4.3.1-1.debian.tar.xz
 fcbf816bcfafdff263210d7c52b2ea7e30920223 14982 tortoisehg-caja_4.3.1-1_all.deb
 ca5a8d947f124b780701439ebf7296083faccde2 14888 
tortoisehg-nautilus_4.3.1-1_all.deb
 0c1cbb5937ca123bc88601ab2d9ec87dd9df218e 2431874 tortoisehg_4.3.1-1_all.deb
 6fa3cf59f5979b0d22084feae1c923d0a5cb9cd4 9184 
tortoisehg_4.3.1-1_amd64.buildinfo
Checksums-Sha256:
 f80482ce43131d94f0a007d153decb00501128e434dd6b6ea69d59f64da39189 2147 
tortoisehg_4.3.1-1.dsc
 5698db60320574769c73e4f910909e75a8e32ba84adcea902f9457899bbcb753 7930491 
tortoisehg_4.3.1.orig.tar.gz
 8b06094b39ed5c5272663119b1f968554115761b1673755ab106b9eec1313c5f 17216 
tortoisehg_4.3.1-1.debian.tar.xz
 7beb6a45490df9be0186adcabe2862ec33064ec98ff369646fb714429c0d4896 14982 
tortoisehg-caja_4.3.1-1_all.deb
 22c5e94d796ab71b66f70a46998e0bfa52d5f7a5228e29d3e7e6d1d3642d800e 14888 
tortoisehg-nautilus_4.3.1-1_all.deb
 0c561aded8ea16bb823b28fa9c8f91a258d733311d3663f464f1b90028a86f83 2431874 
tortoisehg_4.3.1-1_all.deb
 88bdfd389aa8f60338af52015c9180a3715c38d72ad57579139a090f58f5b9f0 9184 
tortoisehg_4.3.1-1_amd64.buildinfo
Files:
 81a74c1b8a640e0c0a986e6686e3830c 2147 vcs optional tortoisehg_4.3.1-1.dsc
 eab0617be0e42be5552de2377d0f2b67 7930491 vcs optional 
tortoisehg_4.3.1.orig.tar.gz
 2b1ea429ec2c1c12692766c4ddbfac86 17216 vcs optional 
tortoisehg_4.3.1-1.debian.tar.xz
 3381c68c6bbc544953ffdca72e2ae69c 14982 vcs optional 
tortoisehg-caja_4.3.1-1_all.deb
 9d1ea10dc2a1d4a186e02a73968ee0dc 14888 vcs optional 
tortoisehg-nautilus_4.3.1-1_all.deb
 ac825b9c91f691dba75117ac67c72a3c 2431874 vcs optional 
tortoisehg_4.3.1-1_all.deb
 1d1ad53fa078be388ee889d0af409f19 9184 vcs optional 
tortoisehg_4.3.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEExi9RJLiVCtv386tME8C1Zno4sLAFAlmmoN4ACgkQE8C1Zno4
sLAWdg/+JTTUmpJ7mLmyILclmN5QaraMn0289MYscLvONxLyzRCNJQ1goYKiLiGF

Bug#856862: marked as done (libvibe-core-dev: missing Depends: libvibe-core0 (= ${binary:Version}))

[Debian Bug Tracking System]

Your message dated Wed, 30 Aug 2017 21:00:16 +
with message-id 
and subject line Bug#856862: fixed in vibe.d 0.8.1-1
has caused the Debian Bug report #856862,
regarding libvibe-core-dev: missing Depends: libvibe-core0 (= ${binary:Version})
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.)


-- 
856862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856862
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libvibe-core-dev
Version: 0.7.30-1
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...):

0m11.1s ERROR: FAIL: Broken symlinks:
  /usr/lib/x86_64-linux-gnu/libvibe-core.so -> libvibe-core.so.0

I'd guess that library is in libvibe-core0

Please also check the other -dev packages.


cheers,

Andreas


libvibe-core-dev_0.7.30-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: vibe.d
Source-Version: 0.8.1-1

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

Debian distribution maintenance software
pp.
Matthias Klumpp  (supplier of updated vibe.d package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 30 Aug 2017 17:30:38 +0200
Source: vibe.d
Binary: vibe.d libvibe-core0 libvibe-core-dev libvibe-crypto0 
libvibe-crypto-dev libvibe-data0 libvibe-data-dev libvibe-http0 
libvibe-http-dev libvibe-inet0 libvibe-inet-dev libvibe-mail0 libvibe-mail-dev 
libvibe-mongodb0 libvibe-mongodb-dev libvibe-redis0 libvibe-redis-dev 
libvibe-stream0 libvibe-stream-dev libvibe-textfilter0 libvibe-textfilter-dev 
libvibe-tls0 libvibe-tls-dev libvibe-utils0 libvibe-utils-dev libvibe-web0 
libvibe-web-dev
Architecture: source amd64 all
Version: 0.8.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian D Language Group 
Changed-By: Matthias Klumpp 
Description:
 libvibe-core-dev - High-performance web application toolkit - Core 
(development)
 libvibe-core0 - High-performance web application toolkit - Core
 libvibe-crypto-dev - High-performance web application toolkit - Crypto 
(development)
 libvibe-crypto0 - High-performance web application toolkit - Cryptographic 
routines
 libvibe-data-dev - High-performance web application toolkit - Data 
(development)
 libvibe-data0 - High-performance web application toolkit - Data
 libvibe-http-dev - High-performance web application toolkit - HTTP 
(development)
 libvibe-http0 - High-performance web application toolkit - HTTP
 libvibe-inet-dev - High-performance web application toolkit - INet 
(development)
 libvibe-inet0 - High-performance web application toolkit - INet
 libvibe-mail-dev - High-performance web application toolkit - Mail 
(development)
 libvibe-mail0 - High-performance web application toolkit - Mail
 libvibe-mongodb-dev - High-performance web application toolkit - MongoDB 
(development)
 libvibe-mongodb0 - High-performance web application toolkit - MongoDB
 libvibe-redis-dev - High-performance web application toolkit - Redis 
(development)
 libvibe-redis0 - High-performance web application toolkit - Redis
 libvibe-stream-dev - High-performance web application toolkit - Stream 
(development)
 libvibe-stream0 - High-performance web application toolkit - Stream
 libvibe-textfilter-dev - High-performance web application toolkit - TextFilter 
(developmen
 libvibe-textfilter0 - High-performance web application toolkit - TextFilter
 libvibe-tls-dev - High-performance web application toolkit - TLS (development)
 libvibe-tls0 - High-performance web application toolkit - TLS
 libvibe-utils-dev - High-performance web application toolkit - Utils 
(development)
 libvibe-utils0 - High-performance web application toolkit - Utils
 libvibe-web-dev - High-performance web application toolkit - Web (development)
 libvibe-web0 - High-performance web application toolkit - Web
 vibe.d   

Processed: tagging 873557

[Debian Bug Tracking System]

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

> tags 873557 + fixed-upstream
Bug #873557 {Done: James Cowgill } [src:mbedtls] mbedtls: 
CVE-2017-14032: authentication bypass
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Processed: retitle 873557 to mbedtls: CVE-2017-14032: authentication bypass

[Debian Bug Tracking System]

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

> retitle 873557 mbedtls: CVE-2017-14032: authentication bypass
Bug #873557 {Done: James Cowgill } [src:mbedtls] mbedtls: 
possible authentication bypass
Changed Bug title to 'mbedtls: CVE-2017-14032: authentication bypass' from 
'mbedtls: possible authentication bypass'.
> thanks
Stopping processing here.

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

Processed: reassign 873749 to gnome-user-docs, forcibly merging 873716 873749

[Debian Bug Tracking System]

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

> reassign 873749 gnome-user-docs
Bug #873749 [gnome-user-docs] gnome-user-docs conflicts with gnome-user-guide
Ignoring request to reassign bug #873749 to the same package
> forcemerge 873716 873749
Bug #873716 {Done: Michael Biebl } [gnome-user-docs] trying 
to overwrite '/usr/share/help/C/gnome-help/a11y-bouncekeys.page', which is also 
in package gnome-user-guide 3.22.0-1
Bug #873749 [gnome-user-docs] gnome-user-docs conflicts with gnome-user-guide
Severity set to 'serious' from 'normal'
Marked Bug as done
Marked as found in versions gnome-user-docs/3.25.90-1.
Merged 873716 873749
> thanks
Stopping processing here.

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

Bug#873716: closing 873716

[Michael Biebl]

close 873716 
thanks

Bug#873749: marked as done (gnome-user-docs conflicts with gnome-user-guide)

[Debian Bug Tracking System]

Your message dated Wed, 30 Aug 2017 21:42:12 +0200
with message-id <00da3094-9791-34e0-6a7d-52b9d6ce7...@debian.org>
and subject line Re: trying to overwrite 
'/usr/share/help/C/gnome-help/a11y-bouncekeys.page', which is also in package 
gnome-user-guide 3.22.0-1
has caused the Debian Bug report #873716,
regarding gnome-user-docs conflicts with gnome-user-guide
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.)


-- 
873716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873716
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-user-docs
Version: 3.25.90-1_all

Package: gnome-user-guide
Version: 3.22.0-1

OS: debian unstable

Full error:
E: /tmp/apt-dpkg-install-sckApZ/11-gnome-user-docs_3.25.90-1_all.deb:
trying to overwrite '/usr/share/help/C/gnome-help/a11y-bouncekeys.page',
which is also in package gnome-user-guide 3.22.0-1

Thanks
--- End Message ---
--- Begin Message ---
Version: 3.25.90-2


 gnome-user-docs (3.25.90-2) unstable; urgency=medium
 .
   * Add missing Breaks/Replaces for package rename
-- 
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
--- End Message ---

Bug#873716: marked as done (trying to overwrite '/usr/share/help/C/gnome-help/a11y-bouncekeys.page', which is also in package gnome-user-guide 3.22.0-1)

[Debian Bug Tracking System]

Your message dated Wed, 30 Aug 2017 21:42:12 +0200
with message-id <00da3094-9791-34e0-6a7d-52b9d6ce7...@debian.org>
and subject line Re: trying to overwrite 
'/usr/share/help/C/gnome-help/a11y-bouncekeys.page', which is also in package 
gnome-user-guide 3.22.0-1
has caused the Debian Bug report #873716,
regarding trying to overwrite 
'/usr/share/help/C/gnome-help/a11y-bouncekeys.page', which is also in package 
gnome-user-guide 3.22.0-1
to be marked as done.

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

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


-- 
873716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873716
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-user-docs
Version: 3.25.90-1
Severity: serious

Selecting previously unselected package gnome-user-docs.
Preparing to unpack .../5-gnome-user-docs_3.25.90-1_all.deb ...
Unpacking gnome-user-docs (3.25.90-1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-8HHTlR/5-gnome-user-docs_3.25.90-1_all.deb (--unpack):
 trying to overwrite '/usr/share/help/C/gnome-help/a11y-bouncekeys.page', which 
is also in package gnome-user-guide 3.22.0-1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Preparing to unpack .../6-gnome-user-guide_3.25.90-1_all.deb ...
Unpacking gnome-user-guide (3.25.90-1) over (3.22.0-1) ...
Errors were encountered while processing:
 /tmp/apt-dpkg-install-8HHTlR/5-gnome-user-docs_3.25.90-1_all.deb
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)



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

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

Versions of packages gnome-user-guide depends on:
pn  gnome-user-docs  

gnome-user-guide recommends no packages.

gnome-user-guide suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 3.25.90-2


 gnome-user-docs (3.25.90-2) unstable; urgency=medium
 .
   * Add missing Breaks/Replaces for package rename
-- 
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
--- End Message ---

Processed: closing 873716

[Debian Bug Tracking System]

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

> close 873716
Bug #873716 [gnome-user-docs] trying to overwrite 
'/usr/share/help/C/gnome-help/a11y-bouncekeys.page', which is also in package 
gnome-user-guide 3.22.0-1
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#873557: mbedtls: possible authentication bypass

[Salvatore Bonaccorso]

Control: retitle mbedtls: CVE-2017-14032: authentication bypass

Hi

On Tue, Aug 29, 2017 at 12:09:30AM +0100, James Cowgill wrote:
> Source: mbedtls
> Version: 2.1.2-1
> Severity: grave
> Tags: security
> 
> Hi,
> 
> The following security advisory was published for mbedtls:
> https://tls.mbed.org/tech-updates/security-advisories/mbedtls-security-advisory-2017-02

MITRE has assigned CVE-2017-14032 for this issue.

Regards,
Salvatore

Processed: forcibly merging 873627 873721

[Debian Bug Tracking System]

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

> forcemerge 873627 873721
Bug #873627 {Done: Andreas Henriksson } [udisks2] udisks2 in 
sid apparently left me with a borked system in plasma(?)
Bug #873634 {Done: Andreas Henriksson } [udisks2] missing 
module files libbd_*.so
Bug #873687 {Done: Andreas Henriksson } [udisks2] udisks2: 
udisks crashes, and desktop lists all system mounts
Bug #873721 [udisks2] [udisks2] Doesn't mount external USB drives
Severity set to 'grave' from 'important'
Marked Bug as done
Marked as fixed in versions udisks2/2.7.2-2.
Bug #873634 {Done: Andreas Henriksson } [udisks2] missing 
module files libbd_*.so
Bug #873687 {Done: Andreas Henriksson } [udisks2] udisks2: 
udisks crashes, and desktop lists all system mounts
Merged 873627 873634 873687 873721
> thanks
Stopping processing here.

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

Bug#873718: Fixes for security vulnerabilities on libgig?

[Christian Schoenebeck]

On Wednesday, August 30, 2017 15:09:39 Raphael Hertzog wrote:
> [ Copy to the Debian bugtracker ]
> 
> Hello Christian,

Hi Raphael,

> a few security issues have been reported against libgig:
> http://seclists.org/fulldisclosure/2017/Aug/39
> 
> The reproducer files are attached too:
> http://seclists.org/fulldisclosure/2017/Aug/att-39/poc_zip.bin
> 
> I wanted to check that you were aware of those issues and if
> you had any patch already. 

Thanks for letting me know. And no, I don't have any patch against those 
issues on my side yet. I see you already came up with some, so I will have a 
look at your patches.

> I could not find any bug tracker
> with open issues so I'm writing to you directly. The subversion
> repository has no recent history related to those issues either.

We do have a bug tracker:

https://bugs.linuxsampler.org

However it currently does not accept new user (self)registrations, because we 
had to struggle with massive spam bot attacks on that tracker. So we decided 
to disable self-registrations for a while.

Thanks!

CU
Christian

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

[Uwe Kleine-König]

Hello,

On Wed, Aug 30, 2017 at 05:55:00PM +0100, Ramsay Jones wrote:
> On 30/08/17 17:14, Uwe Kleine-König wrote:
> > ukleinek@plummer:~/sparse$ make check V=1
> 
> It would be easier to see the results if you _didn't_ add V=1. ;-)

noted for the next time.

> [snip]
> > Out of 287 tests, 272 passed, 15 failed (10 of them are known to fail)
> > Makefile:232: recipe for target 'check' failed
> > make: *** [check] Error 1
> > ukleinek@plummer:~/sparse$ 
> 
> The additional five failures are all in the llvm backend (sparsec),
> which you do not need to use sparse as a 'checker'.
> 
> > The problem is that some cpp symbols are not defined in sparse that are
> > expected to exist. So I can "fix" backend/sum.c with the following
> > patch:
> > 
> > diff --git a/validation/backend/sum.c b/validation/backend/sum.c
> > index 0604299..d0be8dd 100644
> > --- a/validation/backend/sum.c
> > +++ b/validation/backend/sum.c
> > @@ -1,3 +1,5 @@
> > +#define __powerpc64__
> > +#define _CALL_ELF 2
> >  #include 
> >  #include 
> >  
> > 
> 
> Yep, sparse/sparsec do not define various macros that gcc/clang define
> by default on a given architecture. This is a known problem (that I have
> been meaning to fix ...). The 'workaround' for the time being is to use
> the cgcc front-end to sparse. (for example 'make CC=cgcc', or perhaps
> 'cgcc -no-compile').
> 
> [You didn't mention your usage - is this for a kernel build?]

This problem became visible during the make check phase when creating packaged
on the listed archs for horst[1]. You can see a build logs at


https://buildd.debian.org/status/fetch.php?pkg=horst=s390x=5.0-1=1503905687=0

https://buildd.debian.org/status/fetch.php?pkg=horst=ppc64el=5.0-1=1503906226=0

The error message looks identical (I checked the ppc64el log) to the
problem with backend/sum.c:

sparse -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=gnu99 -Wall 
-Wextra -g -I. -DDO_DEBUG -I/usr/include/libnl3 *.[ch]
/usr/include/powerpc64le-linux-gnu/gnu/stubs.h:8:12: error: unable to 
open 'gnu/stubs-32.h'
Makefile:113: recipe for target 'check' failed
make[1]: *** [check] Error 1

Best regards
Uwe

[1] https://packages.debian.org/sid/horst


signature.asc
Description: PGP signature

Bug#872992: marked as done (pytest-qt: FTBFS: Tests failures because of logging changes in Qt)

[Debian Bug Tracking System]

Your message dated Wed, 30 Aug 2017 17:23:49 +
with message-id 
and subject line Bug#872992: fixed in pytest-qt 2.1.2-3
has caused the Debian Bug report #872992,
regarding pytest-qt: FTBFS: Tests failures because of logging changes in Qt
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.)


-- 
872992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872992
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pytest-qt
Version: 2.1.2-2
Severity: serious
Tags: patch

Dear maintainer,

pytest-qt fails to build in the current sid:

  tests/test_logging.py .F.FF..F.

  tests/test_logging.py::test_basic_logging[True-False] FAILED
  tests/test_logging.py::test_basic_logging[False-False] FAILED
  tests/test_logging.py::test_qtlog_fixture FAILED
  tests/test_logging.py::test_logging_fails_tests[DEBUG-1] FAILED

These failures are caused by the configure file that is now shipped with Qt
and which disables all debug output. See bug #805399 for details.

The fix is exporting QT_LOGGING_RULES="default.debug=true" when running the
tests. A patch to do this is attached.

--
Dmitry Shachnev
--- pytest-qt-2.1.2/debian/rules
+++ pytest-qt-2.1.2/debian/rules
@@ -26,5 +26,5 @@
 
 override_dh_auto_test:
 ifeq (,$(findstring nocheck,$(DEB_BUILD_PROFILES)))
-	xvfb-run -a dh_auto_test
+	QT_LOGGING_RULES="default.debug=true" xvfb-run -a dh_auto_test
 endif
--- pytest-qt-2.1.2/debian/tests/control
+++ pytest-qt-2.1.2/debian/tests/control
@@ -3,7 +3,7 @@
  ; for py in $(py3versions -r 2>/dev/null)
  ; do cd "$AUTOPKGTEST_TMP"
  ; echo "Testing with $py:"
- ; PYTEST_QT_API=pyqt5 xvfb-run -a $py -m pytest tests
+ ; QT_LOGGING_RULES="default.debug=true" PYTEST_QT_API=pyqt5 xvfb-run -a $py -m pytest tests
  ; done
 Depends: python3-all, python3-pyqt5, python3-pytestqt, xauth, xvfb
 
@@ -12,6 +12,6 @@
  ; for py in $(py3versions -r 2>/dev/null)
  ; do cd "$AUTOPKGTEST_TMP"
  ; echo "Testing with $py:"
- ; PYTEST_QT_API=pyqt4 xvfb-run -a $py -m pytest tests
+ ; QT_LOGGING_RULES="default.debug=true" PYTEST_QT_API=pyqt4 xvfb-run -a $py -m pytest tests
  ; done
 Depends: python3-all, python3-pyqt4, python3-pytestqt, xauth, xvfb
--- End Message ---
--- Begin Message ---
Source: pytest-qt
Source-Version: 2.1.2-3

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

Debian distribution maintenance software
pp.
Ghislain Antony Vaillant  (supplier of updated pytest-qt 
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, 23 Aug 2017 19:26:33 +0100
Source: pytest-qt
Binary: python3-pytestqt python-pytestqt-doc
Architecture: source all
Version: 2.1.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Ghislain Antony Vaillant 
Description:
 python-pytestqt-doc - documentation for pytest-qt
 python3-pytestqt - pytest plugin for Qt application testing (Python 3)
Closes: 872992
Changes:
 pytest-qt (2.1.2-3) unstable; urgency=medium
 .
   * Fix FTBFS due to logging changes in Qt.
 Thanks to Dmitry Shachnev for the patch (Closes: #872992)
   * Use DEB_BUILD_OPTIONS for nocheck and nodoc guards
   * Fixup the Vcs-Browser URI
   * Bump standards version to 4.1.0
Checksums-Sha1:
 21923fea4b682703bc2c05f3128b6964e1177d4d 2429 pytest-qt_2.1.2-3.dsc
 38e28d28f1f9afa0275e7667c975a41b2d7b5098 108381 pytest-qt_2.1.2.orig.tar.gz
 9fa09ef23872de9dc33e8999a8e36724e5769cbd 3880 pytest-qt_2.1.2-3.debian.tar.xz
 ece9e436f49b13badd500c54870c744a3e1755c9 10398 
pytest-qt_2.1.2-3_amd64.buildinfo
 4e0a9deafa1a0f13b0f01f7231560482ba63fd1f 96692 
python-pytestqt-doc_2.1.2-3_all.deb
 9a89d866ccbb68a52ef3ea2c098729189a26726b 28104 python3-pytestqt_2.1.2-3_all.deb
Checksums-Sha256:
 2c2ed6a4487c34489c989ea075d50271a6cfb58c71a5722a44b67af937e4af7e 2429 
pytest-qt_2.1.2-3.dsc
 1f029b2aa1654f6b90fb7b2cbebd185cc1de7b792df6fdbb9af948b854a05ff7 108381 
pytest-qt_2.1.2.orig.tar.gz
 

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

[Ramsay Jones]

On 30/08/17 17:14, Uwe Kleine-König wrote:
> Hello,
> 
> Antoine Beaupre (on Cc:) noticed that sparse doesn't work on some not so
> common architectures like ppc32le, s390x, ppc64 and sparc64[1]. This is
> nicely catched by the testsuite, e.g.:

The only architecture, from the above list, that is not supported
by cgcc seems to be ppc32le.

>   ukleinek@plummer:~/sparse$ git rev-parse HEAD
>   958c11c35d98417eb6b948bffe2dffed14eb3320
>   ukleinek@plummer:~/sparse$ uname -a
>   Linux plummer 4.9.0-3-powerpc64le #1 SMP Debian 4.9.30-2+deb9u3 
> (2017-08-06) ppc64le GNU/Linux
>   ukleinek@plummer:~/sparse$ make check V=1

It would be easier to see the results if you _didn't_ add V=1. ;-)

[snip]
>   Out of 287 tests, 272 passed, 15 failed (10 of them are known to fail)
>   Makefile:232: recipe for target 'check' failed
>   make: *** [check] Error 1
>   ukleinek@plummer:~/sparse$ 

The additional five failures are all in the llvm backend (sparsec),
which you do not need to use sparse as a 'checker'.

> The problem is that some cpp symbols are not defined in sparse that are
> expected to exist. So I can "fix" backend/sum.c with the following
> patch:
> 
> diff --git a/validation/backend/sum.c b/validation/backend/sum.c
> index 0604299..d0be8dd 100644
> --- a/validation/backend/sum.c
> +++ b/validation/backend/sum.c
> @@ -1,3 +1,5 @@
> +#define __powerpc64__
> +#define _CALL_ELF 2
>  #include 
>  #include 
>  
> 

Yep, sparse/sparsec do not define various macros that gcc/clang define
by default on a given architecture. This is a known problem (that I have
been meaning to fix ...). The 'workaround' for the time being is to use
the cgcc front-end to sparse. (for example 'make CC=cgcc', or perhaps
'cgcc -no-compile').

[You didn't mention your usage - is this for a kernel build?]

ATB,
Ramsay Jones

Bug#873747: astroid segfault on startup when config is available.

[Sandro Tosi]

control: reassign -1 astroidmail

astroidmail maintaner, second misfired grave bug...

On Wed, Aug 30, 2017 at 12:27 PM, Abhijit Hoskeri
 wrote:
> Package: astroid
> Version: 0.9.1-1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> Thanks for packaging astroidmail!
>
> astroid crashes on startup with segmentation fault.
>
> This is the traceback from gdb.
>
> This appears to be different issue from 873484, because this crashes
> even with a working notmuch config available.
>
> [Switching to Thread 0x7f38ecd3a700 (LWP 28946)]
> 0x7f3906ee5f17 in g_mime_parser_options_get_address_compliance_mode () 
> from /usr/lib/x86_64-linux-gnu/libgmime-3.0.so.0
> (gdb) where
> #0  0x7f3906ee5f17 in g_mime_parser_options_get_address_compliance_mode 
> () at /usr/lib/x86_64-linux-gnu/libgmime-3.0.so.0
> #1  0x7f3906ef642f in  () at /usr/lib/x86_64-linux-gnu/libgmime-3.0.so.0
> #2  0x7f3906ef7cbb in internet_address_list_parse () at 
> /usr/lib/x86_64-linux-gnu/libgmime-3.0.so.0
> #3  0x7f39109cd18e in  () at /usr/lib/x86_64-linux-gnu/libnotmuch.so.5
> #4  0x7f39109c9ea9 in notmuch_threads_get () at 
> /usr/lib/x86_64-linux-gnu/libnotmuch.so.5
> #5  0x0001003561a4 in Astroid::QueryLoader::loader() ()
> #6  0x000100358ff9 in void std::__invoke_impl (Astroid::QueryLoader::*)(), 
> Astroid::QueryLoader*>(std::__invoke_memfun_deref, void 
> (Astroid::QueryLoader::*&&)(), Astroid::QueryLoader*&&) ()
> #7  0x00010035864c in std::__invoke_result (Astroid::QueryLoader::*)(), Astroid::QueryLoader*>::type std::__invoke (Astroid::QueryLoader::*)(), Astroid::QueryLoader*>(void 
> (Astroid::QueryLoader::*&&)(), Astroid::QueryLoader*&&) ()
> #8  0x00010035b28d in decltype (__invoke((_S_declval<0ul>)(), 
> (_S_declval<1ul>)())) std::thread::_Invoker >::_M_invoke<0ul, 
> 1ul>(std::_Index_tuple<0ul, 1ul>) ()
> #9  0x00010035b243 in std::thread::_Invoker >::operator()() ()
> #10 0x00010035b222 in 
> std::thread::_State_impl > >::_M_run() ()
> #11 0x7f39080d972f in  () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
> #12 0x7f39078de4f7 in start_thread (arg=0x7f38ecd3a700) at 
> pthread_create.c:456
> #13 0x7f390762081f in clone () at 
> ../sysdeps/unix/sysv/linux/x86_64/clone.S:97
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.12.0-trunk-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
> LANGUAGE=en_US.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages astroid depends on:
> ii  libatk1.0-0 2.24.0-1
> ii  libatkmm-1.6-1v52.24.2-2
> ii  libboost-date-time1.62.01.62.0+dfsg-4+b1
> ii  libboost-filesystem1.62.0   1.62.0+dfsg-4+b1
> ii  libboost-log1.62.0  1.62.0+dfsg-4+b1
> ii  libboost-program-options1.62.0  1.62.0+dfsg-4+b1
> ii  libboost-system1.62.0   1.62.0+dfsg-4+b1
> ii  libboost-thread1.62.0   1.62.0+dfsg-4+b1
> ii  libc6   2.25-0experimental3
> ii  libcairo-gobject2   1.14.10-1
> ii  libcairo2   1.14.10-1
> ii  libcairomm-1.0-1v5  1.12.2-1
> ii  libgcc1 1:7.2.0-1
> ii  libgdk-pixbuf2.0-0  2.36.5-3
> ii  libgirepository-1.0-1   1.53.2-4
> ii  libglib2.0-02.53.6-1
> ii  libglibmm-2.4-1v5   2.50.1-1
> ii  libgmime-2.6-0  2.6.23+dfsg1-1
> ii  libgnutls30 3.6.0-1
> ii  libgtk-3-0  3.22.19-1
> ii  libgtkmm-3.0-1v53.22.1-1
> ii  libjavascriptcoregtk-3.0-0  2.4.11-3
> ii  libnotmuch5 0.25-6
> ii  libpango-1.0-0  1.40.11-1
> ii  libpangocairo-1.0-0 1.40.11-1
> ii  libpangomm-1.4-1v5  2.40.1-3
> ii  libpcre2-8-010.22-3
> ii  libpeas-1.0-0   1.21.0-1
> ii  libsass03.4.3-1
> ii  libsigc++-2.0-0v5   2.10.0-1
> ii  libsoup2.4-12.56.1-1
> ii  libstdc++6  7.2.0-1
> ii  libvte-2.91-0   0.46.2-1
> ii  libwebkitgtk-3.0-0  2.4.11-3
> ii  zlib1g  1:1.2.8.dfsg-5
>
> Versions of packages astroid recommends:
> ii  gnupg  2.1.23-2
> ii  notmuch0.25-6
> ii  vim-gtk3   2:8.0.0946-1
> ii  xdg-utils  1.1.1-1
>
> astroid suggests no packages.
>
> -- no debconf information



-- 
Sandro "morph" Tosi
My website: 

Processed: Re: Bug#873747: astroid segfault on startup when config is available.

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 astroidmail
Bug #873747 [astroid] astroid segfault on startup when config is available.
Bug reassigned from package 'astroid' to 'astroidmail'.
No longer marked as found in versions astroidmail/0.9.1-1.
Ignoring request to alter fixed versions of bug #873747 to the same values 
previously set

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

Bug#873748: libblockdev-part2: uninstallable - sgdisk package does not exist

[James Cowgill]

Package: libblockdev-part2
Version: 2.12-1
Severity: serious
Tags: sid buster

Hi,

libblockdev-part2 2.12-1 cannot be installed in unstable because it
depends on the sgdisk package which does not exist. I guess you are
looking for the gdisk package instead.

> # rmadison sgdisk

> $ apt-file search sgdisk
> gdisk: /sbin/sgdisk

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Processed: bug 873508 is forwarded to linux-spa...@vger.kernel.org, tagging 873508

[Debian Bug Tracking System]

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

> forwarded 873508 linux-spa...@vger.kernel.org
Bug #873508 [src:sparse] parsing horst source code fails on s390x and ppc64el
Set Bug forwarded-to-address to 'linux-spa...@vger.kernel.org'.
> tags 873508 + upstream
Bug #873508 [src:sparse] parsing horst source code fails on s390x and ppc64el
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#873747: astroid segfault on startup when config is available.

[Abhijit Hoskeri]

Package: astroid
Version: 0.9.1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Thanks for packaging astroidmail!

astroid crashes on startup with segmentation fault.

This is the traceback from gdb.

This appears to be different issue from 873484, because this crashes
even with a working notmuch config available.

[Switching to Thread 0x7f38ecd3a700 (LWP 28946)]
0x7f3906ee5f17 in g_mime_parser_options_get_address_compliance_mode () from 
/usr/lib/x86_64-linux-gnu/libgmime-3.0.so.0
(gdb) where
#0  0x7f3906ee5f17 in g_mime_parser_options_get_address_compliance_mode () 
at /usr/lib/x86_64-linux-gnu/libgmime-3.0.so.0
#1  0x7f3906ef642f in  () at /usr/lib/x86_64-linux-gnu/libgmime-3.0.so.0
#2  0x7f3906ef7cbb in internet_address_list_parse () at 
/usr/lib/x86_64-linux-gnu/libgmime-3.0.so.0
#3  0x7f39109cd18e in  () at /usr/lib/x86_64-linux-gnu/libnotmuch.so.5
#4  0x7f39109c9ea9 in notmuch_threads_get () at 
/usr/lib/x86_64-linux-gnu/libnotmuch.so.5
#5  0x0001003561a4 in Astroid::QueryLoader::loader() ()
#6  0x000100358ff9 in void std::__invoke_impl(std::__invoke_memfun_deref, 
void (Astroid::QueryLoader::*&&)(), Astroid::QueryLoader*&&) ()
#7  0x00010035864c in std::__invoke_result::type std::__invoke(void 
(Astroid::QueryLoader::*&&)(), Astroid::QueryLoader*&&) ()
#8  0x00010035b28d in decltype (__invoke((_S_declval<0ul>)(), 
(_S_declval<1ul>)())) std::thread::_Invoker::_M_invoke<0ul, 
1ul>(std::_Index_tuple<0ul, 1ul>) ()
#9  0x00010035b243 in std::thread::_Invoker::operator()() ()
#10 0x00010035b222 in 
std::thread::_State_impl >::_M_run() ()
#11 0x7f39080d972f in  () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#12 0x7f39078de4f7 in start_thread (arg=0x7f38ecd3a700) at 
pthread_create.c:456
#13 0x7f390762081f in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

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

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

Versions of packages astroid depends on:
ii  libatk1.0-0 2.24.0-1
ii  libatkmm-1.6-1v52.24.2-2
ii  libboost-date-time1.62.01.62.0+dfsg-4+b1
ii  libboost-filesystem1.62.0   1.62.0+dfsg-4+b1
ii  libboost-log1.62.0  1.62.0+dfsg-4+b1
ii  libboost-program-options1.62.0  1.62.0+dfsg-4+b1
ii  libboost-system1.62.0   1.62.0+dfsg-4+b1
ii  libboost-thread1.62.0   1.62.0+dfsg-4+b1
ii  libc6   2.25-0experimental3
ii  libcairo-gobject2   1.14.10-1
ii  libcairo2   1.14.10-1
ii  libcairomm-1.0-1v5  1.12.2-1
ii  libgcc1 1:7.2.0-1
ii  libgdk-pixbuf2.0-0  2.36.5-3
ii  libgirepository-1.0-1   1.53.2-4
ii  libglib2.0-02.53.6-1
ii  libglibmm-2.4-1v5   2.50.1-1
ii  libgmime-2.6-0  2.6.23+dfsg1-1
ii  libgnutls30 3.6.0-1
ii  libgtk-3-0  3.22.19-1
ii  libgtkmm-3.0-1v53.22.1-1
ii  libjavascriptcoregtk-3.0-0  2.4.11-3
ii  libnotmuch5 0.25-6
ii  libpango-1.0-0  1.40.11-1
ii  libpangocairo-1.0-0 1.40.11-1
ii  libpangomm-1.4-1v5  2.40.1-3
ii  libpcre2-8-010.22-3
ii  libpeas-1.0-0   1.21.0-1
ii  libsass03.4.3-1
ii  libsigc++-2.0-0v5   2.10.0-1
ii  libsoup2.4-12.56.1-1
ii  libstdc++6  7.2.0-1
ii  libvte-2.91-0   0.46.2-1
ii  libwebkitgtk-3.0-0  2.4.11-3
ii  zlib1g  1:1.2.8.dfsg-5

Versions of packages astroid recommends:
ii  gnupg  2.1.23-2
ii  notmuch0.25-6
ii  vim-gtk3   2:8.0.0946-1
ii  xdg-utils  1.1.1-1

astroid suggests no packages.

-- no debconf information

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

[Uwe Kleine-König]

Hello,

Antoine Beaupre (on Cc:) noticed that sparse doesn't work on some not so
common architectures like ppc32le, s390x, ppc64 and sparc64[1]. This is
nicely catched by the testsuite, e.g.:

ukleinek@plummer:~/sparse$ git rev-parse HEAD
958c11c35d98417eb6b948bffe2dffed14eb3320
ukleinek@plummer:~/sparse$ uname -a
Linux plummer 4.9.0-3-powerpc64le #1 SMP Debian 4.9.30-2+deb9u3 
(2017-08-06) ppc64le GNU/Linux
ukleinek@plummer:~/sparse$ make check V=1
cd validation && ./test-suite
 TESTWoverride-init-def (Woverride-init-def.c)
Using command   : ../sparse Woverride-init-def.c
Expecting exit value: 0
 TESTWoverride-init-no (Woverride-init-no.c)
Using command   : ../sparse -Wno-override-init 
Woverride-init-no.c
Expecting exit value: 0
 TESTWoverride-init-yes (Woverride-init-yes.c)
Using command   : ../sparse -Woverride-init 
Woverride-init-yes.c
Expecting exit value: 0
 TESTwarn-unknown-attribute (Wunknown-attribute-def.c)
Using command   : ../sparse Wunknown-attribute-def.c
Expecting exit value: 0
 TESTwarn-unknown-attribute-no (Wunknown-attribute-no.c)
Using command   : ../sparse -Wno-unknown-attribute 
Wunknown-attribute-no.c
Expecting exit value: 0
 TESTwarn-unknown-attribute-yes (Wunknown-attribute-yes.c)
Using command   : ../sparse -Wunknown-attribute 
Wunknown-attribute-yes.c
Expecting exit value: 0
 TEST__func__ (__func__.c)
Using command   : ../sparse -Wall __func__.c
Expecting exit value: 0
 TESTabstract array declarator static 
(abstract-array-declarator-static.c)
Using command   : ../sparse 
abstract-array-declarator-static.c
Expecting exit value: 0
 TESTaddress_space attribute (address_space.c)
Using command   : ../sparse address_space.c
Expecting exit value: 0
 TESTalias distinct symbols (alias-distinct.c)
Using command   : ../test-linearize alias-distinct.c
Expecting exit value: 0
 TESTalias symbol/pointer (alias-mixed.c)
Using command   : ../test-linearize alias-mixed.c
Expecting exit value: 0
 TESTalias same symbols (alias-same.c)
Using command   : ../test-linearize alias-same.c
Expecting exit value: 0
 TESTattribute __alloc_align__ (alloc-align.c)
Using command   : ../sparse alloc-align.c
Expecting exit value: 0
 TESTalternate keywords (alternate-keywords.c)
Using command   : ../sparse alternate-keywords.c
Expecting exit value: 0
 TESTtest anonymous union initializer (anon-union.c)
Using command   : ../sparse anon-union.c
Expecting exit value: 0
 TESTAsm with goto labels. (asm-empty-clobber.c)
Using command   : ../sparse asm-empty-clobber.c
Expecting exit value: 0
 TESTAsm with goto labels. (asm-goto-lables.c)
Using command   : ../sparse asm-goto-lables.c
Expecting exit value: 0
 TESTasm-toplevel.c (asm-toplevel.c)
Using command   : ../test-linearize asm-toplevel.c
Expecting exit value: 0
 TESTinline attributes (attr-inline.c)
Using command   : ../sparse attr-inline.c
Expecting exit value: 0
 TESTattribute no_sanitize_address (attr-no_sanitize_address.c)
Using command   : ../sparse attr-no_sanitize_address.c
Expecting exit value: 0
 TESTattribute noclone (attr-noclone.c)
Using command   : ../sparse attr-noclone.c
Expecting exit value: 0
 TESToptimize attributes (attr-optimize.c)
Using command   : ../sparse attr-optimize.c
Expecting exit value: 0
 TESTattribute warning (attr-warning.c)
Using command   : ../sparse attr-warning.c
Expecting exit value: 0
 TESTattribute assume_aligned (attr_aligned.c)
Using command   : ../sparse attr_aligned.c
Expecting exit value: 0
 TESTattribute after ( in direct-declarator 
(attr_in_parameter.c)
Using command   : ../sparse attr_in_parameter.c
Expecting exit value: 0
 TESTattribute vector_size (attr_vector_size.c)
 

Bug#873745: bioperl: please Build-Depend on rename

[Dominic Hargreaves]

Source: bioperl
Version: 1.7.1-2
Severity: serious

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

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

# prename is the rename utility written in perl usually available as 
/usr/bin/rename in Debian.
prename s/.pl$// debian/bioperl/usr/bin/*pl
/bin/sh: 1: prename: not found

[1] 

Bug#868966: marked as done (bzr: FTBFS: Test failures)

[Debian Bug Tracking System]

Your message dated Wed, 30 Aug 2017 15:19:37 +
with message-id <20170830151937.66fjckyt6dozs...@jelmer.uk>
and subject line Fixed in unstable
has caused the Debian Bug report #868966,
regarding bzr: FTBFS: Test failures
to be marked as done.

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

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


-- 
868966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868966
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bzr
Version: 2.7.0+bzr6622-3
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170719 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>   File 
> "/<>/bzr-2.7.0+bzr6622/build/lib.linux-x86_64-2.7/bzrlib/transport/http/__init__.py",
>  line 86, in get
> code, response_file = self._get(relpath, None)
>   File 
> "/<>/bzr-2.7.0+bzr6622/build/lib.linux-x86_64-2.7/bzrlib/transport/http/_pycurl.py",
>  line 176, in _get
> return self._get_full(relpath)
>   File 
> "/<>/bzr-2.7.0+bzr6622/build/lib.linux-x86_64-2.7/bzrlib/transport/http/_pycurl.py",
>  line 211, in _get_full
> self._curl_perform(curl, header)
>   File 
> "/<>/bzr-2.7.0+bzr6622/build/lib.linux-x86_64-2.7/bzrlib/transport/http/_pycurl.py",
>  line 395, in _curl_perform
> curl.perform()
> pycurl.error: (51, "SSL: certificate subject name (127.0.0.1) does not match 
> target host name '127.0.0.1'")
> 
> --
> Ran 28549 tests in 141.987s
> 
> FAILED (errors=29, known_failure_count=78)
> 2810 tests skipped
> debian/rules:21: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2017/07/19/bzr_2.7.0+bzr6622-3_unstable.log

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

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

This is fixed in newer versions of bzr.


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

Bug#873740: golang-1.9: Incomplete debian/copyright?

[Chris Lamb]

Source: golang-1.9
Version: 1.9-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Michael Hudson-Doyle 

Hi,

I just ACCEPTed golang-1.9 from NEW but noticed it was missing 
attribution in debian/copyright for at least Stephen Moshier,

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


Regards,

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

Bug#869263: libgd2: CVE-2017-7890: Buffer over-read into uninitialized memory

[Salvatore Bonaccorso]

Source: libgd2
Source-Version: 2.2.5-1

On Sat, Jul 22, 2017 at 09:11:15AM +0200, Salvatore Bonaccorso wrote:
> Source: libgd2
> Version: 2.2.4-2
> Severity: important
> Tags: security upstream
> Forwarded: https://github.com/libgd/libgd/issues/399
> 
> Hi,
> 
> the following vulnerability was published for libgd2.
> 
> CVE-2017-7890[0]:
> Buffer over-read into uninitialized memory

This one is fixed with the 2.2.5-1 upload to unstable.

Regards,
Salvatore

Bug#869263: marked as done (libgd2: CVE-2017-7890: Buffer over-read into uninitialized memory)

[Debian Bug Tracking System]

Your message dated Wed, 30 Aug 2017 16:58:33 +0200
with message-id <20170830145833.fwgi4iloorrkia5b@eldamar.local>
and subject line Re: Bug#869263: libgd2: CVE-2017-7890: Buffer over-read into 
uninitialized memory
has caused the Debian Bug report #869263,
regarding libgd2: CVE-2017-7890: Buffer over-read into uninitialized memory
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.)


-- 
869263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869263
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgd2
Version: 2.2.4-2
Severity: important
Tags: security upstream
Forwarded: https://github.com/libgd/libgd/issues/399

Hi,

the following vulnerability was published for libgd2.

CVE-2017-7890[0]:
Buffer over-read into uninitialized memory

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-7890
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7890
[1] https://github.com/libgd/libgd/issues/399

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libgd2
Source-Version: 2.2.5-1

On Sat, Jul 22, 2017 at 09:11:15AM +0200, Salvatore Bonaccorso wrote:
> Source: libgd2
> Version: 2.2.4-2
> Severity: important
> Tags: security upstream
> Forwarded: https://github.com/libgd/libgd/issues/399
> 
> Hi,
> 
> the following vulnerability was published for libgd2.
> 
> CVE-2017-7890[0]:
> Buffer over-read into uninitialized memory

This one is fixed with the 2.2.5-1 upload to unstable.

Regards,
Salvatore--- End Message ---

Processed: found 873718 in 4.0.0-3

[Debian Bug Tracking System]

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

> found 873718 4.0.0-3
Bug #873718 [src:libgig] Multiple security issues (CVE-2017-12950 to 
CVE-2017-12954)
Marked as found in versions libgig/4.0.0-3.
> thanks
Stopping processing here.

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

Bug#873718: Fixes for security vulnerabilities on libgig?

[Salvatore Bonaccorso]

On Wed, Aug 30, 2017 at 04:34:44PM +0200, Salvatore Bonaccorso wrote:
> Hi
> 
> All, but not CVE-2017-12951 are probably fixed already with the
> 4.0.0-4 upload to unstable today.

Might actually just uncover another problem after the fix.

Regards,
Salvatore

Bug#873718: Fixes for security vulnerabilities on libgig?

[Salvatore Bonaccorso]

Hi

All, but not CVE-2017-12951 are probably fixed already with the
4.0.0-4 upload to unstable today.

Regards,
Salvatore

Bug#864162: opendkim: systemd ExecStart ignore configuration options

[deZillium]

Hello,

The correct solution is:


Change /lib/systemd/system/opendkim.serviceline 11 to:

ExecStart=/usr/sbin/opendkim -x /etc/opendkim.conf



This changeneeds to be implemented with a small incremental update to 
the currect stretch version, since it is essentially a breakage bug 
(affects functionality). The only thing that needs to be changed is to 
let opendkim read its own configuration file, there are no other changes 
needed anywhere else in the package.



Thank you

Processed: tagging 873718

[Debian Bug Tracking System]

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

> tags 873718 + upstream
Bug #873718 [src:libgig] Multiple security issues (CVE-2017-12950 to 
CVE-2017-12954)
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#867648: jruby-maven-plugins: FTBFS: RailsService.java:[26,20] variable session might not have been initialized

[Emmanuel Bourg]

The build currently fails with another error:

[INFO] --- exec-maven-plugin:1.6.0:exec (install gems) @ ruby-tools ---
LoadError: no such file to load -- rubygems/installer
  require at org/jruby/RubyKernel.java:961
at 
/build/jruby-maven-plugins-1.1.5+ds1/ruby-tools/src/main/scripts/install_gems.rb:1
[ERROR] Command execution failed.
org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit 
value: 1)
at org.apache.commons.exec.DefaultExecutor.executeInternal 
(DefaultExecutor.java:404)
at org.apache.commons.exec.DefaultExecutor.execute 
(DefaultExecutor.java:166)
at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:804)
at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:751)
at org.codehaus.mojo.exec.ExecMojo.execute (ExecMojo.java:313)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
(DefaultBuildPluginManager.java:134)

Bug#873627: fixed in udisks2 2.7.2-2

[Moi .]

hi
Dear maintainer

Problem also present since the update of udisks2
Debian Sid Cinnamon 3.2.7-4 kernel 4.12
As explained above

- all mounted volumes appear in Nemo and on the desktop.
- can not mount external hard disks, USB key, or other partitions on the
internal hard drive.
- Gnome-disk-utility does not open.
- Gparted does not give me the possibility to mount my external supports
usb.
(See screenshot).
- and once the password entered in Lightdm, Cinnamon is extremely slow to
launch (almost a minute)
http://pix.toile-libre.org/?img=1504100747.png
http://pix.toile-libre.org/?img=1504100768.png

thank you
Cheers

-- 
Melissa.

Bug#873674: marked as done (libdazzle: FTBFS: 'ascii' codec can't decode byte 0xe2)

[Debian Bug Tracking System]

Your message dated Wed, 30 Aug 2017 13:24:50 +
with message-id 
and subject line Bug#873674: fixed in libdazzle 3.25.91-2
has caused the Debian Bug report #873674,
regarding libdazzle: FTBFS: 'ascii' codec can't decode byte 0xe2
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.)


-- 
873674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873674
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libdazzle
Version: 3.25.5-1
Severity: serious
Justification: fails to build from source

Builds of libdazzle under the traditional C locale (as on the
autobuilders, implicitly) have been failing as detailed below.  Please
try arranging for debian/rules to export LC_ALL=C.UTF-8, which should
be available by default (via libc-bin) these days.

Thanks!

Building documentation for libdazzle
Traceback (most recent call last):
  File "/usr/share/meson/meson", line 37, in 
sys.exit(main())
  File "/usr/share/meson/meson", line 34, in main
return mesonmain.run(sys.argv[1:], launcher)
  File "/usr/share/meson/mesonbuild/mesonmain.py", line 297, in run
sys.exit(run_script_command(args[1:]))
  File "/usr/share/meson/mesonbuild/mesonmain.py", line 264, in 
run_script_command
return cmdfunc(cmdargs)
  File "/usr/share/meson/mesonbuild/scripts/gtkdochelper.py", line 218, in run
options.mode)
  File "/usr/share/meson/mesonbuild/scripts/gtkdochelper.py", line 166, in 
build_gtkdoc
gtkdoc_run_check(fixref_cmd, abs_out)
  File "/usr/share/meson/mesonbuild/scripts/gtkdochelper.py", line 51, in 
gtkdoc_run_check
p, out = Popen_safe(cmd, cwd=cwd, stderr=subprocess.STDOUT)[0:2]
  File "/usr/share/meson/mesonbuild/mesonlib.py", line 522, in Popen_safe
o, e = p.communicate(write)
  File "/usr/lib/python3.5/subprocess.py", line 790, in communicate
stdout = self.stdout.read()
  File "/usr/lib/python3.5/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 16994: 
ordinal not in range(128)
Warning: You are using 'ANSI_X3.4-1968' which is not a a Unicode-compatible 
locale.
You might see errors if you use UTF-8 strings as filenames, as strings, or as 
file contents.
Please switch to a UTF-8 locale for your platform.

-- 
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: libdazzle
Source-Version: 3.25.91-2

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

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

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

Debian distribution maintenance software
pp.
Andreas Henriksson  (supplier of updated libdazzle 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, 30 Aug 2017 14:52:06 +0200
Source: libdazzle
Binary: libdazzle-1.0-0 libdazzle-1.0-dev libdazzle-doc libdazzle-tools 
gir1.2-dazzle-1.0
Architecture: source
Version: 3.25.91-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Andreas Henriksson 
Description:
 gir1.2-dazzle-1.0 - GObject introspection data for libdazzle
 libdazzle-1.0-0 - feature-filled library for GTK+ and GObject
 libdazzle-1.0-dev - feature-filled library for GTK+ and GObject - development 
files
 libdazzle-doc - feature-filled library for GTK+ and GObject - documentation
 libdazzle-tools - feature-filled library for GTK+ and GObject - tools
Closes: 873674
Changes:
 libdazzle (3.25.91-2) unstable; urgency=medium
 .
   * Use C.UTF-8 locale when building (Closes: #873674)
   * Bump Standards-Version to 4.1.0
Checksums-Sha1:
 fac5a562bf496ea8f28daed9d07b6fb1ab72790b 2440 libdazzle_3.25.91-2.dsc
 341a3e30832db4f32734bca8fb59f42ad41b8412 7988 libdazzle_3.25.91-2.debian.tar.xz
 311ce5a5c154ff65995fa98e82701b7f73470cc0 15595 
libdazzle_3.25.91-2_amd64.buildinfo
Checksums-Sha256:
 

Bug#871340: avro-java: FTBFS: [ERROR] Failed to execute goal com.thoughtworks.paranamer:paranamer-maven-plugin:2.8:generate (paranamer-test) on project avro: Fa

[Emmanuel Bourg]

This issue was caused by the update of libqdox2-java. Reverting to the
version 2.0~M3-3 in stretch fixes this issue.

Bug#873718: Fixes for security vulnerabilities on libgig?

[Raphael Hertzog]

[ Copy to the Debian bugtracker ]

Hello Christian,

a few security issues have been reported against libgig:
http://seclists.org/fulldisclosure/2017/Aug/39

The reproducer files are attached too:
http://seclists.org/fulldisclosure/2017/Aug/att-39/poc_zip.bin

I wanted to check that you were aware of those issues and if
you had any patch already. I could not find any bug tracker
with open issues so I'm writing to you directly. The subversion
repository has no recent history related to those issues either.

Thank you!
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Bug#873598: spice-gtk: diff for NMU version 0.34-1.1

[Laurent Bigonville]

Control: tags 873598 + pending

Dear maintainer,

I've prepared an NMU for spice-gtk (versioned as 0.34-1.1) and
uploaded it to DELAYED/3. Please feel free to tell me if I
should delay it longer.

Regards.
diff -Nru spice-gtk-0.34/debian/changelog spice-gtk-0.34/debian/changelog
--- spice-gtk-0.34/debian/changelog 2017-08-06 11:02:13.0 +0200
+++ spice-gtk-0.34/debian/changelog 2017-08-30 14:45:42.0 +0200
@@ -1,3 +1,13 @@
+spice-gtk (0.34-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Call the gir sequence so the gir1.2-* packages have the
+correct dependencies defined. (Closes: #873598)
+  * Make the gir1.2-* packages Multi-Arch: same
+  * Add Breaks to force the uninstallation of the old gir1.2-* packages
+
+ -- Laurent Bigonville   Wed, 30 Aug 2017 14:45:42 +0200
+
 spice-gtk (0.34-1) unstable; urgency=medium
 
   * New upstream release
@@ -7,7 +17,7 @@
 - Rename gir1.2* to fix lintian warning
 - Install gir*.typelib to multiarch directory
 - Remove build-depends on gstreamer1.0-plugins-*(Closes: #863978)
-- Chnage Depends on gstreamer1.0-plugins-* to Suggests(Closes: #849047)
+- Change Depends on gstreamer1.0-plugins-* to Suggests(Closes: #849047)
   * debian/patches:
 - debian/patches/ssl-Rework-our-custom-BIO-type.patch, removed, applied 
   upstream
diff -Nru spice-gtk-0.34/debian/control spice-gtk-0.34/debian/control
--- spice-gtk-0.34/debian/control   2017-08-06 11:02:13.0 +0200
+++ spice-gtk-0.34/debian/control   2017-08-30 14:45:10.0 +0200
@@ -88,8 +88,10 @@
 Package: gir1.2-spiceclientglib-2.0
 Section: introspection
 Architecture: any
+Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
 Depends: ${misc:Depends}, ${gir:Depends}
+Breaks: gir1.2-spice-client-glib-2.0 (<< 0.34)
 Description: GObject for communicating with Spice servers 
(GObject-Introspection)
  libspice-glib4 provides glib objects for spice protocol
  decoding and surface rendering
@@ -126,7 +128,9 @@
 Package: gir1.2-spiceclientgtk-3.0
 Section: introspection
 Architecture: any
+Multi-Arch: same
 Depends: ${misc:Depends}, ${gir:Depends}
+Breaks: gir1.2-spice-client-gtk-3.0 (<< 0.34)
 Description: GTK3 widget for SPICE clients (GObject-Introspection)
  libspice-gtk3 provides gtk3 widget to show spice display 
  and accept user input.
diff -Nru spice-gtk-0.34/debian/rules spice-gtk-0.34/debian/rules
--- spice-gtk-0.34/debian/rules 2017-08-06 11:02:13.0 +0200
+++ spice-gtk-0.34/debian/rules 2017-08-30 14:42:19.0 +0200
@@ -1,7 +1,7 @@
 #!/usr/bin/make -f
 
 %:
-   dh $@ --parallel --with autoreconf
+   dh $@ --parallel --with autoreconf,gir
 
 override_dh_auto_configure:
dh_auto_configure -- \

Processed: spice-gtk: diff for NMU version 0.34-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 873598 + pending
Bug #873598 [src:spice-gtk] spice-gtk: gir package missing dependencies
Added tag(s) pending.

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

Bug#862380: marked as done (khmer: FTBFS with Python 3.6)

[Debian Bug Tracking System]

Your message dated Wed, 30 Aug 2017 12:52:26 +
with message-id 
and subject line Bug#862380: fixed in khmer 2.1.1+dfsg-1
has caused the Debian Bug report #862380,
regarding khmer: FTBFS with Python 3.6
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.)


-- 
862380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862380
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: khmer
Version: 2.0+dfsg-10
Severity: normal
Tags: patch

Dear Maintainer,

I've applied this patch to get the build working now that Python 3.6 is a
supported version in Ubuntu. I admit I don't entirely understand why it is
necessary! Maybe you do? :)

Cheers,
mwh

-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (400, 'xenial-proposed'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-75-generic (SMP w/4 CPU cores)
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru khmer-2.0+dfsg/debian/changelog khmer-2.0+dfsg/debian/changelog
--- khmer-2.0+dfsg/debian/changelog	2017-04-07 08:02:24.0 +1200
+++ khmer-2.0+dfsg/debian/changelog	2017-05-12 13:34:33.0 +1200
@@ -1,3 +1,9 @@
+khmer (2.0+dfsg-10ubuntu1) artful; urgency=medium
+
+  * Fix build with Python 3.6.
+
+ -- Michael Hudson-Doyle   Fri, 12 May 2017 13:15:00 +1200
+
 khmer (2.0+dfsg-10) unstable; urgency=medium
 
   * Team upload.
diff -Nru khmer-2.0+dfsg/debian/control khmer-2.0+dfsg/debian/control
--- khmer-2.0+dfsg/debian/control	2017-04-07 08:01:23.0 +1200
+++ khmer-2.0+dfsg/debian/control	2017-05-12 13:15:39.0 +1200
@@ -1,5 +1,6 @@
 Source: khmer
-Maintainer: Debian Med Packaging Team 
+Maintainer: Ubuntu Developers 
+XSBC-Original-Maintainer: Debian Med Packaging Team 
 Uploaders: Michael R. Crusoe ,
Kevin Murray 
 Section: science
diff -Nru khmer-2.0+dfsg/debian/rules khmer-2.0+dfsg/debian/rules
--- khmer-2.0+dfsg/debian/rules	2017-04-07 07:57:50.0 +1200
+++ khmer-2.0+dfsg/debian/rules	2017-05-12 13:31:58.0 +1200
@@ -26,7 +26,7 @@
 	dh_auto_install
 	PYBUILD_SYSTEM=custom \
 	PYBUILD_TEST_ARGS="cd {dir}; export PATH={destdir}/usr/lib/khmer/bin:$$PATH ; \
-	cd {build_dir}; {interpreter} -m nose --attr \
+	cd {build_dir}; export PYTHONPATH=$$(pwd); {interpreter} -m nose --attr \
 	'!known_failing,!jenkins,!huge'" dh_auto_test
 
 
--- End Message ---
--- Begin Message ---
Source: khmer
Source-Version: 2.1.1+dfsg-1

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

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated khmer package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 29 Aug 2017 23:30:09 -0700
Source: khmer
Binary: khmer-common khmer liboxli1 liboxli-dev
Architecture: source
Version: 2.1.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Michael R. Crusoe 
Description:
 khmer  - in-memory DNA sequence kmer counting, filtering & graph traversal
 khmer-common - common files for the khmer project tools
 liboxli-dev - in-memory DNA sequence analysis dev library
 liboxli1   - in-memory DNA sequence analysis library from the khmer project
Closes: 862380
Changes:
 khmer (2.1.1+dfsg-1) unstable; urgency=medium
 .
   [ Andreas Tille ]
   * Remove empty field
 .
   [ Michael R. Crusoe ]
   * New upstream version 2.1.1
   * Incorporate patch from Ubuntu, thank you Michael Hudson-Doyle.
 Closes: #862380
Checksums-Sha1:
 

Bug#873718: Multiple security issues (CVE-2017-12950 to CVE-2017-12954)

[Raphael Hertzog]

Source: libgig
X-Debbugs-CC: t...@security.debian.org 
secure-testing-t...@lists.alioth.debian.org
Severity: grave
Tags: security

Hi,

the following vulnerabilities were published for libgig. See
http://seclists.org/fulldisclosure/2017/Aug/39 for the initial report
with reproducer files.

CVE-2017-12950[0]:
| The gig::Region::Region function in gig.cpp in libgig 4.0.0 allows
| remote attackers to cause a denial of service (NULL pointer
| dereference and application crash) via a crafted gig file.

CVE-2017-12951[1]:
| The gig::DimensionRegion::CreateVelocityTable function in gig.cpp in
| libgig 4.0.0 allows remote attackers to cause a denial of service
| (stack-based buffer over-read and application crash) via a crafted gig
| file.

CVE-2017-12952[2]:
| The LoadString function in helper.h in libgig 4.0.0 allows remote
| attackers to cause a denial of service (NULL pointer dereference and
| application crash) via a crafted gig file.

CVE-2017-12953[3]:
| The gig::Instrument::UpdateRegionKeyTable function in gig.cpp in
| libgig 4.0.0 allows remote attackers to cause a denial of service
| (invalid memory write and application crash) via a crafted gig file.

CVE-2017-12954[4]:
| The gig::Region::GetSampleFromWavePool function in gig.cpp in libgig
| 4.0.0 allows remote attackers to cause a denial of service (invalid
| memory read and application crash) via a crafted gig file.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-12950
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12950
[1] https://security-tracker.debian.org/tracker/CVE-2017-12951
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12951
[2] https://security-tracker.debian.org/tracker/CVE-2017-12952
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12952
[3] https://security-tracker.debian.org/tracker/CVE-2017-12953
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12953
[4] https://security-tracker.debian.org/tracker/CVE-2017-12954
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12954

Please adjust the affected versions in the BTS as needed.


-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Bug#873716: trying to overwrite '/usr/share/help/C/gnome-help/a11y-bouncekeys.page', which is also in package gnome-user-guide 3.22.0-1

[Martin Zobel-Helas]

Package: gnome-user-docs
Version: 3.25.90-1
Severity: serious

Selecting previously unselected package gnome-user-docs.
Preparing to unpack .../5-gnome-user-docs_3.25.90-1_all.deb ...
Unpacking gnome-user-docs (3.25.90-1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-8HHTlR/5-gnome-user-docs_3.25.90-1_all.deb (--unpack):
 trying to overwrite '/usr/share/help/C/gnome-help/a11y-bouncekeys.page', which 
is also in package gnome-user-guide 3.22.0-1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Preparing to unpack .../6-gnome-user-guide_3.25.90-1_all.deb ...
Unpacking gnome-user-guide (3.25.90-1) over (3.22.0-1) ...
Errors were encountered while processing:
 /tmp/apt-dpkg-install-8HHTlR/5-gnome-user-docs_3.25.90-1_all.deb
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)



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

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

Versions of packages gnome-user-guide depends on:
pn  gnome-user-docs  

gnome-user-guide recommends no packages.

gnome-user-guide suggests no packages.

-- no debconf information

Bug#873623: sudo: occasionally stalls infinitely instead of running command

[Thorsten Glaser]

Bob Proulx dixit:

>independent of sssd.  There is no sssd installed on my system which
>also exhibits the sudo hang problem.

Same for me, no sssd. My nsswitch.conf has no sudoers entry, just:

-cutting here may damage your screen surface-
# $Id: nsswitch.conf 432 2009-06-30 11:31:23Z tglase $

passwd: compat #ldap
group:  compat #ldap
shadow: compat #ldap

hosts:  files dns
networks:   files

protocols:  db files
services:   db files
ethers: db files
rpc:db files

netgroup:   nis
-cutting here may damage your screen surface-

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

Processed: forcibly merging 873627 873687

[Debian Bug Tracking System]

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

> forcemerge 873627 873687
Bug #873627 {Done: Andreas Henriksson } [udisks2] udisks2 in 
sid apparently left me with a borked system in plasma(?)
Bug #873634 {Done: Andreas Henriksson } [udisks2] missing 
module files libbd_*.so
Bug #873687 [udisks2] udisks2: udisks crashes, and desktop lists all system 
mounts
Severity set to 'grave' from 'important'
Marked Bug as done
Marked as fixed in versions udisks2/2.7.2-2.
Bug #873634 {Done: Andreas Henriksson } [udisks2] missing 
module files libbd_*.so
Merged 873627 873634 873687
> thanks
Stopping processing here.

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

Processed: Re: Bug#870700: [gnome-flashback] gnome-session-flashback segfaults after login

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #870700 [gnome-flashback] [gnome-flashback] gnome-session-flashback 
segfaults after login
Severity set to 'important' from 'critical'

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

Bug#870700: [gnome-flashback] gnome-session-flashback segfaults after login

[Dmitry Shachnev]

Control: severity -1 important

On Tue, Aug 08, 2017 at 01:31:16PM +0300, Dmitry Shachnev wrote:
> Yesterday I have uploaded GNOME Flashback 3.24.0 to unstable, with some
> additional fixes backported from upstream. Can you please test that version
> and check if your crash still happens with it?

As I have not gotten response on this yet, downgrading the severity to
important to prevent auto-removal from testing.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Processed: Version tracking fix

[Debian Bug Tracking System]

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

> fixed 873303 0.20170609-1
Bug #873303 {Done: Riku Voipio } [src:kvmtool] kvmtool 
FTBFS with linux-libc-dev >= 4.12
Marked as fixed in versions kvmtool/0.20170609-1.
> thanks
Stopping processing here.

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

Bug#873713: node-foreground-child FTBFS: test failures

[Graham Inggs]

Source: node-foreground-child
Version: 1.5.6-1
Severity: serious

Hi Maintainer

Node-foreground-child FTBFS in unstable:

https://tests.reproducible-builds.org/debian/history/node-foreground-child.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-foreground-child.html

...
test/immortal-child.js

  1) should match pattern provided

  38 passing (11s)
  1 failing

  1) test/immortal-child.js should match pattern provided:
 Error: should match pattern provided
  at ChildProcess. (test/immortal-child.js:37:7)

debian/rules:12: recipe for target 'override_dh_auto_test' failed

Regards
Graham

Bug#867730: marked as done (dummydroid: unusable due to authentication failure)

[Debian Bug Tracking System]

Your message dated Wed, 30 Aug 2017 10:34:26 +
with message-id 
and subject line Bug#867730: fixed in dummydroid 1.2-1
has caused the Debian Bug report #867730,
regarding dummydroid: unusable due to authentication failure
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.)


-- 
867730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867730
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dummydroid
Version: 1.1-1
Severity: grave
Justification: renders package unusable

I am attempting to use gplaycli on stretch, for which I need a google play
device id.

After the Credentials step, no matter how I setup the google account, I always
get an error displayed on the Profile Upload step:

com.akdeniz.googleplaycrawler.GooglePlayException: Error=BadAuthentication

Google Auth methods tried:
* custom domain, two-factor
* custom domain, password only
* registered dummydro...@gmail.com

Steps to reproduce:
1) register account at https://accounts.google.com/SignUp
2) sign in at https://play.google.com/store
3) launch dummydroid
4) open Google_Nexus_6.prop (or Azpen_A727.prop)
5) click next through to Credentials
6) enter details registered and click next

I can't find a manpage or guess any flags to enter debug mode, so there is no
extra detail on stdout - please let me know if there's a way to test this, or
if you're unable to reproduce the error.

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

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

Versions of packages dummydroid depends on:
ii  default-jre [java8-runtime]2:1.8-58
ii  jarwrapper 0.59
ii  libhttpclient-java 4.5.2-2
ii  libhttpcore-java   4.4.6-1
ii  openjdk-8-jre [java8-runtime]  8u131-b11-2

dummydroid recommends no packages.

dummydroid suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: dummydroid
Source-Version: 1.2-1

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

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

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

Debian distribution maintenance software
pp.
Hans-Christoph Steiner  (supplier of updated dummydroid package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 30 Aug 2017 11:35:51 +0200
Source: dummydroid
Binary: dummydroid
Architecture: source all
Version: 1.2-1
Distribution: unstable
Urgency: medium
Maintainer: Android tools Maintainer 

Changed-By: Hans-Christoph Steiner 
Description:
 dummydroid - Register a GSF ID for mock-up Android devices
Closes: 867730
Changes:
 dummydroid (1.2-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #867730)
Checksums-Sha1:
 2065b734e3ab9802ecaeee2094019c2c99d4af99 1758 dummydroid_1.2-1.dsc
 6773167f09c7a335c541614b775db999cc52b6d0 556147 dummydroid_1.2.orig.tar.gz
 07225525e35a66b92c138aeff3b20ba2a3b77297 9748 dummydroid_1.2-1.debian.tar.xz
 556564a4d9869110cd979ffd08a0569295047710 3819602 dummydroid_1.2-1_all.deb
 7f2a5afc8367cadeed386bbe571578a94f548336 15092 dummydroid_1.2-1_amd64.buildinfo
Checksums-Sha256:
 8b6273a79f4982dc3fdcdad1d43b09e3620a3bf99aedfbabd430025d2f16155b 1758 
dummydroid_1.2-1.dsc
 b8427afd195a591135c871ab3d9b7e7fbd2cc3edab0a8e1c220c4dea12511874 556147 
dummydroid_1.2.orig.tar.gz
 b059ed0b7a227435b8f800833ee03a78263fbb5f66045da6ff124abd15ceddb8 9748 
dummydroid_1.2-1.debian.tar.xz
 63d0be7690972808b882ef0d9f454ad53742fefc974ad16df9825563c17e5a23 3819602 
dummydroid_1.2-1_all.deb
 8b2494ac3c38fd9035b19766bb346a66026541698af2e1a7498ddf176d203fd0 15092 
dummydroid_1.2-1_amd64.buildinfo
Files:
 4b71933b54f8de9036e733dbf17e7dde 1758 devel optional dummydroid_1.2-1.dsc
 2a1c969caa77499e25f4f993d57373a4 556147 devel optional 

Bug#873303: marked as done (kvmtool FTBFS with linux-libc-dev >= 4.12)

[Debian Bug Tracking System]

Your message dated Wed, 30 Aug 2017 13:37:46 +0300
with message-id 

Bug#872844: Wheezy update of connman?

[Raphael Hertzog]

Hello Alf,

The Debian LTS team would like to fix the security issues which are
currently open in the Wheezy version of connman:
https://security-tracker.debian.org/tracker/CVE-2017-12865

Would you like to take care of this yourself?

If yes, please follow the workflow we have defined here:
https://wiki.debian.org/LTS/Development

If that workflow is a burden to you, feel free to just prepare an
updated source package and send it to debian-...@lists.debian.org
(via a debdiff, or with an URL pointing to the source package,
or even with a pointer to your packaging repository), and the members
of the LTS team will take care of the rest. Indicate clearly whether you
have tested the updated package or not.

If you don't want to take care of this update, it's not a problem, we
will do our best with your package. Just let us know whether you would
like to review and/or test the updated package before it gets released.

You can also opt-out from receiving future similar emails in your
answer and then the LTS Team will take care of connman updates
for the LTS releases.

Thank you very much.

Raphaël Hertzog,
  on behalf of the Debian LTS team.

PS: A member of the LTS team might start working on this update at
any point in time. You can verify whether someone is registered
on this update in this file:
https://anonscm.debian.org/viewvc/secure-testing/data/dla-needed.txt?view=markup
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Processed: Not a problem in stretch

[Debian Bug Tracking System]

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

> tags 825220 buster sid
Bug #825220 [src:fwanalog] fwanalog: please Build-Depend on rename
Added tag(s) sid and buster.
> tags 826056 buster sid
Bug #826056 [src:smokeping] smokeping: please Build-Depend on rename
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#853611: marked as done (pick: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Wed, 30 Aug 2017 10:08:15 +
with message-id 
and subject line Bug#853611: fixed in pick 1.8.0-1
has caused the Debian Bug report #853611,
regarding pick: ftbfs with GCC-7
to be marked as done.

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

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


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

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]
checking for stdlib.h... (cached) yes
checking for GNU libc compatible malloc... yes
checking for stdlib.h... (cached) yes
checking for GNU libc compatible realloc... yes
checking for memmove... yes
checking for setlocale... yes
checking for strdup... yes
checking for strlcpy... no
checking for strlcat... no
checking for library containing initscr... -lncursesw
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating man/Makefile
config.status: creating config.h
config.status: executing depfiles commands
configure: WARNING: unrecognized options: --disable-maintainer-mode
   dh_auto_build
make -j1
make[1]: Entering directory '/<>'
make  all-recursive
make[2]: Entering directory '/<>'
Making all in src
make[3]: Entering directory '/<>/src'
gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra 
-pedantic-errors -Wno-unused-parameter -Werror -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o choice.o choice.c
gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra 
-pedantic-errors -Wno-unused-parameter -Werror -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o choices.o choices.c
gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra 
-pedantic-errors -Wno-unused-parameter -Werror -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o io.o io.c
gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra 
-pedantic-errors -Wno-unused-parameter -Werror -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o main.o main.c
main.c: In function 'main':
main.c:34:4: error: this statement may fall through 
[-Werror=implicit-fallthrough=]
version();
^
main.c:35:3: note: here
   case 'd':
   ^~~~
cc1: all warnings being treated as errors
Makefile:369: recipe for target 'main.o' failed
make[3]: *** [main.o] Error 1
make[3]: Leaving directory '/<>/src'
Makefile:359: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/<>'
Makefile:300: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
debian/rules:5: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---
Source: pick
Source-Version: 1.8.0-1

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

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

Bug#873627: fixed in udisks2 2.7.2-2

[Andreas Henriksson]

Hello Julian Wollrath,

On Wed, Aug 30, 2017 at 11:52:52AM +0200, Julian Wollrath wrote:
> udisksd[15752]: Cannot load the part plugin: The 'sgdisk' utility is not 
> available
[...]
> It seems to me, that 'gdisk' is a non obligatory dependency too and
> indeed installing 'gdisk' makes udisks2 start again.
[...]

Thanks for your feedback.

This is an issue in libblockdev-part2 package which needs that dependency.
(Long-term even better would likely be to port away from gdisk usage
and spawning cli commands at all.)

I'll fix that up, but feel free to file a (severity serious) bug report
on libblockdev-part2

Regards,
Andreas Henriksson

Bug#873627: fixed in udisks2 2.7.2-2

[Julian Wollrath]

Hi,

this does not fix it for me, I still get a complain:
udisksd[15752]: udisks daemon version 2.7.2 starting
udisksd[15752]: Cannot load the part plugin: The 'sgdisk' utility is
not available
udisksd[15752]: Error initializing libblockdev library: Failed to load
plugins (g-bd-init-error-quark, 0)
systemd[1]: udisks2.service: Main process exited, code=killed,
status=5/TRAP
systemd[1]: Failed to start Disk Manager.
systemd[1]: udisks2.service: Unit entered failed state.
systemd[1]: udisks2.service: Failed with result 'signal'.

It seems to me, that 'gdisk' is a non obligatory dependency too and
indeed installing 'gdisk' makes udisks2 start again.

Cheers,
Julian

On Wed, 30 Aug 2017 09:06:08 + Andreas Henriksson
 wrote:
> Source: udisks2
> Source-Version: 2.7.2-2
> 
> We believe that the bug you reported is fixed in the latest version of
> udisks2, which is due to be installed in the Debian FTP archive.
> 
> A summary of the changes between this version and the previous one is
> attached.
> 
> Thank you for reporting the bug, which will now be closed.  If you
> have further comments please address them to 873...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
> 
> Debian distribution maintenance software
> pp.
> Andreas Henriksson  (supplier of updated udisks2
> package)
> 
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmas...@ftp-master.debian.org)
> 
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Format: 1.8
> Date: Wed, 30 Aug 2017 09:36:18 +0200
> Source: udisks2
> Binary: udisks2 udisks2-doc libudisks2-0 libudisks2-dev
> gir1.2-udisks-2.0 Architecture: source
> Version: 2.7.2-2
> Distribution: unstable
> Urgency: medium
> Maintainer: Utopia Maintenance Team
>  Changed-By: Andreas
> Henriksson  Description:
>  gir1.2-udisks-2.0 - GObject based library to access udisks2 -
> introspection data libudisks2-0 - GObject based library to access
> udisks2 libudisks2-dev - GObject based library to access udisks2 -
> development files udisks2- D-Bus service to access and manipulate
> storage devices udisks2-doc - udisks2 documentation
> Closes: 873627
> Changes:
>  udisks2 (2.7.2-2) unstable; urgency=medium
>  .
>* Depend on blockdev plugins required by udisks2 core (Closes:
> #873627)
>* Add libblockdev plugins used by udisks modules to suggests
> Checksums-Sha1:
>  cda6ef6deecebaf3258d529517294050c8ab3c24 3026 udisks2_2.7.2-2.dsc
>  2b963c7e1dc87977613e229b630a2f75bbf5880e 13308
> udisks2_2.7.2-2.debian.tar.xz
> 5b33cc95f61e943b600f3e834bd4b7b547ed1db5 12795
> udisks2_2.7.2-2_amd64.buildinfo Checksums-Sha256:
> 73029bc345f07b082c96319573fb6e66dce478892862ddee48410faecb05d1f2 3026
> udisks2_2.7.2-2.dsc
> e96ad56de9baf8021cf5a1cc5d8de8e2b1f2187ee4154962da0e6aba414d0f49
> 13308 udisks2_2.7.2-2.debian.tar.xz
> 5584a9bd8816620c4a733b8162d987b5eda6a29df01814548556373209c1c8f7
> 12795 udisks2_2.7.2-2_amd64.buildinfo Files:
> 4056e291230932c7c06bd0908055a4e4 3026 admin optional
> udisks2_2.7.2-2.dsc 1d476835a887a24001edb37c490f75db 13308 admin
> optional udisks2_2.7.2-2.debian.tar.xz
> 0506a5da3e4cd9901b15f0c4b58c721a 12795 admin optional
> udisks2_2.7.2-2_amd64.buildinfo
> 



-- 
 ()  ascii ribbon campaign - against html e-mail 
 /\- against proprietary attachments

Processed: Also reopen them

[Debian Bug Tracking System]

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

> reopen 854272
Bug #854272 {Done: Chris Lamb } [src:zoneminder] 
CVE-2016-10201 CVE-2016-10202 CVE-2016-10203 CVE-2016-10204 CVE-2016-10205 
CVE-2016-10206
Bug reopened
Ignoring request to alter fixed versions of bug #854272 to the same values 
previously set
> reopen 854733
Bug #854733 {Done: Chris Lamb } [src:zoneminder] zoneminder: 
CVE-2017-5367 CVE-2017-5368 CVE-2017-5595
Bug reopened
Ignoring request to alter fixed versions of bug #854733 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: Upgrading to RC

[Debian Bug Tracking System]

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

> # rename is gone in 5.26.0-6 in experimental, soon to hit unstable
> severity 825220 serious
Bug #825220 [src:fwanalog] fwanalog: please Build-Depend on rename
Severity set to 'serious' from 'normal'
> severity 826056 serious
Bug #826056 [src:smokeping] smokeping: please Build-Depend on rename
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Processed: update 873697

[Debian Bug Tracking System]

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

> owner  873697 sm...@cpan.org
Bug #873697 [src:libtext-bibtex-perl] libtext-bibtex-perl FTBFS on 
arm*/ppc64el: t/unlimited.t (Wstat: 11 Tests: 4 Failed: 0)
Owner recorded as sm...@cpan.org.
> thanks
Stopping processing here.

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

Bug#873627: marked as done (udisks2 in sid apparently left me with a borked system in plasma(?))

[Debian Bug Tracking System]

Your message dated Wed, 30 Aug 2017 09:06:08 +
with message-id 
and subject line Bug#873627: fixed in udisks2 2.7.2-2
has caused the Debian Bug report #873627,
regarding udisks2 in sid apparently left me with a borked system in plasma(?)
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.)


-- 
873627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873627
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: udisks2
Version: 2.6.5-2
Severity: important

Dear Maintainer,

Upon an upgrade in sid, my computer gave a message, something like "disk 
manager failed" or something like that, and also "see systemctl status 
udisks2.service". When trying to boot into KDE Plasma I had no taskbar and 
could not open programs with alt+f2 that I was aware of. I appear to have fixed 
the problem by downgrading udisks2 to testing, in that I now have a functioning 
GUI again. 


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

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

Versions of packages udisks2 depends on:
ii  dbus   1.11.16+really1.10.22-1
ii  init-system-helpers1.49
ii  libacl12.2.52-3+b1
ii  libatasmart4   0.19-4+b1
ii  libc6  2.24-17
ii  libglib2.0-0   2.53.6-1
ii  libgudev-1.0-0 230-3
ii  libpam-systemd 234-2.3
ii  libpolkit-agent-1-00.105-18
ii  libpolkit-gobject-1-0  0.105-18
ii  libsystemd0234-2.3
ii  libudisks2-0   2.7.2-1
ii  parted 3.2-17
ii  udev   234-2.3

Versions of packages udisks2 recommends:
ii  dosfstools   4.1-1
ii  eject2.1.5+deb1+cvs20081104-13.2
ii  exfat-utils  1.2.7-1
ii  gdisk1.0.1-1
ii  ntfs-3g  1:2016.2.22AR.2-2
ii  policykit-1  0.105-18

Versions of packages udisks2 suggests:
pn  btrfs-progs | btrfs-tools  
pn  cryptsetup-bin 
pn  mdadm  
pn  reiserfsprogs  
pn  xfsprogs   

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: udisks2
Source-Version: 2.7.2-2

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

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

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

Debian distribution maintenance software
pp.
Andreas Henriksson  (supplier of updated udisks2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 30 Aug 2017 09:36:18 +0200
Source: udisks2
Binary: udisks2 udisks2-doc libudisks2-0 libudisks2-dev gir1.2-udisks-2.0
Architecture: source
Version: 2.7.2-2
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Andreas Henriksson 
Description:
 gir1.2-udisks-2.0 - GObject based library to access udisks2 - introspection 
data
 libudisks2-0 - GObject based library to access udisks2
 libudisks2-dev - GObject based library to access udisks2 - development files
 udisks2- D-Bus service to access and manipulate storage devices
 udisks2-doc - udisks2 documentation
Closes: 873627
Changes:
 udisks2 (2.7.2-2) unstable; urgency=medium
 .
   * Depend on blockdev plugins required by udisks2 core (Closes: #873627)
   * Add libblockdev plugins used by udisks modules to suggests
Checksums-Sha1:
 cda6ef6deecebaf3258d529517294050c8ab3c24 3026 udisks2_2.7.2-2.dsc
 2b963c7e1dc87977613e229b630a2f75bbf5880e 13308 udisks2_2.7.2-2.debian.tar.xz
 5b33cc95f61e943b600f3e834bd4b7b547ed1db5 12795 udisks2_2.7.2-2_amd64.buildinfo
Checksums-Sha256:
 73029bc345f07b082c96319573fb6e66dce478892862ddee48410faecb05d1f2 3026 
udisks2_2.7.2-2.dsc
 e96ad56de9baf8021cf5a1cc5d8de8e2b1f2187ee4154962da0e6aba414d0f49 13308 
udisks2_2.7.2-2.debian.tar.xz
 

Bug#873634: marked as done (missing module files libbd_*.so)

[Debian Bug Tracking System]

Your message dated Wed, 30 Aug 2017 09:06:08 +
with message-id 
and subject line Bug#873627: fixed in udisks2 2.7.2-2
has caused the Debian Bug report #873627,
regarding missing module files libbd_*.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.)


-- 
873627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873627
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: udisks2
Version: 2.7.2-1
Severity: important

Hi,

I just upgraded udisks2 package to the new sid version and it failed to start 
its service:

# systemctl status udisks2.service

Aug 29 18:32:10 helios systemd[1]: Starting Disk Manager...
Aug 29 18:32:10 helios udisksd[7107]: udisks daemon version 2.7.2 starting
Aug 29 18:32:10 helios udisksd[7107]: failed to load module swap: 
libbd_swap.so.2: cannot open shared object file: No such file or directory
Aug 29 18:32:10 helios udisksd[7107]: failed to load module loop: 
libbd_loop.so.2: cannot open shared object file: No such file or directory
Aug 29 18:32:10 helios udisksd[7107]: failed to load module crypto: 
libbd_crypto.so.2: cannot open shared object file: No such file or directory
Aug 29 18:32:10 helios udisksd[7107]: failed to load module mdraid: 
libbd_mdraid.so.2: cannot open shared object file: No such file or directory
Aug 29 18:32:10 helios systemd[1]: udisks2.service: Main process exited, 
code=killed, status=5/TRAP
Aug 29 18:32:10 helios systemd[1]: Failed to start Disk Manager.

I used packages.d.o to find the package which contains these files, but haven't 
found one.

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

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

Versions of packages udisks2 depends on:
ii  dbus   1.11.16+really1.10.22-1
ii  init-system-helpers1.49
ii  libacl12.2.52-3+b1
ii  libatasmart4   0.19-4+b1
ii  libblockdev2   2.11-2
ii  libc6  2.24-17
ii  libglib2.0-0   2.53.6-1
ii  libgudev-1.0-0 230-3
ii  libpam-systemd 234-2.3
ii  libpolkit-agent-1-00.113-6
ii  libpolkit-gobject-1-0  0.113-6
ii  libsystemd0234-2.3
ii  libudisks2-0   2.7.2-1
ii  parted 3.2-17
ii  udev   234-2.3

Versions of packages udisks2 recommends:
ii  dosfstools   4.1-1
ii  e2fsprogs1.43.5-1
ii  eject2.1.5+deb1+cvs20081104-13.2
ii  exfat-utils  1.2.7-1
ii  ntfs-3g  1:2016.2.22AR.2-2
ii  policykit-1  0.113-6
pn  udftools 

Versions of packages udisks2 suggests:
ii  btrfs-progs 4.12-1
ii  cryptsetup-bin  2:1.7.3-4
pn  f2fs-tools  
pn  mdadm   
pn  nilfs-tools 
pn  reiserfsprogs   
pn  xfsprogs

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: udisks2
Source-Version: 2.7.2-2

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

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

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

Debian distribution maintenance software
pp.
Andreas Henriksson  (supplier of updated udisks2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 30 Aug 2017 09:36:18 +0200
Source: udisks2
Binary: udisks2 udisks2-doc libudisks2-0 libudisks2-dev gir1.2-udisks-2.0
Architecture: source
Version: 2.7.2-2
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Andreas Henriksson 
Description:
 gir1.2-udisks-2.0 - GObject based library to access udisks2 - introspection 
data
 libudisks2-0 - GObject based library to access udisks2
 libudisks2-dev - GObject based library to access udisks2 - development files
 udisks2- D-Bus service to access and manipulate storage devices
 udisks2-doc - udisks2 

Bug#871486: marked as done (kvmtool FTBFS on arm* with gcc 7)

[Debian Bug Tracking System]

Your message dated Wed, 30 Aug 2017 08:59:20 +
with message-id 
and subject line Bug#871486: fixed in kvmtool 0.20170609-1
has caused the Debian Bug report #871486,
regarding kvmtool FTBFS on arm* with gcc 7
to be marked as done.

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

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


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

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

...
arm/fdt.c: In function 'setup_fdt':
arm/fdt.c:58:45: error: '%lx' directive output may be truncated writing between 
1 and 10 bytes into a region of size 4 [-Werror=format-truncation=]
   snprintf(cpu_name, CPU_NAME_MAX_LEN, "cpu@%lx", mpidr);
 ^~~
arm/fdt.c:58:40: note: directive argument in the range [0, 1095233437695]
   snprintf(cpu_name, CPU_NAME_MAX_LEN, "cpu@%lx", mpidr);
^
In file included from /usr/include/stdio.h:938:0,
 from include/kvm/util.h:13,
 from include/kvm/disk-image.h:5,
 from include/kvm/kvm-config.h:4,
 from include/kvm/kvm.h:5,
 from arm/fdt.c:3:
/usr/include/aarch64-linux-gnu/bits/stdio2.h:64:10: note: 
'__builtin___snprintf_chk' output between 6 and 15 bytes into a destination of 
size 8
   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
  ^~~~
__bos (__s), __fmt, __va_arg_pack ());
~
...
--- End Message ---
--- Begin Message ---
Source: kvmtool
Source-Version: 0.20170609-1

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

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

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

Debian distribution maintenance software
pp.
Riku Voipio  (supplier of updated kvmtool package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 30 Aug 2017 10:17:33 +0300
Source: kvmtool
Binary: kvmtool
Architecture: source
Version: 0.20170609-1
Distribution: sid
Urgency: medium
Maintainer: Riku Voipio 
Changed-By: Riku Voipio 
Description:
 kvmtool- Native Linux KVM TOOL
Closes: 87333 871486
Changes:
 kvmtool (0.20170609-1) sid; urgency=medium
 .
   * New upstream snapshot, closes: #871486
   * Apply patch to fix libc-dev FTBFS, closes: #87333
Checksums-Sha1:
 159ff20243b1d10eaae2e6d0de78dde826a104b9 2224 kvmtool_0.20170609-1.dsc
 3309fdc720ed7b7fadbba940e9ea99b69413457e 194824 kvmtool_0.20170609.orig.tar.xz
 2e9dfd34b397131fd774513e5a592e2f86304094 3484 
kvmtool_0.20170609-1.debian.tar.xz
 2ece356199bcb01428374be335d096de84998e1f 9840 
kvmtool_0.20170609-1_amd64.buildinfo
Checksums-Sha256:
 2e34e362e36fef0052ea2149d9a618f15209ba0bd2df432e97dba97c5d41c834 2224 
kvmtool_0.20170609-1.dsc
 6b378c4db03538e5da104b751cc5c41869a2c2eeba5c3a0bfb5121a317c04c91 194824 
kvmtool_0.20170609.orig.tar.xz
 45613946533b2694ca7fbaea767daeaa19469926f302f320ee4b2ea22cd77d4b 3484 
kvmtool_0.20170609-1.debian.tar.xz
 b4621ae73313c64b49e40c5bedb877d8466e42ba48829bed842c14098261f676 9840 
kvmtool_0.20170609-1_amd64.buildinfo
Files:
 1ce809a4d2ea3b5bf9bba66a53cada1b 2224 kernel optional kvmtool_0.20170609-1.dsc
 a6e0d6fad6a9997b62ea80d6a805adbc 194824 kernel optional 
kvmtool_0.20170609.orig.tar.xz
 fef3504598d0339d6989c5d86c7e0929 3484 kernel optional 
kvmtool_0.20170609-1.debian.tar.xz
 3df65cda4626e370b5dfdfb4fed714d1 9840 kernel optional 
kvmtool_0.20170609-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJLBAEBCAA1FiEE/4IDyMORmK4FgUHvtEiQ3t48m8AFAlmmbHwXHHJpa3Uudm9p
cGlvQGxpbmFyby5vcmcACgkQtEiQ3t48m8CGcg/8DvByTLzbSrTwJ1lK4CF17v/q
87JbwataZp2GviA1zwYmqVmFqgdfEfvnq26vPCJfW6B7iFNiSkTLFVd1nNP682P7
RU1OIQ8JTgGtWIzd61NAFp1euNm6RZJDt/2PWrc9OECE95VtGFGYLoCyPNbOdbqd
GQaaDXfR4GkLhVnHWPsD5HPKZXvrA0MLF5Vt5YY0A4dfxoxmR2VNrrLYlwkKwhS2

Bug#873676: marked as done (breezy: FTBFS: test_unicode_commit_message_is_filename fails in C locale)

[Debian Bug Tracking System]

Your message dated Wed, 30 Aug 2017 08:53:11 +
with message-id 
and subject line Bug#873676: fixed in breezy 3.0.0~bzr6772-1
has caused the Debian Bug report #873676,
regarding breezy: FTBFS: test_unicode_commit_message_is_filename fails in C 
locale
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.)


-- 
873676: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873676
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: breezy
Version: 3.0.0~bzr6753-1
Severity: serious
Justification: fails to build from source

Builds of breezy under the traditional C locale (as on the
autobuilders, implicitly) have been failing as detailed below.  Please
try arranging for debian/rules to export LC_ALL=C.UTF-8, which should
be available by default (via libc-bin) these days.

Thanks!

==
ERROR: 
breezy.tests.blackbox.test_commit.TestCommit.test_unicode_commit_message_is_filename
--
Traceback (most recent call last):
testtools.testresult.real._StringException: log: {{{
19.942  run brz: ['init']
19.942  breezy version: 3.0.0dev1
19.943  brz arguments: [u'init']
19.960  creating repository in 
file:///tmp/testbzr-qu2rYD.tmp/breezy.tests.blackbox.test_commit.TestCommit.test_unicode_commit_message_is_filename/work/.bzr/.
19.965  creating branch  in 
file:///tmp/testbzr-qu2rYD.tmp/breezy.tests.blackbox.test_commit.TestCommit.test_unicode_commit_message_is_filename/work/
19.983  trying to create missing lock 
'/tmp/testbzr-qu2rYD.tmp/breezy.tests.blackbox.test_commit.TestCommit.test_unicode_commit_message_is_filename/work/.bzr/checkout/dirstate'
19.984  opening working tree 
'/tmp/testbzr-qu2rYD.tmp/breezy.tests.blackbox.test_commit.TestCommit.test_unicode_commit_message_is_filename/work'
20.000  opening working tree 
'/tmp/testbzr-qu2rYD.tmp/breezy.tests.blackbox.test_commit.TestCommit.test_unicode_commit_message_is_filename/work'
20.004  output:
'Created a standalone tree (format: 2a)\n'
20.005  run brz: ['add']
20.005  breezy version: 3.0.0dev1
20.005  brz arguments: [u'add']
20.015  opening working tree 
'/tmp/testbzr-qu2rYD.tmp/breezy.tests.blackbox.test_commit.TestCommit.test_unicode_commit_message_is_filename/work'
20.027  skip control directory '.bzr'
20.027  creating config directory: 
'/tmp/testbzr-qu2rYD.tmp/breezy.tests.blackbox.test_commit.TestCommit.test_unicode_commit_message_is_filename/home/breezy'
20.032  output:
'adding "?"\n'
20.032  run brz: ['commit', '-m', u'\u20ac']
20.032  breezy version: 3.0.0dev1
20.032  brz arguments: [u'commit', u'-m', u'\u20ac']
20.044  opening working tree 
'/tmp/testbzr-qu2rYD.tmp/breezy.tests.blackbox.test_commit.TestCommit.test_unicode_commit_message_is_filename/work'
}}}

Traceback (most recent call last):
  File 
"/<>/build/lib.linux-aarch64-2.7/breezy/tests/blackbox/test_commit.py",
 line 144, in test_unicode_commit_message_is_filename
out, err = self.run_bzr(['commit', '-m', file_name])
  File "/<>/build/lib.linux-aarch64-2.7/breezy/tests/__init__.py", 
line 2021, in run_bzr
working_dir=working_dir,
  File "/<>/build/lib.linux-aarch64-2.7/breezy/tests/__init__.py", 
line 1923, in _run_bzr_autosplit
encoding=encoding, stdin=stdin, working_dir=working_dir,
  File "/<>/build/lib.linux-aarch64-2.7/breezy/tests/__init__.py", 
line 1965, in _run_bzr_core
args)
  File "/<>/build/lib.linux-aarch64-2.7/breezy/tests/__init__.py", 
line 2301, in apply_redirected
return a_callable(*args, **kwargs)
  File "/<>/build/lib.linux-aarch64-2.7/breezy/commands.py", line 
1309, in run_bzr_catch_user_errors
return run_bzr(argv)
  File "/<>/build/lib.linux-aarch64-2.7/breezy/commands.py", line 
1199, in run_bzr
ret = run(*run_argv)
  File "/<>/build/lib.linux-aarch64-2.7/breezy/commands.py", line 
755, in run_argv_aliases
return self.run(**all_cmd_args)
  File "/<>/build/lib.linux-aarch64-2.7/breezy/commands.py", line 
779, in run
return self._operation.run_simple(*args, **kwargs)
  File "/<>/build/lib.linux-aarch64-2.7/breezy/cleanup.py", line 
136, in run_simple
self.cleanups, self.func, *args, **kwargs)
  File "/<>/build/lib.linux-aarch64-2.7/breezy/cleanup.py", line 
165, in _do_with_cleanups
result = func(*args, **kwargs)
  File "/<>/build/lib.linux-aarch64-2.7/breezy/builtins.py", line 
3616, in run
ui.ui_factory.show_warning(warning_msg)
  File "/<>/build/lib.linux-aarch64-2.7/breezy/ui/text.py", line 
343, in show_warning
self.stderr.write("bzr: 

Bug#873697: libtext-bibtex-perl FTBFS on arm*/ppc64el: t/unlimited.t (Wstat: 11 Tests: 4 Failed: 0)

[Adrian Bunk]

Source: libtext-bibtex-perl
Version: 0.83-1
Severity: serious

https://buildd.debian.org/status/package.php?p=libtext-bibtex-perl=sid

...
Test Summary Report
---
t/unlimited.t (Wstat: 11 Tests: 4 Failed: 0)
  Non-zero wait status: 11
Files=13, Tests=544,  2 wallclock secs ( 0.14 usr  0.04 sys +  1.92 cusr  0.24 
csys =  2.34 CPU)
Result: FAIL
Failed 1/13 test programs. 0/544 subtests failed.
dh_auto_test: perl Build test --verbose 1 returned exit code 255
debian/rules:6: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2

Processed: found 865633 in 0.33-3.3

[Debian Bug Tracking System]

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

> found 865633 0.33-3.3
Bug #865633 [src:spice-gtk] can't drag windows or click "Activities" in GNOME 3 
guest
Marked as found in versions spice-gtk/0.33-3.3.
> thanks
Stopping processing here.

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

Bug#873694: python-greenlet FTBFS on ppc64el: error: PIC register clobbered by 'r2' in 'asm'

[GCS]

On Wed, Aug 30, 2017 at 10:13 AM, Adrian Bunk  wrote:
> powerpc64le-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
> -Wstrict-prototypes -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.6m -c greenlet.c -o 
> build/temp.linux-ppc64le-3.6/greenlet.o -fno-tree-dominator-opts
> In file included from slp_platformselect.h:16:0,
>  from greenlet.c:328:
> platform/switch_ppc64_linux.h: In function 'slp_switch':
> platform/switch_ppc64_linux.h:72:5: error: PIC register clobbered by 'r2' in 
> 'asm'
>  __asm__ volatile ("" : : : REGS_TO_SAVE);
>  ^~~
> platform/switch_ppc64_linux.h:85:5: error: PIC register clobbered by 'r2' in 
> 'asm'
>  __asm__ volatile ("" : : : REGS_TO_SAVE);
>  ^~~
[...]
> http://gcc.gnu.org/gcc-7/changes.html
> - GCC now diagnoses inline assembly that clobbers register r2. This has 
> always been invalid code, and is no longer quietly tolerated.
 Already seen and found this, thanks. Solution is pending.

Laszlo/GCS

Bug#873696: python-intbitset builds with "-march=core2 -mtune=native"

[Adrian Bunk]

Source: python-intbitset
Version: 2.3.0-1
Severity: serious

https://buildd.debian.org/status/package.php?p=python-intbitset=sid

...
aarch64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
-Wstrict-prototypes -fno-strict-aliasing -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/usr/include/python2.7 -c intbitset/intbitset.c -o 
build/temp.linux-arm64-2.7/intbitset/intbitset.o -O3 -march=core2 -mtune=native
cc1: error: unknown value 'core2' for -march
error: command 'aarch64-linux-gnu-gcc' failed with exit status 1
E: pybuild pybuild:283: build: plugin distutils failed with: exit code=1: 
/usr/bin/python setup.py build 
dh_auto_build: pybuild --build --test-nose -i python{version} -p 2.7 returned 
exit code 13
debian/rules:10: recipe for target 'override_dh_auto_build-arch' failed
make[1]: *** [override_dh_auto_build-arch] Error 25


Neither option is permitted here:
- -march=core2 is not available on non-x86
- on i386 and amd64, -march=core2 violates the
  baseline of the Deban architecture
- -mtune=native gives different packages (with different performance)
  depending on the buildd used

Bug#873693: tslib FTBFS: configure.ac:66: error: possibly undefined macro: AC_CHECK_LIB

[Adrian Bunk]

Source: tslib
Version: 1.12-1
Severity: serious

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

...
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4/internal'.
libtoolize: copying file 'm4/internal/libtool.m4'
libtoolize: copying file 'm4/internal/ltoptions.m4'
libtoolize: copying file 'm4/internal/ltsugar.m4'
libtoolize: copying file 'm4/internal/ltversion.m4'
libtoolize: copying file 'm4/internal/lt~obsolete.m4'
configure.ac:66: error: possibly undefined macro: AC_CHECK_LIB
  If this token and others are legitimate, please use m4_pattern_allow.
  See the Autoconf documentation.
autoreconf: /usr/bin/autoconf failed with exit status: 1
dh_autoreconf: autoreconf -f -i returned exit code 1
debian/rules:20: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2

Bug#873694: python-greenlet FTBFS on ppc64el: error: PIC register clobbered by 'r2' in 'asm'

[Adrian Bunk]

Source: python-greenlet
Version: 0.4.12-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=python-greenlet=ppc64el=0.4.12-1=1504055313=0

...
running build_ext
building 'greenlet' extension
creating build
creating build/temp.linux-ppc64le-3.6
powerpc64le-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
-Wstrict-prototypes -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.6m -c greenlet.c -o 
build/temp.linux-ppc64le-3.6/greenlet.o -fno-tree-dominator-opts
In file included from slp_platformselect.h:16:0,
 from greenlet.c:328:
platform/switch_ppc64_linux.h: In function 'slp_switch':
platform/switch_ppc64_linux.h:72:5: error: PIC register clobbered by 'r2' in 
'asm'
 __asm__ volatile ("" : : : REGS_TO_SAVE);
 ^~~
platform/switch_ppc64_linux.h:85:5: error: PIC register clobbered by 'r2' in 
'asm'
 __asm__ volatile ("" : : : REGS_TO_SAVE);
 ^~~
error: command 'powerpc64le-linux-gnu-gcc' failed with exit status 1
debian/rules:25: recipe for target 'build-python3.6' failed
make[1]: *** [build-python3.6] Error 1
make[1]: Leaving directory '/<>'
debian/rules:16: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2



http://gcc.gnu.org/gcc-7/changes.html
- GCC now diagnoses inline assembly that clobbers register r2. This has always 
been invalid code, and is no longer quietly tolerated.

Processed: tagging 873512, bug 873512 is forwarded to https://github.com/statsmodels/statsmodels/issues/3892

[Debian Bug Tracking System]

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

> tags 873512 + upstream
Bug #873512 [src:statsmodels] statsmodels FTBFS with Cython 0.26
Added tag(s) upstream.
> forwarded 873512 https://github.com/statsmodels/statsmodels/issues/3892
Bug #873512 [src:statsmodels] statsmodels FTBFS with Cython 0.26
Set Bug forwarded-to-address to 
'https://github.com/statsmodels/statsmodels/issues/3892'.
> thanks
Stopping processing here.

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

Bug#873627: udisks2 in sid apparently left me with a borked system in plasma(?)

[Michał Milanowski]

This solves issue for me as well. aprropriate libblockdev-* libs
should be added as
required by udisks2

On Wed, 30 Aug 2017 07:37:00 +0200 Daniel Schaal  wrote:
> I'm experiencing the same issue. I attached the log output and the
> backtrace of the coredump.
>
> After installing the missing plugins (libblockdev-* packages) it
> complains about, I don't get this issue anymore.
>
> syslog output:
> -
> Starting Disk Manager...
> udisks daemon version 2.7.2 starting
> failed to load module mdraid: libbd_mdraid.so.2: cannot open shared
> object file: No such file or directory
> Cannot load the part plugin: The 'sgdisk' utility is not available
> failed to load module fs: libbd_fs.so.2: cannot open shared object file:
> No such file or directory
> Error initializing libblockdev library: Failed to load plugins
> (g-bd-init-error-quark, 0)
> traps: udisksd[2390] trap int3 ip:7f77dd711921 sp:7ffce682cbd0 error:0
> in libglib-2.0.so.0.5306.0[7f77dd6c1000+111000]
> Started Process Core Dump (PID 2395/UID 0).
> udisks2.service: Main process exited, code=dumped, status=5/TRAP
> Failed to start Disk Manager.
> udisks2.service: Unit entered failed state.
> udisks2.service: Failed with result 'core-dump'.
> --
>
> Backtrace:
> -
> #0  _g_log_abort (breakpoint=breakpoint@entry=1) at
> ../../../../glib/gmessages.c:554
> #1  0x7fd1ff261f41 in g_log_writer_default (log_level=6,
> log_level@entry=G_LOG_LEVEL_ERROR, fields=fields@entry=0x7ffc32a375a0,
> n_fields=n_fields@entry=3, user_data=user_data@entry=0x0)
>  at ../../../../glib/gmessages.c:2628
> #2  0x7fd1ff2604be in g_log_structured_array
> (log_level=G_LOG_LEVEL_ERROR, fields=0x7ffc32a375a0, n_fields=3) at
> ../../../../glib/gmessages.c:1941
> #3  0x7fd1ff2607b7 in g_log_structured (log_domain=0x55ea532e0c08
> "udisks", log_level=G_LOG_LEVEL_ERROR) at ../../../../glib/gmessages.c:1768
> #4  0x55ea532d8e9b in udisks_log ()
> #5  0x55ea532ad74f in ?? ()
> #6  0x7fd1ff538510 in g_object_new_internal
> (class=class@entry=0x55ea53e38c00, params=params@entry=0x7ffc32a38060,
> n_params=n_params@entry=4) at ../../../../gobject/gobject.c:1821
> #7  0x7fd1ff53a4e0 in g_object_new_valist
> (object_type=94464918131104, first_property_name=,
> var_args=var_args@entry=0x7ffc32a381b0) at
> ../../../../gobject/gobject.c:2104
> #8  0x7fd1ff53a859 in g_object_new (object_type=,
> first_property_name=) at ../../../../gobject/gobject.c:1624
> #9  0x55ea532add55 in udisks_daemon_new ()
> #10 0x55ea532aceab in ?? ()
> #11 0x7fd1ff83de74 in connection_get_cb (source_object= out>, res=0x55ea53e41030, user_data=0x55ea53e34e70) at
> ../../../../gio/gdbusnameowning.c:487
> #12 0x7fd1ff801fd3 in g_task_return_now (task=0x55ea53e41030) at
> ../../../../gio/gtask.c:1145
> #13 0x7fd1ff8029f6 in g_task_return (task=0x55ea53e41030,
> type=) at ../../../../gio/gtask.c:1203
> #14 0x7fd1ff830b92 in bus_get_async_initable_cb

Bug#844861: wsjtx: FTBFS: ld: final link failed: Nonrepresentable section on output

[Steve Langasek]

Package: wsjtx
Version: 1.1.r3496-3.2
Followup-For: Bug #844861
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu artful ubuntu-patch

Hello,

The fix for this build failure is trivial; just don't disable pie in the
hardening flags for the build.  Now that PIE is enabled by default in
Debian, whatever issue caused wsjtx to fail before when building with PIE
has been resolved.

I have built wsjtx on amd64 with this patch and verified that the resulting
binary runs.

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru wsjtx-1.1.r3496/debian/rules wsjtx-1.1.r3496/debian/rules
--- wsjtx-1.1.r3496/debian/rules2016-10-03 03:49:36.0 -0700
+++ wsjtx-1.1.r3496/debian/rules2017-08-29 23:05:22.0 -0700
@@ -4,7 +4,7 @@
 #export DH_VERBOSE=1
 
 # enable hardedning.  Don't enable PIE as it causes wsjtx to segfault 
immediately
-export DEB_BUILD_MAINT_OPTIONS = hardening=+all,-pie
+export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
 override_dh_auto_configure:
echo "running debian/rules/override_dh_auto_configure"

Bug#873627: udisks2 in sid apparently left me with a borked system in plasma(?)

[Michał Milanowski]

Exactly the same issue on Cinnamon. Cinnamon starts very long and I
can see following in xsession log:

Error creating proxy: Error calling StartServiceByName
org.gtk.vfs.UDisks2VolumeMonitor Timeout was reached

However, Cinnamon finally boots after timeout. But, as somebody
mentioned above, all unneceassary devices like systemd are visible in
file manager. Please make this bug serious. For now, need to downgrade
udisks2 to Testing version.