Bug#863267: marked as done (python-django: Upgrades from jessie to stretch)

[Debian Bug Tracking System]

Your message dated Wed, 24 May 2017 23:57:46 -0400
with message-id <1530639.3EspIQlAHj@kitterma-e6430>
and subject line Re: [Python-modules-team] Bug#863267: python-django: Upgrades 
from jessie to stretch
has caused the Debian Bug report #863267,
regarding python-django: Upgrades from jessie to stretch
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
863267: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863267
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django
Version: 1:1.10.7-1
Severity: serious
Control: block 847277 by -1
Control: block 863259 by -1

This bug is based on #847277, #863259, and the related
discussion on the debian-backports list.

If upgrading from 1.7 in jessie to 1.10 in stretch is not
fully supported unless upgrading through 1.8, then 1.8 is
required in stretch.

Either in addition to 1.10 (with properly supported and
documented 1.7 -> 1.8 -> 1.10 upgrade paths), or as 2:1.8

If lava-server is in a special situation due to doing
something very uncommon, then this bug should be closed
and the severity of #847277 set back to RC (with the likely
consequence that lava-server won't be part of stretch).
--- End Message ---
--- Begin Message ---
On Wednesday, May 24, 2017 07:01:38 PM Adrian Bunk wrote:
> Source: python-django
> Version: 1:1.10.7-1
> Severity: serious
> Control: block 847277 by -1
> Control: block 863259 by -1
> 
> This bug is based on #847277, #863259, and the related
> discussion on the debian-backports list.
> 
> If upgrading from 1.7 in jessie to 1.10 in stretch is not
> fully supported unless upgrading through 1.8, then 1.8 is
> required in stretch.
> 
> Either in addition to 1.10 (with properly supported and
> documented 1.7 -> 1.8 -> 1.10 upgrade paths), or as 2:1.8
> 
> If lava-server is in a special situation due to doing
> something very uncommon, then this bug should be closed
> and the severity of #847277 set back to RC (with the likely
> consequence that lava-server won't be part of stretch).

This bug is not at all correct.  I don't know about LAVA, but Django upgrades 
just fine.

Scott K--- End Message ---

Bug#863286: completely broken in non-US locales

[Daurnimator]

On 25 May 2017 at 08:03, Steinar H. Gunderson  wrote:
> lua-http cannot construct legal requests if a non-US locale (or more 
> precisely,
> anything using comma as decimal separator) is in use.

Fixed upstream in
https://github.com/daurnimator/lua-http/commit/f822bbef48f8ee6b42ce4cca843d4cc10cd0f775

Bug#863290: src:linux: no warning that btrfs RAID5/6 is buggered up

[Ben Hutchings]

On Thu, 2017-05-25 at 00:19 +0200, Adam Borowski wrote:
[...]
> There's no config setting to disable RAID5/6, such a setting would also make
> it hard to migrate to supported raid levels as you need to mount rw in order
> to convert.  And, you really hate non-trivial divergences from upstream.
> 
> A proposed warning patch attached.

Haven't looked closely, but I'm OK with this in principle.  I think we
should also taint the kernel (like we do for FAN_ALL_PERM_EVENTS).

Ben.

-- 
Ben Hutchings
Life would be so much easier if we could look at the source code.


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

Processed: Re: Bug#740893: libjs-jquery-hotkeys: Incompatible ABI change

[Debian Bug Tracking System]

Processing control commands:

> unblock 848188 by 740893
Bug #848188 [python-coverage] python-coverage: Avoid broken ‘jquery.hotkeys.js’ 
version
848188 was blocked by: 740893
848188 was not blocking any bugs.
Removed blocking bug(s) of 848188: 740893
> summary 848188 0
Summary recorded from message bug 848188 message 63

-- 
740893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740893
848188: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848188
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#740893: libjs-jquery-hotkeys: Incompatible ABI change

[Debian Bug Tracking System]

Processing control commands:

> unblock 848188 by 740893
Bug #848188 [python-coverage] python-coverage: Avoid broken ‘jquery.hotkeys.js’ 
version
848188 was not blocked by any bugs.
848188 was not blocking any bugs.
Removed blocking bug(s) of 848188: 740893
> summary 848188 0
Ignoring request to change the summary of bug 848188 to the same value

-- 
848188: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848188
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#740893: libjs-jquery-hotkeys: Incompatible ABI change

[Ben Finney]

Control: unblock 848188 by 740893
Control: summary 848188 0

Until the ‘libjs-jquery-hotkeys’ package resolves bug#740893, the
‘python-coverage’ packages should not use that library.

I will patch the ‘python-coverage’ source so it omits any use of that
library.

On 06-Apr-2017, Philipp Hahn wrote:
> 
> introduced an incompatible ABI change how events are registered:

Thanks again for the analysis, I hope this package can be fixed for
its dependents.

