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

[Andreas Metzler]

On 2016-01-19 Doug Torrance  wrote:
> On 01/19/2016 02:41 PM, Andreas Metzler wrote:
[...]
>> 2a Patch the source to fix back the symbol versioning to
>> LIBWRASTER3
[...]
> Option 2a sounds good to me.  Feel free to revert my last few commits if you
> get to it before I do.

Thanks for preparing for my commit in advance. How about opening a
experimental branch for the package split, to spare us the commit/revert
cycle if we find another urgent issue?

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

I think 2a is also the best option for upstream, not a soname bump.
Perhaps a timely 0.95.7.1 issue?

BTW: Do you have admin privileges for the pkg-wmaker-devel list? If so
would you mind disabling addition of a the [Pkg-wmaker-devel] tag to 
the subject?

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'

Bug#812072: module 'subprocess' has no attribute 'mswindows'

[Andreas Beckmann]

Control: tag -1 sid stretch
Control: block 810136 with -1

On Wed, 20 Jan 2016 16:46:24 +0800 Thomas Goirand  wrote:
> Package: python3-cmd2
> Version: 0.6.7-2

> AttributeError: module 'subprocess' has no attribute 'mswindows'
> 
> Obviously, I'm not running mswindows... :)

seems to be related to python 3.5:

$ python3.4 -m cmd2
$ python3.5 -m cmd2
Traceback (most recent call last):
  File "/usr/lib/python3.5/runpy.py", line 184, in _run_module_as_main
"__main__", mod_spec)
  File "/usr/lib/python3.5/runpy.py", line 85, in _run_code
exec(code, run_globals)
  File "/usr/lib/python3/dist-packages/cmd2.py", line 181, in 
if subprocess.mswindows:
AttributeError: module 'subprocess' has no attribute 'mswindows'


Andreas

Processed: Re: module 'subprocess' has no attribute 'mswindows'

[Debian Bug Tracking System]

Processing control commands:

> tag -1 sid stretch
Bug #812072 [python3-cmd2] module 'subprocess' has no attribute 'mswindows'
Added tag(s) sid and stretch.
> block 810136 with -1
Bug #810136 [release.debian.org] transition: python3-defaults (python3.5 as 
default python3)
810136 was not blocked by any bugs.
810136 was not blocking any bugs.
Added blocking bug(s) of 810136: 812072

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

Bug#812153: [Pkg-utopia-maintainers] Bug#812153: Bug#812153: policykit-1: allows ordinary users to mount filesystems

[Christoph Anton Mitterer]

On Thu, 2016-01-21 at 04:13 +0100, Michael Biebl wrote:
> This behaviour has been since 2000 or so, since at least the
> introduction of hal and pmount.

Then one has still some 30 years before where it has been different...


> You don't gain anything security wise by not allowing removable media
> to
> be mounted. The only thing it will cause for sure is inconvenience.

As I told you before, this is not true,.. you may have easily have
secured terminals where people can log in, but where they cannot e.g.
physically access such devices.


> Please don't reopen anymore, or I'll ask bts listmaster to block your
> address.

Ah quite funny... "do as I want... or I use dictatorship methods"...

It's quite disturbing when a real issue is reported, that this is
simply done away by threatening people.

How sad to see, that certain cabals that pursue to convert Debian to a
desktop/tablet only OS succeed since they simply hold all the necessary
organisational positions and quite successfully push out any other DDs
that try to resist that agenda...

smime.p7s
Description: S/MIME cryptographic signature

Bug#812153: marked as done (policykit-1: allows ordinary users to mount filesystems)

[Debian Bug Tracking System]

Your message dated Thu, 21 Jan 2016 04:13:10 +0100
with message-id <56a04cc6.5030...@debian.org>
and subject line Re: [Pkg-utopia-maintainers] Bug#812153: Bug#812153: 
policykit-1: allows ordinary users to mount filesystems
has caused the Debian Bug report #812153,
regarding policykit-1: allows ordinary users to mount filesystems
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.)


-- 
812153: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812153
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: policykit-1
Version: 0.105-14.1
Severity: grave
Tags: security


Hi.

Apparently polkit (or at least I guess it's ultimately the offender here,
if not please reassign accordingly) allows ordinary users to mount any
filesystem per default.
E.g. such connected via USB, or set up via losetup.
At least that works so e.g. via nautilus,.. wich disturbingly seem to do
that even automatically though nothing from that attached device/fs was
accessed... o.O

Since such filesystems may have totally different user/group owners
or even none and be world wrtiable (e.g. with *FAT filesystems) and since
they may contain any sensitve data frm keys to secret source code, etc.,
this is a grave security breach.


May not matter that much on a notebook or tablet, but one should hope that
even nowadays Debian isn't just made for those people,.. and there are
perhaps still some other systems out there were devices with such filesystems
are connected and where uses have direct and/or remote accesses, but where
they should not be able to mount any fs.

Since it has been the long standing behaviour of UNIX/Linux ever, that normal
users cannot mountfilesystems unless explicitly allowed, please revert to
that behaviour.

Cheers,
Chris.
--- End Message ---
--- Begin Message ---
Am 21.01.2016 um 03:52 schrieb Christoph Anton Mitterer:
> Control: reopen -1
> Control: reassign -1 udisks2
> 
> On Thu, 2016-01-21 at 03:39 +0100, Michael Biebl wrote:
>> Policykit is the wrong package. What you look for is udisks, most
>> likely.
> I went through /usr/share/polkit-
> 1/actions/org.freedesktop.udisks2.policy but all settings there seem to
> be auth_admin and none seems to be specifically for removable devices.
> 
>>  And what you say is not true, only removable drives  are
>> automounted, and that is deliberate and not going to change.
> It's still breaking long standing behaviour. You cannot just add such
> security regressions and call it "deliberate" thus "not going to
> change".

This behaviour has been since 2000 or so, since at least the
introduction of hal and pmount.

> Especially since any device can be removable... people connect normal
> hard disks via USB/SATA gateways, which are detected as such as well.
> 
> If Debian introduces behaviour that likely allows access to data where
> normal users shouldn't have access, than this should be an opt-in.

You don't gain anything security wise by not allowing removable media to
be mounted. The only thing it will cause for sure is inconvenience.

> Thus reopening.

Please don't reopen anymore, or I'll ask bts listmaster to block your
address.

Michael


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

Bug#808126: marked as done (simpletal: maintainer address bounces)

[Debian Bug Tracking System]

Your message dated Thu, 21 Jan 2016 01:22:35 +
with message-id 
and subject line Bug#808126: fixed in simpletal 4.1-9
has caused the Debian Bug report #808126,
regarding simpletal: maintainer address bounces
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.)


-- 
808126: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808126
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: simpletal
Severity: serious
Tags: sid

The maintainer address for simpletal bounces, see below.

Ansgar

Mail Delivery System  writes:
> This message was created automatically by mail delivery software.
>
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es) failed:
>
>   jen...@rulim.de
> SMTP error from remote mail server after RCPT TO::
> host aspmx.l.google.com [2607:f8b0:400e:c00::1b]:
> 550-5.1.1 The email account that you tried to reach does not exist. 
> Please try
> 550-5.1.1 double-checking the recipient's email address for typos or
> 550-5.1.1 unnecessary spaces. Learn more at
> 550 5.1.1  https://support.google.com/mail/answer/6596 
> wi4si16656301pab.220 - gsmtp
>
> -- This is a copy of the message, including all the headers. --
>
[...]
> From: Debian FTP Masters 
> To: Igor Stroh , Mattia Rizzolo 
[...]
> Subject: simpletal_4.1-8_source.changes ACCEPTED into unstable
> Message-Id: 
> Date: Tue, 15 Dec 2015 00:35:41 +
>
[...]
> Maintainer: Igor Stroh 
> Changed-By: Mattia Rizzolo 
--- End Message ---
--- Begin Message ---
Source: simpletal
Source-Version: 4.1-9

We believe that the bug you reported is fixed in the latest version of
simpletal, 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.
Mattia Rizzolo  (supplier of updated simpletal 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: Thu, 21 Jan 2016 00:46:58 +
Source: simpletal
Binary: python-simpletal
Architecture: source
Version: 4.1-9
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Mattia Rizzolo 
Description:
 python-simpletal - Simple TAL, TALES and METAL implementation
Closes: 808126
Changes:
 simpletal (4.1-9) unstable; urgency=medium
 .
   * QA upload.
   * debian/control:
 + Orphan the package.  Closes: #808126
 + Move the git repository to collab-maint.
Checksums-Sha1:
 e94cfb2d3ce39df90e2ec8fb4df520384517ccb5 1873 simpletal_4.1-9.dsc
 676d292a486bf92dc6c8aa4fd3d1e0cd6a295fdd 3440 simpletal_4.1-9.debian.tar.xz
Checksums-Sha256:
 a7ca7e74c220e61afc0eef5fe830aa0d8c25629339a417a8397eb84586250ecb 1873 
simpletal_4.1-9.dsc
 38c078009beee25ff76870588b0e4ffb88eb423694a876dc121bbb6f05632404 3440 
simpletal_4.1-9.debian.tar.xz
Files:
 2975263a60218ef1ac0df3f962af1181 1873 python optional simpletal_4.1-9.dsc
 2a286e39e95ab753d65185096667f863 3440 python optional 
simpletal_4.1-9.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWoCtXAAoJEEsEP825REVAeAgQAMnAzzmGtkVbyk5Cdg0ez8KB
AFDu30uUewDIZYIRNbv4Tp3pDuQHX1dUk3vWC5+lH7keyB3NMttIrjWuSVwQeGZ1
s3QC3B67sSYQPduXa9mEfEjmqvf8H0Vnijtblq7FvT7IiZSBixaQTEeQhh+LxwdJ
0i19jraBYDfm/0e2QwxU3vvWaqJIGMsOt1vmxh/ttwEJUIK/pk27N4q3LL/9QQ5f
GRl/JNiznRoncjJVbpK+Aw/YUK7I3wKYJXsBj9B/kx5nPR7EZJUHE5NOLezlpOro
mbIs1NA6xMGP7IMCH+2Y4AYzXBopxqbK+DjNh+eQoBcmR+4VFWQRezsNpNUidpCo
PUTQ62l8dsD/T2/ZFLH9Ua2qFz90GFvxCYfArE0snopL7VBxS8BFfZa5Va6J8GF4
dVHLIMNCh3eqbEdcuNUKBuVB25FDn45XKEt4a1Ikag0trHbh0OZhTe+jBx8/a2As
BNKXvM4vh8w40NQnRBsH2GW/g3DtUy0Vuggq81I3ZuGxsaZCaFxK7Kzj/XKsgs9k
9Hl78QWdRry2xuXjwHQEBM5cZekqXBsDDZcHAP2SZpI2g1VhVKey2A5ZollGeGND
A7rtcxQbDFBGTiiSL3d6kPxMXLt4cs88ogIXaeZEYb6GgtvhHUnWDBDZBpRrmDYK
8iLk/yWimUn0F9ghhtVc
=5PFX
-END PGP SIGNATURE End Message ---

Bug#812153: [Pkg-utopia-maintainers] Bug#812153: Bug#812153: Bug#812153: policykit-1: allows ordinary users to mount filesystems

[Christoph Anton Mitterer]

On Thu, 2016-01-21 at 04:32 +0100, Michael Biebl wrote:
> Right, since we had removable media 30 years ago.
No but mounting filesystems.


> In such a very specialised situation you can easily lock down the
> configuration. For such a setup you will most likely need custom
> configuration anyway to be secure.
> A default configuration needs to usable by the majority of users.
The problem with that is:
AFAIU, when I override polkit rules, that it's really just the specific
rule that are overriden... and no the whole config file e.g.
org.freedesktop.udisks2.policy

While this makes at first since of course, it also means that one have
no real chance to go back to sane permissions unless one would track
any single change of /usr/share/polkit-
1/actions/org.freedesktop.udisks2.policy.
Of course one can override all rules that are there right now, but new
properties get added or existing ones removed, and then one's back to
insecure-per-default settings.


> There is no "real issue".
Maybe not for you, others may have tighter security constraints,
though. E.g. I wouldn't want to have everyone-may-access-everything
just it may seem convenient for some people and they set up their
systems like this.


>  Point.
> You are making a big fuss for nothing and wasting everyones time,
> mine
> included. I'm not willing to tolerate that.
Uhm I had understood that before.
Not-an-issue-for-you plus threatening people for whom it is - bug
solving by oppression (guess I should try that at the institute as well
=) ),...
So no need to point out and praise your position of power again.

Anyway,.. the bug is closed as you enforced it,.. perhaps it should be
marked wontfix?

Cheers,
Chris.

smime.p7s
Description: S/MIME cryptographic signature

Bug#812116: newly built initrd complains about missing init

[Harald Dunkel]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Yup.

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJWoGOcAAoJEAqeKp5m04HLqk8H/RLH14ZPiDgZr1yHFCyiGEPY
46snYvavBNa2JBjYZXdwynHTRS9oWApYPTgSAdNYhYJ2Kjbr838hiH9V/5Wv030q
yVofhD1bNm7sA1ynflMXdgvvDI8RemNRpmKflG7rRBeZfOHkDxgOXYiT0wNLaoDg
TmGv8PNzqIw83ioTXg/Q2M71aB0QrHes/HKjnfQI/Axak6P7AWOj/9tLqx7ApxAn
KKozOFtg1m8WeUzHaIHZ+Q/NaUmmDaM5CYQIXEgVdni2UoAUgrqdNcf9DYf/KwFw
P1OUD2BRT6lVRr3Q62gcPWKOavmcpXKzmm3hLuMRl98PrdCvJMwkXLeehUCks78=
=8I09
-END PGP SIGNATURE-

Bug#812153: policykit-1: allows ordinary users to mount filesystems

[Christoph Anton Mitterer]

Package: policykit-1
Version: 0.105-14.1
Severity: grave
Tags: security


Hi.

Apparently polkit (or at least I guess it's ultimately the offender here,
if not please reassign accordingly) allows ordinary users to mount any
filesystem per default.
E.g. such connected via USB, or set up via losetup.
At least that works so e.g. via nautilus,.. wich disturbingly seem to do
that even automatically though nothing from that attached device/fs was
accessed... o.O

Since such filesystems may have totally different user/group owners
or even none and be world wrtiable (e.g. with *FAT filesystems) and since
they may contain any sensitve data frm keys to secret source code, etc.,
this is a grave security breach.


May not matter that much on a notebook or tablet, but one should hope that
even nowadays Debian isn't just made for those people,.. and there are
perhaps still some other systems out there were devices with such filesystems
are connected and where uses have direct and/or remote accesses, but where
they should not be able to mount any fs.

Since it has been the long standing behaviour of UNIX/Linux ever, that normal
users cannot mountfilesystems unless explicitly allowed, please revert to
that behaviour.

Cheers,
Chris.

Bug#812153: marked as done (policykit-1: allows ordinary users to mount filesystems)

[Debian Bug Tracking System]

Your message dated Thu, 21 Jan 2016 03:39:56 +0100
with message-id <56a044fc.4070...@debian.org>
and subject line Re: [Pkg-utopia-maintainers] Bug#812153: policykit-1: allows 
ordinary users to mount filesystems
has caused the Debian Bug report #812153,
regarding policykit-1: allows ordinary users to mount filesystems
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.)


-- 
812153: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812153
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: policykit-1
Version: 0.105-14.1
Severity: grave
Tags: security


Hi.

Apparently polkit (or at least I guess it's ultimately the offender here,
if not please reassign accordingly) allows ordinary users to mount any
filesystem per default.
E.g. such connected via USB, or set up via losetup.
At least that works so e.g. via nautilus,.. wich disturbingly seem to do
that even automatically though nothing from that attached device/fs was
accessed... o.O

Since such filesystems may have totally different user/group owners
or even none and be world wrtiable (e.g. with *FAT filesystems) and since
they may contain any sensitve data frm keys to secret source code, etc.,
this is a grave security breach.


May not matter that much on a notebook or tablet, but one should hope that
even nowadays Debian isn't just made for those people,.. and there are
perhaps still some other systems out there were devices with such filesystems
are connected and where uses have direct and/or remote accesses, but where
they should not be able to mount any fs.

Since it has been the long standing behaviour of UNIX/Linux ever, that normal
users cannot mountfilesystems unless explicitly allowed, please revert to
that behaviour.

Cheers,
Chris.
--- End Message ---
--- Begin Message ---
Am 21.01.2016 um 03:33 schrieb Christoph Anton Mitterer:
> Package: policykit-1
> Version: 0.105-14.1
> Severity: grave
> Tags: security
> 
> 
> Hi.
> 
> Apparently polkit (or at least I guess it's ultimately the offender here,
> if not please reassign accordingly) allows ordinary users to mount any
> filesystem per default.

Policykit is the wrong package. What you look for is udisks, most
likely. And what you say is not true, only removable drives  are
automounted, and that is deliberate and not going to change.
So closing.


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

Bug#812153: [Pkg-utopia-maintainers] Bug#812153: policykit-1: allows ordinary users to mount filesystems

[Christoph Anton Mitterer]

Control: reopen -1
Control: reassign -1 udisks2

On Thu, 2016-01-21 at 03:39 +0100, Michael Biebl wrote:
> Policykit is the wrong package. What you look for is udisks, most
> likely.
I went through /usr/share/polkit-
1/actions/org.freedesktop.udisks2.policy but all settings there seem to
be auth_admin and none seems to be specifically for removable devices.

>  And what you say is not true, only removable drives  are
> automounted, and that is deliberate and not going to change.
It's still breaking long standing behaviour. You cannot just add such
security regressions and call it "deliberate" thus "not going to
change".

Especially since any device can be removable... people connect normal
hard disks via USB/SATA gateways, which are detected as such as well.

If Debian introduces behaviour that likely allows access to data where
normal users shouldn't have access, than this should be an opt-in.

Thus reopening.

smime.p7s
Description: S/MIME cryptographic signature

Processed: severity 798681 serious

[Debian Bug Tracking System]

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

> severity 798681 serious
Bug #798681 [src:cmd2] cmd2: Python 3.5 compatibility
Severity set to 'serious' from 'important'
>
End of message, stopping processing here.

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

Processed: Re: [Pkg-utopia-maintainers] Bug#812153: policykit-1: allows ordinary users to mount filesystems

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #812153 {Done: Michael Biebl } [policykit-1] policykit-1: 
allows ordinary users to mount filesystems
Bug reopened
Ignoring request to alter fixed versions of bug #812153 to the same values 
previously set
> reassign -1 udisks2
Bug #812153 [policykit-1] policykit-1: allows ordinary users to mount 
filesystems
Bug reassigned from package 'policykit-1' to 'udisks2'.
No longer marked as found in versions policykit-1/0.105-14.1.
Ignoring request to alter fixed versions of bug #812153 to the same values 
previously set

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

Processed: severity of 808730 is important

[Debian Bug Tracking System]

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

> severity 808730 important
Bug #808730 [stalin] stalin: CVE-2015-8697: Insecure use of temporary files
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Bug#812149: retext: program crash

[Erik]

Package: retext
Version: 5.3.0-1
Severity: grave
Justification: renders package unusable

Ran: retext docs/api.md and received the below output:

Traceback (most recent call last):
  File "/usr/share/retext/ReText/highlighter.py", line 129, in highlightBlock
if not self.dictionary.check(match.group(0)):
  File "/usr/lib/python3/dist-packages/enchant/__init__.py", line 634, in check
self._check_this()
  File "/usr/lib/python3/dist-packages/enchant/__init__.py", line 606, in 
_check_this
_EnchantObject._check_this(self,msg)
  File "/usr/lib/python3/dist-packages/enchant/__init__.py", line 176, in 
_check_this
raise Error(msg)
enchant.errors.Error: Dict unusable: the underlying C-library object has been 
freed.

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

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

Versions of packages retext depends on:
ii  python3-docutils0.12+dfsg-1
ii  python3-enchant 1.6.6-2
ii  python3-markdown2.6.5-1
ii  python3-markups 1.0.1-1
ii  python3-pygments2.0.1+dfsg-2
ii  python3-pyqt5   5.5.1+dfsg-3+b1
ii  python3-pyqt5.qtwebkit  5.5.1+dfsg-3+b1
pn  python3:any 

Versions of packages retext recommends:
ii  docutils-common   0.12+dfsg-1
ii  shared-mime-info  1.5-2

retext suggests no packages.

-- no debconf information

Bug#804455: marked as done (gsoap: FTBFS on mips/mipsel: Segmantation fault)

[Debian Bug Tracking System]

Your message dated Thu, 21 Jan 2016 04:37:15 +0100
with message-id <1453347435.15936.10.ca...@fysast.uu.se>
and subject line Bug#804455: fixed in gsoap 2.8.22-2
has caused the Debian Bug report #804455,
regarding gsoap: FTBFS on mips/mipsel: Segmantation fault
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.)


-- 
804455: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804455
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gsoap
Version: 2.8.22-1
Severity: serious
Control: block 797926 by -1

Hi,

Your package is failing to build on mips and mipsel with the
following error:
make[5]: Entering directory '/«PKGBUILDDIR»/gsoap/wsdl'
../../gsoap/src/soapcpp2 -SC -pwsdl -I. -I../../gsoap/import ./wsdl.h
soapcpp2: using both options -C and -S omits client/server code

**  The gSOAP code generator for C and C++, soapcpp2 release 2.8.22
**  Copyright (C) 2000-2015, Robert van Engelen, Genivia Inc.
**  All Rights Reserved. This product is provided "as is", without any warranty.
**  The soapcpp2 tool is released under one of the following licenses:
**  GPL or the commercial license by Genivia Inc.

Saving wsdlStub.h annotated copy of the source input
Saving wsdlH.h declarations to #include
Makefile:833: recipe for target 'wsdlC.cpp' failed
make[5]: *** [wsdlC.cpp] Segmentation fault


Kurt
--- End Message ---
--- Begin Message ---
Source: gsoap
Source-Version: 2.8.22-2

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

Debian distribution maintenance software
pp.
Mattias Ellert  (supplier of updated gsoap 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)


Format: 1.8
Date: Wed, 20 Jan 2016 21:30:22 +0100
Source: gsoap
Binary: libgsoap7 libgsoap-dev gsoap gsoap-doc libgsoap-dbg gsoap-dbg
Architecture: source amd64 all
Version: 2.8.22-2
Distribution: unstable
Urgency: medium
Maintainer: Mattias Ellert 
Changed-By: Mattias Ellert 
Description:
 gsoap  - Stub generators for gSOAP
 gsoap-dbg  - Debugging symbols for gSOAP stub generators
 gsoap-doc  - gSOAP documentation
 libgsoap-dbg - Debugging symbols for gSOAP libraries
 libgsoap-dev - Development libraries and headers for gSOAP
 libgsoap7  - Runtime libraries for gSOAP
Closes: 804455
Changes:
 gsoap (2.8.22-2) unstable; urgency=medium
 .
   * Introduce workaround for gcc optimization bug on mips and mipsel, add
 -fno-ipa-sra to CFLAGS and CXXFLAGS - see BTS #804536 (Closes: #804455)
   * Fix some compilation warnings
Checksums-Sha1:
 679a6146af64cb2e7761e762ab81881c5d92a90e 2140 gsoap_2.8.22-2.dsc
 9674d0b216b308e3a7e9a08d5005835a2faa3aae 11792 gsoap_2.8.22-2.debian.tar.xz
 c2586ee708862537e44dc393ac60b4112bedd904 2149648 gsoap-dbg_2.8.22-2_amd64.deb
 7f8fe5e630c28459b6d4ec29e84dd95eebb07b4a 3195224 gsoap-doc_2.8.22-2_all.deb
 dedbc5c6c2c97c0ba1c2e269ce3c5b8509d49b4b 719324 gsoap_2.8.22-2_amd64.deb
 952f0bfa1fdf0f2fccff5066043cb14932d1fd16 570330 libgsoap-dbg_2.8.22-2_amd64.deb
 afa483e2913cefc848be21fb30e0922ee3cb1a2d 206950 libgsoap-dev_2.8.22-2_amd64.deb
 f77f3aa83c29f973bf82888759bb6d7d6710402d 203744 libgsoap7_2.8.22-2_amd64.deb
Checksums-Sha256:
 56984332edb6e79c795ea7b3fb1ed4d944613a8004a8aab5874336e82a59ae14 2140 
gsoap_2.8.22-2.dsc
 1da02f47baf7c672b6eef89cf96702956ea0632bb73d50827fd55c3add6663ac 11792 
gsoap_2.8.22-2.debian.tar.xz
 9e6bfb88d348a3f135dee306407beec39afd6853bc99cbad84de81e1d9b2ed89 2149648 
gsoap-dbg_2.8.22-2_amd64.deb
 c22728878ba5db8320b785e79d2563aa139487f414c579c9a337f2706e96fef9 3195224 
gsoap-doc_2.8.22-2_all.deb
 5aa8b15b14b3f27ac873a8f9179603b15366d2f59fffb236a026ce80bf72aa81 719324 
gsoap_2.8.22-2_amd64.deb
 67307b11a6ccda66a8103bccefb1e714dd743d8705a1ed90163155f5ac9e82d4 570330 
libgsoap-dbg_2.8.22-2_amd64.deb
 93021ddc01adde0378bf76d1b07ec4db4d954eb891be7eb5234be24e9ffaba19 206950 
libgsoap-dev_2.8.22-2_amd64.deb
 0a9befa9959db74f839692d7f24c7a01d3e8d555992ca5205ac65ea7cefbaaa1 203744 
libgsoap7_2.8.22-2_amd64.deb
Files:
 9ac84ab98a40d4223477ee88743b5287 2140 devel optional gsoap_2.8.22-2.dsc
 

Bug#812153: [Pkg-utopia-maintainers] Bug#812153: Bug#812153: Bug#812153: policykit-1: allows ordinary users to mount filesystems

[Michael Biebl]

Am 21.01.2016 um 04:18 schrieb Christoph Anton Mitterer:
> On Thu, 2016-01-21 at 04:13 +0100, Michael Biebl wrote:
>> This behaviour has been since 2000 or so, since at least the
>> introduction of hal and pmount.
> 
> Then one has still some 30 years before where it has been different...

Right, since we had removable media 30 years ago.

> 
>> You don't gain anything security wise by not allowing removable media
>> to
>> be mounted. The only thing it will cause for sure is inconvenience.
> 
> As I told you before, this is not true,.. you may have easily have
> secured terminals where people can log in, but where they cannot e.g.
> physically access such devices.

In such a very specialised situation you can easily lock down the
configuration. For such a setup you will most likely need custom
configuration anyway to be secure.
A default configuration needs to usable by the majority of users.

>> Please don't reopen anymore, or I'll ask bts listmaster to block your
>> address.
> 
> Ah quite funny... "do as I want... or I use dictatorship methods"...
> 
> It's quite disturbing when a real issue is reported, that this is
> simply done away by threatening people.

There is no "real issue". Point.
You are making a big fuss for nothing and wasting everyones time, mine
included. I'm not willing to tolerate that.


Michael

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

Bug#812093: libimager-perl: FTBFS: Failed 1/65 test programs. 0/4481 subtests failed.

[Tony Cook]

