Bug#877992: 9.3 still a problem

[jaltek]

Can confirm that the problem still persists after upgrade to 9.3 and a
reboot.

Like Kurt (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877992#40)
mentioned, I had to

systemctl enable postfix@-

followed by

systemctl start postfix@-

to get Postfix back running.

Before the above mentioned enable/start procedure, systemclt reported
the following:

# systemctl status postfix
● postfix.service - Postfix Mail Transport Agent
   Loaded: loaded (/lib/systemd/system/postfix.service; enabled; vendor
preset: enabled)
   Active: active (exited) since Mon 2017-12-11 08:47:03 CET; 41s ago
  Process: 1033 ExecReload=/bin/true (code=exited, status=0/SUCCESS)
  Process: 640 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
 Main PID: 640 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 4915)
   CGroup: /system.slice/postfix.service

Cheers,

Jan




On 12/10/2017 04:11 PM, Thomas Leister wrote:
> Haven't checked it myself yet, but I've heard that this issue indeed
> still exists in Debian 9.3. So you're not the only one. I hope this gets
> resolved by a skilled dev / packager (or another responsible person)
> soon as workarounds are no real solution.
> 
> Kind regards,
> Thomas
> 
> 
> Am 10.12.2017 um 09:05 schrieb b4d:
>> Hi, any info of resolution to this problem, as in 9.3 it still exists
>> for me?
>>
>> Deni
>>
> 

Bug#872305: diaspora: Package fails to install

[Joseph Nuthalapati]

reopen 872305 !
tag 872305 + patch
thanks

Was able to reproduce this.

Steps to reproduce:

1. Install diaspora and diaspora-common
2. Uninstall diaspora but not diaspora-common
3. Install diaspora package - the above error will be thrown

diaspora package shouldn't be deleting symlinks from diaspora-common.
The attached patch is to fix this issue.

-- 
Thanks,
Joseph Nuthalapati
From 810201286f5b4ed8400977ba39058aa60b0690fc Mon Sep 17 00:00:00 2001
From: Joseph Nuthalapati 
Date: Mon, 11 Dec 2017 13:01:46 +0530
Subject: [PATCH] Don't remove files that are created/removed by
 diaspora-common

The following symlinks are removed when diaspora-common is removed:

/usr/share/diaspora/public
/usr/share/diaspora/.bundle
/usr/share/diaspora/Gemfile.lock
/usr/share/diaspora/tmp
/usr/share/diaspora/app/assets

The following files are removed as part of postrm purge of diaspora-common:

/var/lib/diaspora/app-assets

/usr/share/diaspora/.eye is never created only /var/lib/diaspora/.eye exists.

Signed-off-by: Joseph Nuthalapati 
---
 debian/postrm | 7 ---
 1 file changed, 7 deletions(-)

diff --git a/debian/postrm b/debian/postrm
index 3ed8fa7..295877b 100644
--- a/debian/postrm
+++ b/debian/postrm
@@ -18,13 +18,6 @@ case "$1" in
 # This package is being removed, but its configuration has not yet
 # been purged.
 :
-
-rm -rf /usr/share/diaspora/tmp
-rm -rf /usr/share/diaspora/public
-rm -rf /usr/share/diaspora/app/assets/images
-rm -rf /usr/share/diaspora/.bundle
-rm -rf /usr/share/diaspora/.eye
-rm -rf /usr/share/diaspora/Gemfile.lock
 
 # Remove diversion
 # ldconfig is NOT needed during removal of a library, only during
-- 
2.15.0



signature.asc
Description: OpenPGP digital signature

Bug#884069: Kernel crash on boot on IBM BladeCenter HS22

[Bernhard Schmidt]

Control: severity -1 critical

On Mon, Dec 11, 2017 at 09:14:27AM +0200, Rolandas Naujikas wrote:

Hi,

