Processed (with 9 errors): Re: Bug#850887: To the right bug this time: Why do you want us to keep this open?

[Debian Bug Tracking System]

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

> clone 851412 -1
Bug #851412 [src:systemd] FTBFS on mips*, tests fail with SIGSEGV
Bug #851505 [src:systemd] Xvfb segfaults on mips64el
Bug #851549 [src:systemd] dbus: Segmentation fault in dbus.postinst on mips64el
Bug #851642 [src:systemd] perl: FTBFS on mips64el: dist/threads/t/join.t failure
Failed to clone 851412: Bug is marked as being merged with others. Use an 
existing clone.

> reassign -1 binutils
Failed to clear fixed versions and reopen on -1: The 'bug' parameter ("-1") to 
Debbugs::Control::set_package did not pass regex check
.

> forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=21054
Failed to set the forwarded-to-address of -1: The 'bug' parameter ("-1") to 
Debbugs::Control::set_forwarded did not pass regex check
.

> retitle -1 Forced local symbol rearranging messes up GOT
Failed to set the title of -1: The 'bug' parameter ("-1") to 
Debbugs::Control::set_title did not pass regex check
.

> Hi James
Unknown command or malformed arguments to command.
> Am 17.01.2017 um 12:18 schrieb James Cowgill:
Unknown command or malformed arguments to command.
> > On 17/01/17 09:10, Michael Biebl wrote:
Unknown command or malformed arguments to command.
> >> Am 17.01.2017 um 10:02 schrieb Michael Biebl:
Unknown command or malformed arguments to command.
> >>> Hi there,
Unknown command or malformed arguments to command.
Too many unknown commands, stopping here.

Please contact me if you need assistance.
-- 
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#851412: Bug#850887: To the right bug this time: Why do you want us to keep this open?

[Michael Biebl]

clone 851412 -1
reassign -1 binutils
forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=21054
retitle -1 Forced local symbol rearranging messes up GOT

Hi James

Am 17.01.2017 um 12:18 schrieb James Cowgill:
> On 17/01/17 09:10, Michael Biebl wrote:
>> Am 17.01.2017 um 10:02 schrieb Michael Biebl:
>>> Hi there,
>>>
>>> as additional input, please have a look at [1] which just recently
>>> popped up. There seem to be still unresolved issues with binutils on
>>> mips*.
>>
>> I haven't reassigned this bug report to binutils yet, as I wanted to
>> have confirmation from the mips porters that it's a binutils bug.
>> They sort-of already confirmed it on IRC but wanted to look into it more
>> closely first. In any case, I've CCed them, so maybe they can respond to
>> #850887 or #851412
> 
> I had a closer look yesterday and it looks like a bug in the gold
> linker. You may be able to workaround it by using the bfd linker on mips.
> 
> Upstream bug:
> https://sourceware.org/bugzilla/show_bug.cgi?id=21054

Thanks a lot for your input and for having a look at this issue.
We had a discussion on #debian-release, which I'm quoting for
completeness sake:

 aurel32: are we sure systemd is the only package affected by this?
 mbiebl: no it's not only systemd
 mbiebl: there are some conditions to have the issue, which is
to use the gold linker
 so that's not that many packages given bfd is the default
 in addition you need to have symbols with hidden visibility
 so clearly we'll have to rebuild a few packages when it's
fixed on the binutils side, but we don't have 2.5 weeks of binaries
 aurel32: can we easily compile a list of "gold linker" consumers?
 mbiebl: i think having the workaround in systemd will help to
not accumulate too much packages in the queue
 aurel32: I guess as a first step, I'll clone the current
systemd bug and reassign it binutils
 nthykier: 1) we can parse the build logs from the last 3 weeks
 nthykier: 2) i think there is a way to identify the broken
binaries
 aurel32: and I'll apply the workaround for systemd
 mbiebl: ok, thanks
 ifneq ($(filter $(DEB_BUILD_ARCH), mips mipsel mips64el),)
 export DEB_LDFLAGS_MAINT_APPEND = -Wl,-fuse-ld=bfd
 endif
 does that look ok?
 it looks fine to me


We plan on uploading src:systemd today with this workaround applied
until binutils is properly fixed.

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




signature.asc
Description: OpenPGP digital signature

Bug#851235: [debian-mysql] Bug#851235: Bug#851235: Security fixes from the January 2017 CPU

[Lars Tangvald]

CVE List for 5.7:

CVE-2016-8318
CVE-2016-8327
CVE-2017-3238
CVE-2017-3244
CVE-2017-3251
CVE-2017-3256
CVE-2017-3257
CVE-2017-3258
CVE-2017-3265
CVE-2017-3273
CVE-2017-3291
CVE-2017-3312
CVE-2017-3313
CVE-2017-3317
CVE-2017-3318
CVE-2017-3319
CVE-2017-3320

--
Lars
On 01/17/2017 09:48 PM, Lars Tangvald wrote:

I've built and tested the updates, and will pass debdiffs on to the security 
team once the CVE list is available.

--
Lars
- norvald.ry...@oracle.com wrote:


Source: mysql-5.7
Version: 5.7.16-2
Severity: grave
Tags: security upstream fixed-upstream

The Oracle Critical Patch Update for January 2017 will be released on

Tuesday, January 17. According to the pre-release announcement [1], it
  
will contain information about CVEs fixed in MySQL 5.7.17.


The CVE numbers will be available when the CPU is released.

Regards,

Norvald H. Ryeng

[1]
http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html

___
pkg-mysql-maint mailing list
pkg-mysql-ma...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint

___
pkg-mysql-maint mailing list
pkg-mysql-ma...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint

Bug#851234: [debian-mysql] Bug#851234: Bug#851234: Security fixes from the January 2017 CPU

[Lars Tangvald]

CVE List for 5.6:

CVE-2016-8318
CVE-2016-8327
CVE-2017-3238
CVE-2017-3244
CVE-2017-3257
CVE-2017-3258
CVE-2017-3265
CVE-2017-3273
CVE-2017-3291
CVE-2017-3312
CVE-2017-3313
CVE-2017-3317
CVE-2017-3318

--
Lars
On 01/17/2017 09:48 PM, Lars Tangvald wrote:

I've built and tested the update, and will pass debdiffs on to the security 
team once the CVE list is available.

--
Lars
- norvald.ry...@oracle.com wrote:


Source: mysql-5.6
Version: 5.6.34-1
Severity: grave
Tags: security upstream fixed-upstream

The Oracle Critical Patch Update for January 2017 will be released on

Tuesday, January 17. According to the pre-release announcement [1], it
  
will contain information about CVEs fixed in MySQL 5.6.35.


The CVE numbers will be available when the CPU is released.

Regards,

Norvald H. Ryeng

[1]
http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html

___
pkg-mysql-maint mailing list
pkg-mysql-ma...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint

___
pkg-mysql-maint mailing list
pkg-mysql-ma...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint

Bug#851233: [debian-mysql] Bug#851233: Security fixes from the January 2017 CPU

[Lars Tangvald]

CVE List for 5.5:

CVE-2017-3238
CVE-2017-3243
CVE-2017-3244
CVE-2017-3258
CVE-2017-3265
CVE-2017-3291
CVE-2017-3312
CVE-2017-3313
CVE-2017-3317
CVE-2017-3318

--
Lars
On 01/13/2017 09:19 AM, Norvald H. Ryeng wrote:

Source: mysql-5.5
Version: 5.5.53-0+deb8u1
Severity: grave
Tags: security upstream fixed-upstream

The Oracle Critical Patch Update for January 2017 will be released on
Tuesday, January 17. According to the pre-release announcement [1], it
will contain information about CVEs fixed in MySQL 5.5.54.

The CVE numbers will be available when the CPU is released.

Regards,

Norvald H. Ryeng

[1] http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html

___
pkg-mysql-maint mailing list
pkg-mysql-ma...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint

Bug#851634: Confirmed

[Francisco José Rodríguez Bogado]

I can confirm this bug and both workaround: add double-quote to line 21 
and launch with --enable-remote-extensions. That solves the problem.

Processed: tagging 851412

[Debian Bug Tracking System]

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

> tags 851412 + pending
Bug #851412 [src:systemd] FTBFS on mips*, tests fail with SIGSEGV
Bug #851505 [src:systemd] Xvfb segfaults on mips64el
Bug #851549 [src:systemd] dbus: Segmentation fault in dbus.postinst on mips64el
Bug #851642 [src:systemd] perl: FTBFS on mips64el: dist/threads/t/join.t failure
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#851412: FTBFS on mips*, tests fail with SIGSEGV

[YunQiang Su]

On Sun, Jan 15, 2017 at 1:15 AM, Michael Biebl  wrote:
> Am 14.01.2017 um 18:02 schrieb Michael Biebl:
>
>> binutils_2.27.90.20170114-1. Building in stretch chroot though was
>> successful. So my observation is:
>>
>> binutils_2.27.90.20170114-1: fails
>> binutils_2.27.90.20170113-1: fails
>> binutils_2.27.51.20161220-1: ok
>>
>> So it looks like a mips related regression in binutils at a first
>> glance. In the past, systemd built reasonably reliably on mips* [3].
>
> A notable difference (aside from binutils) between the sid and stretch
> chroot is gcc-6, which is at version 6.2.1-5 in stretch and 6.3.0-2 in
> unstable.
> I couldn't test this combination (old binutils + new gcc) on the porter
> boxes though.
>

I tried to build a package libsystemd0-dbgsym, and test it with gdb,
it seems all binary linked with libsystemd will fail.

root@thor:/tmp# gdb /usr/bin/top
GNU gdb (Debian 7.12-4) 7.12
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "mips64el-linux-gnuabi64".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/top...(no debugging symbols found)...done.
(gdb) r
Starting program: /usr/bin/top
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/lib/mips64el-linux-gnuabi64/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
_IO_new_fclose (fp=0x1) at iofclose.c:48
48  iofclose.c: No such file or directory.
(gdb) bt
#0  _IO_new_fclose (fp=0x1) at iofclose.c:48
#1  0x00fff7c96d28 in _init () from
/lib/mips64el-linux-gnuabi64/libsystemd.so.0
#2  0x00fff7fdb9d0 in call_init (l=0xfff7fc4120,
argc=argc@entry=1, argv=argv@entry=0xfff5c8,
env=env@entry=0xfff5d8) at dl-init.c:58
#3  0x00fff7fdbba8 in call_init (env=0xfff5d8,
argv=0xfff5c8, argc=1, l=) at dl-init.c:30
#4  _dl_init (main_map=0xfff7fff848, argc=,
argv=0xfff5c8, env=0xfff5d8) at dl-init.c:120
#5  0x00fff7fca450 in _dl_start_user () from /lib64/ld.so.1
Backtrace stopped: frame did not save the PC


It seems that binutils generate bad shared lib.


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



-- 
YunQiang Su

Bug#851412: FTBFS on mips*, tests fail with SIGSEGV

[YunQiang Su]

On Sun, Jan 15, 2017 at 1:15 AM, Michael Biebl  wrote:
> Am 14.01.2017 um 18:02 schrieb Michael Biebl:
>
>> binutils_2.27.90.20170114-1. Building in stretch chroot though was
>> successful. So my observation is:
>>
>> binutils_2.27.90.20170114-1: fails
>> binutils_2.27.90.20170113-1: fails
>> binutils_2.27.51.20161220-1: ok
>>
>> So it looks like a mips related regression in binutils at a first
>> glance. In the past, systemd built reasonably reliably on mips* [3].
>
> A notable difference (aside from binutils) between the sid and stretch
> chroot is gcc-6, which is at version 6.2.1-5 in stretch and 6.3.0-2 in
> unstable.
> I couldn't test this combination (old binutils + new gcc) on the porter
> boxes though.
>

I tried to build a package libsystemd0-dbgsym, and test it with gdb,
it seems all binary linked with libsystemd will fail.

root@thor:/tmp# gdb /usr/bin/top
GNU gdb (Debian 7.12-4) 7.12
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "mips64el-linux-gnuabi64".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/top...(no debugging symbols found)...done.
(gdb) r
Starting program: /usr/bin/top
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/lib/mips64el-linux-gnuabi64/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
_IO_new_fclose (fp=0x1) at iofclose.c:48
48  iofclose.c: No such file or directory.
(gdb) bt
#0  _IO_new_fclose (fp=0x1) at iofclose.c:48
#1  0x00fff7c96d28 in _init () from
/lib/mips64el-linux-gnuabi64/libsystemd.so.0
#2  0x00fff7fdb9d0 in call_init (l=0xfff7fc4120,
argc=argc@entry=1, argv=argv@entry=0xfff5c8,
env=env@entry=0xfff5d8) at dl-init.c:58
#3  0x00fff7fdbba8 in call_init (env=0xfff5d8,
argv=0xfff5c8, argc=1, l=) at dl-init.c:30
#4  _dl_init (main_map=0xfff7fff848, argc=,
argv=0xfff5c8, env=0xfff5d8) at dl-init.c:120
#5  0x00fff7fca450 in _dl_start_user () from /lib64/ld.so.1
Backtrace stopped: frame did not save the PC


It seems that binutils generate bad shared lib.


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



-- 
YunQiang Su

Bug#849756: sssd-ldap fails to connect to ldaps:// due to problem with non-blocking socket

[Tomas Forsman]

Hello.

Applying the patch from https://github.com/SSSD/sssd/pull/67 onto sssd
1.14.2-1 in stretch, will make both ldaps:// and ldap://+starttls work
again. Applies cleanly, no regression found so far.

It would be quite unfortunate to have stretch without this fix, as I
believe ldap(s) support is one of the primary uses for sssd.

