Bug#899180: marked as done (rustc needs Breaks+Replaces: libstd-rust-dev (<< 1.25.0+dfsg1-2~))

2018-05-22 Thread Debian Bug Tracking System
Your message dated Wed, 23 May 2018 05:20:10 +
with message-id 
and subject line Bug#899180: fixed in rustc 1.26.0+dfsg1-1~exp2
has caused the Debian Bug report #899180,
regarding rustc needs Breaks+Replaces: libstd-rust-dev (<< 1.25.0+dfsg1-2~)
to be marked as done.

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

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


-- 
899180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899180
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rustc
Version: 1.25.0+dfsg1-2
Severity: serious

Unpacking rustc (1.25.0+dfsg1-2) over (1.25.0+dfsg1-1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-f1rkSW/2-rustc_1.25.0+dfsg1-2_amd64.deb (--unpack):
 trying to overwrite 
'/usr/lib/rustlib/x86_64-unknown-linux-gnu/codegen-backends/librustc_trans-llvm.so',
 which is also in package libstd-rust-dev:amd64 1.25.0+dfsg1-1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
--- End Message ---
--- Begin Message ---
Source: rustc
Source-Version: 1.26.0+dfsg1-1~exp2

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

Debian distribution maintenance software
pp.
Ximin Luo  (supplier of updated rustc 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, 22 May 2018 22:00:53 -0700
Source: rustc
Binary: rustc libstd-rust-1.26 libstd-rust-dev rust-gdb rust-lldb rust-doc 
rust-src
Architecture: source
Version: 1.26.0+dfsg1-1~exp2
Distribution: experimental
Urgency: medium
Maintainer: Rust Maintainers 
Changed-By: Ximin Luo 
Description:
 libstd-rust-1.26 - Rust standard libraries
 libstd-rust-dev - Rust standard libraries - development files
 rust-doc   - Rust systems programming language - Documentation
 rust-gdb   - Rust debugger (gdb)
 rust-lldb  - Rust debugger (lldb)
 rust-src   - Rust systems programming language - source code
 rustc  - Rust systems programming language
Closes: 899180
Changes:
 rustc (1.26.0+dfsg1-1~exp2) experimental; urgency=medium
 .
   * Add Breaks+Replaces for older libstd-rust-dev with codegen-backends.
 (Closes: #899180)
   * Backport some test and packaging fixes from Ubuntu.
Checksums-Sha1:
 84fe3eaa3234d91e4a90f888571c75e7746eb1b5 3057 rustc_1.26.0+dfsg1-1~exp2.dsc
 e7c70c3d39ef737de215561548d0e5d06ff7cdb5 59100 
rustc_1.26.0+dfsg1-1~exp2.debian.tar.xz
 4fada4824159744f2f9a3689817cce215913ab2e 7585 
rustc_1.26.0+dfsg1-1~exp2_source.buildinfo
Checksums-Sha256:
 558c8ea2bb9310a683cafb1fe5e977c16cf8715df50668690afa9be72543b811 3057 
rustc_1.26.0+dfsg1-1~exp2.dsc
 f4dcdc7a48510ed82d5d9226144fc46cbaad033988added8a1ed74fa276361a2 59100 
rustc_1.26.0+dfsg1-1~exp2.debian.tar.xz
 a4fa50925f21bb64188670591900aeee11b5a97b4bb55b91967d84e2fbded7c1 7585 
rustc_1.26.0+dfsg1-1~exp2_source.buildinfo
Files:
 d5118717bb7590c6b5979a1cfc399d66 3057 devel optional 
rustc_1.26.0+dfsg1-1~exp2.dsc
 0be5ec4136f6ac3aefeae1f2740fcc8a 59100 devel optional 
rustc_1.26.0+dfsg1-1~exp2.debian.tar.xz
 07ce97f9dbea4749c35892042d862812 7585 devel optional 
rustc_1.26.0+dfsg1-1~exp2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEENmdIajJtsnZtJVVGhg3vO49lC3kFAlsE9a4VHGluZmluaXR5
MEBkZWJpYW4ub3JnAAoJEIYN7zuPZQt5xugP/jCP4Ja0vtyYlOwCNBBq9/eTKkvP
dH+BO7Ba2xDA7ulJznIq+KBk+AE2bLOTdEPxHnP5hA1vYBHWo5Z+DU1ee+RWekLr
ECh3Ncux2u4kTMlWZbkeO1SIcsxk/19LAINUQfy4LpZZVRiE2I+c4Gzb0GMeWRVz
ommSVYaET7D0NfGKoVUpv06qFzeozR/xjL/NtmlhxpXIU0d2VIZX+PxAVGXth21r
U4zw6r6dPCrAqfrvGDfVEjeeAbOAhWdMqepYerZeMn8gEDsW+od4QoojIj8BjEae
eK+xzkOp9sWxkR27vHH+d5pxJ9q3xV9uvZ0uHLWwc15dBzWNuyWaRPbx7raZDPvi
Zkd0Q53oypGvIMl1NrJ34wIcCP9TaUCKQ07yAs59eeK/8Y6eSGVQLpm5+Cqm7Smk
dpw+x1rR+fbH+nwm0ri2G+IMOaNSLOlS4HAT4i94S8YdEiekLohuGS8MZo6fjrz6
iRgZLhozwRcJy9BR2blA1ucr67eB/71ovZllujR3hUreOiB5LyU+JMp5Y4cW91VX
JfVuVWEobjqMy199SzSX989hOJKVfuvA+/1b5C9A+L/Urns3Zqyo+B/gQeLxAY6y
8fY9JMqSrHnbrU8W/cMWoQuHDQiCJ822JUqtKpAYllt8UAu6vhJHiF+5sqTi2Ohv
zjbUXV/MHNPW9Pho
=EeVg
-END PGP SIGNATURE End Message ---


Processed (with 1 error): Re: Bug#899342: bluez 5.49-2 preinst is improperly authored and fails during preinstall

2018-05-22 Thread Debian Bug Tracking System
Processing control commands:

> merge 899342 899340
Bug #899342 [bluez] bluez 5.49-2 preinst is improperly authored and fails 
during preinstall
Unable to merge bugs because:
package of #899340 is 'src:bluez' not 'bluez'
Failed to merge 899342: Did not alter merged bugs.


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



Processed (with 1 error): Re: Bug#899342: bluez 5.49-2 preinst is improperly authored and fails during preinstall

2018-05-22 Thread Debian Bug Tracking System
Processing control commands:

> merge 899342 899340
Bug #899342 [bluez] bluez 5.49-2 preinst is improperly authored and fails 
during preinstall
Unable to merge bugs because:
package of #899340 is 'src:bluez' not 'bluez'
Failed to merge 899342: Did not alter merged bugs.


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



Bug#899340: Bug#899342: bluez 5.49-2 preinst is improperly authored and fails during preinstall

2018-05-22 Thread Nobuhiro Iwamatsu
Control: merge 899342 899340

Hi,

Thanks for your report.
This already fixed in -3.

Best regards,
  Nobuhiro


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



Bug#896722: marked as done (apt-listdifferences: missing build dependency on dh-python)

2018-05-22 Thread Debian Bug Tracking System
Your message dated Wed, 23 May 2018 04:49:21 +
with message-id 
and subject line Bug#896722: fixed in apt-listdifferences 1.20180523
has caused the Debian Bug report #896722,
regarding apt-listdifferences: missing build dependency on dh-python
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.)


-- 
896722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896722
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apt-listdifferences
Version: 1.20170813
Severity: serious

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

...
 fakeroot debian/rules clean
dh clean --with python3
dh: unable to load addon python3: Can't locate 
Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the 
Debian::Debhelper::Sequence::python3 module) (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.26.2 /usr/local/share/perl/5.26.2 
/usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 10) line 
1.
BEGIN failed--compilation aborted at (eval 10) line 1.

make: *** [debian/rules:6: clean] Error 2
--- End Message ---
--- Begin Message ---
Source: apt-listdifferences
Source-Version: 1.20180523

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

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated apt-listdifferences 
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 May 2018 04:16:34 +
Source: apt-listdifferences
Binary: apt-listdifferences
Architecture: source
Version: 1.20180523
Distribution: unstable
Urgency: medium
Maintainer: Michael Gilbert 
Changed-By: Michael Gilbert 
Description:
 apt-listdifferences - source differences notification tool
Closes: 896722 898462
Changes:
 apt-listdifferences (1.20180523) unstable; urgency=medium
 .
   * Update to debhelper 11.
   * Update standards to 4.1.4.
   * Change priority to optional.
   * Add dh-python build dependency (closes: #896722).
   * Add Brazilian Portuguese translation (closes: #898462).
Checksums-Sha1:
 29f5a11aad56694f32279b84b0d8f6e40a519f60 2241 
apt-listdifferences_1.20180523.dsc
 6c9b8bf818f4c1b1f2965e672bc4df28a7c77ec1 12832 
apt-listdifferences_1.20180523.tar.xz
 6afeb80d76a510f78b4e3b764f00b8a6debd512f 6531 
apt-listdifferences_1.20180523_source.buildinfo
Checksums-Sha256:
 074f25f06a28eed65f71b6e910e4e46b419f516546f2bf593a0254060796f89a 2241 
apt-listdifferences_1.20180523.dsc
 3078e6a9b0dd6c84e107590084d4bb676b956afefefd50fbbce25f1f13708802 12832 
apt-listdifferences_1.20180523.tar.xz
 9fc10d3df98c2bfc7a2d2fbc06cc54c353b2081fd39bc50f0512955529fe188e 6531 
apt-listdifferences_1.20180523_source.buildinfo
Files:
 e6f2e61ec4100136567bc70356d97ae8 2241 utils optional 
apt-listdifferences_1.20180523.dsc
 d474404b44e17c0ca38908d97ef2a659 12832 utils optional 
apt-listdifferences_1.20180523.tar.xz
 0331509cce0cb8d9f7b7bbdbbceff07e 6531 utils optional 
apt-listdifferences_1.20180523_source.buildinfo

-BEGIN PGP SIGNATURE-

iQQzBAEBCgAdFiEEluhy7ASCBulP9FUWuNayzQLW9HMFAlsE76gACgkQuNayzQLW
9HOEuh//XTByyGJb59tjitq/8qebtkHMmcm2rbeWj6SqMTV6S5x44gV9IG8zUUyp
vFyMS00exfAi7z6WbbYoc1x5Cs9uqViVoa2TsZuD6OizhYuE6MVZYYS0wvC+4X9X
m9O/diCVZQZBCzH//IxSfeqfxNqoUspzDL3LmynSNF/SPh/DqObiS97Zyw/OAyEg
GzoJADsz1mxFNVa1h8XmTTllBsRJUmuoQsf1E3juVW0iNMV/DZKaNCGrmbhh1m0G
EIjdqga0X+FvMNj0PS417B4NI/hwpS1YH79quXHULumUEqHO8oc5KTQYPwd9Mo+m
/L+tkW2blvpi6MYFmGuNt+9Wp2Qe/0zDug3lblhbTbMuQNe1mHw0eWzHHuvdO53V
RWRDs8uLPDpR7300s8tyo/blA5gA8F0EDhG+ZpbFEBVmopReslI+xuop358uJUTm
HXr6vMNW4FkITOuuGLctt80gT6vitAZ9ZGBb5kvg46N/XKvwsYSLxmLz6ZxXt6eB
7KR5Ly64L1P7EG63HrqYzSUxAGPHq94EHpgeGkcxnrd4aO2az36Xh/vvMY5/F42H
p0KrenhcM4vKlJUIn7PNzzADD7Pej87wtwtW2Fk+RlLI2oiN1onFhY/ycW+an0PE
Pox53kv5Gdj8ZdzU9S/4Qwfi8rgLGHhPY4KD7ltna1UFFCFSVmkkqR2NRua/i5Dx

Bug#896445: marked as done (cutesdr FTBFS with Qt 5.10)

2018-05-22 Thread Debian Bug Tracking System
Your message dated Wed, 23 May 2018 04:34:43 +
with message-id 
and subject line Bug#896445: fixed in cutesdr 1.20-1
has caused the Debian Bug report #896445,
regarding cutesdr FTBFS with Qt 5.10
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.)


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

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

...
g++ -c -pipe -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-g -O2 -fstack-protector-strong -Wformat -Werror=format-security -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -W -D_REENTRANT -fPIC -DQT_NO_DEBUG 
-DQT_MULTIMEDIA_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB 
-DQT_CORE_LIB -I. -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtMultimedia -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -I. -isystem /usr/include/libdrm -I. 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o plotter.o gui/plotter.cpp
gui/plotter.cpp: In member function 'void CPlotter::DrawOverlay()':
gui/plotter.cpp:681:59: error: no matching function for call to 
'QPainter::drawStaticText(int, int, const QString)'
   painter.drawStaticText(5, y-1, QString::number(dB)+" dB");
   ^
In file included from 
/usr/include/x86_64-linux-gnu/qt5/QtGui/qpaintengine.h:47:0,
 from /usr/include/x86_64-linux-gnu/qt5/QtGui/QtGui:64,
 from ./gui/plotter.h:11,
 from gui/plotter.cpp:41:
/usr/include/x86_64-linux-gnu/qt5/QtGui/qpainter.h:409:10: note: candidate: 
void QPainter::drawStaticText(const QPointF&, const QStaticText&)
 void drawStaticText(const QPointF , const QStaticText 
);
  ^~
/usr/include/x86_64-linux-gnu/qt5/QtGui/qpainter.h:409:10: note:   candidate 
expects 2 arguments, 3 provided
/usr/include/x86_64-linux-gnu/qt5/QtGui/qpainter.h:865:13: note: candidate: 
void QPainter::drawStaticText(const QPoint&, const QStaticText&)
 inline void QPainter::drawStaticText(const QPoint , const QStaticText 
)
 ^~~~
/usr/include/x86_64-linux-gnu/qt5/QtGui/qpainter.h:865:13: note:   candidate 
expects 2 arguments, 3 provided
/usr/include/x86_64-linux-gnu/qt5/QtGui/qpainter.h:870:13: note: candidate: 
void QPainter::drawStaticText(int, int, const QStaticText&)
 inline void QPainter::drawStaticText(int x, int y, const QStaticText 
)
 ^~~~
/usr/include/x86_64-linux-gnu/qt5/QtGui/qpainter.h:870:13: note:   no known 
conversion for argument 3 from 'const QString' to 'const QStaticText&'
make[1]: *** [Makefile:1120: plotter.o] Error 1
--- End Message ---
--- Begin Message ---
Source: cutesdr
Source-Version: 1.20-1

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

Debian distribution maintenance software
pp.
A. Maitland Bottoms  (supplier of updated cutesdr 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: Mon, 21 May 2018 00:26:20 -0400
Source: cutesdr
Binary: cutesdr
Architecture: source
Version: 1.20-1
Distribution: unstable
Urgency: medium
Maintainer: A. Maitland Bottoms 
Changed-By: A. Maitland Bottoms 
Description:
 cutesdr- simple demodulation and spectrum display program
Closes: 810385 896445
Changes:
 cutesdr (1.20-1) unstable; urgency=medium
 .
   * New upstream release - svn commit r68 (Closes: #896445)
   * update to svn r72 - V1.21b0
   * build with libftdi1 (Closes: #810385)
   * bring back siqs_ftdi from cutesdr 1.0.5
Checksums-Sha1:
 69331249eead8449cd8447392bef5f6da9bdc315 2144 cutesdr_1.20-1.dsc
 

Processed: Re: Bug#899342: bluez 5.49-2 preinst is improperly authored and fails during preinstall

2018-05-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 899342 grave
Bug #899342 [bluez] bluez 5.49-2 preinst is improperly authored and fails 
during preinstall
Severity set to 'grave' from 'important'
> stop
Stopping processing here.

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



Processed: found 899332 in 3.3.5+dfsg1-2, tagging 899332 ...

2018-05-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> found 899332 3.3.5+dfsg1-2
Bug #899332 [zookeeper] CVE-2018-8012: Apache ZooKeeper Quorum Peer mutual 
authentication
Marked as found in versions zookeeper/3.3.5+dfsg1-2.
> tags 899332 + upstream fixed-upstream
Bug #899332 [zookeeper] CVE-2018-8012: Apache ZooKeeper Quorum Peer mutual 
authentication
Added tag(s) upstream and fixed-upstream.
> forwarded 899332 https://issues.apache.org/jira/browse/ZOOKEEPER-1045
Bug #899332 [zookeeper] CVE-2018-8012: Apache ZooKeeper Quorum Peer mutual 
authentication
Set Bug forwarded-to-address to 
'https://issues.apache.org/jira/browse/ZOOKEEPER-1045'.
> thanks
Stopping processing here.

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



Bug#859054: libpam-ssh: Please migrate to openssl1.1 in buster

2018-05-22 Thread Jerome BENOIT
Hello,



On 22/05/18 23:52, Moritz Muehlenhoff wrote:
> Hi Jerome,
> 
> On Fri, Oct 13, 2017 at 07:05:26PM +0400, Jerome BENOIT wrote:
>> Dear Sebastian, thanks for your warning.
>>
>> The amount of change might be too heavy for me.
>> Second, pam_ssh seems no more maintained.
>>
>> I have just contacted the upstream maintainer.
> 
> Did you get a reply?

No.

I will have a look if time permit.
And, of course, any patch is welcome.

Cheers,
Jerome

> 
> Cheers,
> Moritz
> 

-- 
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B



signature.asc
Description: OpenPGP digital signature


Bug#899340: bluez: Syntax error in bluez preinst script: 28: : "fi" unexpected (expecting "done")

2018-05-22 Thread Boyuan Yang
Source: bluez
Version: 5.49-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Inside preinst script:

#!/bin/sh

set -e

if dpkg-maintscript-helper supports rm_conffile; then
for conffile in \
"/etc/bluetooth/network.service" \
"/etc/bluetooth/serial.service" \
"/etc/bluetooth/input.service"; do
dpkg-maintscript-helper rm_conffile \
"${conffile}" 3.30-1 bluez-utils -- "$@"
done
dpkg-maintscript-helper rm_conffile \
/etc/dbus-1/system.d/bluez-hcid.conf 3.7-1 bluez-utils -- "$@"

for conffile in \
/etc/bluetooth/rfcomm.conf \
/etc/bluetooth/serial.conf \
/etc/bluetooth/audio.conf; do \
dpkg-maintscript-helper rm_conffile \
${conffile} 5.21-2 bluez -- "$@"

for conffile in \
/etc/bluetooth/proximity.conf; do \
dpkg-maintscript-helper rm_conffile \
${conffile} 5.47-1 bluez -- "$@"
done
fi


Obviously you missed a "done".

--
Regards,
Boyuan Yang



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

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

-- no debconf information



Bug#899338: workaround

2018-05-22 Thread 積丹尼 Dan Jacobson
Here's how I successfully was able to browse finally again:

 Remove the following packages:
1) libwebkit2gtk-4.0-37-gtk2 [2.21.2-1 (experimental, now)]

 Downgrade the following packages:
2) libwebkit2gtk-4.0-37 [2.21.2-1 (experimental, now) -> 2.20.2-1+b1 
(unstable)]



Bug#899338: WTFCrash

2018-05-22 Thread 積丹尼 Dan Jacobson
Package: libjavascriptcoregtk-4.0-18
Version: 2.21.2-1
Severity: grave

1   0xb37f73a4 
/usr/lib/i386-linux-gnu/libjavascriptcoregtk-4.0.so.18(WTFCrash+0x14) 
[0xb37f73a4]
2   0xb340f325 
/usr/lib/i386-linux-gnu/libjavascriptcoregtk-4.0.so.18(_ZN3JSC3JIT20emitSlow_op_in_by_idEPNS_11InstructionERPNS_13SlowCaseEntryE+0x1a5)
 [0xb340f325]
3   0xb33c243a 
/usr/lib/i386-linux-gnu/libjavascriptcoregtk-4.0.so.18(_ZN3JSC3JIT23privateCompileSlowCasesEv+0x60a)
 [0xb33c243a]
4   0xb33c707d 
/usr/lib/i386-linux-gnu/libjavascriptcoregtk-4.0.so.18(_ZN3JSC3JIT21compileWithoutLinkingENS_20JITCompilationEffortE+0x55d)
 [0xb33c707d]
5   0xb34279ae 
/usr/lib/i386-linux-gnu/libjavascriptcoregtk-4.0.so.18(_ZN3JSC11JITWorklist4Plan10compileNowEPNS_9CodeBlockEj+0x6e)
 [0xb34279ae]
6   0xb342484a 
/usr/lib/i386-linux-gnu/libjavascriptcoregtk-4.0.so.18(_ZN3JSC11JITWorklist12compileLaterEPNS_9CodeBlockEj+0x7a)
 [0xb342484a]
7   0xb345093e 
/usr/lib/i386-linux-gnu/libjavascriptcoregtk-4.0.so.18(_ZN3JSC5LLInt26jitCompileAndSetHeuristicsEPNS_9CodeBlockEPNS_9ExecStateEj+0x12e)
 [0xb345093e]
8   0xb344f444 
/usr/lib/i386-linux-gnu/libjavascriptcoregtk-4.0.so.18(+0x778444) [0xb344f444]

Seen in epiphany or webkit minibrowser on pages like
https://www.couchsurfing.com/dashboard
or even after logging in to
bugs.webkit.org .



Bug#889111: marked as done (bluez: Causes extreme non-stop CPU usage leading to notebook overheating quickly)

2018-05-22 Thread Debian Bug Tracking System
Your message dated Wed, 23 May 2018 09:22:25 +0900
with message-id 

and subject line Re: bluez: Causes extreme non-stop CPU usage leading to 
notebook overheating quickly
has caused the Debian Bug report #889111,
regarding bluez: Causes extreme non-stop CPU usage leading to notebook 
overheating quickly
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.)


-- 
889111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889111
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bluez
Version: 5.47-1+b1
Severity: critical
Justification: breaks the whole system

Hello, I initially reported this as a bug to udev/systemd but it resolved after 
removing the "bluez" package from my system,
with no other changes besides that. The original report has all the pertinent 
information:

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

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

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

Versions of packages bluez depends on:
ii  dbus  1.12.2-1
ii  kmod  25-1
ii  libasound21.1.3-5
ii  libc6 2.26-4
ii  libdbus-1-3   1.12.2-1
ii  libdw10.170-0.2
ii  libglib2.0-0  2.54.3-2
ii  libreadline7  7.0-3
ii  libudev1  236-3
ii  lsb-base  9.20170808
ii  udev  236-3

bluez recommends no packages.

Versions of packages bluez suggests:
pn  pulseaudio-module-bluetooth  
--- End Message ---
--- Begin Message ---
Control: tags -1 moreinfo unreproducible

Hi,

I could not reproduce this problem.
I  added moreinfo and unreproducible tag, and close this bug.

Best regards,
  Nobuhiroi

2018-04-08 7:26 GMT+09:00 Nobuhiro Iwamatsu :
> Hi,
>
>> Package: bluez
>> Version: 5.47-1+b1
>> Severity: critical
>> Justification: breaks the whole system
>>
>> Hello, I initially reported this as a bug to udev/systemd but it resolved 
>> after removing the "bluez" package from my system,
>> with no other changes besides that. The original report has all the 
>> pertinent information:
>>
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889110
>
> As also pointed out at 889110, I think that this is not a problem of
> udev or bluez, but
> a problem of kenrel.
> If you delete or rename /lib/udev/rules.d/97-hid2hci.rules and restart
> your sysrtem,
> will this problem occur?
>
> Best regards,
>   Nobuhiro
>
> --
> Nobuhiro Iwamatsu
>iwamatsu at {nigauri.org / debian.org}
>GPG ID: 40AD1FA6



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


Bug#898201: marked as done (bluetoothd segfault in btd_adv_manager_refresh())

2018-05-22 Thread Debian Bug Tracking System
Your message dated Wed, 23 May 2018 00:19:20 +
with message-id 
and subject line Bug#898201: fixed in bluez 5.49-2
has caused the Debian Bug report #898201,
regarding bluetoothd segfault in btd_adv_manager_refresh()
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.)


-- 
898201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898201
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bluez
Version: 5.49-1
Severity: grave

I'm trying to use Bluetooth through the GNOME UI, but bluetoothd keeps
crashing:

$ systemctl status bluetooth
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: signal) since Tue 2018-05-08 14:55:38 BST; 1min 23s 
ago
 Docs: man:bluetoothd(8)
  Process: 13542 ExecStart=/usr/lib/bluetooth/bluetoothd (code=killed, 
signal=SEGV)
 Main PID: 13542 (code=killed, signal=SEGV)
   Status: "Running"