> Package: linux-image-3.16.0-4-amd64
> Version: 3.16.51-2
> 
> Loading Linux 3.16.0-4-amd64 ...
> Loading initial ramdisk ...
> [0.604128] general protection fault:  [#1] SMP
> [0.609303] Modules linked in:
> [0.612493] CPU: 0 PID: 1 Comm: swapper/0 Tainted: GW
> 3.16.0-4-amd64 #1 Debian 3.16.51-2
> [0.621685] Hardware name: IBM BladeCenter HS22 -[7870SGX]-/68Y8077,
> BIOS -[P9E163AUS-1.24]- 09/17/2014
> [0.631141] task: 8803731392d0 ti: 88037313c000 task.ti:
> 88037313c000
> [0.638684] RIP: 0010:[]  []
> build_sched_domains+0x72d/0xcf0
> [0.647609] RSP: :88037313fdf8  EFLAGS: 00010216
> [0.652982] RAX:  RBX:  RCX:
> 0012
> [0.660175] RDX: 00016f48 RSI:  RDI:
> 0200
> [0.667372] RBP: 880372f5d698 R08: 880372f5e0e0 R09:
> 0139
> [0.674566] R10:  R11: 88037313fb06 R12:
> 880372f5e0c0
> [0.681761] R13: 0200 R14: 880672e640c0 R15:
> 0200
> [0.688958] FS:  () GS:88037fc0()
> knlGS:
> [0.697110] CS:  0010 DS:  ES:  CR0: 8005003b
> 
> [0.702914] CR2: 88067000 CR3: 01813000 CR4:
> 07f0
> [0.710109] Stack:
> [0.712183]  8806 880372f5e0d8 880372f5d600
> 880672e640c0
> [0.719940]    
> 880372f53e00
> [0.727715]   f1c8 
> 
> [0.735501] Call Trace:
> [0.738022]  [] ? sched_init_smp+0x398/0x452
> 
> [0.743930]  [] ? mutex_lock+0xe/0x2a
> [0.749229]  [] ? put_online_cpus+0x23/0x80
> 
> [0.755050]  [] ? stop_machine+0x2c/0x40
> 
> [0.760618]  [] ? kernel_init_freeable+0xdd/0x1e1
> 
> [0.766963]  [] ? rest_init+0x80/0x80
> [0.772264]  [] ? kernel_init+0xa/0xf0
> 
> [0.777652]  [] ? ret_from_fork+0x58/0x90
> 
> [0.783298]  [] ? rest_init+0x80/0x80
> [0.788595] Code: c0 0f 85 46 05 00 00 48 8b 74 24 08 48 c7 c2 00 dd
> a6 81 bf ff ff ff ff e8 91 78 21 00 48 98 49 8b 56 10 48 8b 04 c5 a0 1e
> 8e 81 <48> 8b 14 10 b8 01 00 00 00 49 89 54 24 10 f0 0f c1 02 85 c0 75
> 
> [0.812501] RIP  [] build_sched_domains+0x72d/0xcf0
> 
> [0.819101]  RSP 
> [0.822668] ---[ end trace b6ea7a8f78a6ba93 ]---
> [0.827375] Kernel panic - not syncing: Attempted to kill init!
> exitcode=0x000b
> [0.827375]
> [0.836621] ---[ end Kernel panic - not syncing: Attempted to kill
> init! exitcode=0x000b
> [0.836621]

Seeing the same on two Dell R610 after the point release.

Bernhard

Bug#884069: the same problem on different hardware

[Rolandas Naujikas]

Loading Linux 3.16.0-4-amd64 ...
Loading initial ramdisk ...
[0.349165] general protection fault:  [#1] SMP
[0.352000] Modules linked in:
[0.352000] CPU: 0 PID: 1 Comm: swapper/0 Tainted: GW
3.16.0-4-amd64 #1 Debian 3.16.51-2
[0.352000] Hardware name: Sun Microsystems Sun Fire X2200 M2
/S39  , BIOS S39_3B27 02/04/2009


[0.352000] task: 88021b4dd2d0 ti: 88021b4f task.ti:
88021b4f
[0.352000] RIP: 0010:[]  []
build_sched_domains+0x72d/0xcf0
[0.352000] RSP: :88021b4f3df8  EFLAGS: 00010216

[0.352000] RAX:  RBX:  RCX:
0002
[0.352000] RDX: 00016cc8 RSI:  RDI:
0200
[0.352000] RBP: 88021b5d1d98 R08: 88021b5d0760 R09:
00f4
[0.352000] R10:  R11: 88021b4f3b06 R12:
88021b5d0740
[0.352000] R13: 0200 R14: 88021b58cac0 R15:
0200
[0.352000] FS:  () GS:880223c0()
knlGS:
[0.352000] CS:  0010 DS:  ES:  CR0: 8005003b

[0.352000] CR2: 880323fff000 CR3: 01813000 CR4:
07f0
[0.352000] Stack:
[0.352000]  8802 88021b5d0758 88021b5d1d00
88021b58cac0
[0.352000]    
880323418e00
[0.352000]   f1c8 

[0.352000] Call Trace:
[0.352000]  [] ? sched_init_smp+0x398/0x452

[0.352000]  [] ? mutex_lock+0xe/0x2a
[0.352000]  [] ? put_online_cpus+0x23/0x80

[0.352000]  [] ? stop_machine+0x2c/0x40

[0.352000]  [] ? kernel_init_freeable+0xdd/0x1e1

[0.352000]  [] ? rest_init+0x80/0x80
[0.352000]  [] ? kernel_init+0xa/0xf0

[0.352000]  [] ? ret_from_fork+0x58/0x90

[0.352000]  [] ? rest_init+0x80/0x80
[0.352000] Code: c0 0f 85 46 05 00 00 48 8b 74 24 08 48 c7 c2 00 dd
a6 81 bf ff ff ff ff e8 91 78 21 00 48 98 49 8b 56 10 48 8b 04 c5 a0 1e
8e 81 <48> 8b 14 10 b8 01 00 00 00 49 89 54 24 10 f0 0f c1 02 85 c0 75

[0.352000] RIP  [] build_sched_domains+0x72d/0xcf0

[0.352000]  RSP 
[0.352006] ---[ end trace 68d23c2290c77ca9 ]---
[0.356017] Kernel panic - not syncing: Attempted to kill init!
exitcode=0x000b
[0.356017]
[0.36] ---[ end Kernel panic - not syncing: Attempted to kill
init! exitcode=0x000b
[0.36]

Bug#884068: Suggested change to test http2

[Christian Ehrhardt]

Hi,
please check out the http2 test with

browser: 
https://code.launchpad.net/~paelzer/apache2/+git/apache2/+ref/test-for-http2
git: git clone -b test-for-http2 https://git.launchpad.net/~paelzer/apache2

Looking forward to your review, kind regards
Christian Ehrhardt

Bug#884069: system cannot boot after upgrade to Debian 8.10

[Rolandas Naujikas]

Severity: critical

Bug#882699: ngspice: Remove build dependency on elyxer to allow for the elyxer removal from Debian

[Andreas Tille]

Hi Gudjon,

On Mon, Dec 11, 2017 at 06:58:10AM +0100, Gudjon I. Gudjonsson wrote:
> I'm terribly sorry for having missed the bug.
> There is a new version in SVN (27) that is not fully prepared but will
> be in the next few days. If somebody is willing to sponsor it I will be
> very happy.

I'll do.
 
> Andreas: Moving from SVN to git is fine by me, I will try to find out how to 
> do that.

I have a migration script and will run this, move to Git and will tell
you once it is done.

Kind regards

  Andreas. 

-- 
http://fam-tille.de

Bug#884068: autopkgtest to ensure http2 builds and works correctly

[Christian Ehrhardt]

Package: apache2
Version: 2.4.29-1

Hi,
I recently followed Debian and enabled http2 in Ubuntu.
Along that I thought http2 is "new enough" to be reasonable to add at
least a basic test for it.
I have done so and it worked fine on all architectures - one example
at [1] and the overview at [2].

I'll propose a change that you can review and pick in a bit, just need
a bug number to reference first.

[1]: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/a/apache2/20171208_113209_4302b@/log.gz
[2]: http://autopkgtest.ubuntu.com/packages/apache2


-- 
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd

Bug#884069: Kernel crash on boot on IBM BladeCenter HS22

[Rolandas Naujikas]

Package: linux-image-3.16.0-4-amd64
Version: 3.16.51-2

Loading Linux 3.16.0-4-amd64 ...
Loading initial ramdisk ...
[0.604128] general protection fault:  [#1] SMP
[0.609303] Modules linked in:
[0.612493] CPU: 0 PID: 1 Comm: swapper/0 Tainted: GW
3.16.0-4-amd64 #1 Debian 3.16.51-2
[0.621685] Hardware name: IBM BladeCenter HS22 -[7870SGX]-/68Y8077,
BIOS -[P9E163AUS-1.24]- 09/17/2014
[0.631141] task: 8803731392d0 ti: 88037313c000 task.ti:
88037313c000
[0.638684] RIP: 0010:[]  []
build_sched_domains+0x72d/0xcf0
[0.647609] RSP: :88037313fdf8  EFLAGS: 00010216
[0.652982] RAX:  RBX:  RCX:
0012
[0.660175] RDX: 00016f48 RSI:  RDI:
0200
[0.667372] RBP: 880372f5d698 R08: 880372f5e0e0 R09:
0139
[0.674566] R10:  R11: 88037313fb06 R12:
880372f5e0c0
[0.681761] R13: 0200 R14: 880672e640c0 R15:
0200
[0.688958] FS:  () GS:88037fc0()
knlGS:
[0.697110] CS:  0010 DS:  ES:  CR0: 8005003b

[0.702914] CR2: 88067000 CR3: 01813000 CR4:
07f0
[0.710109] Stack:
[0.712183]  8806 880372f5e0d8 880372f5d600
880672e640c0
[0.719940]    
880372f53e00
[0.727715]   f1c8 

[0.735501] Call Trace:
[0.738022]  [] ? sched_init_smp+0x398/0x452

[0.743930]  [] ? mutex_lock+0xe/0x2a
[0.749229]  [] ? put_online_cpus+0x23/0x80

[0.755050]  [] ? stop_machine+0x2c/0x40

[0.760618]  [] ? kernel_init_freeable+0xdd/0x1e1

[0.766963]  [] ? rest_init+0x80/0x80
[0.772264]  [] ? kernel_init+0xa/0xf0

[0.777652]  [] ? ret_from_fork+0x58/0x90

[0.783298]  [] ? rest_init+0x80/0x80
[0.788595] Code: c0 0f 85 46 05 00 00 48 8b 74 24 08 48 c7 c2 00 dd
a6 81 bf ff ff ff ff e8 91 78 21 00 48 98 49 8b 56 10 48 8b 04 c5 a0 1e
8e 81 <48> 8b 14 10 b8 01 00 00 00 49 89 54 24 10 f0 0f c1 02 85 c0 75

[0.812501] RIP  [] build_sched_domains+0x72d/0xcf0

[0.819101]  RSP 
[0.822668] ---[ end trace b6ea7a8f78a6ba93 ]---
[0.827375] Kernel panic - not syncing: Attempted to kill init!
exitcode=0x000b
[0.827375]
[0.836621] ---[ end Kernel panic - not syncing: Attempted to kill
init! exitcode=0x000b
[0.836621]

Bug#883938: HP ProLiant DL360 Gen9

[Stephane Lapie]

One more bit of info if it helps.

I noticed that I had some ProLiant DL360 Gen9 servers that booted fine with
that version.
The main difference between the ones that failed booting had more CPU cores
detected than the ones that succeeded.
For reference, the successful one had 20, the failed one had 32.
Given the kernel panic seems to be scheduler related, are there any chances
this is an edge case for servers with tons of CPUs?

Cheers,
-- 
ラピー ステファン Lapie Stephane
株式会社朝日ネット システム部
AsahiNet, Inc. - System Division

Bug#884066: Debian mirror ftp.halifax.rwth-aachen.de: out-of-date

[Carsten Otto]

Hi Bastian,

thank you, we noticed related issues and are investigating. I'll keep
you posted.

Thanks,
Carsten
-- 
Dr. Carsten Otto
http://verify.rwth-aachen.de/otto/


signature.asc
Description: PGP signature

Bug#884067: GIO lists removable storage devices even after they have been unplugged when using Linux kernel v4.14

[Torbjörn Andersson]

Package: libglib2.0-0
Version: 2.54.2-1

Dear maintainer,

After upgrading the Linux kernel to linux-image-4.14.0-1-amd64 , version 
4.14.2-1 (I'm using Debian sid), I noticed that when plugging in my 
phone via USB I would see an icon for it in my file manager (Thunar) and 
on my desktop (Xfce), but when unplugging the phone the icon would no 
longer disappar. Plugging in the phone again would give me a second 
icon. Doing it again a third, and so on.


This did not happen when I tried KDE's file manager, Dolphin, which 
suggests that the problem might be Glib-related, unless it's even 
further down. I'm still not sure where it actually gets the information, 
but the following program gave me the same list as the file manager, 
including the duplicates:


#include 
#include 

int main() {
  GVolumeMonitor *monitor = g_volume_monitor_get();
  GList *volumes = g_volume_monitor_get_volumes(monitor);
  GList *lp;

  for (lp = volumes; lp != NULL; lp = lp->next) {
GVolume *volume = lp->data;
char *volume_name = g_volume_get_name(volume);
printf("%s\n", g_volume_get_name(volume));
g_free(volume_name);
  }

  g_object_unref(monitor);
  g_list_free(volumes);

  return 0;
}

I don't know if it's relevant, but I also tried running "udevadm 
monitor" while plugging in and removing the phone. This is what I got 
with a 4.13 kernel (4.13.13-1):


KERNEL[50.806104] add  /devices/pci:00/:00:14.0/usb3/3-9 (usb)
KERNEL[50.806778] add 
/devices/pci:00/:00:14.0/usb3/3-9/3-9:1.0 (usb)

UDEV  [50.811697] add  /devices/pci:00/:00:14.0/usb3/3-9 (usb)
UDEV  [50.815390] add 
/devices/pci:00/:00:14.0/usb3/3-9/3-9:1.0 (usb)
KERNEL[54.278046] remove 
/devices/pci:00/:00:14.0/usb3/3-9/3-9:1.0 (usb)

KERNEL[54.278584] remove   /devices/pci:00/:00:14.0/usb3/3-9 (usb)
UDEV  [54.279883] remove 
/devices/pci:00/:00:14.0/usb3/3-9/3-9:1.0 (usb)

UDEV  [54.281104] remove   /devices/pci:00/:00:14.0/usb3/3-9 (usb)

And this is what I got with the aforementioned 4.14 kernel:

KERNEL[69.838042] add  /devices/pci:00/:00:14.0/usb1/1-9 (usb)
KERNEL[69.838679] add 
/devices/pci:00/:00:14.0/usb1/1-9/1-9:1.0 (usb)

KERNEL[69.838770] bind /devices/pci:00/:00:14.0/usb1/1-9 (usb)
UDEV  [69.843453] add  /devices/pci:00/:00:14.0/usb1/1-9 (usb)
UDEV  [69.845072] add 
/devices/pci:00/:00:14.0/usb1/1-9/1-9:1.0 (usb)

UDEV  [69.849294] bind /devices/pci:00/:00:14.0/usb1/1-9 (usb)
KERNEL[73.46] remove 
/devices/pci:00/:00:14.0/usb1/1-9/1-9:1.0 (usb)

KERNEL[73.667196] unbind   /devices/pci:00/:00:14.0/usb1/1-9 (usb)
KERNEL[73.667273] remove   /devices/pci:00/:00:14.0/usb1/1-9 (usb)
UDEV  [73.668520] remove 
/devices/pci:00/:00:14.0/usb1/1-9/1-9:1.0 (usb)

UDEV  [73.670060] unbind   /devices/pci:00/:00:14.0/usb1/1-9 (usb)
UDEV  [73.670446] remove   /devices/pci:00/:00:14.0/usb1/1-9 (usb)

Regards,

Torbjörn Andersson

Bug#883938: same issue

[Tomáš Thiemel]

Have the same issue (kernel panic) after kernel upgade this night. I had to 
restore the old kernel+initrd+modules from backup (Linux xxx 3.16.0-4-amd64 #1 
SMP Debian 3.16.43-2+deb8u5 (2017-09-19) x86_64 GNU/Linux).
 
Server: HP ProLiant DL380 G6
# lspci
00:00.0 Host bridge: Intel Corporation 5520 I/O Hub to ESI Port (rev 13)
00:01.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root 
Port 1 (rev 13)
00:02.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root 
Port 2 (rev 13)
00:03.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root 
Port 3 (rev 13)
00:04.0 PCI bridge: Intel Corporation 5520/X58 I/O Hub PCI Express Root Port 4 
(rev 13)
00:05.0 PCI bridge: Intel Corporation 5520/X58 I/O Hub PCI Express Root Port 5 
(rev 13)
00:06.0 PCI bridge: Intel Corporation 5520/X58 I/O Hub PCI Express Root Port 6 
(rev 13)
00:07.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root 
Port 7 (rev 13)
00:08.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root 
Port 8 (rev 13)
00:09.0 PCI bridge: Intel Corporation 7500/5520/5500/X58 I/O Hub PCI Express 
Root Port 9 (rev 13)
00:0a.0 PCI bridge: Intel Corporation 7500/5520/5500/X58 I/O Hub PCI Express 
Root Port 10 (rev 13)
00:0d.0 Host bridge: Intel Corporation Device 343a (rev 13)
00:0d.1 Host bridge: Intel Corporation Device 343b (rev 13)
00:0d.2 Host bridge: Intel Corporation Device 343c (rev 13)
00:0d.3 Host bridge: Intel Corporation Device 343d (rev 13)
00:0d.4 Host bridge: Intel Corporation 7500/5520/5500/X58 Physical Layer Port 0 
(rev 13)
00:0d.5 Host bridge: Intel Corporation 7500/5520/5500 Physical Layer Port 1 
(rev 13)
00:0d.6 Host bridge: Intel Corporation Device 341a (rev 13)
00:0e.0 Host bridge: Intel Corporation Device 341c (rev 13)
00:0e.1 Host bridge: Intel Corporation Device 341d (rev 13)
00:0e.2 Host bridge: Intel Corporation Device 341e (rev 13)
00:0e.3 Host bridge: Intel Corporation Device 341f (rev 13)
00:0e.4 Host bridge: Intel Corporation Device 3439 (rev 13)
00:14.0 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub System Management 
Registers (rev 13)
00:14.1 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub GPIO and Scratch Pad 
Registers (rev 13)
00:14.2 PIC: Intel Corporation 7500/5520/5500/X58 I/O Hub Control Status and 
RAS Registers (rev 13)
00:1c.0 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root 
Port 1
00:1c.2 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root 
Port 3
00:1d.0 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI 
Controller #1
00:1d.1 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI 
Controller #2
00:1d.2 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI 
Controller #3
00:1d.3 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI 
Controller #6
00:1d.7 USB controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI 
Controller #1
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90)
00:1f.0 ISA bridge: Intel Corporation 82801JIB (ICH10) LPC Interface Controller
01:03.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
ES1000 (rev 02)
01:04.0 System peripheral: Compaq Computer Corporation Integrated Lights Out 
Controller (rev 03)
01:04.2 System peripheral: Compaq Computer Corporation Integrated Lights Out  
Processor (rev 03)
01:04.4 USB controller: Hewlett-Packard Company Integrated Lights-Out Standard 
Virtual USB Controller
01:04.6 IPMI SMIC interface: Hewlett-Packard Company Integrated Lights-Out 
Standard KCS Interface
02:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit 
Ethernet (rev 20)
02:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit 
Ethernet (rev 20)
03:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit 
Ethernet (rev 20)
03:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit 
Ethernet (rev 20)
04:00.0 RAID bus controller: Hewlett-Packard Company Smart Array G6 controllers 
(rev 01)
14:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9125 PCIe SATA 6.0 
Gb/s controller (rev 11)
3e:00.0 Host bridge: Intel Corporation Xeon 5600 Series QuickPath Architecture 
Generic Non-core Registers (rev 02)
3e:00.1 Host bridge: Intel Corporation Xeon 5600 Series QuickPath Architecture 
System Address Decoder (rev 02)
3e:02.0 Host bridge: Intel Corporation Xeon 5600 Series QPI Link 0 (rev 02)
3e:02.1 Host bridge: Intel Corporation Xeon 5600 Series QPI Physical 0 (rev 02)
3e:02.2 Host bridge: Intel Corporation Xeon 5600 Series Mirror Port Link 0 (rev 
02)
3e:02.3 Host bridge: Intel Corporation Xeon 5600 Series Mirror Port Link 1 (rev 
02)
3e:02.4 Host bridge: Intel Corporation Xeon 5600 Series QPI Link 1 (rev 02)
3e:02.5 Host bridge: Intel Corporation Xeon 5600 Series QPI Physical 1 (rev 02)
3e:03.0 Host bridge: Intel Corporation Xeon 5600 Series Integrated Memory 
Controller Registers (rev 02)
3e:03.1 

Bug#884023: [Pkg-crosswire-devel] Bug#884023: bibledit: Installs same file as bibledit-gtk

[Teus Benschop]

Thank you for the remark about the same file that gets shipped in
"bibledit-gtk" and in "bibledit".
Recently we had a fix for this on Ubuntu too, not sure why this fix didn't
make it to Debian.
I'll have a look at this one to get it fixed.
Thanks!

On Sun, 10 Dec 2017 at 16:18 Jeremy Bicha  wrote:

> Source: bibledit
> Version: 5.0.331-1
> Severity: serious
>
> Both bibledit-gtk and bibledit ship the same file:
> /usr/share/pixmaps/bibledit.xpm
>
> See § 7.6.1 of Debian Policy which recommends that you use Breaks/Replaces
> here.
> https://www.debian.org/doc/debian-policy/#document-ch-relationships
>
> Also, I highly recommend that you add a transitional package so that
> people using bibledit-gtk will be upgraded to bibledit.
>
> Thanks,
> Jeremy Bicha
>
> ___
> Pkg-crosswire-devel mailing list
> pkg-crosswire-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-crosswire-devel

Bug#884014: apparmor: AppArmor does not allow Thunderbird to open Hyperlinks with Chromium

[intrigeri]

Control: tag -1 + upstream
Control: tag -1 + fixed-upstream

Hi Martin!

Martin:
> if Chromium is configured as the default web browser, then clicking a 
> hyperlink
> in Thunderbird has no effect. The following error message is printed:

>   Failed to execute child process “/usr/bin/chromium” (Permission denied).

Thanks for reporting.

> After having a look at /etc/apparmor.d/abstractions/ubuntu-browsers, I noticed
> that the only lines referring to chromium are the following:

>   /usr/bin/chromium-browser Cx -> sanitized_helper,
>   /usr/lib/chromium-browser/chromium-browser Cx -> sanitized_helper,

> These paths appear to be incorrect. On Debian testing at least, they should
> read as follows:

>   /usr/bin/chromium Cx -> sanitized_helper,
>   /usr/lib/chromium/chromium Cx -> sanitized_helper,

Right, we've fixed this upstream a few months ago:
https://gitlab.com/apparmor/apparmor/commit/cc5a23d4c1236a0221f7bae0fd3d59f583ec9a1d

> However, while this does allow Thunderbird to execute /usr/bin/chromium, it
> still doesn't fix the problem. Clicking on a hyperlink now prints the 
> following
> stack trace to the console:

> /usr/lib/chromium/chrome-sandbox: error while loading shared libraries:

I believe an update of abstractions/ubuntu-helpers is needed to fix
that, see the second part of the commit I've linked to above.
Can you please confirm?

So this should be fixed in Debian once we package AppArmor 2.11.95
(aka. 2.12~beta1), unless someone wants to cherry-pick this commit as
a Debian patch for now.

Cheers,
-- 
intrigeri

Bug#882699: ngspice: Remove build dependency on elyxer to allow for the elyxer removal from Debian

[Gudjon I. Gudjonsson]

Hi Sven and Andreas

I'm terribly sorry for having missed the bug.
There is a new version in SVN (27) that is not fully prepared but will
be in the next few days. If somebody is willing to sponsor it I will be
very happy.

Andreas: Moving from SVN to git is fine by me, I will try to find out how to do 
that.

Regards
Gudjon

Bug#884047: [Pkg-crosswire-devel] Bug#884047: bibledit: please make the build reproducible

[Teus Benschop]

Thank you for that, I will look into this, and see that such build-files
won't make it to the data directory, as it indeed should not. Thanks again
for noticing this!

On Sun, 10 Dec 2017 at 21:33 Chris Lamb  wrote:

> Source: bibledit
> Version: 5.0.331-1
> Severity: wishlist
> Tags: patch
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: timestamps
> X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
>
> Hi,
>
> Whilst working on the Reproducible Builds effort [0], we noticed
> that bibledit could not be built reproducibly.
>
> This is because it uselessly ships config.log etc. in the binary
> packages which include all sorts of environment-specific data.
>
> Patch attached that simply doesn't install these files... BUT it looks
> like there is a whole bunch of cruft in the -data package anyway,
> essentially including the build-directory itself (with Makefile.am etc.
> etc.)
>
> In other words, only specifying the stuff bibledit really needs in
> bibledit-data.install would be the superior solution. :)
>
>  [0] https://reproducible-builds.org/
>
>
> Regards,
>
> --
>   ,''`.
>  : :'  : Chris Lamb
>  `. `'`  la...@debian.org / chris-lamb.co.uk
>`-
> ___
> Pkg-crosswire-devel mailing list
> pkg-crosswire-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-crosswire-devel

Bug#884065: mariadb-10.2: CVE-2017-10378 CVE-2017-10268 CVE-2017-15365

[Salvatore Bonaccorso]

Control: retitle -1 mariadb-10.2 CVE-2017-10378 CVE-2017-10268 CVE-2017-15365 
CVE-2017-3636 CVE-2017-3641 CVE-2017-3653 CVE-2017-10320 CVE-2017-10365 
CVE-2017-10379 CVE-2017-10384 CVE-2017-10286 CVE-2017-3257 

On Mon, Dec 11, 2017 at 07:19:22AM +0100, Salvatore Bonaccorso wrote:
> Source: mariadb-10.2
> Version: 10.2.7-1
> Severity: grave
> Tags: security upstream
>
> Hi,
>
> the following vulnerabilities were published for mariadb-10.2, these
> are fixed in 10.2.10.

There are the following more as well adressend in 10.2.8:

CVE-2017-3636
CVE-2017-3641
CVE-2017-3653
CVE-2017-10320
CVE-2017-10365
CVE-2017-10379
CVE-2017-10384
CVE-2017-10286
CVE-2017-3257

Cf. https://mariadb.com/kb/en/library/mariadb-1028-release-notes/

Regards,
Salvatore

Bug#881936: apparmor: support usrmerge

[intrigeri]

Control: tag -1 + fixed-upstream

Héctor Orón Martínez:
> FYI patch got merged upstream:
> https://gitlab.com/apparmor/apparmor/commit/b24a1c4d546a6825f252d27243e09c80d04cf484

Congrats! Tagging this bug accordingly :)

Bug#884066: Debian mirror ftp.halifax.rwth-aachen.de: out-of-date

[Bastian Blank]

Package: mirrors
User: mirr...@packages.debian.org
Usertags: mirror-problem may-auto-close
Control: submitter -1 mirr...@debian.org

Hi

You receive this mail because you are listed as contact for:
  ftp.halifax.rwth-aachen.de

Your mirror have not finished a single sync since almost three days.
Please investigate.

In the meantime, I pointed ftp2.de.debian.org to another system.

Regards,
Bastian

-- 
We Klingons believe as you do -- the sick should die.  Only the strong
should live.
-- Kras, "Friday's Child", stardate 3497.2

Bug#884043: obfsproxy: Ship an AppArmor profile again

[intrigeri]

Hi,

I suggest first checking why we're still including obfsproxy:
I suspect most of the reverse-dependency relationships might be
obsolete nowadays (the last upstream version was released 3 years ago,
and AFAIK obfs4proxy is the future).

If obfsproxy is still useful in contexts where AppArmor confining
matters, I'm fine with us including a profile again *if* someone
commits to maintaining it, which apparently is hard to do properly
without routinely using it on testing/sid.

Thanks!

Cheers,
-- 
intrigeri

Bug#884065: mariadb-10.2: CVE-2017-10378 CVE-2017-10268 CVE-2017-15365

[Salvatore Bonaccorso]

Source: mariadb-10.2
Version: 10.2.7-1
Severity: grave
Tags: security upstream

Hi,

the following vulnerabilities were published for mariadb-10.2, these
are fixed in 10.2.10.

CVE-2017-10378[0]:
| Vulnerability in the MySQL Server component of Oracle MySQL
| (subcomponent: Server: Optimizer). Supported versions that are
| affected are 5.5.57 and earlier, 5.6.37 and earlier and 5.7.11 and
| earlier. Easily exploitable vulnerability allows low privileged
| attacker with network access via multiple protocols to compromise
| MySQL Server. Successful attacks of this vulnerability can result in
| unauthorized ability to cause a hang or frequently repeatable crash
| (complete DOS) of MySQL Server. CVSS 3.0 Base Score 6.5 (Availability
| impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).

CVE-2017-10268[1]:
| Vulnerability in the MySQL Server component of Oracle MySQL
| (subcomponent: Server: Replication). Supported versions that are
| affected are 5.5.57 and earlier, 5.6.37 and earlier and 5.7.19 and
| earlier. Difficult to exploit vulnerability allows high privileged
| attacker with logon to the infrastructure where MySQL Server executes
| to compromise MySQL Server. Successful attacks of this vulnerability
| can result in unauthorized access to critical data or complete access
| to all MySQL Server accessible data. CVSS 3.0 Base Score 4.1
| (Confidentiality impacts). CVSS Vector:
| (CVSS:3.0/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N).

CVE-2017-15365[2]:
Replication in sql/event_data_objects.cc occurs before ACL checks

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-10378
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10378
[1] https://security-tracker.debian.org/tracker/CVE-2017-10268
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10268
[2] https://security-tracker.debian.org/tracker/CVE-2017-15365
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15365

Regards,
Salvatore

Bug#883938: HP ProLiant DL360 Gen9

[Stephane Lapie]

Hi,

I also got some hardware refusing to boot with this bug :
HP ProLiant DL360 Gen9

The crash is instant, right after GRUB loads the kernel and initramfs.

Partial backtrace (re-typed from a KVM screen capture) :
[0.649289] Call Trace:
[0.649362]  [] ? sched_init_smp+0x398/0x452
[0.649437]  [] ? mutex_lock+0xe/0x2a
[0.649512]  [] ? put_online_cpus+0x23/0x80
[0.649587]  [] ? stop_machine+0x2c/0x40
[0.649662]  [] ? kernel_init_freeable+0xdd/0x1e1
[0.649738]  [] ? rest_init+0x80/0x80
[0.649813]  [] ? kernel_init+0xa/0xf0
[0.649888]  [] ? ret_from_fork+0x58/0x90
[0.649963]  [] ? rest_init+0x80/0x80
[0.650037] Code: c0 0f 85 46 05 00 00 48 8b 74 24 08 48 c7 c2 00 dd a6
81 bf ff ff ff ff e8 91 78 21 00 48 98 49 8b 56 10 48 8b 04 c5 a0 1e 8e 81
<48> 8b 14 10 b8 01 00 00 00 49 89 54 24 10 f0 0f c1 02 85 c0 75
[0.653853] RIP  [] build_sched_domains+0x72d/0xcf0
[0.653986]  RSP 
[0.654061] ---[ end trace 5d1a1ddbcedef31d ]---
[0.654145] Kernel panic - not syncing: Attempted to kill init! exit
code=0x000b
[0.654145]
[0.654252] ---[ end Kernel panic - not syncing: Attempted to kill init!
exit code=0x000b
[0.654252]

I could only fix the issue by downgrading.
It should be noted that even after the downgrade, it reports this error, if
there is any chance of relevance :
[0.059876] [Firmware Bug]: the BIOS has corrupted hw-PMU resources (MSR
38d is 330)

Cheers,
-- 
ラピー ステファン Lapie Stephane
株式会社朝日ネット システム部
AsahiNet, Inc. - System Division

Bug#883156: version 1.1

[Paolo Greppi]

Il 10/12/2017 21:16, Samuel Thibault ha scritto:
> Hello,
> 
> Paolo Greppi, on lun. 04 déc. 2017 18:24:46 +0100, wrote:
>> P.S. IMHO it would make sense to separate the libttspico-utils binary 
>> package from the svox source package.
>> In this way it would have its own version number, plus the code would not be 
>> in a patch 
>> but in plaintext.
> 
> Indeed, it makes a lot of sense, it "just needs" to be done, any taker ? :)
> (it means: submitting the ITP, setting up a repo on alioth for the
> debian packaging, writing the packaging bits, and upload. I can quickly
> do the last step if all the previous steps are done).
> 
> Samuel

I can do the ITP and the packaging.

I propose to name the new source pico2wave.
It would produce a new binary pico2wave and a transitional libttspico-utils as 
per:
https://wiki.debian.org/RenamingPackages

Re. the repo on alioth, as a DM I can not write in 
git.debian.org:/git/collab-maint
so somebody should create the pico2wave.git directory in there and assign the 
owner to paolog-guest.
Or we place the repo somewhere else.

Paolo

Bug#875858: pkgsel: Offer to install/manage unattended-upgrades

[Christian PERRIER]

Quoting Raymond Burkholder (r...@oneunified.net):
> > 
> > I think its totally adequate to assume people want automatic security
> > updates, on all kinds of systems, unless they opt out.
> 
> Security updates, yes.  Automated, no.  Desktops, maybe.  Servers, no.
> 
> For my infrastructure, updates, of what ever kind, need to be incorporated 
> into the test/build/roll-out cycle.
> 
> Unless I misunderstand the intent of this thread.
> 
> So, as an accommodation,  a flag in the preseed mechanism to enable/disable 
> would be helpful.  But would need to be exposed in maybe the expert mode 
> menus, which I think was already mentioned.


You mean something like:

emplate: pkgsel/update-policy
Type: select
Default: unattended-upgrades
Choices-C: none, unattended-upgrades
__Choices: No automatic updates, Install security updates automatically
_Description: Updates management on this system:
 Applying updates on a frequent basis is an important part of keeping the
 system secure.
 .
 By default, security updates are automatically installed by the
 unattended-upgrades package. Alternatively, you can opt-out from
 this system and apply updates manually using standard package management
 tools.


pkgsel/update-policy=none thus seem the perfect preseed choice for
your use case.




signature.asc
Description: PGP signature

Bug#883980: Fifth Manifestation

[Gerard M. Vignes]

I was using the latest, built-in version of Firefox ESR 52.5.2 (64-bit), 
and I noticed that I got the same, consistent problem as with Chromium.


When I move the mouse cursor between surrounding page and embedded video 
(either direction), the screen goes black for 1 second. This behavior is 
identical to what I experience in Chromium.


This is the list of applications for which I have seen this problem so far:
Chromium
Terminator
Terminal running Bash
Software
Firefox ESR

Bug#866758: upgrade-reports: Gnome3 boots only to Wayland session

[Roger Takeshi Imai]

Package: upgrade-reports
Followup-For: Bug #866758


Following the Debian upgrade below, GDM3 boots to a blank *graphical desktop* 
when Default X11 login is selected. Desktop shuts down automatically after 
several minutes, (usually.)

The cursor is active at login prompt, then disappears if 'System X11 Default,' 
'Gnome,' 'Gnome Classic,' is selected and the login button is pressed. An 
unresponsive desktop background displays with no cursor.

The desktop appears to start normally only when 'Gnome on Wayland' is selected. 
(However, some applications still have display issues on Wayland, including 
Gedit. Therefore, this workaround is not very satisfactory.)


Commandline: /usr/bin/unattended-upgrade
Upgrade: libxcursor1:amd64 (1:1.1.14-1+b4, 1:1.1.14-1+deb9u1)
End-Date: 2017-12-09  00:11:57

Start-Date: 2017-12-10  19:54:15
Commandline: packagekit role='update-packages'
Upgrade: dbus-x11:amd64 (1.10.22-0+deb9u1, 1.10.24-0+deb9u1), libdbus-1-3:amd64 
(1.10.22-0+deb9u1, 1.10.24-0+deb9u1), linux-libc-dev:amd64 (4.9.51-1, 
4.9.65-3), fig2dev:amd64 (1:3.2.6a-2, 1:3.2.6a-2+deb9u1), transfig:amd64 
(1:3.2.6a-2, 1:3.2.6a-2+deb9u1), dbus:amd64 (1.10.22-0+deb9u1, 
1.10.24-0+deb9u1), python2.7-minimal:amd64 (2.7.13-2, 2.7.13-2+deb9u2), 
libsqlite3-0:amd64 (3.16.2-5, 3.16.2-5+deb9u1), libicu57:amd64 (57.1-6, 
57.1-6+deb9u1), liblouis12:amd64 (3.0.0-3+b1, 3.0.0-3+deb9u1), 
linux-image-4.9.0-4-amd64:amd64 (4.9.51-1, 4.9.65-3), libpython2.7:amd64 
(2.7.13-2, 2.7.13-2+deb9u2), python2.7:amd64 (2.7.13-2, 2.7.13-2+deb9u2), 
python3-louis:amd64 (3.0.0-3, 3.0.0-3+deb9u1), 
linux-headers-4.9.0-4-common:amd64 (4.9.51-1, 4.9.65-3), 
linux-compiler-gcc-6-x86:amd64 (4.9.51-1, 4.9.65-3), gdm3:amd64 (3.22.3-3, 
3.22.3-3+deb9u1), gir1.2-gdm-1.0:amd64 (3.22.3-3, 3.22.3-3+deb9u1), 
libxkbcommon-x11-0:amd64 (0.7.1-1, 0.7.1-2~deb9u1), libgdm1:amd64 (3.22.3-3, 
3.22.3-3+deb9u1), linux-kbuild-4.9
 :amd64 (4.9.51-1, 4.9.65-3), iproute2:amd64 (4.9.0-1, 4.9.0-1+deb9u1), 
openssh-client:amd64 (1:7.4p1-10+deb9u1, 1:7.4p1-10+deb9u2), 
libpython2.7-minimal:amd64 (2.7.13-2, 2.7.13-2+deb9u2), liblouis-data:amd64 
(3.0.0-3, 3.0.0-3+deb9u1), linux-headers-4.9.0-4-amd64:amd64 (4.9.51-1, 
4.9.65-3), dbus-user-session:amd64 (1.10.22-0+deb9u1, 1.10.24-0+deb9u1), 
libpython2.7-stdlib:amd64 (2.7.13-2, 2.7.13-2+deb9u2), libxkbcommon0:amd64 
(0.7.1-1, 0.7.1-2~deb9u1), base-files:amd64 (9.9+deb9u2, 9.9+deb9u3)
End-Date: 2017-12-10  19:56:04

~$ uname -r
4.9.0-4-amd64

~$ lsb_release -d
Description:Debian GNU/Linux 9.3 (stretch)

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

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


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

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

Bug#883731: audacious: Debian packaging has incorrect license

[John Lindgren]

On 12/10/2017 06:12 PM, Nicholas D Steeves wrote:
> In particular I'm concerned about lines like this from
> d/copyright:
> 
> "po/uk.po" is © 2005 Mykola Lynnyk and is distributed under the terms of the
>  GPL.
> 
> Where the new po/uk.po is GPL-incompatible 2-clause BSD:

The line "Copyright (C) 2005 Mykola Lynnyk <...>" appears to have been
lost accidentally in commit 1a013156d209b, when we switched over to
Transifex.  I'll see about restoring it.

As far as our Git history goes back (to October 2005), uk.po had no
license declaration and was assumed to be under the same license as the
source files it translated (which at the time was GPLv2+). At the time
of the BSD relicense, we took the liberty of assuming that such
translations would automatically switch to the new license along with
the source files they translated.  No one (to my knowledge) has
contacted us in the five years since to clarify that their translations
were intended to be forever GPL-only, but I suppose that to take a more
cautious approach, Debian could still distribute the package as GPL in
total.

> Oh, and if
> everything goes according to plan we'll have a qt variant again
> sometime in 2018 (one src:package will build the gtk variant, cleanup,
> build the qt variant, and then package the two variants separately).

+1 from me!

John

Bug#884064: ITP: jsonrpclib-pelix -- This project is an implementation of the JSON-RPC v2.0 specification (backwards-

[Tristan Seligmann]

Package: wnpp
Severity: wishlist
Owner: Tristan Seligmann 

* Package name: jsonrpclib-pelix
  Version : 0.3.1
  Upstream Author : Thomas Calmant 
* URL : http://github.com/tcalmant/jsonrpclib/
* License : Apache License 2.0
  Programming Lang: Python
  Description : This project is an implementation of the JSON-RPC v2.0 
specification (backwards-

Binary package names: python3-jsonrpclib-pelix

This is a fork of jsonrpclib used by electrum for Python 3 support; I intend
not to ship the Python 2 package to avoid conflicts with python-jsonrpclib.

Bug#884063: vlc-plugin-base: fails to upgrade from 'sid' - trying to overwrite /usr/lib/x86_64-linux-gnu/vlc/plugins/codec/libzvbi_plugin.so

[Andreas Beckmann]

Package: vlc-plugin-base
Version: 3.0.0~rc1~20171210-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package vlc-plugin-base:amd64.
  Preparing to unpack .../155-vlc-plugin-base_3.0.0~rc1~20171210-2_amd64.deb ...
  Unpacking vlc-plugin-base:amd64 (3.0.0~rc1~20171210-2) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-PUAXac/155-vlc-plugin-base_3.0.0~rc1~20171210-2_amd64.deb 
(--unpack):
   trying to overwrite 
'/usr/lib/x86_64-linux-gnu/vlc/plugins/codec/libzvbi_plugin.so', which is also 
in package vlc-plugin-zvbi:amd64 2.2.8-2+b1
  Errors were encountered while processing:
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
   
/tmp/apt-dpkg-install-PUAXac/155-vlc-plugin-base_3.0.0~rc1~20171210-2_amd64.deb


cheers,

Andreas


vlc-plugin-zvbi=2.2.8-2+b1_vlc-plugin-base=3.0.0~rc1~20171210-2.log.gz
Description: application/gzip

Bug#883966: debian-policy: please add MIT/Expat to common licenses

[Russ Allbery]

Markus Koschany  writes:

> as discussed on debian-devel [1] I would like to see that more DFSG
> licenses are added to /usr/share/common-licenses and that package
> maintainers are just allowed to reference them.

> License: MIT / Expat
> Source: https://opensource.org/licenses/mit-license.php
> Example packages: https://wiki.debian.org/DFSGLicenses#The_MIT_License

I continue to be concerned that adding any version of this license to
common-licenses will create a trap for the unwary.  There are very
frequent wording differences in the exact terms of this license between
different packages, and any version that doesn't exactly match the wording
that we include in common-licenses still legally needs to be reproduced in
the package's copyright file.  And this is an error that's very hard to
find with Lintian.

-- 
Russ Allbery (r...@debian.org)   

Bug#884062: python-cryptography: please update to 2.1.4

[Sandro Tosi]

Package: python-cryptography
Version: 1.7.1-3
Severity: wishlist

Hello,
the latest pyopenssl release (17.5.0) depends on cryptography 2.1.4, but debian
currently has 2.1.3 - could you please update it?

Thanks,
Sandro

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

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

Versions of packages python-cryptography depends on:
ii  libc62.24-11
ii  libssl1.11.1.0f-3
ii  python   2.7.13-2
pn  python-cffi-backend-api-max  
pn  python-cffi-backend-api-min  
ii  python-enum341.1.6-1
ii  python-idna  2.2-1
ii  python-ipaddress 1.0.17-1
ii  python-pyasn10.1.9-2
ii  python-setuptools33.1.1-1
ii  python-six   1.10.0-4

python-cryptography recommends no packages.

Versions of packages python-cryptography suggests:
pn  python-cryptography-doc  
pn  python-cryptography-vectors  

-- no debconf information

Bug#875433: The packages "list of files" data has not been updated for at least TWO YEARS

[David Steele]

severity -1 important

On the packages.d.o binary packages pages, a "list of files" link is offered 
for every supported
architecture. For (at least many) packages that have been introduced in the 
last two years, that link points to a page that says "No such package in this 
suite on this architecture".

https://packages.debian.org/sid/net/comitup
https://packages.debian.org/sid/all/comitup/filelist

https://packages.debian.org/sid/gocryptfs
https://packages.debian.org/sid/arm64/gocryptfs/filelist

https://packages.debian.org/sid/golang-github-rfjakob-eme-dev
https://packages.debian.org/sid/all/golang-github-rfjakob-eme-dev/filelist

For older packages, the information is way stale. The gnome-gmail package 
introduced the file gnomegmail.py in 2015, but it is not represented in the 
displayed list of files.

https://packages.debian.org/sid/gnome/gnome-gmail
https://packages.debian.org/sid/all/gnome-gmail/filelist

This feature should be fixed or removed in the short term.

Bumping severity because two years.

-- 
AE0D BF5A 92A5 ADE4 9481  BA6F 8A31 71EF 3661 50CE


signature.asc
Description: GooPG digital signature

Bug#875572: unifont FTCBFS: many reasons

[Paul Hardy]

On Tue, Oct 31, 2017 at 1:52 PM, Manuel A. Fernandez Montecelo
 wrote:
> Control: tags -1 + pending

I just want to note that this has not fallen off my radar.  I have
already applied the patch in the upcoming version.

I am hoping to provide a resolution to over 40 bug reports that
someone has made against Unifont over the past few months on Savannah:

https://savannah.gnu.org/bugs/?group=unifont

I hope to get through most of those over the next month, and then
provide an updated version for Debian.  I had worked through many more
for the current Unifont release.

This Debian bug was mentioned as being low priority, so I would like
to submit the next release with as many updates as possible versus a
"micro-release".

I also recently helped the HarfBuzz maintainer identify a HarfBuzz
bug.  HarfBuzz renders glyphs for Pango, which in turn renders text
for GNOME.  I was not sure if there was something deep down in
Unifont's structure that I would have to update, but that turns out
not to be the case:

https://bugzilla.gnome.org/show_bug.cgi?id=787284

If anyone does need this patch applied urgently, let me know and I
will be able to fix it the following weekend.  Otherwise, I am
planning for a Unifont update with a lot of glyph fixes.

Thank you,


Paul Hardy

Bug#884061: linux-image-4.9.0-4-amd64: screen scrolls wildly

[Vagrant Cascadian]

Package: src:linux
Version: 4.9.65-3
Severity: normal

Since upgrading to 4.9.65-3, my screen occasionally starts rapidly
scrolling sideways, flashing on and off repeatedly... looks almost like
the refresh rate or sync was off, and it's displaying the leftmost part
of the screen on the rightmost or the top of the display in the middle
of the screen and other similar behaviors...

When this starts to happen, usually there is a log in the dmesg output
like this:

  [drm:gen8_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun

Closing the lid and openening it again seems to fix it for a while, or
makes it less severe (e.g. brief moments where the screen slides around
or flickers).

I'm going to try to find the last kernel version before I upgraded and
see if I the issue is also triggered on that...

live well,
  vagrant


-- Package-specific info:
** Version:
Linux version 4.9.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 
20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.65-3 (2017-12-03)

** Command line:
BOOT_IMAGE=/vmlinuz-4.9.0-4-amd64 root=/dev/mapper/yucca--vg-root ro quiet

** Not tainted

** Kernel log:
[   15.039432] tun: Universal TUN/TAP device driver, 1.6
[   15.039434] tun: (C) 1999-2004 Max Krasnyansky 
[   20.700661] input: BYDPS/2 BYD TouchPad as 
/devices/platform/i8042/serio1/input/input16
[   80.954137] [drm:gen8_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
[  170.836656] PM: Syncing filesystems ... done.
[  170.842268] PM: Preparing system for sleep (mem)
[  170.842382] Freezing user space processes ... (elapsed 0.001 seconds) done.
[  170.843569] Freezing remaining freezable tasks ... (elapsed 0.003 seconds) 
done.
[  170.846679] PM: Suspending system (mem)
[  170.846687] Suspending console(s) (use no_console_suspend to debug)
[  170.846858] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[  170.847683] sd 0:0:0:0: [sda] Stopping disk
[  171.622232] PM: suspend of devices complete after 775.439 msecs
[  171.641624] PM: late suspend of devices complete after 19.389 msecs
[  171.642387] xhci_hcd :00:14.0: System wakeup enabled by ACPI
[  171.681571] PM: noirq suspend of devices complete after 39.943 msecs
[  171.681842] ACPI: Preparing to enter system sleep state S3
[  171.681903] ACPI : EC: event blocked
[  171.681903] ACPI : EC: EC stopped
[  171.681904] PM: Saving platform NVS memory
[  171.681905] Disabling non-boot CPUs ...
[  171.683157] smpboot: CPU 1 is now offline
[  171.683865] Broke affinity for irq 49
[  171.684874] smpboot: CPU 2 is now offline
[  171.685248] Broke affinity for irq 1
[  171.685255] Broke affinity for irq 9
[  171.685260] Broke affinity for irq 12
[  171.685273] Broke affinity for irq 47
[  171.685274] Broke affinity for irq 49
[  171.686288] smpboot: CPU 3 is now offline
[  171.687652] ACPI: Low-level resume complete
[  171.687705] ACPI : EC: EC started
[  171.687706] PM: Restoring platform NVS memory
[  171.688023] Suspended for 4.062 seconds
[  171.688050] Enabling non-boot CPUs ...
[  171.688106] x86: Booting SMP configuration:
[  171.688106] smpboot: Booting Node 0 Processor 1 APIC 0x1
[  171.690656]  cache: parent cpu1 should not be sleeping
[  171.690885] CPU1 is up
[  171.690936] smpboot: Booting Node 0 Processor 2 APIC 0x3
[  171.693606]  cache: parent cpu2 should not be sleeping
[  171.694177] CPU2 is up
[  171.694277] smpboot: Booting Node 0 Processor 3 APIC 0x2
[  171.697493]  cache: parent cpu3 should not be sleeping
[  171.698318] CPU3 is up
[  171.706857] ACPI: Waking up from system sleep state S3
[  171.727103] xhci_hcd :00:14.0: System wakeup disabled by ACPI
[  171.747157] PM: noirq resume of devices complete after 40.223 msecs
[  171.747360] PM: early resume of devices complete after 0.186 msecs
[  171.747431] ACPI : EC: event unblocked
[  171.747529] ath: phy0: ASPM enabled: 0x43
[  171.757620] sd 0:0:0:0: [sda] Starting disk
[  171.820062] rtc_cmos 00:03: System wakeup disabled by ACPI
[  172.070341] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[  172.070732] ata1.00: supports DRM functions and may not be fully accessible
[  172.072477] ata1.00: disabling queued TRIM support
[  172.073107] ata1.00: supports DRM functions and may not be fully accessible
[  172.073834] ata1.00: disabling queued TRIM support
[  172.074067] ata1.00: configured for UDMA/133
[  172.175151] PM: resume of devices complete after 427.782 msecs
[  172.175516] PM: Finishing wakeup.
[  172.175518] Restarting tasks ... done.
[  172.267311] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
[  172.295044] usb 1-5: new full-speed USB device number 6 using xhci_hcd
[  172.309093] r8169 :02:00.0 enp2s0: link down
[  172.309140] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
[  172.310073] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[  172.415056] usb 1-5: device descriptor read/64, error -71
[  172.643192] usb 1-5: device descriptor read/64, error -71
[  172.875059] usb 1-5: new full-speed USB 

Bug#874706:

[nurupo]

Looks like this bug got resolved. Had the same issue before, but it got
fixed in the latest (4:17.08.3-1) version of the package.

Bug#884060: iproute2: Upgrade from 4.9.0-2 to 4.9.0-2.1 breaks wireless.

[Van]

Package: iproute2
Version: 4.9.0-2
Severity: normal

Dear Maintainer,

Upgrade back in November broke wireless.  Downgrading to 4.9.0-2 fixes
the issue.  If you need log info, please tell me what you need.  This is
my first bug report, so I'm a newbie.
Wireless Info:
Broadcom BCM4352 802.11ac
Driver:  r8169

Using broadcom-sta-dkms version 6.30.223.271-7


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

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

Versions of packages iproute2 depends on:
ii  libc62.25-3
ii  libdb5.3 5.3.28-13.1+b1
ii  libelf1  0.170-0.1
ii  libmnl0  1.0.4-2
ii  libselinux1  2.7-2

Versions of packages iproute2 recommends:
pn  libatm1   
ii  libxtables12  1.6.1-2+b1

Versions of packages iproute2 suggests:
pn  iproute2-doc  

-- no debconf information

Bug#878115: plymouthd: random crash (SIGSEGV) during shutdown for reboot

[Paul Wise]

Control: retitle -1 plymouthd: crash (SIGSEGV) during shutdown for reboot
Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=104204

On Tue, 10 Oct 2017 11:53:26 +0800 Paul Wise wrote:

> During the shutdown process for rebooting I got a random crash
> (SIGSEGV) of the plymouthd process.

Looks like it isn't random and happens every time I reboot.
I've forwarded the crash to upstream, URL is available above.

$ sudo gdb -batch -n -ex 'set pagination off' -ex bt -ex 'thread apply all bt 
full' --core /var/crash/0/765-0-0-11-1512873881-chianamo--sbin-plymouthd.core 
/sbin/plymouthd
[New LWP 765]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `@sbin/plymouthd --mode=shutdown --attach-to-session'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  strlen () at ../sysdeps/x86_64/strlen.S:106
106 ../sysdeps/x86_64/strlen.S: No such file or directory.
#0  0x7f917f290f46 in strlen () at ../sysdeps/x86_64/strlen.S:106
#1  0x7f917f290c6e in __GI___strdup (s=0x0) at strdup.c:41
#2  0x7f917f5c0fb0 in ply_renderer_load_plugin (module_path=0x7f917f5c52b8 
"/usr/lib/x86_64-linux-gnu/plymouth/renderers/x11.so", renderer=0x562aa6b81a60) 
at ply-renderer.c:160
#3  0x7f917f5c0fb0 in ply_renderer_open_plugin (plugin_path=0x7f917f5c52b8 
"/usr/lib/x86_64-linux-gnu/plymouth/renderers/x11.so", renderer=0x562aa6b81a60) 
at ply-renderer.c:238
#4  0x7f917f5c0fb0 in ply_renderer_open 
(renderer=renderer@entry=0x562aa6b81a60) at ply-renderer.c:281
#5  0x7f917f5b8b82 in create_devices_for_terminal_and_renderer_type 
(manager=0x562aa6b80440, device_path=0x0, terminal=0x562aa6b804e0, 
renderer_type=PLY_RENDERER_TYPE_AUTO) at ply-device-manager.c:683
#6  0x562aa622653b in load_devices 
(flags=PLY_DEVICE_MANAGER_FLAGS_IGNORE_UDEV, state=0x7ffc246e3a50) at 
main.c:1130
#7  0x562aa622653b in main (argc=3, argv=0x7ffc246e4c38) at main.c:2368

Thread 1 (Thread 0x7f917fbbeb80 (LWP 765)):
#0  0x7f917f290f46 in strlen () at ../sysdeps/x86_64/strlen.S:106
#1  0x7f917f290c6e in __GI___strdup (s=0x0) at strdup.c:41
len = 
new = 
#2  0x7f917f5c0fb0 in ply_renderer_load_plugin (module_path=0x7f917f5c52b8 
"/usr/lib/x86_64-linux-gnu/plymouth/renderers/x11.so", renderer=0x562aa6b81a60) 
at ply-renderer.c:160
get_renderer_backend_interface = 
i = 
known_plugins = {{type = PLY_RENDERER_TYPE_X11, path = 0x7f917f5c52b8 
"/usr/lib/x86_64-linux-gnu/plymouth/renderers/x11.so"}, {type = 
PLY_RENDERER_TYPE_DRM, path = 0x7f917f5c52f0 
"/usr/lib/x86_64-linux-gnu/plymouth/renderers/drm.so"}, {type = 
PLY_RENDERER_TYPE_FRAME_BUFFER, path = 0x7f917f5c5328 
"/usr/lib/x86_64-linux-gnu/plymouth/renderers/frame-buffer.so"}, {type = 
PLY_RENDERER_TYPE_NONE, path = 0x0}}
__func__ = "ply_renderer_open"
#3  0x7f917f5c0fb0 in ply_renderer_open_plugin (plugin_path=0x7f917f5c52b8 
"/usr/lib/x86_64-linux-gnu/plymouth/renderers/x11.so", renderer=0x562aa6b81a60) 
at ply-renderer.c:238
i = 
known_plugins = {{type = PLY_RENDERER_TYPE_X11, path = 0x7f917f5c52b8 
"/usr/lib/x86_64-linux-gnu/plymouth/renderers/x11.so"}, {type = 
PLY_RENDERER_TYPE_DRM, path = 0x7f917f5c52f0 
"/usr/lib/x86_64-linux-gnu/plymouth/renderers/drm.so"}, {type = 
PLY_RENDERER_TYPE_FRAME_BUFFER, path = 0x7f917f5c5328 
"/usr/lib/x86_64-linux-gnu/plymouth/renderers/frame-buffer.so"}, {type = 
PLY_RENDERER_TYPE_NONE, path = 0x0}}
__func__ = "ply_renderer_open"
#4  0x7f917f5c0fb0 in ply_renderer_open 
(renderer=renderer@entry=0x562aa6b81a60) at ply-renderer.c:281
i = 
known_plugins = {{type = PLY_RENDERER_TYPE_X11, path = 0x7f917f5c52b8 
"/usr/lib/x86_64-linux-gnu/plymouth/renderers/x11.so"}, {type = 
PLY_RENDERER_TYPE_DRM, path = 0x7f917f5c52f0 
"/usr/lib/x86_64-linux-gnu/plymouth/renderers/drm.so"}, {type = 
PLY_RENDERER_TYPE_FRAME_BUFFER, path = 0x7f917f5c5328 
"/usr/lib/x86_64-linux-gnu/plymouth/renderers/frame-buffer.so"}, {type = 
PLY_RENDERER_TYPE_NONE, path = 0x0}}
__func__ = "ply_renderer_open"
#5  0x7f917f5b8b82 in create_devices_for_terminal_and_renderer_type 
(manager=0x562aa6b80440, device_path=0x0, terminal=0x562aa6b804e0, 
renderer_type=PLY_RENDERER_TYPE_AUTO) at ply-device-manager.c:683
old_renderer = 0x0
renderer = 0x562aa6b81a60
keyboard = 0x0
__func__ = "create_devices_for_terminal_and_renderer_type"
#6  0x562aa622653b in load_devices 
(flags=PLY_DEVICE_MANAGER_FLAGS_IGNORE_UDEV, state=0x7ffc246e3a50) at 
main.c:1130
state = {loop = 0x562aa6b79150, boot_server = 0x562aa6b7bb30, 
boot_splash = 0x0, session = 0x562aa6b7bc50, boot_buffer = 0x562aa6b7be30, 
progress = 0x562aa6b801a0, keystroke_triggers = 0x562aa6b7aaa0, entry_triggers 
= 0x562aa6b7aac0, entry_buffer = 0x562aa6b7aae0, messages = 0x562aa6b7bb10, 
command_parser = 0x562aa6b79010, mode = PLY_MODE_SHUTDOWN, 

Bug#879639: squid takes 30 seconds to restart, should be < 1 second

[Amos Jeffries]

Package: squid
Version: 4.0.21-1~exp5

This should be fixed in the upcoming Squid-4 packages.

Amos Jeffries

Bug#879801: ftbfs with icu from experimental

[Norbert Preining]

> Not sure if it is useful: I've replaced "rm -f" by "rm -fv". Now the
> build runs OK and reports which files are really found (and removed).

Very useful!

I think I have removed now all useless rm statements (the
fmtutil.cnf/updmap.cfg and the long with ep2all etc ... interesting).

Thanks a lot!

Norbert

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

Bug#884059: libnunit-core-interfaces2.6.3-cil fails to install

[A. Maitland Bottoms]

Source: nunit
Version: 2.6.4+dfsg-1
Severity: important

Rebuilding libiio in unstable fails in recent months:

Setting up libnunit-core-interfaces2.6.3-cil (2.6.4+dfsg-1) ...
Segmentation fault
Use of uninitialized value $_ in scalar chomp at 
/usr/share/cli-common/runtimes.d/mono line 275.
Use of uninitialized value $fullname in concatenation (.) or string at 
/usr/share/cli-common/runtimes.d/mono line 225.
Segmentation fault
E: installing Assembly 
/usr/share/cli-common/policies.d/libnunit-core-interfaces2.6.3-cil/policy.2.6.nunit.core.interfaces.dll
 failed
E: Installation of policy.2.6.nunit.core.interfaces with 
/usr/share/cli-common/runtimes.d/mono failed
dpkg: error processing package libnunit-core-interfaces2.6.3-cil (--configure):
 installed libnunit-core-interfaces2.6.3-cil package post-installation script 
subprocess returned error exit status 1

Setting up libnunit-framework2.6.3-cil (2.6.4+dfsg-1) ...
Segmentation fault
W: removing assembly:  failed!
Segmentation fault
Use of uninitialized value $_ in scalar chomp at 
/usr/share/cli-common/runtimes.d/mono line 275.
Use of uninitialized value $fullname in concatenation (.) or string at 
/usr/share/cli-common/runtimes.d/mono line 225.
Segmentation fault
E: installing Assembly 
/usr/share/cli-common/policies.d/libnunit-framework2.6.3-cil/policy.2.6.nunit.framework.dll
 failed
E: Installation of policy.2.6.nunit.framework with 
/usr/share/cli-common/runtimes.d/mono failed
dpkg: error processing package libnunit-framework2.6.3-cil (--configure):
 installed libnunit-framework2.6.3-cil package post-installation script 
subprocess returned error exit status 1

This Build-Depends: is uninstallable:
Build-Depends: bison,
   cli-common-dev [amd64 arm64 armel armhf i386 mipsel ppc64el 
s390x kfreebsd-any powerpc ppc64],
   cmake (>= 2.8),
   debhelper (>= 9),
   dh-python,
   doxygen,
   flex,
   libserialport-dev,
   libudev-dev [linux-any],
   libusb-1.0-0-dev [linux-any],
   libusb2-dev [kfreebsd-any],
   libxml2-dev,
   python

Adding mono-devel and mono-runtime-common does not help.

-Maitland

Bug#883761: libgdamm5.0: Includes "docs/reference/html/jquery.js" listed in Files-Excluded header

[Jeremy Bicha]

Control: severity -1 normal

On Thu, Dec 7, 2017 at 5:20 AM, Chris Lamb  wrote:
> libgdamm5.0 lists "docs/reference/html/jquery.js" in the Files-Excluded field 
> in
> debian/copyright but the source tree contain docs/reference/html/jquery.js.
>
> This is probably a DFSG violation, or at the upstream tarball was not
> repacked as intended. Alternatively, the field is simply out of date.

What really happened here is that I intentionally used the original
tarball so that the updated packaging could be synced to Ubuntu, which
requires the original tarball to match.

I don't think this is at all a DFSG violation (or if it is, it is very
minor) since the bundled jquery.js is intentionally not included in
the binary packages. This will all be fixed whenever upstream releases
a new version.

I'm lowering the severity because there is no need to kick the package
out of Testing for this.

goocanvasmm-2.0 has the same situation.

Thanks,
Jeremy Bicha

Bug#878063: ansible-pull broke fully after update from 2.3 to 2.4

[Lee]

Hi Klaus,

can you test if ansible 2.4.2 from sid fixes it for you? This version and the
one before has several fixes around ansible-pull.

Greets,
Lee

On Mon, 9 Oct 2017 11:02:19 +0100 Klaus Ethgen  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Package: ansible
> Version: 2.4.0.0+dfsg-1
> Severity: important
> 
> See https://github.com/ansible/ansible/issues/31449
> 
> - -- System Information:
> Debian Release: buster/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'testing'), (400, 'unstable'), (1, 
> 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.11.12 (SMP w/8 CPU cores)
> Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1), LANGUAGE=de_DE:en 
> (charmap=ISO-8859-1)
> Shell: /bin/sh linked to /bin/dash
> Init: sysvinit (via /sbin/init)
> 
> Versions of packages ansible depends on:
> ii  python2.7.14-1
> ii  python-crypto 2.6.1-7+b1
> ii  python-cryptography   1.9-1
> ii  python-httplib2   0.9.2+dfsg-1
> ii  python-jinja2 2.9.6-1
> ii  python-netaddr0.7.18-2
> ii  python-paramiko   2.0.0-1
> ii  python-pkg-resources  36.2.7-2
> ii  python-yaml   3.12-1+b1
> 
> Versions of packages ansible recommends:
> pn  python-jmespath   
> pn  python-kerberos   
> pn  python-libcloud   
> pn  python-selinux
> pn  python-winrm  
> pn  python-xmltodict  
> 
> Versions of packages ansible suggests:
> pn  cowsay   
> ii  sshpass  1.06-1
> 
> - -- Configuration Files:
> /etc/ansible/ansible.cfg changed:
> [defaults]
> gathering = smart
> ansible_managed = Ansible managed file
> retry_files_enabled = False
> [inventory]
> [privilege_escalation]
> become_method = su
> [paramiko_connection]
> [ssh_connection]
> pipelining = True
> [persistent_connection]
> [accelerate]
> [selinux]
> [colors]

