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

Processed: Re: diaspora: Package fails to install

[Debian Bug Tracking System]

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

> reopen 872305 !
Bug #872305 {Done: Joseph N } [diaspora] diaspora: Package 
fails to install
Bug reopened
Changed Bug submitter to 'Joseph Nuthalapati ' from 
'njoseph '.
Ignoring request to alter fixed versions of bug #872305 to the same values 
previously set
> tag 872305 + patch
Bug #872305 [diaspora] diaspora: Package fails to install
Added tag(s) patch.
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

Processing control commands:

> severity -1 critical
Bug #884069 [linux-image-3.16.0-4-amd64] Kernel crash on boot on IBM 
BladeCenter HS22
Severity set to 'critical' from 'normal'

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

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#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#875349: marked as pending

[Eric Dorland]

tag 875349 pending
thanks

Hello,

Bug #875349 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

https://anonscm.debian.org/cgit/pkg-opensc/libp11.git/commit/?id=b76e48c

---
commit b76e48c5f8f8339fae60a01398a45e962f75bebe
Author: Eric Dorland 
Date:   Mon Dec 11 00:43:49 2017 -0500

Rebuild against libssl 1.1 once again

Closes: 875349

diff --git a/debian/changelog b/debian/changelog
index 5836600..a623820 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+libp11 (0.4.7-2) unstable; urgency=medium
+
+  * debian/control, debian/libengine-pkcs11-openssl.install, debian/rules:
+Rebuild against libssl 1.1 once again. (Closes: #875349)
+
+ --
+
 libp11 (0.4.7-1) unstable; urgency=medium
 
   * New upstream release.

Processed: Bug#875349 marked as pending

[Debian Bug Tracking System]

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

> tag 875349 pending
Bug #875349 [libp11] libp11: Please migrate to openssl1.1 in Buster
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#881668: marked as done (python3-txtorcon: unsatisfiable Depends: python3-ipaddr)

[Debian Bug Tracking System]

Your message dated Mon, 11 Dec 2017 06:49:23 +
with message-id 
and subject line Bug#881668: fixed in txtorcon 0.19.3-3
has caused the Debian Bug report #881668,
regarding python3-txtorcon: unsatisfiable Depends: python3-ipaddr
to be marked as done.

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

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


-- 
881668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881668
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-txtorcon
Version: 0.19.3-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is not
installable in sid:

python3-txtorcon/amd64 unsatisfiable Depends: python3-ipaddr
python3-txtorcon/i386 unsatisfiable Depends: python3-ipaddr


python3-ipaddr was last seen in wheezy.


Cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: txtorcon
Source-Version: 0.19.3-3

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

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

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

Debian distribution maintenance software
pp.
Nicolas Braud-Santoni  (supplier of updated txtorcon 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 10 Dec 2017 02:48:18 +0100
Source: txtorcon
Binary: python-txtorcon python3-txtorcon python-txtorcon-doc
Architecture: source
Version: 0.19.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers 

Changed-By: Nicolas Braud-Santoni 
Description:
 python-txtorcon - Twisted-based asynchronous Tor control protocol 
implementation (P
 python-txtorcon-doc - Twisted-based asynchronous Tor control protocol 
implementation (D
 python3-txtorcon - Twisted-based asynchronous Tor control protocol 
implementation (P
Closes: 881668
Changes:
 txtorcon (0.19.3-3) unstable; urgency=medium
 .
   * Team upload.
   * Moving signing key to debian/upstream/
   * debian/control
 * Depend on ipaddress, not ipaddr (Closes: #881668)
 * Replace `Priority: extra` with `optional`
 * Declare compliance with Debian Policy version 4.1.2
   No change required
 * Use HTTPS URIs
   * Removed privacy-infringing buttons & JS.
Checksums-Sha1:
 0d17c5458474a5804bbaa84e25699edd7bd40273 2724 txtorcon_0.19.3-3.dsc
 a039340845982cf261345ed3e4ad674f8177 265716 txtorcon_0.19.3.orig.tar.gz
 a1947817a300142aa6922d1541586204904e6469 455 txtorcon_0.19.3.orig.tar.gz.asc
 0139ef5b91ec1675cf206672544d4f63c73dd6ab 8032 txtorcon_0.19.3-3.debian.tar.xz
 b9ee022016e6b5bdb533b6d8e6d7951ab767f03e 8147 
txtorcon_0.19.3-3_source.buildinfo
Checksums-Sha256:
 bca640131fa3a539a887ac8fc070a1dc936f8c3ddc456327d7589cb877957d99 2724 
txtorcon_0.19.3-3.dsc
 f73396667909a3c7a98f4dd865edf4ed6a2518ee5a935d92e18b8a479ec244fd 265716 
txtorcon_0.19.3.orig.tar.gz
 d94e1dd0b07a83b62e741210559111f26e7147f2f0dde9e8e30f57c32e909ca0 455 
txtorcon_0.19.3.orig.tar.gz.asc
 01c7a0776b41143c50846d1b5550548e43cfcc314ce4f360c9ecf80626e4c059 8032 
txtorcon_0.19.3-3.debian.tar.xz
 bab9964ce059a2f7710b38356df34cbdbd51b6e1dee5dea10d6f13175a7eb00b 8147 
txtorcon_0.19.3-3_source.buildinfo
Files:
 3f9dd0b66881a63a236ce4a3095633d1 2724 python optional txtorcon_0.19.3-3.dsc
 4d7380fa7e721c77cac103d971882374 265716 python optional 
txtorcon_0.19.3.orig.tar.gz
 63ad7d61a9a559c80e70e429dfc471dd 455 python optional 
txtorcon_0.19.3.orig.tar.gz.asc
 849c646ea391826b0ed0ec41671e6d1c 8032 python optional 
txtorcon_0.19.3-3.debian.tar.xz
 4bdd08d1ce3aa6f697d5c394638d2dc2 8147 python optional 
txtorcon_0.19.3-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEExyA8CpIGcL+U8AuxsB0acqyNyaEFAlotX8cPHGpjY0BkZWJp
YW4ub3JnAAoJELAdGnKsjcmhG1cP/2Oksew4KPRw+/Eqm03QTtCp6HtdQIwtPvc5
tCDoqfnikSj0m/87z7oUkYi7ba1ylERv2sQMFPFkuFBKNm4NtZBPwRGcJTymJ0sG
U/qRsxwI5jc4bFWbmMoPKyzgOtF6+X5F7xQPEsKQeFZchl3rWqn8hUbhhY47I+eq
xxFFUv4HcKP78PFf0EEhHnwRLAhWpUuZL/s+psQNFUOo+IqngOEmoeFoZCJDmeSz
voljTJwSqk8py1iMxbDSgxOYUTV5lnSdpl8moelLuIpfFHoQ5ZPXaTWBQHYOvYRY

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#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

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

[Debian Bug Tracking System]

Processing control commands:

> 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
Bug #884065 [src:mariadb-10.2] mariadb-10.2: CVE-2017-10378 CVE-2017-10268 
CVE-2017-15365
Changed Bug title to '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' from 'mariadb-10.2: 
CVE-2017-10378 CVE-2017-10268 CVE-2017-15365'.

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

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#878318: marked as done (nyquist FTBFS with gcc 7: undefined references)

[Debian Bug Tracking System]

Your message dated Mon, 11 Dec 2017 06:04:05 +
with message-id 
and subject line Bug#878318: fixed in nyquist 3.12+ds-1
has caused the Debian Bug report #878318,
regarding nyquist FTBFS with gcc 7: undefined references
to be marked as done.

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

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


-- 
878318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878318
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nyquist
Version: 3.05-2.1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/nyquist.html

...
g++  xlisp/extern.o xlisp/xldmem.o xlisp/xlbfun.o xlisp/xlcont.o xlisp/xldbug.o 
xlisp/xleval.o xlisp/xlfio.o xlisp/xlftab.o xlisp/xlglob.o xlisp/xlimage.o 
xlisp/xlinit.o xlisp/xlio.o xlisp/xlisp.o xlisp/xljump.o xlisp/xllist.o 
xlisp/xlmath.o xlisp/xlobj.o xlisp/xlpp.o xlisp/xlprin.o xlisp/xlread.o 
xlisp/xlstr.o xlisp/xlsubr.o xlisp/xlsym.o xlisp/xlsys.o xlisp/path.o 
tran/abs.o tran/allpoles.o tran/alpass.o tran/alpasscv.o tran/alpassvv.o 
tran/amosc.o tran/areson.o tran/aresonvc.o tran/aresoncv.o tran/aresonvv.o 
tran/atone.o tran/atonev.o tran/biquadfilt.o tran/buzz.o tran/chase.o 
tran/clip.o tran/congen.o tran/const.o tran/coterm.o tran/delaycc.o 
tran/delaycv.o tran/eqbandvvv.o tran/exp.o tran/follow.o tran/fmosc.o 
tran/fromobject.o tran/fromarraystream.o tran/gate.o tran/ifft.o 
tran/instrclar.o tran/instrclarall.o tran/instrclarfreq.o tran/instrsax.o 
tran/instrsaxall.o tran/instrsaxfreq.o tran/integrate.o tran/log.o 
tran/lpreson.o tran/maxv.o tran/offset.o tran/oneshot.o tran/osc.o 
 tran/partial.o tran/pluck.o tran/prod.o tran/pwl.o tran/quantize.o 
tran/recip.o tran/reson.o tran/resonvc.o tran/resoncv.o tran/resonvv.o 
tran/sampler.o tran/scale.o tran/shape.o tran/sine.o tran/siosc.o tran/slope.o 
tran/sqrt.o tran/tapf.o tran/tapv.o tran/tone.o tran/tonev.o tran/upsample.o 
tran/white.o tran/stkrev.o tran/stkpitshift.o tran/stkchorus.o tran/instrbow.o 
tran/instrbowedfreq.o tran/instrbanded.o tran/instrmandolin.o tran/instrsitar.o 
tran/instrmodalbar.o tran/instrflute.o tran/instrflutefreq.o 
tran/instrfluteall.o tran/fmfb.o tran/fmfbv.o cmt/cext.o cmt/cleanup.o 
cmt/cmdline.o cmt/cmtcmd.o cmt/moxc.o cmt/mem.o cmt/midifile.o cmt/midifns.o 
cmt/record.o cmt/seq.o cmt/seqmread.o cmt/seqmwrite.o cmt/seqread.o 
cmt/seqwrite.o cmt/tempomap.o cmt/timebase.o cmt/userio.o nyqsrc/debug.o 
nyqsrc/falloc.o nyqsrc/local.o nyqsrc/handlers.o nyqsrc/multiread.o 
nyqsrc/seqext.o nyqsrc/seqinterf.o nyqsrc/stats.o nyqsrc/ffilterkit.o 
nyqsrc/sliders.o nyqsrc/sound.o nyqsrc/add.o nyqsrc/avg.
 o nyqsrc/compose.o nyqsrc/convolve.o nyqsrc/downsample.o nyqsrc/fft.o 
nyqsrc/inverse.o nyqsrc/multiseq.o nyqsrc/resamp.o nyqsrc/resampv.o 
nyqsrc/samples.o nyqsrc/sndmax.o nyqsrc/sndread.o nyqsrc/sndseq.o 
nyqsrc/sndwritepa.o nyqsrc/yin.o nyqsrc/nyq-osc-server.o nyqsrc/trigger.o 
nyqsrc/lpanal.o nyqsrc/phasevocoder.o nyqsrc/pvshell.o nyqstk/src/Generator.o 
nyqstk/src/SineWave.o nyqstk/src/Function.o nyqstk/src/FileRead.o 
nyqstk/src/FileWvIn.o nyqstk/src/Effect.o nyqstk/src/Clarinet.o 
nyqstk/src/Delay.o nyqstk/src/DelayL.o nyqstk/src/Envelope.o 
nyqstk/src/Filter.o nyqstk/src/Instrmnt.o nyqstk/src/Noise.o 
nyqstk/src/OneZero.o nyqstk/src/ReedTable.o nyqstk/src/Saxofony.o 
nyqstk/src/Stk.o nyqstk/src/WaveLoop.o nyqstk/src/WvIn.o nyqstk/src/NRev.o 
nyqstk/src/JCRev.o nyqstk/src/PRCRev.o nyqstk/src/PitShift.o 
nyqstk/src/Chorus.o nyqstk/src/Bowed.o nyqstk/src/BowTable.o nyqstk/src/ADSR.o 
nyqstk/src/OnePole.o nyqstk/src/BiQuad.o nyqstk/src/BandedWG.o 
nyqstk/src/DelayA.o nyqstk/src/Mandolin.o nyq
 stk/src/PluckTwo.o nyqstk/src/Sitar.o nyqstk/src/ModalBar.o nyqstk/src/Modal.o 
nyqstk/src/Flute.o nyqstk/src/JetTable.o nyqstk/src/PoleZero.o nyqstk/stkinit.o 
nyqstk/instr.o nyqstk/stkint.o ffts/src/fftext.o ffts/src/fftlib.o 
ffts/src/matlib.o nyqsrc/sndfnint.o nyqsrc/seqfnint.o sys/unix/osstuff.o 
sys/unix/term.o  -lsndfile -llo -lportaudio -lm -lpthread -lrt -o ny
ffts/src/fftlib.o: In function `fftrecurs':
fftlib.c:(.text+0xcf8): undefined reference to `bfstages'
ffts/src/fftlib.o: In function `ffts1':
fftlib.c:(.text+0x1441): undefined reference to `bfstages'
ffts/src/fftlib.o: In function `ifftrecurs':
fftlib.c:(.text+0x250a): undefined reference to `ibfstages'
ffts/src/fftlib.o: In function `iffts1':
fftlib.c:(.text+0x2d30): undefined reference to `ibfstages'
ffts/src/fftlib.o: In function `.L186':
fftlib.c:(.text+0x3cd2): undefined reference to `bfstages'
ffts/src/fftlib.o: In function `riffts1':
fftlib.c:(.text+0x4c5c): undefined 

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#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#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

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

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #883761 [src:libgdamm5.0] libgdamm5.0: Includes 
"docs/reference/html/jquery.js" listed in Files-Excluded header
Severity set to 'normal' from 'serious'

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

Bug#883996: marked as done (Could not import PyQt4 on Linux systems)

[Debian Bug Tracking System]

Your message dated Mon, 11 Dec 2017 00:42:24 +
with message-id 

and subject line Re: Bug#883996: Could not import PyQt4 on Linux systems
has caused the Debian Bug report #883996,
regarding Could not import PyQt4 on Linux systems
to be marked as done.

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

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


-- 
883996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883996
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: electrum
Version: 2.9.3-1
Severity: grave

# aptitude install electrum
$ electrum
Error: Could not import PyQt4 on Linux systems, you may try 'sudo apt-get 
install python-qt4'
Exception in thread Thread-9 (most likely raised during interpreter shutdown):
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
  File "/usr/lib/python2.7/dist-packages/electrum/interface.py", line 208, in 
run17:10 1 ~$ 
--- End Message ---
--- Begin Message ---
Control: notfound -1 2.9.3-1

On Sun, 10 Dec 2017 at 11:18 積丹尼 Dan Jacobson  wrote:

> Error: Could not import PyQt4 on Linux systems, you may try 'sudo apt-get
> install python-qt4'
>

python-qt4 is in Recommends, because it is required for the GUI but the
command-line interface is usable without it.
--- End Message ---

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#884044: marked as done (jitescript FTBFS with libasm-java 6.0-1)

[Debian Bug Tracking System]

Your message dated Mon, 11 Dec 2017 00:06:48 +
with message-id 
and subject line Bug#884044: fixed in jitescript 0.4.1-3
has caused the Debian Bug report #884044,
regarding jitescript FTBFS with libasm-java 6.0-1
to be marked as done.

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

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


-- 
884044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884044
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jitescript
Version: 0.4.1-2
Severity: serious

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

...
[INFO] Scanning for projects...
[INFO] 
[INFO] 
[INFO] Building jitescript 0.4.1
[INFO] 
[INFO] 
[INFO] --- maven-resources-plugin:3.0.2:resources (default-resources) @ 
jitescript ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/build/1st/jitescript-0.4.1/src/main/resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.6.2:compile (default-compile) @ jitescript 
---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 8 source files to /build/1st/jitescript-0.4.1/target/classes
[INFO] -
[ERROR] COMPILATION ERROR : 
[INFO] -
[ERROR] 
/build/1st/jitescript-0.4.1/src/main/java/me/qmx/jitescript/MethodDefinition.java:[58,37]
 incompatible types: java.util.ArrayList 
cannot be converted to java.util.List
[ERROR] 
/build/1st/jitescript-0.4.1/src/main/java/me/qmx/jitescript/FieldDefinition.java:[25,35]
 incompatible types: java.util.ArrayList 
cannot be converted to java.util.List
[INFO] 2 errors 
[INFO] -
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 10.282 s
[INFO] Finished at: 2017-12-10T06:17:39-12:00
[INFO] Final Memory: 13M/559M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.6.2:compile (default-compile) 
on project jitescript: Compilation failure: Compilation failure: 
[ERROR] 
/build/1st/jitescript-0.4.1/src/main/java/me/qmx/jitescript/MethodDefinition.java:[58,37]
 incompatible types: java.util.ArrayList 
cannot be converted to java.util.List
[ERROR] 
/build/1st/jitescript-0.4.1/src/main/java/me/qmx/jitescript/FieldDefinition.java:[25,35]
 incompatible types: java.util.ArrayList 
cannot be converted to java.util.List
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/jitescript-0.4.1 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/build/1st/jitescript-0.4.1/debian 
-Dmaven.repo.local=/build/1st/jitescript-0.4.1/debian/maven-repo --batch-mode 
package -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1
debian/rules:3: recipe for target 'build' failed
make: *** [build] Error 1
--- End Message ---
--- Begin Message ---
Source: jitescript
Source-Version: 0.4.1-3

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

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

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

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

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the 

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#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

Processed: Pending fixes for bugs in the jitescript package

[Debian Bug Tracking System]

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

> tag 884044 + pending
Bug #884044 [src:jitescript] jitescript FTBFS with libasm-java 6.0-1
Added tag(s) pending.
> thanks
Stopping processing here.

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

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#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


pgpOALhYIXdRX.pgp
Description: PGP signature

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#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#851506: marked as done (cpanminus: major parts of upstream sources with compressed white-space)

[Debian Bug Tracking System]

Your message dated Sun, 10 Dec 2017 22:37:06 +
with message-id 
and subject line Bug#851506: fixed in cpanminus 1.7043-1
has caused the Debian Bug report #851506,
regarding cpanminus: major parts of upstream sources with compressed white-space
to be marked as done.

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

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


-- 
851506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851506
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cpanminus
Version: 1.7042-2
Severity: normal

Dear Maintainer,

cpanminus embeds convenience copies of other modules.

Outside of Debian, fatpacking other modules with cpanminus makes sense
to help users install this tool (which is a package manager). THis
avoid a catch22 issue.

BUt in Debian context, all required modules are available as Debian
packages and are installed with apt. So the fatpacked modules are
needlessly duplicated.

Providing cpanminus without fatpack can be done by either:
- removing fatpacked part from the cpan tarball
- create debian package from upstream git repo (where fatpack
  is not yet done, even if this repo contains convenience
  copies of the modules).

All the best

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

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

Versions of packages cpanminus depends on:
ii  curl 7.52.1-1
ii  libcpan-distnameinfo-perl0.12-1
ii  libcpan-meta-check-perl  0.014-1
ii  libfile-pushd-perl   1.014-1
ii  liblocal-lib-perl2.19-1
ii  libmodule-cpanfile-perl  1.1002-1
ii  libparse-pmfile-perl 0.41-1
ii  libstring-shellquote-perl1.03-1.2
ii  perl 5.24.1~rc4-1
ii  perl-modules-5.24 [libversion-perl]  5.24.1~rc4-1
ii  wget 1.18-4

cpanminus recommends no packages.

cpanminus suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: cpanminus
Source-Version: 1.7043-1

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

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

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated cpanminus package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 10 Dec 2017 23:15:52 +0100
Source: cpanminus
Binary: cpanminus
Architecture: source
Version: 1.7043-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 851506
Description: 
 cpanminus  - script to get, unpack, build and install modules from CPAN
Changes:
 cpanminus (1.7043-1) unstable; urgency=medium
 .
   [ gregor herrmann ]
   * Add a patch to add a test which tries to load all modules.
 .
   [ Alex Muntada ]
   * Remove inactive pkg-perl members from Uploaders.
 .
   [ gregor herrmann ]
   * debian/watch: download tarball from Github but keep searching for
 latest stable release version on MetaCPAN, as Github also has devel
 releases with higher version numbers.
   * Add debian/gbp.conf to ignore .gitignore on import.
 .
   * Import upstream version 1.7043.
   * Update debian/copyright.
 The tarball from Github contains some third-party files.
   * Update build machinery to new tarball source and avoid any fatpacking.
 - run (patched) maint/build.pl in debian/rules instead of removing
   fatpacked modules after the fact
 - update build dependencies
 - remove generated files via debian/clean
 - update debian/patches/test-load.patch (new modules)
 (Closes: #851506)
   * Replace ad-hoc test in debian/rules with a (patch that creates a) test
 script which runs both during build and autopkgtest.
   * 

Bug#883118: marked as done (libupnp: SEGV in upnp/src/genlib/net/http/httpreadwrite.c:1662)

[Debian Bug Tracking System]

Your message dated Sun, 10 Dec 2017 22:25:19 +
with message-id 
and subject line Bug#883118: fixed in libupnp 1:1.6.24-2
has caused the Debian Bug report #883118,
regarding libupnp: SEGV in upnp/src/genlib/net/http/httpreadwrite.c:1662
to be marked as done.

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

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


-- 
883118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883118
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gmediarender
Version: 0.0.7~git20160329+repack-1
Severity: normal

Dear Maintainer,

as usually, last weekend i upgraded my sid boxes.
these run gmediarender. now i restarted two of them,
then noticed that gmediarender crashes just after the
first incoming upnp search. i dist-upgraded again,
but the issue still exists.
i see this if i start from the terminal:
mc36@acer:~$ gmediarender
gmediarender 0.0.7-git started [ gmediarender 0.0.7-git 
(libupnp-1.6.19+git20160116; glib-2.49.6; gstreamer-1.8.3) ].
Logging switched off. Enable with --logfile= (e.g. 
--logfile=/dev/stdout for console)
Segmentation fault
mc36@acer:~$
i see this in the dmesg:
[ 9788.977982] gmediarender[6368]: segfault at 0 ip 7f4cbc7cd375 sp 
7f4c2893c1b0 error 4 in libupnp.so.6.4.0[7f4cbc7b7000+36000]
i see this packet as a trigger, but probaby others will do:
User Datagram Protocol, Src Port: 40871, Dst Port: 1900
Source Port: 40871
Destination Port: 1900
Length: 157
Checksum: 0xafb8 [correct]
[Calculated Checksum: 0xafb8]
[Checksum Status: Good]
[Stream index: 50]
Simple Service Discovery Protocol
M-SEARCH * HTTP/1.1\r\n
[Expert Info (Chat/Sequence): M-SEARCH * HTTP/1.1\r\n]
[M-SEARCH * HTTP/1.1\r\n]
[Severity level: Chat]
[Group: Sequence]
Request Method: M-SEARCH
Request URI: *
Request Version: HTTP/1.1
HOST: 239.255.255.250:1900\r\n
MAN: "ssdp:discover"\r\n
MX: 3\r\n
ST: upnp:rootdevice\r\n
USER-AGENT: Android/25 UPnP/1.1 UPnPTool/1.4.8\r\n
\r\n
[Full request URI: http://239.255.255.250:1900*]
[HTTP request 1/1]
to trigger, i used android's upnptool.


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

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

Versions of packages gmediarender depends on:
ii  libc6  2.25-2
ii  libglib2.0-0   2.54.2-1
ii  libgstreamer1.0-0  1.12.3-1
ii  libupnp6   1:1.6.24-1
ii  lsb-base   9.20170808

Versions of packages gmediarender recommends:
ii  gstreamer1.0-plugins-good  1.12.3-1

Versions of packages gmediarender suggests:
pn  gstreamer-plugins-ugly
ii  gstreamer1.0-plugins-bad  1.12.3-2

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libupnp
Source-Version: 1:1.6.24-2

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

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

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

Debian distribution maintenance software
pp.
Uwe Kleine-König  (supplier of updated libupnp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 10 Dec 2017 23:02:08 +0100
Source: libupnp
Binary: libupnp6 libupnp6-dev libupnp-dev libupnp6-doc
Architecture: source
Version: 1:1.6.24-2
Distribution: unstable
Urgency: high
Maintainer: Uwe Kleine-König 
Changed-By: Uwe Kleine-König 
Description:
 libupnp-dev - Portable SDK for UPnP Devices (development files)
 libupnp6   - Portable SDK for UPnP Devices, version 1.6 (shared libraries)
 libupnp6-dev - Portable SDK for UPnP Devices, version 1.6 (development files)
 libupnp6-doc - Documentation for the Portable SDK for UPnP Devices, version 1.6
Closes: 883118
Changes:
 libupnp (1:1.6.24-2) unstable; urgency=high
 .
   * Cherry pick "Fix segmentation fault 

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#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#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

Processed: poppler 0.61.1 is now in unstable

[Debian Bug Tracking System]

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

> severity 883523 serious
Bug #883523 [xpdf] xpdf: FTBFS with poppler 0.61.1
Severity set to 'serious' from 'important'
> severity 883522 serious
Bug #883522 [src:utopia-documents] utopia-documents: FTBFS with poppler 0.61.1
Severity set to 'serious' from 'important'
> severity 883525 serious
Bug #883525 [pdf2htmlex] pdf2htmlex: FTBFS with poppler 0.61.1
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #884019 [src:terminology] terminology: FTBFS if $HOME is not writable
Added tag(s) pending.

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

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

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

[Debian Bug Tracking System]

Processing control commands:

> tag -1 += upstream fixed-upstream
Bug #883118 [libupnp] libupnp: SEGV in 
upnp/src/genlib/net/http/httpreadwrite.c:1662
Ignoring request to alter tags of bug #883118 to the same tags previously set

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

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

[Debian Bug Tracking System]

Processing control commands:

> tag -1 += upstream fixed-upstream
Bug #883118 [libupnp] libupnp: SEGV in 
upnp/src/genlib/net/http/httpreadwrite.c:1662
Added tag(s) fixed-upstream and upstream; removed tag(s) confirmed.

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

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#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.

Processed: cloning 884012, reassign -1 to libical3, found -1 in 3.0.1-5

[Debian Bug Tracking System]

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

> clone 884012 -1
Bug #884012 [gnome-shell] gnome-shell: 
/usr/lib/gnome-shell/gnome-shell-calendar-server continually crashes with 
segfault
Bug 884012 cloned as bug 884048
> reassign -1 libical3
Bug #884048 [gnome-shell] gnome-shell: 
/usr/lib/gnome-shell/gnome-shell-calendar-server continually crashes with 
segfault
Bug reassigned from package 'gnome-shell' to 'libical3'.
No longer marked as found in versions gnome-shell/3.26.2-1.
Ignoring request to alter fixed versions of bug #884048 to the same values 
previously set
> found -1 3.0.1-5
Bug #884048 [libical3] gnome-shell: 
/usr/lib/gnome-shell/gnome-shell-calendar-server continually crashes with 
segfault
Marked as found in versions libical3/3.0.1-5.
> thanks
Stopping processing here.

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

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#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

Processed: Re: Bug#863788: oolite: Please drop dependency against mozjs 1.8.5

[Debian Bug Tracking System]

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

> forwarded 863788 https://github.com/OoliteProject/oolite/issues/271
Bug #863788 [src:oolite] oolite: Please drop dependency against mozjs 1.8.5
Set Bug forwarded-to-address to 
'https://github.com/OoliteProject/oolite/issues/271'.
>
End of message, stopping processing here.

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

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

Bug#876695: Fixed upstream

[Leonardo Zide]

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#884044: jitescript FTBFS with libasm-java 6.0-1

[Adrian Bunk]

Source: jitescript
Version: 0.4.1-2
Severity: serious

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

...
[INFO] Scanning for projects...
[INFO] 
[INFO] 
[INFO] Building jitescript 0.4.1
[INFO] 
[INFO] 
[INFO] --- maven-resources-plugin:3.0.2:resources (default-resources) @ 
jitescript ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/build/1st/jitescript-0.4.1/src/main/resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.6.2:compile (default-compile) @ jitescript 
---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 8 source files to /build/1st/jitescript-0.4.1/target/classes
[INFO] -
[ERROR] COMPILATION ERROR : 
[INFO] -
[ERROR] 
/build/1st/jitescript-0.4.1/src/main/java/me/qmx/jitescript/MethodDefinition.java:[58,37]
 incompatible types: java.util.ArrayList 
cannot be converted to java.util.List
[ERROR] 
/build/1st/jitescript-0.4.1/src/main/java/me/qmx/jitescript/FieldDefinition.java:[25,35]
 incompatible types: java.util.ArrayList 
cannot be converted to java.util.List
[INFO] 2 errors 
[INFO] -
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 10.282 s
[INFO] Finished at: 2017-12-10T06:17:39-12:00
[INFO] Final Memory: 13M/559M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.6.2:compile (default-compile) 
on project jitescript: Compilation failure: Compilation failure: 
[ERROR] 
/build/1st/jitescript-0.4.1/src/main/java/me/qmx/jitescript/MethodDefinition.java:[58,37]
 incompatible types: java.util.ArrayList 
cannot be converted to java.util.List
[ERROR] 
/build/1st/jitescript-0.4.1/src/main/java/me/qmx/jitescript/FieldDefinition.java:[25,35]
 incompatible types: java.util.ArrayList 
cannot be converted to java.util.List
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/jitescript-0.4.1 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/build/1st/jitescript-0.4.1/debian 
-Dmaven.repo.local=/build/1st/jitescript-0.4.1/debian/maven-repo --batch-mode 
package -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1
debian/rules:3: recipe for target 'build' failed
make: *** [build] Error 1

Bug#872531: node-argparse FTBFS with nodejs 6.11.2

[Juhani Numminen]

Control: tags -1 fixed-upstream

Hi,
There's a commit to fix this, and upstream versions >= 1.0.8
include that change.
https://github.com/nodeca/argparse/commit/8d4bcdb29b1def6f44c88fc13236e6e3fc85806d

Regards,
Juhani

Processed: Re: node-argparse FTBFS with nodejs 6.11.2

[Debian Bug Tracking System]

Processing control commands:

> tags -1 fixed-upstream
Bug #872531 [src:node-argparse] node-argparse FTBFS with nodejs 6.11.2
Added tag(s) fixed-upstream.

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

Processed: severity of 884012 is grave

[Debian Bug Tracking System]

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

> severity 884012 grave
Bug #884012 [gnome-shell] gnome-shell: 
/usr/lib/gnome-shell/gnome-shell-calendar-server continually crashes with 
segfault
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Processed: obfsproxy: Ship an AppArmor profile again

[Debian Bug Tracking System]

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

> clone 882103 -1
Bug #882103 {Done: intrigeri } [obfsproxy] 
python-pkg-resources: crashing with "ImportError: No module named 
load_entry_point"
Bug 882103 cloned as bug 884043
> reopen -1
Bug #884043 {Done: intrigeri } [obfsproxy] 
python-pkg-resources: crashing with "ImportError: No module named 
load_entry_point"
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions obfsproxy/0.2.13-3.
> retitle -1 obfsproxy: Ship an AppArmor package again
Bug #884043 [obfsproxy] python-pkg-resources: crashing with "ImportError: No 
module named load_entry_point"
Changed Bug title to 'obfsproxy: Ship an AppArmor package again' from 
'python-pkg-resources: crashing with "ImportError: No module named 
load_entry_point"'.
> severity -1 wishlist
Bug #884043 [obfsproxy] obfsproxy: Ship an AppArmor package again
Severity set to 'wishlist' from 'grave'
> user pkg-apparmor-t...@lists.alioth.debian.org
Setting user to pkg-apparmor-t...@lists.alioth.debian.org (was 
nico...@braud-santoni.eu).
> usertag -1 buggy-profile
There were no usertags set.
Usertags are now: buggy-profile.
>
End of message, stopping processing here.

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

Bug#884041: node-braces FTBFS: test failures

[Adrian Bunk]

Source: node-braces
Version: 2.0.2-1
Severity: serious
Tags: buster sid

Some recent change in unstable makes node-braces FTBFS:

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

...
  5 failing

  1) bash.expanded should compile: {214748364..2147483649}:
 AssertionError: {214748364..2147483649}
  at match (/build/1st/node-braces-2.0.2/test/bash.expanded.js:9:10)
  at Context. 
(/build/1st/node-braces-2.0.2/test/bash.expanded.js:408:7)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:223:21)
  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:216:7)
  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:373:10)
  at /usr/lib/nodejs/mocha/lib/runner.js:451:12
  at next (/usr/lib/nodejs/mocha/lib/runner.js:298:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:308:7
  at next (/usr/lib/nodejs/mocha/lib/runner.js:246:23)
  at Immediate. (/usr/lib/nodejs/mocha/lib/runner.js:275:5)
  at runCallback (timers.js:672:20)
  at tryOnImmediate (timers.js:645:5)
  at processImmediate [as _immediateCallback] (timers.js:617:5)

  2) bash.expanded should compile: {214748364..2147483649}:
 AssertionError: {214748364..2147483649}
  at match (/build/1st/node-braces-2.0.2/test/bash.optimized.js:9:10)
  at Context. 
(/build/1st/node-braces-2.0.2/test/bash.optimized.js:406:7)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:223:21)
  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:216:7)
  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:373:10)
  at /usr/lib/nodejs/mocha/lib/runner.js:451:12
  at next (/usr/lib/nodejs/mocha/lib/runner.js:298:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:308:7
  at next (/usr/lib/nodejs/mocha/lib/runner.js:246:23)
  at Immediate. (/usr/lib/nodejs/mocha/lib/runner.js:275:5)
  at runCallback (timers.js:672:20)
  at tryOnImmediate (timers.js:645:5)
  at processImmediate [as _immediateCallback] (timers.js:617:5)

  3) bash.expanded should compile: {214748364..2147483649}:
 AssertionError: {214748364..2147483649}
  at match (/build/1st/node-braces-2.0.2/test/bash.optimized.js:9:10)
  at Context. 
(/build/1st/node-braces-2.0.2/test/bash.optimized.js:406:7)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:223:21)
  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:216:7)
  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:373:10)
  at /usr/lib/nodejs/mocha/lib/runner.js:451:12
  at next (/usr/lib/nodejs/mocha/lib/runner.js:298:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:308:7
  at next (/usr/lib/nodejs/mocha/lib/runner.js:246:23)
  at Immediate. (/usr/lib/nodejs/mocha/lib/runner.js:275:5)
  at runCallback (timers.js:672:20)
  at tryOnImmediate (timers.js:645:5)
  at processImmediate [as _immediateCallback] (timers.js:617:5)

  4) expanded ranges large numbers should expand large numbers:
 AssertionError: [ 
'(21474836[4-9]|2147483[7-9][0-9]|214748[4-9][0-9]{2}|214749[0-9]{3}|2147[5-9][0-9]{4}|214[89][0-9]{5}|21[5-9][0-9]{6}|2[2-9][
 deepEqual [ 
'(21474836[4-9]|2147483[7-9][0-9]|214748[4-9][0-9]{2}|214749[0-9]{3}|2147[5-9][0-9]{4}|214[8-9][0-9]{5}|21[5-9][0-9]{6}|2[2-9]
  at match (/build/1st/node-braces-2.0.2/test/expanded.ranges.js:8:10)
  at Context. 
(/build/1st/node-braces-2.0.2/test/expanded.ranges.js:128:7)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:223:21)
  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:216:7)
  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:373:10)
  at /usr/lib/nodejs/mocha/lib/runner.js:451:12
  at next (/usr/lib/nodejs/mocha/lib/runner.js:298:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:308:7
  at next (/usr/lib/nodejs/mocha/lib/runner.js:246:23)
  at Immediate. (/usr/lib/nodejs/mocha/lib/runner.js:275:5)
  at runCallback (timers.js:672:20)
  at tryOnImmediate (timers.js:645:5)
  at processImmediate [as _immediateCallback] (timers.js:617:5)

  5) optimized ranges large numbers should expand large numbers:
 AssertionError: [ 
'(21474836[4-9]|2147483[7-9][0-9]|214748[4-9][0-9]{2}|214749[0-9]{3}|2147[5-9][0-9]{4}|214[89][0-9]{5}|21[5-9][0-9]{6}|2[2-9][
 deepEqual [ 
'(21474836[4-9]|2147483[7-9][0-9]|214748[4-9][0-9]{2}|214749[0-9]{3}|2147[5-9][0-9]{4}|214[8-9][0-9]{5}|21[5-9][0-9]{6}|2[2-9]
  at match (/build/1st/node-braces-2.0.2/test/optimized.js:15:10)
  at Context. 
(/build/1st/node-braces-2.0.2/test/optimized.js:269:9)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:223:21)
  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:216:7)
  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:373:10)
  at 

Bug#884040: python-matplotlib-venn FTBFS: test failure

[Adrian Bunk]

Source: python-matplotlib-venn
Version: 0.11.5-2
Severity: serious

Some recent change in unstable makes python-matplotlib-venn FTBFS:

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/python-matplotlib-venn-0.11.5'
xvfb-run --auto-servernum --server-args="-screen 0 1024x768x24" \
dh_auto_test -- --test --system=custom --test-args='cp -a README.rst 
{home_dir}/build && cd {home_dir}/build && {interpreter} 
/build/1st/python-matplotlib-venn-0.11.5/setup.py test && rm README.rst'
pybuild --test --test-pytest -i python{version} -p 2.7 --test 
--system=custom "--test-args=cp -a README.rst {home_dir}/build && cd 
{home_dir}/build && {interpreter} 
/build/1st/python-matplotlib-venn-0.11.5/setup.py test && rm README.rst"
I: pybuild base:184: cp -a README.rst 
/build/1st/python-matplotlib-venn-0.11.5/.pybuild/pythonX.Y_2.7/build && cd 
/build/1st/python-matplotlib-venn-0.11.5/.pybuild/pythonX.Y_2.7/build && 
python2.7 /build/1st/python-matplotlib-venn-0.11.5/setup.py test && rm 
README.rst
running test
running egg_info
creating matplotlib_venn.egg-info
writing requirements to matplotlib_venn.egg-info/requires.txt
writing matplotlib_venn.egg-info/PKG-INFO
writing top-level names to matplotlib_venn.egg-info/top_level.txt
writing dependency_links to matplotlib_venn.egg-info/dependency_links.txt
writing manifest file 'matplotlib_venn.egg-info/SOURCES.txt'
reading manifest file 'matplotlib_venn.egg-info/SOURCES.txt'
writing manifest file 'matplotlib_venn.egg-info/SOURCES.txt'
running build_ext
= test session starts ==
platform linux2 -- Python 2.7.14+, pytest-3.2.1, py-1.4.34, pluggy-0.4.0 -- 
/usr/bin/python2.7
cachedir: ../../../.cache
rootdir: /build/1st/python-matplotlib-venn-0.11.5, inifile: setup.cfg
collecting ... 
=== warnings summary ===
None
  [pytest] section in setup.cfg files is deprecated, use [tool:pytest] instead.

-- Docs: http://doc.pytest.org/en/latest/warnings.html
== 1 warnings in 0.00 seconds ==
ERROR: file not found: discover
E: pybuild pybuild:283: test: plugin custom failed with: exit code=4: cp -a 
README.rst 
/build/1st/python-matplotlib-venn-0.11.5/.pybuild/pythonX.Y_2.7/build && cd 
/build/1st/python-matplotlib-venn-0.11.5/.pybuild/pythonX.Y_2.7/build && 
python2.7 /build/1st/python-matplotlib-venn-0.11.5/setup.py test && rm 
README.rst
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 --test 
--system=custom "--test-args=cp -a README.rst {home_dir}/build && cd 
{home_dir}/build && {interpreter} 
/build/1st/python-matplotlib-venn-0.11.5/setup.py test && rm README.rst" 
returned exit code 13
debian/rules:10: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25

Bug#884039: linuxtv-dvb-apps FTBFS with linux-libc-dev 4.14.2-1

[Adrian Bunk]

Source: linuxtv-dvb-apps
Version: 1.1.1+rev1500-1.1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/linuxtv-dvb-apps.html

...
dst_test.c: In function 'dst_set_pid':
dst_test.c:116:19: error: 'CA_SET_PID' undeclared (first use in this function); 
did you mean 'CA_GET_CAP'?
  if ((ioctl(cafd, CA_SET_PID)) < 0) {
   ^~
   CA_GET_CAP


CA_SET_PID never did more than returning -EOPNOTSUPP,
and was therefore removed from the kernel.

Bug#884038: [git] 2.15.x fails to fetch remote repository

[mirq-deboogs]

Package: git
Version: 1:2.15.1-1
Severity: grave

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

git 2.15.x from testing can't properly fetch from remote repository:

$ git fetch --all
Fetching origin   
remote: Counting objects: 752, done.
remote: Total 752 (delta 578), reused 578 (delta 578), pack-reused 174
Receiving objects: 100% (752/752), 244.37 KiB | 1.89 MiB/s, done.
Resolving deltas: 100% (619/619), completed with 214 local objects.
fatal: bad object HEAD
error: https://github.com/torvalds/linux.git did not send all necessary objects
  
error: Could not fetch origin 

Downgrading to 2.14.2-1~bpo9+1 from stretch-backports fixes the issue.
Both current 2.15.1-1 and previous 2.15.0-1 in testing are affected.

Example output from working version:

$ git fetch --all
Fetching origin
>From https://github.com/torvalds/linux
   968edbd93c0c..51090c5d6de0  master -> origin/master

.git/config:
[fetch]
prune = true
[remote "origin"]
url = https://github.com/torvalds/linux.git
fetch = +refs/heads/*:refs/remotes/origin/*


--- System information. ---
Architecture: 
Kernel:   Linux 4.14.4mq+

Debian Release: buster/sid
  900 testing-debug   debug.mirrors.debian.org 
  900 testing ftp.pl.debian.org 
  800 stretch-backports ftp.pl.debian.org 
  750 stable  security.debian.org 
  750 stable  ftp.pl.debian.org 
  750 proposed-updates ftp.pl.debian.org 
  700 unstableftp.pl.debian.org 
  600 experimentalftp.pl.debian.org 
  500 unstable-debug  debug.mirrors.debian.org 
  500 stable-debugdebug.mirrors.debian.org 
  500 stable  repository.spotify.com 
  500 stable  dl.google.com 
1 experimental-debug debug.mirrors.debian.org 

--- Package information. ---
Depends   (Version) | Installed
===-+-
libc6 (>= 2.16) | 
libcurl3-gnutls (>= 7.16.2) | 
libexpat1(>= 2.0.1) | 
libpcre2-8-0| 
zlib1g (>= 1:1.2.0) | 
perl| 
liberror-perl   | 
git-man   (>> 1:2.15.1) | 
git-man (<< 1:2.15.1-.) | 


Recommends  (Version) | Installed
=-+-===
patch | 2.7.5-1+b2
less  | 487-0.1
ssh-client| 


Suggests (Version) | Installed
==-+-===
gettext-base   | 0.19.8.1-4
git-daemon-run | 
 OR git-daemon-sysvinit| 
git-doc| 
git-el | 
git-email  | 1:2.15.1-1
git-gui| 
gitk   | 1:2.15.1-1
gitweb | 
git-cvs| 
git-mediawiki  | 
git-svn| 1:2.15.1-1

Bug#883938: Sun Fire X4200 M2 Xen

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

Hi,

Update: probably reproduced the bug in Xen on a Sun Fire X4200 M2 ;(

After 4.5 hours, it froze so hard that I could not power it off via the iLOM, 
even Num Lock wouldn't work. After 
rebooting, lock-ups occurred in about 5-30 minutes. There is nothing in the 
syslog.

After downgrading the Dom0+Xen kernel, the problem persisted.

Downgraded all Dom0 kernels as well, waiting for next lockup :I

Elmar

Bug#836934: frobtads: FTBFS with GCC 6: error: exception cleanup for this placement new selects non-placement operator delete

[Juhani Numminen]

Juhani Numminen kirjoitti 10.12.2017 klo 14:42:


Juhani Numminen kirjoitti 10.12.2017 klo 14:31:


...
On Sat, 24 Sep 2016 22:05:34 +0200 Andreas Beckmann wrote:
... >> Nope. It builds fine on amd64, but fails on i386 (both in 
pbuilder on an

amd64 host).

...
In this patch that applies to frobtads, I add -std=gnu++98 because 
that was the default before GCC 6 changed it to -std=gnu++14.
Actually I think going to C++11 or GNU++11 suffices since due to 
frobtads and qtads duplicating code, this (#836934) is pretty much the 
same as https://bugs.debian.org/857897


Juhani

Processed: Fix the version

[Debian Bug Tracking System]

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

> notfound 883118 1:1.6.24
Bug #883118 [libupnp] libupnp: SEGV in 
upnp/src/genlib/net/http/httpreadwrite.c:1662
There is no source info for the package 'libupnp' at version '1:1.6.24' with 
architecture ''
Unable to make a source version for version '1:1.6.24'
No longer marked as found in versions 1:1.6.24.
> found 883118 1:1.6.24-1
Bug #883118 [libupnp] libupnp: SEGV in 
upnp/src/genlib/net/http/httpreadwrite.c:1662
There is no source info for the package 'libupnp' at version '1:1.6.24-1' with 
architecture ''
Unable to make a source version for version '1:1.6.24-1'
Marked as found in versions 1:1.6.24-1.
> thanks
Stopping processing here.

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

Bug#883938: Same problem with KVM

[Grischa Zengel]

I had the same problem with my VMs under Proxmox/KVM.

After changing CPU structure from "2 socket 1 CPU" to "1 socket 2 CPU" the 
problem was gone.
Only enabling/disabling NUMA didn't work.

So I think it's a problem with aktivating second prozessor.

Bug#828245: marked as done (balsa: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Sun, 10 Dec 2017 17:34:05 +
with message-id 
and subject line Bug#828245: fixed in balsa 2.5.3-3
has caused the Debian Bug report #828245,
regarding balsa: FTBFS with openssl 1.1.0
to be marked as done.

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

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


-- 
828245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828245
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: balsa
Version: 2.4.12-3
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/balsa_2.4.12-3_amd64-20160529-1407

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: balsa
Source-Version: 2.5.3-3

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

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

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

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated balsa package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 10 Dec 2017 18:09:25 +0100
Source: balsa
Binary: balsa
Architecture: source amd64
Version: 2.5.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Laurent Bigonville 
Description:
 balsa  - e-mail client for GNOME
Closes: 828245
Changes:
 balsa (2.5.3-3) unstable; urgency=medium
 .
   * Fix FTBFS with openssl 1.1.0, thanks to Fedora for the patch (Closes:
 #828245)
   * Bump Standards-Version to 4.1.2 (no further changes)
Checksums-Sha1:
 ae9287db9f72dc98560f32e5c17575018c7ee9d0 2197 balsa_2.5.3-3.dsc
 b309954e68b4a1545cff8b1d0369841b3e27c331 13276 balsa_2.5.3-3.debian.tar.xz
 f118613445bdae8edfefb549cfc4936200f77cd3 2382876 balsa-dbgsym_2.5.3-3_amd64.deb
 8eecd6ea180f7b0779d5fd387de762bb8e4e17d0 17344 balsa_2.5.3-3_amd64.buildinfo
 78472f6c98571e56dfa56845a0c0c48f7969f95a 2642576 balsa_2.5.3-3_amd64.deb
Checksums-Sha256:
 61a422c5d81c8af6258752a76dd464679f08c2a6be448a2ad43608d0da3abf55 2197 
balsa_2.5.3-3.dsc
 263819ce38de85d47af52902efa6b3bddb9c7f6d492a4a84d8af8164c2d9a775 13276 
balsa_2.5.3-3.debian.tar.xz
 3541d31adf1f83e1bf9479e7139a041656ce93cc5272efcdce3c6f1a015733d1 2382876 
balsa-dbgsym_2.5.3-3_amd64.deb
 6019903798471e57a90515931093a30739afb1059eb6320bbb84ecab0e256dfd 17344 
balsa_2.5.3-3_amd64.buildinfo
 2cecc118b3db2ce7dab3f05540b2ce1d5189a314843059d43abef26bdca6c842 2642576 
balsa_2.5.3-3_amd64.deb
Files:
 c93123c9451b3b4980457c42c9bd9186 2197 gnome optional balsa_2.5.3-3.dsc
 56cae99d627a7ce2aa2d4dee93d658dd 13276 gnome optional 
balsa_2.5.3-3.debian.tar.xz
 3107cc238b7cc8afd9bcb35bba587cc9 2382876 debug optional 
balsa-dbgsym_2.5.3-3_amd64.deb
 d0dfc22f45adb7edf8a2c3413e3259ae 17344 gnome optional 
balsa_2.5.3-3_amd64.buildinfo
 1c0ce4129d7c1baf61a751a0e8a7bcda 2642576 gnome optional balsa_2.5.3-3_amd64.deb

-BEGIN PGP SIGNATURE-

iQFFBAEBCAAvFiEEmRrdqQAhuF2x31DwH8WJHrqwQ9UFAlotbAMRHGJpZ29uQGRl
Ymlhbi5vcmcACgkQH8WJHrqwQ9UEMAf9FMkW0zoyWLUaZTSFjMzM3AhIOpxv0uXk
gPb7SCocFMlOXpnzq7f07x9qO9/bkZha2tSzb7NmRltUqhqWmNoIapOIMdlVT/sw
rgHWOKJOJznxfA5yMFukBAuM5d0yv8VXz+kgtAKnTuLDqUbCgw0dppvqnv+MiPfK
IIxWu3bpEZkid/0bD2nDb2A433B2Ji6cJc6NDMs9EJlFE8QxxV9pm5HVWDuTDk4V
sI4Jxhdp5Kxf6KvJrMzwvpm18l1hjLn3wlJB+q7bWGj56g5zGWbqWiLKR5/VOjAC
S8sC2rQtF/H0PyDj5dHmA7+Sm3PjK0xaXzYsa4FIQe8KsEP4jhgY8A==
=ePGE
-END PGP SIGNATURE End Message ---

Bug#884034: trinity FTBFS with linux-libc-dev 4.14.2-1

[Adrian Bunk]

Source: trinity
Version: 1.8-1
Severity: serious

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

...
In file included from ioctls/autofs.c:4:0:
ioctls/autofs.c:241:8: error: 'AUTOFS_IOC_EXPIRE_INDIRECT' undeclared here (not 
in a function); did you mean 'AUTOFS_IOC_EXPIRE_CMD'?
  IOCTL(AUTOFS_IOC_EXPIRE_INDIRECT),
^
include/ioctls.h:53:15: note: in definition of macro 'IOCTL'
  { .request = _request, .name = #_request, }
   ^~~~
ioctls/autofs.c:242:8: error: 'AUTOFS_IOC_EXPIRE_DIRECT' undeclared here (not 
in a function); did you mean 'AUTOFS_IOC_EXPIRE_INDIRECT'?
  IOCTL(AUTOFS_IOC_EXPIRE_DIRECT),
^
include/ioctls.h:53:15: note: in definition of macro 'IOCTL'
  { .request = _request, .name = #_request, }
   ^~~~
Makefile:130: recipe for target 'ioctls/autofs.o' failed
make[2]: *** [ioctls/autofs.o] Error 1


These old compatibility defines are no longer available.

Bug#884033: scilab segfaults building scilab-{ann,celestlab,plotlib}

[Adrian Bunk]

Package: scilab
Version: 6.0.0-1
Severity: serious
Control: affects -1 src:scilab-ann src:scilab-celestlab src:scilab-plotlib

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/scilab-ann.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/scilab-celestlab.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/scilab-plotlib.html

...
SCI_DISABLE_TK=1 SCI_JAVA_ENABLE_HEADLESS=1 /usr/bin/scilab -nw -f builder.sce  
A fatal error has been detected by Scilab.
Please check your user-defined functions (or external module ones) should they 
appear in the stack trace.
Otherwise you can report a bug on http://bugzilla.scilab.org/ with:
 * a sample code which reproduces the issue
 * the result of [a, b] = getdebuginfo()
 * the following information:
[profitbricks-build11-amd64:15107] Signal: Segmentation fault (11)
[profitbricks-build11-amd64:15107] Signal code: Address not mapped (1)
[profitbricks-build11-amd64:15107] Failing at address: (nil)
 
Call stack:
   1: 0x9bc60   
(/lib/x86_64-linux-gnu/libc.so.6)
   2: 0x9bc1e   
(/lib/x86_64-linux-gnu/libc.so.6)
   3: 0x46da76  
(/usr/lib/scilab/libsciast.so.6)
   4: 0x46e042  
(/usr/lib/scilab/libsciast.so.6)
   5: 0x3b9c17 (/usr/lib/scilab/libsciast.so.6)
   6: 0x3b9d61   (/usr/lib/scilab/libsciast.so.6)
   7: 0x3ba9ce  (/usr/lib/scilab/libsciast.so.6)
   8: 0x192d05   
(/usr/lib/scilab/libscilab-cli.so.6)
   9: 0x1a23  (/usr/bin/scilab-bin)
  10: 0x20561  <__libc_start_main>  
(/lib/x86_64-linux-gnu/libc.so.6)
  11: 0x247a   < >  (/usr/bin/scilab-bin)
End of stack



debian/rules:8: recipe for target 'build/scilab-ann' failed
make: *** [build/scilab-ann] Error 51

Processed: scilab segfaults building scilab-{ann,celestlab,plotlib}

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:scilab-ann src:scilab-celestlab src:scilab-plotlib
Bug #884033 [scilab] scilab segfaults building scilab-{ann,celestlab,plotlib}
Added indication that 884033 affects src:scilab-ann, src:scilab-celestlab, and 
src:scilab-plotlib

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

Bug#853629: frobtads: FTBFS with GCC-7: error: ISO C++ forbids comparison between pointer and integer

[Juhani Numminen]

Control: tags -1 + patch

In qtads, this is actually fixed upstream, probably because qtads can be 
built with Qt5 and Qt5 requires >= C++11.


The attached patch is tested to work on amd64 and i386.
It fixes "ISO C++ forbids comparison between pointer and integer" for 
both qtads and frobtads.


For frobtads this is not enough, https://bugs.debian.org/836934 needs to 
be taken care of as well.


Juhani
Description: fix pointer/integer comparison
 This change has been adopted in TADS upstream.
Author: Nikos Chantziaras 
Origin: https://github.com/realnc/qtads/commit/46701a23e77756f267e33d33df3a90b59a91c0cd
Bug-Debian: https://bugs.debian.org/853629

--- a/tads3/tct3stm.cpp
+++ b/tads3/tct3stm.cpp
@@ -315,7 +315,7 @@
 CTcPrsNode *create_iter = G_cg->get_metaclass_prop("collection", 0);
 
 /* if we didn't find the property, it's an error */
-if (create_iter != VM_INVALID_PROP)
+if (create_iter != 0)
 {
 /* 
  *   generate a call to the createIterator() property on the

Processed: Re: frobtads: FTBFS with GCC-7: error: ISO C++ forbids comparison between pointer and integer

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #871215 [src:frobtads] frobtads: FTBFS with GCC-7: error: ISO C++ forbids 
comparison between pointer and integer
Ignoring request to alter tags of bug #871215 to the same tags previously set

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

Processed: Re: frobtads: FTBFS with GCC-7: error: ISO C++ forbids comparison between pointer and integer

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #853629 [src:qtads] qtads: ftbfs with GCC-7
Added tag(s) patch.

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

Bug#884032: burp FTBFS: FAIL: runner

[Adrian Bunk]

Source: burp
Version: 2.0.54-4
Severity: serious

https://buildd.debian.org/status/package.php?p=burp=sid

...
make  check-TESTS
make[2]: Entering directory '/<>'
make[3]: Entering directory '/<>'
FAIL: runner
===
   Burp 2.0.54: ./test-suite.log
===

# TOTAL: 1
# PASS:  0
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: runner


Running suite(s): alloc
 asfd
 attribs
 base64
 client_acl
 client_auth
 client_extra_comms
 client_extrameta
 client_find
 client_monitor
 client_monitor_json_input
 client_monitor_lline
 client_monitor_status_client_ncurses
 client_protocol1_backup_phase2
 client_protocol2_backup_phase2
 client_protocol2_rabin_read
 client_restore
 client_xattr
 cmd
 conf
 conffile
 fzp
 hexmap
 lock
 pathcmp
 protocol1_handy
 protocol1_rs_buf
 protocol2_blist
 protocol2_blk
 protocol2_rabin_rabin
 protocol2_rabin_rconf
 protocol2_rabin_win
 sbuf_protocol2
 server_auth
 server_ca
 server_backup_phase3
 server_bu_get
 server_delete
 server_extra_comms
 server_list
 server_manio
 server_monitor_browse
 server_monitor_cache
 server_monitor_cstat
 server_monitor_json_output
 server_protocol1_backup_phase2
 server_protocol1_backup_phase4
0.4
0.3
 server_protocol1_bedup
 server_protocol1_blocklen
 server_protocol1_dpth
 server_protocol1_fdirs
 server_protocol1_restore
 server_protocol2_backup_phase2
 server_protocol2_backup_phase4
 server_protocol2_champ_chooser_champ_chooser
 server_protocol2_champ_chooser_champ_server
 server_protocol2_champ_chooser_dindex
 server_protocol2_champ_chooser_hash
 server_protocol2_champ_chooser_scores
 server_protocol2_champ_chooser_sparse
 server_protocol2_dpth
 server_restore
 server_resume
 server_run_action
 server_sdirs
 slist
99%: Checks: 324, Failures: 3, Errors: 0
utest/client/test_extrameta.c:102:F:Core:test_extrametas:0: Assertion 
'!set_extrameta( NULL, path, expected, strlen(expected), NULL )' failed
utest/client/protocol2/test_rabin_read.c:80:F:Core:test_rabin_read:0: Assertion 
'!set_xattr( NULL, sb->path.buf, x.write, strlen(x.write), metasymbol, NULL )' 
failed
utest/client/test_xattr.c:149:F:Core:test_xattrs:0: Assertion '!set_xattr( 
NULL, path, x.write, strlen(x.write), metasymbol, NULL )' failed
FAIL runner (exit status: 1)


Testsuite summary for Burp 2.0.54

# TOTAL: 1
# PASS:  0
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See ./test-suite.log
Please report to https://github.com/grke/burp/issues

Makefile:7953: recipe for target 'test-suite.log' failed
make[3]: *** [test-suite.log] Error 1
make[3]: Leaving directory '/<>'
Makefile:8059: recipe for target 'check-TESTS' failed
make[2]: *** [check-TESTS] Error 2
make[2]: Leaving directory '/<>'
Makefile:8264: recipe for target 'check-am' failed
make[1]: *** [check-am] Error 2
make[1]: Leaving directory '/<>'
dh_auto_test: make -j3 check VERBOSE=1 returned exit code 2
debian/rules:7: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2

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

[Tobias Frost]

Control: reassign -1 libupnp 1:1.6.24
Control: retitle -1 libupnp: SEGV in 
upnp/src/genlib/net/http/httpreadwrite.c:1662
Control: affects -1 gmediarender

Hallo Uwe,

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.

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)

Looking at the diff from 1.6.22 it looks like that this has been touched:
- before, extra_headers was a string and if NULL it would have been set to an
  empty string ("" == '\0')
- now it is a struct which will be only allocated conditionally (line 1188 in
  webserver.c). Otherwise it is NULL.
- before, it used command "s" not "E"...

Adding this patch:

--- a/upnp/src/genlib/net/http/webserver.c
+++ b/upnp/src/genlib/net/http/webserver.c
@@ -1296,6 +1296,12 @@
goto error_handler;
}
 
+   if (!extra_headers) {
+   extra_headers = (struct Extra_Headers*) malloc(sizeof(struct 
Extra_Headers));
+   if (!extra_headers) goto error_handler;
+   extra_headers->name = NULL;
+   }
+
/* Check if chunked encoding should be used. */
if (using_virtual_dir && finfo.file_length == UPNP_USING_CHUNKED) {
/* Chunked encoding is only supported by HTTP 1.1 clients */

seems to fix the crash, but as soon after the assertion on httpreadwrite:1862
will trigger. It looks like that in line 1672 a "else" is missing to correctly
chain up the commands after the new "E" command:

--- 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);


When applying the patch (attached), gmediarender stops crashing.
However, I cannot say if my changes are sane at all, thus not tagging
"patch". (and also I neglected return code checking of malloc)

Let me know if you need some details!

Cheers,
tobi 

--- a/upnp/src/genlib/net/http/webserver.c
+++ b/upnp/src/genlib/net/http/webserver.c
@@ -1296,6 +1296,12 @@
 		goto error_handler;
 	}
 
+	if (!extra_headers) {
+		extra_headers = (struct Extra_Headers*) malloc(sizeof(struct Extra_Headers));
+		if (!extra_headers) goto error_handler;
+		extra_headers->name = NULL;
+	}
+
 	/* Check if chunked encoding should be used. */
 	if (using_virtual_dir && finfo.file_length == UPNP_USING_CHUNKED) {
 		/* Chunked encoding is only supported by HTTP 1.1 clients */
--- 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);


signature.asc
Description: PGP signature

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

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libupnp 1:1.6.24
Bug #883118 [libupnp] libupnp: SEGV in 
upnp/src/genlib/net/http/httpreadwrite.c:1662
Ignoring request to reassign bug #883118 to the same package
Bug #883118 [libupnp] libupnp: SEGV in 
upnp/src/genlib/net/http/httpreadwrite.c:1662
There is no source info for the package 'libupnp' at version '1:1.6.24' with 
architecture ''
Unable to make a source version for version '1:1.6.24'
Ignoring request to alter found versions of bug #883118 to the same values 
previously set
> retitle -1 libupnp: SEGV in upnp/src/genlib/net/http/httpreadwrite.c:1662
Bug #883118 [libupnp] libupnp: SEGV in 
upnp/src/genlib/net/http/httpreadwrite.c:1662
Ignoring request to change the title of bug#883118 to the same title
> affects -1 gmediarender
Bug #883118 [libupnp] libupnp: SEGV in 
upnp/src/genlib/net/http/httpreadwrite.c:1662
Ignoring request to set affects of bug 883118 to the same value previously set

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

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

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libupnp 1:1.6.24
Bug #883118 [gmediarender] gmediarender crashes when gets an upnp search
Bug reassigned from package 'gmediarender' to 'libupnp'.
No longer marked as found in versions 
gmrender-resurrect/0.0.7~git20160329+repack-1.
Ignoring request to alter fixed versions of bug #883118 to the same values 
previously set
Bug #883118 [libupnp] gmediarender crashes when gets an upnp search
There is no source info for the package 'libupnp' at version '1:1.6.24' with 
architecture ''
Unable to make a source version for version '1:1.6.24'
Marked as found in versions 1:1.6.24.
> retitle -1 libupnp: SEGV in upnp/src/genlib/net/http/httpreadwrite.c:1662
Bug #883118 [libupnp] gmediarender crashes when gets an upnp search
Changed Bug title to 'libupnp: SEGV in 
upnp/src/genlib/net/http/httpreadwrite.c:1662' from 'gmediarender crashes when 
gets an upnp search'.
> affects -1 gmediarender
Bug #883118 [libupnp] libupnp: SEGV in 
upnp/src/genlib/net/http/httpreadwrite.c:1662
Added indication that 883118 affects gmediarender

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

Bug#884030: Depends on obsolete libgoo-canvas-perl

[Jeff]

On 10/12/17 17:24, Laurent Bigonville wrote:
> We are trying to remove the old goocanvas library out of buster.

I know:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785553#35

I've just uploaded libgoocanvas2-perl to NEW:

https://ftp-master.debian.org/new.html

Now I've got to find some code to replace Gtk2::ImageView.

> Please keep gscan2pdf out of testing.

Certainly not! But I'm doing my best to migrate it from Gtk2 to Gtk3 so
that it no longer depends on goocanvas.

Unfortunately, this is not something that takes five minutes.



signature.asc
Description: OpenPGP digital signature

Bug#884031: golang-github-hashicorp-serf: FTBFS on most architectures

[Andreas Beckmann]

Source: golang-github-hashicorp-serf
Version: 0.8.1+git20171021.c20a0b1~ds1-3
Severity: serious

Hi,

the last golang-github-hashicorp-serf upload FTBFS on most
architectures:

https://buildd.debian.org/status/package.php?p=golang-github-hashicorp-serf=unstable

with something that is probably a test failure.


Andreas

Processed: found 877970 in 62.0.3202.89-1

[Debian Bug Tracking System]

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

> found 877970 62.0.3202.89-1
Bug #877970 {Done: Michael Gilbert } 
[chromium-common,chromium-shell] chromium-common,chromium-shell: security 
update in stable invalidated Breaks+Replaces for package split in testing/sid
Marked as found in versions chromium-browser/62.0.3202.89-1.
> thanks
Stopping processing here.

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

Processed: block 785553 with 884030

[Debian Bug Tracking System]

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

> block 785553 with 884030
Bug #785553 [libgoo-canvas-perl] libgoo-canvas-perl: FTBFS with experimental 
goocanvas
785553 was not blocked by any bugs.
785553 was blocking: 858636
Added blocking bug(s) of 785553: 884030
> thanks
Stopping processing here.

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

Bug#884030: Depends on obsolete libgoo-canvas-perl

[Laurent Bigonville]

Package: gscan2pdf
Version: 1.8.10-1
Severity: serious

Hi,

We are trying to remove the old goocanvas library out of buster.

Please keep gscan2pdf out of testing.

Kind regards,

Laurent Bigonville

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

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

Bug#884029: libtirpc3: fails to upgrade from 'sid' - trying to overwrite /etc/netconfig

[Andreas Beckmann]

Package: libtirpc3
Version: 1.0.2-0.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 libtirpc3:amd64.
  Preparing to unpack .../libtirpc3_1.0.2-0.2_amd64.deb ...
  Unpacking libtirpc3:amd64 (1.0.2-0.2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libtirpc3_1.0.2-0.2_amd64.deb (--unpack):
   trying to overwrite '/etc/netconfig', which is also in package 
libtirpc1:amd64 0.2.5-1.2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libtirpc3_1.0.2-0.2_amd64.deb


cheers,

Andreas


libtirpc1=0.2.5-1.2_libtirpc3=1.0.2-0.2.log.gz
Description: application/gzip

Bug#884025: marked as done (analitza-common: file conflict with kde-l10n-*: /usr/share/locale/*/LC_MESSAGES/analitza_qt.qm)

[Debian Bug Tracking System]

Your message dated Sun, 10 Dec 2017 16:56:08 +0100
with message-id <2229728.iHk3ubodTF@pendragon>
and subject line Re: Bug#884025: analitza-common: file conflict with 
kde-l10n-*: /usr/share/locale/*/LC_MESSAGES/analitza_qt.qm
has caused the Debian Bug report #884025,
regarding analitza-common: file conflict with kde-l10n-*: 
/usr/share/locale/*/LC_MESSAGES/analitza_qt.qm
to be marked as done.

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

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


-- 
884025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884025
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: analitza-common
Version: 4:17.08.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts ... well you should know the sermon by now :-)

  Selecting previously unselected package analitza-common.
  Preparing to unpack .../analitza-common_4%3a17.08.3-1_all.deb ...
  Unpacking analitza-common (4:17.08.3-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/analitza-common_4%3a17.08.3-1_all.deb (--unpack):
   trying to overwrite '/usr/share/locale/ar/LC_MESSAGES/analitza_qt.qm', which 
is also in package kde-l10n-ar 4:16.04.3-7
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/analitza-common_4%3a17.08.3-1_all.deb


cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: analitza
Source-Version: 4:17.08.3-2

In data domenica 10 dicembre 2017 16:33:47 CET, Andreas Beckmann ha scritto:
> Package: analitza-common
> Version: 4:17.08.3-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts ... well you should know the sermon by now :-)
> 
>   Selecting previously unselected package analitza-common.
>   Preparing to unpack .../analitza-common_4%3a17.08.3-1_all.deb ...
>   Unpacking analitza-common (4:17.08.3-1) ...
>   dpkg: error processing archive 
> /var/cache/apt/archives/analitza-common_4%3a17.08.3-1_all.deb (--unpack):
>trying to overwrite '/usr/share/locale/ar/LC_MESSAGES/analitza_qt.qm', 
> which is also in package kde-l10n-ar 4:16.04.3-7
>   dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
>   Errors were encountered while processing:
>/var/cache/apt/archives/analitza-common_4%3a17.08.3-1_all.deb

Yes, I spotted this already while fixing #884015.

> during a test with piuparts ... well you should know the sermon by now :-)

Hey, a piuparts bug without the piuparts sermon is not a piuparts bug!
:-D

Thanks,
-- 
Pino Toscano

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

Bug#884015: marked as done (kalgebra-common: Kalgebra-common can't be updated in 4:17.08.3-1)

[Debian Bug Tracking System]

Your message dated Sun, 10 Dec 2017 15:49:17 +
with message-id 
and subject line Bug#884015: fixed in kalgebra 4:17.08.3-2
has caused the Debian Bug report #884015,
regarding kalgebra-common: Kalgebra-common can't be updated in 4:17.08.3-1
to be marked as done.

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

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


-- 
884015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884015
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kalgebra-common
Version: 4:16.08.3-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,
The update of kalgebra-common from 4:16.08.3-1 to 4:17.08.3-1 led to a conflict
with kde-l10n-fr 4:16.04.3-7
dpkg: erreur de traitement de l'archive /var/cache/apt/archives/kalgebra-
common_4%3a17.08.3-1_amd64.deb (--unpack) :
 tentative de remplacement de « /usr/share/locale/fr/LC_MESSAGES/kalgebra.mo »,
qui appartient aussi au paquet kde-l10n-fr 4:16.04.3-7
Sorry for the error message in french
Recently i have the same problem with kstars an it was corrected by Pino
Toscano



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

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

Versions of packages kalgebra-common depends on:
ii  plasma-framework 5.37.0-2
pn  qml-module-org-kde-analitza  

kalgebra-common recommends no packages.

kalgebra-common suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: kalgebra
Source-Version: 4:17.08.3-2

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

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

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

Debian distribution maintenance software
pp.
Pino Toscano  (supplier of updated kalgebra package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 10 Dec 2017 16:08:19 +0100
Source: kalgebra
Binary: kalgebra kalgebra-common kalgebramobile
Architecture: source
Version: 4:17.08.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Pino Toscano 
Description:
 kalgebra   - algebraic graphing calculator
 kalgebra-common - contains files common for kalgebra and kalgebramobile
 kalgebramobile - algebraic graphing calculator for small touch based interfaces
Closes: 884015
Changes:
 kalgebra (4:17.08.3-2) unstable; urgency=medium
 .
   * Team upload.
   * Adjust again l10npkgs_firstversion_ok to the fixed version of kde-
 l10n. (Closes: #884015)
Checksums-Sha1:
 7a4678271cf27b1d2e9c0a4c3a4cd742bb9608e3 2867 kalgebra_17.08.3-2.dsc
 ed85bb4d238893c4acca6e701c16721deba56690 13136 kalgebra_17.08.3-2.debian.tar.xz
 d281ce89728b47074f9db2756eca2ca614c8d1ae 19265 
kalgebra_17.08.3-2_source.buildinfo
Checksums-Sha256:
 2dcfd693ada2a5afb240e29a6a1b4f9d2380fb3765aebaf1e31ce00ca8497655 2867 
kalgebra_17.08.3-2.dsc
 b9bc24ac8debdceb842062f8184f4598da8ff8558ece2fcdb8b41a5190affcb0 13136 
kalgebra_17.08.3-2.debian.tar.xz
 8ac9f430cf4b2a053dcb3cac92ea1c8c8ec076856c2528a34580e5bdacb2d470 19265 
kalgebra_17.08.3-2_source.buildinfo
Files:
 089bebe45ff45345afe617d239d14b66 2867 kde optional kalgebra_17.08.3-2.dsc
 c7acab8ddec95261d7a8c7d8c6f16668 13136 kde optional 
kalgebra_17.08.3-2.debian.tar.xz
 c2ea38e9029f30edd6a95533eb68e977 19265 kde optional 
kalgebra_17.08.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAlotTegACgkQLRkciEOx
P00WMhAAnVe8toKT8XF/s+DjzjiXopLs+TpI1lCTVP3aed0gmwkqDqb2/d109U8/
juenXoEoLBWp82/lvwqMBlsnSRIJQW2zAJ6Hm5PlOFcxdB5QiyYPu2srFWCHsw18
Kwru3gqT7Q3T+5wE6IEior+OwqvVOyW8+eGL1xuaZ42w4nyH5sGarD36dK6yGOuI
HgFZMCqZ2s9V/lrwmhkeY0aEp828/DMeJKKa8ZAy+5MecjgC+o7U9kaqlbo7CehQ
rXIoVtMxdn2XvRNEsbjotQgPZP+aY4D8bwTxV3L6dN//8YBHqC6iEDZOJum66L2I

Bug#884026: marked as done (kalgebra-common: file conflict with kde-l10n-*: /usr/share/locale/*/LC_MESSAGES/kalgebra.mo)

[Debian Bug Tracking System]

Your message dated Sun, 10 Dec 2017 15:49:17 +
with message-id 
and subject line Bug#884015: fixed in kalgebra 4:17.08.3-2
has caused the Debian Bug report #884015,
regarding kalgebra-common: file conflict with kde-l10n-*: 
/usr/share/locale/*/LC_MESSAGES/kalgebra.mo
to be marked as done.

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

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


-- 
884015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884015
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kalgebra-common
Version: 4:17.08.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts ... well you should know the sermon by now :-)

  Selecting previously unselected package kalgebra-common.
  Preparing to unpack .../362-kalgebra-common_4%3a17.08.3-1_amd64.deb ...
  Unpacking kalgebra-common (4:17.08.3-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-w3sjeI/362-kalgebra-common_4%3a17.08.3-1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/share/locale/ar/LC_MESSAGES/kalgebra.mo', which is 
also in package kde-l10n-ar 4:16.04.3-7
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-w3sjeI/148-analitza-common_4%3a17.08.3-1_all.deb
   /tmp/apt-dpkg-install-w3sjeI/362-kalgebra-common_4%3a17.08.3-1_amd64.deb


cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: kalgebra
Source-Version: 4:17.08.3-2

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

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

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

Debian distribution maintenance software
pp.
Pino Toscano  (supplier of updated kalgebra package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 10 Dec 2017 16:08:19 +0100
Source: kalgebra
Binary: kalgebra kalgebra-common kalgebramobile
Architecture: source
Version: 4:17.08.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Pino Toscano 
Description:
 kalgebra   - algebraic graphing calculator
 kalgebra-common - contains files common for kalgebra and kalgebramobile
 kalgebramobile - algebraic graphing calculator for small touch based interfaces
Closes: 884015
Changes:
 kalgebra (4:17.08.3-2) unstable; urgency=medium
 .
   * Team upload.
   * Adjust again l10npkgs_firstversion_ok to the fixed version of kde-
 l10n. (Closes: #884015)
Checksums-Sha1:
 7a4678271cf27b1d2e9c0a4c3a4cd742bb9608e3 2867 kalgebra_17.08.3-2.dsc
 ed85bb4d238893c4acca6e701c16721deba56690 13136 kalgebra_17.08.3-2.debian.tar.xz
 d281ce89728b47074f9db2756eca2ca614c8d1ae 19265 
kalgebra_17.08.3-2_source.buildinfo
Checksums-Sha256:
 2dcfd693ada2a5afb240e29a6a1b4f9d2380fb3765aebaf1e31ce00ca8497655 2867 
kalgebra_17.08.3-2.dsc
 b9bc24ac8debdceb842062f8184f4598da8ff8558ece2fcdb8b41a5190affcb0 13136 
kalgebra_17.08.3-2.debian.tar.xz
 8ac9f430cf4b2a053dcb3cac92ea1c8c8ec076856c2528a34580e5bdacb2d470 19265 
kalgebra_17.08.3-2_source.buildinfo
Files:
 089bebe45ff45345afe617d239d14b66 2867 kde optional kalgebra_17.08.3-2.dsc
 c7acab8ddec95261d7a8c7d8c6f16668 13136 kde optional 
kalgebra_17.08.3-2.debian.tar.xz
 c2ea38e9029f30edd6a95533eb68e977 19265 kde optional 
kalgebra_17.08.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAlotTegACgkQLRkciEOx
P00WMhAAnVe8toKT8XF/s+DjzjiXopLs+TpI1lCTVP3aed0gmwkqDqb2/d109U8/
juenXoEoLBWp82/lvwqMBlsnSRIJQW2zAJ6Hm5PlOFcxdB5QiyYPu2srFWCHsw18
Kwru3gqT7Q3T+5wE6IEior+OwqvVOyW8+eGL1xuaZ42w4nyH5sGarD36dK6yGOuI
HgFZMCqZ2s9V/lrwmhkeY0aEp828/DMeJKKa8ZAy+5MecjgC+o7U9kaqlbo7CehQ
rXIoVtMxdn2XvRNEsbjotQgPZP+aY4D8bwTxV3L6dN//8YBHqC6iEDZOJum66L2I
pcgLPd0LYtYlwb7zo1oWf5aop/lk8RB1gLnlY/jrh9B5hDoTwy6ppJ5AQop6UMDx
bIQomODxI4GCkNPa1BV6NSLF0flzWM8PGB9/8e2UskGhi4CInvm6B+PCv4+JRuQc
wpBcKIW4W+5mbsXDwj3rqHqelykNHqAD9noTHKQFL6P9/yVQAJGnNt069y7mgZnD
rLlX6PAyeOAmlvzR6JJlaqXbF3SE/YuG2nR3L5N3K65FkY7aspSPTztCRYBn5r0M
EbgxapTEciZQfqx6VrGYrwHpxmHGtmnJJsTmW+NlYIz6ph4le+sD5WJHByTF1Cra
mJxPYLQIK006x2lTiDAYhfQFM//8ANQiAxsrw+p1ImGwKt4VW0U=
=KBrh
-END PGP SIGNATURE 

Processed: forcibly merging 884015 884026

[Debian Bug Tracking System]

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

> forcemerge 884015 884026
Bug #884015 [kalgebra-common] kalgebra-common: Kalgebra-common can't be updated 
in 4:17.08.3-1
Bug #884026 [kalgebra-common] kalgebra-common: file conflict with kde-l10n-*: 
/usr/share/locale/*/LC_MESSAGES/kalgebra.mo
Added tag(s) pending.
Merged 884015 884026
> thanks
Stopping processing here.

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

Bug#884026: kalgebra-common: file conflict with kde-l10n-*: /usr/share/locale/*/LC_MESSAGES/kalgebra.mo

[Andreas Beckmann]

Package: kalgebra-common
Version: 4:17.08.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts ... well you should know the sermon by now :-)

  Selecting previously unselected package kalgebra-common.
  Preparing to unpack .../362-kalgebra-common_4%3a17.08.3-1_amd64.deb ...
  Unpacking kalgebra-common (4:17.08.3-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-w3sjeI/362-kalgebra-common_4%3a17.08.3-1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/share/locale/ar/LC_MESSAGES/kalgebra.mo', which is 
also in package kde-l10n-ar 4:16.04.3-7
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-w3sjeI/148-analitza-common_4%3a17.08.3-1_all.deb
   /tmp/apt-dpkg-install-w3sjeI/362-kalgebra-common_4%3a17.08.3-1_amd64.deb


cheers,

Andreas

Processed: tagging 884025

[Debian Bug Tracking System]

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

> tags 884025 + pending
Bug #884025 [analitza-common] analitza-common: file conflict with kde-l10n-*: 
/usr/share/locale/*/LC_MESSAGES/analitza_qt.qm
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#884025: analitza-common: file conflict with kde-l10n-*: /usr/share/locale/*/LC_MESSAGES/analitza_qt.qm

[Andreas Beckmann]

Package: analitza-common
Version: 4:17.08.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts ... well you should know the sermon by now :-)

  Selecting previously unselected package analitza-common.
  Preparing to unpack .../analitza-common_4%3a17.08.3-1_all.deb ...
  Unpacking analitza-common (4:17.08.3-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/analitza-common_4%3a17.08.3-1_all.deb (--unpack):
   trying to overwrite '/usr/share/locale/ar/LC_MESSAGES/analitza_qt.qm', which 
is also in package kde-l10n-ar 4:16.04.3-7
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/analitza-common_4%3a17.08.3-1_all.deb


cheers,

Andreas

Bug#883976: marked as done (nfs-common: Shell script executed by systemd to mount net /home * /var fails)

[Debian Bug Tracking System]

Your message dated Sun, 10 Dec 2017 15:21:14 +
with message-id <1512919274.2723.4.ca...@decadent.org.uk>
and subject line Re: Bug#883976: nfs-common: Shell script executed by systemd 
to mount net /home * /var fails
has caused the Debian Bug report #883976,
regarding nfs-common: Shell script executed by systemd to mount net /home * 
/var fails
to be marked as done.

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

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


-- 
883976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883976
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nfs-common
Version: 1:1.3.4-2.1
Severity: grave
Justification: renders package unusable

Netboot file system on /devnfs (except that dev/nfs causes errors) so rootfs is 
mounted per fstab.
Trying to mount nfs file system for var and home and the mount fails.

When linux is fully up, and I'm logged into a user, su to root
the file systems can be mounted with no error message.

Why during boot are the messages:

mount: can't find 192.168.1.10:/nsfroot/b827eb/c23849/var  /var in /etc/fstab
mount: can't find 192.168.1.10:/nsfroot/b827eb/c23849/home /home in /etc/fstab

being generated as though the root id during boot is a normal unprivilaged 
unser?

fstab:

proc /proc   procdefaults   
0 0
/dev/mmcblk0p1   /boot   vfatdefaults,ro
0 2
#PARTUUID=62bc0a1f-02/   ext4defaults,noatime   
0 1
192.168.1.10:/nfsroot/r.32.test  /   nfs defaults,rw
0 0
#192.168.1.10:/nfsroot/b827eb/c23849/var  /var   nfs defaults,rw
0 0
#192.168.1.10:/nfsroot/b827eb/c23849/home /home   nfs defaults,rw   
 0 0
#browne:/nfsroot/b827eb/c23849/home  /home   nfs defaults,rw
0 0
tmpfs/tmptmpfs   
nodev,nosuid,size=1%,mode=1777 0 0

systemctl unit:

[Unit]
Description=Setup directory tree in var filesystem
DefaultDependencies=no
After=local-fs.target
Before=basic.target

[Service]
Type=oneshot
ExecStart=/usr/bin/setup-var-home.sh

[Install]
WantedBy=basic.target

hostname:
b827ebc23849

/usr/bin/setup-var-home.sh:
#!/bin/bash
H=$(hostname);
#H="b827ebc23849";
/bin/mount 192.168.1.10:/nsfroot/${H:0:-6}"/"${H:6:12}"/var  /var";
/bin/mount 192.168.1.10:/nsfroot/${H:0:-6}"/"${H:6:12}"/home /home";

systemctl status

● setup-var-home.service - Setup directory tree in var filesystem
   Loaded: loaded (/lib/systemd/system/setup-var-home.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Sat 2017-12-09 13:43:43 PST; 22min 
ago
  Process: 267 ExecStart=/usr/bin/setup-var-home.sh (code=exited, 
status=1/FAILURE)
 Main PID: 267 (code=exited, status=1/FAILURE)

Dec 09 13:43:42 b827ebc23849 systemd[1]: Starting Setup directory tree in var 
filesystem...
Dec 09 13:43:43 b827ebc23849 setup-var-home.sh[267]: mount: can't find 
192.168.1.10:/nsfroot/b827eb/c23849/var  /var in /etc/fstab
Dec 09 13:43:43 b827ebc23849 setup-var-home.sh[267]: mount: can't find 
192.168.1.10:/nsfroot/b827eb/c23849/home /home in /etc/fstab
Dec 09 13:43:43 b827ebc23849 systemd[1]: setup-var-home.service: Main process 
exited, code=exited, status=1/FAILURE
Dec 09 13:43:43 b827ebc23849 systemd[1]: Failed to start Setup directory tree 
in var filesystem.
Dec 09 13:43:43 b827ebc23849 systemd[1]: setup-var-home.service: Unit entered 
failed state.
Dec 09 13:43:43 b827ebc23849 systemd[1]: setup-var-home.service: Failed with 
result 'exit-code'.

mount command output

192.168.1.10:/nfsroot/r.32.test on / type nfs 
(rw,relatime,vers=3,rsize=4096,wsize=4096,namlen=255,hard,nolock,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.10,mountvers=3,mountp$
devtmpfs on /dev type devtmpfs 
(rw,relatime,size=405220k,nr_inodes=101305,mode=755)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/cpuset type 

Bug#879857: xserver-xorg-video-intel: [i915] GPU hang after every suspend or hibernate on Debian 9 stretch

[Ferdinand Rau]

Dear Maintainer,

There are reports that this issue is resolved when using the same version of 
xserver-xorg-video-intel, but another kernel version. Therefore, I now assume 
that this issue is caused by a kernel bug, not a bug in your package.

I filed a new bug report against src:linux here:
https://bugs.debian.org/883935

I will post any updates or new information there. Feel free to close this bug 
any time.

Kind regards,
Ferdinand

Processed: Re: nyquist FTBFS with gcc 7: undefined references

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #878318 [src:nyquist] nyquist FTBFS with gcc 7: undefined references
Added tag(s) patch.

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

Bug#878318: nyquist FTBFS with gcc 7: undefined references

[Juhani Numminen]

Control: tags -1 patch

Juhani Numminen kirjoitti 04.12.2017 klo 00:39:


A FreeBSD bug from 2012 looks similar, there the fix was
s|inline void|static inline void|.[1]
That change entered upstream repository earlier in 2012.[2]
Debian's version doesn't have it.[3]


A patch is attached. Build was successful using cowbuilder, sid i386.

Juhani
Description: Fix FTBFS with gcc 7: undefined references
Origin: https://sourceforge.net/p/nyquist/code/73/tree/trunk/nyquist/ffts/src/fftlib.c?diff=50d0ad1227184648a86e886f:72
Author: Roger B. Dannenberg 
Bug-Debian: https://bugs.debian.org/878318
Bug-FreeBSD: https://bugs.freebsd.org/174376
Last-Update: 2017-12-10

--- a/ffts/src/fftlib.c
+++ b/ffts/src/fftlib.c
@@ -1,6 +1,8 @@
 /***
 lower level fft stuff including routines called in fftext.c and fft2d.c
 ***/
+/* inline declarations modified by RBD for C99 compiler */
+
 #include "fftlib.h"
 #include 
 #define	MCACHE	(11-(sizeof(float)/8))	// fft's with M bigger than this bust primary cache
@@ -61,8 +63,8 @@
 parts of ffts1
 */
 
-inline void bitrevR2(float *ioptr, long M, short *BRLow);
-inline void bitrevR2(float *ioptr, long M, short *BRLow){
+//inline void bitrevR2(float *ioptr, long M, short *BRLow);
+static inline void bitrevR2(float *ioptr, long M, short *BRLow){
 /*** bit reverse and first radix 2 stage of forward or inverse fft ***/
 float	f0r;
 float	f0i;
@@ -198,8 +200,8 @@
 };
 }
 
-inline void fft2pt(float *ioptr);
-inline void fft2pt(float *ioptr){
+//inline void fft2pt(float *ioptr);
+static inline void fft2pt(float *ioptr){
 /***   RADIX 2 fft	***/
 float f0r, f0i, f1r, f1i;
 float t0r, t0i;
@@ -229,8 +231,8 @@
 }
 
 
-inline void fft4pt(float *ioptr);
-inline void fft4pt(float *ioptr){
+//inline void fft4pt(float *ioptr);
+static inline void fft4pt(float *ioptr){
 /***   RADIX 4 fft	***/
 float f0r, f0i, f1r, f1i, f2r, f2i, f3r, f3i;
 float t0r, t0i, t1r, t1i;
@@ -284,8 +286,8 @@
 ioptr[7] = f3i;
 }
 
-inline void fft8pt(float *ioptr);
-inline void fft8pt(float *ioptr){
+//inline void fft8pt(float *ioptr);
+static inline void fft8pt(float *ioptr){
 /***   RADIX 8 fft	***/
 float w0r = 1.0/MYROOT2; /* cos(pi/4)	*/
 float f0r, f0i, f1r, f1i, f2r, f2i, f3r, f3i;
@@ -403,8 +405,8 @@
 ioptr[15] = f6i;
 }
 
-inline void bfR2(float *ioptr, long M, long NDiffU);
-inline void bfR2(float *ioptr, long M, long NDiffU){
+//inline void bfR2(float *ioptr, long M, long NDiffU);
+static inline void bfR2(float *ioptr, long M, long NDiffU){
 /*** 2nd radix 2 stage ***/
 unsigned long	pos;
 unsigned long	posi;
@@ -512,8 +514,8 @@
 }
 }
 
-inline void bfR4(float *ioptr, long M, long NDiffU);
-inline void bfR4(float *ioptr, long M, long NDiffU){
+//inline void bfR4(float *ioptr, long M, long NDiffU);
+static inline void bfR4(float *ioptr, long M, long NDiffU){
 /*** 1 radix 4 stage ***/
 unsigned long	pos;
 unsigned long	posi;
@@ -721,8 +723,8 @@
 
 }
 
-inline void bfstages(float *ioptr, long M, float *Utbl, long Ustride, long NDiffU, long StageCnt);
-inline void bfstages(float *ioptr, long M, float *Utbl, long Ustride, long NDiffU, long StageCnt){
+// inline void bfstages(float *ioptr, long M, float *Utbl, long Ustride, long NDiffU, long StageCnt);
+static inline void bfstages(float *ioptr, long M, float *Utbl, long Ustride, long NDiffU, long StageCnt){
 /***   RADIX 8 Stages	***/
 unsigned long	pos;
 unsigned long	posi;
@@ -1125,8 +1127,8 @@
 parts of iffts1
 */
 
-inline void scbitrevR2(float *ioptr, long M, short *BRLow, float scale);
-inline void scbitrevR2(float *ioptr, long M, short *BRLow, float scale){
+// inline void scbitrevR2(float *ioptr, long M, short *BRLow, float scale);
+static inline void scbitrevR2(float *ioptr, long M, short *BRLow, float scale){
 /*** scaled bit reverse and first radix 2 stage forward or inverse fft ***/
 float	f0r;
 float	f0i;
@@ -1262,8 +1264,8 @@
 };
 }
 
-inline void ifft2pt(float *ioptr, float scale);
-inline void ifft2pt(float *ioptr, float scale){
+//inline void ifft2pt(float *ioptr, float scale);
+static inline void ifft2pt(float *ioptr, float scale){
 /***   RADIX 2 ifft	***/
 float f0r, f0i, f1r, f1i;
 float t0r, t0i;
@@ -1292,8 +1294,8 @@
 ioptr[3] = scale*f1i;
 }
 
-inline void ifft4pt(float *ioptr, float scale);
-inline void ifft4pt(float *ioptr, float scale){
+// inline void ifft4pt(float *ioptr, float scale);
+static inline void ifft4pt(float *ioptr, float scale){
 /***   RADIX 4 ifft	***/
 float f0r, f0i, f1r, f1i, f2r, f2i, f3r, f3i;
 float t0r, t0i, t1r, t1i;
@@ -1347,8 +1349,8 @@
 ioptr[7] = scale*f3i;
 }
 
-inline void ifft8pt(float *ioptr, float scale);
-inline void ifft8pt(float *ioptr, float scale){
+//inline void ifft8pt(float *ioptr, float scale);
+static inline void ifft8pt(float *ioptr, float scale){
 

Processed: severity of 884015 is serious, tagging 884015

[Debian Bug Tracking System]

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

> severity 884015 serious
Bug #884015 [kalgebra-common] kalgebra-common: Kalgebra-common can't be updated 
in 4:17.08.3-1
Severity set to 'serious' from 'grave'
> tags 884015 + pending
Bug #884015 [kalgebra-common] kalgebra-common: Kalgebra-common can't be updated 
in 4:17.08.3-1
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#884023: bibledit: Installs same file as bibledit-gtk

[Jeremy Bicha]

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

Bug#884022: kcachegrind: FTBFS with recent Qt5: Could not find a package configuration file provided by "Qt5LinguistTools"

[Andreas Beckmann]

Source: kcachegrind
Version: 4:17.08.1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

kcachegrind/experimental recently started to FTBFS:

 debian/rules build
/usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.pl --with=kf5,pkgkde-symbolshelper 
dpkg-buildflags --export=make > debian/dhmk_env.mk
/usr/bin/make -f debian/rules dhmk_run_configure_commands 
DHMK_TARGET="configure"
make[1]: Entering directory '/build/kcachegrind-17.08.1'
dh_testdir  
dh_auto_configure '--buildsystem=kf5' --parallel  
cd obj-i686-linux-gnu && cmake .. -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAG
E_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_BUILD_TYPE=Debian -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DKDE_INSTALL_USE_QT_SYS_PATHS=ON
-- The C compiler identification is GNU 7.2.1
-- The CXX compiler identification is GNU 7.2.1
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Could not set up the appstream test. appstreamcli is missing.
-- Looking for __GLIBC__
-- Looking for __GLIBC__ - found
-- Performing Test _OFFT_IS_64BIT
-- Performing Test _OFFT_IS_64BIT - Failed
-- Performing Test HAVE_DATE_TIME
-- Performing Test HAVE_DATE_TIME - Success
-- Found KF5Archive: 
/usr/lib/i386-linux-gnu/cmake/KF5Archive/KF5ArchiveConfig.cmake (found version 
"5.37.0") 
-- Found KF5CoreAddons: 
/usr/lib/i386-linux-gnu/cmake/KF5CoreAddons/KF5CoreAddonsConfig.cmake (found 
version "5.37.0") 
-- Found KF5DocTools: 
/usr/lib/i386-linux-gnu/cmake/KF5DocTools/KF5DocToolsConfig.cmake (found 
version "5.37.0") 
-- Found KF5WidgetsAddons: 
/usr/lib/i386-linux-gnu/cmake/KF5WidgetsAddons/KF5WidgetsAddonsConfig.cmake 
(found version "5.37.0") 
-- Found KF5XmlGui: 
/usr/lib/i386-linux-gnu/cmake/KF5XmlGui/KF5XmlGuiConfig.cmake (found version 
"5.37.0") 
-- Found Gettext: /usr/bin/msgmerge (found version "0.19.8.1") 
-- Found PythonInterp: /usr/bin/python (found version "2.7.14") 
-- Found KF5I18n: /usr/lib/i386-linux-gnu/cmake/KF5I18n/KF5I18nConfig.cmake 
(found version "5.37.0") 
-- Found KF5Config: 
/usr/lib/i386-linux-gnu/cmake/KF5Config/KF5ConfigConfig.cmake (found version 
"5.37.0") 
-- Found KF5KIO: /usr/lib/i386-linux-gnu/cmake/KF5KIO/KF5KIOConfig.cmake (found 
version "5.37.0") 
-- Found KF5: success (found version "5.37.0") found components:  Archive 
CoreAddons DocTools WidgetsAddons XmlGui I18n Config KIO 
-- The following REQUIRED packages have been found:

 * ECM (required version >= 1.7.0)
 * Qt5Core
 * Qt5DBus
 * Qt5Gui
 * Qt5Widgets
 * Qt5 (required version >= 5.2.0)
 * KF5Archive
 * KF5CoreAddons
 * KF5DocTools
 * KF5WidgetsAddons
 * KF5XmlGui
 * Gettext
 * PythonInterp
 * KF5I18n
 * KF5Config
 * KF5KIO
 * KF5

CMake Error at /usr/share/ECM/modules/ECMPoQmTools.cmake:144 (find_package):
  Could not find a package configuration file provided by "Qt5LinguistTools"
  with any of the following names:

Qt5LinguistToolsConfig.cmake
qt5linguisttools-config.cmake

  Add the installation prefix of "Qt5LinguistTools" to CMAKE_PREFIX_PATH or
  set "Qt5LinguistTools_DIR" to a directory containing one of the above
  files.  If "Qt5LinguistTools" provides a separate development package or
  SDK, be sure it has been installed.
Call Stack (most recent call first):
  /usr/share/ECM/modules/ECMPoQmTools.cmake:220 (ecm_process_po_files_as_qm)
  CMakeLists.txt:57 (ecm_install_po_files_as_qm)


-- Configuring incomplete, errors occurred!


Andreas


kcachegrind_4%17.08.1-1.log.gz
Description: application/gzip

Processed: Version fix

[Debian Bug Tracking System]

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

> notfound 884015 4:16.08.3-1
Bug #884015 [kalgebra-common] kalgebra-common: Kalgebra-common can't be updated 
in 4:17.08.3-1
No longer marked as found in versions kalgebra/4:16.08.3-1.
> found 884015 4:17.08.3-1
Bug #884015 [kalgebra-common] kalgebra-common: Kalgebra-common can't be updated 
in 4:17.08.3-1
Marked as found in versions kalgebra/4:17.08.3-1.
> thanks
Stopping processing here.

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

Bug#884019: terminology: FTBFS if $HOME is not writable

[Andreas Beckmann]

Source: terminology
Version: 1.1.1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

same problem as in e17:

make[6]: Entering directory '/build/terminology-1.1.1/data/themes/nyanology'
/usr/bin/edje_cc  -id ../../../data/themes/nyanology/images -id 
../../../data/themes/images -fd ../../../data/fonts -sd 
../../../data/themes/sounds \
../../../data/themes/nyanology/nyanology.edc \
../../../data/themes/nyanology/nyanology.edj
FATAL: Cannot create run dir '/nonexistent/.run' - errno=2
Makefile:692: recipe for target 'nyanology.edj' failed
make[6]: *** [nyanology.edj] Aborted
make[6]: Leaving directory '/build/terminology-1.1.1/data/themes/nyanology'


Andreas


terminology_1.1.1-1.log.gz
Description: application/gzip

Bug#883938: Sun Fire X4200 M2 too

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

Hi,

Reproduced it on a Sun Fire X4200 M2 too, screenshot attached.

Could we increase the severity to critical like Debian bug #883294? It downed a 
production server ;(

Downgrading to "3.16.43-2+deb8u5 (2017-09-19)" fixed it.

Elmar

Bug#884018: yamcha: FTBFS with debhelper >= 10.9.2: dh_systemd_enable is no longer used in compat >= 11, please use dh_installsystemd instead

[Andreas Beckmann]

Source: yamcha
Version: 0.33-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

yamcha FTBFS since debhelper changed w.r.t. systemd handling:

dh_systemd_enable -pyamcha 
dh_systemd_enable: dh_systemd_enable is no longer used in compat >= 11, please 
use dh_installsystemd instead
/usr/share/cdbs/1/rules/debhelper.mk:233: recipe for target 
'binary-install/yamcha' failed
make: *** [binary-install/yamcha] Error 25


Andreas


yamcha_0.33-2.log.gz
Description: application/gzip

Bug#878498: snakemake FTBFS with Python 3.6 as default

[chrysn]

On Fri, Dec 08, 2017 at 09:18:42AM +0100, Andreas Tille wrote:
> The problem is that when trying to build this I get a lot of errors in
> the build time tests.  Is there any volunteer to have a look?

I've started with the tests more or less at random, and the second seems
to be promising to solve most of them:

* test_delete_output is IMO an upstream bug that only triggers when
  SHELL does not try to be POSIX compatible (why should it unless
  invoked as `sh`), eg. when SHELL=zsh.

  There are 3 more that fail even when run locally w/o any Debian
  modifications, so we might need to mask them or apply any of the
  workarounds. (Postponed that until the big ones are done).

* The noop-rate-limiter workaround I introduced earlier to be able to
  work on the other issues of the new version doesn't work right now.
  Before I spend any more time fixing a workaround, I'll go ahead and
  ITP python3-ratelimiter [880661] -- with that workaround in place, we
  shouldn't release an updated snakemake anyway.

If the delay introduced by ratelimiter (even with me getting packaging
done "immediately" and follow-up sponsorship from DPMT, this will need
to go through NEW.

Best regards
chrysn

[1]: 
https://bitbucket.org/snakemake/snakemake/issues/722/tests-fail-when-shell-is-zsh-and-not-bash
[880661]: https://bugs.debian.org/880661

-- 
To use raw power is to make yourself infinitely vulnerable to greater powers.
  -- Bene Gesserit axiom


signature.asc
Description: PGP signature

Bug#884015: kalgebra-common: Kalgebra-common can't be updated in 4:17.08.3-1

[merlin]

Package: kalgebra-common
Version: 4:16.08.3-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,
The update of kalgebra-common from 4:16.08.3-1 to 4:17.08.3-1 led to a conflict
with kde-l10n-fr 4:16.04.3-7
dpkg: erreur de traitement de l'archive /var/cache/apt/archives/kalgebra-
common_4%3a17.08.3-1_amd64.deb (--unpack) :
 tentative de remplacement de « /usr/share/locale/fr/LC_MESSAGES/kalgebra.mo »,
qui appartient aussi au paquet kde-l10n-fr 4:16.04.3-7
Sorry for the error message in french
Recently i have the same problem with kstars an it was corrected by Pino
Toscano



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

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

Versions of packages kalgebra-common depends on:
ii  plasma-framework 5.37.0-2
pn  qml-module-org-kde-analitza  

kalgebra-common recommends no packages.

kalgebra-common suggests no packages.

-- no debconf information

Bug#877840: marked as pending

[Ondřej Nový]

tag 877840 pending
thanks

Hello,

Bug #877840 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


https://anonscm.debian.org/cgit/openstack/clients/python-magnumclient.git/commit/?id=b01c07e

---
commit b01c07e9159236b57bffa303ddb86a423d226a0d
Author: Ondřej Nový 
Date:   Sun Dec 10 14:49:52 2017 +0100

Add B-D on python{,3}-openstackclient (Closes: #877840)

diff --git a/debian/changelog b/debian/changelog
index 2e79277..39ac8bd 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+python-magnumclient (2.7.0-4) UNRELEASED; urgency=medium
+
+  * Team upload.
+  * Add B-D on python{,3}-openstackclient (Closes: #877840)
+
+ -- Ondřej Nový   Sun, 10 Dec 2017 14:48:11 +0100
+
 python-magnumclient (2.7.0-3) unstable; urgency=medium
 
   * Uploading to unstable.

Processed: Bug#877840 marked as pending

[Debian Bug Tracking System]

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

> tag 877840 pending
Bug #877840 [src:python-magnumclient] python-magnumclient: FTBFS  ImportError: 
No module named oslo_log, openstackclient.tests.unit
Ignoring request to alter tags of bug #877840 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#883938: linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51

[Dominic Benson]

I encountered this on an old Intel SR1600 box with Westmere Xeons.

I have an Ivy Bridge E5-1620v2 physical box that has booted successfully
with this kernel, and I haven't seen any problem among the dozen or so
VMs that have so far rebooted onto it (VMware ESXi 6.0/6.5, on dual E5
Xeon Sandy Bridge/Ivy Bridge/Haswell/Broadwell).

As with previous reporters, reverting to 3.16.43-2+deb8u5 avoids the
problem.

Details of the problematic system as follows:

** Command line:
BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64 root=/dev/mapper/raid1-root ro quiet

** Tainted: I (2048)
 * Working around severe firmware bug.

** Kernel log:
[    5.810814] ioatdma :00:16.4: irq 95 for MSI/MSI-X
[    5.811126] ioatdma :00:16.5: irq 96 for MSI/MSI-X
[    5.811438] ioatdma :00:16.6: irq 97 for MSI/MSI-X
[    5.811752] ioatdma :00:16.7: irq 98 for MSI/MSI-X
[    5.875627] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[    5.913072] ipmi message handler version 39.2
[    5.950042] EDAC MC: Ver: 3.0.0
[    5.962572] input: Sleep Button as
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0
[    5.962578] ACPI: Sleep Button [SLPB]
[    5.962625] input: Power Button as
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
[    5.962627] ACPI: Power Button [PWRF]
[    5.974649] SSE version of gcm_enc/dec engaged.
[    5.978346] alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni)
[    6.022862] EDAC MC1: Giving out device to module i7core_edac.c
controller i7 core #1: DEV :fe:03.0 (POLLED)
[    6.022894] EDAC PCI0: Giving out device to module i7core_edac
controller EDAC PCI controller: DEV :fe:03.0 (POLLED)
[    6.023304] EDAC MC0: Giving out device to module i7core_edac.c
controller i7 core #0: DEV :ff:03.0 (POLLED)
[    6.023329] EDAC PCI1: Giving out device to module i7core_edac
controller EDAC PCI controller: DEV :ff:03.0 (POLLED)
[    6.023600] EDAC i7core: Driver loaded, 2 memory controller(s) found.
[    6.062760] cdc_acm 7-1:1.0: This device cannot do calls on its own.
It is not a modem.
[    6.062885] cdc_acm 7-1:1.0: ttyACM0: USB ACM device
[    6.064546] usbcore: registered new interface driver cdc_acm
[    6.064549] cdc_acm: USB Abstract Control Model driver for USB modems
and ISDN adapters
[    6.072093] IPMI System Interface driver.
[    6.072121] ipmi_si: probing via ACPI
[    6.072143] ipmi_si 00:02: [io  0x0ca2] regsize 1 spacing 1 irq 0
[    6.072144] ipmi_si: Adding ACPI-specified kcs state machine
[    6.072156] ipmi_si: probing via SMBIOS
[    6.072158] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
[    6.072159] ipmi_si: Adding SMBIOS-specified kcs state machine
duplicate interface
[    6.072161] ipmi_si: Trying ACPI-specified kcs state machine at i/o
address 0xca2, slave address 0x0, irq 0
[    6.122134] input: PC Speaker as /devices/platform/pcspkr/input/input2
[    6.215855] ipmi_si 00:02: Found new BMC (man_id: 0x000157, prod_id:
0x003e, dev_id: 0x21)
[    6.215869] ipmi_si 00:02: IPMI kcs interface initialized
[    6.639127] hidraw: raw HID events driver (C) Jiri Kosina
[    6.727507] alg: No test for crc32 (crc32-pclmul)
[    6.853789] iTCO_vendor_support: vendor-support=0
[    6.857666] usbcore: registered new interface driver usbhid
[    6.857668] usbhid: USB HID core driver
[    6.885272] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[    6.885304] iTCO_wdt: unable to reset NO_REBOOT flag, device disabled
by hardware/BIOS
[    6.911461] [drm] Initialized drm 1.1.0 20060810
[    6.995935] input: Dell Dell USB Keyboard as
/devices/pci:00/:00:1a.1/usb4/4-1/4-1:1.0/0003:413C:2003.0001/input/input3
[    6.996179] hid-generic 0003:413C:2003.0001: input,hidraw0: USB HID
v1.10 Keyboard [Dell Dell USB Keyboard] on usb-:00:1a.1-1/input0
[    6.996349] input: American Megatrends Inc. Virtual Keyboard and
Mouse as
/devices/pci:00/:00:1a.2/usb5/5-1/5-1:1.0/0003:046B:FF10.0002/input/input4
[    6.996455] hid-generic 0003:046B:FF10.0002: input,hidraw1: USB HID
v1.10 Keyboard [American Megatrends Inc. Virtual Keyboard and Mouse] on
usb-:00:1a.2-1/input0
[    6.996622] input: American Megatrends Inc. Virtual Keyboard and
Mouse as
/devices/pci:00/:00:1a.2/usb5/5-1/5-1:1.1/0003:046B:FF10.0003/input/input5
[    6.996956] hid-generic 0003:046B:FF10.0003: input,hidraw2: USB HID
v1.10 Mouse [American Megatrends Inc. Virtual Keyboard and Mouse] on
usb-:00:1a.2-1/input1
[    7.014469] kvm: VM_EXIT_LOAD_IA32_PERF_GLOBAL_CTRL does not work
properly. Using workaround
[    7.565424] Adding 11717628k swap on /dev/sdb5.  Priority:-1
extents:1 across:11717628k FS
[    8.905845] XFS (dm-1): Mounting V4 Filesystem
[    8.921306] XFS (dm-2): Mounting V4 Filesystem
[    9.319538] XFS (dm-4): Mounting V4 Filesystem
[    9.484788] XFS (dm-5): Mounting V4 Filesystem
[    9.564591] XFS (dm-5): Starting recovery (logdev: internal)
[    9.666941] XFS (dm-5): Ending recovery (logdev: internal)
[    9.696815] XFS (dm-6): Mounting V4 Filesystem
[    9.718313]