-- 
 \  “The trouble with the rat race is that even if you win, you're |
  `\   still a rat.” —Jane Wagner, via Lily Tomlin |
_o__)  |
Ben Finney 


signature.asc
Description: PGP signature

Processed: fixed 862999 in 3.22.1-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 862999 3.22.1-1
Bug #862999 [totem] totem: crash of totem about join-packages at the start of 
"vidéos" (french version)
Marked as fixed in versions totem/3.22.1-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
862999: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862999
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: fixed 862837 in 0.9.1-9

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 862837 0.9.1-9
Bug #862837 [xrdp] xrdp: Package install failure - dpkg: error processing 
package xrdp (--configure)
Marked as fixed in versions xrdp/0.9.1-9.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
862837: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862837
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: notfound 862837 in 0.9.1-4

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> notfound 862837 0.9.1-4
Bug #862837 [xrdp] xrdp: Package install failure - dpkg: error processing 
package xrdp (--configure)
No longer marked as found in versions xrdp/0.9.1-4.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
862837: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862837
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: notfound 862999 in 3.22.1-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> notfound 862999 3.22.1-1
Bug #862999 [totem] totem: crash of totem about join-packages at the start of 
"vidéos" (french version)
Ignoring request to alter found versions of bug #862999 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
862999: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862999
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: notfound 862837 in 0.9.1-9

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> notfound 862837 0.9.1-9
Bug #862837 [xrdp] xrdp: Package install failure - dpkg: error processing 
package xrdp (--configure)
Ignoring request to alter found versions of bug #862837 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
862837: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862837
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#862249: marked as done (Mounting an SFTP share with path may lead to data being deleted)

[Debian Bug Tracking System]

Your message dated Thu, 25 May 2017 00:05:06 +0200
with message-id 
and subject line Re: Bug#862249: Mounting an SFTP share with path may lead to 
data being deleted
has caused the Debian Bug report #862249,
regarding Mounting an SFTP share with path may lead to data being deleted
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
862249: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862249
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nautilus
Version: 3.22.3-1
Severity: critical

Hello,

I just discovered a severe bug in the sftp protocol support of nautilus:

I tried to mount a remote folder via SFTP/SSH by using a syntax similar
to the following:

'sftp:///path/to/directory'. Instead of displaying
'/path/to/directory' on the remote host, nautilus kept giving warnings
that it doesn't know what to do with file 'directory' and moved to the
home directory on the remote host.

I tried it with different syntax (colon between host and path, 'user@'
in front of host, using 'ssh://' instead of 'sftp://') and I tried both
using the 'Andere Orte' (something like 'different locations' in
english) and the address bar (+). One time nautilus even
crashed (the Files window got closed).

After some time, I went back to the remote console SSH session and was
shocked to realize that the whole directory '/path/to/directory' was
removed on the remote host. Luckily I had backups.

I don't have time to do further debugging right now as I'm quite busy,
but I will do further debugging and try to find a clear reproducer in
the following days.

Kind regards
 jonas

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

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

Versions of packages nautilus depends on:
ii  desktop-file-utils 0.23-1
ii  gsettings-desktop-schemas  3.22.0-1
ii  gvfs   1.30.4-1
ii  libatk1.0-02.22.0-1
ii  libc6  2.24-10
ii  libcairo-gobject2  1.14.8-1
ii  libcairo2  1.14.8-1
ii  libexempi3 2.4.1-1
ii  libexif12  0.6.21-2+b2
ii  libgail-3-03.22.11-1
ii  libgdk-pixbuf2.0-0 2.36.5-2
ii  libglib2.0-0   2.50.3-2
ii  libglib2.0-data2.50.3-2
ii  libgnome-autoar-0-00.1.1-4+b1
ii  libgnome-desktop-3-12  3.22.2-1
ii  libgtk-3-0 3.22.11-1
ii  libnautilus-extension1a3.22.3-1
ii  libpango-1.0-0 1.40.5-1
ii  libselinux12.6-3+b1
ii  libtracker-sparql-1.0-01.10.5-1
ii  libx11-6   2:1.6.4-3
ii  nautilus-data  3.22.3-1
ii  shared-mime-info   1.8-1

Versions of packages nautilus recommends:
ii  gnome-sushi  3.21.91-2
ii  gvfs-backends1.30.4-1
ii  librsvg2-common  2.40.16-1+b1

Versions of packages nautilus suggests:
ii  brasero  3.12.1-4
ii  eog  3.20.5-1+b1
ii  evince [pdf-viewer]  3.22.1-3
ii  nautilus-sendto  3.8.4-2+b1
ii  okular [pdf-viewer]  4:16.08.2-1+b1
ii  totem3.22.1-1
ii  tracker  1.10.5-1
ii  vlc [mp3-decoder]2.2.5-1
ii  xdg-user-dirs0.15-2+b1

-- no debconf information
--- End Message ---
--- Begin Message ---
Am 24.05.2017 um 23:20 schrieb John Paul Adrian Glaubitz:
> Control: tags -1 moreinfo
> 
> Hello Jonas!
> 
>> I don't have time to do further debugging right now as I'm quite busy,
>> but I will do further debugging and try to find a clear reproducer in
>> the following days.
> 
> It has been almost two weeks now. Could you please provide some more 
> information
> on how to reproduce this issue? Otherwise we would have to assume a 
> configuration
> error on your side and not an actual bug in nautilus.
> 
> RC bugs shouldn't be left without attention for too long as they are blocking
> the release of the next version of Debian.

Hi Adrian, hi Jason,

thanks for reminding me. I just spent some time trying to reproduce the
issue but I failed. Apparently something changed and now all my tests
mounting sftp/ssh folders with Nautilus succeeded.

I honestly don't understand it as I didn't change anything in the
meantime (using the same remote host, same client, no configuration
change). And I'm still pretty confident 

Processed: Re: Packaging (and RFS) for pymssql 2.1.1+dfsg-1

[Debian Bug Tracking System]

Processing control commands:

> severity 709210 grave
Bug #709210 [python-pymssql] python-pymssql: Valid select queries return no 
results
Bug #826475 [python-pymssql] pymssql fetch functions return nothing, traces 
back to freetdx and 1.0.x incompatibility
Severity set to 'grave' from 'important'
Severity set to 'grave' from 'important'

-- 
648230: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648230
709210: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709210
826475: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826475
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#863290: src:linux: no warning that btrfs RAID5/6 is buggered up

[Adam Borowski]

Package: src:linux
Version: 4.9.25-1
Severity: grave
Tags: patch

(Not sure what an appropriate severity is -- very likely total filesystem
loss screams "critical" but "please add a warning" might be even wishlist.)


Btrfs, while stable and reliable when using a subset of features, or at
least reasonable with some caveats on a bigger feature set, also includes a
couple of experimental eats-data-babies-and-kittens features.  The problem
is, (shouting warranted) THERE'S NO MENTION WHATSOEVER THEY'RE BROKEN!!!

One of those features, qgroups, notoriously causes bogus ENOSPC and kills
performance, but at least leaves data recoverable.

RAID5/6, not so.  It suffers from a number of both implementation and design
errors, resulting in frequent data loss.  Even worse, when such data loss
happens, in a good majority of cases you lose the whole filesystem.

Known implementation issues are mostly fixed in 4.12 (except for 32-bit
kernels which still insta-die the moment you say "scrub"), the design one
(write hole) will be harder to fix but is nowhere as nasty; because of
metadata write patterns, it is still likely to result in whole filesystem
loss but that's easily workable around -- btrfs supports different raid
levels for data-vs-metadata so an adventureous user might live with a
-draid5 -mraid1 profile.  On 4.12.

The last I checked, however, Stretch has kernel 4.9.

There's some discussion on the btrfs mailing list, but it is going quite
slowly; way too slow for a warning to filter past the usual channels
(mainline->GregKH->you) in time for Stretch.

It looks like there's a consensus that such a warning should live in the
kernel rather than userland -- on 4.12 64-bit -draid5/6 is already nowhere
as bad, it's very common to use new kernels on old userland.  This means my
beautiful fiery letters from
https://www.spinics.net/lists/linux-btrfs/msg60913.html will remain unused.

There's no config setting to disable RAID5/6, such a setting would also make
it hard to migrate to supported raid levels as you need to mount rw in order
to convert.  And, you really hate non-trivial divergences from upstream.

A proposed warning patch attached.


-- System Information:
Debian Release: 9.0
  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.12.0-rc1-debug-00011-gb82803d91ae5 (SMP w/6 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
>From 5ce4e611eab1a451332e0745ee91f787057e929b Mon Sep 17 00:00:00 2001
From: Adam Borowski 
Date: Tue, 28 Mar 2017 16:55:05 +0200
Subject: [PATCH] btrfs: warn about RAID5/6 being experimental at mount time

Too many people come complaining about losing their data -- and indeed,
there's no warning outside a wiki and the mailing list tribal knowledge.
Message severity chosen for consistency with XFS -- "alert" makes dmesg
produce nice red background which should get the point across.

Signed-off-by: Adam Borowski 
---
 fs/btrfs/disk-io.c | 8 
 1 file changed, 8 insertions(+)

diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
index 8685d67185d0..6aad1110602e 100644
--- a/fs/btrfs/disk-io.c
+++ b/fs/btrfs/disk-io.c
@@ -3068,6 +3068,14 @@ int open_ctree(struct super_block *sb,
btrfs_set_opt(fs_info->mount_opt, SSD);
}
 
+   if ((fs_info->avail_data_alloc_bits |
+fs_info->avail_metadata_alloc_bits |
+fs_info->avail_system_alloc_bits) &
+   BTRFS_BLOCK_GROUP_RAID56_MASK) {
+   btrfs_alert(fs_info,
+   "btrfs RAID5/6 is EXPERIMENTAL and has known data-loss bugs");
+   }
+
/*
 * Mount does not set all options immediately, we can do it now and do
 * not have to wait for transaction commit
-- 
2.11.0

Bug#863286: completely broken in non-US locales

[Steinar H. Gunderson]

Package: lua-http
Version: 0.1-1
Severity: grave
Tags: upstream

Hi,

lua-http cannot construct legal requests if a non-US locale (or more precisely,
anything using comma as decimal separator) is in use. Example:

  klump:~> cat test.lua
  os.setlocale('nb_NO.UTF-8')
  local http_request = require "http.request"
  local headers, stream = 
assert(http_request.new_from_uri("http://example.com;):go())
  local body = assert(stream:get_body_as_string())
  if headers:get ":status" ~= "200" then
  error(body)
  end
  print(body)
  
  klump:~> lua5.2 test.lua
  lua5.2: test.lua:6: 
  http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;>
  http://www.w3.org/1999/xhtml; xml:lang="en" lang="en">

505 - HTTP Version Not Supported


505 - HTTP Version Not Supported

  
  
  stack traceback:
[C]: in function 'error'
test.lua:6: in main chunk
[C]: in ?

This is because the request it constructs looks like this:

  GET / HTTP/1,1
  host: example.com
  user-agent: lua-http/0.1

Note the “1,1” in the HTTP version number where it should have been 1.1.

This makes the library completely broken for a large swath of Debian's user 
base;
thus the severity.

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

Kernel: Linux 4.11.2 (SMP w/40 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 861558 important
Bug #861558 [src:libpodofo] libpodofo: CVE-2017-6841
Severity set to 'important' from 'grave'
> severity 861562 important
Bug #861562 [src:libpodofo] libpodofo: CVE-2017-6845
Severity set to 'important' from 'grave'
> severity 861563 important
Bug #861563 [src:libpodofo] libpodofo: CVE-2017-6846
Severity set to 'important' from 'grave'
> severity 861566 important
Bug #861566 [src:libpodofo] libpodofo: CVE-2017-6849
Severity set to 'important' from 'grave'
> --
Stopping processing here.

Please contact me if you need assistance.
-- 
861558: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861558
861562: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861562
861563: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861563
861566: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861566
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#863106: quadrapassel: segfaults when unpausing an paused finished gmae

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 863106 https://bugzilla.gnome.org/show_bug.cgi?id=771541
Bug #863106 {Done: Chris Lamb } [quadrapassel] quadrapassel: 
segfaults when unpausing a paused finished game
Set Bug forwarded-to-address to 
'https://bugzilla.gnome.org/show_bug.cgi?id=771541'.
> tags 863106 + fixed-upstream
Bug #863106 {Done: Chris Lamb } [quadrapassel] quadrapassel: 
segfaults when unpausing a paused finished game
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
863106: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863106
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#863106: quadrapassel: segfaults when unpausing an paused finished gmae

[Chris Lamb]

forwarded 863106 https://bugzilla.gnome.org/show_bug.cgi?id=771541
tags 863106 + fixed-upstream
thanks

Hi Emilio,

> Also if you can forward the patch upstream at [1] that'd be great.

Done, in the sense of I located the duplicate. I don't think the upstream
fix is as good IMHO (it only ignores the unpause in the keypress catch, not
the in the "game" abstraction layer) so I won't re-upload just for that.


Regards,

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

Processed: Re: Bug#862249: Mounting an SFTP share with path may lead to data being deleted

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #862249 [nautilus] Mounting an SFTP share with path may lead to data being 
deleted
Added tag(s) moreinfo.

-- 
862249: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862249
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#862249: Mounting an SFTP share with path may lead to data being deleted

[John Paul Adrian Glaubitz]

Control: tags -1 moreinfo

Hello Jonas!

> I don't have time to do further debugging right now as I'm quite busy,
> but I will do further debugging and try to find a clear reproducer in
> the following days.

It has been almost two weeks now. Could you please provide some more information
on how to reproduce this issue? Otherwise we would have to assume a 
configuration
error on your side and not an actual bug in nautilus.

RC bugs shouldn't be left without attention for too long as they are blocking
the release of the next version of Debian.

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

Bug#862999: totem: crash of totem about join-packages at the start of "vidéos" (french version)

[John Paul Adrian Glaubitz]

Control: notfound -1 3.22.1-1
Control: tags -1 moreinfo

Hello Benoit!

Your bug report is incomplete and I'm not sure whether I understand what your
actual problem is. If I understand correctly, you have some videos that play
in VLC but don't play in totem?

Do you have any error messages? Are there any particular files that cannot be
played back? Can you link to a sample file where it doesn't work?

I just tried the totem package from unstable/testing and it works fine with
a standard mkv file. I'm therefore marking version 3.22.1-1 as unaffected.

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

Processed: Re: totem: crash of totem about join-packages at the start of "vidéos" (french version)

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 3.22.1-1
Bug #862999 [totem] totem: crash of totem about join-packages at the start of 
"vidéos" (french version)
Ignoring request to alter found versions of bug #862999 to the same values 
previously set
> tags -1 moreinfo
Bug #862999 [totem] totem: crash of totem about join-packages at the start of 
"vidéos" (french version)
Added tag(s) moreinfo.

-- 
862999: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862999
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#862837: xrdp: Package install failure - dpkg: error processing package xrdp (--configure)

[John Paul Adrian Glaubitz]

Control: notfound 0.9.1-4
Control: notfound 0.9.1-9

Hi!

This does not affect the version of xrdp in esting and unstable, so this needs
to be marked accordingly. I don't know why you marked this as found in 0.9.1-4
though because that version is currently not packaged anywhere in Debian, it
merely affects the version from jessie-backports which is 0.9.1-4~bpo8+1.

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

Bug#863283: cantor-backend-r: Cantor fails to start R server/session

[Rubén Gómez Antolí]

Package: cantor-backend-r
Version: 4:16.08.3-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

When I try to select R engine with Cantor, R fails to start and Cantor
is freeze on "starting session" window.

I paste console exit:

 Start Cantor from console ---
$ cantor
dir:  "/usr/lib/x86_64-linux-gnu/qt5/plugins/cantor/backends"
Error while loading plugin:  "."
Error while loading plugin:  ".."
Creating MaximaBackend
Creating NullBackend
Creating PythonBackend
Creating RBackend
dir:  "/usr/bin/cantor/backends"
Created a CantorPart
Backend  "R"  offers extensions:  ("ScriptExtension", "AdvancedPlotExtension")
Spawning a new R session
new worksheetaccess interface
()
()
()
()
()
()
()
()
()
()
()
()
(QKeySequence("Ctrl+Shift+S"))
(QKeySequence("Ctrl+S"))
()
(QKeySequence("Ctrl+Z"))
(QKeySequence("Ctrl+Shift+Z"))
(QKeySequence("Ctrl+X"), QKeySequence("Shift+Del"))
(QKeySequence("Ctrl+C"), QKeySequence("Ctrl+Ins"))
(QKeySequence("Ctrl+V"), QKeySequence("Shift+Ins"))
(QKeySequence("Ctrl+F"))
(QKeySequence("Ctrl+R"))
(QKeySequence("F3"))
(QKeySequence("Shift+F3"))
()
(QKeySequence("Ctrl+P"))
()
(QKeySequence("Ctrl++"), QKeySequence("Ctrl+="))
(QKeySequence("Ctrl+-"))
()
()
()
()
()
()
()
(QKeySequence("Shift+Return"))
(QKeySequence("Ctrl+Return"))
()
()
()
()
(QKeySequence("Shift+Del"))
()
()
()
()
loading assistants...
dir:  "/usr/lib/x86_64-linux-gnu/qt5/plugins/cantor/assistants"
Error while loading assistant:  "."
Error while loading assistant:  ".."
plugin  "Gráficos avanzados"  requires  ("AdvancedPlotExtension")
plugin  "Gráficos avanzados"  issupported by  "R"
KXMLGUI file found at deprecated location 
("/usr/share/cantor/cantor_advancedplot_assistant.rc") -- please use 
${KXMLGUI_INSTALL_DIR} to install this file instead.
plugin  "Crear matriz"  requires  ("LinearAlgebraExtension")
plugin  "Crear matriz"  is   not   supported by  "R"
plugin  "Diferenciar"  requires  ("CalculusExtension")
plugin  "Diferenciar"  is   not   supported by  "R"
plugin  "Eigenvalores"  requires  ("LinearAlgebraExtension", "HistoryExtension")
plugin  "Eigenvalores"  is   not   supported by  "R"
plugin  "Eigenvectores"  requires  ("LinearAlgebraExtension", 
"HistoryExtension")
plugin  "Eigenvectores"  is   not   supported by  "R"
plugin  "Importar paquete"  requires  ("PackagingExtension")
plugin  "Importar paquete"  is   not   supported by  "R"
plugin  "Integrar"  requires  ("CalculusExtension")
plugin  "Integrar"  is   not   supported by  "R"
plugin  "Invertir matriz"  requires  ("LinearAlgebraExtension", 
"HistoryExtension")
plugin  "Invertir matriz"  is   not   supported by  "R"
plugin  "Plot2d"  requires  ("PlotExtension")
plugin  "Plot2d"  is   not   supported by  "R"
plugin  "Plot3d"  requires  ("PlotExtension")
plugin  "Plot3d"  is   not   supported by  "R"
plugin  "QalculatePlot"  requires  ("QalculatePlotExtension")
plugin  "QalculatePlot"  is   not   supported by  "R"
plugin  "RunScript"  requires  ("ScriptExtension")
plugin  "RunScript"  issupported by  "R"
KXMLGUI file found at deprecated location 
("/usr/share/cantor/cantor_runscript_assistant.rc") -- please use 
${KXMLGUI_INSTALL_DIR} to install this file instead.
plugin  "Resolver"  requires  ("CASExtension")
plugin  "Resolver"  is   not   supported by  "R"
dir:  "/usr/bin/cantor/assistants"
loading panel plugins for session of type  "R"
dir:  "/usr/lib/x86_64-linux-gnu/qt5/plugins/cantor/panels"
Error while loading panel:  "."
Error while loading panel:  ".."
plugin  "Ayuda"  requires  ("")
Requesting capabilities of RSession
plugin  "Ayuda"  issupported
setting session to  0x55efb3b16c80
plugin  "Gestor de variables"  requires  ("VariableManagementExtension")
plugin  "Gestor de variables"  is   not   supported
dir:  "/usr/bin/cantor/panels"
Requesting capabilities of RSession
Requesting capabilities of RSession
login
wsStatusChange 1
storing plots at  "/tmp/cantor/rserver-29302"

R version 3.4.0 (2017-04-21) -- "You Stupid Darkness"
Copyright (C) 2017 The R Foundation for Statistical Computing
Platform: x86_64-pc-linux-gnu (64-bit)

R es un software libre y viene sin GARANTIA ALGUNA.
Usted puede redistribuirlo bajo ciertas circunstancias.
Escriba 'license()' o 'licence()' para detalles de distribucion.

R es un proyecto colaborativo con muchos contribuyentes.
Escriba 'contributors()' para obtener más información y
'citation()' para saber cómo citar R o paquetes de R en publicaciones.

Escriba 'demo()' para demostraciones, 'help()' para el sistema on-line de ayuda,
o 'help.start()' para abrir el sistema de ayuda HTML con su navegador.
Escriba 'q()' para salir de R.

setting up callbacks
integrating plots
running command  "png(filename=\"/tmp/cantor/rserver-29302/Rplot0.png\", width 
= 480, height = 480, units = \"px\")"
PARSING  "png(filename=\"/tmp/cantor/rserver-29302/Rplot0.png\", width = 480, 
height = 480, units = \"px\")"  went OK
done running
std:  ""  err:  ""
printing result...
internal result:  0 

Bug#863276: nvidia-driver: nvidia fails to initialize Xorg with linux-image-4.9.0-0.bpo.3-amd64

[NeatNerdPrime]

Package: nvidia-driver
Version: 375.39-1~bpo8+1
Severity: grave
File: nvidia-driver
Tags: upstream
Justification: causes non-serious data loss

Dear Maintainer,

TL;DR: please update nvidia driver to version 375.66 in backports, so it works
with backports kernel available.

Elaborate explanation:

When updating today to the newest kernel release available on jessie backports
(linux-image-4.9.0-0.bpo.3-amd64:amd64 and it's dependencies), after reboot,
the system refuses to start X. This is in conjunction with the Nvidia driver ,
also available from jessie backports nvidia-driver:amd64 (375.39-1~bpo8+1).
Restarting with a prior kernel version proved ineffective (DKMS modules were
installed), this seemed to be caused by various kernel components being
replaced, what the older kernel is not suited for.

When inspecting the logfile /var/log/messages it shows these lines that cause
the X server to constantly re-initialize and fail, /var/log/xorg.0.log shows
nothing useful. Logfile shown below steps of reproduction and possible
resolution (attached with this bugreport):


   * What led up to the situation?
- Upgrading to newest kernel release available from jessie-backports
(linux-image-4.9.0-0.bpo.3-amd64:amd64)
- dependencies installed with this kernel update:
- linux-headers-4.9.0-0.bpo.3-amd64:amd64
- linux-headers-4.9.0-0.bpo.3-common:amd64
- dependencies updated with this upgrade:
- linux-kbuild-4.9:amd64 (4.9.18-1~bpo8+1, 4.9.25-1~bpo8+1),
- linux-image-amd64:amd64 (4.9+79~bpo8+1, 4.9+80~bpo8+1),
- linux-headers-amd64:amd64 (4.9+79~bpo8+1, 4.9+80~bpo8+1),
- linux-compiler-gcc-4.9-x86:amd64 (4.9.18-1~bpo8+1,
4.9.25-1~bpo8+1)
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
- What was ineffective:
- booting from older kernels, DKMS modules ensured installed
- reinstalling/building modules with "sudo dkms install
module/version"
- reverting to prior packages, they are not available anymore
in backports
- Effective solution:
- remove all nvidia related packages from APT &&
- installing the nvidia driver from nvidia.com manually (.run
script from site): http://us.download.nvidia.com/XFree86/Linux-x86_64/375.66
/NVIDIA-Linux-x86_64-375.66.run

- Nvidia driver version that works: 375.66
   * What was the outcome of this action?
- After UNINSTALLING the nvidia software from APT and INSTALLING the
Nvidia driver from site script, the system started X again
   * What outcome did you expect instead?
- expected normal reboot after upgrading to newest kernel without
uninstalling nvidia software pacakges.


As for now it is unclear what really caused the breakage. Is it the kernel? Is
it the driver? My guts tell me it's the driver since it works with the newest
release from their site.

Additional information can be supplied on request.



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

Kernel: Linux 4.9.0-0.bpo.3-amd64 (SMP w/8 CPU cores)
Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8)
May 24 19:43:07 Agnes gdm-Xorg-:0[1370]: X.Org X Server 1.16.4
May 24 19:43:07 Agnes gdm-Xorg-:0[1370]: Release Date: 2014-12-20
May 24 19:43:07 Agnes gdm-Xorg-:0[1370]: X Protocol Version 11, Revision 0
May 24 19:43:07 Agnes gdm-Xorg-:0[1370]: Build Operating System: Linux 
3.16.0-4-amd64 x86_64 Debian
May 24 19:43:07 Agnes gdm-Xorg-:0[1370]: Current Operating System: Linux Agnes 
4.9.0-0.bpo.3-amd64 #1 SMP Debian 4.9.25-1~bpo8+1 (2017-05-19) x86_64
May 24 19:43:07 Agnes gdm-Xorg-:0[1370]: Kernel command line: 
BOOT_IMAGE=/vmlinuz-4.9.0-0.bpo.3-amd64 root=/dev/mapper/agnes-root ro quiet
May 24 19:43:07 Agnes gdm-Xorg-:0[1370]: Build Date: 11 February 2015  
12:32:02AM
May 24 19:43:07 Agnes gdm-Xorg-:0[1370]: xorg-server 2:1.16.4-1 
(http://www.debian.org/support)
May 24 19:43:07 Agnes gdm-Xorg-:0[1370]: Current version of pixman: 0.32.6
May 24 19:43:07 Agnes gdm-Xorg-:0[1370]: Before reporting problems, check 
http://wiki.x.org
May 24 19:43:07 Agnes gdm-Xorg-:0[1370]: to make sure that you have the latest 
version.
May 24 19:43:07 Agnes gdm-Xorg-:0[1370]: Markers: (--) probed, (**) from config 
file, (==) default setting,
May 24 19:43:07 Agnes gdm-Xorg-:0[1370]: (++) from command line, (!!) notice, 
(II) informational,
May 24 19:43:07 Agnes gdm-Xorg-:0[1370]: (WW) warning, (EE) error, (NI) not 
implemented, (??) unknown.
May 24 19:43:07 Agnes gdm-Xorg-:0[1370]: (==) Log file: "/var/log/Xorg.0.log", 
Time: Wed May 24 19:43:07 2017
May 24 19:43:07 Agnes gdm-Xorg-:0[1370]: (==) Using config file: 
"/etc/X11/xorg.conf"
May 24 19:43:07 Agnes gdm-Xorg-:0[1370]: (==) Using system config directory 

Processed: Re: Bug#863269: usrmerge is not yet ready for a stable release

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #863269 {Done: m...@linux.it (Marco d'Itri)} [usrmerge] usrmerge is not yet 
ready for a stable release
Bug reopened
Ignoring request to alter fixed versions of bug #863269 to the same values 
previously set
> block -1 by 838995 843461 810499 848622 842315
Bug #863269 [usrmerge] usrmerge is not yet ready for a stable release
863269 was blocked by: 837928 810158 860523 759410
863269 was not blocking any bugs.
Added blocking bug(s) of 863269: 848622, 843461, 842315, 810499, 838995, and 
843653

-- 
863269: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863269
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#863269: usrmerge is not yet ready for a stable release

[Adrian Bunk]

Control: reopen -1
Control: block -1 by 838995 843461 810499 848622 842315 

On Wed, May 24, 2017 at 06:29:33PM +0200, Marco d'Itri wrote:
> On May 24, Adrian Bunk  wrote:
> 
> > While merged /usr seems to be the future and will likely be the
> > default in buster, shipping the usrmerge package in stretch
> > wouldn't bring real benefits to users while creating situations
> > where the only proper solution for a user might be to reinstall.
> We already discussed this. I disagree.

If a member of the release team states that this is acceptable
for a stable release, then that's how it is.

Until then I prefer to keep this bug open.

> ciao,
> Marco

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#792934: marked as done (libebook-tools-perl: install_driver(SQLite) failed: Can't locate DBD/SQLite.pm in @INC)

[Debian Bug Tracking System]

Your message dated Wed, 24 May 2017 17:49:09 +
with message-id 
and subject line Bug#792934: fixed in libebook-tools-perl 0.5.4-1.3
has caused the Debian Bug report #792934,
regarding libebook-tools-perl: install_driver(SQLite) failed: Can't locate 
DBD/SQLite.pm in @INC
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
792934: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792934
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: libebook-tools-perl
Version: 0.5.4-1
Severity: serious
Justification: Policy §3.5

$ perl -e 'use EBook::Tools'
install_driver(SQLite) failed: Can't locate DBD/SQLite.pm in @INC (you may need 
to install the DBD::SQLite module) (@INC contains: /etc/perl 
/usr/local/lib/i386-linux-gnu/perl/5.20.2 /usr/local/share/perl/5.20.2 
/usr/lib/i386-linux-gnu/perl5/5.20 /usr/share/perl5 
/usr/lib/i386-linux-gnu/perl/5.20 /usr/share/perl/5.20 /usr/local/lib/site_perl 
.) at (eval 30) line 3.
Perhaps the DBD::SQLite perl module hasn't been fully installed,
or perhaps the capitalisation of 'SQLite' isn't right.
Available drivers: DBM, ExampleP, File, Gofer, Proxy, Sponge.
at /usr/share/perl5/EBook/Tools/BISG.pm line 326.
Compilation failed in require at -e line 1.
BEGIN failed--compilation aborted at -e line 1.


If you install libdbd-sqlite3-perl, the error goes away.


-- System Information:
Debian Release: stretch/sid
 APT prefers unstable
 APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 4.0.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libebook-tools-perl depends on:
ii  libarchive-zip-perl1.48-1
ii  libbit-vector-perl 7.4-1
ii  libconfig-inifiles-perl2.83-3
ii  libdate-manip-perl 6.50-1
ii  libdbi-perl1.633-1
ii  libencode-detect-perl  1.01-4
ii  libfile-mimeinfo-perl  0.27-1
ii  libfile-slurp-perl .19-4
ii  libfile-which-perl 1.18-1
ii  libhtml-parser-perl3.71-2
ii  libimage-size-perl 3.300-1
ii  liblingua-en-nameparse-perl1.32-1
ii  liblist-moreutils-perl 0.413-1
ii  libmojolicious-perl5.54+dfsg-1
ii  libossp-uuid-perl  1.6.2-1.5+b1
ii  libpalm-perl   1:1.013-1
ii  libstring-crc32-perl   1.5-1+b1
ii  libtie-ixhash-perl 1.23-2
ii  libwww-perl6.13-1
ii  libxml-twig-perl   1:3.48-1
ii  perl   5.20.2-6
ii  perl-modules [libtime-local-perl]  5.20.2-6
ii  txt2html   2.51-1

--
Jakub Wilk
--- End Message ---
--- Begin Message ---
Source: libebook-tools-perl
Source-Version: 0.5.4-1.3

We believe that the bug you reported is fixed in the latest version of
libebook-tools-perl, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 792...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Axel Beckert  (supplier of updated libebook-tools-perl package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 22 May 2017 22:59:07 +0200
Source: libebook-tools-perl
Binary: libebook-tools-perl
Architecture: source amd64
Version: 0.5.4-1.3
Distribution: unstable
Urgency: medium
Maintainer: Zed Pobre 
Changed-By: Axel Beckert 
Description:
 libebook-tools-perl - E-Book manipulation tool and Perl libraries
Closes: 792934
Changes:
 libebook-tools-perl (0.5.4-1.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Really add missing dependency on libdbd-sqlite3-perl. Thanks to Adrian
 Bunk for noticing. (Closes: #792934)
Checksums-Sha1:
 b6e66531b409d8efb1f0a9cc965b5e4bd6977287 2337 libebook-tools-perl_0.5.4-1.3.dsc
 551c3e773f10e9c8206f6bdd03513041e880b9b8 3197 
libebook-tools-perl_0.5.4-1.3.diff.gz
 00ea5bb34702e4b29f9b0c901c22c275ebe16c4d 7460 
libebook-tools-perl_0.5.4-1.3_amd64.buildinfo
 

Bug#863269: marked as done (usrmerge is not yet ready for a stable release)

[Debian Bug Tracking System]

Your message dated Wed, 24 May 2017 18:29:33 +0200
with message-id <20170524162933.xjxryuqc5jhmd...@bongo.bofh.it>
and subject line Re: Bug#863269: usrmerge is not yet ready for a stable release
has caused the Debian Bug report #863269,
regarding usrmerge is not yet ready for a stable release
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
863269: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863269
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: usrmerge
Version: 13
Severity: serious
Control: block -1 by 860523 810158 759410 837928

While merged /usr seems to be the future and will likely be the
default in buster, shipping the usrmerge package in stretch
wouldn't bring real benefits to users while creating situations
where the only proper solution for a user might be to reinstall.

Anyone explitely using "debootstrap --merged-usr" should be aware
that this is a non-default option, but just installing a package
shouldn't result in errors like the following in a stable release:

# apt-get install usrmerge
...
# apt-get install ksh
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libfile-find-rule-perl libnumber-compare-perl libtext-glob-perl
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
  binfmt-support
The following packages will be REMOVED:
  usrmerge
The following NEW packages will be installed:
  binfmt-support ksh
0 upgraded, 2 newly installed, 1 to remove and 0 not upgraded.
Need to get 950 kB of archives.
After this operation, 3521 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://deb.debian.org/debian stretch/main amd64 binfmt-support amd64 
2.1.6-2 [59.5 kB]
Get:2 http://deb.debian.org/debian stretch/main amd64 ksh amd64 
93u+20120801-2+b1 [890 kB]
Fetched 950 kB in 0s (1137 kB/s)
E: Can not write log (Is /dev/pts mounted?) - posix_openpt (2: No such file or 
directory)
(Reading database ... 10978 files and directories currently installed.)
Removing usrmerge (13) ...
Selecting previously unselected package binfmt-support.
(Reading database ... 10972 files and directories currently installed.)
Preparing to unpack .../binfmt-support_2.1.6-2_amd64.deb ...
Unpacking binfmt-support (2.1.6-2) ...
Selecting previously unselected package ksh.
Preparing to unpack .../ksh_93u+20120801-2+b1_amd64.deb ...
Unpacking ksh (93u+20120801-2+b1) ...
Setting up binfmt-support (2.1.6-2) ...
Created symlink 
/etc/systemd/system/multi-user.target.wants/binfmt-support.service -> 
/lib/systemd/system/binfmt-support.service.
Running in chroot, ignoring request.
Setting up ksh (93u+20120801-2+b1) ...
update-alternatives: using /bin/ksh93 to provide /bin/ksh (ksh) in auto mode
update-alternatives: error: unable to install '/usr/bin/ksh.dpkg-tmp' as 
'/usr/bin/ksh': No such file or directory
dpkg: error processing package ksh (--configure):
 subprocess installed post-installation script returned error exit status 2
Processing triggers for systemd (232-23) ...
Errors were encountered while processing:
 ksh
E: Sub-process /usr/bin/dpkg returned an error code (1)
# 

Additionally, there is also an unknown number of runtime bugs
like #860523 where code makes path assumptions that break with
merged /usr. And there is no good way to find these automatically,
only a longer time of merged /usr as default in testing/unstable
would find them.

The worst part is that the merged /usr via "apt-get install usrmerge"
is irreversible, and having to tell users of stable that they have
to reinstall for reverting it would be a huge blow for the stable
reputation of Debian.
--- End Message ---
--- Begin Message ---
On May 24, Adrian Bunk  wrote:

> While merged /usr seems to be the future and will likely be the
> default in buster, shipping the usrmerge package in stretch
> wouldn't bring real benefits to users while creating situations
> where the only proper solution for a user might be to reinstall.
We already discussed this. I disagree.

-- 
ciao,
Marco


signature.asc
Description: PGP signature
--- End Message ---

Bug#863269: usrmerge is not yet ready for a stable release

[Adrian Bunk]

Package: usrmerge
Version: 13
Severity: serious
Control: block -1 by 860523 810158 759410 837928

While merged /usr seems to be the future and will likely be the
default in buster, shipping the usrmerge package in stretch
wouldn't bring real benefits to users while creating situations
where the only proper solution for a user might be to reinstall.

Anyone explitely using "debootstrap --merged-usr" should be aware
that this is a non-default option, but just installing a package
shouldn't result in errors like the following in a stable release:

# apt-get install usrmerge
...
# apt-get install ksh
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libfile-find-rule-perl libnumber-compare-perl libtext-glob-perl
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
  binfmt-support
The following packages will be REMOVED:
  usrmerge
The following NEW packages will be installed:
  binfmt-support ksh
0 upgraded, 2 newly installed, 1 to remove and 0 not upgraded.
Need to get 950 kB of archives.
After this operation, 3521 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://deb.debian.org/debian stretch/main amd64 binfmt-support amd64 
2.1.6-2 [59.5 kB]
Get:2 http://deb.debian.org/debian stretch/main amd64 ksh amd64 
93u+20120801-2+b1 [890 kB]
Fetched 950 kB in 0s (1137 kB/s)
E: Can not write log (Is /dev/pts mounted?) - posix_openpt (2: No such file or 
directory)
(Reading database ... 10978 files and directories currently installed.)
Removing usrmerge (13) ...
Selecting previously unselected package binfmt-support.
(Reading database ... 10972 files and directories currently installed.)
Preparing to unpack .../binfmt-support_2.1.6-2_amd64.deb ...
Unpacking binfmt-support (2.1.6-2) ...
Selecting previously unselected package ksh.
Preparing to unpack .../ksh_93u+20120801-2+b1_amd64.deb ...
Unpacking ksh (93u+20120801-2+b1) ...
Setting up binfmt-support (2.1.6-2) ...
Created symlink 
/etc/systemd/system/multi-user.target.wants/binfmt-support.service -> 
/lib/systemd/system/binfmt-support.service.
Running in chroot, ignoring request.
Setting up ksh (93u+20120801-2+b1) ...
update-alternatives: using /bin/ksh93 to provide /bin/ksh (ksh) in auto mode
update-alternatives: error: unable to install '/usr/bin/ksh.dpkg-tmp' as 
'/usr/bin/ksh': No such file or directory
dpkg: error processing package ksh (--configure):
 subprocess installed post-installation script returned error exit status 2
Processing triggers for systemd (232-23) ...
Errors were encountered while processing:
 ksh
E: Sub-process /usr/bin/dpkg returned an error code (1)
# 

Additionally, there is also an unknown number of runtime bugs
like #860523 where code makes path assumptions that break with
merged /usr. And there is no good way to find these automatically,
only a longer time of merged /usr as default in testing/unstable
would find them.

The worst part is that the merged /usr via "apt-get install usrmerge"
is irreversible, and having to tell users of stable that they have
to reinstall for reverting it would be a huge blow for the stable
reputation of Debian.

Processed: usrmerge is not yet ready for a stable release

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 860523 810158 759410 837928
Bug #863269 [usrmerge] usrmerge is not yet ready for a stable release
863269 was not blocked by any bugs.
863269 was not blocking any bugs.
Added blocking bug(s) of 863269: 837928, 860523, 759410, and 810158

-- 
863269: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863269
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#863267: python-django: Upgrades from jessie to stretch

[Adrian Bunk]

Source: python-django
Version: 1:1.10.7-1
Severity: serious
Control: block 847277 by -1
Control: block 863259 by -1

This bug is based on #847277, #863259, and the related
discussion on the debian-backports list.

If upgrading from 1.7 in jessie to 1.10 in stretch is not
fully supported unless upgrading through 1.8, then 1.8 is
required in stretch.

Either in addition to 1.10 (with properly supported and
documented 1.7 -> 1.8 -> 1.10 upgrade paths), or as 2:1.8

If lava-server is in a special situation due to doing
something very uncommon, then this bug should be closed
and the severity of #847277 set back to RC (with the likely
consequence that lava-server won't be part of stretch).

Processed: python-django: Upgrades from jessie to stretch

[Debian Bug Tracking System]

Processing control commands:

> block 847277 by -1
Bug #847277 [lava-server] django migrations in jessie require django from 
jessie-backports to upgrade to stretch
847277 was not blocked by any bugs.
847277 was not blocking any bugs.
Added blocking bug(s) of 847277: 863267
> block 863259 by -1
Bug #863259 [release-notes] document that jessie2stretch upgrades need to 
involve backports if django is upgraded
863259 was not blocked by any bugs.
863259 was not blocking any bugs.
Added blocking bug(s) of 863259: 863267

-- 
847277: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847277
863259: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863259
863267: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863267
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#858539: marked as done (ca-certificates: Contains untrusted StartCom and WoSign certificates)

[Debian Bug Tracking System]

Your message dated Wed, 24 May 2017 15:48:45 +
with message-id 
and subject line Bug#858539: fixed in ca-certificates 20161130+nmu1
has caused the Debian Bug report #858539,
regarding ca-certificates: Contains untrusted StartCom and WoSign certificates
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
858539: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858539
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ca-certificates
Version: 20141019+deb8u2
Severity: important
Tags: security

Hi,

StartCom and WoSign certificates are now untrusted by the major browser
vendors[0][1], making websites that use certs from these vendors
inaccessible.

However, as this is not reflected in ca-certificates, tools such as curl
still intepret these as valid/secure.

(This has a knock-on effect that health-check tools that use the output
of such tools to determine whether a site is "up" — eg. updown.io — will
misleadingly imply that the site is available to users when, in all
practical senses, they are not.)

I would suggest we remove the offending authorities from ca-certificates
as soon as possible.


[0] 
https://blog.mozilla.org/security/2016/10/24/distrusting-new-wosign-and-startcom-certificates/
[1] My installation "chrome-stable" rejects them as well.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: ca-certificates
Source-Version: 20161130+nmu1

We believe that the bug you reported is fixed in the latest version of
ca-certificates, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 858...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated ca-certificates package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 19 May 2017 16:53:16 +0200
Source: ca-certificates
Binary: ca-certificates ca-certificates-udeb
Architecture: source all
Version: 20161130+nmu1
Distribution: unstable
Urgency: medium
Maintainer: Michael Shuler 
Changed-By: Chris Lamb 
Description:
 ca-certificates - Common CA certificates
 ca-certificates-udeb - Common CA certificates - udeb (udeb)
Closes: 858539
Changes:
 ca-certificates (20161130+nmu1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add StartCom and WoSign certificates to mozilla/blacklist.txt as they are
 now untrusted by the major browser vendors. Closes: #858539
Checksums-Sha1:
 f599c3a2a1610db575840e0fb008ea7103184b8b 1886 ca-certificates_20161130+nmu1.dsc
 0a5f4cfde484de562c711044ec85ea7cdc54318d 298648 
ca-certificates_20161130+nmu1.tar.xz
 ea4d034472615b20124b060c26b3f37d8e9d1025 151078 
ca-certificates-udeb_20161130+nmu1_all.udeb
 eab87c1cfabf5da427365c2826432b684f62fec2 195794 
ca-certificates_20161130+nmu1_all.deb
 861b048cfbc147e502aa1e026f6b75c6d8d2725d 6100 
ca-certificates_20161130+nmu1_amd64.buildinfo
Checksums-Sha256:
 09e8d33c479827b070719170a9a98de7c1d4e9c7973ed8556321d08d8ae27494 1886 
ca-certificates_20161130+nmu1.dsc
 77f9aca431e3122bf04aa0ffd989b723d906db4d1c106e3290e463d73c177f0e 298648 
ca-certificates_20161130+nmu1.tar.xz
 9643f55c0eeac414155340aa553e12b4f3a9c080f5226af9ebc886cb712698df 151078 
ca-certificates-udeb_20161130+nmu1_all.udeb
 25d6f749c4fb33ae0d7999c2c7c52b842a8b6e5487f3a5c1e61b3c21f90ac452 195794 
ca-certificates_20161130+nmu1_all.deb
 d6a346c124f7415d2dc61ea4f62657265a2af9c4cbcffe8982b39c57c00250ed 6100 
ca-certificates_20161130+nmu1_amd64.buildinfo
Files:
 50d47199c79c936633e4048edf410c66 1886 misc optional 
ca-certificates_20161130+nmu1.dsc
 a09e8b63126188fd0ed77f6fbaf5d35f 298648 misc optional 
ca-certificates_20161130+nmu1.tar.xz
 13def6a0b886d635d9c5f57973d486d3 151078 debian-installer optional 
ca-certificates-udeb_20161130+nmu1_all.udeb
 3eed7f5c0075abe44f932df597312af0 195794 misc optional 
ca-certificates_20161130+nmu1_all.deb
 66b2d6b55abfc28a19d29ae058ce771c 6100 misc optional 
ca-certificates_20161130+nmu1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Bug#857531: marked as done (spambayes: broken symlink: /usr/bin/sb_notesfilter.py -> /usr/bin/sb_notesfilter)

[Debian Bug Tracking System]

Your message dated Wed, 24 May 2017 15:19:08 +
with message-id 
and subject line Bug#857531: fixed in spambayes 1.1b1-2
has caused the Debian Bug report #857531,
regarding spambayes: broken symlink: /usr/bin/sb_notesfilter.py -> 
/usr/bin/sb_notesfilter
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
857531: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857531
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: spambayes
Version: 1.1b1-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...):

0m32.2s ERROR: FAIL: Broken symlinks:
  /usr/bin/sb_notesfilter.py -> /usr/bin/sb_notesfilter


cheers,

Andreas


spambayes_1.1b1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: spambayes
Source-Version: 1.1b1-2

We believe that the bug you reported is fixed in the latest version of
spambayes, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 857...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Hugo Lefeuvre  (supplier of updated spambayes package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 24 May 2017 15:09:12 +0200
Source: spambayes
Binary: spambayes
Architecture: source all
Version: 1.1b1-2
Distribution: experimental
Urgency: low
Maintainer: Python Applications Packaging Team 

Changed-By: Hugo Lefeuvre 
Description:
 spambayes  - Python-based spam filter using statistical analysis
Closes: 789564 857531
Changes:
 spambayes (1.1b1-2) experimental; urgency=low
 .
   * Acknowledge NMU (Closes: #857531). Thanks Marcio !
   * debian/control:
 - Update Hugo Lefeuvre's e-mail address.
 - Depend on debhelper 10 instead of 5.
 - Bump Standards-Version to 3.9.8.
 - Remove useless version indication in the python dependency.
   * Bump debian/compat to 10.
   * Port debian/rules to pybuild.
   * debian/copyright:
 - Make debian/copyright DEP5 compliant.
 - Re-license debian/* to GPL-3+ (Approved by Alexandre Fayolle).
 - Update Hugo Lefeuvre's e-mail address.
   * Upstream changelog is automatically installed, stop mentionning
 it in debian/spambayes.docs
   * Remove debian/TODO, not up-to-date anymore.
   * debian/patches/lockfile.patch:
 - Compatibility with newer python-lockfile (>> 0.10) (Closes: #789564)
Checksums-Sha1:
 87c910a03267c00286c999febec49c3ca8a9a96b 2050 spambayes_1.1b1-2.dsc
 e42fd5f9dbbcef7ac9d8747dc498e57f092ea704 12308 spambayes_1.1b1-2.debian.tar.xz
 4e977969ceed6cea0e7ba8762bdb92a33a29d509 395776 spambayes_1.1b1-2_all.deb
 b4d7c7018a19649c4324af4578b98080769e76dc 6091 spambayes_1.1b1-2_amd64.buildinfo
Checksums-Sha256:
 48f5b937dcefe68f2fc6b1de3686ca6e27c63582d1b85a8f72e5851635f03b8f 2050 
spambayes_1.1b1-2.dsc
 320f49e3f3d64199f1bfde1b38a1e92226cf94b1d608dd768cfad5188fc614b6 12308 
spambayes_1.1b1-2.debian.tar.xz
 740384dea52672dbf0db380ba21708962b255298d783fc7ad12b9382a2250ff8 395776 
spambayes_1.1b1-2_all.deb
 2255a7e8d6449e2226d04614568856bf6d068b5ae1657a8588023f6c9ee62175 6091 
spambayes_1.1b1-2_amd64.buildinfo
Files:
 bfbb83251006ce29a0cc755ef354cde5 2050 mail optional spambayes_1.1b1-2.dsc
 90f6fb48299e47cf69898b3c0199756e 12308 mail optional 
spambayes_1.1b1-2.debian.tar.xz
 c3bb5853899fcd4e399b716b818701c9 395776 mail optional spambayes_1.1b1-2_all.deb
 e00633df0fa0322669f1366c4d67ae3f 6091 mail optional 
spambayes_1.1b1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCAAtFiEErLe2fxl/mzIVM0McrJCsPsUkBl4FAlklnecPHGhsZUBkZWJp
YW4ub3JnAAoJEKyQrD7FJAZe+JYQALwLY/hr81p5Romp0I2t8qhSAYkWt8YC0Xs8
W6Lz0CWOJdTzRHT2qNy+yp95+AFFJCI0w5hdjBuogp/8kUBLwDGO5iE7UFJnk0IL
MHNrLJDeBKXjZQtzz9oKzgu8AdX9yhDSB6MozeW0zxBVotS1kQIQBuFcyNhXCtp8
c7iSI/NxFKhohgsKZxj/axWSNhQQR0299OJXLOH7d+TRILReW9TcRIKRGVwrEcbq
4UMBNVpgW1e06PNXSvTiCOujrTuEWYcP23dPM7f4K0QZt2CIyTFZAjg83K6E2pTX
+Y4OjpedjNwbS+pJvT/OODoUTJvRd/JdPywP5GV48rBLtRKUDs3Nu8arRLo3GNhg

Bug#860567: marked as done (fop: CVE-2017-5661: information disclosure vulnerability)

[Debian Bug Tracking System]

Your message dated Wed, 24 May 2017 15:04:51 +
with message-id 
and subject line Bug#860567: fixed in fop 1:2.1-6
has caused the Debian Bug report #860567,
regarding fop: CVE-2017-5661: information disclosure vulnerability
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
860567: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860567
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fop
Version: 1:1.0.dfsg-1
Severity: important
Tags: upstream security

Hi,

the following vulnerability was published for fop.

CVE-2017-5661[0]:
| In Apache FOP before 2.2, files lying on the filesystem of the server
| which uses FOP can be revealed to arbitrary users who send maliciously
| formed SVG files. The file types that can be shown depend on the user
| context in which the exploitable application is running. If the user
| is root a full compromise of the server - including confidential or
| sensitive files - would be possible. XXE can also be used to attack
| the availability of the server via denial of service as the references
| within a xml document can trivially trigger an amplification attack.

I was not able to verify that myself, but it is claimed to affect all
fop version from 1.0 up to 2.1.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-5661
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5661
[1] http://www.openwall.com/lists/oss-security/2017/04/18/2

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: fop
Source-Version: 1:2.1-6

We believe that the bug you reported is fixed in the latest version of
fop, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 860...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated fop package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 24 May 2017 15:53:03 +0200
Source: fop
Binary: fop libfop-java fop-doc
Architecture: source
Version: 1:2.1-6
Distribution: unstable
Urgency: high
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 fop- XML formatter driven by XSL Formatting Objects (XSL-FO.) - app
 fop-doc- XML formatter driven by XSL Formatting Objects (doc) - doc
 libfop-java - XML formatter driven by XSL Formatting Objects (XSL-FO.) - libs
Closes: 860567
Changes:
 fop (1:2.1-6) unstable; urgency=high
 .
   * Team upload.
   * Fixed CVE-2017-5661: Information disclosure vulnerability (Closes: #860567)
Checksums-Sha1:
 03aefdca9334b932835a978357671dd1f56bdbcd 2492 fop_2.1-6.dsc
 65808a7ffce63a0fa006dda4458a430bcae2de32 870416 fop_2.1-6.debian.tar.xz
 61765c1f3d45e63c47744cb64c86da2e74ac12dc 5310 fop_2.1-6_source.buildinfo
Checksums-Sha256:
 8dc1a44f7f621127061993970e69bdf49f16067a6c9a276e27144ccc36ef4f2e 2492 
fop_2.1-6.dsc
 a59f86deb333458326e0e62600066d4b741923f29f9cc18714034a68d059f73f 870416 
fop_2.1-6.debian.tar.xz
 b25d50a885c426a1bf2ce3d9a662b518518212ddf6351d3f3bb1df9d1eefd1b0 5310 
fop_2.1-6_source.buildinfo
Files:
 5d5632ee47527572eff4bbbd61391fa1 2492 text optional fop_2.1-6.dsc
 efa740348a632d77994b33f43c4e6bdf 870416 text optional fop_2.1-6.debian.tar.xz
 c081d15c17868d4f7f0a00e5ca7cfe83 5310 text optional fop_2.1-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlklkWgSHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCsHRQQAMGpCn4Ctdxnhd6CKqCQngX0irXpPZBn
Ay0XGF60iCrGso5df10y2cu1/f8vvyublBXwKcMStn21UL1ydWM2ns4aaH4li+5i
xS8v+Lz7G6ekIlZlm0aFSHztoKhEwi/uIRF1JYS1yWv1IfBOK2rn3oh9W4hTrO9j
d8aIKxyXksmz9lOSf1RbbFrRFLcoWQEmHS08pbVMyNj6yWH5g2E1z3TGVCORKLKP
SZL8QWALq+2N8tF1CaAPLF/Rcvo2Xfqs/KF1JkpXhhFJj3yM4HNjZamc8li1a27l
4H3G+4XZYO2xdJ1lxK85kaNQlUtzXVM5OKcpFlWsTsRhaVREtGCGC1OQDMQBjGMY
nWv5bYBPV3a5v7o7KYNVDmsdwccKVX5++FwmJJbzb4qcE2FdnbG0NpocGKB17V4X
fxM0RIpYXEhvu1hFYmJSVL/5WuGI4hBt1adfsdVNp4JyBOpT0TrPmR62euqOyX62

Bug#863258: marked as done (libblas.a is empty)

[Debian Bug Tracking System]

Your message dated Wed, 24 May 2017 15:05:09 +
with message-id 
and subject line Bug#863258: fixed in lapack 3.7.0-2
has caused the Debian Bug report #863258,
regarding libblas.a is empty
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
863258: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863258
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libblas-dev
Version: 3.6.1-1
Severity: serious

libblas.a is empty. This regression has been introduced in the fix for #813309:
the $(shell LC_ALL=C ls tmp/*.o) construct used to have a consistent ordering
of object files is evaluated too early, and results in an empty list.

-- 
 .''`.Sébastien Villemot
