Bug#901127: dpkg: dpkg crashed with segfault and core dump: ../../src/packages.c:245: process_queue: Assertion `dependtry <= 4' failed.

2018-06-08 Thread Axel Beckert
Package: dpkg
Version: 1.19.0.5+b1
Severity: important

Dear Guillem,

dpkg just crashed with a segfault during setting up all remaining
package after a dist-upgrade (via aptitude) which had some issues with a
few packages (namely some emacs plugins which caused emacs'
recompilation-trigger to fail). But it crashed on another package:

[...]
Setting up python-opencv (3.2.0+dfsg-4+b5) ...
dpkg: ../../src/packages.c:245: process_queue: Assertion `dependtry <= 4' 
failed.
Aborted (core dumped)

Additional facts: The machine did not have much free disk space and
hadn't been upgraded for months.

Backtrace:

Core was generated by `dpkg --configure -a'.
Program terminated with signal SIGABRT, Aborted.
#0  0xb7f0ad09 in __kernel_vsyscall ()
(gdb) bt
#0  0xb7f0ad09 in __kernel_vsyscall ()
#1  0xb7cf25b2 in __libc_signal_restore_set (set=0xbfacc6dc)
at ../sysdeps/unix/sysv/linux/nptl-signals.h:80
#2  __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:48
#3  0xb7cf39d1 in __GI_abort () at abort.c:79
#4  0xb7cea6ab in __assert_fail_base (
fmt=0xb7e44100 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", 
assertion=0x52d220 "dependtry <= 4", file=0x52d1ae "../../src/packages.c", 
line=245, function=0x52da18 <__PRETTY_FUNCTION__.6143> "process_queue")
at assert.c:92
#5  0xb7cea709 in __GI___assert_fail (assertion=0x52d220 "dependtry <= 4", 
file=0x52d1ae "../../src/packages.c", line=245, 
function=0x52da18 <__PRETTY_FUNCTION__.6143> "process_queue") at 
assert.c:101
#6  0x0050ccd0 in process_queue () at ../../src/packages.c:245
#7  0x0050cf1b in packages (argv=0xbfaccbd0) at ../../src/packages.c:162
#8  0x004fe79d in main (argc=, argv=)
at ../../src/main.c:926


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (900, 'testing'), (500, 'unstable-debug'), 
(500, 'buildd-unstable'), (201, 'experimental'), (1, 'experimental-debug'), (1, 
'buildd-experimental')
Architecture: i386 (i686)

Kernel: Linux 4.16.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages dpkg depends on:
ii  libbz2-1.0   1.0.6-8.1
ii  libc62.27-3
ii  liblzma5 5.2.2-1.3
ii  libselinux1  2.8-1
ii  tar  1.30+dfsg-2
ii  zlib1g   1:1.2.11.dfsg-1

dpkg recommends no packages.

Versions of packages dpkg suggests:
ii  apt1.6.1
pn  debsig-verify  

-- no debconf information



Bug#900605: mirrors: Debian mirror debian.parspack.com: unavailable

2018-06-08 Thread Farid Zarazvand
Yes, It was twice per day.
I have increased update frequency to 4 time per day as recommended,
on 4:10, 10:10, 16:10 and 22:10 (in UTC )

Regards,
Farid

On Tue, Jun 5, 2018 at 1:01 PM, Julien Cristau  wrote:

> Looks much better, thanks.
>
> How often does the mirror update?  It looks like it's about twice a day,
> versus the recommended 4 times (per
> https://www.debian.org/mirror/ftpmirror#when)?
>
> Cheers,
> Julien
>
> On 06/03/2018 12:45 PM, ParsPack Info wrote:
> > Hello
> >
> > Thank you, we have fixed the issue, would you please check this out
> again?
> >
> > Best Regards
> >
> > On Sat, Jun 2, 2018 at 1:59 AM, Julien Cristau  > > wrote:
> >
> > Package: mirrors
> > User: mirr...@packages.debian.org  debian.org>
> > Usertags: mirror-problem may-auto-close
> > Control: submitter -1 mirr...@debian.org 
> >
> > Hi,
> >
> > I was checking some things in the Debian mirror universe and noticed
> a
> > problem with your mirror:
> >
> > It seems your mirror is no longer available.  (I cannot reach it.)
> Is
> > this intentional?
> >
> > Status:
> > https://mirror-master.debian.org/status/mirror-info/debian.
> parspack.com.html
> >  parspack.com.html>
> >
> > Thanks,
> > Julien Cristau
> >
> >
>
>


Bug#901001: python3-minimal should Pre-Depend on python3.N-minimal

2018-06-08 Thread Steve Langasek
On Thu, Jun 07, 2018 at 03:00:46PM -0700, Julian Andres Klode wrote:
> Package: python3-default
> Severity: serious

> When python3 default version changes, and a new python3-minimal is
> unpacked before its python3.N-minimal, we end up with a system without a
> working python3 symlink.  This breaks upgrades because prerm scripts of
> python3 packages use:

> if which py3clean >/dev/null 2>&1; then
> py3clean -p PKGNAME 

> the which succeeds, as py3clean exists, but since the python3 symlink will be 
> broken,
> py3clean will be run and fail with Not Found.

> (originally reported at https://bugs.launchpad.net/bugs/1768379)
> (CCing debian-devel)

As discussed elsewhere, I concur that a pre-depends is the right solution
here.

However, just to explore the alternatives:  only the prerms are at issue,
because python3 packages should depend on python3; so while they also call
py3compile in the postinst, at time of postinst invocation the dependency
should always be satisfied which means that python3 -> python3-minimal ->
python3.X-minimal should all be unpacked and configured and therefore
/usr/bin/python (the interpreter of py3compile and py3clean) is a valid
symlink.

In the prerm case, there are two possible scenarios:

- the package is being removed; it is important to run py3clean so that
  stray files are not left behind in /usr/lib/python3.
- the package is being upgraded; it is in the common case (when no python
  module names have been dropped from within the package) less important to
  run py3clean because the same files will be recreated shortly afterwards
  by py3compile from the new postinst.

It is possible that the dh_python prerm snippet could be changed to skip the
redundant py3clean in the upgrade case; but in the removal case, this code
does need to be run unless python3 itself is also being removed, and there
is no way to enforce the availability of /usr/bin/python during a
dist-upgrade without this pre-depends.

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


signature.asc
Description: PGP signature


Bug#901126: gkrellmoon FTCBFS: uses the build architecture toolchain

2018-06-08 Thread Helmut Grohne
Source: gkrellmoon
Version: 0.6-5.1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

gkrellmoon fails to cross build from source, because it uses the build
architecture toolchain. debian/rules does not pass cross tools to make
(fixed by using dh_auto_build) and the build system does not pick them
up properly. Furthermore it stuffs flags into CC, which get overridden
by dh_auto_build, so they must be moved out of CC. After applying the
attached patch, gkrellmoon cross builds successfully. Please consider
using it.

Helmut
diff -u gkrellmoon-0.6/Makefile gkrellmoon-0.6/Makefile
--- gkrellmoon-0.6/Makefile
+++ gkrellmoon-0.6/Makefile
@@ -1,5 +1,6 @@
-GTK_INCLUDE = `pkg-config gtk+-2.0 --cflags`
-GTK_LIB = `pkg-config gtk+-2.0 --libs`
+PKG_CONFIG ?= pkg-config
+GTK_INCLUDE = `$(PKG_CONFIG) gtk+-2.0 --cflags`
+GTK_LIB = `$(PKG_CONFIG) gtk+-2.0 --libs`
 
 INSTALLDIR = ${DESTDIR}/usr/lib/gkrellm2/plugins
 
@@ -8,12 +9,14 @@
 LIBS = $(GTK_LIB)
 LFLAGS = -shared
 
-CC = gcc $(CFLAGS) $(FLAGS)
+CC = gcc
+%.o:%.c
+   $(CC) $(CFLAGS) $(FLAGS) -c $< -o $@
 
 OBJS = gkrellmoon.o MoonRise.o CalcEphem.o Moon.o
 
 gkrellmoon.so: $(OBJS)
-   $(CC) $(OBJS) -o gkrellmoon.so $(LFLAGS) $(LIBS)
+   $(CC) $(CFLAGS) $(FLAGS) $(OBJS) -o gkrellmoon.so $(LFLAGS) $(LIBS)
 
 clean:
rm -f *.o core *.so* *.bak *~
diff -u gkrellmoon-0.6/debian/changelog gkrellmoon-0.6/debian/changelog
--- gkrellmoon-0.6/debian/changelog
+++ gkrellmoon-0.6/debian/changelog
@@ -1,3 +1,13 @@
+gkrellmoon (0.6-5.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ Let dh_auto_build pass cross tools to make.
++ Do not stuff flags into CC.
++ Make pkg-config substitutable.
+
+ -- Helmut Grohne   Sat, 09 Jun 2018 06:48:10 +0200
+
 gkrellmoon (0.6-5.1) unstable; urgency=medium
 
   * Non-maintainer upload
diff -u gkrellmoon-0.6/debian/rules gkrellmoon-0.6/debian/rules
--- gkrellmoon-0.6/debian/rules
+++ gkrellmoon-0.6/debian/rules
@@ -19,10 +19,7 @@
 
 build:
dh_testdir
-
-   # Add here commands to compile the package.
-   $(MAKE)
-
+   dh_auto_build
 
 clean:
dh_testdir


Bug#853258: #853258 docker.io: uses sleep to query user in maintainer script

2018-06-08 Thread Dmitry Smirnov
To me severity of this issue is minor:

1) Purge does exactly what's expected. IMHO no need to prompt user, not at 
the cost of debconf maintenance for merely one boolean question.

2) This not a real prompt but merely a 10 seconds delay. Could have been 
worse but definitely breaks no unattended scripts.

3) Using debconf would elevate harmless delay to full interactive prompt 
demanding user's response which appears excessive as "purge" is already 
chosen.

4) To me script is already policy compliant because 10 seconds delay without 
human interaction is not a real prompt hence is does not fall under §3.9.1 
[1].

5) To avoid any doubt I'm going to patch away prompt and delay.

[1]: https://www.debian.org/doc/debian-policy/#prompting-in-maintainer-scripts

-- 
Best wishes,
 Dmitry Smirnov

---

Truth never damages a cause that is just.
-- Mahatma Gandhi


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


Bug#901125: npm2deb: npm notice messages confuse npm2deb create

2018-06-08 Thread Diane Trout
Package: npm2deb
Version: 0.2.7-6
Severity: normal
Tags: patch

Dear Maintainer,

While trying to use npm2deb with my prototype package form npm 6.0.1 I
discovered newer versions of npm report more warning messages

so Npm2Deb.download() was failing with a filename to long error message because
npm pack now reports extra information:

$ npm pack cmd-shim
npm notice
npm notice   cmd-shim@2.0.2
npm notice === Tarball Contents ===
npm notice 444B  package.json
npm notice 98B   .npmignore
npm notice 1.1kB README.md
npm notice 1.3kB LICENSE
npm notice 4.6kB index.js
npm notice 47B   .travis.yml
npm notice 861B  test/00-setup.js
npm notice 6.0kB test/basic.js
npm notice 277B  test/zz-cleanup.js
npm notice === Tarball Details ===
npm notice name:  cmd-shim
npm notice version:   2.0.2
npm notice filename:  cmd-shim-2.0.2.tgz
npm notice package size:  5.1 kB
npm notice unpacked size: 14.8 kB
npm notice shasum:6fcbda99483a8fd15d7d30a196ca69d688a2efdb
npm notice integrity: sha512-NLt0ntM0kvuSN[...]p1WI00eetDYzw==
npm notice total files:   9
npm notice
cmd-shim-2.0.2.tgz


A pretty simple solution is instead to do "npm pack -q cmd-shim" which just
prints the tgz file name as expected.

I tested on stretch and npm 1.4.21+ds-2 support npm pack -q

Diane



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

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

Versions of packages npm2deb depends on:
ii  devscripts2.18.3
ii  node-github-url-from-git  1.4.0-1
ii  npm   6.0.1+ds-1
ii  python3   3.6.5-3
ii  python3-dateutil  2.6.1-1

npm2deb recommends no packages.

npm2deb suggests no packages.

-- no debconf information
>From f51da497495a48aaf33d2c686b4e0f02fc2e8929 Mon Sep 17 00:00:00 2001
From: Diane Trout 
Date: Fri, 8 Jun 2018 20:08:39 -0700
Subject: [PATCH] Force quiet mode on download

---
 npm2deb/__init__.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/npm2deb/__init__.py b/npm2deb/__init__.py
