Bug#803212: KDE affected in general, not just kate

[Gregor Riepl]

I see the same crash since my last package upgrade (today).

And it affects not just kate, but _all_ of KDE 5: plasmashell, sddm, konsole,
you name it. The crashes produce different backtraces sometimes, but in
general, it happens after xcb_intern_atom or XInternAtoms. konsole still uses
KDE framework 4 AFAIK, so it calls out to libx11, not libxcb.

Could this be a bug in Xorg?

Bug#803216: torus-trooper: segfault on startup in src/abagames/tt/barrage.d:111

[Linus Lüssing]

Package: torus-trooper
Version: 0.22.dfsg1-9
Severity: grave
Justification: renders package unusable

Hi,

I am currently unable to start torus-trooper as it crashes with a segmentation 
fault. I have downloaded the source package (apt-get source torus-trooper), 
rebuilt it (dpkg-buildpackage) and started it with gdb. The backtrace shows a 
crash in src/abagames/tt/barrage.d:111. See the attached gdb output for details.

Let me know if you need any further information.

Cheers, Linus


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

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

Versions of packages torus-trooper depends on:
ii  libbulletml0v50.0.6-6.1
ii  libc6 2.19-22
ii  libgcc1   1:5.2.1-22
ii  libgl1-mesa-glx [libgl1]  10.6.3-1
ii  libglu1-mesa [libglu1]9.0.0-2.1
ii  libsdl-mixer1.2   1.2.12-11+b1
ii  libsdl1.2debian   1.2.15-11
ii  torus-trooper-data0.22.dfsg1-9

torus-trooper recommends no packages.

torus-trooper suggests no packages.

-- no debconf information
GNU gdb (Debian 7.10-1) 7.10
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from torus-trooper...done.
(gdb) run
Starting program: /tmp/tt-deb/torus-trooper-0.22.dfsg1/torus-trooper 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe5283700 (LWP 26362)]
[Thread 0x7fffe5283700 (LWP 26362) exited]
[New Thread 0x7fffe5283700 (LWP 26363)]

Program received signal SIGSEGV, Segmentation fault.
0x00418b32 in abagames.tt.barrage.BarrageManager.getInstance(immutable(char)[], immutable(char)[]) (
fileName=..., dirName=...) at src/abagames/tt/barrage.d:111
111	if (!parser[dirName][fileName]) {
(gdb) bt
#0  0x00418b32 in abagames.tt.barrage.BarrageManager.getInstance(immutable(char)[], immutable(char)[])
(fileName=..., dirName=...) at src/abagames/tt/barrage.d:111
#1  abagames.tt.barrage.BarrageManager.load() () at src/abagames/tt/barrage.d:105
#2  0x00427a74 in abagames.tt.gamemanager.GameManager.init() (this=...)
at src/abagames/tt/gamemanager.d:63
#3  0x00427364 in abagames.util.sdl.mainloop.MainLoop.initFirst() (this=...)
at src/abagames/util/sdl/mainloop.d:53
#4  abagames.util.sdl.mainloop.MainLoop.loop() (this=...) at src/abagames/util/sdl/mainloop.d:79
#5  0x004291dc in abagames.tt.boot.boot(immutable(char)[][]) (args=...) at src/abagames/tt/boot.d:86
#6  0x00434e7f in __lambda1 (this=0x7fffe170)
at ../../../../src/libphobos/libdruntime/rt/dmain2.d:411
#7  0x00434faf in rt.dmain2._d_run_main(int, char**, extern(C) int(char[][]) function*).tryExec(scope void() delegate) (this=this@entry=0x7fffe170, dg=...)
at ../../../../src/libphobos/libdruntime/rt/dmain2.d:386
#8  0x00435359 in runAll (this=0x7fffe170)
at ../../../../src/libphobos/libdruntime/rt/dmain2.d:411
#9  0x00434faf in rt.dmain2._d_run_main(int, char**, extern(C) int(char[][]) function*).tryExec(scope void() delegate) (this=this@entry=0x7fffe170, dg=...)
at ../../../../src/libphobos/libdruntime/rt/dmain2.d:386
#10 0x00435136 in _d_run_main (argc=1, argv=0x7fffe2b8, mainFunc=)
at ../../../../src/libphobos/libdruntime/rt/dmain2.d:419
#11 0x764f1b45 in __libc_start_main (main=0x406c20 , argc=1, argv=0x7fffe2b8, 
init=, fini=, rtld_fini=, stack_end=0x7fffe2a8)
at libc-start.c:287
#12 0x00407eb3 in _start ()
(gdb) quit
A debugging session is active.

	Inferior 1 [process 26358] will be killed.

Quit anyway? (y or n) y

Bug#784070: is it maybe possible to settle dislikings and fix this bug?

[Ben Hutchings]

On Tue, 2015-10-27 at 17:04 +, Dimitri John Ledkov wrote:
> On 27 October 2015 at 15:42, Ben Hutchings  wrote:
> > On Tue, 2015-10-27 at 18:30 +0300, Michael Tokarev wrote:
> > > 27.10.2015 18:23, Ben Hutchings wrote:
> > > > On Tue, 2015-10-27 at 10:25 +0300, Michael Tokarev wrote:
> > > > > I'm not maintaining mdadm anymore.
> > > > 
> > > > Then why have you not orphaned it?
> > > 
> > > It is team-maintained (or was),
> > 
> > I don't see any sign of anyone else active in the team.
> > 
> 
> I have outstanding patches to upload. And Michael previously asked me
> to continue mdadm maintenance.
[...]

OK, that's good to hear but I didn't see any of this in the public git
repo.

Ben.

-- 
Ben Hutchings
Never attribute to conspiracy what can adequately be explained by stupidity.

Processed: bug 803037 is forwarded to http://www.synfig.org/issues/thebuggenie/synfig/issues/904

[Debian Bug Tracking System]

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

> forwarded 803037 http://www.synfig.org/issues/thebuggenie/synfig/issues/904
Bug #803037 [src:synfigstudio] synfigstudio: FTBFS: uimanager.h:33:27: fatal 
error: sigc++/object.h: No such file or directory
Set Bug forwarded-to-address to 
'http://www.synfig.org/issues/thebuggenie/synfig/issues/904'.
> thanks
Stopping processing here.

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

Processed: tagging 803037

[Debian Bug Tracking System]

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

> tags 803037 + upstream
Bug #803037 [src:synfigstudio] synfigstudio: FTBFS: uimanager.h:33:27: fatal 
error: sigc++/object.h: No such file or directory
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#801564: A possible way to solve this.

[Santiago Garcia Mantinan]

Hi!

I've been doing some tests on this and I think I may have come to a way to
work around this.

The first thing is that we must keep the user settings, but
/etc/squid/squid.conf is not marked as a conffile, anyway keeping the user
settings in mind I did the following:

At preinst move /etc/squid/squid.conf to /etc/squid/squid.conf.pre_3.4_upgrade

Then at postinst we have the new dpkg squid.conf file installed without any
warning so I did:
move /etc/squid/squid.conf to /etc/squid/squid.conf.dpkg-new
sed /etc/squid/squid.conf.pre_3.4_upgrade >/etc/squid/squid.conf

We should take care of other things like permissions of the file, ... but
that's just the idea and it seems to work on my tests.

This is the output with squid/oldstable installed:
# dpkg -i squid-common_3.5.10-2_all.deb squid_3.5.10-2_amd64.deb
(A ler a base de datos ... 255231 files and directories currently installed.)
Preparing to unpack squid-common_3.5.10-2_all.deb ...
Unpacking squid-common (3.5.10-2) over (2.7.STABLE9-4.1+deb7u1) ...
Preparing to unpack squid_3.5.10-2_amd64.deb ...
Unpacking squid (3.5.10-2) over (2.7.STABLE9-4.1+deb7u1) ...
A configurar squid-common (3.5.10-2) ...
A configurar squid (3.5.10-2) ...
A instalar a nova versión do ficheiro de configuración /etc/init.d/squid ...
A instalar a nova versión do ficheiro de configuración /etc/logrotate.d/squid 
...
A instalar a nova versión do ficheiro de configuración 
/etc/resolvconf/update-libc.d/squid ...
Filtering squid.conf manager ACL.
[] Restarting Squid HTTP Proxy: squid2015/10/28 01:04:23| WARNING: (B) 
'::/0' is a subnetwork of (A) '::/0'
2015/10/28 01:04:23| WARNING: because of this '::/0' is ignored to keep splay 
tree searching predictable
2015/10/28 01:04:23| WARNING: You should probably remove '::/0' from the ACL 
named 'all'
2015/10/28 01:04:23| WARNING: (B) '127.0.0.1' is a subnetwork of (A) '127.0.0.1'
2015/10/28 01:04:23| WARNING: because of this '127.0.0.1' is ignored to keep 
splay tree searching predictable
2015/10/28 01:04:23| WARNING: You should probably remove '127.0.0.1' from the 
ACL named 'localhost'
2015/10/28 01:04:23| WARNING: (B) '127.0.0.1' is a subnetwork of (A) '127.0.0.1'
2015/10/28 01:04:23| WARNING: because of this '127.0.0.1' is ignored to keep 
splay tree searching predictable
2015/10/28 01:04:23| WARNING: You should probably remove '127.0.0.1' from the 
ACL named 'localhost'
2015/10/28 01:04:23| WARNING: (B) '127.0.0.0/8' is a subnetwork of (A) 
'127.0.0.0/8'
2015/10/28 01:04:23| WARNING: because of this '127.0.0.0/8' is ignored to keep 
splay tree searching predictable
2015/10/28 01:04:23| WARNING: You should probably remove '127.0.0.0/8' from the 
ACL named 'to_localhost'
2015/10/28 01:04:23| WARNING: (B) '0.0.0.0' is a subnetwork of (A) '0.0.0.0'
2015/10/28 01:04:23| WARNING: because of this '0.0.0.0' is ignored to keep 
splay tree searching predictable
2015/10/28 01:04:23| WARNING: You should probably remove '0.0.0.0' from the ACL 
named 'to_localhost'
2015/10/28 01:04:23| WARNING: (B) '0.0.0.0' is a subnetwork of (A) '0.0.0.0'
2015/10/28 01:04:23| WARNING: because of this '0.0.0.0' is ignored to keep 
splay tree searching predictable
2015/10/28 01:04:23| WARNING: You should probably remove '0.0.0.0' from the ACL 
named 'to_localhost'
2015/10/28 01:04:23| ERROR: Directive 'hierarchy_stoplist' is obsolete.
2015/10/28 01:04:23| ERROR: Directive 'upgrade_http0.9' is obsolete.
2015/10/28 01:04:23| ERROR: Directive 'broken_vary_encoding' is obsolete.
2015/10/28 01:04:23| ERROR: Directive 'extension_methods' is obsolete.
. ok 
Processing triggers for man-db (2.7.0.2-5) ...

And this is what my /etc/squid looks like after the install:

-rw--- 1 root root 169404 Out 28 00:58 squid.conf.pre_3.4_upgrade
-rw-r--r-- 1 root root   1817 Out 28 01:01 errorpage.css
-rw-r--r-- 1 root root 285765 Out 28 01:04 squid.conf.dpkg-new
-rw-r--r-- 1 root root 169440 Out 28 01:04 squid.conf

Of course the squid.conf is based on the old 2.7 version and we have the
.dpkg-new file like if we had told dpkg to keep the old config.

Hope that helps.

Regards.
-- 
Manty/BestiaTester -> http://manty.net

Bug#801564: A possible way to solve this.

[Santiago Garcia Mantinan]

> Of course the squid.conf is based on the old 2.7 version and we have the
> .dpkg-new file like if we had told dpkg to keep the old config.

Now that I have gone over this again... it should have been .dpkg-dist, not
.dpkg-new, which is how dpkg unpacks the original file, not how it keeps it
if we say we want to keep user settings.

Regards.
-- 
Manty/BestiaTester -> http://manty.net

Processed: pending

[Debian Bug Tracking System]

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

> tags 803154 + pending
Bug #803154 [monitoring-plugins-basic] Does not build on hardened systems
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#803212: kate: Crash (segmentation fault) on startup in xcb_send_request

[Kyanos]

Package: kate
Version: 4:15.08.2-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Kate crashes on startup. When running it in GDB, it manages to create
the window before crashing.

Backtrace and GDB output:

Program received signal SIGSEGV, Segmentation fault.
xcb_send_request (c=0x0, flags=flags@entry=1,
vector=vector@entry=0x7fffd550, req=req@entry=0x708d0280 )
at ../../src/xcb_out.c:160
160 ../../src/xcb_out.c: No such file or directory.
(gdb) bt
#0  xcb_send_request (c=0x0, flags=flags@entry=1,
vector=vector@entry=0x7fffd550, req=req@entry=0x708d0280 )
at ../../src/xcb_out.c:160
#1  0x708c5caf in xcb_intern_atom (c=,
only_if_exists=only_if_exists@entry=0 '\000', name_len=,
name=name@entry=0x74cd32e0 "UTF8_STRING") at xproto.c:3338
#2  0x74cc3380 in Atoms::init (this=this@entry=0xf0dc60)
at ../../src/platforms/xcb/netwm.cpp:304
#3  0x74cc7e37 in Atoms::Atoms (c=, this=0xf0dc60)
at ../../src/platforms/xcb/netwm.cpp:83
#4  atomsForConnection (c=c@entry=0x0) at ../../src/platforms/xcb/netwm.cpp:69
#5  0x74cca373 in NETRootInfo::NETRootInfo (this=0x7fffdb20,
connection=0x0, properties=..., properties2=..., screen=-1,
doActivate=) at ../../src/platforms/xcb/netwm.cpp:517
#6  0x7fffd893a0f3 in KWindowSystemPrivateX11::mapViewport (
this=)
at ../../../../src/platforms/xcb/kwindowsystem.cpp:1076
#7  0x7fffd89386ff in KWindowSystemPrivateX11::setOnDesktop (
this=0x7446d0, win=41943045, desktop=1)
at ../../../../src/platforms/xcb/kwindowsystem.cpp:556
#8  0x74cb69dc in KStartupInfo::setNewStartupId (window=0x7aa520,
startup_id=...) at ../../src/kstartupinfo.cpp:717
#9  0x77b60981 in KateApp::startupKate (this=0x7fffe0b0)
at ../../../kate/src/kateapp.cpp:168
#10 0x77b61ead in KateApp::init (this=this@entry=0x7fffe0b0)
at ../../../kate/src/kateapp.cpp:108
#11 0x77ba82b3 in kdemain (argc=1, argv=)
at ../../../kate/src/main.cpp:427
#12 0x777abb45 in __libc_start_main (
main=0x400720 , argc=1, argv=0x7fffe218,
init=, fini=, rtld_fini=,
stack_end=0x7fffe208) at libc-start.c:287
#13 0x0040074e in _start ()

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

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

Versions of packages kate depends on:
ii  kate5-data   4:15.08.2-1
ii  ktexteditor-katepart 5.15.0-1
ii  libc62.19-22
ii  libgit2-23   0.23.1-1
ii  libkf5activities55.15.0-1
ii  libkf5bookmarks5 5.15.0-1
ii  libkf5completion55.15.0-1
ii  libkf5configcore55.15.0-1
ii  libkf5configgui5 5.15.0-1
ii  libkf5configwidgets5 5.15.0-1
ii  libkf5coreaddons55.15.0-1
ii  libkf5dbusaddons55.15.0-1
ii  libkf5guiaddons5 5.15.0-1
ii  libkf5i18n5  5.15.0-1
ii  libkf5iconthemes55.15.0-1
ii  libkf5itemmodels55.15.0-1
ii  libkf5jobwidgets55.15.0-1
ii  libkf5kiocore5   5.15.0-1
ii  libkf5kiofilewidgets55.15.0-1
ii  libkf5kiowidgets55.15.0-1
ii  libkf5newstuff5  5.15.0-1
ii  libkf5notifications5 5.15.0-1
ii  libkf5parts5 5.15.0-1
ii  libkf5plasma55.15.0-1
ii  libkf5service-bin5.15.0+-1
ii  libkf5service5   5.15.0+-1
ii  libkf5texteditor55.15.0-1
ii  libkf5textwidgets5   5.15.0-1
ii  libkf5threadweaver5  5.15.0-1
ii  libkf5wallet-bin 5.15.0-1
ii  libkf5wallet55.15.0-1
ii  libkf5widgetsaddons5 5.15.0-1
ii  libkf5windowsystem5  5.15.0-1
ii  libkf5xmlgui55.15.0-1
ii  libqt5core5a 5.4.2+dfsg-9
ii  libqt5dbus5  5.4.2+dfsg-9
ii  libqt5gui5   5.4.2+dfsg-9
ii  libqt5sql5   5.4.2+dfsg-9
ii  libqt5widgets5   5.4.2+dfsg-9
ii  libqt5xml5   5.4.2+dfsg-9
ii  libstdc++6   5.2.1-22
ii  plasma-framework 5.15.0-1
ii  qml-module-

Bug#802811: libqt5x11extras5: causes konsole to segfault in libX11 on startup

[Diego Gomez]

I can confirm this problem.
After upgrading libqt5x11extras5 from 5.4.2-2+b1 to 5.5.1-2
I get segfaults on execution of nearly all KDE programs.

Downgrading to the previous version solved the issue.

--
Diego.-

Bug#784070: is it maybe possible to settle dislikings and fix this bug?

[Francesco Poli]

On Tue, 27 Oct 2015 17:04:43 + Dimitri John Ledkov wrote:

[...]
> I have outstanding patches to upload. And Michael previously asked me
> to continue mdadm maintenance.

That's really good news, Dimitri!
Thanks a lot for stepping in, it's definitely appreciated.

I think you should upload a version (or Debian revision) of mdadm with
Michael's name replaced by yours in the Uploaders control field.

Then, if you feel you could use some help from other people, you might
consider the possibility of filing a RFH bug report (about mdadm)
against the wnpp pseudo package...


Thanks for your time and helpfulness.
Bye!

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


pgpvwpCBQMnm3.pgp
Description: PGP signature

Bug#803178: marked as done (libmongodb-perl: FTBFS on various architectures)

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2015 23:05:06 +
with message-id 
and subject line Bug#803178: fixed in libmongodb-perl 1.0.2-2
has caused the Debian Bug report #803178,
regarding libmongodb-perl: FTBFS on various architectures
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Yesterday's 1.0.2-1 upload failed to build on mips, powerpc, and
s390x (plus hppa and ppc64):

https://buildd.debian.org/status/package.php?p=libmongodb-perl
https://buildd.debian.org/status/logs.php?pkg=libmongodb-perl&ver=1.0.2-1

The failing tests seem to be the same on all architectures, and they
are new in this release.

Cheers,
gregor

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJWL7kLXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGfcwP/1WrCIFUU45q89fZWNLGi/7T
KuVVlpFkdaNUZde9oMqAX1i8X0opkwhOkBHDv6Hk/cLLjR3hZPFLGFY3y8gWnwFM
aHgIpWk8oWx7cWPnSwCmFHmGDCeIPMR8OyYfUNP3eFP7r6eU8Hg0j2Z9qAko8g2s
H0GA6YL4Gf2kk3jZF3s6FsZlVrqk7XBoJ8KWhGLtQJDd8T2QsxgN+mTykdp1Bl2w
Bqep8lRiuSb7lU0lWPEEAQHdh/XVMmEmxag0bacx3zUHIeXYz8t5cZtzco9yKoVk
4QVzr9rNZCHws2xUQfKpW7MjuYHjmSfQvEhpmDO15GXblAs6OusnKsac/tvYxm2y
0QdZCTMgSEslLtHh8M0VR3IIzNFrdM6u0Yce0KeAThkoyn+3XLKvUqw36/LH5e2U
fmPFlVA0h5m7feuiKvuzUywT/pjvZHdegU4f5tjLQZ4YvE4C47DGL6+nbTJFShuY
MTtR0fRWBmIHjK1auqS70x1oJgcUCKShz2w67Dcy1MPQrUweIhKNHhiGj2rgBm1M
Fdey+8u+nPntEZ2+2Pd1mv1iRVqxZDg/c3HzgnhifpyZg5BqKHH/ceO/BttmatIy
6pcMKUEpfDpNl3b0K4baUAqHjoXC76xQbL+sD1eubGSUfzH1Um1ujUq5CokdoG6W
V4GN1ByIT4SL9yU4XaaK
=+/VU
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: libmongodb-perl
Source-Version: 1.0.2-2

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libmongodb-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: Tue, 27 Oct 2015 23:51:42 +0100
Source: libmongodb-perl
Binary: libmongodb-perl
Architecture: source
Version: 1.0.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 803178
Description: 
 libmongodb-perl - Mongo Driver for Perl
Changes:
 libmongodb-perl (1.0.2-2) unstable; urgency=medium
 .
   * Add patch from Niko Tyni to fix endianness issue in tests.
 (Closes: #803178)
Checksums-Sha1: 
 f7f4b29e4203a0dd8d1d9e1f52ea330a8de920f4 2816 libmongodb-perl_1.0.2-2.dsc
 b679cc97c356e09cd4ca71f755a2e3728a07f091 7628 
libmongodb-perl_1.0.2-2.debian.tar.xz
Checksums-Sha256: 
 a70ce19d1f4cd0300e2beb903586172d8e69431323086e0ef26862369228012a 2816 
libmongodb-perl_1.0.2-2.dsc
 96f4880b1be06d661c392c32efa41863898c6404b6f8e918c7a45889258ed58a 7628 
libmongodb-perl_1.0.2-2.debian.tar.xz
Files: 
 7245e758325947aa86ccf12afae5c01a 2816 perl optional libmongodb-perl_1.0.2-2.dsc
 caa80fa48da9ae3589fa5d3bcd66c064 7628 perl optional 
libmongodb-perl_1.0.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJWMACGXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGVYcP/1OMNI5v+O+wiABfoYgBWGIY
Soxz62X2HSngGmvLAyWFAjwe+w2dwRBWZI/8i4txa09jfT4iOqe7cESAGwUoOd8x
f/4de9T+aVwR4hCdDUpYqTy/ablkdNbs+teALZv9x++iGC+flo/TL9Kiv2Ia6oaa
Tb47pJCw2I6RMrthQrCTC9EsUFIv/vH38Wwg5t1fJvWZYoxlwwVI0AeDOYw11VSX
//appXWMFJBEssV5pHmGIQR0ytJD3etSUnag1wSDu+YVXWwNhraNGePdUJHfk7tz
T9QgkoLbiWnh6Fr/yNcQpQyRNXHr05iIvFOZ5sa1njpgQSz4IAUuR8UbWtxCZGqf
7exwnDgatI7/SXQswVA1D9giC1aqk1MbmDU8VJ4CehDIYQxcW/uHGvkr1MKtmHO9
Zs2wRsImqfPbGlDPWrjlNdPY0FgloiWfpqfx8BFxRIRl3n0DQuzxbH2VvZ6zbcWX
1Fw9k/9n98sZsBDjCkoO81ovCDz7UyMU16+8mgt1tNiCpLIrAfI4N4eLENCsXzOG
FdmmfB41AgQMXQ6v041

Bug#803204: marked as done (libiksemel: utterly insecure GNUTLS settings)

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2015 23:05:00 +
with message-id 
and subject line Bug#803204: fixed in libiksemel 1.4-3
has caused the Debian Bug report #803204,
regarding libiksemel: utterly insecure GNUTLS settings
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.)


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

Package: libiksemel
Version: 1.4-2
Severity: grave
tags: security
Control: affects -1 = zabbix-server-pgsql zabbix-server-mysql


Coin,