: :' :Debian Developer
`. `' http://sebastien.villemot.name
  `-  GPG Key: 4096R/381A7594


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: lapack
Source-Version: 3.7.0-2

We believe that the bug you reported is fixed in the latest version of
lapack, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 863...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sébastien Villemot  (supplier of updated lapack package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 24 May 2017 16:24:37 +0200
Source: lapack
Binary: liblapack3 liblapacke liblapacke-dev libtmglib3 libtmglib-dev 
liblapack-dev liblapack-pic liblapack-test liblapack-doc liblapack-doc-man 
libblas3 libblas-common libblas-dev libblas-test libblas-doc
Architecture: source
Version: 3.7.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Sébastien Villemot 
Description:
 libblas-common - Dependency package for all BLAS implementations
 libblas-dev - Basic Linear Algebra Subroutines 3, static library
 libblas-doc - Transitional package for BLAS manpages
 libblas-test - Basic Linear Algebra Subroutines 3, testing programs
 libblas3   - Basic Linear Algebra Reference implementations, shared library
 liblapack-dev - Library of linear algebra routines 3 - static version
 liblapack-doc - Library of linear algebra routines 3 - documentation (HTML)
 liblapack-doc-man - Library of linear algebra routines 3 - documentation 
(manual page
 liblapack-pic - Library of linear algebra routines 3 - static PIC version
 liblapack-test - Library of linear algebra routines 3 - testing programs
 liblapack3 - Library of linear algebra routines 3 - shared version
 liblapacke - Library of linear algebra routines 3 - C lib shared version
 liblapacke-dev - Library of linear algebra routines 3 - Headers
 libtmglib-dev - test matrix generators of LAPACK - development files
 libtmglib3 - test matrix generators of LAPACK - shared version
Closes: 863258
Changes:
 lapack (3.7.0-2) unstable; urgency=medium
 .
   * Fix regression in libblas.a, which was empty since 3.6.1-1.
 The bug has been introduced in the fix for #813309: the $(shell LC_ALL=C ls
 tmp/*.o) construct used to have a consistent ordering of object files is
 evaluated too early, and results in an empty list. Replace it by a $$(env 
…)
 construct, which is evaluated after the object files have been created.
 (Closes: #863258)
Checksums-Sha1:
 debb7ebb4df0d56be88dda30eccbfd13fc326d9a 2900 lapack_3.7.0-2.dsc
 b35670b46a6c3bbdc937eca20185fb7683bd76f1 21100 lapack_3.7.0-2.debian.tar.xz
 1fb7d83b2bfc7d4539775486f5adc2aaa9d41ac8 12798 lapack_3.7.0-2_amd64.buildinfo
Checksums-Sha256:
 8e6a856bbf932f19456de2bad5b2955ae0ccb36e740d38afe011444be10fac9f 2900 
lapack_3.7.0-2.dsc
 bc423933dd01b179bee02649675f5b87f669945530b291aeb95229f5e8d51035 21100 
lapack_3.7.0-2.debian.tar.xz
 db5cf704f8842ea115e91db6f8ff2b2019c493df7725aecc5d5c9121f94e79e1 12798 
lapack_3.7.0-2_amd64.buildinfo
Files:
 4e55a2d02a24777d7cdbd0232942be70 2900 libs optional lapack_3.7.0-2.dsc
 6f3885707727006332896fa497c75988 21100 libs optional 
lapack_3.7.0-2.debian.tar.xz
 2412d009b5674612a072d778f19dfb88 12798 libs optional 
lapack_3.7.0-2_amd64.buildinfo

Bug#863258: libblas.a is empty

[Sébastien Villemot]

Package: libblas-dev
Version: 3.6.1-1
Severity: serious

libblas.a is empty. This regression has been introduced in the fix for #813309:
the $(shell LC_ALL=C ls tmp/*.o) construct used to have a consistent ordering
of object files is evaluated too early, and results in an empty list.

-- 
 .''`.Sébastien Villemot
