Bug#872482: why the further fixup is not needed

2017-08-17 Thread Christian Ehrhardt
For a grain of confidence and background - Upstream there is also a follow
up fix [1], but that is not needed for your package.

The reason is, that this follow up is only needed if dpdk has no
pkg-config, which the 16.11 based package that is in Debian right now
already have.

[1]: https://github.com/collectd/collectd/pull/2405


-- 
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd


Bug#872519: src:gpgme1.0: FTBFS due to upstream file reorganization

2017-08-17 Thread Daniel Kahn Gillmor
On Fri 2017-08-18 00:38:33 -0400, Daniel Kahn Gillmor wrote:
> 1.9.0-3 builds fine on my own system, but sending it to the buildd's
> ends up with messages like:
>
> x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions 
> -Wl,-z,relro -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall 
> -Wstrict-prototypes -Wdate-time -D_FORTIFY_SOURCE=2 -g 
> -fdebug-prefix-map=/build/python2.7-qMUuQf/python2.7-2.7.13=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro 
> -Wl,-z,now -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wcast-align 
> -Wshadow -Wstrict-prototypes -Wdate-time -D_FORTIFY_SOURCE=2 
> python2-gpg/temp.linux-x86_64-2.7/python2-gpg/gpgme_wrap.o 
> python2-gpg/temp.linux-x86_64-2.7/python2-gpg/helpers.o -L../../src/.libs -o 
> python2-gpg/lib.linux-x86_64-2.7/gpg/_gpgme.so -L/usr/lib/x86_64-linux-gnu 
> -lgpgme -lassuan -lgpg-error
> running build_py
> package init file 'gpg/__init__.py' not found (or not a regular file)
> error: package directory 'gpg/constants' does not exist
> Makefile:752: recipe for target 'all-local' failed
> make[5]: *** [all-local] Error 1
> make[5]: Leaving directory '/<>/lang/python'
> Makefile:472: recipe for target 'all-recursive' failed
> make[4]: *** [all-recursive] Error 1
> make[4]: Leaving directory '/<>/lang/python'
>
> This is likely due to
> debian/patches/0007-python-simplify-build-some-fixups.patch, a patch
> from upstream which does a major overhaul of the python layout (which
> i've included because it's on upstream's path to fixing the gcc 7
> errors).
>
> I'm trying to replicate the build failure myself, but haven't done it
> yet.

interesting, it looks like this is a failure if i build from the
upstream+debian.tar.gz, but it succeeds if i build from a debcheckout
with gbp buildpackage.

 --dkg



Bug#872520: hplip-gui: Broken python dependency

2017-08-17 Thread Karagkiaouris Diamantis
Package: hplip-gui
Version: hplip-gui
Severity: important

Dear Maintainer,

Package seems to be broken as it cannot be installed due to missing
python dependencies.

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

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

Versions of packages hplip-gui depends on:
ii  dbus-user-session [default-dbus-session-bus]1.11.16+really1.10.22-1
ii  dbus-x11 [dbus-session-bus] 1.11.16+really1.10.22-1
pn  gksu | kdebase-bin | kde-runtime | kdebase-runtime  
ii  hplip   3.17.7+repack0-3
pn  python3-dbus.mainloop.pyqt5 
pn  python3-pyqt5   

Versions of packages hplip-gui recommends:
pn  python3-notify2  
ii  xsane0.999-5

hplip-gui suggests no packages.



Bug#871325: Pending fixes for bugs in the shiro package

2017-08-17 Thread pkg-java-maintainers
tag 871325 + pending
thanks

Some bugs in the shiro package are closed in revision
ea98dfd94df20016a7f48c498f79a5578eae6751 in branch 'master' by tony
mancill

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

Commit message:

Add missing build-dep on junit4 (Closes: #871325)



Bug#872478: cacti: XSS in spikekill.php via method parameter

2017-08-17 Thread Salvatore Bonaccorso
Control: retitle -1 cacti: CVE-2017-12927: XSS in spikekill.php via method 
parameter

On Thu, Aug 17, 2017 at 09:17:42PM +0200, Salvatore Bonaccorso wrote:
> Source: cacti
> Version: 1.1.17+ds1-1
> Severity: important
> Tags: patch upstream security fixed-upstream
> Forwarded: https://github.com/Cacti/cacti/issues/907
> 
> hi
> 
> Opening the tracking bug for the XSS issue reported at
> https://github.com/Cacti/cacti/issues/907 .  Upstream fix:
> https://github.com/Cacti/cacti/commit/a032ce0be6a4ea47862c594e40a619ac8de1ef99
> 
> A CVE has been requested for this issue.

CVE-2017-12927 has been assigned.

Regards,
Salvatore



Bug#872316: gdm3: "GNOME on Xorg" always uses Xwayland

2017-08-17 Thread 足永 拓郎
Hi.

On Thu, 17 Aug 2017 15:39:37 +0200 Michael Biebl  wrote:
> Again, a misunderstanding. Those sessions are for the user login
> session, not the gdm session.
> 
>> plan 2. rewrite Name= entry more suitable one.
>>   (not to be confused)
> 
> Why would we do that? I'm not sure what's unsuitable about them. Please
> elaborate.

Yes, it's a *user session*.
Indeed the problem that he'd like to report is about the *user session*.

The problem is that Xorg server daemon still isn't launched after the
*user sesession* is started, although the menu item says "GNOME on Xorg".
A user will expect that Xorg will be lauched by selecting it when he/she
see the title "GNOME on Xorg".

It seems that the title should be "GNOME on X" or "GNOME on X Window System",
not "GNOME on Xorg". "Xorg" isn't equal to "X Window System". "Xorg" is just
only an implementation of "X Window System" specification.

Regards,
Takuro Ashie



Bug#853688: tulip: ftbfs with GCC-7

2017-08-17 Thread Aaron M. Ucko
Source: tulip
Version: 4.8.0dfsg-2
Followup-For: Bug #853688

This bug broke the recent attempt to perform a binNMU against binutils
2.29, blocking a number of upgrades on systems with tulip installed.
AFAICT, you can address the immediate problem by having
thirdparty/OGDF/include/ogdf/basic/DisjointSets.h #include 
for memcpy().  I haven't checked whether there are other compatibility
issues, but suspect they should be similarly trivial to address.  (If
not, you can temporarily build-depend on, and build with, g++-6.)
Could you please take a look?

Thanks!

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



Bug#872519: src:gpgme1.0: FTBFS due to upstream file reorganization

2017-08-17 Thread Daniel Kahn Gillmor
Package: src:gpgme1.0
Version: 1.9.0-3
Severity: normal

1.9.0-3 builds fine on my own system, but sending it to the buildd's
ends up with messages like:

x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions 
-Wl,-z,relro -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall 
-Wstrict-prototypes -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-fdebug-prefix-map=/build/python2.7-qMUuQf/python2.7-2.7.13=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro 
-Wl,-z,now -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -Wcast-align 
-Wshadow -Wstrict-prototypes -Wdate-time -D_FORTIFY_SOURCE=2 
python2-gpg/temp.linux-x86_64-2.7/python2-gpg/gpgme_wrap.o 
python2-gpg/temp.linux-x86_64-2.7/python2-gpg/helpers.o -L../../src/.libs -o 
python2-gpg/lib.linux-x86_64-2.7/gpg/_gpgme.so -L/usr/lib/x86_64-linux-gnu 
-lgpgme -lassuan -lgpg-error
running build_py
package init file 'gpg/__init__.py' not found (or not a regular file)
error: package directory 'gpg/constants' does not exist
Makefile:752: recipe for target 'all-local' failed
make[5]: *** [all-local] Error 1
make[5]: Leaving directory '/<>/lang/python'
Makefile:472: recipe for target 'all-recursive' failed
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory '/<>/lang/python'

This is likely due to
debian/patches/0007-python-simplify-build-some-fixups.patch, a patch
from upstream which does a major overhaul of the python layout (which
i've included because it's on upstream's path to fixing the gcc 7
errors).

I'm trying to replicate the build failure myself, but haven't done it
yet.

--dkg

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

Kernel: Linux 4.11.0-1-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)



Bug#872518: qt5-style-plugin: Can't install the package anymore. It depends on: qtbase-abi-5-7-1.

2017-08-17 Thread felipe
Package: qt5-style-plugin
Version: 5.0.0+git23.g335dbec-2
Severity: important

Dear Maintainer,


After updating qt5 packages from 5.7 to 5.9.1 it is no longer possible
to install this package. Apt returns the error:

   qt5-style-plugins : Depends: qtbase-abi-5-7-1 but it is not installable

Without this package, qt5 apps do not use the GTK theme anymore.

If possible, update the package.

Thanks.


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

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



Bug#871352: Pending fixes for bugs in the jdeb package

2017-08-17 Thread pkg-java-maintainers
tag 871352 + pending
thanks

Some bugs in the jdeb package are closed in revision
401873652282632a48e34fd76381089a37a71949 in branch 'master' by tony
mancill

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

Commit message:

Add build-dep on junit (Closes: #871352)



Bug#844431: debian-policy: Packages should be reproducible

2017-08-17 Thread Chris Lamb
Hi Edroman,

> Regarding to reproducible, I would suggest Debian should consider
> integrating Nix into Debian

Curiously, I had a brief foray into packaging the Nix tools for Debian:

  https://github.com/lamby/pkg-nix

> Nix builds packages in isolation from each other. This ensures that
> they are reproducible

(As Georg writes, we are using different usages of reproducible.)


Regards,

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



Bug#849525: Bug also confirmed in version 1.28.2

2017-08-17 Thread Hamilton Engineering
On Mon, 14 Aug 2017 21:41:20 -0500 Jason Crain  
wrote:

On Mon, Aug 14, 2017 at 05:15:56PM -0400, Markus Hamilton wrote:
> The bug is still there using version 1.28.2 now ... in fact there 

are forum
> discussions and bug reports all over the internet about this 

problem for
> years now. Could we at least get a statement from the maintainers 

whether
> this will ever get fixed or is there some policy we could implement 

to allow
> this. SOME information would really help to figure out where this 

is going.


From the gvfs-mount manpage:

-a, --anonymous
Use an anonymous user when authenticating

This option was added in gvfs version 1.23.90 so gvfs-mount (or gio
mount) should work on stretch or later. On earlier versions you can try
entering a fake username and password depending on how you have samba
set up.

About pcmanfm and caja - I don't see any problem with anonymous smb
shares using nautilus so this is likely something that pcmanfm and caja
need to add support for.




I think we misunderstand each other. I am not talking about anonymous 
access. I am talking about accessing a samba server which does not have 
anonymous (guest) access enabled. So users do have to provide a username 
to be able to login. Some of these usernames (aka smb accounts) just 
have no (or in other words an empty) password. Using anonymous access 
will not work (disabled on the server). A fake username will not work 
either (unknown to the server). It has to be a valid username and an 
empty password. Using mount via command line works fine. Here's an 
example - "markus" is a valid smb account at the server. The password is 
empty.


sudo mount -t cifs //servername/sharename /mnt -o 
username=markus,password=""


But when I try the same operation using gvfs-mount like this:

gvfs-mount smb://servername/sharename

Then the first thing gvfs-mount does is spitting out a message saying 
"Password required for share sharename on servername". It then asks for 
username, then domain and finally password. Just hitting "enter" doesn't 
cut it. gvfs-mount asks again for the password.


So far I have not managed to mount a smb share using gvfs-mount if the 
valid smb account simply is passwordless. If you can tell me how to do 
that then I'm ready to shift the blame to pcmanfm and caja. "mount -t 
cifs..." is living proof that it's not a samba (or Windows, for that 
matter) problem.


So again: how do I gvfs-mount a smb share with a non-anonymous, valid 
smb username but without entering (because there is none) a password?


Thank you for reading here. There are so many users out there with the 
same problem. It used to work. It stopped working at some point during 
the life of jessie.




Bug#872461: googler: Please tidy package long and short descriptions

