Bug#884418: marked as done (2to3: fails to upgrade from 'testing' - trying to overwrite /usr/bin/2to3)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2017 07:53:17 +
with message-id 
and subject line Bug#884418: fixed in python3-defaults 3.6.4~rc1-2
has caused the Debian Bug report #884418,
regarding 2to3: fails to upgrade from 'testing' - trying to overwrite 
/usr/bin/2to3
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.)


-- 
884418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884418
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: 2to3
Version: 3.6.4~rc1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package 2to3.
  Preparing to unpack .../2to3_3.6.4~rc1-1_all.deb ...
  Unpacking 2to3 (3.6.4~rc1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/2to3_3.6.4~rc1-1_all.deb (--unpack):
   trying to overwrite '/usr/bin/2to3', which is also in package python 2.7.14-3
  Errors were encountered while processing:
   /var/cache/apt/archives/2to3_3.6.4~rc1-1_all.deb


cheers,

Andreas


python=2.7.14-3_2to3=3.6.4~rc1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python3-defaults
Source-Version: 3.6.4~rc1-2

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated python3-defaults 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, 15 Dec 2017 08:24:00 +0100
Source: python3-defaults
Binary: python3 python3-venv python3-minimal python3-examples python3-dev 
libpython3-dev libpython3-stdlib idle idle3 python3-doc python3-dbg 
libpython3-dbg python3-all python3-all-dev python3-all-dbg libpython3-all-dev 
libpython3-all-dbg 2to3
Architecture: source
Version: 3.6.4~rc1-2
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Matthias Klose 
Description:
 2to3   - 2to3 binary using python3
 idle   - IDE for Python using Tkinter (default version)
 idle3  - IDE for Python using Tkinter (transitional package)
 libpython3-all-dbg - package depending on all supported Python 3 debugging 
packages
 libpython3-all-dev - package depending on all supported Python 3 development 
packages
 libpython3-dbg - debug build of the Python 3 Interpreter (version 3.6)
 libpython3-dev - header files and a static library for Python (default)
 libpython3-stdlib - interactive high-level object-oriented language (default 
python3
 python3- interactive high-level object-oriented language (default python3
 python3-all - package depending on all supported Python 3 runtime versions
 python3-all-dbg - package depending on all supported Python 3 debugging 
packages
 python3-all-dev - package depending on all supported Python 3 development 
packages
 python3-dbg - debug build of the Python 3 Interpreter (version 3.6)
 python3-dev - header files and a static library for Python (default)
 python3-doc - documentation for the high-level object-oriented language Python
 python3-examples - examples for the Python language (default version)
 python3-minimal - minimal subset of the Python language (default python3 
version)
 python3-venv - pyvenv-3 binary for python3 (default python3 version)
Closes: 884418
Changes:
 python3-defaults (3.6.4~rc1-2) unstable; urgency=medium
 .
   * 2to3: Fix breaks/replaces relation with python. Closes: #884418.
Checksums-Sha1:
 a5ad61b0fef2ec611f0a13a5dce5cd5db4b538bd 2890 python3-defaults_3.6.4~rc1-2.dsc
 53511ba1e910b440669f669b7055777471897059 131388 
python3-defaults_3.6.4~rc1-2.tar.gz
 

Bug#884414: marked as done (python3-tk: file conflict with libpython3.[67]-testsuite: /usr/lib/python3.[67]/tkinter/test/README)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2017 07:53:24 +
with message-id 
and subject line Bug#884414: fixed in python3-stdlib-extensions 3.6.4~rc1-5
has caused the Debian Bug report #884414,
regarding python3-tk: file conflict with libpython3.[67]-testsuite: 
/usr/lib/python3.[67]/tkinter/test/README
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.)


-- 
884414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884414
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-tk
Version: 3.6.4~rc1-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package python3-tk:amd64.
  Preparing to unpack .../23-python3-tk_3.6.4~rc1-4_amd64.deb ...
  Unpacking python3-tk:amd64 (3.6.4~rc1-4) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-MHZvJC/23-python3-tk_3.6.4~rc1-4_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/python3.7/tkinter/test/README', which is also 
in package libpython3.7-testsuite 3.7.0~a3-2
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-MHZvJC/23-python3-tk_3.6.4~rc1-4_amd64.deb


cheers,

Andreas


libpython3.6-testsuite=3.6.4~rc1-2_python3-tk=3.6.4~rc1-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python3-stdlib-extensions
Source-Version: 3.6.4~rc1-5

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated python3-stdlib-extensions 
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, 15 Dec 2017 08:19:15 +0100
Source: python3-stdlib-extensions
Binary: python3-tk python3-gdbm python3-tk-dbg python3-gdbm-dbg 
python3-distutils
Architecture: source
Version: 3.6.4~rc1-5
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Matthias Klose 
Description:
 python3-distutils - distutils package for Python 3.x
 python3-gdbm - GNU dbm database support for Python 3.x
 python3-gdbm-dbg - GNU dbm database support for Python 3.x (debug extension)
 python3-tk - Tkinter - Writing Tk applications with Python 3.x
 python3-tk-dbg - Tkinter - Writing Tk applications with Python 3.x (debug 
extensio
Closes: 884414
Changes:
 python3-stdlib-extensions (3.6.4~rc1-5) unstable; urgency=medium
 .
   * python3-tk: Don't ship the tkinter test files. Closes: #884414.
Checksums-Sha1:
 8a1179187fc83f1d07bf1b040354cca9387ff36e 2361 
python3-stdlib-extensions_3.6.4~rc1-5.dsc
 9bd54a3077894ee98653b1119d80da274b09eb6b 14500 
python3-stdlib-extensions_3.6.4~rc1-5.debian.tar.xz
 38327a7da3ef6dc59183155976ed235e0f372d2e 8372 
python3-stdlib-extensions_3.6.4~rc1-5_source.buildinfo
Checksums-Sha256:
 ea9789339400cf95eccd4eb6d924c08bbc99ad8b905484c2b315114ceec20dec 2361 
python3-stdlib-extensions_3.6.4~rc1-5.dsc
 1d91ceaff9e713b1fa5a66c467dec6b1bdcd14af1d0cb699da62e7b9133d3050 14500 
python3-stdlib-extensions_3.6.4~rc1-5.debian.tar.xz
 ce48b8737fc160c5174fdfd5676bb52ce663783f4ad8a853ebaaed29960f229e 8372 
python3-stdlib-extensions_3.6.4~rc1-5_source.buildinfo
Files:
 eb2f55923d216d0d6e2e93cb069b8443 2361 python optional 
python3-stdlib-extensions_3.6.4~rc1-5.dsc
 56e9cf56e5b5465ceb6e2877bc16d6e6 14500 python optional 
python3-stdlib-extensions_3.6.4~rc1-5.debian.tar.xz
 1bc91aa2ce84c5cfef380a706d9958ec 8372 python optional 
python3-stdlib-extensions_3.6.4~rc1-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAlozeSsQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9ae1EADNoMIU4XwgtGAMG76MZKlM/bqhNeq1TCDP

Bug#884331: marked as done (python3-defaults: please update, as python3-distutils cannot install now)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2017 08:35:35 +0100
with message-id <58b3390b-5468-d2ff-f22d-c3b389b00...@debian.org>
and subject line Re: Bug#884331: python3-defaults: please update, as 
python3-distutils cannot install now
has caused the Debian Bug report #884331,
regarding python3-defaults: please update, as python3-distutils cannot install 
now
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.)


-- 
884331: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884331
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-defaults
Version: 3.6.3-2
Severity: grave

python3-distutils depends on python3>=3.6.4~rc1,
while the current python3-default is still 3.6.3-2.

Please update the python3-defaults package.


-- 
YunQiang Su
--- End Message ---
--- Begin Message ---
On 14.12.2017 02:16, YunQiang Su wrote:
> Package: python3-defaults
> Version: 3.6.3-2
> Severity: grave
> 
> python3-distutils depends on python3>=3.6.4~rc1,
> while the current python3-default is still 3.6.3-2.
> 
> Please update the python3-defaults package.

fixed in unstable.--- End Message ---

Bug#882141: closed by Scott Kitterman <deb...@kitterman.com> (Re: postfix - systemd generator broken with inet_interfaces)

[Scott Kitterman]

On Friday, December 15, 2017 07:19:55 AM Bastian Blank wrote:
> Control: tags -1 stretch
> 
> On Fri, Dec 15, 2017 at 06:12:11AM +, Debian Bug Tracking System wrote:
> > I've rewritten the postfix-instance-generator to avoid using postmap. 
> > That
> > should solve this problem.  Please let me know if it does (just hit dput,
> > so should be coming to a mirror near you soon).
> 
> The problem also appears in Stretch, marking accordingly.  Please also
> fix it there.

I plan to.  Can you confirm this fixes it for you?

Scott K

Bug#882141: marked as done (postfix - systemd generator broken with inet_interfaces)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2017 06:20:22 +
with message-id 
and subject line Bug#882141: fixed in postfix 3.2.4-1
has caused the Debian Bug report #882141,
regarding postfix - systemd generator broken with inet_interfaces
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.)


-- 
882141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882141
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: postfix
Version: 3.2.3-1
Severity: grave

The systemd generator is completely broken if inet_interfaces is set in
main.cf.  Due to the environment systemd generators are executed in, no
error is reported anywhere.

The generator uses postmulti, which bails out if the ip in
inet_interfaces can't be found:

| # bash -x /lib/systemd/system-generators/postfix-instance-generator
| + set -e
| + WANTDIR=/postfix.service.wants
| + SERVICEFILE=/lib/systemd/system/postfix@.service
| + mkdir -p /postfix.service.wants
| + '[' -f /etc/postfix/main.cf ']'
| ++ awk '{ print $1}'
| ++ postmulti -l -a
| postmulti: fatal: parameter inet_interfaces: no local interface found for 
1.2.3.4
| + exit 0

At the time the generator is executed, only 127.0.0.1 and ::1 is
available.  This means this can never work.

Bastian

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

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

We believe that the bug you reported is fixed in the latest version of
postfix, 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.
Scott Kitterman  (supplier of updated postfix 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, 15 Dec 2017 00:51:49 -0500
Source: postfix
Binary: postfix postfix-ldap postfix-lmdb postfix-cdb postfix-pcre 
postfix-mysql postfix-pgsql postfix-sqlite postfix-doc
Architecture: source amd64 all
Version: 3.2.4-1
Distribution: unstable
Urgency: medium
Maintainer: LaMont Jones 
Changed-By: Scott Kitterman 
Description:
 postfix- High-performance mail transport agent
 postfix-cdb - CDB map support for Postfix
 postfix-doc - Documentation for Postfix
 postfix-ldap - LDAP map support for Postfix
 postfix-lmdb - LMDB map support for Postfix
 postfix-mysql - MySQL map support for Postfix
 postfix-pcre - PCRE map support for Postfix
 postfix-pgsql - PostgreSQL map support for Postfix
 postfix-sqlite - SQLite map support for Postfix
Closes: 882141
Changes:
 postfix (3.2.4-1) unstable; urgency=medium
 .
   [Wietse Venema]
 .
   * 3.2.4
 .
   [Scott Kitterman]
 .
   * Rewrite debian/postfix-instance-generator to avoid use of postmulti
 to fix failures when inet_interfaces != all Closes: #882141
   * Bump standards-version to 4.1.2 without further change
   * Build-depends on debhelper (>= 9.20160709) instead of dh-systemd
Checksums-Sha1:
 eb14385e1f677a291bed2322e7cd272a12921958 2674 postfix_3.2.4-1.dsc
 86de2f38ca0894f42b9473bec6ac061ed6369c9a 4390376 postfix_3.2.4.orig.tar.gz
 09dc1bab92be5fe0b9ff50f62072a3ecf4a1dd55 190852 postfix_3.2.4-1.debian.tar.xz
 5f1f65663b34660b62e0832ac6e628f2c05f16b3 2864 
postfix-cdb-dbgsym_3.2.4-1_amd64.deb
 10e61455f3cebe2a6ede525e00ae8fdc743aec2c 320612 postfix-cdb_3.2.4-1_amd64.deb
 9b5016a749a11040fab96aa7f53a13840b68058b 105748 
postfix-dbgsym_3.2.4-1_amd64.deb
 2b6ed81ecc1e23e8ecbf7f983f77acb7295d1a41 1183096 postfix-doc_3.2.4-1_all.deb
 82c1cd7c29dc41dc9f00595fb01e5baf9256d057 3552 
postfix-ldap-dbgsym_3.2.4-1_amd64.deb
 8946a52f2dffca32cb87a56339801c824ff4ff42 338108 postfix-ldap_3.2.4-1_amd64.deb
 578803bb0fe8f3e204ada57267a2c582c2ee5756 3184 

Processed: Re: Bug#882141 closed by Scott Kitterman <deb...@kitterman.com> (Re: postfix - systemd generator broken with inet_interfaces)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 stretch
Bug #882141 {Done: Scott Kitterman } [src:postfix] 
postfix - systemd generator broken with inet_interfaces
Added tag(s) stretch.

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

Bug#882141: closed by Scott Kitterman <deb...@kitterman.com> (Re: postfix - systemd generator broken with inet_interfaces)

[Bastian Blank]

Control: tags -1 stretch

On Fri, Dec 15, 2017 at 06:12:11AM +, Debian Bug Tracking System wrote:
> I've rewritten the postfix-instance-generator to avoid using postmap.  That 
> should solve this problem.  Please let me know if it does (just hit dput, so 
> should be coming to a mirror near you soon).

The problem also appears in Stretch, marking accordingly.  Please also
fix it there.

Bastian

-- 
Conquest is easy. Control is not.
-- Kirk, "Mirror, Mirror", stardate unknown

Bug#882141: marked as done (postfix - systemd generator broken with inet_interfaces)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2017 01:09:24 -0500
with message-id <2566599.Va8x85HAtx@kitterma-e6430>
and subject line Re: postfix - systemd generator broken with inet_interfaces
has caused the Debian Bug report #882141,
regarding postfix - systemd generator broken with inet_interfaces
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.)


-- 
882141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882141
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: postfix
Version: 3.2.3-1
Severity: grave

The systemd generator is completely broken if inet_interfaces is set in
main.cf.  Due to the environment systemd generators are executed in, no
error is reported anywhere.

The generator uses postmulti, which bails out if the ip in
inet_interfaces can't be found:

| # bash -x /lib/systemd/system-generators/postfix-instance-generator
| + set -e
| + WANTDIR=/postfix.service.wants
| + SERVICEFILE=/lib/systemd/system/postfix@.service
| + mkdir -p /postfix.service.wants
| + '[' -f /etc/postfix/main.cf ']'
| ++ awk '{ print $1}'
| ++ postmulti -l -a
| postmulti: fatal: parameter inet_interfaces: no local interface found for 
1.2.3.4
| + exit 0

At the time the generator is executed, only 127.0.0.1 and ::1 is
available.  This means this can never work.

Bastian

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

Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
On Sun, 19 Nov 2017 16:34:37 +0100 Bastian Blank  wrote:
> Source: postfix
> Version: 3.2.3-1
> Severity: grave
> 
> The systemd generator is completely broken if inet_interfaces is set in
> main.cf.  Due to the environment systemd generators are executed in, no
> error is reported anywhere.
> 
> The generator uses postmulti, which bails out if the ip in
> inet_interfaces can't be found:
> 
> | # bash -x /lib/systemd/system-generators/postfix-instance-generator
> | + set -e
> | + WANTDIR=/postfix.service.wants
> | + SERVICEFILE=/lib/systemd/system/postfix@.service
> | + mkdir -p /postfix.service.wants
> | + '[' -f /etc/postfix/main.cf ']'
> | ++ awk '{ print $1}'
> | ++ postmulti -l -a
> | postmulti: fatal: parameter inet_interfaces: no local interface found for 
1.2.3.4
> | + exit 0
> 
> At the time the generator is executed, only 127.0.0.1 and ::1 is
> available.  This means this can never work.

I've rewritten the postfix-instance-generator to avoid using postmap.  That 
should solve this problem.  Please let me know if it does (just hit dput, so 
should be coming to a mirror near you soon).

Scott K--- End Message ---

Processed: found 878030 in 0.7.1-1.1, found 879909 in 3.99.7-1, reassign 878205 to src:autofs ...

[Debian Bug Tracking System]

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

> found 878030 0.7.1-1.1
Bug #878030 [python3-dotenv] python3-dotenv: /usr/bin/dotenv already provided 
by ruby-dotenv
Marked as found in versions python-dotenv/0.7.1-1.1.
> found 879909 3.99.7-1
Bug #879909 [libgtksourceview-4-dev] libgtksourceview-4-dev: fails to upgrade 
from 'sid' - trying to overwrite /usr/share/glade/catalogs/gtksourceview.xml
Marked as found in versions gtksourceview4/3.99.7-1.
> reassign 878205 src:autofs 5.1.2-1
Bug #878205 {Done: Laurent Bigonville } 
[autofs5-hesiod,autofs5-hesiod,autofs5] please drop transitional packages 
autofs5, autofs5-hesiod and autofs5-ldap
Bug reassigned from package 'autofs5-hesiod,autofs5-hesiod,autofs5' to 
'src:autofs'.
No longer marked as found in versions 5.1.2-1.
No longer marked as fixed in versions autofs/5.1.2-2.
Bug #878205 {Done: Laurent Bigonville } [src:autofs] please 
drop transitional packages autofs5, autofs5-hesiod and autofs5-ldap
Marked as found in versions autofs/5.1.2-1.
> fixed 878205 5.1.2-2
Bug #878205 {Done: Laurent Bigonville } [src:autofs] please 
drop transitional packages autofs5, autofs5-hesiod and autofs5-ldap
Marked as fixed in versions autofs/5.1.2-2.
> tags 878636 + sid buster
Bug #878636 {Done: Debian FTP Masters } 
[kdewallpapers,kde-icons-nuvola] please drop transitional packages 
kdewallpapers and kde-icons-nuvola
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#878144: marked as done (CVE-2017-17439: Remote unauthenticated DoS in Heimdal-KDC 7.1)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2017 03:05:33 +
with message-id 
and subject line Bug#878144: fixed in heimdal 7.5.0+dfsg-1
has caused the Debian Bug report #878144,
regarding CVE-2017-17439: Remote unauthenticated DoS in Heimdal-KDC 7.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.)


