Processed: your mail

[Debian Bug Tracking System]

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

> fixed 859655 1:0.0~git20170407.0.55a552f-1
Bug #859655 [src:golang-go.crypto] golang-go.crypto: CVE-2017-3204
Marked as fixed in versions golang-go.crypto/1:0.0~git20170407.0.55a552f-1.
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> fixed 859655 
> 1:0.0~git20170407.0.55a552f+REALLY.0.0~git20161012.0.5f31782-1~bpo8+1
Bug #859655 [src:golang-go.crypto] golang-go.crypto: CVE-2017-3204
Marked as fixed in versions 
golang-go.crypto/1:0.0~git20170407.0.55a552f+REALLY.0.0~git20161012.0.5f31782-1~bpo8+1.
> fixed 859655 1:0.0~git20170425.0.c7af5bf-1
Bug #859655 [src:golang-go.crypto] golang-go.crypto: CVE-2017-3204
The source 'golang-go.crypto' and version '1:0.0~git20170425.0.c7af5bf-1' do 
not appear to match any binary packages
Marked as fixed in versions golang-go.crypto/1:0.0~git20170425.0.c7af5bf-1.
> thanks
Stopping processing here.

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

Bug#861782: marked as done (mariadb-server-10.1: Upgrade fails because mariadb-server-10.1.prerm fails to stop mysqld.)

[Debian Bug Tracking System]

Your message dated Thu, 04 May 2017 06:03:59 +
with message-id 
and subject line Bug#861782: fixed in mariadb-10.1 10.1.23-1
has caused the Debian Bug report #861782,
regarding mariadb-server-10.1: Upgrade fails because mariadb-server-10.1.prerm 
fails to stop mysqld.
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.)


-- 
861782: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861782
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mariadb-server-10.1
Version: 10.1.22-4
Severity: important

Dear Maintainer,

Upgrade from 1 month old version failed.

Installation says:

There is a MySQL server running, but we failed in our attempts to stop it.
Stop it yourself and try again!

and fails.

When looking at:
/var/lib/dpkg/info/mariadb-server-10.1.prerm
one can see:
invoke-rc.d mysql stop
pidof -c /usr/sbin/mysqld

Executing those lines myself, I get:
# invoke-rc.d mysql stop; pidof -c /usr/sbin/mysqld
3174

Similarly:
# systemctl stop mariadb.service; pidof -c /usr/sbin/mysqld
3174

However I could stop the sever as a plain user:
$ akonadictl stop

Verify it is stopped:
# pidof -c /usr/sbin/mysqld

Then the upgrade worked flawlessly:
# apt-get upgrade

A very verbose description can be found there:
https://lists.debian.org/debian-kde/2017/05/msg0.html


Best,
Chris



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

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

Versions of packages mariadb-server-10.1 depends on:
ii  adduser   3.115
ii  debconf [debconf-2.0] 1.5.60
ii  galera-3  25.3.20-1
ii  gawk  1:4.1.4+dfsg-1
ii  init-system-helpers   1.48
ii  iproute2  4.9.0-1
ii  libaio1   0.3.110-3
ii  libc6 2.24-10
ii  libdbi-perl   1.636-1+b1
ii  libpam0g  1.1.8-3.5
ii  libstdc++66.3.0-16
ii  lsb-base  9.20161125
ii  lsof  4.89+dfsg-0.1
ii  mariadb-client-10.1   10.1.22-4
ii  mariadb-common10.1.22-4
ii  mariadb-server-core-10.1  10.1.22-4
ii  passwd1:4.4-4
ii  perl  5.24.1-2
ii  psmisc22.21-2.1+b2
ii  rsync 3.1.2-2
ii  socat 1.7.3.1-2+b1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages mariadb-server-10.1 recommends:
ii  libhtml-template-perl  2.95-2

Versions of packages mariadb-server-10.1 suggests:
ii  bsd-mailx [mailx]  8.1.2-0.20160123cvs-4
pn  mariadb-test   
pn  netcat-openbsd 
pn  tinyca 

-- debconf information:
  mariadb-server-10.1/postrm_remove_databases: false
  mariadb-server-10.1/nis_warning:
  mariadb-server-10.1/old_data_directory_saved:
--- End Message ---
--- Begin Message ---
Source: mariadb-10.1
Source-Version: 10.1.23-1

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

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated mariadb-10.1 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 04 May 2017 07:23:23 +0200
Source: mariadb-10.1
Binary: libmariadbclient18 libmariadbclient-dev libmariadbclient-dev-compat 
libmariadbd18 libmariadbd-dev mariadb-common mariadb-client-core-10.1 
mariadb-client-10.1 mariadb-server-core-10.1 mariadb-server-10.1 mariadb-server 
mariadb-client mariadb-plugin-connect mariadb-plugin-oqgraph 
mariadb-plugin-tokudb mariadb-plugin-mroonga mariadb-plugin-spider 
mariadb-plugin-gssapi-server mariadb-plugin-gssapi-client 
mariadb-plugin-cracklib-password-check mariadb-test mariadb-test-data
Architecture: source
Version: 10.1.23-1
Distribution: unstable
Urgency: medium
Maintainer: Debian MySQL Maintainers 
Changed-By: Ondřej 

Processed: severity of 861782 is serious

[Debian Bug Tracking System]

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

> severity 861782 serious
Bug #861782 [mariadb-server-10.1] mariadb-server-10.1: Upgrade fails because 
mariadb-server-10.1.prerm fails to stop mysqld.
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: Re: Bug#860660: golang-github-cznic-fileutil: FTBFS on i386: dh_auto_test

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/cznic/fileutil/issues/16
Bug #860660 [src:golang-github-cznic-fileutil] golang-github-cznic-fileutil: 
FTBFS on i386: dh_auto_test: go test -v -p 1 github.com/cznic/fileutil 
github.com/cznic/fileutil/falloc github.com/cznic/fileutil/hdb 
github.com/cznic/fileutil/storage returned exit code 1
Set Bug forwarded-to-address to 'https://github.com/cznic/fileutil/issues/16'.
> tag -1 +patch
Bug #860660 [src:golang-github-cznic-fileutil] golang-github-cznic-fileutil: 
FTBFS on i386: dh_auto_test: go test -v -p 1 github.com/cznic/fileutil 
github.com/cznic/fileutil/falloc github.com/cznic/fileutil/hdb 
github.com/cznic/fileutil/storage returned exit code 1
Added tag(s) patch.

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

Bug#860660: golang-github-cznic-fileutil: FTBFS on i386: dh_auto_test

[Roger Shimizu]

control: forwarded -1 https://github.com/cznic/fileutil/issues/16
control: tag -1 +patch

Backport the patch from upstream, FTBFS issue seems fixed.
So I pushed commit to master (w/o the releasing commit), and mentors branch
with the releasing commit.

Package is uploaded to mentors for RFS.
Thank you!

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1


pgp2bFHUyOGrJ.pgp
Description: PGP signature

Bug#860660: Pending fixes for bugs in the golang-github-cznic-fileutil package

[pkg-go-maintainers]

tag 860660 + pending
thanks

Some bugs in the golang-github-cznic-fileutil package are closed in
revision a8dbbc2c3e52e0d5dae95878a9725b48487b6baf in branch 'master'
by Roger Shimizu

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-cznic-fileutil.git/commit/?id=a8dbbc2

Commit message:

debian/patches: Add a patch from upstream

Patch to fix FTBFS on 32-bit system

Closes: #860660

Processed: Pending fixes for bugs in the golang-github-cznic-fileutil package

[Debian Bug Tracking System]

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

> tag 860660 + pending
Bug #860660 [src:golang-github-cznic-fileutil] golang-github-cznic-fileutil: 
FTBFS on i386: dh_auto_test: go test -v -p 1 github.com/cznic/fileutil 
github.com/cznic/fileutil/falloc github.com/cznic/fileutil/hdb 
github.com/cznic/fileutil/storage returned exit code 1
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#860952: marked as done (Statically linked to glibc, in breach of policy and copyright)

[Debian Bug Tracking System]

Your message dated Thu, 04 May 2017 04:03:36 +
with message-id 
and subject line Bug#860952: fixed in rar 2:5.4.0+dfsg.1-0.1
has caused the Debian Bug report #860952,
regarding Statically linked to glibc, in breach of policy and 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.)


-- 
860952: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860952
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rar
Version: 2:5.4.0-1
Severity: serious

Policy forbids executables statically linked to glibc (though other
C libraries such as dietlibc are allowed).

This is also a copyright violation.  Proprietary programs can
generally be dynamically linked with glibc and distributed under the
terms of LGPL 2.1 section 6, but a statically linked binary does not
comply - there are no object files for the rest of rar, and we don't
even know which version of glibc to provide source for.

Ben.

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

Kernel: Linux 4.9.0-2-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 ---
Source: rar
Source-Version: 2:5.4.0+dfsg.1-0.1

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated rar package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 04 May 2017 03:52:05 +0100
Source: rar
Binary: rar
Architecture: source
Version: 2:5.4.0+dfsg.1-0.1
Distribution: unstable
Urgency: medium
Maintainer: Martin Meredith 
Changed-By: Ben Hutchings 
Description:
 rar- Archiver for .rar files
Closes: 693396 860952
Changes:
 rar (2:5.4.0+dfsg.1-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Upstream re-release excludes statically linked rar
 (Closes: #693396, #860952)
   * Install dynamically linked rar
   * Use debhelper compatibility level 9
Checksums-Sha1:
 a8c2abf714663db8d4b60739de8c7d927bc49134 2015 rar_5.4.0+dfsg.1-0.1.dsc
 3eb60caadfa4534beda7be059cb9b47451c1125a 531782 
rar_5.4.0+dfsg.1.orig-amd64.tar.gz
 861e51ef4a8a170a4a7db656627c8228d8571988 541123 rar_5.4.0+dfsg.1.orig.tar.gz
 5c6c901db9ffa576978e2181f40740bde660822b 9124 
rar_5.4.0+dfsg.1-0.1.debian.tar.xz
 3a047554cde1ef5d00ade2d1325e6118be136184 5637 
rar_5.4.0+dfsg.1-0.1_source.buildinfo
Checksums-Sha256:
 d3fd081b4a6c3bd455a3df756e10d3f7310d15809471429dc1c5ac6fa0bb 2015 
rar_5.4.0+dfsg.1-0.1.dsc
 264b7f09270c44ee9be5f0e8e8cab48781822c9d3aa6caf078af01719511b6de 531782 
rar_5.4.0+dfsg.1.orig-amd64.tar.gz
 ea4ec74f1692ceff09e890a427eed3257400124a1e0c173f53737a37993ade6e 541123 
rar_5.4.0+dfsg.1.orig.tar.gz
 dfc75f9516b4bdc1910bd8147d15c5699f745c76a74a33f5d2576854cfd91ad3 9124 
rar_5.4.0+dfsg.1-0.1.debian.tar.xz
 048b229041d3f980c685e7e5d109cd96a7472489dcd4e49b50f8c917bb52c5a2 5637 
rar_5.4.0+dfsg.1-0.1_source.buildinfo
Files:
 6e4f05c3a05bc43f3eaab0da36e6d163 2015 non-free/utils optional 
rar_5.4.0+dfsg.1-0.1.dsc
 d02b8742478d5e6428c12ee14b2a678d 531782 non-free/utils optional 
rar_5.4.0+dfsg.1.orig-amd64.tar.gz
 efa2a5a29f57f34999a9bae355510618 541123 non-free/utils optional 
rar_5.4.0+dfsg.1.orig.tar.gz
 a8223a408d2e8e3be2e73caf21da259d 9124 non-free/utils optional 
rar_5.4.0+dfsg.1-0.1.debian.tar.xz
 aa92212e604f7c183d5a56d7dfc2a6dd 5637 non-free/utils optional 
rar_5.4.0+dfsg.1-0.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEErCspvTSmr92z9o8157/I7JWGEQkFAlkKos4ACgkQ57/I7JWG
EQmfGQ//eoLUyixAk/0LEYyTBcD7nvbig/2bTnVnWmI1deDLXr/QsH5cXw2obk1F
rP9L8C2r9TU7Q+FAUsxjRP1zGqjoXkqiCEOlSCkHJjqhEIDIhjnI7GaM7m/2KU8f
ge8x6QchnPz6xCaV4KhH2negpM/jF7vCQyayzXXn1Hw3Uoxvrfjq7TgBpVTB1MCw
WBcajFSxuv1C5h8V3ka9ZSoBflGnrft+8asGB3CSwOryTQyQArlVHhXcrRkWInKc
fP0JiTSxKRykfr2TWntP4hRpa/k8lLZZ

Processed: Re: [Letsencrypt-devel] Bug#861696: certbot: Python package not found.

[Debian Bug Tracking System]

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

> tag 861696 +unreproducible +wontfix
Bug #861696 [certbot] certbot: Python package not found.
Added tag(s) unreproducible.
Bug #861696 [certbot] certbot: Python package not found.
Added tag(s) wontfix.
> thanks
Stopping processing here.

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

Bug#861696: marked as done (certbot: Python package not found.)

[Debian Bug Tracking System]

Your message dated Wed, 3 May 2017 23:21:11 -0400
with message-id 

and subject line Re: [Letsencrypt-devel] Bug#861696: certbot: Python package 
not found.
has caused the Debian Bug report #861696,
regarding certbot: Python package not found.
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.)


-- 
861696: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861696
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: certbot
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?
test -x /usr/bin/certbot -a \! -d /run/systemd/system && perl -e 'sleep 
int(rand(3600))' && certbot -q renew
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Installed certbot. I think it's missing a TTY handler. The Jessie version works.


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

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

Traceback (most recent call last):
  File "/usr/bin/certbot", line 11, in 
load_entry_point('certbot==0.10.2', 'console_scripts', 'certbot')()
  File 
"/usr/local/lib/python2.7/dist-packages/distribute-0.6.28-py2.7.egg/pkg_resources.py",
 line 337, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
  File 
"/usr/local/lib/python2.7/dist-packages/distribute-0.6.28-py2.7.egg/pkg_resources.py",
 line 2311, in load_entry_point
return ep.load()
  File 
"/usr/local/lib/python2.7/dist-packages/distribute-0.6.28-py2.7.egg/pkg_resources.py",
 line 2017, in load
entry = __import__(self.module_name, globals(),globals(), ['__name__'])
  File "/usr/lib/python2.7/dist-packages/certbot/main.py", line 11, in 
import zope.component
  File "/usr/lib/python2.7/dist-packages/zope/component/__init__.py", line 19, 
in 
from zope.interface import named
ImportError: cannot import name named
--- End Message ---
--- Begin Message ---
tag 861696 +unreproducible +wontfix
thanks

Hello Jeff!  Thanks for your report.

This looks like it's a result of some locally installed python
packages that are interfering with the version of python packages that
certbot depends on.  Specifically, it looks like certbot is grabbing
some things out of a deprecated setuptools fork -- the traceback shows
that load_entry_point is getting called from a distribute egg in
/usr/local/lib.

I'd recommend either removing these libraries entirely, or setting
PYTHONPATH inside the cronjob (and systemd timer!) to exclude
/usr/local/lib.

Sincerely,
-- 
Harlan Lieberman-Berg
~hlieberman--- End Message ---

Processed: fails every time

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #851877 [src:sslh] sslh: FTBFS randomly (sbuild hangs)
Severity set to 'serious' from 'important'

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

Bug#859524: libpfm4: Unexpected libpfm abi change between libpfm-4.7 and libpfm-4.8

[Andreas Beckmann]

On 2017-04-11 22:07, Andreas Beckmann wrote:
> I just uploaded a git snaphot reverting the abi change (and implementing
> an alternate solution) plus an s390x patch from the mailing list to
> experimental. If that builds everywhere and 4.9 doesn't come in time,
> I'll upload it to unstable. And thereafter upload papi with a bumped
> build dependency.

4.9 didn't get released so far, therefore a new libpfm4 snapshot
(including the s390x patch) is now in unstable and a papi with a bumped
B-D, too.


Andreas

Bug#861711: marked as done (buildd.debian.org: Architecture: all B-D confusion)

[Debian Bug Tracking System]

Your message dated Thu, 4 May 2017 00:25:21 +0200
with message-id <20170503222521.63zqqyqa7qgjo...@aurel32.net>
and subject line Re: Bug#861711: buildd.debian.org: Architecture: all B-D 
confusion
has caused the Debian Bug report #861711,
regarding buildd.debian.org: Architecture: all B-D confusion
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.)


-- 
861711: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861711
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: buildd.debian.org
Severity: serious
Justification: makes some packages fail to build from source

Per https://buildd.debian.org/status/package.php?p=gsequencer&suite=sid ,
gsequencer shows up as BD-Uninstallable for Architecture: all with the
explanation

gsequencer build-depends on missing:
- liboss4-salsa-dev:amd64

gsequencer specifies an appropriate architecture restriction here:

Build-Depends: debhelper (>= 10), autotools-dev, dh-autoreconf, pkg-config, 
libcunit1-dev, libgtk2.0-dev, libcairo2-dev, xvfb, xauth, libx11-dev, 
libinstpatch-dev, libsndfile1-dev, libsamplerate-dev, libxml2-dev, ladspa-sdk, 
dssi-dev, lv2-dev, libgmp-dev, libasound2-dev [linux-any], liboss4-salsa-dev 
[!linux-any], oss4-dev [kfreebsd-any], libjack-dev, uuid-dev, docbook-xsl, 
docbook-xml, gtk-doc-tools, xsltproc