2017-08-17 Thread 林上智
On Thu, Aug 17, 2017 at 09:54:40AM -0700, Chris Lamb wrote:
> Source: googler
> Version: 3.2.0-1
> Severity: wishlist
> Tags: patch
> 
> Hi,
> 
> Please tidy the package long and short descriptions. Patch attached. :)
> 
> 
> Regards,
> 
> -- 
>   ,''`.
>  : :'  : Chris Lamb
>  `. `'`  la...@debian.org / chris-lamb.co.uk
>`-

> diff --git a/debian/control b/debian/control
> index bde6bbb..e80f6eb 100644
> --- a/debian/control
> +++ b/debian/control
> @@ -12,11 +12,11 @@ Vcs-Git: 
> https://anonscm.debian.org/git/collab-maint/googler.git
>  Package: googler
>  Architecture: all
>  Depends: ${misc:Depends}, ${python3:Depends}, python3 (>= 3.3)
> -Description: Power tool to Google(Web & News) and Google Site Search from 
> the terminal
> - Features
> +Description: Power tool to Google (Web & News) and Google Site Search from 
> the terminal
> + Features:
>   .
>- Google Search, Google Site Search, Google News
> -  - Fast and clean (no ads, stray URLs or clutter), custom color
> +  - Fast and clean (no ads, stray URLs or clutter), customisable color
>- Open result URLs (or the actual search) in browser
>- Navigate search result pages from omniprompt
>- Fetch n results in a go, start at the nth result
> @@ -26,9 +26,7 @@ Description: Power tool to Google(Web & News) and Google 
> Site Search from the te
>- Supports Google search keywords like 'filetype:mime', 
> 'site:somesite.com' 
>  etc.
>- Optionally open the first result directly in browser 
> -(as in I'm Feeling Lucky)
> +(as in "I'm Feeling Lucky")
>- Non-stop searches: fire new searches at omniprompt without exiting
>- Proxy support
>- Man page with examples, shell completion scripts for Bash, Zsh and Fish
> -  - Minimal dependencies
> - .

Thanks for the suggestion, the package description will be updated in next 
upstream release

- 
https://anonscm.debian.org/git/collab-maint/googler.git/commit/?id=3d33d75b8d408dd3aa8ea4eaf8e83fe7a370035d

-- 
SZ Lin (林上智) , http://people.debian.org/~szlin

4096R/ 178F 8338 B314 01E3 04FC 44BA A959 B38A 9561 F3F9


signature.asc
Description: PGP signature


Bug#869416: [pkg-gnupg-maint] Bug#869416: pinentry-gtk2: fails to request passphrase when importing OpenPGP secret key with Seahorse

2017-08-17 Thread NIIBE Yutaka
Control: reassign -1 gcr

NIIBE Yutaka  wrote:
> Now, I guess that the problem is in the implementaiton of libgcr library.
>
> While I'm reading gcr-3.20.0/gcr/gcr-gnupg-process.c, getting the source
> by apt source libgcr-base-3-1, I suspect the function
> _gcr_gnupg_process_run_async, which doesn't provide GPG_TTY and/or
> DISPLAY to "gpg" process.

Attached is a patch for gcr to fix this issue.  When I apply this patch
to build libgcr-base-3-1 package (and install), the problem of seahorse
has gone.

I also created a ticket for GnuPG upstream to improve its documentation:

https://dev.gnupg.org/T3353

I put the patch in public domain, or it may be distributed
under the licence of LGPL-2.1+.
-- 
Index: gcr-3.20.0/gcr/Makefile.am
===
--- gcr-3.20.0.orig/gcr/Makefile.am
+++ gcr-3.20.0/gcr/Makefile.am
@@ -118,6 +118,7 @@ nodist_libgcr_base_@GCR_MAJOR@_la_SOURCE
 libgcr_base_@GCR_MAJOR@_la_CFLAGS = \
 	$(LIBGCRYPT_CFLAGS) \
 	$(P11_KIT_CFLAGS) \
+	$(GTK_CFLAGS) \
 	-DGCK_API_SUBJECT_TO_CHANGE \
 	-DP11_KIT_API_SUBJECT_TO_CHANGE \
 	-DGCR_COMPILATION \
@@ -133,7 +134,8 @@ libgcr_base_@GCR_MAJOR@_la_LIBADD = \
 	libgck-@GCK_MAJOR@.la \
 	$(GLIB_LIBS) \
 	$(LIBGCRYPT_LIBS) \
-	$(P11_KIT_LIBS)
+	$(P11_KIT_LIBS) \
+	$(GTK_LIBS)
 
 gcr/gcr-marshal.h: gcr/gcr-marshal.list $(GLIB_GENMARSHAL)
 	$(AM_V_GEN) $(GLIB_GENMARSHAL) $< --header --prefix=_gcr_marshal > $@
Index: gcr-3.20.0/gcr/gcr-gnupg-process.c
===
--- gcr-3.20.0.orig/gcr/gcr-gnupg-process.c
+++ gcr-3.20.0/gcr/gcr-gnupg-process.c
@@ -27,6 +27,7 @@
 #include "gcr/gcr-marshal.h"
 
 #include 
+#include 
 
 #include 
 #include 
@@ -971,6 +972,8 @@ _gcr_gnupg_process_run_async (GcrGnupgPr
 	GSource *source;
 	GPid pid;
 	guint i;
+	GdkDisplay *display;
+	const gchar *display_name;
 
 	g_return_if_fail (GCR_IS_GNUPG_PROCESS (self));
 	g_return_if_fail (argv);
@@ -996,6 +999,13 @@ _gcr_gnupg_process_run_async (GcrGnupgPr
 	child_fds[FD_OUTPUT] = 1;
 	child_fds[FD_ERROR] = 2;
 
+	if ((display = gdk_display_get_default ())
+	&& (display_name = gdk_display_get_name (display)))
+	  {
+	g_ptr_array_add (args, g_strdup ("--display"));
+	g_ptr_array_add (args, g_strdup (display_name));
+	  }
+
 	if (flags & GCR_GNUPG_PROCESS_WITH_STATUS) {
 		if (pipe (status_fds) < 0)
 			g_return_if_reached ();


Bug#872194: espeakup: Espeakup fails to start due to libespeak-ng.so.1.1.49 segfault

2017-08-17 Thread Steven Shiau

On 08/18/2017 08:31 AM, Samuel Thibault wrote:
> Control: tags -1 + moreinfo
>
> Hello,
>
> Steven Shiau, on mar. 15 août 2017 14:28:56 +0800, wrote:
>> Espeakup fails to start due to libespeak-ng.so.1.1.49 segfault in Debian Sid.
>>
>>* How to reproduce the issue?
>>  Just run "sudo service espeakup start"
> I can't reproduce it, I have these versions, and things work just fine
> for me.
>
> Does the crash happen very quickly, or some particular things need to be
> done on the console?
> What configuration do you have in /etc/default/espeakup?
Hi Samuel,
Yes, the crash happens very quickly if I run "sudo service espeakup
restart". I can see the in /var/log/messages, and it actually will retry
and the segfalut occurs every about 90 secs.
Nothing was changed in /etc/default/espeakup:
==
$ cat /etc/default/espeakup
# To choose the default voice of the espeakup daemon, define VOICE here.
# See /usr/lib/*/espeak-data/voices/ for a list of possible voices.

VOICE=

# To choose audio output on another sound card, uncomment this and set as
# appropriate (either a card number or a card name as seen in CARD= alsa
# output).
#
# ALSA_CARD=0
==

I can reproduce this issue in many of different machines, like the
latest (updated these 2 days)  Debian Sid on VMWare WS, both i386 and
AMD64 architectures with Linux kernel 4.12.0-1, and on my Lenovo x230
laptop.
Thanks.

Steven
>
> Samuel

-- 
Steven Shiau 
Public Key Server PGP Key ID: 4096R/47CF935C
Fingerprint: 0240 1FEB 695D 7112 62F0  8796 11C1 12DA 47CF 935C



Bug#850980: (no subject)

2017-08-17 Thread hexa-
Dear Maintainer,

the machine boots up fine after disabling KASLR (`nokalsr`). I therefore
consider this issue as resolved.


Best Regards,

Martin



signature.asc
Description: OpenPGP digital signature


Bug#872517: ffmpeg: CVE-2017-7206: heap-based buffer over-read in embed libav

2017-08-17 Thread Luciano Bello
Package: ffmpeg
X-Debbugs-CC: t...@security.debian.org secure-testing-
t...@lists.alioth.debian.org
Severity: grave
Tags: security

Hi,

the following vulnerability was published for libav (which is embed in 
ffmpeg).

CVE-2017-7206[0]:
| The ff_h2645_extract_rbsp function in libavcodec in libav 9.21 allows
| remote attackers to cause a denial of service (heap-based buffer
| over-read) or obtain sensitive information from process memory via a
| crafted h264 video file.

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-7206
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7206

Please adjust the affected versions in the BTS as needed.



Bug#871199: pysodium: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13

2017-08-17 Thread Christopher Hoskin
Package: src:pysodium
Version: 0.6.14-1
Followup-For: Bug #871199

Dear Lucas,

Thanks for the bug report. This was a bug in 0.6.11-1, I beleive it is fixed in 
0.6.14-1.

Unfortunately I didn't spot this bug report before I uploaded 0.6.14-1, so it 
isn't referenced in the changelog.

Christopher



Bug#872509: ITP: inhomog -- kinematical backreaction and average scale factor evolution

2017-08-17 Thread Jonas Smedegaard
Quoting Boud Roukema (2017-08-18 03:41:01)
> hi Jonas, Debian Astro team,
> 
> On Fri, 18 Aug 2017, Jonas Smedegaard wrote:
> 
> > I have never seen a package description so stuffed with advanced 
> > technical terms.
> >
> > I am very impressed at how it still (I guess) succeeds at hinting at 
> > its purpose for non-experts like myself.
> 
> Thanks for the pedagogical suggestion :).

Oh, I was not being sarcastic: I genuinely found your package 
description helpful - being a non-scientist.


> I've added a more general-science sentence "The inhomog library 
> calculates average cosmological expansion" to the three binary 
> sections of the debian/control file:

Even better. Thanks!

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature


Bug#872509: ITP: inhomog -- kinematical backreaction and average scale factor evolution

2017-08-17 Thread Boud Roukema

hi Jonas, Debian Astro team,

On Fri, 18 Aug 2017, Jonas Smedegaard wrote:


I have never seen a package description so stuffed with advanced
technical terms.

I am very impressed at how it still (I guess) succeeds at hinting at its
purpose for non-experts like myself.


Thanks for the pedagogical suggestion :). I've added a more general-science
sentence "The inhomog library calculates average cosmological expansion"
to the three binary sections of the debian/control file:

https://anonscm.debian.org/cgit/debian-astro/packages/inhomog.git

That's still a very technical sentence: it distinguishes calculating average
expansion from assuming average expansion.

Hope this helps :)
Boud



Bug#796802: Bug 762449 fix lost in 2.0.10-1

2017-08-17 Thread Tiago Stürmer Daitx
I have prepared a patch based on Uwe Kleine-König's proposal that
fixes the arm build.

thanks

diff -Nru numactl-2.0.11/debian/changelog numactl-2.0.11/debian/changelog
--- numactl-2.0.11/debian/changelog2016-12-21 18:27:02.0 +
+++ numactl-2.0.11/debian/changelog2017-08-17 22:16:39.0 +
@@ -1,3 +1,13 @@
+numactl (2.0.11-2.2) UNRELEASED; urgency=medium
+
+  * syscall.c:
+- add __arm__ to avoid failure due to missing syscalls.
+- return -1 and set errno to ENOSYS on migrate_pages function
+  if __NR_migrate_pages is undefined, thanks Uwe Kleine-König
+  for the initial patch. Closes: #796802. LP: #1711478.
+
+ -- Tiago Stürmer Daitx   Thu, 17 Aug 2017
22:16:39 +
+
 numactl (2.0.11-2.1) unstable; urgency=medium

   * Non-maintainer upload.
diff -Nru numactl-2.0.11/debian/patches/fix-arm-nr-missing-pages.patch
numactl-2.0.11/debian/patches/fix-arm-nr-missing-pages.patch
--- numactl-2.0.11/debian/patches/fix-arm-nr-missing-pages.patch
1970-01-01 00:00:00.0 +
+++ numactl-2.0.11/debian/patches/fix-arm-nr-missing-pages.patch
2017-08-17 22:16:39.0 +
@@ -0,0 +1,43 @@
+Description: allow __arm__ to pass syscall check even without migrate_pages
+ numactl build fails on arm because arm does not define __NR_migrate_pages.
+ In order to build it on arm the arch must be added to the syscalls check
+ and the migrate_pages must return with -1 and set errno to ENOSYS.
+ .
+ This patch is based on Uwe Kleine-König's suggestion at
+ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796802#15
+Author: Tiago Stürmer Daitx 
+Origin: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796802#15
+Bug-Debian: https://bugs.debian.org/796802
+Bug-Ubuntu: https://launchpad.net/bugs/1711478
+Last-Update: 2017-08-17
+
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+
+--- a/syscall.c
 b/syscall.c
+@@ -109,6 +109,10 @@
+
+ #define __NR_migrate_pages272
+
++#elif defined(__arm__)
++// arm does not define __NR_migrate_pages
++// ignore that and continue (Debian #796802)
++
+ #elif !defined(DEPS_RUN)
+ #error "Add syscalls for your architecture or update kernel headers"
+ #endif
+@@ -206,7 +210,13 @@ long WEAK set_mempolicy(int mode, const
+ long WEAK migrate_pages(int pid, unsigned long maxnode,
+ const unsigned long *frommask, const unsigned long *tomask)
+ {
++#if defined(__NR_migrate_pages)
+ return syscall(__NR_migrate_pages, pid, maxnode, frommask, tomask);
++#else
++// See Debian #796802
++errno = ENOSYS;
++return -1;
++#endif
+ }
+
+ long WEAK move_pages(int pid, unsigned long count,
diff -Nru numactl-2.0.11/debian/patches/series
numactl-2.0.11/debian/patches/series
--- numactl-2.0.11/debian/patches/series1970-01-01 00:00:00.0 +
+++ numactl-2.0.11/debian/patches/series2017-08-17 22:16:39.0 +
@@ -0,0 +1 @@
+fix-arm-nr-missing-pages.patch


numactl_2.0.11-2.1_2.0.11-2.2.debdif
Description: Binary data


Bug#872516: pristine-tar: add flag to create missing directories

2017-08-17 Thread brian m. carlson
Package: pristine-tar
Version: 1.40
Severity: wishlist
Tags: patch

pristine-tar gentar doesn't have a way to create missing directories
like commit and checkout do.  This causes problems if one wants to store
the pristine-tar directory in a subdirectory of a Git repository instead
of in a separate branch at the top level.

Attached is a patch to implement a --create-missing option, which simply
enables the internal create_missing flag that checkout and commit use,
but for gentar.

I've verified that it works as expected by using gendelta and gentar in
a subdirectory of a Git repository using the git-2.14.1.tar.gz tarball.

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

Kernel: Linux 4.11.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)

Versions of packages pristine-tar depends on:
ii  libbz2-1.0  1.0.6-8.1
ii  libc6   2.24-14
ii  perl5.26.0-5
ii  tar 1.29b-2
ii  xdelta  1.1.3-9.1+b1
ii  xdelta3 3.0.11-dfsg-1+b1
ii  zlib1g  1:1.2.8.dfsg-5

Versions of packages pristine-tar recommends:
ii  bzip2 1.0.6-8.1
ii  pbzip21.1.9-1+b1
ii  xz-utils  5.2.2-1.3

pristine-tar suggests no packages.

-- no debconf information

-- 
brian m. carlson / brian with sandals: Houston, Texas, US
https://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: https://keybase.io/bk2204
From b42ac744f532baa4c2f8614dc4e4f38a5b27eceb Mon Sep 17 00:00:00 2001
From: "brian m. carlson" 
Date: Fri, 18 Aug 2017 00:56:50 +
Subject: [PATCH] Add a --create-missing option to gentar

pristine-tar handles the automatic recreation of empty directories with
the checkout command, since some version control systems, like Git,
don't store empty directories.  This is done by the internal use of a
flag, create_missing.

However, some workflows do not use checkout and commit for various
reasons, and hence cannot make use of this functionality.  Expose the
functionality using a flag, --create-missing, that recreates these
directories automatically.
---
 pristine-tar | 10 --
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/pristine-tar b/pristine-tar
index d4f4b0e..9a1c7b1 100755
--- a/pristine-tar
+++ b/pristine-tar
@@ -8,7 +8,7 @@ pristine-tar - regenerate pristine tarballs
 
 B [-vdk] gendelta I I
 
-B [-vdk] gentar I I
+B [-vdk] [--create-missing] gentar I I
 
 B [-vdk] [-m message] commit I [I]
 
@@ -120,6 +120,10 @@ Don't clean up the temporary directory on exit.
 
 Use this option to specify a custom commit message to pristine-tar commit.
 
+=item --create-missing
+
+When regenerating a tarball, create any missing empty directories.
+
 =back
 
 =head1 EXAMPLES
@@ -227,6 +231,7 @@ use constant {
 };
 
 my $message;
+my $create_missing;
 my $genversion =
   version_from_env(XDELTA3, "xdelta" => XDELTA, "xdelta3" => XDELTA3);
 
@@ -244,6 +249,7 @@ dispatch(
   },
   options => {
 "m|message=s" => \$message,
+"create-missing" => \$create_missing,
   },
 );
 
@@ -343,7 +349,7 @@ sub recreatetarball {
   );
   $full_sweep = 1;
 
-  if ($options{create_missing}) {
+  if ($create_missing || $options{create_missing}) {
 # Avoid tar failing on the nonexistent item by
 # creating a dummy directory.
 debug("creating missing $unquoted_file");
-- 
2.14.1.480.gb18f417b89



signature.asc
Description: PGP signature


Bug#871465: [pkg-gnupg-maint] Bug#871465: dput seems to miss a dependency on python3-tofu

2017-08-17 Thread Daniel Kahn Gillmor
Control: retitle 871465 python3-gpg package should ship tofu module

On Tue 2017-08-08 12:51:59 +0300, Adrian Bunk wrote:
> On Tue, Aug 08, 2017 at 03:11:40AM -0400, Jonathan Carter wrote:
>>...
>>   File "/usr/lib/python3/dist-packages/gpg/constants/__init__.py", line
>> 28, in 
>> from . import data, keylist, sig, tofu # The subdirs.
>> ImportError: cannot import name 'tofu'
>> """
>>...
>> Versions of packages dput depends on:
>>...
>> ii  python3-gpg1.9.0-2
>>...
>
> This is a bug in the python3-gpg package in experimental.
>
> tofu is part of gpgme and should be shipped in python3-gpg.

  --dkg



Bug#872515: apt: upgrade the binaries for a particular source package

2017-08-17 Thread Luciano Bello
Package: apt
Severity: wishlist

Hello,
  The security team releases a DSA when a package is vulnerable, with the 
recommendation "[...] upgrade your XX packages". The thing is, XX is a source 
package. The users should be able to upgrade the binaries from XX that are 
installed in their system.
Something like:
 apt-get upgrade src:XX

It would be awesome to be able to recommend such a command in the DSAs.

Thanks, luciano



Bug#872514: devscripts: Please add script to report on reproducibility status of installed packages

2017-08-17 Thread Chris Lamb
Package: devscripts
Version: 2.17.9
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: toolchain
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi!

Thanks for your work on devscripts. Attached is the following:

  commit 57512128c75ac74b6cfa3c70a0613ba85789b992
  Author: Chris Lamb 
  Date:   Thu Aug 17 17:07:16 2017 -0700
  
  reproducible-check: New script to report on reproducibility status
of installed packages.
  
  Signed-off-by: Chris Lamb 
  
   .gitignore |   1 +
   debian/control |   7 ++
   debian/copyright   |   6 ++
   scripts/Makefile   |   7 +-
   scripts/reproducible-check | 170 
+
   scripts/setup.py   |   2 +-
   6 files changed, 190 insertions(+), 3 deletions(-)

Example output:

  $ reproducible-check
  […]
  xen (4.8.1-1+deb9u1) is unreproducible (libxen-4.8, libxenstore3.0) 

  xmlrpc-c (1.33.14-4) is unreproducible (libxmlrpc-core-c3) 

  xmlstarlet (1.6.1-2) is unreproducible 

  xorg-server (2:1.19.3-2) is unreproducible (xserver-xephyr, 
xserver-xorg-core) 
  zsh (5.4.1-1) is unreproducible 

366/4083 (8.96%) of installed binary packages are unreproducible.

Also:

  $ reproducible-check --raw | dd-list -i
  […]
  Torsten Marek 
 pycairo (U)

  Vagrant Cascadian 
 qemu (U)

  Vincent Fourmond 
 imagemagick (U)

  Yury V. Zaytsev 
 mc (U)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
>From 57512128c75ac74b6cfa3c70a0613ba85789b992 Mon Sep 17 00:00:00 2001
From: Chris Lamb 
Date: Thu, 17 Aug 2017 17:07:16 -0700
Subject: [PATCH] reproducible-check: New script to report on reproducibility
 status of installed packages.

Signed-off-by: Chris Lamb 
---
 .gitignore |   1 +
 debian/control |   7 ++
 debian/copyright   |   6 ++
 scripts/Makefile   |   7 +-
 scripts/reproducible-check | 170 +
 scripts/setup.py   |   2 +-
 6 files changed, 190 insertions(+), 3 deletions(-)
 create mode 100755 scripts/reproducible-check

diff --git a/.gitignore b/.gitignore
index e96730cd..248fd399 100644
--- a/.gitignore
+++ b/.gitignore
@@ -98,6 +98,7 @@ scripts/origtargz.1
 scripts/plotchangelog
 scripts/pts-subscribe
 scripts/rc-alert
+scripts/reproducible-check.1
 scripts/rmadison
 scripts/rmadison.1
 scripts/sadt.1
diff --git a/debian/control b/debian/control
index 82165b80..6eac2ce5 100644
--- a/debian/control
+++ b/debian/control
@@ -13,6 +13,7 @@ Build-Depends: bash-completion,
dpkg-dev (>= 1.17.6),
file,
gnupg | gnupg2,
+   help2man,
libdistro-info-perl,
libdpkg-perl,
libfile-desktopentry-perl,
@@ -29,11 +30,14 @@ Build-Depends: bash-completion,
po4a (>= 0.40),
pylint,
python3-all,
+   python3-apt,
python3-debian (>= 0.1.15),
python3-flake8,
python3-magic,
+   python3-requests,
python3-setuptools,
python3-unidiff ,
+   python3-xdg,
shunit2 (>= 2.1.6),
unzip,
wdiff,
@@ -72,9 +76,12 @@ Recommends: apt,
 man-db,
 patch,
 patchutils,
+python3-apt,
 python3-debian (>= 0.1.15),
 python3-magic,
+python3-requests,
 python3-unidiff,
+python3-xdg,
 sensible-utils,
 strace,
 unzip,
diff --git a/debian/copyright b/debian/copyright
index c22addad..95550dc7 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -68,6 +68,12 @@ Copyright: 2009,  Jonathan Patrick Davies 
2006-2008, Kees Cook 
2007-2008, Siegfried-Angel Gevatter Pujals 
2013,  Rafael Laboissiere 
+License: GPL-3+
+
+Files: scripts/reproducible-check
+Copyright: © 2017 Chris Lamb 
+License: GPL-3+
+
 License: GPL-3+
  This program is free software; you can redistribute it and/or modify
  it under the terms of the GNU General Public License as published by
diff --git a/scripts/Makefile b/scripts/Makefile
index ece5455a..21ed11a6 100644
--- a/scripts/Makefile
+++ b/scripts/Makefile
@@ 

Bug#833193: chapel/1.15 [ITP]

2017-08-17 Thread Sean Whitton
control: noowner -1

Dear Ben,

On Wed, May 24 2017, Sean Whitton wrote:

> I will continue as the reviewer and eventual sponsor of the chapel
> source package itself (i.e. this RFS).

Unfortunately, I'm going to have to renege on this.  I recently got a
new job within Debian, and the new semester is starting.  I wish you the
best of luck and hope that chapel is able to make its way into Debian
soon.  I hope my comments were helpful to that process.

-- 
Sean Whitton


signature.asc
Description: PGP signature


Bug#790222: [boinc_dev] Bug#790222: wxwidgets3.0: depends on libwebkitgtk-1.0-0 which is deprecated

2017-08-17 Thread Olly Betts
On Thu, Aug 17, 2017 at 05:34:02PM -0400, Jeremy Bicha wrote:
> > But as I've said already, I don't have a problem with just disabling
> > webview before buster if it comes to it.  It just seems unhelpful to
> > boinc users running testing to do that right now, unless you're actually
> > at the point of removing the old webkitgtk from testing.
> 
> Removal of webkitgtk from testing is still a few weeks away.

There's been a bit of progress on the wx+GTK3 front - most notably wx
upstream have now fixed all the bugs I spotted in my initial testing
with a couple of applications.

However, I don't think we're very close to starting a transition to
wx+GTK3 at this point, so probably we need to decide what to do with
boinc.  The options for the short term seem to be:

* Remove boinc from testing and break it in unstable (which is clearly
  not helpful for anyone wanting to use it and running either).

* Drop the use of wx webview in boinc, which doesn't render it entirely
  unusable, but isn't great.

* Patch boinc to use wxHtmlWindow instead, which has more simplistic
  rendering, but is probably OK if there's not Javascript or CSS
  involved.  I've no idea how much work that would be, or if boinc
  upstream has done any work towards this.

* Upload parallel packages of wx+GTK3 for boinc to use.  I have started
  work on packaging, but it needs more work so that parallel installs
  work properly.  I'm also hesitant to take this approach without a firm
  plan to actually do the transition, as I don't think we have the
  resources to adequately maintain two sets of wx packages (historically
  we've tried this, and one set just ended up neglected).

> But in my opinion, this is the last package blocking removal of
> webkitgtk from Ubuntu 17.10. Removal there is also probably a few
> weeks away since many Ubuntu removals happen late in Ubuntu's release
> cycle.)

I'm sure Ubuntu can make that decision for themselves.

Cheers,
Olly



Bug#872513: chessx: Please add an option to set the default to "game text" instead of "game list"

2017-08-17 Thread debianuser
Package: chessx
Version: 1.4.6-1
Severity: wishlist

Dear Maintainer,

As far as I can tell, there is no option to start chessx in a mode where it 
displays the game text window rather than game list, at bottom right. I have to 
manually select it every time.


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

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

Versions of packages chessx depends on:
ii  libc6 2.24-14
ii  libgcc1   1:7.1.0-13
ii  libgl1-mesa-glx [libgl1]  17.1.5-1
ii  libqt5core5a  5.7.1+dfsg-4
ii  libqt5gui55.7.1+dfsg-4
ii  libqt5multimedia5 5.7.1~20161021-2
ii  libqt5network55.7.1+dfsg-4
ii  libqt5printsupport5   5.7.1+dfsg-4
ii  libqt5svg55.7.1~20161021-2+b2
ii  libqt5widgets55.7.1+dfsg-4
ii  libqt5xml55.7.1+dfsg-4
ii  libstdc++67.1.0-13
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages chessx recommends:
ii  stockfish  8-3

chessx suggests no packages.

-- no debconf information



Bug#872512: move away from deprecated simple-patchsys

2017-08-17 Thread dann frazier
Source: google-perftools
Version: 2.5-2.2
Tags: patch

When building google-perftools, cdbs emits the following message:

CDBS WARNING:simple-patchsys.mk is deprecated since 0.4.85 - please use 
source format 3.0 (quilt) instead

In lieu of a diff, which would go out of date should the patchset
change, here's a set of commands you can run to make the transition:

mkdir debian/source
echo '3.0 (quilt)' > debian/source/format
find debian/patches -type f -not -name series | \
 sed 's,debian/patches/,,' > debian/patches/series
sed -i '/simple-patchsys\.mk/d' debian/rules



Bug#872194: espeakup: Espeakup fails to start due to libespeak-ng.so.1.1.49 segfault

2017-08-17 Thread Samuel Thibault
Control: tags -1 + moreinfo

Hello,

Steven Shiau, on mar. 15 août 2017 14:28:56 +0800, wrote:
> Espeakup fails to start due to libespeak-ng.so.1.1.49 segfault in Debian Sid.
> 
>* How to reproduce the issue?
>  Just run "sudo service espeakup start"

I can't reproduce it, I have these versions, and things work just fine
for me.

Does the crash happen very quickly, or some particular things need to be
done on the console?
What configuration do you have in /etc/default/espeakup?

Samuel



Bug#872511: s390x support

2017-08-17 Thread dann frazier
Source: google-perftools
Version: 2.5-2.2
Severity: important
Tags: patch, fixed-upstream

With one cherry-pick from upstream, google-perftools builds cleanly on
s390x and all tests pass.
diff -urpN google-perftools-2.5.orig/debian/control google-perftools-2.5/debian/control
--- google-perftools-2.5.orig/debian/control	2017-08-17 22:36:49.0 +
+++ google-perftools-2.5/debian/control	2017-08-17 22:38:16.154296198 +
@@ -11,7 +11,7 @@ Vcs-Browser: http://svn.debian.org/viewv
 
 Package: libgoogle-perftools-dev
 Section: libdevel
-Architecture: i386 amd64 powerpc ppc64el arm64 armel armhf
+Architecture: i386 amd64 powerpc ppc64el arm64 armel armhf s390x
 Depends: ${misc:Depends}, libgoogle-perftools4 (= ${binary:Version}), libtcmalloc-minimal4 (= ${binary:Version}), libunwind8-dev [amd64]
 Description: libraries for CPU and heap analysis, plus an efficient thread-caching malloc
  The gperftools, previously called google-perftools, package contains some
@@ -22,7 +22,7 @@ Description: libraries for CPU and heap
 
 Package: libtcmalloc-minimal4
 Section: libs
-Architecture: i386 amd64 powerpc ppc64el arm64 armel armhf
+Architecture: i386 amd64 powerpc ppc64el arm64 armel armhf s390x
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Description: efficient thread-caching malloc
  The gperftools, previously called google-perftools, package contains some
@@ -31,7 +31,7 @@ Description: efficient thread-caching ma
 
 Package: libgoogle-perftools4
 Section: libs
-Architecture: i386 amd64 powerpc ppc64el arm64 armel armhf
+Architecture: i386 amd64 powerpc ppc64el arm64 armel armhf s390x
 Depends: libtcmalloc-minimal4 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}
 Conflicts: libgoogle-perftools0
 Description: libraries for CPU and heap analysis, plus an efficient thread-caching malloc
diff -urpN google-perftools-2.5.orig/debian/patches/Add-support-for-31-bit-s390-merge-linux_syscall_supp.patch google-perftools-2.5/debian/patches/Add-support-for-31-bit-s390-merge-linux_syscall_supp.patch
--- google-perftools-2.5.orig/debian/patches/Add-support-for-31-bit-s390-merge-linux_syscall_supp.patch	1970-01-01 00:00:00.0 +
+++ google-perftools-2.5/debian/patches/Add-support-for-31-bit-s390-merge-linux_syscall_supp.patch	2017-08-17 23:18:16.546439347 +
@@ -0,0 +1,606 @@
+From bf8eacce69df877d1cecdab8c7a6cc3f218ebcc2 Mon Sep 17 00:00:00 2001
+From: Bryan Chan 
+Date: Wed, 15 Jun 2016 00:10:45 -0400
+Subject: [PATCH] Add support for 31-bit s390; merge linux_syscall_support.h
+ changes from upstream.
+
+---
+ configure.ac |   4 +-
+ m4/pc_from_ucontext.m4   |   2 +-
+ src/base/basictypes.h|   2 +-
+ src/base/linux_syscall_support.h | 293 ---
+ src/base/linuxthreads.h  |   2 +-
+ src/getpc.h  |   5 +
+ src/malloc_hook_mmap_linux.h |  16 +--
+ 7 files changed, 222 insertions(+), 102 deletions(-)
+
+diff --git a/configure.ac b/configure.ac
+index c7221ca..a688a25 100644
+--- a/configure.ac
 b/configure.ac
+@@ -53,8 +53,8 @@ case "$host" in
+*-darwin*) default_enable_heap_checker=no;;
+ esac
+ 
+-# Currently only backtrace works on s390x.
+-AC_COMPILE_IFELSE([AC_LANG_PROGRAM(, [return __s390x__])],
++# Currently only backtrace works on s390.
++AC_COMPILE_IFELSE([AC_LANG_PROGRAM(, [return __s390__])],
+   [default_enable_libunwind=no
+default_enable_backtrace=yes],
+   [default_enable_libunwind=yes
+diff --git a/m4/pc_from_ucontext.m4 b/m4/pc_from_ucontext.m4
+index d743fa4..c9224bc 100644
+--- a/m4/pc_from_ucontext.m4
 b/m4/pc_from_ucontext.m4
+@@ -27,7 +27,7 @@ AC_DEFUN([AC_PC_FROM_UCONTEXT],
+pc_fields="$pc_fields uc_mcontext.sc_ip"# Linux (ia64)
+pc_fields="$pc_fields uc_mcontext.pc"   # Linux (mips)
+pc_fields="$pc_fields uc_mcontext.uc_regs->gregs[[PT_NIP]]" # Linux (ppc)
+-   pc_fields="$pc_fields uc_mcontext.psw.addr" # Linux (s390x)
++   pc_fields="$pc_fields uc_mcontext.psw.addr" # Linux (s390)
+pc_fields="$pc_fields uc_mcontext.gregs[[R15]]" # Linux (arm old [untested])
+pc_fields="$pc_fields uc_mcontext.arm_pc"   # Linux (arm arch 5)
+pc_fields="$pc_fields uc_mcontext.gp_regs[[PT_NIP]]"  # Suse SLES 11 (ppc64)
+diff --git a/src/base/basictypes.h b/src/base/basictypes.h
+index b628709..72c27b4 100644
+--- a/src/base/basictypes.h
 b/src/base/basictypes.h
+@@ -363,7 +363,7 @@ class AssignAttributeStartEnd {
+ # elif (defined(__aarch64__))
+ #   define CACHELINE_ALIGNED __attribute__((aligned(64)))
+ // implementation specific, Cortex-A53 and 57 should have 64 bytes
+-# elif (defined(__s390x__))
++# elif (defined(__s390__))
+ #   define CACHELINE_ALIGNED __attribute__((aligned(256)))
+ # else
+ #   error Could not determine cache line length - unknown architecture
+diff --git a/src/base/linux_syscall_support.h 

Bug#872509: ITP: inhomog -- kinematical backreaction and average scale factor evolution

2017-08-17 Thread Jonas Smedegaard
Hi Boud,

Quoting Boud Roukema (2017-08-18 00:01:59)
>   This package contains an example front end program that uses the 
>   biscale_partition routines of the inhomog library, illustrating 
>   effective scale factor evolution in a universe with a T^3 spatial 
>   section that is divided into two complementary domains. The inhomog 
>   library provides Raychaudhuri integration of cosmological 
>   domain-wise average scale factor evolution using an analytical 
>   formula for kinematical backreaction Q_D evolution. The library 
>   routine lib/Omega_D_precalc.c is callable by RAMSES using 
>   ramses-scalav.
>   .
>   You may use this front-end program for command-line investigation of 
>   the role of virialisation as a potential replacement for dark energy 
>   (see Roukema 2017, arXiv:1706.06179).

I have never seen a package description so stuffed with advanced 
technical terms.

I am very impressed at how it still (I guess) succeeds at hinting at its 
purpose for non-experts like myself.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature


Bug#872510: debhelper: dh_update_autotools_config does not handle old config.* files

2017-08-17 Thread Guillem Jover
Package: debhelper
Version: 10.7.2
Severity: wishlist

Hi!

I was updating the arj package to switch from its manual code to
update config.* to use dh_update_autotools_config, but while checking
the source after noticing it didn't do anything, saw that it only
considers config.* files if they contain a timestamp= line withing
the first 10 lines. Which means I cannot use that command, as old
files didn't contain that marker. :(

Could the detection be improved, or new options added to either force
it or to be able to specify the files to update?

Thanks,
Guillem



Bug#854387: owner

2017-08-17 Thread Bastien ROUCARIES
control: owner -1 ro...@debian.org



Bug#872475: libisofs6: buffer under-read in read_rr_SL()

2017-08-17 Thread Jakub Wilk

* Thomas Schmitt , 2017-08-17, 21:36:

i see the bug in the code but not the attached ISO.


Oops. Now really attached.

--
Jakub Wilk


underread.iso.gz
Description: application/gzip


Bug#857540: scite: Scroll bar not moving when scrolling

2017-08-17 Thread Andreas Ronnquist
> This seems to be fixed in 4.0, which were advertised on the Scintilla
> mailinglist earlier today.
> 
> From the changelist:
> * On GTK+ fix drawing problems including incorrect scrollbar redrawing
> and flickering of text. Bug #1876.
> 
> I have installed it on my unstable virtual machine, and the problems
> as described in this bug report I had earlier have gone away.
> 

I'll take that back - I have tested in another virtual machine, also
Debian unstable (upgraded and up to date), and _not_ upgraded to SciTE
4.0 (still on Debian packaged 3.7.2) - there too the problem is gone, so
the solution must be elsewhere.

-- Andreas Rönnquist
gus...@debian.org



Bug#872410: AHCI module not loaded when using preseed

2017-08-17 Thread Ben Hutchings
On Thu, 2017-08-17 at 17:48 +0200, Cyril Brulebois wrote:
> Hi Gilles,
> 
> Gilles MOREL  (2017-08-17):
> > After some search, I noticed that the ahci kernel module was not
> > loaded when I use preseed.
> 
> This is strange, it seems the sata-modules udeb is fetched just fine,
> I'm not sure why ahci wouldn't be loaded.
> 
> linux.git has this as its configuration:
> 
> debian/installer/modules/sata-modules:drivers/ata/ahci* ?
> 
> so ahci* modules should end up in that udeb, and that's indeed the
> case for what I can see.
> 
> Are you using brand new hardware for which support might be missing?
> Is the non-preseed installation loading appropriate modules… on the
> same HW as the failing preseed installation?

Could this be due to a missing 'depmod' in the installer?

Ben.

-- 
Ben Hutchings
This sentence contradicts itself - no actually it doesn't.



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


Bug#872509: ITP: inhomog -- kinematical backreaction and average scale factor evolution

2017-08-17 Thread Boud Roukema

Package: wnpp
Severity: wishlist
Owner: Boud Roukema 

* Package name: inhomog
  Version : 0.1.5
  Upstream Author : Boud Roukema, Jan Ostrowski, Justyna Borkowska
* URL : https://bitbucket.org/broukema/inhomog
* License : GPL-2+
  Programming Lang: C
  Description : kinematical backreaction and average scale factor evolution

This is a library (shared + static) and a front-end example program
used for relativistic cosmology. The front-end `inhomog' provides
command-line numerical exploration of a key question in present-day
observational cosmology (is dark energy just an artefact of not
modelling structure formation properly?) and the library is aimed for
use by more computationally intensive simulations studying the same
family of questions. The description of the binary is here:

 This package contains an example front end program that uses the
 biscale_partition routines of the inhomog library, illustrating
 effective scale factor evolution in a universe with a T^3 spatial
 section that is divided into two complementary domains. The inhomog
 library provides Raychaudhuri integration of cosmological
 domain-wise average scale factor evolution using an analytical formula for
 kinematical backreaction Q_D evolution. The library routine
 lib/Omega_D_precalc.c is callable by RAMSES using ramses-scalav.
 .
 You may use this front-end program for command-line investigation
 of the role of virialisation as a potential replacement for dark
 energy (see Roukema 2017, arXiv:1706.06179).