-- 
878144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878144
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: heimdal-kdc
Version: 7.1.0+dfsg-13+deb9u1 amd64
Severity: important


We are running heimdal-kdc 7.1.0+dfsg-13+deb9u1 amd64 shipped with
Debian stretch for our Domain and have discovered several crashes in the
past few months. Investigation showed that dmesg contained several logs
about segfaults:

[Fr Jun 23 12:07:17 2017] kdc[14596]: segfault at 18 ip 7f65c02ef5d0
sp 7ffd1d7f7298 error 4 in libasn1.so.8.0.0[7f65c0268000+a7000]
[Di Jun 27 21:37:26 2017] kdc[10087]: segfault at 18 ip 7f65c02ef5d0
sp 7ffd1d7f7298 error 4 in libasn1.so.8.0.0[7f65c0268000+a7000]
[Mo Jul  3 16:18:39 2017] kdc[2656]: segfault at 18 ip 7fa27ec105d0
sp 7ffedcb061f8 error 4 in libasn1.so.8.0.0[7fa27eb89000+a7000]
[So Jul  9 08:55:39 2017] kdc[6092]: segfault at 18 ip 7fa27ec105d0
sp 7ffedcb061f8 error 4 in libasn1.so.8.0.0[7fa27eb89000+a7000]
[Di Jul 11 13:06:14 2017] kdc[28993]: segfault at 18 ip 7fb9dccda5d0
sp 7ffc6e2ee648 error 4 in libasn1.so.8.0.0[7fb9dcc53000+a7000]
[Di Jul 11 23:39:40 2017] kdc[32211]: segfault at 18 ip 7fb9dccda5d0
sp 7ffc6e2ee648 error 4 in libasn1.so.8.0.0[7fb9dcc53000+a7000]
[Sa Jul 15 13:20:17 2017] kdc[6902]: segfault at 18 ip 7fb76d5ef5d0
sp 7ffc22a84078 error 4 in libasn1.so.8.0.0[7fb76d568000+a7000]
[Fr Jul 21 12:17:37 2017] kdc[9219]: segfault at 18 ip 7fdfcbf2b5d0
sp 7ffe9f295128 error 4 in libasn1.so.8.0.0[7fdfcbea4000+a7000]
[So Jul 23 21:10:59 2017] kdc[26977]: segfault at 18 ip 7fdfcbf2b5d0
sp 7ffe9f295128 error 4 in libasn1.so.8.0.0[7fdfcbea4000+a7000]
[So Aug  6 12:06:04 2017] kdc[26494]: segfault at 18 ip 7f342c8d35d0
sp 7fff8ae39088 error 4 in libasn1.so.8.0.0[7f342c84c000+a7000]
[Di Aug 15 15:21:41 2017] kdc[28412]: segfault at 18 ip 7f4780b605d0
sp 7ffd63250328 error 4 in libasn1.so.8.0.0[7f4780ad9000+a7000]
[Mi Aug 16 08:46:13 2017] kdc[5166]: segfault at 18 ip 7f4780b605d0
sp 7ffd63250328 error 4 in libasn1.so.8.0.0[7f4780ad9000+a7000]
[Di Aug 29 04:01:58 2017] kdc[5268]: segfault at 18 ip 7f31fdd065d0
sp 7ffd8392c748 error 4 in libasn1.so.8.0.0[7f31fdc7f000+a7000]
[Fr Sep  1 16:56:57 2017] kdc[13396]: segfault at 18 ip 7f31fdd065d0
sp 7ffd8392c748 error 4 in libasn1.so.8.0.0[7f31fdc7f000+a7000]
[Mo Sep 11 20:10:45 2017] kdc[16093]: segfault at 18 ip 7f8a096715d0
sp 7ffd48ba4b28 error 4 in libasn1.so.8.0.0[7f8a095ea000+a7000]
[Di Sep 12 13:46:17 2017] kdc[24683]: segfault at 18 ip 7f8a096715d0
sp 7ffd48ba4b28 error 4 in libasn1.so.8.0.0[7f8a095ea000+a7000]

The heimdal-kdc log gave us additional information:

lofar log # zgrep "AS-REQ malformed client name" heimdal-kdc.log*
heimdal-kdc.log:2017-09-11T20:10:46 AS-REQ malformed client name from
IPv4:80.82.77.139
heimdal-kdc.log:2017-09-12T13:46:18 AS-REQ malformed client name from
IPv4:185.100.87.246
heimdal-kdc.log.2.gz:2017-08-29T04:01:59 AS-REQ malformed client name
from IPv4:71.6.135.131
heimdal-kdc.log.2.gz:2017-09-01T16:56:58 AS-REQ malformed client name
from IPv4:34.208.25.133
heimdal-kdc.log.4.gz:2017-08-15T15:21:41 AS-REQ malformed client name
from IPv4:96.126.127.61
heimdal-kdc.log.4.gz:2017-08-16T08:46:13 AS-REQ malformed client name
from IPv4:71.6.158.166
heimdal-kdc.log.5.gz:2017-08-06T12:06:05 AS-REQ malformed client name
from IPv4:71.6.167.142

The KDC was directly reachable over the Internet - those IPs do not
belong to us but seemed to send packets crashing our master or our slave
(we observed the same there).
While waiting to capture one of those packets and reproduce the issues,
my colleague Thomas Kittel located the part of the code responsible for
the crash:

  * RIP in libasn1.so.0 (relativ) 0x875d0.
  * "der_length_visible_string@@HEIMDAL_ASN1_1.0"
  
   875d0:   48 8b 3fmovrdi,QWORD PTR [rdi]
   875d3:   e9 e8 83 f9 ff  jmp1f9c0 
   875d8:   0f 1f 84 00 00 00 00nopDWORD PTR [rax+rax*1+0x0]
   875df:   00
  

  * Source:
https://github.com/heimdal/heimdal/blob/master/lib/asn1/der_length.c
  size_t
  

Bug#882463: Wheezy update of xrdp?

[Dominik George]

Hi,

> Would you like to take care of this yourself?

Not really. Go ahead ☺.

-nik

-- 
PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17  FD26 B79A 3C16 A0C4 F296

Dominik George · Hundeshagenstr. 26 · 53225 Bonn
Phone: +49 228 92934581 · https://www.dominik-george.de/

Teckids e.V. · FrOSCon e.V.
Fellowship of the FSFE · Piratenpartei Deutschland
Opencaching Deutschland e.V. · Debian Maintainer

LPIC-3 Linux Enterprise Professional (Security)


signature.asc
Description: PGP signature

Bug#882463: marked as done (xrdp: CVE-2017-16927: Buffer-overflow in scp_v0s_accept function in session manager)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2017 01:49:23 +
with message-id 
and subject line Bug#882463: fixed in xrdp 0.9.4-2
has caused the Debian Bug report #882463,
regarding xrdp: CVE-2017-16927: Buffer-overflow in scp_v0s_accept function in 
session manager
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.)


-- 
882463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882463
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xrdp
Version: 0.9.1-1
Severity: grave
Tags: security upstream
Forwarded: https://github.com/neutrinolabs/xrdp/pull/958

Hi,

the following vulnerability was published for xrdp.

CVE-2017-16927[0]:
| The scp_v0s_accept function in sesman/libscp/libscp_v0.c in the session
| manager in xrdp through 0.9.4 uses an untrusted integer as a write
| length, which allows local users to cause a denial of service (buffer
| overflow and application crash) or possibly have unspecified other
| impact via a crafted input stream.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-16927
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16927
[1] https://groups.google.com/forum/#!topic/xrdp-devel/PmVfMuy_xBA
[2] https://github.com/neutrinolabs/xrdp/pull/958

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: xrdp
Source-Version: 0.9.4-2

We believe that the bug you reported is fixed in the latest version of
xrdp, 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.
Dominik George  (supplier of updated xrdp 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, 15 Dec 2017 02:10:18 +0100
Source: xrdp
Binary: xrdp xorgxrdp
Architecture: source amd64
Version: 0.9.4-2
Distribution: unstable
Urgency: high
Maintainer: Debian Remote Maintainers 
Changed-By: Dominik George 
Description:
 xorgxrdp   - Remote Desktop Protocol (RDP) modules for X.org
 xrdp   - Remote Desktop Protocol (RDP) server
Closes: 882463
Changes:
 xrdp (0.9.4-2) unstable; urgency=high
 .
   [ Dominik George ]
   * Fix typo in previous changelog.
   * Fix CVE-2017-16927. (Closes: #882463)
   * Bump Standards-Version.
 + No changes needed.
 .
   [ Thorsten Glaser ]
   * Place missing log_end_msg in init script.
   * Run libpainter/bootstrap as well.
   * Re-enable SIMD on any-i386.
   * Cherry-pick missing parts from experimental branch.
   * Fix another typo in previous changelog.
Checksums-Sha1:
 b1cde0d1c99637a015bdfa3c50b9daa8c3f22e05 2668 xrdp_0.9.4-2.dsc
 7b16f45d926cab36ce369dbf953ae3b29533ea60 24692 xrdp_0.9.4-2.debian.tar.xz
 a1bf0e0e3f72234142cb77e482e1e10d69ce225b 907692 
xorgxrdp-dbgsym_0.9.4-2_amd64.deb
 a54bbfc36a76eb711b9fabf507f82fad2981c694 83748 xorgxrdp_0.9.4-2_amd64.deb
 f6cac895b9efbf3507dbb08029503694d33bd390 689996 xrdp-dbgsym_0.9.4-2_amd64.deb
 febe0a93bc08b9e59fed91296c8b783609e11068 10562 xrdp_0.9.4-2_amd64.buildinfo
 e6e08824b2cd25dd4c23130a2d8842177b1d0cfe 423532 xrdp_0.9.4-2_amd64.deb
Checksums-Sha256:
 84cbe65db64b63a829baf96a9d138bb3c4ce8e3464a20304e67993bc3000c1e1 2668 
xrdp_0.9.4-2.dsc
 af5bf78ac6fce04db69c9d59eb079f1c71877dc93dc727e672c73132158725fb 24692 
xrdp_0.9.4-2.debian.tar.xz
 e8792d001062b3f96eafc8182e82139c35d18496a2fa3d1babb1fdfa262b0a69 907692 
xorgxrdp-dbgsym_0.9.4-2_amd64.deb
 dd72b1736275148a308e18631d4ea4d80c0c8ed1a9937c4447198e97468122ac 83748 
xorgxrdp_0.9.4-2_amd64.deb
 460cbc5ec1c333b0e6d6f0adf57c7dfc7729b5da0f2864faebd4920d845d09eb 689996 
xrdp-dbgsym_0.9.4-2_amd64.deb
 7a9a9d5488c44e31ea44d4324e8f5f3b403b67514205b727424192db5277e793 10562 
xrdp_0.9.4-2_amd64.buildinfo
 20ad910e145adc7969b08ac4a84e7f3c4a98c37b0421782e907c15d6c19a3f56 423532 
xrdp_0.9.4-2_amd64.deb
Files:
 fba6ff6b7ef2456ebb4ad3446711574f 2668 net optional xrdp_0.9.4-2.dsc
 

Bug#884053: marked as done (python-lib389: missing build dependencies)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2017 01:35:52 +
with message-id 
and subject line Bug#884298: Removed package(s) from unstable
has caused the Debian Bug report #884053,
regarding python-lib389: missing build dependencies
to be marked as done.

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

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


-- 
884053: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884053
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-lib389
Version: 1.0.2-3
Severity: serious
Tags: buster sid

Some recent change in unstable (new python-setuptools?)
makes python-lib389 FTBFS:

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

...
==
ERROR: lib389.tests.test_module_proxy (unittest.loader.ModuleImportFailure)
--
ImportError: Failed to import test module: lib389.tests.test_module_proxy
Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/loader.py", line 254, in _find_tests
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/unittest/loader.py", line 232, in 
_get_module_from_name
__import__(name)
  File "/build/1st/python-lib389-1.0.2/lib389/__init__.py", line 67, in 
from lib389._entry import Entry
  File "/build/1st/python-lib389-1.0.2/lib389/_entry.py", line 10, in 
import six
ImportError: No module named six


--
Ran 1 test in 0.000s

FAILED (errors=1)
Test failed: 
error: Test failed: 
debian/rules:9: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1


Reproduced locally, and seems to require build dependencies on
python-six, python-pyasn1 and python-pyasn1-modules.
--- End Message ---
--- Begin Message ---
Version: 1.0.2-3+rm

Dear submitter,

as the package python-lib389 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/884298

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#875017: marked as done ([libkmahjongg] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2017 01:30:52 +
with message-id 
and subject line Bug#883998: Removed package(s) from unstable
has caused the Debian Bug report #875017,
regarding [libkmahjongg] Future Qt4 removal from 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.)


-- 
875017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875017
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libkmahjongg
Version: 4:14.12.3-3
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Version: 4:14.12.3-3+rm

Dear submitter,

as the package libkmahjongg has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/883998

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#866980: marked as done (biomaj-watcher: fails to upgrade from 'jessie': Exception in thread "main" java.lang.UnsupportedClassVersionError: WatcherConfigurator : Unsupported major.minor version 52.

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2017 01:33:07 +
with message-id 
and subject line Bug#884180: Removed package(s) from unstable
has caused the Debian Bug report #866980,
regarding biomaj-watcher: fails to upgrade from 'jessie': Exception in thread 
"main" java.lang.UnsupportedClassVersionError: WatcherConfigurator : 
Unsupported major.minor version 52.0
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.)


-- 
866980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866980
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: biomaj-watcher
Version: 1.2.2-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'jessie'.
It installed fine in 'jessie', then the upgrade to 'stretch' fails.

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

  Setting up biomaj-watcher (1.2.2-4) ...
  Exception in thread "main" java.lang.UnsupportedClassVersionError: 
WatcherConfigurator : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:803)
at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)
  dpkg: error processing package biomaj-watcher (--configure):
   subprocess installed post-installation script returned error exit status 1


This was observed while doing two-stage upgrade tests:
  apt-get upgrade && apt-get dist-upgrade
during the apt-get upgrade phase.
A one-stage upgrade (only apt-get dist-upgrade) works fine.

There is probably an insufficiently versioned Depends (or Breaks) ...
but I have no idea which package could be meant with 
  Unsupported major.minor version 52.0


cheers,

Andreas


biomaj-watcher_1.2.2-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 1.2.2-6+rm

Dear submitter,

as the package biomaj-watcher has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/884180

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#875030: marked as done ([lightdm-kde] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2017 01:29:55 +
with message-id 
and subject line Bug#883714: Removed package(s) from unstable
has caused the Debian Bug report #875030,
regarding [lightdm-kde] Future Qt4 removal from 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.)


-- 
875030: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875030
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lightdm-kde
Version: 0.3.2.2-1
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Version: 0.3.2.2-1+rm

Dear submitter,

as the package lightdm-kde has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/883714

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#845453: marked as done (golang-github-googleapis-proto-client-go: FTBFS: logging.pb.go:216: undefined: grpc.SupportPackageIsVersion3)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2017 01:26:57 +
with message-id 
and subject line Bug#883568: Removed package(s) from unstable
has caused the Debian Bug report #845453,
regarding golang-github-googleapis-proto-client-go: FTBFS: logging.pb.go:216: 
undefined: grpc.SupportPackageIsVersion3
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.)


-- 
845453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845453
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-googleapis-proto-client-go
Version: 0.0~git20160726.0.e5790fe-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

golang-github-googleapis-proto-client-go fails to build from source in 
unstable/amd64:

  […]
 dh_auto_build -O--buildsystem=golang
go install -v -p 1 github.com/googleapis/proto-client-go/api 
github.com/googleapis/proto-client-go/logging/type_ 
github.com/googleapis/proto-client-go/logging/v2 
github.com/googleapis/proto-client-go/rpc
  github.com/golang/protobuf/proto
  github.com/googleapis/proto-client-go/api
  github.com/googleapis/proto-client-go/logging/type_
  github.com/golang/protobuf/ptypes/any
  github.com/golang/protobuf/ptypes/empty
  github.com/golang/protobuf/ptypes/struct
  github.com/golang/protobuf/ptypes/timestamp
  github.com/googleapis/proto-client-go/rpc
  golang.org/x/net/context
  golang.org/x/net/http2/hpack
  golang.org/x/net/idna
  golang.org/x/net/lex/httplex
  golang.org/x/net/http2
  golang.org/x/net/internal/timeseries
  golang.org/x/net/trace
  google.golang.org/grpc/codes
  google.golang.org/grpc/credentials
  google.golang.org/grpc/grpclog
  google.golang.org/grpc/internal
  google.golang.org/grpc/metadata
  google.golang.org/grpc/naming
  google.golang.org/grpc/peer
  google.golang.org/grpc/transport
  google.golang.org/grpc
  github.com/googleapis/proto-client-go/logging/v2
  # github.com/googleapis/proto-client-go/logging/v2
  src/github.com/googleapis/proto-client-go/logging/v2/logging.pb.go:216: 
