Bug#917656: libnet-server-mail-perl: FTBFS (failing tests)

2018-12-29 Thread Xavier
Le 29/12/2018 à 22:39, Santiago Vila a écrit :
> Package: src:libnet-server-mail-perl
> Version: 0.25-4
> Severity: serious
> Tags: ftbfs
> 
> Dear maintainer:
> 
> I tried to build this package in buster but it failed:
> 
> 
> [...]
> ok 10
> ok
> # Error: Can't call method "peerhost" on an undefined value at t/starttls.t 
> line 131.
> # kill 9, 1658 (server)

Hi all,

SSL randomly timeout error is back. Do I have to disable the relevant test ?



Bug#901651: Python debian: deb822: add support for returning Version objects from iter_paragraphs

2018-12-29 Thread Paul Wise
On Sun, 2018-12-30 at 17:39 +1100, Stuart Prescott wrote:

> Comments or thoughts?

Looks good to me.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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


Bug#916034: sl-modem-dkms: module FTBFS for 4.18.0-3-amd64, 4.9.0-8-amd64

2018-12-29 Thread أحمد المحمودي
On Wed, Dec 12, 2018 at 01:56:11PM +0100, Andreas Beckmann wrote:
> You you get the compile flags from Kbuild, or do you reinvent them on
> your own?
---end quoted text---

This is the DKMS build line:
MAKE[0]="cd ${dkms_tree}/sl-modem/#MODULE_VERSION#/build; make -C drivers USB=1 
KERNEL_DIR=$kernel_source_dir KERNEL_VER=$kernelver; make -C ungrab-winmodem 
KERNEL_DIR=$kernel_source_dir KERNEL_VER=$kernelver; cd .."

-- 
‎أحمد المحمودي (Ahmed El-Mahmoudy)
 Digital design engineer
GPG KeyIDs: 4096R/A7EF5671 2048R/EDDDA1B7
GPG Fingerprints:
 6E2E E4BB 72E2 F417 D066  6ABF 7B30 B496 A7EF 5761
 8206 A196 2084 7E6D 0DF8  B176 BC19 6A94 EDDD A1B7


signature.asc
Description: PGP signature


Bug#917779: groff FTCBFS: directory layout changed

2018-12-29 Thread Helmut Grohne
Source: groff
Version: 1.22.4-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

groff fails to cross build from source, because it now fails running the
native cross. It uses two build passes (native and cross) since it needs
a native groff. That used to be located in
build-native/src/roff/groff/groff, but some recent upstream release
moved it to build-native/groff. Other tools followed. The hierarchy got
flattened. Unfortunately the debian packaging was not updated for the
new layout and now it fails. The attached patch fixes that. Please
include that in buster, because groff is part of build-essential.