$ sudo dmesg | grep bluetooth
[333848.278325] bluetoothd[13542]: segfault at 8 ip 55983cd7e4d0 sp 
7ffca41fd988 error 4 in bluetoothd[55983cd0a000+10d000]

There seems to be a race condition involved, because if I run
bluetoothd under gdbserver, it usually doesn't crash until I toggle
Bluetooth on and off once or twice.

Anyway, I got the following backtrace:

Program received signal SIGSEGV, Segmentation fault.
btd_adv_manager_refresh (manager=0x0) at src/advertising.c:1176
1176src/advertising.c: No such file or directory.
(gdb) bt
#0  btd_adv_manager_refresh (manager=0x0) at src/advertising.c:1176
#1  0x555d4702 in settings_changed (settings=, 
adapter=0x55888390) at src/adapter.c:543
#2  new_settings_callback (index=, length=, 
param=, user_data=0x55888390) at src/adapter.c:573
#3  0x55603fc8 in request_complete (mgmt=mgmt@entry=0x55880e10, 
status=, opcode=opcode@entry=7, index=index@entry=0, 
length=length@entry=4, param=0x55880e99) at src/shared/mgmt.c:261
#4  0x55604aed in can_read_data (io=, 
user_data=0x55880e10) at src/shared/mgmt.c:353
#5  0x55611203 in watch_callback (channel=, 
cond=, user_data=)
at src/shared/io-glib.c:170
#6  0x776c00f5 in g_main_context_dispatch ()
   from target:/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x776c04c0 in ?? ()
   from target:/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x776c07d2 in g_main_loop_run ()
   from target:/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x5557493b in main (argc=, argv=)
at src/main.c:770

Ben.

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

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

Versions of packages bluez depends on:
ii  dbus  1.12.8-2
ii  kmod  25-1
ii  libasound21.1.6-1
ii  libc6 2.27-3
ii  libdbus-1-3   1.12.8-2
ii  libdw10.170-0.4
ii  libglib2.0-0  2.56.1-2
ii  libreadline7  7.0-5
ii  libudev1  238-4
ii  lsb-base  9.20170808
ii  udev  238-4

bluez recommends no packages.

Versions of packages bluez suggests:
ii  pulseaudio-module-bluetooth  11.1-5

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: bluez
Source-Version: 5.49-2

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