Since I changed my XMPP server, Zabbix failed to send alerts via XMPP 
with "tls handshake failed". The XMPP server said "no shared cipher". 
After some research to see how Zabbix do its job I ended up into this 
library. I confirmed there is no way to setup the ciphers into Zabbix, 
but I was then astonished to see them hardcoded and very low grade in 
libiksemel:

   const int protocol_priority[] = { GNUTLS_TLS1, GNUTLS_SSL3, 0 };
   const int kx_priority[] = { GNUTLS_KX_RSA, 0 };
   const int cipher_priority[] = { GNUTLS_CIPHER_3DES_CBC, 
GNUTLS_CIPHER_ARCFOUR, 0};
   const int comp_priority[] = { GNUTLS_COMP_ZLIB, GNUTLS_COMP_NULL, 
0 };

   const int mac_priority[] = { GNUTLS_MAC_SHA, GNUTLS_MAC_MD5, 0 };

SSL3, 3DES, RC4, SSL compression… With this setting not only low grade 
ciphers are available, but higher grades are disabled. So this is a 
major security issue, also affecting stable.


The following patch fixes the security problem (and compatibility 
problem with servers rejecting low grade ciphers). You should 
nevertheless proofread my choices, as I'm no security expert. The patch 
does not change the original priority lists because I failed somehow to 
fix them all, so I replaced it by a priority string (which is a 
non-obsolete method to do it anyway).


Regards.

--
Marc DequènesIndex: libiksemel-1.4/src/stream.c
===
--- libiksemel-1.4.orig/src/stream.c
+++ libiksemel-1.4/src/stream.c
@@ -63,11 +63,7 @@ tls_pull (iksparser *prs, char *buffer,
 static int
 handshake (struct stream_data *data)
 {
-	const int protocol_priority[] = { GNUTLS_TLS1, GNUTLS_SSL3, 0 };
-	const int kx_priority[] = { GNUTLS_KX_RSA, 0 };
-	const int cipher_priority[] = { GNUTLS_CIPHER_3DES_CBC, GNUTLS_CIPHER_ARCFOUR, 0};
-	const int comp_priority[] = { GNUTLS_COMP_ZLIB, GNUTLS_COMP_NULL, 0 };
-	const int mac_priority[] = { GNUTLS_MAC_SHA, GNUTLS_MAC_MD5, 0 };
+	const char *priority_string = "SECURE256:+SECURE192:-VERS-TLS-ALL:+VERS-TLS1.2";
 	int ret;
 
 	if (gnutls_global_init () != 0)
@@ -80,11 +76,7 @@ handshake (struct stream_data *data)
 		gnutls_certificate_free_credentials (data->cred);
 		return IKS_NOMEM;
 	}
-	gnutls_protocol_set_priority (data->sess, protocol_priority);
-	gnutls_cipher_set_priority(data->sess, cipher_priority);
-	gnutls_compression_set_priority(data->sess, comp_priority);
-	gnutls_kx_set_priority(data->sess, kx_priority);
-	gnutls_mac_set_priority(data->sess, mac_priority);
+	gnutls_priority_set_direct(data->sess, priority_string, NULL);
 	gnutls_credentials_set (data->sess, GNUTLS_CRD_CERTIFICATE, data->cred);
 
 	gnutls_transport_set_push_function (data->sess, (gnutls_push_func) tls_push);
--- End Message ---
--- Begin Message ---
Source: libiksemel
Source-Version: 1.4-3

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

Debian distribution maintenance software
pp.
Dmitry Smirnov  (supplier of updated libiksemel 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, 28 Oct 2015 09:51:46 +1100
Source: libiksemel
Binary: libiksemel-dev libiksemel3 libiksemel-utils
Architecture: source amd64
Version: 1.4-3
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Dmitry Smirnov 
Description:
 libiksemel-dev - C library for the Jabber IM platform - development files
 libiksemel-utils - utilities from the iksemel library
 libiksemel3 - C library for the Jabber IM platform
Closes: 80

Bug#803072: marked as done (qlipper: FTBFS: error: ambiguous overload for 'operator<<' (operand types are 'QDataStream' and 'int'))

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2015 23:05:17 +
with message-id 
and subject line Bug#803072: fixed in qlipper 5.0.0+20150823-2
has caused the Debian Bug report #803072,
regarding qlipper: FTBFS: error: ambiguous overload for 'operator<<' (operand 
types are 'QDataStream' and 'int')
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.)


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

qlipper fails to build from source in unstable/amd64:

  [..]

  /build/qlipper-5.0.0+20150823/src/qlipperpreferences.cpp: In function
  'QDataStream& operator<<(QDataStream&, const ClipboardContent&)':
  /build/qlipper-5.0.0+20150823/src/qlipperpreferences.cpp:26:9: error:
  ambiguous overload for 'operator<<' (operand types are 'QDataStream'
  and 'int')
   out << size;
   ^
  In file included from
  /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:41:0,
   from
   /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:41,
   from
   /usr/include/x86_64-linux-gnu/qt5/QtCore/qsettings.h:37,
   from
   /usr/include/x86_64-linux-gnu/qt5/QtCore/QSettings:1,
   from
   /build/qlipper-5.0.0+20150823/src/qlipperpreferences.h:23,
   from
   /build/qlipper-5.0.0+20150823/src/qlipperpreferences.cpp:20:
  /usr/include/x86_64-linux-gnu/qt5/QtCore/qchar.h:584:28: note:
  candidate: QDataStream& operator<<(QDataStream&, QChar)
   Q_CORE_EXPORT QDataStream &operator<<(QDataStream &, QChar);
  ^
  In file included from
  /usr/include/x86_64-linux-gnu/qt5/QtCore/qsettings.h:38:0,
   from
   /usr/include/x86_64-linux-gnu/qt5/QtCore/QSettings:1,
   from
   /build/qlipper-5.0.0+20150823/src/qlipperpreferences.h:23,
   from
   /build/qlipper-5.0.0+20150823/src/qlipperpreferences.cpp:20:
  /usr/include/x86_64-linux-gnu/qt5/QtCore/qvariant.h:534:28: note:
  candidate: QDataStream& operator<<(QDataStream&, const QVariant&)
   Q_CORE_EXPORT QDataStream& operator<< (QDataStream& s, const
   QVariant& p);
  ^
  /build/qlipper-5.0.0+20150823/src/qlipperpreferences.cpp: In function
  'QDataStream& operator>>(QDataStream&, ClipboardContent&)':
  /build/qlipper-5.0.0+20150823/src/qlipperpreferences.cpp:42:11: error:
  invalid conversion from 'int' to 'QVariant::Type' [-fpermissive]
   in >> size;
 ^
  In file included from
  /usr/include/x86_64-linux-gnu/qt5/QtCore/qsettings.h:38:0,
   from
   /usr/include/x86_64-linux-gnu/qt5/QtCore/QSettings:1,
   from
   /build/qlipper-5.0.0+20150823/src/qlipperpreferences.h:23,
   from
   /build/qlipper-5.0.0+20150823/src/qlipperpreferences.cpp:20:
  /usr/include/x86_64-linux-gnu/qt5/QtCore/qvariant.h:535:28: note:  
  initializing argument 2 of 'QDataStream& operator>>(QDataStream&,
  QVariant::Type&)'
   Q_CORE_EXPORT QDataStream& operator>> (QDataStream& s,
   QVariant::Type& p);
  ^
  /build/qlipper-5.0.0+20150823/src/qlipperpreferences.cpp:42:11: error:
  cannot bind rvalue '(QVariant::Type)size' to 'QVariant::Type&'
   in >> size;
 ^
  [ 83%] Building CXX object
  CMakeFiles/qlipper.dir/src/moc_qlippermodel.cpp.o
  /usr/bin/c++   -DIS_CMAKE -DQLIPPER_VERSION=\"5.0.0\" -DQT_CORE_LIB
  -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_WIDGETS_LIB
  -DTRANSLATION_DIR=\"/usr/share/qlipper/translations\" -g -O2
  -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
  -D_FORTIFY_SOURCE=2  -I/usr/include/x86_64-linux-gnu/qt5/QtGui/5.5.1
  -I/usr/include/x86_64-linux-gnu/qt5/QtGui/5.5.1/QtGui
  -I/usr/include/x86_64-linux-gnu/qt5/QtCore/5.5.1
  -I/usr/include/x86_64-linux-gnu/qt5/QtCore/5.5.1/QtCore
  -I/build/qlipper-5.0.0+20150823/src
  -I/build/qlipper-5.0.0+20150823/obj-x86_64-linux-gnu
  -I/build/qlipper-5.0.0+20150823/obj-x86_64-linux-gnu/src
  -I/build/qlipper-5.0.0+20150823/qkeysequencewidget
  -I/build/qlipper-5.0.0+20150823/qxt
  -I/build/qlipper-5.0.0+20150823/qmenuview -isystem
  /usr/include/x86_64-linux-gnu/qt5 -isyste

Bug#803178: libmongodb-perl: FTBFS on various architectures

[gregor herrmann]

On Tue, 27 Oct 2015 17:30:10 -0400, David Golden wrote:

> > Adding some diagnostics indicates the actual data encoding is stable
> > between the platforms, but the test suite expectations depend on the
> > endianness. The attached patch seems to fix this on at least s390x,
> > but perhaps we should have a test run with it before pushing it upstream.
> I only had a chance to skim the output, but that was my assessment as
> well.  I have no problem applying that patch, but a test to verify would be
> appreciated (and would save us another round of automated failures).

Ah, different mailfolder, new mail :)

Thanks for chiming in here, David.

You can follow the output of the buildds with Niko's patch applied at
https://buildd.debian.org/status/package.php?p=libmongodb-perl

and the patches are at
https://anonscm.debian.org/cgit/pkg-perl/packages/libmongodb-perl.git
https://anonscm.debian.org/cgit/pkg-perl/packages/libmongodb-perl.git/tree/debian/patches


Cheers,
gregor

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Fleetwood Mac: No Questions Asked


signature.asc
Description: Digital Signature

Bug#803204: tagged as pending

[Dmitry Smirnov]

tag 803204 pending
--

We believe that the bug #803204 you reported has been fixed in the Git
repository. You can see the commit message below and/or inspect the
commit contents at:

http://anonscm.debian.org/cgit/collab-maint/libiksemel.git/diff/?id=ba5da30

(This message was generated automatically by
 'git-post-receive-tag-pending-commitmsg' hook).
---
commit ba5da30
Author: Dmitry Smirnov 
Date:   Tue Oct 27 22:48:48 2015

New patch to fix insecure GNUTLS settings (Closes: #803204)

 Thanks, Marc Dequènes (duck).

Processed: Bug#803204 tagged as pending

[Debian Bug Tracking System]

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

> tag 803204 pending
Bug #803204 [libiksemel] libiksemel: utterly insecure GNUTLS settings
Added tag(s) pending.
> --
Stopping processing here.

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

Bug#803178: libmongodb-perl: FTBFS on various architectures

[gregor herrmann]

On Tue, 27 Oct 2015 22:53:08 +0200, Niko Tyni wrote:

> > https://buildd.debian.org/status/package.php?p=libmongodb-perl
> > https://buildd.debian.org/status/logs.php?pkg=libmongodb-perl&ver=1.0.2-1
> > 
> > The failing tests seem to be the same on all architectures, and they
> > are new in this release.
> 
> It's clearly an endianness issue. All the failing platforms are big
> endian and this looks pretty clear:

That was my guess too.
 
> Adding some diagnostics indicates the actual data encoding is stable
> between the platforms, but the test suite expectations depend on the
> endianness. The attached patch seems to fix this on at least s390x,
> but perhaps we should have a test run with it before pushing it upstream.

Thanks a lot!

I've uploaded the package with your patch now, let's see what the
buildds say.

As for forwarding upstream, does anyone already have an account at
https://jira.mongodb.org/browse/PERL ?
(There's another patch in the package but that's just spelling
fixes.)


Cheers,
gregor

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Cat Stevens: Can't Keep It In


signature.asc
Description: Digital Signature

Processed: bug 803204 is forwarded to https://github.com/meduketto/iksemel/issues/48

[Debian Bug Tracking System]

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

> forwarded 803204 https://github.com/meduketto/iksemel/issues/48
Bug #803204 [libiksemel] libiksemel: utterly insecure GNUTLS settings
Set Bug forwarded-to-address to 
'https://github.com/meduketto/iksemel/issues/48'.
> thanks
Stopping processing here.

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

Bug#802811: libqt5x11extras5: causes konsole to segfault in libX11 on startup

[Lisandro Damián Nicanor Pérez Meyer]

On Tuesday 27 October 2015 21:54:38 Raphael Geissert wrote:
> Hi Lisandro!
> 
> On Tue, 27 Oct 2015 15:30:42 -0300 Lisandro Damián Nicanor Pérez Meyer
> 
>  wrote:
> > Hi everyone! We possibly have two issues here.
> > 
> > The first one is the reported one, which should be fixed.
> > 
> > Now the second one might most probably be because qtx11extras migrated to
> > testing when it shouldn't have. This is the first time it happens for us.
> 
> Doesn't that sound like there's a missing dependency, somewhere?
> It sounds like a person using a testing-unstable mix would also be affected.

Actually libqt5x11extras5 didn't use any new symbols in 5.5.x, so the 
dependencies got fullfiled in testing... and migrated.

We need to ensure to make each qt submodule depend on the version of qtbase it 
was built with (I think we do something very similar for KDE too).


-- 
http://www.tiraecol.net/modules/comic/comic.php?content_id=162

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


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

Bug#803130: marked as done (libdevel-cover-perl and golang-golang-x-tools: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2015 22:20:11 +
with message-id 
and subject line Bug#803130: fixed in golang-golang-x-tools 
1:0.0~git20151026.0.0f9d71c-2
has caused the Debian Bug report #803130,
regarding libdevel-cover-perl and golang-golang-x-tools: 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.)


-- 
803130: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803130
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: golang-golang-x-tools,libdevel-cover-perl
Version: golang-golang-x-tools/1:0.0~git20151026.0.0f9d71c-1
Version: libdevel-cover-perl/1.21-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2015-10-27
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:


(Reading database ... 10923 files and directories currently installed.)
Preparing to unpack .../perl_5.20.2-6_amd64.deb ...
Unpacking perl (5.20.2-6) over (5.18.2-2) ...
Preparing to unpack .../libtext-charwidth-perl_0.04-7+b3_amd64.deb ...
Unpacking libtext-charwidth-perl (0.04-7+b3) over (0.04-7+b2) ...
Preparing to unpack .../perl-modules_5.20.2-6_all.deb ...
Unpacking perl-modules (5.20.2-6) over (5.18.2-7) ...
Preparing to unpack .../perl-base_5.20.2-6_amd64.deb ...
Unpacking perl-base (5.20.2-6) over (5.18.2-2) ...
Processing triggers for man-db (2.7.4-1) ...
Setting up perl-base (5.20.2-6) ...
(Reading database ... 10273 files and directories currently installed.)
Preparing to unpack .../liblocale-gettext-perl_1.07-1_amd64.deb ...
Unpacking liblocale-gettext-perl (1.07-1) over (1.05-7+b2) ...
Preparing to unpack .../libtext-iconv-perl_1.7-5+b2_amd64.deb ...
Unpacking libtext-iconv-perl (1.7-5+b2) over (1.7-5+b1) ...
Selecting previously unselected package libdb5.3:amd64.
Preparing to unpack .../libdb5.3_5.3.28-11_amd64.deb ...
Unpacking libdb5.3:amd64 (5.3.28-11) ...
Selecting previously unselected package libhtml-tagset-perl.
Preparing to unpack .../libhtml-tagset-perl_3.20-2_all.deb ...
Unpacking libhtml-tagset-perl (3.20-2) ...
Selecting previously unselected package liburi-perl.
Preparing to unpack .../liburi-perl_1.69-1_all.deb ...
Unpacking liburi-perl (1.69-1) ...
Selecting previously unselected package libhtml-parser-perl.
Preparing to unpack .../libhtml-parser-perl_3.71-2_amd64.deb ...
Unpacking libhtml-parser-perl (3.71-2) ...
Selecting previously unselected package libdevel-cover-perl.
Preparing to unpack .../libdevel-cover-perl_1.21-1_amd64.deb ...
Unpacking libdevel-cover-perl (1.21-1) ...
Selecting previously unselected package libjs-jquery.
Preparing to unpack .../libjs-jquery_1.11.3+dfsg-4_all.deb ...
Unpacking libjs-jquery (1.11.3+dfsg-4) ...
Selecting previously unselected package libjs-jquery-ui.
Preparing to unpack .../libjs-jquery-ui_1.10.1+dfsg-1_all.deb ...
Unpacking libjs-jquery-ui (1.10.1+dfsg-1) ...
Selecting previously unselected package golang-golang-x-tools-dev.
Preparing to unpack 
.../golang-golang-x-tools-dev_1%3a0.0~git20151026.0.0f9d71c-1_all.deb ...
Unpacking golang-golang-x-tools-dev (1:0.0~git20151026.0.0f9d71c-1) ...
Selecting previously unselected package golang-golang-x-tools.
Preparing to unpack 
.../golang-golang-x-tools_1%3a0.0~git20151026.0.0f9d71c-1_amd64.deb ...
Unpacking golang-golang-x-tools (1:0.0~git20151026.0.0f9d71c-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/golang-golang-x-tools_1%3a0.0~git20151026.0.0f9d71c-1_amd64.deb
 (--unpack):
 trying to overwrite '/usr/bin/cover', which is also in package 
libdevel-cover-perl 1.21-1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Processing triggers for man-db (2.7.4-1) ...
Errors were encountered while processing:
 
/var/cache/apt/archives/golang-golang-x-tools_1%3a0.0~git20151026.0.0f9d71c-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


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 

Bug#802113: marked as done (zope.i18n: FTBFS: Tries to download zope.testing from pypy)

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2015 22:22:20 +
with message-id 
and subject line Bug#802113: fixed in zope.i18n 4.0.1-3
has caused the Debian Bug report #802113,
regarding zope.i18n: FTBFS: Tries to download zope.testing from pypy
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.)


-- 
802113: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802113
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zope.i18n
Version: 4.0.1-2
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 without downloading external dependencies.
Policy requires the package not to use external dependencies, and,
hence, the builders run without a network connection:

Ran 468 tests in 3.677s

OK
I: pybuild base:170: python3.5 setup.py test 
running test
Searching for zope.testing
Reading https://pypi.python.org/simple/zope.testing/
Download error on https://pypi.python.org/simple/zope.testing/: [Errno 111] 
Connection refused -- Some packages may not be found!
Couldn't find index page for 'zope.testing' (maybe misspelled?)
Scanning index of all packages (this may take a while)
Reading https://pypi.python.org/simple/
Download error on https://pypi.python.org/simple/: [Errno 111] Connection 
refused -- Some packages may not be found!
No local packages or download links found for zope.testing
error: Could not find suitable distribution for 
Requirement.parse('zope.testing')
E: pybuild pybuild:262: test: plugin distutils failed with: exit code=1: 
python3.5 setup.py test 
dh_auto_test: pybuild --test -i python{version} -p 3.5 3.4 --dir . returned 
exit code 13


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

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: zope.i18n
Source-Version: 4.0.1-3

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