: :' :Debian Developer
`. `' http://sebastien.villemot.name
  `-  GPG Key: 4096R/381A7594


signature.asc
Description: PGP signature

Bug#863176: marked as done (debian-edu-config: missing entries in Makefile break exim4 configuration)

[Debian Bug Tracking System]

Your message dated Wed, 24 May 2017 13:18:40 +
with message-id 
and subject line Bug#863176: fixed in debian-edu-config 1.928
has caused the Debian Bug report #863176,
regarding debian-edu-config: missing entries in Makefile break exim4 
configuration
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
863176: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863176
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-edu-config
Version: 1.927
Severity: serious

The exim4 tools added to fix the broken exim4 security are missing due 
to forgotten Makefile entries.

Wolfgang


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: debian-edu-config
Source-Version: 1.928

We believe that the bug you reported is fixed in the latest version of
debian-edu-config, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 863...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Holger Levsen  (supplier of updated debian-edu-config 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 24 May 2017 15:04:36 +0200
Source: debian-edu-config
Binary: debian-edu-config
Architecture: source
Version: 1.928
Distribution: unstable
Urgency: medium
Maintainer: Debian Edu Developers 
Changed-By: Holger Levsen 
Description:
 debian-edu-config - Configuration files for Skolelinux systems
Closes: 863176
Changes:
 debian-edu-config (1.928) unstable; urgency=medium
 .
   [ Wolfgang Schweer ]
   * Fix Makefile, include exim4 tools. (Closes: #863176).
 - Add share/debian-edu-config/tools/exim4-create-cert.
 - Add share/debian-edu-config/tools/exim4-create-environment.
Checksums-Sha1:
 88f9bd00f4c88cfceb8e001dca05d7eaf2a75cf7 1821 debian-edu-config_1.928.dsc
 34ecb47ad6275a0c5246e6c46e4c5ed5b2ad4238 385224 debian-edu-config_1.928.tar.xz
 3cb54bd1e56843925b43974b88840e5eeef460e3 4265 
debian-edu-config_1.928_source.buildinfo
Checksums-Sha256:
 6496a3c2f5bb47671c888f834834b9f755c74bde11cef55a43f4f9d261087c1b 1821 
debian-edu-config_1.928.dsc
 dd465fe7af8805492dafb3503e86e67fcbee956c1964824b48a80daedd6b0792 385224 
debian-edu-config_1.928.tar.xz
 bb434766659e7f47bc506e159c9bed33da72ac58c2c1f218c1e578d92f7dfaf8 4265 
debian-edu-config_1.928_source.buildinfo
Files:
 78578bee9ba9e17bd02ea9ad93df5a07 1821 misc extra debian-edu-config_1.928.dsc
 bd22f152855fa27a851e5579ff80d4c1 385224 misc extra 
debian-edu-config_1.928.tar.xz
 fbf6738f8b61ce88bd34e7d2560539b1 4265 misc extra 
debian-edu-config_1.928_source.buildinfo

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIVAwUBWSWFIgkauFYGmqocAQqu/RAAo5q/ct+IW8HwTsbuGfYfKzTKcQjei85G
T3saKFYTDwMXD9C4X3um2ttCblIJ5tkAAl9EbgDLcZiJqUbjVAatJAo9PExnhggU
96DjOlnpKUKOfZFrQLmlGkC+Be7ihcmT6BoCpFXBGYwmRK/YaxxUmOMH0qFSZtws
qw3BZUNUCPJ/8IDBR+672LAwbot8PnobdEAlh5dfZzOeYMq4SSM9hzMejuXFrrK+
ufEhtHDhDuqDnwJN2OqO+SJgM4rVc2NRf26ahBF9rZHcUFDof8xQ3NRN3w726jc2
iuV4n1aQ4CpcK4YzvpO3A27er26JQar6K5nVe5EcTeClPgrBNK8TO48xnzmXg377
M6+Xl0ZzVAgVQW92F5u2tv9+6FLYOOjmfgRR3GoidJh6XhxuN86TyyXDt4v7+ySF
B0YUS+UvMb/ltoG4IgPEq98qWtdDYNXbJzvMJF2/AU7Zch2AY6JHJ+PgVLsmaHe1
NPm16fixP6dsyJf3x3L+xIZxYv0zuja7+bNzna555hIrAnOGT/t4xJDGiJl35ZFp
sXnbDVYd2p8kFT3YxBrqf7tDzEoXnyiwth2I/thRleAgy+xpl3f97/1b/U4qtEsJ
ZOgdPf35Q+k9vzN84OJOWdJiTt8q4HOmtjsmU03fB++58T0M/wILHNUdt7bnH+ev
3mi5XOJ7o7c=
=clRx
-END PGP SIGNATURE End Message ---

Bug#854610: marked as done (libsofthsm2 is not installable because of wrong libssl dependency)

[Debian Bug Tracking System]

Your message dated Wed, 24 May 2017 15:18:50 +0300
with message-id <20170524121850.zhw76py6aiyjarec@localhost>
and subject line The libsofthsm2 dependency is fixed in 2.2.0-3~bpo8+1
has caused the Debian Bug report #854610,
regarding libsofthsm2 is not installable because of wrong libssl dependency
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
854610: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854610
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsofthsm2
Version: 2.1.0-3~bpo8+1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I'm trying to install libsofthsm on debian jessie, using the
jessie-backports repository. The amd64 package depends on libssl1.0.2,
which does not exist. I think this should be libssl1.0.0, which does
exist in an appropriate version (>=1.0.2d). As is, the package can only
be installed after building from source.

In addition, before being able to use the package, I had to manually
create /var/lib/softhsm/tokens. This should probably be created during
the installation process.

Kind regards
Dominik Reusser


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

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Version: 2.2.0-3~bpo8+1

The libsofthsm2 dependency is fixed in 2.2.0-3~bpo8+1

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--- End Message ---

Bug#861744: [Pkg-privacy-maintainers] Bug#861744: Bug#861744: Bug#861744: torbrowser-launcher: Should not be part of Stretch

[Holger Levsen]

On Tue, May 23, 2017 at 03:06:48PM +, Holger Levsen wrote:
> On Tue, May 23, 2017 at 09:13:59AM +0200, intrigeri wrote:
> > > So of course what I shall do is to disable those mails to me, after all
> > > I'm one of the maintainers of jenkins.d.n :) But then I fear that
> > > torbrowser-launcher will bitrot even more…
> > Perhaps Ulrike would want to be the recipient of those email?
> she is, since 2016-11-09.

as it was pointed out to me that this comment could be seen as finger pointing
I would like to clarify that this absolutly wasn't ment that way but rather
as a reply to intri's suggestion…

Apologies if I came accross differently. I'm well aware that we are volunteers,
usually with too much stuff on our plates.


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#863248: containerd 0.2.3+git20170126.85.aa8187d~ds1-1: container not started (docker.io 1.13.0~ds1-3)

[Roland Kammerer]

Package: containerd
Version: 0.2.3+git20170126.85.aa8187d~ds1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I have the following versions:
containerd: 0.2.3+git20170126.85.aa8187d~ds1-1
docker.io: 1.13.0~ds1-3

I report the bug against containerd because it shows up in the logs, but
it could be docker.io as well.

docker pulling works, but starting a container fails with the following
message in /var/log/syslog:

May 24 13:24:52 aperol dockerd[8119]: 
time="2017-05-24T13:24:52.902469508+02:00" level=error msg="containerd: start 
container" error="containerd: container not started" 
id=c755b6c444b4a3326eba965a7e94d46d794ec7cd28395452a34f11fafff2ff5a
May 24 13:24:52 aperol dockerd[8119]: 
time="2017-05-24T13:24:52.904963464+02:00" level=error msg="Create container 
failed with error: containerd: container not started"

Regards, rck

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable'), (550, 'experimental'), (500, 
'testing-debug')
Architecture: amd64
 (x86_64)

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

Versions of packages containerd depends on:
ii  libc6  2.24-10
ii  runc   0.1.1+dfsg1-2+b2

containerd recommends no packages.

containerd suggests no packages.

-- no debconf information

Bug#861282: packer: FTBFS

[Roger Shimizu]

On Tue, 23 May 2017 21:35:06 -0400 (EDT)
JD Friedrikson  wrote:

> Am I doing something wrong here?

Yes, I got fail by local "gbp buildpackage", too.
Previous -4 release is the same result. So it's not a regression of my patch.

I build this package well by git-pbuilder. (and of course it built well on 
debian's buildd)
I didn't confirm below commands one by one, but I guess it should be:

# below: if you didn't do this before
sudo apt install git-buildpackage pristine-tar cowbuilder 
git-pbuilder create
gbp clone --pristine-tar 
https://anonscm.debian.org/git/pkg-go/packages/packer.git
cd packer
# below: routine building work
git checkout fix_861282
gbp buildpackage --git-ignore-branch --git-pristine-tar --git-pbuilder 
--git-export-dir=../build-area

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1


pgpY42iAbbC1q.pgp
Description: PGP signature

Processed: forcibly merging 863230 863236

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 863230 863236
Bug #863230 [kodi] kodi: CVE-2017-8314: malicious subtitle zip files 
vulnerability
Bug #863236 [kodi] kodi: Kodi advising to upgrade to 17.2, due to security flaw
Severity set to 'serious' from 'important'
Added tag(s) security and upstream.
Bug #863230 [kodi] kodi: CVE-2017-8314: malicious subtitle zip files 
vulnerability
Marked as found in versions kodi/2:17.1+dfsg1-2.
Merged 863230 863236
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
863230: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863230
863236: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863236
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#863230: kodi: malicious subtitle zip files vulnerability

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 kodi: CVE-2017-8314: malicious subtitle zip files vulnerability
Bug #863230 [kodi] kodi: malicious subtitle zip files vulnerability
Changed Bug title to 'kodi: CVE-2017-8314: malicious subtitle zip files 
vulnerability' from 'kodi: malicious subtitle zip files vulnerability'.
> tags -1 + upstream security
Bug #863230 [kodi] kodi: CVE-2017-8314: malicious subtitle zip files 
vulnerability
Added tag(s) upstream.

-- 
863230: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863230
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#863230: kodi: malicious subtitle zip files vulnerability

[Salvatore Bonaccorso]

Control: retitle -1 kodi: CVE-2017-8314: malicious subtitle zip files 
vulnerability
Control: tags -1 + upstream security

On Wed, May 24, 2017 at 09:35:29AM +0200, Jonatan Nyberg wrote:
> Package: kodi
> severity: important
> 
> Dear Maintainer,
> 
> Kodi 17.2 have an important fix for the malicious subtitles
> vulnerability that has the potential to compromise your machine. It is
> important to update to this version as soon as possible.
> 
> http://blog.checkpoint.com/2017/05/23/hacked-in-translation/

This got a CVE assigned (CVE-2017-8314)

Regards,
Salvatore

Processed: Re: Bug#863186: libtasn1-6: CVE-2017-6891

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #863186 [src:libtasn1-6] libtasn1-6: CVE-2017-6891
Severity set to 'serious' from 'important'

-- 
863186: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863186
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#863208: marked as done (mash sometimes FTBFS in parallel builds)

[Debian Bug Tracking System]

Your message dated Wed, 24 May 2017 09:33:59 +
with message-id 
and subject line Bug#863208: fixed in mash 1.1.1-2
has caused the Debian Bug report #863208,
regarding mash sometimes FTBFS in parallel builds
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
863208: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863208
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mash
Version: 1.1.1-1
Severity: serious
Tags: patch

https://buildd.debian.org/status/fetch.php?pkg=mash=ppc64el=1.1.1-1=1472296851=0

...
dh_auto_build
make -j4
make[2]: Entering directory '/«PKGBUILDDIR»'
cd src/mash/capnp;export 
PATH=/usr/bin/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games;capnp
 compile -I /usr/include -oc++ MinHash.capnp
cd src/mash/capnp;export 
PATH=/usr/bin/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games;capnp
 compile -I /usr/include -oc++ MinHash.capnp
g++ -c -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security -O3 -std=c++11 -Isrc 
-I/usr/include -I /usr/include -Wdate-time -D_FORTIFY_SOURCE=2  -o 
src/mash/capnp/MinHash.capnp.o src/mash/capnp/MinHash.capnp.c++
g++ -c -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security -O3 -std=c++11 -Isrc 
-I/usr/include -I /usr/include -Wdate-time -D_FORTIFY_SOURCE=2  -o 
src/mash/Command.o src/mash/Command.cpp
g++ -c -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security -O3 -std=c++11 -Isrc 
-I/usr/include -I /usr/include -Wdate-time -D_FORTIFY_SOURCE=2  -o 
src/mash/CommandBounds.o src/mash/CommandBounds.cpp
g++ -c -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security -O3 -std=c++11 -Isrc 
-I/usr/include -I /usr/include -Wdate-time -D_FORTIFY_SOURCE=2  -o 
src/mash/CommandContain.o src/mash/CommandContain.cpp
src/mash/capnp/MinHash.capnp.c++:581:23: error: expected primary-expression at 
end of input
   9,   0,   0,   0,   0,   0,   0,   0,
   ^
src/mash/capnp/MinHash.capnp.c++:581:23: error: expected ‘}’ at end of input
src/mash/capnp/MinHash.capnp.c++:581:23: error: expected ‘}’ at end of input
src/mash/capnp/MinHash.capnp.c++:581:23: error: expected ‘,’ or ‘;’ at end of 
input
src/mash/capnp/MinHash.capnp.c++:581:23: error: expected ‘}’ at end of input
src/mash/capnp/MinHash.capnp.c++:581:23: error: expected ‘}’ at end of input
Makefile:47: recipe for target 'src/mash/capnp/MinHash.capnp.o' failed
make[2]: *** [src/mash/capnp/MinHash.capnp.o] Error 1


This is caused by "capnp compile" running twice in parallel,
fix is attached.
Description: Fix parallel build failures
 "capnp compile" ran twice, and in parallel builds twice in parallel.
 This resulted in occasional build failures caused by corrupt output files.
 .
 Fix the Makefile to only run "capnp compile" once.
Author: Adrian Bunk 

--- mash-1.1.1.orig/Makefile.in
+++ mash-1.1.1/Makefile.in
@@ -46,7 +46,9 @@ libmash.a : $(OBJECTS)
 %.o : %.c++
$(CXX) -c $(CXXFLAGS) $(CPPFLAGS) -o $@ $<
 
-src/mash/capnp/MinHash.capnp.c++ src/mash/capnp/MinHash.capnp.h : 
src/mash/capnp/MinHash.capnp
+src/mash/capnp/MinHash.capnp.c++ : src/mash/capnp/MinHash.capnp.h
+
+src/mash/capnp/MinHash.capnp.h : src/mash/capnp/MinHash.capnp
cd src/mash/capnp;export PATH=@capnp@/bin/:${PATH};capnp compile -I 
@capnp@/include -oc++ MinHash.capnp
 
 install : mash
--- End Message ---
--- Begin Message ---
Source: mash
Source-Version: 1.1.1-2

We believe that the bug you reported is fixed in the latest version of
mash, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 863...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sascha Steinbiss  (supplier of updated mash package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 24 May 2017 08:43:17 +
Source: mash
Binary: mash libmash-dev mash-doc
Architecture: source amd64 all
Version: 1.1.1-2

Bug#857444: [debian-mysql] Bug#857444: Moving to src:mariadb-10.1

[Ondřej Surý]

Control: fixed -1 mysql-transitional/5.5.+default

This was actually fixed with upload of mysql-transitional to
testing-p-u.  I'll close it when the package migrates from t-p-u to
testing.

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
fast DNS(SEC) resolver
Vše pro chleba (https://vseprochleba.cz) – Mouky ze mlýna a potřeby pro
pečení chleba všeho druhu

On Wed, May 24, 2017, at 10:09, Adrian Bunk wrote:
> Control: reassign -1 src:mariadb-10.1
> 
> I am moving this bug to src:mariadb-10.1 to make it visible that this
> is a jessie -> stretch upgrade problem that should be fixed in stretch.
> 
> 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
> 
> ___
> pkg-mysql-maint mailing list
> pkg-mysql-ma...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint

Processed: Re: [debian-mysql] Bug#857444: Moving to src:mariadb-10.1

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 mysql-transitional/5.5.+default
Bug #857444 [src:mariadb-10.1] mysql-server-5.5: upgrade from jessie to stretch 
leaves mysql server uninstalled
Marked as fixed in versions mysql-transitional/5.5.+default.

-- 
857444: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857444
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#862556: marked as done (CVE-2017-9058: Heap-based buffer overflow due to incorrect boundary checking)

[Debian Bug Tracking System]

Your message dated Wed, 24 May 2017 09:05:44 +
with message-id 
and subject line Bug#862556: fixed in libytnef 1.9.2-2
has caused the Debian Bug report #862556,
regarding CVE-2017-9058: Heap-based buffer overflow due to incorrect boundary 
checking
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
862556: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862556
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libytnef 
 Version:  1.5-6+deb8u1
 Severity:  normal
 Tags: security
 
 
 Hi,
   We found a heap-buffer-overflow vulnerability in the libytnef.
 This affects both 1.5-6+deb8u1 and 1.9.1 .
 The cause is an incorrect boundary checking in SIZECHCK macro in  
lib/ytnef.c:39
 -- #define SIZECHECK(x) { if char *)d - (char *)data) + x) >  size) {  
printf("Corrupted file detected at %s : %i\n", __FILE__,  __LINE__); 
return(-1); } }
 ++ #define SIZECHECK(x) { if char *)d - (char *)data) + x) >=  size) {  
printf("Corrupted file detected at %s : %i\n", __FILE__,  __LINE__); 
return(-1); } }
   
   
 To verify this, use the testcase from:
 
https://github.com/bingosxs/fuzzdata/blob/master/ytnef-1.9/TNEFFreeMapiProps-Invalid-read.tnef?raw=true
   
 run the sample with command:
 
 ytnef/.libs/ytnef -v @@


The tracelog is:
=
==15221==ERROR: AddressSanitizer: heap-buffer-overflow on address 
0x6020ef90 at pc 0x7f7f8986e69f bp 0x7ffe3fc1b820 sp 0x7ffe3fc1b818
READ of size 4 at 0x6020ef90 thread T0
#0 0x7f7f8986e69e in SwapDWord 
/home/canicula/afl/test/libytnef0/libytnef-1.5.x/ytnef.c:136:12
#1 0x7f7f8986e69e in TNEFPriority 
/home/canicula/afl/test/libytnef0/libytnef-1.5.x/ytnef.c:670
#2 0x7f7f8987ac87 in TNEFParse 
/home/canicula/afl/test/libytnef0/libytnef-1.5.x/ytnef.c:1076:29
#3 0x7f7f8987997f in TNEFParseFile 
/home/canicula/afl/test/libytnef0/libytnef-1.5.x/ytnef.c:936:12
#4 0x4ea71b in main /home/canicula/afl/test/ytnef.0/ytnef/main.c:125:9
#5 0x7f7f8897782f in __libc_start_main 
/build/glibc-9tT8Do/glibc-2.23/csu/../csu/libc-start.c:291
#6 0x418bd8 in _start 
(/data/canicula/afl/test/ytnef.0/ytnef/.libs/ytnef+0x418bd8)

0x6020ef92 is located 0 bytes to the right of 2-byte region 
[0x6020ef90,0x6020ef92)
allocated by thread T0 here:
#0 0x4b8e90 in calloc 
(/data/canicula/afl/test/ytnef.0/ytnef/.libs/ytnef+0x4b8e90)
#1 0x7f7f8987a29d in TNEFParse 
/home/canicula/afl/test/libytnef0/libytnef-1.5.x/ytnef.c:1046:20
#2 0x7f7f8987997f in TNEFParseFile 
/home/canicula/afl/test/libytnef0/libytnef-1.5.x/ytnef.c:936:12
#3 0x4ea71b in main /home/canicula/afl/test/ytnef.0/ytnef/main.c:125:9
#4 0x7f7f8897782f in __libc_start_main 
/build/glibc-9tT8Do/glibc-2.23/csu/../csu/libc-start.c:291

SUMMARY: AddressSanitizer: heap-buffer-overflow 
/home/canicula/afl/test/libytnef0/libytnef-1.5.x/ytnef.c:136:12 in SwapDWord
Shadow bytes around the buggy address:
  0x0c047fff9da0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
  0x0c047fff9db0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
  0x0c047fff9dc0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
  0x0c047fff9dd0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
  0x0c047fff9de0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
=>0x0c047fff9df0: fa fa[02]fa fa fa 00 fa fa fa fd fa fa fa fd fa
  0x0c047fff9e00: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
  0x0c047fff9e10: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
  0x0c047fff9e20: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
  0x0c047fff9e30: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
  0x0c047fff9e40: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
Shadow byte legend (one shadow byte represents 8 application bytes):
  Addressable:   00
  Partially addressable: 01 02 03 04 05 06 07 
  Heap left redzone:   fa
  Heap right redzone:  fb
  Freed heap region:   fd
  Stack left redzone:  f1
  Stack mid redzone:   f2
  Stack right redzone: f3
  Stack partial redzone:   f4
  Stack after return:  f5
  Stack use after scope:   f8
  Global redzone:  f9
  Global init order:   f6
  Poisoned by user:f7
  Container overflow:  fc
  Array cookie:ac
  Intra object redzone:bb
  ASan internal:   fe
  Left alloca redzone: ca
  Right alloca redzone:cb
==15221==ABORTING--- End Message ---
--- Begin Message ---
Source: libytnef
Source-Version: 1.9.2-2

We believe that the bug you reported is fixed in the latest version of
libytnef, 

Processed: severity of 863224 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 863224 serious
Bug #863224 [src:acl2] acl2: build fails on mips (mips-aql-05)
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
863224: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863224
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Moving to src:mariadb-10.1

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:mariadb-10.1
Bug #857444 [mysql-server-5.5] mysql-server-5.5: upgrade from jessie to stretch 
leaves mysql server uninstalled
Bug reassigned from package 'mysql-server-5.5' to 'src:mariadb-10.1'.
No longer marked as found in versions mysql-5.5/5.5.54-0+deb8u1.
Ignoring request to alter fixed versions of bug #857444 to the same values 
previously set

-- 
857444: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857444
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#857444: Moving to src:mariadb-10.1

[Adrian Bunk]

Control: reassign -1 src:mariadb-10.1

I am moving this bug to src:mariadb-10.1 to make it visible that this
is a jessie -> stretch upgrade problem that should be fixed in stretch.

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#850335: marked as done (golang-goyaml: FTBFS (failing tests))

[Debian Bug Tracking System]

Your message dated Wed, 24 May 2017 11:02:49 +0300
with message-id <20170524080249.y7y752vnm5jz7rum@localhost>
and subject line src:golang-goyaml was removed from stretch+unstable
has caused the Debian Bug report #850335,
regarding golang-goyaml: FTBFS (failing tests)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
850335: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850335
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:golang-goyaml
Version: 0.0~bzr50-1
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-arch
I: golang-goyaml_0.0~bzr50
dh build-arch --buildsystem=golang --with=golang
dh: Compatibility levels before 9 are deprecated (level 8 in use)
   dh_testdir -a -O--buildsystem=golang
   dh_update_autotools_config -a -O--buildsystem=golang
   dh_auto_configure -a -O--buildsystem=golang
dh_auto_configure: Compatibility levels before 9 are deprecated (level 8 in use)
   dh_auto_build -a -O--buildsystem=golang
dh_auto_build: Compatibility levels before 9 are deprecated (level 8 in use)
go install -v -p 1 launchpad.net/goyaml
launchpad.net/goyaml
   dh_auto_test -a -O--buildsystem=golang
dh_auto_test: Compatibility levels before 9 are deprecated (level 8 in use)
go test -v -p 1 launchpad.net/goyaml
=== RUN   Test

--
FAIL: encode_test.go:217: S.TestMarshal

encode_test.go:221:
c.Assert(string(data), Equals, item.data)
... obtained string = "" +
... "a: 1\n" +
... "b: 2\n"
... expected string = "" +
... "a: 1\n" +
... "b: 2\n" +
... "c: 3\n"


--
FAIL: encode_test.go:238: S.TestMarshalErrors

encode_test.go:241:
c.Assert(err, ErrorMatches, item.error)
... value = nil
... regex string = "Duplicated key 'b' in struct struct \\{ B int; .*"
... Error value is nil


--
FAIL: decode_test.go:364: S.TestUnmarshal

decode_test.go:385:
c.Assert(value, DeepEquals, item.value, Commentf("Item #%d", i))
... obtained *struct { A int; C goyaml_test.inlineB "yaml:\",inline\"" } = 
 { A int; C goyaml_test.inlineB "yaml:\",inline\"" }{A:1, 
C:goyaml_test.inlineB{B:2, inlineC:goyaml_test.inlineC{C:0}}}
... expected *struct { A int; C goyaml_test.inlineB "yaml:\",inline\"" } = 
 { A int; C goyaml_test.inlineB "yaml:\",inline\"" }{A:1, 
C:goyaml_test.inlineB{B:2, inlineC:goyaml_test.inlineC{C:3}}}
... Item #84

OOPS: 9 passed, 3 FAILED
--- FAIL: Test (0.01s)
FAIL
exit status 1
FAILlaunchpad.net/goyaml0.009s
dh_auto_test: go test -v -p 1 launchpad.net/goyaml returned exit code 1
debian/rules:7: recipe for target 'build-arch' failed
make: *** [build-arch] Error 1
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2


This is just how the build ends, not necessarily the relevant part.

I've put several build logs here:

https://people.debian.org/~sanvila/build-logs/golang-goyaml/

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

The bug should be reproducible with sbuild on a single CPU virtual machine.

Thanks.
--- End Message ---
--- Begin Message ---
src:golang-goyaml was removed from stretch+unstable,
and the problem is not in jessie.

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--- End Message ---

Processed: Version tracking fix

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 862837 0.9.1-4
Bug #862837 [xrdp] xrdp: Package install failure - dpkg: error processing 
package xrdp (--configure)
Marked as found in versions xrdp/0.9.1-4.
> found 837091 45.3.0esr-1
Bug #837091 [firefox-esr] firefox-esr: EME DRM extention present and enabled
Marked as found in versions firefox-esr/45.3.0esr-1.
> # the BTS is completely confused when source package and binary
> # package have the same name, but the binary package is built
> # from a different source
> reassign 854884 baloo4
Bug #854884 [src:baloo] baloo: is this obsoleted by src:baloo-kf5?
Bug reassigned from package 'src:baloo' to 'baloo4'.
No longer marked as found in versions baloo/4:4.14.3-3.
Ignoring request to alter fixed versions of bug #854884 to the same values 
previously set
> tags 854884 stretch sid
Bug #854884 [baloo4] baloo: is this obsoleted by src:baloo-kf5?
Added tag(s) stretch and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
837091: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837091
854884: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854884
862837: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862837
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#805676: marked as done (paco: FTBFS: build flags incompatiable with glibmm-2.4)

[Debian Bug Tracking System]

Your message dated Wed, 24 May 2017 10:46:38 +0300
with message-id <20170524074638.cpzjf7ok523jdghi@localhost>
and subject line paco was removed from stretch+unstable
has caused the Debian Bug report #805676,
regarding paco: FTBFS: build flags incompatiable with glibmm-2.4
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
805676: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805676
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: paco
Version: 2.0.9-3
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

In file included from /usr/include/c++/5/type_traits:35:0,
 from /usr/include/sigc++-2.0/sigc++/visit_each.h:22,
 from /usr/include/sigc++-2.0/sigc++/functors/slot.h:6,
 from /usr/include/sigc++-2.0/sigc++/signal_base.h:27,
 from /usr/include/sigc++-2.0/sigc++/signal.h:8,
 from /usr/include/sigc++-2.0/sigc++/sigc++.h:86,
 from /usr/include/glibmm-2.4/glibmm/thread.h:51,
 from /usr/include/glibmm-2.4/glibmm.h:87,
 from /usr/include/gtkmm-2.4/gtkmm/window.h:7,
 from mainwindow.h:12,
 from main.cc:11:
/usr/include/c++/5/bits/c++0x_warning.h:32:2: error: #error This file requires 
compiler and library support for the ISO C++ 2011 standard. This support is 
currently experimental, and must be enabled with the -std=c++11 or -std=gnu++11 
compiler options.
 #error This file requires compiler and library support for the \
  ^

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/paco.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
paco was removed from stretch+unstable, and the problem is not in jessie.

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--- End Message ---

Processed: severity of 863230 is serious, tagging 863230

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 863230 serious
Bug #863230 [kodi] kodi: malicious subtitle zip files vulnerability
Severity set to 'serious' from 'important'
> tags 863230 + security
Bug #863230 [kodi] kodi: malicious subtitle zip files vulnerability
Added tag(s) security.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
863230: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863230
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#863223: marked as done (maven-plugin-tools: FTBFS: maven/tools/plugin/generator/PluginHelpGenerator.java:[300,61] unreported exception java.io.IOException; must be caught or declared to be thrown)

[Debian Bug Tracking System]

Your message dated Wed, 24 May 2017 07:03:58 +
with message-id 
and subject line Bug#863223: fixed in plexus-utils2 3.0.24-2
has caused the Debian Bug report #863223,
regarding maven-plugin-tools: FTBFS: 
maven/tools/plugin/generator/PluginHelpGenerator.java:[300,61] unreported 
exception java.io.IOException; must be caught or declared to be thrown
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
863223: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863223
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: maven-plugin-tools
Version: 3.3-5
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

maven-plugin-tools fails to build from source in unstable/amd64:

  […]

  Setting up default-jre-headless (2:1.8-58) ...
  Setting up default-jdk-headless (2:1.8-58) ...
  Setting up openjdk-8-jdk:amd64 (8u131-b11-2) ...
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/appletviewer 
to provide /usr/bin/appletviewer (appletviewer) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jconsole to 
provide /usr/bin/jconsole (jconsole) in auto mode
  Setting up default-jre (2:1.8-58) ...
  Setting up ant-optional (1.9.9-1) ...
  Setting up libxbean-java (4.5-4) ...
  Setting up default-jdk (2:1.8-58) ...
  Setting up libplexus-containers-java (1.0~beta3.0.7-8) ...
  Setting up libplexus-build-api-java (0.0.7-1) ...
  Setting up libplexus-io-java (1.0~alpha5-2) ...
  Setting up libplexus-interactivity-api-java (1.0-alpha-6-7) ...
  Setting up libplexus-container-default1.5-java (1.6-3) ...
  Setting up libwagon-java (1.0.0-9) ...
  Setting up libplexus-i18n-java (1.0-beta-10-3) ...
  Setting up libplexus-cli-java (1.2-5) ...
  Setting up libwagon2-java (2.10-6) ...
  Setting up libplexus-velocity-java (1.2-1) ...
  Setting up libplexus-archiver-java (2.2-1) ...
  Setting up libdoxia-java (1.1.4-6) ...
  Setting up libmaven2-core-java (2.2.1-26) ...
  Setting up libeclipse-aether-java (1.0.2-1) ...
  Setting up libmodello-java (1.8.3-3) ...
  Setting up libmaven-common-artifact-filters-java (1.4-1) ...
  Setting up libmodello-maven-plugin-java (1.8.3-1) ...
  Setting up libdoxia-sitetools-java (1.1.4-1.1) ...
  Setting up libmaven3-core-java (3.3.9-4) ...
  Setting up libmaven-filtering-java (1.1-1) ...
  Setting up libmaven-clean-plugin-java (2.5-1) ...
  Setting up maven (3.3.9-4) ...
  update-alternatives: using /usr/share/maven/bin/mvn to provide /usr/bin/mvn 
(mvn) in auto mode
  Setting up libplexus-compiler-java (2.4-3) ...
  Setting up libplexus-component-metadata-java (1.6-3) ...
  Setting up libmaven-resources-plugin-java (2.6-1) ...
  Setting up libmaven-archiver-java (2.6-3) ...
  Setting up libmaven-shared-incremental-java (1.1-1) ...
  Setting up libmaven-doxia-tools-java (1.2.1-2) ...
  Setting up libmaven-compiler-plugin-java (3.2-5) ...
  Setting up libmaven-site-plugin-java (2.1-4) ...
  Setting up libmaven-jar-plugin-java (2.4-1) ...
  Processing triggers for sgml-base (1.29) ...
  Setting up libmaven-reporting-impl-java (2.3-1) ...
  Setting up libmaven-plugin-tools-java (3.3-5) ...
  Setting up libsurefire-java (2.17-3) ...
  Setting up maven-debian-helper (2.1.3) ...
  Setting up maven-plugin-tools-build-deps (3.3-5) ...
  Processing triggers for libc-bin (2.24-10) ...
  Processing triggers for systemd (232-23) ...
  Processing triggers for ca-certificates (20161130) ...
  Updating certificates in /etc/ssl/certs...
  0 added, 0 removed; done.
  Running hooks in /etc/ca-certificates/update.d...
  
  done.
  done.
  Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.36.5-2) ...
  
  
**
  ** Environment
  **
  
**
  
  
PATH=/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  HOSTNAME=63b9f2da964e
  TERM=xterm
  PAGER=more
  DISPLAY=:0
  DOCKER_IMAGE=lamby-debian-sid
  DEB_BUILD_OPTIONS=parallel=9
  DEB_BUILD_PROFILES=
  PIP_DOWNLOAD_CACHE=/home/lamby/.cache/pip
  HOME=/home/lamby
  LOGNAME=lamby
  SHLVL=1
  
PWD=/home/lamby/temp/cdt.20170523225408.mDMW4OzuJ6.db.maven-plugin-tools/maven-plugin-tools-3.3
  

Processed: Add affects on the src:

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 863223 src:maven-plugin-tools
Bug #863223 [plexus-utils2] maven-plugin-tools: FTBFS: 
maven/tools/plugin/generator/PluginHelpGenerator.java:[300,61] unreported 
exception java.io.IOException; must be caught or declared to be thrown
Added indication that 863223 affects src:maven-plugin-tools
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
863223: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863223
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Pending fixes for bugs in the plexus-utils2 package

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 863223 + pending
Bug #863223 [plexus-utils2] maven-plugin-tools: FTBFS: 
maven/tools/plugin/generator/PluginHelpGenerator.java:[300,61] unreported 
exception java.io.IOException; must be caught or declared to be thrown
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
863223: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863223
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#863223: Pending fixes for bugs in the plexus-utils2 package

[pkg-java-maintainers]

tag 863223 + pending
thanks

Some bugs in the plexus-utils2 package are closed in revision
82a82d9044fd237b9a9abe01e684b1fb223443ca in branch 'master' by
Emmanuel Bourg

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/plexus-utils2.git/commit/?id=82a82d9

Commit message:

Fixed the backward compatibility by removing the IOException on 
PropertyUtils.loadProperties() (Closes: #863223)