Debian distribution maintenance software
pp.
Nobuhiro Iwamatsu  (supplier of updated bluez 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, 23 May 2018 08:29:05 +0900
Source: bluez
Binary: libbluetooth3 libbluetooth-dev bluetooth bluez bluez-cups bluez-obexd 

Bug#896845: marked as done (bluetoothd crashes when turning on discoverable)

2018-05-22 Thread Debian Bug Tracking System
Your message dated Wed, 23 May 2018 00:19:20 +
with message-id 
and subject line Bug#898201: fixed in bluez 5.49-2
has caused the Debian Bug report #898201,
regarding bluetoothd crashes when turning on discoverable
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.)


-- 
898201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898201
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bluez
Version: 5.49-1
Severity: important
Tags: upstream

Hello,

bluetoothd crashes when turning on discoverable with some Bluetooth
adapters. 5.47-1 works fine.

# bluetoothctl discoverable on

causes:

Program received signal SIGSEGV, Segmentation fault.
btd_adv_manager_refresh (manager=0x0) at src/advertising.c:1176
1176src/advertising.c: Toks failas ar aplankas neegzistuoja.
(gdb) bt
#0  btd_adv_manager_refresh (manager=0x0) at src/advertising.c:1176
#1  0x55bc1d76f702 in settings_changed (settings=, 
adapter=0x55bc1f0a5120) at src/adapter.c:543
#2  new_settings_callback (index=, length=, 
param=, user_data=0x55bc1f0a5120) at src/adapter.c:573
#3  0x55bc1d79efc8 in request_complete (mgmt=mgmt@entry=0x55bc1f09d3e0, 
status=, opcode=opcode@entry=6, index=index@entry=0, 
length=length@entry=4, param=0x55bc1f09d469)
at src/shared/mgmt.c:261
#4  0x55bc1d79faed in can_read_data (io=, 
user_data=0x55bc1f09d3e0) at src/shared/mgmt.c:353
#5  0x55bc1d7ac203 in watch_callback (channel=, 
cond=, user_data=) at src/shared/io-glib.c:170
#6  0x7f9950d1e0f5 in g_main_context_dispatch () from 
target:/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f9950d1e4c0 in ?? () from 
target:/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f9950d1e7d2 in g_main_loop_run () from 
target:/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x55bc1d70f93b in main (argc=, argv=) at 
src/main.c:770
(gdb)

Upstream seems to have fixes for that though but I have not tested them.
It would nice to have them backported since this is a pretty significant
regression.

https://git.kernel.org/pub/scm/bluetooth/bluez.git/log/?qt=grep=btd_adv_manager_refresh

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

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

Versions of packages bluez depends on:
ii  dbus  1.12.6-2
ii  kmod  25-1
ii  libasound21.1.3-5
ii  libc6 2.27-3
ii  libdbus-1-3   1.12.6-2
ii  libdw10.170-0.4
ii  libglib2.0-0  2.56.1-2
ii  libreadline7  7.0-3
ii  libudev1  238-4
ii  lsb-base  9.20170808
ii  udev  238-4

bluez recommends no packages.

Versions of packages bluez suggests:
ii  pulseaudio-module-bluetooth  11.1-5

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: bluez
Source-Version: 5.49-2

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

Debian distribution maintenance software
pp.
Nobuhiro Iwamatsu  (supplier of updated bluez 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, 23 May 2018 08:29:05 +0900
Source: bluez
Binary: libbluetooth3 libbluetooth-dev bluetooth bluez bluez-cups bluez-obexd 
bluez-hcidump bluez-test-tools bluez-test-scripts
Architecture: source
Version: 5.49-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Bluetooth Maintainers 

Changed-By: Nobuhiro Iwamatsu 
Description:
 bluetooth  - Bluetooth support
 bluez  - Bluetooth tools and daemons
 bluez-cups - Bluetooth printer driver for CUPS
 bluez-hcidump - Analyses Bluetooth HCI packets
 bluez-obexd - bluez obex daemon
 bluez-test-scripts - test scripts of bluez
 bluez-test-tools - test tools of bluez
 

Bug#898149: marked as done (Recommends: freerdp-x11 won't be in buster)

2018-05-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 May 2018 23:50:33 +
with message-id 
and subject line Bug#898149: fixed in krdc 4:18.04.1-1
has caused the Debian Bug report #898149,
regarding Recommends: freerdp-x11 won't be in buster
to be marked as done.

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

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


-- 
898149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898149
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: krdc
Version: 4:17.08.3-1
Severity: serious
Justification: Policy 2.2.1

Dear Maintainer,

Due to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890928
freerdp-x11 won't be in buster, was superseded by freerdp2-x11.

Policy 2.2.1:

the packages in main must not require or recommend a package outside of main
for compilation or execution.

Versions of packages krdc depends on:
ii  libc6 2.27-3
ii  libkf5bookmarks5  5.44.0-1
ii  libkf5completion5 5.44.0-1
ii  libkf5configcore5 5.44.0-1
ii  libkf5configgui5  5.44.0-1
ii  libkf5configwidgets5  5.44.0-1
ii  libkf5coreaddons5 5.44.0-1
ii  libkf5dnssd5  5.44.0-1
ii  libkf5i18n5   5.44.0-1
ii  libkf5kcmutils5   5.44.0-1
ii  libkf5notifications5  5.44.0-1
ii  libkf5notifyconfig5   5.44.0-1
ii  libkf5service-bin 5.44.0-1
ii  libkf5service55.44.0-1
ii  libkf5wallet-bin  5.44.0-1
ii  libkf5wallet5 5.44.0-1
ii  libkf5widgetsaddons5  5.44.0-1
ii  libkf5xmlgui5 5.44.0-2+b1
ii  libqt5core5a  5.10.1+dfsg-5
ii  libqt5gui55.10.1+dfsg-5
ii  libqt5widgets55.10.1+dfsg-5
ii  libqt5xml55.10.1+dfsg-5
ii  libstdc++68.1.0-1
ii  libvncclient1 0.9.11+dfsg-1

Versions of packages krdc recommends:
ii  freerdp-x11  1.1.0~git20140921.1.440916e+dfsg1-15

Versions of packages krdc suggests:
ii  khelpcenter  4:17.08.3-1
pn  krfb 

-- no debconf information


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: krdc
Source-Version: 4:18.04.1-1

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

Debian distribution maintenance software
pp.
Sandro Knauß  (supplier of updated krdc 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 May 2018 01:10:11 +0200
Source: krdc
Binary: krdc
Architecture: source
Version: 4:18.04.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Sandro Knauß 
Description:
 krdc   - Remote Desktop Connection client
Closes: 898149
Changes:
 krdc (4:18.04.1-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Sandro Knauß ]
   * Bump debhelper build-dep and compat to 11.
   * Update Vcs links to salsa.
   * Bump Standards-Version to 4.1.4 (No changes needed).
   * New upstream release (18.04.1).
   * use secure copyright format uri.
   * update copyright file for new upstream.
   * Replaceed freerdp-x11 with freerdp2-x11 (Closes: #898149)
Checksums-Sha1:
 64bd362d5959bf72d7ef0d2c2253ddc0d31ac09e 2654 krdc_18.04.1-1.dsc
 0519d675d4057513afe134d3d9efedeb8a557e27 1553624 krdc_18.04.1.orig.tar.xz
 3f6db205aadc60d9dc3da2524c12ed1ccbf2acc8 774 krdc_18.04.1.orig.tar.xz.asc
 8e97c73d80bfd7f2a44887213dca05461e464329 10652 krdc_18.04.1-1.debian.tar.xz
 9b8abf9b66f62707f458d137b43d5c15f62b5c9e 23923 krdc_18.04.1-1_source.buildinfo
Checksums-Sha256:
 b3db6e06f467f1378fc1fd7c49fec427aa750412f5c0dcfa3bb2858d0a5924fc 2654 
krdc_18.04.1-1.dsc
 3d4c1bcb7fd17505b4fed7054ee0e9f13c610da32abb0c95f66bba472948c998 1553624 
krdc_18.04.1.orig.tar.xz
 e9db5e0138f1afb195ddb2f82fcd14af28a6042ec0f66eab25ae8fe1b3984648 774 
krdc_18.04.1.orig.tar.xz.asc
 3d71fe06d82544afb7e80b5edf635a48d19db3f2f788cdceb64ad47bb96069ab 10652 
krdc_18.04.1-1.debian.tar.xz
 6b2c54c3ff096ca11810b3ed7459ea067ffca01b5497e8914bf8beaf9e9cbed0 23923 
krdc_18.04.1-1_source.buildinfo
Files:
 63bdff03de01cfd2efb06254b885370b 2654 kde optional krdc_18.04.1-1.dsc
 72cde018ad3d6b8a8b05b4fca6d984b8 

Processed: Re: bluetoothd crashes when turning on discoverable

2018-05-22 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 grave
Bug #896845 [bluez] bluetoothd crashes when turning on discoverable
Severity set to 'grave' from 'important'
> merge 898201 896845
Bug #898201 [bluez] bluetoothd segfault in btd_adv_manager_refresh()
Bug #898201 [bluez] bluetoothd segfault in btd_adv_manager_refresh()
Added tag(s) upstream.
Bug #896845 [bluez] bluetoothd crashes when turning on discoverable
Merged 896845 898201

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



Processed: Re: CVE-2018-8012: Apache ZooKeeper Quorum Peer mutual authentication

2018-05-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> fixed 899332 3.4.10-1
Bug #899332 [zookeeper] CVE-2018-8012: Apache ZooKeeper Quorum Peer mutual 
authentication
Marked as fixed in versions zookeeper/3.4.10-1.
> thanks
Stopping processing here.

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



Bug#876541: marked as done ("SyntaxError: missing ] after element list" in SieveFilterEditor.js (fixed upstream 0.2.3k))

2018-05-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 May 2018 21:37:32 +
with message-id 
and subject line Bug#876541: fixed in sieve-extension 0.2.12+dfsg-1
has caused the Debian Bug report #876541,
regarding "SyntaxError: missing ] after element list" in SieveFilterEditor.js 
(fixed upstream 0.2.3k)
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.)


-- 
876541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876541
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xul-ext-sieve
Version: 0.2.3h+dfsg-2
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

The filters editing window hangs with Thunderbird 52.3.0, which is currently
available in stretch and buster.

As a consequence it is not possible to edit filters using xul-ext-sieve.

The following error appears in the console:

SyntaxError: missing ] after element list[En savoir plus]
SieveFilterEditor.js:137:42
ReferenceError: onWindowLoad is not defined[En savoir plus]
SieveFilterEditor.xul:1:1

Symptoms match upstream bug 67, which is fixed in upstream release 0.2.3k :
https://github.com/thsmi/sieve/issues/67

Please consider packaging the latest upstream release to fix this.

Regards,

Guillaume



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

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

Versions of packages xul-ext-sieve depends on:
ii  icedove1:52.3.0-4
ii  libjs-codemirror   5.4.0-1
ii  libjs-jquery   3.2.1-1
ii  thunderbird [icedove]  1:52.3.0-4

xul-ext-sieve recommends no packages.

xul-ext-sieve suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: sieve-extension
Source-Version: 0.2.12+dfsg-1

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

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

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

Debian distribution maintenance software
pp.
Martín Ferrari  (supplier of updated sieve-extension package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 22 May 2018 21:00:08 +
Source: sieve-extension
Binary: xul-ext-sieve
Architecture: source
Version: 0.2.12+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Martín Ferrari 
Changed-By: Martín Ferrari 
Description:
 xul-ext-sieve - extension that implements the ManageSieve protocol
Closes: 808645 858079 870198 876541 899131
Changes:
 sieve-extension (0.2.12+dfsg-1) unstable; urgency=medium
 .
   * New upstream release. Closes: #876541, #870198, #808645.
   * debian/control:
 - Adopt the package. Closes: #899131.
 - Automated cme fixes; update Vcs locations.
 - Raise dh compat to 11.
   * debian/copyright: Update Files-Excluded.
   * Update patches.
   * Update watchfile.
   * Use dpkg-maintscript-helper. Closes: #858079.
Checksums-Sha1:
 5a8b63b9ffd94a263ac35708dd91e1417157b867 1958 sieve-extension_0.2.12+dfsg-1.dsc
 0c05151391901d4249eef4c908eca2f3d2161c9a 409164 
sieve-extension_0.2.12+dfsg.orig.tar.bz2
 14f76566858dc32dc19b7d66c594ad10c20e2aa9 17648 
sieve-extension_0.2.12+dfsg-1.debian.tar.xz
 858b90cf8fb43e7e526fc3b0ba248dbb0f974a0b 7027 
sieve-extension_0.2.12+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 95f2cc7bed33586b55d3818d15d25ac20dcc1bc7346762af6606e93dd78a67b0 1958 
sieve-extension_0.2.12+dfsg-1.dsc
 3f63c90c900b7ff652ecbe6bc27529f26e32d6b818d9a7fb79fd54eea67ea8e1 409164 
sieve-extension_0.2.12+dfsg.orig.tar.bz2
 d5dc0485b47e40c3d0bbf92cdd8e0138fe067c108131ee0b7a0c8582b7cb0a1a 17648 
sieve-extension_0.2.12+dfsg-1.debian.tar.xz
 00f38d05f9e657f2c06b7b59873f16972143877c573417d34d4f94ef54b4e3c2 7027 
sieve-extension_0.2.12+dfsg-1_amd64.buildinfo
Files:
 c0fc6ed5d735ce6c272c3dc22ac9db38 1958 mail optional 
sieve-extension_0.2.12+dfsg-1.dsc
 

Bug#858079: marked as done (xul-ext-sieve: makes files disappear from libjs-codemirror on upgrade)

2018-05-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 May 2018 21:37:32 +
with message-id 
and subject line Bug#858079: fixed in sieve-extension 0.2.12+dfsg-1
has caused the Debian Bug report #858079,
regarding xul-ext-sieve: makes files disappear from libjs-codemirror on upgrade
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.)


-- 
858079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858079
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xul-ext-sieve
Version: 0.2.3h+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package removes files that
were installed by another package.
The removed files were already present before the package was installed,
they may have been shipped or created by a dependency.

This was observed on tests from jessie directly to sid as well as from 
stretch to sid.

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

1m41.4s ERROR: FAIL: debsums reports modifications inside the chroot:
  debsums: missing file 
/usr/share/javascript/codemirror/addon/edit/matchbrackets.js (from 
libjs-codemirror package)
  debsums: missing file 
/usr/share/javascript/codemirror/addon/search/searchcursor.js (from 
libjs-codemirror package)
  debsums: missing file /usr/share/javascript/codemirror/lib/codemirror.css 
(from libjs-codemirror package)
  debsums: missing file /usr/share/javascript/codemirror/lib/codemirror.js 
(from libjs-codemirror package)
  debsums: missing file /usr/share/javascript/codemirror/mode/sieve/sieve.js 
(from libjs-codemirror package)
  debsums: missing file /usr/share/javascript/codemirror/theme/eclipse.css 
(from libjs-codemirror package)

This code from the preinst looks extremely fishy
(I only looked at the diff between -1 and -2):

+# versions prior to 0.2.3h+dfsg-2 either shipped a copy of codemirror or
+# symlinks inside the CodeMirror directory. Make sure the directory is
+# removed so it can be replaces with the symlink.
+if [ -d 
/usr/share/xul-ext/sieve/chrome/chromeFiles/content/libs/CodeMirror ] ; then
+  rm -rf 
/usr/share/xul-ext/sieve/chrome/chromeFiles/content/libs/CodeMirror
 fi

1.) this sounds like you should use 
dpkg-maintscript-helper dir_to_symlink ...
2.) there is no version check at all ...