Bug#884008: [Filesystems-devel] Bug#884008: aufs-dkms: aufs triggers kernel WARN during boot

[sfjro]

Hello Jan,

Jan Luca Naumann:
> the following Debian bug (see also webpage [1]) seems to be a upstream
> problem of the aufs-kernel-module. Could you take a look into it?

Please provide me these necessary info.

(from aufs README file)
--
When you have any problems or strange behaviour in aufs, please let me
know with:
- /proc/mounts (instead of the output of mount(8))
- /sys/module/aufs/*
- /sys/fs/aufs/* (if you have them)
- /debug/aufs/* (if you have them)
- linux kernel version
  if your kernel is not plain, for example modified by distributor,
  the url where i can download its source is necessary too.
- aufs version which was printed at loading the module or booting the
  system, instead of the date you downloaded.
- configuration (define/undefine CONFIG_AUFS_xxx)
- kernel configuration or /proc/config.gz (if you have it)
- behaviour which you think to be incorrect
- actual operation, reproducible one is better
- mailto: aufs-users at lists.sourceforge.net
--


J. R. Okajima

Bug#880596: Please backport Ansible 2.4 to stretch-backports

[Lee]

Hi Jonas,

ansible 2.4.0 is now in stretch-backports, and I'll push 2.4.2 to there as
soon as it has migrated to buster.

Greets,
Lee

On Thu, 02 Nov 2017 18:32:34 +0100 Jonas Meurer  wrote:
> Package: ansible
> Version: 2.4.0.0+dfsg-1
> Severity: wishlist
> 
> Hi Harlan,
> 
> as we discussed on IRC, it would be awesome if you could provide a
> backport of Ansible 2.4 to stretch-backports.
> 
> Amongh others, Ansible 2.4 ships several bugfixes to include_role that
> didn't get backported to 2.3, thus having 2.4 available for Stretch
> systems would be of great help.
> 
> Cheers,
>  jonas
> 
> 

Bug#883753: RFS: deepin-picker/1.6.1-1 [ITP]

[Yangfl]

Sorry. Uploaded to git and mentors.

Bug#883751: RFS: deepin-calculator/1.0.1-1 [ITP]

[Yangfl]

added patches from upstream branch.

2017-12-11 7:26 GMT+08:00 Adam Borowski :
> On Thu, Dec 07, 2017 at 04:04:41PM +0800, Yangfl wrote:
>>  * Package name: deepin-calculator
>>Version : 1.0.1-1
>
>>   It builds those binary packages:
>>
>> deepin-calculator - Calculator for deepin
>
> Lintian sez:
> W: deepin-calculator: desktop-entry-lacks-main-category 
> usr/share/applications/deepin-calculator.desktop
> and indeed, it shows in the menu as "Other".
>
> Otherwise, everything seems fine.
>
>
> 喵!
> --
> // If you believe in so-called "intellectual property", please immediately
> // cease using counterfeit alphabets.  Instead, contact the nearest temple
> // of Amon, whose priests will provide you with scribal services for all
> // your writing needs, for Reasonable And Non-Discriminatory prices.

Bug#844303: Working on it porting ncrack to OpenSSL 1.1

[Hilko Bengen]

Hi,

just a heads-up: I am working on porting ncrack to OpenSSL 1.1. There
are two main causes of issues:

(1) OpenSSL-related checks in opensshlib/configure.ac are broken, they use
old SSLeay_* APIs, this is fixed easily.

(2) The usual getter/setter mess. There's a lot of code and in
opensshlib/ that needs to be touched. Since this is more than just
search/replace, I'll try to get my patch reviewed by upstream before
making updates to the Debian package.

Cheers,
-Hilko

Bug#883378: RFS: deepin-image-viewer/1.2.16.4-1 [ITP]

[Adam Borowski]

On Sun, Dec 03, 2017 at 04:50:55PM +0800, Yangfl wrote:
>  * Package name: deepin-image-viewer
>Version : 1.2.16.4-1

>   It builds those binary packages:
> 
> deepin-image-viewer - Image Viewer for Deepin Desktop Environment

Please run lintian.  The red parts need to be fixed: dependency is obvious,
ConvertUTF.c license is nasty -- you'll have to replace that whole file.
Brown parts are because only you are marked as Uploader, yet the changelog
bears Boyuan Yang's name, not yours.  I get that you guys are working
together, but the tools have no way to know this without either adding you
both as Uploaders, mentioning "Team upload", or being careful with names.

Also, the copyright file is incomplete: for example, there are files by
2012 Alberto Mardegan .


喵!
-- 
// If you believe in so-called "intellectual property", please immediately
// cease using counterfeit alphabets.  Instead, contact the nearest temple
// of Amon, whose priests will provide you with scribal services for all
// your writing needs, for Reasonable And Non-Discriminatory prices.

Bug#884058: RFS: php-netscape-bookmark-parser/2.0.4-1 [ITP]

[James Valleroy]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "php-netscape-bookmark-parser"

 * Package name: php-netscape-bookmark-parser
   Version : 2.0.4-1
   Upstream Author : Kafene , VirtualTam

 * URL : https://github.com/shaarli/netscape-bookmark-parser
 * License : MIT Expat
   Section : php

It builds those binary packages:

  php-netscape-bookmark-parser - generic Netscape bookmark parser

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

https://mentors.debian.net/package/php-netscape-bookmark-parser


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

  dget -x
https://mentors.debian.net/debian/pool/main/p/php-netscape-bookmark-parser/php-netscape-bookmark-parser_2.0.4-1.dsc


Regards,
James Valleroy



signature.asc
Description: OpenPGP digital signature

Bug#883753: RFS: deepin-picker/1.6.1-1 [ITP]

[Adam Borowski]

On Thu, Dec 07, 2017 at 04:18:13PM +0800, Yangfl wrote:
>  * Package name: deepin-picker
>Version : 1.6.1-1

>   It builds those binary packages:
> 
> deepin-picker - Color picker tool for deepin
> 
>   To access further information about this package, please visit the
> following URL:
> 
>   https://mentors.debian.net/package/deepin-picker
> 
>   Git repo:
> 
> https://anonscm.debian.org/git/pkg-deepin/deepin-picker.git

Alas, the mentors link is 404-compliant, and the git repository has only the
upstream branch and tags.  I don't see the package already in NEW either.
Thus: have you actually uploaded it?


喵!
-- 
// If you believe in so-called "intellectual property", please immediately
// cease using counterfeit alphabets.  Instead, contact the nearest temple
// of Amon, whose priests will provide you with scribal services for all
// your writing needs, for Reasonable And Non-Discriminatory prices.

Bug#884046: jetty9 FTBFS: org.eclipse.jetty.websocket.jsr356.ClientContainer is not abstract and does not override abstract method setDefaultAsyncSendTimeout(long) in javax.websocket.WebSocketContaine

[Emmanuel Bourg]

Le 10/12/2017 à 21:13, Adrian Bunk a écrit :

> Some recent change in unstable makes jetty9 FTBFS:
> 
> https://tests.reproducible-builds.org/debian/history/jetty9.html
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/jetty9.html

This was caused by tomcat8/8.5.24-1. I'll take care of it.

Emmanuel Bourg

Bug#883751: RFS: deepin-calculator/1.0.1-1 [ITP]

[Adam Borowski]

On Thu, Dec 07, 2017 at 04:04:41PM +0800, Yangfl wrote:
>  * Package name: deepin-calculator
>Version : 1.0.1-1

>   It builds those binary packages:
> 
> deepin-calculator - Calculator for deepin

Lintian sez:
W: deepin-calculator: desktop-entry-lacks-main-category 
usr/share/applications/deepin-calculator.desktop
and indeed, it shows in the menu as "Other".

Otherwise, everything seems fine.


喵!
-- 
// If you believe in so-called "intellectual property", please immediately
// cease using counterfeit alphabets.  Instead, contact the nearest temple
// of Amon, whose priests will provide you with scribal services for all
// your writing needs, for Reasonable And Non-Discriminatory prices.

Bug#883731: audacious: Debian packaging has incorrect license

[Nicholas D Steeves]

On Mon, Dec 11, 2017 at 12:23:47AM +0100, Francesco Poli wrote:
> On Sun, 10 Dec 2017 18:12:39 -0500 Nicholas D Steeves wrote:
> 
> [...]
> > GPL-incompatible 2-clause BSD
> [...]
> 
> A nitpick: the 2-clause BSD license is not GPL-incompatible (it's
> indeed compatible with the GNU GPL).
> It's just a distinct license with different (and much simpler)
> wording...

Good point.  I ought to have phrased that differently ;-) What I mean
is that a GPL piece cannot become a BSD piece without explicit
relicensing by all copyright holders.


signature.asc
Description: PGP signature

Bug#883731: audacious: Debian packaging has incorrect license

[Francesco Poli]

On Sun, 10 Dec 2017 18:12:39 -0500 Nicholas D Steeves wrote:

[...]
> GPL-incompatible 2-clause BSD
[...]

A nitpick: the 2-clause BSD license is not GPL-incompatible (it's
indeed compatible with the GNU GPL).
It's just a distinct license with different (and much simpler)
wording...



-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpTdD2W9VOTr.pgp
Description: PGP signature

Bug#884044: Pending fixes for bugs in the jitescript package

[pkg-java-maintainers]

tag 884044 + pending
thanks

Some bugs in the jitescript package are closed in revision
19d92dc825f4844348275465114db5cc7d85c9c0 in branch 'master' by
Emmanuel Bourg

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

Commit message:

Fixed the build failure with ASM 6.0 (Closes: #884044)

Bug#884054: polyml: FTBFS on sh4: MemMgr: Assertion `t->tree[r] == 0' failed.

[James Clarke]

On 10 Dec 2017, at 23:06, John Paul Adrian Glaubitz 
 wrote:
> On 12/11/2017 12:04 AM, James Clarke wrote:
>> Yeah, I noticed this back when I was uploading to experimental a few months
>> ago. I suspect it's an issue with qemu-user's atomics support on sh4, which
>> have been notoriously unreliable in the past, and asked Adrian to see if he
>> could reproduce this on real hardware, but that never ended up happening.
> Sorry, I must have missed that. I will give that a go.

No problem, I asked once a while ago while you were busy and I've had other
priorities since so never got round to reminding you.

> Is there a reduced test case?

Not that I know of; it dies building a module with the just-built Poly/ML
compiler, so dpkg-buildpackage is probably the easiest reproducer.

James

Bug#883731: audacious: Debian packaging has incorrect license

[Nicholas D Steeves]

On Fri, Dec 08, 2017 at 10:36:49AM -0500, John Lindgren wrote:
> Nicholas D Steeves wrote:
> 
> > Both BSD 3-clause and BSD 2-clause allow relicensing as GPL, thus so
> > long as the licensing terms are complied with correctly BSD code can
> > perpetually and unidirectionally flow to GPL projects.
> 
> Yes, I agree.  It's perfectly okay for the Debian package(s) to be
> distributed as GPL, *as long as* the original BSD license text is still
> retained.
> 
> > I'm also unsure whether the patch
> > that changes the user-visible bits and the out-of-date
> > debian/copyright outweigh the 2-clause license that wasn't stripped
> > from the headers of various files.
> 
> Speaking for myself as upstream project lead, I'm not worried about
> the legal status of already-built packages, but I would prefer that the
> upstream (BSD 2-clause) license remain user-visible in future Debian
> builds.  The simplest way to achieve this would be to remove
> use-system-licenses.patch and let the GUI again display
> /usr/share/audacious/COPYING as the upstream version does.

This will be easier to do.

> Alternatively, debian/copyright could be updated to include the full
> text of the upstream license, plus any Debian-specific bits (packaging
> copyrights, etc.), and the patch could be updated so that the GUI
> displays the installed version of that file instead (I think that would
> be /usr/share/doc/audacious/copyright?)

Thank you for your blessing on doing it this way.  If Debian was/is
relicensing as GPL in a non-reversible way then this the way it
would/might have to be done.

> Francesco Poli wrote:
> 
> > The Audacious upstream developers may be willing to help, by clarifying
> > any doubts upon request.
> 
> Yes, for sure.

Please see my question about a missing copyright holder; I paused my
review at this point, so there might be other examples.

> > If that is deemed to be needed or useful, it could be feasible to also
> > fix the debian/copyright file for audacious version 3.7.2 in a Debian
> > stable update (and possibly also address the same issue for
> > oldstable)... On the other hand, this extra effort could perhaps be
> > considered not worth doing.
> 
> For my part, I'm not worried about the stable+oldstable packages being
> fixed, only that the problem is resolved in a new unstable upload going
> forward.  I think that the other upstream developers would agree.

Whew, thank you, that makes things easier for everyone :-)

> Thank you both for the prompt reply and good discussion!

You're welcome!  Thank you for reaching out.

Sincerely,
Nicholas


signature.asc
Description: PGP signature

Bug#874312: Info received (Bug#874312: Acknowledgement (kdelibs4support: FTBFS on hppa - segmentation fault in desktoptojson))

[John David Anglin]

Segmentation fault doesn't occur when kcoreaddons is built with g++-6.

Dave
--
John David Anglin   dave.ang...@bell.net

Bug#826582: hippomocks: Looking for uploader

[Philippe Coval]

Hi,
I am looking for uploader:
https://mentors.debian.net/package/hippomocks

ps: unrelated info,
my previous debian email r...@gna.org is offline,
so I reverted to older one.
-- 
http://rzr.online.fr/# gpg:0x467094BC mailto:r...@users.sf.net

   .





signature.asc
Description: OpenPGP digital signature

Bug#866734: btrfs-progs: btrfs replace fails with unknown error

[Lukas Pirl]

Hi Russel,

On Sat, 01 Jul 2017 20:40:05 +1000 Russell Coker 
wrote:
> # btrfs replace start -B 3 /dev/sdd2 /
> ERROR: ioctl(DEV_REPLACE_START) on '/' returns error: 
> # btrfs replace start -B /dev/sdb2 /dev/sdd2 /
> ERROR: ioctl(DEV_REPLACE_START) on '/' returns error: 
> # btrfs replace start -B /dev/sdc2 /dev/sdd2 /
> ERROR: ioctl(DEV_REPLACE_START) on '/' returns error: 
> # btrfs replace start -B 1 /dev/sdd2 /
> ERROR: ioctl(DEV_REPLACE_START) on '/' returns error: 

I just observed similar symptoms.

Check if there is a add/delete/balance/replace/resize running on the
file system.

In my case, there was a paused balance that I wasn't aware of (since
weeks? Months? …?).

Cheers,

Lukas

Bug#883731: audacious: Debian packaging has incorrect license

[Nicholas D Steeves]

Hi Francesco, John, and everybody else reading this,

On Fri, Dec 08, 2017 at 11:10:40AM +0100, Francesco Poli wrote:
> On Thu, 7 Dec 2017 22:39:41 -0500 Nicholas D Steeves wrote:
[...]
> Failing to retain the license text in the package distribution is in
> fact lack of compliance with the 2-clause BSD license, I would say...
> 
> > and also how
> > this should be resolved.  The Debian packaging is GPL-2+, so it's
> > possible to move to copyright-format/1.0 if that would simplify
> > things.
> 
> I personally think that the first thing to do is an accurate copyright
> and licensing status review of the audacious package, so that the
> debian/copyright file may be fixed to reflect the actual current state
> of affairs.
> The Audacious upstream developers may be willing to help, by clarifying
> any doubts upon request.
> This may be a perfect opportunity to switch to the [machine readable]
> format.
> 
> [machine readable]: 
> 

Thanks for the clarification.  I guess I've dropped the offending
patch in git and am currently working on a copyright-format/1.0
debian/copyright.

Will I also need to provide formal copies in debian/COPYING.emails or
would a README.copyright or similar pointing to the bug report
suffice?  In particular I'm concerned about lines like this from
d/copyright:

"po/uk.po" is © 2005 Mykola Lynnyk and is distributed under the terms of the
 GPL.

Where the new po/uk.po is GPL-incompatible 2-clause BSD:

# Ukrainian translation for Audacious
# Copyright (C) Audacious translators
# This file is distributed under the same license as the Audacious package.
#
# Translators:
# Dennis , 2014
# Eugene Paskevich , 2015-2016
# Kostyantyn Fedenko , 2011
# Oleg , 2012
# NaiLi (aka jamesjames) Rootaerc , 2012
# NaiLi (aka jamesjames) Rootaerc , 2012
# Oleg , 2012
# Rax Garfield , 2012
# Rax Garfield (http://biokillaz.com/), 2012
# Rax Garfield , 2012-2013
# Rustam Tsurik , 2013
# Rustam Tsurik , 2013
# Oleg , 2012
# Taras Shevchenko, 2017
# Yaroslav Yenkala , 2016
msgid ""
msgstr ""
"Project-Id-Version: Audacious\n"
"Report-Msgid-Bugs-To: http://redmine.audacious-media-player.org/\n;
"POT-Creation-Date: 2017-08-19 19:12+0200\n"
"PO-Revision-Date: 2017-08-06 05:54+\n"
"Last-Translator: Taras Shevchenko\n"

John, what happened here with Mykola Lynnyk's 2005 GPL copyright?

> > Also, please reply to point 2. OTTO "ancient plugins...under
> > different licenses.  I assume audacious-plugins will also need a
> > copyright review.
> 
> Probably.

I took a cursory glance and it seems to be in better shape than the
main audacious package but I'll take a look later.

> > Please CC John and I, Bug #883731, and
> > debian-legal as appropriate.
> 
> Done.
> 
> I hope my comments may help.
> 
> Bye and thanks to the Debian Multimedia Maintainers for the time they
> spend in maintaining a number of great Debian packages, and to the
> Audacious upstream developers for the time they spend in
> developing/maintaining that very nice audio player (that I personally
> use everyday!). Thank you!

Thank you Francesco, your comments do help.  I'm also a big fan of
Audacious and use it all the time. (thank you John!)  Oh, and if
everything goes according to plan we'll have a qt variant again
sometime in 2018 (one src:package will build the gtk variant, cleanup,
build the qt variant, and then package the two variants separately).

Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#874312: Acknowledgement (kdelibs4support: FTBFS on hppa - segmentation fault in desktoptojson)

[John David Anglin]

Problem is either in gcc or kcoreaddons:

(gdb) set args -i krdc_rdp_config.desktop -o 
/home/dave/debian/krdc/krdc-17.08.3/obj-hppa-linux-gnu/rdp/krdc_rdp_config.json
(gdb) r
Starting program: 
/home/dave/debian/kcoreaddons/kcoreaddons-5.37.0/obj-hppa-linux-gnu/src/desktoptojson/desktoptojson
 -i krdc_rdp_config.desktop -o 
/home/dave/debian/krdc/krdc-17.08.3/obj-hppa-linux-gnu/rdp/krdc_rdp_config.json
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/hppa-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x00022a9c in __sync_sub_and_fetch_4 ()
(gdb) bt
#0  0x00022a9c in __sync_sub_and_fetch_4 ()
#1  0x00018ce4 in std::__atomic_base::operator-- (this=)
at /usr/include/c++/7/bits/atomic_base.h:304
#2  QAtomicOps::deref (_q_value=...)
at /usr/include/hppa-linux-gnu/qt5/QtCore/qatomic_cxx11.h:271
#3  QBasicAtomicInteger::deref (this=)
at /usr/include/hppa-linux-gnu/qt5/QtCore/qbasicatomic.h:114
#4  QtPrivate::RefCount::deref (this=)
at /usr/include/hppa-linux-gnu/qt5/QtCore/qrefcount.h:73
#5  QVector::~QVector (this=0xf8d02804, 
__in_chrg=)
at /usr/include/hppa-linux-gnu/qt5/QtCore/qvector.h:75
#6  QtPrivate::QForeachContainer::~QForeachContainer (this=0xf8d02804, __in_chrg=)
at /usr/include/hppa-linux-gnu/qt5/QtCore/qglobal.h:934
#7  ServiceTypeDefinition::parseValue (this=this@entry=0x27130, key=..., 
value=...) at ./src/lib/plugin/desktopfileparser.cpp:403
#8  0x0001aed0 in DesktopFileParser::convertToJson (key=..., serviceTypes=..., 
value=..., json=..., kplugin=..., lineNr=)
at ./src/lib/plugin/desktopfileparser.cpp:506
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) disass $pc-16,$pc+16
Dump of assembler code from 0x22a8c to 0x22aac:
   0x00022a8c <__sync_sub_and_fetch_4+20>:  stw r3,-34(sp)
   0x00022a90 <__sync_sub_and_fetch_4+24>:  copy r26,r3
   0x00022a94 <__sync_sub_and_fetch_4+28>:  stw r4,-38(sp)
   0x00022a98 <__sync_sub_and_fetch_4+32>:  stw r19,-20(sp)
=> 0x00022a9c <__sync_sub_and_fetch_4+36>:  ldw 0(r3),rp
   0x00022aa0 <__sync_sub_and_fetch_4+40>:  sub rp,r5,r4
   0x00022aa4 <__sync_sub_and_fetch_4+44>:  copy r3,r26
   0x00022aa8 <__sync_sub_and_fetch_4+48>:  copy rp,r25
End of assembler dump.
(gdb) p/x $r3
$1 = 0x436f6d70

Dave
--
John David Anglin   dave.ang...@bell.net

Bug#884054: polyml: FTBFS on sh4: MemMgr: Assertion `t->tree[r] == 0' failed.

[John Paul Adrian Glaubitz]

On 12/11/2017 12:04 AM, James Clarke wrote:
> Yeah, I noticed this back when I was uploading to experimental a few months
> ago. I suspect it's an issue with qemu-user's atomics support on sh4, which
> have been notoriously unreliable in the past, and asked Adrian to see if he
> could reproduce this on real hardware, but that never ended up happening.
Sorry, I must have missed that. I will give that a go.

Is there a reduced test case?

Thanks,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#884054: polyml: FTBFS on sh4: MemMgr: Assertion `t->tree[r] == 0' failed.

[James Clarke]

> On 10 Dec 2017, at 22:09, Aaron M. Ucko  wrote:
> 
> Source: polyml
> Version: 5.7.1-1
> Severity: important
> Tags: upstream
> Justification: fails to build from source (but built successfully in the past)
> User: debian-sup...@lists.debian.org
> Usertags: sh4
> 
> Builds of polyml 5.7.x for sh4 (admittedly not a release architecture)
> have been failing:
> 
>  echo "use \"./ROOT.sml\";" | ../../poly -q -error-exit
>  poly: memmgr.cpp:957: void MemMgr::AddTreeRange(SpaceTree**, MemSpace*, 
> uintptr_t, uintptr_t): Assertion `t->tree[r] == 0' failed.
> 
> Could you please take a look?

Yeah, I noticed this back when I was uploading to experimental a few months
ago. I suspect it's an issue with qemu-user's atomics support on sh4, which
have been notoriously unreliable in the past, and asked Adrian to see if he
could reproduce this on real hardware, but that never ended up happening. Given
its reliable reproduction on the sh4 vs9X buildds and nowhere else I would be
surprised if it was in fact a bug in the package, but you never know...

James

Bug#884057: sweethome3d: crashes just after startup with nouveau graphics drivers

[Francesco Poli (wintermute)]

Package: sweethome3d
Version: 5.6+dfsg-1
Severity: important

Hello and thanks for maintaining this nice interior design tool!

I have been experiencing an issue for some time.
If I recall correctly, it started during last summer (on
Debian testing systems).
When starting sweethome3d on a box with an nVidia video card
and the nouveau graphics drivers, the program crashes almost
immediately (resizing the main window and/or its subwindows
suffices).
The redirected output on the terminal is attached (file sweethome.out).
The log file written to /tmp is also attached (file hs_err_pid1414.log).

However, sweethome3d seems to work correctly on other boxes with Intel
integrated graphics (and intel drivers). I cannot test it on other
different graphics stacks...

This bug could perhaps be similar to #873962, but I am not sure it's
actually the same (the problematic frame does not refer to the same
shared object).

What can be done in order to fix (or, at least, work around) this
bug?
Could you please investigate or reassign or forward upstream, as
appropriate?

Thanks for your time.
Bye!


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

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

Versions of packages sweethome3d depends on:
ii  default-jre [java7-runtime] 2:1.8-59
ii  icedtea-netx-common 1.6.2-3.1
ii  java-wrappers   0.2
ii  libbatik-java   1.9-3
ii  libfreehep-graphicsio-svg-java  2.1.1-5
ii  libitext-java   2.1.7-11
ii  libjava3d-java  1.5.2+dfsg-11
ii  libsunflow-java 0.07.2.svn396+dfsg-16
ii  openjdk-8-jre [java7-runtime]   8u151-b12-1

Versions of packages sweethome3d recommends:
pn  sweethome3d-furniture  

sweethome3d suggests no packages.

-- no debconf information
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x7f2397bed3b3, pid=1414, tid=0x7f2391a10700
#
# JRE version: OpenJDK Runtime Environment (8.0_151-b12) (build 
1.8.0_151-8u151-b12-1-b12)
# Java VM: OpenJDK 64-Bit Server VM (25.151-b12 mixed mode linux-amd64 
compressed oops)
# Problematic frame:
# C  [libdrm_nouveau.so.2+0x43b3]
#
# Failed to write core dump. Core dumps have been disabled. To enable core 
dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /tmp/hs_err_pid1414.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x7f2397bed3b3, pid=1414, tid=0x7f2391a10700
#
# JRE version: OpenJDK Runtime Environment (8.0_151-b12) (build 
1.8.0_151-8u151-b12-1-b12)
# Java VM: OpenJDK 64-Bit Server VM (25.151-b12 mixed mode linux-amd64 
compressed oops)
# Problematic frame:
# C  [libdrm_nouveau.so.2+0x43b3]
#
# Failed to write core dump. Core dumps have been disabled. To enable core 
dumping, try "ulimit -c unlimited" before starting Java again
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

---  T H R E A D  ---

Current thread (0x7f236c003800):  JavaThread "J3D-Renderer-1" 
[_thread_in_native, id=1448, stack(0x7f239191,0x7f2391a11000)]

siginfo: si_signo: 11 (SIGSEGV), si_code: 1 (SEGV_MAPERR), si_addr: 
0x0008

Registers:
RAX=0x0002, RBX=0x0002, RCX=0x7f23e443a8c0, 
RDX=0x7f23
RSP=0x7f2391a0eff0, RBP=0x7f238c049d98, RSI=0x, 
RDI=0x7f23e443a8c0
R8 =0x0116, R9 =0x028c, R10=0x7f23e4431020, 
R11=0x0246
R12=0x, R13=0x7f23e4430f70, R14=0x7f23, 
R15=0x7f238c049da8
RIP=0x7f2397bed3b3, EFLAGS=0x00010206, CSGSFS=0x002b0033, 
ERR=0x0004
  TRAPNO=0x000e

Top of Stack: (sp=0x7f2391a0eff0)
0x7f2391a0eff0:   0002 0004
0x7f2391a0f000:   0003 7f2397bed949
0x7f2391a0f010:    7f23e443a8c0
0x7f2391a0f020:   7f238c049d98 
0x7f2391a0f030:    7f238c049d80
0x7f2391a0f040:   7f238c049da8 7f2397bedadd
0x7f2391a0f050:   0276 0001
0x7f2391a0f060:   7f23e44310d0 7f23700ea090
0x7f2391a0f070:   

Bug#691763: kodi: Wish: Please support some low res (SDTV) skin

[Philippe Coval]

>  default skin in Kodi 17 seems to work better on low-res devices.

It's a bit better but still not acceptable IMHO,
anyway I think this bug can be forwarded upstream,
and eventually closed debian's side.

-- 
http://rzr.online.fr/# gpg:0x467094BC mailto:r...@users.sf.net

   .





signature.asc
Description: OpenPGP digital signature

Bug#845756: keepass2 crashes when super key is pressed

[Dario Andres Susman]

Package: keepass2
Version: 2.35+dfsg-2
Followup-For: Bug #845756

Keepass crashes when pressing the meta/windows key.
I've just updated the distro to latest.

I'm pasting here the output from stdout:

dsusman@fgx-laptop:~$ keepass2 
Stacktrace:

  at  <0x>
  at (wrapper managed-to-native) 
System.Windows.Forms.X11Keyboard.Xutf8LookupString 
(intptr,System.Windows.Forms.XEvent&,byte[],int,intptr&,System.Windows.Forms.XLookupStatus&)
 <0x000a4>
  at System.Windows.Forms.X11Keyboard.LookupString 
(System.Windows.Forms.XEvent&,int,System.Windows.Forms.XKeySym&,System.Windows.Forms.XLookupStatus&)
 <0x000c3>
  at System.Windows.Forms.X11Keyboard.EventToVkey (System.Windows.Forms.XEvent) 
<0x0003f>
  at System.Windows.Forms.X11Keyboard.ToUnicode (int,int,string&) <0x0035f>
  at System.Windows.Forms.X11Keyboard.TranslateMessage 
(System.Windows.Forms.MSG&) <0x00127>
  at System.Windows.Forms.XplatUIX11.TranslateMessage 
(System.Windows.Forms.MSG&) <0x00027>
  at System.Windows.Forms.XplatUI.TranslateMessage (System.Windows.Forms.MSG&) 
<0x00024>
  at System.Windows.Forms.Application.RunLoop 
(bool,System.Windows.Forms.ApplicationContext) <0x00da7>
  at System.Windows.Forms.Application.Run 
(System.Windows.Forms.ApplicationContext) <0x0005b>
  at System.Windows.Forms.Application.Run (System.Windows.Forms.Form) <0x00037>
  at KeePass.Program.Main (string[]) <0x00e0b>
  at (wrapper runtime-invoke) .runtime_invoke_void_object 
(object,intptr,intptr,intptr) <0x000d1>

Native stacktrace:

/usr/bin/cli(+0xc8d94) [0x55a1ddfcdd94]
/usr/bin/cli(+0x12204e) [0x55a1de02704e]
/usr/bin/cli(+0x3e063) [0x55a1ddf43063]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0) [0x7f77e18440c0]
/lib/x86_64-linux-gnu/libc.so.6(strlen+0x26) [0x7f77e12fd646]
/usr/lib/x86_64-linux-gnu/libX11.so.6(_XimLocalUtf8LookupString+0xde) 
[0x7f77dd3f9d7e]
[0x419da475]

Debug info from gdb:

[New LWP 14764]
[New LWP 14765]
[New LWP 14772]
[New LWP 14773]
[New LWP 14774]
[New LWP 14775]
[New LWP 14777]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f77e1843b3a in __waitpid (pid=14788, stat_loc=0x7f77e23720fc, options=0) 
at ../sysdeps/unix/sysv/linux/waitpid.c:29
29  ../sysdeps/unix/sysv/linux/waitpid.c: No such file or directory.
  Id   Target Id Frame 
* 1Thread 0x7f77e2345740 (LWP 14763) "Main" 0x7f77e1843b3a in __waitpid 
(pid=14788, stat_loc=0x7f77e23720fc, options=0) at 
../sysdeps/unix/sysv/linux/waitpid.c:29
  2Thread 0x7f77e07ff700 (LWP 14764) "SGen worker" 
pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  3Thread 0x7f77e0f12700 (LWP 14765) "Finalizer" 0x7f77e1842536 in 
futex_abstimed_wait_cancelable (private=0, abstime=0x0, expected=0, 
futex_word=0x55a1de4b1ee0) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
  4Thread 0x7f77cfc66700 (LWP 14772) "Main" 0x7f77e135871d in read () 
at ../sysdeps/unix/syscall-template.S:84
  5Thread 0x7f77cfa65700 (LWP 14773) "Main" 
pthread_cond_timedwait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
  6Thread 0x7f77cfa24700 (LWP 14774) "Threadpool work" 
pthread_cond_timedwait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
  7Thread 0x7f77cf823700 (LWP 14775) "Threadpool work" 
pthread_cond_timedwait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
  8Thread 0x7f77cedfe700 (LWP 14777) "Threadpool work" 
pthread_cond_timedwait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225

Thread 8 (Thread 0x7f77cedfe700 (LWP 14777)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x55a1de0ce756 in ?? ()
#2  0x55a1de0c8461 in ?? ()
#3  0x55a1de1879ca in ?? ()
#4  0x7f77e183a494 in start_thread (arg=0x7f77cedfe700) at 
pthread_create.c:333
#5  0x7f77e1365aff in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 7 (Thread 0x7f77cf823700 (LWP 14775)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x55a1de0ce756 in ?? ()
#2  0x55a1de0c8461 in ?? ()
#3  0x55a1de1879ca in ?? ()
#4  0x7f77e183a494 in start_thread (arg=0x7f77cf823700) at 
pthread_create.c:333
#5  0x7f77e1365aff in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 6 (Thread 0x7f77cfa24700 (LWP 14774)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x55a1de0ce756 in ?? ()
#2  0x55a1de0c8461 in ?? ()
#3  0x55a1de1879ca in ?? ()
#4  0x7f77e183a494 in start_thread (arg=0x7f77cfa24700) at 
pthread_create.c:333
#5  0x7f77e1365aff in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 5 

Bug#876413: [feedparser] new upstream version available

[Carl Suster]

Thanks! I updated the changelog in git as well now.

On 11/12/17 08:59, Antoine Beaupré wrote:

I did a source-only upload with only the slightest changes (added the
Closes entry and fixed the distribution field in the changelog), but I
can't push those because I am not in the DPTM team.

Bug#851506: cpanminus embeds other modules in fatpacked library

[gregor herrmann]

On Sun, 10 Dec 2017 13:04:49 +, Damyan Ivanov wrote:

> > Please review/improve/revert before I upload.
> The result is pretty impressive, eliminating both fatpacked bundled 
> libraries from the cpanm script as installed by the binary package.
> I just added a short note to d/watch trying to explain why the 
> downloading is dome from github instead of cpan.

Thanks for the review and this update.

Now uploaded.


Cheers,
greogr

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


signature.asc
Description: Digital Signature

Bug#884056: RM: ktp-text-ui [armel hurd-i386 kfreebsd-amd64 kfreebsd-i386 mips mips64el ppc64el s390x] -- ROM; requires QtWebEngine

[Pino Toscano]

Package: ftp.debian.org
Severity: normal

Hi,

the new version of src:ktp-text-ui requires QtWebEngine, which so far
is ported to a limited number of architectures.  Hence, please remove
the binaries of ktp-text-ui on the other architectures.

Thanks,
-- 
Pino

Bug#884054: polyml: FTBFS on sh4: MemMgr: Assertion `t->tree[r] == 0' failed.

[Aaron M. Ucko]

Source: polyml
Version: 5.7.1-1
Severity: important
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
User: debian-sup...@lists.debian.org
Usertags: sh4

Builds of polyml 5.7.x for sh4 (admittedly not a release architecture)
have been failing:

  echo "use \"./ROOT.sml\";" | ../../poly -q -error-exit
  poly: memmgr.cpp:957: void MemMgr::AddTreeRange(SpaceTree**, MemSpace*, 
uintptr_t, uintptr_t): Assertion `t->tree[r] == 0' failed.

Could you please take a look?

Thanks!

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

Bug#884055: gpsd: gpsmon u-blox time reporting incorrect

[Chris Lawrence]

Package: gpsd
Version: 3.17-3
Severity: normal
Tags: patch upstream

When using the gpsmon tool with a u-blox GPS module, the time is
reported incorrectly in the NAV_SOL box. This is because of a series of
arithmetic errors in the code (times are reported in milliseconds, but
the math seems to assume they are in centiseconds).

This patch corrects the error and produces accurate times. Tested with
both a NEO-M8N connected over USB and a NEO-6N module on a Raspberry Pi.

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

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

Versions of packages gpsd depends on:
ii  adduser3.116
ii  libbluetooth3  5.47-1
ii  libc6  2.25-3
ii  libdbus-1-31.12.2-1
ii  libgps23   3.17-3
ii  libusb-1.0-0   2:1.0.21-2
ii  lsb-base   9.20170808
ii  netbase5.4
ii  systemd-sysv   235-3

Versions of packages gpsd recommends:
ii  python  2.7.14-3
ii  udev235-3

Versions of packages gpsd suggests:
ii  dbus  1.12.2-1
ii  gpsd-clients  3.17-3

-- Configuration Files:
/etc/default/gpsd changed:
START_DAEMON="true"
USBAUTO="true"
DEVICES=""
GPSD_OPTIONS="-D 1"


-- debconf information:
  gpsd/autodetection: false
  gpsd/socket: /var/run/gpsd.sock
  gpsd/daemon_options:
* gpsd/start_daemon: false
  gpsd/device:
  gpsd/brokenconfig:
diff --git a/monitor_ubx.c b/monitor_ubx.c
index 2ba82de8..35026349 100644
--- a/monitor_ubx.c
+++ b/monitor_ubx.c
@@ -173,16 +173,16 @@ static void display_nav_sol(unsigned char *buf, size_t 
data_len)
 
 (void)wmove(navsolwin, 7, 7);
 {
-   unsigned int day = tow / 864;
-   unsigned int tod = tow % 864;
-   unsigned int h = tod / 36;
-   unsigned int m = tod % 36;
-   unsigned int s = m % 6000;
+   unsigned int day = tow / 8640;
+   unsigned int tod = tow % 8640;
+   unsigned int h = tod / 360;
+   unsigned int m = tod % 360;
+   unsigned int s = m % 6;
 
-   m = (m - s) / 6000;
+   m = (m - s) / 6;
 
(void)wattrset(navsolwin, A_UNDERLINE);
-   (void)wprintw(navsolwin, "%u %02u:%02u:%05.2f", day, h, m, (double)s / 
100);
+   (void)wprintw(navsolwin, "%u %02u:%02u:%05.2f", day, h, m, (double)s / 
1000);
(void)wattrset(navsolwin, A_NORMAL);
 }
 (void)wmove(navsolwin, 8, 11);

Bug#876413: [feedparser] new upstream version available

[Antoine Beaupré]

Control: tags -1 +pending

I did a source-only upload with only the slightest changes (added the
Closes entry and fixed the distribution field in the changelog), but I
can't push those because I am not in the DPTM team.

Thanks!

A.
-- 
What this country needs is more unemployed politicians.
- Angela Davis

Bug#876413: [feedparser] new upstream version available

[Antoine Beaupré]

On 2017-12-11 08:49:20, Carl Suster wrote:
> Thanks - I actually already am adding myself to Uploaders in the 
> existing package on mentors. .
>
>> That looks good to me, let's see if the maintainer picks it up -
>> otherwise I'll take care of doing a NMU.
>
> The maintainer is DPMT of which I'm a member so I don't think this would 
> have been an NMU anyway though.

Alright, I'll build here to see if everything is already and upload this
shortly.

A.

-- 
We must shift America from a needs- to a desires-culture. People must
be trained to desire, to want new things, even before the old have
been entirely consumed. Man's desires must overshadow his needs.
 - Paul Mazur, Lehman Brothers

Bug#876413: [feedparser] new upstream version available

[Carl Suster]

Thanks - I actually already am adding myself to Uploaders in the 
existing package on mentors. .



That looks good to me, let's see if the maintainer picks it up -
otherwise I'll take care of doing a NMU.


The maintainer is DPMT of which I'm a member so I don't think this would 
have been an NMU anyway though.

Bug#876413: [feedparser] new upstream version available

[Étienne Millon]

Sure, go ahead!
Carl, if you're interested, feel free to add yourself to Uploaders and make
this not a NMU, as I won't have time in the near future to take care of
this package.
Thanks a lot for taking care of this package.

On Sun, Dec 10, 2017 at 8:21 PM, Antoine Beaupré  wrote:

> Control: tags -1 +patch
>
> On 2017-12-02 13:08:42, Carl Suster wrote:
> > Hi Antoine,
> >
> > I've updated the packaging of feedparser and pushed 5.2.1-1 to mentors:
> >
> > https://mentors.debian.net/debian/pool/main/f/feedparser/
> feedparser_5.2.1-1.dsc
> >
> > https://mentors.debian.net/package/feedparser
> >
> >  > Unfortunately, it seems the newer version from the `devel` branch may
> >  > be needed for 3.5 support. As it stands now, 5.2.1 works fine in
> >  > Python 3.5 here.
> >
> > 5.2.1 is at least a start, and maybe afterwards we can look at improving
> > the python3 support. However it does seem that the project has been
> > semi-abandoned upstream.
> >
> > If you're still interested in feedparser, could you perhaps review my
> > package?
> >
> > A couple of the tests were failing but it wasn't obvious to me why they
> > should ever have passed in the first place. For now I disabled those,
> > and then later in a subsequent version I intend to investigate in more
> > detail while exploring the python3 situation.
>
> Hi!
>
> That looks good to me, let's see if the maintainer picks it up -
> otherwise I'll take care of doing a NMU.
>
> Thanks!
>
> A.
>
> --
> We have no friends but the mountains.
> - Kurdish saying
>
>

Bug#884053: python-lib389: missing build dependencies

[Adrian Bunk]

Source: python-lib389
Version: 1.0.2-3
Severity: serious
Tags: buster sid

Some recent change in unstable (new python-setuptools?)
makes python-lib389 FTBFS:

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

...
==
ERROR: lib389.tests.test_module_proxy (unittest.loader.ModuleImportFailure)
--
ImportError: Failed to import test module: lib389.tests.test_module_proxy
Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/loader.py", line 254, in _find_tests
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/unittest/loader.py", line 232, in 
_get_module_from_name
__import__(name)
  File "/build/1st/python-lib389-1.0.2/lib389/__init__.py", line 67, in 
from lib389._entry import Entry
  File "/build/1st/python-lib389-1.0.2/lib389/_entry.py", line 10, in 
import six
ImportError: No module named six


--
Ran 1 test in 0.000s

FAILED (errors=1)
Test failed: 
error: Test failed: 
debian/rules:9: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1


Reproduced locally, and seems to require build dependencies on
python-six, python-pyasn1 and python-pyasn1-modules.

Bug#709879: espeak: Alsa lib underflow and clicking sounds.

[Samuel Thibault]

Control: reassign -1 linux

Hello,

Really sorry this apparently went unnoticed for so long.

anton, on dim. 26 mai 2013 19:19:32 +1000, wrote:
> Espeak does not start normally and throws out the error message:
> ALSA lib pcm.c:7339:(snd_pcm_recover) underrun occurred
> Hundreds of times. It does it when the computer has been on for a while. 
> A reset is needed before it returns to normal for a few hours then the same 
> problem shows up again.

Is it still an issue today?

Since espeak is not running all that time along, this really rather
looks like a kernel bug, thus reassigning.

Samuel

Bug#884052: python-oslo.log FTBFS: AssertionError: Expected '_log' to be called once. Called 0 times.

[Adrian Bunk]

Source: python-oslo.log
Version: 3.30.0-2
Severity: serious

Some recent change in unstable makes python-oslo.log FTBFS:

https://tests.reproducible-builds.org/debian/history/python-oslo.log.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-oslo.log.html

...
==
FAIL: 
oslo_log.tests.unit.test_log.KeywordArgumentAdapterTestCase.test_pass_args_to_log
oslo_log.tests.unit.test_log.KeywordArgumentAdapterTestCase.test_pass_args_to_log
--
_StringException: Traceback (most recent call last):
  File "/build/1st/python-oslo.log-3.30.0/oslo_log/tests/unit/test_log.py", 
line 1684, in test_pass_args_to_log
exc_info=exc_message
  File "/usr/lib/python3/dist-packages/mock/mock.py", line 947, in 
assert_called_once_with
raise AssertionError(msg)
AssertionError: Expected '_log' to be called once. Called 0 times.


==
FAIL: 
oslo_log.tests.unit.test_log.KeywordArgumentAdapterTestCase.test_pass_args_via_debug
oslo_log.tests.unit.test_log.KeywordArgumentAdapterTestCase.test_pass_args_via_debug
--
_StringException: Traceback (most recent call last):
  File "/build/1st/python-oslo.log-3.30.0/oslo_log/tests/unit/test_log.py", 
line 1710, in test_pass_args_via_debug
exc_info=exc_message
  File "/usr/lib/python3/dist-packages/mock/mock.py", line 947, in 
assert_called_once_with
raise AssertionError(msg)
AssertionError: Expected '_log' to be called once. Called 0 times.


--
Ran 168 tests in 14.053s

FAILED (failures=2, skipped=1)
debian/rules:28: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#882699: ngspice: Remove build dependency on elyxer to allow for the elyxer removal from Debian

[Andreas Tille]

Hi Sven,

thanks a lot for your work on this.  Its perfectly fine for me (except
that I would have moved the package from SVN to Git.  I *personally* do
not really work on the package - just did the sponsoring if Gudjon
provide some new package.

I can do the move from SVN to Git once the package is accepted to
not interfere with the current NMU.

Kind regards

   Andreas.

On Sun, Dec 10, 2017 at 05:58:40PM +0100, Sven Hoexter wrote:
> Hi Gudjon, hi Andreas,
> I've uploaded the attached NMU to delayed/10 since I received no note from
> you since opening the bug. So in case you object there's still some time
> to act.
> 
> Cheers,
> Sven


> diff -Nru ngspice-26/debian/changelog ngspice-26/debian/changelog
> --- ngspice-26/debian/changelog   2016-04-25 20:51:09.0 +0200
> +++ ngspice-26/debian/changelog   2017-12-10 14:53:20.0 +0100
> @@ -1,3 +1,14 @@
> +ngspice (26-1.2) unstable; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * Remove elyxer from Build-Depends-Indep to allow for the removal of elyxer
> +from Debian. The build in HTML export support in LyX improved during the
> +last years and is equally usable or even better regarding new LyX file
> +formats.
> +  * Change package priority from extra to optional.
> +
> + -- Sven Hoexter   Sun, 10 Dec 2017 14:53:20 +0100
> +
>  ngspice (26-1.1) unstable; urgency=medium
>  
>* Non-maintainer upload.
> diff -Nru ngspice-26/debian/control ngspice-26/debian/control
> --- ngspice-26/debian/control 2014-07-05 23:49:29.0 +0200
> +++ ngspice-26/debian/control 2017-12-10 14:52:17.0 +0100
> @@ -1,13 +1,13 @@
>  Source: ngspice
>  Section: non-free/electronics
> -Priority: extra
> +Priority: optional
>  Maintainer: Debian Science Team 
> 
>  Uploaders: Gudjon I. Gudjonsson ,
>   Andreas Tille 
>  Build-Depends: debhelper (>= 8), automake, libtool, libxaw7-dev, flex,
>   bison, gfortran, libedit-dev, libncurses5-dev,
>   texinfo, tcl8.6-dev, tcl8.6, tk8.6-dev, tk8.6, blt-dev
> -Build-Depends-Indep: lyx, elyxer, texlive, texlive-latex-extra, 
> texlive-lang-greek,
> +Build-Depends-Indep: lyx, texlive, texlive-latex-extra, texlive-lang-greek,
>   texlive-generic-recommended, imagemagick
>  Standards-Version: 3.9.5
>  Homepage: http://ngspice.sourceforge.net

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> Format: 3.0 (quilt)
> Source: ngspice
> Binary: ngspice, tclspice, ngspice-doc
> Architecture: any all
> Version: 26-1.2
> Maintainer: Debian Science Team 
> 
> Uploaders: Gudjon I. Gudjonsson , Andreas Tille 
> 
> Homepage: http://ngspice.sourceforge.net
> Standards-Version: 3.9.5
> Vcs-Browser: 
> http://anonscm.debian.org/viewvc/debian-science/packages/ng-spice-rework/trunk/
> Vcs-Svn: 
> svn://anonscm.debian.org/debian-science/packages/ng-spice-rework/trunk/
> Build-Depends: debhelper (>= 8), automake, libtool, libxaw7-dev, flex, bison, 
> gfortran, libedit-dev, libncurses5-dev, texinfo, tcl8.6-dev, tcl8.6, 
> tk8.6-dev, tk8.6, blt-dev
> Build-Depends-Indep: lyx, texlive, texlive-latex-extra, texlive-lang-greek, 
> texlive-generic-recommended, imagemagick
> Package-List:
>  ngspice deb non-free/electronics optional arch=any
>  ngspice-doc deb non-free/doc optional arch=all
>  tclspice deb non-free/electronics optional arch=any
> Checksums-Sha1:
>  be5c90e0552bbe4f0091543742d5863dd50319e0 847177 ngspice_26.orig-manual.tar.gz
>  270da390743f7cfd7dae5f915a2c30dee65d4262 6732799 ngspice_26.orig.tar.gz
>  3fdb9c2de03fbd3ca1634bf08336e439afb393dd 12868 ngspice_26-1.2.debian.tar.xz
> Checksums-Sha256:
>  952d8118289fdace380505b589e0b45172259bd8f4385aa2149bdb1cc41d2ad0 847177 
> ngspice_26.orig-manual.tar.gz
>  d6bb6cba146810c08a384a56016484ad47f7246a2dd1a932344b4161c8b86284 6732799 
> ngspice_26.orig.tar.gz
>  fdd6a697991579ca0da793f2eb98c92345ea858172de94ee7aaa34840cc6efd2 12868 
> ngspice_26-1.2.debian.tar.xz
> Files:
>  59bdfaba4f550507909060ad3f308e2f 847177 ngspice_26.orig-manual.tar.gz
>  4f1e945cb94a3f42176cf84ba8f2d4f4 6732799 ngspice_26.orig.tar.gz
>  be1744c58fe304330fc02b26f3643f03 12868 ngspice_26-1.2.debian.tar.xz
> Autobuild: yes
> 
> -BEGIN PGP SIGNATURE-
> 
> iQIzBAEBCAAdFiEEfAcX+forK514ixQbptwk2dokk9EFAlotRUEACgkQptwk2dok
> k9FlThAAliZNuE/LLScNPn1kCQsu+/tZbzjFdsB1mWmWbcYYd8pL8sCfgxD5nOhQ
> D5oqEvBg/LkWuRyTTD98gJ3CeXtYE3V1FBXA4FYwGwQzbUKfphaokXrUmtbiFgNo
> 2336nODfxlBlI7+KhYOXdKPZPawt0U7D+aRjAOpD6zxpETuCP2A/Dy8imWvHyc06
> b/c++C4/LRdH2Iq5LdXVcY50UGYbs5NcUfWiVJ+jlYqWawIu775BRJ+eQgN41huN
> aOPNDKe466HoebYl/C8hhqCAWsA98RM6L5txYiHe93X6v4Umpa2zHx2x8jAhB/e4
> eLjlXb15kR6cLRPhQsKMUW9ysO7Rncn0uZeVVWT3i5vDCXKhB7lZ7/KcAn1Y8IR8
> YvWqi7jmAIhzAo7+0oHHMZ6EzTzuHYmUzURgbbqfI7XqLB+ele4Bs37nDWByC4b5
> eSri4AGBY9x4SHmJyifsQk8iY/jpaWnmw6xZ8tibLjnlhc1YxRMgy9WnTAlFc68m
> 

Bug#884051: cross-gcc-dev needs an update for the gcc-8 cilkrts removal

[Helmut Grohne]

Source: cross-gcc
Version: 163
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

cilkrts got removed from gcc-8, so cross-ma-install-location.diff needs
to stop patching it.

Helmut
--- 0004-added-multi-arch-specific-install-location-patch.patch
+++ 0004-added-multi-arch-specific-install-location-patch.patch
@@ -16,7 +16,7 @@
 index 000..97117d6
 --- /dev/null
 +++ b/debian/patches/cross-ma-install-location.diff
-@@ -0,0 +1,379 @@
+@@ -0,0 +1,357 @@
 +Index: b/src/libada/configure.ac
 +===
 +--- a/src/libada/configure.ac
@@ -340,28 +340,6 @@
 + toolexeclibdir='$(toolexecdir)/$(gcc_version)$(MULTISUBDIR)'
 + ;;
 +   no)
-+-if test -n "$with_cross_host" &&
-+-   test x"$with_cross_host" != x"no"; then
-+-  # Install a library built with a cross compiler in tooldir, not libdir.
-+-  toolexecdir='$(exec_prefix)/$(target_alias)'
-+-  toolexeclibdir='$(toolexecdir)/lib'
-+-else
-+-  toolexecdir='$(libdir)/gcc-lib/$(target_alias)'
-+-  toolexeclibdir='$(libdir)'
-+-fi
-++toolexecdir='$(libdir)/gcc-lib/$(target_alias)'
-++toolexeclibdir='$(libdir)'
-+ multi_os_directory=`$CC -print-multi-os-directory`
-+ case $multi_os_directory in
-+   .) ;; # Avoid trailing /.
-+Index: b/src/libcilkrts/configure.ac
-+===
-+--- a/src/libcilkrts/configure.ac
- b/src/libcilkrts/configure.ac
-+@@ -103,15 +103,8 @@
-+ toolexeclibdir='$(toolexecdir)/$(gcc_version)$(MULTISUBDIR)'
-+ ;;
-+   no)
 +-if test -n "$with_cross_host" &&
 +-   test x"$with_cross_host" != x"no"; then
 +-  # Install a library built with a cross compiler in tooldir, not libdir.

Bug#884019: [Pkg-e-devel] Bug#884019: terminology: FTBFS if $HOME is not writable

[Ross Vandegrift]

Control: tags -1 pending

On Sun, Dec 10, 2017 at 03:48:30PM +0100, Andreas Beckmann wrote:
> same problem as in e17:

Thanks, I've applied the fix from e17.

Ross

Bug#825383: /usr/share/hplip/doctor.py: hp-doctor will not accept sudo password and there is no root account

[Reinhard]

Package: hplip
Version: 3.16.11+repack0-3
Followup-For: Bug #825383

Dear Maintainer,

I can confirm that this bug is still existent in Debian 9.

I understand that there will be not so many users affected by this bug since
only a minority will configure their Debian system with sudo instead of a root
account. But I think Debian stable should be able to handle a configuration
with sudo.

I am no programmer, but if I can contribute somehow in solving this problem,
let me know.

Greetings
Reinhard



-- Package-specific info:

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

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

Versions of packages hplip depends on:
ii  adduser3.115
ii  coreutils  8.26-3
ii  cups   2.2.1-8
ii  hplip-data 3.16.11+repack0-3
ii  libc6  2.24-11+deb9u1
ii  libcups2   2.2.1-8
ii  libdbus-1-31.10.24-0+deb9u1
ii  libhpmud0  3.16.11+repack0-3
ii  libsane1.0.25-4.1
ii  libsane-hpaio  3.16.11+repack0-3
ii  libsnmp30  5.7.3+dfsg-1.7
ii  libusb-1.0-0   2:1.0.21-1
ii  lsb-base   9.20161125
ii  policykit-10.105-18
ii  printer-driver-hpcups  3.16.11+repack0-3
ii  python33.5.3-1
ii  python3-dbus   1.2.4-1+b1
ii  python3-gi 3.22.0-2
ii  python3-pexpect4.2.1-1
ii  python3-pil4.0.0-4
ii  python3-reportlab  3.3.0-2
ii  wget   1.18-5+deb9u1

Versions of packages hplip recommends:
ii  avahi-daemon  0.6.32-2
ii  printer-driver-postscript-hp  3.16.11+repack0-3
ii  sane-utils1.0.25-4.1

Versions of packages hplip suggests:
pn  hplip-doc  
ii  hplip-gui  3.16.11+repack0-3
ii  python3-notify20.3-3
pn  system-config-printer  

-- no debconf information

Bug#884006: copyright-format: Documenting copyrights not in source package but in binary package

[Yao Wei]

On Sun, Dec 10, 2017 at 10:46:12AM -0700, Sean Whitton wrote:
> > One of the files inside Package A is generated during build time.
> > However, the generation of the file requires Package B which has
> > different copyright, and the generated file in Package A is basically
> > a format conversion of the file in Package B, and the copyright needs
> > to be retained per license of Package B.  It could be copyright
> > violation of Package B if copyright status and requirements is not
> > fulfilled in Package A and we redistribute Package A.
> >
> > I would suggest a tag "Files-Binary" in copyright-format to fulfill
> > this situation.
> 
> What would the definition of this field be?  It is not clear from your
> example.

Files-Binary would be package name and file path to the files which its
copyright is not in source package but in binary package.  For example:

  Files-Binary: package-a-data, usr/share/package-a-data/file-in-question
  Copyright:2038 John Doe
  License:  Expat

---

Another solution to this problem is mark certain file which is generated
using what source package inside the header, and during build process
the copyright information requires to be attached in the binary package.
This should introduce another tag "Depends", like:

  Files-Binary: package-a-data, usr/share/package-a-data/file-in-question
  Depends:  package-b

If the maintainer knows what specific file in package-b it requires,
they can specify it like:

  Files-Binary: package-a-data, usr/share/package-a-data/file-in-question
  Depends:  package-b, data/orig-file

And if the specified file in package-b has the same problem of
package-a, as it only exists in binary package, it can be like this:

  Files-Binary:   package-a-data, usr/share/package-a-data/file-in-question
  Depends-Binary: package-b-data, usr/share/package-b-data/orig-file

---

For real-world use case, I am packaging glyphslib, which has above
problem for a stripped file which needs to be generated from source:

  https://anonscm.debian.org/cgit/pkg-fonts/glyphslib.git/tree/debian/copyright

Please comment or propose another idea if the use case of them is not
clear.

Yao Wei


signature.asc
Description: PGP signature

Bug#881102: RM: libnet-ping-external-perl -- RoQA; unmaintained upstream, contains security issue for several years unadressed

[Brian May]

On Tue, Nov 07, 2017 at 09:14:17PM +0100, Salvatore Bonaccorso wrote:
> There are no packages depending on it in Debian, so it looks the
> safest course of action is to remove it from unstable (possibly as
> well from other suites later on via point release) and not having it
> included in buster.

This package should be removed from wheezy too. Please let me know if I
need a seperate bug for wheezy, for now reusing the same bug for sid and
testing.

This package was removed from Jessie and Stretch in the latest point
release.

For more additional discussion see:

http://www.openwall.com/lists/oss-security/2017
https://bugs.debian.org/881097
https://lists.debian.org/debian-lts/2017/12/msg9.html

I note that initially there was some disgreement as to if this package
should be removed or not from Wheezy. However I believe the consensus
now is that it should get removed. Especially as it has been removed
from Jessie and Stretch.
-- 
Brian May 

Bug#883156: version 1.1

[Paul Gevers]

Hi all,

On 10-12-17 21:16, Samuel Thibault wrote:
> I can quickly do the last step if all the previous steps are done).

So can I.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#884050: qtconnectivity-opensource-src FTCBFS: does not pass cross flags to qmake

[Helmut Grohne]

Source: qtconnectivity-opensource-src
Version: 5.9.2-2
Severity: minor
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

qtconnectivity-opensource-src fails to cross build from source, because
it does not pass cross flags to qmake. This is best done by deferring to
dh_auto_configure these days. After doing so, it still fails to cross
build, because it fails finding libbluetooth. I don't have a solution
here, but let me try to describe the problem.

In src/bluetooth/configure.json it describes how to check for BlueZ with
pkg-config. It seems that qmake implements this by running another qmake
on a small test project to determine success or failure. Unfortunately,
this sub-qmake lacks cross flags again, so it uses the build
architecture pkg-config and g++ thus failing to find the bluetooth
library.

Potential options for fixing this:
 * Maybe we need to set PKG_CONFIG_EXECUTABLE?
 * Maybe we need to set a suitable QMAKE_QMAKE?

In any case, please close this bug when switching to dh_auto_configure
and making the BlueZ finding issue visible.

Helmut
diff --minimal -Nru qtconnectivity-opensource-src-5.9.2/debian/changelog 
qtconnectivity-opensource-src-5.9.2/debian/changelog
--- qtconnectivity-opensource-src-5.9.2/debian/changelog2017-10-27 
10:33:07.0 +0200
+++ qtconnectivity-opensource-src-5.9.2/debian/changelog2017-12-10 
13:32:07.0 +0100
@@ -1,3 +1,10 @@
+qtconnectivity-opensource-src (5.9.2-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Address FTCBFS: Let dh_auto_configure pass cross flags to qmake.
+
+ -- Helmut Grohne   Sun, 10 Dec 2017 13:32:07 +0100
+
 qtconnectivity-opensource-src (5.9.2-2) unstable; urgency=medium
 
   * Upload to unstable.
diff --minimal -Nru qtconnectivity-opensource-src-5.9.2/debian/control 
qtconnectivity-opensource-src-5.9.2/debian/control
--- qtconnectivity-opensource-src-5.9.2/debian/control  2017-10-27 
10:33:07.0 +0200
+++ qtconnectivity-opensource-src-5.9.2/debian/control  2017-12-10 
13:32:02.0 +0100
@@ -8,7 +8,7 @@
Felix Geyer ,
Timo Jyrinki ,
Dmitry Shachnev 
-Build-Depends: debhelper (>= 10),
+Build-Depends: debhelper (>= 10.9.2~),
libbluetooth-dev [linux-any],
pkg-config,
pkg-kde-tools,
diff --minimal -Nru qtconnectivity-opensource-src-5.9.2/debian/rules 
qtconnectivity-opensource-src-5.9.2/debian/rules
--- qtconnectivity-opensource-src-5.9.2/debian/rules2017-10-27 
10:33:07.0 +0200
+++ qtconnectivity-opensource-src-5.9.2/debian/rules2017-12-10 
13:31:11.0 +0100
@@ -15,7 +15,7 @@
# Be sure to regenerate the DBus cpp files
cd src/bluetooth/bluez/ ; ./generate
# Now call qmake
-   qmake
+   dh_auto_configure
 
 override_dh_auto_build-indep:
dh_auto_build -Smakefile -- docs

Bug#883118: Crash in libupnp -- NULL-ptr dereference

[Uwe Kleine-König]

Control: tag -1 += upstream fixed-upstream

Hello,

On Sun, Dec 10, 2017 at 05:47:43PM +0100, Tobias Frost wrote:
> I'm reassigning this bug as I'm suspecting it in the recent release of 
> libupnp,
> after I had debugged it a bit.
> 
> The bug does not trigger in 1.6.22.
> 
> How to reproduce:
> 
> Install gmediarender and (as a DLNA/uPnP control point) gupnp-tools.
> 
> run gmediarender , eg. gmediarender --logfile=/dev/stdout and then the DLNA
> controlpoint, e.g  gupnp-av-cp
> 
> As soon as the the cp queries for the DLNA server, gmediarender crashes.

thanks, that reproduction recipe was very helpful.

> Debugging into it it segfaults in 
> upnp/src/genlib/net/http/httpreadwrite.c:1662
> deferencing a NULL pointer (extras being NULL); it is called from
> upnp/src/genlib/net/http/webserver.c:1316; the relvant paremter is
> "extra_headers", passed for the "E" command  (its NULL)

This is already fixed upstream, see
https://github.com/mrjimenez/pupnp/commit/70e3d626378e12ea50d76dfda50311c8bb4a2a78

> --- a/upnp/src/genlib/net/http/httpreadwrite.c
> +++ b/upnp/src/genlib/net/http/httpreadwrite.c
> @@ -1668,8 +1668,7 @@
> }
> extras++;
> }
> -   }
> -   if (c == 's') {
> +   } else if (c == 's') {
> /* C string */
> s = (char *)va_arg(argp, char *);
> assert(s);