On Wed, Jan 20, 2016 at 10:38:27PM +0200, Niko Tyni wrote:
> On Wed, Jan 20, 2016 at 02:42:04PM +0100, Chris Lamb wrote:
> > Source: libimager-perl
> > Version: 1.004+dfsg-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
> 
> > libimager-perl fails to build from source in unstable/amd64:
> 
> It broke with src:giflib 5.1.2-0.1 -> 5.1.1-0.2. Don't know
> why yet.
> 
> % perl -MImager -e 'Imager->new->read(type => "gif", file => 
> "GIF/testimg/expected.gif") or die'
> 
> dies with the new giflib but not the old one.
> 
> Cc'ing Matthias Klose as a heads-up, he uploaded 5.1.1-0.2.

The read failures are caused by a bug present in both 5.1.1 and 5.1.2,
partly fixed in giflib git at commit
ef0cb9b4be572262b49fbc26fb2348683f44a517.

A similar fix is required to DGifOpen() for Imager's GIF support to
work (reliably), reported upstream as
https://sourceforge.net/p/giflib/bugs/81/

Without the fix the Private member RunningBits isn't initialized,
leaving RunningBits as whatever happened to be in memory at that
point, so the check in DGifSetupDecompress() has a large chance of
failing with a D_GIF_ERR_READ_FAILED error.

Adding the initialization allows Imager to pass its tests.

That said, there is a bug in that test script, since its custom ok()
doesn't have a prototype, the tests on line 65 and 78 pass when they
should fail, leading to the crash on line 79 when it tries to compare
uninitialized images.

Adding a prototype fixes it, though I'll probably end up tossing the
custom code and using Test::More.

Tony

Processed: apt fails to distinguish between different Provides of different package versions

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:libjpeg9
Bug #812173 [apt] apt fails to distinguish between different Provides of 
different package versions
Added indication that 812173 affects src:libjpeg9

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

Bug#812173: apt fails to distinguish between different Provides of different package versions

[Johannes Schauer]

Package: apt
Version: 1.2
Severity: serious
Justification: Policy 7.5
Control: affects -1 + src:libjpeg9

Hi,

steps to reproduce for apt-get build-dep:

$ sudo debootstrap --include=equivs sid debian-apt-bug  
http://snapshot.debian.org/archive/debian/20160119T151500Z
$ echo deb-src http://snapshot.debian.org/archive/debian/20160119T151500Z 
sid main | sudo tee -a debian-apt-bug/etc/apt/sources.list
$ sudo chroot debian-apt-bug apt-get update
$ sudo chroot debian-apt-bug apt-get build-dep libjpeg9
Reading package lists... Done
Building dependency tree... Done
The following NEW packages will be installed:
  autoconf automake autopoint build-essential cpp cpp-5 dh-autoreconf g++ 
g++-5 gcc gcc-5 libasan2 libatomic1
  libc-dev-bin libc6-dev libcc1-0 libcilkrts5 libgcc-5-dev libisl15 libitm1 
liblsan0 libmpc3 libmpfr4 libmpx0
  libquadmath0 libsigsegv2 libstdc++-5-dev libtool libtsan0 libubsan0 
linux-libc-dev m4
0 upgraded, 32 newly installed, 0 to remove and 0 not upgraded.
Need to get 102 MB of archives.
[...]
Get:7 http://snapshot.debian.org/archive/debian/20160119T151500Z sid/main 
amd64 automake all 1:1.15-3 [735 kB]
[...]
Selecting previously unselected package automake.
Preparing to unpack .../automake_1%3a1.15-3_all.deb ...
Unpacking automake (1:1.15-3) ...
[...]
$ sudo chroot debian-apt-bug apt-get source --build libjpeg9
dpkg-checkbuilddeps: error: Unmet build dependencies: automake-1.14
dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; 
aborting
dpkg-buildpackage: warning: (Use -d flag to override.)
Build command 'cd libjpeg9-9a && dpkg-buildpackage -b -uc' failed.

As you can see from above, dpkg-checkbuilddeps and apt-get build-dep
disagree. This might be because unstable currently carries two automake
packages in different versions:

Package: automake
Source: automake-1.14
Version: 1:1.14.1-4
Architecture: all
Provides: automake-1.14, automaken
Depends: autoconf (>= 2.65), autotools-dev (>= 20020320.1)
Conflicts: automake (<< 1:1.4-p5-1), automake1.10-doc, automake1.5 (<< 
1.5-2), automake1.6 (<< 1.6.1-4)
Multi-Arch: foreign

Package: automake
Source: automake-1.15
Version: 1:1.15-3
Architecture: all
Provides: automake-1.15, automaken
Depends: autoconf (>= 2.65), autotools-dev (>= 20020320.1)
Suggests: autoconf-doc, gnu-standards
Conflicts: automake (<< 1:1.4-p5-1), automake1.10-doc, automake1.5 (<< 
1.5-2), automake1.6 (<< 1.6.1-4)
Multi-Arch: foreign

Steps to reproduce for apt-get install:

$ cat > control << END
> Package: dummy
> Depends: automake-1.14
> END
$ equivs-build control
$ apt-get install ./dummy_1.0_all.deb
The following packages have unmet dependencies:
 dummy : Depends: automake-1.14
E: Unable to correct problems, you have held broken packages.

It seems automake (= 1:1.14.1-4) provides automake-1.14 while automake
(= 1:1.15-3) provides automake-1.15. It might be that somehow apt sees
that "automake" provides automake-1.14 but does not store which version
of "automake" provides it and just either installs the newest one in the
"apt-get build-dep" case or only picks the newest one as a candidate and
then fails to satisfy the dependency because that version doesn't
provide automake-1.14.

Ideally, apt should see that there are different versions of the same
package with the same pin value but different provides and pick the one
that satisfies the dependency even if it's of a lower version. After
all, both packages are part of the same suite. Though with apt's
behaviour of selecting only the highest version as the candidate I can
see why this will not be happening and maybe instead automake should
change how they do their virtual packages. But then again, on what
grounds should automake change their provides? Only because of an apt
limitation? As far as I can see they are policy compliant and other
resolvers like dose3 or aspcud will happily find a solution.

The clear policy violation here is the "apt-get build-dep" problem
because apt installs a package that is not satisfying the build
dependency at hand. This has to be fixed. At least just fail in the same
way as during binary package installation.

What do you think?

cheers, josch

Processed: FTBFS in unstable

[Debian Bug Tracking System]

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

> retitle 811714 FTBFS: unknown type name 'matrix'; did you mean 
> 'Feel::tag::matrix'
Bug #811714 [feel++] feel++: FTBFS with GCC 6: unknown type name
Changed Bug title to 'FTBFS: unknown type name 'matrix'; did you mean 
'Feel::tag::matrix'' from 'feel++: FTBFS with GCC 6: unknown type name'
> severity 811714 serious
Bug #811714 [feel++] FTBFS: unknown type name 'matrix'; did you mean 
'Feel::tag::matrix'
Severity set to 'serious' from 'important'
> user debian-...@lists.debian.org
Setting user to debian-...@lists.debian.org (was t...@hpe.com).
> usertag 811714 - ftbfs-gcc-6
Usertags were: gcc-6-unknown-type-name ftbfs-gcc-6.
Usertags are now: gcc-6-unknown-type-name.
> thanks
Stopping processing here.

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

Bug#811566: marked as done (run-init: opening console: No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 20 Jan 2016 14:38:35 +
with message-id 
and subject line Bug#811479: fixed in initramfs-tools 0.122
has caused the Debian Bug report #811479,
regarding run-init: opening console: No such file or directory
to be marked as done.

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

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


-- 
811479: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811479
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: initramfs-tools
Version: 0.121
Severity: important

Dear Maintainer,

Since upgrading initramfs-tools, the system no longer boots.

Instead the initramfs rescue shell is started:

  Loading Linux 4.3.0-1-amd64 ...
  Loading initial ramdisk ...
  Loading, please wait...
  Scanning for Btrfs filesystems
  run-init: opening console: No such file or directory
  Target filesystem doesn't have requested /sbin/init.
  run-init: opening console: No such file or directory
  run-init: opening console: No such file or directory
  run-init: opening console: No such file or directory
  run-init: opening console: No such file or directory
  run-init: : No such file or directory
  No init found. Try passing init= bootarg.
  modprobe: module ehci-orion not found in modules.dep


  BusyBox v1.22.1 (Debian 1:1.22.0-16) built-in shell (ash)
  Enter 'help' for a list of built-in commands.

  /bin/sh: can't access tty; job control turned off
  (initramfs) 

The system is installed on a single btrfs filesystem.

Regards,
Peter

-- Package-specific info:
-- initramfs sizes
-- /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.3.0-1-amd64 
root=UUID=bdb66c4b-0279-47b3-8c08-0ab0d0b2accc ro console=ttyS0,115200n8 quiet

-- resume
RESUME=UUID=46ee0f17-5ab6-4722-a108-9145cb6f1020
-- /proc/filesystems
btrfs

-- lsmod
Module  Size  Used by
binfmt_misc20480  1
iptable_raw16384  1
ipt_REJECT 16384  2
nf_reject_ipv4 16384  1 ipt_REJECT
nf_conntrack_ipv4  20480  2
nf_defrag_ipv4 16384  1 nf_conntrack_ipv4
iptable_filter 16384  1
ip_tables  28672  2 iptable_filter,iptable_raw
xt_tcpudp  16384  9
xt_multiport   16384  8
xt_CT  16384  16
ip6table_raw   16384  1
ip6t_REJECT16384  2
nf_reject_ipv6 16384  1 ip6t_REJECT
nf_conntrack_ipv6  20480  2
nf_defrag_ipv6 36864  1 nf_conntrack_ipv6
xt_conntrack   16384  4
nf_conntrack  118784  4 
xt_CT,xt_conntrack,nf_conntrack_ipv4,nf_conntrack_ipv6
ip6table_filter16384  1
ip6_tables 28672  2 ip6table_filter,ip6table_raw
x_tables   36864  12 
ip6table_filter,xt_CT,ip_tables,xt_tcpudp,xt_conntrack,xt_multiport,iptable_filter,ip6table_raw,ipt_REJECT,ip6_tables,iptable_raw,ip6t_REJECT
iosf_mbi   16384  0
crct10dif_pclmul   16384  0
crc32_pclmul   16384  0
jitterentropy_rng  16384  0
sha256_ssse3   28672  1
sha256_generic 24576  1 sha256_ssse3
hmac   16384  1
drbg   24576  1
ansi_cprng 16384  0
aesni_intel   167936  0
aes_x86_64 20480  1 aesni_intel
lrw16384  1 aesni_intel
i2c_piix4  24576  0
gf128mul   16384  1 lrw
ppdev  20480  0
acpi_cpufreq   20480  0
pvpanic16384  0
evdev  20480  1
glue_helper16384  1 aesni_intel
psmouse   126976  0
8250_fintek16384  0
serio_raw  16384  0
ablk_helper16384  1 aesni_intel
pcspkr 16384  0
processor  36864  1 acpi_cpufreq
button 16384  0
cryptd 20480  2 aesni_intel,ablk_helper
parport_pc 28672  0
parport49152  2 ppdev,parport_pc
tun28672  2
autofs440960  2
btrfs 954368  1
xor24576  1 btrfs
raid6_pq  102400  1 btrfs
ata_generic16384  0
virtio_net 28672  0
virtio_blk 20480  2
ata_piix   36864  0
crc32c_intel   24576  1
libata233472  2 ata_generic,ata_piix
virtio_pci 24576  0
virtio_ring20480  3 virtio_blk,virtio_net,virtio_pci
virtio 16384  3 virtio_blk,virtio_net,virtio_pci
scsi_mod  229376  1 libata
floppy 69632  0

-- /etc/initramfs-tools/modules

-- /etc/kernel-img.conf
# Kernel image management overrides
# See kernel-img.conf(5) for details

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

[Emmanuel Bourg]

Hi Ansgar,

Le 19/01/2016 17:11, Ansgar Burchardt a écrit :

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

FYI the fate of the jenkins package is currently being discussed on the
debian-java list:

  https://lists.debian.org/debian-java/2016/01/msg00019.html


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

jenkins-memory-monitor can indeed be removed with jenkins, as well as
the various plugins packaged and some libraries. Here is a quick list:

  access-modifier-checker
  bytecode-compatibility-transformer
  jellydoc
  jenkins-ant-plugin
  jenkins-antisamy-markup-formatter-plugin
  jenkins-commons-jelly
  jenkins-commons-jexl
  jenkins-constant-pool-scanner
  jenkins-crypto-util
  jenkins-dom4j
  jenkins-executable-war
  jenkins-htmlunit
  jenkins-htmlunit-core-js
  jenkins-instance-identity
  jenkins-json
  jenkins-mailer-plugin
  jenkins-matrix-auth-plugin
  jenkins-matrix-project-plugin
  jenkins-memory-monitor
  jenkins-remoting
  jenkins-ssh-cli-auth
  jenkins-task-reactor
  jenkins-test-annotations
  jenkins-trilead-ssh2
  jenkins-winstone
  jenkins-xstream
  maven-hpi-plugin
  maven-stapler-plugin
  sezpoz
  stapler
  stapler-adjunct-codemirror
  stapler-adjunct-timeline

Emmanuel Bourg

Processed: forcibly merging 809195 810076

[Debian Bug Tracking System]

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

> forcemerge 809195 810076
Bug #809195 [network-manager] network-manager_1.0.10-1_amd64.deb does not 
update my I.P address correctly when I start my VPN
Bug #809494 [network-manager] network-manager: NetworkManager 1.0.10-1 does not 
add default route for VPN
Bug #809526 [network-manager] network-manager-openvpn: Fail to set IPv4 route
Bug #809494 [network-manager] network-manager: NetworkManager 1.0.10-1 does not 
add default route for VPN
Removed indication that 809494 affects network-manager-openvn, 
network-manager-vpnc, and network-manager-pptp
Added indication that 809494 affects 
network-manager-vpnc,network-manager-openvn,network-manager-pptp
Removed indication that 809195 affects network-manager-vpnc, 
network-manager-openvn, and network-manager-pptp
Added indication that 809195 affects 
network-manager-vpnc,network-manager-openvn,network-manager-pptp
Removed indication that 809526 affects network-manager-openvn, 
network-manager-vpnc, and network-manager-pptp
Added indication that 809526 affects 
network-manager-vpnc,network-manager-openvn,network-manager-pptp
Marked as found in versions network-manager/1.0.6-1.
Marked as found in versions network-manager/1.0.6-1.
Marked as found in versions network-manager/1.0.6-1.
Bug #810076 [network-manager] network-manager: NM does not honor "push route" 
any more
Set Bug forwarded-to-address to 
'https://bugzilla.gnome.org/show_bug.cgi?id=759892'.
Severity set to 'serious' from 'normal'
Added indication that 810076 affects 
network-manager-vpnc,network-manager-openvn,network-manager-pptp
Marked as found in versions network-manager/1.0.10-1.
Added tag(s) fixed-upstream.
Bug #809526 [network-manager] network-manager-openvpn: Fail to set IPv4 route
Merged 809195 809494 809526 810076
> thanks
Stopping processing here.

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

Bug#812114: jsonpickle: FTBFS: SyntaxError: unexpected EOF while parsing

[Chris Lamb]

Source: jsonpickle
Version: 0.9.2-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,

jsonpickle fails to build from source in unstable/amd64:

  [..]
  
  ==
  ERROR: test_ndarray_roundtrip (numpy_test.NumpyTestCase)
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20160120190203.sPKSaEICvX/jsonpickle-0.9.2/tests/numpy_test.py",
 line 103, in test_ndarray_roundtrip
  decoded = self.roundtrip(array)
File 
"/home/lamby/temp/cdt.20160120190203.sPKSaEICvX/jsonpickle-0.9.2/tests/numpy_test.py",
 line 32, in roundtrip
  return jsonpickle.decode(jsonpickle.encode(obj))
File 
"/home/lamby/temp/cdt.20160120190203.sPKSaEICvX/jsonpickle-0.9.2/jsonpickle/__init__.py",
 line 148, in decode
  return unpickler.decode(string, backend=backend, keys=keys)
File 
"/home/lamby/temp/cdt.20160120190203.sPKSaEICvX/jsonpickle-0.9.2/jsonpickle/unpickler.py",
 line 26, in decode
  return context.restore(backend.decode(string), reset=reset)
File 
"/home/lamby/temp/cdt.20160120190203.sPKSaEICvX/jsonpickle-0.9.2/jsonpickle/unpickler.py",
 line 119, in restore
  value = self._restore(obj)
File 
"/home/lamby/temp/cdt.20160120190203.sPKSaEICvX/jsonpickle-0.9.2/jsonpickle/unpickler.py",
 line 159, in _restore
  return restore(obj)
File 
"/home/lamby/temp/cdt.20160120190203.sPKSaEICvX/jsonpickle-0.9.2/jsonpickle/unpickler.py",
 line 235, in _restore_object
  instance = handler(self).restore(obj)
File 
"/home/lamby/temp/cdt.20160120190203.sPKSaEICvX/jsonpickle-0.9.2/jsonpickle/ext/numpy.py",
 line 49, in restore
  dtype = self.restore_dtype(data)
File 
"/home/lamby/temp/cdt.20160120190203.sPKSaEICvX/jsonpickle-0.9.2/jsonpickle/ext/numpy.py",
 line 19, in restore_dtype
  return np.dtype(dtype)
File "/usr/lib/python2.7/dist-packages/numpy/core/_internal.py", line 191, 
in _commastring
  newitem = (dtype, eval(repeats))