but I still fail to see how this could remove the above files ...


cheers,

Andreas


xul-ext-sieve_0.2.3h+dfsg-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: sieve-extension
Source-Version: 0.2.12+dfsg-1

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

Debian distribution maintenance software
pp.
Martín Ferrari  (supplier of updated sieve-extension package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 22 May 2018 21:00:08 +
Source: sieve-extension
Binary: xul-ext-sieve
Architecture: source
Version: 0.2.12+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Martín Ferrari 
Changed-By: Martín Ferrari 
Description:
 xul-ext-sieve - extension that implements the ManageSieve protocol
Closes: 808645 858079 870198 876541 899131
Changes:
 sieve-extension (0.2.12+dfsg-1) unstable; urgency=medium
 .
   * New upstream release. Closes: #876541, #870198, #808645.
   * debian/control:
 - Adopt the package. Closes: #899131.
 - Automated cme fixes; update Vcs locations.
 - Raise dh compat to 11.
   * debian/copyright: Update Files-Excluded.
   * Update patches.
   * Update watchfile.
   * Use dpkg-maintscript-helper. Closes: #858079.
Checksums-Sha1:
 5a8b63b9ffd94a263ac35708dd91e1417157b867 1958 sieve-extension_0.2.12+dfsg-1.dsc
 0c05151391901d4249eef4c908eca2f3d2161c9a 409164 
sieve-extension_0.2.12+dfsg.orig.tar.bz2
 14f76566858dc32dc19b7d66c594ad10c20e2aa9 17648 
sieve-extension_0.2.12+dfsg-1.debian.tar.xz
 858b90cf8fb43e7e526fc3b0ba248dbb0f974a0b 7027 
sieve-extension_0.2.12+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 

Bug#899334: node-sha.js: FTBFS and autopkgtest failure on 32-bit

2018-05-22 Thread Graham Inggs
Source: node-sha.js
Version: 2.4.11-1
Severity: serious
Tags: patch
Forwarded: https://github.com/crypto-browserify/sha.js/pull/56
User: debian...@lists.debian.org
Usertags: needs-update

Hi Maintainer

Since the upload of 2.4.11-1 to unstable, node-sha.js FTBFS
and fails its autopkgtests on 32-bit architectures [1][2] with the
following error:

RangeError: "size" argument must not be larger than 1073741823
at Function.Buffer.alloc (buffer.js:233:3)
at Test. (/build/1st/node-sha.js-2.4.11/test/test.js:90:24)
at Test.bound [as _cb] (/usr/lib/nodejs/tape/lib/test.js:76:32)
at Test.run (/usr/lib/nodejs/tape/lib/test.js:95:10)
at Test.bound [as run] (/usr/lib/nodejs/tape/lib/test.js:76:32)
at Immediate.next [as _onImmediate]
(/usr/lib/nodejs/tape/lib/results.js:71:15)
at runCallback (timers.js:794:20)
at tryOnImmediate (timers.js:752:5)
at processImmediate [as _immediateCallback] (timers.js:729:5)

Regards
Graham


[1] https://tests.reproducible-builds.org/debian/history/i386/node-sha.js.html
[2] https://tests.reproducible-builds.org/debian/history/armhf/node-sha.js.html



Bug#899332: CVE-2018-8012: Apache ZooKeeper Quorum Peer mutual authentication

2018-05-22 Thread Markus Koschany
Package: zookeeper
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security
Fixed: 3.4.10-1

Hi,

The following vulnerability was published for zookeeper.

CVE-2018-8012[0]:
| No authentication/authorization is enforced when a server attempts to
| join a quorum in Apache ZooKeeper before 3.4.10, and 3.5.0-alpha
| through 3.5.3-beta. As a result an arbitrary end point could join the
| cluster and begin propagating counterfeit changes to the leader.

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-2018-8012
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-8012

Please adjust the affected versions in the BTS as needed.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature


Bug#859054: libpam-ssh: Please migrate to openssl1.1 in buster

2018-05-22 Thread Moritz Muehlenhoff
Hi Jerome,

On Fri, Oct 13, 2017 at 07:05:26PM +0400, Jerome BENOIT wrote:
> Dear Sebastian, thanks for your warning.
> 
> The amount of change might be too heavy for me.
> Second, pam_ssh seems no more maintained.
> 
> I have just contacted the upstream maintainer.

Did you get a reply?

Cheers,
Moritz



Bug#899324: ruby-font-awesome-rails: broken with fonts-font-awesome 5

2018-05-22 Thread Antonio Terceiro
Package: ruby-font-awesome-rails
Version: 4.7.0.2-1
Severity: grave
Justification: renders package unusable

Recently fonts-font-awesome 5 has been uploaded to ustable. There are
some significant changes upstream, including but not limited to font
files being renamed. fonts-font-awesome 5.0.10-4 includes a
compatibility layer for packages that assumed the structure of
FontAwesome v4, but some packages that make too aggressive assumptions
about the internal structure of FontAwesome are beyond help.

This is the case of ruby-font-awesome-rails.

The symlinks to the font files are not broken:

~$ ll /usr/share/ruby-font-awesome-rails/app/assets/fonts/
total 12K
lrwxrwxrwx 1 root root 61 jul  6  2017 fontawesome-webfont.woff2 -> 
../../../../fonts/woff/font-awesome/fontawesome-webfont.woff2
lrwxrwxrwx 1 root root 60 jul  6  2017 fontawesome-webfont.woff -> 
../../../../fonts/woff/font-awesome/fontawesome-webfont.woff
lrwxrwxrwx 1 root root 63 jul  6  2017 fontawesome-webfont.ttf -> 
../../../../fonts/truetype/font-awesome/fontawesome-webfont.ttf
lrwxrwxrwx 1 root root 58 jul  6  2017 fontawesome-webfont.svg -> 
../../../../fonts/svg/font-awesome/fontawesome-webfont.svg
lrwxrwxrwx 1 root root 58 jul  6  2017 fontawesome-webfont.eot -> 
../../../../fonts/eot/font-awesome/fontawesome-webfont.eot
lrwxrwxrwx 1 root root 55 jul  6  2017 FontAwesome.otf -> 
../../../../fonts/opentype/font-awesome/FontAwesome.otf

and, this package includes a modified copy of the FontAwesome CSS file
(/usr/share/ruby-font-awesome-rails/app/assets/stylesheets/font-awesome.css.erb),
that is also out of date.

My suggestion would be to:

- base the CSS template on
  /usr/share/fonts-font-awesome/css/font-awesome.css which is a modified
  version of the FontAwesome v5 stylesheet adding backwards
  compatibility for usage of FontAwesome v4.
- symlink /usr/share/ruby-font-awesome-rails/app/assets/fonts/ directly
  to /usr/share/fonts-font-awesome/webfonts instead of symlinking
  individual files (and probably rename the link from fonts to webfonts)

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

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

Versions of packages ruby-font-awesome-rails depends on:
ii  fonts-font-awesome  5.0.10-4
ii  ruby1:2.5.1

ruby-font-awesome-rails recommends no packages.

ruby-font-awesome-rails suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature


Processed: reopening 899248

2018-05-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reopen 899248
Bug #899248 {Done: Niels Thykier } [debhelper] debhelper: 
upstream changelog no longer installed
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions debhelper/11.3.1.
> thanks
Stopping processing here.

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



Bug#896347: marked as done (python-kopano: kopano fails to import)

2018-05-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 May 2018 19:00:45 +
with message-id 
and subject line Bug#896347: fixed in kopanocore 8.6.1-2
has caused the Debian Bug report #896347,
regarding python-kopano: kopano fails to import
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.)


-- 
896347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896347
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-kopano
Version: 8.6.1-1
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python-kopano importing the module kopano
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/kopano/__init__.py", line 54, in 

from .config import Config, CONFIG
  File "/usr/lib/python2.7/dist-packages/kopano/config.py", line 17, in 
import utils as _utils
  File "/usr/lib/python2.7/dist-packages/kopano/utils.py", line 40, in 
import user as _user
  File "/usr/lib/python2.7/dist-packages/kopano/user.py", line 26, in 
from .store import Store
  File "/usr/lib/python2.7/dist-packages/kopano/store.py", line 62, in 
from . import notification as _notification
  File "/usr/lib/python2.7/dist-packages/kopano/notification.py", line 33, in 

import folder as _folder
  File "/usr/lib/python2.7/dist-packages/kopano/folder.py", line 52, in 
from .recurrence import Occurrence
  File "/usr/lib/python2.7/dist-packages/kopano/recurrence.py", line 42, in 