I saw this inconsistency but didn't notice that this runs in an
assert(0). It seems nobody runs debug builds of libupnp :-\.

I'll prepare a patch for upstream.

Best regards
Uwe


signature.asc
Description: PGP signature

Bug#884049: '?' in Title not properly escaped

[Bernhard Schmidt]

Package: abcde
Version: 2.8.1-1
Severity: normal

Hi,

to test abcde I just tried to rip the first CD that lay around here, which
happens to be an audio play of the popular German youth series 'Die drei ???'.

It looks like abcde is improperly feeding the ??? to the shell, substituting
the name of all three-letter files in my home directory

Grabbing entire CD - tracks: 01 02 03 04 05 06 07 08 09 10 11 12
Retrieved 1 Musicbrainz match...done.
 Die drei bin git mnt tmp / Die drei bin git mnt tmp Spezial: und der 
Tornadojäger 
1: Eine rasante Flucht
2: Superhelden der besonderen Art
3: Die Lauscherin
4: Überraschende Enthüllungen
5: Auf Rachefeldzug
6: Intrigen überall
7: Entführt!
8: Schlussfolgerungen
9: Schein und Sein
10: Licht ins Dunkel
11: Ein Paar
12: Sonnenklar

Editing the CDDB data shows the title correctly

DTITLE=Die drei ??? / Die drei ??? Spezial: und der Tornadojäger