/Tomas
-- 
Tomas Forsman, st...@cs.umu.se, http://www.cs.umu.se/~stric/
`- SysAdmin at Computing Science, University of Umeå

Processed: Bug#851010 marked as pending

[Debian Bug Tracking System]

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

> tag 851010 pending
Bug #851010 [src:txfixtures] txfixtures: FTBFS: dh_auto_test: pybuild --test -i 
python{version} -p 2.7 returned exit code 13
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#851010: marked as pending

[Free Ekanayaka]

tag 851010 pending
thanks

Hello,

Bug #851010 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:


http://git.debian.org/?p=python-modules/packages/txfixtures.git;a=commitdiff;h=49557f3

---
commit 49557f332e060faf08247687f10a26bd3e35bb46
Author: Free Ekanayaka 
Date:   Wed Jan 18 09:10:56 2017 +

Release 0.2.6-1

diff --git a/debian/changelog b/debian/changelog
index f7493e1..5850b2a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+txfixtures (0.2.6-1) unstable; urgency=medium
+
+  * New upstream version 0.2.6
+
+- Fixes test_no_expected_port_exit using a potentially open port ()
+  to exercise the service not opening a port (Closes: #851010)
+
+ -- Free Ekanayaka   Wed, 18 Jan 2017 10:10:21 +0100
+
 txfixtures (0.2.5-1) unstable; urgency=medium
 
   * New upstream version 0.2.5

Bug#851115: marked as done (pcs: violates font license)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 09:35:58 +
with message-id 
and subject line Bug#851115: fixed in pcs 0.9.155+dfsg-1
has caused the Debian Bug report #851115,
regarding pcs: violates font license
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.)


-- 
851115: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851115
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pcs
Version: 0.9.155-3
Severity: serious
User: pkg-fonts-de...@lists.alioth.debian.org
Usertags: license-violation
X-Debbugs-CC: pkg-fonts-de...@lists.alioth.debian.org

Your source package contains an GPL/LGPL font:

pcsd/public/css/LiberationSans-BoldItalic.ttf
pcsd/public/css/LiberationSans-Italic.ttf
pcsd/public/css/LiberationSans-Regular.ttf
pcsd/public/css/LiberationSans-Bold.ttf

This looks to be from here:

https://fedorahosted.org/liberation-fonts/

The font's source code appears to be here:

https://git.fedorahosted.org/cgit/liberation-fonts.git/tree/src

Your source package does not contain the font source code, therefore
your distribution of the font constitutes a violation of the license.

Please notify your upstream that they are violating the font license.

Please remove the font from the source package and build-depend or
depend on the fonts-liberation binary font package instead.

Please contact your upstream and ask them to use fontconfig or similar
to get fonts for use by the software instead of using a specific font.

This message is brought to you by the Debian Fonts Task Force:

http://wiki.debian.org/Fonts

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: pcs
Source-Version: 0.9.155+dfsg-1

We believe that the bug you reported is fixed in the latest version of
pcs, 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.
Valentin Vidic  (supplier of updated pcs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 13 Jan 2017 13:50:46 +0100
Source: pcs
Binary: pcs
Architecture: source
Version: 0.9.155+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian HA Maintainers 

Changed-By: Valentin Vidic 
Description:
 pcs- Pacemaker Configuration System
Closes: 851115
Changes:
 pcs (0.9.155+dfsg-1) unstable; urgency=medium
 .
   * Repack upstream source without Liberation fonts (Closes: #851115)
   * Update font linking for new upstream
Checksums-Sha1:
 0db1bf5ae62ebb699387fe07b3ae62226d99444a 2213 pcs_0.9.155+dfsg-1.dsc
 89aa8a1db8296501e43838fbf3efc8b06c14acaf 1411909 pcs_0.9.155+dfsg.orig.tar.gz
 b9c5fe6381da1228fa06179bd88c8e8e30077672 167864 
pcs_0.9.155+dfsg-1.debian.tar.xz
Checksums-Sha256:
 4b10161dd2f01dec4ce840a7732ce341aa2089d13699431fb07f90bdd40210e4 2213 
pcs_0.9.155+dfsg-1.dsc
 76d66a614be3c739ed9f19932230bc728c646c2361dab684bae855199ad0d636 1411909 
pcs_0.9.155+dfsg.orig.tar.gz
 414b825fd191994da145fdf150b618272d37fa57c605d874c76bca6fbdcf1244 167864 
pcs_0.9.155+dfsg-1.debian.tar.xz
Files:
 7ccb5009cc30dd7c0cbab635d93cb284 2213 admin extra pcs_0.9.155+dfsg-1.dsc
 ef90e1321fcfcd1c6fd4dbe1c0274000 1411909 admin extra 
pcs_0.9.155+dfsg.orig.tar.gz
 1dcbbac81b206cfacb8bdb3bc800df81 167864 admin extra 
pcs_0.9.155+dfsg-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAlh/McMACgkQTFprqxLS
p64laxAAjni4zKIZCbNyAyHmZ89EI4+uFWV/93cmVLWq6C93O2txAmkI+qIQdntB
WUMj4EvDPqwDvpU8tolkMpluYpahxZaWceaD5ruvnorZ5MC72fZ/2ozgvJiJVqJY
/Vv6UNicpyF1jduYvBxPdsviAIWo/YTNoVzWFowEo5IqdRV3Ns1UfQGW3UADu4+D
pF3mTLKORrRovgX9ObA7tdTKUdhJS2/vHDhA7VWZqNQNORx2+srKNx0Gi78imFp6
H/TzhWxanRcNFLEEGQK/CUSo6/uQ8Bom0Wm1mKlCuwjrENqk53Pd59pSsWkAXoq1
MFMFRXytX52oPZ1wF4EdM0WvdKlcTa/hNir7a9FxKBgTNTBYG76F9Q009WP2qKay
4r9skF0AOr7gt+eAlXC9hd4pQqe8mX9eD93eoshJiwdv/8vs4QmNd/5t3XYGmifO
xCMz3f/VqeAu+ba9sBXTE/kqscTfOqYNREKTlGO2tB0lIfYPaCoAG4LzsxXtb7mT
6lpfo5zFfudDinC6LLyoEkjyBX05FwtUolc0HZOlFWMzVhjNJF60SI2SPYcL/ikX
Xt4dN0U5Q+vGsylcrSJg0bzO1ypzeK8qbMd6Y6+w2SvByo2eRVch0SNdA16mGsUU
54eSXhJGCRrtsFIfrxkEZHN5npOuieG0qt6BC8ETZ3PxZDwsJ7Y=
=T7

Bug#851741: python-jinja2: New major version breaks ansible templates

[Jeremy Bicha]

Package: python-jinja2
Version: 2.9.4-1
Severity: serious
Affects: ansible

The new version of jinja2 breaks several templates used by ansible.

Please see https://github.com/ansible/ansible/issues/20063

I stumbled across this when using debops:
https://github.com/debops/ansible-postfix/issues/84

Thanks,
Jeremy Bicha

Bug#851010: marked as done (txfixtures: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 11:04:11 +
with message-id 
and subject line Bug#851010: fixed in txfixtures 0.2.6-1
has caused the Debian Bug report #851010,
regarding txfixtures: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 
2.7 returned exit code 13
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.)


-- 
851010: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851010
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: txfixtures
Version: 0.2.5-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build --with python2,python3 --buildsystem=pybuild
>dh_testdir -O--buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py config 
> running config
> I: pybuild base:184: python3.5 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_2.7/build/txfixtures
> creating /<>/.pybuild/pythonX.Y_2.7/build/txfixtures/_twisted
> copying txfixtures/_twisted/testing.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/txfixtures/_twisted
> copying txfixtures/_twisted/threading.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/txfixtures/_twisted
> copying txfixtures/_twisted/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/txfixtures/_twisted
> creating /<>/.pybuild/pythonX.Y_2.7/build/txfixtures/tests
> copying txfixtures/tests/test_mongodb.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/txfixtures/tests
> copying txfixtures/tests/test_service.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/txfixtures/tests
> copying txfixtures/tests/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/txfixtures/tests
> copying txfixtures/tests/test_phantomjs.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/txfixtures/tests
> copying txfixtures/tests/test_reactor.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/txfixtures/tests
> copying txfixtures/phantomjs.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/txfixtures
> copying txfixtures/tachandler.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/txfixtures
> copying txfixtures/mongodb.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/txfixtures
> copying txfixtures/_testtools.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/txfixtures
> copying txfixtures/osutils.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/txfixtures
> copying txfixtures/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/txfixtures
> copying txfixtures/service.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/txfixtures
> copying txfixtures/reactor.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/txfixtures
> creating 
> /<>/.pybuild/pythonX.Y_2.7/build/txfixtures/_twisted/tests
> copying txfixtures/_twisted/tests/test_threading.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/txfixtures/_twisted/tests
> copying txfixtures/_twisted/tests/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/txfixtures/_twisted/tests
> running egg_info
> writing requirements to txfixtures.egg-info/requires.txt
> writing txfixtures.egg-info/PKG-INFO
> writing top-level names to txfixtures.egg-info/top_level.txt
> writing dependency_links to txfixtures.egg-info/dependency_links.txt
> [pbr] Reusing existing SOURCES.txt
> I: pybuild base:184: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_3.5/build/txfixtures
> creating /<>/.pybuild/pythonX.Y_3.5/build/txfixtures/tests
> copying txfixtures/tests/test_mongodb.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/txfixtures/tests
> copying txfixtures/tests/test_service.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/txfixtures/tests
> copying txfixtures/tests/__init__.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/txfixtures/tests
> copying txfixtures/tests/test_phantomjs.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/txfixtures/tests
> copying txfixtures/tests/test_reactor.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/txfixtures/tests
> copying txfixtures/phantomjs.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/txfixtures
> copying txfixtures/tachandler.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/txfixtures
> copying txfixtures/mongodb.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/txfixtures
> copying txfixtures/_testtools.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/txfixtures
> copying txfixtures/osutils.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/txfixtures
> copying 

Bug#844785: "not authorised" doing various desktoppy things [and 1 more messages] [and 1 more messages]

[Michael Biebl]

Hi Ian

On Tue, 17 Jan 2017 13:35:14 + Ian Jackson
 wrote:
> Martín Ferrari writes ("Re: "not authorised" doing various desktoppy things 
> [and 1 more messages]"):
> > This seems to solve the problem for me, thank you very much! (And I hope
> > you can get this in for stretch!)
> 
> Thanks to everyone for their reports.  This is very helpful.
> 
> Currently experimental has 10-3~exp2 which also has a patch from
> Nikolaus Schulz to support hybrid sleep[1].  I don't use this myself
> so reports on that would also be welcome.
> 
> I indeed intend to push this to sid in the next few days, with the
> plan that it will be in stretch.

We are currently preparing an upload for systemd. It contains a
workaround for #851412 so we plan to upload today as we don't want to
block other packages unnecessarily.

While at it, I've also added [1] to ensure we have a working setup for
our sysvinit users when upgrading to stretch.
As the fixed version is only available in exp atm I'm not sure how apt
will behave i.e. if it puts the old systemd version on hold or installs
systemd-sysv, thus replacing sysvinit-core. So it would be nice if you
could upload systemd-shim to unstable as soon as possible.

Regards,
Michael


[1]
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=aceda6fa5fe4aaa1a93cd134a266b84c7cc983c4
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#844785: "not authorised" doing various desktoppy things [and 1 more messages] [and 1 more messages]

[Ian Jackson]

Michael Biebl writes ("Re: "not authorised" doing various desktoppy things [and 
1 more messages] [and 1 more messages]"):
> We are currently preparing an upload for systemd. It contains a
> workaround for #851412 so we plan to upload today as we don't want to
> block other packages unnecessarily.

Oh, that.  Right.  Yes.

> While at it, I've also added [1] to ensure we have a working setup for
> our sysvinit users when upgrading to stretch.

Thanks.

> As the fixed version is only available in exp atm I'm not sure how apt
> will behave i.e. if it puts the old systemd version on hold or installs
> systemd-sysv, thus replacing sysvinit-core. So it would be nice if you
> could upload systemd-shim to unstable as soon as possible.

I will do that ASAP.

Thanks for coordinating.

Regards,
Ian.

-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#851741: python-jinja2: New major version breaks ansible templates

[Piotr Ożarowski]

Hi Jeremy,

[Jeremy Bicha, 2017-01-18]
> The new version of jinja2 breaks several templates used by ansible.
> 
> Please see https://github.com/ansible/ansible/issues/20063
> 
> I stumbled across this when using debops:
> https://github.com/debops/ansible-postfix/issues/84

could you check if this commit fixes it for you?
https://github.com/pallets/jinja/commit/c6ddeb7d5f64789ed0bbc1ffef8596a79bc06fd9

Bug#851233: [debian-mysql] Bug#851233: Bug#851233: Security fixes from the January 2017 CPU

[Salvatore Bonaccorso]

Hi Lars,

On Wed, Jan 18, 2017 at 10:33:30AM +0100, Lars Tangvald wrote:
> Hi,
> 
> The update builds and passes testing.
> I've attached debdiff output for Wheezy and Jessie for this update. Aside
> from the changelog, the only change to packaging is a patch for a test
> (main.events_2) that was failing because of a hardcoded date.

Thanks for preparing the update.

> diff -r mysql-5.5-5.5.53/debian/changelog 
> ../mysql-5.5/mysql-5.5/debian/changelog
> 0a1,14
> > mysql-5.5 (5.5.54-0+deb8u1) jessie-security; urgency=high
> > 
> >   * Imported upstream version 5.5.54 to fix security issues:
> > - 
> > http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html
> > - CVE-2017-3238 CVE-2017-3243 CVE-2017-3244 CVE-2017-3258
> > - CVE-2017-3265 CVE-2017-3291 CVE-2017-3312 CVE-2017-3313
> > - CVE-2017-3317 CVE-2017-3318
> > (Closes: #851233)
> >   * Fix failing test main.events_2
> > The test was failing due to hardcoded date (2017-01-01). Added patch
> > pending upstream fix.
> > 
> >  -- Lars Tangvald   Tue, 17 Jan 2017 13:04:58 
> > +0100

This looks good, but see one change which seem included below:

> 5c19
> < - CVE-2016-7440 CVE-2016-5584
> ---
> > - CVE-2016-6662 CVE-2016-7440 CVE-2016-5584

Did you build not on top of the last update? Because we corrected the
CVE ids in the 5.5.53-0+deb8u1 upload. CVE-2016-6662 does not belong
there, and was already fixed in the DSA-3666-1 with mysql-5.5
5.5.52-0+deb8u1, cf. the resulting changelog for 5.5.53-0+deb8u1 in
https://bugs.debian.org/841050#62 for the DSA-3666-1 upload . I don't
remember exactly, but I though I had asked someone of the mysql
packaging team to import the final changes to the packaging
repository.

With that fixed, and build with -sa (to include the orig tarball)
please do upload to security-master.

Thanks for your work!

Regards,
Salvatore

Bug#848236: Remaining issue with gbrowse - any help (Was: Urgent call to BioPerl users (Was: Bug#848236: src:gbrowse: ...)

[Lincoln Stein]

Hi,

Unfortunately I can't reproduce the testing failures, and the build got all
the way to the signature generation, at which point it aborted because I do
not have the proper gpg signing key.

Bear with me, because I am new at this. Here is what I did:

   1. git clone https://anonscm.debian.org/git/debian-med/gbrowse.git
   2. Created a tarball of the current 2.56 GBrowse distribution
   named gbrowse_2.56+dfsg.orig.tar.gz and located in the parent directory of
   the just-cloned directory.
   3. ran debuild

So there are apparently differences in the environment that are causing
Gregor's build to fail. Here is my build environment:

Linux Mint 18.1 Serena

Perl v5.22.1 (debian package)

Bioperl 1.007001 (built from source)

Bio::Graphics 2.39-4 (debian package)


My guess is that I should be using the Bioperl 1.007001 debian package, or
possibly a newer version of the libbio-graphics package? In any case, I'm
stuck in the "works for me" phase.

Lincoln

On Tue, Jan 17, 2017 at 2:07 AM, Andreas Tille  wrote:

> Hi Lincoln,
>
> On Mon, Jan 16, 2017 at 06:14:34PM -0500, Lincoln Stein wrote:
> > I need a little help to reproduce Gregor's failed tests, given that I'm a
> > complete newbie wrt the Debian packaging system. I have cloned gbrowse
> > 2.56+dfsg-1 from the Debian Med repository, but I don't know what command
> > line to use to attempt the build. What is the next step? I'm guessing it
> is
> > some form of dpkg-buildpackage, but the number of options is pretty
> > overwhelming!
>
> If you have installed the devscripts package you can try
>
> debuild
>
> which is a wrapper around dpkg-buildpackage and in principle needs no
> options to reproduce the issue.  Debuild will inform you about missing
> Build-Dependencies you need to install - simply use apt-get install what
> is listed if anything is missing.  When doing so I get
>
> ...
> Test Summary Report
> ---
> t/00.compile.t  (Wstat: 3840 Tests: 90 Failed: 15)
>   Failed tests:  1, 3, 5, 7, 10, 15, 17-18, 29, 31, 33, 35
> 41, 45, 47
>   Non-zero exit status: 15
> t/02.rearchitecture.t   (Wstat: 512 Tests: 0 Failed: 0)
>   Non-zero exit status: 2
>   Parse errors: Bad plan.  You planned 90 tests but ran 0.
> t/03.render.t   (Wstat: 512 Tests: 0 Failed: 0)
>   Non-zero exit status: 2
>   Parse errors: Bad plan.  You planned 150 tests but ran 0.
> t/04.remoteserver.t (Wstat: 512 Tests: 0 Failed: 0)
>   Non-zero exit status: 2
>   Parse errors: Bad plan.  You planned 43 tests but ran 0.
> t/05.deferredrendering.t (Wstat: 512 Tests: 0 Failed: 0)
>   Non-zero exit status: 2
>   Parse errors: Bad plan.  You planned 19 tests but ran 0.
> t/06.featuresearch.t(Wstat: 512 Tests: 0 Failed: 0)
>   Non-zero exit status: 2
>   Parse errors: Bad plan.  You planned 26 tests but ran 0.
> t/07.karyotype.t(Wstat: 512 Tests: 0 Failed: 0)
>   Non-zero exit status: 2
>   Parse errors: Bad plan.  You planned 3 tests but ran 0.
> Files=10, Tests=103,  5 wallclock secs ( 0.05 usr  0.01 sys +  4.19 cusr
> 0.30 csys =  4.55 CPU)
> Result: FAIL
> Failed 7/10 test programs. 15/103 subtests failed.
> dh_auto_test: perl Build test --verbose 1 TEST_FILES=t/02.rearchitecture.t
> t/05.deferredrendering.t t/00.compile.t t/01.yeast.t t/07.balancer.t
> t/08.calign.t returned exit code 255
>
>
> Kind regards
>
>Andreas.
>
> --
> http://fam-tille.de
>



-- 
*Lincoln Stein*

Scientific Director (Interim), Ontario Institute for Cancer Research
Director, Informatics and Bio-computing Program, OICR
Senior Principal Investigator, OICR
Professor, Department of Molecular Genetics, University of Toronto


*Ontario Institute for Cancer Research*
MaRS Centre
661 University Avenue
Suite 510
Toronto, Ontario
Canada M5G 0A3

Tel: 416-673-8514
Mobile: 416-817-8240
Email: lincoln.st...@gmail.com
Toll-free: 1-866-678-6427
Twitter: @OICR_news

*Executive Assistant*
*Lisa Duncan*
Tel: 647-260-7970 <(647)%20260-7970>
Email: lisa.dun...@oicr.on.ca 
www.oicr.on.ca

This message and any attachments may contain confidential and/or privileged
information for the sole use of the intended recipient. Any review or
distribution by anyone other than the person for whom it was originally
intended is strictly prohibited. If you have received this message in
error, please contact the sender and delete all copies. Opinions,
conclusions or other information contained in this message may not be that
of the organization.

Bug#851233: [debian-mysql] Bug#851233: Bug#851233: Security fixes from the January 2017 CPU

[Lars Tangvald]

Hi,

On 01/18/2017 12:39 PM, Salvatore Bonaccorso wrote:

Hi Lars,

On Wed, Jan 18, 2017 at 10:33:30AM +0100, Lars Tangvald wrote:

Hi,

The update builds and passes testing.
I've attached debdiff output for Wheezy and Jessie for this update. Aside
from the changelog, the only change to packaging is a patch for a test
(main.events_2) that was failing because of a hardcoded date.

Thanks for preparing the update.


diff -r mysql-5.5-5.5.53/debian/changelog 
../mysql-5.5/mysql-5.5/debian/changelog
0a1,14

mysql-5.5 (5.5.54-0+deb8u1) jessie-security; urgency=high

   * Imported upstream version 5.5.54 to fix security issues:
 - 
http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html
 - CVE-2017-3238 CVE-2017-3243 CVE-2017-3244 CVE-2017-3258
 - CVE-2017-3265 CVE-2017-3291 CVE-2017-3312 CVE-2017-3313
 - CVE-2017-3317 CVE-2017-3318
 (Closes: #851233)
   * Fix failing test main.events_2
 The test was failing due to hardcoded date (2017-01-01). Added patch
 pending upstream fix.

  -- Lars Tangvald   Tue, 17 Jan 2017 13:04:58 +0100

This looks good, but see one change which seem included below:


5c19
< - CVE-2016-7440 CVE-2016-5584
---

 - CVE-2016-6662 CVE-2016-7440 CVE-2016-5584

Did you build not on top of the last update? Because we corrected the
CVE ids in the 5.5.53-0+deb8u1 upload. CVE-2016-6662 does not belong
there, and was already fixed in the DSA-3666-1 with mysql-5.5
5.5.52-0+deb8u1, cf. the resulting changelog for 5.5.53-0+deb8u1 in
https://bugs.debian.org/841050#62 for the DSA-3666-1 upload . I don't
remember exactly, but I though I had asked someone of the mysql
packaging team to import the final changes to the packaging
repository.
Aha, yes. I see the vcs hasn't got the 5.5.53 packages imported 
properly. I'll do the import and rebuild, thanks.

With that fixed, and build with -sa (to include the orig tarball)
please do upload to security-master.
Do we have access to upload here? I think the security team have handled 
the upload in the past.


--
Lars

Thanks for your work!

Regards,
Salvatore

Bug#848236: Remaining issue with gbrowse - any help (Was: Urgent call to BioPerl users (Was: Bug#848236: src:gbrowse: ...)

[Lincoln Stein]

Ok, here is the last key piece of information. Replacing source-built
Bioperl with the debian bioperl-1.7.1-1 package from
https://packages.debian.org/sid/bioperl reproduced Gregor's test errors
exactly.

I also tried swapping in libbio-graphics-perl 2.40-1 from the same
repository (with both versions of bioperl), but this has no effect one way
or another.

Conclusion: something in the bioperl debian 1.7.1-1 package is causing the
test failures.

Lincoln


On Wed, Jan 18, 2017 at 6:43 AM, Lincoln Stein 
wrote:

> Hi,
>
> Unfortunately I can't reproduce the testing failures, and the build got
> all the way to the signature generation, at which point it aborted because
> I do not have the proper gpg signing key.
>
> Bear with me, because I am new at this. Here is what I did:
>
>1. git clone https://anonscm.debian.org/git/debian-med/gbrowse.git
>2. Created a tarball of the current 2.56 GBrowse distribution
>named gbrowse_2.56+dfsg.orig.tar.gz and located in the parent
>directory of the just-cloned directory.
>3. ran debuild
>
> So there are apparently differences in the environment that are causing
> Gregor's build to fail. Here is my build environment:
>
> Linux Mint 18.1 Serena
>
> Perl v5.22.1 (debian package)
>
> Bioperl 1.007001 (built from source)
>
> Bio::Graphics 2.39-4 (debian package)
>
>
> My guess is that I should be using the Bioperl 1.007001 debian package, or
> possibly a newer version of the libbio-graphics package? In any case, I'm
> stuck in the "works for me" phase.
>
> Lincoln
>
> On Tue, Jan 17, 2017 at 2:07 AM, Andreas Tille  wrote:
>
>> Hi Lincoln,
>>
>> On Mon, Jan 16, 2017 at 06:14:34PM -0500, Lincoln Stein wrote:
>> > I need a little help to reproduce Gregor's failed tests, given that I'm
>> a
>> > complete newbie wrt the Debian packaging system. I have cloned gbrowse
>> > 2.56+dfsg-1 from the Debian Med repository, but I don't know what
>> command
>> > line to use to attempt the build. What is the next step? I'm guessing
>> it is
>> > some form of dpkg-buildpackage, but the number of options is pretty
>> > overwhelming!
>>
>> If you have installed the devscripts package you can try
>>
>> debuild
>>
>> which is a wrapper around dpkg-buildpackage and in principle needs no
>> options to reproduce the issue.  Debuild will inform you about missing
>> Build-Dependencies you need to install - simply use apt-get install what
>> is listed if anything is missing.  When doing so I get
>>
>> ...
>> Test Summary Report
>> ---
>> t/00.compile.t  (Wstat: 3840 Tests: 90 Failed: 15)
>>   Failed tests:  1, 3, 5, 7, 10, 15, 17-18, 29, 31, 33, 35
>> 41, 45, 47
>>   Non-zero exit status: 15
>> t/02.rearchitecture.t   (Wstat: 512 Tests: 0 Failed: 0)
>>   Non-zero exit status: 2
>>   Parse errors: Bad plan.  You planned 90 tests but ran 0.
>> t/03.render.t   (Wstat: 512 Tests: 0 Failed: 0)
>>   Non-zero exit status: 2
>>   Parse errors: Bad plan.  You planned 150 tests but ran 0.
>> t/04.remoteserver.t (Wstat: 512 Tests: 0 Failed: 0)
>>   Non-zero exit status: 2
>>   Parse errors: Bad plan.  You planned 43 tests but ran 0.
>> t/05.deferredrendering.t (Wstat: 512 Tests: 0 Failed: 0)
>>   Non-zero exit status: 2
>>   Parse errors: Bad plan.  You planned 19 tests but ran 0.
>> t/06.featuresearch.t(Wstat: 512 Tests: 0 Failed: 0)
>>   Non-zero exit status: 2
>>   Parse errors: Bad plan.  You planned 26 tests but ran 0.
>> t/07.karyotype.t(Wstat: 512 Tests: 0 Failed: 0)
>>   Non-zero exit status: 2
>>   Parse errors: Bad plan.  You planned 3 tests but ran 0.
>> Files=10, Tests=103,  5 wallclock secs ( 0.05 usr  0.01 sys +  4.19 cusr
>> 0.30 csys =  4.55 CPU)
>> Result: FAIL
>> Failed 7/10 test programs. 15/103 subtests failed.
>> dh_auto_test: perl Build test --verbose 1 TEST_FILES=t/02.rearchitecture.t
>> t/05.deferredrendering.t t/00.compile.t t/01.yeast.t t/07.balancer.t
>> t/08.calign.t returned exit code 255
>>
>>
>> Kind regards
>>
>>Andreas.
>>
>> --
>> http://fam-tille.de
>>
>
>
>
> --
> *Lincoln Stein*
>
> Scientific Director (Interim), Ontario Institute for Cancer Research
> Director, Informatics and Bio-computing Program, OICR
> Senior Principal Investigator, OICR
> Professor, Department of Molecular Genetics, University of Toronto
>
> 
> *Ontario Institute for Cancer Research*
> MaRS Centre
> 661 University Avenue
> Suite 510
> Toronto, Ontario
> Canada M5G 0A3
>
> Tel: 416-673-8514 <(416)%20673-8514>
> Mobile: 416-817-8240 <(416)%20817-8240>
> Email: lincoln.st...@gmail.com
> Toll-free: 1-866-678-6427 <(866)%20678-6427>
> Twitter: @OICR_news
>
> *Executive Assistant*
> *Lisa Duncan*
> Tel: 647-260-7970 <(647)%20260-7970>
> Email: lisa.dun...@oicr.on.ca 
> www.oicr.on.ca
>
> This message and any attachments may contain confidential and/or
> privileged information for the sole use of the intended recipient. Any
> review or distribution by anyone other than the person for whom it was

Bug#848236: Remaining issue with gbrowse - any help (Was: Urgent call to BioPerl users (Was: Bug#848236: src:gbrowse: ...)

[Lincoln Stein]

Ok, and here is a little command-line test that takes the problem a bit
deeper. I'm sending this out because I have to go to work now and can't get
back to this again today:

 perl -MBio::Perl -MBio::Graphics -MBio::Graphics::Glyph::span
Can't locate Bio/Coordinate/Pair.pm in @INC (you may need to install the
Bio::Coordinate::Pair module) (@INC contains: /etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.22.1 /usr/local/share/perl/5.22.1
/usr/lib/x86_64-linux-gnu/perl5/5.22 /usr/share/perl5
/usr/lib/x86_64-linux-gnu/perl/5.22 /usr/share/perl/5.22
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at
/usr/share/perl5/Bio/Graphics/Glyph/arrow.pm line 13,  line 192.
BEGIN failed--compilation aborted at /usr/share/perl5/Bio/Graphics/Glyph/
arrow.pm line 13,  line 192.
Compilation failed in require at /usr/share/perl/5.22/base.pm line 97,
 line 192.
...propagated at /usr/share/perl/5.22/base.pm line 106,  line 192.
BEGIN failed--compilation aborted at /usr/share/perl5/Bio/Graphics/Glyph/
anchored_arrow.pm line 5,  line 192.
Compilation failed in require at /usr/share/perl/5.22/base.pm line 97,
 line 192.
...propagated at /usr/share/perl/5.22/base.pm line 106,  line 192.
BEGIN failed--compilation aborted at /usr/share/perl5/Bio/Graphics/Glyph/
span.pm line 4,  line 192.
Compilation failed in require,  line 192.
BEGIN failed--compilation aborted,  line 192.

There appears to be a new dependency on libbio-coordinate. Probably best to
add a "use Bio::Coordinate" and the dependency to Bio::Graphics. Then the
problem will disappear.

Lincoln

On Wed, Jan 18, 2017 at 7:00 AM, Lincoln Stein 
wrote:

> Ok, here is the last key piece of information. Replacing source-built
> Bioperl with the debian bioperl-1.7.1-1 package from
> https://packages.debian.org/sid/bioperl reproduced Gregor's test errors
> exactly.
>
> I also tried swapping in libbio-graphics-perl 2.40-1 from the same
> repository (with both versions of bioperl), but this has no effect one way
> or another.
>
> Conclusion: something in the bioperl debian 1.7.1-1 package is causing the
> test failures.
>
> Lincoln
>
>
> On Wed, Jan 18, 2017 at 6:43 AM, Lincoln Stein 
> wrote:
>
>> Hi,
>>
>> Unfortunately I can't reproduce the testing failures, and the build got
>> all the way to the signature generation, at which point it aborted because
>> I do not have the proper gpg signing key.
>>
>> Bear with me, because I am new at this. Here is what I did:
>>
>>1. git clone https://anonscm.debian.org/git/debian-med/gbrowse.git
>>2. Created a tarball of the current 2.56 GBrowse distribution
>>named gbrowse_2.56+dfsg.orig.tar.gz and located in the parent
>>directory of the just-cloned directory.
>>3. ran debuild
>>
>> So there are apparently differences in the environment that are causing
>> Gregor's build to fail. Here is my build environment:
>>
>> Linux Mint 18.1 Serena
>>
>> Perl v5.22.1 (debian package)
>>
>> Bioperl 1.007001 (built from source)
>>
>> Bio::Graphics 2.39-4 (debian package)
>>
>>
>> My guess is that I should be using the Bioperl 1.007001 debian package,
>> or possibly a newer version of the libbio-graphics package? In any case,
>> I'm stuck in the "works for me" phase.
>>
>> Lincoln
>>
>> On Tue, Jan 17, 2017 at 2:07 AM, Andreas Tille  wrote:
>>
>>> Hi Lincoln,
>>>
>>> On Mon, Jan 16, 2017 at 06:14:34PM -0500, Lincoln Stein wrote:
>>> > I need a little help to reproduce Gregor's failed tests, given that
>>> I'm a
>>> > complete newbie wrt the Debian packaging system. I have cloned gbrowse
>>> > 2.56+dfsg-1 from the Debian Med repository, but I don't know what
>>> command
>>> > line to use to attempt the build. What is the next step? I'm guessing
>>> it is
>>> > some form of dpkg-buildpackage, but the number of options is pretty
>>> > overwhelming!
>>>
>>> If you have installed the devscripts package you can try
>>>
>>> debuild
>>>
>>> which is a wrapper around dpkg-buildpackage and in principle needs no
>>> options to reproduce the issue.  Debuild will inform you about missing
>>> Build-Dependencies you need to install - simply use apt-get install what
>>> is listed if anything is missing.  When doing so I get
>>>
>>> ...
>>> Test Summary Report
>>> ---
>>> t/00.compile.t  (Wstat: 3840 Tests: 90 Failed: 15)
>>>   Failed tests:  1, 3, 5, 7, 10, 15, 17-18, 29, 31, 33, 35
>>> 41, 45, 47
>>>   Non-zero exit status: 15
>>> t/02.rearchitecture.t   (Wstat: 512 Tests: 0 Failed: 0)
>>>   Non-zero exit status: 2
>>>   Parse errors: Bad plan.  You planned 90 tests but ran 0.
>>> t/03.render.t   (Wstat: 512 Tests: 0 Failed: 0)
>>>   Non-zero exit status: 2
>>>   Parse errors: Bad plan.  You planned 150 tests but ran 0.
>>> t/04.remoteserver.t (Wstat: 512 Tests: 0 Failed: 0)
>>>   Non-zero exit status: 2
>>>   Parse errors: Bad plan.  You planned 43 tests but ran 0.
>>> t/05.deferredrendering.t (Wstat: 512 Tests: 0 Failed: 0)
>>>   Non-zero exit status: 2
>>>   Parse errors: Bad p

Bug#851745: diamond: lintian error: init.d-script-needs-depends-on-lsb-base etc/init.d/diamond

[David Stapleton]

Package: diamond
Version: 4.0.515-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

I'm attempting to build diamond from source, however the build fails at lintian
check time:

"diamond: init.d-script-needs-depends-on-lsb-base etc/init.d/diamond (line 42)
 
The given init script sources the /lib/lsb/init-functions utility
functions without declaring the corresponding dependency on lsb-base (>=
3.0-6).

Severity: important, Certainty: possible

Check: init.d, Type: binary"

Thanks,
David

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

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

Bug#849574: Just a note from the regular sponsor of this package

[Andreas Tille]

Hi,

the uploader of this package Daniele E. Domenichelli confirmed that he
is not using this package any more and I personally do not consider my
time well spent to save a package which I never used.  From my point of
view the package should be orphaned and possibly even removed from
Debian.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#846230: marked as done (policykit-1-gnome: Fails to start with warning: "Unable to determine the session we are in: No session for pid")

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 12:19:22 +
with message-id 
and subject line Bug#844785: fixed in systemd-shim 10-3
has caused the Debian Bug report #844785,
regarding policykit-1-gnome: Fails to start with warning: "Unable to determine 
the session we are in: No session for pid"
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.)


-- 
844785: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844785
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: policykit-1-gnome
Version: 0.105-5
Severity: important

Dear Maintainer,

I use lightdm and Xfce.

The agent is not started on start
up, so many functions do not work, such as controlling network through
NetworkManager, mounting disks with Nano, running Gparted, powering off
or suspending through Xfce's log out panel and possibly others.

I tried starting polkit-gnome-authentication-agent-1 manually, but the
process closes/crashes immediately, reporting the following message:

(polkit-gnome-authentication-agent-1:7502): polkit-gnome-1-WARNING **:
Unable to determine the session we are in: No session for pid 7502

I read several threads on the internet describing similar issues, but
they none of them helped in solving the issue or identifying its cause.

This problem presented itself after a recent update. I think that the
package itself was not updated, however this is my best bet on where
to report this bug.

Please let me know if I should provide more information.

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

Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages policykit-1-gnome depends on:
ii  libc6  2.24-7
ii  libgdk-pixbuf2.0-0 2.36.0-1
ii  libglib2.0-0   2.50.2-2
ii  libgtk-3-0 3.22.4-1
ii  libpolkit-agent-1-00.105-17
ii  libpolkit-gobject-1-0  0.105-17
ii  policykit-10.105-17

policykit-1-gnome recommends no packages.

policykit-1-gnome suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: systemd-shim
Source-Version: 10-3

We believe that the bug you reported is fixed in the latest version of
systemd-shim, 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 844...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ian Jackson  (supplier of updated systemd-shim 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 18 Jan 2017 12:02:27 +
Source: systemd-shim
Binary: systemd-shim
Architecture: source
Version: 10-3
Distribution: unstable
Urgency: high
Maintainer: Debian QA Group 
Changed-By: Ian Jackson 
Description:
 systemd-shim - shim for systemd
Closes: 780697 844785 851566
Changes:
 systemd-shim (10-3) unstable; urgency=high
 .
   * QA upload.
   * Upload to unstable, for stretch.
   * No code changes.
 .
 systemd-shim (10-3~exp2) experimental; urgency=medium
 .
   * QA upload.
 .
   [ Ian Jackson ]
   * Wrapper script moved to libexec, as it contains an arch-specific path
 and is therefore itself arch-specific.  Closes:#851566.
   * Fix my email address in changelog entry for 10-3~exp1.
 .
   [ Nikolaus Schulz ]
   * Support hybrid-sleep.  Closes:#780697.
 .
 systemd-shim (10-3~exp1) experimental; urgency=high
 .
   QA upload:
   * Install wrapper script to mount /sys/fs/cgroup/systemd.
 Fixes "not authorised" problem with various desktop services,
 when running with newer systemd.  Closes:#844785 in Debian.
 [Michael Biebl, Ian Jackson]
   * Add debian/.gitignore.
Checksums-Sha1:
 ac9bd21e32dafb614761dbdaf44bdb47ba1ace5b 1805 systemd-shim_10-3.dsc
 5fef21f4c86f3461130da8675f427e5380b81566 8948 systemd-shim_10-3.debian.tar.xz
Checksums-Sha256:
 c9e672cbde072b53853774ece75d3562fb539f80feb7f1aa9ce7936fd8a59c6f 1805 
systemd-shim_10-3.dsc
 a74e2cacfae5b6db343472742d5d63dfafd90f77bd0210f9e50331b1b445d6e9 8948 
systemd-shim_10-3.debian.tar.xz
Files:
 0165bf4d49a9ff08a

Bug#844785: marked as done (systemd-shim not fully compatible with systemd 232)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 12:19:22 +
with message-id 
and subject line Bug#844785: fixed in systemd-shim 10-3
has caused the Debian Bug report #844785,
regarding systemd-shim not fully compatible with systemd 232
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.)


-- 
844785: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844785
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 232-1

Since systemd 232, lightdm's menu entries to
shutdown/reboot/suspend/hibernate the system are grayed out.

Furthermore, GNOME polkit authentication agent fails to start (I use
openbox, with the agent normally started from
~/.config/openbox/autostart). When manually run in a terminal, it
immediately exits with the error message:

"polkit-gnome-1-WARNING **: Unable to determine the session we are in:
No session for pid ..."

Downgrading systemd/libsystemd0/libpam-systemd to version 231-10 fixes
the problem (I also tried 232-1 and 232-2, but they didn't work either).

Sorry for the vague bug title (and the probably wrong binary package),
but it's the best I can do since I'm not at all familiar with the way
systemd/polkit/pam/lightdm/whatever interact with each other.

Also, I just spotted this bug today despite the fact that it was
introduced two weeks ago, because I rarely shutdown my sid box.

Regards,

-- 
Raphaël Halimi



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: systemd-shim
Source-Version: 10-3

We believe that the bug you reported is fixed in the latest version of
systemd-shim, 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 844...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ian Jackson  (supplier of updated systemd-shim 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 18 Jan 2017 12:02:27 +
Source: systemd-shim
Binary: systemd-shim
Architecture: source
Version: 10-3
Distribution: unstable
Urgency: high
Maintainer: Debian QA Group 
Changed-By: Ian Jackson 
Description:
 systemd-shim - shim for systemd
Closes: 780697 844785 851566
Changes:
 systemd-shim (10-3) unstable; urgency=high
 .
   * QA upload.
   * Upload to unstable, for stretch.
   * No code changes.
 .
 systemd-shim (10-3~exp2) experimental; urgency=medium
 .
   * QA upload.
 .
   [ Ian Jackson ]
   * Wrapper script moved to libexec, as it contains an arch-specific path
 and is therefore itself arch-specific.  Closes:#851566.
   * Fix my email address in changelog entry for 10-3~exp1.
 .
   [ Nikolaus Schulz ]
   * Support hybrid-sleep.  Closes:#780697.
 .
 systemd-shim (10-3~exp1) experimental; urgency=high
 .
   QA upload:
   * Install wrapper script to mount /sys/fs/cgroup/systemd.
 Fixes "not authorised" problem with various desktop services,
 when running with newer systemd.  Closes:#844785 in Debian.
 [Michael Biebl, Ian Jackson]
   * Add debian/.gitignore.
Checksums-Sha1:
 ac9bd21e32dafb614761dbdaf44bdb47ba1ace5b 1805 systemd-shim_10-3.dsc
 5fef21f4c86f3461130da8675f427e5380b81566 8948 systemd-shim_10-3.debian.tar.xz
Checksums-Sha256:
 c9e672cbde072b53853774ece75d3562fb539f80feb7f1aa9ce7936fd8a59c6f 1805 
systemd-shim_10-3.dsc
 a74e2cacfae5b6db343472742d5d63dfafd90f77bd0210f9e50331b1b445d6e9 8948 
systemd-shim_10-3.debian.tar.xz
Files:
 0165bf4d49a9ff08ac5e3077aff13f1f 1805 admin extra systemd-shim_10-3.dsc
 ddcd87c81360b744208329d95510ccd6 8948 admin extra 
systemd-shim_10-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEVZrkbC1rbTJl58uh4+M5I0i1DTkFAlh/WZQACgkQ4+M5I0i1
DTkT9Qf+M+7Oaz7FtZmKd5vSHwB2N1yTrfkWicGVapo3BcS9/OPPpdsQo1C8oIyI
lNbt3k/ms7f7WeoQLuGGHL1qngzdg75cxOnhqZqXuoFScSlhj6Juo6n+UeYi6kUj
QDXRd36uyXLUmYE/1tcREl80MnpzxdWny6ntXqMfG4eGT8RFPgGKZYWx2xd9VfUG
Hx9ALGB21hY2a8iYx03Na61FoL6muBGw5CW6B3W+tlV1Tqgr/8ZQf1Brom1OfQa0
UYv5/+2DL3imjvjU1GWe1X13BY16ZDEjh2a6cxvhxGHqvb+KI03Ef8YU96D7hxmk
cbcOpqgJ02y4kC+/O0JGkmLwNRCpzg==
=5sqA
-END PGP SIGNATURE End Message ---

Bug#851750: kpatch: module FTBFS for Linux 4.9

[Andreas Beckmann]

Package: kpatch
Version: 0.3.2-3
Severity: serious
Justification: fails to build from source

Hi,

kpatch cannot build the kernel module for the current kernel in sid:

DKMS make.log for kpatch-0.3.2 for kernel 4.9.0-1-amd64 (x86_64)
Wed Jan 18 12:55:36 UTC 2017
make: Entering directory '/var/lib/dkms/kpatch/0.3.2/build/kmod'
make -C core clean
make[1]: Entering directory '/var/lib/dkms/kpatch/0.3.2/build/kmod/core'
rm -f -Rf .*.o.cmd .*.ko.cmd .tmp_versions *.o *.ko *.mod.c \
Module.symvers
make[1]: Leaving directory '/var/lib/dkms/kpatch/0.3.2/build/kmod/core'
make -C core
make[1]: Entering directory '/var/lib/dkms/kpatch/0.3.2/build/kmod/core'
make -C /lib/modules/4.9.0-1-amd64/build 
M=/var/lib/dkms/kpatch/0.3.2/build/kmod/core kpatch.ko
make[2]: Entering directory '/var/lib/dkms/kpatch/0.3.2/build/kmod/core'
make[2]: warning: jobserver unavailable: using -j1.  Add '+' to parent make 
rule.
  CC [M]  /var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.o
/var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:308:21: error: variable 
'kpatch_backtrace_ops' has initializer but incomplete type
 static const struct stacktrace_ops kpatch_backtrace_ops = {
 ^~
/var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:309:2: error: unknown field 
'address' specified in initializer
  .address = kpatch_backtrace_address_verify,
  ^
/var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:309:13: warning: excess 
elements in struct initializer
  .address = kpatch_backtrace_address_verify,
 ^~~
/var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:309:13: note: (near 
initialization for 'kpatch_backtrace_ops')
/var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:310:2: error: unknown field 
'stack' specified in initializer
  .stack  = kpatch_backtrace_stack,
  ^
/var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:310:12: warning: excess 
elements in struct initializer
  .stack  = kpatch_backtrace_stack,
^~
/var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:310:12: note: (near 
initialization for 'kpatch_backtrace_ops')
/var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:311:2: error: unknown field 
'walk_stack' specified in initializer
  .walk_stack = print_context_stack_bp,
  ^
/var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:311:16: error: 
'print_context_stack_bp' undeclared here (not in a function)
  .walk_stack = print_context_stack_bp,
^~
/var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:311:16: warning: excess 
elements in struct initializer
/var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:311:16: note: (near 
initialization for 'kpatch_backtrace_ops')
/var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:338:21: error: variable 
'kpatch_print_trace_ops' has initializer but incomplete type
 static const struct stacktrace_ops kpatch_print_trace_ops = {
 ^~
/var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:339:2: error: unknown field 
'stack' specified in initializer
  .stack  = kpatch_print_trace_stack,
  ^
/var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:339:12: warning: excess 
elements in struct initializer
  .stack  = kpatch_print_trace_stack,
^~~~
/var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:339:12: note: (near 
initialization for 'kpatch_print_trace_ops')
/var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:340:2: error: unknown field 
'address' specified in initializer
  .address = kpatch_print_trace_address,
  ^
/var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:340:13: warning: excess 
elements in struct initializer
  .address = kpatch_print_trace_address,
 ^~
/var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:340:13: note: (near 
initialization for 'kpatch_print_trace_ops')
/var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:341:2: error: unknown field 
'walk_stack' specified in initializer
  .walk_stack = print_context_stack,
  ^
/var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:341:16: error: 
'print_context_stack' undeclared here (not in a function)
  .walk_stack = print_context_stack,
^~~
/var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:341:16: warning: excess 
elements in struct initializer
/var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:341:16: note: (near 
initialization for 'kpatch_print_trace_ops')
/var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c: In function 
'kpatch_verify_activeness_safety':
/var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:362:3: error: implicit 
declaration of function 'dump_trace' [-Werror=implicit-function-declaration]
   dump_trace(t, NULL, NULL, 0, &kpatch_backtrace_ops, &args);
   ^~
/var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c: At top level:
/var/lib/dkms/kpatch/0.3.2/build/kmod/core/core.c:308:36: error: storage size 
of 'kpatch_backtrace_ops' isn't known
 static const struct stacktrace_ops kpatch_backtrace_ops = {

Bug#851745: diamond: Patch to fix this issue

[David Stapleton]

Package: diamond
Version: 4.0.515-2
Followup-For: Bug #851745

Dear Maintainer,

Below, I've provided a patch that fixes this issue (#851745) but also #851198:

--
diff -Nru diamond-4.0.515/debian/changelog diamond-4.0.515/debian/changelog
--- diamond-4.0.515/debian/changelog2017-01-05 18:04:13.0 +
+++ diamond-4.0.515/debian/changelog2017-01-18 12:35:58.0 +
@@ -1,3 +1,13 @@
+diamond (4.0.515-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/control
+- add lsb-base (>= 3.0-6) to depend; Closes: #851745
+  * debian/control
+- add python-pkg-resources to depends; Closes: #851198
+
+ -- David Stapleton   Wed, 18 Jan 2017 12:00:03 
+
+
 diamond (4.0.515-2) unstable; urgency=medium
 
   * debian/control
diff -Nru diamond-4.0.515/debian/control diamond-4.0.515/debian/control
--- diamond-4.0.515/debian/control 2017-01-05 18:02:44.0 +
+++ diamond-4.0.515/debian/control 2017-01-18 12:02:37.0 +
@@ -11,7 +11,8 @@
 
 Package: diamond
 Architecture: all
-Depends: ${python:Depends}, ${misc:Depends}, adduser, python-diamond (=
${binary:Version}), python-configobj
+Depends: ${python:Depends}, ${misc:Depends}, adduser, lsb-base (>= 3.0-6),
+ python-diamond (= ${binary:Version}), python-configobj
 Suggests: python-psutil
 Description: smart data producer for Graphite graphing package
  Diamond is a python daemon that collects system metrics and publishes them to
@@ -24,7 +25,7 @@
 Package: python-diamond
 Architecture: all
 Section: python
-Depends: ${python:Depends}, ${misc:Depends}, python-configobj
+Depends: ${python:Depends}, ${misc:Depends}, python-configobj, python-pkg-
resources 
 Description: smart data producer for Graphite graphing package (Python module)
  Diamond is a python daemon that collects system metrics and publishes them to
  Graphite (and others). It is capable of collecting cpu, memory, network, i/o,
--

Hopefully this is useful.

Thanks,
David

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

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

Bug#811593: marked as done (FTBFS with GCC 6: statement indented as if it were guarded by)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 13:04:52 +
with message-id 
and subject line Bug#851302: Removed package(s) from unstable
has caused the Debian Bug report #811593,
regarding FTBFS with GCC 6: statement indented as if it were guarded by
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.)


-- 
811593: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811593
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgetopt++
Version: 0.0.2-p22-3.1
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-misleading-indentation

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
>  g++ -DHAVE_CONFIG_H -I. -I.. -I./include -I../include -Wall -Werror -Wall -g 
> -O2 -c ../src/OptionSet.cc  -fPIC -DPIC -o src/.libs/OptionSet.o
> ../src/OptionSet.cc: In member function 'void 
> OptionSet::doOption(std::__cxx11::string&, const size_type&)':
> ../src/OptionSet.cc:129:8: error: statement is indented as if it were guarded 
> by... [-Werror=misleading-indentation]
> argv.erase(argv.begin() + 1);
> ^~~~
> 
> ../src/OptionSet.cc:126:25: note: ...this 'if' clause, but it is not
>  if (!isOption(maybepos))
>  ^~
> 
> ../src/OptionSet.cc:162:8: error: statement is indented as if it were guarded 
> by... [-Werror=misleading-indentation]
> argv.erase(argv.begin() + 1);
> ^~~~
> 
> ../src/OptionSet.cc:160:25: note: ...this 'if' clause, but it is not
>  if (!isOption(maybepos))
>  ^~
> 
> cc1plus: all warnings being treated as errors
> Makefile:435: recipe for target 'src/OptionSet.lo' failed
> make[1]: *** [src/OptionSet.lo] Error 1
> make[1]: Leaving directory 
> '/build/libgetopt++-MRY0f4/libgetopt++-0.0.2-p22/obj-x86_64-linux-gnu'
> debian/rules:52: recipe for target 'build-stamp' failed
> make: *** [build-stamp] Error 2

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Version: 0.0.2-p22-3.1+rm

Dear submitter,

as the package libgetopt++ has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/851302

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#851752: sysdig-dkms: module FTBFS for Linux 4.9

[Andreas Beckmann]

Package: sysdig-dkms
Version: 0.13.0-1
Severity: serious
Justification: fails to build from source
Control: found -1 0.9.0-1

Hi,

sysdig-dkms cannot build the kernel module for the current kernel in sid:

DKMS make.log for sysdig-0.13.0 for kernel 4.9.0-1-amd64 (x86_64)
Wed Jan 18 12:58:21 UTC 2017
make: Entering directory '/usr/src/linux-headers-4.9.0-1-amd64'
  LD  /var/lib/dkms/sysdig/0.13.0/build/built-in.o
  CC [M]  /var/lib/dkms/sysdig/0.13.0/build/main.o
  CC [M]  /var/lib/dkms/sysdig/0.13.0/build/dynamic_params_table.o
  CC [M]  /var/lib/dkms/sysdig/0.13.0/build/flags_table.o
  CC [M]  /var/lib/dkms/sysdig/0.13.0/build/ppm_fillers.o
  CC [M]  /var/lib/dkms/sysdig/0.13.0/build/event_table.o
  CC [M]  /var/lib/dkms/sysdig/0.13.0/build/ppm_events.o
  CC [M]  /var/lib/dkms/sysdig/0.13.0/build/syscall_table.o
  CC [M]  /var/lib/dkms/sysdig/0.13.0/build/ppm_cputime.o
/var/lib/dkms/sysdig/0.13.0/build/main.c:1740:5: error: conflicting types for 
'__access_remote_vm'
 int __access_remote_vm(struct task_struct *t, struct mm_struct *mm, unsigned 
long addr,
 ^~
In file included from 
/usr/src/linux-headers-4.9.0-1-common/include/linux/scatterlist.h:7:0,
 from 
/usr/src/linux-headers-4.9.0-1-common/include/linux/dmaengine.h:24,
 from 
/usr/src/linux-headers-4.9.0-1-common/include/linux/netdevice.h:38,
 from 
/usr/src/linux-headers-4.9.0-1-common/include/net/sock.h:51,
 from /var/lib/dkms/sysdig/0.13.0/build/main.c:47:
/usr/src/linux-headers-4.9.0-1-common/include/linux/mm.h:1295:12: note: 
previous declaration of '__access_remote_vm' was here
 extern int __access_remote_vm(struct task_struct *tsk, struct mm_struct *mm,
^~
/usr/src/linux-headers-4.9.0-1-common/scripts/Makefile.build:298: recipe for 
target '/var/lib/dkms/sysdig/0.13.0/build/main.o' failed
make[3]: *** [/var/lib/dkms/sysdig/0.13.0/build/main.o] Error 1
make[3]: *** Waiting for unfinished jobs
/usr/src/linux-headers-4.9.0-1-common/Makefile:1507: recipe for target 
'_module_/var/lib/dkms/sysdig/0.13.0/build' failed
make[2]: *** [_module_/var/lib/dkms/sysdig/0.13.0/build] Error 2
Makefile:150: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
Makefile:8: recipe for target 'all' failed
make: *** [all] Error 2
make: Leaving directory '/usr/src/linux-headers-4.9.0-1-amd64'


The version from testing fails differently:

DKMS make.log for sysdig-0.9.0 for kernel 4.9.0-1-amd64 (x86_64)
Wed Jan 18 13:03:41 UTC 2017
make: Entering directory '/usr/src/linux-headers-4.9.0-1-amd64'
  LD  /var/lib/dkms/sysdig/0.9.0/build/built-in.o
  CC [M]  /var/lib/dkms/sysdig/0.9.0/build/main.o
  CC [M]  /var/lib/dkms/sysdig/0.9.0/build/dynamic_params_table.o
  CC [M]  /var/lib/dkms/sysdig/0.9.0/build/event_table.o
  CC [M]  /var/lib/dkms/sysdig/0.9.0/build/ppm_fillers.o
  CC [M]  /var/lib/dkms/sysdig/0.9.0/build/syscall_table.o
  CC [M]  /var/lib/dkms/sysdig/0.9.0/build/flags_table.o
  CC [M]  /var/lib/dkms/sysdig/0.9.0/build/ppm_events.o
  CC [M]  /var/lib/dkms/sysdig/0.9.0/build/ppm_cputime.o
/var/lib/dkms/sysdig/0.9.0/build/ppm_fillers.c: In function 'append_cgroup':
/var/lib/dkms/sysdig/0.9.0/build/ppm_fillers.c:835:7: warning: assignment makes 
pointer from integer without a cast [-Wint-conversion]
  path = cgroup_path(css->cgroup, buf, *available);
   ^
In file included from 
/usr/src/linux-headers-4.9.0-1-common/include/uapi/linux/stddef.h:1:0,
 from 
/usr/src/linux-headers-4.9.0-1-common/include/linux/stddef.h:4,
 from 
/usr/src/linux-headers-4.9.0-1-common/include/uapi/linux/posix_types.h:4,
 from 
/usr/src/linux-headers-4.9.0-1-common/include/uapi/linux/types.h:13,
 from 
/usr/src/linux-headers-4.9.0-1-common/include/linux/types.h:5,
 from 
/usr/src/linux-headers-4.9.0-1-common/include/uapi/linux/audit.h:27,
 from 
/usr/src/linux-headers-4.9.0-1-common/arch/x86/include/asm/syscall.h:16,
 from /var/lib/dkms/sysdig/0.9.0/build/main.c:28:
/var/lib/dkms/sysdig/0.9.0/build/main.c: In function 'syscall_enter_probe':
/var/lib/dkms/sysdig/0.9.0/build/main.c:1641:40: error: 'struct thread_info' 
has no member named 'status'
  if (unlikely(task_thread_info(current)->status & TS_COMPAT)) {
^
/usr/src/linux-headers-4.9.0-1-common/include/linux/compiler.h:168:42: note: in 
definition of macro 'unlikely'
 # define unlikely(x) __builtin_expect(!!(x), 0)
  ^
/var/lib/dkms/sysdig/0.9.0/build/main.c: In function 'syscall_exit_probe':
/var/lib/dkms/sysdig/0.9.0/build/main.c:1703:41: error: 'struct thread_info' 
has no member named 'status'
  if (unlikely((task_thread_info(current)->status & TS_COMPAT) && id != 
__NR_execve)) {
 ^
/usr/src/linux-headers-4.9.0-1-common/include/linux/compiler.h:168:42: note: in 

Processed: Re: Bug#851745: diamond: lintian error: init.d-script-needs-depends-on-lsb-base etc/init.d/diamond

[Debian Bug Tracking System]

Processing control commands:

> severity -1 minor
Bug #851745 [diamond] diamond: lintian error: 
init.d-script-needs-depends-on-lsb-base etc/init.d/diamond
Severity set to 'minor' from 'serious'

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

Processed: sysdig-dkms: module FTBFS for Linux 4.9

[Debian Bug Tracking System]

Processing control commands:

> found -1 0.9.0-1
Bug #851752 [sysdig-dkms] sysdig-dkms: module FTBFS for Linux 4.9
Marked as found in versions sysdig/0.9.0-1.

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

Bug#851745: diamond: lintian error: init.d-script-needs-depends-on-lsb-base etc/init.d/diamond

[Sandro Tosi]

control: severity -1 minor

On Wed, Jan 18, 2017 at 7:13 AM, David Stapleton
 wrote:
> Package: diamond
> Version: 4.0.515-2
> Severity: serious

this is NOT a serious issue, lintian is not part of the official build
process and if the tool you use add lintian at the end and mark the
build as failed, it;s up to you to differentiate between a real FTBFS
and a succesfull build with lintian generating an error

> Justification: fails to build from source (but built successfully in the past)
>
> Dear Maintainer,
>
> I'm attempting to build diamond from source, however the build fails at 
> lintian
> check time:

why were you doing that? does the package not work for you?

>
> "diamond: init.d-script-needs-depends-on-lsb-base etc/init.d/diamond (line 42)
>
> The given init script sources the /lib/lsb/init-functions utility
> functions without declaring the corresponding dependency on lsb-base (>=
> 3.0-6).

the right solution is to remove the init file, and just use the
systemd unit provided

>
> Severity: important, Certainty: possible
>
> Check: init.d, Type: binary"
>
> Thanks,
> David
>
> -- System Information:
> Debian Release: 8.6
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)



-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Processed: tagging 851752

[Debian Bug Tracking System]

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

> tags 851752 + pending
Bug #851752 [sysdig-dkms] sysdig-dkms: module FTBFS for Linux 4.9
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: bug 851752 is forwarded to https://github.com/draios/sysdig/issues/710

[Debian Bug Tracking System]

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

> forwarded 851752 https://github.com/draios/sysdig/issues/710
Bug #851752 [sysdig-dkms] sysdig-dkms: module FTBFS for Linux 4.9
Set Bug forwarded-to-address to 'https://github.com/draios/sysdig/issues/710'.
> thanks
Stopping processing here.

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

Bug#851505: marked as done (Xvfb segfaults on mips64el)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 13:20:18 +
with message-id 
and subject line Bug#851412: fixed in systemd 232-11
has caused the Debian Bug report #851412,
regarding Xvfb segfaults on mips64el
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.)


-- 
851412: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851412
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xvfb
Version: 2:1.19.0-3
Severity: grave

Xvfb segfaults on mips64el:

(sid_mips64el-dchroot)sebastien@eller:~$ Xvfb
Segmentation fault

As a consequence, octave FTBFS on mips64el (it uses xvfb-run for its testsuite):

  
https://buildd.debian.org/status/fetch.php?pkg=octave&arch=mips64el&ver=4.0.3-3&stamp=1484413473

Cheers,

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


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 232-11

We believe that the bug you reported is fixed in the latest version of
systemd, 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.
Michael Biebl  (supplier of updated systemd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 18 Jan 2017 12:38:54 +0100
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote 
systemd-coredump libpam-systemd libnss-myhostname libnss-mymachines 
libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev libudev1 
libudev-dev udev-udeb libudev1-udeb
Architecture: source
Version: 232-11
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Michael Biebl 
Description:
 libnss-myhostname - nss module providing fallback resolution for the current 
hostname
 libnss-mymachines - nss module to resolve hostnames for local container 
instances
 libnss-resolve - nss module to resolve names via systemd-resolved
 libnss-systemd - nss module providing dynamic user and group name resolution
 libpam-systemd - system and service manager - PAM module
 libsystemd-dev - systemd utility library - development files
 libsystemd0 - systemd utility library
 libudev-dev - libudev development files
 libudev1   - libudev shared library
 libudev1-udeb - libudev shared library (udeb)
 systemd- system and service manager
 systemd-container - systemd container/nspawn tools
 systemd-coredump - tools for storing and retrieving coredumps
 systemd-journal-remote - tools for sending and receiving remote journal logs
 systemd-sysv - system and service manager - SysV links
 udev   - /dev/ and hotplug management daemon
 udev-udeb  - /dev/ and hotplug management daemon (udeb)
Closes: 851412 851445 851475 851492 851688
Changes:
 systemd (232-11) unstable; urgency=medium
 .
   [ Martin Pitt ]
   * Fix RestrictAddressFamilies=
 Backport upstream fix for setting up seccomp filters to fix
 RestrictAddressFamilies= on non-amd64 architectures. Drop the hack from
 debian/rules to remove this property from unit files.
 See #843160
   * Use local machine-id for running tests during package build.
 Since "init" and thus "systemd" are not part of debootstrap any more,
 some buildd chroots don't have an /etc/machine-id any more. Port the old
 Add-env-variable-for-machine-ID-path.patch to the current code, use a
 local machine-id again, and always make test suite failures fatal.
 (Closes: #851445)
 .
   [ Michael Biebl ]
   * gpt-auto-generator: support LUKS encrypted root partitions
 (Closes: #851475)
   * Switch to bfd linker on mips*
 The gold linker is currently producing broken libraries on mips*
 resulting in segfaults for users of libsystemd. Switch to bfd until
 binutils has been fixed. (Closes: #851412)
   * Revert "core: turn on specifier expansion for more unit file settings"
 The expansion of the % character broke the fstab-generator and
 specifying the tmpfs size as percentage of physical RAM resulted in the
 size being set to 4k. (Closes: #851492)
   * Drop obsolete Con

Bug#851412: marked as done (FTBFS on mips*, tests fail with SIGSEGV)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 13:20:18 +
with message-id 
and subject line Bug#851412: fixed in systemd 232-11
has caused the Debian Bug report #851412,
regarding FTBFS on mips*, tests fail with SIGSEGV
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.)


-- 
851412: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851412
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: systemd
Version: 232-10
Severity: serious
User: debian-m...@lists.debian.org
Usertags: mips-port

Hi mips porters,

the latest upload of systemd FTBFS on mips* [1]. Contrary to what the
buildd status page shows, mips64el is also affected. The build chroot on
mips64el did not have a /etc/machine-id, which is why the test suite was
non-fatal [2]. If you install systemd in the chroot (which sets up
/etc/machine-id) mips64el fails exactly like mips and mipsel, i.e. the
following two tests segfault:

../build-aux/test-driver: line 107: 26379 Segmentation fault   "$@" > $log_file 
2>&1
FAIL: test-bus-marshal

../build-aux/test-driver: line 107: 27445 Segmentation fault   "$@" > $log_file 
2>&1
FAIL: test-libsystemd-sym

Building the package on a porter pox (eller: mipsel, mips64el, minkus:
mips), the problem is 100% reproducible.

dmesg shows
[7368858.796075] 
 do_page_fault(): sending SIGSEGV to test-bus-marsha for 
invalid read access from 0064658b
[7368858.806215] epc = 77e19058 in
[7368858.829057]  libsystemd-shared-232.so[77dda000+18]
[7368858.832726] ra  = 77e19078 in
[7368858.845049]  libsystemd-shared-232.so[77dda000+18]

[7368895.490458] 
 do_page_fault(): sending SIGSEGV to test-libsystemd for 
invalid read access from 0064658b
[7368895.500588] epc = 77b85f44 in
[7368895.524124]  libsystemd.so.0.17.0[77b77000+82000]
[7368895.527490] ra  = 77b85f64 in
[7368895.536107]  libsystemd.so.0.17.0[77b77000+82000]



The initial test builds on the porter machines were using
binutils_2.27.90.20170113-1. As I suspected a binutils problem, I
upgraded to the recently uploaded 
binutils_2.27.90.20170114-1. Building in stretch chroot though was
successful. So my observation is:

binutils_2.27.90.20170114-1: fails
binutils_2.27.90.20170113-1: fails
binutils_2.27.51.20161220-1: ok

So it looks like a mips related regression in binutils at a first
glance. In the past, systemd built reasonably reliably on mips* [3].


Dear mips porters, it would be great if you can have a look. Can you
confirm these findings or is there something else causing these issues?

I've also CCed the binutils maintainers so they are aware of this
problem. Maybe they have an idea what's going wrong.

Regards,
Michael


[1] https://buildd.debian.org/status/package.php?p=systemd&suite=sid
[2] 
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/tree/debian/rules#n357
[3] https://buildd.debian.org/status/logs.php?pkg=systemd&arch=mipsel
-- Package-specific info:

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

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

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.126
ii  udev 232-10

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 232-11

We believe that the bug you reported is fixed in the latest version of
systemd, 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.
Michael Biebl  (supplier of updated systemd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 18 Jan 2017 12:38:54 +0100
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote 
systemd-coredump libpam-systemd libnss-myhostname libnss-mymachines 
libnss-resolve libnss-systemd lib

Bug#851642: marked as done (perl: FTBFS on mips64el: dist/threads/t/join.t failure)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 13:20:18 +
with message-id 
and subject line Bug#851412: fixed in systemd 232-11
has caused the Debian Bug report #851412,
regarding perl: FTBFS on mips64el: dist/threads/t/join.t failure
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.)


-- 
851412: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851412
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: perl
Version: 5.24.1-1
Severity: serious
X-Debbugs-Cc: debian-m...@lists.debian.org

This package failed to build on mips64el:

 dist/threads/t/join ... Died at 
t/join.t line 134.
 FAILED--expected 20 tests, saw 10

This has now happened twice on different buildds so it doesn't seem to be 
transient.

 https://buildd.debian.org/status/logs.php?pkg=perl&arch=mips64el

5.24.1~rc5-1 built fine in experimental a couple of weeks ago, and there
were no thread-related source changes between the versions (and a minimal
set of changes overall as the debian/cross/ ones don't affect native
builds).

So either something changed in the toolchain / platform or this was a
latent undeterministic bug and we're just unlucky now.

Needs investigation. Cc'ing the mips porters; any help would be welcome.
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 232-11

We believe that the bug you reported is fixed in the latest version of
systemd, 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.
Michael Biebl  (supplier of updated systemd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 18 Jan 2017 12:38:54 +0100
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote 
systemd-coredump libpam-systemd libnss-myhostname libnss-mymachines 
libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev libudev1 
libudev-dev udev-udeb libudev1-udeb
Architecture: source
Version: 232-11
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Michael Biebl 
Description:
 libnss-myhostname - nss module providing fallback resolution for the current 
hostname
 libnss-mymachines - nss module to resolve hostnames for local container 
instances
 libnss-resolve - nss module to resolve names via systemd-resolved
 libnss-systemd - nss module providing dynamic user and group name resolution
 libpam-systemd - system and service manager - PAM module
 libsystemd-dev - systemd utility library - development files
 libsystemd0 - systemd utility library
 libudev-dev - libudev development files
 libudev1   - libudev shared library
 libudev1-udeb - libudev shared library (udeb)
 systemd- system and service manager
 systemd-container - systemd container/nspawn tools
 systemd-coredump - tools for storing and retrieving coredumps
 systemd-journal-remote - tools for sending and receiving remote journal logs
 systemd-sysv - system and service manager - SysV links
 udev   - /dev/ and hotplug management daemon
 udev-udeb  - /dev/ and hotplug management daemon (udeb)
Closes: 851412 851445 851475 851492 851688
Changes:
 systemd (232-11) unstable; urgency=medium
 .
   [ Martin Pitt ]
   * Fix RestrictAddressFamilies=
 Backport upstream fix for setting up seccomp filters to fix
 RestrictAddressFamilies= on non-amd64 architectures. Drop the hack from
 debian/rules to remove this property from unit files.
 See #843160
   * Use local machine-id for running tests during package build.
 Since "init" and thus "systemd" are not part of debootstrap any more,
 some buildd chroots don't have an /etc/machine-id any more. Port the old
 Add-env-variable-for-machine-ID-path.patch to the current code, use a
 local machine-id again, and always make test suite failures fatal.
 (Closes: #851445)
 .
   [ Michael Biebl ]
   * gpt-auto-generator: support LUKS encrypted root partitions
 (Closes: #851475)
   * Switch to bfd linker on mips*
 The gold linker is currently producing broken libraries on mips*
 resulting in s

Bug#851549: marked as done (dbus: Segmentation fault in dbus.postinst on mips64el)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 13:20:18 +
with message-id 
and subject line Bug#851412: fixed in systemd 232-11
has caused the Debian Bug report #851412,
regarding dbus: Segmentation fault in dbus.postinst on mips64el
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.)


-- 
851412: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851412
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dbus
Version: 1.10.14-1
Severity: grave
Justification: renders package unusable

Current package on mips64el won't install. Segmentation fault will occur in
postinst script.

I don't have a mips64el box so cannot reproduce it, but examples are *all
around* official buildd.

This bug is preventing many packages from building and migrating to testing.

Examples: [1] [2]

[1] https://buildd.debian.org/status/fetch.php?pkg=kwallet-
kf5&arch=mips64el&ver=5.28.0-3&stamp=1484543446
[2]
https://buildd.debian.org/status/fetch.php?pkg=xfce4-terminal&ver=0.8.3-1&arch=mips64el&stamp=1484543729



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

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

Versions of packages dbus depends on:
ii  adduser  3.115
ii  init-system-helpers  1.46
ii  libapparmor1 2.11.0-1
ii  libaudit11:2.6.7-1
ii  libc62.24-8
ii  libcap-ng0   0.7.7-3
ii  libdbus-1-3  1.10.14-1
ii  libexpat12.2.0-2
ii  libselinux1  2.6-3
ii  libsystemd0  232-10
ii  lsb-base 9.20161125

dbus recommends no packages.

Versions of packages dbus suggests:
ii  dbus-user-session [default-dbus-session-bus]  1.10.14-1
ii  dbus-x11 [dbus-session-bus]   1.10.14-1

Versions of packages dbus is related to:
ii  dbus-x11  1.10.14-1
ii  systemd   232-10
ii  systemd-sysv  232-10

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 232-11

We believe that the bug you reported is fixed in the latest version of
systemd, 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.
Michael Biebl  (supplier of updated systemd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 18 Jan 2017 12:38:54 +0100
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote 
systemd-coredump libpam-systemd libnss-myhostname libnss-mymachines 
libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev libudev1 
libudev-dev udev-udeb libudev1-udeb
Architecture: source
Version: 232-11
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Michael Biebl 
Description:
 libnss-myhostname - nss module providing fallback resolution for the current 
hostname
 libnss-mymachines - nss module to resolve hostnames for local container 
instances
 libnss-resolve - nss module to resolve names via systemd-resolved
 libnss-systemd - nss module providing dynamic user and group name resolution
 libpam-systemd - system and service manager - PAM module
 libsystemd-dev - systemd utility library - development files
 libsystemd0 - systemd utility library
 libudev-dev - libudev development files
 libudev1   - libudev shared library
 libudev1-udeb - libudev shared library (udeb)
 systemd- system and service manager
 systemd-container - systemd container/nspawn tools
 systemd-coredump - tools for storing and retrieving coredumps
 systemd-journal-remote - tools for sending and receiving remote journal logs
 systemd-sysv - system and service manager - SysV links
 udev   - /dev/ and hotplug management daemon
 udev-udeb  - /dev/ and hotplug management daemon (udeb)
Closes: 851412 851445 851475 851492 851688
Changes:
 systemd (232-11) unstable; urgency=medium
 .
   [ Martin Pitt ]
   * Fix RestrictAddressFamilies=
 Backpor

Bug#848236: Remaining issue with gbrowse - any help (Was: Urgent call to BioPerl users (Was: Bug#848236: src:gbrowse: ...)

[Andreas Tille]

Hi Lincoln,

On Wed, Jan 18, 2017 at 07:07:55AM -0500, Lincoln Stein wrote:
> 
> There appears to be a new dependency on libbio-coordinate. Probably best to
> add a "use Bio::Coordinate" and the dependency to Bio::Graphics. Then the
> problem will disappear.

Cool.  In Debian terminology this means a new "Build-Depends" and after adding
libbio-coordinate-perl package to this the tests succeeded.  Thanks a lot for
your help and patience!

I now need to sort out some other issues with packaging and think I'll upload
soon.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#851233: [debian-mysql] Bug#851233: Bug#851233: Security fixes from the January 2017 CPU

[Salvatore Bonaccorso]

Hi Lars,

On Wed, Jan 18, 2017 at 12:45:45PM +0100, Lars Tangvald wrote:
> Hi,
> 
> On 01/18/2017 12:39 PM, Salvatore Bonaccorso wrote:
> >Hi Lars,
> >
> >On Wed, Jan 18, 2017 at 10:33:30AM +0100, Lars Tangvald wrote:
> >>Hi,
> >>
> >>The update builds and passes testing.
> >>I've attached debdiff output for Wheezy and Jessie for this update. Aside
> >>from the changelog, the only change to packaging is a patch for a test
> >>(main.events_2) that was failing because of a hardcoded date.
> >Thanks for preparing the update.
> >
> >>diff -r mysql-5.5-5.5.53/debian/changelog 
> >>../mysql-5.5/mysql-5.5/debian/changelog
> >>0a1,14
> >>>mysql-5.5 (5.5.54-0+deb8u1) jessie-security; urgency=high
> >>>
> >>>   * Imported upstream version 5.5.54 to fix security issues:
> >>> - 
> >>> http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html
> >>> - CVE-2017-3238 CVE-2017-3243 CVE-2017-3244 CVE-2017-3258
> >>> - CVE-2017-3265 CVE-2017-3291 CVE-2017-3312 CVE-2017-3313
> >>> - CVE-2017-3317 CVE-2017-3318
> >>> (Closes: #851233)
> >>>   * Fix failing test main.events_2
> >>> The test was failing due to hardcoded date (2017-01-01). Added patch
> >>> pending upstream fix.
> >>>
> >>>  -- Lars Tangvald   Tue, 17 Jan 2017 13:04:58 
> >>> +0100
> >This looks good, but see one change which seem included below:
> >
> >>5c19
> >>< - CVE-2016-7440 CVE-2016-5584
> >>---
> >>> - CVE-2016-6662 CVE-2016-7440 CVE-2016-5584
> >Did you build not on top of the last update? Because we corrected the
> >CVE ids in the 5.5.53-0+deb8u1 upload. CVE-2016-6662 does not belong
> >there, and was already fixed in the DSA-3666-1 with mysql-5.5
> >5.5.52-0+deb8u1, cf. the resulting changelog for 5.5.53-0+deb8u1 in
> >https://bugs.debian.org/841050#62 for the DSA-3666-1 upload . I don't
> >remember exactly, but I though I had asked someone of the mysql
> >packaging team to import the final changes to the packaging
> >repository.
> Aha, yes. I see the vcs hasn't got the 5.5.53 packages imported properly.
> I'll do the import and rebuild, thanks.

Thanks!

> >With that fixed, and build with -sa (to include the orig tarball)
> >please do upload to security-master.
> Do we have access to upload here? I think the security team have handled the
> upload in the past.

yes it nees to be a key in the DD keyring. Do you have a DD in the
mysql-pkg team who could sponsor the upload?

Regards,
Salvatore

Bug#851755: mariadb-10.0: CVE-2017-3238 CVE-2017-3243 CVE-2017-3244 CVE-2017-3257 CVE-2017-3258 CVE-2017-3265 CVE-2017-3291 CVE-2017-3312 CVE-2017-3317 CVE-2017-3318

[Salvatore Bonaccorso]

Source: mariadb-10.0
Version: 10.0.16-1
Severity: grave
Tags: security upstream

Hi

The following CVE's were addressed in 10.0.29 upstream, whereas
CVE-2016-6664 has already a seprate bug in the BTS:

CVE-2016-6664
CVE-2017-3238
CVE-2017-3243
CVE-2017-3244
CVE-2017-3257
CVE-2017-3258
CVE-2017-3265
CVE-2017-3291
CVE-2017-3312
CVE-2017-3317
CVE-2017-3318 

https://mariadb.com/kb/en/mariadb/mariadb-10029-release-notes/

Regards,
Salvatore

Processed: tagging 851755

[Debian Bug Tracking System]

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

> tags 851755 + fixed-upstream
Bug #851755 [src:mariadb-10.0] mariadb-10.0: CVE-2017-3238 CVE-2017-3243 
CVE-2017-3244 CVE-2017-3257 CVE-2017-3258 CVE-2017-3265 CVE-2017-3291 
CVE-2017-3312 CVE-2017-3317 CVE-2017-3318
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#851759: mariadb-10.1: CVE-2017-3238 CVE-2017-3243 CVE-2017-3244 CVE-2017-3257 CVE-2017-3258 CVE-2017-3265 CVE-2017-3291 CVE-2017-3312 CVE-2017-3317 CVE-2017-3318

[Salvatore Bonaccorso]

Source: mariadb-10.1
Version: 10.1.20-3
Severity: grave
Tags: upstream security fixed-upstream
Justification: user security hole

Hi

The following CVEs were fixed with a new upstream version 10.1.21,
whereas CVE-2016-6664 has already a separate bug in the BTS:

CVE-2016-6664
CVE-2017-3238
CVE-2017-3243
CVE-2017-3244
CVE-2017-3257
CVE-2017-3258
CVE-2017-3265
CVE-2017-3291
CVE-2017-3312
CVE-2017-3317
CVE-2017-3318 

https://mariadb.com/kb/en/mariadb/mariadb-10121-release-notes/

Regards,
Salvatore

Bug#841583: ruby-dataobjects-mysql: FTBFS: mysql_install_db: [ERROR] unknown option '--force'

[Andreas Beckmann]

Followup-For: Bug #841583
Control: block -1 with 851131

The --force problem is specific to mysql, it does not happen with
mariadb. But it fails differently on mariadb:

[...]
2017-01-18 13:52:53 140102037378944 [Note] /usr/sbin/mysqld (mysqld 
10.1.20-MariaDB-3) starting as process 3768 ...
2017-01-18 13:52:53 140102037378944 [Note] InnoDB: Using mutexes to ref count 
buffer pool pages
2017-01-18 13:52:53 140102037378944 [Note] InnoDB: The InnoDB memory heap is 
disabled
2017-01-18 13:52:53 140102037378944 [Note] InnoDB: Mutexes and rw_locks use GCC 
atomic builtins
2017-01-18 13:52:53 140102037378944 [Note] InnoDB: GCC builtin 
__atomic_thread_fence() is used for memory barrier
2017-01-18 13:52:53 140102037378944 [Note] InnoDB: Compressed tables use zlib 
1.2.8
2017-01-18 13:52:53 140102037378944 [Note] InnoDB: Using Linux native AIO
2017-01-18 13:52:53 140102037378944 [Note] InnoDB: Using SSE crc32 instructions
2017-01-18 13:52:53 140102037378944 [Note] InnoDB: Initializing buffer pool, 
size = 128.0M
2017-01-18 13:52:53 140102037378944 [Note] InnoDB: Completed initialization of 
buffer pool
2017-01-18 13:52:53 140102037378944 [Note] InnoDB: Highest supported file 
format is Barracuda.
2017-01-18 13:52:53 140102037378944 [Note] InnoDB: 128 rollback segment(s) are 
active.
2017-01-18 13:52:53 140102037378944 [Note] InnoDB: Waiting for purge to start
2017-01-18 13:52:53 140102037378944 [Note] InnoDB:  Percona XtraDB 
(http://www.percona.com) 5.6.34-79.1 started; log sequence number 1622838
2017-01-18 13:52:53 140102037378944 [Note] Plugin 'FEEDBACK' is disabled.
2017-01-18 13:52:53 140101342430976 [Note] InnoDB: Dumping buffer pool(s) not 
yet started
2017-01-18 13:52:53 140102037378944 [Note] /usr/sbin/mysqld: ready for 
connections.
Version: '10.1.20-MariaDB-3'  socket: '/tmp/tmp.mXSW0s03Pw/mysql.sock'  port: 0 
 Debian unstable
/usr/bin/mysqladmin: connect to server at 'localhost' failed
error: 'Access denied for user 'root'@'localhost''
ERROR 1698 (28000): Access denied for user 'root'@'localhost'
debian/rules:19: recipe for target 'override_dh_auto_install' failed

which seems to be another instance of #851131


Andreas

Processed: Re: ruby-dataobjects-mysql: FTBFS: mysql_install_db: [ERROR] unknown option '--force'

[Debian Bug Tracking System]

Processing control commands:

> block -1 with 851131
Bug #841583 [src:ruby-dataobjects-mysql] ruby-dataobjects-mysql: FTBFS: 
mysql_install_db: [ERROR] unknown option '--force'
841583 was not blocked by any bugs.
841583 was not blocking any bugs.
Added blocking bug(s) of 841583: 851131

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

Bug#848236: Remaining issue with gbrowse - any help (Was: Urgent call to BioPerl users (Was: Bug#848236: src:gbrowse: ...)

[Lincoln Stein]

Glad to be of help. No source changes to bio::graphics needed then?

At some point in near future I will be making changes to the exception
reporting in bio::graphics so that the error messages are more informative.

Lincoln

On Wed, Jan 18, 2017 at 8:30 AM Andreas Tille  wrote:

> Hi Lincoln,
>
>
>
> On Wed, Jan 18, 2017 at 07:07:55AM -0500, Lincoln Stein wrote:
>
> >
>
> > There appears to be a new dependency on libbio-coordinate. Probably best
> to
>
> > add a "use Bio::Coordinate" and the dependency to Bio::Graphics. Then the
>
> > problem will disappear.
>
>
>
> Cool.  In Debian terminology this means a new "Build-Depends" and after
> adding
>
> libbio-coordinate-perl package to this the tests succeeded.  Thanks a lot
> for
>
> your help and patience!
>
>
>
> I now need to sort out some other issues with packaging and think I'll
> upload
>
> soon.
>
>
>
> Kind regards
>
>
>
>Andreas.
>
>
>
> --
>
> http://fam-tille.de
>
> --
Written on my cell phone. Anything that seems odd is the fault of
auto-correct.

Processed: retitle 851755 to mariadb-10.0: CVE-2016-6664 CVE-2017-3238 CVE-2017-3243 CVE-2017-3244 CVE-2017-3257 CVE-2017-3258 CVE-2017-3265 CVE-2017-3291 CVE-2017-3312 CVE-2017-3317 CVE-2017-3318 ...

[Debian Bug Tracking System]

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

> # including CVE-2016-6664 as well in list
> retitle 851755 mariadb-10.0: CVE-2016-6664 CVE-2017-3238 CVE-2017-3243 
> CVE-2017-3244 CVE-2017-3257 CVE-2017-3258 CVE-2017-3265 CVE-2017-3291 
> CVE-2017-3312 CVE-2017-3317 CVE-2017-3318
Bug #851755 [src:mariadb-10.0] mariadb-10.0: CVE-2017-3238 CVE-2017-3243 
CVE-2017-3244 CVE-2017-3257 CVE-2017-3258 CVE-2017-3265 CVE-2017-3291 
CVE-2017-3312 CVE-2017-3317 CVE-2017-3318
Changed Bug title to 'mariadb-10.0: CVE-2016-6664 CVE-2017-3238 CVE-2017-3243 
CVE-2017-3244 CVE-2017-3257 CVE-2017-3258 CVE-2017-3265 CVE-2017-3291 
CVE-2017-3312 CVE-2017-3317 CVE-2017-3318' from 'mariadb-10.0: CVE-2017-3238 
CVE-2017-3243 CVE-2017-3244 CVE-2017-3257 CVE-2017-3258 CVE-2017-3265 
CVE-2017-3291 CVE-2017-3312 CVE-2017-3317 CVE-2017-3318'.
> # including CVE-2016-6664 as well in list
> retitle 851759 mariadb-10.1: CVE-2016-6664 CVE-2017-3238 CVE-2017-3243 
> CVE-2017-3244 CVE-2017-3257 CVE-2017-3258 CVE-2017-3265 CVE-2017-3291 
> CVE-2017-3312 CVE-2017-3317 CVE-2017-3318
Bug #851759 [src:mariadb-10.1] mariadb-10.1: CVE-2017-3238 CVE-2017-3243 
CVE-2017-3244 CVE-2017-3257 CVE-2017-3258 CVE-2017-3265 CVE-2017-3291 
CVE-2017-3312 CVE-2017-3317 CVE-2017-3318
Changed Bug title to 'mariadb-10.1: CVE-2016-6664 CVE-2017-3238 CVE-2017-3243 
CVE-2017-3244 CVE-2017-3257 CVE-2017-3258 CVE-2017-3265 CVE-2017-3291 
CVE-2017-3312 CVE-2017-3317 CVE-2017-3318' from 'mariadb-10.1: CVE-2017-3238 
CVE-2017-3243 CVE-2017-3244 CVE-2017-3257 CVE-2017-3258 CVE-2017-3265 
CVE-2017-3291 CVE-2017-3312 CVE-2017-3317 CVE-2017-3318'.
> thanks
Stopping processing here.

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

Processed: Re: cfengine3: switch to build depend on the metapackage default-libmysqlclient-dev

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #845829 [cfengine3] cfengine3: switch to build depend on the metapackage 
default-libmysqlclient-dev
Added tag(s) pending.

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

Bug#845829: cfengine3: switch to build depend on the metapackage default-libmysqlclient-dev

[Andreas Beckmann]

Control: tag -1 pending

On 2017-01-17 02:21, Andreas Beckmann wrote:
> attached is a patch to fix this (and another) issue.
> If you need help, I could also upload this as a NMU.

I now uploaded this as a NMU to DELAYED/2 since cfengine3 is the last
(fixable) package in stretch blocking the mariadb transition. All others
are fixed in sid (or a delayed NMU to sid) waiting to migrate, except
for two ruby packages that need more work and will probably be removed
from stretch.


Andreas

Bug#848236: Remaining issue with gbrowse - any help (Was: Urgent call to BioPerl users (Was: Bug#848236: src:gbrowse: ...)

[gregor herrmann]

On Wed, 18 Jan 2017 14:00:47 +, Lincoln Stein wrote:

> Glad to be of help. No source changes to bio::graphics needed then?

Probably that too :)
I'll take a look later today.
 
Thanks for your efforts and your enormous help!


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   BOFH excuse #267:  The UPS is on strike. 

Bug#851233: [debian-mysql] Bug#851233: Bug#851233: Security fixes from the January 2017 CPU

[Lars Tangvald]

- car...@debian.org wrote:


> > >With that fixed, and build with -sa (to include the orig tarball)
> > >please do upload to security-master.
> > Do we have access to upload here? I think the security team have
> handled the
> > upload in the past.
> 
> yes it nees to be a key in the DD keyring. Do you have a DD in the
> mysql-pkg team who could sponsor the upload?
> 

Not really, unfortunately (Otto is a DD, but he's only involved with the 
MariaDB packaging).
It's an issue for us, since it also causes problems with uploads to unstable.

--
Lars

Bug#851293: marked as done (CVE-2016-9590)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 15:08:39 +
with message-id 
and subject line Bug#851293: fixed in puppet-module-swift 9.4.4-1
has caused the Debian Bug report #851293,
regarding CVE-2016-9590
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.)


-- 
851293: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: puppet-module-swift
Severity: grave
Tags: security

Hi,
please see https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2016-9590
for details.

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: puppet-module-swift
Source-Version: 9.4.4-1

We believe that the bug you reported is fixed in the latest version of
puppet-module-swift, 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.
Ondřej Kobližek  (supplier of updated puppet-module-swift 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 18 Jan 2017 14:23:19 +0100
Source: puppet-module-swift
Binary: puppet-module-swift
Architecture: source all
Version: 9.4.4-1
Distribution: unstable
Urgency: medium
Maintainer: PKG OpenStack 
Changed-By: Ondřej Kobližek 
Description:
 puppet-module-swift - Puppet module for OpenStack Swift
Closes: 851293
Changes:
 puppet-module-swift (9.4.4-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release (Closes: #851293, CVE-2016-9590)
Checksums-Sha1:
 f77732e3a52b2587b0cade7ccc32536a244fd143 2096 puppet-module-swift_9.4.4-1.dsc
 1bf7563abec35c7552d481d36749853008c5dc8b 64588 
puppet-module-swift_9.4.4.orig.tar.xz
 fec6dc2315fbc762640dfe26ef0b6075962ef112 2720 
puppet-module-swift_9.4.4-1.debian.tar.xz
 203c3ce5d18058e7505aa89280140f2483b1d108 61716 
puppet-module-swift_9.4.4-1_all.deb
 a9ab06dc1a00f46fc589259134ba7b93cc1267ea 6562 
puppet-module-swift_9.4.4-1_amd64.buildinfo
Checksums-Sha256:
 8deb8caaf1f19b4054b605d4bc8d5d49c6a4c86996347404f44fd9d0410cb708 2096 
puppet-module-swift_9.4.4-1.dsc
 c2dbdd84605fa547f0741c1e6cca22d0639f70227fa084ca7e90e006e10b5d45 64588 
puppet-module-swift_9.4.4.orig.tar.xz
 321a7a4df28a0a44bb0c9da257f005b390f6a508c86b54b9be098f848497362a 2720 
puppet-module-swift_9.4.4-1.debian.tar.xz
 199143275e731aca63a280a1faa2206e5dce72ac08a7ddbbcc0004d59d84b73e 61716 
puppet-module-swift_9.4.4-1_all.deb
 b448da09b61c2a2e9b6fb8890d988b95ce75779f46031c3e85e70825fb708339 6562 
puppet-module-swift_9.4.4-1_amd64.buildinfo
Files:
 51dd73294b1572198ed71099e9c550da 2096 admin extra 
puppet-module-swift_9.4.4-1.dsc
 5a4e42e7393655a151fb2c5b363efef9 64588 admin extra 
puppet-module-swift_9.4.4.orig.tar.xz
 f7370c6cf957d42c06b92f8fe0fcbdaf 2720 admin extra 
puppet-module-swift_9.4.4-1.debian.tar.xz
 a1ec66ffe873330b2eeefb88beb5d042 61716 admin extra 
puppet-module-swift_9.4.4-1_all.deb
 7af43f2548c6aaad64d85e9c2ca273eb 6562 admin extra 
puppet-module-swift_9.4.4-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEPZg8UuuFmAxGpWCQNXMSVZ0eBksFAlh/fesACgkQNXMSVZ0e
BktmmA/+KJEkodvTKETn5dRowF1CXa1y8/mZesSBQcjlHuSVBq4PCqVnLeyC8ixI
yrU7btbXXKyauJ7iSnssX38PdHljd3HZmLx1AOBzbWhQ8VuuFAAFH+w6ElDfqWjX
Jyk66KLDhXnMC9HqkgrvZYvEaYJFUa0uPlyYqSFZD/OJQnrRRDClq3yeewZjKmtK
O/G/aJ8q0Dh0N8RC+9DKqZs9UEdUrEEpn1N6pTskeuHMN10YYoRrpxCWHKjxR/jv
OxduIlLfCMoeA3qYNX9LScJA3dAjX6xpzdTCeXxOaJ1zcQoHXL5Fdr8WcOaZalc8
xqqApYBqddOgx3zEN90tnW5kJPCq4wchznMYnr0dH80I/o700zUjGe0cdf3KbXyy
dGzXWER9lg01vcDVSGuuwI8JSPFiAw7ytBWJ5yt+kPeqr948IcoHViahw0pBTTpE
RAiGEL86xvMsM1rEwb7FF1BjOB2FCKM0yklezm/wxNVZcNRXrHO498ZkA4z6Qdkl
7VmlveNZBqmO5mMPyvfH8xnaxBXQszhV7OjXL3aEcFk04KN9DILJS+7gJDlNMEyw
qur2UHbYk3o8ViYUzBegEErHaKwEhOEiMe8r84mV+snAsdv9OxzNZCLFOQnPBKMU
/UCR1pA+lFYvKn1CkZchrRVy5HDqOn5UGIoeSNxcvLvqcMlhPs0=
=g9er
-END PGP SIGNATURE End Message ---

Bug#845899: marked as done (python-mysqldb: switch to build depend on the metapackage default-libmysqlclient-dev)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 15:08:44 +
with message-id 
and subject line Bug#845899: fixed in python-mysqldb 1.3.7-1.1
has caused the Debian Bug report #845899,
regarding python-mysqldb: switch to build depend on the metapackage 
default-libmysqlclient-dev
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.)


-- 
845899: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845899
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-mysqldb
Severity: important

Hi! 

This package build depends on libmysqlclient-dev. It should instead
build-depend on default-libmysqlclient-dev metapackage, and end up
having the run-time dependency of the libmysqlclient implementation
Debian has chosen to use, currently MariaDB instead of Oracle MySQL. 

Announcement of new default-mysql-* metapackages:
https://lists.debian.org/debian-devel-announce/2016/09/msg0.html 

Wiki: https://wiki.debian.org/Teams/MySQL/default-mysql-server 

MBF: https://lists.debian.org/debian-devel/2016/11/msg00832.html 

Please update the depencies accordingly. In most cases the required
change is: 

* BEFORE: Build-Depends: libmysqlclient-dev 

* AFTER: Build-Depends: default-libmysqlclient-dev 

Thanks, 

Otto 
--- End Message ---
--- Begin Message ---
Source: python-mysqldb
Source-Version: 1.3.7-1.1

We believe that the bug you reported is fixed in the latest version of
python-mysqldb, 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 845...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated python-mysqldb package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 16 Jan 2017 14:51:04 +0100
Source: python-mysqldb
Binary: python-mysqldb python-mysqldb-dbg python3-mysqldb python3-mysqldb-dbg
Architecture: source
Version: 1.3.7-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Andreas Beckmann 
Description:
 python-mysqldb - Python interface to MySQL
 python-mysqldb-dbg - Python interface to MySQL (debug extension)
 python3-mysqldb - Python interface to MySQL
 python3-mysqldb-dbg - Python interface to MySQL (debug extension)
Closes: 738180 845899 848484 848485
Changes:
 python-mysqldb (1.3.7-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Switch Build-Depends to default-libmysqlclient-dev.  (Closes: #845899)
   * Switch Suggests to default-mysql-* | virtual-mysql-*.
 (Closes: #848484, #848485)
   * Remove Monty Taylor from Uploaders.  (Closes: #738180)
   * Run dh_strip with option --no-automatic-dbgsym to avoid generation of
 -dbg-dbgsym packages.
Checksums-Sha1:
 75615306158f96bdd42a92483f06313aa7182490 2425 python-mysqldb_1.3.7-1.1.dsc
 4bee7c89d5c9f9b84a7217aa26af66b4ba6a4666 8992 
python-mysqldb_1.3.7-1.1.debian.tar.xz
Checksums-Sha256:
 758d7153836f8085c7e0ac6c424bfad2623faadde8341de7eb0276e4d6c0 2425 
python-mysqldb_1.3.7-1.1.dsc
 b969f64e88a8f8a6cd356f3f206f6ea7ae466e50986b4c87588fc3921e4c6a6d 8992 
python-mysqldb_1.3.7-1.1.debian.tar.xz
Files:
 94b3368d51eb4a6b63a6ea8916b9243b 2425 python optional 
python-mysqldb_1.3.7-1.1.dsc
 b9c089939a25aa9e1777220db0f99e4b 8992 python optional 
python-mysqldb_1.3.7-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJYfNCXAAoJEF+zP5NZ6e0Iw4cP/3WQ4i/CL6dUIVihi33vTvbP
N5i/YiclyzvtqVlRUXbAExSqpBlJ1uG69C0MU+pR7qFCR6VUyRTLWmUwsG6AY+3m
jbBPB4780IeHOLNT8J6N4Gd/okVC2PHORZJPfttifS6J+YYdA6tmmPxpMXPpSU/3
4MJ6BXX24BS0DnMZRpxp1zF6v7SycC6cDnNLfWLgQIqe+4mlJCv8NsA9VSQBYeYy
br2E11agGpbNVEJw1emufgJo9IIdlm/hVkx8Ag0zTkSixPuI9a8fkRXd5OgvJgXH
62jIwcJGEYM7WE5+D/O2k9eTi3Lxw8rkXbZ1QrzbJx+vqPat7YqXiLYU/+9+gHtL
vmBZJtKFQEhjKiCVtKnpFqZG8ik7t11782x9TDe4JFqqtJrTol03B0oSY1SZuH6V
QbTmrNsWLMZjbyhScUzCzBaYsg7Mmk0KH24CvlOt4xdA/9ZPNQpfhRo2HlDUiSCH
FJ/+bURugyCga3YWg+0mc6aDju7iSN48ko9tYsALmMJ5K2lrYUf7HSAODqi7Adu/
e/nOeqTL677BzpPNE6Wk0i0igJiPIf1LjjUa4sJXXz3MwpB+/Img/LnnuZLx794g
47htNDfyqFumCbSLLJHlsTGsXh6ZGfDpcGeRjx07mFIXQunmXFX6ts5Octx4BkSR
RrhUIncLwfJkR7aDeg8k
=4vzP
-END PGP SIGNATURE End Message ---

Bug#851233: [debian-mysql] Bug#851233: Bug#851233: Security fixes from the January 2017 CPU

[Salvatore Bonaccorso]

Hi Lars,

On Wed, Jan 18, 2017 at 06:41:40AM -0800, Lars Tangvald wrote:
> 
> - car...@debian.org wrote:
> 
> 
> > > >With that fixed, and build with -sa (to include the orig tarball)
> > > >please do upload to security-master.
> > > Do we have access to upload here? I think the security team have
> > handled the
> > > upload in the past.
> > 
> > yes it nees to be a key in the DD keyring. Do you have a DD in the
> > mysql-pkg team who could sponsor the upload?
> > 
> 
> Not really, unfortunately (Otto is a DD, but he's only involved with
> the MariaDB packaging).
> It's an issue for us, since it also causes problems with uploads to
> unstable.

Ok. I though in the past James Page was sponsoring the uploads.
Alright, in that case, let me know when you have finished the
packaging with the small changes mentioned, I can take care of
sponsoring the upload.

Regards,
Salvatore

Bug#851714: marked as done (gitlab: Cannot push to gitlab repositories with git >= 2.11.0)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 15:33:49 +
with message-id 
and subject line Bug#851714: fixed in gitlab 8.13.11+dfsg-1
has caused the Debian Bug report #851714,
regarding gitlab: Cannot push to gitlab repositories with git >= 2.11.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.)


-- 
851714: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 8.13.6+dfsg2-2
Severity: grave

Dear Maintainer,

Gitlab repositories will no longer accept remote pushes to protected branches
(which is the default!) with git 2.11.0 installed on the gitlab system, failing
with:

remote: GitLab: You are not allowed to force push code to a protected branch on 
this project.
To (sitename):(user)/(repo).git
 ! [remote rejected] master -> master (pre-receive hook declined)

even for ordinary, non-forced pushes.

This is upstream bug https://gitlab.com/gitlab-org/gitlab-ce/issues/25301

Since gitlab seems pretty useless without the ability to push to a repository
by default, I've marked this grave.


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

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

Versions of packages gitlab depends on:
ii  adduser   3.115
ii  apache2 [httpd]   2.4.25-1
ii  asciidoctor   1.5.4-2
ii  bc1.06.95-9+b2
ii  bundler   1.13.6-2
ii  debconf [debconf-2.0] 1.5.59
ii  git   1:2.11.0-2
ii  gitlab-shell  3.6.6-1
ii  gitlab-workhorse  0.8.5+debian-3
ii  init-system-helpers   1.46
ii  libjs-chartjs 1.0.2-1
ii  libjs-clipboard   1.4.2-1
ii  libjs-fuzzaldrin-plus 0.3.1+git.20161008.da2cb58+dfsg-4
ii  libjs-graphael0.5+dfsg-1
ii  libjs-jquery-cookie   11-3
ii  libjs-jquery-history  11-3
ii  libjs-jquery-nicescroll   3.6.6-1
ii  lsb-base  9.20161125
ii  nodejs4.7.2~dfsg-1
ii  openssh-client1:7.4p1-5
ii  postfix [mail-transport-agent]3.1.3-6
ii  postgresql-client 9.6+178
ii  postgresql-client-9.6 [postgresql-client  9.6.1-2
ii  postgresql-contrib9.6+178
ii  rake  10.5.0-2
pn  redis-server  
ii  ruby  1:2.3.3
ii  ruby-ace-rails-ap 4.1.1-1
ii  ruby-activerecord-session-store   1.0.0-2
ii  ruby-acts-as-taggable-on  4.0.0-2
ii  ruby-addressable  2.4.0-1
ii  ruby-after-commit-queue   1.3.0-1
ii  ruby-akismet  2.0.0-1
ii  ruby-allocations  1.0.3-1+b2
ii  ruby-asana0.4.0-1
ii  ruby-attr-encrypted   3.0.1-2
ii  ruby-babosa   1.0.2-2
ii  ruby-base32   0.3.2-3
ii  ruby-bootstrap-sass   3.3.5.1-3
ii  ruby-browser  2.2.0-2
ii  ruby-cal-heatmap-rails3.6.0+dfsg-1
ii  ruby-carrierwave  0.10.0+gh-4
ii  ruby-charlock-holmes  0.7.3+dfsg-2+b3
ii  ruby-chronic  0.10.2-3
ii  ruby-chronic-duration 0.10.6-1
ii  ruby-coffee-rails 4.1.0-2
ii  ruby-coffee-script-source 1.10.0-1
ii  ruby-connection-pool  2.2.0-1
ii  ruby-creole   0.5.0-2
ii  ruby-d3-rails 3.5.6+dfsg-1
ii  ruby-default-value-for3.0.1-1
ii  ruby-devise   4.2.0-1
ii  ruby-devise-two-factor3.0.0-2
ii  ruby-diffy3.0.6-1
ii  ruby-doorkeeper   4.2.0-3
ii  ruby-dropzonejs-rails 0.7.1-1
ii  ruby-

Bug#851767: chromium: Line 21 in the startup script /usr/bin/chromium is missing a terminating quote.

[Grigor Gatchev]

Package: chromium
Version: 55.0.2883.75-4
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I upgraded package chromium to 55.0.2883-75.4. After that, the Chromium browser 
would not run.
I browsed the starting script /usr/bin/chromium and noticed that the string in 
line 21 is
missing a terminating quote. After adding that quote, the script worked OK.

Could you please add that quote?

Thank you for your service to the Debian community and users,

Grigor


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

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

Versions of packages chromium depends on:
ii  libasound2   1.1.2-1
ii  libatk1.0-0  2.22.0-1
ii  libavcodec57 7:3.2.2-1
ii  libavformat577:3.2.2-1
ii  libavutil55  7:3.2.2-1
ii  libc62.24-9
ii  libcairo21.14.8-1
ii  libcups2 2.2.1-5
ii  libdbus-1-3  1.10.14-1
ii  libevent-2.0-5   2.0.21-stable-2.1
ii  libexpat12.2.0-2
ii  libflac8 1.3.2-1
ii  libfontconfig1   2.11.0-6.7
ii  libfreetype6 2.6.3-3+b1
ii  libgcc1  1:6.3.0-2
ii  libgdk-pixbuf2.0-0   2.36.4-1
ii  libglib2.0-0 2.50.2-2
ii  libgtk2.0-0  2.24.31-1
ii  libharfbuzz0b1.2.7-1+b1
ii  libicu57 57.1-5
ii  libjpeg62-turbo  1:1.5.1-2
ii  libminizip1  1.1-8
ii  libnspr4 2:4.12-6
ii  libnss3  2:3.26.2-1
ii  libpango-1.0-0   1.40.3-3
ii  libpangocairo-1.0-0  1.40.3-3
ii  libpng16-16  1.6.28-1
ii  libpulse09.0-5
ii  libre2-3 20170101+dfsg-1
ii  libsnappy1v5 1.1.3-3
ii  libstdc++6   6.3.0-2
ii  libvpx4  1.6.1-2
ii  libwebp6 0.5.2-1
ii  libwebpdemux20.5.2-1
ii  libx11-6 2:1.6.4-2
ii  libx11-xcb1  2:1.6.4-2
ii  libxcb1  1.12-1
ii  libxcomposite1   1:0.4.4-1
ii  libxcursor1  1:1.1.14-1+b1
ii  libxdamage1  1:1.1.4-2+b1
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.3-1
ii  libxi6   2:1.7.8-2
ii  libxml2  2.9.4+dfsg1-2.1
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxslt1.1   1.1.29-2
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.3-1
ii  x11-utils7.7+3
ii  xdg-utils1.1.1-1
ii  zlib1g   1:1.2.8.dfsg-4

Versions of packages chromium recommends:
ii  fonts-liberation  1:1.07.4-2

Versions of packages chromium suggests:
pn  chromium-driver
pn  chromium-l10n  
pn  chromium-shell 
pn  chromium-widevine  

-- no debconf information

Bug#796609: fcoe-utils: Has init script in runlevel S but no matching service file

[Yann Richard]

Le 17/01/2017 à 14:01, Felipe Sateler a écrit :

Hi Yann,

On 17 January 2017 at 06:54, Yann Richard  wrote:

Hi,

We have made a package from fcoe-utils source version 1.0.31 which fix init bug 
:

https://github.com/DSI-Universite-Rennes2/fcoe-utils

Tested on HP 465c G8 on Ethernet controller: Broadcom Limited BCM57840 
NetXtreme II 10/20-Gigabit Ethernet (rev 11) in HP C7000 enclosure with
HP VC FlexFabric-20/40 F8 Module

Any Debian maintainer or developer would like to verify and push this into 
stretch ?

Could you please post this as a patch against the current debian
package? The linked git repository contains the entire debian
directory as a single commit. Moreover, that commit includes build
artifacts (eg, the scripts generated by debhelper), so that makes
review harder.


Hi,

In attachement debian's directory patch for 
fcoe-utils-1.0.29+git20140505 version.


It contains 9 patchs from OpenSuse.

At boot both systemd service and socket are successfully loaded and 
active but no host in /sys/class/fc_host/ are present (we expected them 
to be..). But they are after ifdown/ifup the interface.


We think there is a bug on this version and we'll try to test 1.0.31 or 
HEAD git version (not modified since 6 month).


Best Regards,

--
 🐧 M. Yann Richard
 🎓 Université Rennes 2
 Direction du Système d'Information
  Pôle Infrastructure / Serveurs
 🔗 http://www.univ-rennes2.fr/dsi

diff --git a/patches/0028-systemctl-cannot-start-fcoemon.socket.patch b/patches/0028-systemctl-cannot-start-fcoemon.socket.patch
index e69de29..a80f1a8 100644
--- a/patches/0028-systemctl-cannot-start-fcoemon.socket.patch
+++ b/patches/0028-systemctl-cannot-start-fcoemon.socket.patch
@@ -0,0 +1,31 @@
+From 444f3c66ee5a2b59a563d78cb70db7da2326d446 Mon Sep 17 00:00:00 2001
+From: Hannes Reinecke 
+Date: Fri, 21 Mar 2014 14:46:40 +0100
+Subject: systemctl cannot start fcoemon.socket
+
+systemctl start fcoemon.socket fails, as systemd cannot find
+the referenced service.
+
+References: bnc#869392
+
+Signed-off-by: Hannes Reinecke 
+---
+ etc/systemd/fcoemon.socket | 4 
+ 1 file changed, 4 insertions(+)
+
+diff --git a/etc/systemd/fcoemon.socket b/etc/systemd/fcoemon.socket
+index 4de8715..fdf7141 100644
+--- a/etc/systemd/fcoemon.socket
 b/etc/systemd/fcoemon.socket
+@@ -1,4 +1,8 @@
++[Unit]
++Description=Open-FCoE daemon control socket
++
+ [Socket]
++Service=fcoe.service
+ ListenDatagram=@/com/intel/fcoemon
+ PassCredentials=true
+ 
+-- 
+1.8.1.4
+
diff --git a/patches/0029-fcoemon-Correctly-handle-options-in-the-service-file.patch b/patches/0029-fcoemon-Correctly-handle-options-in-the-service-file.patch
index e69de29..b99cbef 100644
--- a/patches/0029-fcoemon-Correctly-handle-options-in-the-service-file.patch
+++ b/patches/0029-fcoemon-Correctly-handle-options-in-the-service-file.patch
@@ -0,0 +1,121 @@
+From 5216ae2ef4434d92ff3d49c4d5a7b73b438aee2d Mon Sep 17 00:00:00 2001
+From: Hannes Reinecke 
+Date: Fri, 11 Apr 2014 15:38:26 +0200
+Subject: fcoemon: Correctly handle options in the service file
+
+When runnig under systemd we can't really modify the arguments
+to provide an 'FCOEMON_OPTS' variable. Instead we should be
+modifying fcoemon --debug and --syslog to accept 'yes' or 'no'
+as parameters; that way we can use the variables directly.
+
+References: bnc#872732
+
+Signed-off-by: Hannes Reinecke 
+---
+ doc/fcoemon.txt  |  6 +++---
+ etc/systemd/fcoe.service |  4 ++--
+ fcoemon.c| 24 +++-
+ 3 files changed, 20 insertions(+), 14 deletions(-)
+
+diff --git a/doc/fcoemon.txt b/doc/fcoemon.txt
+index 7ccf892..7449601 100644
+--- a/doc/fcoemon.txt
 b/doc/fcoemon.txt
+@@ -53,13 +53,13 @@ OPTIONS
+ ---
+ *-f*, *--foreground*::
+ 	Run *fcoemon* in the foreground.
+-*-d*, *--debug*::
+-	Enable debugging messages.
++*-d*, *--debug=yes|no*::
++	Enable or disable debugging messages.
+ *-l*, *--legacy*::
+ 	Force fcoemon to use the legacy /sys/module/libfcoe/parameters/
+ 	interface. The default is to use the newer /sys/bus/fcoe/ interfaces
+ 	if they are available.
+-*-s*, *--syslog*::
++*-s*, *--syslog=yes|no*::
+ 	Use syslogd for logging. The default behavior is to log to stdout
+ 	and stderr.
+ *-h*, *--help*::
+diff --git a/etc/systemd/fcoe.service b/etc/systemd/fcoe.service
+index 5e5c8a2..2e10bcd 100644
+--- a/etc/systemd/fcoe.service
 b/etc/systemd/fcoe.service
+@@ -4,9 +4,9 @@ After=syslog.target network.target
+ 
+ [Service]
+ Type=simple
+-EnvironmentFile=/etc/sysconfig/fcoe
++EnvironmentFile=/etc/fcoe/config
+ ExecStartPre=/sbin/modprobe -qa $SUPPORTED_DRIVERS
+-ExecStart=/usr/sbin/fcoemon $FCOEMON_OPTS
++ExecStart=/usr/sbin/fcoemon --debug=$DEBUG --syslog=$SYSLOG
+ 
+ [Install]
+ WantedBy=multi-user.target
+diff --git a/fcoemon.c b/fcoemon.c
+index 5e4f8d7..23fc2f6 100644
+--- a/fcoemon.c
 b/fcoemon.c
+@@ -336,9 +336,9 @@ static int fcoe_vid_from_ifname(const char *ifname);
+  * Table for getopt_long(3).
+  */
+ static struct option fcm_optio

Bug#851233: [debian-mysql] Bug#851233: Bug#851233: Security fixes from the January 2017 CPU

[Lars Tangvald]

- car...@debian.org wrote:

> Hi Lars,
> 
> On Wed, Jan 18, 2017 at 06:41:40AM -0800, Lars Tangvald wrote:
> > 
> > - car...@debian.org wrote:
> > 
> > 
> > > > >With that fixed, and build with -sa (to include the orig
> tarball)
> > > > >please do upload to security-master.
> > > > Do we have access to upload here? I think the security team
> have
> > > handled the
> > > > upload in the past.
> > > 
> > > yes it nees to be a key in the DD keyring. Do you have a DD in
> the
> > > mysql-pkg team who could sponsor the upload?
> > > 
> > 
> > Not really, unfortunately (Otto is a DD, but he's only involved
> with
> > the MariaDB packaging).
> > It's an issue for us, since it also causes problems with uploads to
> > unstable.
> 
> Ok. I though in the past James Page was sponsoring the uploads.
> Alright, in that case, let me know when you have finished the
> packaging with the small changes mentioned, I can take care of
> sponsoring the upload.
> 
I might be going a bit senile, since I forgot he's got access as well, but for 
the last months he's been occupied, so I don't think he's available now.
I'll let you know when the new build is ready, thanks.

--
Lars
> Regards,
> Salvatore

Bug#737167: marked as done (xfonts-wqy: prompting due to modified conffiles which were not modified by the user)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 16:06:02 +
with message-id 
and subject line Bug#737167: fixed in xfonts-wqy 1.0.0~rc1-3
has caused the Debian Bug report #737167,
regarding xfonts-wqy: prompting due to modified conffiles which were not 
modified by the user
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.)


-- 
737167: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xfonts-wqy
Version: 0.9.9-8
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed the piuparts
upgrade test because dpkg detected a conffile as being modified and then
prompted the user for an action. As there is no user input, this fails.
But this is not the real problem, the real problem is that this prompt
shows up in the first place, as there was nobody modifying this conffile
at all, the package has just been installed and upgraded...

This is a violation of policy 10.7.3, see
http://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3,
which says "[These scripts handling conffiles] must not ask unnecessary
questions (particularly during upgrades), and must otherwise be good
citizens."

http://wiki.debian.org/DpkgConffileHandling should help with figuring
out how to do this properly.

In http://lists.debian.org/debian-devel/2009/08/msg00675.html and
followups it has been agreed that these bugs are to be filed with
severity serious.

This was observed on an upgrade from wheezy to jessie to sid.

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

  Setting up xfonts-wqy (0.9.9-8) ...
  
  Configuration file '/etc/X11/fonts/misc/xfonts-wqy.alias'
   ==> Deleted (by you or by a script) since installation.
   ==> Package distributor has shipped an updated version.
 What would you like to do about it ?  Your options are:
  Y or I  : install the package maintainer's version
  N or O  : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
   The default action is to keep your current version.
  *** xfonts-wqy.alias (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing 
package xfonts-wqy (--configure):
   EOF on stdin at conffile prompt
  Processing triggers for libc-bin (2.17-97) ...
  Errors were encountered while processing:
   xfonts-wqy
  E: Sub-process /usr/bin/dpkg returned an error code (1)


cheers,

Andreas


xfonts-wqy_0.9.9-8.log.gz
Description: GNU Zip compressed data
--- End Message ---
--- Begin Message ---
Source: xfonts-wqy
Source-Version: 1.0.0~rc1-3

We believe that the bug you reported is fixed in the latest version of
xfonts-wqy, 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 737...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
ChangZhuo Chen (陳昌倬)  (supplier of updated xfonts-wqy 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 18 Jan 2017 23:44:24 +0800
Source: xfonts-wqy
Binary: xfonts-wqy
Architecture: source
Version: 1.0.0~rc1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Fonts Task Force 
Changed-By: ChangZhuo Chen (陳昌倬) 
Description:
 xfonts-wqy - WenQuanYi Bitmap Song CJK font for X
Closes: 737167
Changes:
 xfonts-wqy (1.0.0~rc1-3) unstable; urgency=medium
 .
   * Rename /etc/X11/fonts/misc/xfonts-wqy.alias to fix wrongly placed
 fonts.alias file (Closes: #737167).
Checksums-Sha1:
 a45a04b151a6970d624f89c2cb2e0adef9c046c6 2053 xfonts-wqy_1.0.0~rc1-3.dsc
 89575a1b97b8a0268b4169c5e1ae5b5647d2baae 13056 
xfonts-wqy_1.0.0~rc1-3.debian.tar.xz
Checksums-Sha256:
 9ebb1a4d45b758b667912205625bf5e4ce112e52337bc15a508b724a04bb0fff 2053 
xfonts-wqy_1.0.0~rc1-3.dsc
 a5fa6ad4a847272f31a90e521213f9fb32cdf1508cad6f23c7c828d27de2039f 13056 
xfonts-wqy_1.0.0~rc1-3.debian.tar.xz
Files:
 8eef6d92952df514a55b4821a0b55a56 2053 fonts optional xfonts-wqy_1.0.0~rc1-3.dsc
 ac276225131ac769e22107c0f9d5dbac 13056 fonts optional 
xfonts-wqy_1.0.0~rc1-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEE5H9tOJ8ReWWaF1PGrc2MXdaTaQFAlh/jz4ACgkQGrc2M

Bug#835189: python-pyrax: FTBFS (failing tests)

[Sascha Girrulat]

thx for the update. I try to handle it asap. I'm only short of time at
the moment.

Regards
Sascha

Am 17.01.2017 um 01:50 schrieb Santiago Vila:
> retitle 835189 python-pyrax: FTBFS (failing tests)
> thanks
> 
> Hi.
> 
> After building this package many times today, it always fail
> and not just sometimes, so I'm retitling accordingly.
> 
> As a summary, I see that the following tests always fail:
> 
> ERROR: test_set_http_debug (tests.unit.test_module.PyraxInitTest)
> ERROR: test_connect_to_cloudservers (tests.unit.test_module.PyraxInitTest)
> 
> and the following one fails approximately 70% of the time:
> 
> ERROR: test_rax_endpoints (tests.unit.test_identity.IdentityTest)
> 
> [ The first two failing tests are the ones reported by Lucas Nussbaum
>   in Bug #841623 ].
> 
> Thanks.
> 



signature.asc
Description: OpenPGP digital signature

Bug#851769: 389-ds-base: CVE-2017-2591

[Salvatore Bonaccorso]

Source: 389-ds-base
Version: 1.3.5.15-1
Severity: grave
Tags: security upstream patch
Justification: user security hole

Hi,

the following vulnerability was published for 389-ds-base. Choosed
severity > important, since possibly as well triggerable by
unauthenticated attackers, but I'm not too familiar if that setup is
common.

CVE-2017-2591[0]:
DoS via OOB heap read in "attribute uniqueness" plugin

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-2591
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-2591

Regards,
Salvatore

Processed: forcibly merging 648208 794849

[Debian Bug Tracking System]

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

> forcemerge 648208 794849
Bug #648208 [os-prober] os-prober: blockdev --setro affects running kvm 
instances
Bug #788062 [os-prober] os-prober corrupts LVs/partitions while being mounted 
inside a VM
Bug #806273 [os-prober] os-prober: remove or disable-per default the non 
grub-mount based probing
Bug #810121 [os-prober] linux: KVM guests randomly get I/O errors on VirtIO 
based devices
Bug #794849 [os-prober] linux: custom linux-image packages fail to install
Severity set to 'critical' from 'serious'
Marked as found in versions os-prober/1.65 and os-prober/1.42.
Added tag(s) patch.
Bug #788062 [os-prober] os-prober corrupts LVs/partitions while being mounted 
inside a VM
Bug #806273 [os-prober] os-prober: remove or disable-per default the non 
grub-mount based probing
Bug #810121 [os-prober] linux: KVM guests randomly get I/O errors on VirtIO 
based devices
Merged 648208 788062 794849 806273 810121
> thanks
Stopping processing here.

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

Bug#851770: php-gettext: CVE-2015-8980

[Salvatore Bonaccorso]

Source: php-gettext
Version: 1.0.11-1
Severity: grave
Tags: security upstream

Hi,

the following vulnerability was published for php-gettext.

CVE-2015-8980[0]:
|Arbitrary code execution in select_string, ngettext and npgettext
|count parameter

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2015-8980
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-8980
[1] http://seclists.org/fulldisclosure/2016/Aug/76

Regards,
Salvatore

Bug#851771: php-gettext: CVE-2016-6175

[Salvatore Bonaccorso]

Source: php-gettext
Version: 1.0.11-1
Severity: grave
Tags: security upstream
Forwarded: https://bugs.launchpad.net/php-gettext/+bug/1606184

Hi,

the following vulnerability was published for php-gettext.

CVE-2016-6175[0]:
Use of eval too unrestrictive 

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-6175
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6175
[1] https://bugs.launchpad.net/php-gettext/+bug/1606184

Regards,
Salvatore

Bug#848236: Remaining issue with gbrowse - any help (Was: Urgent call to BioPerl users (Was: Bug#848236: src:gbrowse: ...)

[Andreas Tille]

[droping debian-perl list from CC]

On Wed, Jan 18, 2017 at 02:30:32PM +0100, Andreas Tille wrote:
> Hi Lincoln,
> 
> On Wed, Jan 18, 2017 at 07:07:55AM -0500, Lincoln Stein wrote:
> > 
> > There appears to be a new dependency on libbio-coordinate. Probably best to
> > add a "use Bio::Coordinate" and the dependency to Bio::Graphics. Then the
> > problem will disappear.
> 
> Cool.  In Debian terminology this means a new "Build-Depends" and after adding
> libbio-coordinate-perl package to this the tests succeeded.  Thanks a lot for
> your help and patience!
> 
> I now need to sort out some other issues with packaging and think I'll upload
> soon.

This is done now.

I'd recommend you have a look at several patches for the Debian package which
are available here:

   https://anonscm.debian.org/cgit/debian-med/gbrowse.git/tree/debian/patches

They apply in the sequence of the series file and I guess several of them are
useful also for your upstream code.

Thanks a lot for your help

  Andreas.

-- 
http://fam-tille.de

Bug#848236: marked as done (src:gbrowse: Fails to build from source since bioperl upgrade has broken libbio-graphics-perl)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 16:34:04 +
with message-id 
and subject line Bug#848236: fixed in gbrowse 2.56+dfsg-1
has caused the Debian Bug report #848236,
regarding src:gbrowse: Fails to build from source since bioperl upgrade has 
broken libbio-graphics-perl
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.)


-- 
848236: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848236
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gbrowse
Severity: serious
Justification: FTBFS

Hi,

when trying to build gbrowse it fails to build from source:

...
CGI::param called in list context from 
/build/gbrowse-2.54+dfsg/t/../lib/Bio/Graphics/Browser2/Render.pm line 2348, 
this can lead to vulnerabilities. See the warning in "Fetching the value or 
values of a single named parameter" at /usr/share/perl5/CGI.pm line 412.
CGI::param called in list context from 
/build/gbrowse-2.54+dfsg/t/../lib/Bio/Graphics/Browser2/Render/Slave.pm line 
271, this can lead to vulnerabilities. See the warning in "Fetching the value 
or values of a single named parameter" at /usr/share/perl5/CGI.pm line 412, 
 line 1.
CGI::param called in list context from 
/build/gbrowse-2.54+dfsg/t/../lib/Bio/Graphics/Browser2/Render/Slave.pm line 
271, this can lead to vulnerabilities. See the warning in "Fetching the value 
or values of a single named parameter" at /usr/share/perl5/CGI.pm line 412, 
 line 1.
RenderPanels error: 
- EXCEPTION -
MSG: The requested glyph class, ``span'' is not available: Attempt to reload 
Bio/Graphics/Glyph/span.pm aborted.
Compilation failed in require at (eval 180) line 2, <> line 45.

STACK Bio::Graphics::Glyph::Factory::make_glyph 
/usr/share/perl5/Bio/Graphics/Glyph/Factory.pm:342
STACK Bio::Graphics::Glyph::add_feature 
/usr/share/perl5/Bio/Graphics/Glyph.pm:424
STACK Bio::Graphics::Browser2::RenderPanels::add_features_to_track 
/build/gbrowse-2.54+dfsg/t/../lib/Bio/Graphics/Browser2/RenderPanels.pm:1842
STACK (eval) 
/build/gbrowse-2.54+dfsg/t/../lib/Bio/Graphics/Browser2/RenderPanels.pm:1570
STACK Bio::Graphics::Browser2::RenderPanels::run_local_requests 
/build/gbrowse-2.54+dfsg/t/../lib/Bio/Graphics/Browser2/RenderPanels.pm:1524
STACK Bio::Graphics::Browser2::RenderPanels::request_panels 
/build/gbrowse-2.54+dfsg/t/../lib/Bio/Graphics/Browser2/RenderPanels.pm:195
STACK Bio::Graphics::Browser2::Render::render_deferred 
/build/gbrowse-2.54+dfsg/t/../lib/Bio/Graphics/Browser2/Render.pm:3589
STACK toplevel t/05.deferredrendering.t:102
-
...


The cause is most probably that libbio-graphics-perl does not work
together with bioperl 1.7.1 (see also #848105).  I'm now becoming aware
that with the naive upgrade to bioperl 1.7.1 we have triggered problems
that should have solved inside a transition via experimental.  My
proposed course of action is as follows:

  1. Revert the version bump of bioperl and upload the old version
 with an epoch (1:1.6.924-6).
  2. Upload 1.7.1-2 to experimental
  3. Solve all issues with BioPerl 1.7.x after Stretch release.

Does anybody have a better plan?

Kind regards

Andreas.


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

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: gbrowse
Source-Version: 2.56+dfsg-1

We believe that the bug you reported is fixed in the latest version of
gbrowse, 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 848...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated gbrowse package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 18 Jan 2017 17:16:19 +0100
Source: gbrowse
Binary: gbrowse gbrowse-data gbrowse-calign
Architecture: source amd64 all
Version: 2.56+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

C

Bug#848236: Remaining issue with gbrowse - any help (Was: Urgent call to BioPerl users (Was: Bug#848236: src:gbrowse: ...)

[gregor herrmann]

On Wed, 18 Jan 2017 17:27:21 +0100, Andreas Tille wrote:

> > Cool.  In Debian terminology this means a new "Build-Depends" and after 
> > adding
> > libbio-coordinate-perl package to this the tests succeeded.  Thanks a lot 
> > for
> > your help and patience!
> > 
> > I now need to sort out some other issues with packaging and think I'll 
> > upload
> > soon.
> 
> This is done now.
> 
> I'd recommend you have a look at several patches for the Debian package which
> are available here:
> 
>https://anonscm.debian.org/cgit/debian-med/gbrowse.git/tree/debian/patches

Oh, cool, adding the (build)-dep is really enough, no patching
required. Nice.
 
For stretch, I think there's still one thing to do:
autopkgtest still fails with

pmerror:/tmp/apt-dpkg-install-qeDTFa/103-gbrowse.deb:42.2343:trying to 
overwrite '/usr/share/man/man3/Bio::DB::SeqFeature::Store::LoadHelper.3pm.gz', 
which is also in package libbio-perl-perl 1.7.1-2

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Schmetterlinge: Kommt ihr tausend Haufen


signature.asc
Description: Digital Signature

Bug#847577: marked as done (Embeds dietlibc (GPL) but does not have a Built-Using field)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 16:48:31 +
with message-id 
and subject line Bug#847577: fixed in integrit 4.1-1.1
has caused the Debian Bug report #847577,
regarding Embeds dietlibc (GPL) but does not have a Built-Using field
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.)


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

integrit is statically linked to dietlibc which is licensed under
GNU GPL.  integrit must have a Built-Using field to record which
version was used and ensure that the corresponding source package is
kept in the archive.

Ben.

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

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 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)
--- End Message ---
--- Begin Message ---
Source: integrit
Source-Version: 4.1-1.1

We believe that the bug you reported is fixed in the latest version of
integrit, 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 847...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated integrit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 18 Jan 2017 16:50:19 +0200
Source: integrit
Binary: integrit
Architecture: source
Version: 4.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Gerrit Pape 
Changed-By: Adrian Bunk 
Description:
 integrit   - A file integrity verification program
Closes: 776973 846891 847577
Changes:
 integrit (4.1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Apply change from Andreas Henriksson to add a Built-Using field.
 (Closes: #847577)
   * Apply changes from Chris Lamb and Valerie R Young to make the
 build reproducible. (Closes: #776973, #846891)
Checksums-Sha1:
 e938a2c7b915c5aa81e6e2dcb4057449776bcb61 1704 integrit_4.1-1.1.dsc
 0e1c559e5447b26e3f33697794480007dd1095ee 9875 integrit_4.1-1.1.diff.gz
Checksums-Sha256:
 e19dae338df5f9185e9e0d922a5ca2669f9e6fc44dfa213a12fd24400f7ee41d 1704 
integrit_4.1-1.1.dsc
 84751076a8c967367cc69212f458f867c4f84d6550356ea146334a6e5e2c54de 9875 
integrit_4.1-1.1.diff.gz
Files:
 e26441418b3bd66cec0acaf0bb78d209 1704 admin optional integrit_4.1-1.1.dsc
 8e156807b45ba4feb15f877744566cb4 9875 admin optional integrit_4.1-1.1.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlh/mXsACgkQiNJCh6LY
mLHOJxAAoe7zFNuk9Qn4HzPTJm+yTN5bYVEntK0AJmR+iUw7NaVwT/6wFZOCdloy
AJw82oy4TvhAczrAS9maZwQX97vrJGt5aV0JzL3ICbIsx6wkxjh3VBMOHB75TTnZ
Iby9GJ6IUIdHYFo7sgCsA6118dLzgapHo1/KK7XiMW1eEExTWXgDp/TGkZFzjiPV
PFoabPnxYh7jgQ0ikWOCpFaQnedcwYYcTxYaL6P9RgtEfDHrX80OyEQL4eEuF1eQ
jaWLcQS1sSQalaIf/KlBik5H2LHu20wtar5H1rT/v4L9js+g0EUrJrjlGFQCh+UI
yCQr3zEbJqmPFEOlP2bpoNIdyeZck9SWZfeKZ3kdYvtvP9c5dxbRjSvYk0CrW5k2
D7b+qveLfO5gmD9lujKvbma8FbcyLdGrbOd6BrGgSuAcoUmfF2Vuq8K/xXf2JEfa
+1Gg4GF7CPf3e3kHBO2PY2NjR5gNvA/JdTKDOfKPltQNAyFE3Ne5jJmn7IGWBosU
iEgT4lXbLT7WqMf/eUfZwj6Oqc49em0irE+PUpP83FWGKvuoVHaodPF1z+I6JkRT
iAA0ERdyIEECJPv9N+QDi9aZHrkziTt3lBKEwmlyBg6ZmhabwyGUiIqXng5WfQmp
+dcE1se8XUJGc1wN6HUwW0ckpB4QL0O7TfVO5E49IYkW7DZ8SgU=
=JOaE
-END PGP SIGNATURE End Message ---

Bug#851775: libgcj-bc shlibs creates dependency that cannot be fulfilled in unstable

[Adrian Bunk]

Package: libgcj-bc
Version: 6.2.1-1
Severity: grave
Control: affects -1 libecj-java-gcj ecj1 ecj-gcj ant-gcj ant-optional-gcj

$ cat /var/lib/dpkg/info/libgcj-bc\:amd64.shlibs 
libgcj_bc 1 libgcj-bc (>= 6.2.1-3~)
$ 


That seems to be the reason why several packages can currently
not be installed in unstable:

  libecj-java-gcj,libgcj-bc 6.2.1-3~
  ecj1,libgcj-bc 6.2.1-3~
  ecj-gcj,libgcj-bc 6.2.1-3~
  ant-gcj,libgcj-bc 6.2.1-3~
  ant-optional-gcj,libgcj-bc 6.2.1-3~

Processed: libgcj-bc shlibs creates dependency that cannot be fulfilled in unstable

[Debian Bug Tracking System]

Processing control commands:

> affects -1 libecj-java-gcj ecj1 ecj-gcj ant-gcj ant-optional-gcj
Bug #851775 [libgcj-bc] libgcj-bc shlibs creates dependency that cannot be 
fulfilled in unstable
Added indication that 851775 affects libecj-java-gcj, ecj1, ecj-gcj, ant-gcj, 
and ant-optional-gcj

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

Bug#848236: Remaining issue with gbrowse - any help (Was: Urgent call to BioPerl users (Was: Bug#848236: src:gbrowse: ...)

[Andreas Tille]

On Wed, Jan 18, 2017 at 05:39:05PM +0100, gregor herrmann wrote:
> > 
> >
> > https://anonscm.debian.org/cgit/debian-med/gbrowse.git/tree/debian/patches
> 
> Oh, cool, adding the (build)-dep is really enough, no patching
> required. Nice.

Yes, we needed this for another package ...
  
> For stretch, I think there's still one thing to do:
> autopkgtest still fails with
> 
> pmerror:/tmp/apt-dpkg-install-qeDTFa/103-gbrowse.deb:42.2343:trying to 
> overwrite 
> '/usr/share/man/man3/Bio::DB::SeqFeature::Store::LoadHelper.3pm.gz', which is 
> also in package libbio-perl-perl 1.7.1-2

Urgs - Lincoln, I guess it makes sense to remove this copy of bioperl
even in your distribution.  What do you think?

Kind regards

   Andreas.


-- 
http://fam-tille.de

Bug#851741: python-jinja2: New major version breaks ansible templates

[Jeremy Bicha]

On 18 January 2017 at 06:29, Piotr Ożarowski  wrote:
> could you check if this commit fixes it for you?
> https://github.com/pallets/jinja/commit/c6ddeb7d5f64789ed0bbc1ffef8596a79bc06fd9

Thanks for the quick response.

I'm still getting the KeyError: undefined variable after I built
jinja2 with that patch and installed it. :(

Thanks,
Jeremy Bicha

Bug#223915: marked as done (tk-brief: Please don't package it as a native package)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 17:20:28 +
with message-id 
and subject line Bug#223915: fixed in tk-brief 5.10-0.1
has caused the Debian Bug report #223915,
regarding tk-brief: Please don't package it as a native package
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.)


-- 
223915: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=223915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tk-brief
Version: 5.9-1
Severity: normal


seesat5 is not a native Debian package. Please change the packaging to
a non-native packaging (.orig.tar.gz + .diff.gz + .dsc).

TIA
Adrian




--- End Message ---
--- Begin Message ---
Source: tk-brief
Source-Version: 5.10-0.1

We believe that the bug you reported is fixed in the latest version of
tk-brief, 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 223...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christoph Biedl  (supplier of updated tk-brief 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 18 Jan 2017 07:31:01 +0100
Source: tk-brief
Binary: tk-brief
Architecture: source all
Version: 5.10-0.1
Distribution: unstable
Urgency: medium
Maintainer: Yven Johannes Leist 
Changed-By: Christoph Biedl 
Description:
 tk-brief   - GUI for easily writing letters with LaTeX
Closes: 223915 249196
Changes:
 tk-brief (5.10-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream version. Closes: #249196
   * Build as a package with orig tarball. Closes: #223915
Checksums-Sha1:
 21a949f5624c5923ab8cac92e99d949750543b24 1651 tk-brief_5.10-0.1.dsc
 0742bda99d99df2185262abda103ff7f94cc72a9 99516 tk-brief_5.10.orig.tar.gz
 67f53dbb5001d84d89d06b9a7b4a188274e3fc67 2708 tk-brief_5.10-0.1.debian.tar.xz
 030a951b05a487daa196f6580d440ea4e4dabf92 90440 tk-brief_5.10-0.1_all.deb
 ef1b130c4fe1031c6feef0e95112ba210b25d956 4219 
tk-brief_5.10-0.1_powerpc.buildinfo
Checksums-Sha256:
 4f8dc032c89a174fc8ce6dcef13682dced5879c49f967873e58f492225064ad8 1651 
tk-brief_5.10-0.1.dsc
 6b93d6fa31ac98c44086ca19be1eb4d9cbea51728d1d02b090fd1f5a757d0379 99516 
tk-brief_5.10.orig.tar.gz
 4ccbd69cd3f2b06141323e7f656f8f40c1c14d32035b4b89b19f4f15dabd367e 2708 
tk-brief_5.10-0.1.debian.tar.xz
 6d272742d62c0762979f765fbbb4133901a8f046e0cc2901ec282eaaf479676b 90440 
tk-brief_5.10-0.1_all.deb
 1767861f48d0b5c8e4b9378fd3b91344a0d96ca3bd19e548c5936b09f8aa2ab8 4219 
tk-brief_5.10-0.1_powerpc.buildinfo
Files:
 37268b01522a815364627ac2dadb8aa0 1651 tex optional tk-brief_5.10-0.1.dsc
 452db4d7b4bdaffd13d0af634e835509 99516 tex optional tk-brief_5.10.orig.tar.gz
 f68f3d1c77f6c69fa45fbdd1da1f70c3 2708 tex optional 
tk-brief_5.10-0.1.debian.tar.xz
 86f0e003e202646a50b96e982cb3b6b3 90440 tex optional tk-brief_5.10-0.1_all.deb
 d80567b3d0f14abeb2ff7d149bf7e3ff 4219 tex optional 
tk-brief_5.10-0.1_powerpc.buildinfo

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJYfxh7AAoJEMQsWOtZFJL9b1EP/3gTw5Q8Q/1HrllC1DO93wH3
UVKg3TRo8JzvOCTNmDDZgzZRxZIPSPrH4TQr4+MPAD9dAclv7Tdb41ro7vbQhnMn
fuL/UettDM4h7sRQAgLguydgwiNoLt56ITiVOyzcKYlPP7YwHRsiCxbST8/mJA8E
5IogLDx0UlFMvuLiikOX7Dp/4jN9pP/ZtDMQzgWK/MLkdapOZTk8pJHzA5c5n2X+
iETfGWhCTH6CxME76q6xTJSGsP+JzPPqCRcpcDhaE1iUAFvqu77VdXc17ETfFF6r
Tc436IvH9YXxaCN6xVQH9WhXE4wsT01GNfMaA8JIgx/z6TLE8+3/bXMkkHbA4hTP
CM7+Y804DJN3Y60E9TriYjPxy6dNMcMtjzeK6VZWv2XXg3zlvUWA7M0f09col36X
Wd2v2ICq54L8YWi+e28b5tbnbexHlfOL/SSVflaTdE+UZs1rfTOewNll0u3coU/+
cmwXppA4n2LTiKpycGGarklp3mL9BzXxdZ+FlWEjrIPLZtyi9lQmFOHTuTrtoH6V
BeP15nF3jKyQ6HMmNCqRK30/lkApI6OmIlIV6dOa3HTjZpMtg5HA7BJXXlupYPiq
UUm+ngDhiXcaOD73RT1aBZpMzaKU6qi6EWDROf1Tgn72RLeHxvAE03NmW+4/A8Mz
huz8rr+/6UJtcR/ay2ZK
=oKBV
-END PGP SIGNATURE End Message ---

Bug#851779: chromium: crashes at startup

[Guy Durrieu]

Package: chromium
Version: 55.0.2883.75-4
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Since last recent release, chromium does not start anymore.

Wen typing the command in a shell, I get the following message:

---

chromium
/usr/bin/chromium: 122: /usr/bin/chromium: Syntax error: "fi" unexpected 
(expecting "}")---


--

but when having a look to the script, I do not understand why this 
syntax error appears.


Thanks in advance for your help !

Regards.

-- GD.


System Information:
Debian Release: 9.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 
'testing'), (500, 'stable')

Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages chromium depends on:
ii  libasound2   1.1.2-1
ii  libatk1.0-0  2.22.0-1
ii  libavcodec57 10:3.2.2-dmo3
ii  libavformat5710:3.2.2-dmo3
ii  libavutil55  10:3.2.2-dmo3
ii  libc62.24-9
ii  libcairo21.14.8-1
ii  libcups2 2.2.1-5
ii  libdbus-1-3  1.10.14-1
ii  libevent-2.0-5   2.0.21-stable-2.1
ii  libexpat12.2.0-2
ii  libflac8 1.3.2-1
ii  libfontconfig1   2.11.0-6.7
ii  libfreetype6 2.6.3-3+b1
ii  libgcc1  1:6.3.0-2
ii  libgdk-pixbuf2.0-0   2.36.4-1
ii  libglib2.0-0 2.50.2-2
ii  libgtk2.0-0  2.24.31-1
ii  libharfbuzz0b1.2.7-1+b1
ii  libicu57 57.1-5
ii  libjpeg62-turbo  1:1.5.1-2
ii  libminizip1  1.1-8
ii  libnspr4 2:4.12-6
ii  libnss3  2:3.26.2-1
ii  libpango-1.0-0   1.40.3-3
ii  libpangocairo-1.0-0  1.40.3-3
ii  libpng16-16  1.6.28-1
ii  libpulse09.0-5
ii  libre2-3 20170101+dfsg-1
ii  libsnappy1v5 1.1.3-3
ii  libstdc++6   6.3.0-2
ii  libvpx4  1.6.1-2
ii  libwebp6 0.5.2-1
ii  libwebpdemux20.5.2-1
ii  libx11-6 2:1.6.4-2
ii  libx11-xcb1  2:1.6.4-2
ii  libxcb1  1.12-1
ii  libxcomposite1   1:0.4.4-1
ii  libxcursor1  1:1.1.14-1+b1
ii  libxdamage1  1:1.1.4-2+b1
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.3-1
ii  libxi6   2:1.7.8-2
ii  libxml2  2.9.4+dfsg1-2.1
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxslt1.1   1.1.29-2
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.3-1
ii  x11-utils7.7+3
ii  xdg-utils1.1.1-1
ii  zlib1g   1:1.2.8.dfsg-4

Versions of packages chromium recommends:
ii  fonts-liberation  1:1.07.4-2

Versions of packages chromium suggests:
pn  chromium-driver
ii  chromium-l10n  55.0.2883.75-4
pn  chromium-shell 
pn  chromium-widevine  

-- no debconf information

Bug#733433: marked as done (tk-brief: FTBFS: dpkg-source: error: can't build with source format '3.0 (native)': native package version may not have a revision)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 17:20:28 +
with message-id 
and subject line Bug#223915: fixed in tk-brief 5.10-0.1
has caused the Debian Bug report #223915,
regarding tk-brief: FTBFS: dpkg-source: error: can't build with source format 
'3.0 (native)': native package version may not have a revision
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.)


-- 
223915: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=223915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tk-brief
Version: 5.9-1.1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20131226 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh_testdir
> dh_testroot
> rm -f build-stamp configure-stamp
> # Add here commands to clean up after the build process.
> dh_clean
>  dpkg-source -b tk-brief-5.9
> dpkg-source: error: can't build with source format '3.0 (native)': native 
> package version may not have a revision
> dpkg-buildpackage: error: dpkg-source -b tk-brief-5.9 gave error exit status 
> 255
> 
> Build finished at 20131227-0323

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/12/26/tk-brief_5.9-1.1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: tk-brief
Source-Version: 5.10-0.1

We believe that the bug you reported is fixed in the latest version of
tk-brief, 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 223...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christoph Biedl  (supplier of updated tk-brief 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 18 Jan 2017 07:31:01 +0100
Source: tk-brief
Binary: tk-brief
Architecture: source all
Version: 5.10-0.1
Distribution: unstable
Urgency: medium
Maintainer: Yven Johannes Leist 
Changed-By: Christoph Biedl 
Description:
 tk-brief   - GUI for easily writing letters with LaTeX
Closes: 223915 249196
Changes:
 tk-brief (5.10-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream version. Closes: #249196
   * Build as a package with orig tarball. Closes: #223915
Checksums-Sha1:
 21a949f5624c5923ab8cac92e99d949750543b24 1651 tk-brief_5.10-0.1.dsc
 0742bda99d99df2185262abda103ff7f94cc72a9 99516 tk-brief_5.10.orig.tar.gz
 67f53dbb5001d84d89d06b9a7b4a188274e3fc67 2708 tk-brief_5.10-0.1.debian.tar.xz
 030a951b05a487daa196f6580d440ea4e4dabf92 90440 tk-brief_5.10-0.1_all.deb
 ef1b130c4fe1031c6feef0e95112ba210b25d956 4219 
tk-brief_5.10-0.1_powerpc.buildinfo
Checksums-Sha256:
 4f8dc032c89a174fc8ce6dcef13682dced5879c49f967873e58f492225064ad8 1651 
tk-brief_5.10-0.1.dsc
 6b93d6fa31ac98c44086ca19be1eb4d9cbea51728d1d02b090fd1f5a757d0379 99516 
tk-brief_5.10.orig.tar.gz
 4ccbd69cd3f2b06141323e7f656f8f40c1c14d32035b4b89b19f4f15dabd367e 2708 
tk-brief_5.10-0.1.debian.tar.xz
 6d272742d62c0762979f765fbbb4133901a8f046e0cc2901ec282eaaf479676b 90440 
tk-brief_5.10-0.1_all.deb
 1767861f48d0b5c8e4b9378fd3b91344a0d96ca3bd19e548c5936b09f8aa2ab8 4219 
tk-brief_5.10-0.1_powerpc.buildinfo
Files:
 37268b01522a815364627ac2dadb8aa0 1651 tex optional tk-brief_5.10-0.1.dsc
 452db4d7b4bdaffd13d0af634e835509 99516 tex optional tk-brief_5.10.orig.tar.gz
 f68f3d1c77f6c69fa45fbdd1da1f70c3 2708 tex optional 
tk-brief_5.10-0.1.debian.tar.xz
 86f0e003e202646a50b96e982cb3b6b3 90440 tex optional tk-brief_5.10-0.1_all.deb
 d80567b3d0f14abeb2ff7d149bf7e3ff 4219 tex optional 
tk-brief_5.10-0.1_powerpc.buildinfo

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJYfxh7AAoJEMQsWOtZFJL9b1EP/3gTw5Q8Q/1HrllC1DO93wH3
UVKg3TRo8JzvOCTNmDDZg

Bug#805988: aboot : include the binaries in source to build on amd64

[jhcha54008]

Hi,

I wonder if the following solution would be accepted (see the two patches 
attached) : let the source package ship the two binaries (bootlx and 
net_aboot.nh). One can build aboot-base on amd64 then.
The two binaries are generated from source if the source package is
built on alpha.
(The inspiration came from Helge Deller's palo package on hppa)

I tested so far that dpkg-buildpackage -B builds aboot (on alpha)
and aboot-cross (on amd64),
and that dpkg-builpackage -A builds aboot-base (on both).

A bootable CD including a just compiled bootlx indeed booted an XP1000 
alpha workstation.

I hope it will help !

Regards,
JH Chatenet
Description: Build-depends on opensp instead of sp (deprecated, removed)
 This is the concatenation of two patches from the thread of bug
 #832491 (see the discussion therein). Should close #832491
Forwarded: no
Origin: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832491#5
Origin: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832491#23
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832491
Author: Neil Roeth 
Author: jhcha54008 

diff -Naur aboot-1.0~pre20040408/debian/control aboot-1.0~pre20040408/debian/control
--- aboot-1.0~pre20040408/debian/control	
+++ aboot-1.0~pre20040408/debian/control	
@@ -1,5 +1,5 @@
 Source: aboot
-Build-Depends: debhelper (>= 9), sp, sgmlspl, docbook-utils
+Build-Depends: debhelper (>= 9), opensp, sgmlspl, docbook-utils
 Build-Depends-Indep: sgmltools-lite
 Section: admin
 Priority: standard
diff -Naur aboot-1.0~pre20040408/doc/man/Makefile aboot-1.0~pre20040408/doc/man/Makefile
--- aboot-1.0~pre20040408/doc/man/Makefile	
+++ aboot-1.0~pre20040408/doc/man/Makefile	
@@ -32,20 +32,20 @@
 	rm -f aboot.8 aboot.conf.5 abootconf.8 isomarkboot.1 sdisklabel.8 netabootwrap.1 manpage.log manpage.links manpage.refs
 
 aboot.8: aboot.sgml
-	nsgmls aboot.sgml | sgmlspl sgmlspl-specs/docbook2man-spec.pl
+	onsgmls aboot.sgml | sgmlspl sgmlspl-specs/docbook2man-spec.pl
 
 aboot.conf.5: aboot.conf.sgml
-	nsgmls aboot.conf.sgml | sgmlspl sgmlspl-specs/docbook2man-spec.pl
+	onsgmls aboot.conf.sgml | sgmlspl sgmlspl-specs/docbook2man-spec.pl
 
 abootconf.8: abootconf.sgml
-	nsgmls abootconf.sgml | sgmlspl sgmlspl-specs/docbook2man-spec.pl
+	onsgmls abootconf.sgml | sgmlspl sgmlspl-specs/docbook2man-spec.pl
 
 isomarkboot.1: isomarkboot.sgml
-	nsgmls isomarkboot.sgml | sgmlspl sgmlspl-specs/docbook2man-spec.pl
+	onsgmls isomarkboot.sgml | sgmlspl sgmlspl-specs/docbook2man-spec.pl
 
 netabootwrap.1: netabootwrap.sgml
-	nsgmls netabootwrap.sgml | sgmlspl sgmlspl-specs/docbook2man-spec.pl
+	onsgmls netabootwrap.sgml | sgmlspl sgmlspl-specs/docbook2man-spec.pl
 
 sdisklabel.8: sdisklabel.sgml
-	nsgmls sdisklabel.sgml | sgmlspl sgmlspl-specs/docbook2man-spec.pl
+	onsgmls sdisklabel.sgml | sgmlspl sgmlspl-specs/docbook2man-spec.pl
 
diff -Naur aboot-1.0~pre20040408/doc/man/README aboot-1.0~pre20040408/doc/man/README
--- aboot-1.0~pre20040408/doc/man/README	2003-05-30 16:57:34.0 +
+++ aboot-1.0~pre20040408/doc/man/README	
@@ -26,7 +26,7 @@
 please contact me.
 
 Technical note:
-To create the nroff version from the SGML sources, nsgml was used like
-nsgmls abootconf.sgml | sgmlspl sgmlspl-specs/docbook2man-spec.pl
+To create the nroff version from the SGML sources, onsgmls was used like
+onsgmls abootconf.sgml | sgmlspl sgmlspl-specs/docbook2man-spec.pl
 
 Hannover, Germany, January 17th 2003
diff -Naur aboot-1.0~pre20040408/doc/man/de/Makefile aboot-1.0~pre20040408/doc/man/de/Makefile
--- aboot-1.0~pre20040408/doc/man/de/Makefile	
+++ aboot-1.0~pre20040408/doc/man/de/Makefile	
@@ -1,35 +1,35 @@
 all:  srmbootraw.de.8 aboot.de.8 aboot.conf.de.5 abootconf.de.8 isomarkboot.de.1 sdisklabel.de.8 srmbootfat.de.1 e2writeboot.de.8 swriteboot.de.8 netabootwrap.de.1
 
 aboot.de.8: aboot.sgml
-	nsgmls aboot.sgml | sgmlspl docbook2man-de-spec.pl
+	onsgmls aboot.sgml | sgmlspl docbook2man-de-spec.pl
 	mv aboot.8 aboot.de.8
 
 aboot.conf.de.5: aboot.conf.sgml
-	nsgmls aboot.conf.sgml | sgmlspl docbook2man-de-spec.pl
+	onsgmls aboot.conf.sgml | sgmlspl docbook2man-de-spec.pl
 	mv aboot.conf.5 aboot.conf.de.5
 
 abootconf.de.8: abootconf.sgml
-	nsgmls abootconf.sgml | sgmlspl docbook2man-de-spec.pl
+	onsgmls abootconf.sgml | sgmlspl docbook2man-de-spec.pl
 	mv abootconf.8 abootconf.de.8
 
 netabootwrap.de.1: netabootwrap.sgml
-	nsgmls netabootwrap.sgml | sgmlspl docbook2man-de-spec.pl
+	onsgmls netabootwrap.sgml | sgmlspl docbook2man-de-spec.pl
 	mv netabootwrap.1 netabootwrap.de.1
 
 isomarkboot.de.1: isomarkboot.sgml
-	nsgmls isomarkboot.sgml | sgmlspl docbook2man-de-spec.pl
+	onsgmls isomarkboot.sgml | sgmlspl docbook2man-de-spec.pl
 	mv isomarkboot.1 isomarkboot.de.1
 
 sdisklabel.de.8: sdisklabel.sgml
-	nsgmls sdisklabel.sgml | sgmlspl docbook2man-de-spec.pl
+	onsgmls sdisklabel.sgml | sgmlspl docbook2man-de-spec.pl
 	mv sdisklabel.8 sdisklabel.de.8
 
 srmbootfat.de.1: srmbootfat.sgml
-	nsgmls srmbootfat.sgml | sgmlspl docbook2man-de

Bug#832656: marked as done (runit: breaks users of runit: ln: failed to create symbolic link '/etc/service/bcron-sched': No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 17:33:27 +
with message-id 
and subject line Bug#832656: fixed in bcron 0.10-4
has caused the Debian Bug report #832656,
regarding runit: breaks users of runit: ln: failed to create symbolic link 
'/etc/service/bcron-sched': No such file or directory
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.)


-- 
832656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: runit
Version: 2.1.2-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Selecting previously unselected package bcron-run.
  (Reading database ... 
(Reading database ... 6995 files and directories currently installed.)
  Preparing to unpack .../bcron-run_0.10-3_all.deb ...
  Unpacking bcron-run (0.10-3) ...
  Setting up bcron-run (0.10-3) ...
  Installing new version of config file /etc/crontab ...
  Adding system user `cron' (UID 151) ...
  Adding new group `cron' (GID 152) ...
  Adding new user `cron' (UID 151) with group `cron' ...
  Not creating home directory `/var/spool/cron'.
  Warning: The home dir /nonexistent you specified can't be accessed: No such 
file or directory
  Adding system user `cronlog' (UID 152) ...
  Adding new user `cronlog' (UID 152) with group `nogroup' ...
  Not creating home directory `/nonexistent'.
  ln: failed to create symbolic link '/etc/service/bcron-sched': No such file 
or directory
  dpkg: error processing package bcron-run (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   bcron-run

Similar problems were seen in different *-run packages.


cheers,

Andreas


bcron-run_0.10-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: bcron
Source-Version: 0.10-4

We believe that the bug you reported is fixed in the latest version of
bcron, 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 832...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dmitry Bogatov  (supplier of updated bcron 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: Tue, 23 Aug 2016 15:42:04 +0300
Source: bcron
Binary: bcron bcron-run
Architecture: source amd64 all
Version: 0.10-4
Distribution: unstable
Urgency: medium
Maintainer: Gerrit Pape 
Changed-By: Dmitry Bogatov 
Description:
 bcron  - ${S:Short-Desc} (programs)
 bcron-run  - ${S:Short-Desc} (integration with runit)
Closes: 832656
Changes:
 bcron (0.10-4) unstable; urgency=medium
 .
   * Write debian/watch
   * Change source package format to quilt, remove manual patches
 application
   * Convert package to use debhelper
   * Use `dh-runit' to install runit scripts and generate log scripts
 (Closes: #832656)
   * Use `dh-buildinfo' to simplify tracking bugs, related to build-tools
   * Avoid need of hand-written maintainer scripts by
 use of `dh-runit' and `dh-sysuser'
   * Drop dietlibc-dev from Build-Depends for now. (Libraries
 depended upon are not compiled for dietlibc anymore.)
   * Remove no longer needed README files
   * Move 'debian/crontab' into 'debian/contrib' for more clean package layout
   * Enable hardening
   * Fix @dircategory in texinfo manual
   * Install `doc-base' document
   * Add Homepage field
   * Bump standards version to 3.9.8 (no changes needed)
   * Remove Section field from `bcron-run' field, since it duplicated one
 defined in first paragraph.
   * Update Vcs-Git and Vcs-Browser fields
   * Convert `debian/copyrigh' to dep5 format
   * Use S:fieldname substitution to avoid duplication in `debian/control'.
 + Add versioned dependency on (dpkg-dev >= 1.18.11)
   * Disable unreliable tests (see: #835274)
Checksums-Sha1:
 51d01b1be3ab30affd67f954e68e4a6de5febc67 2029 bcron_0.10-4.dsc
 e012001ea4a903b6fd47396025a76054ad22a7a5 68314 bcron_0.10.orig.tar.gz
 fe24a

Bug#789407: unable to send openpgp messages

[Christoph Biedl]

Control: tags 789407 unreproducible
Control: severity 789407 normal

Lowering severity as this problem was not reproducible, and the original
submitter did not provide additional information upon request.

Christoph


signature.asc
Description: Digital signature

Processed: Re: Bug#789407: unable to send openpgp messages

[Debian Bug Tracking System]

Processing control commands:

> tags 789407 unreproducible
Bug #789407 [pidgin-openpgp] unable to send openpgp messages
Added tag(s) unreproducible.
> severity 789407 normal
Bug #789407 [pidgin-openpgp] unable to send openpgp messages
Severity set to 'normal' from 'grave'

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

Bug#805988: aboot : include the binaries in source to build on amd64

[Santiago Vila]

On Wed, Jan 18, 2017 at 06:38:44PM +0100, jhcha54008 wrote:

> I wonder if the following solution would be accepted (see the two patches 
> attached) : let the source package ship the two binaries (bootlx and 
> net_aboot.nh). [...]

Hmm, but this is like removing a hack and creating another one in another place.

The previous package was a "fake" Arch:all package, so to speak, and now
we would have a "fake" source package, as it would include binaries.

We don't want binaries inside source packages (and I think ftpmasters
would surely agree on this).

If alpha is not a release architecture, would it really be a problem
to remove this from testing before the release of stretch while we keep it in
unstable?

We could meet the release goal of all packages being buildable
in our Arch:all autobuilder that way without causing a major headache
to users of alpha.

Alternatively, there is also the possibility of asking the Release
Managers for permission to use stretch-ignore here.

Thanks.

Bug#749661: marked as done (ifuse: Segfault)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 19:57:32 +0200
with message-id <20170118175732.nwmnfecckaxvyibo@localhost>
and subject line Re: Bug#749661: ifuse: Segfault
has caused the Debian Bug report #749661,
regarding ifuse: Segfault
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.)


-- 
749661: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749661
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ifuse
Version: 1.1.2-0.1+b2
Severity: grave

Hello,

I get a segfault when trying to mount my phone. I think this is the
backtrace:

Program terminated with signal 11, Segmentation fault.
#0  strlen () at ../sysdeps/x86_64/strlen.S:106
106 ../sysdeps/x86_64/strlen.S: No such file or directory.


Looking for strlen.S on my machine:

$ locate strlen.S
/usr/src/linux-source-3.10/arch/alpha/lib/ev67-strlen.S
/usr/src/linux-source-3.10/arch/alpha/lib/strlen.S
/usr/src/linux-source-3.10/arch/arc/lib/strlen.S
/usr/src/linux-source-3.10/arch/ia64/lib/strlen.S
/usr/src/linux-source-3.10/arch/m32r/lib/strlen.S
/usr/src/linux-source-3.10/arch/sh/lib/strlen.S
/usr/src/linux-source-3.10/arch/sh/lib64/strlen.S
/usr/src/linux-source-3.10/arch/sparc/lib/strlen.S



Best regards,

George

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

Kernel: Linux 3.14-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

Versions of packages ifuse depends on:
ii  fuse   2.9.3-10
ii  libc6  2.18-7
ii  libfuse2   2.9.3-10
ii  libimobiledevice4  1.1.6+dfsg-1
ii  libplist2  1.11-3

ifuse recommends no packages.

ifuse suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
On Mon, Jan 09, 2017 at 07:49:26PM +, George B. wrote:
> Hi Andreas,
> 
> I have successfully used ifuse since then so I think this bug is safe to 
> close.

Thanks for the update, I am closing it now.

> Best regards,
> 
> George

cu
Adrian

-- 

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

Bug#811945: marked as done (ucimf-openvanilla: FTBFS with GCC 6: unable to find string literal operator)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 20:14:12 +0200
with message-id <20170118181412.xh64oottft7jewcr@localhost>
and subject line Fixed in 2.10.11-3
has caused the Debian Bug report #811945,
regarding ucimf-openvanilla: FTBFS with GCC 6: unable to find string literal 
operator
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.)


-- 
811945: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811945
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ucimf-openvanilla
Version: 2.10.11-2
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-literal-operator

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> /bin/bash ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. 
>  -I../include   -g -O2 -c -o openvanilla_la-openvanilla.lo `test -f 
> 'openvanilla.cpp' || echo './'`openvanilla.cpp
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -I../include -g -O2 -c 
> openvanilla.cpp  -fPIC -DPIC -o .libs/openvanilla_la-openvanilla.o
> In file included from openvanilla.cpp:26:0:
> openvanilla.cpp: In member function 'virtual void OVImfService::notify(const 
> char*)':
> debug.h:9:93: error: unable to find string literal operator 
> 'operator""format' with 'const char [9]', 'long unsigned int' arguments
>  #define UCIMF_DEBUG(format...)  {extern int LogFd; if( LogFd >=0 ){ 
> dprintf( LogFd, "[DEBUG]:"format);} }
>   
>^
> 
> debug.h:12:28: note: in expansion of macro 'UCIMF_DEBUG'
>  #define UrDEBUG(format...) UCIMF_DEBUG(format)
> ^~~
> 
> openvanilla.cpp:147:2: note: in expansion of macro 'UrDEBUG'
>   UrDEBUG( "%s\n", msg );
>   ^~~
> 
> Makefile:333: recipe for target 'openvanilla_la-openvanilla.lo' failed
> make[3]: *** [openvanilla_la-openvanilla.lo] Error 1

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Version: 2.10.11-3


ucimf-openvanilla (2.10.11-3) unstable; urgency=medium
...
  * Fix GCC-6 compiling error.
...
 -- ChangZhuo Chen (陳昌倬)   Wed, 18 Jan 2017 19:56:54 +0800


cu
Adrian

-- 

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

Bug#838665: /usr/lib/python3/dist-packages/speechd_config/config.py: runs argparse on Python module import

[Adrian Bunk]

On Mon, Sep 26, 2016 at 02:16:45PM +0200, Sebastian Humenda wrote:
> Hi

Hi Sebastian,

> I'll provide a patch to upstream shortly and attach it here as well, so that 
> it
> is fixed both upstream and downstream.

any news regarding that?

> Sebastian

Thanks
Adrian

-- 

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

Bug#851790: installation-reports: DNS not working

[Wookey]

Package: installation-reports
Severity: grave
Tags: d-i
Justification: renders package unusable

Dear Maintainer,

The current installer, with the new 4.9 kernel, is unable to resolve
domains, so is quite seriously broken.

This was noted during install on an arm64 gigabyte MP30-AR1
desktop/server, when choose-mirror failed, but it soon became clear
that DNS was not working.

Testing on an x86 VM with the same daily image (18th Jan 2017) found
the same problem. Going back to the rc1 installer image (4.8 kernel)
it works OK.

Tests showed that the network came up fine and things are pingable by IP, but 
not name:
# ping wookware.org   
ping: bad address 'wookware.org'
# ping 93.93.131.118
PING 93.93.131.118 (93.93.131.118): 56 data bytes
64 bytes from 93.93.131.118: seq=0 ttl=50 time=19.892 ms

similarly the failing line from the choose-mirror log works if an address is 
inserted:
Jan 18 17:04:11 choose-mirror[31201]: DEBUG: command: wget --no-verbose 
http://debian-mirror.cambridge.arm.com/debian/dists/stretch/Release -O - | grep 
-E '^(Suite|Codename|Architectures):'   

Jan 18 17:04:11 choose-mirror[31201]: WARNING **: mirror does not support the 
specified release (stretch) 

# wget --no-verbose 
http://debian-mirror.cambridge.arm.com/debian/dists/stretch/Release -O - | grep 
-E '^(Suite|Codename|Architectures):'
wget: unable to resolve host address 'debian-mirror.cambridge.arm.com'

# wget --no-verbose http://10.1.194.51/debian/dists/stretch/Release -O - | gre
p -E '^(Suite|Codename|Architectures):'
Suite: testing
Codename: stretch
Architectures: amd64 arm64 armel armhf i386 mips mips64el mipsel ppc64el s390x
2017-01-18 17:47:12 URL:http://10.1.194.51/debian/dists/stretch/Release 
[177979/177979] -> "-" [1]

resolv.conf is as expected:
search cambridge.arm.com
nameserver 10.1.2.24
nameserver 10.1.2.23

(adding nameserver 8.8.8.8 makes no difference)

Watching packets go by when doing a VM install it is clear that the
local DNS server returns the correct response, but this is being ignored
or lost by the D-I initrd.

attached is an strace of strace ping wookware.org > /tmp/tracelog 2>&1

That gets a response from the server OK, but then goes on to ask the
other one. a working strace then uses the provided IP address. So
there is nothing obviously going wrong there.

-- Package-specific info:

Boot method: USB
Image version: 
http://gemmei.acc.umu.se/cdimage/daily-builds/daily/arch-latest/arm64/iso-cd/debian-testing-arm64-netinst.iso
Date: 

Machine: Gigabyte MP30-AR1, (and x86 VM)
Partitions: (default guided LVM, with separate /home chosen)


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

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

Comments/Problems:

Worked as expected until DNS needed

-- 

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

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

removed automatic info as this report written on different machine fro install.
execve("/bin/ping", ["ping", "wookware.org"], [/* 14 vars */]) = 0
brk(NULL)   = 0xc9893000
faccessat(AT_FDCWD, "/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or 
directory)
mmap(NULL, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x86677000
faccessat(AT_FDCWD, "/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or 
directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
openat(AT_FDCWD, "/lib/aarch64-linux-gnu/tls/aarch64/libc.so.6", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
newfstatat(AT_FDCWD, "/lib/aarch64-linux-gnu/tls/aarch64", 0xc66b2660, 0) = 
-1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/aarch64-linux-gnu/tls/libc.so.6", O_RDONLY|O_CLOEXEC) = 
-1 ENOENT (No such file or directory)
newfstatat(AT_FDCWD, "/lib/aarch64-linux-gnu/tls", 0xc66b2660, 0) = -1 
ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/aarch64-linux-gnu/aarch64/libc.so.6", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
newfstatat(AT_FDCWD, "/lib/aarch64-linux-gnu/aarch64", 0xc66b2660, 0) = -1 
ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/aarch64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 
ENOENT (No such file or directory)
newfstatat(AT_FDCWD, "/lib/aarch64-linux-gnu", {st_mode=S_IFDIR|0755, 
st_size=360, ...}, 0) = 0
openat(AT_FDCWD, 

Bug#848368: llvm-toolchain-3.9: Please add ELF symbols versions to the libraries

[Lisandro Damián Nicanor Pérez Meyer]

On martes, 17 de enero de 2017 22:21:51 ART Rebecca N. Palmer wrote:
[snip] 
> This suggests the fix (warning: untested and not my area of expertise -
> and if it is using that line, why is there no -Wl,--no-whole-archive in
> the build log?):

This part I don't know.

> --- a/tools/llvm-shlib/CMakeLists.txt
> +++ b/tools/llvm-shlib/CMakeLists.txt
> @@ -42,7 +42,7 @@
>   list(REMOVE_DUPLICATES LIB_NAMES)
>   if("${CMAKE_SYSTEM_NAME}" STREQUAL "Linux" OR "${CMAKE_SYSTEM_NAME}"
> STREQUAL "GNU" OR "${CMAKE_SYSTEM_NAME}" STREQUAL "kFreeBSD") # FIXME:
> It should be "GNU ld for elf"
> # GNU ld doesn't resolve symbols in the version script.
> -  set(LIB_NAMES -Wl,--whole-archive ${LIB_NAMES} -Wl,--no-whole-archive)
> +  set(LIB_NAMES
> -Wl,--version-script,../../../tools/llvm-shlib/simple_version_script.map
> -Wl,--whole-archive ${LIB_NAMES} -Wl,--no-whole-archive)
>   elseif("${CMAKE_SYSTEM_NAME}" STREQUAL "Darwin")
> set(LIB_NAMES -Wl,-all_load ${LIB_NAMES})
>   endif()
> --- a/dev/null
> +++ b/simple_version_script.map
> @@ -0,0 +1,1 @@
> +LLVM_3.9 { global: *; };

Probably the "../../../tools" path should be replaced by $
{CMAKE_CURRENT_SOURCE_DIR}/tools

> (Should also work with the obvious change for 3.8; I haven't checked
> 3.7.  Deliberately not making 3.9 "depend" on 3.8, as the whole point is
> to make the linker treat them as separate libraries)

Right.

> Some LLVM-using libraries use -Bsymbolic to avoid similar problems (e.g.
> #768185), but I don't know whether enabling that on LLVM itself would
> help: it may well be papering over a problem that symbol versioning
> would really solve.

Right.

-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#851579: marked as done (lcdproc: fails to install: post-installation script returned error exit status 10)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 19:03:59 +
with message-id 
and subject line Bug#851579: fixed in lcdproc 0.5.8~rc2-1
has caused the Debian Bug report #851579,
regarding lcdproc: fails to install: post-installation script returned error 
exit status 10
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.)


-- 
851579: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851579
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lcdproc
Version: 0.5.8~rc1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Selecting previously unselected package lcdproc.
  (Reading database ... 
(Reading database ... 8007 files and directories currently installed.)
  Preparing to unpack .../lcdproc_0.5.8~rc1-1_amd64.deb ...
  Unpacking lcdproc (0.5.8~rc1-1) ...
  Setting up lcdproc (0.5.8~rc1-1) ...
  dpkg: error processing package lcdproc (--configure):
   subprocess installed post-installation script returned error exit status 10
  Errors were encountered while processing:
   lcdproc


Is that a debconf question not being asked since piuparts runs the tests with
DEBIAN_FRONTEND=noninteractive ?


cheers,

Andreas


lcdproc_0.5.8~rc1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: lcdproc
Source-Version: 0.5.8~rc2-1

We believe that the bug you reported is fixed in the latest version of
lcdproc, 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.
Dominique Dumont  (supplier of updated lcdproc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 18 Jan 2017 19:29:02 +0100
Source: lcdproc
Binary: lcdproc lcdproc-extra-drivers lcdproc-dbg
Architecture: source
Version: 0.5.8~rc2-1
Distribution: experimental
Urgency: medium
Maintainer: Dominique Dumont 
Changed-By: Dominique Dumont 
Description:
 lcdproc- LCD display driver daemon and clients
 lcdproc-dbg - debugging symbols for lcdproc
 lcdproc-extra-drivers - extra drivers for the LCD display driver daemon
Closes: 851579
Changes:
 lcdproc (0.5.8~rc2-1) experimental; urgency=medium
 .
   * New upstream version 0.5.8~rc2
   * control: build-dep on cme >= 1.016-2 to deliver
 debconf files (Closes: #851579)
Checksums-Sha1:
 dd9c29450a99d616d5ca73caac7764c7f45a90ef 2644 lcdproc_0.5.8~rc2-1.dsc
 1e1efdcb8fb3b22c0b2f2ced4991f68d653d38fd 905790 lcdproc_0.5.8~rc2.orig.tar.gz
 0b77dbeced4dbff0829069847f2a591014c65fa5 14420 
lcdproc_0.5.8~rc2-1.debian.tar.xz
Checksums-Sha256:
 399e152e6e76117a87daed67bebe66890185eebc6d9cbcf18c620f185f3a78e2 2644 
lcdproc_0.5.8~rc2-1.dsc
 5748ee9198f8900c976e8291a531bb32ff7589a357c426dbc9d26e05287b1207 905790 
lcdproc_0.5.8~rc2.orig.tar.gz
 7b6cbadcb84e3e461bfe36f9a3055c244f9085241db1074b5740ccb7cea8f152 14420 
lcdproc_0.5.8~rc2-1.debian.tar.xz
Files:
 9c00c455199f33b50b4b53eb5baa6875 2644 utils extra lcdproc_0.5.8~rc2-1.dsc
 7b3fc854e003f2bf7e0f3f77224c789e 905790 utils extra 
lcdproc_0.5.8~rc2.orig.tar.gz
 ee07fdb46950d2220c2bd6a0edc934b2 14420 utils extra 
lcdproc_0.5.8~rc2-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEn3I5/LZk8Qsz6dwDwx9P2UmrK2wFAlh/uNIACgkQwx9P2Umr
K2wVyQ//aiKF+R4kYLknV0vmgzv7hS8HqBEytLAOMyGT5fkQjknbGry8nlHMKMQ5
8Z6zGeISsRyT+XcVtZt9ZGO/5yn3OcoRFLh0e9hXhSiiUtsHP16Jp1+SH+jYy18O
JdJOHnjypKVRIo7YDrqN4sje1aKbxBigNVuwHqU2Aax64aMq87bXE+ECykRf4V/f
u3J5v8WXGlDVz7CSDaK7Z6Dpn1ga4HG0j2Dm4ehZhOggf+pkw11H2WdLXztZmQQq
gAHnyyTO0X4dirU9eXUZwludKsY51SyJld4TL4tjqjfVmEeQM0sITYpszF7lR0ip
I/gG79P9RYkm3+POeI/uh4aLynmivsebc/83txU/DXThk3Xb3nG07nbi83c8/CsZ
Mo+gkqZLAAcYTEykk2/BL+ngE7i79VDjYYLz+dVSxAhinXog+FEFRUqnPcZ5B4Bm
bDweNmtjjnbPXQQW5DuqtJyV8PbLy56l3v1MTJ8JzC3TAxIR2vVpdIcV7YLRa9PE
ZT/4Jr6FluDRMJM0vdFg8GEDuWuTfIE1SWNxeza+769bIOGAr8FaQ7kuJn5E06gU
BtVIsmXwPgVEhXoNWw6CjrXYynrLt/Iz0vCdUVahn5/L4aIXRdzoMANRGkJiXNAa
TJimqxwtLcmOGrKK+x1esGmWF8/NjyjuirewLFUjiBmkhyMWD6M=
=AyFJ
-END PG

Processed: tagging 851039

[Debian Bug Tracking System]

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

> tags 851039 + help
Bug #851039 [src:python-apt] python-apt: FTBFS: Test failures
Added tag(s) help.
> thanks
Stopping processing here.

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

Bug#848236: Remaining issue with gbrowse - any help (Was: Urgent call to BioPerl users (Was: Bug#848236: src:gbrowse: ...)

[Lincoln Stein]

Yes, I'll remove it immediately and apply the patches to bio::graphics as
well.

Lincoln

On Wed, Jan 18, 2017 at 11:58 AM, Andreas Tille  wrote:

> On Wed, Jan 18, 2017 at 05:39:05PM +0100, gregor herrmann wrote:
> > >
> > >https://anonscm.debian.org/cgit/debian-med/gbrowse.git/
> tree/debian/patches
> >
> > Oh, cool, adding the (build)-dep is really enough, no patching
> > required. Nice.
>
> Yes, we needed this for another package ...
>
> > For stretch, I think there's still one thing to do:
> > autopkgtest still fails with
> >
> > pmerror:/tmp/apt-dpkg-install-qeDTFa/103-gbrowse.deb:42.2343:trying to
> overwrite '/usr/share/man/man3/Bio::DB::SeqFeature::Store::LoadHelper.3pm.gz',
> which is also in package libbio-perl-perl 1.7.1-2
>
> Urgs - Lincoln, I guess it makes sense to remove this copy of bioperl
> even in your distribution.  What do you think?
>
> Kind regards
>
>Andreas.
>
>
> --
> http://fam-tille.de
>



-- 
*Lincoln Stein*

Scientific Director (Interim), Ontario Institute for Cancer Research
Director, Informatics and Bio-computing Program, OICR
Senior Principal Investigator, OICR
Professor, Department of Molecular Genetics, University of Toronto


*Ontario Institute for Cancer Research*
MaRS Centre
661 University Avenue
Suite 510
Toronto, Ontario
Canada M5G 0A3

Tel: 416-673-8514
Mobile: 416-817-8240
Email: lincoln.st...@gmail.com
Toll-free: 1-866-678-6427
Twitter: @OICR_news

*Executive Assistant*
*Lisa Duncan*
Tel: 647-260-7970 <(647)%20260-7970>
Email: lisa.dun...@oicr.on.ca 
www.oicr.on.ca

This message and any attachments may contain confidential and/or privileged
information for the sole use of the intended recipient. Any review or
distribution by anyone other than the person for whom it was originally
intended is strictly prohibited. If you have received this message in
error, please contact the sender and delete all copies. Opinions,
conclusions or other information contained in this message may not be that
of the organization.

Bug#851790: installation-reports: DNS not working

[Steve McIntyre]

On Wed, Jan 18, 2017 at 06:43:33PM +, Wookey wrote:
>Package: installation-reports
>Severity: grave
>Tags: d-i
>Justification: renders package unusable
>
>Dear Maintainer,
>
>The current installer, with the new 4.9 kernel, is unable to resolve
>domains, so is quite seriously broken.

hosts, not domains, but yes...

>This was noted during install on an arm64 gigabyte MP30-AR1
>desktop/server, when choose-mirror failed, but it soon became clear
>that DNS was not working.
>
>Testing on an x86 VM with the same daily image (18th Jan 2017) found
>the same problem. Going back to the rc1 installer image (4.8 kernel)
>it works OK.
>
>Tests showed that the network came up fine and things are pingable by IP, but 
>not name:
># ping wookware.org   
>ping: bad address 'wookware.org'
># ping 93.93.131.118
>PING 93.93.131.118 (93.93.131.118): 56 data bytes
>64 bytes from 93.93.131.118: seq=0 ttl=50 time=19.892 ms
>
>similarly the failing line from the choose-mirror log works if an address is 
>inserted:
>Jan 18 17:04:11 choose-mirror[31201]: DEBUG: command: wget --no-verbose 
>http://debian-mirror.cambridge.arm.com/debian/dists/stretch/Release -O - | 
>grep -E '^(Suite|Codename|Architectures):' 
>  
>Jan 18 17:04:11 choose-mirror[31201]: WARNING **: mirror does not support the 
>specified release (stretch) 
>
># wget --no-verbose 
>http://debian-mirror.cambridge.arm.com/debian/dists/stretch/Release -O - | 
>grep -E '^(Suite|Codename|Architectures):'
>wget: unable to resolve host address 'debian-mirror.cambridge.arm.com'
>
># wget --no-verbose http://10.1.194.51/debian/dists/stretch/Release -O - | gre
>p -E '^(Suite|Codename|Architectures):'
>Suite: testing
>Codename: stretch
>Architectures: amd64 arm64 armel armhf i386 mips mips64el mipsel ppc64el s390x
>2017-01-18 17:47:12 URL:http://10.1.194.51/debian/dists/stretch/Release 
>[177979/177979] -> "-" [1]
>
>resolv.conf is as expected:
>search cambridge.arm.com
>nameserver 10.1.2.24
>nameserver 10.1.2.23
>
>(adding nameserver 8.8.8.8 makes no difference)
>
>Watching packets go by when doing a VM install it is clear that the
>local DNS server returns the correct response, but this is being ignored
>or lost by the D-I initrd.

For the sake of completeness, I can confirm that the same problem
shows up when running on a different network too. I also see this
using the oldest amd64 daily I can grab (from 2017-01-17) which has
the 4.9 kernel too.

I'll see if I can debug this, but I'm not sure where to look straight
away.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Managing a volunteer open source project is a lot like herding
 kittens, except the kittens randomly appear and disappear because they
 have day jobs." -- Matt Mackall

Bug#805988: aboot : include the binaries in source to build on amd64

[Adrian Bunk]

On Wed, Jan 18, 2017 at 06:54:10PM +0100, Santiago Vila wrote:
> On Wed, Jan 18, 2017 at 06:38:44PM +0100, jhcha54008 wrote:
> 
> > I wonder if the following solution would be accepted (see the two patches 
> > attached) : let the source package ship the two binaries (bootlx and 
> > net_aboot.nh). [...]
> 
> Hmm, but this is like removing a hack and creating another one in another 
> place.
> 
> The previous package was a "fake" Arch:all package, so to speak, and now
> we would have a "fake" source package, as it would include binaries.
> 
> We don't want binaries inside source packages (and I think ftpmasters
> would surely agree on this).
> 
> If alpha is not a release architecture, would it really be a problem
> to remove this from testing before the release of stretch while we keep it in
> unstable?
> 
> We could meet the release goal of all packages being buildable
> in our Arch:all autobuilder that way without causing a major headache
> to users of alpha.
> 
> Alternatively, there is also the possibility of asking the Release
> Managers for permission to use stretch-ignore here.

"Arch:all autobuilder" is only part of the problem, since alpha won't be 
part of stretch there is no option to build this package on *any* machine
running stretch.

Looks like a clear GPL violation to me.

As Steve already suggested, using the gcc-alpha-linux-gnu package might 
be an option for building aboot.

I'll open a similar bug against palo.

> Thanks.

cu
Adrian

-- 

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

Bug#851792: palo ships binary in the sources

[Adrian Bunk]

Package: palo
Version: 1.95
Severity: serious

>From debian/rules:

@if [ `dpkg --print-architecture` = hppa ]; \
 then \
echo "Regenerating iplboot."; \
$(MAKE) realclean; \
$(MAKE) iplboot; \
 else \
echo "Leaving iplboot in place since we're not building on 
hppa."; \
 fi

Since hppa isn't part of jessie or stretch, there is no option to build
this package on *any* machine inside this release.

Looks like a clear GPL violation to me.

If palo should continue to be available on non-hppa machines,
a (binary-all) package that uses gcc-hppa-linux-gnu for building
might be an option.

Bug#828468: marked as done (openhpi: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 20:53:05 +
with message-id 
and subject line Bug#828468: fixed in openhpi 3.6.1-2.1
has caused the Debian Bug report #828468,
regarding openhpi: 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.)


-- 
828468: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828468
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openhpi
Version: 3.6.1-2
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/openhpi_3.6.1-2_amd64-20160529-1459

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: openhpi
Source-Version: 3.6.1-2.1

We believe that the bug you reported is fixed in the latest version of
openhpi, 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.
Adrian Bunk  (supplier of updated openhpi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 18 Jan 2017 21:45:48 +0200
Source: openhpi
Binary: libopenhpi3 libopenhpi-dev openhpid openhpi-clients 
openhpi-plugin-ilo2-ribcl openhpi-plugin-ipmi openhpi-plugin-ipmidirect 
openhpi-plugin-oa-soap openhpi-plugin-slave openhpi-plugin-test-agent 
openhpi-plugin-snmp-bc openhpi-plugin-sysfs openhpi-plugin-watchdog 
openhpi-plugin-simulator openhpi-plugin-dynamic-simulator openhpi 
libopenhpi3-dbgsym openhpid-dbgsym openhpi-clients-dbgsym 
openhpi-plugin-ilo2-ribcl-dbgsym openhpi-plugin-ipmi-dbgsym 
openhpi-plugin-ipmidirect-dbgsym openhpi-plugin-oa-soap-dbgsym 
openhpi-plugin-slave-dbgsym openhpi-plugin-test-agent-dbgsym 
openhpi-plugin-snmp-bc-dbgsym openhpi-plugin-sysfs-dbgsym 
openhpi-plugin-watchdog-dbgsym openhpi-plugin-simulator-dbgsym 
openhpi-plugin-dynamic-simulator-dbgsym
Architecture: source
Version: 3.6.1-2.1
Distribution: unstable
Urgency: medium
Maintainer: Bryan Sutula 
Changed-By: Adrian Bunk 
Description:
 libopenhpi-dev - OpenHPI libraries (development files)
 libopenhpi3 - OpenHPI libraries (runtime and support files)
 libopenhpi3-dbgsym - Debug symbols for libopenhpi3 library
 openhpi- SAF's HPI: Abstracted interface for managing computer hardware
 openhpi-clients - OpenHPI example client programs
 openhpi-clients-dbgsym - Debug symbols for OpenHPI example client programs
 openhpi-plugin-dynamic-simulator - OpenHPI plugin module for a dynamic 
simulator
 openhpi-plugin-dynamic-simulator-dbgsym - Debug symbols for 
openhpi-plugin-dynamic-simulator plugin module
 openhpi-plugin-ilo2-ribcl - OpenHPI plugin module for HP's ProLiant rackmount 
servers
 openhpi-plugin-ilo2-ribcl-dbgsym - Debug symbols for openhpi-plugin-ilo2-ribcl 
plugin module
 openhpi-plugin-ipmi - OpenHPI plugin module for OpenIPMI
 openhpi-plugin-ipmi-dbgsym - Debug symbols for openhpi-plugin-ipmi plugin 
module
 openhpi-plugin-ipmidirect - OpenHPI plugin module for direct IPMI over LAN 
(RMCP) or SMI
 openhpi-plugin-ipmidirect-dbgsym - Debug symbols for openhpi-plugin-ipmidirect 
plugin module
 openhpi-plugin-oa-soap - OpenHPI plugin module for HP's BladeSystem c-Class
 openhpi-plugin-oa-soap-dbgsym - Debug symbols for openhpi-plugin-oa-soap 
plugin module
 openhpi-plugin-simulator - OpenHPI plugin module for a simulator that works 
without hardware
 openhpi-plugin-simulator-dbgsym - Debug symbols for openhpi-plugin-simulator 
plugin module
 openhpi-plugin-slave - OpenHPI plugin module for slave plugin
 openhpi-plugin-slave-dbgsym - Debug symbols for openhpi-plugin-slave plugin 
module
 openhpi-plugin-snm

Processed: Tag

[Debian Bug Tracking System]

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

> tags 762400 stretch sid
Bug #762400 {Done: Michael Biebl } [src:gtk+3.0] gtk+3.0 has 
a direct Build-Depends on itself
Bug #824982 {Done: Michael Biebl } [src:gtk+3.0] src:gtk+3.0: 
unsatisfiable dependency on libgtk-3-common
Bug #824999 {Done: Michael Biebl } [src:gtk+3.0] gtk+3.0: 
Architecture: all packages cannot be built
Added tag(s) stretch and sid.
Added tag(s) stretch and sid.
Added tag(s) sid and stretch.
> thanks
Stopping processing here.

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

Processed: bcron: some failing test disabled for now

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #839443 [src:bcron] bcron: FTBFS: tests failures
Severity set to 'important' from 'serious'

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

Processed: Unarchive and mark RC

[Debian Bug Tracking System]

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

> unarchive 783615
Bug #783615 {Done: Michael Shuler } [ca-certificates] 
"update-ca-certificates --fresh" doesn't correctly re-add certificates in 
/usr/local/share/ca-certificates
Unarchived Bug 783615
> severity 783615 serious
Bug #783615 {Done: Michael Shuler } [ca-certificates] 
"update-ca-certificates --fresh" doesn't correctly re-add certificates in 
/usr/local/share/ca-certificates
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#839443: bcron: some failing test disabled for now

[Gianfranco Costamagna]

control: severity -1 important

Hi, I'm downgrading this one, to make the current bcron have chances to 
migrated.

I think tests should be fixed, but disabling a couple of them "fixed" the 
build, and
will probably make it go in Stretch

G.



signature.asc
Description: OpenPGP digital signature

Processed: tor: IPv6 connections through tor do not appear to work

[Debian Bug Tracking System]

Processing control commands:

> block 849845 with -1
Bug #849845 [dirmngr] dirmngr: Can't resolve keyserver hostname anymore
Bug #850606 [dirmngr] dirmngr: can't resolve ipv6 addresses when use-tor is 
enabled
849845 was not blocked by any bugs.
849845 was not blocking any bugs.
Added blocking bug(s) of 849845: 851798
850606 was not blocked by any bugs.
850606 was not blocking any bugs.
Added blocking bug(s) of 850606: 851798
> affects -1 dirmgnr
Bug #851798 [tor] tor: IPv6 connections through tor do not appear to work
Added indication that 851798 affects dirmgnr

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

Bug#850885: marked as done (apache2: Using dwww, fails with internal server error when trying to access /usr/share/doc)

[Debian Bug Tracking System]

Your message dated Wed, 18 Jan 2017 21:19:01 +
with message-id 
and subject line Bug#850885: fixed in dwww 1.13.3
has caused the Debian Bug report #850885,
regarding apache2: Using dwww, fails with internal server error when trying to 
access /usr/share/doc
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.)


-- 
850885: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850885
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apache2
Version: 2.4.25-1
Severity: normal

Dear Maintainer,

Upgrading from jessie to stretch partially broke the package "dwww" when
using apache2 as web server. dwww is a CGI web application allowing
easy access to the Debian documentation. Its entry page still works on
stretch, but when trying to access any resource under /usr/share/doc
through dwww, Apache returns an "500 Internal Server Error".

To reproduce the problem one just has to go to http://localhost/dwww,
and click on the top menu link for "/usr/share/doc".

When looking at the Apache log, the following entry can be found:

[Fri Jan 06 21:34:53.830541 2017] [http:error] [pid 6785:tid
140419151554304] [client ::1:45220] AH02429: Response header name
'Last modified' contains invalid characters, aborting request,
referer: http://localhost/dwww/

When calling the dwww CGI script manually, the 'Last modified' field
is correct however, here's the HTTP header part:

Content-type: text/html
Last modified: Tue Dec 13 14:16:35 2016
Content-Disposition: inline; filename="index.html"

When using the very same dwww application with another web server (I
tried lighttpd), it works fine as before so the issue is related to
Apache.

Compared to a default apache2 configuration, I just enabled the cgid
module as well as the dwww, dhelp and dpkg-dwww configurations. No
other changes under /etc/apache2. 

Thanks

-- Package-specific info:

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

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

Versions of packages apache2 depends on:
ii  apache2-bin  2.4.25-1
ii  apache2-data 2.4.25-1
ii  apache2-utils2.4.25-1
ii  dpkg 1.18.18
ii  init-system-helpers  1.46
ii  lsb-base 9.20161125
ii  mime-support 3.60
ii  perl 5.24.1~rc4-1
pn  perl:any 
ii  procps   2:3.3.12-3

Versions of packages apache2 recommends:
ii  ssl-cert  1.0.38

Versions of packages apache2 suggests:
pn  apache2-doc  
pn  apache2-suexec-pristine | apache2-suexec-custom  
ii  chromium [www-browser]   55.0.2883.75-3
ii  konqueror [www-browser]  4:16.08.3-1
ii  w3m [www-browser]0.5.3-33

Versions of packages apache2-bin depends on:
ii  libapr1  1.5.2-5
ii  libaprutil1  1.5.4-3
ii  libaprutil1-dbd-sqlite3  1.5.4-3
ii  libaprutil1-ldap 1.5.4-3
ii  libc62.24-8
ii  libldap-2.4-22.4.44+dfsg-2
ii  liblua5.2-0  5.2.4-1.1+b1
ii  libnghttp2-141.17.0-1
ii  libpcre3 2:8.39-2
ii  libssl1.0.2  1.0.2j-4
ii  libxml2  2.9.4+dfsg1-2.1
pn  perl:any 
ii  zlib1g   1:1.2.8.dfsg-4

Versions of packages apache2-bin suggests:
pn  apache2-doc  
pn  apache2-suexec-pristine | apache2-suexec-custom  
ii  chromium [www-browser]   55.0.2883.75-3
ii  konqueror [www-browser]  4:16.08.3-1
ii  w3m [www-browser]0.5.3-33

Versions of packages apache2 is related to:
ii  apache2  2.4.25-1
ii  apache2-bin  2.4.25-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: dwww
Source-Version: 1.13.3

We believe that the bug you reported is fixed in the latest version of
dwww, 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 850...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Robert Luberda  (sup