Helmut
diff --minimal -Nru groff-1.22.4/debian/changelog groff-1.22.4/debian/changelog
--- groff-1.22.4/debian/changelog   2018-12-24 00:35:24.0 +0100
+++ groff-1.22.4/debian/changelog   2018-12-28 16:24:18.0 +0100
@@ -1,3 +1,10 @@
+groff (1.22.4-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Update build-native paths to new layout. (Closes: #-1)
+
+ -- Helmut Grohne   Fri, 28 Dec 2018 16:24:18 +0100
+
 groff (1.22.4-1) unstable; urgency=medium
 
   * New upstream release.
diff --minimal -Nru groff-1.22.4/debian/rules groff-1.22.4/debian/rules
--- groff-1.22.4/debian/rules   2018-12-24 00:29:59.0 +0100
+++ groff-1.22.4/debian/rules   2018-12-28 16:24:18.0 +0100
@@ -65,27 +65,12 @@
   cross :=
 else
   native_tmp := $(CURDIR)/debian/build-native
-  groff_bin_dirs := \
-   $(native_tmp)/src/roff/groff \
-   $(native_tmp)/src/roff/troff \
-   $(native_tmp)/src/preproc/pic \
-   $(native_tmp)/src/preproc/eqn \
-   $(native_tmp)/src/preproc/tbl \
-   $(native_tmp)/src/preproc/grn \
-   $(native_tmp)/src/preproc/refer \
-   $(native_tmp)/src/preproc/soelim \
-   $(native_tmp)/src/preproc/html \
-   $(native_tmp)/src/devices/grops \
-   $(native_tmp)/src/devices/grodvi \
-   $(native_tmp)/src/devices/grotty \
-   $(native_tmp)/src/devices/grolj4 \
-   $(native_tmp)/src/devices/grolbp \
-   $(native_tmp)/src/devices/grohtml
+  groff_bin_dirs := $(native_tmp)
   empty :=
   space := $(empty) $(empty)
   cross := \
-   GROFFBIN=$(native_tmp)/src/roff/groff/groff \
-   GROFF_BIN_DIR=$(native_tmp)/src/roff/groff \
+   GROFFBIN=$(native_tmp)/groff \
+   GROFF_BIN_DIR=$(native_tmp) \
GROFF_BIN_PATH=$(subst $(space),:,$(groff_bin_dirs))
 endif
 


Bug#917778: supercat: make supercat reproducible adding debhelper

2018-12-29 Thread Juan Picca
Package: supercat
Version: 0.5.5-4.3
Severity: normal
Tags: patch
Usertags: fileordering locale umask

Dear Maintainer,

While working on the "reproducible builds" effort [1], we have noticed
that supercat could not be built reproducibly.

The attached patch (make-reproducible-adding-debhelper.patch) adds
debhelper to build the package, removing reproducibility issues.

Also, a second patch (fix-lintian-issues.patch) is added to fix some
lintian issues.

Regards,
JMPC

[1]: https://wiki.debian.org/ReproducibleBuilds
diff -urN supercat-0.5.5.old/debian/compat supercat-0.5.5/debian/compat
--- supercat-0.5.5.old/debian/compat2016-08-02 03:45:06.0 +
+++ supercat-0.5.5/debian/compat2018-12-28 13:59:14.374775078 +
@@ -1 +1 @@
-5
+11
diff -urN supercat-0.5.5.old/debian/control supercat-0.5.5/debian/control
--- supercat-0.5.5.old/debian/control   2016-08-02 16:45:18.0 +
+++ supercat-0.5.5/debian/control   2018-12-28 13:59:41.158359483 +
@@ -2,7 +2,7 @@
 Section: utils
 Priority: optional
 Maintainer: Kumar Appaiah 
-Build-Depends: autotools-dev, quilt, autoconf, automake
+Build-Depends: debhelper (>= 11)
 Standards-Version: 3.8.3
 Homepage: http://supercat.nosredna.net/
 Vcs-Browser: http://git.debian.org/?p=users/akumar/supercat.git
diff -urN supercat-0.5.5.old/debian/rules supercat-0.5.5/debian/rules
--- supercat-0.5.5.old/debian/rules 2016-08-02 08:57:31.0 +
+++ supercat-0.5.5/debian/rules 2018-12-28 12:02:39.513188272 +
@@ -1,117 +1,4 @@
 #!/usr/bin/make -f
-# -*- makefile -*-
-
-export SOURCE_DATE_EPOCH = $(shell date -d "$$(dpkg-parsechangelog --count 1 
-SDate)" +%s)
-
-# Package name
-PACKAGE_NAME = supercat
-
-# Install program
-INSTALL = install
-
-INSTALL_FILE= $(INSTALL) -p-o root -g root  -m  644
-INSTALL_PROGRAM = $(INSTALL) -p-o root -g root  -m  755
-INSTALL_SCRIPT  = $(INSTALL) -p-o root -g root  -m  755
-INSTALL_DIR = $(INSTALL) -p -d -o root -g root  -m  755
-
-
-# The installation directory
-PACKAGE_DIR = debian/$(PACKAGE_NAME)
-
-CFLAGS=$(shell dpkg-buildflags --get CFLAGS)
-LDFLAGS=$(shell dpkg-buildflags --get LDFLAGS)
-
-ifneq ($(DEB_HOST_GNU_TYPE),$(DEB_BUILD_GNU_TYPE))
-CROSS= --build $(DEB_BUILD_GNU_TYPE) --host $(DEB_HOST_GNU_TYPE)
-else
-CROSS= --build $(DEB_BUILD_GNU_TYPE)
-endif
-
-ifeq (,$(findstring nostrip,$(DEB_BUILD_OPTIONS)))
-INSTALL_PROGRAM += -s
-endif
-
-configure:
-   cp -f configure.ac configure.ac.bak
-   autoupdate configure.ac
-   autoreconf --force --install --symlink --warnings=all
-   ./configure $(CROSS) --prefix=/usr --mandir=\$${prefix}/share/man 
--infodir=\$${prefix}/share/info CFLAGS="$(CFLAGS)" LDFLAGS="$(LDFLAGS)"
-
-config.status: configure
-   $(checkdir)
-ifneq "$(wildcard /usr/share/misc/config.sub)" ""
-   cp -f /usr/share/misc/config.sub config.sub
-endif
-ifneq "$(wildcard /usr/share/misc/config.guess)" ""
-   cp -f /usr/share/misc/config.guess config.guess
-endif
-
-
-build: build-stamp
-
-build-stamp: config.status
-   $(checkdir)
-   $(MAKE)
-   touch $@
-
-clean: checkroot
-   $(checkdir)
-   rm -f build-stamp
-   [ ! -f Makefile ] || $(MAKE) distclean
-   rm -f config.sub config.guess config.log
-   rm -rf $(PACKAGE_DIR) debian/files debian/substvars
-   test -e configure.ac.bak && mv -f configure.ac.bak configure.ac || true
-   rm -f Makefile.in */Makefile.in aclocal.m4 config.h.in configure
-   rm -f compile install-sh missing depcomp
-   rm -rf autom4te.cache/
-
-install: checkroot build
-   $(checkdir)
-   $(MAKE) DESTDIR=$(CURDIR)/$(PACKAGE_DIR) install
-
-# Build architecture-independent files here.
-binary-indep: checkroot build install
-# We have nothing to do by default.
-
-# Build architecture-dependent files here.
-binary-arch: checkroot build install
-   $(checkdir)
-   $(INSTALL_DIR) $(PACKAGE_DIR)/usr/share/doc/$(PACKAGE_NAME)/
-   for i in doc/spc.txt debian/README.Debian;do \
-   $(INSTALL_FILE) -m 644 $$i 
$(PACKAGE_DIR)/usr/share/doc/$(PACKAGE_NAME)/; \
-   done;
-   $(INSTALL_FILE) -m 644 ChangeLog 
$(PACKAGE_DIR)/usr/share/doc/$(PACKAGE_NAME)/changelog
-   $(INSTALL_FILE) -m 644 debian/changelog 
$(PACKAGE_DIR)/usr/share/doc/$(PACKAGE_NAME)/changelog.Debian
-   for i in $(PACKAGE_DIR)/usr/share/doc/$(PACKAGE_NAME)/changelog*;do \
-   gzip -9nv $$i; \
-   done;
-   $(INSTALL_FILE) -m 644 debian/copyright 
$(PACKAGE_DIR)/usr/share/doc/$(PACKAGE_NAME)/copyright
-   $(INSTALL_DIR) $(PACKAGE_DIR)/etc/$(PACKAGE_NAME)
-   $(INSTALL_DIR) $(PACKAGE_DIR)/usr/share/man/man1
-   $(INSTALL_FILE) -m 644 doc/spc.1 $(PACKAGE_DIR)/usr/share/man/man1
-   gzip -9nv $(PACKAGE_DIR)/usr/share/man/*/*
-# Strip binaries (including hack by policy wonks)
-ifeq (,$(findstring nostrip,$(DEB_BUILD_OPTIONS)))
-   strip -R.note -R.comment $(PACKAGE_DIR)/usr/bin/*
-endif
-   dpkg-shlibdeps $(PACKAGE_DIR)/us

Bug#901651: Python debian: deb822: add support for returning Version objects from iter_paragraphs

2018-12-29 Thread Stuart Prescott
Control: tags -1 + patch

On Saturday, 16 June 2018 16:48:13 AEDT Paul Wise wrote:
> It would be a useful feature to have the iter_paragraphs method from
> the deb822 Sources and Packages classes support returning Version
> objects in the Version field. This would help with sorting versions.
> 
> Since this would add overhead and might be incompatible with things
> like json.dumps, it might be best to either not enable it by default
> or declare it as a breaking API change in the docuentation.

I've had a go at implementing this in a backwards-compatible fashion by 
exposing methods for get_version() and set_version(v) within the classes for 
which that makes sense (Dsc, Changes, Packages, Sources).

https://salsa.debian.org/python-debian-team/python-debian/merge_requests/7

Comments or thoughts?

cheers
Stuart

-- 
Stuart Prescotthttp://www.nanonanonano.net/   stu...@nanonanonano.net
Debian Developer   http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7



Bug#917579: new upstream version (3.36)

2018-12-29 Thread Norbert Preining
On Fri, 28 Dec 2018, Daniel Baumann wrote:
> it would be nice if you could upgrade to the current upstream version

https://lists.debian.org/debian-tex-maint/2018/12/msg00019.html

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13



Bug#917717: pylint-django: FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7 returned exit code 13

2018-12-29 Thread eamanu15
Hi,

This is because upstream deleted the "YES" alias from astroid on
https://github.com/PyCQA/astroid/commit/36fa294e9b84885d95a03b1fbc07da63e6d6a79b

This issue was opened on pylint-django (
https://github.com/PyCQA/pylint-django/issues/201)

They resolve the issue adding on setup.py the requirement of astroid ==
2.0.4.

I've push to salsa a patch adding the 'YES' alias on pylint-django (
https://salsa.debian.org/python-team/modules/pylint-django/commit/c3f38068cda75d4125b4e6274598a8f4acd892bd#58ef006ab62b83b4bec5d81fe5b32c3b4c2d1cc2
)

Cheers

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest


Bug#917777: ITP: sexpect -- Expect for Shells

2018-12-29 Thread Clark Wang
Package: wnpp
Severity: wishlist
Owner: Clark Wang 

* Package name: sexpect
  Version : 2.1.8
  Upstream Author : Clark Wang 
* URL : https://github.com/clarkwang/sexpect
* License : GPL
  Programming Lang: C
  Description : Expect for Shells

Expect is for Tcl. Expect.pm is for Perl. Pexpect is for Python. ... But
what for shells?

Quite often, shell scripters need to use Expect to progmatically
interact with another program. The big problem is they don't have time
to learn Tcl's syntax or they don't want to.

I developed "sexpect" which is a single program. It works like GNU
screen. It runs the spawned process on a pty in background as a daemon
and it can talk with the daemon and control the spawned process.

Example:

 # sexpect spawn ssh user@host echo hello world
 # sexpect expect -nocase password:
 # sexpect send -cstring 'password\r'
 # sexpect expect -eof
 # sexpect wait



Bug#917776: python3-astroid: The homepage "www.astroid.com" does not exist

2018-12-29 Thread eamanu
Package: python3-astroid
Severity: normal

Dear Maintainer,

The Homepage "www.astroid.org" Doest not exist. 


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

Kernel: Linux 4.9.0-8-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)

Versions of packages python3-astroid depends on:
ii  python33.5.3-1
pn  python3-lazy-object-proxy  
ii  python3-six1.10.0-3
pn  python3-wrapt  

python3-astroid recommends no packages.

python3-astroid suggests no packages.



Bug#917775: RFP: xrandr-invert-colors -- xrandr-invert-colors

2018-12-29 Thread Eric Wong
Package: wnpp
Severity: wishlist

* Package name: xrandr-invert-colors
  Version : git
  Upstream Author : Zoltan Padrah 
* URL : https://github.com/zoltanp/xrandr-invert-colors
* License : GPL-3.0+
  Programming Lang: C
  Description : invert colors on all screens using XRandR

"xcalib -i -a" does not work with all video cards and doesn't
work on all screens.  xrandr-invert-colors is better than xcalib
in this case.



Bug#917774: RFP: rubygems-roda -- routing tree web toolkit for Ruby

2018-12-29 Thread Eric Wong
Package: wnpp
Severity: wishlist

* Package name: rubygems-roda
  Version : 3.15.0
  Upstream Author : Jeremy Evans
* URL : http://roda.jeremyevans.net/
* License : MIT
  Programming Lang: Ruby
  Description : routing tree web toolkit for Ruby

Roda is a routing tree web toolkit, designed for building fast and
maintainable web applications in ruby.

It's faster and simpler than existing frameworks like sinatra
or rails

I don't plan to maintain it in Debian myself.



Bug#917428: [Debian-science-sagemath] Python 2 matplotlib package required for sagemath

2018-12-29 Thread Sandro Tosi
> You are right, I didn't notice the new matplotlib2 package and sagemath 
> failed to build due to the missing matplotlibrc in python-matplotlib-data.

this should be fixed, does sagemath build fine now?

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi



Bug#907998: gimp: Gimp does not load or crashes quickly

2018-12-29 Thread Jeremy Bicha
On Tue, Sep 4, 2018 at 7:57 PM Michael Biebl  wrote:
> On 9/5/18 01:08, Attila Kinali wrote:
> > Package: gimp
> > Version: 2.10.6-2
> > Severity: grave
> > Justification: renders package unusable
> >
> > Hi,
> >
> > No matter what I do, Gimp does not load properly. Most times it
> > just gets stuck on some routine on boot up. If it successfully
> > loads, then it crashes within a few operations. There does not
> > seem a pattern, at least not one that I could descern.
> >
>
> When it crashes, what's the output on stdout/stderr?

There has been no reply in nearly 3 months. Therefore, we will be
closing this bug soon since there is not enough information for us to
be able to do anything here.

Thanks,
Jeremy Bicha



Bug#803197: SOGo isn't the only victim, cups breaks as well

2018-12-29 Thread Ryan Tandy

On Sat, Dec 29, 2018 at 05:36:32PM -0800, Ryan Tandy wrote:

I have attached a test program


Actually attached this time.
#include 
#include 
#include 
#include 

#include 
#include 
#include 
#include 
#include 

#include 
#include 

#define LDAP_DEPRECATED 1
#include 

static const char *server_name = "ldap.stanford.edu";
static const char *server_service = "ldaps";
static const char *server_uri = "ldap://ldap.stanford.edu";;

static void *libldap;

static int (*myldap_initialize)(LDAP **, const char *);
static int (*myldap_set_option)(LDAP *, int, const void *);
static char *(*myldap_err2string)(int );
static int (*myldap_start_tls_s)(LDAP *, LDAPControl **, LDAPControl **);
static int (*myldap_simple_bind_s)(LDAP *, const char *, const char *);
static int (*myldap_unbind_s)(LDAP *);

#define DLSYM(sym) { my##sym = dlsym(libldap, #sym); chk_dl("dlopen"); }

static void chk_g(int rc) {
	if (rc < 0) {
		gnutls_perror(rc);
		exit(EXIT_FAILURE);
	}
}

static void chk_dl(const char *s) {
	const char *err = dlerror();
	if (err != NULL) {
		fprintf(stderr, "%s: %s\n", s, err);
		exit(EXIT_FAILURE);
	}
}

static void chk_ld(int rc, const char *s) {
	if (rc != LDAP_SUCCESS) {
		const char *err = myldap_err2string(rc);
		fprintf(stderr, "%s: %s\n", s, err);
		exit(EXIT_FAILURE);
	}
}

static void chk(int rc, const char *s) {
	if (rc < 0) {
		perror(s);
		exit(EXIT_FAILURE);
	}
}

static gnutls_session_t tls_connect(gnutls_certificate_credentials_t cred) {
	gnutls_session_t session;
	chk_g(gnutls_init(&session, GNUTLS_CLIENT));
	chk_g(gnutls_set_default_priority(session));
	chk_g(gnutls_server_name_set(session, GNUTLS_NAME_DNS, server_name, strlen(server_name)));
	chk_g(gnutls_credentials_set(session, GNUTLS_CRD_CERTIFICATE, cred));

	struct addrinfo *ai;
	chk(getaddrinfo(server_name, server_service, NULL, &ai), "getaddrinfo");

	int sd = socket(AF_INET, SOCK_STREAM, 0);
	chk(sd, "socket");

	chk(connect(sd, ai->ai_addr, ai->ai_addrlen), "connect");

	printf("Connected to %s:%s\n", server_name, server_service);

	gnutls_transport_set_int(session, sd);

	int rc;
	while ((rc = gnutls_handshake(session)) == GNUTLS_E_AGAIN) {
		printf("gnutls_handshake: %s\n", gnutls_strerror(rc));

	}
	chk_g(rc);

	printf("TLS established\n");
	return session;
}

static void tls_disconnect(gnutls_session_t session) {
	int rc = gnutls_bye(session, GNUTLS_SHUT_RDWR);
	chk_g(rc);
	gnutls_deinit(session);

	printf("Disconnected\n");
}

static void open_libldap() {
	libldap = dlopen("libldap.so", RTLD_NOW);
	chk_dl("dlopen");

	DLSYM(ldap_initialize);
	DLSYM(ldap_set_option);
	DLSYM(ldap_err2string);
	DLSYM(ldap_start_tls_s);
	DLSYM(ldap_simple_bind_s);
	DLSYM(ldap_unbind_s);
}

int main(void) {
	chk_g(gnutls_global_init());

	gnutls_certificate_credentials_t cred;
	chk_g(gnutls_certificate_allocate_credentials(&cred));
	chk_g(gnutls_certificate_set_x509_system_trust(cred));

	gnutls_session_t session = tls_connect(cred);
	tls_disconnect(session);

	open_libldap();

	LDAP *ld;
	chk_ld(myldap_initialize(&ld, server_uri), "ldap_initialize");

	const int version = 3;
	chk_ld(myldap_set_option(ld, LDAP_OPT_PROTOCOL_VERSION, &version), "ldap_set_option");

	chk_ld(myldap_start_tls_s(ld, NULL, NULL), "ldap_start_tls_s");
	chk_ld(myldap_simple_bind_s(ld, NULL, NULL), "ldap_simple_bind_s");

	chk_ld(myldap_unbind_s(ld), "ldap_unbind_s");

	chk(dlclose(libldap), "dlclose");

	session = tls_connect(cred);
	tls_disconnect(session);

	gnutls_certificate_free_credentials(cred);
	gnutls_global_deinit();

	exit(EXIT_SUCCESS);
}


Bug#803197: Exactly the same problem happens with sendmail.

2018-12-29 Thread Ryan Tandy

Hi John,

On Mon, Sep 04, 2017 at 06:42:37PM +0200, John Hughes wrote:

Sendmail, on start, closes all fd's above 2.

Since sendmail is linked to libldap, which is linked to gnutls this 
means sendmail closes fd 3, on which gnutls has opened /dev/urandom.


Later on in the sendmail run fd 3 gets reopened, and if a ldap 
function is called then gnutls unceremoniously closes the fd and 
reopens /dev/urandom.


From sendmail's point of view it looks like one of its files has 
suddenly been replaced with random garbage!


I'm sorry for not responding to this for so long, but do you recall what 
release of Debian you saw this behaviour on?


I've been looking at this ticket again and it looks like in stretch 
(Debian 9) and later, GnuTLS uses the getrandom() system call and does 
not open/reopen anything. So I'm wondering whether you encountered this 
problem in stretch as well, or only in jessie - or whether getrandom() 
is for some reason not available on your setup and GnuTLS falls back to 
opening urandom.


If you still have the same problem on stretch or buster, I'd welcome any 
info about how to set up a system to reproduce it.


Thanks
Ryan



Bug#803197: SOGo isn't the only victim, cups breaks as well

2018-12-29 Thread Ryan Tandy
Upon reviewing this bug, I've found that in stretch and later, GnuTLS 
actually uses getrandom() instead of opening /dev/urandom. This was 
introduced in GnuTLS 3.5.3 and requires Linux 3.18 and Glibc 2.25. The 
fd-clobber program that I attached to an earlier comment [1] 
demonstrates the issue in jessie, but works without issue in stretch and 
buster.


[1] 
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=803197;filename=fd-clobber.c;msg=25

You can observe this by running any LDAP client with 
GNUTLS_DEBUG_LEVEL=2:


gnutls[2]: getrandom random generator was detected

Based on that, I believe that the issue originally reported was actually 
resolved by that change, and the fd closing could probably be reinstated 
for systems where getrandom() is available. I will try to patch that 
back into SOGo and see what happens on a current system.


As for the cupsd issue you reported: I haven't been able to reproduce 
the segfault in cupsd, but I have attached a test program that I think 
demonstrates the issue as you described it. However, it crashes 
consistently in stretch but not in buster. :) Not sure whether that is a 
functional change or just luck of memory layout.


I need to do some more testing, but I think I will be OK with removing 
the gnutls_global_set_mutex() calls in the next upload. But even so, 
please do migrate to nss-pam-ldapd! Your point about libldap messing 
with global state is valid, but in the specific case of PAM modules we 
already have a solution, as Howard did point out to you.




Bug#238585: [Pkg-sysvinit-devel] Bug#238585: changing submitter

2018-12-29 Thread Jay Berkenbilt
No, I think this has long since been overcome by events. Please feel free
to close. We live in a world of systemd today. Thanks for following up.

On Sat, Dec 29, 2018 at 1:33 PM Dmitry Bogatov  wrote:

>
> control: tags -1 +moreinfo
>
> Dear submitter, are you still going to implement your suggestion?
>
> [2008-06-11 18:35] Petter Reinholdtsen 
> >
> > part   text/plain 448
> > [Jay Berkenbilt]
> > > A quick perusal of the code suggests that it should be a pretty
> > > localized change.
> >
> > I would recommend looking at how SuSe and Fedore does this, to see if
> > they got some nice ideas.  In SuSe, I know that parallel booting is
> > disabled when interactive boot is activated, and I suspect this is a
> > good idea for Debian too.
> >
> > And yes, a patch relative to the latest svn version is prefered. :)
> >
> > Happy hacking,
> > --
> > Petter Reinholdtsen
>
>


Bug#746221: initscripts: Debian should have an init script for saving/restoring backlight level on laptops

2018-12-29 Thread Benda Xu
Hi Dmitry,

Dmitry Bogatov  writes:

> Dear co-maintainers, what do you think? While personally I never used
> this feature, I believe it would not introduce much of complexity into
> initscripts. Neither I believe this functionality deserves separate
> binary package. So, objections to inclusion?

Recently I have been tuning the backlight of my laptop manually.

We have, for example `xbacklight` in the repository that needs to be
updated to support newer laptop models.

Benda



Bug#917773: shadow: doesn't respect SOURCE_DATE_EPOCH

2018-12-29 Thread Johannes 'josch' Schauer
Source: shadow
Severity: normal
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps

Hi,

the /etc/shadow as created by debootstrap does not respect the
SOURCE_DATE_EPOCH environment variable anymore. This bug was formerly
fixed in #857803. Steps to reproduce:

$ sudo SOURCE_DATE_EPOCH=0 debootstrap --variant=minbase unstable 
debian-unstable
$ sudo cat debian-unstable/etc/shadow
root:*:17895:0:9:7:::
daemon:*:17895:0:9:7:::
bin:*:17895:0:9:7:::
sys:*:17895:0:9:7:::
sync:*:17895:0:9:7:::
games:*:17895:0:9:7:::
man:*:17895:0:9:7:::
lp:*:17895:0:9:7:::
mail:*:17895:0:9:7:::
news:*:17895:0:9:7:::
uucp:*:17895:0:9:7:::
proxy:*:17895:0:9:7:::
www-data:*:17895:0:9:7:::
backup:*:17895:0:9:7:::
list:*:17895:0:9:7:::
irc:*:17895:0:9:7:::
gnats:*:17895:0:9:7:::
nobody:*:17895:0:9:7:::
_apt:*::0:9:7:::

So some parts of shadow respect SOURCE_DATE_EPOCH (the user _apt is
created with a lastchange field of zero) but other parts do not (the
remaining users).

Unfortunately I don't have time to debug this problem right now but my
hunch is, that the culprit is a line like this:

https://sources.debian.org/src/shadow/1:4.5-1.1/src/pwconv.c/?hl=268#L268

Instead, spent.sp_lstchg should be set to the return value of the
gettime() function.

Thanks!

cheers, josch



Bug#917772: java-common: Please bump OpenJDK version for sh4 to 11

2018-12-29 Thread John Paul Adrian Glaubitz
Source: java-common
Version: 0.70
Severity: normal
User: debian-sup...@lists.debian.org
Usertags: sh4

Hello!

I have successfully bootstrapped OpenJDK 11 for sh4, thus we can
bump the default Java version for sh4 in the java-common package
to 11:

--- debian/java_defaults.mk.orig2018-10-03 23:26:42.0 +0200
+++ debian/java_defaults.mk 2018-12-29 23:11:51.998816128 +0100
@@ -7,10 +7,9 @@
alpha amd64 arm64 armel armhf i386 \
ia64 m68k mips mipsel mips64el \
powerpc ppc64 ppc64el \
-   riscv64 s390x sparc64 x32
+   riscv64 s390x sh4 sparc64 x32
 java10_architectures = $(java11_architectures) \
-   powerpcspe \
-   sh4
+   powerpcspe
 java9_architectures = $(java10_architectures)
 java8_architectures = $(java9_architectures) \
kfreebsd-amd64 kfreebsd-i386

Please incorporate this change for the next upload.

Thanks,
Adrian

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
--- debian/java_defaults.mk.orig2018-10-03 23:26:42.0 +0200
+++ debian/java_defaults.mk 2018-12-29 23:11:51.998816128 +0100
@@ -7,10 +7,9 @@
alpha amd64 arm64 armel armhf i386 \
ia64 m68k mips mipsel mips64el \
powerpc ppc64 ppc64el \
-   riscv64 s390x sparc64 x32
+   riscv64 s390x sh4 sparc64 x32
 java10_architectures = $(java11_architectures) \
-   powerpcspe \
-   sh4
+   powerpcspe
 java9_architectures = $(java10_architectures)
 java8_architectures = $(java9_architectures) \
kfreebsd-amd64 kfreebsd-i386


Bug#917532: RFP: fava -- web interface for the Beancount accounting tool

2018-12-29 Thread Pierre-Elliott Bécue
Le dimanche 30 décembre 2018 à 01:24:23+0100, Pierre-Elliott Bécue a écrit :
> Le samedi 29 décembre 2018 à 21:26:50+0100, Stefano Zacchiroli a écrit :
> > On Sat, Dec 29, 2018 at 09:11:23PM +0100, Pierre-Elliott Bécue wrote:
> > > It's in new now. :)
> > 
> > Thanks! :-)
> 
> You're very welcome.
> 
> Let's go back to fava.
> 
> As any flask app, it could be served as a true website, but I'm not sure
> it's the actual goal of the software (there seem to be no auth and no
> security).
> 
> I think a webserver config + WSGI handling is quite overkill. Do you agree?

I uploaded a batch of fixes on the skeleton you had set up on salsa.

Cheers!

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature


Bug#916415: nocache broken with glibc 2.28: several programs just hang in call to futex(..., FUTEX_WAIT_PRIVATE, 2, NULL)

2018-12-29 Thread Aurelien Jarno
On 2018-12-23 01:14, Aurelien Jarno wrote:
> control: reassign -1 nocache
> control: tag -1 + patch
> 
> On 2018-12-14 07:44, Aurelien Jarno wrote:
> > control: forwarded -1 https://github.com/Feh/nocache/issues/34
> > 
> > On 2018-12-14 13:33, Paul Wise wrote:
> > > Package: nocache/1.0-1,libc6/2.28-2
> > > Severity: critical
> > > Justification: breaks unrelated software
> > > Usertags: hang
> > > 
> > > The upgrade from libc6 2.27-8 to 2.28-2 breaks nocache; some programs,
> > > when run under it (but not all of them), hang in a call to read/futex:
> > 
> > I haven't looked at it in details, but at least accorded to the upstream
> > bug, it seems to be an issue on the nocache side:
> > 
> > https://github.com/Feh/nocache/issues/34
> 
> There is now an upstream commit fixing the issue on the nocache side:
> 
> https://github.com/Feh/nocache/commit/e4e77a48528739188dccbdbd8b4d2d2d49aa0d99
> 

And a new upstream version 1.1 which includes this patch.

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


signature.asc
Description: PGP signature


Bug#917532: RFP: fava -- web interface for the Beancount accounting tool

2018-12-29 Thread Pierre-Elliott Bécue
Le samedi 29 décembre 2018 à 21:26:50+0100, Stefano Zacchiroli a écrit :
> On Sat, Dec 29, 2018 at 09:11:23PM +0100, Pierre-Elliott Bécue wrote:
> > It's in new now. :)
> 
> Thanks! :-)

You're very welcome.

Let's go back to fava.

As any flask app, it could be served as a true website, but I'm not sure
it's the actual goal of the software (there seem to be no auth and no
security).

I think a webserver config + WSGI handling is quite overkill. Do you agree?

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature


Bug#917719: libbio-tools-run-alignment-tcoffee-perl: FTBFS: dh_auto_test: make -j2 test TEST_VERBOSE=1 returned exit code 2

2018-12-29 Thread gregor herrmann
Control: reassign -1 t-coffee 12.00.7fb08c2-1
Control: forcemerge 917143  -1

On Sat, 29 Dec 2018 23:06:16 +0100, Lucas Nussbaum wrote:

> Source: libbio-tools-run-alignment-tcoffee-perl
> Version: 1.7.4-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: buster sid
> Usertags: ftbfs-20181229 ftbfs-buster
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

That's #917143 in t-coffee which affects libbio-tools-run-alignment-tcoffee-perl


Cheers,
gregor

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


signature.asc
Description: Digital Signature


Bug#872935: FTBFS: Could not locate puppetlabs/kitchensink/testutils__init.class or puppetlabs/kitchensink/testutils.clj on classpath.

2018-12-29 Thread Santiago Vila
On Tue, 22 Aug 2017, Hans Joachim Desserud wrote:

> Source: kitchensink-clojure
> Version: 2.3.0-1
> Severity: important
> 
> Dear Maintainer,
> 
> kitchensink-clojure currently fails to build from source with the
> following error message:
> 
> dh_auto_test
> (cd test && find . -name "*_test.clj" | \
>   xargs --verbose clojure -cp
> /build/kitchensink-clojure-2.3.0/kitchensink.jar:/usr/share/java/clojure.jar:/usr/share/java/tools.cli.jar:/usr/share/java/tools.logging.jar:/usr/share/java/clj-time.jar:/usr/share/java/raynes-fs.jar:/usr/share/java/slingshot.jar:/usr/share/java/cheshire.jar:/usr/share/java/ini4j.jar:/usr/share/java/dynapath.jar:/usr/share/java/clj-digest.jar)
> clojure -cp
> /build/kitchensink-clojure-2.3.0/kitchensink.jar:/usr/share/java/clojure.jar:/usr/share/java/tools.cli.jar:/usr/share/java/tools.logging.jar:/usr/share/java/clj-time.jar:/usr/share/java/raynes-fs.jar:/usr/share/java/slingshot.jar:/usr/share/java/cheshire.jar:/usr/share/java/ini4j.jar:/usr/share/java/dynapath.jar:/usr/share/java/clj-digest.jar
> ./puppetlabs/kitchensink/core_test.clj ./puppetlabs/kitchensink/json_test.clj
> ./puppetlabs/kitchensink/classpath_test.clj
> Exception in thread "main" java.io.FileNotFoundException: Could not locate
> puppetlabs/kitchensink/testutils__init.class or
> puppetlabs/kitchensink/testutils.clj on classpath.,
> compiling:(/build/kitchensink-clojure-2.3.0/test/./puppetlabs/kitchensink/core_test.clj:1:1)
>   at clojure.lang.Compiler.load(Compiler.java:7391)
>   at clojure.lang.Compiler.loadFile(Compiler.java:7317)
>   at clojure.main$load_script.invokeStatic(main.clj:275)
>   at clojure.main$load_script.invoke(main.clj:268)
>   at clojure.main$script_opt.invokeStatic(main.clj:337)
>   at clojure.main$script_opt.invoke(main.clj:330)
>   at clojure.main$main.invokeStatic(main.clj:421)
>   at clojure.main$main.doInvoke(main.clj:384)
>   at clojure.lang.RestFn.invoke(RestFn.java:436)
>   at clojure.lang.Var.invoke(Var.java:388)
>   at clojure.lang.AFn.applyToHelper(AFn.java:160)
>   at clojure.lang.Var.applyTo(Var.java:700)
>   at clojure.main.main(main.java:37)
> Caused by: java.io.FileNotFoundException: Could not locate
> puppetlabs/kitchensink/testutils__init.class or
> puppetlabs/kitchensink/testutils.clj on classpath.

This seems to be the same problem which happens in honeysql-clojure or 
ssl-utils-clojure.

There is a failed build log in reproducible-builds on armhf:

https://tests.reproducible-builds.org/debian/logs/buster/armhf/kitchensink-clojure_2.3.0-1.build2.log.gz

and I can reproduce it nearly 100% of the time on 1-XS instances (amd64) from 
Scaleway.

I hope Cyril can team-upload this one as well.

Thanks.



Bug#853858: 안녕하세요

2018-12-29 Thread lisa jaster
안녕하세요, 저는 Lisa Jaster입니다. 당신을 알게되어 대단히 기쁩니다.이 매체를 통해 연락하는 것을 허락 해 주시기 바랍니다. 저는 
매우 중요하고 기밀 사항이 있습니다. 제가 당신과상의하고 싶습니다. 친절하게 답장을 보내서 소개하겠습니다. 내 자신을 당신에게, 고마워,
관련
리사 재 스터.

Bug#917598: closed by Drew Parsons (Bug#917598: fixed in petsc4py 3.10.0-3)

2018-12-29 Thread peter green

Found 917598 3.10.0-3
thanks.

Unfortunately it seems it still fails with the same error.

On 29/12/18 20:21, Debian Bug Tracking System wrote:

This is an automatic notification regarding your Bug report
which was filed against the petsc4py package:

#917598: petsc4py FTBFS error: ‘SNESTEST’ undeclared

It has been closed by Drew Parsons .

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Drew Parsons 
 by
replying to this email.






Bug#917771: python-pywebview: Incomplete debian/copyright?

2018-12-29 Thread Chris Lamb
Source: python-pywebview
Version: 2.2.1+dfsg-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Jochen Sprickerhof , 
ftpmas...@debian.org

Hi,

I just ACCEPTed python-pywebview from NEW but noticed it was missing 
attribution in debian/copyright for at least examples/todos/README.

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.

(Please also clarify in debian/rules why you disable the testsuite
there.)


Regards,

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



Bug#917770: dump1090-mutability: user running dump1090-mutability service should be added to plugdev group

2018-12-29 Thread Pavel Kreuzt
Package: dump1090-mutability
Version: 1.15~20180310.4a16df3+dfsg-3
Severity: normal

Dear Maintainer,

selected user to run dump1090-mutability service is not added automatically to 
plugdev group, which causes permissions problems with rtl-sdr udev rules and 
prevents service start.

Versions of packages dump1090-mutability depends on:
ii  adduser   3.118
ii  cdebconf [debconf-2.0]0.245
ii  debconf [debconf-2.0] 1.5.69
ii  libc6 2.28-2
ii  libjs-excanvas0.r3-4
ii  libjs-jquery-ui   1.12.1+dfsg-5
ii  libjs-jquery-ui-theme-smoothness  1.12.1+dfsg-1
ii  librtlsdr00.6-1
ii  libusb-1.0-0  2:1.0.22-2
ii  lsb-base  10.2018112800

Versions of packages dump1090-mutability recommends:
ii  lighttpd  1.4.52-2
ii  python2.7.15-3

dump1090-mutability suggests no packages.

-- debconf information excluded



Bug#746204: gnome-terminal: -t/--title command line ignored

2018-12-29 Thread Vincent Lefevre
On 2015-01-19 21:06:22 +, Simon McVittie wrote:
> Control: tags 746204 + upstream wontfix
> 
> On Mon, 28 Apr 2014 at 11:03:33 +0900, Norbert Preining wrote:
> > since the step to 3.12 gnome-terminal ignores any
> > -t
> > --title
> > option.
> 
> This appears to be a deliberate upstream change: setting the title via
> configuration is no longer supported, because users complained that
> the title from menu configuration or the command-line ("static title")
> was in practice usually overwritten by the one set by the ESC]0;...\a
> escape sequence ("dynamic title"). This changed between 3.10 and 3.12.

Well, it seems that they have reverted the change since -t / --title
is currently working correctly: If I run

  gnome-terminal -t foo -- sleep 10

or

  gnome-terminal --title foo -- sleep 10

I get a window with the title "foo".

> The suggested solution is to use the escape sequence in your shell
> prompt (e.g. $PS1), or ensure that /etc/profile.d/vte-2.91.sh is
> sourced (it sets up a PROMPT_COMMAND suitable for gnome-terminal's
> terminal emulation library).

But one does not necessarily use a shell (see above), and this would
need a wrapper to start a shell in order to send the escape sequence
before running the command... So, it is great that the option is
working now.

And even when one uses a shell, having an initial title (before it
is changed by the shell) may be useful for the window manager, to
have different behaviors depending on this title.

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



Bug#917769: ITP: golang-github-tealeg-xlsx -- golang library for reading and writing XLSX files

2018-12-29 Thread Nobuhiro Iwamatsu
Package: wnpp
Severity: wishlist
Owner: Nobuhiro Iwamatsu 

* Package name: golang-github-tealeg-xlsx
  Version : 1.0.3+git20181024.dbf71b6-1
  Upstream Author : Geoffrey J. Teale
* URL : https://github.com/tealeg/xlsx
* License : BSD-3-clause
  Programming Lang: Go
  Description : golang library for reading and writing XLSX files
 
 golang-github-tealeg-xlsx is a library to simplify reading and writing the XML
 format used by recent version of Microsoft Excel in Go programs.



Bug#917692: [Pkg-electronics-devel] Bug#917692: sdcc: FTBFS: LaTeX Error: File `footnotehyper.sty' not found.

2018-12-29 Thread Jonathan McDowell
On Sat, Dec 29, 2018 at 10:39:07PM +0100, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
...
> > ! LaTeX Error: File `footnotehyper.sty' not found.
> > 
> > Type X to quit or  to proceed,
> > or enter new name. (Default extension: sty)
> > 
> > Enter file name: 
> > ! Emergency stop.
> >  
> >  
> > l.22 \usepackage
> > {amstext}^^M
> > No pages of output.
> > Transcript written on sdccman.log.
> > make[1]: *** [Makefile:67: sdccman.dvi] Error 1

Looks like lyx has changed again; we now need a build-dep on
texlive-latex-extra for this (lyx only recommends it).

J.

-- 
 No program done by a hacker will  |  .''`.  Debian GNU/Linux Developer
 work unless he is on the system.  | : :' :  Happy to accept PGP signed
   | `. `'   or encrypted mail - RSA
   |   `-key on the keyservers.



Bug#917768: [debian-refcard] bigger font for Spanish and French

2018-12-29 Thread Holger Wansing
Package: refcard
Tags: patch


There are three languages which have a smaller font size set: Bulgarian, 
Spanish 
and French. 
This has been set in the past in intend for sure, but these days it can be
reverted for Spanish and French without any disadvantage. 
It would lead to better readability.

Patch is attached.


Holger




-- 
Holger Wansing 
PGP-Finterprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076
diff --git a/dblatex.xsl b/dblatex.xsl
index c489d6e..2359679 100644
--- a/dblatex.xsl
+++ b/dblatex.xsl
@@ -83,7 +83,7 @@
 \newpages{
 
 2
-0
 1
 
diff --git a/preproc.xsl b/preproc.xsl
index 2565066..356f452 100644
--- a/preproc.xsl
+++ b/preproc.xsl
@@ -20,7 +20,7 @@
   
   
 	
-	  footnotesize
 	  small
 	


Bug#917752: lintian: FTBFS: tests failed

2018-12-29 Thread Chris Lamb
[Adding felix.lech...@lease-up.com to CC]

Hi Lucas,

Looks like we have a number of issues here.

> > +I: changes-upstream-signature-not-missing source: 
> > public-upstream-key-unusable upstream/signing-key.asc cannot be processed

Felix, not sure your MR/branch handles this one?

> > -W: debhelper-compat-experimental source: 
> > package-needs-versioned-debhelper-build-depends 12

I assume it addresses this one in an ongoing/sustainable manner.

> > -W: manpages-general: manpage-has-errors-from-man 
> > usr/share/man/man1/test.1p.gz 14: warning: macro `dep' not defined 
> > (possibly missing space after `de')

I don't recall seeing one for these.


Best wishes,

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



Bug#917767: gnome-terminal outputs debug messages when started from the command line

2018-12-29 Thread Vincent Lefevre
Package: gnome-terminal
Version: 3.30.2-2
Severity: minor
Tags: upstream
Forwarded: https://gitlab.gnome.org/GNOME/gnome-terminal/issues/42

When one starts gnome-terminal from the command line, it outputs
useless debug messages such as:

# watch_fast: "/org/gnome/terminal/legacy/" (establishing: 0, active: 0)
# unwatch_fast: "/org/gnome/terminal/legacy/" (active: 0, establishing: 1)
# watch_established: "/org/gnome/terminal/legacy/" (establishing: 0)

Not sure what has changed, but 2 weeks ago, I did not get such
messages.

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

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

Versions of packages gnome-terminal depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.12.12-1
ii  dbus-x11 [dbus-session-bus]   1.12.12-1
ii  dconf-gsettings-backend [gsettings-backend]   0.30.1-2
ii  gnome-terminal-data   3.30.2-2
ii  gsettings-desktop-schemas 3.28.1-1
ii  libatk1.0-0   2.30.0-2
ii  libc6 2.28-4
ii  libdconf1 0.30.1-2
ii  libglib2.0-0  2.58.1-2
ii  libgtk-3-03.24.2-3
ii  libpango-1.0-01.42.1-1
ii  libuuid1  2.33-0.2
ii  libvte-2.91-0 0.54.2-2
ii  libx11-6  2:1.6.7-1

Versions of packages gnome-terminal recommends:
ii  gvfs   1.38.1-2
ii  nautilus-extension-gnome-terminal  3.30.2-2
ii  yelp   3.30.0-2

gnome-terminal suggests no packages.

-- no debconf information



Bug#917654: bacula-doc: FTBFS (LaTeX Error: Missing begin{document})

2018-12-29 Thread Carsten Leonhardt
Control: merge 917654 917735

Hi,

I'm sorry for having used your time by not reporting this myself. As far
as I can say, one of the last TeX updates introduced this FTBFS. I have
yet to find the exact cause.

Regards,

Carsten



Bug#917516: anbox: does not pull binder or ashmem kernel drivers as dependency

2018-12-29 Thread Svetlana Tkachenko
You are right, with wmaker I don't have a desktop icon but the .desktop file 
gives me the command to run.

$ anbox launch --package=org.anbox.appmgr 
--component=org.anbox.appmgr.AppViewActivity
[ 2018-12-29 22:38:20] [launch.cpp:214@operator()] Session manager failed to 
become ready
$ journalctl -u anbox-container-manager.service
-- Logs begin at Wed 2018-12-26 10:59:10 AEDT, end at Sun 2018-12-30 10:13:28 A
дек 29 21:17:55 debians systemd[1]: Starting Anbox Container Manager...
дек 29 21:17:57 debians systemd[1]: Started Anbox Container Manager.
$ journalctl -u anbox-session-manager.service
-- Logs begin at Wed 2018-12-26 10:59:10 AEDT, end at Sun 2018-12-30 10:13:38 A
-- No entries --
$ 



Bug#917632: bugs.debian.org: During kernel boot the nvme module is not loaded, make the kernel not finding the rootfs

2018-12-29 Thread Don Armstrong
Control: reassign -1 linux-signed-amd64
Control: found -1 4.17.0-3

Just a note, bugs.debian.org is the package for reporting issues with
the bug tracking system itself, not general issues in packages (or the
kernel.)

I've reassigned this bug for you.

On Sat, 29 Dec 2018, Patrick Boettcher wrote:
> I did an apt upgrade this morning, I'm running testing/unstable. This updated
> my kernels to 4.17.0-3-amd64 and 4.19.0-1-amd64. I think the first since a few
> months (6 or more, but less then one year).

>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> 
> sudo apt update; sudo apt dist-upgrade
> 
>* What was the outcome of this action?
> 
> After rebooting to the new kernel booting stuck with some messages about mdadm
> looking for a RAID I don't have.
> 
> Ultimately the initramfs-shell came up and I found out that there are no 
> block-
> devices loaded. /dev/sda* and /dev/nvme* did not exists.
> 
> I manually modprobe'd nvme. Followed by CTRL-D and the boot continued.
> 
> 
> 
> -- System Information:
> Debian Release: buster/sid
>   APT prefers unstable
>   APT policy: (602, 'unstable'), (601, 'testing'), (600, 'stable'), (598, 
> 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.17.0-3-amd64 (SMP w/12 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=C.UTF-8 (charmap=locale: Cannot set LC_ALL 
> to default locale: No such file or directory
> UTF-8), LANGUAGE=en_US:en (charmap=locale: Cannot set LC_ALL to default 
> locale: No such file or directory
> UTF-8)
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
-- 
Don Armstrong  https://www.donarmstrong.com

When bad men combine, the good must associate; else they will fall one
by one, an unpitied sacrifice in a contemptible struggle.
 -- Edmund Burke "Thoughts on the Cause of Present Discontents"



Bug#917766: [debian-refcard] improve layout for some languages

2018-12-29 Thread Holger Wansing
Package: refcard
Tags: patch


The attached patch gives some improvement to the layout of the following 
languages: 
ca, de, eu, fi, gl, hu, it, nl, pl, pt, ro, uk.
In concrete, that means: 
The copyright notice is moved to the bottom of the middle column of page 1,
as it is for English (taking English as reference).


Holger




-- 
Holger Wansing 
PGP-Finterprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076
diff --git a/dblatex.xsl b/dblatex.xsl
index c489d6e..1198d97 100644
--- a/dblatex.xsl
+++ b/dblatex.xsl
@@ -82,8 +82,8 @@
 
 \newpages{
 
-2
-2
+0
 1
 


Bug#917750: node-redis: FTBFS: tests failed

2018-12-29 Thread Lucas Nussbaum
Source: node-redis
Version: 0.12.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> NODE_DISABLE_COLORS=1 nodejs test.js
> [redis-server] 31493:C 29 Dec 2018 13:29:06.704 # oO0OoO0OoO0Oo Redis is 
> starting oO0OoO0OoO0Oo
> 31493:C 29 Dec 2018 13:29:06.704 # Redis version=5.0.3, bits=64, 
> commit=, modified=0, pid=31493, just started
> 31493:C 29 Dec 2018 13:29:06.704 # Configuration loaded
> 31493:M 29 Dec 2018 13:29:06.705 * Running mode=standalone, port=6379.
> 31493:M 29 Dec 2018 13:29:06.705 # WARNING: The TCP backlog setting of 511 
> cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower 
> value of 128.
> 31493:M 29 Dec 2018 13:29:06.705 # Server initialized
> 31493:M 29 Dec 2018 13:29:06.705 # WARNING overcommit_memory is set to 0! 
> Background save may fail under low memory condition. To fix this issue add 
> 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the 
> command 'sysctl vm.overcommit_memory=1' for this to take effect.
> 31493:M 29 Dec 2018 13:29:06.705 # WARNING you have Transparent Huge Pages 
> (THP) support enabled in your kernel. This will create latency and memory 
> usage issues with Redis. To fix this issue run the command 'echo never > 
> /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your 
> /etc/rc.local in order to retain the setting after a reboot. Redis must be 
> restarted after THP is disabled.
> 31493:M 29 Dec 2018 13:29:06.705 * Ready to accept connections
> 31493:M 29 Dec 2018 13:29:06.705 * The server is now ready to accept 
> connections at /tmp/redis.sock
> 
> Connected to 127.0.0.1:6379, Redis server version 5.0.3
> 
> Using reply parser javascript
> - ipv4:(node:31487) [DEP0026] DeprecationWarning: util.print is deprecated. 
> Use console.log instead.
> Connected to 127.0.0.1:6379, Redis server version 5.0.3
> 
> Using reply parser javascript
> - ipv6:Connected to ::1:6379, Redis server version 5.0.3
> 
> Using reply parser javascript
> - unix_socket:Connected to /tmp/redis.sock, Redis server version 5.0.3
> 
> Using reply parser javascript
> - flushdb: 1 ms
> - incr: 0 ms
> - multi_1: 2 ms
> - multi_2: 0 ms
> - multi_3: 1 ms
> - multi_4: 0 ms
> - multi_5: 1 ms
> - multi_6: 0 ms
> - multi_7: 1 ms
> - multi_exception_1: 1 ms
> - multi_8: 1 ms
> - fwd_errors_1:incoming
>  151 ms
> - eval_1: 5 ms
> - script_load: 0 ms
> - client_list:id=3 addr=127.0.0.1:56828 fd=9 name= age=0 idle=0 flags=N db=15 
> sub=0 psub=0 multi=-1 qbuf=0 qbuf-free=32768 obl=0 oll=0 omem=0 events=r 
> cmd=exec
> id=4 addr=127.0.0.1:56830 fd=10 name= age=0 idle=0 flags=N db=15 sub=0 psub=0 
> multi=-1 qbuf=0 qbuf-free=0 obl=0 oll=0 omem=0 events=r cmd=select
> id=5 addr=127.0.0.1:56832 fd=11 name= age=0 idle=0 flags=P db=15 sub=1 psub=0 
> multi=-1 qbuf=0 qbuf-free=0 obl=0 oll=0 omem=0 events=r cmd=subscribe
> id=6 addr=127.0.0.1:56834 fd=12 name= age=0 idle=0 flags=N db=0 sub=0 psub=0 
> multi=-1 qbuf=26 qbuf-free=32742 obl=0 oll=0 omem=0 events=r cmd=client
> 
> id=3 addr=127.0.0.1:56828 fd=9 name= age=0 idle=0 flags=x db=15 sub=0 psub=0 
> multi=1 qbuf=14 qbuf-free=32754 obl=4 oll=0 omem=0 events=r cmd=exec
> id=4 addr=127.0.0.1:56830 fd=10 name= age=0 idle=0 flags=N db=15 sub=0 psub=0 
> multi=-1 qbuf=0 qbuf-free=0 obl=0 oll=0 omem=0 events=r cmd=select
> id=5 addr=127.0.0.1:56832 fd=11 name= age=0 idle=0 flags=P db=15 sub=1 psub=0 
> multi=-1 qbuf=0 qbuf-free=0 obl=0 oll=0 omem=0 events=r cmd=subscribe
> id=6 addr=127.0.0.1:56834 fd=12 name= age=0 idle=0 flags=N db=0 sub=0 psub=0 
> multi=-1 qbuf=0 qbuf-free=32768 obl=0 oll=0 omem=0 events=r cmd=client
> 
> id=3 addr=127.0.0.1:56828 fd=9 name= age=0 idle=0 flags=x db=15 sub=0 psub=0 
> multi=1 qbuf=55 qbuf-free=32713 obl=18 oll=0 omem=0 events=r cmd=exec
> id=4 addr=127.0.0.1:56830 fd=10 name= age=0 idle=0 flags=N db=15 sub=0 psub=0 
> multi=-1 qbuf=0 qbuf-free=0 obl=0 oll=0 omem=0 events=r cmd=select
> id=5 addr=127.0.0.1:56832 fd=11 name= age=0 idle=0 flags=P db=15 sub=1 psub=0 
> multi=-1 qbuf=0 qbuf-free=0 obl=0 oll=0 omem=0 events=r cmd=subscribe
> id=6 addr=127.0.0.1:56834 fd=12 name= age=0 idle=0 flags=N db=0 sub=0 psub=0 
> multi=-1 qbuf=0 qbuf-free=32768 obl=0 oll=0 omem=0 events=r cmd=client
> 
>  1 ms
> - watch_multi: 0 ms
> - watch_transaction: 0 ms
> - detect_buffers: 2 ms
> - socket_nodelay: 2 ms
> - reconnect:reconnecting: { delay: 255, attempt: 2 }
>  257 ms
> - reconnect_select_db_after_pubsub:reconnecting: { delay: 255, attempt

Bug#917749: python-periodictable: FTBFS: Could not import extension matplotlib.sphinxext.only_directives (exception: No module named 'matplotlib.sphinxext.only_directives')

2018-12-29 Thread Lucas Nussbaum
Source: python-periodictable
Version: 1.5.0-6
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:217: /usr/bin/python setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable
> copying periodictable/activation.py -> 
> /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable
> copying periodictable/fasta.py -> 
> /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable
> copying periodictable/plot.py -> 
> /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable
> copying periodictable/mass.py -> 
> /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable
> copying periodictable/cromermann.py -> 
> /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable
> copying periodictable/covalent_radius.py -> 
> /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable
> copying periodictable/__init__.py -> 
> /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable
> copying periodictable/core.py -> 
> /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable
> copying periodictable/crystal_structure.py -> 
> /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable
> copying periodictable/constants.py -> 
> /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable
> copying periodictable/util.py -> 
> /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable
> copying periodictable/density.py -> 
> /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable
> copying periodictable/chemicals.py -> 
> /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable
> copying periodictable/magnetic_ff.py -> 
> /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable
> copying periodictable/formulas.py -> 
> /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable
> copying periodictable/nsf.py -> 
> /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable
> copying periodictable/xsf.py -> 
> /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable
> running egg_info
> creating periodictable.egg-info
> writing requirements to periodictable.egg-info/requires.txt
> writing periodictable.egg-info/PKG-INFO
> writing top-level names to periodictable.egg-info/top_level.txt
> writing dependency_links to periodictable.egg-info/dependency_links.txt
> writing manifest file 'periodictable.egg-info/SOURCES.txt'
> reading manifest file 'periodictable.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching 'doc'
> no previously-included directories found matching 'doc/sphinx/_build'
> no previously-included directories found matching 'doc/sphinx/build'
> warning: no previously-included files found matching 'build'
> warning: no previously-included files found matching 'dist'
> warning: no previously-included files found matching '*.pyc'
> writing manifest file 'periodictable.egg-info/SOURCES.txt'
> copying periodictable/activation.dat -> 
> /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable
> creating 
> /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable/xsf
> copying periodictable/xsf/ac.nff -> 
> /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable/xsf
> copying periodictable/xsf/ag.nff -> 
> /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable/xsf
> copying periodictable/xsf/al.nff -> 
> /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable/xsf
> copying periodictable/xsf/ar.nff -> 
> /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable/xsf
> copying periodictable/xsf/as.nff -> 
> /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable/xsf
> copying periodictable/xsf/at.nff -> 
> /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable/xsf
> copying periodictable/xsf/au.nff -> 
> /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable/xsf
> copying periodictable/xsf/b.nff -> 
> /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable/xsf
> copying periodictable/xsf/ba.nff -> 
> /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable/xsf
> copying periodictable/xsf/be.nff -> 
> /<>/.pybuild/cpython2_2.7_periodictable/build/periodictable/xsf
> copying periodictable/xsf/bi.nff -&

Bug#917752: lintian: FTBFS: tests failed

2018-12-29 Thread Lucas Nussbaum
Source: lintian
Version: 2.5.118
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
>  running tests 
> mkdir -p "/<>/debian/test-out"
> t/runtests -k -j 2 t "/<>/debian/test-out" 
> Host architecture is amd64.
> Latest policy version is 4.3.0 from Sun, 23 Dec 2018 10:17:55 +
> 
> Environment:
> DEB_HOST_ARCH=amd64
> DUMP_LOGS=yes
> HARNESS_EPOCH=1545583328
> IPCRUNDEBUG=none
> LC_ALL=C
> LINTIAN_DPLINT_FRONTEND=/<>/frontend/dplint
> LINTIAN_FRONTEND=/<>/frontend/lintian
> LINTIAN_ROOT=/<>
> LINTIAN_TEST_INSTALLED=no
> LINTIAN_TEST_ROOT=/<>
> NO_PKG_MANGLE=true
> 
> PATH=/<>/t/helpers/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> POLICY_EPOCH=1545560275
> POLICY_VERSION=4.3.0
> 
> Test scripts:
> /<>/t/scripts/01-critic/checks.t ... 
> skipped: Only UNRELEASED versions are criticised
> /<>/t/scripts/01-critic/collection.t ... 
> skipped: Only UNRELEASED versions are criticised
> /<>/t/scripts/01-critic/commands.t . 
> skipped: Only UNRELEASED versions are criticised
> /<>/t/scripts/01-critic/docs-examples.t  
> skipped: Only UNRELEASED versions are criticised
> /<>/t/scripts/01-critic/frontend.t . 
> skipped: Only UNRELEASED versions are criticised
> /<>/t/scripts/01-critic/helpers.t .. 
> skipped: Only UNRELEASED versions are criticised
> /<>/t/scripts/01-critic/lib.t .. 
> skipped: Only UNRELEASED versions are criticised
> /<>/t/scripts/01-critic/private.t .. 
> skipped: Only UNRELEASED versions are criticised
> /<>/t/scripts/01-critic/test-scripts.t . 
> skipped: Only UNRELEASED versions are criticised
> /<>/t/scripts/02-minimum-version/collection.t .. ok
> /<>/t/scripts/02-minimum-version/commands.t  ok
> /<>/t/scripts/02-minimum-version/docs-examples.t ... ok
> /<>/t/scripts/02-minimum-version/frontend.t  ok
> /<>/t/scripts/02-minimum-version/helpers.t . ok
> /<>/t/scripts/02-minimum-version/checks.t .. ok
> /<>/t/scripts/02-minimum-version/lib.t . ok
> /<>/t/scripts/02-minimum-version/private.t . ok
> /<>/t/scripts/02-minimum-version/test-scripts.t  ok
> /<>/t/scripts/03-strict/collection.t ... ok
> /<>/t/scripts/03-strict/commands.t . ok
> /<>/t/scripts/03-strict/docs-examples.t  ok
> /<>/t/scripts/03-strict/frontend.t . ok
> /<>/t/scripts/03-strict/helpers.t .. ok
> /<>/t/scripts/03-strict/checks.t ... ok
> /<>/t/scripts/03-strict/private.t .. ok
> /<>/t/scripts/03-strict/lib.t .. ok
> /<>/t/scripts/Lintian/DepMap/01add-select-satisfy.t  ok
> /<>/t/scripts/Lintian/DepMap/03pending.t ... ok
> /<>/t/scripts/Lintian/DepMap/04satisfiability.t  ok
> /<>/t/scripts/Lintian/DepMap/05multi-add.t . ok
> /<>/t/scripts/Lintian/DepMap/06parents.t ... ok
> /<>/t/scripts/Lintian/DepMap/08initialise.t  ok
> /<>/t/scripts/Lintian/DepMap/08initialise2.t ... ok
> /<>/t/scripts/Lintian/DepMap/09unlink.t  ok
> /<>/t/scripts/Lintian/DepMap/10circular.t .. ok
> /<>/t/scripts/Lintian/DepMap/11prefix.t  ok
> /<>/t/scripts/Lintian/DepMap/12done.t .. ok
> /<>/t/scripts/Lintian/DepMap/Properties/00construct.t .. ok
> /<>/t/scripts/Lintian/Lab/Manifest/01-basic.t .. ok
> /<>/t/scripts/Lintian/Lab/Manifest/02-io.t . ok
> /<>/t/scripts/Lintian/Lab/Manifest/03-diff.t ... ok
> /<>/t/scripts/Lintian/Lab/auto-repair.t  ok
> /<>/t/scripts/Lintian/Lab/repair.t . ok
> /<>/t/scripts/Lintian/Relation/01-basic.t .. ok
> /<>/t/scripts/Lintian/Relation/02-architecture.t ... ok
> /<>/t/scripts/Lintian/Relation/03-duplicates.t . ok
> /<>/t/scripts/Lintian/Relation/04-multiarch.t .. ok
> /<>/t/scripts/Lintian

Bug#917762: python-xarray: FTBFS: tests failed

2018-12-29 Thread Lucas Nussbaum
Source: python-xarray
Version: 0.11.0-3
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> for p in python3.7; do \
>   PY3VERNUM=`echo $p | sed -e 's/python//' `; \
>   pybuild --test --test-pytest -i $p -p $PY3VERNUM  ;  \
>   done
> I: pybuild base:217: cd /<>/.pybuild/cpython3_3.7_xarray/build; 
> python3.7 -m pytest 
> = test session starts 
> ==
> platform linux -- Python 3.7.2rc1, pytest-3.10.1, py-1.7.0, pluggy-0.8.0
> rootdir: /<>, inifile: setup.cfg
> collected 6537 items / 1 skipped
> 
> xarray/tests/test_accessors.py . [  
> 0%]
> ..   [  
> 1%]
> xarray/tests/test_backends.py .. [  
> 2%]
>  [  
> 3%]
> ..ss [  
> 4%]
>  [  
> 5%]
>  [  
> 6%]
> ..ss [  
> 7%]
>  [  
> 8%]
> ..X. [  
> 9%]
> sss. [ 
> 11%]
> .... [ 
> 12%]
> ..ss [ 
> 13%]
> ...s..   [ 
> 13%]
> xarray/tests/test_backends_api.py .  [ 
> 14%]
> xarray/tests/test_backends_file_manager.py . [ 
> 14%]
> xarray/tests/test_backends_locks.py .[ 
> 14%]
> xarray/tests/test_backends_lru_cache.py  [ 
> 14%]
> xarray/tests/test_cftime_offsets.py  [ 
> 15%]
>  [ 
> 16%]
>  [ 
> 17%]
>  [ 
> 18%]
>  [ 
> 19%]
>  [ 
> 20%]
>  [ 
> 21%]
>  [ 
> 22%]
>  [ 
> 23%]
>  [ 
> 24%]
>  [ 
> 26%]
>  [ 
> 27%]
>  [ 
> 28%]
>  [ 
> 29%]
>  [ 
> 30%]
>  [ 
> 31%]
>  [ 
> 32%]
>  [ 
> 33%]
>  [ 
> 34%]
>  [ 
> 35%]
> .[ 
> 36%]
> xarray/tests/test_cftimeindex.py ... [ 
> 37%]
>  [ 
> 38%]
>  [ 
> 39%]
>  [ 
> 40%]
>  [ 
> 41%]
>  [ 
> 43%]
> .

Bug#917754: statsmodels: FTBFS: Could not import extension matplotlib.sphinxext.only_directives (exception: No module named 'matplotlib.sphinxext.only_directives')

2018-12-29 Thread Lucas Nussbaum
Source: statsmodels
Version: 0.8.0-7
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>/docs'
> Make static directory for images
> mkdir -p build/html/_static
> # generate the examples rst files
> Generating reST from examples folder
> #../tools/examples_rst.py
> Generating datasets from installed statsmodels.datasets
> python3 ../tools/dataset_rst.py
> /<>/.pybuild/cpython3_3.7_statsmodels/build/statsmodels/compat/pandas.py:56:
>  FutureWarning: The pandas.core.datetools module is deprecated and will be 
> removed in a future version. Please use the pandas.tseries module instead.
>   from pandas.core import datetools
> Generating notebooks from examples/notebooks folder
> python3 ../tools/nbgenerate.py --execute=True --allow_errors=True
> RUNNING THE L-BFGS-B CODE
> 
>* * *
> 
> Machine precision = 2.220D-16
>  N =4 M =   10
>  This problem is unconstrained.
> 
> At X0 0 variables are exactly at the bounds
> 
> At iterate0f=  4.23082D+00|proj g|=  4.24640D-03
> 
> At iterate5f=  4.23081D+00|proj g|=  4.05724D-04
> 
> At iterate   10f=  4.23081D+00|proj g|=  1.30108D-04
> 
> At iterate   15f=  4.23080D+00|proj g|=  1.31695D-03
> 
>* * *
> 
> Tit   = total number of iterations
> Tnf   = total number of function evaluations
> Tnint = total number of segments explored during Cauchy searches
> Skip  = number of BFGS updates skipped
> Nact  = number of active bounds at final generalized Cauchy point
> Projg = norm of the final projected gradient
> F = final function value
> 
>* * *
> 
>NTit Tnf  Tnint  Skip  Nact ProjgF
> 4 19 23  1 0 0   3.347D-06   4.231D+00
>   F =   4.2308031361514127 
> 
> CONVERGENCE: NORM_OF_PROJECTED_GRADIENT_<=_PGTOL
> 
>  Cauchytime 0.000E+00 seconds.
>  Subspace minimization time 0.000E+00 seconds.
>  Line search   time 0.000E+00 seconds.
> 
>  Total User time 0.000E+00 seconds.
> 
> RUNNING THE L-BFGS-B CODE
> 
>* * *
> 
> Machine precision = 2.220D-16
>  N =5 M =   10
>  This problem is unconstrained.
> 
> At X0 0 variables are exactly at the bounds
> 
> At iterate0f=  4.22237D+00|proj g|=  5.01920D-03
> 
> At iterate5f=  4.22236D+00|proj g|=  2.92744D-04
> 
> At iterate   10f=  4.22235D+00|proj g|=  2.35973D-04
> 
> At iterate   15f=  4.22234D+00|proj g|=  1.81119D-03
> 
> At iterate   20f=  4.22234D+00|proj g|=  4.50080D-05
> 
>* * *
> 
> Tit   = total number of iterations
> Tnf   = total number of function evaluations
> Tnint = total number of segments explored during Cauchy searches
> Skip  = number of BFGS updates skipped
> Nact  = number of active bounds at final generalized Cauchy point
> Projg = norm of the final projected gradient
> F = final function value
> 
>* * *
> 
>NTit Tnf  Tnint  Skip  Nact ProjgF
> 5 20 23  1 0 0   4.501D-05   4.222D+00
>   F =   4.2223359703293983 
> 
> CONVERGENCE: REL_REDUCTION_OF_F_<=_FACTR*EPSMCH 
> 
>  Cauchytime 0.000E+00 seconds.
>  Subspace minimization time 0.000E+00 seconds.
>  Line search   time 0.000E+00 seconds.
> 
>  Total User time 0.000E+00 seconds.
> 
> RUNNING THE L-BFGS-B CODE
> 
>* * *
> 
> Machine precision = 2.220D-16
>  N =3 M =   12
>  This problem is unconstrained.
> 
> At X0 0 variables are exactly at the bounds
> 
> At iterate0f=  4.23082D+00|proj g|=  8.41904D-04
> 
> At iterate5f=  4.23082D+00|proj g|=  2.53486D-04
> 
> At iterate   10f=  4.23080D+00|proj g|=  3.19123D-04
> 
> At iterate   15f=  4.23080D+00|proj g|=  0.0D+00
> 
>* * *
> 
> Tit   = total number of iterations
> Tnf   = total number of function evaluations
> Tnint = total number of segments explored during Cauchy searches
> Skip  = number of BFGS updates skipped
> Nact  = number of active bounds at final generalized Cauchy point
> Projg = norm of the final projected gradient
> F = final function value
> 
>* * *
> 
>NTit Tnf  Tnint  Skip  Nact ProjgF
> 3 15 19  1 0 0   0.

Bug#917764: postgresql-11: FTBFS: pg_regress: initdb failed

2018-12-29 Thread Lucas Nussbaum
Source: postgresql-11
Version: 11.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/<>/build/contrib/spi'
> make[3]: Nothing to be done for 'all'.
> make[3]: Leaving directory '/<>/build/contrib/spi'
> rm -rf ./testtablespace
> mkdir ./testtablespace
> PATH="/<>/build/tmp_install/usr/lib/postgresql/11/bin:$PATH" 
> LD_LIBRARY_PATH="/<>/build/tmp_install/usr/lib/x86_64-linux-gnu" 
> ../../../src/test/regress/pg_regress --temp-instance=./tmp_check 
> --inputdir=/<>/build/../src/test/regress --bindir=
> --port=10015 --dlpath=. --max-concurrent-tests=20 --port=10015 
> --schedule=/<>/build/../src/test/regress/parallel_schedule  
> == creating temporary instance==
> == initializing database system   ==
> 
> pg_regress: initdb failed
> Examine /<>/build/src/test/regress/log/initdb.log for the reason.
> Command was: "initdb" -D 
> "/<>/build/src/test/regress/./tmp_check/data" --no-clean 
> --no-sync > "/<>/build/src/test/regress/log/initdb.log" 2>&1
> make[2]: *** [GNUmakefile:132: check] Error 2

The full build log is available from:
   http://aws-logs.debian.net/2018/12/29/postgresql-11_11.1-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



Bug#917758: jabberd2: FTBFS: mysql-related errors

2018-12-29 Thread Lucas Nussbaum
Source: jabberd2
Version: 2.6.1-3
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/<>/storage'
> /bin/bash ../libtool --quiet  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H 
> -I. -I..  -DLIBRARY_DIR=\"/usr/lib/x86_64-linux-gnu/jabberd2\" -Wdate-time 
> -D_FORTIFY_SOURCE=2 -I../c2s -I.. -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -funsigned-char -fdiagnostics-color -c -o 
> libstorage_la-storage.lo `test -f 'storage.c' || echo './'`storage.c
> /bin/bash ../libtool --quiet  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H 
> -I. -I..  -DLIBRARY_DIR=\"/usr/lib/x86_64-linux-gnu/jabberd2\" -Wdate-time 
> -D_FORTIFY_SOURCE=2 -I../c2s -I.. -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -funsigned-char -fdiagnostics-color -c -o 
> libstorage_la-object.lo `test -f 'object.c' || echo './'`object.c
> /bin/bash ../libtool --quiet  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H 
> -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -I../c2s -I.. -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -funsigned-char -fdiagnostics-color -c -o 
> authreg_anon.lo authreg_anon.c
> /bin/bash ../libtool --quiet  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H 
> -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -I../c2s -I.. -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -funsigned-char -fdiagnostics-color -c -o 
> authreg_db.lo authreg_db.c
> /bin/bash ../libtool --quiet  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H 
> -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -I../c2s -I.. -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -funsigned-char -fdiagnostics-color -c -o 
> storage_db.lo storage_db.c
> /bin/bash ../libtool --quiet  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H 
> -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -I../c2s -I.. -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -funsigned-char -fdiagnostics-color -c -o 
> storage_fs.lo storage_fs.c
> storage_fs.c: In function '_st_fs_put':
> storage_fs.c:173:64: warning: cast from 
> pointer to integer of different size [-Wpointer-to-int-cast]
>  fprintf(f, "%s %d %d\n", key, ot, 
> ((int)val != 0) ? 1 : 0);
> 
> ^
> storage_fs.c:177:63: warning: cast from 
> pointer to integer of different size [-Wpointer-to-int-cast]
>  fprintf(f, "%s %d %d\n", key, ot, 
> (int) val);
>
> ^
> storage_fs.c: In function '_st_fs_delete':
> storage_fs.c:383:34: warning: 
> '%s' directive output may be truncated writing up to 255 
> bytes into a region of size between 0 and 1023 
> [-Wformat-truncation=]
>  snprintf(file, 1024, "%s/%s", path, dirent->d_name);
>   ^~
> In file included from /usr/include/stdio.h:873,
>  from ../util/util.h:27,
>  from storage.h:38,
>  from storage_fs.c:36:
> /usr/include/x86_64-linux-gnu/bits/stdio2.h:67:10: 
> note: '__builtin___snprintf_chk' output 
> between 2 and 1280 bytes into a destination of size 1024
>return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL 
> - 1,
>   
> ^~~~
>     __bos (__s), __fmt, __va_arg_pack ());
> ~
> /bin/bash ../libtool --quiet  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H 
> -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -I../c2s -I.. -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -funsigned-char -fdiagnostics-color -c -o 
> authr

Bug#917763: hoel: FTBFS: dh_auto_configure fails

2018-12-29 Thread Lucas Nussbaum
Source: hoel
Version: 1.4.8-2
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/<>/build/CMakeFiles/CMakeTmp'
> Building C object CMakeFiles/cmTC_2220a.dir/CheckSymbolExists.c.o
> /usr/bin/cc   -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wall -Werror-o 
> CMakeFiles/cmTC_2220a.dir/CheckSymbolExists.c.o   -c 
> /<>/build/CMakeFiles/CMakeTmp/CheckSymbolExists.c
> Linking C executable cmTC_2220a
> /usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_2220a.dir/link.txt 
> --verbose=1
> /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wall -Werror   -Wl,-z,relro -Wl,-z,now  
> CMakeFiles/cmTC_2220a.dir/CheckSymbolExists.c.o  -o cmTC_2220a 
> make[3]: Leaving directory '/<>/build/CMakeFiles/CMakeTmp'
> make[2]: Leaving directory '/<>/build/CMakeFiles/CMakeTmp'
> 
> File /<>/build/CMakeFiles/CMakeTmp/CheckSymbolExists.c:
> /* */
> #include 
> 
> int main(int argc, char** argv)
> {
>   (void)argv;
> #ifndef __GNU_LIBRARY__
>   return ((int*)(&__GNU_LIBRARY__))[argc];
> #else
>   (void)argc;
>   return 0;
> #endif
> }
> 
> dh_auto_configure: cd build && cmake -DCMAKE_INSTALL_PREFIX=/usr 
> -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
> -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
> -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
> "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
> -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu --no-warn-unused-cli .. returned 
> exit code 1
> make[1]: *** [debian/rules:24: override_dh_auto_configure] Error 2

The full build log is available from:
   http://aws-logs.debian.net/2018/12/29/hoel_1.4.8-2_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



Bug#917755: phpmyadmin: FTBFS: PHP Fatal error: Uncaught Error: Class 'PHPUnit_Framework_TestCase' not found in /<>/test/PMATestCase.php:14

2018-12-29 Thread Lucas Nussbaum
Source: phpmyadmin
Version: 4:4.6.6-5
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # We exclude:
> # - selenium tests as the setup would be too complex
> # - some network based tests
> LC_ALL=en_US.UTF-8 phpunit --config phpunit.xml.nocoverage --exclude-group 
> selenium --exclude-group network
> No headers testing.
> Please install runkit and enable runkit.internal_override!
> PHP Fatal error:  Uncaught Error: Class 'PHPUnit_Framework_TestCase' not 
> found in /<>/test/PMATestCase.php:14
> Stack trace:
> #0 /<>/test/classes/AdvisorTest.php(13): require_once()
> #1 /usr/share/php/PHPUnit/Util/FileLoader.php(57): 
> include_once('/build/phpmyadm...')
> #2 /usr/share/php/PHPUnit/Util/FileLoader.php(45): 
> PHPUnit\Util\FileLoader::load('/build/phpmyadm...')
> #3 /usr/share/php/PHPUnit/Framework/TestSuite.php(540): 
> PHPUnit\Util\FileLoader::checkAndLoad('/build/phpmyadm...')
> #4 /usr/share/php/PHPUnit/Framework/TestSuite.php(618): 
> PHPUnit\Framework\TestSuite->addTestFile('/build/phpmyadm...')
> #5 /usr/share/php/PHPUnit/Util/Configuration.php(1137): 
> PHPUnit\Framework\TestSuite->addTestFiles(Array)
> #6 /usr/share/php/PHPUnit/Util/Configuration.php(1003): 
> PHPUnit\Util\Configuration->getTestSuite(Object(DOMElement), Array)
> #7 /usr/share/php/PHPUnit/TextUI/Command.php(902): 
> PHPUnit\Util\Configuration->getTestSuiteConfiguration('')
> #8 /usr/share/php/PHPUnit in /<>/test/PMATestCase.php on line 14
> make[1]: *** [debian/rules:14: override_dh_auto_test] Error 255

The full build log is available from:
   http://aws-logs.debian.net/2018/12/29/phpmyadmin_4.6.6-5_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



Bug#917760: php-zeta-console-tools: FTBFS: PHP Fatal error: Uncaught Error: Class 'PHPUnit_Framework_TestCase' not found in /usr/share/php/ezc/UnitTest/test/case.php:33

2018-12-29 Thread Lucas Nussbaum
Source: php-zeta-console-tools
Version: 1.7-3
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> phpunit --exclude-group interactive
> PHP Fatal error:  Uncaught Error: Class 'PHPUnit_Framework_TestCase' not 
> found in /usr/share/php/ezc/UnitTest/test/case.php:33
> Stack trace:
> #0 /usr/share/php/ezc/UnitTest/autoload.php(19): require()
> #1 [internal function]: PHPUnit\Util\FileLoader::{closure}('ezcTestCase')
> #2 /<>/tests/argument_test.php(34): 
> spl_autoload_call('ezcTestCase')
> #3 /usr/share/php/PHPUnit/Util/FileLoader.php(57): 
> include_once('/build/php-zeta...')
> #4 /usr/share/php/PHPUnit/Util/FileLoader.php(45): 
> PHPUnit\Util\FileLoader::load('/build/php-zeta...')
> #5 /usr/share/php/PHPUnit/Framework/TestSuite.php(540): 
> PHPUnit\Util\FileLoader::checkAndLoad('/build/php-zeta...')
> #6 /usr/share/php/PHPUnit/Framework/TestSuite.php(618): 
> PHPUnit\Framework\TestSuite->addTestFile('/build/php-zeta...')
> #7 /usr/share/php/PHPUnit/Util/Configuration.php(1137): 
> PHPUnit\Framework\TestSuite->addTestFiles(Array)
> #8 /usr/share/php/PHPUnit/Util/Configuration.php(996): 
> PHPUnit\Util\Configuration->getTestSuite(Object(DOMEleme in 
> /usr/share/php/ezc/UnitTest/test/case.php on line 33
> make[1]: *** [debian/rules:20: override_dh_auto_test] Error 255

The full build log is available from:
   
http://aws-logs.debian.net/2018/12/29/php-zeta-console-tools_1.7-3_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



Bug#917759: openhft-chronicle-wire: FTBFS: Could not resolve dependencies for project net.openhft:chronicle-wire:bundle:1.1.13

2018-12-29 Thread Lucas Nussbaum
Source: openhft-chronicle-wire
Version: 1.1.13-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=maven
>dh_update_autotools_config -O--buildsystem=maven
>dh_auto_configure -O--buildsystem=maven
>   mh_patchpoms -plibopenhft-chronicle-wire-java --debian-build 
> --keep-pom-version --maven-repo=/<>/debian/maven-repo
>dh_auto_build -O--buildsystem=maven
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
> -DskipTests -Dnotimestamp=true -Dlocale=en_US
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by 
> com.google.inject.internal.cglib.core.$ReflectUtils$1 
> (file:/usr/share/maven/lib/guice.jar) to method 
> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
> WARNING: Please consider reporting this to the maintainers of 
> com.google.inject.internal.cglib.core.$ReflectUtils$1
> WARNING: Use --illegal-access=warn to enable warnings of further illegal 
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> [INFO] Scanning for projects...
> [INFO] 
> [INFO] -< net.openhft:chronicle-wire 
> >-
> [INFO] Building OpenHFT/Chronicle-Wire 1.1.13
> [INFO] ---[ bundle 
> ]---
> [WARNING] The POM for org.easymock:easymock:jar:debian is missing, no 
> dependency information available
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  1.064 s
> [INFO] Finished at: 2018-12-29T13:59:39Z
> [INFO] 
> 
> [ERROR] Failed to execute goal on project chronicle-wire: Could not resolve 
> dependencies for project net.openhft:chronicle-wire:bundle:1.1.13: Cannot 
> access central (https://repo.maven.apache.org/maven2) in offline mode and the 
> artifact org.easymock:easymock:jar:debian has not been downloaded from it 
> before. -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
> dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
> -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1
> make: *** [debian/rules:4: build] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/2018/12/29/openhft-chronicle-wire_1.1.13-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



Bug#917751: ccdproc: FTBFS: tests failed

2018-12-29 Thread Lucas Nussbaum
Source: ccdproc
Version: 1.3.0-4
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> py3versions: no X-Python3-Version in control file, using supported versions
> python3.7 setup.py test -vv --args -v
> running test
> running install
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/ccdproc
> copying ccdproc/log_meta.py -> build/lib/ccdproc
> copying ccdproc/__init__.py -> build/lib/ccdproc
> copying ccdproc/core.py -> build/lib/ccdproc
> copying ccdproc/ccddata.py -> build/lib/ccdproc
> copying ccdproc/version.py -> build/lib/ccdproc
> copying ccdproc/conftest.py -> build/lib/ccdproc
> copying ccdproc/_astropy_init.py -> build/lib/ccdproc
> copying ccdproc/image_collection.py -> build/lib/ccdproc
> copying ccdproc/combiner.py -> build/lib/ccdproc
> creating build/lib/ccdproc/utils
> copying ccdproc/utils/__init__.py -> build/lib/ccdproc/utils
> copying ccdproc/utils/slices.py -> build/lib/ccdproc/utils
> creating build/lib/ccdproc/tests
> copying ccdproc/tests/setup_package.py -> build/lib/ccdproc/tests
> copying ccdproc/tests/test_ccdproc_logging.py -> build/lib/ccdproc/tests
> copying ccdproc/tests/test_bitfield.py -> build/lib/ccdproc/tests
> copying ccdproc/tests/test_rebin.py -> build/lib/ccdproc/tests
> copying ccdproc/tests/__init__.py -> build/lib/ccdproc/tests
> copying ccdproc/tests/test_ccdmask.py -> build/lib/ccdproc/tests
> copying ccdproc/tests/test_wrapped_external_funcs.py -> 
> build/lib/ccdproc/tests
> copying ccdproc/tests/test_keyword.py -> build/lib/ccdproc/tests
> copying ccdproc/tests/test_image_collection.py -> build/lib/ccdproc/tests
> copying ccdproc/tests/test_ccdproc.py -> build/lib/ccdproc/tests
> copying ccdproc/tests/test_combiner.py -> build/lib/ccdproc/tests
> copying ccdproc/tests/test_ccddata.py -> build/lib/ccdproc/tests
> copying ccdproc/tests/test_cosmicray.py -> build/lib/ccdproc/tests
> copying ccdproc/tests/test_gain.py -> build/lib/ccdproc/tests
> copying ccdproc/tests/pytest_fixtures.py -> build/lib/ccdproc/tests
> creating build/lib/ccdproc/extern
> copying ccdproc/extern/__init__.py -> build/lib/ccdproc/extern
> copying ccdproc/extern/bitfield.py -> build/lib/ccdproc/extern
> creating build/lib/ccdproc/utils/tests
> copying ccdproc/utils/tests/__init__.py -> build/lib/ccdproc/utils/tests
> copying ccdproc/utils/tests/test_slices.py -> build/lib/ccdproc/utils/tests
> copying ccdproc/tests/coveragerc -> build/lib/ccdproc/tests
> creating build/lib/ccdproc/tests/data
> copying ccdproc/tests/data/a8280271.fits -> build/lib/ccdproc/tests/data
> copying ccdproc/tests/data/sip-wcs.fit -> build/lib/ccdproc/tests/data
> running install_lib
> creating /tmp/ccdproc-test-m_j8ygd0/lib
> creating /tmp/ccdproc-test-m_j8ygd0/lib/python3.7
> creating /tmp/ccdproc-test-m_j8ygd0/lib/python3.7/site-packages
> creating /tmp/ccdproc-test-m_j8ygd0/lib/python3.7/site-packages/ccdproc
> copying build/lib/ccdproc/log_meta.py -> 
> /tmp/ccdproc-test-m_j8ygd0/lib/python3.7/site-packages/ccdproc
> creating /tmp/ccdproc-test-m_j8ygd0/lib/python3.7/site-packages/ccdproc/utils
> copying build/lib/ccdproc/utils/__init__.py -> 
> /tmp/ccdproc-test-m_j8ygd0/lib/python3.7/site-packages/ccdproc/utils
> creating 
> /tmp/ccdproc-test-m_j8ygd0/lib/python3.7/site-packages/ccdproc/utils/tests
> copying build/lib/ccdproc/utils/tests/__init__.py -> 
> /tmp/ccdproc-test-m_j8ygd0/lib/python3.7/site-packages/ccdproc/utils/tests
> copying build/lib/ccdproc/utils/tests/test_slices.py -> 
> /tmp/ccdproc-test-m_j8ygd0/lib/python3.7/site-packages/ccdproc/utils/tests
> copying build/lib/ccdproc/utils/slices.py -> 
> /tmp/ccdproc-test-m_j8ygd0/lib/python3.7/site-packages/ccdproc/utils
> copying build/lib/ccdproc/__init__.py -> 
> /tmp/ccdproc-test-m_j8ygd0/lib/python3.7/site-packages/ccdproc
> copying build/lib/ccdproc/core.py -> 
> /tmp/ccdproc-test-m_j8ygd0/lib/python3.7/site-packages/ccdproc
> creating /tmp/ccdproc-test-m_j8ygd0/lib/python3.7/site-packages/ccdproc/tests
> copying build/lib/ccdproc/tests/setup_package.py -> 
> /tmp/ccdproc-test-m_j8ygd0/lib/python3.7/site-packages/ccdproc/tests
> copying build/lib/ccdproc/tests/coveragerc -> 
> /tmp/ccdproc-test-m_j8ygd0/lib/python3.7/site-packages/ccdproc/tests
> copying build/lib/ccdproc/tests/test_ccdproc_logging.py -> 
> /tmp/ccdproc-test-m_j8ygd0/lib/python3.7/site-packages/ccdproc/tests
> copying build/lib/ccdproc/tests/test_bitfield.

Bug#917757: node-object-path: FTBFS: tests failed

2018-12-29 Thread Lucas Nussbaum
Source: node-object-path
Version: 0.11.3-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mocha test.js -R spec
> 
> 
>   get
> ✓ should return the value using unicode key
> ✓ should return the value using dot in key
> ✓ should return the value under shallow object
> ✓ should work with number path
> ✓ should return the value under deep object
> ✓ should return the value under array
> ✓ should return the value under array deep
> ✓ should return undefined for missing values under object
> ✓ should return undefined for missing values under array
> ✓ should return the value under integer-like key
> ✓ should return the default value when the key doesnt exist
> ✓ should return the default value when path is empty
> ✓ should return the default value when object is null or undefined
> ✓ should not fail on an object with a null prototype
> ✓ should skip non own properties
> 
>   set
> ✓ should set the value using unicode key
> ✓ should set the value using dot in key
> 1) should set value under shallow object
> 2) should set value using number path
> 3) should set value under deep object
> 4) should set value under array
> 5) should create intermediate objects
> 6) should create intermediate arrays
> ✓ should set value under integer-like key
> ✓ should set value under empty array
> 
>   push
> 7) should push value to existing array using unicode key
> ✓ should push value to existing array using dot key
> 8) should push value to existing array
> 9) should push value to new array
> 10) should push value to existing array using number path
> 
>   ensureExists
> 11) should create the path if it does not exists
> ✓ should return the object if path is empty
> ✓ Issue #26
> 
>   coalesce
> ✓ should return the first non-undefined value
> ✓ should work with falsy values (null, 0, '', false)
> ✓ returns defaultValue if no paths found
> ✓ works with unicode and dot keys
> 
>   empty
> ✓ should ignore invalid arguments safely
> ✓ should empty each path according to their types
> 
>   del
> ✓ should work with number path
> 12) should delete deep paths
> ✓ should remove items from existing array
> 
>   insert
> 13) should insert value into existing array
> 14) should create intermediary array
> 15) should insert in another index
> ✓ should handle sparse array
> 
>   has
> ✓ should return false for empty object
> ✓ should handle empty paths properly
> ✓ should test under shallow object
> ✓ should work with number path
> ✓ should test under deep object
> ✓ should test value under array
> ✓ should test the value under array deep
> ✓ should test the value under integer-like key
> ✓ should distinct nonexistent key and key = undefined
> ✓ should work with deep undefined/null values
> 
>   bind object
> ✓ should return the value under shallow object
> 16) should set value under shallow object
> 17) should push value to existing array
> 18) should create the path if it does not exists
> ✓ should return the first non-undefined value
> ✓ should empty each path according to their types
> 19) should delete deep paths
> 20) should insert value into existing array
> ✓ should test under shallow object
> 
>   Don't access not own properties [default]
> ✓ should not get a not own property
> ✓ should set a not own property on the instance (not the prototype)
> ✓ has should return false on a not own property
> ✓ empty should not empty on a not own property
> ✓ del should not delete not own property
> 
>   Access own properties [optional]
> ✓ should get a not own property
> ✓ should set a deep not own property on the prototype (if exists)
> ✓ has should return true on a not own property
> ✓ empty should empty a not own property
> ✓ del should delete a not own property
> 
> 
>   55 passing (37ms)
>   20 failing
> 
>   1) set
>should set value under shallow object:
>  AssertionError: expected { Object (a, b, ...) } to have deep property 
> 'c.m'
>   at Context. (test.js:164:30)
>   at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21)
>   at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
>   at Runner.runTest (/usr/lib/n

Bug#917745: cross-toolchain-base: FTBFS: applying patches fails

2018-12-29 Thread Lucas Nussbaum
Source: cross-toolchain-base
Version: 30
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> linux: 4.19.12-1 / 4.18.20-2cross2
> glibc: 2.28-4 / 2.28-2cross2
> 
> old linux version: 4.18.20-2 / 2
> old glibc version: 2.28-2 / 2
> 
> new linux version: 4.19.12-1cross1
> new glibc version: 2.28-4cross1
> START stamp-dir/init-glibc
> rm -rf glibc-2.28
> tar -x -f  /usr/src/glibc/glibc-2.28.tar.xz
> cp -a /usr/src/glibc/debian/ glibc-2.28
> cd glibc-2.28 ; \
> QUILT_PATCHES=/<>/debian/patches/glibc/debian quilt --quiltrc 
> /dev/null push -a && \
> rm -rf .pc/
> Applying patch dpkg-shlibs.patch
> patching file debian/rules.d/debhelper.mk
> 
> Applying patch local-kill-locales.patch
> patching file debian/rules
> patching file localedata/SUPPORTED
> 
> Applying patch glibc-build-tools.diff
> patching file debian/rules
> 
> Applying patch gcc-8-armel.diff
> patching file debian/sysdeps/armel.mk
> Hunk #1 FAILED at 1.
> 1 out of 1 hunk FAILED -- rejects in file debian/sysdeps/armel.mk
> Patch gcc-8-armel.diff does not apply (enforce with -f)
> make: *** [debian/rules:436: stamp-dir/init-glibc] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2018/12/29/cross-toolchain-base_30_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



Bug#917761: php-monolog: FTBFS: PHP Fatal error: Uncaught Error: Class 'PHPUnit_Framework_TestCase' not found in /<>/tests/Monolog/ErrorHandlerTest.php:16

2018-12-29 Thread Lucas Nussbaum
Source: php-monolog
Version: 1.23.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> phpunit --bootstrap autoload.php --include-path src
> PHP Fatal error:  Uncaught Error: Class 'PHPUnit_Framework_TestCase' not 
> found in /<>/tests/Monolog/ErrorHandlerTest.php:16
> Stack trace:
> #0 /usr/share/php/PHPUnit/Util/FileLoader.php(57): include_once()
> #1 /usr/share/php/PHPUnit/Util/FileLoader.php(45): 
> PHPUnit\Util\FileLoader::load('/build/php-mono...')
> #2 /usr/share/php/PHPUnit/Framework/TestSuite.php(540): 
> PHPUnit\Util\FileLoader::checkAndLoad('/build/php-mono...')
> #3 /usr/share/php/PHPUnit/Framework/TestSuite.php(618): 
> PHPUnit\Framework\TestSuite->addTestFile('/build/php-mono...')
> #4 /usr/share/php/PHPUnit/Util/Configuration.php(1137): 
> PHPUnit\Framework\TestSuite->addTestFiles(Array)
> #5 /usr/share/php/PHPUnit/Util/Configuration.php(996): 
> PHPUnit\Util\Configuration->getTestSuite(Object(DOMElement), Array)
> #6 /usr/share/php/PHPUnit/TextUI/Command.php(902): 
> PHPUnit\Util\Configuration->getTestSuiteConfiguration('')
> #7 /usr/share/php/PHPUnit/TextUI/Command.php(173): 
> PHPUnit\TextUI\Command->handleArguments(Array)
> #8 /usr/share/php/PHPUnit in 
> /<>/tests/Monolog/ErrorHandlerTest.php on line 16
> make[1]: *** [debian/rules:20: override_dh_auto_test] Error 255

The full build log is available from:
   http://aws-logs.debian.net/2018/12/29/php-monolog_1.23.0-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



Bug#917756: astropy-healpix: FTBFS: tests failed

2018-12-29 Thread Lucas Nussbaum
Source: astropy-healpix
Version: 0.4-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> python3.7 setup.py test -vv --args "-vv"
> running test
> running install
> running build
> running build_py
> creating build/lib.linux-x86_64-3.7
> creating build/lib.linux-x86_64-3.7/astropy_healpix
> copying astropy_healpix/setup_package.py -> 
> build/lib.linux-x86_64-3.7/astropy_healpix
> copying astropy_healpix/healpy.py -> 
> build/lib.linux-x86_64-3.7/astropy_healpix
> copying astropy_healpix/__init__.py -> 
> build/lib.linux-x86_64-3.7/astropy_healpix
> copying astropy_healpix/core.py -> build/lib.linux-x86_64-3.7/astropy_healpix
> copying astropy_healpix/version.py -> 
> build/lib.linux-x86_64-3.7/astropy_healpix
> copying astropy_healpix/high_level.py -> 
> build/lib.linux-x86_64-3.7/astropy_healpix
> copying astropy_healpix/conftest.py -> 
> build/lib.linux-x86_64-3.7/astropy_healpix
> copying astropy_healpix/_astropy_init.py -> 
> build/lib.linux-x86_64-3.7/astropy_healpix
> copying astropy_healpix/bench.py -> build/lib.linux-x86_64-3.7/astropy_healpix
> creating build/lib.linux-x86_64-3.7/astropy_healpix/tests
> copying astropy_healpix/tests/test_core.py -> 
> build/lib.linux-x86_64-3.7/astropy_healpix/tests
> copying astropy_healpix/tests/setup_package.py -> 
> build/lib.linux-x86_64-3.7/astropy_healpix/tests
> copying astropy_healpix/tests/six.py -> 
> build/lib.linux-x86_64-3.7/astropy_healpix/tests
> copying astropy_healpix/tests/__init__.py -> 
> build/lib.linux-x86_64-3.7/astropy_healpix/tests
> copying astropy_healpix/tests/test_high_level.py -> 
> build/lib.linux-x86_64-3.7/astropy_healpix/tests
> copying astropy_healpix/tests/test_bench.py -> 
> build/lib.linux-x86_64-3.7/astropy_healpix/tests
> copying astropy_healpix/tests/test_healpy.py -> 
> build/lib.linux-x86_64-3.7/astropy_healpix/tests
> copying astropy_healpix/interpolation.c -> 
> build/lib.linux-x86_64-3.7/astropy_healpix
> copying astropy_healpix/_compiler.c -> 
> build/lib.linux-x86_64-3.7/astropy_healpix
> copying astropy_healpix/_core.c -> build/lib.linux-x86_64-3.7/astropy_healpix
> copying astropy_healpix/tests/coveragerc -> 
> build/lib.linux-x86_64-3.7/astropy_healpix/tests
> running build_ext
> building 'astropy_healpix._compiler' extension
> creating build/temp.linux-x86_64-3.7
> creating build/temp.linux-x86_64-3.7/astropy_healpix
> x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -I/usr/include/python3.7m -c astropy_healpix/_compiler.c -o 
> build/temp.linux-x86_64-3.7/astropy_healpix/_compiler.o
> x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions 
> -Wl,-z,relro -Wl,-z,relro -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 build/temp.linux-x86_64-3.7/astropy_healpix/_compiler.o 
> -o 
> build/lib.linux-x86_64-3.7/astropy_healpix/_compiler.cpython-37m-x86_64-linux-gnu.so
> building 'astropy_healpix._core' extension
> creating build/temp.linux-x86_64-3.7/cextern
> creating build/temp.linux-x86_64-3.7/cextern/astrometry.net
> x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -I/usr/lib/python3/dist-packages/numpy/core/include -Icextern/astrometry.net 
> -Iastropy_healpix -Icextern/lalsuite -Icextern/numpy 
> -I/usr/include/python3.7m -c cextern/astrometry.net/bl.c -o 
> build/temp.linux-x86_64-3.7/cextern/astrometry.net/bl.o -O2
> cextern/astrometry.net/bl.c: In function 'sl_appendvf':
> cextern/astrometry.net/bl.c:1218:9: warning: implicit declaration of function 
> 'vasprintf'; did you mean 'vsprintf'? [-Wimplicit-function-declaration]
>  if (vasprintf(&str, format, va) == -1)
>  ^
>  vsprintf
> x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -I/usr/lib/python3/dist-packages/numpy/core/include -Icextern/astrometry.net 
> -Iastropy_healpix -Icextern/lalsuite -Icextern/numpy 
> -I/usr/include/python3.7m -c cextern/astrometry.net/healpix-utils.c -o 
> buil

Bug#917748: octave-msh: FTBFS: tests failed

2018-12-29 Thread Lucas Nussbaum
Source: octave-msh
Version: 1.0.10-5
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>/src'
> /usr/bin/mkoctfile --verbose -Wdate-time -D_FORTIFY_SOURCE=2  mshm_refine.cc 
> -Wl,-z,relro 
> /usr/bin/mkoctfile --verbose -Wdate-time -D_FORTIFY_SOURCE=2  
> mshm_dolfin_read.cc -Wl,-z,relro 
> g++ -c -Wdate-time -D_FORTIFY_SOURCE=2  -fPIC 
> -I/usr/include/octave-4.4.1/octave/.. -I/usr/include/octave-4.4.1/octave  
> -pthread -fopenmp -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security  -Wdate-time   
> -D_FORTIFY_SOURCE=2 mshm_refine.cc -o mshm_refine.o
> g++ -c -Wdate-time -D_FORTIFY_SOURCE=2  -fPIC 
> -I/usr/include/octave-4.4.1/octave/.. -I/usr/include/octave-4.4.1/octave  
> -pthread -fopenmp -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security  -Wdate-time   
> -D_FORTIFY_SOURCE=2 mshm_dolfin_read.cc -o mshm_dolfin_read.o
> g++ -I/usr/include/octave-4.4.1/octave/.. -I/usr/include/octave-4.4.1/octave  
> -pthread -fopenmp -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -shared 
> -Wl,-Bsymbolic  -Wdate-time -o mshm_refine.oct  mshm_refine.o   -Wl,-z,relro 
> -L/usr/lib/x86_64-linux-gnu/octave/4.4.1 -L/usr/lib/x86_64-linux-gnu 
> -loctinterp -loctave -Wl,-z,relro 
> g++ -I/usr/include/octave-4.4.1/octave/.. -I/usr/include/octave-4.4.1/octave  
> -pthread -fopenmp -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -shared 
> -Wl,-Bsymbolic  -Wdate-time -o mshm_dolfin_read.oct  mshm_dolfin_read.o   
> -Wl,-z,relro -L/usr/lib/x86_64-linux-gnu/octave/4.4.1 
> -L/usr/lib/x86_64-linux-gnu -loctinterp -loctave -Wl,-z,relro 
> /usr/bin/mkoctfile --verbose -Wdate-time -D_FORTIFY_SOURCE=2  
> mshm_dolfin_write.cc -Wl,-z,relro 
> g++ -c -Wdate-time -D_FORTIFY_SOURCE=2  -fPIC 
> -I/usr/include/octave-4.4.1/octave/.. -I/usr/include/octave-4.4.1/octave  
> -pthread -fopenmp -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security  -Wdate-time   
> -D_FORTIFY_SOURCE=2 mshm_dolfin_write.cc -o mshm_dolfin_write.o
> g++ -I/usr/include/octave-4.4.1/octave/.. -I/usr/include/octave-4.4.1/octave  
> -pthread -fopenmp -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -shared 
> -Wl,-Bsymbolic  -Wdate-time -o mshm_dolfin_write.oct  mshm_dolfin_write.o   
> -Wl,-z,relro -L/usr/lib/x86_64-linux-gnu/octave/4.4.1 
> -L/usr/lib/x86_64-linux-gnu -loctinterp -loctave -Wl,-z,relro 
> make[1]: Leaving directory '/<>/src'
> copyfile /<>/./src/mshm_dolfin_read.oct 
> /<>/./src/mshm_dolfin_write.oct 
> /<>/./src/mshm_refine.oct 
> /<>/./inst/x86_64-pc-linux-gnu-api-v52
> For information about changes from previous versions of the msh package, run 
> 'news msh'.
>dh_octave_check -O--buildsystem=octave
> Checking package...
> Checking m files ...
> [inst/msh2m_submesh.m]
> >>>>> /<>/inst/msh2m_submesh.m
> * test
>  [mesh1] = msh2m_structured_mesh(0:.5:1, 0:.5:1, 1, 1:4, 'left');
>  [mesh2] = msh2m_structured_mesh(1:.5:2, 0:.5:1, 1, 1:4, 'left');
>  [mesh]  = msh2m_join_structured_mesh(mesh1,mesh2,2,4);
>  [omesh,nodelist,elementlist] = msh2m_submesh(mesh,[],2);
>  p = [1.0   1.0   1.0   1.5   1.5   1.5   2.0   
> 2.0   2.0
>   0.0   0.5   1.0   0.0   0.5   1.0   0.0   
> 0.5   1.0];
>  e = [1   1   2   3   4   6   7   8
>   2   4   3   6   7   9   8   9
>   0   0   0   0   0   0   0   0
>   0   0   0   0   0   0   0   0
>   2   5   2   7   5   7   6   6
>   2   0   2   0   0   0   0   0
>   1   2   1   2   2   2   2   2];
>  t = [1   2   4   5   2   3   5   6
>   4   5   7   8   4   5   7   8
>   2   3   5   6   5   6   8   9
>   2   2   2   2   2   2   2   2];
>  nl = [789   10   11   12   13   14   15];
>  el = [9   10   11   12   13   14   15   16];
>  toll = 1e-4;
>  assert(omesh.p,p,toll);
>  assert(omesh.e,e);
>  assert(omesh.t,t);
>  assert(nodelist,nl);
>  assert(elementlist,el);
> * demo
>  name = [tmpnam ".geo"];
>  fid = fopen (name, "w");
>  fputs (fid, "Point(1) = {0, 0, 0, .1};\n");
>  fputs (fid, "Point(2) = {1, 0, 0, .1};\n");
>  fputs (fid, "Point(3) = {1, 0.5, 0, .1};\n");
>  fputs (fid, "Point(4) 

Bug#917747: golang-github-rackspace-gophercloud: FTBFS: tests failed

2018-12-29 Thread Lucas Nussbaum
Source: golang-github-rackspace-gophercloud
Version: 1.0.0+git20161013.1012.e00690e8-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory 
> '/<>/golang-github-rackspace-gophercloud-1.0.0+git20161013.1012.e00690e8'
> (export GOPATH=`pwd`/obj-x86_64-linux-gnu; \
>   cd $GOPATH/src/$DH_GOPKG/; \
>   go test -v -tags=fixtures ./...)
> go: disabling cache (/sbuild-nonexistent/.cache/go-build) due to 
> initialization failure: mkdir /sbuild-nonexistent: permission denied
> === RUN   TestApplyDefaultsToEndpointOpts
> --- PASS: TestApplyDefaultsToEndpointOpts (0.00s)
> === RUN   TestMaybeString
> --- PASS: TestMaybeString (0.00s)
> === RUN   TestMaybeInt
> --- PASS: TestMaybeInt (0.00s)
> === RUN   TestBuildQueryString
> --- PASS: TestBuildQueryString (0.00s)
> === RUN   TestBuildHeaders
> --- PASS: TestBuildHeaders (0.00s)
> === RUN   TestIsZero
> --- PASS: TestIsZero (0.00s)
> === RUN   TestQueriesAreEscaped
> --- PASS: TestQueriesAreEscaped (0.00s)
> === RUN   TestAuthenticatedHeaders
> --- PASS: TestAuthenticatedHeaders (0.00s)
> === RUN   TestUserAgent
> --- PASS: TestUserAgent (0.00s)
> === RUN   TestServiceURL
> --- PASS: TestServiceURL (0.00s)
> === RUN   TestWaitFor
> --- PASS: TestWaitFor (1.00s)
> === RUN   TestNormalizeURL
> --- PASS: TestNormalizeURL (0.00s)
> === RUN   TestNormalizePathURL
> --- PASS: TestNormalizePathURL (0.00s)
> PASS
> okgithub.com/rackspace/gophercloud1.004s
> ? github.com/rackspace/gophercloud/acceptance/openstack/blockstorage/v1   
> [no test files]
> ? github.com/rackspace/gophercloud/acceptance/openstack/blockstorage/v2   
> [no test files]
> ? 
> github.com/rackspace/gophercloud/acceptance/openstack/blockstorage/v2/extensions
> [no test files]
> ? github.com/rackspace/gophercloud/acceptance/openstack/compute/v2
> [no test files]
> ? github.com/rackspace/gophercloud/acceptance/openstack/db/v1 [no 
> test files]
> ? github.com/rackspace/gophercloud/acceptance/openstack/identity/v2   
> [no test files]
> ? github.com/rackspace/gophercloud/acceptance/openstack/identity/v3   
> [no test files]
> ? github.com/rackspace/gophercloud/acceptance/openstack/imageservice/v2   
> [no test files]
> ? github.com/rackspace/gophercloud/acceptance/openstack/networking/v2 
> [no test files]
> ? 
> github.com/rackspace/gophercloud/acceptance/openstack/networking/v2/extensions
>   [no test files]
> ? 
> github.com/rackspace/gophercloud/acceptance/openstack/networking/v2/extensions/fwaas
> [no test files]
> ? 
> github.com/rackspace/gophercloud/acceptance/openstack/networking/v2/extensions/lbaas
> [no test files]
> ? 
> github.com/rackspace/gophercloud/acceptance/openstack/networking/v2/extensions/lbaas_v2
>  [no test files]
> ? 
> github.com/rackspace/gophercloud/acceptance/openstack/networking/v2/extensions/portsbinding
>  [no test files]
> ? github.com/rackspace/gophercloud/acceptance/rackspace   [no test files]
> ? github.com/rackspace/gophercloud/acceptance/rackspace/compute/v2
> [no test files]
> ? github.com/rackspace/gophercloud/acceptance/rackspace/db/v1 [no 
> test files]
> ? github.com/rackspace/gophercloud/acceptance/rackspace/identity/v2   
> [no test files]
> ? github.com/rackspace/gophercloud/acceptance/rackspace/networking/v2 
> [no test files]
> ? github.com/rackspace/gophercloud/acceptance/tools   [no test files]
> === RUN   TestAuthenticatedClientV3
> --- PASS: TestAuthenticatedClientV3 (0.00s)
> === RUN   TestAuthenticatedClientV2
> --- PASS: TestAuthenticatedClientV2 (0.00s)
> === RUN   TestNewClient
> --- PASS: TestNewClient (0.00s)
> === RUN   TestV2EndpointExact
> --- PASS: TestV2EndpointExact (0.00s)
> === RUN   TestV2EndpointNone
> --- PASS: TestV2EndpointNone (0.00s)
> === RUN   TestV2EndpointMultiple
> --- PASS: TestV2EndpointMultiple (0.00s)
> === RUN   TestV2EndpointBadAvailability
> --- PASS: TestV2EndpointBadAvailability (0.00s)
> === RUN   TestV3EndpointExact
> --- PASS: TestV3EndpointExact (0.00s)
> === RUN   TestV3EndpointNone
> --- PASS: TestV3EndpointNone (0.00s)
> === RUN   TestV3EndpointMultiple
> --- PASS: TestV3EndpointMultiple (0.00s)
> === RUN   TestV3EndpointBadAvailability
> --- PASS: TestV3EndpointBadAvailability (0.00s)
> PASS
> okgithub.com/rackspace/gophercloud/openstack  0.014s
> === RUN   TestListVersions
> --- PASS: TestListVersions (0.00s)
> === RUN

Bug#917741: globus-xio-gridftp-driver: FTBFS: tests failed

2018-12-29 Thread Lucas Nussbaum
Source: globus-xio-gridftp-driver
Version: 3.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[4]: Entering directory '/<>/test'
> FAIL: globus_gridftp_driver_test.pl
> 
>globus_xio_gridftp_driver 3.1: test/test-suite.log
> 
> 
> # TOTAL: 1
> # PASS:  0
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> .. contents:: :depth: 2
> 
> FAIL: globus_gridftp_driver_test.pl
> ===
> 
> #./globus_gridftp_driver_test.pl 
> 1..8
> not ok 1 - globus_gridftp_driver_test -r exits with 6
> #   Failed test 'globus_gridftp_driver_test -r exits with 6'
> #   at ./globus_gridftp_driver_test.pl line 53.
> not ok 2 - File compares with remote original
> #   Failed test 'File compares with remote original'
> #   at ./globus_gridftp_driver_test.pl line 54.
> not ok 3 - globus_gridftp_driver_test -w exits with 6
> #   Failed test 'globus_gridftp_driver_test -w exits with 6'
> #   at ./globus_gridftp_driver_test.pl line 72.
> not ok 4 - File compares with remote
> #   Failed test 'File compares with remote'
> #   at ./globus_gridftp_driver_test.pl line 73.
> not ok 5 - globus_gridftp_driver_test -a exits with 6
> #   Failed test 'globus_gridftp_driver_test -a exits with 6'
> #   at ./globus_gridftp_driver_test.pl line 91.
> not ok 6 - File compares with remote
> #   Failed test 'File compares with remote'
> #   at ./globus_gridftp_driver_test.pl line 92.
> not ok 7 - 2nd globus_gridftp_driver_test -a exits with 6
> #   Failed test '2nd globus_gridftp_driver_test -a exits with 6'
> #   at ./globus_gridftp_driver_test.pl line 112.
> # 
> not ok 8 - File compares with appended remote
> #   Failed test 'File compares with appended remote'
> #   at ./globus_gridftp_driver_test.pl line 113.
> # 
> # Looks like you failed 8 tests of 8.
> # Test exited with 2048
> FAIL globus_gridftp_driver_test.pl (exit status: 1)
> 
> 
> Testsuite summary for globus_xio_gridftp_driver 3.1
> 
> # TOTAL: 1
> # PASS:  0
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> See test/test-suite.log
> Please report to https://github.com/gridcf/gct/issues
> 
> make[4]: *** [Makefile:709: test-suite.log] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/2018/12/29/globus-xio-gridftp-driver_3.1-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



Bug#917742: ca-cacert: FTBFS: tests failed

2018-12-29 Thread Lucas Nussbaum
Source: ca-cacert
Version: 2011.0523-2
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> #find . -maxdepth 1 -type f -name "*.crt" -exec openssl verify "{}" \;
> certtool --verify --load-ca-certificate root.crt --infile class3.crt
> Loaded CAs (1 available)
>   Subject: CN=CAcert Class 3 Root,OU=http://www.CAcert.org,O=CAcert Inc.
>   Issuer: EMAIL=supp...@cacert.org,CN=CA Cert Signing 
> Authority,OU=http://www.cacert.org,O=Root CA
>   Checked against: EMAIL=supp...@cacert.org,CN=CA Cert Signing 
> Authority,OU=http://www.cacert.org,O=Root CA
>   Signature algorithm: RSA-SHA256
>   Output: Verified. The certificate is trusted. 
> 
> Chain verification output: Verified. The certificate is trusted. 
> 
> certtool --verify --load-ca-certificate root.crt --infile root.crt
> Loaded CAs (1 available)
>   Subject: EMAIL=supp...@cacert.org,CN=CA Cert Signing 
> Authority,OU=http://www.cacert.org,O=Root CA
>   Issuer: EMAIL=supp...@cacert.org,CN=CA Cert Signing 
> Authority,OU=http://www.cacert.org,O=Root CA
>   Checked against: EMAIL=supp...@cacert.org,CN=CA Cert Signing 
> Authority,OU=http://www.cacert.org,O=Root CA
>   Signature algorithm: RSA-MD5
>   Output: Not verified. The certificate is NOT trusted. 
> 
> Chain verification output: Not verified. The certificate is NOT trusted. 
> 
> make[1]: *** [debian/rules:13: override_dh_auto_test] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2018/12/29/ca-cacert_2011.0523-2_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



Bug#917746: uglifyjs: FTBFS: tests failures

2018-12-29 Thread Lucas Nussbaum
Source: uglifyjs
Version: 2.8.29-3
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> test -x debian/rules
> mkdir -p "."
> NODE_PATH=lib help2man --no-info bin/uglifyjs | sed \
> -e 's/[[:space:]]*\[string\]$/ This parameter is a string./g' \
> -e 's/[[:space:]]*\[boolean\]$/ This parameter is a boolean./g' \
> -e 's/[[:space:]]*\[array\]$/ This parameter is an array./g'> 
> debian/uglifyjs.1
> NODE_PATH=lib nodejs test/run-tests.js 
> *** Entering [compress]
> --- angular-inject.js
> Running test [ng_inject_defun]
> Running test [ng_inject_assignment]
> Running test [ng_inject_inline]
> --- arrays.js
> Running test [holes_and_undefined]
> Running test [constant_join]
> Running test [constant_join_2]
> Running test [constant_join_3]
> Running test [for_loop]
> --- ascii.js
> Running test [ascii_only_true]
> Running test [ascii_only_false]
> --- asm.js
> Running test [asm_mixed]
> --- assignment.js
> Running test [op_equals_left_local_var]
> Running test [op_equals_right_local_var]
> Running test [op_equals_left_global_var]
> Running test [op_equals_right_global_var]
> --- blocks.js
> Running test [remove_blocks]
> Running test [keep_some_blocks]
> --- collapse_vars.js
> Running test [collapse_vars_side_effects_1]
> Running test [collapse_vars_side_effects_2]
> Running test [collapse_vars_issue_721]
> Running test [collapse_vars_properties]
> Running test [collapse_vars_if]
> Running test [collapse_vars_while]
> Running test [collapse_vars_do_while]
> Running test [collapse_vars_do_while_drop_assign]
> Running test [collapse_vars_seq]
> Running test [collapse_vars_throw]
> Running test [collapse_vars_switch]
> Running test [collapse_vars_assignment]
> Running test [collapse_vars_lvalues]
> Running test [collapse_vars_lvalues_drop_assign]
> Running test [collapse_vars_misc1]
> Running test [collapse_vars_self_reference]
> Running test [collapse_vars_repeated]
> Running test [collapse_vars_closures]
> Running test [collapse_vars_unary]
> Running test [collapse_vars_try]
> Running test [collapse_vars_array]
> Running test [collapse_vars_object]
> Running test [collapse_vars_eval_and_with]
> Running test [collapse_vars_constants]
> Running test [collapse_vars_arguments]
> Running test [collapse_vars_short_circuit]
> Running test [collapse_vars_short_circuited_conditions]
> Running test [collapse_vars_regexp]
> Running test [issue_1537]
> Running test [issue_1562]
> Running test [issue_1605_1]
> Running test [issue_1605_2]
> Running test [issue_1631_1]
> Running test [issue_1631_2]
> Running test [issue_1631_3]
> Running test [var_side_effects_1]
> Running test [var_side_effects_2]
> Running test [var_side_effects_3]
> Running test [reassign_const_1]
> Running test [reassign_const_2]
> --- comparing.js
> Running test [keep_comparisons]
> Running test [keep_comparisons_with_unsafe_comps]
> Running test [dont_change_in_or_instanceof_expressions]
> --- concat-strings.js
> Running test [concat_1]
> Running test [concat_2]
> Running test [concat_3]
> Running test [concat_4]
> Running test [concat_5]
> Running test [concat_6]
> Running test [concat_7]
> Running test [concat_8]
> --- conditionals.js
> Running test [ifs_1]
> Running test [ifs_2]
> Running test [ifs_3_should_warn]
> Running test [ifs_4]
> Running test [ifs_5]
> Running test [ifs_6]
> Running test [cond_1]
> Running test [cond_2]
> Running test [cond_3]
> Running test [cond_4]
> Running test [cond_5]
> Running test [cond_7]
> Running test [cond_7_1]
> Running test [cond_8]
> Running test [cond_8b]
> Running test [cond_8c]
> Running test [ternary_boolean_consequent]
> Running test [ternary_boolean_alternative]
> Running test [trivial_boolean_ternary_expressions]
> Running test [issue_1154]
> Running test [no_evaluate]
> Running test [equality_conditionals_false]
> Running test [equality_conditionals_true]
> Running test [issue_1645_1]
> Running test [issue_1645_2]
> Running test [condition_symbol_matches_consequent]
> Running test [delete_conditional_1]
> Running test [delete_cond

Bug#917743: clj-time-clojure: FTBFS: tests failed

2018-12-29 Thread Lucas Nussbaum
Source: clj-time-clojure
Version: 0.14.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> (cd test && find . -name '*.clj' | \
>   xargs --verbose clojure -cp 
> /<>/clj-time.jar:/usr/share/java/clojure.jar:/usr/share/java/joda-time.jar:/usr/share/java/java.jdbc.jar)
> clojure -cp 
> /<>/clj-time.jar:/usr/share/java/clojure.jar:/usr/share/java/joda-time.jar:/usr/share/java/java.jdbc.jar
>  ./clj_time/local_test.clj ./clj_time/predicates_test.clj 
> ./clj_time/types_test.clj ./clj_time/jdbc_test.clj ./clj_time/core_test.clj 
> ./clj_time/periodic_test.clj ./clj_time/coerce_test.clj 
> ./clj_time/format_test.clj 
> Exception in thread "main" java.io.FileNotFoundException: Could not locate 
> clj_time/core_test__init.class or clj_time/core_test.clj on classpath. Please 
> check that namespaces with dashes use underscores in the Clojure file name., 
> compiling:(/<>/test/./clj_time/local_test.clj:1:1)
>   at clojure.lang.Compiler.load(Compiler.java:7526)
>   at clojure.lang.Compiler.loadFile(Compiler.java:7452)
>   at clojure.main$load_script.invokeStatic(main.clj:278)
>   at clojure.main$script_opt.invokeStatic(main.clj:338)
>   at clojure.main$script_opt.invoke(main.clj:333)
>   at clojure.main$main.invokeStatic(main.clj:424)
>   at clojure.main$main.doInvoke(main.clj:387)
>   at clojure.lang.RestFn.applyTo(RestFn.java:137)
>   at clojure.lang.Var.applyTo(Var.java:702)
>   at clojure.main.main(main.java:37)
> Caused by: java.io.FileNotFoundException: Could not locate 
> clj_time/core_test__init.class or clj_time/core_test.clj on classpath. Please 
> check that namespaces with dashes use underscores in the Clojure file name.
>   at clojure.lang.RT.load(RT.java:463)
>   at clojure.lang.RT.load(RT.java:426)
>   at clojure.core$load$fn__9115.invoke(core.clj:6046)
>   at clojure.core$load.invokeStatic(core.clj:6045)
>   at clojure.core$load.doInvoke(core.clj:6029)
>   at clojure.lang.RestFn.invoke(RestFn.java:408)
>   at clojure.core$load_one.invokeStatic(core.clj:5848)
>   at clojure.core$load_one.invoke(core.clj:5843)
>   at clojure.core$load_lib$fn__9060.invoke(core.clj:5888)
>   at clojure.core$load_lib.invokeStatic(core.clj:5887)
>   at clojure.core$load_lib.doInvoke(core.clj:5868)
>   at clojure.lang.RestFn.applyTo(RestFn.java:142)
>   at clojure.core$apply.invokeStatic(core.clj:659)
>   at clojure.core$load_libs.invokeStatic(core.clj:5925)
>   at clojure.core$load_libs.doInvoke(core.clj:5909)
>   at clojure.lang.RestFn.applyTo(RestFn.java:137)
>   at clojure.core$apply.invokeStatic(core.clj:659)
>   at clojure.core$require.invokeStatic(core.clj:5947)
>   at clojure.core$require.doInvoke(core.clj:5947)
>   at clojure.lang.RestFn.invoke(RestFn.java:436)
>   at 
> clj_time.local_test$eval2694$loading__9001__auto2695.invoke(local_test.clj:1)
>   at clj_time.local_test$eval2694.invokeStatic(local_test.clj:1)
>   at clj_time.local_test$eval2694.invoke(local_test.clj:1)
>   at clojure.lang.Compiler.eval(Compiler.java:7062)
>   at clojure.lang.Compiler.eval(Compiler.java:7051)
>   at clojure.lang.Compiler.load(Compiler.java:7514)
>   ... 9 more
> make[1]: *** [debian/rules:29: override_dh_auto_test] Error 123

The full build log is available from:
   http://aws-logs.debian.net/2018/12/29/clj-time-clojure_0.14.0-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



Bug#917744: php-zeta-base: FTBFS: PHP Fatal error: Uncaught Error: Class 'PHPUnit_Framework_TestCase' not found in /usr/share/php/ezc/UnitTest/test/case.php:33

2018-12-29 Thread Lucas Nussbaum
Source: php-zeta-base
Version: 1.9-3
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> phpunit
> PHP Fatal error:  Uncaught Error: Class 'PHPUnit_Framework_TestCase' not 
> found in /usr/share/php/ezc/UnitTest/test/case.php:33
> Stack trace:
> #0 /usr/share/php/ezc/UnitTest/autoload.php(19): require()
> #1 [internal function]: PHPUnit\Util\FileLoader::{closure}('ezcTestCase')
> #2 /<>/tests/base_init_test.php(34): 
> spl_autoload_call('ezcTestCase')
> #3 /usr/share/php/PHPUnit/Util/FileLoader.php(57): 
> include_once('/build/php-zeta...')
> #4 /usr/share/php/PHPUnit/Util/FileLoader.php(45): 
> PHPUnit\Util\FileLoader::load('/build/php-zeta...')
> #5 /usr/share/php/PHPUnit/Framework/TestSuite.php(540): 
> PHPUnit\Util\FileLoader::checkAndLoad('/build/php-zeta...')
> #6 /usr/share/php/PHPUnit/Framework/TestSuite.php(618): 
> PHPUnit\Framework\TestSuite->addTestFile('/build/php-zeta...')
> #7 /usr/share/php/PHPUnit/Util/Configuration.php(1137): 
> PHPUnit\Framework\TestSuite->addTestFiles(Array)
> #8 /usr/share/php/PHPUnit/Util/Configuration.php(996): 
> PHPUnit\Util\Configuration->getTestSuite(Object(DOMElement), Array)
> #9 /u in /usr/share/php/ezc/UnitTest/test/case.php on line 33
> make[1]: *** [debian/rules:17: override_dh_auto_test] Error 255

The full build log is available from:
   http://aws-logs.debian.net/2018/12/29/php-zeta-base_1.9-3_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



Bug#839387: package builds crashing under fakeroot

2018-12-29 Thread Sylvestre Ledru

> Having that spelled out explicitly in a searchable internel-accessible
> post would likely help more than just me.

For me,
override_dh_auto_test:
# Disable fakeroot because of 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839387

    env -u LD_PRELOAD make check

was good enough!

S



Bug#917465: aplpy: autopkgtest needs update for new version of python-numpy

2018-12-29 Thread Ole Streicher
Control: reassign -1 python3-aplpy 1.1.1-4
Control: forwarded -1 https://github.com/aplpy/aplpy/issues/406

On 28.12.18 19:55, Sandro Tosi wrote:
>> warnings.warn('np.asscalar(a) is deprecated since NumPy v1.16, use '
>>> 'a.item() instead', DeprecationWarning, stacklevel=1)
>> E   DeprecationWarning: np.asscalar(a) is deprecated since NumPy
>> v1.16, use a.item() instead
> 
> it's a DeprecationWarning, why does aplpy tests suite treats it as an error?

That is an upstream setting.

Cheers

Ole



Bug#917737: ocaml-qtest: FTBFS: dh_install: missing files, aborting

2018-12-29 Thread Lucas Nussbaum
Source: ocaml-qtest
Version: 2.9-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mkdir -p '/<>/debian/tmp/usr/lib/ocaml'
> jbuilder install --prefix=/<>/debian/tmp/usr 
> --libdir=/<>/debian/tmp/usr/lib/ocaml --verbose
> # Workspace root: /<>
> Running[0]: /usr/bin/nproc > /tmp/dune98b49a.output 2> /dev/null
> # # Workspace root: /<>
> # Auto-detected concurrency: 2
> Running[1]: /usr/bin/ocamlc.opt -config > /tmp/dune3af626.output
> # # # Workspace root: /<>
> # # Auto-detected concurrency: 2
> # Dune context:
> #  ((name default)
> #   (kind default)
> #   (profile release)
> #   (merlin true)
> #   (for_host ())
> #   (build_dir (In_build_dir default))
> #   (toplevel_path ())
> #   (ocaml_bin (External /usr/bin))
> #   (ocaml (External /usr/bin/ocaml))
> #   (ocamlc (External /usr/bin/ocamlc.opt))
> #   (ocamlopt ((External /usr/bin/ocamlopt.opt)))
> #   (ocamldep (External /usr/bin/ocamldep.opt))
> #   (ocamlmklib (External /usr/bin/ocamlmklib.opt))
> #   (env
> #((CAML_LD_LIBRARY_PATH
> #  /<>/_build/install/default/lib/stublibs)
> # (DUNE_CONFIGURATOR /usr/bin/ocamlc.opt)
> # (INSIDE_DUNE 1)
> # (MANPATH
> #  /<>/_build/install/default/bin)
> # (OCAMLFIND_IGNORE_DUPS_IN
> #  /<>/_build/install/default/lib)
> # (OCAMLPATH
> #  /<>/_build/install/default/lib)))
> #   (findlib_path ((External /usr/lib/ocaml)))
> #   (arch_sixtyfour true)
> #   (natdynlink_supported true)
> #   (supports_shared_libraries true)
> #   (opam_vars ())
> #   (ocaml_config
> #((version 4.05.0)
> # (standard_library_default /usr/lib/ocaml)
> # (standard_library /usr/lib/ocaml)
> # (standard_runtime /usr/bin/ocamlrun)
> # (ccomp_type cc)
> # (c_compiler gcc)
> # (ocamlc_cflags
> #  (-O2
> #   -fno-strict-aliasing
> #   -fwrapv
> #   -D_FILE_OFFSET_BITS=64
> #   -D_REENTRANT
> #   -fPIC))
> # (ocamlopt_cflags
> #  (-O2 -fno-strict-aliasing -fwrapv -D_FILE_OFFSET_BITS=64 -D_REENTRANT))
> # (bytecomp_c_compiler
> #  (gcc
> #   -O2
> #   -fno-strict-aliasing
> #   -fwrapv
> #   -D_FILE_OFFSET_BITS=64
> #   -D_REENTRANT
> #   -fPIC))
> # (bytecomp_c_libraries (-lm -ldl -lcurses -lpthread))
> # (native_c_compiler
> #  (gcc
> #   -O2
> #   -fno-strict-aliasing
> #   -fwrapv
> #   -D_FILE_OFFSET_BITS=64
> #   -D_REENTRANT))
> # (native_c_libraries (-lm -ldl))
> # (cc_profile (-pg))
> # (architecture amd64)
> # (model default)
> # (int_size 63)
> # (word_size 64)
> # (system linux)
> # (asm (as))
> # (asm_cfi_supported true)
> # (with_frame_pointers false)
> # (ext_exe )
> # (ext_obj .o)
> # (ext_asm .s)
> # (ext_lib .a)
> # (ext_dll .so)
> # (os_type Unix)
> # (default_executable_name a.out)
> # (systhread_supported true)
> # (host x86_64-pc-linux-gnu)
> # (target x86_64-pc-linux-gnu)
> # (profiling true)
> # (flambda false)
> # (spacetime false)
> # (safe_string false)
> # (exec_magic_number Caml1999X011)
> # (cmi_magic_number Caml1999I021)
> # (cmo_magic_number Caml1999O011)
> # (cma_magic_number Caml1999A012)
> # (cmx_magic_number Caml1999Y015)
> # (cmxa_magic_number Caml1999Z014)
> # (ast_impl_magic_number Caml1999M020)
> # (ast_intf_magic_number Caml1999N018)
> # (cmxs_magic_number Caml2007D002)
> # (cmt_magic_number Caml2012T009)
> # (natdynlink_supported true)
> # (supports_shared_libraries true)
> # (windows_unicode false)))
> #   (which
> #((ocaml ((External /usr/bin/ocaml)))
> # (ocamlc ((External /usr/bin/ocamlc.opt))
> Installing /<>/debian/tmp/usr/lib/ocaml/qtest/META
> Installing /<>/debian/tmp/usr/lib/ocaml/qtest/lib/qtest.lib.dune
> Installing /<>/debian/tmp/usr/lib/ocaml/qtest/lib/qtestlib.a
> Installing /<>/debian/tmp/usr/lib/ocaml/qtest/lib/qtestlib.cma
> Installing /<>/debian/tmp/usr/lib/ocaml/qtest/lib/qtestlib.cmi
> Installing /<>/debian/tmp/usr/lib/ocaml/qtest/lib/qtestlib.cmt
> Installing /<>/debian/tmp/usr/lib/ocaml/qtest/lib/qtestlib.cmx
> Installing /<>/debian/tmp/usr/lib/ocaml/qtest/lib/qtestlib.cmxa
> Installing /<>/debian/tmp/usr/lib/ocaml/qtest/lib/qtestlib.cmxs
> In

Bug#917725: python-acora: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2

2018-12-29 Thread Lucas Nussbaum
Source: python-acora
Version: 2.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> rm -f acora/_acora.c acora/_cacora.c
> dh_auto_clean
> I: pybuild base:217: python2.7 setup.py clean 
> WARNING: Generated .c files are missing, enabling Cython compilation
> Building with Cython 0.28.4
> Compiling acora/_acora.py because it changed.
> Compiling acora/_cacora.pyx because it changed.
> [1/2] Cythonizing acora/_acora.py
> [2/2] Cythonizing acora/_cacora.pyx
> running clean
> removing '/<>/.pybuild/cpython2_2.7_acora/build' (and everything 
> under it)
> 'build/bdist.linux-amd64' does not exist -- can't clean it
> 'build/scripts-2.7' does not exist -- can't clean it
> I: pybuild base:217: python3.7 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.7_acora/build' (and everything 
> under it)
> 'build/bdist.linux-amd64' does not exist -- can't clean it
> 'build/scripts-3.7' does not exist -- can't clean it
> make[1]: Leaving directory '/<>'
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building python-acora using existing 
> ./python-acora_2.1.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: local changes detected, the modified files are:
>  python-acora-2.1/acora/_acora.c
>  python-acora-2.1/acora/_acora.html
>  python-acora-2.1/acora/_cacora.c
>  python-acora-2.1/acora/_cacora.html
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/python-acora_2.1-1.diff.T8mOsr
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> 
> Build finished at 2018-12-29T12:29:03Z

The full build log is available from:
   http://aws-logs.debian.net/2018/12/29/python-acora_2.1-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



Bug#917732: openhft-chronicle-bytes: FTBFS: [ERROR] /<>/src/main/java/net/openhft/chronicle/bytes/NativeBytesStore.java:[78,48] cannot find symbol

2018-12-29 Thread Lucas Nussbaum
Source: openhft-chronicle-bytes
Version: 1.1.15-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=maven
>dh_update_autotools_config -O--buildsystem=maven
>dh_auto_configure -O--buildsystem=maven
>   mh_patchpoms -plibopenhft-chronicle-bytes-java --debian-build 
> --keep-pom-version --maven-repo=/<>/debian/maven-repo
>dh_auto_build -O--buildsystem=maven
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
> -DskipTests -Dnotimestamp=true -Dlocale=en_US
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by 
> com.google.inject.internal.cglib.core.$ReflectUtils$1 
> (file:/usr/share/maven/lib/guice.jar) to method 
> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
> WARNING: Please consider reporting this to the maintainers of 
> com.google.inject.internal.cglib.core.$ReflectUtils$1
> WARNING: Use --illegal-access=warn to enable warnings of further illegal 
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> [INFO] Scanning for projects...
> [INFO] 
> [INFO] < net.openhft:chronicle-bytes 
> >-
> [INFO] Building OpenHFT/Chronicle-Bytes 1.1.15
> [INFO] ---[ bundle 
> ]---
> [INFO] 
> [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ 
> chronicle-bytes ---
> [WARNING] Using platform encoding (ANSI_X3.4-1968 actually) to copy filtered 
> resources, i.e. build is platform dependent!
> [INFO] skip non existing resourceDirectory /<>/src/main/resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.8.0:compile (default-compile) @ 
> chronicle-bytes ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 52 source files to /<>/target/classes
> [INFO] 
> /<>/src/main/java/net/openhft/chronicle/bytes/BytesStore.java: 
> Some input files use unchecked or unsafe operations.
> [INFO] 
> /<>/src/main/java/net/openhft/chronicle/bytes/BytesStore.java: 
> Recompile with -Xlint:unchecked for details.
> [INFO] -
> [WARNING] COMPILATION WARNING : 
> [INFO] -
> [WARNING] 
> /<>/src/main/java/net/openhft/chronicle/bytes/BytesStore.java:[23,18]
>  sun.nio.ch.DirectBuffer is internal proprietary API and may be removed in a 
> future release
> [WARNING] 
> /<>/src/main/java/net/openhft/chronicle/bytes/HeapBytesStore.java:[23,16]
>  sun.misc.Unsafe is internal proprietary API and may be removed in a future 
> release
> [WARNING] 
> /<>/src/main/java/net/openhft/chronicle/bytes/HeapBytesStore.java:[24,18]
>  sun.nio.ch.DirectBuffer is internal proprietary API and may be removed in a 
> future release
> [WARNING] 
> /<>/src/main/java/net/openhft/chronicle/bytes/NativeBytesStore.java:[27,18]
>  sun.nio.ch.DirectBuffer is internal proprietary API and may be removed in a 
> future release
> [WARNING] 
> /<>/src/main/java/net/openhft/chronicle/bytes/BytesStore.java:[42,76]
>  sun.nio.ch.DirectBuffer is internal proprietary API and may be removed in a 
> future release
> [WARNING] 
> /<>/src/main/java/net/openhft/chronicle/bytes/HeapBytesStore.java:[60,27]
>  sun.misc.Unsafe is internal proprietary API and may be removed in a future 
> release
> [WARNING] 
> /<>/src/main/java/net/openhft/chronicle/bytes/HeapBytesStore.java:[68,27]
>  sun.misc.Unsafe is internal proprietary API and may be removed in a future 
> release
> [WARNING] 
> /<>/src/main/java/net/openhft/chronicle/bytes/HeapBytesStore.java:[337,33]
>  sun.nio.ch.DirectBuffer is internal proprietary API and may be removed in a 
> future release
> [WARNING] 
> /<>/src/main/java/net/openhft/chronicle/bytes/NativeBytesStore.java:[142,22]
>  sun.nio.ch.DirectBuffer is internal proprietary API and may be removed in a 
> future release
> [WARNING] 
> /<>/src/mai

Bug#917730: caffeine: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2

2018-12-29 Thread Lucas Nussbaum
Source: caffeine
Version: 2.9.4-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3,bash-completion --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:217: python3.7 setup.py clean 
> Compiling for Locale: bg
> Compiling for Locale: ro
> Compiling for Locale: pl
> Compiling for Locale: en_GB
> Compiling for Locale: ru
> Compiling for Locale: gl
> Compiling for Locale: fr
> Compiling for Locale: it
> Compiling for Locale: nl
> Compiling for Locale: lt
> Compiling for Locale: pt
> Compiling for Locale: sv
> Compiling for Locale: da
> Compiling for Locale: ms
> Compiling for Locale: he
> Compiling for Locale: no
> Compiling for Locale: ar
> Compiling for Locale: pt_BR
> Compiling for Locale: eu
> Compiling for Locale: xh
> Compiling for Locale: eo
> Compiling for Locale: tr
> Compiling for Locale: bs
> Compiling for Locale: fi
> Compiling for Locale: vi
> Compiling for Locale: uk
> Compiling for Locale: sk
> Compiling for Locale: es
> Compiling for Locale: de
> Compiling for Locale: zh_TW
> Compiling for Locale: el
> Compiling for Locale: th
> Compiling for Locale: ja
> Compiling for Locale: hu
> Compiling for Locale: ca
> Compiling for Locale: cs
> running clean
> removing '/<>/.pybuild/cpython3_3.7_caffeine/build' (and 
> everything under it)
> 'build/bdist.linux-amd64' does not exist -- can't clean it
> 'build/scripts-3.7' does not exist -- can't clean it
>dh_clean -O--buildsystem=pybuild
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building caffeine using existing 
> ./caffeine_2.9.4.orig.tar.gz
> dpkg-source: warning: ignoring deletion of file 
> translations/caffeine-indicator.pot, use --include-removal to override
> dpkg-source: error: cannot represent change to 
> share/locale/ar/LC_MESSAGES/caffeine-indicator.mo: binary file contents 
> changed
> dpkg-source: error: add share/locale/ar/LC_MESSAGES/caffeine-indicator.mo in 
> debian/source/include-binaries if you want to store the modified binary in 
> the debian tarball
> dpkg-source: error: cannot represent change to 
> share/locale/bg/LC_MESSAGES/caffeine-indicator.mo: binary file contents 
> changed
> dpkg-source: error: add share/locale/bg/LC_MESSAGES/caffeine-indicator.mo in 
> debian/source/include-binaries if you want to store the modified binary in 
> the debian tarball
> dpkg-source: error: cannot represent change to 
> share/locale/bs/LC_MESSAGES/caffeine-indicator.mo: binary file contents 
> changed
> dpkg-source: error: add share/locale/bs/LC_MESSAGES/caffeine-indicator.mo in 
> debian/source/include-binaries if you want to store the modified binary in 
> the debian tarball
> dpkg-source: error: cannot represent change to 
> share/locale/ca/LC_MESSAGES/caffeine-indicator.mo: binary file contents 
> changed
> dpkg-source: error: add share/locale/ca/LC_MESSAGES/caffeine-indicator.mo in 
> debian/source/include-binaries if you want to store the modified binary in 
> the debian tarball
> dpkg-source: error: cannot represent change to 
> share/locale/cs/LC_MESSAGES/caffeine-indicator.mo: binary file contents 
> changed
> dpkg-source: error: add share/locale/cs/LC_MESSAGES/caffeine-indicator.mo in 
> debian/source/include-binaries if you want to store the modified binary in 
> the debian tarball
> dpkg-source: error: cannot represent change to 
> share/locale/da/LC_MESSAGES/caffeine-indicator.mo: binary file contents 
> changed
> dpkg-source: error: add share/locale/da/LC_MESSAGES/caffeine-indicator.mo in 
> debian/source/include-binaries if you want to store the modified binary in 
> the debian tarball
> dpkg-source: error: cannot represent change to 
> share/locale/de/LC_MESSAGES/caffeine-indicator.mo: binary file contents 
> changed
> dpkg-source: error: add share/locale/de/LC_MESSAGES/caffeine-indicator.mo in 
> debian/source/include-binaries if you want to store the modified binary in 
> the debian tarball
> dpkg-source: error: cannot represent change to 
> share/locale/el/LC_MESSAGES/caffeine-indicator.mo: binary file contents 
> changed
> dpkg-source: error: add share/locale/el/LC_MESSAGES/caffeine-indicator.mo in 
> debian/source/include-binaries if you want to store the modified binary in 
> the debian tarball
> dpkg-source: error: cannot represent change to 
> share/locale/en_GB/LC_MESSAGES/caffeine-indicator.mo: binary file contents 
> changed
> dpkg-sour

Bug#917735: bacula-doc: FTBFS: ! LaTeX Error: Missing \begin{document}.

2018-12-29 Thread Lucas Nussbaum
Source: bacula-doc
Version: 9.4.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>/manuals/en/misc'
> 
> Making output directories...
> echo "Output directories done"
> Output directories done
>  
> Building external references for misc
> This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) 
> (preloaded format=pdflatex)
>  restricted \write18 enabled.
> entering extended mode
> (./misc.tex
> LaTeX2e <2018-12-01>
> (../../../latex/borgmanual.cls
> Document Class: borgmanual 2014/03/02 v1.0 Standard bacula.org Book LaTeX 
> docum
> ent class
> (/usr/share/texlive/texmf-dist/tex/latex/eso-pic/eso-pic.sty
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/atbegshi.sty
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/infwarerr.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ltxcmds.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifpdf.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/xcolor/xcolor.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/color.cfg)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics-def/pdftex.def)))
> (../../../latex/atxy.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/graphics.cfg)))
> (/usr/share/texlive/texmf-dist/tex/latex/base/ifthen.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/base/bk10.clo))
> (/usr/share/texmf/tex/latex/html/html.sty
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/hyperref.sty
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-hyperref.sty
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-generic.sty))
> (/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/auxhook.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/kvoptions.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/pd1enc.def)
> (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/hyperref.cfg)
> (/usr/share/texlive/texmf-dist/tex/latex/url/url.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/hpdftex.def
> (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/rerunfilecheck.sty)))
> (/usr/share/texlive/texmf-dist/tex/latex/float/float.sty) (./bacula.sty
> (/usr/share/texlive/texmf-dist/tex/latex/carlisle/ltxtable.sty
> (/usr/share/texlive/texmf-dist/tex/latex/tools/tabularx.sty
> (/usr/share/texlive/texmf-dist/tex/latex/tools/array.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/tools/longtable.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/tools/varioref.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty
> (/usr/share/texlive/texmf-dist/tex/generic/babel/switch.def)
> (/usr/share/texlive/texmf-dist/tex/generic/babel-english/english.ldf
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.def
> (/usr/share/texlive/texmf-dist/tex/generic/babel/txtbabel.def
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/xr-hyper.sty
> 
> Package xr-hyper Warning: Load package `hyperref' after `xr-hyper'.
> 
> ) (/usr/share/texlive/texmf-dist/tex/latex/tools/xr.sty)
> (../../../latex/external-references.tex
> 
> Package xr Warning: 
> No file ../main/sqlite.aux
> LABELS NOT IMPORTED.
>  on input line 26.
> 
> 
> Package xr Warning: 
> No file ../main/fileset.aux
> LABELS NOT IMPORTED.
>  on input line 54.
> 
> 
> ! LaTeX Error: Missing \begin{document}.
> 
> See the LaTeX manual or LaTeX Companion for explanation.
> Type  H   for immediate help.
>  ...  
>   
> l.55 \externaldocument[main-]{../main/main}
>
> !  ==> Fatal error occurred, no output PDF file produced!
> Transcript written on ../pdf-and-html/misc/misc.log.
> make[2]: *** [Makefile:116: external-references] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2018/12/29/bacula-doc_9.4.1-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



Bug#917733: ocaml-atd: FTBFS: dh_install: missing files, aborting

2018-12-29 Thread Lucas Nussbaum
Source: ocaml-atd
Version: 2.0.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mkdir -p '/<>/debian/tmp/usr/bin'
> mkdir -p '/<>/debian/tmp//usr/lib/ocaml'
> jbuilder install --destdir=/<>/debian/tmp/usr 
> --libdir=/<>/debian/tmp//usr/lib/ocaml --verbose
> # Workspace root: /<>
> Running[0]: /usr/bin/nproc > /tmp/dune9c2993.output 2> /dev/null
> # # Workspace root: /<>
> # Auto-detected concurrency: 2
> Running[1]: /usr/bin/ocamlc.opt -config > /tmp/dune80f501.output
> # # # Workspace root: /<>
> # # Auto-detected concurrency: 2
> # Dune context:
> #  ((name default)
> #   (kind default)
> #   (profile release)
> #   (merlin true)
> #   (for_host ())
> #   (build_dir (In_build_dir default))
> #   (toplevel_path ())
> #   (ocaml_bin (External /usr/bin))
> #   (ocaml (External /usr/bin/ocaml))
> #   (ocamlc (External /usr/bin/ocamlc.opt))
> #   (ocamlopt ((External /usr/bin/ocamlopt.opt)))
> #   (ocamldep (External /usr/bin/ocamldep.opt))
> #   (ocamlmklib (External /usr/bin/ocamlmklib.opt))
> #   (env
> #((CAML_LD_LIBRARY_PATH
> #  /<>/_build/install/default/lib/stublibs)
> # (DUNE_CONFIGURATOR /usr/bin/ocamlc.opt)
> # (INSIDE_DUNE 1)
> # (MANPATH
> #  /<>/_build/install/default/bin)
> # (OCAMLFIND_IGNORE_DUPS_IN
> #  /<>/_build/install/default/lib)
> # (OCAMLPATH
> #  /<>/_build/install/default/lib)))
> #   (findlib_path ((External /usr/lib/ocaml)))
> #   (arch_sixtyfour true)
> #   (natdynlink_supported true)
> #   (supports_shared_libraries true)
> #   (opam_vars ())
> #   (ocaml_config
> #((version 4.05.0)
> # (standard_library_default /usr/lib/ocaml)
> # (standard_library /usr/lib/ocaml)
> # (standard_runtime /usr/bin/ocamlrun)
> # (ccomp_type cc)
> # (c_compiler gcc)
> # (ocamlc_cflags
> #  (-O2
> #   -fno-strict-aliasing
> #   -fwrapv
> #   -D_FILE_OFFSET_BITS=64
> #   -D_REENTRANT
> #   -fPIC))
> # (ocamlopt_cflags
> #  (-O2 -fno-strict-aliasing -fwrapv -D_FILE_OFFSET_BITS=64 -D_REENTRANT))
> # (bytecomp_c_compiler
> #  (gcc
> #   -O2
> #   -fno-strict-aliasing
> #   -fwrapv
> #   -D_FILE_OFFSET_BITS=64
> #   -D_REENTRANT
> #   -fPIC))
> # (bytecomp_c_libraries (-lm -ldl -lcurses -lpthread))
> # (native_c_compiler
> #  (gcc
> #   -O2
> #   -fno-strict-aliasing
> #   -fwrapv
> #   -D_FILE_OFFSET_BITS=64
> #   -D_REENTRANT))
> # (native_c_libraries (-lm -ldl))
> # (cc_profile (-pg))
> # (architecture amd64)
> # (model default)
> # (int_size 63)
> # (word_size 64)
> # (system linux)
> # (asm (as))
> # (asm_cfi_supported true)
> # (with_frame_pointers false)
> # (ext_exe )
> # (ext_obj .o)
> # (ext_asm .s)
> # (ext_lib .a)
> # (ext_dll .so)
> # (os_type Unix)
> # (default_executable_name a.out)
> # (systhread_supported true)
> # (host x86_64-pc-linux-gnu)
> # (target x86_64-pc-linux-gnu)
> # (profiling true)
> # (flambda false)
> # (spacetime false)
> # (safe_string false)
> # (exec_magic_number Caml1999X011)
> # (cmi_magic_number Caml1999I021)
> # (cmo_magic_number Caml1999O011)
> # (cma_magic_number Caml1999A012)
> # (cmx_magic_number Caml1999Y015)
> # (cmxa_magic_number Caml1999Z014)
> # (ast_impl_magic_number Caml1999M020)
> # (ast_intf_magic_number Caml1999N018)
> # (cmxs_magic_number Caml2007D002)
> # (cmt_magic_number Caml2012T009)
> # (natdynlink_supported true)
> # (supports_shared_libraries true)
> # (windows_unicode false)))
> #   (which
> #((ocaml ((External /usr/bin/ocaml)))
> # (ocamlc ((External /usr/bin/ocamlc.opt))
> Running[2]: /usr/bin/opam config var prefix > /tmp/dune68e10c.output
> Output[2]:
> [WARNING] Running as root is not recommended
> [ERROR] Opam has not been initialised, please run `opam init'
> Warning: Command [2] exited with code 50, but I'm ignoring it, hope that's OK.
> Installing 
> /<>/debian/tmp/usr/<>/debian/tmp/usr/lib/ocaml/atd/META
> Installing 
> /<>/debian/tmp/usr/<>/debian/tmp/usr/lib/ocaml/atd/annot.ml
> Installing 
> /<>/debian/tmp/usr/<>/debian/tmp/usr/lib/ocaml/atd/annot.mli
> Installing 

Bug#917731: ocaml-rope: FTBFS: dh_install: missing files, aborting

2018-12-29 Thread Lucas Nussbaum
Source: ocaml-rope
Version: 0.6.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mkdir -p '/<>/debian/tmp/usr/lib/ocaml'
> jbuilder install --destdir=/<>/debian/tmp 
> --libdir=/<>/debian/tmp/usr/lib/ocaml --verbose
> # Workspace root: /<>
> Running[0]: /usr/bin/nproc > /tmp/dunef1a789.output 2> /dev/null
> # # Workspace root: /<>
> # Auto-detected concurrency: 2
> Running[1]: /usr/bin/ocamlc.opt -config > /tmp/duneab278c.output
> # # # Workspace root: /<>
> # # Auto-detected concurrency: 2
> # Dune context:
> #  ((name default)
> #   (kind default)
> #   (profile release)
> #   (merlin true)
> #   (for_host ())
> #   (build_dir (In_build_dir default))
> #   (toplevel_path ())
> #   (ocaml_bin (External /usr/bin))
> #   (ocaml (External /usr/bin/ocaml))
> #   (ocamlc (External /usr/bin/ocamlc.opt))
> #   (ocamlopt ((External /usr/bin/ocamlopt.opt)))
> #   (ocamldep (External /usr/bin/ocamldep.opt))
> #   (ocamlmklib (External /usr/bin/ocamlmklib.opt))
> #   (env
> #((CAML_LD_LIBRARY_PATH
> #  /<>/_build/install/default/lib/stublibs)
> # (DUNE_CONFIGURATOR /usr/bin/ocamlc.opt)
> # (INSIDE_DUNE 1)
> # (MANPATH
> #  /<>/_build/install/default/bin)
> # (OCAMLFIND_IGNORE_DUPS_IN
> #  /<>/_build/install/default/lib)
> # (OCAMLPATH
> #  /<>/_build/install/default/lib)))
> #   (findlib_path ((External /usr/lib/ocaml)))
> #   (arch_sixtyfour true)
> #   (natdynlink_supported true)
> #   (supports_shared_libraries true)
> #   (opam_vars ())
> #   (ocaml_config
> #((version 4.05.0)
> # (standard_library_default /usr/lib/ocaml)
> # (standard_library /usr/lib/ocaml)
> # (standard_runtime /usr/bin/ocamlrun)
> # (ccomp_type cc)
> # (c_compiler gcc)
> # (ocamlc_cflags
> #  (-O2
> #   -fno-strict-aliasing
> #   -fwrapv
> #   -D_FILE_OFFSET_BITS=64
> #   -D_REENTRANT
> #   -fPIC))
> # (ocamlopt_cflags
> #  (-O2 -fno-strict-aliasing -fwrapv -D_FILE_OFFSET_BITS=64 -D_REENTRANT))
> # (bytecomp_c_compiler
> #  (gcc
> #   -O2
> #   -fno-strict-aliasing
> #   -fwrapv
> #   -D_FILE_OFFSET_BITS=64
> #   -D_REENTRANT
> #   -fPIC))
> # (bytecomp_c_libraries (-lm -ldl -lcurses -lpthread))
> # (native_c_compiler
> #  (gcc
> #   -O2
> #   -fno-strict-aliasing
> #   -fwrapv
> #   -D_FILE_OFFSET_BITS=64
> #   -D_REENTRANT))
> # (native_c_libraries (-lm -ldl))
> # (cc_profile (-pg))
> # (architecture amd64)
> # (model default)
> # (int_size 63)
> # (word_size 64)
> # (system linux)
> # (asm (as))
> # (asm_cfi_supported true)
> # (with_frame_pointers false)
> # (ext_exe )
> # (ext_obj .o)
> # (ext_asm .s)
> # (ext_lib .a)
> # (ext_dll .so)
> # (os_type Unix)
> # (default_executable_name a.out)
> # (systhread_supported true)
> # (host x86_64-pc-linux-gnu)
> # (target x86_64-pc-linux-gnu)
> # (profiling true)
> # (flambda false)
> # (spacetime false)
> # (safe_string false)
> # (exec_magic_number Caml1999X011)
> # (cmi_magic_number Caml1999I021)
> # (cmo_magic_number Caml1999O011)
> # (cma_magic_number Caml1999A012)
> # (cmx_magic_number Caml1999Y015)
> # (cmxa_magic_number Caml1999Z014)
> # (ast_impl_magic_number Caml1999M020)
> # (ast_intf_magic_number Caml1999N018)
> # (cmxs_magic_number Caml2007D002)
> # (cmt_magic_number Caml2012T009)
> # (natdynlink_supported true)
> # (supports_shared_libraries true)
> # (windows_unicode false)))
> #   (which
> #((ocaml ((External /usr/bin/ocaml)))
> # (ocamlc ((External /usr/bin/ocamlc.opt))
> Running[2]: /usr/bin/opam config var prefix > /tmp/dunec6d5c6.output
> Output[2]:
> [WARNING] Running as root is not recommended
> [ERROR] Opam has not been initialised, please run `opam init'
> Warning: Command [2] exited with code 50, but I'm ignoring it, hope that's OK.
> Installing 
> /<>/debian/tmp/<>/debian/tmp/usr/lib/ocaml/rope/META
> Installing 
> /<>/debian/tmp/<>/debian/tmp/usr/lib/ocaml/rope/opam
> Installing 
> /<>/debian/tmp/<>/debian/tmp/usr/lib/ocaml/rope/rope.a
> Installing 
> /<>/debian/tmp/<>/debian/tmp/usr/lib/ocaml/rope/rope.cma
> I

Bug#917734: flexpart: FTBFS: Fatal Error: Can't open module file 'grib_api.mod' for reading at (1): No such file or directory

2018-12-29 Thread Lucas Nussbaum
Source: flexpart
Version: 9.02-19
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> gfortran -c -O2 -I/usr/include/x86_64-linux-gnu -g -mcmodel=medium  -O2 
> -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include 
> par_mod.f90
> gfortran -c -O2 -I/usr/include/x86_64-linux-gnu -g -mcmodel=medium  -O2 
> -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include 
> com_mod.f90
> gfortran -c -O2 -I/usr/include/x86_64-linux-gnu -g -mcmodel=medium  -O2 
> -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include 
> conv_mod.f90
> gfortran -c -O2 -I/usr/include/x86_64-linux-gnu -g -mcmodel=medium  -O2 
> -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include 
> hanna_mod.f90
> gfortran -c -O2 -I/usr/include/x86_64-linux-gnu -g -mcmodel=medium  -O2 
> -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include 
> interpol_mod.f90
> gfortran -c -O2 -I/usr/include/x86_64-linux-gnu -g -mcmodel=medium  -O2 
> -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include 
> cmapf_mod.f90
> gfortran -c -O2 -I/usr/include/x86_64-linux-gnu -g -mcmodel=medium  -O2 
> -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include 
> unc_mod.f90
> gfortran -c -O2 -I/usr/include/x86_64-linux-gnu -g -mcmodel=medium  -O2 
> -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include 
> oh_mod.f90
> gfortran -c -O2 -I/usr/include/x86_64-linux-gnu -g -mcmodel=medium  -O2 
> -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include 
> xmass_mod.f90
> gfortran -c -O2 -I/usr/include/x86_64-linux-gnu -g -mcmodel=medium  -O2 
> -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include 
> flux_mod.f90
> gfortran -c -O2 -I/usr/include/x86_64-linux-gnu -g -mcmodel=medium  -O2 
> -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include 
> point_mod.f90
> gfortran -c -O2 -I/usr/include/x86_64-linux-gnu -g -mcmodel=medium  -O2 
> -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include 
> outg_mod.f90
> gfortran -c -O2 -I/usr/include/x86_64-linux-gnu -g -mcmodel=medium  -O2 
> -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include 
> writeheader.f90
> gfortran -c -O2 -I/usr/include/x86_64-linux-gnu -g -mcmodel=medium  -O2 
> -fdefault-real-8 -fconvert=little-endian -frecord-marker=4 -I/usr/include 
> assignland.f90
> assignland.f90:181:16:
> 
>do l=1,numbnests
>   2
>  do ix=0,nxn(l)-1
> 1
> Warning: Array reference at (1) out of bounds (1 > 0) in loop beginning at (2)
> assignland.f90:182:18:
> 
> assignland.f90:180:18:
> 
>do l=1,numbnests
>   2
> assignland.f90:182:18:
> 
>do jy=0,nyn(l)-1
>   1
> Warning: Array reference at (1) out of bounds (1 > 0) in loop beginning at (2)
> assignland.f90:185:28:
> 
> assignland.f90:180:18:
> 
>do l=1,numbnests
>   2  
> assignland.f90:185:28:
> 
>xlandusen(ix,jy,k,l)=0.
> 1
> Warning: Array reference at (1) out of bounds (1 > 0) in loop beginning at (2)
> assignland.f90:185:20:
> 
> assignland.f90:181:20:
> 
>  do ix=0,nxn(l)-1
> 2
> assignland.f90:185:20:
> 
>xlandusen(ix,jy,k,l)=0.
> 1
> Warning: Array reference at (1) out of bounds (0 > -1) in loop beginning at 
> (2)
> assignland.f90:185:23:
> 
> assignland.f90:182:22:
> 
>do jy=0,nyn(l)-1
>   2 
> assignland.f90:185:23:
> 
>xlandusen(ix,jy,k,l)=0.
>1
> Warning: Array reference at (1) out of bounds (0 > -1) in loop beginning at 
> (2)
> assignland.f90:188:47:
> 
> assignland.f90:180:18:
> 
>do l=1,numbnests
>   2 
> assignland.f90:188:47:
> 
> xlon=(ix+(iix-1)/real(nrefine))*dxn(l)+xlon0n(l)
>1
> Warning: Array reference at (1) out of bounds (1 > 0) in loop beginning at (2)
> assignland.f90:188:57:
> 
> assignland.f90:180:18:
> 
>do l=1,numbnests
>   2   
> assignland.f90:188:57:
> 
> xlon=(ix+(iix-1)/real(nrefine))*dxn(l)+xlon0n(l)
>  1
> Warning: Array reference a

Bug#917736: openhft-chronicle-core: FTBFS: [ERROR] /<>/src/main/java/net/openhft/chronicle/core/io/IOTools.java:[32,27] cannot find symbol

2018-12-29 Thread Lucas Nussbaum
Source: openhft-chronicle-core
Version: 1.1.8-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=maven
>dh_update_autotools_config -O--buildsystem=maven
>dh_auto_configure -O--buildsystem=maven
>   mh_patchpoms -plibopenhft-chronicle-core-java --debian-build 
> --keep-pom-version --maven-repo=/<>/debian/maven-repo
>dh_auto_build -O--buildsystem=maven
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
> -DskipTests -Dnotimestamp=true -Dlocale=en_US
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by 
> com.google.inject.internal.cglib.core.$ReflectUtils$1 
> (file:/usr/share/maven/lib/guice.jar) to method 
> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
> WARNING: Please consider reporting this to the maintainers of 
> com.google.inject.internal.cglib.core.$ReflectUtils$1
> WARNING: Use --illegal-access=warn to enable warnings of further illegal 
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> [INFO] Scanning for projects...
> [INFO] 
> [INFO] -< net.openhft:chronicle-core 
> >-
> [INFO] Building OpenHFT/Chronicle-Core 1.1.8
> [INFO] ---[ bundle 
> ]---
> [INFO] 
> [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ 
> chronicle-core ---
> [WARNING] Using platform encoding (ANSI_X3.4-1968 actually) to copy filtered 
> resources, i.e. build is platform dependent!
> [INFO] skip non existing resourceDirectory /<>/src/main/resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.8.0:compile (default-compile) @ 
> chronicle-core ---
> [INFO] Changes detected - recompiling the module!
> [WARNING] File encoding has not been set, using platform encoding 
> ANSI_X3.4-1968, i.e. build is platform dependent!
> [INFO] Compiling 58 source files to /<>/target/classes
> [INFO] 
> /<>/src/main/java/net/openhft/chronicle/core/util/ObjectUtils.java:
>  Some input files use unchecked or unsafe operations.
> [INFO] 
> /<>/src/main/java/net/openhft/chronicle/core/util/ObjectUtils.java:
>  Recompile with -Xlint:unchecked for details.
> [INFO] -
> [WARNING] COMPILATION WARNING : 
> [INFO] -
> [WARNING] 
> /<>/src/main/java/net/openhft/chronicle/core/UnsafeMemory.java:[20,16]
>  sun.misc.Unsafe is internal proprietary API and may be removed in a future 
> release
> [WARNING] 
> /<>/src/main/java/net/openhft/chronicle/core/OS.java:[21,18] 
> sun.nio.ch.FileChannelImpl is internal proprietary API and may be removed in 
> a future release
> [WARNING] 
> /<>/src/main/java/net/openhft/chronicle/core/UnsafeMemory.java:[26,12]
>  sun.misc.Unsafe is internal proprietary API and may be removed in a future 
> release
> [WARNING] 
> /<>/src/main/java/net/openhft/chronicle/core/UnsafeMemory.java:[32,48]
>  sun.misc.Unsafe is internal proprietary API and may be removed in a future 
> release
> [WARNING] 
> /<>/src/main/java/net/openhft/chronicle/core/UnsafeMemory.java:[33,27]
>  sun.misc.Unsafe is internal proprietary API and may be removed in a future 
> release
> [WARNING] 
> /<>/src/main/java/net/openhft/chronicle/core/UnsafeMemory.java:[265,34]
>  sun.misc.Unsafe is internal proprietary API and may be removed in a future 
> release
> [WARNING] 
> /<>/src/main/java/net/openhft/chronicle/core/OS.java:[273,29] 
> sun.nio.ch.FileChannelImpl is internal proprietary API and may be removed in 
> a future release
> [INFO] 7 warnings 
> [INFO] -
> [INFO] -
> [ERROR] COMPILATION ERROR : 
> [INFO] -
> [ERROR] 
> /<>/src/main/java/net/openhft/chronicle/core/io/IOTools.j

Bug#917728: flextra: FTBFS: Fatal Error: Can't open module file 'grib_api.mod' for reading at (1): No such file or directory

2018-12-29 Thread Lucas Nussbaum
Source: flextra
Version: 5.0-10
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> gfortran-8 -I/usr/include/x86_64-linux-gnu -g -fPIC  -fconvert=little-endian 
> -frecord-marker=4  -I/usr/include   -c -o caldate.o caldate.f
> gfortran-8 -I/usr/include/x86_64-linux-gnu -g -fPIC  -fconvert=little-endian 
> -frecord-marker=4  -I/usr/include   -c -o openoutput.o openoutput.f
> gfortran-8 -I/usr/include/x86_64-linux-gnu -g -fPIC  -fconvert=little-endian 
> -frecord-marker=4  -I/usr/include   -c -o checklimits.o checklimits.f
> gfortran-8 -I/usr/include/x86_64-linux-gnu -g -fPIC  -fconvert=little-endian 
> -frecord-marker=4  -I/usr/include   -c -o coordtrafo.o coordtrafo.f
> gfortran-8 -I/usr/include/x86_64-linux-gnu -g -fPIC  -fconvert=little-endian 
> -frecord-marker=4  -I/usr/include   -c -o orolininterpol.o orolininterpol.f
> gfortran-8 -I/usr/include/x86_64-linux-gnu -g -fPIC  -fconvert=little-endian 
> -frecord-marker=4  -I/usr/include   -c -o etatrafo.o etatrafo.f
> gfortran-8 -I/usr/include/x86_64-linux-gnu -g -fPIC  -fconvert=little-endian 
> -frecord-marker=4  -I/usr/include   -c -o petters.o petters.f
> gfortran-8 -I/usr/include/x86_64-linux-gnu -g -fPIC  -fconvert=little-endian 
> -frecord-marker=4  -I/usr/include   -c -o eta.ecmwf.o eta.ecmwf.f
> gfortran-8 -I/usr/include/x86_64-linux-gnu -g -fPIC  -fconvert=little-endian 
> -frecord-marker=4  -I/usr/include   -c -o FLEXTRA.o FLEXTRA.f
> gfortran-8 -I/usr/include/x86_64-linux-gnu -g -fPIC  -fconvert=little-endian 
> -frecord-marker=4  -I/usr/include   -c -o pp.ecmwf.o pp.ecmwf.f
> gfortran-8 -I/usr/include/x86_64-linux-gnu -g -fPIC  -fconvert=little-endian 
> -frecord-marker=4  -I/usr/include   -c -o geteta.o geteta.f
> gfortran-8 -I/usr/include/x86_64-linux-gnu -g -fPIC  -fconvert=little-endian 
> -frecord-marker=4  -I/usr/include   -c -o getfields.o getfields.f
> gfortran-8 -I/usr/include/x86_64-linux-gnu -g -fPIC  -fconvert=little-endian 
> -frecord-marker=4  -I/usr/include   -c -o pvinterpol.o pvinterpol.f
> gfortran-8 -I/usr/include/x86_64-linux-gnu -g -fPIC  -fconvert=little-endian 
> -frecord-marker=4  -I/usr/include   -c -o getheight.o getheight.f
> gfortran-8 -I/usr/include/x86_64-linux-gnu -g -fPIC  -fconvert=little-endian 
> -frecord-marker=4  -I/usr/include   -c -o random.o random.f
> gfortran-8 -I/usr/include/x86_64-linux-gnu -g -fPIC  -fconvert=little-endian 
> -frecord-marker=4  -I/usr/include   -c -o readavailable.o readavailable.f
> gfortran-8 -I/usr/include/x86_64-linux-gnu -g -fPIC  -fconvert=little-endian 
> -frecord-marker=4  -I/usr/include   -c -o getwind.o getwind.f
> gfortran-8 -I/usr/include/x86_64-linux-gnu -g -fPIC  -fconvert=little-endian 
> -frecord-marker=4  -I/usr/include   -c -o readcommand.o readcommand.f
> gfortran-8 -I/usr/include/x86_64-linux-gnu -g -fPIC  -fconvert=little-endian 
> -frecord-marker=4  -I/usr/include   -c -o gridcheck.o gridcheck.f
> gridcheck.f:52:9:
> 
>use grib_api
>  1
> Fatal Error: Can't open module file 'grib_api.mod' for reading at (1): No 
> such file or directory
> compilation terminated.
> make[2]: *** [: gridcheck.o] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2018/12/29/flextra_5.0-10_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



Bug#917729: weresync: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2

2018-12-29 Thread Lucas Nussbaum
Source: weresync
Version: 1.0.7-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3,sphinxdoc --buildsystem=pybuild 
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:217: python3.7 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.7/build' (and everything under 
> it)
> 'build/bdist.linux-amd64' does not exist -- can't clean it
> 'build/scripts-3.7' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building weresync using existing 
> ./weresync_1.0.7.orig.tar.gz
> dpkg-source: error: cannot represent change to 
> src/weresync/resources/locale/en/LC_MESSAGES/weresync.mo: binary file 
> contents changed
> dpkg-source: error: add 
> src/weresync/resources/locale/en/LC_MESSAGES/weresync.mo in 
> debian/source/include-binaries if you want to store the modified binary in 
> the debian tarball
> dpkg-source: error: unrepresentable changes to source
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> 
> Build finished at 2018-12-29T12:40:29Z

The full build log is available from:
   http://aws-logs.debian.net/2018/12/29/weresync_1.0.7-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



Bug#917726: globus-gass-copy: FTBFS: tests failed

2018-12-29 Thread Lucas Nussbaum
Source: globus-gass-copy
Version: 10.3-2
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[4]: Entering directory '/<>/test'
> FAIL: guc-fw.pl
> FAIL: guc-pp-cc.pl
> FAIL: guc-stack.pl
> FAIL: guc-cc.pl
> FAIL: guc-cc-fast.pl
> FAIL: guc-cc-p2.pl
> FAIL: guc-cc-p4.pl
> FAIL: guc-cc-stripe.pl
> FAIL: guc-cc-stripe-p4.pl
> 
>globus_gass_copy 10.3: test/test-suite.log
> 
> 
> # TOTAL: 9
> # PASS:  0
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  9
> # XPASS: 0
> # ERROR: 0
> 
> .. contents:: :depth: 2
> 
> FAIL: guc-fw.pl
> ===
> 
> # Started server at port 45897
> 1..32
> # stderr:
> # 
> # error: globus_ftp_client: the server responded with an error
> # 530 Login incorrect. : Access denied, user's system account is disabled.
> 
> # 
> not ok 1 - guc fw -nodcau exits with 0
> #   Failed test 'guc fw -nodcau exits with 0'
> #   at ./guc-fw.pl line 121.
> not ok 2 - guc-fw data compare
> #   Failed test 'guc-fw data compare'
> #   at ./guc-fw.pl line 124.
> # stderr:
> # 
> # error: globus_ftp_client: the server responded with an error
> # 530 Login incorrect. : Access denied, user's system account is disabled.
> 
> # 
> not ok 3 - guc fw exits with 0
> #   Failed test 'guc fw exits with 0'
> #   at ./guc-fw.pl line 121.
> not ok 4 - guc-fw data compare
> #   Failed test 'guc-fw data compare'
> #   at ./guc-fw.pl line 124.
> # stderr:
> # 
> # error: globus_ftp_client: the server responded with an error
> # 530 Login incorrect. : Access denied, user's system account is disabled.
> 
> # 
> not ok 5 - guc fw -dcsafe exits with 0
> #   Failed test 'guc fw -dcsafe exits with 0'
> #   at ./guc-fw.pl line 121.
> not ok 6 - guc-fw data compare
> #   Failed test 'guc-fw data compare'
> #   at ./guc-fw.pl line 124.
> # stderr:
> # 
> # error: globus_ftp_client: the server responded with an error
> # 530 Login incorrect. : Access denied, user's system account is disabled.
> 
> # 
> not ok 7 - guc fw -dcpriv exits with 0
> #   Failed test 'guc fw -dcpriv exits with 0'
> #   at ./guc-fw.pl line 121.
> not ok 8 - guc-fw data compare
> #   Failed test 'guc-fw data compare'
> #   at ./guc-fw.pl line 124.
> # stderr:
> # 
> # error: globus_ftp_client: the server responded with an error
> # 530 Login incorrect. : Access denied, user's system account is disabled.
> 
> # 
> not ok 9 - guc fw -fast -nodcau exits with 0
> #   Failed test 'guc fw -fast -nodcau exits with 0'
> #   at ./guc-fw.pl line 121.
> not ok 10 - guc-fw data compare
> #   Failed test 'guc-fw data compare'
> #   at ./guc-fw.pl line 124.
> # stderr:
> # 
> # error: globus_ftp_client: the server responded with an error
> # 530 Login incorrect. : Access denied, user's system account is disabled.
> 
> # 
> not ok 11 - guc fw -fast exits with 0
> #   Failed test 'guc fw -fast exits with 0'
> #   at ./guc-fw.pl line 121.
> not ok 12 - guc-fw data compare
> #   Failed test 'guc-fw data compare'
> #   at ./guc-fw.pl line 124.
> # stderr:
> # 
> # error: globus_ftp_client: the server responded with an error
> # 530 Login incorrect. : Access denied, user's system account is disabled.
> 
> # 
> not ok 13 - guc fw -fast -dcsafe exits with 0
> #   Failed test 'guc fw -fast -dcsafe exits with 0'
> #   at ./guc-fw.pl line 121.
> not ok 14 - guc-fw data compare
> #   Failed test 'guc-fw data compare'
> #   at ./guc-fw.pl line 124.
> # stderr:
> # 
> # error: globus_ftp_client: the server responded with an error
> # 530 Login incorrect. : Access denied, user's system account is disabled.
> 
> # 
> not ok 15 - guc fw -fast -dcpriv exits with 0
> #   Failed test 'guc fw -fast -dcpriv exits with 0'
> #   at ./guc-fw.pl line 121.
> not ok 16 - guc-fw data compare
> #   Failed test 'guc-fw data compare'
> #   at ./guc-fw.pl line 124.
> # stderr:
> # 
> # error: globus_ftp_client: the server responded with an error
> # 530 Login incorrect. : Access denied, user's system account is disabled.
> 
> # 
> not ok 17 - guc fw -p 2 -nodcau exits with 0
> #   Failed test 'guc fw -p 2 -nodcau exits with 0'
> #   at ./guc-fw.pl line 121.
> not ok 18 - guc-fw data compare
> #   Failed test 'g

Bug#917738: openhft-chronicle-threads: FTBFS: [ERROR] /<>/src/main/java/net/openhft/chronicle/threads/MonitorEventLoop.java:[123,32] cannot find symbol

2018-12-29 Thread Lucas Nussbaum
Source: openhft-chronicle-threads
Version: 1.1.6-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=maven
>dh_update_autotools_config -O--buildsystem=maven
>dh_auto_configure -O--buildsystem=maven
>   mh_patchpoms -plibopenhft-chronicle-threads-java --debian-build 
> --keep-pom-version --maven-repo=/<>/debian/maven-repo
>dh_auto_build -O--buildsystem=maven
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
> -DskipTests -Dnotimestamp=true -Dlocale=en_US
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by 
> com.google.inject.internal.cglib.core.$ReflectUtils$1 
> (file:/usr/share/maven/lib/guice.jar) to method 
> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
> WARNING: Please consider reporting this to the maintainers of 
> com.google.inject.internal.cglib.core.$ReflectUtils$1
> WARNING: Use --illegal-access=warn to enable warnings of further illegal 
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> [INFO] Scanning for projects...
> [INFO] 
> [INFO] ---< net.openhft:chronicle-threads 
> >
> [INFO] Building OpenHFT/Chronicle-Threads 1.1.6
> [INFO] ---[ bundle 
> ]---
> [INFO] 
> [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ 
> chronicle-threads ---
> [WARNING] Using platform encoding (ANSI_X3.4-1968 actually) to copy filtered 
> resources, i.e. build is platform dependent!
> [INFO] skip non existing resourceDirectory /<>/src/main/resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.8.0:compile (default-compile) @ 
> chronicle-threads ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 14 source files to /<>/target/classes
> [INFO] -
> [ERROR] COMPILATION ERROR : 
> [INFO] -
> [ERROR] 
> /<>/src/main/java/net/openhft/chronicle/threads/MonitorEventLoop.java:[28,20]
>  package javax.xml.ws does not exist
> [ERROR] 
> /<>/src/main/java/net/openhft/chronicle/threads/MonitorEventLoop.java:[123,32]
>  cannot find symbol
>   symbol:   class WebServiceException
>   location: class net.openhft.chronicle.threads.MonitorEventLoop
> [INFO] 2 errors 
> [INFO] -
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  2.117 s
> [INFO] Finished at: 2018-12-29T13:57:53Z
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile 
> (default-compile) on project chronicle-threads: Compilation failure: 
> Compilation failure: 
> [ERROR] 
> /<>/src/main/java/net/openhft/chronicle/threads/MonitorEventLoop.java:[28,20]
>  package javax.xml.ws does not exist
> [ERROR] 
> /<>/src/main/java/net/openhft/chronicle/threads/MonitorEventLoop.java:[123,32]
>  cannot find symbol
> [ERROR]   symbol:   class WebServiceException
> [ERROR]   location: class net.openhft.chronicle.threads.MonitorEventLoop
> [ERROR] -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<>

Bug#917727: openhft-lang: FTBFS: [ERROR] /<>/lang/src/main/java/net/openhft/lang/io/IOTools.java:[85,13] cannot find symbol

2018-12-29 Thread Lucas Nussbaum
Source: openhft-lang
Version: 6.7.6-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=maven
>dh_update_autotools_config -O--buildsystem=maven
>dh_auto_configure -O--buildsystem=maven
>   mh_patchpoms -plibopenhft-lang-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>dh_auto_build -O--buildsystem=maven
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
> -DskipTests -Dnotimestamp=true -Dlocale=en_US
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by 
> com.google.inject.internal.cglib.core.$ReflectUtils$1 
> (file:/usr/share/maven/lib/guice.jar) to method 
> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
> WARNING: Please consider reporting this to the maintainers of 
> com.google.inject.internal.cglib.core.$ReflectUtils$1
> WARNING: Use --illegal-access=warn to enable warnings of further illegal 
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO] 
> [INFO] OpenHFT/Java-Lang/lang  
> [bundle]
> [INFO] Java Lang Parent   
> [pom]
> [INFO] 
> [INFO] --< net.openhft:lang 
> >--
> [INFO] Building OpenHFT/Java-Lang/lang 6.7.6  
> [1/2]
> [INFO] ---[ bundle 
> ]---
> [INFO] 
> [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ lang 
> ---
> [WARNING] Using platform encoding (ANSI_X3.4-1968 actually) to copy filtered 
> resources, i.e. build is platform dependent!
> [INFO] skip non existing resourceDirectory 
> /<>/lang/src/main/resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.8.0:compile (default-compile) @ lang ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 165 source files to /<>/lang/target/classes
> [INFO] 
> /<>/lang/src/main/java/net/openhft/lang/model/DataValueClassCache.java:
>  Some input files use or override a deprecated API.
> [INFO] 
> /<>/lang/src/main/java/net/openhft/lang/model/DataValueClassCache.java:
>  Recompile with -Xlint:deprecation for details.
> [INFO] 
> /<>/lang/src/main/java/net/openhft/lang/locks/NativeAtomicAccess.java:
>  Some input files use unchecked or unsafe operations.
> [INFO] 
> /<>/lang/src/main/java/net/openhft/lang/locks/NativeAtomicAccess.java:
>  Recompile with -Xlint:unchecked for details.
> [INFO] -
> [WARNING] COMPILATION WARNING : 
> [INFO] -
> [WARNING] 
> /<>/lang/src/main/java/net/openhft/lang/io/NativeBytes.java:[22,16]
>  sun.misc.Unsafe is internal proprietary API and may be removed in a future 
> release
> [WARNING] 
> /<>/lang/src/main/java/net/openhft/lang/io/ChronicleUnsafe.java:[20,16]
>  sun.misc.Unsafe is internal proprietary API and may be removed in a future 
> release
> [WARNING] 
> /<>/lang/src/main/java/net/openhft/lang/io/MappedMemory.java:[21,18]
>  sun.nio.ch.DirectBuffer is internal proprietary API and may be removed in a 
> future release
> [WARNING] 
> /<>/lang/src/main/java/net/openhft/lang/io/DirectByteBufferBytes.java:[18,18]
>  sun.nio.ch.DirectBuffer is internal proprietary API and may be removed in a 
> future release
> [WARNING] 
> /<>/lang/src/main/java/net/openhft/lang/io/MappedNativeBytes.java:[21,16]
>  sun.misc.Unsafe is internal proprietary API and may be removed in a future 
> release
> [WARNING] 
> /<>/lang/src/main/java/net/openhft/lang/io/VanillaMappedBytes.java:[19,18]
>  sun.nio.ch.DirectBuffer is internal proprietary API and may be removed in a 
> future release
> [WARNIN

Bug#915424: Openfortivpn Patch

2018-12-29 Thread Helmut Grohne
Hi Daniel,

On Sat, Dec 29, 2018 at 01:00:08PM -0500, Daniel Echeverry wrote:
> Thanks for your reply, I was trying build this new version with
> pbuilder --host-arch=... but doesn't build fine (please log attached),
> However I will upload this new version to unstable. Feel free to sent
> me the new patch and I will apply it in a new revision and forward to
> the upstream.

openfortivpn is one of the packages that need extra information about
the host architecture. For autotools this is done using "cache
variables". So for cross building openfortivpn to linux-any (we don't
have non-linux release architectures at the moment), you need to provide
the following value:

ac_cv_file__proc_net_route=yes

The easiest way of doing so is passing it as an environment variable to
the build.

If the patch from bug #915424 got applied upstream, you should no longer
need other cache variables. So you can easily tell whether that is the
case.

Thank you for trying

Helmut



Bug#917724: RFS: budgie-extras/0.7.0-1

2018-12-29 Thread David Mohammed
Package: sponsorship-requests
Severity: normal

  Dear mentors,

  I am looking for a sponsor for my package "budgie-extras"

 * Package name: budgie-extras
   Version : 0.7.0-1
Upstream Author : Ubuntu Budgie Developers
 * URL : https://github.com/ubuntubudgie/budgie-extras
 * License : GPL-3+
   Section : misc

  It builds those binary packages:

budgie-app-launcher-applet - Applet to provide an alternative
means to launch applications
 budgie-clockworks-applet - Applet to display clock across multiple time zones
 budgie-countdown-applet - Applet providing a countdown capability on
the Budgie Desktop
 budgie-dropby-applet - Applet to popup when a USB device is connected
 budgie-extras-common - Shared component of budgie-extras applets
 budgie-hotcorners-applet - Applet providing hotcorners capabilities
for the Budgie Desktop
 budgie-kangaroo-applet - Applet to allow quick file-browsing
 budgie-keyboard-autoswitch-applet - Applet adding the ability to set
a different keyboard layout per
 budgie-previews-applet - Applet providing window previews
capabilities for the Budgie Desk
 budgie-quicknote-applet - Applet providing simple notes capability
for the Budgie Desktop
 budgie-recentlyused-applet - Applet displays files recently accessed
for the Budgie Desktop
 budgie-rotation-lock-applet - Applet to lock or unlock the screen rotation
 budgie-showtime-applet - Applet displaying date and time on the Budgie Desktop
 budgie-trash-applet - Applet allows access to trash capabilities for
the Budgie Desktop
 budgie-weathershow-applet - Applet to display the weather and forecast
 budgie-window-mover-applet - Applet allows moving windows between
workspaces for the Budgie De
 budgie-workspace-overview-applet - Applet providing quick access to
workspaces for the Budgie Deskto
 budgie-workspace-wallpaper-applet - Applet providing per workspace wallpaper

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

  https://mentors.debian.net/package/budgie-extras


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

dget -x 
https://mentors.debian.net/debian/pool/main/b/budgie-extras/budgie-extras_0.7.0-1.dsc

Notes:
I am the debian maintainer - this request is due to the new/changed
binaries which is not part of my upload rights

lintiian -i -I --pedantic run on the built source and is lintian free
check-all-the-things run on the source and corrections made to the source
pbuilder-dist run to ensure builds correctly for unstable

This upload introduces new built binaries to be authorised by
archive-admins via the NEW queue:
- budgie-weathershow-applet
- budgie-extras-common

  Changes since the last upload:

* New release
- See ChangeLog
  * Packaging Changes
- remove unneeded clockworks doc
- drop existing patchset since now included in the new release
- Control: budgie-weather-applet build
  and runtime dependencies updated due to python to Vala rewrite
- Control: Add budgie-extras-common build together with dependency
  updates for several applets where they share the extras common
  component
- Control: several build install changes where budgie-extras-common
  now replaces individual component installations
- Copyright: updates due to extra licensing for the release
  including year change
- Control: Bump StandardsVersion - no changes required


  Regards,
   David Mohammed



Bug#917639: gnome-disk-utility FTCBFS: broken fallocate check

2018-12-29 Thread Jeremy Bicha
Control: forwarded -1
https://gitlab.gnome.org/GNOME/gnome-disk-utility/merge_requests/11

Thanks, let's see what upstream says about your patch.

Jeremy Bicha



Bug#917714: lizzie: FTBFS: dh_auto_test: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirec

2018-12-29 Thread Lucas Nussbaum
Source: lizzie
Version: 0.6+dfsg1-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>/lizzie-0.6+dfsg1'
> HOME=/<>/lizzie-0.6+dfsg1/debian/runtest xvfb-run -a dh_auto_test
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<>/lizzie-0.6\+dfsg1 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml 
> -Ddebian.dir=/<>/lizzie-0.6\+dfsg1/debian 
> -Dmaven.repo.local=/<>/lizzie-0.6\+dfsg1/debian/maven-repo 
> --batch-mode test
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by 
> com.google.inject.internal.cglib.core.$ReflectUtils$1 
> (file:/usr/share/maven/lib/guice.jar) to method 
> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
> WARNING: Please consider reporting this to the maintainers of 
> com.google.inject.internal.cglib.core.$ReflectUtils$1
> WARNING: Use --illegal-access=warn to enable warnings of further illegal 
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> [INFO] Scanning for projects...
> [INFO] 
> [INFO] -< featurecat:lizzie 
> >--
> [INFO] Building lizzie 0.6
> [INFO] [ jar 
> ]-
> [WARNING] The artifact org.json:json:jar:debian-latest has been relocated to 
> org.json:json:jar:debian
> [INFO] 
> [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ 
> lizzie ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 7 resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.8.0:compile (default-compile) @ lizzie ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO] 
> [INFO] --- maven-resources-plugin:3.1.0:testResources (default-testResources) 
> @ lizzie ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory 
> /<>/lizzie-0.6+dfsg1/src/test/resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.8.0:testCompile (default-testCompile) @ 
> lizzie ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO] 
> [INFO] --- maven-surefire-plugin:2.22.1:test (default-test) @ lizzie ---
> [INFO] 
> [INFO] ---
> [INFO]  T E S T S
> [INFO] ---
> [INFO] Running featurecat.lizzie.rules.SGFParserTest
> Creating config file /home/user42/.config/leela-zero/lizzie-config.txt
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.072 
> s <<< FAILURE! - in featurecat.lizzie.rules.SGFParserTest
> [ERROR] run(featurecat.lizzie.rules.SGFParserTest)  Time elapsed: 0.03 s  <<< 
> ERROR!
> java.io.IOException: No such file or directory
>   at featurecat.lizzie.rules.SGFParserTest.run(SGFParserTest.java:24)
> 
> [INFO] Running featurecat.lizzie.analysis.MoveDataTest
> [INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 
> s - in featurecat.lizzie.analysis.MoveDataTest
> [INFO] 
> [INFO] Results:
> [INFO] 
> [ERROR] Errors: 
> [ERROR]   SGFParserTest.run:24 ? IO No such file or directory
> [INFO] 
> [ERROR] Tests run: 7, Failures: 0, Errors: 1, Skipped: 0
> [INFO] 
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  11.280 s
> [INFO] Finished at: 2018-12-29T12:16:43Z
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.22.1:test (default-test) on 
> project lizzie: There are test failures.
> [ERROR] 
> [ERROR] Please refer to 
> /<>/lizzie-0.6+dfsg1/target/surefire-reports for the individual 
> test results.
> [ERROR] Please refer to dump files (if any exist) [date].dump, 
> [date]-jvmRun[N].dump and [date].dumpstream.
> [ERROR] -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch 

Bug#917717: pylint-django: FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7 returned exit code 13

2018-12-29 Thread Lucas Nussbaum
Source: pylint-django
Version: 2.0.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="PYTHONDONTWRITEBYTECODE=1 
> PYTHONPATH=. {interpreter} pylint_django/tests/test_func.py" dh_auto_test
> I: pybuild base:217: PYTHONDONTWRITEBYTECODE=1 PYTHONPATH=. python3.7 
> pylint_django/tests/test_func.py
> = test session starts 
> ==
> platform linux -- Python 3.7.2rc1, pytest-3.10.1, py-1.7.0, pluggy-0.8.0
> rootdir: /<>, inifile:
> collected 0 items / 1 errors
> 
>  ERRORS 
> 
> __ ERROR collecting pylint_django/tests/test_func.py 
> ___
> ImportError while importing test module 
> '/<>/pylint_django/tests/test_func.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> pylint_django/__init__.py:6: in 
> from pylint_django import plugin
> pylint_django/plugin.py:5: in 
> from pylint_django.checkers import register_checkers
> pylint_django/checkers/__init__.py:3: in 
> from pylint_django.checkers.models import ModelChecker
> pylint_django/checkers/models.py:11: in 
> from pylint_django.utils import node_is_subclass, PY3
> pylint_django/utils.py:4: in 
> from astroid.util import YES
> E   ImportError: cannot import name 'YES' from 'astroid.util' 
> (/usr/lib/python3/dist-packages/astroid/util.py)
> !!! Interrupted: 1 errors during collection 
> 
> === 1 error in 0.07 seconds 
> 
> E: pybuild pybuild:338: test: plugin custom failed with: exit code=2: 
> PYTHONDONTWRITEBYTECODE=1 PYTHONPATH=. python3.7 
> pylint_django/tests/test_func.py
> dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7 returned 
> exit code 13

The full build log is available from:
   http://aws-logs.debian.net/2018/12/29/pylint-django_2.0.1-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



Bug#917720: sunpy: FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7 returned exit code 13

2018-12-29 Thread Lucas Nussbaum
Source: sunpy
Version: 0.9.5-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:217: python3.7 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy
> copying sunpy/__init__.py -> 
> /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy
> copying sunpy/version.py -> 
> /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy
> copying sunpy/conftest.py -> 
> /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy
> creating /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/instr
> copying sunpy/instr/aia.py -> 
> /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/instr
> copying sunpy/instr/rhessi.py -> 
> /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/instr
> copying sunpy/instr/goes.py -> 
> /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/instr
> copying sunpy/instr/lyra.py -> 
> /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/instr
> copying sunpy/instr/__init__.py -> 
> /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/instr
> copying sunpy/instr/fermi.py -> 
> /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/instr
> creating /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/map
> copying sunpy/map/mapcube.py -> 
> /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/map
> copying sunpy/map/mapbase.py -> 
> /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/map
> copying sunpy/map/__init__.py -> 
> /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/map
> copying sunpy/map/map_factory.py -> 
> /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/map
> copying sunpy/map/compositemap.py -> 
> /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/map
> copying sunpy/map/mapsequence.py -> 
> /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/map
> creating /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/util
> copying sunpy/util/xml.py -> 
> /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/util
> copying sunpy/util/create.py -> 
> /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/util
> copying sunpy/util/cond_dispatch.py -> 
> /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/util
> copying sunpy/util/sysinfo.py -> 
> /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/util
> copying sunpy/util/multimethod.py -> 
> /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/util
> copying sunpy/util/__init__.py -> 
> /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/util
> copying sunpy/util/scraper.py -> 
> /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/util
> copying sunpy/util/metadata.py -> 
> /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/util
> copying sunpy/util/config.py -> 
> /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/util
> copying sunpy/util/exceptions.py -> 
> /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/util
> copying sunpy/util/net.py -> 
> /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/util
> copying sunpy/util/datatype_factory_base.py -> 
> /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/util
> copying sunpy/util/progressbar.py -> 
> /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/util
> copying sunpy/util/decorators.py -> 
> /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/util
> copying sunpy/util/util.py -> 
> /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/util
> creating /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/coordinates
> copying sunpy/coordinates/wcs_utils.py -> 
> /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/coordinates
> copying sunpy/coordinates/offset_frame.py -> 
> /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/coordinates
> copying sunpy/coordinates/frames.py -> 
> /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/coordinates
> copying sunpy/coordinates/__init__.py -> 
> /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/coordinates
> copying sunpy/coordinates/utils.py -> 
> /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/coordinates
> copying sunpy/coordinates/frameattributes.py -> 
> /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/coordinates
> copying sunpy/coordinates/ephemeris.py -> 
> /<>/.pybuild/cpython3_3.7_sunpy/build/sunpy/coordinates
> copying sunpy/coordinates/transformations.py -> 
> 

Bug#917722: pybind11: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && make -j2 check ARGS\+=-j2 returned exit code 2

2018-12-29 Thread Lucas Nussbaum
Source: pybind11
Version: 2.2.4-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
> cd /<>/tests && /usr/bin/python3.7 -m pytest test_buffers.py 
> test_builtin_casters.py test_call_policies.py test_callbacks.py 
> test_chrono.py test_class.py test_constants_and_functions.py 
> test_copy_move.py test_docstring_options.py test_eigen.py test_enum.py 
> test_eval.py test_exceptions.py test_factory_constructors.py test_iostream.py 
> test_kwargs_and_defaults.py test_local_bindings.py 
> test_methods_and_attributes.py test_modules.py test_multiple_inheritance.py 
> test_numpy_array.py test_numpy_dtypes.py test_numpy_vectorize.py 
> test_opaque_types.py test_operator_overloading.py test_pickling.py 
> test_pytypes.py test_sequences_and_iterators.py test_smart_ptr.py test_stl.py 
> test_stl_binders.py test_virtual_functions.py
> [100%] Built target test_cmake_build
> = test session starts 
> ==
> platform linux -- Python 3.7.2rc1, pytest-3.10.1, py-1.7.0, pluggy-0.8.0
> rootdir: /<>/tests, inifile: pytest.ini
> collected 298 items
> 
> test_buffers.py  [  
> 1%]
> test_builtin_casters.py s.   [  
> 6%]
> test_call_policies.py .  [  
> 9%]
> test_callbacks.py ...[ 
> 11%]
> test_chrono.py ...   [ 
> 13%]
> test_class.py ...[ 
> 18%]
> test_constants_and_functions.py  [ 
> 20%]
> test_copy_move.py s..[ 
> 22%]
> test_docstring_options.py .  [ 
> 22%]
> test_eigen.py F  [ 
> 31%]
> test_enum.py .   [ 
> 32%]
> test_eval.py .   [ 
> 33%]
> test_exceptions.py ...   [ 
> 35%]
> test_factory_constructors.py .   [ 
> 38%]
> test_iostream.py [ 
> 42%]
> test_kwargs_and_defaults.py .[ 
> 44%]
> test_local_bindings.py ..[ 
> 47%]
> test_methods_and_attributes.py   [ 
> 54%]
> test_modules.py .[ 
> 56%]
> test_multiple_inheritance.py ... [ 
> 59%]
> test_numpy_array.py .[ 
> 70%]
> test_numpy_dtypes.py [ 
> 74%]
> test_numpy_vectorize.py ...  [ 
> 77%]
> test_opaque_types.py ..  [ 
> 77%]
> test_operator_overloading.py ... [ 
> 78%]
> test_pickling.py [ 
> 80%]
> test_pytypes.py ...  [ 
> 83%]
> test_sequences_and_iterators.py ..   [ 
> 85%]
> test_smart_ptr.py ...[ 
> 89%]
> test_stl.py ...ss.   [ 
> 94%]
> test_stl_binders.py .[ 
> 97%]
> test_virtual_functions.py    
> [100%]
> 
> === FAILURES 
> ===
> _ test_sparse 
> __
> 
> @pytest.requires_eigen_and_scipy
> def test_sparse():
> >   assert_sparse_equal_ref(m.sparse_r())
> 
> test_eigen.py:646: 
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> /usr/lib/python3/dist-packages/scipy/sparse/__init__.py:231: in 
> from .lil import *
> /usr/lib/python3/dist-packages/scipy/sparse/lil.py:19: in 
> from . import _csparsetools
>

Bug#917715: openconnect: FTBFS: dh_auto_test: make -j2 check VERBOSE=1 returned exit code 2

2018-12-29 Thread Lucas Nussbaum
Source: openconnect
Version: 7.08-3
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[4]: Entering directory '/<>/tests'
> FAIL: auth-username-pass
> FAIL: auth-certificate
> FAIL: id-test
> FAIL: auth-pkcs11
> PASS: seqtest
> PASS: lzstest
> 
>openconnect 7.08: tests/test-suite.log
> 
> 
> # TOTAL: 6
> # PASS:  2
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  4
> # XPASS: 0
> # ERROR: 0
> 
> .. contents:: :depth: 2
> 
> FAIL: auth-username-pass
> 
> 
> Testing certificate auth... 
> warning: skipping unknown option 'cookie-validity'
> Parsing plain auth method subconfig using legacy format
> note: setting 'plain' as primary authentication method
> note: setting 'file' as supplemental config option
> listening (TCP) on 0.0.0.0:443...
> listening (TCP) on [::]:443...
> listening (UDP) on 0.0.0.0:443...
> listening (UDP) on [::]:443...
> ocserv[13182]: main: not using control unix socket
> ocserv[13182]: main: initialized ocserv 0.12.1
> ocserv[13186]: sec-mod: reading supplemental config from files
> ocserv[13186]: sec-mod: sec-mod initialized (socket: ./ocserv-socket.51a94d1b)
> Connecting to obtain cookie... ocserv[13221]: GnuTLS error (at 
> worker-vpn.c:795): No supported cipher suites have been found.
> Failure: Could not receive cookie from server
> ocserv[13182]: main: termination request received; waiting for children to die
> ocserv[13182]: main:127.0.0.2:23190 user disconnected (reason: unspecified, 
> rx: 0, tx: 0)
> FAIL auth-username-pass (exit status: 1)
> 
> FAIL: auth-certificate
> ==
> 
> Testing certificate auth... 
> warning: skipping unknown option 'cookie-validity'
> Parsing plain auth method subconfig using legacy format
> note: setting 'certificate+plain' as primary authentication method
> note: setting 'file' as supplemental config option
> listening (TCP) on 0.0.0.0:443...
> listening (TCP) on [::]:443...
> listening (UDP) on 0.0.0.0:443...
> listening (UDP) on [::]:443...
> ocserv[13184]: main: not using control unix socket
> ocserv[13184]: main: initialized ocserv 0.12.1
> ocserv[13187]: sec-mod: reading supplemental config from files
> ocserv[13187]: sec-mod: sec-mod initialized (socket: ./ocserv-socket.6c6705ae)
> Connecting to obtain cookie (with key user-key-pkcs1.pem)... ocserv[13220]: 
> GnuTLS error (at worker-vpn.c:795): No supported cipher suites have been 
> found.
> ocserv[13184]: main:127.0.0.2:23193 user disconnected (reason: unspecified, 
> rx: 0, tx: 0)
> SSL connection failure: The TLS connection was non-properly terminated.
> Failed to open HTTPS connection to 127.0.0.2
> Failed to obtain WebVPN cookie
> Failure: Could not connect with key user-key-pkcs1.pem!
> ocserv[13184]: main: termination request received; waiting for children to die
> FAIL auth-certificate (exit status: 1)
> 
> FAIL: id-test
> =
> 
> Testing certificate auth... 
> Connecting with legacy hash... Failure: Could not receive cookie from server
> FAIL id-test (exit status: 1)
> 
> FAIL: auth-pkcs11
> =
> 
> Testing PKCS#11 auth... 
> warning: skipping unknown option 'cookie-validity'
> Parsing plain auth method subconfig using legacy format
> note: setting 'certificate+plain' as primary authentication method
> note: setting 'file' as supplemental config option
> listening (TCP) on 0.0.0.0:443...
> listening (TCP) on [::]:443...
> listening (UDP) on 0.0.0.0:443...
> listening (UDP) on [::]:443...
> ocserv[13242]: main: not using control unix socket
> ocserv[13242]: main: initialized ocserv 0.12.1
> ocserv[13245]: sec-mod: reading supplemental config from files
> ocserv[13245]: sec-mod: sec-mod initialized (socket: ./ocserv-socket.ea41c786)
> Connecting to obtain cookie (token openconnect-test key object=RSA)... 
> ocserv[13281]: GnuTLS error (at worker-vpn.c:795): No supported cipher suites 
> have been found.
> SSL connection failure: The TLS connection was non-properly terminated.
> ocserv[13242]: main:127.0.0.2:23259 user disconnected (reason: unspecified, 
> rx: 0, tx: 0)
> Failed to open HTTPS connection to 127.0.0.2
> Failed to obtain WebVPN cookie
> Failure: Could not connect with token openconnect-test key object=RSA!
> ocserv[13242]: main: termination request received; waiting for children to die
> FAIL 

Bug#917719: libbio-tools-run-alignment-tcoffee-perl: FTBFS: dh_auto_test: make -j2 test TEST_VERBOSE=1 returned exit code 2

2018-12-29 Thread Lucas Nussbaum
Source: libbio-tools-run-alignment-tcoffee-perl
Version: 1.7.4-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" 
> "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 
> 'blib/arch')" t/*.t
> t/00-compile.t ... 
> 1..1
> ok 1 - Bio/Tools/Run/Alignment/TCoffee.pm loaded ok
> ok
> t/author-eol.t ... skipped: these tests are for testing by the author
> t/author-mojibake.t .. skipped: these tests are for testing by the author
> t/author-no-tabs.t ... skipped: these tests are for testing by the author
> t/author-pod-coverage.t .. skipped: these tests are for testing by the author
> t/author-pod-syntax.t  skipped: these tests are for testing by the author
> 
> 
> *
> *FULL TRACE BACK PID: 16494   
>  
> 16518 -- ERROR: COREDUMP: T-COFFEE Version_12.00.7fb08c2 (2018-12-11 09:27:12 
> - Revision 7fb08c2 - Build 211)
> *
> 
>   **
>   * Abnormal Termination
>   * Job NOT Completed:[T-COFFEE, Version_12.00.7fb08c2]
>   * Please CHECK:   
>   *   -1 The format of your Input Files 
>   *   -2 The parameters 
>   *   -3 The use of special characters in sequence names:
>   *(@, |, %...)
>   *   -4 The Online Doc (http://www.tcoffee.org)   
>   *   -5 re-run your CL (see below) with the -debug option. This will 
> produce a debug file you can send us.
>   *
>   *   NO 
>   * to:
>   *   cedric.notred...@gmail.com
>   * If you run T-Coffee over the WEB:
>   *   Windows Cut and Paste is sometimes erratic and
>   *   it can loose carriage returns. If you suspect this,
>   *   try to cut and paste through an intermediate application
>   *   (word pad) and inspect the results
> 
> 
>   * CONFIDENTIALITY:
>   *   The File NO may contain your personal DATA
>   *   Remove ALL confidential DATA from this file BEFORE sending it
>   **
> # Command Line: /usr/bin/t_coffee -profile C3uHd27Vnl -seq rKVo1aRtb4 -matrix 
> blosum -method lalign_id_pair clustalw_pair -ktuple 3 -outfile 
> /tmp/D_LRrJQoYx/TbKy3eG8L7 -output clustalw -quiet  [PROGRAM:T-COFFEE]
> 
> # TERMINATION STATUS: FAILURE [PROGRAM: T-COFFEE pid 16494 ppid 16412
> #CL: /usr/bin/t_coffee -profile C3uHd27Vnl -seq rKVo1aRtb4 -matrix blosum 
> -method lalign_id_pair clustalw_pair -ktuple 3 -outfile 
> /tmp/D_LRrJQoYx/TbKy3eG8L7 -output clustalw -quiet 
> ERROR: /var/tmp/tco/tcouusjjsfj16494/9295616514392 FILE is NOT a supported 
> format [ERROR]
> #   Failed test at t/TCoffee.t line 74.
> # died: 
> # - EXCEPTION -
> # MSG: TCoffee call crashed: 256 [command /usr/bin/t_coffee  
> -profile=C3uHd27Vnl -seq=rKVo1aRtb4 -matrix=blosum 
> -method=lalign_id_pair,clustalw_pair  -ktuple=3 
> -outfile=/tmp/D_LRrJQoYx/TbKy3eG8L7 -output=clustalw -quiet]
> # 
> # STACK Bio::Root::RootI::warn /usr/share/perl5/Bio/Root/RootI.pm:150
> # STACK Bio::Tools::Run::Alignment::TCoffee::_run 
> /<>/blib/lib/Bio/Tools/Run/Alignment/TCoffee.pm:272
> # STACK Bio::Tools::Run::Alignment::TCoffee::profile_align 
> /<>/blib/lib/Bio/Tools/Run/Alignment/TCoffee.pm:198
> # STACK Test::Exception::lives_ok t/TCoffee.t:74
> # STACK toplevel t/TCoffee.t:74
> # -
> #   Failed test 'no T-COFFEE errors'
> #   at t/TCoffee.t line 76.
> sh: 1: cannot create /var/tmp/tco/tcouusjjsfj16494/9295616494252: Directory 
> nonexistent
> 
> --COULD NOT READ 
> /<>/debian/build//.t_coffee//cache//var/tmp/tco/tcouusjjsfj16494//9295616494252
> 
> --ERROR: FORCED EXIT (NON INTERACTIVE MODE pid 16516)
> 
> COULD NOT Append anything to /var/tmp/tco/tcouusjjsfj16494//9295616513411
> 
> --COULD NOT READ 
> /<>/debian/build//.t_coffee//cache//var/tmp/tco/tcouusjjsfj16494//9295616513411
> 
> --ERROR: FORCED EXIT (NON INTERACTIVE MOD

Bug#917721: libbiod: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=2 ninja test returned exit code 1

2018-12-29 Thread Lucas Nussbaum
Source: libbiod
Version: 0.2.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dpkg-query: no packages found matching gdc
> dh build
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
> --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
> --localstatedir=/var --libdir=lib/x86_64-linux-gnu 
> --libexecdir=lib/x86_64-linux-gnu
> The Meson build system
> Version: 0.49.0
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: BioD
> Project version: 0.2.2
> Appending DFLAGS from environment: '-O -g -release -wi'
> Appending LDFLAGS from environment: '-Wl,-z,relro -Wl,-z,now'
> Native D compiler: ldc2 (llvm 1.12.0 "LDC - the LLVM D compiler (1.12.0):")
> Build machine cpu family: x86_64
> Build machine cpu: x86_64
> Found pkg-config: /usr/bin/pkg-config (0.29)
> Dependency undead found: YES 1.0.7
> Dependency zlib found: YES 1.2.11
> Build targets in project: 2
> Found ninja-1.8.2 at /usr/bin/ninja
>dh_auto_build
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j2 -v
> [1/177] ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g 
> -release -wi -relocation-model=pic   -of='biod@sha/bio_bam_bai_bin.d.o' -c 
> ../bio/bam/bai/bin.d
> [2/177] ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g 
> -release -wi -relocation-model=pic   
> -of='biod@sha/bio_bam_abstractreader.d.o' -c ../bio/bam/abstractreader.d
> [3/177] ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g 
> -release -wi -relocation-model=pic   -of='biod@sha/bio_bam_baifile.d.o' -c 
> ../bio/bam/baifile.d
> [4/177] ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g 
> -release -wi -relocation-model=pic   -of='biod@sha/bio_bam_baseinfo.d.o' -c 
> ../bio/bam/baseinfo.d
> [5/177] ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g 
> -release -wi -relocation-model=pic   -of='biod@sha/bio_bam_cigar.d.o' -c 
> ../bio/bam/cigar.d
> [6/177] ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g 
> -release -wi -relocation-model=pic   -of='biod@sha/bio_bam_constants.d.o' -c 
> ../bio/bam/constants.d
> [7/177] ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g 
> -release -wi -relocation-model=pic   -of='biod@sha/bio_bam_bai_indexing.d.o' 
> -c ../bio/bam/bai/indexing.d
> [8/177] ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g 
> -release -wi -relocation-model=pic   
> -of='biod@sha/bio_bam_iontorrent_flowindex.d.o' -c 
> ../bio/bam/iontorrent/flowindex.d
> [9/177] ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g 
> -release -wi -relocation-model=pic   -of='biod@sha/bio_bam_md_core.d.o' -c 
> ../bio/bam/md/core.d
> [10/177] ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g 
> -release -wi -relocation-model=pic   
> -of='biod@sha/bio_bam_iontorrent_flowcall.d.o' -c 
> ../bio/bam/iontorrent/flowcall.d
> [11/177] ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g 
> -release -wi -relocation-model=pic   -of='biod@sha/bio_bam_md_operation.d.o' 
> -c ../bio/bam/md/operation.d
> [12/177] ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g 
> -release -wi -relocation-model=pic   
> -of='biod@sha/bio_bam_md_reconstruct.d.o' -c ../bio/bam/md/reconstruct.d
> [13/177] ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g 
> -release -wi -relocation-model=pic   -of='biod@sha/bio_bam_md_parse.d.o' -c 
> ../bio/bam/md/parse.d
> [14/177] ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g 
> -release -wi -relocation-model=pic   -of='biod@sha/bio_bam_pileup.d.o' -c 
> ../bio/bam/pileup.d
> [15/177] ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g 
> -release -wi -relocation-model=pic   
> -of='biod@sha/bio_bam_randomaccessmanager.d.o' -c 
> ../bio/bam/randomaccessmanager.d
> [16/177] ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g 
> -release -wi -relocation-model=pic   -of='biod@sha/bio_bam_multireader.d.o' 
> -c ../bio/bam/multireader.d
> [17/177] ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g 
> -release -wi -relocation-model=pic   -of='biod@sha/bio_bam_read.d.o' -c 
> ../bio/bam/read.d
> [18/177] ldc2 -I=biod@sha -I=. 

Bug#917718: libuv1: FTBFS: dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2

2018-12-29 Thread Lucas Nussbaum
Source: libuv1
Version: 1.24.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/<>'
> 1..343
> ok 1 - platform_output
> # Output from process `platform_output`:
> # uv_get_process_title: /<>/test/.libs/run-tests
> # uv_cwd: /<>
> # uv_resident_set_memory: 1069056
> # uv_uptime: 7932.00
> # uv_getrusage:
> #   user: 0 sec 0 microsec
> #   system: 0 sec 0 microsec
> #   page faults: 0
> #   maximum resident set size: 1044
> # uv_cpu_info:
> #   model: Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz
> #   speed: 2500
> #   times.sys: 6262800
> #   times.user: 60641700
> #   times.idle: 10290400
> #   times.irq: 0
> #   times.nice: 0
> #   model: Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz
> #   speed: 2500
> #   times.sys: 6210200
> #   times.user: 59260500
> #   times.idle: 11656300
> #   times.irq: 0
> #   times.nice: 0
> # uv_interface_addresses:
> #   name: lo
> #   internal: 1
> #   physical address: 00:00:00:00:00:00
> #   address: 127.0.0.1
> #   netmask: 255.0.0.0
> #   name: eth0
> #   internal: 0
> #   physical address: 06:c0:2d:38:cd:2c
> #   address: 172.31.2.71
> #   netmask: 255.255.240.0
> #   name: lo
> #   internal: 1
> #   physical address: 00:00:00:00:00:00
> #   address: ::1
> #   netmask: :::::::
> #   name: eth0
> #   internal: 0
> #   physical address: 06:c0:2d:38:cd:2c
> #   address: fe80::4c0:2dff:fe38:cd2c
> #   netmask: :::::
> # uv_os_get_passwd:
> #   euid: 1001
> #   gid: 1001
> #   username: user42
> #   shell: 
> #   home directory: /home/user42
> # uv_os_getpid: 14358
> # uv_os_getppid: 14344
> ok 2 - active
> ok 3 - async
> ok 4 - async_null_cb
> ok 5 - async_ref
> ok 6 - barrier_1
> ok 7 - barrier_2
> ok 8 - barrier_3
> ok 9 - barrier_serial_thread
> ok 10 - barrier_serial_thread_single
> ok 11 - callback_stack
> ok 12 - check_ref
> ok 13 - close_fd
> ok 14 - close_order
> ok 15 - closed_fd_events
> ok 16 - condvar_1
> ok 17 - condvar_2
> ok 18 - condvar_3
> ok 19 - condvar_4
> ok 20 - condvar_5
> ok 21 - connect_unspecified
> ok 22 - connection_fail
> ok 23 - connection_fail_doesnt_auto_close
> ok 24 - cwd_and_chdir
> ok 25 - default_loop_close
> ok 26 - delayed_accept
> ok 27 - dlerror
> ok 28 - eintr_handling
> ok 29 - embed
> ok 30 - emfile
> ok 31 - env_vars
> ok 32 - error_message
> ok 33 - fork_fs_events_child
> ok 34 - fork_fs_events_child_dir
> ok 35 - fork_fs_events_file_parent_child
> ok 36 - fork_signal_to_child
> ok 37 - fork_signal_to_child_closed
> ok 38 - fork_socketpair
> ok 39 - fork_socketpair_started
> ok 40 - fork_threadpool_queue_work_simple
> ok 41 - fork_timer
> ok 42 - fs_access
> ok 43 - fs_async_dir
> ok 44 - fs_async_sendfile
> ok 45 - fs_chmod
> ok 46 - fs_chown
> ok 47 - fs_copyfile
> ok 48 - fs_event_close_in_callback
> ok 49 - fs_event_close_with_pending_event
> ok 50 - fs_event_error_reporting
> ok 51 - fs_event_getpath
> ok 52 - fs_event_immediate_close
> ok 53 - fs_event_no_callback_after_close
> ok 54 - fs_event_no_callback_on_close
> ok 55 - fs_event_ref
> ok 56 - fs_event_start_and_close
> ok 57 - fs_event_watch_dir
> ok 58 - fs_event_watch_dir_recursive # SKIP Recursive directory watching not 
> supported on this platform.
> ok 59 - fs_event_watch_file
> ok 60 - fs_event_watch_file_current_dir
> ok 61 - fs_event_watch_file_exact_path
> ok 62 - fs_event_watch_file_twice
> ok 63 - fs_event_watch_invalid_path
> ok 64 - fs_file_async
> ok 65 - fs_file_loop
> ok 66 - fs_file_nametoolong
> ok 67 - fs_file_noent
> ok 68 - fs_file_open_append
> ok 69 - fs_file_pos_after_op_with_offset
> ok 70 - fs_file_sync
> ok 71 - fs_file_write_null_buffer
> ok 72 - fs_fstat
> ok 73 - fs_futime
> ok 74 - fs_mkdtemp
> ok 75 - fs_null_req
> ok 76 - fs_open_dir
> ok 77 - fs_partial_read
> ok 78 - fs_partial_write
> ok 79 - fs_poll
> ok 80 - fs_poll_getpath
> ok 81 - fs_poll_ref
> ok 82 - fs_read_dir
> ok 83 - fs_read_file_eof
> ok 84 - fs_read_write_null_arguments
> ok 85 - fs_readlink
> ok 86 - fs_realpath
> ok 87 - fs_rename_to_existing_file
> ok 88 - fs_scandir_empty_dir
> ok 89 - fs_scandir_file
> ok 90 - fs_scandir_non_existent_dir
> ok 91 - fs_stat_missing_path
> ok 92 - fs_symlink
> ok 93 - fs_symlink_dir
> ok 94 - fs_unlink_readonly
> ok 95 - fs_utime
> ok 96 - fs_write_alotof_bufs
> ok 97 - fs_write_alotof_bufs

Bug#917713: pyscanfcs: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 3.7 returned exit code 13

2018-12-29 Thread Lucas Nussbaum
Source: pyscanfcs
Version: 0.3.2+ds-2
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>/pyscanfcs-0.3.2+ds'
> cd doc && \
> (   faketime -f "2018-12-20 12:17:24+00:00" pdflatex -synctex=1 
> -interaction=nonstopmode PyScanFCS_doc.tex \
>   bibtex PyScanFCS_doc.aux \
>   faketime -f "2018-12-20 12:17:24+00:00" pdflatex -synctex=1 
> -interaction=nonstopmode PyScanFCS_doc.tex \
>   faketime -f "2018-12-20 12:17:24+00:00" pdflatex -synctex=1 
> -interaction=nonstopmode PyScanFCS_doc.tex \
> )
> This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) 
> (preloaded format=pdflatex)
>  restricted \write18 enabled.
> entering extended mode
> (./PyScanFCS_doc.tex
> LaTeX2e <2018-12-01>
> (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrartcl.cls
> Document Class: scrartcl 2018/03/30 v3.25 KOMA-Script document class (article)
> (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrkbase.sty
> (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrbase.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrlfile.sty)))
> (/usr/share/texlive/texmf-dist/tex/latex/koma-script/tocbasic.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/koma-script/scrsize12pt.clo)
> (/usr/share/texlive/texmf-dist/tex/latex/koma-script/typearea.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty
> (/usr/share/texlive/texmf-dist/tex/latex/ucs/utf8x.def))
> (/usr/share/texlive/texmf-dist/tex/latex/ucs/ucs.sty
> (/usr/share/texlive/texmf-dist/tex/latex/ucs/data/uni-global.def))
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty
> (/usr/share/texlive/texmf-dist/tex/generic/babel/switch.def)
> (/usr/share/texlive/texmf-dist/tex/generic/babel-english/english.ldf
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.def
> (/usr/share/texlive/texmf-dist/tex/generic/babel/txtbabel.def
> (/usr/share/texlive/texmf-dist/tex/latex/SIstyle/sistyle.sty
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amstext.sty
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsgen.sty)))
> (/usr/share/texlive/texmf-dist/tex/latex/geometry/geometry.sty
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifpdf.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifvtex.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsmath.sty
> For additional information on amsmath, use the `?' option.
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsbsy.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsopn.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amssymb.sty
> (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amsfonts.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/tools/array.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/cite/cite.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/url/url.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/subfig/subfig.sty
> (/usr/share/texlive/texmf-dist/tex/latex/caption/caption.sty
> (/usr/share/texlive/texmf-dist/tex/latex/caption/caption3.sty)))
> (/usr/share/texlive/texmf-dist/tex/latex/tools/tabularx.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/base/textcomp.sty
> (/usr/share/texlive/texmf-dist/tex/latex/base/ts1enc.def))
> (/usr/share/texlive/texmf-dist/tex/latex/wrapfig/wrapfig.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/xcolor/xcolor.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/color.cfg)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics-def/pdftex.def)
> (/usr/share/texlive/texmf-dist/tex/latex/xcolor/svgnam.def))
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/graphics.cfg)))
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/hyperref.sty
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-hyperref.sty
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-generic.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/auxhook.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/kvoptions.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/pd1enc.def)
> (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/hyperref.cfg)
> 
> Package hyperref Warning: Unexpected value for option `pdftex'
> (hyperref)is ignored on input line 4393.
>

Bug#879538: mandos: (tries to) use GnuTLS OpenPGP support

2018-12-29 Thread Steinar H. Gunderson
severity 879538 grave
thanks

On Thu, Oct 26, 2017 at 09:56:18PM +0200, Teddy Hogeborn wrote:
>> plugins.d/mandos-client.c actually uses GnuTLS OpenPGP support. This
>> code was marked deprecated in 3.5.9 and was removed in 3.6.0. Noop stub
>> functions are still shipped to avoid ABI breakage but return 
>> GNUTLS_E_UNIMPLEMENTED_FEATURE.
> We can't do that, it's an integral part of the Mandos client/server
> network protocol; removing it would entail creating an entirely new
> incompatible protocol.  We plan to do that using a feature not yet
> available in GnuTLS called "raw public keys" (RFC7250), but its
> developer has not merged it to GnuTLS upstream yet.

If so, mandos in unstable has to be completely broken, as GnuTLS 3.6.5
is now the current version. Marking the bug accordingly.

/* Steinar */
-- 
Homepage: https://www.sesse.net/



Bug#917711: grantlee5: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && make -j2 test ARGS\+=-j2 returned exit code 2

2018-12-29 Thread Lucas Nussbaum
Source: grantlee5
Version: 5.1.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
> Running tests...
> /usr/bin/ctest --force-new-ctest-process -j2
> Test project /<>/obj-x86_64-linux-gnu
>   Start  1: testsafestring
>   Start  2: testbuiltins
>  1/12 Test  #1: testsafestring ...   Passed0.00 sec
>   Start  3: testloadertags
>  2/12 Test  #3: testloadertags ...   Passed0.02 sec
>   Start  4: testdefaulttags
>  3/12 Test  #2: testbuiltins .   Passed0.04 sec
>   Start  5: testcachingloader
>  4/12 Test  #5: testcachingloader    Passed0.01 sec
>   Start  6: testfilters
>  5/12 Test  #6: testfilters ..***Failed0.03 sec
> * Start testing of TestFilters *
> Config: Using QtTest library 5.11.3, Qt 5.11.3 (x86_64-little_endian-lp64 
> shared (dynamic) release build; by GCC 8.2.0)
> PASS   : TestFilters::initTestCase()
> PASS   : TestFilters::testDateBasedFilters(filter-timesince01)
> PASS   : TestFilters::testDateBasedFilters(filter-timesince02)
> PASS   : TestFilters::testDateBasedFilters(filter-timesince03)
> PASS   : TestFilters::testDateBasedFilters(filter-timesince04)
> PASS   : TestFilters::testDateBasedFilters(filter-timesince05)
> PASS   : TestFilters::testDateBasedFilters(filter-timesince07)
> PASS   : TestFilters::testDateBasedFilters(filter-timesince08)
> PASS   : TestFilters::testDateBasedFilters(filter-timesince09)
> PASS   : TestFilters::testDateBasedFilters(filter-timesince10)
> PASS   : TestFilters::testDateBasedFilters(filter-timesince17)
> PASS   : TestFilters::testDateBasedFilters(filter-timesince18)
> PASS   : TestFilters::testDateBasedFilters(filter-timeuntil01)
> PASS   : TestFilters::testDateBasedFilters(filter-timeuntil02)
> PASS   : TestFilters::testDateBasedFilters(filter-timeuntil03)
> PASS   : TestFilters::testDateBasedFilters(filter-timeuntil04)
> PASS   : TestFilters::testDateBasedFilters(filter-timeuntil05)
> PASS   : TestFilters::testDateBasedFilters(filter-timeuntil06)
> PASS   : TestFilters::testDateBasedFilters(filter-timeuntil07)
> PASS   : TestFilters::testDateBasedFilters(filter-timeuntil08)
> PASS   : TestFilters::testDateBasedFilters(filter-timeuntil09)
> PASS   : TestFilters::testDateBasedFilters(filter-timeuntil12)
> PASS   : TestFilters::testDateBasedFilters(filter-timeuntil13)
> FAIL!  : TestFilters::testDateBasedFilters(date01) Compared values are not 
> the same
>Actual   (result): ""
>Expected (output): "01"
>Loc: [/<>/templates/tests/testfilters.cpp(117)]
> FAIL!  : TestFilters::testDateBasedFilters(date02) Compared values are not 
> the same
>Actual   (result): ""
>Expected (output): "Jan. 1, 2008"
>Loc: [/<>/templates/tests/testfilters.cpp(117)]
> PASS   : TestFilters::testDateBasedFilters(date03)
> PASS   : TestFilters::testStringFilters(filter-addslash01)
> PASS   : TestFilters::testStringFilters(filter-addslash02)
> PASS   : TestFilters::testStringFilters(filter-capfirst01)
> PASS   : TestFilters::testStringFilters(filter-capfirst02)
> PASS   : TestFilters::testStringFilters(filter-fix_ampersands01)
> PASS   : TestFilters::testStringFilters(filter-fix_ampersands02)
> PASS   : TestFilters::testStringFilters(filter-floatformat01)
> PASS   : TestFilters::testStringFilters(filter-floatformat02)
> PASS   : TestFilters::testStringFilters(filter-linenumbers01)
> PASS   : TestFilters::testStringFilters(filter-linenumbers02)
> PASS   : TestFilters::testStringFilters(filter-lower01)
> PASS   : TestFilters::testStringFilters(filter-lower02)
> PASS   : TestFilters::testStringFilters(filter-make_list01)
> PASS   : TestFilters::testStringFilters(filter-make_list02)
> PASS   : TestFilters::testStringFilters(filter-make_list03)
> PASS   : TestFilters::testStringFilters(filter-make_list04)
> PASS   : TestFilters::testStringFilters(filter-slugify01)
> PASS   : TestFilters::testStringFilters(filter-slugify02)
> PASS   : TestFilters::testStringFilters(filter-slugify03)
> PASS   : TestFilters::testStringFilters(escapejs01)
> PASS   : TestFilters::testStringFilters(escapejs02)
> PASS   : TestFilters::testStringFilters(filter-stringformat01)
> PASS   : TestFilters::testStringFilters(filter-stringformat02)
> PASS   : TestFilters::testStringFilters(filter-stringformat03)
> PASS   : TestFilters::testStringFilters(filter-stringformat04)
> PASS   : TestFilters::testStringFilters(filter-title

Bug#917710: bolt: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=2 ninja test returned exit code 1

2018-12-29 Thread Lucas Nussbaum
Source: bolt
Version: 0.5-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_configure -- \
>   --libexecdir=/usr/lib/bolt \
>   -Dman=true \
>   -Dprivileged-group=sudo
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
> --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
> --localstatedir=/var --libdir=lib/x86_64-linux-gnu 
> --libexecdir=lib/x86_64-linux-gnu --libexecdir=/usr/lib/bolt -Dman=true 
> -Dprivileged-group=sudo
> The Meson build system
> Version: 0.49.0
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: bolt
> Project version: 0.5
> Appending CFLAGS from environment: '-g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security'
> Appending LDFLAGS from environment: '-Wl,-z,relro -Wl,-z,now -Wl,-z,defs 
> -Wl,--as-needed'
> Appending CPPFLAGS from environment: '-Wdate-time -D_FORTIFY_SOURCE=2'
> Native C compiler: cc (gcc 8.2.0 "cc (Debian 8.2.0-13) 8.2.0")
> Build machine cpu family: x86_64
> Build machine cpu: x86_64
> Compiler for C supports arguments -fstack-protector-strong: YES
> Compiler for C supports arguments -Waggregate-return: YES
> Compiler for C supports arguments -Wunused: YES
> Compiler for C supports arguments -Warray-bounds: YES
> Compiler for C supports arguments -Wcast-align: YES
> Compiler for C supports arguments -Wclobbered: YES
> Compiler for C supports arguments -Wdeclaration-after-statement: YES
> Compiler for C supports arguments -Wempty-body: YES
> Compiler for C supports arguments -Wformat=2: YES
> Compiler for C supports arguments -Wformat-nonliteral: YES
> Compiler for C supports arguments -Wformat-security: YES
> Compiler for C supports arguments -Wformat-signedness: YES
> Compiler for C supports arguments -Wignored-qualifiers: YES
> Compiler for C supports arguments -Wimplicit-function-declaration: YES
> Compiler for C supports arguments -Winit-self: YES
> Compiler for C supports arguments -Wmissing-declarations: YES
> Compiler for C supports arguments -Wmissing-format-attribute: YES
> Compiler for C supports arguments -Wmissing-include-dirs: YES
> Compiler for C supports arguments -Wmissing-noreturn: YES
> Compiler for C supports arguments -Wmissing-parameter-type: YES
> Compiler for C supports arguments -Wmissing-prototypes: YES
> Compiler for C supports arguments -Wnested-externs: YES
> Compiler for C supports arguments -Wno-discarded-qualifiers 
> -Wdiscarded-qualifiers: YES
> Compiler for C supports arguments -Wno-missing-field-initializers 
> -Wmissing-field-initializers: YES
> Compiler for C supports arguments -Wno-strict-aliasing -Wstrict-aliasing: YES
> Compiler for C supports arguments -Wno-suggest-attribute=format 
> -Wsuggest-attribute=format: YES
> Compiler for C supports arguments -Wno-unused-parameter -Wunused-parameter: 
> YES
> Compiler for C supports arguments -Wold-style-definition: YES
> Compiler for C supports arguments -Woverride-init: YES
> Compiler for C supports arguments -Wpointer-arith: YES
> Compiler for C supports arguments -Wredundant-decls: YES
> Compiler for C supports arguments -Wreturn-type: YES
> Compiler for C supports arguments -Wshadow: YES
> Compiler for C supports arguments -Wsign-compare: YES
> Compiler for C supports arguments -Wstrict-aliasing: YES
> Compiler for C supports arguments -Wstrict-prototypes: YES
> Compiler for C supports arguments -Wtype-limits: YES
> Compiler for C supports arguments -Wundef: YES
> Compiler for C supports arguments -Wuninitialized: YES
> Compiler for C supports arguments -Wunused-but-set-variable: YES
> Compiler for C supports arguments -Wwrite-strings: YES
> Found pkg-config: /usr/bin/pkg-config (0.29)
> Dependency glib-2.0 found: YES 2.58.1
> Dependency gio-2.0 found: YES 2.58.1
> Dependency libudev found: YES 240
> Dependency gio-unix-2.0 found: YES 2.58.1
> Dependency udev found: YES 240
> Dependency polkit-gobject-1 found: YES 0.105
> Dependency umockdev-1.0 found: YES 0.12.1
> Program git found: NO
> Program a2x found: YES (/usr/bin/a2x)
> Dependency systemd found: YES 240
> Checking for function "explicit_bzero" : YES
> Checking for function "getrandom" : YES
> Configuring config.h using configuration
> Configuring org.freedesktop.bolt.service using configuration
> Configuring org.freedesktop.bolt.rules using configuration
> Configuring org.freedesktop.bolt.policy using configuration

Bug#917707: golang-github-gin-gonic-gin: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 2 github.com/gin-gonic/gin github.com/gin-gonic/gin/binding github.com/gin-gonic/gin/gin

2018-12-29 Thread Lucas Nussbaum
Source: golang-github-gin-gonic-gin
Version: 1.3.0+dfsg1-3
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_autoreconf -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go install 
> -gcflags=all=\"-trimpath=/<>/golang-github-gin-gonic-gin-1.3.0\+dfsg1/obj-x86_64-linux-gnu/src\"
>  
> -asmflags=all=\"-trimpath=/<>/golang-github-gin-gonic-gin-1.3.0\+dfsg1/obj-x86_64-linux-gnu/src\"
>  -v -p 2 github.com/gin-gonic/gin github.com/gin-gonic/gin/binding 
> github.com/gin-gonic/gin/ginS github.com/gin-gonic/gin/json 
> github.com/gin-gonic/gin/render
> errors
> internal/race
> internal/cpu
> runtime/internal/atomic
> runtime/internal/sys
> sync/atomic
> unicode
> runtime
> unicode/utf8
> crypto/subtle
> math
> strconv
> encoding
> internal/testlog
> unicode/utf16
> math/bits
> container/list
> crypto/internal/cipherhw
> crypto/rc4
> vendor/golang_org/x/crypto/cryptobyte/asn1
> internal/nettrace
> runtime/cgo
> vendor/golang_org/x/crypto/poly1305
> vendor/golang_org/x/crypto/curve25519
> sync
> io
> reflect
> bytes
> bufio
> syscall
> time
> encoding/binary
> encoding/base64
> strings
> internal/poll
> sort
> os
> hash
> hash/crc32
> crypto/cipher
> crypto/aes
> fmt
> path/filepath
> io/ioutil
> internal/syscall/unix
> math/rand
> crypto
> encoding/xml
> encoding/json
> compress/flate
> context
> math/big
> compress/gzip
> crypto/des
> crypto/sha512
> crypto/hmac
> crypto/md5
> crypto/sha1
> crypto/sha256
> encoding/hex
> crypto/rand
> crypto/elliptic
> encoding/asn1
> crypto/rsa
> crypto/ecdsa
> crypto/dsa
> crypto/x509/pkix
> encoding/pem
> vendor/golang_org/x/crypto/cryptobyte
> internal/singleflight
> net
> net/url
> vendor/golang_org/x/crypto/chacha20poly1305/internal/chacha20
> vendor/golang_org/x/crypto/chacha20poly1305
> vendor/golang_org/x/net/http2/hpack
> vendor/golang_org/x/text/transform
> log
> vendor/golang_org/x/text/unicode/bidi
> vendor/golang_org/x/text/secure/bidirule
> vendor/golang_org/x/text/unicode/norm
> vendor/golang_org/x/net/idna
> mime
> mime/quotedprintable
> net/http/internal
> path
> github.com/gin-gonic/gin/json
> github.com/golang/protobuf/proto
> crypto/x509
> crypto/tls
> vendor/golang_org/x/net/lex/httplex
> vendor/golang_org/x/net/proxy
> net/textproto
> mime/multipart
> encoding/gob
> net/http/httptrace
> net/http
> html
> text/template/parse
> text/template
> html/template
> regexp/syntax
> regexp
> gopkg.in/go-playground/validator.v8
> github.com/gin-contrib/sse
> net/rpc
> gopkg.in/yaml.v2
> github.com/ugorji/go/codec
> github.com/mattn/go-isatty
> net/http/httputil
> github.com/gin-gonic/gin/binding
> github.com/gin-gonic/gin/render
> github.com/gin-gonic/gin
> github.com/gin-gonic/gin/ginS
>dh_auto_test -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go test -vet=off -v -p 2 
> github.com/gin-gonic/gin github.com/gin-gonic/gin/binding 
> github.com/gin-gonic/gin/ginS github.com/gin-gonic/gin/json 
> github.com/gin-gonic/gin/render
> === RUN   TestBasicAuth
> --- PASS: TestBasicAuth (0.00s)
> === RUN   TestBasicAuthFails
> --- PASS: TestBasicAuthFails (0.00s)
> === RUN   TestBasicAuthSearchCredential
> --- PASS: TestBasicAuthSearchCredential (0.00s)
> === RUN   TestBasicAuthAuthorizationHeader
> --- PASS: TestBasicAuthAuthorizationHeader (0.00s)
> === RUN   TestBasicAuthSecureCompare
> --- PASS: TestBasicAuthSecureCompare (0.00s)
> === RUN   TestBasicAuthSucceed
> --- PASS: TestBasicAuthSucceed (0.00s)
> === RUN   TestBasicAuth401
> --- PASS: TestBasicAuth401 (0.00s)
> === RUN   TestBasicAuth401WithCustomRealm
> --- PASS: TestBasicAuth401WithCustomRealm (0.00s)
> === RUN   TestContextFormFile
> --- PASS: TestContextFormFile (0.00s)
> === RUN   TestContextMultipartForm
> --- PASS: TestContextMultipartForm (0.00s)
> === RUN   TestSaveUploadedOpenFailed
> --- PASS: TestSaveUploadedOpenFailed (0.00s)
> === RUN   TestSaveUploadedCreateFailed
> --- PASS: TestSaveUploadedCreateFailed (0.00s)
> === RUN   TestContextReset
> --- PASS: TestContextReset (0.00s)
> === RUN   TestContextHandlers
> --- PASS: TestContextHandlers (0.00s)
> === RUN   TestContextSetG

Bug#917712: gitano: FTBFS: dh_auto_test: make -j1 test returned exit code 2

2018-12-29 Thread Lucas Nussbaum
Source: gitano
Version: 1.1.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> NOTE: Coverage gathering is not enabled
> /usr/bin/luac5.1 -p plugins/rsync.lua plugins/archive.lua 
> plugins/git-annex.lua plugins/testing-hooks.lua plugins/demo.lua 
> plugins/git-multimail.lua
> for PLUGIN in plugins/rsync.lua plugins/archive.lua plugins/git-annex.lua 
> plugins/testing-hooks.lua plugins/demo.lua; do \
>   env LUA_PATH="/<>/lib/?.lua;;" /usr/bin/lua5.1 $PLUGIN; \
> done
> Running full yarns in 'ssh' mode
> Parsing scenario file testing/library.yarn
> Parsing scenario file testing/01-basics.yarn
> Parsing scenario file testing/01-hooks.yarn
> Parsing scenario file testing/02-commands-as.yarn
> Parsing scenario file testing/02-commands-config.yarn
> Parsing scenario file testing/02-commands-copy.yarn
> Parsing scenario file testing/02-commands-count-objects.yarn
> Parsing scenario file testing/02-commands-create.yarn
> Parsing scenario file testing/02-commands-destroy.yarn
> Parsing scenario file testing/02-commands-fsck.yarn
> Parsing scenario file testing/02-commands-gc.yarn
> Parsing scenario file testing/02-commands-graveyard.yarn
> Parsing scenario file testing/02-commands-git-upload-archive.yarn
> Parsing scenario file testing/02-commands-group.yarn
> Parsing scenario file testing/02-commands-help.yarn
> Parsing scenario file testing/02-commands-keyring.yarn
> Parsing scenario file testing/02-commands-ls.yarn
> Parsing scenario file testing/02-commands-rename.yarn
> Parsing scenario file testing/02-commands-rsync.yarn
> Parsing scenario file testing/02-commands-sshkey.yarn
> Parsing scenario file testing/02-commands-user.yarn
> Parsing scenario file testing/02-commands-whoami.yarn
> Parsing scenario file testing/03-cgit-support.yarn
> Parsing scenario file testing/03-shallow-push.yarn
> Parsing scenario file testing/03-treedelta-rules.yarn
> Parsing scenario file testing/03-force-pushing.yarn
> Parsing scenario file testing/03-dangling-HEAD.yarn
> Parsing scenario file testing/03-config-user-whitelist.yarn
> No shell libraries defined
> Found 66 scenarios
> Running scenario Verification of basic behaviour
> DATADIR is /tmp/tmpSdYDTe/Verification_of_basic_behaviour/datadir
> HOME for tests is 
> /tmp/tmpSdYDTe/Verification_of_basic_behaviour/datadir/HOME
> Running step "GIVEN a standard instance"
> ERROR: In scenario "Verification of basic behaviour"
> step "GIVEN a standard instance" failed,
> with exit code 2:
> Standard output from shell command:
> 
> Standard error from shell command:
> + /<>/testing/gitano-test-tool createunixuser testinstance
> + /<>/testing/gitano-test-tool createsshkey testinstance 
> adminkey
> + /<>/testing/gitano-test-tool createsshkey testinstance 
> bypasskey
> + /<>/testing/gitano-test-tool setupstandard testinstance 
> adminkey bypasskey
> [gitano-setup] Welcome to the Gitano setup process
> [gitano-setup] Performing system checks
> [gitano-setup] ... Checking supple sandboxing
> [gitano-setup] System checks out
> [gitano-setup] Step 1: Determine everything
> [gitano-setup] Step 2: Gather required content
> [gitano-setup] Step 3: Write out paths and gitano-admin.git
> [gitano-setup]  Set project.description to  administration repository>
> [gitano-setup]  Set project.owner to 
> [gitano-setup] SSH authorised key file updated
> /tmp/tmpmJlbny: 8: /tmp/tmpmJlbny: Syntax error: "&" unexpected
> 
> Running step "FINALLY the instance is torn down"
> Running scenario whoami shows the gitano-admin group
> DATADIR is /tmp/tmpxu9J3I/whoami_shows_the_gitano-admin_group/datadir
> HOME for tests is 
> /tmp/tmpxu9J3I/whoami_shows_the_gitano-admin_group/datadir/HOME
> Running step "GIVEN a standard instance"
> ERROR: In scenario "whoami shows the gitano-admin group"
> step "GIVEN a standard instance" failed,
> with exit code 2:
> Standard output from shell command:
> 
> Standard error from shell command:
> + /<>/testing/gitano-test-tool createunixuser testinstance
> + /<>/testing/gitano-test-tool createsshkey testinstance 
> adminkey
> + /<>/testing/gitano-test-tool createsshkey testinstance 
> bypasskey
> + /<>/testing/gitano-test-tool setupstandard testinstance 
> adminkey bypasskey
> [gitano-setup] Welcome to the Gitano setup p

Bug#917708: gnome-settings-daemon: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=2 ninja test returned exit code 1

2018-12-29 Thread Lucas Nussbaum
Source: gnome-settings-daemon
Version: 3.30.1.2-2
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> xvfb-run dh_auto_test
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=2 ninja test
> [0/1] Running all tests.
> 1/3 gcm-self-test   FAIL 0.02 s (killed by signal 
> 6 SIGABRT)
> 2/3 test-power  OK   0.12 s 
> 3/3 test-xsettings  OK   0.12 s 
> 
> Ok:2
> Expected Fail: 0
> Fail:  1
> Unexpected Pass:   0
> Skipped:   0
> Timeout:   0
> 
> 
> The output from the failed tests:
> 
> 1/3 gcm-self-test   FAIL 0.02 s (killed by signal 
> 6 SIGABRT)
> 
> --- command ---
> GSETTINGS_SCHEMA_DIR='/<>/obj-x86_64-linux-gnu/data' 
> /<>/obj-x86_64-linux-gnu/plugins/color/gcm-self-test
> --- stdout ---
> /color/edid: 
> --- stderr ---
> **
> ERROR:../plugins/color/gcm-self-test.c:243:gcm_test_edid_func: assertion 
> failed (gcm_edid_get_vendor_name (edid) == "Goldstar Company Ltd"): ("LG 
> Electronics" == "Goldstar Company Ltd")
> ---
> 
> Full log written to 
> /<>/obj-x86_64-linux-gnu/meson-logs/testlog.txt
> FAILED: meson-test 
> /usr/bin/meson test --no-rebuild --print-errorlogs
> ninja: build stopped: subcommand failed.
> dh_auto_test: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=2 
> ninja test returned exit code 1

The full build log is available from:
   
http://aws-logs.debian.net/2018/12/29/gnome-settings-daemon_3.30.1.2-2_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



Bug#917600: puppetlabs-ring-middleware-clojure: FTBFS (failing tests)

2018-12-29 Thread Emmanuel Bourg
On 29/12/2018 18:47, Cyril Brulebois wrote:

> I've been contacted by Elana, and an MR is in progress for this package;
> if it passes review, I'll submit other MRs for the remaining packages
> (as fixes are almost identical), or I can push to the Java repositories
> directly, as you folks prefer.

Great, for the clojure packages it's good to have Elana to review them
first. For the other Java packages you can send a MR or push directly to
the repositories if you feel confident.

Emmanuel Bourg



Bug#917706: nfs-utils: New upstream release available

2018-12-29 Thread Christopher Martin
Source: nfs-utils
Version: 1:1.3.4-2.3
Severity: wishlist

Upstream has released 2.3.3 and is getting close to 2.3.4, while
Debian remains on 1.3.4, which was released in mid-2016.

An update in time for buster would be very much appreciated.

Thanks,
Christopher Martin



Bug#917703: golang-gopkg-macaroon.v2: FTBFS: build-dependency not installable: golang-github-juju-testing-dev

2018-12-29 Thread Lucas Nussbaum
Source: golang-gopkg-macaroon.v2
Version: 0.0~git20171017.bed2a42-3
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 10), dh-golang, golang-any, 
> golang-github-juju-testing-dev, golang-golang-x-crypto-dev, 
> golang-gopkg-check.v1-dev
> Filtered Build-Depends: debhelper (>= 10), dh-golang, golang-any, 
> golang-github-juju-testing-dev, golang-golang-x-crypto-dev, 
> golang-gopkg-check.v1-dev
> dpkg-deb: building package 
> 'sbuild-build-depends-golang-gopkg-macaroon.v2-dummy' in 
> '/<>/resolver-3WmOKm/apt_archive/sbuild-build-depends-golang-gopkg-macaroon.v2-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-golang-gopkg-macaroon.v2-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-3WmOKm/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-3WmOKm/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-3WmOKm/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-3WmOKm/apt_archive ./ Sources [550 B]
> Get:5 copy:/<>/resolver-3WmOKm/apt_archive ./ Packages [638 B]
> Fetched 2151 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install golang-gopkg-macaroon.v2 build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-golang-gopkg-macaroon.v2-dummy : Depends: 
> golang-github-juju-testing-dev but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://aws-logs.debian.net/2018/12/29/golang-gopkg-macaroon.v2_0.0~git20171017.bed2a42-3_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



  1   2   3   4   >