Processed: Re: src:alot: Please drop "Use file-magic instead of python-magic" patch, alot will FTBFS soon

[Debian Bug Tracking System]

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

> # FTBFS
> severity 889293 serious
Bug #889293 [src:alot] alot: FTBFS: Please drop "Use file-magic instead of 
python-magic" patch
Ignoring request to change severity of Bug 889293 to the same value.
> tags 889293 patch
Bug #889293 [src:alot] alot: FTBFS: Please drop "Use file-magic instead of 
python-magic" patch
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#889293: src:alot: Please drop "Use file-magic instead of python-magic" patch, alot will FTBFS soon

[Christoph Biedl]

# FTBFS
severity 889293 serious
tags 889293 patch
thanks

Christoph Biedl wrote...

> The new python-magic implementation will hit unstable very soon,
> causing your package to FTBFS.

python-magic 2:0.4.15-1 is now in unstable, hence raising severity.

Also, I've prepared a NMU as attached but found alot fails to build on
some (non-release) archs and like to investigate first. Feel free to go
ahead, though.

Regards,

Christoph
diff -Nru alot-0.6/debian/changelog alot-0.6/debian/changelog
--- alot-0.6/debian/changelog   2017-09-07 02:41:22.0 +0200
+++ alot-0.6/debian/changelog   2018-02-04 18:24:59.0 +0100
@@ -1,3 +1,10 @@
+alot (0.6-2.1) unstable; urgency=high
+
+  * Non-maintainer upload
+  * Drop "Use file-magic instead of python-magic" patch. Closes: #889293
+
+ -- Christoph Biedl   Sun, 04 Feb 2018 
18:24:59 +0100
+
 alot (0.6-2) unstable; urgency=low
 
   * Depend on python-gpg rather than pygpgme for alot package
diff -Nru alot-0.6/debian/control alot-0.6/debian/control
--- alot-0.6/debian/control 2017-09-07 02:41:22.0 +0200
+++ alot-0.6/debian/control 2018-02-04 18:24:59.0 +0100
@@ -14,7 +14,7 @@
  python-configobj,
  python-doc,
  python-gpg,
- python-magic,
+ python-magic (>= 2:0.4.15),
  python-mock,
  python-notmuch,
  python-setuptools,
diff -Nru 
alot-0.6/debian/patches/0002-debian-Use-file-magic-instead-of-python-magic-in-set.patch
 
alot-0.6/debian/patches/0002-debian-Use-file-magic-instead-of-python-magic-in-set.patch
--- 
alot-0.6/debian/patches/0002-debian-Use-file-magic-instead-of-python-magic-in-set.patch
 2017-08-21 01:37:30.0 +0200
+++ 
alot-0.6/debian/patches/0002-debian-Use-file-magic-instead-of-python-magic-in-set.patch
 1970-01-01 01:00:00.0 +0100
@@ -1,26 +0,0 @@
-From c8e3b0d9fce9b95b52f5f9c42ba35a3a1c631d18 Mon Sep 17 00:00:00 2001
-From: Jordan Justen 
-Date: Thu, 16 Feb 2017 17:35:32 -0800
-Subject: [PATCH] debian: Use file-magic instead of python-magic in setup.py
-
-Signed-off-by: Jordan Justen 

- setup.py | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/setup.py b/setup.py
-index f20c5cba..03a1969e 100755
 a/setup.py
-+++ b/setup.py
-@@ -45,7 +45,7 @@ setup(
- 'urwid>=1.1.0',
- 'urwidtrees>=1.0',
- 'twisted>=10.2.0',
--'python-magic',
-+'file-magic',
- 'configobj>=4.7.0',
- 'gpg'
- ],
--- 
-2.14.0
-
diff -Nru alot-0.6/debian/patches/series alot-0.6/debian/patches/series
--- alot-0.6/debian/patches/series  2017-07-10 00:53:58.0 +0200
+++ alot-0.6/debian/patches/series  2018-02-04 18:24:59.0 +0100
@@ -1,2 +1 @@
 0001-Description-Use-local-intersphinx-inventories.patch
-0002-debian-Use-file-magic-instead-of-python-magic-in-set.patch


signature.asc
Description: PGP signature

Bug#889608: man-db: man(1) dumps core (AppArmor involved)

[intrigeri]

Control: tag -1 + patch

intrigeri:
>> B) remove the AppArmor profile entirely and rely on seccomp instead
>> C) don't enable "no new privs" and rely on AppArmor instead

> I think B is fine given all the non-AppArmor hardening efforts Colin
> has been putting into man-db recently.

There we go: https://salsa.debian.org/debian/man-db/merge_requests/1

I've verified that upgrading from 2.8.0-1 successfully unloads the
profile on my system. I didn't test this upgrade path on a system
that has AppArmor disabled though.

Cheers,
-- 
intrigeri

Processed: Re: Bug#889608: man-db: man(1) dumps core (AppArmor involved)

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + patch
Bug #889608 [man-db] man-db: man(1) dumps core (AppArmor involved)
Bug #889617 [man-db] man-db: all man pages fail to display with "command exited 
with status 4"
Added tag(s) patch.
Added tag(s) patch.

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

Bug#889608: man-db: man(1) dumps core (AppArmor involved)

[intrigeri]

intrigeri:
> A) drop the child profiles (groff, filter), merge their rules into the
>main /usr/bin/man profile, and use ix instead of Cx; these rules
>are not particularly scary so this doesn't seem crazy an option

I had a closer look and what's scary is not the rules that can be
found in the child profiles, it's the fact that if we drop the child
profiles, all processes run by man will have full access to the
filesystem:

  # The purpose of this profile isn't to confine man itself (that might be
  # nice in the future, but is tricky since it's quite configurable), but to
  # confine the processes it calls that parse untrusted data.
  /** mrixwlk,

… i.e. the /usr/bin/man profile would be mostly useless. So let's
forget about option A and instead choose between:

> B) remove the AppArmor profile entirely and rely on seccomp instead
> C) don't enable "no new privs" and rely on AppArmor instead

I think B is fine given all the non-AppArmor hardening efforts Colin
has been putting into man-db recently.

Cheers,
-- 
intrigeri

Bug#889629: pd-iemutils binary-all FTBFS: debian/*//usr/lib/pd/extra': No such file or directory

[Adrian Bunk]

Source: pd-iemutils
Version: 0.0.20161027-2
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=pd-iemutils=all=0.0.20161027-2=1517780292=0

...
   debian/rules override_dh_install
make[1]: Entering directory '/<>'
dh_install
find /<>/debian/*//usr/lib/pd/extra -name "*.pd_linux" -exec \
chmod 0664 {} +
find: '/<>/debian/*//usr/lib/pd/extra': No such file or directory
debian/rules:34: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 1

Bug#889608: Bug#889617: man-db: all man pages fail to display with "command exited with status 4"

[intrigeri]

Ben Caradoc-Davies:
>> Ben Caradoc-Davies wrote:
>>> And what I would like to know is how the fscking apparmor module got
>>> loaded in the first place, given that I have the apparmor service
>>> masked:
>>> # ls -al /etc/systemd/system/apparmor.service
>>> lrwxrwxrwx 1 root root 9 Dec  8 11:24
>>> /etc/systemd/system/apparmor.service -> /dev/null
>>> Yet:
>>> # aa-status
>>> apparmor module is loaded.
>> You've masked a systemd service. But "module" probably refers to some
>> kernel module here, which is enabled by default since a while in
>> Debian Unstable.

More precisely "module" in this context is to be understood as in
Linux Security Module (LSM). To fully disable the AppArmor LSM, pass
apparmor=0 on the kernel command line (security= might be needed on
top of that, didn't check recently, sorry). Marking/disabling
apparmor.service merely prevents policy loading on boot and might not
be what you want.

Cheers,
-- 
intrigeri

Bug#889627: firebird3.0 FTBFS on most architectures: crash in self-build binaries during the build

[Adrian Bunk]

Source: firebird3.0
Version: 3.0.3.32900.ds4-1
Severity: serious

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

Symptoms are slightly varying, e.g. on arm64:

...
/usr/bin/make gpre
make[4]: Entering directory '/<>/gen'
rm -f metadata.fdb
/<>/gen/Release/firebird/bin/isql -q -i 
/<>/src/dbs/metadata.sql
free(): invalid size
Makefile:323: recipe for target 'metadata.fdb' failed
make[4]: *** [metadata.fdb] Aborted

Bug#889626: man-db FTBFS on ppc64el: error: invalid application of 'sizeof' to incomplete type 'struct termios'

[Adrian Bunk]

Source: man-db
Version: 2.8.0-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=man-db=ppc64el=2.8.0-1=1517768128=0

...
../../../lib/sandbox.c: In function 'make_seccomp_filter':
../../../lib/sandbox.c:435:50: error: invalid application of 'sizeof' to 
incomplete type 'struct termios'
   SC_ALLOW_ARG_1 ("ioctl", SCMP_A1 (SCMP_CMP_EQ, TCGETS));
  ^
../../../lib/sandbox.c:183:53: note: in definition of macro 'SC_ALLOW_ARG_1'
   if (seccomp_rule_add (ctx, SCMP_ACT_ALLOW, nr, 1, cmp1) < 0) \
 ^~~~
Makefile:1662: recipe for target 'libman_la-sandbox.lo' failed
make[3]: *** [libman_la-sandbox.lo] Error 1

Bug#889608: man-db: man(1) dumps core (AppArmor involved)

[intrigeri]

Hi,

gregor herrmann:
> drop_effective_privs()
> ++priv_drop_count = 1
> man: command exited with status 4: /usr/lib/man-db/zsoelim |
> /usr/lib/man-db/manconv -f UTF-8:ISO-8859-1 -t UTF-8//IGNORE | preconv -e 
> UTF-8 | tbl
> | nroff -mandoc -rLL=146n -rLT=146n -Tutf8
> hashtable_free: 9 entries, 9 (100%) unique

> (without --debug only the last line)

> In parallel AppArmor says:

> Feb 4 23:37:53 jadzia kernel: [1342803.492299] audit: type=1400
> audit(1517783873.721:714): apparmor="DENIED" operation="exec" info="no new 
> privs"
> error=-1 profile="/usr/bin/man" name="/usr/bin/preconv" pid=14287 comm="man"
> requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 
> target="/usr/bin/man//groff"

"no new privs" forbids profile transitions, see
https://lists.ubuntu.com/archives/apparmor/2017-October/011142.html
for details.

So we have a few options:

A) drop the child profiles (groff, filter), merge their rules into the
   main /usr/bin/man profile, and use ix instead of Cx; these rules
   are not particularly scary so this doesn't seem crazy an option

B) remove the AppArmor profile entirely and rely on seccomp instead

C) don't enable "no new privs" and rely on AppArmor instead

Personally my choice would be A >> B >> C.

Colin, if you need help with option A, please let us know :)

Cheers,
-- 
intrigeri

Bug#888131: marked as done (ruby-oj: FTBFS on ruby2.5: too many arguments to function 'rb_struct_ptr')

[Debian Bug Tracking System]

Your message dated Mon, 05 Feb 2018 06:52:03 +
with message-id 
and subject line Bug#888131: fixed in ruby-oj 3.4.0-1
has caused the Debian Bug report #888131,
regarding ruby-oj: FTBFS on ruby2.5: too many arguments to function 
'rb_struct_ptr'
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.)


-- 
888131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888131
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-oj
Version: 2.17.4-1
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5

Dear Maintainer,

This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.

There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition

Build log excerpt:

current directory: /build/ruby-oj-2.17.4/ext/oj
make V=1 "DESTDIR="
make[1]: Entering directory '/build/ruby-oj-2.17.4/ext/oj'
...
gcc -I. -I/usr/include/x86_64-linux-gnu/ruby-2.5.0 
-I/usr/include/ruby-2.5.0/ruby/backward -I/usr/include/ruby-2.5.0 -I. 
-Wdate-time -D_FORTIFY_SOURCE=2   -DRUBY_TYPE=ruby -DRUBY_RUBY 
-DRUBY_VERSION=2.5.0 -DRUBY_VERSION_MAJOR=2 -DRUBY_VERSION_MINOR=5 
-DRUBY_VERSION_MICRO=0 -DHAS_RB_TIME_TIMESPEC=1 -DHAS_ENCODING_SUPPORT=1 
-DHAS_NANO_TIME=1 -DHAS_IVAR_HELPERS=1 -DHAS_EXCEPTION_MAGIC=1 
-DHAS_PROC_WITH_BLOCK=1 -DHAS_TOP_LEVEL_ST_H=0 -DNEEDS_RATIONAL=0 
-DIS_WINDOWS=0 -DUSE_PTHREAD_MUTEX=1 -DUSE_RB_MUTEX=0 -DDATETIME_1_8=0 
-DNO_TIME_ROUND_PAD=0 -DHAS_DATA_OBJECT_WRAP=1 -Wall -fPIC -g -O2 
-fdebug-prefix-map=/build/ruby2.5-ed5dT1/ruby2.5-2.5.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC  -o dump.o -c 
dump.c
dump.c: In function 'dump_struct_obj':
dump.c:1880:2: warning: 'rb_struct_ptr' is deprecated 
[-Wdeprecated-declarations]
  for (i = (int)RSTRUCT_LEN(obj), vp = RSTRUCT_CONST_PTR(obj); 0 < i; i--, 
vp++) {
  ^~~
In file included from /usr/include/ruby-2.5.0/ruby/ruby.h:24:0,
 from /usr/include/ruby-2.5.0/ruby.h:33,
 from oj.h:43,
 from dump.c:43:
/usr/include/ruby-2.5.0/ruby/backward.h:47:37: note: declared here
 DECLARE_DEPRECATED_INTERNAL_FEATURE(rb_struct_ptr);
 ^
/usr/include/x86_64-linux-gnu/ruby-2.5.0/ruby/config.h:129:52: note: in 
definition of macro 'NORETURN'
 #define NORETURN(x) __attribute__ ((__noreturn__)) x
^
/usr/include/ruby-2.5.0/ruby/backward.h:39:14: note: in expansion of macro 
'ERRORFUNC'
 NORETURN(ERRORFUNC(("deprecated internal function"), DEPRECATED(void 
func(void
  ^
/usr/include/ruby-2.5.0/ruby/backward.h:39:58: note: in expansion of macro 
'DEPRECATED'
 NORETURN(ERRORFUNC(("deprecated internal function"), DEPRECATED(void 
func(void
  ^~
/usr/include/ruby-2.5.0/ruby/backward.h:47:1: note: in expansion of macro 
'DECLARE_DEPRECATED_INTERNAL_FEATURE'
 DECLARE_DEPRECATED_INTERNAL_FEATURE(rb_struct_ptr);
 ^
In file included from /usr/include/ruby-2.5.0/ruby.h:33:0,
 from oj.h:43,
from dump.c:43:








/usr/include/ruby-2.5.0/ruby/ruby.h:1189:33: error: too many arguments to 
function 'rb_struct_ptr'
 #define RSTRUCT_PTR(st) rb_struct_ptr(st)








^
dump.c:1878:47: note: in expansion of macro 'RSTRUCT_PTR'
 # define RSTRUCT_CONST_PTR(st) (const VALUE *)RSTRUCT_PTR(st)
   ^~~
dump.c:1880:39: note: in expansion of macro 'RSTRUCT_CONST_PTR'
  for (i = (int)RSTRUCT_LEN(obj), vp = RSTRUCT_CONST_PTR(obj); 0 < i; i--, 
vp++) {
   ^
In file included from /usr/include/ruby-2.5.0/ruby/ruby.h:24:0,
 from /usr/include/ruby-2.5.0/ruby.h:33,
 from oj.h:43,
 from dump.c:43:
/usr/include/ruby-2.5.0/ruby/backward.h:47:37: note: declared here
 DECLARE_DEPRECATED_INTERNAL_FEATURE(rb_struct_ptr);
 ^
/usr/include/x86_64-linux-gnu/ruby-2.5.0/ruby/config.h:129:52: note: in 
definition of macro 'NORETURN'
 #define NORETURN(x) __attribute__ ((__noreturn__)) x
^
/usr/include/ruby-2.5.0/ruby/backward.h:39:14: note: in expansion of macro 
'ERRORFUNC'
 NORETURN(ERRORFUNC(("deprecated internal function"), DEPRECATED(void 
func(void
  ^
/usr/include/ruby-2.5.0/ruby/backward.h:39:58: note: in 

Bug#889609: marked as done (moonshot-gss-eap: uninstallable in sid: libgssapi-krb5-2 : Breaks: moonshot-gss-eap (<= 1.0) but 0.9.5-3+b1 is to be installed)

[Debian Bug Tracking System]

Your message dated Mon, 5 Feb 2018 08:40:53 +0200
with message-id <20180205064052.GU3126@localhost>
and subject line Already fixed in experimental
has caused the Debian Bug report #889609,
regarding moonshot-gss-eap: uninstallable in sid: libgssapi-krb5-2 : Breaks: 
moonshot-gss-eap (<= 1.0) but 0.9.5-3+b1 is to be installed
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.)


-- 
889609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889609
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: moonshot-gss-eap
Version: 0.9.5-3
Severity: serious
Tags: sid
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable in sid:

The following packages have unmet dependencies:
 libgssapi-krb5-2 : Breaks: moonshot-gss-eap (<= 1.0) but 0.9.5-3+b1 is to be 
installed

This can probably be fixed by migrating the packages from experimental
to sid ...


Cheers,

Andreas
--- End Message ---
--- Begin Message ---
Version: 1.0.1-3

1.0.1-3 > 1.0

cu
Adrian

-- 

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

Bug#734101: [Pkg-javascript-devel] Bug#734101: libjs-jquery-mobile: New Release

[Daniel Kahn Gillmor]

On Fri 2014-01-03 14:04:26 -0600, in https://bugs.debian.org/734101 Charlie 
Smotherman wrote:
> Package: libjs-jquery-mobile
> Version: 1.2.0+dfsg-2
> Severity: wishlist

What's going on with libjs-jquery-mobile?  It would be really good for
debian to ship an up-to-date version of libjs-jquery-mobile, or at least
as up-to-date as libjs-jquery at any rate.

is there a reason that libjs-jquery-mobile is in worse shape than the
other libjs-jquery-* packages?

  --dkg

Bug#888730: marked as done (booth binary-all FTBFS: test failure)

[Debian Bug Tracking System]

Your message dated Mon, 05 Feb 2018 03:00:13 +
with message-id 
and subject line Bug#888730: fixed in booth 1.0-6
has caused the Debian Bug report #888730,
regarding booth binary-all FTBFS: test failure
to be marked as done.

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

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


-- 
888730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888730
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: booth
Version: 1.01.0-5
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=booth=all=1.0-5=1516927397=0

...
FAILED (failures=1)

Stdout:


--
Running /<>/test/../src/boothd client grant -s site -t 
abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijk
with config from /etc/booth/booth.conf
Started subprocess pid 11380
Waiting on 11380 for 0.1s ...
Waiting on 11380 for 0.2s ...
Waiting on 11380 for 0.4s ...
Waiting on 11380 for 0.8s ...
Waiting on 11380 for 0.5s ...
pid 11380 still running
Left /tmp/booth-tests/1516927377.44GRmP for debugging
FAIL test/runtests.py (exit status: 1)


Testsuite summary for booth 1.0

# TOTAL: 1
# PASS:  0
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See ./test-suite.log
Please report to us...@clusterlabs.org

Makefile:1042: recipe for target 'test-suite.log' failed
make[4]: *** [test-suite.log] Error 1
--- End Message ---
--- Begin Message ---
Source: booth
Source-Version: 1.0-6

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

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

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

Debian distribution maintenance software
pp.
Valentin Vidic  (supplier of updated booth package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 29 Jan 2018 21:32:49 +0100
Source: booth
Binary: booth booth-pacemaker
Architecture: source amd64 all
Version: 1.0-6
Distribution: unstable
Urgency: medium
Maintainer: Debian HA Maintainers 

Changed-By: Valentin Vidic 
Description:
 booth  - Cluster Ticket Manager
 booth-pacemaker - Resource agents to integrate booth with Pacemaker
Closes: 888730
Changes:
 booth (1.0-6) unstable; urgency=medium
 .
   * d/rules: replace dh_systemd_{enable,start} with dh_installsystemd
   * d/tests: run upstream unit tests (Closes: #888730)
   * d/copyright: update Format URL
   * d/copyright: remove duplicate paragraph
   * d/control: remove duplicate Section
   * d/patches: fix spelling errors reported by lintian
   * d/rules: don't ship html versions of man pages
   * d/booth.service: add Documentation key
Checksums-Sha1:
 f4aab9b50661539ae1af9518f3d2e0c97f542687 2306 booth_1.0-6.dsc
 ee17b83ba1e2956c3ea096b65703a0d33ee0f6b7 7556 booth_1.0-6.debian.tar.xz
 bd78cf5c749916a77ab82fbc56c5c5be0a2fe65d 323148 booth-dbgsym_1.0-6_amd64.deb
 cb6f4cf11f3534831d4e81540534fdf7c7609a7a 12480 booth-pacemaker_1.0-6_all.deb
 40571ca3bba2a093bcdd6f9d38ed199839305ccb 7911 booth_1.0-6_amd64.buildinfo
 6b247b34be60f1463d06a8594ce9fd254b4b19ca 77360 booth_1.0-6_amd64.deb
Checksums-Sha256:
 fe371b6af1f3cd0a0ce4a3798063a2ebf48fab9f1ba6d0c46dae82d9c65d33c6 2306 
booth_1.0-6.dsc
 3eea3d36afd19c551566762ab6b5ee4abd1967d125500108c3538eff1084 7556 
booth_1.0-6.debian.tar.xz
 8e21a108f44135378b82718df3f48a871c127e8ebba29d8ef1e48d156c38bc91 323148 
booth-dbgsym_1.0-6_amd64.deb
 1cdc0e66cae76b8b31bbb8e7c43b5aa9c67da3ab75d25ad0b639b57a6253180d 12480 
booth-pacemaker_1.0-6_all.deb
 0f86f17be3ac7a3bf75db46902c776f7bc674307cbd3107d60f5e9e3d22429c8 7911 
booth_1.0-6_amd64.buildinfo
 117e20c6f1f662342e7a132fea40173d955a12b8240577c526988265157c8f9e 77360 
booth_1.0-6_amd64.deb
Files:
 4879177a1f60a10e29ccb9b61118a39d 2306 admin optional booth_1.0-6.dsc
 

Bug#884102: marked as done (yowsup FTBFS: TypeError: Error when calling the metaclass bases)

[Debian Bug Tracking System]

Your message dated Mon, 05 Feb 2018 03:01:15 +
with message-id 
and subject line Bug#884102: fixed in yowsup 2.5.7-1
has caused the Debian Bug report #884102,
regarding yowsup FTBFS: TypeError: Error when calling the metaclass bases
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.)


-- 
884102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884102
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yowsup
Version: 2.5.0~git20160904.d69c1ff-1
Severity: serious
Tags: buster sid

Some recent change in unstable makes yowsup FTBFS:

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

...
==
ERROR: yowsup.common.http.test_warequest (unittest.loader.ModuleImportFailure)
--
ImportError: Failed to import test module: yowsup.common.http.test_warequest
Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/loader.py", line 254, in _find_tests
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/unittest/loader.py", line 232, in 
_get_module_from_name
__import__(name)
  File 
"/build/1st/yowsup-2.5.0~git20160904.d69c1ff/yowsup/common/http/__init__.py", 
line 2, in 
from .warequest import WARequest
  File 
"/build/1st/yowsup-2.5.0~git20160904.d69c1ff/yowsup/common/http/warequest.py", 
line 4, in 
from yowsup.env import YowsupEnv
  File "/build/1st/yowsup-2.5.0~git20160904.d69c1ff/yowsup/env/__init__.py", 
line 1, in 
from .env import YowsupEnv
  File "/build/1st/yowsup-2.5.0~git20160904.d69c1ff/yowsup/env/env.py", line 
15, in 
class YowsupEnv(with_metaclass(YowsupEnvType, object)):
  File "/usr/lib/python2.7/abc.py", line 87, in __new__
cls = super(ABCMeta, mcls).__new__(mcls, name, bases, namespace)
TypeError: Error when calling the metaclass bases
metaclass conflict: the metaclass of a derived class must be a (non-strict) 
subclass of the metaclasses of all its bases


==
ERROR: yowsup.env.test_env_s40 (unittest.loader.ModuleImportFailure)
--
ImportError: Failed to import test module: yowsup.env.test_env_s40
Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/loader.py", line 254, in _find_tests
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/unittest/loader.py", line 232, in 
_get_module_from_name
__import__(name)
  File "/build/1st/yowsup-2.5.0~git20160904.d69c1ff/yowsup/env/__init__.py", 
line 1, in 
from .env import YowsupEnv
  File "/build/1st/yowsup-2.5.0~git20160904.d69c1ff/yowsup/env/env.py", line 
15, in 
class YowsupEnv(with_metaclass(YowsupEnvType, object)):
  File "/usr/lib/python2.7/abc.py", line 87, in __new__
cls = super(ABCMeta, mcls).__new__(mcls, name, bases, namespace)
TypeError: Error when calling the metaclass bases
metaclass conflict: the metaclass of a derived class must be a (non-strict) 
subclass of the metaclasses of all its bases
...
--- End Message ---
--- Begin Message ---
Source: yowsup
Source-Version: 2.5.7-1

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

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

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

Debian distribution maintenance software
pp.
Josue Ortega  (supplier of updated yowsup package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 06 Jan 2018 13:18:33 -0600
Source: yowsup
Binary: python-yowsup python3-yowsup python-yowsup-common yowsup-cli
Architecture: source all
Version: 2.5.7-1
Distribution: experimental
Urgency: medium
Maintainer: Josue Ortega 
Changed-By: Josue Ortega 
Description:
 python-yowsup - library to implement a WhatsApp client
 python-yowsup-common - library to implement a WhatsApp client (common files)
 python3-yowsup - Python 

Bug#790169: marked as done (geany-plugins: depends on vte which is deprecated)

[Debian Bug Tracking System]

Your message dated Mon, 05 Feb 2018 03:00:43 +
with message-id 
and subject line Bug#790169: fixed in geany-plugins 1.32+dfsg-3
has caused the Debian Bug report #790169,
regarding geany-plugins: depends on vte which is deprecated
to be marked as done.

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

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


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

Hi,

geany-plugins depends on python-vte / libvte9, which are deprecated
in favor of gir1.2-vte-2.91 / libvte-2.91-0. Thus we want to remove
src:vte from the archive. geany-plugins should switch to the new vte
version.

Please try to do this before the Stretch release as we're going to
try to remove src:vte this cycle.

We'll bump this to serious when the list of rdeps is small and we're
getting ready to removing vte completely.

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

Emilio 
--- End Message ---
--- Begin Message ---
Source: geany-plugins
Source-Version: 1.32+dfsg-3

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

Debian distribution maintenance software
pp.
Chow Loong Jin  (supplier of updated geany-plugins package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 11 Jan 2018 03:17:55 +0800
Source: geany-plugins
Binary: geany-plugins geany-plugins-common geany-plugin-addons 
geany-plugin-autoclose geany-plugin-automark geany-plugin-codenav 
geany-plugin-commander geany-plugin-ctags geany-plugin-defineformat 
geany-plugin-doc geany-plugin-extrasel geany-plugin-gendoc 
geany-plugin-geniuspaste geany-plugin-gproject geany-plugin-git-changebar 
geany-plugin-keyrecord geany-plugin-insertnum geany-plugin-latex 
geany-plugin-lipsum geany-plugin-lua geany-plugin-lineoperations 
geany-plugin-macro geany-plugin-miniscript geany-plugin-overview 
geany-plugin-numberedbookmarks geany-plugin-pairtaghighlighter geany-plugin-pg 
geany-plugin-pohelper geany-plugin-prj geany-plugin-projectorganizer 
geany-plugin-sendmail geany-plugin-tableconvert geany-plugin-vc 
geany-plugin-prettyprinter geany-plugin-shiftcolumn geany-plugin-spellcheck 
geany-plugin-treebrowser geany-plugin-updatechecker geany-plugin-workbench 
geany-plugin-xmlsnippets
Architecture: source amd64 all
Version: 1.32+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Geany Packaging Team 
Changed-By: Chow Loong Jin 
Description:
 geany-plugin-addons - miscellaneous plugins for Geany
 geany-plugin-autoclose - auto-closing plugin for Geany
 geany-plugin-automark - auto-mark plugin for Geany
 geany-plugin-codenav - code navigation plugin for Geany
 geany-plugin-commander - command panel plugin for Geany
 geany-plugin-ctags - ctags plugin for Geany
 geany-plugin-defineformat - on-the-fly #define prettyprinter plugin for Geany
 geany-plugin-doc - documentation plugin for Geany
 geany-plugin-extrasel - extra selection plugin for Geany
 geany-plugin-gendoc - documentation generation plugin for Geany
 geany-plugin-geniuspaste - GeniusPaste plugin for Geany
 geany-plugin-git-changebar - git change bar plugin for Geany
 geany-plugin-gproject - transitional dummy package for 
geany-plugin-projectorganizer
 geany-plugin-insertnum - number inserting plugin for Geany
 geany-plugin-keyrecord - git change bar plugin for Geany
 geany-plugin-latex - improved LaTeX support plugin for Geany
 geany-plugin-lineoperations - Line Operations plugin for Geany
 geany-plugin-lipsum - Lorem Ipsum generator plugin for Geany
 geany-plugin-lua - Lua scripting plugin for Geany
 geany-plugin-macro - macro plugin for Geany
 geany-plugin-miniscript - Geany Mini-Script filter plugin
 geany-plugin-numberedbookmarks - numbered bookmarks plugin for Geany
 geany-plugin-overview - overview plugin for Geany
 geany-plugin-pairtaghighlighter - 

Bug#790169: marked as done (geany-plugins: depends on vte which is deprecated)

[Debian Bug Tracking System]

Your message dated Mon, 05 Feb 2018 03:00:35 +
with message-id 
and subject line Bug#790169: fixed in geany-plugins 1.32+dfsg-2
has caused the Debian Bug report #790169,
regarding geany-plugins: depends on vte which is deprecated
to be marked as done.

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

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


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

Hi,

geany-plugins depends on python-vte / libvte9, which are deprecated
in favor of gir1.2-vte-2.91 / libvte-2.91-0. Thus we want to remove
src:vte from the archive. geany-plugins should switch to the new vte
version.

Please try to do this before the Stretch release as we're going to
try to remove src:vte this cycle.

We'll bump this to serious when the list of rdeps is small and we're
getting ready to removing vte completely.

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

Emilio 
--- End Message ---
--- Begin Message ---
Source: geany-plugins
Source-Version: 1.32+dfsg-2

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

Debian distribution maintenance software
pp.
Chow Loong Jin  (supplier of updated geany-plugins package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 09 Jan 2018 03:35:45 +0800
Source: geany-plugins
Binary: geany-plugins geany-plugins-common geany-plugin-addons 
geany-plugin-autoclose geany-plugin-automark geany-plugin-codenav 
geany-plugin-commander geany-plugin-ctags geany-plugin-defineformat 
geany-plugin-doc geany-plugin-extrasel geany-plugin-gendoc 
geany-plugin-geniuspaste geany-plugin-gproject geany-plugin-git-changebar 
geany-plugin-keyrecord geany-plugin-insertnum geany-plugin-latex 
geany-plugin-lipsum geany-plugin-lua geany-plugin-lineoperations 
geany-plugin-macro geany-plugin-markdown geany-plugin-miniscript 
geany-plugin-overview geany-plugin-numberedbookmarks 
geany-plugin-pairtaghighlighter geany-plugin-pg geany-plugin-pohelper 
geany-plugin-prj geany-plugin-projectorganizer geany-plugin-sendmail 
geany-plugin-tableconvert geany-plugin-vc geany-plugin-prettyprinter 
geany-plugin-shiftcolumn geany-plugin-spellcheck geany-plugin-treebrowser 
geany-plugin-updatechecker geany-plugin-webhelper geany-plugin-workbench 
geany-plugin-xmlsnippets
Architecture: source amd64 all
Version: 1.32+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Geany Packaging Team 
Changed-By: Chow Loong Jin 
Description:
 geany-plugin-addons - miscellaneous plugins for Geany
 geany-plugin-autoclose - auto-closing plugin for Geany
 geany-plugin-automark - auto-mark plugin for Geany
 geany-plugin-codenav - code navigation plugin for Geany
 geany-plugin-commander - command panel plugin for Geany
 geany-plugin-ctags - ctags plugin for Geany
 geany-plugin-defineformat - on-the-fly #define prettyprinter plugin for Geany
 geany-plugin-doc - documentation plugin for Geany
 geany-plugin-extrasel - extra selection plugin for Geany
 geany-plugin-gendoc - documentation generation plugin for Geany
 geany-plugin-geniuspaste - GeniusPaste plugin for Geany
 geany-plugin-git-changebar - git change bar plugin for Geany
 geany-plugin-gproject - transitional dummy package for 
geany-plugin-projectorganizer
 geany-plugin-insertnum - number inserting plugin for Geany
 geany-plugin-keyrecord - git change bar plugin for Geany
 geany-plugin-latex - improved LaTeX support plugin for Geany
 geany-plugin-lineoperations - Line Operations plugin for Geany
 geany-plugin-lipsum - Lorem Ipsum generator plugin for Geany
 geany-plugin-lua - Lua scripting plugin for Geany
 geany-plugin-macro - macro plugin for Geany
 geany-plugin-markdown - markdown plugin for Geany
 geany-plugin-miniscript - Geany Mini-Script filter plugin
 geany-plugin-numberedbookmarks - numbered bookmarks plugin 

Processed: severity of 889293 is serious ...

[Debian Bug Tracking System]

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

> severity 889293 serious
Bug #889293 [src:alot] src:alot: Please drop "Use file-magic instead of 
python-magic" patch, alot will FTBFS soon
Severity set to 'serious' from 'important'
> retitle 889293 alot: FTBFS: Please drop "Use file-magic instead of 
> python-magic" patch
Bug #889293 [src:alot] src:alot: Please drop "Use file-magic instead of 
python-magic" patch, alot will FTBFS soon
Changed Bug title to 'alot: FTBFS: Please drop "Use file-magic instead of 
python-magic" patch' from 'src:alot: Please drop "Use file-magic instead of 
python-magic" patch, alot will FTBFS soon'.
> thanks
Stopping processing here.

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

Bug#889620: missing entry in debian/copyright

[Thorsten Alteholz]

Package: jupyter-core
Version: 4.4.0
Severity: serious
thanks

Hi,

please add the missing licenses of:
 jupyter_core-4.4.0/jupyter_core/utils/shutil_which.py
to debian/copyright.

Thanks!
  Thorsten

Bug#889608: Bug#889617: man-db: all man pages fail to display with "command exited with status 4"

[Ben Caradoc-Davies]

On 05/02/18 13:40, Axel Beckert wrote:

Control: merge 889608 -1
Hi Ben,
thanks for the bug report.
Ben Caradoc-Davies wrote:

under man-db 2.8.0-1 amd64 all man pages fail to display with:
$ man man
man: command exited with status 4: /usr/lib/man-db/zsoelim | /usr/lib/man-
db/manconv -f UTF-8:ISO-8859-1 -t UTF-8//IGNORE | preconv -e UTF-8 | tbl |
nroff -mandoc -rLL=184n -rLT=184n -Tutf8

Ben Caradoc-Davies wrote:

With 2.8.0-1, I see AppArmor messages in the systemd journal for "man man":

This sounds like https://bugs.debian.org/889608 reported only shortly
before your bug report. Hence merging.


Thanks, Axel. I just read the MAN_DISABLE_SECCOMP=1 discussion in 
#889608 and I concur that they are likely the same apparmor problem.



Ben Caradoc-Davies wrote:

And what I would like to know is how the fscking apparmor module got
loaded in the first place, given that I have the apparmor service
masked:
# ls -al /etc/systemd/system/apparmor.service
lrwxrwxrwx 1 root root 9 Dec  8 11:24
/etc/systemd/system/apparmor.service -> /dev/null
Yet:
# aa-status
apparmor module is loaded.

You've masked a systemd service. But "module" probably refers to some
kernel module here, which is enabled by default since a while in
Debian Unstable.


Yes, I think you are right. I am guessing that the man-db package 
install phase dh_apparmor command loads or enables the kernel apparmor 
module and the man apparmor profile. Masking apparmor.service only 
prevents profile loading at boot time, but this is why rebooting with 
apparmor.service masked restore man functionality.


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#889618: entry in debian/copyright missing

[Thorsten Alteholz]

Package: flask-login
Version: 0.4.0-2
Severity: serious
thanks

Hi

one of our trainees looked at your package and found that a whole 
directory in the source (docs/_themes) is copyrighted by Armin Ronacher 
and licensed with a 3-clause BSD license.

This whole information is missing from the copyright file.

Thanks!
  Thorsten

Bug#889617: man-db: all man pages fail to display with "command exited with status 4"

[Ben Caradoc-Davies]

Rebooting restores man page rendering, even with 2.8.0-1, but 
reinstalling causes the bug to reappear.


It looks like root can view man pages but an unprivileged user cannot.

Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#889617: man-db: all man pages fail to display with "command exited with status 4"

[Axel Beckert]

Control: merge 889608 -1

Hi Ben,

thanks for the bug report.

Ben Caradoc-Davies wrote:
> under man-db 2.8.0-1 amd64 all man pages fail to display with:
> 
> $ man man
> man: command exited with status 4: /usr/lib/man-db/zsoelim | /usr/lib/man-
> db/manconv -f UTF-8:ISO-8859-1 -t UTF-8//IGNORE | preconv -e UTF-8 | tbl |
> nroff -mandoc -rLL=184n -rLT=184n -Tutf8

Ben Caradoc-Davies wrote:
> With 2.8.0-1, I see AppArmor messages in the systemd journal for "man man":

This sounds like https://bugs.debian.org/889608 reported only shortly
before your bug report. Hence merging.

Ben Caradoc-Davies wrote:
> And what I would like to know is how the fscking apparmor module got
> loaded in the first place, given that I have the apparmor service
> masked:
> 
> # ls -al /etc/systemd/system/apparmor.service
> lrwxrwxrwx 1 root root 9 Dec  8 11:24
> /etc/systemd/system/apparmor.service -> /dev/null
> 
> Yet:
> 
> # aa-status
> apparmor module is loaded.

You've masked a systemd service. But "module" probably refers to some
kernel module here, which is enabled by default since a while in
Debian Unstable.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Processed: Re: Bug#889617: man-db: all man pages fail to display with "command exited with status 4"

[Debian Bug Tracking System]

Processing control commands:

> merge 889608 -1
Bug #889608 [man-db] man-db: man(1) dumps core (AppArmor involved)
Bug #889617 [man-db] man-db: all man pages fail to display with "command exited 
with status 4"
Merged 889608 889617

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

Bug#889617: man-db: all man pages fail to display with "command exited with status 4"

[Ben Caradoc-Davies]

And what I would like to know is how the fscking apparmor module got 
loaded in the first place, given that I have the apparmor service masked:


# ls -al /etc/systemd/system/apparmor.service
lrwxrwxrwx 1 root root 9 Dec  8 11:24 
/etc/systemd/system/apparmor.service -> /dev/null


Yet:

# aa-status
apparmor module is loaded.
3 profiles are loaded.
3 profiles are in enforce mode.
   /usr/bin/man
   /usr/bin/man//filter
   /usr/bin/man//groff
0 profiles are in complain mode.
0 processes have profiles defined.
0 processes are in enforce mode.
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.

Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#889617: man-db: all man pages fail to display with "command exited with status 4"

[Ben Caradoc-Davies]

With 2.8.0-1, I see AppArmor messages in the systemd journal for "man man":

Feb 05 13:09:30 ripley audit[30186]: AVC apparmor="DENIED" 
operation="exec" info="no new privs" error=-1 profile="/usr/bin/man" 
name="/usr/bin/preconv" pid=30186 comm="man" requested_mask="x" 
denied_mask="x" fsuid=1000 ouid=0 target="/usr/bin/man//groff"
Feb 05 13:09:30 ripley kernel: audit: type=1400 
audit(1517789370.641:103): apparmor="DENIED" operation="exec" info="no 
new privs" error=-1 profile="/usr/bin/man" name="/usr/bin/preconv" 
pid=30186 comm="man" requested_mask="x" denied_mask="x" fsuid=1000 
ouid=0 target="/usr/bin/man//groff"
Feb 05 13:09:30 ripley audit[30187]: AVC apparmor="DENIED" 
operation="exec" info="no new privs" error=-1 profile="/usr/bin/man" 
name="/usr/bin/tbl" pid=30187 comm="man" requested_mask="x" 
denied_mask="x" fsuid=1000 ouid=0 target="/usr/bin/man//groff"
Feb 05 13:09:30 ripley kernel: audit: type=1400 
audit(1517789370.641:104): apparmor="DENIED" operation="exec" info="no 
new privs" error=-1 profile="/usr/bin/man" name="/usr/bin/tbl" pid=30187 
comm="man" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 
target="/usr/bin/man//groff"
Feb 05 13:09:30 ripley audit[30195]: AVC apparmor="DENIED" 
operation="exec" info="no new privs" error=-1 profile="/usr/bin/man" 
name="/usr/bin/troff" pid=30195 comm="groff" requested_mask="x" 
denied_mask="x" fsuid=1000 ouid=0 target="/usr/bin/man//groff"
Feb 05 13:09:30 ripley kernel: audit: type=1400 
audit(1517789370.645:105): apparmor="DENIED" operation="exec" info="no 
new privs" error=-1 profile="/usr/bin/man" name="/usr/bin/troff" 
pid=30195 comm="groff" requested_mask="x" denied_mask="x" fsuid=1000 
ouid=0 target="/usr/bin/man//groff"


With 2.7.6.1-4+b1, there are no messages.

Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#889617: man-db: all man pages fail to display with "command exited with status 4"

[Ben Caradoc-Davies]

Package: man-db
Version: 2.8.0-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

under man-db 2.8.0-1 amd64 all man pages fail to display with:

$ man man
man: command exited with status 4: /usr/lib/man-db/zsoelim | /usr/lib/man-
db/manconv -f UTF-8:ISO-8859-1 -t UTF-8//IGNORE | preconv -e UTF-8 | tbl |
nroff -mandoc -rLL=184n -rLT=184n -Tutf8

(Where "all" means all those I tested including "man", "ls", "tar", "git
commit".)

Workaround is to downgrade man-db to 2.7.6.1-4+b1.

Kind regards,
Ben.



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

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

Versions of packages man-db depends on:
ii  bsdmainutils   11.1.2
ii  debconf [debconf-2.0]  1.5.65
ii  dpkg   1.19.0.5
ii  groff-base 1.22.3-9
ii  libc6  2.26-6
ii  libgdbm5   1.14.1-2
ii  libpipeline1   1.5.0-1
ii  libseccomp22.3.1-2.1
ii  zlib1g 1:1.2.8.dfsg-5

man-db recommends no packages.

Versions of packages man-db suggests:
ii  apparmor2.12-2
ii  firefox [www-browser]   58.0.1-1
ii  google-chrome-stable [www-browser]  64.0.3282.140-1
pn  groff   
ii  less487-0.1

-- debconf information:
  man-db/auto-update: true
  man-db/install-setuid: false

Bug#889608: man-db: man(1) dumps core (AppArmor involved)

[gregor herrmann]

On Sun, 04 Feb 2018 23:32:38 +, Colin Watson wrote:

> On Sun, Feb 04, 2018 at 11:42:57PM +0100, gregor herrmann wrote:
> > Since the upgrade to 2.8.0-1, man(1) is not really cooperative:
> Does MAN_DISABLE_SECCOMP=1 help?  

Yes, `MAN_DISABLE_SECCOMP=1 man man' just works.

> I may have made the mistake of only
> trying this with the kernel in Ubuntu 16.04, which I suspect is relevant
> here ...

In case it matters, I'm not yet running the latest kernel from
unstable (reboot missing) but linux-image-4.14.0-3-amd64 / 4.14.12-2 

Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#889615: python-tifffile: broken autopkgtest, broken package

[Steve Langasek]

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

Dear Andreas,

Since the upload of tifffile 20170914-1, the autopkgtests for this package
hav been consistently failing in both Debian and Ubuntu.  While the test
failure is (unfortunately) not considered a blocker for Debian testing,
autopkgtest regressions are blockers for Ubuntu releases.

The failure shows that the module simply fails a python import test,
indicating that the package has missing dependencies; therefore I am marking
this bug 'serious'.

autopkgtest [19:30:42]: test python-import: [---
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.1pxu7uus/downtmp/build.LXT/src/debian/tests/python-import",
 line 5, in 
import tifffile
  File "/usr/lib/python2.7/dist-packages/tifffile.py", line 313, in 
import enum
ImportError: No module named enum
autopkgtest [19:30:42]: test python-import: ---]
autopkgtest [19:30:42]: test python-import:  - - - - - - - - - - results - - - 
- - - - - - -
python-importFAIL non-zero exit status 1

  https://ci.debian.net/packages/t/tifffile/unstable/amd64/

After installing the python-enum34 package, the autopkgtest still fails with
another import error about concurrent.futures (package:
python-concurrent.futures).

And if all of these undeclared dependencies are installed, the test still
fails:

$ ./debian/tests/python-import 
2017.09.14
Traceback (most recent call last):
  File "./debian/tests/python-import", line 16, in 
for page in tif:
TypeError: 'TiffFile' object is not iterable
$

This part looks like it might be a bug in the test rather than the package,
but without being familiar with the package it's hard for me to know.

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


signature.asc
Description: PGP signature

Processed: Re: Bug#889608: man-db: man(1) dumps core (AppArmor involved)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #889608 [man-db] man-db: man(1) dumps core (AppArmor involved)
Severity set to 'grave' from 'important'

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

Bug#889545: marked as done (libopenmpt0: CVE-2018-6611)

[Debian Bug Tracking System]

Your message dated Sun, 04 Feb 2018 23:21:35 +
with message-id 
and subject line Bug#889545: fixed in libopenmpt 0.3.6-1
has caused the Debian Bug report #889545,
regarding libopenmpt0: CVE-2018-6611
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.)


-- 
889545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889545
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libopenmpt0
Version: 0.3.1-1
Severity: grave
Tags: security

This security update was published for libopenmpt:
https://lib.openmpt.org/libopenmpt/2018/02/03/security-update-0.3.6/

> The OpenMPT/libopenmpt project released the latest stable libopenmpt version:
> 
> libopenmpt 0.3.6 (2018-02-03)
> [Sec] Possible out-of-bounds memory read with malformed STP files. (r9576)

The bug only affects 0.3.x so it will not require any updates to stable.

I have requested a CVE for this bug.

Thanks,
James



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: libopenmpt
Source-Version: 0.3.6-1

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

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

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

Debian distribution maintenance software
pp.
James Cowgill  (supplier of updated libopenmpt package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 04 Feb 2018 23:09:22 +
Source: libopenmpt
Binary: openmpt123 libopenmpt0 libopenmpt-dev libopenmpt-doc 
libopenmpt-modplug1 libopenmpt-modplug-dev
Architecture: source
Version: 0.3.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: James Cowgill 
Description:
 libopenmpt-dev - module music library based on OpenMPT -- development files
 libopenmpt-doc - module music library based on OpenMPT -- documentation
 libopenmpt-modplug-dev - module music library based on OpenMPT -- modplug 
compat developme
 libopenmpt-modplug1 - module music library based on OpenMPT -- modplug compat 
library
 libopenmpt0 - module music library based on OpenMPT -- shared library
 openmpt123 - module music library based on OpenMPT -- music player
Closes: 889545
Changes:
 libopenmpt (0.3.6-1) unstable; urgency=medium
 .
   * New upstream release.
 - Fixes CVE-2018-6611 (Closes: #889545).
 .
   * debian/copyright:
 - Update dates.
   * debian/compat:
 - Use debhelper 11.
   * debian/control:
 - Set Maintainer to debian-multimedia@lists.d.o.
 - Switch Vcs URLs to salsa.debian.org.
 - Bump standards version to 4.1.3.
   * debian/rules:
 - Revert workaround implementing build targets manually now that debhelper
   has been fixed.
Checksums-Sha1:
 68605b76b113269e8fed7af312497e83ca43527e 2589 libopenmpt_0.3.6-1.dsc
 00041fe8ee777399316b09541fd2c713c920df05 1409983 libopenmpt_0.3.6.orig.tar.gz
 9fe2f103619cf614735525a479b56d4ab9970248 12336 libopenmpt_0.3.6-1.debian.tar.xz
 ce073b32776655b0337b2fc8889ae072a28e89f2 5767 
libopenmpt_0.3.6-1_source.buildinfo
Checksums-Sha256:
 3e9131101540793a44323aef4bc146dccd608ace202245b0032552c098f64da6 2589 
libopenmpt_0.3.6-1.dsc
 0a49e4770c9c7778cd6544ad559bff873ec905c4a3ba6521f6bf192b1c0b34d2 1409983 
libopenmpt_0.3.6.orig.tar.gz
 74d9634433a10c335be3ce612657dc4bc0bf26647e1f521edd0c0e7dde27821c 12336 
libopenmpt_0.3.6-1.debian.tar.xz
 6567d654392112b261cdadf93658ce8ffb5aee91fea421a199fb923662c6cbe5 5767 
libopenmpt_0.3.6-1_source.buildinfo
Files:
 e89ebf3226d8d7e6bb443df8bef08c29 2589 libs optional libopenmpt_0.3.6-1.dsc
 f8159da38cbbecdae3792ec4d3a535e6 1409983 libs optional 
libopenmpt_0.3.6.orig.tar.gz
 1a9bf4b251466a1dbf4c06cc1fc9d467 12336 libs optional 
libopenmpt_0.3.6-1.debian.tar.xz
 c40de97af42275fcfdeda578dc61fbc1 5767 libs optional 
libopenmpt_0.3.6-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE+Ixt5DaZ6POztUwQx/FnbeotAe8FAlp3k9IUHGpjb3dnaWxs
QGRlYmlhbi5vcmcACgkQx/FnbeotAe9d/g/8C7T90UdGfOtTJo6qyT7+zwQRKOBt
bjfCg51K6GywX3CKh9aDmdsuySI/fyFTSl47g1+JXkcJMko0O7QA9/8uD98BXXQw

Bug#887618: marked as done (libgetfem++-dev: needs Depends: libgmm++-dev (= ${source:Version}))

[Debian Bug Tracking System]

Your message dated Sun, 04 Feb 2018 23:20:53 +
with message-id 
and subject line Bug#887618: fixed in getfem++ 5.2+dfsg1-6
has caused the Debian Bug report #887618,
regarding libgetfem++-dev: needs Depends: libgmm++-dev (= ${source:Version})
to be marked as done.

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

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


-- 
887618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887618
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgetfem++-dev
Version: 5.2+dfsg1-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable.
Since libgmm++-dev is an arch:all package, the (= ${binary:Version}) is
incorrect and no longer satisfiable after the recent binNMU.

Andreas
--- End Message ---
--- Begin Message ---
Source: getfem++
Source-Version: 5.2+dfsg1-6

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

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

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated getfem++ package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 04 Feb 2018 19:03:14 +0100
Source: getfem++
Binary: libgetfem++-dev libgetfem5++ libgmm++-dev python-getfem++
Architecture: source
Version: 5.2+dfsg1-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Anton Gladky 
Description:
 libgetfem++-dev - Development files for the GETFEM++ generic finite element 
library
 libgetfem5++ - GETFEM++ generic finite element library
 libgmm++-dev - Generic C++ template library for sparse, dense and skyline 
matric
 python-getfem++ - Python interface to the GETFEM++ generic finite element 
library
Closes: 887618
Changes:
 getfem++ (5.2+dfsg1-6) unstable; urgency=medium
 .
   * Team upload.
   * [7f95df8] Use (= ${source:Version}) for the libgmm++-dev. (Closes: #887618)
   * [8197c7b] Bump Standards-Version: 4.1.3
   * [e5c6cd0] Switch to compat-level 11
   * [0d4f384] Remove myself from uploaders
   * [432ed30] Remove testsuite-field in the d/control
Checksums-Sha1:
 c67f3e4c10ddac0ffcac0b169b93630608a36bba 2409 getfem++_5.2+dfsg1-6.dsc
 7ac66bd7e053e0266f7361c9daadf3790b3d862b 17696 
getfem++_5.2+dfsg1-6.debian.tar.xz
 7241f9f465ad21c52bd4cc4b4c6f2d50fab93e9e 12287 
getfem++_5.2+dfsg1-6_source.buildinfo
Checksums-Sha256:
 703aeac54b9cae609facc9f2094fd9dd2cfac5aeee8669ca7a6819dcd467dcff 2409 
getfem++_5.2+dfsg1-6.dsc
 cf30762141d6b7d5da91d84bfa1f65f2c76ad979d473cd4944e0307a1164c03a 17696 
getfem++_5.2+dfsg1-6.debian.tar.xz
 985eb416e30cc6c49b56966590cb9d0620b34757fbdd9f7d5163307211d4b0a0 12287 
getfem++_5.2+dfsg1-6_source.buildinfo
Files:
 6ef9f25e8a7fce153aaf8fd57494866b 2409 libs optional getfem++_5.2+dfsg1-6.dsc
 5dc5e2778395acfbd0a3a8423942326e 17696 libs optional 
getfem++_5.2+dfsg1-6.debian.tar.xz
 825b8d6e643c00a58021057e1c3caa8a 12287 libs optional 
getfem++_5.2+dfsg1-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAlp3jX0ACgkQ0+Fzg8+n
/waExw//ezGTB3erGFr4PrsIbku/xjlPFLElL0WY90ffhLMVG7PQtZ1x8cAoMRKB
uwedkhyvMrui4p96FBuEVEHAIRDt+lkxS7j8hoaQKRc55WECE4BcYEYq2OiEsmRu
2Kgpdq7OZ2sUj2bhIP+qWcgHyIkgjPKak4zWF4l/WEGL2jeJe8RBIsbyL26gufgA
iepVXOVlxEAbx5NNUsq1A9xXWrQ9rHMqxuS/Q0Izh/277fa+3j9NaVFmmPDmdjwQ
MIUuV1PhLdTdD0H1qv8jXCoy7ESNn80rBpkd9JSCPLxxg2cwB1ooCAFIBhfGCdSy
ErraJ8A4HaJTKsU8rMULGlqay8hAKrsuILTtdllyRwr0zHFFnFkMGqDdkoLgeUnd
2AMEKckg1ahlv7sicAYDBSViup9QNEVrfBhK6GPI2BW66poq+5xJZB7yP98ho5VA
zeYS19f8c7Y84pOtydQ8cAfB3WJcPY9nRIX62AElStH5wBPsEYh1hrRMzQqh5B65
rlNt4p0GCZsonDGM+e/xS/60eN4pqqKkWX6MU3PhFf4Jp6VRXdS5WGks7FqJgawQ
IdMb0utuItjomKmpZ+SXXtl5GOSLii0LccPeUkCuQe+p4R+UJ5e+T75aA6cauSx/
S5B8xjSYY287kgEp2SC2xNKZ0rysaUzSC+RTf2gpR9nxHkRlDnc=
=zZOg
-END PGP SIGNATURE End Message ---

Bug#889610: tesseract-ocr-srp-latn: uninstallable in sid: Depends: tesseract-srp (>= 3.99) which is unknown

[Andreas Beckmann]

Package: tesseract-ocr-srp-latn
Version: 4.00~git15-45ed289-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable in sid:

The following packages have unmet dependencies:
 tesseract-ocr-srp-latn : Depends: tesseract-srp (>= 3.99) which is a virtual 
package and is not provided by any available package


Cheers,

Andreas

Bug#889609: moonshot-gss-eap: uninstallable in sid: libgssapi-krb5-2 : Breaks: moonshot-gss-eap (<= 1.0) but 0.9.5-3+b1 is to be installed

[Andreas Beckmann]

Package: moonshot-gss-eap
Version: 0.9.5-3
Severity: serious
Tags: sid
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable in sid:

The following packages have unmet dependencies:
 libgssapi-krb5-2 : Breaks: moonshot-gss-eap (<= 1.0) but 0.9.5-3+b1 is to be 
installed

This can probably be fixed by migrating the packages from experimental
to sid ...


Cheers,

Andreas

Bug#889144: stricter PIDfile handling breaks several daemons

[Simon Kelley]

On 04/02/18 20:26, Sven Hartge wrote:

> Does dnsmasq need a PIDfile when running under systemd? Can't it just
> not double fork, stay in the foreground using a Type=simple systemd unit?
> 
> That way the whole problem could be avoided all together.
> 

Sending signals to the dnsmasq process cause it to take various actions,
so it's likely that there are scripts out there that do the equivalent of

kill - `cat /run/dnsmasq/dnsmasq.pid`

The double-fork code in dnsmasq is also quite careful about error
handling; for instance passing an error code back through a pipe from
the forked process to the original process, so that any failure gets
reflected in the return code when the original process exits. That's
relevant to Michael's point, I think.

Cheers,

Simon.

Processed: bug 886833 is forwarded to https://bugs.launchpad.net/debian/+source/gweled/+bug/1741664

[Debian Bug Tracking System]

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

> forwarded 886833 https://bugs.launchpad.net/debian/+source/gweled/+bug/1741664
Bug #886833 [gweled] [gweled] Not compatable with recent gtk
Set Bug forwarded-to-address to 
'https://bugs.launchpad.net/debian/+source/gweled/+bug/1741664'.
> thanks
Stopping processing here.

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

Bug#889598: plasma-desktop: FTBFS problems finding AppStreamQt

[Andreas Beckmann]

On 2018-02-04 23:02, Matthias Klumpp wrote:
> This bug was fixed in appstream quite a while ago, looking at the full
> buildlog one can see that an old version of the appstream package was
> used for building. Therefore, I think this bug can be closed. If the
> issue persists with the version of AppStream that is currently in
> testing/unstable, please reopen the issue (ideally with a fresh build
> log).
> See issue #888144 for details on the original bug.

Aargh, missed to reschedule this build yesterday and filed the bug for
the "persistent" problem today without checking build log date ...

Sorry for the noise.

Andreas

Bug#889606: mupen64plus-video-glide64mk2: uninstallable in sid: virtual package libtxc-dxtn0 is no longer provided

[Andreas Beckmann]

Package: mupen64plus-video-glide64mk2
Version: 2.5-4
Severity: serious
Tags: sid buster
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable in sid:

The following packages have unmet dependencies:
 mupen64plus-video-glide64mk2 : Depends: libtxc-dxtn0 but it is not installable

libtxc-dxtn0 was provided by libtxc-dxtn-s2tc which has been
removed from sid.


Cheers,

Andreas

Bug#889598: marked as done (plasma-desktop: FTBFS problems finding AppStreamQt)

[Debian Bug Tracking System]

Your message dated Sun, 4 Feb 2018 23:02:10 +0100
with message-id 

and subject line Re: Bug#889598: plasma-desktop: FTBFS problems finding 
AppStreamQt
has caused the Debian Bug report #889598,
regarding plasma-desktop: FTBFS problems finding AppStreamQt
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.)


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

Hi,

plasma-desktop/experimental recently started to FTBFS:

from the attached buidlog:

[...]
-- The following RECOMMENDED packages have been found:

 * AppStreamQt (required version >= 0.10.4), Appstream integration
   Needed to allow appstream integration from application menus
 * KF5Baloo (required version >= 5.15), File Searching
   Needed to build the File Search KCM
[...]
[ 37%] Linking CXX shared library libkickerplugin.so
cd /build/plasma-desktop-5.11.4/obj-x86_64-linux-gnu/applets/kicker && 
/usr/bin/cmake -E cmake_link_script CMakeFiles/kickerplugin.dir/link.txt 
--verbose=1
/usr/bin/c++ -fPIC -g -O2 -fdebug-prefix-map=/build/plasma-desktop-5.11.4=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=c++0x -fno-operator-names -fno-exceptions -Wall 
-Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long 
-Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual 
-Werror=return-type -Wvla -Wdate-time -Wl,--no-undefined -Wl,--fatal-warnings 
-Wl,--enable-new-dtags -Wl,-z,relro -shared -Wl,-soname,libkickerplugin.so -o 
libkickerplugin.so CMakeFiles/kickerplugin.dir/plugin/abstractentry.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/abstractmodel.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/actionlist.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/appentry.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/appsmodel.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/computermodel.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/contactentry.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/containmentinterface.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/draghelper.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/simplefavoritesmodel.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/kastatsfavoritesmodel.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/fileentry.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/forwardingmodel.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/placeholdermodel.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/funnelmodel.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/dashboardwindow.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/kickerplugin.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/menuentryeditor.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/processrunner.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/rootmodel.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/runnermodel.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/runnermatchesmodel.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/recentcontactsmodel.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/recentusagemodel.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/submenu.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/systementry.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/systemmodel.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/systemsettings.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/wheelinterceptor.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/windowsystem.cpp.o 
CMakeFiles/kickerplugin.dir/krunner_interface.cpp.o 
CMakeFiles/kickerplugin.dir/ksmserver_interface.cpp.o 
CMakeFiles/kickerplugin.dir/kickerplugin_autogen/mocs_compilation.cpp.o 
/usr/lib/x86_64-linux-gnu/libKF5ActivitiesStats.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5ItemModels.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5KDELibs4Support.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5PeopleWidgets.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5PlasmaQuick.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5Runner.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libkworkspace5.so.5.10.5 AppStreamQt-NOTFOUND 
/usr/lib/x86_64-linux-gnu/libKF5Activities.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5Crash.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5KIOFileWidgets.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5Bookmarks.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5UnitConversion.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5Parts.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5People.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5Solid.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5Plasma.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5Notifications.so.5.41.0 

Bug#889602: python-cloudkitty: uninstallable in sid: Depends: python-sqlalchemy (< 1.1.0) but 1.1.11+ds1-1 is to be installed

[Andreas Beckmann]

Package: python-cloudkitty
Version: 6.0.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is not
installable in sid:

The following packages have unmet dependencies:
 python-cloudkitty : Depends: python-sqlalchemy (< 1.1.0) but 1.1.11+ds1-1 is 
to be installed


Cheers,

Andreas

Bug#889144: stricter PIDfile handling breaks several daemons

[Michael Biebl]

Am 04.02.2018 um 21:26 schrieb Sven Hartge:
> On Sun, 4 Feb 2018 15:41:37 + Simon Kelley 
> wrote:
> 
>> With my dnsmasq maintainer hat on, the current arrangement looks like this.
>>
>> 1) /run/dnsmasq is a directory owned by dnsmasq:nogroup
>> 2) /run/dnsmasq/dnsmasq.pid gets written by dnsmasq before it drops
>> root, so is root:root
>> 3) The reason /run/dnsmasq is owned by dnsmasq is so that dnsmasq can
>> unlink the pidfile at shutdown, after it has dropped root and is running
>> as 'dnsmasq'
> 
> Does dnsmasq need a PIDfile when running under systemd? Can't it just
> not double fork, stay in the foreground using a Type=simple systemd unit?
> 
> That way the whole problem could be avoided all together.

If other services depend on dnsmasq, please keep
https://www.lucas-nussbaum.net/blog/?p=877 in mind




-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#889598: plasma-desktop: FTBFS problems finding AppStreamQt

[Andreas Beckmann]

Source: plasma-desktop
Version: 4:5.11.4-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

plasma-desktop/experimental recently started to FTBFS:

from the attached buidlog:

[...]
-- The following RECOMMENDED packages have been found:

 * AppStreamQt (required version >= 0.10.4), Appstream integration
   Needed to allow appstream integration from application menus
 * KF5Baloo (required version >= 5.15), File Searching
   Needed to build the File Search KCM
[...]
[ 37%] Linking CXX shared library libkickerplugin.so
cd /build/plasma-desktop-5.11.4/obj-x86_64-linux-gnu/applets/kicker && 
/usr/bin/cmake -E cmake_link_script CMakeFiles/kickerplugin.dir/link.txt 
--verbose=1
/usr/bin/c++ -fPIC -g -O2 -fdebug-prefix-map=/build/plasma-desktop-5.11.4=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=c++0x -fno-operator-names -fno-exceptions -Wall 
-Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long 
-Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual 
-Werror=return-type -Wvla -Wdate-time -Wl,--no-undefined -Wl,--fatal-warnings 
-Wl,--enable-new-dtags -Wl,-z,relro -shared -Wl,-soname,libkickerplugin.so -o 
libkickerplugin.so CMakeFiles/kickerplugin.dir/plugin/abstractentry.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/abstractmodel.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/actionlist.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/appentry.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/appsmodel.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/computermodel.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/contactentry.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/containmentinterface.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/draghelper.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/simplefavoritesmodel.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/kastatsfavoritesmodel.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/fileentry.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/forwardingmodel.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/placeholdermodel.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/funnelmodel.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/dashboardwindow.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/kickerplugin.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/menuentryeditor.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/processrunner.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/rootmodel.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/runnermodel.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/runnermatchesmodel.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/recentcontactsmodel.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/recentusagemodel.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/submenu.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/systementry.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/systemmodel.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/systemsettings.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/wheelinterceptor.cpp.o 
CMakeFiles/kickerplugin.dir/plugin/windowsystem.cpp.o 
CMakeFiles/kickerplugin.dir/krunner_interface.cpp.o 
CMakeFiles/kickerplugin.dir/ksmserver_interface.cpp.o 
CMakeFiles/kickerplugin.dir/kickerplugin_autogen/mocs_compilation.cpp.o 
/usr/lib/x86_64-linux-gnu/libKF5ActivitiesStats.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5ItemModels.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5KDELibs4Support.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5PeopleWidgets.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5PlasmaQuick.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5Runner.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libkworkspace5.so.5.10.5 AppStreamQt-NOTFOUND 
/usr/lib/x86_64-linux-gnu/libKF5Activities.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5Crash.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5KIOFileWidgets.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5Bookmarks.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5UnitConversion.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5Parts.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5People.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5Solid.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5Plasma.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5Notifications.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libQt5PrintSupport.so.5.9.2 
/usr/lib/x86_64-linux-gnu/libKF5TextWidgets.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5SonnetUi.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5.9.2 
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5.9.2 
/usr/lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5Service.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5WindowSystem.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libQt5Network.so.5.9.2 
/usr/lib/x86_64-linux-gnu/libKF5Completion.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5JobWidgets.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5IconThemes.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5ConfigWidgets.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5WidgetsAddons.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5GuiAddons.so.5.41.0 

Bug#889597: libtirpc: FTBFS: xdr_sizeof.c:93:13: error: 'uintptr_t' undeclared

[Andreas Beckmann]

Source: libtirpc
Version: 1.0.2-0.2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

libtirpc/experimental recently started to FTBFS:

/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..  
-I../tirpc -include config.h -DPORTMAP -DINET6 -D_GNU_SOURCE -Wall -pipe 
-Wdate-time -D_FORTIFY_SOURCE=2 -DHAVE_RPCSEC_GSS -isystem /us
r/include/mit-krb5 -g -O2 -fdebug-prefix-map=/build/libtirpc-1.0.2=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o 
libtirpc_la-xdr_sizeof.lo `test -f 'xdr_sizeof.c' || echo './'`xdr_sizeof.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I../tirpc -include config.h 
-DPORTMAP -DINET6 -D_GNU_SOURCE -Wall -pipe -Wdate-time -D_FORTIFY_SOURCE=2 
-DHAVE_RPCSEC_GSS -isystem /usr/include/mit-krb5 -g -O2 -fde
bug-prefix-map=/build/libtirpc-1.0.2=. -fstack-protector-strong -Wformat 
-Werror=format-security -c xdr_sizeof.c  -fPIC -DPIC -o 
.libs/libtirpc_la-xdr_sizeof.o
xdr_sizeof.c: In function 'x_inline':
xdr_sizeof.c:93:13: error: 'uintptr_t' undeclared (first use in this function); 
did you mean '__intptr_t'?
  if (len < (uintptr_t)xdrs->x_base) {
 ^
 __intptr_t
xdr_sizeof.c:93:13: note: each undeclared identifier is reported only once for 
each function it appears in
xdr_sizeof.c:93:23: error: expected ')' before 'xdrs'
  if (len < (uintptr_t)xdrs->x_base) {
   ^~~~
xdr_sizeof.c:105:38: error: expected ';' before 'len'
   xdrs->x_base = (caddr_t)(uintptr_t)len;
  ^~~
xdr_sizeof.c:109:1: warning: control reaches end of non-void function 
[-Wreturn-type]
 }
 ^
Makefile:977: recipe for target 'libtirpc_la-xdr_sizeof.lo' failed
make[3]: *** [libtirpc_la-xdr_sizeof.lo] Error 1


Andreas


libtirpc_1.0.2-0.2.log.gz
Description: application/gzip

Bug#889139: marked as done (telegram-desktop FTBFS on mips/mipsel: Memory exhausted)

[Debian Bug Tracking System]

Your message dated Sun, 04 Feb 2018 21:08:36 +
with message-id 
and subject line Bug#889139: fixed in telegram-desktop 1.2.6-2
has caused the Debian Bug report #889139,
regarding telegram-desktop FTBFS on mips/mipsel: Memory exhausted
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.)


-- 
889139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889139
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: telegram-desktop
Version: 1.2.6-1
Severity: serious
Tags: patch

https://buildd.debian.org/status/package.php?p=telegram-desktop=sid

...
/usr/bin/c++  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -flto 
-Werror=invalid-pch -Wdate-time -D_FORTIFY_SOURCE=2 -DDEBIAN_API_ID 
-DRPL_CONSUMER_TYPE_ERASED_ALWAYS -DTDESKTOP_DISABLE_AUTOUPDATE 
-DTDESKTOP_DISABLE_CRASH_REPORTS -DTDESKTOP_DISABLE_REGISTER_CUSTOM_SCHEME  
-Wl,-z,relro -Wl,-z,now -flto -rdynamic -Wl,--no-as-needed,-lrt -pthread 
-rdynamic  
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/base/observer.o 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/base/parse_helper.o
 CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/base/qthelp_url.o 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/base/runtime_composer.o
 CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/base/task_queue.o 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/base/timer.o 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/boxes/peers/edit_peer_info_box.o
 CMakeFiles/Tel
 egram.dir/<>/Telegram/SourceFiles/boxes/peers/manage_peer_box.o 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/boxes/about_box.o 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/boxes/abstract_box.o
 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/boxes/add_contact_box.o
 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/boxes/autolock_box.o
 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/boxes/background_box.o
 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/boxes/calendar_box.o
 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/boxes/change_phone_box.o
 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/boxes/confirm_box.o
 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/boxes/confirm_phone_box.o
 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/boxes/connection_box.o
 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/boxes/download_path_box.o
 C
 
MakeFiles/Telegram.dir/<>/Telegram/SourceFiles/boxes/edit_caption_box.o
 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/boxes/edit_color_box.o
 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/boxes/edit_participant_box.o
 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/boxes/edit_privacy_box.o
 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/boxes/language_box.o
 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/boxes/local_storage_box.o
 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/boxes/mute_settings_box.o
 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/boxes/notifications_box.o
 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/boxes/peer_list_box.o
 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/boxes/peer_list_controllers.o
 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/boxes/passcode_box.o
 CMakeFiles/Telegram.dir/<>/Telegram/Sour
 ceFiles/boxes/photo_crop_box.o 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/boxes/rate_call_box.o
 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/boxes/report_box.o 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/boxes/self_destruction_box.o
 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/boxes/send_files_box.o
 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/boxes/sessions_box.o
 CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/boxes/share_box.o 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/boxes/sticker_set_box.o
 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/boxes/stickers_box.o
 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/boxes/username_box.o
 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/calls/calls_box_controller.o
 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/calls/calls_call.o 
CMakeFiles/Telegram.dir/<>/Telegram/
 SourceFiles/calls/calls_emoji_fingerprint.o 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/calls/calls_instance.o
 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/calls/calls_panel.o
 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/calls/calls_top_bar.o
 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/chat_helpers/bot_keyboard.o
 
CMakeFiles/Telegram.dir/<>/Telegram/SourceFiles/chat_helpers/emoji_list_widget.o
 

Bug#883908: marked as done (missing dependencies)

[Debian Bug Tracking System]

Your message dated Sun, 04 Feb 2018 21:06:11 +
with message-id 
and subject line Bug#883908: fixed in libbluray 1:1.0.2-2
has caused the Debian Bug report #883908,
regarding missing dependencies
to be marked as done.

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

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


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

Package: libbluray-dev
Version: 1:1.0.2-1

the -dev packages needs to depend on other -dev packages:

pkg-config libbluray --cflags
Package libxml-2.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libxml-2.0.pc'
to the PKG_CONFIG_PATH environment variable
Package 'libxml-2.0', required by 'libbluray', not found

pkg-config libbluray --cflags
Package fontconfig was not found in the pkg-config search path.
Perhaps you should add the directory containing `fontconfig.pc'
to the PKG_CONFIG_PATH environment variable
Package 'fontconfig', required by 'libbluray', not found

and probably libfreetype6-dev, although libfontconfig1-dev already 
depends on it
--- End Message ---
--- Begin Message ---
Source: libbluray
Source-Version: 1:1.0.2-2

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

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

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated libbluray 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 04 Feb 2018 21:16:18 +0100
Source: libbluray
Binary: libbluray-dev libbluray2 libbluray-bdj libbluray-bin libbluray-doc
Architecture: source
Version: 1:1.0.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Sebastian Ramacher 
Description:
 libbluray-bdj - Blu-ray Disc Java support library (BD-J library)
 libbluray-bin - Blu-ray disc playback support library (tools)
 libbluray-dev - Blu-ray disc playback support library (development files)
 libbluray-doc - Blu-ray disc playback support library (documentation)
 libbluray2 - Blu-ray disc playback support library (shared library)
Closes: 883908
Changes:
 libbluray (1:1.0.2-2) unstable; urgency=medium
 .
   * debian/control:
 - Bump Standards-Version.
 - Move to salsa.debian.org.
 - Depend on packages referenced by pkg-config file. (Closes: #883908)
   * debian/: Bump debhelper compat to 11.
Checksums-Sha1:
 9b7fcb48b9ace43de5227f415efbbd8ebaed3e0f 2528 libbluray_1.0.2-2.dsc
 50bceb5e397daa6b7c8f628f8ab531d9f7644b0c 16660 libbluray_1.0.2-2.debian.tar.xz
Checksums-Sha256:
 db1ef5bbceca023c690dacfde4be5e5afd1e27446f843eb11fe81ef5b1a6b068 2528 
libbluray_1.0.2-2.dsc
 d443bf2a01319da1153f376d9c17aa3937f7714c485795239103e0516c0c7e0f 16660 
libbluray_1.0.2-2.debian.tar.xz
Files:
 f06f756e668441d68a322bb0d77b2eb5 2528 libs optional libbluray_1.0.2-2.dsc
 88a61037cab08981539654d3d96ee2a4 16660 libs optional 
libbluray_1.0.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAlp3at8ACgkQafL8UW6n
GZMcnA/+LIr7UzrNafkan7FZEnasnEOnN9d8V4G93gfGzBj9hNwc4cUFsOup/JtD
CjmYbvlFWYtwiEOQ7qTJotwj1koxqWM4QPXDovo81EgP8KrNreVf0g9S5v1Ww5h4
2PfyQvOtPeLn66AsaBFStRSkWMM98ATW+Oocwren6+dDqI4zLWd8mCtCg1GGxPF8
aoIsM6itJw77LWgFgLZorJFqdegWZQnx7JBAzHa2bsc3yBORKXfhQnBccoZv1XqB
/ZrLO7CZZ0ldUa9aJbNCvKAl3ZDpHCnbXBYMbuJ9E5u2wg5BLnJDThnZuGnb+Bmk
L8gK9OYaFkdxyfhNm0Q35McxyHDadaIz1UmEhPJZiO3BVlbXT1AAvZJPbNvAOrUg
fH5gEuLskMLEbz1wYqAzsq0agAv/fpgf2dJVRqNW/ILcBD4176yNWr6q82Ohr1Lp
MPFnp8wnwpNKnnKEedx9Y0V2qx26k5CU/vvOHjwRbUmAK4LTxkcoT7CBl3c4TK+b
01LQy09+l1XW0DS5g81kk+RoAa2DCfWDKz7ppSGm5hXipsTUOpqBl+i+btmPhsUK
8wurcUGGGu3hUTIgczfmhnfccPUrE38OBrW4VRpIkc5oAqrt49yP8e4xengNGNfT
0j+fDwpXsqUxXY8vgClyTegrWxN6ED5VteuI1seh7OtX9/5VVaA=
=VBkf
-END PGP SIGNATURE End Message ---

Bug#886164: marked as done (libspring-java: FTBFS MockServerContainer.java method does not override or implement a method from a supertype)

[Debian Bug Tracking System]

Your message dated Sun, 04 Feb 2018 21:06:55 +
with message-id 
and subject line Bug#886164: fixed in libspring-java 4.3.13-2
has caused the Debian Bug report #886164,
regarding libspring-java: FTBFS MockServerContainer.java method does not 
override or implement a method from a supertype
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.)


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

Source: libspring-java
Version: 4.3.13-1
Severity: serious
Tags: patch

Dear Maintainer,

The package currently fails to build from source with the following 
error message:


All input files are considered out-of-date for incremental task 
':spring-test:compileJava'.

Compiling with JDK Java compiler API.
/build/1st/libspring-java-4.3.13/spring-test/src/main/java/org/springframework/test/context/web/socket/MockServerContainer.java:56: 
warning: [deprecation] setAsyncSendTimeout(long) in WebSocketContainer 
has been deprecated

public void setAsyncSendTimeout(long timeout) {
^
/build/1st/libspring-java-4.3.13/spring-test/src/main/java/org/springframework/test/context/web/socket/MockServerContainer.java:60: 
error: method does not override or implement a method from a supertype

@Override
^
1 error
1 warning
:spring-test:compileJava FAILED

For more details see
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libspring-java.html
I first spotted this issue when the package was synced to Ubuntu, but 
was able to

reproduce it on my Sid system.

The issue itself seems to be related to a method which used to(?) be 
part of an
interface, but is now causing this error. Surprisingly enough, the 
method was
added by one of the Debian patches. The attached patch modifies the 
original
patch a bit and resolves the FTBFS. I must admit I don't have the full 
overview

over what's going on here, so there might be a better way to fix this :)



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

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

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


--
mvh / best regards
Hans Joachim Desserud
http://desserud.orgdiff --git a/debian/patches/0041-servlet-api-compatibility.patch b/debian/patches/0041-servlet-api-compatibility.patch
index 55887129..0f2e3280 100644
--- a/debian/patches/0041-servlet-api-compatibility.patch
+++ b/debian/patches/0041-servlet-api-compatibility.patch
@@ -100,17 +100,3 @@ Forwarded: no
 +		throw new UnsupportedOperationException();
 +	}
  }
 a/spring-test/src/main/java/org/springframework/test/context/web/socket/MockServerContainer.java
-+++ b/spring-test/src/main/java/org/springframework/test/context/web/socket/MockServerContainer.java
-@@ -58,6 +58,11 @@
- 	}
- 
- 	@Override
-+	public void setDefaultAsyncSendTimeout(long timeout) {
-+		this.defaultAsyncSendTimeout = timeout;
-+	}
-+
-+	@Override
- 	public long getDefaultMaxSessionIdleTimeout() {
- 		return this.defaultMaxSessionIdleTimeout;
- 	}
--- End Message ---
--- Begin Message ---
Source: libspring-java
Source-Version: 4.3.13-2

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated libspring-java package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 04 Feb 2018 20:47:33 +0100
Source: libspring-java
Binary: libspring-core-java libspring-beans-java libspring-aop-java 
libspring-context-java libspring-context-support-java libspring-web-java 
libspring-web-servlet-java libspring-web-portlet-java libspring-test-java 
libspring-transaction-java libspring-jdbc-java libspring-messaging-java 
libspring-jms-java libspring-orm-java 

Bug#889537: marked as done (distro-info FTBFS: FAIL: test_pylint (distro_info_test.test_pylint.PylintTestCase))

[Debian Bug Tracking System]

Your message dated Sun, 04 Feb 2018 21:05:08 +
with message-id 
and subject line Bug#889537: fixed in distro-info 0.18
has caused the Debian Bug report #889537,
regarding distro-info FTBFS: FAIL: test_pylint 
(distro_info_test.test_pylint.PylintTestCase)
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.)


-- 
889537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889537
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: distro-info
Version: 0.17
Severity: serious

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

...
==
FAIL: test_pylint (distro_info_test.test_pylint.PylintTestCase)
Test: Run pylint on Python source code
--
Traceback (most recent call last):
  File "/build/1st/distro-info-0.17/python/distro_info_test/test_pylint.py", 
line 52, in test_pylint
self.assertFalse(err, pylint_binary + ' crashed. Error output:\n' + 
err.decode())
AssertionError: pylint crashed. Error output:
Using config file 
/build/1st/distro-info-0.17/python/distro_info_test/pylint.conf


--
Ran 26 tests in 5.776s

FAILED (failures=1)
Test failed: 
error: Test failed: 
Makefile:45: recipe for target 'test-python' failed
make[1]: *** [test-python] Error 1
--- End Message ---
--- Begin Message ---
Source: distro-info
Source-Version: 0.18

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

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

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

Debian distribution maintenance software
pp.
Benjamin Drung  (supplier of updated distro-info package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 04 Feb 2018 20:42:26 +0100
Source: distro-info
Binary: distro-info libdistro-info-perl python-distro-info python3-distro-info
Architecture: source
Version: 0.18
Distribution: unstable
Urgency: medium
Maintainer: Benjamin Drung 
Changed-By: Benjamin Drung 
Description:
 distro-info - provides information about the distributions' releases
 libdistro-info-perl - information about distributions' releases (Perl module)
 python-distro-info - information about distributions' releases (Python module)
 python3-distro-info - information about distributions' releases (Python 3 
module)
Closes: 889537
Changes:
 distro-info (0.18) unstable; urgency=medium
 .
   * Update Python unittests to support pylint 1.8 (Closes: #889537)
   * Bump debhelper to version 11
   * Bump Standards-Version to 4.1.3 (no changes needed)
   * Update copyright year and format spec URL to https
Checksums-Sha1:
 3fe41578b489fec40302c3e65e6e793b124d4037 1984 distro-info_0.18.dsc
 be4fdd138df6b6c3088a59fd5f82ccbd905eeb30 28196 distro-info_0.18.tar.xz
 de82a17816005ee9b2ab57fcd8803fc8ccb090fc 8129 distro-info_0.18_source.buildinfo
Checksums-Sha256:
 bffec36cacc62fdd320f0f4ebea46a00a95f2a72e352bcdfab64276fa839412d 1984 
distro-info_0.18.dsc
 ab5d0a7c3b0c54328997d5a9376f12232514a650ca69a03594cbb9f51793e431 28196 
distro-info_0.18.tar.xz
 f23cc166f3b68c49a9345aa5ee2598c2640525a61a573abe1a0a8404985d 8129 
distro-info_0.18_source.buildinfo
Files:
 f7071f8a0095dce5014f797eb74b07c6 1984 devel optional distro-info_0.18.dsc
 bf0d5bfe5018e1f1b489ad92cb584e17 28196 devel optional distro-info_0.18.tar.xz
 e2a3fb1353ed40db8f4f6bbffda061d9 8129 devel optional 
distro-info_0.18_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJad2O4AAoJEBWetcTvyHdMoSsP/1yB9Orhm4/ANkSFqYQRFZK1
hdTZ9Ng2RJXC8qPuGARx9uFor+yY4D78nZCo9ZzTbO08wxjJxIuDvnLYd9/a7NIr
ShXLJdQWIK+vyaZ6365tlb5akL3l4D6m8IuyEjG3DFPxXT9bTgJ689j0b/bE4Mh0
T9y3rVtnFayRVNQNQYE4hBF6N3q5iLjtdyYtJwNtlzTFnzbDRHNNYPpCU9JmG8vf
CS5i3NMTrA9Z7fpgK55L20XxZ5N4gr/K/6dj8gR40Vil9M7E1Ox2pAb+l1OUI34H
U1cTdgMmKEhIaZOQRMHSWw9BBhonDQIPFFhQVYryft7GTKUpX5MPM1RJc2kIqkBo
G9SdMa03+oVKbRaved0KV2StJaY2uo/8XaXDdcmZgRYop58dfpGEQPqjqVG8i2ZJ

Bug#889528: marked as done (libbluray-dev: missing dependencies on libxml, freetype, and fontconfig)

[Debian Bug Tracking System]

Your message dated Sun, 04 Feb 2018 21:06:11 +
with message-id 
and subject line Bug#883908: fixed in libbluray 1:1.0.2-2
has caused the Debian Bug report #883908,
regarding libbluray-dev: missing dependencies on libxml, freetype, and 
fontconfig
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.)


-- 
883908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883908
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mpv
Version: 0.27.0-3
Severity: important

Dear Maintainer,

I am using smplayer to read blurays - choosen multimedia engine is mpv - but it
fails with following message :

Playing: br:media/toto/cdrom0
No protocol handler found to open URL br:media/toto/cdrom0
The protocol is either unsupported, or was disabled at compile-time.


If I choose mplayer as multimedia  engine - inside smplayer options - it
works flawlessly. The same with vlc, no problems with reading blurays

Regards


-- System Information:
Debian Release: buster/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages mpv depends on:
ii  libasound2  1.1.3-5
ii  libass9 1:0.14.0-1
ii  libavcodec577:3.4.1-1+b2
pn  libavdevice57   
pn  libavfilter6 | libavfilter-extra6   
pn  libavformat57   
pn  libavutil55 
ii  libc6   2.26-6
ii  libcaca00.99.beta19-2+b2
ii  libcdio-cdda2   10.2+0.94+2-2+b1
ii  libcdio-paranoia2   10.2+0.94+2-2+b1
ii  libcdio17   1.0.0-2
ii  libdrm2 2.4.89-1
ii  libdvdnav4  6.0.0-1
ii  libdvdread4 6.0.0-1
ii  libegl1 1.0.0-2
ii  libgbm1 17.3.3-1
ii  libgl1  1.0.0-2
ii  libjack-jackd2-0 [libjack-0.125]1.9.10+20150825git1ed50c92~dfsg-5
ii  libjpeg62-turbo 1:1.5.2-2+b1
ii  liblcms2-2  2.9-1
ii  liblua5.2-0 5.2.4-1.1+b2
ii  libpulse0   11.1-4
ii  librubberband2  1.8.1-7
ii  libsdl2-2.0-0   2.0.7+dfsg1-3
ii  libsmbclient2:4.7.4+dfsg-1
ii  libsndio6.1 1.1.0-3
pn  libswresample2  
pn  libswscale4 
ii  libuchardet00.0.6-2
ii  libva-drm2  2.0.0-2
ii  libva-wayland2  2.0.0-2
ii  libva-x11-2 2.0.0-2
ii  libva2  2.0.0-2
ii  libvdpau1   1.1.1-8
ii  libwayland-client0  1.14.0-1+b1
ii  libwayland-cursor0  1.14.0-1+b1
ii  libwayland-egl1-mesa [libwayland-egl1]  17.3.3-1
ii  libx11-62:1.6.4-3
ii  libxext62:1.3.3-1+b2
ii  libxinerama12:1.1.3-1+b3
ii  libxkbcommon0   0.8.0-1
ii  libxrandr2  2:1.5.1-1
ii  libxss1 1:1.2.2-1+b2
ii  libxv1  2:1.0.11-1
ii  zlib1g  1:1.2.8.dfsg-5

Versions of packages mpv recommends:
ii  xdg-utils   1.1.2-1
ii  youtube-dl  2018.01.27-1

mpv suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libbluray
Source-Version: 1:1.0.2-2

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

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

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated libbluray 
package)

Bug#878757: Openvswitch must started before networking servise

[Michael Biebl]

On Mon, 16 Oct 2017 20:28:26 +0700 Fedor Goncharov  wrote:
> Package: openvswitch-switch
> Version: 2.6.2~pre+git20161223-3
> Priority: critical
> 
> The Openvswitch daemon must be started before the network.service. 
> Because when the initiation of the network started interfaces from the 
> options should exist, or if you try to configure openvswitch in 
> /etc/network/interfaces, then the ovs daemon must be running to execute 
> commands.
> Please create a systemd configuration with the option "Before: 
> networking.service" for a stable version of debian.

That seems like the wrong thing to do.
networking.service is specific to ifupdown (auto). We do have several
other network configuration systems. I hope this was not actually
applied as a fix? The changelog is unfortunately unclear in that regard:

  * Added 2 debian/*.service files (Closes: #878757, #771507).

Thomas, can you please post the complete change that was actually applied.


Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#889144: stricter PIDfile handling breaks several daemons

[Sven Hartge]

On Sun, 4 Feb 2018 15:41:37 + Simon Kelley 
wrote:

> With my dnsmasq maintainer hat on, the current arrangement looks like this.
> 
> 1) /run/dnsmasq is a directory owned by dnsmasq:nogroup
> 2) /run/dnsmasq/dnsmasq.pid gets written by dnsmasq before it drops
> root, so is root:root
> 3) The reason /run/dnsmasq is owned by dnsmasq is so that dnsmasq can
> unlink the pidfile at shutdown, after it has dropped root and is running
> as 'dnsmasq'

Does dnsmasq need a PIDfile when running under systemd? Can't it just
not double fork, stay in the foreground using a Type=simple systemd unit?

That way the whole problem could be avoided all together.

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature

Bug#886164: Pending fixes for bugs in the libspring-java package

[pkg-java-maintainers]

tag 886164 + pending
thanks

Some bugs in the libspring-java package are closed in revision
e6539dac72289eb3318bd2a9b92718d2b7d336be in branch 'master' by Markus
Koschany

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/libspring-java.git/commit/?id=e6539da

Commit message:

Fix FTBFS and update 0041-servlet-api-compatibility.patch

Thanks: Hans Joachim Desserud for the report and patch.
Closes: #886164

Processed: Pending fixes for bugs in the libspring-java package

[Debian Bug Tracking System]

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

> tag 886164 + pending
Bug #886164 [src:libspring-java] libspring-java: FTBFS MockServerContainer.java 
method does not override or implement a method from a supertype
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#888201: mailman: CVE-2018-5950

[Salvatore Bonaccorso]

Control: found -1 1:2.1.18-1

On Thu, Feb 01, 2018 at 01:46:05PM +0100, Thijs Kinkhorst wrote:
> >> I plan to release Mailman 2.1.26 along with a patch for older releases
> >> to fix this issue on Feb 4, 2018. At that time, full details of the
> >> vulnerability will be public.
> 
> I've reserved time on Sunday to in any case to sid when the fix is
> released, and depending on the details/severity look into a security
> upload.

Thijs, unless I'm completely wrong, this issue goes at least back to
the jessie version? Marking as such for the BTS, but please correct me
if I'm wrong.

Regards,
Salvatore

Processed: Re: Bug#888201: mailman: CVE-2018-5950

[Debian Bug Tracking System]

Processing control commands:

> found -1 1:2.1.18-1
Bug #888201 {Done: Thijs Kinkhorst } [src:mailman] mailman: 
CVE-2018-5950
Marked as found in versions mailman/1:2.1.18-1.

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

Processed: bug 888201 is forwarded to https://bugs.launchpad.net/mailman/+bug/1747209

[Debian Bug Tracking System]

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

> forwarded 888201 https://bugs.launchpad.net/mailman/+bug/1747209
Bug #888201 {Done: Thijs Kinkhorst } [src:mailman] mailman: 
CVE-2018-5950
Set Bug forwarded-to-address to 
'https://bugs.launchpad.net/mailman/+bug/1747209'.
> thanks
Stopping processing here.

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

Processed: merge libbluray dependencies bugs

[Debian Bug Tracking System]

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

> forcemerge 889528 883908
Bug #889528 [libbluray-dev] libbluray-dev: missing dependencies on libxml, 
freetype, and fontconfig
Bug #883908 [libbluray-dev] missing dependencies
Severity set to 'serious' from 'normal'
Added indication that 883908 affects src:mpv
Merged 883908 889528
> thanks
Stopping processing here.

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

Processed: Re: Bug#889528: mpv: Reading bluray using mpv fails

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - confirmed
Bug #889528 [mpv] mpv: Reading bluray using mpv fails
Removed tag(s) confirmed.
> reassign -1 libbluray-dev 1:1.0.2-1
Bug #889528 [mpv] mpv: Reading bluray using mpv fails
Bug reassigned from package 'mpv' to 'libbluray-dev'.
No longer marked as found in versions mpv/0.27.0-3.
Ignoring request to alter fixed versions of bug #889528 to the same values 
previously set
Bug #889528 [libbluray-dev] mpv: Reading bluray using mpv fails
Marked as found in versions libbluray/1:1.0.2-1.
> retitle -1 libbluray-dev: missing dependencies on libxml, freetype, and 
> fontconfig
Bug #889528 [libbluray-dev] mpv: Reading bluray using mpv fails
Changed Bug title to 'libbluray-dev: missing dependencies on libxml, freetype, 
and fontconfig' from 'mpv: Reading bluray using mpv fails'.
> severity -1 serious
Bug #889528 [libbluray-dev] libbluray-dev: missing dependencies on libxml, 
freetype, and fontconfig
Severity set to 'serious' from 'important'
> affects -1 src:mpv
Bug #889528 [libbluray-dev] libbluray-dev: missing dependencies on libxml, 
freetype, and fontconfig
Added indication that 889528 affects src:mpv

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

Bug#889584: fpylll: FTBFS on 32-bit architectures: test failures: OverflowError, SystemError

[Andreas Beckmann]

Source: fpylll
Version: 0.3.0+ds1-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

fpylll/experimental FTBFS on all 32-bit architectures with test
failures:

https://buildd.debian.org/status/package.php?p=fpylll=experimental

   dh_auto_test -a -O--buildsystem=pybuild
I: pybuild base:184: cd 
/<>/fpylll-0.3.0+ds1/.pybuild/pythonX.Y_2.7/build; python2.7 -m 
pytest tests
= test session starts ==
platform linux2 -- Python 2.7.14+, pytest-3.2.1, py-1.4.34, pluggy-0.4.0
rootdir: /<>/fpylll-0.3.0+ds1, inifile:
collected 24 items

tests/test_bkz.py ..
tests/test_bkz_python.py 
tests/test_cvp.py .
tests/test_gso.py .
tests/test_lll.py ..
tests/test_multisol_enum.py .
tests/test_numpy.py ..
tests/test_precision.py .
tests/test_pruner.py .
tests/test_random.py .
tests/test_simple_bkz.py ..
tests/test_strategies.py .
tests/test_util.py .

== 24 passed in 62.16 seconds ==
I: pybuild base:184: cd 
/<>/fpylll-0.3.0+ds1/.pybuild/pythonX.Y_3.6/build; python3.6 -m 
pytest tests
= test session starts ==
platform linux -- Python 3.6.4, pytest-3.2.1, py-1.4.34, pluggy-0.4.0
rootdir: /<>/fpylll-0.3.0+ds1, inifile:
collected 24 items

tests/test_bkz.py ..
tests/test_bkz_python.py 
tests/test_cvp.py .
tests/test_gso.py FFF.F
tests/test_lll.py ..
tests/test_multisol_enum.py .
tests/test_numpy.py ..
tests/test_precision.py .
tests/test_pruner.py .
tests/test_random.py .
tests/test_simple_bkz.py ..
tests/test_strategies.py .
tests/test_util.py .

=== FAILURES ===
 test_gso_init _
OverflowError: Python int too large to convert to C long

The above exception was the direct cause of the following exception:

def test_gso_init():
for int_type in int_types:
for m, n in dimensions:
A = make_integer_matrix(m, n, int_type=int_type)
for float_type in float_types:
>   M = GSO.Mat(copy(A), float_type=float_type)

tests/test_gso.py:21: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

x = 

def copy(x):
"""Shallow copy operation on arbitrary Python objects.

See the module's __doc__ string for more info.
"""

cls = type(x)

copier = _copy_dispatch.get(cls)
if copier:
return copier(x)

try:
issc = issubclass(cls, type)
except TypeError: # cls is not a class
issc = False
if issc:
# treat it as a regular class:
return _copy_immutable(x)

copier = getattr(cls, "__copy__", None)
if copier:
>   return copier(x)
E   SystemError:  
returned a result with an error set

/usr/lib/python3.6/copy.py:88: SystemError
__ test_gso_d __
OverflowError: Python int too large to convert to C long

The above exception was the direct cause of the following exception:

def test_gso_d():
for int_type in int_types:
for m, n in dimensions:
A = make_integer_matrix(m, n, int_type=int_type)
for float_type in float_types:
>   M = GSO.Mat(copy(A), float_type=float_type)

tests/test_gso.py:38: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

x = 

def copy(x):
"""Shallow copy operation on arbitrary Python objects.

See the module's __doc__ string for more info.
"""

cls = type(x)

copier = _copy_dispatch.get(cls)
if copier:
return copier(x)

try:
issc = issubclass(cls, type)
except TypeError: # cls is not a class
issc = False
if issc:
# treat it as a regular class:
return _copy_immutable(x)

copier = getattr(cls, "__copy__", None)
if copier:
>   return copier(x)
E   SystemError:  
returned a result with an error set

/usr/lib/python3.6/copy.py:88: SystemError
__ test_gso_int_gram_enabled ___
OverflowError: Python int too large to convert to C long

The above exception was the direct cause of the following exception:

def test_gso_int_gram_enabled():
for int_type in int_types:
for m, n in dimensions:
A = make_integer_matrix(m, n, int_type=int_type)
for float_type in float_types:
>   M = GSO.Mat(copy(A), float_type=float_type)

tests/test_gso.py:47: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

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

[Debian Bug Tracking System]

Your message dated Sun, 04 Feb 2018 18:49:54 +
with message-id 
and subject line Bug#888201: fixed in mailman 1:2.1.26-1
has caused the Debian Bug report #888201,
regarding mailman: CVE-2018-5950
to be marked as done.

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

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


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

Hi,

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

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

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

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

For further information see:

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

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

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: mailman
Source-Version: 1:2.1.26-1

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

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

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

Debian distribution maintenance software
pp.
Thijs Kinkhorst  (supplier of updated mailman package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 04 Feb 2018 18:23:18 +
Source: mailman
Binary: mailman
Architecture: source amd64
Version: 1:2.1.26-1
Distribution: unstable
Urgency: medium
Maintainer: Mailman for Debian 
Changed-By: Thijs Kinkhorst 
Description:
 mailman- Web-based mailing list manager (legacy branch)
Closes: 888201
Changes:
 mailman (1:2.1.26-1) unstable; urgency=medium
 .
   * New upstream release.
 - Fixes XSS in user options CGI (CVE-2018-5950, closes: #888201)
   * Document that this is the legacy branch of Mailman and that all
 major development is focused on Mailman 3 (package mailman3).
Checksums-Sha1:
 6064ab921656d86f270871f21f8487dc6e97d37b 1698 mailman_2.1.26-1.dsc
 13d457555cb1603419d49aed560bffad89a9550b 9264592 mailman_2.1.26.orig.tar.gz
 643189ee31c3901135a6e1df66f31d8dc103d060 101792 mailman_2.1.26-1.debian.tar.xz
 2b70c7685c59028c3d842d277931ad00d5df04e9 18524 
mailman-dbgsym_2.1.26-1_amd64.deb
 a11293cfc9f84d951e2a98fa4f35d84ca59d7904 6286 mailman_2.1.26-1_amd64.buildinfo
 de0e0c8a50144c7940e19d649268b00f5fa60454 4446688 mailman_2.1.26-1_amd64.deb
Checksums-Sha256:
 70b7e3fbc76ade5407740339525e5ab2e531f4695b53cd1f4cc0c1fa54424094 1698 
mailman_2.1.26-1.dsc
 240177e1ef561ede88d7b48283c3835f39bbd0b1ae19100d3520cbe43058339f 9264592 
mailman_2.1.26.orig.tar.gz
 3f1f23deecf5fb08904227b87ce8146aa5167d2bcac0f6883325a102a2d18e59 101792 
mailman_2.1.26-1.debian.tar.xz
 2f7059e09f831d96d71fed10231bf90ae94ebaf48a88ff738380ec6ea28fcd33 18524 
mailman-dbgsym_2.1.26-1_amd64.deb
 bf7b505671459017b3cea4784a36fe52250cf0e7a190503432d538b1b580cdde 6286 
mailman_2.1.26-1_amd64.buildinfo
 01236fde31b09e3e35c93e278bf14b8dd0ee0b364dd987088c42456bea1e23df 4446688 
mailman_2.1.26-1_amd64.deb
Files:
 0885c32eaadbc2704ee8284c1ea67987 1698 mail optional mailman_2.1.26-1.dsc
 07d075148a3ffc03e6dc2613e797921e 9264592 mail optional 

Bug#889581: syslog-ng-incubator: FTBFS with syslog-ng 3.13.2

[Andreas Beckmann]

Source: syslog-ng-incubator
Version: 0.5.0-5
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

syslog-ng-incubator FTBFS with syslog-ng 3.13.2 that has merged
eventlog, s.t. it is no longer available as a separate package:

[...]
checking for strdup... yes
checking for strtoll... yes
checking for GLIB... yes
checking for SYSLOG_NG... yes
checking for EVENTLOG... no
configure: error: Package requirements (eventlog >= 0.2.10) were not met:

No package 'eventlog' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables EVENTLOG_CFLAGS
and EVENTLOG_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.


Andreas


syslog-ng-incubator.build.gz
Description: application/gzip

Bug#681726: Time to remove eclipse from Testing?

[Markus Koschany]

On Wed, 15 Nov 2017 18:01:07 +0200 Adrian Bunk  wrote:
[...]
> I tried to sort out what I could find as required for getting the
> ancient eclipse out of testing in [1]:
> 
> 1. src:bnd
> You fixed that already.
> 
> 2. batik -> maven -> guice -> libspring-java -> aspectj -> eclipse-platform
> Is there some good way to break this dependency chain?
> 
> 3. split libequinox-osgi-java out of src:eclise
> Or as a short-term hack, build only libequinox-osgi-java from src:eclipse.

I have spent some time this weekend on Eclipse again. I have created a
standalone src:libequinox-osgi-java package and successfully rebuilt all
reverse-dependencies. We only have to make a small adjustment in
src:netbeans and src:libnb-platform18-java and update the osgi patch.

If there are no objections I could go ahead and upload
libequinox-osgi-java to NEW.

eclipse-rcp:

* svnkit:

There are two Eclipse specific classes that fail to build. As a
workaround we could remove one of them and patch SVNWCUtil.

* android-sdktools and android-platform-tools-swt

According to [1] both packages should be removed anyway.

After that there would be only three packages left (not counting the
eclipse plugins) that build-depend on either eclipse-platform (aspectj)
or eclipse-jdt (lombok, biogenesis)

Next I'm going to try if a separate eclipse-jdt package from [2] could
be a drop-in-replacement for our current package. The latest stable
release appears to be S4_8_0_M5.

Regards,

Markus

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879175#10
[2] https://github.com/eclipse/eclipse.jdt.core

Bug#855942: Beta version of Anki has been available since July 2017

[Julian Gilbey]

Update on this bug: the beta version of anki is currently in unstable,
but upstream has explicitly requested that it not be packaged for
distributions until a new stable version has been released.  So I will
leave this bug report open until then.

   Julian

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> forcemerge 889188 881657
Bug #889188 [haskell-misfortune] haskell-misfortune is empty
Bug #881657 [haskell-misfortune] haskell-misfortune: No executable shipped, doh!
Severity set to 'grave' from 'important'
Merged 881657 889188
> thanks
Stopping processing here.

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

Bug#889144: stricter PIDfile handling breaks several daemons

[Sven Hartge]

On 04.02.2018 17:25, Michael Biebl wrote:
> Am 03.02.2018 um 14:35 schrieb Sven Hartge:
>> Um 14:00 Uhr am 03.02.18 schrieb Michael Biebl:

>>> The alternative afaics would be, that the daemon writes the pid file as
>>> munin:munin then (or ulog:ulog for the above case).
>>
>> No, this would open a potential DoS vector.
>>
>> Image an attacker gaining access to the munin user. He would then be able
>> to write any PID to the PIDfile and the init system would kill the other
>> process when the munin-node service is stopped/restarted.
>>
> 
> I don't think this applies to systemd though. If the process id listed
> in the pid file is not found in the service cgroup, systemd should not
> kill the process listed in the pid file. I suspect that MainPID will not
> be properly set and systemd will complain about it.

But it applies to SysV-Init. If the init-script does not use
start-stop-daemon correctly to check if the PID in the PIDfile belongs
to the executable to be killed or if the init-script uses some other
method of killing the daemon, it might easily kill a different program.

I know, this is not systemds concern whether other init implementations
behave correctly, but if you change the behaviour of a program because
of a behaviour change in systemd and then break other init systems or
increase the insecurity when used with other init systems because of
this, it will fall back negatively on systemd.

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature

Bug#889567: cloning 889006, reassign 889006 to dpatch ...

[Adrian Bunk]

On Sun, Feb 04, 2018 at 03:17:33PM +, Niels Thykier wrote:
> clone 889006 -1
> reassign 889006 dpatch 
> retitle -1 debhelper,dh-autoreconf: Handle backports for quilt.pm users
> thanks

Is there a reason against doing
  reassign 889567 dh-autoreconf 16
  retitle 889567 dh-autoreconf needs Breaks: quilt (<< 0.63-8.2~)
?

cu
Adrian

-- 

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

Bug#889144: stricter PIDfile handling breaks several daemons

[Michael Biebl]

Am 03.02.2018 um 14:35 schrieb Sven Hartge:
> Um 14:00 Uhr am 03.02.18 schrieb Michael Biebl:

>> The alternative afaics would be, that the daemon writes the pid file as
>> munin:munin then (or ulog:ulog for the above case).
> 
> No, this would open a potential DoS vector.
> 
> Image an attacker gaining access to the munin user. He would then be able
> to write any PID to the PIDfile and the init system would kill the other
> process when the munin-node service is stopped/restarted.
> 

I don't think this applies to systemd though. If the process id listed
in the pid file is not found in the service cgroup, systemd should not
kill the process listed in the pid file. I suspect that MainPID will not
be properly set and systemd will complain about it.

Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#889568: ibm-3270: Incomplete debian/copyright?

[Chris Lamb]

Source: ibm-3270
Version: 3.6ga4-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Philipp Kern 

Hi,

I just ACCEPTed ibm-3270 from NEW but noticed it was missing 
attribution in debian/copyright for some attributions in
x3270/select.c.

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

Congrats on this hitting main!


Regards,

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

Bug#888654: marked as done (mpv: CVE-2018-6360)

[Debian Bug Tracking System]

Your message dated Sun, 04 Feb 2018 16:09:20 +
with message-id 
and subject line Bug#888654: fixed in mpv 0.28.0-1
has caused the Debian Bug report #888654,
regarding mpv: CVE-2018-6360
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.)


-- 
888654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888654
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mpv
Version: 0.23.0-1
Severity: grave
Tags: security upstream
Forwarded: https://github.com/mpv-player/mpv/issues/5456

Hi,

the following vulnerability was published for mpv.

CVE-2018-6360[0]:
| mpv through 0.28.0 allows remote attackers to execute arbitrary code
| via a crafted web site, because it reads HTML documents containing
| VIDEO elements, and accepts arbitrary URLs in a src attribute without a
| protocol whitelist in player/lua/ytdl_hook.lua. For example, an
| av://lavfi:ladspa=file= URL signifies that the product should call
| dlopen on a shared object file located at an arbitrary local pathname.
| The issue exists because the product does not consider that youtube-dl
| can provide a potentially unsafe URL.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-6360
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6360
[1] https://github.com/mpv-player/mpv/issues/5456

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: mpv
Source-Version: 0.28.0-1

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

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

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

Debian distribution maintenance software
pp.
James Cowgill  (supplier of updated mpv package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 04 Feb 2018 12:53:27 +0100
Source: mpv
Binary: mpv libmpv1 libmpv-dev
Architecture: source
Version: 0.28.0-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: James Cowgill 
Description:
 libmpv-dev - video player based on MPlayer/mplayer2 (client library dev files)
 libmpv1- video player based on MPlayer/mplayer2 (client library)
 mpv- video player based on MPlayer/mplayer2
Closes: 888654
Changes:
 mpv (0.28.0-1) experimental; urgency=medium
 .
   * New upstream release.
 .
   * debian/compat:
 - Use debhelper 11.
   * debian/control:
 - Set Maintainer to debian-multimedia@l.d.o.
 - Switch Vcs URLs to salsa.debian.org.
 - Drop unused dependency on libavresample-dev.
 - Add dependencies on libarchive-dev and libvulkan-dev.
 - Bump ffmpeg dependencies to 3.5.
 - Set Rules-Requires-Root: no.
 - Bump standards to 4.1.3.
   * debian/copyright:
 - Update for 0.28.
 - Use secure copyright format URL.
   * debian/patches:
 - Drop vaapi patch applied upstream.
 - Add patch for CVE-2018-6360. (Closes: #888654)
 - Refresh other patches.
Checksums-Sha1:
 0ae7ce67a5e8f69f3879eca327d76b892ec243b2 2857 mpv_0.28.0-1.dsc
 626e20b8de6144566726e9939dd1ef8aa23f6257 2982165 mpv_0.28.0.orig.tar.gz
 ea2b0bee443e6144b6e1655a365643e2a2bb8ffa 105560 mpv_0.28.0-1.debian.tar.xz
 fe84a1cee43e8db994519e142d3e8228df9cb58d 8273 mpv_0.28.0-1_source.buildinfo
Checksums-Sha256:
 43bc6c7fda6817cce272875f677a2f7480157bf9492a631a5ac19759083a5bd9 2857 
mpv_0.28.0-1.dsc
 eeac559d422357470040b83d8cdabec74b8a64ce8f50d5ee421dd3e4c73457b4 2982165 
mpv_0.28.0.orig.tar.gz
 6a7a92023bde7cb5a623792d84f1035b78749b7fc9dca50b9093451c1cfaef42 105560 
mpv_0.28.0-1.debian.tar.xz
 4c7c6e7e687e88d2c95e33eeefe3f21309ad6801f72405e333fe7224015b3a41 8273 
mpv_0.28.0-1_source.buildinfo
Files:
 5cb68c855109dd76e6d2804e6b021dc1 2857 video optional mpv_0.28.0-1.dsc
 2ee9b57091fdc80c91a7fca1aae0e396 2982165 video optional mpv_0.28.0.orig.tar.gz
 9f922012bc26786221778485eb5a6344 105560 video optional 
mpv_0.28.0-1.debian.tar.xz
 a606b201a7134ba28f0dff5f2dbfb284 

Bug#889144: stricter PIDfile handling breaks several daemons

[Simon Kelley]

With my dnsmasq maintainer hat on, the current arrangement looks like this.

1) /run/dnsmasq is a directory owned by dnsmasq:nogroup
2) /run/dnsmasq/dnsmasq.pid gets written by dnsmasq before it drops
root, so is root:root
3) The reason /run/dnsmasq is owned by dnsmasq is so that dnsmasq can
unlink the pidfile at shutdown, after it has dropped root and is running
as 'dnsmasq'


There's a potential security hole here, since an attacker who can become
user dnsmasq, can create a symlink at /run/dnsmasq/dnsmasq.pid to
anywhere, and have the target of the symlink overwritten (as root) at
startup. The dnsmasq PID-file creation code detects and blocks this
case: see src/dnsmasq.c around line 507.

I think that this can be fixed in dnsmasq by chown()ing the pid file to
the same user dnsmasq is about to drop privs too, but I'm not sure is
that's enough to keep the new systemd checks happy.

Cheers,

Simon.

Bug#887782: marked as done (gcc-3.3 FTBFS: unwind-dw2.c:954: error: dereferencing pointer to incomplete type)

[Debian Bug Tracking System]

Your message dated Sun, 04 Feb 2018 16:06:47 +
with message-id 
and subject line Bug#887782: fixed in gcc-3.3 1:3.3.6ds1-30
has caused the Debian Bug report #887782,
regarding gcc-3.3 FTBFS: unwind-dw2.c:954: error: dereferencing pointer to 
incomplete type
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.)


-- 
887782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887782
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-3.3
Version: 1:3.3.6ds1-29
Severity: serious

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

...
./xgcc -B./ -B/usr/x86_64-linux-gnu/bin/ -isystem /usr/x86_64-linux-gnu/include 
-isystem /usr/x86_64-linux-gnu/sys-include -O2  -DIN_GCC-W -Wall 
-Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem ./include  
-fPIC -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED  -I. -I. 
-I../../src/gcc -I../../src/gcc/. -I../../src/gcc/config 
-I../../src/gcc/../include -fexceptions -c ../../src/gcc/unwind-dw2.c -o 
libgcc/./unwind-dw2.o
../../src/gcc/unwind-dw2.c: In function `uw_frame_state_for':
../../src/gcc/unwind-dw2.c:954: error: dereferencing pointer to incomplete type
libgcc.mk:104: recipe for target 'libgcc/./unwind-dw2.o' failed
make[5]: *** [libgcc/./unwind-dw2.o] Error 1


My first suspect would be some change in the glibc 2.26 headers.
--- End Message ---
--- Begin Message ---
Source: gcc-3.3
Source-Version: 1:3.3.6ds1-30

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

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

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

Debian distribution maintenance software
pp.
Philipp Kern  (supplier of updated gcc-3.3 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 04 Feb 2018 16:11:34 +0100
Source: gcc-3.3
Binary: libstdc++5
Architecture: source
Version: 1:3.3.6ds1-30
Distribution: unstable
Urgency: medium
Maintainer: Philipp Kern 
Changed-By: Philipp Kern 
Description:
 libstdc++5 - The GNU Standard C++ Library v3
Closes: 855851 887782 887783
Changes:
 gcc-3.3 (1:3.3.6ds1-30) unstable; urgency=medium
 .
   * Use ucontext_t instead of struct ucontext. (Closes: #887782)
   * Clarify that libstdc++5 is only still around for proprietary
 binaries that cannot be recompiled in the package's description.
 (Closes: #887783, #855851)
Checksums-Sha1:
 381a8f1044c5ded958ff942ba4299fd57479c474 2135 gcc-3.3_3.3.6ds1-30.dsc
 4a5134cb42582d02b1fe88fe495745e196d8fb6d 371105 gcc-3.3_3.3.6ds1-30.diff.gz
 95f3f19c4c7e381df5f9044a517169a07a008ae5 6902 
gcc-3.3_3.3.6ds1-30_source.buildinfo
Checksums-Sha256:
 cbb2655bb513dbb603eaeb364d60afd80d21889955e214c1bbb092bfe5c90abd 2135 
gcc-3.3_3.3.6ds1-30.dsc
 32a6d1d53509a50103303926c0aea24bac0f66a16795152bb25602c0a41a05e2 371105 
gcc-3.3_3.3.6ds1-30.diff.gz
 abcbb4557a4b31421973851f0bbee4ac2080c5bfa36bc0e064067c4f75d64330 6902 
gcc-3.3_3.3.6ds1-30_source.buildinfo
Files:
 1849fe7787f07a4f737065ca543b3dfd 2135 devel optional gcc-3.3_3.3.6ds1-30.dsc
 69f666a521068997bdf09c8289b29f88 371105 devel optional 
gcc-3.3_3.3.6ds1-30.diff.gz
 0ec9f2c88f04f8d71e7bdd1768b76fd3 6902 devel optional 
gcc-3.3_3.3.6ds1-30_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFFBAEBCgAvFiEEPzuChCNsw7gPxr3/RG4lRTXQVuwFAlp3LGYRHHBrZXJuQGRl
Ymlhbi5vcmcACgkQRG4lRTXQVuxAFAf+KMnlwXNd+r+Ets8jVUWTcpgmg4ZPY0cD
jOLeiyWd+MUmObBncrOks6JC8wCq+Kc2peBvjCWiadPv6cHehnHCCxSHVAg5e/AS
JkIw5vVnNKLp6jOZO4HKEfeodVkfW1n0fhCqbVzh3857s4hBz47FLqlbQpTOnwiU
9yHY3eDGU91QKaP2PTAF4z8CayzKNXb83TU4OgWavMrxtax59CGmTProcOja3nTN
is8hnJRrG/Y3N9auWmI5RuohMnvWpDizijSDCsNtGVFEHjalpQePJQcG8SpPjNLQ
/OBhMfDWNKA8l6ANDpBV79FPWaBlVRIj7u0aYAfefLqihAmRw+CfAQ==
=rhSr
-END PGP SIGNATURE End Message ---

Processed: Remove fixed version that confuses version tracking

[Debian Bug Tracking System]

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

> notfixed 884197 1.0.3-2+b1
Bug #884197 {Done: Ondřej Surý } [src:php-apcu-bc] php-apcu-bc 
FTBFS: php_apc.c:34:10: fatal error: ext/apcu/php_apc.h: No such file or 
directory
The source 'php-apcu-bc' and version '1.0.3-2+b1' do not appear to match any 
binary packages
No longer marked as fixed in versions 1.0.3-2+b1.
> close 884197
Bug #884197 {Done: Ondřej Surý } [src:php-apcu-bc] php-apcu-bc 
FTBFS: php_apc.c:34:10: fatal error: ext/apcu/php_apc.h: No such file or 
directory
Bug 884197 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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

Bug#878757: Ping! autoremovals need help

[debian]

This bug needs a modification so autoremovals/testing migrations can
work. Thanks, nthykier!

Thanks, BTS.

Chris.

Bug#858930: Ping! Trying to help openvswitch

[debian]

openvswitch, the only rdep of this package, has been fixed to not depend
on it. This bug needs pinging to help it migrating (thanks, nthykier!).

Hopefully this bug will eventually be fixed by RM.

Cheers,
Chris.

Bug#889006: marked as done (dh-autoreconf is run before patching)

[Debian Bug Tracking System]

Your message dated Sun, 04 Feb 2018 15:49:45 +
with message-id 
and subject line Bug#889006: fixed in dpatch 2.0.38+nmu1
has caused the Debian Bug report #889006,
regarding dh-autoreconf is run before patching
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.)


-- 
889006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889006
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debhelper,dh-autoreconf
Severity: serious
Control: found -1 16
Control: affects -1 src:dansguardian

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

...
   dh_autoreconf
configure.ac:14: installing './compile'
src/Makefile.am:13: warning: source file 'contentscanners/clamav.cpp' is in a 
subdirectory,
src/Makefile.am:13: but option 'subdir-objects' is disabled
automake: warning: possible forward-incompatibility.
automake: At least a source file is in a subdirectory, but the 'subdir-objects'
automake: automake option hasn't been enabled.  For now, the corresponding 
output
automake: object file(s) will be placed in the top-level directory.  However,
automake: this behaviour will change in future Automake versions: they will
automake: unconditionally cause object files to be placed in the same 
subdirectory
automake: of the corresponding sources.
automake: You are advised to start using 'subdir-objects' option throughout your
automake: project, to avoid future incompatibilities.
src/Makefile.am:31: warning: source file 'contentscanners/icapscan.cpp' is in a 
subdirectory,
src/Makefile.am:31: but option 'subdir-objects' is disabled
src/Makefile.am:39: warning: source file 'contentscanners/kavdscan.cpp' is in a 
subdirectory,
src/Makefile.am:39: but option 'subdir-objects' is disabled
src/Makefile.am:25: warning: source file 'contentscanners/clamdscan.cpp' is in 
a subdirectory,
src/Makefile.am:25: but option 'subdir-objects' is disabled
src/Makefile.am:43: warning: source file 'contentscanners/commandlinescan.cpp' 
is in a subdirectory,
src/Makefile.am:43: but option 'subdir-objects' is disabled
src/Makefile.am:48: warning: source file 'downloadmanagers/default.cpp' is in a 
subdirectory,
src/Makefile.am:48: but option 'subdir-objects' is disabled
src/Makefile.am:53: warning: source file 'downloadmanagers/fancy.cpp' is in a 
subdirectory,
src/Makefile.am:53: but option 'subdir-objects' is disabled
src/Makefile.am:57: warning: source file 'downloadmanagers/trickle.cpp' is in a 
subdirectory,
src/Makefile.am:57: but option 'subdir-objects' is disabled
src/Makefile.am:62: warning: source file 'authplugins/proxy.cpp' is in a 
subdirectory,
src/Makefile.am:62: but option 'subdir-objects' is disabled
src/Makefile.am:63: warning: source file 'authplugins/ident.cpp' is in a 
subdirectory,
src/Makefile.am:63: but option 'subdir-objects' is disabled
src/Makefile.am:64: warning: source file 'authplugins/ip.cpp' is in a 
subdirectory,
src/Makefile.am:64: but option 'subdir-objects' is disabled
src/Makefile.am:70: warning: source file 'authplugins/ntlm.cpp' is in a 
subdirectory,
src/Makefile.am:70: but option 'subdir-objects' is disabled
src/Makefile.am:65: warning: source file 'authplugins/digest.cpp' is in a 
subdirectory,
src/Makefile.am:65: but option 'subdir-objects' is disabled
   dh_dpatch_patch
applying patch 03_add_unconfigures to ./ ... ok.
applying patch 07_fix_config_paths to ./ ... ok.
applying patch 11_FixOptionContainer.cpp_on_arm to ./ ... ok.
applying patch 50_clamav095_support to ./ ... ok.
applying patch 60_add_gcc4.4_support to ./ ... ok.
applying patch 65-fix_clamdsocket to ./ ... ok.
applying patch 70-gcc4.6 to ./ ... ok.
applying patch 70_fix_clamav_detection to ./ ... ok.
applying patch 80_fix_libcre3_max_sub_expression_allocation to ./ ... ok.
...
checking for CLAMAV... no
configure: error: Package requirements (libclamav >= 4) were not met:

Requested 'libclamav >= 4' but version of libclamav is 0.99.3-beta2


This is caused by:


dh-autoreconf (16) unstable; urgency=medium
...
  * Run dh_autoreconf after dh_update_autotools_config,
not before dh_auto_configure
--- End Message ---
--- Begin Message ---
Source: dpatch
Source-Version: 2.0.38+nmu1

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

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

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

Processed: Re: Bug#889545: libopenmpt0: possible out-of-bounds memory read with malformed STP files

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 libopenmpt0: CVE-2018-6611
Bug #889545 [libopenmpt0] libopenmpt0: possible out-of-bounds memory read with 
malformed STP files
Changed Bug title to 'libopenmpt0: CVE-2018-6611' from 'libopenmpt0: possible 
out-of-bounds memory read with malformed STP files'.

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

Bug#889006: dh-autoreconf is run before patching

[Niels Thykier]

Gergely Nagy:
> Sorry for the brevity, I'm a tad short on time right now: yeah, I'm ok
> with a 0-day NMU of dpatch, that tweaks the sequence, and includes the
> patch for #868978 as well.
> 
> Thanks!
> 

Thanks, I have uploaded dpatch/2.0.38+nmu1 with the attached changes. :)

Apologies for the noise from a "2.0.37+nmu1" upload; I was basing it off
git and did not notice that git was out of date for the upload.

Thanks,
~Niels
diff -Nru dpatch-2.0.38/debhelper/dpatch.pm 
dpatch-2.0.38+nmu1/debhelper/dpatch.pm
--- dpatch-2.0.38/debhelper/dpatch.pm   2015-11-30 11:34:18.0 +0100
+++ dpatch-2.0.38+nmu1/debhelper/dpatch.pm  2018-02-04 16:23:16.0 
+0100
@@ -3,7 +3,7 @@
 use strict;
 use Debian::Debhelper::Dh_Lib;
 
-insert_before("dh_auto_configure", "dh_dpatch_patch");
+insert_before("dh_update_autotools_config", "dh_dpatch_patch");
 insert_before("dh_clean", "dh_dpatch_unpatch");
 
 # Eval to avoid problem with debhelper < 7.3.12
diff -Nru dpatch-2.0.38/debian/changelog dpatch-2.0.38+nmu1/debian/changelog
--- dpatch-2.0.38/debian/changelog  2015-11-30 12:19:57.0 +0100
+++ dpatch-2.0.38+nmu1/debian/changelog 2018-02-04 16:23:16.0 +0100
@@ -1,3 +1,15 @@
+dpatch (2.0.38+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.  Uploaded without delay with
+maintainer's permission  (#889006 comment 44).
+  * Apply patch from Sven Joachim to FTBFS if awk is provided
+by original-awk rather than mawk.  (Closes: #868978)
+  * Run dh_dpatch_patch before dh_update_autotools_config rather
+than before dh_auto_configure to ensure patching happens
+before autotools "retooling".  (Closes: #889006)
+
+ -- Niels Thykier   Sun, 04 Feb 2018 15:23:16 +
+
 dpatch (2.0.38) unstable; urgency=medium
 
   * Don't just install bash completion to a new place, remove the old files
diff -Nru dpatch-2.0.38/tools/shpp.awk dpatch-2.0.38+nmu1/tools/shpp.awk
--- dpatch-2.0.38/tools/shpp.awk2015-11-30 11:34:18.0 +0100
+++ dpatch-2.0.38+nmu1/tools/shpp.awk   2018-02-04 16:23:16.0 +0100
@@ -1,4 +1,4 @@
-#!/usr/bin/nawk -f
+#!/usr/bin/awk -f
 # shpp.awk -- Simple preprocessor for shell scripts
 #
 #  Copyright (C) 2003  Miles Bader 


signature.asc
Description: OpenPGP digital signature

Bug#889545: libopenmpt0: possible out-of-bounds memory read with malformed STP files

[James Cowgill]

Control: retitle -1 libopenmpt0: CVE-2018-6611

On 04/02/18 12:26, James Cowgill wrote:
> Package: libopenmpt0
> Version: 0.3.1-1
> Severity: grave
> Tags: security
> 
> This security update was published for libopenmpt:
> https://lib.openmpt.org/libopenmpt/2018/02/03/security-update-0.3.6/
> 
>> The OpenMPT/libopenmpt project released the latest stable libopenmpt version:
>>
>> libopenmpt 0.3.6 (2018-02-03)
>> [Sec] Possible out-of-bounds memory read with malformed STP files. (r9576)
> 
> The bug only affects 0.3.x so it will not require any updates to stable.
> 
> I have requested a CVE for this bug.

... and it was allocated CVE-2018-6611.

James



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#887586: node-chokidar: build hangs with mocha 4.0.1-3

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 mocha 4.0.1-3
Bug #887586 [src:node-chokidar] node-chokidar: build hangs with mocha 4.0.1-3
Bug reassigned from package 'src:node-chokidar' to 'mocha'.
No longer marked as found in versions node-chokidar/1.7.0-1.
Ignoring request to alter fixed versions of bug #887586 to the same values 
previously set
Bug #887586 [mocha] node-chokidar: build hangs with mocha 4.0.1-3
Marked as found in versions node-mocha/4.0.1-3.
> retitle -1 mocha 4.0.1-3 causes build hangs in various build-rdeps
Bug #887586 [mocha] node-chokidar: build hangs with mocha 4.0.1-3
Changed Bug title to 'mocha 4.0.1-3 causes build hangs in various build-rdeps' 
from 'node-chokidar: build hangs with mocha 4.0.1-3'.
> affects -1 src:node-chokidar src:node-errorhandler src:node-compression 
> src:node-connect src:node-connect-timeout src:node-cookie-parser 
> src:node-on-finished src:node-vhost src:node-webpack
Bug #887586 [mocha] mocha 4.0.1-3 causes build hangs in various build-rdeps
Added indication that 887586 affects src:node-chokidar, src:node-errorhandler, 
src:node-compression, src:node-connect, src:node-connect-timeout, 
src:node-cookie-parser, src:node-on-finished, src:node-vhost, and 
src:node-webpack

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

Bug#887586: node-chokidar: build hangs with mocha 4.0.1-3

[Adrian Bunk]

Control: reassign -1 mocha 4.0.1-3
Control: retitle -1 mocha 4.0.1-3 causes build hangs in various build-rdeps
Control: affects -1 src:node-chokidar src:node-errorhandler 
src:node-compression src:node-connect src:node-connect-timeout 
src:node-cookie-parser src:node-on-finished src:node-vhost src:node-webpack

On Thu, Jan 18, 2018 at 09:59:11AM +0200, Adrian Bunk wrote:
> Source: node-chokidar
> Version: 1.7.0-1
> Severity: serious
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-chokidar.html
> 
> ...
>debian/rules override_dh_auto_test
> make[1]: Entering directory '/build/1st/node-chokidar-1.7.0'
> mocha -R spec
>...
> Wed Jan  3 16:30:12 UTC 2018 - pbuilder was killed by timeout after 18h.
> Wed Jan  3 16:30:14 UTC 2018  I: 
> https://tests.reproducible-builds.org/debian/unstable/amd64/node-chokidar : 
> reproducible ➤ FTBFS
> Wed Jan  3 16:30:16 UTC 2018 - total duration: 18h 0m 31s.

This is actually an issue that seems to affect more build-rdeps of mocha
(build logs are in the reproducible builds of the affected packages).

cu
Adrian

-- 

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

Processed: Re: severity of 889189 is normal

[Debian Bug Tracking System]

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

> severity 889189 normal
Bug #889189 [inventor-doc] inventor-doc is empty
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

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

Processed: cloning 889006, reassign 889006 to dpatch ...

[Debian Bug Tracking System]

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

> clone 889006 -1
Bug #889006 [debhelper,dh-autoreconf] dh-autoreconf is run before patching
Bug 889006 cloned as bug 889567
> reassign 889006 dpatch
Bug #889006 [debhelper,dh-autoreconf] dh-autoreconf is run before patching
Bug reassigned from package 'debhelper,dh-autoreconf' to 'dpatch'.
No longer marked as found in versions dh-autoreconf/16.
Ignoring request to alter fixed versions of bug #889006 to the same values 
previously set
> retitle -1 debhelper,dh-autoreconf: Handle backports for quilt.pm users
Bug #889567 [debhelper,dh-autoreconf] dh-autoreconf is run before patching
Changed Bug title to 'debhelper,dh-autoreconf: Handle backports for quilt.pm 
users' from 'dh-autoreconf is run before patching'.
> thanks
Stopping processing here.

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

Bug#887576: marked as done (mupen64plus-qt FTBFS with libquazip5-headers 0.7.3-3)

[Debian Bug Tracking System]

Your message dated Sun, 04 Feb 2018 15:19:59 +
with message-id 
and subject line Bug#887576: fixed in mupen64plus-qt 1.11-1
has caused the Debian Bug report #887576,
regarding mupen64plus-qt FTBFS with libquazip5-headers 0.7.3-3
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.)


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

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

...
src/emulation/emulatorhandler.cpp:42:10: fatal error: quazip/quazip.h: No such 
file or directory
 #include 
  ^
compilation terminated.
Makefile:608: recipe for target 'emulatorhandler.o' failed
make[1]: *** [emulatorhandler.o] Error 1
--- End Message ---
--- Begin Message ---
Source: mupen64plus-qt
Source-Version: 1.11-1

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated mupen64plus-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: Sun, 04 Feb 2018 15:46:17 +0100
Source: mupen64plus-qt
Binary: mupen64plus-qt
Architecture: source
Version: 1.11-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Description:
 mupen64plus-qt - Basic launcher for Mupen64Plus
Closes: 887576
Changes:
 mupen64plus-qt (1.11-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version 1.11.
 - Fix FTBFS with libquazip5-headers. (Closes: #887576)
   * Use compat level 11.
   * Declare compliance with Debian Policy 4.1.3.
Checksums-Sha1:
 dd8653c50f728eded9d814fad57e5817fe8a 2221 mupen64plus-qt_1.11-1.dsc
 73a1cdf161e9a7306eb07144cd49a2519199359c 506652 mupen64plus-qt_1.11.orig.tar.gz
 2b8b232fe895f38295badc2db436ececc7ef4cc2 2776 
mupen64plus-qt_1.11-1.debian.tar.xz
 34e0dde8d42494efee918c90c21b98ed54b0b02c 10001 
mupen64plus-qt_1.11-1_amd64.buildinfo
Checksums-Sha256:
 e9178773c051aac5dd19ff12765c8a52fb7f332a36e3cf7cb52a3a370ceff927 2221 
mupen64plus-qt_1.11-1.dsc
 28a9566f138ff5048dd761fa867892fc7325bdc489a79057360f2e4ddaac8eee 506652 
mupen64plus-qt_1.11.orig.tar.gz
 97e12430968f550ec713a8f1c76e285e2fe988b68b175c2f06d4d1a08e3c38b8 2776 
mupen64plus-qt_1.11-1.debian.tar.xz
 645402bef5d778ad9100d1c1e534ffcd42405406ee773cdf6d02e2ddc88857a0 10001 
mupen64plus-qt_1.11-1_amd64.buildinfo
Files:
 39390091c6b1a8d27df551d962a86944 2221 games optional mupen64plus-qt_1.11-1.dsc
 43226917e195c37b41382bd72f4bdbf6 506652 games optional 
mupen64plus-qt_1.11.orig.tar.gz
 11b230b8696832e8d8ecbf1b42927f45 2776 games optional 
mupen64plus-qt_1.11-1.debian.tar.xz
 de1e90e6e7a91211ea51322fde2b44c4 10001 games optional 
mupen64plus-qt_1.11-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAlp3HghfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1HkPScP/jswBL6teYWivZ9CJuKDzzcVolyGkIJv3EaT
loaExE0UQvcXAlRHu+dl0C0EE4WKMLNz7o5PtJp2T2kydtz46S7ttzdEu39nwTNe
5W0uzp/vAVEej7K6+VAuvF1OzkpLvsbAmrFoiVWy10TGE/I0/xuT90MOQP24YHP0
erCXOp6GhKmB2Tzj0gZtljvVyRQG4JQhQW7NyLjPpyOJ9hbjtlW5KbPz7Q8CjaiH
zNVBhdJInX5vdmks/78b4qhQQu0YgQSubTpy1Q/wcj+lPH5jEeXz2EfFwbVvopdX
Zrw7Tv4hBjSkdKfsFIOxVnxLi7aAdEEVHQMXQxNNCGwfKpUbL0F/D2EygYSvP50B
BeuPfkETL1L6RN7RRrvsHfa79e991qv4JKJKtqYNEfxLvweXa2mVQEybUos3z/Bx
g2MdVAamBqnaxyZTMumF3M3TPAAfGoMvUTfGtGI1jVsDg0lT0qaLQ5nNfYE/1/mg
Kv18mh2BMmEVVVDiMyOj/ED4q1MihCjDzZ3wJyDpVXWxTPEg9FF0BTdMXqUO9X0G
GLLlP4ywdyDToHOMmCqF5x5TmBGbE87fnU7NTEkYRk0IqlRoWKN2xRD3Vu9uTuhA
dNiA9hXRCyCl3njveULDegvtk5kFCvg/j8ccKGKWRd5hM886NDnyu+veWPJ216iS
39XYdZde
=wz1n
-END PGP SIGNATURE End Message ---

Processed: Sorry, this found version was bogus

[Debian Bug Tracking System]

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

> notfound 889557 2.8.1+dfsg2-5
Bug #889557 [ovito] ovito: (Build-)Depends on obsolete libbotan1.10-dev
No longer marked as found in versions ovito/2.8.1+dfsg2-5.
> thanks
Stopping processing here.

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

Processed: Applies to buster, but not to stretch

[Debian Bug Tracking System]

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

> found 889557 2.8.1+dfsg2-5
Bug #889557 [ovito] ovito: (Build-)Depends on obsolete libbotan1.10-dev
Marked as found in versions ovito/2.8.1+dfsg2-5.
> tags 889556 buster sid
Bug #889556 [monotone] monotone: (Build-)Depends on obsolete libbotan1.10-dev
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Bug#889521: marked as done (libmsv: missing build-dependency on file)

[Debian Bug Tracking System]

Your message dated Sun, 04 Feb 2018 15:06:55 +
with message-id 
and subject line Bug#889521: fixed in libmsv 1.1.1-2
has caused the Debian Bug report #889521,
regarding libmsv: missing build-dependency on file
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=libmsv=mips64el=1.1.1-1=1517695216=0

...
checking whether to build shared libraries... no
...
mv debian/libmsv1/usr/lib/*.a debian/libmsv-dev/usr/lib
mv debian/libmsv1/usr/lib/*.so debian/libmsv-dev/usr/lib
mv: cannot stat 'debian/libmsv1/usr/lib/*.so': No such file or directory
debian/rules:45: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 1


For some reason it Works for me on eller.
--- End Message ---
--- Begin Message ---
Source: libmsv
Source-Version: 1.1.1-2

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

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

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

Debian distribution maintenance software
pp.
Clint Adams  (supplier of updated libmsv package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 04 Feb 2018 09:27:07 -0500
Source: libmsv
Binary: libmsv-dev libmsv1
Architecture: source
Version: 1.1.1-2
Distribution: unstable
Urgency: medium
Maintainer: Clint Adams 
Changed-By: Clint Adams 
Description:
 libmsv-dev - Monkeysphere validation library (development files)
 libmsv1- Monkeysphere validation library
Closes: 889521
Changes:
 libmsv (1.1.1-2) unstable; urgency=medium
 .
   * Build-depend on file.  closes: #889521
Checksums-Sha1:
 7e935c27524e2a8b066617a93b32d02bfe044e7c 2085 libmsv_1.1.1-2.dsc
 1e2e3192907a25ade14a143d8fd008f399fd2d28 365737 libmsv_1.1.1.orig.tar.gz
 e40dd9fd71f8482bef6b8e90aad4d1f31105dead 3128 libmsv_1.1.1-2.debian.tar.xz
 78a7d3610d71cea95a9df9a406108cd5c04e8993 5403 libmsv_1.1.1-2_source.buildinfo
Checksums-Sha256:
 4c6fb9ebccc66e12cf3e333be4dbe56954b0794ce92a40a450bb8e92a16bd637 2085 
libmsv_1.1.1-2.dsc
 00f585ddc91505e2c0ca199479f65c4dcc7ff68ff7334edd6159ed89fc2dae7c 365737 
libmsv_1.1.1.orig.tar.gz
 e514d33d502710e2318668b2d0e49ce365ab85a8ad5c92144c410c8a21931105 3128 
libmsv_1.1.1-2.debian.tar.xz
 e132d4166d8e0758df171335fdb55972a8bc2586967ae56f12a1427e073891b8 5403 
libmsv_1.1.1-2_source.buildinfo
Files:
 1f2e5cd4bdd92a8ef825ba253c9fec1f 2085 libs optional libmsv_1.1.1-2.dsc
 e1408398cca089f08c0042c0efdb2ea4 365737 libs optional libmsv_1.1.1.orig.tar.gz
 055208cdb8ecf2cd7fb92d36664f3f5c 3128 libs optional 
libmsv_1.1.1-2.debian.tar.xz
 9f51d6087272a68ca08ee609c7e9c1a5 5403 libs optional 
libmsv_1.1.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-
Comment: Debian!

iQKlBAEBCgCPFiEEdYHsh0BT5sgHeRubVZIzHhmdOKgFAlp3GItfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDc1
ODFFQzg3NDA1M0U2QzgwNzc5MUI5QjU1OTIzMzFFMTk5RDM4QTgRHGNsaW50QGRl
Ymlhbi5vcmcACgkQVZIzHhmdOKgeJA//cP0569Cles3eDCM8z8khEWmOGliBy669
xJTfKOOl8FrpAzW7txqK4JI2vuolBuQ6HnqRYmyLRbtzxoBEphNXDzX6cmD80a+N
bgFwvFVPBhRrdNmYVrCrHkHMRz2ATcym1MX/w1uDTPy4rpMAQdOyLzlNF7J7LVHH
Fp0zPAz89BHSQ40f4cz9ylN6adi9QyxyARA7oZyv6VDDIApoxrvyvJF+e923yNi+
WCQivwiLLwxscwjyaIhu4IJXcfYYLRc2ls/E/Pi5yxgbJMj0XGXj+HNd4zOfYBG4
2eAKaKLj1p37kkJK21EolJ/RYRNLJMhtbX0oUhASe8WQy2NEFLKmtlrmPV6hp1H5
f+9FKKy2OT+SQaWJ+ZllMztg19ISMnbjTu5UdOYzp9r8kYTK/cBZhtc9BH6sdlc8
BMT3q05PdeOidt19VlawUj4g07vOTKHYSG9oYuHL5Vr25aS/xzpciPp/Z5n82KBK
im2XNlYqq3YQWr+BIDaKPZg1SL5BRaE+I4T/o1JUk2Ls+JwdJ1IYJ7KL/yF2YAmL
fE1LMUhKrk9brUj8TNaOA51mi8ztKsL+p3twILBPp8uR7e+xMDm6KcCBQz1dqCPg
q6CiyTDJngEYmKybp2BzfDKRFEkrkotwAmo1XgsX83uZ1VGwIxggEU3JDT1Bt5cV
U9eeS/yMIoA=
=9ASi
-END PGP SIGNATURE End Message ---

Bug#888080: marked as done (python-tackerclient FTBFS: AttributeError: 'module' object has no attribute 'exceptions')

[Debian Bug Tracking System]

Your message dated Sun, 04 Feb 2018 15:05:28 +
with message-id 
and subject line Bug#888080: fixed in cmd2 0.7.7-1.1
has caused the Debian Bug report #888080,
regarding python-tackerclient FTBFS: AttributeError: 'module' object has no 
attribute 'exceptions'
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.)


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

Some recent change in unstable makes python-tackerclient FTBFS:

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

...
==
FAIL: tackerclient.tests.unit.test_ssl.TestSSL.test_ca_cert_passed
tackerclient.tests.unit.test_ssl.TestSSL.test_ca_cert_passed
--
_StringException: Traceback (most recent call last):
  File "tackerclient/tests/unit/test_ssl.py", line 67, in test_ca_cert_passed
self._test_verify_client_manager(cacert)
  File "tackerclient/tests/unit/test_ssl.py", line 53, in 
_test_verify_client_manager
shell.run(cacert)
  File "tackerclient/shell.py", line 579, in run
return self.interact()
  File "/usr/lib/python2.7/dist-packages/cliff/app.py", line 316, in interact
from .interactive import InteractiveApp
  File "/usr/lib/python2.7/dist-packages/cliff/interactive.py", line 20, in 

import cmd2
  File "/usr/lib/python2.7/dist-packages/cmd2.py", line 333, in 
except pyperclip.exceptions.PyperclipException:
AttributeError: 'module' object has no attribute 'exceptions'


==
FAIL: tackerclient.tests.unit.test_ssl.TestSSL.test_ca_cert_passed_as_env_var
tackerclient.tests.unit.test_ssl.TestSSL.test_ca_cert_passed_as_env_var
--
_StringException: Traceback (most recent call last):
  File "tackerclient/tests/unit/test_ssl.py", line 71, in 
test_ca_cert_passed_as_env_var
self._test_verify_client_manager([])
  File "tackerclient/tests/unit/test_ssl.py", line 53, in 
_test_verify_client_manager
shell.run(cacert)
  File "tackerclient/shell.py", line 579, in run
return self.interact()
  File "/usr/lib/python2.7/dist-packages/cliff/app.py", line 316, in interact
from .interactive import InteractiveApp
  File "/usr/lib/python2.7/dist-packages/cliff/interactive.py", line 20, in 

import cmd2
  File "/usr/lib/python2.7/dist-packages/cmd2.py", line 333, in 
except pyperclip.exceptions.PyperclipException:
AttributeError: 'module' object has no attribute 'exceptions'


--
Ran 152 tests in 2.691s

FAILED (failures=2)
debian/rules:14: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Source: cmd2
Source-Version: 0.7.7-1.1

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

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

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated cmd2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 01 Feb 2018 08:57:32 +
Source: cmd2
Binary: python-cmd2 python3-cmd2
Architecture: source all
Version: 0.7.7-1.1
Distribution: unstable
Urgency: medium
Maintainer: Federico Ceratto 
Changed-By: Thomas Goirand 
Description:
 python-cmd2 - enhanced Python cmd module - Python 2.x
 python3-cmd2 - enhanced Python cmd module - Python 3.x
Closes: 888080
Changes:
 cmd2 (0.7.7-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Added patch to make cmd2 work with newer pyperclip (Closes: #888080).
Checksums-Sha1:
 337878e5099507d82600fe937cb48470cd63cb57 2037 

Bug#888459: flint-arb's tests fail on 32bit archs using mpfr 4.0.0

[Vincent Lefevre]

On 2018-01-26 15:13:53 +0100, Vincent Lefevre wrote:
> It may be a bug in MPFR 4.

This was due to a bug in mpfr_div_ui, fixed in MPFR 4.0.1-rc2.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#889560: trilinos: cmake files seem to be missing

[Adrian Bunk]

Source: trilinos
Version: 12.12.1-3
Severity: serious
Control: affects -1 src:deal.ii

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

...
-- Include /build/1st/deal.ii-8.4.2/cmake/configure/configure_2_trilinos.cmake
CMake Error at /usr/lib/x86_64-linux-gnu/cmake/ROL/ROLConfig.cmake:174 
(INCLUDE):
  INCLUDE could not find load file:

/usr/lib/x86_64-linux-gnu/cmake/ROL/../MiniTensor/MiniTensorConfig.cmake
Call Stack (most recent call first):
  /usr/lib/x86_64-linux-gnu/cmake/Piro/PiroConfig.cmake:143 (INCLUDE)
  /usr/lib/x86_64-linux-gnu/cmake/Trilinos/TrilinosConfig.cmake:146 (INCLUDE)
  cmake/macros/macro_find_package.cmake:27 (_FIND_PACKAGE)
  cmake/modules/FindTRILINOS.cmake:40 (FIND_PACKAGE)
  cmake/macros/macro_find_package.cmake:27 (_FIND_PACKAGE)
  cmake/configure/configure_2_trilinos.cmake:22 (FIND_PACKAGE)
  obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/macro_configure_feature.tmp:1 
(FEATURE_TRILINOS_FIND_EXTERNAL)
  cmake/macros/macro_configure_feature.cmake:76 (INCLUDE)
  cmake/macros/macro_configure_feature.cmake:240 (RUN_COMMAND)
  cmake/configure/configure_2_trilinos.cmake:220 (CONFIGURE_FEATURE)
  cmake/macros/macro_verbose_include.cmake:19 (INCLUDE)
  CMakeLists.txt:119 (VERBOSE_INCLUDE)


CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Piro/PiroConfig.cmake:145 
(INCLUDE):
  INCLUDE could not find load file:

/usr/lib/x86_64-linux-gnu/cmake/Piro/../Tempus/TempusConfig.cmake
Call Stack (most recent call first):
  /usr/lib/x86_64-linux-gnu/cmake/Trilinos/TrilinosConfig.cmake:146 (INCLUDE)
  cmake/macros/macro_find_package.cmake:27 (_FIND_PACKAGE)
  cmake/modules/FindTRILINOS.cmake:40 (FIND_PACKAGE)
  cmake/macros/macro_find_package.cmake:27 (_FIND_PACKAGE)
  cmake/configure/configure_2_trilinos.cmake:22 (FIND_PACKAGE)
  obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/macro_configure_feature.tmp:1 
(FEATURE_TRILINOS_FIND_EXTERNAL)
  cmake/macros/macro_configure_feature.cmake:76 (INCLUDE)
  cmake/macros/macro_configure_feature.cmake:240 (RUN_COMMAND)
  cmake/configure/configure_2_trilinos.cmake:220 (CONFIGURE_FEATURE)
  cmake/macros/macro_verbose_include.cmake:19 (INCLUDE)
  CMakeLists.txt:119 (VERBOSE_INCLUDE)


CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Piro/PiroConfig.cmake:181 
(INCLUDE):
  INCLUDE could not find load file:

/usr/lib/x86_64-linux-gnu/cmake/Piro/../MiniTensor/MiniTensorConfig.cmake
Call Stack (most recent call first):
  /usr/lib/x86_64-linux-gnu/cmake/Trilinos/TrilinosConfig.cmake:146 (INCLUDE)
  cmake/macros/macro_find_package.cmake:27 (_FIND_PACKAGE)
  cmake/modules/FindTRILINOS.cmake:40 (FIND_PACKAGE)
  cmake/macros/macro_find_package.cmake:27 (_FIND_PACKAGE)
  cmake/configure/configure_2_trilinos.cmake:22 (FIND_PACKAGE)
  obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/macro_configure_feature.tmp:1 
(FEATURE_TRILINOS_FIND_EXTERNAL)
  cmake/macros/macro_configure_feature.cmake:76 (INCLUDE)
  cmake/macros/macro_configure_feature.cmake:240 (RUN_COMMAND)
  cmake/configure/configure_2_trilinos.cmake:220 (CONFIGURE_FEATURE)
  cmake/macros/macro_verbose_include.cmake:19 (INCLUDE)
  CMakeLists.txt:119 (VERBOSE_INCLUDE)


CMake Warning at 
/usr/lib/x86_64-linux-gnu/cmake/Trilinos/TrilinosConfig.cmake:156 (MESSAGE):
  Component "Tempus" NOT found.
Call Stack (most recent call first):
  cmake/macros/macro_find_package.cmake:27 (_FIND_PACKAGE)
  cmake/modules/FindTRILINOS.cmake:40 (FIND_PACKAGE)
  cmake/macros/macro_find_package.cmake:27 (_FIND_PACKAGE)
  cmake/configure/configure_2_trilinos.cmake:22 (FIND_PACKAGE)
  obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/macro_configure_feature.tmp:1 
(FEATURE_TRILINOS_FIND_EXTERNAL)
  cmake/macros/macro_configure_feature.cmake:76 (INCLUDE)
  cmake/macros/macro_configure_feature.cmake:240 (RUN_COMMAND)
  cmake/configure/configure_2_trilinos.cmake:220 (CONFIGURE_FEATURE)
  cmake/macros/macro_verbose_include.cmake:19 (INCLUDE)
  CMakeLists.txt:119 (VERBOSE_INCLUDE)


CMake Warning at 
/usr/lib/x86_64-linux-gnu/cmake/Trilinos/TrilinosConfig.cmake:156 (MESSAGE):
  Component "Domi" NOT found.
Call Stack (most recent call first):
  cmake/macros/macro_find_package.cmake:27 (_FIND_PACKAGE)
  cmake/modules/FindTRILINOS.cmake:40 (FIND_PACKAGE)
  cmake/macros/macro_find_package.cmake:27 (_FIND_PACKAGE)
  cmake/configure/configure_2_trilinos.cmake:22 (FIND_PACKAGE)
  obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/macro_configure_feature.tmp:1 
(FEATURE_TRILINOS_FIND_EXTERNAL)
  cmake/macros/macro_configure_feature.cmake:76 (INCLUDE)
  cmake/macros/macro_configure_feature.cmake:240 (RUN_COMMAND)
  cmake/configure/configure_2_trilinos.cmake:220 (CONFIGURE_FEATURE)
  cmake/macros/macro_verbose_include.cmake:19 (INCLUDE)
  CMakeLists.txt:119 (VERBOSE_INCLUDE)


CMake Warning at 
/usr/lib/x86_64-linux-gnu/cmake/Trilinos/TrilinosConfig.cmake:156 (MESSAGE):
  Component "MiniTensor" NOT found.
Call Stack (most recent call first):
  cmake/macros/macro_find_package.cmake:27 (_FIND_PACKAGE)
  cmake/modules/FindTRILINOS.cmake:40 

Processed: trilinos: cmake files seem to be missing

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:deal.ii
Bug #889560 [src:trilinos] trilinos: cmake files seem to be missing
Added indication that 889560 affects src:deal.ii

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

Bug#889558: qtcreator: (Build-)Depends on obsolete libbotan1.10-dev

[Christian Hofstaedtler]

Package: qtcreator
Version: 4.5.0-2
Severity: serious

Dear Maintainer,

your package qtcreator (build-)depends on botan1.10, which itself is
obsolete. Upstream will end security support at the end of 2018, so it
must not be part of buster.

Please drop the libbotan1.10-dev build dependency.

Thanks,
Chris

Bug#889556: monotone: (Build-)Depends on obsolete libbotan1.10-dev

[Christian Hofstaedtler]

Package: monotone
Version: 1.1-9
Severity: serious

Dear Maintainer,

your package monotone (build-)depends on botan1.10, which itself is
obsolete. Upstream will end security support at the end of 2018, so it
must not be part of buster.

Please drop the libbotan1.10-dev build dependency.

Thanks,
Chris

Bug#889557: ovito: (Build-)Depends on obsolete libbotan1.10-dev

[Christian Hofstaedtler]

Package: ovito
Version: 2.9.0+dfsg1-5
Severity: serious

Dear Maintainer,

your package ovito (build-)depends on botan1.10, which itself is
obsolete. Upstream will end security support at the end of 2018, so it
must not be part of buster.

Please drop the libbotan1.10-dev build dependency.

Thanks,
Chris

Processed: severity of 888089 is serious

[Debian Bug Tracking System]

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

> severity 888089 serious
Bug #888089 [src:botan1.10] botan1.10 EOL
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#886833: [gweled] Not compatable with recent gtk

[Juhani Numminen]

Followup-For: Bug #886833
Package: gweled
Version: 0.9.1-4

I'm getting a segfault at startup as well. I obtained a backtrace
using the instructions from wiki:
https://wiki.debian.org/HowToGetABacktrace


juhani@computer:~$ LANG=C gdb gweled
GNU gdb (Debian 7.12-6+b1) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from gweled...Reading symbols from 
/usr/lib/debug/.build-id/e4/b0823b7d96de627877b9462eeccbf06106f160.debug...done.
done.
(gdb) set pagination 0
(gdb) run
Starting program: /usr/games/gweled 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Gtk-Message: Failed to load module "atk-bridge"
Error loading config file: No such file or directory
[New Thread 0x7fd56aaf3700 (LWP 2992)]
[New Thread 0x7fd56a2f2700 (LWP 2993)]

(gweled:2987): GLib-WARNING **: GError set over the top of a previous GError or 
uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before 
it's set.
The overwriting error message was: Operation not supported

Thread 1 "gweled" received signal SIGSEGV, Segmentation fault.
__GI___libc_free (mem=0x180) at malloc.c:3097
3097malloc.c: No such file or directory.
(gdb) bt
#0  0x7fd578b463d1 in __GI___libc_free (mem=0x180) at malloc.c:3097
#1  0x562f8f00e179 in sge_load_svg_to_pixbuf 
(filename=filename@entry=0x562f9002dc00 "gweled/gem01.svg", width=48, 
height=48) at sge_utils.c:42
#2  0x562f8f00c676 in gweled_load_pixmaps () at graphic_engine.c:81
#3  0x562f8f00866d in main (argc=1, argv=0x7ffde66328a8) at main.c:429
(gdb) quit
A debugging session is active.

Inferior 1 [process 2987] will be killed.

Quit anyway? (y or n) y
juhani@computer:~$ 


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

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

Versions of packages gweled depends on:
ii  libatk1.0-0  2.26.1-3
ii  libc62.26-4
ii  libcairo21.15.8-3
ii  libfontconfig1   2.12.6-0.1
ii  libfreetype6 2.8.1-1
ii  libgdk-pixbuf2.0-0   2.36.11-1
ii  libglib2.0-0 2.54.3-2
ii  libgtk2.0-0  2.24.32-1
ii  libmikmod3   3.3.11.1-3
ii  libpango-1.0-0   1.40.14-1
ii  libpangocairo-1.0-0  1.40.14-1
ii  libpangoft2-1.0-01.40.14-1
ii  librsvg2-2   2.40.20-2

gweled recommends no packages.

gweled suggests no packages.

-- no debconf information

Bug#882066: marked as done (ansible-lint fails with ansible 2.4)

[Debian Bug Tracking System]

Your message dated Sun, 04 Feb 2018 13:34:53 +
with message-id 
and subject line Bug#882066: fixed in ansible-lint 3.4.20+git.20180203-1
has caused the Debian Bug report #882066,
regarding ansible-lint fails with ansible 2.4
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.)


-- 
882066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882066
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ansible-lint
Version: 3.4.13+git.20170811-1-1
Severity: important

Hi,

ansible-lint fails with ansible 2.4:

$ ansible-lint
Traceback (most recent call last):
  File "/usr/bin/ansible-lint", line 11, in 
load_entry_point('ansible-lint==3.4.13', 'console_scripts', 
'ansible-lint')()
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 572, 
in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2769, 
in load_entry_point
return ep.load()
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2422, 
in load
return self.resolve()
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2428, 
in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/lib/python2.7/dist-packages/ansiblelint/__init__.py", line 28, in 

import ansiblelint.utils
  File "/usr/lib/python2.7/dist-packages/ansiblelint/utils.py", line 53, in 

from ansible.plugins import module_loader
ImportError: cannot import name module_loader
$

The issue is fixed upstream since 3.4.15.

So please update the package to the latest upstream version.

Thanks and best regards

Hannes


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (900, 'testing'), (200, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages ansible-lint depends on:
ii  ansible  2.4.0.0+dfsg-1
ii  python   2.7.14-1
ii  python-six   1.11.0-1
ii  python-yaml  3.12-1+b1

ansible-lint recommends no packages.

ansible-lint suggests no packages.
--- End Message ---
--- Begin Message ---
Source: ansible-lint
Source-Version: 3.4.20+git.20180203-1

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

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

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

Debian distribution maintenance software
pp.
Gregory Colpart  (supplier of updated ansible-lint package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 03 Feb 2018 18:50:23 +0100
Source: ansible-lint
Binary: ansible-lint
Architecture: source all
Version: 3.4.20+git.20180203-1
Distribution: unstable
Urgency: medium
Maintainer: Gregory Colpart 
Changed-By: Gregory Colpart 
Description:
 ansible-lint - lint tool for Ansible playbooks
Closes: 882066
Changes:
 ansible-lint (3.4.20+git.20180203-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #882066)
Checksums-Sha1:
 b988cb1d8eab488afe4e7480e2a3e8693cdcd672 2031 
ansible-lint_3.4.20+git.20180203-1.dsc
 23efd4d747fdf9d8453e5bf38102459872385bff 34610 
ansible-lint_3.4.20+git.20180203.orig.tar.gz
 b8a2f62c179a54b8d2501fda55fbd5069aff591c 3840 
ansible-lint_3.4.20+git.20180203-1.debian.tar.xz
 182e3aa181cfa12a32347a0334a2fc5af966c7af 24764 
ansible-lint_3.4.20+git.20180203-1_all.deb
 1a4df3f485050f3cd9dc2fb45868513cb447b874 6151 
ansible-lint_3.4.20+git.20180203-1_amd64.buildinfo
Checksums-Sha256:
 9bceedb7eb8f2fa1f5db0b773d93c7cc483f0f3383eb73ed321ac567f7ac5805 2031 
ansible-lint_3.4.20+git.20180203-1.dsc
 b525b174c3c299ef4c40b8ad26c066b8c2a88e4b70abcc93e067b63e09b5f675 34610 
ansible-lint_3.4.20+git.20180203.orig.tar.gz
 c7ba7879f2a98bef12a32f0870a9bde31390f182ff041e6e8d9b4e9c16e769a1 3840 
ansible-lint_3.4.20+git.20180203-1.debian.tar.xz
 

Bug#871208: marked as done (python-xarray: FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p "3.6 3.5" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Sun, 04 Feb 2018 12:36:18 +
with message-id 
and subject line Bug#871208: fixed in python-xarray 0.9.6-1
has caused the Debian Bug report #871208,
regarding python-xarray: FTBFS: dh_auto_test: pybuild --test --test-pytest -i 
python{version} -p "3.6 3.5" returned exit code 13
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.)


-- 
871208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871208
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-xarray
Version: 0.9.2-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>/doc'
> sphinx-build -b html -d _build/doctrees   . _build/html
> Running Sphinx v1.5.6
> making output directory...
> python exec: /usr/bin/python3
> sys.path: ['/usr/share/sphinx/scripts/python3', '/<>', 
> '/usr/lib/python35.zip', '/usr/lib/python3.5', 
> '/usr/lib/python3.5/plat-x86_64-linux-gnu', '/usr/lib/python3.5/lib-dynload', 
> '/usr/local/lib/python3.5/dist-packages', '/usr/lib/python3/dist-packages']
> numpy: 1.12.1, /usr/lib/python3/dist-packages/numpy/__init__.py
> scipy: 0.18.1, /usr/lib/python3/dist-packages/scipy/__init__.py
> pandas: 0.20.3, /usr/lib/python3/dist-packages/pandas/__init__.py
> matplotlib: 2.0.0, /usr/lib/python3/dist-packages/matplotlib/__init__.py
> dask: 0.15.1, /usr/lib/python3/dist-packages/dask/__init__.py
> ipython: 5.1.0, /usr/lib/python3/dist-packages/IPython/__init__.py
> seaborn: 0.8.0, /usr/lib/python3/dist-packages/seaborn/__init__.py
> cartopy: 0.14.2, /usr/lib/python3/dist-packages/cartopy/__init__.py
> netCDF4: 1.2.9, /usr/lib/python3/dist-packages/netCDF4/__init__.py
> xarray: 0.9.2, /<>/xarray/__init__.py
> loading pickled environment... not yet created
> [autosummary] generating autosummary for: api-hidden.rst, api.rst, 
> combining.rst, computation.rst, dask.rst, data-structures.rst, examples.rst, 
> examples/monthly-means.rst, examples/multidimensional-coords.rst, 
> examples/quick-overview.rst, ..., indexing.rst, installing.rst, 
> internals.rst, io.rst, pandas.rst, plotting.rst, reshaping.rst, 
> time-series.rst, whats-new.rst, why-xarray.rst
> [autosummary] generating autosummary for: 
> /<>/doc/generated/xarray.DataArray.T.rst, 
> /<>/doc/generated/xarray.DataArray.__getitem__.rst, 
> /<>/doc/generated/xarray.DataArray.__setitem__.rst, 
> /<>/doc/generated/xarray.DataArray.all.rst, 
> /<>/doc/generated/xarray.DataArray.any.rst, 
> /<>/doc/generated/xarray.DataArray.argmax.rst, 
> /<>/doc/generated/xarray.DataArray.argmin.rst, 
> /<>/doc/generated/xarray.DataArray.argsort.rst, 
> /<>/doc/generated/xarray.DataArray.assign_attrs.rst, 
> /<>/doc/generated/xarray.DataArray.assign_coords.rst, ..., 
> /<>/doc/generated/xarray.ufuncs.sign.rst, 
> /<>/doc/generated/xarray.ufuncs.signbit.rst, 
> /<>/doc/generated/xarray.ufuncs.sin.rst, 
> /<>/doc/generated/xarray.ufuncs.sinh.rst, 
> /<>/doc/generated/xarray.ufuncs.sqrt.rst, 
> /<>/doc/generated/xarray.ufuncs.square.rst, 
> /<>/doc/generated/xarray.ufuncs.tan.rst, 
> /<>/doc/generated/xarray.ufuncs.tanh.rst, 
> /<>/doc/generated/xarray.ufuncs.trunc.rst, 
> /<>/doc/generated/xarray.zeros_like.rst
> loading intersphinx inventory from /usr/share/doc/python3/html/objects.inv...
> loading intersphinx inventory from 
> /usr/share/doc/python-pandas-doc/html/objects.inv...
> loading intersphinx inventory from 
> /usr/share/doc/python-numpy-doc/html/objects.inv...
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 24 source files that are out of date
> updating environment: 322 added, 0 changed, 0 removed
> reading sources... [  0%] api
> reading sources... [  0%] api-hidden
> reading sources... [  0%] combining
> reading sources... [  1%] computation
> reading sources... [  1%] dask
> reading sources... [  1%] data-structures
> reading sources... [  2%] examples
> reading sources... [  2%] examples/monthly-means
> reading sources... [  2%] examples/multidimensional-coords
> reading sources... [  3%] examples/quick-overview
> reading sources... [  3%] examples/weather-data
> reading sources... [  3%] faq
> reading sources... [  4%] generated/xarray.DataArray
> reading sources... [  4%] generated/xarray.DataArray.T
> reading sources... [  4%] generated/xarray.DataArray.__getitem__
> reading sources... [  4%] generated/xarray.DataArray.__setitem__
> 

Bug#882559: marked as done (python-xarray FTBFS - GenericNetCDFDataTest.test_cross_engine_read_write_netcdf3 failed)

[Debian Bug Tracking System]

Your message dated Sun, 04 Feb 2018 12:36:18 +
with message-id 
and subject line Bug#882559: fixed in python-xarray 0.9.6-1
has caused the Debian Bug report #882559,
regarding python-xarray FTBFS - 
GenericNetCDFDataTest.test_cross_engine_read_write_netcdf3 failed
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.)


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

Package: python3-xarray
Version: 0.9.2-1
Severity: serious
Control: tags -1 upstream

Two netcdf tests fail in current sid (see log below).

This is known upstream as https://github.com/pydata/xarray/issues/1721 , 
according to which the actual problem is that scipy has been writing 
netcdf files with invalid padding for some time ( 
https://github.com/scipy/scipy/pull/8170 ), and netcdf 4.5 rejects such 
invalid files ( https://github.com/Unidata/netcdf-c/issues/657 ).


netcdf have since reverted this change, and a patch has been posted for 
the original scipy bug, but given that neither of these are xarray's 
fault it might make most sense to temporarily disable these tests.


=== FAILURES 
===
__ GenericNetCDFDataTest.test_cross_engine_read_write_netcdf3 
__


self = testMethod=test_cross_engine_read_write_netcdf3>


def test_cross_engine_read_write_netcdf3(self):
data = create_test_data()
valid_engines = set()
if has_netCDF4:
valid_engines.add('netcdf4')
if has_scipy:
valid_engines.add('scipy')

for write_engine in valid_engines:
for format in ['NETCDF3_CLASSIC', 'NETCDF3_64BIT']:
with create_tmp_file() as tmp_file:
data.to_netcdf(tmp_file, format=format,
   engine=write_engine)
for read_engine in valid_engines:
with open_dataset(tmp_file,
> engine=read_engine) as actual:

xarray/tests/test_backends.py:977:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _

xarray/backends/api.py:291: in open_dataset
autoclose=autoclose)
xarray/backends/netCDF4_.py:210: in __init__
self.ds = opener()
xarray/backends/netCDF4_.py:185: in _open_netcdf4_group
ds = nc4.Dataset(filename, mode=mode, **kwargs)
netCDF4/_netCDF4.pyx:2015: in netCDF4._netCDF4.Dataset.__init__
???
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _


>   ???
E   OSError: [Errno -36] NetCDF: Invalid argument: 
b'/tmp/tmpmgjj7gx5/temp-88.nc'


netCDF4/_netCDF4.pyx:1636: OSError
___ 
GenericNetCDFDataTestAutocloseTrue.test_cross_engine_read_write_netcdf3 


self = testMethod=test_cross_engine_read_write_netcdf3>


def test_cross_engine_read_write_netcdf3(self):
data = create_test_data()
valid_engines = set()
if has_netCDF4:
valid_engines.add('netcdf4')
if has_scipy:
valid_engines.add('scipy')

for write_engine in valid_engines:
for format in ['NETCDF3_CLASSIC', 'NETCDF3_64BIT']:
with create_tmp_file() as tmp_file:
data.to_netcdf(tmp_file, format=format,
   engine=write_engine)
for read_engine in valid_engines:
with open_dataset(tmp_file,
> engine=read_engine) as actual:

xarray/tests/test_backends.py:977:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _

xarray/backends/api.py:291: in open_dataset
autoclose=autoclose)
xarray/backends/netCDF4_.py:210: in __init__
self.ds = opener()
xarray/backends/netCDF4_.py:185: in _open_netcdf4_group
ds = nc4.Dataset(filename, mode=mode, **kwargs)
netCDF4/_netCDF4.pyx:2015: in netCDF4._netCDF4.Dataset.__init__
???
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _


>   ???
E   OSError: [Errno -36] NetCDF: Invalid argument: 
b'/tmp/tmpfc4acgiv/temp-93.nc'


netCDF4/_netCDF4.pyx:1636: OSError

(followed by a few more failures that look like #871208 - see there)
--- End Message ---
--- Begin Message ---
Source: python-xarray
Source-Version: 0.9.6-1

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

A summary of the changes between this version and the 

Processed: retitle 889521 to libmsv: missing build-dependency on file

[Debian Bug Tracking System]

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

> retitle 889521 libmsv: missing build-dependency on file
Bug #889521 [src:libmsv] Bug#889521: libmsv: missing build-dependency on file
Changed Bug title to 'libmsv: missing build-dependency on file' from 
'Bug#889521: libmsv: missing build-dependency on file'.
> thanks
Stopping processing here.

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

Bug#889521: libmsv FTBFS on mips64el: shared library not built

[Aurelien Jarno]

control: retitle -1 Bug#889521: libmsv: missing build-dependency on file
control: tag -1 + patch

On 2018-02-04 08:38, Adrian Bunk wrote:
> Source: libmsv
> Version: 1.1.1-1
> Severity: serious
> 
> https://buildd.debian.org/status/fetch.php?pkg=libmsv=mips64el=1.1.1-1=1517695216=0
> 
> ...
> checking whether to build shared libraries... no
> ...
> mv debian/libmsv1/usr/lib/*.a debian/libmsv-dev/usr/lib
> mv debian/libmsv1/usr/lib/*.so debian/libmsv-dev/usr/lib
> mv: cannot stat 'debian/libmsv1/usr/lib/*.so': No such file or directory
> debian/rules:45: recipe for target 'binary-arch' failed
> make: *** [binary-arch] Error 1

The problem comes from the following lines at the beginning of the build
log when running the configure script:

| checking how to truncate binary pipes... /bin/dd bs=4096 count=1
| ./configure: line 6508: /usr/bin/file: No such file or directory
| ./configure: line 6516: /usr/bin/file: No such file or directory
| ./configure: line 6524: /usr/bin/file: No such file or directory
| checking for mt... no

The new upstream version has an updated libtool, which requires
/usr/bin/file on mips64el.

Note that file is also missing on other architectures, though the build
succeed. For example on amd64:

| checking how to truncate binary pipes... /bin/dd bs=4096 count=1
| ./configure: line 6548: /usr/bin/file: No such file or directory
| checking for mt... no

The fix for that is to build-depends on file, like done in the attached
patch.

> For some reason it Works for me on eller.

The default chroots on porterboxes have file installed.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
diff -Nru libmsv-1.1.1/debian/control libmsv-1.1.1/debian/control
--- libmsv-1.1.1/debian/control	2018-02-03 21:19:40.0 +0100
+++ libmsv-1.1.1/debian/control	2018-02-04 12:54:28.0 +0100
@@ -1,7 +1,7 @@
 Source: libmsv
 Priority: optional
 Maintainer: Clint Adams 
-Build-Depends: doxygen, libcurl4-nss-dev, libjansson-dev, dpkg (>= 1.19.0.3~)
+Build-Depends: doxygen, libcurl4-nss-dev, libjansson-dev, dpkg (>= 1.19.0.3~), file
 Standards-Version: 4.1.3
 Section: libs
 Homepage: http://floss.scru.org/libmsv/


signature.asc
Description: PGP signature

Processed: Re: Bug#889521: libmsv FTBFS on mips64el: shared library not built

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 Bug#889521: libmsv: missing build-dependency on file
Bug #889521 [src:libmsv] libmsv FTBFS on mips64el: shared library not built
Changed Bug title to 'Bug#889521: libmsv: missing build-dependency on file' 
from 'libmsv FTBFS on mips64el: shared library not built'.
> tag -1 + patch
Bug #889521 [src:libmsv] Bug#889521: libmsv: missing build-dependency on file
Added tag(s) patch.

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