Bug#889717:

2018-02-07 Thread Akash mazumder
Package: installation-reports

Seems like it won't allow attachments so here is the raw text.

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Akash Mazumder 
To: Debian Bug Tracking System 
Subject: installation-reports: Successful installed dual boot on UEFI,
but laptop boots directly to windows 10
Message-ID: <151790716743.5533.8006320745762086275.reportbug@debian>
X-Mailer: reportbug 7.1.7
Date: Tue, 06 Feb 2018 14:22:47 +0530

Package: installation-reports
Severity: normal

Dear Maintainer,

   * What led up to the situation?
Dual Boot Debian with Win10, with win10 already installed.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
1.Plugged in USB pendrive.
2.I get the options which were on the lines of "boot from USB flash
drive" and "boot from USB Flash drive(UEFI)"
3.I choose the UEFI option (i.e the second one)
   *What was the outcome of this action?
Installer installs normally, but when I boot up it directly logs me
into Win10. I have manually select F9 and choose my boot option
[something like UEFI Operating system(Debian) I don't exactly recall
the options]. Then I'm shown the GRUB menu. Everything else is fine.
   * What outcome did you expect instead?
GRUB menu asking me to select the OS that I want to Boot.


-- Package-specific info:

Boot method: USB Flash Drive
Image version: debian-9.3.0-amd64-DVD-1.iso.torrent
link:https://cdimage.debian.org/debian-cd/current/amd64/bt-dvd/debian-9.3.0-amd64-DVD-1.iso.torrent
Date: About 7-10 days prior to this installation report

Machine: HP Notebook - 15-bs579tx
Partitions:
Filesystem Type 1K-blocks Used Available Use% Mounted on
udev   devtmpfs   40356080   4035608   0% /dev
tmpfs  tmpfs   809472 9552799920   2% /run
/dev/sda8  ext4  47799020  4548516  40792700  11% /
tmpfs  tmpfs  404734029096   4018244   1% /dev/shm
tmpfs  tmpfs 51204  5116   1% /run/lock
tmpfs  tmpfs  40473400   4047340   0% /sys/fs/cgroup
/dev/sda9  ext4 191197068 22602300 158812752  13% /home
/dev/sda2  vfat 9830425461 72843  26% /boot/efi
tmpfs  tmpfs   809468   12809456   1% /run/user/1000



Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[E]
Configure network:  [O]
Detect CD:  [ ]
Load installer modules: [ ]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[O]

Comments/Problems:

The base install was all good. But I have a Realtek RTL8723de network
card. So WiFi didn't work out of the box. Had to DKMS the downloaded
driver/firmware from the official repo on github.
I'm not technically knowlegdeable but r/debian and a few internet
searches helped. The WiFi signal is low though: I get 60-50% even when
I'm sitting beside the router.
As metioned in the report above, the GRUB doesn't let me choose the OS
by default.
I could use some help there, it is alright though, I boot manually;
but would love an alternative.
First time using linux, so don't know if this is correct.

Would like to thank the maintainers and the community for this wonderful Distro.
-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="9 (stretch) - installer build 20170615+deb9u2+b1"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux debian 4.9.0-4-amd64 #1 SMP Debian 4.9.65-3
(2017-12-03) x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Skylake Host
Bridge/DRAM Registers [8086:1904] (rev 08)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:8329]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel
Corporation HD Graphics 520 [8086:1916] (rev 07)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:8329]
lspci -knn: 00:04.0 Signal processing controller [1180]: Intel
Corporation Skylake Processor Thermal Subsystem [8086:1903] (rev 08)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:8329]
lspci -knn: 00:08.0 System peripheral [0880]: Intel Corporation
Skylake Gaussian Mixture Model [8086:1911]

Bug#884001: Severe graphics corruption on intel graphics since linux-image-4.9.0-4-amd64

2018-02-07 Thread Narcis Garcia
Debian 9 (amd64) with Gnome in a notebook "HP TPN-C125"

$ lspci -k
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 5500
(rev 09)
Subsystem: Hewlett-Packard Company HD Graphics 5500
Kernel driver in use: i915
Kernel modules: i915
$ lspci -Q -k
00:02.0 Class 0300: Device 8086:1616 (rev 09)
Subsystem: Device 103c:81ef
Kernel driver in use: i915
Kernel modules: i915

Debian Live (amd64-Gnome) 9.0 -> all fine (Linux 4.9.0-3)
Debian Live (amd64-Gnome) 9.3 -> shifting, flick, black (Linux 4.9.0-4)
Debian installed updated -> shifting, flick, black (Linux 4.9.0-5)
Debian installed downgraded -> shifting, flick, black (Linux 4.9.0-4)
Debian installed downgraded -> all fine (Linux 4.9.0-3)

Current workaround for me:
$ sudo apt-get install linux-image-4.9.0-3-amd64
$ sudo apt-get remove linux-image-amd64 linux-image-4.9.0-5-amd64
$ sudo apt-get remove linux-image-4.9.0-4-amd64

-- 


__
I'm using this express-made address because personal addresses aren't
masked enough at this mail public archive. Public archive administrator
should fix this against automated addresses collectors.



Bug#889717: Package: installation-reports

2018-02-07 Thread Akash mazumder
Package: installation-reports

Seems like I messed up again. Here is the installation-reports.bug file.

cheers.



Bug#889653: netdata: missing python module 'pyyaml2'

2018-02-07 Thread Thomas Leuxner
* Guillaume Clercin  2018.02.07 12:13:

> netdata@kazoo:/usr/lib/x86_64-linux-gnu/netdata$ ./plugins.d/python.d.plugin 
> 1 debug trace mdstat
> Traceback (most recent call last):
>   File "./plugins.d/python.d.plugin", line 31, in 
> from bases.loaders import ModuleAndConfigLoader
>   File 
> "/usr/lib/x86_64-linux-gnu/netdata/python.d/python_modules/bases/loaders.py", 
> line 15, in 
> from pyyaml2 import SafeLoader as YamlSafeLoader
> ImportError: No module named pyyaml2
> 
> According the file 
> "/usr/lib/x86_64-linux-gnu/netdata/python.d/python_modules/bases/loaders.py",
> python2 module require pyyaml2 and python3 module require pyyaml3.
> 
> Import thing, I modified 
> "/usr/lib/x86_64-linux-gnu/netdata/plugins.d/python.d.plugin"
> in order to fix the path of "PLUGIN_CONFIG_DIR".

I can confirm the python plugins don't work for me either and I'm getting 
similar errors when calling the module manually. The suggested patch however 
doesn't change it for me...

Regards
Thomas


signature.asc
Description: PGP signature


Bug#889871: incorrect file and hash

2018-02-07 Thread nsa spy
incorrect file and hash

my apologies, i provided incorrect information about file and hash.
following is the one i have used (although, bug may be in live image as well).

firmware-9.3.0-amd64-netinst.iso
hash sha256: 6e049662dd10cacd75883889d105d919b33bb8c7c09c9f2617f7783f383e8f91



Bug#889010: should it rather be network online target in the service file?

2018-02-07 Thread Christian Ehrhardt
On Tue, Feb 6, 2018 at 4:47 PM, Vincent Blut  wrote:
> Control: tags -1 moreinfo
>
> Hi Christian,
>
> On Thu, Feb 01, 2018 at 09:43:07AM +0100, Christian Ehrhardt wrote:
>>
>> Package: chrony
>> Version: 3.2-2
>>
>> Description:
>> Conversions of old $network behavior should be on online target [2].
>> And I think for chrony it makes sense to start when it really is
>> online to not rely too much on the hooks to set it online.
>
>
> Prior to the 3.0-1 release, we used to heavily rely on the hooks as the time
> sources weren’t polled by chronyd due to the use of the “offline” option.
> This behaviour wasn’t satisfactory to me, so I decided it was time to change
> it for Debian Stretch so what's happening now is:
>   - If the network is up:
>- chronyd starts
>- chronyc online runs, but doesn't actually do anything
>- names are resolved
>- sources are added as online
>- burst is executed
>
>- If the network is down:
>- chronyd starts
>- chronyc online doesn't run
>- chronyd is periodically trying, in exponentially increasing
> interval, to resolve the pool.ntp.org name, but fails
>- network is up
>- chronyc online runs from the hooks
>- chronyd resolves the name
>- sources are added as online
>- burst is executed
>
> Also, I think chronyd should be started quite early so the clock frequency
> offset is set from the drift file. It should also be noted that when used
> with a reference clock, chronyd does not necessarily need network nor DNS.

Thanks for your explanations Vincent - I think you are right.
We will need to make sure the hooks work for us (=Ubuntu) which might
in some scenarios be an issue but is being worked on.
I agree to keeping it starting as it is right now.
Closing bug ...

> However, if starting chronyd after the network is fully up is something you
> really are looking for, I think you should start it after nss-lookup.target‽
>
>> Ubuntu-Bug: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1746458
>> Fix-in-Review:
>> https://git.launchpad.net/~paelzer/ubuntu/+source/chrony/commit/?id=2baea8e0bde5d6a1de60098019fb658a4a94d489
>>
>> [1]:
>> https://code.launchpad.net/~paelzer/ubuntu/+source/chrony/+git/chrony/+merge/336844
>> [2]: https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/
>>
>> --
>> Christian Ehrhardt
>> Software Engineer, Ubuntu Server
>> Canonical Ltd
>
>
> Cheers,
> Vincent



-- 
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd



Bug#889872: show-ip: load fails: TypeError: Object is NM.IPAddress.prototype, not an object instance - cannot convert to a boxed instance

2018-02-07 Thread Paul Wise
Package: gnome-shell-extension-show-ip
Version: 8-3
Severity: serious

Since the recent upgrade to libnm, I get these errors from gnome-shell
in the systemd user journal. The first line is also present in the
gnome-shell looking-glass interface (run 'lg' in the Alt+F2 dialog).

Extension "show...@sgaraud.github.com" had error: TypeError: Object is 
NM.IPAddress.prototype, not an object instance - cannot convert to a boxed 
instance
((libnm-core/nm-setting-ip-config.c:210)): assertion '' failed
((libnm-core/nm-setting-ip-config.c:210)): assertion '' failed

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

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

Versions of packages gnome-shell-extension-show-ip depends on:
ii  gnome-shell  3.26.2-5

gnome-shell-extension-show-ip recommends no packages.

gnome-shell-extension-show-ip suggests no packages.

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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


Bug#888925: libminc FTBFS with netcdf 1:4.6.0-2: NetCDF: Attempt to use feature that was not turned on when netCDF was built

2018-02-07 Thread Sebastiaan Couwenberg
On 02/08/2018 07:41 AM, Andreas Tille wrote:
>> libminc needs to fix their test or their usage of libnetcdf.
> 
> Could you be more verbose what exactly needs to be changed?

You can skip the test until upstream has provided a fix.

> I admit, I have no idea about libnetcdf and Steve did not responded
> to the issue yet.

libminc passed custom flags to the nccreate() via its micreate() wrapper:

 ip->fd = micreate(ip->name, NC_CLOBBER|MI2_CREATE_V1); /*Create MINC1
format*/

These flags are passed along to nccreate() which is more strict in its
what it accepts.

nccreate() is also part of the legacy V2 API of netCDF, the V3 API and
its nc_create() should be used instead.

Kind Regards,

Bas



Bug#889871: debian-installer loses networking after some time (dhcp-lease?)

2018-02-07 Thread nsa spy
Package: debian-installer
Version: 20170615+deb9u2+b1
Severity: important

debian-installer loses networking after some time (dhcp-lease?).

i hope that version number is correct, i tested debian netinstall 9.3 amd64.
debian-live-9.3.0-amd64-lxde+nonfree.iso
hash sha256: 45eb352681d07c6def0acb3b6606b27b75d5d0fee65bb82308f260ef00e2498d

basically point is, debian installer loses networking when doing installation.
i have very low dhcp-lease, so i suspect it's because of this. at this point
i haven't done any virtual tests about dhcp-lease and i don't have any major
log files to provide.



Bug#888925: libminc FTBFS with netcdf 1:4.6.0-2: NetCDF: Attempt to use feature that was not turned on when netCDF was built

2018-02-07 Thread Andreas Tille
Control: tags -1 help

Hi Bas,

> libminc needs to fix their test or their usage of libnetcdf.

Could you be more verbose what exactly needs to be changed?
I admit, I have no idea about libnetcdf and Steve did not responded
to the issue yet.

Kind regards

   Andreas.

-- 
http://fam-tille.de



Bug#858588: lintian: Classification tag for missing systemd units

2018-02-07 Thread Lucas Nussbaum
On 03/02/18 at 04:00 +0530, Chris Lamb wrote:
> tags 858588 + moreinfo
> thanks
> 
> Hi Lucas,
> 
> > It would be great to add a classification tag in the case where
> > no service file is provided for an init script, even if the maintainer
> > did not make any other effort to make the package work with systemd.
>   ^^
> 
> I can't quite get/parse this bit. :)  As you quote, the code is:

Yeah, it was hard to parse it again for me too :-)

> tag 'systemd-no-service-for-init-script', $basename
>   if (%{$services} and not $services->{$servicename});
> 
> .. but surely this captures the idea of /etc/init.d/foo exists yet
> there is no foo.service?  ie. the systemd unit is missing.
> 
> (It might helpful in a concrete sense to give an example of a package
> that is not being triggered by the above but would be triggered by
> your proposed tag?)

This tag:
https://lintian.debian.org/tags/systemd-no-service-for-init-script.html
is only emitted if:
   there's an init script without a corresponding service file
 AND
   there are other init scripts in the package with a corresponding
   service file

My point is that it would be useful to have a tag emitted when a package
ships an init script without a corresponding service file, regardless of
whether there are other init scripts with a corresponding service file
in the package.

I could even argue that the above tag is misnamed, and should be e.g.
 
systemd-no-service-file-for-init-script-but-other-init-scripts-have-service-file

An example is dictd. It should raise 
   systemd-no-service-file-for-init-script
But not
   
systemd-no-service-file-for-init-script-but-other-init-scripts-have-service-file

Lucas



Bug#889870: libcmocka-dev: mtd-utils unit tests fail on ppc64el

2018-02-07 Thread Balint Reczey
Package: libcmocka-dev
Version: 1.1.1-1
Control: affects -1 mtd-utils

Dear Maintainer,

Unit tests of mtd-utils are failing on ppc64el and it looks like due
to issues in cmocka rather than in ppc64el.
The failures are observable on Ubuntu [1], but they are reprodicible
on Debian as well using the patches in #889868.

Thanks,
Balint

[1] 
https://launchpadlibrarian.net/356161809/buildlog_ubuntu-bionic-ppc64el.mtd-utils_1%3A2.0.1-1ubuntu3_BUILDING.txt.gz

-- 
Balint Reczey
Ubuntu & Debian Developer



Bug#889869: bash: crash in qemu-user: bash: xmalloc: ... cannot allocate XX bytes (0 bytes allocated)

2018-02-07 Thread Adam Borowski
Package: bash
Version: 4.4.18-1
Severity: important

Hi!
I'm afraid that running bash in any qemu-user chroot/container crashes with:
bash: xmalloc: .././locale.c:81: cannot allocate 2 bytes (0 bytes allocated)
or
bash: xmalloc: .././shell.c:1709: cannot allocate 10 bytes (0 bytes allocated)

Happens for any target arch I tried.