Debian distribution maintenance software
pp.
Barry Warsaw  (supplier of updated zope.i18n 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, 27 Oct 2015 17:48:35 -0400
Source: zope.i18n
Binary: python-zope.i18n python3-zope.i18n
Architecture: source all
Version: 4.0.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian/Ubuntu Zope Team 

Changed-By: Barry Warsaw 
Description:
 python-zope.i18n - Zope Internationalization Support
 python3-zope.i18n - Zope Internationalization Support
Closes: 802113
Changes:
 zope.i18n (4.0.1-3) unstable; urgency=medium
 .
   * d/patches/setup-py-requires.patch: Added to prevent the attempted
 downloading of zope.testing from PyPI even though it's already a
 Build-Depends.  (Closes: #802113)
   * d/tests/control: Use the simpler Test-Command syntax for the smoketests.
   * d/tests/smoketest-{2,3}: Removed.
Checksums-Sha1:
 9e744485212fb8dfab80423cfb59b7ec8ac3ec43 2627 zope.i18n_4.0.1-3.dsc
 9f1c6ffe0d36ea9b3b296c6a22cb1d4275f97029 5236 zope.i18n_4.0.1-3.debian.tar.xz
 04efde55a278cee85878981910bc07e4f09e8042 302398 
python-zope.i18n_4.0.1-3_all.deb
 1627362ba348f5fe09025e11f8b3a5d0d6714990 302196 
python3-zope.i18n_4.0.1-3_all.deb
Checksums-Sha256:
 7409b6ed4c25e792ae315037be54c7767fb7833c86af139bec97193b4bb569ed 2627 
zope.i18n_4.0.1-3.dsc
 a60e44e67d8f80e213b98f56fa351674435493700bbaf6bf83306851c793485b 5236 
zope.i18n_4.0.1-3.debian.tar.xz
 69e4366f3a6f4af1dfb8c0bcac6a1300cb718916ddc92511f767a7cbba09a181 302398 
python-zope.i18n_4.0.1-3_all.deb
 9b20668c3d2362e2bc576055310369dec35d9b7ef72394b651bc5caf9aceee80 302196 
python3-zope.i18n_4.0.1-3_all.deb
Files:
 d88cccf900898348c9437c0cb8171cc8 2627 zope extra zope.i18n_4.0.1-3.dsc
 08560011160c0407bda7535ef245ce9f 5236 zope extra 
zope.i18n_4.0.1-3.debian.tar.xz
 1650d96ecf4074689d92f3fc668f8885 302398 zope extra 
python-zope.i18n_4.0.1-3_all.

Bug#789108: marked as done (FTBFS: Graphics.hs:91: No instance for (TwoDimensionalTextureTarget (Maybe a0)))

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2015 22:21:42 +
with message-id 
and subject line Bug#789108: fixed in raincat 1.1.1.2-2
has caused the Debian Bug report #789108,
regarding FTBFS: Graphics.hs:91: No instance for (TwoDimensionalTextureTarget 
(Maybe a0))
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.)


-- 
789108: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789108
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: raincat
Version: 1.1.1.2-1
Severity: serious
Tags: sid stretch
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

The package fails to build in sid:

rc/Nxt/Graphics.hs:91:5:
No instance for (TwoDimensionalTextureTarget (Maybe a0))
  arising from a use of ‘texImage2D’
In a stmt of a 'do' block:
  texImage2D Nothing NoProxy 0 RGBA' surfaceSize 0 pixelData

The full build log can be seen on the Reproducible Builds builder:
https://reproducible.debian.net/rb-pkg/unstable/amd64/raincat.html

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

Kernel: Linux 3.19.0-20-generic (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: raincat
Source-Version: 1.1.1.2-2

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated raincat package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 27 Oct 2015 21:54:22 +0100
Source: raincat
Binary: raincat raincat-data
Architecture: source
Version: 1.1.1.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Description:
 raincat- 2D puzzle game featuring a fuzzy little cat
 raincat-data - 2D puzzle game featuring a fuzzy little cat - data files
Closes: 789108
Changes:
 raincat (1.1.1.2-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Markus Koschany ]
   * Add opengl-2.9.patch and fix FTBFS with newer versions of OpenGL.
 (Closes: #789108)
   * Declare compliance with Debian Policy 3.9.6.
   * raincat.desktop: Add keywords and GenericName and Comment in German.
   * Fix debian/copyright syntax to silence Lintian warnings.
   * Drop raincat-dbg package because it is not of sufficient use for most
 users. It also appears that the debug file did not contain debug
 symbols.
   * Remove dh-buildinfo from Build-Depends. It is no strictly required
 build-dependency.
   * wrap-and-sort -sa.
   * Vcs-Browser: Use https.
 .
   [ Evgeni Golov ]
   * Correct Vcs-* URLs to point to anonscm.debian.org
Checksums-Sha1:
 d331bdb0fc5d0c27c192555ebfcc155468c1bf52 2433 raincat_1.1.1.2-2.dsc
 739232d2767508b8d6ea4fa5a2668727a7c80ea8 35276 raincat_1.1.1.2-2.debian.tar.xz
Checksums-Sha256:
 0d63d8224350d674756b148a293f7af778a139e9393e55469f6cb087a268135f 2433 
raincat_1.1.1.2-2.dsc
 5935bc6fdecdc78b0093e2520473167b79e8425ee5a407859c4fffeec22bc481 35276 
raincat_1.1.1.2-2.debian.tar.xz
Files:
 d1064cf99467194aba0c338c185e88eb 2433 games optional raincat_1.1.1.2-2.dsc
 3bba0a1653c7ecc2113b361a706d7f33 35276 games optional 
raincat_1.1.1.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJWL+ivXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBQ0YzRDA4OEVGMzJFREVGNkExQTgzNUZE
OUFEMTRCOTUxM0I1MUU0AAoJENmtFLlRO1HkoZ0QAIlgfXHgod+z9IlEFY8sR3rz
xQN1gnEo7QwCRoTIW9ZL0dK0l6v5S+3X27YgotSCAWjhi/JcLJaabbBDwP5X6HlM
pm8em74mM6ATRbukfO+et1ZdT9Mmfnzcr+k/875Bkh/ZKxsJ7/TQqEGrzGVv1jpg
US8pXqvVhUXR/Wp0P9yjPWweyQmHCW56FSj5jsUFgoerVohhZ03H6+Fuy+/gCcWv
wzpmRVz8lVNlOnShm8L4zLJe8+/RevTkOAy9jbFLNeq21ssbFNJhBhBxRdf1slaj
GCyv91VpT7QdFgG5EYgUVA6T2kKgEUkc5Elsuka7B/3fa3IQpCvyvfykPNyjX96g
I54OQh0SStxy5x7yr4MjrvKUsX9+l5COpocTIfzQ4zGDHO1UI17ScKfwji7wmrDG
YvdvOv2IYJ59/xwphFuGaNR2RgtuJHwrsHGAOajGTCUy8o7

Processed: libiksemel: utterly insecure GNUTLS settings

[Debian Bug Tracking System]

Processing control commands:

> affects -1 = zabbix-server-pgsql zabbix-server-mysql
Bug #803204 [libiksemel] libiksemel: utterly insecure GNUTLS settings
Added indication that 803204 affects zabbix-server-pgsql and zabbix-server-mysql

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

Bug#803204: libiksemel: utterly insecure GNUTLS settings

[duck]

Package: libiksemel
Version: 1.4-2
Severity: grave
tags: security
Control: affects -1 = zabbix-server-pgsql zabbix-server-mysql


Coin,

Since I changed my XMPP server, Zabbix failed to send alerts via XMPP 
with "tls handshake failed". The XMPP server said "no shared cipher". 
After some research to see how Zabbix do its job I ended up into this 
library. I confirmed there is no way to setup the ciphers into Zabbix, 
but I was then astonished to see them hardcoded and very low grade in 
libiksemel:

   const int protocol_priority[] = { GNUTLS_TLS1, GNUTLS_SSL3, 0 };
   const int kx_priority[] = { GNUTLS_KX_RSA, 0 };
   const int cipher_priority[] = { GNUTLS_CIPHER_3DES_CBC, 
GNUTLS_CIPHER_ARCFOUR, 0};
   const int comp_priority[] = { GNUTLS_COMP_ZLIB, GNUTLS_COMP_NULL, 
0 };

   const int mac_priority[] = { GNUTLS_MAC_SHA, GNUTLS_MAC_MD5, 0 };

SSL3, 3DES, RC4, SSL compression… With this setting not only low grade 
ciphers are available, but higher grades are disabled. So this is a 
major security issue, also affecting stable.


The following patch fixes the security problem (and compatibility 
problem with servers rejecting low grade ciphers). You should 
nevertheless proofread my choices, as I'm no security expert. The patch 
does not change the original priority lists because I failed somehow to 
fix them all, so I replaced it by a priority string (which is a 
non-obsolete method to do it anyway).


Regards.

--
Marc DequènesIndex: libiksemel-1.4/src/stream.c
===
--- libiksemel-1.4.orig/src/stream.c
+++ libiksemel-1.4/src/stream.c
@@ -63,11 +63,7 @@ tls_pull (iksparser *prs, char *buffer,
 static int
 handshake (struct stream_data *data)
 {
-	const int protocol_priority[] = { GNUTLS_TLS1, GNUTLS_SSL3, 0 };
-	const int kx_priority[] = { GNUTLS_KX_RSA, 0 };
-	const int cipher_priority[] = { GNUTLS_CIPHER_3DES_CBC, GNUTLS_CIPHER_ARCFOUR, 0};
-	const int comp_priority[] = { GNUTLS_COMP_ZLIB, GNUTLS_COMP_NULL, 0 };
-	const int mac_priority[] = { GNUTLS_MAC_SHA, GNUTLS_MAC_MD5, 0 };
+	const char *priority_string = "SECURE256:+SECURE192:-VERS-TLS-ALL:+VERS-TLS1.2";
 	int ret;
 
 	if (gnutls_global_init () != 0)
@@ -80,11 +76,7 @@ handshake (struct stream_data *data)
 		gnutls_certificate_free_credentials (data->cred);
 		return IKS_NOMEM;
 	}
-	gnutls_protocol_set_priority (data->sess, protocol_priority);
-	gnutls_cipher_set_priority(data->sess, cipher_priority);
-	gnutls_compression_set_priority(data->sess, comp_priority);
-	gnutls_kx_set_priority(data->sess, kx_priority);
-	gnutls_mac_set_priority(data->sess, mac_priority);
+	gnutls_priority_set_direct(data->sess, priority_string, NULL);
 	gnutls_credentials_set (data->sess, GNUTLS_CRD_CERTIFICATE, data->cred);
 
 	gnutls_transport_set_push_function (data->sess, (gnutls_push_func) tls_push);

Processed: python-gunicorn: Merge duplicate bugs

[Debian Bug Tracking System]

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

> severity 803202 grave
Bug #803202 [python-gunicorn] python-gunicorn: post-inst fails to pycompile 
_gaiohttp.py
Severity set to 'grave' from 'important'
> merge 803170 803202
Bug #803170 [python-gunicorn] python-gunicorn: fails to upgrade with a syntax 
error
Bug #803202 [python-gunicorn] python-gunicorn: post-inst fails to pycompile 
_gaiohttp.py
Merged 803170 803202
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> tag 802113 pending
Bug #802113 [src:zope.i18n] zope.i18n: FTBFS: Tries to download zope.testing 
from pypy
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed (with 1 error): python-gunicorn: Merge duplicate bugs

[Debian Bug Tracking System]

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

> merge 803170 803202
Bug #803170 [python-gunicorn] python-gunicorn: fails to upgrade with a syntax 
error
Unable to merge bugs because:
severity of #803202 is 'important' not 'grave'
Failed to merge 803170: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#801900: axe-demultiplexer: /usr/bin/axe already used by the axe package

[Kevin Murray]

Hi Andreas,

On 17:56 27/10, Andreas Tille wrote:
> Hi Kevin,
> 
> do you have a plan to work on this?  I'd recommend to choose the name
> 
> /usr/bin/axe-demultiplexer
> 
> and provide
> 
> /usr/lib/debian-med/bin/axe
> 
> in addition and add
> 
> Recommends: med-config (>= 2.1)
> 
> to d/control.  This could be completed by and according hint in
> debian/README.Debian.  You might like to have a look into the packages
> inspect, libgenome-perl or plink as examples.  Feel free to ask for
> further advise.
> 

Sorry, I thought I responded to this already.

I'm fixing this upstream so that the binary name doesn't change; it will now be
`axe-demux` everywhere. I've re-released. I've decided to re-do the entire
packaging too, so that we don't bundle libqes or a cut-down gsl. I have a
couple of questions about this but I'll as those in a separate email.

Cheers,
Kevin

---
Kevin Murray

GPG pubkey: http://www.kdmurray.id.au/static/A4B4EE6A.asc
FPR: 656C 0632 1EAB 2C3F 3837  9767 17C2 8EB1 A4B4 EE6A

Bug#803178: libmongodb-perl: FTBFS on various architectures

[David Golden]

On Tue, Oct 27, 2015 at 4:53 PM, Niko Tyni  wrote:

> Adding some diagnostics indicates the actual data encoding is stable
> between the platforms, but the test suite expectations depend on the
> endianness. The attached patch seems to fix this on at least s390x,
> but perhaps we should have a test run with it before pushing it upstream.
>
>
I only had a chance to skim the output, but that was my assessment as
well.  I have no problem applying that patch, but a test to verify would be
appreciated (and would save us another round of automated failures).

Thank you for digging into it so quickly!

David

Bug#802945: marked as done (golang-go: Install fails with golang-golang-x-tools 1:0.0~git20150716.0.87156cb+dfsg1-4 installed)

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2015 21:29:05 +
with message-id 
and subject line Bug#802945: fixed in golang 2:1.5.1-2
has caused the Debian Bug report #802945,
regarding golang-go: Install fails with golang-golang-x-tools 
1:0.0~git20150716.0.87156cb+dfsg1-4 installed
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.)


-- 
802945: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802945
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: golang-go
Version: 2:1.5.1-1
Severity: grave

When I tried upgrading today, I got:

,
| Preconfiguring packages ...
| (Reading database ... 750549 files and directories currently installed.)
| Preparing to unpack .../golang-go_2%3a1.5.1-1_amd64.deb ...
| Unpacking golang-go (2:1.5.1-1) over (2:1.4.3-3) ...
| dpkg: error processing archive 
/var/cache/apt/archives/golang-go_2%3a1.5.1-1_amd64.deb (--unpack):
|  trying to overwrite '/usr/lib/go/pkg/tool/linux_amd64/vet', which is also in 
package golang-golang-x-tools 1:0.0~git20150716.0.87156cb+dfsg1-4
| dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
`

Since vet and cover are shipped with the main distribution now, they
should no longer be shipped with golang-golang-x-tools and golang-go
should conflict with versions of golang-golang-x-tools that still
contain them.

The attached patches should fix this.

Cheers,
-Hilko
>From 89eb32084e10c733439c947876a205e79279aaf3 Mon Sep 17 00:00:00 2001
From: Hilko Bengen 
Date: Sun, 25 Oct 2015 14:21:25 +0100
Subject: [PATCH] Add Conflicts for golang-golang-x-tools that still contain
 vet, cover

---
 debian/control | 1 +
 1 file changed, 1 insertion(+)

diff --git a/debian/control b/debian/control
index dd82625..36244d1 100644
--- a/debian/control
+++ b/debian/control
@@ -35,6 +35,7 @@ Replaces: golang-go-darwin-386,
   golang-go-netbsd-amd64,
   golang-go-windows-386,
   golang-go-windows-amd64
+Conflicts: golang-golang-x-tools (<< 1:0.0~git20150716.0.87156cb+dfsg1-5~)
 Recommends: g++, gcc, libc6-dev, pkg-config
 Suggests: bzr, ca-certificates, git, golang-golang-x-tools, mercurial, subversion
 Description: Go programming language compiler, linker, compiled stdlib
-- 
2.6.1

>From 1d7a492f00c7f9fe04e19b6917efd2158cb3b946 Mon Sep 17 00:00:00 2001
From: Hilko Bengen 
Date: Sun, 25 Oct 2015 14:17:54 +0100
Subject: [PATCH] Do not ship vet and cover binaries

---
 debian/rules | 4 
 1 file changed, 4 insertions(+)

diff --git a/debian/rules b/debian/rules
index b1c1840..091bd64 100755
--- a/debian/rules
+++ b/debian/rules
@@ -65,6 +65,10 @@ override_dh_auto_install:
 	ln -s /usr/share/javascript/jquery/jquery.min.js $(CURDIR)/debian/tmp/usr/share/gocode/src/golang.org/x/tools/godoc/static/jquery.js
 	-rm $(CURDIR)/debian/tmp/usr/share/gocode/src/golang.org/x/tools/cmd/present/static/jquery-ui.js && \
 	ln -s /usr/share/javascript/jquery-ui/jquery-ui.min.js $(CURDIR)/debian/tmp/usr/share/gocode/src/golang.org/x/tools/cmd/present/static/jquery-ui.js
+	# Don't ship vet and cover as they have been moved to the main
+	# repository.
+	-rm $(CURDIR)/debian/tmp//usr/lib/go/pkg/tool/*/cover
+	-rm $(CURDIR)/debian/tmp//usr/lib/go/pkg/tool/*/vet
 
 %:
 	dh $@ --buildsystem=golang --with=golang
-- 
2.6.1

--- End Message ---
--- Begin Message ---
Source: golang
Source-Version: 2:1.5.1-2

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

Debian distribution maintenance software
pp.
Tianon Gravi  (supplier of updated golang package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 27 Oct 2015 13:28:56 -0700
Source: golang
Binary: golang-go golang-src golang-doc golang
Architecture: source
Version: 2:1.5.1-2
Distribution: unstable
Urgency: medium
Maintainer: Go Compiler Team 
Changed-By: Tianon Gravi 
Description:
 golang - Go programming language compiler - metapackage
 golang-doc - Go programming language - documentation
 golang-go  - Go programming language compiler, linker, compiled stdlib
 golang-src - Go programming language - source files

Bug#801413: polarssl: CVE-2015-5291: Remote attack on clients using session tickets or SNI

[Moritz Mühlenhoff]

On Wed, Oct 21, 2015 at 01:43:26PM +0100, James Cowgill wrote:
> Hi,
> 
> On Tue, 2015-10-20 at 19:37 +0200, Florian Weimer wrote:
> > * James Cowgill:
> [...]
> > > One thing which was suggested was to use 1.3.14 and then disable at
> > > compile time all the new features which may affect the ABI and then
> > > revert the SONAME change, but is doing that actually allowed for the
> > > security archive or will the update be too big?
> > 
> > We can do that, but I don't know if it is a good idea to patch
> > cryptographic software in such extensive ways.
> > 
> > We can live with the addition of new symbols, but removal of symbols,
> > changes in struct sizes or offsets, and so on, would be hugely
> > problematic.  For are start, you could just build both the old and new
> > versions and run libabigail on them, to get an idea what actually did
> > change.
> 
> So I checked the ABI and had to revert a few commits. I've attached the
> original libabigail diff (all against upstream versions) and the diff
> after my patches. The variables don't look to me like they were ever
> intended to be part of the public ABI so I don't think they're that
> important.

Could you test that the reverse build deps in jessie still build?
If so, I'd be fine with that approach for jessie.

For wheezy we can probably only make it end-of-life? There's
only two reverse deps (pdns and gatling).

Cheers,
Moritz

Bug#803130: [pkg-go] Bug#803130: libdevel-cover-perl and golang-golang-x-tools: error when trying to install together

[Tianon Gravi]

On 27 October 2015 at 01:28, Ralf Treinen  wrote:
> 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/bin/cover

Doh -- I'll update golang-golang-x-tools to not build this binary
anymore since it's included in "golang-go" now.  Thanks for the
pointer!

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#802650: marked as done (miniupnpc: CVE-2015-6031: Buffer overflow vulnerability in XML parser functionality)

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2015 21:23:08 +
with message-id 
and subject line Bug#802650: fixed in miniupnpc 1.5-2+deb7u1
has caused the Debian Bug report #802650,
regarding miniupnpc: CVE-2015-6031: Buffer overflow vulnerability in XML parser 
functionality
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.)


-- 
802650: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802650
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: miniupnpc
Version: 1.5-2
Severity: grave
Tags: security patch upstream fixed-upstream
Justification: user security hole

Hi,

the following vulnerability was published for miniupnpc.

CVE-2015-6031[0]:
Buffer overflow vulnerability in XML parser functionality

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-6031
[1] 
https://github.com/miniupnp/miniupnp/commit/79cca974a4c2ab1199786732a67ff6d898051b78

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: miniupnpc
Source-Version: 1.5-2+deb7u1

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated miniupnpc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 25 Oct 2015 07:35:29 +0100
Source: miniupnpc
Binary: miniupnpc libminiupnpc5 libminiupnpc-dev
Architecture: source amd64
Version: 1.5-2+deb7u1
Distribution: wheezy-security
Urgency: high
Maintainer: Thomas Goirand 
Changed-By: Salvatore Bonaccorso 
Description: 
 libminiupnpc-dev - UPnP IGD client lightweight library development files
 libminiupnpc5 - UPnP IGD client lightweight library
 miniupnpc  - UPnP IGD client lightweight library client
Closes: 802650
Changes: 
 miniupnpc (1.5-2+deb7u1) wheezy-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * CVE-2015-6031: Buffer overflow vulnerability in XML parser functionality
 (Closes: #802650)
Checksums-Sha1: 
 6901fbb4fd914d756f75b8a6e5374a035755a0e2 1905 miniupnpc_1.5-2+deb7u1.dsc
 53ceae5515a547fed28b93bd5abba517586b0b3e 53309 miniupnpc_1.5.orig.tar.gz
 b8256818cdf1f1bbd2a13a453631b879fa0e95c1 3520 miniupnpc_1.5-2+deb7u1.diff.gz
 405c0d4a4365761a766ea9580f576fde1e66d939 14216 miniupnpc_1.5-2+deb7u1_amd64.deb
 3377cb5b10a70ef0b7de014cdd4981675a8aeba5 35140 
libminiupnpc5_1.5-2+deb7u1_amd64.deb
 4b71a78893ddf787b04ac24e09641924902708de 12014 
libminiupnpc-dev_1.5-2+deb7u1_amd64.deb
Checksums-Sha256: 
 6a977d6110a13670e09cf6ef19538ccfc1a07e4e8ad101372cc8a3de30f58367 1905 
miniupnpc_1.5-2+deb7u1.dsc
 440f0e64e92c92c6624f49d21cf8279b9c05afe99261e4add357b2ee2828a957 53309 
miniupnpc_1.5.orig.tar.gz
 e873c1133f45bead520cba0caa177e9b935363bf8980aea9e73413975c4a94f3 3520 
miniupnpc_1.5-2+deb7u1.diff.gz
 7a32f87df6b503da0a7132fa1faabeb020ef1d0f49ed6747bea3039e6890521c 14216 
miniupnpc_1.5-2+deb7u1_amd64.deb
 439729b5278eebc8f09a41ad6bdea4633f575fa8f52eaa35c64e01aaa97c64ea 35140 
libminiupnpc5_1.5-2+deb7u1_amd64.deb
 800415d2c93765bbbac3dfb4585d1bc9dc0f66f8bc5ca917b34d0093d15680a8 12014 
libminiupnpc-dev_1.5-2+deb7u1_amd64.deb
Files: 
 eec432c1f539b5a62756a25e04da227d 1905 net optional miniupnpc_1.5-2+deb7u1.dsc
 0efa7498d27c82a56a0300b0c05c4f58 53309 net optional miniupnpc_1.5.orig.tar.gz
 cc7a80528bb15e5485e10e30ebb322d8 3520 net optional 
miniupnpc_1.5-2+deb7u1.diff.gz
 dc0967a0db949a57d398811233666c0b 14216 net optional 
miniupnpc_1.5-2+deb7u1_amd64.deb
 211e5c79641e78c05535acb9bc25bde9 35140 net optional 
libminiupnpc5_1.5-2+deb7u1_amd64.deb
 8644a2e50f2ed83b013f0f2e9a92b1a3 12014 libdevel optional 
libminiupnpc-dev_1.5-2+deb7u1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJWLH9qAAoJEAVMuPMTQ89EG5AP/3ztHuFVgPjiZmvwnaT84ckm
Z4g+ARcVm31cIU0zHh9MfVaygE98jM6ZBS+Hpc50eQMdxG27n7GoBf1r5flxFQJ7
NJuMEQYwsol3lK7RAy/snP2Wjfz8F/75ij1Tgqquu/hSqOyV1ex4JBDz5W9YSf7G
rCNlt0J2mDUhCJy1JWE2lZXwRTkhpNNTnojudyAgbFeZHIs1Do9/

Processed: diff NMU for xenomai_2.6.4+dfsg-0.1

[Debian Bug Tracking System]

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

> tags 791980 +pending +patch
Bug #791980 [xenomai] New upstream available
Added tag(s) pending.
Bug #791980 [xenomai] New upstream available
Added tag(s) patch.
> tags 802420 +pending +patch
Bug #802420 [src:xenomai] xenomai: FTBFS: dh_compress: gzip: . is a directory 
-- ignored
Added tag(s) pending.
Bug #802420 [src:xenomai] xenomai: FTBFS: dh_compress: gzip: . is a directory 
-- ignored
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#802650: marked as done (miniupnpc: CVE-2015-6031: Buffer overflow vulnerability in XML parser functionality)

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2015 21:20:02 +
with message-id 
and subject line Bug#802650: fixed in miniupnpc 1.9.20140610-2+deb8u1
has caused the Debian Bug report #802650,
regarding miniupnpc: CVE-2015-6031: Buffer overflow vulnerability in XML parser 
functionality
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.)


-- 
802650: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802650
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: miniupnpc
Version: 1.5-2
Severity: grave
Tags: security patch upstream fixed-upstream
Justification: user security hole

Hi,

the following vulnerability was published for miniupnpc.

CVE-2015-6031[0]:
Buffer overflow vulnerability in XML parser functionality

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-6031
[1] 
https://github.com/miniupnp/miniupnp/commit/79cca974a4c2ab1199786732a67ff6d898051b78

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: miniupnpc
Source-Version: 1.9.20140610-2+deb8u1

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated miniupnpc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 25 Oct 2015 07:49:17 +0100
Source: miniupnpc
Binary: miniupnpc libminiupnpc10 libminiupnpc-dev python-miniupnpc
Architecture: source
Version: 1.9.20140610-2+deb8u1
Distribution: jessie-security
Urgency: high
Maintainer: Thomas Goirand 
Changed-By: Salvatore Bonaccorso 
Closes: 802650
Description: 
 libminiupnpc-dev - UPnP IGD client lightweight library development files
 libminiupnpc10 - UPnP IGD client lightweight library
 miniupnpc  - UPnP IGD client lightweight library client
 python-miniupnpc - UPnP IGD client lightweight library Python bindings
Changes:
 miniupnpc (1.9.20140610-2+deb8u1) jessie-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * Add CVE-2015-6031.patch patch.
 CVE-2015-6031: Buffer overflow vulnerability in XML parser
 functionality. (Closes: #802650)
Checksums-Sha1: 
 3eebe316498e3045120e1e365d777efff05ea6af 2121 
miniupnpc_1.9.20140610-2+deb8u1.dsc
 cd7f300d71019dfb915b79d1ea701d163d778c5b 76674 
miniupnpc_1.9.20140610.orig.tar.gz
 e11483de62f464cada2ec8b249d11143cccd0be1 6568 
miniupnpc_1.9.20140610-2+deb8u1.debian.tar.xz
Checksums-Sha256: 
 896d1185780778644f62c261e0ab78cefbbaa8ca1924de5c40c12da84e0bc3a8 2121 
miniupnpc_1.9.20140610-2+deb8u1.dsc
 31beffe44a5d7b7bbad3729cdd6f9f85844b9e5771aebb56550f87cbedcf5d3b 76674 
miniupnpc_1.9.20140610.orig.tar.gz
 f11579aafe66aacfeba7e3e3df386f49dbf14a29fe2b40fb165cf6d0325c5ed6 6568 
miniupnpc_1.9.20140610-2+deb8u1.debian.tar.xz
Files: 
 bd6b059e690592b52f16223614d38e37 2121 net optional 
miniupnpc_1.9.20140610-2+deb8u1.dsc
 6a812904b1a84766d03825341fc17365 76674 net optional 
miniupnpc_1.9.20140610.orig.tar.gz
 eced304501de6207082dff9df28253de 6568 net optional 
miniupnpc_1.9.20140610-2+deb8u1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJWLH1VAAoJEAVMuPMTQ89E5hQP+wVzCDMjUUY0LN+8x/u9b4AY
qGDMXHDLbGDF5w/YkUsqerHtZvzQ4lO4gHnU9Upxw1OphJiK0kkO0VkcD5aAKK2q
RddUqMaE9BFFYnvT+jbE+Rwus/m/PBpJ5fOKlrtRUT5y0QZ6dAn7p/zS6YVHIbG4
XoE4LTR/KBoSde9uktXVe0AZH3RiSMAwhybzZxrKNh83TMUSWx+hBszwCi1uJVLD
LL0OSVX61U3Ce8Ey1qIthIvsRbtDLWY9qtxJROyb8orS5GC8pitF/s2Urjlqpgmp
W8HsvVE0QxIspilxKhGh39KGA37GduYaaTO5WcyMgfmpn35JRrv+j+WqGj3xl0B4
++1z/otkSJGmTpR7eAZFlC6OyXwe1cSl9LNUDmo+SNhW0LTae1mVIcNyfcPgbwYp
awCfUcuQoA090n0J7yQY1eU8GlmGqRMqRYGKu3Ve6Qh1lvDJSEmWNHKmigk2U+qI
KEeEDk1Hsf+U1cQ8gp/EBQzEJS/zXkU8dQLEd5fKlod3Vn/gVt2yRWmvflqF5KuE
AJh8/aBafPQLLD53Br8+lj99lvJg3TCTlKm8zx18W/EOcNRTMBJEjI3iVPJP/Jce
ljK1Zc57+ZjqLd3YBsatbcTpO0pTJHpvxOeh/GC71RbbfeW9uWE3HS2PwuHJW/af
PJ+4JHGJIcDwZdjxq+Ml
=oM+O
-END PGP SIGNATURE End Message ---

Bug#802130: (no subject)

[Barry Warsaw]

https://github.com/malthe/chameleon/issues/206


pgpqR6mDavIMd.pgp
Description: OpenPGP digital signature

Processed: found 803130 in 1:0.0~git20151026.0.0f9d71c-1, found 803130 in 1.21-1

[Debian Bug Tracking System]

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

> found 803130 1:0.0~git20151026.0.0f9d71c-1
Bug #803130 [golang-golang-x-tools,libdevel-cover-perl] libdevel-cover-perl and 
golang-golang-x-tools: error when trying to install together
There is no source info for the package 'libdevel-cover-perl' at version 
'1:0.0~git20151026.0.0f9d71c-1' with architecture ''
Marked as found in versions golang-golang-x-tools/1:0.0~git20151026.0.0f9d71c-1.
> found 803130 1.21-1
Bug #803130 [golang-golang-x-tools,libdevel-cover-perl] libdevel-cover-perl and 
golang-golang-x-tools: error when trying to install together
There is no source info for the package 'golang-golang-x-tools' at version 
'1.21-1' with architecture ''
Marked as found in versions libdevel-cover-perl/1.21-1.
> thanks
Stopping processing here.

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

Bug#803178: libmongodb-perl: FTBFS on various architectures

[Niko Tyni]

On Tue, Oct 27, 2015 at 06:48:59PM +0100, gregor herrmann wrote:
> Package: libmongodb-perl
> Version: 1.0.2-1
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Yesterday's 1.0.2-1 upload failed to build on mips, powerpc, and
> s390x (plus hppa and ppc64):
> 
> https://buildd.debian.org/status/package.php?p=libmongodb-perl
> https://buildd.debian.org/status/logs.php?pkg=libmongodb-perl&ver=1.0.2-1
> 
> The failing tests seem to be the same on all architectures, and they
> are new in this release.

It's clearly an endianness issue. All the failing platforms are big
endian and this looks pretty clear:

#   Failed test 'encode_one( HASH )'
#   at t/bson_codec/containers.t line 201.
#  got: 
'\x{10}\x{00}\x{00}\x{00}\x{01}a\x{00}\x{ae}G\x{e1}z\x{14}\x{ae}\x{f3}?\x{00}'
# expected: 
'\x{10}\x{00}\x{00}\x{00}\x{01}a\x{00}?\x{f3}\x{ae}\x{14}z\x{e1}G\x{ae}\x{00}'

Adding some diagnostics indicates the actual data encoding is stable
between the platforms, but the test suite expectations depend on the
endianness. The attached patch seems to fix this on at least s390x,
but perhaps we should have a test run with it before pushing it upstream.
-- 
Niko Tyni   nt...@debian.org
>From 6469bf8eb321686c3b38a15b9a8a311a838568cb Mon Sep 17 00:00:00 2001
From: Niko Tyni 
Date: Tue, 27 Oct 2015 20:49:00 +
Subject: [PATCH] Expect BSON encoded doubles in little endian order

This fixes bson_codec test failures on big endian platforms.

Bug-Debian: https://bugs.debian.org/803178
---
 t/lib/TestBSON.pm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/t/lib/TestBSON.pm b/t/lib/TestBSON.pm
index e400586..b0f5b04 100644
--- a/t/lib/TestBSON.pm
+++ b/t/lib/TestBSON.pm
@@ -82,7 +82,7 @@ sub _doc {
 sub _cstring { return $_[0] . "\x00" }
 BEGIN { *_ename = \&_cstring }
 
-sub _double { return pack( "d", shift ) }
+sub _double { return pack( PERL58 ? "d" : "d<", shift ) }
 
 sub _int32 { return pack( P_INT32, shift ) }
 
-- 
2.1.4

Bug#802811: libqt5x11extras5: causes konsole to segfault in libX11 on startup

[Raphael Geissert]

Hi Lisandro!

On Tue, 27 Oct 2015 15:30:42 -0300 Lisandro Damián Nicanor Pérez Meyer
 wrote:
> Hi everyone! We possibly have two issues here.
>
> The first one is the reported one, which should be fixed.
>
> Now the second one might most probably be because qtx11extras migrated to
> testing when it shouldn't have. This is the first time it happens for us.

Doesn't that sound like there's a missing dependency, somewhere?
It sounds like a person using a testing-unstable mix would also be affected.


/me who also got hit by it
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net

Bug#787371: wpa: CVE-2015-4143 CVE-2015-4144 CVE-2015-4145 CVE-2015-4146: EAP-pwd missing payload length validation

[Salvatore Bonaccorso]

Hi Julian,

On Mon, Oct 26, 2015 at 02:30:39PM +0100, Julian Wollrath wrote:
> Hi Salvatore,
> 
> Am Sun, 25 Oct 2015 16:14:56 +0100
> schrieb Salvatore Bonaccorso :
> 
> > Hi Julian,
> > 
> > On Sat, Oct 24, 2015 at 05:04:56PM +0200, Julian Wollrath wrote:
> > > +wpa (2.3-1+deb8u2) jessie-security; urgency=high
> > > +
> > > +  * Add fixes for http://w1.fi/security/2015-5/
> > > +  * Add fixes for CVE-2015-4141, CVE-2015-4142, CVE-2015-4143,
> > > CVE-2015-4144,
> > > +CVE-2015-4145, CVE-2015-4146 (Closes: #787371).  
> > 
> > Only looked from a changelog point of view: Please close as well the
> > other releated bugs in the changelog entries:
> > 
> > fixes for http://w1.fi/security/2015-5/ -> #795740
> > CVE-2015-4141 -> #787372
> > CVE-2015-4142 -> #787373
> > CVE-2015-4143 -> #787371
> > CVE-2015-4144 -> #787371
> > CVE-2015-4145 -> #787371
> > CVE-2015-4146 -> #787371
> > 
> > (you can find the information via the security-tracker, i.e.
> > https://security-tracker.debian.org/wpa)
> > 
> > The reason i filled different bug reports is that different version
> > ranges are affected, so that we have proper version tracking as well
> > for the BTS.
> ok. I can change that. Not sure though, if I have time for it today.
> 
> > 
> > Thanks for having worked on that update and attached your patchset.
> > Hav you worked as well on wheezy?
> No I have not and I am unsure, if I have time do look at it before the
> weekend.

I will tentatively look into it soon in the next few days as well.

Regards,
Salvatore

Bug#802145: Attached debdiff for NMU - please commit to packaging Git

[Barry Warsaw]

On Oct 26, 2015, at 11:04 AM, Andreas Tille wrote:

>I took the freedom to fix the minor bug in addition to the serious
>one.  Please add the debdiff to your packaging git.

Done, and thanks!

Bug#802380: epiphany-browser: System crashes when visiting reuters.com URL (GPU crash?)

[Michael Biebl]

Control: reassign -1 libwebkit2gtk-4.0-37
Control: found -1 2.10.0+dfsg1-1

Am 19.10.2015 um 21:45 schrieb David Glover-Aoki:
> Package: epiphany-browser
> Version: 3.18.0-1
> Severity: critical
> Justification: breaks the whole system
> 
> Dear Maintainer,
> 
> When visiting the following URL in Epiphany/Web:
> http://www.reuters.com/article/2015/10/18/us-new-york-flightcenter-
> idUSKCN0SC14B20151018
> 
> The entire screen turns black, then red, then finally is covered in garbage
> random red pixels. It looks very much like a GPU crash. At this point the
> system is hung and must be rebooted.
> 
> My GPU is an Nvidia GTX 770, I'm using the nouveau driver, version 
> 1.0.11-1+b1.
> 
> Errors from syslog are attached.

...

> 
> Versions of packages epiphany-browser depends on:

> ii  libwebkit2gtk-4.0-37 2.10.0+dfsg1-1

I don't think this is a epiphany bug, but a bug in WebKit, X or the
kernel graphics driver.
Re-assigning to WebKit for now
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#802380: epiphany-browser: System crashes when visiting reuters.com URL (GPU crash?)

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libwebkit2gtk-4.0-37
Bug #802380 [epiphany-browser] epiphany-browser: System crashes when visiting 
reuters.com URL (GPU crash?)
Bug reassigned from package 'epiphany-browser' to 'libwebkit2gtk-4.0-37'.
No longer marked as found in versions epiphany-browser/3.18.0-1.
Ignoring request to alter fixed versions of bug #802380 to the same values 
previously set
> found -1 2.10.0+dfsg1-1
Bug #802380 [libwebkit2gtk-4.0-37] epiphany-browser: System crashes when 
visiting reuters.com URL (GPU crash?)
Marked as found in versions webkit2gtk/2.10.0+dfsg1-1.

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

Bug#802145: marked as pending

[Barry Warsaw]

tag 802145 pending
thanks

Hello,

Bug #802145 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-cachecontrol.git;a=commitdiff;h=8b1eec6

---
commit 8b1eec6402bfe18f0c92f5d094a1ea467917c205
Author: Barry Warsaw 
Date:   Tue Oct 27 16:20:02 2015 -0400

* Non-maintainer upload.
* Add python-requests to Build-Depends. (Closes: #802145)
* Removed some underscores from long description. (Closes: #799531)

diff --git a/debian/changelog b/debian/changelog
index 992ae56..59819cf 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+python-cachecontrol (0.11.5-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add python-requests to Build-Depends. (Closes: #802145)
+  * Removed some underscores from long description. (Closes: #799531)
+
+ -- Andreas Tille   Mon, 26 Oct 2015 10:51:48 +0100
+
 python-cachecontrol (0.11.5-1) unstable; urgency=medium
 
   * New upstream release.

Processed: Bug#802145 marked as pending

[Debian Bug Tracking System]

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

> tag 802145 pending
Bug #802145 {Done: Andreas Tille } [src:python-cachecontrol] 
python-cachecontrol: FTBFS: ImportError: No module named 'requests'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#803191: jeepyb FTBFS: A newer version of python-pbr has been packaged

[Hans Joachim Desserud]

Package: jeepyb
Version: 0+20150929-1
Severity: serious
Justification: fails to build from source

Dear Maintainer,

It is currently not possible to build jeepyb because the
build dependencies fail to install with the following error:

# apt-get build-dep jeepyb
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Failed to satisfy Build-Depends dependency for jeepyb: Installed 
package python-pbr is too new


This is likely because jeepyb list the following version
restrictions for python-pbr:
   python-pbr (<<1.0),
   python-pbr (>=0.6),
which fails now that python-pbr 1.8.0-4 has been packaged.


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

Kernel: Linux 4.2.0-1-amd64 (SMP w/1 CPU core)
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 jeepyb depends on:
ii  libpython2.7-stdlib [python-argparse]  2.7.10-5
ii  python 2.7.9-1
ii  python-gerritlib   0.4.0+git20150319-1
ii  python-mysqldb 1.3.4-2.1
ii  python-paramiko1.15.3-1
ii  python-pbr 1.8.0-4
ii  python-pkginfo 1.1-2
ii  python-pygithub1.25.2-4
ii  python-pyrss2gen   1.1-1
ii  python-requests2.7.0-3
ii  python-six 1.10.0-1
ii  python-swiftclient 1:2.6.0-3
ii  python-yaml3.11-2+b1
pn  python:any 

jeepyb recommends no packages.

jeepyb suggests no packages.

-- no debconf information


--
mvh / best regards
Hans Joachim Desserud
http://desserud.org

Bug#798601: Reproduction of #798601: qemu

[Roelof Berg]

Based on https://people.debian.org/~aurel32/qemu/mips/

wget 
https://people.debian.org/~aurel32/qemu/mips/debian_wheezy_mips_standard.qcow2

wget https://people.debian.org/~aurel32/qemu/mips/vmlinux-3.2.0-4-4kc-malta
qemu-system-mips -M malta -kernel vmlinux-3.2.0-4-4kc-malta -hda 
debian_wheezy_mips_standard.qcow2 -append "root=/dev/sda1 console=tty0"


Thanks Aurel32

On 26.10.2015 21:47, Roelof Berg wrote:

I wonder what might be the best way, to test my fix for MIPS.

Bug#802380: epiphany-browser: System crashes when visiting reuters.com URL (GPU crash?)

[Sven Arvidsson]

On Mon, 2015-10-19 at 12:45 -0700, David Glover-Aoki wrote:
> When visiting the following URL in Epiphany/Web:
> http://www.reuters.com/article/2015/10/18/us-new-york-flightcenter-
> idUSKCN0SC14B20151018
> 
> The entire screen turns black, then red, then finally is covered in
> garbage
> random red pixels. It looks very much like a GPU crash. At this point
> the
> system is hung and must be rebooted.
> 
> My GPU is an Nvidia GTX 770, I'm using the nouveau driver, version
> 1.0.11-1+b1.
> 
> Errors from syslog are attached.
> 
> The URL loads fine in Iceweasel, and other URLs load fine in
> Epiphany.

I filed an upstream bug about a very similar problem:
https://bugzilla.gnome.org/show_bug.cgi?id=757213

My symptoms are different from yours (different GPU) but both sites
misbehave the same with Epiphany. 

-- 
Cheers,
Sven Arvidsson
http://www.whiz.se
PGP Key ID 6FAB5CD5





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

Bug#802867: marked as done (python-biom-format: FTBFS: _filter.pyx: Incompatible types in conditional expression ((Py_ssize_t, Py_ssize_t); (long, long)))

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2015 19:25:50 +
with message-id 
and subject line Bug#802867: fixed in python-biom-format 2.1.4+dfsg-1
has caused the Debian Bug report #802867,
regarding python-biom-format: FTBFS: _filter.pyx: Incompatible types in 
conditional expression ((Py_ssize_t, Py_ssize_t); (long, long))
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.)


-- 
802867: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802867
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-biom-format
Version: 2.1+dfsg-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:

running config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/python-biom-format-2.1+dfsg'
USE_CYTHON=true dh_auto_build
I: pybuild base:170: /usr/bin/python setup.py build 

Error compiling Cython file:

...
offset += end - start
offset_rows += 1
arr.data = data[:nnz]
arr.indices = indices[:nnz]
arr.indptr = indptr[:m-offset_rows+1]
arr._shape = (m - offset_rows, n) if m-offset_rows else (0, 0)
^


biom/_filter.pyx:87:17: Incompatible types in conditional expression 
((Py_ssize_t, Py_ssize_t); (long, long))
Compiling biom/_filter.pyx because it changed.
Compiling biom/_transform.pyx because it changed.
Compiling biom/_subsample.pyx because it changed.
[1/3] Cythonizing biom/_filter.pyx
Traceback (most recent call last):
  File "setup.py", line 80, in 
extensions = cythonize(extensions)
  File "/usr/lib/python2.7/dist-packages/Cython/Build/Dependencies.py", line 
877, in cythonize
cythonize_one(*args)
  File "/usr/lib/python2.7/dist-packages/Cython/Build/Dependencies.py", line 
997, in cythonize_one
raise CompileError(None, pyx_file)
Cython.Compiler.Errors.CompileError: biom/_filter.pyx
E: pybuild pybuild:262: build: plugin distutils failed with: exit code=1: 
/usr/bin/python setup.py build 
dh_auto_build: pybuild --build -i python{version} -p 2.7 --dir . returned exit 
code 13
debian/rules:23: recipe for target 'override_dh_auto_build' failed

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/python-biom-format.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: python-biom-format
Source-Version: 2.1.4+dfsg-1

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated python-biom-format 
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, 27 Oct 2015 18:46:33 +0100
Source: python-biom-format
Binary: python-biom-format
Architecture: source amd64
Version: 2.1.4+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 python-biom-format - Biological Observation Matrix (BIOM) format
Closes: 802867
Changes:
 python-biom-format (2.1.4+dfsg-1) unstable; urgency=medium
 .
   * New upstream version
 Closes: #802867
   * Moved from SVN to Git
   * cme fix dpkg-control
   * Fix watch file
Checksums-Sha1:
 4e1b860422e37f89868b8e9f1497bb7d9ab103c9 2247 
python-biom-format_2.1.4+dfsg-1.dsc
 692860e540e5496ea5696a85bde8cdc2ed9bdde1 8513052 
python-biom-format_2.1.4+dfsg.orig.tar.xz
 ed56ee62acf1363d773a7532c9bc16a61c4c4eff 7136 
python-biom-format_2.1.4+dfsg-1.debian.tar.xz
 ffc1a59568284e70b40e1cff020dd34bfaf1c7ef 206628 
python-biom-format_2.1.4+dfsg-1_amd64.deb
Checksums-Sha256:
 e22e0cac4f68bcd271368783d15906e15fff1c517105febc02e843048ed8d4b6 2247 
python-biom-format_2.1.4+dfsg-1.dsc
 866fa7379367624c184a4274c62844bc539075dd86ea987e468d65eb4791

Bug#800407: marked as done (woo: FTBFS with python3.5 due to test failures)

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2015 19:26:03 +
with message-id 
and subject line Bug#800407: fixed in woo 1.0+dfsg1-1
has caused the Debian Bug report #800407,
regarding woo: FTBFS with python3.5 due to test failures
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.)


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

Here is an excerpt from the build log from the binNMU to add python3.5
support:

pybuild --test -i python{version} -p "3.5 3.4" --dir .
I: pybuild base:170: cd /«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build; python3.5 
-m unittest discover -v 
woo (unittest.loader._FailedTest) ... ERROR

==
ERROR: woo (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: woo
Traceback (most recent call last):
  File "/usr/lib/python3.5/unittest/loader.py", line 462, in _find_test_path
package = self._get_module_from_name(name)
  File "/usr/lib/python3.5/unittest/loader.py", line 369, in 
_get_module_from_name
__import__(name)
  File "/«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build/woo/__init__.py", line 125, 
in 
import minieigen
ImportError: No module named 'minieigen'


--
Ran 1 test in 0.000s

FAILED (errors=1)
E: pybuild pybuild:262: test: plugin distutils failed with: exit code=1: cd 
/«PKGBUILDDIR»/.pybuild/pythonX.Y_3.5/build; python3.5 -m unittest discover -v 
dh_auto_test: pybuild --test -i python{version} -p 3.5 3.4 --dir . returned 
exit code 13
make: *** [build-arch] Error 25
debian/rules:7: recipe for target 'build-arch' failed
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

Build finished at 20150928-2128

Scott K
--- End Message ---
--- Begin Message ---
Source: woo
Source-Version: 1.0+dfsg1-1

We believe that the bug you reported is fixed in the latest version of
woo, 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.
Anton Gladky  (supplier of updated woo 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: SHA1

Format: 1.8
Date: Tue, 27 Oct 2015 19:59:36 +0100
Source: woo
Binary: python-woo python3-woo
Architecture: source
Version: 1.0+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Anton Gladky 
Description:
 python-woo - Discrete dynamic computations, esp. granular mechanics (python 2)
 python3-woo - Discrete dynamic compuations, esp. granular mechanics (python 3)
Closes: 800407
Changes:
 woo (1.0+dfsg1-1) unstable; urgency=medium
 .
   * [ae1639e] Move to vtk6, add BD for python3.
   * [1e74080] Disable autotests temporarly. (Closes: #800407)
   * [6a9fe9e] Add MathJax_local.js to Files-Excluded.
   * [8ee1c9d] Imported Upstream version 1.0+dfsg1
   * [02150d7] Fix warnings in d/copyright.
Checksums-Sha1:
 f9b0727aaf283c10fe24c275ebb34aa2df7ccb05 2291 woo_1.0+dfsg1-1.dsc
 f10305065817979cdbb437ba43ede61db5151949 15684656 woo_1.0+dfsg1.orig.tar.xz
 29c09080ad060a4491aca3713ec889fdbf69ebd4 10168 woo_1.0+dfsg1-1.debian.tar.xz
Checksums-Sha256:
 d0fe81650507aea4a86febf319ea0590e9e3322c8dd20a42706da79abfe280c6 2291 
woo_1.0+dfsg1-1.dsc
 cf4d363e6497865795b490fe117c2975fe829cfdaba0183e34217666af6ea5df 15684656 
woo_1.0+dfsg1.orig.tar.xz
 0a41a3646c51a3f4c7a8a73ed8f3e84cd7aca7a8b7012986aa494e7fa60d7d91 10168 
woo_1.0+dfsg1-1.debian.tar.xz
Files:
 e396acb3e223faf9ab429198c8a2ddf3 2291 python optional woo_1.0+dfsg1-1.dsc
 c03cabffeb951c88c318d4be2a7ad68b 15684656 python optional 
woo_1.0+dfsg1.orig.tar.xz
 4fa97ec570217757165de463bebca35a 10168 python optional 
woo_1.0+dfsg1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJWL8n8AAoJENPhc4PPp/8GviIP+wdbeiVM

Bug#802171: marked as done (comet-ms: build-depends on libmstoolkit-dev (= 77.0.0-1) which doesn't exist)

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2015 19:19:05 +
with message-id 
and subject line Bug#802171: fixed in comet-ms 2014022-3
has caused the Debian Bug report #802171,
regarding comet-ms: build-depends on libmstoolkit-dev (= 77.0.0-1) which 
doesn't exist
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.)


-- 
802171: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802171
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: comet-ms
Version: 2014022-2
Severity: serious

Your package build-depends on libmstoolkit-dev (= 77.0.0-1). That's too strict
and since that package no longer exists at that version, your package cannot be
built.

Emilio
--- End Message ---
--- Begin Message ---
Source: comet-ms
Source-Version: 2014022-3

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

Debian distribution maintenance software
pp.
Filippo Rusconi  (supplier of updated comet-ms 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, 26 Oct 2015 20:59:18 +0100
Source: comet-ms
Binary: comet-ms comet-ms-dbg
Architecture: source amd64
Version: 2014022-3
Distribution: unstable
Urgency: medium
Maintainer: The Debichem Group 
Changed-By: Filippo Rusconi 
Description:
 comet-ms   - Tandem mass spectrometry (MS/MS) search engine
 comet-ms-dbg - Tandem mass spectrometry (MS/MS) search engine - debug symbols
Closes: 802171
Changes:
 comet-ms (2014022-3) unstable; urgency=medium
 .
   * Modify the version rule of the libmstoolkit-dev Build-Depends to be
 more flexible (Closes: #802171).
Checksums-Sha1:
 dcade01a338c12152359d5ecdba215c0954a 2107 comet-ms_2014022-3.dsc
 3d3f39802b1f4a19063f0f0f85bac284cdf8e9d7 11064 comet-ms_2014022-3.debian.tar.xz
 0e3f4dbc8e00795b9249ace3fb9e85afa7595958 728952 
comet-ms-dbg_2014022-3_amd64.deb
 8d50c23d4d2422f8646013fb46bd28605bbe02c1 96668 comet-ms_2014022-3_amd64.deb
Checksums-Sha256:
 42b6ad612b5a54b7fc5115f4b544ffee066293929403b7de727bc64f01aed93b 2107 
comet-ms_2014022-3.dsc
 ce764a9394384ea4b037e572c25f3ef964147f90aa9df7c99c625b225a968777 11064 
comet-ms_2014022-3.debian.tar.xz
 1ed4f7467575db3d5f29dfd1935ab90bedf53f0105c5a3c320dbb31ea1ae256c 728952 
comet-ms-dbg_2014022-3_amd64.deb
 e1be0f6f0c07f7997e08bda46c8ce0ab7d50d56cb18a6b02c03990e5559742cd 96668 
comet-ms_2014022-3_amd64.deb
Files:
 8e32efc869c49eb41ff88cd35ff1fafe 2107 science optional comet-ms_2014022-3.dsc
 559a916f9a9944b980dbbea555d6952d 11064 science optional 
comet-ms_2014022-3.debian.tar.xz
 de9a27bf2f7375a9c0f87fc0beb508a9 728952 debug extra 
comet-ms-dbg_2014022-3_amd64.deb
 ef70d0b7ac8a46c7d869fbe9dd28d00b 96668 science optional 
comet-ms_2014022-3_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWL8o6AAoJEEGrSE12lM9Cbk0P/1vcvejkKqzCnEUug09kVij9
+pcHlxh7niEP2mkF2KTpY//oVmQ8x5d9h0rpAhPfhRF7Wc8QZiXz3M3OhHG+Remq
K18HN6ivYj2Ngd/ZEy79618i8/QormaV8+yCDLWtHBMHzyK/KC8x7/jDtUwdXAVI
1BFaRZz99ZNA4frZ7SroZrMXroWQFSB7f36wpAWzSRrvush80v1qIHkI9EUgjJHr
JPd0aNf7Iqx3zlByKCrQdOzuneMDO3EyYmfBidhp+1nIxMFojnP8lKqE1+IXmVrG
DbB52zMVwDsIqg3LMBd/+Ipf842YlGwbcxnSyrlUywEoltFWen/iYsx5LkDzLbE3
64ycXdT7osO/6IO7RaGna2nniKw7EuLXV1T7vCsSENHd62WhJvDPLgZaLUoP96tu
3y0vnxqYDvoubJxIVA+6wNAYY0CXSqZgTZRI3orxzYsTeh4duNxNiEEusWz0LeK1
O7b2/VdeYn18scAWHROAQBKjpe32CtazKpS9qB7kIZR/JTt4AfB7mHogMIHRtych
d7BlACxZBTf5Z+eUnj96XbTAkFExVp2K9cWFCV7hxkiMv5CDgwEaH7OJL1znBdLR
YpBbbo9ebqAGV2QnHFgCYeEN5Mi1DObbQz7G5sdWPUiCXpPO+I0nto0T63FLkNYJ
f2vhcIv5PEwgePdg7H1s
=BK1s
-END PGP SIGNATURE End Message ---

Bug#780162: shouldn't the bug be tackled at upstream - i.e. smartmontools upstream ?

[shirish शिरीष]

Hi all,

@ Chris - could you share the relevant bug number where you posted the
scripts/patch upstream ?

>From the initial bug you reported

" (The scripts have been posted upstream without response, but it is still
a distro resposibility to ensure that insta(The scripts have been
posted upstream without response, but it is still
a distro resposibility to ensure that installations will have safe
defaults. Note that the provided udev rules specific to mdadm are only
to be included in the mdadm package.)

This is at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780162#5

Look forward to having that but number so maybe we could also apply
some pressure there as well.

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Bug#802069: marked as done (comet-ms: overly strict B-D: libmstoolkit-dev (= 77.0.0-1))

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2015 19:19:05 +
with message-id 
and subject line Bug#802171: fixed in comet-ms 2014022-3
has caused the Debian Bug report #802171,
regarding comet-ms: overly strict B-D: libmstoolkit-dev (= 77.0.0-1)
to be marked as done.

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

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


-- 
802171: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802171
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: comet-ms
Version: 77.0.0-1
Severity: serious
Justification: fails to build from source

comet-ms has an overly strict Build-depends on
libmstoolkit-dev (= 77.0.0-1) which is no longer satisfiable after
libmstoolkit got binNMUed (it is now at version 77.0.0-1+b1).


Andreas
--- End Message ---
--- Begin Message ---
Source: comet-ms
Source-Version: 2014022-3

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

Debian distribution maintenance software
pp.
Filippo Rusconi  (supplier of updated comet-ms 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, 26 Oct 2015 20:59:18 +0100
Source: comet-ms
Binary: comet-ms comet-ms-dbg
Architecture: source amd64
Version: 2014022-3
Distribution: unstable
Urgency: medium
Maintainer: The Debichem Group 
Changed-By: Filippo Rusconi 
Description:
 comet-ms   - Tandem mass spectrometry (MS/MS) search engine
 comet-ms-dbg - Tandem mass spectrometry (MS/MS) search engine - debug symbols
Closes: 802171
Changes:
 comet-ms (2014022-3) unstable; urgency=medium
 .
   * Modify the version rule of the libmstoolkit-dev Build-Depends to be
 more flexible (Closes: #802171).
Checksums-Sha1:
 dcade01a338c12152359d5ecdba215c0954a 2107 comet-ms_2014022-3.dsc
 3d3f39802b1f4a19063f0f0f85bac284cdf8e9d7 11064 comet-ms_2014022-3.debian.tar.xz
 0e3f4dbc8e00795b9249ace3fb9e85afa7595958 728952 
comet-ms-dbg_2014022-3_amd64.deb
 8d50c23d4d2422f8646013fb46bd28605bbe02c1 96668 comet-ms_2014022-3_amd64.deb
Checksums-Sha256:
 42b6ad612b5a54b7fc5115f4b544ffee066293929403b7de727bc64f01aed93b 2107 
comet-ms_2014022-3.dsc
 ce764a9394384ea4b037e572c25f3ef964147f90aa9df7c99c625b225a968777 11064 
comet-ms_2014022-3.debian.tar.xz
 1ed4f7467575db3d5f29dfd1935ab90bedf53f0105c5a3c320dbb31ea1ae256c 728952 
comet-ms-dbg_2014022-3_amd64.deb
 e1be0f6f0c07f7997e08bda46c8ce0ab7d50d56cb18a6b02c03990e5559742cd 96668 
comet-ms_2014022-3_amd64.deb
Files:
 8e32efc869c49eb41ff88cd35ff1fafe 2107 science optional comet-ms_2014022-3.dsc
 559a916f9a9944b980dbbea555d6952d 11064 science optional 
comet-ms_2014022-3.debian.tar.xz
 de9a27bf2f7375a9c0f87fc0beb508a9 728952 debug extra 
comet-ms-dbg_2014022-3_amd64.deb
 ef70d0b7ac8a46c7d869fbe9dd28d00b 96668 science optional 
comet-ms_2014022-3_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWL8o6AAoJEEGrSE12lM9Cbk0P/1vcvejkKqzCnEUug09kVij9
+pcHlxh7niEP2mkF2KTpY//oVmQ8x5d9h0rpAhPfhRF7Wc8QZiXz3M3OhHG+Remq
K18HN6ivYj2Ngd/ZEy79618i8/QormaV8+yCDLWtHBMHzyK/KC8x7/jDtUwdXAVI
1BFaRZz99ZNA4frZ7SroZrMXroWQFSB7f36wpAWzSRrvush80v1qIHkI9EUgjJHr
JPd0aNf7Iqx3zlByKCrQdOzuneMDO3EyYmfBidhp+1nIxMFojnP8lKqE1+IXmVrG
DbB52zMVwDsIqg3LMBd/+Ipf842YlGwbcxnSyrlUywEoltFWen/iYsx5LkDzLbE3
64ycXdT7osO/6IO7RaGna2nniKw7EuLXV1T7vCsSENHd62WhJvDPLgZaLUoP96tu
3y0vnxqYDvoubJxIVA+6wNAYY0CXSqZgTZRI3orxzYsTeh4duNxNiEEusWz0LeK1
O7b2/VdeYn18scAWHROAQBKjpe32CtazKpS9qB7kIZR/JTt4AfB7mHogMIHRtych
d7BlACxZBTf5Z+eUnj96XbTAkFExVp2K9cWFCV7hxkiMv5CDgwEaH7OJL1znBdLR
YpBbbo9ebqAGV2QnHFgCYeEN5Mi1DObbQz7G5sdWPUiCXpPO+I0nto0T63FLkNYJ
f2vhcIv5PEwgePdg7H1s
=BK1s
-END PGP SIGNATURE End Message ---

Bug#802415: marked as done (zope.schema: FTBFS: Missing build-dep on zope.interface(?))

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2015 19:07:58 +
with message-id 
and subject line Bug#802415: fixed in zope.schema 4.4.2-3
has caused the Debian Bug report #802415,
regarding zope.schema: FTBFS: Missing build-dep on zope.interface(?)
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.)


-- 
802415: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802415
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zope.schema
Version: 4.4.2-2
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 without networking.  It's against Policy to
download stuff from PyPy during the build, so this needs to be in a
build-dep:

test_w_non_fields (zope.schema.tests.test_interfaces.Test__fields) ... ok

--
Ran 412 tests in 0.084s

OK
I: pybuild base:170: python3.5 setup.py test 
running test
Searching for zope.interface>=3.6.0
Reading https://pypi.python.org/simple/zope.interface/
Download error on https://pypi.python.org/simple/zope.interface/: [Errno 111] 
Connection refused -- Some packages may not be found!
Couldn't find index page for 'zope.interface' (maybe misspelled?)
Scanning index of all packages (this may take a while)
Reading https://pypi.python.org/simple/
Download error on https://pypi.python.org/simple/: [Errno 111] Connection 
refused -- Some packages may not be found!
No local packages or download links found for zope.interface>=3.6.0
error: Could not find suitable distribution for 
Requirement.parse('zope.interface>=3.6.0')
E: pybuild pybuild:262: test: plugin distutils failed with: exit code=1: 
python3.5 setup.py test 

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

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: zope.schema
Source-Version: 4.4.2-3

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

Debian distribution maintenance software
pp.
Barry Warsaw  (supplier of updated zope.schema 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, 27 Oct 2015 12:53:11 -0400
Source: zope.schema
Binary: python-zope.schema python3-zope.schema
Architecture: source all
Version: 4.4.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian/Ubuntu Zope Team 

Changed-By: Barry Warsaw 
Description:
 python-zope.schema - zope.interface extension for defining data schemas
 python3-zope.schema - zope.interface extension for defining data schemas
Closes: 802415
Changes:
 zope.schema (4.4.2-3) unstable; urgency=medium
 .
   * d/control: Add missing build dependency on python{,3}-zope.interface.
 (Closes: #802415)
   * d/patches/setup-test-require.patch: Added to work around a bug in
 dh_python3.
   * d/tests/control, d/tests/all: Rewrite to use simple Test-Commands and
 remove the 'all' script.
Checksums-Sha1:
 054ec2c4912c0fcaf4af70b46ee18f13b0c270f5 2329 zope.schema_4.4.2-3.dsc
 97a19f14d77e055e97c25619b137502d3521139c 4460 zope.schema_4.4.2-3.debian.tar.xz
 1c0cbf7a4cec97c99e4be8ab555d09da2f4e0e2b 48412 
python-zope.schema_4.4.2-3_all.deb
 710f8b85cffb16097957de03aae592da8a49b50a 48444 
python3-zope.schema_4.4.2-3_all.deb
Checksums-Sha256:
 82435e199c89a47c30fe1e4a1774c4187763ee8121432d0e384e5e9514b01cbb 2329 
zope.schema_4.4.2-3.dsc
 b5ffa7f53489d2c3130b3d1479b20c2d86c857a5a84f6fd28c36d3d5b50f8531 4460 
zope.schema_4.4.2-3.debian.tar.xz
 fd8f458d4de224d3917ab0fe74f99d74648e0d9402b4d4d39518ea15b04501ed 48412 
python-zope.schema_4.4.2-3_all.deb
 fb5cc6e94edc0c718dbfb8534e0a496388940e999ac956717459fb6f1a85faf9 48444 
python3-zope.schema_4.4.2-3_all.deb
Files:
 d7bcbd1e627689f90af5a1d30ae0a577 2329 zope extra zope.schema_4.4.2-3.dsc
 bdee3d1cbfe6297f950d662cc3f82e6c 4460 zope extra 
z

Bug#802811: libqt5x11extras5: causes konsole to segfault in libX11 on startup

[Lisandro Damián Nicanor Pérez Meyer]

Hi everyone! We possibly have two issues here.

The first one is the reported one, which should be fixed.

Now the second one might most probably be because qtx11extras migrated to 
testing when it shouldn't have. This is the first time it happens for us.

The workaround is to either downgrade it from snapshots.debian.org or update 
qt from unstable.

Kinds regards, Lisandro.


-- 
I must confess, I was born at a very early age.
 -- Groucho Marx

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


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

Bug#803178: libmongodb-perl: FTBFS on various architectures

[gregor herrmann]

Package: libmongodb-perl
Version: 1.0.2-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Yesterday's 1.0.2-1 upload failed to build on mips, powerpc, and
s390x (plus hppa and ppc64):

https://buildd.debian.org/status/package.php?p=libmongodb-perl
https://buildd.debian.org/status/logs.php?pkg=libmongodb-perl&ver=1.0.2-1

The failing tests seem to be the same on all architectures, and they
are new in this release.

Cheers,
gregor

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJWL7kLXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGfcwP/1WrCIFUU45q89fZWNLGi/7T
KuVVlpFkdaNUZde9oMqAX1i8X0opkwhOkBHDv6Hk/cLLjR3hZPFLGFY3y8gWnwFM
aHgIpWk8oWx7cWPnSwCmFHmGDCeIPMR8OyYfUNP3eFP7r6eU8Hg0j2Z9qAko8g2s
H0GA6YL4Gf2kk3jZF3s6FsZlVrqk7XBoJ8KWhGLtQJDd8T2QsxgN+mTykdp1Bl2w
Bqep8lRiuSb7lU0lWPEEAQHdh/XVMmEmxag0bacx3zUHIeXYz8t5cZtzco9yKoVk
4QVzr9rNZCHws2xUQfKpW7MjuYHjmSfQvEhpmDO15GXblAs6OusnKsac/tvYxm2y
0QdZCTMgSEslLtHh8M0VR3IIzNFrdM6u0Yce0KeAThkoyn+3XLKvUqw36/LH5e2U
fmPFlVA0h5m7feuiKvuzUywT/pjvZHdegU4f5tjLQZ4YvE4C47DGL6+nbTJFShuY
MTtR0fRWBmIHjK1auqS70x1oJgcUCKShz2w67Dcy1MPQrUweIhKNHhiGj2rgBm1M
Fdey+8u+nPntEZ2+2Pd1mv1iRVqxZDg/c3HzgnhifpyZg5BqKHH/ceO/BttmatIy
6pcMKUEpfDpNl3b0K4baUAqHjoXC76xQbL+sD1eubGSUfzH1Um1ujUq5CokdoG6W
V4GN1ByIT4SL9yU4XaaK
=+/VU
-END PGP SIGNATURE-

Bug#802544: Xorg.wrap move to xorg-legacy broke X startup (permissions)

[Julien Cristau]

On Thu, Oct 22, 2015 at 14:39:40 -0700, Scott Mcdermott wrote:

> Julien Cristau on 2015/10/22 +0200 @07:47:28:
> > > That would surely be a regression.  Debian went
> > > from a working X that dropped privileges, to a
> > > non-working X that can only be run as root.  Huh??
> >
> > No, Debian is going from an X server that always runs
> > as root to one that can run as unprivileged user in
> > most cases.  There was previously no dropping
> > privileges.
> 
> Ok, my mistake; I inferred from being able to "pkill X"
> successfully as ordinary user, that it was not running
> as root.  It turns out that while X runs with ruid=user
> (which allows kill(2) to work), it retains euid=0 still
> the whole time.  Thank you for your correction.
> 
> However, since I'm running KMS, I don't understand why
> root is needed (ignoring the tty permission issue -- I
> could make easily make a group for this) in the first
> place?
> 
> I found three places which make me think this is both
> possible and was working at some point:
> 
> 1. I found a trivial patch[1] that was in both Ubuntu
>and ChromeOS before, which added a '-nohwaccess'
>flag to Xorg, which basically just no-oped
>xf86EnableIOPorts, and it seemed to work fine for
>people before...
> 
> 2. I also found a mailing list post[2] indicating that
>Gentoo Hardened removed ioperm(2) and iopl(2) from
>their kernel entirely and X still ran fine (with
>KMS) once it was told to continue (ignore the
>error).
> 
> 3. it looks like Xorg itself merged a fix[3][4] to
>ignore hardware I/O port error, based on comments[5]
>by keithp.
> 
> Why can't '-nohwaccess' flag be added to the X server
> (I'll handle device node permissions myself)?
> Alternatively, why not just have X drop privs via
> setreuid() after it does whatever it thinks it has to
> with the hardware?
> 
> Also, how does systemd-logind do this? It must have
> euid=0 itself do the iopl, unless there is some magic
> trick?
> 
> Please do not force me to install systemd.  I realize I
> can run the X server as root, but there seems to be a
> trivial way to make it so that those of us who don't
> use systemd (but still use Debian) don't have to run
> our X server as root either.
> 
The main problem logind solves for display servers (and which is
privileged) is access to input devices.  Something has to decide which
user session gets to read from which input devices.  That's logind's
job.  It's still privileged, but it's a lot less code than the whole X
server.  AIUI ChromeOS could get away without that because, being a
single-user system, it doesn't care about one user reading another
user's passwords.  You can still use this without systemd as pid 1 (why
one would want to keep sysvinit is beyond me, but whatever); you do need
logind though.

Cheers,
Julien


signature.asc
Description: PGP signature

Bug#802650: marked as done (miniupnpc: CVE-2015-6031: Buffer overflow vulnerability in XML parser functionality)

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2015 17:33:59 +
with message-id 
and subject line Bug#802650: fixed in miniupnpc 1.9.20140610-2.1
has caused the Debian Bug report #802650,
regarding miniupnpc: CVE-2015-6031: Buffer overflow vulnerability in XML parser 
functionality
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.)


-- 
802650: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802650
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: miniupnpc
Version: 1.5-2
Severity: grave
Tags: security patch upstream fixed-upstream
Justification: user security hole

Hi,

the following vulnerability was published for miniupnpc.

CVE-2015-6031[0]:
Buffer overflow vulnerability in XML parser functionality

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-6031
[1] 
https://github.com/miniupnp/miniupnp/commit/79cca974a4c2ab1199786732a67ff6d898051b78

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: miniupnpc
Source-Version: 1.9.20140610-2.1

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated miniupnpc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 25 Oct 2015 13:41:21 +0100
Source: miniupnpc
Binary: miniupnpc libminiupnpc10 libminiupnpc-dev python-miniupnpc
Architecture: source
Version: 1.9.20140610-2.1
Distribution: unstable
Urgency: high
Maintainer: Thomas Goirand 
Changed-By: Salvatore Bonaccorso 
Closes: 802650
Description: 
 libminiupnpc-dev - UPnP IGD client lightweight library development files
 libminiupnpc10 - UPnP IGD client lightweight library
 miniupnpc  - UPnP IGD client lightweight library client
 python-miniupnpc - UPnP IGD client lightweight library Python bindings
Changes:
 miniupnpc (1.9.20140610-2.1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Add CVE-2015-6031.patch patch.
 CVE-2015-6031: Buffer overflow vulnerability in XML parser
 functionality. (Closes: #802650)
Checksums-Sha1: 
 a7bc5553eb59635f2a2423cc289025f7dd17c267 2101 miniupnpc_1.9.20140610-2.1.dsc
 5751dce0e0e57bba6ce6610ad68c0efad5c9796e 6536 
miniupnpc_1.9.20140610-2.1.debian.tar.xz
Checksums-Sha256: 
 c7a3b1bda0d6952d1701cc1887a8bf1e2812528b7116d54bbcce9ed32021b40e 2101 
miniupnpc_1.9.20140610-2.1.dsc
 8cfb387b2211b60a972a397047f8d5906de340efd74bfd5841fe072d2d4752b6 6536 
miniupnpc_1.9.20140610-2.1.debian.tar.xz
Files: 
 80d534e474897c3b600b14d9ad4aaec2 2101 net optional 
miniupnpc_1.9.20140610-2.1.dsc
 4282ef8e85f73252d4ea6f5d0b874baf 6536 net optional 
miniupnpc_1.9.20140610-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJWLlX6AAoJEAVMuPMTQ89EzjgP/RUcfO/rrNRL1YM7yFIfO/yE
QMhjQbDRg2tTvsE01wuMzFKAaUstJVkg8Rn0JpZzqV0NfjA0VVRDSTGKbRhqcVS7
0ettIzXomAMtiyA9A3zgtenN/HFbVLpszCB531b87GwKVjJIFETkLm7W2OMOctq0
Pbet+h1RD31F56TYTUkzUasA0/jfaEZ9v/sj3bpysLbrTAxmmHm6j2rd3lTXvyzk
TMdPpG4kh6vRrg1e24Dv56RuoN8jULJCw4Tp0EPwnqAygCOkNqLTwkZ6FElheDrB
h/MnizrSNiY5UK9OBVCMtzFb1U6dZ/dqstRE5iW/FLXQT1cr4eKV6CTYxCvp3RJl
B6aPyHSutGUwk8Ii+hOyCq6cRYqnp/jbcrAHI8LOXI0w3CPT2tUJIWZypDxMsdjQ
jNVUW8oeojpLlUOi9Y1QHV9tFiNHNHyWF+QwRsbk3TDYLUb6VVzZEOTjSTha1aYy
QID7w3qOhIQre+n4chWgwQ71i58XQ2tnC7segUWPXvDnPGWxlTv2EPqyHRV8TY19
0q1jfRlHqPzuEIl/KtZVCVuUxTXVqXKcwsgG1R6BdIOaIyX6VDlkkixrOPt4IkPn
PPn2t7tKW4y3rVv6rZJ2uj6j8mWtNpIWVjI3qycPGmavxeLdtURt52Pp7s6WmSb6
XD1mBso8dUn9JlTWw5rI
=un+6
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#803161: mailman: /var/log/mailman/* world-readable by default, leaking sensitive list information

[Debian Bug Tracking System]

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

> severity 803161 normal
Bug #803161 [mailman] mailman: /var/log/mailman/* world-readable by default, 
leaking sensitive list information
Severity set to 'normal' from 'critical'
> thanks
Stopping processing here.

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

Bug#803161: mailman: /var/log/mailman/* world-readable by default, leaking sensitive list information

[Florian Weimer]

severity 803161 normal
thanks

* Dominik George:

> Severity: critical
> Tags: security
> Justification: root security hole
>
> The log files of mailman, residing in /var/lib/mailman/log and in
> /var/log/mailman, and the log directory itself are created
> world-readable by default. This discloses sensitive information about
> list users, for example e-mail addresses and full names in the subscribe
> log, to all unprivileged system users that have shell or filesystem
> access.

This issue can be considered a security vulnerability, but it is
certainly not a rot security hole, hence lowering the severity.

Florian

Bug#793328: marked as done (gphoto2-cffi: Must build-depend on python3-all-dev, not python-dev)

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2015 17:19:00 +
with message-id 
and subject line Bug#793328: fixed in gphoto2-cffi 0.2-3
has caused the Debian Bug report #793328,
regarding gphoto2-cffi: Must build-depend on python3-all-dev, not python-dev
to be marked as done.

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

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


-- 
793328: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793328
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gphoto2-cffi
Version: 0.2-2
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu wily ubuntu-patch

Hi Aigars,

The gphoto2-cffi package has a build-dependency on python3-dev, but tries to
build for all supported versions of python3.  This causes a build failure
when there is more than one version of python3 in the "supported" set,
because since python3-all-dev is missing the C headers are unavailable.

The attached trivial patch fixed the bug in Ubuntu.

As there is a transition to python3.5 coming soon in Debian, I expect the
severity of this bug to increase shortly.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru gphoto2-cffi-0.2/debian/control gphoto2-cffi-0.2/debian/control
--- gphoto2-cffi-0.2/debian/control	2015-06-25 12:05:02.0 -0700
+++ gphoto2-cffi-0.2/debian/control	2015-07-22 14:30:36.0 -0700
@@ -2,7 +2,7 @@
 Maintainer: Aigars Mahinovs 
 Section: python
 Priority: optional
-Build-Depends: python-setuptools (>= 0.6b3), python3-setuptools, python-enum34, python-all (>= 2.6.6-3), python3-all, debhelper (>= 9), dh-python, python-cffi, python3-cffi, python-dev, python3-dev, libgphoto2-dev
+Build-Depends: python-setuptools (>= 0.6b3), python3-setuptools, python-enum34, python-all (>= 2.6.6-3), python3-all, debhelper (>= 9), dh-python, python-cffi, python3-cffi, python-dev, python3-all-dev, libgphoto2-dev
 Standards-Version: 3.9.6
 
 Package: python-gphoto2
--- End Message ---
--- Begin Message ---
Source: gphoto2-cffi
Source-Version: 0.2-3

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

Debian distribution maintenance software
pp.
Aigars Mahinovs  (supplier of updated gphoto2-cffi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 25 Oct 2015 09:11:23 +0300
Source: gphoto2-cffi
Binary: python-gphoto2 python3-gphoto2
Architecture: source amd64
Version: 0.2-3
Distribution: unstable
Urgency: low
Maintainer: Aigars Mahinovs 
Changed-By: Aigars Mahinovs 
Description:
 python-gphoto2 - GPhoto2 bindings with simpler API
 python3-gphoto2 - GPhoto2 bindings with simpler API
Closes: 793328
Changes:
 gphoto2-cffi (0.2-3) unstable; urgency=low
 .
   * Python 3.5 support (Closes: #793328)
Checksums-Sha1:
 f667e2df4b68912ae73ea21c1d5c2d219bcf8e1b 1929 gphoto2-cffi_0.2-3.dsc
 d80e2005e42c89894795a0fa9aca3fa3b9251c5b 2080 gphoto2-cffi_0.2-3.debian.tar.xz
 033b08b7eb864c51fd42c65ed9d06398baa795ff 31086 python-gphoto2_0.2-3_amd64.deb
 48b6289afad1754d797922999b8fe2080a9870cc 31544 python3-gphoto2_0.2-3_amd64.deb
Checksums-Sha256:
 8ad1a84ba0495adc50b883a691df2a78476835a9b1fc9084f2b14f83e1f2d2b7 1929 
gphoto2-cffi_0.2-3.dsc
 394e0cc7ec5d9767ef055590ac6889a2779858513bb5f5861fe41e491170c13b 2080 
gphoto2-cffi_0.2-3.debian.tar.xz
 a6c731940a344dc3fcf97a8054bad14caf865d3b21c92dfe7925cc1b55da2091 31086 
python-gphoto2_0.2-3_amd64.deb
 9635a70461429dab2189d4528a5ec76088c315e4a63291680dacf22874fb748d 31544 
python3-gphoto2_0.2-3_amd64.deb
Files:
 25db4b543856db808dd6bb3b7af4afe1 1929 python optional gphoto2-cffi_0.2-3.dsc
 cd391acb32d9e15b24ce698cf44cb4bc 2080 python optional 
gphoto2-cffi_0.2-3.debian.tar.xz
 3250d63357bf31fc34fcee4fe5e21d66 31086 python optional 
python-gphoto2_0.2-3_amd64.deb
 95f2f0e14fc3689c6b3836b0074a34ce 31544 python optional 
python3-gphoto2_0.2-3_amd64.deb

-BEGIN PG

Bug#802452: nvidia-legacy-304xx-driver: X fails to start

[Stéphane Glondu]

Le 27/10/2015 17:07, Stéphane Glondu a écrit :
> It seems that I am experiencing the same bug. I have upgraded to
> 304.128-6, and the bug is still present.

I tried using the vesa driver. It worked for a few hours, then froze the
graphical display (I could still SSH in). Then, it never worked again. I
tried with different drivers: nouveau, fbdev. None of them work (X
doesn't start). I then downgraded the kernel to 4.1.0-2-amd64 and it
seems to work. Note: in the process, I also downgraded
xserver-xorg-video-nvidia-legacy-304xx to 304.125-2.

Note: it seems that #801515 happens when using the nvidia driver. I have
no idea how it is related.

Cheers,

-- 
Stéphane

Bug#802867: [Debian-med-packaging] Bug#802867: pyqi not running in python-biom-format build

[Andreas Tille]

Hi Tim,

On Tue, Oct 27, 2015 at 02:57:49PM +, Tim Booth wrote:
> It is called explicitly in debian/rules.  It may even have been me who
> originally added the line.  It works for 2.1.4.

Arg.  Sorry for missing that ...
 
> All it does is generate the BASH completions so I wouldn't call it
> critical.  Heck, I don't even use BASH as my shell anyway.
> 
> > Do you think we should delay 2.1.5 and rather upload 2.1.4 until things
> > are fully settled?
> 
> From my point of view, yes.  This module supports QIIME and I tested
> QIIME with 2.1.4.  The fact that 2.1.5 has substantial changes makes me
> suspicious.

OK, I realise test errors now (since the build went further) for 2.1.5.
I'll step back to 2.1.4 and will keep on asking here in case the
problems might not vanish. 

Thanks for opening my eyes

Andreas.

-- 
http://fam-tille.de

Bug#802811: libqt5x11extras5: causes konsole to segfault in libX11 on startup

[Alexandre Pereira Nunes]

Package: libqt5x11extras5
Version: 5.5.1-2
Followup-For: Bug #802811

I can confirm that too. no kde app opens after having this upgraded.
Besides, the testing version is gone so I'll have to manually search for an
older version.


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

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

Versions of packages libqt5x11extras5 depends on:
ii  libc6 2.19-22
ii  libqt5core5a  5.4.2+dfsg-9
ii  libqt5gui55.4.2+dfsg-9

libqt5x11extras5 recommends no packages.

libqt5x11extras5 suggests no packages.

-- no debconf information

Bug#802618: marked as done (keyboard/mouse support broken - mising dep on libpam-systemd?)

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2015 17:05:47 +
with message-id 
and subject line Bug#802618: fixed in xorg-server 2:1.17.3-1
has caused the Debian Bug report #802618,
regarding keyboard/mouse support broken - mising dep on libpam-systemd?
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.)


-- 
802618: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802618
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xinit
Version: 1.3.4-3
Severity: important

Hello,

yesterday's X11 upgrade broke my setup, both keyboard and mouse are
dead under X.

I am starting X with startx, and am ataching the X log file. Comparing
old (X as root) ad new logfile, these seem to be the interesting
lines: 


[   406.871] (II) LoadModule: "evdev"
[   406.871] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[   406.898] (II) Module evdev: vendor="X.Org Foundation"
[   406.898]compiled for 1.16.4, module version = 2.9.2
[   406.898]Module class: X.Org XInput Driver
[   406.898]ABI class: X.Org XInput driver, version 21.0
[...]
[   406.899] (II) config/udev: Adding input device HID 046a:0023 
(/dev/input/event0)
[   406.899] (**) HID 046a:0023: Applying InputClass "evdev keyboard catchall"
[   406.899] (II) Using input driver 'evdev' for 'HID 046a:0023'
[   406.899] (**) HID 046a:0023: always reports core events
[   406.899] (**) evdev: HID 046a:0023: Device: "/dev/input/event0"
[   406.899] (EE) evdev: HID 046a:0023: Unable to open evdev device 
"/dev/input/event0".
[   406.899] (EE) PreInit returned 2 for "HID 046a:0023"
[   406.899] (II) UnloadModule: "evdev"
[   406.900] (II) config/udev: Adding input device HID 046a:0023 
(/dev/input/event1)
[   406.900] (**) HID 046a:0023: Applying InputClass "evdev keyboard catchall"
[   406.900] (II) Using input driver 'evdev' for 'HID 046a:0023'
[   406.900] (**) HID 046a:0023: always reports core events
[   406.900] (**) evdev: HID 046a:0023: Device: "/dev/input/event1"
[   406.900] (EE) evdev: HID 046a:0023: Unable to open evdev device 
"/dev/input/event1".
[   406.900] (EE) PreInit returned 2 for "HID 046a:0023"
[   406.900] (II) UnloadModule: "evdev"
[   406.901] (II) config/udev: Adding input device Logitech USB-PS/2 Optical 
Mouse (/dev/input/event2)
[   406.901] (**) Logitech USB-PS/2 Optical Mouse: Applying InputClass "evdev 
pointer catchall"
[   406.901] (II) Using input driver 'evdev' for 'Logitech USB-PS/2 Optical 
Mouse'
[   406.901] (**) Logitech USB-PS/2 Optical Mouse: always reports core events
[   406.901] (**) evdev: Logitech USB-PS/2 Optical Mouse: Device: 
"/dev/input/event2"
[   406.901] (EE) evdev: Logitech USB-PS/2 Optical Mouse: Unable to open evdev 
device "/dev/input/event2".
[   406.901] (EE) PreInit returned 2 for "Logitech USB-PS/2 Optical Mouse"
[   406.901] (II) UnloadModule: "evdev"
[   406.901] (II) config/udev: Adding input device Logitech USB-PS/2 Optical 
Mouse (/dev/input/mouse0)
[   406.901] (II) No input driver specified, ignoring this device.



ls l /dev/input
insgesamt 0
drwxr-xr-x 2 root root 120 Okt 21 19:23 by-id
drwxr-xr-x 2 root root 140 Okt 21 19:23 by-path
crw-rw 1 root input 13, 64 Okt 21 19:23 event0
crw-rw 1 root input 13, 65 Okt 21 19:23 event1
crw-rw 1 root input 13, 74 Okt 21 19:23 event10
crw-rw 1 root input 13, 75 Okt 21 19:23 event11
crw-rw 1 root input 13, 76 Okt 21 19:23 event12
crw-rw 1 root input 13, 77 Okt 21 19:23 event13
crw-rw 1 root input 13, 66 Okt 21 19:23 event2
crw-rw 1 root input 13, 67 Okt 21 19:23 event3
crw-rw 1 root input 13, 68 Okt 21 19:23 event4
crw-rw 1 root input 13, 69 Okt 21 19:23 event5
crw-rw 1 root input 13, 70 Okt 21 19:23 event6
crw-rw 1 root input 13, 71 Okt 21 19:23 event7
crw-rw 1 root input 13, 72 Okt 21 19:23 event8
crw-rw 1 root input 13, 73 Okt 21 19:23 event9
crw-rw 1 root input 13, 63 Okt 21 19:23 mice
crw-rw 1 root input 13, 32 Okt 21 19:23 mouse0

I am not a member of the input group.

I am not sure against which package I should report this, wich is
basically the only reason I have importanr severity. ;-) I would be
grateful for a quick fix. 

cu Andreas

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: s

Bug#802544: marked as done (Xorg.wrap move to xorg-legacy broke X startup (permissions))

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2015 17:05:47 +
with message-id 
and subject line Bug#802544: fixed in xorg-server 2:1.17.3-1
has caused the Debian Bug report #802544,
regarding Xorg.wrap move to xorg-legacy broke X startup (permissions)
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.)


-- 
802544: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802544
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xserver-xorg-legacy
Version: 2:1.17.2-3
Severity: grave

I recently did an upgrade of X, which broke it on my machine.
Here are old (working) and new (broken) versions that apt-get
installed, as shown in /var/log/apt/history.log:

xserver-xorg-core:amd64 (1.17.2-1.1, 1.17.2-3)

This upgrade has broken X startup for me.  Here is how
I start X (as ordinary user):

exec setsid env -i \
LOGNAME=$LOGNAME \
USER=$USER \
HOME=$HOME \
PATH=$PATH \
EDITOR=$EDITOR \
DISPLAY=$DISPLAY \
SHELL=$SHELL \
TERM=$TERM \
LANG=$LANG \
X :0 vt63 \
-dpi 106 \
-nolisten tcp \
-noreset \
-keeptty \
-novtswitch

Then I run my window manager.  This has worked for me
at least 10 years.  I am using KMS (Intel i965GM):

 $ fbset
mode "1024x768"
geometry 1024 768 1024 768 32
timings 0 0 0 0 0 0 0
accel true
rgba 8/16,8/8,8/0,0/0
endmode

 $ dmesg | grep fbcon:
fbcon: inteldrmfb (fb0) is primary device

I have been able to run the X server (as an ordinary user)
using /usr/bin/X since modesetting was originally
implemented in the kernel.

Looking at the ChangeLog, I saw that /usr/bin/X was actually a
wrapper, which was moved to xserver-xorg-legacy.  Ok then:

Install: xserver-xorg-legacy:amd64 (1.17.2-3)

Problem 1: after upgrade, permissions bad on device

/usr/lib/xorg/Xorg.wrap: (EE) xf86OpenConsole:
  Cannot open virtual console 63 (Permission denied)

That didn't happen before.  It's mode 0620 root:tty, and
I'm not in the tty group, so the wrapper must have opened
the terminal with escalated privs before the upgrade, but
not after.  Note that I routinely "pkill X" to kill my
server -- as the ordinary user that started it -- so it
was definitely running without privs after initialization.
It must have done something while setuid, and then dropped
the privs.

My /etc/X11/Xwrapper.config contains the single line:

allowed_users=anybody

I changed /dev/tty63 to mode 0666 to move past this, but
then got a new problem.

Problem 2: after upgrade, IO ports operation not permitted:

X: xf86EnableIOPorts: failed to set IOPL for I/O
  (Operation not permitted)

I tried invoking Xorg.wrap directly (to eliminate the new
shell script at /usr/bin/X) and also copying it into place as
/usr/bin/X, but neither works, same errors.  I traced it to be
sure it was running the wrapper.  Not clear to me why this is
broken, since the ChangeLog implies only that it moved to a
different package.  But clearly the behavior is different now
and it actually works differently.

Note, X *does* start fine as root with the new package, but, I
don't want to run my X server as root, and didn't have to
before this upgrade.

Note, I used same kernel before and after: 4.1.0-2-amd64

Downgrade fixes it:

Commandline: apt-get install xserver-xorg-core=2:1.17.2-1.1
Downgrade: xserver-xorg-core:amd64 (1.17.2-3, 1.17.2-1.1)
Remove: xserver-xorg-legacy:amd64 (1.17.2-3),
xserver-xspice:amd64 (0.1.4-3),
xserver-xorg:amd64 (7.7+12)

Commandline: apt-get install xserver-xorg=1:7.7+9
Install: xserver-xorg:amd64 (7.7+9)

Note that I *do not* use systemd.  Please don't tell me I have
to either use systemd, or run my X server as root.  I didn't
have to do either before this upgrade.

Please advise; thanks.
--- End Message ---
--- Begin Message ---
Source: xorg-server
Source-Version: 2:1.17.3-1

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

Debian distribution maintenance software
pp.
Julien Cristau  (supplier of updated xorg-server package)

(This message was generated automatically at their re

Bug#784070: is it maybe possible to settle dislikings and fix this bug?

[Dimitri John Ledkov]

On 27 October 2015 at 15:42, Ben Hutchings  wrote:
> On Tue, 2015-10-27 at 18:30 +0300, Michael Tokarev wrote:
>> 27.10.2015 18:23, Ben Hutchings wrote:
>> > On Tue, 2015-10-27 at 10:25 +0300, Michael Tokarev wrote:
>> > > I'm not maintaining mdadm anymore.
>> >
>> > Then why have you not orphaned it?
>>
>> It is team-maintained (or was),
>
> I don't see any sign of anyone else active in the team.
>

I have outstanding patches to upload. And Michael previously asked me
to continue mdadm maintenance.

However 0-day / low NMUs are more than welcomed. I trust all DDs to
act in good faith.

>>  and orphaning it means uploading
>> it which means I'll have to ask the d-i team again.  I described
>> it all in the previous email.
>
> Please be a little more mature about this.
>
> Ben.

-- 
Regards,

Dimitri.

Processed: Re: Marking as found in older versions

[Debian Bug Tracking System]

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

> notfound 798661 5.4.2+dfsg-9
Bug #798661 [libqt5widgets5] libqt5widgets5: regression in 5.5 breaks vlc video 
playback
Bug #801442 [libqt5widgets5] vlc: plane 0 not alingned, diabling direct 
rendering
Bug #802886 [libqt5widgets5] vlc: QT Interface wont full screen or renders only 
a small portion of the video
Bug #802922 [libqt5widgets5] vlc: only top half of video shown when playing 
DVD's under kwin/xfce
No longer marked as found in versions qtbase-opensource-src/5.4.2+dfsg-9.
No longer marked as found in versions qtbase-opensource-src/5.4.2+dfsg-9.
No longer marked as found in versions qtbase-opensource-src/5.4.2+dfsg-9.
No longer marked as found in versions qtbase-opensource-src/5.4.2+dfsg-9.
> thanks
Stopping processing here.

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

Bug#798661: Marking as found in older versions

[Lisandro Damián Nicanor Pérez Meyer]

notfound 798661 5.4.2+dfsg-9
thanks

My bad, it appears in 5.5

-- 
Una vez que hemos eliminado lo imposible, lo que queda, por improbable que
parezca, es la verdad.
  Sherlock Holmes

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


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

Processed: Marking as found in older versions

[Debian Bug Tracking System]

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

> found 798661 5.4.2+dfsg-9
Bug #798661 [libqt5widgets5] libqt5widgets5: regression in 5.5 breaks vlc video 
playback
Bug #801442 [libqt5widgets5] vlc: plane 0 not alingned, diabling direct 
rendering
Bug #802886 [libqt5widgets5] vlc: QT Interface wont full screen or renders only 
a small portion of the video
Bug #802922 [libqt5widgets5] vlc: only top half of video shown when playing 
DVD's under kwin/xfce
Marked as found in versions qtbase-opensource-src/5.4.2+dfsg-9.
Marked as found in versions qtbase-opensource-src/5.4.2+dfsg-9.
Marked as found in versions qtbase-opensource-src/5.4.2+dfsg-9.
Marked as found in versions qtbase-opensource-src/5.4.2+dfsg-9.
> thanks
Stopping processing here.

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

Bug#798661: Marking as found in older versions

[Lisandro Damián Nicanor Pérez Meyer]

found 798661 5.4.2+dfsg-9
thanks

This bug is already present in 5.4.2 in testing (+/- some half fixes in 5.5), 
so marking it as found there too.

-- 
http://xkcd.com/162/

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


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

Processed: your mail

[Debian Bug Tracking System]

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

> tag 802415 pending
Bug #802415 [src:zope.schema] zope.schema: FTBFS: Missing build-dep on 
zope.interface(?)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#801900: axe-demultiplexer: /usr/bin/axe already used by the axe package

[Andreas Tille]

Hi Kevin,

do you have a plan to work on this?  I'd recommend to choose the name

/usr/bin/axe-demultiplexer

and provide

/usr/lib/debian-med/bin/axe

in addition and add

Recommends: med-config (>= 2.1)

to d/control.  This could be completed by and according hint in
debian/README.Debian.  You might like to have a look into the packages
inspect, libgenome-perl or plink as examples.  Feel free to ask for
further advise.

Kind regards

   Andreas.

On Thu, Oct 15, 2015 at 09:36:38PM +0200, Andreas Beckmann wrote:
> Package: axe-demultiplexer
> Version: 0.2.8-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> 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 axe-demultiplexer.
>   Preparing to unpack .../axe-demultiplexer_0.2.8-1_amd64.deb ...
>   Unpacking axe-demultiplexer (0.2.8-1) ...
>   dpkg: error processing archive 
> /var/cache/apt/archives/axe-demultiplexer_0.2.8-1_amd64.deb (--unpack):
>trying to overwrite '/usr/bin/axe', which is also in package axe 6.1.2-16.2
>   Errors were encountered while processing:
>/var/cache/apt/archives/axe-demultiplexer_0.2.8-1_amd64.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.
> 
> 
> Cheers,
> 
> Andreas



-- 
http://fam-tille.de

Bug#803173: [mediatomb] Cannot start

[Antonio Marcos López Alonso]

Package: mediatomb
Version: 0.12.1-47-g7ab7616-1
Severity: grave

--- Please enter the report below this line. ---
Since one of the latest system upgrades, mediatomb has ceased to work, not 
even with "service mediatomb restart" as some previous report stated.

Output of "service mediatomb status" follows:

● mediatomb.service - UPnP MediaServer
   Loaded: loaded (/lib/systemd/system/mediatomb.service; disabled; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since mar 2015-10-27 16:30:21 WET; 11min 
ago
  Process: 15963 ExecStopPost=/sbin/ifconfig $MT_INTERFACE -allmulti 
(code=exited, status=0/SUCCESS)
  Process: 15960 ExecStopPost=/sbin/route del -net 239.0.0.0 netmask 255.0.0.0 
(code=exited, status=0/SUCCESS)
  Process: 15951 ExecStart=/usr/bin/mediatomb -d -u $MT_USER -g $MT_GROUP -P 
/run/mediatomb.pid -l $MT_LOGFILE -m $MT_HOME -f $MT_CFGDIR -p $MT_PORT -e 
$MT_INTERFACE (code=exited, status=0/SUCCESS)
  Process: 15948 ExecStartPre=/sbin/ifconfig $MT_INTERFACE allmulti 
(code=exited, status=0/SUCCESS)
  Process: 15945 ExecStartPre=/sbin/route add -net 239.0.0.0 netmask 255.0.0.0 
$MT_INTERFACE (code=exited, status=0/SUCCESS)
  Process: 15942 ExecStartPre=/bin/grep -q MT_USER /etc/default/mediatomb 
(code=exited, status=0/SUCCESS)
 Main PID: 15952 (code=exited, status=1/FAILURE)

oct 27 16:30:21 ... systemd[1]: Starting UPnP MediaServer...
oct 27 16:30:21 ... systemd[1]: Started UPnP MediaServer.
oct 27 16:30:21 ... systemd[1]: mediatomb.service: Main process exited, 
code=exited, status=1/FAILURE
oct 27 16:30:21 ... systemd[1]: mediatomb.service: Unit entered failed state.
oct 27 16:30:21 ... systemd[1]: mediatomb.service: Failed with result 'exit-
code'.

--- System information. ---
Architecture: amd64
Kernel:   Linux 4.2.0-1-amd64

Debian Release: stretch/sid
  900 testing security.debian.org 
  900 testing ftp.es.debian.org 
  500 wilyppa.launchpad.net 
  500 unstableftp.es.debian.org 
  500 trusty  ppa.launchpad.net 
  500 stable  update.devolo.com 
  500 stable  kxstudio.linuxaudio.org 
  500 stable  dl.google.com 
  500 sid linux.dropbox.com 
  500 lucid   ppa.launchpad.net 
  500 gcc5kxstudio.linuxaudio.org 

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.

Bug#803136: docker.io: FTBFS

[Tianon Gravi]

On 27 October 2015 at 02:33, Edmund Grimley Evans
 wrote:
> There is a different error in each case, unfortunately, and on an
> up-to-date amd64 system there is a yet another, different error.

Yeah, this is most definitely due to the Go 1.5.1 upload.  Thanks for
the heads up.

> I would guess that the change to Go 1.5.1 is implicated and that it
> would be a good idea to upgrade docker.io first of all. Apparently
> 1.9.0 is due to be released on 2015-10-29.

I've been working on packaging deps for 1.8+ for several weeks now --
we're down to the last one waiting in NEW ("notary") before I can
upload 1.8, so I might have to look at an intermediate 1.7.1 upload if
it doesn't get ACCEPT soon. :(

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#803170: python-gunicorn: fails to upgrade with a syntax error

[Antonio Terceiro]

Package: python-gunicorn
Version: 19.3-1
Severity: grave
Justification: renders package unusable

Setting up python-gunicorn (19.3-1) ...
  File "/usr/lib/python2.7/dist-packages/gunicorn/workers/_gaiohttp.py", line 68
yield from self.wsgi.close()
 ^
SyntaxError: invalid syntax

dpkg: error processing package python-gunicorn (--configure):
 subprocess installed post-installation script returned error exit status 101
dpkg: dependency problems prevent configuration of gunicorn:
 gunicorn depends on python-gunicorn (= 19.3-1); however:
  Package python-gunicorn is not configured yet.

dpkg: error processing package gunicorn (--configure):
 dependency problems - leaving unconfigured




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

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

Versions of packages python-gunicorn depends on:
ii  python-pkg-resources  18.4-2
ii  python-setuptools 18.4-2
pn  python:any

python-gunicorn recommends no packages.

python-gunicorn suggests no packages.

-- no debconf information

-- 
Antonio Terceiro 


signature.asc
Description: PGP signature

Bug#802757: marked as done (djangorestframework-gis: FTBFS with djangorestframework 3.2.2-1)

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2015 16:19:16 +
with message-id 
and subject line Bug#802757: fixed in djangorestframework-gis 0.9.5-1
has caused the Debian Bug report #802757,
regarding djangorestframework-gis: FTBFS with djangorestframework 3.2.2-1
to be marked as done.

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

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


-- 
802757: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802757
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: djangorestframework-gis
Version: 0.8-2
Severity: serious
Justification: Does not build from source

I just uploaded djangorestframework 3.2.2-1 to unstable.

Will see if I can look at this if I get a chance. If not tonight, possibly
tomorrow.

An example of the error - there are several similar errors that occur during
testing.

==
ERROR: test_HTML_browsable_geojson_location_list 
(django_restframework_gis_tests.tests.TestRestFrameworkGis)
--
Traceback (most recent call last):
  File "tests/django_restframework_gis_tests/tests.py", line 23, in setUp
self.location_list_url = reverse('api_location_list')
  File "/usr/lib/python2.7/dist-packages/django/core/urlresolvers.py", line 
551, in reverse
return iri_to_uri(resolver._reverse_with_prefix(view, prefix, *args, 
**kwargs))
  File "/usr/lib/python2.7/dist-packages/django/core/urlresolvers.py", line 
415, in _reverse_with_prefix
self._populate()
  File "/usr/lib/python2.7/dist-packages/django/core/urlresolvers.py", line 
292, in _populate
for name in pattern.reverse_dict:
  File "/usr/lib/python2.7/dist-packages/django/core/urlresolvers.py", line 
315, in reverse_dict
self._populate()
  File "/usr/lib/python2.7/dist-packages/django/core/urlresolvers.py", line 
303, in _populate
lookups.appendlist(pattern.callback, (bits, p_pattern, 
pattern.default_args))
  File "/usr/lib/python2.7/dist-packages/django/core/urlresolvers.py", line 
231, in callback
self._callback = get_callable(self._callback_str)
  File "/usr/lib/python2.7/dist-packages/django/utils/lru_cache.py", line 101, 
in wrapper
result = user_function(*args, **kwds)
  File "/usr/lib/python2.7/dist-packages/django/core/urlresolvers.py", line 97, 
in get_callable
mod = import_module(mod_name)
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
__import__(name)
  File "tests/django_restframework_gis_tests/views.py", line 5, in 
from .serializers import *
  File "tests/django_restframework_gis_tests/serializers.py", line 2, in 

from rest_framework_gis import serializers as gis_serializers
  File "/«PKGBUILDDIR»/rest_framework_gis/serializers.py", line 16, in 
_geo_field_mapping = ModelSerializer._field_mapping.mapping
AttributeError: type object 'ModelSerializer' has no attribute '_field_mapping'

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

Kernel: Linux 4.2.0-0.bpo.1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: djangorestframework-gis
Source-Version: 0.9.5-1

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

Debian distribution maintenance software
pp.
Michael Fladischer  (supplier of updated 
djangorestframework-gis package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 27 Oct 2015 09:53:28 +0100
Source: djangorestframework-gis
Binary: python-djangorestframework-gis python3-djangorestframework-gis
Architecture: source all
Version: 0.9.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Michael Fladischer 
Description:
 python-djangorestframework-gis - Geographic add-ons for Django REST Framework
 p

Bug#802811: libqt5x11extras5: causes konsole to segfault in libX11 on startup

[Eric Chapman]

On Tue, 27 Oct 2015 08:48:27 +0100 =?utf-8?q?Moritz_Nisbl=C3=A9?=
 wrote:
> Package: libqt5x11extras5
> Followup-For: Bug #802811
> 
> Dear Maintainer,
> 
> I can confirm this problem.
> After upgrading libqt5x11extras5 from 5.4.2-2+b1 to 5.5.1-2
> I get segfaults on execution of nearly all KDE programs.
> 
> kernel: drkonqi[21514]: segfault at 0 ip 7f51bb302a74 sp
> 7ffee7bcf2a0 error 4 in libxcb.so.1.1.0[7f51bb2f8000+21000]
> kernel: kate[20110]: segfault at 0 ip 7f4970e58a74 sp
> 7ffe33644420 error 4 in libxcb.so.1.1.0[7f4970e4e000+21000]
> kernel: kwrite[20197]: segfault at 0 ip 7f146cf19a74 sp
> 7ffed9f43330 error 4 in libxcb.so.1.1.0[7f146cf0f000+21000]
> ...
> 
> This is especially a problem since 5.5.1-2 was migrated to testing
> this morning.
> Installation of libqt5xcbqpa5 is not an option because it hits the
> ongoing qtbase-abi-5-5-1 transition.
> 
> The downgrade of libqt5x11extras5 to version 5.4.2-2+b1 fixes the
> problem.
> 
> Best regards
> Moritz
> 
> 
> 
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers testing-updates
>   APT policy: (900, 'testing-updates'), (900,
> 'testing-proposed-updates'), (900, 'testing'), (50, 'unstable'), (49,
> 'experimental') Architecture: amd64 (x86_64) Foreign Architectures:
> i386
> 
> Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages libqt5x11extras5 depends on:
> ii  libc6 2.19-22
> ii  libqt5core5a  5.4.2+dfsg-9
> ii  libqt5gui55.4.2+dfsg-9
> 
> libqt5x11extras5 recommends no packages.
> 
> libqt5x11extras5 suggests no packages.
> 
> -- no debconf information
> 
> 
I can also confirm this bug, with the same details as above.

Regards
Eric

Bug#784070: is it maybe possible to settle dislikings and fix this bug?

[Ben Hutchings]

On Tue, 2015-10-27 at 18:30 +0300, Michael Tokarev wrote:
> 27.10.2015 18:23, Ben Hutchings wrote:
> > On Tue, 2015-10-27 at 10:25 +0300, Michael Tokarev wrote:
> > > I'm not maintaining mdadm anymore.
> > 
> > Then why have you not orphaned it?
> 
> It is team-maintained (or was),

I don't see any sign of anyone else active in the team.

>  and orphaning it means uploading
> it which means I'll have to ask the d-i team again.  I described
> it all in the previous email.

Please be a little more mature about this.

Ben.

-- 
Ben Hutchings
Never attribute to conspiracy what can adequately be explained by stupidity.


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

Bug#801410: marked as done (java-policy and java-common: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2015 15:36:22 +
with message-id 
and subject line Bug#801410: fixed in java-policy 0.55
has caused the Debian Bug report #801410,
regarding java-policy and java-common: 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.)


-- 
801410: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801410
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: java-common,java-policy
Version: java-common/0.52
Version: java-policy/0.54
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2015-10-09
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 java-common.
(Reading database ... 10896 files and directories currently installed.)
Preparing to unpack .../java-common_0.52_all.deb ...
Unpacking java-common (0.52) ...
Selecting previously unselected package java-policy.
Preparing to unpack .../java-policy_0.54_all.deb ...
Unpacking java-policy (0.54) ...
dpkg: error processing archive /var/cache/apt/archives/java-policy_0.54_all.deb 
(--unpack):
 trying to overwrite '/usr/share/doc-base/java-policy', which is also in 
package java-common 0.52
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Processing triggers for man-db (2.7.4-1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/java-policy_0.54_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


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/share/doc-base/debian-java-faq
  /usr/share/doc-base/java-policy

This bug has been filed against 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 then
also register in the BTS that the other package is affected by the bug.

-Ralf.

PS: for more information about the detection of file overwrite errors
of this kind see http://qa.debian.org/dose/file-overwrites.html.
--- End Message ---
--- Begin Message ---
Source: java-policy
Source-Version: 0.55

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated java-policy 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, 27 Oct 2015 16:02:18 +0100
Source: java-policy
Binary: java-policy
Architecture: source all
Version: 0.55
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 java-policy - Debian Java Policy
Closes: 801410
Changes:
 java-policy (0.55) unstable; urgency=medium
 .
   * Team upload.
   * Declare that java-policy breaks/replaces java-common (<< 0.54~)
 (Closes: #801410)
Checksums-Sha1:
 92e41e7bc27a82d168651aa091c304cffe3b8b97 1688 java-policy_0.55.dsc
 bd1095a2bf465476e06dbd3871e8fa915c97bd15 20180 java-policy_0.55.tar.xz
 3f3bb69e6efeeb9780ac0269d418cc8952048760 132790 java-policy_0.55_all.deb
Checksums-Sha256:
 73356a6f7766436271f52fa853b7ba37fdcbd69d4b80bb83c765beed9394af5d 1688 
java-policy_0.55.dsc
 2160f3c359865514c10fbf

Bug#803050: marked as done (miaviewit: FTBFS: configure: error: Unable to find MIA 2.2)

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2015 15:36:47 +
with message-id 
and subject line Bug#803050: fixed in miaviewit 1.0.2-1
has caused the Debian Bug report #803050,
regarding miaviewit: FTBFS: configure: error: Unable to find MIA 2.2
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.)


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

miaviewit fails to build from source in unstable/amd64:

  [..]

  checking pkg-config is at least version 0.9.0... yes
  checking for MIA... no
  configure: error: Unable to find MIA 2.2
"tail -v -n +0 config.log"

  [..]
  
  configure: exit 1
  dh_auto_configure: ./configure --build=x86_64-linux-gnu --prefix=/usr
  --includedir=${prefix}/include --mandir=${prefix}/share/man
  --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
  --disable-silent-rules --libdir=${prefix}/lib/x86_64-linux-gnu
  --libexecdir=${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode
  --disable-dependency-tracking returned exit code 1
  debian/rules:12: recipe for target 'build' failed
  make: *** [build] Error 255
  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/miaviewit_1.0.1-1.build1.log.gz


Regards,

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


miaviewit.1.0.1-1.unstable.amd64.log.txt.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: miaviewit
Source-Version: 1.0.2-1

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

Debian distribution maintenance software
pp.
Gert Wollny  (supplier of updated miaviewit 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, 27 Oct 2015 13:28:09 +0100
Source: miaviewit
Binary: libmiaviewit0 libmiaviewit-dev libmiaviewit0-dbg mia-viewit 
mia-viewit-dbg
Architecture: source i386
Version: 1.0.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Gert Wollny 
Description:
 libmiaviewit-dev - development files for the 3D visualization library
 libmiaviewit0 - MIA addon library for 3D visualization
 libmiaviewit0-dbg - Debug information for the MIA addon library for 3D 
visualization
 mia-viewit - Viewer program for 3D data sets created by using MIA
 mia-viewit-dbg - Debugging information for the MIA viewer program
Closes: 803050
Changes:
 miaviewit (1.0.2-1) unstable; urgency=medium
 .
   * New upstream release, Closes: #803050
   * d/control: - update standarts version to 3.9.6
- add libxml++2.6-dev since libmia-2.2-dev no longer
  pulls it in
- tighen build dependency on libmia-2.2-dev
   * d/rules:   correct the buildflags
   * d/copyright: Correct copyright for viewit/trackball.*
Checksums-Sha1:
 7ba4a7be0e0fd04df5f9493d32389b7f61f3e152 2311 miaviewit_1.0.2-1.dsc
 d63ac382850eedc90d696376f363bfa055960d7d 395572 miaviewit_1.0.2.orig.tar.xz
 da5760a2c2aae379f45704b1c23b43a6f5bfd823 3472 miaviewit_1.0.2-1.debian.tar.xz
 b4b57057068d0226cf04ef3d250dfbe55ac6ad6a 2734210 
libmiaviewit-dev_1.0.2-1_i386.deb
 10e49969e07c477274a57d5b28aab6b9cf6c2305 2560898 
libmiaviewit0-dbg_1.0.2-1_i386.deb
 dffdf80126106887bd41b1480543a6b90fd06305 178638 libmiaviewit0_1.0.2-1_i386.deb
 d0e209ad61b46529f92206040df56e14c060bbf8 2678702 
mia-viewit-dbg_1.0.2-1_i386.deb
 2863a0577025b35f730d21d14f554fc4ab52be51 186084 mia-viewit_1.0.2-1_i386.deb
Checksums-Sha256:
 0d3d35f860b67fe330a10732bac7d9bd5dcf1c4ac4489e98d5f20a3bab1a7939 2311 
miaviewit_1.0.2-1.dsc
 673c732301b3980690f083afb49f840764079cef9ebe4cc64c91b8c5cad4b190 395572 
miaviewit_1.0.2

Bug#784070: is it maybe possible to settle dislikings and fix this bug?

[Michael Tokarev]

27.10.2015 18:23, Ben Hutchings wrote:
> On Tue, 2015-10-27 at 10:25 +0300, Michael Tokarev wrote:
>> I'm not maintaining mdadm anymore.
> 
> Then why have you not orphaned it?

It is team-maintained (or was), and orphaning it means uploading
it which means I'll have to ask the d-i team again.  I described
it all in the previous email.

Thanks,

/mjt

Bug#784070: is it maybe possible to settle dislikings and fix this bug?

[Ben Hutchings]

On Tue, 2015-10-27 at 10:25 +0300, Michael Tokarev wrote:
[...]
> I'm not maintaining mdadm anymore.
[...]

Then why have you not orphaned it?

Ben.

-- 
Ben Hutchings
Never attribute to conspiracy what can adequately be explained by stupidity.


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

Bug#802395: debmake-doc: FTBFS: ImportError: No module named 'gi'

[Osamu Aoki]

Hi,

This reproduceble build bug is really reproduceble :-)

On Mon, Oct 19, 2015 at 10:31:37PM +0100, Chris West (Faux) wrote:
> Source: debmake-doc
> Version: 1.0-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:
> 
>   pybuild --test -i python{version} -p "3.5 3.4" --dir .
> I: pybuild base:170: cd 
> /debmake-doc-1.0/debhello-1.3-pkg1/test/debhello-1.3/.pybuild/pythonX.Y_3.5/build;
>  python3.5 -m unittest discover -v 
> hello_py (unittest.loader._FailedTest) ... ERROR
> 
> ==
> ERROR: hello_py (unittest.loader._FailedTest)
> --
> ImportError: Failed to import test module: hello_py
> Traceback (most recent call last):
>   File "/usr/lib/python3.5/unittest/loader.py", line 462, in _find_test_path
> package = self._get_module_from_name(name)
>   File "/usr/lib/python3.5/unittest/loader.py", line 369, in 
> _get_module_from_name
> __import__(name)
>   File 
> "/debmake-doc-1.0/debhello-1.3-pkg1/test/debhello-1.3/.pybuild/pythonX.Y_3.5/build/hello_py/__init__.py",
>  line 2, in 
> from gi.repository import Gtk
> ImportError: No module named 'gi'


I got the same with my local pbuilder build.  I wonder why I did not
catch this in the first place.

Anyway, adding python3-gi to B-D should fix this.  Thanks.

Osamu

Processed: reassign 801410 to java-policy

[Debian Bug Tracking System]

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

> reassign 801410 java-policy
Bug #801410 [java-common,java-policy] java-policy and java-common: error when 
trying to install together
Bug reassigned from package 'java-common,java-policy' to 'java-policy'.
No longer marked as found in versions java-policy/0.54, java-common/0.52, and 
java-common/0.52.1.
Ignoring request to alter fixed versions of bug #801410 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#802867: [Debian-med-packaging] Bug#802867: pyqi not running in python-biom-format build

[Tim Booth]

Hi Andreas,

> Well, "is not used" is interesting - but why is it called then and leads
> to an error?

It is called explicitly in debian/rules.  It may even have been me who
originally added the line.  It works for 2.1.4.

All it does is generate the BASH completions so I wouldn't call it
critical.  Heck, I don't even use BASH as my shell anyway.

> Do you think we should delay 2.1.5 and rather upload 2.1.4 until things
> are fully settled?

From my point of view, yes.  This module supports QIIME and I tested
QIIME with 2.1.4.  The fact that 2.1.5 has substantial changes makes me
suspicious.

TIM

Bug#802867: pyqi not running in python-biom-format build

[Andreas Tille]

Hi Tim,

On Tue, Oct 27, 2015 at 01:39:57PM +, Tim Booth wrote:
> Hi,
> 
> Regarding the error seen by Andreas:
> 
> "ImportError: No module named interfaces.optparse.config"
> 
> Line 84 of setup.py says:
> "pyqi is not used anymore in this project."
> 
> and this is also mentioned in the ChangeLog.md
> 
> So that explains the error.

Well, "is not used" is interesting - but why is it called then and leads
to an error?
 
> >From the looks of it this is a very significant change from 2.1.4 to
> 2.1.5 with other things aside from PyQi.  The minor change in version
> number is misleading!

Do you think we should delay 2.1.5 and rather upload 2.1.4 until things
are fully settled?

Kind regards

   Andreas. 

-- 
http://fam-tille.de

Bug#785833: New upstream version incoming

[Thibaut Girka]

A major upstream version is scheduled for early december.
Amongst other things, this version will switch to Python 3, Gtk 3 as well as
GStreamer 1.0.

I plan to package it shortly after it releases.

Best regards,
Thibaut Girka


signature.asc
Description: PGP signature

Bug#803161: mailman: /var/log/mailman/* world-readable by default, leaking sensitive list information

[Dominik George]

Package: mailman
Version: 1:2.1.18-2
Severity: critical
Tags: security
Justification: root security hole

The log files of mailman, residing in /var/lib/mailman/log and in
/var/log/mailman, and the log directory itself are created
world-readable by default. This discloses sensitive information about
list users, for example e-mail addresses and full names in the subscribe
log, to all unprivileged system users that have shell or filesystem
access.

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

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

Versions of packages mailman depends on:
ii  apache2 [httpd]  2.4.10-10+deb8u3
ii  apache2-mpm-prefork [httpd]  2.4.10-10+deb8u3
ii  apache2-mpm-worker [httpd]   2.4.10-10+deb8u3
ii  cron 3.0pl1-127+deb8u1
ii  debconf [debconf-2.0]1.5.56
ii  libc62.19-18+deb8u1
ii  logrotate3.8.7-1+b1
ii  lsb-base 4.1+Debian13+nmu1
ii  python-dnspython 1.12.0-1
pn  python:any   
ii  ucf  3.0030

Versions of packages mailman recommends:
ii  postfix [mail-transport-agent]  2.11.3-1

Versions of packages mailman suggests:
ii  listadmin 2.40-4
ii  lynx  2.8.9dev1-2+deb8u1
ii  spamassassin  3.4.0-6

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

-- debconf information excluded

Bug#802976: Should this package be removed?

[Thibaut Girka]

On Sun, Oct 25, 2015 at 09:22:53PM +0100, Moritz Mühlenhoff wrote:
> On Sun, Oct 25, 2015 at 07:51:20PM +0100, Thibaut Girka wrote:
> > On Sun, Oct 25, 2015 at 07:41:29PM +0100, Moritz Muehlenhoff wrote:
> > > Package: bluemindo
> > > Severity: serious
> > > 
> > > - Dead upstream (the current 0.3 release is from 2009)
> > 
> > A new major version is on the way and should be released soon.
> 
> Sounds good. Is there a rough timeline for that?

It should be released in early november.
As for the package itself, I might start working on it during the
next weekend or so.

Regards,
Thibaut Girka


signature.asc
Description: PGP signature

Bug#802867: pyqi not running in python-biom-format build

[Tim Booth]

Hi,

Regarding the error seen by Andreas:

"ImportError: No module named interfaces.optparse.config"

Line 84 of setup.py says:
"pyqi is not used anymore in this project."

and this is also mentioned in the ChangeLog.md

So that explains the error.

From the looks of it this is a very significant change from 2.1.4 to
2.1.5 with other things aside from PyQi.  The minor change in version
number is misleading!

TIM  

-- 
Tim Booth 

Centre for Ecology and Hydrology
Maclean Bldg, Benson Lane
Crowmarsh Gifford
Wallingford, England
OX10 8BB 

http://environmentalomics.org/bio-linux
+44 1491 69 2297



-- 
Tim Booth 

Centre for Ecology and Hydrology
Maclean Bldg, Benson Lane
Crowmarsh Gifford
Wallingford, England
OX10 8BB 

http://environmentalomics.org/bio-linux
+44 1491 69 2297

Bug#803145: [Debian-med-packaging] Bug#803145: opensurgsim: FTBFS: static assertion failed: THIS_METHOD_IS_ONLY_FOR_INNER_OR_LAZY_PRODUCTS

[Paul Novotny]

On Tue, 2015-10-27 at 11:20 +, Chris Lamb wrote:
> Source: opensurgsim
> Version: 0.6.0-3
> 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,
> 
> opensurgsim fails to build from source in unstable/amd64.
> 
> In file included from /usr/include/eigen3/Eigen/Core:297:0,
>  from
>  /build/opensurgsim-
> 0.6.0/SurgSim/Math/Quaternion.h:24,
>  from
>  /build/opensurgsim-
> 0.6.0/SurgSim/Collision/UnitTests/RepresentationUtilities.h:21,
>  from
>  /build/opensurgsim-
> 0.6.0/SurgSim/Collision/UnitTests/ContactCalculationTestsCommon.h:22,
>  from
>  /build/opensurgsim-
> 0.6.0/SurgSim/Collision/UnitTests/BoxPlaneContactCalculationTests.cpp
> :16:
> /usr/include/eigen3/Eigen/src/Core/Product.h: In instantiation of
> 'Eigen::ProductImpl::Scalar
> Eigen::ProductImpl::coeff(Eigen::Ind
> ex, Eigen::Index) const [with Lhs = Eigen::Matrix; Rhs
> =
> Eigen::Matrix; int Option = 0; Eigen::ProductImpl Rhs, Option, Eigen::Dense>::Scalar = double; Eigen::In
> dex = long int]':
> /usr/include/eigen3/Eigen/src/Geometry/Quaternion.h:749:31:   require
> d
> from 'static void Eigen::internal::quaternionbase_assign_impl 3,
> 3>::run(Eigen::QuaternionBase&, const
>  Other&) [with Derived = Eigen::Quaternion; Other =
>  Eigen::Product, Eigen::Matrix  3>, 0>]'
> /usr/include/eigen3/Eigen/src/Geometry/Quaternion.h:517:59:   require
> d
> from 'Derived& Eigen::QuaternionBase::operator=(const
> Eigen::MatrixBase&) [with OtherDerived = Eigen
> ::Product, Eigen::Matrix,
> 0>;
> Derived = Eigen::Quaternion]'
> /usr/include/eigen3/Eigen/src/Geometry/Quaternion.h:267:72:   require
> d
> from 'Eigen::Quaternion::Quaternion(const
> Eigen::MatrixBase&) [with Derived = Eigen::Product
> , Eigen::Matrix, 0>;
> _Scalar =
> double; int _Options = 0]'
> /build/opensurgsim-
> 0.6.0/SurgSim/Collision/UnitTests/BoxPlaneContactCalculationTests.cpp
> :135:72:
>   required from here
> /usr/include/eigen3/Eigen/src/Core/Product.h:203:7: error: static
> assertion failed: THIS_METHOD_IS_ONLY_FOR_INNER_OR_LAZY_PRODUCTS
>    EIGEN_STATIC_ASSERT(EnableCoeff,
>    THIS_METHOD_IS_ONLY_FOR_INNER_OR_LAZY_PRODUCTS);
>    ^
> SurgSim/Collision/UnitTests/CMakeFiles/SurgSimCollisionTest.dir/build
> .make:89:
> recipe for target
> 'SurgSim/Collision/UnitTests/CMakeFiles/SurgSimCollisionTest.dir/BoxD
> oubleSidedPlaneContactCalcul
> ationTests.cpp.o' failed
> 
> [..]
> 
> The full build log is attached or (an alternate build) can be viewed
> here:
> 
> https://reproducible.debian.net/logs/unstable/amd64/opensurgsim_0
> .6.0-3.build1.log.gz
> 

Thanks for the bug report, I believe this is due to the recent Eigen
update to 3.3-alpha1 in sid. I'll see what I can do. The likely
solution is to upgrade OpenSurgSim to a new release, which should come
out in a couple weeks.

-Paul

Bug#802665: augeas-lenses: httpd lens is broken in 1.2

[Dominic Cleal]

On 22/10/15 11:52, Erebus wrote:
> Package: augeas-lenses
> Version: 1.2.0-0.2
> Severity: serious
> Justification: httpd lens is broken in 1.2 
> 
> Dear Maintainer,
> 
> I have learned that augeas-lenses v1.2 includes a broken httpd lens. In
> particular, the 1.2 lens throws errors when an httpd config happens to end 
> with
> a comment. This is causing trouble for several other projects.
> 
> This issue is fixed in upstream version 1.4.
>
> See also: https://github.com/letsencrypt/letsencrypt/issues/981

Attached is a patch against upstream's Augeas 1.2.0 tarball to resolve
the issue reported on the letsencrypt issue when parsing ssl.conf.

-- 
Dominic Cleal
Red Hat Engineering
>From 875b63ce9c0eaa72fc1451697b18c60ba50b8165 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Rapha=C3=ABl=20Pinson?= 
Date: Tue, 11 Mar 2014 17:41:35 +0100
Subject: [PATCH] Httpd: Allow eol comments after section tags

(cherry picked from commit 3af5c7d44c838b52bbdaf1beb8780fd6a471a77e)

Httpd: Define an eol_comment in section to allow for \n before comment

(cherry picked from commit fb749ea4d1ba4ecd95a5cec6aa7b20b010ef04a8)

Httpd: Do not pass empty as body to section

This causes a conflict with eol_comment over newlines.
`empty` is just a generic part of `section`, not really a body.

(cherry picked from commit 97d3d931fefdfe816e6fb1d6e55a779742f255fa)

Httpd: Make \ illegal in char_arg_dir

Add tests to check non-recursive behaviour
of partial lenses

Fix #223

(cherry picked from commit 3df041be9196a8ca0b7a3e8c90a47b800500cba1)

Httpd: Properly manage eol after opening tag

Allow comments and empty lines after opening tag.

Fix #220

(cherry picked from commit 34980ae52bf4367664ad0551a15c2d1e5a3f2ac4)
---
 lenses/httpd.aug|  9 ---
 lenses/tests/test_httpd.aug | 62 +
 2 files changed, 68 insertions(+), 3 deletions(-)

diff --git a/lenses/httpd.aug b/lenses/httpd.aug
index caea9b6..331d807 100644
--- a/lenses/httpd.aug
+++ b/lenses/httpd.aug
@@ -59,7 +59,7 @@ let empty   = Util.empty_dos
 let indent  = Util.indent
 
 (* borrowed from shellvars.aug *)
-let char_arg_dir  = /[^ '"\t\r\n]|"|'/
+let char_arg_dir  = /[^\\ '"\t\r\n]|"|'/
 let char_arg_sec  = /[^ '"\t\r\n>]|"|'/
 let dquot = /"([^"\\\r\n]|.)*"/
 let squot = /'([^'\\\r\n]|.)*'/
@@ -77,13 +77,16 @@ let directive = [ indent . label "directive" . store word .
   (sep_spc . argv arg_dir)? . eol ]
 
 let section (body:lens) =
+(* opt_eol includes empty lines *)
+let opt_eol = del /([ \t]*#?\r?\n)*/ "\n" in
 let inner = (sep_spc . argv arg_sec)? . sep_osp .
- dels ">" . eol . body* . indent . dels "" . opt_eol . ((body|comment) . (body|empty|comment)*)? .
+ indent . dels "" ">" . eol ]
 
-let rec content = section (content|directive|comment|empty)
+let rec content = section (content|directive)
 
 let lns = (content|directive|comment|empty)*
 
diff --git a/lenses/tests/test_httpd.aug b/lenses/tests/test_httpd.aug
index af6cdc1..bed6cc6 100644
--- a/lenses/tests/test_httpd.aug
+++ b/lenses/tests/test_httpd.aug
@@ -1,5 +1,11 @@
 module Test_httpd =
 
+(* Check that we can iterate on directive *)
+let _ = Httpd.directive+
+
+(* Check that we can do a non iterative section *)
+let _ = Httpd.section Httpd.directive
+
 (* directives testing *)
 let d1 = "ServerRoot \"/etc/apache2\"\n"
 test Httpd.directive get d1 =
@@ -339,3 +345,59 @@ test Httpd.lns get conf2 =
 {  }
   }
 
+(* Eol comment *)
+test Httpd.lns get " # a comment
+MyDirective Foo
+\n" =
+  { "a"
+{ "#comment" = "a comment" }
+{ "directive" = "MyDirective" { "arg" = "Foo" } } }
+
+test Httpd.lns get "
+# a comment
+\n" =
+  { "a" { "#comment" = "a comment" } }
+
+(* GH #220 *)
+let double_comment = "
+##
+## Comment
+##
+\n"
+
+test Httpd.lns get double_comment =
+  { "IfDefine"
+{ "arg" = "Foo" }
+{ "#comment" = "#" }
+{ "#comment" = "# Comment" }
+{ "#comment" = "#" }
+  }
+
+let single_comment = "
+#
+## Comment
+##
+\n"
+
+test Httpd.lns get single_comment =
+  { "IfDefine"
+{ "arg" = "Foo" }
+{ "#comment" = "# Comment" }
+{ "#comment" = "#" }
+  }
+
+let single_empty = "
+#
+
+\n"
+test Httpd.lns get single_empty =
+  { "IfDefine"
+{ "arg" = "Foo" }
+  }
+
+let eol_empty = " #
+\n"
+test Httpd.lns get eol_empty =
+  { "IfDefine"
+{ "arg" = "Foo" }
+  }
-- 
2.4.3

Processed: Re: libqt5x11extras5: causes konsole to segfault in libX11 on startup

[Debian Bug Tracking System]

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

> package  libqt5x11extras5
Limiting to bugs with field 'package' containing at least one of 
'libqt5x11extras5'
Limit currently set to 'package':'libqt5x11extras5'

> severity  802811  critical
Bug #802811 [libqt5x11extras5] libqt5x11extras5: causes konsole to segfault in 
libX11 on startup
Severity set to 'critical' from 'important'
> stop
Stopping processing here.

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

Bug#803154: Does not build on hardened systems

[Klaus Ethgen]

Package: monitoring-plugins-basic
Version: 2.1.2-1
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)

I have only systems with hardened security settings like a /proc that do
not show not owned stuff to users. For this reason the /proc check in
control file fails and so do build.

See attached patch to fix that.

-- 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.0.7 (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 monitoring-plugins-basic depends on:
ii  iputils-ping   3:20121221-5+b2
ii  libc6  2.19-22
ii  libssl1.0.01.0.2d-1
ii  monitoring-plugins-common  2.1.2-1
ii  procps 2:3.3.10-4
ii  ucf3.0030

Versions of packages monitoring-plugins-basic recommends:
ii  libcap2-bin  1:2.24-12

Versions of packages monitoring-plugins-basic suggests:
pn  icinga | icinga | nagios3  

-- no debconf information

-- 
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
commit 8aef581146a792933ec4da3d22d12f3f8aaef980
Author: Klaus Ethgen 
Date:   Tue Oct 27 13:13:01 2015 +0100

Fix /proc check on systems that have hardened system

diff --git a/debian/rules b/debian/rules
index c6cd1fc..902074e 100755
--- a/debian/rules
+++ b/debian/rules
@@ -69,7 +69,7 @@ config.status: configure
 	
 	# if /proc is not mounted, check_nagios and check_procs are
 	# silently omitted from build.
-	@if ! [ -d /proc/1 ]; then \
+	@if ! [ -d /proc/ ]; then \
 	  echo "monitoring-plugins needs a mounted /proc to correctly build"; \
 	  exit 1; \
 	fi


signature.asc
Description: PGP signature

Bug#802155: marked as done (versiontools: FTBFS: FAIL: test_not_found (versiontools.tests.HandleVersionTests))

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2015 12:19:04 +
with message-id 
and subject line Bug#802155: fixed in versiontools 1.9.1-1.1
has caused the Debian Bug report #802155,
regarding versiontools: FTBFS: FAIL: test_not_found 
(versiontools.tests.HandleVersionTests)
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.)


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

test_formatting_without_vcs 
(versiontools.tests.VersionFormattingTestsWithMockedVCS) ... ok

==
FAIL: test_not_found (versiontools.tests.HandleVersionTests)
--
Traceback (most recent call last):
  File "/versiontools-1.9.1/versiontools/__init__.py", line 241, in 
from_expression
version = getattr(obj, identifier)
AttributeError: module 'versiontools' has no attribute '__nonexisting__'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/versiontools-1.9.1/versiontools/setuptools_hooks.py", line 64, in 
version
version = Version.from_expression(value)
ValueError: Unable to access '__nonexisting__' in 'versiontools': module 
'versiontools' has no attribute '__nonexisting__'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/versiontools-1.9.1/versiontools/tests.py", line 147, in test_not_found
handle_version(self.dist, None, version)
distutils.errors.DistutilsSetupError: Unable to access '__nonexisting__' in 
'versiontools': module 'versiontools' has no attribute '__nonexisting__'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/versiontools-1.9.1/versiontools/tests.py", line 151, in test_not_found
self.assertEqual(str(e), "Unable to access '__nonexisting__' in "
AssertionError: "Unab[44 chars]ols': module 'versiontools' has no attribute 
'__nonexisting__'" != "Unab[44 chars]ols': 'module' object has no attribute 
'__nonexisting__'"
- Unable to access '__nonexisting__' in 'versiontools': module 'versiontools' 
has no attribute '__nonexisting__'
? - ^ ^ -
+ Unable to access '__nonexisting__' in 'versiontools': 'module' object has no 
attribute '__nonexisting__'
?   +    ^


--
Ran 16 tests in 0.025s

FAILED (failures=1)
E: pybuild pybuild:262: test: plugin distutils failed with: exit code=1: 
python3.5 setup.py test 

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

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: versiontools
Source-Version: 1.9.1-1.1

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

Debian distribution maintenance software
pp.
Neil Williams  (supplier of updated versiontools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 25 Oct 2015 12:06:40 +
Source: versiontools
Binary: python-versiontools python3-versiontools
Architecture: source all
Version: 1.9.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Benjamin Drung 
Changed-By: Neil Williams 
Description:
 python-versiontools - Smart replacement for plain tuple used in __version__ 
(Python 2)
 python3-versiontools - Smart replacement for plain tuple used in __version__ 
(Python 3)
Closes: 802155
Changes:
 versiontools (1.9.1-

Bug#802071: marked as done (gnucash-docs: FTBFS: /tmp/buildd/gnucash-docs-2.6.7/mincho.xml (No such file or directory))

[Debian Bug Tracking System]

Your message dated Tue, 27 Oct 2015 11:34:08 +
with message-id 
and subject line Bug#802071: fixed in gnucash-docs 2.6.9-1
has caused the Debian Bug report #802071,
regarding gnucash-docs: FTBFS: /tmp/buildd/gnucash-docs-2.6.7/mincho.xml (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.)


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

[ERROR] FOUserAgent - Image not found. URI: 
http://docbook.sourceforge.net/release/images/draft.png. (See position 2:22048)
[ERROR] LazyFont - Failed to read font metrics file mincho.xml 
java.io.FileNotFoundException: /gnucash-docs-2.6.7/mincho.xml (No 
such file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.(FileInputStream.java:146)
at java.io.FileInputStream.(FileInputStream.java:101)
at 
sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90)
at 
sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:188)
at java.net.URL.openStream(URL.java:1041)
at 
org.apache.fop.apps.io.ResourceResolverFactory$NormalResourceResolver.getResource(ResourceResolverFactory.java:224)
at 
org.apache.fop.apps.io.ResourceResolverFactory$TempAwareResourceResolver.getResource(ResourceResolverFactory.java:152)
at 
org.apache.fop.apps.io.ResourceResolverFactory$DefaultResourceResolver.getResource(ResourceResolverFactory.java:121)
at 
org.apache.fop.apps.io.InternalResourceResolver.getResource(InternalResourceResolver.java:92)
at org.apache.fop.fonts.LazyFont.load(LazyFont.java:102)
at org.apache.fop.fonts.LazyFont.getAscender(LazyFont.java:233)
at org.apache.fop.fonts.Font.getAscender(Font.java:118)
at 
org.apache.fop.layoutmgr.BlockLayoutManager.initialize(BlockLayoutManager.java:82)
at 
org.apache.fop.layoutmgr.AbstractLayoutManager.getChildLM(AbstractLayoutManager.java:118)
at 
org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:108)
at 
org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:69)
at 
org.apache.fop.layoutmgr.PageBreaker.getNextKnuthElements(PageBreaker.java:252)
at 
org.apache.fop.layoutmgr.AbstractBreaker.getNextBlockList(AbstractBreaker.java:643)
at 
org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:178)
at 
org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:158)
at 
org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.java:384)
at org.apache.fop.layoutmgr.PageBreaker.doLayout(PageBreaker.java:112)
at 
org.apache.fop.layoutmgr.PageSequenceLayoutManager.activateLayout(PageSequenceLayoutManager.java:138)
at 
org.apache.fop.area.AreaTreeHandler.endPageSequence(AreaTreeHandler.java:267)
at 
org.apache.fop.fo.pagination.PageSequence.endOfNode(PageSequence.java:130)
at 
org.apache.fop.fo.FOTreeBuilder$MainFOHandler.endElement(FOTreeBuilder.java:360)
at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:190)
at 
org.apache.xalan.transformer.TransformerIdentityImpl.endElement(TransformerIdentityImpl.java:1102)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown 
Source)
at org.apache.xerces.xinclude.XIncludeHandler.endElement(Unknown Source)
at 
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
at 
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
 Source)
at 
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown 
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown 
Source)
at 
org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentit

Processed: this is really a bug in dh-exec

[Debian Bug Tracking System]

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

> reassign 803141 dh-exec
Bug #803141 [src:telegnome] telegnome: FTBFS: cp: cannot stat 
'debian/tmp/debian/tmp/dh-exec.395JP73r/etc/gnome/config/telegnome': No such 
file or directory
Bug reassigned from package 'src:telegnome' to 'dh-exec'.
No longer marked as found in versions telegnome/0.1.1-9.
Ignoring request to alter fixed versions of bug #803141 to the same values 
previously set
> forcemerge 802034 803141
Bug #802034 [dh-exec] mb2md: FTBFS: dh_install failure
Bug #802068 [dh-exec] dphys-config: FTBFS: cp: cannot stat 
'debian/tmp/debian/tmp/dh-exec.lZEHcJBh/etc/dphys-config': No such file or 
directory
Bug #803141 [dh-exec] telegnome: FTBFS: cp: cannot stat 
'debian/tmp/debian/tmp/dh-exec.395JP73r/etc/gnome/config/telegnome': No such 
file or directory
Added indication that 803141 affects 
telegnome,src:dphys-config,src:mb2md,mb2md,dphys-config
Added tag(s) sid.
Bug #802068 [dh-exec] dphys-config: FTBFS: cp: cannot stat 
'debian/tmp/debian/tmp/dh-exec.lZEHcJBh/etc/dphys-config': No such file or 
directory
Removed indication that 802068 affects telegnome, src:mb2md, src:dphys-config, 
dphys-config, and mb2md
Added indication that 802068 affects 
telegnome,src:dphys-config,src:mb2md,mb2md,dphys-config
Removed indication that 802034 affects telegnome, src:mb2md, dphys-config, 
src:dphys-config, and mb2md
Added indication that 802034 affects 
telegnome,src:dphys-config,src:mb2md,mb2md,dphys-config
Merged 802034 802068 803141
> affects 802034 telegnome
Bug #802034 [dh-exec] mb2md: FTBFS: dh_install failure
Bug #802068 [dh-exec] dphys-config: FTBFS: cp: cannot stat 
'debian/tmp/debian/tmp/dh-exec.lZEHcJBh/etc/dphys-config': No such file or 
directory
Bug #803141 [dh-exec] telegnome: FTBFS: cp: cannot stat 
'debian/tmp/debian/tmp/dh-exec.395JP73r/etc/gnome/config/telegnome': No such 
file or directory
Ignoring request to set affects of bug 802034 to the same value previously set
Ignoring request to set affects of bug 802068 to the same value previously set
Ignoring request to set affects of bug 803141 to the same value previously set
> retitle 802034 dh-exec: can't deal with plain d/install anymore
Bug #802034 [dh-exec] mb2md: FTBFS: dh_install failure
Bug #802068 [dh-exec] dphys-config: FTBFS: cp: cannot stat 
'debian/tmp/debian/tmp/dh-exec.lZEHcJBh/etc/dphys-config': No such file or 
directory
Bug #803141 [dh-exec] telegnome: FTBFS: cp: cannot stat 
'debian/tmp/debian/tmp/dh-exec.395JP73r/etc/gnome/config/telegnome': No such 
file or directory
Changed Bug title to 'dh-exec: can't deal with plain d/install anymore' from 
'mb2md: FTBFS: dh_install failure'
Changed Bug title to 'dh-exec: can't deal with plain d/install anymore' from 
'dphys-config: FTBFS: cp: cannot stat 
'debian/tmp/debian/tmp/dh-exec.lZEHcJBh/etc/dphys-config': No such file or 
directory'
Changed Bug title to 'dh-exec: can't deal with plain d/install anymore' from 
'telegnome: FTBFS: cp: cannot stat 
'debian/tmp/debian/tmp/dh-exec.395JP73r/etc/gnome/config/telegnome': No such 
file or directory'
> --
Stopping processing here.

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

Bug#803145: opensurgsim: FTBFS: static assertion failed: THIS_METHOD_IS_ONLY_FOR_INNER_OR_LAZY_PRODUCTS

[Chris Lamb]

Source: opensurgsim
Version: 0.6.0-3
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,

opensurgsim fails to build from source in unstable/amd64.

In file included from /usr/include/eigen3/Eigen/Core:297:0,
 from
 /build/opensurgsim-0.6.0/SurgSim/Math/Quaternion.h:24,
 from
 
/build/opensurgsim-0.6.0/SurgSim/Collision/UnitTests/RepresentationUtilities.h:21,
 from
 
/build/opensurgsim-0.6.0/SurgSim/Collision/UnitTests/ContactCalculationTestsCommon.h:22,
 from
 
/build/opensurgsim-0.6.0/SurgSim/Collision/UnitTests/BoxPlaneContactCalculationTests.cpp:16:
/usr/include/eigen3/Eigen/src/Core/Product.h: In instantiation of
'Eigen::ProductImpl::Scalar
Eigen::ProductImpl::coeff(Eigen::Ind
ex, Eigen::Index) const [with Lhs = Eigen::Matrix; Rhs =
Eigen::Matrix; int Option = 0; Eigen::ProductImpl::Scalar = double; Eigen::In
dex = long int]':
/usr/include/eigen3/Eigen/src/Geometry/Quaternion.h:749:31:   required
from 'static void Eigen::internal::quaternionbase_assign_impl::run(Eigen::QuaternionBase&, const
 Other&) [with Derived = Eigen::Quaternion; Other =
 Eigen::Product, Eigen::Matrix, 0>]'
/usr/include/eigen3/Eigen/src/Geometry/Quaternion.h:517:59:   required
from 'Derived& Eigen::QuaternionBase::operator=(const
Eigen::MatrixBase&) [with OtherDerived = Eigen
::Product, Eigen::Matrix, 0>;
Derived = Eigen::Quaternion]'
/usr/include/eigen3/Eigen/src/Geometry/Quaternion.h:267:72:   required
from 'Eigen::Quaternion::Quaternion(const
Eigen::MatrixBase&) [with Derived = Eigen::Product
, Eigen::Matrix, 0>; _Scalar =
double; int _Options = 0]'
/build/opensurgsim-0.6.0/SurgSim/Collision/UnitTests/BoxPlaneContactCalculationTests.cpp:135:72:
  required from here
/usr/include/eigen3/Eigen/src/Core/Product.h:203:7: error: static
assertion failed: THIS_METHOD_IS_ONLY_FOR_INNER_OR_LAZY_PRODUCTS
   EIGEN_STATIC_ASSERT(EnableCoeff,
   THIS_METHOD_IS_ONLY_FOR_INNER_OR_LAZY_PRODUCTS);
   ^
SurgSim/Collision/UnitTests/CMakeFiles/SurgSimCollisionTest.dir/build.make:89:
recipe for target
'SurgSim/Collision/UnitTests/CMakeFiles/SurgSimCollisionTest.dir/BoxDoubleSidedPlaneContactCalcul
ationTests.cpp.o' failed

[..]

The full build log is attached or (an alternate build) can be viewed
here:


https://reproducible.debian.net/logs/unstable/amd64/opensurgsim_0.6.0-3.build1.log.gz


Regards,

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


opensurgsim.0.6.0-3.unstable.amd64.log.txt.gz
Description: application/gzip