from dateutil.rrule import (
ImportError: No module named dateutil.rrule

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Source: kopanocore
Source-Version: 8.6.1-2

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

Debian distribution maintenance software
pp.
Carsten Schoenert  (supplier of updated kopanocore 
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, 17 May 2018 16:14:59 +0200
Source: kopanocore
Binary: kopano-libs kopano-core kopano-archiver kopano-backup kopano-common 
kopano-contacts kopano-dev kopano-dagent kopano-gateway kopano-ical kopano-l10n 
kopano-monitor kopano-presence kopano-search kopano-server kopano-spamd 
kopano-spooler kopano-utils python-mapi python-kopano php-mapi
Architecture: source amd64 all
Version: 8.6.1-2
Distribution: unstable
Urgency: medium
Maintainer: Giraffe Maintainers 

Changed-By: Carsten Schoenert 
Description:
 kopano-archiver - Complete and feature rich groupware solution - archiver
 kopano-backup - Complete and feature rich groupware solution - backup
 kopano-common - Complete and feature rich groupware solution - common files
 kopano-contacts - Complete and feature rich groupware solution - contact mapi 
provi
 kopano-core - Metapackage to install the Kopano Core stack
 kopano-dagent - Complete and feature rich groupware solution - delivery agent
 kopano-dev - C++ Development files and libraries for Kopano Core
 kopano-gateway - Complete and feature rich groupware solution - POP3 and IMAP 
gate
 kopano-ical - Complete and feature rich groupware solution - CalDAV and CalDAV
 kopano-l10n - Complete and feature rich groupware solution - l10n files
 kopano-libs - Complete and feature rich groupware solution - Free/Busy library
 kopano-monitor - Complete and feature rich groupware solution - quota monitor
 kopano-presence - Complete and feature rich groupware solution - presence 
daemon
 kopano-search - Complete and feature 

Bug#896324: marked as done (python-tktreectrl: TkTreectrl fails to import)

2018-05-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 May 2018 19:00:52 +
with message-id 
and subject line Bug#896324: fixed in python-tktreectrl 2.0.2-1
has caused the Debian Bug report #896324,
regarding python-tktreectrl: TkTreectrl fails to import
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.)


-- 
896324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896324
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-tktreectrl
Version: 2.0.1-1
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python-tktreectrl importing the module TkTreectrl
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/TkTreectrl/__init__.py", line 71, in 

from TkTreectrl.Treectrl import Treectrl
  File "/usr/lib/python2.7/dist-packages/TkTreectrl/Treectrl.py", line 22, in 

import tkinter
ImportError: No module named tkinter

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Source: python-tktreectrl
Source-Version: 2.0.2-1

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated python-tktreectrl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 18 May 2018 10:28:04 +0200
Source: python-tktreectrl
Binary: python-tktreectrl python3-tktreectrl python-tktreectrl-doc
Architecture: source all
Version: 2.0.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Andreas Tille 
Description:
 python-tktreectrl - Tkinter-based wrapper for Tk TreeCtrl
 python-tktreectrl-doc - documentation and examples for Python TkTreeCtrl
 python3-tktreectrl - Tkinter-based wrapper for Tk TreeCtrl for Python 3
Closes: 890792 896324
Changes:
 python-tktreectrl (2.0.2-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version
 Closes: #896324
   * Reworked watch file
   * Moved to DPMT
   * cme fix dpkg-control
   * debhelper 11
   * Use pybuild
   * Move content from d/README.source to DEP3 patch
   * Add Python3 package
 Closes: #890792
   * Drop unneeded X-Python*-Version fields
   * Do not provide README which only explains installation which is just done
 once the package is installed
   * Testsuite: autopkgtest-pkg-python
Checksums-Sha1:
 bd80c4f68cd8a0cab50576b37ca5be4573552aa3 2319 python-tktreectrl_2.0.2-1.dsc
 e259fd199168838a294c38204eb8b46e0966e36c 79054 
python-tktreectrl_2.0.2.orig.tar.gz
 c7b9f7c527db6a5b2eecc556ceab58bc10024418 2228 
python-tktreectrl_2.0.2-1.debian.tar.xz
 44c47365ab4e4ce9e4006f1ebb5510def717dab1 38266 
python-tktreectrl-doc_2.0.2-1_all.deb
 157d62f97e0f58dbe3d3a5199056291d60e63bac 37948 
python-tktreectrl_2.0.2-1_all.deb
 0bf757b16f40f13993870b7e91550d41d5182bc7 7554 
python-tktreectrl_2.0.2-1_amd64.buildinfo
 f5e09c17e75fca98c60d6871b84b6dce4b9c9c68 38052 
python3-tktreectrl_2.0.2-1_all.deb
Checksums-Sha256:
 efc09462a26b5f60b2ad93f91027f2a5c887cba488986c217c5fbd2af2f71edd 2319 
python-tktreectrl_2.0.2-1.dsc
 725c9c28e38b0ab22bad1b7115ec7ec5735ed8f13b0bac6d02199b9486967b08 79054 
python-tktreectrl_2.0.2.orig.tar.gz
 1e71af08c2f8ae7c2708c93f870c8f0333c17282d46e41a4b513fc1e0d9242b4 2228 
python-tktreectrl_2.0.2-1.debian.tar.xz
 9903b628cacabc33854efc80c40f39a61136fa3e332802370b5e538518698f55 38266 
python-tktreectrl-doc_2.0.2-1_all.deb
 

Bug#899248: closed by Niels Thykier <ni...@thykier.net> (Bug#899248: fixed in debhelper 11.3.1)

2018-05-22 Thread gregor herrmann
On Tue, 22 May 2018 20:14:28 +0200, gregor herrmann wrote:

> Maybe this is unrelated but I just found a situation where debhelper 11.3.1
> doesn't install the upstream changelog anymore.
> 
> + This is libcourriel-perl 0.47 in git at
>   https://salsa.debian.org/perl-team/modules/packages/libcourriel-perl

Same for a couple of other perl packages with either ./Changes or
./ChangeLog.
 
Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Lenny Kravitz: Let Love Rule


signature.asc
Description: Digital Signature


Bug#899248: closed by Niels Thykier <ni...@thykier.net> (Bug#899248: fixed in debhelper 11.3.1)

2018-05-22 Thread gregor herrmann
On Mon, 21 May 2018 20:39:10 +, Debian Bug Tracking System wrote:

>  debhelper (11.3.1) unstable; urgency=medium
>  .
>* dh_installchangelogs: Fix logic error that made
>  dh_installchangelogs incorrectly ignore explicitly passed
>  changelogs.  Thanks to Sven Joachim and Rene Engelhard
>  for reporting the bug.  (Closes: #899248)

Maybe this is unrelated but I just found a situation where debhelper 11.3.1
doesn't install the upstream changelog anymore.

Background:

+ This is libcourriel-perl 0.47 in git at
  https://salsa.debian.org/perl-team/modules/packages/libcourriel-perl

+ We have an upstream changelog at ./Changes:
  % find -iname "change*"
  ./Changes
  ./debian/changelog

+ Build log:
Preparing to unpack .../035-debhelper_11.3.1_all.deb ...
Unpacking debhelper (11.3.1) ...
...
   dh_installchangelogs
install -p -m0644 debian/changelog 
debian/libcourriel-perl/usr/share/doc/libcourriel-perl/changelog.Debian
install -p -m0644 debian/NEWS 
debian/libcourriel-perl/usr/share/doc/libcourriel-perl/NEWS.Debian

+ And lintian complained rightly so about the missing upstream
  changelog:
% debc | grep -i doc
drwxr-xr-x root/root 0 2018-05-22 06:39 ./usr/share/doc/
drwxr-xr-x root/root 0 2018-05-22 06:39 
./usr/share/doc/libcourriel-perl/
-rw-r--r-- root/root  1780 2018-05-20 18:34 
./usr/share/doc/libcourriel-perl/CONTRIBUTING.md.gz
-rw-r--r-- root/root  1028 2018-05-22 06:39 
./usr/share/doc/libcourriel-perl/NEWS.Debian.gz
-rw-r--r-- root/root  2443 2018-05-22 06:39 
./usr/share/doc/libcourriel-perl/changelog.Debian.gz
-rw-r--r-- root/root 10279 2018-05-22 06:39 
./usr/share/doc/libcourriel-perl/copyright
drwxr-xr-x root/root 0 2018-05-22 06:39 
./usr/share/doc/libcourriel-perl/examples/
-rw-r--r-- root/root  2760 2018-05-20 18:34 
./usr/share/doc/libcourriel-perl/examples/sendgrid


With debhelper 11.3 I see what I'm used to see:

   dh_installchangelogs
install -p -m0644 debian/changelog 
debian/libcourriel-perl/usr/share/doc/libcourriel-perl/changelog.Debian
install -p -m0644 debian/NEWS 
debian/libcourriel-perl/usr/share/doc/libcourriel-perl/NEWS.Debian
install -p -m0644 ./Changes 
debian/libcourriel-perl/usr/share/doc/libcourriel-perl/changelog



Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: [DKP]: Lied von Breendonck (Belgien)


signature.asc
Description: Digital Signature


Processed (with 2 errors): yorick-yao is not unmaintained

2018-05-22 Thread Debian Bug Tracking System
Processing control commands:

> not-found -1 yorick-yao/5.4.0-1
Unknown command or malformed arguments to command.

> severity -1 wishlist
Bug #898589 {Done: Thibaut Paumard } [src:yorick-yao] 
yorick-yao: Intent to remove from Debian
Severity set to 'wishlist' from 'serious'
> thanks
Unknown command or malformed arguments to command.


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



Bug#898589: yorick-yao is not unmaintained

2018-05-22 Thread Thibaut Paumard

control: not-found -1 yorick-yao/5.4.0-1
control: severity -1 wishlist
control: thanks

Hi,

I object and I'm closing this bug as yorick-yao is not unmaintained. 
I'll remove it after buster if upstream does not update it.


Regards, Thibaut.



Bug#898589: marked as done (yorick-yao: Intent to remove from Debian)

2018-05-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 May 2018 19:04:17 +0200
with message-id <65ba306d-d78b-c5f1-56a8-4446372c8...@debian.org>
and subject line Yorick-yao is not unmaintained
has caused the Debian Bug report #898589,
regarding yorick-yao: Intent to remove from Debian
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.)


-- 
898589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898589
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yorick-yao
Version: 5.4.0-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

yorick-yao depends on the unmaintained pygtk which the Debian GNOME team is 
trying to remove from Debian.

It looks like yorick-yao itself is unmaintained. Therefore, I intend to file a 
removal bug for yorick-yao. Please reply immediately to let me know if you 
approve or object.

References
--
https://bugs.debian.org/885506
https://lists.debian.org/debian-devel/2018/02/msg00169.html

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

Hi,

This package is not unmaintained.

I'll remove myself after the Buster release if upstream doesn't port it 
to Gtk3.


Regards, Thibaut.--- End Message ---


Bug#882888: marked as done (php-cache-lite FTBFS with phpunit 6.4.4-2)

2018-05-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 May 2018 15:53:24 +
with message-id 
and subject line Bug#882888: fixed in php-cache-lite 1.8.2-1
has caused the Debian Bug report #882888,
regarding php-cache-lite FTBFS with phpunit 6.4.4-2
to be marked as done.

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

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


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

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/php-cache-lite.html

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/php-cache-lite-1.7.16'
cd Cache_Lite-*/ && phpunit tests
PHP Fatal error:  Class 'PHPUnit_Framework_TestCase' not found in 
/build/1st/php-cache-lite-1.7.16/Cache_Lite-1.7.16/tests/ErrorDieTest.php on 
line 14
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 255
--- End Message ---
--- Begin Message ---
Source: php-cache-lite
Source-Version: 1.8.2-1

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

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

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

Debian distribution maintenance software
pp.
Prach Pongpanich  (supplier of updated php-cache-lite 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, 22 May 2018 21:36:42 +0700
Source: php-cache-lite
Binary: php-cache-lite
Architecture: source
Version: 1.8.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: Prach Pongpanich 
Description:
 php-cache-lite -
Closes: 882888
Changes:
 php-cache-lite (1.8.2-1) unstable; urgency=medium
 .
   [ Nishanth Aravamudan ]
   * Remove deprecation warnings on PHP5 and PHP7.
 .
   [ Remi Collet ]
   * drop each usage, deprecated in PHP 7.2
 .
   [ Chuck Burgess ]
   * prep for v1.8.2
 .
   [ Prach Pongpanich ]
   * Fix FTBFS on recent phpunit (Closes: #882888)
   * Update Standards-Version to 4.1.4
   * Bump debhelper compat level to 11
   * Move git repository to salsa
   * Use secure copyright format URI
Checksums-Sha1:
 63b1b5af86d8b41f78f35e46486b90d732b02944 2086 php-cache-lite_1.8.2-1.dsc
 c7e735626d78c3bab6befc057f0f13029d7c37c1 33873 php-cache-lite_1.8.2.orig.tar.gz
 2c249fb09b92b2692f2aeb2ad9904c6607234ea6 4720 
php-cache-lite_1.8.2-1.debian.tar.xz
 4b0945236e7b1861cd5fcd2c67bbb29afbfc7520 7424 
php-cache-lite_1.8.2-1_amd64.buildinfo
Checksums-Sha256:
 8b3bb94cd154b2ede65fce221bfeddbabcd889efbd1f0c028f0e206bd9d2ca64 2086 
php-cache-lite_1.8.2-1.dsc
 636bc73e653775a6c124f632be94392c35b5a747f1288ad70d2aefbc62d079fd 33873 
php-cache-lite_1.8.2.orig.tar.gz
 c5dbc31091f7123dbec33d07c3a0cfe4c4e6687d095e2d5b1e91285f7825a44d 4720 
php-cache-lite_1.8.2-1.debian.tar.xz
 a966095e43836f5298b02168904994688df59085903061bb4b250bf67870d12e 7424 
php-cache-lite_1.8.2-1_amd64.buildinfo
Files:
 77368e84155ae4e7541cd99132484d9d 2086 php optional php-cache-lite_1.8.2-1.dsc
 5a3bb30b288ec396e26cf041b5389923 33873 php optional 
php-cache-lite_1.8.2.orig.tar.gz
 6a2fc9712b17fa6da7bb570d07b4afbc 4720 php optional 
php-cache-lite_1.8.2-1.debian.tar.xz
 f7db82e382891ed88029686b165dc2e3 7424 php optional 
php-cache-lite_1.8.2-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEDKddmHuOz26pRDrYOQkegSPOHAkFAlsEMzYRHHByYWNoQGRl
Ymlhbi5vcmcACgkQOQkegSPOHAkiRg/+P8uthHDSAzUFhczW6+UBAWM5xzesRP++
SkZAY97cINrERj3DSt5UTofU+KudAvoM0djideqRTeNRgGHvXoaNsnHocxq1N1b3
C+GE6AqzVWJ2rIQXNXUuM0Um78ctGGWXViUx9yVMVMUEW6Ndr16g9ckY0ozow3jC
1jNJraDMBZwNHuS/iTsBcwYbse3PCp7oe6PZLZ2AlFUiDLeczvcTBZN8+yAmpuql
cXVLJPfe2IOsW4pdPW3FGR0vLMiqj8c4QHAntjNM8lS8cO02WvBbukUocmvH4WgS
ddkL8JwTXuT1fZWfSFwKJLoQo1QD+SbrMuxUggn/OO/sHc6YK/xIxD57uiRSIYW5
e4aw4/mtKtpJY8Dv5vsAPYSUSVtaEZ15r+HVpGhdIIj/MzqDW/PGdR/tC7rGxv0Y
X1yVFqyrR+cE9gw9A6NtWh8nH9rDNvJwWKkDTDzse16sfHvJuJGmxF9xL6u8x513
eh2b9M7SJQZFsz4lLM7weTZbtvLAkvwI+zQ0Se+2hspklGEV8+FpnMzKNpNSPAUq

Bug#899124: fonts-font-awesome: completely breaks web applications, with no notice

2018-05-22 Thread Vasudev Kamath
Hi Antonio,

Antonio Terceiro  writes:

> Control: forwarded -1 
> https://salsa.debian.org/fonts-team/fonts-font-awesome/merge_requests/1
>
> On Sun, May 20, 2018 at 06:15:08PM -0300, Antonio Terceiro wrote:
>> Control: reopen -1
>> 
>> On Sun, May 20, 2018 at 10:32:38PM +0530, Vasudev Kamath wrote:
>> > Antonio Terceiro  writes:
>> > > 2) revert the changes in fonts-font-awesome in unstable, upload the
>> > > new release to experimental, and give people a few months to adapt.
>> > 
>> > I'm okay with this solution. I've currently fixed the broken links and
>> > uploaded the fixes. If you would like more time to adapt to the version
>> > 5 of font, I can request its removal from unstable and re-upload old
>> > version to unstable and then upload this new version to experimental.
>> 
>> There is no such thing as requesting removal. you need to upload it with
>> a higher version number, but with the old contents. Something like
>> 5.0.10+really4.7.0-1.
>> 
>> Or maybe not. I will try if I can work things out with the new version,
>> so expect a few patches.
>> 
>> For now I'm reopening this bug (which was not really fixed by your -3
>> upload), and let's see what I can get.
>
> So here it is:
> https://salsa.debian.org/fonts-team/fonts-font-awesome/merge_requests/1
>
> This merge request fixes usage of v5, and add a backwards compatibility
> layer for the v4 when used with CSS (which was the only option in v4
> AFAICT). It also adds autopkgtest to automatically test that the needed
> files are in the right places both for v5 and for v4.

Thanks for this!. I've merged this and pushed new version to unstable.

>
> LESS and SCSS are not handled.

Let's see if any one is really using them, if so we will get bug report.

Thanks and Warm Regards,

Vasudev

--



Bug#899311: libmapnik3.0: not installable

2018-05-22 Thread Bas Couwenberg

Control: severity -1 important

On 2018-05-22 16:32, Vincent Lefevre wrote:

 libboost-regex1.62.0 : Breaks: libmapnik3.0 (< 3.0.20+ds-1+b2) but
3.0.20+ds-1+b1 is to be installed


This is a known issue, see:

 https://bugs.debian.org/898369

mapnik will be rebuilt for the upcoming gdal transition which will 
resolve this issue.


If you are not willing to wait for that, you can rebuild mapnik yourself 
with the new boost.


Kind Regards,

Bas



Processed: Re: Bug#899311: libmapnik3.0: not installable

2018-05-22 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 important
Bug #899311 [libmapnik3.0] libmapnik3.0: not installable
Severity set to 'important' from 'grave'

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



Bug#899282: marked as done (libbsd0: bsd-mailx segfaults)

2018-05-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 May 2018 14:53:45 +
with message-id 
and subject line Bug#899282: fixed in libbsd 0.9.1-1
has caused the Debian Bug report #899282,
regarding libbsd0: bsd-mailx segfaults
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.)


-- 
899282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899282
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libbsd0
Version: 0.9.0-1
Severity: serious

Today I have received a mail from the daily cron job, and to my
surprise /usr/bin/mail (pointing to bsd-mailx) crashed when it accessed
it.  Downgrading libbsd0 to version 0.8.7-1.1 fixed that, here is a
backtrace:

,
| % gdb =mail
| Reading symbols from /usr/bin/mail...Reading symbols from 
/usr/lib/debug/.build-id/27/8239e9ab527ec872a29337b01bb283253cfebe.debug...done.
| done.
| (gdb) run
| Starting program: /usr/bin/mail 
| [Thread debugging using libthread_db enabled]
| Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
| Mail version 8.1.2 01/15/2001.  Type ? for help.
| "/var/mail/sven": 1 message 1 new
| 
| Program received signal SIGSEGV, Segmentation fault.
| __strlen_sse2_bsf () at ../sysdeps/i386/i686/multiarch/strlen-sse2-bsf.S:50
| 50../sysdeps/i386/i686/multiarch/strlen-sse2-bsf.S: Datei oder 
Verzeichnis nicht gefunden.
| (gdb) bt full
| #0  __strlen_sse2_bsf () at 
../sysdeps/i386/i686/multiarch/strlen-sse2-bsf.S:50
| No locals.
| #1  0xf7f9bae9 in istrsenvisxl (mbdstp=mbdstp@entry=0x3080, 
dlen=dlen@entry=0x3084, 
| mbsrc=mbsrc@entry=0x2000 , 
flags=96, mbextra=0xf7f9d9be "", 
| cerr_ptr=0x0) at vis.c:583
| No locals.
| #2  0xf7f9be2c in strnvis (mbdst=, dlen=, 
| mbsrc=0x2000 , flags=96) 
at vis.c:707
| No locals.
| #3  0x56558ea8 in printhead (mesg=1) at cmd1.c:229
| mp = 0x5657a1c0
| headline = "From root@localhost.localdomain  Tue May 22 08:25:32 
2018", '\000' 
| subjline = 0x5657cdd8 "Anacron job 'cron.daily' on turtle"
| dispc = 
| visname = '\000' , 
"\300-WV\300-WV\030Q\377\377\202\364UV\035\242\377\377\030Q\377\377", '\000' 
, 
"\034Q\377\377\035\242\377\377\000\000\000\000\000\000\000\000\220q\377\377root@localhost.localdomain",
 '\000' ...