Its maintainers could probably stand to split out B-D-Arch and
B-D-Indep settings, but my understanding is that the Architecture: all
build should have been able to proceed regardless; it certainly did in
the past.

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
--- End Message ---
--- Begin Message ---
On 2017-05-02 21:51, Aaron M. Ucko wrote:
> Package: buildd.debian.org
> Severity: serious
> Justification: makes some packages fail to build from source
> 
> Per https://buildd.debian.org/status/package.php?p=gsequencer&suite=sid ,
> gsequencer shows up as BD-Uninstallable for Architecture: all with the
> explanation
> 
> gsequencer build-depends on missing:
> - liboss4-salsa-dev:amd64
> 
> gsequencer specifies an appropriate architecture restriction here:
> 
> Build-Depends: debhelper (>= 10), autotools-dev, dh-autoreconf, pkg-config, 
> libcunit1-dev, libgtk2.0-dev, libcairo2-dev, xvfb, xauth, libx11-dev, 
> libinstpatch-dev, libsndfile1-dev, libsamplerate-dev, libxml2-dev, 
> ladspa-sdk, dssi-dev, lv2-dev, libgmp-dev, libasound2-dev [linux-any], 
> liboss4-salsa-dev [!linux-any], oss4-dev [kfreebsd-any], libjack-dev, 
> uuid-dev, docbook-xsl, docbook-xml, gtk-doc-tools, xsltproc
> 
> Its maintainers could probably stand to split out B-D-Arch and
> B-D-Indep settings, but my understanding is that the Architecture: all
> build should have been able to proceed regardless; it certainly did in
> the past.
> 
> Could you please take a look?

I have pushed a patch to fix that. The package has now been built.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net--- End Message ---

Bug#861486: [Pkg-julia-devel] Bug#861486: Bug#861486: Bug#861486: Bug#861486: julia: FTBFS on mips64el (segmentation fault)

[Graham Inggs]

On 3 May 2017 at 13:17, Aurelien Jarno  wrote:
> The problem only happens when using multiple OpenMP threads, it can be
> workarounded by setting OMP_NUM_THREADS=1.

Thanks for investigating!
Modifying debian/rules as follows did work:

override_dh_link-arch:
# Create *.so symlinks for dlopen'd libraries in private libdir.
OMP_NUM_THREADS=1 make -f debian/shlibdeps.mk $(COMMON_FLAGS)
debian/julia.links
dh_link

> I *guess* therefore that either
> openblas should be built with OpenMP support or that suitesparse should
> not use OpenMP.

Another option is to build Julia on mips64el with blas and lapack
instead of openblas.
This works for mips64el, but makes no difference to the arm64 issue in #861484.

Bug#859462: marked as done (telepathy-qt FTBFS on ppc64el: undefined reference to QTest::qCompare)

[Debian Bug Tracking System]

Your message dated Wed, 03 May 2017 21:34:34 +
with message-id 
and subject line Bug#859462: fixed in telepathy-qt 0.9.6.1-6.1
has caused the Debian Bug report #859462,
regarding telepathy-qt FTBFS on ppc64el: undefined reference to QTest::qCompare
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.)


-- 
859462: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859462
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: telepathy-qt
Version: 0.9.6.1-6
Severity: serious

telepathy-qt FTBFS on ppc64el (originally reported by Frederic Bonnard):

...
[ 93%] Linking CXX executable test-contacts-capabilities
cd /home/bunk/build/telepathy-qt-0.9.6.1/build-qt5/tests/dbus && /usr/bin/cmake 
-E cmake_link_script CMakeFiles/test-contacts-capabilities.dir/link.txt 
--verbose=1
/usr/bin/c++   -g -O2 
-fdebug-prefix-map=/home/bunk/build/telepathy-qt-0.9.6.1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -Wall -Wextra -Wsign-compare -Wpointer-arith 
-Wformat-security -Winit-self -Wnon-virtual-dtor 
-Wno-missing-field-initializers -Wno-unused-parameter 
-Wno-unused-local-typedefs -fPIC  -O2 -ggdb  -Wl,-z,relro -Wl,--no-add-needed 
CMakeFiles/test-contacts-capabilities.dir/contacts-capabilities.cpp.o  -o 
test-contacts-capabilities 
-Wl,-rpath,/home/bunk/build/telepathy-qt-0.9.6.1/build-qt5/tests/lib/glib:/home/bunk/build/telepathy-qt-0.9.6.1/build-qt5/TelepathyQt
 -rdynamic /usr/lib/powerpc64le-linux-gnu/libQt5Test.so.5.7.1 
../lib/libtp-qt-tests.a ../lib/glib/libtp-glib-tests.so 
../lib/glib-helpers/libtp-qt-tests-glib-helpers.a -lgio-2.0 -ldbus-1 
../lib/glib/call/libexample-cm-call.a 
../lib/glib/callable/libexample-cm-callable.a 
../lib/glib/contactlist/libexample-cm-contactlist.a 
../lib/glib/echo/libexample-cm-echo.a ../li
 b/glib/echo2/libexample-cm-echo2.a 
../lib/glib/future/extensions/libtp-glib-tests-future-extensions.a 
../../TelepathyQt/libtelepathy-qt5.so.0.0.9.6.1 
/usr/lib/powerpc64le-linux-gnu/libQt5DBus.so.5.7.1 
/usr/lib/powerpc64le-linux-gnu/libQt5Network.so.5.7.1 
/usr/lib/powerpc64le-linux-gnu/libQt5Xml.so.5.7.1 
/usr/lib/powerpc64le-linux-gnu/libQt5Core.so.5.7.1 -ltelepathy-glib -lglib-2.0 
-lgobject-2.0 -lglib-2.0 -ldbus-glib-1 
CMakeFiles/test-contacts-capabilities.dir/contacts-capabilities.cpp.o: In 
function `TestContactsCapabilities::testCapabilities()':
./build-qt5/tests/dbus/./tests/dbus/contacts-capabilities.cpp:138: undefined 
reference to `bool QTest::qCompare(bool const&, int const&, char 
const*, char const*, char const*, int)'
collect2: error: ld returned 1 exit status
tests/dbus/CMakeFiles/test-contacts-capabilities.dir/build.make:121: recipe for 
target 'tests/dbus/test-contacts-capabilities' failed
make[4]: *** [tests/dbus/test-contacts-capabilities] Error 1


Complete log is attached.


LOG.telepathy-qt.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: telepathy-qt
Source-Version: 0.9.6.1-6.1

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

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

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

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer  (supplier of updated telepathy-qt 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 03 May 2017 22:56:53 +0200
Source: telepathy-qt
Binary: libtelepathy-qt4-2 libtelepathy-qt4-farstream2 libtelepathy-qt4-dev 
libtelepathy-qt4-dbg libtelepathy-qt4-doc libtelepathy-qt5-0 
libtelepathy-qt5-farstream0 libtelepathy-qt5-dev libtelepathy-qt5-dbg
Architecture: source
Version: 0.9.6.1-6.1
Distribution: unstable
Urgency: medium
Maintainer: Debian KDE Extras Team 
Changed-By: Dr. Tobias Quathamer 
Description:
 libtelepathy-qt4-2 - Telepathy framework - Qt 4 library
 libtelepathy-qt4-dbg - Qt 4 Telepathy library (debug symbols)
 libtelepathy-qt4-dev - Qt 4 Telepathy library (headers and static library)
 libtelepathy-qt4-doc - Qt 4 Telepathy library (documentation)
 libtelepathy-qt4-farstream2 - Telepathy/Farsight integration - Qt 4 library
 libtelepathy-qt5-0 - Telepathy framework - Qt 5 library
 libtele

Bug#861474: slim: Session restarts in a loop renedering whole system useless.

[Mateusz Łukasik]

W dniu 03.05.2017 o 17:42, Apollon Oikonomopoulos pisze:

Hi Mateusz,

On 17:12 Tue 02 May , Apollon Oikonomopoulos wrote:

The attached debdiff resolves the restart loop, while ensuring that
slim plays nice with plymouth. If nobody responds, I intend to NMU the
package tomorrow.


Would you like to update the package, or should I go ahead with the NMU
as described above?

Regards,
Apollon



Hi Apollon,

Go ahead, I don't have time on this week to check that.

--
 .''`.  Mateusz Łukasik
: :' :  http://mati75.eu
`. `'   Debian Member - mat...@linuxmint.pl
  `-GPG: D93B 0C12 C8D0 4D7A AFBC  FA27 CCD9 1D61 11A0 6851

Bug#859462: NMU for stretch release

[Dr. Tobias Quathamer]

Hi,

I've just uploaded a new version with this fix included. The debdiff is 
attached.


Regards,
Tobias
diff -Nru telepathy-qt-0.9.6.1/debian/changelog telepathy-qt-0.9.6.1/debian/changelog
--- telepathy-qt-0.9.6.1/debian/changelog	2016-04-06 20:14:17.0 +0200
+++ telepathy-qt-0.9.6.1/debian/changelog	2017-05-03 22:56:53.0 +0200
@@ -1,3 +1,11 @@
+telepathy-qt (0.9.6.1-6.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add fix-failing-test.patch to fix failing tests on some architectures
+(Closes: #859462)
+
+ -- Dr. Tobias Quathamer   Wed, 03 May 2017 22:56:53 +0200
+
 telepathy-qt (0.9.6.1-6) unstable; urgency=medium
 
   * Add fix-deprecated-bsd-source.patch
diff -Nru telepathy-qt-0.9.6.1/debian/patches/fix-failing-test.patch telepathy-qt-0.9.6.1/debian/patches/fix-failing-test.patch
--- telepathy-qt-0.9.6.1/debian/patches/fix-failing-test.patch	1970-01-01 01:00:00.0 +0100
+++ telepathy-qt-0.9.6.1/debian/patches/fix-failing-test.patch	2017-05-03 22:53:06.0 +0200
@@ -0,0 +1,15 @@
+Author: David Edmundson 
+Description: Use C++ bool type rather than mixing with gboolean
+ They are not always the same size.
+ This fixes a compile error on some systems.
+--- a/tests/dbus/contacts-capabilities.cpp
 b/tests/dbus/contacts-capabilities.cpp
+@@ -111,7 +111,7 @@
+ QStringList ids = QStringList() << QLatin1String("alice")
+ << QLatin1String("bob") << QLatin1String("chris");
+ 
+-gboolean supportTextChat[] = { TRUE, FALSE, FALSE };
++bool supportTextChat[] = { true, false, false };
+ 
+ TpHandleRepoIface *serviceRepo =
+ tp_base_connection_get_handles(TP_BASE_CONNECTION(mConn->service()),
diff -Nru telepathy-qt-0.9.6.1/debian/patches/series telepathy-qt-0.9.6.1/debian/patches/series
--- telepathy-qt-0.9.6.1/debian/patches/series	2016-03-25 21:55:06.0 +0100
+++ telepathy-qt-0.9.6.1/debian/patches/series	2017-05-03 22:53:27.0 +0200
@@ -3,3 +3,4 @@
 gstreamer-1.5.patch
 force-service-pic.patch
 fix-deprecated-bsd-source.patch
+fix-failing-test.patch


signature.asc
Description: OpenPGP digital signature

Bug#861771: Fails to install: postinst script returned error exit status 1

[Ryan Kavanagh]

Package: nodm
Version: 0.13-1.2
Severity: grave

nodm fails to install/upgrade. Please see the attached output from
journalctl -xe. I marked the severity as grave because the package fails
to install/upgrade, thus rendering it unusable to (all?) users.

--8<---
$ sudo apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Setting up nodm (0.13-1.2) ...
Job for nodm.service failed because the control process exited with error code.
See "systemctl status nodm.service" and "journalctl -xe" for details.
invoke-rc.d: initscript nodm, action "start" failed.
● nodm.service - Display manager for automatic session logins
   Loaded: loaded (/lib/systemd/system/nodm.service; static; vendor preset: 
enabled)
   Active: activating (auto-restart) (Result: exit-code) since Wed 2017-05-03 
16:05:42 EDT; 7ms ago
 Docs: man:nodm(8)
  Process: 20265 ExecStartPre=/usr/bin/test ${NODM_ENABLED} != no -a 
${NODM_ENABLED} != false (code=exited, status=1/FAILURE)

May 03 16:05:42 zeta systemd[1]: nodm.service: Unit entered failed state.
May 03 16:05:42 zeta systemd[1]: nodm.service: Failed with result 'exit-code'.
dpkg: error processing package nodm (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 nodm
E: Sub-process /usr/bin/dpkg returned an error code (1)
$ sudo systemctl status nodm.service
● nodm.service - Display manager for automatic session logins
   Loaded: loaded (/lib/systemd/system/nodm.service; static; vendor preset: 
enabled)
   Active: failed (Result: exit-code) since Wed 2017-05-03 16:06:47 EDT; 3min 
41s ago
 Docs: man:nodm(8)
  Process: 20844 ExecStartPre=/usr/bin/test ${NODM_ENABLED} != no -a 
${NODM_ENABLED} != false (code=exited, status=1/FAILURE)

May 03 16:06:47 zeta systemd[1]: nodm.service: Unit entered failed state.
May 03 16:06:47 zeta systemd[1]: nodm.service: Failed with result 'exit-code'.
May 03 16:06:47 zeta systemd[1]: nodm.service: Service hold-off time over, 
scheduling restart.
May 03 16:06:47 zeta systemd[1]: Stopped Display manager for automatic session 
logins.
May 03 16:06:47 zeta systemd[1]: nodm.service: Start request repeated too 
quickly.
May 03 16:06:47 zeta systemd[1]: Failed to start Display manager for automatic 
session logins.
May 03 16:06:47 zeta systemd[1]: nodm.service: Unit entered failed state.
May 03 16:06:47 zeta systemd[1]: nodm.service: Failed with result 'exit-code'.
--8<---


-- System Information:
Debian Release: 9.0
  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.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_CA.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages nodm depends on:
ii  debconf [debconf-2.0]  1.5.60
ii  libc6  2.24-10
ii  libpam0g   1.1.8-3.5
ii  libx11-6   2:1.6.4-3
ii  lsb-base   9.20161125
ii  x11-common 1:7.7+19
ii  xserver-xorg-core  2:1.19.3-1

nodm recommends no packages.

nodm suggests no packages.

-- debconf information:
  nodm/first_vt: 7
* shared/default-x-display-manager: xdm
  nodm/min_session_time: 60
  nodm/x_timeout: 300
  nodm/x_options: -nolisten tcp
  nodm/user: rak
  nodm/daemon_name: /usr/sbin/nodm
* nodm/enabled: false
  nodm/xsession: /etc/X11/Xsession

-- 
|_)|_/  Ryan Kavanagh  | GPG: 4E46 9519 ED67 7734 268F
| \| \  https://ryanak.ca/ |  BD95 8F7B F8FC 4A11 C97A
May 03 16:06:40 zeta sudo[20525]: pam_unix(sudo:session): session closed for 
user root
May 03 16:06:41 zeta sudo[20665]:  rak : TTY=pts/8 ; PWD=/home/rak ; 
USER=root ; COMMAND=/usr/bin/apt upgrade
May 03 16:06:41 zeta sudo[20665]: pam_unix(sudo:session): session opened for 
user root by rak(uid=0)
May 03 16:06:46 zeta systemd[1]: Reloading.
May 03 16:06:46 zeta systemd[1]: Starting Display manager for automatic session 
logins...
-- Subject: Unit nodm.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit nodm.service has begun starting up.
May 03 16:06:46 zeta systemd[1]: nodm.service: Control process exited, 
code=exited status=1
May 03 16:06:46 zeta systemd[1]: Failed to start Display manager for automatic 
session logins.
-- Subject: Unit nodm.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit nodm.service has failed.
-- 
-- The result is failed.
May 03 16:06:46 zeta sy

Bug#861767: libgetdata: Incomplete debian/copyright?

[Chris Lamb]

Source: libgetdata
Version: 0.10.0-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Alastair McKinstry 

Hi,

I just ACCEPTed libgetdata from NEW but noticed it was missing 
attribution in debian/copyright for at least m4/ax_compare_version.m4.

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

Processed: Re: xpuzzles: package not comply with DFSG, it should be in non-free

[Debian Bug Tracking System]

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

> retitle 861750 xpuzzles: "without fee" requirement in copyright renders 
> package non-DFSG compliant
Bug #861750 [xpuzzles] xpuzzles: package not comply with DFSG, it should be in 
non-free
Changed Bug title to 'xpuzzles: "without fee" requirement in copyright renders 
package non-DFSG compliant' from 'xpuzzles: package not comply with DFSG, it 
should be in non-free'.
> thanks
Stopping processing here.

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

Bug#859262: marked as done (gnome-orca: Gets stuck if target app is busy)

[Debian Bug Tracking System]

Your message dated Wed, 03 May 2017 18:48:40 +
with message-id 
and subject line Bug#859262: fixed in gnome-orca 3.22.2-3
has caused the Debian Bug report #859262,
regarding gnome-orca: Gets stuck if target app is busy
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.)


-- 
859262: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859262
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: synaptic
Version: 0.84.2
Severity: grave

Synaptic often freezes the Orca screen reader so that Orca speaks nothing until
Synaptic is closed. The same happens on both of my laptops running Debian
Stretch.

I am blind so I have to use computer using Orca screen reader. It happens wery
often that when I e.g click the Reload button in Synaptic, or select Reload
from the Synaptic menu, then Orca screen reader stops speaking. Synapticdoes
not freeze the whole desktop, just Orca.  This problem seems to happen
randomly, sometimes it happens sometimes it does not. When Synaptic has
finished reloading the package database information Orca may start speaking
again, but often it does not. If it does not then I have to close the Synaptic
by pressing alt + F4 after which Orca starts to speak again.

It also happens sometimes that if I have reloaded repository package database
information and click Mark all updades after that then Orca stops speaking. On
my second laptop it currently happens almost every time that Orca stops
speaking when I click the Mark all updates or select it from the menu. Tkhat
also seems to happen randomly, sometimes it happens sometimes not.

I have not noticed any problems like that when I have used other applications,
this happns only when I am using Synaptic.

As I said I have two laptops running Debian Stretch and both have the same
problems. Both laptops have been upgraded from Jessie to Stretch. The first
laptop was almost clean Jessie installation before it was upgraded to Stretch,
it still has wery little apps installed.

I am using Gnome desktop. I am blind so it is difficult for me to try to figure
out what is wrong. I I have used both espeak and espeak-ng speech synthetisers
with Orca screen reader, the same problem exists notmatter which of those is in
use.



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

Kernel: Linux 4.9.0-2-amd64 (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)

Versions of packages synaptic depends on:
ii  hicolor-icon-theme   0.15-1
ii  libapt-inst2.0   1.4~rc2
ii  libapt-pkg5.01.4~rc2
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-9
ii  libcairo-gobject21.14.8-1
ii  libcairo21.14.8-1
ii  libept1.5.0  1.1+nmu3+b1
ii  libgcc1  1:6.3.0-11
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0 2.50.3-2
ii  libgnutls30  3.5.8-3
ii  libgtk-3-0   3.22.9-4
ii  libpango-1.0-0   1.40.4-1
ii  libpangocairo-1.0-0  1.40.4-1
ii  libpcre2-8-0 10.22-3
ii  libstdc++6   6.3.0-11
ii  libvte-2.91-00.46.1-1
ii  libx11-6 2:1.6.4-3
ii  libxapian30  1.4.3-1
ii  policykit-1  0.105-17
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages synaptic recommends:
ii  libgtk2-perl   2:1.2499-1
ii  rarian-compat  0.8.1-6+b1
ii  xdg-utils  1.1.1-1

Versions of packages synaptic suggests:
ii  apt-xapian-index 0.49
pn  deborphan
pn  dwww 
ii  menu 2.1.47+b1
ii  software-properties-gtk  0.96.20.2-1
ii  tasksel  3.39

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gnome-orca
Source-Version: 3.22.2-3

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated gnome-orca 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 

Bug#859560: fixed in xen 4.8.1-1

[Maximilian Engelhardt]

On Dienstag, 25. April 2017 00:08:20 CEST Ivar Smolin wrote:
> On Tue, 18 Apr 2017 17:34:15 + Ian Jackson
> 
>  wrote:
> > Source: xen
> > Source-Version: 4.8.1-1
> > 
> > We believe that the bug you reported is fixed in the latest version of
> > xen, which is due to be installed in the Debian FTP archive.
> 
> Thanks for fixing!
> 
> This bug affects also Xen 4.4.x, Jessie is still vulnerable.


Hi, what's the status of this in Jessie?

According to https://security-tracker.debian.org/tracker/CVE-2017-7228 Jessie 
is still vulnerable.

Thanks,
Maxi

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

Bug#861575: tilix: Does not start on Stretch (symbol lookup error: undefined symbol)

[Mathieu Basille]

Hey Jason,

Thanks for looking it up! As a matter of fact, it looks like both
libgtkd-3-0 and libvted-3-0 needs to be >= 3.5.1-1. Installing both
libraries from unstable (both v.3.5.1-1) fixes the problem, and Tilix is
able to run with it.

Cheers,
Mathieu.


On 05/03/2017 01:42 AM, Jason Crain wrote:
> On Sun, Apr 30, 2017 at 06:43:18PM -0400, Mathieu Basille wrote:
>> Following the name change from terminix to tilix, I updated 
>> my Stretch system (which uses apt pining to install Sid 
>> packages whenever possible) to use the new developments of 
>> tilix.
>>
>> Install of v1.5.4-1 works without any problem, but I'm unable
>> to run tilix:
>>
>> tilix: symbol lookup error: tilix: undefined symbol:
>>  
>> _D7gobject7ObjectG7ObjectG11addOnNotifyMFDFC7gobject9ParamSpec9ParamSpecC7gobject7ObjectG7ObjectGZvAyaE4gtkc12gobjecttypes13GConnectFlagsZm
> ...
>>
>> Versions of packages tilix depends on:
>> ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2+b1
>> ii  libc62.24-10
>> ii  libgtkd-3-0  3.3.1-2
>> ii  libphobos2-ldc71 1:1.1.1-1
>> ii  libvted-3-0  3.3.1-2
>> ii  libx11-6 2:1.6.4-3
>> ii  tilix-common 1.5.4-1
> 
> tilix seems to require libgtkd-3-0 >= 3.5.1-1 and should have its
> Depends increased.
> 

-- 

Ce message est signé pour en assurer l'authenticité.
Pour une correspondance avec moi réellement privée,
utilisez ma clé publique pour chiffrer vos messages :

  http://mathieu.basille.net/pub.asc

Plus d'infos : http://mzl.la/1BsOGiZ



signature.asc
Description: OpenPGP digital signature

Bug#861480: ImportError: No module named QtWebKit

[Dejan Muhamedagic]

On Sat, Apr 29, 2017 at 11:25:41PM +0200, Michal Čihař wrote:
> Gammu/Wammu should work as well [1], though the GUI is probably not
> that nice.
> 
> [1]:https://wammu.eu/docs/manual/protocol/s60.html

Unfortunately the gnapplet thing won't run on my S60 phone (Nokia
C05 I think), so I cannot test wammu. Anyway, apparently the
porting shouldn't be so difficult.

Bug#798601: marked as done (limereg: FTBFS on mips/mipsel)

[Debian Bug Tracking System]

Your message dated Wed, 03 May 2017 16:48:45 +
with message-id 
and subject line Bug#798601: fixed in limereg 1.4.1-2
has caused the Debian Bug report #798601,
regarding limereg: FTBFS on mips/mipsel
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.)


-- 
798601: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798601
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: limereg
Version: 1.4.0-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

your package no longer builds on mips and mipsel autobuilders, see
https://buildd.debian.org/status/logs.php?pkg=limereg&ver=1.4.0-1%2Bb1&suite=sid

Cheers,
Julien


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: limereg
Source-Version: 1.4.1-2

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated limereg package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 03 May 2017 18:30:28 +0200
Source: limereg
Binary: limereg liblimereg-dev liblimereg1
Architecture: source
Version: 1.4.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Mattia Rizzolo 
Description:
 liblimereg-dev - Library for lightweight image registration [development files]
 liblimereg1 - Library for lightweight image registration
 limereg- Lightweight Image Registration
Closes: 798601
Changes:
 limereg (1.4.1-2) unstable; urgency=medium
 .
   * Team upload.
   * Add patch to fix FTBFS in mips/mipsel.  Closes: #798601
 Thanks to James Cowgill  for the patch.
Checksums-Sha1:
 9af0d1f876cd3e372af8dbbd9f35f186ec571634 2230 limereg_1.4.1-2.dsc
 aadf0452dac629e6f16ac5a8b41c0bfa42c9dc8d 4576 limereg_1.4.1-2.debian.tar.xz
 aa41d9cab59c19e2bff03b1daa245320eb952bad 15051 limereg_1.4.1-2_amd64.buildinfo
Checksums-Sha256:
 2348e2febead4b8577810325d30fa3a214a63340e3676e3f30a4ff4ad77ac87b 2230 
limereg_1.4.1-2.dsc
 069e6099abf9052b7fb85395c478a54214c1734362275ae92e618b6ad14abf0c 4576 
limereg_1.4.1-2.debian.tar.xz
 da121b63a2fe02ce79674a0c6be671c9128929f8105c761e52ffbad0977b9e69 15051 
limereg_1.4.1-2_amd64.buildinfo
Files:
 13533862cef9053b7fd9e588f0bdcb92 2230 science optional limereg_1.4.1-2.dsc
 04fccfcf5584f4382d031705babbc372 4576 science optional 
limereg_1.4.1-2.debian.tar.xz
 a3df61a0503fe7a817c1640ed14c614b 15051 science optional 
limereg_1.4.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAlkKBnIACgkQCBa54Yx2
K606+A//YDJehha7fDElRtLkCRKrRCHXyROaBsJ/Q98KcU/6PBA6t5U0KxLUghXb
LxZtotCc+BoV204KMZAIVKOtLfKgHObA29NEDy1pH9M/Dr3WaDYFVReHmYcYCa6D
gdBjwZvZ72wdmSE2hn0D2uTQ5UVVctbgBmcCm7peYDj2SNuHA1SoDxgJeSkCx48l
n4F5lU62ah4BHU+iOnSrAuYk/eGWjnmBP4IL5RMhB+oFts2cnOHQsIsyiPlHI65x
uKcJGwZ9MEaN0zM0OwjBl8HBArZg5ZaMkTUCyydG47WSojbBSq2likpl9bsf5i1U
nqFR0ywKHjY7zMsQbLsJ5iQl8rMLCujPlK6a0qSMxu91YR3zAY7SCT5liFTJ3v3V
Hnw04yFA66UIDONrynf+TAYO9ZZZztFmqsaHHG7x1oMrUVIMGwEVK5+2HURBqE3v
1h6S3tjCOi+HJaQ+rZHTOqfTVhG+noG7Jotkx/ffuDdtftLGHiZ11GM5Kj+MFPTA
y5MQR2FfQitjewcI+l7dZgKUSydc+uNKX9Tg9I8ABleNl8WAYhVz6KAtZL+fgNkM
6Sl+643fYGOdGb5jmBZ5vlbkyJWrpSaUIPEIrCdIsVBJD7f29vqEEgfV6fFJxsZr
s9L/Q7hZfzmL3EELQORDufBcd7MxZMscMPp4pwOo+ldYC9sTzUU=
=CbY2
-END PGP SIGNATURE End Message ---

Bug#798601: limereg: FTBFS on mips/mipsel

[Mattia Rizzolo]

On Wed, May 03, 2017 at 05:19:37PM +0100, James Cowgill wrote:
> It looks like this was just an uninitialized variable in
> test_searchSubimage.c. Applying the attached patch fixes this issue for
> me on mipsel.


Thank you for the patch!
Uploading :)

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Processed: Triaging and downgrading severity (includes rationale and suggestions)