File "", line 1
  (
  ^
  SyntaxError: unexpected EOF while parsing
  
  --
  Ran 230 tests in 0.166s
  
  FAILED (errors=1, skipped=9)
  E: pybuild pybuild:274: test: plugin custom failed with: exit code=1: 
tests/runtests.py
  dh_auto_test: pybuild --test -i python{version} -p 2.7 --dir . returned exit 
code 13
  debian/rules:10: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 25
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160120190203.sPKSaEICvX/jsonpickle-0.9.2'
  debian/rules:7: 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
   `-


jsonpickle.0.9.2-1.unstable.amd64.log.txt.gz
Description: Binary data

Processed: Bug#796647 marked as pending

[Debian Bug Tracking System]

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

> tag 796647 pending
Bug #796647 [src:python-sptest] python-sptest: FTBFS: Missing Build-Depends on 
python
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#790273: marked as done (publib: FTBFS with glibc 2.21 and gcc-5)

[Debian Bug Tracking System]

Your message dated Wed, 20 Jan 2016 15:11:06 +
with message-id 
and subject line Bug#790273: fixed in publib 0.40-2
has caused the Debian Bug report #790273,
regarding publib: FTBFS with glibc 2.21 and gcc-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.)


-- 
790273: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790273
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: publib
Version: 0.40-1
Severity: normal

>From my pbuilder build log, using a setup preferring glibc and gcc-defaults
from experimental:

...
gcc -Iincludes -D__publib__ -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -MD -MF iset/iset_rm_rng.d -c 
iset/iset_rm_rng.c -o iset/iset_rm_rng.o
gcc -Iincludes -D__publib__ -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -MD -MF iset/iset_union.d -c 
iset/iset_union.c -o iset/iset_union.o
gcc -Iincludes -D__publib__ -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -MD -MF lockfile/lockfile.d -c 
lockfile/lockfile.c -o lockfile/lockfile.o
In file included from /usr/include/string.h:634:0,
 from lockfile/lockfile.c:42:
includes/publib/strutil.h:67:7: error: expected identifier or '(' before 
'__extension__'
 char *strndup(const char *, size_t);
   ^
Makefile:403: recipe for target 'lockfile/lockfile.o' failed
make[1]: *** [lockfile/lockfile.o] Error 1
make[1]: Leaving directory '/tmp/buildd/publib-0.40'
dh_auto_build: make -j1 returned exit code 2
debian/rules:4: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
-- 
Daniel Schepler
--- End Message ---
--- Begin Message ---
Source: publib
Source-Version: 0.40-2

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

Debian distribution maintenance software
pp.
Robert Luberda  (supplier of updated publib 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 23:18:43 +0100
Source: publib
Binary: publib-dev
Architecture: source i386
Version: 0.40-2
Distribution: unstable
Urgency: high
Maintainer: Debian QA Group 
Changed-By: Robert Luberda 
Description:
 publib-dev - library of miscellaneous C functions
Closes: 790273
Changes:
 publib (0.40-2) unstable; urgency=high
 .
   * QA upload:
 - maintainer set to Debian QA Group;
 - git packaging moved to the collab-maint project.
   * Introduced the following patches:
 - 001-Remove-strndup.patch to fix FTBFS on current gcc and glibc
   by removing declaration of strndup() function together with its
   implementation and man page (closes: #790273);
 - 0002-Fix-undefined-behavior-warning.patch to fix an off-by-one
   bug in base64 decoder resulting in an undefined behavior warning
   given by gcc-5;
 - 0003-Remove-Makefile-at-distclean.patch to make sure the generated
   Makefile is dropped, so that sequential builds do not fail;
 - 0004-Fix-spelling-errors-in-manpages.patch to fix spelling typos
   in `occurrence' and `occurred' words, noticed by lintian.
   in `occurrence' and `occurred' words, noticed by lintian;
 - 0005-Pass-LDFLAGS-to-test-programs.patch to use $(LDFLAGS) while
   linking test programs.
   * Mark the binary package as `Multi-Arch: same'.
   * Bump Standards-Version to 3.9.6 (no other changes needed).
Checksums-Sha1:
 6869637e7ca8e807e29680c8a17d1bde08b9fe31 1772 publib_0.40-2.dsc
 cc2c6c119490fa0a7d3e8e050e4bccbff73d78ad 8140 publib_0.40-2.debian.tar.xz
 3424010487b726175385c62dc300e20f9715fba1 154148 publib-dev_0.40-2_i386.deb
Checksums-Sha256:
 6a1902e360fd64a07a241d0d74cba89c1a573cbff61c8a3b34f357400f1ea0d4 1772 
publib_0.40-2.dsc
 659d335cfecd0496bf019959740bc20837351b5f808aaf9bb9332aa9e8e47a69 8140 
publib_0.40-2.debian.tar.xz
 e32d90f5e6915cd0f1016ecc213c186cd822c59bde84ddecdab9c0ee66e85ba4 

Bug#811490: marked as done (python-falcon fails the tests running with python3)

[Debian Bug Tracking System]

Your message dated Wed, 20 Jan 2016 15:12:02 +
with message-id 
and subject line Bug#811490: fixed in python-falcon 0.3.0-5
has caused the Debian Bug report #811490,
regarding python-falcon fails the tests running with python3
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.)


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

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'
--- End Message ---
--- Begin Message ---
Source: python-falcon
Source-Version: 0.3.0-5

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 20 Jan 2016 07:27:47 +
Source: python-falcon
Binary: python-falcon python3-falcon
Architecture: source amd64
Version: 0.3.0-5
Distribution: unstable
Urgency: medium
Maintainer: PKG OpenStack 
Changed-By: Thomas Goirand 
Description:
 python-falcon - supersonic micro-framework for building cloud APIs - Python 2.x
 python3-falcon - supersonic micro-framework for building cloud APIs - Python 
3.x
Closes: 811465 811490
Changes:
 python-falcon (0.3.0-5) unstable; urgency=medium
 .
   * Added patch to fix test_request_cookie_parsing which fixes FTBFS
 (Closes: #811490, #811465).
   * Fix debian/copyright ordering.
   * Add patch to fix some spelling mistakes.
Checksums-Sha1:
 d8d4825bacd0f49a2c6276de5243ea12b649829c 2370 python-falcon_0.3.0-5.dsc
 e13503dc8f396c3d3396da1bab103af13a84a596 5120 
python-falcon_0.3.0-5.debian.tar.xz
 b395b45e6927afdaf0f9a83b3f5a6db9b6cd8500 1209914 
python-falcon-dbgsym_0.3.0-5_amd64.deb
 021def2d510d2cca24e442aad0600b8fff44e25d 395524 python-falcon_0.3.0-5_amd64.deb
 12cea2718db10dd2a6bbb40f925d0773d45d4b96 2828710 
python3-falcon-dbgsym_0.3.0-5_amd64.deb
 867808ef6de56dc55a6d6f04229499ca4b663371 585294 
python3-falcon_0.3.0-5_amd64.deb
Checksums-Sha256:
 35a05e1d927eb01cfd7f7494694a29a3d8381ee6727812c62903e98815f8b5ed 2370 
python-falcon_0.3.0-5.dsc
 635a564adb381f855c96b61731c7a1659aec8cd35f772d71fd9de90a22589d79 5120 
python-falcon_0.3.0-5.debian.tar.xz
 e7be10efc4b49d0502af168a8e3c21a9c3757b5715d2f58cb37d7569d3e4955a 1209914 
python-falcon-dbgsym_0.3.0-5_amd64.deb
 e5f33b2f5b6cab589b32ea5f336be930885932dd92930e39e3a94dd62fcb8931 395524 
python-falcon_0.3.0-5_amd64.deb
 1e88db6c82c0146a33e26e48fd94aeca13790ed8a84a967c45e87cfb822ae6c3 2828710 
python3-falcon-dbgsym_0.3.0-5_amd64.deb
 

Bug#800303: marked as done (libipc-signal-perl: Please migrate a supported debhelper compat level)

[Debian Bug Tracking System]

Your message dated Wed, 20 Jan 2016 15:53:13 +
with message-id 
and subject line Bug#800303: fixed in libipc-signal-perl 1.00-6.2
has caused the Debian Bug report #800303,
regarding libipc-signal-perl: 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.)


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

Hi,

The package libipc-signal-perl 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: libipc-signal-perl
Source-Version: 1.00-6.2

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

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

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libipc-signal-perl 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 15 Jan 2016 15:16:17 +0100
Source: libipc-signal-perl
Binary: libipc-signal-perl
Architecture: source
Version: 1.00-6.2
Distribution: unstable
Urgency: medium
Maintainer: Roderick Schertler 
Changed-By: gregor herrmann 
Closes: 800303
Description: 
 libipc-signal-perl - utility functions dealing with signals for Perl
Changes:
 libipc-signal-perl (1.00-6.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix "Please migrate a supported debhelper compat level":
 Bump debhelper compatibility level to 9 in debian/{compat,control,rules}.
 (Closes: #800303)
Checksums-Sha1: 
 e5bf423822e4a003b776b606e32d595e801845dc 1862 libipc-signal-perl_1.00-6.2.dsc
 8543669b18d3823e83ef0f6be3069da5aa6ffd21 2535 
libipc-signal-perl_1.00-6.2.diff.gz
Checksums-Sha256: 
 a23937acfe4cc2f3dab08123192f91344d42854e31d110e2c6308070fa5851d0 1862 
libipc-signal-perl_1.00-6.2.dsc
 54ffe89faf571ef8f808cf3d0e3c8a672fb0138e52552ae9e92ba3141c1981b8 2535 
libipc-signal-perl_1.00-6.2.diff.gz
Files: 
 cd5f8e3cbefe6f4cc1e0fe4fad50417f 1862 perl optional 
libipc-signal-perl_1.00-6.2.dsc
 daa86139da6c7f6967568a474778f4b0 2535 perl optional 
libipc-signal-perl_1.00-6.2.diff.gz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJWmQCDXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGQ1IP/iXBJZUhrGkv4aDL/Hw7Hmyp
AGvhn7g49gxisf/0Iaua+CBrXGCq6vwg+hTOLTkRb4D28Y12bUn14NT8eWi5tN95
xt6tutoYTwzqASmCTA5XVNruscqY7pUs3lLa3JutkcVhCRkFO78Y6PmYzS5s851i
8XEaiOxZm+KMpM8tsJuqXE1cwN9PZ82EV4fE+jGwU6FAN414lecYTMo4hknjT3y0
juS3wqX7hbnT6cEfbPaZeozDlrOyHue58yg8wyqMU6CVt8zRL/vpPW/VRm7CNE2k

Bug#812085: marked as done (libcommons-jexl2-java: FTBFS: Error resolving version for plugin 'org.apache.felix:maven-bundle-plugin' from the repositories )

[Debian Bug Tracking System]

Your message dated Wed, 20 Jan 2016 15:53:04 +
with message-id 
and subject line Bug#812085: fixed in libcommons-jexl2-java 2.1.1-3
has caused the Debian Bug report #812085,
regarding libcommons-jexl2-java: FTBFS: Error resolving version for plugin 
'org.apache.felix:maven-bundle-plugin' from the repositories 
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.)


-- 
812085: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812085
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libcommons-jexl2-java
Version: 2.1.1-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,

libcommons-jexl2-java fails to build from source in unstable/amd64:

  [..]

  cd . && /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 
-Dproperties.file.manual=/home/lamby/temp/cdt.20160120125708.4BbRf6rkUu/libcommons-jexl2-java-2.1.1/debian/maven.properties
 -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/home/lamby/temp/cdt.20160120125708.4BbRf6rkUu/libcommons-jexl2-java-2.1.1
 org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Dmaven.repo.local=/home/lamby/temp/cdt.20160120125708.4BbRf6rkUu/libcommons-jexl2-java-2.1.1/debian/maven-repo
  package -DskipTests
  [INFO] Scanning for projects...
  [WARNING] 
  [WARNING] Some problems were encountered while building the effective model 
for org.apache.commons:commons-jexl:jar:2.1.1
  [WARNING] 'build.plugins.plugin.version' for 
org.apache.felix:maven-bundle-plugin is missing. @ 
org.apache.commons:commons-parent:debian, 
/home/lamby/temp/cdt.20160120125708.4BbRf6rkUu/libcommons-jexl2-java-2.1.1/debian/maven-repo/org/apache/commons/commons-parent/debian/commons-parent-debian.pom,
 line 322, column 12
  [WARNING] 
  [WARNING] It is highly recommended to fix these problems because they 
threaten the stability of your build.
  [WARNING] 
  [WARNING] For this reason, future Maven versions might no longer support 
building such malformed projects.
  [WARNING] 
  [INFO]
 
  [INFO] 

  [INFO] Building Commons JEXL 2.1.1
  [INFO] 

  [INFO] 

  [INFO] BUILD FAILURE
  [INFO] 

  [INFO] Total time: 0.174 s
  [INFO] Finished at: 2016-01-20T12:59:10+01:00
  [INFO] Final Memory: 6M/236M
  [INFO] 

  [ERROR] Error resolving version for plugin 
'org.apache.felix:maven-bundle-plugin' from the repositories [local 
(/home/lamby/temp/cdt.20160120125708.4BbRf6rkUu/libcommons-jexl2-java-2.1.1/debian/maven-repo),
 central (https://repo.maven.apache.org/maven2)]: Plugin not found in any 
plugin repository -> [Help 1]
  [ERROR] 
  [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
  [ERROR] Re-run Maven using the -X switch to enable full debug logging.
  [ERROR] 
  [ERROR] For more information about the errors and possible solutions, please 
read the following articles:
  [ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/PluginVersionResolutionException
  /usr/share/cdbs/1/class/maven.mk:92: recipe for target 'mvn-build' failed
  make: *** [mvn-build] Error 1

  [..]

The full build log is attached.


Regards,

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


libcommons-jexl2-java.2.1.1-2.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: libcommons-jexl2-java
Source-Version: 2.1.1-3

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

Debian distribution maintenance 

Bug#811498: marked as done (libconsole-bridge0.2v5: ABI bump without package rename)

[Debian Bug Tracking System]

Your message dated Wed, 20 Jan 2016 17:18:46 +
with message-id 
and subject line Bug#811498: fixed in console-bridge 0.3.0-2
has caused the Debian Bug report #811498,
regarding libconsole-bridge0.2v5: ABI bump without package rename
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.)


-- 
811498: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811498
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Source: console-bridge
Source-Version: 0.3.0-2

We believe that the bug you reported is fixed in the latest version of
console-bridge, 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.
Jose Luis Rivero  (supplier of updated 
console-bridge package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 20 Jan 2016 17:27:35 +0100
Source: console-bridge
Binary: libconsole-bridge0.2v5 libconsole-bridge-dev libconsole-bridge0.2v5-dbg
Architecture: source
Version: 0.3.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jose Luis Rivero 
Description:
 libconsole-bridge-dev - console bridge - development files
 libconsole-bridge0.2v5 - console bridge - library
 libconsole-bridge0.2v5-dbg - console bridge - debugging symbols
Closes: 811498
Changes:
 console-bridge (0.3.0-2) unstable; urgency=medium
 .
   * Fix package name lost in update by using a symlink libconsole-bridge0.2
   * Patch to implement 0.2 ABI and keep the 0.3 library installed
 (Closes: #811498)
Checksums-Sha1:
 08d3d154f06665ba1840e68afbdf20fab252b054 1927 console-bridge_0.3.0-2.dsc
 0cf2e77d6794e4d008c31444d187d90e8467b041 6298 console-bridge_0.3.0.orig.tar.gz
 ae545cb68bb2c7ec8ea1c79f8919fa679a617820 3640 
console-bridge_0.3.0-2.debian.tar.xz
Checksums-Sha256:
 e9360625bb410bf87c793658b904c766d92b121c227834ae705bbf155782e4d3 1927 
console-bridge_0.3.0-2.dsc
 1b43a1b8d3e762415290d4ba9ef68beb3c8412f340aa053d2b1beec660685a69 6298 
console-bridge_0.3.0.orig.tar.gz
 4f09664e66490bedb616bc9539640b3e232c3e7abe12a5e115951052cab9ad88 3640 
console-bridge_0.3.0-2.debian.tar.xz
Files:
 b20ec0fdd5d644d8804b8ecea2317ed4 1927 libs extra console-bridge_0.3.0-2.dsc
 54502ee866db73d81fc556af1319ce37 6298 libs extra 
console-bridge_0.3.0.orig.tar.gz
 1ff6af636921a1da8a9b367e5838b332 3640 libs extra 
console-bridge_0.3.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCgAGBQJWn7XzAAoJEF6UbAkK/wQnagUH/R96ayA5oEg3bg8hP2pBHZhV
Hp8mwSSVxo8nsv9Gyp4rldOPVzj7tR83gP+PddZrJnQOMuM/HwRyLn0GZstwild0

Processed: Interesting fact, bumping severity

[Debian Bug Tracking System]

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

> severity 757379 serious
Bug #757379 [ksystemlog] ksystemlog: Can't open KSystemLog
Severity set to 'serious' from 'important'
> notfound 757379 4:15.08.0-1
Bug #757379 [ksystemlog] ksystemlog: Can't open KSystemLog
Ignoring request to alter found versions of bug #757379 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#796647: marked as pending

[Mattia Rizzolo]

tag 796647 pending
thanks

Hello,

Bug #796647 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-sptest.git;a=commitdiff;h=bff3963

---
commit bff396340f95e376cd6c31b95833bfbeca6a89a4
Author: Jakub Wilk 
Date:   Thu Sep 22 11:41:00 2011 +

Build-depend on python.  Closes: #796647

diff --git a/debian/changelog b/debian/changelog
index bad46a5..27cf6e6 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -10,6 +10,9 @@ python-sptest (0.2.1-3) UNRELEASED; urgency=low
   to uscan call in get-orig-source target.
 - Define DEB_UPSTREAM_VERSION variable.
 
+  [ Jakub Wilk ]
+  * Build-depend on python.  Closes: #796647
+
  -- Stephan Peijnik   Wed, 25 Feb 2009 16:29:50 +0100
 
 python-sptest (0.2.1-2.1) unstable; urgency=medium

Processed: Re: Bug#812116: newly built initrd complains about missing init

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 initramfs-tools-core 0.121
Bug #812116 [initramfs-tools] newly built initrd complains about missing init
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 #812116 to the same values 
previously set
Bug #812116 [initramfs-tools-core] newly built initrd complains about missing 
init
Marked as found in versions initramfs-tools/0.121.
> forcemerge 811479 -1
Bug #811479 {Done: Ben Hutchings } [initramfs-tools-core] 
boot fails in "run-init -n ..."
Bug #811566 {Done: Ben Hutchings } [initramfs-tools-core] 
run-init: opening console: No such file or directory
Bug #812116 [initramfs-tools-core] newly built initrd complains about missing 
init
Severity set to 'critical' from 'normal'
Marked Bug as done
Added indication that 812116 affects xen-tools
Marked as fixed in versions initramfs-tools/0.122.
Added tag(s) moreinfo and patch.
Bug #811566 {Done: Ben Hutchings } [initramfs-tools-core] 
run-init: opening console: No such file or directory
Merged 811479 811566 812116

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

Bug#796931: [pkg-gnupg-maint] Bug#796931: Another data point

[Daniel Kahn Gillmor]

Hi Manoj--

On Wed 2016-01-20 04:04:43 -0500, Manoj Srivastava wrote:

> I sourced the file 70gnupg-agent.sh discussed earlier int he bug
> report.

If you're running X11, i'd assume that file would have been sourced
during your session startup.

> I am still having issues -- at least, with gpg, I can actually use
> gpg; gpg2 just fails.

can you show the version numbers you're using?

dpkg -l gnupg gnupg2 gnupg-agent


>> echo $GNUPGHOME
> /home/srivasta/lib/.sec
>>echo $GPG_AGENT_INFO
>
>> echo $GPG_AGENT
>
>> gpg-agent
> gpg-agent[1725]: gpg-agent running and available

the fact that GPG_AGENT_INFO isn't set is a little odd if you've sourced
70gpg-agent.sh, although the fact that you're not using a standard
GNUPGHOME also makes me wonder what's going on here.  do you have
"use-agent" set in /home/srivastava/lib/.sec/gpg.conf?  what about in
/home/srivastava/.gnupg/gpg.conf ?

>> gpg2 -vvv --clearsign ~/.login
> gpg: keyserver option 'include-disabled' is unknown
> gpg: keyserver option 'honor-http-proxy' is unknown
> gpg: using character set 'utf-8'
> gpg: Note: signature key 9D760D4D has been revoked
> gpg: Note: signature key 840A4306 expired Wed 11 May 2011 02:33:47 PM PDT
> gpg: using PGP trust model
> gpg: key C5779A1C: accepted as trusted key
> gpg: Note: signature key 9D760D4D has been revoked
> gpg: Note: signature key 840A4306 expired Wed 11 May 2011 02:33:47 PM PDT
> gpg: using subkey 6F576472 instead of primary key C5779A1C
> gpg: writing to '/home/srivasta/.login.asc'
> gpg: signing failed: No secret key
> gpg: /home/srivasta/.login: clearsign failed: No secret key
> [1]1767 exit 2 gpg2 -vvv --clearsign ~/.login

This response suggests that you might be using gpg2 2.1.x (it finds the
agent while GPG_AGENT_INFO is unset, without specifying
--use-standard-socket), but your secret keys have not been imported.
does /home/srivastava/lib/.sec/private-keys-v1.d/ contain the keygrip of
the secret key you need to use?

the keygrip for your signing-capable subkey 0x36BD720F6F576472 is
4AA76328759B16116F1C2F3380A3C313A1398F34 (you can find this with "gpg2
--with-keygrip --list-keys 0x36BD720F6F576472), so i'd expect there to
be a file at:

 
/home/srivastava/lib/.sec/private-keys-v1.d/4AA76328759B16116F1C2F3380A3C313A1398F34.key

If that doesn't exist, and you're using gpg 2.1.x, can you try importing
your gpgv1 secret keyring again and then retrying your command?

   gpg2 --import < /home/srivastava/lib/.sec/secring.gpg


If this solves things for you, i'd still like to understand why the
secret keyring didn't get imported automatically the first time you used
gpg 2.1.x.  Can you tell me any history of how and when (what versions?)
you first moved to 2.1.x ?

>> gpg -vvv --clearsign ~/.login
> gpg: using character set `utf-8'
> gpg: using PGP trust model
> gpg: key C5779A1C: accepted as trusted key
> gpg: can't handle public key algorithm 22
> gpg: can't handle public key algorithm 19
> gpg: error checking usability status of C7261095
> gpg: key C7261095: secret key without public key - skipped
> gpg: NOTE: signature key 840A4306 expired Wed 11 May 2011 02:33:47 PM PDT
> gpg: NOTE: signature key 840A4306 expired Wed 11 May 2011 02:33:47 PM PDT
> gpg: no secret subkey for public subkey 840A4306 - ignoring
> gpg: using subkey 6F576472 instead of primary key C5779A1C
>
> You need a passphrase to unlock the secret key for
> user: "Manoj Srivastava "
> gpg: NOTE: signature key 840A4306 expired Wed 11 May 2011 02:33:47 PM PDT
> gpg: using subkey 6F576472 instead of primary key C5779A1C
> 2048-bit RSA key, ID 6F576472, created 2009-07-23 (main key ID C5779A1C)
>
> gpg: gpg-agent is not available in this session
> You need a passphrase to unlock the secret key for
> user: "Manoj Srivastava "
> 2048-bit RSA key, ID 6F576472, created 2009-07-23 (main key ID C5779A1C)
>
> gpg: writing to `/home/srivasta/.login.asc'
> gpg: RSA/SHA512 signature from: "6F576472 Manoj Srivastava 
> "

This shows you not using the gpg-agent at all.

>  ps auwwx | egrep '[g]pg-agent'
> srivasta 24911  0.0  0.0 165000  2180 ?SNs  00:39   0:00 gpg-agent 
> --daemon --enable-ssh-support --allow-preset-passphrase 
> --no-allow-external-cache

OK, so the agent is running, but it's not clear what started it.  I
suspect it's likely that it was auto-launched by gpg 2.1.x.

Regards,

 --dkg

Bug#811217: marked as done (diaspora: Configure error, Could not find gem 'timers (~> 4.0.0) ruby')

[Debian Bug Tracking System]

Your message dated Wed, 20 Jan 2016 15:16:04 +
with message-id 
and subject line Bug#811217: fixed in ruby-celluloid 0.16.0-4
has caused the Debian Bug report #811217,
regarding diaspora: Configure error, Could not find gem 'timers (~> 4.0.0) ruby'
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.)


-- 
811217: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811217
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: diaspora
Version: 0.5.5.1+debian-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

When trying to install Diaspora on Debian unstable, I got this error:

Setting up diaspora (0.5.5.1+debian-2) ...
Setting up environment varibales...
Using /etc/diaspora.conf...
export RAILS_ENV=production
export DB=postgres
RAILS_ENV=production DB=postgres ENVIRONMENT_URL=https://localhost
Verifying we have all required libraries...
Resolving dependencies
Bundler could not find compatible versions for gem "timers":
  In Gemfile:
sidekiq (= 3.4.2) ruby depends on
  celluloid (~> 0.16.0) ruby depends on
timers (~> 4.0.0) ruby
Could not find gem 'timers (~> 4.0.0) ruby', which is required by gem
'celluloid
(~> 0.16.0) ruby', in any of the sources.
dpkg: error processing package diaspora (--configure):
 subprocess installed post-installation script returned error exit status 6

The full log is attached.


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

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

Versions of packages diaspora depends on:
ii  adduser  3.113+nmu3
ii  bundler  1.10.6-2
ii  dbconfig-common  2.0.0
ii  diaspora-common  0.5.3.0+debian1
ii  fonts-roboto-hinted  2:0~20151012-1
ii  imagemagick  8:6.8.9.9-6+b1
ii  nodejs   4.2.4~dfsg-2
ii  postgresql-client9.5+172
ii  postgresql-client-9.5 [postgres  9.5.0-2
ii  rake 10.4.2-2
ii  ruby 1:2.2.4
ii  ruby-actionpack-action-caching   1.1.1-4
ii  ruby-actionpack-page-caching 1.0.2-4
ii  ruby-active-model-serializers0.9.3-1
ii  ruby-activerecord-import 0.10.0-1
ii  ruby-acts-as-api 0.4.2-1
ii  ruby-acts-as-taggable-on 3.5.0-2
ii  ruby-addressable 2.3.8-1
ii  ruby-asset-sync  1.1.0-2
ii  ruby-autoprefixer-rails  6.0.3-2
ii  ruby-backbone-on-rails   1.2.0.0-2
ii  ruby-carrierwave 0.10.0+gh-1
ii  ruby-client-side-validations 3.2.6+gh-1
ii  ruby-compass-rails   2.0.5-5
ii  ruby-configurate 0.3.1-1
ii  ruby-devise  3.5.2-3
ii  ruby-devise-lastseenable 0.0.6-1
ii  ruby-devise-token-authenticatab  0.4.0-1
ii  ruby-diaspora-federation-rails   0.0.8-2
ii  ruby-entypo-rails2.2.3-1
ii  ruby-eye 0.7-2
ii  ruby-facebox-rails   0.2.0-2
ii  ruby-faraday 0.9.2-2
ii  ruby-faraday-cookie-jar  0.0.6-1
ii  ruby-faraday-middleware  0.10.0-1
ii  ruby-fog 1.34.0-2
ii  ruby-foreigner   1.7.4-1
ii  ruby-gon 6.0.1-1
ii  ruby-haml4.0.7-1
ii  ruby-handlebars-assets   2:0.21.0-5
ii  ruby-http-accept-language2.0.5-3
ii  ruby-i18n-inflector-rails1.0.7-3
ii  ruby-jquery-rails4.0.5-1
ii  ruby-jquery-ui-rails 5.0.5-3
ii  ruby-js-image-paths  0.0.2-1
ii  ruby-js-routes   1.1.2-1
ii  ruby-json1.8.3-1+b1
ii  ruby-json-schema 2.5.1-1
ii  ruby-logging-rails   0.5.0-2
ii  ruby-markerb 1.1.0-1
ii  ruby-messagebus-api 
3.0.7+git.20130130.97b34ece.REALLY.1.0.3-2
ii  ruby-mini-magick 4.3.6-2
ii  ruby-mobile-fu   1.3.1-2
ii  ruby-mysql2  0.3.18-1
ii  ruby-nokogiri1.6.7.1-1
ii  ruby-oembed  0.8.14-1
ii  ruby-omniauth1.2.2-3
ii  ruby-omniauth-facebook   2.0.1-1
ii  ruby-omniauth-tumblr 1.1+git.20140424.078c18c746-1
ii  ruby-omniauth-twitter   

Bug#809195: marked as done (network-manager_1.0.10-1_amd64.deb does not update my I.P address correctly when I start my VPN)

[Debian Bug Tracking System]

Your message dated Wed, 20 Jan 2016 15:54:57 +
with message-id 
and subject line Bug#809195: fixed in network-manager 1.0.10-2
has caused the Debian Bug report #809195,
regarding network-manager_1.0.10-1_amd64.deb does not update my I.P address 
correctly when I start my VPN
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.)


-- 
809195: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809195
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: network-manager
Version: 1.0.10-1
Severity: important

Dear Maintainer,


Hallo

When I start my VPN network-manager_1.0.10-1 does not update my IP address
correctly , as shown by using  various IP address check sites i.e :

https://whoer.net/

http://www.iplocationfinder.com/


These websites continue to show my ISP provider IP address.

If I return to using network-manager_1.0.8-2 my VPN IP address is shown as
having been updated correctly .

My system is fully up to date



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

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

Versions of packages network-manager depends on:
ii  adduser3.113+nmu3
ii  dbus   1.10.6-1
ii  init-system-helpers1.24
ii  isc-dhcp-client4.3.3-5
ii  libbluetooth3  5.36-1
ii  libc6  2.21-6
ii  libdbus-1-31.10.6-1
ii  libdbus-glib-1-2   0.102-1
ii  libglib2.0-0   2.46.2-3
ii  libgnutls-deb0-28  3.3.18-1
ii  libgudev-1.0-0 230-2
ii  libmm-glib01.4.12-1
ii  libndp01.4-2
ii  libnewt0.520.52.18-1+b1
ii  libnl-3-2003.2.26-1
ii  libnl-genl-3-200   3.2.26-1
ii  libnl-route-3-200  3.2.26-1
ii  libnm0 1.0.10-1
ii  libpam-systemd 228-2+b1
ii  libpolkit-agent-1-00.105-14
ii  libpolkit-gobject-1-0  0.105-14
ii  libreadline6   6.3-8+b4
ii  libsoup2.4-1   2.52.2-1
ii  libsystemd0228-2+b1
ii  libteamdctl0   1.18-1
ii  libuuid1   2.27.1-1
ii  lsb-base   9.20150917
ii  policykit-10.105-14
ii  udev   228-2+b1
ii  wpasupplicant  2.3-2.3

Versions of packages network-manager recommends:
ii  crda3.13-1+b1
pn  dnsmasq-base
ii  iptables1.4.21-2+b1
pn  iputils-arping  
ii  modemmanager1.4.12-1
ii  ppp 2.4.7-1+1

Versions of packages network-manager suggests:
pn  avahi-autoipd  
pn  libteam-utils  

-- Configuration Files:
/etc/NetworkManager/NetworkManager.conf changed [not included]

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: network-manager
Source-Version: 1.0.10-2

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

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated network-manager package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 20 Jan 2016 16:16:13 +0100
Source: network-manager
Binary: network-manager network-manager-dev libnm-glib4 libnm-glib-dev 
libnm-glib-vpn1 libnm-glib-vpn-dev libnm-util2 libnm-util-dev libnm0 libnm-dev 
network-manager-dbg gir1.2-networkmanager-1.0
Architecture: source
Version: 1.0.10-2
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Michael Biebl 
Description:
 gir1.2-networkmanager-1.0 - GObject introspection data for NetworkManager
 libnm-dev  - GObject-based client library for NetworkManager (development file
 libnm-glib-dev - network management framework (GLib interface)
 libnm-glib-vpn-dev - network management framework (GLib interface)
 libnm-glib-vpn1 - 

Bug#809526: marked as done (network-manager-openvpn: Fail to set IPv4 route)

[Debian Bug Tracking System]

Your message dated Wed, 20 Jan 2016 15:54:57 +
with message-id 
and subject line Bug#809195: fixed in network-manager 1.0.10-2
has caused the Debian Bug report #809195,
regarding network-manager-openvpn: Fail to set IPv4 route
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.)


-- 
809195: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809195
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: network-manager-openvpn
Version: 1.0.8-1
Severity: normal

Dear Maintainer,

   * What led up to the situation?

I have this problem after the last network-manager update, from 1.0.8-1 -> 
1.0.10-1.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I'm tring to connect to my vpn-server

   * What was the outcome of this action?

I get the following error:

Dec 31 18:30:42 lucaws14 NetworkManager[650]:   platform-linux: 
do-add-ip4-route: failure adding ip4-route '10: 10.150.184.0/22 50': Unspecific 
failure (1)
Dec 31 18:30:42 lucaws14 NetworkManager[650]:   platform-linux: 
do-add-ip4-route: failure adding ip4-route '10: 192.168.20.1/32 50': Unspecific 
failure (1)

   * What outcome did you expect instead?

With the previous network-manager package I get the correct ipv4 route.



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

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

Versions of packages network-manager-openvpn depends on:
ii  adduser   3.113+nmu3
ii  libc6 2.21-6
ii  libdbus-1-3   1.10.6-1
ii  libdbus-glib-1-2  0.102-1
ii  libglib2.0-0  2.46.2-3
ii  libnm-glib-vpn1   1.0.10-1
ii  libnm-glib4   1.0.10-1
ii  libnm-util2   1.0.10-1
ii  openvpn   2.3.8-1

network-manager-openvpn recommends no packages.

network-manager-openvpn suggests no packages.

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: network-manager
Source-Version: 1.0.10-2

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

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated network-manager package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 20 Jan 2016 16:16:13 +0100
Source: network-manager
Binary: network-manager network-manager-dev libnm-glib4 libnm-glib-dev 
libnm-glib-vpn1 libnm-glib-vpn-dev libnm-util2 libnm-util-dev libnm0 libnm-dev 
network-manager-dbg gir1.2-networkmanager-1.0
Architecture: source
Version: 1.0.10-2
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Michael Biebl 
Description:
 gir1.2-networkmanager-1.0 - GObject introspection data for NetworkManager
 libnm-dev  - GObject-based client library for NetworkManager (development file
 libnm-glib-dev - network management framework (GLib interface)
 libnm-glib-vpn-dev - network management framework (GLib interface)
 libnm-glib-vpn1 - network management framework (GLib VPN shared library)
 libnm-glib4 - network management framework (GLib shared library)
 libnm-util-dev - network management framework (development files)
 libnm-util2 - network management framework (shared library)
 libnm0 - GObject-based client library for NetworkManager
 network-manager - network management framework (daemon and userspace tools)
 network-manager-dbg - network management framework (debugging symbols)
 network-manager-dev - network management framework (development files)
Closes: 783525 809195
Changes:
 network-manager (1.0.10-2) unstable; urgency=medium
 .
   * Fix failure to configure routes due to wrong device-route for IPv4
 peer-addresses. Patch cherry-picked from upstream Git. (Closes: #809195)
   * Switch from user-mode PPPoE client back 

Processed: Re: Bug#797961: How to proceed?

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #797961 [ecryptfs-utils] ecryptfs-utils: encrypted swap fails
Severity set to 'important' from 'grave'

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

Bug#797961: How to proceed?

[GCS]

Control: severity -1 important

On Sun, Jan 17, 2016 at 12:14 AM, Andreas Hilboll  wrote:
> I would very much appreciate if this package would return into testing.
 Yes, this bug doesn't make ecryptfs-utils fail for everyone.

> Christan has suggested that the problem is not even with ecryptfs-utils but
> rather with cryptsetup.
 I'm busy with other things, but I do hope that I can reproduce this
next week or so. Then I can do tests and debugging.

Cheers,
Laszlo/GCS

Bug#809494: marked as done (network-manager: NetworkManager 1.0.10-1 does not add default route for VPN)

[Debian Bug Tracking System]

Your message dated Wed, 20 Jan 2016 15:54:57 +
with message-id 
and subject line Bug#809195: fixed in network-manager 1.0.10-2
has caused the Debian Bug report #809195,
regarding network-manager: NetworkManager 1.0.10-1 does not add default route 
for VPN
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.)


-- 
809195: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809195
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: network-manager
Version: 1.0.10-1
Severity: important

Dear Maintainer,

I am using NetworkManager and the OpenVPN plugin (network-manager-openvpn).
After upgrading NetworkManager 1.0.8-1 to 1.0.10-1, no default routes were set
anymore.

The corresponding lines in /var/log/syslog are:

Dec 31 11:11:00 snowfox NetworkManager[2599]:   platform-linux: 
do-add-ip4-route: failure adding ip4-route '10: 0.0.0.0/0 50': Unspecific 
failure (1)
Dec 31 11:11:00 snowfox NetworkManager[2599]:   default-route: failed to 
add default route 0.0.0.0/0 via 10.8.0.5 dev 10 metric 50 mss 0 src vpn with 
effective metric 50

I choose severity ‘important’, because this renders a VPN tunnel useless in many
cases, and this is a major security leak.  Please feel free to change the
severity level if you disagree.

Best wishes,

Marcel


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

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

Versions of packages network-manager depends on:
ii  adduser3.113+nmu3
ii  dbus   1.10.6-1
ii  init-system-helpers1.24
ii  isc-dhcp-client4.3.3-5
ii  libbluetooth3  5.36-1
ii  libc6  2.21-6
ii  libdbus-1-31.10.6-1
ii  libdbus-glib-1-2   0.102-1
ii  libglib2.0-0   2.46.2-3
ii  libgnutls-deb0-28  3.3.18-1
ii  libgudev-1.0-0 230-2
ii  libmm-glib01.4.12-1
ii  libndp01.4-2
ii  libnewt0.520.52.18-1+b1
ii  libnl-3-2003.2.26-1
ii  libnl-genl-3-200   3.2.26-1
ii  libnl-route-3-200  3.2.26-1
ii  libnm0 1.0.10-1
ii  libpam-systemd 228-2+b1
ii  libpolkit-agent-1-00.105-14
ii  libpolkit-gobject-1-0  0.105-14
ii  libreadline6   6.3-8+b4
ii  libsoup2.4-1   2.52.1-1
ii  libsystemd0228-2+b1
ii  libteamdctl0   1.18-1
ii  libuuid1   2.27.1-1
ii  lsb-base   9.20150917
ii  policykit-10.105-14
ii  udev   228-2+b1
ii  wpasupplicant  2.3-2.3

Versions of packages network-manager recommends:
ii  crda3.13-1+b1
ii  dnsmasq-base2.75-1
ii  iptables1.4.21-2+b1
ii  iputils-arping  3:20121221-5+b2
ii  modemmanager1.4.12-1
ii  ppp 2.4.7-1+1

Versions of packages network-manager suggests:
pn  avahi-autoipd  
pn  libteam-utils  

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: network-manager
Source-Version: 1.0.10-2

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

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated network-manager package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 20 Jan 2016 16:16:13 +0100
Source: network-manager
Binary: network-manager network-manager-dev libnm-glib4 libnm-glib-dev 
libnm-glib-vpn1 libnm-glib-vpn-dev libnm-util2 libnm-util-dev libnm0 libnm-dev 
network-manager-dbg gir1.2-networkmanager-1.0
Architecture: source
Version: 1.0.10-2
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Michael Biebl 
Description:
 gir1.2-networkmanager-1.0 - 

Bug#800789: marked as done (pygccjit: FTBFS due to test failures during binNMU for python3.5 support)

[Debian Bug Tracking System]

Your message dated Wed, 20 Jan 2016 15:55:56 +
with message-id 
and subject line Bug#800789: fixed in pygccjit 0.4-5
has caused the Debian Bug report #800789,
regarding pygccjit: FTBFS due to test failures during binNMU for python3.5 
support
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.)


-- 
800789: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800789
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pygccjit
Version: 0.4-4
Severity: serious
Justification: fails to build from source (but built successfully in the past)

The binNMU for adding python3.5 support has failed on all archs it's so far
been tried on.  Here's the log extract for arm64 as an example:

--
Traceback (most recent call last):
  File "/«PKGBUILDDIR»/tests/test.py", line 190, in test_get_type_error
ctxt.get_type(-1)
  File "/gccjit/gccjit.pyx", line 53, in gccjit._gccjit.Context.get_type 
(gccjit/gccjit.c:2289)
OverflowError: can't convert negative value to enum gcc_jit_types

--
Ran 15 tests in 0.821s

FAILED (errors=1)
ABCDEFGHIJKLMNOPQRSTUVWXYZE: pybuild pybuild:262: 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:12: recipe for target 'build-arch' failed
make: *** [build-arch] Error 25
--- End Message ---
--- Begin Message ---
Source: pygccjit
Source-Version: 0.4-5

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 20 Jan 2016 12:42:08 +0100
Source: pygccjit
Binary: python-gccjit python-gccjit-dbg python3-gccjit python3-gccjit-dbg 
python-gccjit-doc
Architecture: source amd64 all
Version: 0.4-5
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Matthias Klose 
Description:
 python-gccjit - Python bindings for libgccjit
 python-gccjit-dbg - Python bindings for libgccjit (debug build)
 python-gccjit-doc - Python bindings for libgccjit (documentation)
 python3-gccjit - Python3 bindings for libgccjit
 python3-gccjit-dbg - Python3 bindings for libgccjit (debug build)
Closes: 800789
Changes:
 pygccjit (0.4-5) unstable; urgency=medium
 .
   * Ignore testsuite failures (one failing test). Closes: #800789.
Checksums-Sha1:
 9ed63ae8344de1e6a1d9ae01738393c00d9ebd2e 2174 pygccjit_0.4-5.dsc
 a7ba851202c501f596e4564a9c963e3b102f9fe8 2704 pygccjit_0.4-5.debian.tar.xz
 0bc6d1793d067e50787d9dc1d6d82521d3564719 333708 
python-gccjit-dbg_0.4-5_amd64.deb
 e2849c990756b3e89adfa0b633517b0a318a2101 75272 python-gccjit-doc_0.4-5_all.deb
 457435f5dc309b5aa7222e2b764361cb5de80791 48532 python-gccjit_0.4-5_amd64.deb
 64532c486ede469699275772939fe07a22712b5a 592208 
python3-gccjit-dbg_0.4-5_amd64.deb
 4ae1eace0111ac6ab0ba39f7917fe4f06b8a222a 66124 python3-gccjit_0.4-5_amd64.deb
Checksums-Sha256:
 49ac442ba729f89691678adde68be7f9a3df8fc9833a6960d86b95908dec9947 2174 
pygccjit_0.4-5.dsc
 0459360b750e93cf3dbcb13858a1370ac1d70587ae24a1c7790d092b3db9a03b 2704 
pygccjit_0.4-5.debian.tar.xz
 690c334ff6edd2011532d0b8d0fa87e863ec5479e9ec2be06c0e155a37accdb4 333708 
python-gccjit-dbg_0.4-5_amd64.deb
 58b5632131ebc934e9b023b2bc0bffbe511dd927488fd8be6a770c29abf7c40e 75272 
python-gccjit-doc_0.4-5_all.deb
 803b70f8b9dfe0195757204604fd8d0d56c214048885e1072a73f8e46f458fd0 48532 
python-gccjit_0.4-5_amd64.deb
 405c3acf35972a06d50b36c54cec0b4f6c818172d2ada6cc23f1265bb639f737 592208 
python3-gccjit-dbg_0.4-5_amd64.deb
 e33eb46c8b98e598185c89121a4474f0df424de2f89c1753a2f81e73b7470762 66124 
python3-gccjit_0.4-5_amd64.deb
Files:
 fc1ff18d9d582587728c30821aa492af 2174 python optional pygccjit_0.4-5.dsc
 51422e1131b80b07e1b9c27957baef79 2704 python 

Bug#810076: marked as done (network-manager: NM does not honor "push route" any more)

[Debian Bug Tracking System]

Your message dated Wed, 20 Jan 2016 15:54:57 +
with message-id 
and subject line Bug#809195: fixed in network-manager 1.0.10-2
has caused the Debian Bug report #809195,
regarding network-manager: NM does not honor "push route" any more
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.)


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

Dear Maintainer,

I have just upgraded network-manager from 1.0.6 to 1.0.10 just to
determine that my OpenVPN connection stopped working. Downgrading to
1.0.6 fixes the connection again.

In my configuration, the central OpenVPN server pushes some route to
the client with the

   push "route 192.168.x.x 255.255.x.x"

directive. Everything has been set up properly so whenever I make a

   ip route

on my nm-1.0.6 client I see the appropriate route. However, this has
changed with 1.0.10: The appropriate route is no longer listed when
doing a call to "ip route".

If this behaviour change is intended, I could not find documentation
on how to manually revert to the previous behaviour. If this change
was not done by intention, it is a regression we should trace and fix.
I am filing this bug report with network-manager (not
network-manager-openvpn) because downgrading network-manager-openvpn
alone did not have an effect. However, downgrading network-manager
(without downgrading network-manager-openvpn) already had the desired
effect.

My current (working) package combination is:
hi  network-manager   1.0.6-1
ii  network-manager-gnome 1.0.10-1
hi  network-manager-openvpn   1.0.6-3

Best regards,
Thomas

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

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

Versions of packages network-manager depends on:
ii  adduser3.113+nmu3
ii  dbus   1.10.6-1
ii  init-system-helpers1.24
ii  isc-dhcp-client4.3.3-5
ii  libbluetooth3  5.36-1
ii  libc6  2.21-6
ii  libdbus-1-31.10.6-1
ii  libdbus-glib-1-2   0.102-1
ii  libglib2.0-0   2.46.2-3
ii  libgnutls-deb0-28  3.3.19-1
ii  libgudev-1.0-0 230-2
ii  libmm-glib01.4.12-1
ii  libndp01.4-2
ii  libnewt0.520.52.18-1+b1
ii  libnl-3-2003.2.26-1
ii  libnl-genl-3-200   3.2.26-1
ii  libnl-route-3-200  3.2.26-1
ii  libnm0 1.0.10-1
ii  libpam-systemd 228-2+b1
ii  libpolkit-agent-1-00.105-14
ii  libpolkit-gobject-1-0  0.105-14
ii  libreadline6   6.3-8+b4
ii  libsoup2.4-1   2.52.1-1
ii  libsystemd0228-2+b1
ii  libteamdctl0   1.18-1
ii  libuuid1   2.27.1-1
ii  lsb-base   9.20150917
ii  policykit-10.105-14
ii  udev   228-2+b1
ii  wpasupplicant  2.3-2.3

Versions of packages network-manager recommends:
ii  crda3.13-1+b1
ii  dnsmasq-base2.75-1
ii  iptables1.4.21-2+b1
ii  iputils-arping  3:20121221-5+b2
ii  modemmanager1.4.12-1
ii  ppp 2.4.7-1+1

Versions of packages network-manager suggests:
ii  avahi-autoipd  0.6.32~rc+dfsg-1
pn  libteam-utils  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: network-manager
Source-Version: 1.0.10-2

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

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated network-manager 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: tagging 812093

[Debian Bug Tracking System]

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

> tags 812093 + confirmed
Bug #812093 [src:libimager-perl] libimager-perl: FTBFS: Failed 1/65 test 
programs. 0/4481 subtests failed.
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Bug#807349: marked as done (dwww: FTBFS: error: expected identifier or '(' before '__extension__')

[Debian Bug Tracking System]

Your message dated Wed, 20 Jan 2016 15:11:06 +
with message-id 
and subject line Bug#790273: fixed in publib 0.40-2
has caused the Debian Bug report #790273,
regarding dwww: FTBFS: error: expected identifier or '(' before '__extension__'
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.)


-- 
790273: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790273
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dwww
Version: 1.12.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,

dwww fails to build from source in unstable/amd64:

  [..]

  gcc -c -D_FORTIFY_SOURCE=2 -DVERSION='"1.12.1"' -g -O2
  -fstack-protector-strong -Wformat -Werror=format-security -Wall
  -Wextra -Wstrict-prototypes -Wmissing-prototypes -Werror -g  -o
  _build/dwww-cache.o dwww-cache.c
  In file included from /usr/include/string.h:634:0,
   from dwww-cache.c:30:
  /usr/include/publib/strutil.h:67:7: error: expected identifier or '('
  before '__extension__'
   char *strndup(const char *, size_t);
 ^
  Makefile:25: recipe for target '_build/dwww-cache.o' failed
  make[2]: *** [_build/dwww-cache.o] Error 1
  common.mk:190: recipe for target 'all' failed
  make[1]: *** [all] Error 2
  make[1]: Leaving directory
  '/home/lamby/temp/cdt.20151207215750.Wr0BRL256Q/dwww-1.12.1'
  dh_auto_build: make -j1 returned exit code 2
  debian/rules:12: 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
   `-


dwww.1.12.1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: publib
Source-Version: 0.40-2

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

Debian distribution maintenance software
pp.
Robert Luberda  (supplier of updated publib 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 23:18:43 +0100
Source: publib
Binary: publib-dev
Architecture: source i386
Version: 0.40-2
Distribution: unstable
Urgency: high
Maintainer: Debian QA Group 
Changed-By: Robert Luberda 
Description:
 publib-dev - library of miscellaneous C functions
Closes: 790273
Changes:
 publib (0.40-2) unstable; urgency=high
 .
   * QA upload:
 - maintainer set to Debian QA Group;
 - git packaging moved to the collab-maint project.
   * Introduced the following patches:
 - 001-Remove-strndup.patch to fix FTBFS on current gcc and glibc
   by removing declaration of strndup() function together with its
   implementation and man page (closes: #790273);
 - 0002-Fix-undefined-behavior-warning.patch to fix an off-by-one
   bug in base64 decoder resulting in an undefined behavior warning
   given by gcc-5;
 - 0003-Remove-Makefile-at-distclean.patch to make sure the generated
   Makefile is dropped, so that sequential builds do not fail;
 - 0004-Fix-spelling-errors-in-manpages.patch to fix spelling typos
   in `occurrence' and `occurred' words, noticed by lintian.
   in `occurrence' and `occurred' words, noticed by lintian;
 - 0005-Pass-LDFLAGS-to-test-programs.patch to use $(LDFLAGS) while
   linking test programs.
   * Mark the binary package as `Multi-Arch: same'.
   * Bump Standards-Version to 3.9.6 (no other changes needed).
Checksums-Sha1:
 6869637e7ca8e807e29680c8a17d1bde08b9fe31 1772 publib_0.40-2.dsc
 cc2c6c119490fa0a7d3e8e050e4bccbff73d78ad 8140 publib_0.40-2.debian.tar.xz
 3424010487b726175385c62dc300e20f9715fba1 154148 publib-dev_0.40-2_i386.deb
Checksums-Sha256:
 6a1902e360fd64a07a241d0d74cba89c1a573cbff61c8a3b34f357400f1ea0d4 1772 
publib_0.40-2.dsc
 659d335cfecd0496bf019959740bc20837351b5f808aaf9bb9332aa9e8e47a69 8140 

Bug#811465: marked as done (python-falcon: FTBFS: KeyError: 'logged_in')

[Debian Bug Tracking System]

Your message dated Wed, 20 Jan 2016 15:12:02 +
with message-id 
and subject line Bug#811465: fixed in python-falcon 0.3.0-5
has caused the Debian Bug report #811465,
regarding python-falcon: FTBFS: KeyError: 'logged_in'
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.)


-- 
811465: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811465
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Source: python-falcon
Source-Version: 0.3.0-5

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 20 Jan 2016 07:27:47 +
Source: python-falcon
Binary: python-falcon python3-falcon
Architecture: source amd64
Version: 0.3.0-5
Distribution: unstable
Urgency: medium
Maintainer: PKG OpenStack 
Changed-By: Thomas Goirand 
Description:
 python-falcon - supersonic micro-framework for building cloud APIs - Python 2.x
 python3-falcon - supersonic micro-framework for building cloud APIs - Python 
3.x
Closes: 811465 811490
Changes:
 python-falcon (0.3.0-5) unstable; urgency=medium
 .
   * Added patch to fix test_request_cookie_parsing which fixes FTBFS
 (Closes: #811490, #811465).
   * Fix debian/copyright ordering.
   * Add patch to fix some spelling mistakes.
Checksums-Sha1:
 d8d4825bacd0f49a2c6276de5243ea12b649829c 2370 python-falcon_0.3.0-5.dsc
 e13503dc8f396c3d3396da1bab103af13a84a596 5120 
python-falcon_0.3.0-5.debian.tar.xz
 b395b45e6927afdaf0f9a83b3f5a6db9b6cd8500 1209914 
python-falcon-dbgsym_0.3.0-5_amd64.deb
 021def2d510d2cca24e442aad0600b8fff44e25d 395524 python-falcon_0.3.0-5_amd64.deb
 12cea2718db10dd2a6bbb40f925d0773d45d4b96 2828710 
python3-falcon-dbgsym_0.3.0-5_amd64.deb
 867808ef6de56dc55a6d6f04229499ca4b663371 585294 
python3-falcon_0.3.0-5_amd64.deb
Checksums-Sha256:
 35a05e1d927eb01cfd7f7494694a29a3d8381ee6727812c62903e98815f8b5ed 2370 
python-falcon_0.3.0-5.dsc
 635a564adb381f855c96b61731c7a1659aec8cd35f772d71fd9de90a22589d79 5120 
python-falcon_0.3.0-5.debian.tar.xz
 e7be10efc4b49d0502af168a8e3c21a9c3757b5715d2f58cb37d7569d3e4955a 1209914 

Bug#808675: marked as done (liwc: FTBFS: strutil.h:67:7: error: expected identifier or '(' before '__extension__' char *strndup(const char *, size_t))

[Debian Bug Tracking System]

Your message dated Wed, 20 Jan 2016 15:11:06 +
with message-id 
and subject line Bug#790273: fixed in publib 0.40-2
has caused the Debian Bug report #790273,
regarding liwc: FTBFS: strutil.h:67:7: error: expected identifier or '(' before 
'__extension__'char *strndup(const char *, size_t)
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.)


-- 
790273: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790273
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: liwc
Version: 1.21-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,

liwc fails to build from source in unstable/amd64:

  [..]

  dh_auto_build -- \
CPPFLAGS="-D_FORTIFY_SOURCE=2" \
CFLAGS="-g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security" \
LDFLAGS="-Wl,-z,relro"
make -j1 CPPFLAGS=-D_FORTIFY_SOURCE=2 "CFLAGS=-g -O2 
-fstack-protector-strong -Wformat -Werror=format-security" LDFLAGS=-Wl,-z,relro
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20151221183809.aJRPcooGBx/liwc-1.21'
  gcc -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,-z,relro -o ccmtcnvt ccmtcnvt.c -lpub
  In file included from /usr/include/string.h:634:0,
   from ccmtcnvt.c:82:
  /usr/include/publib/strutil.h:67:7: error: expected identifier or '(' before 
'__extension__'
   char *strndup(const char *, size_t);
 ^
  Makefile:40: recipe for target 'ccmtcnvt' failed
  make[2]: *** [ccmtcnvt] Error 1
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20151221183809.aJRPcooGBx/liwc-1.21'
  dh_auto_build: make -j1 CPPFLAGS=-D_FORTIFY_SOURCE=2 CFLAGS=-g -O2 
-fstack-protector-strong -Wformat -Werror=format-security LDFLAGS=-Wl,-z,relro 
returned exit code 2
  debian/rules:7: recipe for target 'override_dh_auto_build' failed
  make[1]: *** [override_dh_auto_build] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151221183809.aJRPcooGBx/liwc-1.21'
  debian/rules:4: 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
   `-


liwc.1.21-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: publib
Source-Version: 0.40-2

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

Debian distribution maintenance software
pp.
Robert Luberda  (supplier of updated publib 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 23:18:43 +0100
Source: publib
Binary: publib-dev
Architecture: source i386
Version: 0.40-2
Distribution: unstable
Urgency: high
Maintainer: Debian QA Group 
Changed-By: Robert Luberda 
Description:
 publib-dev - library of miscellaneous C functions
Closes: 790273
Changes:
 publib (0.40-2) unstable; urgency=high
 .
   * QA upload:
 - maintainer set to Debian QA Group;
 - git packaging moved to the collab-maint project.
   * Introduced the following patches:
 - 001-Remove-strndup.patch to fix FTBFS on current gcc and glibc
   by removing declaration of strndup() function together with its
   implementation and man page (closes: #790273);
 - 0002-Fix-undefined-behavior-warning.patch to fix an off-by-one
   bug in base64 decoder resulting in an undefined behavior warning
   given by gcc-5;
 - 0003-Remove-Makefile-at-distclean.patch to make sure the generated
   Makefile is dropped, so that sequential builds do not fail;
 - 0004-Fix-spelling-errors-in-manpages.patch to fix spelling typos
   in `occurrence' and `occurred' words, noticed by lintian.
   in `occurrence' and `occurred' words, noticed by lintian;
 - 

Bug#811144: marked as done (FTBFS: error: expected identifier or '(' before '__extension__')

[Debian Bug Tracking System]

Your message dated Wed, 20 Jan 2016 15:11:06 +
with message-id 
and subject line Bug#790273: fixed in publib 0.40-2
has caused the Debian Bug report #790273,
regarding FTBFS: error: expected identifier or '(' before '__extension__'
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.)


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

dwww fails to build in unstable:

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> creating /<>/scripts/_build/functions.sh
> gcc -c -Wdate-time -D_FORTIFY_SOURCE=2 -DVERSION='"1.12.1"' -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wextra 
> -Wstrict-prototypes -Wmissing-prototypes -Werror -g  -o _build/dwww-cache.o 
> dwww-cache.c
> In file included from /usr/include/string.h:634:0,
>  from dwww-cache.c:30:
> /usr/include/publib/strutil.h:67:7: error: expected identifier or '(' before 
> '__extension__'
>  char *strndup(const char *, size_t);
>^
> Makefile:25: recipe for target '_build/dwww-cache.o' failed

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: publib
Source-Version: 0.40-2

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

Debian distribution maintenance software
pp.
Robert Luberda  (supplier of updated publib 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 23:18:43 +0100
Source: publib
Binary: publib-dev
Architecture: source i386
Version: 0.40-2
Distribution: unstable
Urgency: high
Maintainer: Debian QA Group 
Changed-By: Robert Luberda 
Description:
 publib-dev - library of miscellaneous C functions
Closes: 790273
Changes:
 publib (0.40-2) unstable; urgency=high
 .
   * QA upload:
 - maintainer set to Debian QA Group;
 - git packaging moved to the collab-maint project.
   * Introduced the following patches:
 - 001-Remove-strndup.patch to fix FTBFS on current gcc and glibc
   by removing declaration of strndup() function together with its
   implementation and man page (closes: #790273);
 - 0002-Fix-undefined-behavior-warning.patch to fix an off-by-one
   bug in base64 decoder resulting in an undefined behavior warning
   given by gcc-5;
 - 0003-Remove-Makefile-at-distclean.patch to make sure the generated
   Makefile is dropped, so that sequential builds do not fail;
 - 0004-Fix-spelling-errors-in-manpages.patch to fix spelling typos
   in `occurrence' and `occurred' words, noticed by lintian.
   in `occurrence' and `occurred' words, noticed by lintian;
 - 0005-Pass-LDFLAGS-to-test-programs.patch to use $(LDFLAGS) while
   linking test programs.
   * Mark the binary package as `Multi-Arch: same'.
   * Bump Standards-Version to 3.9.6 (no other changes needed).
Checksums-Sha1:
 6869637e7ca8e807e29680c8a17d1bde08b9fe31 1772 publib_0.40-2.dsc
 cc2c6c119490fa0a7d3e8e050e4bccbff73d78ad 8140 publib_0.40-2.debian.tar.xz
 3424010487b726175385c62dc300e20f9715fba1 154148 publib-dev_0.40-2_i386.deb
Checksums-Sha256:
 6a1902e360fd64a07a241d0d74cba89c1a573cbff61c8a3b34f357400f1ea0d4 1772 
publib_0.40-2.dsc
 659d335cfecd0496bf019959740bc20837351b5f808aaf9bb9332aa9e8e47a69 8140 
publib_0.40-2.debian.tar.xz
 e32d90f5e6915cd0f1016ecc213c186cd822c59bde84ddecdab9c0ee66e85ba4 154148 
publib-dev_0.40-2_i386.deb
Files:
 9ff704916b686bd6acdc9c54abed5fd5 1772 libdevel optional publib_0.40-2.dsc
 fd5598770a8847057b9976f0787d739b 8140 libdevel optional 
publib_0.40-2.debian.tar.xz
 7ddf34ea9b8e4626174630dd9d2eaa8e 154148 libdevel optional 
publib-dev_0.40-2_i386.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWnrdrAAoJEGMd51U76K/UJQ0QAJHaKs0Yd5neCbovUMa4JMYT
ltITXIu69eLZ+OYGPSFUnSpwYRcWAMnH1LC7BP7tqPZDu3trhjMqqRXKtJ0dE58x

Bug#811105: marked as done (python-dcos: FTBFS: /usr/bin/python2.7: No module named pytest)

[Debian Bug Tracking System]

Your message dated Wed, 20 Jan 2016 15:11:52 +
with message-id 
and subject line Bug#811105: fixed in python-dcos 0.2.0-2
has caused the Debian Bug report #811105,
regarding python-dcos: FTBFS: /usr/bin/python2.7: No module named pytest
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.)


-- 
811105: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811105
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-dcos
Version: 0.2.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,

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

  [..]

 debian/rules override_dh_auto_test
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160115174931.AKTD5UK6WO/python-dcos-0.2.0'
  pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
  pyversions: missing debian/pyversions file, fall back to supported versions
  py3versions: no X-Python3-Version in control file, using supported versions
  set -e ; for pyvers in 2.7 3.4 3.5; do \
python$pyvers -m pytest -p no:cacheprovider tests ; \
  done
  /usr/bin/python2.7: No module named pytest
  debian/rules:25: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 1
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160115174931.AKTD5UK6WO/python-dcos-0.2.0'
  debian/rules:10: 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-dcos.0.2.0-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: python-dcos
Source-Version: 0.2.0-2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 20 Jan 2016 14:59:31 +0800
Source: python-dcos
Binary: python-dcos python3-dcos
Architecture: source all
Version: 0.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: PKG OpenStack 
Changed-By: Thomas Goirand 
Description:
 python-dcos - Datacenter Operating System (DCOS) CLI - Python 2.7
 python3-dcos - DCOS Common Modules - Python 3.x
Closes: 811105
Changes:
 python-dcos (0.2.0-2) unstable; urgency=medium
 .
   * Added missing build-depends: python{3,}-pytest (Closes: #811105).
   * Fixed debian/copyright ordering.
Checksums-Sha1:
 1a71b2c30559be1d5c53429be88c506db9c90749 2505 python-dcos_0.2.0-2.dsc
 6a024218656fa54b286c5bb3eef11d19a59be65e 2676 python-dcos_0.2.0-2.debian.tar.xz
 45be6a1b721538bc017abb32ceb7c3b8d0d2410c 35372 python-dcos_0.2.0-2_all.deb
 1f16bdc27d89bb1e0feeb8c5d69b76cda5ab03c3 35466 python3-dcos_0.2.0-2_all.deb
Checksums-Sha256:
 ad3dcc352c584703da00d8240a525be8823bfe019478629c3e972e1aab20a86b 2505 
python-dcos_0.2.0-2.dsc
 43d2a2c0c8827f4366f9e21e3b4845b9733a9381cb64a6d8d55e314901c88a6a 2676 
python-dcos_0.2.0-2.debian.tar.xz
 63b4a0b241270c8a90181897300f42808c875427c27787291594ac6db5b2dd48 35372 
python-dcos_0.2.0-2_all.deb
 b8abfbb5a04cba8f9dea48ea08f3676adad86078094322b17e862bd3c320571c 35466 
python3-dcos_0.2.0-2_all.deb
Files:
 ab2fc8e1eabad0a0b5a978c6c0eb89c7 2505 python optional python-dcos_0.2.0-2.dsc
 e5d579e5db518d42b93b910edef26340 2676 python optional 
python-dcos_0.2.0-2.debian.tar.xz
 e6656fc96e2ef8c5b55352c25fdc8eab 35372 python optional 
python-dcos_0.2.0-2_all.deb
 56353435fb926ca15c2a7c4b06ca10ac 35466 python optional 
python3-dcos_0.2.0-2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWnzEfAAoJENQWrRWsa0P+xrUQAJoNn8izt5Ogx2NfRrCiEsNV
OkOTbvOWAHbodys7irLQb4W9DvXIO13Yl5x9bsOrKQnmM1TabqMHcVI9Sx6TQzds

Bug#797896: marked as done (FTBFS: error: 'buildString' is not a member of 'Puma::StrCol')

[Debian Bug Tracking System]

Your message dated Wed, 20 Jan 2016 15:17:16 +
with message-id 
and subject line Bug#797896: fixed in undertaker 1.6.1-1
has caused the Debian Bug report #797896,
regarding FTBFS: error: 'buildString' is not a member of 'Puma::StrCol'
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.)


-- 
797896: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797896
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: undertaker
Version: 1.6-2.1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

your package no longer builds in sid, see logs at
https://buildd.debian.org/status/logs.php?pkg=undertaker=1.6-2.1%2Bb1=sid

Cheers,
Julien


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: undertaker
Source-Version: 1.6.1-1

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

Debian distribution maintenance software
pp.
Reinhard Tartler  (supplier of updated undertaker 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 06:15:12 -0500
Source: undertaker
Binary: undertaker
Architecture: source
Version: 1.6.1-1
Distribution: unstable
Urgency: medium
Maintainer: Christoph Egger 
Changed-By: Reinhard Tartler 
Description:
 undertaker - variability-aware tool for static code analysis
Closes: 769137 797896
Changes:
 undertaker (1.6.1-1) unstable; urgency=medium
 .
   * New upstream release
 - Incorporated patch for undertaker-checkpatch (Closes: #769137)
   * Add patch to fix FTBFS 'buildString' is not a member of 'Puma::StrCol'
 (Closes: #797896)
   * Relax CFLAGS (Don't add -Werror to everything)
Checksums-Sha1:
 897ac7fb99293c8fcbe08e0d5bd89e4921f4b9c4 2005 undertaker_1.6.1-1.dsc
 53afdd93d8617acb7bb9ebf2b1457356c4bd19df 1581360 undertaker_1.6.1.orig.tar.xz
 38a9f0da381b25b0725198745da9787214c32426 6384 undertaker_1.6.1-1.debian.tar.xz
Checksums-Sha256:
 869a8c43d005fcead9dc1c92183449005710c3d7b16635db9ac468e94240028e 2005 
undertaker_1.6.1-1.dsc
 579f3c3cf961a655d5943b86fbc93402f57c47bfb96374c838985d1014ae0bf3 1581360 
undertaker_1.6.1.orig.tar.xz
 d88fb071bad10ed1d895c55bcafd5913ac7b60f42278ad27841ea32dbac657c0 6384 
undertaker_1.6.1-1.debian.tar.xz
Files:
 81bd05742e04962997a889e57e2be19a 2005 devel optional undertaker_1.6.1-1.dsc
 06bab0b89f38e4b2f40b8c64c5d5a232 1581360 devel optional 
undertaker_1.6.1.orig.tar.xz
 346d635614a8df9545bc57f40dd3e64b 6384 devel optional 
undertaker_1.6.1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQGcBAEBCAAGBQJWnuZUAAoJEIuAbIZKeKRF2toMALWM2TGm0HOyvvfgNYmvsi5Q
m6KLGGfxwltVg9IN/4VLDVS/uQF/J9VXxOClLTwllGzzAQmoR1uTQB8lw9rdRiP+
o40b8kA44uMoLxWS6/3R6zrLNROPtUQrZxYsPLAffEpebhxg/GY12/vFAxKAsA5I
Nf5U6Qe7lbfCkxCgxdUkZMjEnnGPL7h6rEpEpydRKH/tGQEg7lyOUzZgT6lNkp60
1Fdpzo9X2c6j7b89C2lFm4XH5oef9v2bpsgbnEwVSmoVJyarstco7JWJ6XTiA9ih
XBWPr1M5k3AcJjOQzj3rJvrvSbm28K9oEMX0dVXUUItm1FDt1Kz2gxxHXBtP18w8
YQBO9Yrf99F0aEp7HP0uBvuJVaIEORYuMNfivaxYoMoL98Oon3H5bR2tLHkP22D/
1JGUPgHBgcWN/cwGkdb24vDpT2cCXp7z6P3WOqSyDD5P4fEcK+0Slu5J3ZfzHVcs
tEkJaM12A+Sc4pGIeN9q/HEhP/02OpZV1rZ5J3Hr9w==
=Qbq4
-END PGP SIGNATURE End Message ---

Bug#788168: marked as done (python-greenlet-doc: copyright file missing after upgrade (policy 12.5))

[Debian Bug Tracking System]

Your message dated Wed, 20 Jan 2016 19:00:38 +
with message-id 
and subject line Bug#788168: fixed in python-greenlet 0.4.9-1
has caused the Debian Bug report #788168,
regarding python-greenlet-doc: copyright file missing after upgrade (policy 
12.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.)


-- 
788168: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788168
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-greenlet-doc
Version: 0.4.7-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package misses the copyright
file after an upgrade, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory.

This was observed on the following upgrade paths:

  jessie -> sid

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

  MISSING COPYRIGHT FILE: /usr/share/doc/python-greenlet-doc/copyright
  # ls -lad /usr/share/doc/python-greenlet-doc
  drwxr-xr-x 2 root root 40 May 16 22:35 /usr/share/doc/python-greenlet-doc
  # ls -la /usr/share/doc/python-greenlet-doc/
  total 0
  drwxr-xr-x   2 root root   40 May 16 22:35 .
  drwxr-xr-x 114 root root 2440 May 16 22:35 ..


Additional info may be available here:
https://wiki.debian.org/MissingCopyrightFile

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.mainstscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


cheers,

Andreas


python-greenlet-doc_0.4.7-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-greenlet
Source-Version: 0.4.9-1

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated python-greenlet 
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: Sat, 05 Sep 2015 16:58:57 +0200
Source: python-greenlet
Binary: python-greenlet-dbg python3-greenlet-dbg python-greenlet-doc 
python-greenlet-dev python-greenlet python3-greenlet
Architecture: source amd64 all
Version: 0.4.9-1
Distribution: unstable
Urgency: low
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 python-greenlet - Lightweight in-process concurrent programming
 python-greenlet-dbg - Lightweight in-process concurrent programming - 
debugging symbols
 python-greenlet-dev - Lightweight in-process concurrent programming - 
development files
 python-greenlet-doc - Lightweight in-process concurrent programming - 
documentation
 python3-greenlet - Lightweight in-process concurrent programming (python3)
 python3-greenlet-dbg - Lightweight in-process concurrent programming - 
debugging symbols
Closes: 681257 788168 793802 811433
Changes:
 python-greenlet (0.4.9-1) unstable; urgency=low
 .
   * New upstream release.
   * Do not depend on, only suggest python-greenlet for -doc (closes: #811433).
   * Re-enable python3-greenlet-dbg package (closes: #793802).
   * Don't symlink doc/ directory between packages (closes: #788168).
   * Use upstream test suite (closes: #681257).
   * Build using pybuild.
   * Remove ppc64le.diff , applied upstream.
   * Update watch file.
Checksums-Sha1:
 03e43f2a77e3017420e48e8e8de203632767d650 2292 python-greenlet_0.4.9-1.dsc
 6643237458c421ac5eac8681cc6fa9983d3550f7 54489 
python-greenlet_0.4.9.orig.tar.gz
 2779f0035ce5ca9a9af26a68bf32b1558b3d435f 6680 

Bug#811433: marked as done (python-greenlet-doc: Exact version depends makes package unsafe for binNMUs)

[Debian Bug Tracking System]

Your message dated Wed, 20 Jan 2016 19:00:38 +
with message-id 
and subject line Bug#811433: fixed in python-greenlet 0.4.9-1
has caused the Debian Bug report #811433,
regarding python-greenlet-doc: Exact version depends makes package unsafe for 
binNMUs
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.)


-- 
811433: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811433
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-greenlet-doc
Version: 0.4.7-1
Severity: grave
Justification: renders package unusable

In sid and all testing archs except amd64 and i386 python-greenlet-doc is
uninstallable:

apt-get install python-greenlet-doc
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 python-greenlet-doc : Depends: python-greenlet (= 0.4.7-1) but it is not going 
to be installed
E: Unable to correct problems, you have held broken packages.

This is due to the way the doc directory is handled in debian/rules:

override_dh_installdocs:
dh_installdocs --link-doc=python-greenlet

This is currently one of the blockers for getting python3.5 as default in
testing, so please resolve ASAP.

Scott K
--- End Message ---
--- Begin Message ---
Source: python-greenlet
Source-Version: 0.4.9-1

We believe that the bug you reported is fixed in the latest version of
python-greenlet, 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 python-greenlet 
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: Sat, 05 Sep 2015 16:58:57 +0200
Source: python-greenlet
Binary: python-greenlet-dbg python3-greenlet-dbg python-greenlet-doc 
python-greenlet-dev python-greenlet python3-greenlet
Architecture: source amd64 all
Version: 0.4.9-1
Distribution: unstable
Urgency: low
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 python-greenlet - Lightweight in-process concurrent programming
 python-greenlet-dbg - Lightweight in-process concurrent programming - 
debugging symbols
 python-greenlet-dev - Lightweight in-process concurrent programming - 
development files
 python-greenlet-doc - Lightweight in-process concurrent programming - 
documentation
 python3-greenlet - Lightweight in-process concurrent programming (python3)
 python3-greenlet-dbg - Lightweight in-process concurrent programming - 
debugging symbols
Closes: 681257 788168 793802 811433
Changes:
 python-greenlet (0.4.9-1) unstable; urgency=low
 .
   * New upstream release.
   * Do not depend on, only suggest python-greenlet for -doc (closes: #811433).
   * Re-enable python3-greenlet-dbg package (closes: #793802).
   * Don't symlink doc/ directory between packages (closes: #788168).
   * Use upstream test suite (closes: #681257).
   * Build using pybuild.
   * Remove ppc64le.diff , applied upstream.
   * Update watch file.
Checksums-Sha1:
 03e43f2a77e3017420e48e8e8de203632767d650 2292 python-greenlet_0.4.9-1.dsc
 6643237458c421ac5eac8681cc6fa9983d3550f7 54489 
python-greenlet_0.4.9.orig.tar.gz
 2779f0035ce5ca9a9af26a68bf32b1558b3d435f 6680 
python-greenlet_0.4.9-1.debian.tar.xz
 7e71ea2cbb1f58c6804049234620adcc5bb7f081 47264 
python-greenlet-dbg_0.4.9-1_amd64.deb
 102f6aad9471c9a6bbed84db3c210d5576eb5e7e 6488 
python-greenlet-dev_0.4.9-1_amd64.deb
 2f0027d2f042d8d9d1876aa92ad1c9ddc077717a 42810 
python-greenlet-doc_0.4.9-1_all.deb
 cdba9dfb7deec9d632170e55b013ea6af2de648f 18908 
python-greenlet_0.4.9-1_amd64.deb
 b967fbf5dee8cf78ec681921f33d66084f76ca4a 67104 
python3-greenlet-dbg_0.4.9-1_amd64.deb
 38075d7e6f53b7dd8b3c41365a4c391611961202 19034 

Bug#789670: marked as done (python-future,python-pies2overrides: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Wed, 20 Jan 2016 19:22:41 +
with message-id 
and subject line Bug#812066: Removed package(s) from unstable
has caused the Debian Bug report #789670,
regarding python-future,python-pies2overrides: error when trying to install 
together
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.)


-- 
789670: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789670
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-future,python-pies2overrides
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Selecting previously unselected package python-pies2overrides.
  Preparing to unpack .../python-pies2overrides_2.6.1-1_all.deb ...
  Unpacking python-pies2overrides (2.6.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-pies2overrides_2.6.1-1_all.deb (--unpack):
   trying to overwrite '/usr/lib/python2.7/dist-packages/xmlrpc/client.py', 
which is also in package python-future 0.14.3-1
  Errors were encountered while processing:
   /var/cache/apt/archives/python-pies2overrides_2.6.1-1_all.deb


This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

usr/lib/python2.7/dist-packages/html/__init__.py
usr/lib/python2.7/dist-packages/html/entities.py
usr/lib/python2.7/dist-packages/html/parser.py
usr/lib/python2.7/dist-packages/http/__init__.py
usr/lib/python2.7/dist-packages/http/client.py
usr/lib/python2.7/dist-packages/http/cookiejar.py
usr/lib/python2.7/dist-packages/http/cookies.py
usr/lib/python2.7/dist-packages/http/server.py
usr/lib/python2.7/dist-packages/xmlrpc/__init__.py
usr/lib/python2.7/dist-packages/xmlrpc/client.py


This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


python-future=0.14.3-1_python-pies2overrides=2.6.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 2.6.7-0.1+rm

Dear submitter,

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

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

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

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

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

Processed: tagging 811479

[Debian Bug Tracking System]

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

> tags 811479 - moreinfo
Bug #811479 {Done: Ben Hutchings } [initramfs-tools-core] 
boot fails in "run-init -n ..."
Bug #811566 {Done: Ben Hutchings } [initramfs-tools-core] 
run-init: opening console: No such file or directory
Bug #812116 {Done: Ben Hutchings } [initramfs-tools-core] 
newly built initrd complains about missing init
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.
> 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
812116: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812116
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#796647: marked as done (python-sptest: FTBFS: Missing Build-Depends on python)

[Debian Bug Tracking System]

Your message dated Wed, 20 Jan 2016 19:05:19 +
with message-id 
and subject line Bug#796647: fixed in python-sptest 0.2.1-3
has caused the Debian Bug report #796647,
regarding python-sptest: FTBFS: Missing Build-Depends on python
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.)


-- 
796647: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796647
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-sptest
Version: 0.2.1-2.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-sptest fails to build from source in unstable/amd64 due to
missing Build-Depends on python (dh-python Depends on python3):

  [..]

   debian/rules build
  python setup.py build
  make: python: Command not found
  debian/rules:15: recipe for target 'build' failed
  make: *** [build] Error 127
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/python-sptest_0.2.1-2.1.build1.log.gz


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Sat Aug 22 19:24:17 GMT+12 2015
I: pbuilder-time-stamp: 1440314657
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /dev/shm
I: Mounting /sys
I: policy-rc.d already exists
I: Installing the build-deps
 -> Attempting to satisfy build-dependencies
 -> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team 
Description: Dummy package to satisfy dependencies with aptitude - created by 
pbuilder
 This package was created automatically by pbuilder to satisfy the
 build-dependencies of the package being currently built.
Depends: dh-python, debhelper (>= 5)
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20247 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...
Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring 
anyway as you requested:
 pbuilder-satisfydepends-dummy depends on dh-python; however:
  Package dh-python is not installed.

Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
Reading package lists...
Building dependency tree...
Reading state information...
Initializing package states...
Writing extended state information...
Building tag database...
The following NEW packages will be installed:
  dh-python{a} libexpat1{a} libmpdec2{a} libpython3-stdlib{a} 
  libpython3.4-minimal{a} libpython3.4-stdlib{a} libssl1.0.0{a} 
  mime-support{a} python3{a} python3-minimal{a} python3.4{a} 
  python3.4-minimal{a} 
0 packages upgraded, 12 newly installed, 0 to remove and 0 not upgraded.
Need to get 5794 kB of archives. After unpacking 26.9 MB will be used.
Writing extended state information...
Get: 1 http://ftp.de.debian.org/debian/ unstable/main libmpdec2 amd64 2.4.1-1 
[85.7 kB]
Get: 2 http://ftp.de.debian.org/debian/ unstable/main libssl1.0.0 amd64 
1.0.2d-1 [1274 kB]
Get: 3 http://ftp.de.debian.org/debian/ unstable/main libpython3.4-minimal 
amd64 3.4.3-8 [495 kB]
Get: 4 http://ftp.de.debian.org/debian/ unstable/main mime-support all 3.59 
[36.4 kB]
Get: 5 http://ftp.de.debian.org/debian/ unstable/main libpython3.4-stdlib amd64 
3.4.3-8 [2057 kB]
Get: 6 http://ftp.de.debian.org/debian/ unstable/main libexpat1 amd64 2.1.0-7 
[80.0 kB]
Get: 7 http://ftp.de.debian.org/debian/ unstable/main python3.4-minimal amd64 
3.4.3-8 [1401 kB]
Get: 8 http://ftp.de.debian.org/debian/ unstable/main python3-minimal amd64 
3.4.3-4 [34.7 kB]
Get: 9 http://ftp.de.debian.org/debian/ unstable/main python3.4 amd64 3.4.3-8 
[219 kB]
Get: 10 http://ftp.de.debian.org/debian/ unstable/main libpython3-stdlib amd64 
3.4.3-4 [18.1 kB]

Bug#800285: marked as done (cgi-extratags-perl: Please migrate a supported debhelper compat level)

[Debian Bug Tracking System]

Your message dated Wed, 20 Jan 2016 19:21:21 +
with message-id 
and subject line Bug#812063: Removed package(s) from unstable
has caused the Debian Bug report #800285,
regarding cgi-extratags-perl: 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.)


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

Hi,

The package cgi-extratags-perl 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 ---
Version: 0.03-1.2+rm

Dear submitter,

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

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

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

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

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

Bug#807760: marked as done (cfflib: maintainer address bounces)

[Debian Bug Tracking System]

Your message dated Wed, 20 Jan 2016 19:33:48 +
with message-id 
and subject line Bug#807760: fixed in cfflib 2.0.5-2
has caused the Debian Bug report #807760,
regarding cfflib: maintainer address bounces
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.)


-- 
807760: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807760
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cfflib
Tags: sid
Severity: serious

The maintainer address for cfflib bounces, see below.

Ansgar

Mail Delivery System writes:
> This message was created automatically by mail delivery software.
>
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es) failed:
>
>   deb...@unidesign.ch
> SMTP error from remote mail server after RCPT TO::
> host unidesign.ch [194.126.200.43]: 550 No Such User Here"
>
> -- This is a copy of the message, including all the headers. --
>
[...]
> To: Stephan Gerhard , Mattia Rizzolo 
[...]
> Subject: cfflib_2.0.5-1.1_source.changes ACCEPTED into unstable
> Message-Id: 
> Date: Sat, 12 Dec 2015 00:18:58 +
--- End Message ---
--- Begin Message ---
Source: cfflib
Source-Version: 2.0.5-2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 20 Jan 2016 19:18:17 +
Source: cfflib
Binary: python-cfflib
Architecture: source
Version: 2.0.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Mattia Rizzolo 
Description:
 python-cfflib - Multi-modal connectome and metadata management and integration
Closes: 807760
Changes:
 cfflib (2.0.5-2) unstable; urgency=medium
 .
   * QA upload.
   * Orphan the package.  Closes: #807760
   * Run wrap-and-sort
Checksums-Sha1:
 819098e1c296a290e130d78040cfe5c74e4f2f6d 1890 cfflib_2.0.5-2.dsc
 edbc16f60b445748e420025b539dba004f2717d9 3536 cfflib_2.0.5-2.debian.tar.xz
Checksums-Sha256:
 4b397696f961b53fbad897e6fe41e35c490d9489b4951fbf786300d5d2ad2403 1890 
cfflib_2.0.5-2.dsc
 5d3de7ae40bcd0dc12cc0941e1763c5120be81a0acd37984f5cbe7c5d19027e8 3536 
cfflib_2.0.5-2.debian.tar.xz
Files:
 b7ee051389746dff44ff9f301d6f2304 1890 python extra cfflib_2.0.5-2.dsc
 d06380fa8eafd6ef327a08ed394c3b24 3536 python extra cfflib_2.0.5-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWn92WAAoJEEsEP825REVADX4P/2zAvNqYWMi8PjnIOD9fvCVr
5NfESyYBPPjkh+Wk7O339eQqsScIwAidaDjB2zBknciuET3r0LS92s+4BXpzt+QE
Wl3gaNyZZ5d5V9GFgjuCfqdI0zgrdGvt80AOdr//zdvI8n/dXjyzn9IwwUwarZXL
CiA3w/HIOPc/cnCkCFcdBjQL0mOpj/4rQgFuKIzBlzsMAmxI+HoPc+Kaz/CLx+GY
qwh/P/1t5kCRePvZyNpyG55UuGPgl67DW5Dccpzte8ciOdyeQYytBUJqVHBELTSN
H3iWhiPsdVicwI62YVPRN4Ld1vy/lhSJglhmTsxcCEUcJIzEcXAVEvTA5K2wvTB3
8B2oBy+MATZ7OrU1ZylMSlwk2jqQI9Fx7zeKVX2Yf0yKUg9N9Zul5rpozkcgH/gv
n2JjX/qTtgMV+x/YM6umr3AquDnpqgAVA+CBjqLUy0QkDF6O6N5m8lB7KwrWXVMO
Ko72IBZixYgMSLQVj8tFn6+s7NlIlYbikpo3tfeaeuiiqAgLmxKbzjC/m2SggvDU
wZZHOqdABcW2zWoxJqnqsj5Qn67Jp8RAL0sBR11V72rHVHbWcGBz1CU6VaPX6+WC
uKWiczC2k92OfNQ32P/PdpvH6VI+T6ve7U9yTOM2F/lhTW5rdpHNNsFjhGI6XRA/
6bJAafdX5H/KQlVfZQWP
=BK/o
-END PGP SIGNATURE End Message ---

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

[Debian Bug Tracking System]

Your message dated Wed, 20 Jan 2016 19:50:01 +
with message-id 
and subject line Bug#811304: fixed in wmaker 0.95.7-3
has caused the Debian Bug report #811304,
regarding After recent system upgrade, wdm does not start anymore with "version 
`LIBWRASTER3' not found (required by wdmLogin)"
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.)


-- 
811304: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811304
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
-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-
--- End Message ---
--- Begin Message ---
Source: wmaker
Source-Version: 0.95.7-3

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 20 Jan 2016 20:19:27 +0100
Source: wmaker
Binary: wmaker wmaker-common libwraster-dev libwraster5 libwings-dev libwutil5 
libwings3 wmaker-dbg
Architecture: all source
Version: 0.95.7-3
Distribution: unstable
Urgency: low
Maintainer: Debian Window Maker Team 
Changed-By: Andreas Metzler 

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

[Debian Bug Tracking System]

Your message dated Wed, 20 Jan 2016 19:50:01 +
with message-id 
and subject line Bug#811304: fixed in wmaker 0.95.7-3
has caused the Debian Bug report #811304,
regarding wdmLogin: /usr/lib/x86_64-linux-gnu/libwraster.so.5: version 
`LIBWRASTER3' 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.)


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

Package: libwraster5
Severity: grave
Version: 0.95.7-2

Hi,

upgrading libwraster5 broke wdm with the above error message.

I hope that helps,

Snark on a few Debian IRC channels
--- End Message ---
--- Begin Message ---
Source: wmaker
Source-Version: 0.95.7-3

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 20 Jan 2016 20:19:27 +0100
Source: wmaker
Binary: wmaker wmaker-common libwraster-dev libwraster5 libwings-dev libwutil5 
libwings3 wmaker-dbg
Architecture: all source
Version: 0.95.7-3
Distribution: unstable
Urgency: low
Maintainer: Debian Window Maker Team 
Changed-By: Andreas Metzler 
Closes: 811304
Description: 
 libwings3  - Window Maker's own widget set - runtime library
 libwings-dev - Window Maker's own widget set
 libwraster5 - Shared libraries of Window Maker rasterizer
 libwraster-dev - Static libraries and headers of Window Maker rasterizer
 libwutil5  - Window Maker's own widget set - utility library
 wmaker-common - Window Maker - Architecture independent files
 wmaker-dbg - Debugging symbols for WindowMaker packages
 wmaker - NeXTSTEP-like window manager for X
Changes:
 wmaker (0.95.7-3) unstable; urgency=low
 .
   * Patch back libwraster symbol version to LIBWRASTER3. Temporarily mark
 RDrawLine@LIBWRASTER3 with a dep >= 0.95.7-3~ to force lockstep upgrades
 from broken 0.95.7-2. Closes: #811304
Checksums-Sha1: 
 69e6208503a50be91290a167fa34c4640b9d5828 2641 wmaker_0.95.7-3.dsc
 e854994c72ea50b5f57a0c06a98af78b21c888df 484804 wmaker_0.95.7-3.debian.tar.xz
 8cba26df94fb646cd6373c6f29bd2bf14911e932 1553180 wmaker-common_0.95.7-3_all.deb
Checksums-Sha256: 
 1c6da968cde70634870b8a6d0f4ef94a53331eb50a38758f59732160da610184 2641 
wmaker_0.95.7-3.dsc
 1bb68b4bf4d4599c4638dfd6cf44a932f108ef6e100b817d901ec4dbf66c22e8 484804 
wmaker_0.95.7-3.debian.tar.xz
 d4232cdd51f890ab208d66a984785c08e8804b10d5401ef5d68299a92c9ba6fb 1553180 
wmaker-common_0.95.7-3_all.deb
Files: 
 cb4f5bafa209a2d3a908b7a40581df4a 2641 x11 optional wmaker_0.95.7-3.dsc
 6e0fa1d5cc11cadbedb4f2320b6334e5 484804 x11 optional 
wmaker_0.95.7-3.debian.tar.xz
 2dcf4ac950cebabd5b6eceedb1208d9d 1553180 x11 optional 
wmaker-common_0.95.7-3_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJWn+E+AAoJEKVPAYVDghSEzosP/0ZYCMmzUk1pwNvN0XEg+8TK
JPhv5GqwGFeH/K4wJzHw1VfoCL5LLDficZ6h5Ivt75RzFjOnH2OdmhZ0ouMkSMF7
K9TcQOp5pGH1itY1LvbOFQkR8TkSg9/OIYpkF0rB9lMoZRUXd8ztJVF8Z42H26gU
qdjZtMeXtw0xg5la6gHu0l+T2C4ru/rKirJtwDtkgfOgny+x7I33Z4INXv+SQ9Zs
HoIjLqIQ0ebUFIatXLnlnEdRdexN6xfAI77INzbIn7knfJImlrC0aL8PI5h9rvbV
aS6HtkXRYakFCO1Z02j/Qs1CrW/+lDwlKoyYSbFerBLAv56MJBS7pM7YnSSuTDMz
CdyebvAxcGugZdgREDb7c165CTf3Ocbdx3Em8uYd1KiP0rs83aeUzExtfpcQ0u/o
fRZzl1I5qruyJf3OhTsvRHupYxI4Kyr1v+OnBXBU23sR4dXr8J1pFyVgNw867+Sr
epmx65EmqvLmMx4BAxVglT1gIVVs/9rDq8jD1M1eHrMBk5VPAuEyAU/F4EI42hXM
b3RG1yQ+3hpKCe4lfNFDLFgdb7sH1fXK/1zT8SMe9ADgmvZPdgkuKLEDj1K4z4vt
tHxHO6+EQBs9xsACVVXgwG2+kW/cbZsj/P5nfkuoDqZpogJLXdgvRe74IFEEgvi3
TbxzTJLMn4kGP9sbSCJr
=Aq2L
-END PGP SIGNATURE End Message ---

Bug#805610: marked as done (python-lamson: maintainer address bounces)

[Debian Bug Tracking System]

Your message dated Wed, 20 Jan 2016 19:49:11 +
with message-id 
and subject line Bug#805610: fixed in python-lamson 1.0pre11-1.3
has caused the Debian Bug report #805610,
regarding python-lamson: maintainer address bounces
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.)


-- 
805610: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805610
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-lamson
Tags: sid
Severity: serious
X-Debbugs-Cc: David Watson 

The maintainer address for python-lamson bounces:

+---
| This message was created automatically by mail delivery software.
|
| A message that you sent could not be delivered to one or more of its
| recipients. This is a permanent error. The following address(es) failed:
|
|   da...@kutoken.com
| Unrouteable address
+---

Ansgar
--- End Message ---
--- Begin Message ---
Source: python-lamson
Source-Version: 1.0pre11-1.3

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated python-lamson package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 20 Jan 2016 19:41:23 +
Source: python-lamson
Binary: python-lamson
Architecture: source
Version: 1.0pre11-1.3
Distribution: unstable
Urgency: medium
Maintainer: David Watson 
Changed-By: Mattia Rizzolo 
Description:
 python-lamson - A pure Python SMTP server
Closes: 805610
Changes:
 python-lamson (1.0pre11-1.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Swap the Maintainer and Uploaders addresses (both of David Watson).
 Closes: #805610
Checksums-Sha1:
 24e0bf96f30830fe188fa106cc2d66f6da87409c 1798 python-lamson_1.0pre11-1.3.dsc
 5421cead5a34d31c0e2da00e5a43d8d9426711bf 4410 
python-lamson_1.0pre11-1.3.diff.gz
Checksums-Sha256:
 db443376412aaadf182766176abdcc6674e4083ff6c0052cf59d69f0cb2749ef 1798 
python-lamson_1.0pre11-1.3.dsc
 a4c5a4472f1ead5b95683885717aae2de1846bd13e5393f76e9e31a7e7766cc7 4410 
python-lamson_1.0pre11-1.3.diff.gz
Files:
 237fb4a724243c241bbc3c1140e210b8 1798 python extra 
python-lamson_1.0pre11-1.3.dsc
 0a35d79a89a309a40025d10b24301ee0 4410 python extra 
python-lamson_1.0pre11-1.3.diff.gz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWn+LvAAoJEEsEP825REVAnwQP/0FBs1YUWUEtLhKD8lJDJybs
TrRe+IKazuN8sWj5v42ScBFMxMQDQxfB/fUD7eC0PF2BtLZlyatTC82DB6w2dPHY
sPR7KhU085yquftj7r/f+ta/N5CsOSvCAbLdyNwMvhgYdPEK6V0eybFov734sF6a
etv36Mjm6ftew/b29Mm5DlRh7rJpwvpGgmVCY95v2F6Cru9lnk+cdJBGXfMqS2UJ
0mdKeVaiGNkihd60+x10OyT8mj9yVrcE1HNGeb8liUQla9YZB+XvbgCvLbLgJ4w4
ZztEmNkKfkJ7Qhe5dQHGhSQOydMMlnGu/HUNmPdXlJB4hOHFchoZGZYbiEzMZEbQ
+gnorbkIx2qGH6E4BXlP5SsmclxseYJV5SIl+Dbjm+CAGwZ1WGnabdi+FPUXQcv0
5F1KyQP8MNelOwvhmzdjaAdYkwS0DtxZi7HiCxt0gco9MuBDF9Gy5vZ6+zVFCVje
ZWZZnKU+bVdG9sz/2lUdO/CC1El3VUN0VkHDEDr+zciYlpf9gD0GegBCCVhy8A3l
OvHtX6XTkhtTjp8Bf8fVYl+w4G4NuJyRkZKJFwT5RohfpBztkfCxMTGsB/Nr6SY7
YBFOKLYcBI2YAhh38WlGmh0i+ITghVuL8Rr0Vr4cH3dNSfF/wVB/sjquNFzfoUqu
6R4DkokpKbhFP3uCbuL0
=KTeK
-END PGP SIGNATURE End Message ---

Processed: clone bugs

[Debian Bug Tracking System]

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

> clone 810990 -1 -2
Bug #810990 [libxmlrpcpp-dev,heimdal-dev] libxmlrpcpp-dev: 
/usr/include/base64.h already shipped by heimdal-dev
Bug 810990 cloned as bugs 812129-812130
> reassign -1 libxmlrpcpp-dev
Bug #812129 [libxmlrpcpp-dev,heimdal-dev] libxmlrpcpp-dev: 
/usr/include/base64.h already shipped by heimdal-dev
Bug reassigned from package 'libxmlrpcpp-dev,heimdal-dev' to 'libxmlrpcpp-dev'.
No longer marked as found in versions heimdal/1.6~rc2+dfsg-10 and 
ros-ros-comm/1.11.16-2.
Ignoring request to alter fixed versions of bug #812129 to the same values 
previously set
> reassign -2 heimdal-dev
Bug #812130 [libxmlrpcpp-dev,heimdal-dev] libxmlrpcpp-dev: 
/usr/include/base64.h already shipped by heimdal-dev
Bug reassigned from package 'libxmlrpcpp-dev,heimdal-dev' to 'heimdal-dev'.
No longer marked as found in versions heimdal/1.6~rc2+dfsg-10 and 
ros-ros-comm/1.11.16-2.
Ignoring request to alter fixed versions of bug #812130 to the same values 
previously set
>
End of message, stopping processing here.

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

Bug#812093: libimager-perl: FTBFS: Failed 1/65 test programs. 0/4481 subtests failed.

[Niko Tyni]

On Wed, Jan 20, 2016 at 02:42:04PM +0100, Chris Lamb wrote:
> Source: libimager-perl
> Version: 1.004+dfsg-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

> libimager-perl fails to build from source in unstable/amd64:

It broke with src:giflib 5.1.2-0.1 -> 5.1.1-0.2. Don't know
why yet.

% perl -MImager -e 'Imager->new->read(type => "gif", file => 
"GIF/testimg/expected.gif") or die'

dies with the new giflib but not the old one.

Cc'ing Matthias Klose as a heads-up, he uploaded 5.1.1-0.2.
-- 
Niko Tyni   nt...@debian.org

Bug#802264: src:matita: FTBFS with OCaml 4.02.3

[Mehdi Dogguy]

Hi Enrico,

On 20/01/2016 11:15, Enrico Tassi wrote:
> On Sun, Oct 18, 2015 at 11:03:35PM +0200, Mehdi Dogguy wrote:
>> Package: src:matita
>> Version: 0.99.1-3
>> Severity: serious
>>
>> Dear Maintainer,
> 
> This bugs is due to camlp5 and fixed in
> caca3dd0643ec5aae9df4399fa73eb280808ef18
> 
> see https://gforge.inria.fr/projects/camlp5/
> 

Even using that fix, I get the following failure (while building matita):

  OCAMLC hExtlib.ml
File "hExtlib.ml", line 463, characters 10-23:
Warning 3: deprecated: String.create
Use Bytes.create instead.
File "hExtlib.ml", line 1:
Error: The implementation hExtlib.ml
   does not match the interface hExtlib.cmi:
   Values do not match:
 val find : ?test:(string -> bool) -> string -> string list
   is not included in
 val find : ?test: -> string -> string list
   File "hExtlib.ml", line 530, characters 4-8: Actual declaration
../Makefile.common:99: recipe for target 'hExtlib.cmo' failed
make: *** [hExtlib.cmo] Error 2

Didn't you get that error?

-- 
Mehdi

Bug#812083: reassign 812083 to libconsole-bridge-dev

[Jochen Sprickerhof]

reassign 812083 libconsole-bridge-dev
tag 812083 patch
retitle retitle libconsole-bridge-dev: missing cmake files
thanks

Hi,

This is actually due to a new version of libconsole-bridge-dev. Upstream
moved the cmake files from usr/share to usr/lib. The attached patch
fixes this.

Cheers Jochen
From 15603360c8f21f5775cd6c8f4f5cf9639b4d4f20 Mon Sep 17 00:00:00 2001
From: Jochen Sprickerhof 
Date: Wed, 20 Jan 2016 22:56:20 +0100
Subject: [PATCH] Install cmake files again

---
 debian/libconsole-bridge-dev.install | 1 +
 1 file changed, 1 insertion(+)

diff --git a/debian/libconsole-bridge-dev.install b/debian/libconsole-bridge-dev.install
index 60fe5cb..10685ff 100644
--- a/debian/libconsole-bridge-dev.install
+++ b/debian/libconsole-bridge-dev.install
@@ -1,3 +1,4 @@
 usr/include/*
 usr/lib/*/*.so
 usr/lib/*/pkgconfig/*
+usr/lib/*/console_bridge
-- 
2.7.0.rc3



signature.asc
Description: PGP signature

Processed (with 1 error): reassign 812083 to libconsole-bridge-dev

[Debian Bug Tracking System]

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

> reassign 812083 libconsole-bridge-dev
Bug #812083 [src:ros-ros-comm] ros-ros-comm: FTBFS: Make Error at 
tools/rosbag_storage/CMakeLists.txt:5 (find_package)
Bug reassigned from package 'src:ros-ros-comm' to 'libconsole-bridge-dev'.
No longer marked as found in versions ros-ros-comm/1.11.16-2.
Ignoring request to alter fixed versions of bug #812083 to the same values 
previously set
> tag 812083 patch
Bug #812083 [libconsole-bridge-dev] ros-ros-comm: FTBFS: Make Error at 
tools/rosbag_storage/CMakeLists.txt:5 (find_package)
Added tag(s) patch.
> retitle retitle libconsole-bridge-dev: missing cmake files
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.

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

Bug#811233: marked as done (FTBFS: At least the following dependencies are missing)

[Debian Bug Tracking System]

Your message dated Wed, 20 Jan 2016 23:19:17 +
with message-id 
and subject line Bug#811233: fixed in ganeti 2.15.2-2
has caused the Debian Bug report #811233,
regarding FTBFS: At least the following dependencies are missing
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.)


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

ganeti fails to build in unstable:

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> Warning: No remote package servers have been specified. Usually you would have
> one specified in the config file.
> Resolving dependencies...
> Configuring ganeti-2.15...
> cabal: At least the following dependencies are missing:
> attoparsec >=0.10.1.1 && <0.13, zlib >=0.5.3.3 && <0.6
> Makefile:4382: recipe for target 'cabal_macros.h' failed
> make[2]: *** [cabal_macros.h] Error 1
> make[2]: Leaving directory '/<>'
> dh_auto_build: make -j1 returned exit code 2
> debian/rules:76: recipe for target 'override_dh_auto_build' failed

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: ganeti
Source-Version: 2.15.2-2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 18 Jan 2016 15:46:10 +0200
Source: ganeti
Binary: ganeti2 ganeti ganeti-2.15 ganeti-haskell-2.15 ganeti-htools 
ganeti-htools-2.15 ganeti-doc python-ganeti-rapi
Architecture: source all amd64
Version: 2.15.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ganeti Team 
Changed-By: Apollon Oikonomopoulos 
Description:
 ganeti - cluster virtualization manager
 ganeti-2.15 - cluster virtualization manager - Python components
 ganeti-doc - cluster virtualization manager - documentation
 ganeti-haskell-2.15 - cluster virtualization manager - Haskell components
 ganeti-htools - cluster virtualization manager - tools (stand-alone)
 ganeti-htools-2.15 - cluster virtualization manager - tools for Ganeti 2.15
 ganeti2- transitional dummy package
 python-ganeti-rapi - cluster virtualization manager - RAPI client library
Closes: 811233 811515
Changes:
 ganeti (2.15.2-2) unstable; urgency=medium
 .
   * Add a patch to allow building against haskell-zlib 0.6 and relax
 attoparsec and zlib deps (Closes: #811233).
 .
   [ Debconf translations ]
   * Brazilian Portuguese (Adriano Rafael Gomes, closes: #811515)
Checksums-Sha1:
 32bd2d4202259f36bffe2935a77f68079cbeecad 3290 ganeti_2.15.2-2.dsc
 831d116e8a98382fa83672a4af1cd2e30186b32f 40040 ganeti_2.15.2-2.debian.tar.xz
 07825a56171fedd90d0e3c5e950c9ab05ba892b6 865718 ganeti-2.15_2.15.2-2_all.deb
 f2874704275c232a52e7f08b090fb616a78273a4 961014 ganeti-doc_2.15.2-2_all.deb
 3032f0932b76e976d2af07a741d64e1f16129453 7762290 
ganeti-haskell-2.15-dbgsym_2.15.2-2_amd64.deb
 1f6c0695d4c380e0377f2e816cc16032064dc58b 13469476 
ganeti-haskell-2.15_2.15.2-2_amd64.deb
 94473e26f910ea49547cf8793da6f1aa78b3ba98 1682302 
ganeti-htools-2.15-dbgsym_2.15.2-2_amd64.deb
 001ab6c119e40f2ba2dd6609c8e91238cc9d80e2 2906136 
ganeti-htools-2.15_2.15.2-2_amd64.deb
 90524b75623d40d1657674f8fcbec1a3c4ac01cd 19890 ganeti-htools_2.15.2-2_all.deb
 6e16eec38baed2705a5ea5be3ff321a6f1b643b1 76070 ganeti2_2.15.2-2_all.deb
 38021d1e3630fa709f65f8e398d3f1d10640723d 96810 ganeti_2.15.2-2_all.deb
 700c484d87fbc797162b8301e6cc56b00c15e3be 32480 
python-ganeti-rapi_2.15.2-2_all.deb
Checksums-Sha256:
 1b83a24fba7362215533ec219afac541f47cb2748f1cf18b9a160c6081d1a979 3290 
ganeti_2.15.2-2.dsc
 f669d8f45ae9ef819658ce44e8266861e6b8f4577355a26553a70b140449090d 40040 
ganeti_2.15.2-2.debian.tar.xz
 b56d1214a923e0fa740071e64c70ff8cafc6890fea25a1cc0ff63c4a9e1926ae 

Processed: severity of 810794 is important

[Debian Bug Tracking System]

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

> severity 810794 important
Bug #810794 [samba] samba: Uses very lax matching options for start-stop-daemon
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#613674: marked as done (Subject: xutils-dev: Can't get have_xmlto_text unless I add some content to the conftest.xml)

[Debian Bug Tracking System]

Your message dated Wed, 20 Jan 2016 22:40:48 +
with message-id 
and subject line Bug#613674: fixed in xutils-dev 1:7.7+4
has caused the Debian Bug report #613674,
regarding Subject: xutils-dev: Can't get have_xmlto_text unless I add some 
content to the conftest.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.)


-- 
613674: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613674
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xutils-dev
Version: 1:7.5+4
Severity: normal

Need to edit xorg-macros.m4:: # XORG_WITH_XMLTO([MIN-VERSION], [DEFAULT])

to add content to the file used to detect XML to .txt conversion

e.g.

--- xorg-cf-files/aclocal.m42011-01-08 22:50:19 +
+++ xorg-cf-files/aclocal.m42011-02-16 15:15:16 +
@@ -1803,6 +1803,11 @@
 # Test for the ability of xmlto to generate a text target
 have_xmlto_text=no
 cat > conftest.xml << "EOF"
+http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd;>
+
+
+
 EOF
 AS_IF([test "$have_xmlto" = yes],
   [AS_IF([$XMLTO --skip-validation txt conftest.xml >/dev/null 2>&1],


-- System Information:
Debian Release: squeeze/sid
  APT prefers maverick-updates
  APT policy: (500, 'maverick-updates'), (500, 'maverick-security'),
(500, 'maverick-proposed'), (500, 'maverick-backports'), (500,
'maverick')
Architecture: i386 (i686)

Kernel: Linux 2.6.35-26-generic-pae (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages xutils-dev depends on:
ii  cpp   4:4.4.4-1ubuntu2   The GNU C preprocessor (cpp)
ii  libc6 2.12.1-0ubuntu10.2 Embedded GNU C Library: Shared lib

xutils-dev recommends no packages.

xutils-dev suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: xutils-dev
Source-Version: 1:7.7+4

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

Debian distribution maintenance software
pp.
Julien Cristau  (supplier of updated xutils-dev package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 20 Jan 2016 23:06:52 +0100
Source: xutils-dev
Binary: xutils-dev
Architecture: source
Version: 1:7.7+4
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Julien Cristau 
Description:
 xutils-dev - X Window System utility programs for development
Closes: 613674
Changes:
 xutils-dev (1:7.7+4) unstable; urgency=medium
 .
   [ Andreas Boll ]
   * [util-macros] Add patch from upstream git to fix macro
 XORG_WITH_XMLTO (Closes: #613674).  Thanks, Peter Pearse, Helmut
 Grohne and Gaetan Nadon!
   * Update Vcs-* fields.
 .
   [ Julien Cristau ]
   * Use dh, drop xsfbs.
   * Let uscan verify tarball signatures.
Checksums-Sha1:
 200f89c2619ed081a8d43b288377e72fc8e56a90 1642 xutils-dev_7.7+4.dsc
 11aa04238cd78361516c555c92db98900e6a0808 1261095 xutils-dev_7.7+4.tar.gz
Checksums-Sha256:
 0afb63fe74692b0bf0b2c6980aeec4bc9f6a94085db27530bacffbbadae5c64e 1642 
xutils-dev_7.7+4.dsc
 d57d0892fc06e29d021523bc5e30e1d96232e3d6328d506a9745e00da0c1a31a 1261095 
xutils-dev_7.7+4.tar.gz
Files:
 0012097c4a91500e877f74658767d517 1642 x11 optional xutils-dev_7.7+4.dsc
 bc9d91fa4be0a2e38d1bc3685c5720ef 1261095 x11 optional xutils-dev_7.7+4.tar.gz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJWoAW4AAoJEJ2wI1VW+M+tlY0QALNoc/LmzIzMT3e4vOP19G0L
x/8KItLLzquL87GVqrR6xnVESTCUFGNpw5rVCKR88Tt+4rYYvhviewTiL6cgZ1/b
It1VDqV4vMftNx0FIT5oUAMJAKeLG2wDw4STSzqrdCEKHVz+c7Yl2WZ/NK1hO9VR
5tznVWbnlkh4h98GBQrLuOFerGFM6Ut3GlVGkyaP8aOe0SFhnzI99rbyQXOLRo7g
3uj80YJNIOB6wtf55XF5Bj2l+37bhIS3pqHcREvvInY29gpS9jNkGEUZRFuHyeEY
6DTrLl2lQcmicBPzkefI+urUjnyVyzbHjKsE2l4fW9aRMpM2L8bGaz6x5KSdbCB6
DxSo88I8ASlNnHOu3f+sa/MBMVfWYQUYXob2xzYlfoAXUNdLajBet6t8jTCg+m+A
zbxYdrcKSao1gpF+jdSlaVcCcKFgvIALksWh3B13ur/q75ofSZGssHWXXF4U7wlE
cbYdJiYgTixyAWNAncPBCIuwrIvWdAW5BekZ678CNIsAlA+kRji6yPCPBFIqhbGK

Bug#812083: marked as done (ros-ros-comm: FTBFS: Make Error at tools/rosbag_storage/CMakeLists.txt:5 (find_package))

[Debian Bug Tracking System]

Your message dated Wed, 20 Jan 2016 23:48:47 +
with message-id 
and subject line Bug#812083: fixed in console-bridge 0.3.0-3
has caused the Debian Bug report #812083,
regarding ros-ros-comm: FTBFS: Make Error at 
tools/rosbag_storage/CMakeLists.txt:5 (find_package)
to be marked as done.

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

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


-- 
812083: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812083
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ros-ros-comm
Version: 1.11.16-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,

ros-ros-comm fails to build from source in unstable/amd64:

  [..]

  
roswtf_SOURCE_DIR:STATIC=/home/lamby/temp/cdt.20160120122038.zVASOBK0h6/ros-ros-comm-1.11.16/utilities/roswtf
  
  //The directory containing a CMake configuration file for std_msgs.
  std_msgs_DIR:PATH=/usr/share/std_msgs/cmake
  
  //Value Computed by CMake
  
xmlrpcpp_BINARY_DIR:STATIC=/home/lamby/temp/cdt.20160120122038.zVASOBK0h6/ros-ros-comm-1.11.16/obj-x86_64-linux-gnu/utilities/xmlrpcpp
  
  //The directory containing a CMake configuration file for xmlrpcpp.
  
xmlrpcpp_DIR:PATH=/home/lamby/temp/cdt.20160120122038.zVASOBK0h6/ros-ros-comm-1.11.16/obj-x86_64-linux-gnu/devel/share/xmlrpcpp/cmake
  
  //Dependencies for target
  xmlrpcpp_LIB_DEPENDS:STATIC=
  
  //Value Computed by CMake
  
xmlrpcpp_SOURCE_DIR:STATIC=/home/lamby/temp/cdt.20160120122038.zVASOBK0h6/ros-ros-comm-1.11.16/utilities/xmlrpcpp
  
  
  
  # INTERNAL cache entries
  
  
  //ADVANCED property for variable: Boost_DIR
  Boost_DIR-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_FILESYSTEM_LIBRARY_DEBUG
  Boost_FILESYSTEM_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_FILESYSTEM_LIBRARY_RELEASE
  Boost_FILESYSTEM_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_INCLUDE_DIR
  Boost_INCLUDE_DIR-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_LIBRARY_DIR_DEBUG
  Boost_LIBRARY_DIR_DEBUG-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_LIBRARY_DIR_RELEASE
  Boost_LIBRARY_DIR_RELEASE-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_REGEX_LIBRARY_DEBUG
  Boost_REGEX_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_REGEX_LIBRARY_RELEASE
  Boost_REGEX_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_SIGNALS_LIBRARY_DEBUG
  Boost_SIGNALS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_SIGNALS_LIBRARY_RELEASE
  Boost_SIGNALS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_SYSTEM_LIBRARY_DEBUG
  Boost_SYSTEM_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_SYSTEM_LIBRARY_RELEASE
  Boost_SYSTEM_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_THREAD_LIBRARY_DEBUG
  Boost_THREAD_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_THREAD_LIBRARY_RELEASE
  Boost_THREAD_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
  //catkin environment
  
CATKIN_ENV:INTERNAL=/home/lamby/temp/cdt.20160120122038.zVASOBK0h6/ros-ros-comm-1.11.16/obj-x86_64-linux-gnu/catkin_generated/env_cached.sh
  
CATKIN_TEST_RESULTS_DIR:INTERNAL=/home/lamby/temp/cdt.20160120122038.zVASOBK0h6/ros-ros-comm-1.11.16/obj-x86_64-linux-gnu/test_results
  //ADVANCED property for variable: CMAKE_AR
  CMAKE_AR-ADVANCED:INTERNAL=1
  //This is the directory where this CMakeCache.txt was created
  
CMAKE_CACHEFILE_DIR:INTERNAL=/home/lamby/temp/cdt.20160120122038.zVASOBK0h6/ros-ros-comm-1.11.16/obj-x86_64-linux-gnu
  //Major version of cmake used to create the current loaded cache
  CMAKE_CACHE_MAJOR_VERSION:INTERNAL=3
  //Minor version of cmake used to create the current loaded cache
  CMAKE_CACHE_MINOR_VERSION:INTERNAL=4
  //Patch version of cmake used to create the current loaded cache
  CMAKE_CACHE_PATCH_VERSION:INTERNAL=1
  //ADVANCED property for variable: CMAKE_COLOR_MAKEFILE
  CMAKE_COLOR_MAKEFILE-ADVANCED:INTERNAL=1
  //Path to CMake executable.
  CMAKE_COMMAND:INTERNAL=/usr/bin/cmake
  //Path to cpack program executable.
  CMAKE_CPACK_COMMAND:INTERNAL=/usr/bin/cpack
  //Path to ctest program executable.
  CMAKE_CTEST_COMMAND:INTERNAL=/usr/bin/ctest
  //ADVANCED property for variable: CMAKE_CXX_COMPILER
  CMAKE_CXX_COMPILER-ADVANCED:INTERNAL=1
  //ADVANCED 

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

[Andreas Henriksson]

Hello Adam Borowski.

Thanks for your bug report. I'm sorry I missed openrc.

On Wed, Jan 20, 2016 at 01:46:08AM +0100, Adam Borowski wrote:
> 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.

It seems like openrc is following the old approach also taken by file-rc
to fork and conflict as I understand it was in the old days recommended.
(I'm not really sure that this was properly policy compliant. In my view
the Conflict/Replaces needs to be set up in *both* directions, not only
in one of the packages.)

I think this is a bad approach and think the way upstart and systemd
handled it by incorporating support in the same program is better.

Some random reasons for this:
 - not everyone can conflict with sysv-rc (see e.g. systemd actually declaring
   a  *dependency* on sysv-rc). And I think Conflicting with
   init-system-helpers will also be problematic.
 - just because openrc is installed doesn't mean openrc is actually running
   (specially not when the package is first installed and even if it's been
rebooted and has claimed /sbin/init someone might have still overriden
init via kernel cmdline).
 - keeping state in sync, eg. as done by systemd and sysvinit, so you can
   switch back and forward seems like it becomes more troublesome.

Do you think it would be possible for open-rc to incorporate its
invoke-rc.d and update-rc.d into the init-system-helpers version
so we can all help out maintaining one version instead?

If you still think it's better for openrc to ship its own versions of
these programs, could you please consider switching to using a proper
divert? If you could also runtime detect if openrc is actually running
(how do you do that by the way?) and forward the calls to the diverted
version if not would be good as well IMHO.
A divert would have the benefit of also avoiding problems like the one
you reported in the future, no matter which package ships the progams.

I'm willing to help out on the init-system-helpers side if needed (although
I'm not maintaining it).

Which way do you think is best way forward?

Regards,
Andreas Henriksson

Bug#796931: Another data point

[Manoj Srivastava]

Hi,

I sourced the file 70gnupg-agent.sh discussed earlier int he bug
 report. I am still having issues -- at least, with gpg, I can actually
 use gpg; gpg2 just fails.

manoj

> echo $GNUPGHOME
/home/srivasta/lib/.sec
>echo $GPG_AGENT_INFO

> echo $GPG_AGENT

> gpg-agent
gpg-agent[1725]: gpg-agent running and available
> gpg2 -vvv --clearsign ~/.login
gpg: keyserver option 'include-disabled' is unknown
gpg: keyserver option 'honor-http-proxy' is unknown
gpg: using character set 'utf-8'
gpg: Note: signature key 9D760D4D has been revoked
gpg: Note: signature key 840A4306 expired Wed 11 May 2011 02:33:47 PM PDT
gpg: using PGP trust model
gpg: key C5779A1C: accepted as trusted key
gpg: Note: signature key 9D760D4D has been revoked
gpg: Note: signature key 840A4306 expired Wed 11 May 2011 02:33:47 PM PDT
gpg: using subkey 6F576472 instead of primary key C5779A1C
gpg: writing to '/home/srivasta/.login.asc'
gpg: signing failed: No secret key
gpg: /home/srivasta/.login: clearsign failed: No secret key
[1]1767 exit 2 gpg2 -vvv --clearsign ~/.login
> gpg -vvv --clearsign ~/.login
gpg: using character set `utf-8'
gpg: using PGP trust model
gpg: key C5779A1C: accepted as trusted key
gpg: can't handle public key algorithm 22
gpg: can't handle public key algorithm 19
gpg: error checking usability status of C7261095
gpg: key C7261095: secret key without public key - skipped
gpg: NOTE: signature key 840A4306 expired Wed 11 May 2011 02:33:47 PM PDT
gpg: NOTE: signature key 840A4306 expired Wed 11 May 2011 02:33:47 PM PDT
gpg: no secret subkey for public subkey 840A4306 - ignoring
gpg: using subkey 6F576472 instead of primary key C5779A1C

You need a passphrase to unlock the secret key for
user: "Manoj Srivastava "
gpg: NOTE: signature key 840A4306 expired Wed 11 May 2011 02:33:47 PM PDT
gpg: using subkey 6F576472 instead of primary key C5779A1C
2048-bit RSA key, ID 6F576472, created 2009-07-23 (main key ID C5779A1C)

gpg: gpg-agent is not available in this session
You need a passphrase to unlock the secret key for
user: "Manoj Srivastava "
2048-bit RSA key, ID 6F576472, created 2009-07-23 (main key ID C5779A1C)

gpg: writing to `/home/srivasta/.login.asc'
gpg: RSA/SHA512 signature from: "6F576472 Manoj Srivastava 
"


 ps auwwx | egrep '[g]pg-agent'
srivasta 24911  0.0  0.0 165000  2180 ?SNs  00:39   0:00 gpg-agent 
--daemon --enable-ssh-support --allow-preset-passphrase 
--no-allow-external-cache

-- 
Man is a military animal, glories in gunpowder, and loves
parade. P.J. Bailey
Manoj Srivastava    
4096R/C5779A1C E37E 5EC5 2A01 DA25 AD20  05B6 CF48 9438 C577 9A1C


signature.asc
Description: PGP signature

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

[Lars Tangvald]

On 01/20/2016 12:59 AM, Clint Byrum wrote:

Is anyone working on the build/test/upload of the final binaries?
I'm working with Robie to get the upload ready. Dep8 tests have passed 
on stable, and the changes made by the security team for previous 
releases should all be merged into my github tree.


Once it's merged into Alioth we'll need someone to take over for tag and 
upload.


--
Lars Tangvald

Bug#812072: module 'subprocess' has no attribute 'mswindows'

[Thomas Goirand]

Package: python3-cmd2
Version: 0.6.7-2
Severity: grave

Hi,

When using cmd2 in the unit test suite of python-cliff, I get:

  File 
"/home/zigo/sources/openstack/liberty/python-cliff/build-area/python-cliff-1.15.0/cliff/interactive.py",
 line 10, in 
import cmd2
  File "/usr/lib/python3/dist-packages/cmd2.py", line 181, in 
if subprocess.mswindows:
AttributeError: module 'subprocess' has no attribute 'mswindows'

Obviously, I'm not running mswindows... :)

Changing the line 181 from:
if subprocess.mswindows:

to:
if hasattr(subprocess, 'mswindows'):

fixed it. There must be so many ways to fix it anyway (we just need to
neutralize the code for MSWin...).

Cheers,

Thomas Goirand (zigo)

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

[Florent Rougon]

Hello,

Same problem here after yesterday's upgrade. The 0.122~a.test
initramfs-tools and initramfs-tools-core packages mentioned by Ben at
 allowed my
system to boot, thank you!

(along with the Debian jessie installation DVD in rescue mode, its
option to automatically assemble RAID arrays, followed by mounting the
/, /usr and /var filesystems of my normal system at temporary mount
points, chrooting into the temporarily-mounted root before running dpkg
-i the_deb_files [maybe simply booting with the previous kernel to
install the test packages would have worked, too?..])

Regards

-- 
Florent

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

[Tiziano Zito]

Hi, 

Same problem here after upgrading to 0.121. System does not boot anymore 
and gets stuck at initramfs prompt after "run-init: opening console: No 
such file or directory" error. 

The 0.122~a.test packages made my system bootable again too. Like 
Florent, I had to rescue the system by booting with a temporary live-cd, 
and installing within a chroot.


Ciao,
Tiziano

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

[Lars Tangvald]

http://anonscm.debian.org/cgit/pkg-mysql/mysql-5.5.git/  is updated.
I'll send a notice to the security team. They may want us to do the 
upload, in which case we'll need someone who has the permissions to do so :)


--
Lars Tangvald

Bug#811469: marked as done (isomd5sum: FTBFS: cc: error: libcheckisomd5.a: No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 20 Jan 2016 10:32:31 +0100
with message-id 
<1453282351.1708458.497288242.51d75...@webmail.messagingengine.com>
and subject line Re: Bug#811469: isomd5sum: FTBFS: cc: error: libcheckisomd5.a: 
No such file or directory
has caused the Debian Bug report #811469,
regarding isomd5sum: FTBFS: cc: error: libcheckisomd5.a: No such file or 
directory
to be marked as done.

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

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


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

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

[Chris Lamb]

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

Nor can I now. Closing (in BCC)


Regards,

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

Bug#812077: bind9: CVE-2015-8704: Specific APL data could trigger an INSIST in apl_42.c

[Salvatore Bonaccorso]

Source: bind9
Version: 1:9.7.3.dfsg-1
Severity: serious
Tags: security upstream fixed-upstream

Hi,

(Marking as RC, since fixes are in stable already and need to go to
stretch as well).

the following vulnerability was published for bind9.

CVE-2015-8704[0]:
Specific APL data could trigger an INSIST in apl_42.c

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2015-8704

Regards,
Salvatore

Processed: fixed 812077 in 1:9.7.3.dfsg-1~squeeze19, fixed 812077 in 1:9.8.4.dfsg.P1-6+nmu2+deb7u9 ...

[Debian Bug Tracking System]

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

> fixed 812077 1:9.7.3.dfsg-1~squeeze19
Bug #812077 [src:bind9] bind9: CVE-2015-8704: Specific APL data could trigger 
an INSIST in apl_42.c
Marked as fixed in versions bind9/1:9.7.3.dfsg-1~squeeze19.
> fixed 812077 1:9.8.4.dfsg.P1-6+nmu2+deb7u9
Bug #812077 [src:bind9] bind9: CVE-2015-8704: Specific APL data could trigger 
an INSIST in apl_42.c
The source 'bind9' and version '1:9.8.4.dfsg.P1-6+nmu2+deb7u9' do not appear to 
match any binary packages
Marked as fixed in versions bind9/1:9.8.4.dfsg.P1-6+nmu2+deb7u9.
> fixed 812077 1:9.9.5.dfsg-9+deb8u5
Bug #812077 [src:bind9] bind9: CVE-2015-8704: Specific APL data could trigger 
an INSIST in apl_42.c
Marked as fixed in versions bind9/1:9.9.5.dfsg-9+deb8u5.
> thanks
Stopping processing here.

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

Bug#810070: [Pkg-xen-devel] Bug#810070: XEN Hypervisor crashes/reboots at Startup after "Scrubbing Free Ram"

[Ian Campbell]

Control: tag -1 +upstream

On Wed, 2016-01-06 at 08:36 +, Wolf Karsten Dietz wrote:
> Package: xen-hypervisor-4.4-amd64
> Version: 4.4.1-9+deb8u3
> Severity: grave
> 
> Hello,
> I am trying to install the XEN Hypervisor on a Debian Jessie Server.  
> When I am booting without the Hypervisor, everything works fine, but  
> when I am Booting WITH the XEN-Hypervisor, then System crashes /  
> reboots after the "Scrubbing Free RAM" Message without any  
> Error-message, just a blank screen.

Thanks for your report. 

I don't think we are going to be able to resolve this within Debian. Would
you mind reporting this to upstream please:
http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen

We could forward it but I expect there will need to be some back and forth
with the maintainers so ti makes sense for you to speak to them directly.
You can CC 810...@bugs.debian.org to keep this bug in the loop.

If possible it might be interesting to first try the 4.6 hypervisor in
Stretch, I suspect the xen-hypervisor-4.6-amd64 package will just install
on Jessie with no issues since it has no dependencies and you don't need
the userspace tools just to check if it boots.

Ian.

> 
> Technical Data of the Server:
> CPU: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz (with VT-x)
> MEMORY: 64GB RAM (Memtest reports no Errors)
> HDD: SSD as Software-Raid
> 
> Debian-Version: 8.2 (Jessie) with all Updates
> System/Dom0-Kernel: 3.16.7-ckt20-1 / 3.16+63
> I have also tried the Kernels from Backports: 4.2.6-3-bpo8+2 and  
> 4.3.3-2-bpo8+1 ... makes no difference
> 
> According to other Bug-reports, etc. in the Internet I tried to set  
> Parameters in the Grub-Command-line (/etc/default/grub :  
> GRUB_CMDLINE_XEN_DEFAULT) followed by an update-grub everytime:
> 
> dom0_mem : different Values between 512M,max:512M and 64G,max:64G ( At  
> the beginning in Steps of 256M and at the end in Steps of 2G) ...  
> makes no difference
> mem : diffent Values between 512M and 64G ( like dom0_mem or a little  
> bit higher) ... makes no difference
> dom0_max_vcpus=1 dom0_vcpus_pin : with and without  makes no
> difference
> no-bootscrub : with or without ... the only difference is that the  
> Scubbing Free RAM Message and the dots afterwards are disappearing ...  
> the crash/reboot is happening at the same Position
> noreboot: with or without ... no difference ... with the System hangs  
> with a blank screen and needs a hardware-reset ... without the System  
> is rebooting after the Blank Screen
> acpi=ht|off or without ... makes no difference
> loglvl=all guest_loglvl=all ... no other messages seen
> 
> The Server is in a Data-Center, so I have no physical access to it and  
> i cannot put something like a serial console on it. I have only some  
> Videos from the Remote VGA-Utility of the boot-Sequenz. In all Videos  
> the Screen gets black after the Message of reported VCPUs and the  
> Scrubbing Free RAM.
> 
> dmesg from a normal Startup without XEN-Hypervisor (this time the  
> 4.3-kernel ... if other Kernel needed please ask):
> [0.00] Initializing cgroup subsys cpuset
> [0.00] Initializing cgroup subsys cpu
> [0.00] Initializing cgroup subsys cpuacct
> [0.00] Linux version 4.3.0-0.bpo.1-amd64  
> (debian-ker...@lists.debian.org) (gcc version 4.9.2 (Debian 4.9.2-10)  
> ) #1 SMP Debian 4.3.3-2~bpo8+1 (2015-12-23)
> [0.00] Command line: BOOT_IMAGE=/vmlinuz-4.3.0-0.bpo.1-amd64  
> root=UUID=fc273ce0-6e58-4b9f-9cec-5d625697326c ro nomodeset
> [0.00] x86/fpu: xstate_offset[2]: 0240, xstate_sizes[2]: 0100
> [0.00] x86/fpu: xstate_offset[3]: 03c0, xstate_sizes[3]: 0040
> [0.00] x86/fpu: xstate_offset[4]: 0400, xstate_sizes[4]: 0040
> [0.00] x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating  
> point registers'
> [0.00] x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers'
> [0.00] x86/fpu: Supporting XSAVE feature 0x04: 'AVX registers'
> [0.00] x86/fpu: Supporting XSAVE feature 0x08: 'MPX bounds
> registers'
> [0.00] x86/fpu: Supporting XSAVE feature 0x10: 'MPX CSR'
> [0.00] x86/fpu: Enabled xstate features 0x1f, context size is  
> 0x440 bytes, using 'standard' format.
> [0.00] x86/fpu: Using 'eager' FPU context switches.
> [0.00] e820: BIOS-provided physical RAM map:
> [0.00] BIOS-e820: [mem 0x-0x0009c7ff]
> usable
> [0.00] BIOS-e820: [mem 0x0009c800-0x0009]
> reserved
> [0.00] BIOS-e820: [mem 0x000e-0x000f]
> reserved
> [0.00] BIOS-e820: [mem 0x0010-0xbf873fff]
> usable
> [0.00] BIOS-e820: [mem 0xbf874000-0xbf874fff]
> ACPI NVS
> [0.00] BIOS-e820: [mem 0xbf875000-0xbf8befff]
> reserved
> [0.00] BIOS-e820: [mem 0xbf8bf000-0xc2f53fff]
> usable
> [0.00] BIOS-e820: [mem 

Processed: Re: [Pkg-xen-devel] Bug#810070: XEN Hypervisor crashes/reboots at Startup after "Scrubbing Free Ram"

[Debian Bug Tracking System]

Processing control commands:

> tag -1 +upstream
Bug #810070 [xen-hypervisor-4.4-amd64] XEN Hypervisor crashes/reboots at 
Startup after "Scrubbing Free Ram"
Added tag(s) upstream.

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

Bug#802264: src:matita: FTBFS with OCaml 4.02.3

[Enrico Tassi]

On Sun, Oct 18, 2015 at 11:03:35PM +0200, Mehdi Dogguy wrote:
> Package: src:matita
> Version: 0.99.1-3
> Severity: serious
> 
> Dear Maintainer,

This bugs is due to camlp5 and fixed in
caca3dd0643ec5aae9df4399fa73eb280808ef18

see https://gforge.inria.fr/projects/camlp5/

Best,
-- 
Enrico Tassi

Processed: reassign 802264 to camlp5

[Debian Bug Tracking System]

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

> reassign 802264 camlp5
Bug #802264 [src:matita] src:matita: FTBFS with OCaml 4.02.3
Bug reassigned from package 'src:matita' to 'camlp5'.
No longer marked as found in versions matita/0.99.1-3.
Ignoring request to alter fixed versions of bug #802264 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#812083: ros-ros-comm: FTBFS: Make Error at tools/rosbag_storage/CMakeLists.txt:5 (find_package)

[Chris Lamb]

Source: ros-ros-comm
Version: 1.11.16-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,

ros-ros-comm fails to build from source in unstable/amd64:

  [..]

  
roswtf_SOURCE_DIR:STATIC=/home/lamby/temp/cdt.20160120122038.zVASOBK0h6/ros-ros-comm-1.11.16/utilities/roswtf
  
  //The directory containing a CMake configuration file for std_msgs.
  std_msgs_DIR:PATH=/usr/share/std_msgs/cmake
  
  //Value Computed by CMake
  
xmlrpcpp_BINARY_DIR:STATIC=/home/lamby/temp/cdt.20160120122038.zVASOBK0h6/ros-ros-comm-1.11.16/obj-x86_64-linux-gnu/utilities/xmlrpcpp
  
  //The directory containing a CMake configuration file for xmlrpcpp.
  
xmlrpcpp_DIR:PATH=/home/lamby/temp/cdt.20160120122038.zVASOBK0h6/ros-ros-comm-1.11.16/obj-x86_64-linux-gnu/devel/share/xmlrpcpp/cmake
  
  //Dependencies for target
  xmlrpcpp_LIB_DEPENDS:STATIC=
  
  //Value Computed by CMake
  
xmlrpcpp_SOURCE_DIR:STATIC=/home/lamby/temp/cdt.20160120122038.zVASOBK0h6/ros-ros-comm-1.11.16/utilities/xmlrpcpp
  
  
  
  # INTERNAL cache entries
  
  
  //ADVANCED property for variable: Boost_DIR
  Boost_DIR-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_FILESYSTEM_LIBRARY_DEBUG
  Boost_FILESYSTEM_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_FILESYSTEM_LIBRARY_RELEASE
  Boost_FILESYSTEM_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_INCLUDE_DIR
  Boost_INCLUDE_DIR-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_LIBRARY_DIR_DEBUG
  Boost_LIBRARY_DIR_DEBUG-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_LIBRARY_DIR_RELEASE
  Boost_LIBRARY_DIR_RELEASE-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_REGEX_LIBRARY_DEBUG
  Boost_REGEX_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_REGEX_LIBRARY_RELEASE
  Boost_REGEX_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_SIGNALS_LIBRARY_DEBUG
  Boost_SIGNALS_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_SIGNALS_LIBRARY_RELEASE
  Boost_SIGNALS_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_SYSTEM_LIBRARY_DEBUG
  Boost_SYSTEM_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_SYSTEM_LIBRARY_RELEASE
  Boost_SYSTEM_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_THREAD_LIBRARY_DEBUG
  Boost_THREAD_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_THREAD_LIBRARY_RELEASE
  Boost_THREAD_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
  //catkin environment
  
CATKIN_ENV:INTERNAL=/home/lamby/temp/cdt.20160120122038.zVASOBK0h6/ros-ros-comm-1.11.16/obj-x86_64-linux-gnu/catkin_generated/env_cached.sh
  
CATKIN_TEST_RESULTS_DIR:INTERNAL=/home/lamby/temp/cdt.20160120122038.zVASOBK0h6/ros-ros-comm-1.11.16/obj-x86_64-linux-gnu/test_results
  //ADVANCED property for variable: CMAKE_AR
  CMAKE_AR-ADVANCED:INTERNAL=1
  //This is the directory where this CMakeCache.txt was created
  
CMAKE_CACHEFILE_DIR:INTERNAL=/home/lamby/temp/cdt.20160120122038.zVASOBK0h6/ros-ros-comm-1.11.16/obj-x86_64-linux-gnu
  //Major version of cmake used to create the current loaded cache
  CMAKE_CACHE_MAJOR_VERSION:INTERNAL=3
  //Minor version of cmake used to create the current loaded cache
  CMAKE_CACHE_MINOR_VERSION:INTERNAL=4
  //Patch version of cmake used to create the current loaded cache
  CMAKE_CACHE_PATCH_VERSION:INTERNAL=1
  //ADVANCED property for variable: CMAKE_COLOR_MAKEFILE
  CMAKE_COLOR_MAKEFILE-ADVANCED:INTERNAL=1
  //Path to CMake executable.
  CMAKE_COMMAND:INTERNAL=/usr/bin/cmake
  //Path to cpack program executable.
  CMAKE_CPACK_COMMAND:INTERNAL=/usr/bin/cpack
  //Path to ctest program executable.
  CMAKE_CTEST_COMMAND:INTERNAL=/usr/bin/ctest
  //ADVANCED property for variable: CMAKE_CXX_COMPILER
  CMAKE_CXX_COMPILER-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: CMAKE_CXX_FLAGS
  CMAKE_CXX_FLAGS-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: CMAKE_CXX_FLAGS_DEBUG
  CMAKE_CXX_FLAGS_DEBUG-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: CMAKE_CXX_FLAGS_MINSIZEREL
  CMAKE_CXX_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: CMAKE_CXX_FLAGS_RELEASE
  CMAKE_CXX_FLAGS_RELEASE-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: CMAKE_CXX_FLAGS_RELWITHDEBINFO
  CMAKE_CXX_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: CMAKE_C_COMPILER
  CMAKE_C_COMPILER-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: CMAKE_C_FLAGS
  CMAKE_C_FLAGS-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: CMAKE_C_FLAGS_DEBUG
  CMAKE_C_FLAGS_DEBUG-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: CMAKE_C_FLAGS_MINSIZEREL
  CMAKE_C_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
  

Bug#812087: pcscd takes 100 % cpu each time I insert a mass storage USB key

[Ludovic Rousseau]

Le 20/01/2016 13:03, Eric Valette a écrit :

Package: pcscd
Version: 1.8.15-1
Severity: critical
Justification: breaks unrelated software

Twice in two days, I noticed my laptop fan was going carsy allthough I
was only doing many mail activity.

Twice I found that pcscd was eating a complete CPU and remembered that
each time I had inserted a regular mass storage USB key (two different keys)
not my crypto key.

  -
top - 12:56:25 up  3:14,  5 users,  load average: 2.03, 1.56, 1.31
Tasks: 242 total,   2 running, 239 sleeping,   0 stopped,   1 zombie
%Cpu(s): 34.1 us, 21.1 sy,  0.0 ni, 44.8 id,  0.0 wa,  0.0 hi,  0.1 si,  0.0 st
KiB Mem :  8219052 total,  3472188 free,  2336828 used,  2410036 buff/cache
KiB Swap: 16383996 total, 16383996 free,0 used.  5812264 avail Mem

   PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND
  1687 root  20   0  394560   2916   2120 S 100.3  0.0 147:37.75 pcscd
14477 ceva6380  20   0  424288  57364  37792 R  99.7  0.7   2:59.83 konsole
  2921 ceva6380  20   0 1410776 448992  87860 S  15.9  5.5   6:48.46 icedove
  4463 ceva6380  20   0 1435116 363080  97112 S   1.7  4.4   4:12.69 iceweasel


Do you have some pcscd related logs in /var/log/* ?

Bye

--
 Dr. Ludovic Rousseau

Bug#812087: pcscd takes 100 % cpu each time I insert a mass storage USB key

[Eric Valette]

Package: pcscd
Version: 1.8.15-1
Severity: critical
Justification: breaks unrelated software

Twice in two days, I noticed my laptop fan was going carsy allthough I
was only doing many mail activity.

Twice I found that pcscd was eating a complete CPU and remembered that
each time I had inserted a regular mass storage USB key (two different keys)
not my crypto key.

 -
top - 12:56:25 up  3:14,  5 users,  load average: 2.03, 1.56, 1.31
Tasks: 242 total,   2 running, 239 sleeping,   0 stopped,   1 zombie
%Cpu(s): 34.1 us, 21.1 sy,  0.0 ni, 44.8 id,  0.0 wa,  0.0 hi,  0.1 si,  0.0 st
KiB Mem :  8219052 total,  3472188 free,  2336828 used,  2410036 buff/cache
KiB Swap: 16383996 total, 16383996 free,0 used.  5812264 avail Mem 

  PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND 
 
 1687 root  20   0  394560   2916   2120 S 100.3  0.0 147:37.75 pcscd   
 
14477 ceva6380  20   0  424288  57364  37792 R  99.7  0.7   2:59.83 konsole 
 
 2921 ceva6380  20   0 1410776 448992  87860 S  15.9  5.5   6:48.46 icedove 
 
 4463 ceva6380  20   0 1435116 363080  97112 S   1.7  4.4   4:12.69 iceweasel 

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

Kernel: Linux 4.4.0 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF8, LC_CTYPE=en_US.UTF8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages pcscd depends on:
ii  init-system-helpers 1.25
ii  libc6   2.22-0experimental1
ii  libccid [pcsc-ifd-handler]  1.4.22-1
ii  libpcsclite11.8.15-1
ii  libudev1228-4
ii  lsb-base9.20160110

pcscd recommends no packages.

Versions of packages pcscd suggests:
ii  systemd  228-4

-- no debconf information

Bug#812087: pcscd takes 100 % cpu each time I insert a mass storage USB key

[eric2.valette]

On 01/20/2016 01:31 PM, Ludovic Rousseau wrote:

Le 20/01/2016 13:03, Eric Valette a écrit :

Package: pcscd
Version: 1.8.15-1
Severity: critical
Justification: breaks unrelated software

Twice in two days, I noticed my laptop fan was going carsy allthough I
was only doing many mail activity.

Twice I found that pcscd was eating a complete CPU and remembered that
each time I had inserted a regular mass storage USB key (two 
different keys)

not my crypto key.

  -
top - 12:56:25 up  3:14,  5 users,  load average: 2.03, 1.56, 1.31
Tasks: 242 total,   2 running, 239 sleeping,   0 stopped,   1 zombie
%Cpu(s): 34.1 us, 21.1 sy,  0.0 ni, 44.8 id,  0.0 wa,  0.0 hi, 0.1 
si,  0.0 st
KiB Mem :  8219052 total,  3472188 free,  2336828 used,  2410036 
buff/cache
KiB Swap: 16383996 total, 16383996 free,0 used.  5812264 
avail Mem


   PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND
  1687 root  20   0  394560   2916   2120 S 100.3  0.0 147:37.75 
pcscd
14477 ceva6380  20   0  424288  57364  37792 R  99.7  0.7 2:59.83 
konsole
  2921 ceva6380  20   0 1410776 448992  87860 S  15.9  5.5 6:48.46 
icedove
  4463 ceva6380  20   0 1435116 363080  97112 S   1.7  4.4 4:12.69 
iceweasel


Do you have some pcscd related logs in /var/log/* ?

Bye



Note that in the laptop there is a build in  broadcom credit card format 
crypto key reader (that you see in the log), but I do not use it 
although for testing purpose I have enabled the driver. But the bug is 
only if I insert a USB key.





daemon.log:Jan 18 15:17:11 r-x-ceva6380 pcscd[11283]:  
ifdhandler.c:144:CreateChannelByNameOrChannel() failed
daemon.log:Jan 18 15:17:11 r-x-ceva6380 pcscd[11283]: 0032 
readerfactory.c:1097:RFInitializeReader() Open Port 0x20 Failed 
(usb:0a5c/5800:libudev:0:/dev/bus/usb/002/004)
daemon.log:Jan 18 15:17:11 r-x-ceva6380 pcscd[11283]: 0004 
readerfactory.c:372:RFAddReader() Broadcom Corp 5880 [Broadcom USH] 
(0123456789ABCD) init failed.
daemon.log:Jan 19 13:52:56 r-x-ceva6380 pcscd[1604]:  
ifdhandler.c:144:CreateChannelByNameOrChannel() failed
daemon.log:Jan 19 13:52:56 r-x-ceva6380 pcscd[1604]: 0027 
readerfactory.c:1097:RFInitializeReader() Open Port 0x20 Failed 
(usb:0a5c/5800:libudev:0:/dev/bus/usb/002/004)
daemon.log:Jan 19 13:52:56 r-x-ceva6380 pcscd[1604]: 0005 
readerfactory.c:372:RFAddReader() Broadcom Corp 5880 [Broadcom USH] 
(0123456789ABCD) init failed.
daemon.log:Jan 20 09:42:05 r-x-ceva6380 pcscd[1687]:  
ifdhandler.c:144:CreateChannelByNameOrChannel() failed
daemon.log:Jan 20 09:42:05 r-x-ceva6380 pcscd[1687]: 0026 
readerfactory.c:1097:RFInitializeReader() Open Port 0x20 Failed 
(usb:0a5c/5800:libudev:0:/dev/bus/usb/002/004)
daemon.log:Jan 20 09:42:05 r-x-ceva6380 pcscd[1687]: 0004 
readerfactory.c:372:RFAddReader() Broadcom Corp 5880 [Broadcom USH] 
(0123456789ABCD) init failed.
daemon.log:Jan 20 12:56:47 r-x-ceva6380 systemd[1]: pcscd.service: Main 
process exited, code=killed, status=9/KILL
daemon.log:Jan 20 12:56:47 r-x-ceva6380 systemd[1]: pcscd.service: Unit 
entered failed state.
daemon.log:Jan 20 12:56:47 r-x-ceva6380 systemd[1]: pcscd.service: 
Failed with result 'signal'.   < killed it by kill -9 to get CPU back
daemon.log:Jan 20 12:56:47 r-x-ceva6380 pcscd[14663]:  
ifdhandler.c:144:CreateChannelByNameOrChannel() failed
daemon.log:Jan 20 12:56:47 r-x-ceva6380 pcscd[14663]: 0022 
readerfactory.c:1097:RFInitializeReader() Open Port 0x20 Failed 
(usb:0a5c/5800:libudev:0:/dev/bus/usb/002/004)
daemon.log:Jan 20 12:56:47 r-x-ceva6380 pcscd[14663]: 0003 
readerfactory.c:372:RFAddReader() Broadcom Corp 5880 [Broadcom USH] 
(0123456789ABCD) init failed.



-- eric
 



_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

Bug#812085: libcommons-jexl2-java: FTBFS: Error resolving version for plugin 'org.apache.felix:maven-bundle-plugin' from the repositories

[Chris Lamb]

Source: libcommons-jexl2-java
Version: 2.1.1-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,

libcommons-jexl2-java fails to build from source in unstable/amd64:

  [..]

  cd . && /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 
-Dproperties.file.manual=/home/lamby/temp/cdt.20160120125708.4BbRf6rkUu/libcommons-jexl2-java-2.1.1/debian/maven.properties
 -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/home/lamby/temp/cdt.20160120125708.4BbRf6rkUu/libcommons-jexl2-java-2.1.1
 org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Dmaven.repo.local=/home/lamby/temp/cdt.20160120125708.4BbRf6rkUu/libcommons-jexl2-java-2.1.1/debian/maven-repo
  package -DskipTests
  [INFO] Scanning for projects...
  [WARNING] 
  [WARNING] Some problems were encountered while building the effective model 
for org.apache.commons:commons-jexl:jar:2.1.1
  [WARNING] 'build.plugins.plugin.version' for 
org.apache.felix:maven-bundle-plugin is missing. @ 
org.apache.commons:commons-parent:debian, 
/home/lamby/temp/cdt.20160120125708.4BbRf6rkUu/libcommons-jexl2-java-2.1.1/debian/maven-repo/org/apache/commons/commons-parent/debian/commons-parent-debian.pom,
 line 322, column 12
  [WARNING] 
  [WARNING] It is highly recommended to fix these problems because they 
threaten the stability of your build.
  [WARNING] 
  [WARNING] For this reason, future Maven versions might no longer support 
building such malformed projects.
  [WARNING] 
  [INFO]
 
  [INFO] 

  [INFO] Building Commons JEXL 2.1.1
  [INFO] 

  [INFO] 

  [INFO] BUILD FAILURE
  [INFO] 

  [INFO] Total time: 0.174 s
  [INFO] Finished at: 2016-01-20T12:59:10+01:00
  [INFO] Final Memory: 6M/236M
  [INFO] 

  [ERROR] Error resolving version for plugin 
'org.apache.felix:maven-bundle-plugin' from the repositories [local 
(/home/lamby/temp/cdt.20160120125708.4BbRf6rkUu/libcommons-jexl2-java-2.1.1/debian/maven-repo),
 central (https://repo.maven.apache.org/maven2)]: Plugin not found in any 
plugin repository -> [Help 1]
  [ERROR] 
  [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
  [ERROR] Re-run Maven using the -X switch to enable full debug logging.
  [ERROR] 
  [ERROR] For more information about the errors and possible solutions, please 
read the following articles:
  [ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/PluginVersionResolutionException
  /usr/share/cdbs/1/class/maven.mk:92: recipe for target 'mvn-build' failed
  make: *** [mvn-build] Error 1

  [..]

The full build log is attached.


Regards,

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


libcommons-jexl2-java.2.1.1-2.unstable.amd64.log.txt.gz
Description: Binary data

Bug#808484: marked as done (django-stronghold: FTBFS: AttributeError: 'module' object has no attribute 'tests')

[Debian Bug Tracking System]

Your message dated Wed, 20 Jan 2016 14:33:22 +
with message-id 
and subject line Bug#808484: fixed in django-stronghold 0.2.7+debian-2
has caused the Debian Bug report #808484,
regarding django-stronghold: FTBFS: AttributeError: 'module' object has no 
attribute '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.)


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

Dear Maintainer,

The package fails to build:

copying stronghold/tests/testutils.py -> 
/django-stronghold-0.2.7+debian/.pybuild/pythonX.Y_3.4/build/stronghold/tests
   debian/rules override_dh_auto_test
make[1]: Entering directory '/django-stronghold-0.2.7+debian'
python2 test_project/manage.py test --pythonpath=. 
--settings=test_project.settings stronghold.tests
Traceback (most recent call last):
  File "test_project/manage.py", line 10, in 
execute_from_command_line(sys.argv)
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 350, in execute_from_command_line
utility.execute()
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 342, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
  File 
"/usr/lib/python2.7/dist-packages/django/core/management/commands/test.py", 
line 30, in run_from_argv
super(Command, self).run_from_argv(argv)
  File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 
348, in run_from_argv
self.execute(*args, **cmd_options)
  File 
"/usr/lib/python2.7/dist-packages/django/core/management/commands/test.py", 
line 74, in execute
super(Command, self).execute(*args, **options)
  File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 
399, in execute
output = self.handle(*args, **options)
  File 
"/usr/lib/python2.7/dist-packages/django/core/management/commands/test.py", 
line 90, in handle
failures = test_runner.run_tests(test_labels)
  File "/usr/lib/python2.7/dist-packages/django/test/runner.py", line 531, in 
run_tests
suite = self.build_suite(test_labels, extra_tests)
  File "/usr/lib/python2.7/dist-packages/django/test/runner.py", line 422, in 
build_suite
tests = self.test_loader.loadTestsFromName(label)
  File "/usr/lib/python2.7/unittest/loader.py", line 100, in loadTestsFromName
parent, obj = obj, getattr(obj, part)
AttributeError: 'module' object has no attribute 'tests'
debian/rules:10: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/django-stronghold-0.2.7+debian'
debian/rules:7: recipe for target 'build' failed

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

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: django-stronghold
Source-Version: 0.2.7+debian-2

We believe that the bug you reported is fixed in the latest version of
django-stronghold, 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.
Sunil Mohan Adapa  (supplier of updated django-stronghold 
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 22:28:41 +0530
Source: django-stronghold
Binary: python-django-stronghold python3-django-stronghold
Architecture: source all
Version: 0.2.7+debian-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sunil Mohan Adapa 
Description:
 python-django-stronghold - Django app to make all views default login_required
 python3-django-stronghold - Python3 

Bug#812093: libimager-perl: FTBFS: Failed 1/65 test programs. 0/4481 subtests failed.

[Chris Lamb]

Source: libimager-perl
Version: 1.004+dfsg-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,

libimager-perl fails to build from source in unstable/amd64:

  [..]

  ok 30 - check mono is mono
  ok 31 - got basic test image (by name)
  ok 32 - check basic image type
  ok 33 - check basic image channels
  ok 34 - check basic image bits
  ok 35 - check basic isn't mono
  ok 36 - got 16-bit basic test image (by name)
  ok 37 - check 16-bit basic image type
  ok 38 - check 16-bit basic image channels
  ok 39 - check 16-bit basic image bits
  ok 40 - check 16-bit basic isn't mono
  ok 41 - got double basic test image (by name)
  ok 42 - check double basic image type
  ok 43 - check double basic image channels
  ok 44 - check double basic image bits
  ok 45 - check double basic isn't mono
  ok 46 - got gray test image (by name)
  ok 47 - check gray image type
  ok 48 - check gray image channels
  ok 49 - check gray image bits
  ok 50 - check gray isn't mono
  ok 51 - got gray test image (by name)
  ok 52 - check 16-bit gray image type
  ok 53 - check 16-bit gray image channels
  ok 54 - check 16-bit gray image bits
  ok 55 - check 16-bit isn't mono
  ok 56 - got mono image (by name)
  ok 57 - check mono image type
  ok 58 - check mono image channels
  ok 59 - check mono image bits
  ok 60 - check mono is mono
  ok
  t/900-util/020-error.t .. 
  1..7
  ok 1 - use Imager;
  ok 2 - read of junk.ppm should have failed
  ok 3 - got the errors
  ok 4 - entry 0 is an array ref
  ok 5 - entry 0 has 2 elements
  ok 6 - check message
  ok 7 - error code should be 0
  ok
  t/900-util/030-log.t  
  1..6
  ok 1 - open log
  ok 2 - file is there
  ok 3 - check message made it to the log
  ok 4 # skip Logging built
  ok 5 # skip Logging built
  ok 6 # skip Logging built
  ok
  t/900-util/040-limit.t .. 
  1..31
  ok 1 - set limits to 10, 10, 300
  ok 2 - successful check limits in parent
  ok 3 - failed check limits in parent
  ok 4 - 1: set limits to 5 x 5, 75 bytes
  ok 5 - 1: successful check 5 x 5
  ok 6 - 1: failed check 5 x 5, ssize 2
  ok 7 - check limits are still 5 x 5 , 75 bytes
  ok 8 - 2: set limits to 10 x 10, 300 bytes
  ok 9 - 2: successful check 10 x 10
  ok 10 - 2: failed check 10 x 10, ssize 2
  ok 11 - check limits are still 10 x 10 , 300 bytes
  ok 12 - 3: set limits to 15 x 15, 675 bytes
  ok 13 - 3: successful check 15 x 15
  ok 14 - 3: failed check 15 x 15, ssize 2
  ok 15 - check limits are still 15 x 15 , 675 bytes
  ok 16 - 4: set limits to 20 x 20, 1200 bytes
  ok 17 - 4: successful check 20 x 20
  ok 18 - 4: failed check 20 x 20, ssize 2
  ok 19 - check limits are still 20 x 20 , 1200 bytes
  ok 20 - 5: set limits to 25 x 25, 1875 bytes
  ok 21 - 5: successful check 25 x 25
  ok 22 - 5: failed check 25 x 25, ssize 2
  ok 23 - check limits are still 25 x 25 , 1875 bytes
  ok 24 - join child 1
  ok 25 - join child 2
  ok 26 - join child 3
  ok 27 - join child 4
  ok 28 - join child 5
  ok 29 - test we still pass
  ok 30 - test we still fail
  ok 31 - check original main thread limits still set
  ok
  t/900-util/050-matrix.t . 
  1..25
  ok 1 - use Imager::Matrix2d;
  ok 2 - identity matrix
  ok 3 - translate matrix
  ok 4 - translate just x
  ok 5 - translate just y
  ok 6 - rotate matrix
  ok 7 - shear matrix
  ok 8 - scale matrix
  ok 9 - custom matrix
  ok 10 - translate called on rotate with just x
  ok 11 - translate called on rotate with just y
  ok 12 - bad custom matrix
  ok 13 - check error
  ok 14 - mult by unblessed matrix
  ok 15 - mult with unblessed matrix
  ok 16 - mult by three
  ok 17 - mult with three
  ok 18 - mult by hash ref died
  ok 19 - check message
  ok 20 - mult by short array ref died
  ok 21 - check message
  ok 22 - mult by bad scalar died
  ok 23 - check message
  ok 24 - x from rotate (0,0) around (10, 5)
  ok 25 - y from rotate (0,0) around (10, 5)
  ok
  t/900-util/060-extutil.t  
  1..6
  ok 1 - check dirs absolute
  ok 2 - has the -I
  ok 3 - found a header
  ok 4 - got a typemap path
  ok 5 - it exists
  ok 6 - it seems to be the right file
  ok
  t/900-util/060-hlines.t . 
  1..17
  ok 1 - made hline
  ok 2 - check values
  ok 3 - check (-5, 7) added
  ok 4 - check (8, 4) added
  ok 5 - check (3, 3) added
  ok 6 - check (2, 6) added
  ok 7 - check (6, -5, 5) not added
  ok 8 - check (6, 100, 5) not added
  ok 9 - check (-1, 5, 2) not added
  ok 10 - check (10, 5, 2) not added
  ok 11 - check internal overlap merged
  ok 12 - lots of segments
  ok 13 - merge lots of segments
  ok 14 - left merge
  ok 15 - right merge
  ok 16 - make hlines object from image
  ok 17 - check initialized properly
  ok
  t/950-kwalitee/010-pod.t  skipped: POD only tested under automated or 
author testing
  t/950-kwalitee/020-samples.t  
  1..32
  ok 1 - sample file 

Bug#812094: ros-roscpp-core: FTBFS: Could not find a package configuration file provided by "console_bridge"

[Chris Lamb]

Source: ros-roscpp-core
Version: 0.5.6-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,

ros-roscpp-core fails to build from source in unstable/amd64:

  [..]

  //Path to a program.
  NOSETESTS:FILEPATH=NOSETESTS-NOTFOUND
  
  //Path to a program.
  PYTHON_EXECUTABLE:FILEPATH=/usr/bin/python
  
  //Specify specific Python version to use ('major.minor' or 'major')
  PYTHON_VERSION:STRING=
  
  //Path to a library.
  RT_LIBRARY:FILEPATH=/usr/lib/x86_64-linux-gnu/librt.so
  
  //Enable debian style python package layout
  SETUPTOOLS_DEB_LAYOUT:BOOL=ON
  
  //Path to a file.
  _CATKIN_GTEST_INCLUDE:FILEPATH=/usr/include/gtest/gtest.h
  
  //Path to a file.
  _CATKIN_GTEST_SRC:FILEPATH=/usr/src/gtest/src/gtest.cc
  
  //The directory containing a CMake configuration file for catkin.
  catkin_DIR:PATH=/usr/share/catkin/cmake
  
  //The directory containing a CMake configuration file for console_bridge.
  console_bridge_DIR:PATH=console_bridge_DIR-NOTFOUND
  
  //Value Computed by CMake
  
cpp_common_BINARY_DIR:STATIC=/home/lamby/temp/cdt.20160120145910.XuLwsnVWmM/ros-roscpp-core-0.5.6/obj-x86_64-linux-gnu/cpp_common
  
  //Value Computed by CMake
  
cpp_common_SOURCE_DIR:STATIC=/home/lamby/temp/cdt.20160120145910.XuLwsnVWmM/ros-roscpp-core-0.5.6/cpp_common
  
  //Value Computed by CMake
  
gtest_BINARY_DIR:STATIC=/home/lamby/temp/cdt.20160120145910.XuLwsnVWmM/ros-roscpp-core-0.5.6/obj-x86_64-linux-gnu/gtest
  
  //Dependencies for the target
  gtest_LIB_DEPENDS:STATIC=general;-lpthread;
  
  //Value Computed by CMake
  gtest_SOURCE_DIR:STATIC=/usr/src/gtest
  
  //Build gtest's sample programs.
  gtest_build_samples:BOOL=OFF
  
  //Build all of gtest's own tests.
  gtest_build_tests:BOOL=OFF
  
  //Disable uses of pthreads in gtest.
  gtest_disable_pthreads:BOOL=OFF
  
  //Use shared (DLL) run-time lib even when Google Test is built
  // as static lib.
  gtest_force_shared_crt:BOOL=OFF
  
  //Dependencies for the target
  gtest_main_LIB_DEPENDS:STATIC=general;-lpthread;general;gtest;
  
  //Value Computed by CMake
  
roscpp_core_BINARY_DIR:STATIC=/home/lamby/temp/cdt.20160120145910.XuLwsnVWmM/ros-roscpp-core-0.5.6/obj-x86_64-linux-gnu
  
  //Value Computed by CMake
  
roscpp_core_SOURCE_DIR:STATIC=/home/lamby/temp/cdt.20160120145910.XuLwsnVWmM/ros-roscpp-core-0.5.6
  
  //Value Computed by CMake
  
roscpp_traits_BINARY_DIR:STATIC=/home/lamby/temp/cdt.20160120145910.XuLwsnVWmM/ros-roscpp-core-0.5.6/obj-x86_64-linux-gnu/roscpp_traits
  
  //Value Computed by CMake
  
roscpp_traits_SOURCE_DIR:STATIC=/home/lamby/temp/cdt.20160120145910.XuLwsnVWmM/ros-roscpp-core-0.5.6/roscpp_traits
  
  
  
  # INTERNAL cache entries
  
  
  //ADVANCED property for variable: Boost_DIR
  Boost_DIR-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_INCLUDE_DIR
  Boost_INCLUDE_DIR-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_LIBRARY_DIR_DEBUG
  Boost_LIBRARY_DIR_DEBUG-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_LIBRARY_DIR_RELEASE
  Boost_LIBRARY_DIR_RELEASE-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_SYSTEM_LIBRARY_DEBUG
  Boost_SYSTEM_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_SYSTEM_LIBRARY_RELEASE
  Boost_SYSTEM_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_THREAD_LIBRARY_DEBUG
  Boost_THREAD_LIBRARY_DEBUG-ADVANCED:INTERNAL=1
  //ADVANCED property for variable: Boost_THREAD_LIBRARY_RELEASE
  Boost_THREAD_LIBRARY_RELEASE-ADVANCED:INTERNAL=1
  //catkin environment
  
CATKIN_ENV:INTERNAL=/home/lamby/temp/cdt.20160120145910.XuLwsnVWmM/ros-roscpp-core-0.5.6/obj-x86_64-linux-gnu/catkin_generated/env_cached.sh
  
CATKIN_TEST_RESULTS_DIR:INTERNAL=/home/lamby/temp/cdt.20160120145910.XuLwsnVWmM/ros-roscpp-core-0.5.6/obj-x86_64-linux-gnu/test_results
  //ADVANCED property for variable: CMAKE_AR
  CMAKE_AR-ADVANCED:INTERNAL=1
  //This is the directory where this CMakeCache.txt was created
  
CMAKE_CACHEFILE_DIR:INTERNAL=/home/lamby/temp/cdt.20160120145910.XuLwsnVWmM/ros-roscpp-core-0.5.6/obj-x86_64-linux-gnu
  //Major version of cmake used to create the current loaded cache
  CMAKE_CACHE_MAJOR_VERSION:INTERNAL=3
  //Minor version of cmake used to create the current loaded cache
  CMAKE_CACHE_MINOR_VERSION:INTERNAL=4
  //Patch version of cmake used to create the current loaded cache
  CMAKE_CACHE_PATCH_VERSION:INTERNAL=1
  //ADVANCED property for variable: CMAKE_COLOR_MAKEFILE
  CMAKE_COLOR_MAKEFILE-ADVANCED:INTERNAL=1
  //Path to CMake executable.
  CMAKE_COMMAND:INTERNAL=/usr/bin/cmake
  //Path to cpack program executable.
  CMAKE_CPACK_COMMAND:INTERNAL=/usr/bin/cpack
  //Path to ctest program executable.
  CMAKE_CTEST_COMMAND:INTERNAL=/usr/bin/ctest
  //ADVANCED property for variable: CMAKE_CXX_COMPILER
  

Bug#812087: pcscd takes 100 % cpu each time I insert a mass storage USB key

[Ludovic Rousseau]

Le 20/01/2016 14:02, eric2.vale...@orange.com a écrit :

Note that in the laptop there is a build in  broadcom credit card format crypto 
key reader (that you see in the log), but I do not use it although for testing 
purpose I have enabled the driver. But the bug is only if I insert a USB key.




daemon.log:Jan 18 15:17:11 r-x-ceva6380 pcscd[11283]:  
ifdhandler.c:144:CreateChannelByNameOrChannel() failed
daemon.log:Jan 18 15:17:11 r-x-ceva6380 pcscd[11283]: 0032 
readerfactory.c:1097:RFInitializeReader() Open Port 0x20 Failed 
(usb:0a5c/5800:libudev:0:/dev/bus/usb/002/004)
daemon.log:Jan 18 15:17:11 r-x-ceva6380 pcscd[11283]: 0004 
readerfactory.c:372:RFAddReader() Broadcom Corp 5880 [Broadcom USH] 
(0123456789ABCD) init failed.
daemon.log:Jan 19 13:52:56 r-x-ceva6380 pcscd[1604]:  
ifdhandler.c:144:CreateChannelByNameOrChannel() failed
daemon.log:Jan 19 13:52:56 r-x-ceva6380 pcscd[1604]: 0027 
readerfactory.c:1097:RFInitializeReader() Open Port 0x20 Failed 
(usb:0a5c/5800:libudev:0:/dev/bus/usb/002/004)
daemon.log:Jan 19 13:52:56 r-x-ceva6380 pcscd[1604]: 0005 
readerfactory.c:372:RFAddReader() Broadcom Corp 5880 [Broadcom USH] 
(0123456789ABCD) init failed.
daemon.log:Jan 20 09:42:05 r-x-ceva6380 pcscd[1687]:  
ifdhandler.c:144:CreateChannelByNameOrChannel() failed
daemon.log:Jan 20 09:42:05 r-x-ceva6380 pcscd[1687]: 0026 
readerfactory.c:1097:RFInitializeReader() Open Port 0x20 Failed 
(usb:0a5c/5800:libudev:0:/dev/bus/usb/002/004)
daemon.log:Jan 20 09:42:05 r-x-ceva6380 pcscd[1687]: 0004 
readerfactory.c:372:RFAddReader() Broadcom Corp 5880 [Broadcom USH] 
(0123456789ABCD) init failed.
daemon.log:Jan 20 12:56:47 r-x-ceva6380 systemd[1]: pcscd.service: Main process 
exited, code=killed, status=9/KILL
daemon.log:Jan 20 12:56:47 r-x-ceva6380 systemd[1]: pcscd.service: Unit entered 
failed state.
daemon.log:Jan 20 12:56:47 r-x-ceva6380 systemd[1]: pcscd.service: Failed with 
result 'signal'.   < killed it by kill -9 to get CPU back
daemon.log:Jan 20 12:56:47 r-x-ceva6380 pcscd[14663]:  
ifdhandler.c:144:CreateChannelByNameOrChannel() failed
daemon.log:Jan 20 12:56:47 r-x-ceva6380 pcscd[14663]: 0022 
readerfactory.c:1097:RFInitializeReader() Open Port 0x20 Failed 
(usb:0a5c/5800:libudev:0:/dev/bus/usb/002/004)
daemon.log:Jan 20 12:56:47 r-x-ceva6380 pcscd[14663]: 0003 
readerfactory.c:372:RFAddReader() Broadcom Corp 5880 [Broadcom USH] 
(0123456789ABCD) init failed.


It does not look like the problem is the Broadcom reader.

Can you generate a log as documented in 
https://pcsclite.alioth.debian.org/pcsclite.html#support ?
Start the log and then connect your problematic mass-storage USB key.

Thanks

--
 Dr. Ludovic Rousseau

Bug#812096: smc: FTBFS: configure: error: Package requirements (CEGUI-OPENGL >= 0.7.2) were not met:

[Chris Lamb]

Source: smc
Version: 1.9+git20121121-1.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,

smc fails to build from source in unstable/amd64:

  [..]

  cd . &&   CFLAGS="-g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wall" CXXFLAGS="-g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -Wall" CPPFLAGS="-Wdate-time 
-D_FORTIFY_SOURCE=2" LDFLAGS="-Wl,-z,relro -lboost_system" 
/home/lamby/temp/cdt.20160120150439.uTPv8ahNyp/smc-1.9+git20121121/./configure 
--build=x86_64-linux-gnu  --prefix=/usr --includedir="\${prefix}/include" 
--mandir="\${prefix}/share/man" --infodir="\${prefix}/share/info" 
--sysconfdir=/etc --localstatedir=/var --libexecdir="\${prefix}/lib/smc" 
--srcdir=. --disable-maintainer-mode --disable-dependency-tracking 
--disable-silent-rules   
--prefix=/home/lamby/temp/cdt.20160120150439.uTPv8ahNyp/smc-1.9+git20121121/debian/tmp//usr
 --bindir=/usr/games --datadir=/usr/share/games 
  configure: WARNING: unrecognized options: --disable-maintainer-mode
  checking build system type... x86_64-pc-linux-gnu
  checking host system type... x86_64-pc-linux-gnu
  checking for a BSD-compatible install... /usr/bin/install -c
  checking whether build environment is sane... yes
  checking for a thread-safe mkdir -p... /bin/mkdir -p
  checking for gawk... no
  checking for mawk... mawk
  checking whether make sets $(MAKE)... yes
  checking whether make supports nested variables... yes
  checking whether make supports nested variables... (cached) yes
  checking for g++... g++
  checking whether the C++ compiler works... yes
  checking for C++ compiler default output file name... a.out
  checking for suffix of executables... 
  checking whether we are cross compiling... no
  checking for suffix of object files... o
  checking whether we are using the GNU C++ compiler... yes
  checking whether g++ accepts -g... yes
  checking for style of include used by make... GNU
  checking dependency style of g++... none
  checking for pkg-config... /usr/bin/pkg-config
  checking pkg-config is at least version 0.9.0... yes
  checking for main in -lboost_filesystem... yes
  checking for main in -lboost_thread... yes
  checking for main in -lboost_system... yes
  checking for main in -lX11... yes
  checking for main in -lGL... yes
  checking for main in -lGLU... yes
  checking for SDL... yes
  checking for png_init_io in -lpng... yes
  checking for IMG_LoadPNG_RW in -lSDL_image... yes
  checking for IMG_Init in -lSDL_image... yes
  checking for Mix_OpenAudio in -lSDL_mixer... yes
  checking for TTF_Init in -lSDL_ttf... yes
  checking for CEGUI_OPENGL... no
  configure: error: Package requirements (CEGUI-OPENGL >= 0.7.2) were not met:
  
  No package 'CEGUI-OPENGL' found
  
  Consider adjusting the PKG_CONFIG_PATH environment variable if you
  installed software in a non-standard prefix.
  
  Alternatively, you may set the environment variables CEGUI_OPENGL_CFLAGS
  and CEGUI_OPENGL_LIBS to avoid the need to call pkg-config.
  See the pkg-config man page for more details.
  /usr/share/cdbs/1/class/autotools.mk:42: recipe for target 
'debian/stamp-autotools' failed
  make: *** [debian/stamp-autotools] Error 1

  [..]

The full build log is attached.


Regards,

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


smc.1.9+git20121121-1.2.unstable.amd64.log.txt.gz
Description: Binary data

Bug#812087: pcscd takes 100 % cpu each time I insert a mass storage USB key

[eric2.valette]

On 01/20/2016 03:07 PM, Ludovic Rousseau wrote:

Le 20/01/2016 14:02, eric2.vale...@orange.com a écrit :

It does not look like the problem is the Broadcom reader.

Can you generate a log as documented in 
https://pcsclite.alioth.debian.org/pcsclite.html#support ?
Start the log and then connect your problematic mass-storage USB key. 


Will do when I have time. I suspect the USB key does not matter as 
anyway they are not cryptokey just regular usb storage key...


-- eric

_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.