Bug#880293: marked as done (golang-github-fsouza-go-dockerclient: FTBFS: dh_auto_test: cd _build && go test -v -p 1 github.com/fsouza/go-dockerclient github.com/fsouza/go-dockerclient/testing returned

[Debian Bug Tracking System]

Your message dated Thu, 15 Feb 2018 07:49:12 +
with message-id 
and subject line Bug#880293: fixed in golang-github-fsouza-go-dockerclient 
0.0+git20160622-3
has caused the Debian Bug report #880293,
regarding golang-github-fsouza-go-dockerclient: FTBFS: dh_auto_test: cd _build 
&& go test -v -p 1 github.com/fsouza/go-dockerclient 
github.com/fsouza/go-dockerclient/testing returned exit code 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.)


-- 
880293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-fsouza-go-dockerclient
Version: 0.0+git20160622-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20171030 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> I: golang-github-fsouza-go-dockerclient_0.0+git20160622
> I: UDATE=2016-06-22 00:00:00+00:00
> dh build --buildsystem=golang --with=golang --builddirectory=_build
>dh_update_autotools_config -O--buildsystem=golang -O--builddirectory=_build
>dh_auto_configure -O--buildsystem=golang -O--builddirectory=_build
>dh_auto_build -O--buildsystem=golang -O--builddirectory=_build
>   cd _build && go install 
> -gcflags=\"-trimpath=/<>/golang-github-fsouza-go-dockerclient-0.0\+git20160622/_build/src\"
>  
> -asmflags=\"-trimpath=/<>/golang-github-fsouza-go-dockerclient-0.0\+git20160622/_build/src\"
>  -v -p 1 github.com/fsouza/go-dockerclient 
> github.com/fsouza/go-dockerclient/testing
> github.com/docker/docker/api/types/blkiodev
> github.com/docker/docker/api/types/mount
> github.com/docker/docker/api/types/strslice
> github.com/docker/go-connections/nat
> github.com/docker/go-units
> github.com/docker/docker/api/types/container
> github.com/docker/docker/api/types/versions
> github.com/docker/docker/api/types/filters
> github.com/docker/docker/api/types/network
> github.com/docker/docker/api/types/registry
> github.com/docker/docker/api/types/swarm
> github.com/docker/docker/api/types
> github.com/docker/docker/opts
> github.com/Sirupsen/logrus
> github.com/docker/docker/pkg/fileutils
> github.com/docker/docker/pkg/system
> github.com/opencontainers/runc/libcontainer/user
> github.com/docker/docker/pkg/idtools
> golang.org/x/net/context
> github.com/docker/docker/pkg/ioutils
> github.com/docker/docker/pkg/pools
> github.com/docker/docker/pkg/promise
> github.com/opencontainers/runc/libcontainer/system
> github.com/docker/docker/pkg/archive
> github.com/docker/docker/pkg/homedir
> github.com/docker/docker/pkg/stdcopy
> github.com/hashicorp/go-cleanhttp
> github.com/fsouza/go-dockerclient
> github.com/gorilla/context
> github.com/gorilla/mux
> github.com/fsouza/go-dockerclient/testing
>dh_auto_test -O--buildsystem=golang -O--builddirectory=_build
>   cd _build && go test -v -p 1 github.com/fsouza/go-dockerclient 
> github.com/fsouza/go-dockerclient/testing
> === RUN   TestAuthLegacyConfig
> --- PASS: TestAuthLegacyConfig (0.00s)
> === RUN   TestAuthBadConfig
> --- PASS: TestAuthBadConfig (0.00s)
> === RUN   TestAuthAndOtherFields
> --- PASS: TestAuthAndOtherFields (0.00s)
> === RUN   TestAuthConfig
> --- PASS: TestAuthConfig (0.00s)
> === RUN   TestAuthCheck
> --- PASS: TestAuthCheck (0.00s)
> === RUN   TestBuildImageMultipleContextsError
> --- PASS: TestBuildImageMultipleContextsError (0.00s)
> === RUN   TestBuildImageContextDirDockerignoreParsing
> --- PASS: TestBuildImageContextDirDockerignoreParsing (0.00s)
> === RUN   TestBuildImageSendXRegistryConfig
> --- PASS: TestBuildImageSendXRegistryConfig (0.00s)
> === RUN   TestChangeString
> --- PASS: TestChangeString (0.00s)
> === RUN   TestNewAPIClient
> --- PASS: TestNewAPIClient (0.00s)
> === RUN   TestNewTSLAPIClient
> --- PASS: TestNewTSLAPIClient (0.00s)
> === RUN   TestNewVersionedClient
> --- PASS: TestNewVersionedClient (0.00s)
> === RUN   TestNewVersionedClientFromEnv
> --- PASS: TestNewVersionedClientFromEnv (0.00s)
> === RUN   TestNewVersionedClientFromEnvTLS
> --- PASS: TestNewVersionedClientFromEnvTLS (0.00s)
> === RUN   TestNewTLSVersionedClient
> --- PASS: TestNewTLSVersionedClient (0.00s)
> === RUN   TestNewTLSVersionedClientInvalidCA
> --- PASS: TestNewTLSVersionedClientInvalidCA (0.00s)
> === RUN   TestNewClientInvalidEndpoint
> --- PASS: TestNewClientInvalidEndpoint (0.00s)
> === RUN   TestNewClientNoSchemeEndpoint
> --- PASS: TestNewClientNoSchemeEndpoint (0.00s)
> === RUN   

Bug#880293: Pending fixes for bugs in the golang-github-fsouza-go-dockerclient package

[pkg-go-maintainers]

tag 880293 + pending
thanks

Some bugs in the golang-github-fsouza-go-dockerclient package are
closed in revision 7efea7e1c0c443d2abffd51efdec46579ef2f21a in branch
'master' by Michael Stapelberg

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-fsouza-go-dockerclient.git/commit/?id=7efea7e

Commit message:

fix FTBFS by applying upstream certificate update (Closes: #880293)

Processed: Pending fixes for bugs in the golang-github-fsouza-go-dockerclient package

[Debian Bug Tracking System]

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

> tag 880293 + pending
Bug #880293 [src:golang-github-fsouza-go-dockerclient] 
golang-github-fsouza-go-dockerclient: FTBFS: dh_auto_test: cd _build && go test 
-v -p 1 github.com/fsouza/go-dockerclient 
github.com/fsouza/go-dockerclient/testing returned exit code 1
Ignoring request to alter tags of bug #880293 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#890479: pytz can't find any time zones

[Evgeny Kapun]

Package: python3-tz
Version: 2018.3-1
Severity: grave

After upgrade to version 2018.3-1:

>>> import pytz
>>> pytz.all_timezones
[]

This is caused by this line in /usr/lib/python3/dist-packages/pytz/__init__.py:

filename = os.path.join('usr','share'
'zoneinfo', *name_parts)

So, instead of looking at /usr/share/zoneinfo/$time_zone_name, it is looking at 
(relative path) usr/sharezoneinfo/$time_zone_name (note the lack of comma after 
'share', which leads 'share' and 'zoneinfo' to be merged into a single string 
literal). This code is horribly broken, but it worked because it fell back to 
using time zone files bundled with the package. Now that these files are not 
included anymore (see bug #884079), this package doesn't work!

Processed: Re: salt-formula-kubernetes: FTBFS and Debci failure with salt 2017.7.2

[Debian Bug Tracking System]

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

> forwarded 889932 
> https://github.com/salt-formulas/salt-formula-kubernetes/pull/12
Bug #889932 [src:salt-formula-kubernetes] salt-formula-kubernetes: FTBFS and 
Debci failure with salt 2017.7.2
Set Bug forwarded-to-address to 
'https://github.com/salt-formulas/salt-formula-kubernetes/pull/12'.
> thanks
Stopping processing here.

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

Bug#889932: salt-formula-kubernetes: FTBFS and Debci failure with salt 2017.7.2

[Benjamin Drung]

forwarded 889932 
https://github.com/salt-formulas/salt-formula-kubernetes/pull/12
thanks

Hi,

the build failure is caused by missing Python 3 support. I created a
upstream pull request and backported that commit for the Debian package.
An attached patch that I applied for the Ubuntu package is attached.

On Thu, 08 Feb 2018 23:08:57 +0200 Adrian Bunk  wrote:
> Source: salt-formula-kubernetes
> Version: 2016.12.1-1
> Severity: serious
> Tags: buster sid
> 
> https://ci.debian.net/packages/s/salt-formula-kubernetes/unstable/amd6
4/
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sal
t-formula-kubernetes.html
> 
> ...
>dh_auto_test
>   make -j15 test
> make[1]: Entering directory '/build/1st/salt-formula-kubernetes-
2016.12.1'
> [ ! -d tests ] || (cd tests; ./run_tests.sh)
> /usr/bin/salt-call
> [ERROR   ] Rendering exception occurred: Jinja variable
'salt.utils.odict.OrderedDict object' has no attribute 'iteritems'
> [CRITICAL] Rendering SLS 'base:kubernetes.master.controller' failed:
Jinja variable 'salt.utils.odict.OrderedDict object' has no attribute
'iteritems'
> [ERROR   ] Rendering exception occurred: Jinja variable
'salt.utils.odict.OrderedDict object' has no attribute 'iteritems'
> [CRITICAL] Rendering SLS 'base:kubernetes.master.setup' failed: Jinja
variable 'salt.utils.odict.OrderedDict object' has no attribute
'iteritems'
> local:
> - Rendering SLS 'base:kubernetes.master.controller' failed: Jinja
variable 'salt.utils.odict.OrderedDict object' has no attribute
'iteritems'
> - Rendering SLS 'base:kubernetes.master.setup' failed: Jinja
variable 'salt.utils.odict.OrderedDict object' has no attribute
'iteritems'
> [ERROR] Execution of kubernetes.master_cluster failed
> [ERROR] Execution failed
> Makefile:22: recipe for target 'test' failed
> make[1]: *** [test] Error 1
> 
> 
-- 
Benjamin Drung
Debian & Ubuntu Developerdiff -Nru salt-formula-kubernetes-2016.12.1/debian/changelog salt-formula-kubernetes-2016.12.1/debian/changelog
--- salt-formula-kubernetes-2016.12.1/debian/changelog	2016-12-25 17:05:59.0 +0100
+++ salt-formula-kubernetes-2016.12.1/debian/changelog	2018-02-15 00:34:06.0 +0100
@@ -1,3 +1,9 @@
+salt-formula-kubernetes (2016.12.1-1ubuntu1) bionic; urgency=medium
+
+  * Support Python 3 (Closes: #889932)
+
+ -- Benjamin Drung   Thu, 15 Feb 2018 00:34:06 +0100
+
 salt-formula-kubernetes (2016.12.1-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru salt-formula-kubernetes-2016.12.1/debian/control salt-formula-kubernetes-2016.12.1/debian/control
--- salt-formula-kubernetes-2016.12.1/debian/control	2016-11-21 16:06:19.0 +0100
+++ salt-formula-kubernetes-2016.12.1/debian/control	2018-02-15 00:34:06.0 +0100
@@ -1,5 +1,6 @@
 Source: salt-formula-kubernetes
-Maintainer: PKG OpenStack 
+Maintainer: Ubuntu Developers 
+XSBC-Original-Maintainer: PKG OpenStack 
 Uploaders: Filip Pytloun ,
Ondřej Nový ,
 Section: admin
diff -Nru salt-formula-kubernetes-2016.12.1/debian/patches/0001-Support-Python-3.patch salt-formula-kubernetes-2016.12.1/debian/patches/0001-Support-Python-3.patch
--- salt-formula-kubernetes-2016.12.1/debian/patches/0001-Support-Python-3.patch	1970-01-01 01:00:00.0 +0100
+++ salt-formula-kubernetes-2016.12.1/debian/patches/0001-Support-Python-3.patch	2018-02-15 00:34:06.0 +0100
@@ -0,0 +1,204 @@
+From 8af2fa9672fd2a3f0045465b24738206e8f8d552 Mon Sep 17 00:00:00 2001
+From: Benjamin Drung 
+Date: Thu, 15 Feb 2018 00:08:00 +0100
+Subject: [PATCH] Support Python 3
+
+Bug-Debian: https://bugs.debian.org/889932
+Forwarded: https://github.com/salt-formulas/salt-formula-kubernetes/pull/12
+---
+ kubernetes/control/configmap.sls   |  4 ++--
+ kubernetes/control/job.sls |  2 +-
+ kubernetes/control/role.sls|  4 ++--
+ kubernetes/control/service.sls |  4 ++--
+ kubernetes/files/basic_auth.csv|  2 +-
+ kubernetes/files/collectd_calico_bird.conf |  2 +-
+ kubernetes/files/configmap.yml |  2 +-
+ kubernetes/files/dockershim/default.master |  2 +-
+ kubernetes/files/dockershim/default.pool   |  2 +-
+ kubernetes/files/job.yml   |  6 +++---
+ kubernetes/files/known_tokens.csv  |  2 +-
+ kubernetes/files/kube-addons/dns/kubedns-rc.yaml   |  2 +-
+ kubernetes/files/kubelet/default.master|  2 +-
+ kubernetes/files/kubelet/default.pool  |  2 +-
+ kubernetes/files/manifest/kube-apiserver.manifest  |  2 +-
+ 

Processed: Re: salt-formula-keyston: FTBFS and Debci failure with salt 2017.7.2

[Debian Bug Tracking System]

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

> forwarded 889929 
> https://github.com/salt-formulas/salt-formula-keystone/pull/21
Bug #889929 [src:salt-formula-keystone] salt-formula-keyston: FTBFS and Debci 
failure with salt 2017.7.2
Set Bug forwarded-to-address to 
'https://github.com/salt-formulas/salt-formula-keystone/pull/21'.
> thanks
Stopping processing here.

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

Bug#889929: salt-formula-keyston: FTBFS and Debci failure with salt 2017.7.2

[Benjamin Drung]

forwarded 889929 https://github.com/salt-formulas/salt-formula-keystone/pull/21
thanks

Hi,

the build failure is caused by missing Python 3 support. I created a
upstream pull request and backported that commit for the Debian package.
An attached patch that I applied for the Ubuntu package is attached.

On Thu, 08 Feb 2018 23:05:23 +0200 Adrian Bunk  wrote:
> Source: salt-formula-keystone
> Version: 2016.12.1-1
> Severity: serious
> Tags: buster sid
> 
> https://ci.debian.net/packages/s/salt-formula-keystone/unstable/amd64/
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sal
t-formula-keystone.html
> 
> ...
>dh_auto_test
>   make -j15 test
> make[1]: Entering directory '/build/1st/salt-formula-keystone-
2016.12.1'
> [ ! -d tests ] || (cd tests; ./run_tests.sh)
> /usr/bin/salt-call
> [ERROR   ] Rendering exception occurred: Jinja variable 'dict object'
has no attribute 'iteritems'
> [CRITICAL] Rendering SLS 'base:keystone.server' failed: Jinja variable
'dict object' has no attribute 'iteritems'
> local:
> - Rendering SLS 'base:keystone.server' failed: Jinja variable
'dict object' has no attribute 'iteritems'
> [ERROR] Execution of keystone.cluster failed
> [ERROR] Execution failed
> Makefile:22: recipe for target 'test' failed
> make[1]: *** [test] Error 1
> 
> 
-- 
Benjamin Drung
Debian & Ubuntu Developerdiff -Nru salt-formula-keystone-2016.12.1/debian/changelog salt-formula-keystone-2016.12.1/debian/changelog
--- salt-formula-keystone-2016.12.1/debian/changelog	2016-12-25 17:05:55.0 +0100
+++ salt-formula-keystone-2016.12.1/debian/changelog	2018-02-15 00:32:55.0 +0100
@@ -1,3 +1,9 @@
+salt-formula-keystone (2016.12.1-1ubuntu1) bionic; urgency=medium
+
+  * Support Python 3 (Closes: #889929)
+
+ -- Benjamin Drung   Thu, 15 Feb 2018 00:32:55 +0100
+
 salt-formula-keystone (2016.12.1-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru salt-formula-keystone-2016.12.1/debian/control salt-formula-keystone-2016.12.1/debian/control
--- salt-formula-keystone-2016.12.1/debian/control	2016-11-21 15:56:04.0 +0100
+++ salt-formula-keystone-2016.12.1/debian/control	2018-02-15 00:32:55.0 +0100
@@ -1,5 +1,6 @@
 Source: salt-formula-keystone
-Maintainer: PKG OpenStack 
+Maintainer: Ubuntu Developers 
+XSBC-Original-Maintainer: PKG OpenStack 
 Uploaders: Filip Pytloun ,
Ondřej Nový ,
 Section: admin
diff -Nru salt-formula-keystone-2016.12.1/debian/patches/0001-Support-Python-3.patch salt-formula-keystone-2016.12.1/debian/patches/0001-Support-Python-3.patch
--- salt-formula-keystone-2016.12.1/debian/patches/0001-Support-Python-3.patch	1970-01-01 01:00:00.0 +0100
+++ salt-formula-keystone-2016.12.1/debian/patches/0001-Support-Python-3.patch	2018-02-15 00:32:55.0 +0100
@@ -0,0 +1,177 @@
+From 5fe8041e1b29c067fb38d8b98f6f7f5ef0b239c8 Mon Sep 17 00:00:00 2001
+From: Benjamin Drung 
+Date: Wed, 14 Feb 2018 23:55:54 +0100
+Subject: [PATCH] Support Python 3
+
+json.dumps() and yaml.safe_dump() return a str object on Python 2 and Python 3.
+Therefore the unicode conversion is only needed for Python 2.
+
+Bug-Debian: https://bugs.debian.org/889929
+Forwarded: https://github.com/salt-formulas/salt-formula-keystone/pull/21
+---
+ _modules/keystone_policy.py | 13 ++---
+ keystone/client/project.sls |  4 ++--
+ keystone/client/server.sls  | 10 +-
+ keystone/control.sls|  2 +-
+ keystone/files/kilo/keystone.conf.Debian|  2 +-
+ keystone/files/liberty/keystone.conf.Debian |  2 +-
+ keystone/files/mitaka/keystone.conf.Debian  |  6 +++---
+ keystone/files/newton/keystone.conf.Debian  |  6 +++---
+ keystone/files/ocata/keystone.conf.Debian   |  6 +++---
+ keystone/files/ocata/keystone.conf.RedHat   |  6 +++---
+ keystone/files/pike/keystone.conf.Debian|  6 +++---
+ keystone/files/pike/keystone.conf.RedHat|  6 +++---
+ keystone/meta/salt.yml  |  2 +-
+ keystone/meta/sphinx.yml|  2 +-
+ keystone/server.sls | 10 +-
+ 15 files changed, 45 insertions(+), 38 deletions(-)
+
+--- a/keystone/client/project.sls
 b/keystone/client/project.sls
+@@ -20,7 +20,7 @@
+   - require:
+ - file: keystone_salt_config
+ 
+-{%- for tenant_name, tenant in client.get('tenant', {}).iteritems() %}
++{%- for tenant_name, tenant in client.get('tenant', {}).items() %}
+ 
+ keystone_tenant_{{ tenant_name }}:
+   keystone.tenant_present:
+@@ -32,7 +32,7 @@
+   - require:
+ - keystone: keystone_client_roles
+ 
+-{%- for user_name, user in tenant.get('user', {}).iteritems() %}
++{%- for user_name, user in tenant.get('user', {}).items() %}
+ 
+ keystone_{{ tenant_name }}_user_{{ 

Bug#889928: salt-formula-cinder: FTBFS and Debci failure with salt 2017.7.2

[Benjamin Drung]

forwarded 889928 https://github.com/salt-formulas/salt-formula-cinder/pull/23
thanks

Hi,

the build failure is caused by missing Python 3 support. I created a
upstream pull request and backported that commit for the Debian package.
An attached patch that I applied for the Ubuntu package is attached.

On Thu, 08 Feb 2018 23:03:43 +0200 Adrian Bunk  wrote:
> Source: salt-formula-cinder
> Version: 2016.12.1-1
> Severity: serious
> 
> https://ci.debian.net/packages/s/salt-formula-cinder/unstable/amd64/
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sal
t-formula-cinder.html
> 
> ...
>dh_auto_test
>   make -j15 test
> make[1]: Entering directory '/build/1st/salt-formula-cinder-2016.12.1'
> [ ! -d tests ] || (cd tests; ./run_tests.sh)
> /usr/bin/salt-call
> [WARNING ] Failed to open log file, do you have permission to write to
/var/log/salt/minion?
> [ERROR   ] Rendering exception occurred: Jinja variable
'salt.utils.odict.OrderedDict object' has no attribute 'iteritems'
> [CRITICAL] Rendering SLS 'base:cinder.controller' failed: Jinja
variable 'salt.utils.odict.OrderedDict object' has no attribute
'iteritems'
> [ERROR   ] Rendering exception occurred: Jinja variable
'salt.utils.odict.OrderedDict object' has no attribute 'iteritems'
> [CRITICAL] Rendering SLS 'base:cinder.volume' failed: Jinja variable
'salt.utils.odict.OrderedDict object' has no attribute 'iteritems'
> local:
> - Rendering SLS 'base:cinder.controller' failed: Jinja variable
'salt.utils.odict.OrderedDict object' has no attribute 'iteritems'
> - Rendering SLS 'base:cinder.volume' failed: Jinja variable
'salt.utils.odict.OrderedDict object' has no attribute 'iteritems'
> [ERROR] Execution of cinder.ceph_single failed
> [ERROR] Execution failed
> Makefile:22: recipe for target 'test' failed
> make[1]: *** [test] Error 1
> 
> 
-- 
Benjamin Drung
Debian & Ubuntu Developerdiff -Nru salt-formula-cinder-2016.12.1/debian/changelog salt-formula-cinder-2016.12.1/debian/changelog
--- salt-formula-cinder-2016.12.1/debian/changelog	2016-12-25 17:05:43.0 +0100
+++ salt-formula-cinder-2016.12.1/debian/changelog	2018-02-15 00:25:17.0 +0100
@@ -1,3 +1,9 @@
+salt-formula-cinder (2016.12.1-1ubuntu1) bionic; urgency=medium
+
+  * Support Python 3 (Closes: #889928)
+
+ -- Benjamin Drung   Thu, 15 Feb 2018 00:25:17 +0100
+
 salt-formula-cinder (2016.12.1-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru salt-formula-cinder-2016.12.1/debian/control salt-formula-cinder-2016.12.1/debian/control
--- salt-formula-cinder-2016.12.1/debian/control	2016-11-21 15:55:43.0 +0100
+++ salt-formula-cinder-2016.12.1/debian/control	2018-02-15 00:25:17.0 +0100
@@ -1,5 +1,6 @@
 Source: salt-formula-cinder
-Maintainer: PKG OpenStack 
+Maintainer: Ubuntu Developers 
+XSBC-Original-Maintainer: PKG OpenStack 
 Uploaders: Filip Pytloun ,
Ondřej Nový ,
 Section: admin
diff -Nru salt-formula-cinder-2016.12.1/debian/patches/0001-Support-Python-3.patch salt-formula-cinder-2016.12.1/debian/patches/0001-Support-Python-3.patch
--- salt-formula-cinder-2016.12.1/debian/patches/0001-Support-Python-3.patch	1970-01-01 01:00:00.0 +0100
+++ salt-formula-cinder-2016.12.1/debian/patches/0001-Support-Python-3.patch	2018-02-15 00:25:17.0 +0100
@@ -0,0 +1,270 @@
+From c5ea00cd7379b8a1dfcdc224c4a8de81553a8f28 Mon Sep 17 00:00:00 2001
+From: Benjamin Drung 
+Date: Wed, 14 Feb 2018 23:44:07 +0100
+Subject: [PATCH] Support Python 3
+
+Bug-Debian: https://bugs.debian.org/889928
+Forwarded: https://github.com/salt-formulas/salt-formula-cinder/pull/23
+---
+ cinder/client.sls  | 4 ++--
+ cinder/controller.sls  | 4 ++--
+ cinder/files/juno/cinder.conf.controller.Debian| 4 ++--
+ cinder/files/juno/cinder.conf.volume.Debian| 4 ++--
+ cinder/files/kilo/cinder.conf.controller.Debian| 4 ++--
+ cinder/files/kilo/cinder.conf.volume.Debian| 4 ++--
+ cinder/files/liberty/cinder.conf.controller.Debian | 4 ++--
+ cinder/files/liberty/cinder.conf.volume.Debian | 4 ++--
+ cinder/files/mitaka/cinder.conf.controller.Debian  | 4 ++--
+ cinder/files/mitaka/cinder.conf.volume.Debian  | 4 ++--
+ cinder/files/newton/cinder.conf.controller.Debian  | 4 ++--
+ cinder/files/newton/cinder.conf.volume.Debian  | 4 ++--
+ cinder/files/ocata/cinder.conf.controller.Debian   | 4 ++--
+ cinder/files/ocata/cinder.conf.volume.Debian   | 4 ++--
+ cinder/files/pike/cinder.conf.controller.Debian| 4 ++--
+ cinder/files/pike/cinder.conf.volume.Debian| 4 ++--
+ cinder/meta/sphinx.yml | 4 ++--
+ cinder/volume.sls  | 2 +-
+ 18 files changed, 35 insertions(+), 35 

Processed: Re: salt-formula-glance: FTBFS and Debci failure with salt 2017.7.2

[Debian Bug Tracking System]

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

> forwarded 889933 https://github.com/salt-formulas/salt-formula-glance/pull/23
Bug #889933 [src:salt-formula-glance] salt-formula-glance: FTBFS and Debci 
failure with salt 2017.7.2
Set Bug forwarded-to-address to 
'https://github.com/salt-formulas/salt-formula-glance/pull/23'.
> thanks
Stopping processing here.

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

Processed: Re: salt-formula-ceilometer: FTBFS and Debci failure with salt 2017.7.2

[Debian Bug Tracking System]

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

> forwarded 889927 
> https://github.com/salt-formulas/salt-formula-ceilometer/pull/6
Bug #889927 [src:salt-formula-ceilometer] salt-formula-ceilometer: FTBFS and 
Debci failure with salt 2017.7.2
Set Bug forwarded-to-address to 
'https://github.com/salt-formulas/salt-formula-ceilometer/pull/6'.
> thanks
Stopping processing here.

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

Bug#889933: salt-formula-glance: FTBFS and Debci failure with salt 2017.7.2

[Benjamin Drung]

forwarded 889933 https://github.com/salt-formulas/salt-formula-glance/pull/23
thanks

Hi,

the build failure is caused by missing Python 3 support. I created a
upstream pull request and backported that commit for the Debian package.
An attached patch that I applied for the Ubuntu package is attached.

On Thu, 08 Feb 2018 23:10:25 +0200 Adrian Bunk  wrote:
> Source: salt-formula-glance
> Version: 2016.12.1-1
> Severity: serious
> Tags: buster sid
> 
> https://ci.debian.net/packages/s/salt-formula-glance/unstable/amd64/
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sal
t-formula-glance.html
> 
> ...
>dh_auto_test
>   make -j15 test
> make[1]: Entering directory '/build/1st/salt-formula-glance-2016.12.1'
> [ ! -d tests ] || (cd tests; ./run_tests.sh)
> /usr/bin/salt-call
> [WARNING ] Failed to open log file, do you have permission to write to
/var/log/salt/minion?
> [ERROR   ] Rendering exception occurred: Jinja variable 'dict object'
has no attribute 'iteritems'
> [CRITICAL] Rendering SLS 'base:glance.server' failed: Jinja variable
'dict object' has no attribute 'iteritems'
> local:
> - Rendering SLS 'base:glance.server' failed: Jinja variable 'dict
object' has no attribute 'iteritems'
> [ERROR] Execution of glance.cluster failed
> [ERROR] Execution failed
> Makefile:22: recipe for target 'test' failed
> make[1]: *** [test] Error 1
> 
> 
-- 
Benjamin Drung
Debian & Ubuntu Developerdiff -Nru salt-formula-glance-2016.12.1/debian/changelog salt-formula-glance-2016.12.1/debian/changelog
--- salt-formula-glance-2016.12.1/debian/changelog	2016-12-25 17:05:47.0 +0100
+++ salt-formula-glance-2016.12.1/debian/changelog	2018-02-15 00:30:56.0 +0100
@@ -1,3 +1,9 @@
+salt-formula-glance (2016.12.1-1ubuntu1) bionic; urgency=medium
+
+  * Support Python 3 (Closes: #889933)
+
+ -- Benjamin Drung   Thu, 15 Feb 2018 00:30:56 +0100
+
 salt-formula-glance (2016.12.1-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru salt-formula-glance-2016.12.1/debian/control salt-formula-glance-2016.12.1/debian/control
--- salt-formula-glance-2016.12.1/debian/control	2016-11-21 15:55:48.0 +0100
+++ salt-formula-glance-2016.12.1/debian/control	2018-02-15 00:30:56.0 +0100
@@ -1,5 +1,6 @@
 Source: salt-formula-glance
-Maintainer: PKG OpenStack 
+Maintainer: Ubuntu Developers 
+XSBC-Original-Maintainer: PKG OpenStack 
 Uploaders: Filip Pytloun ,
Ondřej Nový ,
 Section: admin
diff -Nru salt-formula-glance-2016.12.1/debian/patches/0001-Support-Python-3.patch salt-formula-glance-2016.12.1/debian/patches/0001-Support-Python-3.patch
--- salt-formula-glance-2016.12.1/debian/patches/0001-Support-Python-3.patch	1970-01-01 01:00:00.0 +0100
+++ salt-formula-glance-2016.12.1/debian/patches/0001-Support-Python-3.patch	2018-02-15 00:30:56.0 +0100
@@ -0,0 +1,34 @@
+From 35de76452ffa540decd2b158bb33a42cebf3314d Mon Sep 17 00:00:00 2001
+From: Benjamin Drung 
+Date: Wed, 14 Feb 2018 23:54:30 +0100
+Subject: [PATCH] Support Python 3
+
+Bug-Debian: https://bugs.debian.org/889933
+Forwarded: https://github.com/salt-formulas/salt-formula-glance/pull/23
+---
+ _states/glanceng.py| 2 +-
+ glance/client.sls  | 4 ++--
+ glance/files/_backends/_swift.conf | 2 +-
+ glance/server.sls  | 4 ++--
+ 4 files changed, 6 insertions(+), 6 deletions(-)
+
+--- a/glance/server.sls
 b/glance/server.sls
+@@ -121,7 +121,7 @@
+ 
+ {%- endfor %}
+ 
+-{%- for image_name, image in server.get('image', {}).iteritems() %}
++{%- for image_name, image in server.get('image', {}).items() %}
+ 
+ glance_download_{{ image_name }}:
+   cmd.run:
+@@ -144,7 +144,7 @@
+ 
+ {%- if server.policy is defined %}
+ 
+-{%- for key, policy in server.policy.iteritems() %}
++{%- for key, policy in server.policy.items() %}
+ 
+ policy_{{ key }}:
+   file.replace:
diff -Nru salt-formula-glance-2016.12.1/debian/patches/series salt-formula-glance-2016.12.1/debian/patches/series
--- salt-formula-glance-2016.12.1/debian/patches/series	1970-01-01 01:00:00.0 +0100
+++ salt-formula-glance-2016.12.1/debian/patches/series	2018-02-15 00:30:35.0 +0100
@@ -0,0 +1 @@
+0001-Support-Python-3.patch

Processed: Re: salt-formula-cinder: FTBFS and Debci failure with salt 2017.7.2

[Debian Bug Tracking System]

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

> forwarded 889928 https://github.com/salt-formulas/salt-formula-cinder/pull/23
Bug #889928 [src:salt-formula-cinder] salt-formula-cinder: FTBFS and Debci 
failure with salt 2017.7.2
Set Bug forwarded-to-address to 
'https://github.com/salt-formulas/salt-formula-cinder/pull/23'.
> thanks
Stopping processing here.

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

Bug#889927: salt-formula-ceilometer: FTBFS and Debci failure with salt 2017.7.2

[Benjamin Drung]

forwarded 889927 https://github.com/salt-formulas/salt-formula-ceilometer/pull/6
thanks

Hi,

the build failure is caused by missing Python 3 support. I created a
upstream pull request and backported that commit for the Debian package.
An attached patch that I applied for the Ubuntu package is attached.

On Thu, 08 Feb 2018 22:58:19 +0200 Adrian Bunk  wrote:
> Source: salt-formula-ceilometer
> Version: 2016.12.1-1
> Severity: serious
> Tags: buster sid
> 
> https://ci.debian.net/packages/s/salt-formula-ceilometer/unstable/amd6
4/
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sal
t-formula-ceilometer.html
> 
> ...
>dh_auto_test
>   make -j15 test
> make[1]: Entering directory '/build/1st/salt-formula-ceilometer-
2016.12.1'
> [ ! -d tests ] || (cd tests; ./run_tests.sh)
> /usr/bin/salt-call
> [ERROR   ] Rendering exception occurred: Jinja variable
'salt.utils.odict.OrderedDict object' has no attribute 'iteritems'
> [CRITICAL] Rendering SLS 'base:ceilometer.agent' failed: Jinja
variable 'salt.utils.odict.OrderedDict object' has no attribute
'iteritems'
> local:
> - Rendering SLS 'base:ceilometer.agent' failed: Jinja variable
'salt.utils.odict.OrderedDict object' has no attribute 'iteritems'
> [ERROR] Execution of ceilometer.agent_cluster failed
> [ERROR] Execution failed
> Makefile:22: recipe for target 'test' failed
> make[1]: *** [test] Error 1
> 
> 
-- 
Benjamin Drung
Debian & Ubuntu Developerdiff -Nru salt-formula-ceilometer-2016.12.1/debian/changelog salt-formula-ceilometer-2016.12.1/debian/changelog
--- salt-formula-ceilometer-2016.12.1/debian/changelog	2016-12-25 17:05:26.0 +0100
+++ salt-formula-ceilometer-2016.12.1/debian/changelog	2018-02-15 00:18:13.0 +0100
@@ -1,3 +1,9 @@
+salt-formula-ceilometer (2016.12.1-1ubuntu1) bionic; urgency=medium
+
+  * Support Python 3 (Closes: #889927)
+
+ -- Benjamin Drung   Thu, 15 Feb 2018 00:18:13 +0100
+
 salt-formula-ceilometer (2016.12.1-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru salt-formula-ceilometer-2016.12.1/debian/control salt-formula-ceilometer-2016.12.1/debian/control
--- salt-formula-ceilometer-2016.12.1/debian/control	2016-11-21 15:55:36.0 +0100
+++ salt-formula-ceilometer-2016.12.1/debian/control	2018-02-15 00:18:13.0 +0100
@@ -1,5 +1,6 @@
 Source: salt-formula-ceilometer
-Maintainer: PKG OpenStack 
+Maintainer: Ubuntu Developers 
+XSBC-Original-Maintainer: PKG OpenStack 
 Uploaders: Filip Pytloun ,
Ondřej Nový ,
 Section: admin
diff -Nru salt-formula-ceilometer-2016.12.1/debian/patches/0001-Support-Python-3.patch salt-formula-ceilometer-2016.12.1/debian/patches/0001-Support-Python-3.patch
--- salt-formula-ceilometer-2016.12.1/debian/patches/0001-Support-Python-3.patch	1970-01-01 01:00:00.0 +0100
+++ salt-formula-ceilometer-2016.12.1/debian/patches/0001-Support-Python-3.patch	2018-02-15 00:18:13.0 +0100
@@ -0,0 +1,227 @@
+From d473ad28bc38e2152f77c8b50133e65e458776d1 Mon Sep 17 00:00:00 2001
+From: Benjamin Drung 
+Date: Tue, 13 Feb 2018 23:39:58 +0100
+Subject: [PATCH] Support Python 3
+
+Bug-Debian: https://bugs.debian.org/889927
+Forwarded: https://github.com/salt-formulas/salt-formula-ceilometer/pull/6
+---
+ ceilometer/agent.sls   | 2 +-
+ ceilometer/files/juno/ceilometer-server.conf.Debian| 2 +-
+ ceilometer/files/juno/pipeline.yaml| 8 
+ ceilometer/files/kilo/ceilometer-server.conf.Debian| 2 +-
+ ceilometer/files/kilo/pipeline.yaml| 8 
+ ceilometer/files/liberty/ceilometer-server.conf.Debian | 2 +-
+ ceilometer/files/liberty/pipeline.yaml | 8 
+ ceilometer/files/mitaka/ceilometer-server.conf.Debian  | 2 +-
+ ceilometer/files/mitaka/compute_pipeline.yaml  | 2 +-
+ ceilometer/files/mitaka/pipeline.yaml  | 2 +-
+ ceilometer/files/newton/compute_pipeline.yaml  | 2 +-
+ ceilometer/files/newton/pipeline.yaml  | 2 +-
+ ceilometer/files/ocata/compute_pipeline.yaml   | 2 +-
+ ceilometer/files/ocata/pipeline.yaml   | 2 +-
+ ceilometer/server.sls  | 4 ++--
+ 15 files changed, 25 insertions(+), 25 deletions(-)
+
+--- a/ceilometer/agent.sls
 b/ceilometer/agent.sls
+@@ -12,7 +12,7 @@
+   - require:
+ - pkg: ceilometer_agent_packages
+ 
+-{%- for publisher_name, publisher in agent.get('publisher', {}).iteritems() %}
++{%- for publisher_name, publisher in agent.get('publisher', {}).items() %}
+ 
+ {%- if publisher_name != "default" %}
+ 
+--- a/ceilometer/files/juno/ceilometer-server.conf.Debian
 b/ceilometer/files/juno/ceilometer-server.conf.Debian
+@@ -928,7 +928,7 @@
+ #metering_secret=change this or 

Bug#890406: linux-image-4.14.0-0.bpo.3-amd64: Installing kernel fails to build broadcom-sta

[Ben Hutchings]

On Wed, 2018-02-14 at 20:19 +0100, Steve wrote:
> Hi,
> 
> Le 14-02-2018, à 18:52:16 +, Ben Hutchings a écrit :
> 
> > If an external module is not compatible with a new kernel version, that
> > is not a bug in the new kernel version.
> 
> Which I perfectly understand. 
> 
> But as a user, I'm stuck with a broken system (no wireless) after
> choosing to update my kernel by regular means. What should be my next
> steps?

Boot the old kernel version.

Ben.

> > As it happens, this has just been fixed in a new version of
> > broadcom-sta in unstable.
> 
> Good to hear that. I'll give it a try even though I'm running stable.
> 
> Thanks for the quick answer.
> 
> Steve
-- 
Ben Hutchings
Beware of programmers who carry screwdrivers. - Leonard Brandwein



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

Bug#890467: sssd: upgrade from 1.16.0-3 to 1.16.0-5 causes total failure of sssd to work, can not log into machine

[Daniel Lakeland]

Package: sssd
Version: 1.16.0-3
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

   * What led up to the situation?

I had a working system with sssd providing my users and authentication
using an openldap and kerberos backend. I upgraded from 1.16.0-3 to
1.16.0-5 and the system could not find any users or allow anyone to
login.


I downgraded sssd an associated packages to 1.16.0-3 and rebooted, all 
services were fully restored


Please note, the problem also occurred when I tried to install a brand
new machine based on stable, and then dist-upgraded it to current
testing, which pulled in sssd 1.16.0-5


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (750, 'testing'), (500, 'unstable'), (500, 'stable'), 
(102, 'experimental')

Architecture: amd64 (x86_64)

Kernel: Linux 4.14.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages sssd depends on:
ii  python3-sss  1.16.0-3
ii  sssd-ad  1.16.0-3
ii  sssd-common  1.16.0-3
ii  sssd-ipa 1.16.0-3
ii  sssd-krb5    1.16.0-3
ii  sssd-ldap    1.16.0-3
ii  sssd-proxy   1.16.0-3

sssd recommends no packages.

sssd suggests no packages.

-- no debconf information

Bug#890465: pioneers: Depends on libgnome

[Jeremy Bicha]

Package: pioneers
Version: 15.4-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libgnome
Tags: sid buster

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

pioneers Build-Depends on libgnome2-dev (which adds a libgnome2-0
Depends). That seems wrong because libgnome is a gtk2 library but
pioneers is built with gtk3.

Without that build dependency, pioneers doesn't offer user help which
seems really wrong.

[1] https://lists.debian.org/debian-devel/2018/02/msg00169.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Processed: Raising severity of libgnome perl rdepends bugs

[Debian Bug Tracking System]

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

> severity 870421 serious
Bug #870421 [libgnome2-canvas-perl] libgnome2-canvas-perl: Remove 
libgnome2-canvas-perl during the Buster cycle
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Bug#868404: libswt-gnome-gtk-3-jni: Raising severity of libgnome rdepends bugs

[Jeremy Bicha]

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. As part of this process, I
am now raising the severity of this bug.

libswt-gnome-gtk3-jni has only 2 rdepends in Debian: eclipse-rcp and
zekr. eclipse-rcp only recommends libswt-gnom3-gtk3-jni and zekr was
removed from Testing last year because it depends on the old
webkitgtk. So maybe this bug can be fixed by dropping the
libswt-gnome-gtk3-jni package.

libswt-gnome-gtk-4-jni still has no rdepends in Debian.

[1] https://lists.debian.org/debian-devel/2018/02/msg00169.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#890459: orbit2: Don't release with Debian Buster

[Jeremy Bicha]

Package: orbit2
Version: 1:2.14.19-4
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs
Tags: sid buster

orbit2 is unmaintained and is only kept in Debian because it's used by
obsolete libgnome libraries that the Debian GNOME team is trying to
remove from Debian Buster. [1] Therefore, I am filing this bug so that
this package can be removed soon.

[1] https://lists.debian.org/debian-devel/2018/02/msg00169.html

Thanks,
Jeremy Bicha

Processed: oregano: Raising severity of libgnome rdepends bugs

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #868401 [src:oregano] oregano: Please drop the (build-)dependency against 
gnome-vfs
Severity set to 'serious' from 'important'

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

Bug#890457: latrace FTBFS with flex 2.6.4-2

[Adrian Bunk]

Source: latrace
Version: 0.5.11-1
Severity: serious
Tags: buster sid

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

...
  LD latrace
src/config-flex.o: In function `lt_config_lex':
latrace_0.5.11-1/:1481: undefined reference to `lt_config_wrap'
collect2: error: ld returned 1 exit status
make[1]: *** [src/Makefile:87: latrace] Error 1

Bug#890456: pike7.8-gtk: Depends on old GNOME libraries

[Jeremy Bicha]

Package: pike7.8-gtk
Version: 7.8.866-8
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libgnomecanvas libgnomeui libgnome gtksourceview2
Tags: sid buster

As announced [1], we do not intend to release Debian 10 "Buster" with
the old libgnome (and related) libraries. These libraries have been
deprecated and unmaintained for several years.

pike7.8-gtk depends on these:

- libgnome-2-0
- libgnomecanvas2-0
- libgnomeui-0
- libgtksourceview2.0-0

As far as I can tell, Pike doesn't offer GTK3 support yet. I think
you're going to need to drop this package.

See also https://bugs.debian.org/885673 for Pike 8.

[1] https://lists.debian.org/debian-devel/2018/02/msg00169.html

On behalf of the Debian GNOME team,
Jeremy Bicha

Processed: zapping: Raising severity of libgnome rdepends bugs

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #886188 [src:zapping] zapping: Depends on gconf
Severity set to 'serious' from 'important'

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

Processed: zapping: Raising severity of libgnome rdepends bugs

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #886187 [src:zapping] zapping: Depends on libgnomeui
Severity set to 'serious' from 'important'

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

Processed: Raising severity of libgnome perl rdepends bugs

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #889108 [libgtk2-appindicator-perl] libgtk2-appindicator-perl: Remove 
libgtk2-appindicator-perl during the Buster cycle
Severity set to 'serious' from 'important'

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

Processed: Raising severity of libgnome perl rdepends bugs

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #868398 [src:libgnome2-vfs-perl] libgnome2-vfs-perl: Please drop the 
(build-)dependency against gnome-vfs
Severity set to 'serious' from 'important'

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

Processed: Raising severity of libgnome perl rdepends bugs

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #870418 [shutter] shutter: Depends on obsolete libgnome2-vfs-perl that will 
go away during the Buster cycle
Severity set to 'serious' from 'important'

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

Processed: Raising severity of libgnome perl rdepends bugs

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #870423 [libgnome2-wnck-perl] libgnome2-wnck-perl: Remove 
libgnome2-wnck-perl during the Buster cycle
Severity set to 'serious' from 'normal'

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

Processed: Raising severity of libgnome perl rdepends bugs

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #885811 [src:libgtk2-unique-perl] libgtk2-unique-perl: Remove 
libgtk2-unique-perl during the Buster cycle
Severity set to 'serious' from 'important'

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

Processed: Raising severity of libgnome perl rdepends bugs

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #868395 [src:libgnome2-perl] libgnome2-perl: Please drop the 
(build-)dependency against gnome-vfs
Severity set to 'serious' from 'important'

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

Processed: Raising severity of libgnome perl rdepends bugs

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #870422 [libgnome2-gconf-perl] libgnome2-gconf-perl: Remove 
libgnome2-gconf-perl during the Buster cycle
Severity set to 'serious' from 'normal'

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

Processed: gnome-commander: Raising severity of libgnome rdepends bugs

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #868417 [src:gnome-commander] gnome-commander: Please drop the 
(build-)dependency against gnome-vfs
Severity set to 'serious' from 'important'

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

Processed: gbonds: Raising severity of libgnome rdepends

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #886080 [src:gbonds] gbonds: Depends on gconf
Severity set to 'serious' from 'important'

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

Processed: ggcov: Raising severity of libgnome rdepends bugs

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #885736 [src:ggcov] ggcov: Depends on libgnomeui
Severity set to 'serious' from 'important'

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

Processed: gbonds: Raising severity of libgnome rdepends

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #868413 [src:gbonds] gbonds: Please drop the (build-)dependency against 
gnome-vfs
Severity set to 'serious' from 'important'

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

Bug#884098: marked as done (agenda.app: Cannot create new task or appointment)

[Debian Bug Tracking System]

Your message dated Wed, 14 Feb 2018 21:17:08 +
with message-id 
and subject line Bug#884098: fixed in agenda.app 0.42.2-1+deb9u1
has caused the Debian Bug report #884098,
regarding agenda.app: Cannot create new task or appointment
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.)


-- 
884098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884098
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: agenda.app
Version: 0.42.2-1+b7
Severity: grave
Justification: renders package unusable
Control: fixed -1 0.44-1

Creating a new task or appointment is impossible; an exception occurs:

2017-12-11 13:40:53.671 SimpleAgenda[2016:2016] Problem posting notification: 
 NAME:NSInvalidArgumentException 
REASON:TaskEditor(instance) does not recognize document INFO:(null)
2017-12-11 13:41:10.333 SimpleAgenda[2016:2016] Problem posting notification: 
 NAME:NSInvalidArgumentException 
REASON:AppointmentEditor(instance) does not recognize document INFO:(null)

Much to my regret I've let this bug sneak into a Debian stable
release.  Shame on me.

-- System Information:
Debian Release: 9.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable')
Architecture: i386 (i686)

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

Versions of packages agenda.app depends on:
ii  gnustep-back0.25   0.25.0-2
ii  gnustep-common [gnustep-fslayout-fhs]  2.6.8-2.1
ii  gnustep-gui-runtime0.25.0-4+b1
ii  libaddresses0  0.4.8-2+b2
ii  libc6  2.24-11+deb9u1
ii  libgcc11:6.3.0-18
ii  libgnustep-base1.241.24.9-3.1
ii  libgnustep-gui0.25 0.25.0-4+b1
ii  libical2   2.0.0-0.5+b1
ii  libobjc4   6.3.0-18
ii  libuuid1   2.29.2-1

agenda.app recommends no packages.

agenda.app suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: agenda.app
Source-Version: 0.42.2-1+deb9u1

We believe that the bug you reported is fixed in the latest version of
agenda.app, 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.
Yavor Doganov  (supplier of updated agenda.app 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: Mon, 25 Dec 2017 22:09:00 +0200
Source: agenda.app
Binary: agenda.app
Architecture: source
Version: 0.42.2-1+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian GNUstep maintainers 

Changed-By: Yavor Doganov 
Description:
 agenda.app - Calendar manager for GNUstep
Closes: 884098
Changes:
 agenda.app (0.42.2-1+deb9u1) stretch; urgency=medium
 .
   * debian/patches/fix-editors-exception.patch: New, fixes creation of
 tasks and appointments (Closes: #884098).
   * debian/patches/series: New file.
Checksums-Sha1:
 ca74a02fc4ad01283b1944eb473e92e19705cf7b 2079 agenda.app_0.42.2-1+deb9u1.dsc
 a634fd5476a7e4866233303dce445249aca83c64 4964 
agenda.app_0.42.2-1+deb9u1.debian.tar.xz
 768d03c2f3df22f3d630b4066c10b3a0e47d1ee8 6219 
agenda.app_0.42.2-1+deb9u1_source.buildinfo
Checksums-Sha256:
 bc9f2de49807a2b0337b125b2004b157cb5205ac5898cd1b336c13da1b8995ee 2079 
agenda.app_0.42.2-1+deb9u1.dsc
 c5625328215958da01584e48b28b44fadb921756fa83d0c8cae46d1bad73b670 4964 
agenda.app_0.42.2-1+deb9u1.debian.tar.xz
 dcb72395cbdc83bb42f8b9f11f3300e2fdfd0a00ebb004b27da0ad0dfebedf6a 6219 
agenda.app_0.42.2-1+deb9u1_source.buildinfo
Files:
 bb5023690d701545ee989841075a2a7d 2079 gnustep optional 
agenda.app_0.42.2-1+deb9u1.dsc
 5728e14ef7687eb82dd3c00c02202690 4964 gnustep optional 
agenda.app_0.42.2-1+deb9u1.debian.tar.xz
 449bc8b60d6755dad043228e54834b27 6219 gnustep 

Bug#883394: marked as done (libc6: keep /etc/ld.so.nohwcap after upgrade, breaking Nvidia GLX)

[Debian Bug Tracking System]

Your message dated Wed, 14 Feb 2018 21:17:19 +
with message-id 
and subject line Bug#883394: fixed in glibc 2.24-11+deb9u3
has caused the Debian Bug report #883394,
regarding libc6: keep /etc/ld.so.nohwcap after upgrade, breaking Nvidia GLX
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.)


-- 
883394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883394
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: 2.24-11+deb9u2
Severity: important

This seems to be a regression in the stretch-proposed-updates release
2.24.11+deb9u2, at least I did not observe it when going
jessie->stretch, or in the 2.24.11->2.24.11+deb9u1 update.

And yes, I am sure the file was created by 2.24.11+deb9u2, since I
noticed it due to etckeeper.

Fix:
  run dpkg-reconfigure libc6:amd64 after the update.  It detects that
  /etc/ld.so.nohwcap is not needed anymore, and unlinks it.


Update details:
  aptitude and dpkg logs attached.


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

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

Versions of packages libc6:amd64 depends on:
ii  libgcc1  1:6.3.0-18

libc6:amd64 recommends no packages.

Versions of packages libc6:amd64 suggests:
ii  debconf [debconf-2.0]  1.5.61
ii  glibc-doc  2.24-11+deb9u2
ii  libc-l10n  2.24-11+deb9u2
ii  locales2.24-11+deb9u2

-- debconf information:
  glibc/upgrade: true
* glibc/restart-services: spamassassin samba postfix mysql cups cron atd
  glibc/disable-screensaver:
  glibc/kernel-not-supported:
* libraries/restart-without-asking: true
  glibc/kernel-too-old:
  glibc/restart-failed:

-- 
  Henrique Holschuh

  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.24-11+deb9u3

We believe that the bug you reported is fixed in the latest version of
glibc, 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.
Aurelien Jarno  (supplier of updated glibc 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: Sun, 14 Jan 2018 11:39:44 +0100
Source: glibc
Binary: libc-bin libc-dev-bin libc-l10n glibc-doc glibc-source locales 
locales-all nscd multiarch-support libc6 libc6-dev libc6-dbg libc6-pic 
libc6-udeb libc6.1 libc6.1-dev libc6.1-dbg libc6.1-pic libc6.1-udeb libc0.3 
libc0.3-dev libc0.3-dbg libc0.3-pic libc0.3-udeb libc0.1 libc0.1-dev 
libc0.1-dbg libc0.1-pic libc0.1-udeb libc6-i386 libc6-dev-i386 libc6-sparc 
libc6-dev-sparc libc6-sparc64 libc6-dev-sparc64 libc6-s390 libc6-dev-s390 
libc6-amd64 libc6-dev-amd64 libc6-powerpc libc6-dev-powerpc libc6-ppc64 
libc6-dev-ppc64 libc6-mips32 libc6-dev-mips32 libc6-mipsn32 libc6-dev-mipsn32 
libc6-mips64 libc6-dev-mips64 libc0.1-i386 libc0.1-dev-i386 libc6-x32 
libc6-dev-x32 libc6-xen libc0.3-xen libc6.1-alphaev67 libc0.1-i686 libc0.3-i686 
libc6-i686
Architecture: source
Version: 2.24-11+deb9u3
Distribution: stretch
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Description:
 glibc-doc  - GNU C Library: Documentation
 glibc-source - GNU C Library: sources
 libc-bin   - GNU C Library: Binaries
 libc-dev-bin - GNU C Library: Development binaries
 libc-l10n  - GNU C Library: localization files
 libc0.1- GNU C Library: Shared libraries
 libc0.1-dbg - GNU C Library: detached debugging symbols
 libc0.1-dev - GNU C Library: Development Libraries and Header Files
 libc0.1-dev-i386 - GNU C Library: 32bit development libraries 

Bug#883705: marked as done (libc6: keep /etc/ld.so.nohwcap after upgrade, breaking Nvidia GLX)

[Debian Bug Tracking System]

Your message dated Wed, 14 Feb 2018 21:17:19 +
with message-id 
and subject line Bug#883394: fixed in glibc 2.24-11+deb9u3
has caused the Debian Bug report #883394,
regarding libc6: keep /etc/ld.so.nohwcap after upgrade, breaking Nvidia GLX
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.)


-- 
883394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883394
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Severity: critical
Justification: breaks the whole system

Hi,

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

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

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

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

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

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

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



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

Kernel: Linux 4.9.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.24-11+deb9u3

We believe that the bug you reported is fixed in the latest version of
glibc, 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.
Aurelien Jarno  (supplier of updated glibc 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: Sun, 14 Jan 2018 11:39:44 +0100
Source: glibc
Binary: libc-bin libc-dev-bin libc-l10n glibc-doc glibc-source locales 
locales-all nscd multiarch-support libc6 libc6-dev libc6-dbg libc6-pic 
libc6-udeb libc6.1 libc6.1-dev libc6.1-dbg libc6.1-pic libc6.1-udeb libc0.3 
libc0.3-dev libc0.3-dbg libc0.3-pic libc0.3-udeb libc0.1 libc0.1-dev 
libc0.1-dbg libc0.1-pic libc0.1-udeb libc6-i386 libc6-dev-i386 libc6-sparc 
libc6-dev-sparc libc6-sparc64 libc6-dev-sparc64 libc6-s390 libc6-dev-s390 
libc6-amd64 libc6-dev-amd64 libc6-powerpc libc6-dev-powerpc libc6-ppc64 
libc6-dev-ppc64 libc6-mips32 libc6-dev-mips32 libc6-mipsn32 libc6-dev-mipsn32 
libc6-mips64 libc6-dev-mips64 libc0.1-i386 libc0.1-dev-i386 libc6-x32 
libc6-dev-x32 libc6-xen libc0.3-xen libc6.1-alphaev67 libc0.1-i686 libc0.3-i686 
libc6-i686
Architecture: source
Version: 2.24-11+deb9u3
Distribution: stretch
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Description:
 glibc-doc  - GNU C Library: Documentation
 glibc-source - GNU C Library: sources
 libc-bin   - GNU C Library: Binaries
 libc-dev-bin - GNU C Library: 

Bug#881438: marked as done (activity-log-manager: Missing dependency against python-zeitgeist)

[Debian Bug Tracking System]

Your message dated Wed, 14 Feb 2018 21:17:07 +
with message-id 
and subject line Bug#881438: fixed in activity-log-manager 0.8.0-1.2~deb9u1
has caused the Debian Bug report #881438,
regarding activity-log-manager: Missing dependency against python-zeitgeist
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.)


-- 
881438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881438
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: activity-log-manager
Version: 0.8.0-1.1
Severity: serious
File: /usr/bin/activity-log-manager

Hi,

It seems that activity-log-manager is missing a dependecy against 
python-zeitgeist

/usr/bin/activity-log-manager fails to start if the package is not
installed

Regards,

Laurent Bigonville

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

Kernel: Linux 4.14.0-rc8+ (SMP w/8 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages activity-log-manager depends on:
ii  python  2.7.14-1
ii  python-cairo1.8.8-2.2
ii  python-gtk2 2.24.0-5.1
ii  zeitgeist-core  1.0-0.1

activity-log-manager recommends no packages.

activity-log-manager suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: activity-log-manager
Source-Version: 0.8.0-1.2~deb9u1

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated activity-log-manager 
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: Sun, 14 Jan 2018 00:57:20 +0100
Source: activity-log-manager
Binary: activity-log-manager
Architecture: source
Version: 0.8.0-1.2~deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Siegfried-Angel Gevatter Pujals 
Changed-By: Andreas Beckmann 
Description:
 activity-log-manager - blacklist configuration user interface for Zeitgeist
Closes: 881438
Changes:
 activity-log-manager (0.8.0-1.2~deb9u1) stretch; urgency=medium
 .
   * Non-maintainer upload.
   * Rebuild for stretch.
 .
 activity-log-manager (0.8.0-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add dependency against python-zeitgeist (Closes: #881438)
Checksums-Sha1:
 c794a62ad59ffae50248e64d06d6f9b44816b881 1936 
activity-log-manager_0.8.0-1.2~deb9u1.dsc
 a4e37e9a1db13bbc5f4586f38eee0474ded3e4e5 1788 
activity-log-manager_0.8.0-1.2~deb9u1.debian.tar.xz
 2e963d012c5d84f82810606eb80fa7ceb192492c 6637 
activity-log-manager_0.8.0-1.2~deb9u1_source.buildinfo
Checksums-Sha256:
 5fbf760dea7dbf9ecf9569dc4aeff157ddb9bbe80808382f8c0f8181be3c0773 1936 
activity-log-manager_0.8.0-1.2~deb9u1.dsc
 c37b236d6c7a23d68d2e5714c19ccf5c8e7b3ec2765789a2629c822658764184 1788 
activity-log-manager_0.8.0-1.2~deb9u1.debian.tar.xz
 1691a4c2349d90f6dee804c927f198ae3e9cf65cba7b2fb2fbc126b2d08845ed 6637 
activity-log-manager_0.8.0-1.2~deb9u1_source.buildinfo
Files:
 2793f7369e875bb622319130775c0300 1936 utils optional 
activity-log-manager_0.8.0-1.2~deb9u1.dsc
 81eeb1f9d7b8e3a66f1d099597906852 1788 utils optional 
activity-log-manager_0.8.0-1.2~deb9u1.debian.tar.xz
 182389300edb0a6f0255c949f8b08728 6637 utils optional 
activity-log-manager_0.8.0-1.2~deb9u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAlpanZMQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCOt/D/4vbqr49ZBN1HoL3VMe+bvmrDTcJtAtm7o5
Z5s9TLo/idapcCnttBzs93o0XDyw30eW1+AeRah9qfFp6sre1C1vk6Wwc21yWwYd
H0awqEWIaHMKSsh0NA3viJtulYUhEovKYNj1qbn1xM58J1pu1R8PDbpfCd3FLanH
LxPRvyEed6udZTarqMcHgj1fs0neloWSbhDUyS5iGEX0MfU324Mffd8XICE7bbwC
cKAzzsRNjjJqBPeiqrBnvQcn6JaAVA20cuvjyBBOCR1qg+nWBFkdOuV5bju7hvKJ

Bug#890000: marked as done (exim4: CVE-2018-6789: Buffer overflow in an utility function)

[Debian Bug Tracking System]

Your message dated Wed, 14 Feb 2018 21:17:09 +
with message-id 
and subject line Bug#89: fixed in exim4 4.89-2+deb9u3
has caused the Debian Bug report #89,
regarding exim4: CVE-2018-6789: Buffer overflow in an utility function
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.)


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

Hi,

the following vulnerability was published for exim4 (actually not
really the details, filling the bug for having a tracking bug in the
BTS).

CVE-2018-6789[0]:
| An issue was discovered in the SMTP listener in Exim 4.90 and earlier.
| By sending a handcrafted message, a buffer overflow may happen in a
| specific function. This can be used to execute code remotely.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-6789
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6789
[1] https://exim.org/static/doc/security/CVE-2018-6789.txt

Please adjust the affected versions in the BTS as needed, when issue
goes public with details and possibly adjust severity.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: exim4
Source-Version: 4.89-2+deb9u3

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated exim4 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, 10 Feb 2018 09:26:05 +0100
Source: exim4
Binary: exim4-base exim4-config exim4-daemon-light exim4 exim4-daemon-heavy 
eximon4 exim4-dbg exim4-daemon-light-dbg exim4-daemon-heavy-dbg exim4-dev
Architecture: source
Version: 4.89-2+deb9u3
Distribution: stretch-security
Urgency: high
Maintainer: Exim4 Maintainers 
Changed-By: Salvatore Bonaccorso 
Closes: 89
Description: 
 exim4  - metapackage to ease Exim MTA (v4) installation
 exim4-base - support files for all Exim MTA (v4) packages
 exim4-config - configuration for the Exim MTA (v4)
 exim4-daemon-heavy - Exim MTA (v4) daemon with extended features, including 
exiscan-ac
 exim4-daemon-heavy-dbg - debugging symbols for the Exim MTA "heavy" daemon
 exim4-daemon-light - lightweight Exim MTA (v4) daemon
 exim4-daemon-light-dbg - debugging symbols for the Exim MTA "light" daemon
 exim4-dbg  - debugging symbols for the Exim MTA (utilities)
 exim4-dev  - header files for the Exim MTA (v4) packages
 eximon4- monitor application for the Exim MTA (v4) (X11 interface)
Changes:
 exim4 (4.89-2+deb9u3) stretch-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * Fix base64d() buffer size (CVE-2018-6789) (Closes: #89)
Checksums-Sha1: 
 dbad576884736adda0d719408224b29b0ebe1264 2973 exim4_4.89-2+deb9u3.dsc
 6c7133297ea15795a2377d30de6bd52a600df553 449860 
exim4_4.89-2+deb9u3.debian.tar.xz
Checksums-Sha256: 
 3f289571d21fe4c8febd17e1c6e2e886f089e842ee2dfb090752ce4ba405b495 2973 
exim4_4.89-2+deb9u3.dsc
 18be4af54197b369c5c1ce19a3c0a1ad7699252d90f837e620a7c592c6842a66 449860 
exim4_4.89-2+deb9u3.debian.tar.xz
Files: 
 36cfb76d9cae7b72a6053bd1af1cf1d6 2973 mail standard exim4_4.89-2+deb9u3.dsc
 a077b49a39af9dbf31d9e6ea70eaa493 449860 mail standard 
exim4_4.89-2+deb9u3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAlp+9w5fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EjUIP/jihWCdQ0yGUnQDuZDZyEB+9FLLonC3x
6Xsgo9p+MPw/wp12z2c2u0bmB+s+Y1KbEukCrIDndzfn5jUUvgfe8PKHAalR1VWY
QOw0AhqMWtLIWoW1dg39eoEPhvEy/92WuYsUYvzjpAC58hEkXPq9qb1sFDFk/n/I

Bug#888201: marked as done (mailman: CVE-2018-5950)

[Debian Bug Tracking System]

Your message dated Wed, 14 Feb 2018 21:17:20 +
with message-id 
and subject line Bug#888201: fixed in mailman 1:2.1.23-1+deb9u2
has caused the Debian Bug report #888201,
regarding mailman: CVE-2018-5950
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.)


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

Hi,

the following vulnerability was published for mailman, filling for now
as grave since no details on the impact nor the fix is public, cf.
[1], where it states:

> An XSS vulnerability in the Mailman 2.1 web UI has been reported and
> assigned CVE-2018-5950 which is not yet public.
> 
> I plan to release Mailman 2.1.26 along with a patch for older releases
> to fix this issue on Feb 4, 2018. At that time, full details of the
> vulnerability will be public.
> 
> This is advance notice of the upcoming release and patch for those that
> need a week or two to prepare. The patch will be small and only affect
> one module.

CVE-2018-5950[0]:
| Cross-site scripting (XSS) vulnerability in the web UI in Mailman
| before 2.1.26 allows remote attackers to inject arbitrary web script
| or HTML via unspecified vectors.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-5950
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5950
[1] https://www.mail-archive.com/mailman-users@python.org/msg70375.html

Please adjust the affected versions in the BTS as needed, once more
details are known.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: mailman
Source-Version: 1:2.1.23-1+deb9u2

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

Debian distribution maintenance software
pp.
Thijs Kinkhorst  (supplier of updated mailman 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, 08 Feb 2018 07:54:28 +0100
Source: mailman
Binary: mailman
Architecture: source amd64
Version: 1:2.1.23-1+deb9u2
Distribution: stretch-security
Urgency: high
Maintainer: Mailman for Debian 
Changed-By: Thijs Kinkhorst 
Description:
 mailman- Powerful, web-based mailing list manager
Closes: 888201
Changes:
 mailman (1:2.1.23-1+deb9u2) stretch-security; urgency=high
 .
   * CVE-2018-5950: XSS and information leak in user options.
 (Closes: #888201)
Checksums-Sha1:
 a4fd22e8751bfa4e6a824d0f23536f1d2eff9a9a 1800 mailman_2.1.23-1+deb9u2.dsc
 bee329ca989fc4e217fc5cdb814a1a4ecde79615 9290881 mailman_2.1.23.orig.tar.gz
 44ca0103fa0ba36632be16b9cafe362d72897b7f 102836 
mailman_2.1.23-1+deb9u2.debian.tar.xz
 6e941845c135950d1a95ebffcb695131669eaa79 19232 
mailman-dbgsym_2.1.23-1+deb9u2_amd64.deb
 9e4589da848ff6875f6fb061f4b9c738bbf7e4e0 6743 
mailman_2.1.23-1+deb9u2_amd64.buildinfo
 2db8fd3855de65de02d1750ef065dabbc099288c 4466422 
mailman_2.1.23-1+deb9u2_amd64.deb
Checksums-Sha256:
 5a54f221827d4625cebf27c85c836cf9ff50f7f3189b99052364d8640c1cce4f 1800 
mailman_2.1.23-1+deb9u2.dsc
 b022ca6f8534621c9dbe50c983948688bc4623214773b580c2c78e4a7ae43e69 9290881 
mailman_2.1.23.orig.tar.gz
 23f3165bf7157644e0de2999a7951accd9bd8f1f222e6e77ab93b602e1189aea 102836 
mailman_2.1.23-1+deb9u2.debian.tar.xz
 85c519c176bdef86927909fba9f2255bfedc2702075dd1f915253e2300423b1f 19232 
mailman-dbgsym_2.1.23-1+deb9u2_amd64.deb
 8893c4e15d887a2f9b0d1485b8767f1b1f7796d47d772404ea8122aeb11821f0 6743 
mailman_2.1.23-1+deb9u2_amd64.buildinfo
 eab844b20c2e7e6eab5ba84af0cbee276b2da1bfe19de66693bcd7a5ed5dc3c9 4466422 
mailman_2.1.23-1+deb9u2_amd64.deb
Files:
 410c5d780329d7fda9e9353dc82adfd7 1800 mail optional mailman_2.1.23-1+deb9u2.dsc
 ceb2d8427e29f4e69b2505423ffeb60b 9290881 mail optional 
mailman_2.1.23.orig.tar.gz
 

Bug#867450: marked as done (python3-pyperclip: missing python3 dependency)

[Debian Bug Tracking System]

Your message dated Wed, 14 Feb 2018 21:17:27 +
with message-id 
and subject line Bug#867450: fixed in python-pyperclip 1.5.27-3~deb9u1
has caused the Debian Bug report #867450,
regarding python3-pyperclip: missing python3 dependency
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.)


-- 
867450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867450
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pyperclip
Version: 1.5.27-2
Severity: serious
Tags: patch

Due to a cut'n'paste error the python3 dependency is missing.

Fix:

--- debian/control.old  2017-07-06 17:10:18.0 +
+++ debian/control  2017-07-06 17:10:29.0 +
@@ -20,7 +20,7 @@
 
 Package: python3-pyperclip
 Architecture: all
-Depends: ${shlibs:Depends}, ${misc:Depends}, ${python:Depends}, xclip | xsel | 
python3-pyqt4
+Depends: ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends}, xclip | xsel 
| python3-pyqt4
 Description: Cross-platform clipboard module for Python3
  This module is a cross-platform Python3 module for copy and paste clipboard
  functions. Currently only handles plaintext.
--- End Message ---
--- Begin Message ---
Source: python-pyperclip
Source-Version: 1.5.27-3~deb9u1

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

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

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated python-pyperclip 
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: Sat, 13 Jan 2018 23:56:47 +0100
Source: python-pyperclip
Binary: python-pyperclip python3-pyperclip
Architecture: source
Version: 1.5.27-3~deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Sebastien Delafond 
Changed-By: Andreas Beckmann 
Description:
 python-pyperclip - Cross-platform clipboard module for Python
 python3-pyperclip - Cross-platform clipboard module for Python3
Closes: 867450
Changes:
 python-pyperclip (1.5.27-3~deb9u1) stretch; urgency=medium
 .
   * Non-maintainer upload.
   * Rebuild for stretch.
 .
 python-pyperclip (1.5.27-3) unstable; urgency=medium
 .
   * Fix typo in Depends for python3 package (Closes: #867450)
Checksums-Sha1:
 2beec8c621e6580ed7c7eaf8dcb5db524bd72852 2157 
python-pyperclip_1.5.27-3~deb9u1.dsc
 3d8c6dbd6b5cbf7fff288c161f2a76a1b27cf099 2432 
python-pyperclip_1.5.27-3~deb9u1.debian.tar.xz
 71e0ebece49b7ad8c646880347d93f709b0e378b 7439 
python-pyperclip_1.5.27-3~deb9u1_source.buildinfo
Checksums-Sha256:
 55f0ae6365d2c095068d5fac1d3be0b9afdd8e85721b4f2cd1e5a3dc97cde5bc 2157 
python-pyperclip_1.5.27-3~deb9u1.dsc
 ad409fa0332fb0c30f60bc791881a73df58a9d1fc55c202736948c6a1b35f448 2432 
python-pyperclip_1.5.27-3~deb9u1.debian.tar.xz
 4272b353820793dd7116c5de1fc572f7e4bb32666731f8bbda94516cb54f397a 7439 
python-pyperclip_1.5.27-3~deb9u1_source.buildinfo
Files:
 587c483204b336f81f8b885e5a9c1710 2157 python optional 
python-pyperclip_1.5.27-3~deb9u1.dsc
 26657862fd127d82556008046df3db5f 2432 python optional 
python-pyperclip_1.5.27-3~deb9u1.debian.tar.xz
 0fe6b66f91dfafef2cf23ec0da094297 7439 python optional 
python-pyperclip_1.5.27-3~deb9u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAlpakNkQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCBFAD/wLlUlyBELAonliRNTpEo8dC7ytRfvnPOkG
/tYbPtuIxYx50wiYrVbtWYx9Hu8IqPcF6PXShtjXQcqfYx3oG2lb3IDeILxBNxbX
JhQI4fiarxzAsLWCJn3iuFJd2WP6JZzZWFoYDKuI+GNWBsiU42/IP8a7DYH+FQEV
wYnb+l3v56mCXn3WvbnPKgPQkRX3RF6qfD0EiFkRqws1S/W7aeXEGjM93Q03+eVd
n0Cjr0wNRj5snYV2hZqgEqmhR20lXjvKktv24c3JKWLfY+rUdsWoK4zHcNFft5S1
Zpv0nnMbver3xEWRwGQ1mp3/sqwPoA+RKC1v+KtKvelDdWvgtRyPgCAhtLLTvJSP
VWAuCMdsaaD8ZtowzohNoazBL69Rdz322874oxzSDwaBMBSnbZnVmDpPTY+HTc+E
jCwC50KkRtlG3li9z3Rrg62froIPo+lyHjolnWppgfCn5zHeaGuiz2P3VsaTWnvc
Tsk8AoWLOKiZiHiJidtYnXnEa606ecwR20avNc3ZZPxqdRUf1Ttru40NM/ir26cj
VCzONrLamAseMmkrRYQG/JW3juVVT++WHLAOV/Rtub8mVJP8OHwrX4AKJfYsVOU+
EUMjb4dQ+m84X4XQgAvEC7fo5JSDzz7qkmBM3wKseQKUHuBNU5NsxCmemzTscCmC
SyLFgBA+bg==
=NFsS
-END PGP 

Bug#867457: marked as done (python3-spake2: missing dependencies)

[Debian Bug Tracking System]

Your message dated Wed, 14 Feb 2018 21:17:27 +
with message-id 
and subject line Bug#867457: fixed in python-spake2 0.7-3~deb9u1
has caused the Debian Bug report #867457,
regarding python3-spake2: missing 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.)


-- 
867457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867457
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-spake2
Version: 0.7-2
Severity: serious
Tags: patch

Due to a cut'n'paste error there are no package dependencies.

Fix:

--- debian/control.old  2017-07-06 17:29:51.0 +
+++ debian/control  2017-07-06 17:29:59.0 +
@@ -40,7 +40,7 @@
 
 Package: python3-spake2
 Architecture: all
-Depends: ${misc:Depends}, ${python:Depends}
+Depends: ${misc:Depends}, ${python3:Depends}
 Description: SPAKE2 password-authenticated key exchange (pure python)
  This library implements the SPAKE2 password-authenticated key
  exchange ("PAKE") algorithm. This allows two parties, who share a
--- End Message ---
--- Begin Message ---
Source: python-spake2
Source-Version: 0.7-3~deb9u1

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

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

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated python-spake2 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: Sun, 14 Jan 2018 00:16:34 +0100
Source: python-spake2
Binary: python-spake2 python3-spake2
Architecture: source
Version: 0.7-3~deb9u1
Distribution: stretch
Urgency: high
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Description:
 python-spake2 - SPAKE2 password-authenticated key exchange (pure python)
 python3-spake2 - SPAKE2 password-authenticated key exchange (pure python)
Closes: 867457
Changes:
 python-spake2 (0.7-3~deb9u1) stretch; urgency=medium
 .
   * QA upload.
   * Rebuild for stretch.
 .
 python-spake2 (0.7-3) unstable; urgency=high
 .
   * QA upload.
   * Set maintainer to Debian QA Group. (see #833947)
   * Fix the python3-spake2 dependencies. (Closes: #867457)
Checksums-Sha1:
 4038e14f9ef6e815049a76d0e71557f09656e1a3 1987 python-spake2_0.7-3~deb9u1.dsc
 fa2859bd9719d1ec4dc784606fe20f0163ee5a3a 2484 
python-spake2_0.7-3~deb9u1.debian.tar.xz
 80b66f3bb81e0b8eecd0c891fa17f79e7f263909 6299 
python-spake2_0.7-3~deb9u1_source.buildinfo
Checksums-Sha256:
 3deef9e2fe24f263a3f7b35aecf2e20a014c120ec1ec52d7a826b9faf9efbb7f 1987 
python-spake2_0.7-3~deb9u1.dsc
 be01e021750f567476b3241034f5c1e29bd2c86b7d4e7651c6bab7dd7f446467 2484 
python-spake2_0.7-3~deb9u1.debian.tar.xz
 07ec7e26d1283a78b608d52ad8ea2d42effd8ab9721a0553ad5387e1c1005cfe 6299 
python-spake2_0.7-3~deb9u1_source.buildinfo
Files:
 4ceb3c6733c0fdf25a6d0feadeebf0d6 1987 python optional 
python-spake2_0.7-3~deb9u1.dsc
 660a237c6200424f69046a0c37823c1c 2484 python optional 
python-spake2_0.7-3~deb9u1.debian.tar.xz
 75dd4ac77eb1e7812d09fdd4c92f625d 6299 python optional 
python-spake2_0.7-3~deb9u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAlpalIAQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCLnJD/9XqgYqJ/cnA3+3V7SBRFZN3EXAz6XSROMg
doWSxxYe9lHg9o8ddm84GrT1T6WZAuHRGwApisCcKHvHzwILwohSL308KDv2Utrm
qLGSSYF9UmATy1qx8+UFUTPzB6Vnnu3LpuXf+qPZCe9Cu1YJvnUKw/VgxzyW0VmX
+fsdPdodBtAT8YR/44qNHfFPCpYlfKbcsRVNN7oB9Jr+cH0sA+MU97F7AQ968rzi
Q7EbbU9cKLPaVEKhkkYU2gIBi40Um2nrVOkeXAviIEEsGNuIYQkIVdHksL+dIOWK
11KgLRBjFhF0JqhGj7ucgM+UxRmjeB+HQei5jn3+d0pt6/l7MnGbXJa0Q+IE09S4
sce4R7gNSFa3L0xHuegIy5EnG97mKkNwf5Szp4TFdt+xs69Wrub26EHgjP4bHWBm
c8e8boLq1mjxKO7FrnMVwcIhFjKXQepbMR/23ZAXEpvtf8q1Qx746NVSQjSIZuNe
mhg0oYsF0io2taFiuInM7s1kfmcmSzF6J0kIMAXEuZthmYNna4sMIs0qe5S8MdM9
MZEpstDO4CHMUvEWxRLohiVazVBMN4Ot0cNIQKnQ9Tr8206S/jpg8GvkYG1Rmv1w
T2YYi+Odv9EuFIxtCHoOxmq5rsiSf/7uEws8Vh7pReTnIW9jEsm1JVgLU8BeHLxz
KDqqS3EsRA==
=H/N5
-END PGP SIGNATURE End Message ---

Bug#867433: marked as done (python3-hkdf: missing dependencies)

[Debian Bug Tracking System]

Your message dated Wed, 14 Feb 2018 21:17:26 +
with message-id 
and subject line Bug#867433: fixed in python-hkdf 0.0.3-3~deb9u1
has caused the Debian Bug report #867433,
regarding python3-hkdf: missing 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.)


-- 
867433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867433
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-hkdf
Version: 0.0.3-1
Severity: serious
Tags: patch

Due to a cut'n'paste error there are no dependencies.

Fix:

--- debian/control.old  2017-07-06 16:14:08.0 +
+++ debian/control  2017-07-06 16:14:23.0 +
@@ -26,7 +26,7 @@
 
 Package: python3-hkdf
 Architecture: all
-Depends: ${misc:Depends}, ${python:Depends}
+Depends: ${misc:Depends}, ${python3:Depends}
 Description: HMAC-based Extract-and-Expand Key Derivation Function (HKDF)
  This module implements the HMAC Key Derivation function, defined at
  http://tools.ietf.org/html/draft-krawczyk-hkdf-01
--- End Message ---
--- Begin Message ---
Source: python-hkdf
Source-Version: 0.0.3-3~deb9u1

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

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

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated python-hkdf 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: Sun, 14 Jan 2018 00:25:36 +0100
Source: python-hkdf
Binary: python-hkdf python3-hkdf
Architecture: source
Version: 0.0.3-3~deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Description:
 python-hkdf - HMAC-based Extract-and-Expand Key Derivation Function (HKDF)
 python3-hkdf - HMAC-based Extract-and-Expand Key Derivation Function (HKDF)
Closes: 864149 867433
Changes:
 python-hkdf (0.0.3-3~deb9u1) stretch; urgency=medium
 .
   * QA upload.
   * Rebuild for stretch.
 .
 python-hkdf (0.0.3-3) unstable; urgency=medium
 .
   * QA upload.
   * Fix the python3-hkdf dependencies. (Closes: #867433)
 .
 python-hkdf (0.0.3-2) unstable; urgency=medium
 .
   * Add missing URL to package descriptions.  closes: #864149.
   * Set maintainer to Debian QA Group.
Checksums-Sha1:
 e0f0753ac51e33dc50fe083391c4ee73f3cde319 1977 python-hkdf_0.0.3-3~deb9u1.dsc
 171bad583b0f71c7703dd6fc99fc3d9af13d32f5 2132 
python-hkdf_0.0.3-3~deb9u1.debian.tar.xz
 1de80b27bb4997375c7877590032df54f499b3a4 6295 
python-hkdf_0.0.3-3~deb9u1_source.buildinfo
Checksums-Sha256:
 d93d566d0f07fc89d466545b1582609ec2ca56ddbd868b88a010fc6b4646ffa3 1977 
python-hkdf_0.0.3-3~deb9u1.dsc
 80811f7aebb06e559c84ddd3f8f301b4291643e933ca9f3cfedf28dcd1bcdf36 2132 
python-hkdf_0.0.3-3~deb9u1.debian.tar.xz
 10c1a7960870008cfbfbce7e50e6bcfdbcd877392702673cf183574de3b753df 6295 
python-hkdf_0.0.3-3~deb9u1_source.buildinfo
Files:
 b81c5c72362acb6ab553892f142d7e82 1977 python optional 
python-hkdf_0.0.3-3~deb9u1.dsc
 9f1c9ac28f6e853ba59146d32a20a1ad 2132 python optional 
python-hkdf_0.0.3-3~deb9u1.debian.tar.xz
 b3a913685cdda5764d12a10cf131b4de 6295 python optional 
python-hkdf_0.0.3-3~deb9u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAlpalhIQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCBryD/4tg9ZjDLpFwXpyTbAKqvE2qSKsDS7dfkd2
d/4j/r4Exhkobu/k4/47uBk4JsO/VZYsb7dqnomx9tKqdzcrzKI3Z+5LPOpAqqDY
r6DGmn5583/5PYMVLoGucSYMrl0Lhn3WQK82fpfGxq9UaT9otmYQ6kcgm13s/Q/1
vOicAIN2mcZ+1FqxtH3xeap0LHwYrlT/PVYa7CYzpb8fWBwgx2/l9wDrv45swvlj
Cd0clz/N/Rpfjalj8QMTKmMBosukiKTWo7pWT4nlLC4Vhymv0hkrWGxymDxyBYCw
ZT6hHRbLF9tPvg7tE2aKT9tuQjXHBBDcqNYNPGOGwhZ0ECqYGHUndayHDya6Yr6H
q5r1NpIQ+9DpE4saXFh6SdiuqPJ2iMcSzmsUFbEgYu+CwGXz6EMraYswsXWn42kO
6zb8ekMpZ75GHre+GsomGK8LIOqvc9jQ9SSjor58l7g0It/SyZn4/NkWeAE9DgJ1
xuHiUqjPmxbo8Spm1l0tJVCvEIM1M1l4stfLw5ExPyEGpdVal0Td3LQwBySYNrT1
YWF97Ap74npJlgw1Xmjbnocu5yjCYMjx5kSf4WHOiRn+nQLqlbP6JfSkymPDJwUA
bWTX3BxGgQrhWigepdTcBIEUuSMHs2RYMFRkGmLMC7xaE3K+113EyC76qg4bjabZ
3w5lm+zL8w==
=jTnM
-END PGP SIGNATURE End Message ---

Bug#867439: marked as done (python3-mimeparse: missing dependencies)

[Debian Bug Tracking System]

Your message dated Wed, 14 Feb 2018 21:17:27 +
with message-id 
and subject line Bug#867439: fixed in python-mimeparse 0.1.4-3.1~deb9u1
has caused the Debian Bug report #867439,
regarding python3-mimeparse: missing 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.)


-- 
867439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867439
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-mimeparse
Version: 0.1.4-1
Severity: serious
Tags: patch

Due to a cut'n'paste error there are no dependencies.

Fix:

--- debian/control.old  2017-07-06 16:46:30.0 +
+++ debian/control  2017-07-06 16:46:36.0 +
@@ -25,7 +25,7 @@
 
 Package: python3-mimeparse
 Architecture: all
-Depends: ${misc:Depends}, ${python:Depends}
+Depends: ${misc:Depends}, ${python3:Depends}
 Description: Parse mime-types and quality parameters - python 3.x
  This module provides basic functions for parsing mime-type names and
  matching them against a list of media-ranges.
--- End Message ---
--- Begin Message ---
Source: python-mimeparse
Source-Version: 0.1.4-3.1~deb9u1

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

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

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated python-mimeparse 
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: Sun, 14 Jan 2018 00:37:15 +0100
Source: python-mimeparse
Binary: python-mimeparse python3-mimeparse
Architecture: source
Version: 0.1.4-3.1~deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Mathias Ertl 
Changed-By: Andreas Beckmann 
Description:
 python-mimeparse - Parse mime-types and quality parameters - python 2.x
 python3-mimeparse - Parse mime-types and quality parameters - python 3.x
Closes: 867439
Changes:
 python-mimeparse (0.1.4-3.1~deb9u1) stretch; urgency=medium
 .
   * Non-maintainer upload.
   * Rebuild for stretch.
 .
 python-mimeparse (0.1.4-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix the python3-mimeparse dependencies. (Closes: #867439)
Checksums-Sha1:
 e7f4ff01d3d9e78fbd7ebe93bc669a70b0cc21a6 2234 
python-mimeparse_0.1.4-3.1~deb9u1.dsc
 464b682612bb92f86db731067cd94a0cefb122d8 2980 
python-mimeparse_0.1.4-3.1~deb9u1.debian.tar.xz
 bf356cc3ca775479e9304cc1054e5597b30c9d79 6285 
python-mimeparse_0.1.4-3.1~deb9u1_source.buildinfo
Checksums-Sha256:
 74b10b1e791d606d218e13e74b2e54c45a9a93f476605cb99b63656721e2d732 2234 
python-mimeparse_0.1.4-3.1~deb9u1.dsc
 f5d176b4a113127b34e3f3efdcb49aa851f91d9eec919a33d186619bc8350b02 2980 
python-mimeparse_0.1.4-3.1~deb9u1.debian.tar.xz
 648bfdab2d5f40a0e7a44484c0e162447b8dcacd4430afcdae7c06c1fd4b78c5 6285 
python-mimeparse_0.1.4-3.1~deb9u1_source.buildinfo
Files:
 490cdbfd909a1820c00b42586103f2f6 2234 python optional 
python-mimeparse_0.1.4-3.1~deb9u1.dsc
 237e92e4efe8869db165f2b1578403c4 2980 python optional 
python-mimeparse_0.1.4-3.1~deb9u1.debian.tar.xz
 f9af89d423e79d6ec5a2aadd257be531 6285 python optional 
python-mimeparse_0.1.4-3.1~deb9u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAlpamOAQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCPPeD/4l5aWJsbgm9FYzVddNRun7d9IGjoHi8NJg
2ifeoU/gvMao+pgsNDFhNG5dlJQM/8gajx+pTU/h2wO/dihI4Cd7bpeFgV77slIY
sJEZ53zUIQUY8yCRo0g4HluDGVb9u55rQoLo8X8EqvM77gXhz6vAEsOon9HAuiXK
6D1nS8JILr6QD2ONEVR1Tig7XcIbVTYP0WG/SmvhBnlh+KNvSbR5gNWqGOGOV6JU
Qpne8ZXn/himMZ/2zkJMbHBGQTQ7g4U0cnwD/Xmar69SgJcdyt2yjdHg3nPaS+OJ
gQUyinQh9kwg7bcamveaxGMMPS/VkybOGpIJJmAtHOrm+vcSKzrPoT4EmXfj7esC
OXP0drpx65BLr29Cufe5d7SYKEwmdfSQL8qpiFq6XFz+4qZQEnOK9ae8SmFxRpI1
ckT1+EWtm4EP7OPO9vnCzlantmeJDudZI28TDJsXruJIiaZaiN2c5pW4RAXrKnAA
j/p7nNIqN25M9Plzp+B/0vZYZCoIYsQXZJ0/dkt6OTievmo/3zg4v6xCdRMr/RCe
izHH0OxTc75OkKE6EZRIs0yl0X1S2PVPMYoMO1xphbAoNiyplQVMZ5kMHSmhbFDo
oRAIL/2b+XYGG2ZfdaV22jqnuQdrVTL9PeI7Q3sAP5IDfAVTunQpM9eTczpLQ4gW
NritZgUbPA==
=iCih
-END PGP SIGNATURE End Message ---

Bug#867428: marked as done (python3-evtx: missing dependencies)

[Debian Bug Tracking System]

Your message dated Wed, 14 Feb 2018 21:17:26 +
with message-id 
and subject line Bug#867428: fixed in python-evtx 0.5.3b-3+deb9u1
has caused the Debian Bug report #867428,
regarding python3-evtx: missing 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.)


-- 
867428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867428
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-evtx
Version: 0.5.3b-3
Severity: serious
Tags: patch

Due to a cut'n'paste error there are no package dependencies.

Fix:

--- debian/control.old  2017-07-06 15:57:38.0 +
+++ debian/control  2017-07-06 15:57:46.0 +
@@ -23,10 +23,10 @@
 
 Package: python3-evtx
 Architecture: all
-Depends: ${misc:Depends}, ${python:Depends}
+Depends: ${misc:Depends}, ${python3:Depends}
 Description: parser for recent Windows Event Log files -- Python 3 version
  This module provides programmatic access to the File and Chunk
  headers, record templates, and event entries from Microsoft Windows
  Vista and later.
  .
- This package contains modules for Python 3.
\ No newline at end of file
+ This package contains modules for Python 3.
--- End Message ---
--- Begin Message ---
Source: python-evtx
Source-Version: 0.5.3b-3+deb9u1

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

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

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

Debian distribution maintenance software
pp.
Hilko Bengen  (supplier of updated python-evtx package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 12 Dec 2017 10:35:05 +0100
Source: python-evtx
Binary: python-evtx python3-evtx
Architecture: source
Version: 0.5.3b-3+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Hilko Bengen 
Changed-By: Hilko Bengen 
Description:
 python-evtx - parser for recent Windows Event Log files -- Python 2 version
 python3-evtx - parser for recent Windows Event Log files -- Python 3 version
Closes: 867428
Changes:
 python-evtx (0.5.3b-3+deb9u1) stretch; urgency=medium
 .
   * Fix Python3 dependencies (Closes: #867428)
Checksums-Sha1:
 1b43c13bae28c4bd3dead8cc958aed386d112203 2074 python-evtx_0.5.3b-3+deb9u1.dsc
 254ec7115a05d05e9c0ddeadbf284c95af17 7168 
python-evtx_0.5.3b-3+deb9u1.debian.tar.xz
 9a65072312905ce6b2fbc1314b8e2f443dc57849 6554 
python-evtx_0.5.3b-3+deb9u1_source.buildinfo
Checksums-Sha256:
 3e8693ee814d650c814b26757634a7dff6f8d936fe5087675b58577b79a0ebaf 2074 
python-evtx_0.5.3b-3+deb9u1.dsc
 0ae7887fc4eaabaf8474cc1fa9f67901a8f6b1f676856e49850448434f1f5270 7168 
python-evtx_0.5.3b-3+deb9u1.debian.tar.xz
 7ab56ac7ba1b084669e98696abb3c1f41259d7af80a27cf100c58bf82ff6001a 6554 
python-evtx_0.5.3b-3+deb9u1_source.buildinfo
Files:
 30f3d8bf4b03ffd5474bc067ff63eccc 2074 python optional 
python-evtx_0.5.3b-3+deb9u1.dsc
 4be25d206ee3e254d2ee4822419131ca 7168 python optional 
python-evtx_0.5.3b-3+deb9u1.debian.tar.xz
 8862a31a8b953fed54097ed4bff98dfb 6554 python optional 
python-evtx_0.5.3b-3+deb9u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErnMQVUQqHZbPTUx4dbcQY1whOn4FAlozovMACgkQdbcQY1wh
On41qhAAgsHtvim5hYUUw/PuDCx8uf+8Zq/7LouU8CKgaii3dYyyMGegMYpnZzVW
iixKtHro1z61hakB89gXPiooS72Dl2+RXls1jo7Ljt+k2qKf3P/zwyAH0uJ9NeGR
V3ZCVXwdVypxioF7jyQpHpagM8xl+lDCuFYvqeOmY8WceV/aJ0p6rbyDpTW9OgR9
7DiFQp/v7WB0v+0AxsnNyBpZsh7OlFFF5fC05IdEIzTFE+DYry9U8+n0+TdMIkma
+msSUq+vNFebuxsOtIHvwKtKGZs+lF3lg3IyfB/FuSFcRAO7De5sW1HLoRb+S2Fo
ePMibgj8PKhUdRNX9gonr4roULrP7Ly0BdBkqaoxfzEFtLA6LRJuWuPirbwEYWZ2
99A5QOuEXYOFP1zKj4ieT5mVVw3ykOnRG22MCaVRnOr7t22SocReyP+HsWWiOiq/
p6wInVJcY4+GnAcr1jYjqsrfIm51i/NfXS0onSmmFXErPNMmCOi8axBeo0sjsZgQ
hNW0MwL7WjZL7Tr4zzdhbTzpmtylK6hJljs6SgAczwXnzdimH9eiXdwO1vHjt24a
I/tXdmMP3X6Rqc1vWy3j3/Cy4tmURF5Kjw96ON6PCx6z6EP9RMs2m79Z2uUJnj5I
T0K3HPOifuwTxZAe/e2Jts00pK4aT14R2SCxYegtLl801TeUIBc=
=LVhe
-END PGP SIGNATURE End Message ---

Bug#867409: marked as done (python3-libvhdi: missing python3 dependency)

[Debian Bug Tracking System]

Your message dated Wed, 14 Feb 2018 21:17:19 +
with message-id 
and subject line Bug#867409: fixed in libvhdi 20160424-1+deb9u1
has caused the Debian Bug report #867409,
regarding python3-libvhdi: missing python3 dependency
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.)


-- 
867409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867409
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-libvhdi
Version: 20160424-1
Severity: serious
Tags: patch

Due to a cut'n'paste error the python3 dependency is missing.

Fix:

--- debian/control.old  2017-07-06 13:56:16.0 +
+++ debian/control  2017-07-06 13:56:24.0 +
@@ -68,7 +68,7 @@
 Package: python3-libvhdi
 Section: python
 Architecture: any
-Depends: libvhdi1 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}, 
${python:Depends}
+Depends: libvhdi1 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}, 
${python3:Depends}
 Description: Virtual Hard Disk image format access library -- Python 3 bindings
  libvhdi is a library to access the Virtual Hard Disk (VHD) image format.
  .
--- End Message ---
--- Begin Message ---
Source: libvhdi
Source-Version: 20160424-1+deb9u1

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

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

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

Debian distribution maintenance software
pp.
Hilko Bengen  (supplier of updated libvhdi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 12 Dec 2017 10:31:06 +0100
Source: libvhdi
Binary: libvhdi-dev libvhdi1 libvhdi-dbg libvhdi-utils python-libvhdi 
python3-libvhdi
Architecture: source
Version: 20160424-1+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian Forensics 
Changed-By: Hilko Bengen 
Description:
 libvhdi-dbg - Virtual Hard Disk image format access library -- debug symbols
 libvhdi-dev - Virtual Hard Disk image format access library -- development file
 libvhdi-utils - Virtual Hard Disk image format access library -- Utilities
 libvhdi1   - Virtual Hard Disk image format access library
 python-libvhdi - Virtual Hard Disk image format access library -- Python 2 
binding
 python3-libvhdi - Virtual Hard Disk image format access library -- Python 3 
binding
Closes: 867409 867610
Changes:
 libvhdi (20160424-1+deb9u1) stretch; urgency=medium
 .
   * Add mising Python3 dependency, thanks to Adrian Bunk, Scott Kitterman
 (Closes: #867409, #867610)
Checksums-Sha1:
 1c5ee6b241f8561504ba81badf020e043108 2325 libvhdi_20160424-1+deb9u1.dsc
 04be6ba67d012d4a2bd3b68645cdff6499d0ee5b 2960 
libvhdi_20160424-1+deb9u1.debian.tar.xz
 bcf58aa64f2f65c5843648da9d93eeaa6324ae4b 7049 
libvhdi_20160424-1+deb9u1_source.buildinfo
Checksums-Sha256:
 30ae2d94e5d3ccb7a7186758001238d8044f94790ceff921fe6c3b6c63cb7b91 2325 
libvhdi_20160424-1+deb9u1.dsc
 a554b36e2c10a2e345f2390774993527f3f8c44df7ca85d9f9673fb92a43ad25 2960 
libvhdi_20160424-1+deb9u1.debian.tar.xz
 86114f7f1d62e9c9740b38290c19a90058b9b26d2f50c5301f00f5e2cffd1722 7049 
libvhdi_20160424-1+deb9u1_source.buildinfo
Files:
 66f3bedf0cd3cc95d887afad28b65a91 2325 libs optional 
libvhdi_20160424-1+deb9u1.dsc
 f76cf739c63c33cec27b6efd0d76da95 2960 libs optional 
libvhdi_20160424-1+deb9u1.debian.tar.xz
 2de238b3099703470d94aaa53d5010a8 7049 libs optional 
libvhdi_20160424-1+deb9u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErnMQVUQqHZbPTUx4dbcQY1whOn4FAlozoiIACgkQdbcQY1wh
On7J9Q//RNZmLe6MJT56G9Gm4YY+ybRlD6asxQUK3lXBgIBX+a7cvWNbuM5GxzMt
Im20slWAiooSRH5i8+soYJPbRQFu2cVuCdV+holzRJ8mW8P8TDXEtFmJ3ucTEwir
3TlfMKdgb/E1XZO17Clg7hxTygdePVIw9sEo6YS+0oGRW5J+NBlYHAwCbOJ3IYQq
r28R/p8wtB0xzxteH6Pw7GAMyOEE52QQJptiZuDmmcqTd50cNwjghGkr7vV+O2b2
0T2HIIWzH1jhpb4B4FzIuoGCA94ZeRocXKBi31OEbb/fWmyEehKnXQAEQmF27BGU
s6hzxHl1SDWxB7hfJ++4MqcSgSUnlDszGb5Y6PSEoZ6DHcFwlLkPyZfuSAl0d6Z0
XOjLEKEKjz8xNhfl8tvfCiIC1Ia16qWNKzACxPgpw+OXaIhpM6XrvZLD/pBWCugr
q1wDLiTi+gqPc8HzVwm8OQOO9H/uCHLuYx0PYrHvJmjvrA8veA8Ok4qqxAwIXTqX

Bug#867431: marked as done (python3-hacking: incorrect dependencies)

[Debian Bug Tracking System]

Your message dated Wed, 14 Feb 2018 21:17:26 +
with message-id 
and subject line Bug#867431: fixed in python-hacking 0.11.0-2.1~deb9u1
has caused the Debian Bug report #867431,
regarding python3-hacking: incorrect 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.)


-- 
867431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867431
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-hacking
Version: 0.8.1-4
Severity: serious
Tags: patch

Due to a cut'n'paste error the dependencies are incorrect.

Fix:

--- debian/control.old  2017-07-06 16:03:45.0 +
+++ debian/control  2017-07-06 16:10:07.0 +
@@ -55,13 +55,13 @@
 
 Package: python3-hacking
 Architecture: all
-Depends: pyflakes,
+Depends: pyflakes3,
  python3-flake8 (>= 3.0.0),
  python3-pbr (>= 1.8),
  python3-pep8 (>= 1.5.7),
  python3-six (>= 1.9.0),
  ${misc:Depends},
- ${python:Depends},
+ ${python3:Depends},
 Recommends: ${python3:Recommends},
 Description: Flake8 OpenStack Hacking Guidelines Enforcement plugins - Python 
3.x
  Hacking is a set of flake8 plugins that test and enforce the OpenStack Style
--- End Message ---
--- Begin Message ---
Source: python-hacking
Source-Version: 0.11.0-2.1~deb9u1

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

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

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated python-hacking 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: Sun, 14 Jan 2018 00:46:21 +0100
Source: python-hacking
Binary: python-hacking python3-hacking python-hacking-doc
Architecture: source
Version: 0.11.0-2.1~deb9u1
Distribution: stretch
Urgency: medium
Maintainer: PKG OpenStack 
Changed-By: Andreas Beckmann 
Description:
 python-hacking - Flake8 OpenStack Hacking Guidelines Enforcement plugins - 
Python
 python-hacking-doc - Flake8 OpenStack Hacking Guidelines Enforcement plugins - 
doc
 python3-hacking - Flake8 OpenStack Hacking Guidelines Enforcement plugins - 
Python
Closes: 867431
Changes:
 python-hacking (0.11.0-2.1~deb9u1) stretch; urgency=medium
 .
   * Non-maintainer upload.
   * Rebuild for stretch.
 .
 python-hacking (0.11.0-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix the python3-hacking dependencies. (Closes: #867431)
Checksums-Sha1:
 19981f8f90f4d2dba2cdd610a2a3b9f81f81bd05 2748 
python-hacking_0.11.0-2.1~deb9u1.dsc
 9f51360380b9593f7b3a8b9089b41f115985d486 5080 
python-hacking_0.11.0-2.1~deb9u1.debian.tar.xz
 8592af5ec8a7b26e0eac8ea7f33a6fc14769981c 8245 
python-hacking_0.11.0-2.1~deb9u1_source.buildinfo
Checksums-Sha256:
 e0c27370f9ffec6e9452d3c687869e0b123e90bbd3f2469b8916854caf59a0fd 2748 
python-hacking_0.11.0-2.1~deb9u1.dsc
 467e42bcfe510feac913d29304d723abe55300e2b7f91aca78c1f03588cd7242 5080 
python-hacking_0.11.0-2.1~deb9u1.debian.tar.xz
 00a3d97377171ce73d5e72aad32b844ab115a5d3834243f9604f00e350b1e30b 8245 
python-hacking_0.11.0-2.1~deb9u1_source.buildinfo
Files:
 fa6d917b1344b26c73819418b8e0c66c 2748 python optional 
python-hacking_0.11.0-2.1~deb9u1.dsc
 f21851c27c3bab67c254d9cfd22e10bf 5080 python optional 
python-hacking_0.11.0-2.1~deb9u1.debian.tar.xz
 cc97e348afd609b9eeb684faf16c57ea 8245 python optional 
python-hacking_0.11.0-2.1~deb9u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAlpam7cQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCJa2EACbFEc3GayR40FjuJ9QzeDUhDU2xAB6ny5J
BzCNmGMcFCv55LBaWPmtQOA2zsXw75DGghyX8CV3sznVv1ck+pFEl7dXiasm8Gdp
P8xv2WzSuE7qCCft/9mv2087qwXrfZSFv+MdaM0IOna40FLr/6/BioMrcq55bdtB
wHjOYOyCLMevNsB/PlBTQ19cVpQUsUhjGX7Xy82ZdXtIEIHkVNGz7SxrONT6m8BR
WHVyB7qGhETZBNDrRZUomaZFHI8B94LOnUHvDZlG+iBZpqPfzWXVzfs/4cik17a/
Z0siGRRsZ1bS5Rs5sjQ9f/EZ1FplO5w/C0nkmjUPQQMASeBD4ZxF/moiF9bTc5vK
GmNSAlD2RIzDdhYSq2p/xBnrkYPcAr4J096fYyeH/0Tt7zgibQegCimr8BTYAwrD

Bug#890255: Bug #890255 in vala marked as pending

[jbicha]

Control: tag -1 pending

Hello,

Bug #890255 in vala reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/gnome-team/vala/commit/fb9d14580e4440a285e6e5ae94f252772a39817a


Use correct bug number

Closes: #890255



(this message was generated automatically)
-- 
Greetings

Processed: Bug #890255 in vala marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #890255 [valac] libkkc: Fails to build: unknown type name ‘KkcState’
Added tag(s) pending.

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

Processed: gamazons: Raising severity for libgnome dependencies

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #885735 [src:gamazons] gamazons: Depends on libgnomeui
Severity set to 'serious' from 'important'

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

Processed: affects 890255

[Debian Bug Tracking System]

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

> affects 890255 src:libkkc
Bug #890255 [valac] libkkc: Fails to build: unknown type name ‘KkcState’
Added indication that 890255 affects src:libkkc
> thanks
Stopping processing here.

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

Processed: camorama: Raising severity for libgnome dependencies

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #868388 [src:camorama] camorama: Please drop the (build-)dependency against 
gnome-vfs
Severity set to 'serious' from 'important'

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

Processed: set upstream bug of #890407

[Debian Bug Tracking System]

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

> forwarded 890407 https://github.com/milkytracker/MilkyTracker/issues/35
Bug #890407 [milkytracker] milkytracker: various buffer overflows possibly 
leading to remote code execution
Set Bug forwarded-to-address to 
'https://github.com/milkytracker/MilkyTracker/issues/35'.
> thanks
Stopping processing here.

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

Processed: Re: fails 100% for me

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #855091 [src:aiocoap] aiocoap: FTBFS randomly (failing tests)
Severity set to 'normal' from 'serious'
> tag -1 moreinfo
Bug #855091 [src:aiocoap] aiocoap: FTBFS randomly (failing tests)
Added tag(s) moreinfo.

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

Bug#855091: fails 100% for me

[Agustin Henze]

Control: severity -1 normal
Control: tag -1 moreinfo

Hi Adam,

On 06/25/17 20:35, Adam Borowski wrote:
> Control: severity -1 serious
> 
> Hi!
> I've tried to build this package many times (5 on armhf, 10 on amd64, once
> on arm64), and it fails every single time.
> 
> Either Santiago's systems differ from those three of mine enough for the
> fail to be only random for him, or something else changed -- but the present
> state is that I have yet to see a successful build.
> 
>> The bug should be reproducible with sbuild on a single CPU virtual machine,
>> provided you try enough times (as the failure happens randomly).
> 
> All the machines I tried it on have multiple cores (4, 6 and 4,
> respectively).
I have tried to reproduce it with no success. Could you tell me more about your
setup please? I'm using the following command for testing it

set -e && for i in $(seq 10); do docker run --rm -it debian:stretch bash -c
'echo "deb-src http://deb.debian.org/debian stretch main" >
/etc/apt/sources.list.d/sources.list && apt-get update && apt-get install
eatmydata -y && eatmydata apt-get install dpkg-dev -y && apt-get source
aiocoap; eatmydata apt-get build-dep aiocoap -y && cd aiocoap-0.1+9ae36f4/ &&
dpkg-buildpackage -j$(getconf _NPROCESSORS_ONLN) -A'; done

Also I've tried using schroot and it finished correctly as well. As you can
see, I ran the command successfully 10 times, with multiple cores, with only
one core, etc. Please let me know if there is anything special on your setup to
be able to reproduce it. Or could you provide a single command to reproduce it?

Thanks,

-- 
TiN

Processed: Re: Bug#890391: libjs-jquery-atwho: ReferenceError: Controller is not defined

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #890391 [libjs-jquery-atwho] libjs-jquery-atwho: ReferenceError: Controller 
is not defined
Added tag(s) moreinfo.

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

Bug#890391: libjs-jquery-atwho: ReferenceError: Controller is not defined

[Ben Finney]

Control: tags -1 + moreinfo

On 14-Feb-2018, Pirate Praveen wrote:

> Originally reported with full error log at
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890333 and I was
> able to reproduce it in my system.

This bug report (bug#890391) begins with that message, and no
information on the error or steps to reproduce.

For reference in this bug report, can you please give complete steps
to reproduce with the current Debian package?

-- 
 \   “I have a map of the United States; it's actual size. It says |
  `\‘1 mile equals 1 mile’. Last summer, I folded it.” —Steven |
_o__)   Wright |
Ben Finney 


signature.asc
Description: PGP signature

Bug#855091: aiocoap: FTBFS randomly (failing tests)

[Agustin Henze]

On 02/13/17 20:25, Santiago Vila wrote:
[snipped]
> 
> This is just how the build ends, not necessarily the relevant part.
> 
> I've put several build logs here:
> 
> https://people.debian.org/~sanvila/build-logs/aiocoap/
> 
> If this is really a bug in one of the build-depends, please use reassign and 
> affects,
> so that this is still visible in the page for this package.
> 
> The bug should be reproducible with sbuild on a single CPU virtual machine,
> provided you try enough times (as the failure happens randomly).


Hi Santiago, sorry for the looonggg delay. I have tried to reproduce it with no
success. Could you tell me more about your setup please?
I'm using the following command for testing it

set -e && for i in $(seq 10); do docker run --rm -it debian:stretch bash -c
'echo "deb-src http://deb.debian.org/debian stretch main" >
/etc/apt/sources.list.d/sources.list && apt-get update && apt-get install
eatmydata -y && eatmydata apt-get install dpkg-dev -y && apt-get source
aiocoap; eatmydata apt-get build-dep aiocoap -y && cd aiocoap-0.1+9ae36f4/ &&
dpkg-buildpackage -j$(getconf _NPROCESSORS_ONLN) -A'; done

Also I've tried using schroot and it finished correctly as well. As you can
see, I ran the command successfully 10 times, with multiple cores, with only
one core, etc. Please let me know if there is anything special on your setup to
be able to reproduce it.

Thanks,

-- 
TiN



signature.asc
Description: OpenPGP digital signature

Processed: Re: libkkc: Fails to build: unknown type name ‘KkcState’

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 valac 0.38.7-1
Bug #890255 [src:libkkc] libkkc: Fails to build: unknown type name ‘KkcState’
Bug reassigned from package 'src:libkkc' to 'valac'.
No longer marked as found in versions libkkc/0.3.5-2.
Ignoring request to alter fixed versions of bug #890255 to the same values 
previously set
Bug #890255 [valac] libkkc: Fails to build: unknown type name ‘KkcState’
Marked as found in versions vala/0.38.7-1.

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

Bug#890255: libkkc: Fails to build: unknown type name ‘KkcState’

[Jeremy Bicha]

Control: reassign -1 valac 0.38.7-1

I can't reproduce this build failure with vala 0.39.91. I am uploading
vala 0.39.91 to experimental now and we'll push it to unstable soon.

Thanks,
Jeremy Bicha

Bug#890406: linux-image-4.14.0-0.bpo.3-amd64: Installing kernel fails to build broadcom-sta

[Steve]

Hi,

Le 14-02-2018, à 18:52:16 +, Ben Hutchings a écrit :


If an external module is not compatible with a new kernel version, that
is not a bug in the new kernel version.


Which I perfectly understand. 


But as a user, I'm stuck with a broken system (no wireless) after
choosing to update my kernel by regular means. What should be my next
steps?


As it happens, this has just been fixed in a new version of
broadcom-sta in unstable.


Good to hear that. I'll give it a try even though I'm running stable.

Thanks for the quick answer.

Steve

Processed: severity of 890355 is important

[Debian Bug Tracking System]

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

> # missing cc to control@ in message 15
> severity 890355 important
Bug #890355 [man-db] man: nroff: Bad system call
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Processed: reassign 890406 to src:broadcom-sta, forcibly merging 885885 890406

[Debian Bug Tracking System]

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

> reassign 890406 src:broadcom-sta
Bug #890406 [broadcom-sta] linux-image-4.14.0-0.bpo.3-amd64: Installing kernel 
fails to build broadcom-sta
Bug reassigned from package 'broadcom-sta' to 'src:broadcom-sta'.
No longer marked as found in versions 6.30.223.271-7.
Ignoring request to alter fixed versions of bug #890406 to the same values 
previously set
> forcemerge 885885 890406
Bug #885885 {Done: Eduard Bloch } [src:broadcom-sta] FTBTS 
with linux 4.15, severe warnings with linux 4.14
Bug #890406 [src:broadcom-sta] linux-image-4.14.0-0.bpo.3-amd64: Installing 
kernel fails to build broadcom-sta
Severity set to 'serious' from 'important'
Marked Bug as done
Marked as fixed in versions broadcom-sta/6.30.223.271-8.
Marked as found in versions broadcom-sta/6.30.223.271-7.
Added tag(s) patch.
Merged 885885 890406
> thanks
Stopping processing here.

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

Bug#888508: gitlab: multiple CVEs from GitLab Security Release: 10.3.4, 10.2.6, and 10.1.6 advisory

[Moritz Mühlenhoff]

On Fri, Jan 26, 2018 at 10:14:16PM +0530, Pirate Praveen wrote:
> On വെള്ളി 26 ജനുവരി 2018 07:32 വൈകു, Salvatore Bonaccorso wrote:
> > See
> > https://about.gitlab.com/2018/01/16/gitlab-10-dot-3-dot-4-released/
> > for which several go back to 8.9.0 versions.
> > 
> > There are three CVEs out of
> > https://security-tracker.debian.org/tracker/source-package/gitlab
> > belonging to that list wich are yet marked undetermined, because not
> > clear from the advisory if 8.13.11=dfsg1-12 might be affected.
> > But assuming the 'version affected' information is correct, they are
> > not, please confirm so we can adjust the security-tracker information.
> 
> We are working on backporting the patches (8.13.12 don't have most of
> these patches). We will confirm once we go through all of it.

What's the status?

Cheers,
Moritz

Processed: affects 890415

[Debian Bug Tracking System]

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

> affects 890415 src:java2html src:haskell98-tutorial src:fped src:ifmail
Bug #890415 [libfl-dev] libfl-dev: Debian-specific libfl.so linker script 
causes FTBFS
Added indication that 890415 affects src:java2html, src:haskell98-tutorial, 
src:fped, and src:ifmail
> thanks
Stopping processing here.

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

Processed: Bug #890423 in systemd marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #890423 [systemd] systemd getpeergroups break rsync
Added tag(s) pending.

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

Bug#890423: Bug #890423 in systemd marked as pending

[fsateler]

Control: tag -1 pending

Hello,

Bug #890423 in systemd reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/systemd-team/systemd/commit/d5a2610b2db36ac8557480d44acb17114ef7b1d0


Backport upstream patch fixing a wrong assert() call

Closes: #890423



(this message was generated automatically)
-- 
Greetings

Bug#890431: grub2 FTBFS with flex 2.6.4

[Adrian Bunk]

Source: grub2
Version: 2.02-2
Severity: serious
Tags: patch

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

...
grub_script.yy.c:19:22: error: statement with no effect [-Werror=unused-value]
 #define fprintf(...) 0
  ^
grub_script.yy.c:2367:2: note: in expansion of macro 'fprintf'
  fprintf( stderr, "%s\n", msg );
  ^~~


Upstream fix attached.
>From c36c2a86404f373100775305f532c09d46f3c6ce Mon Sep 17 00:00:00 2001
From: Vladimir Serbinenko 
Date: Mon, 14 Aug 2017 14:11:43 +0200
Subject: yylex: Explicilty cast fprintf to void.

It's needed to avoid warning on recent GCC.
---
 grub-core/script/yylex.l | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/grub-core/script/yylex.l b/grub-core/script/yylex.l
index 95b219170..7b44c37b7 100644
--- a/grub-core/script/yylex.l
+++ b/grub-core/script/yylex.l
@@ -91,7 +91,7 @@ typedef size_t yy_size_t;
 #define stdin  0
 #define stdout 0
 
-#define fprintf(...) 0
+#define fprintf(...) (void)0
 #define exit(...) grub_fatal("fatal error in lexer")
 #endif
 
-- 
2.11.0

Bug#865043: Please drop Build-Depends on deprecated libck-connector-dev

[Michael Biebl]

On Sun, 18 Jun 2017 22:08:54 +0200 Michael Biebl  wrote:
> Source: lxdm
> Version: 0.5.3-2
> Severity: normal
> Tags: patch
> 
> Hi,
> 
> ConsoleKit is dead upstream since almost 4 years [1] and unmaintained in
> Debian [2]. With logind a much better, well maintained alternative exists.
> I would thus like to remove ConsoleKit from the archive.
> lxdm is the only remaining package which declares a Build-Depends on
> libck-connector-dev. Please consider dropping that Build-Depends in your
> next upload. Patch for that is attached.

I've uploaded a fixed package to DELAYED/7. Debdiff is attached.
While at it, I've also removed the ExecStartPre= hack from lxdm.service
which is no longer necessary.

Please holler if I should delay longer or you want me to cancel for
other reasons.

Regards,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
diff -Nru lxdm-0.5.3/debian/changelog lxdm-0.5.3/debian/changelog
--- lxdm-0.5.3/debian/changelog 2016-11-11 22:58:40.0 +0100
+++ lxdm-0.5.3/debian/changelog 2018-02-14 18:18:12.0 +0100
@@ -1,3 +1,11 @@
+lxdm (0.5.3-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop Build-Depends on deprecated libck-connector-dev (Closes: #865043).
+  * Drop ExecStartPre hack from lxdm.service which is no longer necessary.
+
+ -- Michael Biebl   Wed, 14 Feb 2018 18:18:12 +0100
+
 lxdm (0.5.3-2) unstable; urgency=medium
 
   * Adding 41-force-reset.patch to enforce reset (Closes: #842333).
diff -Nru lxdm-0.5.3/debian/control lxdm-0.5.3/debian/control
--- lxdm-0.5.3/debian/control   2016-11-11 22:45:19.0 +0100
+++ lxdm-0.5.3/debian/control   2018-02-14 18:17:54.0 +0100
@@ -7,7 +7,7 @@
  Andriy Grytsenko 
 Build-Depends:
  debhelper (>= 9), intltool, iso-codes,
- libck-connector-dev, libgtk2.0-dev, libpam0g-dev,
+ libgtk2.0-dev, libpam0g-dev,
  libx11-dev, libxmu-dev, pkg-config,
  dh-systemd, po-debconf
 Standards-Version: 3.9.8
diff -Nru lxdm-0.5.3/debian/lxdm.service lxdm-0.5.3/debian/lxdm.service
--- lxdm-0.5.3/debian/lxdm.service  2015-11-26 12:26:47.0 +0100
+++ lxdm-0.5.3/debian/lxdm.service  2018-02-14 18:18:12.0 +0100
@@ -5,9 +5,6 @@
 After=systemd-user-sessions.service getty@tty7.service plymouth-quit.service
 
 [Service]
-# temporary safety check until all DMs are converted to correct
-# display-manager.service symlink handling
-ExecStartPre=/bin/sh -c '[ ! -f /etc/X11/default-display-manager -o "$(cat 
/etc/X11/default-display-manager 2>/dev/null)" = "/usr/sbin/lxdm" ]'
 ExecStart=/usr/sbin/lxdm
 Restart=always
 IgnoreSIGPIPE=no


signature.asc
Description: OpenPGP digital signature

Bug#890400: physamp: autopkgtest failure

[Adrian Bunk]

Control: reassign -1 libbpp-core3 2.3.2-1
Control: reassign 890405 libbpp-core3 2.3.2-1
Control: forcemerge -1 890405
Control: retitle -1 libbpp-core3: ABI change without soname chenge
Control: affects -1 src:physamp src:maffilter

On Wed, Feb 14, 2018 at 04:08:10PM +0100, Julien Yann Dutheil wrote:
> Will do, also for maffilter.
> 
> J.
> 
> On 14 Feb 2018 13:15, "Andreas Tille"  wrote:
> 
> > Hi Graham,
> >
> > I guess Julien Dutheil will care for a patch.
> >
> > Kind regards
> >
> >Andreas.
> >
> > On Wed, Feb 14, 2018 at 02:00:18PM +0200, Graham Inggs wrote:
> > > Source: physamp
> > > Version: 1.0.3-1
> > > Severity: serious
> > > User: ubuntu-de...@lists.ubuntu.com
> > > Usertags: origin-ubuntu bionic autopkgtest
> > >
> > > Hi Maintainer
> > >
> > > Since the upload of libbpp-core 2.3.2-1, physamp's autopkgtests have been
> > > failing [1] with the following error:
> > >
> > > autopkgtest [03:46:54]: test run-unit-test: [---
> > > bppalnoptim: symbol lookup error: bppalnoptim: undefined symbol: _
> > ZN3bpp16ApplicationTools18getDoubleParameterERKNSt7__
> > cxx1112basic_stringIcSt11char_traitsIcESaIcEEERSt3mapIS6_S6_
> > St4lessIS6_ESaISt4pairIS7_S6_EEEdS8_bi
>...

Note that there is nothing in maffilter or physamp that needs fixing,[1]
the bug is that the libbpp-core3 ABI changed without changing the soname:

src/Bpp/App/ApplicationTools.h:
 static double getDoubleParameter(
   const std::string& parameterName,
-  std::map& params,
+  const std::map& params,
   double defaultValue,
   const std::string& suffix = "",
   bool suffixIsOptional = true,

And a few other functions with similar changes.

In C++ this is an ABI change.

cu
Adrian

[1] a no-change rebuild would make them work again,
but that wouldn't fix the actual problem

-- 

   "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: Bug#890400: physamp: autopkgtest failure

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libbpp-core3 2.3.2-1
Bug #890400 [src:physamp] physamp: autopkgtest failure
Bug reassigned from package 'src:physamp' to 'libbpp-core3'.
No longer marked as found in versions physamp/1.0.3-1.
Ignoring request to alter fixed versions of bug #890400 to the same values 
previously set
Bug #890400 [libbpp-core3] physamp: autopkgtest failure
Marked as found in versions libbpp-core/2.3.2-1.
> reassign 890405 libbpp-core3 2.3.2-1
Bug #890405 [maffilter] maffilter: undefined symbol
Bug reassigned from package 'maffilter' to 'libbpp-core3'.
No longer marked as found in versions maffilter/1.2.1+dfsg-1.
Ignoring request to alter fixed versions of bug #890405 to the same values 
previously set
Bug #890405 [libbpp-core3] maffilter: undefined symbol
Marked as found in versions libbpp-core/2.3.2-1.
> forcemerge -1 890405
Bug #890400 [libbpp-core3] physamp: autopkgtest failure
Bug #890405 [libbpp-core3] maffilter: undefined symbol
Merged 890400 890405
> retitle -1 libbpp-core3: ABI change without soname chenge
Bug #890400 [libbpp-core3] physamp: autopkgtest failure
Bug #890405 [libbpp-core3] maffilter: undefined symbol
Changed Bug title to 'libbpp-core3: ABI change without soname chenge' from 
'physamp: autopkgtest failure'.
Changed Bug title to 'libbpp-core3: ABI change without soname chenge' from 
'maffilter: undefined symbol'.
> affects -1 src:physamp src:maffilter
Bug #890400 [libbpp-core3] libbpp-core3: ABI change without soname chenge
Bug #890405 [libbpp-core3] libbpp-core3: ABI change without soname chenge
Added indication that 890400 affects src:physamp and src:maffilter
Added indication that 890405 affects src:physamp and src:maffilter

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

Bug#890400: physamp: autopkgtest failure

[Julien Yann Dutheil]

Will do, also for maffilter.

J.

On 14 Feb 2018 13:15, "Andreas Tille"  wrote:

> Hi Graham,
>
> I guess Julien Dutheil will care for a patch.
>
> Kind regards
>
>Andreas.
>
> On Wed, Feb 14, 2018 at 02:00:18PM +0200, Graham Inggs wrote:
> > Source: physamp
> > Version: 1.0.3-1
> > Severity: serious
> > User: ubuntu-de...@lists.ubuntu.com
> > Usertags: origin-ubuntu bionic autopkgtest
> >
> > Hi Maintainer
> >
> > Since the upload of libbpp-core 2.3.2-1, physamp's autopkgtests have been
> > failing [1] with the following error:
> >
> > autopkgtest [03:46:54]: test run-unit-test: [---
> > bppalnoptim: symbol lookup error: bppalnoptim: undefined symbol: _
> ZN3bpp16ApplicationTools18getDoubleParameterERKNSt7__
> cxx1112basic_stringIcSt11char_traitsIcESaIcEEERSt3mapIS6_S6_
> St4lessIS6_ESaISt4pairIS7_S6_EEEdS8_bi
> > autopkgtest [03:46:55]: test run-unit-test: ---]
> > autopkgtest [03:46:55]: test run-unit-test:  - - - - - - - - - - results
> - -
> > - - - - - - - -
> > run-unit-testFAIL non-zero exit status 127
> >
> >
> > It looks like a symbol was dropped and a transition is needed.
> >
> > Regards
> > Graham
> >
> >
> > [1] https://ci.debian.net/packages/p/physamp/unstable/amd64/
> >
> > ___
> > Debian-med-packaging mailing list
> > debian-med-packag...@lists.alioth.debian.org
> > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/
> debian-med-packaging
> >
>
> --
> http://fam-tille.de
>

Bug#890378: marked as done (centrifuge: FTBFS on !x86 and FTBFS on i386)

[Debian Bug Tracking System]

Your message dated Wed, 14 Feb 2018 15:05:29 +
with message-id 
and subject line Bug#890378: fixed in centrifuge 1.0.3~beta-2
has caused the Debian Bug report #890378,
regarding centrifuge: FTBFS on !x86 and FTBFS on i386
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.)


-- 
890378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890378
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: centrifuge
Version: 1.0.3~beta-1
Severity: serious

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

-msse2 is:
- already enabled by default on amd64
- a baseline violation on i386
- not available on any other architectures (except x32)

Related to the resolution of this bug:
centrifuge/i386 unsatisfiable Depends: hisat2
centrifuge/i386 unsatisfiable Depends: jellyfish

Since the dependency hisat2 is amd64-only,
there is no point in trying to build centrifuge
on other architectures.
--- End Message ---
--- Begin Message ---
Source: centrifuge
Source-Version: 1.0.3~beta-2

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated centrifuge package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 14 Feb 2018 14:18:27 +0100
Source: centrifuge
Binary: centrifuge
Architecture: source
Version: 1.0.3~beta-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 centrifuge - rapid and memory-efficient system for classification of DNA seque
Closes: 890378
Changes:
 centrifuge (1.0.3~beta-2) unstable; urgency=medium
 .
   * Move hisat2 and jellyfish to Build-Depends to make sure package builds
 only on those architectures where it can be installed later
   * -msse2 is already enabled by default on amd64 (which is the only
 architecture the package runs anyway)
 Closes: #890378
   * debhelper 11
Checksums-Sha1:
 c4da55d2f08b1ea5bceac339fcb03abfd603d2e0 2030 centrifuge_1.0.3~beta-2.dsc
 a3528ec8106a394ed2c9431cabe9031aad87feb3 6512 
centrifuge_1.0.3~beta-2.debian.tar.xz
 e508ff741c66ce92d61088d555a9d1f4551e0771 13485 
centrifuge_1.0.3~beta-2_source.buildinfo
Checksums-Sha256:
 7ac97067515fa5b0cb7e2e6c1c0a8754db1aa2489cce5f9e7e2cc03c72bc34a4 2030 
centrifuge_1.0.3~beta-2.dsc
 8b1d4ace4c5ca3c18d68df34e379563bc30b79af2c0350d987903e77430253b5 6512 
centrifuge_1.0.3~beta-2.debian.tar.xz
 0b03a34a7df1db8dd5a16da32616b8a7afae549e37e79b0b6e9da18a67df1f77 13485 
centrifuge_1.0.3~beta-2_source.buildinfo
Files:
 9a8918527d2d89efd256979a66c188db 2030 science optional 
centrifuge_1.0.3~beta-2.dsc
 89b91a317e43b2007573b6a77cbc950f 6512 science optional 
centrifuge_1.0.3~beta-2.debian.tar.xz
 ccfe77592ef3fbf5a151e196d21e63cc 13485 science optional 
centrifuge_1.0.3~beta-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJCBAEBCAAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlqEQw4OHHRpbGxlYUBy
a2kuZGUACgkQV4oElNHGRtFqCw//WHYNCDRE9p01+c6Prc7hRZ41VBAN2IdC6ngI
ktBDqD3n9Qw76uSQTIKhlQwNzBjHGci0QWBd5dAma8OgU/P73fXyWpojbYRikkze
/BHxshWP0SxrxAkje8qcax9ccbwm2sxS1flvMLb/z1DLVDmoAWjT/z/arD8TImQU
4kVtliMQKx+ShRQkWIsm3xqlYI7Z0KqikZ4rog5JpTQDoP4ctvxmL9JiLNYNfDzc
sfwRHKZGn+57n4ax/DX5aisR19WmDxrCWLqE/EpvCQunw7HF6k1mlEBISy0IvSlj
0qMInTTEdUlAUyaz0HhheWZKJEUoRAm5OWeQdbP6pNKJU9NMVKLCcu111anOLrk8
2Qe1f6dZKfNGA7xycHmoJZq0KfOL4PJ+BbiktXKcDTUy6gEa60wRUyRmecB8eqLG
1vQW/PbllWLTgSltt3b6rpz/pibiqIt0c6pWhqjSwzfBTD0yLPTuoWNwcPFBVfB5
VJNqvZgOETPiSWL2U5nN9coMjC/UXge6HQpLnKGuAMFAoreREbwPjJgyPR0SWm1x
APezS7DiLMxRKcTujTXGkUOBjbVYGl8ksZmA4Vcj8xeI5k2X4a9mj3926l6a7wke
xhudntOscSrQni+PalgV9UhSbkqBEwjym53b/l1Bz+83ZV2nS+dwDFN7FYMv3i+A
cDbXMho=
=MUI2
-END PGP SIGNATURE End Message ---

Bug#890415: libfl-dev: Debian-specific libfl.so linker script causes FTBFS

[Adrian Bunk]

Package: libfl-dev
Version: 2.6.4-2
Severity: serious
Control: affects -1 src:acedb src:bsdgames src:chemeq src:ctn src:filters

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

...
/usr/bin/ld: cannot find /usr/lib/x86_64-linux-gnu/libfl_pic.a
collect2: error: ld returned 1 exit status
make[3]: *** [makefile:1271: metacheck] Error 1


See #837658 and the upstream bug linked there for background.

Processed: libfl-dev: Debian-specific libfl.so linker script causes FTBFS

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:acedb src:bsdgames src:chemeq src:ctn src:filters
Bug #890415 [libfl-dev] libfl-dev: Debian-specific libfl.so linker script 
causes FTBFS
Added indication that 890415 affects src:acedb, src:bsdgames, src:chemeq, 
src:ctn, and src:filters

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

Bug#889843: marked as done (nose2 FTBFS: ERROR: test_can_discover_test_modules_in_zipped_eggs (nose2.tests.functional.test_eggdiscovery_loader.EggDiscoveryFunctionalTest))

[Debian Bug Tracking System]

Your message dated Wed, 14 Feb 2018 13:50:32 +
with message-id 
and subject line Bug#889843: fixed in nose2 0.7.3-3
has caused the Debian Bug report #889843,
regarding nose2 FTBFS: ERROR: test_can_discover_test_modules_in_zipped_eggs 
(nose2.tests.functional.test_eggdiscovery_loader.EggDiscoveryFunctionalTest)
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.)


-- 
889843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889843
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nose2
Version: 0.7.3-2
Severity: serious

Some recent change in unstable makes nose2 FTBFS:

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

...
==
ERROR: test_can_discover_test_modules_in_zipped_eggs 
(nose2.tests.functional.test_eggdiscovery_loader.EggDiscoveryFunctionalTest)
--
Traceback (most recent call last):
  File "nose2/tests/functional/test_eggdiscovery_loader.py", line 38, in 
test_can_discover_test_modules_in_zipped_eggs
self.assertTestRunOutputMatches(proc, stderr='FAILED \(failures=5, 
errors=1, skipped=1\)')
  File "nose2/tests/_common.py", line 82, in assertTestRunOutputMatches
cmd_stdout, cmd_stderr = proc.communicate()
  File "nose2/tests/_common.py", line 227, in communicate
**self.kwargs)
  File "nose2/main.py", line 306, in discover
return main(*args, **kwargs)
  File "nose2/main.py", line 100, in __init__
super(PluggableTestProgram, self).__init__(**kw)
  File "/usr/lib/python2.7/unittest/main.py", line 94, in __init__
self.parseArgs(argv)
  File "nose2/main.py", line 133, in parseArgs
self.createTests()
  File "nose2/main.py", line 258, in createTests
self.testNames, self.module)
  File "nose2/loader.py", line 68, in loadTestsFromNames
for name in event.names]
  File "nose2/loader.py", line 83, in loadTestsFromName
result = self.session.hooks.loadTestsFromName(event)
  File "nose2/events.py", line 225, in __call__
result = getattr(plugin, self.method)(event)
  File "nose2/plugins/loader/eggdiscovery.py", line 41, in loadTestsFromName
return discovery.Discoverer.loadTestsFromName(self, event)
  File "nose2/plugins/loader/discovery.py", line 84, in loadTestsFromName
self._find_tests_in_module(event, module, top_level_dir))
  File "nose2/plugins/loader/discovery.py", line 229, in _find_tests_in_module
event, full_path, top_level_dir):
  File "nose2/plugins/loader/eggdiscovery.py", line 78, in _find_tests_in_dir
event, modname, dist):
  File "nose2/plugins/loader/eggdiscovery.py", line 62, in 
_find_tests_in_egg_dir
for test in self._find_tests_in_egg_dir(event, entry_path, dist):
  File "nose2/plugins/loader/eggdiscovery.py", line 62, in 
_find_tests_in_egg_dir
for test in self._find_tests_in_egg_dir(event, entry_path, dist):
  File "nose2/plugins/loader/eggdiscovery.py", line 62, in 
_find_tests_in_egg_dir
for test in self._find_tests_in_egg_dir(event, entry_path, dist):
...
nose2.plugins.loader.eggdiscovery: DEBUG: find in egg dir 
/build/1st/nose2-0.7.3/nose2/tests/functional/support/scenario/tests_in_zipped_eggs/pkgegg-0.0.0-py2.7.egg
 pkgegg/test/ (pkgegg)
nose2.plugins.loader.eggdiscovery: DEBUG: find in egg dir 
/build/1st/nose2-0.7.3/nose2/tests/functional/support/scenario/tests_in_zipped_eggs/pkgegg-0.0.0-py2.7.egg
 pkgegg/test/ (pkgegg)
- >> end captured logging << -
--
Ran 246 tests in 139.913s

FAILED (errors=1, skipped=1)
E: pybuild pybuild:283: test: plugin custom failed with: exit code=1: python2.7 
-m nose2.__main__ -v
dh_auto_test: pybuild --test -i python{version} -p 2.7 --system=custom 
"--test-args={interpreter} -m nose2.__main__ -v" returned exit code 13
debian/rules:35: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25
--- End Message ---
--- Begin Message ---
Source: nose2
Source-Version: 0.7.3-3

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

Bug#890411: flex: backported commit causes FTBFS (and potentially miscompilation) of generated files

[Adrian Bunk]

Package: flex
Version: 2.6.4-2
Severity: serious
Forwarded: https://github.com/westes/flex/issues/313
Control: affects -1 src:libreswan

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

...
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -I/<>/ports/linux/include 
-I../../OBJ.linux.aarch64/lib/libipsecconf -I. 
-I/<>/linux/net/ipsec -I/<>/linux/include 
-I/<>/include -I/usr/include/nss -I/usr/include/nspr  -pthread 
-std=gnu99 -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fstack-protector-all 
-fno-strict-aliasing -fPIE -DPIE -DUSE_DNSSEC 
-DDEFAULT_DNSSEC_ROOTKEY_FILE=\"/usr/share/dns/root.key\" -DUSE_NIC_OFFLOAD 
-DHAVE_LABELED_IPSEC -DLIBCURL -DUSE_LINUX_AUDIT -DUSE_SYSTEMD_WATCHDOG 
-DLIBLDAP -DHAVE_NM -DXAUTH_HAVE_PAM -DUSE_MD5 -DUSE_SHA2 -DUSE_SHA1 -DUSE_AES 
-DUSE_3DES -DUSE_CAMELLIA -DUSE_SERPENT -DUSE_TWOFISH -DUSE_CAST 
-DDEFAULT_RUNDIR=\"/run/pluto\" -DFIPSPRODUCTCHECK=\"/etc/system-fips\" 
-DIPSEC_CONF=\"/etc/ipsec.conf\" -DIPSEC_CONFDDIR=\"/etc/ipsec.d\" 
-DIPSEC_NSSDIR=\"/var/lib/ipsec/nss\" -DIPSEC_CONFDIR=\"/etc\" 
-DIPSEC_EXECDIR=\"/usr/lib/ipsec\" -DIPSEC_S
 BINDIR=\"/usr/sbin\" -DIPSEC_VARDIR=\"/var\" 
-DPOLICYGROUPSDIR=\"/etc/ipsec.d/policies\" 
-DIPSEC_SECRETS_FILE=\"/etc/ipsec.secrets\" -DFORCE_PR_ASSERT -DUSE_FORK=1 
-DUSE_VFORK=0 -DUSE_DAEMON=0 -DUSE_PTHREAD_SETSCHEDPRIO=1 -DGCC_LINT 
-DALLOW_MICROSOFT_BAD_PROPOSAL -Werror -Wall -Wextra -Wformat 
-Wformat-nonliteral -Wformat-security -Wundef -Wmissing-declarations 
-Wredundant-decls -Wnested-externs -I/<>/ports/linux/include 
-I../../OBJ.linux.aarch64/lib/libipsecconf -I. 
-I/<>/linux/net/ipsec -I/<>/linux/include 
-I/<>/include -I/usr/include/nss -I/usr/include/nspr  -pthread 
-std=gnu99 -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fstack-protector-all 
-fno-strict-aliasing -fPIE -DPIE -DUSE_DNSSEC 
-DDEFAULT_DNSSEC_ROOTKEY_FILE=\"/usr/share/dns/root.key\" -DUSE_NIC_OFFLOAD 
-DHAVE_LABELED_IPSEC -DLIBCURL -DUSE_LINUX_AUDIT -DUSE_SYSTEMD_WATCHDOG 
-DLIBLDAP -DHAVE_NM -DXAUTH_HAVE_PAM -DUSE_MD5 -DUSE_SHA2 -DUSE_SHA1 -DUSE_AES 
-DUSE_3DES -DUSE_
 CAMELLIA -DUSE_SERPENT -DUSE_TWOFISH -DUSE_CAST 
-DDEFAULT_RUNDIR=\"/run/pluto\" -DFIPSPRODUCTCHECK=\"/etc/system-fips\" 
-DIPSEC_CONF=\"/etc/ipsec.conf\" -DIPSEC_CONFDDIR=\"/etc/ipsec.d\" 
-DIPSEC_NSSDIR=\"/var/lib/ipsec/nss\" -DIPSEC_CONFDIR=\"/etc\" 
-DIPSEC_EXECDIR=\"/usr/lib/ipsec\" -DIPSEC_SBINDIR=\"/usr/sbin\" 
-DIPSEC_VARDIR=\"/var\" -DPOLICYGROUPSDIR=\"/etc/ipsec.d/policies\" 
-DIPSEC_SECRETS_FILE=\"/etc/ipsec.secrets\" -DFORCE_PR_ASSERT -DUSE_FORK=1 
-DUSE_VFORK=0 -DUSE_DAEMON=0 -DUSE_PTHREAD_SETSCHEDPRIO=1 -DGCC_LINT 
-DALLOW_MICROSOFT_BAD_PROPOSAL -Werror -Wall -Wextra -Wformat 
-Wformat-nonliteral -Wformat-security -Wundef -Wmissing-declarations 
-Wredundant-decls -Wnested-externs \
-MF ../../OBJ.linux.aarch64/lib/libipsecconf/lex.yy.d \
-MP -MMD -MT lex.yy.o \
-o ../../OBJ.linux.aarch64/lib/libipsecconf/lex.yy.o \
-c /<>/OBJ.linux.aarch64/lib/libipsecconf/lex.yy.c
parser.l: In function 'parser_y_init':
parser.l:104:33: error: implicit declaration of function 'strdup' 
[-Werror=implicit-function-declaration]
  ic_private.stack[0].filename = strdup(name);
 ^~
parser.l:104:33: error: incompatible implicit declaration of built-in function 
'strdup' [-Werror]
parser.l: In function 'parser_y_nextglobfile':
parser.l:155:18: error: incompatible implicit declaration of built-in function 
'strdup' [-Werror]
  iis->filename = strdup(iis->fileglob.gl_pathv[fcnt]);
  ^~
parser.l: In function 'yylex':
parser.l:451:16: error: incompatible implicit declaration of built-in function 
'strdup' [-Werror]
 yylval.s = strdup(yytext);
^~
parser.l:467:16: error: incompatible implicit declaration of built-in function 
'strdup' [-Werror]
 yylval.s = strdup(s);
^~
parser.l:483:16: error: incompatible implicit declaration of built-in function 
'strdup' [-Werror]
 yylval.s = strdup(s);
^~
parser.l:490:16: error: incompatible implicit declaration of built-in function 
'strdup' [-Werror]
 yylval.s = strdup(yytext);
^~
parser.l:497:16: error: incompatible implicit declaration of built-in function 
'strdup' [-Werror]
 yylval.s = strdup(yytext);
^~
cc1: all warnings being treated as errors
../../mk/depend.mk:34: recipe for target 'lex.yy.o' failed
make[5]: *** [lex.yy.o] Error 1

Processed: flex: backported commit causes FTBFS (and potentially miscompilation) of generated files

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:libreswan
Bug #890411 [flex] flex: backported commit causes FTBFS (and potentially 
miscompilation) of generated files
Added indication that 890411 affects src:libreswan

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

Bug#890410: mpv: fix for CVE-2018-6360 overlooks subtitles

[James Cowgill]

Package: mpv
Version: 0.23.0-1
Severity: grave
Tags: security upstream

Yet another bug relating to the fix for CVE-2018-6360...

This time the bug is not a regression, but a mistake upstream made when
writing the original patch. Upstream overlooked the handling of subtitle
URLs which were not protected.

Upstream has released 0.27.2 and 0.28.2 to fix these. I think the bug
affects 0.23 as well (but I have not yet checked).

Possibly this warrants a new CVE number.

Upstream commit:
https://github.com/mpv-player/mpv/commit/3e71eb8676de53a05f51b987d294e7d2fa0a5bc1

James



signature.asc
Description: OpenPGP digital signature

Bug#890397: marked as done (python3-aiohttp: Can't use new yarl version)

[Debian Bug Tracking System]

Your message dated Wed, 14 Feb 2018 14:38:14 +0100
with message-id <20180214133814.tdeiweumi76bq...@sar0.p1otr.com>
and subject line fixed in 3.0.1-1
has caused the Debian Bug report #890397,
regarding python3-aiohttp: Can't use new yarl version
to be marked as done.

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

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


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

Dear Maintainer,

The new version of python3-yarl present in the archive
makes this package completely unusable.

I have opened a bug against yarl as well, but probably the most effective fix
is to patch it here.

Best

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

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

Versions of packages python3-aiohttp depends on:
ii  libc6  2.26-6
ii  python33.6.4-1
ii  python3-async-timeout  2.0.0-1
ii  python3-chardet3.0.4-1
ii  python3-multidict  4.1.0-1
ii  python3-yarl   1.1.0-1

python3-aiohttp recommends no packages.

python3-aiohttp suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: python-aiohttp
Source-Version: 3.0.1-1

I forgot to close it in the changelog--- End Message ---

Bug#890287: marked as done (mbedtls: CVE-2018-0488 - Risk of remote code execution when truncated HMAC is enabled)

[Debian Bug Tracking System]

Your message dated Wed, 14 Feb 2018 13:00:12 +
with message-id 
and subject line Bug#890287: fixed in mbedtls 2.7.0-1
has caused the Debian Bug report #890287,
regarding mbedtls: CVE-2018-0488 - Risk of remote code execution when truncated 
HMAC is enabled
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.)


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

https://tls.mbed.org/tech-updates/security-advisories/mbedtls-security-advisory-2018-01

Vulnerability
When the truncated HMAC extension is enabled and CBC is used, sending a
malicious application packet can be used to selectively corrupt 6 bytes
on the peer's heap, potentially leading to a crash or remote code
execution. This can be triggered remotely from either side in both TLS
and DTLS.

If the truncated HMAC extension, which can be set by the compile time
option MBEDTLS_SSL_TRUNCATED_HMAC in config.h, is disabled when
compiling the library, then the vulnerability is not present. The
truncated HMAC extension is enabled in the default configuration.

The vulnerability is only present if
* The compile-time option MBEDTLS_SSL_TRUNCATED_HMAC is set in config.h.
  (It is set by default) AND
* The truncated HMAC extension is explicitly offered by calling
  mbedtls_ssl_conf_truncated_hmac(). (It is not offered by default)

Impact
Depending on the platform, an attack exploiting this vulnerability could
lead to an application crash or allow remote code execution.

Resolution
Affected users should upgrade to Mbed TLS 1.3.22, Mbed TLS 2.1.10 or
Mbed TLS 2.7.0.

Workaround
Users should wherever possible upgrade to the newer version of Mbed TLS.
Where this is not practical, users should consider disabling the
truncated HMAC extension by removing any call to
mbedtls_ssl_conf_truncated_hmac() in their application, and the option
MBEDTLS_SSL_TRUNCATED_HMAC in the Mbed TLS configuration is practical
for their application.



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: mbedtls
Source-Version: 2.7.0-1

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

Debian distribution maintenance software
pp.
James Cowgill  (supplier of updated mbedtls 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, 14 Feb 2018 09:25:58 +
Source: mbedtls
Binary: libmbedtls-dev libmbedcrypto1 libmbedtls10 libmbedx509-0 libmbedtls-doc
Architecture: source amd64 all
Version: 2.7.0-1
Distribution: experimental
Urgency: medium
Maintainer: James Cowgill 
Changed-By: James Cowgill 
Description:
 libmbedcrypto1 - lightweight crypto and SSL/TLS library - crypto library
 libmbedtls-dev - lightweight crypto and SSL/TLS library - development files
 libmbedtls-doc - lightweight crypto and SSL/TLS library - documentation
 libmbedtls10 - lightweight crypto and SSL/TLS library - tls library
 libmbedx509-0 - lightweight crypto and SSL/TLS library - x509 certificate 
library
Closes: 890287 890288
Changes:
 mbedtls (2.7.0-1) experimental; urgency=medium
 .
   * New upstream release.
 - Fixes CVE-2018-0488. (Closes: #890287)
 - Fixes CVE-2018-0487. (Closes: #890288)
   * Rename libmbedcrypto0 to libmbedcrypto1 due to SONAME bump.
 .
   * debian/compat:
 - Use debhelper compat 11.
   * debian/control:
 - Switch to salsa.debian.org Vcs URLs.
 - Bump standards version to 4.1.3.
 - Drop useless Testsuite field in debian/control.
   * debian/copyright:
 - Update copyright dates.
   * debian/libmbedtls-doc.*:
 - Fix various paths to work with the new documentation location used
   by debhelper 11.
   * debian/patches:
 - Refresh config patch.
   * debian/*.symbols:
 - Add symbols updates for libmbedtls10.
 - Rewrite symbols libmbedcrypto1 symbols file.
Checksums-Sha1:
 

Bug#890288: marked as done (mbedtls: CVE-2018-0487 - Risk of remote code execution when verifying RSASSA-PSS signatures)

[Debian Bug Tracking System]

Your message dated Wed, 14 Feb 2018 13:00:12 +
with message-id 
and subject line Bug#890288: fixed in mbedtls 2.7.0-1
has caused the Debian Bug report #890288,
regarding mbedtls: CVE-2018-0487 - Risk of remote code execution when verifying 
RSASSA-PSS signatures
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.)


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

https://tls.mbed.org/tech-updates/security-advisories/mbedtls-security-advisory-2018-01

Vulnerability
When RSASSA-PSS signature verification is enabled, sending a maliciously
constructed certificate chain can be used to cause a buffer overflow on
the peer's stack, potentially leading to crash or remote code execution.
This can be triggered remotely from either side in both TLS and DTLS.

RSASSA-PSS is the part of PKCS #1 v2.1 standard and can be enabled by
the compile time option MBEDTLS_PKCS1_V21 in config.h. If
MBEDTLS_PKCS1_V21 is disabled when compiling the library, then the
vulnerability is not present. RSASSA-PSS signatures are enabled in the
default configuration.

Impact
Depending on the platform, an attack exploiting this vulnerability could
lead to an application crash or remote code execution.

Resolution
Affected users should upgrade to Mbed TLS 1.3.22, Mbed TLS 2.1.10 or
Mbed TLS 2.7.0.

Workaround
Users should wherever possible upgrade to the newer version of Mbed TLS.
Where this is not practical, users should consider if disabling the
option MBEDTLS_PKCS1_V21 in the Mbed TLS configuration is practical for
their application. Disabling RSASSA-PSS signatures in the verification
profile at runtime is not a sufficient countermeasure.



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: mbedtls
Source-Version: 2.7.0-1

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

Debian distribution maintenance software
pp.
James Cowgill  (supplier of updated mbedtls 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, 14 Feb 2018 09:25:58 +
Source: mbedtls
Binary: libmbedtls-dev libmbedcrypto1 libmbedtls10 libmbedx509-0 libmbedtls-doc
Architecture: source amd64 all
Version: 2.7.0-1
Distribution: experimental
Urgency: medium
Maintainer: James Cowgill 
Changed-By: James Cowgill 
Description:
 libmbedcrypto1 - lightweight crypto and SSL/TLS library - crypto library
 libmbedtls-dev - lightweight crypto and SSL/TLS library - development files
 libmbedtls-doc - lightweight crypto and SSL/TLS library - documentation
 libmbedtls10 - lightweight crypto and SSL/TLS library - tls library
 libmbedx509-0 - lightweight crypto and SSL/TLS library - x509 certificate 
library
Closes: 890287 890288
Changes:
 mbedtls (2.7.0-1) experimental; urgency=medium
 .
   * New upstream release.
 - Fixes CVE-2018-0488. (Closes: #890287)
 - Fixes CVE-2018-0487. (Closes: #890288)
   * Rename libmbedcrypto0 to libmbedcrypto1 due to SONAME bump.
 .
   * debian/compat:
 - Use debhelper compat 11.
   * debian/control:
 - Switch to salsa.debian.org Vcs URLs.
 - Bump standards version to 4.1.3.
 - Drop useless Testsuite field in debian/control.
   * debian/copyright:
 - Update copyright dates.
   * debian/libmbedtls-doc.*:
 - Fix various paths to work with the new documentation location used
   by debhelper 11.
   * debian/patches:
 - Refresh config patch.
   * debian/*.symbols:
 - Add symbols updates for libmbedtls10.
 - Rewrite symbols libmbedcrypto1 symbols file.
Checksums-Sha1:
 a8d1f6702d69006801e97d778983033ec95c3a7d 2163 mbedtls_2.7.0-1.dsc
 01ffebf679c8696cc941c41224fa73d8944d2c85 2108442 mbedtls_2.7.0.orig.tar.gz
 057da4c0aefaeee4495fe54712976a6afe7788de 11332 mbedtls_2.7.0-1.debian.tar.xz
 ca6eebb2f885ad21a9b2510f98a6cc9688db673e 323092 

Bug#890407: milkytracker: various buffer overflows possibly leading to remote code execution

[James Cowgill]

Package: milkytracker
Severity: grave
Tags: security upstream

Forwarding this bug sent to me by Johannes Schultz. It sounds bad. I
have not investigated it (and I don't know if it affects the pre-1.0
version in stable or not)

 Forwarded Message 
Subject: MilkyTracker - critical patches
Date: Wed, 14 Feb 2018 13:39:45 +0100
From: Johannes Schultz 
To: jcowg...@debian.org

Hi James,
I have recently fixed a bunch of very obvious and at the same time very
dangerous bugs in various module loaders in MilkyTracker, most of them
leading to out-of-bond writes both on the heap and stack. I think most
of them would be suitable for remote code execution.
You can find them here:
https://github.com/milkytracker/MilkyTracker/commit/6f7922616f31e5ceddd6f346cfc7f5d61a2f7683
You will also see the individual commits in the commit timeline around
October 2017.
I don't know if there is any immediate release planned by Deltafire, so
I recommend you to update the Debian packages based on those patches ASAP.
The individual diffs can also be found here:
https://sagagames.de/stuff/mt-patches.zip
They should apply to all MilkyTracker versions supported by the various
Debian releases, not just 1.01.00.

Best regards,
Johannes / OpenMPT Dev (and occasionall MilkyTracker bugfixer ;)



signature.asc
Description: OpenPGP digital signature

Bug#890405: maffilter: undefined symbol

[Graham Inggs]

Hi Maintainer

maffilter is affected by the same dropped symbol as in #890400:


$ maffilter
maffilter:symbol lookup error: maffilter: undefined symbol:
_ZN3bpp16ApplicationTools18getDoubleParameterERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERSt3mapIS6_S6_St4lessIS6_ESaISt4pairIS7_S6_EEEdS8_bi


Regards
Graham

Processed: maffilter: undefined symbol

[Debian Bug Tracking System]

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

> clone 890400 -1
Bug #890400 [src:physamp] physamp: autopkgtest failure
Bug 890400 cloned as bug 890405
> reassign -1 maffilter
Bug #890405 [src:physamp] physamp: autopkgtest failure
Bug reassigned from package 'src:physamp' to 'maffilter'.
No longer marked as found in versions physamp/1.0.3-1.
Ignoring request to alter fixed versions of bug #890405 to the same values 
previously set
> found -1 1.2.1+dfsg-1
Bug #890405 [maffilter] physamp: autopkgtest failure
Marked as found in versions maffilter/1.2.1+dfsg-1.
> retitle -1 maffilter: undefined symbol
Bug #890405 [maffilter] physamp: autopkgtest failure
Changed Bug title to 'maffilter: undefined symbol' from 'physamp: autopkgtest 
failure'.
> thanks
Stopping processing here.

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

Bug#890400: physamp: autopkgtest failure

[Andreas Tille]

Hi Graham,

I guess Julien Dutheil will care for a patch.

Kind regards

   Andreas.

On Wed, Feb 14, 2018 at 02:00:18PM +0200, Graham Inggs wrote:
> Source: physamp
> Version: 1.0.3-1
> Severity: serious
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu bionic autopkgtest
> 
> Hi Maintainer
> 
> Since the upload of libbpp-core 2.3.2-1, physamp's autopkgtests have been
> failing [1] with the following error:
> 
> autopkgtest [03:46:54]: test run-unit-test: [---
> bppalnoptim: symbol lookup error: bppalnoptim: undefined symbol: 
> _ZN3bpp16ApplicationTools18getDoubleParameterERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERSt3mapIS6_S6_St4lessIS6_ESaISt4pairIS7_S6_EEEdS8_bi
> autopkgtest [03:46:55]: test run-unit-test: ---]
> autopkgtest [03:46:55]: test run-unit-test:  - - - - - - - - - - results - -
> - - - - - - - -
> run-unit-testFAIL non-zero exit status 127
> 
> 
> It looks like a symbol was dropped and a transition is needed.
> 
> Regards
> Graham
> 
> 
> [1] https://ci.debian.net/packages/p/physamp/unstable/amd64/
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
> 

-- 
http://fam-tille.de

Bug#890400: physamp: autopkgtest failure

[Graham Inggs]

Source: physamp
Version: 1.0.3-1
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic autopkgtest

Hi Maintainer

Since the upload of libbpp-core 2.3.2-1, physamp's autopkgtests have 
been failing [1] with the following error:


autopkgtest [03:46:54]: test run-unit-test: [---
bppalnoptim: symbol lookup error: bppalnoptim: undefined symbol: 
_ZN3bpp16ApplicationTools18getDoubleParameterERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERSt3mapIS6_S6_St4lessIS6_ESaISt4pairIS7_S6_EEEdS8_bi

autopkgtest [03:46:55]: test run-unit-test: ---]
autopkgtest [03:46:55]: test run-unit-test:  - - - - - - - - - - results 
- - - - - - - - - -

run-unit-testFAIL non-zero exit status 127


It looks like a symbol was dropped and a transition is needed.

Regards
Graham


[1] https://ci.debian.net/packages/p/physamp/unstable/amd64/

Bug#890397: python3-aiohttp: Can't use new yarl version

[Salvo Tomaselli]

Package: python3-aiohttp
Version: 2.3.6-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The new version of python3-yarl present in the archive
makes this package completely unusable.

I have opened a bug against yarl as well, but probably the most effective fix
is to patch it here.

Best

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

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

Versions of packages python3-aiohttp depends on:
ii  libc6  2.26-6
ii  python33.6.4-1
ii  python3-async-timeout  2.0.0-1
ii  python3-chardet3.0.4-1
ii  python3-multidict  4.1.0-1
ii  python3-yarl   1.1.0-1

python3-aiohttp recommends no packages.

python3-aiohttp suggests no packages.

-- no debconf information

Bug#890391: libjs-jquery-atwho: ReferenceError: Controller is not defined

[Pirate Praveen]

Package: libjs-jquery-atwho
Version: 1.5.3+dfsg.1-1
Severity: grave
Justification: makes the package unuseable
Control: block 890333 by -1

Originally reported with full error log at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890333 and I was able
to reproduce it in my system.

gulp is now packaged, so may be its a good idea to use the upstream
build system (so its easier to support the package than learning a
custom build script). Also if it were part of javascript packaging team
repos, I could have helped directly.



signature.asc
Description: OpenPGP digital signature

Processed: libjs-jquery-atwho: ReferenceError: Controller is not defined

[Debian Bug Tracking System]

Processing control commands:

> block 890333 by -1
Bug #890333 [gitlab] gitlab: javascript errors after upgrade to 9.5.4
890333 was not blocked by any bugs.
890333 was not blocking any bugs.
Added blocking bug(s) of 890333: 890391

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

Bug#890387: python-jpype FTBFS: ImportError: No module named setuptools

[Adrian Bunk]

Source: python-jpype
Version: 0.6.2+dfsg-1
Severity: serious

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

...
   dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py clean 
Traceback (most recent call last):
  File "setup.py", line 10, in 
from setuptools import setup
ImportError: No module named setuptools
E: pybuild pybuild:283: clean: plugin distutils failed with: exit code=1: 
python2.7 setup.py clean 
dh_auto_clean: pybuild --clean -i python{version} -p 2.7 returned exit code 13
debian/rules:9: recipe for target 'clean' failed
make: *** [clean] Error 25

Bug#890384: ignition-math4: baseline violation on amd64

[Adrian Bunk]

Source: ignition-math4
Version: 4.0.0+dfsg1-1
Severity: serious

https://sources.debian.org/src/ignition-math4/4.0.0+dfsg1-1/debian/rules/#L10

ifeq ($(DEB_HOST_ARCH),amd64)
SSE_FLAGS = -mfpmath=sse -msse -msse2 -msse3 -mssse3 -DSSE
endif

SSE3 and SSSE3 are not part of the amd64 baseline.

"-mfpmath=sse -msse -msse2" are already enabled
by default on amd64, no need to do that manually.

The SSE define does not seem to be used anywhere in the code.

Bug#890378: centrifuge: FTBFS on !x86 and FTBFS on i386

[Adrian Bunk]

Source: centrifuge
Version: 1.0.3~beta-1
Severity: serious

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

-msse2 is:
- already enabled by default on amd64
- a baseline violation on i386
- not available on any other architectures (except x32)

Related to the resolution of this bug:
centrifuge/i386 unsatisfiable Depends: hisat2
centrifuge/i386 unsatisfiable Depends: jellyfish

Since the dependency hisat2 is amd64-only,
there is no point in trying to build centrifuge
on other architectures.

Bug#887769: marked as done (starplot FTBFS: error: 'starstrings' has not been declared)

[Debian Bug Tracking System]

Your message dated Wed, 14 Feb 2018 08:53:48 +
with message-id 
and subject line Bug#887769: fixed in starplot 0.95.5-8.3
has caused the Debian Bug report #887769,
regarding starplot FTBFS: error: 'starstrings' has not been declared
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.)


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

Some recent change in unstable makes starplot FTBFS:

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

...
classes/specclass.cc: In function 'double roman_to_int(const string&)':
classes/specclass.cc:23:7: error: 'starstrings' has not been declared
   if (starstrings::compare_n(roman_num, "VI", 2)) return 6.0;
   ^~~
--- End Message ---
--- Begin Message ---
Source: starplot
Source-Version: 0.95.5-8.3

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

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

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated starplot package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 08 Feb 2018 17:11:01 +0200
Source: starplot
Binary: starplot
Architecture: source
Version: 0.95.5-8.3
Distribution: unstable
Urgency: high
Maintainer: Francisco Manuel Garcia Claramonte 
Changed-By: Adrian Bunk 
Description:
 starplot   - 3-dimensional perspective star map viewer
Closes: 862065 869333 887769
Changes:
 starplot (0.95.5-8.3) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Add patch from Bernhard Übelacker to fix startup crash.
 (Closes: #862065)
   * Add patch from Juhani Numminen to fix FTBFS with glibc 2.26.
 (Closes: #887769)
   * Remove Kevin B. McCarty from Uploaders. (Closes: #869333)
Checksums-Sha1:
 2225917c5458a0acb869e13edc615f43712a153a 1831 starplot_0.95.5-8.3.dsc
 64bd667c8dcacbf3e3a435966f215eb5db1b8500 14668 
starplot_0.95.5-8.3.debian.tar.xz
Checksums-Sha256:
 3286c24a59f497bfe278482cc6583a1434c7b9c60c16792ba34be2486986b983 1831 
starplot_0.95.5-8.3.dsc
 267f0efecf8b8653f9bb00fe8da2c2b343c809f0ea3b422f3d5c90ad92553b5f 14668 
starplot_0.95.5-8.3.debian.tar.xz
Files:
 7015cb38b95b6a2d24fb5e3426810cef 1831 science optional starplot_0.95.5-8.3.dsc
 4e98f42ed5045daba5f4ea83c28a209f 14668 science optional 
starplot_0.95.5-8.3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlp8a1cACgkQiNJCh6LY
mLEChA/+Nsudyfh8OWfix9WnTKbGV5eyrF1R3gGE4HPk5uoYaEvHoID0tYyXgMRm
DDpr1STWvQUpkSVJWpwULxH1mLpQVsv8Ca0faidZT/aYVWuNe/8xdXJY9K0ulrFd
nYIeHz4D4ZBWkBGnXBDnKkEZPWEG7d/vhzCpUzUIC4JeS5LAlUpeDd2yNxif+aJ6
sS96BBC+zml3zEv5U/kV41GP+j2FfyvcXa0aS7SWAzWMHD6OXTvgLUiU2Hr5rAT+
OsVaDx3gEyzO5yRK+UbTg33y2iXq86jwU9XdXoGcek3IR+kXRHFjLERwSjiBt13x
YBrMZwOz/QzS0WtiYg8jRv3uKbiTh0XX/f75iRJRVG7Iol16Kz1K44Xhor4Jjp3E
0nZpEFh+V5PJoR6uq/KAFai/fVfKHlNH7iHulJBfcKvJuYt/GQ83uEoH6aEn7HI4
0SF4b2Mn2OVT05F17rL3wkAA2obz/3M944+BKvuIw0isKB06szf2XPdxaeSDJElU
uOYcT96n/mOMdE98SGV2ZwkOMKuE59Hu9DoQlD0qx3lmw1oeOB+mK9BDGZLrNn0R
ls8mK045iMgBJKO0meYKi4tgWuDXDz7QJIYXPwUKGN4R1rgD/dk8qmfyVZfPGemq
SCdwsF/Ps9yVMgK8K6JHwKfLFlS1qejzY7XHRGqo9Ixh4KPsVfM=
=UEyE
-END PGP SIGNATURE End Message ---

Bug#862065: marked as done (starplot: does not start due to invalid pointer error)

[Debian Bug Tracking System]

Your message dated Wed, 14 Feb 2018 08:53:48 +
with message-id 
and subject line Bug#862065: fixed in starplot 0.95.5-8.3
has caused the Debian Bug report #862065,
regarding starplot: does not start due to invalid pointer error
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.)


-- 
862065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862065
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: starplot
Version: 0.95.5-8.2
Severity: important

Dear Maintainer,

Starplot doesn't start and returns `*** Error in `starplot': free(): invalid
pointer: 0x55f5759e60d0 ***` when started from terminal.

However, `valgrind starplot` allows starplot to run normally.

This is a completely fresh installation of starplot on a computer that's never
had starplot installed before (so no leftover data in ${HOME}).



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

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

Versions of packages starplot depends on:
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-10
ii  libcairo21.14.8-1
ii  libfontconfig1   2.11.0-6.7+b1
ii  libfreetype6 2.6.3-3.2
ii  libgcc1  1:6.3.0-16
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0 2.50.3-2
ii  libgtk2.0-0  2.24.31-2
ii  libpango-1.0-0   1.40.5-1
ii  libpangocairo-1.0-0  1.40.5-1
ii  libpangoft2-1.0-01.40.5-1
ii  libstdc++6   6.3.0-16

Versions of packages starplot recommends:
ii  stardata-common  0.8+b1

Versions of packages starplot suggests:
pn  gliese  
pn  yale

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: starplot
Source-Version: 0.95.5-8.3

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

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

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated starplot package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 08 Feb 2018 17:11:01 +0200
Source: starplot
Binary: starplot
Architecture: source
Version: 0.95.5-8.3
Distribution: unstable
Urgency: high
Maintainer: Francisco Manuel Garcia Claramonte 
Changed-By: Adrian Bunk 
Description:
 starplot   - 3-dimensional perspective star map viewer
Closes: 862065 869333 887769
Changes:
 starplot (0.95.5-8.3) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Add patch from Bernhard Übelacker to fix startup crash.
 (Closes: #862065)
   * Add patch from Juhani Numminen to fix FTBFS with glibc 2.26.
 (Closes: #887769)
   * Remove Kevin B. McCarty from Uploaders. (Closes: #869333)
Checksums-Sha1:
 2225917c5458a0acb869e13edc615f43712a153a 1831 starplot_0.95.5-8.3.dsc
 64bd667c8dcacbf3e3a435966f215eb5db1b8500 14668 
starplot_0.95.5-8.3.debian.tar.xz
Checksums-Sha256:
 3286c24a59f497bfe278482cc6583a1434c7b9c60c16792ba34be2486986b983 1831 
starplot_0.95.5-8.3.dsc
 267f0efecf8b8653f9bb00fe8da2c2b343c809f0ea3b422f3d5c90ad92553b5f 14668 
starplot_0.95.5-8.3.debian.tar.xz
Files:
 7015cb38b95b6a2d24fb5e3426810cef 1831 science optional starplot_0.95.5-8.3.dsc
 4e98f42ed5045daba5f4ea83c28a209f 14668 science optional 
starplot_0.95.5-8.3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlp8a1cACgkQiNJCh6LY
mLEChA/+Nsudyfh8OWfix9WnTKbGV5eyrF1R3gGE4HPk5uoYaEvHoID0tYyXgMRm
DDpr1STWvQUpkSVJWpwULxH1mLpQVsv8Ca0faidZT/aYVWuNe/8xdXJY9K0ulrFd
nYIeHz4D4ZBWkBGnXBDnKkEZPWEG7d/vhzCpUzUIC4JeS5LAlUpeDd2yNxif+aJ6
sS96BBC+zml3zEv5U/kV41GP+j2FfyvcXa0aS7SWAzWMHD6OXTvgLUiU2Hr5rAT+
OsVaDx3gEyzO5yRK+UbTg33y2iXq86jwU9XdXoGcek3IR+kXRHFjLERwSjiBt13x
YBrMZwOz/QzS0WtiYg8jRv3uKbiTh0XX/f75iRJRVG7Iol16Kz1K44Xhor4Jjp3E
0nZpEFh+V5PJoR6uq/KAFai/fVfKHlNH7iHulJBfcKvJuYt/GQ83uEoH6aEn7HI4

Bug#890318: marked as done (util-linux: FTBFS on big endian - sha1/sha1 test fails)

[Debian Bug Tracking System]

Your message dated Wed, 14 Feb 2018 08:53:59 +
with message-id 
and subject line Bug#890318: fixed in util-linux 2.31.1-0.2
has caused the Debian Bug report #890318,
regarding util-linux: FTBFS on big endian - sha1/sha1 test fails
to be marked as done.

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

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


-- 
890318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890318
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: util-linux
Version: 2.31.1-0.1
Severity: serious
Tags: sid buster fixed-upstream

Hi,

util-linux FTBFS on all big endian architectures with this testsuite failure:>  
script: /«PKGBUILDDIR»/tests/ts/sha1/sha1
> sub dir: /«PKGBUILDDIR»/tests/ts/sha1
> top dir: /«PKGBUILDDIR»/tests
>self: /«PKGBUILDDIR»/tests/ts/sha1
>   test name: sha1
>   test desc: sha1
>   component: sha1
>   namespace: sha1/sha1
> verbose: yes
>  output: /«PKGBUILDDIR»/tests/output/sha1/sha1
>valgrind: /«PKGBUILDDIR»/tests/output/sha1/sha1.vgdump
>expected: /«PKGBUILDDIR»/tests/expected/sha1/sha1
>  mountpoint: /«PKGBUILDDIR»/tests/output/sha1/sha1-mnt
> 
>  sha1: sha1   ... FAILED (sha1/sha1)
> = script: /«PKGBUILDDIR»/tests/ts/sha1/sha1 =
> = OUTPUT =
>  19844f81e1408f6ecb932137d33bed7cfdcf518a3
>  214c20690f653fb16396e4f804c9dafb46e513d4f
>  3b39356f080492701e97317f88ca581acffae89cf
>  45e7c72295e61b1f0d733e6485bac4237b17d293a
>  597faba6b0f94c599ad7dd08a8801b7e7f4994b15
>  608b5f5340abf513bc11f824daea8828bb00c4541
>  76d49c77f9f4fbb8ef5fd4db0bd3cad4111dcf1c3
> = EXPECTED ===
>  1da39a3ee5e6b4b0d3255bfef95601890afd80709
>  2a9993e364706816aba3e25717850c26c9cd0d89d
>  3da3175a32e6c1aacfd3d3f35770188ae0ab6d078
>  47496226c17d4d0a770cea72eebb659c16753b956
>  5db50ea8b1b20567cd4d8a7fa14de8d37ce9b722c
>  690e072e1df8de879ca307610d5ced675af55a4ac
>  72eda696c8df17722d80518bebb33742e311a4ac1
> = O/E diff ===
> --- /«PKGBUILDDIR»/tests/output/sha1/sha1 2018-02-09 19:15:42.389991140 
> +
> +++ /«PKGBUILDDIR»/tests/expected/sha1/sha1   2017-12-21 14:44:24.0 
> +
> @@ -1,7 +1,7 @@
> -9844f81e1408f6ecb932137d33bed7cfdcf518a3
> -14c20690f653fb16396e4f804c9dafb46e513d4f
> -b39356f080492701e97317f88ca581acffae89cf
> -5e7c72295e61b1f0d733e6485bac4237b17d293a
> -97faba6b0f94c599ad7dd08a8801b7e7f4994b15
> -08b5f5340abf513bc11f824daea8828bb00c4541
> -6d49c77f9f4fbb8ef5fd4db0bd3cad4111dcf1c3
> +da39a3ee5e6b4b0d3255bfef95601890afd80709
> +a9993e364706816aba3e25717850c26c9cd0d89d
> +da3175a32e6c1aacfd3d3f35770188ae0ab6d078
> +7496226c17d4d0a770cea72eebb659c16753b956
> +db50ea8b1b20567cd4d8a7fa14de8d37ce9b722c
> +90e072e1df8de879ca307610d5ced675af55a4ac
> +2eda696c8df17722d80518bebb33742e311a4ac1
> ==

I think this if fixed by this upstream commit:

https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=4ff4b1106e8c6a71cce59ca40a2019342a92d47d

Thanks,
James



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: util-linux
Source-Version: 2.31.1-0.2

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

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated util-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: SHA256

Format: 1.8
Date: Tue, 13 Feb 2018 19:14:21 +0100
Source: util-linux
Binary: util-linux util-linux-locales mount bsdutils fdisk fdisk-udeb libblkid1 
libblkid1-udeb libblkid-dev libfdisk1 libfdisk1-udeb libfdisk-dev libmount1 
libmount1-udeb libmount-dev libsmartcols1 libsmartcols1-udeb libsmartcols-dev 
libuuid1 uuid-runtime libuuid1-udeb uuid-dev util-linux-udeb setpriv rfkill
Architecture: source

Bug#785044: marked as done (stardict: Should build-dep on libestools-dev instead of libestools2.0-dev)

[Debian Bug Tracking System]

Your message dated Wed, 14 Feb 2018 08:53:42 +
with message-id 
and subject line Bug#785044: fixed in stardict 3.0.1-9.4
has caused the Debian Bug report #785044,
regarding stardict: Should build-dep on libestools-dev instead of 
libestools2.0-dev
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.)


-- 
785044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785044
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: stardict
Version: 3.0.1-9.2
Severity: normal

Hello,

I have renamed the libestools2.1-dev package into libestools-dev.
Stardict should be building fine with its libestools2.0-dev build-dep
because libestools-dev provides it, but stardict should still be fixed
into explicitly build-depending on libestools-dev.

Thanks,
Samuel

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

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

-- 
Samuel
What's this script do?
unzip ; touch ; finger ; mount ; gasp ; yes ; umount ; sleep
Hint for the answer: not everything is computer-oriented. Sometimes you're
in a sleeping bag, camping out.
(Contributed by Frans van der Zande.)
--- End Message ---
--- Begin Message ---
Source: stardict
Source-Version: 3.0.1-9.4

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated stardict 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, 03 Feb 2018 08:35:40 +0200
Source: stardict
Binary: stardict stardict-gnome stardict-gtk stardict-plugin-espeak 
stardict-plugin-festival stardict-plugin-spell stardict-plugin stardict-common
Architecture: source
Version: 3.0.1-9.4
Distribution: unstable
Urgency: medium
Maintainer: Andrew Lee (李健秋) 
Changed-By: Adrian Bunk 
Description:
 stardict   - International dictionary
 stardict-common - International dictionary - data files
 stardict-gnome - International dictionary for GNOME 2
 stardict-gtk - International dictionary written in GTK+ 2.x
 stardict-plugin - International dictionary - common plugins
 stardict-plugin-espeak - International dictionary - eSpeak TTS plugin
 stardict-plugin-festival - International dictionary - Festival TTS plugin
 stardict-plugin-spell - International dictionary - spell plugin
Closes: 785044
Changes:
 stardict (3.0.1-9.4) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Update the build dependency from libestools2.0-dev
 to libestools-dev. (Closes: #785044)
Checksums-Sha1:
 f4b9dac6b6a4b110ad3e7909e912a27b800aaf37 2744 stardict_3.0.1-9.4.dsc
 08fff66d45d9051c0e4ca8b319b36f5c2a3ede30 31508 stardict_3.0.1-9.4.debian.tar.xz
Checksums-Sha256:
 02d51875ad6d90a12d2491a530e6d563a75df56109ff5f26d8438fee95419ddc 2744 
stardict_3.0.1-9.4.dsc
 f504b652229cff3f142bcdecca9e65e9bd58e79cb9765cc0ca1349dc741f690c 31508 
stardict_3.0.1-9.4.debian.tar.xz
Files:
 136ee97fee234e42cfb9f1f808230f05 2744 utils optional stardict_3.0.1-9.4.dsc
 efd8f52a08b64571db696b88e4bb995b 31508 utils optional 
stardict_3.0.1-9.4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlp1WmoACgkQiNJCh6LY
mLGyNg//dZjUbDDXbereWoU39GBfLGk3rc47l3pbd12SQaHu2OCfD6WSTN3vr6ee
AB3qHazqswv4A6jXmapGDXV1yc1td97P6ljAecMOuPyedeOXwV9kfT5esmAc5di6
7aKSaHnxGNKQL4y3Mz6bY/EhLHMdPEekK7sIUSmyxvKdrJT+lYp4pc4qLr5mb3UI
VtyAM+nDnx9EGMAutWzVOxrPG/mJqLP/vO4xLl4d/CG+f2o2oBOcsyr00IgDgieb
ltcCFT6RvZosf/s2/8ODyBDFvxxPour1hYu/hWiwiPkw2MhppnfYlR+GjJRaMmzZ
Jj93tMlvqKUr/VKVLVWsiTePcF6toaX2I3+RuStk3kT2eX6plk9kbP+/Bq+nix+K
K1R1FETz/mZgTN1MUFIQU6ZgCrazyaoAInZuLD7oJEAkPF99kUTeQd5H8m4GPa3P

Processed: Package never built on 32bit

[Debian Bug Tracking System]

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

> severity 890372 important
Bug #890372 [src:ddnet] ddnet: FTBFS on 32bit architectures
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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