[Debian Bug Tracking System]

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

> severity 861169 important
Bug #861169 [src:opendkim] opendkim: Systemd service file should not specify a 
socket
Severity set to 'important' from 'grave'
> retitle 861169 systemd service overrides opendkim.conf socket at start
Bug #861169 [src:opendkim] opendkim: Systemd service file should not specify a 
socket
Changed Bug title to 'systemd service overrides opendkim.conf socket at start' 
from 'opendkim: Systemd service file should not specify a socket'.
> thanks
Stopping processing here.

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

Processed: #798601 is forwarded

[Debian Bug Tracking System]

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

> forwarded 798601 https://github.com/RoelofBerg/limereg/issues/2
Bug #798601 [src:limereg] limereg: FTBFS on mips/mipsel
Set Bug forwarded-to-address to 
'https://github.com/RoelofBerg/limereg/issues/2'.
> thanks
Stopping processing here.

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

Bug#861169: Triaging and downgrading severity (includes rationale and suggestions)

[Henrique de Moraes Holschuh]

severity 861169 important
retitle 861169 systemd service overrides opendkim.conf socket at start
thanks


The previous report mentioned by the bug submitter is #853769.
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853769)

>From that bug report, message #38
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853769#38)
says:

Using the existing service file I confirmed that changes in
/etc/opendkim.conf do affect the configuration of the running
service after it is restarted.  There's no change needed.

Apparently, this not correct when the service is started, or at least in
the specific way the submitter used to configure opendkim.


Still, the behavior described in this new bug report is exactly how the
sysvinit script behaves (according to #853769), which means the local
admin is supposed to *override* this in the initscript.  While this is
NOT nearly as userfriendly as one might like, the *same* logic may be
applied to systemd support if no better fix is possible at this time.

IMHO, if a better choice is not available (e.g. due to security concerns
or complexity of the required fix to avoid regressing any
already-installed systems that depended on the initscript/systemd unit
forced unix socket path), this could be properly documented in
NEWS.debian/README.debian and also in the default /etc/ config file (and
maybe as comments in the systemd unit and also the sysvinit initscript
-- being through in these things pays off).


I am downgrading this bug to important (which does *NOT* mean it should
not be fixed, and if the fix is actually going to be just documentation,
IMO that fix should be uploaded ASAP since it has zero regression risk
and should be present in the next Debian stable if possible).

Reasons for the severity downgrade:

1.  It does *NOT* render the package unusable to the majority of its
users, and it only affects more complex setups that would never
work out-of-the-box without local configuration being done.

2.  AFAIK, it matches previous behavior of Debian stable, and also when
using initscripts instead of systemd.

3.  It is not a regression in itself, and it doesn't cause regressions
when the package is updated, as far as I can tell.

4.  The issue it causes is going to be detected when the local admin is
first configuring opendkim, and it is easy to work around (by
editing the sysvinit script -- which is a conffile -- or by dropping an
override for the systemd unit in the appropriate place under /etc).

Bugs #853769 and #861169 are available as temporary documentation
for the issue and provide hints to the required configuration change
for the workaround.

5.  The "grave" severity is very troublesome for every package depending
on opendkim, and risks kicking all those packages out of the next
Debian stable.

-- 
  Henrique Holschuh

Bug#798601: limereg: FTBFS on mips/mipsel

[James Cowgill]

Control: tags -1 patch

Hi,

I investigated this a bit by comparing in gdb a good version of limereg
compiled without -Ofast and -fstack-protector and the original version.

It looks like this was just an uninitialized variable in
test_searchSubimage.c. Applying the attached patch fixes this issue for
me on mipsel.

Thanks,
James
--- a/tests/test_searchSubimage.c
+++ b/tests/test_searchSubimage.c
@@ -86,6 +86,7 @@ bool test_searchSubimage()
 	const unsigned int skipLvl=2;
 	struct Limereg_AdvancedRegControl advancedRegControl;
 	advancedRegControl.maxIterations = 50;
+	advancedRegControl.stopSensitivity = 0;
 	advancedRegControl.pyramidLevelCount = pyramidLvl;
 	advancedRegControl.skipFineLevelCount = skipLvl;
 	advancedRegControl.startParameters = &startParams;


signature.asc
Description: OpenPGP digital signature

Processed: Bug#798601: limereg: FTBFS on mips/mipsel

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #798601 [src:limereg] limereg: FTBFS on mips/mipsel
Added tag(s) patch.

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

Bug#861755: libpll: FTBFS on x86: AVX target specific option mismatch

[Aaron M. Ucko]

Source: libpll
Version: 0.0+20160909+ds1-1
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)

Builds of libpll on x86 architectures (even kfreebsd-amd64) fail too:

  libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -Wsign-compare -D_GNU_SOURCE -std=c99 -O3 -msse3 -g 
-c core_partials_avx.c  -fPIC -DPIC -o .libs/libpll_la-core_partials_avx.o
  core_partials_avx.c: In function 'pll_core_create_lookup_4x4_avx':
  core_partials_avx.c:155:11: warning: AVX vector return without AVX enabled 
changes the ABI [-Wpsabi]
  [...]
  /usr/lib/gcc/x86_64-kfreebsd-gnu/6/include/avxintrin.h:1270:1: error: 
inlining failed in call to always_inline '_mm256_set_epi64x': target specific 
option mismatch

It appears to be performing CPU type detection at build time rather
than runtime.  As such, please specify --disable-avx everywhere and
--disable-sse on i386 and ensure that the resulting configurations
build.

Thanks!

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

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#861748: r-cran-rmpi: Loading library fails

[Ralf Stubner]

On Wed, May 3, 2017 at 5:42 PM, Dirk Eddelbuettel  wrote:
>
> I think I found it.  Do an 'apt-get install libopenmpi-dev' and it will work.

I was about to write that 'pkg-config --libs ompi' produces an error
and that there is no libmpi.so on my system. After installing
libopenmpi-dev, both symptoms go away and I am able to load the Rmpi
library. thanks a lot!

> Looks like we are missing an ldconfig run there.

Is it really an ldconfig runthat is missing? To me it looks like the
necessary link for libmpi.so is set-up by libopenmpi-dev and not
libopenmpi2. So either r-cran-rmpi should (also) depend on
libopenmpi-dev, or creating this link should be moved to libopenmpi2.

Greetings
Ralf

Processed: severity of 861746 is important

[Debian Bug Tracking System]

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

> severity 861746 important
Bug #861746 [src:linux] linux-image-4.9.0-2-amd64: Infinity `soft lockup` at 
kernel 4.9.0-1+ on HP ProLiant DL360G5
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Bug#861474: slim: Session restarts in a loop renedering whole system useless.

[Apollon Oikonomopoulos]

Hi Mateusz,

On 17:12 Tue 02 May , Apollon Oikonomopoulos wrote:
> The attached debdiff resolves the restart loop, while ensuring that 
> slim plays nice with plymouth. If nobody responds, I intend to NMU the 
> package tomorrow.