Team: Debian Astro

The aim is for this source package and the associated binary and
library packages created from it to be maintained by the Debian Astro
team.

Sponsor:

I will need a sponsor, since I'm not a debian developer.  I'm
presently maintaining mpgrafic as part of the Debian Astro team.
This is my first try at debian packaging a library. I was happy
to find that this time around :), I found the libtool documentation
quite straightforward for creating both a shared and static library.

Cheers
Boud



Bug#859157: multipath-tools: after bootup multipathd timeout on commands - requires daemon restart

2017-08-17 Thread Info ZioSEM
Dear mantainer,

I'm hitting this bug also. Simptoms are exactly the same described by Alban, 
altough the setup is quite different. The problem arise in a proxmox 
environment where a PV is configured on a shared iscsi LUN. The iscsi LUN is 
quite lazy to come online at boot, because the ethernet interface needs about 
30 sec to become active. This is due to the spanning tree loop check performed 
by the cisco switch on the other side. After the boot, multipath -ll return no 
paths and multipathd goes stuck, as Alban said.

I can confirm that recompiling multipath-tools package with Alban's patch solve 
the problem. So far, no regression for me.

I think would be great to include the patch in a stretch update of the 
package, the bug could be not so hard to hit in many situations, IMHO.

Many thanks to Alban for his analisys and for providing the patch.

Thank you,

--
Ciao,
S.



Bug#872508: RFS: minetest-mod-character-creator/1.0-1 ITP

2017-08-17 Thread Julien Puydt
Package: sponsorship-requests
Severity: wishlist

  Dear mentors,

  I am looking for a sponsor for my package "minetest-mod-character-creator"

 * Package name: minetest-mod-character-creator
   Version : 1.0-1
   Upstream Author : Rui
 * URL : https://github.com/minetest-mods/character_creator
 * License : Expat & CC-BY-SA-3.0
   Section : games

  It builds those binary packages:

minetest-mod-character-creator - Minetest module to customize your skin

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

  https://mentors.debian.net/package/minetest-mod-character-creator


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

dget -x
https://mentors.debian.net/debian/pool/main/m/minetest-mod-character-creator/minetest-mod-character-creator_1.0-1.dsc

  It is packaged within the Debian Games Team repositories:
Vcs-Git:
https://anonscm.debian.org/git/pkg-games/minetest-mod-character-creator.git
Vcs-Browser:
https://anonscm.debian.org/git/pkg-games/minetest-mod-character-creator.git

Thanks,

Snark on #debian-games



Bug#790222: [boinc_dev] Bug#790222: wxwidgets3.0: depends on libwebkitgtk-1.0-0 which is deprecated

2017-08-17 Thread Jeremy Bicha
> But as I've said already, I don't have a problem with just disabling
> webview before buster if it comes to it.  It just seems unhelpful to
> boinc users running testing to do that right now, unless you're actually
> at the point of removing the old webkitgtk from testing.

Removal of webkitgtk from testing is still a few weeks away.

But in my opinion, this is the last package blocking removal of
webkitgtk from Ubuntu 17.10. Removal there is also probably a few
weeks away since many Ubuntu removals happen late in Ubuntu's release
cycle.)

Thanks,
Jeremy Bicha



Bug#869953: budgie-core: Adapt to gnome-settings-daemon 3.24

2017-08-17 Thread Bruno Miguel
Changing the RequiredComponents content fixed things. I now have
"RequiredComponents=org.gnome.SettingsDaemon.A11yKeyboard;org.gnome.SettingsDaemon.A11ySettings;org.gnome.SettingsDaemon.Clipboard;org.gnome.SettingsDaemon.Color;org.gnome.SettingsDaemon.Datetime;org.gnome.SettingsDaemon.Housekeeping;org.gnome.SettingsDaemon.Keyboard;org.gnome.SettingsDaemon.MediaKeys;org.gnome.SettingsDaemon.Mouse;org.gnome.SettingsDaemon.Orientation;org.gnome.SettingsDaemon.Power;org.gnome.SettingsDaemon.PrintNotifications;org.gnome.SettingsDaemon.Rfkill;org.gnome.SettingsDaemon.ScreensaverProxy;org.gnome.SettingsDaemon.Sharing;org.gnome.SettingsDaemon.Smartcard;org.gnome.SettingsDaemon.Sound;org.gnome.SettingsDaemon.Wacom;org.gnome.SettingsDaemon.XRANDR;org.gnome.SettingsDaemon.XSettings;budgie-wm;budgie-daemon;budgie-panel;budgie-polkit;"

Thanks for the help!

On Thu, Aug 17, 2017 at 10:09 PM, Bruno Miguel
 wrote:
> On Thu, Aug 17, 2017 at 9:21 PM, Jeremy Bicha  wrote:
>> Control: reopen -1
>>
>> On Thu, Aug 17, 2017 at 3:47 PM, Bruno Miguel
>>  wrote:
>>> I've installed Budgie in Testing and it won't login due to missing gnome-
>>> settings-daemon binary.
>>
>> I downloaded budgie-core 10.3.1-4+b1 from
>> https://packages.debian.org/sid/amd64/budgie-core/download
>>
>> and verified that
>> /usr/share/gnome-session/sessions/budgie-desktop.session contains this
>> line:
>>
>> RequiredComponents=gnome-settings-daemon;budgie-wm;budgie-daemon;budgie-panel;budgie-polkit;
>>
>> which won't work with gnome-settings-daemon 3.24. It should have the
>> individual gnome-settings-daemon binaries instead of
>> 'gnome-settings-daemon' listed.
>
> It does have 
> "RequiredComponents=gnome-settings-daemon;budgie-wm;budgie-daemon;budgie-panel;budgie-polkit;"
>
> I'll change it and test.
>
>> Thanks,
>> Jeremy Bicha
>
> Cheers.



Bug#872507: [ifcico] ifcico segfaults when started

2017-08-17 Thread Ingo Juergensmann
Package: ifcico
Version: 2.14tx8.10-23
Severity: normal

--- Please enter the report below this line. ---

Hi!

I'm trying to get my Fido node running again with modem line.

When invoked by mgetty, ifcico segfaults:

08/17 22:57:03 yS0   got:  12000/ARQ/V42b[0d]
08/17 22:57:03 yS0CND: CONNECT 12000/ARQ/V42b
08/17 22:57:03 yS0CND: found: 12000/ARQ/V42b[0a] ** found **
08/17 22:57:03 yS0   waiting for line to clear (VTIME=3), read:  [0d] [0d]
08/17 22:57:03 yS0  warning: carrier signal is ignored
08/17 22:57:03 yS0looking for utmp entry... (my PID: 23668)
08/17 22:57:04 yS0   tio_set_flow_control( HARD )
08/17 22:57:04 yS0   print welcome banner (/etc/issue.mgetty)
08/17 22:57:04 yS0   getlogname (FIDO AUTO_PPP), read: [0d]
08/17 22:57:04 yS0   input finished with '\r', setting ICRNL ONLCR
08/17 22:57:04 yS0   tio_set_flow_control( HARD )
08/17 22:57:04 yS0   print welcome banner (/etc/issue.mgetty)
08/17 22:57:04 yS0   getlogname (FIDO AUTO_PPP), read: [0d]
08/17 22:57:04 yS0   input finished with '\r', setting ICRNL ONLCR
08/17 22:57:04 yS0   tio_set_flow_control( HARD )
08/17 22:57:04 yS0   print welcome banner (/etc/issue.mgetty)
08/17 22:57:04 yS0   getlogname (FIDO AUTO_PPP), read:**EMSI_
08/17 22:57:04 yS0   got EMSI signature
08/17 22:57:04 yS0   input finished with '\r', setting ICRNL ONLCR
08/17 22:57:04 yS0   tio_get_rs232_lines: status: RTS CTS DSR DTR DCD
08/17 22:57:04 yS0login: use login config file /etc/mgetty/login.config
08/17 22:57:04 yS0   match: user='_**EMSI_INQC816', key=''
08/17 22:57:04 yS0   match: user='_**EMSI_INQC816', key='/FIDO/'*** hit!
08/17 22:57:04 yS0   login: utmp entry: ftn
08/17 22:57:04 yS0looking for utmp entry... (my PID: 23668)
08/17 22:57:04 yS0   login: user id: uucp (uid 10, gid 10)
08/17 22:57:04 yS0   calling login: cmd='/usr/lib/ifmail/ifcico',
argv[]='ifcico **EMSI_INQC816'
08/17 22:57:04 yS0   setenv: 'CALLER_ID=none'
08/17 22:57:04 yS0   setenv: 'CONNECT=12000/ARQ/V42b'
08/17 22:57:04 yS0   setenv: 'DEVICE=ttyS0'
08/17 22:57:04 # data dev=ttyS0, pid=23668, caller='none',
conn='12000/ARQ/V42b', name='', cmd='/usr/lib/ifmail/ifcico',
user='**EMSI_INQC816'

==> /var/log/syslog <==
Aug 17 22:57:04 muaddib systemd[1]: mgetty.service: Main process exited,
code=killed, status=11/SEGV
Aug 17 22:57:04 muaddib systemd[1]: mgetty.service: Unit entered failed
state.
Aug 17 22:57:04 muaddib systemd[1]: mgetty.service: Failed with result
'signal'.
Aug 17 22:57:04 muaddib kernel: [2389715.757624] ifcico[23668]: segfault
at 0 ip 55bf88ec2493 sp 7ffd1d0b2490 error 6 in
ifcico[55bf88eb9000+3e000]
Aug 17 22:57:04 muaddib systemd[1]: mgetty.service: Service hold-off
time over, scheduling restart.
Aug 17 22:57:04 muaddib systemd[1]: Stopped Smart Modem Getty(mgetty).
Aug 17 22:57:04 muaddib systemd[1]: Started Smart Modem Getty(mgetty).


If even segfaults when called from command line:

#  /usr/lib/ifmail/ifcico
Segmentation fault

Strace shows this:

write(2, "creating directory tree for \"/va"..., 54) = 54
mkdir("/var", 0700) = -1 EEXIST (File exists)
write(2, "mkdir(\"/var\") errno 17\n", 23) = 23
mkdir("/var/spool", 0700)   = -1 EEXIST (File exists)
write(2, "mkdir(\"/var/spool\") errno 17\n", 29) = 29
mkdir("/var/spool/ftn", 0700)   = -1 EEXIST (File exists)
write(2, "mkdir(\"/var/spool/ftn\") errno 17"..., 33) = 33
mkdir("/var/spool/ftn/inb", 0700)   = -1 EEXIST (File exists)
write(2, "mkdir(\"/var/spool/ftn/inb\") errn"..., 37) = 37
mkdir("/var/spool/ftn/inb/tmp", 0700)   = -1 EEXIST (File exists)
write(2, "mkdir(\"/var/spool/ftn/inb/tmp\") "..., 41) = 41
ioctl(0, TCGETS, {B38400 opost isig icanon echo ...}) = 0
fstat(0, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 4), ...}) = 0
readlink("/proc/self/fd/0", "/dev/pts/4", 4095) = 10
stat("/dev/pts/4", {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 4), ...}) = 0
ioctl(0, TCGETS, {B38400 opost isig icanon echo ...}) = 0
fstat(0, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 4), ...}) = 0
readlink("/proc/self/fd/0", "/dev/pts/4", 4095) = 10
stat("/dev/pts/4", {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 4), ...}) = 0
open("/etc/localtime", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=2335, ...}) = 0
fstat(3, {st_mode=S_IFREG|0644, st_size=2335, ...}) = 0
read(3,
"TZif2\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\t\0\0\0\t\0\0\0\0"..., 4096)
= 2335
lseek(3, -1476, SEEK_CUR)   = 859
read(3,
"TZif2\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\t\0\0\0\t\0\0\0\0"..., 4096)
= 1476
close(3)= 0
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=NULL} ---
+++ killed by SIGSEGV +++
Segmentation fault


... and gdb this:

(gdb) r
Starting program: /usr/lib/ifmail/ifcico

Program received signal SIGSEGV, Segmentation fault.
0xd493 in ?? ()
(gdb) bt
#0  0xd493 in ?? ()
#1  0xe5c9 in ?? ()
#2  0xeb19 in ?? ()
#3  0xfb0b in ?? ()
#4  0x5556ccfc in 

Bug#872506: profitbricks-sdk-python FTBFS: UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 11333: ordinal not in range(128)

2017-08-17 Thread Adrian Bunk
Source: profitbricks-sdk-python
Version: 4.1.0-1
Severity: serious

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

...
I: pybuild base:184: python3.6 setup.py clean 
Traceback (most recent call last):
  File "setup.py", line 48, in 
long_desc = read('README.md')
  File "setup.py", line 35, in read
return codecs.open(os.path.join(here, *parts), 'r').read()
  File "/usr/lib/python3.6/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 11333: 