| vissub = '\000' , 
"\v{X\000\000\000\000\000\000\000\000\351\363UV\300-WV\374\241\377\377:\000\000\000\001\000\000\000\213\365UV\374\241\377\377Pq\377\377\\q\377\377\000\000\000\000\\q\377\377\000\000\000\000wq\377\377root@localhost.localdoma"...
| pbuf = "root@localhost.localdomain\000Tue May 22 08:25:32 
2018\000@\240WV\006\000\000\000\300\241WV\000\000\000\000\240\241WV\024\000\000\000K/\341\367\300-WV@\240WV\006\000\000\000\300\241WV\302\065VV@\240WV\024\000\000\000\024\000\000\000*\342UV\247\065VV\300-WV\024\000\000\000\225\342UV@\240WV\300\241WV\024\000\000\000\300-WV\000\000\000\000\001\000\000\000LRWV@nWV\350\221\377\377\024\000\000\000\211\341UV\300-WV\000\000\000\000\001\000\000\000\001\000\000\000\034\350UV@\240WV"...
| fmtline = '\000' , 
"e\035\342\367H\036\342\367W\027\342\367L\261\377\377\254\262\377\377\205\062\342\367L\261\377\377\254\262\377\377\253\302\377\377\000\v{X\354\261\377\377L\261\377\377[h\337\367\000\060\370\367\354\261\377\377L\261\377\377\224\262\377\377-=\353\367L\261\377\377^\202VV\224\262\377\377\254\262\377\377\000\000\000\000^\202VV\377\017\000\000\254\262\377\377",
 '\000' , 