Would you like to update the package, or should I go ahead with the NMU 
as described above?

Regards,
Apollon

Bug#861748: r-cran-rmpi: Loading library fails

[Dirk Eddelbuettel]

On 3 May 2017 at 09:36, Dirk Eddelbuettel wrote:
| 
| This may have something to do with it:
| 
|   root@ef11adb9da1c:/# pkg-config --libs ompi
|   -L/usr/lib/x86_64-linux-gnu/openmpi/lib -L/usr//lib -lmpi
|   root@ef11adb9da1c:/#
| 
| This is what we use at build-time.  Yet:
| 
|   root@ef11adb9da1c:/# ls -l /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi.*
|   lrwxrwxrwx 1 root root 16 Feb 10 05:43 
/usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi.so -> libmpi.so.20.0.2
|   -rw-r--r-- 1 root root 919704 Feb 10 05:43 
/usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi.so.20.0.2
|   root@ef11adb9da1c:/#
|   root@ef11adb9da1c:/# ldconfig -p|grep libmpi.so
|   libmpi.so.20 (libc6,x86-64) => /lib/x86_64-linux-gnu/libmpi.so.20
|   root@ef11adb9da1c:/# 
| 
| Looks like ldconfig is unaware of libmpi.so.  But why? Maybe this?
| 
|   root@ef11adb9da1c:/# ls -l /etc/alternatives/libmpi*
|   lrwxrwxrwx 1 root root 47 May  3 14:26 /etc/alternatives/libmpi.so -> 
/usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi.so
|   lrwxrwxrwx 1 root root 51 May  3 14:26 /etc/alternatives/libmpi++.so -> 
/usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi_cxx.so
|   root@ef11adb9da1c:/#
| 
| Weirder still, now that I ran `ldconfig` a few times it loads (but dies over
| an OpenMPI config wart in the Docker container I am in right now).

I think I found it.  Do an 'apt-get install libopenmpi-dev' and it will work.

Looks like we are missing an ldconfig run there.

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Processed: Re: Bug#860747: dh_ruby: please inject versioned dependency on ruby metapackage

[Debian Bug Tracking System]

Processing control commands:

> severity 860747 serious
Bug #860747 [ruby-all-dev] ruby-all-dev: include upper bound on generated ruby 
dependencies
Severity set to 'serious' from 'normal'
> tag 860747 stretch-ignore jessie-ignore
Bug #860747 [ruby-all-dev] ruby-all-dev: include upper bound on generated ruby 
dependencies
Added tag(s) stretch-ignore and jessie-ignore.

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

Bug#861152: marked as done (nagstamon: InsecureRequestWarning: Unverified HTTPS request is being made.)

[Debian Bug Tracking System]

Your message dated Wed, 03 May 2017 15:04:32 +
with message-id 
and subject line Bug#861152: fixed in nagstamon 2.0.1-5
has caused the Debian Bug report #861152,
regarding nagstamon: InsecureRequestWarning: Unverified HTTPS request is being 
made.
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.)


-- 
861152: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861152
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nagstamon
Version: 2.0.1-1
Severity: serious
Tags: security

When I run nagstamon from a terminal against the Debian nagios I get a
warning about unverified and thus insecure HTTPS requests being made:

https://nagios.debian.org/icinga/
https://dsa.debian.org/ (see here for guest login)

$ nagstamon 
...
/usr/lib/python3/dist-packages/urllib3/connectionpool.py:845: 
InsecureRequestWarning: Unverified HTTPS request is being made. Adding 
certificate verification is strongly advised. See: 
https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
  InsecureRequestWarning)

-- System Information:
Debian Release: 9.0
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (860, 
'testing-proposed-updates'), (800, 'unstable-debug'), (800, 'unstable'), (790, 
'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 
'buildd-experimental')
Architecture: amd64
 (x86_64)

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

Versions of packages nagstamon depends on:
ii  libqt5multimedia5-plugins5.7.1~20161021-2
ii  python3-bs4  4.5.3-1
ii  python3-dbus.mainloop.pyqt5  5.7+dfsg-5
ii  python3-pkg-resources33.1.1-1
ii  python3-psutil   5.0.1-1
ii  python3-pyqt55.7+dfsg-5
ii  python3-pyqt5.qtmultimedia   5.7+dfsg-5
ii  python3-pyqt5.qtsvg  5.7+dfsg-5
ii  python3-requests 2.12.4-1
pn  python3:any  

nagstamon recommends no packages.

nagstamon suggests no packages.

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: nagstamon
Source-Version: 2.0.1-5

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

Debian distribution maintenance software
pp.
Moritz Schlarb  (supplier of updated nagstamon package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 03 May 2017 14:47:04 +0200
Source: nagstamon
Binary: nagstamon
Architecture: source
Version: 2.0.1-5
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Moritz Schlarb 
Description:
 nagstamon  - Nagios status monitor which takes place in systray or on desktop
Closes: 861152
Changes:
 nagstamon (2.0.1-5) unstable; urgency=medium
 .
   * Don't disable InsecureRequestWarning warnings from urllib3
 Closes: #861152
Checksums-Sha1:
 a841acbecf877d4cc80ceb77bef69a865fb96056 2025 nagstamon_2.0.1-5.dsc
 4a56705fe03286ebfb0cd5117f458c07058cdefa 7380 nagstamon_2.0.1-5.debian.tar.xz
Checksums-Sha256:
 65189abbcd388e22e7ce51bc19275fd4bb7831ec5974793c7aa42e09040c8f5a 2025 
nagstamon_2.0.1-5.dsc
 7f337fa044cb5b3226a16432fe57037da9475aa99b9971d0b1e87c14d18cb9cd 7380 
nagstamon_2.0.1-5.debian.tar.xz
Files:
 7558b03bfacacac19b3ef031cc6a03fe 2025 utils optional nagstamon_2.0.1-5.dsc
 68f65ed7e6fdf5b571212061b3181a0d 7380 utils optional 
nagstamon_2.0.1-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJZCedfAAoJEPqBswqWsQmcPukP/iFh5RkwdmhvifO5jew1WujJ
xJSd2Ja0te5SYDlYbRjqnbPj5t9txfXZ2uo3dyql07zHmAN6ajfBK9+oBrBNJNUU
eECjrxB5e1MpyePWAyq7vVtJ8Ss0GLSxm/U6l3HSpa6Cw0DKrTVzSgwvf3LD18YD
OTNeZeZAWXOoighGo/JOAMRj93uQ2tyIFlKSCuFWeO8/upRq3HW7YWekySTlRDDJ
1h9kb9HgjSN+3qmbxiW4i7xHjVq0OTDGarGflxNYPyk8FGw/Ul0eW/m+jArCpAW4
XHuM6vQn8gskDHC9e7tzq+qefWDrRMIK5UMuGVHS0vOQO4NyvFRYlKoant+QQxIB
6sXTLNCDQ8C3oOf13V8l7M/REE95B

Bug#853167: marked as done (ganeti-instance-debootstrap: OS installations fails because sfdisk believes the disk is in use)

[Debian Bug Tracking System]

Your message dated Wed, 03 May 2017 15:03:56 +
with message-id 
and subject line Bug#853167: fixed in ganeti-instance-debootstrap 0.16-2
has caused the Debian Bug report #853167,
regarding ganeti-instance-debootstrap: OS installations fails because sfdisk 
believes the disk is in use
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.)


-- 
853167: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ganeti-instance-debootstrap
Version: 0.16-1
Severity: important

Dear Maintainer,

as agreed on IRC I'll submit this bug for you to triage.

The OS installation through ganeti-instance-debootstrap fails on
stretch because sfdisk believes that the disk is in use.

I'm using the drbd disk template in a two node cluster.

```
Mon Jan 30 13:01:58 2017 * running the instance OS create scripts...
Failure: command execution error:
Could not add os for instance kirk.chaos.hg.tu-darmstadt.de on node
deimos.darmstadt.ccc.de: OS create script failed (exited with exit code
1), last lines in the log file:
This disk is currently in use - repartitioning is probably a bad idea.
Umount all file systems, and swapoff all swap partitions on this disk.
Use the --no-reread flag to suppress this check.

sfdisk: Use the --force flag to overrule all checks.
```

Adding `--force` to the sfdisk call in 
/usr/share/ganeti/os/debootstrap/common.sh:98
will allow for completion of the os installation.
Adding `--no-reread` didn't change a thing for me.


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

Kernel: Linux 4.9.0-1-amd64 (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)

Versions of packages ganeti-instance-debootstrap depends on:
ii  debootstrap  1.0.87
ii  dump 0.4b46-3+b1
ii  kpartx   0.6.4-3

ganeti-instance-debootstrap recommends no packages.

ganeti-instance-debootstrap suggests no packages.

-- Configuration Files:
/etc/ganeti/instance-debootstrap/variants.list changed:
stretch
default


-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ganeti-instance-debootstrap
Source-Version: 0.16-2

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

Debian distribution maintenance software
pp.
Apollon Oikonomopoulos  (supplier of updated 
ganeti-instance-debootstrap package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 03 May 2017 16:44:54 +0300
Source: ganeti-instance-debootstrap
Binary: ganeti-instance-debootstrap
Architecture: source all
Version: 0.16-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ganeti Team 
Changed-By: Apollon Oikonomopoulos 
Description:
 ganeti-instance-debootstrap - debootstrap-based instance OS definition for 
ganeti
Closes: 853167
Changes:
 ganeti-instance-debootstrap (0.16-2) unstable; urgency=medium
 .
   * Skip newer sfdisk's check using the BLKRRPART ioctl (Closes: #853167).
 This check will always fail with non-partitionable devices, such as DRBD
 and LVM, completely breaking disk partitioning. Thanks to Martin Weinelt
  for testing and feedback!
Checksums-Sha1:
 ed9cce509c60c2230c8aa0415ea2311e74819b83 2212 
ganeti-instance-debootstrap_0.16-2.dsc
 263f5b9fe98b89b8c4cb263cf1e7f187f1e39402 8468 
ganeti-instance-debootstrap_0.16-2.debian.tar.xz
 d3dd96c4ee5d181e93459b8c51fcbcc8ebed61b4 19610 
ganeti-instance-debootstrap_0.16-2_all.deb
 3d9118513170c04e609aa46f6bcdc0cd05bdf582 6326 
ganeti-instance-debootstrap_0.16-2_amd64.buildinfo
Checksums-Sha256:
 822071013b6c03c903f347b1f469b63edffd243dd991043815a95fd3cc241fc2 2212 
ganeti-instance-debootstrap_0.16-2.dsc
 1bb77afc3dab40bf77f2e9886741728e87524116dd5a5a2eac04a3af5e1d3555 8468 
ganeti-instance-debootstrap_0.16-2.debian.tar.xz
 aa8760c1bef8bae81d7303438e7d448aa72e280721f5f74ab4c49a7d4d7da99c 19610 
ganeti-instance-debootstrap_0.16-2_all.deb
 

Bug#861748: r-cran-rmpi: Loading library fails

[Dirk Eddelbuettel]

This may have something to do with it:

  root@ef11adb9da1c:/# pkg-config --libs ompi
  -L/usr/lib/x86_64-linux-gnu/openmpi/lib -L/usr//lib -lmpi
  root@ef11adb9da1c:/#

This is what we use at build-time.  Yet:

  root@ef11adb9da1c:/# ls -l /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi.*
  lrwxrwxrwx 1 root root 16 Feb 10 05:43 
/usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi.so -> libmpi.so.20.0.2
  -rw-r--r-- 1 root root 919704 Feb 10 05:43 
/usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi.so.20.0.2
  root@ef11adb9da1c:/#
  root@ef11adb9da1c:/# ldconfig -p|grep libmpi.so
  libmpi.so.20 (libc6,x86-64) => /lib/x86_64-linux-gnu/libmpi.so.20
  root@ef11adb9da1c:/# 

Looks like ldconfig is unaware of libmpi.so.  But why? Maybe this?

  root@ef11adb9da1c:/# ls -l /etc/alternatives/libmpi*
  lrwxrwxrwx 1 root root 47 May  3 14:26 /etc/alternatives/libmpi.so -> 
/usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi.so
  lrwxrwxrwx 1 root root 51 May  3 14:26 /etc/alternatives/libmpi++.so -> 
/usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi_cxx.so
  root@ef11adb9da1c:/#

Weirder still, now that I ran `ldconfig` a few times it loads (but dies over
an OpenMPI config wart in the Docker container I am in right now).

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#861748: r-cran-rmpi: Loading library fails

[Dirk Eddelbuettel]

On 3 May 2017 at 15:11, Ralf Stubner wrote:
| Package: r-cran-rmpi
| Version: 0.6-6-3
| Severity: grave
| Justification: renders package unusable
| 
| Dear Maintainer,
| 
| When I try to load the Rmpi library, it fails with an error about a missing
| shared object file:
| 
| $ LANG=C Rscript -e "library(Rmpi)"
| libmpi.so: cannot open shared object file: No such file or directory
| Error : .onLoad failed in loadNamespace() for 'Rmpi', details:
|   call: fun(libname, pkgname)
|   error: Cannot start MPI_Init(). Exit
| Error: package or namespace load failed for 'Rmpi'
| Execution halted

Darn. 
 
| Any idea what is going on here?

Upstream changes in MPI, likely.  The new 2.* release may be here.

I recall from first updating OpenMPI in Debian a decade ago I had to fight
quite a bit with symbols spread over several shared library.  We "eventually"
figured out the flags we needed for dlopen in upstream's Rmpi.  It may be
related.

Do you think you may have a chance to poke around?

Dirk

 
| Greetings
| Ralf
| 
| 
| -- System Information:
| Debian Release: 9.0
|   APT prefers testing
|   APT policy: (500, 'testing')
| Architecture: i386 (i686)
| 
| Kernel: Linux 4.9.0-2-686-pae (SMP w/2 CPU cores)
| Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
| Shell: /bin/sh linked to /bin/dash
| Init: systemd (via /run/systemd/system)
| 
| Versions of packages r-cran-rmpi depends on:
| ii  libc6  2.24-9
| ii  libopenmpi22.0.2-2
| ii  mpi-default-bin1.8
| ii  r-base-core [r-api-3]  3.3.3-1
| 
| r-cran-rmpi recommends no packages.
| 
| Versions of packages r-cran-rmpi suggests:
| pn  r-cran-rsprng  
| 
| -- no debconf information

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#861750: xpuzzles: package not comply with DFSG, it should be in non-free

[Anon Sricharoenchai]

Package: xpuzzles
Version: 5.5.4.1-2
Severity: serious
Justification: Policy 2.2.1

*** Please type your report below this line ***
According to the copyright file in this package,

   #  Permission to use, copy, modify, and distribute this software and
   #  its documentation for any purpose and without fee is hereby granted,

It not allow selling the software, so the package should be in non-free
archive.


-- System Information:
Debian Release: testing/unstable
Architecture: i386 (i686)
Kernel: Linux 2.6.8.1-3-386
Locale: LANG=en_US, LC_CTYPE=en_US

Versions of packages xpuzzles depends on:
ii  libc6   2.3.5-1ubuntu12.5.10.1   GNU C Library: Shared libraries an
ii  libice6 4.3.0.dfsg.1-6ubuntu25.3 Inter-Client Exchange library
ii  libsm6  4.3.0.dfsg.1-6ubuntu25.3 X Window System Session Management
ii  libx11-64.3.0.dfsg.1-6ubuntu25.3 X Window System protocol client li
ii  libxt6  4.3.0.dfsg.1-6ubuntu25.3 X Toolkit Intrinsics
ii  xlibs   4.3.0.dfsg.1-6ubuntu25.3 X Window System client libraries m

-- no debconf information

Bug#861656: [PKG-Openstack-devel] Bug#861656: BROKEN: 0.4.11 lacks support for get_info and URLs with a prefix path

[Antoine Musso]

Le 02/05/2017 à 15:22, Thomas Goirand a écrit :
> 
> How come this issue is only reported now? The package was uploaded in
> this version more than a year ago.
>
> The main reason why I maintain python-jenkins, is for Jenkins Jobs
> Builder. I believe it's not affected by this, is it?

I haven't hit the issue until I tried to upgrade a software on a jessie
machine having python-jenkins.  And I guess close to nobody uses the
python-jenkins Debian package unless they happen to install Jenkins Job
Builder.


> What do you mean by "creating a node"?

That is the method create_node which is to attach a slave to a Jenkins
instance.  Definitely not used by Jenkins Job Builder.



There is another bug. When the target URL has a suffix such as
https://integration.wikimedia.org/ci/ . With python-jenkins 0.4.11

>>> from jenkins import Jenkins
>>> j = Jenkins('https://integration.wikimedia.org/ci/')
>>> j.get_info()
Traceback (most recent call last):
  File "", line 1, in 
  File "jenkins/__init__.py", line 461, in get_info
Request(self._build_url(url))
  File "jenkins/__init__.py", line 361, in jenkins_open
raise NotFoundException('Requested item could not be found')
jenkins.NotFoundException: Requested item could not be found

That is fixed by 2aa1a5f1b8 released with 0.4.12.



> Last, do you believe the release team will accept using 0.4.12 instead?
> I do not want to upload to later on figure out the release team refuses
> the upload. I'm asking for pre-approval. If it's not granted, I'll keep
> the old version in testing.


0.4.11 to 0.4.12 is only a few patches.

$ git log --oneline --no-merges 0.4.11..0.4.12
dccae5f Drop py33 support
302eb5d Fixed create_node() Error
83c53c4 Deprecated tox -downloadcache option removed
2aa1a5f Use TestWithScenarios to add additional url tests
46a2f0a Change repositories from stackforge to openstack
3b2dc28 Update .gitreview for new namespace
$

Most are related to testing or are solely metadata. The two patches that
change code in jenkins are:


1)  302eb5d Fixed create_node() Error