index 3f7c187..e508803 100644
--- a/npm2deb/__init__.py
+++ b/npm2deb/__init__.py
@@ -397,7 +397,7 @@ and may not include tests.\n""")
 
 def download(self):
 utils.debug(1, "downloading %s tarball from npm registry" % self.name)
-info = _getstatusoutput('npm pack "%s"' % self.name)
+info = _getstatusoutput('npm pack -q "%s"' % self.name)
 if info[0] is not 0:
 exception = "Error downloading package %s\n" % self.name
 exception += info[1]
-- 
2.17.1



Bug#901124: roundcube: patching roundcube breaks it

2018-06-08 Thread stven jones
Package: roundcube
Version: 1.2.3+dfsg.1-4+deb9u2
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?

Patching operating system

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

reset the debian database config to the remote mysql server's IP after the 
patching wiped this.

   * What was the outcome of this action?

roundcube now works.

   * What outcome did you expect instead?

That the locally set config is not altered on patching but local config is 
honoured.

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


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

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

Versions of packages roundcube depends on:
ii  dpkg1.18.24
ii  roundcube-core  1.2.3+dfsg.1-4+deb9u2

roundcube recommends no packages.

roundcube suggests no packages.

Versions of packages roundcube-core depends on:
ii  dbconfig-common 2.0.8
ii  debconf [debconf-2.0]   1.5.61
ii  dpkg1.18.24
ii  libapache2-mod-php7.0 [libapache2-mod-php]  7.0.27-0+deb9u1
ii  libmagic1   1:5.30-1+deb9u1
ii  php-auth-sasl   1.0.6-3
ii  php-common  1:49
ii  php-mail-mime   1.10.0-2
ii  php-mcrypt  1:7.0+49
ii  php-net-smtp1.7.1-2
ii  php-net-socket  1.0.14-2
ii  php-pear1:1.10.1+submodules+notgz-9
ii  php7.0-cli [php-cli]7.0.27-0+deb9u1
ii  php7.0-intl [php-intl]  7.0.27-0+deb9u1
ii  php7.0-json [php-json]  7.0.27-0+deb9u1
ii  php7.0-mcrypt [php-mcrypt]  7.0.27-0+deb9u1
ii  roundcube-mysql 1.2.3+dfsg.1-4+deb9u2
ii  ucf 3.0036

Versions of packages roundcube-core recommends:
ii  apache2 [httpd-cgi] 2.4.25-3+deb9u4
ii  php-pspell  1:7.0+49
ii  php7.0-gd [php-gd]  7.0.27-0+deb9u1
ii  php7.0-pspell [php-pspell]  7.0.27-0+deb9u1

Versions of packages roundcube-core suggests:
pn  php-crypt-gpg  
pn  php-net-ldap2  
pn  php-net-ldap3  
ii  roundcube-plugins  1.2.3+dfsg.1-4+deb9u2

-- debconf information:
  roundcube/app-password-confirm: (password omitted)
  roundcube/password-confirm: (password omitted)
  roundcube/mysql/app-pass: (password omitted)
  roundcube/mysql/admin-pass: (password omitted)
* roundcube/mysql/admin-user: root
* roundcube/dbconfig-reinstall: false
  roundcube/passwords-do-not-match:
* roundcube/restart-webserver: true
  roundcube/dbconfig-upgrade: true
* roundcube/dbconfig-install: true
* roundcube/language: en_US
  roundcube/missing-db-package-error: abort
* roundcube/reconfigure-webserver: apache2, lighttpd
  roundcube/db/dbname: roundcubemail
  roundcube/upgrade-backup: true
  roundcube/remote/newhost:
  roundcube/remote/port:
  roundcube/internal/skip-preseed: false
* roundcube/install-error: ignore
  roundcube/mysql/method: Unix socket
* roundcube/hosts:
  roundcube/upgrade-error: abort
  roundcube/db/app-user: roundcube@localhost
  roundcube/remote/host: localhost
  roundcube/purge: false
* roundcube/database-type: mysql
  roundcube/internal/reconfiguring: false
  roundcube/remove-error: abort
  roundcube/dbconfig-remove: true



Bug#901122: ess fails to start when emacs instance started with git mergetool

2018-06-08 Thread Dirk Eddelbuettel


On 9 June 2018 at 12:28, Pavel N. Krivitsky wrote:
| Package: ess
| Version: 17.11-2
| Severity: normal
| Tags: patch
| 
| Dear Maintainer,

How about we close this here and you reopen over here:
https://github.com/emacs-ess/ESS/issues

There is not a long I can do for you here...

Dirk
| 
| STEPS TO REPRODUCE:
| 
| 1) Set up a git merge conflict:
| 
| # Create the repository.
| git init test
| cd test
| 
| # Create and commit a file containing '0' (a syntactically correct R file).
| echo '0' > test.R
| git add .
| git commit -m 'Zero.'
| 
| # Create a branch in which '0' is replaced by '1'.
| git branch one
| git checkout one
| echo '1' > test.R
| git add .
| git commit -m 'One.'
| 
| # Replace '0' with '2' in the mater branch.
| git checkout master
| echo '2' > test.R
| git add .
| git commit -m 'Two.'
| 
| # Attempt a merge, creating a conflict.
| git checkout one
| git merge master
| 
| 2) Try running mergetool with emacs as editor:
| 
| git mergetool -t emerge
| 
| EXPECTED RESULT:
| 
| A three-way merge interface comes up with files open in ESS R mode.
| 
| ACTUAL RESULT:
| 
| Empty emacs buffer appears, with the following message in the minibuffer
| (without the quotes):
| "ess-mode: Customise alist is not specified, nor  ess-local-customize-alist is
| set."
| 
| 
| 
| -- System Information:
| Debian Release: buster/sid
|   APT prefers testing
|   APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'unstable'), 
(500, 'stable'), (500, 'oldstable')
| Architecture: amd64 (x86_64)
| Foreign Architectures: i386
| 
| Kernel: Linux 4.16.0-1-amd64 (SMP w/8 CPU cores)
| Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU.UTF-8 (charmap=UTF-8)
| Shell: /bin/sh linked to /bin/dash
| Init: systemd (via /run/systemd/system)
| LSM: AppArmor: enabled
| 
| Versions of packages ess depends on:
| ii  dpkg1.19.0.5+b1
| ii  emacsen-common  2.0.8
| ii  install-info6.5.0.dfsg.1-3
| 
| Versions of packages ess recommends:
| ii  r-base-core  3.4.4-1+b2
| 
| Versions of packages ess suggests:
| ii  jags   4.3.0-1
| ii  julia  0.4.7-7+b3
| pn  pspp   
| pn  xlispstat  
| 
| -- no debconf information

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



Bug#901122: Patch tag is in error.

2018-06-08 Thread Pavel N. Krivitsky
Dear Maintainer,

My apologies, there is no patch. I made a mistake on reportbug.

Best,
Pavel



Bug#899030: jessie-pu: package intel-microcode/3.20180425.1~deb8u1

2018-06-08 Thread Henrique de Moraes Holschuh
On Fri, 08 Jun 2018, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Fri, 2018-05-18 at 12:24 -0300, Henrique de Moraes Holschuh wrote:
> ...
> > I'd like to update the intel-microcode package in Debian jessie.
> > 
> > This update adds the microcode-side fix for CVE-2017-5715 aka Spectre
> > v2.
> > 
> > It has been very extensibly tested, as noted in the changelog:
> > 
> 
> Please go ahead.

Uploaded, thank you!

Now waiting for a go-ahead for the stretch-pu version (#899006).  It is
the very same package, the only differences between the two are in
debian/changelog.

-- 
  Henrique Holschuh



Bug#901123: xfonts-jmk: Add Unicode 7.0 runic characters to neep

2018-06-08 Thread Ben Wong
Package: xfonts-jmk
Version: 3.0-21
Severity: normal
Tags: patch

Dear Maintainer,

The neep font has surprisingly good Unicode coverage, but it is
missing some characters. In particular, I noticed it is missing the
eight RUNIC LETTERS, U+16F1 to U+16F8, that were added in Unicode 7.0
a few years ago. These glyphs are necessary for rendering things like
the Franks Casket, Tolkein's moon-letters, and certain video games. 

I have created glyphs for both the 10x20 and 6x13 sizes. To use them,
simply apply the attached runicupdate.patch to the files in
xfonts-jmk/neep/iso10646-1-parts/.

cd xfonts-jmk
patch -p0 < runicupdate.patch
fakeroot dh binary
sudo dpkg -i ../xfonts-jmk*deb
xset fp rehash

To examine what my additions look like, see the last eight glyphs in
the xfd screenshot (attached). Or cat the runic.txt file (also
attached) in an xterm that has been started like so:

xterm -fn *neep-medium-r-normal--20*10646*
cat runic.txt

I hand drew the 10x20 letterforms using gbdfed, but the shapes were
were inspired and informed by GNU unifont and the BabelStone Beowulf.
I designed the style to match the current runic characters already in
the Neep font. The 6x13 letterforms are simply cropped versions from
unifont.

Note: I only added the extra runes to the three variants of Neep that
already had runes in that region: 10x20, 10x20-bold, and 6x13. I did
not touch 6x13-bold, 8x15, nor 8x15-bold.


(Also note: moon-letters may not be visible until viewed under
starlight or moonlight. This is not a bug.)

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

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

Versions of packages xfonts-jmk depends on:
ii  xfonts-utils  1:7.7+4

xfonts-jmk recommends no packages.

xfonts-jmk suggests no packages.

-- no debconf information
--- neep/iso10646-1-parts/neep-iso10646-1-part-06x13.bdf.orig   2018-06-08 
17:22:00.0 -0700
+++ neep/iso10646-1-parts/neep-iso10646-1-part-06x13.bdf2018-06-08 
17:46:03.407327222 -0700
@@ -25,11 +25,11 @@
 FONT_DESCENT 2
 FONT_ASCENT 11
 COPYRIGHT "Public domain font.  Share and enjoy."
-_XMBDFED_INFO "Edited with xmbdfed 4.5."
 CAP_HEIGHT 9
 X_HEIGHT 6
+_GBDFED_INFO "Edited with gbdfed 1.6."
 ENDPROPERTIES
-CHARS 4238
+CHARS 4246
 STARTCHAR Amacron
 ENCODING 256
 SWIDTH 480 0
@@ -27430,6 +27430,166 @@
 00
 00
 ENDCHAR
+STARTCHAR U+16F1
+ENCODING 5873
+SWIDTH 480 0
+DWIDTH 6 0
+BBX 6 13 0 -2
+BITMAP
+00
+00
+80
+80
+80
+A0
+A0
+D0
+90
+88
+88
+00
+00
+ENDCHAR
+STARTCHAR U+16F2
+ENCODING 5874
+SWIDTH 480 0
+DWIDTH 6 0
+BBX 6 13 0 -2
+BITMAP
+00
+00
+08
+88
+C8
+A8
+98
+88
+80
+80
+80
+00
+00
+ENDCHAR
+STARTCHAR U+16F3
+ENCODING 5875
+SWIDTH 480 0
+DWIDTH 6 0
+BBX 6 13 0 -2
+BITMAP
+00
+00
+20
+70
+A8
+70
+20
+20
+20
+20
+20
+00
+00
+ENDCHAR
+STARTCHAR U+16F4
+ENCODING 5876
+SWIDTH 480 0
+DWIDTH 6 0
+BBX 6 13 0 -2
+BITMAP
+00
+00
+40
+50
+50
+58
+70
+D0
+50
+50
+10
+00
+00
+ENDCHAR
+STARTCHAR U+16F5
+ENCODING 5877
+SWIDTH 480 0
+DWIDTH 6 0
+BBX 6 13 0 -2
+BITMAP
+00
+00
+00
+38
+E0
+38
+E0
+38
+E0
+38
+00
+00
+00
+ENDCHAR
+STARTCHAR U+16F6
+ENCODING 5878
+SWIDTH 480 0
+DWIDTH 6 0
+BBX 6 13 0 -2
+BITMAP
+00
+00
+80
+40
+48
+30
+20
+50
+90
+08
+08
+00
+00
+ENDCHAR
+STARTCHAR U+16F7
+ENCODING 5879
+SWIDTH 480 0
+DWIDTH 6 0
+BBX 6 13 0 -2
+BITMAP
+00
+00
+80
+80
+80
+E0
+90
+88
+88
+88
+88
+00
+00
+ENDCHAR
+STARTCHAR U+16F8
+ENCODING 5880
+SWIDTH 480 0
+DWIDTH 6 0
+BBX 6 13 0 -2
+BITMAP
+00
+00
+20
+20
+20
+20
+20
+20
+50
+88
+88
+00
+00
+ENDCHAR
 STARTCHAR uni1E00
 ENCODING 7680
 SWIDTH 480 0
--- neep/iso10646-1-parts/neep-iso10646-1-part-10x20.bdf.orig   2018-06-08 
17:22:00.0 -0700
+++ neep/iso10646-1-parts/neep-iso10646-1-part-10x20.bdf2018-06-07 
03:52:08.925123279 -0700
@@ -27,9 +27,9 @@
 X_HEIGHT 9
 CAP_HEIGHT 13
 COPYRIGHT "Public domain font.  Share and enjoy."
-_XMBDFED_INFO "Edited with xmbdfed 4.5."
+_GBDFED_INFO "Edited with gbdfed 1.6."
 ENDPROPERTIES
-CHARS 4821
+CHARS 4829
 STARTCHAR Amacron
 ENCODING 256
 SWIDTH 480 0
@@ -53029,6 +53029,222 @@
 
 
 
+
+ENDCHAR
+STARTCHAR U+16F1
+ENCODING 5873
+SWIDTH 480 0
+DWIDTH 10 0
+BBX 10 20 0 -4
+BITMAP
+
+
+
+6000
+6000
+6000
+6000
+6600
+6E00
+7E00
+7B00
+7300
+6300
+6180
+6180
+6180
+
+
+
+
+ENDCHAR
+STARTCHAR U+16F2
+ENCODING 5874
+SWIDTH 480 0
+DWIDTH 10 0
+BBX 10 20 0 -4
+BITMAP
+
+
+
+0180
+6180
+7180
+7980
+6D80
+6780
+6380
+6180
+6000
+6000
+6000
+6000
+6000
+
+
+
+
+ENDCHAR
+STARTCHAR U+16F3
+ENCODING 5875
+SWIDTH 480 0
+DWIDTH 10 0
+BBX 10 20 0 -4
+BITMAP
+
+
+
+0C00
+1E00
+3F00
+6D80
+4C80
+6D80
+3F00
+1E00
+0C00
+0C00
+0C00
+0C00
+0C00

Bug#901122: ess fails to start when emacs instance started with git mergetool

2018-06-08 Thread Pavel N. Krivitsky
Package: ess
Version: 17.11-2
Severity: normal
Tags: patch

Dear Maintainer,

STEPS TO REPRODUCE:

1) Set up a git merge conflict:

# Create the repository.
git init test
cd test

# Create and commit a file containing '0' (a syntactically correct R file).
echo '0' > test.R
git add .
git commit -m 'Zero.'

# Create a branch in which '0' is replaced by '1'.
git branch one
git checkout one
echo '1' > test.R
git add .
git commit -m 'One.'

# Replace '0' with '2' in the mater branch.
git checkout master
echo '2' > test.R
git add .
git commit -m 'Two.'

# Attempt a merge, creating a conflict.
git checkout one
git merge master

2) Try running mergetool with emacs as editor:

git mergetool -t emerge

EXPECTED RESULT:

A three-way merge interface comes up with files open in ESS R mode.

ACTUAL RESULT:

Empty emacs buffer appears, with the following message in the minibuffer
(without the quotes):
"ess-mode: Customise alist is not specified, nor  ess-local-customize-alist is
set."



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

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

Versions of packages ess depends on:
ii  dpkg1.19.0.5+b1
ii  emacsen-common  2.0.8
ii  install-info6.5.0.dfsg.1-3

Versions of packages ess recommends:
ii  r-base-core  3.4.4-1+b2

Versions of packages ess suggests:
ii  jags   4.3.0-1
ii  julia  0.4.7-7+b3
pn  pspp   
pn  xlispstat  

-- no debconf information



Bug#898237: unable to find IP for freedombox

2018-06-08 Thread hjenkins
Solved.

Added workaround instructions for re-instating a fixed-IP network
configuration after running freedombox-setup at:

https://wiki.debian.org/FreedomBox/Hardware/Debian

Most of the problem was my complete unfamiliarity with NetworkManager,
including not knowing that a lot of things can't be changed through nmtui
but can be changed through nmcli (as of May 2018).



Bug#900985: [procps debian Stretch 9.4] procps : Depends: libprocps6 but it is not going to be installed

2018-06-08 Thread Craig Small
Hi Jean-Marc,

Can you try installing libprocps6 directly? Eg apt install libprocps6 procps

It's saying it cannot install it but not why. I suspect there is something
awry with that arch but not sure what.

 - Craig

>
> --
Craig Small https://dropbear.xyz/ csmall at : dropbear.xyz
Debian GNU/Linuxhttps://www.debian.org/   csmall at : debian.org
Mastodon: @smalls...@social.dropbear.xyz Twitter: @smallsees
GPG fingerprint:  5D2F B320 B825 D939 04D2  0519 3938 F96B DF50 FEA5


Bug#901114: python-coverage: FTBFS when built with dpkg-buildpackage -A

2018-06-08 Thread Santiago Vila
On Sat, Jun 09, 2018 at 10:26:05AM +1000, Ben Finney wrote:

> The package currently has (discovered when investigating this
> behaviour, so thank you) a bug in its definition of the ‘debian/rules’
> target ‘override_dh_auto_build’.
> 
> I'm unsure about Debhelper failing to find the sequence for ‘python2’.
> That should already be pulled in when you install the build
> dependencies. Maybe this is complicated by the
> ‘override_dh_auto_build’ bug.
> 
> I am adding this change, please let me know whether it corrects the
> package behaviour for you:

Sorry, I can't test external packages easily in my setup.

Instead, I'll be more precise so that you can reproduce this too:

I'm using "sbuild --arch-all --no-arch-any" on a clean chroot,
which is what an official autobuilder would do to build the arch-indep
packages.

By looking at the debian/control file, this seems to be a bad interaction
between Build-Depends / Build-Depends-Indep / Build-Depends-Arch.

My feeling is that you are assuming some packages to be present
when in fact they do not necessarily have to be present according to
debian/control when building only the arch-independent packages.

(And this would be why debhelper does not "find" the python2 thing).

Hope this helps.



Bug#901121: turing: missing dependency on python3-matplotlib

2018-06-08 Thread Ludovic Brenta
Package: turing
Version: 0.10~beta-1
Severity: serious

Dear Maintainer,

Launching turing on the command line yields:

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-lbrenta'
NoneType: None
Traceback (most recent call last):
  File "/usr/share/turing/src/main.py", line 86, in 
from forms import mainwindow
  File "/usr/share/turing/src/forms/mainwindow.py", line 15, in 
from matplotlib.axes import Axes
ModuleNotFoundError: No module named 'matplotlib'

Installing the package python3-matplotlib solves this problem.

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

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

Versions of packages turing depends on:
ii  python3 3.6.5-3
ii  python3-altgraph0.15~repack0-2
ii  python3-autopep81.3.5-2
ii  python3-cycler  0.10.0-1
ii  python3-dateutil2.6.1-1
ii  python3-docutils0.14+dfsg-3
ii  python3-future  0.15.2-4
ii  python3-jedi0.11.1-1
ii  python3-kiwisolver  1.0.1-2
ii  python3-macholib1.9+repack0-1
ii  python3-numpy   1:1.14.3-2
ii  python3-parso   0.1.1-1
ii  python3-pefile  2017.11.5-2
ii  python3-pep81.7.1-1
ii  python3-pyflakes1.6.0-1
ii  python3-pygments2.2.0+dfsg-1
ii  python3-pyparsing   2.2.0+dfsg1-2
ii  python3-pyqt5   5.10.1+dfsg-2
ii  python3-tz  2018.4-1

turing recommends no packages.

turing suggests no packages.

-- no debconf information



Bug#901114: python-coverage: FTBFS when built with dpkg-buildpackage -A

2018-06-08 Thread Ben Finney
Control: tags -1 + patch moreinfo

On 08-Jun-2018, Santiago Vila wrote:

>  dpkg-source --before-build python-coverage-4.5+dfsg.1
>  fakeroot debian/rules clean
> debian/rules:166: warning: overriding recipe for target 
> 'override_dh_auto_build'
> debian/rules:129: warning: ignoring old recipe for target 
> 'override_dh_auto_build'
> dh clean --with python3,python2,pypy,sphinxdoc --buildsystem=pybuild
> dh: unable to load addon python2: Can't locate 
> Debian/Debhelper/Sequence/python2.pm in @INC (you may need to install the 
> Debian::Debhelper::Sequence::python2 module) (@INC contains: /etc/perl 
> /usr/local/lib/x86_64-linux-gnu/perl/5.26.2 /usr/local/share/perl/5.26.2 
> /usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 
> /usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 
> /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 10) 
> line 1.
> BEGIN failed--compilation aborted at (eval 10) line 1.

The package currently has (discovered when investigating this
behaviour, so thank you) a bug in its definition of the ‘debian/rules’
target ‘override_dh_auto_build’.

I'm unsure about Debhelper failing to find the sequence for ‘python2’.
That should already be pulled in when you install the build
dependencies. Maybe this is complicated by the
‘override_dh_auto_build’ bug.

I am adding this change, please let me know whether it corrects the
package behaviour for you:


diff --git a/debian/rules b/debian/rules
index cd4633de..8f9a88f1 100755
--- a/debian/rules
+++ b/debian/rules
@@ -127,6 +127,8 @@ endef # uscan-download-source
 override_dh_auto_build: remove-bundled-libraries
 override_dh_auto_build:
dh_auto_build --buildsystem=pybuild
+   $(SPHINX) ${SPHINX_OPTS} -bhtml ${DOCUMENTATION_DIR}/ \
+ ${DOCUMENTATION_BUILD_HTML_DIR}/
 
 # Upstream test suite doesn't currently run in our build environment.
 override_dh_auto_test:
@@ -162,11 +164,6 @@ override_dh_auto_clean:
   dh_auto_clean
   $(RM) -r ${GENERATED_FILES}
 
-override_dh_auto_build:
-   dh_auto_build
-   $(SPHINX) ${SPHINX_OPTS} -bhtml ${DOCUMENTATION_DIR}/ \
- ${DOCUMENTATION_BUILD_HTML_DIR}/
-
 
 # Local variables:
 # mode: makefile

-- 
 \  “Begin with false premises and you risk reaching false |
  `\   conclusions. Begin with falsified premises and you forfeit your |
_o__)  authority.” —Kathryn Schulz, 2015-10-19 |
Ben Finney 


signature.asc
Description: PGP signature


Bug#802284: git-buildpackage: should assemble overlay before issuing 'debian/rules' commands

2018-06-08 Thread Ben Finney
Control: found -1 git-buildpackage/0.9.9
Control: affects -1 src:python-coverage

On 01-Dec-2017, Guido Günther wrote:
> […] since the upstream tarball is not in the build-area at this
> point "debuild -S" will complain. That's o.k. since the postexport
> hook is exactly for messing with the upstream sources.

My point in reporting this bug is that “hooks” should not be needed.

Git-BuildPackage should simply assemble the package source as an
overlay, *before* calling ‘debuild -S’ or ‘debian/rules clean’ or
anything else which requires the source assembled in that directory.

That shouldn't require defining a hook; it should be the default
behaviour in response to “this package source should be assembled as
an overlay” (the ‘overlay = true’ option).

-- 
 \“You can't have everything; where would you put it?” —Steven |
  `\Wright |
_o__)  |
Ben Finney 


signature.asc
Description: PGP signature


Bug#900437: Acknowledgement (Erroneous generated code)

2018-06-08 Thread Mario Xerxes Castelán Castro
Any advance? Did you report it upstream?



signature.asc
Description: OpenPGP digital signature


Bug#900398: mariadb-server-10.1: postinst fails since official rebuild

2018-06-08 Thread Faustin Lammler
Hi Paul,
my guess is that the DB crashed so the 'tc.log' file was created and it
prevent the mariadb-server to start again.

Let me check with the dev team were to investigate on this possible
crash and I will come back to you.

In the mean time, if you want to continue your investigation, I suggest
you to take a look at:
https://jira.mariadb.org/browse/MDEV-16442?jql=text%20~%20%22tc.log%22

Faustin



Bug#887610: vim-fugitive: Doesn't quote filenames

2018-06-08 Thread Andrea Capriotti
Il giorno gio, 18/01/2018 alle 13.42 +0100, Philipp Marek ha scritto:
> Package: vim-fugitive
> Version: 2.2-2
> Severity: normal
> 
> At least the current version doesn't quote filenames when passing to
> "git", 
> so any pathnames with spaces in them aren't relayed properly.
> 
> Eg. when in a (git) relative directory "with spaces", the command
> :Git add file
> 
> translates to
> :!LANG=C git add with spaces/filename
> 
> and that makes "git" return
> 
> fatal: pathspec 'with' did not match any files

Hi Philipp, 

it should be fixed in 2.3-1 version. 

Let me know if it works and I can close the bug.

Regards
-- 
Andrea Capriotti 

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


Bug#901103: adios: FTBFS when built with dpkg-buildpackage -A

2018-06-08 Thread Santiago Vila
On Fri, Jun 08, 2018 at 11:22:59PM +, Santiago Vila wrote:
> Package: src:adios
> Version: 1.13.1-1
> Severity: serious
> 
> Dear maintainer:
> 
> I tried to build this package in stretch with "dpkg-buildpackage -A"

Oops. I meant "buster" here, of course. (The same is also true for the
other 16 bug reports I've just reported right now).

Sorry for the confusion.



Bug#901120: RFS: linoleum/1.6-1 [ITP] -- Java desktop environment

2018-06-08 Thread raphael . jolly
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

* Package name: linoleum
   Version : 1.6-1
   Upstream Author : Raphael Jolly 
* URL : http://linoleum.java.net/
* License : GPL
  Section : java

It builds those binary packages:

  linoleum   - Java desktop environment and software distribution

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/l/linoleum/linoleum_1.6-1.dsc

More information about linoleum can be obtained from http://linoleum.java.net/

Changes since the last upload:

Initial release.

Regards,
 Raphael Jolly



Bug#901118: udunits: FTBFS when built with dpkg-buildpackage -A

2018-06-08 Thread Santiago Vila
Package: src:udunits
Version: 2.2.26-4
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep  
   dh_update_autotools_config -i
   dh_autoreconf -i
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: copying file 'build-aux/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:78: installing 'build-aux/compile'
configure.ac:16: installing 'build-aux/missing'

[... snipped ...]

Output written on udunits2.pdf (13 pages, 168679 bytes).
Transcript written on udunits2.log.
make[3]: Leaving directory '/<>'
Making html in lib
make[3]: Entering directory '/<>/lib'
make[4]: Entering directory '/<>/lib'
make[4]: Nothing to be done for 'html-am'.
make[4]: Leaving directory '/<>/lib'
make[3]: Leaving directory '/<>/lib'
Making html in prog
make[3]: Entering directory '/<>/prog'
make[3]: Nothing to be done for 'html'.
make[3]: Leaving directory '/<>/prog'
make[3]: Entering directory '/<>'
rm -rf udunits2.htp
if /bin/bash /<>/build-aux/missing makeinfo --html --no-split  -I 
. \
 -o udunits2.htp udunits2.texi; \
then \
  rm -rf udunits2.html && mv udunits2.htp udunits2.html; \
else \
  rm -rf udunits2.htp; exit 1; \
fi
make[3]: Leaving directory '/<>'
Making info in lib
make[3]: Entering directory '/<>/lib'
make[4]: Entering directory '/<>/lib'
make[4]: Nothing to be done for 'info-am'.
make[4]: Leaving directory '/<>/lib'
make[3]: Leaving directory '/<>/lib'
Making info in prog
make[3]: Entering directory '/<>/prog'
make[3]: Nothing to be done for 'info'.
make[3]: Leaving directory '/<>/prog'
make[3]: Entering directory '/<>'
make[3]: Nothing to be done for 'info-am'.
make[3]: Leaving directory '/<>'
make[2]: Leaving directory '/<>'
cp udunits2.info debian/udunits-bin/usr/share/info
cp: cannot create regular file 'debian/udunits-bin/usr/share/info': No such 
file or directory
debian/rules:22: recipe for target 'override_dh_auto_install' failed
make[1]: *** [override_dh_auto_install] Error 1
make[1]: Leaving directory '/<>'
debian/rules:15: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


To reproduce, please try "dpkg-buildpackage -A".
(The error does not happen with "dpkg-buildpackage").

Thanks.



Bug#901113: pyro: FTBFS when built with dpkg-buildpackage -A

2018-06-08 Thread Santiago Vila
Package: src:pyro
Version: 1:3.16-2
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_configure -i
   dh_auto_build -i
make -j1 "INSTALL=install --strip-program=true"
make[1]: Entering directory '/<>'
This makefile is only for cleaning stuff up. ('make clean')
You can also build the tarball dist with it ('make sdist')
You can also build the win32 binary dist with it ('make windist')
make[1]: Leaving directory '/<>'
   dh_auto_test -i
   create-stamp debian/debhelper-build-stamp

[... snipped ...]

copying build/scripts-2.7/pyro-ns -> /<>/debian/tmp/usr/local/bin
copying build/scripts-2.7/pyro-nsd -> /<>/debian/tmp/usr/local/bin
copying build/scripts-2.7/pyro-es -> /<>/debian/tmp/usr/local/bin
copying build/scripts-2.7/pyro-wxnsc -> 
/<>/debian/tmp/usr/local/bin
changing mode of /<>/debian/tmp/usr/local/bin/pyro-genguid to 775
changing mode of /<>/debian/tmp/usr/local/bin/pyro-nsc to 775
changing mode of /<>/debian/tmp/usr/local/bin/pyro-esd to 775
changing mode of /<>/debian/tmp/usr/local/bin/pyro-xnsc to 775
changing mode of /<>/debian/tmp/usr/local/bin/pyro-ns to 775
changing mode of /<>/debian/tmp/usr/local/bin/pyro-nsd to 775
changing mode of /<>/debian/tmp/usr/local/bin/pyro-es to 775
changing mode of /<>/debian/tmp/usr/local/bin/pyro-wxnsc to 775
running install_egg_info
Writing 
/<>/debian/tmp/usr/local/lib/python2.7/dist-packages/Pyro-3.16.egg-info
mv debian/tmp/usr/local/lib debian/tmp/usr/lib
dh_install -ppyro -Xwxnsc.py -Xxnsc.py
dh_install: Cannot find (any matches for) "usr/bin/pyro-es" (tried in ., 
debian/tmp)

dh_install: pyro missing files: usr/bin/pyro-es
dh_install: Cannot find (any matches for) "usr/bin/pyro-genguid" (tried in ., 
debian/tmp)

dh_install: pyro missing files: usr/bin/pyro-genguid
dh_install: Cannot find (any matches for) "usr/bin/pyro-ns" (tried in ., 
debian/tmp)

dh_install: pyro missing files: usr/bin/pyro-ns
dh_install: Cannot find (any matches for) "usr/bin/pyro-nsc" (tried in ., 
debian/tmp)

dh_install: pyro missing files: usr/bin/pyro-nsc
dh_install: Cannot find (any matches for) "usr/bin/pyro-esd" (tried in ., 
debian/tmp)

dh_install: pyro missing files: usr/bin/pyro-esd
dh_install: Cannot find (any matches for) "usr/bin/pyro-nsd" (tried in ., 
debian/tmp)

dh_install: pyro missing files: usr/bin/pyro-nsd
dh_install: missing files, aborting
install -d debian/.debhelper/generated/pyro
install -d debian/.debhelper/generated/pyro-gui
install -d debian/.debhelper/generated/pyro-doc
install -d debian/.debhelper/generated/pyro-examples
debian/rules:27: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 25
make[1]: Leaving directory '/<>'
debian/rules:12: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


Hint: Try splitting override_dh_install into override_dh_install-indep and 
override_dh_install-arch.

Thanks.



Bug#901119: yodl: FTBFS when built with dpkg-buildpackage -A

2018-06-08 Thread Santiago Vila
Package: src:yodl
Version: 4.02.00-2
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_build-indep
make[1]: Entering directory '/<>'
./build manual
mkdir -p tmp/wip
mkdir -p tmp/install
mkdir -p tmp/install/usr/share/doc/yodl-doc
tmp/install/usr/bin/yodl -I.:tmp/wip:tmp/wip/macros:manual -otmp/wip/out html 
manual
sh: 1: tmp/install/usr/bin/yodl: not found
Fatal: system - failure of system call (status 32512)
debian/rules:39: recipe for target 'override_dh_auto_build-indep' failed
make[1]: *** [override_dh_auto_build-indep] Error 1
make[1]: Leaving directory '/<>'
debian/rules:25: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


To reproduce, please try "dpkg-buildpackage -A".
(The error does not happen with "dpkg-buildpackage").

Thanks.



Bug#901112: openvswitch: FTBFS when built with dpkg-buildpackage -A

2018-06-08 Thread Santiago Vila
Package: src:openvswitch
Version: 2.8.1+dfsg1-6
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
debian/rules:43: warning: overriding recipe for target 'override_dh_installinit'
/usr/share/openstack-pkg-tools/pkgos.make:43: warning: ignoring old recipe for 
target 'override_dh_installinit'
debian/rules:67: warning: overriding recipe for target 'override_dh_installinit'
debian/rules:43: warning: ignoring old recipe for target 
'override_dh_installinit'
dh build-indep --with autoreconf,python2,python3,systemd --parallel
   dh_update_autotools_config -i -O--parallel
   debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>/openvswitch-2.8.1+dfsg1'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions

[... snipped ...]

dh_missing: usr/share/man/man8/ovs-appctl.8 exists in debian/tmp but is not 
installed to anywhere
dh_missing: usr/share/man/man8/ovs-l3ping.8 exists in debian/tmp but is not 
installed to anywhere
dh_missing: usr/share/man/man8/ovn-controller-vtep.8 exists in debian/tmp but 
is not installed to anywhere
dh_missing: usr/share/man/man8/ovs-ofctl.8 exists in debian/tmp but is not 
installed to anywhere
dh_missing: usr/share/man/man8/ovn-controller.8 exists in debian/tmp but is not 
installed to anywhere
dh_missing: usr/share/man/man8/ovs-vswitchd.8 exists in debian/tmp but is not 
installed to anywhere
dh_missing: usr/share/man/man8/ovs-dpctl-top.8 exists in debian/tmp but is not 
installed to anywhere
dh_missing: usr/share/man/man8/ovn-northd.8 exists in debian/tmp but is not 
installed to anywhere
dh_missing: usr/share/man/man8/ovs-parse-backtrace.8 exists in debian/tmp but 
is not installed to anywhere
dh_missing: usr/share/man/man8/ovs-tcpdump.8 exists in debian/tmp but is not 
installed to anywhere
dh_missing: usr/share/man/man5/ovs-vswitchd.conf.db.5 exists in debian/tmp but 
is not installed to anywhere
dh_missing: usr/share/man/man5/vtep.5 exists in debian/tmp but is not installed 
to anywhere
dh_missing: usr/share/man/man5/ovn-nb.5 exists in debian/tmp but is not 
installed to anywhere
dh_missing: usr/share/man/man5/ovn-sb.5 exists in debian/tmp but is not 
installed to anywhere
dh_missing: usr/share/man/man1/ovs-pcap.1 exists in debian/tmp but is not 
installed to anywhere
dh_missing: usr/share/man/man1/ovsdb-server.1 exists in debian/tmp but is not 
installed to anywhere
dh_missing: usr/share/man/man1/ovsdb-tool.1 exists in debian/tmp but is not 
installed to anywhere
dh_missing: usr/share/man/man1/ovsdb-client.1 exists in debian/tmp but is not 
installed to anywhere
dh_missing: usr/share/man/man1/ovn-detrace.1 exists in debian/tmp but is not 
installed to anywhere
dh_missing: usr/share/man/man1/ovs-tcpundump.1 exists in debian/tmp but is not 
installed to anywhere
dh_missing: usr/share/man/man7/ovn-architecture.7 exists in debian/tmp but is 
not installed to anywhere
dh_missing: usr/share/man/man7/ovs-fields.7 exists in debian/tmp but is not 
installed to anywhere
dh_missing: usr/lib/x86_64-linux-gnu/libovn.la exists in debian/tmp but is not 
installed to anywhere
dh_missing: usr/lib/x86_64-linux-gnu/libopenvswitch.la exists in debian/tmp but 
is not installed to anywhere
dh_missing: usr/lib/x86_64-linux-gnu/libovsdb.la exists in debian/tmp but is 
not installed to anywhere
dh_missing: usr/lib/x86_64-linux-gnu/libofproto.la exists in debian/tmp but is 
not installed to anywhere
dh_missing: usr/lib/x86_64-linux-gnu/libsflow.la exists in debian/tmp but is 
not installed to anywhere
dh_missing: usr/lib/x86_64-linux-gnu/libvtep.la exists in debian/tmp but is not 
installed to anywhere
The following debhelper tools have reported what they installed (with 
files per package)
 * dh_install: openvswitch-common (64), openvswitch-dbg (0), 
openvswitch-dev (234), openvswitch-pki (0), openvswitch-switch (5), 
openvswitch-testcontroller (0), openvswitch-vtep (2), ovn-central (2), 
ovn-controller-vtep (0), ovn-host (0), python-openvswitch (2), 
python3-openvswitch (0)
If the missing files are installed by another tool, please file a bug 
against it.
When filing the report, if the tool is not part of debhelper itself, 
please reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
for debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
when only a subset is built
   

Bug#901111: libgpuarray: FTBFS when built with dpkg-buildpackage -A

2018-06-08 Thread Santiago Vila
Package: src:libgpuarray
Version: 0.6.9-2
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3,sphinxdoc --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure --buildsystem=cmake
cd obj-x86_64-linux-gnu && cmake .. -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -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 "-GUnix Makefiles"
-- The C compiler identification is GNU 7.3.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features

[... snipped ...]

I: pybuild base:217: python2.7 setup.py config 
Compiling pygpu/gpuarray.pyx because it changed.
Compiling pygpu/blas.pyx because it changed.
Compiling pygpu/_elemwise.pyx because it changed.
Compiling pygpu/collectives.pyx because it changed.
[1/4] Cythonizing pygpu/_elemwise.pyx
[2/4] Cythonizing pygpu/blas.pyx
[3/4] Cythonizing pygpu/collectives.pyx
[4/4] Cythonizing pygpu/gpuarray.pyx
running config
I: pybuild base:217: python2.7-dbg setup.py config 
running config
I: pybuild base:217: python3.6 setup.py config 
running config
I: pybuild base:217: python3.6-dbg setup.py config 
running config
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_build-indep
make[1]: Entering directory '/<>'
python3 setup.py build_ext --inplace -I /<>/src -L 
/<>/lib
running build_ext
building 'pygpu.gpuarray' extension
creating build
creating build/temp.linux-x86_64-3.6
creating build/temp.linux-x86_64-3.6/pygpu
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -DGPUARRAY_SHARED 
-I/usr/lib/python3/dist-packages/numpy/core/include -I/<>/src 
-I/usr/include/python3.6m -c pygpu/gpuarray.c -o 
build/temp.linux-x86_64-3.6/pygpu/gpuarray.o -Wno-unused-variable 
-Wno-unused-function
In file included from 
/usr/lib/python3/dist-packages/numpy/core/include/numpy/ndarraytypes.h:1816:0,
 from 
/usr/lib/python3/dist-packages/numpy/core/include/numpy/ndarrayobject.h:18,
 from 
/usr/lib/python3/dist-packages/numpy/core/include/numpy/arrayobject.h:4,
 from pygpu/gpuarray.c:514:
/usr/lib/python3/dist-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h:15:2:
 warning: #warning "Using deprecated NumPy API, disable it by " "#defining 
NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp]
 #warning "Using deprecated NumPy API, disable it by " \
  ^~~
creating build/lib.linux-x86_64-3.6
creating build/lib.linux-x86_64-3.6/pygpu
x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions 
-Wl,-z,relro -Wl,-z,relro -Wl,-z,now -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
build/temp.linux-x86_64-3.6/pygpu/gpuarray.o -L/<>/lib -lgpuarray 
-o build/lib.linux-x86_64-3.6/pygpu/gpuarray.cpython-36m-x86_64-linux-gnu.so
/usr/bin/ld: cannot find -lgpuarray
collect2: error: ld returned 1 exit status
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
debian/rules:39: recipe for target 'override_dh_auto_build-indep' failed
make[1]: *** [override_dh_auto_build-indep] Error 1
make[1]: Leaving directory '/<>'
debian/rules:15: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


To reproduce, please try "dpkg-buildpackage -A".
(The error does not happen with "dpkg-buildpackage").

Thanks.



Bug#901117: syslog-ng: FTBFS when built with dpkg-buildpackage -A

2018-06-08 Thread Santiago Vila
Package: src:syslog-ng
Version: 3.13.2-4
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
make: 'build-indep' is up to date.
 fakeroot debian/rules binary-indep
dh binary-indep --with autoreconf,systemd,python2 --parallel
   debian/rules build-indep
make[1]: Entering directory '/<>'
make[1]: 'build-indep' is up to date.
make[1]: Leaving directory '/<>'
   dh_testroot -i -O--parallel
   dh_prep -i -O--parallel
   dh_installdirs -i -O--parallel
   debian/rules override_dh_auto_install
make[1]: Entering directory '/<>'
dh_auto_install -- pkgconfigdir=/usr/lib/pkgconfig \
   PYSETUP_OPTIONS="--install-layout=deb 
--root=/<>/debian/tmp/"
find . -name \*.la | xargs --no-run-if-empty rm
make[1]: Leaving directory '/<>'
   dh_install -i -O--parallel
dh_install: Cannot find (any matches for) 
"usr/share/syslog-ng/include/scl/windowseventlog/plugin.conf" (tried in ., 
debian/tmp)

dh_install: syslog-ng-mod-extra missing files: 
usr/share/syslog-ng/include/scl/windowseventlog/plugin.conf
dh_install: Cannot find (any matches for) 
"usr/share/syslog-ng/include/scl/windowseventlog/windowseventlog.xml" (tried in 
., debian/tmp)

dh_install: syslog-ng-mod-extra missing files: 
usr/share/syslog-ng/include/scl/windowseventlog/windowseventlog.xml
dh_install: Cannot find (any matches for) 
"usr/share/syslog-ng/include/scl/loadbalancer/gen-loadbalancer.sh" (tried in ., 
debian/tmp)

dh_install: syslog-ng-mod-extra missing files: 
usr/share/syslog-ng/include/scl/loadbalancer/gen-loadbalancer.sh
dh_install: Cannot find (any matches for) 
"usr/share/syslog-ng/include/scl/loadbalancer/plugin.conf" (tried in ., 
debian/tmp)

dh_install: syslog-ng-mod-extra missing files: 
usr/share/syslog-ng/include/scl/loadbalancer/plugin.conf
dh_install: Cannot find (any matches for) 
"usr/share/syslog-ng/include/scl/default-network-drivers/plugin.conf" (tried in 
., debian/tmp)

dh_install: syslog-ng-mod-extra missing files: 
usr/share/syslog-ng/include/scl/default-network-drivers/plugin.conf
dh_install: Cannot find (any matches for) 
"usr/share/syslog-ng/include/scl/osquery/plugin.conf" (tried in ., debian/tmp)

dh_install: syslog-ng-mod-extra missing files: 
usr/share/syslog-ng/include/scl/osquery/plugin.conf
dh_install: Cannot find (any matches for) 
"usr/share/syslog-ng/include/scl/ewmm/ewmm.conf" (tried in ., debian/tmp)

dh_install: syslog-ng-mod-extra missing files: 
usr/share/syslog-ng/include/scl/ewmm/ewmm.conf
dh_install: Cannot find (any matches for) 
"usr/share/syslog-ng/include/scl/graylog2/plugin.conf" (tried in ., debian/tmp)

dh_install: syslog-ng-mod-extra missing files: 
usr/share/syslog-ng/include/scl/graylog2/plugin.conf
dh_install: missing files, aborting
debian/rules:207: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 25
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


To reproduce, please try "dpkg-buildpackage -A".
(The error does not happen with "dpkg-buildpackage").

Thanks.



Bug#901115: rxvt-unicode: FTBFS when built with dpkg-buildpackage -A

2018-06-08 Thread Santiago Vila
Package: src:rxvt-unicode
Version: 9.22-3
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- \
--host=x86_64-linux-gnu \
--build=x86_64-linux-gnu \
--mandir=\${prefix}/share/man \
--infodir=\${prefix}/share/info \
--enable-256-color \
--enable-combining \
--enable-fading \

[... snipped ...]

> mantmp
/usr/bin/install -c -m 644 mantmp 
/<>/debian/tmp/usr/share/man/man1/urxvt-extensions.1
< ./urxvt.pm \
perl -MPod::Man -e '(new Pod::Man name => "urxvtperl", section => 3, quotes => 
q<"> , center => q, release => q<9.22>)->parse_from_file' \
> mantmp
/usr/bin/install -c -m 644 mantmp 
/<>/debian/tmp/usr/share/man/man3/urxvtperl.3
make[3]: Leaving directory '/<>/src'
make[3]: Entering directory '/<>/doc'
sed -e 's%@@RXVT_VERSION@@%9.22%g;' -e 's%@@RXVT_NAME@@%urxvt%g;' -e 
's%@@RXVT_DATE@@%2016-01-23%g;' -e 
's%@@RXVT_LIBDIR@@%/usr/lib/x86_64-linux-gnu%g;' -e 's%@@URXVT_NAME@@%urxvt%g;' 
< ./rxvt.1.man.in  >rxvt.1.man
sed -e 's%@@RXVT_VERSION@@%9.22%g;' -e 's%@@RXVT_NAME@@%urxvt%g;' -e 
's%@@RXVT_DATE@@%2016-01-23%g;' -e 
's%@@RXVT_LIBDIR@@%/usr/lib/x86_64-linux-gnu%g;' -e 's%@@URXVT_NAME@@%urxvt%g;' 
< ./rxvtc.1.man.in >rxvtc.1.man
sed -e 's%@@RXVT_VERSION@@%9.22%g;' -e 's%@@RXVT_NAME@@%urxvt%g;' -e 
's%@@RXVT_DATE@@%2016-01-23%g;' -e 
's%@@RXVT_LIBDIR@@%/usr/lib/x86_64-linux-gnu%g;' -e 's%@@URXVT_NAME@@%urxvt%g;' 
< ./rxvtd.1.man.in >rxvtd.1.man
sed -e 's%@@RXVT_VERSION@@%9.22%g;' -e 's%@@RXVT_NAME@@%urxvt%g;' -e 
's%@@RXVT_DATE@@%2016-01-23%g;' -e 
's%@@RXVT_LIBDIR@@%/usr/lib/x86_64-linux-gnu%g;' -e 's%@@URXVT_NAME@@%urxvt%g;' 
< ./rxvt.7.man.in  >rxvt.7.man
/usr/bin/install -c -d /<>/debian/tmp/usr/share/man/man1
/usr/bin/install -c -d /<>/debian/tmp/usr/share/man/man7
/usr/bin/install -c -m 644 rxvt.1.man  
/<>/debian/tmp/usr/share/man/man1/urxvt.1
/usr/bin/install -c -m 644 rxvtc.1.man 
/<>/debian/tmp/usr/share/man/man1/urxvtc.1
/usr/bin/install -c -m 644 rxvtd.1.man 
/<>/debian/tmp/usr/share/man/man1/urxvtd.1
/usr/bin/install -c -m 644 rxvt.7.man  
/<>/debian/tmp/usr/share/man/man7/urxvt.7
make[3]: Leaving directory '/<>/doc'
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
   dh_install -i
   dh_installdocs -i
   debian/rules override_dh_installchangelogs
make[1]: Entering directory '/<>'
dh_installchangelogs Changes
make[1]: Leaving directory '/<>'
   dh_installman -i
   dh_lintian -i
   dh_perl -i
   dh_link -i
   dh_strip_nondeterminism -i
   dh_compress -i
   debian/rules override_dh_fixperms
make[1]: Entering directory '/<>'
dh_fixperms
chgrp utmp /<>/debian/rxvt-unicode/usr/bin/urxvt 
/<>/debian/rxvt-unicode/usr/bin/urxvtd
chgrp: cannot access '/<>/debian/rxvt-unicode/usr/bin/urxvt': No 
such file or directory
chgrp: cannot access '/<>/debian/rxvt-unicode/usr/bin/urxvtd': No 
such file or directory
debian/rules:67: recipe for target 'override_dh_fixperms' failed
make[1]: *** [override_dh_fixperms] Error 1
make[1]: Leaving directory '/<>'
debian/rules:15: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


Hint: Try splitting override_dh_fixperms into override_dh_fixperms-indep and 
override_dh_fixperms-arch.

Thanks.



Bug#901116: sane-backends-extras: FTBFS when built with dpkg-buildpackage -A

2018-06-08 Thread Santiago Vila
Package: src:sane-backends-extras
Version: 1.0.22.5
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
configure.ac:511: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in 
body
../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2672: _AC_LINK_IFELSE is expanded from...
../../lib/autoconf/general.m4:2689: AC_LINK_IFELSE is expanded from...
m4/libtool.m4:1084: _LT_SYS_MODULE_PATH_AIX is expanded from...
m4/libtool.m4:4211: _LT_LINKER_SHLIBS is expanded from...
m4/libtool.m4:5343: _LT_LANG_C_CONFIG is expanded from...
m4/libtool.m4:143: _LT_SETUP is expanded from...
m4/libtool.m4:69: LT_INIT is expanded from...
m4/libtool.m4:107: AC_PROG_LIBTOOL is expanded from...

[... snipped ...]

make[3]: Entering directory '/<>/backend'
 /bin/mkdir -p '/<>/debian/tmp/usr/lib/x86_64-linux-gnu/sane'
 /bin/bash ../libtool --silent   --mode=install /usr/bin/install -c   
libsane-geniusvp2.la libsane-ls5000.la 
'/<>/debian/tmp/usr/lib/x86_64-linux-gnu/sane'
libtool: warning: remember to run 'libtool --finish 
/usr/lib/x86_64-linux-gnu/sane'
make  install-data-hook
make[4]: Entering directory '/<>/backend'
rm -f /<>/debian/tmp/usr/lib/x86_64-linux-gnu/sane/libsane.*
test -z "/etc/sane.d" || /bin/mkdir -p "/<>/debian/tmp/etc/sane.d"
test -z "/etc/sane.d/dll.d" || /bin/mkdir -p 
"/<>/debian/tmp/etc/sane.d/dll.d"
installing geniusvp2.conf in /etc/sane.d/geniusvp2.conf...
for dir in  ; do \
  /bin/bash ../mkinstalldirs /<>/debian/tmp/usr/share/sane/${dir} 
; \
  done
make[4]: Leaving directory '/<>/backend'
make[3]: Leaving directory '/<>/backend'
make[2]: Leaving directory '/<>/backend'
Making install in doc
make[2]: Entering directory '/<>/doc'
make[3]: Entering directory '/<>/doc'
make[3]: Nothing to be done for 'install-exec-am'.
test -z "/usr/share/man/man5" || /bin/mkdir -p 
"/<>/debian/tmp/usr/share/man/man5"
installing sane-geniusvp2.5 in /usr/share/man/man5/sane-geniusvp2.5...
make[3]: Leaving directory '/<>/doc'
make[2]: Leaving directory '/<>/doc'
make[2]: Entering directory '/<>'
make[3]: Entering directory '/<>'
make[3]: Nothing to be done for 'install-exec-am'.
make[3]: Nothing to be done for 'install-data-am'.
make[3]: Leaving directory '/<>'
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
   debian/rules override_dh_install
make[1]: Entering directory '/<>'
dh_install
# remove wrong libsane.so.1 symlink
rm -f debian/libsane-extras/usr/lib/x86_64-linux-gnu/sane/libsane.so.1
# remove damn rpath
find debian/libsane-extras/usr/lib/x86_64-linux-gnu/sane -name "libsane-*.so.1" 
-exec chrpath -d {} \;
find: 'debian/libsane-extras/usr/lib/x86_64-linux-gnu/sane': No such file or 
directory
debian/rules:36: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 1
make[1]: Leaving directory '/<>'
debian/rules:16: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


Hint: Try splitting override_dh_install into override_dh_install-indep and 
override_dh_install-arch.

Thanks.



Bug#901105: ciftilib: FTBFS when built with dpkg-buildpackage -A

2018-06-08 Thread Santiago Vila
Package: src:ciftilib
Version: 1.5.1-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- -DBUILD_SHARED_LIBS=ON -DIGNORE_QT=ON
cd obj-x86_64-linux-gnu && cmake .. -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -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 "-GUnix Makefiles" 
-DBUILD_SHARED_LIBS=ON -DIGNORE_QT=ON
CMake Deprecation Warning at CMakeLists.txt:7 (CMAKE_POLICY):
  The OLD behavior for policy CMP0045 will be removed from a future version
  of CMake.

  The cmake-policies(7) manual explains that the OLD behaviors of all
  policies are deprecated and that a policy should be set to OLD only under

[... snipped ...]

CMake Error at /<>/cmake/scripts/testmd5.cmake:1 (FILE):
  FILE MD5 failed to read file "big-ones.dscalar.nii": No such file or
  directory




0% tests passed, 25 tests failed out of 25

Total Test time (real) =   0.17 sec

The following tests FAILED:
  1 - info-Conte69.MyelinAndCorrThickness.32k_fs_LR.dscalar.nii (Not 
Run)
  2 - 
rewrite-little-Conte69.MyelinAndCorrThickness.32k_fs_LR.dscalar.nii (Not Run)
  3 - 
rewrite-little-md5-Conte69.MyelinAndCorrThickness.32k_fs_LR.dscalar.nii (Failed)
  4 - rewrite-big-Conte69.MyelinAndCorrThickness.32k_fs_LR.dscalar.nii 
(Not Run)
  5 - 
rewrite-big-md5-Conte69.MyelinAndCorrThickness.32k_fs_LR.dscalar.nii (Failed)
  6 - info-Conte69.MyelinAndCorrThickness.32k_fs_LR.dtseries.nii (Not 
Run)
  7 - 
rewrite-little-Conte69.MyelinAndCorrThickness.32k_fs_LR.dtseries.nii (Not Run)
  8 - 
rewrite-little-md5-Conte69.MyelinAndCorrThickness.32k_fs_LR.dtseries.nii 
(Failed)
  9 - rewrite-big-Conte69.MyelinAndCorrThickness.32k_fs_LR.dtseries.nii 
(Not Run)
 10 - 
rewrite-big-md5-Conte69.MyelinAndCorrThickness.32k_fs_LR.dtseries.nii (Failed)
 11 - info-Conte69.MyelinAndCorrThickness.32k_fs_LR.ptseries.nii (Not 
Run)
 12 - 
rewrite-little-Conte69.MyelinAndCorrThickness.32k_fs_LR.ptseries.nii (Not Run)
 13 - 
rewrite-little-md5-Conte69.MyelinAndCorrThickness.32k_fs_LR.ptseries.nii 
(Failed)
 14 - rewrite-big-Conte69.MyelinAndCorrThickness.32k_fs_LR.ptseries.nii 
(Not Run)
 15 - 
rewrite-big-md5-Conte69.MyelinAndCorrThickness.32k_fs_LR.ptseries.nii (Failed)
 16 - info-Conte69.parcellations_VGD11b.32k_fs_LR.dlabel.nii (Not Run)
 17 - rewrite-little-Conte69.parcellations_VGD11b.32k_fs_LR.dlabel.nii 
(Not Run)
 18 - 
rewrite-little-md5-Conte69.parcellations_VGD11b.32k_fs_LR.dlabel.nii (Failed)
 19 - rewrite-big-Conte69.parcellations_VGD11b.32k_fs_LR.dlabel.nii 
(Not Run)
 20 - rewrite-big-md5-Conte69.parcellations_VGD11b.32k_fs_LR.dlabel.nii 
(Failed)
 21 - info-ones.dscalar.nii (Not Run)
 22 - rewrite-little-ones.dscalar.nii (Not Run)
 23 - rewrite-little-md5-ones.dscalar.nii (Failed)
 24 - rewrite-big-ones.dscalar.nii (Not Run)
 25 - rewrite-big-md5-ones.dscalar.nii (Failed)
Errors while running CTest
Makefile:110: recipe for target 'test' failed
make[1]: *** [test] Error 8
make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu'
dh_auto_test: cd obj-x86_64-linux-gnu && make -j1 test ARGS\+=-j1 returned exit 
code 2
debian/rules:11: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


To reproduce, please try "dpkg-buildpackage -A".
(The error does not happen with "dpkg-buildpackage").

Thanks.



Bug#901103: adios: FTBFS when built with dpkg-buildpackage -A

2018-06-08 Thread Santiago Vila
Package: src:adios
Version: 1.13.1-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3
   dh_update_autotools_config -i
   dh_autoreconf -i
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'config'.
libtoolize: copying file 'config/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'config'.
libtoolize: copying file 'config/libtool.m4'
libtoolize: copying file 'config/ltoptions.m4'
libtoolize: copying file 'config/ltsugar.m4'
libtoolize: copying file 'config/ltversion.m4'
libtoolize: copying file 'config/lt~obsolete.m4'
configure.ac:20: installing 'config/compile'
configure.ac:14: installing 'config/missing'

[... snipped ...]

cp -a /<>/debian/tmpp/lib/$p/site-packages/* 
debian/tmp/usr/lib/python3/dist-packages ; \
done
mv 
/<>/debian/tmp/usr/lib/python2.7/dist-packages/adios_mpi/adios_mpi.so
 \
   
debian/tmp/usr/lib/python2.7/dist-packages/adios_mpi/adios_mpi.x86_64-linux-gnu.so
mv /<>/debian/tmp/usr/lib/python2.7/dist-packages/adios/adios.so \
   
debian/tmp/usr/lib/python2.7/dist-packages/adios/adios.x86_64-linux-gnu.so
# remove due to it not working in multi-arch;
rm -f  /<>/debian/tmp/usr/bin/adios_config.flags
# renamed as per Adios CCS issue #118716, Debbug #639257
mv /<>/debian/tmp/usr/bin/gpp.py 
/<>/debian/tmp/usr/bin/adiosxml2h
mv /<>/debian/tmp/usr/bin/skel_cat.py 
/<>/debian/tmp/usr/bin/skel_cat
mv /<>/debian/tmp/usr/bin/skel_extract.py 
/<>/debian/tmp/usr/bin/skel_extract
cp debian/adios_config /<>/debian/tmp/usr/bin/adios_config
rm -rf 
debian/libadios-examples/usr/share/doc/libadios-examples/examples/C/attributes/.libs
make[1]: Leaving directory '/<>'
   dh_install -i
   dh_installdocs -i
   dh_installchangelogs -i
   debian/rules override_dh_installexamples
make[1]: Entering directory '/<>'
dh_installexamples
if test -d debian/libadios-examples/usr/share/doc/libadios-examples/examples ; 
then \
find debian/libadios-examples/usr/share/doc/libadios-examples/examples 
-name '*.o' -delete  ; \
find 
debian/libadios-examples/usr/share/doc/libadios-examples/examples/C -type f 
-exec chmod -x {} \; ; \
fi 
make[1]: Leaving directory '/<>'
   dh_python2 -i
E: dh_python2 dh_python2:408: no package to act on (python-foo or one with 
${python:Depends} in Depends)
   dh_python3 -i
E: dh_python3 dh_python3:176: no package to act on (python3-foo or one with 
${python3:Depends} in Depends)
   dh_perl -i
   dh_link -i
   dh_strip_nondeterminism -i
   dh_compress -i
   debian/rules override_dh_fixperms
make[1]: Entering directory '/<>'
dh_fixperms
chmod +x debian/libadios-bin/etc/adios/skel/templates/submit*.tpl
chmod: cannot access 
'debian/libadios-bin/etc/adios/skel/templates/submit*.tpl': No such file or 
directory
debian/rules:118: recipe for target 'override_dh_fixperms' failed
make[1]: *** [override_dh_fixperms] Error 1
make[1]: Leaving directory '/<>'
debian/rules:39: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


Hint: Try splitting override_dh_fixperms into override_dh_fixperms-indep and 
override_dh_fixperms-arch.

Thanks.



Bug#901114: python-coverage: FTBFS when built with dpkg-buildpackage -A

2018-06-08 Thread Santiago Vila
Package: src:python-coverage
Version: 4.5+dfsg.1-3
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
dpkg-buildpackage: info: source package python-coverage
dpkg-buildpackage: info: source version 4.5+dfsg.1-3
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Ben Finney 
 dpkg-source --before-build python-coverage-4.5+dfsg.1
 fakeroot debian/rules clean
debian/rules:166: warning: overriding recipe for target 'override_dh_auto_build'
debian/rules:129: warning: ignoring old recipe for target 
'override_dh_auto_build'
dh clean --with python3,python2,pypy,sphinxdoc --buildsystem=pybuild
dh: unable to load addon python2: Can't locate 
Debian/Debhelper/Sequence/python2.pm in @INC (you may need to install the 
Debian::Debhelper::Sequence::python2 module) (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.26.2 /usr/local/share/perl/5.26.2 
/usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 10) line 
1.
BEGIN failed--compilation aborted at (eval 10) line 1.

debian/rules:74: recipe for target 'clean' failed
make: *** [clean] Error 2
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit 
status 2


To reproduce, please try "dpkg-buildpackage -A".
(The error does not happen with "dpkg-buildpackage").

Thanks.



Bug#901104: chezscheme: FTBFS when built with dpkg-buildpackage -A

2018-06-08 Thread Santiago Vila
Package: src:chezscheme
Version: 9.5+dfsg-2
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/chezscheme-9.5+dfsg'
CC=x86_64-linux-gnu-gcc ./configure --workarea=build -m=ta6le --threads 
--installprefix=/usr --temproot=/<>/chezscheme-9.5+dfsg/debian/tmp
cp -a release_notes/ build/
cp -a csug/ build/
(echo "\def\INSERTREVISIONMONTHSPACEYEAR{}"; cat csug/copyright.stex) > \
build/csug/copyright.stex
make[1]: Leaving directory '/<>/chezscheme-9.5+dfsg'
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>/chezscheme-9.5+dfsg'
make -C build
make[2]: Entering directory '/<>/chezscheme-9.5+dfsg/build'
(cd c ; make)
ln -s ../../c/statics.c statics.c
ln -s ../../c/system.h system.h
ln -s ../../c/types.h types.h
ln -s ../../c/version.h version.h
ln -s ../../c/externs.h externs.h
ln -s ../../c/globals.h globals.h
ln -s ../../c/segment.h segment.h
ln -s ../../c/thread.h thread.h
ln -s ../../c/sort.h sort.h
x86_64-linux-gnu-gcc -Wdate-time -D_FORTIFY_SOURCE=2 -m64 -msse2 
-Wpointer-arith -Wall -Wextra -Werror -Wno-implicit-fallthrough -O2 
-D_REENTRANT -pthread -g -O2 
-fdebug-prefix-map=/<>/chezscheme-9.5+dfsg=. -fstack-protector-strong 
-Wformat -Werror=format-security -c -DX86_64 -I../boot/ta6le statics.c
In file included from statics.c:18:0:
system.h:25:10: fatal error: zlib.h: No such file or directory
 #include "zlib.h"
  ^~~~
compilation terminated.
Makefile:29: recipe for target 'statics.o' failed
make[3]: *** [statics.o] Error 1
Makefile:20: recipe for target 'build' failed
make[2]: *** [build] Error 2
make[2]: Leaving directory '/<>/chezscheme-9.5+dfsg/build'
debian/rules:61: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>/chezscheme-9.5+dfsg'
debian/rules:38: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


To reproduce, please try "dpkg-buildpackage -A".

The error does not happen with "dpkg-buildpackage".

Thanks.



Bug#901109: icmake: FTBFS when built with dpkg-buildpackage -A

2018-06-08 Thread Santiago Vila
Package: src:icmake
Version: 9.02.07-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_build-indep
make[1]: Entering directory '/<>'
./icm_install docdoc  debian/icmake-doc

Usage: ./icm_install [strip] all|progs|scripts|man|skel|doc|etc|docdoc 
[installdir]

debian/rules:37: recipe for target 'override_dh_auto_build-indep' failed
make[1]: *** [override_dh_auto_build-indep] Error 1
make[1]: Leaving directory '/<>'
debian/rules:14: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


To reproduce, please try "dpkg-buildpackage -A".
(The error does not happen with "dpkg-buildpackage").

Thanks.



Bug#901108: grr: FTBFS when built with dpkg-buildpackage -A

2018-06-08 Thread Santiago Vila
Package: src:grr
Version: 3.1.0.2+dfsg-5
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep  --with python2,systemd --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/grr-3.1.0.2+dfsg'
dh_auto_configure
pybuild --configure -i python{version} -p 2.7
I: pybuild base:217: python2.7 setup.py config 
/usr/lib/python2.7/dist-packages/setuptools/dist.py:388: UserWarning: 
Normalizing '3.1.0post2' to '3.1.0.post2'
  normalized_version,
*
  WARNING: You are not installing in a virtual
  environment. This configuration is not supported!!!
  Expect breakage.

[... snipped ...]

  debian/man/grr_run_tests.1.txt > debian/man/grr_run_tests.1
TZ=UTC LC_ALL=C \
  txt2man -d "28 April 2018" \
  -s 1 -r "GRR 3.1.0.2" -t grr_fuse \
  debian/man/grr_fuse.1.txt > debian/man/grr_fuse.1
TZ=UTC LC_ALL=C \
  txt2man -d "28 April 2018" \
  -s 1 -r "GRR 3.1.0.2" -t grr_run_tests_gui \
  debian/man/grr_run_tests_gui.1.txt > debian/man/grr_run_tests_gui.1
TZ=UTC LC_ALL=C \
  txt2man -d "28 April 2018" \
  -s 1 -r "GRR 3.1.0.2" -t grr_dataserver \
  debian/man/grr_dataserver.1.txt > debian/man/grr_dataserver.1
TZ=UTC LC_ALL=C \
  txt2man -d "28 April 2018" \
  -s 1 -r "GRR 3.1.0.2" -t grr_front_end \
  debian/man/grr_front_end.1.txt > debian/man/grr_front_end.1
dh_installman
install -d debian/grr-client-templates-installer/usr/share/man/man8/
install -p -m0644 ./debian/man/update-grr-client-templates.8 
debian/grr-client-templates-installer/usr/share/man/man8/update-grr-client-templates.8
man -l --recode UTF-8 
./debian/grr-client-templates-installer/usr/share/man/man8/update-grr-client-templates.8
 > 
debian/grr-client-templates-installer/usr/share/man/man8/update-grr-client-templates.8.dh-new
mv 
debian/grr-client-templates-installer/usr/share/man/man8/update-grr-client-templates.8.dh-new
 
debian/grr-client-templates-installer/usr/share/man/man8/update-grr-client-templates.8
chmod 0644 -- 
debian/grr-client-templates-installer/usr/share/man/man8/update-grr-client-templates.8
make[1]: Leaving directory '/<>/grr-3.1.0.2+dfsg'
   debian/rules override_dh_python2
make[1]: Entering directory '/<>/grr-3.1.0.2+dfsg'
dh_python2 --skip-private
make[1]: Leaving directory '/<>/grr-3.1.0.2+dfsg'
   debian/rules override_dh_installinit
make[1]: Entering directory '/<>/grr-3.1.0.2+dfsg'
dh_installinit --name=grr-server
dh_installinit --name=grr-server@
make[1]: Leaving directory '/<>/grr-3.1.0.2+dfsg'
   dh_perl -i -O--buildsystem=pybuild
   debian/rules override_dh_link
make[1]: Entering directory '/<>/grr-3.1.0.2+dfsg'
cp  /usr/share/artifacts/*.yaml \
debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts
cp: target 'debian/grr-server/usr/lib/python2.7/dist-packages/grr/artifacts' is 
not a directory
debian/rules:57: recipe for target 'override_dh_link' failed
make[1]: *** [override_dh_link] Error 1
make[1]: Leaving directory '/<>/grr-3.1.0.2+dfsg'
debian/rules:12: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


Hint: Try splitting override_dh_link into override_dh_link-indep and 
override_dh_link-arch.

Thanks.



Bug#901110: libgdamm5.0: FTBFS when built with dpkg-buildpackage -A

2018-06-08 Thread Santiago Vila
Package: src:libgdamm5.0
Version: 4.99.11-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with gnome
   dh_update_autotools_config -i
   dh_autoreconf -i
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build'.
libtoolize: copying file 'build/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'build'.
libtoolize: copying file 'build/libtool.m4'
libtoolize: copying file 'build/ltoptions.m4'
libtoolize: copying file 'build/ltsugar.m4'
libtoolize: copying file 'build/ltversion.m4'
libtoolize: copying file 'build/lt~obsolete.m4'
configure.ac:47: installing 'build/compile'
configure.ac:38: installing 'build/missing'

[... snipped ...]

/usr/bin/make -C examples clean
make[2]: Entering directory '/<>/examples'
 rm -f config/example simple/example sqlbuilder/example
rm -rf .libs _libs
rm -rf config/.libs config/_libs
rm -rf simple/.libs simple/_libs
rm -rf sqlbuilder/.libs sqlbuilder/_libs
rm -f *.o
rm -f config/*.o
rm -f simple/*.o
rm -f sqlbuilder/*.o
rm -f *.lo
make[2]: Leaving directory '/<>/examples'
dh_installexamples -X.deps -X.dirstamp -XMakefile
make[1]: Leaving directory '/<>'
   dh_gnome -i
   dh_perl -i
   dh_link -i
   dh_strip_nondeterminism -i
   debian/rules override_dh_compress
make[1]: Entering directory '/<>'
dh_compress -X reference -X examples
make[1]: Leaving directory '/<>'
   dh_fixperms -i
   debian/rules override_dh_missing
make[1]: Entering directory '/<>'
dh_missing --fail-missing
dh_missing: usr/lib/x86_64-linux-gnu/libgdamm-5.0.la exists in debian/tmp but 
is not installed to anywhere
dh_missing: missing files, aborting
The following debhelper tools have reported what they installed (with 
files per package)
 * dh_install: libgdamm-5.0-13 (2), libgdamm5.0-dev (4), 
libgdamm5.0-doc (2)
 * dh_installdocs: libgdamm-5.0-13 (1), libgdamm5.0-dev (0), 
libgdamm5.0-doc (0)
 * dh_installexamples: libgdamm-5.0-13 (0), libgdamm5.0-dev (0), 
libgdamm5.0-doc (7)
If the missing files are installed by another tool, please file a bug 
against it.
When filing the report, if the tool is not part of debhelper itself, 
please reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
for debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
when only a subset is built
For a short-term work-around: Add the files to debian/not-installed
debian/rules:30: recipe for target 'override_dh_missing' failed
make[1]: *** [override_dh_missing] Error 255
make[1]: Leaving directory '/<>'
debian/rules:13: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


To reproduce, please try "dpkg-buildpackage -A".
(The error does not happen with "dpkg-buildpackage").

Thanks.



Bug#901107: grib-api: FTBFS when built with dpkg-buildpackage -A

2018-06-08 Thread Santiago Vila
Package: src:grib-api
Version: 1.26.1-2
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=cmake --with=python2,python3,fortran_mod 
--no-parallel
   dh_update_autotools_config -i -O--buildsystem=cmake
install -d debian/.debhelper/bucket/files
cp -an --reflink=auto config/config.guess 
debian/.debhelper/bucket/files/4676029966e14b0a9bfc430963a97196ea50451e4aa3ff23c41256b0046f6efe.tmp
mv 
debian/.debhelper/bucket/files/4676029966e14b0a9bfc430963a97196ea50451e4aa3ff23c41256b0046f6efe.tmp
 
debian/.debhelper/bucket/files/4676029966e14b0a9bfc430963a97196ea50451e4aa3ff23c41256b0046f6efe
cp -f /usr/share/misc/config.guess ./config/config.guess
cp -an --reflink=auto config/config.sub 
debian/.debhelper/bucket/files/4add30a10b137a5a4667e12868fb4783e385dbf865cfb7017b205321bd1a2f39.tmp
mv 
debian/.debhelper/bucket/files/4add30a10b137a5a4667e12868fb4783e385dbf865cfb7017b205321bd1a2f39.tmp
 
debian/.debhelper/bucket/files/4add30a10b137a5a4667e12868fb4783e385dbf865cfb7017b205321bd1a2f39
cp -f /usr/share/misc/config.sub ./config/config.sub
   dh_autoreconf -i -O--buildsystem=cmake
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*' 
-o -path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a  -type f -exec 
md5sum {} + -o -type l -printf "symlink  %p
" > debian/autoreconf.before
grep -q ^XDT_ configure.ac

[... snipped ...]

done
`debian/tmp/usr/bin/grib1to2' probably isn't an ELF file.
elf_open: Exec format error
Ignoring chrpath error for non-ELF 
dh_numpy
(grep -a -s -v python:Depends debian/libgrib-api-doc.substvars; echo 
python:Depends=python-numpy) > debian/libgrib-api-doc.substvars.new
mv debian/libgrib-api-doc.substvars.new debian/libgrib-api-doc.substvars
dh_numpy3
(grep -a -s -v python3:Depends debian/libgrib-api-doc.substvars; echo 
python3:Depends=python3-numpy) > debian/libgrib-api-doc.substvars.new
mv debian/libgrib-api-doc.substvars.new debian/libgrib-api-doc.substvars
dh_install
install -d debian/.debhelper/generated/libgrib-api0
install -d debian/.debhelper/generated/libgrib-api-dev
install -d debian/.debhelper/generated/libgrib-api-tools
install -d debian/.debhelper/generated/libgrib-api-doc
install -d debian/.debhelper/generated/python-gribapi
install -d debian/.debhelper/generated/python3-gribapi
#
# Setup cmake files for magics++, metview, etc.
#
mkdir -p debian/libgrib-api-dev//usr/lib/x86_64-linux-gnu/cmake/grib_api
cp debian/tmp/usr/share/grib_api/cmake/* 
debian/libgrib-api-dev//usr/lib/x86_64-linux-gnu/cmake/grib_api
cat debian/tmp/usr/share/grib_api//cmake/grib_api-targets-release.cmake | \
sed -e 's% *IMPORTED_LINK_INTERFACE_LIBRARIES_RELEASE.*%  
IMPORTED_LINK_INTERFACE_LIBRARIES_RELEASE ""%' \
-e 's%${_IMPORT_PREFIX}%/usr%g' \
> 
debian/libgrib-api-dev//usr/lib/x86_64-linux-gnu/cmake/grib_api/grib_api-targets-release.cmake
cat debian/tmp/usr/share/grib_api//cmake/grib_api-config.cmake | \
sed -e 's%^set( grib_api_BASE_DIR.*%set ( grib_api_BASE_DIR /build/grib-api )%' 
| \
sed -e 's%^set( GRIB_API_TPLS.*%set( GRIB_API_TPLS "")%' | \
sed -e 's%^set( GRIB_API_TPL_LIBRARIES.*%set( GRIB_API_TPL_LIBRARIES "" )%' \
> 
debian/libgrib-api-dev//usr/lib/x86_64-linux-gnu/cmake/grib_api/grib_api-config.cmake
# For bit-reproducibility, sanitize the build paths
for f in grib_api-import.cmake grib_api-config.cmake ; do \
sed -e 's%/<>%/build/grib_api%g' < 
debian/libgrib-api-dev//usr/lib/x86_64-linux-gnu/cmake/grib_api/$f \
> debian/libgrib-api-dev//usr/lib/x86_64-linux-gnu/cmake/grib_api/x; \
mv debian/libgrib-api-dev//usr/lib/x86_64-linux-gnu/cmake/grib_api/x  
debian/libgrib-api-dev//usr/lib/x86_64-linux-gnu/cmake/grib_api/$f ; \
done
sed -e 's%/<>%/build/grib_api%g' < 
debian/libgrib-api-dev/usr/include/grib_api_ecbuild_config.h > x
/bin/sh: 1: cannot open 
debian/libgrib-api-dev/usr/include/grib_api_ecbuild_config.h: No such file
debian/rules:86: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 2
make[1]: Leaving directory '/<>'
debian/rules:47: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


To reproduce, please try "dpkg-buildpackage -A".
(The error does not happen with "dpkg-buildpackage").

Thanks.



Bug#901106: eccodes: FTBFS when built with dpkg-buildpackage -A

2018-06-08 Thread Santiago Vila
Package: src:eccodes
Version: 2.7.3-2
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=cmake --with=python3,fortran_mod 
--builddirectory=/<>/debian/build --no-parallel
   dh_update_autotools_config -i -O--buildsystem=cmake 
-O--builddirectory=/<>/debian/build
   dh_autoreconf -i -O--buildsystem=cmake 
-O--builddirectory=/<>/debian/build
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
F77=gfortran-8 dh_auto_configure -- \
-DCMAKE_BUILD_TYPE=Release -DDISABLE_OS_CHECK=ON 
-DENABLE_INSTALL_ECCODES_DEFINITIONS=ON -DENABLE_INSTALL_ECCODES_SAMPLES=ON 
-DENABLE_PNG=ON -DENABLE_AEC=ON -DENABLE_RPATHS=OFF 
-DENABLE_RELATIVE_RPATHS=OFF -DENABLE_MEMFS=ON -DHAVE_BIT_REPRODUCIBLE=ON 
-DCMAKE_C_CFLAGS="-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -Wl,-z,relro" -DENABLE_ALIGN_MEMORY=ON 
-DENABLE_GRIB_TIMER=ON -DENABLE_ECCODES_OMP_THREADS=On -DENABLE_PYTHON=ON 
-DPYTHON_EXECUTABLE=/usr/bin/python3 
install -d debian/build
cd debian/build && cmake ../.. -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -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 "-GUnix Makefiles" 
-DCMAKE_BUILD_TYPE=Release -DDISABLE_OS_CHECK=ON 
-DENABLE_INSTALL_ECCODES_DEFINITIONS=ON -DENABLE_INSTALL_ECCODES_SAMPLES=ON 
-DENABLE_PNG=ON -DENABLE_AEC=ON -DENABLE_RPATHS=OFF 
-DENABLE_RELATIVE_RPATHS=OFF -DENABLE_MEMFS=ON -DHAVE_BIT_REPRODUCIBLE=ON 
"-DCMAKE_C_CFLAGS=-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -Wl,-z,relro" -DENABLE_ALIGN_MEMORY=ON 
-DENABLE_GRIB_TIMER=ON -DENABLE_ECCODES_OMP_THREADS=On -DENABLE_PYTHON=ON 
-DPYTHON_EXECUTABLE=/usr/bin/python3
-- The C compiler identification is GNU 7.3.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info

[... snipped ...]

(grep -a -s -v python3:Depends debian/libeccodes-data.substvars; echo 
python3:Depends=python3-numpy) > debian/libeccodes-data.substvars.new
mv debian/libeccodes-data.substvars.new debian/libeccodes-data.substvars
(grep -a -s -v python3:Depends debian/libeccodes-doc.substvars; echo 
python3:Depends=python3-numpy) > debian/libeccodes-doc.substvars.new
mv debian/libeccodes-doc.substvars.new debian/libeccodes-doc.substvars
dh_install
install -d debian/.debhelper/generated/libeccodes0
install -d debian/libeccodes-data//usr/share/eccodes
cp --reflink=auto -a debian/tmp/usr/share/eccodes/definitions 
debian/tmp/usr/share/eccodes/samples debian/libeccodes-data//usr/share/eccodes/
install -d debian/.debhelper/generated/libeccodes-data
install -d debian/.debhelper/generated/libeccodes-dev
install -d debian/.debhelper/generated/libeccodes-tools
install -d debian/.debhelper/generated/python3-eccodes
install -d debian/.debhelper/generated/libeccodes-doc
#
# Setup cmake files for magics++, metview, etc.
#
mkdir -p debian/libeccodes-dev//usr/lib/x86_64-linux-gnu/cmake/eccodes
cp debian/tmp/usr/share/eccodes/cmake/* 
debian/libeccodes-dev//usr/lib/x86_64-linux-gnu/cmake/eccodes
sed -e 's%${_IMPORT_PREFIX}%/usr%' \
   < debian/tmp/usr/share/eccodes/cmake/eccodes-targets-release.cmake | \
sed -e 's%-lpython3.6 %%g' | \
sed -e 's%/usr/lib/libeccodes%/usr/lib/x86_64-linux-gnu/libeccodes%' | \
sed -e 's%/usr/lib/x86_64-linux-gnu/libopenjpeg.so;%%' | sed -e 
's%;/usr/lib/x86_64-linux-gnu/libpng.so%%g' \
  > 
debian/libeccodes-dev//usr/lib/x86_64-linux-gnu/cmake/eccodes/eccodes-targets-release.cmake
sed -e 's%;/usr/lib/x86_64-linux-gnu/libopenjpeg.so%%g' \
< debian/tmp/usr/share/eccodes/cmake/eccodes-config.cmake | \
sed -e 's%-lpython3.6 %%g' | \
sed -s 's%/usr/include/python3.6;%%g' | sed -e 's%/usr/include/python2.7;%%g' | 
\
sed -e 's%;/usr/lib/x86_64-linux-gnu/libpng.so%%g' \
> 
debian/libeccodes-dev//usr/lib/x86_64-linux-gnu/cmake/eccodes/grib_api-config.cmake
# For bit-reproducibility, sanitize the build paths
for f in eccodes-config.cmake eccodes-import.cmake grib_api-config.cmake ; do \
sed -e 's%/<>%/build/eccodes%g' < 
debian/libeccodes-dev//usr/lib/x86_64-linux-gnu/cmake/eccodes/$f \
> debian/libeccodes-dev//usr/lib/x86_64-linux-gnu/cmake/eccodes/x; \
mv debian/libeccodes-dev//usr/lib/x86_64-linux-gnu/cmake/eccodes/x  
debian/libeccodes-dev//usr/lib/x86_64-linux-gnu/cmake/eccodes/$f ; \
done
sed -e 's%/<>%/build/eccodes%g' < 
debian/libeccodes-dev//usr/include/x86_64-linux-gnu/eccodes_ecbuild_config.h \
> 

Bug#901102: firehol-doc,firehol-tools-doc,fireqos-doc: fails to install, trying to overwrite other packages files

2018-06-08 Thread Andreas Beckmann
Package: firehol-doc,firehol-tools-doc,fireqos-doc
Version: 3.1.5+ds-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package fireqos-doc.
  Preparing to unpack .../fireqos-doc_3.1.5+ds-2_all.deb ...
  Unpacking fireqos-doc (3.1.5+ds-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/fireqos-doc_3.1.5+ds-2_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/fireqos/README', which is also in 
package fireqos 3.1.5+ds-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/fireqos-doc_3.1.5+ds-2_all.deb

  Selecting previously unselected package firehol-doc.
  Preparing to unpack .../firehol-doc_3.1.5+ds-2_all.deb ...
  Unpacking firehol-doc (3.1.5+ds-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/firehol-doc_3.1.5+ds-2_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/firehol/README', which is also in 
package firehol 3.1.5+ds-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/firehol-doc_3.1.5+ds-2_all.deb

  Selecting previously unselected package firehol-tools-doc.
  Preparing to unpack .../firehol-tools-doc_3.1.5+ds-2_all.deb ...
  Unpacking firehol-tools-doc (3.1.5+ds-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/firehol-tools-doc_3.1.5+ds-2_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/firehol-tools/README', which is also in 
package firehol-tools 3.1.5+ds-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/firehol-tools-doc_3.1.5+ds-2_all.deb


This is most likely caused by a behavioral change in dh_installdocs
in debhelper compat level 11.


cheers,

Andreas


fireqos=3.1.5+ds-2_fireqos-doc=3.1.5+ds-2.log.gz
Description: application/gzip


Bug#766167: GNS3 ppa

2018-06-08 Thread Eldon Koyle
For future reference, there is an Ubuntu PPA for GNS3 [1], and it looks
like their development team [2] is fairly active.

[1] https://launchpad.net/~gns3/+archive/ubuntu/ppa
[2] https://launchpad.net/~gns3

-- 
Eldon Koyle


Bug#901101: SIGSEGV in gatttool

2018-06-08 Thread Vitamin Vitamin
Package: bluez
Version: 5.43-2+deb9u1

Several crashes while working with gatttool in stretch kernel 4.9.0-6-amd64
#1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07) x86_64 GNU/Linux
libglib2 version 2.50.3-2


Here's some output from gdb session (using bliez-dbg)

Starting program: /usr/bin/gatttool -b 4C:65:A8:D5:40:CA -I
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[4C:65:A8:D5:40:CA][LE]> connect
Attempting to connect to 4C:65:A8:D5:40:CA
Error: connect error: Transport endpoint is not connected (107)
[4C:65:A8:D5:40:CA][LE]> char-read-hnd 0x18
Command Failed: Disconnected
[4C:65:A8:D5:40:CA][LE]> connect
Attempting to connect to 4C:65:A8:D5:40:CA
Connection successful
[4C:65:A8:D5:40:CA][LE]> char-read-hnd 0x18
Error: Characteristic value/descriptor read failed: Request attribute has
encountered an unlikely error
[4C:65:A8:D5:40:CA][LE]>
(gatttool:6617): GLib-WARNING **: Invalid file descriptor.


Program received signal SIGSEGV, Segmentation fault.
malloc_consolidate (av=av@entry=0x77453b00 ) at
malloc.c:4205
4205malloc.c: No such file or directory.
(gdb) bt
#0  malloc_consolidate (av=av@entry=0x77453b00 ) at
malloc.c:4205
#1  0x77131ed8 in _int_free (av=0x77453b00 ,
p=0x557bddb0, have_lock=0) at malloc.c:4113
#2  0x779157d2 in g_log_writer_standard_streams () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x779158b7 in g_log_writer_default () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x77913dfc in g_log_structured_array () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x779142b7 in g_log_default_handler () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x779145c4 in g_logv () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x779147cf in g_log () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x778ff7e2 in g_io_channel_error_from_errno () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7795375f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x778fffc2 in g_io_channel_shutdown () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x77900167 in g_io_channel_unref () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x7790a7c6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x7790d820 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x7790da60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x7790dd82 in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x55564898 in interactive (src=0x0, dst=,
dst_type=, psm=) at attrib/interactive.c:1017
#17 0xa942 in main (argc=, argv=)
at attrib/gatttool.c:568


and

Starting program: /usr/bin/gatttool -b 4C:65:A8:D5:40:CA -I
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[4C:65:A8:D5:40:CA][LE]> connect
Attempting to connect to 4C:65:A8:D5:40:CA
Connection successful
[4C:65:A8:D5:40:CA][LE]> connect
(gatttool:6800): GLib-WARNING **: Invalid file descriptor.

[4C:65:A8:D5:40:CA][LE]> connect
Attempting to connect to 4C:65:A8:D5:40:CA
Error: connect error: Transport endpoint is not connected (107)
[4C:65:A8:D5:40:CA][LE]> char-read-hnd 0x18
Command Failed: Disconnected
[4C:65:A8:D5:40:CA][LE]> connect
Attempting to connect to 4C:65:A8:D5:40:CA
Error: connect error: Transport endpoint is not connected (107)
[4C:65:A8:D5:40:CA][LE]> char-read-hnd 0x18
Command Failed: Disconnected
[4C:65:A8:D5:40:CA][LE]> connect
Attempting to connect to 4C:65:A8:D5:40:CA
Connection successful
[4C:65:A8:D5:40:CA][LE]> char-read-hnd 0x18
Error: Characteristic value/descriptor read failed: Request attribute has
encountered an unlikely error
[4C:65:A8:D5:40:CA][LE]>
(gatttool:6800): GLib-WARNING **: Invalid file descriptor.

char-read-hnd 0x18

Program received signal SIGSEGV, Segmentation fault.
_int_malloc (av=av@entry=0x77453b00 , bytes=bytes@entry=14)
at malloc.c:3416
3416malloc.c: No such file or directory.
(gdb) bt
#0  _int_malloc (av=av@entry=0x77453b00 , bytes=bytes@entry=14)
at malloc.c:3416
#1  0x77134f64 in __GI___libc_malloc (bytes=14) at malloc.c:2928
#2  0x77912e09 in g_malloc () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7792ceaf in g_strdup () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x77929906 in g_shell_unquote () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7792a0a4 in g_shell_parse_argv () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x555636cc in parse_line (line_read=0x557bdf60 "") at
attrib/interactive.c:842
#7  0x776a5ac3 in rl_callback_read_char () from
/lib/x86_64-linux-gnu/libreadline.so.7
#8  0x5556386e in prompt_read (chan=,
cond=, user_data=) at attrib/interactive.c:868
#9  0x7790d6aa in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 

Bug#901100: cluster-glue-dev: missing Breaks+Replaces: cluster-glue (<< 1.0.12-8)

2018-06-08 Thread Andreas Beckmann
Package: cluster-glue-dev
Version: 1.0.12-9
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then the upgrade to 'buster' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package cluster-glue-dev.
  Preparing to unpack .../11-cluster-glue-dev_1.0.12-9_amd64.deb ...
  Unpacking cluster-glue-dev (1.0.12-9) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-iCxNhp/11-cluster-glue-dev_1.0.12-9_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/heartbeat/plugins/compress/bz2.a', which is 
also in package cluster-glue 1.0.12-5
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-iCxNhp/11-cluster-glue-dev_1.0.12-9_amd64.deb


According to the changelog, these files were moved in -8.


cheers,

Andreas


cluster-glue=1.0.12-5_cluster-glue-dev=1.0.12-9.log.gz
Description: application/gzip


Bug#901099: libatlas-doc: fails to upgrade from 'stretch' - trying to overwrite /usr/share/doc/libatlas-base-dev/README

2018-06-08 Thread Andreas Beckmann
Package: libatlas-doc
Version: 3.10.3-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then the upgrade to 'buster' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package libatlas-doc.
  Preparing to unpack .../libatlas-doc_3.10.3-6_all.deb ...
  Unpacking libatlas-doc (3.10.3-6) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libatlas-doc_3.10.3-6_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/libatlas-base-dev/README', which is also 
in package libatlas-base-dev 3.10.3-1+b1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libatlas-doc_3.10.3-6_all.deb


This is most likely caused by a behavioral change in dh_installdocs
in debhelper compat level 11.


cheers,

Andreas


libatlas-base-dev=3.10.3-1+b1_libatlas-doc=3.10.3-6.log.gz
Description: application/gzip


Bug#901086: preliminary packaging

2018-06-08 Thread Jeffrey Cliff
Built a package that at least builds successfully on linux/amd64.  It was a
little finicky to get right because of node-gyp being involved..but it does
seem to work:

https://notabug.org/themusicgod1/node-fibers

hopefully this helps
Jeff Cliff


Bug#736126: Please install haveged on physical machines

2018-06-08 Thread Nicolas Braud-Santoni
On Fri, Jun 08, 2018 at 07:37:09PM +, Holger Levsen wrote:
> Hi nicoo,
> 
> On Fri, Jun 08, 2018 at 09:27:10PM +0200, Nicolas Braud-Santoni wrote:
> > On virtual machines, however, the data that the HAVEGE algorithm produces
> > is not necessarily unpredictable [1]; hence, we shouldn't install haveged
> > on those environments.
>  
> interesting, thanks! sadly it doesnt say which virtualisation environments
> were/are affected.

IIRC, back then VMware ESXi was the only platform virtualizing the rdtsc
instruction, but 1) I do not have access to it to test (nor do I want to)
2) other virtualization platforms, now or in the future, might do this too.



Bug#901073: python-biom-format autopkg test failure

2018-06-08 Thread Andreas Tille
Control: forwarded -1 https://github.com/biocore/biom-format/issues/777
Control: tags -1 upstream
Control: tags -1 help

Hi,

I have reported the issue upstream.  I have the vague suspicion that the
migration to numpy 1.4.x might have caused the problem since it is
connected in time to the failure of this test.  There is a bit more
detailed information than the autopkg log provides:


$ python2.7 -m nose tests
...
unzip(items) should be the inverse of zip(*items) ... ok

==
FAIL: TableSummarizer functions as expected
--
Traceback (most recent call last):
  File "/tmp/tmp.ovLIvfIx3j/tests/test_cli/test_summarize_table.py", line 
33, in test_default
self.assertEqual(sorted(result), sorted(summary_default))
AssertionError: Lists differ: [u'\n', u'\n', u'\n', u'\n', u... != ['\n', 
'\n', '\n', '\n', '\n',...

First differing element 68:
u','
'-'

Diff is 9507 characters long. Set self.maxDiff to None to see it.

==
FAIL: TableSummarizer functions as expected with qualitative=True
--
Traceback (most recent call last):
  File "/tmp/tmp.ovLIvfIx3j/tests/test_cli/test_summarize_table.py", line 
42, in test_qualitative
self.assertEqual(sorted(result), sorted(summary_qualitative))
AssertionError: Lists differ: [u'\n', u'\n', u'\n', u'\n', u... != ['\n', 
'\n', '\n', '\n', '\n',...

First differing element 56:
u','
'.'

Diff is 7916 characters long. Set self.maxDiff to None to see it.

--
Ran 308 tests in 31.762s

FAILED (SKIP=1, failures=2)

With Python3 the output is slightly different but the same test is failing:

$ python3 -m nose tests
...
unzip(items) should be the inverse of zip(*items) ... ok

==
FAIL: TableSummarizer functions as expected
--
Traceback (most recent call last):
  File "/tmp/tmp.ovLIvfIx3j/tests/test_cli/test_summarize_table.py", line 
33, in test_default
self.assertEqual(sorted(result), sorted(summary_default))
AssertionError: Lists differ: ['\n'[355 chars])', ',', ',', ',', ',', ',', 
',', ',', ',', ',[1687 chars] 'z'] != ['\n'[355 chars])', '-', '.', '.', '.', 
'.', '.', '.', '.', '.[1687 chars] 'z']

First differing element 68:
','
'-'

Diff is 3455 characters long. Set self.maxDiff to None to see it.

==
FAIL: TableSummarizer functions as expected with qualitative=True
--
Traceback (most recent call last):
  File "/tmp/tmp.ovLIvfIx3j/tests/test_cli/test_summarize_table.py", line 
42, in test_qualitative
self.assertEqual(sorted(result), sorted(summary_qualitative))
AssertionError: Lists differ: ['\n'[293 chars] ', ',', ',', ',', ',', ',', 
',', ',', ',', ',[1402 chars] 'y'] != ['\n'[293 chars] ', '.', '.', '.', '.', 
'.', '.', '.', '.', '.[1402 chars] 'y']

First differing element 56:
','
'.'

Diff is 2901 characters long. Set self.maxDiff to None to see it.

--
Ran 308 tests in 2.339s

FAILED (SKIP=1, failures=2)

Any help to fix this is welcome.  My current approach would probably be
to exclude the two failing tests and decrease the severity of the bug to
normal.

What do you think?

Kind regards

  Andreas.

-- 
http://fam-tille.de



Bug#901098: autopkgtest regression

2018-06-08 Thread Paul Gevers
Source: primesieve
Version: 7.0+ds-1
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

With the upload of version 7.0+ds-1 your autopkgtest¹ started to fail.
I have copied the output below.

Could you please investigate and fix your autopkgtest? This is currently
delaying the migration of your package to testing with 13 days.

Paul

¹ https://ci.debian.net/packages/p/primesieve

https://ci.debian.net/data/autopkgtest/unstable/amd64/p/primesieve/428060/log.gz

autopkgtest [13:54:17]: test make-check-dev: [---
'include/primesieve/PrimeSieve.hpp' ->
'/tmp/autopkgtest-lxc.1gzk72p2/downtmp/autopkgtest_tmp/include/primesieve/PrimeSieve.hpp'
cp: cannot stat 'include/primesieve/ParallelPrimeSieve.hpp': No such
file or directory
autopkgtest [13:54:17]: test make-check-dev: ---]



signature.asc
Description: OpenPGP digital signature


Bug#899030: jessie-pu: package intel-microcode/3.20180425.1~deb8u1

2018-06-08 Thread Adam D. Barratt
Control: tags -1 + confirmed

On Fri, 2018-05-18 at 12:24 -0300, Henrique de Moraes Holschuh wrote:
...
> I'd like to update the intel-microcode package in Debian jessie.
> 
> This update adds the microcode-side fix for CVE-2017-5715 aka Spectre
> v2.
> 
> It has been very extensibly tested, as noted in the changelog:
> 

Please go ahead.

Regards,

Adam



Bug#901080: libtest-differences-perl: FTBFS with Perl 5.28: t/column-headers.t failure with verbose tests

2018-06-08 Thread gregor herrmann
Control: tag -1 + confirmed patch

On Fri, 08 Jun 2018 21:28:37 +0300, Niko Tyni wrote:

> Source: libtest-differences-perl
> Version: 0.64-1
> Severity: important
> User: debian-p...@lists.debian.org
> Usertags: perl-5.28-transition
> 
> This package fails to build with perl 5.28.0-RC1 (currently in
> experimental).
> 
>  
> http://perl.debian.net/rebuild-logs/perl-5.28-throwaway/libtest-differences-perl_0.64-1/libtest-differences-perl_0.64-1_amd64-2018-06-08T17:52:42Z.build
> 
> This seems to be related to verbose test output. 
> 
> $ prove -b t/column-headers.t 
> t/column-headers.t .. ok   
> All tests successful.
> Files=1, Tests=2,  0 wallclock secs ( 0.02 usr  0.00 sys +  0.13 cusr  0.02 
> csys =  0.17 CPU)
> Result: PASS
> 
> $ prove -v -b t/column-headers.t 
> t/column-headers.t .. 
> not ok 1 - got expected error output
> #   Failed test 'got expected error output'
> #   at t/column-headers.t line 14.
> #  got: '#   Failed test 'both the same'
> # #   at t/script/default-headers line 8.
> # # ++++
> # # | Elt|Got |Expected|
> # # ++++
> # # |   0|{   |{   |
> # # *   1|  foo => 'bar'  |  foo => 'baz'  *
> # # |   2|}   |}   |
> # # ++++
> # # Looks like you failed 1 test of 1.
> # '
> # expected: '
> # #   Failed test 'both the same'
> # #   at t/script/default-headers line 8.
> # # ++++
> # # | Elt|Got |Expected|
> # # ++++
> # # |   0|{   |{   |
> # # *   1|  foo => 'bar'  |  foo => 'baz'  *
> # # |   2|}   |}   |
> # # ++++
> # # Looks like you failed 1 test of 1.
> # '

Confirmed, both the failure and the correlation with test verbosity.
The following "fixes" the issue:


#v+
--- a/debian/rules
+++ b/debian/rules
@@ -1,3 +1,6 @@
 #!/usr/bin/make -f
 %:
dh $@
+
+override_dh_auto_test:
+   dh_auto_test -- --verbose 0
#v-


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: U2: Sunday Bloody Sunday


signature.asc
Description: Digital Signature


Bug#899014: stretch-pu: package blktrace/1.1.0-2

2018-06-08 Thread Adam D. Barratt
Control: tags -1 + confirmed

On Fri, 2018-05-18 at 21:13 +0200, Bas Zoetekouw wrote:
> Hi!
> 
> > Please use 1.0.5-1+deb8u1 and as target distribution just 'jessie'.
> > Use 1.1.0-2+deb9u1 and targeting 'stretch' instead (not
> > stretch-security).
> > 
> 
> Fixed.  New debdiffs follow:
> 

Please go ahead.

Regards,

Adam



Bug#888767: jessie-pu: package debian-security-support/2018.01.29~deb8u1

2018-06-08 Thread Adam D. Barratt
Control: tags -1 + confirmed

On Mon, 2018-01-29 at 17:45 +0100, Guido Günther wrote:
> This update brings debian-security-support in line with unstable.
> Most
> notably in oldstable this affects swftools since security support for
> it is
> now limited and chromium which doesn't receive any further security
> updates.
> 

Please go ahead.

Regards,

Adam



Bug#901097: ethstatus FTCBFS: Makefile hard codes gcc

2018-06-08 Thread Helmut Grohne
Source: ethstatus
Version: 0.4.8
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

ethstatus fails to cross build from source, because the Makefile hard
codes gcc. After making it substitutable, ethstatus cross builds
successfully. Please consider applying the attached patch.

Helmut
diff --minimal -Nru ethstatus-0.4.8/Makefile ethstatus-0.4.8+nmu1/Makefile
--- ethstatus-0.4.8/Makefile2016-03-27 07:29:44.0 +0200
+++ ethstatus-0.4.8+nmu1/Makefile   2018-06-08 23:17:22.0 +0200
@@ -18,7 +18,7 @@
 all : ethstatus
 
 ethstatus : ethstatus.c ethstatus.h
-   gcc $(CFLAGS) $(CPPFLAGS) -o ${BIN} ${SRC} $(LDFLAGS)
+   $(CC) $(CFLAGS) $(CPPFLAGS) -o ${BIN} ${SRC} $(LDFLAGS)
 
 clean:
rm -f ${BIN} *.o core *~ 
diff --minimal -Nru ethstatus-0.4.8/debian/changelog 
ethstatus-0.4.8+nmu1/debian/changelog
--- ethstatus-0.4.8/debian/changelog2016-06-01 04:25:53.0 +0200
+++ ethstatus-0.4.8+nmu1/debian/changelog   2018-06-08 23:17:28.0 
+0200
@@ -1,3 +1,10 @@
+ethstatus (0.4.8+nmu1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Make gcc substitutable. (Closes: #-1)
+
+ -- Helmut Grohne   Fri, 08 Jun 2018 23:17:28 +0200
+
 ethstatus (0.4.8) unstable; urgency=medium
 
   * New release.


Bug#901096: Idle desktop file is broken

2018-06-08 Thread itraveller
Package: idle
Version: 3.6.5-3
Priority: minor

The desktop file does not display the desired icon and clicking on the script 
shortcut starts only IDLE itself.

The reason is a broken link to the icon and an incorrect argument format in the 
desktop file.

To fix "idle.desktop" needs to replace "idle3.xml" -> "idle.xml" and "idle %U" 
-> "idle %F".

I am using Debian GNU/Linux 9.4, kernel 4.16.0-1-686-pae and libc6 2.27-3.

--

Bug#901095: sqlite3: Please package sqlite3_analyzer tool

2018-06-08 Thread Tobias Gruetzmacher
Package: sqlite3
Version: 3.24.0-1
Severity: wishlist

Hi,

there is a tool named "sqlite3_analyzer" described on
https://www.sqlite.org/sqlanalyze.html and part of the SQLite source
code. Unfortunatly, it's not packaged in Debian. It would be nice if
this tool was available in Debian.

Regards, Tobias

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

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

Versions of packages sqlite3 depends on:
ii  libc6 2.27-3
ii  libreadline7  7.0-5
ii  libsqlite3-0  3.24.0-1
ii  zlib1g1:1.2.11.dfsg-1

sqlite3 recommends no packages.

Versions of packages sqlite3 suggests:
pn  sqlite3-doc  

-- no debconf information



Bug#901082: libpgobject-type-json-perl: FTBFS with Perl 5.28: t/02-serialization.t failure

2018-06-08 Thread gregor herrmann
On Fri, 08 Jun 2018 21:38:12 +0300, Niko Tyni wrote:

> Source: libpgobject-type-json-perl
> Version: 2.01-1
> Severity: important
> User: debian-p...@lists.debian.org
> Usertags: perl-5.28-transition
> 
> This package fails to build with Perl 5.28 (currently in experimental.)
> 
>   
> http://perl.debian.net/rebuild-logs/perl-5.28-throwaway/libpgobject-type-json-perl_2.01-1/libpgobject-type-json-perl_2.01-1_amd64-2018-06-08T17:55:53Z.build
> 
>   #   Failed test 'Literal serializes correctly'
>   #   at t/02-serialization.t line 49.
>   #  got: '123'
>   # expected: '"123"'
>   # Looks like you failed 1 test of 23.
>  
> I don't see an upstream bug or a failing CPAN test report
> but it fails consistently for me.

I can confirm the failure with 5.28, and it still passes the tests
with 5.26.

No idea which JSON thing in which part adds/removes the quotation
marks. All I can think of is the different version of JSON::PP but
then the problem should show up elsewhere as well.


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: Kante: Ituri


signature.asc
Description: Digital Signature


Bug#901094: caja-seahorse FTCBFS: lintian: autotools-pkg-config-macro-not-cross-compilation-safe

2018-06-08 Thread Helmut Grohne
Source: caja-seahorse
Version: 1.18.4-1
Tags: patch upstream
User: helm...@debian.org
Usertags: rebootstrap

caja-seahorse fails to cross build from source. The reason is best
explained in lintian tag
autotools-pkg-config-macro-not-cross-compilation-safe. The attached
patch fixes that. Please consider applying it.

Helmut
--- caja-seahorse-1.18.4.orig/configure.ac
+++ caja-seahorse-1.18.4/configure.ac
@@ -26,7 +26,7 @@
 AM_DISABLE_STATIC
 AM_PROG_LIBTOOL
 IT_PROG_INTLTOOL([0.35.0])
-AC_PATH_PROG(PKG_CONFIG, pkg-config, no)
+PKG_PROG_PKG_CONFIG
 
 AC_SYS_LARGEFILE
 AC_TYPE_OFF_T


Bug#901093: node-sshpk: CVE-2018-3737

2018-06-08 Thread Salvatore Bonaccorso
Source: node-sshpk
Version: 1.13.1+dfsg-1
Severity: important
Tags: security upstream
Forwarded: https://github.com/joyent/node-sshpk/issues/44

Hi,

The following vulnerability was published for node-sshpk.

CVE-2018-3737[0]:
| sshpk is vulnerable to ReDoS when parsing crafted invalid public keys.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-3737
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-3737
[1] https://github.com/joyent/node-sshpk/issues/44
[2] 
https://github.com/joyent/node-sshpk/commit/46065d38a5e6d1bccf86d3efb2fb83c14e3f9957

Regards,
Salvatore



Bug#901092: passwordsafe FTCBFS: multiple reasons

2018-06-08 Thread Helmut Grohne
Source: passwordsafe
Version: 1.05+dfsg-2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

passwordsafe fails to cross build from source for two reasons. The
upstream build system hard codes the build architecture pkg-config and
the debian packaging fails running tests despite
DEB_BUILD_OPTIONS=nocheck. The attached patch fixes both and makes
passwordsafe cross build successfully. Please consider applying it.

Helmut
diff --minimal -Nru passwordsafe-1.05+dfsg/debian/changelog 
passwordsafe-1.05+dfsg/debian/changelog
--- passwordsafe-1.05+dfsg/debian/changelog 2018-04-27 03:35:53.0 
+0200
+++ passwordsafe-1.05+dfsg/debian/changelog 2018-06-08 23:02:28.0 
+0200
@@ -1,3 +1,12 @@
+passwordsafe (1.05+dfsg-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ cross.patch: Make pkg-config substitutable.
++ Honour DEB_BUILD_OPTIONS=nocheck.
+
+ -- Helmut Grohne   Fri, 08 Jun 2018 23:02:28 +0200
+
 passwordsafe (1.05+dfsg-2) unstable; urgency=medium
 
   * Fix build issue that causes help files to not be found by the program
diff --minimal -Nru passwordsafe-1.05+dfsg/debian/patches/cross.patch 
passwordsafe-1.05+dfsg/debian/patches/cross.patch
--- passwordsafe-1.05+dfsg/debian/patches/cross.patch   1970-01-01 
01:00:00.0 +0100
+++ passwordsafe-1.05+dfsg/debian/patches/cross.patch   2018-06-08 
23:02:27.0 +0200
@@ -0,0 +1,20 @@
+--- passwordsafe-1.05+dfsg.orig/src/os/unix/Makefile
 passwordsafe-1.05+dfsg/src/os/unix/Makefile
+@@ -24,6 +24,8 @@
+ 
+ NAME=os
+ 
++PKG_CONFIG ?= pkg-config
++
+ ifndef NO_YUBI
+ YUBI_SRC=PWYubi.cpp
+ # Use the following if you've installed ykpers-1 manually
+@@ -32,7 +34,7 @@
+ 
+ # If you've installed it from your distro's package repo, you
+ # should use this instead:
+-YBPERSFLAGS=$(shell pkg-config --cflags ykpers-1)
++YBPERSFLAGS=$(shell $(PKG_CONFIG) --cflags ykpers-1)
+ endif
+ 
+ LIBSRC  = cleanup.cpp debug.cpp dir.cpp env.cpp \
diff --minimal -Nru passwordsafe-1.05+dfsg/debian/patches/series 
passwordsafe-1.05+dfsg/debian/patches/series
--- passwordsafe-1.05+dfsg/debian/patches/series2018-04-27 
03:35:53.0 +0200
+++ passwordsafe-1.05+dfsg/debian/patches/series2018-06-08 
23:01:54.0 +0200
@@ -1,2 +1,3 @@
 no_force_debug
 perl_shebangs
+cross.patch
diff --minimal -Nru passwordsafe-1.05+dfsg/debian/rules 
passwordsafe-1.05+dfsg/debian/rules
--- passwordsafe-1.05+dfsg/debian/rules 2018-04-27 03:35:53.0 +0200
+++ passwordsafe-1.05+dfsg/debian/rules 2018-06-08 23:02:28.0 +0200
@@ -18,6 +18,7 @@
 override_dh_installchangelogs:
dh_installchangelogs --keep docs/ReleaseNotes.txt
 
+ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
 override_dh_auto_test:
LC_ALL=C.UTF-8 make release-test
-
+endif


Bug#901091: dwm FTCBFS: does not pass cross tools to make

2018-06-08 Thread Helmut Grohne
Source: dwm
Version: 6.1-4
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

dwm fails to cross build from source, because it does not pass cross
tools to make and thus uses the build architecture compiler. The easiest
way of passing them is letting dh_auto_build do it and then dwm cross
builds successfully. Please consider applying the attached patch.

Helmut
diff --minimal -Nru dwm-6.1/debian/changelog dwm-6.1/debian/changelog
--- dwm-6.1/debian/changelog2017-08-30 12:12:50.0 +0200
+++ dwm-6.1/debian/changelog2018-06-08 22:54:56.0 +0200
@@ -1,3 +1,10 @@
+dwm (6.1-4.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_build pass cross tools to make. (Closes: #-1)
+
+ -- Helmut Grohne   Fri, 08 Jun 2018 22:54:56 +0200
+
 dwm (6.1-4) unstable; urgency=medium
 
   * debian/control:
diff --minimal -Nru dwm-6.1/debian/rules dwm-6.1/debian/rules
--- dwm-6.1/debian/rules2017-08-30 12:12:50.0 +0200
+++ dwm-6.1/debian/rules2018-06-08 22:54:51.0 +0200
@@ -22,7 +22,7 @@
do \
$(MAKE) clean; \
cp $${ALTERNATIVE} config.h; \
-   CFLAGS="$(CFLAGS)" $(MAKE) PREFIX=/usr; \
+   CFLAGS="$(CFLAGS)" dh_auto_build -- PREFIX=/usr; \
install -m 0755 dwm debian/dwm/usr/bin/dwm.`basename 
$${ALTERNATIVE} | cut -d'.' -f 2`; \
ln -s dwm.1.gz debian/dwm/usr/share/man/man1/dwm.`basename 
$${ALTERNATIVE} | cut -d'.' -f 2`.1.gz; \
done


Bug#901085: libur-perl: FTBFS with Perl 5.28: test failures

2018-06-08 Thread gregor herrmann
On Fri, 08 Jun 2018 22:18:49 +0300, Niko Tyni wrote:

> Source: libur-perl
> Version: 0.450-1
> Severity: important
> User: debian-p...@lists.debian.org
> Usertags: perl-5.28-transition
> 
> This package fails to build with Perl 5.28 (currently in experimental.)
> 
>   
> http://perl.debian.net/rebuild-logs/perl-5.28-throwaway/libur-perl_0.450-1/libur-perl_0.450-1_amd64-2018-06-08T17:53:04Z.build

>   Test Summary Report
>   ---
>   t/URT/t/41_rpc_basic.t  
> (Wstat: 256 Tests: 40 Failed: 1)
> Failed test:  27
> Non-zero exit status: 1
>   t/URT/t/42_rpc_between_processes.t  
> (Wstat: 256 Tests: 35 Failed: 1)
> Failed test:  24
> Non-zero exit status: 1
>   t/URT/t/63c_view_with_subviews.t
> (Wstat: 512 Tests: 23 Failed: 2)
> Failed tests:  11, 19
> Non-zero exit status: 2
>   Files=273, Tests=7420, 145 wallclock secs ( 0.96 usr  0.30 sys + 125.43 
> cusr  8.59 csys = 135.28 CPU)
>   Result: FAIL

Confirmed, and I can offer even more failures:

Test Summary Report
---
t/URT/t/41_rpc_basic.t  (Wstat: 
256 Tests: 40 Failed: 1)
  Failed test:  27
  Non-zero exit status: 1
t/URT/t/42_rpc_between_processes.t  (Wstat: 
256 Tests: 35 Failed: 1)
  Failed test:  24
  Non-zero exit status: 1
t/URT/t/63c_view_with_subviews.t(Wstat: 
512 Tests: 23 Failed: 2)
  Failed tests:  11, 19
  Non-zero exit status: 2
t/URT/t/70d_command_sub_command_factory.t   (Wstat: 
768 Tests: 6 Failed: 3)
  Failed tests:  3-5
  Non-zero exit status: 3
t/class_browser/internal.t  (Wstat: 
65280 Tests: 8 Failed: 2)
  Failed tests:  2, 8
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 38 tests but ran 8.
Files=273, Tests=7390, 212 wallclock secs ( 1.68 usr  0.43 sys + 195.85 cusr 
10.47 csys = 208.43 CPU)
Result: FAIL


The two new ones are:

#   Failed test 'sub_command_classes'
#   at t/URT/t/70d_command_sub_command_factory.t line 17.
# died: Error while autoloading with 'use 
CmdTest::Thing::/build/libur-perl-0.460+ds/t//CmdTest/Thing/Create': Unknown 
regexp modifier "/b" at (eval 234) line 1, at end of line
# Regexp modifiers "/l" and "/u" are mutually exclusive at (eval 234) line 1, 
at end of line
# Unknown regexp modifier "/r" at (eval 234) line 1, at end of line
# BEGIN not safe after errors--compilation aborted at (eval 234) line 1.
#   Failed test 'sub_command_classes are correct'
#   at t/URT/t/70d_command_sub_command_factory.t line 18.
# Structures begin differing at:
#  $got->[0] = Does not exist
# $expected->[0] = 'CmdTest::Thing::Create::One'
#   Failed test 'create thing one command meta'
#   at t/URT/t/70d_command_sub_command_factory.t line 19.
# died: Can't locate object method "__meta__" via package 
"CmdTest::Thing::Create::One" at t/URT/t/70d_command_sub_command_factory.t line 
19.
#   Test::Exception::lives_ok() called at 
t/URT/t/70d_command_sub_command_factory.t line 19
# Looks like you failed 3 tests of 6.
t/URT/t/70d_command_sub_command_factory.t .
1..6
ok 1 - use Command::SubCommandFactory;
ok 2 - use CmdTest::Thing::Create;
not ok 3 - sub_command_classes
not ok 4 - sub_command_classes are correct
not ok 5 - create thing one command meta
ok 6 - no thing two create command meta
Dubious, test returned 3 (wstat 768, 0x300)
Failed 3/6 subtests



Can't call method "data" on an undefined value at t/class_browser/internal.t 
line 87.
# Looks like your test exited with 255 just after 8.
t/class_browser/internal.t  
1..38
ok 1 - Created ClassBrowser command
not ok 2 - _generate__class_name_cache
ok 3 - _load_class_info_from_modules_on_filesystem
ok 4 - Get directory tree cache
ok 5 - Tree root has children
ok 6 - Tree root name
ok 7 - Tree root data
not ok 8 - Root has 3 children
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 32/38 subtests 


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: Dadoo


signature.asc
Description: Digital Signature


Bug#894045: libvncserver: CVE-2018-7225

2018-06-08 Thread Salvatore Bonaccorso
Hi Markus,

On Fri, Jun 08, 2018 at 10:46:19PM +0200, Markus Koschany wrote:
> Hi Salvatore,
> 
> Am 08.06.2018 um 22:38 schrieb Salvatore Bonaccorso:
> > Hi Markus,
> > 
> > On Tue, Jun 05, 2018 at 02:52:58PM +0200, Markus Koschany wrote:
> >> Control: tags -1 patch
> >>
> >> Dear maintainer,
> >>
> >> I've prepared a patch fixing CVE-2018-7225. I am also going to send the
> >> debdiffs for stretch and jessie to the security team.
> >>
> >> Please find attached the debdiff for sid.
> > 
> > Are you planning to upload a fix proposing a NMU (In case maintainer
> > has no time to work on it)? I did raise the severity to RC now, given
> > Moritz has released the DSA with your updates for jessie- and
> > stretch-security.
> 
> Sure, I can do that. I just wanted to give the maintainer some time but
> I can upload the fix at the weekend.

Sure there is no pressure.

Regards,
Salvatore



Bug#894045: libvncserver: CVE-2018-7225

2018-06-08 Thread Markus Koschany
Hi Salvatore,

Am 08.06.2018 um 22:38 schrieb Salvatore Bonaccorso:
> Hi Markus,
> 
> On Tue, Jun 05, 2018 at 02:52:58PM +0200, Markus Koschany wrote:
>> Control: tags -1 patch
>>
>> Dear maintainer,
>>
>> I've prepared a patch fixing CVE-2018-7225. I am also going to send the
>> debdiffs for stretch and jessie to the security team.
>>
>> Please find attached the debdiff for sid.
> 
> Are you planning to upload a fix proposing a NMU (In case maintainer
> has no time to work on it)? I did raise the severity to RC now, given
> Moritz has released the DSA with your updates for jessie- and
> stretch-security.

Sure, I can do that. I just wanted to give the maintainer some time but
I can upload the fix at the weekend.

Cheers,

Markus



signature.asc
Description: OpenPGP digital signature


Bug#901090: lv2vocoder FTCBFS: GNUmakefile hard codes build architecture tools

2018-06-08 Thread Helmut Grohne
Source: lv2vocoder
Version: 1-5
Tags: patch upstream
User: helm...@debian.org
Usertags: rebootstrap

lv2vocoder fails to cross build from source, because the upstream
GNUmakefile hard codes build architecture build tools. The attached
patch fixes that and makes lv2vocoder cross build successfully. Please
consider applying it.

Helmut
--- lv2vocoder-1.orig/GNUmakefile
+++ lv2vocoder-1/GNUmakefile
@@ -3,7 +3,8 @@
 # These files go into the bundle
 BUNDLE_FILES = manifest.ttl vocoder.ttl vocoder.so
 
-CFLAGS += -c -Wall -fPIC -DPIC $(strip $(shell pkg-config --cflags lv2core))
+PKG_CONFIG ?= pkg-config
+CFLAGS += -c -Wall -fPIC -DPIC $(strip $(shell $(PKG_CONFIG) --cflags lv2core))
 
 GENDEP_SED_EXPR = "s/^\\(.*\\)\\.o *: /$(subst /,\/,$(@:.d=.o)) $(subst /,\/,$@) : /g"
 GENDEP_C = set -e; $(GCC_PREFIX)gcc -MM $(CFLAGS) $< | sed $(GENDEP_SED_EXPR) > $@; [ -s $@ ] || rm -f $@
@@ -20,7 +21,7 @@
 
 vocoder.so: vocoder.o
 	@echo "Creating LV2 shared library $@ ..."
-	@g++ -shared -fPIC $(LDFLAGS) $< -o $@
+	@$(CXX) -shared -fPIC $(LDFLAGS) $< -o $@
 
 # The main target - the LV2 plugin bundle
 $(PLUGIN_NAME).lv2: $(BUNDLE_FILES)


Bug#901089: stretch-pu: package dosbox/0.74-4.2+deb9u1

2018-06-08 Thread Moritz Muehlenhoff
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

dosbox is broken in the default setting on a number of systems/DOS binaries
(see #857341). This got fixed in unstable back in September, but the patch
is also needed in stretch. Apart from debian/changelog, the debdiff the
only change applied to the package in unstable since the stretch release.

I've verified that with updated packages "Syndicate" now works fine.

Cheers,
Moritz
diff -Nru dosbox-0.74/debian/changelog dosbox-0.74/debian/changelog
--- dosbox-0.74/debian/changelog2015-10-13 16:55:00.0 +0200
+++ dosbox-0.74/debian/changelog2018-05-21 22:55:46.0 +0200
@@ -1,3 +1,10 @@
+dosbox (0.74-4.2+deb9u1) stretch; urgency=medium
+
+  * Non-maintainer upload:
+  * Fix crashes with core=dynamic (Closes: #857341)
+
+ -- Moritz Mühlenhoff   Mon, 21 May 2018 22:55:46 +0200
+
 dosbox (0.74-4.2) unstable; urgency=medium
 
   * non-maintainer upload
diff -Nru dosbox-0.74/debian/patches/series dosbox-0.74/debian/patches/series
--- dosbox-0.74/debian/patches/series   2015-06-17 20:28:00.0 +0200
+++ dosbox-0.74/debian/patches/series   2018-05-21 22:55:31.0 +0200
@@ -3,3 +3,4 @@
 fix-ftbfs-format-security.patch
 wine-move-z-mount-svn3736.patch
 wine-style-namemangling-svn3742.patch
+update-64bit-recompiler.patch
diff -Nru dosbox-0.74/debian/patches/update-64bit-recompiler.patch 
dosbox-0.74/debian/patches/update-64bit-recompiler.patch
--- dosbox-0.74/debian/patches/update-64bit-recompiler.patch1970-01-01 
01:00:00.0 +0100
+++ dosbox-0.74/debian/patches/update-64bit-recompiler.patch2018-05-21 
22:55:22.0 +0200
@@ -0,0 +1,437 @@
+From: gulikoza
+Bug-Debian: https://bugs.debian.org/857341
+Description: Update 64bit dynamic recompiler to fix several bugs
+ This adds support for absolute 64bit addressing and fixes the
+ "Unhandled memory reference" crash. This comes from upstream SVN
+ r3951, and includes related patches r3674 and r3894. This patch also
+ contains an LLVM compile fix (r3990).
+Index: dosbox-0.74/src/cpu/core_dynrec/risc_x64.h
+===
+--- dosbox-0.74.orig/src/cpu/core_dynrec/risc_x64.h
 dosbox-0.74/src/cpu/core_dynrec/risc_x64.h
+@@ -83,36 +83,106 @@ static void gen_mov_regs(HostReg reg_dst
+   cache_addb(0xc0+(reg_dst<<3)+reg_src);
+ }
+ 
++// move a 64bit constant value into a full register
++static void gen_mov_reg_qword(HostReg dest_reg,Bit64u imm) {
++  cache_addb(0x48);
++  cache_addb(0xb8+dest_reg);  // mov dest_reg,imm
++  cache_addq(imm);
++}
+ 
+-static INLINE void gen_memaddr(HostReg reg,void* data) {
+-  Bit64s diff = (Bit64s)data-((Bit64s)cache.pos+5);
+-  if ((diff<0x8000LL) && (diff>-0x8000LL)) {
++
++// This function generates an instruction with register addressing and a 
memory location
++static INLINE void gen_reg_memaddr(HostReg reg,void* data,Bit8u op,Bit8u 
prefix=0) {
++  Bit64s diff = (Bit64s)data-((Bit64s)cache.pos+(prefix?7:6));
++//if ((diff<0x8000LL) && (diff>-0x8000LL)) { //clang messes 
itself up on this...
++  if ( (diff>>63) == (diff>>31) ) { //signed bit extend, test to see if 
value fits in a Bit32s
++  // mov reg,[rip+diff] (or similar, depending on the op) to 
fetch *data
++  if(prefix) cache_addb(prefix);
++  cache_addb(op);
+   cache_addb(0x05+(reg<<3));
+   // RIP-relative addressing is offset after the instruction 
+   cache_addd((Bit32u)(((Bit64u)diff)&0xLL)); 
+   } else if ((Bit64u)data<0x1LL) {
++  // mov reg,[data] (or similar, depending on the op) when 
absolute address of data is <4GB
++  if(prefix) cache_addb(prefix);
++  cache_addb(op);
+   cache_addw(0x2504+(reg<<3));
+   cache_addd((Bit32u)(((Bit64u)data)&0xLL));
+   } else {
+-  E_Exit("DRC64:Unhandled memory reference");
++  // load 64-bit data into tmp_reg and do mov reg,[tmp_reg] (or 
similar, depending on the op)
++  HostReg tmp_reg = HOST_EAX;
++  if(reg == HOST_EAX) tmp_reg = HOST_ECX;
++
++  cache_addb(0x50+tmp_reg);   // push rax/rcx
++  gen_mov_reg_qword(tmp_reg,(Bit64u)data);
++
++  if(prefix) cache_addb(prefix);
++  cache_addb(op);
++  cache_addb(tmp_reg+(reg<<3));
++
++  cache_addb(0x58+tmp_reg);   // pop rax/rcx
+   }
+ }
+ 
++// Same as above, but with immediate addressing and a memory location
++static INLINE void gen_memaddr(Bitu modreg,void* data,Bitu off,Bitu imm,Bit8u 
op,Bit8u prefix=0) {
++  Bit64s diff = (Bit64s)data-((Bit64s)cache.pos+off+(prefix?7:6));
++//if ((diff<0x8000LL) && (diff>-0x8000LL)) {
++  if ( (diff>>63) == (diff>>31) ) {
++

Bug#894045: libvncserver: CVE-2018-7225

2018-06-08 Thread Salvatore Bonaccorso
Hi Markus,

On Tue, Jun 05, 2018 at 02:52:58PM +0200, Markus Koschany wrote:
> Control: tags -1 patch
> 
> Dear maintainer,
> 
> I've prepared a patch fixing CVE-2018-7225. I am also going to send the
> debdiffs for stretch and jessie to the security team.
> 
> Please find attached the debdiff for sid.

Are you planning to upload a fix proposing a NMU (In case maintainer
has no time to work on it)? I did raise the severity to RC now, given
Moritz has released the DSA with your updates for jessie- and
stretch-security.

Regards,
Salvatore



Bug#862030: jessie-pu: package rar/2:4.2.0+dfsg.1-0.1

2018-06-08 Thread Adam D. Barratt
Control: tags -1 + confirmed

On Fri, 2017-11-24 at 17:14 +, Ben Hutchings wrote:
> On Tue, 2017-06-27 at 22:55 +0200, Cyril Brulebois wrote:
> > Control: tag -1 moreinfo
> > 
> > Ben Hutchings  (2017-05-07):
> > > rar should be updated to fix #860952.
> > > 
> > > The orig tarballs need to be repacked to exclude
> > > rar_static.  Then I
> > > would apply the following source patch:
> > > 
> > 
...
> > Based on the last line of context and the first line of the diff
> > (marked
> > with <=== above), I'm not sure whether you plan to remove
> > default.sfx
> > along with it, since the previous line still mentions it, and the
> > rules
> > file as well, see below.
> 
> That was intentional, although I forgot to mention it.  default.sfx
> hasn't been statically linked since (I think) version 3.9.3-1.
> 

Please go ahead; apologies for the long delay.

Regards,

Adam



Bug#887047: jessie-pu: package dh-make-perl/0.84-2+deb8u1

2018-06-08 Thread gregor herrmann
On Fri, 08 Jun 2018 21:21:35 +0100, Adam D. Barratt wrote:

> On Sat, 2018-01-13 at 02:42 +0100, gregor herrmann wrote:
> > I've prepared an update for dh-make-perl in jessie which fixes
> > #851848.
> 
> Please go ahead; sorry for the long delay.

Thank you. Uploaded.


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: Police: The Bed's Too Big Without You


signature.asc
Description: Digital Signature


Bug#867461: Bug#858539: should ca-certificates certdata.txt synchronize across all suites?

2018-06-08 Thread Adam D. Barratt
Control: tags -1 + moreinfo

On Mon, 2017-10-23 at 08:59 -0400, Antoine Beaupré wrote:
> On 2017-07-19 11:35:56, Michael Shuler wrote:
...
> > I spent a few sessions over the past few days getting the mozilla
> > bundle
> > 2.14 committed to all the suite branches wheezy and newer. I have
> > some
> > more verification to work on and I'll get some packages rolled up
> > and
> > tested for all the suites.
> > 
> > I appreciate the notes here!
> 
> Hi!
> 
> Any update here? According to our records, this issue is still
> pending... I see you pushed the updates to wheezy, but didn't upload
> the
> results... Do you need help preparing the upload?
> 

Ping? We're a week away from the final chance to get an update into
jessie-as-oldstable before it becomes jessie-lts.

Regards,

Adam



Bug#882904: MariaDB 10.0.33 to next Jessie point release

2018-06-08 Thread Adam D. Barratt
Control: tags -1 +moreinfo

On Mon, 2017-11-27 at 19:50 +, Adam D. Barratt wrote:
...
> On Mon, 2017-11-27 at 21:23 +0200, Otto Kekäläinen wrote:
...
> > I will prepare the final changelog when I have thumbs up from you
> > to
> > do so.
> 
> You appear to be stuck in a little bit of a chicken-and-egg
> situation,
> given that the final decision as to whether to accept the package
> will
> be based on a diff of the final source package.
> 
...
> We very much prefer diffs to form part of the bug log, not least
> because they're guaranteed to persist in that manner.
> 

That never happened, and 10.0.32 is stuck in oldstable-new because it
FTBFS on multiple architectures. Is 10.0.33 expected to fix all of
those issues?

Regards,

Adam



Bug#898381: pypass: diff for NMU version 0.2.1-1.1

2018-06-08 Thread Adrian Bunk
Control: tags 898381 + patch
Control: tags 898381 + pending

Dear maintainer,

I've prepared an NMU for pypass (versioned as 0.2.1-1.1) and uploaded
it to DELAYED/14. Please feel free to tell me if I should cancel it.

cu
Adrian

-- 

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

diff -Nru pypass-0.2.1/debian/changelog pypass-0.2.1/debian/changelog
--- pypass-0.2.1/debian/changelog	2018-04-30 03:01:50.0 +0300
+++ pypass-0.2.1/debian/changelog	2018-06-08 23:29:22.0 +0300
@@ -1,3 +1,11 @@
+pypass (0.2.1-1.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Add the missing Breaks+Replaces: pypass (<< 0.2.1-1~) to
+python3-pypass, thanks to Andreas Beckmann. (Closes: #898381)
+
+ -- Adrian Bunk   Fri, 08 Jun 2018 23:29:22 +0300
+
 pypass (0.2.1-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru pypass-0.2.1/debian/control pypass-0.2.1/debian/control
--- pypass-0.2.1/debian/control	2018-04-30 02:57:47.0 +0300
+++ pypass-0.2.1/debian/control	2018-06-08 23:29:22.0 +0300
@@ -36,6 +36,8 @@
 Multi-Arch: foreign
 Depends: ${misc:Depends},
  ${python3:Depends},
+Breaks: pypass (<< 0.2.1-1~)
+Replaces: pypass (<< 0.2.1-1~)
 Description: pypass library for Python3
  pypass is a password manager written in Python that provides the same
  functionality as pass. In addition, it is useable as a library.


Bug#881481: tarantool FTBFS with recent debhelper: dh_systemd_enable: Requested unit "tarantool.service" but it was not found in any package acted on

2018-06-08 Thread Alexander Turenko
On Thu, 7 Jun 2018 21:36:40 +0300 Alexander Turenko 
wrote:
> On Sun, 12 Nov 2017 11:15:19 +0200 Adrian Bunk  wrote:
> > Source: tarantool
> > Version: 1.7.5.46.gd98815384-1
> > Severity: serious
> >
> >
>
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/tarantool.html
> >
> > ...
> > dh_systemd_enable -ptarantool --name=tarantool tarantool.service
> > dh_systemd_enable: Requested unit "tarantool.service" but it was not
> found in any package acted on.
> > dh_systemd_enable: Could not handle all of the requested services
> > /usr/share/cdbs/1/rules/debhelper.mk:233: recipe for target
> 'binary-install/tarantool' failed
> > make: *** [binary-install/tarantool] Error 2
> >
> >
> > < nthykier> tarantool:  Tries to enable the service in a package that
> does not ship the service => bug in tarantool
> > < nthykier> Failing call "dh_systemd_enable -ptarantool --name=tarantool
> tarantool.service" - a bit further up, there is a successful call
> > "dh_systemd_enable -ptarantool-common --name=tarantool
> tarantool.service"
> > < nthykier> (note the -p argument differs)
> >
> >
>
> Fixed in mainstream tarantool 1.9 and 1.10.
>
>
https://github.com/tarantool/tarantool/commit/8925b8622f381378684de633e917229051e3482f
>
> Don't know how to proceed with 1.7 package Debian has. It seems to be out
of
> the scope of my responsibility.
>
> WBR, Alexander Turenko.

It was fixed partially by the commit above, so another patch is necessary:

https://github.com/tarantool/tarantool/commit/e38d2762cd1950ed3bbb70306350cbc441c2a938

Now it is really fixed in 1.9, 1.10 and 2.0.

WBR, Alexander Turenko.


Bug#885087: Slightly improved version

2018-06-08 Thread Adam D. Barratt
Control: tags -1 + confirmed

On Sat, 2018-01-20 at 11:22 -0200, Eduardo M KALINOWSKI wrote:
> I've made a small change to the package, changing the new dependency
> from gvfs to desktop-file-utils, since that's what's really necessary
> (as discovered in #885086).
> 
> The new debdiff is attached.
> 

Please go ahead; sorry for the delay.

Regards,

Adam



Bug#883831: jessie-pu: package publicsuffix/20171028.2055-0+deb8u1

2018-06-08 Thread Adam D. Barratt
Control: tags -1 + moreinfo

On Thu, 2017-12-07 at 18:14 -0500, d...@fifthhorseman.net wrote:
> Please consider an update to publicsuffix in debian jessie.
> 
> This package reflects the state of the network, and keeping it
> current
> is useful for all the packages that depend on it.
> 

I'm guessing you'd prefer to look at a more recent revision by now.
(Although bear in mind that we're looking at just over a week before
the final window for getting fixes into jessie-as-oldstable rather than
jessie-lts.)

Regards,

Adam



Bug#898995: live-wrapper: debian-live-9.4.0-amd64-xfce.iso image file is larger than its isosize

2018-06-08 Thread Steve McIntyre
Control tag -1 +pending

On Sat, Jun 02, 2018 at 03:38:20PM +0200, Thomas Schmitt wrote:
>Hi,
>
>i wrote:
>> Add to the xorriso run of live-wrapper the command
>>
>>   -compliance no_emul_toc

Added in git now, so should show up in builds from this point
forwards.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Further comment on how I feel about IBM will appear once I've worked out
 whether they're being malicious or incompetent. Capital letters are forecast."
 Matthew Garrett, http://www.livejournal.com/users/mjg59/30675.html



Bug#885028: jessie-pu: package mosquitto/1.3.4-2+deb8u2

2018-06-08 Thread Adam D. Barratt
Control: tags -1 + confirmed

On Fri, 2017-12-22 at 23:44 +, Roger A. Light wrote:
> This patch fixes CVE-2017-9868 for mosquitto. The security team
> believes
> it is not worthy of a DSA and should be fixed by a point release
> instead.
> 

Please go ahead; sorry for the delay.

Regards,

Adam



Bug#885584: jessie-pu: package ncurses/5.9+20140913-1+deb8u3

2018-06-08 Thread Adam D. Barratt
Control: tags -1 + confirmed

On Thu, 2017-12-28 at 11:43 +0100, Sven Joachim wrote:
> 
The same problem with the same fix as in #885582 for stretch.

Please go ahead. Apologies for the very long delay.

Regards,

Adam



Bug#898375: duo-unix: diff for NMU version 1.9.21-1.1

2018-06-08 Thread Adrian Bunk
Control: tags 898375 + patch
Control: tags 898375 + pending

Dear maintainer,

I've prepared an NMU for duo-unix (versioned as 1.9.21-1.1) and uploaded 
it to DELAYED/14. Please feel free to tell me if I should cancel it.

cu
Adrian

-- 

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

diff -Nru duo-unix-1.9.21/debian/changelog duo-unix-1.9.21/debian/changelog
--- duo-unix-1.9.21/debian/changelog	2017-05-31 21:16:05.0 +0300
+++ duo-unix-1.9.21/debian/changelog	2018-06-08 22:18:44.0 +0300
@@ -1,3 +1,12 @@
+duo-unix (1.9.21-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Move the headers to /usr/include/duo as already done by several
+other distributions, thanks to Juhani Numminen. (Closes: #898375)
+  * Priority: extra -> optional
+
+ -- Adrian Bunk   Fri, 08 Jun 2018 22:18:44 +0300
+
 duo-unix (1.9.21-1) unstable; urgency=medium
 
   * New upstream release (Closes: 863831).
diff -Nru duo-unix-1.9.21/debian/control duo-unix-1.9.21/debian/control
--- duo-unix-1.9.21/debian/control	2016-11-17 07:25:57.0 +0200
+++ duo-unix-1.9.21/debian/control	2018-06-08 22:18:44.0 +0300
@@ -1,5 +1,5 @@
 Source: duo-unix
-Priority: extra
+Priority: optional
 Maintainer: Kees Cook 
 Build-Depends: debhelper (>= 9), dh-autoreconf, libcurl4-openssl-dev,
  libssl-dev, libpam-dev, python, chrpath
diff -Nru duo-unix-1.9.21/debian/libduo-dev.install duo-unix-1.9.21/debian/libduo-dev.install
--- duo-unix-1.9.21/debian/libduo-dev.install	2011-09-02 23:21:02.0 +0300
+++ duo-unix-1.9.21/debian/libduo-dev.install	2018-06-08 22:18:44.0 +0300
@@ -1,3 +1,3 @@
 usr/lib/*/libduo.so
 usr/lib/*/pkgconfig/*
-usr/include/*
+usr/include/duo/*
diff -Nru duo-unix-1.9.21/debian/rules duo-unix-1.9.21/debian/rules
--- duo-unix-1.9.21/debian/rules	2016-11-17 07:25:57.0 +0200
+++ duo-unix-1.9.21/debian/rules	2018-06-08 22:18:44.0 +0300
@@ -12,7 +12,8 @@
 
 override_dh_auto_configure:
 	dh_auto_configure -- --with-pam=/lib/$(DEB_HOST_MULTIARCH)/security \
-			 --sysconfdir=/etc/security
+			 --sysconfdir=/etc/security \
+			 --includedir=\$${prefix}/include/duo
 
 # Disable testsuite completely -- it is very broken on buildds
 override_dh_auto_test:


Bug#900848: Should this package be removed?

2018-06-08 Thread Moritz Mühlenhoff
retitle 900848 RM: skipfish -- RoM; dead upstream, RC-buggy
reassign 900848 ftp.debian.org
severity 900848 normal
thanks

On Fri, Jun 08, 2018 at 08:41:06AM +0200, bart...@fenski.pl wrote:
> Hey Moritz,
> 
> Yeah I think we should remove that package at this point.
> Thanks a lot for taking care of that.

Ack, reassining to ftp.debian.org

Cheers,
Moritz



Bug#885533: jessie-pu: package soundtouch/1.8.0-1+deb8u1

2018-06-08 Thread Adam D. Barratt
Control: tags -1 + confirmed

On Wed, 2017-12-27 at 17:19 +, James Cowgill wrote:
> This soundtouch update fixes 3 no-DSA security bugs: #870854,
> #870856,
> and #870857. I have tested the package on jessie and with the
> attached
> debdiff, soundstretch still works and the proof of concepts for the 3
> security issues behave correctly now.

Please go ahead. Sorry for the long delay.

Regards,

Adam



Bug#885619: jessie-pu: package libextractor/1:1.3-2

2018-06-08 Thread Adam D. Barratt
Control: tags -1 + moreinfo

On Thu, 2017-12-28 at 17:32 +0100, Bertrand Marc wrote:
> Would you allow an update of libextractor 1.3-2 in Jessie to fix
> several minor security issues?
> 7 issues skipped by the security teams:
> 
[...]
>   * CVE-2017-15600  2017-15600>: In GNU Libextractor 1.4, there is a NULL Pointer
> Dereference in the
> EXTRACTOR_nsf_extract_method function of plugins/nsf_extractor.c.
> 

I assume the same issue that Julien raised for the stretch package
applies here.

Regards,

Adam



Bug#887047: jessie-pu: package dh-make-perl/0.84-2+deb8u1

2018-06-08 Thread Adam D. Barratt
Control: tags -1 + confirmed

On Sat, 2018-01-13 at 02:42 +0100, gregor herrmann wrote:
> I've prepared an update for dh-make-perl in jessie which fixes
> #851848.
> 
> The problem is that the Contents files have changed between then and
> now, and dh-make-perl in jessie fails to parse them now. Manfred
> Stock has provides a patch which simply removes the check for the
> "headers", which don't exist in the Contents files anymore, and
> additionally adds tests.
> 

Please go ahead; sorry for the long delay.

Regards,

Adam



Bug#891251: jessie-pu: package cups/1.7.5-11+deb8u3

2018-06-08 Thread Adam D. Barratt
Control: tags -1 + confirmed

On Fri, 2018-02-23 at 20:03 +0100, Didier 'OdyX' Raboud wrote:
> (Mirroring #891142 for stretch):
> 
> CUPS is affected by CVE-2017-18190: remote attackers could execute
> arbitrary
> IPP commands by sending POST requests to the CUPS daemon in
> conjunction with
> DNS rebinding. This was caused by a whitelisted
> "localhost.localdomain" entry.
> 
> According to the Security Team it doesn't warrant a DSA, but still
> makes sense
> to be addressed on Jessie (and Stretch). It was fixed independently
> on wheezy
> already.
> 

Please go ahead; sorry for the delay.

Regards,

Adam



Bug#892032: jessie-pu: package wayland/1.6.0-2

2018-06-08 Thread Adam D. Barratt
Control: tags -1 + confirmed

On Sun, 2018-03-04 at 18:52 +0100, Héctor Orón Martínez wrote:
> Hello,
> 
> 2018-03-04 15:44 GMT+01:00 Emilio Pozuelo Monfort :
> > On 04/03/18 12:46, Héctor Orón Martínez wrote:
> > > 
> > > diff --git a/debian/changelog b/debian/changelog
> > > index 645a4bc..b6409a8 100644
> > > --- a/debian/changelog
> > > +++ b/debian/changelog
> > > @@ -1,3 +1,14 @@
> > > +wayland (1.6.0-2+deb8u1) stretch; urgency=medium
> > 
> > Distribution should be jessie.
> 
> Ouch! Right. Find new version attached

Please go ahead. Sorry for the delay.

Regards,

Adam



Bug#901088: gnupg1: CVE-2018-12020: filename sanitization problem in GnuPG

2018-06-08 Thread Salvatore Bonaccorso
Source: gnupg1
Version: 1.4.21-4
Severity: grave
Tags: patch security upstream
Justification: user security hole
Forwarded: https://dev.gnupg.org/T4012

Hi,

The following vulnerability was published for gnupg1. I'm aware this
is only the legacy packages, the issue though is present there and not
having the fix in buster will later on represent a regression from
updates from stretch. Thus the RC severity as well as reasoning.

CVE-2018-12020[0]:
filename sanitization problem in GnuPG

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-12020
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12020
[1] https://dev.gnupg.org/T4012

Regards,
Salvatore



Bug#879012: I guess "release a=now" superseded 'origin ""'?

2018-06-08 Thread Ralph, Kenyon [US] (MS)
Indeed, "release a=now" seems to have superseded 'origin ""' for matching 
locally-installed packages. Using origin with an empty string is shown twice in 
apt_preferences(5), but it appears to not work anymore, whereas "release a=now" 
does work.

-- 
Kenyon Ralph



Bug#901087: libcatalyst-plugin-session-store-dbi-perl: FTBFS: Base class package "Class::Data::Inheritable" is empty.

2018-06-08 Thread Niko Tyni
Source: libcatalyst-plugin-session-store-dbi-perl
Version: 0.16-2 
Severity: serious
Tags: buster sid

This package fails to build on current sid/amd64.  The autopkgtest
checks are broken too, though ci.debian.net hasn't noticed yet (seems
wedged somehow?)

It looks like it's just missing an explicit build and runtime dependency
on libclass-data-inheritable-perl. It was probably pulled in earlier by
libcatalyst-perl which dropped it in 5.90118-1:

 
https://salsa.debian.org/perl-team/modules/packages/libcatalyst-perl/commit/ba916b4447ac328c13f1fa872e9fd00fd8508e2c

   dh_auto_test
dh_auto_test: Compatibility levels before 9 are deprecated (level 8 in use)
make -j1 test TEST_VERBOSE=1
make[1]: Entering directory '/<>'
PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" 
"-e" "undef *Test::Harness::Switches; test_harness(1, 'inc', 'blib/lib', 
'blib/arch')" t/01use.t t/02pod.t t/03podcoverage.t t/04critic.t t/04dbi.t 
t/05cdbi.t t/06dbic.t t/07dbic_schema.t

#   Failed test 'use Catalyst::Plugin::Session::Store::DBI;'
#   at t/01use.t line 3.
# Tried to use 'Catalyst::Plugin::Session::Store::DBI'.
# Error:  Base class package "Class::Data::Inheritable" is empty.
# (Perhaps you need to 'use' the module which defines that package first,
# or make that module available in @INC (@INC contains: 
/<>/inc /<>/blib/lib /<>/blib/arch 
/etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.26.2 
/usr/local/share/perl/5.26.2 /usr/lib/x86_64-linux-gnu/perl5/5.26 
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .).
#  at /<>/blib/lib/Catalyst/Plugin/Session/Store/DBI.pm line 5.
# BEGIN failed--compilation aborted at 
/<>/blib/lib/Catalyst/Plugin/Session/Store/DBI.pm line 5.
# Compilation failed in require at t/01use.t line 3.
# BEGIN failed--compilation aborted at t/01use.t line 3.
# Looks like you failed 1 test of 1.
t/01use.t .. 
1..1
not ok 1 - use Catalyst::Plugin::Session::Store::DBI;
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/1 subtests 
t/02pod.t .. skipped: Test::Pod 1.14 required
t/03podcoverage.t .. skipped: Test::Pod::Coverage 1.04 required
t/04critic.t ... skipped: Critic test only for developers.
t/04dbi.t .. skipped: Catalyst::Plugin::Session::State::Cookie is 
required for this test
t/05cdbi.t . skipped: Catalyst::Plugin::Session::State::Cookie is 
required for this test
t/06dbic.t . skipped: Catalyst::Plugin::Session::State::Cookie is 
required for this test
t/07dbic_schema.t .. skipped: Catalyst::Plugin::Session::State::Cookie is 
required for this test

Test Summary Report
---
t/01use.t(Wstat: 256 Tests: 1 Failed: 1)
  Failed test:  1
  Non-zero exit status: 1
Files=8, Tests=1,  1 wallclock secs ( 0.04 usr  0.01 sys +  0.47 cusr  0.05 
csys =  0.57 CPU)
Result: FAIL

-- 
Niko Tyni   nt...@debian.org



Bug#895935: jessie-pu: package patch/2.7.5-1+deb8u1

2018-06-08 Thread Adam D. Barratt
Control: tags -1 + confirmed

On Tue, 2018-04-17 at 17:45 +0200, Laszlo Boszormenyi (GCS) wrote:
> I'd like to fix CVE-2018-1000156 in patch for Jessie, which is an
> arbitrary command execution in ed-style patches.
> While it might be used for remote compromise, it would need a setup
> to
> accept patches unconditionally. But then an attacker has an easy path
> already to insert vulnerable code to source files or JavaScript
> injection to HTML pages, etc. Hence it doesn't warrant a DSA on its
> own, but would be good to fix in a point release.
> 

Please go ahead.

Regards,

Adam



Bug#893507: jessie-pu: package reportbug/6.6.3+deb8u1

2018-06-08 Thread Adam D. Barratt
Control: tags -1 + confirmed

On Mon, 2018-03-19 at 14:39 +0100, Salvatore Bonaccorso wrote:
> This is the corresponding request to #891918 but for jessie-pu.
> 
> I like to propose the following little change for the upcoming point
> release to include for reportbug. The secure testing security team
> does not exists for a long time by now, and when alioth will be
> decomissioned the secure-testing-team list will disapear. Cf.
> #32.
> 
> It would thus be good if reportbug stops Cc'ing the secure-testing
> team.
> 

Please go ahead; sorry for the delay.

Regards,

Adam



Bug#899014: jessie-pu: package blktrace/1.0.5-1

2018-06-08 Thread Adam D. Barratt
Control: tags -1 + confirmed

On Fri, 2018-05-18 at 21:13 +0200, Bas Zoetekouw wrote:
> Hi!
> 
> > Please use 1.0.5-1+deb8u1 and as target distribution just 'jessie'.
> > Use 1.1.0-2+deb9u1 and targeting 'stretch' instead (not
> > stretch-security).
> > 
> 
> Fixed.  New debdiffs follow:
> 

Please go ahead.

Regards,

Adam



Bug#736126: Please install haveged on physical machines

2018-06-08 Thread Holger Levsen
Hi nicoo,

On Fri, Jun 08, 2018 at 09:27:10PM +0200, Nicolas Braud-Santoni wrote:
> On virtual machines, however, the data that the HAVEGE algorithm produces
> is not necessarily unpredictable [1]; hence, we shouldn't install haveged
> on those environments.
 
interesting, thanks! sadly it doesnt say which virtualisation environments
were/are affected.
 

-- 
cheers,
Holger


signature.asc
Description: PGP signature


Bug#900581: linux: Enable Buster kernel features for newer ARM64 servers.

2018-06-08 Thread Geoff Levand
On 06/05/2018 12:28 AM, Ian Campbell wrote:
> On Tue, 2018-06-05 at 02:14 +0100, Ben Hutchings wrote:
> 
>> I don't think it's OK to cause a regression like this.  Since this is
>> problem affects a specific known platform, the driver ought to
>> recognise it and disable itself automatically.
> 
> Indeed, while the Fedora bug upthread claims such a patch wouldn't be
> upstreamable, AFAIK it is not uncommon to have such quirks for broken
> firmware based upon DMI identifiers or similar.

Just to mention it, Mark Salter submitted one of the work-around patches
for the m400 firmware.  The reply from the ACPI maintainer wasn't very
encouraging. See:

  https://lkml.org/lkml/2018/4/19/1020 (ACPI / scan: Fix regression related to 
X-Gene UARTs)

CONFIG_ACPI_APEI allows for automated error reporting, so it is something
that is very desirable for unattended servers in a production environment.
Mark sent me a minimal patch that allows CONFIG_ACPI_APEI to work on m400.
I've attached a patch that puts his patch into the kernel patch series.  

  arm64-Add-fix-for-broken-HPE-moonshot-ACPI-APEI-supp.patch

Is this an acceptable solution?
>From e2bbf7bd8ef0231dcaa440a5baa8722a11634f75 Mon Sep 17 00:00:00 2001
From: Geoff Levand 
Date: Fri, 8 Jun 2018 10:52:29 -0700
Subject: [PATCH] [arm64] Add fix for broken HPE moonshot ACPI-APEI support

Signed-off-by: Geoff Levand 
---
 ...4-Ignore-broken-HPE-moonshot-APEI-support.patch | 39 ++
 debian/patches/series  |  1 +
 2 files changed, 40 insertions(+)
 create mode 100644 debian/patches/bugfix/arm64/ACPI-APEI-arm64-Ignore-broken-HPE-moonshot-APEI-support.patch

diff --git a/debian/patches/bugfix/arm64/ACPI-APEI-arm64-Ignore-broken-HPE-moonshot-APEI-support.patch b/debian/patches/bugfix/arm64/ACPI-APEI-arm64-Ignore-broken-HPE-moonshot-APEI-support.patch
new file mode 100644
index ..ca7a7bf67258
--- /dev/null
+++ b/debian/patches/bugfix/arm64/ACPI-APEI-arm64-Ignore-broken-HPE-moonshot-APEI-support.patch
@@ -0,0 +1,39 @@
+From 2c4be2497e1cdbeaeee2decd9f85bfd9926d0321 Mon Sep 17 00:00:00 2001
+From: Mark Salter 
+Date: Tue, 27 Feb 2018 00:21:23 -0500
+Subject: [PATCH] ACPI: APEI: arm64: Ignore broken HPE moonshot APEI support
+
+The aarch64 HP moonshot platforms have a firmware bug which causes a
+spurious fatal memory error via APEI at boot time. This platform is no
+longer supported and no further firmware updates are expected. This is
+a downstream-only hack to avoid the problem by bailing out of HEST
+table probing if we detect a moonshot HEST table.
+
+Signed-off-by: Mark Salter 
+Signed-off-by: Geoff Levand 
+---
+ drivers/acpi/apei/hest.c | 8 
+ 1 file changed, 8 insertions(+)
+
+diff --git a/drivers/acpi/apei/hest.c b/drivers/acpi/apei/hest.c
+index 9cb74115a43d..9305daabe24c 100644
+--- a/drivers/acpi/apei/hest.c
 b/drivers/acpi/apei/hest.c
+@@ -89,6 +89,14 @@ int apei_hest_parse(apei_hest_func_t func, void *data)
+ 	if (hest_disable || !hest_tab)
+ 		return -EINVAL;
+ 
++#ifdef CONFIG_ARM64
++	/* Ignore broken firmware */
++	if (!strncmp(hest_tab->header.oem_id, "HPE   ", 6) &&
++	!strncmp(hest_tab->header.oem_table_id, "ProLiant", 8) &&
++	MIDR_IMPLEMENTOR(read_cpuid_id()) == ARM_CPU_IMP_APM)
++		return -EINVAL;
++#endif
++
+ 	hest_hdr = (struct acpi_hest_header *)(hest_tab + 1);
+ 	for (i = 0; i < hest_tab->error_source_count; i++) {
+ 		len = hest_esrc_len(hest_hdr);
+-- 
+2.14.1
+
diff --git a/debian/patches/series b/debian/patches/series
index cb1d40074141..d77fa2bf4faf 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -68,6 +68,7 @@ bugfix/x86/perf-tools-fix-unwind-build-on-i386.patch
 bugfix/sh/sh-boot-do-not-use-hyphen-in-exported-variable-name.patch
 bugfix/x86/mmap-remember-the-map_fixed-flag-as-vm_fixed.patch
 bugfix/x86/mmap-add-an-exception-to-the-stack-gap-for-hotspot-jvm.patch
+bugfix/arm64/ACPI-APEI-arm64-Ignore-broken-HPE-moonshot-APEI-support.patch
 
 # Arch features
 features/mips/MIPS-increase-MAX-PHYSMEM-BITS-on-Loongson-3-only.patch
-- 
2.14.1



Bug#901085: libur-perl: FTBFS with Perl 5.28: test failures

2018-06-08 Thread Niko Tyni
On Fri, Jun 08, 2018 at 10:18:49PM +0300, Niko Tyni wrote:
> Source: libur-perl
> Version: 0.450-1
> Severity: important
> User: debian-p...@lists.debian.org
> Usertags: perl-5.28-transition
> 
> This package fails to build with Perl 5.28 (currently in experimental.)
> 
>   
> http://perl.debian.net/rebuild-logs/perl-5.28-throwaway/libur-perl_0.450-1/libur-perl_0.450-1_amd64-2018-06-08T17:53:04Z.build
> 
>   #   Failed test 'Response excpetion correctly reflects calling an undefined 
> function'
>   #   at t/URT/t/41_rpc_basic.t line 103.
>   # Looks like you failed 1 test of 40.
> 
> [...]
> 
>   #   Failed test 'Response excpetion correctly reflects calling an undefined 
> function'
>   #   at t/URT/t/42_rpc_between_processes.t line 126.
>   # Looks like you failed 1 test of 35.

These parts seem to be

 https://github.com/genome/UR/issues/136

>   #   Failed test 'content matches!'
>   #   at t/URT/t/63c_view_with_subviews.t line 151.
>   #  got: '{
>   #"id" : "Acme::Cat/And/owner_id/O:\u001dO:111\u001e",
>   #"members" : [
>   #   {
>   #  "id" : 222
>   #   },
>   #   {
>   #  "id" : 333
>   #   }
>   #]
>   # }
>   # '
>   # expected: '{
>   #"id" : "Acme::Cat/And/owner_id/O:\u001dO:111\u001e",
>   #"members" : [
>   #   {
>   #  "id" : "222"
>   #   },
>   #   {
>   #  "id" : "333"
>   #   }
>   #]
>   # }
>   # '

This looks similar to #901082 and doesn't seem to show in the CPAN
test reports. I wonder what's different for us.
-- 
Niko



Bug#736126: Please install haveged on physical machines

2018-06-08 Thread Nicolas Braud-Santoni
Hi Holger,

On Thu, May 24, 2018 at 09:06:27AM +, Holger Levsen wrote:
> > > Do we have a reasonablish way of telling whether a system is “real”
> > > hardware or a virtual machine, and choose whether to install haveged or 
> > > not
> > > accordingly?
>
> why only install it on physical machines? IME haveged is useful on real
> *and* virtual machines.

Regardless of the platform, haveged will put data into random(4) and use
the appropriate ioctl to increase the entropy counter, which is useful in
that it prevents random(4) from “running out” of entropy. [0]


On virtual machines, however, the data that the HAVEGE algorithm produces
is not necessarily unpredictable [1]; hence, we shouldn't install haveged
on those environments.

Moreover, on virtual machines, the host virtualization system should provide
entropy to its guests, for instance through virtio-rng (which can be picked
up with rngd).


TL;DR: On VMs, haveged might be unsafe, depending on the virtualization
   environment's configuration, and we (d-i/tasksel) do not have enough
   information available to make that call.


Best,

  nicoo


[0]: Gods, this is painful to write. There is no reason for random(4) to
 ever “run out” of entropy once initialized, but for some
 misconceptions about cryptography; however, this is the implemented
 behaviour and we kinda have to live with it for now.

[1]: 
https://tls.mbed.org/tech-updates/security-advisories/polarssl-security-advisory-2011-02
 is an example of the same algorithm failing on VMs.



Bug#901086: RFP: node-fibers -- Fiber/coroutine support for v8 and node

2018-06-08 Thread Jeff Cliff
Package: wnpp
Severity: wishlist

* Package name: node-fibers
  Version : 2.0.0
  Upstream Author : Marcel Laverdet
* URL : https://notabug.org/themusicgod1/node-fibers
* License : MIT
  Programming Lang: Javascript
  Description : Fiber/coroutine support for v8 and node

Fibers, sometimes called coroutines, are a powerful tool which expose an API to 
jump between multiple
call stacks from within a single thread. This can be useful to make code 
written for a synchronous
library play nicely in an asynchronous environment.



Bug#901085: libur-perl: FTBFS with Perl 5.28: test failures

2018-06-08 Thread Niko Tyni
Source: libur-perl
Version: 0.450-1
Severity: important
User: debian-p...@lists.debian.org
Usertags: perl-5.28-transition

This package fails to build with Perl 5.28 (currently in experimental.)

  
http://perl.debian.net/rebuild-logs/perl-5.28-throwaway/libur-perl_0.450-1/libur-perl_0.450-1_amd64-2018-06-08T17:53:04Z.build

  #   Failed test 'Response excpetion correctly reflects calling an undefined 
function'
  #   at t/URT/t/41_rpc_basic.t line 103.
  # Looks like you failed 1 test of 40.

[...]

  #   Failed test 'Response excpetion correctly reflects calling an undefined 
function'
  #   at t/URT/t/42_rpc_between_processes.t line 126.
  # Looks like you failed 1 test of 35.

[...]

  #   Failed test 'content matches!'
  #   at t/URT/t/63c_view_with_subviews.t line 151.
  #  got: '{
  #"id" : "Acme::Cat/And/owner_id/O:\u001dO:111\u001e",
  #"members" : [
  #   {
  #  "id" : 222
  #   },
  #   {
  #  "id" : 333
  #   }
  #]
  # }
  # '
  # expected: '{
  #"id" : "Acme::Cat/And/owner_id/O:\u001dO:111\u001e",
  #"members" : [
  #   {
  #  "id" : "222"
  #   },
  #   {
  #  "id" : "333"
  #   }
  #]
  # }
  # '

[...]

  Test Summary Report
  ---
  t/URT/t/41_rpc_basic.t  
(Wstat: 256 Tests: 40 Failed: 1)
Failed test:  27
Non-zero exit status: 1
  t/URT/t/42_rpc_between_processes.t  
(Wstat: 256 Tests: 35 Failed: 1)
Failed test:  24
Non-zero exit status: 1
  t/URT/t/63c_view_with_subviews.t
(Wstat: 512 Tests: 23 Failed: 2)
Failed tests:  11, 19
Non-zero exit status: 2
  Files=273, Tests=7420, 145 wallclock secs ( 0.96 usr  0.30 sys + 125.43 cusr  
8.59 csys = 135.28 CPU)
  Result: FAIL
 
-- 
Niko Tyni   nt...@debian.org



Bug#901062: qtbase5-dev: qtbase5-dev: QFile::exists() returns false for existing files?!

2018-06-08 Thread Wearenotalone
Found the bug.

Docker uses seccomp security profiles to restrict e.g. system calls [1].
In docker 17.05 system call "statx" is blocked [2][3], in trunk and in
18.04 which is not released yet that system call will be allowed [4][5].
By running the docker container with "--security-opt seccomp=unconfined"
or "--privileged" the system call "statx" not blocked [5] and everything
works as excepted: QFile::exists() returns true for existing files.

Older revisions of QFile (e.g. qt 5.7 from debian stretch) do work as
excepted even when statx is blocked, because they do not use system call
"statx".

That system call is not necessary to find out if a file exists. Qt is
able to detect whether "statx" is supported. But it fails to detect that
its call is not permitted. The reason for that is in
src/corelib/io/qfilesystemengine_unix.cpp which is still present in
latest upstream revision [6]. But lets start from the beginning:

QFile::exists() returns true if ExistsFlag is set [7]. Attributes are
set in "QFSFileEnginePrivate::doStat" [10]. This function first reads
attributes with 2-args-function-overload
"QFileSystemEngine::fillMetaData" [11] and then loads the missing
attributes with 3-args-function-overload
"QFileSystemEngine::fillMetaData" [12]. Boths overloads suffer from the
same bug.

The 2-args-overload "bool QFileSystemEngine::fillMetaData(int fd,
QFileSystemMetaData )" [11] calls "qt_fstatx". QtCore in debian sid
was build with a kernel that supports the statx system call and thus
function "qt_fstatx" does indeed call "syscall(SYS_statx, ...)". If this
syscall is blocked, then "syscall(...)" returns -1 and errno is set to 1
(EPERM == "Operation not permitted") [13]. Back in
"QFileSystemEngine::fillMetaData" [11] look at this code snippet:

  int ret = qt_fstatx(fd, );
  if (ret != -ENOSYS) {
  if (ret == 0) {
  data.fillFromStatxBuf(statxBuffer);
  return true;
  }
  return false;
  }

If statx is blocked, then ret==-EPERM (negated in [14]), which means
"return false" is executed, thus no attributes are read.

"QFSFileEnginePrivate::doStat" now executes the 3-args-overload "bool
QFileSystemEngine::fillMetaData(const QFileSystemEntry ,
QFileSystemMetaData , QFileSystemMetaData::MetaDataFlags what)"
[12]. It contains this snippet:

  statResult = qt_lstatx(nativeFilePath, );
  if (statResult == -ENOSYS) {
  //...
  } else if (statResult == 0) {
  //...
  }
 
  if (statResult >= 0) {
  //...
  } else {
  // it doesn't exist
  entryErrno = errno;
  data.knownFlagsMask |= QFileSystemMetaData::ExistsAttribute;
  }

When statx is blocked then statResult is -1 (-EPERM) and thus last
branch is executed. Thus 3-args-overload of fillMetaData says "i know
that file does not exist" (knownFlagsMask has ExistsAttribute but
entryFlags has not). The code "data.entryFlags |= flag |
QFileSystemMetaData::ExistsAttribute;" later in that function [16] is
never executed because entryErrno equals -1 (-EPERM).

Thus QFile always returns false, for all files, even existing once, as
long as statx is supported but blocked via e.g. seccomp.

Cheers,
Jakob


[1] https://github.com/Microsoft/docker/blob/master/docs/security/seccomp.md
[2] debian package "docker-engine" currently available for stretch is
17.05.0~ce-0~debian-stretch
[3] https://github.com/moby/moby/blob/17.05.x/profiles/seccomp/default.json
[4] https://github.com/moby/moby/blob/master/profiles/seccomp/default.json
[5] https://github.com/docker/for-linux/issues/208
[6]
https://code.qt.io/cgit/qt/qtbase.git/tree/src/corelib/io/qfilesystemengine_unix.cpp
[7] https://code.qt.io/cgit/qt/qtbase.git/tree/src/corelib/io/qfile.cpp#n425
[8] -DELETED-
[9] -DELETED-
[10]
https://code.qt.io/cgit/qt/qtbase.git/tree/src/corelib/io/qfsfileengine_unix.cpp#n419
[11]
https://code.qt.io/cgit/qt/qtbase.git/tree/src/corelib/io/qfilesystemengine_unix.cpp#n439
[12]
https://code.qt.io/cgit/qt/qtbase.git/tree/src/corelib/io/qfilesystemengine_unix.cpp#n931
[13] /usr/include/asm-generic/errno-base.h
[14]
https://code.qt.io/cgit/qt/qtbase.git/tree/src/corelib/io/qfilesystemengine_unix.cpp#n350
[15]
https://code.qt.io/cgit/qt/qtbase.git/tree/src/corelib/io/qfilesystemengine_unix.cpp#n979
[16]
https://code.qt.io/cgit/qt/qtbase.git/tree/src/corelib/io/qfilesystemengine_unix.cpp#n1053

Am 08.06.2018 um 20:54 schrieb Dmitry Shachnev:
> Hi Jakob!
>
> On Fri, Jun 08, 2018 at 04:01:54PM +0200, Wearenotalone wrote:
>> did a fresh install of debian sid within docker and stumbled upon this
>> bug in QFile:
>> QFile's method exists() returns false even if that file exists.
> Thanks for your bug report and the test case.
>
> Can you please obtain strace of your example and attach it?
> I am not able to reproduce this issue, but I would like to compare yours
> and mine strace outputs.
>
> --
> Dmitry Shachnev



Bug#901084: flightgear: "install downloaded scenery" tool needs support for zip files

2018-06-08 Thread Pavel Kreuzt
Package: flightgear
Version: 1:2018.1.1+dfsg-3
Severity: normal

Dear Maintainer,

In launcher mode, there is a tool to "install (manually) downloaded scenery" 
from FlightGear site. This tools expects to find tar, gz or tgz files, but 
Scenery Download site serves zip files, which are not recognized. This renders 
the tool useless and scenery needs to be manually extracted to the correct 
place.


-- System Information:
Release:Buster
Architecture:   x86_64

Versions of packages flightgear depends on:
ii  flightgear-data-all1:2018.1.1+dfsg-2
ii  libc6  2.27-3
ii  libcurl3-gnutls7.60.0-2
ii  libdbus-1-31.12.8-2
ii  libexpat1  2.2.5-3
ii  libflite1  2.1-release-2
ii  libgcc11:8.1.0-5
ii  libgl1 1.0.0+git20180308-3
ii  libgsm11.0.13-4+b2
ii  libhtsengine1  1.10-3
ii  libopenal1 1:1.18.2-3
ii  libopenscenegraph-3.4-131  3.4.1+dfsg1-3+b1
ii  libopenthreads20   3.2.3+dfsg1-2+b8
ii  libplib1   1.8.5-8
ii  libqt5core5a   5.10.1+dfsg-7
ii  libqt5gui5 5.10.1+dfsg-7
ii  libqt5network5 5.10.1+dfsg-7
ii  libqt5qml5 [qtdeclarative-abi-5-10-1]  5.10.1-4
ii  libqt5quick5   5.10.1-4
ii  libqt5quickwidgets55.10.1-4
ii  libqt5widgets5 5.10.1+dfsg-7
ii  libspeex1  1.2~rc1.2-1+b2
ii  libspeexdsp1   1.2~rc1.2-1+b2
ii  libsqlite3-0   3.23.1-1
ii  libstdc++6 8.1.0-5
ii  libudev1   238-5
ii  libudns0   0.4-1+b1
ii  libx11-6   2:1.6.5-1
ii  qml-module-qtquick-window2 5.10.1-4
ii  qml-module-qtquick25.10.1-4
ii  zlib1g 1:1.2.11.dfsg-1

Versions of packages flightgear recommends:
ii  flightgear-phi  2018.1.1+dfsg1-1

flightgear suggests no packages.

-- no debconf information



Bug#898336: hpwdt NMI kernel crash on shutdown/reboot

2018-06-08 Thread Russell Mosemann

Package: src:linux
Version: 4.16.12-1~bpo9+1
Severity: important

 
[  OK  ] Stopped Remount Root and Kernel File Systems.
[  OK  ] Reached target Shutdown.
[ 1125.048758] hpwdt: Unexpected close, not stopping watchdog!
[ 1129.467546] Kernel panic - not syncing: An NMI occurred. Depending on your 
system the reason for the NMI is logged in any one of the following resources:
[ 1129.467546] 1. Integrated Management Log (IML)
[ 1129.467546] 2. OA Syslog
[ 1129.467546] 3. OA Forward Progress Log
[ 1129.467546] 4. iLO Event Log
[ 1129.467551] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.16.0-0.bpo.2-amd64 
#1 Debian 4.16.12-1~bpo9+1
[ 1129.467553] Hardware name: HP ProLiant DL380p Gen8, BIOS P70 02/10/2014
[ 1129.467554] Call Trace:
[ 1129.467559]  
[ 1129.467569]  dump_stack+0x5c/0x85
[ 1129.467575]  panic+0xe4/0x252
[ 1129.467581]  nmi_panic+0x35/0x40
[ 1129.467587]  hpwdt_pretimeout+0x27/0x48 [hpwdt]
[ 1129.467591]  nmi_handle+0x72/0x120
[ 1129.467594]  io_check_error+0x16/0x90
[ 1129.467597]  default_do_nmi+0xa2/0x100
[ 1129.467600]  do_nmi+0xe5/0x130
[ 1129.467604]  end_repeat_nmi+0x16/0x50
[ 1129.467610] RIP: 0010:intel_idle+0x76/0x120
[ 1129.467612] RSP: 0018:a9403e50 EFLAGS: 0046
[ 1129.467615] RAX: 0030 RBX: 0030 RCX: 0001
[ 1129.467617] RDX:  RSI: a94b2ba0 RDI: 
[ 1129.467618] RBP: 0005 R08: 0f05 R09: 0018
[ 1129.467620] R10: 0c62 R11: 0f05 R12: a94b2d98
[ 1129.467621] R13: 0005 R14: 0005 R15: 0106b559f2b2
[ 1129.467628]  ? intel_idle+0x76/0x120
[ 1129.467631]  ? intel_idle+0x76/0x120
[ 1129.467633]  
[ 1129.467638]  cpuidle_enter_state+0x72/0x2b0
[ 1129.467643]  do_idle+0x193/0x200
[ 1129.467646]  cpu_startup_entry+0x6f/0x80
[ 1129.467652]  start_kernel+0x458/0x478
[ 1129.467658]  secondary_startup_64+0xa5/0xb0
[ 1129.467748] Kernel Offset: 0x2740 from 0x8100 (relocation 
range: 0x8000-0xbfff)
[ 1130.244043] ---[ end Kernel panic - not syncing: An NMI occurred. Depending 
on your system the reason for the NMI is logged in any one of the following 
resources:
[ 1130.244043] 1. Integrated Management Log (IML)
[ 1130.244043] 2. OA Syslog
[ 1130.244043] 3. OA Forward Progress Log
[ 1130.244043] 4. iLO Event Log


  1   2   3   >