Bug#877376: RFS: codeblocks/16.01+dfsg-2.1 [NMU] [RC]

[Andreas Moog]

Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for a nmu for the package "codeblocks", the current 
maintainer has given the "OK" for it:

 * Package name: codeblocks
   Version : 16.01+dfsg-2.1
   Section : x11

It builds those binary packages:

  codeblocks - Code::Blocks integrated development environment (IDE)
  codeblocks-common - common files for Code::Blocks IDE
  codeblocks-contrib - contrib plugins for Code::Blocks IDE
  codeblocks-dbg - Code::Blocks debugging libraries
  codeblocks-dev - Code::Blocks development files (SDK)
  libcodeblocks0 - Code::Blocks shared library
  libwxsmithlib-dev - wxSmith development files (Code::Blocks plugin for RAD 
GUI editin
  libwxsmithlib0 - wxSmith shared library (Code::Blocks plugin for RAD GUI 
editing)

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/codeblocks

Alternatively, one can download the package with dget using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/c/codeblocks/codeblocks_16.01+dfsg-2.1.dsc

Changes since the last upload:

codeblocks (16.01+dfsg-2.1) unstable; urgency=medium

  * Non-maintainer upload.
  * Apply patch from upstream svn to fix FTBFS with GCC 7.1 (Closes: #853349)

  Regards,
   Andreas Moog

-- 
PGP-encrypted mails preferred
PGP Fingerprint: 74CD D9FE 5BCB FE0D 13EE 8EEA 61F3 4426 74DE 6624


signature.asc
Description: PGP signature

Bug#869746: where to assign this bug

[Timo Aaltonen]

On 01.10.2017 00:48, 積丹尼 Dan Jacobson wrote:
>> "TA" == Timo Aaltonen  writes:
> TA> so you have nvidia installed..
> 
> Yes, lots of
> libgl1-nvidia-legacy-304xx-glx:amd64/unstable 304.135-5 uptodate
> libnvidia-legacy-304xx-cfg1:amd64/unstable 304.135-5 uptodate
> libnvidia-legacy-304xx-glcore:amd64/unstable 304.135-5 uptodate
> libnvidia-legacy-304xx-ml1:amd64/unstable 304.135-5 uptodate
> nvidia-legacy-304xx-alternative:amd64/unstable 304.135-5 uptodate
> nvidia-legacy-304xx-driver-bin:amd64/unstable 304.135-5 uptodate
> nvidia-legacy-304xx-driver-libs:amd64/unstable 304.135-5 uptodate
> nvidia-legacy-304xx-driver:amd64/unstable 304.135-5 uptodate
> nvidia-legacy-304xx-kernel-dkms:amd64/unstable 304.135-5 uptodate
> nvidia-legacy-304xx-kernel-support:amd64/unstable 304.135-5 uptodate
> nvidia-legacy-304xx-vdpau-driver:amd64/unstable 304.135-5 uptodate
> nvidia-settings-legacy-304xx:amd64/unstable 304.134-1 uptodate
> xserver-xorg-legacy:amd64/unstable 2:1.19.3-2 uptodate
> xserver-xorg-video-nvidia-legacy-304xx:amd64/unstable 304.135-5 uptodate
> etc.

I was trying to hint you towards the probable culprit. Nvidia legacy
doesn't even work with glvnd. So please move this bug elsewhere.



-- 
t

Bug#877375: polygen: please make the build reproducible

[Chris Lamb]

Source: polygen
Version: 1.0.6.ds2-17
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: fileordering
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0], we noticed
that polygen could not be built reproducibly due to iterating
over the filesystem in a nondeterminstic order.

Patch attached.

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/rules  2017-09-30 22:33:16.304169618 +0100
--- b/debian/rules  2017-09-30 22:37:03.932967181 +0100
@@ -43,7 +43,7 @@
 build/polygen::
$(POLYGEN) debian/man.grm > polygen.1
chmod 0755 debian/make_polygen-data_manpage
-   find $(POLYGEN_BASE)/grm/ -name \*.grm | 
debian/make_polygen-data_manpage > polygen-data.6
+   find $(POLYGEN_BASE)/grm/ -name \*.grm | LC_ALL=C sort | 
debian/make_polygen-data_manpage > polygen-data.6
 
 install/polygen::
install -o root -g root -m 755 $(POLYGEN_BIN) 
debian/$(cdbs_curpkg)/usr/games/

Bug#742829: closed by intrigeri (Bug#742829: fixed in apparmor 2.10.95-8)

[intrigeri]

Hi,

Guido Günther:
> On Fri, Sep 29, 2017 at 04:09:02PM -0400, Daniel Richard G. wrote:
>>   #include 

> This file is currently not included in Debian's apparmor
> package. @intrigeri, can this be added?

Before r1608 (in Vcs-Bzr) we shipped that file in
/usr/share/apparmor-profiles/abstractions/ubuntu-browsers.d/

I don't see any Include directive for that path in
/etc/apparmor/parser.conf, so I doubt it was actually used.

> I assume we don't want other packages to mess around
> in abstractions?

I think it's fine: any package can ship the abstractions it needs (and
quite a few do), as long as side-effects are considered carefully.
In the case at hand, it seems that
/etc/apparmor.d/abstractions/ubuntu-browsers.d is a place from which
profiles can include selected bits they need, rather than a directory
that will get included all at once, so there's no side effect and we
should be good (checked with codesearch.d.net that supports my guess :)

Cheers,
-- 
intrigeri

Bug#877357: [debhelper-devel] Bug#877357: debhelper: Make qmake buildsystem support cross building

[Niels Thykier]

Dmitry Shachnev:
> Package: debhelper
> Version: 10.9
> Severity: wishlist
> Tags: patch
> 
> Dear debhelper maintainers,
> 
> I am attaching two patches against Git master that should make packages
> using qmake buildsystem cross-buildable (at least some of them).
> 
> The first patch sets the proper toolchain commands, the second one adds
> a very basic qt.conf so that qmake searches for Qt headers in a proper
> location. It was enough in my case, but we may extend it with other paths
> later if needed.
> 
> --
> Dmitry Shachnev
> 
> [...]

Hi Dmitry,

Thanks for providing this patch set. :)

I am CC'ing Helmut, who is usually on top of cross-building for his input.

I have done a quick review and with my remarks below:

[patch1]
> @@ -52,6 +52,10 @@ sub configure {
>  
>   push @options, '-makefile';
>   push @options, '-nocache';
> + if (is_cross_compiling()) {
> + # Force generic mkspec to avoid -m32 / -m64 flags
> + push @options, ("-spec", "linux-g++");
^^

I believe we rely on cross-builds producing bit-for-bit identical output
with a native build as a part of the QA.  If so, then this need to be
unconditional (possibly in a later compat level).

If the -spec option is used, then I will need something that also works
for other architectures/OSes.  It is fine if it is a stable of known
OSes mapped to their option (like we do for cmake).


[patch2]
> @@ -55,6 +56,14 @@ sub configure {
>   if (is_cross_compiling()) {
>   # Force generic mkspec to avoid -m32 / -m64 flags
>   push @options, ("-spec", "linux-g++");
> +
> + my ($fh, $filename) = tempfile("qt.", SUFFIX => ".conf", 
> TMPDIR => 1, UNLINK => 1);
> + $fh->print("[Paths]\n");
> + $fh->print("Prefix=/usr\n");
> + $fh->print("HostData=lib/" . 
> dpkg_architecture_value("DEB_HOST_GNU_TYPE") . "/qt5\n");
> + $fh->print("Headers=include/" . 
> dpkg_architecture_value("DEB_HOST_GNU_TYPE") . "/qt5\n");

These two lines should almost certainly use DEB_HOST_MULTIARCH.  :)

Thanks,
~Niels

Bug#877374: stretch-pu: shadow 1:4.4-4.1+deb9u1

[Balint Reczey]

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

Dear Release Team,

I have prepared an update for the shadow package which may be released
as a stable update:

Changes:
 shadow (1:4.4-4.1+deb9u1) stretch; urgency=medium
 .
   * Revert adding pts/0 and pts/1 to securetty.
     Adding pts/* defeats the purpose of securetty. Let containers add it if
     needed as described in #830255.
   * Fix buffer overflow if NULL line is present in db (CVE-2017-12424)
     (Closes: #756630)

The Security Team suggested fixing those minor security-related issues via
proposed-updates rather than via stretch-security.

Thanks,
Balint

diff -Nru shadow-4.4/debian/changelog shadow-4.4/debian/changelog
--- shadow-4.4/debian/changelog	2017-05-17 13:59:59.0 +0200
+++ shadow-4.4/debian/changelog	2017-09-30 03:30:30.0 +0200
@@ -1,3 +1,13 @@
+shadow (1:4.4-4.1+deb9u1) stretch; urgency=medium
+
+  * Revert adding pts/0 and pts/1 to securetty.
+Adding pts/* defeats the purpose of securetty. Let containers add it if
+needed as described in #830255.
+  * Fix buffer overflow if NULL line is present in db (CVE-2017-12424)
+(Closes: #756630)
+
+ -- Balint Reczey   Fri, 29 Sep 2017 21:30:30 -0400
+
 shadow (1:4.4-4.1) unstable; urgency=high
 
   * Non-maintainer upload.
diff -Nru shadow-4.4/debian/patches/0009-Fix-buffer-overflow-if-NULL-line-is-present-in-db.patch shadow-4.4/debian/patches/0009-Fix-buffer-overflow-if-NULL-line-is-present-in-db.patch
--- shadow-4.4/debian/patches/0009-Fix-buffer-overflow-if-NULL-line-is-present-in-db.patch	1970-01-01 01:00:00.0 +0100
+++ shadow-4.4/debian/patches/0009-Fix-buffer-overflow-if-NULL-line-is-present-in-db.patch	2017-09-30 03:30:30.0 +0200
@@ -0,0 +1,42 @@
+From 954e3d2e7113e9ac06632aee3c69b8d818cc8952 Mon Sep 17 00:00:00 2001
+From: Tomas Mraz 
+Date: Fri, 31 Mar 2017 16:25:06 +0200
+Subject: [PATCH] Fix buffer overflow if NULL line is present in db.
+
+If ptr->line == NULL for an entry, the first cycle will exit,
+but the second one will happily write past entries buffer.
+We actually do not want to exit the first cycle prematurely
+on ptr->line == NULL.
+Signed-off-by: Tomas Mraz 
+---
+ lib/commonio.c | 8 
+ 1 file changed, 4 insertions(+), 4 deletions(-)
+
+diff --git a/lib/commonio.c b/lib/commonio.c
+index b10da06a..31edbaaf 100644
+--- a/lib/commonio.c
 b/lib/commonio.c
+@@ -751,16 +751,16 @@ commonio_sort (struct commonio_db *db, int (*cmp) (const void *, const void *))
+ 	for (ptr = db->head;
+ 	(NULL != ptr)
+ #if KEEP_NIS_AT_END
+-	 && (NULL != ptr->line)
+-	 && (   ('+' != ptr->line[0])
+-	 && ('-' != ptr->line[0]))
++	 && ((NULL == ptr->line)
++	 || (('+' != ptr->line[0])
++	 && ('-' != ptr->line[0])))
+ #endif
+ 	 ;
+ 	 ptr = ptr->next) {
+ 		n++;
+ 	}
+ #if KEEP_NIS_AT_END
+-	if ((NULL != ptr) && (NULL != ptr->line)) {
++	if (NULL != ptr) {
+ 		nis = ptr;
+ 	}
+ #endif
+-- 
+2.11.0
+
diff -Nru shadow-4.4/debian/patches/series shadow-4.4/debian/patches/series
--- shadow-4.4/debian/patches/series	2017-05-17 13:59:59.0 +0200
+++ shadow-4.4/debian/patches/series	2017-09-30 03:30:30.0 +0200
@@ -6,6 +6,7 @@
 0006-French-manpage-translation.patch
 0007-Fix-some-spelling-issues-in-the-Norwegian-translatio.patch
 0008-su-properly-clear-child-PID.patch
+0009-Fix-buffer-overflow-if-NULL-line-is-present-in-db.patch
 301-Reset-pid_child-only-if-waitpid-was-successful.patch
 
 # These patches are only for the testsuite:
diff -Nru shadow-4.4/debian/securetty.linux shadow-4.4/debian/securetty.linux
--- shadow-4.4/debian/securetty.linux	2017-05-17 13:59:59.0 +0200
+++ shadow-4.4/debian/securetty.linux	2017-09-30 03:30:30.0 +0200
@@ -164,11 +164,6 @@
 ttyM1
 #...
 
-# Unix98 PTY slaves
-pts/0
-pts/1
-#...
-
 # Technology Concepts serial card
 ttyT0
 ttyT1

Bug#877373: dupload: Use of uninitialized value $mailtx in hash element at /usr/bin/dupload line 439, <$fh_changes> line 10.

[Paul Wise]

Package: dupload
Version: 2.9.0
Severity: minor

When I was uploading autorevision_1.21-1 to Debian I got a Perl warning
from dupload. The full log of the upload is listed below, warning is:

Use of uninitialized value $mailtx in hash element at /usr/bin/dupload line 
439, <$fh_changes> line 10.

$ dupload ../autorevision_1.21-1_source.changes
dupload note: no announcement will be sent.
../autorevision_1.21-1_source.changes:
  Good signature found
   validating autorevision_1.21-1.dsc
  Good signature found
   validating autorevision_1.21.orig.tar.gz
   validating autorevision_1.21.orig.tar.gz.asc
   validating autorevision_1.21-1.debian.tar.xz
All files validated successfully.
Uploading (scpb) to ssh.upload.debian.org:/srv/upload.debian.org/UploadQueue/
autorevision_1.21-1.dsc:
  Good signature found
   validating autorevision_1.21.orig.tar.gz
   validating autorevision_1.21.orig.tar.gz.asc
   validating autorevision_1.21-1.debian.tar.xz
All files validated successfully.
[ job autorevision_1.21-1_source from autorevision_1.21-1_source.changesUse of 
uninitialized value $mailtx in hash element at /usr/bin/dupload line 439, 
<$fh_changes> line 10.

 autorevision_1.21-1.debian.tar.xz, size ok, md5sum ok, sha1sum ok, sha256sum ok
 autorevision_1.21.orig.tar.gz.asc, size ok, md5sum ok, sha1sum ok, sha256sum ok
 autorevision_1.21.orig.tar.gz, size ok, md5sum ok, sha1sum ok, sha256sum ok
 autorevision_1.21-1.dsc, size ok, md5sum ok, sha1sum ok, sha256sum ok
 autorevision_1.21-1_source.changes ok ]
Uploading (scp) to ftp-master (ssh.upload.debian.org)
[ Uploading job autorevision_1.21-1_source
 autorevision_1.21-1.debian.tar.xz 36.7 kB, ok
 autorevision_1.21.orig.tar.gz.asc 2.1 kB, ok
 autorevision_1.21.orig.tar.gz 20.7 kB, ok
 autorevision_1.21-1.dsc 2.0 kB, ok
 autorevision_1.21-1_source.changes 2.5 kB, ok
autorevision_1.21-1.debian.tar.xz   
   100%   
37KB  36.7KB/s   00:01
autorevision_1.21.orig.tar.gz.asc   
   100% 
2191 5.8KB/s   00:00
autorevision_1.21.orig.tar.gz   
   100%   
21KB  24.3KB/s   00:00
autorevision_1.21-1.dsc 
   100% 
2078 5.7KB/s   00:00
autorevision_1.21-1_source.changes  
   100% 
2544 7.1KB/s   00:00
 ]

-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages dupload depends on:
ii  perl  5.26.0-8

Versions of packages dupload recommends:
ii  openssh-client  1:7.5p1-10

Versions of packages dupload suggests:
ii  exim4-daemon-light [mail-transport-agent]  4.89-6
ii  lintian2.5.54

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#877372: ITP: bzrmk -- Generator for .bzrignore files

[Sascha Manns]

Package: wnpp
Severity: wishlist
Owner: Sascha Manns 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

* Package name: bzrmk
  Version : 1.3.0
  Upstream Author : Sascha Manns 
* URL : https://launchpad.net/bzrmk
* License : (GPL3+)
  Programming Lang: (Python, Make)
  Description : Generator for .bzrignore files

This program helps by creating a .bzrignore file for your project. After
installing it provides a binary, which can copy the installed bzr.mk into your
current project directory. bzr.mk itself provides some useful rules for
blacklisting some of your files to put them into the .bzrignore.

- - why is this package useful/relevant?
It can simplify developers (which using bzr) workflow.

- - is it a dependency for another package?
It isn't a dependency for other Packages.

- - do you use it?
Yes i'm using it daily.

- - if there are other packages providing similar functionality, how does it
compare?
No other packages with similar functionality found.

- - how do you plan to maintain it?
I'm the upstream developer and can take care of this package. I don't need a
co-maintainer, but a sponsor.




-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJZ0IOrAAoJEHUnY+i/qDosEFYP/R95Rrj0N6jgG44j9ZECQE7b
Gq99RtUs8vFL0CFh5g7YACb9aeLFwU3tch2hltgfVqnYV7IQg7ZUTn9E8Pf5F8rK
ptqe7pEkHcoGVkydhSUhCdDGV8a2MBRUAGspmgYUFFsOj5F1BlXxCwOrqWa0b97q
rSkHOnqn7fV00bIaBYW0T03DcPoN86Y0+DKaF03nq0ELWfWhiScbmDaV2maZvvwq
u5hf9QFfKh1IaD71PfeE2nmToLGfuuIo3lEA1KHFWEbh+VstWJj+C7lxeW3pQsuU
DIzIitSkRODj94Z4vSNpIY6/BaWbzp7KcC3SFfOr6buC12D3lteKuHcGI6EPs7aB
zIfsnVCd3NF2IYkvBcZ7TpC59RKq5ApqyIYQUsulyWz6nj7ftSR1VCMAhw/TlZc9
aEhZaOuwnfPAH/jFdkayUen4/hFbhNYPuWGpp2HYl4oDUzQWhKf3e1VvOlYQuDyB
l4OobUKJ5VdvypIlYjZmTRAq9RXih7+Z16+vuxVOuI8B8nGGjqpgd6GBFqdZMoIw
dQhTQbNhtzL0nn4ng5Q+G1RDiw2o557lcfqpZP4FVkAI4EC6fxcIjJGB6UDV2p4w
yYeNFemhtgK/gnaKLcFLRGBbP42aJtcHibil8t3d/LtPnVCdPAMMwsB9bRq75E2+
CHS+8pcc6lsfPH6NI3W0
=mUMu
-END PGP SIGNATURE-

Bug#875759: [uim-chewing] Future uim-utils removal

[dai]

Control: severity -1 serious

uim package uploaded into unstable, so elevate severity.
-- 
Regards,
dai

GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E


signature.asc
Description: PGP signature

Bug#877371: plinth: Selecting Configuration->Certificates (Let's Encrypt) fail

[Petter Reinholdtsen]

Package: plinth
Version: 0.15.2+ds-1
Severity: important

When using the web GUI and selecting Configuration->Certificates (Let's
Encrypt), I get a 500 internal server error.  This is the output in
/var/log/plinth/status.log when it happen:

[2017-10-01 05:18:15,289] plinth.actions INFO Executing command - ['sudo', 
'-n', '/usr/share/plinth/actions/letsencrypt', 'get-status']
[2017-10-01 05:18:17,130] plinth.actions INFO Executing command - ['sudo', 
'-n', '/usr/share/plinth/actions/letsencrypt', 'manage_hooks', 'status']
[2017-10-01 05:18:17,650] django.request ERRORInternal Server Error: 
/plinth/sys/letsencrypt/
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 
41, in inner
response = get_response(request)
  File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 249, 
in _legacy_get_response
response = self._get_response(request)
  File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 217, 
in _get_response
response = self.process_exception_by_middleware(e, request)
  File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 215, 
in _get_response
response = response.render()
  File "/usr/lib/python3/dist-packages/django/template/response.py", line 107, 
in render
self.content = self.rendered_content
  File "/usr/lib/python3/dist-packages/django/template/response.py", line 84, 
in rendered_content
content = template.render(context, self._request)
  File "/usr/lib/python3/dist-packages/django/template/backends/django.py", 
line 66, in render
return self.template.render(context)
  File "/usr/lib/python3/dist-packages/django/template/base.py", line 207, in 
render
return self._render(context)
  File "/usr/lib/python3/dist-packages/django/template/base.py", line 199, in 
_render
return self.nodelist.render(context)
  File "/usr/lib/python3/dist-packages/django/template/base.py", line 990, in 
render
bit = node.render_annotated(context)
  File "/usr/lib/python3/dist-packages/django/template/base.py", line 957, in 
render_annotated
return self.render(context)
  File "/usr/lib/python3/dist-packages/django/template/loader_tags.py", line 
177, in render
return compiled_parent._render(context)
  File "/usr/lib/python3/dist-packages/django/template/base.py", line 199, in 
_render
return self.nodelist.render(context)
  File "/usr/lib/python3/dist-packages/django/template/base.py", line 990, in 
render
bit = node.render_annotated(context)
  File "/usr/lib/python3/dist-packages/django/template/base.py", line 957, in 
render_annotated
return self.render(context)
  File "/usr/lib/python3/dist-packages/django/template/loader_tags.py", line 
177, in render
return compiled_parent._render(context)
  File "/usr/lib/python3/dist-packages/django/template/base.py", line 199, in 
_render
return self.nodelist.render(context)
  File "/usr/lib/python3/dist-packages/django/template/base.py", line 990, in 
render
bit = node.render_annotated(context)
  File "/usr/lib/python3/dist-packages/django/template/base.py", line 957, in 
render_annotated
return self.render(context)
  File "/usr/lib/python3/dist-packages/django/template/loader_tags.py", line 
72, in render
result = block.nodelist.render(context)
  File "/usr/lib/python3/dist-packages/django/template/base.py", line 990, in 
render
bit = node.render_annotated(context)
  File "/usr/lib/python3/dist-packages/django/template/base.py", line 957, in 
render_annotated
return self.render(context)
  File "/usr/lib/python3/dist-packages/django/template/loader_tags.py", line 
72, in render
result = block.nodelist.render(context)
  File "/usr/lib/python3/dist-packages/django/template/base.py", line 990, in 
render
bit = node.render_annotated(context)
  File "/usr/lib/python3/dist-packages/django/template/base.py", line 957, in 
render_annotated
return self.render(context)
  File "/usr/lib/python3/dist-packages/django/template/loader_tags.py", line 
72, in render
result = block.nodelist.render(context)
  File "/usr/lib/python3/dist-packages/django/template/base.py", line 990, in 
render
bit = node.render_annotated(context)
  File "/usr/lib/python3/dist-packages/django/template/base.py", line 957, in 
render_annotated
return self.render(context)
  File "/usr/lib/python3/dist-packages/django/template/defaulttags.py", line 
322, in render
return nodelist.render(context)
  File "/usr/lib/python3/dist-packages/django/template/base.py", line 990, in 
render
bit = node.render_annotated(context)
  File "/usr/lib/python3/dist-packages/django/template/base.py", line 957, in 
render_annotated
return self.render(context)
  File "/usr/lib/python3/dist-packages/django/template/defaulttags.py", line 
458, in render
url = reverse(view_name, args=args, kwargs=kwargs, current_app=current_app)
  File "/usr/lib/python3/dist-packages/django/urls/base.py", li

Bug#876516: plinth: .../plinth/sys/pagekite/configure/ return 500 internal server error

[Petter Reinholdtsen]

Control: found -1 0.15.2+ds-1

I just tested with the upgraded plinth version in testing, and the
problem still exist (from /var/log/plinth/status.log):

[2017-10-01 05:11:39,763] plinth.actions INFO Executing command - ['sudo', 
'-n', '/usr/share/plinth/actions/pagekite', 'is-disabled']
[2017-10-01 05:11:40,281] plinth.actions INFO Executing command - ['sudo', 
'-n', '/usr/share/plinth/actions/pagekite', 'get-kite']
[2017-10-01 05:11:40,903] plinth.actions INFO Executing command - ['sudo', 
'-n', '/usr/share/plinth/actions/pagekite', 'get-frontend']
[2017-10-01 05:11:41,421] django.request ERRORInternal Server Error: 
/plinth/sys/pagekite/configure/
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 
41, in inner
response = get_response(request)
  File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 249, 
in _legacy_get_response
response = self._get_response(request)
  File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 217, 
in _get_response
response = self.process_exception_by_middleware(e, request)
  File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 215, 
in _get_response
response = response.render()
  File "/usr/lib/python3/dist-packages/django/template/response.py", line 107, 
in render
self.content = self.rendered_content
  File "/usr/lib/python3/dist-packages/django/template/response.py", line 84, 
in rendered_content
content = template.render(context, self._request)
  File "/usr/lib/python3/dist-packages/django/template/backends/django.py", 
line 66, in render
return self.template.render(context)
  File "/usr/lib/python3/dist-packages/django/template/base.py", line 207, in 
render
return self._render(context)
  File "/usr/lib/python3/dist-packages/django/template/base.py", line 199, in 
_render
return self.nodelist.render(context)
  File "/usr/lib/python3/dist-packages/django/template/base.py", line 990, in 
render
bit = node.render_annotated(context)
  File "/usr/lib/python3/dist-packages/django/template/base.py", line 957, in 
render_annotated
return self.render(context)
  File "/usr/lib/python3/dist-packages/django/template/loader_tags.py", line 
177, in render
return compiled_parent._render(context)
  File "/usr/lib/python3/dist-packages/django/template/base.py", line 199, in 
_render
return self.nodelist.render(context)
  File "/usr/lib/python3/dist-packages/django/template/base.py", line 990, in 
render
bit = node.render_annotated(context)
  File "/usr/lib/python3/dist-packages/django/template/base.py", line 957, in 
render_annotated
return self.render(context)
  File "/usr/lib/python3/dist-packages/django/template/loader_tags.py", line 
72, in render
result = block.nodelist.render(context)
  File "/usr/lib/python3/dist-packages/django/template/base.py", line 990, in 
render
bit = node.render_annotated(context)
  File "/usr/lib/python3/dist-packages/django/template/base.py", line 957, in 
render_annotated
return self.render(context)
  File "/usr/lib/python3/dist-packages/django/template/loader_tags.py", line 
72, in render
result = block.nodelist.render(context)
  File "/usr/lib/python3/dist-packages/django/template/base.py", line 990, in 
render
bit = node.render_annotated(context)
  File "/usr/lib/python3/dist-packages/django/template/base.py", line 957, in 
render_annotated
return self.render(context)
  File "/usr/lib/python3/dist-packages/django/template/base.py", line 1040, in 
render
output = self.filter_expression.resolve(context)
  File "/usr/lib/python3/dist-packages/django/template/base.py", line 736, in 
resolve
new_obj = func(obj, *arg_vals)
  File 
"/usr/lib/python3/dist-packages/bootstrapform/templatetags/bootstrap.py", line 
46, in bootstrap_horizontal
return render(element, markup_classes)
  File 
"/usr/lib/python3/dist-packages/bootstrapform/templatetags/bootstrap.py", line 
83, in render
return template.render(context)
  File "/usr/lib/python3/dist-packages/django/template/backends/django.py", 
line 64, in render
context = make_context(context, request, 
autoescape=self.backend.engine.autoescape)
  File "/usr/lib/python3/dist-packages/django/template/context.py", line 287, 
in make_context
raise TypeError('context must be a dict rather than %s.' % 
context.__class__.__name__)
TypeError: context must be a dict rather than Context.

--
Happy hacking
Petter Reinholdtsen

Bug#877370: Doesn't allow saying "do not print answers"

[Luke Faraone]

Package: purity-ng
Version: 0.2.0-2.1
Severity: important

purity-ng incorrectly checks the user's answer to the "should answers be
printed" text, v.s. accepting "n" as an answer. 

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

Kernel: Linux 4.13.3-1-ARCH (SMP w/12 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C 
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages purity-ng depends on:
ii  python  2.7.13-2

Versions of packages purity-ng recommends:
ii  purity  1-19

purity-ng suggests no packages.

-- no debconf information

Bug#869638: slic3r-prusa FTBFS on big endian: admesh works correctly on little endian machines only

[Petter Reinholdtsen]

[Adrian Bunk]
> If this is not fixable with reasonable effort, an RM bug for the old mips
> binary should be sent against ftp.debian.org and this bug downgraded to
> important.

I had a quick look at the code, and the trigger is of course this in
xs/src/admesh/stl.h:

  #ifndef BOOST_LITTLE_ENDIAN
  #error "admesh works correctly on little endian machines only!"
  #endif

I was unable to see what should cause the code to only work on little endian
machines, and did not have a big endian machine easily available.  I would
recommend forwarding the issue to upstream and asking the ftpmasters to
remove the old mips binaries until upstream or some big endian porters have
time to look at it.
-- 
Happy hacking
Petter Reinholdtsen

Bug#877326: ITP: emoji-data -- The associated data files for emoji characters

[Paul Wise]

On Sat, Sep 30, 2017 at 11:04 PM, Osamu Aoki wrote:

> If this is already available, point me to it.

http://metadata.ftp-master.debian.org/changelogs/main/u/unicode-data/unstable_changelog

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#877369: perl: Digest::MD5 64 bit issue, calculates incorrect MD5

[Marc Lehmann]

Package: perl
Version: 5.24.1-3+deb9u2
Severity: normal

Dear Maintainer,

Digest::MD5 calculates the wrong MD5 for large scalars:

$ perl -e 'print "\x00" x 1024 x 1024 x 1024 x 9'|md5sum -
97606009c3309d3a0b4b40ae9fadc720  -

$ perl -MDigest::MD5 -E 'say Digest::MD5::md5_hex "\x00" x 1024 x 1024 x 1024 x 
9'
e02694e929aec3068ff272bebe0ae0a4

This is likely due to buggy length calculation in MD5.xs, which fails for
large values of "len" (and hasn't changed for 5.26):

ctx->bytes_low += len;
if (ctx->bytes_low < len) /* wrap around */
ctx->bytes_high++;

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

Kernel: Linux 4.9.51-040951-generic (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages perl depends on:
ii  dpkg   1.18.24
ii  libperl5.245.24.1-3+deb9u2
ii  perl-base  5.24.1-3+deb9u2
ii  perl-modules-5.24  5.24.1-3+deb9u2

Versions of packages perl recommends:
ii  netbase  5.4
pn  rename   

Versions of packages perl suggests:
ii  libterm-readline-gnu-perl   1.35-1
ii  libterm-readline-perl-perl  1.0303-1
ii  make4.1-9.1
pn  perl-doc

-- no debconf information

Bug#721358: bug#28574: cross compilnng, man pages

[Pádraig Brady]

On 23/09/17 20:18, Peter Bohning wrote:
> Cross compiling for aarch64 from amd64
>  
> Is there no way to disable the man pages in configure options?  Thanks.
>  
> https://lists.gnu.org/archive/html/coreutils/2014-11/msg0.html

I've seen this issue in various places now (CC'd).

We should probably reinstate distribution of man pages
since these generated pages are so similar on various systems.
Also given the amount of old ChangeLogs removed recently
I don't think the addition of 273K (uncompressed) is prohibitive.

The attached was tested in these modes:
 git repo build
 tarball build with/without help2man
 tarball vpath build with/without help2man
 make distcheck
 make install  (and ensure only enabled program man pages installed)

I've not applied this yet, but hope to soon after a bit more testing.

cheers,
Pádraig
From d05e91c7b6c84b22cab3f30abdf3490b7c83910b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?P=C3=A1draig=20Brady?= 
Date: Sat, 30 Sep 2017 17:08:02 -0700
Subject: [PATCH] build: reinstate distribution of man pages

man pages change little between systems,
so falling back to distributed pages make sense
when cross compiling or lacking perl.

* man/local.mk: Add all man pages to EXTRA_DIST
so that they're distributed in the generated tarball.
Use the dummy-man page generator if cross compiling.
Set TZ to avoid a distcheck failure where man pages
used a diffent month than those rebuilt (with a .timestamp).
* man/dummy-man: Only fall back to generating a stub
if copying an existing man page fails.
* NEWS: Mention the build-related change.
---
 NEWS  |  5 +
 man/dummy-man | 23 ---
 man/local.mk  | 16 +++-
 3 files changed, 28 insertions(+), 16 deletions(-)

diff --git a/NEWS b/NEWS
index 5d57c72..2878b70 100644
--- a/NEWS
+++ b/NEWS
@@ -11,6 +11,11 @@ GNU coreutils NEWS-*- outline -*-
   to attempt to hide the original length of the file name.
   [bug introduced in coreutils-8.28]
 
+** Build-related
+
+  Default man pages are now distributed which are used if perl is
+  not available on the build system, or when cross compiling.
+
 
 * Noteworthy changes in release 8.28 (2017-09-01) [stable]
 
diff --git a/man/dummy-man b/man/dummy-man
index f05ce2a..e298295 100755
--- a/man/dummy-man
+++ b/man/dummy-man
@@ -1,8 +1,7 @@
 #!/bin/sh
-# Poor man's placeholder for help2man invocation on systems lacking perl;
-# it generates a dummy man page stating that a proper one could not be
-# generated, and redirecting the user back to either the info
-# documentation or the '--help' output.
+# Poor man's placeholder for help2man invocation on systems lacking perl,
+# or when cross compiling.
+# It just copies the distributed man pages.
 
 set -e; set -u
 
@@ -24,12 +23,12 @@ while test $# -gt 0; do
 # Help2man options we recognize and handle.
 --output=*) output=`expr x"$1" : x'--output=\(.*\)'`;;
 --output) shift; output=$1;;
+--include=*) include=`expr x"$1" : x'--include=\(.*\)'`;;
+--include) shift; include=$1;;
 --source=*) source=`expr x"$1" : x'--source=\(.*\)'`;;
 --source) shift; source=$1;;
 # Recognize (as no-op) other help2man options that might be used
 # in the makefile.
---include=*);;
---include) shift;;
 --info-page=*);;
 -*) fatal_ "invalid or unrecognized help2man option '$1'";;
 --) shift; break;;
@@ -41,10 +40,13 @@ done
 test $# -gt 0 || fatal_ "missing argument"
 test $# -le 1 || fatal_ "too many non-option arguments"
 
+dist_man=$(printf '%s\n' "$include" | sed 's/\.x$/.1/')
+test -f "$dist_man" && cp "$dist_man" "$output" && exit || :
+
 baseout=`basename_ "$output"`
 sed 's/^/WARNING: /' >&2 <"$output"  $@-t			\
 	  && rm -rf $$t			\
 	  && chmod a-w $@-t		\
-	  && mv $@-t $@
+	  && rm -f $@ && mv $@-t $@
-- 
2.9.3

Bug#877368: RFS: yuma123/2.10-1

[Vladimir Vassilev]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "yuma123"

* Package name: yuma123
  Version : 2.10-1
  Upstream Author : Vladimir Vassilev 
* URL :https://sourceforge.net/projects/yuma123
* License : BSD
  Section : net

It builds those binary packages:

libyuma-base - Netconf configuration script, YANG models and documentation
libyuma-dev - Netconf/YANG development files
libyuma2   - Netconf/YANG library
netconfd   - netconf (RFC-6241) agent
netconfd-module-ietf-interfaces - SIL module for netconfd implementing 
ietf-interfaces.yang
netconfd-module-ietf-system - SIL module for netconfd implementing 
ietf-system.yang
yangcli- netconf/YANG command line client application

To access further information about this package, please visit the following 
URL:

https://mentors.debian.net/package/yuma123


Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/y/yuma123/yuma123_2.10-1.dsc

More information about yuma123 can be obtained fromhttp://yuma123.org/wiki   .

Changes since the last upload:

* New upstream release.


Regards,
 Vladimir Vassilev

Bug#871083: [Debian-med-packaging] Bug#871083: python-pysam: FTBFS: Test failures

[peter green]

On 30/09/17 21:43, Afif Elghraoui wrote:

The new upstream version is the solution to this problem, but we've been
going back and forth over issues  (fixing one, revealing another) in
updating the package. I'll see if I can do it today, but I don't
understand why this should be blocking python itself. It's not python
that broke this package-- it was updating some of its other dependencies
(htslib/samtools).

My understanding is that the new version of python 2.7 removed a module called 
"_PyFPE" and that C extensions referencing symbols from this module need to be 
rebuilt. This has been enforced by breaks in the python2.7 package. Your package is on 
said list.

So for the new python2.7 to migrate to testing the FTBFS in python-pysam needs 
to be fixed.

Bug#871484: fixed-upstream

[Stéphane Aulery]

This bug should be fixed with LO 6.0.0.

See https://bugs.documentfoundation.org/show_bug.cgi?id=59424#c11

-- 
Stéphane Aulery

Bug#877350: nm.d.o: tweak suggestions for the removal notice mail

[Clint Adams]

On Sat, Sep 30, 2017 at 09:22:52PM +0200, Mattia Rizzolo wrote:
> We regret to report that we have not been able to
> contact %NAME% (CC'd).

I object to "regret", whether it is sincere or not.

Bug#877367: www.debian.org: Please consider adding redirects for old Policy chapters/appendices

[Sean Whitton]

Package: www.debian.org
Severity: wishlist

Hello www-team,

I'd like to suggest adding redirects for the old chapters and appendices
of the Policy Manual, redirecting to the single HTML version, if
possible with anchor references.  E.g.

https://www.debian.org/doc/debian-policy/upgrading-checklist.html
--> https://www.debian.org/doc/debian-policy/#upgrading-checklist

https://www.debian.org/doc/debian-policy/ch-opersys.html
--> https://www.debian.org/doc/debian-policy/#the-operating-system

I've had several people suggest this, especially for the upgrading
checklist, on IRC.

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

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

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#877337: www.debian.org: Switch back to single page version of Policy Manual

[Sean Whitton]

Hello Laura,

On Sun, Oct 01 2017, Laura Arjona Reina wrote:

> I've applied your patch, and also reviewed our mvhtml_sphinx()
> function and adapted it to copy the 1-page manual and the _static and
> _images files only.
>
> (If in the future the package carries translations, we'll need to
> readapt this function to take care about the translations, too).
>
> After running the last website build,
> https://www.debian.org/doc/debian-policy seems to show the correct
> info.
>
> Since the old files were still there, I've logged in
> www-master.debian.org and removed them manually (together with some
> other .gz files of old versions of debian-policy). I believe that
> these changes will be visible in the next website build (the old files
> will be removed from mirrors too).

Many thanks for all your work on this today.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#853338: Andreas' NMU in DELAYED/7

[Adam Borowski]

Control: tags -1 +pending

> I've prepared a minimal NMU and will be looking for a sponsor.

I've put the NMU into DELAYED/7.  Preferred way to NACK is to upload a
better fix yourself, but if anything is wrong, please holler.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ We domesticated dogs 36000 years ago; together we chased
⣾⠁⢰⠒⠀⣿⡁ animals, hung out and licked or scratched our private parts.
⢿⡄⠘⠷⠚⠋⠀ Cats domesticated us 9500 years ago, and immediately we got
⠈⠳⣄ agriculture, towns then cities. -- whitroth on /.

Bug#877168: [Pkg-d-devel] Bug#877168: nmu: gtk-d_3.6.5-2

[Matthias Klumpp]

2017-09-30 15:52 GMT+02:00 Matthias Klumpp :
> 2017-09-30 11:30 GMT+02:00 Emilio Pozuelo Monfort :
>> [...]
>>> Agreed. Ideally we'd need to coordinate binNMUs on new ABI versions
>>> better, so thinks are rebuilt in order, and not randomly.
>>
>> Some coordination when things need special treatment is always good :)
>>
>> Let me know what is needed here and I'll help if I can.

What about this tracker, to really catch all the LDC stuff?

title = "ldc-phobos";
is_affected = .build-depends ~ /ldc/;
is_good = .depends ~ /\b(libphobos2\-ldc74)\b/;
is_bad = (.depends ~ /\b(libphobos2\-ldc73)\b/) | (.depends ~
/\b(libphobos2\-ldc72)\b/);
notes = "";

I couldn't test it, so maybe there are issues.
Thanks!
Matthias

-- 
I welcome VSRE emails. See http://vsre.info/

Bug#877348: stretch-pu: package vim/8.0.0197-4+deb9u1

[James McCoy]

On Sat, Sep 30, 2017 at 09:42:14PM +0100, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Sat, 2017-09-30 at 14:48 -0400, James McCoy wrote:
> > * Backport upstream patches to fix CVE-2017-11109  (Closes: #867720)
> >   + 8.0.0703: Illegal memory access with empty :doau command
> >   + 8.0.0706: Crash when cancelling the cmdline window in Ex mode
> >   + 8.0.0707: Freeing wrong memory when manipulating buffers in
> > autocommands
> > 
> 
> Please go ahead, bearing in mind that the window for 9.2 closes during
> this weekend.

Thanks!  Uploaded.

-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#877337: www.debian.org: Switch back to single page version of Policy Manual

[Laura Arjona Reina]

Hello Sean

El 30/09/17 a las 18:33, Sean Whitton escribió:
> 
> Please revert this, so the single page version is published on our web
> mirrors.  Here is a patch (against [1]; unfortunately, I'm not in a
> position to test it).  I'd appreciate it if this change could be made
> quickly, to avoid URLs to the multi page version ending up in too many
> mailing list posts/other documents.

I've applied your patch, and also reviewed our mvhtml_sphinx() function and
adapted it to copy the 1-page manual and the _static and _images files only.

(If in the future the package carries translations, we'll need to readapt this
function to take care about the translations, too).

After running the last website build, https://www.debian.org/doc/debian-policy
seems to show the correct info.

Since the old files were still there, I've logged in www-master.debian.org and
removed them manually (together with some other .gz files of old versions of
debian-policy). I believe that these changes will be visible in the next website
build (the old files will be removed from mirrors too).

I leave this bug open for the case further action is needed; if everything goes
well I'll close the bug in some days.

Best regards
-- 
Laura Arjona Reina
https://wiki.debian.org/LauraArjona

Bug#876252: mhddfs segfaults seemingly randomly (not from updatedb like other bug)

[Ben Gladstone]

Update: so far the patched version hasn't crashed on my system. No
guarantees but it looks like it's working

On Sep 20, 2017 1:24 AM, "Ben Gladstone"  wrote:

> Oh whoops reading fail, I missed that part. Thanks!
>
> On Sep 20, 2017 1:22 AM, "Roman Mamedov"  wrote:
>
>> On Wed, 20 Sep 2017 01:16:08 -0700
>> Ben Gladstone  wrote:
>>
>> > I'm just waiting to see if it crashes in the next week or so. Have you
>> tried
>> > that patch yet?
>>
>> As I have no crashes even without the patch, I can't provide any useful
>> testing. Perhaps I no longer hit that corner case which you still do.
>> Let's
>> hope it fixes that for you.
>>
>> --
>> With respect,
>> Roman
>>
>

Bug#877262: proper shell indenting does not work anymore

[James McCoy]

Control: tag -1 fixed-upstream

On Fri, Sep 29, 2017 at 10:13:03PM +0100, Klaus Ethgen wrote:
> Usually (with 7.x) when writing in shell scripts "if ...\nthen" the then
> start indented and gets not indented when the "n" is typed. With version
> 8, that is not working anymore and the then stays intended.

This specifically broke in the last upload, because 8.0.1041 introduced
a bug.  It will be fixed when an upload with 8.0.1154 happens.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#877366: stretch-pu: package abiword/3.0.2-2+deb9u1

[Jeremy Bicha]

Package: release.debian.org
X-Debbugs-Cc:abiw...@packages.debian.org
User: release.debian@packages.debian.org
Usertags: pu
Tags: stretch
Severity: normal

The attached debdiff fixes a flickering bug that makes Abiword nearly
unusable for some users.

https://bugs.debian.org/851052

The patch was rejected upstream because it doesn't work for GNOME on
Wayland. But Debian's GNOME does not default to Wayland in Stretch.
And Abiword is more commonly used on less powerful desktop
environments instead of the resource-intensive GNOME.

This patch was uploaded to unstable (and Ubuntu 17.10 Beta) as 3.0.2-3
just now. The package was uploaded with urgency: high so it should be
in testing in a few days. It builds on all architectures so far. I
didn't want to delay filing this bug in case it wasn't quite too late
for Debian 9.2. Sorry for the late request.

Thanks,
Jeremy Bicha


abiword-flickering-stretch.debdiff
Description: Binary data

Bug#877365: pjproject: source contains non-free files

[Jonas Smedegaard]

Source: pjproject
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

A recent inspection of copyright and licensing revealed several files
lacking proper licensing.

debian/copyright has been corrected, including hinting for repackaging
source - but I am not familiar with the git packaging routines so have
not the actual re-repackaging of source.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlnQJqMACgkQLHwxRsGg
ASGCThAAl8x1akM/W98csyTbcTbFiD4FAvDg5TiYy/kzg82gxmAfqmsHPFo03bqh
JziXsoivcxLcaUgRH8VA84U70z40zPKZK9UAqebETx1iFzxZhdedHGsTA2cTd+rY
xSCXN/irL4vqgDaskA+tNHW3kyMZqAm53qsI5K98WGq1FXeLdVzSqO+Iz62YfHip
1SiVCyH+/uxRzmFf3gZiffnazk2TUUDLnozA31Tp0hqBUBRcF5raStaACCgDN2Yd
8fwDxx6tazt8QAoIFk0rQs0Ppv5cb1c3hQztMEHjfkPxqk+Q/t7bYkx4i3MxF01W
YAwPkADnAJbvECDjG7Cj4BRZESj9hnazdbIhHge8uGRfYDI+qjLpFcxXoajKVXtB
yAJm32SuivgnGQTNnDcTfFy/w+4VwqpNO90SImKDCMrVYdN7o4eg5zJjmpJdWZk+
xMdb0Nnwv3X4/5KPdVaOrQDUKg8GY5hVB47sGEdklkM9OavQqtD35FlRtbHiq7p6
N2W4mZ7Mgtgduu3UQTyh5YXZYD9WNr6rMwyyyIpqqIXPh89NMMix3DxML87fYZCv
zbaLjaCNad0sOnHjGmUf3DsVbSrfQ4ozWckCdUxPQkmZZ5dUm4ZjhaLpmz2hsTv5
EDK++CWg8bdSvOnYtg2s4QoD1+AXgiaQCAlzdGjbFjd4FBNn9vk=
=F0Hi
-END PGP SIGNATURE-

Bug#877364: pjproject: source file licensed as BSD-4-clause and GPL-2+ effectively unlicensed

[Jonas Smedegaard]

Source: pjproject
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The file pjlib/src/pj/sock_linux_kernel.c is licensed as both
BSD-4-clause and GPL-2+. Not dual-licensed, but separately declared.
Those licenses are incompatible, and therefore the licensing is useless.


 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlnQJagACgkQLHwxRsGg
ASFrdA//Rl1lunFKUdJ6Tnq/VLbCBoxXk0cEmb3mZqW+KiEJjpLYD8prbenKxOWG
0ZkmCgS4WXtERRov/2kJe+gJOplpJCMKNvEISoDFnFDgn5zkFEfMDTFBJZSZtf5f
5HfWaXTd8+S6i6CQ5OKdxVgkW98SQJHqhn6/1nEbnoc5Fnxti9GoXpC6TTgNd0Lg
p/vgJrUYoe4GC67iPmynnHBZHqJ05jJ6BZ81cYkFZYg4gQDPHsQ8ACv9HhkkE7xf
4PoJnPOj3ZtUNKh0esl3rc14GIk/a2UNTJzJlWD/SKE/XEJELyoaxd7NW6qVT2m0
5y2+9+7fFo4xX7xvHXH20cP185ZOI/qZSrPHdyxmr/I1UZteTa+Yv2fIPm+anr3W
Hg8jva9OIUaiYj+anr1bK7ZSbvAE1atuob8hnL6o3As0E7u2D+6OY+mVCqXwLpdk
xmRHaqv2LPqJnB9EhA87lqtufX0MEMwL0MLCHzfwkTug6Anpd3T0qA/NcKqrZw60
WLrN4/iq2srrS98HZ6W2uqIuzQf9A630Z6brZ1ZLewInjJdGoQXwVe2SehxvuLm1
A6j0i9yY0uu17nJHftOWGhqVfTG3X2QxHwh8VxW5+g4VVu6s5Xd7uBIaoOjnLu2e
N9JeNCGWlw1tjGvR67S+C5MTeKc1Y3VBhKPDYs3yd4jNqChS2Y8=
=T4GA
-END PGP SIGNATURE-

Bug#876377: ruby2.3: Ruby process stuck on sched_yield busyloop

[Gregory Potamianos]

On Mon, Sep 25, 2017 at 11:44:52AM -0700, Antonio Terceiro wrote:
> Hi,
> 
> thanks for your bug report
> [...] 
> > Our case seems identical to this [1] bug report. We have applied the patch 
> > [2]
> > by Eric Wong and the problem seems resolved without causing any other 
> > problems.
> > 
> > [1] https://bugs.ruby-lang.org/issues/13794
> > [2] https://80x24.org/spew/20170809232533.14932-...@80x24.org/raw
> 
> can you provide a minimal test case that can reproduce the issue that
> does not take hours/days?
The attached script sometimes exits and leaves a stray child process on
busyloop when run as:

`while nice -n19 ruby sched_yield_loop.rb; do :; done`

> 
> Also, it would be nice to have some feedback from upstream about whether
> one of those patches is going to be applied. I would not like to to
> carry such patch indefinitely.
The patch i mentioned was just merged in [1] and seems to be tagged as
needing backport to v2.3 on ruby's bugtracker.

`
Backport changed from 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN to
2.2: UNKNOWN, 2.3: REQUIRED, 2.4: REQUIRED
`


[1] https://bugs.ruby-lang.org/projects/ruby-trunk/repository/revisions/60079


Kind regards,
-- 
Gregory Potamianos
Skroutz S.A
greg...@skroutz.gr


sched_yield_loop.rb
Description: application/ruby

Bug#877363: CVE-2017-14102

[Moritz Muehlenhoff]

Source: mimedefang
Severity: important
Tags: security

This was assigned CVE-2017-14102:
http://lists.roaringpenguin.com/pipermail/mimedefang/2017-August/038077.html

Fixed in 2.81:
http://lists.roaringpenguin.com/pipermail/mimedefang/2017-August/038085.html

Cheers,
Moritz

Bug#677484: libreoffice: Menu / submenu overlapping

[Stéphane Aulery]

Hello jEsuSdA,

What version is working for you please?

Reagrds,

-- 
Stéphane Aulery

Bug#877330: dpkg: tar (>= 1.28-1) is a build dependency

[William Herrin]

Thanks Niels,

I ended up removing the two conflicting tar options from the two files
which had them, and then striking the dependency from dpkg. For what I'm
doing, I don't need the .deb's to come up byte-identical when the source is
unchanged.

You are also correct; I could have just used debhelper from backports.

Regards,
Bill


On Sat, Sep 30, 2017 at 5:04 PM, Niels Thykier  wrote:

> On Sat, 30 Sep 2017 12:11:34 -0400 William Herrin 
> wrote:
> > Package: dpkg
> > Version: 1.18.24
> > Severity: normal
> >
> > Dear Maintainer,
> >
> > *** Reporter, please consider answering these questions, where
> appropriate ***
> >
> >* What led up to the situation?
> > Want to build quagga 1.1 on a Jessie machine
> > won't build because debhelper < version 10
> > [...]
>
> Hi,
>
> (Not the dpkg maintainer, but ...)
>
> Have you considered using the debhelper/10.2.5~bpo8+1 release from
> jessie-backports?  Assuming you just need debhelper (>= 10) that should
> be sufficient. :)
>
> FYI/FTR: The backported version of debhelper works without dpkg 1.18 by
> disabling some features[1].  I suspect none of them are critical for
> your use-case (although, the lack of dbgsym packages can be inconvenient)
>
> Thanks,
> ~Niels
>
> [1]
> >   * Existing changes from previous bpo releases:
> > - Disable automatic dbgsym as it requires dpkg-dev 1.18.2
> > - Revert of sgml-base trigger as it needs a newer version
> >   of sgml-base (Related bug: #825005)
>
>


-- 
William Herrin  her...@dirtside.com  b...@herrin.us
Dirtside Systems . Web: 

Bug#877347: [Packaging] Bug#877347: munin: Failing autopkgtest with 2.0.33-3

[Holger Levsen]

control: tags -1 + Help

Thanks for the bug report, Jeremy!

On Sat, Sep 30, 2017 at 02:42:35PM -0400, Jeremy Bicha wrote:
> munin's autopkgtest started failing in Debian and Ubuntu after
> 2.0.33-3 was uploaded.

how strange given there were 0 code changes.

> https://ci.debian.net/packages/m/munin/unstable/amd64/

any help fixing this is much welcome!


-- 
cheers,
Holger


signature.asc
Description: PGP signature

Bug#869404: resiprocate: CVE-2017-11521: Adding too many media connections may lead to memory exhaustion

[Moritz Muehlenhoff]

On Sun, Jul 23, 2017 at 07:55:20AM +0200, Salvatore Bonaccorso wrote:
> Source: resiprocate
> Version: 1:1.9.7-5
> Severity: grave
> Tags: upstream security
> Forwarded: https://github.com/resiprocate/resiprocate/pull/88
> 
> Hi,
> 
> the following vulnerability was published for resiprocate.
> 
> CVE-2017-11521[0]:
> | The SdpContents::Session::Medium::parse function in
> | resip/stack/SdpContents.cxx in reSIProcate 1.10.2 allows remote
> | attackers to cause a denial of service (memory consumption) by
> | triggering many media connections.
> 
> If you fix the vulnerability please also make sure to include the
> CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
> 
> For further information see:
> 
> [0] https://security-tracker.debian.org/tracker/CVE-2017-11521
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-11521
> [1] https://github.com/resiprocate/resiprocate/pull/88

What's the status, this is unfixed for many months now?

Cheers,
Moritz

Bug#877362: xtables-addons-source: Buffer overflow in xt_DNETMAP

[Loic]

Package: xtables-addons-source
Version: 2.12-0.1
Severity: important

Dear Maintainer,

prefix_str was only 16 bytes, but the largest emitted string could be
"255.255.255.255/32" (19 bytes).

xt_DNETMAP.c: In function "dnetmap_tg_check":
compat_xtables.h:46:22: warning: "%u" directive writing between 1 and 10
bytes into a region of size between 0 and 8 [-Wformat-overflow=]
# define NIPQUAD_FMT "%u.%u.%u.%u"
xt_DNETMAP.c:296:2: note: "sprintf" output between 10 and 27 bytes into
a destination of size 16
sprintf(p->prefix_str, NIPQUAD_FMT "/%u", NIPQUAD(mr->min_addr.ip),
33 - ffs(~(ip_min ^ ip_max)));

So, please apply this patch:
https://sourceforge.net/p/xtables-addons/xtables-addons/ci/1874fcd519eb5332b63bddcd76fadae9a8260798/

Thanks, regards

Bug#877361: CVE-2017-14609

[Moritz Muehlenhoff]

Source: kannel
Severity: important
Tags: security

Please see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14609
https://redmine.kannel.org/issues/771

Cheers,
Moritz
  

Bug#864535: ceph: CVE-2017-7519: libradosstriper processes arbitrary printf placeholders in user input

[Moritz Muehlenhoff]

On Sat, Jun 10, 2017 at 08:49:33AM +0200, Salvatore Bonaccorso wrote:
> Source: ceph
> Version: 10.2.5-7.2
> Severity: important
> Tags: security patch upstream
> Forwarded: http://tracker.ceph.com/issues/20240
> 
> Hi,
> 
> the following vulnerability was published for ceph.
> 
> CVE-2017-7519[0]:
> libradosstriper processes arbitrary printf placeholders in user input

> [1] http://tracker.ceph.com/issues/20240

According to the quoted bug that should now be fixed upstream.

Cheers,
Moritz

Bug#877360: please provide a tool to check for upload rejections

[Matthias Klose]

Package: ftp.debian.org
Severity: normal

The Debian upload system automatically rejects packages on a basis which can
determined by automatic checks.  Fro lintian related uploads I can check that by
running lintian -F on my planned upload, however there are some checks which I
cannot guard before, seeing that for my first gcc-8-cross upload attempt.

Please could you provide/document a method how to check for such upload 
rejections?

Thanks, Matthias

Bug#640462: libreoffice: default window appears partly off-screen

[Stéphane Aulery]

Hello Vincent,

Could you reproduce it with a current version please?

Regards,

-- 
Stéphane Aulery

Bug#836767: libreoffice-calc: Slow rendering of UI

[Stéphane Aulery]

Hello Emil,

Could you try to reproduce with the current version please?

It should be fixed now.

Regards,

-- 
Stéphane Aulery

Bug#877359: clang: precompiled headers are not reproducible

[Rebecca N. Palmer]

Package: clang-4.0
Version: 1:4.0.1-5
Severity: wishlist
User: reproducible-bui...@lists.alioth.debian.org
Usertags: toolchain randomness
Control: affects -1 beignet-opencl-icd liboclgrind-16.10
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Generating a .pch precompiled header with clang gives a different result 
each time, even when run with faketime (i.e. probably not a timestamp) 
and separately from the rest of the build process (i.e. probably not a 
filesystem ordering issue).


Possibly a pseudorandom ordering of something within the file?? e.g. the 
method pool hash table http://clang.llvm.org/docs/PCHInternals.html


There are ~12 packages that ship .pch files, but I suspect that only 2 
(beignet and oclgrind) actually build and use them in Debian; the rest 
look like either iOS/MacOS-only files (mostly documentation examples), 
or files that are called .pch but contain something entirely different.


$ faketime "2017-10-01 12:00:00" /usr/bin/clang-4.0 -cc1 -fno-builtin 
-ffp-contract=off -triple spir64 -cl-kernel-arg-info -fblocks 
-DGEN7_SAMPLER_CLAMP_BORDER_WORKAROUND -cl-std=CL2.0 
-D__OPENCL_C_VERSION__=200 -I 
/home/rnpalmer/Debian/builds/stackbuild/beignet/build2/backend/src/libocl//usr/local/lib/beignet//include/ 
--relocatable-pch -emit-pch -isysroot 
/home/rnpalmer/Debian/builds/stackbuild/beignet/build2/backend/src/libocl 
-x cl 
/home/rnpalmer/Debian/builds/stackbuild/beignet/build2/backend/src/libocl//usr/local/lib/beignet//include/ocl.h 
-o 
/home/rnpalmer/Debian/builds/stackbuild/beignet/build2/backend/src/libocl//usr/local/lib/beignet//beignet_20.pch

E: cowdancer: cannot fstat ilistfile /.ilist
Can't read /proc/cpuinfo: Cannot allocate memory
$ md5sum usr/local/lib/beignet/*.pch
d55df577aa72cefc69c5b39df3491841  usr/local/lib/beignet/beignet_20.pch
$ faketime "2017-10-01 12:00:00" /usr/bin/clang-4.0 -cc1 -fno-builtin 
-ffp-contract=off -triple spir64 -cl-kernel-arg-info -fblocks 
-DGEN7_SAMPLER_CLAMP_BORDER_WORKAROUND -cl-std=CL2.0 
-D__OPENCL_C_VERSION__=200 -I 
/home/rnpalmer/Debian/builds/stackbuild/beignet/build2/backend/src/libocl//usr/local/lib/beignet//include/ 
--relocatable-pch -emit-pch -isysroot 
/home/rnpalmer/Debian/builds/stackbuild/beignet/build2/backend/src/libocl 
-x cl 
/home/rnpalmer/Debian/builds/stackbuild/beignet/build2/backend/src/libocl//usr/local/lib/beignet//include/ocl.h 
-o 
/home/rnpalmer/Debian/builds/stackbuild/beignet/build2/backend/src/libocl//usr/local/lib/beignet//beignet_20.pch

E: cowdancer: cannot fstat ilistfile /.ilist
Can't read /proc/cpuinfo: Cannot allocate memory
$ md5sum usr/local/lib/beignet/*.pch
e61f28727c32337a63bddced613fcf78  usr/local/lib/beignet/beignet_20.pch

Bug#869746: where to assign this bug

[積丹尼 Dan Jacobson]

> "TA" == Timo Aaltonen  writes:
TA> so you have nvidia installed..

Yes, lots of
libgl1-nvidia-legacy-304xx-glx:amd64/unstable 304.135-5 uptodate
libnvidia-legacy-304xx-cfg1:amd64/unstable 304.135-5 uptodate
libnvidia-legacy-304xx-glcore:amd64/unstable 304.135-5 uptodate
libnvidia-legacy-304xx-ml1:amd64/unstable 304.135-5 uptodate
nvidia-legacy-304xx-alternative:amd64/unstable 304.135-5 uptodate
nvidia-legacy-304xx-driver-bin:amd64/unstable 304.135-5 uptodate
nvidia-legacy-304xx-driver-libs:amd64/unstable 304.135-5 uptodate
nvidia-legacy-304xx-driver:amd64/unstable 304.135-5 uptodate
nvidia-legacy-304xx-kernel-dkms:amd64/unstable 304.135-5 uptodate
nvidia-legacy-304xx-kernel-support:amd64/unstable 304.135-5 uptodate
nvidia-legacy-304xx-vdpau-driver:amd64/unstable 304.135-5 uptodate
nvidia-settings-legacy-304xx:amd64/unstable 304.134-1 uptodate
xserver-xorg-legacy:amd64/unstable 2:1.19.3-2 uptodate
xserver-xorg-video-nvidia-legacy-304xx:amd64/unstable 304.135-5 uptodate
etc.

Bug#877358: perldoc -f '<<' POD ERRORS

[積丹尼 Dan Jacobson]

Package: perl-doc
Version: 5.26.0-8
Severity: minor

$ perldoc -f '<<'|tail
rule is that the identifier must be a string literal. Stick with
that, and you should be safe.

POD ERRORS
Hey! The above document had some coding errors, which are explained
below:

Around line 198:
=back without =over

Bug#877357: debhelper: Make qmake buildsystem support cross building

[Dmitry Shachnev]

Package: debhelper
Version: 10.9
Severity: wishlist
Tags: patch

Dear debhelper maintainers,

I am attaching two patches against Git master that should make packages
using qmake buildsystem cross-buildable (at least some of them).

The first patch sets the proper toolchain commands, the second one adds
a very basic qt.conf so that qmake searches for Qt headers in a proper
location. It was enough in my case, but we may extend it with other paths
later if needed.

--
Dmitry Shachnev
From bc931b90ae9181c63957c4038c64d94add6a9c0b Mon Sep 17 00:00:00 2001
From: Dmitry Shachnev 
Date: Sat, 30 Sep 2017 23:38:29 +0300
Subject: [PATCH 1/2] qmake.pm: Add initial support for cross-building

---
 lib/Debian/Debhelper/Buildsystem/qmake.pm | 21 -
 1 file changed, 20 insertions(+), 1 deletion(-)

diff --git a/lib/Debian/Debhelper/Buildsystem/qmake.pm b/lib/Debian/Debhelper/Buildsystem/qmake.pm
index c39c2474..9618334f 100644
--- a/lib/Debian/Debhelper/Buildsystem/qmake.pm
+++ b/lib/Debian/Debhelper/Buildsystem/qmake.pm
@@ -8,7 +8,7 @@ package Debian::Debhelper::Buildsystem::qmake;
 
 use strict;
 use warnings;
-use Debian::Debhelper::Dh_Lib qw(error);
+use Debian::Debhelper::Dh_Lib qw(dpkg_architecture_value error is_cross_compiling);
 use parent qw(Debian::Debhelper::Buildsystem::makefile);
 
 our $qmake="qmake";
@@ -52,6 +52,10 @@ sub configure {
 
 	push @options, '-makefile';
 	push @options, '-nocache';
+	if (is_cross_compiling()) {
+		# Force generic mkspec to avoid -m32 / -m64 flags
+		push @options, ("-spec", "linux-g++");
+	}
 
 	if ($ENV{CFLAGS}) {
 		push @flags, "QMAKE_CFLAGS_RELEASE=$ENV{CFLAGS} $ENV{CPPFLAGS}";
@@ -68,6 +72,21 @@ sub configure {
 	push @flags, "QMAKE_STRIP=:";
 	push @flags, "PREFIX=/usr";
 
+	if (is_cross_compiling()) {
+		if ($ENV{CC}) {
+			push @flags, "QMAKE_CC=" . $ENV{CC};
+		} else {
+			push @flags, "QMAKE_CC=" . dpkg_architecture_value("DEB_HOST_GNU_TYPE") . "-gcc";
+		}
+		if ($ENV{CXX}) {
+			push @flags, "QMAKE_CXX=" . $ENV{CXX};
+		} else {
+			push @flags, "QMAKE_CXX=" . dpkg_architecture_value("DEB_HOST_GNU_TYPE") . "-g++";
+		}
+		push @flags, "QMAKE_LINK=\$(CXX)";
+		push @flags, "PKG_CONFIG=" . dpkg_architecture_value("DEB_HOST_GNU_TYPE") . "-pkg-config";
+	}
+
 	$this->mkdir_builddir();
 	$this->doit_in_builddir($qmake, @options, @flags, @_);
 }
-- 
2.14.2

From 32c2f3ce473f40f8711c7a6ed2220d7fd51aeea0 Mon Sep 17 00:00:00 2001
From: Dmitry Shachnev 
Date: Sat, 30 Sep 2017 23:55:31 +0300
Subject: [PATCH 2/2] qmake.pm: Use a custom qt.conf file for cross builds

---
 lib/Debian/Debhelper/Buildsystem/qmake.pm | 9 +
 1 file changed, 9 insertions(+)

diff --git a/lib/Debian/Debhelper/Buildsystem/qmake.pm b/lib/Debian/Debhelper/Buildsystem/qmake.pm
index 9618334f..c25206a8 100644
--- a/lib/Debian/Debhelper/Buildsystem/qmake.pm
+++ b/lib/Debian/Debhelper/Buildsystem/qmake.pm
@@ -8,6 +8,7 @@ package Debian::Debhelper::Buildsystem::qmake;
 
 use strict;
 use warnings;
+use File::Temp qw(tempfile);
 use Debian::Debhelper::Dh_Lib qw(dpkg_architecture_value error is_cross_compiling);
 use parent qw(Debian::Debhelper::Buildsystem::makefile);
 
@@ -55,6 +56,14 @@ sub configure {
 	if (is_cross_compiling()) {
 		# Force generic mkspec to avoid -m32 / -m64 flags
 		push @options, ("-spec", "linux-g++");
+
+		my ($fh, $filename) = tempfile("qt.", SUFFIX => ".conf", TMPDIR => 1, UNLINK => 1);
+		$fh->print("[Paths]\n");
+		$fh->print("Prefix=/usr\n");
+		$fh->print("HostData=lib/" . dpkg_architecture_value("DEB_HOST_GNU_TYPE") . "/qt5\n");
+		$fh->print("Headers=include/" . dpkg_architecture_value("DEB_HOST_GNU_TYPE") . "/qt5\n");
+		close $fh;
+		push @options, ("-qtconf", $filename);
 	}
 
 	if ($ENV{CFLAGS}) {
-- 
2.14.2



signature.asc
Description: PGP signature

Bug#877312: Compatibility with desktop session or systemd started ibus etc.

[Simon McVittie]

On Sat, 30 Sep 2017 at 22:36:06 +0900, Osamu Aoki wrote:
> This is a placeholder bug to discuss how Debian's glue hook code for the
> keyboard input method (currently, my humble im-config) should be moving

If im-config is started as a D-Bus session service (with a file
in /usr/share/dbus-1/services, like xdg-desktop-portal-gtk), then it is
advantageous (and very simple) to add a systemd user-service, like I did
for xdg-desktop-portal-gtk. This will be used if dbus-user-session is
installed and active (requires systemd-logind and systemd as pid 1),
and ignored if not. It makes the process inheritance and cgroup tree
look like this:

systemd pid 1
|- (system services)
\- systemd --user for uid 1000
|- dbus.service
|   \- dbus-daemon --session
\- your-daemon.service
\- your daemon

(so systemd --user knows your daemon is a separate thing and not part
of dbus-daemon). Traditional D-Bus activation looks more like this:

systemd pid 1
|- (system services)
\- systemd --user for uid 1000
\- dbus.service
\- dbus-daemon --session
   \- your daemon

which misrepresents the relationship between dbus-daemon and your
daemon, and makes it harder for a user or sysadmin to terminate,
restart or disable your daemon.

If im-config is not a D-Bus session service then the equivalent of
https://github.com/flatpak/xdg-desktop-portal-gtk/pull/52 is not
directly applicable.

> If ibus is started outside of im-config, it may be better to
> automatically set im-config to set to "REMOVE".  (I think Ubuntu at one
> point in history did so under Unity.)

Sorry, I don't know how im-config works.

If ibus is made available as a systemd user service, and everything that
would start ibus knows how to start it as a systemd user service (or via
D-Bus activation, having configured dbus-daemon to start ibus as a systemd
user service), then that has the advantage that you will not accidentally
get two copies of ibus running and fighting with each other.

There will need to be a fallback code path for systems that do not run
`systemd --user`, which might involve traditional D-Bus activation, or
running ibus directly.

> Also, I am wondering if all wayland based environment
> get started after executing /etc/X11/Xsession.d/*

Wayland-based environments do not execute /etc/X11/Xsession.d/*.
They do launch /etc/xdg/autostart/*.desktop (at least, GNOME does,
and I would be very surprised if KDE doesn't).

Traditional X11 desktop environments do execute /etc/X11/Xsession.d/*.
The scripts in /etc/X11/Xsession.d/ could have logic like this:

if systemd --user is available
ask systemd --user to start my service if necessary
else
use traditional implementation

if that's what you want?

> ... especially it's confusing how dbus etc. work.

Wayland-based environments currently rely on systemd --user and
dbus-user-session to start the session dbus-daemon. There could be a
non-systemd implementation, but as far as I know nobody has written it.

> Maybe this kind of hook script is not
> needed any more.  Maybe we should also place hook code at some other
> place to be compatible with the new situation such as wayland.

Please describe which daemons/services you need to start, what
configuration those daemons/services need, and which processes need to
be able to connect to those daemons/services? With that information,
perhaps someone can suggest a design.

smcv

Bug#877356: yojson: Please consider putting /usr/bin/ydump into its own binary package

[Johannes Schauer]

Source: yojson
Version: 1.3.2-1+b1
Severity: wishlist

Hi,

currently /usr/bin/ydump is part of the libyojson-ocaml-dev binary
package. Due to an ongoing OCaml transition, that package has been
uninstallable for a while.

The botch binary package needs /usr/bin/ydump for some of its
functionality and thus Depends on libyojson-ocaml-dev. But since
libyojson-ocaml-dev is uninstallable, so is botch.

Since, OCaml is statically linked, the problem could be averted by
putting /usr/bin/ydump in its own binary package. Then botch could just
depend on that new binary package instead of depending on
libyojson-ocaml-dev.

The advantage would be that in situations like right now during an OCaml
transition, botch would still be installable.

Thanks!

cheers, josch

Bug#855268: I wrote a systemd service which I have packaged with my packages and these seems to work well.

[Eliezer Croitoru]

I have packaged the latest versions of 3.5 for Debian with system service
file and not init.d
For me it works fine, it can be found at:
http://ngtech.co.il/repo/debian/

I have just started my cycle of 4.0.21 testing and I packaged it for CentOS
7 and couple other RPM based systems.
If someone wants me to start packaging 4.0.x for Debian 8+9 I can oribably
sit on it in the next month.

All The Bests,
Eliezer


Eliezer Croitoru
Linux System Administrator
Mobile: +972-5-28704261
Email: elie...@ngtech.co.il

Bug#780607: libreoffice-writer: TrueType Hebrew fonts have stopped working in Writer

[Stéphane Aulery]

Hello Celejar,

Do you still have this problem with your current version of LO?

I can't find any bug like that in LO bugtracker.

Regards,

-- 
Stéphane Aulery

Bug#877330: dpkg: tar (>= 1.28-1) is a build dependency

[Niels Thykier]

On Sat, 30 Sep 2017 12:11:34 -0400 William Herrin 
wrote:
> Package: dpkg
> Version: 1.18.24
> Severity: normal
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>* What led up to the situation?
> Want to build quagga 1.1 on a Jessie machine
> won't build because debhelper < version 10
> [...]

Hi,

(Not the dpkg maintainer, but ...)

Have you considered using the debhelper/10.2.5~bpo8+1 release from
jessie-backports?  Assuming you just need debhelper (>= 10) that should
be sufficient. :)

FYI/FTR: The backported version of debhelper works without dpkg 1.18 by
disabling some features[1].  I suspect none of them are critical for
your use-case (although, the lack of dbgsym packages can be inconvenient)

Thanks,
~Niels

[1]
>   * Existing changes from previous bpo releases:
> - Disable automatic dbgsym as it requires dpkg-dev 1.18.2
> - Revert of sgml-base trigger as it needs a newer version
>   of sgml-base (Related bug: #825005)

Bug#871083: [Debian-med-packaging] Bug#871083: python-pysam: FTBFS: Test failures

[Afif Elghraoui]

على السبت 30 أيلول 2017 ‫16:43، كتب Afif Elghraoui:
>  I'll see if I can do it today,

I see Andreas Tille is on top of this. The current issue right now is
this upstream bug we encounter when trying to build the latest upstream
version:

https://github.com/pysam-developers/pysam/issues/542

regards
Afif

-- 
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name

Bug#871083: [Debian-med-packaging] Bug#871083: python-pysam: FTBFS: Test failures

[Afif Elghraoui]

Hi, Peter,

على السبت 30 أيلول 2017 ‫09:18، كتب peter green:
> Any ETA on fixing this? it is blocking the migration of python2.7 to testing.
> 
> I notice that the package tracker claims that there is a new upstream version 
> available.
> 

The new upstream version is the solution to this problem, but we've been
going back and forth over issues  (fixing one, revealing another) in
updating the package. I'll see if I can do it today, but I don't
understand why this should be blocking python itself. It's not python
that broke this package-- it was updating some of its other dependencies
(htslib/samtools).

regards
Afif

-- 
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name

Bug#877348: stretch-pu: package vim/8.0.0197-4+deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Sat, 2017-09-30 at 14:48 -0400, James McCoy wrote:
> * Backport upstream patches to fix CVE-2017-11109  (Closes: #867720)
>   + 8.0.0703: Illegal memory access with empty :doau command
>   + 8.0.0706: Crash when cancelling the cmdline window in Ex mode
>   + 8.0.0707: Freeing wrong memory when manipulating buffers in
> autocommands
> 

Please go ahead, bearing in mind that the window for 9.2 closes during
this weekend.

Regards,

Adam

Bug#867591: libreoffice-writer: bug or no bug? Libreoffice-dmath inhibits to open gallery in libreoffice-writer

[Stéphane Aulery]

Hello,

I can't test with stable but in testing I have no problem like that.

Regards,

-- 
Stéphane Aulery

Bug#877355: imagemagick: CVE-2017-14625: NULL pointer dereference flaw in sixel_output_create in coders/sixel.c

[Salvatore Bonaccorso]

Source: imagemagick
Version: 8:6.9.7.4+dfsg-11
Severity: important
Tags: security patch upstream
Forwarded: https://github.com/ImageMagick/ImageMagick/issues/721

Hi,

the following vulnerability was published for imagemagick.

CVE-2017-14625[0]:
| ImageMagick 7.0.7-0 Q16 has a NULL Pointer Dereference vulnerability in
| the function sixel_output_create in coders/sixel.c.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-14625
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14625
[1] https://github.com/ImageMagick/ImageMagick/issues/721

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#789927: This is bug in anthy

[astian]

Osamu Aoki:
> control: severity -1 important
> control: tags -1 pending
> thanks
> 
> Hi
> 
> With the delayed 7 day upload of anthy, this problem is gone.
> 
> Osamu

Hi, thanks for working on this.  Newbie question: How should one
proceed in order to test this kind of patches (which change the
relationship between packages)?  Setting up a local repository
containing the relevant packages and a higher than normal priority?

Cheers.

Bug#877353: acpica-unix FTBFS on mips64el: error: cast from pointer to integer of different size

[Adrian Bunk]

Source: acpica-unix
Version: 20170831-1
Severity: serious
Tags: patch

https://buildd.debian.org/status/fetch.php?pkg=acpica-unix&arch=mips64el&ver=20170831-1&stamp=1506550333&raw=0

...
-  Intermediate obj/aslcompilerparse.c
/<>/generate/unix/iasl/obj/aslcompiler.y: In function 
'AslCompilerparse':
/<>/generate/unix/iasl/obj/aslcompiler.y:1089:60: error: cast from 
pointer to integer of different size [-Werror=pointer-to-int-cast]
 | PARSEOP_NAMESTRING{$$ = TrCreateValuedLeafOp 
(PARSEOP_NAMESTRING, (ACPI_NATIVE_INT) $1);}
^
/<>/generate/unix/iasl/obj/aslcompiler.y:1090:60: error: cast from 
pointer to integer of different size [-Werror=pointer-to-int-cast]
 | PARSEOP_IO{$$ = TrCreateValuedLeafOp 
(PARSEOP_NAMESTRING, (ACPI_NATIVE_INT) "IO");}
^
/<>/generate/unix/iasl/obj/aslcompiler.y:1091:60: error: cast from 
pointer to integer of different size [-Werror=pointer-to-int-cast]
 | PARSEOP_DMA   {$$ = TrCreateValuedLeafOp 
(PARSEOP_NAMESTRING, (ACPI_NATIVE_INT) "DMA");}
^
/<>/generate/unix/iasl/obj/aslcompiler.y:1092:60: error: cast from 
pointer to integer of different size [-Werror=pointer-to-int-cast]
 | PARSEOP_IRQ   {$$ = TrCreateValuedLeafOp 
(PARSEOP_NAMESTRING, (ACPI_NATIVE_INT) "IRQ");}
^
/<>/generate/unix/iasl/obj/aslcompiler.y:1093:60: error: cast from 
pointer to integer of different size [-Werror=pointer-to-int-cast]
 | PARSEOP_FOR   {$$ = TrCreateValuedLeafOp 
(PARSEOP_NAMESTRING, (ACPI_NATIVE_INT) "FOR");}
^
/<>/generate/unix/iasl/obj/aslcompiler.y:1104:41: error: cast from 
pointer to integer of different size [-Werror=pointer-to-int-cast]
 (ACPI_NATIVE_INT) AslCompilerlval.s);}
 ^
/<>/generate/unix/iasl/obj/aslcompiler.y:1474:41: error: cast from 
pointer to integer of different size [-Werror=pointer-to-int-cast]
 (ACPI_NATIVE_INT) AslCompilerlval.s);}
 ^
cc1: all warnings being treated as errors
Makefile:344: recipe for target 'obj/aslcompilerparse.o' failed
make[3]: *** [obj/aslcompilerparse.o] Error 1



The fix is attached.
Description: Stop listing all 64bit architectures
 Check __LP64__ instead of maintaining a list of all
 64bit architectures.
Author: Adrian Bunk 

--- acpica-unix-20170831.orig/source/include/platform/aclinux.h
+++ acpica-unix-20170831/source/include/platform/aclinux.h
@@ -208,9 +208,7 @@
 #define ACPI_FLUSH_CPU_CACHE()
 #define ACPI_CAST_PTHREAD_T(Pthread) ((ACPI_THREAD_ID) (Pthread))
 
-#if defined(__ia64__)|| defined(__x86_64__) ||\
-defined(__aarch64__) || defined(__PPC64__) ||\
-defined(__s390x__)
+#if defined(__LP64__)
 #define ACPI_MACHINE_WIDTH  64
 #define COMPILER_DEPENDENT_INT64long
 #define COMPILER_DEPENDENT_UINT64   unsigned long

Bug#877354: imagemagick: CVE-2017-14624: NULL pointer dereference flaw in PostscriptDelegateMessage in coders/ps.c

[Salvatore Bonaccorso]

Source: imagemagick
Version: 8:6.9.7.4+dfsg-11
Severity: important
Tags: patch upstream security
Forwarded: https://github.com/ImageMagick/ImageMagick/issues/722

Hi,

the following vulnerability was published for imagemagick.

CVE-2017-14624[0]:
| ImageMagick 7.0.7-0 Q16 has a NULL Pointer Dereference vulnerability in
| the function PostscriptDelegateMessage in coders/ps.c.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-14624
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14624
[1] https://github.com/ImageMagick/ImageMagick/issues/722

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#877212: [Pkg-javascript-devel] Bug#877212: Bug#877212: node-d3-color: B-D npm not available in testing

[Julien Puydt]

Hi,

Le 30/09/2017 à 21:06, Jérémy Lal a écrit :
>
> I did a quick check on acorn and rollup and i fail to see how
> acorn-object-spread
> is related to these modules. Even the github issue is not really explicit.
> Can you explain please ?

The dep thread is the following: rollup needs rollup-plugin-buble, which
needs buble, which needs acorn-object-spread ; and acorn-object-spread
is written for an older version of acorn than what we have in Debian.

Snark on #debian-js

Bug#838262: libreoffice-calc: Renders wrong characters in sheet after some time

[Stéphane Aulery]

Hello,

Do you still have the same behaviour with a current version please?

Regards,

-- 
Stéphane Aulery

Bug#865210: xdg-utils: New upstream version

[Коля Гурьев]

forwarded 865210 https://bugs.freedesktop.org/show_bug.cgi?id=101640
stop

Hi,

In the latest upstream version, autotests are faulty. Therefore, I
believe we have to refrain from updating the package right now.

I provided a patch[1] to fix some kind of errors, but I'd like to wait
for review from upstream authors.

I've put the link to an upstream bug in the tests into forwarded field
to track changes there.

 [1]: https://bugs.freedesktop.org/attachment.cgi?id=134577

Bug#877345: tmux: Clearing output with Ctrl+L does not work when using tmux

[Romain Francoise]

Hi,

On Sat, Sep 30, 2017 at 09:25:59PM +0300, Vincas Dargis wrote:
> I have discovered that pressing Ctrl+L while in Konsole (KDE) within
> tmux session does move cursor to the top of the console, but it does not
> clear all previous output below.

This is probably a duplicate of #876362, can you try with konsole from
experimental?

Thanks,
-- 
Romain Francoise 
https://people.debian.org/~rfrancoise/

Bug#877212: [Pkg-javascript-devel] Bug#877212: node-d3-color: B-D npm not available in testing

[Sean Whitton]

Hello,

On Sat, Sep 30 2017, Christian Seiler wrote:

> Ack. Wouldn't it be preferable to just include a copy of the prebuilt
> node-d3-color "binary" alongside its actual source tarball and have
> debian/rules just copy the prebuilt "binary" for now? That would
> fulfill one of the widely accepted use cases for contrib (needs
> something currently not in Debian to build, but is otherwise free
> software - see e.g. the VirtualBox BIOS requiring a non-free compiler)
> much closer than downloading stuff from the network.

This does seem preferable to the current situation.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#877352: openexr:CVE-2017-12596

[Salvatore Bonaccorso]

Source: openexr
Version: 2.2.0-11.1
Severity: important
Tags: upstream security
Forwarded: https://github.com/openexr/openexr/issues/238

Hi,

the following vulnerability was published for openexr, filling this
bug to track the upstream issue at [1].

CVE-2017-12596[0]:
| In OpenEXR 2.2.0, a crafted image causes a heap-based buffer over-read
| in the hufDecode function in IlmImf/ImfHuf.cpp during exrmaketiled
| execution; it may result in denial of service or possibly unspecified
| other impact.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-12596
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12596
[1] https://github.com/openexr/openexr/issues/238

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#836935: libreoffice-gtk3: Setting GDK_SCALE and GDK_DPI_SCALE to values other than 1 screws up rendering

[Stéphane Aulery]

Hello,

I tested with your command and LO 5.4.1-1 and the result is not bad.
Could you look into my screenshot Christian?

Regards,

-- 
Stéphane Aulery

Bug#877212: [Pkg-javascript-devel] Bug#877212: node-d3-color: B-D npm not available in testing

[Christian Seiler]

On 09/30/2017 09:10 PM, Sean Whitton wrote:
> On Sun, Oct 01 2017, Pirate Praveen wrote:
>> Packaging of rollup is stuck [1] and I can make progress with gitlab
>> package with node-d3-color in contrib. Quite a lot of work can happen
>> even with gitlab in contrib, like making sure everything is configured
>> correctly, making sure update from previous version is working, people
>> can test and report bugs while we are working on getting all
>> dependencies in main etc. If I simply wait for rollup to arrive in
>> main, I can't do any of those.
> 
> Okay, I see how this would be useful -- thanks for the explanation.
> 
> I am still very uneasy about serving our users -- even our users of
> Debian unstable -- with packages that are built using material pulled
> from the net.  I think that people who add 'contrib' to their
> sources.list do not expect this kind of thing.

Ack. Wouldn't it be preferable to just include a copy of the prebuilt
node-d3-color "binary" alongside its actual source tarball and have
debian/rules just copy the prebuilt "binary" for now? That would
fulfill one of the widely accepted use cases for contrib (needs
something currently not in Debian to build, but is otherwise free
software - see e.g. the VirtualBox BIOS requiring a non-free
compiler) much closer than downloading stuff from the network.

I think that requiring network access during build is a big no-no in
general, regardless of where the software is sorted into. For
example it fails the dissident test. And it ensures that that what's
in the Debian source package is that what you actually get in the
end, not subject to the whim of server operators outside of Debian
during build time (which may be at any point as there are binNMUs).

Regards,
Christian

Bug#877350: nm.d.o: tweak suggestions for the removal notice mail

[Ian Jackson]

Mattia Rizzolo writes ("Bug#877350: nm.d.o: tweak suggestions for the removal 
notice mail"):
...
> The Front Desk and Missing In Action Teams have been trying to trace
> this developer since %DATE1%; we sent the last mail on %DATE2%.
> Our search process is tracked here:
>https://nm.debian.org/process/%NUMBER%
...
> As a first comment, I have to say that reporting the date of first
> contact is annoying, as the first contact by the MIA team is not done
> through nm.d.o but completely manually, so at the very least that's one
> information the person doing the WAT ping has to copy manually over.

I wrote the suggestion without knowing what data was available.

How about:

 The Front Desk and Missing In Action Teams have been trying to trace
 this developer since before %DATE1%; we sent the last mail on
 %DATE2%.  Our search process is tracked here:
https://nm.debian.org/process/%NUMBER%

Then you can use the first tracked entry.

Ian.

Bug#877294: gnudatalanguage: gdl segfaults while running testsuite

[Ole Streicher]

The buildd (of 0.9.7-2b1) contains the list of failed tests (partially
with segfaults):

test_bug_3275334
test_file_search
test_hdf5
test_obj_isa
test_qhull
test_sem
test_tv
test_window_background

The CI tests contain lists of tests (d/tests/test-gdl.(xfail|ignore))
that are known to fail (and which are excluded there, or marked as
xfail). The only test from above that are not on the CI xfail/ignore
list is "test_file_search", which does not segfault according to the
build log:

% TEST_SPECIAL_PATHS: Error on operation : pb with ~
% TEST_SPECIAL_PATHS:   1 errors encoutered during TEST_SPECIAL_PATHS
tests

This may have something to do with a missing home dir.

I am not sure what to do with this bug; I think that I already reported
the problems upstream, so they are aware.

Bug#876875: FTBFS in reproducible, but not everywhere else

[Adrian Bunk]

Control: severity -1 normal

These FTBFS are in reproducible builds reliably present in sid
and not in buster:
https://tests.reproducible-builds.org/debian/history/golang-github-approvals-go-approval-tests.html
https://tests.reproducible-builds.org/debian/history/packer.html
https://tests.reproducible-builds.org/debian/history/golang-github-gin-gonic-gin.html

For unknown reasons they are not easily reproducible elsewhere.

I am keeping these bugs open for now, but with lowered severity.

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#877351: libkf5kdegames-dev: cmake config generates wrong include paths

[Yann Dirson]

Package: libkf5kdegames-dev
Version: 4:16.08.3-1
Severity: important

Using KDEGAMES_INCLUDE_DIRS in a CMakeLists file does not work as
expected, we get this on commandline:

 -I/usr/lib/x86_64-linux-gnu/cmake/KF5KDEGames
 -I/usr/lib/x86_64-linux-gnu/cmake/KF5KDEGames/KDE

The source of the problem seems quite obvious in 
/usr/lib/x86_64-linux-gnu/cmake/KF5KDEGames/KF5KDEGamesConfig.cmake:

 # compute paths
 get_filename_component(KDEGAMES_CMAKE_DIR "${CMAKE_CURRENT_LIST_FILE}" PATH)
 set(KDEGAMES_INCLUDE_DIR "${KDEGAMES_CMAKE_DIR}/")
 set(KDEGAMES_INCLUDE_DIRS "${KDEGAMES_INCLUDE_DIR}" 
"${KDEGAMES_INCLUDE_DIR}/KDE")


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

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

Versions of packages libkf5kdegames-dev depends on:
ii  libkf5completion-dev5.28.0-1
ii  libkf5declarative-dev   5.28.0-1
ii  libkf5kdegames7 4:16.08.3-1
ii  libkf5kdegamesprivate1  4:16.08.3-1
ii  qtbase5-dev 5.7.1+dfsg-3+b1

libkf5kdegames-dev recommends no packages.

libkf5kdegames-dev suggests no packages.

-- no debconf information

Bug#877350: nm.d.o: tweak suggestions for the removal notice mail

[Mattia Rizzolo]

Package: nm.debian.org
X-Debbugs-Cc: Ian Jackson 

We receive complaints about the removal notice that is sent to
d-private.

Fortunately, there wes one suggestion from Ian, I'm reporting this here,
as this is the appropriate forum to discuss such improvements, not
d-private@.


Dear debian-private,

We regret to report that we have not been able to
contact %NAME% (CC'd).

The Front Desk and Missing In Action Teams have been trying to trace
this developer since %DATE1%; we sent the last mail on %DATE2%.
Our search process is tracked here:
   https://nm.debian.org/process/%NUMBER%

If you think you can help us get in touch with %NAME% please let us
know now by replying to this email or, for a more confidential
channel, replace debian-private with w...@debian.org.

Unfortunately, in the absence of a better alternative, we will have
to shut down this developer's accounts on %DEADLINE%.

Thanks for your attention,

For Front Desk / MIA team,
%AUTHOR%


For comparison, this is what is currently used:

Dear debian-private,

This mail is a notice for the removal of {{person.fullname}} 
({{person.uid}}, in CC)
after failed contact attempts by the Front Desk and Missing In Action teams.

{{text|safe}}

The process is tracked at [1].

The account will be shut down after {{deadline|date:"F d, Y"}}.

If you know something about the situation of {{person.fullname}} please let 
us
know now by replying to this email or, for a more confidential channel, 
replace
debian-private with w...@debian.org.  Please keep the archive address in CC 
in
both cases.

For Front Desk / MIA team,
{{visitor.fullname}}




As a first comment, I have to say that reporting the date of first
contact is annoying, as the first contact by the MIA team is not done
through nm.d.o but completely manually, so at the very least that's one
information the person doing the WAT ping has to copy manually over.


-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#853349: codeblocks: Patch for the build-failure

[David Paleino]

Please go ahead, I currently don't have time :(

David
(sorry for topquoting, replying from my mobile)

Il 30 Set 2017 20:51, "Andreas Moog"  ha scritto:

> Control: tags 853349 + patch
>
> Dear maintainer,
>
> this particular error is fixed already in upstream's SVN repo:
>
> https://sourceforge.net/p/codeblocks/code/11006/
>
> I've attached a minimal nmu for which I will seek sponsoring. Please tell
> me if
> I shouldn't upload this!
>
> Thanks!
>
> Regards,
>   Andreas
>
> --
> PGP-encrypted mails preferred
> PGP Fingerprint: 74CD D9FE 5BCB FE0D 13EE 8EEA 61F3 4426 74DE 6624
>

Bug#821401: libreoffice-gtk3: First [Ctrl+Scroll Down] after changing focus to LO makes LO to zoom in instead of zoom out

[Stéphane Aulery]

Hello,

I can't reproduce it with LO 1:5.4.1-1.

Regards,

-- 
Stéphane Aulery

Bug#877212: [Pkg-javascript-devel] Bug#877212: node-d3-color: B-D npm not available in testing

[Sean Whitton]

Hello Pirate,

On Sun, Oct 01 2017, Pirate Praveen wrote:

> On 09/30/2017 09:26 PM, Sean Whitton wrote:
>> To my mind, this complies with the letter of Policy but not its
>> spirit.
>
> The whole purpose of having contrib and non-free is to host packages
> that can't be in main, either permanently or temporarily. I fail to
> see how it is against the spirit.

To my mind, at least, the purpose of contrib and non-free is for
packages that can't be in main for DFSG reasons /alone/.  Social
Contract item 5:

We acknowledge that some of our users require the use of works that
do not conform to the Debian Free Software Guidelines.  We have
created "contrib" and "non-free" areas in our archive for these
works.

> This is in dependency chain of gitlab
> https://wiki.debian.org/Javascript/Nodejs/Tasks/gitlab
>
> Packaging of rollup is stuck [1] and I can make progress with gitlab
> package with node-d3-color in contrib. Quite a lot of work can happen
> even with gitlab in contrib, like making sure everything is configured
> correctly, making sure update from previous version is working, people
> can test and report bugs while we are working on getting all
> dependencies in main etc. If I simply wait for rollup to arrive in
> main, I can't do any of those.

Okay, I see how this would be useful -- thanks for the explanation.

I am still very uneasy about serving our users -- even our users of
Debian unstable -- with packages that are built using material pulled
from the net.  I think that people who add 'contrib' to their
sources.list do not expect this kind of thing.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#869755: debian refcard: remove auto-apt? (package is not in Stretch)

[Holger Wansing]

Control: tags -1 + pending

Holger Wansing  wrote:
> Package: refcard
> Severity: wishlist
> 
> 
> I noticed that auto-apt is not part of Stretch.
> If it does not make it into Buster, it has to be removed from the refcard, 
> too.

Since auto-apt has been removed from unstable shortly, I have deleted it from
the refcard now.

Tagging this bug as pending


Holger

Bug#877212: [Pkg-javascript-devel] Bug#877212: node-d3-color: B-D npm not available in testing

[Jérémy Lal]

2017-09-30 20:37 GMT+02:00 Pirate Praveen :

> On 09/30/2017 09:26 PM, Sean Whitton wrote:
> > To my mind, this complies with the letter of Policy but not its spirit.
>
> The whole purpose of having contrib and non-free is to host packages
> that can't be in main, either permanently or temporarily. I fail to see
> how it is against the spirit.
>
> > Could you explain why it is so urgent to have node-d3-color in Debian
> > that it can't wait on rollup arriving in main?
> >
>
> This is in dependency chain of gitlab
> https://wiki.debian.org/Javascript/Nodejs/Tasks/gitlab
>
> Packaging of rollup is stuck [1] and I can make progress with gitlab
> package with node-d3-color in contrib. Quite a lot of work can happen
> even with gitlab in contrib, like making sure everything is configured
> correctly, making sure update from previous version is working, people
> can test and report bugs while we are working on getting all
> dependencies in main etc. If I simply wait for rollup to arrive in main,
> I can't do any of those.
>
> It is much easier to move a package from contrib to main than start
> packaging from scratch after rollup is in main. I have been able to move
> many packages to main, which needed babel, using this same strategy.
>
> [1] It needs someone to port acorn-object-spread to acorn 5
> https://github.com/UXtemple/acorn-object-spread/issues/5
>
>
I did a quick check on acorn and rollup and i fail to see how
acorn-object-spread
is related to these modules. Even the github issue is not really explicit.
Can you explain please ?

Jérémy

Bug#877349: seqan2: please disable armel again

[Adrian Bunk]

Source: seqan2
Version: 2.3.2+dfsg-1
Severity: normal

seqan2 (2.3.2+dfsg-1) unstable; urgency=medium
...
  * Re-enable armel, now that upstream bug fixed in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64735
...
 -- Michael R. Crusoe   Thu, 28 Sep 2017 09:15:34 
-0700

This bug in gcc was fixed.


Now it did FTBFS on the buildd:
/tmp/ccddFuJv.s:16668: Error: selected processor does not support `yield' in 
ARM mode

This FTBFS is easily fixable.


After fixing this, the next problem is that seqan2 fails to build
even with -O1 due to virtual memory exhausted.

The file where I ran into the -O1 problem did build with -O0,
but then there is the point that it doesn't make sense to
compile this package without any optimization (which is
expected to result in *very* slow code) for an architecture
where it might have zero users.

Bug#853349: codeblocks: Patch for the build-failure

[Andreas Moog]

Control: tags 853349 + patch

Dear maintainer,

this particular error is fixed already in upstream's SVN repo:

https://sourceforge.net/p/codeblocks/code/11006/

I've attached a minimal nmu for which I will seek sponsoring. Please tell me if 
I shouldn't upload this!

Thanks!

Regards,
  Andreas

-- 
PGP-encrypted mails preferred
PGP Fingerprint: 74CD D9FE 5BCB FE0D 13EE 8EEA 61F3 4426 74DE 6624
diff -Nru codeblocks-16.01+dfsg/debian/changelog codeblocks-16.01+dfsg/debian/changelog
--- codeblocks-16.01+dfsg/debian/changelog	2016-06-15 09:26:34.0 +0200
+++ codeblocks-16.01+dfsg/debian/changelog	2017-09-30 20:21:54.0 +0200
@@ -1,3 +1,10 @@
+codeblocks (16.01+dfsg-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Apply patch from upstream svn to fix FTBFS with GCC 7.1 (Closes: #853349)
+
+ -- Andreas Moog   Sat, 30 Sep 2017 20:21:54 +0200
+
 codeblocks (16.01+dfsg-2) unstable; urgency=medium
 
   * Drop debian/patches/05-fix-boost-system-1.60.patch; obsolete.
diff -Nru codeblocks-16.01+dfsg/debian/patches/06-fix-ftbfs-gcc71.patch codeblocks-16.01+dfsg/debian/patches/06-fix-ftbfs-gcc71.patch
--- codeblocks-16.01+dfsg/debian/patches/06-fix-ftbfs-gcc71.patch	1970-01-01 01:00:00.0 +0100
+++ codeblocks-16.01+dfsg/debian/patches/06-fix-ftbfs-gcc71.patch	2017-09-30 20:21:54.0 +0200
@@ -0,0 +1,19 @@
+Description: Fix compilation with GCC 7.1.0
+Bug-Debian: https://bugs.debian.org/853349
+Origin: upstream, https://sourceforge.net/p/codeblocks/code/11006/
+Last-Update: 2017-09-30
+
+--- codeblocks-16.01+dfsg.orig/src/include/scripting/sqplus/sqplus.h
 codeblocks-16.01+dfsg/src/include/scripting/sqplus/sqplus.h
+@@ -154,10 +154,10 @@
+ return safeStringCopy(s,_s.s,MaxLength);
+   }
+   bool operator == (const ScriptStringVar & _s) {
+-return _strcmp(s,_s.s) == 0;
++return strcmp(s,_s.s) == 0;
+   }
+   bool compareCaseInsensitive(const ScriptStringVar & _s) {
+-return _stricmp(s,_s.s) == 0;
++return strcasecmp(s,_s.s) == 0;
+   }
+ };
diff -Nru codeblocks-16.01+dfsg/debian/patches/series codeblocks-16.01+dfsg/debian/patches/series
--- codeblocks-16.01+dfsg/debian/patches/series	2016-06-15 09:25:21.0 +0200
+++ codeblocks-16.01+dfsg/debian/patches/series	2017-09-30 20:21:54.0 +0200
@@ -3,3 +3,4 @@
 03-remove-fPIC-from-pkg-info.patch
 04-reproducible_build.patch
 05-remove-rsa-md5-impl.patch
+06-fix-ftbfs-gcc71.patch


signature.asc
Description: PGP signature

Bug#877348: stretch-pu: package vim/8.0.0197-4+deb9u1

[James McCoy]

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

* Backport upstream patches to fix CVE-2017-11109  (Closes: #867720)
  + 8.0.0703: Illegal memory access with empty :doau command
  + 8.0.0706: Crash when cancelling the cmdline window in Ex mode
  + 8.0.0707: Freeing wrong memory when manipulating buffers in autocommands

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

Kernel: Linux 4.12.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diffstat for vim-8.0.0197 vim-8.0.0197

 changelog  
  |9 +
 patches/debian/Add-recognition-of-more-LaTeX-commands-for-tex-filetype-d.patch 
  |2 
 patches/debian/Detect-the-rst-filetype-using-the-contents-of-the-file.patch
  |2 
 patches/debian/Document-Debian-s-decision-to-disable-modelines-by-defaul.patch 
  |2 
 patches/debian/Support-sourcing-a-vimrc.tiny-when-Vim-is-invoked-as-vi.patch   
  |6 
 patches/series 
  |3 
 patches/upstream/Add-Zesty-Zapus-to-deb-changelog-sources-syntax-files.patch   
  |4 
 patches/upstream/Support-defining-compilation-date-in-SOURCE_DATE_EPOCH.patch  
  |6 
 patches/upstream/debcontrol.vim-Add-sections-for-Rust-and-JavaScript.patch 
  |2 
 
patches/upstream/patch-8.0.0703-illegal-memory-access-with-empty-doau-comm.patch
 |   69 ++
 
patches/upstream/patch-8.0.0706-crash-when-cancelling-the-cmdline-window-i.patch
 |   42 ++
 
patches/upstream/patch-8.0.0707-freeing-wrong-memory-with-certain-autocomm.patch
 |   40 +
 12 files changed, 175 insertions(+), 12 deletions(-)

diff -Nru vim-8.0.0197/debian/changelog vim-8.0.0197/debian/changelog
--- vim-8.0.0197/debian/changelog   2017-04-23 08:10:29.0 -0400
+++ vim-8.0.0197/debian/changelog   2017-09-30 14:21:38.0 -0400
@@ -1,3 +1,12 @@
+vim (2:8.0.0197-4+deb9u1) stretch; urgency=medium
+
+  * Backport upstream patches to fix CVE-2017-11109  (Closes: #867720)
++ 8.0.0703: Illegal memory access with empty :doau command
++ 8.0.0706: Crash when cancelling the cmdline window in Ex mode
++ 8.0.0707: Freeing wrong memory when manipulating buffers in autocommands
+
+ -- James McCoy   Sat, 30 Sep 2017 14:21:38 -0400
+
 vim (2:8.0.0197-4) unstable; urgency=medium
 
   * Backport upstream patch v8.0.0550 to fix a regression in tag lookups for
diff -Nru 
vim-8.0.0197/debian/patches/debian/Add-recognition-of-more-LaTeX-commands-for-tex-filetype-d.patch
 
vim-8.0.0197/debian/patches/debian/Add-recognition-of-more-LaTeX-commands-for-tex-filetype-d.patch
--- 
vim-8.0.0197/debian/patches/debian/Add-recognition-of-more-LaTeX-commands-for-tex-filetype-d.patch
  2017-04-23 08:10:29.0 -0400
+++ 
vim-8.0.0197/debian/patches/debian/Add-recognition-of-more-LaTeX-commands-for-tex-filetype-d.patch
  2017-09-30 14:21:38.0 -0400
@@ -13,7 +13,7 @@
  1 file changed, 1 insertion(+), 1 deletion(-)
 
 diff --git a/runtime/filetype.vim b/runtime/filetype.vim
-index 9c9c808b4..13e2c0479 100644
+index 9c9c808..13e2c04 100644
 --- a/runtime/filetype.vim
 +++ b/runtime/filetype.vim
 @@ -2227,7 +2227,7 @@ func! s:FTtex()
diff -Nru 
vim-8.0.0197/debian/patches/debian/Detect-the-rst-filetype-using-the-contents-of-the-file.patch
 
vim-8.0.0197/debian/patches/debian/Detect-the-rst-filetype-using-the-contents-of-the-file.patch
--- 
vim-8.0.0197/debian/patches/debian/Detect-the-rst-filetype-using-the-contents-of-the-file.patch
 2017-04-23 08:10:29.0 -0400
+++ 
vim-8.0.0197/debian/patches/debian/Detect-the-rst-filetype-using-the-contents-of-the-file.patch
 2017-09-30 14:21:38.0 -0400
@@ -8,7 +8,7 @@
  1 file changed, 8 insertions(+)
 
 diff --git a/runtime/scripts.vim b/runtime/scripts.vim
-index 276382808..d3101c6b7 100644
+index 2763828..d3101c6 100644
 --- a/runtime/scripts.vim
 +++ b/runtime/scripts.vim
 @@ -332,6 +332,14 @@ else
diff -Nru 
vim-8.0.0197/debian/patches/debian/Document-Debian-s-decision-to-disable-modelines-by-defaul.patch
 
vim-8.0.0197/debian/patches/debian/Document-Debian-s-decision-to-disable-modelines-by-defaul.patch
--- 
vim-8.0.0197/debian/patches/debian/Document-Debian-s-decision-to-disable-modelines-by-defaul.patch
  2017-04-23 08:10:29.0 -0400
+++ 
vim-8.0.0197/debian/patches/debian/Document-Debian-s-decision-to-disable-modelines-by-defaul.patch
  2017-09-30 14:21:38.0 -0400
@@ -15,7 +15,7 @@
  1 file changed, 1 insertion(+), 1 deletion(-)
 
 diff --git a/runtime/doc/options.txt b/runtime/doc/options.txt
-index 88dca60b7

Bug#877347: munin: Failing autopkgtest with 2.0.33-3

[Jeremy Bicha]

Source: munin
Version: 2.0.33-3
Severity: important

munin's autopkgtest started failing in Debian and Ubuntu after
2.0.33-3 was uploaded.

https://ci.debian.net/packages/m/munin/unstable/amd64/
http://autopkgtest.ubuntu.com/packages/m/munin/artful/amd64

Thanks,
Jeremy Bicha

Bug#877346: mosquitto doesn't start after upgrade (jessie to stretch)

[joerg]

Package: mosquitto
Version: 1.4.10-3
Severity: normal

Dear Maintainer,

After upgrading from jessie to stretch (raspbian) the service failed to
start. No clear error message was shown.
The issue was caused by the still existing log file (in
/var/log/mosquitto) which was not owned by user mosquitto.

fix: chown mosquitto /var/log/mosquitto/*

-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux 9.1 (stretch)
Release:9.1
Codename:   stretch
Architecture: armv7l

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

Versions of packages mosquitto depends on:
ii  adduser 3.115
ii  libc6   2.24-11+deb9u1
ii  libssl1.1   1.1.0f-3
ii  libuuid12.29.2-1
ii  libwebsockets8  2.0.3-2
ii  libwrap07.6.q-26
ii  lsb-base9.20161125+rpi1

mosquitto recommends no packages.

Versions of packages mosquitto suggests:
pn  apparmor  

-- no debconf information

Bug#877341: libapache2-mod-md: Doesn't seem to work at all: "AH02572: Failed to configure at least one certificate and key" (seems to require a patched version of mod_ssl / apache2)

[Ondřej Surý]

Thank you!

On Sat, 30 Sep 2017 at 11:31 Axel Beckert  wrote:

> Control: tag -1 + confirmed
> Control: retitle -1 libapache2-mod-md: Doesn't work yet: "AH02572: Failed
> to configure at least one certificate and key" (require a patched version
> of apache2)
>
> Hi Ondřej,
>
> Ondřej Surý wrote:
> > you are right and I intended to fill an bug on apache2 to get the patch
> > included. But I didn't get to it yet. So here we are...
>
> thanks for the confirmation and the cloning of the bug report!
>
> I've allowed myself to mark this bug as confirmed and to make the
> title shorter (remove all "seems" and only refer to the apache2
> package).
>
> 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
>
-- 
Ondřej Surý 

Bug#876731: stretch-pu: package osinfo-db/0.20170225-3~deb9u1

[Adam D. Barratt]

Control: tags -1 + pending

On Fri, 2017-09-29 at 20:21 +0200, Guido Günther wrote:
> Hi,
> On Fri, Sep 29, 2017 at 06:45:37PM +0100, Adam D. Barratt wrote:
> > Control: tags -1 + confirmed
> > 
> > On Mon, 2017-09-25 at 12:43 +0200, Guido Günther wrote:
> > > I'd like to update osinfo-db in stretch. This would allow us to
> > > have
> > > up
> > > to date information for operating system installs with e.g.
> > > gnome-
> > > boxes
> > > by adding new data for recent centos, ubuntu and freebsd releases
> > > as
> > > well as updating existing ones.
> > > 
> > > This version also included all our debian/patches/.
> > > 
> > > Since it's a new upstream version I've attached the full diff.
> > > Note
> > > that
> > > osinfo-db was split out from libosinfo to facilitate this kind of
> > > upgrades.
> > > 
> > 
> > Please go ahead, bearing in mind that the window for 9.2 closes
> > during
> > this weekend.
> 
> Uploaded. Thanks!
> 

Thanks; flagged for acceptance.

Regards,

Adam

Bug#877212: [Pkg-javascript-devel] Bug#877212: node-d3-color: B-D npm not available in testing

[Pirate Praveen]

On 09/30/2017 09:26 PM, Sean Whitton wrote:
> To my mind, this complies with the letter of Policy but not its spirit.

The whole purpose of having contrib and non-free is to host packages
that can't be in main, either permanently or temporarily. I fail to see
how it is against the spirit.

> Could you explain why it is so urgent to have node-d3-color in Debian
> that it can't wait on rollup arriving in main?
> 

This is in dependency chain of gitlab
https://wiki.debian.org/Javascript/Nodejs/Tasks/gitlab

Packaging of rollup is stuck [1] and I can make progress with gitlab
package with node-d3-color in contrib. Quite a lot of work can happen
even with gitlab in contrib, like making sure everything is configured
correctly, making sure update from previous version is working, people
can test and report bugs while we are working on getting all
dependencies in main etc. If I simply wait for rollup to arrive in main,
I can't do any of those.

It is much easier to move a package from contrib to main than start
packaging from scratch after rollup is in main. I have been able to move
many packages to main, which needed babel, using this same strategy.

[1] It needs someone to port acorn-object-spread to acorn 5
https://github.com/UXtemple/acorn-object-spread/issues/5



signature.asc
Description: OpenPGP digital signature

Bug#877341: libapache2-mod-md: Doesn't seem to work at all: "AH02572: Failed to configure at least one certificate and key" (seems to require a patched version of mod_ssl / apache2)

[Axel Beckert]

Control: tag -1 + confirmed
Control: retitle -1 libapache2-mod-md: Doesn't work yet: "AH02572: Failed to 
configure at least one certificate and key" (require a patched version of 
apache2)

Hi Ondřej,

Ondřej Surý wrote:
> you are right and I intended to fill an bug on apache2 to get the patch
> included. But I didn't get to it yet. So here we are...

thanks for the confirmation and the cloning of the bug report!

I've allowed myself to mark this bug as confirmed and to make the
title shorter (remove all "seems" and only refer to the apache2
package).

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

Bug#877345: tmux: Clearing output with Ctrl+L does not work when using tmux

[Vincas Dargis]

Package: tmux
Version: 2.6~rc3-1
Severity: normal

Dear Maintainer,

I have discovered that pressing Ctrl+L while in Konsole (KDE) within
tmux session does move cursor to the top of the console, but it does not
clear all previous output below.

Please see screenshot attached. I have executed:
$ head /usr/share/dict/words

and then pressed Ctrl+L.

I cannot reproduced when tmux is not used.

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


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

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

Versions of packages tmux depends on:
ii  libc6   2.24-17
ii  libevent-2.1-6  2.1.8-stable-4
ii  libtinfo5   6.0+20170902-1
ii  libutempter01.1.6-3

tmux recommends no packages.

tmux suggests no packages.

-- no debconf information

Bug#708162: dd

[Stéphane Aulery]

Hello,

Maybe it's the reason of the circular dependancy [1]?

[1] 
https://lintian.debian.org/tags/intra-source-package-circular-dependency.html

-- 
Stéphane Aulery

Bug#877212: [Pkg-javascript-devel] Bug#877212: node-d3-color: B-D npm not available in testing

[Pirate Praveen]

On 09/30/2017 01:30 PM, Andreas Beckmann wrote:
> Unstable is not outside the archive.

But that dos not seem logical. Does it mean these packages can stay in
testing if we remove npm from unstable?





signature.asc
Description: OpenPGP digital signature

Bug#873081: akonadi-server: Akonadi failed to connect to database: Socket not found. QMYSQL: Unable to connect

[Sandro Knauß]

Hey,

> The problem seemed to be the Akonadi database which got corrupted during
> the dist-upgrade (guess I shouldn't do dist-upgrades anymore, everytime
> I do it something gets corrupted...).

well you need to dist-upgrade otherwise your debian is out of sync. and you 
use testing/unstable, so bugs may happen. And keep in mind, that this issue 
happens because of mysql/mariadb 5.5->5.6 switch and the drop out of innodb so 
unfortunatelly out of scope of akonadi. It is a pitty the main dev of akonadi 
is at the moment not reachable, he surly would have a better solution... 

> My solution was to set back the complete Akonadi database and it's
> configs with this description:
> 

this is really only the last of all options! you loose everything and will 
need to setup akonadi again form the beginning. and please backup all the files 
before doing this!
 
Best regards,

sandro


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

Bug#875322: Batik: make rhino and jython optional

[Erich Schubert]

Hi,

Please cherry-pick this patch:

http://svn.apache.org/viewvc?view=revision&revision=1805148

Also note that upstream has a 1.9.1 release that apparently fixes the poms.

Regards,
Erich

Bug#877344: python-mne FTBFS: ERROR: Test ICA on raw and epochs

[Adrian Bunk]

Source: python-mne
Version: 0.13.1+dfsg-3
Severity: serious
Tags: buster sid

Some recent change in unstable makes python-mne FTBFS:

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

...
==
ERROR: Test ICA on raw and epochs.
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File "/build/1st/python-mne-0.13.1+dfsg/mne/utils.py", line 824, in dec
return function(*args, **kwargs)
  File "/build/1st/python-mne-0.13.1+dfsg/mne/preprocessing/tests/test_ica.py", 
line 214, in test_ica_core
ica.fit(raw, picks=pcks, start=start, stop=stop)
  File "", line 2, in fit
  File "/build/1st/python-mne-0.13.1+dfsg/mne/utils.py", line 708, in verbose
return function(*args, **kwargs)
  File "/build/1st/python-mne-0.13.1+dfsg/mne/preprocessing/ica.py", line 359, 
in fit
tstep, verbose)
  File "/build/1st/python-mne-0.13.1+dfsg/mne/preprocessing/ica.py", line 425, 
in _fit_raw
self._fit(data, self.max_pca_components, 'raw')
  File "/build/1st/python-mne-0.13.1+dfsg/mne/preprocessing/ica.py", line 539, 
in _fit
raise RuntimeError('One PCA component captures most of the '
RuntimeError: One PCA component captures most of the explained variance, your 
threshold results in 0 components. You should select a higher value.
 >> begin captured stdout << -
Opening raw data file 
/build/1st/python-mne-0.13.1+dfsg/mne/io/tests/data/test_raw.fif...
Read a total of 3 projection items:
PCA-v1 (1 x 102)  idle
PCA-v2 (1 x 102)  idle
PCA-v3 (1 x 102)  idle
Range : 25800 ... 40199 = 42.956 ...66.930 secs
Ready.
Current compensation grade : 0
Reading 0 ... 2703  =  0.000 ... 4.500 secs...
366 x 366 full covariance (kind = 1) found.
Read a total of 4 projection items:
PCA-v1 (1 x 102) active
PCA-v2 (1 x 102) active
PCA-v3 (1 x 102) active
Average EEG reference (1 x 60) active
1 matching events found
Applying baseline correction (mode: mean)
Created an SSP operator (subspace dimension = 3)
3 projection items activated
Loading data for 1 events and 241 original time points ...
0 bad epochs dropped

Fitting ICA to data using 306 channels. 
Please be patient, this may take some time
Selection by number: 2 components
Fitting ICA to data using 306 channels. 
Please be patient, this may take some time
Selection by number: 2 components
Fitting ICA to data using 306 channels. 
Please be patient, this may take some time
Selection by number: 2 components


Fitting ICA to data using 306 channels. 
Please be patient, this may take some time

- >> end captured stdout << --

--
Ran 628 tests in 878.575s

FAILED (SKIP=225, errors=1)
debian/rules:25: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#877341: libapache2-mod-md: Doesn't seem to work at all: "AH02572: Failed to configure at least one certificate and key" (seems to require a patched version of mod_ssl / apache2)

[Ondřej Surý]

Control: clone 877341 -1
Control: reassign -1 src:apache2
Control: retitle -1 apache2: please include mod_md patch in apache2
Control: severity -1 normal
Control: block 877341 by -1

Hi Axel,

you are right and I intended to fill an bug on apache2 to get the patch
included. But I didn't get to it yet. So here we are...

Apache2 maintainers, could you please include:

https://raw.githubusercontent.com/icing/mod_md/v0.9.7/patches/mod_ssl_md-2.4.x-v5.diff

My apache2 ppa has to patch for quite some time and there was no bug report
related to it, so it should be very safe to include (I also checked with
upstream maintainer whether it has any downside, and according to him, it
does not).

Cheers,
Ondrej

On Sat, 30 Sep 2017 at 10:30 Axel Beckert  wrote:

Package: libapache2-mod-md
Version: 0.9.0-1
Severity: grave

Dear Ondřej,

I've installed libapache2-mod-md on a machine (Raspberry Pi) running
Debian Unstable where apache2 was already installed.

I've disabled all previous site configurations and wrote a new site
configuration from scratch and only enabled that site:

---8<---
ServerAdmin a...@deuxchevaux.org
ServerName ….deuxchevaux.org
ManagedDomain ….deuxchevaux.org

# Requires libapache2-mod-md ≥ 0.9.4
#MDRequireHttps temporary

DocumentRoot /var/www/html

ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined


Protocols h2 h2c http/1.1




Protocols h2 http/1.1

SSLEngine on


--->8---

"apache2ctl configtest" said that everything is fine: "Syntax OK".

Upon "service apache2 restart" I though got the following lines in the
error.log:

---8<---
[Sat Sep 30 18:39:45.407137 2017] [ssl:emerg] [pid 4976:tid 1995292672]
AH02572: Failed to configure at least one certificate and key for ….
deuxchevaux.org:443
[Sat Sep 30 18:39:45.407356 2017] [ssl:emerg] [pid 4976:tid 1995292672] SSL
Library Error: error:02001002:system library:fopen:No such file or
directory (fopen('/etc/apache2/md/domains/….deuxchevaux.org/privkey.pem
','r'))
[Sat Sep 30 18:39:45.407449 2017] [ssl:emerg] [pid 4976:tid 1995292672] SSL
Library Error: error:2006D080:BIO routines:BIO_new_file:no such file
[Sat Sep 30 18:39:45.407621 2017] [ssl:emerg] [pid 4976:tid 1995292672] SSL
Library Error: error:140A80B1:SSL routines:SSL_CTX_check_private_key:no
certificate assigned
[Sat Sep 30 18:39:45.407675 2017] [ssl:emerg] [pid 4976:tid 1995292672]
AH02312: Fatal error initialising mod_ssl, exiting.
AH00016: Configuration Failed
--->8---

According to https://github.com/icing/mod_md/wiki/2.4.x-Installation,
this module needs either Apache 2.5/2.6 (not yet in Debian) or a patched
Apache 2.4, otherwise I'd get the AH02572 error message and an SSL
Library Error. Which I got, see above.

So I checked apache2's changelog.Debian.gz for inclusion of such a patch
but found none. I also checked https://bugs.debian.org/src:apache2 for
an according request to include such a patch, but haven't found any
either.

So I assume that libapache2-mod-md is currently not usable at all with
plain Debian unstable.

-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500,
'buildd-unstable'), (500, 'stable'), (1, 'experimental-debug'), (1,
'buildd-experimental'), (1, 'experimental')
Architecture: armhf (armv7l)

Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C:en
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libapache2-mod-md depends on:
ii apache2-bin [apache2-api-20120211] 2.4.27-6
ii libapr1 1.6.2-1
ii libaprutil1 1.6.0-2
ii libc6 2.24-17
ii libcurl3-gnutls 7.55.1-1
ii libjansson4 2.10-1
ii libssl1.1 1.1.0f-5

libapache2-mod-md recommends no packages.

libapache2-mod-md suggests no packages.

-- no debconf information
-- 
Ondřej Surý 

Bug#877342: stretch-pu: package qtcurve/1.8.18+git20160320-3d8622c-3+deb9u1

[Boris Pek]

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

Dear release team,

I would like to push a fix for qtcurve bug #865765 (crash when using QtCurve
widget style with Breeze preset).

Debdiff looks big but in fact it is very simple: just s/memcmp/strncmp/

Please consider accepting this as a stretch-pu.

Thanks,
Boris
diff -Nru qtcurve-1.8.18+git20160320-3d8622c/debian/changelog qtcurve-1.8.18+git20160320-3d8622c/debian/changelog
--- qtcurve-1.8.18+git20160320-3d8622c/debian/changelog	2016-05-11 23:52:09.0 +0300
+++ qtcurve-1.8.18+git20160320-3d8622c/debian/changelog	2017-09-30 19:37:12.0 +0300
@@ -1,3 +1,11 @@
+qtcurve (1.8.18+git20160320-3d8622c-3+deb9u1) stable; urgency=medium
+
+  * Add patch replace-memcmp-with-strncmp. It fixes crash when using QtCurve
+widget style and Breeze preset. (Closes: #865765)
+[Thanks to Sergey Sharybin]
+
+ -- Boris Pek   Sat, 30 Sep 2017 19:37:12 +0300
+
 qtcurve (1.8.18+git20160320-3d8622c-3) unstable; urgency=medium
 
   * Add workaround-for-kwin-x11-crashes.patch. (Closes: #823674)
diff -Nru qtcurve-1.8.18+git20160320-3d8622c/debian/patches/replace-memcmp-with-strncmp.patch qtcurve-1.8.18+git20160320-3d8622c/debian/patches/replace-memcmp-with-strncmp.patch
--- qtcurve-1.8.18+git20160320-3d8622c/debian/patches/replace-memcmp-with-strncmp.patch	1970-01-01 03:00:00.0 +0300
+++ qtcurve-1.8.18+git20160320-3d8622c/debian/patches/replace-memcmp-with-strncmp.patch	2017-09-07 18:52:54.0 +0300
@@ -0,0 +1,1337 @@
+Description: Replace memcmp with strncmp
+ Do not exceed string buffer length while parsing config file.
+Origin: upstream, https://cgit.kde.org/qtcurve.git/commit/?id=f164a4b69
+Bug: https://bugs.kde.org/show_bug.cgi?id=374046
+Bug-Debian: https://bugs.debian.org/865765
+Last-Update: 2017-08-03
+
+--- a/gtk2/common/config_file.cpp
 b/gtk2/common/config_file.cpp
+@@ -88,17 +88,17 @@
+ {
+ if(str && 0!=str[0])
+ {
+-if(0==memcmp(str, "dashes", 6))
++if(0==strncmp(str, "dashes", 6))
+ return LINE_DASHES;
+-if(0==memcmp(str, "none", 4))
++if(0==strncmp(str, "none", 4))
+ return LINE_NONE;
+-if(0==memcmp(str, "sunken", 6))
++if(0==strncmp(str, "sunken", 6))
+ return LINE_SUNKEN;
+-if(0==memcmp(str, "dots", 4))
++if(0==strncmp(str, "dots", 4))
+ return LINE_DOTS;
+-if(0==memcmp(str, "flat", 4))
++if(0==strncmp(str, "flat", 4))
+ return LINE_FLAT;
+-if(0==memcmp(str, "1dot", 5))
++if(0==strncmp(str, "1dot", 5))
+ return LINE_1DOT;
+ }
+ return def;
+@@ -108,12 +108,12 @@
+ {
+ if(str && 0!=str[0])
+ {
+-if(0==memcmp(str, "dark", 4))
+-return 0==memcmp(&str[4], "-all", 4) ? TB_DARK_ALL : TB_DARK;
+-if(0==memcmp(str, "none", 4))
++if(0==strncmp(str, "dark", 4))
++return 0==strncmp(&str[4], "-all", 4) ? TB_DARK_ALL : TB_DARK;
++if(0==strncmp(str, "none", 4))
+ return TB_NONE;
+-if(0==memcmp(str, "light", 5))
+-return 0==memcmp(&str[5], "-all", 4) ? TB_LIGHT_ALL : TB_LIGHT;
++if(0==strncmp(str, "light", 5))
++return 0==strncmp(&str[5], "-all", 4) ? TB_LIGHT_ALL : TB_LIGHT;
+ }
+ return def;
+ }
+@@ -122,15 +122,15 @@
+ {
+ if(str && 0!=str[0])
+ {
+-if(0==memcmp(str, "true", 4) || 0==memcmp(str, "colored", 7))
++if(0==strncmp(str, "true", 4) || 0==strncmp(str, "colored", 7))
+ return MO_COLORED;
+-if(0==memcmp(str, "thickcolored", 12))
++if(0==strncmp(str, "thickcolored", 12))
+ return MO_COLORED_THICK;
+-if(0==memcmp(str, "plastik", 7))
++if(0==strncmp(str, "plastik", 7))
+ return MO_PLASTIK;
+-if(0==memcmp(str, "glow", 4))
++if(0==strncmp(str, "glow", 4))
+ return MO_GLOW;
+-if(0==memcmp(str, "false", 4) || 0==memcmp(str, "none", 4))
++if(0==strncmp(str, "false", 4) || 0==strncmp(str, "none", 4))
+ return MO_NONE;
+ }
+ return def;
+@@ -140,40 +140,40 @@
+ {
+ if(str && 0!=str[0])
+ {
+-if(0==memcmp(str, "flat", 4))
++if(0==strncmp(str, "flat", 4))
+ return APPEARANCE_FLAT;
+-if(0==memcmp(str, "raised", 6))
++if(0==strncmp(str, "raised", 6))
+ return APPEARANCE_RAISED;
+-if(0==memcmp(str, "dullglass", 9))
++if(0==strncmp(str, "dullglass", 9))
+ return APPEARANCE_DULL_GLASS;
+-if(0==memcmp(str, "glass", 5) || 0==memcmp(str, "shinyglass", 10))
++if(0==strncmp(str, "glass", 5) || 0==strncmp(str, "shinyglass", 10))
+ return APPEARANCE_SHINY_GLASS;
+-if(0==memcmp(str, "agua", 4))
++if(0==strncmp(str, "agua", 4))
+ return APPEARANCE_AGUA;
+-if(0==memcmp(str, "soft", 4

Bug#877341: libapache2-mod-md: Doesn't seem to work at all: "AH02572: Failed to configure at least one certificate and key" (seems to require a patched version of mod_ssl / apache2)

[Axel Beckert]

Package: libapache2-mod-md
Version: 0.9.0-1
Severity: grave

Dear Ondřej,

I've installed libapache2-mod-md on a machine (Raspberry Pi) running
Debian Unstable where apache2 was already installed.

I've disabled all previous site configurations and wrote a new site
configuration from scratch and only enabled that site:

---8<---
ServerAdmin a...@deuxchevaux.org
ServerName ….deuxchevaux.org
ManagedDomain ….deuxchevaux.org

# Requires libapache2-mod-md ≥ 0.9.4
#MDRequireHttps temporary

DocumentRoot /var/www/html

ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined


Protocols h2 h2c http/1.1




Protocols h2 http/1.1

SSLEngine on


--->8---

"apache2ctl configtest" said that everything is fine: "Syntax OK".

Upon "service apache2 restart" I though got the following lines in the
error.log:

---8<---
[Sat Sep 30 18:39:45.407137 2017] [ssl:emerg] [pid 4976:tid 1995292672] 
AH02572: Failed to configure at least one certificate and key for 
….deuxchevaux.org:443 
[Sat Sep 30 18:39:45.407356 2017] [ssl:emerg] [pid 4976:tid 1995292672] SSL 
Library Error: error:02001002:system library:fopen:No such file or directory 
(fopen('/etc/apache2/md/domains/….deuxchevaux.org/privkey.pem','r')) 
[Sat Sep 30 18:39:45.407449 2017] [ssl:emerg] [pid 4976:tid 1995292672] SSL 
Library Error: error:2006D080:BIO routines:BIO_new_file:no such file 
[Sat Sep 30 18:39:45.407621 2017] [ssl:emerg] [pid 4976:tid 1995292672] SSL 
Library Error: error:140A80B1:SSL routines:SSL_CTX_check_private_key:no 
certificate assigned 
[Sat Sep 30 18:39:45.407675 2017] [ssl:emerg] [pid 4976:tid 1995292672] 
AH02312: Fatal error initialising mod_ssl, exiting. 
AH00016: Configuration Failed 
--->8---

According to https://github.com/icing/mod_md/wiki/2.4.x-Installation,
this module needs either Apache 2.5/2.6 (not yet in Debian) or a patched
Apache 2.4, otherwise I'd get the AH02572 error message and an SSL
Library Error. Which I got, see above.

So I checked apache2's changelog.Debian.gz for inclusion of such a patch
but found none. I also checked https://bugs.debian.org/src:apache2 for
an according request to include such a patch, but haven't found any
either.

So I assume that libapache2-mod-md is currently not usable at all with
plain Debian unstable.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 
'buildd-unstable'), (500, 'stable'), (1, 'experimental-debug'), (1, 
'buildd-experimental'), (1, 'experimental')
Architecture: armhf (armv7l)

Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libapache2-mod-md depends on:
ii  apache2-bin [apache2-api-20120211]  2.4.27-6
ii  libapr1 1.6.2-1
ii  libaprutil1 1.6.0-2
ii  libc6   2.24-17
ii  libcurl3-gnutls 7.55.1-1
ii  libjansson4 2.10-1
ii  libssl1.1   1.1.0f-5

libapache2-mod-md recommends no packages.

libapache2-mod-md suggests no packages.

-- no debconf information

Bug#831458: tidy: adds too much vertical space

[Francesco Poli]

On Mon, 8 May 2017 22:17:21 +0200 Francesco Poli wrote:

> On Thu, 16 Feb 2017 23:29:25 +0100 Francesco Poli wrote:
> 
> > On Sat, 26 Nov 2016 17:47:19 +0100 Francesco Poli wrote:
> > 
> > > On Sat, 29 Oct 2016 17:55:09 +0200 Francesco Poli wrote:
> > > 
> > > > On Sat, 20 Aug 2016 18:45:29 +0200 Francesco Poli wrote:
> > > > 
> > > > > On Sat, 16 Jul 2016 13:12:44 +0200 Francesco Poli (wintermute) wrote:
> > > > > 
> > > > > [...]
> > > > > > Hello again,
> > > > > > besides bug #830066, another thing that I noticed after the upgrade
> > > > > > 
> > > > > >   [UPGRADE] tidy:amd64 20091223cvs-1.5 -> 1:5.2.0-1.1
> > > > > > 
> > > > > > is that tidy started to add too much vertical space.
> > > > > 
> > > > > Hello!
> > > > > 
> > > > > Thanks for fixing the other bug (#830066).
> > > > > What's the status of this bug (#831458), on the other hand?
> > > > > Is there any progress?
> > > > > Has it been forwarded upstream, by chance?
> > > > > 
> > > > > Please let me know, thanks for your time!
> > > > 
> > > > Ping?
> > > 
> > > Second ping?
> > 
> > Third ping?
> > 
> 
> Fourth ping?

Fifth ping?
May I have some sort of reply?

This bug log is a monologue!
I see several other bug reports left unanswered for 1 year or more.

Is this package maintained by anyone or should it be declared orphaned?




-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpUhrnRIUJdb.pgp
Description: PGP signature

Bug#877339: libreoffice-core: OOlibreoffice SEGV in _expand_stack_to on most documents

[Rene Engelhard]

Hi,

sent to early.

On Sat, Sep 30, 2017 at 05:53:47PM +0100, Matthew Vernon wrote:
> #0  0x51fb0f95 in _expand_stack_to(unsigned char*) ()
>from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
  

OpenJDK.

> Identifier: com.sun.wiki-publisher
>   Version: 1.2.0
>   URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher
>   is registered: yes
>   Media-Type: application/vnd.sun.star.package-bundle
>   Description: The Wiki Publisher enables you to create Wiki articles on 
> MediaWiki servers without having to know the syntax of the MediaWiki markup 
> language. Publish your new and existing documents transparently with the 
> Writer to a wiki page.

Ah, there it is.

> Identifier: com.sun.star.comp.Calc.NLPSolver
>   Version: 0.9
>   URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/nlpsolver
>   is registered: yes
>   Media-Type: application/vnd.sun.star.package-bundle
>   Description: This extension integrates into Calc and offers new Solver 
> engines to use for optimizing nonlinear programming models.

Also Java

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

And there we have a big point, this regression is 32-bit/i386 only. If you
used amd64 it wouldn't happen..

Regards,

Rene

Bug#877339: libreoffice-core: OOlibreoffice SEGV in _expand_stack_to on most documents

[Rene Engelhard]

retitle 877339 libreoffice-core: libreoffice SEGV in _expand_stack_to on most 
documents
reassign 877339 src:linux
forcemerge 865303 877339
thanks

Hi,

On Sat, Sep 30, 2017 at 05:53:47PM +0100, Matthew Vernon wrote:
> I've found stable's version of libreoffice basically unusable (I
> previously found oldoldstable's just fine), crashing on nearly

oldoldstables would also crash the same way if it happened to initialize
someting Javaish (e.g. libreoffice-wiki-publisher).

And wiki-publisher is installed by the libreoffice metapackage in stretch...
(Recommends:, which is installed per default.)

> everything I try and open with it. Unfortunately, most of the
> Office docs I have to interact with are confidential. I've finally
> found one that isn't, so I'll attach it to this bug report.
> 
> The failure mode is always the same - libreoffice gets much of the way
> through start up, often opening a window, and then core dumps:
> 
> matthew@aragorn:~$ gdb /usr/lib/libreoffice/program/soffice.bin core
> GNU gdb (Debian 7.12-6) 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 "i686-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 /usr/lib/libreoffice/program/soffice.bin...(no debugging 
> symbols found)...done.
> [New LWP 25365]
> [New LWP 25380]
> [New LWP 25367]
> [New LWP 25370]
> [New LWP 25374]
> [New LWP 25372]
> [New LWP 25371]
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
> Core was generated by `/usr/lib/libreoffice/program/soffice.bin 
> firefox-downloads/it_manager_person_sp'.
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0  0x51fb0f95 in _expand_stack_to(unsigned char*) ()
>from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
> [Current thread is 1 (Thread 0x483dc180 (LWP 25365))]
> (gdb) bt
> #0  0x51fb0f95 in _expand_stack_to(unsigned char*) ()
>from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so

There we go. The infamous Stack Clash kernel regression (maybe also a bug in
OpenJDK).

A simple look at the mostly affected modules (Base, Writer if wiki-publisher
is installed) would have shown you that bugs:

Outstanding bugs -- Grave functionality bugs; More information needed (1 bug)

#865303 [G|Mu|=☣] [src:linux] libreoffice: Libreoffice Java features crash with 
Linux 3.16.43-2+deb8u1
Outstanding bugs -- Important bugs; Patch Available (2 bugs)

#876051 [i|+|☣] [openjdk-8-jre-headless] i386 applications using JNI may crash 
due to Hotspot workaround for Exec Shield
#876069 [i|+|☣] [openjdk-9-jre-headless] i386 applications using JNI may crash 
due to Hotspot workaround for Exec Shield
[...]
#876068 [i|+|☣] [openjdk-7-jre-headless] i386 applications using JNI may crash 
due to Hotspot workaround for Exec Shield

See the above bugs, especially on the kernel and

https://lwn.net/Articles/727206/
https://lwn.net/Articles/727703/

Yes, everything here is _still_ unfixed.

Regards,

Rene

Bug#742829: closed by intrigeri (Bug#742829: fixed in apparmor 2.10.95-8)

[Guido Günther]

Hi Daniel,
On Fri, Sep 29, 2017 at 04:09:02PM -0400, Daniel Richard G. wrote:
> On Fri, 2017 Sep 29 00:18+0200, Guido Günther wrote:
> >
> > Attaching to this the report is fine. I can handle it from there.
> 
> Okay, greatly appreciated. My current profile is attached. Please Cc: me
> on the new bug report.
> 
> As it happens, this file is identical to the current version of the
> profile in the apparmor-profiles Git repository, with the exception of
> the Debian alias lines.
> 
> It seems that the AppArmor folks accepted my changes in the merge
> request, not by approving the merge, but by applying the changes to a
> new version-specific copy in the repo. They added a few more things of
> their own, which I have in turn merged into my/this copy.
> 
> I never heard anything from them about this, however; I learned about
> this only now that I diffed my profile with their latest. Their process
> could certainly stand to be more transparent.

> # Author: Jamie Strandboge 
> #include 
> 
> # Debian compatibility aliases
> # https://bugs.debian.org/742829
> #
> alias /etc/chromium-browser/ -> /etc/chromium/,
> alias /usr/bin/chromium-browser -> /usr/bin/chromium,
> alias /usr/lib/chromium-browser/chromium-browser-sandbox -> 
> /usr/lib/chromium/chrome-sandbox,
> alias /usr/lib/chromium-browser/chromium-browser -> 
> /usr/lib/chromium/chromium,
> alias /usr/lib/chromium-browser/ -> /usr/lib/chromium/,
> 
> # We need 'flags=(attach_disconnected)' in newer chromium versions
> /usr/lib/chromium-browser/chromium-browser flags=(attach_disconnected) {
>   #include 
>   #include 
>   #include 
>   #include 
>   #include 
>   #include 
>   #include 
>   #include 
> 
>   # This include specifies which ubuntu-browsers.d abstractions to use. Eg, if
>   # you want access to productivity applications, adjust the following file
>   # accordingly.
>   #include 

This file is currently not included in Debian's apparmor
package. @intrigeri, can this be added? I assume we don't want other
packages to mess around in abstractions? If not I can pull the code from
that file into the profile.

I'm attaching a patch against chromium here for reference.
Cheers,
 -- Guido

> 
>   # Networking
>   network inet stream,
>   network inet6 stream,
>   @{PROC}/[0-9]*/net/if_inet6 r,
>   @{PROC}/[0-9]*/net/ipv6_route r,
> 
>   # Should maybe be in abstractions
>   /etc/mime.types r,
>   /etc/mailcap r,
>   /etc/mtab r,
>   /etc/xdg/xubuntu/applications/defaults.list r,
>   owner @{HOME}/.local/share/applications/defaults.list r,
>   owner @{HOME}/.local/share/applications/mimeinfo.cache r,
> 
>   @{PROC}/[0-9]*/fd/ r,
>   @{PROC}/filesystems r,
>   @{PROC}/ r,
>   @{PROC}/[0-9]*/task/[0-9]*/stat r,
>   owner @{PROC}/[0-9]*/cmdline r,
>   owner @{PROC}/[0-9]*/io r,
>   owner @{PROC}/[0-9]*/setgroups w,
>   owner @{PROC}/[0-9]*/{uid,gid}_map w,
>   @{PROC}/[0-9]*/smaps r,
>   owner @{PROC}/[0-9]*/stat r,
>   @{PROC}/[0-9]*/statm r,
>   owner @{PROC}/[0-9]*/status r,
>   owner @{PROC}/[0-9]*/task/[0-9]*/status r,
>   deny @{PROC}/[0-9]*/oom_{,score_}adj w,
>   @{PROC}/sys/kernel/yama/ptrace_scope r,
>   @{PROC}/sys/net/ipv4/tcp_fastopen r,
> 
>   # Newer chromium needs these now
>   /etc/udev/udev.conf r,
>   /sys/devices/**/uevent r,
>   /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_max_freq r,
>   /sys/devices/system/node/node*/meminfo r,
>   /sys/devices/pci[0-9]*/**/class r,
>   /sys/devices/pci[0-9]*/**/device r,
>   /sys/devices/pci[0-9]*/**/irq r,
>   /sys/devices/pci[0-9]*/**/resource r,
>   /sys/devices/pci[0-9]*/**/vendor r,
>   /sys/devices/pci[0-9]*/**/removable r,
>   /sys/devices/pci[0-9]*/**/block/**/size r,
>   /sys/devices/virtual/block/**/removable r,
>   /sys/devices/virtual/block/**/size r,
>   /sys/devices/virtual/tty/tty*/active r,
>   # This is requested, but doesn't seem to actually be needed so deny for now
>   deny /run/udev/data/** r,
> 
>   # Needed for the crash reporter
>   owner @{PROC}/[0-9]*/auxv r,
> 
>   # chromium mmaps all kinds of things for speed.
>   /etc/passwd m,
>   /usr/share/fonts/truetype/**/*.tt[cf] m,
>   /usr/share/fonts/**/*.pfb m,
>   /usr/share/mime/mime.cache m,
>   /usr/share/icons/**/*.cache m,
>   owner /{dev,run}/shm/pulse-shm* m,
>   owner @{HOME}/.local/share/mime/mime.cache m,
>   owner /tmp/** m,
> 
>   @{PROC}/sys/kernel/shmmax r,
>   owner /{dev,run}/shm/{,.}org.chromium.* mrw,
>   owner /{,var/}run/shm/shmfd-* mrw,
> 
>   /usr/lib/chromium-browser/*.pak mr,
>   /usr/lib/chromium-browser/locales/* mr,
> 
>   # Noisy
>   deny /usr/lib/chromium-browser/** w,
> 
>   capability sys_admin,
>   capability sys_chroot,
>   capability sys_ptrace,
> 
>   # Allow ptracing ourselves
>   ptrace (trace) peer=@{profile_name},
> 
>   # Make browsing directories work
>   / r,
>   /**/ r,
> 
>   # Allow access to documentation and other files the user may want to look
>   # at in /usr
>   /usr/{include,share,src}** r,
> 
>   # Default profile allows downloads to ~/Downloads and uploads from ~/Public
>