This makes bash non-installable (as its postinst is written in bash), and
obviously makes the emulated system pretty much broken.

Alas, gdb can't run binfmt-ed processes; a workaround apparently exists but
it's anything but simple.


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

Kernel: Linux 4.15.2+ (SMP w/6 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)

Versions of packages bash depends on:
ii  base-files   10.1
ii  debianutils  4.8.4
ii  libc62.26-6
ii  libtinfo56.0+20171125-1

Versions of packages bash recommends:
ii  bash-completion  1:2.1-4.3

Versions of packages bash suggests:
pn  bash-doc  

-- no debconf information



Bug#889868: mtd-utils: please enable running unit tests

2018-02-07 Thread Bálint Réczey
Source: mtd-utils
Version: 1:2.0.1-1
Tags: patch

Dear Maintainer,

Please enable running unit tests during the build. The tests are
already enabled in Ubuntu in a slightly different way.

The upstream patches are already upstreamed.

Thanks,
Balint
From d09b0ec4a93d71b23c5688c7451f182077dea4f2 Mon Sep 17 00:00:00 2001
From: Balint Reczey 
Date: Tue, 30 Jan 2018 03:16:07 +0100
Subject: [PATCH 1/6] Enable running tests using cherry-picked upstream commit

---
 ...Run-unit-test-programs-through-make-check.patch | 51 ++
 debian/patches/series  |  1 +
 2 files changed, 52 insertions(+)
 create mode 100644 debian/patches/0001-Run-unit-test-programs-through-make-check.patch
 create mode 100644 debian/patches/series

diff --git a/debian/patches/0001-Run-unit-test-programs-through-make-check.patch b/debian/patches/0001-Run-unit-test-programs-through-make-check.patch
new file mode 100644
index 000..a2b42db
--- /dev/null
+++ b/debian/patches/0001-Run-unit-test-programs-through-make-check.patch
@@ -0,0 +1,51 @@
+From 6766178412934e29db12ff5e6663604c6e909c6e Mon Sep 17 00:00:00 2001
+From: David Oberhollenzer 
+Date: Tue, 5 Dec 2017 13:20:54 +0100
+Subject: [PATCH] Run unit test programs through "make check"
+
+Signed-off-by: David Oberhollenzer 
+---
+ .gitignore| 3 +++
+ Makefile.am   | 2 ++
+ tests/unittests/Makemodule.am | 3 ++-
+ 3 files changed, 7 insertions(+), 1 deletion(-)
+
+--- a/.gitignore
 b/.gitignore
+@@ -127,6 +127,9 @@
+ /include/config.h
+ /include/config.h.in
+ /include/stamp-h1
++test-driver
++*.log
++*.trs
+ 
+ #
+ # Top-level generic files
+--- a/Makefile.am
 b/Makefile.am
+@@ -16,6 +16,7 @@
+ 
+ sbin_PROGRAMS =
+ sbin_SCRIPTS =
++check_PROGRAMS =
+ noinst_LIBRARIES =
+ noinst_PROGRAMS =
+ noinst_SCRIPTS =
+@@ -24,6 +25,7 @@
+ dist_man1_MANS =
+ dist_man8_MANS =
+ 
++TESTS =
+ EXTRA_DIST =
+ 
+ GLOBAL_HEADER = \
+--- a/tests/unittests/Makemodule.am
 b/tests/unittests/Makemodule.am
+@@ -20,4 +20,5 @@
+ 
+ EXTRA_DIST += $(UNITTEST_HEADER) $(UNITTEST_EXTRA)
+ 
+-noinst_PROGRAMS += $(TEST_BINS)
++TESTS += $(TEST_BINS)
++check_PROGRAMS += $(TEST_BINS)
diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 000..3f709ed
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+0001-Run-unit-test-programs-through-make-check.patch
-- 
2.14.1

From 6ab2272a7b32ab4f3c75cba9b91f99c43a521799 Mon Sep 17 00:00:00 2001
From: Balint Reczey 
Date: Tue, 30 Jan 2018 03:20:55 +0100
Subject: [PATCH 2/6] Build-depend on libcmocka-dev

---
 debian/control | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/control b/debian/control
index 48fd393..c0c14de 100644
--- a/debian/control
+++ b/debian/control
@@ -2,7 +2,7 @@ Source: mtd-utils
 Section: utils
 Priority: extra
 Maintainer: Riku Voipio 
-Build-Depends: debhelper (>= 9), pkg-config, dh-autoreconf, zlib1g-dev, libacl1-dev, liblzo2-dev, uuid-dev
+Build-Depends: debhelper (>= 9), pkg-config, dh-autoreconf, zlib1g-dev, libacl1-dev, libcmocka-dev , liblzo2-dev, uuid-dev
 Standards-Version: 3.9.8
 Homepage: http://www.linux-mtd.infradead.org/
 Vcs-Git: https://alioth.debian.org/anonscm/git/collab-maint/mtd-utils.git
-- 
2.14.1

From 806eefc2b3effe1deade5625be1d9fc73b96 Mon Sep 17 00:00:00 2001
From: Balint Reczey 
Date: Tue, 6 Feb 2018 05:33:37 +0700
Subject: [PATCH 3/6] Stop testing stat() calls to let tests succeed

---
 debian/patches/0002-Stop-testing-stat-calls.patch | 79 +++
 debian/patches/series |  1 +
 2 files changed, 80 insertions(+)
 create mode 100644 debian/patches/0002-Stop-testing-stat-calls.patch

diff --git a/debian/patches/0002-Stop-testing-stat-calls.patch b/debian/patches/0002-Stop-testing-stat-calls.patch
new file mode 100644
index 000..2181a8a
--- /dev/null
+++ b/debian/patches/0002-Stop-testing-stat-calls.patch
@@ -0,0 +1,79 @@
+From 2de9f76b500319cd07c480a6b82bb4b085ac4ed3 Mon Sep 17 00:00:00 2001
+From: Balint Reczey 
+Date: Tue, 6 Feb 2018 05:31:32 +0700
+Subject: [PATCH] Stop testing stat() calls
+
+Sometimes __xstat is called instead that makes tests fragile.
+---
+ tests/unittests/Makemodule.am |  2 +-
+ tests/unittests/libmtd_test.c |  2 --
+ tests/unittests/libubi_test.c |  1 -
+ tests/unittests/test_lib.h| 12 
+ 4 files changed, 1 insertion(+), 16 deletions(-)
+
+--- a/tests/unittests/Makemodule.am
 b/tests/unittests/Makemodule.am
+@@ -1,6 +1,6 @@
+ ubilib_test_SOURCES = tests/unittests/libubi_test.c lib/libubi.c
+ ubilib_test_LDADD = $(CMOCKA_LIBS)
+-ubilib_test_LDFLAGS = -Wl,--wrap=open -Wl,--wrap=close -Wl,--wrap=stat -Wl,--wrap=ioctl -Wl,--wrap=read -Wl,--wrap=lseek
++ubilib_test_LDFLAGS = 

Bug#889829: ghc: error while loading shared libraries: libHShaskeline-0.7.3.0-ghc8.0.2.so

2018-02-07 Thread Petter Reinholdtsen
I see this problem too in my sid chroot:

# apt upgrade -y
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  liblivemedia61 libplacebo2
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
E: Can not write log (Is /dev/pts mounted?) - posix_openpt (2: No such file or 
directory)
Setting up ghc (8.0.2-11) ...
/usr/lib/ghc/bin/ghc: error while loading shared libraries: 
libHShaskeline-0.7.3.0-ghc8.0.2.so: cannot open shared object file: No such 
file or directory
/usr/lib/ghc/bin/ghc-pkg: error while loading shared libraries: 
libHSterminfo-0.4.0.2-ghc8.0.2.so: cannot open shared object file: No such file 
or directory
dpkg: error processing package ghc (--configure):
 installed ghc package post-installation script subprocess returned error exit 
status 127
Errors were encountered while processing:
 ghc
E: Sub-process /usr/bin/dpkg returned an error code (1)
#

[James Clarke]
> Can you run
> `/usr/lib/ghc/bin/ghc-pkg --version` successfully? Please try running
> with LD_DEBUG=libs,files and post the output.

Here is what I am seeing:

# LD_DEBUG=libs,files /usr/lib/ghc/bin/ghc-pkg --version
 15427:
 15427: file=libffi.so.6 [0];  needed by /usr/lib/ghc/bin/ghc-pkg [0]
 15427: find library=libffi.so.6 [0]; searching
 15427:  search cache=/etc/ld.so.cache
 15427:   trying file=/usr/lib/x86_64-linux-gnu/libffi.so.6
 15427:
 15427: file=libffi.so.6 [0];  generating link map
 15427:   dynamic: 0x7f57e6da3e08  base: 0x7f57e6b9c000   size: 
0x00208668
 15427: entry: 0x7f57e6b9d960  phdr: 0x7f57e6b9c040  phnum: 
 7
 15427:
 15427:
 15427: file=libHSterminfo-0.4.0.2-ghc8.0.2.so [0];  needed by 
/usr/lib/ghc/bin/ghc-pkg [0]
 15427: find library=libHSterminfo-0.4.0.2-ghc8.0.2.so [0]; searching
 15427:  search cache=/etc/ld.so.cache
 15427:  search 
path=/lib/x86_64-linux-gnu/tls/x86_64/x86_64:/lib/x86_64-linux-gnu/tls/x86_64:/lib/x86_64-linux-gnu/tls/x86_64:/lib/x86_64-linux-gnu/tls:/lib/x86_64-linux-gnu/x86_64/x86_64:/lib/x86_64-linux-gnu/x86_64:/lib/x86_64-linux-gnu/x86_64:/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu/tls/x86_64/x86_64:/usr/lib/x86_64-linux-gnu/tls/x86_64:/usr/lib/x86_64-linux-gnu/tls/x86_64:/usr/lib/x86_64-linux-gnu/tls:/usr/lib/x86_64-linux-gnu/x86_64/x86_64:/usr/lib/x86_64-linux-gnu/x86_64:/usr/lib/x86_64-linux-gnu/x86_64:/usr/lib/x86_64-linux-gnu:/lib/tls/x86_64/x86_64:/lib/tls/x86_64:/lib/tls/x86_64:/lib/tls:/lib/x86_64/x86_64:/lib/x86_64:/lib/x86_64:/lib:/usr/lib/tls/x86_64/x86_64:/usr/lib/tls/x86_64:/usr/lib/tls/x86_64:/usr/lib/tls:/usr/lib/x86_64/x86_64:/usr/lib/x86_64:/usr/lib/x86_64:/usr/lib
(system search path)
 15427:   trying 
file=/lib/x86_64-linux-gnu/tls/x86_64/x86_64/libHSterminfo-0.4.0.2-ghc8.0.2.so
 15427:   trying 
file=/lib/x86_64-linux-gnu/tls/x86_64/libHSterminfo-0.4.0.2-ghc8.0.2.so
 15427:   trying 
file=/lib/x86_64-linux-gnu/tls/x86_64/libHSterminfo-0.4.0.2-ghc8.0.2.so
 15427:   trying 
file=/lib/x86_64-linux-gnu/tls/libHSterminfo-0.4.0.2-ghc8.0.2.so
 15427:   trying 
file=/lib/x86_64-linux-gnu/x86_64/x86_64/libHSterminfo-0.4.0.2-ghc8.0.2.so
 15427:   trying 
file=/lib/x86_64-linux-gnu/x86_64/libHSterminfo-0.4.0.2-ghc8.0.2.so
 15427:   trying 
file=/lib/x86_64-linux-gnu/x86_64/libHSterminfo-0.4.0.2-ghc8.0.2.so
 15427:   trying 
file=/lib/x86_64-linux-gnu/libHSterminfo-0.4.0.2-ghc8.0.2.so
 15427:   trying 
file=/usr/lib/x86_64-linux-gnu/tls/x86_64/x86_64/libHSterminfo-0.4.0.2-ghc8.0.2.so
 15427:   trying 
file=/usr/lib/x86_64-linux-gnu/tls/x86_64/libHSterminfo-0.4.0.2-ghc8.0.2.so
 15427:   trying 
file=/usr/lib/x86_64-linux-gnu/tls/x86_64/libHSterminfo-0.4.0.2-ghc8.0.2.so
 15427:   trying 
file=/usr/lib/x86_64-linux-gnu/tls/libHSterminfo-0.4.0.2-ghc8.0.2.so
 15427:   trying 
file=/usr/lib/x86_64-linux-gnu/x86_64/x86_64/libHSterminfo-0.4.0.2-ghc8.0.2.so
 15427:   trying 
file=/usr/lib/x86_64-linux-gnu/x86_64/libHSterminfo-0.4.0.2-ghc8.0.2.so
 15427:   trying 
file=/usr/lib/x86_64-linux-gnu/x86_64/libHSterminfo-0.4.0.2-ghc8.0.2.so
 15427:   trying 
file=/usr/lib/x86_64-linux-gnu/libHSterminfo-0.4.0.2-ghc8.0.2.so
 15427:   trying 
file=/lib/tls/x86_64/x86_64/libHSterminfo-0.4.0.2-ghc8.0.2.so
 15427:   trying file=/lib/tls/x86_64/libHSterminfo-0.4.0.2-ghc8.0.2.so
 15427:   trying file=/lib/tls/x86_64/libHSterminfo-0.4.0.2-ghc8.0.2.so
 15427:   trying file=/lib/tls/libHSterminfo-0.4.0.2-ghc8.0.2.so
 15427:   trying 

Bug#889867: [claws-mail] selection jumps to the last item in a folder after Delete

2018-02-07 Thread Roman Mamedov
Package: claws-mail
Version: 3.14.1-3+b1
Severity: normal

When a folder has multiple messages, selecting any of them and pressing the
"Delete" key deletes the message and then jumps the selection cursor to the
very last message in that folder.

This is not observed with 3.11.1-3+deb8u1. In that version, after pressing the
Delete key the cursor remains logically in the same position, i.e. moves on to
message which was adjacent to the just-deleted one.

-- 
With respect,
Roman



Bug#889866: nagstamon: crashes under openbox: python tracebacks, SIGSEGV

2018-02-07 Thread Paul Wise
Package: nagstamon
Version: 3.0.2-1
Severity: normal
Usertags: crash

When I try to run nagstamon under openbox I get two Python tracebacks
and a Python crash (SIGSEGV). It would be nice if nagstamon could
handle the lack of a notifications mechanism in openbox by just
updating the nagstamon window with the current status of remote
servers. If the crash is a problem in Python or Qt, please clone
and or reassign this bug as appropriate.

$ gdb -batch -n -ex 'set pagination off' -ex run -ex bt -ex 'thread apply all 
bt full' --args python3 /usr/bin/nagstamon
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe00f0700 (LWP 9886)]
[New Thread 0x7fffda119700 (LWP 9946)]
[New Thread 0x7fffd9918700 (LWP 9948)]
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/dbus/bus.py", line 175, in 
activate_name_owner
return self.get_name_owner(bus_name)
  File "/usr/lib/python3/dist-packages/dbus/bus.py", line 361, in get_name_owner
's', (bus_name,), **keywords)
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in 
call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NameHasNoOwner: Could 
not get owner of name 'org.freedesktop.Notifications': no such name

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/Nagstamon/QUI/__init__.py", line 6426, 
in __init__
'/org/freedesktop/Notifications')
  File "/usr/lib/python3/dist-packages/dbus/bus.py", line 241, in get_object