undefined: grpc.SupportPackageIsVersion3
  
src/github.com/googleapis/proto-client-go/logging/v2/logging_config.pb.go:223: 
undefined: grpc.SupportPackageIsVersion3
  
src/github.com/googleapis/proto-client-go/logging/v2/logging_metrics.pb.go:183: 
undefined: grpc.SupportPackageIsVersion3
  dh_auto_build: go install -v -p 1 github.com/googleapis/proto-client-go/api 
github.com/googleapis/proto-client-go/logging/type_ 
github.com/googleapis/proto-client-go/logging/v2 
github.com/googleapis/proto-client-go/rpc returned exit code 2
  debian/rules:4: recipe for target 'build' failed
  make: *** [build] Error 2

  […]

The full build log is attached.


Regards,

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


golang-github-googleapis-proto-client-go.0.0~git20160726.0.e5790fe-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Version: 0.0~git20160726.0.e5790fe-1+rm

Dear submitter,

as the package golang-github-googleapis-proto-client-go has just been removed 
from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/883568

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Processed: found 882463 in 0.9.4-1

[Debian Bug Tracking System]

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

> found 882463 0.9.4-1
Bug #882463 [src:xrdp] xrdp: CVE-2017-16927: Buffer-overflow in scp_v0s_accept 
function in session manager
Marked as found in versions xrdp/0.9.4-1.
> thanks
Stopping processing here.

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

Bug#882463: marked as pending

[Dominik George]

tag 882463 pending
thanks

Hello,

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

https://anonscm.debian.org/cgit/pkg-remote/xrdp.git/commit/?id=d852069

---
commit d8520695e237c8853380e247e82d22d155c8b7e3
Author: Dominik George 
Date:   Fri Dec 15 02:05:25 2017 +0100

Add patch for CVE-2017-16927.

diff --git a/debian/changelog b/debian/changelog
index ce894b1..b430e2a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+xrdp (0.9.1-9+deb9u2) stretch-security; urgency=high
+
+  * Fix CVE-2017-16927. (Closes: #882463)
+
+ -- Dominik George   Fri, 15 Dec 2017 02:05:40 +0100
+
 xrdp (0.9.1-9+deb9u1) stretch; urgency=medium
 
   * Fix high CPU load on SSL shutdown. (Closes: #876976)

Bug#859554: marked as done (pidgin-openfetion: Please migrate to openssl1.1 in buster)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2017 01:17:27 +
with message-id 
and subject line Bug#882673: Removed package(s) from unstable
has caused the Debian Bug report #859554,
regarding pidgin-openfetion: Please migrate to openssl1.1 in buster
to be marked as done.

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

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


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

Hi,

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

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

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

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


Kurt
--- End Message ---
--- Begin Message ---
Version: 0.3-2+rm

Dear submitter,

as the package pidgin-openfetion has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/882673

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

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

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2017 01:17:52 +
with message-id 
and subject line Bug#882675: Removed package(s) from unstable
has caused the Debian Bug report #859053,
regarding libofetion: Please migrate to openssl1.1 in buster
to be marked as done.

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

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


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

Hi,

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

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

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

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


Kurt
--- End Message ---
--- Begin Message ---
Version: 2.2.2-1.1+rm

Dear submitter,

as the package libofetion has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/882675

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Processed: Bug#882463 marked as pending

[Debian Bug Tracking System]

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

> tag 882463 pending
Bug #882463 [src:xrdp] xrdp: CVE-2017-16927: Buffer-overflow in scp_v0s_accept 
function in session manager
Ignoring request to alter tags of bug #882463 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#882463: marked as pending

[Dominik George]

tag 882463 pending
thanks

Hello,

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

https://anonscm.debian.org/cgit/pkg-remote/xrdp.git/commit/?id=690b1ae

---
commit 690b1aea2b21dde4d82c154d0f132c5348bd24e9
Author: Dominik George 
Date:   Fri Dec 15 02:10:06 2017 +0100

Add patch for CVE-2017-16927.

diff --git a/debian/changelog b/debian/changelog
index a6c0ade..355b3db 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -2,6 +2,7 @@ xrdp (0.9.4-2) UNRELEASED; urgency=medium
 
   [ Dominik George ]
   * Fix typo in previous changelog.
+  * Fix CVE-2017-16927. (Closes: #882463)
 
   [ Thorsten Glaser ]
   * Place missing log_end_msg in init script.
@@ -10,7 +11,7 @@ xrdp (0.9.4-2) UNRELEASED; urgency=medium
   * Cherry-pick missing parts from experimental branch.
   * Fix another typo in previous changelog.
 
- -- Thorsten Glaser   Tue, 10 Oct 2017 20:21:09 +0200
+ -- Dominik George   Fri, 15 Dec 2017 02:10:18 +0100
 
 xrdp (0.9.4-1) unstable; urgency=medium
 

Bug#873195: marked as done (zoomer: please switch to ffmpeg)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2017 01:11:26 +
with message-id 
and subject line Bug#882031: Removed package(s) from unstable
has caused the Debian Bug report #873195,
regarding zoomer: please switch to ffmpeg
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.)


-- 
873195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873195
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libav-tools
Version: 7:3.2.5-1
Severity: normal
user: qa.debian@packages.debian.org
usertags: transitional

Please drop transitional package libav-tools for Buster, as it has been 
released with Stretch.

Thanks for maintaining ffmpeg!


-- 
cheers,
Holger


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 0.1-1.1+rm

Dear submitter,

as the package zoomer has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/882031

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#881763: marked as done (pynmea2: duplicate package with python-nmea2)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2017 01:10:08 +
with message-id 
and subject line Bug#881907: Removed package(s) from unstable
has caused the Debian Bug report #881763,
regarding pynmea2: duplicate package with python-nmea2
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.)


-- 
881763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881763
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pynmea2
Version: 1.9.0-1
Severity: serious
Justification: Policy 4.13, 7.4


Hi!
I'm afraid that your package ships the very same code as python-nmea2 (other
than yours being outdated: while 1.9.0 sat in NEW, 1.12.0 was released
upstream and the other package is already updated).  Both are packagings of
https://github.com/Knio/pynmea2 .

src: pynmea2
* python3-pynmea2
src: python-nmea2
* python-nmea2
* python3-nmea2

This violates Policy 4.13 (sort of: this is no mere convenience copy but a
whole-sale duplicate), and also 7.4 because of undeclared file conflict:

dpkg: error processing archive 
/var/cache/apt/archives/python3-pynmea2_1.9.0-1_all.deb (--unpack):
 trying to overwrite '/usr/lib/python3/dist-packages/pynmea2/__init__.py', 
which is also in package python3-nmea2 1.12.0-1


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

Kernel: Linux 4.14.0+ (SMP w/6 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
Version: 1.9.0-1+rm

Dear submitter,

as the package pynmea2 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/881907

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#873535: marked as done (zoomer: should zoomer be removed?)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2017 01:11:26 +
with message-id 
and subject line Bug#882031: Removed package(s) from unstable
has caused the Debian Bug report #873535,
regarding zoomer: should zoomer be removed?
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.)


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

zoomer has only ever seen one maintainer upload in 2008 and we had to NMU it
while switching from to ffmpeg to libav in 2013. It seems that we now have to
NMU again to switch back from libav to ffmpeg. Since it's evident that zoomer is
unmaintained and also appears to be dead upstream, I think it is time to get it
removed from the archive.

If you agree, please reassign this bug to ftp.debian.org:

Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: zoomer -- RM; unmaintained
Control: severity -1 normal

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 0.1-1.1+rm

Dear submitter,

as the package zoomer has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/882031

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Processed: tagging 884309

[Debian Bug Tracking System]

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

> tags 884309 + pending
Bug #884309 [starpu-examples] starpu-examples: depends indirectly on nonfree 
package libsocl-contrib-1.2-0
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Bug#882463 marked as pending

[Debian Bug Tracking System]

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

> tag 882463 pending
Bug #882463 [src:xrdp] xrdp: CVE-2017-16927: Buffer-overflow in scp_v0s_accept 
function in session manager
Ignoring request to alter tags of bug #882463 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#882463: marked as pending

[Dominik George]

tag 882463 pending
thanks

Hello,

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

https://anonscm.debian.org/cgit/pkg-remote/xrdp.git/commit/?id=180d149

---
commit 180d1495f0729e6afdda2e60c1c0aeaf2bec05b5
Author: Dominik George 
Date:   Fri Dec 15 02:05:25 2017 +0100

Add patch for CVE-2017-16927.

diff --git a/debian/changelog b/debian/changelog
index ce894b1..422df4c 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+xrdp (0.9.1-9+deb9u2) stretch; urgency=medium
+
+  * Fix CVE-2017-16927. (Closes: #882463)
+
+ -- Dominik George   Fri, 15 Dec 2017 02:05:40 +0100
+
 xrdp (0.9.1-9+deb9u1) stretch; urgency=medium
 
   * Fix high CPU load on SSL shutdown. (Closes: #876976)

Processed: Bug#882463 marked as pending

[Debian Bug Tracking System]

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

> tag 882463 pending
Bug #882463 [src:xrdp] xrdp: CVE-2017-16927: Buffer-overflow in scp_v0s_accept 
function in session manager
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#880337: [pkg-php-pear] Bug#880337: php-sabre-vobject-3: diff for NMU version 3.5.2-1.1

[David Prévot]

Hi,

Le 14/12/2017 à 14:48, David Prévot a écrit :
> Le 14/12/2017 à 07:33, Adrian Bunk a écrit :
>> On Wed, Dec 13, 2017 at 12:19:41PM -1000, David Prévot wrote:
>>> Le 13/12/2017 à 09:27, Adrian Bunk a écrit :
>>>
 I've prepared an NMU for php-sabre-vobject-3 (versioned as 3.5.2-1.1)
> […]
>>> Since this package was introduced as an ownCloud dependency (removed
>>> from Debian for a while now), I’d rather see this package removed
[…]
>> My biggest interest is in getting this bug fixed for stable,
>> do you plan to do that or shall I submit a pu request?

By the way, maybe a removal (with its rdeps) from stable would be
acceptable too. Keeping it in Stretch was an oversight of mine in the
first place.

Regards

David



signature.asc
Description: OpenPGP digital signature

Bug#785813: marked as done (gnome-activity-journal: Please update to GStreamer 1.x)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2017 01:03:00 +
with message-id 
and subject line Bug#881585: Removed package(s) from unstable
has caused the Debian Bug report #785813,
regarding gnome-activity-journal: Please update to GStreamer 1.x
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.)


-- 
785813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785813
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-activity-journal
Severity: important
User: sl...@debian.org
Usertags: gstreamer0.10-removal

Hi maintainer,

your package gnome-activity-journal currently still depends on
GStreamer 0.10.

GStreamer 0.10 is no longer maintained and supported by the upstream
project since almost 3 years, and contains many known bugs that are
fixed in the new 1.x release series of GStreamer. Next to many bug
fixes, the new release series also contains many other improvements,
new features and a more streamlined API.

For the next Debian release GStreamer 0.10 is planned to be removed,
and if your package is not updated it might not be included in the
release. Please update your package to use the new version as soon as
possible.

If you need any help with porting or have further questions, please
feel free to also contact me privately.

Best regards, Sebastian

PS: See https://bugs.debian.org/785198 and
https://lists.debian.org/debian-devel/2015/05/msg00335.html for some
further discussion.
--- End Message ---
--- Begin Message ---
Version: 0.8.0-2.1+rm

Dear submitter,

as the package gnome-activity-journal has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/881585

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#790583: marked as done (gnome-activity-journal: depends on python-gnome2 which is deprecated)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2017 01:03:00 +
with message-id 
and subject line Bug#881585: Removed package(s) from unstable
has caused the Debian Bug report #790583,
regarding gnome-activity-journal: depends on python-gnome2 which is deprecated
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.)


-- 
790583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790583
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-activity-journal
Severity: important
Tags: sid stretch
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs python-gnome2 gnome-python

Hi,

gnome-activity-journal depends on python-gnome2, which is long
deprecated and going to be removed from the archive.
gnome-activity-journal should be ported away from it.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Stretch release as we're going to
try to remove python-gnome2 this cycle.

If you have any question don't hesitate to ask.

Emilio

[1] https://wiki.gnome.org/action/show/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/action/show/Projects/PyGObject 
--- End Message ---
--- Begin Message ---
Version: 0.8.0-2.1+rm

Dear submitter,

as the package gnome-activity-journal has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/881585

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

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

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2017 01:03:50 +
with message-id 
and subject line Bug#881693: Removed package(s) from unstable
has caused the Debian Bug report #859546,
regarding owl: Please migrate to openssl1.1 in buster
to be marked as done.

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

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


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

Hi,

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

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

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

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


Kurt
--- End Message ---
--- Begin Message ---
Version: 2.2.2-4.1+rm

Dear submitter,

as the package owl has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/881693

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#879734: marked as done (deprecated upstream; drop-in replacement exists)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2017 01:02:29 +
with message-id 
and subject line Bug#881505: Removed package(s) from unstable
has caused the Debian Bug report #879734,
regarding deprecated upstream; drop-in replacement exists
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.)


-- 
879734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879734
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libemail-sender-transport-smtps-perl
Version: 0.03-1
Severity: serious
Tags: upstream

Email::Sender::Transport::SMTPS is deprecated upstream¹. 
Email::Sender::Transport::SMTP (part of libemail-sender-perl) can work with and 
without SSL/TLS and is a drop-in replacement.

I think we should remove libemail-sender-transport-smtps-perl from Debian.

Popcon:
  inst: 32
  vote: 6
  old: 21
  recent: 5
  no files: 0

DAK:
  coccia:~$ dak rm -n -R -s sid -m 'ROM; deprecated upstream; drop-in 
replacement exists' libemail-sender-transport-smtps-perl
  Will remove the following packages from sid:

  libemail-sender-transport-smtps-perl | 0.03-1 | source, all

  Maintainer: Debian Perl Group 

  --- Reason ---
  ROM; deprecated upstream; drop-in replacement exists
  --

  Checking reverse dependencies...
  No dependency problem found.

Filing a serious bug for now. I plan to request removal in no less than two
weeks time if no one objects.


-- dam
--- End Message ---
--- Begin Message ---
Version: 0.03-1+rm

Dear submitter,

as the package libemail-sender-transport-smtps-perl has just been removed from 
the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/881505

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#879733: marked as done (Deprecated upstream; Email::Sender::Transport::SMTP is a replacement)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2017 00:57:23 +
with message-id 
and subject line Bug#881500: Removed package(s) from unstable
has caused the Debian Bug report #879733,
regarding Deprecated upstream; Email::Sender::Transport::SMTP is a replacement
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.)


-- 
879733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879733
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libemail-sender-transport-smtp-tls-perl
Version: 0.15-1
Severity: serious
Tags: upstream

Email::Sender::Transport::SMTP::TLS is deprecated upstream since 2013. 
Email::Sender::Transport::SMTP (part of libemail-sender-perl) works with and 
without SSL/TLS and is a drop-in replacement.

I think we should remove libemail-sender-transport-smtp-tls-perl from Debian.

Popcon:
 inst: 59
 vote: 18
 old: 39
 recent: 2
 no files: 0

dak:
 coccia:~$ dak rm -n -R -s sid -m 'ROM; deprecated upstream; drop-in 
replacement exists' libemail-sender-transport-smtp-tls-perl
 Will remove the following packages from sid:

 libemail-sender-transport-smtp-tls-perl | 0.15-1 | source, all

 Maintainer: Debian Perl Group 

 --- Reason ---
 ROM; deprecated upstream; drop-in replacement exists
 --

 Checking reverse dependencies...
 No dependency problem found.

Filing a serious bug for now. If no one objects, I'll request removal in no 
less than two weeks time.


-- dam
--- End Message ---
--- Begin Message ---
Version: 0.15-1+rm

Dear submitter,

as the package libemail-sender-transport-smtp-tls-perl has just been removed 
from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/881500

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#883386: [pkg-php-pear] Bug#883386: Bug#883386: php-apigen depends on php-symfony-* (< 3~~) but 3.4.0+dfsg-1 is to be installed

[David Prévot]

Hi,

Le 14/12/2017 à 13:18, Florian Schlichting a écrit :

> Perhaps apigen and friends should have been removed from Debian two
> years ago, as David had suggested. Unless anybody objects, that's
> probably what I'm going to request in a few weeks. Any thoughts?

Still no objections here ;). Thank you for documenting your thoughts and
investigations.

Regards

David



signature.asc
Description: OpenPGP digital signature

Bug#884419: torbrowser-launcher: debian/rules clean does not run dh_clean

[Andreas Beckmann]

Source: torbrowser-launcher
Version: 0.2.8-5
Severity: serious
Justification: Policy 4.9

Hi,

from the attached pbuilder --twice buildlog after the first build has finished:

 dpkg-source --before-build torbrowser-launcher-0.2.8
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
dh clean --with python2 --buildsystem=python_distutils
   dh_auto_clean -O--buildsystem=python_distutils
python setup.py clean -a
running clean
removing 'build/lib.linux-x86_64-2.7' (and everything under it)
'build/bdist.linux-x86_64' does not exist -- can't clean it
removing 'build/scripts-2.7' (and everything under it)
find . -name \*.pyc -exec rm {} \+
   debian/rules override_dh_clean
