Bug#876590: marked as done (uclmmbase FTBFS with gtk-doc-tools 1.26: gtkdoc-mktmpl is no longer available)

[Debian Bug Tracking System]

Your message dated Tue, 13 Feb 2018 06:30:15 +
with message-id 
and subject line Bug#889958: Removed package(s) from unstable
has caused the Debian Bug report #876590,
regarding uclmmbase FTBFS with gtk-doc-tools 1.26: gtkdoc-mktmpl is no longer 
available
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.)


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

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

...
make[2]: Entering directory '/build/1st/uclmmbase-1.2.16.0/doc'
gtkdoc-scan --module=uclmmbase --source-dir=../src
gtkdoc-mktmpl --module=uclmmbase
make[2]: gtkdoc-mktmpl: Command not found
Makefile:21: recipe for target 'tmpl' failed
make[2]: *** [tmpl] Error 127
--- End Message ---
--- Begin Message ---
Version: 1.2.16.0-2+rm

Dear submitter,

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

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

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

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

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

Bug#888471: marked as done (Please keep libsexy out of buster)

[Debian Bug Tracking System]

Your message dated Tue, 13 Feb 2018 06:32:29 +
with message-id 
and subject line Bug#890248: Removed package(s) from unstable
has caused the Debian Bug report #888471,
regarding Please keep libsexy out of buster
to be marked as done.

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

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


-- 
888471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888471
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libsexy
Version: 0.1.11-4
Severity: serious

Hi,

I guess that libsexy should not be part of buster.

The package only seems to be used by xchat. Xchat could switch to
gtkspell I guess?

Kind 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-3-amd64 (SMP w/4 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)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
--- End Message ---
--- Begin Message ---
Version: 0.1.11-4+rm

Dear submitter,

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

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

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

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

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

Bug#888095:

[Andy Li]

This has been affecting neko (https://tracker.debian.org/pkg/neko) for a
while.
Would you fix it soonish?

Best regards,
Andy

Bug#858844: marked as done (cobbler: CVE-2016-9605: Cross site scripting in profile page)

[Debian Bug Tracking System]

Your message dated Tue, 13 Feb 2018 06:21:21 +
with message-id 
and subject line Bug#889099: Removed package(s) from unstable
has caused the Debian Bug report #858844,
regarding cobbler: CVE-2016-9605: Cross site scripting in profile page
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.)


-- 
858844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858844
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cobbler
Version: 2.6.6+dfsg1-13
Severity: grave
Tags: security upstream

Hi,

the following vulnerability was published for cobbler.

CVE-2016-9605[0]:
Cross site scripting in profile page

AFAICT and from the corresponding Red Hat bugzilla entries, the
problematic code has been introduced in 2.6. I was not able to set up
a corresponding working cobbler instance.

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-2016-9605
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9605
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1433950
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1399333

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Version: 2.6.6+dfsg1-13+rm

Dear submitter,

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

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

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

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

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

Bug#856856: marked as done (cobbler-web: Doesn't run out of the box with Django 1.10)

[Debian Bug Tracking System]

Your message dated Tue, 13 Feb 2018 06:21:21 +
with message-id 
and subject line Bug#889099: Removed package(s) from unstable
has caused the Debian Bug report #856856,
regarding cobbler-web: Doesn't run out of the box with Django 1.10
to be marked as done.

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

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


-- 
856856: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856856
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cobbler-web
Version: 2.6.6+dfsg1-13
Severity: important

The cobbler-web package appears to assume an earlier django version and
breaks on version 1.10 which is currently in Stretch.  500 Server error.

I've made the following changes in an effort to workaround, but given up
as didn't look like it was going to be a quick fix...  Haven't checked
upstream git to see if this has already been done...

in  /usr/share/cobbler-common/web/settings.py


TEMPLATES = [
{
'BACKEND': 'django.template.backends.django.DjangoTemplates',
'DIRS': [
'/usr/share/cobbler/web/templates',
],
'APP_DIRS': True,
'OPTIONS': {
'context_processors': [
'django.core.context_processors.request',
],
},
},
]

ALLOWED_HOSTS = ['cobbler.mydomain']

and have commented out:

#from django.conf.global_settings import TEMPLATE_CONTEXT_PROCESSORS
#
#TEMPLATE_CONTEXT_PROCESSORS += (
# 'django.core.context_processors.request',
#) 

... sources were: 
https://review.fuel-infra.org/gitweb?p=packages%2Fcentos7%2Fcobbler.git;a=commitdiff;h=234bb8912faacdc1840d00e67caf8833d12ab502

and https://docs.djangoproject.com/en/1.10/ref/templates/upgrading/


In /usr/share/cobbler-common/web/urls.py :


from django.conf.urls import include, url

urlpatterns=[
url(r'^', include('cobbler_web.urls')),
]

reference: 
http://stackoverflow.com/questions/38786036/importerror-cannot-import-name-patterns




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

Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Version: 2.6.6+dfsg1-13+rm

Dear submitter,

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

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

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

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

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

Bug#855077: marked as done (azure-cli: Running az command fails with error)

[Debian Bug Tracking System]

Your message dated Tue, 13 Feb 2018 06:19:08 +
with message-id 
and subject line Bug#889081: Removed package(s) from unstable
has caused the Debian Bug report #855077,
regarding azure-cli: Running az command fails with 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.)


-- 
855077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: azure-cli
Version: 0.1.0~b7-1
Severity: important

Dear Maintainer,

   * What led up to the situation?

After installing 'azure-cli', running the 'az' command fails with an error.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

$ az
Error loading command module 'storage'
__init__() got multiple values for keyword argument 'default_completer'
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/azure/cli/main.py", line 35, in main
cmd_result = APPLICATION.execute(args)
  File "/usr/lib/python3/dist-packages/azure/cli/core/application.py", line 84, 
in execute
self.parser.load_command_table(command_table)
  File "/usr/lib/python3/dist-packages/azure/cli/core/parser.py", line 91, in 
load_command_table
enable_autocomplete(self)
  File "/usr/lib/python3/dist-packages/azure/cli/core/parser.py", line 34, in 
enable_autocomplete
argcomplete.autocomplete(parser, validator=lambda c, p: 
c.lower().startswith(p.lower()))
  File "/usr/lib/python3/dist-packages/argcomplete/__init__.py", line 166, in 
__call__
default_completer=default_completer)
  File "/usr/lib/python3/dist-packages/azure/cli/core/parser.py", line 30, in 
__init__
**kwargs)
TypeError: __init__() got multiple values for keyword argument 
'default_completer'

   * What was the outcome of this action?

An error loading hte command module 'storage'.

   * What outcome did you expect instead?

The azure cli to start

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

Kernel: Linux 4.8.6-x86_64-linode78 (SMP w/1 CPU core)
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 azure-cli depends on:
ii  python3-adal 0.4.4-1
ii  python3-applicationinsights  0.10.0-2
ii  python3-argcomplete  1.8.1-1
ii  python3-azure2.0.0~rc6+dfsg-2
ii  python3-colorama 0.3.7-1
ii  python3-jmespath 0.9.0-2
ii  python3-msrest   0.4.4-1
ii  python3-msrestazure  0.4.7-1
ii  python3-pip  9.0.1-2
ii  python3-pygments 2.2.0+dfsg-1
ii  python3-requests 2.12.4-1
ii  python3-six  1.10.0-3
ii  python3-tabulate 0.7.7-1
ii  python3-urllib3  1.19.1-1
ii  python3-yaml 3.12-1
pn  python3:any  

azure-cli recommends no packages.

azure-cli suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.1.0~b7-1+rm

Dear submitter,

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

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

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

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

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

Bug#867506: marked as done (azure-cli FTBFS: ImportError: No module named 'setuptools')

[Debian Bug Tracking System]

Your message dated Tue, 13 Feb 2018 06:19:08 +
with message-id 
and subject line Bug#889081: Removed package(s) from unstable
has caused the Debian Bug report #867506,
regarding azure-cli FTBFS: ImportError: No module named 'setuptools'
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.)


-- 
867506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867506
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: azure-cli
Version: 0.1.0~b7-1
Severity: serious

Some recent change in unstable makes azure-cli FTBFS:

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

...
   debian/rules override_dh_auto_clean
make[1]: Entering directory '/build/1st/azure-cli-0.1.0~b7'
for MODULE in src/azure-cli src/azure-cli-core 
src/command_modules/azure-cli-component/ 
src/command_modules/azure-cli-configure/ 
src/command_modules/azure-cli-feedback/ src/command_modules/azure-cli-iot/ 
src/command_modules/azure-cli-keyvault/ src/command_modules/azure-cli-network/ 
src/command_modules/azure-cli-profile/ src/command_modules/azure-cli-redis/ 
src/command_modules/azure-cli-resource/ src/command_modules/azure-cli-role/ 
src/command_modules/azure-cli-storage/ src/command_modules/azure-cli-taskhelp/ 
src/command_modules/azure-cli-vm/ src/command_modules/azure-cli-webapp/; do \
( cd $MODULE; python3 setup.py clean ); \
done
Traceback (most recent call last):
  File "setup.py", line 10, in 
from setuptools import setup
ImportError: No module named 'setuptools'
Traceback (most recent call last):
  File "setup.py", line 10, in 
from setuptools import setup
ImportError: No module named 'setuptools'
Traceback (most recent call last):
  File "setup.py", line 9, in 
from setuptools import setup
ImportError: No module named 'setuptools'
Traceback (most recent call last):
  File "setup.py", line 9, in 
from setuptools import setup
ImportError: No module named 'setuptools'
Traceback (most recent call last):
  File "setup.py", line 9, in 
from setuptools import setup
ImportError: No module named 'setuptools'
Traceback (most recent call last):
  File "setup.py", line 9, in 
from setuptools import setup
ImportError: No module named 'setuptools'
Traceback (most recent call last):
  File "setup.py", line 10, in 
from setuptools import setup
ImportError: No module named 'setuptools'
Traceback (most recent call last):
  File "setup.py", line 9, in 
from setuptools import setup
ImportError: No module named 'setuptools'
Traceback (most recent call last):
  File "setup.py", line 9, in 
from setuptools import setup
ImportError: No module named 'setuptools'
Traceback (most recent call last):
  File "setup.py", line 10, in 
from setuptools import setup
ImportError: No module named 'setuptools'
Traceback (most recent call last):
  File "setup.py", line 9, in 
from setuptools import setup
ImportError: No module named 'setuptools'
Traceback (most recent call last):
  File "setup.py", line 9, in 
from setuptools import setup
ImportError: No module named 'setuptools'
Traceback (most recent call last):
  File "setup.py", line 9, in 
from setuptools import setup
ImportError: No module named 'setuptools'
Traceback (most recent call last):
  File "setup.py", line 9, in 
from setuptools import setup
ImportError: No module named 'setuptools'
Traceback (most recent call last):
  File "setup.py", line 9, in 
from setuptools import setup
ImportError: No module named 'setuptools'
Traceback (most recent call last):
  File "setup.py", line 9, in 
from setuptools import setup
ImportError: No module named 'setuptools'
debian/rules:24: recipe for target 'override_dh_auto_clean' failed
make[1]: *** [override_dh_auto_clean] Error 1
--- End Message ---
--- Begin Message ---
Version: 0.1.0~b7-1+rm

Dear submitter,

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

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

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

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the 

Bug#805217: marked as done (passepartout: FTBFS: fatal error: sigc++/object.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Tue, 13 Feb 2018 06:08:07 +
with message-id 
and subject line Bug#888920: Removed package(s) from unstable
has caused the Debian Bug report #805217,
regarding passepartout: FTBFS: fatal error: sigc++/object.h: No such file or 
directory
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.)


-- 
805217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805217
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: passepartout
Version: 0.7.1-1.1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

In file included from processman.cc:4:0:
processman.h:9:27: fatal error: sigc++/object.h: No such file or directory
compilation terminated.
Makefile:283: recipe for target 'processman.o' failed
make[4]: *** [processman.o] Error 1
make[4]: Leaving directory '/passepartout-0.7.1/src/util'
Makefile:222: recipe for target 'all-recursive' failed

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/passepartout.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Version: 0.7.1-1.1+rm

Dear submitter,

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

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

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

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

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

Bug#889028: minissdpd (1.5.20161216-2) assumes IPV6

[M. Klonner]

Package: minissdpd
Version: 1.5.20161216-2
Followup-For: Bug #889028

Dear Maintainer,

During dist-upgrade minissdpd failed to install. It seems to try opening an 
IPV6 socket. 

-- Error message from apt:
Setting up minissdpd (1.5.20161216-2) ...
Job for minissdpd.service failed because the control process exited with 
error code.
See "systemctl status minissdpd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript minissdpd, action "restart" failed.
● minissdpd.service - keep memory of all UPnP devices that announced 
themselves
   Loaded: loaded (/lib/systemd/system/minissdpd.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Sat 2018-02-10 16:29:47 CET; 
14ms ago
 Docs: man:minissdpd(1)
  Process: 3450 ExecStart=/usr/sbin/minissdpd -i 
$MiniSSDPd_INTERFACE_ADDRESS $MiniSSDPd_OTHER_OPTIONS (code=exited, 
status=1/FAILURE)
 Main PID: 966 (code=exited, status=0/SUCCESS)

Feb 10 16:29:47 Bantiger systemd[1]: Starting keep memory of all UPnP 
devices that announced themselves...
Feb 10 16:29:47 Bantiger minissdpd[3450]: socket(udp): Address family not 
supported by protocol
Feb 10 16:29:47 Bantiger minissdpd[3450]: Cannot open socket for receiving 
SSDP messages (IPv6), exiting
Feb 10 16:29:47 Bantiger systemd[1]: minissdpd.service: Control process 
exited, code=exited status=1
Feb 10 16:29:47 Bantiger minissdpd[3450]: unlink(/var/run/minissdpd.pid): 
No such file or directory
Feb 10 16:29:47 Bantiger systemd[1]: minissdpd.service: Failed with result 
'exit-code'.
Feb 10 16:29:47 Bantiger systemd[1]: Failed to start keep memory of all 
UPnP devices that announced themselves.
dpkg: error processing package minissdpd (--configure):
 installed minissdpd package post-installation script subprocess returned 
error exit status 1
Processing triggers for libc-bin (2.26-4) ...
Errors were encountered while processing:
 minissdpd
E: Sub-process /usr/bin/dpkg returned an error code (1)



-- 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=en, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages minissdpd depends on:
ii  libc6  2.26-4
ii  libnfnetlink0  1.0.1-3+b1
ii  lsb-base   9.20170808

minissdpd recommends no packages.

minissdpd suggests no packages.

-- no debconf information

Bug#877038: marked as done (libavahi-ui0.0-cil depends on obsolete package libavahi-ui0)

[Debian Bug Tracking System]

Your message dated Tue, 13 Feb 2018 06:05:53 +
with message-id 
and subject line Bug#888790: Removed package(s) from unstable
has caused the Debian Bug report #877038,
regarding libavahi-ui0.0-cil depends on obsolete package libavahi-ui0
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.)


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

Package: libavahi-ui0.0-cil
Severity: serious
Tags: buster sid

libavahi-ui0.0-cil depends on libavahi-ui0 which has been dropped by the avahi 
source package.
--- End Message ---
--- Begin Message ---
Version: 0.6.19-4.3+rm

Dear submitter,

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

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

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

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

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

Bug#866632: marked as done (bibledit-gtk: depends on libwebkitgtk-1.0-0 which is deprecated)

[Debian Bug Tracking System]

Your message dated Tue, 13 Feb 2018 06:06:57 +
with message-id 
and subject line Bug#33: Removed package(s) from unstable
has caused the Debian Bug report #866632,
regarding bibledit-gtk: depends on libwebkitgtk-1.0-0 which is deprecated
to be marked as done.

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

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


-- 
866632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866632
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bibledit-gtk
Severity: serious
Tags: sid buster
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs libwebkitgtk-1.0-0 webkit1

Hi,

bibledit-gtk depends on libwebkitgtk-1.0-0, which is deprecated in
favor of libwebkit2gtk-4.0-37 (provided in Debian by webkit2gtk).
bibledit-gtk should be ported to the new webkitgtk version so we can
remove the old, unmaintained one.

Please try to do soon as we're going to try to remove the old webkitgtk soon.

I am filing this bug as "serious" since the old webkitgtk will not be
available in the next major stable release of Debian (codenamed
"buster").

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

On behalf of the Debian WebKit Maintainers,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 4.9-1+rm

Dear submitter,

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

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

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

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

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

Bug#724867: marked as done (Main window is empty, apparent busy-loop)

[Debian Bug Tracking System]

Your message dated Tue, 13 Feb 2018 06:03:05 +
with message-id 
and subject line Bug#870987: Removed package(s) from unstable
has caused the Debian Bug report #724867,
regarding Main window is empty, apparent busy-loop
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.)


-- 
724867: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724867
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vuze
Version: 4.3.0.6-5
Severity: grave

Currently, starting vuze results in a big empty window and the vuze
process using ~80% of the time of one CPU.

I tried renaming ~/.azureus in order to start with a fresh
configuration, but this was still reproducible.

Ben.

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

Kernel: Linux 3.10-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages vuze depends on:
ii  azureus  4.3.0.6-5
ii  libswt-cairo-gtk-3-jni   3.8.2-3
ii  libswt-gnome-gtk-3-jni   3.8.2-3
ii  libswt-webkit-gtk-3-jni  3.8.2-3

vuze recommends no packages.

vuze suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 4.3.0.6-5+rm

Dear submitter,

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

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

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

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

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

Bug#813185: marked as done (pygoocanvas is deprecated)

[Debian Bug Tracking System]

Your message dated Tue, 13 Feb 2018 06:03:31 +
with message-id 
and subject line Bug#879053: Removed package(s) from unstable
has caused the Debian Bug report #813185,
regarding pygoocanvas is deprecated
to be marked as done.

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

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


-- 
813185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813185
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pygoocanvas
Severity: wishlist

Hi,

Pygoocanvas is deprecated and not maintained upstream. The Debian maintainer
(Jose Carlos Garcia Sogo) is not currently active.

There are several reverse dependencies. I have submitted wishlist bugs
requesting that these programs move away from pygoocanvas, to the more recent
gobject introspection goocanvas package (gir1.2-goocanvas-2.0).

Once this occurs, pygoocanvas should be removed from the archive.

Regards,

Ross



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

Kernel: Linux 4.2.0-25-generic (SMP w/4 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)
--- End Message ---
--- Begin Message ---
Version: 0.14.1-1.3+rm

Dear submitter,

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

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

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

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

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

Bug#793492: marked as done (Should this package be removed?)

[Debian Bug Tracking System]

Your message dated Tue, 13 Feb 2018 06:03:05 +
with message-id 
and subject line Bug#870987: Removed package(s) from unstable
has caused the Debian Bug report #793492,
regarding Should this package be removed?
to be marked as done.

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

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


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

The version of azureus currently in the archive has been uploaded
in 2009 and it many upstream releases behind. It has been dropped
from testing back in 2013 and the last upload was in 2011. Since
there's apparently no current maintenance interest in Vuze/Azureus
and since there are plenty of other Torrent clients in Debian I
suggest we remove it from the archive.

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

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Version: 4.3.0.6-5+rm

Dear submitter,

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

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

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

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

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

Bug#814176: marked as done (azureus: (Build-)Depends on OpenJDK 7)

[Debian Bug Tracking System]

Your message dated Tue, 13 Feb 2018 06:03:05 +
with message-id 
and subject line Bug#870987: Removed package(s) from unstable
has caused the Debian Bug report #814176,
regarding azureus: (Build-)Depends on OpenJDK 7
to be marked as done.

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

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


-- 
814176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814176
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:azureus
Version: 4.3.0.6-5
Severity: serious
User: debian-j...@lists.debian.org
Usertags: openjdk-8-transition

The package build-depends or depends one an openjdk-7-* package,
which is scheduled for removal for stretch.  Please do not depend
on a specific openjdk version, but on one of the default-java,
default-java-headless or default-jdk packages instead.

default-java defaulting to openjdk-8 on most architectures is now
available in unstable.
--- End Message ---
--- Begin Message ---
Version: 4.3.0.6-5+rm

Dear submitter,

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

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

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

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

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

Processed: #890287 and #890288 are upstream bugs

[Debian Bug Tracking System]

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

> tags 890287 upstream
Bug #890287 [src:mbedtls] mbedtls: CVE-2018-0488 - Risk of remote code 
execution when truncated HMAC is enabled
Added tag(s) upstream.
> tags 890288 upstream
Bug #890288 [src:mbedtls] mbedtls: CVE-2018-0487 - Risk of remote code 
execution when verifying RSASSA-PSS signatures
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#890289: bibledit: embeds mbedtls - vulnerable to CVE-2017-2784, CVE-2017-14032, CVE-2018-0487, CVE-2018-0488

[James Cowgill]

Source: bibledit
Version: 5.0.331-1
Severity: grave
Tags: security

Hi,

I notice bibledit embeds mbed TLS 2.2.1. The embedded version is
vulnerable to at least these CVEs (based on the version number and
assuming they have not been manually patched):
 CVE-2017-2784
 CVE-2017-14032
 CVE-2018-0487
 CVE-2018-0488

[disclaimer: the mbedtls package is still vulnerable to the last two,
but I am working on fixing those]

I see you have overridden lintian which warns you about this:
> # For just now the mbed TLS library is included.
> # When using the system-provided libmbedtls, there currently is a 
> segmentation fault.
> # Pending investigation of this fault, temporarily include mbed TLS.
> # Here is the link to the issue: 
> https://github.com/bibledit/bibledit/issues/499
> # By the way, isn't it called "mbed" TLS, obviously intended to be "embedded"?
> # So Bibledit is doing that right now, it "embeds" mbed TLS.
> bibledit: embedded-library usr/bin/bibledit: mbedtls

"mbed" is the brand name ARM uses for its IOT operating system (of which
mbedtls is a component) and therefore is derived from "embedded systems".

IMO embedding a security library is unacceptable and the package should
not be in a stable release in its current state.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#890288: mbedtls: CVE-2018-0487 - Risk of remote code execution when verifying RSASSA-PSS signatures

[James Cowgill]

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

Bug#890287: mbedtls: CVE-2018-0488 - Risk of remote code execution when truncated HMAC is enabled

[James Cowgill]

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

Processed: delayed NMU of auto-complete-el/1.5.1-0.1

[Debian Bug Tracking System]

Processing control commands:

> Tag -1 patch
Bug #886161 [auto-complete-el] auto-complete-el: extremely outdated, blocks 
packaging of new Emacs packages
Added tag(s) patch.

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

Bug#886161: delayed NMU of auto-complete-el/1.5.1-0.1

[Hilko Bengen]

Control: Tag -1 patch

Hi Takaya,

I have prepared a package based on the current upstream version 1.5.1 of
auto-complete and uploaded to DELAYED/5. I have gone ahead and fixed
most of the outstanding bugs and modernized the package: It is now based
on dh-elpa.

Please feel free to cancel or reschedule as you see fit.

What do you think about maintaining the auto-complete-el as part of the
Debian Emacs addons team?

Cheers,
-Hilko


auto-complete-el_1.5.1-0.1_source.changes
Description: Binary data

Bug#884061: This bug severely affects anybody using intel graphics cards from 2015

[Vagrant Cascadian]

Control: fixed 884061 4.9.80-1

On 2018-01-22, Marga Manterola wrote:
> This bug can make machines that include the affected graphics card
> completely unusable.
...
> Any chance we can get a new kernel without that commit?

I can confirm 4.9.80-1 from stretch-proposed-updates fixes the issue for
me. I've been running it for several days without issue.

It appears 4.9.80-2 is out now as well.

Not sure how long till the next point release, but at least one can use
stretch-proposed-updates for now.

Thanks to everyone who helped resolve the issue!


live well,
  vagrant


signature.asc
Description: PGP signature

Processed: Re: Bug#884061: This bug severely affects anybody using intel graphics cards from 2015

[Debian Bug Tracking System]

Processing control commands:

> fixed 884061 4.9.80-1
Bug #884061 {Done: Yves-Alexis Perez } [src:linux] 
linux-image-4.9.0-4-amd64: screen scrolls wildly
Bug #883980 {Done: Yves-Alexis Perez } [src:linux] 
base-files: After updating to 9.3, Screen Sporadically Goes Blank
Bug #884001 {Done: Yves-Alexis Perez } [src:linux] 
linux-image-4.9.0-4-amd64: Severe graphics corruption on intel graphics after 
kernel upgrade
Bug #884116 {Done: Yves-Alexis Perez } [src:linux] 
linux-image-4.9.0-4-amd64: screen atrifacts then crash
Bug #885570 {Done: Yves-Alexis Perez } [src:linux] 
linux-image-4.9.0-4-amd64: display breakage with Intel HD Graphics 5500
Ignoring request to alter fixed versions of bug #884061 to the same values 
previously set
Ignoring request to alter fixed versions of bug #883980 to the same values 
previously set
Ignoring request to alter fixed versions of bug #884001 to the same values 
previously set
Ignoring request to alter fixed versions of bug #884116 to the same values 
previously set
Ignoring request to alter fixed versions of bug #885570 to the same values 
previously set

-- 
883980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883980
884001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884001
884061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884061
884116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884116
885570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885570
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#889913: marked as done (alot FTBFS with python-magic 2:0.4.15-1)

[Debian Bug Tracking System]

Your message dated Mon, 12 Feb 2018 21:04:23 +
with message-id 
and subject line Bug#889293: fixed in alot 0.6-2.1
has caused the Debian Bug report #889293,
regarding alot FTBFS with python-magic 2:0.4.15-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.)


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

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

...
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py test 
running test
Searching for file-magic

Note: Bypassing https://pypi.python.org/simple/file-magic/ (disallowed host; 
see http://bit.ly/2hrImnY for details).

Couldn't find index page for 'file-magic' (maybe misspelled?)
Scanning index of all packages (this may take a while)

Note: Bypassing https://pypi.python.org/simple/ (disallowed host; see 
http://bit.ly/2hrImnY for details).

No local packages or working download links found for file-magic
error: Could not find suitable distribution for Requirement.parse('file-magic')
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: 
python2.7 setup.py test 
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
debian/rules:10: recipe for target 'build' failed
make: *** [build] Error 25
--- End Message ---
--- Begin Message ---
Source: alot
Source-Version: 0.6-2.1

We believe that the bug you reported is fixed in the latest version of
alot, 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 report if appropriate.

Debian distribution maintenance software
pp.
Christoph Biedl  (supplier of updated alot 
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, 04 Feb 2018 18:24:59 +0100
Source: alot
Binary: alot alot-doc
Architecture: source all
Version: 0.6-2.1
Distribution: unstable
Urgency: high
Maintainer: Python Applications Packaging Team 

Changed-By: Christoph Biedl 
Description:
 alot   - Text mode MUA using notmuch mail
 alot-doc   - Text mode MUA using notmuch mail - documentation
Closes: 889293
Changes:
 alot (0.6-2.1) unstable; urgency=high
 .
   * Non-maintainer upload
   * Drop "Use file-magic instead of python-magic" patch. Closes: #889293
Checksums-Sha1:
 51d30b71514f7679d44768201f2382741739e1aa 2279 alot_0.6-2.1.dsc
 9c94974923d69f6c61645cc753593b2bf80edf29 6592 alot_0.6-2.1.debian.tar.xz
 86b0a69f47a62d483ae3994322e828e27392ef05 111568 alot-doc_0.6-2.1_all.deb
 75b67a9159aff416094f56c22473b73370551847 98232 alot_0.6-2.1_all.deb
 bf700c1be08818c04373434b48a8cf5a477b1b82 8782 alot_0.6-2.1_powerpc.buildinfo
Checksums-Sha256:
 e26e1ac28e0331761ace7f8a513cb063ba5dc8a67a872b5984be4125aa769623 2279 
alot_0.6-2.1.dsc
 41a221558d1d662a401780195780bd8e3d628d1413c8ce122922f54e92bc1512 6592 
alot_0.6-2.1.debian.tar.xz
 777a85bfe0bb6af19cbb72e2824a409d5ceb22c022606fa20373a761d4140814 111568 
alot-doc_0.6-2.1_all.deb
 80f2a369126de7df721afa4c8e894db58f59e32771fc98f4c898ad3d63b499cb 98232 
alot_0.6-2.1_all.deb
 02917a9355608c8d0ffac7643e8749cd409504a18eae177755ec45938ddee972 8782 
alot_0.6-2.1_powerpc.buildinfo
Files:
 a7668c4e823c58906a1f1acb03957f66 2279 mail optional alot_0.6-2.1.dsc
 f40aa9508ea345f22cee010ff27400d3 6592 mail optional alot_0.6-2.1.debian.tar.xz
 40e82003f80f5c5982bb75a7bbcef763 111568 doc optional alot-doc_0.6-2.1_all.deb
 87174314f0c8389214332ac8f21d4921 98232 mail optional alot_0.6-2.1_all.deb
 7285cb5bc566ffea98c1e47170cb16c1 8782 mail optional 
alot_0.6-2.1_powerpc.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEWXMI+726A12MfJXdxCxY61kUkv0FAlp4pcAACgkQxCxY61kU
kv0+WQ//YE/Z517d0ibs/+w/c7nEgAXjNV6YQCYhH+NjIsmSeMzQ/A5biRnbJebr
GYZvX5fl1n4RBNxrroybWNZJUa76elxH81HiZ2pSbk34sOZpeAYV14rxowDv3Ju0
V1c/r2rABrAjm/Uq/a/l+k5Dl109MrJADd0Ob2PUcUAUHl5NVlOHVr3WPU7rkatX
ZxrynmdAT7PpBRIyMaIgQ/XRghDAHZi27nuyG0JOhZcdMVrdmPuj4qIuzo5PEndK

Bug#889293: marked as done (alot: FTBFS: Please drop "Use file-magic instead of python-magic" patch)

[Debian Bug Tracking System]

Your message dated Mon, 12 Feb 2018 21:04:23 +
with message-id 
and subject line Bug#889293: fixed in alot 0.6-2.1
has caused the Debian Bug report #889293,
regarding alot: FTBFS: Please drop "Use file-magic instead of python-magic" 
patch
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.)


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

python-magic maintainer here ...

Dear Maintainer,

as announced in debian-devel two weeks ago, the python-magic libary
will switch upstream, from the one provided by src:file to the one
found in PyPI, written by Adam Hupp.

A rebuild of the known rdeps showed src:alot will no longer build then.
Since however alot is currently patched to work with the file-based
implementation, this can easily be cured by just dropping that patch.

The new python-magic implementation will hit unstable very soon,
causing your package to FTBFS. So I'm asking you to prepare for this by

* droping 0002-debian-Use-file-magic-instead-of-python-magic-in-set.patch,
* adding a versioned build dependency on python-magic (>= 2:0.4.15) as
  a hint for backporters

Sorry if this is a bit on short notice.

Christoph



signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: alot
Source-Version: 0.6-2.1

We believe that the bug you reported is fixed in the latest version of
alot, 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 report if appropriate.

Debian distribution maintenance software
pp.
Christoph Biedl  (supplier of updated alot 
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, 04 Feb 2018 18:24:59 +0100
Source: alot
Binary: alot alot-doc
Architecture: source all
Version: 0.6-2.1
Distribution: unstable
Urgency: high
Maintainer: Python Applications Packaging Team 

Changed-By: Christoph Biedl 
Description:
 alot   - Text mode MUA using notmuch mail
 alot-doc   - Text mode MUA using notmuch mail - documentation
Closes: 889293
Changes:
 alot (0.6-2.1) unstable; urgency=high
 .
   * Non-maintainer upload
   * Drop "Use file-magic instead of python-magic" patch. Closes: #889293
Checksums-Sha1:
 51d30b71514f7679d44768201f2382741739e1aa 2279 alot_0.6-2.1.dsc
 9c94974923d69f6c61645cc753593b2bf80edf29 6592 alot_0.6-2.1.debian.tar.xz
 86b0a69f47a62d483ae3994322e828e27392ef05 111568 alot-doc_0.6-2.1_all.deb
 75b67a9159aff416094f56c22473b73370551847 98232 alot_0.6-2.1_all.deb
 bf700c1be08818c04373434b48a8cf5a477b1b82 8782 alot_0.6-2.1_powerpc.buildinfo
Checksums-Sha256:
 e26e1ac28e0331761ace7f8a513cb063ba5dc8a67a872b5984be4125aa769623 2279 
alot_0.6-2.1.dsc
 41a221558d1d662a401780195780bd8e3d628d1413c8ce122922f54e92bc1512 6592 
alot_0.6-2.1.debian.tar.xz
 777a85bfe0bb6af19cbb72e2824a409d5ceb22c022606fa20373a761d4140814 111568 
alot-doc_0.6-2.1_all.deb
 80f2a369126de7df721afa4c8e894db58f59e32771fc98f4c898ad3d63b499cb 98232 
alot_0.6-2.1_all.deb
 02917a9355608c8d0ffac7643e8749cd409504a18eae177755ec45938ddee972 8782 
alot_0.6-2.1_powerpc.buildinfo
Files:
 a7668c4e823c58906a1f1acb03957f66 2279 mail optional alot_0.6-2.1.dsc
 f40aa9508ea345f22cee010ff27400d3 6592 mail optional alot_0.6-2.1.debian.tar.xz
 40e82003f80f5c5982bb75a7bbcef763 111568 doc optional alot-doc_0.6-2.1_all.deb
 87174314f0c8389214332ac8f21d4921 98232 mail optional alot_0.6-2.1_all.deb
 7285cb5bc566ffea98c1e47170cb16c1 8782 mail optional 
alot_0.6-2.1_powerpc.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEWXMI+726A12MfJXdxCxY61kUkv0FAlp4pcAACgkQxCxY61kU
kv0+WQ//YE/Z517d0ibs/+w/c7nEgAXjNV6YQCYhH+NjIsmSeMzQ/A5biRnbJebr
GYZvX5fl1n4RBNxrroybWNZJUa76elxH81HiZ2pSbk34sOZpeAYV14rxowDv3Ju0
V1c/r2rABrAjm/Uq/a/l+k5Dl109MrJADd0Ob2PUcUAUHl5NVlOHVr3WPU7rkatX
ZxrynmdAT7PpBRIyMaIgQ/XRghDAHZi27nuyG0JOhZcdMVrdmPuj4qIuzo5PEndK
vU/KB830BYUhy1ne6eTAmhF+qLCIG2x6w5dXoQa5qooj1U4z8sqy+Im9ImU27o5M

Bug#835542: marked as done (flex: comparison between signed and unsigned integer expressions)

[Debian Bug Tracking System]

Your message dated Mon, 12 Feb 2018 21:05:04 +
with message-id 
and subject line Bug#835542: fixed in flex 2.6.4-1
has caused the Debian Bug report #835542,
regarding flex: comparison between signed and unsigned integer expressions
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.)


-- 
835542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835542
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: flex
Version: 2.5.39-8+deb8u1
Severity: normal

After this update, I get the following warning when compiling the
flex generated code with gcc, which I didn't get before:

scan.cpp: In function ‘int yy_get_next_buffer(yyscan_t)’:
scan.cpp:758:18: error: comparison between signed and unsigned integer 
expressions [-Werror=sign-compare]
scan.cpp:1384:3: note: in expansion of macro ‘YY_INPUT’

Looking at the code:

#define YY_INPUT(buf,result,max_size) \
if ( YY_CURRENT_BUFFER_LVALUE->yy_is_interactive ) \
{ \
int c = '*'; \
size_t n; \
for ( n = 0; n < max_size && \

Invoked as:

int num_to_read = ...
YY_INPUT( (_CURRENT_BUFFER_LVALUE->yy_ch_buf[number_to_move]),
yyg->yy_n_chars, num_to_read );

So indeed an unsigned value (n) is compared with a signed one
(num_to_read). If this is correct, the warning can be silenced with
a cast of the appropriate one of them.

flex hasn't exactly been known for generating warning-free code,
but what really worries me is that this is a security update. Fixing
a security problem by introducing a sign-problem seems fishy to me.

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

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

Versions of packages flex depends on:
ii  debconf [debconf-2.0]  1.5.56
ii  dpkg   1.17.27
ii  install-info   5.2.0.dfsg.1-6
ii  libc6  2.19-18+deb8u5
ii  libfl-dev  2.5.39-8+deb8u1
ii  m4 1.4.17-4

Versions of packages flex recommends:
ii  clang-3.5 [c-compiler]  1:3.5-10
ii  gcc [c-compiler]4:4.9.2-2
ii  gcc-4.8 [c-compiler]4.8.4-1
ii  gcc-4.9 [c-compiler]4.9.2-10

Versions of packages flex suggests:
ii  bison2:3.0.2.dfsg-2
ii  build-essential  11.7

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: flex
Source-Version: 2.6.4-1

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

Debian distribution maintenance software
pp.
Manoj Srivastava  (supplier of updated flex 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, 12 Feb 2018 11:19:29 -0800
Source: flex
Binary: flex flex-doc libfl-dev
Architecture: source amd64 all
Version: 2.6.4-1
Distribution: unstable
Urgency: medium
Maintainer: Manoj Srivastava 
Changed-By: Manoj Srivastava 
Description:
 flex   - fast lexical analyzer generator
 flex-doc   - Documentation for flex (a fast lexical analyzer generator)
 libfl-dev  - static library for flex (a fast lexical analyzer generator)
Closes: 835542 851675 856956
Changes:
 flex (2.6.4-1) unstable; urgency=medium
 .
   * New upstream version. Notable changes
 + a segfalt involving yyrestart(NULL) has been fixed
 + flex should now handle quoting when mixed with m4 processing correctly
 + flex handles `[[' and `]]' correctly
 + flex no longer generates non-ANSI code
 + more compilation warnings were squashed in generated scanners
 + prevented a buffer overflow that could occur when input buffers were
   the exact wrong size
 + several bug fixes resolved problems introduced in recent flex
   versions regarding processing of comments, 

Processed: tagging 877257

[Debian Bug Tracking System]

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

> tags 877257 + buster sid experimental
Bug #877257 [src:ruby-grape] ruby-grape: FTBFS with ruby2.3 and ruby-rack-test 
0.7
Bug #890257 [src:ruby-grape] ruby-grape: FTBFS with ruby2.3 and ruby-rack-test 
0.7
Added tag(s) buster, experimental, and sid.
Added tag(s) sid, experimental, and buster.
> thanks
Stopping processing here.

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

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> forcemerge 890257 877257
Bug #890257 [src:ruby-grape] ruby-grape: FTBFS with ruby2.3 and ruby-rack-test 
0.7
Bug #890257 [src:ruby-grape] ruby-grape: FTBFS with ruby2.3 and ruby-rack-test 
0.7
Marked as found in versions ruby-grape/0.19.2-2.
Bug #877257 [src:ruby-grape] ruby-grape: FTBFS  ERROR: Test "ruby2.3" failed.
Marked as found in versions ruby-grape/0.16.2-2.
Merged 877257 890257
> retitle 877257 ruby-grape: FTBFS with ruby2.3 and ruby-rack-test 0.7
Bug #877257 [src:ruby-grape] ruby-grape: FTBFS  ERROR: Test "ruby2.3" failed.
Bug #890257 [src:ruby-grape] ruby-grape: FTBFS with ruby2.3 and ruby-rack-test 
0.7
Changed Bug title to 'ruby-grape: FTBFS with ruby2.3 and ruby-rack-test 0.7' 
from 'ruby-grape: FTBFS  ERROR: Test "ruby2.3" failed.'.
Ignoring request to change the title of bug#890257 to the same title
> thanks
Stopping processing here.

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

Bug#890264: openclonk FTBFS on armel/armhf: error: conflicting declaration 'typedef khronos_ssize_t GLsizeiptr'

[Adrian Bunk]

Control: forwarded -1 http://bugs.openclonk.org/view.php?id=1996

On Mon, Feb 12, 2018 at 08:02:14PM +0100, Philipp Kern wrote:
> On 02/12/2018 06:30 PM, Adrian Bunk wrote:
>...
> > If possible, this should be made working when Qt is using OpenGL ES.
> > 
> > If this is not easily possible,
> > - please lower the severity of this bug, and
> > - submit a bug against ftp.debian.org asking for the
> >   removal of the old armel+armhf binaries from unstable
> 
> I already filed a bug upstream about this: [1]. I know about the option
> space here. I will likely deactivate the editor, assuming that this
> works. Otherwise I'll ask for binary removal.

Thanks.

> I'll note that technically it doesn't need a serious bug because testing
> migration will be blocked anyhow until it either builds or the crufty
> binaries are deleted.

I'll note that the established way to inform the maintainer
(and everyone else who might be interested) that testing migration
is blocked by a problem in the package is by filing an RC bug.

An obvious example is that likely soon someone from Ubuntu
will check why 8.0-1 did FTBFS for them on armhf and arm64.

> Kind regards
> Philipp Kern
>...

cu
Adrian

-- 

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

Bug#889023: marked as done (ruby-gsl: FTBFS with ruby2.5: 'rb_cFixnum' undeclared)

[Debian Bug Tracking System]

Your message dated Mon, 12 Feb 2018 19:20:31 +
with message-id 
and subject line Bug#889023: fixed in ruby-gsl 2.1.0.3+dfsg1-1
has caused the Debian Bug report #889023,
regarding ruby-gsl: FTBFS with ruby2.5: 'rb_cFixnum' undeclared
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.)


-- 
889023: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889023
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-gsl
Severity: serious
Justification: Fails to build from source
User: debian-r...@lists.debian.org
Usertags: ruby2.5

I am filing this at severity serious as I am about to enable building for
ruby2.5 in unstable.


[...]
gcc -I. -I/usr/include/x86_64-linux-gnu/ruby-2.5.0 
-I/usr/include/ruby-2.5.0/ruby/backward -I/usr/include/ruby-2.5.0 -I. 
-DGSL_VERSION=2.4 -DGSL_1_15_LATER -DGSL_1_15_LATER -DGSL_1_16_LATER 
-DGSL_2_0_LATER -DGSL_2_1_LATER -DHAVE_ROUND -DHAVE_GSL_EIGEN_FRANCIS 
-DHAVE_GNU_GRAPH -DHAVE_TAMU_ANOVA_TAMU_ANOVA_H -DHAVE_GSL_SF_MATHIEU_A_E 
-DHAVE_GSL_SF_MATHIEU_B_E -DHAVE_GSL_SF_MATHIEU_CE_E -DHAVE_GSL_SF_MATHIEU_SE_E 
-DHAVE_GSL_SF_MATHIEU_MC_E -DHAVE_GSL_SF_MATHIEU_MS_E 
-I/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.5.0 -Wdate-time 
-D_FORTIFY_SOURCE=2   -fPIC -g -O2 
-fdebug-prefix-map=/build/ruby2.5-ed5dT1/ruby2.5-2.5.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wall -Iinclude 
-I/usr/include  -o error.o -c error.c
In file included from include/rb_gsl_poly.h:17:0,
 from include/rb_gsl.h:18,
 from error.c:11:
include/rb_gsl_complex.h:21:1: note: #pragma message: EXTERN is deprecated, use 
RUBY_EXTERN instead
 EXTERN VALUE cgsl_complex;
 ^~
In file included from include/rb_gsl_array.h:27:0,
 from include/rb_gsl_poly.h:18,
 from include/rb_gsl.h:18,
 from error.c:11:
include/rb_gsl_common.h:29:1: note: #pragma message: EXTERN is deprecated, use 
RUBY_EXTERN instead
 EXTERN ID rb_gsl_id_beg, rb_gsl_id_end, rb_gsl_id_excl, rb_gsl_id_to_a;
 ^~
In file included from include/rb_gsl_array.h:27:0,
 from include/rb_gsl_poly.h:18,
 from include/rb_gsl.h:18,
 from error.c:11:
include/rb_gsl_common.h:352:1: note: #pragma message: EXTERN is deprecated, use 
RUBY_EXTERN instead
 EXTERN VALUE cGSL_Object;
 ^~
In file included from include/rb_gsl_poly.h:18:0,
 from include/rb_gsl.h:18,
 from error.c:11:
include/rb_gsl_array.h:39:1: note: #pragma message: EXTERN is deprecated, use 
RUBY_EXTERN instead
 EXTERN VALUE cgsl_block, cgsl_block_int;
 ^~
include/rb_gsl_array.h:40:1: note: #pragma message: EXTERN is deprecated, use 
RUBY_EXTERN instead
 EXTERN VALUE cgsl_block_uchar;
 ^~
include/rb_gsl_array.h:41:1: note: #pragma message: EXTERN is deprecated, use 
RUBY_EXTERN instead
 EXTERN VALUE cgsl_block_complex;
 ^~
include/rb_gsl_array.h:42:1: note: #pragma message: EXTERN is deprecated, use 
RUBY_EXTERN instead
 EXTERN VALUE cgsl_vector, cgsl_vector_complex;
 ^~
include/rb_gsl_array.h:43:1: note: #pragma message: EXTERN is deprecated, use 
RUBY_EXTERN instead
 EXTERN VALUE cgsl_vector_col;
 ^~
include/rb_gsl_array.h:44:1: note: #pragma message: EXTERN is deprecated, use 
RUBY_EXTERN instead
 EXTERN VALUE cgsl_vector_col_view;
 ^~
include/rb_gsl_array.h:45:1: note: #pragma message: EXTERN is deprecated, use 
RUBY_EXTERN instead
 EXTERN VALUE cgsl_vector_complex_col;
 ^~
include/rb_gsl_array.h:46:1: note: #pragma message: EXTERN is deprecated, use 
RUBY_EXTERN instead
 EXTERN VALUE cgsl_vector_complex_col_view;
 ^~
include/rb_gsl_array.h:47:1: note: #pragma message: EXTERN is deprecated, use 
RUBY_EXTERN instead
 EXTERN VALUE cgsl_vector_view, cgsl_vector_complex_view;
 ^~
include/rb_gsl_array.h:48:1: note: #pragma message: EXTERN is deprecated, use 
RUBY_EXTERN instead
 EXTERN VALUE cgsl_vector_view_ro, cgsl_vector_col_view_ro;
 ^~
include/rb_gsl_array.h:49:1: note: #pragma message: EXTERN is deprecated, use 
RUBY_EXTERN instead
 EXTERN VALUE cgsl_vector_complex_view_ro;
 ^~
include/rb_gsl_array.h:51:1: note: #pragma message: EXTERN is deprecated, use 
RUBY_EXTERN instead
 EXTERN VALUE cgsl_vector_int, cgsl_vector_int_col;
 ^~
include/rb_gsl_array.h:52:1: note: #pragma message: EXTERN is deprecated, use 
RUBY_EXTERN instead
 EXTERN VALUE cgsl_vector_int_view, cgsl_vector_int_col_view;
 ^~
include/rb_gsl_array.h:53:1: note: #pragma message: EXTERN is deprecated, use 
RUBY_EXTERN instead
 EXTERN VALUE 

Processed: Re: Bug#890264: openclonk FTBFS on armel/armhf: error: conflicting declaration 'typedef khronos_ssize_t GLsizeiptr'

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 http://bugs.openclonk.org/view.php?id=1996
Bug #890264 [src:openclonk] openclonk FTBFS on armel/armhf: error: conflicting 
declaration 'typedef khronos_ssize_t GLsizeiptr'
Set Bug forwarded-to-address to 'http://bugs.openclonk.org/view.php?id=1996'.

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

Bug#890264: openclonk FTBFS on armel/armhf: error: conflicting declaration 'typedef khronos_ssize_t GLsizeiptr'

[Philipp Kern]

On 02/12/2018 06:30 PM, Adrian Bunk wrote:
> Source: openclonk
> Version: 8.0-1
> Severity: serious
> 
> https://buildd.debian.org/status/package.php?p=openclonk=sid
> 
> ...
> In file included from 
> /usr/include/arm-linux-gnueabihf/qt5/QtGui/qopengl.h:105:0,
>  from /usr/include/arm-linux-gnueabihf/qt5/QtGui/QtGui:43,
>  from 
> /usr/include/arm-linux-gnueabihf/qt5/QtWidgets/QtWidgetsDepends:4,
>  from 
> /usr/include/arm-linux-gnueabihf/qt5/QtWidgets/QtWidgets:3,
>  from /<>/src/editor/C4ConsoleQt.h:34,
>  from /<>/src/editor/C4ConsoleQtState.h:27,
>  from /<>/src/editor/C4ConsoleQt.cpp:23:
> /usr/include/GLES3/gl31.h: At global scope:
> /usr/include/GLES3/gl31.h:77:25: error: conflicting declaration 'typedef 
> khronos_ssize_t GLsizeiptr'
>  typedef khronos_ssize_t GLsizeiptr;
>  ^~
> In file included from /<>/src/graphics/C4Shader.h:30:0,
>  from /<>/src/lib/StdMeshMaterial.h:20,
>  from /<>/src/graphics/C4Draw.h:22,
>  from /<>/src/landscape/C4Texture.h:26,
>  from /<>/src/editor/C4ConsoleQt.cpp:20:
> /usr/include/GL/glew.h:1680:19: note: previous declaration as 'typedef 
> ptrdiff_t GLsizeiptr'
>  typedef ptrdiff_t GLsizeiptr;
>^~
> 
> 
> If possible, this should be made working when Qt is using OpenGL ES.
> 
> If this is not easily possible,
> - please lower the severity of this bug, and
> - submit a bug against ftp.debian.org asking for the
>   removal of the old armel+armhf binaries from unstable

I already filed a bug upstream about this: [1]. I know about the option
space here. I will likely deactivate the editor, assuming that this
works. Otherwise I'll ask for binary removal.

I'll note that technically it doesn't need a serious bug because testing
migration will be blocked anyhow until it either builds or the crufty
binaries are deleted.

Kind regards
Philipp Kern

[1] http://bugs.openclonk.org/view.php?id=1996



signature.asc
Description: OpenPGP digital signature

Processed: Re: Processed: correcting severity (888549: chrome-gnome-shell: Please don't use /etc/opt, it's not FHS-compliant)

[Debian Bug Tracking System]

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

> affects 888549 - src:debian-edu
Bug #888549 [chrome-gnome-shell] chrome-gnome-shell: Please don't use /etc/opt, 
it's not FHS-compliant
Removed indication that 888549 affects src:debian-edu
> thanks
Stopping processing here.

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

Bug#890067: libgl1-mesa-dri: breaks kde experimental (sddm or sddm-greeter crash, ksplashscreen crash)

[Eric Valette]

On 2/12/18 10:36 AM, Timo Aaltonen wrote:

On 10.02.2018 20:57, Eric Valette wrote:

Package: libgl1-mesa-dri
Version: 18.0.0~rc2-1
Severity: critical
Justification: breaks unrelated software

After sucesfully upgrading this machine with experimental kde; libc6, mesa, I 
went down and upgraded htpc and kids pc that are

AMD A4-5000
AMD E2-1800
AMD E1

respectively and all did break preventing to log in any way in kde session.
Becasue one of the crash in one machine reported once  a bug in r600_dri.so
ksplashqml[1148]: segfault at 7ffcac73c000 ip 7f9bf07d5be5 sp 
7ffcac739bf8 error 6 in r600_dri.so[7f9bf0394000+a86000]


18.0.0-rc4 is now pushed to experimental, please try with it once it's
built but if the driver still crashes, file a bug upstream.
Only tested on one of the failing machines (AMD A4-5000) : works 
correctly this time (no crash in sddm or sddm-gretter or ksplashscreen, 
and I manage to log in and get my session)


Only strange message in dmesg output is: radeon_dp_aux_transfer_native: 
74 callbacks suppressed.


Note sure I will try to break again kids PC after the nightmare week-end 
I got due this bug, even if I know how to fix now :-)


So I hope it means they really fixed it upstream for all amd devices...

-- eric

Bug#890254: marked as done (gf2x: baseline violations on i386/amd64)

[Debian Bug Tracking System]

Your message dated Mon, 12 Feb 2018 17:49:10 +
with message-id 
and subject line Bug#890254: fixed in gf2x 1.2-4
has caused the Debian Bug report #890254,
regarding gf2x: baseline violations on i386/amd64
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.)


-- 
890254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890254
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gf2x
Version: 1.1-2
Severity: serious
Control: affects -1 src:sagemath

A FTBFS in sagemath boiled down to gf2x violating
the amd64 baseline by building with
"-msse2 -msse3 -mssse3 -msse4.1 -mpclmul".

The same problem exists on i386 with
"-msse2 -msse3 -mssse3".

gf2x 1.1-2 has similar problems by building with
"-msse2 -mpclmul" if supported during the build,
and building with "-msse2" on i386.

gf2x must not ever set any of these flags
(-msse2 on amd64 is harmless since it is
 already enabled by default, but therefore
 also pointless).
--- End Message ---
--- Begin Message ---
Source: gf2x
Source-Version: 1.2-4