"\001\200\255\373\254\262\377\377\254\262\377\377\254\262\377\377\254\262\377\377\276\262\377\377\253\302\377\377\254\262\377\377\253\302\377\377\200=\370\367"...
| fmt = 
| hl = {l_from = 0x90ac "root@localhost.localdomain", l_tty = 0x0, 
|   l_date = 0x90c7 "Tue May 22 08:25:32 2018"}
| name = 0x5657a720 "root@localhost.localdomain"
| to = 0x5657cdfc "root@localhost.localdomain"
| from = 0x5657a720 "root@localhost.localdomain"
| np = 
| ap = 
| #4  0x565590a3 in headers (v=0xd2c4) at cmd1.c:88
| msgvec = 0xd2c4
| n = 
| mesg = 1
| flag = 1
| size = 60
| mp = 0x5657a1c0
| act = {__sigaction_handler = {sa_handler = 0x56558ba0 , 
sa_sigaction = 0x56558ba0 }, sa_mask = {
| __val = {0 }}, sa_flags = 268435456, 
sa_restorer = 0xf7e20b00 }
| oact = {__sigaction_handler = {sa_handler = 0x0, sa_sigaction = 0x0}, 
sa_mask = {__val = {0, 0, 3, 4158230517, 
|   4160623906, 4294955568, 4294955232, 4294955092, 4158502609, 
4160737344, 1, 268435456, 1448506508, 
|   1448507604, 0, 0, 0, 0, 

Bug#899311: libmapnik3.0: not installable

2018-05-22 Thread Vincent Lefevre
Package: libmapnik3.0
Version: 3.0.20+ds-1
Severity: grave
Justification: renders package unusable

libmapnik3.0 is not installable:

# apt install libmapnik3.0
[...]
The following packages have unmet dependencies:
 libmapnik3.0 : Depends: libboost-regex1.62.0 but it is not going to be 
installed
E: Unable to correct problems, you have held broken packages.
# apt install libmapnik3.0 libboost-regex1.62.0
[...]
The following packages have unmet dependencies:
 libboost-regex1.62.0 : Breaks: libmapnik3.0 (< 3.0.20+ds-1+b2) but 
3.0.20+ds-1+b1 is to be installed
E: Unable to correct problems, you have held broken packages.

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

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

Versions of packages libmapnik3.0 depends on:
ii  fonts-dejavu   2.37-1
pn  gdal-abi-2-1-2 
pn  gdal-abi-2-2-3 
ii  libboost-filesystem1.62.0  1.62.0+dfsg-5.1
pn  libboost-regex1.62.0   
ii  libboost-system1.62.0  1.62.0+dfsg-5.1
ii  libc6  2.27-3
ii  libcairo2  1.14.10-1
ii  libfreetype6   2.6.3-3.2
ii  libgcc11:8.1.0-3
pn  libgdal20  
ii  libharfbuzz0b  1.4.2-1
ii  libicu57   57.1-9
ii  libicu60   60.2-6
ii  libjpeg62-turbo1:1.5.2-2+b1
ii  libpng16-161.6.34-1
ii  libpq5 10.4-2
pn  libproj12  
pn  libproj13  
ii  libsqlite3-0   3.23.1-1
ii  libstdc++6 8.1.0-3
ii  libtiff5   4.0.9-5
ii  libwebp6   0.6.1-2
ii  libxml22.9.4+dfsg1-6.1+b1
ii  zlib1g 1:1.2.11.dfsg-1

libmapnik3.0 recommends no packages.

Versions of packages libmapnik3.0 suggests:
pn  postgis  



Bug#896224: python-pyrax: pyrax fails to import

2018-05-22 Thread Sascha Girrulat
Hi,

it's the same error like #882095.

The support of non keystore authentication were removed since
python-novaclient 7.0.0.[1]

I will take a look if it makes sense to patch python-pyrax another time.

Cheers
Sascha

[1]
https://git.openstack.org/cgit/openstack/python-novaclient/commit/?id=daa9bdc82335b37b33d21264a770e10ee452f22c



signature.asc
Description: OpenPGP digital signature


Processed (with 1 error): python-pyrax: pyrax fails to import

2018-05-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> merge 882095 896224
Bug #882095 [src:python-pyrax] python-pyrax FTBFS: test failures
Unable to merge bugs because:
package of #896224 is 'python-pyrax' not 'src:python-pyrax'
Failed to merge 882095: Did not alter merged bugs.

>
End of message, stopping processing here.

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



Bug#899307: ruby-sequel-pg: All SELECT ::Dataset methods fails with FrozenError

2018-05-22 Thread Andrey Nikitin
Package: ruby-sequel-pg
Version: 1.6.16-1+b2
Severity: grave
Justification: renders package unusable

All SELECT methods like all,first,each,... fails with FrozenError.

Example:
irb(main):007:0> DB
=> #"postgres", :database=>"xxx", 
:user=>"xxx", :password=>"xxx", :host=>"127.0.0.1"}>
irb(main):008:0> DB[:events].first
Traceback (most recent call last):
   16: from /usr/lib/ruby/vendor_ruby/sequel/dataset/actions.rb:688:in 
`single_record'
   15: from /usr/lib/ruby/vendor_ruby/sequel/dataset/actions.rb:700:in 
`single_record!'
   14: from /usr/lib/ruby/vendor_ruby/sequel/dataset/actions.rb:947:in 
`with_sql_first'
   13: from /usr/lib/ruby/vendor_ruby/sequel/dataset/actions.rb:939:in 
`with_sql_each'
   12: from /usr/lib/ruby/vendor_ruby/sequel/adapters/postgres.rb:569:in 
`fetch_rows'
   11: from /usr/lib/ruby/vendor_ruby/sequel/dataset/actions.rb:1085:in 
`execute'
   10: from /usr/lib/ruby/vendor_ruby/sequel/adapters/postgres.rb:273:in 
`execute'
9: from /usr/lib/ruby/vendor_ruby/sequel/database/connecting.rb:269:in 
`synchronize'
8: from 
/usr/lib/ruby/vendor_ruby/sequel/connection_pool/threaded.rb:91:in `hold'
7: from /usr/lib/ruby/vendor_ruby/sequel/adapters/postgres.rb:273:in 
`block in execute'
6: from /usr/lib/ruby/vendor_ruby/sequel/adapters/postgres.rb:477:in 
`check_database_errors'
5: from /usr/lib/ruby/vendor_ruby/sequel/adapters/postgres.rb:273:in 
`block (2 levels) in execute'
4: from /usr/lib/ruby/vendor_ruby/sequel/adapters/postgres.rb:455:in 
`_execute'
3: from /usr/lib/ruby/vendor_ruby/sequel/adapters/postgres.rb:135:in 
`execute'
2: from /usr/lib/ruby/vendor_ruby/sequel/adapters/postgres.rb:569:in 
`block in fetch_rows'
1: from /usr/lib/ruby/vendor_ruby/sequel/adapters/postgres.rb:569:in 
`yield_hash_rows'
FrozenError (can't modify frozen Sequel::Postgres::Dataset)

But
irb(main):017:0> DB[:events].delete
=> 0

P.S.
  * With mysql2 apapter it is ok.
  * In Debian 9 Stretch, too, everything is fine, both mysql2 and postgres.


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

Kernel: Linux 4.16.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), 
LANGUAGE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ruby-sequel-pg depends on:
ii  libc62.27-3
ii  libgmp10 2:6.1.2+dfsg-3
ii  libpq5   10.3-2
ii  libruby2.5   2.5.1-1+b1
ii  ruby 1:2.5.1
ii  ruby-pg  0.19.0-2+b1
ii  ruby-sequel  5.6.0-1

ruby-sequel-pg recommends no packages.

ruby-sequel-pg suggests no packages.



Bug#899282: libbsd0: bsd-mailx segfaults

2018-05-22 Thread Guillem Jover
Hi!

On Tue, 2018-05-22 at 08:50:19 +0200, Sven Joachim wrote:
> Package: libbsd0
> Version: 0.9.0-1
> Severity: serious

> Today I have received a mail from the daily cron job, and to my
> surprise /usr/bin/mail (pointing to bsd-mailx) crashed when it accessed
> it.  Downgrading libbsd0 to version 0.8.7-1.1 fixed that, here is a
> backtrace:

Thanks for the backtrace!

> ,
> | % gdb =mail
[…]
> | #1  0xf7f9bae9 in istrsenvisxl (mbdstp=mbdstp@entry=0x3080, 
> dlen=dlen@entry=0x3084, 
> | mbsrc=mbsrc@entry=0x2000  0x2000>, flags=96, mbextra=0xf7f9d9be "", 
> | cerr_ptr=0x0) at vis.c:583
> | No locals.
> | #2  0xf7f9be2c in strnvis (mbdst=, dlen=, 
> | mbsrc=0x2000 , flags=96) 
> at vis.c:707
> | No locals.
[…]
> `

> Please clone/reassign to bsd-mailx if necessary, I haven't investigated
> the issue more closely.

And ugh, the NetBSD vis functions had a different signature for strnvis()
and strnunvis() WRT the pre-existing FreeBSD implementations. :( And I
didn't notice when importing them. I'll quickly revert those signatures
for now, and probably provide the alternative NetBSD via different symbol
versions in 0.9.2 or so.

Thanks,
Guillem



Bug#899304: bareos-storage will not start after upgrade to 16.2.6-4

2018-05-22 Thread Soren Stoutner
Package: bareos-storage
Version: 16.2.6-4
Severity: grave
Justification: renders package unusable

After upgrading from 16.2.6-3 to 16.2.6-4 in Debian testing bareos-storage no 
longer starts.

service bareos-sd status
● bareos-storage.service - Bareos Storage Daemon service
   Loaded: loaded (/lib/systemd/system/bareos-storage.service; enabled; vendor 
preset: enabled)
   Active: activating (start) since Tue 2018-05-22 03:36:03 MST; 1min 22s ago
 Docs: man:bareos-sd(8)
  Process: 1993 ExecStart=/usr/sbin/bareos-sd (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 4476)
   Memory: 168.0K
   CGroup: /system.slice/bareos-storage.service

May 22 03:36:03 backup systemd[1]: Starting Bareos Storage Daemon service...
May 22 03:36:03 backup systemd[1]: bareos-storage.service: Can't open PID file 
/var/lib/bareos/bareos-sd.9103.pid (yet?) after start: No such file or directory

I am not able to find any other error message that provides an indiation of why 
it will not start.  Bareos-filedaemon starts just fine.  Bareos-dir initially 
didn't start because the upgrade added a second director, but I was able to fix 
that by removing the config file that was added by the upgrade.

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

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

Versions of packages bareos-storage depends on:
ii  adduser3.117
ii  bareos-common  16.2.6-4
ii  debconf [debconf-2.0]  1.5.66
ii  libc6  2.27-3
ii  libcap21:2.25-1.2
ii  libgcc11:8.1.0-3
ii  libgnutls303.5.18-1
ii  libjansson42.11-1
ii  liblzo2-2  2.10-0.1
ii  libstdc++6 8.1.0-3
ii  libwrap0   7.6.q-27
ii  lsb-base   9.20170808
ii  lsof   4.89+dfsg-0.1
ii  zlib1g 1:1.2.11.dfsg-1

bareos-storage recommends no packages.

bareos-storage suggests no packages.

-- no debconf information


Bug#887924: marked as done (slurm-drmaa FTBFS with slurm-llnl 17.11.2-1)

2018-05-22 Thread Debian Bug Tracking System
Your message dated Tue, 22 May 2018 11:13:02 +
with message-id 
and subject line Bug#887924: fixed in slurm-llnl 17.11.6-1
has caused the Debian Bug report #887924,
regarding slurm-drmaa FTBFS with slurm-llnl 17.11.2-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.)


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

https://buildd.debian.org/status/package.php?p=slurm-drmaa=sid

...
configure: checking for SLURM
checking for SLURM compile flags... -I/usr/include/slurm/
checking for SLURM library dir... /usr/lib/libslurm.so
checking for usable SLURM libraries/headers... *** The SLURM test program 
failed to link or run. See the file config.log
*** for the exact error that occured.
no
configure: error: 
SLURM libraries/headers not found;
add --with-slurm-inc and --with-slurm-lib with appropriate locations.
debian/rules:10: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 1
--- End Message ---
--- Begin Message ---
Source: slurm-llnl
Source-Version: 17.11.6-1

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

Debian distribution maintenance software
pp.
Gennaro Oliva  (supplier of updated slurm-llnl 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, 22 May 2018 11:43:27 +0200
Source: slurm-llnl
Binary: slurm-wlm slurm-client slurmd slurmctld libslurmdb32 libslurm32 libpmi0 
libpmi2-0 libslurm-dev libslurmdb-dev libpmi0-dev libpmi2-0-dev slurm-wlm-doc 
slurm-wlm-basic-plugins slurm-wlm-basic-plugins-dev sview slurmdbd 
libslurm-perl libslurmdb-perl slurm-wlm-torque libpam-slurm slurm-wlm-emulator 
slurm-client-emulator
Architecture: source amd64 all
Version: 17.11.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian HPC Team 
Changed-By: Gennaro Oliva 
Description:
 libpam-slurm - PAM module to authenticate using the SLURM resource manager
 libpmi0- SLURM PMI library implementation
 libpmi0-dev - SLURM PMI library implementation development files
 libpmi2-0  - SLURM PMI2 library implementation
 libpmi2-0-dev - SLURM PMI2 library implementation development files
 libslurm-dev - SLURM development files
 libslurm-perl - Perl API for SLURM
 libslurm32 - Runtime library files for SLURM
 libslurmdb-dev - SLURM DataBase Daemon development files
 libslurmdb-perl - Perl API for the SLURM database
 libslurmdb32 - Runtime library files for the SLURM DataBase Daemon
 slurm-client - SLURM client side commands
 slurm-client-emulator - SLURM client side commands for the emulator
 slurm-wlm  - Simple Linux Utility for Resource Management
 slurm-wlm-basic-plugins - SLURM basic plugins
 slurm-wlm-basic-plugins-dev - SLURM basic plugins development files
 slurm-wlm-doc - SLURM documentation
 slurm-wlm-emulator - SLURM emulator
 slurm-wlm-torque - Torque compatibility wrappers for SLURM
 slurmctld  - SLURM central management daemon
 slurmd - SLURM compute node daemon
 slurmdbd   - Secure enterprise-wide interface to a database for SLURM
 sview  - GUI to view and modify SLURM state
Closes: 887924
Changes:
 slurm-llnl (17.11.6-1) unstable; urgency=medium
 .
   * New upstream release
   * Update Vcs info with the new salsa.d.o git repo
   * Change Maintainer to HPC Team
   * Add Gennaro Oliva as Uploader
   * Bump standard version to 4.1.4 (no changes)
   * Rename the header files directory to slurm (Closes: #887924)
Checksums-Sha1:
 afdca8a9ed307ed8707f1311a90f6051eb6ab374 3631 slurm-llnl_17.11.6-1.dsc
 6760c1e6d46ad57b9f4e65597aae11695f30f0cf 8556613 slurm-llnl_17.11.6.orig.tar.gz
 2c772318ef75677121bec24630713b72500fabdc 128900 
slurm-llnl_17.11.6-1.debian.tar.xz
 7d1bad8c3589f8bc63223d30fc48bf298c872628 28440 libpam-slurm_17.11.6-1_amd64.deb
 f669d87f47646e60d37524eb23063baaee1af6ec 21940 

Bug#899004: gnome-shell: crash on attempt to lock

2018-05-22 Thread Simon McVittie
On Tue, 22 May 2018 at 11:18:04 +0200, Josep M. Perez wrote:
> So, I opened dconf-editor and saw that for some reason
> /org/gnome/shell/disable-extension-version-validation was active, and that
> was the default value.

That is correct. By default extensions don't need to declare compatibility
with specific GNOME Shell versions since 3.21.92 (in earlier versions, the
Shell interfaces that extensions use changed more frequently).

If that option had any effect, it would be to disable some of your
extensions. Extensions that say they are compatible with Shell 3.28 should
never be affected by it. gpaste and "removable drive menu" seem to both
be from packages that are updated in sync with the rest of GNOME 3.28,
so I would expect that they declare compatibility with Shell 3.28 and are
unaffected by extension version validation.

> Last week, it seemed that disabling the "gpaste" extension solved it. However,
> today I updated, rebooted, and it seems that now that it still happens until I
> disable the "removable drive menu" extension.
...
> I have set it to false, emptied the contents of
> /org/gnome/shell/enabled-extensions, and enabled only gpaste and "removable
> drive menu" through the "tweaks" application. After this, I can lock the
> screen with no trouble.

That sounds like it might be an intermittent bug that doesn't necessarily
depend on the enabled state of those extensions, unfortunately.

> ii  gnome-shell-extensions 3.28.1-1   
> all  Extensions to extend functionality of GNOME Shell

FYI, this is the package containing the "removable drive menu" extension.

smcv



Bug#896353: Bug fixed in Git

2018-05-22 Thread Andreas Tille
Control: tags -1 pending

Hi Ghislain,

I intended to fix this (low hanging fruit ;-) ) bug but when I noticed
that you are carrying an explicit *-dbg package I was wondering whether
this is needed.  I would remove it in favour of the automatically
created one - but may be you have your reasons for doing this.

BTW, I noticed you have specified "sign-tags = True" but there is no
keyid specified.  I've never used this and I simply sneaked in the new
upstream tag by removing "sign-tags = True" temporarily.  Sorry for the
hack - I hope it is acceptable.

Please note: I have *not* build the new version at my side - so you
might expect issues from the new version.  My changes were basically
making the test suite detecting the reported bug and fixing it.

Kind regards

  Andreas.

-- 
http://fam-tille.de



Processed: Bug fixed in Git

2018-05-22 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 pending
Bug #896353 [python3-ltfatpy] python3-ltfatpy: ltfatpy fails to import
Added tag(s) pending.

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



Bug#899004: gnome-shell: crash on attempt to lock

2018-05-22 Thread Josep M. Perez

Hi,

Sorry for the late response.

On 18/05/18 20:15, Simon McVittie wrote:

Control: tags -1 + moreinfo

On Fri, 18 May 2018 at 15:21:57 +0200, Josep M. Perez wrote:

gnome-shell crashes when I press meta+L to lock the session. After the third
failed attempt, it crashes and also suspends the computer.

How reproducible is this? If you reboot your computer and try repeatedly
locking your screen, does the same thing happen again?
Yes, it happens even if I reboot. This started happening when I went 
from 2.26 to 2.28. Since the crash is related to JS, I started to 
disable extensions. Last week, it seemed that disabling the "gpaste" 
extension solved it. However, today I updated, rebooted, and it seems 
that now that it still happens until I disable the "removable drive 
menu" extension.


So, I opened dconf-editor and saw that for some reason 
/org/gnome/shell/disable-extension-version-validation was active, and 
that was the default value. I have set it to false, emptied the contents 
of /org/gnome/shell/enabled-extensions, and enabled only gpaste and 
"removable drive menu" through the "tweaks" application. After this, I 
can lock the screen with no trouble.


Since activating and deactivating extensions makes the problem go away, 
I will keep you posted about whether this is finally stable.



Is there anything that looks relevant in the systemd journal or syslog
at around the time of the crash?

Not really. It only happens when I attempt to lock the screen.

Did you previously run a version of gnome-shell that did not have this bug?
If you did, what packages did you upgrade around the time it started
happening? (/var/log/apt/history.log* might be useful)

Do you have any GNOME Shell extensions enabled?

I notice that the backtrace you provided involves libnm, the NetworkManager
client library. Is there anything unusual about your networking that might
explain why you see this crash when other people don't?
I have an ethernet connection, a wifi connection and an OpenVPN bridge 
using the tap interface.

I uploaded new versions of gnome-shell, mutter and gjs earlier today
(gnome-shell 3.28.2, mutter 3.28.2 and gjs 1.52.3-2). Please could you
try with those when they become available, and report back with whether
this bug is still visible in those versions?

Yes. The list of versions are:

ii  chrome-gnome-shell 10-1    
all  GNOME Shell extensions integration for web browsers
ii  gnome-shell 3.28.2-1    amd64    
graphical shell for the GNOME desktop
ii  gnome-shell-common 3.28.2-1    
all  common files for the GNOME graphical shell
ii  gnome-shell-dbgsym 3.28.2-1    
amd64    debug symbols for gnome-shell
ii  gnome-shell-extension-appindicator 
22-1    all 
AppIndicator/KStatusNotifierItem support for GNOME Shell
ii  gnome-shell-extension-autohidetopbar 
20171126-2  all  GNOME shell 
automatic topbar hider
ii  gnome-shell-extension-dash-to-panel 
13-1    all  combines the dash 
and the GNOME main panel into a single panel
ii  gnome-shell-extension-dashtodock 
63-1    all  dash-to-dock 
extension for GNOME shell
ii  gnome-shell-extension-disconnect-wifi 
17-2    all  disconnect wifi 
extension for GNOME shell
ii  gnome-shell-extension-hide-activities 
0.00~git20131024.1.6574986-1    all  GNOME shell 
extension that hides the activities button
ii  gnome-shell-extension-impatience 
0.4.5-3 all  speed up the 
gnome-shell animation speed
ii  gnome-shell-extension-move-clock 
1.01-1  all  move clock 
extension for GNOME shell
ii  gnome-shell-extension-multi-monitors 
0.00~git20171014.1.df5d6e4-1    all  Better support for 
additional monitors in GNOME shell
ii  gnome-shell-extension-pixelsaver 
1.10+git20161217-49f47bf-1  all  pixel saver 
extension for GNOME shell
ii  gnome-shell-extension-redshift 
3.20.1-2    all  redshift extension 
for GNOME Shell
ii  gnome-shell-extension-remove-dropdown-arrows 
9-1 all  removes drop down 
arrows from panel on GNOME shell
ii  gnome-shell-extension-shortcuts 
1.1.1-1 all  Creates a shortcuts 
help pop-up in GNOME Shell
ii  gnome-shell-extension-show-ip 
8-3 all  Shows the current 
private or public IP address
ii  gnome-shell-extension-suspend-button 
0~git20171025-2 all  Gnome-shell 
extension to modify the suspend/shutdown buttons
ii  gnome-shell-extension-system-monitor 
35-1    all  

Bug#887924: slurm-drmaa FTBFS with slurm-llnl 17.11.2-1

2018-05-22 Thread Gennaro Oliva
Hi Dominique, Steve and Adrian,

On Mon, Apr 16, 2018 at 04:34:54PM -0400, Dominique Belhachemi wrote:
> The bug is also in Debian's slurm-llnl package. The location of the header
> files is not consistent anymore.

thank you for looking into this issue; the forthcoming release of
slurm-llnl will fix it.

Best regards
-- 
Gennaro Oliva



Bug#899243: [PKG-Openstack-devel] Bug#899243: Needs porting to later tornado

2018-05-22 Thread Thomas Goirand
On 05/21/2018 03:35 PM, Enrico Zini wrote:
> Package: python3-sockjs-tornado
> Version: 1.0.3-1
> Severity: serious
> 
> Hello,
> 
> in recent tornado versions, PeriodicCallback lost the io_loop argument:
> http://www.tornadoweb.org/en/stable/ioloop.html#tornado.ioloop.PeriodicCallback
> but sockjs.tornado is still trying to use of it:
> 
 import sockjs.tornado
 sockjs.tornado.SockJSRouter(sockjs.tornado.SockJSConnection)
> Traceback (most recent call last):
>   File "", line 1, in 
>   File "/usr/lib/python3/dist-packages/sockjs/tornado/router.py", line 111, 
> in __init__
> self.io_loop)
> TypeError: __init__() takes 3 positional arguments but 4 were given
> 
> Because of this, sockjs.tornado does not work in current Debian Testing.
> 
> 
> Enrico

Hi Enrico,

I used to maintain sockjs-tornado for OpenStack, but it's not needed for
it anymore. So if you'd like to take over the maintenance of this
package, for example within the DMPT, please do so, and feel free to
take over this package. Otherwise, if nobody cares about it, I probably
will be forced to ask for its removal from Debian.

Cheers,

Thomas Goirand (zigo)



Bug#899282: libbsd0: bsd-mailx segfaults

2018-05-22 Thread Sven Joachim
Package: libbsd0
Version: 0.9.0-1
Severity: serious

Today I have received a mail from the daily cron job, and to my
surprise /usr/bin/mail (pointing to bsd-mailx) crashed when it accessed
it.  Downgrading libbsd0 to version 0.8.7-1.1 fixed that, here is a
backtrace:

,
| % gdb =mail
| Reading symbols from /usr/bin/mail...Reading symbols from 
/usr/lib/debug/.build-id/27/8239e9ab527ec872a29337b01bb283253cfebe.debug...done.
| done.
| (gdb) run
| Starting program: /usr/bin/mail 
| [Thread debugging using libthread_db enabled]
| Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
| Mail version 8.1.2 01/15/2001.  Type ? for help.
| "/var/mail/sven": 1 message 1 new
| 
| Program received signal SIGSEGV, Segmentation fault.
| __strlen_sse2_bsf () at ../sysdeps/i386/i686/multiarch/strlen-sse2-bsf.S:50
| 50../sysdeps/i386/i686/multiarch/strlen-sse2-bsf.S: Datei oder 
Verzeichnis nicht gefunden.
| (gdb) bt full
| #0  __strlen_sse2_bsf () at 
../sysdeps/i386/i686/multiarch/strlen-sse2-bsf.S:50
| No locals.
| #1  0xf7f9bae9 in istrsenvisxl (mbdstp=mbdstp@entry=0x3080, 
dlen=dlen@entry=0x3084, 
| mbsrc=mbsrc@entry=0x2000 , 
flags=96, mbextra=0xf7f9d9be "", 
| cerr_ptr=0x0) at vis.c:583
| No locals.
| #2  0xf7f9be2c in strnvis (mbdst=, dlen=, 
| mbsrc=0x2000 , flags=96) 
at vis.c:707
| No locals.
| #3  0x56558ea8 in printhead (mesg=1) at cmd1.c:229
| mp = 0x5657a1c0
| headline = "From root@localhost.localdomain  Tue May 22 08:25:32 
2018", '\000' 
| subjline = 0x5657cdd8 "Anacron job 'cron.daily' on turtle"
| dispc = 
| visname = '\000' , 
"\300-WV\300-WV\030Q\377\377\202\364UV\035\242\377\377\030Q\377\377", '\000' 
, 
"\034Q\377\377\035\242\377\377\000\000\000\000\000\000\000\000\220q\377\377root@localhost.localdomain",
 '\000' ...
| vissub = '\000' , 
"\v{X\000\000\000\000\000\000\000\000\351\363UV\300-WV\374\241\377\377:\000\000\000\001\000\000\000\213\365UV\374\241\377\377Pq\377\377\\q\377\377\000\000\000\000\\q\377\377\000\000\000\000wq\377\377root@localhost.localdoma"...
| pbuf = "root@localhost.localdomain\000Tue May 22 08:25:32 
2018\000@\240WV\006\000\000\000\300\241WV\000\000\000\000\240\241WV\024\000\000\000K/\341\367\300-WV@\240WV\006\000\000\000\300\241WV\302\065VV@\240WV\024\000\000\000\024\000\000\000*\342UV\247\065VV\300-WV\024\000\000\000\225\342UV@\240WV\300\241WV\024\000\000\000\300-WV\000\000\000\000\001\000\000\000LRWV@nWV\350\221\377\377\024\000\000\000\211\341UV\300-WV\000\000\000\000\001\000\000\000\001\000\000\000\034\350UV@\240WV"...
| fmtline = '\000' , 
"e\035\342\367H\036\342\367W\027\342\367L\261\377\377\254\262\377\377\205\062\342\367L\261\377\377\254\262\377\377\253\302\377\377\000\v{X\354\261\377\377L\261\377\377[h\337\367\000\060\370\367\354\261\377\377L\261\377\377\224\262\377\377-=\353\367L\261\377\377^\202VV\224\262\377\377\254\262\377\377\000\000\000\000^\202VV\377\017\000\000\254\262\377\377",
 '\000' , 
"\001\200\255\373\254\262\377\377\254\262\377\377\254\262\377\377\254\262\377\377\276\262\377\377\253\302\377\377\254\262\377\377\253\302\377\377\200=\370\367"...
| fmt = 
| hl = {l_from = 0x90ac "root@localhost.localdomain", l_tty = 0x0, 
|   l_date = 0x90c7 "Tue May 22 08:25:32 2018"}
| name = 0x5657a720 "root@localhost.localdomain"
| to = 0x5657cdfc "root@localhost.localdomain"
| from = 0x5657a720 "root@localhost.localdomain"
| np = 
| ap = 
| #4  0x565590a3 in headers (v=0xd2c4) at cmd1.c:88
| msgvec = 0xd2c4
| n = 
| mesg = 1
| flag = 1
| size = 60
| mp = 0x5657a1c0
| act = {__sigaction_handler = {sa_handler = 0x56558ba0 , 
sa_sigaction = 0x56558ba0 }, sa_mask = {
| __val = {0 }}, sa_flags = 268435456, 
sa_restorer = 0xf7e20b00 }
| oact = {__sigaction_handler = {sa_handler = 0x0, sa_sigaction = 0x0}, 
sa_mask = {__val = {0, 0, 3, 4158230517, 
|   4160623906, 4294955568, 4294955232, 4294955092, 4158502609, 
4160737344, 1, 268435456, 1448506508, 
|   1448507604, 0, 0, 0, 0, 0, 1448506489, 1448553920, 4294955716, 
0, 1448507604, 1448506620, 1448507604, 0, 0, 
|   0, 0, 0, 1448506601}}, sa_flags = 0, sa_restorer = 0x0}
| oset = {__val = {2, 0, 199, 294, 4, 0, 1990304, 60, 5, 0, 
1990368, 4160239576, 176, 0, 0, 4160239576, 16, 10, 
| 1448579088, 32768, 32768, 4158418805, 4159255269, 40, 0, 
4158787097, 0, 1448582144, 8, 4160237568, 
| 4158783371, 1448594868}}
| #5  0x56560ca6 in announce () at lex.c:621
| vec = {1, 0}
| mdot = 
| #6  0x56557631 in main (argc=, argv=) at 
main.c:303
| i = 
| to = 
| cc = 
| bcc = 
| smopts = 0x0
| fromaddr = 
| subject = 
| replyto = 0x0
| header = 
| ef = 
| cmd = 
| nosrc = 
| rc = 
| (gdb) 

Bug#899280: [libx86emu1] Missing library

2018-05-22 Thread Peje Nilsson
Package: libx86emu1
Version: 1.14-1
Severity: serious

--- Please enter the report below this line. ---
The package is missing its library.
Looking at snapshot.debian.org the last package to actually contain the
library is 1.11-2

Manually downloading the archive and unpacking and looking at the
directory tree i see a softlink pointing to it self.

> wget
http://ftp.ie.debian.org/debian/pool/main/libx/libx86emu/libx86emu1_1.14-1_amd64.deb
--2018-05-22 07:52:50-- 
http://ftp.ie.debian.org/debian/pool/main/libx/libx86emu/libx86emu1_1.14-1_amd64.deb
Resolving ftp.ie.debian.org (ftp.ie.debian.org)... 130.89.148.12,
2001:67c:2564:a119::148:12
Connecting to ftp.ie.debian.org (ftp.ie.debian.org)|130.89.148.12|:80...
connected.
HTTP request sent, awaiting response... 200 OK
Length: 3824 (3.7K) [application/x-debian-package]
Saving to: ‘libx86emu1_1.14-1_amd64.deb’

libx86emu1_1.14-1_amd64.deb   
100%[=>]   3.73K 
--.-KB/s    in 0s 

2018-05-22 07:52:50 (839 MB/s) - ‘libx86emu1_1.14-1_amd64.deb’ saved
[3824/3824]

> ar x libx86emu1_1.14-1_amd64.deb
> tar xf data.tar.xz
> ls -lR usr
usr:
total 8
drwxr-xr-x 3 peje peje 4096 maj 19 15:20 lib
drwxr-xr-x 3 peje peje 4096 maj 19 15:20 share

usr/lib:
total 4
drwxr-xr-x 2 peje peje 4096 maj 22 07:53 x86_64-linux-gnu

usr/lib/x86_64-linux-gnu:
total 0
lrwxrwxrwx 1 peje peje 13 maj 19 15:20 libx86emu.so. -> libx86emu.so.   
            <---

usr/share:
total 4
drwxr-xr-x 3 peje peje 4096 maj 19 15:20 doc

usr/share/doc:
total 4
drwxr-xr-x 2 peje peje 4096 maj 19 15:20 libx86emu1

usr/share/doc/libx86emu1:
total 12
-rw-r--r-- 1 peje peje  852 maj 19 15:20 changelog.Debian.gz
-rw-r--r-- 1 peje peje  854 maj 19 15:20 changelog.gz
-rw-r--r-- 1 peje peje 1591 maj 19 15:20 copyright




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

Debian Release: buster/sid
500 unstable repo.skype.com
500 unstable ftp.se.debian.org
500 unstable deb-multimedia.org
500 testing ftp.se.debian.org
500 testing deb-multimedia.org
500 stable silk.apana.org.au
500 stable security.debian.org
500 stable repository.spotify.com
500 stable packages.microsoft.com
500 stable ftp.se.debian.org
500 stable dl.google.com
500 stable deb.obspy.org
500 sid linux.dropbox.com
500 precise ppa.launchpad.net
500 oldstable packages.x2go.org
1 experimental ftp.se.debian.org

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.

-- 
Peje Nilsson
===
Swedish Institute of Space Physics, Teknikhuset, SE-901 87 Umeå, SWEDEN
Web: www.umea.irf.se,   Phone: +46-(0)980-79018,E-mail: p...@irf.se



Bug#896772: pypolicyd-spf: missing build dependency on python3-distutils

2018-05-22 Thread Scott Kitterman
The next upstream release will use setuptools, so this problem will go away 
then.

Scott K

On Tue, 24 Apr 2018 11:57:36 +0300 Adrian Bunk  wrote:
> Source: pypolicyd-spf
> Version: 2.0.2-1
> Severity: serious
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pypolicyd-spf.html
> 
> ...
> dh clean --with quilt,python3
>debian/rules override_dh_auto_clean
> make[1]: Entering directory '/build/1st/pypolicyd-spf-2.0.2'
> python3 /build/1st/pypolicyd-spf-2.0.2/setup.py clean
> Traceback (most recent call last):
>   File "/build/1st/pypolicyd-spf-2.0.2/setup.py", line 1, in 
> from distutils.core import setup
> ModuleNotFoundError: No module named 'distutils.core'
> make[1]: *** [debian/rules:17: override_dh_auto_clean] Error 1
> 
> 
> Due to
> 
> python3.6 (3.6.5~rc1-2) unstable; urgency=medium
> 
>   * python3.6: Drop dependency on python3-distutils.
> ...
>  -- Matthias Klose   Tue, 20 Mar 2018 14:29:58 +0800
> 
>