follow_name_owner_changes=follow_name_owner_changes)
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 248, in __init__
self._named_service = conn.activate_name_owner(bus_name)
  File "/usr/lib/python3/dist-packages/dbus/bus.py", line 180, in 
activate_name_owner
self.start_service_by_name(bus_name)
  File "/usr/lib/python3/dist-packages/dbus/bus.py", line 278, in 
start_service_by_name
'su', (bus_name, flags)))
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in 
call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The 
name org.freedesktop.Notifications was not provided by any .service files
[New Thread 0x7fffd4728700 (LWP 10085)]
[New Thread 0x7fffd33b2700 (LWP 10124)]
[New Thread 0x7fffd2bb1700 (LWP 10125)]
[New Thread 0x7fffd23b0700 (LWP 10126)]
[New Thread 0x7fffd1baf700 (LWP 10127)]
[Thread 0x7fffd2bb1700 (LWP 10125) exited]
[Thread 0x7fffd23b0700 (LWP 10126) exited]
[Thread 0x7fffd33b2700 (LWP 10124) exited]
QLayout: Attempting to add QLayout "" to StatusWindow "", which already has a 
layout
[New Thread 0x7fffd33b2700 (LWP 10142)]
[New Thread 0x7fffd23b0700 (LWP 10143)]
[New Thread 0x7fffd2bb1700 (LWP 10210)]
[Thread 0x7fffd2bb1700 (LWP 10210) exited]
[New Thread 0x7fffd2bb1700 (LWP 10211)]
[Thread 0x7fffd2bb1700 (LWP 10211) exited]
[New Thread 0x7fffd2bb1700 (LWP 10219)]

Thread 1 "python3" received signal SIGSEGV, Segmentation fault.
_dbus_counter_get_size_value (counter=0x203a73736572706d) at 
../../../dbus/dbus-resources.c:276
276 ../../../dbus/dbus-resources.c: No such file or directory.
#0  0x7fffef9ed3c0 in _dbus_counter_get_size_value 
(counter=0x203a73736572706d) at ../../../dbus/dbus-resources.c:276
#1  0x7fffef9f2b82 in _dbus_transport_get_dispatch_status 
(transport=0x7fffebdb09e0 ) at 
../../../dbus/dbus-transport.c:1126
#2  0x7fffef9f2de6 in _dbus_transport_queue_messages 
(transport=0x7fffebdb09e0 ) at 
../../../dbus/dbus-transport.c:1172
#3  0x7fffef9d9a81 in _dbus_connection_get_dispatch_status_unlocked 
(connection=0x16687a0) at ../../../dbus/dbus-connection.c:4257
#4  0x7fffef9dcf22 in dbus_connection_dispatch (connection=0x16687a0) at 
../../../dbus/dbus-connection.c:4590
#5  0x7fffd4ae02f8 in pyqt5DBusHelper::dispatch() (this=0x166d850) at 
../../dbus/dbus.cpp:323
#6  0x7fffebd338c2 in QObject::event(QEvent*) (this=0x166d850, e=) at kernel/qobject.cpp:1246
#7  0x7fffeca2059c in QApplicationPrivate::notify_helper(QObject*, QEvent*) 
(this=this@entry=0xfcce40, receiver=receiver@entry=0x166d850, 
e=e@entry=0x166a240) at kernel/qapplication.cpp:3722
#8  0x7fffeca27e64 in QApplication::notify(QObject*, QEvent*) 
(this=this@entry=0xfd8000, receiver=receiver@entry=0x166d850, 
e=e@entry=0x166a240) at kernel/qapplication.cpp:3481
#9  0x7fffed4bc97e in sipQApplication::notify(QObject*, QEvent*) 
(this=0xfd8000, a0=0x166d850, a1=0x166a240) at 
./build-3.6/QtWidgets/sipQtWidgetspart9.cpp:12947
#10 0x7fffebd04258 in QCoreApplication::notifyInternal2(QObject*, QEvent*) 
(receiver=0x166d850, event=event@entry=0x166a240) at 
kernel/qcoreapplication.cpp:1018
#11 0x7fffebd069cd in QCoreApplication::sendEvent(QObject*, QEvent*) 
(event=0x166a240, receiver=) at 

Bug#889285: bind9: CVE-2017-3139 affects debian too: assertion failure in validator.c:1858

2018-02-07 Thread Roberto C . Sánchez
On Sat, Feb 03, 2018 at 05:17:01PM +0100, Salvatore Bonaccorso wrote:
> 
> The bug was about CVE-2017-3137, it's never a good idea to mix up
> things ;-).

This is true.  However, it appears that Ondrej Zary's comment to #860225
on 2017-09-02 is in fact related to CVE-2017-3139.  Since one of the
bind9 maintainers was the one to raise the issue of CVE-2017-3139 in
that same bug, I don't see a related follow-up report from a user to be
problematic.

> Anyway thanks that you took action and filled a new bug
> for this issue you are experiencing.
> 
> JTR, since Red Hat does not provide much details on the CVE-2017-3139
> we cannot say Debian is affected as well by this very same CVE. Since
> it's not clear, what CVE-2017-3139 is in detail, I have removed the
> CVE in the subject of this bug.
> 
It is true that there is information provided by RedHat regarding the
details of the vulnerability.  The RHSA mentioned in #860225 is also
linked from this RedHat BZ:

https://bugzilla.redhat.com/show_bug.cgi?id=1447743

However, there are no useful details there either.  I did some digging
and located the bind9 source RPM references in RHSA-2017:1202 and its
immediate predecessor.  By comparing the packages, I was able to
identify the specific patch that was associated with that RHSA.  I have
attached the patch to this email.  The name of the patch refers to
another RedHat BZ entry:

https://bugzilla.redhat.com/show_bug.cgi?id=1447407

That one is not accessible to the public, so we have no way of knowing
the details there.  Additionally, the related upstream RT tickets are
also not public.

Note that the attached patch appears to be based on commit
07dbb507d2913fc35c7edbe3692a976e3248a911 from upstream's git repository:

https://source.isc.org/git/bind9.git

The upstream changes appear to include a hunk in resolver.c which does
not appear in the RedHat patch.  That chunk would also not apply to the
wheezy version of bind9.