We believe that the bug you reported is fixed in the latest version of
gf2x, 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.
Ximin Luo  (supplier of updated gf2x 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, 12 Feb 2018 18:26:47 +0100
Source: gf2x
Binary: libgf2x1 libgf2x-dev
Architecture: source
Version: 1.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Ximin Luo 
Description:
 libgf2x-dev - Routines for fast arithmetic in GF(2)[x] (development files)
 libgf2x1   - Routines for fast arithmetic in GF(2)[x]
Closes: 890254
Changes:
 gf2x (1.2-4) unstable; urgency=medium
 .
   * Team upload.
   * Actually disable HW-specific code also on i386. (Closes: #890254)
Checksums-Sha1:
 358990355ddb56845fbd4ac1011ee81f6262eb89 1994 gf2x_1.2-4.dsc
 177b85d451c395d7b6253639e19ae49f628db6b5 2884 gf2x_1.2-4.debian.tar.xz
 5e0c05609608b45e4617878dc5af4400ba1a93a1 5378 gf2x_1.2-4_source.buildinfo
Checksums-Sha256:
 457d365e70bb761d3deaceec080ef0c0c0f3edb2e16ac4e9728c0d0d65c96e0c 1994 
gf2x_1.2-4.dsc
 cfa4e3ef3de47eb59861f88e0d1f266638d508782e973de3ef7efd0daa53180a 2884 
gf2x_1.2-4.debian.tar.xz
 f3faa3f045f0a3334471cb4a3de114cf0e2484761332e16097953cfadbe66bec 5378 
gf2x_1.2-4_source.buildinfo
Files:
 559fdb5f3bf2e26cd4938d8480117247 1994 math optional gf2x_1.2-4.dsc
 153ed98364e0f8d260df27648cf806dd 2884 math optional gf2x_1.2-4.debian.tar.xz
 dc165518a2aef947c03e39d10e65129e 5378 math optional gf2x_1.2-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEENmdIajJtsnZtJVVGhg3vO49lC3kFAlqBzmEVHGluZmluaXR5
MEBkZWJpYW4ub3JnAAoJEIYN7zuPZQt5QO8P/2u+qGiMI7BCnSz67az7K6XtcLeG
HlTMIXJ3s13C/M1Ch9204s791UEPHRVqSiRC46jlDCPTHo6JfJn22sxhlqP3xoUT
mkmXqXYmbrYtiXyJRWPXRkxHpnpXp76zxAhwZ6sjUD0PI1vIhaLKdbMmJL6BmMML
ZXl6BsTkRYdbBl8j5F7Ouh7uKZoOL+oHsbjaJEJNMokWU/hgTYeGSWYdkQMrjc7f
Uj1KU0exjKBUVT/3wPDZoqmkOKbPw0+4azDEDYLZ3xBu3Zn1WVEM5YIGNiTgR+nJ
qO1QcNRuRzuTimaWiZxtGAVIdqdpZqTGfhJUnNMf5Epie0n42CaSsTV8BsjTO8jn
kiqsR7brbsR5j1vtNIheav0IMkdsLnoXIiiVgvl29Y7aeNgrB3b2fLlNtav+aS0+
yRxdMjop/hWAYbfRBowla34Ib6IMXFYplBSlV6ipO0cvFKZZQtLdvSOWaoQttA7b
zk4bDtAn1dKhv+nU0f+xaqbLz//teTaBioyKqsRxdQM+XVuWt5hrOCPsNOPTdk13
p43Nz2LRqdGRKzOF4yOL7oYyTFqxOWDTarEoOKHEpcYOca7mxn+NGLFMhcfE2aIF
BQbO7XIb0CLxc/wceQRxw6MaMMIY3hdbIT7djZRNcn6IdZU1HOMTUsRqkN01gYUO
TwZVQFV7NC8TFQ4p
=HHwL
-END PGP SIGNATURE End Message ---

Processed: Re: ftconfig.h:113:26: warning: "__SIZEOF_LONG__4" is not defined, evaluates to 0 [-Wundef]

[Debian Bug Tracking System]

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

> severity 887087 serious
Bug #887087 [libfreetype6-dev] ftconfig.h:113:26: warning: "__SIZEOF_LONG__4" 
is not defined, evaluates to 0 [-Wundef]
Severity set to 'serious' from 'important'
>
End of message, stopping processing here.

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

Bug#890262: flash-kernel: QNAP TS109, Not enough space for initrd in MTD

[Ben Hutchings]

Control: severity -1 important
Control: tag -1 moreinfo

On Mon, 2018-02-12 at 17:52 +0100, Gunnar Thorburn wrote:
[...]
> I have not tried editing
>   /etc/initramfs-tools/initramfs.conf
> 
> I suppose i could try to change MODULES=most to MODULES=dep.
[...]

This is definitely not a critical bug in flash-kernel.  It even told
you how to fix the problem.  (It is not allowed for a package to
directly modify configuration files belonging to another package.)

Ben.

-- 
Ben Hutchings
If at first you don't succeed, you're doing about average.



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

Processed: Re: Bug#890262: flash-kernel: QNAP TS109, Not enough space for initrd in MTD

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #890262 [flash-kernel] flash-kernel: QNAP TS109, Not enough space for 
initrd in MTD
Severity set to 'important' from 'critical'
> tag -1 moreinfo
Bug #890262 [flash-kernel] flash-kernel: QNAP TS109, Not enough space for 
initrd in MTD
Added tag(s) moreinfo.

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

Processed: [bts-link] source package src:yabar

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:yabar
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #853713 (http://bugs.debian.org/853713)
> # Bug title: yabar: ftbfs with GCC-7
> #  * https://github.com/geommer/yabar/issues/154
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 853713 + fixed-upstream
Bug #853713 [src:yabar] yabar: ftbfs with GCC-7
Added tag(s) fixed-upstream.
> usertags 853713 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 853713 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:pygame

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:pygame
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #861249 (http://bugs.debian.org/861249)
> # Bug title: FTBFS: math_test.Vector2TypeTest.test_cross fails
> #  * https://github.com/pygame/pygame/issues/368
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 861249 + fixed-upstream
Bug #861249 [src:pygame] FTBFS: math_test.Vector2TypeTest.test_cross fails
Added tag(s) fixed-upstream.
> usertags 861249 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 861249 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> # remote status report for #861250 (http://bugs.debian.org/861250)
> # Bug title: pygame: FTBFS (big-endian): test_get_bounding_rect fails
> #  * https://github.com/pygame/pygame/issues/369
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 861250 + fixed-upstream
Bug #861250 [src:pygame] pygame: FTBFS (big-endian): test_get_bounding_rect 
fails
Added tag(s) fixed-upstream.
> usertags 861250 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 861250 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> # remote status report for #861252 (http://bugs.debian.org/861252)
> # Bug title: pygame: FTBFS on ppc64el: some color-handling tests fail
> #  * https://github.com/pygame/pygame/issues/370
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 861252 + fixed-upstream
Bug #861252 [src:pygame] pygame: FTBFS on ppc64el: some color-handling tests 
fail
Added tag(s) fixed-upstream.
> usertags 861252 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 861252 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> # remote status report for #861253 (http://bugs.debian.org/861253)
> # Bug title: pygame: FTBFS (64-bit BE): BufferProxyLegacyTest.test_write fails
> #  * https://github.com/pygame/pygame/issues/371
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 861253 + fixed-upstream
Bug #861253 [src:pygame] pygame: FTBFS (64-bit BE): 
BufferProxyLegacyTest.test_write fails
Added tag(s) fixed-upstream.
> usertags 861253 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 861253 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> # remote status report for #861256 (http://bugs.debian.org/861256)
> # Bug title: pygame: FTBFS on sh4: surface_test.AllTestCases times out
> #  * https://github.com/pygame/pygame/issues/372
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 861256 + fixed-upstream
Bug #861256 [src:pygame] pygame: FTBFS on sh4: surface_test.AllTestCases times 
out
Added tag(s) fixed-upstream.
> usertags 861256 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 861256 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:obs-build

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:obs-build
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #887306 (http://bugs.debian.org/887306)
> # Bug title: obs-build: CVE-2017-14804: Exploit extractbuild to write to 
> files in the host system
> #  * https://bugzilla.novell.com/show_bug.cgi?id=1069904
> #  * remote status changed: (?) -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 887306 + fixed-upstream
Bug #887306 [src:obs-build] obs-build: CVE-2017-14804: Exploit extractbuild to 
write to files in the host system
Added tag(s) fixed-upstream.
> usertags 887306 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: resolution-FIXED status-RESOLVED.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:morse-simulator

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:morse-simulator
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #853557 (http://bugs.debian.org/853557)
> # Bug title: morse-simulator FTBFS: ImportError: No module named 'version'
> #  * https://github.com/morse-simulator/morse/pull/766
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 853557 + fixed-upstream
Bug #853557 [src:morse-simulator] morse-simulator FTBFS: ImportError: No module 
named 'version'
Bug #867496 [src:morse-simulator] morse-simulator FTBFS: ImportError: No module 
named 'version'
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
> usertags 853557 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 853557 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> # remote status report for #867496 (http://bugs.debian.org/867496)
> # Bug title: morse-simulator FTBFS: ImportError: No module named 'version'
> #  * https://github.com/morse-simulator/morse/pull/766
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 867496 + fixed-upstream
Bug #867496 [src:morse-simulator] morse-simulator FTBFS: ImportError: No module 
named 'version'
Bug #853557 [src:morse-simulator] morse-simulator FTBFS: ImportError: No module 
named 'version'
Ignoring request to alter tags of bug #867496 to the same tags previously set
Ignoring request to alter tags of bug #853557 to the same tags previously set
> usertags 867496 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 867496 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package sieve-extension

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package sieve-extension
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #876541 (http://bugs.debian.org/876541)
> # Bug title: "SyntaxError: missing ] after element list" in 
> SieveFilterEditor.js (fixed upstream 0.2.3k)
> #  * https://github.com/thsmi/sieve/issues/67
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 876541 + fixed-upstream
Bug #876541 [xul-ext-sieve] "SyntaxError: missing ] after element list" in 
SieveFilterEditor.js (fixed upstream 0.2.3k)
Added tag(s) fixed-upstream.
> usertags 876541 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:firefox

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:firefox
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #888634 (http://bugs.debian.org/888634)
> # Bug title: firefox: FTBFS on armhf: spurious -mfloat-abi=softfp, no 
> 
> #  * https://bugzilla.mozilla.org/show_bug.cgi?id=1433725
> #  * remote status changed: (?) -> UNCONFIRMED
> usertags 888634 + status-UNCONFIRMED
There were no usertags set.
Usertags are now: status-UNCONFIRMED.
> # remote status report for #888635 (http://bugs.debian.org/888635)
> # Bug title: firefox: FTBFS on ppc64el: jit unexpected alignment requirements
> #  * https://bugzilla.mozilla.org/show_bug.cgi?id=1425413
> #  * remote status changed: (?) -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 888635 + fixed-upstream
Bug #888635 [src:firefox] firefox: FTBFS on ppc64el: jit unexpected alignment 
requirements
Added tag(s) fixed-upstream.
> usertags 888635 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: resolution-FIXED status-RESOLVED.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package icinga-web

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package icinga-web
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #851671 (http://bugs.debian.org/851671)
> # Bug title: icinga-web: Mysql error: Specified key was too long; max key 
> length is 767 bytes
> #  * https://github.com/Icinga/icinga-web/issues/1382
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 851671 + fixed-upstream
Bug #851671 [icinga-web] icinga-web: Mysql error: Specified key was too long; 
max key length is 767 bytes
Added tag(s) fixed-upstream.
> usertags 851671 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 851671 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:cjs

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:cjs
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #879575 (http://bugs.debian.org/879575)
> # Bug title: cjs: Please don't use mozjs24
> #  * https://github.com/linuxmint/cjs/issues/52
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 879575 + fixed-upstream
Bug #879575 [src:cjs] cjs: Please don't use mozjs24
Added tag(s) fixed-upstream.
> usertags 879575 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 879575 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:firefox-esr

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:firefox-esr
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #853402 (http://bugs.debian.org/853402)
> # Bug title: firefox-esr: ftbfs with GCC-7
> #  * https://bugzilla.mozilla.org/show_bug.cgi?id=1320654
> #  * remote status changed: NEW -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 853402 + fixed-upstream
Bug #853402 [src:firefox-esr] firefox-esr: ftbfs with GCC-7
Added tag(s) fixed-upstream.
> usertags 853402 - status-NEW
Usertags were: status-NEW.
Usertags are now: .
> usertags 853402 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: resolution-FIXED status-RESOLVED.
> thanks
Stopping processing here.

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

Bug#890264: openclonk FTBFS on armel/armhf: error: conflicting declaration 'typedef khronos_ssize_t GLsizeiptr'

[Adrian Bunk]

Source: openclonk
Version: 8.0-1
Severity: serious

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

...
In file included from 
/usr/include/arm-linux-gnueabihf/qt5/QtGui/qopengl.h:105:0,
 from /usr/include/arm-linux-gnueabihf/qt5/QtGui/QtGui:43,
 from 
/usr/include/arm-linux-gnueabihf/qt5/QtWidgets/QtWidgetsDepends:4,
 from 
/usr/include/arm-linux-gnueabihf/qt5/QtWidgets/QtWidgets:3,
 from /<>/src/editor/C4ConsoleQt.h:34,
 from /<>/src/editor/C4ConsoleQtState.h:27,
 from /<>/src/editor/C4ConsoleQt.cpp:23:
/usr/include/GLES3/gl31.h: At global scope:
/usr/include/GLES3/gl31.h:77:25: error: conflicting declaration 'typedef 
khronos_ssize_t GLsizeiptr'
 typedef khronos_ssize_t GLsizeiptr;
 ^~
In file included from /<>/src/graphics/C4Shader.h:30:0,
 from /<>/src/lib/StdMeshMaterial.h:20,
 from /<>/src/graphics/C4Draw.h:22,
 from /<>/src/landscape/C4Texture.h:26,
 from /<>/src/editor/C4ConsoleQt.cpp:20:
/usr/include/GL/glew.h:1680:19: note: previous declaration as 'typedef 
ptrdiff_t GLsizeiptr'
 typedef ptrdiff_t GLsizeiptr;
   ^~


If possible, this should be made working when Qt is using OpenGL ES.

If this is not easily possible,
- please lower the severity of this bug, and
- submit a bug against ftp.debian.org asking for the
  removal of the old armel+armhf binaries from unstable

Bug#887531: marked as done (python-asdf FTBFS: test failures)

[Debian Bug Tracking System]

Your message dated Mon, 12 Feb 2018 17:07:19 +
with message-id 
and subject line Bug#887531: fixed in python-asdf 1.3.1-2
has caused the Debian Bug report #887531,
regarding python-asdf FTBFS: test failures
to be marked as done.

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

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


-- 
887531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887531
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-asdf
Version: 1.3.1-1
Severity: serious

Some recent change in unstable makes python-asdf FTBFS:

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

...
=== FAILURES ===
_ test_urlopen[tree0] __

tree = {'not_shared': array([10,  9,  8,  7,  6,  5,  4,  3,  2,  1], 
dtype=uint8), 'science_data': array([ 0.,  1.,  2.,  3.,  4.,  5.,  6.,  7.,  
8.,  9.]), 'skipping': array([ 0.,  2.,  4.,  6.,  8.]), 'subset': array([ 3.,  
4.,  5.,  6.])}
httpserver = 

@pytest.mark.skipif(INTERNET_OFF, reason="Astropy has disabled internet 
access")
@pytest.mark.skipif(sys.platform.startswith('win'),
reason="Windows firewall prevents test")
def test_urlopen(tree, httpserver):
path = os.path.join(httpserver.tmpdir, 'test.asdf')

def get_write_fd():
return generic_io.get_file(open(path, 'wb'), mode='w')

def get_read_fd():
return generic_io.get_file(
urllib_request.urlopen(
httpserver.url + "test.asdf"))

>   with _roundtrip(tree, get_write_fd, get_read_fd) as ff:

asdf/tests/test_generic_io.py:270: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
asdf/tests/test_generic_io.py:72: in _roundtrip
with get_read_fd() as fd:
asdf/tests/test_generic_io.py:268: in get_read_fd
httpserver.url + "test.asdf"))
/usr/lib/python2.7/urllib2.py:154: in urlopen
return opener.open(url, data, timeout)
/usr/lib/python2.7/urllib2.py:429: in open
response = self._open(req, data)
/usr/lib/python2.7/urllib2.py:447: in _open
'_open', req)
/usr/lib/python2.7/urllib2.py:407: in _call_chain
result = func(*args)
/usr/lib/python2.7/urllib2.py:1228: in http_open
return self.do_open(httplib.HTTPConnection, req)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = 
http_class = 
req = , http_conn_args = {}
host = '127.0.0.1:9', h = 
err = error(111, 'Connection refused')

def do_open(self, http_class, req, **http_conn_args):
"""Return an addinfourl object for the request, using http_class.

http_class must implement the HTTPConnection API from httplib.
The addinfourl return value is a file-like object.  It also
has methods and attributes including:
- info(): return a mimetools.Message object for the headers
- geturl(): return the original request URL
- code: HTTP status code
"""
host = req.get_host()
if not host:
raise URLError('no host given')

# will parse host:port
h = http_class(host, timeout=req.timeout, **http_conn_args)
h.set_debuglevel(self._debuglevel)

headers = dict(req.unredirected_hdrs)
headers.update(dict((k, v) for k, v in req.headers.items()
if k not in headers))

# We want to make an HTTP/1.1 request, but the addinfourl
# class isn't prepared to deal with a persistent connection.
# It will try to read all remaining data from the socket,
# which will block while the server waits for the next request.
# So make sure the connection gets closed after the (only)
# request.
headers["Connection"] = "close"
headers = dict(
(name.title(), val) for name, val in headers.items())

if req._tunnel_host:
tunnel_headers = {}
proxy_auth_hdr = "Proxy-Authorization"
if proxy_auth_hdr in headers:
tunnel_headers[proxy_auth_hdr] = headers[proxy_auth_hdr]
# Proxy-Authorization should not be sent to origin
# server.
del headers[proxy_auth_hdr]
h.set_tunnel(req._tunnel_host, headers=tunnel_headers)