but then again the output directory is wrong.

Bernhard

Bug#876695: Fixed upstream

[Nicolas Guilbert]

Hi Leo,

that sounds great - are you planning a release soon?

Cheers


 Nicolas


On 12/10/2017 09:01 PM, Leonardo Zide wrote:
I believe part of this change 
https://github.com/leozide/leocad/commit/33f33af0aaca49bd4b02a1596e2c677dbd1c4063 
will fix the problem. Right now upstream compiles for iOS, which also 
only has GL ES.

Bug#879764: fixed in golang-1.9 1.9.2-4

[Michael Hudson-Doyle]

On 11 December 2017 at 09:07, Michael Hudson-Doyle <
michael.hud...@canonical.com> wrote:

>
>
> On 9 December 2017 at 00:30, James Cowgill  wrote:
>
>> Hi,
>>
>> On 08/12/17 01:34, Michael Hudson-Doyle wrote:
>> > Source: golang-1.9
>> > Source-Version: 1.9.2-4
>> >
>> > We believe that the bug you reported is fixed in the latest version of
>> > golang-1.9, which is due to be installed in the Debian FTP archive.
>> [...]
>> >* Enable building on mips, mipsel and mips64. (Closes: 879764)
>>
>> Thanks for this. The mips and mipsel builds failed due to #867358,
>> however the fix for this is in the kernel due to be released in the next
>> stable point release tomorrow. After the mips buildds have had their
>> kernels updated, I'll give the package back and it should build.
>>
>
> Ah, good timing (I knew there was a reason I sat on these patches for
> months...)
>
>
>> After this is done, is there anything you want me to do (like rebuilds,
>> give-backs, patches, etc) to get mips* enabled in golang-defaults?
>>
>
> Well patches for golang-defaults could be nice I guess. It's pretty
> trivial though so so long as don't forget I can do it in 5 mins :-) We
> should probably wait for the kernel fix and the rebuilds of golang-1.9
> though.
>

Ah I see that the retries have already happened, so I've uploaded
golang-defaults 1.9~2 with these architectures enabled. Thanks for driving
this!!

Cheers,
mwh

Bug#834002: Pending fixes for bugs in the golang-defaults package

[pkg-golang-maintainers]

tag 834002 + pending
tag 841645 + pending
thanks

Some bugs in the golang-defaults package are closed in revision
975575ddf03d2bdcb6c6ff68bff8956fc0eaedd5 in branch 'master' by
Michael Hudson-Doyle

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-golang/golang-defaults.git/commit/?id=975575d

Commit message:

Add mips, mips64el and mipsel to golang-go Architectures. (Closes: #834002, 
#841645)

Bug#884047: bibledit: please make the build reproducible

[Chris Lamb]

Source: bibledit
Version: 5.0.331-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0], we noticed
that bibledit could not be built reproducibly.

This is because it uselessly ships config.log etc. in the binary
packages which include all sorts of environment-specific data.

Patch attached that simply doesn't install these files... BUT it looks
like there is a whole bunch of cruft in the -data package anyway,
essentially including the build-directory itself (with Makefile.am etc.
etc.)

In other words, only specifying the stuff bibledit really needs in
bibledit-data.install would be the superior solution. :)

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/rules  2017-12-10 17:49:39.121184637 +
--- b/debian/rules  2017-12-10 20:17:48.107528230 +
@@ -15,3 +15,5 @@
 override_dh_installchangelogs:
dh_installchangelogs help/changelog.html
 
+override_dh_install:
+   dh_install -Xconfig.log -Xconfig.status -XMakefile

Bug#883156: version 1.1

[Samuel Thibault]

Hello,

Paolo Greppi, on lun. 04 déc. 2017 18:24:46 +0100, wrote:
> P.S. IMHO it would make sense to separate the libttspico-utils binary package 
> from the svox source package.
> In this way it would have its own version number, plus the code would not be 
> in a patch 
> but in plaintext.

Indeed, it makes a lot of sense, it "just needs" to be done, any taker ? :)
(it means: submitting the ITP, setting up a repo on alioth for the
debian packaging, writing the packaging bits, and upload. I can quickly
do the last step if all the previous steps are done).

Samuel

Bug#884044: jitescript FTBFS with libasm-java 6.0-1

[Emmanuel Bourg]

Thank you Adrian, I didn't remember I reported this issue upstream
earlier this year:

  https://github.com/qmx/jitescript/issues/15

A simple cast to List in MethodDefinition and FieldDefinition should fix
this.

Emmanuel Bourg

Bug#884046: jetty9 FTBFS: org.eclipse.jetty.websocket.jsr356.ClientContainer is not abstract and does not override abstract method setDefaultAsyncSendTimeout(long) in javax.websocket.WebSocketContaine

[Adrian Bunk]

Source: jetty9
Version: 9.2.22-2
Severity: serious

Some recent change in unstable makes jetty9 FTBFS:

https://tests.reproducible-builds.org/debian/history/jetty9.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/jetty9.html

...
[INFO] Reactor Summary:
[INFO] 
[INFO] Jetty :: Project ... SUCCESS [  3.169 s]
[INFO] Jetty :: Utilities . SUCCESS [ 27.806 s]
[INFO] Jetty :: JMX Management  SUCCESS [  1.077 s]
[INFO] Jetty :: IO Utility  SUCCESS [  2.151 s]
[INFO] Jetty :: Http Utility .. SUCCESS [  2.857 s]
[INFO] Jetty :: Continuation .. SUCCESS [  0.833 s]
[INFO] Jetty :: XML utilities . SUCCESS [  1.333 s]
[INFO] Jetty :: Server Core ... SUCCESS [  8.341 s]
[INFO] Jetty :: Security .. SUCCESS [  2.356 s]
[INFO] Jetty :: Servlet Handling .. SUCCESS [  2.087 s]
[INFO] Jetty :: Webapp Application Support  SUCCESS [  1.878 s]
[INFO] Jetty :: Asynchronous HTTP Client .. SUCCESS [  2.793 s]
[INFO] Jetty :: FastCGI :: Parent . SUCCESS [  0.009 s]
[INFO] Jetty :: FastCGI :: Client . SUCCESS [  3.420 s]
[INFO] Jetty :: Utilities :: Ajax(JSON) ... SUCCESS [  0.726 s]
[INFO] Jetty :: Proxy . SUCCESS [  1.242 s]
[INFO] Jetty :: FastCGI :: Server . SUCCESS [  0.631 s]
[INFO] Jetty :: Websocket :: Parent ... SUCCESS [  0.053 s]
[INFO] Jetty :: Websocket :: API .. SUCCESS [  0.840 s]
[INFO] Jetty :: Websocket :: Common ... SUCCESS [  3.353 s]
[INFO] Jetty :: Websocket :: Client ... SUCCESS [  3.176 s]
[INFO] Jetty :: Websocket :: Servlet Interface  SUCCESS [  0.820 s]
[INFO] Jetty :: JNDI Naming ... SUCCESS [  1.257 s]
[INFO] Jetty :: Plus .. SUCCESS [  1.509 s]
[INFO] Jetty :: Servlet Annotations ... SUCCESS [  1.260 s]
[INFO] Jetty :: Websocket :: Server ... SUCCESS [  1.057 s]
[INFO] Jetty :: Websocket :: javax.websocket :: Client Implementation FAILURE [ 
 1.113 s]
[INFO] Jetty :: Websocket :: javax.websocket.server :: Server Implementation 
SKIPPED
[INFO] Jetty :: Utility Servlets and Filters .. SKIPPED
[INFO] Jetty :: Apache JSP Implementation . SKIPPED
[INFO] Apache :: JSTL module .. SKIPPED
[INFO] Jetty :: Deployers . SKIPPED
[INFO] Jetty :: Start . SKIPPED
[INFO] Jetty :: JAAS .. SKIPPED
[INFO] Jetty :: CDI Configurations  SKIPPED
[INFO] Example :: Jetty Spring  SKIPPED
[INFO] Jetty :: JASPI Security  SKIPPED
[INFO] Jetty :: Rewrite Handler ... SKIPPED
[INFO] Jetty :: Quick Start ... SKIPPED
[INFO] Jetty :: Monitoring  SKIPPED
[INFO] Jetty :: ALPN :: API ... SKIPPED
[INFO] Jetty :: ALPN :: Parent  SKIPPED
[INFO] Jetty :: ALPN Server ... SKIPPED
[INFO] Jetty :: ALPN Client ... SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 01:25 min
[INFO] Finished at: 2017-12-10T06:20:16-12:00
[INFO] Final Memory: 49M/1474M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.6.2:compile (default-compile) 
on project javax-websocket-client-impl: Compilation failure
[ERROR] 
/build/1st/jetty9-9.2.22/jetty-websocket/javax-websocket-client-impl/src/main/java/org/eclipse/jetty/websocket/jsr356/ClientContainer.java:[69,8]
 org.eclipse.jetty.websocket.jsr356.ClientContainer is not abstract and does 
not override abstract method setDefaultAsyncSendTimeout(long) in 
javax.websocket.WebSocketContainer
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  

Bug#884045: gnome should recommend gnome-getting-started-docs

[Matteo Cortese]

Package: gnome
Version: 1:3.22+5
Severity: minor

Please consider changing the dependency of gnome on
gnome-getting-started-docs from Depends: to Recommends: for the following
reasons.

1. Not installing gnome-getting-started-docs does not hinder the use of
Gnome. That's a clear call for Recommends.

2. A document called "Getting Started" is, by definition, only used once at
the beginning. It must be possible to remove it later on.

3. The size of gnome-getting-started-docs is far from negligible, nearing
200 MB. On some constrained systems it may be an issue.

​Using Recommends will achieve both goals: the documents will get installed
by default by inexperienced users, and will not bother those users skilled
enough to override a Recommends dependency.
​
Mfc​

Bug#879764: fixed in golang-1.9 1.9.2-4

[Michael Hudson-Doyle]

On 9 December 2017 at 00:30, James Cowgill  wrote:

> Hi,
>
> On 08/12/17 01:34, Michael Hudson-Doyle wrote:
> > Source: golang-1.9
> > Source-Version: 1.9.2-4
> >
> > We believe that the bug you reported is fixed in the latest version of
> > golang-1.9, which is due to be installed in the Debian FTP archive.
> [...]
> >* Enable building on mips, mipsel and mips64. (Closes: 879764)
>
> Thanks for this. The mips and mipsel builds failed due to #867358,
> however the fix for this is in the kernel due to be released in the next
> stable point release tomorrow. After the mips buildds have had their
> kernels updated, I'll give the package back and it should build.
>

Ah, good timing (I knew there was a reason I sat on these patches for
months...)


> After this is done, is there anything you want me to do (like rebuilds,
> give-backs, patches, etc) to get mips* enabled in golang-defaults?
>

Well patches for golang-defaults could be nice I guess. It's pretty trivial
though so so long as don't forget I can do it in 5 mins :-) We should
probably wait for the kernel fix and the rebuilds of golang-1.9 though.

Cheers,
mwh

Bug#883938: Sun Fire X4200 M2 Xen

[Dr. Nagy Elemér Kár oly]

Hi,

The non-booting machines have multiple CPUs:
 * X4200M2: 2 AMD 2220, no Xen, LVM
 * X2200M2: 2 AMD 2347HE

The booting machine has multiple CPUs as well, but Xen is configured to give 
only 1 vCPU to Doms.
 * X4200M2: 2 AMD 2220, Xen

The freezing machine might have a HW problem or might be hit by Debian bug 
#880554 as even after downgrading all DomU and 
Dom0 kernels, the freeze still occurs, even though it boots.

Elmar