ordinal not in range(128)
E: pybuild pybuild:283: clean: plugin distutils failed with: exit code=1: 
python3.6 setup.py clean 
dh_auto_clean: pybuild --clean -i python{version} -p "3.6 3.5" returned exit 
code 13
debian/rules:6: recipe for target 'clean' failed
make: *** [clean] Error 25



Bug#872393: sphinx: autopkgtest failure on armhf with webkit2gtk 2.17.90

2017-08-17 Thread Michael Catanzaro
Hi, thanks for reporting this crash upstream. Turns out one of our 
developers debugged this earlier today. Should be fixed in 2.17.91, and 
there's a patch upstream if you need it sooner.


Michael



Bug#872505: backports-website: "stretch" link misnamed

2017-08-17 Thread Vincent Legoll
Package: backports-website
Severity: normal

Dear Maintainer,

The link to:
http://packages.debian.org/stretch-backports/
is named "jessie-backports" on page:
https://backports.debian.org/Packages/
it should be named "stretch-backports" instead.

Please merge the attached git patch to fix this.



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

Kernel: Linux 4.12.0+ (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
>From e4e4760a093abcbc00afa346c9753bd05c649624 Mon Sep 17 00:00:00 2001
From: Vincent Legoll 
Date: Thu, 17 Aug 2017 23:05:48 +0200
Subject: [PATCH] Fix link to stretch backports overview

Signed-off-by: Vincent Legoll 
---
 Packages.mdwn | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Packages.mdwn b/Packages.mdwn
index 31cb0f9..6bb6143 100644
--- a/Packages.mdwn
+++ b/Packages.mdwn
@@ -2,7 +2,7 @@
 
 If you are interested in a browseable directory included in debian-backports, you can use these overviews: 
 
-http://packages.debian.org/stretch-backports/;>jessie-backports
+http://packages.debian.org/stretch-backports/;>stretch-backports
 http://packages.debian.org/jessie-backports/;>jessie-backports
 http://packages.debian.org/jessie-backports-sloppy/;>jessie-backports-sloppy
 
-- 
2.7.4



Bug#864848: Should not talk about hd-media - that's armhf only

2017-08-17 Thread Holger Wansing
Control: tags -1 + pending

On Thu, 17 Aug 2017 20:55:46 +0100
Steve McIntyre  wrote:
> On Thu, Aug 17, 2017 at 09:17:22PM +0200, Holger Wansing wrote:
> >On Thu, 15 Jun 2017 22:51:21 +0100
> >Steve McIntyre  wrote:
> >> Package: installation-guide-armel
> >> Severity: normal
> >> 
> >> As seen in
> >> 
> >>   https://www.debian.org/releases/jessie/armel/ch05s01.html.en
> >> 
> >> there's discussion of "unpack the hd-media tarball". This doesn't
> >> exist on armel...
> >
> >Does that mean, that armel does not support that "Boot from USB stick in
> >U-Boot" thingy, described under above link?
> >If that _is_ supported, that chapter needs to be rewritten (simply leaving
> >out the part where the hd-media tarball is mentioned, would make the whole
> >chapter senseless/important part missing).
> 
> To the best of my knowledge, we don't have any such support in the
> armel port. I'd love to be corrected on this, but I don't see anything
> like that in our d-i builds.

Ok, so I removed that whole chapter for armel.

Tagging this bug as pending.


Thanks
Holger


-- 
Holger Wansing 



Bug#872441: stretch-pu: package gsoap/2.8.35-4+deb9u1

2017-08-17 Thread Adam D. Barratt
On Thu, 2017-08-17 at 20:22 +0200, Martin Zobel-Helas wrote:
> Hi, 
> 
> On Thu Aug 17, 2017 at 16:38:36 +0200, Mattias Ellert wrote:
[...]
> > +gsoap (2.8.35-4+deb9u1) stretch; urgency=medium
> > +
> > +  * Fix for CVE-2017-9765 (Closes: )
> > +
> > + -- Mattias Ellert   Wed, 16 Aug 2017 
> > 11:58:11 +0200
> > +
> >  gsoap (2.8.35-4) unstable; urgency=medium
> 
> once this changelog has a proper Closes line with bug-number this patch
> looks sane to me.

Is there actually a Debian bug for the issue? I couldn't find one.

Regards,

Adam



Bug#869953: budgie-core: Adapt to gnome-settings-daemon 3.24

2017-08-17 Thread Bruno Miguel
On Thu, Aug 17, 2017 at 9:21 PM, Jeremy Bicha  wrote:
> Control: reopen -1
>
> On Thu, Aug 17, 2017 at 3:47 PM, Bruno Miguel
>  wrote:
>> I've installed Budgie in Testing and it won't login due to missing gnome-
>> settings-daemon binary.
>
> I downloaded budgie-core 10.3.1-4+b1 from
> https://packages.debian.org/sid/amd64/budgie-core/download
>
> and verified that
> /usr/share/gnome-session/sessions/budgie-desktop.session contains this
> line:
>
> RequiredComponents=gnome-settings-daemon;budgie-wm;budgie-daemon;budgie-panel;budgie-polkit;
>
> which won't work with gnome-settings-daemon 3.24. It should have the
> individual gnome-settings-daemon binaries instead of
> 'gnome-settings-daemon' listed.

It does have 
"RequiredComponents=gnome-settings-daemon;budgie-wm;budgie-daemon;budgie-panel;budgie-polkit;"

I'll change it and test.

> Thanks,
> Jeremy Bicha

Cheers.



Bug#872504: gdm3 frozen when starting

2017-08-17 Thread Tomáš Břinčil
Package: gdm
Version: 3.22.3-3
OS: Debian 9.1
 
When I am trying to start gnome using gdm3 service, it freezes and there is no 
possibility get the login screen.
While I use sddm, everything works and I can reach login screen and log in the 
system.
I used to work on Debian 8 and it worked. The machine the Debian is running on 
is virtual private server on virtio.
 
Best regards
 
    Tomas Brincil
 
 



Bug#869953: budgie-core: Adapt to gnome-settings-daemon 3.24

2017-08-17 Thread Bruno Miguel
On Thu, Aug 17, 2017 at 9:06 PM, David  wrote:
> How did you install? - the correct package is budgie-desktop -
> https://packages.debian.org/buster/budgie-desktop

I installed it with apt install budgie-desktop

> as you can see gnome-settings-daemon is a dependency
>
> run
>
> sudo apt update
> sudo apt install --reinstall budgie-desktop gnome-settings-daemon

I've even tried installing from Unstable, but got the same error.

> On Thu, 17 Aug, 2017 at 8:47 PM, Bruno Miguel
>  wrote:
>
> Package: budgie-core Version: 10.3.1-4+b1 Followup-For: Bug #869953 I've
> installed Budgie in Testing and it won't login due to missing gnome-
> settings-daemon binary. Log: ago 17 20:35:30 carlsagan dbus-daemon[2485]:
> Activating via systemd: service name='org.a11y.Bus'
> unit='at-spi-dbus-bus.service' ago 17 20:35:30 carlsagan systemd[2464]:
> Starting Accessibility services bus... ago 17 20:35:30 carlsagan
> dbus-daemon[2485]: Successfully activated service 'org.a11y.Bus' ago 17
> 20:35:30 carlsagan systemd[2464]: Started Accessibility services bus. ago 17
> 20:35:30 carlsagan at-spi-bus-launcher[2553]: Activating service
> name='org.a11y.atspi.Registry' ago 17 20:35:30 carlsagan
> at-spi-bus-launcher[2553]: Successfully activated service
> 'org.a11y.atspi.Registry' ago 17 20:35:30 carlsagan
> org.a11y.atspi.Registry[2558]: SpiRegistry daemon is running with well-known
> name - org.a11y.atspi.Registry ago 17 20:35:30 carlsagan
> gnome-session[2487]: gnome-session-binary[2487]: WARNING: Unable to find
> required component 'gnome-settings-daemon' ==> ago 17 20:35:30 carlsagan
> gnome-session-binary[2487]: WARNING: Unable to find required component
> 'gnome-settings-daemon' ago 17 20:35:30 carlsagan
> gnome-session-binary[2487]: Entering running state ==> ago 17 20:35:30
> carlsagan gnome-session[2487]: Unable to init server: Could not connect:
> Connection refused ==> ago 17 20:35:30 carlsagan gnome-session-f[2568]:
> Cannot open display: ago 17 20:35:30 carlsagan gnome-session[2487]:
> gnome-session-binary[2487]: GLib-GObject-CRITICAL: g_object_unref: assertion
> 'G_IS_OBJECT (object)' failed ago 17 20:35:30 carlsagan
> gnome-session-binary[2487]: GLib-GObject-CRITICAL: g_object_unref: assertion
> 'G_IS_OBJECT (object)' failed ago 17 20:35:30 carlsagan gnome-session[2487]:
> gnome-session-binary[2487]: GLib-GObject-CRITICAL: g_object_unref: assertion
> 'G_IS_OBJECT (object)' failed ago 17 20:35:30 carlsagan
> gnome-session-binary[2487]: GLib-GObject-CRITICAL: g_object_unref: assertion
> 'G_IS_OBJECT (object)' failed ago 17 20:35:30 carlsagan
> gnome-session-binary[2487]: GLib-GObject-CRITICAL: g_object_unref: assertion
> 'G_IS_OBJECT (object)' failed -- System Information: Debian Release:
> buster/sid APT prefers testing APT policy: (900, 'testing') Architecture:
> amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.12.8-xanmod9 (SMP
> w/2 CPU cores; PREEMPT) Locale: LANG=pt_PT.UTF-8, LC_CTYPE=pt_PT.UTF-8
> (charmap=UTF-8), LANGUAGE=pt_PT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked
> to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages
> budgie-core depends on: ii dconf-gsettings-backend [gsettings-backend]
> 0.26.0-2+b1 ii libbudgie-plugin0 10.3.1-4+b1 ii libbudgietheme0 10.3.1-4+b1
> ii libc6 2.24-12 ii libcairo2 1.14.10-1 ii libgdk-pixbuf2.0-0 2.36.5-2 ii
> libgirepository-1.0-1 1.50.0-2 ii libglib2.0-0 2.53.4-3 ii
> libgnome-bluetooth13 3.20.1-1 ii libgnome-desktop-3-12 3.22.2-1 ii
> libgnome-menu-3-0 3.13.3-9 ii libgtk-3-0 3.22.18-1 ii libibus-1.0-5 1.5.14-3
> ii libmutter0i 3.22.4-2 ii libpeas-1.0-0 1.20.0-1+b1 ii libpolkit-agent-1-0
> 0.105-18 ii libpolkit-gobject-1-0 0.105-18 ii libpulse-mainloop-glib0 10.0-2
> ii libpulse0 10.0-2 ii libraven0 10.3.1-4+b1 ii libupower-glib3 0.99.5-3 ii
> libuuid1 2.29.2-2 ii libwnck-3-0 3.24.0-1 ii libx11-6 2:1.6.4-3 budgie-core
> recommends no packages. budgie-core suggests no packages. -- no debconf
> information



Bug#872503: ffmpeg: armhf SIGBUS in ff_diff_pixels_armv6 running winff autopkgtest

2017-08-17 Thread James Cowgill
Source: ffmpeg
Version: 7:3.3.3-3
Severity: important
Control: found -1 7:3.2.4-1
Control: affects -1 src:winff

Hi,

Just noticed that winff's autopkgtests fail on armhf because ffmpeg
receives a SIGBUS.

The failing command is:

> /usr/bin/ffmpeg -i test.avi -vcodec flv -f flv -r 29.97 -vf scale=w=320:h=240 
> -aspect 4:3 -b:v 300k -g 160 -cmp dct -subcmp dct -mbd 2 -flags +aic+mv0+mv4 
> -trellis 1 -ac 1 -ar 22050 -b:a 56k -y -t 1 test.flv

Where test.avi can be obtained from the winff source package:
https://sources.debian.net/src/winff/1.5.5-1/debian/tests/test.avi/

Backtrace:
> (gdb) bt
> #0  ff_diff_pixels_armv6 () at src/libavcodec/arm/pixblockdsp_armv6.S:46
> #1  0xf6540fe8 in dct_sad8x8_c (h=8, stride=352,
> src2=0xaacf377f 
> "ddefhiiihmmmnnnoopqqruuuvvvwwyyz{{|}}\200\200\201\201\202\203\203\203\202\202\202\203\203\203\204\204\206\205\205\204\204\203\203\203\200\201\201\201\201\202\202\202\206\206\206\206\206\206\206\206\210\212\215\220\222\222\221\220\220\220\220\221\221\222\222\222\223\223\224\225\225\226\226\227\235\235\236\236\236",
>  '\237' , 
> "\240\240\241\241\242\242\243\243\243\244\245\245\246\246\247\250\250\251\251\252\252\253\251\251\252\252\252\253\253\253\255\255\255\255\255\255\255\255\256\256\257\257\257\260\260\260\261\261\261\261\261\261\261\261\263\263\263\264\264\264\265\265\264\264\264\264\264\264\264"...,
> src1=0xaadf6990 
> "bcegijjkkklononnnmnnnoppqqqrvvuuuvwxy{|~~\177\200\201\201\202\203\202\202\203\204\204\204\204\205\205\206\206\206\206\205\205\205\204\203\203\203\202\202\202\202\202\203\204\204\205\205\207\211\210\211\213\215\220\222\222\221\221\221\221\220\220\220\220\221\223\223\224\225\226\225\225\225\227\232\233\234\235\235\234\234\235\235\235\236\237\236\237\240\237\236\236\237\237\237\240\241\241\241\241\242\243\243\243\244\245\244\245\246\246\246\247\247\250\251\252\253\253\253\253\252\252\254\254\254\254\254\255\255\256\257\257\257\257\257\257\257\257\260\260\261\262\262\261\260\261\261\262\262\262\263\264\264\264\264\264\264\264\264\264\264\263"...,
>  s=0xaac58b10) at src/libavcodec/me_cmp.c:631
> #2  dct_sad16_c (s=0xaac58b10,
> dst=0xaadf6990 
> "bcegijjkkklononnnmnnnoppqqqrvvuuuvwxy{|~~\177\200\201\201\202\203\202\202\203\204\204\204\204\205\205\206\206\206\206\205\205\205\204\203\203\203\202\202\202\202\202\203\204\204\205\205\207\211\210\211\213\215\220\222\222\221\221\221\221\220\220\220\220\221\223\223\224\225\226\225\225\225\227\232\233\234\235\235\234\234\235\235\235\236\237\236\237\240\237\236\236\237\237\237\240\241\241\241\241\242\243\243\243\244\245\244\245\246\246\246\247\247\250\251\252\253\253\253\253\252\252\254\254\254\254\254\255\255\256\257\257\257\257\257\257\257\257\260\260\261\262\262\261\260\261\261\262\262\262\263\264\264\264\264\264\264\264\264\264\264\263"...,
> src=0xaacf377f 
> "ddefhiiihmmmnnnoopqqruuuvvvwwyyz{{|}}\200\200\201\201\202\203\203\203\202\202\202\203\203\203\204\204\206\205\205\204\204\203\203\203\200\201\201\201\201\202\202\202\206\206\206\206\206\206\206\206\210\212\215\220\222\222\221\220\220\220\220\221\221\222\222\222\223\223\224\225\225\226\226\227\235\235\236\236\236",
>  '\237' , 
> "\240\240\241\241\242\242\243\243\243\244\245\245\246\246\247\250\250\251\251\252\252\253\251\251\252\252\252\253\253\253\255\255\255\255\255\255\255\255\256\256\257\257\257\260\260\260\261\261\261\261\261\261\261\261\263\263\263\264\264\264\265\265\264\264\264\264\264\264\264"...,
>  stride=352, h=16) at src/libavcodec/me_cmp.c:971
> #3  0xf6570cec in cmp_inline (chroma=0, qpel=0, chroma_cmp_func= out>, cmp_func=0x0, src_index=, ref_index=,
> h=16, size=0, suby=0, subx=0, y=, x=-1, s=0x0) at 
> src/libavcodec/motion_est.c:217
> #4  cmp_simple (chroma_cmp_func=, cmp_func=0x0, 
> src_index=, ref_index=, y=, 
> x=-1, s=0x0)
> at src/libavcodec/motion_est.c:234
> #5  cmp (flags=0, chroma_cmp_func=, cmp_func=0x0, 
> src_index=, ref_index=, h=16, size=0, suby=0, 
> subx=0,
> y=, x=-1, s=0x0) at src/libavcodec/motion_est.c:266
> #6  small_diamond_search (flags=0, h=16, size=0, penalty_factor=-16, 
> ref_index=240, src_index=2, dmin=, best=0xfffee064, s=0x0)
> at src/libavcodec/motion_est_template.c:445
> #7  diamond_search (flags=0, h=16, size=0, penalty_factor=-16, ref_index=240, 
> src_index=2, dmin=, best=0xfffee064, s=0x0)
> at src/libavcodec/motion_est_template.c:840
> #8  epzs_motion_search_internal (h=16, size=0, flags=0, ref_mv_scale=0, 
> last_mv=0x0, ref_index=-162058212, src_index=0, P=0xfffee01c,
> my_ptr=0xf77efce8 <__stack_chk_guard>, mx_ptr=0x15, s=0x1196a700) at 
> src/libavcodec/motion_est_template.c:966
> #9  ff_epzs_motion_search (s=0x1196a700, s@entry=0xaac58b10, mx_ptr=0x15, 
> mx_ptr@entry=0xfffee0e4, my_ptr=0xf77efce8 <__stack_chk_guard>,
> my_ptr@entry=0xfffee0e8, P=P@entry=0xfffee0ec, 
> src_index=src_index@entry=0, ref_index=ref_index@entry=0, last_mv=0xaaccf9b8, 
> ref_mv_scale=32768,
> ref_mv_scale@entry=65536, 

Bug#872410: AHCI module not loaded when using preseed

2017-08-17 Thread Gilles MOREL
Hi Cyril,

The ahci kernel module does exist in debian-installer, I can load manually and, 
then, the hard drive appears, but too late.
When I manually install, the kernel modules are correctly (that is to say 
xhci_pci AND ahci).
The hardware was bought in 2016.

I don't know about linux.git configuration, I don't use it in debian-installer.
--
Gilles Émilien MOREL 
Ce message et toutes les pièces jointes sont établies à l'intention exclusive 
de ses destinataires et sont confidentiels. Si vous n'êtes pas le destinataire 
de ce message, merci de détruire votre ordinateur par le feu et d'avertir 
immédiatement les pompiers.

- Message original 
Cyril Brulebois 
à Gilles MOREL , 872...@bugs.debian.org
le jeudi 17 août 2017 à 17:48:10 +0200
avec Mutt/1.5.23 (2014-03-12)

Re: Bug#872410: AHCI module not loaded when using preseed
---
Hi Gilles,

Gilles MOREL  (2017-08-17):
> After some search, I noticed that the ahci kernel module was not
> loaded when I use preseed.

This is strange, it seems the sata-modules udeb is fetched just fine,
I'm not sure why ahci wouldn't be loaded.

linux.git has this as its configuration:

debian/installer/modules/sata-modules:drivers/ata/ahci* ?

so ahci* modules should end up in that udeb, and that's indeed the
case for what I can see.

Are you using brand new hardware for which support might be missing?
Is the non-preseed installation loading appropriate modules… on the
same HW as the failing preseed installation?


KiBi.


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


Bug#872330: nvidia-legacy-340xx-kernel-dkms: Build against Linux 4.12 fails

2017-08-17 Thread Luca Boccassi
Control: tags -1 pending

On Wed, 2017-08-16 at 12:43 +0100, Tim Marston wrote:
> Package: nvidia-legacy-340xx-kernel-dkms
> Version: 340.102-2
> Severity: normal
> 
> Dear Maintainer,
> 
> After a recent package update (sid) which took the kernel to 3.12,
> the
> legacy-340xx kernel module no longer builds.
> 
> E.g.:
> 
>   # dpkg-reconfigure nvidia-legacy-340xx-kernel-dkms
> 
>   --
>   Deleting module version: 340.102
>   completely from the DKMS tree.
>   --
>   Done.
>   Loading new nvidia-legacy-340xx-340.102 DKMS files...
>   Building for 4.12.0-1-amd64
>   Building initial module for 4.12.0-1-amd64
>   Error! Bad return status for module build on kernel: 4.12.0-1-
> amd64 (x86_64)
>   Consult /var/lib/dkms/nvidia-legacy-
> 340xx/340.102/build/make.log for more information.
> 
> I've attached /var/lib/dkms/nvidia-legacy-
> 340xx/340.102/build/make.log,
> but the critical bit would appear to be this:
> 
>   /var/lib/dkms/nvidia-legacy-340xx/340.102/build/nv-linux.h: At
> top level:
>   /var/lib/dkms/nvidia-legacy-340xx/340.102/build/nv-
> linux.h:204:2: error: #error "This driver requires the ability to
> change memory types!"
>#error "This driver requires the ability to change memory
> types!"
>   ^
> 
> Which comes from an error directive in nv-linx.h:
> 
>   #if !defined(NV_VMWARE) && !defined(NVCPU_FAMILY_ARM) &&
> !defined(NVCPU_PPC64LE)
>   #if !defined(NV_SET_MEMORY_UC_PRESENT) &&
> !defined(NV_SET_PAGES_UC_PRESENT) && \
>     !defined(NV_CHANGE_PAGE_ATTR_PRESENT)
>   #error "This driver requires the ability to change memory
> types!"
>   #endif
>   #endif
> 
> Kind regards,
> 
> Tim.

Hi,

This has been fixed a while ago in SVN, and it's pending the next
upload.

Kind regards,
Luca Boccassi

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


Bug#866892: nvidia-legacy-340xx-driver: 8400 GS not functional

2017-08-17 Thread Luca Boccassi
On Thu, 2017-08-17 at 17:18 -0300, Mark Small wrote:
> I have the same problem, but my CPU is 32 bit only, so crossgrading 
> won't help
> 
> Using 9500GT.

I'm sorry but I'm afraid there's nothing we can do here, your best hope
is to open a ticket upstream with Nvidia:

https://devtalk.nvidia.com/default/topic/522835/linux/if-you-have-a-pro
blem-please-read-this-first/

Kind regards,
Luca Boccassi

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


Bug#866892: nvidia-legacy-340xx-driver: 8400 GS not functional

2017-08-17 Thread Mark Small


I have the same problem, but my CPU is 32 bit only, so crossgrading 
won't help


Using 9500GT.


Bug#602503: For Your Attention

2017-08-17 Thread Abeeku Yoofi
Hello !

My Name is Mr.Abeeku Yoofi, I am contacting you to assist me in
repatriating reasonable US$10.5 million and reasonable quantity of Gold
Dust belonging to my late client an Engineer, and I came to the conclusion
of reaching you after several unsuccessful attempts to get in touch with
supposed next of kin to my late client.

I shall be open to discuss further after receiving your favorable reply. So
kindly send  your reply with contact information.

Thanks and God bless you.
Sincerely,
Abeeku Yoofi Esq.


Bug#864848: Should not talk about hd-media - that's armhf only

2017-08-17 Thread Steve McIntyre
On Thu, Aug 17, 2017 at 09:17:22PM +0200, Holger Wansing wrote:
>On Thu, 15 Jun 2017 22:51:21 +0100
>Steve McIntyre  wrote:
>> Package: installation-guide-armel
>> Severity: normal
>> 
>> As seen in
>> 
>>   https://www.debian.org/releases/jessie/armel/ch05s01.html.en
>> 
>> there's discussion of "unpack the hd-media tarball". This doesn't
>> exist on armel...
>
>Does that mean, that armel does not support that "Boot from USB stick in
>U-Boot" thingy, described under above link?
>If that _is_ supported, that chapter needs to be rewritten (simply leaving
>out the part where the hd-media tarball is mentioned, would make the whole
>chapter senseless/important part missing).

To the best of my knowledge, we don't have any such support in the
armel port. I'd love to be corrected on this, but I don't see anything
like that in our d-i builds.

>Adding arm porters to the loop seems to make sense here.

Nod.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
You raise the blade, you make the change... You re-arrange me 'til I'm sane...



Bug#872502: curl FTBFS for powerpc: error: unknown type name 'curl_off_t'; did you mean 'loff_t'?

2017-08-17 Thread Helmut Grohne
Source: curl
Version: 7.55.0-1
Tags: patch upstream
User: helm...@debian.org
Usertags: rebootstrap

curl fails to build from source for powerpc. Its include/curl/system.h
tries to detect lots of platforms but falls short on powerpc. It
attempts to detect it by checking __ppc__, but that's not defined on
Linux. One should be checking __powerpc__ in addition. See
http://nadeausoftware.com/articles/2012/02/c_c_tip_how_detect_processor_type_using_compiler_predefined_macros
for details. The attached patch adds that macro and thus makes the build
continue. Please consider applying it.

Helmut
Index: curl-7.55.0/include/curl/system.h
===
--- curl-7.55.0.orig/include/curl/system.h
+++ curl-7.55.0/include/curl/system.h
@@ -401,7 +401,7 @@
 
 #elif defined(__GNUC__)
 #  if !defined(__LP64__) && (defined(__ILP32__) || \
-  defined(__i386__) || defined(__ppc__) || defined(__arm__) || \
+  defined(__i386__) || defined(__ppc__) || defined(__powerpc__) || defined(__arm__) || \
   defined(__sparc__) || defined(__mips__) || defined(__sh__) || \
   defined(__XTENSA__))
 #define CURL_SIZEOF_LONG   4


Bug#872501: fonts-lato: Please upgrade to newest upstream release

2017-08-17 Thread Jonas Smedegaard
Package: fonts-lato
Version: 2.0-2
Severity: wishlist
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Upstream apparently released version 2.015 two years ago.

Please package that newer release.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlmV/jcACgkQLHwxRsGg
ASHz/g/8D0DosJHIv+VhYBhMFjnMsOkRJHXtw6fj+42WL+/ibO/0s9r56LNBKVQJ
dZQpV+A46XJN0XDLMZ2IkD6F0QJ6EFdc/L5wdAQoQvubRgIAbHmE3fdeNQju32Do
UtEumLF2HgToASj5qNadCkvu2MK9LOv3vB16zMxOsv5OgRfeKLQsXnY5PMhq+UBt
Vy/apr1RNLyQ/NlNwm79qNnsLiuU3R0skpvMUVD+Uhs62UrtVzp4eYQKW9DVs8fZ
5bKpPuv91GIaeR8BexbteDvl/1x4ojDzbAevlpYQocS9qRDLw6cnsDS3tc2xKFNm
JCUMMBPagkANadiWou08zvqBqmpGiz17j2kaAeY5itVB9BlDfw8Oz1rUiVQL1cVp
b0xmOv9JFXaWvhqo0Ru8C6Zjti38SPjY47Lo1pTe1Di957gBTgdhf7p6o79R699a
rTdNytyjmhCvy+E6jkMG/SZWsQUGh2FGGSNZ1zIZywb9F4F5xeWN9O7FSja+XzLF
k72pK0Xx07NfK/sbvXcNy/5qo1lsRpeb9mUEQakADHWkTbnzSV6JVGnld2bs4eeo
y0jVVcVUZVFKH2UrzCI1/xhTMuKeuW2H5ilKlY9geWI25G9jrgNGxkt29F/+6LLd
dLz/WfKWmJkM2g2sXmzuFUbFK1Cr+ponynItWWdo+Q8CqmNtrw8=
=l2cY
-END PGP SIGNATURE-



Bug#872500: telegram-desktop: Impossible to install version 1.1.19-1 as it depends on qtbase-abi-5-7-1

2017-08-17 Thread Anton Nesterov
Package: telegram-desktop
Version: 1.1.19-1
Severity: important

qtbase-abi-5-7-1 is a virtual package provided by libqt5core5a, but
latest libqt5core5a in sid lists qtbase-abi-5-9-0 in Provides, which
makes installation of telegram-desktop impossible.

I manually replaced qtbase-abi-5-7-1 by libqt5core5a in package deps,
and was able to install Telegram that way, but it produce some visual
glitches (sometimes spaces in my messages renders as a new line), which
is probably a bug in upstream.

---
https://nesterov.pw
GPG key: 0CE8 65F1 9043 2B11 25A5 74A7 1187 6869 67AA 56E4
https://keybase.io/komachi/key.asc



Bug#872499: debian-refcard: Outdated Swedish translation

2017-08-17 Thread Andreas Ronnquist
Package: debian-refcard
Version: 10.0
Severity: normal
Tags: l10n

Dear Maintainer,

The Swedish translation of the refcard is out of date - so I have
updated the po-file, and attach it to this bug report.

Thanks for your work with the refcard.


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

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

debian-refcard depends on no packages.

Versions of packages debian-refcard recommends:
ii  atril [pdf-viewer]   1.18.0-1
ii  evince [pdf-viewer]  3.22.1-4

Versions of packages debian-refcard suggests:
pn  doc-base  

-- no debconf information


-- Andreas Rönnquist
gus...@debian.org
# Swedish translation of the Debian reference card
# Copyright (C) 2008 Free Software Foundation, Inc.
# This file is distributed under the same license as the refcard package.
# Johan Ehnberg , 2005
# Martin Bagge , 2008
# Daniel Nylander, 2008
# Andreas Rönnquist , 2016
#
msgid ""
msgstr ""
"Project-Id-Version: refcard 10.0\n"
"POT-Creation-Date: 2017-07-26 09:54+0200\n"
"PO-Revision-Date: 2017-08-17 22:19+0200\n"
"Last-Translator: Andreas Rönnquist \n"
"Language-Team: Swedish \n"
"Language: sv\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Poedit 1.8.11\n"

#. type: Attribute 'lang' of: 
#: entries.dbk:4
msgid "en-GB"
msgstr "sv"

#. type: Content of: 
#: entries.dbk:6
msgid "Debian Reference Card"
msgstr "Referenskort för Debian"

#. type: Content of: 
#: entries.dbk:9
msgid "The 101 most important things when using Debian"
msgstr "De 101 viktigaste sakerna för att använda Debian"

#. type: Content of: 
#: entries.dbk:11
msgid ""
" 2004 2010 W. Martin Borgert   2016 2017 "
"Holger Wansing   2004 "
"2010 Your Name (\"Language\") "
msgstr ""
" 2004 2010 W. Martin Borgert   2016 2017 "
"Holger Wansing   2005 "
"Johan Ehnberg (Swedish)"
"2008 Martin Bagge, Daniel Nylander (Swedish)   2016 Andreas Rönnquist "
"(Swedish) "

#. type: Content of: 
#: entries.dbk:27
msgid ""
"This document may be used under the terms of the GNU General Public License "
"version 3 or higher. The license text can be found at https://;
"www.gnu.org/copyleft/gpl.html\">https://www.gnu.org/copyleft/gpl.html and /usr/share/common-licenses/GPL-3."
msgstr ""
"Detta dokument får användas enligt de villkor som framställs i GNU General "
"Public License version 3 eller nyare. Licenstexten kan hittas på https://www.gnu.org/copyleft/gpl.html\;>https://www.gnu.org/copyleft/gpl.;
"html och /usr/share/common-licenses/GPL-3."

#. type: Content of: 
#: entries.dbk:34 entries.dbk:368
msgid "APT"
msgstr "APT"

#. type: Content of: 
#: entries.dbk:35
msgid "Debian"
msgstr "Debian"

#. type: Content of: 
#: entries.dbk:36
msgid "dpkg"
msgstr "dpkg"

#. type: Content of: 
#: entries.dbk:37
msgid "reference card"
msgstr "referenskort"

#. type: Content of: 
#: entries.dbk:38
msgid "basic commands"
msgstr "grundläggande kommandon"

#. type: Content of: 
#: entries.dbk:39
msgid "Version"
msgstr "Version"

#. type: Content of: 
#: entries.dbk:40
msgid "Made by"
msgstr "Författad av"

#. type: Content of: 
#: entries.dbk:44
msgid "Getting Help"
msgstr "Få hjälp"

#. type: Content of: 
#: entries.dbk:47
msgid "man page or man bash"
msgstr "man kommando eller man bash"

#. type: Content of: 
#: entries.dbk:49
msgid "Read online help for every command and many configuration files."
msgstr ""
"Online-hjälp och manualer för alla kommandon och många konfigurationsfiler."

#. type: Content of: 
#: entries.dbk:53
msgid ""
"command   --"
"help, -h"
msgstr ""
"kommando   "
" "
"--help, -h"

#. type: Content of: 
#: entries.dbk:56
msgid "Brief help for most commands."
msgstr "Kortfattad hjälp för de flesta kommandon."

#. type: Content of: 
#: entries.dbk:60
msgid ""
"/usr/share/doc/package-name/"
msgstr ""
"/usr/share/doc/  paketets-namn/"

#. type: Content of: 
#: entries.dbk:61
msgid ""
"Find all documentation here, optional file README.Debian contains specifics."
msgstr ""
"Hitta all dokumentation här, Debian-specifik information finns i "
"README.Debian."

#. type: Content of: 
#: entries.dbk:66
msgid "https://www.debian.org/doc/\;>Web documentation"
msgstr ""
"https://www.debian.org/doc/\;>Dokumentation på webben"

#. type: Content of: 
#: entries.dbk:68
msgid ""
"Reference, manuals, FAQs, HOWTOs, etc. at https://www.debian.org/;
"doc/"
msgstr ""
"Referens, manualer, frågor och svar, HOWTOs, etc. finns på https://;
"www.debian.org/doc/"

#. type: Content of: 
#: entries.dbk:72
msgid ""
"https://lists.debian.org/\;>Mailing 

Bug#872453: isa-support: please make the build reproducible

2017-08-17 Thread Adam Borowski
Control: tags -1 +pending

On Thu, Aug 17, 2017 at 08:26:00AM -0700, Chris Lamb wrote:
> Whilst working on the Reproducible Builds effort [0], we noticed
> that isa-support could not be built reproducibly due to using
> gzip without the "-n" flag.
> 
> Patch attached.

Thanks for the patch -- in git.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢰⠒⠀⣿⡁ James Damore is a hero.  Even mild criticism of bigots these days
⢿⡄⠘⠷⠚⠋⠀ comes at great personal risk.
⠈⠳⣄ 



Bug#870204: RFS: openfst/1.6.3-1 -- weighted finite-state transducers library

2017-08-17 Thread Adam Borowski
On Thu, Aug 17, 2017 at 08:24:59PM +0200, Giulio Paci wrote:
> Dear mentors,
>   as Jakub, my former sponsor for this package, is not available, I am 
> looking for a new sponsor.
> 
> Please note that this package also closes #871170 (FTBFS with gcc-7).

I've already test-built for a subset of architectures (arm64 43189 seconds,
armhf 27725, unjay!), then got distracted.  Sorry for that.

How are you going to handle the transition?  Have you tried rebuilding your
reverse dependencies?  If not, should I do that for you?

As you maintain all of the rdeps, you'll handle the transition as a single
block, right?


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢰⠒⠀⣿⡁ 
⢿⡄⠘⠷⠚⠋⠀ Being wise is hard, but wise-ass... ooh, this one I can deliver!
⠈⠳⣄ 



Bug#872498: imagemagick: CVE-2017-12418

2017-08-17 Thread Salvatore Bonaccorso
Source: imagemagick
Version: 8:6.9.7.4+dfsg-16
Severity: normal
Tags: patch security upstream
Forwarded: https://github.com/ImageMagick/ImageMagick/issues/643

Hi,

the following vulnerability was published for imagemagick.

CVE-2017-12418[0]:
| ImageMagick 7.0.6-5 has memory leaks in the parse8BIMW and format8BIM
| functions in coders/meta.c, related to the WriteImage function in
| MagickCore/constitute.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-12418
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12418
[1] https://github.com/ImageMagick/ImageMagick/issues/643

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore



Bug#869953: budgie-core: Adapt to gnome-settings-daemon 3.24

2017-08-17 Thread Jeremy Bicha
Control: reopen -1

On Thu, Aug 17, 2017 at 3:47 PM, Bruno Miguel
 wrote:
> I've installed Budgie in Testing and it won't login due to missing gnome-
> settings-daemon binary.

I downloaded budgie-core 10.3.1-4+b1 from
https://packages.debian.org/sid/amd64/budgie-core/download

and verified that
/usr/share/gnome-session/sessions/budgie-desktop.session contains this
line:

RequiredComponents=gnome-settings-daemon;budgie-wm;budgie-daemon;budgie-panel;budgie-polkit;

which won't work with gnome-settings-daemon 3.24. It should have the
individual gnome-settings-daemon binaries instead of
'gnome-settings-daemon' listed.

Thanks,
Jeremy Bicha



Bug#872497: vdr-plugin-games FTBFS with vdr 2.3.8

2017-08-17 Thread Adrian Bunk
Source: vdr-plugin-games
Version: 0.6.3-46
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdr-plugin-games.html

...
g++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -g -O2 
-fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -D_GNU_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -Wdate-time 
-D_FORTIFY_SOURCE=2  -c -DVERSION=\"0.6.3\" -D_GNU_SOURCE -DVDRVERSNUM=20308 -g 
-O2 -fstack-protector-strong -Wformat -Werror=format-security -g -O2 
-fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -D_GNU_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE  
-I/usr/include/vdr/include  -I/usr/include/vdr/include -c screen.cpp -o screen.o
screen.cpp: In function 'int Scr::palette(int)':
screen.cpp:90:23: error: 'cBitmap* cOsd::GetBitmap(int)' is protected within 
this context
screen->GetBitmap(0)->SetColor(i, PALETTE(i));
   ^
In file included from screen.cpp:8:0:
/usr/include/vdr/osd.h:792:12: note: declared protected here
   cBitmap *GetBitmap(int Area);
^
Makefile:95: recipe for target 'screen.o' failed
make[3]: *** [screen.o] Error 1



Bug#872496: vdr-plugin-xineliboutput FTBFS with vdr 2.3.8

2017-08-17 Thread Adrian Bunk
Source: vdr-plugin-xineliboutput
Version: 1.1.0+cvs20150907-3
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdr-plugin-xineliboutput.html

...
g++ -g -O2 -fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-c -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"xineliboutput"' -D_REENTRANT 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DVIDEODIR='"/var/lib/video"' 
-DXINELIBOUTPUT_VERSION='"2.0.0-cvs"' -Wall  -I/usr/include/gtk-3.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 
-I/usr/include/harfbuzz -I/usr/include/atk-1.0 -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -o 
xineliboutput.o xineliboutput.c
xineliboutput.c:112:1: warning: invalid suffix on literal; C++11 requires a 
space between literal and string macro [-Wliteral-suffix]
 "   (default "LISTEN_PORT_S")\n"
 ^
In file included from xineliboutput.c:35:0:
device.h:126:13: error: 'eVideoSystem' does not name a type
 virtual eVideoSystem GetVideoSystem(void);
 ^~~~
Makefile:241: recipe for target 'xineliboutput.o' failed
make[2]: *** [xineliboutput.o] Error 1



Bug#872495: vdr-plugin-remoteosd FTBFS with vdr 2.3.8

2017-08-17 Thread Adrian Bunk
Source: vdr-plugin-remoteosd
Version: 1.0.0-5
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdr-plugin-remoteosd.html

...
g++ -g -O2 -fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-c -DPLUGIN_NAME_I18N='"remoteosd"'  -o menu.o menu.c
menu.c: In member function 'bool cRemoteOsdMenu::Open(const char*, short 
unsigned int, const char*)':
menu.c:72:23: error: 'Channels' was not declared in this scope
   cChannel *channel = Channels.GetByNumber(cDevice::CurrentChannel());
   ^~~~
menu.c:72:23: note: suggested alternative: 'cChannels'
   cChannel *channel = Channels.GetByNumber(cDevice::CurrentChannel());
   ^~~~
   cChannels
Makefile:65: recipe for target 'menu.o' failed
make[1]: *** [menu.o] Error 1



Bug#872494: vdr-plugin-skinenigmang FTBFS with vdr 2.3.8

2017-08-17 Thread Adrian Bunk
Source: vdr-plugin-skinenigmang
Version: 0.1.2+git20150212-3
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdr-plugin-skinenigmang.html

...
g++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -g -O2 
-fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -D_GNU_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -c 
-D_GNU_SOURCE -DPLUGIN_NAME_I18N='"skinenigmang"' -DUSE_PLUGIN_EPGSEARCH 
-DUSE_PLUGIN_MAILBOX -DUSE_PLUGIN_AVARDS -DHAVE_IMAGEMAGICK 
-DRECORDING_COVER='"Cover-Enigma"' -I/usr/include/vdr/include -fopenmp 
-DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp 
-DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp 
-DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 
-I/usr/include/x86_64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 
-I/usr/include/x86_64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 
-I/usr/include/x86_64-linux-gnu//ImageMagick-6 -I/usr/include/ImageMagick-6 
-I/usr/include/freetype2 enigma.c
In file included from enigma.c:36:0:
services/epgsearch.h:164:12: warning: 'template class std::auto_ptr' is 
deprecated [-Wdeprecated-declarations]
   std::auto_ptr handler;
^~~~
In file included from /usr/include/c++/7/bits/locale_conv.h:41:0,
 from /usr/include/c++/7/locale:43,
 from /usr/include/c++/7/iomanip:43,
 from enigma.c:18:
/usr/include/c++/7/bits/unique_ptr.h:51:28: note: declared here
   template class auto_ptr;
^~~~
enigma.c: In member function 'void cSkinEnigmaDisplayChannel::DrawSymbols(const 
cChannel*)':
enigma.c:566:5: error: 'cSchedulesLock' was not declared in this scope
 cSchedulesLock SchedulesLock;
 ^~
enigma.c:566:5: note: suggested alternative: 'cSchedules_Lock'
 cSchedulesLock SchedulesLock;
 ^~
 cSchedules_Lock
enigma.c:567:47: error: 'Schedules' is not a member of 'cSchedules'
 const cSchedules *Schedules = cSchedules::Schedules(SchedulesLock);
   ^
enigma.c:567:57: error: 'SchedulesLock' was not declared in this scope
 const cSchedules *Schedules = cSchedules::Schedules(SchedulesLock);
 ^
enigma.c:567:57: note: suggested alternative: 'cSchedules_Lock'
 const cSchedules *Schedules = cSchedules::Schedules(SchedulesLock);
 ^
 cSchedules_Lock
enigma.c: In constructor 'cSkinEnigmaDisplayMenu::cSkinEnigmaDisplayMenu()':
enigma.c:1379:16: error: 'min' was not declared in this scope
   nMarkerGap = min(MarkerGap, lineHeight / 2 - 1); //lineHeight - 2 * MarkerGap
^~~
enigma.c:1379:16: note: suggested alternative:
In file included from /usr/include/c++/7/bits/char_traits.h:39:0,
 from /usr/include/c++/7/string:40,
 from common.h:11,
 from enigma.c:8:
/usr/include/c++/7/bits/stl_algobase.h:243:5: note:   'std::min'
 min(const _Tp& __a, const _Tp& __b, _Compare __comp)
 ^~~
enigma.c: In member function 'void cSkinEnigmaDisplayMenu::SetColors()':
enigma.c:1417:23: error: 'cBitmap* cOsd::GetBitmap(int)' is protected within 
this context
   if (osd->GetBitmap(1) == NULL) { //single area
   ^
In file included from /usr/include/vdr/skins.h:16:0,
 from config.h:22,
 from enigma.c:9:
/usr/include/vdr/osd.h:792:12: note: declared protected here
   cBitmap *GetBitmap(int Area);
^
enigma.c:1421:37: error: 'cBitmap* cOsd::GetBitmap(int)' is protected within 
this context
   cBitmap *bitmap = osd->GetBitmap(0);
 ^
In file included from /usr/include/vdr/skins.h:16:0,
 from config.h:22,
 from enigma.c:9:
/usr/include/vdr/osd.h:792:12: note: declared protected here
   cBitmap *GetBitmap(int Area);
^
enigma.c:1428:28: error: 'cBitmap* cOsd::GetBitmap(int)' is protected within 
this context
   bitmap = osd->GetBitmap(1);
^
In file included from /usr/include/vdr/skins.h:16:0,
 from config.h:22,
 from enigma.c:9:
/usr/include/vdr/osd.h:792:12: note: declared protected here
   cBitmap *GetBitmap(int Area);
^
enigma.c:1437:28: error: 'cBitmap* cOsd::GetBitmap(int)' is protected within 
this context
   bitmap = osd->GetBitmap(2);
^
In file included from /usr/include/vdr/skins.h:16:0,
 from config.h:22,
 from enigma.c:9:
/usr/include/vdr/osd.h:792:12: note: declared protected here
   cBitmap *GetBitmap(int Area);

Bug#872493: vdr-plugin-sudoku FTBFS with vdr 2.3.8

2017-08-17 Thread Adrian Bunk
Source: vdr-plugin-sudoku
Version: 0.3.5-20
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdr-plugin-sudoku.html

...
g++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -g -O2 
-fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -D_GNU_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -Wl,-z,relro 
-I/usr/include/vdr/include -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"sudoku"' 
-Wdate-time -D_FORTIFY_SOURCE=2  -c -o bitmap.o bitmap.cpp
bitmap.cpp: In member function 'void SudokuPlugin::Bitmap::text(const char*, 
bool)':
bitmap.cpp:54:11: error: 'max' was not declared in this scope
   int y = max((Height() - wrapper.Lines() * font->Height()) / 2, 0);
   ^~~
bitmap.cpp:54:11: note: suggested alternative:
In file included from /usr/include/c++/7/vector:60:0,
 from sudoku.h:29,
 from bitmap.h:24,
 from bitmap.cpp:21:
/usr/include/c++/7/bits/stl_algobase.h:265:5: note:   'std::max'
 max(const _Tp& __a, const _Tp& __b, _Compare __comp)
 ^~~
: recipe for target 'bitmap.o' failed
make[2]: *** [bitmap.o] Error 1



Bug#872491: vdr-plugin-streamdev FTBFS with vdr 2.3.8

2017-08-17 Thread Adrian Bunk
Source: vdr-plugin-streamdev
Version: 0.6.1+git20150213-3
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdr-plugin-streamdev.html

...
g++ -g -O2 -fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-c -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"streamdev-client"' -I/include -I.. -o 
filter.o filter.c
filter.c: In member function 'int cStreamdevFilters::OpenFilter(u_short, 
u_char, u_char)':
filter.c:222:2: error: reference to 'Lock' is ambiguous
  Lock();
  ^~~~
In file included from /usr/include/vdr/tools.h:29:0,
 from /usr/include/vdr/i18n.h:14,
 from /usr/include/vdr/config.h:19,
 from ../client/filter.h:8,
 from filter.c:5:
/usr/include/vdr/thread.h:94:8: note: candidates are: void cThread::Lock()
   void Lock(void) { mutex.Lock(); }
^~~~
In file included from /usr/include/vdr/i18n.h:14:0,
 from /usr/include/vdr/config.h:19,
 from ../client/filter.h:8,
 from filter.c:5:
/usr/include/vdr/tools.h:531:8: note: bool 
cListBase::Lock(cStateKey&, bool, int) const
   bool Lock(cStateKey , bool Write = false, int TimeoutMs = 0) const;
^~~~
Makefile:34: recipe for target 'filter.o' failed
make[2]: *** [filter.o] Error 1



Bug#872492: vdr-plugin-spider FTBFS with vdr 2.3.8

2017-08-17 Thread Adrian Bunk
Source: vdr-plugin-spider
Version: 0.2.2-21
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdr-plugin-spider.html

...
g++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -g -O2 
-fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -D_GNU_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -Wl,-z,relro 
-I/usr/include/vdr/include -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"spider"' 
-Wdate-time -D_FORTIFY_SOURCE=2  -c -o bitmap.o bitmap.cpp
bitmap.cpp: In member function 'void SpiderPlugin::Bitmap::text(const char*, 
bool)':
bitmap.cpp:77:11: error: 'max' was not declared in this scope
   int y = max((Height() - wrapper.Lines() * font->Height()) / 2, 0);
   ^~~
bitmap.cpp:77:11: note: suggested alternative:
In file included from /usr/include/c++/7/vector:60:0,
 from spider.h:30,
 from bitmap.h:26,
 from bitmap.cpp:23:
/usr/include/c++/7/bits/stl_algobase.h:265:5: note:   'std::max'
 max(const _Tp& __a, const _Tp& __b, _Compare __comp)
 ^~~
bitmap.cpp: In constructor 'SpiderPlugin::Bitmap::Bitmap(int, int, const char*, 
const char*)':
bitmap.cpp:54:11: warning: ignoring return value of 'int asprintf(char**, const 
char*, ...)', declared with attribute warn_unused_result [-Wunused-result]
   asprintf(, "%s/%s.xpm", dir, name);
   ^~~
bitmap.cpp: In constructor 'SpiderPlugin::Bitmap::Bitmap(int, int, const char*, 
const char*, const char*)':
bitmap.cpp:65:11: warning: ignoring return value of 'int asprintf(char**, const 
char*, ...)', declared with attribute warn_unused_result [-Wunused-result]
   asprintf(, "%s/%s_%s.xpm", dir, suit, rank);
   ^~~~
: recipe for target 'bitmap.o' failed
make[2]: *** [bitmap.o] Error 1



Bug#872490: vdr-plugin-osdteletext FTBFS with vdr 2.3.8

2017-08-17 Thread Adrian Bunk
Source: vdr-plugin-osdteletext
Version: 0.9.5-3
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdr-plugin-osdteletext.html

...
g++ -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -D_GNU_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -c 
-DPLUGIN_NAME_I18N='"osdteletext"'  -o menu.o menu.c
In file included from display.h:19:0,
 from menu.c:18:
displaybase.h: In member function 'int 
cDisplay::GetColorIndex(enumTeletextColor, int)':
displaybase.h:145:40: error: 'cBitmap* cOsd::GetBitmap(int)' is protected 
within this context
 cBitmap *bm=osd->GetBitmap(Area);
^
In file included from /usr/include/vdr/skins.h:16:0,
 from /usr/include/vdr/interface.h:15,
 from menu.c:14:
/usr/include/vdr/osd.h:792:12: note: declared protected here
   cBitmap *GetBitmap(int Area);
^
In file included from display.h:19:0,
 from menu.c:18:
displaybase.h: In member function 'int 
cDisplay::GetColorIndexAlternate(enumTeletextColor, int)':
displaybase.h:153:40: error: 'cBitmap* cOsd::GetBitmap(int)' is protected 
within this context
 cBitmap *bm=osd->GetBitmap(Area);
^
In file included from /usr/include/vdr/skins.h:16:0,
 from /usr/include/vdr/interface.h:15,
 from menu.c:14:
/usr/include/vdr/osd.h:792:12: note: declared protected here
   cBitmap *GetBitmap(int Area);
^
menu.c: In member function 'bool TeletextBrowser::CheckIsValidChannel(int)':
menu.c:76:12: error: 'Channels' was not declared in this scope
return (Channels.GetByNumber(number) != 0);
^~~~
menu.c:76:12: note: suggested alternative: 'cChannels'
return (Channels.GetByNumber(number) != 0);
^~~~
cChannels
menu.c: In static member function 'static void 
TeletextBrowser::ChannelSwitched(int)':
menu.c:80:19: error: 'Channels' was not declared in this scope
cChannel *chan=Channels.GetByNumber(ChannelNumber);
   ^~~~
menu.c:80:19: note: suggested alternative: 'cChannels'
cChannel *chan=Channels.GetByNumber(ChannelNumber);
   ^~~~
   cChannels
Makefile:64: recipe for target 'menu.o' failed
make[1]: *** [menu.o] Error 1



Bug#872488: nodejs: Build-Dependency loop nodejs => node-yamlish, node-marked => nodejs

2017-08-17 Thread Felipe Sateler
Source: nodejs
Version: 6.11.2~dfsg-2
Severity: important
Tags: patch

Hi,

Currently nodejs has a dependency loop which causes problems when
building on buildds when the previous nodejs version is not installable
for some reason. Fortunately, the node dependencies appear to only be
used for building documentation. Therefore the loop can be broken by
splitting the documentation into an Architecture: all package: this will
make buildds not require installing nodejs to build nodejs.

Please find a patch attached doing this. Patch is against -1 because -2
was not in git...

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

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

-- no debconf information
From 421b536f2e076e35ae75674112d0ca28142d9a6a Mon Sep 17 00:00:00 2001
From: Felipe Sateler 
Date: Thu, 17 Aug 2017 16:53:58 -0300
Subject: [PATCH] Split documentation into a separate, arch:all package

This avoids the dependency loop on the buildds, since they will now no longer 
require
nodejs to be available.
---
 debian/control.in   | 27 -
 debian/{nodejs.doc-base => nodejs-doc.doc-base} |  0
 debian/{nodejs.docs => nodejs-doc.docs} |  0
 debian/rules| 16 ++-
 4 files changed, 28 insertions(+), 15 deletions(-)
 rename debian/{nodejs.doc-base => nodejs-doc.doc-base} (100%)
 rename debian/{nodejs.docs => nodejs-doc.docs} (100%)

diff --git a/debian/control.in b/debian/control.in
index 949b7685..30f03285 100644
--- a/debian/control.in
+++ b/debian/control.in
@@ -5,6 +5,8 @@ Maintainer: Debian Javascript Maintainers 
,
  Jonas Smedegaard 
 Build-Depends: @cdbs@
+Build-Depends-Indep: node-yamlish,
+ node-marked
 Standards-Version: 4.0.0
 Homepage: http://nodejs.org/
 Vcs-Browser: https://anonscm.debian.org/gitweb/?p=collab-maint/nodejs.git
@@ -33,7 +35,8 @@ Architecture: any
 Depends: ${shlibs:Depends},
  ${misc:Depends}
 Provides: ${cdbs:Provides}
-Recommends: ${cdbs:Recommends}
+Recommends: ${cdbs:Recommends},
+ nodejs-doc
 Replaces: nodejs-legacy
 Conflicts: nodejs-legacy
 Description: evented I/O for V8 javascript
@@ -49,3 +52,25 @@ Description: evented I/O for V8 javascript
  System, Events, Standard I/O, Modules, Timers, Child Processes, POSIX,
  HTTP, Multipart Parsing, TCP, DNS, Assert, Path, URL, Query Strings.
 
+Package: nodejs-doc
+Architecture: all
+Depends: ${misc:Depends}
+Provides: ${cdbs:Provides}
+Recommends: ${cdbs:Recommends}, nodejs
+Replaces: nodejs (<< 6.11.2~dfsg-3)
+Conflicts: nodejs (<< 6.11.2~dfsg-3)
+Description: evented I/O for V8 javascript
+ Node.js is a platform built on Chrome's JavaScript runtime for easily
+ building fast, scalable network applications. Node.js uses an
+ event-driven, non-blocking I/O model that makes it lightweight and
+ efficient, perfect for data-intensive real-time applications that run
+ across distributed devices.
+ .
+ Node.js is bundled with several useful libraries to handle server
+ tasks:
+ .
+ System, Events, Standard I/O, Modules, Timers, Child Processes, POSIX,
+ HTTP, Multipart Parsing, TCP, DNS, Assert, Path, URL, Query Strings.
+ .
+ This package contains documentation for nodejs.
+
diff --git a/debian/nodejs.doc-base b/debian/nodejs-doc.doc-base
similarity index 100%
rename from debian/nodejs.doc-base
rename to debian/nodejs-doc.doc-base
diff --git a/debian/nodejs.docs b/debian/nodejs-doc.docs
similarity index 100%
rename from debian/nodejs.docs
rename to debian/nodejs-doc.docs
diff --git a/debian/rules b/debian/rules
index 3e7a938a..5320069f 100755
--- a/debian/rules
+++ b/debian/rules
@@ -24,10 +24,6 @@ bdeps +=, bash-completion, curl, procps, zlib1g-dev, 
libicu-dev, libc-ares-dev (
 bdeps +=, libkvm-dev [kfreebsd-any], gyp (>= 0.1~svn1773)
 # Needed for tests
 bdeps +=, ca-certificates
-# needed by doctool-yaml.patch
-bdeps +=, node-yamlish 
-# needed by doc builder
-bdeps +=, node-marked 
 
 # Needed by upstream build and binary development package
 deps = python, libssl1.0-dev (>= $(ssl-minver))
@@ -160,24 +156,16 @@ clean::
find . -name "*.pyc" -delete
rm -rf out
 
-ifeq ($(filter stage1,$(DEB_BUILD_PROFILES)),)
 # remove *.json files from documentation
-binary-install/nodejs::
+binary-install/nodejs-doc::
find debian/nodejs/usr/share/doc/nodejs -name *.json -delete
-endif
 
 pre-build::
ln -sTf /usr/lib/nodejs node_modules
mkdir -p $(NODE_TEST_DIR)
 
-ifeq ($(filter stage1,$(DEB_BUILD_PROFILES)),)
-build/nodejs::
+build/nodejs-doc::
make doc
-else
-# Stops the stage1 variant from breaking 

Bug#872489: vdr-plugin-femon FTBFS with vdr 2.3.8

2017-08-17 Thread Adrian Bunk
Source: vdr-plugin-femon
Version: 2.2.1-1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdr-plugin-femon.html

...
g++ -g -O2 -fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-c -DPLUGIN_NAME_I18N='"femon"'  -o femon.o femon.c
femon.c: In member function 'virtual cOsdObject* 
cPluginFemon::MainMenuAction()':
femon.c:123:31: error: 'Channels' was not declared in this scope
   if (cControl::Control() || (Channels.Count() <= 0))
   ^~~~
femon.c:123:31: note: suggested alternative: 'kChannels'
   if (cControl::Control() || (Channels.Count() <= 0))
   ^~~~
   kChannels
Makefile:73: recipe for target 'femon.o' failed
make[1]: *** [femon.o] Error 1



Bug#872487: vdr-plugin-infosatepg FTBFS with vdr 2.3.8

2017-08-17 Thread Adrian Bunk
Source: vdr-plugin-infosatepg
Version: 0.0.12-6
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdr-plugin-infosatepg.html

...
g++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -g -O2 
-fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -D_GNU_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -c 
-D_GNU_SOURCE -DPLUGIN_NAME_I18N='"infosatepg"' -I/usr/include/vdr/include 
infosatepg.cpp
infosatepg.cpp: In member function 'virtual bool 
cPluginInfosatepg::Initialize()':
infosatepg.cpp:97:14: error: 'Channels' was not declared in this scope
 if (!Channels.GetByChannelID(ChannelID))
  ^~~~
infosatepg.cpp:97:14: note: suggested alternative: 'kChannels'
 if (!Channels.GetByChannelID(ChannelID))
  ^~~~
  kChannels
infosatepg.cpp: In member function 'virtual void 
cPluginInfosatepg::MainThreadHook()':
infosatepg.cpp:167:20: error: 'Channels' was not declared in this scope
 cChannel *chan=Channels.GetByNumber(global->Channel());
^~~~
infosatepg.cpp:167:20: note: suggested alternative: 'kChannels'
 cChannel *chan=Channels.GetByNumber(global->Channel());
^~~~
kChannels
infosatepg.cpp: In member function 'virtual cString 
cPluginInfosatepg::Active()':
infosatepg.cpp:238:28: error: 'Channels' was not declared in this scope
 cChannel *chan=Channels.GetByNumber(global->LastCurrentChannel);
^~~~
infosatepg.cpp:238:28: note: suggested alternative: 'kChannels'
 cChannel *chan=Channels.GetByNumber(global->LastCurrentChannel);
^~~~
kChannels
Makefile:59: recipe for target 'infosatepg.o' failed
make[2]: *** [infosatepg.o] Error 1



Bug#872486: vdr-plugin-epgsync FTBFS with vdr 2.3.8

2017-08-17 Thread Adrian Bunk
Source: vdr-plugin-epgsync
Version: 1.0.1-2
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdr-plugin-epgsync.html

...
g++ -g -O2 -fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-c -DPLUGIN_NAME_I18N='"epgsync"'  -o thread.o thread.c
thread.c: In function 'cChannel* GetChannelByName(const char*, const cChannel*, 
eChannelTypes)':
thread.c:47:27: error: 'Channels' was not declared in this scope
  for (cChannel *channel = Channels.First(); channel; channel = 
Channels.Next(channel)) {
   ^~~~
thread.c:47:27: note: suggested alternative: 'kChannels'
  for (cChannel *channel = Channels.First(); channel; channel = 
Channels.Next(channel)) {
   ^~~~
   kChannels
thread.c: In member function 'virtual void cEpgSyncThread::Action()':
thread.c:98:4: error: 'cSchedulesLock' was not declared in this scope
cSchedulesLock *lock = NULL;
^~
thread.c:98:4: note: suggested alternative: 'cSchedules_Lock'
cSchedulesLock *lock = NULL;
^~
cSchedules_Lock
thread.c:98:20: error: 'lock' was not declared in this scope
cSchedulesLock *lock = NULL;
^~~~
thread.c:98:20: note: suggested alternative: 'Lock'
cSchedulesLock *lock = NULL;
^~~~
Lock
thread.c:99:29: error: 'Channels' was not declared in this scope
for (cChannel *channel = Channels.First(); channel && Running();
 ^~~~
thread.c:99:29: note: suggested alternative: 'kChannels'
for (cChannel *channel = Channels.First(); channel && Running();
 ^~~~
 kChannels
thread.c:102:17: error: expected type-specifier before 'cSchedulesLock'
  lock = new cSchedulesLock();
 ^~
thread.c:103:21: error: 'Schedules' is not a member of 'cSchedules'
 if (cSchedules::Schedules(*lock)->GetSchedule(channel)) {
 ^
thread.c: In member function 'bool cEpgSyncThread::CmdLSTE(FILE*, const char*)':
thread.c:185:18: error: 'Channels' was not declared in this scope
cChannel *c = Channels.GetByChannelID(tChannelID::FromString(p));
  ^~~~
thread.c:185:18: note: suggested alternative: 'kChannels'
cChannel *c = Channels.GetByChannelID(tChannelID::FromString(p));
  ^~~~
  kChannels
Makefile:65: recipe for target 'thread.o' failed
make[1]: *** [thread.o] Error 1



Bug#869953: budgie-core: Adapt to gnome-settings-daemon 3.24

2017-08-17 Thread David
How did you install? - the correct package is budgie-desktop - 
https://packages.debian.org/buster/budgie-desktop


as you can see gnome-settings-daemon is a dependency

run

sudo apt update
sudo apt install --reinstall budgie-desktop gnome-settings-daemon

On Thu, 17 Aug, 2017 at 8:47 PM, Bruno Miguel 
 wrote:

Package: budgie-core
Version: 10.3.1-4+b1
Followup-For: Bug #869953

I've installed Budgie in Testing and it won't login due to missing 
gnome-

settings-daemon binary.

Log:

ago 17 20:35:30 carlsagan dbus-daemon[2485]: Activating via systemd: 
service

name='org.a11y.Bus' unit='at-spi-dbus-bus.service'
ago 17 20:35:30 carlsagan systemd[2464]: Starting Accessibility 
services bus...
ago 17 20:35:30 carlsagan dbus-daemon[2485]: Successfully activated 
service

'org.a11y.Bus'
ago 17 20:35:30 carlsagan systemd[2464]: Started Accessibility 
services bus.
ago 17 20:35:30 carlsagan at-spi-bus-launcher[2553]: Activating 
service

name='org.a11y.atspi.Registry'
ago 17 20:35:30 carlsagan at-spi-bus-launcher[2553]: Successfully 
activated

service 'org.a11y.atspi.Registry'
ago 17 20:35:30 carlsagan org.a11y.atspi.Registry[2558]: SpiRegistry 
daemon is

running with well-known name - org.a11y.atspi.Registry
ago 17 20:35:30 carlsagan gnome-session[2487]: 
gnome-session-binary[2487]:

WARNING: Unable to find required component 'gnome-settings-daemon'
==> ago 17 20:35:30 carlsagan gnome-session-binary[2487]: WARNING: 
Unable to

find required component 'gnome-settings-daemon'
ago 17 20:35:30 carlsagan gnome-session-binary[2487]: Entering 
running state
==> ago 17 20:35:30 carlsagan gnome-session[2487]: Unable to init 
server: Could

not connect: Connection refused
==> ago 17 20:35:30 carlsagan gnome-session-f[2568]: Cannot open 
display:
ago 17 20:35:30 carlsagan gnome-session[2487]: 
gnome-session-binary[2487]:
GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT 
(object)' failed
ago 17 20:35:30 carlsagan gnome-session-binary[2487]: 
GLib-GObject-CRITICAL:

g_object_unref: assertion 'G_IS_OBJECT (object)' failed
ago 17 20:35:30 carlsagan gnome-session[2487]: 
gnome-session-binary[2487]:
GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT 
(object)' failed
ago 17 20:35:30 carlsagan gnome-session-binary[2487]: 
GLib-GObject-CRITICAL:

g_object_unref: assertion 'G_IS_OBJECT (object)' failed
ago 17 20:35:30 carlsagan gnome-session-binary[2487]: 
GLib-GObject-CRITICAL:

g_object_unref: assertion 'G_IS_OBJECT (object)' failed



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

Kernel: Linux 4.12.8-xanmod9 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=pt_PT.UTF-8, LC_CTYPE=pt_PT.UTF-8 (charmap=UTF-8), 
LANGUAGE=pt_PT.UTF-8 (charmap=UTF-8)

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

Versions of packages budgie-core depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2+b1
ii  libbudgie-plugin010.3.1-4+b1
ii  libbudgietheme0  10.3.1-4+b1
ii  libc62.24-12
ii  libcairo21.14.10-1
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libgirepository-1.0-11.50.0-2
ii  libglib2.0-0 2.53.4-3
ii  libgnome-bluetooth13 3.20.1-1
ii  libgnome-desktop-3-123.22.2-1
ii  libgnome-menu-3-03.13.3-9
ii  libgtk-3-0   3.22.18-1
ii  libibus-1.0-51.5.14-3
ii  libmutter0i  3.22.4-2
ii  libpeas-1.0-01.20.0-1+b1
ii  libpolkit-agent-1-0  0.105-18
ii  libpolkit-gobject-1-00.105-18
ii  libpulse-mainloop-glib0  10.0-2
ii  libpulse010.0-2
ii  libraven010.3.1-4+b1
ii  libupower-glib3  0.99.5-3
ii  libuuid1 2.29.2-2
ii  libwnck-3-0  3.24.0-1
ii  libx11-6 2:1.6.4-3

budgie-core recommends no packages.

budgie-core suggests no packages.

-- no debconf information


Bug#844431: Packages should be reproducible

2017-08-17 Thread Georg Faerber
On 17-08-17 14:38:38, Edroman wrote:
> Regarding to reproducible, I would suggest Debian should consider
> integrating Nix[0] into Debian; as Nix's website mentions
> 
> Nix builds packages in isolation from each other. This ensures that
> they are reproducible and don’t have undeclared dependencies, so if a
> package works on one machine, it will also work on another.

I doubt that building packages in isolation from each other makes
them reproducible, especially in the context which is discussed in this
bug.

Cheers,
Georg


signature.asc
Description: Digital signature


Bug#872485: vdr-plugin-epgsearch FTBFS with vdr 2.3.8

2017-08-17 Thread Adrian Bunk
Source: vdr-plugin-epgsearch
Version: 1.0.1~beta6+git20150211-4
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdr-plugin-epgsearch.html

...
g++ -g -O2 -fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-c  -DSENDMAIL='"/usr/sbin/sendmail"' -DPLUGIN_NAME_I18N='"epgsearch"'  -o 
blacklist.o blacklist.c
blacklist.c: In constructor 'cBlacklist::cBlacklist()':
blacklist.c:50:18: error: 'Channels' was not declared in this scope
 channelMin = Channels.GetByNumber(cDevice::CurrentChannel());
  ^~~~
blacklist.c:50:18: note: suggested alternative: 'kChannels'
 channelMin = Channels.GetByNumber(cDevice::CurrentChannel());
  ^~~~
  kChannels
blacklist.c: In member function 'bool cBlacklist::Parse(const char*)':
blacklist.c:334:17: error: 'Channels' was not declared in this scope
channelMin = 
Channels.GetByChannelID(tChannelID::FromString(channelMinbuffer), true, true);
 ^~~~
blacklist.c:334:17: note: suggested alternative: 'kChannels'
channelMin = 
Channels.GetByChannelID(tChannelID::FromString(channelMinbuffer), true, true);
 ^~~~
 kChannels
blacklist.c: In member function 'cEvent* cBlacklist::GetEventByBlacklist(const 
cSchedule*, const cEvent*, int)':
blacklist.c:521:37: error: invalid conversion from 'const cEvent*' to 'cEvent*' 
[-fpermissive]
   p1 = schedules->Events()->Next(Start);
~^~~
blacklist.c:523:38: error: invalid conversion from 'const cEvent*' to 'cEvent*' 
[-fpermissive]
   p1 = schedules->Events()->First();
~~^~
blacklist.c:548:56: error: invalid conversion from 'const cEvent*' to 'cEvent*' 
[-fpermissive]
   for (cEvent *p = p1; p; p = schedules->Events()->Next(p))
   ~^~~
blacklist.c: In member function 'cSearchResults* 
cBlacklist::Run(cSearchResults*, int)':
blacklist.c:636:5: error: 'cSchedulesLock' was not declared in this scope
 cSchedulesLock schedulesLock;
 ^~
blacklist.c:636:5: note: suggested alternative: 'cSchedules_Lock'
 cSchedulesLock schedulesLock;
 ^~
 cSchedules_Lock
blacklist.c:638:29: error: 'Schedules' is not a member of 'cSchedules'
 schedules = cSchedules::Schedules(schedulesLock);
 ^
blacklist.c:638:39: error: 'schedulesLock' was not declared in this scope
 schedules = cSchedules::Schedules(schedulesLock);
   ^
blacklist.c:638:39: note: suggested alternative: 'cSchedules_Lock'
 schedules = cSchedules::Schedules(schedulesLock);
   ^
   cSchedules_Lock
blacklist.c:647:22: error: 'Channels' was not declared in this scope
  cChannel* channel = Channels.GetByChannelID(Schedule->ChannelID(),true,true);
  ^~~~
blacklist.c:647:22: note: suggested alternative: 'kChannels'
  cChannel* channel = Channels.GetByChannelID(Schedule->ChannelID(),true,true);
  ^~~~
  kChannels
blacklist.c: In member function 'int cBlacklists::GetNewID()':
blacklist.c:740:10: error: 'max' was not declared in this scope
  newID = max(newID, l->ID);
  ^~~
blacklist.c:740:10: note: suggested alternative:
In file included from /usr/include/c++/7/vector:60:0,
 from blacklist.c:24:
/usr/include/c++/7/bits/stl_algobase.h:265:5: note:   'std::max'
 max(const _Tp& __a, const _Tp& __b, _Compare __comp)
 ^~~
Makefile:193: recipe for target 'blacklist.o' failed
make[1]: *** [blacklist.o] Error 1



Bug#872393: sphinx: autopkgtest failure on armhf with webkit2gtk 2.17.90

2017-08-17 Thread Jeremy Bicha
Control: forwarded -1 https://bugs.webkit.org/show_bug.cgi?id=175681

On Thu, Aug 17, 2017 at 3:45 PM, Dmitry Shachnev  wrote:
> This looks like a regression in WebKit to me. Maybe you can report it
> upstream and then we disable the test on armhf as a temporary workaround?

Thanks. I filed the upstream bug (above) ^

I can ask the Ubuntu Release Team to temporarily ignore the armhf
failure instead of doing an upload just for that. But I expect 2.17.91
will be released next week so I think I'll wait for that first.

Thanks,
Jeremy Bicha



Bug#872438: [Pkg-javascript-devel] Bug#872438: src:nodejs: FTBFS on mips64el: Can't determine the arch of ./node

2017-08-17 Thread Bastien ROUCARIES
On Thu, Aug 17, 2017 at 3:54 PM, Felipe Sateler  wrote:
> Package: src:nodejs
> Version: 6.11.2~dfsg-2
> Severity: serious
>
> nodejs failed to build with this error:
>
> make[1]: Entering directory '/<>'
> # Clean up any leftover processes but don't error if found.
> ps awwx | grep Release/node | grep -v grep | cat
> /usr/bin/python tools/test.py  -p tap \
> --mode=release --flaky-tests=dontcare \
> --arch=mips64el --timeout=3000 message parallel sequential
> Can't determine the arch of: './node'
>
> Can't determine the arch of: './node'
>
> Can't determine the arch of: './node'

The line are :

vm = context.GetVm(arch, mode)
if not exists(vm):
  print "Can't find shell executable: '%s'" % vm
  continue
archEngineContext = Execute([vm, "-p", "process.arch"], context)
vmArch = archEngineContext.stdout.rstrip()
if archEngineContext.exit_code is not 0 or vmArch == "undefined":
  print "Can't determine the arch of: '%s'" % vm
  print archEngineContext.stderr.rstrip()
  continue
env = {
  'mode': mode,
  'system': utils.GuessOS(),
  'arch': vmArch,
}


>
> No tests to run.
> Makefile:220: recipe for target 'test-ci-js' failed
> make[1]: *** [test-ci-js] Error 1
> make[1]: Leaving directory '/<>'
>
>
> Full log at 
> https://buildd.debian.org/status/fetch.php?pkg=nodejs=mips64el=6.11.2~dfsg-2=1502862893=0
>
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.9.0-3-amd64 (SMP w/2 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
>
> --
> Pkg-javascript-devel mailing list
> pkg-javascript-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel



Bug#872473: [Pkg-javascript-devel] Bug#872473: node-xmpp outdated

2017-08-17 Thread Jonas Smedegaard
Quoting Thorsten Alteholz (2017-08-17 19:58:24)
> The Homepage:[1] leads to an almost empty page. 
> The github repository URL[2] in debian/copyright is redirected to a 
> different project[3], where the README says:
>"xmpp.js is a rewrite of node-xmpp"
> Further, at least for me it was not possible to connect with the example
> send_message.js to a jabberd2 with legacy ssl.
> 
> Maybe it is time to remove this package and switch to xmpp.js?

Yes. Please kill it.

Thanks for the investigation.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature


Bug#872484: mgba: team maintained packages must be maintained in a VCS

2017-08-17 Thread Markus Koschany
Source: mgba
Version: 0.5.2+dfsg1-3
Severity: normal

Hi,

team maintained packages should be maintained in a version control
system like Git. This allows other team members to work on a package
too and all changes can be reviewed easily.

Regards,

Markus



Bug#869953: budgie-core: Adapt to gnome-settings-daemon 3.24

2017-08-17 Thread Bruno Miguel
Package: budgie-core
Version: 10.3.1-4+b1
Followup-For: Bug #869953

I've installed Budgie in Testing and it won't login due to missing gnome-
settings-daemon binary.

Log:

ago 17 20:35:30 carlsagan dbus-daemon[2485]: Activating via systemd: service
name='org.a11y.Bus' unit='at-spi-dbus-bus.service'
ago 17 20:35:30 carlsagan systemd[2464]: Starting Accessibility services bus...
ago 17 20:35:30 carlsagan dbus-daemon[2485]: Successfully activated service
'org.a11y.Bus'
ago 17 20:35:30 carlsagan systemd[2464]: Started Accessibility services bus.
ago 17 20:35:30 carlsagan at-spi-bus-launcher[2553]: Activating service
name='org.a11y.atspi.Registry'
ago 17 20:35:30 carlsagan at-spi-bus-launcher[2553]: Successfully activated
service 'org.a11y.atspi.Registry'
ago 17 20:35:30 carlsagan org.a11y.atspi.Registry[2558]: SpiRegistry daemon is
running with well-known name - org.a11y.atspi.Registry
ago 17 20:35:30 carlsagan gnome-session[2487]: gnome-session-binary[2487]:
WARNING: Unable to find required component 'gnome-settings-daemon'
==> ago 17 20:35:30 carlsagan gnome-session-binary[2487]: WARNING: Unable to
find required component 'gnome-settings-daemon'
ago 17 20:35:30 carlsagan gnome-session-binary[2487]: Entering running state
==> ago 17 20:35:30 carlsagan gnome-session[2487]: Unable to init server: Could
not connect: Connection refused
==> ago 17 20:35:30 carlsagan gnome-session-f[2568]: Cannot open display:
ago 17 20:35:30 carlsagan gnome-session[2487]: gnome-session-binary[2487]:
GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
ago 17 20:35:30 carlsagan gnome-session-binary[2487]: GLib-GObject-CRITICAL:
g_object_unref: assertion 'G_IS_OBJECT (object)' failed
ago 17 20:35:30 carlsagan gnome-session[2487]: gnome-session-binary[2487]:
GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
ago 17 20:35:30 carlsagan gnome-session-binary[2487]: GLib-GObject-CRITICAL:
g_object_unref: assertion 'G_IS_OBJECT (object)' failed
ago 17 20:35:30 carlsagan gnome-session-binary[2487]: GLib-GObject-CRITICAL:
g_object_unref: assertion 'G_IS_OBJECT (object)' failed



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

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

Versions of packages budgie-core depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2+b1
ii  libbudgie-plugin010.3.1-4+b1
ii  libbudgietheme0  10.3.1-4+b1
ii  libc62.24-12
ii  libcairo21.14.10-1
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libgirepository-1.0-11.50.0-2
ii  libglib2.0-0 2.53.4-3
ii  libgnome-bluetooth13 3.20.1-1
ii  libgnome-desktop-3-123.22.2-1
ii  libgnome-menu-3-03.13.3-9
ii  libgtk-3-0   3.22.18-1
ii  libibus-1.0-51.5.14-3
ii  libmutter0i  3.22.4-2
ii  libpeas-1.0-01.20.0-1+b1
ii  libpolkit-agent-1-0  0.105-18
ii  libpolkit-gobject-1-00.105-18
ii  libpulse-mainloop-glib0  10.0-2
ii  libpulse010.0-2
ii  libraven010.3.1-4+b1
ii  libupower-glib3  0.99.5-3
ii  libuuid1 2.29.2-2
ii  libwnck-3-0  3.24.0-1
ii  libx11-6 2:1.6.4-3

budgie-core recommends no packages.

budgie-core suggests no packages.

-- no debconf information



Bug#872393: sphinx: autopkgtest failure on armhf with webkit2gtk 2.17.90

2017-08-17 Thread Dmitry Shachnev
Hi Jeremy!

On Wed, Aug 16, 2017 at 10:50:13PM -0400, Jeremy Bicha wrote:
> Source: sphinx
> Version: 1.5.6-2
>
> Hi, webkit2gtk 2.17.90 (2.18 Beta 1) is no migrating out of
> artful-proposed because the sphinx-doc autopkgtest is failing on
> armhf.
>
> http://autopkgtest.ubuntu.com/packages/s/sphinx/artful/armhf
>
> Could you look into this?

I am attaching two stacktraces: one for when the actual crash happens,
and another one for the first call of g_log() in the main process, which
happens just before the crash. I could not figure out how to break on
warnings in WebKitWebProcess.

This looks like a regression in WebKit to me. Maybe you can report it
upstream and then we disable the test on armhf as a temporary workaround?

--
Dmitry Shachnev
#0  g_utf8_validate (str=str@entry=0xe , max_len=max_len@entry=-1, end=end@entry=0x0)
at ../../../../glib/gutf8.c:1670
#1  0xf6c3a44c in g_variant_new_string (string=0xe ) at ../../../../glib/gvariant.c:1257
#2  0xf6c3d134 in g_variant_valist_new_nnp (str=0xfffee574, ptr=0xe) at 
../../../../glib/gvariant.c:4770
#3  0xf6c3dffe in g_variant_valist_new_leaf (app=0xfffee588, str=0xfffee574) at 
../../../../glib/gvariant.c:4962
#4  g_variant_valist_new (str=str@entry=0xfffee574, app=app@entry=0xfffee588) 
at ../../../../glib/gvariant.c:5144
#5  0xf6c3df4e in g_variant_valist_new (str=str@entry=0xfffee574, 
app=app@entry=0xfffee588) at ../../../../glib/gvariant.c:5196
#6  0xf6c3e15a in g_variant_new_va (format_string=, endptr=0x0, 
app=0xfffee588) at ../../../../glib/gvariant.c:5372
#7  0xf6c3e1e6 in g_variant_new (format_string=0xf5cc "(tsssb)") at 
../../../../glib/gvariant.c:5307
#8  0xf3278e70 in Inspector::RemoteInspector::listingForInspectionTarget ()
at ./Source/JavaScriptCore/inspector/remote/glib/RemoteInspectorGlib.cpp:192
#9  0xf327713c in Inspector::RemoteInspector::listingForTarget () at 
./Source/JavaScriptCore/inspector/remote/RemoteInspector.cpp:203
#10 0xf3279af8 in 
Inspector::RemoteInspector::updateAutomaticInspectionCandidate ()
at ./Source/JavaScriptCore/inspector/remote/glib/RemoteInspectorGlib.cpp:251
#11 0xf2a4ecc0 in JSGlobalContextCreateInGroup () at 
./Source/JavaScriptCore/API/JSContextRef.cpp:144
#12 0xf38d0288 in webkit_web_view_get_javascript_global_context () at 
./Source/WebKit/UIProcess/API/glib/WebKitWebView.cpp:3154
#13 0xf38d0350 in webkitWebViewRunJavaScriptCallback () at 
./Source/WebKit/UIProcess/API/glib/WebKitWebView.cpp:3183
#14 0xf38d06e8 in operator() () at 
./Source/WebKit/UIProcess/API/glib/WebKitWebView.cpp:3210
#15 call () at ./Source/WTF/wtf/Function.h:102
#16 0xf36eb534 in WTF::Function::operator()(API::SerializedScriptValue*, bool, 
WebCore::ExceptionDetails const&, WebKit::CallbackBase::Error) const () at 
./Source/WTF/wtf/Function.h:56
#17 WebKit::GenericCallback::performCallbackWithReturnValue ()
at ./Source/WebKit/UIProcess/GenericCallback.h:108
#18 WebKit::WebPageProxy::scriptValueCallback () at 
./Source/WebKit/UIProcess/WebPageProxy.cpp:5123
#19 0xf3a058b0 in IPC::callMemberFunctionImpl, 0u, 1u, 2u, 3u>(WebKit::WebPageProxy*, void 
(WebKit::WebPageProxy::*)(IPC::DataReference const&, bool, 
WebCore::ExceptionDetails const&, WebKit::CallbackID), 
std::tuple&&, std::integer_sequence) ()
at ./Source/WebKit/Platform/IPC/HandleMessage.h:40
#20 IPC::callMemberFunction, std::integer_sequence 
>(std::tuple&&, WebKit::WebPageProxy*, void 
(WebKit::WebPageProxy::*)(IPC::DataReference const&, bool, 
WebCore::ExceptionDetails const&, WebKit::CallbackID)) () at 
./Source/WebKit/Platform/IPC/HandleMessage.h:46
#21 IPC::handleMessage () at 
./Source/WebKit/Platform/IPC/HandleMessage.h:126
#22 0xf39fece8 in WebKit::WebPageProxy::didReceiveMessage () at 
./obj-arm-linux-gnueabihf/DerivedSources/WebKit2/WebPageProxyMessageReceiver.cpp:666
#23 0xf363afd4 in IPC::MessageReceiverMap::dispatchMessage () at 
./Source/WebKit/Platform/IPC/MessageReceiverMap.cpp:123
#24 0xf370f6a8 in WebKit::WebProcessProxy::didReceiveMessage () at 
./Source/WebKit/UIProcess/WebProcessProxy.cpp:590
#25 0xf3636ba0 in IPC::Connection::dispatchMessage () at 

Bug#872481: imagemagick: CVE-2017-12433

2017-08-17 Thread Salvatore Bonaccorso
Control: severity -1 important
Control: tags -1 upstream fixed-upstream

On Thu, Aug 17, 2017 at 09:33:18PM +0200, Salvatore Bonaccorso wrote:
> Source: imagemagick
> Version: 8:6.9.7.4+dfsg-16
> Severity: grave
> Tags: security

Something went wrong when submitting the report.

Regards,
Salvatore



Bug#872475: libisofs6: buffer under-read in read_rr_SL()

2017-08-17 Thread Thomas Schmitt
Hi,

i see the bug in the code but not the attached ISO.
It would be helpful for testing a fix and might give me more ideas
about what to harden.


Have a nice day :)

Thomas



Bug#872483: erlang-cherly: FTBFS on sparc64 due to bad uintptr size

2017-08-17 Thread James Clarke
Source: erlang-cherly
Version: 0.12.8+dfsg-7
Severity: important
Tags: patch upstream
User: debian-sp...@lists.debian.org
Usertags: sparc64
X-Debbugs-Cc: debian-sp...@lists.debian.org

Hi,
Currently erlang-cherly FTBFS on sparc64 due to SIGBUSes in the test
suite. On investigating, I found this was because its uintptr type was
being typedef'd as 32-bit, as only amd64 and ia64 were being checked for
with the preprocessor. The attached patch switches to _LP64 as that is
the least invasive change, but perhaps it should be using the standard
uintptr_t instead. During this I also found that the indirectval was not
being set to 0 and instead being left uninitialised (for example, I saw
it have the value 'H'); I believe this could cause memory corruption if
valsize_in_hash is less than sizeof(void *), since indirectval could be
spuriously true and treating the inline value as a pointer would
overflow the allocated space. It also of course wastes time and space
over storing the value inline.