try:
h.request(req.get_method(), 

Processed: [bts-link] source package src:exiv2

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:exiv2
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #886962 (http://bugs.debian.org/886962)
> # Bug title: exiv2: CVE-2018-4868
> #  * https://github.com/Exiv2/exiv2/issues/202
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 886962 + fixed-upstream
Bug #886962 [src:exiv2] exiv2: CVE-2018-4868
Added tag(s) fixed-upstream.
> usertags 886962 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> # remote status report for #63 (http://bugs.debian.org/63)
> # Bug title: exiv2: CVE-2017-1000127
> #  * https://github.com/Exiv2/exiv2/issues/176
> #  * remote status changed: (?) -> open
> usertags 63 + status-open
There were no usertags set.
Usertags are now: status-open.
> # remote status report for #64 (http://bugs.debian.org/64)
> # Bug title: exiv2: CVE-2017-1000126
> #  * https://github.com/Exiv2/exiv2/issues/175
> #  * remote status changed: (?) -> open
> usertags 64 + status-open
There were no usertags set.
Usertags are now: status-open.
> # remote status report for #65 (http://bugs.debian.org/65)
> # Bug title: exiv2: CVE-2017-14865
> #  * https://github.com/Exiv2/exiv2/issues/134
> #  * remote status changed: (?) -> open
> usertags 65 + status-open
There were no usertags set.
Usertags are now: status-open.
> # remote status report for #66 (http://bugs.debian.org/66)
> # Bug title: exiv2: CVE-2017-14863
> #  * https://github.com/Exiv2/exiv2/issues/132
> #  * remote status changed: (?) -> open
> usertags 66 + status-open
There were no usertags set.
Usertags are now: status-open.
> # remote status report for #67 (http://bugs.debian.org/67)
> # Bug title: exiv2: CVE-2017-14860
> #  * https://github.com/Exiv2/exiv2/issues/71
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 67 + fixed-upstream
Bug #67 [src:exiv2] exiv2: CVE-2017-14860
Added tag(s) fixed-upstream.
> usertags 67 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> # remote status report for #69 (http://bugs.debian.org/69)
> # Bug title: exiv2: CVE-2017-14857
> #  * https://github.com/Exiv2/exiv2/issues/76
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 69 + fixed-upstream
Bug #69 [src:exiv2] exiv2: CVE-2017-14857
Added tag(s) fixed-upstream.
> usertags 69 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> # remote status report for #72 (http://bugs.debian.org/72)
> # Bug title: exiv2: CVE-2017-12956
> #  * https://github.com/Exiv2/exiv2/issues/59
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 72 + fixed-upstream
Bug #72 [src:exiv2] exiv2: CVE-2017-12956
Added tag(s) fixed-upstream.
> usertags 72 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> # remote status report for #73 (http://bugs.debian.org/73)
> # Bug title: exiv2: CVE-2017-12955
> #  * https://github.com/Exiv2/exiv2/issues/58
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 73 + fixed-upstream
Bug #73 [src:exiv2] exiv2: CVE-2017-12955
Added tag(s) fixed-upstream.
> usertags 73 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> # remote status report for #74 (http://bugs.debian.org/74)
> # Bug title: exiv2: CVE-2017-11553
> #  * https://github.com/Exiv2/exiv2/issues/54
> #  * remote status changed: (?) -> open
> usertags 74 + status-open
There were no usertags set.
Usertags are now: status-open.
> thanks
Stopping processing here.

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

Bug#890262: flash-kernel: QNAP TS109, Not enough space for initrd in MTD

[Gunnar Thorburn]

Package: flash-kernel
Version: 3.79
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

I have been running Debian on a QNAP TS109 for many years.
I successfully upgraded from Squeeze to Wheezy in 2013 and to Jessie in 2015.

As I now upgrade to Stretch (basically following Debian Upgrade Guide, it
is a very simple system) I now get:

== from apt-get dist-upgrade ==
update-initramfs: Generating /boot/initrd.img-4.9.0-5-marvell
flash-kernel: installing version 4.9.0-5-marvell

The initial ramdisk is too large. This is often due to the unnecessary inclusion
of all kernel modules in the image. To fix this set MODULES=dep in one or both
/etc/initramfs-tools/conf.d/driver-policy (if it exists) and
/etc/initramfs-tools/initramfs.conf and then run 'update-initramfs -u
-k 4.9.0-5-marvell'

Not enough space for initrd in MTD 'RootFS1' (need 4210887 but is
actually 4194304).
run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 1
dpkg: error processing package initramfs-tools (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)
== end of output

That was (obviously) after
 - editing /etc/apt/sources.list (changing jessie to stretch)
 - apt-get update
 - apt-get upgrade

I am completely aware how old and obsolete this QNAP TS109 is.
It would make complete sense to me if it was not supported anymore.
And I would completely understand if you dont want to fix this problem.

But given that TS-109 appears supported
  http://www.cyrius.com/debian/orion/qnap/ts-109/install/
and with no major issues
  http://www.cyrius.com/debian/orion/qnap/ts-109/known-issues/
I would not expect this problem well into the upgrade.

To other users, it would be helpful to advice them not to upgrade to Stretch.

I guess my system would reboot if I try (but I have not tried)
I guess Debain 9.3 can run with Linux 3.16.0-5-orion5x from Debian 8, but
to me (I have used Debian for 20 years) the system seems to be in a rather
bad state. (if it fails to boot a serial cable for direct UBOOT is necessary)

I have not tried editing
  /etc/initramfs-tools/initramfs.conf

I suppose i could try to change MODULES=most to MODULES=dep.

However, if I break the system completely it will be much harder for me
to give you any more useful information.


  Best Regards
  Gunnar Thorburn


-- System Information:
Debian Release: 9.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: armel (armv5tel)

Kernel: Linux 3.16.0-5-orion5x
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages flash-kernel depends on:
ii  debconf [debconf-2.0]  1.5.61
ii  devio  1.2-1.2+b1
ih  initramfs-tools0.130
ii  linux-base 4.5
ii  mtd-utils  1:2.0.0-1
ii  ucf3.0036

Versions of packages flash-kernel recommends:
ii  u-boot-tools  2016.11+dfsg1-4

flash-kernel suggests no packages.

-- debconf information:
  flash-kernel/linux_cmdline: quiet

Processed: notfixed 890254 in 1.2-3

[Debian Bug Tracking System]

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

> notfixed 890254 1.2-3
Bug #890254 [src:gf2x] gf2x: baseline violations on i386/amd64
No longer marked as fixed in versions gf2x/1.2-3.
> thanks
Stopping processing here.

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

Bug#890254: control

[Adrian Bunk]

Control: not fixed -1 1.2-3

On Mon, Feb 12, 2018 at 02:14:00PM +, Ximin Luo wrote:
> Control: fixed -1 1.2-3
> 
> Already fixed there, version in stretch still affected.

That only fixed it for amd64, i386 still builds with -msse2:
https://buildd.debian.org/status/fetch.php?pkg=gf2x=i386=1.2-3=1518451597=0

> X

cu
Adrian

-- 

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

Bug#889829: ghc: error while loading shared libraries: libHShaskeline-0.7.3.0-ghc8.0.2.so

[Holger Levsen]

control: severity -1 normal
thanks

Hi Adrian,

On Mon, Feb 12, 2018 at 03:50:37PM +0100, John Paul Adrian Glaubitz wrote:
> Has the chroot in which you are trying to install /proc mounted?
> 
> Without /proc mounted, GHC is unable to find it's shared libraries
> and this particular issue shows up.

good catch, that was indeed the case and fixed the issue. Thanks!

Downgrading the bug to normal, though I guess you can also close it. The
openjdk packages have the same issue. (But maybe you want to keep it
open to implement a message to the user saying "arg, /proc not mounted,
but we need it, aborting" or some such.)


-- 
cheers,
Holger


signature.asc
Description: PGP signature

Bug#890096: marked as done (bio-tradis uninstallable: r-bioc-edger removed from unstable)

[Debian Bug Tracking System]

Your message dated Mon, 12 Feb 2018 15:19:27 +
with message-id 
and subject line Bug#890096: fixed in bio-tradis 1.3.3+dfsg-3
has caused the Debian Bug report #890096,
regarding bio-tradis uninstallable: r-bioc-edger removed from unstable
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.)


-- 
890096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890096
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bio-tradis
Version: 1.3.3+dfsg-2
Severity: serious
Tags: sid
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic

Dear maintainer,

Per bug #881317, r-bioc-edger has been removed from unstable.  This means
that bio-tradis is now uninstallable in sid.

As you appear to have been the maintainer of both packages, you are perhaps
already aware of this, but filing it in the BTS for the record.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: bio-tradis
Source-Version: 1.3.3+dfsg-3

We believe that the bug you reported is fixed in the latest version of
bio-tradis, 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 bio-tradis package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 12 Feb 2018 15:13:51 +0100
Source: bio-tradis
Binary: bio-tradis
Architecture: source
Version: 1.3.3+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 bio-tradis - analyse the output from TraDIS analyses of genomic sequences
Closes: 890096
Changes:
 bio-tradis (1.3.3+dfsg-3) unstable; urgency=medium
 .
   * Standards-Version: 4.1.3
   * Downgrade r-bioc-edger from Depends to Suggests since the package
 was removed from Debian but people might consider local installations
 Closes: #890096
   * debhelper 11
Checksums-Sha1:
 bd838017bf660b6dd4ba3e5b525867f942296ceb 2121 bio-tradis_1.3.3+dfsg-3.dsc
 4192bd55dd6523e3fa1c6a5b1440bc897320df11 6312 
bio-tradis_1.3.3+dfsg-3.debian.tar.xz
 d356d5bf08dfdc231dfde5673717bf2acb9c406c 15664 
bio-tradis_1.3.3+dfsg-3_source.buildinfo
Checksums-Sha256:
 3077f389c3aa837ba1de6fb077d7866128dca16f16ab3b8adac876bc6c3d98d0 2121 
bio-tradis_1.3.3+dfsg-3.dsc
 827d2ac79ee42b841efef04dd0e52e2207b9245981d7e72b7683975d6bef0249 6312 
bio-tradis_1.3.3+dfsg-3.debian.tar.xz
 f645d62120bfbb9f01c6cfa4c6173ce07467d84a576a0d51d3f0c91989deaa1a 15664 
bio-tradis_1.3.3+dfsg-3_source.buildinfo
Files:
 97a60b674bb2ae94fd83a5b86f4fb311 2121 perl optional bio-tradis_1.3.3+dfsg-3.dsc
 bb796f750b4e66dfb0f58b959bbb7f81 6312 perl optional 
bio-tradis_1.3.3+dfsg-3.debian.tar.xz
 4c416ce04bf4458bedb23f0a4be2b520 15664 perl optional 
bio-tradis_1.3.3+dfsg-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJCBAEBCAAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlqBoY0OHHRpbGxlYUBy
a2kuZGUACgkQV4oElNHGRtGdJQ/+KtmjF11SHnF3zxjLUEi9DMxIFSng6y743Vas
z8V602W6VDRcQfaNoxArLU8LRumn5gvT97VxCGb0wjw33C7q2bNt+LvTaKFIyzCS
+L4HXy63Kt2ZiLvPiUIxgFY5E7/7OFMhFv7+IR/ld4DGyKwfkbMMOXJD/zQGfDNY
TyzE+IVcYDPLZnfn3Al3bmr1N6G3eVZ0MDJpwD1uqtfOGxhSngkyLqe3EnIFncGr
0l6r8OwW6DxBWBj+2gj/QAh/5OiXTL0m5Z0de2zs/SpwgZH64B1FtIznwfPLWKnb
byKu9/DZbGpR3wE6YrRR9kC3u1mnYknXykDnNRds6Z3c3yuiI/ectxQ0cOx5kWRN
R9hzi3Pl5oW1p9V+pS4Xm13hAkCJGp3BA68X3jC4/8VdOcNPRtOpLpYOEILCMiml
2JnWvOykA8Z+rjJFwL5VMP29+kZzB8PZ/PAMct4fCGQ/aAQx5HJQd8OJH1+Z6WyW
bRXOW0nABi0aeJZBWV8lLLKlBVnchC0uMu07+opo54hfk6KMUna7kqxzbGpNUVKd
FR6YpMGMBr9IJZzScFaDIZX7KjMy+0iIrPC24JXXRYc8Oo3K+GoXil/lm19/f3nm
Zq6CJjgWLC3R8do+2oUnPiqEt4o5uZ3FSCVXv9JxMp/bvvumX8btDZ63ki6AmFHi
5+fkFps=
=q2yN
-END PGP SIGNATURE End Message ---

Processed: Re: ghc: error while loading shared libraries: libHShaskeline-0.7.3.0-ghc8.0.2.so

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #889829 [ghc] ghc: error while loading shared libraries: 
libHShaskeline-0.7.3.0-ghc8.0.2.so
Severity set to 'normal' from 'serious'

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

Bug#890257: ruby-grape: FTBFS with ruby2.3 and ruby-rack-test 0.7

[Cédric Boutillier]

Source: ruby-grape
Version: 0.16.2-2
Severity: serious
Justification: fails to build from source

Dear Maintainer,

The version 0.16.2-2 fails to build with ruby2.3. According to
ci.debian.net, this has been happening since Sept, 7 2018
https://ci.debian.net/data/autopkgtest/unstable/amd64/r/ruby-grape/20170907_031907/log.gz
This coincides with the transition to ruby-activesupport 2:4.2.9-3
which itself induced the transition from ruby-rack-test 0.6.3 to 0.7.

Using ruby-rack-test 0.6.3 from stretch makes the tests pass with
ruby2.3 (they fail with ruby2.5, but it is another problem).

Cheers,

Cédric

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

Kernel: Linux 4.14.0-3-amd64 (SMP w/4 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)
LSM: AppArmor: enabled

-- no debconf information

Bug#889829: ghc: error while loading shared libraries: libHShaskeline-0.7.3.0-ghc8.0.2.so

[John Paul Adrian Glaubitz]

Hi Holger!

Has the chroot in which you are trying to install /proc mounted?

Without /proc mounted, GHC is unable to find it's shared libraries
and this particular issue shows up.

Adrian

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#890254: control

[Ximin Luo]

Control: fixed -1 1.2-3

Already fixed there, version in stretch still affected.

X

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

Processed: control

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 1.2-3
Bug #890254 [src:gf2x] gf2x: baseline violations on i386/amd64
The source 'gf2x' and version '1.2-3' do not appear to match any binary packages
Marked as fixed in versions gf2x/1.2-3.

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

Bug#890136: libbpp-phyl: FTBFS on mipsel: Test took too much time

[Andreas Tille]

Control: severity -1 wishlist

Hi,

I'm sorry but I do not consider the fact that mips is to slow to run a
long lasting test a release blocker.  Either mips can cope up or I'll
exclude it from the list or architectures.  Please note that this program
will most probably not be used on mips and I do not intend to spent time
on this issue.

Kind regards

   Andreas.

On Sun, Feb 11, 2018 at 09:40:01PM +0800, Boyuan Yang wrote:
> Source: libbpp-phyl
> Version: 2.3.2-2
> Severity: serious
> 
> https://buildd.debian.org/status/fetch.php?pkg=libbpp-phyl=mipsel=2.3.2-2=1518221367=0
> 
> [...]
> 
> 10/14 Test #13: test_tree_getpath    Passed0.42 sec
>   Start 14: test_tree_rootat
> 11/14 Test #14: test_tree_rootat .   Passed3.21 sec
> 12/14 Test #11: test_simulations .   Passed  1052.22 sec
> 13/14 Test #12: test_tree    Passed  197.04 sec
> E: Build killed with signal TERM after 150 minutes of inactivity
> 
> Build finished at 2018-02-10T00:09:20Z
> 
> Please investigate into it.
> 
> --
> Thanks,
> Boyuan Yang
> 
> ___
> 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

Processed: gf2x: baseline violations on i386/amd64

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:sagemath
Bug #890254 [src:gf2x] gf2x: baseline violations on i386/amd64
Added indication that 890254 affects src:sagemath

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

Processed: Re: Bug#890136: libbpp-phyl: FTBFS on mipsel: Test took too much time

[Debian Bug Tracking System]

Processing control commands:

> severity -1 wishlist
Bug #890136 [src:libbpp-phyl] libbpp-phyl: FTBFS on mipsel: Test took too much 
time
Severity set to 'wishlist' from 'serious'

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

Bug#890254: gf2x: baseline violations on i386/amd64

[Adrian Bunk]

Source: gf2x
Version: 1.1-2
Severity: serious
Control: affects -1 src:sagemath

A FTBFS in sagemath boiled down to gf2x violating
the amd64 baseline by building with
"-msse2 -msse3 -mssse3 -msse4.1 -mpclmul".

The same problem exists on i386 with
"-msse2 -msse3 -mssse3".

gf2x 1.1-2 has similar problems by building with
"-msse2 -mpclmul" if supported during the build,
and building with "-msse2" on i386.

gf2x must not ever set any of these flags
(-msse2 on amd64 is harmless since it is
 already enabled by default, but therefore
 also pointless).

Bug#889808: marked as done (plasma-discover: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Mon, 12 Feb 2018 13:35:17 +
with message-id 
and subject line Bug#889808: fixed in plasma-discover 5.12.0-4
has caused the Debian Bug report #889808,
regarding plasma-discover: Incomplete debian/copyright?
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.)


-- 
889808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889808
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: plasma-discover
Version: 5.12.0-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Matthias Klumpp 

Hi,

I just ACCEPTed plasma-discover from NEW but noticed it was missing 
attribution in debian/copyright for at least Jan Grulich, Kai Uwe
Broulik, etc

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


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: plasma-discover
Source-Version: 5.12.0-4