make[1]: Entering directory '/build/torbrowser-launcher-0.2.8'
rm -rf share/locale/
make[1]: Leaving directory '/build/torbrowser-launcher-0.2.8'
 dpkg-source -b torbrowser-launcher-0.2.8
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: error: unwanted binary file: 
debian/torbrowser-launcher/usr/share/man/man1/torbrowser-launcher.1.gz
dpkg-source: error: unwanted binary file: 
debian/torbrowser-launcher/usr/share/doc/torbrowser-launcher/changelog.Debian.gz
dpkg-source: error: unwanted binary file: 
debian/torbrowser-launcher/usr/share/doc/torbrowser-launcher/changelog.gz
dpkg-source: error: unwanted binary file: 
debian/torbrowser-launcher/usr/share/pixmaps/torbrowser.png
dpkg-source: error: unwanted binary file: 
debian/torbrowser-launcher/usr/share/torbrowser-launcher/modem.ogg
dpkg-source: error: unwanted binary file: 
debian/torbrowser-launcher/usr/share/locale/torbrowser-launcher.mo
dpkg-source: error: unwanted binary file: 
debian/torbrowser-launcher/usr/share/locale/ru/LC_MESSAGES/torbrowser-launcher.mo
dpkg-source: error: unwanted binary file: 
debian/torbrowser-launcher/usr/share/locale/pl/LC_MESSAGES/torbrowser-launcher.mo
dpkg-source: error: unwanted binary file: 
debian/torbrowser-launcher/usr/share/locale/nl/LC_MESSAGES/torbrowser-launcher.mo
dpkg-source: error: unwanted binary file: 
debian/torbrowser-launcher/usr/share/locale/hu/LC_MESSAGES/torbrowser-launcher.mo
dpkg-source: error: unwanted binary file: 
debian/torbrowser-launcher/usr/share/locale/fr/LC_MESSAGES/torbrowser-launcher.mo
dpkg-source: error: unwanted binary file: 
debian/torbrowser-launcher/usr/share/locale/cs/LC_MESSAGES/torbrowser-launcher.mo
dpkg-source: error: detected 12 unwanted binary files (add them in 
debian/source/include-binaries to allow their inclusion).
dpkg-buildpackage: error: dpkg-source -b torbrowser-launcher-0.2.8 subprocess 
returned exit status 29


Without calling dh_clean, all the temporary stuff in debian/ is retained,
but luckily dpkg-source chokes on unwanted binaries, refusing to create
a source package full of binary cruft.

The override_dh_clean target needs to call dh_clean in addition to any
further cleanup it does.


Andreas


torbrowser-launcher_0.2.8-5.log.gz
Description: application/gzip

Bug#882526: marked as done (plexus-classworlds2 FTBFS with debhelper >= 10.9)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2017 00:51:47 +
with message-id 
and subject line Bug#881024: Removed package(s) from unstable
has caused the Debian Bug report #882526,
regarding plexus-classworlds2 FTBFS with debhelper >= 10.9
to be marked as done.

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

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


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

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

...
   dh_install -O--buildsystem=ant
   mh_install -O--buildsystem=ant
dh_link: Requested unknown package plexus-classworlds2-doc via -p/--package, 
expected one of: libplexus-classworlds2-java libplexus-classworlds2-java-doc
dh_link: unknown option or error during option parsing; aborting
debian/rules:11: recipe for target 'binary' failed
make: *** [binary] Error 25
--- End Message ---
--- Begin Message ---
Version: 2.5.2-1+rm

Dear submitter,

as the package plexus-classworlds2 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/881024

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#880337: [pkg-php-pear] Bug#880337: php-sabre-vobject-3: diff for NMU version 3.5.2-1.1

[David Prévot]

Hi,

Le 14/12/2017 à 07:33, Adrian Bunk a écrit :
> On Wed, Dec 13, 2017 at 12:19:41PM -1000, David Prévot wrote:
>> Le 13/12/2017 à 09:27, Adrian Bunk a écrit :
>>
>>> I've prepared an NMU for php-sabre-vobject-3 (versioned as 3.5.2-1.1)
[…]
>> Since this package was introduced as an ownCloud dependency (removed
>> from Debian for a while now), I’d rather see this package removed
[…]
> OK, I've canceled my NMU upload from delayed.
> 
> My biggest interest is in getting this bug fixed for stable,
> do you plan to do that or shall I submit a pu request?

I’m on my way to not have much free time in the coming weeks, so feel
free to handle the pu request. Thanks!

> And the most recent version php-sabre-vobject/experimental
> also seems to need this fix.

It may not be the only thing that need fixing, but there are new
upstream releases that could be useful. CCing Mathieu who has more
interest than I do in this package, and is currently taking over the
maintenance.

Regards

David



signature.asc
Description: OpenPGP digital signature

Bug#882232: marked as done (python-gudev build depends on the removed python-gobject-dev transitional package)

[Debian Bug Tracking System]

Your message dated Fri, 15 Dec 2017 00:47:39 +
with message-id 
and subject line Bug#879032: Removed package(s) from unstable
has caused the Debian Bug report #882232,
regarding python-gudev build depends on the removed python-gobject-dev 
transitional package
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.)


-- 
882232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882232
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-gudev
Version: 147.2-3
Severity: serious
Tags: buster sid

The transitional python-gobject-dev has been removed,
please update the build dependencies.
--- End Message ---
--- Begin Message ---
Version: 147.2-3+rm

Dear submitter,

as the package python-gudev has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/879032

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#884418: 2to3: fails to upgrade from 'testing' - trying to overwrite /usr/bin/2to3

[Andreas Beckmann]

Package: 2to3
Version: 3.6.4~rc1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package 2to3.
  Preparing to unpack .../2to3_3.6.4~rc1-1_all.deb ...
  Unpacking 2to3 (3.6.4~rc1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/2to3_3.6.4~rc1-1_all.deb (--unpack):
   trying to overwrite '/usr/bin/2to3', which is also in package python 2.7.14-3
  Errors were encountered while processing:
   /var/cache/apt/archives/2to3_3.6.4~rc1-1_all.deb


cheers,

Andreas


python=2.7.14-3_2to3=3.6.4~rc1-1.log.gz
Description: application/gzip

Bug#884417: trezor: fails to upgrade from 'testing' - trying to overwrite /usr/bin/trezorctl

[Andreas Beckmann]

Package: trezor
Version: 0.7.16-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package trezor.
  Preparing to unpack .../13-trezor_0.7.16-1_all.deb ...
  Unpacking trezor (0.7.16-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-9MvYHf/13-trezor_0.7.16-1_all.deb (--unpack):
   trying to overwrite '/usr/bin/trezorctl', which is also in package 
python-trezor 0.7.6-1
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-9MvYHf/13-trezor_0.7.16-1_all.deb


cheers,

Andreas


python-trezor=0.7.6-1_trezor=0.7.16-1.log.gz
Description: application/gzip

Bug#884416: osmo-bsc-mgcp: fails to upgrade from 'sid' - trying to overwrite /usr/bin/osmo-bsc_mgcp

[Andreas Beckmann]

Package: osmo-bsc-mgcp
Version: 1.2.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package osmo-bsc-mgcp.
  Preparing to unpack .../7-osmo-bsc-mgcp_1.2.0-1_amd64.deb ...
  Unpacking osmo-bsc-mgcp (1.2.0-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-yWpJNp/7-osmo-bsc-mgcp_1.2.0-1_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/osmo-bsc_mgcp', which is also in package 
osmocom-bsc 0.15.0-3
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-yWpJNp/7-osmo-bsc-mgcp_1.2.0-1_amd64.deb


cheers,

Andreas


osmocom-bsc=0.15.0-3_osmo-bsc-mgcp=1.2.0-1.log.gz
Description: application/gzip

Bug#884415: prelude-lml,prelude-lml-rules: file conflict on /etc/prelude-lml/ruleset/apc-emu.rules

[Andreas Beckmann]

Package: prelude-lml,prelude-lml-rules
Version: 3.1.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package prelude-lml-rules.
  Preparing to unpack .../prelude-lml-rules_3.1.0-1_amd64.deb ...
  Unpacking prelude-lml-rules (3.1.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/prelude-lml-rules_3.1.0-1_amd64.deb (--unpack):
   trying to overwrite '/etc/prelude-lml/ruleset/apc-emu.rules', which is also 
in package prelude-lml 3.1.0-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/prelude-lml-rules_3.1.0-1_amd64.deb


cheers,

Andreas


prelude-lml=3.1.0-1_prelude-lml-rules=3.1.0-1.log.gz
Description: application/gzip

Bug#883938: netinst to a specific source-version?

[Chris Botha]

Hi is there a way to do a netinst to a specific source-version such
as 3.16.48-1.
Thanks in advance.

Bug#884414: python3-tk: file conflict with libpython3.[67]-testsuite: /usr/lib/python3.[67]/tkinter/test/README

[Andreas Beckmann]

Package: python3-tk
Version: 3.6.4~rc1-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package python3-tk:amd64.
  Preparing to unpack .../23-python3-tk_3.6.4~rc1-4_amd64.deb ...
  Unpacking python3-tk:amd64 (3.6.4~rc1-4) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-MHZvJC/23-python3-tk_3.6.4~rc1-4_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/python3.7/tkinter/test/README', which is also 
in package libpython3.7-testsuite 3.7.0~a3-2
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-MHZvJC/23-python3-tk_3.6.4~rc1-4_amd64.deb


cheers,

Andreas


libpython3.6-testsuite=3.6.4~rc1-2_python3-tk=3.6.4~rc1-4.log.gz
Description: application/gzip

Bug#884116: linux-image-4.9.0-4-amd64: screen atrifacts then crash

[Richard James Salts]

Package: src:linux
Version: 4.9.65-3
Followup-For: Bug #884116



-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: 
product_name: 
product_version: 
chassis_vendor: 
chassis_version: 
bios_vendor: Intel Corporation
bios_version: RYBDWi35.86A.0360.2016.1109.0946
board_vendor: Intel Corporation
board_name: NUC5i7RYB
board_version: H73774-101

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Broadwell-U Host Bridge -OPI 
[8086:1604] (rev 09)
Subsystem: Intel Corporation Broadwell-U Host Bridge -OPI [8086:2057]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: bdw_uncore

00:02.0 VGA compatible controller [0300]: Intel Corporation Iris Graphics 6100 
[8086:162b] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Intel Corporation Iris Graphics 6100 [8086:2057]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:03.0 Audio device [0403]: Intel Corporation Broadwell-U Audio Controller 
[8086:160c] (rev 09)
Subsystem: Intel Corporation Broadwell-U Audio Controller [8086:2057]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

00:14.0 USB controller [0c03]: Intel Corporation Wildcat Point-LP USB xHCI 
Controller [8086:9cb1] (rev 03) (prog-if 30 [XHCI])
Subsystem: Intel Corporation Wildcat Point-LP USB xHCI Controller 
[8086:2057]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

00:16.0 Communication controller [0780]: Intel Corporation Wildcat Point-LP MEI 
Controller #1 [8086:9cba] (rev 03)
Subsystem: Intel Corporation Wildcat Point-LP MEI Controller [8086:2057]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: mei_me
Kernel modules: mei_me

00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection (3) 
I218-V [8086:15a3] (rev 03)
Subsystem: Intel Corporation Ethernet Connection (3) I218-V [8086:2057]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: e1000e
Kernel modules: e1000e

00:1b.0 Audio device [0403]: Intel Corporation Wildcat Point-LP High Definition 
Audio Controller [8086:9ca0] (rev 03)
Subsystem: Intel Corporation Wildcat Point-LP High Definition Audio 
Controller [8086:2057]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

00:1c.0 PCI bridge [0604]: Intel Corporation Wildcat Point-LP PCI Express Root 
Port #1 [8086:9c90] (rev e3) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1c.3 PCI bridge [0604]: Intel Corporation Wildcat Point-LP PCI Express Root 
Port #4 [8086:9c96] (rev e3) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1d.0 USB controller [0c03]: Intel Corporation Wildcat Point-LP USB EHCI 
Controller [8086:9ca6] (rev 03) (prog-if 20 [EHCI])
Subsystem: Intel Corporation Wildcat Point-LP USB EHCI Controller 
[8086:2057]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-

Bug#883386: [pkg-php-pear] Bug#883386: php-apigen depends on php-symfony-* (< 3~~) but 3.4.0+dfsg-1 is to be installed

[Florian Schlichting]

Hello php packagers,

On Sun, Dec 03, 2017 at 02:05:10PM +0200, Adrian Bunk wrote:
> Package: php-apigen
> Version: 4.1.2-2
> Severity: serious
> Tags: buster sid
> 
> The following packages have unmet dependencies:
>  php-apigen : Depends: php-symfony-options-resolver (< 3~~) but 3.4.0+dfsg-1 
> is to be installed
>   Depends: php-symfony-console (< 3~~) but 3.4.0+dfsg-1 is to be 
> installed
>   Depends: php-symfony-yaml (< 3~~) but 3.4.0+dfsg-1 is to be 
> installed

I'm thinking about dropping php-apigen and the packages it depends on,
namely php-apigen-theme-default, php-apigen-theme-bootstrap, php-fshl,
php-kdyby-events, php-markdown, php-nette and php-tokenreflection. The
only reverse-(build)-dependencies in Debian are awl and davical, which I
maintain.

When I joined pkg-php-pear to maintain these packages, I didn't know of
any other tools available in Debian that could build API docs for
davical, but I have been experimenting with phpDox and doxygen since and
I think they'll be good enough for my needs.

Apigen on the other hand has been struggling to push out a new release.
After a long quiet period there was frantic activity from a new
maintainer, which resulted in several release candidates being tagged
over the summer. However he has since explained that he burned out,
development is again very slow, and serious issues have surfaced
(crashes, massive performance regression compared to 4.1.2 - see
https://www.tomasvotruba.cz/blog/2017/09/04/how-apigen-survived-its-own-death/
for the whole story). There doesn't appear to be anybody working to
address these issues.

All the while symfony got updated, and apigen 4.1.2 fails to work with
current symfony in obscure ways (exception in eval'd / generated
code)...

Perhaps apigen and friends should have been removed from Debian two
years ago, as David had suggested. Unless anybody objects, that's
probably what I'm going to request in a few weeks. Any thoughts?

Florian

Bug#884409: kio-audiocd failing with "Unknown protocol 'audiocd'".

[Pino Toscano]

severity 884409 important
block 884409 by 874820
thanks

Hi,

In data giovedì 14 dicembre 2017 23:08:30 CET, Hakan Bayindir ha scritto:
> Accessing audio CDs with kio-audiocd package is currently not possible.
> kio-audiocd slave doesn't run, and the CD cannot be read or ripped via 
> dolphin.
> 
> [...]
> 
> kf5.kio.core: couldn't create slave: "klauncher said: Unknown protocol 
> 'audiocd'.\n"

This is because kio-audiocd is still a KIO-Slave for kdelibs 4.x (with
Qt 4), while dolphin is an application based on Frameworks 5.x (with
Qt 5).  Obviously, you cannot use Qt4 plugins in Qt5 applications, and
vice versa.

This will be fixed once kio-audiocd is updated to version >= 17.08;
see also bug #874820.

(BTW: we still ship a dolphin4 package, which is the latest version of
dolphin for kdelibs 4.x; this version is able to use the current
version of kio-audiocd.)

-- 
Pino Toscano

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

Processed: Re: Bug#884409: kio-audiocd failing with "Unknown protocol 'audiocd'".

[Debian Bug Tracking System]

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

> severity 884409 important
Bug #884409 [kio-audiocd] kio-audiocd failing with "Unknown protocol 'audiocd'".
Severity set to 'important' from 'grave'
> block 884409 by 874820
Bug #884409 [kio-audiocd] kio-audiocd failing with "Unknown protocol 'audiocd'".
884409 was not blocked by any bugs.
884409 was not blocking any bugs.
Added blocking bug(s) of 884409: 874820
> thanks
Stopping processing here.

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

Bug#884409: kio-audiocd failing with "Unknown protocol 'audiocd'".

[Hakan Bayindir]

Package: kio-audiocd
Version: 4:16.08.3-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Accessing audio CDs with kio-audiocd package is currently not possible.
kio-audiocd slave doesn't run, and the CD cannot be read or ripped via dolphin.

Reproducing the problem:

1- Install kio-audiocd package.
2- Log-out and log-in.
3- Insert an audio CD to the optical drive, wait for it to be recognized.
4- Open Dolphin.
5- Find your audio CD in left nav-bar, right click, click "open in new tab".
6- A new empty tab opens in dolphin.

Note: If you enabled kio-audiocd debugging in kdebugdialog, you can find the
following line in your ~/.xsession-errors file:

kf5.kio.core: couldn't create slave: "klauncher said: Unknown protocol 
'audiocd'.\n"


Expected results:

1- Install kio-audiocd package.
2- Log-out and log-in.
3- Insert an audio CD to the optical drive, wait for it to be recognized.
4- Open Dolphin.
5- Find your audio CD in left nav-bar, right click, click "open in new tab".
6- Dolphin opens a new tab, optical drive spins up, virtual folders 
   (CDA, wav, FLAC, MP3, etc.) appear in the newly opened tab. Copying any
   folder to hard drive starts on-the-fly ripping of the said audio CD.


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

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

Versions of packages kio-audiocd depends on:
ii  kde-runtime   4:16.08.3-2
ii  libc6 2.25-3
ii  libcdparanoia03.10.2+debian-11.1
ii  libflac8  1.3.2-1
ii  libkcddb4 4:16.08.3-1
ii  libkcompactdisc4  4:16.04.0-2
ii  libkdecore5   4:4.14.36-1
ii  libkdeui5 4:4.14.36-1
ii  libkio5   4:4.14.36-1
ii  libogg0   1.3.2-1+b1
ii  libqtcore44:4.8.7+dfsg-11
ii  libqtgui4 4:4.8.7+dfsg-11
ii  libstdc++67.2.0-17
ii  libvorbis0a   1.3.5-4
ii  libvorbisenc2 1.3.5-4

kio-audiocd recommends no packages.

Versions of packages kio-audiocd suggests:
ii  lame  3.100-2

-- no debconf information

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

[Martin Manns]

I can reproduce this.

The reason is that pyspread uses the cairo component from the package
python-wxgtk3.0
that has been broken.
This bug affects all Cairo based applications that use wxPython (e.g.
the wxPython demo).

Processed: tagging 882894

[Debian Bug Tracking System]

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

> tags 882894 + pending
Bug #882894 [src:awl] awl FTBFS with phpunit 6.4.4-2
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#884407: wslay FTBFS with nettle-dev 3.4-1

[Adrian Bunk]

Source: wslay
Version: 1.0.1~39-g6abacc1-1
Severity: serious

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

...
/build/1st/wslay-1.0.1~39-g6abacc1/examples/echoserv.cc: In function 
'std::__cxx11::string base64(const string&)':
/build/1st/wslay-1.0.1~39-g6abacc1/examples/echoserv.cc:126:83: error: invalid 
conversion from 'uint8_t* {aka unsigned char*}' to 'char*' [-fpermissive]
   base64_encode_raw(dst, src.size(), reinterpret_cast(src.c_str()));

   ^
In file included from 
/build/1st/wslay-1.0.1~39-g6abacc1/examples/echoserv.cc:52:0:
/usr/include/nettle/base64.h:117:1: note:   initializing argument 1 of 'void 
nettle_base64_encode_raw(char*, size_t, const uint8_t*)'
 base64_encode_raw(char *dst, size_t length, const uint8_t *src);
 ^
/build/1st/wslay-1.0.1~39-g6abacc1/examples/testclient.cc: In function 
'std::__cxx11::string base64(const string&)':
/build/1st/wslay-1.0.1~39-g6abacc1/examples/testclient.cc:118:66: error: 
invalid conversion from 'uint8_t* {aka unsigned char*}' to 'char*' 
[-fpermissive]
 reinterpret_cast(src.c_str()));
  ^
In file included from 
/build/1st/wslay-1.0.1~39-g6abacc1/examples/testclient.cc:51:0:
/usr/include/nettle/base64.h:117:1: note:   initializing argument 1 of 'void 
nettle_base64_encode_raw(char*, size_t, const uint8_t*)'
 base64_encode_raw(char *dst, size_t length, const uint8_t *src);
 ^
examples/CMakeFiles/echoserv.dir/build.make:65: recipe for target 
'examples/CMakeFiles/echoserv.dir/echoserv.cc.o' failed
make[4]: *** [examples/CMakeFiles/echoserv.dir/echoserv.cc.o] Error 1

Bug#882894: [DAViCal-devel] Bug#882894: awl FTBFS with phpunit 6.4.4-2

[Florian Schlichting]

On Mon, Nov 27, 2017 at 09:24:58PM +0200, Adrian Bunk wrote:
> Source: awl
> Version: 0.58-1
> Severity: serious
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/awl.html
> 
> ...
>dh_auto_test
>   make -j1 test
> make[1]: Entering directory '/build/1st/awl-0.58'
> # simple php syntax check
> OK (Syntax checked)
> # run phpunit tests
> PATH=/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:./vendor/bin/ phpunit tests/
> PHP Fatal error:  Class 'PHPUnit_Framework_TestCase' not found in 
> /build/1st/awl-0.58/tests/myCalendarTest.php on line 12

this is due to namespacing of classes (PHPUnit\Framework\TestCase)
introduced in phpunit 6; it's possible to use aliasing to satisfy both
old and new phpunit, and I've just pushed a commit to this effect

awl still doesn't build because php-apigen can't be installed; we
could consider moving to doxygen to build the api docs, as I'm not sure
about the future of apigen

Florian

Bug#884405: ucspi-unix FTBFS with libbg-dev 2.03+dfsg-4

[Adrian Bunk]

Source: ucspi-unix
Version: 0.36-4
Severity: serious
Tags: buster sid

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

...
./compile env.c
env.c:4:10: fatal error: sysdeps.h: No such file or directory
 #include 
  ^~~
compilation terminated.
Makefile:38: recipe for target 'env.o' failed
make[1]: *** [env.o] Error 1
make[1]: Leaving directory '/build/1st/ucspi-unix-0.36'
debian/rules:23: recipe for target 'build-stamp' failed
make: *** [build-stamp] Error 2

Bug#884406: golang-google-cloud FTBFS and Debci failure: *MockCloudSpanner does not implement spanner.SpannerServer

[Adrian Bunk]

Source: golang-google-cloud
Version: 0.9.0-2
Severity: serious

https://ci.debian.net/packages/g/golang-google-cloud/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-google-cloud.html

...
# cloud.google.com/go/spanner/internal/testutil
src/cloud.google.com/go/spanner/internal/testutil/mockserver.go:238:30: cannot 
use m (type *MockCloudSpanner) as type spanner.SpannerServer in argument to 
spanner.RegisterSpannerServer:
*MockCloudSpanner does not implement spanner.SpannerServer (missing 
ListSessions method)
...
make[1]: *** [override_dh_auto_build] Error 2

Processed: Re: Bug#832656: runit: breaks users of runit: ln: failed to create symbolic link '/etc/service/bcron-sched': No such file or directory

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #834086 [twoftpd-run] runit: breaks users of runit: ln: failed to create 
symbolic link '/etc/service/bcron-sched': No such file or directory
Severity set to 'important' from 'serious'

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

Bug#834086: Bug#832656: runit: breaks users of runit: ln: failed to create symbolic link '/etc/service/bcron-sched': No such file or directory

[Gianfranco Costamagna]

control: severity -1 important
Hello Andreas,
On Mon, 01 Aug 2016 22:15:18 +0300 Dmitry Bogatov  wrote:
> 
> > I'm not sure, but did you mean to report this bug against bcron package?
> > I fail to understand why runit should have such problem
> 
> Well, it is my bad. runit-2.1.2_4 deserved a transition, but now we have at 
> least following
> uninstallabe packages:
> 
> bcron-run
> twoftpd-run
> tinydns-run
> 
> and rest of -run packages deserve some love, care and debhelper.
> Fixing issue is extremely difficult without converting packages
> to debhelper (since I need dh_runit). I am discussing with
> Gerrit about taking over a least three packages above.
> 

I think this has been fixed a long time ago, but I honestly fail to remember 
how/when...
Can you please raise the severity again in case it is still a trouble?
(I fail to reproduce it, or maybe my pbuilder environment misses some tools)
thanks!

Gianfranco



signature.asc
Description: OpenPGP digital signature

Bug#853398: fcoe-utils: ftbfs with GCC-7

[Juhani Numminen]

On Tue, 31 Jan 2017 09:31:15 + Matthias Klose  wrote:
> Package: src:fcoe-utils
> Version: 1.0.29+git20140505-1
> Severity: normal
> Tags: sid buster
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-7
> ...
> gcc -DPACKAGE_NAME=\"fcoe-utils\" -DPACKAGE_TARNAME=\"fcoe-utils\" 
> -DPACKAGE_VERSION=\"1.0.29\" -DPACKAGE_STRING=\"fcoe-utils\ 1.0.29\" 
> -DPACKAGE_BUGREPORT=\"fcoe-de...@open-fcoe.org\" -DPACKAGE_URL=\"\" 
> -DPACKAGE=\"fcoe-utils\" -DVERSION=\"1.0.29\" -I.  -I./include -I./include 
> -DSYSCONFDIR="\"/etc\"" -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 
> -Wall -Wformat=2 -Werror -Wmissing-prototypes -Wstrict-prototypes -g -O2 
> -fdebug-prefix-map=/<>/fcoe-utils-1.0.29+git20140505=. 
> -fstack-protector-strong -Wformat -Werror=format-security -MT libopenfcoe.o 
> -MD -MP -MF $depbase.Tpo -c -o libopenfcoe.o libopenfcoe.c &&\
> mv -f $depbase.Tpo $depbase.Po
> libopenfcoe.c: In function 'add_fcoe_fcf_device':
> libopenfcoe.c:75:8: error: '%s' directive output may be truncated writing 
> between 0 and 255 bytes into a region of size 0 [-Werror=format-truncation=]
> "%s/%s", ctlr->path, dp->d_name);
> ^~

Fedora has a newer upstream version, but they have a patch related to this:
https://src.fedoraproject.org/rpms/fcoe-utils/blob/master/f/fcoe-utils-ggc7-fmt-truc-err.patch
I have modified it to apply to the Debian package.

However, even after applying the attached patch, the package FTBFS:

fcping.c: In function 'fp_find_hba':
fcping.c:591:9: error: '%s' directive output may be truncated writing up to 255 
bytes into a region of size 61 [-Werror=format-truncation=]
 "fc_%s", port_attrs.OSDeviceName);
 ^~   ~~


Best regards,
Juhani
Description: patch to fix up gcc7 build errors due to Werror=format-truncation
Origin: https://src.fedoraproject.org/rpms/fcoe-utils/blob/master/f/fcoe-utils-ggc7-fmt-truc-err.patch
Bug-Debian: https://bugs.debian.org/853398
Last-Update: 2017-12-14

--- a/fipvlan.c
+++ b/fipvlan.c
@@ -631,8 +631,10 @@
 real_dev->ifname, fcf->vlan, vlan->ifname);
 			return 0;
 		}