Regards,
James
diff -Nru erlang-cherly-0.12.8+dfsg/debian/patches/correct-uintptr-type.patch 
erlang-cherly-0.12.8+dfsg/debian/patches/correct-uintptr-type.patch
--- erlang-cherly-0.12.8+dfsg/debian/patches/correct-uintptr-type.patch 
1970-01-01 01:00:00.0 +0100
+++ erlang-cherly-0.12.8+dfsg/debian/patches/correct-uintptr-type.patch 
2017-08-17 20:18:41.0 +0100
@@ -0,0 +1,11 @@
+--- a/c_src/runtime.h
 b/c_src/runtime.h
+@@ -19,7 +19,7 @@ typedef  unsigned long long int  uint64;
+ typedef   float   float32;
+ typedef   double  float64;
+
+-#if defined(__ia64) || defined(__x86_64) || defined(__amd64)
++#if defined(_LP64)
+ typedef   uint64  uintptr;
+ typedef   int64   intptr;
+ #else
diff -Nru erlang-cherly-0.12.8+dfsg/debian/patches/initialize-indirectval.patch 
erlang-cherly-0.12.8+dfsg/debian/patches/initialize-indirectval.patch
--- erlang-cherly-0.12.8+dfsg/debian/patches/initialize-indirectval.patch   
1970-01-01 01:00:00.0 +0100
+++ erlang-cherly-0.12.8+dfsg/debian/patches/initialize-indirectval.patch   
2017-08-17 20:20:16.0 +0100
@@ -0,0 +1,12 @@
+--- a/c_src/hashmap.c
 b/c_src/hashmap.c
+@@ -711,7 +711,8 @@ runtime_makemap_c(MapType *typ, int64 hi
+   if (val->size > MaxValsize) {
+   h->indirectval = 1;
+   valsize_in_hash = sizeof(void*);
+-  }
++  } else
++  h->indirectval = 0;
+
+   // Align value inside data so that mark-sweep gc can find it.
+   h->valoff = key->size;
diff -Nru erlang-cherly-0.12.8+dfsg/debian/patches/series 
erlang-cherly-0.12.8+dfsg/debian/patches/series
--- erlang-cherly-0.12.8+dfsg/debian/patches/series 2016-12-20 
13:10:20.0 +
+++ erlang-cherly-0.12.8+dfsg/debian/patches/series 2017-08-17 
20:23:15.0 +0100
@@ -1,2 +1,4 @@
 add_support_r17_and_r18
 using-crypto_strong_rand_bytes
+initialize-indirectval.patch
+correct-uintptr-type.patch


Bug#872482: collectd: fails to build with dpdk 17.05.1-2 on !amd64

2017-08-17 Thread Luca Boccassi
Package: collectd
Version: 5.7.1-1.1
Severity: important
Tags: patch

Dear Maintainer,

dpdk in experimental is being fixed to be properly multiarch. This
means segregating architecture-dependent headers so that libdpdk-dev
can be correctly co-installed.

Unfortunately reverse dependencies that do not use the provided pkg-
config will fail to build due to some headers moving.

A change has been sent upstream in collectd by Christian and has been
merged to make it use pkg-config if available [1].

Please consider applying the inline patch, backported from upstream
master for the 5.7.x series which is in Debian, so that when we move
the new version from experimental to unstable collectd will not fail to
build.

Thank you!

-- 
Kind regards,
Luca Boccassi

[1] https://github.com/collectd/collectd/pull/2400


From 013bbe150f72265dd13a7c9af4478f70389fc3ad Mon Sep 17 00:00:00 2001
From: Christian Ehrhardt 
Date: Thu, 17 Aug 2017 20:11:30 +0100
Subject: [PATCH] configure.ac: dpdk: use pkg-config

To detect cflags and libs use the sometimes provided pkg-config for
libdpdk. That avoids build errors on systems where special flags are
needed and provided by dpdk via pkg-config, but not yet considered by
the collectd build system.
---
 configure.ac| 81 +
 src/Makefile.am |  3 ++-
 2 files changed, 60 insertions(+), 24 deletions(-)

--- a/configure.ac
+++ b/configure.ac
@@ -2607,34 +2607,69 @@ fi
 
 # --with-libdpdk {{{
 AC_ARG_VAR([LIBDPDK_CPPFLAGS], [Preprocessor flags for libdpdk])
+AC_ARG_VAR([LIBDPDK_CFLAGS], [Compiler flags for libdpdk])
 AC_ARG_VAR([LIBDPDK_LDFLAGS], [Linker flags for libdpdk])
+AC_ARG_VAR([LIBDPDK_LIBS], [Libraries to link for libdpdk])
 
-AC_ARG_WITH([libdpdk], [AS_HELP_STRING([--without-libdpdk], [Disable 
libdpdk.])])
+AC_ARG_WITH([libdpdk],
+  [AS_HELP_STRING([--without-libdpdk], [Disable libdpdk.])],
+  [with_libdpdk="$withval"],
+  [with_libdpdk="yes"]
+)
 
-if test "x$with_libdpdk" != "xno"
-then
-   if test "x$LIBDPDK_CPPFLAGS" = "x"
-   then
-   LIBDPDK_CPPFLAGS="-I/usr/include/dpdk"
-   fi
-   SAVE_CPPFLAGS="$CPPFLAGS"
-   CPPFLAGS="$LIBDPDK_CPPFLAGS $CPPFLAGS"
-   AC_CHECK_HEADERS([rte_config.h],
-   [with_libdpdk="yes"],
-   [with_libdpdk="no (rte_config.h not found)"]
-   )
-   CPPFLAGS="$SAVE_CPPFLAGS"
+if test "x$with_libdpdk" != "xno"; then
+  PKG_CHECK_MODULES([DPDK], [libdpdk], [],
+   [AC_MSG_NOTICE([no DPDK pkg-config, using defaults])])
+  if test "x$LIBDPDK_CPPFLAGS" = "x"; then
+LIBDPDK_CPPFLAGS="-I/usr/include/dpdk"
+  fi
+  if test "x$LIBDPDK_CFLAGS" = "x"; then
+  LIBDPDK_CFLAGS="$DPDK_CFLAGS"
+  LIBDPDK_CPPFLAGS="$LIBDPDK_CPPFLAGS $DPDK_CFLAGS"
+  fi
+  if test "x$LIBDPDK_LIBS" = "x"; then
+  if test "x$DPDK_LIBS" != "x"; then
+  LIBDPDK_LIBS="$DPDK_LIBS"
+  else
+  LIBDPDK_LIBS="-ldpdk"
+  fi
+  fi
+  SAVE_CPPFLAGS="$CPPFLAGS"
+  CPPFLAGS="$LIBDPDK_CPPFLAGS $CPPFLAGS"
+  SAVE_CFLAGS="$CFLAGS"
+  CFLAGS="$LIBDPDK_CFLAGS $CFLAGS"
+  AC_CHECK_HEADERS([rte_config.h],
+[
+  with_libdpdk="yes"
+  AC_PREPROC_IFELSE(
+[
+  AC_LANG_SOURCE(
+[[
+  #include 
+  #if RTE_VERSION < RTE_VERSION_NUM(16,7,0,0)
+  #error "required DPDK >= 16.07"
+  #endif
+]]
+  )
+],
+[dpdk_keepalive="yes"],
+[dpdk_keepalive="no (DPDK version < 16.07)"]
+  )
+],
+[with_libdpdk="no (rte_config.h not found)"]
+  )
+  CPPFLAGS="$SAVE_CPPFLAGS"
+  CFLAGS="$SAVE_CFLAGS"
 fi
 
-if test "x$with_libdpdk" = "xyes"
-then
-   SAVE_LDFLAGS="$LDFLAGS"
-   LDFLAGS="$LIBDPDK_LDFLAGS $LDFLAGS"
-   AC_CHECK_LIB([dpdk], [rte_eal_init],
-   [with_libdpdk="yes"],
-   [with_libdpdk="no (symbol 'rte_eal_init' not found)"]
-   )
-   LDFLAGS="$SAVE_LDFLAGS"
+if test "x$with_libdpdk" = "xyes"; then
+  SAVE_LDFLAGS="$LDFLAGS"
+  LDFLAGS="$LIBDPDK_LDFLAGS $LDFLAGS"
+  AC_CHECK_LIB([dpdk], [rte_eal_init],
+[with_libdpdk="yes"],
+[with_libdpdk="no (symbol 'rte_eal_init' not found)"]
+  )
+  LDFLAGS="$SAVE_LDFLAGS"
 fi
 
 # }}}
--- a/src/Makefile.am
+++ b/src/Makefile.am
@@ -420,8 +420,9 @@ if BUILD_PLUGIN_DPDKSTAT
 pkglib_LTLIBRARIES += dpdkstat.la
 dpdkstat_la_SOURCES = dpdkstat.c
 dpdkstat_la_CPPFLAGS = $(AM_CPPFLAGS) $(LIBDPDK_CPPFLAGS)
+dpdkstat_la_CFLAGS = $(AM_CFLAGS) $(LIBDPDK_CFLAGS)
 dpdkstat_la_LDFLAGS = $(PLUGIN_LDFLAGS) $(LIBDPDK_LDFLAGS)
-dpdkstat_la_LIBADD = -ldpdk
+dpdkstat_la_LIBADD = $(LIBDPDK_LIBS)
 endif
 
 if BUILD_PLUGIN_DRBD

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


Bug#872481: imagemagick: CVE-2017-12433

2017-08-17 Thread Salvatore Bonaccorso
Source: imagemagick
Version: 8:6.9.7.4+dfsg-16
Severity: grave
Tags: security
Forwarded: https://github.com/ImageMagick/ImageMagick/issues/548

Hi,

the following vulnerability was published for imagemagick.

CVE-2017-12433[0]:
| In ImageMagick 7.0.6-1, a memory leak vulnerability was found in the
| function ReadPESImage in coders/pes.c, which allows attackers to cause
| a denial of service, related to ResizeMagickMemory in memory.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-12433
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12433
[1] https://github.com/ImageMagick/ImageMagick/issues/548

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore



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

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



Bug#812826: xim problem

2017-08-17 Thread Sean Whitton
Hello Osamu,

On Thu, Aug 17 2017, Osamu Aoki wrote:

> I have emacs24 and urxvt accept Japanese text input via ibus.

They worked for me with `ibus-daemon --xim` and the old xim env vars,
but not under the setup you recommend.

> Did you install Korean support package? ibus-hangul

Yes.

> PS: I found ibus-wayland ... installing

What was the result?

-- 
Sean Whitton


signature.asc
Description: PGP signature


Bug#853649: gnulib intprops.h build error with gcc 7

2017-08-17 Thread Adrian Bunk
On Thu, Aug 17, 2017 at 08:40:28PM +0200, Bruno Haible wrote:
>...
> Now about your test case: It is not valid C to try to compile just an
> expression.
>...

I was about to say that this was directly copied from intprops.h

And when double-checking that, I finally realized that this is
what is in intprops.h in rush - but intprops.h in current gnulib
git is fine.

When looking at them I missed that they are different at this relevant 
macro, and that the problem is only in the older intprops.h shipped in 
rush.

Sorry for the confusion
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#872480: [node-acorn] Need depends on nodejs > 6

2017-08-17 Thread Bastien ROUCARIÈS
Package: node-acorn
Version: 5.0.3-1
Severity: grave

This version use a lot of depends of nodejs > 6

YOu could drop the second patch serie and use an hard depends

acorn fail on testing

Bastien

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


Bug#872479: alsa-utils: alsa-restore.service uses /run wiich is tmpfs

2017-08-17 Thread GT
Package: alsa-utils
Version: 1.1.3-1
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?
modified  values with alsamixer are not restored at boot
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
use alsamixer
reboot
   * What was the outcome of this action?
cursors are not well restored
   * What outcome did you expect instead?
same values than before the boot

i modify to  use /var/lib/alsa


cat /lib/systemd/system/alsa-restore.service
#
# Note that two different ALSA card state management schemes exist and they
# can be switched using a file exist check - /etc/alsa/state-daemon.conf .
#

[Unit]
Description=Save/Restore Sound Card State
Documentation=man:alsactl(1)
ConditionPathExists=!/etc/alsa/state-daemon.conf
ConditionPathExistsGlob=/dev/snd/control*
After=alsa-state.service

[Service]
Type=oneshot
RemainAfterExit=true
ExecStart=-/usr/sbin/alsactl -E HOME=/var/lib/alsa restore
ExecStop=-/usr/sbin/alsactl -E HOME=/var/lib/alsa store



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

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

Versions of packages alsa-utils depends on:
ii  kmod  24-1
ii  libasound21.1.3-5
ii  libc6 2.24-12
ii  libfftw3-single3  3.3.6p2-1
ii  libncursesw5  6.0+20170715-2
ii  libsamplerate00.1.8-8+b2
ii  libtinfo5 6.0+20170715-2
ii  lsb-base  9.20161125
ii  whiptail  0.52.20-1+b1

alsa-utils recommends no packages.

alsa-utils suggests no packages.

-- Configuration Files:
/etc/init.d/alsa-utils changed:
[ -x /usr/sbin/alsactl ] || exit 0
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
MYNAME=/etc/init.d/alsa-utils
ALSACTLHOME=/run/alsa
[ -d "$ALSACTLHOME" ] || mkdir -p "$ALSACTLHOME"
. /lib/lsb/init-functions
. /usr/share/alsa/utils.sh
log_action_end_msg_and_exit()
{
log_action_end_msg "$1" ${2:+"$2"}
exit $1
}
executable()
{
# If which is not available then we must be running before
# /usr is mounted on a system that has which in /usr/bin/.
# Conclude that $1 is not executable.
[ -x /bin/which ] || [ -x /usr/bin/which ] || return 1
which "$1" >/dev/null 2>&1
}
executable amixer || { echo "${MYNAME}: Error: No amixer program available." 
>&2 ; exit 1 ; }
restore_levels()
{
[ -f /var/lib/alsa/asound.state ] || return 1
CARD="$1"
[ "$1" = all ] && CARD=""
# Assume that if alsactl prints a message on stderr
# then it failed somehow.  This works around the fact
# that alsactl doesn't return nonzero status when it
# can't restore settings for the card
touch /home/guy/alsa-utils-ok.txt
if MSG="$(alsactl -E HOME="$ALSACTLHOME" restore $CARD 2>&1 
>/dev/null)" && [ ! "$MSG" ] ; then
return 0
else
# Retry with the "force" option.  This restores more levels
# but it results in much longer error messages.
alsactl -F restore $CARD >/dev/null 2>&1
log_action_cont_msg "warning: 'alsactl -E HOME="$ALSACTLHOME" 
restore${CARD:+ $CARD}' failed with error message '$MSG'"
return 1
fi
}
store_levels()
{
CARD="$1"
[ "$1" = all ] && CARD=""
if MSG="$(alsactl -E HOME="$ALSACTLHOME" store $CARD 2>&1)" ; then
sleep 1
return 0
else
log_action_cont_msg "warning: 'alsactl store${CARD:+ $CARD}' 
failed with error message '$MSG'"
return 1
fi
}
mute_and_zero_levels_on_card()
{
CARDOPT="-c $1"
for CTL in \
Master \
PCM \
Synth \
CD \
Line \
Mic \
"PCM,1" \
Wave \
Music \
AC97 \
"Master Digital" \
DAC \
"DAC,0" \
"DAC,1" \
Headphone \
Speaker \
Playback
do
mute_and_zero_level "$CTL"
done
return 0
}
mute_and_zero_levels()
{
TTZML_RETURNSTATUS=0
case "$1" in
  all)
for CARD in $(echo_card_indices) ; do
mute_and_zero_levels_on_card "$CARD" || 
TTZML_RETURNSTATUS=1
done
;;
  *)
mute_and_zero_levels_on_card "$1" || TTZML_RETURNSTATUS=1
;;
esac
return $TTZML_RETURNSTATUS
}

Bug#864848: Should not talk about hd-media - that's armhf only

2017-08-17 Thread Holger Wansing
On Thu, 15 Jun 2017 22:51:21 +0100
Steve McIntyre  wrote:
> Package: installation-guide-armel
> Severity: normal
> 
> As seen in
> 
>   https://www.debian.org/releases/jessie/armel/ch05s01.html.en
> 
> there's discussion of "unpack the hd-media tarball". This doesn't
> exist on armel...

Does that mean, that armel does not support that "Boot from USB stick in
U-Boot" thingy, described under above link?
If that _is_ supported, that chapter needs to be rewritten (simply leaving
out the part where the hd-media tarball is mentioned, would make the whole
chapter senseless/important part missing).


Adding arm porters to the loop seems to make sense here.


Holger

-- 
Holger Wansing 



Bug#872478: cacti: XSS in spikekill.php via method parameter

2017-08-17 Thread Salvatore Bonaccorso
Source: cacti
Version: 1.1.17+ds1-1
Severity: important
Tags: patch upstream security fixed-upstream
Forwarded: https://github.com/Cacti/cacti/issues/907

hi

Opening the tracking bug for the XSS issue reported at
https://github.com/Cacti/cacti/issues/907 .  Upstream fix:
https://github.com/Cacti/cacti/commit/a032ce0be6a4ea47862c594e40a619ac8de1ef99

A CVE has been requested for this issue.

Regards,
Salvatore



Bug#872477: aptitude: incorrect mentioned architecture on dependency information

2017-08-17 Thread Vincent Lefevre
Package: aptitude
Version: 0.8.8-1
Severity: normal

In an upgrade, aptitude shows:

 Actions  Undo  Package  Resolver  Search  Options  Views  Help
C-T: Menu  ?: Help  q: Quit  u: Update  g: Preview/Download/Install/Remove Pkgs
PackagesPreview
aptitude 0.8.8 @ cventin Disk: +137 kB   DL: 6847 kB
--\ Packages to be upgraded (19)
iu  bsdutils   1:2.29.2-2   1:2.29.2-4  
iu  libblkid-dev -4096 B   2.29.2-2 2.29.2-4
iu  libblkid1-4096 B   2.29.2-2 2.29.2-4
iuA libblkid1:i386 2.29.2-2 2.29.2-4
iu  libfdisk1-4096 B   2.29.2-2 2.29.2-4
iu  libmount1-4096 B   2.29.2-2 2.29.2-4
iuA libmount1:i386   +4096 B   2.29.2-2 2.29.2-4
iuA libsamplerate0 0.1.8-8+b2   0.1.9-1 
iu  libsmartcols1  2.29.2-2 2.29.2-4
iuA libsndfile1  +4096 B   1.0.28-3 1.0.28-4
iuA libsndfile1:i386 +4096 B   1.0.28-3 1.0.28-4
iu  libuuid1   2.29.2-2 2.29.2-4
iuA libuuid1:i386  2.29.2-2 2.29.2-4
iu  mount-70.7 kB  2.29.2-2 2.29.2-4
iuA poppler-data +98.3 kB  0.4.7-8  0.4.8-1 
iu  util-linux   -305 kB   2.29.2-2 2.29.2-4
iuA util-linux-local   2.29.2-2 2.29.2-4
iu  uuid-dev   2.29.2-2 2.29.2-4
iuA uuid-runtime   2.29.2-2 2.29.2-4
--\ Packages being automatically installed to satisfy dependencies (1)
piA fdisk+419 kB  2.29.2-4
--\ Packages being held back (2)
iF  xpdf   3.04-1+local43.04-4
iF  xpdf-dbgsym3.04-1+local43.04-4
--\ Packages being automatically held in their current state (3)
iFA libfreetype6   2.6.3-3.22.8-0.2
collection of partitioning utilities
fdisk (install, 2.29.2-4) will be automatically installed to satisfy the   ▒
following dependencies:▒
   ▒
  * util-linux (upgrade, 2.29.2-2 -> 2.29.2-4) depends on fdisk (provided by   ▒
fdisk:i386 2.29.2-4)   ▒

while the cursor is over "fdisk".

It is said "provided by fdisk:i386" whereas it is fdisk that will be
installed (i.e. fdisk:amd64 since amd64 is the default architecture),
not fdisk:i386.

Note: Before the upgrade, "dpkg -l" doesn't show any fdisk:* package
installed; and after the upgrade, "dpkg -l" shows that fdisk is
installed, and "dpkg -s fdisk" confirms that it is from amd64.

-- Package-specific info:
Terminal: xterm-debian
$DISPLAY is set.
which aptitude: /usr/bin/aptitude

aptitude version information:
aptitude 0.8.8
Compiler: g++ 6.3.0 20170516
Compiled against:
  apt version 5.0.1
  NCurses version 6.0
  libsigc++ version: 2.10.0
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.0.20170715
  cwidget version: 0.5.17
  Apt version: 5.0.2

aptitude linkage:
linux-vdso.so.1 (0x7ffdd47d9000)
libgtk3-nocsd.so.0 => /usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0 
(0x7f8730dae000)
libapt-pkg.so.5.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 
(0x7f87309f9000)
libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 
(0x7f87307c9000)
libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 
(0x7f873059f000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7f8730398000)
libcwidget.so.3 => /usr/lib/x86_64-linux-gnu/libcwidget.so.3 
(0x7f873009d000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7f872fd92000)
libboost_iostreams.so.1.62.0 => 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.62.0 (0x7f872fb7a000)
libboost_filesystem.so.1.62.0 => 
/usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.62.0 (0x7f872f961000)
libboost_system.so.1.62.0 => 
/usr/lib/x86_64-linux-gnu/libboost_system.so.1.62.0 (0x7f872f75d000)
libxapian.so.30 => /usr/lib/x86_64-linux-gnu/libxapian.so.30 
(0x7f872f349000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f872f12c000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f872edad000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 

Bug#872258: Same error with slic3r

2017-08-17 Thread Will C.
Apparently, I get the same error when I launch slic3r. On the other hand,
when I launch slic3r-prusa, I get the error in #872275


-Will


  1   2   3   >