We believe that the bug you reported is fixed in the latest version of
plasma-discover, 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 report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klumpp  (supplier of updated plasma-discover 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, 12 Feb 2018 14:45:24 +0100
Source: plasma-discover
Binary: plasma-discover plasma-discover-common plasma-discover-backend-flatpak 
plasma-discover-backend-snap
Architecture: source amd64 all
Version: 5.12.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Matthias Klumpp 
Description:
 plasma-discover - Discover software management suite
 plasma-discover-backend-flatpak - Discover software management suite - Flatpak 
backend
 plasma-discover-backend-snap - Discover software management suite - Snap 
backend
 plasma-discover-common - Discover software manager suite (common data files)
Closes: 889808
Changes:
 plasma-discover (5.12.0-4) unstable; urgency=medium
 .
   * Update d/copyright (Closes: #889808)
Checksums-Sha1:
 60279eabef9666a9597385a1ebef3894092abdcd 3425 plasma-discover_5.12.0-4.dsc
 ab8dd435a5c88b3d6e7649ceb872d3884a85 11140 
plasma-discover_5.12.0-4.debian.tar.xz
 535de01c90ea9dc1bc7465d95d9d7ae4e6dad60c 1431780 
plasma-discover-backend-flatpak-dbgsym_5.12.0-4_amd64.deb
 577367d3ed531efde43a2016a65fc7f7e100c40f 69940 
plasma-discover-backend-flatpak_5.12.0-4_amd64.deb
 c0611cb16c05eb215c4b16fb69199a8815c8da49 1042948 
plasma-discover-backend-snap-dbgsym_5.12.0-4_amd64.deb
 ff0f91d0a3502b837b50d1a61f8ab860a5e51a19 35800 
plasma-discover-backend-snap_5.12.0-4_amd64.deb
 8708e02d2f2b64488d56b81f0fa0067a0facb29a 7621980 
plasma-discover-common_5.12.0-4_all.deb
 7e477a871ab60b5313a704fb618351344688cdf8 840 
plasma-discover-dbgsym_5.12.0-4_amd64.deb
 9e810524d48ba5b4821442254e3cab8a3f667bc1 27110 
plasma-discover_5.12.0-4_amd64.buildinfo
 ad49aff2cb20620ed86bc55a6fa529e2257c7cad 1039944 
plasma-discover_5.12.0-4_amd64.deb
Checksums-Sha256:
 a4cdeed9c49ca1b09bf4aff0a31151a5f76f4c115343c12f46dfb54c8f6d7a91 3425 
plasma-discover_5.12.0-4.dsc
 7e59265318c43f7fcea5419514a42655314de62c37e457b06e9b93e3a3d27e9c 11140 
plasma-discover_5.12.0-4.debian.tar.xz
 74236b8d28a24ece632b527f7978f2194246658fd0320119a8febe3f1d5e0b77 1431780 
plasma-discover-backend-flatpak-dbgsym_5.12.0-4_amd64.deb
 f47137e95be853dd6a78543e9d360cc93371a073993026176a6465aad3ceabf6 69940 
plasma-discover-backend-flatpak_5.12.0-4_amd64.deb
 751e7ced220233b6dbb4f63e6ff9379dbb6b3ddc6bdea5fea3ddeb92c6e1fbc3 1042948 
plasma-discover-backend-snap-dbgsym_5.12.0-4_amd64.deb
 3d5dce6864eb89f95e580752b7e71bd7f659f387d809a0c4fb4bb54a1576157a 35800 
plasma-discover-backend-snap_5.12.0-4_amd64.deb
 9ac7bd0c8c3c13ad09b3b9316741b532c87ffa934165c1964ca3dff81c1851a0 7621980 
plasma-discover-common_5.12.0-4_all.deb
 81e98519130882d2368c02a7eab39abd63337ddcd2f7035e4bb2c7c587d13182 840 

Bug#890023: abcmidi fails autopkg tests on 32bit architectures

[James Cowgill]

Control: tags -1 patch

Hi,

On 10/02/18 08:52, Matthias Klose wrote:
> Package: src:abcmidi
> Version: 20180125-1
> Severity: serious
> Tags: sid buster
> 
> abcmidi fails autopkg tests on 32bit architectures, midi2abc crashing.  Is 
> there
> a reason why the tests are not run at build time?
> 
> 
> MIDI to ABC conversion test
> 
> Convert the araber47.mid file back to abc
> Aborted (core dumped)
> autopkgtest [14:08:29]: test conversions: ---]
> autopkgtest [14:08:33]: test conversions:  - - - - - - - - - - results - - - 
> - -
> - - - - -
> conversions  FAIL non-zero exit status 134
> autopkgtest [14:08:33]: test conversions:  - - - - - - - - - - stderr - - - - 
> -
> - - - - -
> *** Error in `midi2abc': free(): invalid pointer: 0x00c43f28 ***
> Aborted (core dumped)

Caused by a buffer overflow in midi2abc.c:329
> char* addstring(s)
> /* create space for string and store it in memory */
> char* s;
> {
>   char* p;
> 
>   p = (char*) checkmalloc(strlen(s)+1);
>   strncpy(p, s,strlen(s)+2); /* [SS] 2017-08-30 */
>   return(p);
> }

strncpy writes to exactly n bytes to the output buffer, so the call will
always overflow the buffer allocated one line above by 1 byte.

Attached patch fixes this. I think using strcpy is safe here because the
size of the buffer allocated is always greater than the string length.

I think the comment on that line refers to this (from doc/CHANGES):
> August 30 2017
> 
> Midi2abc - The metatext string is not terminated with a 0 and
> as a result can contain random junk, in particular on the Windows
> operating system. Fix in midifile.c, the Msgbuff is initialized to
> 0 when it is allocated.

Some old code I found shows the code originally used strcpy. I'm not I
understand how using strncpy was supposed to fix this. I've copied
upstream who might be able to shed some light on this.

Thanks,
James
--- a/midi2abc.c
+++ b/midi2abc.c
@@ -333,7 +333,7 @@ char* s;
   char* p;
 
   p = (char*) checkmalloc(strlen(s)+1);
-  strncpy(p, s,strlen(s)+2); /* [SS] 2017-08-30 */
+  strcpy(p, s);
   return(p);
 }
 


signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#890023: abcmidi fails autopkg tests on 32bit architectures

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #890023 [src:abcmidi] abcmidi fails autopkg tests on 32bit architectures
Added tag(s) patch.

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

Bug#887690: marked as done (unattended-upgrades: FTBFS and Debci failure after testpackage was removed from Ubuntu server)

[Debian Bug Tracking System]

Your message dated Mon, 12 Feb 2018 12:06:10 +
with message-id <20180212120610.ga16...@archetype.pseudorandom.co.uk>
and subject line Re: Bug#887690: unattended-upgrades: FTBFS and Debci failure 
after testpackage was removed from Ubuntu server
has caused the Debian Bug report #887690,
regarding unattended-upgrades: FTBFS and Debci failure after testpackage was 
removed from Ubuntu server
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.)


-- 
887690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887690
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: unattended-upgrades
Version: 0.98
Severity: serious

https://ci.debian.net/packages/u/unattended-upgrades/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/unattended-upgrades.html

...
==
ERROR: test_remove_unused_dependencies (__main__.TestRemoveUnused)
--
Traceback (most recent call last):
  File "./test_remove_unused.py", line 100, in test_remove_unused_dependencies
options, rootdir="./root.unused-deps")
  File "/build/1st/unattended-upgrades-0.98/test/unattended_upgrade.py", line 
1462, in main
sys.exit(1)
SystemExit: 1

==
ERROR: test_remove_unused_dependencies_new_unused_only 
(__main__.TestRemoveUnused)
--
Traceback (most recent call last):
  File "./test_remove_unused.py", line 122, in 
test_remove_unused_dependencies_new_unused_only
options, rootdir="./root.unused-deps")
  File "/build/1st/unattended-upgrades-0.98/test/unattended_upgrade.py", line 
1462, in main
sys.exit(1)
SystemExit: 1

--
Ran 2 tests in 0.486s

FAILED (errors=2)
The URI 'http://archive.ubuntu.com/ubuntu/test-package_2.0_all.deb' failed to 
download, aborting
The URI 'http://archive.ubuntu.com/ubuntu/test-package_2.0_all.deb' failed to 
download, aborting
Makefile:6: recipe for target 'check' failed
make[2]: *** [check] Error 1
--- End Message ---
--- Begin Message ---
Version: 0.99

On Thu, 08 Feb 2018 at 03:34:02 +0700, Bálint Réczey wrote:
> 2018-02-07 23:25 GMT+07:00 Simon McVittie :
> > On Fri, 19 Jan 2018 at 06:36:43 +0200, Adrian Bunk wrote:
> >> The URI 'http://archive.ubuntu.com/ubuntu/test-package_2.0_all.deb' failed 
> >> to download, aborting
> >> The URI 'http://archive.ubuntu.com/ubuntu/test-package_2.0_all.deb' failed 
> >> to download, aborting
> >
> > I think this is caused by a behaviour change in apt (see #886803).
...
> > The attached patch (from the unattended-upgrades git repository) seems
> > to resolve this for me. It just makes the Filename and the Version
> > consistent with each other so that the problem situation doesn't arise.
>
> I'm trying [to] fix #875383 and release all the queued fixes this week.

Thanks for getting this release out - lots of good fixes there. The patch
I referred to seems to have resolved this, with 0.98 consistently failing
with newer apt, but 0.99 consistently passing:

https://ci.debian.net/packages/u/unattended-upgrades/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/unattended-upgrades.html

So I think the RC bug #887690 has the same root cause as #886803, and is
now resolved.

Regards,
smcv--- End Message ---

Processed: limit source to textedit.app, tagging 890070

[Debian Bug Tracking System]

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

> limit source textedit.app
Limiting to bugs with field 'source' containing at least one of 'textedit.app'
Limit currently set to 'source':'textedit.app'

> tags 890070 + pending
Bug #890070 [textedit.app] textedit.app: Does not start after upgrade; missing 
resources
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#889269: marked as done (liblld-4.0-dbg is empty)

[Debian Bug Tracking System]

Your message dated Mon, 12 Feb 2018 11:00:19 +
with message-id 
and subject line Bug#889269: fixed in llvm-toolchain-4.0 1:4.0.1-9
has caused the Debian Bug report #889269,
regarding liblld-4.0-dbg is empty
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.)


-- 
889269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889269
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: liblld-4.0-dbg
Version: 1:4.0.1-8
Severity: grave

$ dpkg -L liblld-4.0-dbg
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/liblld-4.0-dbg
/usr/share/doc/liblld-4.0-dbg/NEWS.Debian.gz
/usr/share/doc/liblld-4.0-dbg/changelog.Debian.gz
/usr/share/doc/liblld-4.0-dbg/copyright
$
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-4.0
Source-Version: 1:4.0.1-9

We believe that the bug you reported is fixed in the latest version of
llvm-toolchain-4.0, 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 report if appropriate.

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated llvm-toolchain-4.0 
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, 11 Feb 2018 00:01:50 +0100
Source: llvm-toolchain-4.0
Binary: clang-4.0 clang-tools-4.0 clang-format-4.0 clang-tidy-4.0 clang-4.0-doc 
libclang1-4.0 libclang1-4.0-dbg libclang-4.0-dev libclang-common-4.0-dev 
libfuzzer-4.0-dev python-clang-4.0 clang-4.0-examples libllvm4.0 libllvm4.0-dbg 
llvm-4.0 llvm-4.0-runtime llvm-4.0-dev llvm-4.0-tools llvm-4.0-doc 
llvm-4.0-examples lld-4.0 liblld-4.0 liblld-4.0-dev lldb-4.0 liblldb-4.0 
liblldb-4.0-dbg python-lldb-4.0 liblldb-4.0-dev
Architecture: source amd64 all
Version: 1:4.0.1-9
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Description:
 clang-4.0  - C, C++ and Objective-C compiler
 clang-4.0-doc - C, C++ and Objective-C compiler - Documentation
 clang-4.0-examples - Clang examples
 clang-format-4.0 - Tool to format C/C++/Obj-C code
 clang-tidy-4.0 - clang-based C++ linter tool
 clang-tools-4.0 - clang-based tools for C/C++ developments
 libclang-4.0-dev - clang library - Development package
 libclang-common-4.0-dev - clang library - Common development package
 libclang1-4.0 - C interface to the clang library
 libclang1-4.0-dbg - clang library (debug)
 libfuzzer-4.0-dev - Library for coverage-guided fuzz testing
 liblld-4.0 - LLVM-based linker, library
 liblld-4.0-dev - LLVM-based linker, header files
 liblldb-4.0 - Next generation, high-performance debugger, library
 liblldb-4.0-dbg - Next generation, high-performance debugger, debugging 
libraries
 liblldb-4.0-dev - Next generation, high-performance debugger, header files
 libllvm4.0 - Modular compiler and toolchain technologies, runtime library
 libllvm4.0-dbg - Modular compiler and toolchain technologies, debugging 
libraries
 lld-4.0- LLVM-based linker
 lldb-4.0   - Next generation, high-performance debugger
 llvm-4.0   - Modular compiler and toolchain technologies
 llvm-4.0-dev - Modular compiler and toolchain technologies, libraries and 
header
 llvm-4.0-doc - Modular compiler and toolchain technologies, documentation
 llvm-4.0-examples - Modular compiler and toolchain technologies, examples
 llvm-4.0-runtime - Modular compiler and toolchain technologies, IR interpreter
 llvm-4.0-tools - Modular compiler and toolchain technologies, tools
 python-clang-4.0 - Clang Python Bindings
 python-lldb-4.0 - Next generation, high-performance debugger, python lib
Closes: 836397 856545 878502 880221 882505 882781 885827 889269
Changes:
 llvm-toolchain-4.0 (1:4.0.1-9) unstable; urgency=medium
 .
   * Create clang-tools-4.0 and move the various clang tools into it
 clang-tools-4.0 depends on clang-4.0. This might affect some packages.
 (Closes: #836397)
   * Update of the copyright file (Closes: #878502)
 Thanks to Nicholas D Steeves for the work
   * Take a patch for a stack alignment on sparc64 for rust
 Thanks to John Paul Adrian Glaubitz for the work (Closes: #880221)
   

Bug#890109: marked as done (octave-ltfat binary-all FTBFS: gzip: usr/share/octave/packages/ltfat-2.2.0/ChangeLog: No such file or directory)

[Debian Bug Tracking System]

Your message dated Mon, 12 Feb 2018 10:50:19 +
with message-id 
and subject line Bug#890109: fixed in octave-ltfat 2.2.0+dfsg-7
has caused the Debian Bug report #890109,
regarding octave-ltfat binary-all FTBFS: gzip: 
usr/share/octave/packages/ltfat-2.2.0/ChangeLog: No such file or directory
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.)


-- 
890109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890109
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: octave-ltfat
Version: 2.2.0+dfsg-6
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=octave-ltfat=all=2.2.0%2Bdfsg-6=1518327616=0

...
   dh_octave_changelogs -i -O--buildsystem=octave
gzip: 
debian/octave-ltfat-common/usr/share/octave/packages/ltfat-2.2.0/ltfat/inst/ChangeLog
debian/octave-ltfat-common/usr/share/octave/packages/ltfat-2.2.0/ChangeLog: No 
such file or directory
dh_octave_changelogs: gzip 
"debian/octave-ltfat-common/usr/share/octave/packages/ltfat-2.2.0/ltfat/inst/ChangeLog\
debian/octave-ltfat-common/usr/share/octave/packages/ltfat-2.2.0/ChangeLog" 
returned exit code 1
debian/rules:5: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 1
--- End Message ---
--- Begin Message ---
Source: octave-ltfat
Source-Version: 2.2.0+dfsg-7

We believe that the bug you reported is fixed in the latest version of
octave-ltfat, 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.
Rafael Laboissiere  (supplier of updated octave-ltfat 
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, 11 Feb 2018 22:18:20 -0200
Source: octave-ltfat
Binary: octave-ltfat octave-ltfat-common
Architecture: source
Version: 2.2.0+dfsg-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Octave Group 
Changed-By: Rafael Laboissiere 
Description:
 octave-ltfat - Large Time/Frequency Analysis Toolbox
 octave-ltfat-common - Large Time/Frequency Analysis Toolbox (arch-indep files)
Closes: 890109
Changes:
 octave-ltfat (2.2.0+dfsg-7) unstable; urgency=medium
 .
   * d/rules: Remove extraneous directory with duplicated ChangeLog
 (Closes: #890109)
Checksums-Sha1:
 25bc77b5e2e11aca0f0c24e2d9dc3a921910c3c1 2151 octave-ltfat_2.2.0+dfsg-7.dsc
 6351d515b452250b7d0c81c1baad5cd5511e4a9a 7156 
octave-ltfat_2.2.0+dfsg-7.debian.tar.xz
 436834b8692eef4516bd8535df889021b01cdc38 18844 
octave-ltfat_2.2.0+dfsg-7_amd64.buildinfo
Checksums-Sha256:
 debd1df0eb63adace265595d4be2abcf3da541bc645b1ca6930fd3aa1225b3ad 2151 
octave-ltfat_2.2.0+dfsg-7.dsc
 798da07dca68673d495c33ddbae22c5c5b554b14d8adf21a013751438727c31d 7156 
octave-ltfat_2.2.0+dfsg-7.debian.tar.xz
 0d9a94842be7c9388dbf109bd9deef7a1bb350cfe295fcf73ab7228168e513bc 18844 
octave-ltfat_2.2.0+dfsg-7_amd64.buildinfo
Files:
 c88e2902ec2d1bf7a22732e6c0394fe4 2151 math optional 
octave-ltfat_2.2.0+dfsg-7.dsc
 8b427b26f14b3645684b8424e803642a 7156 math optional 
octave-ltfat_2.2.0+dfsg-7.debian.tar.xz
 6f9f78afe6e3630bce9f947eb8d3d78c 18844 math optional 
octave-ltfat_2.2.0+dfsg-7_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEP0ZDkUmP6HS9tdmPISSqGYN4XJAFAlqBY2AACgkQISSqGYN4
XJCHzQ/+LFZxQDwlIRWj8z2sdhgZNOuUGtEJStzj5Q8+gphIQsf1MY1m8IzAwL6y
gcSQPKt4ueyFe5wBefI6XMHCWMxvp1R6Lt/6LWuhRTGFaSTY0ojT9zbRzVHtGUqo
o9L30kX5HxhhUvKFGaAcomvO+78zEwOH6RyvONmWKhH75xdbnIeEOj6N2/yCeOEs
95mfAgX/EYLO/72DnR+MpHjo7WA5xXb0LUD+qImFJctUaiwi10A36+3o/3b3j/3D
vzsS/it060KwZUUfpHEjg7jceSXNEpECugZUvH00VnDR1kjeCCIbaHAXZaHOHAJz
XP3LNGnSWr6/zuxt3j6uMBkauLKU2vmny16wd9mw7JbpUWucB3vLKGUyY/XZkrBb
RdkTVYQGeBNflA2JhIvFBMV031OiipUZnwNv5DOqbNmui5f4UmPl74IqqRtl0l97
o3rOsDWevA5oltABUPx3oFc1goLWdOU29WaIGnusJg03DzaNLCe360nq0KfGdkgl
Rw25ds4ne9+WnPFnnyIRcyCpjv8aa0ODv7U5OFtROJP8DCi3JsyI+Fjv9t3k2aYL
kKZaxys5+xEVgXyVlIt65MOCZk5Jen7ehhWQV5LC7ujNw/rU8pyF2UPgKwI9JPD0
RUSkRwVNo6Bcj+mnlohd7+1V1zrRtBAvDw+4PnqXlwB8v7LStOA=
=Jsr0
-END PGP SIGNATURE End Message ---

Bug#890109: Bug #890109 in octave-ltfat marked as pending

[rafael]

Control: tag -1 pending

Hello,

Bug #890109 in octave-ltfat 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/pkg-octave-team/octave-ltfat/commit/0cfa8995f242c1fdedd6afe39de437ad6cbf9e35


d/rules: Remove extraneous directory with duplicated ChangeLog

Closes: #890109



(this message was generated automatically)
-- 
Greetings

Processed: Bug #890109 in octave-ltfat marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #890109 [src:octave-ltfat] octave-ltfat binary-all FTBFS: gzip: 
usr/share/octave/packages/ltfat-2.2.0/ChangeLog: No such file or directory
Added tag(s) pending.

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

Bug#890229: marked as done (octave-doc: Fails to update)

[Debian Bug Tracking System]

Your message dated Mon, 12 Feb 2018 10:20:06 +
with message-id 
and subject line Bug#890229: fixed in octave 4.2.1-7
has caused the Debian Bug report #890229,
regarding octave-doc: Fails to update
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.)


-- 
890229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890229
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: octave-doc
Version: 4.2.1-6
Severity: normal

Dear Maintainer,

Unpacking octave-doc (4.2.1-6) ...
dpkg: error processing archive /tmp/apt-dpkg-install-DgBJLV/33-octave-
doc_4.2.1-6_all.deb (--unpack):
 trying to overwrite '/usr/share/info/errorbar.png', which is also in package
octave-info 4.2.1-5
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

regards



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

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

Versions of packages octave-doc depends on:
ii  info  6.5.0.dfsg.1-2

octave-doc recommends no packages.

Versions of packages octave-doc suggests:
ii  chromium [www-browser]  64.0.3282.119-2
ii  epiphany-browser [www-browser]  3.26.5.1-1
ii  evince [pdf-viewer] 3.26.0-3
ii  firefox [www-browser]   58.0.1-1
ii  w3m [www-browser]   0.5.3-36
ii  xpdf [pdf-viewer]   3.04-5

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: octave
Source-Version: 4.2.1-7

We believe that the bug you reported is fixed in the latest version of
octave, 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.
Sébastien Villemot  (supplier of updated octave package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 12 Feb 2018 10:39:08 +0100
Source: octave
Binary: octave octave-common octave-doc octave-htmldoc octave-info liboctave4 
liboctave-dev
Architecture: source
Version: 4.2.1-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Octave Group 
Changed-By: Sébastien Villemot 
Description:
 liboctave-dev - development files for the GNU Octave language
 liboctave4 - shared libraries of the GNU Octave language
 octave - GNU Octave language for numerical computations
 octave-common - architecture-independent files for octave
 octave-doc - documentation of the GNU Octave language
 octave-htmldoc - transitional package for Octave HTML documentation
 octave-info - transitional package for Octave info documentation
Closes: 889797 890229
Changes:
 octave (4.2.1-7) unstable; urgency=medium
 .
   * Add missing Breaks+Replaces on octave-doc against octave-{info,htmldoc}.
 (Closes: #890229)
   * octave now Recommends epstool (which is used by print.m). (Closes: #889797)
Checksums-Sha1:
 e3174e0b154ac5ff397158b812f1de32605f4d11 2978 octave_4.2.1-7.dsc
 fe463ae1683ecb106dc596db343690ea216d43cc 65176 octave_4.2.1-7.debian.tar.xz
 b0ae6adf7b8417aeee65eaf0c64f363bf4d73015 23429 octave_4.2.1-7_amd64.buildinfo
Checksums-Sha256:
 fbff2286c7d29404caeaed8079cbf50949877758990c55aec599496c13cbde02 2978 
octave_4.2.1-7.dsc
 229699919cf16019be1922c94fa9f548752e1676608d6daf3c7328f191618aeb 65176 
octave_4.2.1-7.debian.tar.xz
 5de81bcf8dd89a52a318057b3d4f429f0bf5503cbf57a8d7a73745fdfade28c5 23429 
octave_4.2.1-7_amd64.buildinfo
Files:
 1dbd251aff855fd35e7ae0159d369305 2978 math optional octave_4.2.1-7.dsc
 94d68bea0b8655de1661ecba48baa7fd 65176 math optional 
octave_4.2.1-7.debian.tar.xz
 5b1240b99c4249957f33088618b7a8c9 23429 math optional 
octave_4.2.1-7_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAlqBZmIACgkQLOzpNQ7O

Processed: block 889558 with 884130

[Debian Bug Tracking System]

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

> block 889558 with 884130
Bug #889558 [qtcreator] qtcreator: (Build-)Depends on obsolete libbotan1.10-dev
889558 was not blocked by any bugs.
889558 was blocking: 889675
Added blocking bug(s) of 889558: 884130
> thanks
Stopping processing here.

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

Bug#890229: Bug #890229 in octave marked as pending

[sebastien]

Control: tag -1 pending

Hello,

Bug #890229 in octave 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/pkg-octave-team/octave/commit/94b151b6793b71e30da3e02ebb63baf07145d543


Add missing Breaks+Replaces on octave-doc against octave-{info,htmldoc}.

Closes: #890229



(this message was generated automatically)
-- 
Greetings

Processed: Bug #890229 in octave marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #890229 [octave-doc] octave-doc: Fails to update
Added tag(s) pending.

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

Bug#890067: libgl1-mesa-dri: breaks kde experimental (sddm or sddm-greeter crash, ksplashscreen crash)

[Timo Aaltonen]

On 10.02.2018 20:57, Eric Valette wrote:
> Package: libgl1-mesa-dri
> Version: 18.0.0~rc2-1
> Severity: critical
> Justification: breaks unrelated software
> 
> After sucesfully upgrading this machine with experimental kde; libc6, mesa, I 
> went down and upgraded htpc and kids pc that are
> 
> AMD A4-5000
> AMD E2-1800
> AMD E1
> 
> respectively and all did break preventing to log in any way in kde session.
> Becasue one of the crash in one machine reported once  a bug in r600_dri.so
> ksplashqml[1148]: segfault at 7ffcac73c000 ip 7f9bf07d5be5 sp 
> 7ffcac739bf8 error 6 in r600_dri.so[7f9bf0394000+a86000]

18.0.0-rc4 is now pushed to experimental, please try with it once it's
built but if the driver still crashes, file a bug upstream.



-- 
t

Processed: severity of 890229 is serious

[Debian Bug Tracking System]

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

> severity 890229 serious
Bug #890229 [octave-doc] octave-doc: Fails to update
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#890122: marked as done (kcompletion FTBFS on architectures where Qt uses OpenGL ES)

[Debian Bug Tracking System]

Your message dated Mon, 12 Feb 2018 09:06:14 +
with message-id 
and subject line Bug#890122: fixed in kcompletion 5.42.0-3
has caused the Debian Bug report #890122,
regarding kcompletion FTBFS on architectures where Qt uses OpenGL ES
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.)


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

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
xvfb-run -a dh_auto_test
cd obj-arm-linux-gnueabi && make -j4 test ARGS\+=-j4
make[2]: Entering directory '/<>/obj-arm-linux-gnueabi'
Running tests...
/usr/bin/ctest --force-new-ctest-process -j4
Test project /<>/obj-arm-linux-gnueabi
Start 1: kcompletioncoretest
Start 2: klineedit_unittest
Start 3: kcombobox_unittest
Start 4: ksortablelisttest
1/4 Test #4: ksortablelisttest    Passed0.31 sec
2/4 Test #1: kcompletioncoretest ..***Exception: SegFault  0.36 sec
QStandardPaths: XDG_RUNTIME_DIR points to non-existing path '/run/user/2952', 
please create it with 0700 permissions.
libEGL warning: DRI2: failed to create any config

3/4 Test #2: klineedit_unittest ...***Exception: SegFault  0.38 sec
QStandardPaths: XDG_RUNTIME_DIR points to non-existing path '/run/user/2952', 
please create it with 0700 permissions.
libEGL warning: DRI2: failed to create any config

4/4 Test #3: kcombobox_unittest ...***Exception: SegFault  0.37 sec
QStandardPaths: XDG_RUNTIME_DIR points to non-existing path '/run/user/2952', 
please create it with 0700 permissions.
libEGL warning: DRI2: failed to create any config


25% tests passed, 3 tests failed out of 4

Total Test time (real) =   0.40 sec

The following tests FAILED:
  1 - kcompletioncoretest (SEGFAULT)
  2 - klineedit_unittest (SEGFAULT)
  3 - kcombobox_unittest (SEGFAULT)
Errors while running CTest
Makefile:122: recipe for target 'test' failed
make[2]: *** [test] Error 8


Fix (stolen from Ubuntu):

--- debian/rules.old2018-02-11 11:03:20.291380680 +
+++ debian/rules2018-02-11 11:03:36.281213576 +
@@ -15,4 +15,4 @@
dh_strip --dbgsym-migration='libkf5completion5-dbg (<= 5.19.0-1~~)'
 
 override_dh_auto_test:
-   xvfb-run -a dh_auto_test
+   xvfb-run -a --server-args="-screen 0 1024x768x24+32" dh_auto_test
--- End Message ---
--- Begin Message ---
Source: kcompletion
Source-Version: 5.42.0-3

We believe that the bug you reported is fixed in the latest version of
kcompletion, 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.
Maximiliano Curia  (supplier of updated kcompletion 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, 12 Feb 2018 08:45:37 +0100
Source: kcompletion
Binary: libkf5completion-data libkf5completion-dev libkf5completion-doc 
libkf5completion5
Architecture: source
Version: 5.42.0-3
Distribution: sid
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Maximiliano Curia 
Description:
 libkf5completion-data - Widgets with advanced auto-completion features.
 libkf5completion-dev - development files for kcompletion
 libkf5completion-doc - Widgets with advanced auto-completion features 
(documentation)
 libkf5completion5 - Widgets with advanced auto-completion features.
Closes: 890122
Changes:
 kcompletion (5.42.0-3) sid; urgency=medium
 .
   [ Maximiliano Curia ]
   * New revision
   * Release to sid
 .
   [ Adrian Bunk ]
   * Fix FTBFS on architectures where Qt uses OpenGL ES (Closes: 890122)
Checksums-Sha1:
 26c2c90060b689e416d6588c3cb5009bebcd9fae 2590 kcompletion_5.42.0-3.dsc
 64d023ebabe28e1b9d2a7c37de91fa5b8a60ce08 9636 
kcompletion_5.42.0-3.debian.tar.xz
 90d50346f21bf406c6ab8a2bf472de5f33865f98 14689