-		snprintf(vlan_name, IFNAMSIZ, "%s.%d%s",
-			 real_dev->ifname, fcf->vlan, config.suffix);
+		rc = snprintf(vlan_name, IFNAMSIZ, "%s.%d%s",
+			  real_dev->ifname, fcf->vlan, config.suffix);
+		if (rc >= IFNAMSIZ)
+			return -E2BIG;
 		rc = vlan_create(fcf->ifindex, fcf->vlan, vlan_name);
 		if (rc < 0) {
 			printf("Failed to create VLAN device %s\n\t%s\n",
--- a/libopenfcoe.c
+++ b/libopenfcoe.c
@@ -59,6 +59,7 @@
 {
 	struct fcoe_ctlr_device *ctlr = (struct fcoe_ctlr_device *)arg;
 	struct fcoe_fcf_device *fcf;
+	int rc;
 
 	if (!strstr(dp->d_name, "fcf") ||
 	(!strcmp(dp->d_name, "fcf_dev_loss_tmo")))
@@ -71,8 +72,10 @@
 	memset(fcf, 0, sizeof(struct fcoe_fcf_device));
 
 	/* Save the path */
-	snprintf(fcf->path, sizeof(fcf->path),
-		 "%s/%s", ctlr->path, dp->d_name);
+	rc = snprintf(fcf->path, sizeof(fcf->path),
+		  "%s/%s", ctlr->path, dp->d_name);
+	if (rc >= sizeof(fcf->path))
+		goto fail;
 
 	/* Use the index from the logical enumeration */
 	fcf->index = atoi(dp->d_name + sizeof("fcf_") - 1);
@@ -198,7 +201,9 @@
 	sa_sys_read_line(ctlr->path, "mode", buf, sizeof(buf));
 	sa_enum_encode(fip_conn_type_table, buf, >mode);
 
-	snprintf(lesb_path, sizeof(lesb_path), "%s/lesb/", ctlr->path);
+	rc = snprintf(lesb_path, sizeof(lesb_path), "%s/lesb/", ctlr->path);
+	if (rc >= sizeof(lesb_path))
+		goto fail;
 
 	/* Get LESB statistics */
 	sa_sys_read_u32(lesb_path, "link_fail",

Bug#884403: lsh-utils FTBFS with nettle-dev 3.4-1

[Adrian Bunk]

Source: lsh-utils
Version: 2.1-11
Severity: serious
Tags: buster sid

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

...
In file included from dummy.c:31:0:
dummy.c:115:1: error: conflicting types for 'nettle_base64_encode_update'
 base64_encode_update(struct base64_encode_ctx *ctx UNUSED,
 ^
/usr/include/nettle/base64.h:98:1: note: previous declaration of 
'nettle_base64_encode_update' was here
 base64_encode_update(struct base64_encode_ctx *ctx,
 ^
dummy.c:122:1: error: conflicting types for 'nettle_base64_encode_final'
 base64_encode_final(struct base64_encode_ctx *ctx UNUSED,
 ^
/usr/include/nettle/base64.h:106:1: note: previous declaration of 
'nettle_base64_encode_final' was here
 base64_encode_final(struct base64_encode_ctx *ctx,
 ^
dummy.c:131:1: error: conflicting types for 'nettle_base64_decode_update'
 base64_decode_update(struct base64_decode_ctx *ctx UNUSED,
 ^
/usr/include/nettle/base64.h:158:1: note: previous declaration of 
'nettle_base64_decode_update' was here
 base64_decode_update(struct base64_decode_ctx *ctx,
 ^
Makefile:1034: recipe for target 'dummy.o' failed
make[5]: *** [dummy.o] Error 1

Processed: found 884241 in 1.56-1

[Debian Bug Tracking System]

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

> found 884241 1.56-1
Bug #884241 [src:bouncycastle] bouncycastle: CVE-2017-13098
Marked as found in versions bouncycastle/1.56-1.
> thanks
Stopping processing here.

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

Bug#884400: ssh-agent-filter FTBFS with nettle-dev 3.4-1

[Adrian Bunk]

Source: ssh-agent-filter
Version: 0.4.2-1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ssh-agent-filter.html

...
g++ -g -O2 -Werror=array-bounds -Werror=clobbered -Werror=volatile-register-var 
-Werror=implicit-function-declaration 
-fdebug-prefix-map=/build/1st/ssh-agent-filter-0.4.2=. -fstack-protector-strong 
-Wformat -Werror=format-security -std=c++11 -Wdate-time -D_FORTIFY_SOURCE=2 
-D_FILE_OFFSET_BITS=64  -c -o ssh-agent-filter.o ssh-agent-filter.C
ssh-agent-filter.C: In function 'std::__cxx11::string md5_hex(const string&)':
ssh-agent-filter.C:114:48: error: invalid conversion from 'uint8_t* {aka 
unsigned char*}' to 'char*' [-fpermissive]
  base16_encode_update(hex, MD5_DIGEST_SIZE, bin);
^
In file included from ssh-agent-filter.C:82:0:
/usr/include/nettle/base16.h:64:1: note:   initializing argument 1 of 'void 
nettle_base16_encode_update(char*, size_t, const uint8_t*)'
 base16_encode_update(char *dst,
 ^
ssh-agent-filter.C: In function 'std::__cxx11::string base64_encode(const 
string&)':
ssh-agent-filter.C:122:98: error: invalid conversion from 'uint8_t* {aka 
unsigned char*}' to 'char*' [-fpermissive]
  auto len = base64_encode_update(, b64, s.size(), reinterpret_cast(s.data()));

  ^
In file included from ssh-agent-filter.C:81:0:
/usr/include/nettle/base64.h:98:1: note:   initializing argument 2 of 'size_t 
nettle_base64_encode_update(base64_encode_ctx*, char*, size_t, const uint8_t*)'
 base64_encode_update(struct base64_encode_ctx *ctx,
 ^
ssh-agent-filter.C:123:39: error: invalid conversion from 'uint8_t* {aka 
unsigned char*}' to 'char*' [-fpermissive]
  len += base64_encode_final(, b64 + len);
   ^
In file included from ssh-agent-filter.C:81:0:
/usr/include/nettle/base64.h:106:1: note:   initializing argument 2 of 'size_t 
nettle_base64_encode_final(base64_encode_ctx*, char*)'
 base64_encode_final(struct base64_encode_ctx *ctx,
 ^
ssh-agent-filter.C: In function 'int main(int, const char* const*)':
ssh-agent-filter.C:547:8: warning: ignoring return value of 'int chdir(const 
char*)', declared with attribute warn_unused_result [-Wunused-result]
   chdir("/");
   ~^
: recipe for target 'ssh-agent-filter.o' failed
make[1]: *** [ssh-agent-filter.o] Error 1

Bug#883938: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51-2

[Rakesh Ginjupalli]

On Azure Standard DS14 (16 cores) Debian 8 VM, upgraded the kernel to 
3.16.51-2. Upon reboot, VM ended up with kernel panic.





Serial log for reference:





[0.00] Initializing cgroup subsys cpuset

[0.00] Initializing cgroup subsys cpu

[0.00] Initializing cgroup subsys cpuacct

[0.00] Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) 
(gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.51-2 (2017-12-03)

[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 
root=UUID=62cb0c04-37d7-4645-9a63-d0014657d672 ro console=tty0 
console=ttyS0,115200 earlyprintk=ttyS0,115200 consoleblank=0 
systemd.show_status=true

[0.00] e820: BIOS-provided physical RAM map:

[0.00] BIOS-e820: [mem 0x-0x0009fbff] usable

[0.00] BIOS-e820: [mem 0x0009fc00-0x0009] reserved

[0.00] BIOS-e820: [mem 0x000e-0x000f] reserved

[0.00] BIOS-e820: [mem 0x0010-0x1ffe] usable

[0.00] BIOS-e820: [mem 0x1fff-0x1fffefff] ACPI data

[0.00] BIOS-e820: [mem 0x1000-0x1fff] ACPI NVS

[0.00] BIOS-e820: [mem 0x0001-0x000edfff] usable

[0.00] BIOS-e820: [mem 0x000ee020-0x000fdfff] usable

[0.00] BIOS-e820: [mem 0x0010-0x001d001f] usable

[0.00] bootconsole [earlyser0] enabled

[0.00] NX (Execute Disable) protection: active

[0.00] SMBIOS 2.3 present.

[0.00] Hypervisor detected: Microsoft HyperV

[0.00] HyperV: features 0x2e7f, hints 0xc2c

[0.00] HyperV: LAPIC Timer Frequency: 0xc3500

[0.00] AGP: No AGP bridge found

[0.00] e820: last_pfn = 0x1d00200 max_arch_pfn = 0x4

[0.00] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106

[0.00] e820: last_pfn = 0x1fff0 max_arch_pfn = 0x4

[0.00] found SMP MP-table at [mem 0x000ff780-0x000ff78f] mapped at 
[880ff780]

[0.00] Using GB pages for direct mapping

[0.00] init_memory_mapping: [mem 0x-0x000f]

[0.00] init_memory_mapping: [mem 0x1d-0x1d001f]

[0.00] init_memory_mapping: [mem 0x1cfc00-0x1c]

[0.00] init_memory_mapping: [mem 0x1c8000-0x1cfbff]

[0.00] init_memory_mapping: [mem 0x10-0x1c7fff]

[0.00] init_memory_mapping: [mem 0x0010-0x1ffe]

[0.00] init_memory_mapping: [mem 0x1-0xedfff]

[0.00] init_memory_mapping: [mem 0xee020-0xfdfff]

[0.00] RAMDISK: [mem 0x1e9ef000-0x1f7c6fff]

[0.00] ACPI: Early table checksum verification disabled

[0.00] ACPI: RSDP 0x000F5BF0 14 (v00 ACPIAM)

[0.00] ACPI: RSDT 0x1FFF 40 (v01 VRTUAL MICROSFT 
06001702 MSFT 0097)

[0.00] ACPI: FACP 0x1FFF0200 81 (v02 VRTUAL MICROSFT 
06001702 MSFT 0097)

[0.00] ACPI: DSDT 0x1FFF1D24 003CBE (v01 MSFTVM MSFTVM02 
0002 INTL 02002026)

[0.00] ACPI: FACS 0x1000 40

[0.00] ACPI: WAET 0x1FFF1A80 28 (v01 VRTUAL MICROSFT 
06001702 MSFT 0097)

[0.00] ACPI: SLIC 0x1FFF1AC0 000176 (v01 VRTUAL MICROSFT 
06001702 MSFT 0097)

[0.00] ACPI: OEM0 0x1FFF1CC0 64 (v01 VRTUAL MICROSFT 
06001702 MSFT 0097)

[0.00] ACPI: SRAT 0x1FFF0800 0002C0 (v02 VRTUAL MICROSFT 
0001 MSFT 0001)

[0.00] ACPI: APIC 0x1FFF0300 000452 (v01 VRTUAL MICROSFT 
06001702 MSFT 0097)

[0.00] ACPI: OEMB 0x1040 64 (v01 VRTUAL MICROSFT 
06001702 MSFT 0097)

[0.00] SRAT: PXM 0 -> APIC 0x00 -> Node 0

[0.00] SRAT: PXM 0 -> APIC 0x01 -> Node 0

[0.00] SRAT: PXM 0 -> APIC 0x02 -> Node 0

[0.00] SRAT: PXM 0 -> APIC 0x03 -> Node 0

[0.00] SRAT: PXM 0 -> APIC 0x04 -> Node 0

[0.00] SRAT: PXM 0 -> APIC 0x05 -> Node 0

[0.00] SRAT: PXM 0 -> APIC 0x06 -> Node 0

[0.00] SRAT: PXM 0 -> APIC 0x07 -> Node 0

[0.00] SRAT: PXM 1 -> APIC 0x08 -> Node 1

[0.00] SRAT: PXM 1 -> APIC 0x09 -> Node 1

[0.00] SRAT: PXM 1 -> APIC 0x0a -> Node 1

[0.00] SRAT: PXM 1 -> APIC 0x0b -> Node 1

[0.00] SRAT: PXM 1 -> APIC 0x0c -> Node 1

[0.00] SRAT: PXM 1 -> APIC 0x0d -> Node 1

[0.00] SRAT: PXM 1 -> APIC 0x0e -> Node 1

[0.00] SRAT: PXM 1 -> APIC 0x0f -> Node 1

[0.00] SRAT: Node 0 PXM 0 [mem 0x-0x1fff] hotplug

[0.00] SRAT: Node 0 PXM 0 [mem 0x1-0xedfff] hotplug

[0.00] SRAT: Node 1 PXM 1 [mem 0xee020-0xfdfff] hotplug

[0.00] SRAT: Node 1 PXM 1 [mem 0x10-0x1d001f] hotplug

Processed: Move due to BTS confusion (binary package of same name elsewhere)

[Debian Bug Tracking System]

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

> reassign 884292 libkf5tnef5 16.04.2-1
Bug #884292 [src:ktnef] ktnef: Cannot fulfill the build dependencies
Bug reassigned from package 'src:ktnef' to 'libkf5tnef5'.
No longer marked as found in versions ktnef/16.04.2-1.
Ignoring request to alter fixed versions of bug #884292 to the same values 
previously set
Bug #884292 [libkf5tnef5] ktnef: Cannot fulfill the build dependencies
Marked as found in versions ktnef/16.04.2-1.
> thanks
Stopping processing here.

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

Bug#846923: marked as done (mpb: FTBFS on mipsel - hanging on autconf test for BLAS zdotc)

[Debian Bug Tracking System]

Your message dated Thu, 14 Dec 2017 19:05:31 +
with message-id 
and subject line Bug#846923: fixed in mpb 1.5-3
has caused the Debian Bug report #846923,
regarding mpb: FTBFS on mipsel - hanging on autconf test for BLAS zdotc
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.)


-- 
846923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846923
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mpb
Version: 1.5-2
Severity: serious
Justification: FTBFS

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,

mpb now FTBFS on mipsel [1]. It is caused by the autoconf test for BLAS zdotc 
never terminating. Then the build is killed after 150 min of inactivity.
[1] 
https://buildd.debian.org/status/fetch.php?pkg=mpb=mipsel=1.5-2%2Bb5=1480753328

I tested the build on porter box eller.debian.org with the very same result.

Thanks,

_g.

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

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

-BEGIN PGP SIGNATURE-

iQEcBAEBCAAGBQJYQ/ohAAoJEO/obGx//s+DYVkH/2YMlBTGIFTusf79eeb3jTnl
DH0seBCdg8A45CY1gMJaCG++IlWfg45pGH5U2cUFevPmJp7/DYRcgnxmJHskjUz1
TRLADRih5JGQ0sqo0flqlE7or8iRbYrrEtYvY8zkXt0Ox7BqPXInQEWKnwy7JYB5
Hnl+qVB4gNlFBEgB6eM5ouX8w2/9QmJSlDNCLvgpCSxq7XDaEeCpHfjP0oJvRUYe
jpsgXaYljL8YULSkR+kYlvwTYLyBI12p6foXd6Pfdgg/fVECoffcKWMuy/CSn1BO
m7tc1bnJbLTotrodkf+ecl0P7tLgNvR4DyskU7Rjv58V7IC7didDuvlEill/IOw=
=6yK/
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: mpb
Source-Version: 1.5-3

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

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated mpb 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, 13 Dec 2017 19:00:00 +0100
Source: mpb
Binary: mpb mpb-mpi mpb-doc mpb-dev mpb-scm
Architecture: source amd64 all
Version: 1.5-3
Distribution: sid
Urgency: low
Maintainer: Thorsten Alteholz 
Changed-By: Thorsten Alteholz 
Description:
 mpb- MIT Photonic-Bands
 mpb-dev- MIT Photonic-Bands development files
 mpb-doc- MIT Photonic-Bands documentation
 mpb-mpi- MIT Photonic-Bands, parallel (mpich) version
 mpb-scm- MIT Photonic-Bands initialisation files
Closes: 846923
Changes:
 mpb (1.5-3) unstable; urgency=low
 .
   * don't build package on mipsel (Closes: #846923)
   * debian/control: bump Standards Version to 4.1.2 (no changes)
Checksums-Sha1:
 510aea456da854a732df2cfad4cf91a62d65493e 2769 mpb_1.5-3.dsc
 43c8aff07a9810d0910669ab8aa2cd24c6a60c6b 1056327 mpb_1.5.orig.tar.gz
 36335e0f79d36e89b6e24958e5b3b98c773f5a82 11224 mpb_1.5-3.debian.tar.xz
 53d7e8ed17e955bf53223eb459736db14aba1563 573744 mpb-dbgsym_1.5-3_amd64.deb
 20211107991d3c28174db6da41c465a06aae6eea 70648 mpb-dev_1.5-3_amd64.deb
 75591b511fcbc6287fc79db2fb2f8d52301a3ada 442512 mpb-doc_1.5-3_all.deb
 6e3a3a7e366216763c0ca56cbacada9cf999507c 537644 mpb-mpi-dbgsym_1.5-3_amd64.deb
 f2a26138ee06dc09e0c21c954fcae4386a48e358 226920 mpb-mpi_1.5-3_amd64.deb
 e3acb04df53d2a1f0ae1557ff880cf1a48a66946 74524 mpb-scm_1.5-3_all.deb
 3a38aacec4c302db4716599f5f5c45558b4c9428 8785 mpb_1.5-3_amd64.buildinfo
 16dd07ea7d4a9f8f1c698a3c1f9dd4f6b3ad5480 250868 mpb_1.5-3_amd64.deb
Checksums-Sha256:
 9613958516224c1646cd434d68b441e6df0d51df068b92b9c18a10270be865e1 2769 
mpb_1.5-3.dsc
 3deafe79185eb9eb8a8fe97d9fe51624221f51c1cf4baff4b4a7242c51130bd7 1056327 
mpb_1.5.orig.tar.gz
 4ba6bb91d0cf6919c7c7d0237134cf759c5a78678a7d0866d082e3dcf219c471 11224 
mpb_1.5-3.debian.tar.xz
 9f9088c1db2f658b2b32da841d2242aa84b999d99f91ad3ca68a38890b3523fc 573744 
mpb-dbgsym_1.5-3_amd64.deb
 968a7df23a285352dfd283ab2520a6c3474c1b43e93ff2056cb48b5a7fbf0742 70648 
mpb-dev_1.5-3_amd64.deb
 

Bug#884386: reprotest FTBFS: test failure

[Adrian Bunk]

Source: reprotest
Version: 0.7.5
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=reprotest=all=0.7.5=1513272013=0

...
===
Reproduction successful
===
No differences in ./../*.deb
5bd731e16d34c2dc16241cdcccf584ccd6f828b7d676f9608ea55df3e84d9190  
./../reprotest_0.7.5_all.deb
However, other factors may still make the build unreproducible; try re-running 
with --vary=+all.
..
tests/test_shell.py ..

=== FAILURES ===
 test_variations[null-num_cpus] 

virtual_server = ['null'], captures = 'num_cpus'

@pytest.mark.parametrize('captures', list(VARIATIONS.keys()))
def test_variations(virtual_server, captures):
expected = captures not in TEST_VARIATIONS
with setup_logging(False):
>   check_reproducibility('python3 mock_build.py ' + captures, 
> virtual_server, expected)

tests/test_reprotest.py:90: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

command = 'python3 mock_build.py num_cpus', virtual_server = ['null']
reproducible = False

def check_reproducibility(command, virtual_server, reproducible):
result = reprotest.check(
reprotest.TestArgs.of(command, 'tests', 'artifact'),
reprotest.TestbedArgs.of(virtual_server),
Variations.of(VariationSpec.default(TEST_VARIATIONS)))
>   assert result == reproducible
E   assert True == False

tests/test_reprotest.py:28: AssertionError
= 1 failed, 20 passed in 61.23 seconds =
usage: reprotest --help []
   reprotest [options] [-c ]  
[]
 [--  [ ...]]
   reprotest [options] [-s ]  
[]
 [--  [ ...]]
reprotest: error: unrecognized arguments: -d
usage: reprotest --help []
   reprotest [options] [-c ]  
[]
 [--  [ ...]]
   reprotest [options] [-s ]  
[]
 [--  [ ...]]
reprotest: error: unrecognized arguments: null -d
usage: reprotest --help []
   reprotest [options] [-c ]  
[]
 [--  [ ...]]
   reprotest [options] [-s ]  
[]
 [--  [ ...]]
reprotest: error: unrecognized arguments: null -d
usage: reprotest --help []
   reprotest [options] [-c ]  
[]
 [--  [ ...]]
   reprotest [options] [-s ]  
[]
 [--  [ ...]]
reprotest: error: unrecognized arguments: -d
usage: reprotest --help []
   reprotest [options] [-c ]  
[]
 [--  [ ...]]
   reprotest [options] [-s ]  
[]
 [--  [ ...]]
reprotest: error: unrecognized arguments: -d
usage: reprotest --help []
   reprotest [options] [-c ]  
[]
 [--  [ ...]]
   reprotest [options] [-s ]  
[]
 [--  [ ...]]
reprotest: error: unrecognized arguments: null -d
usage: reprotest --help []
   reprotest [options] [-c ]  
[]
 [--  [ ...]]
   reprotest [options] [-s ]  
[]
 [--  [ ...]]
reprotest: error: unrecognized arguments: null -d
usage: reprotest --help []
   reprotest [options] [-c ]  
[]
 [--  [ ...]]
   reprotest [options] [-s ]  
[]
 [--  [ ...]]
reprotest: error: unrecognized arguments: -d
ERROR: InvocationError: '/<>/.tox/py36/bin/python -m coverage run 
--omit .tox/* --parallel -m py.test -s tests/'
___ summary 
ERROR:   py36: commands failed
debian/rules:27: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#884309: starpu-examples: depends indirectly on nonfree package libsocl-contrib-1.2-0

[Adrian Bunk]

On Thu, Dec 14, 2017 at 06:48:33PM +0100, Samuel Thibault wrote:
> Adrian Bunk, on jeu. 14 déc. 2017 19:46:19 +0200, wrote:
> > Related to that, what is actually the difference between the packages in 
> > main and the packages in contrib?
> 
> It happens that for libsocl there is no difference. For other starpu
> packages, it's the availability of the CUDA support.

Sorry for being unclear on that.

I do (at least right now) not personally care about that.

But please make that somehow visible in the package descriptions.

> Samuel

cu
Adrian

-- 

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

Bug#884309: starpu-examples: depends indirectly on nonfree package libsocl-contrib-1.2-0

[Samuel Thibault]

Adrian Bunk, on jeu. 14 déc. 2017 19:46:19 +0200, wrote:
> Related to that, what is actually the difference between the packages in 
> main and the packages in contrib?

It happens that for libsocl there is no difference. For other starpu
packages, it's the availability of the CUDA support.

Samuel

Processed: Not a problem in stretch

[Debian Bug Tracking System]

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

> tags 884230 buster sid
Bug #884230 [enblend-enfuse] needs updated build-deps (add texlive-fonts-extra)
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Processed: reassign 883987 to src:boost1.62, tagging 883987

[Debian Bug Tracking System]

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

> reassign 883987 src:boost1.62 1.62.0+dfsg-4
Bug #883987 [src:boost-defaults] FTBFS error: partial specialization ... after 
instantiation ... (with patch)
Bug #884184 [src:boost-defaults] FTBFS error: partial specialization ... after 
instantiation ... (with patch)
Bug #884185 [src:boost-defaults] FTBFS error: partial specialization ... after 
instantiation ... (with patch)
Bug reassigned from package 'src:boost-defaults' to 'src:boost1.62'.
Bug reassigned from package 'src:boost-defaults' to 'src:boost1.62'.
Bug reassigned from package 'src:boost-defaults' to 'src:boost1.62'.
No longer marked as found in versions boost-defaults/1.62.
No longer marked as found in versions boost-defaults/1.62.
No longer marked as found in versions boost-defaults/1.62.
Ignoring request to alter fixed versions of bug #883987 to the same values 
previously set
Ignoring request to alter fixed versions of bug #884184 to the same values 
previously set
Ignoring request to alter fixed versions of bug #884185 to the same values 
previously set
Bug #883987 [src:boost1.62] FTBFS error: partial specialization ... after 
instantiation ... (with patch)
Bug #884184 [src:boost1.62] FTBFS error: partial specialization ... after 
instantiation ... (with patch)
Bug #884185 [src:boost1.62] FTBFS error: partial specialization ... after 
instantiation ... (with patch)
Marked as found in versions boost1.62/1.62.0+dfsg-4.
Marked as found in versions boost1.62/1.62.0+dfsg-4.
Marked as found in versions boost1.62/1.62.0+dfsg-4.
> tags 883987 + sid buster
Bug #883987 [src:boost1.62] FTBFS error: partial specialization ... after 
instantiation ... (with patch)
Bug #884184 [src:boost1.62] FTBFS error: partial specialization ... after 
instantiation ... (with patch)
Bug #884185 [src:boost1.62] FTBFS error: partial specialization ... after 
instantiation ... (with patch)
Added tag(s) sid and buster.
Added tag(s) sid and buster.
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Bug#884309: starpu-examples: depends indirectly on nonfree package libsocl-contrib-1.2-0

[Adrian Bunk]

On Wed, Dec 13, 2017 at 07:54:59PM +0100, Samuel Thibault wrote:
> Re-answering :)
> 
> Jonas Smedegaard, on mer. 13 déc. 2017 19:36:47 +0100, wrote:
> > The issue I raise here is more generally that the package dependencies 
> > declared are not deterministic regarding main versus non-main packages.
> 
> I understand, but I don't know how to express what we want: both
> choice for the user, and main by default.

The problem is that the package is both real and virtual, the proper 
solution would be to rename libsocl-1.2-0 to libsocl-free-1.2-0 and
have it provide libsocl-1.2-0.

After that the usual way of  |  dependency would work
with libsocl-free-1.2-0 | libsocl-1.2-0.

This is non-trivial to sort out right now, but please consider changing 
the package naming scheme the next time the soname changes.

Related to that, what is actually the difference between the packages in 
main and the packages in contrib?
The package descriptions are currently identical.

> Samuel

cu
Adrian

-- 

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

Bug#877966: This is happening again

[Bastian Blank]

On Tue, Dec 12, 2017 at 05:47:02PM -0600, Julien Cristau wrote:
> So I wonder if we should:
> - kill mirror-bytemark until we fix the I/O issue that plagues us there

Yes, please.

> - increase PUSHDELAY

Can do.

> - change ftpsync so the first mirror that times out waiting for stage1
> locks touches ${LOCKDIR}/all_stage1 so its siblings don't wait in vain
> making the problem worse

Not sure what you mean with that.  A timeout means that all others would
have finished already.

Bastian

-- 
There are always alternatives.
-- Spock, "The Galileo Seven", stardate 2822.3

Bug#884069: marked as done (Kernel crash on boot on IBM BladeCenter HS22)

[Debian Bug Tracking System]

Your message dated Thu, 14 Dec 2017 17:32:32 +
with message-id 
and subject line Bug#883938: fixed in linux 3.16.51-3
has caused the Debian Bug report #883938,
regarding Kernel crash on boot on IBM BladeCenter HS22
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.)


-- 
883938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883938
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-3.16.0-4-amd64
Version: 3.16.51-2

Loading Linux 3.16.0-4-amd64 ...
Loading initial ramdisk ...
[0.604128] general protection fault:  [#1] SMP
[0.609303] Modules linked in:
[0.612493] CPU: 0 PID: 1 Comm: swapper/0 Tainted: GW
3.16.0-4-amd64 #1 Debian 3.16.51-2
[0.621685] Hardware name: IBM BladeCenter HS22 -[7870SGX]-/68Y8077,
BIOS -[P9E163AUS-1.24]- 09/17/2014
[0.631141] task: 8803731392d0 ti: 88037313c000 task.ti:
88037313c000
[0.638684] RIP: 0010:[]  []
build_sched_domains+0x72d/0xcf0
[0.647609] RSP: :88037313fdf8  EFLAGS: 00010216
[0.652982] RAX:  RBX:  RCX:
0012
[0.660175] RDX: 00016f48 RSI:  RDI:
0200
[0.667372] RBP: 880372f5d698 R08: 880372f5e0e0 R09:
0139
[0.674566] R10:  R11: 88037313fb06 R12:
880372f5e0c0
[0.681761] R13: 0200 R14: 880672e640c0 R15:
0200
[0.688958] FS:  () GS:88037fc0()
knlGS:
[0.697110] CS:  0010 DS:  ES:  CR0: 8005003b

[0.702914] CR2: 88067000 CR3: 01813000 CR4:
07f0
[0.710109] Stack:
[0.712183]  8806 880372f5e0d8 880372f5d600
880672e640c0
[0.719940]    
880372f53e00
[0.727715]   f1c8 

[0.735501] Call Trace:
[0.738022]  [] ? sched_init_smp+0x398/0x452

[0.743930]  [] ? mutex_lock+0xe/0x2a
[0.749229]  [] ? put_online_cpus+0x23/0x80

[0.755050]  [] ? stop_machine+0x2c/0x40

[0.760618]  [] ? kernel_init_freeable+0xdd/0x1e1

[0.766963]  [] ? rest_init+0x80/0x80
[0.772264]  [] ? kernel_init+0xa/0xf0

[0.777652]  [] ? ret_from_fork+0x58/0x90

[0.783298]  [] ? rest_init+0x80/0x80
[0.788595] Code: c0 0f 85 46 05 00 00 48 8b 74 24 08 48 c7 c2 00 dd
a6 81 bf ff ff ff ff e8 91 78 21 00 48 98 49 8b 56 10 48 8b 04 c5 a0 1e
8e 81 <48> 8b 14 10 b8 01 00 00 00 49 89 54 24 10 f0 0f c1 02 85 c0 75

[0.812501] RIP  [] build_sched_domains+0x72d/0xcf0

[0.819101]  RSP 
[0.822668] ---[ end trace b6ea7a8f78a6ba93 ]---
[0.827375] Kernel panic - not syncing: Attempted to kill init!
exitcode=0x000b
[0.827375]
[0.836621] ---[ end Kernel panic - not syncing: Attempted to kill
init! exitcode=0x000b
[0.836621]
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 3.16.51-3

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

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

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux 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, 13 Dec 2017 20:11:46 +
Source: linux
Binary: linux-source-3.16 linux-doc-3.16 linux-manual-3.16 
linux-support-3.16.0-4 linux-libc-dev linux-headers-3.16.0-4-all 
linux-headers-3.16.0-4-all-alpha kernel-image-3.16.0-4-alpha-generic-di 
nic-modules-3.16.0-4-alpha-generic-di 
nic-wireless-modules-3.16.0-4-alpha-generic-di 
nic-shared-modules-3.16.0-4-alpha-generic-di 
serial-modules-3.16.0-4-alpha-generic-di 
usb-serial-modules-3.16.0-4-alpha-generic-di 
ppp-modules-3.16.0-4-alpha-generic-di pata-modules-3.16.0-4-alpha-generic-di 
cdrom-core-modules-3.16.0-4-alpha-generic-di 
scsi-core-modules-3.16.0-4-alpha-generic-di 
scsi-modules-3.16.0-4-alpha-generic-di 
scsi-common-modules-3.16.0-4-alpha-generic-di 

Bug#884140: marked as done (Kernel 3.16.51-2 general protection fault in sched_init_smp())

[Debian Bug Tracking System]

Your message dated Thu, 14 Dec 2017 17:32:32 +
with message-id 
and subject line Bug#883938: fixed in linux 3.16.51-3
has caused the Debian Bug report #883938,
regarding Kernel 3.16.51-2 general protection fault in sched_init_smp()
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.)


-- 
883938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883938
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image
Version: 3.16.0-4-amd64

Since the update from version 3.16.43 to 3.16.51-2 the kernel crashes
during the boot (Dell Inc. PowerEdge 2970 with 2 Quad-Core AMD
Opteron(tm) Processor 2350).

We are using Debian GNU/Linux 8, here is the kernel log we collected on
our server:

[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Initializing cgroup subsys cpuacct
[0.00] Linux version 3.16.0-4-amd64
(debian-ker...@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) )
#1 SMP Debian 3.16.51-2 (2017-12-03)
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64
root=UUID=eb8d5ccd-a904-458a-9b58-1555dbd03c95 ro console=tty0
console=ttyS0,115800
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009] usable
[0.00] BIOS-e820: [mem 0x0010-0xbfab] usable
[0.00] BIOS-e820: [mem 0xbfac-0xbfad5fff]
reserved
[0.00] BIOS-e820: [mem 0xbfad6000-0xbfaf5bff]
ACPI data
[0.00] BIOS-e820: [mem 0xbfaf5c00-0xbfff]
reserved
[0.00] BIOS-e820: [mem 0xf000-0xf7ff]
reserved
[0.00] BIOS-e820: [mem 0xfe00-0x]
reserved
[0.00] BIOS-e820: [mem 0x0001-0x00043fff] usable
[0.00] NX (Execute Disable) protection: active
[0.00] SMBIOS 2.4 present.
[0.00] AGP: No AGP bridge found
[0.00] e820: last_pfn = 0x44 max_arch_pfn = 0x4
[0.00] x86 PAT enabled: cpu 0, old 0x7040600070406, new
0x7010600070106
[0.00] e820: last_pfn = 0xbfac0 max_arch_pfn = 0x4
[0.00] found SMP MP-table at [mem 0x000fe710-0x000fe71f] mapped
at [880fe710]
[0.00] Using GB pages for direct mapping
[0.00] init_memory_mapping: [mem 0x-0x000f]
[0.00] init_memory_mapping: [mem 0x43fe0-0x43fff]
[0.00] init_memory_mapping: [mem 0x43c00-0x43fdf]
[0.00] init_memory_mapping: [mem 0x4-0x43bff]
[0.00] init_memory_mapping: [mem 0x0010-0xbfab]
[0.00] init_memory_mapping: [mem 0x1-0x3]
[0.00] RAMDISK: [mem 0x36198000-0x370c3fff]
[0.00] ACPI: Early table checksum verification disabled
[0.00] ACPI: RSDP 0x000F22A0 24 (v02 DELL  )
[0.00] ACPI: XSDT 0x000F231C 8C (v01 DELL   PE_SC3
0001 DELL 0001)
[0.00] ACPI: FACP 0xBFAF1BD8 F4 (v03 DELL   PE_SC3
0001 DELL 0001)
[0.00] ACPI: DSDT 0xBFAD6000 00476A (v01 DELL   PE_SC3
0001 INTL 20050624)
[0.00] ACPI: FACS 0xBFAF4400 40
[0.00] ACPI: FACS 0xBFAF4400 40
[0.00] ACPI: APIC 0xBFAF1878 A0 (v01 DELL   PE_SC3
0001 DELL 0001)
[0.00] ACPI: SPCR 0xBFAF191C 50 (v01 DELL   PE_SC3
0001 DELL 0001)
[0.00] ACPI: HPET 0xBFAF1970 38 (v01 DELL   PE_SC3
0001 DELL 0001)
[0.00] ACPI: MCFG 0xBFAF19AC 3C (v01 DELL   PE_SC3
0001 DELL 0001)
[0.00] ACPI: SLIC 0xBFAF19EC 24 (v01 DELL   PE_SC3
0001 DELL 0001)
[0.00] ACPI: ERST 0xBFADA8EC 000210 (v01 DELL   PE_SC3
0001 DELL 0001)
[0.00] ACPI: HEST 0xBFADAAFC 00027C (v01 DELL   PE_SC3
0001 DELL 0001)
[0.00] ACPI: BERT 0xBFADA76C 30 (v01 DELL   PE_SC3
0001 DELL 0001)
[0.00] ACPI: EINJ 0xBFADA79C 000150 (v01 DELL   PE_SC3
0001 DELL 0001)
[0.00] ACPI: SRAT 0x000FC144 000150 (v01 DELL   PE_SC3
0001 DELL 0001)
[0.00] ACPI: SSDT 0xBFAF4800 30 (v01 DELL   PE_SC3
0001 DELL 0001)
[0.00] ACPI: TCPA 0xBFAF1B70 64 (v01 DELL   PE_SC3
0001 DELL 0001)
[0.00] SRAT: PXM 0 -> APIC 0x00 -> Node 0
[0.00] SRAT: PXM 0 -> APIC 0x01 -> Node 0
[0.00] SRAT: 

Bug#853369: dbus-c++: ftbfs with GCC-7

[Juhani Numminen]

Control: tags -1 + patch

Hi,

Adding the tag patch since there is the fix suggested by Reverend Homer
and then there is another similar change at a repo that is a "Forked
version of dbus-c++ 0.9.0 that fixes various compilation issues."

https://github.com/pkgw/dbus-cplusplus/commit/acbfee07ec

Regards,
Juhani

Bug#880337: [pkg-php-pear] Bug#880337: php-sabre-vobject-3: diff for NMU version 3.5.2-1.1

[Adrian Bunk]

On Wed, Dec 13, 2017 at 12:19:41PM -1000, David Prévot wrote:
> Hi Adrian,
> 
> Le 13/12/2017 à 09:27, Adrian Bunk a écrit :
> 
> > I've prepared an NMU for php-sabre-vobject-3 (versioned as 3.5.2-1.1) 
> > and uploaded it to DELAYED/14. Please feel free to tell me if I should 
> > cancel it.
> 
> Since this package was introduced as an ownCloud dependency (removed
> from Debian for a while now), I’d rather see this package removed from
> the archive, unless you have a real interest into it (then feel free to
> take up the maintainership). php-sabre-vobject is already in Debian
> (even if this is the version in Sid is quite old).

OK, I've canceled my NMU upload from delayed.

My biggest interest is in getting this bug fixed for stable,
do you plan to do that or shall I submit a pu request?

And the most recent version php-sabre-vobject/experimental
also seems to need this fix.

> Regards
> 
> David

cu
Adrian

-- 

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

Processed: Re: dbus-c++: ftbfs with GCC-7

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #853369 [src:dbus-c++] dbus-c++: ftbfs with GCC-7
Added tag(s) patch.

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

Bug#884295: marked as done (node-semver-diff FTBFS: test failure)

[Debian Bug Tracking System]

Your message dated Thu, 14 Dec 2017 17:04:08 +
with message-id 
and subject line Bug#884295: fixed in node-semver-diff 2.1.0-2
has caused the Debian Bug report #884295,
regarding node-semver-diff FTBFS: test failure
to be marked as done.

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

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


-- 
884295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884295
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-semver-diff
Version: 2.1.0-1
Severity: serious

Some recent change in unstable makes node-semver-diff FTBFS:

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/node-semver-diff-2.1.0'
mocha -R spec
module.js:471
throw err;
^

Error: Cannot find module 'semver'
at Function.Module._resolveFilename (module.js:469:15)
at Function.Module._load (module.js:417:25)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object. (/build/1st/node-semver-diff-2.1.0/index.js:2:14)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object. (/build/1st/node-semver-diff-2.1.0/test.js:3:18)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at /usr/lib/nodejs/mocha/lib/mocha.js:172:27
at Array.forEach (native)
at Mocha.loadFiles (/usr/lib/nodejs/mocha/lib/mocha.js:169:14)
at Mocha.run (/usr/lib/nodejs/mocha/lib/mocha.js:356:31)
at Object. (/usr/lib/nodejs/mocha/bin/_mocha:366:16)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.runMain (module.js:604:10)
at run (bootstrap_node.js:383:7)
at startup (bootstrap_node.js:149:9)
at bootstrap_node.js:496:3
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Source: node-semver-diff
Source-Version: 2.1.0-2

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 14 Dec 2017 22:20:51 +0530
Source: node-semver-diff
Binary: node-semver-diff
Architecture: source
Version: 2.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Pirate Praveen 
Description:
 node-semver-diff - get the diff type of two semver versions
Closes: 884295
Changes:
 node-semver-diff (2.1.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Add node-semver as build dependency (Closes: #884295)
Checksums-Sha1:
 1c6723adbf477c38583524e1aa8e2c4f39ed9fd2 2135 node-semver-diff_2.1.0-2.dsc
 b7f96d9c0fc0b0a52f817a4b5b2acb08b2081ae7 2200 
node-semver-diff_2.1.0-2.debian.tar.xz
 c9da6bb18df7be1116c32ed9404635d2dbc9d946 8393 
node-semver-diff_2.1.0-2_source.buildinfo
Checksums-Sha256:
 e9b37ef441c589bc94f412a2283843aed2b93b9203359ce87f10d90daac11154 2135 
node-semver-diff_2.1.0-2.dsc
 d4cd8ac0bce02964fe41a3a7ff1dc646f0cece1f765c12753c377a9bf33fb2aa 2200 
node-semver-diff_2.1.0-2.debian.tar.xz
 

Bug#883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51

[Ian Jackson]

The Xen Project CI has six machines which were affected by this
regression.  (Kernel messages are near-identical to those reported
by others in this bug.)  As suggested I downloaded this kernel;

  
https://people.debian.org/~benh/packages/jessie-pu/linux-image-3.16.0-4-amd64_3.16.51-3~a.test_amd64.deb

and I can confirm that this fixes the issue.

We will continue to use this kernel for the affected machines, until
the next Debian point release (in which I hope this will be fixed).

Thanks to Ben for the quick fix and to #debian-kernel for the pointer
to the right bug report.

Regards,
Ian.

Bug#884183: linux-image-3.16.0-4-amd64: Kernel panic at boot

[Benjamin Moody]

On 12/13/17, Benjamin Moody  wrote:
> Same problem here.  3.16.43-2+deb8u5 works, 3.16.51-2 is broken.
>
> Supermicro H8QM3
>
> Quad-Core AMD Opteron(tm) Processor 8347 HE (fam: 10, model: 02,
> stepping: 03)
>
> Two 3ware 9650SE RAID cards

Sorry I didn't think to look for the duplicate bug reports yesterday.

I can confirm that:

- Version 3.16.51-2 is able to boot if 'numa=off' is specified.

- Version 3.16.51-3~a.test (see
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884069#66) fixes
  the issue.

Processed: Re: node-semver-diff FTBFS: test failure

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #884295 [src:node-semver-diff] node-semver-diff FTBFS: test failure
Added tag(s) patch.

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

Bug#884295: node-semver-diff FTBFS: test failure

[Juhani Numminen]

Control: tags -1 patch

On Wed, 13 Dec 2017 14:49:15 +0200 Adrian Bunk  wrote:
> Source: node-semver-diff
> Version: 2.1.0-1
> Severity: serious
> 
> Some recent change in unstable makes node-semver-diff FTBFS:
>
> https://tests.reproducible-builds.org/debian/history/node-semver-diff.html
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-semver-diff.html
> 
> ...
>debian/rules override_dh_auto_test
> make[1]: Entering directory '/build/1st/node-semver-diff-2.1.0'
> mocha -R spec
> module.js:471
> throw err;
> ^
> 
> Error: Cannot find module 'semver'

I think this package needs a Build-Depends: node-semver to be able to run its 
test
during the build. A patch for that is attached.


Regards
Juhani
--- a/debian/control
+++ b/debian/control
@@ -7,6 +7,7 @@ Build-Depends:
  debhelper (>= 9)
  , dh-buildinfo
  , nodejs
+ , node-semver (>= 5.0.3)
  , mocha
 Standards-Version: 4.0.0
 Homepage: https://github.com/sindresorhus/semver-diff

Processed: severity of 884344 is important

[Debian Bug Tracking System]

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

> severity 884344 important
Bug #884344 [ejabberd] ejabberd: After updating to latest erlang packages, 
ejabberd refuses to start
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#884344: ejabberd: After updating to latest erlang packages, ejabberd refuses to start

[Philipp Huebner]

Hi,

since the security patch in Erlang should not have any impact for
ejabberd and because I don't have this problem on my Stretch ejabberd
servers I doubt it is a generic issue and thus I will lower the severity.

Please make sure that epmd and all other erlang processes are stopped
before trying to start ejabberd again. If necessary, kill them manually.

Please also check whether AppArmor is enabled (dmesg | grep -i
apparmor). Have you tried rebooting the server yet?

Without access to your ejabberd logs + dmesg I cannot really help you.

Regards,
-- 
 .''`.   Philipp Huebner 
: :'  :  pgp fp: 6719 25C5 B8CD E74A 5225  3DF9 E5CA 8C49 25E4 205F
`. `'`
  `-



signature.asc
Description: OpenPGP digital signature

Processed: your mail

[Debian Bug Tracking System]

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

> affects  #883987 = src:rheolef
Bug #883987 [src:boost-defaults] FTBFS error: partial specialization ... after 
instantiation ... (with patch)
Bug #884184 [src:boost-defaults] FTBFS error: partial specialization ... after 
instantiation ... (with patch)
Bug #884185 [src:boost-defaults] FTBFS error: partial specialization ... after 
instantiation ... (with patch)
Added indication that 883987 affects src:rheolef
Added indication that 884184 affects src:rheolef
Added indication that 884185 affects src:rheolef
>
End of message, stopping processing here.

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

Processed: Re: Bug#884214: purify FTBFS with libspdlog-dev 1:0.14.0-1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #884214 [src:purify] purify FTBFS with libspdlog-dev 1:0.14.0-1
Added tag(s) pending.

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

Bug#884214: purify FTBFS with libspdlog-dev 1:0.14.0-1

[Ole Streicher]

Control: tags -1 pending
Hello Juhani,

On 14.12.2017 16:57, Juhani Numminen wrote:
> This purify bug is very similar to the sopt one that you fixed.

Thanks; this is already in the git (I should have marked it as pending).
However sopt now fails on i386. I filed an upstream issue at
https://github.com/basp-group/sopt/issues/20

Once this is fixed (or I get convinced that I can just disable the
failing test), I will upload the fixed version.

Thanks for the patch anyway

Best regards

Ole

Bug#884373: helpman: missing GIR dependencies

[Simon McVittie]

Package: helpman
Version: 1.0-1
Severity: serious
Justification: Policy 3.5

helpman depends on python and python-gi, but not on the necessary
GObject-Introspection typelibs to make "from gi.repository import Gtk",
"from gi.repository import Gdk" and "from gi.repository import Pango"
work as intended. It needs to depend on at least gir1.2-gtk-3.0 and
gir1.2-pango-1.0.

In general these dependencies can't be generated automatically, so
the maintainer needs to provide them.

See: file:///usr/share/doc/gobject-introspection/policy.txt.gz
(python-gi is similar to Seed, but in a different language).

Regards,
smcv

Processed: your mail

[Debian Bug Tracking System]

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

> retitle #883987 FTBFS error: partial specialization ... after instantiation 
> ... (with patch)
Bug #883987 [src:boost-defaults] rheolef: FTBFS error: partial specialization 
... after instantiation ...
Bug #884184 [src:boost-defaults] boost1.62 FTBFS error: partial specialization 
... after instantiation ...
Bug #884185 [src:boost-defaults] boost1.62 FTBFS error: partial specialization 
... after instantiation ... (with attachment files)
Changed Bug title to 'FTBFS error: partial specialization ... after 
instantiation ... (with patch)' from 'rheolef: FTBFS error: partial 
specialization ... after instantiation ...'.
Changed Bug title to 'FTBFS error: partial specialization ... after 
instantiation ... (with patch)' from 'boost1.62 FTBFS error: partial 
specialization ... after instantiation ...'.
Changed Bug title to 'FTBFS error: partial specialization ... after 
instantiation ... (with patch)' from 'boost1.62 FTBFS error: partial 
specialization ... after instantiation ... (with attachment files)'.
>
End of message, stopping processing here.

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

Bug#884214: purify FTBFS with libspdlog-dev 1:0.14.0-1

[Juhani Numminen]

Control: tags -1 + patch fixed-upstream

Hello Ole,

This purify bug is very similar to the sopt one that you fixed.
https://bugs.debian.org/884214
https://bugs.debian.org/884219

Suitable patch is attached. It's from upstream git:
https://github.com/basp-group/purify/commit/032209d3f

Regards
Juhani
From: Mayeul d'Avezac 
Date: Wed, 12 Oct 2016 15:42:49 +0100
Origin: https://github.com/basp-group/purify/commit/032209d3fd8a558cf231b76b565b26b78f47faa9.patch
Bug-Debian: https://bugs.debian.org/884214
Subject: spdlog modified API

So disabling color output for now
---
 cpp/purify/logging.enabled.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/cpp/purify/logging.enabled.h
+++ b/cpp/purify/logging.enabled.h
@@ -12,7 +12,7 @@
 //! \brief Initializes a logger.
 //! \details Logger only exists as long as return is kept alive.
 inline std::shared_ptr initialize(std::string const  = "") {
-  auto const result = spdlog::stdout_logger_mt(default_logger_name() + name, color_logger());
+  auto const result = spdlog::stdout_logger_mt(default_logger_name() + name);
   set_level(default_logging_level(), name);
   return result;
 }

Processed: Re: purify FTBFS with libspdlog-dev 1:0.14.0-1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch fixed-upstream
Bug #884214 [src:purify] purify FTBFS with libspdlog-dev 1:0.14.0-1
Added tag(s) patch and fixed-upstream.

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

Processed: your mail

[Debian Bug Tracking System]

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

> unmerge  #884184
Bug #884184 [src:boost-defaults] boost1.62 FTBFS error: partial specialization 
... after instantiation ...
Bug #883987 [src:boost-defaults] rheolef: FTBFS error: partial specialization 
... after instantiation ...
Bug #884185 [src:boost-defaults] boost1.62 FTBFS error: partial specialization 
... after instantiation ... (with attachment files)
Disconnected #884184 from all other report(s).
> unmerge  #884185
Bug #884185 [src:boost-defaults] boost1.62 FTBFS error: partial specialization 
... after instantiation ... (with attachment files)
Bug #883987 [src:boost-defaults] rheolef: FTBFS error: partial specialization 
... after instantiation ...
Disconnected #884185 from all other report(s).
> merge#883987 #884185
Bug #883987 [src:boost-defaults] rheolef: FTBFS error: partial specialization 
... after instantiation ...
Bug #884185 [src:boost-defaults] boost1.62 FTBFS error: partial specialization 
... after instantiation ... (with attachment files)
Merged 883987 884185
> merge#884185 #884184
Bug #884185 [src:boost-defaults] boost1.62 FTBFS error: partial specialization 
... after instantiation ... (with attachment files)
Bug #883987 [src:boost-defaults] rheolef: FTBFS error: partial specialization 
... after instantiation ...
Bug #883987 [src:boost-defaults] rheolef: FTBFS error: partial specialization 
... after instantiation ...
Bug #884184 [src:boost-defaults] boost1.62 FTBFS error: partial specialization 
... after instantiation ...
Merged 883987 884184 884185
>
End of message, stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> affects #883987 - src:rheolef 6.7
Bug #883987 [src:boost-defaults] rheolef: FTBFS error: partial specialization 
... after instantiation ...
Removed indication that 883987 affects src:rheolef and 6.7
> affects #884184 - src:rheolef 6.7
Bug #884184 [src:boost-defaults] boost1.62 FTBFS error: partial specialization 
... after instantiation ...
Removed indication that 884184 affects src:rheolef and 6.7
> affects #884185 - src:rheolef 6.7
Bug #884185 [src:boost-defaults] boost1.62 FTBFS error: partial specialization 
... after instantiation ... (with attachment files)
Removed indication that 884185 affects src:rheolef and 6.7
> merge#884185 #883987
Bug #884185 [src:boost-defaults] boost1.62 FTBFS error: partial specialization 
... after instantiation ... (with attachment files)
Bug #883987 [src:boost-defaults] rheolef: FTBFS error: partial specialization 
... after instantiation ...
Merged 883987 884185
> merge#884185 #884184
Bug #884185 [src:boost-defaults] boost1.62 FTBFS error: partial specialization 
... after instantiation ... (with attachment files)
Bug #883987 [src:boost-defaults] rheolef: FTBFS error: partial specialization 
... after instantiation ...
Bug #883987 [src:boost-defaults] rheolef: FTBFS error: partial specialization 
... after instantiation ...
Bug #884184 [src:boost-defaults] boost1.62 FTBFS error: partial specialization 
... after instantiation ...
Merged 883987 884184 884185
>
End of message, stopping processing here.

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

Processed (with 2 errors): commands

[Debian Bug Tracking System]

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

> merge#884185 #883987
Bug #884185 [src:boost-defaults] boost1.62 FTBFS error: partial specialization 
... after instantiation ... (with attachment files)
Unable to merge bugs because:
affects of #883987 is 'src:rheolef,6.7' not '6.7,src:rheolef'
Failed to merge 884185: Did not alter merged bugs.

> merge#884185 #884184
Failed to merge 884185: failed to get lock on 
/org/bugs.debian.org/spool/lock/884185 -- Unable to lock 
/org/bugs.debian.org/spool/lock/884185 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/884185 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/884185 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/884185 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/884185 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/884185 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/884185 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/884185 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/884185 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/884185 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
$locks = {
   'locks' => {}
 };
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 622.

>
End of message, stopping processing here.

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

Bug#864964: marked as done (autokey-qt: Depends on python-kde4 which is to be removed for Buster)

[Debian Bug Tracking System]

Your message dated Thu, 14 Dec 2017 15:04:00 +
with message-id 
and subject line Bug#864964: fixed in autokey 0.90.4-1.1
has caused the Debian Bug report #864964,
regarding autokey-qt: Depends on python-kde4 which is to be removed for 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.)


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

Dear Maintainer,

During the Buster development cycle Qt4 is going to be removed.  As a
result, PyQt4 and PyKDE4 will be removed as well.  This package depends
on python-kde4.  If you want it to be part of the Buster release, it
will have to be ported to Qt5 (Kf5 Python bindings are not available
yet, but they are expected to be packaged early in the Buster
development cycle).

Scott K
--- End Message ---
--- Begin Message ---
Source: autokey
Source-Version: 0.90.4-1.1

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated autokey 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: Sat, 09 Dec 2017 13:30:55 +0200
Source: autokey
Binary: autokey-common autokey-gtk
Architecture: source
Version: 0.90.4-1.1
Distribution: unstable
Urgency: medium
Maintainer: Luke Faraone 
Changed-By: Adrian Bunk 
Description:
 autokey-common - desktop automation utility - common data
 autokey-gtk - desktop automation utility - GTK+ version
Closes: 864964 875496
Changes:
 autokey (0.90.4-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Remove the autokey-qt package that depended on python-kde4
 which is about to be removed. (Closes: #864964, #875496)
Checksums-Sha1:
 826b86190479da099bb9c13a3f57cc5233251681 2050 autokey_0.90.4-1.1.dsc
 ab62aebbc970c94563c7f1e5d61abc6cebdd8bec 7436 autokey_0.90.4-1.1.debian.tar.xz
Checksums-Sha256:
 4b511a45389a6bbcb41e84d817c7a01a36c6defb11097ab4949849d676b86c3e 2050 
autokey_0.90.4-1.1.dsc
 5beb6305ec2a135e44840806ebb598843347221beb788a56cc118fc9b403571b 7436 
autokey_0.90.4-1.1.debian.tar.xz
Files:
 2e4eca08a68a12eee2b274bd3c47f56b 2050 utils optional autokey_0.90.4-1.1.dsc
 b3596c64c5089f399f9421780ea797cb 7436 utils optional 
autokey_0.90.4-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlor6v8ACgkQiNJCh6LY
mLES9w//SlbCzOYzD+vSpTrlATJkaaFTw2k2V+D501ne7E6y/BVjZSvGtufTjFVO
uC1kDB5oXaL7pff/yg7pn3FCrtpQ+or6qv7XWyDDYgAhogdJt7SpGkeD4zT2E3S4
Gouze1NMW9g+6ybc0gFhJPFN2yadYR6YsaxC1AszXNEHY1lgHSVlk/RPeGCKOZXF
D21JPd9DIxboVS9pNuKjEaJK3A57Xtwi6n75YVV/Eq6LpDebh0yq2dCy0klk/TK4
EO6i2XujXKOvjQWKxNwEgXBtJTYaW0ULM6umunkVw3Y8IJRt7qHrSgtZUxaXyt2p
IT3LgUMqTwgf2wAEwMz6ga+LYNHYiQInBzmr32dvrJrSp2imffyFFVpmy2YOK9/h
02eFGkgEof6oaiz42WZWb49A4SI4YJQWrsmSU85a4kfkPqs/i1ORiJzh87wkvQVG
sQaHjqL082q9p8Bs3yN50ij1kmADbQvqWIca1kKC6CipadPIFcFu3dYTvGeeMn5Y
RGtqbDEOQjfmx0zR9YMHEvaUTEF5ndcCjVmKzqRDUTFoZYIRneA2srwxJ2D66+gf
NgJRXsUU4O5nAPVAG5vfpM91M5Gn3MJkuk7VchcLzRrK12GlxpAZc512G5D7T4Il
fkLITFpDQJAXBAJtsclGC/EclkwTl+PTi1sHNl8OeqimqWSuzho=
=Ynn7
-END PGP SIGNATURE End Message ---

Processed (with 2 errors): your mail

[Debian Bug Tracking System]

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

> unmerge  #884184
Bug #884184 [src:boost-defaults] boost1.62 FTBFS error: partial specialization 
... after instantiation ...
Bug #883987 [src:boost-defaults] rheolef: FTBFS error: partial specialization 
... after instantiation ...
Bug #884185 [src:boost-defaults] boost1.62 FTBFS error: partial specialization 
... after instantiation ... (with attachment files)
Disconnected #884184 from all other report(s).
> unmerge  #884185
Bug #884185 [src:boost-defaults] boost1.62 FTBFS error: partial specialization 
... after instantiation ... (with attachment files)
Bug #883987 [src:boost-defaults] rheolef: FTBFS error: partial specialization 
... after instantiation ...
Disconnected #884185 from all other report(s).
> merge#884185 #883987
Bug #884185 [src:boost-defaults] boost1.62 FTBFS error: partial specialization 
... after instantiation ... (with attachment files)
Unable to merge bugs because:
affects of #883987 is 'src:rheolef,6.7' not '6.7,src:rheolef'
Failed to merge 884185: Did not alter merged bugs.

> merge#884185 #884184
Failed to merge 884185: failed to get lock on 
/org/bugs.debian.org/spool/lock/884185 -- Unable to lock 
/org/bugs.debian.org/spool/lock/884185 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/884185 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/884185 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/884185 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/884185 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/884185 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/884185 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/884185 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/884185 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/884185 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
$locks = {
   'locks' => {}
 };
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 622.

>
End of message, stopping processing here.

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

Processed: Re: Bug#879901: kded5 mem ballooning consumes over 6520.81MB of RAM!

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #879901 [kded5] kded5 memory leak consumes over 600MB of RAM
Severity set to 'important' from 'grave'

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

Bug#879901: kded5 mem ballooning consumes over 6520.81MB of RAM!

[Maximiliano Curia]

Control: severity -1 important

kded acts as a proxy to the background kde services, most likely the leak is 
in one of them, not in kded per se. I'm degrading the severity as I can't 
reproduce it.


¡Hola Nicholas!

El 2017-11-29 a las 05:14 -0500, Nicholas D Steeves escribió:
Please let me know what I can do to help debug this further, because 
I'd like to help solve this asap.


It would be helpful to know which threads kded is executing, in order to do 
that please run the following command: pstree -tp | less, and look for the kded 
processes.


Also it would be interesting to know which services are being managed by kded, 
to find that out you can use the system settings' "Startup and Shutdown" 
"Background services", you can see which services are currently running in you 
session, you can attach your ~/.config/kded5rc that stores this information.


A known culprit on wasting resources is the baloo file indexer (which should 
be disabled by default), I don't remember seeing a leak in kded related to 
baloo, but I haven't paid much attention to it since we disabled it. You can 
check if your file indexer is disabled in: "System Settings" "Search" "File 
Search" "Enable File Search"


Happy hacking,
--
"Any change looks terrible at first." -- Principle of Design Inertia
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature