Bug#808851: Bug#808851: artemis REMOVED from testing

[Andreas Tille]

On Tue, Jan 19, 2016 at 08:59:36PM -0800, Afif Elghraoui wrote:
> I could use some help with this bug (which
> is why I tagged it "help"), especially if the maintainers who triggered
> the transition could offer some insight.

Unfortunately I can not provide much help in Java issues but I have made
very godd experiences to contact debian-j...@lists.debian.org.

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#811428: [debian-mysql] Bug#811428: Bug#811428: mysql-5.5: Multiple security fixes from the January 2016 CPU

[Lars Tangvald]

The git tree is missing a copyright update made by the security team, 
which will need to be merged.


--
Lars Tangvald

On 01/19/2016 10:02 PM, Norvald H. Ryeng wrote:
The Critical Patch Update is out: 
http://www.oracle.com/technetwork/topics/security/cpujan2016-2367955.html


The following vulnerabilities are fixed by upgrading from MySQL 5.5.46 
to 5.5.47:


CVE-2016-0505
CVE-2016-0546
CVE-2016-0597
CVE-2016-0598
CVE-2016-0600
CVE-2016-0606
CVE-2016-0608
CVE-2016-0609
CVE-2016-0596
CVE-2016-0616

Regards,

Norvald H. Ryeng

___
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#788062: os-prober corrupts LVs/partitions while being mounted inside a VM

[Chris Kuehl]

Hi,

If this can't be fixed quickly, would it make sense to push an update
which disables os-prober on jessie in cases which are known to (even
possibly) lead to data loss?

I hate to post a "me too" message, but it's a little disheartening to
know that a bug that causes pretty bad data loss in fairly common
scenarios has been known about since June without being patched in
stable.

We just spent a lot of time and effort pinpointing and recovering from
this bug ourselves. I wish we could help others who are yet to hit this
bug, as surely more people are going to lose data until we patch this.

A simple reproduction:

- on the host, run
while :; do os-prober; done
- on a guest, perform some disk IO, e.g.
dd if=/dev/zero of=/test

On our systems, this reproduces the issue very quickly. The guest runs
under KVM and the guest's disk is an LVM logical volume. The filesystem
is ext4.

Thanks for your work on Debian!

Chris

Bug#808851: [Debian-med-packaging] Bug#808851: artemis REMOVED from testing

[Afif Elghraoui]

Hi, Andreas,

على الثلاثاء 19 كانون الثاني 2016 ‫08:56، كتب Andreas Tille:
> Hi,
> 
> any news about this bug?

I did some work on this the day after it was reported and posted an
update (besides what can be seen in my commit messages) to the bug log.

>  I wonder whether the latest htsjdk might solve
> this. If I'm not misleaded this depends from libngs-java and is thus
> blocked by #809375.  Could anybody confirm that this is correct?
> 

I don't know. It at least did not used to depend on those, but there
have apparently been some serious API changes in picard and I think
htsjdk is now a dependency. I could use some help with this bug (which
is why I tagged it "help"), especially if the maintainers who triggered
the transition could offer some insight.

Thanks and regards
Afif

-- 
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name

Bug#811433: Not a fix, but a workaround

[Scott Kitterman]

On January 19, 2016 10:43:32 PM EST, "László Böszörményi (GCS)" 
 wrote:
>On Wed, Jan 20, 2016 at 2:20 AM, Scott Kitterman 
>wrote:
>> As discussed with the release team, I'm going to upload the attached
>NMU to at
>> least get python-greenlet-doc installable again.
> Was it rejected? Hours passed and it doesn't show up in the QA pages.
>Uploading my version with other fixes and changes.
>
>Laszlo/GCS

I didn't get a reject, but please go ahead. I've no idea what happened.

Scott K

Bug#811433: Not a fix, but a workaround

[GCS]

On Wed, Jan 20, 2016 at 2:20 AM, Scott Kitterman  wrote:
> As discussed with the release team, I'm going to upload the attached NMU to at
> least get python-greenlet-doc installable again.
 Was it rejected? Hours passed and it doesn't show up in the QA pages.
Uploading my version with other fixes and changes.

Laszlo/GCS

Bug#811401: i7z-gui: X errors and empty window

[Andreas Beckmann]

Control: severity -1 normal
Control: retitle -1 i7z-gui: X errors and empty window when run as root

On 2016-01-18 17:03, Laurent Bigonville wrote:
> When starting i7z-gui I get the following errors and an empty grey window, 
> nothing more.
> 
> This renders the package unusable.

This is a typical symptom of running an X application as root.
I have no (nor do I want any) experience doing this either :-)

> X Error: BadAccess (attempt to access private resource denied) 10
>   Extension:130 (MIT-SHM)
>   Minor opcode: 1 (X_ShmAttach)
>   Resource id:  0x159

I don't use the GUI myself, just the i7z command line tool (and I run
that as root). But I just tried to get the GUI running as a normal user:

# modprobe msr
# chmod 666 /dev/cpu/*/msr
# setcap cap_sys_rawio=ep /usr/sbin/i7z_GUI
$ i7z_GUI

Better (and maybe persistent) solutions welcome.

Andreas

PS: thanks to an insane bit of inline assembly for cpuid usage, it may
crash on amd64. Will be fixed shortly. And maybe I document the above
solution :-)

Processed: Re: Bug#811401: i7z-gui: X errors and empty window

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #811401 [i7z-gui] i7z-gui: X errors and empty window
Severity set to 'normal' from 'grave'
> retitle -1 i7z-gui: X errors and empty window when run as root
Bug #811401 [i7z-gui] i7z-gui: X errors and empty window
Changed Bug title to 'i7z-gui: X errors and empty window when run as root' from 
'i7z-gui: X errors and empty window'

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

Processed: reassign 811662 to init-system-helpers, cloning 811662, reassign -1 to openrc

[Debian Bug Tracking System]

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

> reassign 811662 init-system-helpers
Bug #811662 [openrc] init-system-helpers: file conflict with openrc: 
/usr/sbin/update-rc.d
Bug reassigned from package 'openrc' to 'init-system-helpers'.
Ignoring request to alter found versions of bug #811662 to the same values 
previously set
Ignoring request to alter fixed versions of bug #811662 to the same values 
previously set
> clone 811662 -1
Bug #811662 [init-system-helpers] init-system-helpers: file conflict with 
openrc: /usr/sbin/update-rc.d
Bug 811662 cloned as bug 811708
> reassign -1 openrc
Bug #811708 [init-system-helpers] init-system-helpers: file conflict with 
openrc: /usr/sbin/update-rc.d
Bug reassigned from package 'init-system-helpers' to 'openrc'.
Ignoring request to alter found versions of bug #811708 to the same values 
previously set
Ignoring request to alter fixed versions of bug #811708 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: tagging 810860, tagging 811317

[Debian Bug Tracking System]

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

> tags 810860 + pending
Bug #810860 [usrmerge] usrmerge: System cannot be rebooted after partial 
usrmerge installation
Added tag(s) pending.
> tags 811317 + pending
Bug #811317 [usrmerge] usrmerge: please add a conflicts on cruft-ng (<< 0.4.4)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#811662: init-system-helpers: file conflict with openrc: /usr/sbin/update-rc.d

[Michael Biebl]

Control: clone -1
Control: reassign -1 openrc

Am 20.01.2016 um 01:46 schrieb Adam Borowski:
> Package: init-system-helpers
> Version: 1.25
> Severity: serious
> Justification: Policy 7.4
> 
> Hi!
> 
> Unpacking init-system-helpers (1.25) over (1.24) ...
> dpkg: error processing archive 
> /var/cache/apt/archives/init-system-helpers_1.25_all.deb (--unpack):
>  trying to overwrite '/usr/sbin/update-rc.d', which is also in package openrc 
> 0.18.3-1
> 
> 
> It's not a case of a simple move, as the file in openrc is different and has
> openrc specific contents.

The old sysv-rc package did not have a conflicts against openrc,
possibly because openrc already declared such a conflicts.

Cloning the bug for openrc, which should be updated to add a Conflicts:
init-system-helpers.

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

Processed (with 1 error): Re: Bug#811662: init-system-helpers: file conflict with openrc: /usr/sbin/update-rc.d

[Debian Bug Tracking System]

Processing control commands:

> clone -1
Unknown command or malformed arguments to command.

> reassign -1 openrc
Bug #811662 [init-system-helpers] init-system-helpers: file conflict with 
openrc: /usr/sbin/update-rc.d
Bug reassigned from package 'init-system-helpers' to 'openrc'.
No longer marked as found in versions init-system-helpers/1.25.
Ignoring request to alter fixed versions of bug #811662 to the same values 
previously set

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

Bug#811662: init-system-helpers: file conflict with openrc: /usr/sbin/update-rc.d

[Adam Borowski]

Package: init-system-helpers
Version: 1.25
Severity: serious
Justification: Policy 7.4

Hi!

Unpacking init-system-helpers (1.25) over (1.24) ...
dpkg: error processing archive 
/var/cache/apt/archives/init-system-helpers_1.25_all.deb (--unpack):
 trying to overwrite '/usr/sbin/update-rc.d', which is also in package openrc 
0.18.3-1


It's not a case of a simple move, as the file in openrc is different and has
openrc specific contents.

Bug#811428: [debian-mysql] Bug#811428: Bug#811428: mysql-5.5: Multiple security fixes from the January 2016 CPU

[Clint Byrum]

Is anyone working on the build/test/upload of the final binaries?

Excerpts from Norvald H. Ryeng's message of 2016-01-19 13:02:57 -0800:
> The Critical Patch Update is out:  
> http://www.oracle.com/technetwork/topics/security/cpujan2016-2367955.html
> 
> The following vulnerabilities are fixed by upgrading from MySQL 5.5.46 to  
> 5.5.47:
> 
> CVE-2016-0505
> CVE-2016-0546
> CVE-2016-0597
> CVE-2016-0598
> CVE-2016-0600
> CVE-2016-0606
> CVE-2016-0608
> CVE-2016-0609
> CVE-2016-0596
> CVE-2016-0616
> 
> Regards,
> 
> Norvald H. Ryeng
> 

Bug#754960: Still present in jessie

[James Valleroy]

On Fri, 24 Apr 2015 16:14:57 +0200 Stephane Bortzmeyer
 wrote:
> As of today, jessie still has the problem.
> GnuTLS 2.12.23 and 0.5.10
> That makes two serious security bugs against libapache2-mod-gnutls
> (#642357 and this one).
>
> There was a conversation on ServerFault
>  which mentions a version 0.6
> which never occurred.
>
>

The upstream ticket has been closed as fixed, and mentions the bug is no
longer present in v0.7.2.

Since 0.7.2 is in unstable now, should this bug be closed?

--
James



signature.asc
Description: OpenPGP digital signature

Processed: reassign 808675 to src:publib, forcibly merging 790273 808675

[Debian Bug Tracking System]

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

> reassign 808675 src:publib
Bug #808675 [src:liwc] liwc: FTBFS: strutil.h:67:7: error: expected identifier 
or '(' before '__extension__'char *strndup(const char *, size_t)
Bug reassigned from package 'src:liwc' to 'src:publib'.
No longer marked as found in versions liwc/1.21-1.
Ignoring request to alter fixed versions of bug #808675 to the same values 
previously set
> forcemerge 790273 808675
Bug #790273 [src:publib] publib: FTBFS with glibc 2.21 and gcc-5
Bug #807349 [src:publib] dwww: FTBFS: error: expected identifier or '(' before 
'__extension__'
Bug #811144 [src:publib] FTBFS: error: expected identifier or '(' before 
'__extension__'
Bug #808675 [src:publib] liwc: FTBFS: strutil.h:67:7: error: expected 
identifier or '(' before '__extension__'char *strndup(const char *, size_t)
Marked as found in versions publib/0.40-1.
Added tag(s) patch and pending.
Bug #807349 [src:publib] dwww: FTBFS: error: expected identifier or '(' before 
'__extension__'
Bug #811144 [src:publib] FTBFS: error: expected identifier or '(' before 
'__extension__'
Merged 790273 807349 808675 811144
> thanks
Stopping processing here.

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

Processed: reassign 811566 to initramfs-tools-core, forcibly merging 811479 811566

[Debian Bug Tracking System]

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

> reassign 811566 initramfs-tools-core 0.121
Bug #811566 [initramfs-tools] run-init: opening console: No such file or 
directory
Bug reassigned from package 'initramfs-tools' to 'initramfs-tools-core'.
No longer marked as found in versions initramfs-tools/0.121.
Ignoring request to alter fixed versions of bug #811566 to the same values 
previously set
Bug #811566 [initramfs-tools-core] run-init: opening console: No such file or 
directory
Marked as found in versions initramfs-tools/0.121.
> forcemerge 811479 811566
Bug #811479 [initramfs-tools-core] boot fails in "run-init -n ..."
Bug #811566 [initramfs-tools-core] run-init: opening console: No such file or 
directory
Severity set to 'critical' from 'important'
Added indication that 811566 affects xen-tools
Added tag(s) moreinfo and patch.
Merged 811479 811566
> thanks
Stopping processing here.

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

Bug#811428: [debian-mysql] Bug#811428: mysql-5.5: Multiple security fixes from the January 2016 CPU

[Lars Tangvald]

The updated changelog containing the CPU information can be found at 
https://github.com/ltangvald/mysql-5.5
The final commit is the only change from 
https://anonscm.debian.org/cgit/pkg-mysql/mysql-5.5.git

--
Lars Tangvald

Bug#811428: [debian-mysql] Bug#811428: mysql-5.5: Multiple security fixes from the January 2016 CPU

[Norvald H. Ryeng]

The Critical Patch Update is out:  
http://www.oracle.com/technetwork/topics/security/cpujan2016-2367955.html


The following vulnerabilities are fixed by upgrading from MySQL 5.5.46 to  
5.5.47:


CVE-2016-0505
CVE-2016-0546
CVE-2016-0597
CVE-2016-0598
CVE-2016-0600
CVE-2016-0606
CVE-2016-0608
CVE-2016-0609
CVE-2016-0596
CVE-2016-0616

Regards,

Norvald H. Ryeng

Processed (with 1 error): Re: Bug#811566: run-init: opening console: No such file or directory

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 811479 -1
Bug #811479 [initramfs-tools-core] boot fails in "run-init -n ..."
Unable to merge bugs because:
package of #811566 is 'initramfs-tools' not 'initramfs-tools-core'
Failed to forcibly merge 811479: Did not alter merged bugs.


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

Bug#811187: marked as done (plainbox-provider-checkbox: please switch from module-init-tools to kmod)

[Debian Bug Tracking System]

Your message dated Tue, 19 Jan 2016 22:04:37 +
with message-id 
and subject line Bug#811187: fixed in plainbox-provider-checkbox 0.25-1
has caused the Debian Bug report #811187,
regarding plainbox-provider-checkbox: please switch from module-init-tools to 
kmod
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.)


-- 
811187: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811187
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: plainbox-provider-checkbox
Version: 0.21.3-1
Severity: serious

The transitional module-init-tools package is finally gone, please
switch to kmod.


Andreas
--- End Message ---
--- Begin Message ---
Source: plainbox-provider-checkbox
Source-Version: 0.25-1

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

Debian distribution maintenance software
pp.
Sylvain Pineau  (supplier of updated 
plainbox-provider-checkbox 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: Fri, 15 Jan 2016 16:51:16 +0100
Source: plainbox-provider-checkbox
Binary: plainbox-provider-checkbox
Architecture: source amd64
Version: 0.25-1
Distribution: unstable
Urgency: medium
Maintainer: Checkbox Developers 
Changed-By: Sylvain Pineau 
Description:
 plainbox-provider-checkbox - CheckBox provider for PlainBox
Closes: 811187
Changes:
 plainbox-provider-checkbox (0.25-1) unstable; urgency=medium
 .
   * New upstream maintenance release
   * debian/watch: match new upstream tarball names
   * debian/rules: simplify override_dh_auto_install since installation
 directories are all named plainbox-provider-checkbox
   * debian/control: remove python2.x, dh-python and obexd-client dependencies
   * debian/patches: New patch to depends on kmod instead of module-init-tools.
 (Closes: #811187)
Checksums-Sha1:
 2e649101cf3c937b640b64d0583356bf1038fb6c 2391 
plainbox-provider-checkbox_0.25-1.dsc
 08be2dedd07012ff426bf50c3e409143c0ba7c1a 1352242 
plainbox-provider-checkbox_0.25.orig.tar.gz
 8b894db882f9badf259be3d33ce071817a6cfb73 10228 
plainbox-provider-checkbox_0.25-1.debian.tar.xz
 d058bdadae30501c50d9b3bcacef7b26f0de29b5 21046 
plainbox-provider-checkbox-dbgsym_0.25-1_amd64.deb
 0d2fd2d1081f7510f53a068b26ffdd4fcfdc6693 1131882 
plainbox-provider-checkbox_0.25-1_amd64.deb
Checksums-Sha256:
 02e33ec45c7b0053a8f76bfcd79ca4020a95f0b03fbb748c048bd9e4c9231c4e 2391 
plainbox-provider-checkbox_0.25-1.dsc
 6bfc166ee4fddfd6163aff2e5b0cddb78932b400348d67257c395e2e74c6a796 1352242 
plainbox-provider-checkbox_0.25.orig.tar.gz
 392f5badb400add257a69f71d2a89f3901069313cd56f23eb62bc73ff24bb269 10228 
plainbox-provider-checkbox_0.25-1.debian.tar.xz
 b643cc1f185c0acacaba59dc36068a4840b99dd8ae1d60b7cc742791a5464eae 21046 
plainbox-provider-checkbox-dbgsym_0.25-1_amd64.deb
 116ab6b303de597da5ca692fdc93351eea861c42aad349d5d8986218c44dc24a 1131882 
plainbox-provider-checkbox_0.25-1_amd64.deb
Files:
 64b950404f811a1f19780db52699348c 2391 utils optional 
plainbox-provider-checkbox_0.25-1.dsc
 3bf290caca23ba94955ed768e912ec1c 1352242 utils optional 
plainbox-provider-checkbox_0.25.orig.tar.gz
 d7f0b96882705220e5339622fe765a9b 10228 utils optional 
plainbox-provider-checkbox_0.25-1.debian.tar.xz
 ae2349fd081bbe9ec597a7dde1001f87 21046 debug extra 
plainbox-provider-checkbox-dbgsym_0.25-1_amd64.deb
 9c164a1945bb5b1587cd97e95ff2969d 1131882 utils optional 
plainbox-provider-checkbox_0.25-1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJWnqYjAAoJEK728aKnRXZFI0IP/2L9QFA+0xuvcmwuFfP8zGwK
LeF93KMk2YBH6OLOuPMgieK7D3tVHRyK8Q5dLFUeSsrjtno97tDCyVKvaFxc4+5r
DMLcnEtEqDjFIhKtT7oYghl5aLqtkvJoWTh6rD4KdSR4eDms9IWS6J/yG4N1YlRd
KAISk1j8S+J2Y5wffMEtaQ18S6glZZHkM/mUhyABfiKdm/tkCny+iEPJp2az8npA
4hUIp2OAGO+YsxldGJY+rMj7K59fvGoMejlu0cNrA95e02/TfFM7cqSi4OV2D69P
jae2vDIWxrWjAWL14mnyfeo3e2G/eZXopP2FaUO8IBLTgXD8yMUcdKKAB8iU2uhu
e30lwDCCKx2SaS6xKO5o6X5RfGYSFC/FW9LN1nV8q/qSbR3uH8DGoSRpJCh/JPIX
L0zSoQTV4DxhHGJ8BdmQB4FR5r57P+aVQGhZZi19xHcWdn0SQN+zLdMVI6EdQ4UQ
MeG2MMGF0sl4itLUX7Cq1zVtZgC2uWIzEPuSEHWuBYHNNWFYyc0XGu+WjeQZfFSL
3

Bug#811443: [debian-mysql] Bug#811443: mysql-5.6: Multiple security fixes from the January 2016 CPU

[Norvald H. Ryeng]

The Critical Patch Update is out:  
http://www.oracle.com/technetwork/topics/security/cpujan2016-2367955.html


The following vulnerabilities are fixed by upgrading from MySQL 5.6.27 to  
5.6.28:


CVE-2016-0505
CVE-2016-0546
CVE-2016-0597
CVE-2016-0598
CVE-2016-0600
CVE-2016-0606
CVE-2016-0608
CVE-2016-0609
CVE-2016-0596
CVE-2016-0503
CVE-2016-0504
CVE-2016-0607
CVE-2016-0611
CVE-2016-0595
CVE-2016-0610

Regards,

Norvald H. Ryeng

Bug#790273: Bug#811144: FTBFS: error: expected identifier or '(' before '__extension__'

[Robert Luberda]

Andreas Beckmann pisze:
Hi,
> 
>> I've just prepared NMU for publib-dev (see that attached patch), and
>> uploaded  it to DELAYED/3.
> 
> publib is orphaned, so you could do a proper QA upload instead.
> 
OK, I will prepare QA upload soon.

Thanks,
robert

Bug#811560: elasticache: FTBFS with nonexistant $HOME

[Andreas Beckmann]

Source: elasticache
Version: 1.6.00-1
Severity: serious
Justification: fails to build from source

Current pbuilder changed the build environment to use a nonexistant
$HOME directory. Neither the build process nor the build tools should
have to access $HOME during the build. Also the (non-)existence of
something in $HOME must not influence the build process.

elasticache FTBFS in such a setup since it tries to 'cd' (with no args)
to the $HOME:

[...]
I: Running cd /build/*/ && env PATH="/usr/sbin:/usr/bin:/sbin:/bin" 
HOME="/nonexistent" dpkg-buildpackage -us -uc -rfakeroot
dpkg-buildpackage: source package elasticache
dpkg-buildpackage: source version 1.6.00-1
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage: source changed by Ben Howard 
 dpkg-source --before-build elasticache-1.6.00
dpkg-buildpackage: host architecture amd64
 fakeroot debian/rules clean
dh clean --with_python2
   dh_testdir -O--with_python2
   dh_auto_clean -O--with_python2
make -j1 clean
make[1]: Entering directory '/build/elasticache-1.6.00'
Makefile:77: warning: overriding recipe for target 'build'
Makefile:42: warning: ignoring old recipe for target 'build'
cd 
/bin/sh: 1: cd: can't cd to /nonexistent
Makefile:80: recipe for target 'clean' failed
make[1]: *** [clean] Error 2
make[1]: Leaving directory '/build/elasticache-1.6.00'
dh_auto_clean: make -j1 clean returned exit code 2
debian/rules:5: recipe for target 'clean' failed
make: *** [clean] Error 2
dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2


Andreas

Bug#811304: [Pkg-wmaker-devel] Bug#811304: wdmLogin: /usr/lib/x86_64-linux-gnu/libwraster.so.5: version `LIBWRASTER3' not found

[Doug Torrance]

On 01/19/2016 02:41 PM, Andreas Metzler wrote:

We can choose one of these hacks:
1 Find a way to ship unpatched libwraster 0.95.7 in Debian.

2a Patch the source to fix back the symbol versioning to
LIBWRASTER3

2b Patch the source to use a different soname. (If the ABI breaks in
an incompatible way, requiring rebuilds library maintance 101 says: bump
the soname.)

1 cannot be done /properly/. libwraster-0.95.6 and libwraster-0.95.7
have the same soname and are therefore not co-installable but would
need to conflict. So we cannot do the usual seamless partial upgrades,
it won't be possible to upgrade wmaker (built against
libwraster-0.95.7) while keeping wmweather+ 2.15-1.1 (built against
libwraster-0.95.6) functional.

Both 2a and 2b have the downside that Debian's libwraster/0.95.7 will
be binary incompatible with unpatched libwraster/0.95.7 (as possible
shipped by e.g. Fedora)

2a has the benefit of avoiding an actually useless library transition.
There is little to speak for 2b, except perhaps the fact that it shows
that our ABI differs from upstream.

So, having to choose I would strongly vote for 2a, adding attached
patch to debian/patches/ and updating the symbol file (again).

I have not got more time to spend on this today, but if you agree that
this is best course of action I can make an upload along these lines.
Ideally upstream would fix this instead of us.


Thank you for the clarification, Andreas!  I completely neglected to 
think about the fact that libwraster5 and my proposed libwraster5v2 
would both be trying to install the same file.


Option 2a sounds good to me.  Feel free to revert my last few commits if 
you get to it before I do.


Just to clarify, would the best course of action for upstream to be to 
go ahead and bump the soname for libwraster to 6 for the next release? 
If so, I can prepare a patch.


Doug

Bug#811443: mysql-5.6: Multiple security fixes from the January 2016 CPU

[Salvatore Bonaccorso]

Hi Robie,

On Tue, Jan 19, 2016 at 12:15:53PM +, Robie Basak wrote:
> Question for the security team.
> 
> On Mon, Jan 18, 2016 at 09:16:06PM +0100, Norvald H. Ryeng wrote:
> > Source: mysql-5.6
> > Version: 5.6.27-2
> > Severity: grave
> > Tags: security upstream fixed-upstream
> 
> 5.6.27-2 only exists in testing, and I uploaded 5.6.28-1 to unstable
> recently. It hasn't landed in testing yet, but when it does this bug
> will be fixed.
> 
> Is there anything we should do to accelerate this, given that it will be
> a security fix?

How fast (unless some RC bug is introduced) a package migrates from
unstable to testing is controlled by the urgency set. In this case it
will now happen in three days, which is fine.

See 
https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#testing-unstable

Regards,
Salvatore

Bug#808216: [PATCH] Tolerate unknown lines in *.diff/Index

[Benoit Mortier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sat, 19 Dec 2015 13:51:48 + Colin Watson  wrote:
> We should gain SHA256 support as well, but in the meantime this at least
> avoids an infinite loop if the Index file has a line we don't recognise.
> 
> Closes: #808216
> ---
>  debmirror | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/debmirror b/debmirror
> index 0c2543c..516b36d 100755
> --- a/debmirror
> +++ b/debmirror
> @@ -2463,6 +2463,9 @@ sub fetch_and_apply_diffs {
>   $diff_size{$file} = $size;
>}
>  }
> +else {
> +  $_ = ;
> +}
>}
>close(INDEX);
>  

hello,

as one of the maintener affected by this bug with the removal of all the
argonaut packages, what can we do to help you fix it ?

Cheers

- -- 
Benoit Mortier
CEO
OpenSides "logiciels libres pour entreprises" : http://www.opensides.eu/
Promouvoir et défendre le Logiciel Libre http://www.april.org/
Main developper in FusionDirectory : http://www.fusiondirectory.org/
Official French representative for OPSI : http://opsi.org/
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWnpRmAAoJEO8v8eSGOOrRihcQAM7aM2Om3+UyUimMpqLJXroG
lVSLODcXql2aOAClNfbp7wHQEGtYr5w+/jAB8+J9A9Fq+ZjJibe94tGiYjxE3fjK
Goags5y/6zydUS6nWihlt70Be9yVTCIqBZsmie3HG2bPvXFgWuE+lRy/vie9biWv
ij5SQrBsckLLeow6yLzifPNHdpBkSFcYHvD+eUwk0lho8QMawXVPwlqAo6YGEL9y
lNYagbYcn9rGW5fvK/sc25Uft9ox7b1BYBu4v6CtozZkiG0BhM/1CAYoLzwDJy2k
8iLgbYfWByjFnXfcMob8FKgGCI2F1OgZmz0N6Mbq0m1tdWIj8nDCGK3qzwGIM6ZT
swgXChD1QpJE1C6uNiRKLc28kGzvoRY0gmkZL1cNFBFmuy9YHYfizgEC4s/PP7rO
g6qdlyfuh6JYWC5A/PtbUVH90irkQaL9GARnVVAcrSpk0r9vKfNWLwFmvbv+Eycd
nBgvTiNoq0Syhc68ekFS3t/xnZ0nskTxFxxMlzXyvbFtzTliOdBBREJ6L5g8pyPR
tbtP19bCb9zlIj+7FdEw7suFC3yr4QyBi+CONGj7jEbhvM333e7ng4xb8I9AZELW
mD8+nkxOjU3g0h8+HhkWx5rFW/yxxxcGwgny2t049d8KFd+ARLxcZb/E1JFBHKH8
Qf+rxhttxctRmbAcP9tg
=wazL
-END PGP SIGNATURE-

Processed: its a bug in ruby-celluloid

[Debian Bug Tracking System]

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

> reassign 811217 ruby-celluloid
Bug #811217 [diaspora] diaspora: Configure error, Could not find gem 'timers 
(~> 4.0.0) ruby'
Bug reassigned from package 'diaspora' to 'ruby-celluloid'.
No longer marked as found in versions diaspora/0.5.5.1+debian-2.
Ignoring request to alter fixed versions of bug #811217 to the same values 
previously set
> affects 811217 diaspora
Bug #811217 [ruby-celluloid] diaspora: Configure error, Could not find gem 
'timers (~> 4.0.0) ruby'
Added indication that 811217 affects diaspora
> thanks
Stopping processing here.

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

Bug#811304: wdmLogin: /usr/lib/x86_64-linux-gnu/libwraster.so.5: version `LIBWRASTER3' not found

[Andreas Metzler]

On 2016-01-18 Doug Torrance  wrote:
> Control: tags -1 pending

> On 01/18/2016 02:55 PM, Doug Torrance wrote:
> > I think the solution is to rename libwraster5 to something like
> > libwraster5v2 and trigger an auto transition.

> I've pushed these changes to git.  Note that the new library already
> means we'll have to wait for the NEW queue, so I've kept the new
> wmaker-utils package for #78119 in.

> Andreas or kix, would either of you be able to take a look and upload?
[...]

Hello Doug,

it is not that simple. :-(

We can choose one of these hacks:
1 Find a way to ship unpatched libwraster 0.95.7 in Debian.

2a Patch the source to fix back the symbol versioning to
LIBWRASTER3

2b Patch the source to use a different soname. (If the ABI breaks in
an incompatible way, requiring rebuilds library maintance 101 says: bump
the soname.)

1 cannot be done /properly/. libwraster-0.95.6 and libwraster-0.95.7
have the same soname and are therefore not co-installable but would
need to conflict. So we cannot do the usual seamless partial upgrades,
it won't be possible to upgrade wmaker (built against
libwraster-0.95.7) while keeping wmweather+ 2.15-1.1 (built against
libwraster-0.95.6) functional.

Both 2a and 2b have the downside that Debian's libwraster/0.95.7 will
be binary incompatible with unpatched libwraster/0.95.7 (as possible
shipped by e.g. Fedora)

2a has the benefit of avoiding an actually useless library transition.
There is little to speak for 2b, except perhaps the fact that it shows
that our ABI differs from upstream.

So, having to choose I would strongly vote for 2a, adding attached
patch to debian/patches/ and updating the symbol file (again).

I have not got more time to spend on this today, but if you agree that
this is best course of action I can make an upload along these lines.
Ideally upstream would fix this instead of us.

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
Description: Patch back libwraster symbol version to LIBWRASTER3.
Author: Andreas Metzler 
Bug-Debian: https://bugs.debian.org/811304
Origin: vendor

--- a/configure.ac
+++ b/configure.ac
@@ -76,6 +76,11 @@ WRASTER_REVISION=0
 WRASTER_AGE=0
 WRASTER_VERSION=$WRASTER_CURRENT:$WRASTER_REVISION:$WRASTER_AGE
 AC_SUBST(WRASTER_VERSION)
+dnl After next soname bump drop this and use WRASTER_VERSION as argument
+dnl for generate-mapfile-from-header.sh
+dnl http://bugs.debian.org/811304
+WRASTER_SYMBOL_VERSION=3
+AC_SUBST([WRASTER_SYMBOL_VERSION])
 dnl
 dnl libWINGs
 WINGS_CURRENT=4
--- a/wrlib/Makefile.am
+++ b/wrlib/Makefile.am
@@ -99,5 +99,5 @@ wrlib.pc: Makefile
 if HAVE_LD_VERSION_SCRIPT
 libwraster.map: $(include_HEADERS) $(top_srcdir)/script/generate-mapfile-from-header.sh
 	$(AM_V_GEN)$(top_srcdir)/script/generate-mapfile-from-header.sh \
-		-n LIBWRASTER -v $(WRASTER_VERSION) $(srcdir)/$(include_HEADERS) > libwraster.map
+		-n LIBWRASTER -v $(WRASTER_SYMBOL_VERSION) $(srcdir)/$(include_HEADERS) > libwraster.map
 endif

Bug#811479: boot fails in "run-init -n ..."

[Roderich Schupp]

On Tue, Jan 19, 2016 at 7:50 PM, Ben Hutchings  wrote:

> I think I understand the problem.  Could you try the packages (version
> 0.122~a.test) from https://people.debian.org/~benh/packages/ ?
>

Yes, that works (using the unpatched klibc-utils 2.0.4-7, not my hacked
version). Thanks!

Cheers, Roderich

Processed: found 811428 in 5.5.23-2

[Debian Bug Tracking System]

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

> found 811428 5.5.23-2
Bug #811428 [src:mysql-5.5] mysql-5.5: Multiple security fixes from the January 
2016 CPU
Marked as found in versions mysql-5.5/5.5.23-2.
> thanks
Stopping processing here.

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

Bug#811469: isomd5sum: FTBFS: cc: error: libcheckisomd5.a: No such file or directory

[Ryan Finnie]

tags 811469 + moreinfo unreproducible
thanks

On 01/19/2016 01:00 AM, Chris Lamb wrote:
> Source: isomd5sum
> Version: 1:1.1.0-1
> Severity: serious
> Justification: fails to build from source
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
> 
> Dear Maintainer,
> 
> isomd5sum fails to build from source in unstable/amd64:
> 
>   [..]
> 
>   for python in python2.7 python3.4 python3.5; do \
>   mkdir -p build/$python; \
>   /usr/bin/make -C build/$python -f ../../Makefile 
> VPATH=/home/lamby/temp/cdt.20160119095649.Xd1jzyucCA/isomd5sum-1.1.0 \
>   PYTHON=$python pyisomd5sum.so; \
>   done
>   make[2]: Entering directory 
> '/home/lamby/temp/cdt.20160119095649.Xd1jzyucCA/isomd5sum-1.1.0/build/python2.7'
>   cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -Werror -D_GNU_SOURCE=1 -D_FILE_OFFSET_BITS=64 
> -D_LARGEFILE_SOURCE=1 -D_LARGEFILE64_SOURCE=1 -fPIC -I/usr/include/python2.7 
> -I/usr/include/x86_64-linux-gnu/python2.7 -c -O -o pyisomd5sum.o 
> /home/lamby/temp/cdt.20160119095649.Xd1jzyucCA/isomd5sum-1.1.0/pyisomd5sum.c
>   cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -Werror -D_GNU_SOURCE=1 -D_FILE_OFFSET_BITS=64 
> -D_LARGEFILE_SOURCE=1 -D_LARGEFILE64_SOURCE=1 -fPIC -I/usr/include/python2.7 
> -I/usr/include/x86_64-linux-gnu/python2.7 -shared -g -fpic pyisomd5sum.o 
> libcheckisomd5.a libimplantisomd5.a -Wl,-z,relro -fPIC -o pyisomd5sum.so
>   cc: error: libcheckisomd5.a: No such file or directory
>   cc: error: libimplantisomd5.a: No such file or directory
>   ../../Makefile:37: recipe for target 'pyisomd5sum.so' failed
>   make[2]: *** [pyisomd5sum.so] Error 1
>   make[2]: Leaving directory 
> '/home/lamby/temp/cdt.20160119095649.Xd1jzyucCA/isomd5sum-1.1.0/build/python2.7'
>   debian/rules:16: recipe for target 'override_dh_auto_build' failed
>   make[1]: *** [override_dh_auto_build] Error 2
>   make[1]: Leaving directory 
> '/home/lamby/temp/cdt.20160119095649.Xd1jzyucCA/isomd5sum-1.1.0'
>   debian/rules:13: recipe for target 'build' failed
>   make: *** [build] Error 2

Sorry, I cannot reproduce.  On an up to date sid amd64 chroot, it builds (and 
rebuilds) successfully, though with some warnings:

[...]

for python in python2.7 python3.4 python3.5; do \
mkdir -p build/$python; \
/usr/bin/make -C build/$python -f ../../Makefile 
VPATH=/home/ryan/tmp/811469/isomd5sum-1.1.0 \
PYTHON=$python pyisomd5sum.so; \
done
make[2]: Entering directory 
'/home/ryan/tmp/811469/isomd5sum-1.1.0/build/python2.7'
cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Werror -D_GNU_SOURCE=1 -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE=1 -D_LARGEFILE64_SOURCE=1 -fPIC -I/usr/include/python2.7 
-I/usr/include/x86_64-linux-gnu/python2.7 -c -O -o pyisomd5sum.o 
/home/ryan/tmp/811469/isomd5sum-1.1.0/pyisomd5sum.c
make[2]: Warning: Archive 'libcheckisomd5.a' seems to have been created in 
deterministic mode. 'libcheckisomd5.o' will always be updated. Please consider 
passing the U flag to ar to avoid the problem.
cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Werror -D_GNU_SOURCE=1 -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE=1 -D_LARGEFILE64_SOURCE=1 -fPIC -I/usr/include/python2.7 
-I/usr/include/x86_64-linux-gnu/python2.7 -c -O -o libcheckisomd5.o 
/home/ryan/tmp/811469/isomd5sum-1.1.0/libcheckisomd5.c
ar rv libcheckisomd5.a libcheckisomd5.o
ar: creating libcheckisomd5.a
a - libcheckisomd5.o
make[2]: Warning: Archive 'libcheckisomd5.a' seems to have been created in 
deterministic mode. 'libcheckisomd5.o' will always be updated. Please consider 
passing the U flag to ar to avoid the problem.

Full build log attached.


20160119-isomd5sum.log.gz
Description: application/gzip


signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#811469: isomd5sum: FTBFS: cc: error: libcheckisomd5.a: No such file or directory

[Debian Bug Tracking System]

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

> tags 811469 + moreinfo unreproducible
Bug #811469 [src:isomd5sum] isomd5sum: FTBFS: cc: error: libcheckisomd5.a: No 
such file or directory
Added tag(s) unreproducible and moreinfo.
> thanks
Stopping processing here.

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

Bug#811498: libconsole-bridge0.2v5: ABI bump without package rename

[Julien Cristau]

On Tue, Jan 19, 2016 at 18:52:27 +, Jose Luis Rivero wrote:

> Package: libconsole-bridge0.2v5
> Followup-For: Bug #811498
> 
> Hey Jochen:
> 
> Thanks for the report. You are right, I broke the new update. My
> intention was not to change package and library name since upstream
> did not change the API/ABI (I'm working with them to keep a sane
> semantic versioning scheme). I did that for the package but not for
> the library, sorry for that.
> 
> I believe that we can workaround on this problem by creating a symlink
> from libconsole_bridge.so.0.3 to a new libconsole_bridge.so.0.2. This
> way we can respect the upstream release as-it but keep the dependencies
> stable in debian which depends on the 0.2 lib.
> 
> Jochen, do you see any problem with this? or do you have a better idea
> to solve the situation keeping in mind that there is no ABI/API change
> in the new 0.3.0 version?

If the ABI is compatible, that seems fine.  Note that if the library's
SONAME changed, you would need to bump shlibs to the new version since
any rebuilt reverse dependency is going to reference the new SONAME.

Cheers,
Julien

Bug#811498: libconsole-bridge0.2v5: ABI bump without package rename

[Jose Luis Rivero]

Package: libconsole-bridge0.2v5
Followup-For: Bug #811498

Hey Jochen:

Thanks for the report. You are right, I broke the new update. My
intention was not to change package and library name since upstream
did not change the API/ABI (I'm working with them to keep a sane
semantic versioning scheme). I did that for the package but not for
the library, sorry for that.

I believe that we can workaround on this problem by creating a symlink
from libconsole_bridge.so.0.3 to a new libconsole_bridge.so.0.2. This
way we can respect the upstream release as-it but keep the dependencies
stable in debian which depends on the 0.2 lib.

Jochen, do you see any problem with this? or do you have a better idea
to solve the situation keeping in mind that there is no ABI/API change
in the new 0.3.0 version?

Thanks.

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

Kernel: Linux 3.13.0-74-generic (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libconsole-bridge0.2v5 depends on:
ii  libc6   2.19-22
ii  libgcc1 1:5.2.1-22
ii  libstdc++6  5.2.1-22

libconsole-bridge0.2v5 recommends no packages.

libconsole-bridge0.2v5 suggests no packages.

-- no debconf information

Bug#811479: boot fails in "run-init -n ..."

[Ben Hutchings]

Control: tag -1 patch

On Tue, 2016-01-19 at 15:28 +, Ben Hutchings wrote:
> Control: tag -1 moreinfo
> 
> On Tue, 19 Jan 2016 11:44:39 +0100 Roderich Schupp  wrote:
> > Package: initramfs-tools-core
> > Version: 0.121
> > Severity: critical
> >  
> > boot with an initrd generated by initramfs-tools-core 1.21
> > fails with "run-init: opening console: No such file or directory"
> > (see attached screenshot)
> >  
> > It seems to be caused by validate_init() in /usr/share/initramfs-tools/init
> > which has been reduced to just "run-init -n ..." using the new option -n to
> > klibc's run-init. The latter bombs out in
> >  
> > if ((confd = open(console, O_RDWR)) < 0)
> >    return "opening console";
> >  
> > Dunny why, as sticking "ls -l /dev/console" into /usr/share/initramfs-
> > tools/init
> > right before "run-init -n ..." shows that /dev/console exists...
> [...]
> 
> That's showing you the /dev/console in the initramfs.  However, run-
> init will open it from the 'real' root filesystem.
> 
> At the recovery shell prompt, what does "ls -l /root/dev/console" show?

I think I understand the problem.  Could you try the packages (version
0.122~a.test) from https://people.debian.org/~benh/packages/ ?

The patch is below.

Ben.

---
Subject: [PATCH initramfs-tools] init: Validate the real init after devtmpfs
 is mounted under the real root

Currently 'run-init -n' will fail if there's no static /dev/console on
the real root.  We have to run it after udev's init-bottom script has
moved /dev to ${rootmnt}/dev.

Closes: #811479
Signed-off-by: Ben Hutchings 
---
 init | 27 ++-
 1 file changed, 14 insertions(+), 13 deletions(-)

diff --git a/init b/init
index c10546f..f53760c 100755
--- a/init
+++ b/init
@@ -236,6 +236,20 @@ if read_fstab_entry /usr; then
log_end_msg
 fi
 
+# Mount cleanup
+mount_bottom
+nfs_bottom
+local_bottom
+
+maybe_break bottom
+[ "$quiet" != "y" ] && log_begin_msg "Running /scripts/init-bottom"
+# We expect udev's init-bottom script to move /dev to ${rootmnt}/dev
+run_scripts /scripts/init-bottom
+[ "$quiet" != "y" ] && log_end_msg
+
+# Move /run to the root
+mount -n -o move /run ${rootmnt}/run
+
 validate_init() {
run-init -n "${rootmnt}" "${1}"
 }
@@ -252,19 +266,6 @@ if ! validate_init "$init"; then
done
 fi
 
-# Mount cleanup
-mount_bottom
-nfs_bottom
-local_bottom
-
-maybe_break bottom
-[ "$quiet" != "y" ] && log_begin_msg "Running /scripts/init-bottom"
-run_scripts /scripts/init-bottom
-[ "$quiet" != "y" ] && log_end_msg
-
-# Move /run to the root
-mount -n -o move /run ${rootmnt}/run
-
 # No init on rootmount
 if ! validate_init "${init}" ; then
panic "No init found. Try passing init= bootarg."

-- 
Ben Hutchings
Horngren's Observation:
   Among economists, the real world is often a special case.


signature.asc
Description: Digital signature

Processed: Re: boot fails in "run-init -n ..."

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch
Bug #811479 [initramfs-tools-core] boot fails in "run-init -n ..."
Added tag(s) patch.

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

Bug#804536: gcc-5: [mips,mipsel] regression in optimization causes FTBFS for gsoap

[Emilio Pozuelo Monfort]

On Wed, 16 Dec 2015 16:57:52 +0100 Mattias Ellert 
wrote:
> tis 2015-11-10 klockan 15:50 +0100 skrev Aurelien Jarno:
> >Â 
> > Bug submitted upstream as PR68273.
> 
> Hi!
> 
> How should I handle this? Will there be a solution to the gcc bug
> within a not too distant future, or is this likely to remain broken for
> many months? Not an easy question to answer I imagine.
> 
> If it is likely to remain broken for a long time, should I work around
> it and upload an update that adds -fno-ipa-sra to the compiler flags
> used to compile the package? Or should it be left as it is?

A workaround would be appreciated so we can finish the libssl transition.

Thanks,
Emilio

Bug#811471: marked as done (zopfli: contains sample code from the RFC without any attribution)

[Debian Bug Tracking System]

Your message dated Tue, 19 Jan 2016 17:50:45 +
with message-id 
and subject line Bug#811471: fixed in zopfli 1.0.1+git160119-1
has caused the Debian Bug report #811471,
regarding zopfli: contains sample code from the RFC without any attribution
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.)


-- 
811471: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811471
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zopfli
Severity: serious
Tags: upstream
Control: forwarded -1 https://github.com/google/zopfli/issues/88

The CRC code used in gzip_container.c comes almost directly from the RFC 1952, 
except for the naming conventions and some additional consting. 
Even the comments are copied.

The RFC 1952 has the following license:

"Permission is granted to copy and distribute this document for any
purpose and without charge, including translations into other
languages and incorporation into compilations, provided that the
copyright notice and this notice are preserved, and that any
substantive changes or deletions from the original are clearly
marked."

and copyright
Copyright (c) 1996 L. Peter Deutsch

There does not appear to be any exception for code anywhere, as such the
code must likely be considered non-free and incompatible with the Apache
license.

In any case, the file also does not consist of code solely owned by
Google, AFAICT.

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

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

-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.

When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to (`inline'). Thank you.
--- End Message ---
--- Begin Message ---
Source: zopfli
Source-Version: 1.0.1+git160119-1

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated zopfli 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, 19 Jan 2016 18:31:26 +0100
Source: zopfli
Binary: zopfli libzopfli1 libzopfli-dev
Architecture: source amd64
Version: 1.0.1+git160119-1
Distribution: unstable
Urgency: low
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 libzopfli-dev - Header and static library files for libzopfli1
 libzopfli1 - HTTP and WebDAV client library
 zopfli - zlib (gzip, deflate) compatible compressor
Closes: 811471
Changes:
 zopfli (1.0.1+git160119-1) unstable; urgency=low
 .
   * Use git snapshot for open source and threading compatible CRC
 implementation in gzip_container.c (closes: #811471).
Checksums-Sha1:
 562774cd7a4b222d7a14fccc597eeed675e49d60 1886 zopfli_1.0.1+git160119-1.dsc
 b230acfaf4262877c1df50b69a3e1a9bc7e8e0e0 105940 
zopfli_1.0.1+git160119.orig.tar.xz
 c58f68990b16846068fda4e0f57dda6f98f4f8cd 3472 
zopfli_1.0.1+git160119-1.debian.tar.xz
 1d5832adf82ffd4554282e9bac3b63aa20fc8ac8 34918 
libzopfli-dev_1.0.1+git160119-1_amd64.deb
 354ff1c4ec835bbacbec94b76a8ea2823895ca7f 3472 
libzopfli1-dbgsym_1.0.1+git160119-1_amd64.deb
 66c15649cf2c60540804acaf907b6cb17104c059 26020 
libzopfli1_1.0.1+git160119-1_amd64.deb
 8c18529c4809e7e8a162b0f6f4302e4a729d77ac 3724 
zopfli-dbgsym_1.0.1+git160119-1_amd64.deb
 b05dce48ba9e1ec8c95b8613489ab14b2aad819f 25744 
zopfli_1.0.1+git160119-1_amd64.deb
Checksums-Sha256:
 318f3fb2c0b8fe8de6f90c3a7d8f2e2cb3f737d75c6148637fc05184ad0fc308 1886 
zopfli_1.0.1+git160119-1.dsc
 39a8b35ff8814e5755ba0459d884943c864ae2c7161d52e8ca1c94c4c7fa1009 105940 
zopfli_1.0.1+git160119.orig.tar.xz
 c13fc4b783299e8a2aa98fd6e05bebd38cabb92df1945fb77b713a7073c9df70 3472 
zopfli_1.0.1+git1

Bug#810872: marked as done (sigil: make it work with python 3.5)

[Debian Bug Tracking System]

Your message dated Tue, 19 Jan 2016 17:50:26 +
with message-id 
and subject line Bug#810872: fixed in sigil 0.9.2+dfsg+dfsg-2
has caused the Debian Bug report #810872,
regarding sigil: make it work with python 3.5
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.)


-- 
810872: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810872
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sigil
Version: 0.9.2+dfsg+dfsg-1
Severity: serious
Tags: patch
Justification: Policy 3.5

sigil should have depends on a python3 interpreter.  The attached patch will
do this and also make the package binNMUable to support a change in the
default python3 version.  Despite the python2.7 recommends you have now, this
application does appear to be built for python3.

Please let me know if you're OK with an NMU or if you'd like to take care of
it.  It would be nice to get this resolved quickly to support the current
python3.5 transition.
diff -Nru sigil-0.9.2+dfsg+dfsg/debian/changelog sigil-0.9.2+dfsg+dfsg/debian/changelog
--- sigil-0.9.2+dfsg+dfsg/debian/changelog	2015-12-19 04:16:19.0 -0500
+++ sigil-0.9.2+dfsg+dfsg/debian/changelog	2016-01-12 23:26:38.0 -0500
@@ -1,3 +1,10 @@
+sigil (0.9.2+dfsg+dfsg-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Use dh_python3 to generate missing python3 interpreter depends
+
+ -- Scott Kitterman   Tue, 12 Jan 2016 23:25:51 -0500
+
 sigil (0.9.2+dfsg+dfsg-1) unstable; urgency=medium
 
   * [19a5e34] debian/{control,copyright}: use my @debian.org email address
diff -Nru sigil-0.9.2+dfsg+dfsg/debian/control sigil-0.9.2+dfsg+dfsg/debian/control
--- sigil-0.9.2+dfsg+dfsg/debian/control	2015-12-05 12:49:58.0 -0500
+++ sigil-0.9.2+dfsg+dfsg/debian/control	2016-01-12 23:25:31.0 -0500
@@ -14,7 +14,7 @@
libqt5webkit5-dev (>= 5.4.0),
libqt5xmlpatterns5-dev (>= 5.4.0),
pkg-config,
-   python3.4-dev,
+   python3-dev,
qtbase5-dev (>= 5.4.0),
qttools5-dev (>= 5.4.0),
qttools5-dev-tools (>= 5.4.0),
@@ -30,10 +30,9 @@
  libjs-jquery-scrollto,
  python3-lxml,
  sigil-data (= ${source:Version}),
+ ${python3:Depends},
  ${misc:Depends},
  ${shlibs:Depends}
-Recommends: python2.7,
-python3.4
 Description: multi-platform ebook editor
  Sigil is a free, open source, multi-platform ebook editor.
  It is designed to edit books in ePub format.
diff -Nru sigil-0.9.2+dfsg+dfsg/debian/rules sigil-0.9.2+dfsg+dfsg/debian/rules
--- sigil-0.9.2+dfsg+dfsg/debian/rules	2015-11-29 13:17:08.0 -0500
+++ sigil-0.9.2+dfsg+dfsg/debian/rules	2016-01-12 23:25:43.0 -0500
@@ -5,7 +5,7 @@
 export DEB_LDFLAGS_MAINT_APPEND := -Wl,--as-needed
 
 %:
-	dh $@ --parallel
+	dh $@ --with python3 --parallel
 
 override_dh_auto_configure:
 	ln -sf /usr/share/javascript/jquery/jquery.min.js $(CURDIR)/src/Resource_Files/javascript/jquery-1.6.2.min.js
--- End Message ---
--- Begin Message ---
Source: sigil
Source-Version: 0.9.2+dfsg+dfsg-2

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated sigil 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, 19 Jan 2016 13:45:43 +
Source: sigil
Binary: sigil sigil-data
Architecture: source
Version: 0.9.2+dfsg+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Mattia Rizzolo 
Changed-By: Mattia Rizzolo 
Description:
 sigil  - multi-platform ebook editor
 sigil-data - multi-platform ebook editor - data files
Closes: 810872
Changes:
 sigil (0.9.2+dfsg+dfsg-2) unstable; urgency=medium
 .
   * [2c7b008] debian/clean: files moved, so update the list of files to remove.
   * [adca4b7] Use dh_python3 to compute python dependencies, etc.
   * debian/control:
 + [9bd47bb] Recommends some python3 modules used by the test plugin.
 + [b4ef59b] Build using the default python versio

Processed: Re: Bug#811519: vlc: avio plugin leaks file content

[Debian Bug Tracking System]

Processing control commands:

> tags -1 = moreinfo
Bug #811519 [src:ffmpeg] ffmpeg: needs to build with --disable-protocol=concat 
to really fix CVE-2016-1897
Added tag(s) moreinfo; removed tag(s) patch and security.
> severity -1 important
Bug #811519 [src:ffmpeg] ffmpeg: needs to build with --disable-protocol=concat 
to really fix CVE-2016-1897
Severity set to 'important' from 'grave'

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

Bug#811519: vlc: avio plugin leaks file content

[Andreas Cadhalpun]

Control: tags -1 = moreinfo
Control: severity -1 important

Hi,

On 19.01.2016 17:27, Sebastian Ramacher wrote:
> On 2016-01-19 18:11:01, Rémi Denis-Courmont wrote:
>> With a carefully crafted URL, the VLC avio plugin can be made to leak
>> content of local files to remote parties.
>> The root cause is the same as CVE-2016-1897.
>>
>> See also:
>>
>> https://mailman.videolan.org/pipermail/vlc-devel/2016-January/105718.html
> 
> There is nothing to be done in the vlc package. Reassigning to ffmpeg. It 
> needs
> to be built with --disable-protocol=concat.

How is CVE-2016-1897 not fully fixed?

Rémi, please share details about any remaining vulnerability with
.

Best regards,
Andreas

Bug#811500: cpl-plugin-visir: does not work

[Julian Taylor]

On 01/19/2016 04:50 PM, Ole Streicher wrote:

Hi Julian,

thank you for the bug report. To check the packaging, I run the unit
tests that come with the package (hoping that they cover a good part of
the code), and I think this is a reasonable "minimal effort" to ensure a
package is working.


no running the unittests is not minimal effort for Debian, at least not 
without knowing that the unittests represent a sufficient test coverage 
to guarantee some usability.
For pretty much all pipelines this is not the case. If a pipeline works 
is done via esorex and test datasets. Those are not part of the source 
tarballs, though the demo datasets sometimes contain a subset of the 
test data.
This may not be ideal for third party redistribution, but this is also 
not something upstream needs to necessarily care about.


If you want to package something it is your job to make sure it actually 
works and not only that it builds. And if you don't know the package 
well enough to ensure that, then don't package it. Debian is better of 
without some software than with software that doesn't work.


Fwiw. the easiest way to test at least a subset of the shipped recipes 
is to run the demo datasets via the upstream provided Reflex package, 
ideally you just have to load the workflows and press play.
You can collect the raw esorex calls and sofs from its temporary folders 
printed in the workflow.




Could I ask you to provide a minimal test case that could be used? "Any"
is a bit vague... Can you make a small test case, maybe using your demo
data set

ftp://ftp.eso.org/pub/dfs/pipelines/visir/visir-demo-reflex-0.1.tar.gz

which I could use? Just the parameters, the SOF, and the expected output
would be probably enough


cat data.sof

demoroot/img/aqu/VISIR.2015-07-21T07:09:09.829.fits BURST
demoroot/img/aqu/VISIR.2015-07-21T07:09:56.706.fits BURST
demoroot/img/aqu/VISIR.2015-07-21T07:10:33.128.fits BURST
demoroot/img/aqu/VISIR.2015-07-21T07:11:17.722.fits BURST
demoroot/img/aqu/VISIR.2015-07-21T08:13:14.577.fits BURST
demoroot/img/aqu/VISIR.2015-07-21T08:14:48.712.fits BURST
demoroot/img/aqu/VISIR.2015-07-21T08:16:14.751.fits BURST
demoroot/img/aqu/VISIR.2015-07-21T08:17:48.743.fits BURST

esorex visir_img_reduce --delete-temp=false data.sof

It will fail on all three points. When adding the config and adapting 
the swarp executable name it will fail with a division by zero due to 
the weight maps from swarp being wrongly just zeros (in the tmp folder 
tmp_coadd_wgt_*.fits)
The recipe should work with swarp 2.19 but that version has other issues 
which will cause failures with other data.


The patches to swarp in visir do not fix that, they just work around it 
by reverting some stuff, so they are not much use to the package as is. 
I contacted upstream about the issues when they were discovered (quite a 
long time ago) though never received an answer, though I should retry 
contacting if time allows for it.

Bug#810990: libxmlrpcpp-dev: /usr/include/base64.h already shipped by heimdal-dev

[Jelmer Vernooij]

On Tue, Jan 19, 2016 at 09:38:35AM +0100, Jochen Sprickerhof wrote:
> Hi,
> 
> I've pushed changes to libxmlrpcpp-dev to move the base64.h to
> /usr/include/xmlrpcpp [1]. Would it be ok if I reassign this to
> libxmlrpcpp-dev and close it, or should we split it, to leave one open
> for heimdal-dev?
> 
> * Wookey  [2016-01-16 03:26]:
> > Debian now has this xmplrpc c++ implementation: 
> > https://tracker.debian.org/pkg/xmlrpc-c
> > maybe ros-ros-comm could just use that? I've not looked to see how well the 
> > APIs match up. 
> 
> ROS upstream is currently working on ROS2, replacing most of the core
> system, so I hope this gets resolved with that.

Heimdal already ships a package (heimdal-multidev) that moves these files into
/usr/include/heimdal. 

heimdal-dev currently merely ships symlinks to these files in /usr/include
for backwards compatibility reasons. I'll see if we can remove the backwards
compatibility symlinks.

Cheers,

Jelmer

Bug#808851: artemis REMOVED from testing

[Andreas Tille]

Hi,

any news about this bug?  I wonder whether the latest htsjdk might solve
this.  If I'm not misleaded this depends from libngs-java and is thus
blocked by #809375.  Could anybody confirm that this is correct?

Kind regards

 Andreas.

On Tue, Jan 19, 2016 at 04:39:11PM +, Debian testing watch wrote:
> FYI: The status of the artemis source package
> in Debian's testing distribution has changed.
> 
>   Previous version: 16.0.0+dfsg-4
>   Current version:  (not in testing)
>   Hint: <https://release.debian.org/britney/hints/jmw>
> # 20160118; done 20160119
> Bug #808851: artemis: FTBFS: error: package ReferenceSequenceFileFactory 
> does not exist
> # blocks transition

-- 
http://fam-tille.de

Bug#810520: marked as done (ideviceinstaller: FTBFS: ideviceinstaller.c:527:44: error: comparison between 'afc_error_t {aka enum }' and 'enum ')

[Debian Bug Tracking System]

Your message dated Tue, 19 Jan 2016 16:49:04 +
with message-id 
and subject line Bug#810520: fixed in ideviceinstaller 1.0.1-0.3
has caused the Debian Bug report #810520,
regarding ideviceinstaller: FTBFS: ideviceinstaller.c:527:44: error: comparison 
between 'afc_error_t {aka enum }' and 'enum '
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.)


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

Dear Maintainer,

ideviceinstaller fails to build from source in unstable/amd64:

  [..]

  Making all in src
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160109134246.2sBBOkcruS/ideviceinstaller-1.0.1/src'
  gcc -DHAVE_CONFIG_H -I. -I..-Wall -Wextra -Wmissing-declarations 
-Wredundant-decls -Wshadow -Wpointer-arith -Wwrite-strings -Wswitch-default 
-Wno-unused-parameter -Werror -g -I/usr/include/p11-kit-1 
-I/usr/include/libxml2  -I/usr/include/libxml2 
-I/usr/lib/x86_64-linux-gnu/libzip/include -g -O2 -c -o 
ideviceinstaller-ideviceinstaller.o `test -f 'ideviceinstaller.c' || echo 
'./'`ideviceinstaller.c
  ideviceinstaller.c: In function 'main':
  ideviceinstaller.c:527:44: error: comparison between 'afc_error_t {aka enum 
}' and 'enum ' [-Werror=enum-compare]
 if (afc_client_new(phone, service, &afc) != INSTPROXY_E_SUCCESS) {
  ^
  ideviceinstaller.c:694:49: error: passing argument 4 of 'instproxy_install' 
from incompatible pointer type [-Werror=incompatible-pointer-types]
  instproxy_install(ipc, pkgname, client_opts, status_cb, NULL);
   ^
  In file included from ideviceinstaller.c:40:0:
  /usr/include/libimobiledevice/installation_proxy.h:234:19: note: expected 
'instproxy_status_cb_t {aka void (*)(void *, void *, void *)}' but argument is 
of type 'void (*)(const char *, void *, void *)'
   instproxy_error_t instproxy_install(instproxy_client_t client, const char 
*pkg_path, plist_t client_options, instproxy_status_cb_t status_cb, void 
*user_data);
 ^
  ideviceinstaller.c:701:49: error: passing argument 4 of 'instproxy_upgrade' 
from incompatible pointer type [-Werror=incompatible-pointer-types]
  instproxy_upgrade(ipc, pkgname, client_opts, status_cb, NULL);
   ^
  In file included from ideviceinstaller.c:40:0:
  /usr/include/libimobiledevice/installation_proxy.h:262:19: note: expected 
'instproxy_status_cb_t {aka void (*)(void *, void *, void *)}' but argument is 
of type 'void (*)(const char *, void *, void *)'
   instproxy_error_t instproxy_upgrade(instproxy_client_t client, const char 
*pkg_path, plist_t client_options, instproxy_status_cb_t status_cb, void 
*user_data);
 ^
  ideviceinstaller.c:712:41: error: passing argument 4 of 'instproxy_uninstall' 
from incompatible pointer type [-Werror=incompatible-pointer-types]
 instproxy_uninstall(ipc, appid, NULL, status_cb, NULL);
   ^
  In file included from ideviceinstaller.c:40:0:
  /usr/include/libimobiledevice/installation_proxy.h:283:19: note: expected 
'instproxy_status_cb_t {aka void (*)(void *, void *, void *)}' but argument is 
of type 'void (*)(const char *, void *, void *)'
   instproxy_error_t instproxy_uninstall(instproxy_client_t client, const char 
*appid, plist_t client_options, instproxy_status_cb_t status_cb, void 
*user_data);
 ^
  ideviceinstaller.c:875:45: error: comparison between 'afc_error_t {aka enum 
}' and 'enum ' [-Werror=enum-compare]
  if (afc_client_new(phone, service, &afc) != INSTPROXY_E_SUCCESS) {
   ^
  ideviceinstaller.c:882:46: error: passing argument 4 of 'instproxy_archive' 
from incompatible pointer type [-Werror=incompatible-pointer-types]
 instproxy_archive(ipc, appid, client_opts, status_cb, NULL);
^
  In file included from ideviceinstaller.c:40:0:
  /usr/include/libimobiledevice/installation_proxy.h:325:19: note: expected 
'instproxy_status_cb_t {aka void (*)(void *, void *, void *)}' but argument is 
of type 'void (*)(const char *, void *, void *)'
   instproxy_error_t instproxy_archive(instproxy_client_t client, const char 
*appid, plist_t

Bug#811519: vlc: avio plugin leaks file content

[Sebastian Ramacher]

Control: reassign -1 src:ffmpeg 7:2.8.4-1
Control: retitle -1 ffmpeg: needs to build with --disable-protocol=concat to 
really fix CVE-2016-1897

On 2016-01-19 18:11:01, Rémi Denis-Courmont wrote:
> Package: vlc
> Version: 2.2.1-5+b1
> Severity: grave
> Tags: security patch
> Justification: user security hole
> 
> Dear Maintainer,
> 
> With a carefully crafted URL, the VLC avio plugin can be made to leak
> content of local files to remote parties.
> The root cause is the same as CVE-2016-1897.
> 
> See also:
> 
> https://mailman.videolan.org/pipermail/vlc-devel/2016-January/105718.html

There is nothing to be done in the vlc package. Reassigning to ffmpeg. It needs
to be built with --disable-protocol=concat.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Processed: Re: Bug#811519: vlc: avio plugin leaks file content

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:ffmpeg 7:2.8.4-1
Bug #811519 [vlc-nox] vlc: avio plugin leaks file content
Bug reassigned from package 'vlc-nox' to 'src:ffmpeg'.
No longer marked as found in versions vlc/2.2.0~rc2-2+deb8u1.
Ignoring request to alter fixed versions of bug #811519 to the same values 
previously set
Bug #811519 [src:ffmpeg] vlc: avio plugin leaks file content
Marked as found in versions ffmpeg/7:2.8.4-1.
> retitle -1 ffmpeg: needs to build with --disable-protocol=concat to really 
> fix CVE-2016-1897
Bug #811519 [src:ffmpeg] vlc: avio plugin leaks file content
Changed Bug title to 'ffmpeg: needs to build with --disable-protocol=concat to 
really fix CVE-2016-1897' from 'vlc: avio plugin leaks file content'

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

Processed: your mail

[Debian Bug Tracking System]

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

> reassign 811519 vlc-nox
Bug #811519 [vlc] vlc: avio plugin leaks file content
Bug reassigned from package 'vlc' to 'vlc-nox'.
No longer marked as found in versions vlc/2.2.1-5.
Ignoring request to alter fixed versions of bug #811519 to the same values 
previously set
> found 811519 2.2.0~rc2-2+deb8u1
Bug #811519 [vlc-nox] vlc: avio plugin leaks file content
Marked as found in versions vlc/2.2.0~rc2-2+deb8u1.
> thanks
Stopping processing here.

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

Bug#811522: proposed RM: jenkins -- RoQA; multiple security issues, FTBFS, unmaintained in Debian

[Ansgar Burchardt]

Package: jenkins
Severity: serious

Hi,

the jenkins package in Debian has multiple open security issues[1][2]
and fails to build with Groovy 2[3].  It also is quite outdated
(Debian: 1.565.3 released upstream mid-2014; current version: 1.644
from Jan 2016 with lots of releases inbetween).

Jenkins also isn't part of a stable release (currently only in
unstable).

I suggest to remove the package from Debian.  If there are no
objections, I'll reassign the request to the ftp.debian.org pseudo-
package later.

I'm also wondering if "jenkins-memory-monitor" should also be removed
at the same time or if it is also useful without jenkins?

Ansgar

  [1] 
  [2] 
  [3] 

Bug#811519: vlc: avio plugin leaks file content

[Rémi Denis-Courmont]

Package: vlc
Version: 2.2.1-5+b1
Severity: grave
Tags: security patch
Justification: user security hole

Dear Maintainer,

With a carefully crafted URL, the VLC avio plugin can be made to leak
content of local files to remote parties.
The root cause is the same as CVE-2016-1897.

See also:

https://mailman.videolan.org/pipermail/vlc-devel/2016-January/105718.html

Best regards,

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

Kernel: Linux 4.1.15-basile (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to fi_FI.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages vlc depends on:
ii  fonts-freefont-ttf  20120503-4
ii  libaa1  1.4p5-44
ii  libavcodec-ffmpeg56 7:2.8.5-1
ii  libavutil-ffmpeg54  7:2.8.5-1
ii  libc6   2.21-6
ii  libcaca00.99.beta19-2+b1
ii  libcairo2   1.14.6-1
ii  libegl1-mesa [libegl1-x11]  11.1.1-2
ii  libfreerdp-client1.11.1.0~git20140921.1.440916e+dfsg1-5+b1
ii  libfreerdp-core1.1  1.1.0~git20140921.1.440916e+dfsg1-5+b1
ii  libfreerdp-gdi1.1   1.1.0~git20140921.1.440916e+dfsg1-5+b1
ii  libfreetype62.6.1-0.1
ii  libfribidi0 0.19.7-1
ii  libgcc1 1:5.3.1-6
ii  libgl1-mesa-glx [libgl1]11.1.1-2
ii  libgles1-mesa [libgles1]11.1.1-2
ii  libgles2-mesa [libgles2]11.1.1-2
ii  libglib2.0-02.46.2-3
ii  libpulse0   7.1-2
ii  libqt5core5a5.5.1+dfsg-12
ii  libqt5gui5  5.5.1+dfsg-12
ii  libqt5widgets5  5.5.1+dfsg-12
ii  libqt5x11extras55.5.1-3
ii  librsvg2-2  2.40.13-1
ii  libsdl-image1.2 1.2.12-5+b5
ii  libsdl1.2debian 1.2.15-12
ii  libstdc++6  5.3.1-6
ii  libva-drm1  1.6.2-1
ii  libva-x11-1 1.6.2-1
ii  libva1  1.6.2-1
ii  libvlccore8 2.2.1-5+b1
ii  libvncclient1   0.9.10+dfsg-3
ii  libx11-62:1.6.3-1
ii  libxcb-composite0   1.11.1-1
ii  libxcb-keysyms1 0.4.0-1
ii  libxcb-randr0   1.11.1-1
ii  libxcb-shm0 1.11.1-1
ii  libxcb-xv0  1.11.1-1
ii  libxcb1 1.11.1-1
ii  libxext62:1.3.3-1
ii  libxi6  2:1.7.5-1
ii  libxinerama12:1.1.3-1+b1
ii  libxpm4 1:3.5.11-1+b1
ii  vlc-nox 2.2.1-5+b1
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages vlc recommends:
pn  vlc-plugin-notify  
pn  vlc-plugin-samba   
ii  xdg-utils  1.1.1-1

vlc suggests no packages.

Versions of packages vlc-nox depends on:
ii  liba52-0.7.4   0.7.4-18
ii  libasound2 1.0.29-1
ii  libass50.13.1-1
ii  libavahi-client3   0.6.32~rc+dfsg-1
ii  libavahi-common3   0.6.32~rc+dfsg-1
ii  libavc1394-0   0.5.4-2
ii  libavcodec-ffmpeg567:2.8.5-1
ii  libavformat-ffmpeg56   7:2.8.5-1
ii  libavutil-ffmpeg54 7:2.8.5-1
ii  libbasicusageenvironment0  2014.01.13-1
ii  libbluray1 1:0.9.2-2
ii  libc6  2.21-6
ii  libcddb2   1.3.2-5
ii  libcdio13  0.83-4.2+b1
ii  libchromaprint01.2-1+b1
ii  libcrystalhd3  1:0.0~git20110715.fdd2f19-11+b1
ii  libdbus-1-31.10.6-1
ii  libdc1394-22   2.2.3-1
ii  libdca00.0.5-7
ii  libdirectfb-1.2-9  1.2.10.0-5.1
ii  libdvbpsi101.3.0-4
ii  libdvdnav4 5.0.3-1
ii  libdvdread45.0.3-1
ii  libebml4v5 1.3.3-1
ii  libfaad2   2.8.0~cvs20150510-1
ii  libflac8   1.3.1-4
ii  libfontconfig1 2.11.0-6.3
ii  libfreetype6   2.6.1-0.1
ii  libfribidi00.19.7-1
ii  libgcc11:5.3.1-6
ii  libgcrypt201.6.4-4
ii  libgnutls-deb0-28  3.3.20-1
ii  libgpg-error0  1.21-1
ii  libgroupsock1  2014.01.13-1
ii  libjpeg62-turbo1:1.4.1-2
ii  libkate1   0.4.1-5
ii  liblircclient0 0.9.0~pre1-1.2
ii  liblivemedia23 2014.01.13-1
ii  liblua5.2-05.2.4-1
ii  libmad00.15.1b-8
ii  libmatroska6v5 1.4.4-1
ii  libmodplug11:0.8.8.5-2
ii  libmpcdec6 2:0.1~r475-1
ii  libmpeg2-4 0.5.1-7
ii  libmtp91.1.10-2
ii  libncursesw5   6.0+20151024-2
ii  libogg01.3.2-1
ii  libopus0

Bug#808763: marked as done (ImportError: Entry point ('console_scripts', 'py.test-3.5') not found)

[Debian Bug Tracking System]

Your message dated Tue, 19 Jan 2016 16:03:24 +
with message-id 
and subject line Bug#808763: fixed in pytest 2.8.5-2
has caused the Debian Bug report #808763,
regarding ImportError: Entry point ('console_scripts', 'py.test-3.5') not found
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.)


-- 
808763: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808763
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pytest
Version: 2.8.5-1
Severity: grave

Dear maintainer,

When typing: py.test-3.5

I get: $ py.test-3.5
Traceback (most recent call last):
  File "/usr/bin/py.test-3.5", line 9, in 
load_entry_point('pytest==2.8.5', 'console_scripts', 'py.test-3.5')()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 568,
in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line
2719, in load_entry_point
raise ImportError("Entry point %r not found" % ((group, name),))
ImportError: Entry point ('console_scripts', 'py.test-3.5') not found

Having a look into /usr/bin/py.test-3.5, I can see:

if __name__ == '__main__':
sys.exit(
load_entry_point('pytest==2.8.5', 'console_scripts', 'py.test-3.5')()
)

Obviously, replacing py.test-3.5 by py.test in the load_entry_point()
fixes the issue.

This bug is very annoying, because it prevents from testing with the
correct version of Python 3, in a loop of this kind:

PYTHON3S:=$(shell py3versions -vr)

override_dh_auto_test:
ifeq (,$(findstring nocheck, $(DEB_BUILD_OPTIONS)))
@echo "===> Running tests"
set -e ; set -x ; for i in 2.7 $(PYTHON3S) ; do \
PYMAJOR=`echo $$i | cut -d'.' -f1` ; \
echo "===> Testing with python$$i (python$$PYMAJOR)" ; \
PYTHON=python$$i py.test-$$i ; \
done
endif

Please fix python3-pytest ASAP.

Thanks for maintaining pytest,
Cheers,

Thomas Goirand (zigo)
--- End Message ---
--- Begin Message ---
Source: pytest
Source-Version: 2.8.5-2

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated pytest 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, 19 Jan 2016 15:59:35 +0100
Source: pytest
Binary: python-pytest python3-pytest python-pytest-doc
Architecture: source all
Version: 2.8.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sebastian Ramacher 
Description:
 python-pytest - Simple, powerful testing in Python
 python-pytest-doc - Simple, powerful testing in Python - Documentation
 python3-pytest - Simple, powerful testing in Python3
Closes: 808763
Changes:
 pytest (2.8.5-2) unstable; urgency=medium
 .
   * Team upload.
   * debian/rules:
 - Reduce duplication between python-pytest and python-pytest-doc.
 - Build documentation in *build* step and not in install step.
   * debian/control: Remove XS-Testsuite, no longer needed.
   * Revert parts of c6eb0d1da9bdf2a0cfb40d69711e8a88e86d4657 and bring back
 rtinstall, rtremove, postinstall and prerm for python3-pytest. (Closes:
 #808763)
 Until we decide that py.test-X.Y scripts are not desired, this method
 actually generates them correctly and does not require a sourceful upload
 whenever the set of supported Python 3 version changes.
Checksums-Sha1:
 2c08f8ae9ef04f8b6f2e9d28059c6fc7fe1ce325 2416 pytest_2.8.5-2.dsc
 bec3a460d14414d22ab3cd4d9deee57b035f93ce 7492 pytest_2.8.5-2.debian.tar.xz
 2d6e346eac7d1c844d9c088f4fd0790c54f6fbac 495230 
python-pytest-doc_2.8.5-2_all.deb
 f36a6d334a49167bd47c5287ec207c82237147cc 154712 python-pytest_2.8.5-2_all.deb
 c917ff3b85db89fb9949e157e59ff3c622dc0ca0 155792 python3-pytest_2.8.5-2_all.deb
Checksums-Sha256:
 8eb94a24caa7c2757bd79336714ba122dfe185be3fb3b492fe9feb6324369789 2416 
pytest_2.8.5-2.dsc
 dfa0e3f9619898ecb7a7a30f828402714e07ead7be1c79cab456caa72a31ad87 7492 
pytest_2.8.5-2.debian.tar.

Bug#811493: marked as done (pythonpyscss hard codes the python versions)

[Debian Bug Tracking System]

Your message dated Tue, 19 Jan 2016 16:03:59 +
with message-id 
and subject line Bug#811493: fixed in python-pyscss 1.3.4-5
has caused the Debian Bug report #811493,
regarding pythonpyscss hard codes the python versions
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.)


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

Package: src:python-pyscss
Version: 1.3.4-4
Severity: serious
Tags: sid stretch patch

pythonpyscss hard codes the python versions, currently doesn't test with the 
default python3 version, and will fail to build once 3.4 is removed from the 
supported pythone3 versions.


patch at
http://launchpadlibrarian.net/234612960/python-pyscss_1.3.4-4build1_1.3.4-4ubuntu1.diff.gz
--- End Message ---
--- Begin Message ---
Source: python-pyscss
Source-Version: 1.3.4-5

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

Debian distribution maintenance software
pp.
Scott Kitterman  (supplier of updated python-pyscss 
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, 19 Jan 2016 08:56:08 -0500
Source: python-pyscss
Binary: python-pyscss python3-pyscss
Architecture: source amd64
Version: 1.3.4-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Scott Kitterman 
Description:
 python-pyscss - SCSS compiler - Python 2.x
 python3-pyscss - SCSS compiler - Python 3.x
Closes: 811493
Changes:
 python-pyscss (1.3.4-5) unstable; urgency=medium
 .
   * Team upload.
   * Don't hard-code the python versions used in build to prevent FTBFS once
 python3.4 is dropped from supported versions (Closes: #811493)
 - Thanks to Matthias Klose for the patch
   * Adjust debian/rules not to depend on pytest entry points for all supported
 python/python3 versions
Checksums-Sha1:
 7d60d065f6b0772e9c59782b159973d565392bfb 2342 python-pyscss_1.3.4-5.dsc
 e7f10b2f5abc3538dc45107852c1330c5032f64a 4868 
python-pyscss_1.3.4-5.debian.tar.xz
 e7e522fa3265e502edd9a55acf076b7e43fc0a9d 26140 
python-pyscss-dbgsym_1.3.4-5_amd64.deb
 053300d89b985794e9a83080010f732b3e3fb3c3 102606 python-pyscss_1.3.4-5_amd64.deb
 3e3c4da8749e61cbf74afba925f3e4b3bd9415aa 47732 
python3-pyscss-dbgsym_1.3.4-5_amd64.deb
 f808ff5f56ea64fc315e59385ed2006cf6745819 102882 
python3-pyscss_1.3.4-5_amd64.deb
Checksums-Sha256:
 2e0295b9f833725dc3b65cc2806a125525d24ea9a5b28bc5fe7222a33af62f0f 2342 
python-pyscss_1.3.4-5.dsc
 f103c81d5b51df7bbd9c08b0753cb0634128e2b659e58283cba837c0fd7bc62f 4868 
python-pyscss_1.3.4-5.debian.tar.xz
 cd43ce436d84e58d654d84378487657fd69f7c59d3d53cd312626aadaf2c6bc1 26140 
python-pyscss-dbgsym_1.3.4-5_amd64.deb
 66079cbdee5f82e5e1b8ba64f62ae17938d96673705087b0fcd45720ede0d03f 102606 
python-pyscss_1.3.4-5_amd64.deb
 3a280962b7b0d625dc6be04d2a6b8a8c59aab33394e77c613e1fdaf452a38dd1 47732 
python3-pyscss-dbgsym_1.3.4-5_amd64.deb
 3046020ab35978b5e823b4d1c83359e9ab89dfcf650d6a27bc014d292c1ee144 102882 
python3-pyscss_1.3.4-5_amd64.deb
Files:
 64ec1d3751d1b805fa92acba51ffb17f 2342 python extra python-pyscss_1.3.4-5.dsc
 d4315f2f4769bf9100a4a728aa71bdff 4868 python extra 
python-pyscss_1.3.4-5.debian.tar.xz
 b5bfc827e5385e616dd4bac9baa19a97 26140 debug extra 
python-pyscss-dbgsym_1.3.4-5_amd64.deb
 1a08e315e77b5ad332389761c85d1279 102606 python extra 
python-pyscss_1.3.4-5_amd64.deb
 cab40fbf5728276f6d94dd96b9db94a1 47732 debug extra 
python3-pyscss-dbgsym_1.3.4-5_amd64.deb
 539c3d17a70c4591e0eb4735729dcf05 102882 python extra 
python3-pyscss_1.3.4-5_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWnkGmAAoJEHjX3vua1Zrx03EP/3UNvH0EXJVLUeLF1EIp2L4B
2504Vlf+1nRPFrHSF+jwfSo7bwgnNRh72gJ6acCuCQGtlrEY5MqbIWddgGElWSvi
tCedVD+Vux4Gr6aQGZw3dSnxVVD/mjacPffH8QgzdM/mIqqaZnoGGVr8t5dfVH0z
eCMLpKbsKLyITx3yL9dafG7tpLr5KX0Umy4/ujK7gTG0l/fV+X3BpuPKHhXbKmzb
iPvMlxfNalftViSzzMg5GO7VztgA7E1aoSlc8GfFY4jty3ucPeff5ZvQaG7NIEAV
i3AtnLKHI8QySTX7Xq9VKUxa7m+Tl9BUU7TqvEIcj0a/D8T7NJq4bBmE7WnE+5GT
xBGxa+PzheiS+u2w/GOyTaQUGqUvgG/uSQzgFD

Bug#811492: marked as done (python-gammu fails running the tests)

[Debian Bug Tracking System]

Your message dated Tue, 19 Jan 2016 16:03:38 +
with message-id 
and subject line Bug#811492: fixed in python-gammu 2.5-1
has caused the Debian Bug report #811492,
regarding python-gammu fails running the tests
to be marked as done.

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

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


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

Package: src:python-gammu
Version: 2.4-1
Severity: serious
Tags: sid stretch

test_encode_unicode (test.test_sms.PDUTest) ... ok
test_link (test.test_sms.PDUTest) ... ok
test_mms_decode (test.test_sms.PDUTest) ... ok
test_worker (test.test_worker.WorkerDummyTest) ... ok
test_connections (test.test_data.DataTest) ... ok
test_errors (test.test_data.DataTest) ... ok
test_catching (test.test_errors.ErrorTest) ... ok

==
ERROR: test_inject (test.test_smsd.SMSDDummyTest)
--
Traceback (most recent call last):
  File "/home/packages/tmp/python-gammu-2.4/test/test_smsd.py", line 60, in 
test_inject

smsd.InjectSMS([MESSAGE_1])
ERR_UNKNOWN: {'Text': u'Unknown error.', 'Code': 27, 'Where': 'SMSD_InjectSMS'}

==
ERROR: test_smsd (test.test_smsd.SMSDDummyTest)
--
Traceback (most recent call last):
  File "/home/packages/tmp/python-gammu-2.4/test/test_smsd.py", line 68, in 
test_smsd

smsd.InjectSMS([MESSAGE_1])
ERR_UNKNOWN: {'Text': u'Unknown error.', 'Code': 27, 'Where': 'SMSD_InjectSMS'}

--
Ran 46 tests in 11.161s

FAILED (errors=2)
E: pybuild pybuild:274: test: plugin distutils failed with: exit code=1: 
python2.7 setup.py test

dh_auto_test: pybuild --test -i python{version} -p 2.7 --dir . returned exit 
code 13
debian/rules:7: recipe for target 'build' failed
make: *** [build] Error 25
dpkg-buildpackage: error: debian/rules build gave error exit status 2
test_encode_unicode (test.test_sms.PDUTest) ... ok
test_link (test.test_sms.PDUTest) ... ok
test_mms_decode (test.test_sms.PDUTest) ... ok
test_worker (test.test_worker.WorkerDummyTest) ... ok
test_connections (test.test_data.DataTest) ... ok
test_errors (test.test_data.DataTest) ... ok
test_catching (test.test_errors.ErrorTest) ... ok

==
ERROR: test_inject (test.test_smsd.SMSDDummyTest)
--
Traceback (most recent call last):
  File "/home/packages/tmp/python-gammu-2.4/test/test_smsd.py", line 60, in 
test_inject

smsd.InjectSMS([MESSAGE_1])
ERR_UNKNOWN: {'Text': u'Unknown error.', 'Code': 27, 'Where': 'SMSD_InjectSMS'}

==
ERROR: test_smsd (test.test_smsd.SMSDDummyTest)
--
Traceback (most recent call last):
  File "/home/packages/tmp/python-gammu-2.4/test/test_smsd.py", line 68, in 
test_smsd

smsd.InjectSMS([MESSAGE_1])
ERR_UNKNOWN: {'Text': u'Unknown error.', 'Code': 27, 'Where': 'SMSD_InjectSMS'}

--
Ran 46 tests in 11.161s

FAILED (errors=2)
E: pybuild pybuild:274: test: plugin distutils failed with: exit code=1: 
python2.7 setup.py test

dh_auto_test: pybuild --test -i python{version} -p 2.7 --dir . returned exit 
code 13
debian/rules:7: recipe for target 'build' failed
make: *** [build] Error 25
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---
Source: python-gammu
Source-Version: 2.5-1

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

Debian distribution maintenance software
pp.
Michal Čihař  (supplier of updated python-gammu 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--

Processed: user debian...@lists.debian.org, usertagging 811444, notfound 811444 in 2.2, found 811444 in 2.2-1

[Debian Bug Tracking System]

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 811444 piuparts
There were no usertags set.
Usertags are now: piuparts.
> notfound 811444 2.2
Bug #811444 [dnssec-tools] dnssec-tools fails to install: file conflict with 
dependency
There is no source info for the package 'dnssec-tools' at version '2.2' with 
architecture ''
Unable to make a source version for version '2.2'
No longer marked as found in versions 2.2.
> found 811444 2.2-1
Bug #811444 [dnssec-tools] dnssec-tools fails to install: file conflict with 
dependency
Marked as found in versions dnssec-tools/2.2-1.
> thanks
Stopping processing here.

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

Bug#811500: cpl-plugin-visir: does not work

[Ole Streicher]

Hi Julian,

thank you for the bug report. To check the packaging, I run the unit 
tests that come with the package (hoping that they cover a good part of 
the code), and I think this is a reasonable "minimal effort" to ensure a 
package is working.


Could I ask you to provide a minimal test case that could be used? "Any" 
is a bit vague... Can you make a small test case, maybe using your demo 
data set


ftp://ftp.eso.org/pub/dfs/pipelines/visir/visir-demo-reflex-0.1.tar.gz

which I could use? Just the parameters, the SOF, and the expected output 
would be probably enough.


What concerns the removal: When I started to package the pipelines, I 
asked upstream (on cpl-h...@eso.org) for opinions, but I never got any 
response, neither positive nor negative, to the packaging. The only 
statement here was your mail in debian-science that these packages are 
"too special", but you then did not answer to my response.


I also recently discussed the topic with Pascal Ballester (upstream 
project head), and he also never mentioned that ESO does not want to 
have the pipelines packaged in Debian.


Therefore, I would ask you to start a discussion on the Debian-Astro 
mailing list about the status of the ESO pipelines, and what the reason 
is why ESO does not want them to be in Debian. You may also invite other 
people from ESO to join the discussion -- we are an open community, and 
therefore we should solve this problem accordingly (if it is really one 
for ESO).


For the swarp problem: I regularly check their web page, the SVN 
repository and the forum to see if there are problems that should be 
solved for the Debian package. Up to now, there is no problem reported, 
except some statements by you that were not supported by a concrete 
example. Could I ask you to report the problem to swarp upstream so that 
they are aware of and that they can fix it? We all would benefit from that.


Best regards

Ole

Processed: Re: boot fails in "run-init -n ..."

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #811479 [initramfs-tools-core] boot fails in "run-init -n ..."
Added tag(s) moreinfo.

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

Bug#811479: boot fails in "run-init -n ..."

[Ben Hutchings]

Control: tag -1 moreinfo

On Tue, 19 Jan 2016 11:44:39 +0100 Roderich Schupp  
wrote:
> Package: initramfs-tools-core
> Version: 0.121
> Severity: critical
> 
> boot with an initrd generated by initramfs-tools-core 1.21
> fails with "run-init: opening console: No such file or directory"
> (see attached screenshot)
> 
> It seems to be caused by validate_init() in /usr/share/initramfs-tools/init
> which has been reduced to just "run-init -n ..." using the new option -n to
> klibc's run-init. The latter bombs out in
> 
>if ((confd = open(console, O_RDWR)) < 0)
>   return "opening console";
> 
> Dunny why, as sticking "ls -l /dev/console" into /usr/share/initramfs-
> tools/init
> right before "run-init -n ..." shows that /dev/console exists...
[...]

That's showing you the /dev/console in the initramfs.  However, run-
init will open it from the 'real' root filesystem.

At the recovery shell prompt, what does "ls -l /root/dev/console" show?

Ben.

-- 
Ben Hutchings
Horngren's Observation:
   Among economists, the real world is often a special case.

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

Processed: tagging 811323, tagging 811226, tagging 811222, found 811433 in 0.4.7-1, found 798023 in 1.0-4 ...

[Debian Bug Tracking System]

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

> tags 811323 + sid stretch
Bug #811323 [src:mugshot] mugshot: FTBFS: ImportError: No module named 'gi'
Added tag(s) stretch and sid.
> tags 811226 + sid
Bug #811226 [postgresql-debversion] FTBFS: debian/control needs updating from 
debian/control.in
Added tag(s) sid.
> tags 811222 + sid
Bug #811222 [mysql-5.5] FTBFS: Can't use 'defined(@array)'
Added tag(s) sid.
> found 811433 0.4.7-1
Bug #811433 [python-greenlet-doc] python-greenlet-doc: Exact version depends 
makes package unsafe for binNMUs
Marked as found in versions python-greenlet/0.4.7-1.
> found 798023 1.0-4
Bug #798023 [src:cssutils] cssutils: FTBFS with Python 3.5
Marked as found in versions cssutils/1.0-4.
> tags 811306 + sid
Bug #811306 [mmpong] FTBFS: mmpong-gl-data missing files: 
usr/share/games/mmpong-gl
Added tag(s) sid.
> tags 811238 + sid stretch
Bug #811238 [freebsd-libs] FTBFS: error: ld returned 1 exit status
Added tag(s) sid and stretch.
> tags 811184 + sid stretch
Bug #811184 [phatch] Phatch not loading Debian Stretch
Added tag(s) stretch and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
798023: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798023
811184: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811184
811222: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811222
811226: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811226
811238: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811238
811306: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811306
811323: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811323
811433: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811433
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#807379: kde-full: kdeinit, plasmashell crashes connected with libthread_db.so.1

[Debian Bug Tracking System]

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

> reassign 807379 libqt5widgets5
Bug #807379 [kde-full] kde-full: kdeinit, plasmashell crashes connected with 
libthread_db.so.1
Bug reassigned from package 'kde-full' to 'libqt5widgets5'.
No longer marked as found in versions meta-kde/5:90.
Ignoring request to alter fixed versions of bug #807379 to the same values 
previously set
> forcemerge 790825 807379
Bug #790825 [libqt5widgets5] libqt5widgets5: Crashing when waking up from 
suspend / laptop is undocked / external screen reconnected
Bug #807379 [libqt5widgets5] kde-full: kdeinit, plasmashell crashes connected 
with libthread_db.so.1
Set Bug forwarded-to-address to 'https://bugreports.qt.io/browse/QTBUG-47033'.
Severity set to 'important' from 'grave'
Added indication that 807379 affects vlc
Marked as found in versions qtbase-opensource-src/5.5.1+dfsg-8 and 
qtbase-opensource-src/5.4.2+dfsg-4.
Added tag(s) upstream and fixed-upstream.
Merged 790825 807379
> thanks
Stopping processing here.

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

Bug#807379: kde-full: kdeinit, plasmashell crashes connected with libthread_db.so.1

[Lisandro Damián Nicanor Pérez Meyer]

reassign 807379 libqt5widgets5
forcemerge 790825 807379
thanks

On Tuesday 19 January 2016 11:54:03 Maciej Kotliński wrote:
> The bug is still present and very annoying. I observed it for longer
> period of time.

The solution might come with Qt 5.6.

-- 
Quizá, para muchos, ahora que lo pienso, Wikipedia tiene
ciertamente un defecto imperdonable. No adorna.
  Ariel Torres, "Probablemente, la Wikipedia esté bien"
  La Nación Tecnología, Sábado 25 de agosto de 2007
  http://www.lanacion.com.ar/tecnologia/nota.asp?nota_id=937889

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.

Processed: tagging 613674

[Debian Bug Tracking System]

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

> tag 613674 + fixed-upstream pending
Bug #613674 [xutils-dev] Subject: xutils-dev: Can't get have_xmlto_text unless 
I add some content to the conftest.xml
Added tag(s) pending and fixed-upstream.
> thanks
Stopping processing here.

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

Bug#790273: Bug#811144: FTBFS: error: expected identifier or '(' before '__extension__'

[Andreas Beckmann]

Hi Robert,

On Tue, 19 Jan 2016 00:45:36 +0100 Robert Luberda  wrote:
> > dwww fails to build in unstable:
> 
> This is caused by publib-dev that provides declaration of strndup which
> turned out to be a macro in recent glibc/gcc.
> 
> I've just prepared NMU for publib-dev (see that attached patch), and
> uploaded  it to DELAYED/3.

publib is orphaned, so you could do a proper QA upload instead.


Andreas

Processed: Bug#808763 marked as pending

[Debian Bug Tracking System]

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

> tag 808763 pending
Bug #808763 [python3-pytest] ImportError: Entry point ('console_scripts', 
'py.test-3.5') not found
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#808763: marked as pending

[Sebastian Ramacher]

tag 808763 pending
thanks

Hello,

Bug #808763 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/pytest.git;a=commitdiff;h=e08b488

---
commit e08b488dffb8b7dfe2772be6e2bc46d66e6e57de
Author: Sebastian Ramacher 
Date:   Tue Jan 19 15:57:23 2016 +0100

Use correct bug number

diff --git a/debian/changelog b/debian/changelog
index c3e4731..395aa58 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -6,7 +6,7 @@ pytest (2.8.5-2) UNRELEASED; urgency=medium
 - Build documentation in *build* step and not in install step.
   * Revert parts of c6eb0d1da9bdf2a0cfb40d69711e8a88e86d4657 and bring back
 rtinstall, rtremove, postinstall and prerm for python3-pytest. (Closes:
-#811301)
+#808763)
 Until we decide that py.test-X.Y scripts are not desired, this method
 actually generates them correctly and does not require a sourceful upload
 whenever the set of supported Python 3 version changes.

Bug#811450: marked as done (acheck-rules: No license statement)

[Debian Bug Tracking System]

Your message dated Tue, 19 Jan 2016 12:44:21 -0200
with message-id 

and subject line Re: acheck-rules: No license statement
has caused the Debian Bug report #811450,
regarding acheck-rules: No license statement
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.)


-- 
811450: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811450
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: acheck-rules
Severity: serious
Justification: Policy 2.3

The upstream source code doesn't provide a license file or any copyright
notice. It conflicts with Debian Policy:

"Note that under international copyright law (this applies in the United
 States, too), no distribution or modification of a work is allowed without
 an explicit notice saying so. Therefore a program without a copyright notice
 is copyrighted and you may not do anything to it without risking being sued!
 Likewise if a program has a copyright notice but no statement saying what is
 permitted then nothing is permitted."

Thanks,

Eriberto

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect
--- End Message ---
--- Begin Message ---
This package is native. So, the original debian/copyright can be
considered as the official license. I am closing this bug.

Sorry for my mistake.

PS: I will migrate the d/copyright to 1.0 format now.

Regards,

Eriberto--- End Message ---

Bug#811492: marked as pending

[Michal Čihař]

tag 811492 pending
thanks

Hello,

Bug #811492 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/python-gammu.git;a=commitdiff;h=6ca7156

---
commit 6ca7156012b5bd851dcda73826db567de1643a35
Author: Michal Čihař 
Date:   Tue Jan 19 15:34:08 2016 +0100

New upstream release.

* New upstream release.
  - Compatible with current Gammu (Closes: #811492).

diff --git a/debian/changelog b/debian/changelog
index f71c54b..dce67ba 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8 +1,10 @@
-python-gammu (2.4-2) UNRELEASED; urgency=medium
+python-gammu (2.5-1) unstable; urgency=medium
 
+  * New upstream release.
+- Compatible with current Gammu (Closes: #811492).
   * Add forgotten Vcs-* headers to debian/control.
 
- -- Michal Čihař   Tue, 19 Jan 2016 15:32:35 +0100
+ -- Michal Čihař   Tue, 19 Jan 2016 15:37:46 +0100
 
 python-gammu (2.4-1) unstable; urgency=medium
 

Bug#811500: cpl-plugin-visir: does not work

[Julian Taylor]

Package: cpl-plugin-visir
Version: 4.1.0+dfsg-1
Severity: serious

the packaged recipe does not work at all for several reasons:

1. removed patched copy of swarp, visir does not work with 2.38, it 
needs 2.19 or the embedded convinience copy. To see run the 
visir_img_reduce recipe on any data and look at the garbage weight map 
it produces
2. does not work with packaged swarp even if that one would work because 
it is name SWarp not swarp as the pipeline expects.

3. the required swarp configuration visir_default.swarp is not installed.

Please spend at least at least the minimal effort to see if what you are 
packaging even works or don't bother at all. Note that in future the 
embedded swarp might receive more visir specific patches.


As upstream does not want this pipeline packaged in distributions I 
would recommend removing it completely.

Processed: Bug#811492 marked as pending

[Debian Bug Tracking System]

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

> tag 811492 pending
Bug #811492 [src:python-gammu] python-gammu fails running the tests
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 811493

[Debian Bug Tracking System]

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

> tags 811493 + pending
Bug #811493 [src:python-pyscss] pythonpyscss hard codes the python versions
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: Bug#811471: zopfli: contains sample code from the RFC without any attribution

[Debian Bug Tracking System]

Processing control commands:

> tag -1 fixed-upstream
Bug #811471 [src:zopfli] zopfli: contains sample code from the RFC without any 
attribution
Added tag(s) fixed-upstream.

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

Bug#811471: zopfli: contains sample code from the RFC without any attribution

[Julian Andres Klode]

Control: tag -1 fixed-upstream

On Tue, Jan 19, 2016 at 10:11:41AM +0100, Julian Andres Klode wrote:
> Source: zopfli
> Severity: serious
> Tags: upstream
> Control: forwarded -1 https://github.com/google/zopfli/issues/88
> 
> The CRC code used in gzip_container.c comes almost directly from the RFC 
> 1952, 
> except for the naming conventions and some additional consting. 
> Even the comments are copied.

This has been fixed in this upstream commit:
 
https://github.com/google/zopfli/commit/0e58e4e0adc5302a41cf2ee1c833aa2c20c67fd0


-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.

When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to (`inline'). Thank you.

Bug#811498: libconsole-bridge0.2v5: ABI bump without package rename

[Jochen Sprickerhof]

Package: libconsole-bridge0.2v5
Version: 0.3.0-1
Severity: serious
Justification: Policy 8.1

Hi Jose,

the new libconsole-bridge0.2v5 package contains a library with a new name,
making all depending packages break due to linker error.

0.3.0-1:
$ dpkg -L libconsole-bridge0.2v5 | grep so\.0
/usr/lib/x86_64-linux-gnu/libconsole_bridge.so.0.3

0.2.5-2.1:
$ dpkg -L libconsole-bridge0.2v5 | grep so\.0
/usr/lib/x86_64-linux-gnu/libconsole_bridge.so.0.2

According to policy 8.1:
"The run-time shared library must be placed in a package whose name changes
whenever the SONAME of the shared library changes."

Please rename the package to libconsole-bridge0.3. Note that this means a
transition, so please coordinate with the release team.

Cheers Jochen

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

Kernel: Linux 4.3.0-1-amd64 (SMP w/12 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: sysvinit (via /sbin/init)

Versions of packages libconsole-bridge0.2v5 depends on:
ii  libc6   2.21-6
ii  libgcc1 1:5.3.1-6
ii  libstdc++6  5.3.1-6

libconsole-bridge0.2v5 recommends no packages.

libconsole-bridge0.2v5 suggests no packages.

-- no debconf information

Bug#811492: python-gammu fails running the tests

[Michal Čihař]

Hi

Dne 19.1.2016 v 14:20 Matthias Klose napsal(a):
> Package: src:python-gammu
> Version: 2.4-1
> Severity: serious
> Tags: sid stretch
> 
> test_encode_unicode (test.test_sms.PDUTest) ... ok
> test_link (test.test_sms.PDUTest) ... ok
> test_mms_decode (test.test_sms.PDUTest) ... ok
> test_worker (test.test_worker.WorkerDummyTest) ... ok
> test_connections (test.test_data.DataTest) ... ok
> test_errors (test.test_data.DataTest) ... ok
> test_catching (test.test_errors.ErrorTest) ... ok
> 
> ==
> ERROR: test_inject (test.test_smsd.SMSDDummyTest)
> --
> Traceback (most recent call last):
>   File "/home/packages/tmp/python-gammu-2.4/test/test_smsd.py", line 60,
> in test_inject
> smsd.InjectSMS([MESSAGE_1])
> ERR_UNKNOWN: {'Text': u'Unknown error.', 'Code': 27, 'Where':
> 'SMSD_InjectSMS'}

Thanks for spotting this, I've fixed this testsuite bug upstream and
will upload fixed package soon.

-- 
Michal Čihař | http://cihar.com | http://blog.cihar.com



signature.asc
Description: OpenPGP digital signature

Processed: tagging 811492

[Debian Bug Tracking System]

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

> tags 811492 + upstream fixed-upstream
Bug #811492 [src:python-gammu] python-gammu fails running the tests
Added tag(s) fixed-upstream and upstream.
> thanks
Stopping processing here.

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

Bug#811493: pythonpyscss hard codes the python versions

[Matthias Klose]

Package: src:python-pyscss
Version: 1.3.4-4
Severity: serious
Tags: sid stretch patch

pythonpyscss hard codes the python versions, currently doesn't test with the 
default python3 version, and will fail to build once 3.4 is removed from the 
supported pythone3 versions.


patch at
http://launchpadlibrarian.net/234612960/python-pyscss_1.3.4-4build1_1.3.4-4ubuntu1.diff.gz

Bug#811492: python-gammu fails running the tests

[Matthias Klose]

Package: src:python-gammu
Version: 2.4-1
Severity: serious
Tags: sid stretch

test_encode_unicode (test.test_sms.PDUTest) ... ok
test_link (test.test_sms.PDUTest) ... ok
test_mms_decode (test.test_sms.PDUTest) ... ok
test_worker (test.test_worker.WorkerDummyTest) ... ok
test_connections (test.test_data.DataTest) ... ok
test_errors (test.test_data.DataTest) ... ok
test_catching (test.test_errors.ErrorTest) ... ok

==
ERROR: test_inject (test.test_smsd.SMSDDummyTest)
--
Traceback (most recent call last):
  File "/home/packages/tmp/python-gammu-2.4/test/test_smsd.py", line 60, in 
test_inject

smsd.InjectSMS([MESSAGE_1])
ERR_UNKNOWN: {'Text': u'Unknown error.', 'Code': 27, 'Where': 'SMSD_InjectSMS'}

==
ERROR: test_smsd (test.test_smsd.SMSDDummyTest)
--
Traceback (most recent call last):
  File "/home/packages/tmp/python-gammu-2.4/test/test_smsd.py", line 68, in 
test_smsd

smsd.InjectSMS([MESSAGE_1])
ERR_UNKNOWN: {'Text': u'Unknown error.', 'Code': 27, 'Where': 'SMSD_InjectSMS'}

--
Ran 46 tests in 11.161s

FAILED (errors=2)
E: pybuild pybuild:274: test: plugin distutils failed with: exit code=1: 
python2.7 setup.py test

dh_auto_test: pybuild --test -i python{version} -p 2.7 --dir . returned exit 
code 13
debian/rules:7: recipe for target 'build' failed
make: *** [build] Error 25
dpkg-buildpackage: error: debian/rules build gave error exit status 2
test_encode_unicode (test.test_sms.PDUTest) ... ok
test_link (test.test_sms.PDUTest) ... ok
test_mms_decode (test.test_sms.PDUTest) ... ok
test_worker (test.test_worker.WorkerDummyTest) ... ok
test_connections (test.test_data.DataTest) ... ok
test_errors (test.test_data.DataTest) ... ok
test_catching (test.test_errors.ErrorTest) ... ok

==
ERROR: test_inject (test.test_smsd.SMSDDummyTest)
--
Traceback (most recent call last):
  File "/home/packages/tmp/python-gammu-2.4/test/test_smsd.py", line 60, in 
test_inject

smsd.InjectSMS([MESSAGE_1])
ERR_UNKNOWN: {'Text': u'Unknown error.', 'Code': 27, 'Where': 'SMSD_InjectSMS'}

==
ERROR: test_smsd (test.test_smsd.SMSDDummyTest)
--
Traceback (most recent call last):
  File "/home/packages/tmp/python-gammu-2.4/test/test_smsd.py", line 68, in 
test_smsd

smsd.InjectSMS([MESSAGE_1])
ERR_UNKNOWN: {'Text': u'Unknown error.', 'Code': 27, 'Where': 'SMSD_InjectSMS'}

--
Ran 46 tests in 11.161s

FAILED (errors=2)
E: pybuild pybuild:274: test: plugin distutils failed with: exit code=1: 
python2.7 setup.py test

dh_auto_test: pybuild --test -i python{version} -p 2.7 --dir . returned exit 
code 13
debian/rules:7: recipe for target 'build' failed
make: *** [build] Error 25
dpkg-buildpackage: error: debian/rules build gave error exit status 2

Bug#811490: python-falcon fails the tests running with python3

[Matthias Klose]

Package: src:python-falcon
Version: 0.3.0-4
Severity: serious
Tags: sid stretch

tests.test_wsgi.TestWsgi.test_pep ... ok
tests.test_wsgi.TestWsgi.test_srmock ... ok
tests.test_wsgi.TestWsgi.test_wsgiref ... 127.0.0.1 - - [19/Jan/2016 13:06:15] 
"GET / HTTP/1.1" 200 0

127.0.0.1 - - [19/Jan/2016 13:06:15] "PUT / HTTP/1.1" 200 0
127.0.0.1 - - [19/Jan/2016 13:06:15] "PUT / HTTP/1.1" 200 0
127.0.0.1 - - [19/Jan/2016 13:06:15] "POST / HTTP/1.1" 405 0
ok
tests.test_wsgi_errors.TestWSGIError.test_responder_logged_bytestring ... ok
tests.test_wsgi_errors.TestWSGIError.test_responder_logged_unicode ... SKIP: 
Test only applies to Python 2


==
ERROR: tests.test_cookies.TestCookies.test_request_cookie_parsing
--
testtools.testresult.real._StringException: Traceback (most recent call last):
  File "/home/packages/tmp/python-falcon-0.3.0/tests/test_cookies.py", line 
144, in test_request_cookie_parsing

self.assertEqual("no", req.cookies["logged_in"])
KeyError: 'logged_in'


--
Ran 334 tests in 1.759s

FAILED (SKIP=3, errors=1)
debian/rules:27: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/home/packages/tmp/python-falcon-0.3.0'

Processed: control

[Debian Bug Tracking System]

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

> block 811158 by 793511
Bug #811158 [ftp.debian.org] RM: mysql-5.5 -- ROM; Superceeded by mysql-5.6 
package
811158 was not blocked by any bugs.
811158 was not blocking any bugs.
Added blocking bug(s) of 811158: 793511
> thanks
Stopping processing here.

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

Bug#800265: marked as done (heroes-sound-tracks: Please migrate a supported debhelper compat level)

[Debian Bug Tracking System]

Your message dated Tue, 19 Jan 2016 12:48:57 +
with message-id 
and subject line Bug#800265: fixed in heroes-sound-tracks 1.0-5
has caused the Debian Bug report #800265,
regarding heroes-sound-tracks: Please migrate a supported debhelper compat level
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.)


-- 
800265: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800265
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: heroes-sound-tracks
Severity: important
Usertags: deprecated-debhelper-compat-leq-3

Hi,

The package heroes-sound-tracks is using a debhelper compat level of 3 or less
according to lintian.  These compat levels have been deprecated for
the past ~10 years and debhelper will remove support for them in the near
future (as declared in [1]).

 * Please migrate the package to a supported debhelper compat level.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum (compat 4 will be removed soon as
 well)

 * If your package uses any of the following tools, please remove them
   from the rules files.  Neither of them does anything except warn
   about their deprecation.
   - dh_desktop
   - dh_scrollkeeper (deadline: January 1st 2016)
   - dh_suidregister
   - dh_undocumented

 * Please note that your package might have been flagged for using
   e.g. "DH_COMPAT=2 dh_foo ...".
   - This will still cause issues when the compat level is removed.

 * If the package has been relying on dh_install being lenient about
   missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Deadline: 
   - compat 1+2: November 1st 2015
   - compat 3: January 1st 2016

If you are using other deprecated debhelper features (such as omitting
the debian/compat file), please consider fixing those while you are at
it.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: heroes-sound-tracks
Source-Version: 1.0-5

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

Debian distribution maintenance software
pp.
Stephen Kitt  (supplier of updated heroes-sound-tracks 
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: Tue, 19 Jan 2016 13:31:42 +0100
Source: heroes-sound-tracks
Binary: heroes-sound-tracks
Architecture: source
Version: 1.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Stephen Kitt 
Description:
 heroes-sound-tracks - Optional sound files for heroes
Closes: 529117 738898 800265
Changes:
 heroes-sound-tracks (1.0-5) unstable; urgency=medium
 .
   * New maintainer (closes: #738898).
   * Switch to debhelper compatibility level 9, using dh  (closes:
 #800265).
   * Update debian/watch (thanks to Bart Martens; closes: #529117).
   * Drop obsolete Conflicts/Replaces.
   * Switch to source format "3.0 (quilt)."
   * Standards-Version 3.9.6, no further change required.
   * Add homepage.
   * Add VCS URIs.
Checksums-Sha1:
 f7cac1f61a0b52b0b1f337deb43c6cafdcaf1bff 2017 heroes-sound-tracks_1.0-5.dsc
 5229286e1335338c9c2dcf5130247deee6534ffd 2424 
heroes-sound-tracks_1.0-5.debian.tar.xz
Checksums-Sha256:
 b27f833d07fc20de0ba5695f13ee28ff2c1dc1c53da3e4d2d9084927d7fe07cd 2017 
heroes-sound-tracks_1.0-5.dsc
 877a50c302d70246d1f7c8a19d8abc493d4d71532294248ada83163ecc7b0c23 2424 
heroes-sound-tracks_1.0-5.debian.tar.xz
Files:
 a15901a735940645cdfb05400ee714cc 2017 games optional 
heroes-sound-tracks_1.0-5.dsc
 7885dd6242bcde2f84480bc48d1f0070 2424 games optional 
heroes-sound-tracks_1.0-5.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJWni3uAAoJEIDTAvWIbYOcR9IP/RXLbvRs1FRKk4WpfICLBJ4e
7Q0omotHDxN9EHdD9JJXJG+yF5gfpHYxeWqEEC0cP8f/aTb5gsdPOqfqI93I8sC3
80tViXwG5YqItJYZzrokSkFM1L8pimxyDyY6bHaWnchNK6u//p70CifNg+IN8Of6
73QcjHLHqorygIC6sbMHhyoANtnnVrMlLj3/UzrFecUwuZZWu1TACFqrzOzsG8IX
NW0iOPn/lcFr4npHuJfUL744r+cYW24jG5O0UwBkSYOh+bJc+ITJF1pkAUMzFJnh
aeXI/S74WS1hB2IRHRdnwiPpPpOOR1tki8xeA2HvQB4K5vwNPYb/Ir69N8NwGzjC
8TQH7D6xo7YLqfdWGmFnEUTrs/BbjDqoVeHzz2dHEjh2lIs

Bug#807609: marked as done (spatial4j: FTBFS: [ERROR] The specified user settings file does not exist: /etc/maven2/settings-debian.xml)

[Debian Bug Tracking System]

Your message dated Tue, 19 Jan 2016 12:34:58 +
with message-id 
and subject line Bug#807609: fixed in spatial4j 0.3-1.1
has caused the Debian Bug report #807609,
regarding spatial4j: FTBFS: [ERROR] The specified user settings file does not 
exist: /etc/maven2/settings-debian.xml
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.)


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

Dear Maintainer,

spatial4j fails to build from source in unstable/amd64:

  [..]

  dh_auto_configure
mh_patchpoms -plibspatial4j-java --debian-build
--keep-pom-version

--maven-repo=/home/lamby/temp/cdt.20151210224817.op2c8yjrOs/spatial4j-0.3/debian/maven-repo
  mvn install:install-file -s/etc/maven2/settings-debian.xml
  -Dmaven.repo.local=`pwd`/debian/maven-repo
  -Dfile=/usr/share/java/jts.jar -DgroupId=com.vividsolutions
  -DartifactId=jts -Dversion=fake -Dpackaging=jar
  [ERROR] Error executing Maven.
  [ERROR] The specified user settings file does not exist:
  /etc/maven2/settings-debian.xml
  debian/rules:9: recipe for target 'override_dh_auto_configure' failed
  make[1]: *** [override_dh_auto_configure] Error 1
  make[1]: Leaving directory
  '/home/lamby/temp/cdt.20151210224817.op2c8yjrOs/spatial4j-0.3'
  debian/rules:6: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


spatial4j.0.3-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: spatial4j
Source-Version: 0.3-1.1

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated spatial4j 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, 19 Jan 2016 13:19:03 +0100
Source: spatial4j
Binary: libspatial4j-java
Architecture: source all
Version: 0.3-1.1
Distribution: unstable
Urgency: medium
Maintainer: Hilko Bengen 
Changed-By: Emmanuel Bourg 
Description:
 libspatial4j-java - spatial/geospatial Java library
Closes: 806430 807609
Changes:
 spatial4j (0.3-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fixed the build failure with maven-debian-helper >= 2.0
 (Closes: #806430, #807609)
Checksums-Sha1:
 a19ac70fc23831833fd768b30d7e4e17804d1cb9 1760 spatial4j_0.3-1.1.dsc
 87046cb08bf4ee075391151e12cd67242304c604 2288 spatial4j_0.3-1.1.debian.tar.xz
 421e7bdcfc76312be01014672a27834e5f69ce3d 64904 
libspatial4j-java_0.3-1.1_all.deb
Checksums-Sha256:
 7e06c335a5863056b3d8f5a7c3496b8cf4a4209f904ab28666535d721b1dd399 1760 
spatial4j_0.3-1.1.dsc
 f37c0a5976a30e088cbac5f224a8b776cbadc18ab5f46716474ca9394b7b449b 2288 
spatial4j_0.3-1.1.debian.tar.xz
 a894e4be3fb61eb91d00d129fbd58b55d7731e6587d7361be5b25e2b4bc08f52 64904 
libspatial4j-java_0.3-1.1_all.deb
Files:
 b616d9fbbc26f9cf266a368814b7b6d3 1760 java optional spatial4j_0.3-1.1.dsc
 a82325e69a2fcb4816e0041f5026fb11 2288 java optional 
spatial4j_0.3-1.1.debian.tar.xz
 2beb1321ebbfe4023e0c3ec7dfcbf7d9 64904 java optional 
libspatial4j-java_0.3-1.1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWnioGAAoJEPUTxBnkudCsLTYQAL1H1B1X7RzSsMan2KsD4oUq
7jKWHIaJNEkY2zpM6GD9wYOBY12ZIBT5bOJQl1PZsM7vIJVAwkuFU3QBoo8jZdEC
Ir84Nt65P4jBcg2Z3Q6lYhUkDHy8o7pnwJTbRalo85qs1D4aGfudoTXZCmMS0WRj
J3QTYPfL4KYIYkIJNNvFDJUPaLhi06WbAfMvDM9z21UIyEsTz8/fK6ujgxmFdio7
PjUPRKdxP1JzuDFKR4XLyI7e1XxrAKA/OYsHQ6S2b6SZxDNyORR6gwPpGxvxv0Vv
s030ooYn/V3L4C/ylbJND8jBF8Gq/xelHI8XI2kmTZvHHPG5pJIXpeE007aWYyBR
rRKLSxWfPjLP1E3HURPC33Zsa1HdBnb3HRMy1smdDZYVrwIcnyuNqKiU80RqsRJO
Vkf6rBxtPJQUziqSLqg5vKl1krvjJwrvps+umkULf+z6OEcPxFm4V21mgSVgxsR9
M7+4YAhu

Bug#811443: mysql-5.6: Multiple security fixes from the January 2016 CPU

[Robie Basak]

Question for the security team.

On Mon, Jan 18, 2016 at 09:16:06PM +0100, Norvald H. Ryeng wrote:
> Source: mysql-5.6
> Version: 5.6.27-2
> Severity: grave
> Tags: security upstream fixed-upstream

5.6.27-2 only exists in testing, and I uploaded 5.6.28-1 to unstable
recently. It hasn't landed in testing yet, but when it does this bug
will be fixed.

Is there anything we should do to accelerate this, given that it will be
a security fix?


signature.asc
Description: Digital signature

Processed: affects 811479

[Debian Bug Tracking System]

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

> # Seems to affect Sid DomUs generated with xen-tools and initramfs-tools 
> 0.121, too
> affects 811479 + xen-tools
Bug #811479 [initramfs-tools-core] boot fails in "run-init -n ..."
Added indication that 811479 affects xen-tools
> thanks
Stopping processing here.

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

Bug#807379: kde-full: kdeinit, plasmashell crashes connected with libthread_db.so.1

[Maciej Kotliński]

The bug is still present and very annoying. I observed it for longer 
period of time.


The first observation (and the way to reproduce) is:
-lock the screen without external display connected
-connect external display (I use 2 displays connected via VGA and 
DisplayPort)

External displays start working.
Login/Lock screen disappears. I can see my desktop and all opened 
windows (the password was not typed in!). The windows do not have title 
bar but are responsive (you can scroll the text in editor etc.).
There is an error window telling that kdeinit5 has crashed. I can save 
the file with some debuging info (attached). When I close this window 
the X server restarts.
This is one of the most unpleasant scenarios - all opened apps are 
killed with Xorg restart.


The other way to observe the crash:
After restarting Xorg with external monitor connected disconnect the 
monitor (this time I use one monitor connected to DisplayPort). The 
screen on the laptop is getting black with arrow. I have to restart Xorg 
to do anything.


There is also many other crashes of Plasma, kdeinit5, kwin during normal 
work (without connecting/disconnecting external displays).
The windows lose title bar after crashes of kwin. Kwin can be started 
manually, than everything works fine until the next crash.

It looks like Plasma restarts after the crash. I only see the error message.

All packages are up to date (Debian testing).
kde-full 5:90
xorg 1:7.7+12

Application: kdeinit5 (kdeinit5), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#4  0x7fc10529f21e in QXcbScreen::mapToNative(QRect const&) const () from 
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#5  0x7fc1052a43f3 in QXcbWindow::mapToNative(QRect const&, QXcbScreen 
const*) const () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#6  0x7fc1052a5beb in QXcbWindow::propagateSizeHints() () from 
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#7  0x7fc1052aad7c in QXcbWindow::setGeometry(QRect const&) () from 
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#8  0x7fc1178f19df in QWidgetPrivate::setGeometry_sys(int, int, int, int, 
bool) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#9  0x7fc1178f2590 in QWidget::setGeometry(QRect const&) () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x7fc118e716ca in QMetaObject::activate(QObject*, int, int, void**) () 
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7fc11791055e in QDesktopWidget::resized(int) () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x7fc117911a08 in ?? () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x7fc118e716ca in QMetaObject::activate(QObject*, int, int, void**) () 
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7fc11917b102 in QGuiApplication::screenAdded(QScreen*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#15 0x7fc105291db9 in 
QXcbConnection::updateScreens(xcb_randr_notify_event_t const*) () from 
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#16 0x7fc1052928b3 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) 
() from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#17 0x7fc105292d13 in QXcbConnection::processXcbEvents() () from 
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#18 0x7fc118e72591 in QObject::event(QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x7fc1178b6ffc in QApplicationPrivate::notify_helper(QObject*, QEvent*) 
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#20 0x7fc1178bc4c6 in QApplication::notify(QObject*, QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#21 0x7fc118e42b6b in QCoreApplication::notifyInternal(QObject*, QEvent*) 
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x7fc118e44f66 in QCoreApplicationPrivate::sendPostedEvents(QObject*, 
int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x7fc118e98ed3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x7fc1159e0fd7 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x7fc1159e1230 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x7fc1159e12dc in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x7fc118e992df in 
QEventDispatcherGlib::processEvents(QFlags) () 
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#28 0x7fc118e402fa in 
QEventLoop::exec(QFlags) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#29 0x7fc118e483dc in QCoreApplication::exec() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#30 0x7fc1070a1f46 in kdemain () from 
/usr/lib/x86_64-linux-gnu/libkdeinit5_ksmserver.so
#31 0x00408596 in ?? ()
#32 0x00409da9 in ?? ()
#33 0x0040a3cf in ?? ()
#34 0x0040511c in main ()

Bug#810631: critical: cause found to lxdm pasword fail problem

[Andriy Grytsenko]

control: severity -1 important

This bug, while afecting usability of the system, still does not make it
completely unusable, therefore, according to the BTS policy, should have
another severity, see https://www.debian.org/Bugs/Developer#severities as
a reference.

And since there was no solution found yet, there is no reason to release
any package updates with patches that don't work. Thank you very much.

Processed: Re: critical: cause found to lxdm pasword fail problem

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #810631 [lxdm] lxdm grave problem: not show list users if password fail
Severity set to 'important' from 'grave'

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

Processed: reassign 811480 to libwraster5, forcibly merging 811304 811480, affects 811304

[Debian Bug Tracking System]

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

> reassign 811480 libwraster5
Bug #811480 [wdm] After recent system upgrade, wdm does not start anymore with 
"version `LIBWRASTER3' not found (required by wdmLogin)"
Bug reassigned from package 'wdm' to 'libwraster5'.
No longer marked as found in versions wdm/1.28-18.
Ignoring request to alter fixed versions of bug #811480 to the same values 
previously set
> forcemerge 811304 811480
Bug #811304 [libwraster5] wdmLogin: /usr/lib/x86_64-linux-gnu/libwraster.so.5: 
version `LIBWRASTER3' not found
Bug #811480 [libwraster5] After recent system upgrade, wdm does not start 
anymore with "version `LIBWRASTER3' not found (required by wdmLogin)"
Set Bug forwarded-to-address to 
'http://article.gmane.org/gmane.compw.window-managers.windowmaker.devel/9757'.
Marked as found in versions wmaker/0.95.7-2.
Added tag(s) confirmed and pending.
Merged 811304 811480
> affects 811304 wdm
Bug #811304 [libwraster5] wdmLogin: /usr/lib/x86_64-linux-gnu/libwraster.so.5: 
version `LIBWRASTER3' not found
Bug #811480 [libwraster5] After recent system upgrade, wdm does not start 
anymore with "version `LIBWRASTER3' not found (required by wdmLogin)"
Added indication that 811304 affects wdm
Added indication that 811480 affects wdm
> thanks
Stopping processing here.

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

Bug#811480: After recent system upgrade, wdm does not start anymore with "version `LIBWRASTER3' not found (required by wdmLogin)"

[Klaus Ethgen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package: wdm
Version: 1.28-18
Severity: grave

With the recent upgrade of my systems, wdm does not start anymore with
the following error:
   wdm: wdmLogin: /usr/lib/i386-linux-gnu/libwraster.so.5: version 
`LIBWRASTER3' not found (required by wdmLogin)
  : Greet: guarenteed_read error, UNMANAGE DISPLAY
  : Greet: pipe read error with /usr/bin/wdmLogin
   wdm: Server crash rate too high: removing display :0
   wdm: (II)

I have no idea what triggered that bug. I already tried to downgrade
libwraster5 to version 0.95.7-2 but has no effect.

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

Kernel: Linux 4.2.6 (SMP w/8 CPU cores)
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages wdm depends on:
ii  debconf [debconf-2.0]  1.5.58
ii  libc6  2.21-6
ii  libpam-modules 1.1.8-3.2
ii  libpam-runtime 1.1.8-3.2
ii  libpam0g   1.1.8-3.2
ii  libselinux12.4-3
ii  libwings3  0.95.7-2
ii  libwraster50.95.7-2
ii  libwutil5  0.95.7-2
ii  libx11-6   2:1.6.3-1
ii  libxau61:1.0.8-1
ii  libxdmcp6  1:1.1.2-1
ii  libxinerama1   2:1.1.3-1+b1
ii  libxmu62:1.1.2-2
ii  psmisc 22.21-2.1+b1
ii  x11-apps   7.7+5
ii  x11-common 1:7.7+12
ii  x11-utils  7.7+3
ii  x11-xserver-utils  7.7+5

wdm recommends no packages.

Versions of packages wdm suggests:
ii  xfonts-base  1:1.0.4+nmu1

- -- Configuration Files:
/etc/X11/wdm/wdm-config [Errno 13] Keine Berechtigung: 
u'/etc/X11/wdm/wdm-config'

- -- debconf information:
* shared/default-x-display-manager: wdm
  wdm/daemon_name: /usr/bin/wdm

- -- 
Klaus Ethgen  http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen 
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQGcBAEBCgAGBQJWnhOgAAoJEKZ8CrGAGfasbnoL/Al0nlpt9uHId4LyVAqUW/nS
0h4OYEoa6rSCRYOQrmvqMaRJmusCrDxISjDs+7xScR8XYhQzcb+9KfurIEtnXFgn
tjKOFJDgY4ZHl39lb9JJqnULf8zdSljmDjfJECsLTAMLH1vMl7SwEgmcxJwJBFj0
62paVDb1wvyDlruu3evvBfnt52jJ/8qTq2GnIa7WLw/GyLUWM9XwcenNKsENyj95
GY2oWW1S7pqzQUUuiwGecfKaf6op566zKs+OqsFsc2ivMPK1IS74fDArWl0Zg2d4
4NEcjF03savG2tastoZvyXePsvL3JT1e65Gk/SyVj+sck2l59l1Yub9H3hRY5bc9
aFi2vMqZLW5YcqN0zKSv9J3lyfo2ORO/W7iNoAJ/N9fAMqIVNdpRyly+cwmDpN09
YT7EjTMccDTMVCIrzmdEOqgOpZcktqlBSSF2vKD2KjZfc7/EpS+FpSNX5eH9SV0f
QEsfKXF9CWI+g+5GQLzIXkQrOgPtfrj0XqNnwd6Rmg==
=iT0Q
-END PGP SIGNATURE-

Bug#811477: FTBFS: missing dependency on funcsigs

[Thomas Goirand]

Source: kombu
Version: 3.0.32-1
Severity: serious

Hi,

Building a backport of the package using sbuild, I got:

I: pybuild base:170: python3.4 setup.py test
running test
Searching for funcsigs
Reading https://pypi.python.org/simple/funcsigs/
Download error on https://pypi.python.org/simple/funcsigs/: [Errno 111] 
Connection refused -- Some packages may not be found!
Couldn't find index page for 'funcsigs' (maybe misspelled?)
Scanning index of all packages (this may take a while)
Reading https://pypi.python.org/simple/
Download error on https://pypi.python.org/simple/: [Errno 111] Connection 
refused -- Some packages may not be found!
No local packages or download links found for funcsigs
error: Could not find suitable distribution for Requirement.parse('funcsigs')
E: pybuild pybuild:256: test: plugin custom failed with: exit code=1: python3.4 
setup.py test
dh_auto_test: pybuild --test -i python{version} -p 3.4 --system=custom 
--test-args={interpreter} setup.py test --dir . returned exit code 13
make[1]: *** [override_dh_auto_test] Error 13
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: Leaving directory '/«PKGBUILDDIR»'
make: *** [build] Error 2
debian/rules:6: recipe for target 'build' failed
dpkg-buildpackage: error: debian/rules build gave error exit status 2

Obviously, it's missing a (build) dependency on python{3,}-funcsigs.
Adding it in debian/control fixed the issue for me.

Cheers,

Thomas Goirand (zigo)

Bug#810357: R crashes with "Illegal instruction" on mips

[Julien Cristau]

On Tue, Jan 12, 2016 at 07:21:39 -0600, Dirk Eddelbuettel wrote:

> 
> On 12 January 2016 at 12:55, Julien Cristau wrote:
> | On Sun, Jan 10, 2016 at 17:09:09 +0100, Sébastien Villemot wrote:
> | 
> | > Le dimanche 10 janvier 2016 à 09:56 -0600, Dirk Eddelbuettel a écrit :
> | > 
> | > > Did you get a chance to poke?  Did you get anywhere, or did you get
> | > > stuck?
> | > 
> | > Yes I had the time to look at it. It's indeed a compiler issue. The
> | > problem goes away if one compiles with GCC 4.9 (I could not give a try
> | > to GCC 6, which is not yet compiled in experimental for mips).
> | > 
> | It could also be a kernel issue.  Our mips hosts don't have an fpu, so
> | floating point operations trap to the kernel and are emulated.  Similar
> | bugs have happened before, see e.g #781892.
> 
> Good point, thanks for the reminder.
> 
> So how do we move forward? Report to gcc or fiddle with our machines?
> 
Talk to mips people on the porter list so they can look into this?

Cheers,
Julien
-- 
Julien Cristau  
Logilab http://www.logilab.fr/
Informatique scientifique & gestion de connaissances

Bug#811471: zopfli: contains sample code from the RFC without any attribution

[Julian Andres Klode]

Source: zopfli
Severity: serious
Tags: upstream
Control: forwarded -1 https://github.com/google/zopfli/issues/88

The CRC code used in gzip_container.c comes almost directly from the RFC 1952, 
except for the naming conventions and some additional consting. 
Even the comments are copied.

The RFC 1952 has the following license:

"Permission is granted to copy and distribute this document for any
purpose and without charge, including translations into other
languages and incorporation into compilations, provided that the
copyright notice and this notice are preserved, and that any
substantive changes or deletions from the original are clearly
marked."

and copyright
Copyright (c) 1996 L. Peter Deutsch

There does not appear to be any exception for code anywhere, as such the
code must likely be considered non-free and incompatible with the Apache
license.

In any case, the file also does not consist of code solely owned by
Google, AFAICT.

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

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

-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.

When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to (`inline'). Thank you.

Processed: zopfli: contains sample code from the RFC without any attribution

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/google/zopfli/issues/88
Bug #811471 [src:zopfli] zopfli: contains sample code from the RFC without any 
attribution
Set Bug forwarded-to-address to 'https://github.com/google/zopfli/issues/88'.

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

Bug#811470: mdp: FTBFS: TypeError: Call constructor takes either 0 or 3 positional arguments

[Chris Lamb]

Source: mdp
Version: 3.3+git19-g4ec2f29-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

mdp fails to build from source in unstable/amd64:

  [..]

  _pytest.python:1546: in parsefactories
  >   holderobj = node_or_obj.obj
  _pytest.python:205: in fget
  >   self._obj = obj = self._getobj()
  _pytest.python:344: in _getobj
  >   return self._memoizedcall('_obj', self._importtestmodule)
  _pytest.main:287: in _memoizedcall
  >   ???
  _pytest.python:353: in _importtestmodule
  >   mod = self.fspath.pyimport(ensuresyspath=True)
  py._path.local:532: in pyimport
  >   ???
  :969: in _find_and_load
  >   ???
  :954: in _find_and_load_unlocked
  >   ???
  :892: in _find_spec
  >   ???
  :873: in _find_spec_legacy
  >   ???
  _pytest.assertion.rewrite:136: in find_module
  >   ???
  _pytest.assertion.rewrite:206: in _rewrite_test
  >   ???
  _pytest.assertion.rewrite:259: in rewrite_asserts
  >   ???
  _pytest.assertion.rewrite:370: in run
  >   ???
  /usr/lib/python3.5/ast.py:245: in visit
  >   return visitor(node)
  _pytest.assertion.rewrite:448: in visit_Assert
  >   ???
  /usr/lib/python3.5/ast.py:245: in visit
  >   return visitor(node)
  _pytest.assertion.rewrite:572: in visit_Compare
  >   ???
  /usr/lib/python3.5/ast.py:245: in visit
  >   return visitor(node)
  _pytest.assertion.rewrite:563: in visit_Attribute
  >   ???
  /usr/lib/python3.5/ast.py:245: in visit
  >   return visitor(node)
  _pytest.assertion.rewrite:434: in generic_visit
  >   ???
  _pytest.assertion.rewrite:397: in display
  >   ???
  _pytest.assertion.rewrite:403: in helper
  >   ???
  E   TypeError: Call constructor takes either 0 or 3 positional arguments
  ___ ERROR collecting test_scikits.py 
___
  _pytest.runner:121: in __init__
  >   ???
  _pytest.main:366: in _memocollect
  >   ???
  _pytest.main:287: in _memoizedcall
  >   ???
  _pytest.main:366: in 
  >   ???
  _pytest.python:347: in collect
  >   self.session._fixturemanager.parsefactories(self)
  _pytest.python:1546: in parsefactories
  >   holderobj = node_or_obj.obj
  _pytest.python:205: in fget
  >   self._obj = obj = self._getobj()
  _pytest.python:344: in _getobj
  >   return self._memoizedcall('_obj', self._importtestmodule)
  _pytest.main:287: in _memoizedcall
  >   ???
  _pytest.python:353: in _importtestmodule
  >   mod = self.fspath.pyimport(ensuresyspath=True)
  py._path.local:532: in pyimport
  >   ???
  :969: in _find_and_load
  >   ???
  :954: in _find_and_load_unlocked
  >   ???
  :892: in _find_spec
  >   ???
  :873: in _find_spec_legacy
  >   ???
  _pytest.assertion.rewrite:136: in find_module
  >   ???
  _pytest.assertion.rewrite:206: in _rewrite_test
  >   ???
  _pytest.assertion.rewrite:259: in rewrite_asserts
  >   ???
  _pytest.assertion.rewrite:370: in run
  >   ???
  /usr/lib/python3.5/ast.py:245: in visit
  >   return visitor(node)
  _pytest.assertion.rewrite:448: in visit_Assert
  >   ???
  /usr/lib/python3.5/ast.py:245: in visit
  >   return visitor(node)
  _pytest.assertion.rewrite:572: in visit_Compare
  >   ???
  /usr/lib/python3.5/ast.py:245: in visit
  >   return visitor(node)
  _pytest.assertion.rewrite:434: in generic_visit
  >   ???
  _pytest.assertion.rewrite:397: in display
  >   ???
  _pytest.assertion.rewrite:403: in helper
  >   ???
  E   TypeError: Call constructor takes either 0 or 3 positional arguments
  ___ ERROR collecting test_svm_classifier.py 

  _pytest.runner:121: in __init__
  >   ???
  _pytest.main:366: in _memocollect
  >   ???
  _pytest.main:287: in _memoizedcall
  >   ???
  _pytest.main:366: in 
  >   ???
  _pytest.python:347: in collect
  >   self.session._fixturemanager.parsefactories(self)
  _pytest.python:1546: in parsefactories
  >   holderobj = node_or_obj.obj
  _pytest.python:205: in fget
  >   self._obj = obj = self._getobj()
  _pytest.python:344: in _getobj
  >   return self._memoizedcall('_obj', self._importtestmodule)
  _pytest.main:287: in _memoizedcall
  >   ???
  _pytest.python:353: in _importtestmodule
  >   mod = self.fspath.pyimport(ensuresyspath=True)
  py._path.local:532: in pyimport
  >   ???
  :969: in _find_and_load
  >   ???
  :954: in _find_and_load_unlocked
  >   ???
  :892: in _find_spec
  >   ???
  :873: in _find_spec_legacy
  >   ???
  _pytest.assertion.rewrite:136: in find_module
  >   ???
  _pytest.assertion.rewrite:206: in _rewrite_test
  >   ???
  _pytest.assertion.rewrite:259: in rewrite_asserts
  >   ???
  _pytest.assertion.rewrite:370: in run
  >   ???
  /usr/lib/python3.5/ast.py:245: in visit
  >   return visitor(node)
  _pytest.assertion.rewrite:448: in visit_Assert
  >   ???
  /usr/lib/python3.5/ast.py:245: in visit
  >   return

Bug#811469: isomd5sum: FTBFS: cc: error: libcheckisomd5.a: No such file or directory

[Chris Lamb]

Source: isomd5sum
Version: 1:1.1.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

isomd5sum fails to build from source in unstable/amd64:

  [..]

   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: source package isomd5sum
  dpkg-buildpackage: source version 1:1.1.0-1
  dpkg-buildpackage: source distribution unstable
  dpkg-buildpackage: source changed by Ryan Finnie 
   dpkg-source --before-build isomd5sum-1.1.0
  dpkg-buildpackage: host architecture amd64
   fakeroot debian/rules clean
  dh clean --with=python2,python3
 dh_testdir
 debian/rules override_dh_auto_clean
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160119095649.Xd1jzyucCA/isomd5sum-1.1.0'
  rm -rf build
  /usr/bin/make clean
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20160119095649.Xd1jzyucCA/isomd5sum-1.1.0'
  rm -f *.o *.so *.pyc *.a .depend *~
  rm -f implantisomd5 checkisomd5 
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160119095649.Xd1jzyucCA/isomd5sum-1.1.0'
  dh_clean 
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160119095649.Xd1jzyucCA/isomd5sum-1.1.0'
 dh_clean
   debian/rules build
  dh build --with=python2,python3
 dh_testdir
 dh_update_autotools_config
 dh_auto_configure
 debian/rules override_dh_auto_build
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160119095649.Xd1jzyucCA/isomd5sum-1.1.0'
  py3versions: no X-Python3-Version in control file, using supported versions
  /usr/bin/make implantisomd5 checkisomd5
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20160119095649.Xd1jzyucCA/isomd5sum-1.1.0'
  cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Werror -D_GNU_SOURCE=1 -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE=1 -D_LARGEFILE64_SOURCE=1 -fPIC -I/usr/include/python3.5m 
-I/usr/include/python3.5m -c -O -o implantisomd5.o implantisomd5.c
  cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Werror -D_GNU_SOURCE=1 -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE=1 -D_LARGEFILE64_SOURCE=1 -fPIC -I/usr/include/python3.5m 
-I/usr/include/python3.5m -c -O -o libimplantisomd5.o libimplantisomd5.c
  ar rvU libimplantisomd5.a libimplantisomd5.o
  ar: creating libimplantisomd5.a
  a - libimplantisomd5.o
  cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Werror -D_GNU_SOURCE=1 -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE=1 -D_LARGEFILE64_SOURCE=1 -fPIC -I/usr/include/python3.5m 
-I/usr/include/python3.5m -c -O -o md5.o md5.c
  ar rvU libimplantisomd5.a md5.o
  a - md5.o
  cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Werror -D_GNU_SOURCE=1 -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE=1 -D_LARGEFILE64_SOURCE=1 -fPIC -I/usr/include/python3.5m 
-I/usr/include/python3.5m implantisomd5.o libimplantisomd5.a -lpopt 
-Wl,-z,relro -fPIC -o implantisomd5
  cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Werror -D_GNU_SOURCE=1 -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE=1 -D_LARGEFILE64_SOURCE=1 -fPIC -I/usr/include/python3.5m 
-I/usr/include/python3.5m -c -O -o checkisomd5.o checkisomd5.c
  cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Werror -D_GNU_SOURCE=1 -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE=1 -D_LARGEFILE64_SOURCE=1 -fPIC -I/usr/include/python3.5m 
-I/usr/include/python3.5m -c -O -o libcheckisomd5.o libcheckisomd5.c
  ar rvU libcheckisomd5.a libcheckisomd5.o
  ar: creating libcheckisomd5.a
  a - libcheckisomd5.o
  ar rvU libcheckisomd5.a md5.o
  a - md5.o
  cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Werror -D_GNU_SOURCE=1 -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE=1 -D_LARGEFILE64_SOURCE=1 -fPIC -I/usr/include/python3.5m 
-I/usr/include/python3.5m checkisomd5.o libcheckisomd5.a -lpopt -Wl,-z,relro 
-fPIC -o checkisomd5
  rm libimplantisomd5.o libcheckisomd5.o md5.o
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160119095649.Xd1jzyucCA/isomd5sum-1.1.0'
  set -e; \
  for python in python2.7 python3.4 python3.5; do \
mkdir -p build/$python; \
/usr/bin/make -C build/$python -f ../../Makefile 
VPATH=/home/lamby/temp/cdt.20160119095649.Xd1jzyucCA/isomd5sum-1.1.0 \
PYTHON=$python pyisomd5sum.so; \
  done
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20160119095649.Xd1jzyucCA/isomd5sum-1.1.0/build/python2.7'
  cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Werror -D_GNU_SOURCE=1 -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE=1 -D_LARGEFILE64_SOURCE=1 -fPIC -I/usr/include/python2.7 
-I/usr/inc

Bug#811468: nose: FTBFS: AttributeError: 'Derived' object has no attribute 'value'

[Chris Lamb]

Source: nose
Version: 1.3.6-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

nose fails to build from source in unstable/amd64:

  [..]

  test_defaults (test_xunit.TestOptions) ... ok
  test_file_from_environ (test_xunit.TestOptions) ... ok
  test_file_from_opt (test_xunit.TestOptions) ... ok
  test_dot_in_args (test_xunit.TestSplitId) ... ok
  test_grandchild_has_dot_in_args (test_xunit.TestSplitId) ... ok
  test_no_dot_in_args (test_xunit.TestSplitId) ... ok
  test_no_parenthesis (test_xunit.TestSplitId) ... ok
  test_addError (test_xunit.TestXMLOutputWithXML) ... FAIL
  test_addError_early (test_xunit.TestXMLOutputWithXML) ... ok
  test_addFailure (test_xunit.TestXMLOutputWithXML) ... FAIL
  test_addFailure_early (test_xunit.TestXMLOutputWithXML) ... ok
  test_addSuccess (test_xunit.TestXMLOutputWithXML) ... FAIL
  test_addSuccess_early (test_xunit.TestXMLOutputWithXML) ... ok
  test_non_utf8_error (test_xunit.TestXMLOutputWithXML) ... ok
  
  ==
  FAIL: Doctest: imported_tests.rst
  --
  Traceback (most recent call last):
File "/usr/lib/python3.5/doctest.py", line 2189, in runTest
  raise self.failureException(self.format_failure(new.getvalue()))
  AssertionError: Failed doctest test for imported_tests.rst
File 
"/home/lamby/temp/cdt.20160119095522.QC6hZTcOrV/nose-1.3.6/build/tests/functional_tests/doc_tests/test_issue145/imported_tests.rst",
 line 0
  
  --
  File 
"/home/lamby/temp/cdt.20160119095522.QC6hZTcOrV/nose-1.3.6/build/tests/functional_tests/doc_tests/test_issue145/imported_tests.rst",
 line 43, in imported_tests.rst
  Failed example:
  run(argv=argv) # doctest: +REPORT_NDIFF
  Differences (ndiff with -expected +actual):
package1 setup
test (package1.test_module.TestCase) ... ok
package1.test_module.TestClass.test_class ... ok
package1.test_module.test_function ... ok
package2c setup
  - test (package2c.test_module.TestCase) ... ok
  ? ^^  ^  ^
  + test (package2c.test_module.transplant_class..C) ... ok
  ?   ^^^  
package2c.test_module.TestClass.test_class ... ok
package2f setup
package2f.test_module.test_function ... ok

--
Ran 6 tests in ...s

OK
  --
  File 
"/home/lamby/temp/cdt.20160119095522.QC6hZTcOrV/nose-1.3.6/build/tests/functional_tests/doc_tests/test_issue145/imported_tests.rst",
 line 72, in imported_tests.rst
  Failed example:
  run(argv=argv) # doctest: +REPORT_NDIFF
  Differences (ndiff with -expected +actual):
package2c setup
  - test (package2c.test_module.TestCase) ... ok
  ? ^^  ^  ^
  + test (package2c.test_module.transplant_class..C) ... ok
  ?   ^^^  
package2c.test_module.TestClass.test_class ... ok

--
Ran 2 tests in ...s

OK
  --
  File 
"/home/lamby/temp/cdt.20160119095522.QC6hZTcOrV/nose-1.3.6/build/tests/functional_tests/doc_tests/test_issue145/imported_tests.rst",
 line 99, in imported_tests.rst
  Failed example:
  run(argv=argv) # doctest: +REPORT_NDIFF
  Differences (ndiff with -expected +actual):
package2c setup
  - test (package2c.test_module.TestCase) ... ok
  ? ^^  ^  ^
  + test (package2c.test_module.transplant_class..C) ... ok
  ?   ^^^  

--
Ran 1 test in ...s

OK
  
  
  ==
  FAIL: runTest (test_load_tests_from_test_case.TestLoadTestsFromTestCaseHook)
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20160119095522.QC6hZTcOrV/nose-1.3.6/build/tests/functional_tests/test_load_tests_from_test_case.py",
 line 52, in runTest
  self.assertEqual(line.strip(), expect.pop(0))
  AssertionError: 'test[34 
chars]case.NoFixturePlug.loadTestsFromTestCase..Derived)
 ... ERROR
  + test_value (test_load_tests_from_test_case.Derived) ... ERROR
  
   >> begin captured stdout << -
  o

Bug#811465: python-falcon: FTBFS: KeyError: 'logged_in'

[Chris Lamb]

Source: python-falcon
Version: 0.3.0-4
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

python-falcon fails to build from source in unstable/amd64:

  [..]

  tests.test_wsgi_errors.TestWSGIError.test_responder_logged_bytestring ... ok
  tests.test_wsgi_errors.TestWSGIError.test_responder_logged_unicode ... SKIP: 
Test only applies to Python 2
  
  ==
  ERROR: tests.test_cookies.TestCookies.test_request_cookie_parsing
  --
  testtools.testresult.real._StringException: Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20160119095118.NxQSMaNdZb/python-falcon-0.3.0/tests/test_cookies.py",
 line 144, in test_request_cookie_parsing
  self.assertEqual("no", req.cookies["logged_in"])
  KeyError: 'logged_in'
  
  
  --
  Ran 334 tests in 1.660s
  
  FAILED (SKIP=3, errors=1)
  debian/rules:27: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 1
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160119095118.NxQSMaNdZb/python-falcon-0.3.0'
  debian/rules:11: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


python-falcon.0.3.0-4.unstable.amd64.log.txt.gz
Description: Binary data

Bug#811462: FTBFS: test failure when updating ruby-net-ssh to 3.0.1

[Pirate Praveen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

package: ruby-net-ssh-multi
version: 1.2.1-1
severity: serious
justification: it is blocking ruby-net-ssh update

With ruby-net-ssh 3.0.1-1 in experimental, ruby-net-ssh fails to build
with following test failure

RUBYLIB=/home/pravi/forge/debian/git/pkg-ruby-extras/ruby-net-ssh-multi/
debian/ruby-net-ssh-multi/usr/lib/ruby/vendor_ruby:.
rake2.2 -f debian/ruby-tests.rake
/usr/bin/ruby2.2 -I"test"
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb"
"test/channel_test.rb" "test/multi_test.rb" "test/server_test.rb"
"test/session_actions_test.rb" "test/session_test.rb" -v
Run options: -v --seed 27463

# Running:

..E.
...

   1) session that cannot authenticate adds host to exception message
  NameError: uninitialized constant Timeout

/home/pravi/forge/debian/git/pkg-ruby-extras/ruby-net-ssh-multi/debian/r
uby-net-ssh-multi/usr/lib/ruby/vendor_ruby/net/ssh/multi/server.rb:191:i
n
`rescue in new_session'

/home/pravi/forge/debian/git/pkg-ruby-extras/ruby-net-ssh-multi/debian/r
uby-net-ssh-multi/usr/lib/ruby/vendor_ruby/net/ssh/multi/server.rb:183:i
n
`new_session'

/home/pravi/forge/debian/git/pkg-ruby-extras/ruby-net-ssh-multi/test/ser
ver_test.rb:107:in
`test_session_that_cannot_authenticate_adds_host_to_exception_message'
  /usr/lib/ruby/vendor_ruby/minitest/test.rb:108:in `block (3
levels) in run'
  /usr/lib/ruby/vendor_ruby/minitest/test.rb:205:in
`capture_exceptions'
  /usr/lib/ruby/vendor_ruby/minitest/test.rb:105:in `block (2
levels) in run'
  /usr/lib/ruby/vendor_ruby/minitest/test.rb:256:in `time_it'
  /usr/lib/ruby/vendor_ruby/minitest/test.rb:104:in `block in ru
n'
  /usr/lib/ruby/vendor_ruby/minitest.rb:334:in `on_signal'
  /usr/lib/ruby/vendor_ruby/minitest/test.rb:276:in
`with_info_handler'
  /usr/lib/ruby/vendor_ruby/minitest/test.rb:103:in `run'
  /usr/lib/ruby/vendor_ruby/minitest.rb:781:in `run_one_method'
  /usr/lib/ruby/vendor_ruby/minitest.rb:308:in `run_one_method'
  /usr/lib/ruby/vendor_ruby/minitest.rb:296:in `block (2
levels) in run'
  /usr/lib/ruby/vendor_ruby/minitest.rb:295:in `each'
  /usr/lib/ruby/vendor_ruby/minitest.rb:295:in `block in run'
  /usr/lib/ruby/vendor_ruby/minitest.rb:334:in `on_signal'
  /usr/lib/ruby/vendor_ruby/minitest.rb:321:in `with_info_handle
r'
  /usr/lib/ruby/vendor_ruby/minitest.rb:294:in `run'
  /usr/lib/ruby/vendor_ruby/minitest.rb:155:in `block in __run'
  /usr/lib/ruby/vendor_ruby/minitest.rb:155:in `map'
  /usr/lib/ruby/vendor_ruby/minitest.rb:155:in `__run'
  /usr/lib/ruby/vendor_ruby/minitest.rb:129:in `run'
  #
debian/ruby-net-ssh-multi/usr/lib/ruby/vendor_ruby/net/ssh/multi/server.
rb:191
  #
debian/ruby-net-ssh-multi/usr/lib/ruby/vendor_ruby/net/ssh/multi/server.
rb:183
  # test/server_test.rb:107
  # /usr/lib/ruby/vendor_ruby/minitest/test.rb:108
  # /usr/lib/ruby/vendor_ruby/minitest/test.rb:205
  # /usr/lib/ruby/vendor_ruby/minitest/test.rb:105
  # /usr/lib/ruby/vendor_ruby/minitest/test.rb:256
  # /usr/lib/ruby/vendor_ruby/minitest/test.rb:104
  # /usr/lib/ruby/vendor_ruby/minitest.rb:334
  # /usr/lib/ruby/vendor_ruby/minitest/test.rb:276
  # /usr/lib/ruby/vendor_ruby/minitest/test.rb:103
  # /usr/lib/ruby/vendor_ruby/minitest.rb:781
  # /usr/lib/ruby/vendor_ruby/minitest.rb:308
  # /usr/lib/ruby/vendor_ruby/minitest.rb:296
  # /usr/lib/ruby/vendor_ruby/minitest.rb:295
  # /usr/lib/ruby/vendor_ruby/minitest.rb:295
  # /usr/lib/ruby/vendor_ruby/minitest.rb:334
  # /usr/lib/ruby/vendor_ruby/minitest.rb:321
  # /usr/lib/ruby/vendor_ruby/minitest.rb:294
  # /usr/lib/ruby/vendor_ruby/minitest.rb:155
  # /usr/lib/ruby/vendor_ruby/minitest.rb:155
  # /usr/lib/ruby/vendor_ruby/minitest.rb:155
  # /usr/lib/ruby/vendor_ruby/minitest.rb:129
  # /usr/lib/ruby/vendor_ruby/minitest.rb:56

Finished in 0.047746s, 1822.1248 runs/s, 4670.5037 assertions/s.
87 runs, 223 assertions, no failures, 1 error, no skips

Failed Tests:

rake
TEST=/home/pravi/forge/debian/git/pkg-ruby-extras/ruby-net-ssh-multi/tes
t/server_test.rb
TESTOPTS="--name=test_session_that_cannot_authenticate_adds_host_to_exce
ption_message"

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWnfbtAAoJEM4fnGdFEsIqQiAP/jY9WsFu7JQJdwsH9qoaZ4Wf
1j6JL8V8IdN5biIAvO2+srgLjWoupIdp8Olbc1eWM1AP9u+xlyzII1dzdlBFcqSe
DLnmm6V3OkN+mzMpukpbN1nYxQnOF4SVMSDsOFzR7FkFz7knv3J2UH7AnlmayucX
j+DnqpONAhVd2Jv8VkTCyBwVB1nEW0bAHlTvEYyNlkXz8uEykUc6mWm5PbbyXyF0
anfg5u/NJ3B4WoeY8uZyZIpstD3Oc2VrIHIKiXWUpz/XkoU4DqfwlG3pcC8Y+2j0
YAq+hnEZUyIXqf3w+6IcuMhqEkcY9+BTyasjZvz5tbc+Je8wk0iC/eWm+GUPM/sv
sH8LVQmDszoztU8lZ4W6/Vd/jSMk5gqF3eN/2ceqPeItiwE2b+7tW9sqv7k0wnWK
yZn6bVaExzeLKl2liEddxUHXHAXpQRcC73uRC97RNjK94hqxSTFOunkuiW24Ab4d
mNoANHjcybq

Bug#810990: libxmlrpcpp-dev: /usr/include/base64.h already shipped by heimdal-dev

[Jochen Sprickerhof]

Hi,

I've pushed changes to libxmlrpcpp-dev to move the base64.h to
/usr/include/xmlrpcpp [1]. Would it be ok if I reassign this to
libxmlrpcpp-dev and close it, or should we split it, to leave one open
for heimdal-dev?

* Wookey  [2016-01-16 03:26]:
> Debian now has this xmplrpc c++ implementation: 
> https://tracker.debian.org/pkg/xmlrpc-c
> maybe ros-ros-comm could just use that? I've not looked to see how well the 
> APIs match up. 

ROS upstream is currently working on ROS2, replacing most of the core
system, so I hope this gets resolved with that.

Cheers Jochen

[1] 
http://anonscm.debian.org/cgit/debian-science/packages/ros/ros-ros-comm.git/commit/?id=d363634441477378be652ef328c12cf7bb3c6995


signature.asc
Description: PGP signature

Bug#810645: marked as done (python-pysam: FTBFS: TypeError: can't pickle Cython.Compiler.FlowControl.NameAssignment objects)

[Debian Bug Tracking System]

Your message dated Tue, 19 Jan 2016 03:40:19 -0500
with message-id <2047e79e-3a3a-4d02-a4ac-d2f3c1d5e...@kitterman.com>
and subject line Re: [Help] Bug#810645: python-pysam: FTBFS: TypeError: can't 
pickle Cython.Compiler.FlowControl.NameAssignment objects
has caused the Debian Bug report #810645,
regarding python-pysam: FTBFS: TypeError: can't pickle 
Cython.Compiler.FlowControl.NameAssignment objects
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.)


-- 
810645: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810645
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pysam
Version: 0.8.4+ds-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

python-pysam fails to build from source in unstable/amd64:

  [..]

  running build_ext
  cythoning pysam/csamtools.pyx to pysam/csamtools.c
  Traceback (most recent call last):
File "setup.py", line 518, in 
  dist = setup(**metadata)
File "/usr/lib/python3.5/distutils/core.py", line 148, in setup
  dist.run_commands()
File "/usr/lib/python3.5/distutils/dist.py", line 955, in run_commands
  self.run_command(cmd)
File "/usr/lib/python3.5/distutils/dist.py", line 974, in run_command
  cmd_obj.run()
File "/usr/lib/python3.5/distutils/command/build.py", line 135, in run
  self.run_command(cmd_name)
File "/usr/lib/python3.5/distutils/cmd.py", line 313, in run_command
  self.distribution.run_command(command)
File "/usr/lib/python3.5/distutils/dist.py", line 974, in run_command
  cmd_obj.run()
File "/usr/lib/python3/dist-packages/Cython/Distutils/build_ext.py", line 
164, in run
  _build_ext.build_ext.run(self)
File "/usr/lib/python3.5/distutils/command/build_ext.py", line 338, in run
  self.build_extensions()
File "/usr/lib/python3/dist-packages/Cython/Distutils/build_ext.py", line 
171, in build_extensions
  ext.sources = self.cython_sources(ext.sources, ext)
File "/usr/lib/python3/dist-packages/Cython/Distutils/build_ext.py", line 
320, in cython_sources
  full_module_name=module_name)
File "/usr/lib/python3/dist-packages/Cython/Compiler/Main.py", line 677, in 
compile
  return compile_single(source, options, full_module_name)
File "/usr/lib/python3/dist-packages/Cython/Compiler/Main.py", line 630, in 
compile_single
  return run_pipeline(source, options, full_module_name)
File "/usr/lib/python3/dist-packages/Cython/Compiler/Main.py", line 487, in 
run_pipeline
  err, enddata = Pipeline.run_pipeline(pipeline, source)
File "/usr/lib/python3/dist-packages/Cython/Compiler/Pipeline.py", line 
328, in run_pipeline
  data = phase(data)
File "/usr/lib/python3/dist-packages/Cython/Compiler/Pipeline.py", line 53, 
in generate_pyx_code_stage
  module_node.process_implementation(options, result)
File "/usr/lib/python3/dist-packages/Cython/Compiler/ModuleNode.py", line 
118, in process_implementation
  self.generate_c_code(env, options, result)
File "/usr/lib/python3/dist-packages/Cython/Compiler/ModuleNode.py", line 
339, in generate_c_code
  self.body.generate_function_definitions(env, code)
File "/usr/lib/python3/dist-packages/Cython/Compiler/Nodes.py", line 436, 
in generate_function_definitions
  stat.generate_function_definitions(env, code)
File "/usr/lib/python3/dist-packages/Cython/Compiler/Nodes.py", line 436, 
in generate_function_definitions
  stat.generate_function_definitions(env, code)
File "/usr/lib/python3/dist-packages/Cython/Compiler/Nodes.py", line 3056, 
in generate_function_definitions
  FuncDefNode.generate_function_definitions(self, env, code)
File "/usr/lib/python3/dist-packages/Cython/Compiler/Nodes.py", line 1923, 
in generate_function_definitions
  self.generate_function_body(env, code)
File "/usr/lib/python3/dist-packages/Cython/Compiler/Nodes.py", line 1681, 
in generate_function_body
  self.body.generate_execution_code(code)
File "/usr/lib/python3/dist-packages/Cython/Compiler/Nodes.py", line 442, 
in generate_execution_code
  stat.generate_execution_code(code)
File "/usr/lib/python3/dist-packages/Cython/Compiler/Nodes.py", line 5852, 
in generate_execution_code
  if_clause.generate_execution_code(code, end_label, is_last=i == last)
File "/usr/lib/python3/dist-packages/Cython/Compiler/Nodes.py", line 5895, 
in generate_execution_code
  self.body.generate_execution_code(cod

Bug#746580: sysv-rc: [patch] much improved update-rc.d integration w/ systemd

[Martin Pitt]

Control: severity -1 normal

Florian Schlichting [2015-03-21  0:47 +0100]:
> I think the severity should be raised - the working of update-rc.d ought
> to be improved for jessie.

As that didn't happen, I'm downgrading this back to normal.

Sorry for the late response -- we just mass-reassigned bugs to the
init-system-helpers package as update-rc.d, service, and invoke-rc.d
moved there yesterday.

Martin
-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)