> What seem clear is that apparently a fix in Debian wheezy's bind9
> version causes the regression you notices. Thus I suggest the LTS team
> to try to find the defective patch introducing the issue and then
> issue just a regression update (without referencing CVE-2017-3139. If
> its on the other hand clear that Debian wheezy used the very same
> patch for a previous issue, and CVE-2017-3139 applies as well for
> Debian wheezy, then obviously it's fine to use the CVE).
> 
I examined the changes made from 9.8.4.dfsg.P1-6+nmu2+deb7u15 to
9.8.4.dfsg.P1-6+nmu2+deb7u16, which included fixes for CVE-2017-3136,
CVE-2017-3137, and CVE-2017-3138.  After examining the changes and
comparing them to the related upstream commits, I am convinced that the
fix for CVE-2017-3137 in 9.8.4.dfsg.P1-6+nmu2+deb7u16 is correct and
complete.  I would consider my examination thorough, but not exhaustive
owing to the large volume of change and some departures that are clearly
a result of the upsteam changes being backported to the bind9 in wheezy.
I am further convinced that the problem reported by Ondrej Zary in
#860225 and by Vladislav Kurz are both identical occurrences of
CVE-2017-3139.

In order to confirm the latter hypothesis, I built the current wheezy
version of bind9 and ran the dnssec test.  The test passed.  I then
stripped the changes to validator.c from the attached patch and applied
the remainder to the current wheezy version of bind9, built, and ran the
dnssec test again.  This time the test failed.  This seems to indicate
that the version of bind9 in wheezy is vulnerable to CVE-2017-3139.  I
then applied the remaining validator.c changes, rebuilt, and ran the
dnssec test again.  This time the test passed.

Based on these findings, I conclude that wheezy bind9 is vulnerable to
CVE-2017-3139.  I propose to do the following:

- Mark CVE-2017-3139 as affecting wheezy in the security tracker
- Prepare and upload a version 9.8.4.dfsg.P1-6+nmu2+deb7u20 upload that
  incorporates the CVE-2017-3139 patch from RedHat (and which closes
  this bug, #889285)
- Release a DLA per the normal procedure

I am now in the process of preparing the package for upload, but I will
wait a couple of days to allow for any objections and/or suggestions.

Regards,

-Roberto

-- 
Roberto C. Sánchez
>From 1d31a0cf1712d3eb001a686c06fe1225ba48fd04 Mon Sep 17 00:00:00 2001
From: Mark Andrews 
Date: Sat, 6 Oct 2012 14:56:33 +1000
Subject: [PATCH] 3391. [bug] DNSKEY that encountered a CNAME failed. [RT
 #31262]

(original commit 07dbb507d2913fc35c7edbe3692a976e3248a911)
---
 bin/tests/system/dnssec/clean.sh |  1 +
 bin/tests/system/dnssec/ns3/secure.example.db.in |  4 ++
 bin/tests/system/dnssec/ns3/sign.sh  |  4 +-
 bin/tests/system/dnssec/tests.sh | 66 
 lib/dns/validator.c  |  4 ++
 5 files changed, 78 insertions(+), 1 deletion(-)

diff --git a/bin/tests/system/dnssec/clean.sh b/bin/tests/system/dnssec/clean.sh
index 

Bug#885006: Workaround using Poppler

2018-02-07 Thread martin f krafft
Just a quick note that I've found a workaround to my problem, which
is to either use pdftopdf / pdftops from Poppler directly, or insert
it into the CUPS filter pipeline before Ghostscript to be able to
print, e.g.

  pdftops - - < my.pdf | lp …

-- 
 .''`.   martin f. krafft  @martinkrafft
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems


digital_signature_gpg.asc
Description: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)


Bug#889865: bash(1): Some corrections in the manual

2018-02-07 Thread Bjarni Ingi Gislason
Package: bash
Version: 4.4-5
Severity: minor
Tags: patch

Dear Maintainer (Debian and upstream),

  The result of some tests.  The patch is in the attachment.

Test nr. 1: Remove space at end of lines.

413:does not attempt to read any other startup files. 
1391:Expands to the current option flags as specified upon invocation, 
2062:A filename whose suffix matches one of the entries in 
4251:option to the 
4946:signal by the kernel's terminal driver, 



Test nr. 2: Fix warning from man/groff

:2101 (macro IR): only 1 argument, but more are expected
:3400 (macro BR): only 1 argument, but more are expected
:6801 (macro BR): only 1 argument, but more are expected
:8627 (macro IR): only 1 argument, but more are expected



Test nr. 18: Change - to \- if it means a minus.

2755:each term.  The default increment is 1 or -1 as appropriate.
3000:positional parameter, so an offset of -1 evaluates to the last positional
5533:.B completion\-display\-width (-1)
5539:The default value is -1.
8774:Two special argument values may be used: -1 represents the current
8775:time, and -2 represents the time the shell was invoked.
8776:If no argument is specified, conversion behaves as if -1 had been given.



Test nr. 22: Use (in)valid instead of "(il)legal" (GNU coding standards).

2633:Any reference to a variable using a valid subscript is legal, and



Test nr. 25: Change a HYPHEN-MINUS (code 0x55, 2D) to a dash (minus,
for options), if it matches " -[:alpha:]" or \(aq-[:alpha:]

4344:\fIinteger\fP attribute using \fBdeclare -i\fP is assigned a value.
6644:with \fBcomplete -D\fP.
6667:complete -D -F _completion_loader -o bashdefault -o default

#

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

Kernel: Linux 4.9.65-3u2 (SMP w/2 CPU cores)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
LANGUAGE=is_IS.iso88591 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages bash depends on:
ii  base-files   10.1
ii  dash 0.5.8-2.10
ii  debianutils  4.8.4
ii  libc62.26-4
ii  libtinfo56.0+20171125-1

Versions of packages bash recommends:
ii  bash-completion  1:2.1-4.3

Versions of packages bash suggests:
pn  bash-doc  

-- no debconf information

-- 
Bjarni I. Gislason
--- bash.1  2017-05-15 19:45:32.0 +
+++ bash.1.new  2018-02-08 00:50:03.0 +
@@ -410,7 +410,7 @@ files, the
 option has no effect.
 A non-interactive shell invoked with the name
 .B sh
-does not attempt to read any other startup files. 
+does not attempt to read any other startup files.
 When invoked as
 .BR sh ,
 .B bash
@@ -1388,7 +1388,7 @@ Expands to the exit status of the most r
 pipeline.
 .TP
 .B \-
-Expands to the current option flags as specified upon invocation, 
+Expands to the current option flags as specified upon invocation,
 by the
 .B set
 builtin command, or those set by the shell itself
@@ -2059,7 +2059,7 @@ filename completion (see
 .SM
 .B READLINE
 below).
-A filename whose suffix matches one of the entries in 
+A filename whose suffix matches one of the entries in
 .SM
 .B FIGNORE
 is excluded from the list of matched filenames.
@@ -2098,7 +2098,7 @@ A value of
 .I ignoreboth
 is shorthand for \fIignorespace\fP and \fIignoredups\fP.
 A value of
-.IR erasedups
+.I erasedups
 causes all previous lines matching the current line to be removed from
 the history list before that line is saved.
 Any value not in the above list is ignored.
@@ -2630,7 +2630,7 @@ array, and an index of \-1 references th
 .PP
 Referencing an array variable without a subscript is equivalent to
 referencing the array with a subscript of 0.
-Any reference to a variable using a valid subscript is legal, and
+Any reference to a variable using a valid subscript is valid, and
 .B bash
 will create an array if necessary.
 .PP
@@ -2752,7 +2752,7 @@ lexicographically between \fIx\fP and \f
 using the default C locale.
 Note that both \fIx\fP and \fIy\fP must be of the same type.
 When the increment is supplied, it is used as the difference between
-each term.  The default increment is 1 or -1 as appropriate.
+each term.  The default increment is 1 or \-1 as appropriate.
 .PP
 Brace expansion is performed before any other expansions,
 and any characters special to other expansions are preserved
@@ -2997,7 +2997,7 @@ one space to avoid being confused with t
 If \fIparameter\fP is \fB@\fP, the result is \fIlength\fP positional
 parameters beginning at \fIoffset\fP.
 A negative \fIoffset\fP is taken relative to one greater than the greatest
-positional parameter, so an offset of -1 evaluates to the last positional
+positional parameter, so an offset of \-1 evaluates to the last positional
 parameter.
 It is an expansion error if \fIlength\fP evaluates to a number less than
 zero.
@@ 

Bug#889864: python3-yarl: New release available

2018-02-07 Thread Matthias Urlichs
Package: python3-yarl
Version: 0.16.0-1
Severity: wishlist

Upstream has bumped the version to 1.1.0. Please update the package.

-- System Information:
Debian Release: 9.3
  APT prefers stable
  APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable'), (550, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages python3-yarl depends on:
ii  libc6  2.26-4
ii  python33.6.4-1
ii  python3-multidict  3.3.2-1

python3-yarl recommends no packages.

python3-yarl suggests no packages.

-- no debconf information



Bug#889863: openmsx: FTBFS on x32: bogus -m64 -> "No working C++ compiler"

2018-02-07 Thread Aaron M. Ucko
Source: openmsx
Version: 0.14.0-2
Severity: normal
Tags: upstream

Builds of openmsx for x32 (admittedly not a release architecture) have
been failing:

  python build/probe.py \
"g++  -m64" \
derived/x86_64-linux-debian/config linux SYS_DYN ""
  Probing target system...
  Creating derived/x86_64-linux-debian/config/probed_defs.mk...
  Creating derived/x86_64-linux-debian/config/systemfuncs.hh...
  
  No working C++ compiler was found.

Please do not supply -m64 or the like on *any* architecture.  Debian's
compilers already have appropriate architecture-dependent defaults, so
these flags are redundant at best.

Thanks!

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



Bug#805901: cmake: suggest cmake-doc

2018-02-07 Thread John Scott
Package: cmake
Version: 3.9.5-1
Followup-For: Bug #805901

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I agree. It would be convenient to be able to mark cmake-doc as automatically
installed so that it could be autoremoved if CMake were to be removed.



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

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

Versions of packages cmake depends on:
ii  cmake-data3.9.5-1
ii  dpkg  1.19.0.5
ii  libarchive13  3.2.2-3.1
ii  libc6 2.26-4
ii  libcurl3  7.58.0-2
ii  libexpat1 2.2.5-3
ii  libgcc1   1:7.2.0-19
ii  libjsoncpp1   1.7.4-3
ii  librhash0 1.3.4-3
ii  libstdc++67.2.0-19
ii  libuv11.18.0-3
ii  procps2:3.3.12-3
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages cmake recommends:
ii  gcc   4:7.2.0-1d1
ii  make  4.1-9.1

Versions of packages cmake suggests:
ii  ninja-build  1.8.2-1

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQFGBAEBCgAwFiEEJwCMxdBfG24Y2trvfWFEpid5MHIFAlp7pMQSHGpzY290dEBw
b3N0ZW8ubmV0AAoJEH1hRKYneTByZn8H/340PA00CjSnaYxfPRXxJIi65KQT5CEE
OVQhH/UzjG6ZsrpS+JS8jeX+4EM9Uvyy9wCgcvWxpwpBNXHSpxQ2RVqVs7AI/tyi
jcJWGZgHFUnvG0rBm9GNZSpeir4YW3c+8ClO/TojW71T6b2QuF5Q+GmoQL7dksfV
GyasuHycsRyJTQSYpNNQU/DOrAJ1w4pBZO3e2ARVbjnmQ7n5CcYfQKKU2wNUBcIC
NEuqYYyhsYmuNQIFggvsFD09j6xf+IQNjBDsgKrWUZtgNXvYTlVjGbfoLTErOvQE
vErr7NfomToCrXKW0RSW0OkW4RzK98o94cCddNNx7xCDEOdcdyONy6w=
=Wo/3
-END PGP SIGNATURE-



Bug#882575: dman: support selecting which section to view the manual page from

2018-02-07 Thread Paul Wise
Package: debian-goodies
Version: 0.79
Followup-For: Bug #882575

Here is an example of the errors with dman & sections:

$ man 2 mount | head -n1
MOUNT(2)Linux Programmer's ManualMOUNT(2)
$ man 8 mount | head -n1
MOUNT(8)  System Administration MOUNT(8)
$ dman 2 mount | head -n1
man: -l-/tmp/user/1000/dman.mRrD8b/mount: No such file or directory
man: -l_/tmp/user/1000/dman.mRrD8b/mount: No such file or directory
No manual entry for -l in section 2
MOUNT(2)Linux Programmer's ManualMOUNT(2)
$ dman 8 mount | head -n1
man: -l-/tmp/user/1000/dman.ndfpho/mount: No such file or directory
man: -l_/tmp/user/1000/dman.ndfpho/mount: No such file or directory
No manual entry for -l in section 8
MOUNT(2)Linux Programmer's ManualMOUNT(2)
$ dman mount | head -n1
MOUNT(2)Linux Programmer's ManualMOUNT(2)

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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


Bug#610001: [Pkg-emacsen-addons] Bug#610001: muse-el: muse-insert-thing multi-line message

2018-02-07 Thread Sean Whitton
Hello,

On Wed, Feb 07 2018, Nicholas D Steeves wrote:

> Does this mean we're tagging bugs like these as wontfix until the
> elpafied versions hit old-old-stable (or sooner?), and then closing
> the bugs?

Or just close as wontfix now.

-- 
Sean Whitton


signature.asc
Description: PGP signature


Bug#889814: lintian: Improve long description of epoch-change-without-comment

2018-02-07 Thread Guillem Jover
Hi!

On Wed, 2018-02-07 at 12:12:11 +0100, Raphaël Hertzog wrote:
> Package: lintian
> Version: 2.5.73
> Severity: wishlist

> It would be nice if the long description of epoch-change-without-comment
> could document when it's appropriate to bump the epoch and ways to avoid
> the epoch bump entirely.
> 
> I'm thinking of:
> 
> - upstream changed version numbering scheme in a way that makes the latest
>   version lower than the former one (i.e. switching from date-based
>   version to usual X.Y) => OK and that should really be the only reason
>   to use an epoch
> 
> - you want to revert to a lower version in unstable for a while => you
>   should rather use +really until you can
>   again upload the latest version.
> 
> Maybe others have more suggestions.

Yeahm, I wrote about this some time ago at:

  

Also something I forgot to add there, but Clint Adams mentioned on a
later reply, is the problem with breaking any versioned dependency,
so that also needs careful review and a possible transition.

Thanks,
Guillem



Bug#889838: unzip: CVE-2018-1000035: Heap-based buffer overflow in password protected ZIP archives

2018-02-07 Thread Santiago Vila
forwarded 889838 http://www.info-zip.org/phpBB3/viewtopic.php?f=7=548
thanks

Hello Salvatore. Thanks for the report. I've just forwarded it
upstream as a first step.



Bug#889862: dashel: FTBFS on sparc64: B2500000-B4000000 not declared

2018-02-07 Thread Aaron M. Ucko
Source: dashel
Version: 1.3.3-2
Severity: normal
Tags: upstream
User: debian-sp...@lists.debian.org
Usertags: sparc64

Builds of dashel for sparc64 (admittedly not a release architecture)
have been failing:

  /<>/dashel/dashel-posix.cpp: In constructor 
'Dashel::SerialStream::SerialStream(const string&)':
  /<>/dashel/dashel-posix.cpp:1054:37: error: 'B250' was not 
declared in this scope
  [...]
  /<>/dashel/dashel-posix.cpp:1057:37: error: 'B400' was not 
declared in this scope

Please conditionalize attempts to use these constants on their
existence -- sparc64 historically hasn't had them.  (IIRC, they're
defined as macros, making this approach straightforward.)

Thanks!

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



Bug#878926: Btrbk (>=0.26.0) bpo needed for users of stretch-backports

2018-02-07 Thread Yaroslav Halchenko

On Wed, 07 Feb 2018, Nicholas D Steeves wrote:
> On Fri, Nov 17, 2017 at 09:50:41AM -0300, Leonhard Weber wrote:
> > Hi,

> > I'd like to second the request for a bpo release due to the exact same
> > rationale.

> > In the meantime deferring btrfs bpo upgrades because of btrbk.

> :-o

> Dear Yaroslav,

> I am CCing you in the hopes of closing this bug (open since
> 2017-10-17) because you sponsored uploads of btrbk.

I could close it but I guess you meant "fix/address" it?  for that
unfortunately I don't have bandwidth ATM... FWIW quick
backports are also available from neurodebian

-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik



Bug#889861: [libguestfs0] supermin root filesystem is built without /bin/sh (breaking dhclient)

2018-02-07 Thread Paul Aurich

Package: libguestfs0
Version: 1:1.36.13-1+b2
Severity: important

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

With dash installed as /bin/sh, the supermin "appliance"s ends up being 
built without a /bin/sh (as of bash 4.4.18-1, since bash drops the 
pre-depends on dash).


This sort-of wrecks havoc with the qemu VM via virt-* commands (e.g. 
virt-rescue -a debian-9.img --network -r), particularly those using 
networking, because dhclient-script uses #!/bin/sh.


adding 'dash' to /usr/lib/x86_64-linux-gnu/guestfs/supermin.d/packages 
fixes the issue (though that may not be the correct packaged fix)




On Debian 9.3, supermin's build log shows that it includes dash:

/usr/bin/supermin --build \
--verbose --verbose --verbose \
--lock /var/tmp/.guestfs-1000/lock \
--copy-kernel \
-f ext2 \
--host-cpu x86_64 \
/usr/lib/x86_64-linux-gnu/guestfs/supermin.d \
-o /var/tmp/.guestfs-1000/appliance.d

...
supermin: mapping package names to installed packages
supermin: resolving full list of package dependencies
supermin: build: 192 packages, including dependencies
  - acl_2.2.52-3+b1_amd64
  - adduser_3.115_all
  - attr_1:2.4.47-2+b2_amd64
  - augeas-lenses_1.8.0-1+deb9u1_all
  - base-files_9.9+deb9u3_amd64
  - bash_4.4-5_amd64
  - binutils_2.28-5_amd64
  - bsdmainutils_9.0.12+nmu1_amd64
  - bsdutils_1:2.29.2-1_amd64
  - btrfs-progs_4.7.3-1_amd64
  - btrfs-tools_4.7.3-1_amd64
  - bzip2_1.0.6-8.1_amd64
  - coreutils_8.26-3_amd64
  - cpio_2.11+dfsg-6_amd64
  - cryptsetup-bin_2:1.7.3-4_amd64
  - cryptsetup_2:1.7.3-4_amd64
  - curl_7.52.1-5+deb9u4_amd64
  - dash_0.5.8-2.4_amd64
...



On an up-to-date sid system, supermin's build log is missing dash:

supermin: mapping package names to installed packages
supermin: resolving full list of package dependencies
supermin: build: 191 packages, including dependencies
...
  - bash_4.4.18-1_amd64
...
  - curl_7.58.0-2_amd64
  - debconf_1.5.65_all
...




With /bin/sh as dash, the "appliance" ends up being built in a way that 
networking fails:



> ip link set eth0 up
> dhclient -v eth0
Internet Systems Consortium DHCP Client 4.3.5
Copyright 2004-2016 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

execve (/sbin/dhclient-script, ...): No such file or directory
Listening on LPF/eth0/52:54:00:12:34:56
Sending on   LPF/eth0/52:54:00:12:34:56
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPREQUEST of 169.254.2.15 on eth0 to 255.255.255.255 port 67
DHCPOFFER of 169.254.2.15 from 169.254.2.2
DHCPACK of 169.254.2.15 from 169.254.2.2
execve (/sbin/dhclient-script, ...): No such file or directory
bound to 169.254.2.15 -- renewal in 43114 seconds.

> ip addr show dev eth0
2: eth0:  mtu 1500 qdisc pfifo_fast 
state UP group default qlen 1000

link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff
inet6 fec0::5054:ff:fe12:3456/64 scope site dynamic mngtmpaddr
   valid_lft 86272sec preferred_lft 14272sec
inet6 fe80::5054:ff:fe12:3456/64 scope link
   valid_lft forever preferred_lft forever
> /sbin/dhclient-script
bash: /sbin/dhclient-script: /bin/sh: bad interpreter: No such file or 
directory





(as a side note: on my system, I also have to link up eth0 in the qemu 
guest before dhclient works, but I'm still investigating that. I don't 
know if I've mucked something up or it's an issue with newer dhclient or 
qemu or kernel or what.)




--- System information. ---
Architecture: Kernel:   Linux 4.14.0-3-amd64

Debian Release: buster/sid
  500 unstable-debug  deb.debian.org   500 unstable 
deb.debian.org   500 testing deb.debian.org   500 stable

--- Package information. ---
Depends(Version) | Installed
-+-===
libacl1(>= 2.2.51-8) | 2.2.52-3+b1
libaugeas0(>= 1.0.0) | 1.10.1-1
libc6  (>= 2.17) | 2.26-6
libcap2  (>= 1:2.10) | 1:2.25-1.2
libfuse2(>= 2.8) | 2.9.7-1
libhivex0 (>= 1.2.2+git20100712) | 1.3.14-4+b1
libmagic1  (>= 5.12) | 1:5.32-1
libpcre3 | 2:8.39-9
libselinux1(>= 1.32) | 2.7-2+b1
libsystemd0  | 237-1
libtsk13  (>= 4.2.0) | 4.4.2-3
libvirt0  (>= 0.9.4~rc1) | 4.0.0-1
libxml2   (>= 2.8.0) | 2.9.4+dfsg1-6.1
libyajl2  (>= 2.0.4) | 2.1.0-2+b3
supermin  (>= 5) | 5.1.19-2
qemu-system-x86  | 1:2.11+dfsg-1
sgabios  | 0.0~svn8-4
db-util  | 5.3.1
icoutils | 0.32.2-1
netpbm  

Bug#889860: python3-numpy: TypeError initializing resolution on powerpcspe

2018-02-07 Thread Aaron M. Ucko
Package: python3-numpy
Version: 1:1.13.3-2
Severity: normal
Tags: upstream
User: debian-powerpc
Usertags: powerpcspe
Control: affects -1 src:chemps2

As observed in [1], numpy encounters two warnings and a type error
when initializing itself on powerpcspe:

  /usr/lib/python3/dist-packages/numpy/core/getlimits.py:82: RuntimeWarning: 
overflow encountered in power
self.resolution = float_to_float(float_conv(10) ** (-self.precision))
  /usr/lib/python3/dist-packages/numpy/core/getlimits.py:82: RuntimeWarning: 
invalid value encountered in power
self.resolution = float_to_float(float_conv(10) ** (-self.precision))
  Traceback (most recent call last):
File "setup.py", line 22, in 
  import numpy as np
File "/usr/lib/python3/dist-packages/numpy/__init__.py", line 142, in 

  from . import add_newdocs
File "/usr/lib/python3/dist-packages/numpy/add_newdocs.py", line 13, in 

  from numpy.lib import add_newdoc
File "/usr/lib/python3/dist-packages/numpy/lib/__init__.py", line 8, in 

  from .type_check import *
File "/usr/lib/python3/dist-packages/numpy/lib/type_check.py", line 11, in 

  import numpy.core.numeric as _nx
File "/usr/lib/python3/dist-packages/numpy/core/__init__.py", line 51, in 

  from . import getlimits
File "/usr/lib/python3/dist-packages/numpy/core/getlimits.py", line 226, in 

  tiny=exp2(_ld(-1022)))
File "/usr/lib/python3/dist-packages/numpy/core/getlimits.py", line 82, in 
__init__
  self.resolution = float_to_float(float_conv(10) ** (-self.precision))
  TypeError: unsupported operand type(s) for ** or pow(): 'numpy.float128' and 
'int'

Could you please take a look?

Thanks!

[1] 
https://buildd.debian.org/status/fetch.php?pkg=chemps2=powerpcspe=1.8.5-1=1517806729=0

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



Bug#889859: chemps2: FTBFS on mipsel: test5 segfaults

2018-02-07 Thread Aaron M. Ucko
Source: chemps2
Version: 1.8.5-1
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
User: debian-m...@lists.debian.org
Usertags: mipsel

Builds of chemps2 1.8.5 for mipsel have been failing:

  cd obj-mipsel-linux-gnu/ && ctest -R "^test3|^test5|^test8"
  Test project /<>/obj-mipsel-linux-gnu
  Start 3: test3
  1/3 Test #3: test3    Passed   19.01 sec
  Start 5: test5
  2/3 Test #5: test5 ***Exception: SegFault  1.75 
sec
  Start 8: test8
  3/3 Test #8: test8    Passed   14.19 sec
  
  67% tests passed, 1 tests failed out of 3
  
  Total Test time (real) =  34.99 sec
  
  The following tests FAILED:
  5 - test5 (SEGFAULT)
  Errors while running CTest
  debian/rules:46: recipe for target 'override_dh_auto_test' failed

I don't have additional details, but perhaps you can reproduce the
problem on a porter box.

Could you please take a look?

Thanks!

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



Bug#887461: btrfsmaintenance: blindly assumes systemd

2018-02-07 Thread Nicholas D Steeves
On Sun, Feb 04, 2018 at 05:11:37PM -0500, Nicholas D Steeves wrote:
> Hi Adam,
> 
> I've uploaded a new upstream release of btrfsmaintenance with many
> changes.  Please close this bug if it addresses the issues raised in
> this bug report, or alternatively retitle this bug to something
> concrete and true ;-)
> 
> tldl; "Depends: systemd | cron", and upstream maintains that
> btrfsmaintenance must not use both at the same time.
> 
> Because Debian defaults to systemd, I believe that is a reasonable
> default.  Also, if btrfsmaintenance ever requires patching to function
> without systemd I will search for someone to maintain a
> btrfsmaintenance-nosystemd variant...and of course, you'll be the
> first person I'll ask!
> 
> Kind regards,
> Nicholas

P.S.  I'm considering learning about debconf to make
disabled|systemd|cron a low or medium level configuration
option...mostly it's a "project to learn about and practise using
debconf in a package" but retitling this bug to something to the
effect of "Implement debconf option for easier configuration" might be
nice :-)


signature.asc
Description: PGP signature


Bug#889858: pkg-php-tools: needs update for PHPUnit 6

2018-02-07 Thread Nishanth Aravamudan
Package: pkg-php-tools
Version: 1.35
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic ubuntu-patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * tests/*: PHPUnit 6 has namespaced classes. 


Thanks for considering the patch.

*** /tmp/tmpkeOrJv/pkg-php-tools_1.35ubuntu1.debdiff
diff -Nru pkg-php-tools-1.35/tests/BaseCliTest.php 
pkg-php-tools-1.35ubuntu1/tests/BaseCliTest.php
--- pkg-php-tools-1.35/tests/BaseCliTest.php2016-12-26 23:01:08.0 
-0800
+++ pkg-php-tools-1.35ubuntu1/tests/BaseCliTest.php 2018-02-07 
15:37:16.0 -0800
@@ -30,7 +30,7 @@
  * @author Mathieu Parent 
  * @license Expat http://www.jclark.com/xml/copying.txt
  */
-class BaseCliTest extends PHPUnit_Framework_TestCase {
+class BaseCliTest extends PHPUnit\Framework\TestCase {
 protected $_cli;
 protected $_baseHelp = 'Usage:
 pkgtools COMMAND
diff -Nru pkg-php-tools-1.35/tests/BaseDependencyTest.php 
pkg-php-tools-1.35ubuntu1/tests/BaseDependencyTest.php
--- pkg-php-tools-1.35/tests/BaseDependencyTest.php 2016-12-26 
23:01:08.0 -0800
+++ pkg-php-tools-1.35ubuntu1/tests/BaseDependencyTest.php  2018-02-07 
15:36:59.0 -0800
@@ -30,7 +30,7 @@
  * @author Mathieu Parent 
  * @license Expat http://www.jclark.com/xml/copying.txt
  */
-class BaseDependencyTest extends PHPUnit_Framework_TestCase {
+class BaseDependencyTest extends PHPUnit\Framework\TestCase {
 /**
  * @expectedException InvalidArgumentException
  * @expectedExceptionMessage Unknown property: 'unknown'
diff -Nru pkg-php-tools-1.35/tests/BaseTest.php 
pkg-php-tools-1.35ubuntu1/tests/BaseTest.php
--- pkg-php-tools-1.35/tests/BaseTest.php   2016-12-26 23:01:08.0 
-0800
+++ pkg-php-tools-1.35ubuntu1/tests/BaseTest.php2018-02-07 
15:37:34.0 -0800
@@ -30,7 +30,7 @@
  * @author Mathieu Parent 
  * @license Expat http://www.jclark.com/xml/copying.txt
  */
-class BaseTest extends PHPUnit_Framework_TestCase {
+class BaseTest extends PHPUnit\Framework\TestCase {
 // ===
 // Uninstanciables
 /**
diff -Nru pkg-php-tools-1.35/tests/PhpcomposerCliTest.php 
pkg-php-tools-1.35ubuntu1/tests/PhpcomposerCliTest.php
--- pkg-php-tools-1.35/tests/PhpcomposerCliTest.php 2016-12-26 
23:01:08.0 -0800
+++ pkg-php-tools-1.35ubuntu1/tests/PhpcomposerCliTest.php  2018-02-07 
15:36:50.0 -0800
@@ -30,7 +30,7 @@
  * @author Mathieu Parent 
  * @license Expat http://www.jclark.com/xml/copying.txt
  */
-class PhpcomposerCliTest extends PHPUnit_Framework_TestCase {
+class PhpcomposerCliTest extends PHPUnit\Framework\TestCase {
 protected $_cli;
 
 protected function setUp() {
diff -Nru pkg-php-tools-1.35/tests/PhpcomposerSourceTest.php 
pkg-php-tools-1.35ubuntu1/tests/PhpcomposerSourceTest.php
--- pkg-php-tools-1.35/tests/PhpcomposerSourceTest.php  2016-12-26 
23:01:08.0 -0800
+++ pkg-php-tools-1.35ubuntu1/tests/PhpcomposerSourceTest.php   2018-02-07 
15:37:26.0 -0800
@@ -32,7 +32,7 @@
 * @author Mathieu Parent 
 * @license Expat http://www.jclark.com/xml/copying.txt
 */
-class PhpcomposerSourceTest extends PHPUnit_Framework_TestCase {
+class PhpcomposerSourceTest extends PHPUnit\Framework\TestCase {
 /**
  * @expectedException InvalidArgumentException
  * @expectedExceptionMessage composer.json not found
diff -Nru pkg-php-tools-1.35/tests/PhppearchannelCliTest.php 
pkg-php-tools-1.35ubuntu1/tests/PhppearchannelCliTest.php
--- pkg-php-tools-1.35/tests/PhppearchannelCliTest.php  2016-12-26 
23:01:08.0 -0800
+++ pkg-php-tools-1.35ubuntu1/tests/PhppearchannelCliTest.php   2018-02-07 
15:38:01.0 -0800
@@ -30,7 +30,7 @@
  * @author Mathieu Parent 
  * @license Expat http://www.jclark.com/xml/copying.txt
  */
-class PhppearchannelCliTest extends PHPUnit_Framework_TestCase {
+class PhppearchannelCliTest extends PHPUnit\Framework\TestCase {
 protected $_cli;
 
 protected function setUp() {
diff -Nru pkg-php-tools-1.35/tests/PhppearchannelSourceTest.php 
pkg-php-tools-1.35ubuntu1/tests/PhppearchannelSourceTest.php
--- pkg-php-tools-1.35/tests/PhppearchannelSourceTest.php   2016-12-26 
23:01:08.0 -0800
+++ pkg-php-tools-1.35ubuntu1/tests/PhppearchannelSourceTest.php
2018-02-07 15:36:40.0 -0800
@@ -30,7 +30,7 @@
  * @author Mathieu Parent 
  * @license Expat http://www.jclark.com/xml/copying.txt
  */
-class PhppearchannelSourceTest extends PHPUnit_Framework_TestCase {
+class PhppearchannelSourceTest extends PHPUnit\Framework\TestCase {
 /**
  * @expectedException InvalidArgumentException
  * @expectedExceptionMessage channel.xml not found
diff -Nru pkg-php-tools-1.35/tests/PhppearCliTest.php 
pkg-php-tools-1.35ubuntu1/tests/PhppearCliTest.php
--- 

Bug#832806: Build time test failure

2018-02-07 Thread Jose Luis Rivero
I was not able to reproduce the problem with gbp using the --pbuilder
option. Our buildfarm that only runs docker (not pbuilder) also did not
catch it. I've modified the rules file to run tests on an writable HOME
directory:
https://salsa.debian.org/science-team/ignition-common/commit/671996525d8c09327bce10cab47aa1f7d0800d89

Our buildfarm is happy (but it was not able to catch the previous error):
https://build.osrfoundation.org/view/All/job/ignition-common-pkg_builder-master-debian_sid-amd64/46/

Andreas could you verify please if this fix the error for you?


On Mon, Feb 5, 2018 at 10:22 AM, Andreas Tille  wrote:

> Hi Jose,
>
> I had a sponsor look at ignition-common but when building in a pbuilder
> chroot I've got:
>
> ...
>  #7: UNIT_Console_TEST ...***Timeout 240.00 sec
> [==] Running 17 tests from 1 test case.
> [--] Global test environment set-up.
> [--] 17 tests from Console_TEST
> [ RUN  ] Console_TEST.NoInitAndLog
> Error opening log file: /nonexistent/.ignition/auto_default.log
>
>
> 98% tests passed, 1 tests failed out of 61
>
> Total Test time (real) = 240.07 sec
>
> The following tests FAILED:
>   7 - UNIT_Console_TEST (Timeout)
> Errors while running CTest
> Makefile:143: recipe for target 'test' failed
> make[1]: *** [test] Error 8
> make[1]: Leaving directory '/build/ignition-common-1.0.1/
> obj-x86_64-linux-gnu'
>
>
> Kind regards
>
>Andreas.
>
> --
> http://fam-tille.de
>


Bug#872225: libtss-dev: broken symlink: /usr/lib/x86_64-linux-gnu/libtss.so -> /debian/libtss0/usr/lib/x86_64-linux-gnu/libtss.so.0

2018-02-07 Thread Luca Boccassi
Control: tags -1 patch

On Tue, 15 Aug 2017 10:35:34 +0200 Andreas Beckmann 
wrote:
> Package: libtss-dev
> Version: 1045-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package ships (or creates)
> a broken symlink.
> 
> >From the attached log (scroll to the bottom...):
> 
> 0m10.9s ERROR: FAIL: Broken symlinks:
>   /usr/lib/x86_64-linux-gnu/libtss.so ->
/debian/libtss0/usr/lib/x86_64-linux-gnu/libtss.so.0
> 
> 
> The target looks like an (incorrect) build-time path.
> 
> 
> cheers,
> 
> Andreas

Dear maintainer,

The fix for this is quite simple, patch inlined.

-- 
Kind regards,
Luca Boccassi


--- a/debian/rules
+++ b/debian/rules
@@ -115,7 +115,7 @@ override_dh_auto_install:
dh_install -Pdebian/$(LIBPKG) -p$(LIBPKG) $(USRLIB)/$(VERSIONED_LIB) 
$(USRLIB)
 
dh_link -Pdebian/$(LIBPKG) -p$(LIBPKG) $(USRLIB)/$(VERSIONED_LIB) 
$(USRLIB)/$(LIBSONAME)
-   dh_link -Pdebian/$(DEVPKG) -p$(DEVPKG) 
debian/$(LIBPKG)/$(USRLIB)/$(LIBSONAME) $(USRLIB)/$(LIBSYM)
+   dh_link -Pdebian/$(DEVPKG) -p$(DEVPKG) $(USRLIB)/$(LIBSONAME) 
$(USRLIB)/$(LIBSYM)
 
 
cp -p $(TMP)/$(MAN1)/* $(DESTMAN1)

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


Bug#889857: dnsmasq-base: Failed to open pidfile when started by Network Manager

2018-02-07 Thread Josef Kufner
Package: dnsmasq-base
Version: 2.78-1
Severity: important

Dear Maintainer,

after upgrading dnsmasq-base 2.78-2, Network Manager fails to start dnsmasq.

I'm using Network Manager with following configuration in
/etc/NetworkManager/NetworkManager.conf:

[main]
plugins=ifupdown,keyfile
dns=dnsmasq

So NetworkManager starts dnsmasq, and /etc/resolv.conf contains only 127.0.0.1
as a resolver.

After the upgrade, I get following error in syslog:

NetworkManager[15436]: dnsmasq: failed to open pidfile
/run/NetworkManager/dnsmasq.pid: Operation not permitted
dnsmasq[16073]: failed to open pidfile /run/NetworkManager/dnsmasq.pid:
Operation not permitted
dnsmasq[16073]: FAILED to start up
NetworkManager[15436]:   [1518044623.7035] dnsmasq[0x55f6a42831e0]:
dnsmasq exited with error: Filesystem problem (missing file/directory,
permissions) (3)
NetworkManager[15436]:   [1518044623.7040] dns-mgr: plugin dnsmasq
child quit unexpectedly
NetworkManager[15436]:   [1518044623.7040] dns-
plugin[0x55f6a42831e0]: starting dnsmasq...
NetworkManager[15436]:   [1518044623.7066] dnsmasq[0x55f6a42831e0]:
dnsmasq disappeared

... and local resolver is not running.

I downgraded to dnsmasq-base 2.78-1 and problem is gone -- everything works
fine.

I'm using network-manager 1.10.4-1.


Thank you and have a nice day!



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

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

Versions of packages dnsmasq-base depends on:
ii  adduser  3.117
ii  libc62.26-6
ii  libdbus-1-3  1.12.2-1
ii  libgmp10 2:6.1.2+dfsg-2
ii  libhogweed4  3.4-1
ii  libidn11 1.33-2.1
ii  libnetfilter-conntrack3  1.0.6-2
ii  libnettle6   3.4-1
ii  libnfnetlink01.0.1-3+b1

Versions of packages dnsmasq-base recommends:
ii  dns-root-data  2018013001

dnsmasq-base suggests no packages.

-- no debconf information



Bug#888654: mpv: fix breaks Youtube playlist sites

2018-02-07 Thread James Cowgill
Hi,

On 07/02/18 21:39, Marc Becker wrote:
> Package: mpv
> Version: 0.23.0-2+deb9u1
> Followup-For: Bug #888654
> 
> Patch to line 264 via 08_ytdl-hook-whitelist-protocols.patch is incorrect,
> check is applied to raw Youtube ID instead of valid url and always fails as
> a result.
> 
> Suggestions: no checking of raw IDs (skipped in upstream fix as well)

Yes I think you're right. It's also broken in sid too (but not in
experimental). I think I got thrown off by newer mpv distinguishing
between youtube ids and non youtube ids.

The original fix for 0.29 adds:
if not site:find("://") then
table.insert(playlist, "ytdl://" .. site)
elseif url_is_safe(site) then
table.insert(playlist, site)
end

So maybe this will work (replacing the existing playlist= assignment):
if not site:find("://") then
playlist = playlist .. "ytdl://" .. site .. "\n"
elseif url_is_safe(site) then
playlist = playlist .. site .. "\n"
end

Thanks,
James



signature.asc
Description: OpenPGP digital signature


Bug#738442: lintian: Possibility to provide stats on .deb member compressors

2018-02-07 Thread Mattia Rizzolo
Control: clone -1 -2
Control: retitle -2 lintian: please add a new 
control-tarball-compression-format classification tag

On Thu, Feb 08, 2018 at 03:54:45AM +0530, Chris Lamb wrote:
> > For consistency, would you also please add a
> > control-tarball-compression-format tag as well?
> 
> Sure, please file a wishlist bug :)

Aye!

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#863841: [Pkg-dns-devel] Bug#863841: Enable systemd hardening options for named

2018-02-07 Thread Ludovic Gasc
Done: https://salsa.debian.org/dns-team/bind9/merge_requests/1

Do I need to send also a merge request on:
https://salsa.debian.org/dns-team/bind ?

Thanks for your remarks.


Bug#878926: Btrbk (>=0.26.0) bpo needed for users of stretch-backports

2018-02-07 Thread Nicholas D Steeves
On Fri, Nov 17, 2017 at 09:50:41AM -0300, Leonhard Weber wrote:
> Hi,
> 
> I'd like to second the request for a bpo release due to the exact same
> rationale.
> 
> In the meantime deferring btrfs bpo upgrades because of btrbk.

:-o

Dear Yaroslav,

I am CCing you in the hopes of closing this bug (open since
2017-10-17) because you sponsored uploads of btrbk.

Best regards,
Nicholas


signature.asc
Description: PGP signature


Bug#889853: No way to adjust one's subscription preferences

2018-02-07 Thread Alexander Wirt
On Thu, 08 Feb 2018, 積丹尼 Dan Jacobson wrote:

> Package: lists.debian.org
> 
> On
> https://lists.debian.org/debconf-team/
> there is no way to adjust one's subscription preferences.
> Only a subscribe / unsubscribe button.
There aren't any other preferences. 

Alex
 



Bug#756130: lintian: Please spell check patch headers

2018-02-07 Thread Chris Lamb
tags 756130 + pending
thanks

Fixed in Git, pending upload:

  
https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=4cd9425875a25bb7ad1a29ab27e0b66b080eab37


Regards,

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



Bug#738442: lintian: Possibility to provide stats on .deb member compressors

2018-02-07 Thread Chris Lamb
Hey Mattia,

> For consistency, would you also please add a
> control-tarball-compression-format tag as well?

Sure, please file a wishlist bug :)


Regards,

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



Bug#738442: lintian: Possibility to provide stats on .deb member compressors

2018-02-07 Thread Mattia Rizzolo
On Thu, Feb 08, 2018 at 03:39:41AM +0530, Chris Lamb wrote:
> Fixed in Git, pending upload:
> 
>   
> https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=8dc0a3237cdb6646a84b19f3c6be84103400b0bb

For consistency, would you also please add a
control-tarball-compression-format tag as well?

-- 
regards,
Mattia Rizzolo

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



Bug#889846: qgis: Unable to open qGIS project

2018-02-07 Thread Sebastiaan Couwenberg
On 02/07/2018 11:02 PM, Paul Rogé wrote:
> On 02/07/2018 01:50 PM, Sebastiaan Couwenberg wrote
>> That sounds like a user error, not qgis.
>
> If QGIS crashes with composer window open, projects become
> unrecoverable. I'd consider this a problem with qgis, and time wasted
> recreating projects from scratch.

Then please file the issue upstream, see:

 
https://qgis.org/en/site/getinvolved/development/bugreporting.html#reporting-issues-on-qgis-applications

Kind Regards,

Bas



Bug#889855: apticron: on each run, getting twice: W: --force-yes is deprecated

2018-02-07 Thread Gabriel Filion
Package: apticron
Version: 1.1.61
Severity: normal

Hello,

Ever since we have stretch servers using apticron, we're getting emails
from the cron runs that show only two warning messages, twice the same
line:

W: --force-yes is deprecated, use one of the options starting with
--allow instead.


I've run apticron with tracing on (bash -x apticron) and found out that
the two following commands are the ones causing the warnings:

/usr/bin/apt-get -q -y --ignore-hold --allow-unauthenticated -s
dist-upgrade

and:

/usr/bin/apt-get --ignore-hold -qq -d dist-upgrade

This means that apticron is calling apt-get with a deprecated set of
arguments, but I'm not sure how to fix this yet.

-- System Information:
Debian Release: 9.3
  APT prefers oldoldstable
  APT policy: (500, 'oldoldstable'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_CA.utf8), LANGUAGE=fr_CA.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_CA.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages apticron depends on:
ii  apt1.4.8
ii  bzip2  1.0.6-8.1
ii  cron [cron-daemon] 3.0pl1-128+b1
ii  debconf [debconf-2.0]  1.5.61
ii  dpkg   1.18.24
ii  mailutils [mailx]  1:3.1.1-1
ii  ucf3.0036

Versions of packages apticron recommends:
ii  apt-listchanges  3.10
ii  iproute2 4.9.0-1+deb9u1

apticron suggests no packages.

-- debconf information excluded



Bug#889854: RFS: lxml/4.1.0-1~bpo9+1 [intent to maintain bpo]

2018-02-07 Thread Nicholas D Steeves
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my backport of "lxml".  It is needed
for a bpo of calibre.  I am collaborating with Norbert Preining for
the calibre and html5-parser backports, but have not received a reply
from Matthias Klose wrt lxml.

  https://lists.debian.org/debian-backports/2018/01/msg4.html

Package name: lxml
Version : 4.1.0-1~bpo9+1
Upstream Author : Stefan Behnel 
URL : http://lxml.de/
License : PSF, BSD, MIT, and GPL
Section : python

It builds these binary packages:

  python-lxml - pythonic binding for the libxml2 and libxslt libraries
  python-lxml-dbg - pythonic binding for the libxml2 and libxslt libraries 
(debug ext
  python-lxml-doc - pythonic binding for the libxml2 and libxslt libraries 
(documenta
  python3-lxml - pythonic binding for the libxml2 and libxslt libraries
  python3-lxml-dbg - pythonic binding for the libxml2 and libxslt libraries 
(debug ext

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/l/lxml/lxml_4.1.0-1~bpo9+1.dsc

Finally, one can download it with git using this command.

  git clone https://salsa.debian.org/sten-guest/lxml.git \
  && git checkout stretch-backports

More information about lxml can be obtained from http://lxml.de/.

Changes since the last upload:

lxml (4.1.0-1~bpo9+1) stretch-backports; urgency=medium

  * Rebuild for stretch-backports.

 -- Nicholas D Steeves   Mon, 25 Dec 2017 19:17:48 -0500

lxml (4.1.0-1) unstable; urgency=medium


Regards,
Nicholas D Steeves


signature.asc
Description: PGP signature


Bug#738442: lintian: Possibility to provide stats on .deb member compressors

2018-02-07 Thread Chris Lamb
tags 738442 + pending
thanks

Fixed in Git, pending upload:

  
https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=8dc0a3237cdb6646a84b19f3c6be84103400b0bb


Regards,

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



Bug#889820: debian-policy: 12.5, relaxed requirement for copyright location

2018-02-07 Thread Javier Serrano Polo
X-Debbugs-CC: a...@debian.org, ballo...@debian.org, spwhit...@spwhitton.name, 
r...@debian.org

El dc 07 de 02 de 2018 a les 20:01 +0100, Bill Allombert va escriure:
> > Versioned Recommends actually, but does a versioned Recommends make any
> > difference? 
> 
> That is why a versioned Depends: is needed.

A hard dependency on non-functional data makes no sense. What about a
new Outdates field? It would help to warn the user about outdated
documentation.

El dc 07 de 02 de 2018 a les 11:13 -0800, Russ Allbery va escriure:
> Then we can close this bug as unnecessary?  Since the *-doc mechanism is
> already specified.

I cannot make libc6 depend on glibc-doc.

> > I do not think so. Metadata is usually smaller than those files:
> > copyright, changelog, manpages, etc.
> 
> None of which you're addressing here except copyright.

True. What suffix would you use for copyright plus changelog?
-doc-minimal?

> I'm fairly sure about this, but feel free to do an experiment if you
> really want to check the numbers.

What metadata are you thinking of? What is the test you are suggesting?

El dc 07 de 02 de 2018 a les 12:25 -0700, Sean Whitton va escriure:
> Either way, please X-debbugs-CC the list rather than all four of us
> individually.

It would not work.
https://bugs.debian.org/831059


smime.p7s
Description: S/MIME cryptographic signature


Bug#889831: linux-image-4.14.0-0.bpo.3-amd64: USB RNDIS ethernet gadget - slow download transfers, RX errors

2018-02-07 Thread Ben Hutchings
On Wed, 2018-02-07 at 11:05 -0500, Tomasz Janowski wrote:
> Package: src:linux
> Version: 4.14.13-1~bpo9+1
> Severity: normal
> Tags: upstream
> 
> Dear Maintainer,
> 
> 
> The problems seems to appear with some newer smartphones, in my case I
> test Samsung Galaxy S8. I am trying to use USB tethering and everything
> seems to work as expected (modules are loaded, Ethernet devices are up
> and running, dhcp works fine). I can connect to the external world using
> both phone LTE and phone wireless network.
> 
> Now, the problem is that download speeds are terrible, arounf 64 KB/s
> while uploads are fast, the order of 15 MB/s. These speeds do not depend
> on the provider, as the results are similar when I tether wi-fi. The USB
> Ethernet interface on Linux host reports a lot of receive errors:
> 
> enp0s20u9: flags=4163  mtu 1500
> inet 192.168.42.166  netmask 255.255.255.0  broadcast 192.168.42.255
> inet6 fe80::890:3fff:fe0e:d2c6  prefixlen 64  scopeid 0x20
> ether 0a:90:3f:0e:d2:c6  txqueuelen 1000  (Ethernet)
> RX packets 716  bytes 859199 (839.0 KiB)
> RX errors 459  dropped 0  overruns 0  frame 459
> TX packets 731  bytes 86682 (84.6 KiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

So these are all frame errors.  There is a log message that would give
more information about them, but it's disabled by default.  You can
enable it by running:

echo 'format "bad rndis message" +p' > 
/sys/kernel/debug/dynamic_debug/control

[...]
> I tried the newest kernel from kernel.org git repositories, but the
> problem is still there. Should I contact upstream directly?
[...]

Yes, please mail linux-...@vger.kernel.org and net...@vger.kernel.org. 
You should include a sample of the "bad rndis message" log messages
that should appear after running the above command.  Please also cc
this bug address.

Ben.

-- 
Ben Hutchings
Reality is just a crutch for people who can't handle science fiction.


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


Bug#888654: mpv: fix breaks Youtube playlist sites

2018-02-07 Thread Marc Becker
Package: mpv
Version: 0.23.0-2+deb9u1
Followup-For: Bug #888654

Patch to line 264 via 08_ytdl-hook-whitelist-protocols.patch is incorrect,
check is applied to raw Youtube ID instead of valid url and always fails as
a result.

Suggestions: no checking of raw IDs (skipped in upstream fix as well)

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

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

Versions of packages mpv depends on:
ii  libasound2  1.1.3-5
ii  libass5 1:0.13.4-2
ii  libavcodec577:3.2.10-1~deb9u1
ii  libavdevice57   7:3.2.10-1~deb9u1
ii  libavfilter67:3.2.10-1~deb9u1
ii  libavformat57   7:3.2.10-1~deb9u1
ii  libavutil55 7:3.2.10-1~deb9u1
ii  libbluray1  1:0.9.3-3
ii  libc6   2.24-11+deb9u1
ii  libcdio-cdda1   0.83-4.3+b1
ii  libcdio-paranoia1   0.83-4.3+b1
ii  libcdio13   0.83-4.3+b1
ii  libdrm2 2.4.74-1
ii  libdvdnav4  5.0.3-3
ii  libdvdread4 5.0.3-2
ii  libegl1-mesa [libegl1-x11]  13.0.6-1+b2
ii  libgbm1 13.0.6-1+b2
ii  libgl1-mesa-glx [libgl1]13.0.6-1+b2
ii  libjack-jackd2-0 [libjack-0.125]1.9.10+20150825git1ed50c92~dfsg-5
ii  libjpeg62-turbo 1:1.5.1-2
ii  liblcms2-2  2.8-4
ii  liblua5.2-0 5.2.4-1.1+b2
ii  libpulse0   10.0-1+deb9u1
ii  librubberband2  1.8.1-7
ii  libsdl2-2.0-0   2.0.5+dfsg1-2
ii  libsmbclient2:4.5.12+dfsg-2+deb9u1
ii  libsndio6.1 1.1.0-3
ii  libswresample2  7:3.2.10-1~deb9u1
ii  libswscale4 7:3.2.10-1~deb9u1
ii  libv4l-01.12.3-1
ii  libva-drm1  1.7.3-2
ii  libva-wayland1  1.7.3-2
ii  libva-x11-1 1.7.3-2
ii  libva1  1.7.3-2
ii  libvdpau1   1.1.1-6
ii  libwayland-client0  1.12.0-1
ii  libwayland-cursor0  1.12.0-1
ii  libwayland-egl1-mesa [libwayland-egl1]  13.0.6-1+b2
ii  libx11-62:1.6.4-3
ii  libxext62:1.3.3-1+b2
ii  libxinerama12:1.1.3-1+b3
ii  libxkbcommon0   0.7.1-2~deb9u1
ii  libxrandr2  2:1.5.1-1
ii  libxss1 1:1.2.2-1
ii  libxv1  2:1.0.11-1
ii  zlib1g  1:1.2.8.dfsg-5

Versions of packages mpv recommends:
ii  xdg-utils   1.1.1-1
pn  youtube-dl  

mpv suggests no packages.

-- no debconf information



Bug#889846: qgis: Unable to open qGIS project

2018-02-07 Thread Paul Rogé
On 02/07/2018 01:22 PM, Sebastiaan Couwenberg wrote:
> Which steps did you take to reproduce the issue?
Ok, I figured out what's going on. I've reproduced this several times by
creating new projects using the steps I described. Closing the windows
by going to "Composer / Quit" and "Exit / Quit QGIS" the error is not
reproduced. But if I kill the composer window (in dwm using
|[Shift]+[Alt]+[c])|, then QGIS tries to restore the composer window on
startup, which must cause the problem I'm reporting.


Bug#889853: No way to adjust one's subscription preferences

2018-02-07 Thread 積丹尼 Dan Jacobson
Package: lists.debian.org

On
https://lists.debian.org/debconf-team/
there is no way to adjust one's subscription preferences.
Only a subscribe / unsubscribe button.



Bug#888985: [pkg-go] Bug#888985: RFS: irtt/0.9-1 [ITP] (#888985)

2018-02-07 Thread Michael Stapelberg
Sorry, only saw this email after my other reply. Somehow the threading
broke, it seems.

On Wed, Feb 7, 2018 at 12:20 PM, Pete Heist  wrote:

>
> > On Feb 7, 2018, at 12:01 PM, Clément Hermann  wrote:
> >
> > On 07/02/2018 11:39, Pete Heist wrote:
> >>
> >> Ah, ok. IRTT has an API, but it's not published yet. I think a
> >> binary-only package may be better at this point, and a separate source
> >> package later when that’s ready? If you agree, could you suggest a
> >> simple, current binary package hosted on github as a good example?
> >
> > You can have a single upstream package and produce 2 binary packages -
> > it's a bit more complicated though. Hence the example of Debian Code
> Search.
>
> Ok, I’m getting there, bear with me. :) In my case, would I not want to
> produce both a binary package and eventually a source package?
>

Be careful not to confuse the Debian concept of source packages (i.e. .dsc
files) and binary packages (i.e. .deb files) with a Debian binary package
containing binary files (e.g. a .deb with files in /usr/bin) and a Debian
binary package containing Go source code (e.g. a .deb with files in
/usr/share/gocode).

You always operate on 1 Debian source package (in your case, named irtt)
generating at least 1 Debian binary package (in your case, also named
irtt). We discussed generating 2 Debian binary packages (irtt and
golang-github-peteheist-irtt-dev).


>
> > Usually you would host the packaging on Alioth (soon salsa.debian.org),
> > and leave the upstream on github. Debian Code Search is a bit different
> > since it's specific to Debian. That doesn't change the usefulness of the
> > example for binary/api separation though.
> >
> > Regarding the workflow, the easiest is to tag your releases on github
> > (you probably already do it anyway) and merge the upstream remote in the
> > upstream branch on alioth/salsa every time you want to release (the tag
> > isn't mandatory, it's just easier, and allows for a debian/watch file).
>
> Got it...
>
> > You're expected to run unstable (Sid) for packaging work. At least in a
> > virtual machine.
> >
> > By the way, it's also a good practice to actually build the package in a
> > chroot (using git-buildpackage pbuilder options for instance), to avoid
> > build-depends issues.
>
> That explains a lot. I’ve got my work cut out for me on this part.
>
> Thank you kindly…
>
>
> ___
> Pkg-go-maintainers mailing list
> pkg-go-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers




-- 
Best regards,
Michael


Bug#888691: [bug #53020] wget -b produces empty wget-log file

2018-02-07 Thread Tim Ruehsen
Additional Item Attachment, bug #53020 (project wget):

File name: 0001-Fix-logging-in-background-mode.patch Size:2 KB


___

Reply to this item at:

  

___
  Message sent via/by Savannah
  http://savannah.gnu.org/



Bug#888691: [bug #53020] wget -b produces empty wget-log file

2018-02-07 Thread Tim Ruehsen
Follow-up Comment #2, bug #53020 (project wget):

Added a patch - please review. If OK it goes into master.

___

Reply to this item at:

  

___
  Message sent via/by Savannah
  http://savannah.gnu.org/



Bug#889843: [Python-modules-team] Bug#889843: nose2 FTBFS: ERROR: test_can_discover_test_modules_in_zipped_eggs (nose2.tests.functional.test_eggdiscovery_loader.EggDiscoveryFunctionalTest)

2018-02-07 Thread Adrian Bunk
On Wed, Feb 07, 2018 at 10:16:21PM +0100, Pierre-Elliott Bécue wrote:
> Le 7 février 2018 19:37:43 GMT+01:00, Adrian Bunk  a écrit :
> >Source: nose2
> >Version: 0.7.3-2
> >Severity: serious
>...
> Not sure about the severity but i'll let it as its for now.

A FTBFS that would also happen on the buildds is always an RC bug.

It did FTBFS in reproducible and also when I tried locally.

> Cheers ! 

cu
Adrian

-- 

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



Bug#889144: systemd 237-1: problem starting dnsmasq

2018-02-07 Thread Michael Biebl
Am 07.02.2018 um 22:12 schrieb Jonathan de Boyne Pollard:
> Michael Biebl:
> 
>> If other services depend on dnsmasq, please keep
>> https://www.lucas-nussbaum.net/blog/?p=877 in mind
>>
> Please do not.  It is an erroneous conclusion based upon a faulty
> analysis that conflates the readiness protocols
>  with
> the non-daemon nature of the way that things are run by the |service|
> command

[..]

So how exactly does dnsmasq signal readiness if it's run in foreground?
It does neither implement sd_notify nor use D-Bus activation.
So there is no way for systemd to know when it's ready to accept
connections. As a result, daemon, which depend on dnsmasq would be
started immediately once the dnsmasq binary has been spawned.





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



signature.asc
Description: OpenPGP digital signature


Bug#888985: [pkg-go] RFS: irtt/0.9-1 [ITP] (#888985)

2018-02-07 Thread Michael Stapelberg
On Wed, Feb 7, 2018 at 12:01 PM, Clément Hermann  wrote:

> On 07/02/2018 11:39, Pete Heist wrote:
> >
> > Ah, ok. IRTT has an API, but it's not published yet. I think a
> > binary-only package may be better at this point, and a separate source
> > package later when that’s ready? If you agree, could you suggest a
> > simple, current binary package hosted on github as a good example?
>
> You can have a single upstream package and produce 2 binary packages -
> it's a bit more complicated though. Hence the example of Debian Code
> Search.
>

Given the early stage of the API, I would agree that a binary-only package
is a good choice for now. Just modify debian/rules to delete the source
after installation and you should be good.


>
>
> > Debian Code Search? Though its compat version is 8. I just liked how the
> > debian directory is hosted right in the github repo, which brings me to
> > another question...
> >
> > Is it possible to maintain everything on github, or does it need to be
> > on alioth, and if so, what is a good workflow for when I want to pull in
> > changes from upstream for a new release?
>
> Usually you would host the packaging on Alioth (soon salsa.debian.org),
> and leave the upstream on github. Debian Code Search is a bit different
> since it's specific to Debian. That doesn't change the usefulness of the
> example for binary/api separation though.
>

Yeah, I agree: keeping debian/ in the upstream repo is usually not the best
solution: we really like to have our packages team-maintained, i.e. hosted
on our infrastructure alongside all of our other packages, with the same
workflows, etc.


>
> Regarding the workflow, the easiest is to tag your releases on github
> (you probably already do it anyway) and merge the upstream remote in the
> upstream branch on alioth/salsa every time you want to release (the tag
> isn't mandatory, it's just easier, and allows for a debian/watch file).
>
> [snip]
>
> >
> > Hrm, any idea why I'm seeing large differences in lintian output? I
> > didn’t see any warnings before I posted, but I do see new ones after the
> > .lintianrc changes, just they look completely different...
> >
> > $ cat /etc/debian_version
> > 9.3
> > $ lintian --version
> > Lintian v2.5.50.4
> > $ cat .lintianrc
> > display-info = yes
> > display-experimental = yes
> > pedantic = yes
> > show-overrides = no
> > color = auto
> > $ lintian ~/src/github.com/peteheist/irtt/dpkg/irtt_0.9-1_amd64.changes
> > 
> > P: irtt source: debian-watch-may-check-gpg-signature
> > I: irtt: hardening-no-fortify-functions usr/bin/irtt
> > I: irtt: spelling-error-in-binary usr/bin/irtt writeN written
> > I: irtt: spelling-error-in-binary usr/bin/irtt ot to
> > I: irtt: hardening-no-bindnow usr/bin/irtt
> > I: irtt: hardening-no-pie usr/bin/irtt
> > P: irtt: no-upstream-changelog
> >
> > Also, some of the warnings (like compat-version) just come from output
> > from dh-make-golang, which I just installed with ‘apt-get install
> > dh-make-golang’. Do I need a newer version?
>
> You're expected to run unstable (Sid) for packaging work. At least in a
> virtual machine.
>
> By the way, it's also a good practice to actually build the package in a
> chroot (using git-buildpackage pbuilder options for instance), to avoid
> build-depends issues.
>
>
> Cheers,
>
> --
> nodens
>
> ___
> Pkg-go-maintainers mailing list
> pkg-go-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
>



-- 
Best regards,
Michael


Bug#889852: ca-certificates: piuparts failure causes piuparts failures in (all?) dependent packages

2018-02-07 Thread Nicholas D Steeves
Package: ca-certificates
Version: 20170717
Severity: important

https://piuparts.debian.org/stretch2buster-rcmd/fail/ca-certificates_20170717.log

  1m9.6s DEBUG: Modified(user, group, mode, size, target): 
/etc/ca-certificates.conf expected(root, root, - 100644, 6488, None) != 
found(root, root, - 100644, 7694, None)
1m9.7s INFO: Warning: Package purging left files on system:
  /etc/ca-certificates.conf.dpkg-old not owned

1m9.7s ERROR: FAIL: After purging files have been modified:
  /etc/ca-certificates.conf  not owned

leads to

https://piuparts.debian.org/stretch2buster-rcmd/fail/elpa-muse_3.20+dfsg-4.log

3m56.6s DEBUG: Modified(user, group, mode, size, target): 
/etc/ca-certificates.conf expected(root, root, - 100644, 6488, None) != 
found(root, root, - 100644, 7694, None)
3m56.7s INFO: Warning: Package purging left files on system:
  /etc/ca-certificates.conf.dpkg-old not owned

3m56.7s ERROR: FAIL: After purging files have been modified:
  /etc/ca-certificates.conf  not owned

Adrian bunk helped me track this down in #debian-devel.


Cheers,
Nicholas



Bug#889851: Allow reporting spam from index pages

2018-02-07 Thread 積丹尼 Dan Jacobson
Package: lists.debian.org
Severity: wishlist

On e.g.,
https://lists.debian.org/debconf-team/2018/02/threads.html
there are no "Report as spam" buttons.

Thus forcing the user to click on each individual spam (sending who
knows what HTML etc. into his browser... security issue) to access the
"Report as spam" button, when all along he can see that it had a spammy
title so surely was spam.



Bug#889827: linux-image-4.15.0-rc8-amd64: IP offloading does not work

2018-02-07 Thread Ben Hutchings
Control: tag -1 upstream patch moreinfo

Does the attached patch fix it?  Instructions for building a patched
kernel package can be found at:
https://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official

Ben.

-- 
Ben Hutchings
Reality is just a crutch for people who can't handle science fiction.
From abc83f38abd2d62ce5a443e0b2a40a76d0b75cb8 Mon Sep 17 00:00:00 2001
From: Ben Hutchings 
Date: Wed, 7 Feb 2018 21:05:37 +
Subject: [PATCH] r8152: Fix conditions for setting ip_summed =
 CHECKSUM_UNNECESSARY

Currently r8152_rx_csum() returns CHECKSUM_UNNECESSARY for any packet
which the hardware reports as being IPv4 and not having a layer-4
checksum error, even if the layer-4 protocol was not recognised.
This will incorrectly include, for example, SCTP packets.  It also
appears that some TCP packets with valid headers and bad checksums
also trigger this bug.

Use the same logic for IPv4 as for IPv6.  We don't need to check the
hardware IP header checksum flag because that's always checked in
software.

Reported-by: Vincent Danjean 
Signed-off-by: Ben Hutchings 
---
 drivers/net/usb/r8152.c | 11 +--
 1 file changed, 1 insertion(+), 10 deletions(-)

diff --git a/drivers/net/usb/r8152.c b/drivers/net/usb/r8152.c
index 0657203ffb91..c3c8e2d74f8b 100644
--- a/drivers/net/usb/r8152.c
+++ b/drivers/net/usb/r8152.c
@@ -1845,16 +1845,7 @@ static u8 r8152_rx_csum(struct r8152 *tp, struct rx_desc *rx_desc)
 	opts2 = le32_to_cpu(rx_desc->opts2);
 	opts3 = le32_to_cpu(rx_desc->opts3);
 
-	if (opts2 & RD_IPV4_CS) {
-		if (opts3 & IPF)
-			checksum = CHECKSUM_NONE;
-		else if ((opts2 & RD_UDP_CS) && (opts3 & UDPF))
-			checksum = CHECKSUM_NONE;
-		else if ((opts2 & RD_TCP_CS) && (opts3 & TCPF))
-			checksum = CHECKSUM_NONE;
-		else
-			checksum = CHECKSUM_UNNECESSARY;
-	} else if (opts2 & RD_IPV6_CS) {
+	if (opts2 & (RD_IPV4_CS | RD_IPV6_CS)) {
 		if ((opts2 & RD_UDP_CS) && !(opts3 & UDPF))
 			checksum = CHECKSUM_UNNECESSARY;
 		else if ((opts2 & RD_TCP_CS) && !(opts3 & TCPF))


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


Bug#889846: qgis: Unable to open qGIS project

2018-02-07 Thread Sebastiaan Couwenberg
On 02/07/2018 10:03 PM, Paul Rogé wrote:
> On 02/07/2018 12:53 PM, Sebastiaan Couwenberg wrote:
>> Please provide the shapefile (preferably a minimal subset) with which
>> the issue can be reproduced.
> Here you go...

Creating a new project and adding a layers with the shapefile and qosm
basemap, creating a print composer (not changing anything) and saving
both, does not reproduce the issue. Starting qgis with the saved project
opens it just fine.

Which steps did you take to reproduce the issue?

Kind Regards,

Bas



Bug#858398: curl: Please migrate to openssl1.1 in Buster

2018-02-07 Thread Sebastian Andrzej Siewior
On 2018-01-11 14:32:59 [+0100], To Alessandro Ghedini wrote:
> On 2018-01-10 23:57:56 [+], Alessandro Ghedini wrote:
> > Thoughts?
> 
> If I understand Julien correctly in [0] he suggests a new soname (maybe
> with ssl suffix without bumping the 4 to 5) and a new package name.
> 
> [0] 
> https://lists.debian.org/msgid-search/b4e74ff9-6ac3-54c1-c510-34a4cfd84...@debian.org

Not that I want to rush anything or so but seems to be a RC bug with no
maintainer action > one week (or I missed it while looking through my
inbox).
Did we settle in the meantime on what we want to do? There is a merge
request on salsa with feedback from the maintainer.

Sebastian



Bug#889850: gpodder fails to launch -- ModuleNotFoundError: No module named 'cairo'

2018-02-07 Thread Dimitri Chausson
Package: gpodder
Version: 3.10.0-3
Severity: normal

Dear Maintainer,

After a usual package update routine, I cannot launch gpodder anymore. A call
from the command line gives the following output:

1518037775.639697 [gpodder.log] ERROR: Uncaught exception: Traceback (most 
recent call last):
  File "/usr/bin/gpodder", line 158, in 
main()
  File "/usr/bin/gpodder", line 151, in main
from gpodder.gtkui import main
  File "/usr/lib/python3/dist-packages/gpodder/gtkui/main.py", line 68, in 

from gpodder.gtkui.model import Model
  File "/usr/lib/python3/dist-packages/gpodder/gtkui/model.py", line 38, in 

from gpodder.gtkui import draw
  File "/usr/lib/python3/dist-packages/gpodder/gtkui/draw.py", line 37, in 

import cairo
ModuleNotFoundError: No module named 'cairo'

Traceback (most recent call last):
  File "/usr/bin/gpodder", line 158, in 
main()
  File "/usr/bin/gpodder", line 151, in main
from gpodder.gtkui import main
  File "/usr/lib/python3/dist-packages/gpodder/gtkui/main.py", line 68, in 

from gpodder.gtkui.model import Model
  File "/usr/lib/python3/dist-packages/gpodder/gtkui/model.py", line 38, in 

from gpodder.gtkui import draw
  File "/usr/lib/python3/dist-packages/gpodder/gtkui/draw.py", line 37, in 

import cairo
ModuleNotFoundError: No module named 'cairo'



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

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

Versions of packages gpodder depends on:
ii  python33.6.4-1
ii  python3-dbus   1.2.6-1
ii  python3-gi 3.26.1-2
ii  python3-mygpoclient1.8-1
ii  python3-podcastparser  0.6.2-1

Versions of packages gpodder recommends:
ii  dbus-user-session [default-dbus-session-bus]  1.12.2-1
ii  dbus-x11 [dbus-session-bus]   1.12.2-1
pn  python3-appindicator  
ii  python3-eyed3 0.8.4-2
ii  python3-html5lib  0.9-1
ii  python3-simplejson3.13.2-1

Versions of packages gpodder suggests:
pn  gnome-bluetooth | bluez-gnome  
ii  mplayer4:1.3.0~20171022.svn37997-dmo6

-- no debconf information



Bug#889849: muse-el: Make build reproducible

2018-02-07 Thread Nicholas D Steeves
Source: muse-el
Severity: normal

Muse-el has never been reproducible because documentation is generated
with embedded date stamp hashes using an application-specific method (
muse-batch-publish-files).  Resolving this bug requires one of two methods:

1) patch muse-el to generate the date stamp using a specific date
2) strip the date from the generated files

Resolving this bug will additionally allow a simple autopkgtest to be
written, where the documentation generated at build time will be
compared against a "known good" copy somewhere in the debian subdir.



Bug#889144: systemd 237-1: problem starting dnsmasq

2018-02-07 Thread Jonathan de Boyne Pollard

Michael Biebl:

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


Please do not.  It is an erroneous conclusion based upon a faulty 
analysis that conflates the readiness protocols 
 with 
the non-daemon nature of the way that things are run by the |service| 
command 
 
with the van Smoorenburg system, falsely attributing the output 
behaviour caused by the latter to the former.


The correct approach follows this maxim:

If the many years of pressure have led to a program having a way to run 
under daemontools, and that is even documented right there in the 
program's manual page, then that is also very likely the best way to run 
it under systemd, too.  The requirements that the systemd people put 
forward for what they naïvely call "new-style dæmons" are in fact /the 
same/ behaviours that the daemontools world has lobbied for for the past 
couple of decades (and has fairly widely succeeded in obtaining over 
that time), and that IBM was setting out fast approaching a quarter of a 
century ago.


* http://jdebp.eu./FGA/unix-daemon-design-mistakes-to-avoid.html

That is the case here, using the daemontools mode is how to address this 
problem, and the original service unit file (in |contrib/systemd/|) did 
in fact get this right:



--- systemd.service.original2018-02-07 19:44:24.0 +
+++ systemd.service2018-02-07 19:58:36.307113285 +
@@ -6,8 +6,10 @@
 After=network.target

 [Service]
-Type=forking
-PIDFile=/run/dnsmasq/dnsmasq.pid
+Type=simple
+RuntimeDirectory=dnsmasq
+RuntimeDirectoryMode=0755
+ExecStartPre=/bin/chown dnsmasq:nogroup %t/dnsmasq

 # Test the config file and refuse starting if it is not valid.
--- init.original2018-02-07 19:44:24.0 +
+++ init2018-02-07 20:06:25.215113285 +
@@ -292,13 +292,8 @@
 stop_resolvconf
 ;;
   systemd-exec)
-# /run may be volatile, so we need to ensure that
-# /run/dnsmasq exists here as well as in postinst
-if [ ! -d /run/dnsmasq ]; then
-   mkdir /run/dnsmasq || return 2
-   chown dnsmasq:nogroup /run/dnsmasq || return 2
-fi
-exec $DAEMON -x /run/dnsmasq/$NAME.pid \
+  # systemd's mechanisms handle the runtime directory.
+exec $DAEMON --keep-in-foreground \
 ${MAILHOSTNAME:+ -m $MAILHOSTNAME} \
 ${MAILTARGET:+ -t $MAILTARGET} \
 ${DNSMASQ_USER:+ -u $DNSMASQ_USER} \



Bug#889843: [Python-modules-team] Bug#889843: nose2 FTBFS: ERROR: test_can_discover_test_modules_in_zipped_eggs (nose2.tests.functional.test_eggdiscovery_loader.EggDiscoveryFunctionalTest)

2018-02-07 Thread Pierre-Elliott Bécue
Le 7 février 2018 19:37:43 GMT+01:00, Adrian Bunk  a écrit :
>Source: nose2
>Version: 0.7.3-2
>Severity: serious
>
>Some recent change in unstable makes nose2 FTBFS:
>
>https://tests.reproducible-builds.org/debian/history/nose2.html
>https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/nose2.html
>
>...
>==
>ERROR: test_can_discover_test_modules_in_zipped_eggs
>(nose2.tests.functional.test_eggdiscovery_loader.EggDiscoveryFunctionalTest)
>--
>Traceback (most recent call last):
>File "nose2/tests/functional/test_eggdiscovery_loader.py", line 38, in
>test_can_discover_test_modules_in_zipped_eggs
>self.assertTestRunOutputMatches(proc, stderr='FAILED \(failures=5,
>errors=1, skipped=1\)')
>  File "nose2/tests/_common.py", line 82, in assertTestRunOutputMatches
>cmd_stdout, cmd_stderr = proc.communicate()
>  File "nose2/tests/_common.py", line 227, in communicate
>**self.kwargs)
>  File "nose2/main.py", line 306, in discover
>return main(*args, **kwargs)
>  File "nose2/main.py", line 100, in __init__
>super(PluggableTestProgram, self).__init__(**kw)
>  File "/usr/lib/python2.7/unittest/main.py", line 94, in __init__
>self.parseArgs(argv)
>  File "nose2/main.py", line 133, in parseArgs
>self.createTests()
>  File "nose2/main.py", line 258, in createTests
>self.testNames, self.module)
>  File "nose2/loader.py", line 68, in loadTestsFromNames
>for name in event.names]
>  File "nose2/loader.py", line 83, in loadTestsFromName
>result = self.session.hooks.loadTestsFromName(event)
>  File "nose2/events.py", line 225, in __call__
>result = getattr(plugin, self.method)(event)
>File "nose2/plugins/loader/eggdiscovery.py", line 41, in
>loadTestsFromName
>return discovery.Discoverer.loadTestsFromName(self, event)
>File "nose2/plugins/loader/discovery.py", line 84, in loadTestsFromName
>self._find_tests_in_module(event, module, top_level_dir))
>File "nose2/plugins/loader/discovery.py", line 229, in
>_find_tests_in_module
>event, full_path, top_level_dir):
>File "nose2/plugins/loader/eggdiscovery.py", line 78, in
>_find_tests_in_dir
>event, modname, dist):
>File "nose2/plugins/loader/eggdiscovery.py", line 62, in
>_find_tests_in_egg_dir
>for test in self._find_tests_in_egg_dir(event, entry_path, dist):
>File "nose2/plugins/loader/eggdiscovery.py", line 62, in
>_find_tests_in_egg_dir
>for test in self._find_tests_in_egg_dir(event, entry_path, dist):
>File "nose2/plugins/loader/eggdiscovery.py", line 62, in
>_find_tests_in_egg_dir
>for test in self._find_tests_in_egg_dir(event, entry_path, dist):
>...
>nose2.plugins.loader.eggdiscovery: DEBUG: find in egg dir
>/build/1st/nose2-0.7.3/nose2/tests/functional/support/scenario/tests_in_zipped_eggs/pkgegg-0.0.0-py2.7.egg
>pkgegg/test/ (pkgegg)
>nose2.plugins.loader.eggdiscovery: DEBUG: find in egg dir
>/build/1st/nose2-0.7.3/nose2/tests/functional/support/scenario/tests_in_zipped_eggs/pkgegg-0.0.0-py2.7.egg
>pkgegg/test/ (pkgegg)
>- >> end captured logging << -
>--
>Ran 246 tests in 139.913s
>
>FAILED (errors=1, skipped=1)
>E: pybuild pybuild:283: test: plugin custom failed with: exit code=1:
>python2.7 -m nose2.__main__ -v
>dh_auto_test: pybuild --test -i python{version} -p 2.7 --system=custom
>"--test-args={interpreter} -m nose2.__main__ -v" returned exit code 13
>debian/rules:35: recipe for target 'override_dh_auto_test' failed
>make[1]: *** [override_dh_auto_test] Error 25
Control: tags -1 +upstream
Control: forwarded -1 https://github.com/nose-devs/nose2/issues/388

Thanks for reporting it.

Not sure about the severity but i'll let it as its for now.

Cheers ! 
-- 
PEB



Bug#889325: O: libreflectasm-java -- library that provides reflection by using code generation

2018-02-07 Thread Emmanuel Bourg
Control: Close -1

This package is team maintained.



Bug#889331: O: spock -- testing and specification framework for Java and Groovy application

2018-02-07 Thread Emmanuel Bourg
Control: Close -1

This package is team maintained.



Bug#889848: Acknowledgement (ruby2.5: Please include upstream patch to fix FTBFS on ia64)

2018-02-07 Thread John Paul Adrian Glaubitz
Oops, the previous patch contains some unnecessary cruft.
Attaching a cleaned-up version of the patch.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
Description: Fix FTBFS on ia64
 Fix FTBFS on ia64.
Author: Sergei Trofimovich 
Origin: https://github.com/ruby/ruby/commit/5af43b1ec2674e9f86090790bc61abdb96be14ff
Last-Update: 

--- ruby2.5-2.5.0.orig/cont.c
+++ ruby2.5-2.5.0/cont.c
@@ -475,7 +475,7 @@ cont_save_machine_stack(rb_thread_t *th,
 
 SET_MACHINE_STACK_END(>ec->machine.stack_end);
 #ifdef __ia64
-th->machine.register_stack_end = rb_ia64_bsp();
+th->ec->machine.register_stack_end = rb_ia64_bsp();
 #endif
 
 if (th->ec->machine.stack_start > th->ec->machine.stack_end) {
@@ -499,8 +499,8 @@ cont_save_machine_stack(rb_thread_t *th,
 
 #ifdef __ia64
 rb_ia64_flushrs();
-size = cont->machine.register_stack_size = th->machine.register_stack_end - th->machine.register_stack_start;
-cont->machine.register_stack_src = th->machine.register_stack_start;
+size = cont->machine.register_stack_size = th->ec->machine.register_stack_end - th->ec->machine.register_stack_start;
+cont->machine.register_stack_src = th->ec->machine.register_stack_start;
 if (cont->machine.register_stack) {
 	REALLOC_N(cont->machine.register_stack, VALUE, size);
 }
--- ruby2.5-2.5.0.orig/thread.c
+++ ruby2.5-2.5.0/thread.c
@@ -132,7 +132,7 @@ static inline void blocking_region_end(r
 
 #ifdef __ia64
 #define RB_GC_SAVE_MACHINE_REGISTER_STACK(th)  \
-do{(th)->machine.register_stack_end = rb_ia64_bsp();}while(0)
+do{(th)->ec->machine.register_stack_end = rb_ia64_bsp();}while(0)
 #else
 #define RB_GC_SAVE_MACHINE_REGISTER_STACK(th)
 #endif


Bug#889324: O: tiles -- Java templating framework for web application user interfaces

2018-02-07 Thread Emmanuel Bourg
Control: Close -1

This package is team maintained.



Bug#889316: O: plexus-containers1.5 -- Plexus IoC Container core with companion tools

2018-02-07 Thread Emmanuel Bourg
Control: Close -1

This package is team maintained.



Bug#889327: O: eigenbase-resgen -- Java i18n code generator from XML files

2018-02-07 Thread Emmanuel Bourg
Control: Close -1

This package is team maintained.



Bug#889322: O: aspectj -- aspect-oriented extension for Java - tools

2018-02-07 Thread Emmanuel Bourg
Control: Close -1

This package is team maintained.



Bug#889326: O: mondrian -- OLAP server written in Java

2018-02-07 Thread Emmanuel Bourg
Control: Close -1

This package is team maintained.



Bug#889345: O: easyconf -- library to access configuration of software components

2018-02-07 Thread Emmanuel Bourg
Control: Close -1

This package is team maintained.



Bug#889363: O: sqlline -- JDBC command-line utility for issuing SQL

2018-02-07 Thread Emmanuel Bourg
Control: Close -1

This package is team maintained.



Bug#889343: O: jasypt -- java library for simple high-level encryption

2018-02-07 Thread Emmanuel Bourg
Control: Close -1

This package is team maintained.



Bug#889342: O: bindex -- OSGi BIndex reader

2018-02-07 Thread Emmanuel Bourg
Control: Close -1

This package is team maintained.



Bug#889338: O: felix-gogo-shell -- Apache Felix Gogo Shell bundle

2018-02-07 Thread Emmanuel Bourg
Control: Close -1

This package is team maintained.



Bug#889341: O: ognl -- Java expression language

2018-02-07 Thread Emmanuel Bourg
Control: Close -1

This package is team maintained.



Bug#889340: O: felix-gogo-runtime -- Apache Felix Gogo Runtime bundle

2018-02-07 Thread Emmanuel Bourg
Control: Close -1

This package is team maintained.



Bug#889339: O: felix-gogo-command -- Apache Felix Gogo Command bundle

2018-02-07 Thread Emmanuel Bourg
Control: Close -1

This package is team maintained.



Bug#889337: O: portlet-api-2.0-spec -- Java Portlet Specification V2.0

2018-02-07 Thread Emmanuel Bourg
Control: Close -1

This package is team maintained.



Bug#889370: O: felix-shell -- Felix OSGi shell to issue commands to the framework

2018-02-07 Thread Emmanuel Bourg
Control: Close -1

This package is team maintained.



Bug#889364: O: werken.xpath -- JDOM XPath Engine

2018-02-07 Thread Emmanuel Bourg
Control: Close -1

This package is team maintained.



Bug#889371: O: felix-osgi-obr -- OSGi OBR Service API

2018-02-07 Thread Emmanuel Bourg
Control: Close -1

This package is team maintained.



Bug#889365: O: tomcat-native -- Tomcat native library using the Apache Portable Runtime

2018-02-07 Thread Emmanuel Bourg
Control: Close -1

This package is team maintained.



Bug#889368: O: olap4j -- unified Java API to access an OLAP server

2018-02-07 Thread Emmanuel Bourg
Control: Close -1

This package is team maintained.



Bug#889366: O: gentlyweb-utils -- java utility library used by josql

2018-02-07 Thread Emmanuel Bourg
Control: Close -1

This package is team maintained.



Bug#889369: O: felix-shell-tui -- Apache Felix Shell TUI

2018-02-07 Thread Emmanuel Bourg
Control: Close -1

This package is team maintained.



Bug#889380: O: libspring-java -- modular Java/J2EE application framework - Core

2018-02-07 Thread Emmanuel Bourg
Control: Close -1

This package is team maintained.



Bug#889400: O: sisu-ioc -- JSR 330 container and OSGi/Plexus adapter

2018-02-07 Thread Emmanuel Bourg
Control: Close -1

This package is team maintained.



Bug#889373: O: uima-as -- Apache UIMA Asynch Scaleout framework

2018-02-07 Thread Emmanuel Bourg
Control: Close -1

This package is team maintained.



Bug#889382: O: mvel -- expression language for Java-based applications - Library

2018-02-07 Thread Emmanuel Bourg
Control: Close -1

This package is team maintained.



Bug#889391: O: async-http-client -- Java Asynchronous HTTP Client

2018-02-07 Thread Emmanuel Bourg
Control: Close -1

This package is team maintained.



Bug#889374: O: activemq -- Java message broker core libraries

2018-02-07 Thread Emmanuel Bourg
Control: Close -1

This package is team maintained.



Bug#889376: O: jasperreports -- Java reporting generator library

2018-02-07 Thread Emmanuel Bourg
Control: Close -1

This package is team maintained.



  1   2   3   >