Fix the issue I reported in this bug, does not impact Jenkins Job Builder.

2) 2aa1a5f Use TestWithScenarios to add additional url tests

That fix the example I gave above when trying to get_info() from a
remote Jenkins.


So yeah I think the Debian release team should trust our judgement as
python-jenkins maintainers and happilly accepts the version bump for the
benefit of the Debian project.

cheers,

-- 
Antoine "hashar" Musso

Bug#853167: ganeti-instance-debootstrap: OS installations fails because sfdisk believes the disk is in use

[hexa-]

Hi Apollon,

I can confirm this works now with the `--no-reread` flag set instead of
`--force`.


Thanks alot for taking the time to look into this!


Best Regards,

Martin

On 05/03/2017 03:13 PM, Apollon Oikonomopoulos wrote:
> Hi Martin,
> 
> Apologies for the late response.
> 
> Here's a preliminary root cause analysis:
> 
> On Mon, 30 Jan 2017 13:33:33 +0100 Martin Weinelt  
> wrote:
>> This disk is currently in use - repartitioning is probably a bad idea.
>> Umount all file systems, and swapoff all swap partitions on this disk.
>> Use the --no-reread flag to suppress this check.
>>
>> sfdisk: Use the --force flag to overrule all checks.
>> ```
> 
> In util-linux 2.26, a safeguard was added to sfdisk to try to detect if 
> a disk is in use before partitioning. It does so by issuing the 
> BLKRRPART ioctl, which instructs the kernel to re-read the partition 
> table, which will fail if the disk is currently in use, and this is what 
> sfdisk looks for.
> 
> However, this operation will also fail with -EINVAL in a number of 
> cases, including when devices are declared to the kernel as 
> unpartitionable, i.e. with bdev->minors == 1. And this is how DRBD 
> declares its own devices. IOW, BLKRRPART on DRBD devices will *always* 
> fail, regardless whether the device is in use or not.
> 
>>
>> Adding `--force` to the sfdisk call in 
>> /usr/share/ganeti/os/debootstrap/common.sh:98
>> will allow for completion of the os installation.
>> Adding `--no-reread` didn't change a thing for me.
> 
> In theory, `--no-reread` should work. I tested it manually here, can you 
> please give it a try again? I would prefer to add `--no-reread` rather 
> than `--force`, if the former works.
> 
> Regards,
> Apollon
> 

Bug#860984: marked as done (khal: Please reference debian/patches/0002-Reference-license-from-copyright-file.patch in debian/copyright)

[Debian Bug Tracking System]

Your message dated Wed, 03 May 2017 13:33:26 +
with message-id 
and subject line Bug#860984: fixed in khal 1:0.8.4-4
has caused the Debian Bug report #860984,
regarding khal: Please reference 
debian/patches/0002-Reference-license-from-copyright-file.patch in 
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.)


-- 
860984: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860984
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: khal
Version: 0.9.5-1
Severity: serious
X-Debbugs-CC: Filip Pytloun 

Hi,

I just ACCEPTed khal from NEW but noticed it wasn't 100% obvious
from debian/copyright that the 0002-Reference-license-from-copyright-file.patch
patch existed.

Please update your debian/copyright file, at least to point someone
in the above file's direction. your next upload.


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: khal
Source-Version: 1:0.8.4-4

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

Debian distribution maintenance software
pp.
Filip Pytloun  (supplier of updated khal package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 03 May 2017 14:08:59 +0200
Source: khal
Binary: khal khal-doc
Architecture: source
Version: 1:0.8.4-4
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Filip Pytloun 
Description:
 khal   - Standards based CLI and terminal calendar program
 khal-doc   - Standards based CLI and terminal calendar program - documentation
Closes: 859472 860984
Changes:
 khal (1:0.8.4-4) unstable; urgency=medium
 .
   * Raise epoch to "revert" new upstream version in unstable and pass
 stretch migration
   * d/copyright: mention presence of
 0002-Reference-license-from-copyright-file.patch (Closes: #860984)
   * d/copyright: add upstream contact
   * d/copyright: update copyright year
   * d/patches: some TZ tests may fail due to Debian's python-tz of older
 version but with newer TZ definitions, should be removed when 2017.2
 reaches sid (Closes: #859472)
Checksums-Sha1:
 8ce89b0403c25db749eebff27b322b6c9cfd10e8 2391 khal_0.8.4-4.dsc
 b6dd1252a299979f759a540a79b4dd6eca49ad98 6940 khal_0.8.4-4.debian.tar.xz
 14318c808fdb4e757420da6c935f74f75f3e3e26 7216 khal_0.8.4-4_source.buildinfo
Checksums-Sha256:
 d85a17b498d3dc1c475cbbbe76b89abc84f8bb719edd425044f43bb0e18283e7 2391 
khal_0.8.4-4.dsc
 df2dd79fa54a0c1ed37beef6ad61f4f1117d490018c4263a79ae535f45631719 6940 
khal_0.8.4-4.debian.tar.xz
 ee4620c2f14d09cc4dda7955ed205814f3989fada899afc4280884d0c807f4fd 7216 
khal_0.8.4-4_source.buildinfo
Files:
 da68b4994a165b1636cd6c732ec4715e 2391 utils optional khal_0.8.4-4.dsc
 c76743d657e4d23f1ab101d68f6d9b7b 6940 utils optional khal_0.8.4-4.debian.tar.xz
 a77411858808937cc473356fb9d3cd2e 7216 utils optional 
khal_0.8.4-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEEOAKTsWyox6BpW4soaAgjm5xy5hsFAlkJ2JQRHGZpbGlwQHB5
dGxvdW4uY3oACgkQaAgjm5xy5hvFFQ//bdtDBvHZ60v5JE0OsACj+bUtuupV1gPH
tx9xeWzPAxWr8erHwf7yeiYBVfO81gDXV0Bqs04FMFmt6zIAxXeT8kGC39K5KFNI
xW7CAvJNJP+bvxyvSL5GLhaVopy/eYr1asJQpnQe8lGOfHwP7ElmDJdWQr9ki88d
HE6u6c/X64abH3T7JuexZYwbXdSvtrdq8r7zludQVGWtFh9QQgj4/T5SDrUuFLvr
jC/nu78hGZxvFUDkOrJGxconGEsf3fs0Xns0khqfNmvFNQunAeUDKZdcnzm/vomL
8hZ9VurkJu4+lu7N22V0RrKcuAGDK/mgaW2U66Z3+sVW4W+Q/5znXpH0XS+C5Voc
qeUMjHNuzBq7JFFuVJDtGqXcHFIOdnKrRUHds1MjdXK00Cz61gOTmfHbb6JatUvb
dMqU0BdburrA1hJSL9Q07d+NUa7Irs8D/nsYHbEfc2ts9+zU/OhjzZMlNU/ebTyC
9oRnt0zqnnW1WYC6iNaZ80qeO2PdOJLdzBr6Xds5ShsXdVLKeSkTAGtL3XhWqiPI
ysCuEp4ufFEvo2woiQqS3JAROIsz5t2FDaEx3zgE2smBpw9NKLW4L9+34VcIIzR5
K2CX1e32H6PgR6NDdC+1S+8n/BgV9HqYV9vV1ksM0+JRmsJXuKV3QYhal0nTZq5E
BAzPnObNJ6Y=
=pUsT
-END PGP SIGNATURE End Message ---

Bug#859472: marked as done (khal FTBFS: tests/event_test.py:307: AssertionError)

[Debian Bug Tracking System]

Your message dated Wed, 03 May 2017 13:33:26 +
with message-id 
and subject line Bug#859472: fixed in khal 1:0.8.4-4
has caused the Debian Bug report #859472,
regarding khal FTBFS: tests/event_test.py:307: AssertionError
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.)


-- 
859472: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859472
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: khal
Version: 0.9.4-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=khal&arch=all&ver=0.9.4-1&stamp=1491255368&raw=0

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/«PKGBUILDDIR»'
mkdir -p debian/tmp/locale/
localedef -f UTF-8 -i en_US ./debian/tmp/locale/en_US.UTF-8/
localedef -f UTF-8 -i de_DE ./debian/tmp/locale/de_DE.UTF-8/
localedef -f UTF-8 -i cs_CZ ./debian/tmp/locale/cs_CZ.UTF-8/
localedef -f UTF-8 -i el_GR ./debian/tmp/locale/el_GR.UTF-8/
export LOCPATH=/«PKGBUILDDIR»/debian/tmp/locale/ && \
export LC_ALL=en_US.UTF-8 && \
LC_ALL=en_US.UTF-8 dh_auto_test
I: pybuild base:184: cd /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build; python3.5 
-m pytest tests
= test session starts ==
platform linux -- Python 3.5.3, pytest-3.0.6, py-1.4.32, pluggy-0.4.0
rootdir: /«PKGBUILDDIR», inifile: 
collected 259 items

tests/backend_test.py ..
tests/cal_display_test.py ..s...
tests/cli_test.py 
tests/configwizard_test.py .
tests/controller_test.py 
tests/event_test.py ..F
tests/khalendar_test.py .
tests/khalendar_utils_test.py .s...s..s.
tests/settings_test.py ...
tests/terminal_test.py ...
tests/utils_test.py ..ss...
tests/vdir_test.py x..
tests/vtimezone_test.py ..F
tests/ui/test_calendarwidget.py ..s
tests/ui/test_editor.py .
tests/ui/test_widgets.py .

=== FAILURES ===
__ test_event_no_dst ___

def test_event_no_dst():
"""test the creation of a corect VTIMEZONE for timezones with no dst"""
event_no_dst = _get_text('event_no_dst')
cal_no_dst = _get_text('cal_no_dst')
event = Event.fromString(event_no_dst, calendar='foobar', 
locale=LOCALE_BOGOTA)
>   assert normalize_component(event.raw) == normalize_component(cal_no_dst)
E   assert ('VCALENDAR',...enset())}))})) == ('VCALENDAR', ...enset())}))}))
E At index 2 diff: frozenset({('VTIMEZONE', 
b'BEGIN:VTIMEZONE\r\nTZID:America/Bogota\r\nEND:VTIMEZONE\r\n', 
frozenset({('STANDARD', 
b'BEGIN:STANDARD\r\nDTSTART;VALUE=DATE-TIME:19930403T23\r\nTZNAME:-05\r\nTZOFFSETFROM:-0400\r\nTZOFFSETTO:-0500\r\nEND:STANDARD\r\n',
 frozenset())})), ('VEVENT', b'BEGIN:VEVENT\r\nSUMMARY:An 
Event\r\nDTSTART;TZID=America/Bogota;VALUE=DATE-TIME:20140409T093000\r\nDTEND;TZID=America/Bogota;VALUE=DATE-TIME:20140409T103000\r\nDTSTAMP;VALUE=DATE-TIME:20140401T234817Z\r\nUID:event_no_dst\r\nEND:VEVENT\r\n',
 frozenset())}) != frozenset({('VTIMEZONE', 
b'BEGIN:VTIMEZONE\r\nTZID:America/Bogota\r\nEND:VTIMEZONE\r\n', 
frozenset({('STANDARD', 
b'BEGIN:STANDARD\r\nDTSTART;VALUE=DATE-TIME:19930403T23\r\nTZNAME:COT\r\nTZOFFSETFROM:-0400\r\nTZOFFSETTO:-0500\r\nEND:STANDARD\r\n',
 frozenset())})), ('VEVENT', b'BEGIN:VEVENT\r\nSUMMARY:An 
Event\r\nDTSTART;TZID=America/Bogota;VALUE=DATE-TIME:20140409T093000\r\nDTEND;TZID=America/Bogota;VALUE=DATE-TIME:20140409T103000\r\nDTSTAMP;VALUE=DATE-TIME:20140401T234817Z\r\nUID:event_no_dst\r\nEND:VEVENT\r\n',
 frozenset())})
E Use -v to get the full diff
E Detailed information truncated (-7 more lines), use "-vv" to show

tests/event_test.py:307: AssertionError
_ test_bogota __

def test_bogota():
vbogota = [b'BEGIN:VTIMEZONE',
   b'TZID:America/Bogota',
   b'BEGIN:STANDARD',
   b'DTSTART;VALUE=DATE-TIME:19930403T23',
   b'TZNAME:COT',
   b'TZOFFSETFROM:-0400',
   b'TZOFFSETTO:-0500',
   b'END:STANDARD',
   b'END:VTIMEZONE',
   b'']
>   assert create_timezone(bogota, atime, atime).to_ical().split(b'\r\n') 
> == vbogota
E   assert [b'BEGIN:VTIM...M:-0400', ...] == [b'BEGIN:VTIME...M:-0400', ...]
E At index 4 diff: b'TZNAME:-05'

Bug#853167: ganeti-instance-debootstrap: OS installations fails because sfdisk believes the disk is in use

[Apollon Oikonomopoulos]

Hi Martin,

Apologies for the late response.

Here's a preliminary root cause analysis:

On Mon, 30 Jan 2017 13:33:33 +0100 Martin Weinelt  wrote:
> This disk is currently in use - repartitioning is probably a bad idea.
> Umount all file systems, and swapoff all swap partitions on this disk.
> Use the --no-reread flag to suppress this check.
> 
> sfdisk: Use the --force flag to overrule all checks.
> ```

In util-linux 2.26, a safeguard was added to sfdisk to try to detect if 
a disk is in use before partitioning. It does so by issuing the 
BLKRRPART ioctl, which instructs the kernel to re-read the partition 
table, which will fail if the disk is currently in use, and this is what 
sfdisk looks for.

However, this operation will also fail with -EINVAL in a number of 
cases, including when devices are declared to the kernel as 
unpartitionable, i.e. with bdev->minors == 1. And this is how DRBD 
declares its own devices. IOW, BLKRRPART on DRBD devices will *always* 
fail, regardless whether the device is in use or not.

> 
> Adding `--force` to the sfdisk call in 
> /usr/share/ganeti/os/debootstrap/common.sh:98
> will allow for completion of the os installation.
> Adding `--no-reread` didn't change a thing for me.

In theory, `--no-reread` should work. I tested it manually here, can you 
please give it a try again? I would prefer to add `--no-reread` rather 
than `--force`, if the former works.

Regards,
Apollon

Bug#861748: r-cran-rmpi: Loading library fails

[Ralf Stubner]

Package: r-cran-rmpi
Version: 0.6-6-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

When I try to load the Rmpi library, it fails with an error about a missing
shared object file:

$ LANG=C Rscript -e "library(Rmpi)"
libmpi.so: cannot open shared object file: No such file or directory
Error : .onLoad failed in loadNamespace() for 'Rmpi', details:
  call: fun(libname, pkgname)
  error: Cannot start MPI_Init(). Exit
Error: package or namespace load failed for 'Rmpi'
Execution halted


Any idea what is going on here?

Greetings
Ralf


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

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

Versions of packages r-cran-rmpi depends on:
ii  libc6  2.24-9
ii  libopenmpi22.0.2-2
ii  mpi-default-bin1.8
ii  r-base-core [r-api-3]  3.3.3-1

r-cran-rmpi recommends no packages.

Versions of packages r-cran-rmpi suggests:
pn  r-cran-rsprng  

-- no debconf information

Bug#861747: odil: Incomplete debian/copyright?

[Chris Lamb]

Source: odil
Version: 0.8.0-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Julien Lamy 

Hi,

I just ACCEPTed odil from NEW but noticed it was missing attribution 
in debian/copyright for at least the files © Universite de Strasbourg.

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


Regards,

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

Bug#861746: linux-image-4.9.0-2-amd64: Infinity `soft lockup` at kernel 4.9.0-1+ on HP ProLiant DL360G5

[Arano-kai]

Package: src:linux
Version: 4.9.18-1
Severity: critical
Tags: upstream
Justification: breaks the whole system

Dear Maintainer,
after updating the kernel to `4.9.0-2-amd64` on HP DL360G5, the system hangs up 
with repeating `NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! 
[swapper/0:1]`.
`4.9.0-1-amd64` also affected.
Last working kernel is `4.8.0-2-amd64`

Boot possible only if `acpi=off` provided in kernel opts.

Tried so far:
nolapic (booted with ony one core available)
noapic
acpi_osi=“Linux”
acpi_osi=“Windows 2006”
acpi=ht
pci=noacpi
acpi=noirq
pnpacpi=off
noapic
acpi_osi=“Linux”
acpi_osi=“Windows 2006”
acpi=ht
pci=noacpi
acpi=noirq
pnpacpi=off

Boot log from the serial console is attached.

-- Package-specific info:
** Version:
Linux version 4.9.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 
20170321 (Debian 6.3.0-11) ) #1 SMP Debian 4.9.18-1 (2017-03-30)

** Command line:
BOOT_IMAGE=/root/boot/vmlinuz-4.9.0-2-amd64 
root=UUID=74c84a83-8418-4579-9b0c-44a9298a39aa ro rootflags=subvol=root 
radeon.dpm=1 zswap.enabled=1 zswap.compressor=lz4 zswap.zpool=zbud 
zswap.max_pool_percent=15 acpi=off quiet

** Not tainted

** Kernel log:
[4.875659] ipmi message handler version 39.2
[4.910133] hpilo :01:04.2: PCI->APIC IRQ transform: INT B -> IRQ 22
[4.928771] IPMI System Interface driver.
[4.928811] ipmi_si :01:04.6: probing via PCI
[4.928828] ipmi_si :01:04.6: PCI->APIC IRQ transform: INT A -> IRQ 21
[4.928861] ipmi_si :01:04.6: [mem 0xf7ef-0xf7ef00ff] regsize 1 
spacing 1 irq 21
[4.928862] ipmi_si: Adding PCI-specified kcs state machine
[4.929716] intel_rng: FWH not detected
[4.929746] ipmi_si: probing via SMBIOS
[4.929748] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
[4.929749] ipmi_si: Adding SMBIOS-specified kcs state machine
[4.929752] ipmi_si: Trying PCI-specified kcs state machine at mem address 
0xf7ef, slave address 0x0, irq 21
[4.932683] [drm] radeon kernel modesetting enabled.
[4.956838] CRAT table not found
[4.956841] Finished initializing topology ret=0
[4.956855] kfd kfd: Initialized module
[4.957167] radeon :01:03.0: PCI->APIC IRQ transform: INT A -> IRQ 23
[4.957363] [drm] initializing kernel modesetting (RV100 0x1002:0x515E 
0x103C:0x31FB 0x02).
[4.957381] [drm] register mmio base: 0xF7FF
[4.957382] [drm] register mmio size: 65536
[4.957496] radeon :01:03.0: VRAM: 128M 0xD800 - 
0xDFFF (32M used)
[4.957499] radeon :01:03.0: GTT: 512M 0xB800 - 
0xD7FF
[4.957512] [drm] Detected VRAM RAM=128M, BAR=128M
[4.957513] [drm] RAM width 16bits DDR
[4.957583] [TTM] Zone  kernel: Available graphics memory: 509350 kiB
[4.957584] [TTM] Initializing pool allocator
[4.957591] [TTM] Initializing DMA pool allocator
[4.957621] [drm] radeon: 32M of VRAM memory ready
[4.957623] [drm] radeon: 512M of GTT memory ready.
[4.957640] [drm] GART: num cpu pages 131072, num gpu pages 131072
[4.978717] [drm] PCI GART of 512M enabled (table at 0x3BA8).
[4.978885] radeon :01:03.0: WB disabled
[4.978890] radeon :01:03.0: fence driver on ring 0 use gpu addr 
0xb800 and cpu addr 0x9c093b4e3000
[4.978892] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[4.978893] [drm] Driver supports precise vblank timestamp query.
[4.978917] [drm] radeon: irq initialized.
[4.978939] [drm] Loading R100 Microcode
[4.979594] input: PC Speaker as /devices/platform/pcspkr/input/input5
[4.981521] sr 0:0:0:0: Attached scsi generic sg0 type 5
[5.026313] radeon :01:03.0: firmware: direct-loading firmware 
radeon/R100_cp.bin
[5.026523] [drm] radeon: ring at 0xB8001000
[5.026550] [drm] ring test succeeded in 1 usecs
[5.026687] [drm] ib test succeeded in 0 usecs
[5.027062] [drm] No TV DAC info found in BIOS
[5.027118] [drm] Radeon Display Connectors
[5.027119] [drm] Connector 0:
[5.027120] [drm]   VGA-1
[5.027122] [drm]   DDC: 0x60 0x60 0x60 0x60 0x60 0x60 0x60 0x60
[5.027123] [drm]   Encoders:
[5.027124] [drm] CRT1: INTERNAL_DAC1
[5.027125] [drm] Connector 1:
[5.027126] [drm]   VGA-2
[5.027127] [drm]   DDC: 0x6c 0x6c 0x6c 0x6c 0x6c 0x6c 0x6c 0x6c
[5.027128] [drm]   Encoders:
[5.027129] [drm] CRT2: INTERNAL_DAC2
[5.093779] [drm] fb mappable at 0xD804
[5.093781] [drm] vram apper at 0xD800
[5.093782] [drm] size 786432
[5.093783] [drm] fb depth is 8
[5.093784] [drm]pitch is 1024
[5.093992] fbcon: radeondrmfb (fb0) is primary device
[5.253797] Console: switching to colour frame buffer device 128x48
[5.261376] radeon :01:03.0: fb0: radeondrmfb frame buffer device
[5.276027] [drm] Initialized radeon 2.48.0 20080528 for :01:03.0 on 
minor 0
[5.357185] iTCO_vendor_support: vendor-support=0
[5.406046] iTC

Processed: your mail

[Debian Bug Tracking System]

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

> tag 861152 + pending
Bug #861152 {Done: Moritz Schlarb } [nagstamon] 
nagstamon: InsecureRequestWarning: Unverified HTTPS request is being made.
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#861744: torbrowser-launcher: Should not be part of Stretch

[u]

Package: torbrowser-launcher
Severity: serious

I'm opening this RC bug in order to prevent torbrowser-launcher from
migrating to testing.

Currently, the design of the software makes the package very often
unusable, as soon as TorBrowser upstream gets signed with a different
OpenPGP key or the SSL certificate of the server changes. This is not
reliable and normal users will be unable to workaround these issues
themselves.

It'll be easier and safer to provide up-to-date versions to users using
stable-backports. This shall be documented on the Debian wiki.

Cheers!
u.



signature.asc
Description: OpenPGP digital signature

Bug#861152: Bug#861725: unblock: nagstamon/2.0.1-4

[Julien Cristau]

On 05/03/2017 12:49 PM, Paul Wise wrote:
> On Wed, 2017-05-03 at 12:24 +0200, Moritz Schlarb wrote:
> 
>> - This has been the behavior of the Nagstamon package since forever
>> (which is not a valid argumentation point - I know, but it's still a fact)
> 
> There are two serious bugs here:
> 
> 1) that certificates are not verified at least using CAs and or TOFU
> 
> 2) that this fact was deliberately hidden from users
> 
So FWIW I'm not sure I agree about the severity of either of those
things.  My opinion is that hiding the warning is a regression compared
to showing them, so I'd rather we didn't do that in stretch right now.

>> What do you think?
> 
> I think we should enable the warnings in all suites.
> 
> Once verification is available, backport the patch to all suites.
> 
And I disagree that changing the behaviour in a stable release is
appropriate.

Cheers,
Julien

Processed: severity of 853167 is serious

[Debian Bug Tracking System]

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

> severity 853167 serious
Bug #853167 [ganeti-instance-debootstrap] ganeti-instance-debootstrap: OS 
installations fails because sfdisk believes the disk is in use
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#861121: version in jessie-backports still vulnerable

[Emmanuel Bouthenot]

Eivind,

On Mon, May 01, 2017 at 11:17:17AM +0200, Eivind Uggedal wrote:
> Weechat version 1.5-1~bpo8+10 in jessie-backports is still vulnerable
> to CVE-2017-8073.
> 
> The same for 1.0.1-1~bpo70+1 in weezy-backports.

Both were uploaded a few hours ago.

Regards,

-- 
Emmanuel Bouthenot
  mail: kolter@{openics,debian}.orggpg: 4096R/0x929D42C3
  xmpp: kol...@im.openics.org  irc: kolter@{freenode,oftc}

Bug#861645: gsequencer FTBFS on mips/mipsel: FAIL: ags_xorg_application_context_test

[Joël Krähemann]

Hi

I just tried to run `make check` in a mipsel chroot on tty2.

As running ./ags_xorg_application_context_test I get:

Suite: AgsXorgApplicationContextTest
  Test: test of AgsXorgApplicationContext doing dispose ...Unsupported
ioctl: cmd=0x41785501
Unsupported ioctl: cmd=0x41785501
** Message: Can't get the next card number: Success
Unsupported ioctl: cmd=0x41785501
Unsupported ioctl: cmd=0x41785501
** Message: Can't get the next card number: Success
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Segmentation fault

Might be some output was discarded. Escpecially
Unsupported ioctl: cmd=...

Bests,
Joël

On Tue, May 2, 2017 at 6:53 PM, Joël Krähemann  wrote:
> Hi
>
> I have experienced on some other architectures with
> ags_xorg_application_context_test
> the same problems. It was not evident to me if the problem was related
> to Gtk+-2.0 or
> xvfb-run since the stack-trace ended as doing gtk_widget_show(window);
>
> However other architectures just pass the test. Now, I'm going to set
> up a VM to get a
> meaningful stack-trace.
>
> Bests,
> Joël
>
>
> On Tue, May 2, 2017 at 10:05 AM, Adrian Bunk  wrote:
>> Source: gsequencer
>> Version: 0.8.0-1
>> Severity: serious
>>
>> https://buildd.debian.org/status/package.php?p=gsequencer&suite=sid
>>
>> ...
>> make  check-TESTS
>> make[3]: Entering directory '/«PKGBUILDDIR»'
>> make[4]: Entering directory '/«PKGBUILDDIR»'
>> PASS: ags_thread_test
>> PASS: ags_audio_application_context_test
>> PASS: ags_turtle_test
>> PASS: ags_devout_test
>> PASS: ags_channel_test
>> PASS: ags_audio_test
>> PASS: ags_audio_signal_test
>> PASS: ags_recall_test
>> PASS: ags_port_test
>> PASS: ags_recycling_test
>> PASS: ags_pattern_test
>> PASS: ags_notation_test
>> PASS: ags_automation_test
>> PASS: ags_midi_buffer_util_test
>> PASS: ags_midi_builder_test
>> ./test-driver: line 107:  7386 Segmentation fault  "$@" > $log_file 2>&1
>> FAIL: ags_xorg_application_context_test
>> 
>>gsequencer 0.8.0: ./test-suite.log
>> 
>>
>> # TOTAL: 16
>> # PASS:  15
>> # SKIP:  0
>> # XFAIL: 0
>> # FAIL:  1
>> # XPASS: 0
>> # ERROR: 0
>>
>> .. contents:: :depth: 2
>>
>> FAIL: ags_xorg_application_context_test
>> ===
>>
>>
>>
>>  CUnit - A unit testing framework for C - Version 2.1-3
>>  http://cunit.sourceforge.net/
>>
>> ** Message: loading preferences from data[0x55df8774]
>> ** Message: autosave-thread
>> ** Message: false
>> ** Message: simple-file
>> ** Message: true
>> ** Message: disable-feature
>> ** Message: experimental
>> ** Message: segmentation
>> ** Message: 4/4
>> ** Message: model
>> ** Message: super-threaded
>> ** Message: super-threaded-scope
>> ** Message: channel
>> ** Message: lock-global
>> ** Message: ags-thread
>> ** Message: lock-parent
>> ** Message: ags-recycling-thread
>> ** Message: backend
>> ** Message: alsa
>> ** Message: device
>> ** Message: hw:0,0
>> ** Message: samplerate
>> ** Message: 44100
>> ** Message: buffer-size
>> ** Message: 1024
>> ** Message: pcm-channels
>> ** Message: 2
>> ** Message: dsp-channels
>> ** Message: 2
>> ** Message: format
>> ** Message: 16
>> ** Message: backend
>> ** Message: alsa
>> ** Message: device
>> ** Message: hw:0,0
>> ** Message: samplerate
>> ** Message: 44100
>> ** Message: buffer-size
>> ** Message: 1024
>> ** Message: pcm-channels
>> ** Message: 2
>> ** Message: dsp-channels
>> ** Message: 2
>> ** Message: format
>> ** Message: 16
>> ** Message: auto-sense
>> ** Message: true
>>
>> Suite: AgsXorgApplicationContextTest
>>   Test: test of AgsXorgApplicationContext doing dispose ...** Message: Can't 
>> get the next card number: Success
>> ** Message: Can't get the next card number: Success
>> FAIL ags_xorg_application_context_test (exit status: 139)
>>
>> 
>> Testsuite summary for gsequencer 0.8.0
>> 
>> # TOTAL: 16
>> # PASS:  15
>> # SKIP:  0
>> # XFAIL: 0
>> # FAIL:  1
>> # XPASS: 0
>> # ERROR: 0
>> 
>> See ./test-suite.log
>> Please report to jkraehemann-gu...@users.alioth.debian.org
>> 
>> Makefile:9817: recipe for target 'test-suite.log' failed
>> make[4]: *** [test-suite.log] Error 1
>> ___
>> pkg-multimedia-maintainers mailing list
>> pkg-multimedia-maintain...@lists.alioth.debian.org
>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#861486: [Pkg-julia-devel] Bug#861486: Bug#861486: Bug#861486: julia: FTBFS on mips64el (segmentation fault)

[Aurelien Jarno]

On 2017-05-02 23:30, Graham Inggs wrote:
> On 2 May 2017 at 18:58, Peter Colberg  wrote:
> > Could you comment all lines and then successively uncomment to see
> > which line triggers the segfault?
> 
> I commented out practically your entire program and it still randomly 
> segfaults.
> 
> > You could also try querying a symbol in libm other than pow and see
> > whether that changes anything.
> 
> No difference with 'exp' or 'SuiteSparse_config'.  I also tried
> replacing -lopenlibm with -lm.
> 
> I am able to reproduce the problem with the files below.  Julia's
> build-dependencies are still required, but not Julia's source.
> 
> 
> Contents of shlibdeps.c:
> int main(void)
> {
>   return 0;
> }
> 
> 
> Contents of Makefile:
> SHLIBDEPS+=-larpack
> SHLIBDEPS+=-lopenblas
> SHLIBDEPS+=-ldSFMT
> SHLIBDEPS+=-lfftw3_threads
> SHLIBDEPS+=-lfftw3f_threads
> SHLIBDEPS+=-lgmp
> SHLIBDEPS+=-lopenlibm
> SHLIBDEPS+=-lmpfr
> SHLIBDEPS+=-lopenspecfun
> SHLIBDEPS+=-lpcre2-8
> SHLIBDEPS+=-lcholmod
> SHLIBDEPS+=-lspqr
> SHLIBDEPS+=-lsuitesparseconfig
> SHLIBDEPS+=-lumfpack
> 
> shlibdeps: shlibdeps.c
> gcc -o shlibdeps shlibdeps.c -ldl $(SHLIBDEPS)
> 
> test: shlibdeps
> for n in $(shell seq 1 30); do ./shlibdeps; done
> 
> 
> $ make test
> for n in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
> 24 25 26 27 28 29 30; do ./shlibdeps; done
> Segmentation fault
> Segmentation fault
> Segmentation fault
> Segmentation fault

The problem only happens when using multiple OpenMP threads, it can be
workarounded by setting OMP_NUM_THREADS=1. The crash happens in
blas_memory_free:

  #0  0x00fff22043e4 in blas_memory_free 
(free_area=free_area@entry=0xffed415000) at memory.c:1161
  #1  0x00fff2204ee4 in blas_thread_server (arg=) at 
blas_server.c:461
  #2  0x00fff112f008 in start_thread () from 
/lib/mips64el-linux-gnuabi64/libpthread.so.0

Note that openblas provides a different blas_thread_server in
blas_server_omp.c when OpenMP is in use. I *guess* therefore that either
openblas should be built with OpenMP support or that suitesparse should
not use OpenMP.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#861152: Bug#861725: unblock: nagstamon/2.0.1-4

[Paul Wise]

On Wed, 2017-05-03 at 12:24 +0200, Moritz Schlarb wrote:

> - This has been the behavior of the Nagstamon package since forever
> (which is not a valid argumentation point - I know, but it's still a fact)

There are two serious bugs here:

1) that certificates are not verified at least using CAs and or TOFU

2) that this fact was deliberately hidden from users

> What do you think?

I think we should enable the warnings in all suites.

Once verification is available, backport the patch to all suites.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#861736: python-nxs: Cannot save files with nxs python module

[Marc Rosanes]

Package: python-nxs
Version: 4.3.2-svn1921-4
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

   Run the following python code:

   import nxs
   e = nxs.NXentry(name= "NXtomo")
   e.save("filenamenxs.h5", 'w5')


   * What was the outcome of this action?

   Got the following exception:

NeXusError
Traceback (most recent call last)
 in ()
> 1 e.save("filenamenxs.h5", 'w5')

/usr/lib/python2.7/dist-packages/nxs/tree.pyc in save(self, filename, 
format)

866 root = NXroot(NXentry(self))
867 if root.nxfile: root.nxfile.close()
--> 868 file = NeXusTree(filename, format)
869 file.writefile(root)
870 file.close()

/usr/lib/python2.7/dist-packages/nxs/napi.pyc in __init__(self, 
filename, mode)

318 else:
319 op = 'create'
--> 320 raise NeXusError, "Could not %s %s"%(op,filename)
321 self.isopen = True
322


   * What outcome did you expect instead?

An hdf5 file filenamenxs.h5 saved with no exception.

Note: Tried this with debian:stable docker and it worked correctly.


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

Kernel: Linux 4.9.0-1-amd64 (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/bash
Init: systemd (via /run/systemd/system)

Versions of packages python-nxs depends on:
ii  libnexus0v5  4.3.2-svn1921-4+b1
pn  python:any   

python-nxs recommends no packages.

python-nxs suggests no packages.

-- no debconf information

Bug#861152: Bug#861725: unblock: nagstamon/2.0.1-4

[Moritz Schlarb]

Hi Julien, hi Paul,

On 03.05.2017 11:51, Julien Cristau wrote:
> I don't see how not checking certificates is in any way a reasonable
> thing to do.  Silencing warnings about it makes it even worse.

Absolutely true - but:

- This has been the behavior of the Nagstamon package since forever
(which is not a valid argumentation point - I know, but it's still a fact)
- It is actually the intended behavior by the upstream developer (until
https://github.com/HenriWahl/Nagstamon/issues/302 gets resolved) - the
added patch just actually makes the disabling of warnings work (which
worked before in jessie but not anymore in stretch)
- We anticipated the concerns regarding not checking certificates and
wrote a paragraph in README.debian about our rationale for accepting
that with regards to the primary type of user of such monitoring software

On 03.05.2017 11:32, Paul Wise wrote:
> I don't think the warnings should be disabled,
> I think that the certificates should be verified.
> Why are the warnings being disabled?

Because upstream chose to do so - I want to stress again that my patch
just fixes the code to actually do what upstream wanted it to do.

Now whether these warnings are disabled or not isn't the real problem
here - that should be clear.
But it was because of these warnings (which, again, do not come from a
change in behavior but just in reporting it), that Paul reported #861152
and tagged it as release critical which lead to the package being put in
the removal queue...

If you'd like, we can explicitly re-enable the warnings so the behavior
is visible to the users.
But I don't want to have nagstamon removed simply because of that...

What do you think?

Regards,
-- 
Moritz Schlarb
Unix-Gruppe | Systembetreuung
Zentrum für Datenverarbeitung
Johannes Gutenberg-Universität Mainz
Raum 01-321 - Tel. +49 6131 39-29441
OpenPGP Fingerprint: DF01 2247 BFC6
5501 AFF2 8445 0C24 B841 C7DD BAAF
<>

signature.asc
Description: OpenPGP digital signature

Bug#856592: in libpodofo marked as pending

[Mattia Rizzolo]

Control: tag 856592 pending

Hello,

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

https://anonscm.debian.org/git/collab-maint/libpodofo.git/commit/?id=14c34ec

(this message was generated automatically based on the git commit message)
---
commit 14c34ec02223c7689f504b2428acf1170450e1a3
Author: Mattia Rizzolo 
Date:   Wed May 3 10:36:55 2017 +0200

Add upstream patch for CVE-2017-5853 and CVE-2017-6844

Closes: #854601, #856592
Signed-off-by: Mattia Rizzolo 

Processed: Bug#856592 in libpodofo marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag 856592 pending
Bug #856592 {Done: Mattia Rizzolo } [src:libpodofo] Multiple 
security issues
Added tag(s) pending.

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

Processed: your mail

[Debian Bug Tracking System]

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

> retitle 861563 libpodofo: CVE-2017-6846
Bug #861563 [src:libpodofo] libpodofo: CVE-2017-6845
Changed Bug title to 'libpodofo: CVE-2017-6846' from 'libpodofo: CVE-2017-6845'.
> close 861561 0.9.4-5
Bug #861561 [src:libpodofo] libpodofo: CVE-2017-6844
The source 'libpodofo' and version '0.9.4-5' do not appear to match any binary 
packages
Marked as fixed in versions libpodofo/0.9.4-5.
Bug #861561 [src:libpodofo] libpodofo: CVE-2017-6844
Marked Bug as done
> --
Stopping processing here.

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

Bug#861561: in libpodofo marked as pending

[Mattia Rizzolo]

Control: tag 861561 pending

Hello,

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

https://anonscm.debian.org/git/collab-maint/libpodofo.git/commit/?id=aeabade

(this message was generated automatically based on the debian/changelog diff)
---
commit aeabadeea10d183f0e740524a9d74a82ed8b19ba
Author: Mattia Rizzolo 
Date:   Wed May 3 12:12:14 2017 +0200

Correct bug references

Signed-off-by: Mattia Rizzolo 

Processed: Bug#861561 in libpodofo marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag 861561 pending
Bug #861561 [src:libpodofo] libpodofo: CVE-2017-6844
Added tag(s) pending.

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

Bug#856592: marked as done (Multiple security issues)

[Debian Bug Tracking System]

Your message dated Wed, 03 May 2017 10:03:30 +
with message-id 
and subject line Bug#856592: fixed in libpodofo 0.9.4-5
has caused the Debian Bug report #856592,
regarding Multiple security issues
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.)


-- 
856592: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856592
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libpodofo
Severity: grave
Tags: security

New podofo issues (no CVEs yet):

http://www.openwall.com/lists/oss-security/2017/03/02/10
http://www.openwall.com/lists/oss-security/2017/03/02/9
http://www.openwall.com/lists/oss-security/2017/03/02/8
http://www.openwall.com/lists/oss-security/2017/03/02/7
http://www.openwall.com/lists/oss-security/2017/03/02/6
http://www.openwall.com/lists/oss-security/2017/03/02/5
http://www.openwall.com/lists/oss-security/2017/03/02/4
http://www.openwall.com/lists/oss-security/2017/03/02/3
http://www.openwall.com/lists/oss-security/2017/03/02/2

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: libpodofo
Source-Version: 0.9.4-5

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

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

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated libpodofo package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 03 May 2017 11:41:19 +0200
Source: libpodofo
Binary: libpodofo-dev libpodofo-utils libpodofo0.9.4
Architecture: source
Version: 0.9.4-5
Distribution: unstable
Urgency: high
Maintainer: Mattia Rizzolo 
Changed-By: Mattia Rizzolo 
Description:
 libpodofo-dev - PoDoFo development files
 libpodofo-utils - PoDoFo utilities
 libpodofo0.9.4 - PoDoFo - library to work with the PDF file format
Closes: 854601 854602 854604 856592 859331
Changes:
 libpodofo (0.9.4-5) unstable; urgency=high
 .
   * Add upstream patch for security issues:
 + CVE-2017-5853 Closes: #854601
 + CVE-2017-6844 Closes: #856592
 + CVE-2017-5854 Closes: #854602
 + CVE-2017-5886 Closes: #854604
 + CVE-2017-7379 Closes: #859331
Checksums-Sha1:
 efa896f42140fd0ac2e5cc36014a339cab5dad29 2119 libpodofo_0.9.4-5.dsc
 6238655d640b0738601fd4f35fafd4f39d4ae60a 13308 libpodofo_0.9.4-5.debian.tar.xz
 c0a2be46333e68a33bb4ccf60639480aadca9d9d 8325 libpodofo_0.9.4-5_amd64.buildinfo
Checksums-Sha256:
 60de0684a1a38fff67e1c49bf49f55aec41167eb2cb5c3a4034cc4de063944ef 2119 
libpodofo_0.9.4-5.dsc
 fc150e0534bf808588350c8c6d82bec033481a7039dfbd28742033cc8eddc455 13308 
libpodofo_0.9.4-5.debian.tar.xz
 14ded71340b21dad144d906c0d58e34f7e6416de7abc2c913195fbb099614f08 8325 
libpodofo_0.9.4-5_amd64.buildinfo
Files:
 7f3a7c904e54eeb655044c8adb56d902 2119 libdevel extra libpodofo_0.9.4-5.dsc
 a8a35d56d295eab92b7356bfcc378ea7 13308 libdevel extra 
libpodofo_0.9.4-5.debian.tar.xz
 742c1b148d7356cc3c18eeb9f1fd6f4d 8325 libdevel extra 
libpodofo_0.9.4-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAlkJpsgACgkQCBa54Yx2
K628GQ//dXA9Zo8CS2DoRRBRc3awfFH5WhMiU5urTB3fBWnpmSk28gSS7znHhAZQ
C5QJl9CSK2AHuU2lnYiIilCzWeJZD9gA5VOKNHqiSUnKUDrvgM/xIr3OHoXcl4ti
t5oEODgxFnSu1W5WEwR8ocSbC6oEt50CSGpa2ZFFSWYCGOxeiGjZblwvlsR1Fgh/
s/Yx4wUJ8HXjHhV9BuXlvh733QJ4SLuS0AR/gjykxQo1LdgcenP1VbrQANrvr/b1
mJMFwOhbc6DHdZ9KZbNuN+DZwAPUW1mpg6hJoj1HbfjHr0HV0pu2xHJxs41YIDwM
k5Ir5E/cq5H3tj/cqfW9VMedu4fPBYLqYtR+UDfSv1FJwuFZAhEq6RPaaXbeyRRg
GNRrkH6DCrKgebixct6MxcWXnN32BaSmaUg+HOgAQ06ei9z2YwB03CiSEL3mK0Dd
HX4XjBHZ3V/OUkOv9KlMYpyWwaVoM6E8TdCZZR4Zd5BHVnAQt7YbsQtGgaT5ZVdc
mR1hHvEPaYfaFjGgX/ifObeTsGwTu22IO/7ywIRHDh6j/OIjGoMlqTAechzqo20f
CeI/ksJMNJjD9LDrd9LoV2dLx1kbpurBfbTaz4aNKxH0zl1yK/Tk+4m7OgCt0RrW
e1i4KO/XOiM8cIpQtOqJjG/jNKnZGxCLKKZV8JuV9JNSiDCTThk=
=DN+/
-END PGP SIGNATURE End Message ---

Bug#851120: marked as done (gdm3 does not start on fresh stretch install in vbox)

[Debian Bug Tracking System]

Your message dated Wed, 03 May 2017 10:04:05 +
with message-id 
and subject line Bug#861683: fixed in xorg 1:7.7+19
has caused the Debian Bug report #861683,
regarding gdm3 does not start on fresh stretch install in vbox
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.)


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

Version: 3.22.1-1

Severity: serious


I installed stretch using the 2017-01-12 netinst installer ISO (in a
VirtualBox VM) and then I installed gnome with


  apt-get install gnome


The desktop fails to appear, the console just flickers continuously.

I logged in over ssh and tried various things.  Eventually I tried


   apt-get install xserver-xorg-legacy


and now it runs and I see the GNOME login screen.

The same problem/solution was observed by another user in this discussion:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801749#25

although that bug report appears to be discussing various gdm3 startup
issues so I'm opening this new bug report to focus on this specific issue.
--- End Message ---
--- Begin Message ---
Source: xorg
Source-Version: 1:7.7+19

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

Debian distribution maintenance software
pp.
Julien Cristau  (supplier of updated xorg package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 03 May 2017 11:38:16 +0200
Source: xorg
Binary: x11-common xserver-xorg xserver-xorg-video-all xserver-xorg-input-all 
xorg xorg-dev xbase-clients xutils
Architecture: source
Version: 1:7.7+19
Distribution: unstable
Urgency: high
Maintainer: Debian X Strike Force 
Changed-By: Julien Cristau 
Description:
 x11-common - X Window System (X.Org) infrastructure
 xbase-clients - miscellaneous X clients - metapackage
 xorg   - X.Org X Window System
 xorg-dev   - X.Org X Window System development libraries
 xserver-xorg - X.Org X server
 xserver-xorg-input-all - X.Org X server -- input driver metapackage
 xserver-xorg-video-all - X.Org X server -- output driver metapackage
 xutils - X Window System utility programs metapackage
Closes: 861683
Changes:
 xorg (1:7.7+19) unstable; urgency=high
 .
   * Team upload.
   * xserver-xorg now Recommends xserver-xorg-legacy, we'd have liked to avoid
 installing the setuid Xorg wrapper by default in stretch, but this seems
 to break too much still (closes: #861683).
Checksums-Sha1:
 ec5bca09ebb9d9317d5548727086cddebdfb6a9b 2016 xorg_7.7+19.dsc
 3cd557012a7158b4efb22c14ab7ee5c5e875c340 288723 xorg_7.7+19.tar.gz
 a14ebda764dee649a8d90cfc0e518c4ef3d21e18 5275 xorg_7.7+19_source.buildinfo
Checksums-Sha256:
 fc4a577eee67f3604c56701e21b28dccd3858da0f110b708ca3359e2718e3d46 2016 
xorg_7.7+19.dsc
 5de6df9e19009450b94f4f5307049bc2c7dc1114222f6f2f6fc60d737a33a537 288723 
xorg_7.7+19.tar.gz
 7c3812d4005a32e9e64670c742b66b53a9056a58c0bf29e212d2d9a3a62c395a 5275 
xorg_7.7+19_source.buildinfo
Files:
 e3ca6e310764cdf81cdcc2839cc0be38 2016 x11 optional xorg_7.7+19.dsc
 ad1a54c4e258f4baf5b89f2f5ab6a593 288723 x11 optional xorg_7.7+19.tar.gz
 2c3c2becc4a80566ddc2d3a051505eae 5275 x11 optional xorg_7.7+19_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEVXgdqzTmGgnvuIvhnbAjVVb4z60FAlkJpaoUHGpjcmlzdGF1
QGRlYmlhbi5vcmcACgkQnbAjVVb4z60znw//VIympp3FMgrcCPhk8pp3emLnl71n
4KVQW2/3NO1WaiwZbYnzwNiPfeA0j+yaWj2DEoTJEv5jktg/9W7Rgkbw87gJnI7q
+rKPIDNJg7tnKmvnf1rCW69u6CT6Qfn1GX8ctmpUsUCCDMZXhaq6UzfSBe5yYovZ
qel012DaToVyv2Q0fCEy/HZUmWnMdeytgZXJWmVHn1NRMH/lOJmRkyygB/0h0niR
DtsJcdCSz9XN7LrMaD7JG7X20LPU4ax228/SMRF6YJNS2GclXt5E5g2piLbXsCob
GwH64L09Da0myU8VbWPJ5tJJuI44MSCF2YApQkoIFT4qScVyh4xpoXzbM8bS6/DN
6u0fUoX88DreRFcDX//RQVAMfgClsJ1HbnLY5eEsHaHNKFXChP7qcXK7W3GNKSgs
zE+DgKnurR/lu+Qz5KRFWfazHtMPeBCOG+mQjhqDK4XrmoURDLwy2CHv6scA5SyD
kjpyfwsi4cwnyhn1Z98nU9FpI/rqWpCtxpWzv68h4YaGS0U19fIHxcWQPo3zokmI
7l6W+Gi73sEK9fZ/GhGEAEug11J5IgKq0RiGCcAWD8AzB4vKciciqQDszYZQT56P
bz+JsKgmRB42VLKiDf2cVwk28peln9Oy93NZnqYXz+OzC/6zI+kYiXjLyt54oq3C
cBXCYUslhKmCMKk=
=YXaU

Bug#861683: marked as done (Install xserver-xorg-legacy by default for stretch)

[Debian Bug Tracking System]

Your message dated Wed, 03 May 2017 10:04:05 +
with message-id 
and subject line Bug#861683: fixed in xorg 1:7.7+19
has caused the Debian Bug report #861683,
regarding Install xserver-xorg-legacy by default for stretch
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.)


-- 
861683: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861683
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xorg
Version: 1:7.7+18
Severity: serious

With virtualbox-dkms gone for stretch, trying to install GNOME inside
Virtualbox will lead to gdm failing to start, as it tries to run Xorg as
unprivileged user. This requires a KMS compatible driver though.
Same is true for users of startx. They need the suid wrapper provided by
xserver-xorg-legacy in such a case.

Not having the Xorg.wrap suid wrapper is a worthwile goal, but I guess
we are not quite there yet, as there are still to many popular cases
where it's needed.

I would thus like to see xserver-xorg-legacy added as a Recommends to
one of the xorg packages.

This means it would be installed on upgrades and new installations but
users with a KMS compatible driver can uninstall it.




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

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

Versions of packages xserver-xorg depends on:
ii  x11-xkb-utils7.7+3+b1
ii  xkb-data 2.19-1
ii  xserver-xorg-core2:1.19.3-1
ii  xserver-xorg-input-all   1:7.7+18
ii  xserver-xorg-input-evdev [xorg-driver-input] 1:2.10.5-1
ii  xserver-xorg-input-libinput [xorg-driver-input]  0.23.0-2
ii  xserver-xorg-input-wacom [xorg-driver-input] 0.34.0-1
ii  xserver-xorg-video-all   1:7.7+18
ii  xserver-xorg-video-amdgpu [xorg-driver-video]1.2.0-1+b1
ii  xserver-xorg-video-ati [xorg-driver-video]   1:7.8.0-1+b1
ii  xserver-xorg-video-fbdev [xorg-driver-video] 1:0.4.4-1+b5
ii  xserver-xorg-video-nouveau [xorg-driver-video]   1:1.0.13-3
ii  xserver-xorg-video-radeon [xorg-driver-video]1:7.8.0-1+b1
ii  xserver-xorg-video-vesa [xorg-driver-video]  1:2.3.4-1+b2
ii  xserver-xorg-video-vmware [xorg-driver-video]1:13.2.1-1+b1

Versions of packages xserver-xorg recommends:
ii  libgl1-mesa-dri  13.0.6-1+b2

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: xorg
Source-Version: 1:7.7+19

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

Debian distribution maintenance software
pp.
Julien Cristau  (supplier of updated xorg package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 03 May 2017 11:38:16 +0200
Source: xorg
Binary: x11-common xserver-xorg xserver-xorg-video-all xserver-xorg-input-all 
xorg xorg-dev xbase-clients xutils
Architecture: source
Version: 1:7.7+19
Distribution: unstable
Urgency: high
Maintainer: Debian X Strike Force 
Changed-By: Julien Cristau 
Description:
 x11-common - X Window System (X.Org) infrastructure
 xbase-clients - miscellaneous X clients - metapackage
 xorg   - X.Org X Window System
 xorg-dev   - X.Org X Window System development libraries
 xserver-xorg - X.Org X server
 xserver-xorg-input-all - X.Org X server -- input driver metapackage
 xserver-xorg-video-all - X.Org X server -- output driver metapackage
 xutils - X Window System utility programs metapackage
Closes: 861683
Changes:
 xorg (1:7.7+19) unstable; urgency=high
 .
   * Team upload.
   * xserver-xorg now Recommends xserver-xorg-legacy, we'd have liked to avoid
 installing the setuid Xorg wrapper by default in stretch, but this seems
 to break too much still (closes: #861683).
Checksums-Sha1:
 ec5bca09ebb9d9317d5548727

Bug#861152: closed by Moritz Schlarb (Bug#861152: fixed in nagstamon 2.0.1-4)

[Paul Wise]

On Wed, 2017-05-03 at 09:18 +, Debian Bug Tracking System wrote:

>    * Fix code for disabling InsecureRequestWarning warnings
>  Closes: #861152

I don't think the warnings should be disabled,
I think that the certificates should be verified.
Why are the warnings being disabled?

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#861152: marked as done (nagstamon: InsecureRequestWarning: Unverified HTTPS request is being made.)

[Debian Bug Tracking System]

Your message dated Wed, 03 May 2017 09:14:16 +
with message-id 
and subject line Bug#861152: fixed in nagstamon 2.0.1-4
has caused the Debian Bug report #861152,
regarding nagstamon: InsecureRequestWarning: Unverified HTTPS request is being 
made.
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.)


-- 
861152: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861152
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nagstamon
Version: 2.0.1-1
Severity: serious
Tags: security

When I run nagstamon from a terminal against the Debian nagios I get a
warning about unverified and thus insecure HTTPS requests being made:

https://nagios.debian.org/icinga/
https://dsa.debian.org/ (see here for guest login)

$ nagstamon 
...
/usr/lib/python3/dist-packages/urllib3/connectionpool.py:845: 
InsecureRequestWarning: Unverified HTTPS request is being made. Adding 
certificate verification is strongly advised. See: 
https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
  InsecureRequestWarning)

-- System Information:
Debian Release: 9.0
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (860, 
'testing-proposed-updates'), (800, 'unstable-debug'), (800, 'unstable'), (790, 
'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 
'buildd-experimental')
Architecture: amd64
 (x86_64)

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

Versions of packages nagstamon depends on:
ii  libqt5multimedia5-plugins5.7.1~20161021-2
ii  python3-bs4  4.5.3-1
ii  python3-dbus.mainloop.pyqt5  5.7+dfsg-5
ii  python3-pkg-resources33.1.1-1
ii  python3-psutil   5.0.1-1
ii  python3-pyqt55.7+dfsg-5
ii  python3-pyqt5.qtmultimedia   5.7+dfsg-5
ii  python3-pyqt5.qtsvg  5.7+dfsg-5
ii  python3-requests 2.12.4-1
pn  python3:any  

nagstamon recommends no packages.

nagstamon suggests no packages.

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: nagstamon
Source-Version: 2.0.1-4

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

Debian distribution maintenance software
pp.
Moritz Schlarb  (supplier of updated nagstamon 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: Fri, 28 Apr 2017 21:16:17 +0200
Source: nagstamon
Binary: nagstamon
Architecture: source
Version: 2.0.1-4
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Moritz Schlarb 
Description:
 nagstamon  - Nagios status monitor which takes place in systray or on desktop
Closes: 774002 861152
Changes:
 nagstamon (2.0.1-4) unstable; urgency=medium
 .
   * Add Recommends for python3-secretstorage to debian/control
 Closes: #774002
   * Fix code for disabling InsecureRequestWarning warnings
 Closes: #861152
Checksums-Sha1:
 25d0b7421463ba6a8bcf188fc3d5a1ebc7f26c68 2025 nagstamon_2.0.1-4.dsc
 1a39e1db514304a522413aa118fe3d1542a58035 7340 nagstamon_2.0.1-4.debian.tar.xz
Checksums-Sha256:
 5a6ab345fbf523c5eb5377bac6de805b982c54ca53144c7dd402e98838878a7f 2025 
nagstamon_2.0.1-4.dsc
 79ccb11ec88ebf9395efda2815e455e49516202f93f189418f9dcea1145742e0 7340 
nagstamon_2.0.1-4.debian.tar.xz
Files:
 c506d19b5c8a6b4401ef4d2c638c47ab 2025 utils optional nagstamon_2.0.1-4.dsc
 037891fc300d3eaca484555088562335 7340 utils optional 
nagstamon_2.0.1-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJZCYeLAAoJEPqBswqWsQmcyfYP/1gEtX7qC9BUJoiSkFjmRHzL
CjmWmNwseDHzEqUPTsFWJYy1n4cis2zxLWLJjbv9+QdXWUUA2EngGWwbER9QuisJ
/S2cRtdqk1B7oiNomz+VuRAcD1fksKhi3IAo7VA4Yfu9q8YPzwhSa5Apq5s57It8
nWATkYNiL9vh3CRXZdp72Qq0vdDo1g4k+EkwQXtUlFWFUu+iWoZuSHJcCCRvUxiT
dffHNyDeG6WFW5FsassaeK+RiDuRVP+1VKDmkd8hCbRQ0tgoiESULo8ogcw9rNPD
zUEF9V

Bug#827122: marked as done (liboasis3-0d: libpsmile.so is a broken symbolic link to libpsmile.MPI1.so.0d)

[Debian Bug Tracking System]

Your message dated Wed, 03 May 2017 09:14:28 +
with message-id 
and subject line Bug#827122: fixed in oasis3 3.mct+dfsg.121022-8
has caused the Debian Bug report #827122,
regarding liboasis3-0d: libpsmile.so is a broken symbolic link to 
libpsmile.MPI1.so.0d
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.)


-- 
827122: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827122
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: liboasis3-0d
Version: 3.mct+dfsg.121022-7+b1
Severity: important

Dear Maintainer,

libpsmile.so in /usr/lib/x86_64-linux-gnu is a broken symlink to

libpsmile.MPI1.so.0d

instead of

libpsmile.so.0d

which exists in the same directory (extra .MPI1).

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

Kernel: Linux 4.6.0-1-amd64 (SMP w/2 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)

Versions of packages liboasis3-0d depends on:
ii  libc62.22-11
ii  libnetcdf11  1:4.4.0-2
ii  libnetcdff6  4.4.4+ds-2

liboasis3-0d recommends no packages.

liboasis3-0d suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: oasis3
Source-Version: 3.mct+dfsg.121022-8

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated oasis3 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 03 May 2017 07:16:56 +0100
Source: oasis3
Binary: liboasis3-0d liboasis3-dev liboasis3-doc
Architecture: source amd64 all
Version: 3.mct+dfsg.121022-8
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Description:
 liboasis3-0d - Shared libraries for OASIS3 coupler
 liboasis3-dev - Development files for OASIS3 climate model coupler
 liboasis3-doc - Documentation and Examples for the OASIS climate model coupler
Closes: 827122
Changes:
 oasis3 (3.mct+dfsg.121022-8) unstable; urgency=medium
 .
   * Fix broken symlink libpsmile.so.0d. Closes: #827122
   * Standards-Version: 3.9.8. No changes required
Checksums-Sha1:
 d9d73149708bfb3338c87dc40b46375cba4a32ae 2161 oasis3_3.mct+dfsg.121022-8.dsc
 bdbb65832eb08a987eaf93c4916747bf5357b75a 10776 
oasis3_3.mct+dfsg.121022-8.debian.tar.xz
 21b2a8721a4d2e451c9a4ce9b16e9712b916f98b 272272 
liboasis3-0d_3.mct+dfsg.121022-8_amd64.deb
 d6ce390aeafa5d686356912f81b69d7d84c6c4aa 694266 
liboasis3-dev_3.mct+dfsg.121022-8_amd64.deb
 9670bde6a0d964b64e226b3af350ba8025e111a1 3225702 
liboasis3-doc_3.mct+dfsg.121022-8_all.deb
 8f0fe26a14e4f3ccc6a1c254e5ef960e71a9626b 10312 
oasis3_3.mct+dfsg.121022-8_amd64.buildinfo
Checksums-Sha256:
 f8f91c4814d7fd0116961d7b5c43a51a129016fabe171946dfe9d45ea69726aa 2161 
oasis3_3.mct+dfsg.121022-8.dsc
 7500c560dc3ef2d7a30f05f1d8aa28f7f932698ff95c6d5aa3bfb975c0c922c4 10776 
oasis3_3.mct+dfsg.121022-8.debian.tar.xz
 641e5a7e0f777ecaf8020763df2ff9be5f90b16f347b75941e3a74f06625e1e9 272272 
liboasis3-0d_3.mct+dfsg.121022-8_amd64.deb
 d30fe2ee0d9db3fa2b7d09b2c3ffa565d8f241a82a6a0ce9768989bc1cf8cfbb 694266 
liboasis3-dev_3.mct+dfsg.121022-8_amd64.deb
 f2ce66840a5b862eebe4f8eb94ea8e095f770c1e593876289d72c82afa60441d 3225702 
liboasis3-doc_3.mct+dfsg.121022-8_all.deb
 75ddf68dc2ac19af80a26946352d94f098bfb450055ce8bb391b291a29cae11b 10312 
oasis3_3.mct+dfsg.121022-8_amd64.buildinfo
Files:
 2566995efd38ba7c3ffc0f7047d59478 2161 science optional 
oasis3_3.mct+dfsg.121022-8.dsc
 309611185ecb6c291255e2927c5eb2f2 10776 science optional 
oasis3_3.mct+dfsg.121022-8.debian.tar.xz
 0022b231d5ee45059da911b56519f8ca 272272 libs optional 
liboasis3-0d_3.mct+dfsg.121022-8_amd64.deb
 268cf803d9c64525b2ab9e333034614a 694266 libdevel extra 
liboasis3-dev_3.mct+dfsg.121022-8_amd64.deb
 af8401997b6213def4e095ab850c81fc 3225702 doc optional 
liboasis3-doc_3.mct+dfsg.121022-8_

Bug#861684: r-cran-randomfields: FTBFS against r-base 3.4.0-1

[Anton Gladky]

2017-05-03 10:39 GMT+02:00 Andreas Tille :
> I'm tagging this sid since it is not relevant for testing.  It would be
> great if r-base maintainer would respect freeze policy to avoid this
> kind of problems.

That`s what we discuss each release. Unfortunately...

Anton

Processed: Re: Bug#861684: r-cran-randomfields: FTBFS against r-base 3.4.0-1

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 r-base
Bug #861684 [r-cran-randomfields] r-cran-randomfields: FTBFS against r-base 
3.4.0-1
Bug reassigned from package 'r-cran-randomfields' to 'r-base'.
No longer marked as found in versions r-cran-randomfields/3.1.36-1.
Ignoring request to alter fixed versions of bug #861684 to the same values 
previously set
> forcemerge 861333 -1
Bug #861333 [r-base] r-base: R packages uploaded to Debian before 14 April 2017 
that use .C or .Fortran fail to find objects
Bug #861684 [r-base] r-cran-randomfields: FTBFS against r-base 3.4.0-1
Marked as found in versions r-base/3.4.0-1.
Bug #861333 [r-base] r-base: R packages uploaded to Debian before 14 April 2017 
that use .C or .Fortran fail to find objects
Added tag(s) sid.
Merged 861333 861684

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

Bug#861684: r-cran-randomfields: FTBFS against r-base 3.4.0-1

[Ximin Luo]

Control: reassign -1 r-base
Control: forcemerge 861333 -1

Hey Andreas, I was told that this is a r-base issue, not an issue with 
r-cran-randomfields, and it is already being discussed in 861333.

Ximin

Andreas Tille:
> tags 861684 sid
> thanks
> 
> I'm tagging this sid since it is not relevant for testing.  It would be
> great if r-base maintainer would respect freeze policy to avoid this
> kind of problems. 
> 
> Kind regards
> 
>  Andreas.
> 


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

Processed: Re: Bug#861684: r-cran-randomfields: FTBFS against r-base 3.4.0-1

[Debian Bug Tracking System]

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

> tags 861684 sid
Bug #861684 [r-cran-randomfields] r-cran-randomfields: FTBFS against r-base 
3.4.0-1
Added tag(s) sid.
> thanks
Stopping processing here.

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

Bug#861684: r-cran-randomfields: FTBFS against r-base 3.4.0-1

[Andreas Tille]

tags 861684 sid
thanks

I'm tagging this sid since it is not relevant for testing.  It would be
great if r-base maintainer would respect freeze policy to avoid this
kind of problems. 

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#859262: Re: freezes Orca screen reader

[Alex ARNAUD]

I am CC'ing the accessibility list hoping that they might have an
insight to what is happening.  I have quoted the original mail in full
below for their sake.


I'm not yet a Stretch user but the Orca developer has submitted a patch 
to fix this bug : take a look at 
.


Best regards.
--
Alex ARNAUD
Visual-Impairment Project Manager
Hypra - "Humanizing technology"

Bug#860646: marked as done (golang-github-jacobsa-ogletest: FTBFS on i386: dh_auto_test: go test -v -p 1 github.com/jacobsa/ogletest github.com/jacobsa/ogletest/srcutil github.com/jacobsa/ogletest/tes

[Debian Bug Tracking System]

Your message dated Wed, 03 May 2017 07:33:26 +
with message-id 
and subject line Bug#860646: fixed in golang-github-jacobsa-ogletest 
0.0~git20150610-6.1
has caused the Debian Bug report #860646,
regarding golang-github-jacobsa-ogletest: FTBFS on i386: dh_auto_test: go test 
-v -p 1 github.com/jacobsa/ogletest github.com/jacobsa/ogletest/srcutil 
github.com/jacobsa/ogletest/test_cases 
github.com/jacobsa/ogletest/test_cases/mock_image returned exit code 1
to be marked as done.

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

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


-- 
860646: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860646
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-jacobsa-ogletest
Version: 0.0~git20150610-6
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
Justification: FTBFS in stretch on i386

Hi,

During a rebuild of all packages in stretch (in a stretch chroot, not a
sid chroot), your package failed to build on i386.

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=golang --with=golang
>dh_testdir -O--buildsystem=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   go install -v -p 1 github.com/jacobsa/ogletest 
> github.com/jacobsa/ogletest/srcutil github.com/jacobsa/ogletest/test_cases 
> github.com/jacobsa/ogletest/test_cases/mock_image
> github.com/jacobsa/oglematchers
> github.com/jacobsa/oglemock
> github.com/jacobsa/ogletest/srcutil
> golang.org/x/net/context
> github.com/jacobsa/reqtrace
> github.com/jacobsa/ogletest
> github.com/jacobsa/ogletest/test_cases/mock_image
> github.com/jacobsa/ogletest/test_cases
>dh_auto_test -O--buildsystem=golang
>   go test -v -p 1 github.com/jacobsa/ogletest 
> github.com/jacobsa/ogletest/srcutil github.com/jacobsa/ogletest/test_cases 
> github.com/jacobsa/ogletest/test_cases/mock_image
> === RUN   TestNoCurrentTest
> --- PASS: TestNoCurrentTest (0.00s)
> === RUN   TestNoFailure
> --- PASS: TestNoFailure (0.00s)
> === RUN   TestInvalidFormatString
> --- PASS: TestInvalidFormatString (0.00s)
> === RUN   TestNoMatchWithoutErrorText
> --- PASS: TestNoMatchWithoutErrorText (0.00s)
> === RUN   TestNoMatchWithErrorTExt
> --- PASS: TestNoMatchWithErrorTExt (0.00s)
> === RUN   TestFailureWithUserMessage
> --- PASS: TestFailureWithUserMessage (0.00s)
> === RUN   TestAdditionalFailure
> --- PASS: TestAdditionalFailure (0.00s)
> === RUN   TestGoldenFiles
> --- FAIL: TestGoldenFiles (4.45s)
>   integration_test.go:261: Output for test case panicking doesn't match 
> golden file.
> FAIL
> exit status 1
> FAIL  github.com/jacobsa/ogletest 4.458s
> === RUN   TestRegisterMethodsTest
> [--] Running tests from MethodsTest
> [ RUN  ] MethodsTest.NoMethods
> [   OK ] MethodsTest.NoMethods
> [ RUN  ] MethodsTest.OneMethod
> [   OK ] MethodsTest.OneMethod
> [ RUN  ] MethodsTest.MultipleMethods
> [   OK ] MethodsTest.MultipleMethods
> [--] Finished with tests from MethodsTest
> --- PASS: TestRegisterMethodsTest (0.00s)
> PASS
> okgithub.com/jacobsa/ogletest/srcutil 0.002s
> ? github.com/jacobsa/ogletest/test_cases  [no test files]
> ? github.com/jacobsa/ogletest/test_cases/mock_image   [no test files]
> dh_auto_test: go test -v -p 1 github.com/jacobsa/ogletest 
> github.com/jacobsa/ogletest/srcutil github.com/jacobsa/ogletest/test_cases 
> github.com/jacobsa/ogletest/test_cases/mock_image returned exit code 1

The full build log is available from:
   
http://aws-logs.debian.net/2017/04/18/golang-github-jacobsa-ogletest_0.0~git20150610-6_testing-i386.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: golang-github-jacobsa-ogletest
Source-Version: 0.0~git20150610-6.1

We believe that the bug you reported is fixed in the latest version of
golang-github-jacobsa-ogletest, 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 860...@bugs.debian.org,
and the maintainer will reopen th