Bug#800289: marked as done (ipcheck: Please migrate a supported debhelper compat level)

[Debian Bug Tracking System]

Your message dated Sat, 15 Oct 2016 05:21:56 +
with message-id 
and subject line Bug#800289: fixed in ipcheck 0.233-2
has caused the Debian Bug report #800289,
regarding ipcheck: Please migrate a supported debhelper compat level
to be marked as done.

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

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


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

Hi,

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

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

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

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

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

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

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

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: ipcheck
Source-Version: 0.233-2

We believe that the bug you reported is fixed in the latest version of
ipcheck, 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.
Joao Eriberto Mota Filho  (supplier of updated ipcheck 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 14 Oct 2016 21:14:27 -0300
Source: ipcheck
Binary: ipcheck
Architecture: source
Version: 0.233-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Joao Eriberto Mota Filho 
Description:
 ipcheck- Dyndns.org client to register your dynamic IP address
Closes: 391863 709807 800289 840798
Changes:
 ipcheck (0.233-2) unstable; urgency=medium
 .
   * QA upload. (Closes: #840798)
   * Set Debian QA Group as maintainer. (see #839971)
   * Migrations:
   - debian/copyright to 1.0 format.
   - debian/rules to new (reduced) format.
   - DebSrc to 3.0.
   - DH level to 10. (Closes: #800289)
   * Run wrap-and-sort.
   * debian/compat: created.
   * debian/control:
   - Added ${misc:Depends} variable to Depends field.
   - Added a missing comma in long description. (Closes: #709807)
   - Added the Homepage field.
   - Bumped Standards-Version to 3.9.8.
   - Moved the debhelper to Build-Depends field. (Closes: #391863)
   - Removed the (now) useless build dependency help2man.
   - Removed some spaces from EOF in long description.
   * debian/dirs: removed because the debian/install file already creates the
 necessary directory.
   * debian/doc-base: created to index a HTML file.
   * debian/docs: added to install the index.html.
   * debian/install: created to install files.
   * debian/manpage/: the new manpage, based in txt2man.
   * debian/manpages: created to install the manpage.
   * debian/patches/
   - 10_avoid-direct-changes.patch: added to avoid direct changes in
 upstream source code.
   - 20_remove-logo.patch: added to remove a SF logo to avoid a potential
 privacy breach.
   * debian/watch: added a fake site to explain about the current status of the
 original 

Bug#840806: libgd2: invalid read in gdImageCreateFromTiffPtr()

[Salvatore Bonaccorso]

Source: libgd2
Version: 2.1.0-5
Severity: grave
Tags: security upstream patch
Control: fixed -1 2.1.0-5+deb8u7

For tracking the isssue.

DSA-3693-1 included the patch
0020-Fix-invalid-read-in-gdImageCreateFromTiffPtr.patch to fix:

> Subject: Fix invalid read in gdImageCreateFromTiffPtr()

with patch included in the 2.1.0-5+deb8u7 upload.

Regards,
Salvatore

Processed: libgd2: invalid read in gdImageCreateFromTiffPtr()

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 2.1.0-5+deb8u7
Bug #840806 [src:libgd2] libgd2: invalid read in gdImageCreateFromTiffPtr()
Marked as fixed in versions libgd2/2.1.0-5+deb8u7.

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

Processed: libgd2: Stack Buffer Overflow in GD dynamicGetbuf

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 2.1.0-5+deb8u7
Bug #840805 [src:libgd2] libgd2: Stack Buffer Overflow in GD dynamicGetbuf
Marked as fixed in versions libgd2/2.1.0-5+deb8u7.

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

Bug#840805: libgd2: Stack Buffer Overflow in GD dynamicGetbuf

[Salvatore Bonaccorso]

Source: libgd2
Version: 2.1.0-5
Severity: grave
Tags: security upstream
Control: fixed -1 2.1.0-5+deb8u7

For tracking this issue. DSA-3693-1 included the
0019-Patch-for-security-bug-https-bugs.php.net-bug.php-id.patch patch
fixing a stack buffer overflow in dynamicGetbuf as per upstream commit
https://github.com/libgd/libgd/commit/53110871935244816bbb9d131da0bccff734bfe9

Reference: PHP Bug: https://bugs.php.net/bug.php?id=73280

CVE requested at:
http://www.openwall.com/lists/oss-security/2016/10/15/1

Regards,
Salvatore

Processed: found 839659 in 2.1.0-5, fixed 839659 in 2.1.0-5+deb8u7

[Debian Bug Tracking System]

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

> found 839659 2.1.0-5
Bug #839659 [src:libgd2] libgd2: CVE-2016-7568: Integer overflow in 
gdImageWebpCtx
Ignoring request to alter found versions of bug #839659 to the same values 
previously set
> # fixed in DSA-3693-1
> fixed 839659 2.1.0-5+deb8u7
Bug #839659 [src:libgd2] libgd2: CVE-2016-7568: Integer overflow in 
gdImageWebpCtx
Marked as fixed in versions libgd2/2.1.0-5+deb8u7.
> thanks
Stopping processing here.

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

Bug#840546: CVE-2016-7966 kdepimlibs jessie

[Salvatore Bonaccorso]

Hi Sandro,

On Fri, Oct 14, 2016 at 10:56:00PM +0200, Sandro Knauß wrote:
> Hi,
> 
> now I'm fully confused - you said on IRC, I should better create a deb8u2 
> ontop.  Well I created now the debdiff for a deb8u2.
> 
> So you can decide what is the best way for the sec team and what version 
> should be uploaded where.

Sorry then if some confusion was present. I looked at the debdiff you
sent previously and it was a +deb8u1 with all changes. That would not
have worked, since +deb8u1 is now already on security master and been
rejected by dak.

> diff -Nru kdepimlibs-4.14.2/debian/changelog 
> kdepimlibs-4.14.2/debian/changelog
> --- kdepimlibs-4.14.2/debian/changelog2016-10-12 18:20:26.0 
> +0200
> +++ kdepimlibs-4.14.2/debian/changelog2016-10-14 21:33:53.0 
> +0200
> @@ -1,3 +1,14 @@
> +kdepimlibs (4:4.14.2-2+deb8u2) jessie-security; urgency=high
> +
> +  * Team upload.
> +  * Additional patch to complete the fix for CVE-2016-7966
> +- Replace all scary charactars (", <, > and &) with safe HTML
> +  replacements.
> +- Backport commit kcoreaddons 5e13d2439dbf540fdc840f0b0ab5b3ebf6642c6a
> +  in debian/patches/CVE-2016-7966_part2.diff
> +
> + -- Sandro Knauß   Fri, 14 Oct 2016 21:33:53 +0200
> +

Thanks, that is exactly what I meant. Create a +deb8u2 with your
additional needed fixes on top of the deb8u1 previously already
uploaded by Scott.

It's perfect now as you attached above.

I will now no furhter interfere, since Moritz will take care of the
DSA.

Regards,
Salvatore

Bug#840481: marked as done (Singular4: readline migration: piping error)

[Debian Bug Tracking System]

Your message dated Sat, 15 Oct 2016 04:32:06 +
with message-id 
and subject line Bug#840481: fixed in singular 4.0.3-p3+ds-2
has caused the Debian Bug report #840481,
regarding Singular4: readline migration: piping error
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.)


-- 
840481: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840481
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: singular-ui
Version: 4.0.3-p3+ds-1
Severity: important

Dear Maintainer,

Some extra Sagemath test cases are failing since we upgraded to Singular 4;
minimal test case:

$ echo '12345*54321;' | Singular
[ fails spectacularly ]

but it works if you run `Singular` and type it in manually. Presumably the pipe
version also worked with Singular 3 before.

X

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

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

Versions of packages singular-ui depends on:
ii  libc6   2.24-3
ii  libflint-2.5.2  2.5.2-9
ii  libgcc1 1:6.1.1-11
ii  libgmp102:6.1.1+dfsg-1
ii  libmpfr43.1.5-1
ii  libntl279.9.1-3
ii  libreadline77.0-1
ii  libsingular44.0.3-p3+ds-1
ii  libstdc++6  6.1.1-11
ii  libtinfo5   6.0+20160917-1
ii  singular-data   4.0.3-p3+ds-1

Versions of packages singular-ui recommends:
ii  singular-modules  4.0.3-p3+ds-1

Versions of packages singular-ui suggests:
pn  singular-doc  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: singular
Source-Version: 4.0.3-p3+ds-2

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

Debian distribution maintenance software
pp.
Jerome Benoit  (supplier of updated singular package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 14 Oct 2016 22:41:33 +
Source: singular
Binary: singular libsingular4 libsingular4-dev libsingular4-dev-common 
singular-modules singular-data singular-ui singular-ui-emacs singular-ui-xterm 
singular-doc singular-dev-doc
Architecture: source
Version: 4.0.3-p3+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jerome Benoit 
Description:
 libsingular4 - Computer Algebra System for Polynomial Computations -- library 
pa
 libsingular4-dev - Computer Algebra System for Polynomial Computations -- 
developmen
 libsingular4-dev-common - Computer Algebra System for Polynomial Computations 
-- common dev
 singular   - Computer Algebra System for Polynomial Computations
 singular-data - Computer Algebra System for Polynomial Computations -- shared 
dat
 singular-dev-doc - Computer Algebra System for Polynomial Computations -- 
developer
 singular-doc - Computer Algebra System for Polynomial Computations -- user 
docum
 singular-modules - Computer Algebra System for Polynomial Computations -- 
module pac
 singular-ui - Computer Algebra System for Polynomial Computations -- console us
 singular-ui-emacs - Computer Algebra System for Polynomial Computations -- 
emacs user
 singular-ui-xterm - Computer Algebra System for Polynomial Computations -- 
xterm user
Closes: 840481
Changes:
 singular (4.0.3-p3+ds-2) unstable; urgency=medium
 .
   * RC fix (Closes: #840481), fix readline 6 to 7 migration issue.
   * Debianization:
 - debian/rules, do not compress .hlp data files (for now).
Checksums-Sha1:
 94bb1f2e745e4656fbf56faa60ed6c95a0b01bd6 3580 singular_4.0.3-p3+ds-2.dsc
 b1ef06da9f5ac667aebbbf58813985d82cac3ffb 20980 
singular_4.0.3-p3+ds-2.debian.tar.xz
Checksums-Sha256:
 afa65a37cc6d977b8effdd065288590a675bcbf6604e38f55522cc90470ca154 3580 
singular_4.0.3-p3+ds-2.dsc
 

Bug#817514: kterm: diff for NMU version 6.2.0-46.2

[Joao Eriberto Mota Filho]

Control: tags 817514 + patch
Control: tags 817514 + pending

Dear maintainer,

I've prepared an NMU for kterm (versioned as 6.2.0-46.2) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards,

Eriberto

diff -u kterm-6.2.0/debian/changelog kterm-6.2.0/debian/changelog
--- kterm-6.2.0/debian/changelog
+++ kterm-6.2.0/debian/changelog
@@ -1,3 +1,14 @@
+kterm (6.2.0-46.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Bumped DH level to 10. (Closes: #817514)
+  * Run wrap-and-sort.
+  * debian/control:
+  - Added the ${misc:Depends} variable to Depends field.
+  - Bumped Standards-Version to 3.9.8.
+
+ -- Joao Eriberto Mota Filho   Fri, 14 Oct 2016 20:49:23 
-0300
+
 kterm (6.2.0-46.1) unstable; urgency=low
 
   * Non-maintainer upload.
diff -u kterm-6.2.0/debian/compat kterm-6.2.0/debian/compat
--- kterm-6.2.0/debian/compat
+++ kterm-6.2.0/debian/compat
@@ -1 +1 @@
-4
+10
diff -u kterm-6.2.0/debian/control kterm-6.2.0/debian/control
--- kterm-6.2.0/debian/control
+++ kterm-6.2.0/debian/control
@@ -2,12 +2,23 @@
 Section: x11
 Priority: extra
 Maintainer: ISHIKAWA Mutsumi 
-Build-Depends: libxaw7-dev, libxmu-dev, libxt-dev, libsm-dev, libice-dev, 
libxpm-dev, libxext-dev, libx11-dev, libncurses5-dev, debhelper (>= 4.9.1), 
xutils-dev (>= 1.0.2-2), m4
-Standards-Version: 3.6.1
+Build-Depends: debhelper (>= 10),
+   libice-dev,
+   libncurses5-dev,
+   libsm-dev,
+   libx11-dev,
+   libxaw7-dev,
+   libxext-dev,
+   libxmu-dev,
+   libxpm-dev,
+   libxt-dev,
+   m4,
+   xutils-dev (>= 1.0.2-2)
+Standards-Version: 3.9.8
 
 Package: kterm
 Architecture: any
-Depends: ${shlibs:Depends}, ncurses-term
+Depends: ncurses-term, ${shlibs:Depends}, ${misc:Depends}
 Recommends: locales (>= 2.1.94-2)
 Suggests: xfonts-shinonome | xfonts-a12k12
 Provides: x-terminal-emulator
diff -u kterm-6.2.0/debian/copyright kterm-6.2.0/debian/copyright
--- kterm-6.2.0/debian/copyright
+++ kterm-6.2.0/debian/copyright
@@ -35,13 +35,13 @@
 
 All Rights Reserved
 
-Permission to use, copy, modify, and distribute this software and its 
-documentation for any purpose and without fee is hereby granted, 
+Permission to use, copy, modify, and distribute this software and its
+documentation for any purpose and without fee is hereby granted,
 provided that the above copyright notice appear in all copies and that
-both that copyright notice and this permission notice appear in 
-supporting documentation, and that the name of Digital not be used in 
-advertising or publicity pertaining to distribution of the software 
-without specific, written prior permission.  
+both that copyright notice and this permission notice appear in
+supporting documentation, and that the name of Digital not be used in
+advertising or publicity pertaining to distribution of the software
+without specific, written prior permission.
 
 DIGITAL DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING
 ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL
diff -u kterm-6.2.0/debian/dirs kterm-6.2.0/debian/dirs
--- kterm-6.2.0/debian/dirs
+++ kterm-6.2.0/debian/dirs
@@ -1,4 +1,4 @@
+etc/X11/ja_JP.eucJP/app-defaults
 usr/bin
-usr/share/man/man1
 usr/share/man/ja/man1
-etc/X11/ja_JP.eucJP/app-defaults
+usr/share/man/man1

Processed: kterm: diff for NMU version 6.2.0-46.2

[Debian Bug Tracking System]

Processing control commands:

> tags 817514 + patch
Bug #817514 [src:kterm] kterm: Removal of debhelper compat 4
Added tag(s) patch.
> tags 817514 + pending
Bug #817514 [src:kterm] kterm: Removal of debhelper compat 4
Added tag(s) pending.

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

Bug#835360: rkt: FTBFS on several architectures

[Dmitry Smirnov]

On Friday, 14 October 2016 5:24:53 PM AEDT Andreas Henriksson wrote:
> (Despite this debdiff, asking for removal could possibly be a better
> idea as there's obviously not enough backing to properly support ppc64le
> right now and thus probably not for the lifetime of stretch.)

Andreas, thank you so much for testing. If not too much troubles could you 
please request removal of affected packages on all failing architectures?

Thank you and apologies for not handling removal myself...

-- 
Regards,
 Dmitry Smirnov.

---

If liberty means anything at all, it means the right to tell people what
they do not want to hear.
-- George Orwell


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

Bug#840761: marked as done (python-opcua: FTBFS (ImportError: No module named setuptools))

[Debian Bug Tracking System]

Your message dated Fri, 14 Oct 2016 22:47:09 +
with message-id 
and subject line Bug#840761: fixed in python-opcua 0.10.17-2
has caused the Debian Bug report #840761,
regarding python-opcua: FTBFS (ImportError: No module named setuptools)
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.)


-- 
840761: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840761
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-opcua
Version: 0.10.17-1
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 dpkg-source --before-build python-opcua-0.10.17
 fakeroot debian/rules clean
dh clean --buildsystem=pybuild --with python2,python3
   dh_testdir -O--buildsystem=pybuild
   dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py clean 
Traceback (most recent call last):
  File "setup.py", line 1, in 
from setuptools import setup, find_packages
ImportError: No module named setuptools
E: pybuild pybuild:276: clean: plugin distutils failed with: exit code=1: 
python2.7 setup.py clean 
dh_auto_clean: pybuild --clean -i python{version} -p 2.7 returned exit code 13
debian/rules:8: recipe for target 'clean' failed
make: *** [clean] Error 25
dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2


It is strongly recommended that packages are built in a clean sid chroot
to ensure that they are buildable (i.e. no missing build-dependencies).

Thanks.
--- End Message ---
--- Begin Message ---
Source: python-opcua
Source-Version: 0.10.17-2

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

Debian distribution maintenance software
pp.
W. Martin Borgert  (supplier of updated python-opcua 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 14 Oct 2016 20:50:36 +
Source: python-opcua
Binary: python-opcua python3-opcua python-opcua-tools
Architecture: source all
Version: 0.10.17-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: W. Martin Borgert 
Description:
 python-opcua - Python XMPP (Jabber) Library Implementing Everything as a Plugin
 python-opcua-tools - Python OPC UA Library Implementing Everything as a Plugin
 python3-opcua - Python OPC UA Library Implementing Everything as a Plugin
Closes: 840761
Changes:
 python-opcua (0.10.17-2) unstable; urgency=medium
 .
   * Fix missing build-deps (Closes: #840761).
Checksums-Sha1:
 a4af9d50eed803684fd926389b295a2276c707ab 2278 python-opcua_0.10.17-2.dsc
 517b20e98518d696edd3faf22b1c3fd4f0ca8bcc 2216 
python-opcua_0.10.17-2.debian.tar.xz
 82ac4a1cb49e9a8f344526707785461393eba091 2598 
python-opcua-tools_0.10.17-2_all.deb
 7ea25f6563e2a90f2e76dccf343ffeae829071de 260892 python-opcua_0.10.17-2_all.deb
 6000c2126935c5c7d49881b56a8d1d549ef09537 260712 python3-opcua_0.10.17-2_all.deb
Checksums-Sha256:
 9739f620f281858c959f91fcdd6397388c4b88edd5865dd276041b951f70b53a 2278 
python-opcua_0.10.17-2.dsc
 4b5644f5026aa1fc8a5dd0023c6eebecc08138c4b3762e64c03a63da7da790c0 2216 
python-opcua_0.10.17-2.debian.tar.xz
 c44fb1e0fc6121fe6157dcf6dab8229a2cf48894680f95cfdb83ef2cbcfb498e 2598 
python-opcua-tools_0.10.17-2_all.deb
 1c2e2d56cd931a31119b9ebd8e0d0a3b682b283021f70f0897762bc27650db72 260892 
python-opcua_0.10.17-2_all.deb
 4732380d18cab1ce1fa1e356537885c6481113a3805e6c51d52e406e4c381b2a 260712 
python3-opcua_0.10.17-2_all.deb
Files:
 e8a280d44422aaa823b68f937ea79dc3 2278 python optional 
python-opcua_0.10.17-2.dsc
 215a796553716687a5c608fa404604f4 2216 python optional 
python-opcua_0.10.17-2.debian.tar.xz
 c52db0d82ad0c2b02ef4c82a98561e94 2598 python optional 

Bug#840382: [Pkg-samba-maint] Bug#840382: samba (2:4.4.6+dfsg-2) still crashes with libtevent0-0.31

[J Mo]

Confirmed fixed as of 2:4.4.6+dfsg-2. If there is any release after 
which, I have not teted.




On 10/14/2016 12:08 PM, Mathieu Parent wrote:

To the recipients:

Do you still have the problem when using latest packages from sid?

I cant' reproduce the problem anymore.

Thanks

Mathieu Parent

Bug#840789: ruby-gettext: FTBFS: Error: test_relative(TestToolsXGetText::TestReference): NoMethodError: undefined method `stub' for #

[Chris Lamb]

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

Dear Maintainer,

ruby-gettext fails to build from source in unstable/amd64:

  [..]

  Error: test_email(TestToolsMsgInit::TestTranslator::TestChanged): 
NoMethodError: undefined method `stub' for 
#
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:26:in
 `setup'
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:42:in
 `block (2 levels) in run'
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:41:in
 `chdir'
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:41:in
 `block in run'
  /usr/lib/ruby/2.3.0/tmpdir.rb:89:in `mktmpdir'
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:40:in
 `run'
  
===
  E
  
===
  Error: test_name(TestToolsMsgInit::TestTranslator::TestChanged): 
NoMethodError: undefined method `stub' for 
#
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:26:in
 `setup'
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:42:in
 `block (2 levels) in run'
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:41:in
 `chdir'
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:41:in
 `block in run'
  /usr/lib/ruby/2.3.0/tmpdir.rb:89:in `mktmpdir'
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:40:in
 `run'
  
===
  E
  
===
  Error: test_no_email(TestToolsMsgInit::TestTranslator::TestNotChanged): 
NoMethodError: undefined method `stub' for 
#
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:26:in
 `setup'
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:42:in
 `block (2 levels) in run'
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:41:in
 `chdir'
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:41:in
 `block in run'
  /usr/lib/ruby/2.3.0/tmpdir.rb:89:in `mktmpdir'
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:40:in
 `run'
  
===
  E
  
===
  Error: test_no_name(TestToolsMsgInit::TestTranslator::TestNotChanged): 
NoMethodError: undefined method `stub' for 
#
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:26:in
 `setup'
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:42:in
 `block (2 levels) in run'
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:41:in
 `chdir'
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:41:in
 `block in run'
  /usr/lib/ruby/2.3.0/tmpdir.rb:89:in `mktmpdir'
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:40:in
 `run'
  
===
  E
  
===
  Error: 
test_no_name_no_email(TestToolsMsgInit::TestTranslator::TestNotChanged): 
NoMethodError: undefined method `stub' for 
#
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:26:in
 `setup'
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:42:in
 `block (2 levels) in run'
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:41:in
 `chdir'
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:41:in
 `block in run'
  /usr/lib/ruby/2.3.0/tmpdir.rb:89:in `mktmpdir'

Bug#840761: marked as pending

[W . Martin Borgert]

tag 840761 pending
thanks

Hello,

Bug #840761 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-opcua.git;a=commitdiff;h=9c4f3eb

---
commit 9c4f3ebec1e00a582da134e3b21acf4353163011
Author: W. Martin Borgert 
Date:   Fri Oct 14 21:21:47 2016 +

prepare 0.10.17-2

diff --git a/debian/changelog b/debian/changelog
index dce5309..b761b97 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+python-opcua (0.10.17-2) unstable; urgency=medium
+
+  * Fix missing build-deps (Closes: #840761).
+
+ -- W. Martin Borgert   Fri, 14 Oct 2016 20:50:36 +
+
 python-opcua (0.10.17-1) unstable; urgency=medium
 
   * Initial upload (Closes: #839679).

Processed: Bug#840761 marked as pending

[Debian Bug Tracking System]

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

> tag 840761 pending
Bug #840761 [src:python-opcua] python-opcua: FTBFS (ImportError: No module 
named setuptools)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#805004: marked as done (clang-modernize-3.8: uninstallable in sid)

[Debian Bug Tracking System]

Your message dated Fri, 14 Oct 2016 23:59:34 +0300
with message-id <20161014205934.b77udo5fuoh36...@bunk.spdns.de>
and subject line clang-modernize-3.8 has been removed from unstable
has caused the Debian Bug report #805004,
regarding clang-modernize-3.8: uninstallable in sid
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.)


-- 
805004: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805004
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: clang-modernize-3.8
Version: 1:3.8~svn250696-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to install in
sid.

In order for the transitional package clang-modernize-3.8 to be useful,
it must be installable. Therefore the Breaks+Replaces in clang-tidy-3.8
must be versioned (<< 1:3.8~svn250696-1).


Andreas
--- End Message ---
--- Begin Message ---
clang-modernize-3.8 has been removed from unstable.

cu
Adrian

-- 

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

Bug#840691: libgs9: security update DSA-3691-1 breaks zathura, evince, ... in jessie

[Francesco Poli]

On Fri, 14 Oct 2016 06:47:47 +0200 Salvatore Bonaccorso wrote:

[...]
> Hi Francesco,

Hello Salvatore, thanks for your fast reply!

> 
> On Thu, Oct 13, 2016 at 11:56:22PM +0200, Francesco Poli (wintermute) wrote:
[...]
> > After the security update:
[...]
> > I was unable to use zathura or evince
[...]
> 
> This was indeed not spotted in my testing of the update for the DSA.
> The blame for this should solely go to myself (not the team). We
> should find the cause asap and find a fix. I can reproduce it with
> evince.

It's a relief that you are able to reproduce the bug (at least, I was
not seeing "ghosts"...).

I hope that a fix may be found and applied soon.

P.S.: Thanks for all the good job on the many security updates that
have been issued for a long time!


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


pgpx79gr2IyJQ.pgp
Description: PGP signature

Bug#840546: CVE-2016-7966 kdepimlibs jessie

[Sandro Knauß]

Hi,

now I'm fully confused - you said on IRC, I should better create a deb8u2 
ontop.  Well I created now the debdiff for a deb8u2.

So you can decide what is the best way for the sec team and what version 
should be uploaded where.

Best Regards,

sandro

--
Am Freitag, 14. Oktober 2016, 21:50:18 CEST schrieb Salvatore Bonaccorso:
> Hi,
> 
> Just an additional comment on the debdiff:
> 
> On Fri, Oct 14, 2016 at 08:23:04PM +0200, Sandro Knauß wrote:
> > Hey,
> > 
> > I now back ported the second part of the fix of the CVE. I updated the
> > version deb8u1 from Scott. Should I create a deb8u2 for the additional
> > patch?
> Please note, to build the attached debdiff instead as +deb8u2 on top
> of the +deb8u1 already present on security-master and just
> incoorporate the additional changes needed.
> 
> Regards and thanks for your work!
> 
> Salvatore

diff -Nru kdepimlibs-4.14.2/debian/changelog kdepimlibs-4.14.2/debian/changelog
--- kdepimlibs-4.14.2/debian/changelog	2016-10-12 18:20:26.0 +0200
+++ kdepimlibs-4.14.2/debian/changelog	2016-10-14 21:33:53.0 +0200
@@ -1,3 +1,14 @@
+kdepimlibs (4:4.14.2-2+deb8u2) jessie-security; urgency=high
+
+  * Team upload.
+  * Additional patch to complete the fix for CVE-2016-7966
+- Replace all scary charactars (", <, > and &) with safe HTML
+  replacements.
+- Backport commit kcoreaddons 5e13d2439dbf540fdc840f0b0ab5b3ebf6642c6a
+  in debian/patches/CVE-2016-7966_part2.diff
+
+ -- Sandro Knauß   Fri, 14 Oct 2016 21:33:53 +0200
+
 kdepimlibs (4:4.14.2-2+deb8u1) jessie-security; urgency=high
 
   * Team upload.
diff -Nru kdepimlibs-4.14.2/debian/patches/CVE-2016-7966_part2.diff kdepimlibs-4.14.2/debian/patches/CVE-2016-7966_part2.diff
--- kdepimlibs-4.14.2/debian/patches/CVE-2016-7966_part2.diff	1970-01-01 01:00:00.0 +0100
+++ kdepimlibs-4.14.2/debian/patches/CVE-2016-7966_part2.diff	2016-10-14 21:33:14.0 +0200
@@ -0,0 +1,27 @@
+--- a/kpimutils/linklocator.cpp
 b/kpimutils/linklocator.cpp
+@@ -389,7 +389,23 @@ QString LinkLocator::convertToHtml( cons
+ bool badUrl = false;
+ str = locator.getUrlAndCheckValidHref();
+ if (badUrl) {
+-return locator.mText;
++QString resultBadUrl;
++const int helperTextSize(locator.mText.count());
++for (int i = 0; i < helperTextSize; ++i) {
++const QChar chBadUrl = locator.mText[i];
++if (chBadUrl == QLatin1Char('&')) {
++resultBadUrl += QLatin1String("");
++} else if (chBadUrl == QLatin1Char('"')) {
++resultBadUrl += QLatin1String("");
++} else if (chBadUrl == QLatin1Char('<')) {
++resultBadUrl += QLatin1String("");
++} else if (chBadUrl == QLatin1Char('>')) {
++resultBadUrl += QLatin1String("");
++} else {
++resultBadUrl += chBadUrl;
++}
++}
++return resultBadUrl;
+ }
+ 
+ if ( !str.isEmpty() ) {
diff -Nru kdepimlibs-4.14.2/debian/patches/series kdepimlibs-4.14.2/debian/patches/series
--- kdepimlibs-4.14.2/debian/patches/series	2016-10-12 18:20:26.0 +0200
+++ kdepimlibs-4.14.2/debian/patches/series	2016-10-14 21:33:14.0 +0200
@@ -2,3 +2,4 @@
 sslv2_disabled.patch
 tlscancelled.patch
 CVE-2016-7966.diff
+CVE-2016-7966_part2.diff


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

Bug#840685: TOCTOU race condition in initscript on chown'ing JVM_TMP temporary directory (was: Re: Bug#840685: tomcat8: DSA-3670 incomplete)

[Salvatore Bonaccorso]

Control: severity -1 normal
Control: found -1 8.0.14-1

Hi  Paul,

On Sat, Oct 15, 2016 at 07:25:59AM +1100, paul.sz...@sydney.edu.au wrote:
> Dear Salvatore,
> 
> > You are operating here outside of /tmp (sticky world-writable
> > directory) which the above issue for the init scripts relies on,
> > right?  fs.protected_(hardlinks|symlinks) is exactly a hardening for
> > those issues:
> > https://www.kernel.org/doc/Documentation/sysctl/fs.txt
> 
> I see: the kernel now treats things in /tmp (with sticky bit
> permissions) differently from other places (without "weird"
> permissions). Thanks for pointing this out for me!
> (I never noticed this change...)
> 
> Then I agree that this issue is not exploitable in default Debian,
> no need for DSA. (Sorry about the noise.)

Welcome and thanks for confirming, and no problem (glad we could
elaborate together on the issue the impact).

I'm lowering the severity, and as well mark as found version for the
8.0.14-1 including up to unstable version. 

Regards,
Salvatore

Processed: Re: TOCTOU race condition in initscript on chown'ing JVM_TMP temporary directory (was: Re: Bug#840685: tomcat8: DSA-3670 incomplete)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #840685 [tomcat8] TOCTOU race condition in initscript on chown'ing JVM_TMP 
temporary directory
Severity set to 'normal' from 'critical'
> found -1 8.0.14-1
Bug #840685 [tomcat8] TOCTOU race condition in initscript on chown'ing JVM_TMP 
temporary directory
Marked as found in versions tomcat8/8.0.14-1.

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

Bug#840685: TOCTOU race condition in initscript on chown'ing JVM_TMP temporary directory (was: Re: Bug#840685: tomcat8: DSA-3670 incomplete)

[paul . szabo]

Dear Salvatore,

> You are operating here outside of /tmp (sticky world-writable
> directory) which the above issue for the init scripts relies on,
> right?  fs.protected_(hardlinks|symlinks) is exactly a hardening for
> those issues:
> https://www.kernel.org/doc/Documentation/sysctl/fs.txt

I see: the kernel now treats things in /tmp (with sticky bit
permissions) differently from other places (without "weird"
permissions). Thanks for pointing this out for me!
(I never noticed this change...)

Then I agree that this issue is not exploitable in default Debian,
no need for DSA. (Sorry about the noise.)

Cheers, Paul

Paul Szabo   p...@maths.usyd.edu.au   http://www.maths.usyd.edu.au/u/psz/
School of Mathematics and Statistics   University of SydneyAustralia

Bug#840298: [Pkg-samba-maint] Bug#840382: samba (2:4.4.6+dfsg-2) still crashes with libtevent0-0.31

[Ivan Sergio Borgonovo]

It seems to be fixed, thanks.

On 10/14/2016 09:08 PM, Mathieu Parent wrote:

To the recipients:

Do you still have the problem when using latest packages from sid?

I cant' reproduce the problem anymore.

Thanks

Mathieu Parent



--
Ivan Sergio Borgonovo
http://www.webthatworks.it http://www.borgonovo.net

Bug#839827: marked as done (freeimage: CVE-2016-5684)

[Debian Bug Tracking System]

Your message dated Fri, 14 Oct 2016 20:10:20 +
with message-id 
and subject line Bug#839827: fixed in freeimage 3.15.4-4.2+deb8u1
has caused the Debian Bug report #839827,
regarding freeimage: CVE-2016-5684
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.)


-- 
839827: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839827
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freeimage
Version: 3.17.0+ds1-2
Severity: grave
Tags: security upstream
Justification: user security hole

Hi,

the following vulnerability was published for freeimage.

CVE-2016-5684[0]:
XMP Image Handling Code Execution Vulnerability

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-5684

Please adjust the affected versions in the BTS as needed. Only sid has
been checked source wise in this case.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: freeimage
Source-Version: 3.15.4-4.2+deb8u1

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated freeimage 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, 11 Oct 2016 21:00:24 +0200
Source: freeimage
Binary: libfreeimage-dev libfreeimage3 libfreeimage3-dbg
Architecture: source
Version: 3.15.4-4.2+deb8u1
Distribution: jessie-security
Urgency: high
Maintainer: Debian QA Group 
Changed-By: Anton Gladky 
Description:
 libfreeimage-dev - Support library for graphics image formats (development 
files)
 libfreeimage3 - Support library for graphics image formats (library)
 libfreeimage3-dbg - Support library for graphics image formats (debugging 
symbols)
Closes: 786790 839827
Changes:
 freeimage (3.15.4-4.2+deb8u1) jessie-security; urgency=high
 .
   * [f51f898] Fix CVE-2015-3885: integer overflow in the ljpeg_start function
   (Closes: #786790)
   * [b2e0c3f] Fix CVE-2016-5864: apply patch from wheezy-security.
   Thanks to Salvatore Bonaccorso, Balint Reczey and Chris Lamb
   (Closes: #839827)
Checksums-Sha1:
 ea30cb74210f4e847c67cf6ef2c56c4f2a9d98df 2160 freeimage_3.15.4-4.2+deb8u1.dsc
 0a33537e32ad9bd4cf7b151a32de96905da27d3e 5768019 freeimage_3.15.4.orig.tar.gz
 3ce43cf089d11596f14ea34fbf79d60744305524 34200 
freeimage_3.15.4-4.2+deb8u1.debian.tar.xz
Checksums-Sha256:
 25905f9ec54630e38cfda93391f876779f5b6ff5c413b765e2537f788b61c375 2160 
freeimage_3.15.4-4.2+deb8u1.dsc
 f85b43e8bffda2b26b15a2d09242a77dd08ba17d7207ec2f18278163a29565d9 5768019 
freeimage_3.15.4.orig.tar.gz
 3099001958df24a48afaa4d4c4f913656de4d8ca8705cdb9d0846418cd14cb17 34200 
freeimage_3.15.4-4.2+deb8u1.debian.tar.xz
Files:
 6f12176255121ffc422cf4c67d9cdf6e 2160 libs optional 
freeimage_3.15.4-4.2+deb8u1.dsc
 a1164eb85ab51bda023328ec740a5679 5768019 libs optional 
freeimage_3.15.4.orig.tar.gz
 088bb33194e5b256e8f6a9bbb7805830 34200 libs optional 
freeimage_3.15.4-4.2+deb8u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJX/VVzAAoJENPhc4PPp/8GptcP/0PCO+rWGX6SF09UF8IvEzBB
pgKk+e3AYR+VdsMhVdHMVWytwMSOa5yGs+6ZZHZKOUV8JgA+4ohFINxZJ5Xpcfr6
kA53+g/L/r+WyOsXJTVdG1PDd9wOA5aLb4JV4lzxoo/lY6JS7oEYzSOC/PbLGZTp
TS+EF32lmo9JMjhYe5Nxr3qq5CuWCLBW3QadSfLQQoYnoxTD5Sxtn4aRzz8ocwpe
6U2cgGFuKez+1o6GpNrihV97pW9jKWPWXjA4+GCLG9Th9X9C7zgD3mx1yRmOhT5i
yDN8fXm3xxoLAI2etX5IuqMuCuKRRcB/Q3ypsKAkAxiUksND8UPpLb6C4q0AzepN
YMUCL3h27FFcwHViFRS3UOxiH5i6uJqHdRMqeIedG1qyNUnQv4c9QWOdOfnp+Kvi
oFT0f7XEwEOKVcl0L180Q702ZWqtVncMRkep/sxvd80Gog/ykPoT6bOa0i2qzJXd
yLXNHkAKYSbf3zz74zL/s65EE/qiiIAMdYMrD/LsGg7c2uz7V54Cw/VHneeMFsar
dNKnGUx4g2ZaX9LcxwCIaw0L8yflpFPLxQCcmcLQA7uEMollY2wpNeLXdvpSCE1U
DQC8l/hp8EHvHmhoq17V2vZn+5aJGLTYwbkOTzt1fi3QRycXnVs0y3FMl50K55uc
pqGHaAUYwuH4tcXPnh+p
=9+YY
-END PGP SIGNATURE End Message ---

Bug#840685: tomcat8: DSA-3670 incomplete

[paul . szabo]

Dear Markus,

Sorry to reply again.

> ... But there is another rm -rf "$JVM_TMP" command in the stop target
> that would remove your symlink again.

I now see what you mean. There is an rm when you "stop" tomcat, and
another in the "start"; so maybe there are two in restart. No matter:
I watch (with inotify), keep watch and keep watching, and put in a
symlink to /etc soon as I can, anytime and every time I can. So I will
create a symlink after the rm during stop, a wasted thing, present
between your stop and start; then during start you rm, I create the
symlink, you do the useless "mkdir -p" and you chown; I win.

For your test, you took the rm out of your script: you should see /etc
being chowned to tomcat8. Please confirm.

Cheers, Paul

Paul Szabo   p...@maths.usyd.edu.au   http://www.maths.usyd.edu.au/u/psz/
School of Mathematics and Statistics   University of SydneyAustralia

Bug#840546: CVE-2016-7966 kdepimlibs jessie

[Salvatore Bonaccorso]

Hi,

Just an additional comment on the debdiff:

On Fri, Oct 14, 2016 at 08:23:04PM +0200, Sandro Knauß wrote:
> Hey,
> 
> I now back ported the second part of the fix of the CVE. I updated the 
> version 
> deb8u1 from Scott. Should I create a deb8u2 for the additional patch?

Please note, to build the attached debdiff instead as +deb8u2 on top
of the +deb8u1 already present on security-master and just
incoorporate the additional changes needed.

Regards and thanks for your work!

Salvatore


signature.asc
Description: PGP signature

Bug#840685: TOCTOU race condition in initscript on chown'ing JVM_TMP temporary directory (was: Re: Bug#840685: tomcat8: DSA-3670 incomplete)

[Salvatore Bonaccorso]

Hi Paul,

Markus followed already up, I just want to give some additional
comments on the below:

On Fri, Oct 14, 2016 at 07:07:52PM +1100, paul.sz...@sydney.edu.au wrote:
> Dear Salvatore,
> 
> > ... if the attacher created a symlink between the rm and the mkdir
> > then mkdir will still fail with -p on a symlink.  (Or do I miss
> > something?). ...
> 
> Yes, you missed a simple test:
> 
> $ mkdir mydir
> $ ln -s mydir mylink
> $ ls -ld my*
> drwx-- 2 psz amstaff 4096 Oct 14 18:46 mydir
> lrwxrwxrwx 1 psz amstaff5 Oct 14 18:46 mylink -> mydir
> $ mkdir -p mylink || echo failed
> $ mkdir -p mylink; echo $?
> 0
> $ mkdir mylink || echo failed
> mkdir: cannot create directory `mylink': File exists
> failed
> $ mkdir mylink; echo $?
> mkdir: cannot create directory `mylink': File exists
> 1
> $ ls -ld my*
> drwx-- 2 psz amstaff 4096 Oct 14 18:46 mydir
> lrwxrwxrwx 1 psz amstaff5 Oct 14 18:46 mylink -> mydir
> $ 
> 
> showing that "mkdir -p" does not fail (but plain mkdir does).

You are doing all the tests with the same user. But yes mkdir -p will
succeed for the root user still in some cases. Let's recapitulate your
described attack. The attacker has shell-access on the tomcat8 running
host or by other mean can run code on the server by an unprivileged
user and used inotify to detect when $JVM_TMP will be removed.

Let's say the tomcat8 service is started.

JVM_TMP=/tmp/tomcat8-tomcat8-tmp

# rm -rf "$JVM_TMP".

With inotify the evil user detects, that /tmp/tomcat8-tomcat8-tmp got
removed and has several options for proceeding. Either create a
directory, or directly a malicious symlink. 

evil@jessie:~$ ln -s /etc/passwd /tmp/tomcat8-tomcat8-tmp
evil@jessie:~$ ls -l /tmp/tomcat8-tomcat8-tmp 
lrwxrwxrwx 1 evil evil 11 Oct 14 20:20 /tmp/tomcat8-tomcat8-tmp -> /etc/passwd
evil@jessie:~$

raced before root will issue the mkdir -p call:

root@jessie# mkdir -p /tmp/tomcat8-tomcat8-tmp 
mkdir: cannot create directory ‘/tmp/tomcat8-tomcat8-tmp’: File exists
root@jessie# echo $?
1
root@jessie#

if the evil user instead created a directory, then yes you are right
for that part:

evil@jessie$ mkdir -p /tmp/tomcat8-tomcat8-tmp
evil@jessie$ ls -ld /tmp/tomcat8-tomcat8-tmp
drwxr-xr-x 2 evil evil 4096 Oct 14 20:25 /tmp/tomcat8-tomcat8-tmp
evil@jessie$

followed by the root user

root@jessie# mkdir -p /tmp/tomcat8-tomcat8-tmp
root@jessie# echo $?
0
root@jessie#

If now the evil user wins again the race, and removes the directory in
time and replaces it with the symlink to a desired file to overwrite,
before the chown call of the root user:

evil@jessie$ rmdir /tmp/tomcat8-tomcat8-tmp
evil@jessie$ ln -s /etc/passwd /tmp/tomcat8-tomcat8-tmp
evil@jessie$ ls -l /tmp/tomcat8-tomcat8-tmp
lrwxrwxrwx 1 evil evil 11 Oct 14 20:28 /tmp/tomcat8-tomcat8-tmp -> /etc/passwd
evil@jessie$

root@jessie# chown tomcat8 /tmp/tomcat8-tomcat8-tmp
chown: cannot dereference ‘/tmp/tomcat8-tomcat8-tmp’: Permission denied
root@jessie# echo $?
1
root@jessie# ls -l /etc/passwd
-rw-r--r-- 1 root root 1631 Oct 14 20:07 /etc/passwd
root@jessie#

The same if the evil user created a symlink to a existing directory:

evil@jessie$ ln -sf /etc /tmp/tomcat8-tomcat8-tmp
evil@jessie$ ls -l /tmp/tomcat8-tomcat8-tmp
lrwxrwxrwx 1 evil evil 4 Oct 14 21:01 /tmp/tomcat8-tomcat8-tmp -> /etc
evil@jessie$

root@jessie# mkdir -p /tmp/tomcat8-tomcat8-tmp
mkdir: cannot create directory ‘/tmp/tomcat8-tomcat8-tmp’: File exists
root@jessie#

root@jessie# chown tomcat8 /tmp/tomcat8-tomcat8-tmp 
chown: cannot dereference ‘/tmp/tomcat8-tomcat8-tmp’: Permission denied
root@jessie#

because of the kernel hardening.

> > On the practicality for Debian systems though this is mitigated by the
> > Kernel hardenings which are enabled by default:
> > 
> > fs.protected_hardlinks=1
> > fs.protected_symlink=1
> > 
> > which will prevent that the target of the symlink in /tmp will be
> > changed on the chown call.
> 
> Another missing test (besides: who is changing anything?):
> 
> # grep . /proc/sys/fs/prot*
> /proc/sys/fs/protected_hardlinks:1
> /proc/sys/fs/protected_symlinks:1
> # cd ~psz
> # ls -ld my*
> drwx-- 2 psz amstaff 4096 Oct 14 18:46 mydir
> lrwxrwxrwx 1 psz amstaff5 Oct 14 18:46 mylink -> mydir
> # chown mike mylink
> # ls -ld my*
> drwx-- 2 mike amstaff 4096 Oct 14 18:46 mydir
> lrwxrwxrwx 1 psz  amstaff5 Oct 14 18:46 mylink -> mydir
> # 

You are operating here outside of /tmp (sticky world-writable
directory) which the above issue for the init scripts relies on,
right?  fs.protected_(hardlinks|symlinks) is exactly a hardening for
those issues:

https://www.kernel.org/doc/Documentation/sysctl/fs.txt
https://sources.debian.net/src/linux/3.16.36-1%2Bdeb8u1/Documentation/sysctl/fs.txt/#L205

In the release notes such issues are not treated as security-issues
anymore since:

https://www.debian.org/releases/stable/amd64/release-notes/ch-whats-new.en.html#security


> > So while I think it should be fixed, this would not warrant a DSA,
> > since 

Bug#840546: CVE-2016-7966 kdepimlibs jessie

[Moritz Muehlenhoff]

On Fri, Oct 14, 2016 at 08:23:04PM +0200, Sandro Knauß wrote:
> Hey,
> 
> I now back ported the second part of the fix of the CVE. I updated the 
> version 
> deb8u1 from Scott. Should I create a deb8u2 for the additional patch?
> 
> I attached the uptodate debdiff.

Thanks, please upload.

Cheers,
Moritz

Bug#840298: [Pkg-samba-maint] Bug#840382: samba (2:4.4.6+dfsg-2) still crashes with libtevent0-0.31

[Mathieu Parent]

To the recipients:

Do you still have the problem when using latest packages from sid?

I cant' reproduce the problem anymore.

Thanks

Mathieu Parent

Bug#840394: motif: FTBFS: relocation R_X86_64_PC32 against symbol ...

[Joachim Wiedorn]

Hello Graham,

Graham Inggs wrote on 2016-10-14 16:35:
> 
> PIE by default is happening for Stretch.
> Release Team have given the go-ahead, see message #21 of #835148 [1],
> and the changes have already been committed to SVN [2] and should be
> included in the next GCC6 upload.

Thank you for this information. I think, than the time is short for
some other packages which still have a problem with 'pie'. 

---
Have a nice day.

Joachim (Germany)


pgp8dNtYeBv69.pgp
Description: Digitale Signatur von OpenPGP

Bug#840685: tomcat8: DSA-3670 incomplete

[paul . szabo]

Dear Markus,

> First of all you can only gain write permissions as the tomcat8 user if
> you exploit an yet unknown security vulnerability in a web application
> or Tomcat itself. Debian's tomcat8 user has no shell access by default.

Yes, this is a privilege escalation issue: exactly as in DSA-3670.

> So the server must be running ...

No, you are wrong. Once I managed run-any-code-as-tomcat8 from the
running server, I set up something to run in the background, to keep
running after the server exited.

> ... and somehow you managed to remove /tmp/tomcat8-tomcat8-tmp and
> replaced the directory with a symlink to an arbitrary file.

No I do not remove anything. You do the remove, I create the symlink
after you removed (and before you attempt the mkdir).

> Your attack vector requires that the server must be restarted. ...

Yes, exactly as in DSA-3670.

> ... But there is another rm -rf "$JVM_TMP" command in the stop target
> that would remove your symlink again.

No, not another rm. I create the symlink after your rm.

> Ok, let's imagine that you could find a way around the rm -rf commands.
> Let's remove those rm -rf "$JVM_TMP" calls in /etc/init.d/tomcat8. Then
> run systemctl daemon-reload. Log in as tomcat8 user and create your
> symlink for /tmp/tomcat8-tomcat8-tmp. If I run systemctl restart tomcat8
> now, I get this:
> 
> Job for tomcat8.service failed because the control process exited with
> error code.
> 
> The symlink is still present and nothing has changed regarding the file
> permissions for my arbitrary file.

You created the wrong symlink: not to a random place and not to a file,
but a symlink to /etc (an existing directory). Please try again.

> I agree that we should improve the init script in this regard but I
> actually don't see a major risk like a root escalation for users at the
> moment and I suggest to lower the severity of this bug report to important.

Do the right test, please. You will see /etc owned by tomcat8, that
effectively gives root access.

>> What response time should I have expected of team@security? You had
>> close to a whole day...
> In my opinion it is generally understood that you should give people at
> least enough time to react to an e-mail and to assess the issue.
> Expecting a response time in less than a day is not very reasonable,
> especially when there are things like the time difference between
> Australia and Europe.

You can do better, if you try.

Cheers, Paul

Paul Szabo   p...@maths.usyd.edu.au   http://www.maths.usyd.edu.au/u/psz/
School of Mathematics and Statistics   University of SydneyAustralia

Processed: your mail

[Debian Bug Tracking System]

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

> submitter 840067 la...@debian.org
Bug #840067 {Done: Maximiliano Curia } [src:kscreen] kscreen: 
FTBFS: debug.h:24:25: fatal error: kscreen/log.h: No such file or directory
Changed Bug submitter to 'la...@debian.org' from 'Chris Lamb 
'.
> thanks
Stopping processing here.

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

Bug#840546: CVE-2016-7966 kdepimlibs jessie

[Sandro Knauß]

Hey,

I now back ported the second part of the fix of the CVE. I updated the version 
deb8u1 from Scott. Should I create a deb8u2 for the additional patch?

I attached the uptodate debdiff.
 
Regards,

sandro

Am Donnerstag, 13. Oktober 2016, 18:19:35 CEST schrieb Moritz Mühlenhoff:
> On Thu, Oct 13, 2016 at 12:15:01PM +0200, Sandro Knauß wrote:
> > Hey,
> > 
> > The description
> > https://www.kde.org/info/security/advisory-20161006-1.txt do not describe
> > all patches that are needed to fix the CVE (at the moment).
> > 
> > The additional patches are not part of KDE Frameworks 5.27, so they need
> > to be applied for KF 5.27:
> > 5e13d2439dbf540fdc840f0b0ab5b3ebf6642c6a (0004-Display-bad-url.patch)
> > a06cef31cc4c908bc9b76bd9d103fe9c60e0953f (0003-Add-more-autotests.patch)
> > 
> > (the first two will be included in KF 5.27).
> > 
> > The fixed version is 5.26.0-3 (sid only - already uploaded). I'll test if
> > we need these patches also for stable inside kdepimlibs.
> 
> Ok, please let us know once you know more. Scott Kitterman has already sent
> an update for kdepimlibs (attached).
> 
> Cheers,
> Moritz

diff -Nru kdepimlibs-4.14.2/debian/changelog kdepimlibs-4.14.2/debian/changelog
--- kdepimlibs-4.14.2/debian/changelog	2014-11-17 04:38:20.0 +0100
+++ kdepimlibs-4.14.2/debian/changelog	2016-10-14 18:09:02.0 +0200
@@ -1,3 +1,21 @@
+kdepimlibs (4:4.14.2-2+deb8u1) jessie-security; urgency=high
+
+  * Team upload.
+  [ Scott Kitterman ]
+  * CVE-2016-7966 KMail: HTML injection in plain text viewer (Closes: #840546)
+- Avoid transforming as a url in plain text mode when there is a quote
+- Add debian/patches/CVE-2016-7966.diff from upstream
+
+  [ Sandro Knauß ]
+  * Additional patch to complete the fix for CVE-2016-7966
+- Replace all scary charactars (", <, > and &) with safe HTML
+  replacements.
+- Backport commit kcoreaddons 5e13d2439dbf540fdc840f0b0ab5b3ebf6642c6a
+  in debian/patches/CVE-2016-7966_part2.diff
+  * Update symbols files.
+
+ -- Sandro Knauß   Fri, 14 Oct 2016 18:09:02 +0200
+
 kdepimlibs (4:4.14.2-2) unstable; urgency=medium
 
   * Team upload.
diff -Nru kdepimlibs-4.14.2/debian/libkpimutils4.symbols kdepimlibs-4.14.2/debian/libkpimutils4.symbols
--- kdepimlibs-4.14.2/debian/libkpimutils4.symbols	2014-10-20 17:13:26.0 +0200
+++ kdepimlibs-4.14.2/debian/libkpimutils4.symbols	2016-10-14 18:09:02.0 +0200
@@ -7,6 +7,7 @@
  _ZN9KPIMUtils11LinkLocator15getEmailAddressEv@Base 4:4.3.4
  _ZN9KPIMUtils11LinkLocator15highlightedTextEv@Base 4:4.3.4
  _ZN9KPIMUtils11LinkLocator16setMaxAddressLenEi@Base 4:4.3.4
+ _ZN9KPIMUtils11LinkLocator23getUrlAndCheckValidHrefEPb@Base 4:4.14.2-2+deb8u1
  _ZN9KPIMUtils11LinkLocator6getUrlEv@Base 4:4.3.4
  _ZN9KPIMUtils11LinkLocatorC1ERK7QStringi@Base 4:4.3.4
  _ZN9KPIMUtils11LinkLocatorC2ERK7QStringi@Base 4:4.3.4
diff -Nru kdepimlibs-4.14.2/debian/patches/CVE-2016-7966.diff kdepimlibs-4.14.2/debian/patches/CVE-2016-7966.diff
--- kdepimlibs-4.14.2/debian/patches/CVE-2016-7966.diff	1970-01-01 01:00:00.0 +0100
+++ kdepimlibs-4.14.2/debian/patches/CVE-2016-7966.diff	2016-10-14 16:59:11.0 +0200
@@ -0,0 +1,89 @@
+From: Montel Laurent 
+Date: Fri, 30 Sep 2016 13:55:35 +
+Subject: Backport avoid to transform as a url when we have a quote
+X-Git-Url: http://quickgit.kde.org/?p=kdepimlibs.git=commitdiff=176fee25ca79145ab5c8e2275d248f1a46a8d8cf
+---
+Backport avoid to transform as a url when we have a quote
+---
+
+
+--- a/kpimutils/linklocator.cpp
 b/kpimutils/linklocator.cpp
+@@ -94,6 +94,12 @@
+ }
+ 
+ QString LinkLocator::getUrl()
++{
++return getUrlAndCheckValidHref();
++}
++
++
++QString LinkLocator::getUrlAndCheckValidHref(bool *badurl)
+ {
+   QString url;
+   if ( atUrl() ) {
+@@ -129,13 +135,26 @@
+ 
+ url.reserve( maxUrlLen() );  // avoid allocs
+ int start = mPos;
++bool previousCharIsADoubleQuote = false;
+ while ( ( mPos < (int)mText.length() ) &&
+ ( mText[mPos].isPrint() || mText[mPos].isSpace() ) &&
+ ( ( afterUrl.isNull() && !mText[mPos].isSpace() ) ||
+   ( !afterUrl.isNull() && mText[mPos] != afterUrl ) ) ) {
+   if ( !mText[mPos].isSpace() ) {   // skip whitespace
+-url.append( mText[mPos] );
+-if ( url.length() > maxUrlLen() ) {
++  if (mText[mPos] == QLatin1Char('>') && previousCharIsADoubleQuote) {
++  //it's an invalid url
++  if (badurl) {
++  *badurl = true;
++  }
++  return QString();
++  }
++  if (mText[mPos] == QLatin1Char('"')) {
++  previousCharIsADoubleQuote = true;
++  } else {
++  previousCharIsADoubleQuote = false;
++  }
++  url.append( mText[mPos] );
++  if ( url.length() > maxUrlLen() ) {
+   break;
+ }
+   }
+@@ -367,7 +386,12 @@
+ } else {
+   const int start = 

Processed: retitle 840685 to TOCTOU race condition in initscript on chown'ing JVM_TMP temporary directory

[Debian Bug Tracking System]

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

> retitle 840685 TOCTOU race condition in initscript on chown'ing JVM_TMP 
> temporary directory
Bug #840685 [tomcat8] tomcat8: DSA-3670 incomplete
Changed Bug title to 'TOCTOU race condition in initscript on chown'ing JVM_TMP 
temporary directory' from 'tomcat8: DSA-3670 incomplete'.
> thanks
Stopping processing here.

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

Bug#833741: Workaround

[Paul van der Vlis]

Hello,

There is no big problem for existing installations, but if you make a
new installation then flash does not work. This is what I do as root as
a workaround:

apt-get install pepperflashplugin-nonfree
cd /usr/lib/
mv pepperflashplugin-nonfree pepperflashplugin-nonfree-backup
mkdir pepperflashplugin-nonfree
cd pepperflashplugin-nonfree
wget -r -nd --no-parent
https://vandervlis.nl/files/pepperflashplugin-nonfree/
rm index.html*

After this flash will work, maybe you have to restart the browser.

Of cause you can also use your /usr/lib/pepperflashplugin-nonfree from
an older installation. That's what I did.

With regards,
Paul van der Vlis.

-- 
Paul van der Vlis Linux systeembeheer Groningen
https://www.vandervlis.nl/

Bug#838440: marked as done (nodejs: can't migrate to testing because of lack of armel binaries)

[Debian Bug Tracking System]

Your message dated Fri, 14 Oct 2016 19:07:16 +0200
with message-id <26466882-f042-8eec-f353-9f81c01dd...@xs4all.nl>
and subject line Re: [Pkg-javascript-devel] Bug#838440: Bug#838440: nodejs: 
can't migrate to testing because of lack of armel binaries
has caused the Debian Bug report #838440,
regarding nodejs: can't migrate to testing because of lack of armel binaries
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.)


-- 
838440: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838440
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nodejs
Version: 4.4.7~dfsg-2
Severity: serious

Hi,

I see you dropped support for armel in #818552 and requested the removal
of the outdated armel binaries. That's fine. However, nodejs doesn't
migrate to testing because the lack of armel binaries breaks a number
of packages that depend on nodejs on armel:

trying: nodejs
skipped: nodejs (15, 0, 81)
got: 68+546: a-3:i-18:a-0:a-11:a-0:m-0:m-0:p-35:p-0:s-1:m-546
* armel: node-almond, node-groove, node-iconv, node-leveldown, 
node-node-expat, node-sqlite3, node-topcube, node-websocket, node-ws, 
node-xmlhttprequest, qtwebchannel5-examples

Those need to get their armel binaries removed as well.

Or perhaps, if the version in experimental works on armel (it still has
armel binaries) you could try to get that uploaded to sid?

Cheers,
Emilio

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

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
On 10/10/2016 03:40 PM, Emilio Pozuelo Monfort wrote:
> On 10/10/16 14:01, Sebastiaan Couwenberg wrote:
>> On 10/09/2016 11:02 PM, Sebastiaan Couwenberg wrote:
>>> On 10/09/2016 10:25 PM, Jérémy Lal wrote:
 Now the same is going to happen with "powerpc" arch: libv8 is actually not
 compatible with all processors supported by debian (ppc64xx are ok, 
 though).

 Sebastiaan, i feel bad asking for your help again, but since you already
 filled all the RM bugs once, i suppose you're in the best position to do 
 it again
 for powerpc.
>>>
>>> Sure, the list of immediately affected packages is limited.
>>
>> There has been some progress getting the RM bugs processed. Several of
>> for armel are still outstanding, which may be due to the dependency
>> problems reported by dak for reverse dependencies.
>>
>> I thought that arch:all reverse dependencies didn't need to be removed
>> too, but I may be mistaken in that although dak has the option
>> --no-arch-all-rdeps for apparently that reason.
>>
>> I'll follow up on the outstanding bugreports to mention that only
>> arch:all rdeps are reported by dak in the dependency problems.
> 
> Indeed, arch:all packages don't need to be removed. If dak complains about 
> them,
> point it out they are arch:all and it's OK to break them.
> 
> Cheers, and thanks for looking at this.

Thanks for the feedback, and thanks for Scott K for processing the RM
bugs. All blocking bugs for armel are now fixed.

The blocking bugs for nodejs on powerpc have also been fixed by Scott K,
and I just clarified that the remaining packages dak complains about
when removing nodejs from powerpc are all arch:all or otherwise
unaffected (see: #840269)

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1--- End Message ---

Bug#840581: marked as done (vim-conque: ConqueTerm doesn't appear to load into vim)

[Debian Bug Tracking System]

Your message dated Fri, 14 Oct 2016 18:49:40 +0200
with message-id <20161014164940.l3qbz6ks7xxfl...@jwilk.net>
and subject line Re: Bug#840581: vim-conque: ConqueTerm doesn't appear to load 
into vim
has caused the Debian Bug report #840581,
regarding vim-conque: ConqueTerm doesn't appear to load into vim
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.)


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

Dear Maintainer,

Having installed the vim-conque package, I start vim:

  $ vim

and then try to start bash within it:

  :ConqueTerm bash

and just get this error:

  E492: Not an editor command: ConqueTerm bash

It looks like a bunch of files got installed in /usr/share/vim-conque,
but they don't seem to get loaded when vim starts.

If having access to the machine would help with debugging then I can
arrange that, I'll just need an ssh public key from you.

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

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

Versions of packages vim-conque depends on:
ii  python2.7.9-1
ii  vim-nox [vim-python]  2:7.4.488-7

Versions of packages vim-conque recommends:
ii  vim-addon-manager  0.5.3

vim-conque suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---

* David Cantrell , 2016-10-14, 17:46:
As per Debian Packaging Policy for Vim, vim addons are not enabled by 
default. You have to enable it yourself with vim-addon-manager (or by 
manually creating appropriate symlinks). This is documented in README.Debian.


Ah-ha! Thanks, all is clear now, and working, so the ticket can be closed.


Thanks for the confirmation. :)

--
Jakub Wilk--- End Message ---

Bug#840733: e2fsprogs contains non-free file

[Theodore Ts'o]

On Fri, Oct 14, 2016 at 12:18:31PM +0300, Adrian Bunk wrote:
> Source: e2fsprogs
> Version: 1.43.3-1
> Severity: serious
> 
> lib/et/test_cases/imap_err.et:
> 
> The "for non-commercial purposes only" is a clear violation
> of clause 6 of the DFSG.

Thanks for pointing that out.  Please note that this file is **only**
used as a test case so there is absolutely no binary packages from
e2fsprogs which are derived from this particular file.

I'll remove it from the next version of e2fsprogs sources and can spin
a new tarball at that time.  Since we don't actually depend on this
file it could be easily removed from the e2fsprogs_1.43.orig.tar.gz if
someone really is concerned  but the mere existence of this
"no-commercial-use only file" I don't think will cause any legal risk
to Debian, so IMHO it's not worth doing.  However, if the FTP team
would like to do it, they are free to, of course.

   - Ted

Bug#840756: node-lex-parser: FTBFS: Attempt to unlock ..., which hasn't been locked

[Pirate Praveen]

On വെള്ളി 14 ഒക്ടോബര്‍ 2016 07:29 വൈകു, Aaron M. Ucko wrote:
> depending on the architecture.  For whatever reason, the problem was with
> jison@0.4.x on arm64, armhf, mips, powerpc, ppc64el, s390x, and the
> non-release architecture kfreebsd-amd64, and test@* on i386, mips64el,
> mipsel, and the non-release architecture kfreebsd-i386.
> 
> Could you please take a look?


I'm using npm only to bootstrap (its a circular dependency), once jison
is uploaded to debian (it needs JSONSelect and jison-lex), we can remove
the npm install command and it will work.

> Thanks!
> 
> FTR, I'm classifying this bug as a regression even though node-lex-parser
> is new because I strongly suspect it would also affect binNMUs on amd64.
> 




signature.asc
Description: OpenPGP digital signature

Bug#835360: rkt: FTBFS on several architectures

[Andreas Henriksson]

Hello all.

On Thu, Oct 13, 2016 at 01:29:31PM +, Luca BRUNO wrote:
> On Thursday, 13 October 2016 13:59:27 UTC Andreas Henriksson wrote:
>  
> > Fwiw, there's a chain of {build-,}dependencies that would need to be
> > removed on ppc64el
> 
> Ah, when I wrote my previous answer I didn't realize that.
> Upon further inspection, it looks like it may be just enough to cherry-pick
> this fix on top of gopsutil:
> https://github.com/shirou/gopsutil/pull/261

I've tested applying PR 259 and 261 which indeed fixes the build on ppc64le
but the test-suite still fails.

The problem seems to boil down to gopsutil parsing of /proc/cpuinfo being
extremely (x86 centricly) naive, as cpuinfo content is very architecture
specific. Furter discussion on that topic is probably needed upstream...
Just satisfying what the testsuite needs to call it success is quite
simple though by treating "cpu" field as meaning the same as "model name".

I'm attaching a debdiff which I've testbuilt on the debian ppc64le porterbox.

(Despite this debdiff, asking for removal could possibly be a better
idea as there's obviously not enough backing to properly support ppc64le
right now and thus probably not for the lifetime of stretch.)

Regards,
Andreas Henriksson
diff -Nru golang-github-shirou-gopsutil-2.1/debian/changelog 
golang-github-shirou-gopsutil-2.1/debian/changelog
--- golang-github-shirou-gopsutil-2.1/debian/changelog  2016-07-14 
07:23:30.0 +
+++ golang-github-shirou-gopsutil-2.1/debian/changelog  2016-10-14 
08:43:23.0 +
@@ -1,3 +1,15 @@
+golang-github-shirou-gopsutil (2.1-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add debian/patches/259.patch and debian/patches/261.patch
+- upstream PR 259 + 261, should fix build on ppc64el.
+  * Add debian/patches/gopsutil-ppc64le-model-name.patch
+- ppc64le /proc/cpuinfo doesn't follow the same style as x86 and
+  test-suite require atleast the "model name" field. Map that
+  to the "cpu" field which exists on ppc64le for now.
+
+ -- Andreas Henriksson   Fri, 14 Oct 2016 08:43:23 +
+
 golang-github-shirou-gopsutil (2.1-2) unstable; urgency=medium
 
   * Extend "01-Disable_failing_tests.patch" to disable failing
diff -Nru golang-github-shirou-gopsutil-2.1/debian/patches/259.patch 
golang-github-shirou-gopsutil-2.1/debian/patches/259.patch
--- golang-github-shirou-gopsutil-2.1/debian/patches/259.patch  1970-01-01 
00:00:00.0 +
+++ golang-github-shirou-gopsutil-2.1/debian/patches/259.patch  2016-10-14 
08:43:23.0 +
@@ -0,0 +1,83 @@
+From eb4a57117f5b734246226c9b6d6b1f9edca2e4f2 Mon Sep 17 00:00:00 2001
+From: Thomas Hipp 
+Date: Fri, 16 Sep 2016 09:04:52 +0200
+Subject: [PATCH] process: determine page sizes via function
+
+Instead of hard-coding the page size for linux systems, use Go's
+`Getpagesize` function.
+
+This resolves #258.
+
+Signed-off-by: Thomas Hipp 
+---
+ process/process_linux.go   | 5 -
+ process/process_linux_386.go   | 3 +--
+ process/process_linux_amd64.go | 3 +--
+ process/process_linux_arm.go   | 3 +--
+ process/process_linux_arm64.go | 3 +--
+ 5 files changed, 8 insertions(+), 9 deletions(-)
+
+diff --git a/process/process_linux.go b/process/process_linux.go
+index 158cb04..9eb4f44 100644
+--- a/process/process_linux.go
 b/process/process_linux.go
+@@ -20,7 +20,10 @@ import (
+   "github.com/shirou/gopsutil/net"
+ )
+ 
+-var ErrorNoChildren = errors.New("process does not have children")
++var (
++  ErrorNoChildren = errors.New("process does not have children")
++  PageSize= uint64(os.Getpagesize())
++)
+ 
+ const (
+   PrioProcess = 0 // linux/resource.h
+diff --git a/process/process_linux_386.go b/process/process_linux_386.go
+index 541b854..c4df213 100644
+--- a/process/process_linux_386.go
 b/process/process_linux_386.go
+@@ -4,6 +4,5 @@
+ package process
+ 
+ const (
+-  ClockTicks = 100  // C.sysconf(C._SC_CLK_TCK)
+-  PageSize   = 4096 // C.sysconf(C._SC_PAGE_SIZE)
++  ClockTicks = 100 // C.sysconf(C._SC_CLK_TCK)
+ )
+diff --git a/process/process_linux_amd64.go b/process/process_linux_amd64.go
+index b4a4ce8..99b6659 100644
+--- a/process/process_linux_amd64.go
 b/process/process_linux_amd64.go
+@@ -4,6 +4,5 @@
+ package process
+ 
+ const (
+-  ClockTicks = 100  // C.sysconf(C._SC_CLK_TCK)
+-  PageSize   = 4096 // C.sysconf(C._SC_PAGE_SIZE)
++  ClockTicks = 100 // C.sysconf(C._SC_CLK_TCK)
+ )
+diff --git a/process/process_linux_arm.go b/process/process_linux_arm.go
+index c6123a4..8aef44c 100644
+--- a/process/process_linux_arm.go
 b/process/process_linux_arm.go
+@@ -4,6 +4,5 @@
+ package process
+ 
+ const (
+-  ClockTicks = 100  // C.sysconf(C._SC_CLK_TCK)
+-  PageSize   = 4096 // C.sysconf(C._SC_PAGE_SIZE)
++  ClockTicks = 100 // C.sysconf(C._SC_CLK_TCK)
+ )
+diff --git a/process/process_linux_arm64.go b/process/process_linux_arm64.go
+index 

Bug#840770: openvswitch: FTBFS on almost all big-endian architectures: 954: ofproto-dpif - in place modification (vlan) FAILED (ofproto-dpif.at:7237)

[Emilio Pozuelo Monfort]

Source: openvswitch
Version: 2.5.1~pre+git20160626-2
Severity: serious

Hi,

openvswitch failed to build on almost all of our big-endian architectures:

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

As you can see it failed on mips, powerpc, s390x, m68k, ppc64 and sparc64,
all of which are big endian. powerpcspe is also big endian, but a build
hasn't been attempted there yet. hppa is the notable exception, as it is
the only big endian architecture where this has built. Perhaps it is
because of a difference in one of the build-deps or in some other build
environment difference, or perhaps it is for some other reason. Or maybe
this isn't an endianness issue at all?

Cheers,
Emilio

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

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

Bug#728955: libatomic-ops: diff for NMU version 7.4.2-1.2

[Emilio Pozuelo Monfort]

Hi,

On Sun, 13 Dec 2015 22:12:24 +0100 gregor herrmann  wrote:
> Control: tag -1 - pending
> 
> On Mon, 14 Dec 2015 08:05:22 +1100, Ian Wienand wrote:
> 
> > The patch has not been applied because it is not clear it is correct
> > 
> > There is a thread that starts at [1] and ended inconclusively at [2]
> > 
> > It's unfortunate that the number of people who understand power memory 
> > ordering
> > issues at the level required can probably be counted on one hand.  But I 
> > don't
> > think we should apply patches upstream feel don't address the issue
> > 
> > -i
> > 
> > [1] 
> > http://www.hpl.hp.com/hosted/linux/mail-archives/gc/2014-January/005825.html
> > [2] 
> > http://www.hpl.hp.com/hosted/linux/mail-archives/gc/2014-February/005852.html
> 
> Thanks for this additional information.
> I've cancelled the aforementioned NMU.

The last version had failed on armel, powerpc and ppc64el. I gave it back and it
built on armel and powerpc, but it failed on ppc64el (gave it back twice there):

https://buildd.debian.org/status/package.php?p=libatomic-ops

Dunno if you want to close this bug or retitle it.

Has there been any progress on a fix for ppc64el?

Regards,
Emilio

Bug#806000: brickos: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

On Fri, 14 Oct 2016, Petter Reinholdtsen wrote:

> Control: tags -1 + patch
> 
> I had a look, and while I do not quite understand the build system and why it
> fail to create the directory it need to install, I applied this patch and got
> the 'dpkg-buildpackage -A' build working:
> 
> diff -ur brickos-0.9.0.dfsg/debian/rules brickos-0.9.0.dfsg-pere/debian/rules
> --- brickos-0.9.0.dfsg/debian/rules 2015-02-14 18:21:17.0 +
> +++ brickos-0.9.0.dfsg-pere/debian/rules2016-10-14 07:43:21.284198193 
> +
> @@ -33,6 +33,7 @@
>  
>  override_dh_auto_install:
> #  Install the package into debian/brickos.
> +   mkdir -p $(CURDIR)/debian/brickos/usr/bin
> $(MAKE) install docs-install inst_prefix=/usr 
> prefix=$(CURDIR)/debian/brickos/usr 
> mandir=$(CURDIR)/debian/brickos/usr/share/man
> #  remove docs we shouldn't install
> rm -f 
> $(CURDIR)/debian/brickos/usr/share/doc/brickos/html/INSTALL-cygwin*

Ok, now that you mention it, the bug is easy to explain:

Since I was doing "dpkg-buildpackage -A", this means we are creating
arch-independent packages only (i.e. Arch:all), so dh_installdirs does
not create debian/brickos because brickos is arch-dependent (i.e. Arch:any).

The proposed patch is probably ok as a workaround, but if this were my
package, I would drop dh_movefiles and would use override_dh_auto_install
to install into debian/tmp and then would use debian/*.install files
to determine which files go to which packages.

(That's probably the current trend, or the "orthodox way").

Thanks a lot.

Processed: golang-github-naoina-toml: Source package is not fully buildable within Debian main

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 840766
Bug #840767 [src:golang-github-naoina-toml] golang-github-naoina-toml: Source 
package is not fully buildable within Debian main
840767 was not blocked by any bugs.
840767 was not blocking any bugs.
Added blocking bug(s) of 840767: 840766

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

Bug#840767: golang-github-naoina-toml: Source package is not fully buildable within Debian main

[Guillem Jover]

Source: golang-github-naoina-toml
Source-Version: 0.1.0-1
Severity: serious
Control: block -1 by 840766

Hi!

This package contains a «parse.peg» which is the source for
«parse.peg.go». But the required program to build that
(golang-github-pointlander-peg) is not currently present in Debian,
which makes this unfit for Debian main.

The blocking bug (and all its reverse dependencies) need to be packaged,
either that or this package and all its reverse dependencies moved to
contrib. :/

Thanks,
Guillem

Bug#840394: motif: FTBFS: relocation R_X86_64_PC32 against symbol ...

[Graham Inggs]

Hi Joachim

On 14 October 2016 at 15:23, Joachim Wiedorn  wrote:
> for now motif should be compiled without buildflag 'pie'. I think it is
> not needed for the next release - it is disabled by default, because not
> all packages can be compiled with this flag.

PIE by default is happening for Stretch.
Release Team have given the go-ahead, see message #21 of #835148 [1],
and the changes have already been committed to SVN [2] and should be
included in the next GCC6 upload.

Regards
Graham


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835148#21
[2] https://anonscm.debian.org/viewvc/gcccvs?view=revision=8999

Bug#840761: python-opcua: FTBFS (ImportError: No module named setuptools)

[Santiago Vila]

Package: src:python-opcua
Version: 0.10.17-1
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 dpkg-source --before-build python-opcua-0.10.17
 fakeroot debian/rules clean
dh clean --buildsystem=pybuild --with python2,python3
   dh_testdir -O--buildsystem=pybuild
   dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py clean 
Traceback (most recent call last):
  File "setup.py", line 1, in 
from setuptools import setup, find_packages
ImportError: No module named setuptools
E: pybuild pybuild:276: clean: plugin distutils failed with: exit code=1: 
python2.7 setup.py clean 
dh_auto_clean: pybuild --clean -i python{version} -p 2.7 returned exit code 13
debian/rules:8: recipe for target 'clean' failed
make: *** [clean] Error 25
dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2


It is strongly recommended that packages are built in a clean sid chroot
to ensure that they are buildable (i.e. no missing build-dependencies).

Thanks.

Bug#840760: node-livescript: FTBFS (npm: Command not found)

[Santiago Vila]

Package: src:node-livescript
Version: 1.5.0+dfsg-1
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>/node-livescript-1.5.0+dfsg'
npm install jison
make[1]: npm: Command not found
debian/rules:11: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 127
make[1]: Leaving directory '/<>/node-livescript-1.5.0+dfsg'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

It is strongly recommended that packages are built in a clean sid chroot
to ensure that they are buildable (i.e. no missing build-dependencies).

Thanks.

Bug#840756: node-lex-parser: FTBFS: Attempt to unlock ..., which hasn't been locked

[Aaron M. Ucko]

Source: node-lex-parser
Version: 0.1.4-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Automatic builds of node-lex-parser all failed with either

  npm ERR! Error: Attempt to unlock jison@0.4.x, which hasn't been locked
  npm ERR! at unlock (/usr/share/npm/lib/utils/locker.js:44:11)
  npm ERR! at cb (/usr/share/npm/lib/cache/add-named.js:32:5)
  npm ERR! at /usr/share/npm/lib/cache/add-named.js:41:20
  npm ERR! at /usr/share/npm/lib/utils/locker.js:22:20
  npm ERR! at /usr/share/npm/node_modules/inflight/inflight.js:22:7
  npm ERR! at Array.forEach (native)
  npm ERR! at res (/usr/share/npm/node_modules/inflight/inflight.js:21:9)
  npm ERR! at /usr/lib/nodejs/once.js:17:15
  npm ERR! at afterMkdir (/usr/share/npm/lib/cache/get-stat.js:53:14)
  npm ERR! at /usr/lib/nodejs/mkdirp/index.js:34:29

or

  npm ERR! Error: Attempt to unlock test@*, which hasn't been locked
  npm ERR! at unlock (/usr/share/npm/lib/utils/locker.js:44:11)
  [...]

depending on the architecture.  For whatever reason, the problem was with
jison@0.4.x on arm64, armhf, mips, powerpc, ppc64el, s390x, and the
non-release architecture kfreebsd-amd64, and test@* on i386, mips64el,
mipsel, and the non-release architecture kfreebsd-i386.

Could you please take a look?

Thanks!

FTR, I'm classifying this bug as a regression even though node-lex-parser
is new because I strongly suspect it would also affect binNMUs on amd64.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#840394: motif: FTBFS: relocation R_X86_64_PC32 against symbol ...

[Joachim Wiedorn]

Hello,

for now motif should be compiled without buildflag 'pie'. I think it is
not needed for the next release - it is disabled by default, because not
all packages can be compiled with this flag.

---
Have a nice day.

Joachim (Germany)


pgp0i55wnVLkQ.pgp
Description: Digitale Signatur von OpenPGP

Bug#840685: tomcat8: DSA-3670 incomplete

[Markus Koschany]

On 14.10.2016 10:07, paul.sz...@sydney.edu.au wrote:
[...]
>> So while I think it should be fixed, this would not warrant a DSA,
>> since mitigated by default in Debian.
> 
> No mitigation: fix and DSA, please!

I agree with Salvatore. I have tested the following:

First of all you can only gain write permissions as the tomcat8 user if
you exploit an yet unknown security vulnerability in a web application
or Tomcat itself. Debian's tomcat8 user has no shell access by default.

So the server must be running and somehow you managed to remove
/tmp/tomcat8-tomcat8-tmp and replaced the directory with a symlink to an
arbitrary file.

Your attack vector requires that the server must be restarted. But there
is another rm -rf "$JVM_TMP" command in the stop target that would
remove your symlink again.

Ok, let's imagine that you could find a way around the rm -rf commands.
Let's remove those rm -rf "$JVM_TMP" calls in /etc/init.d/tomcat8. Then
run systemctl daemon-reload. Log in as tomcat8 user and create your
symlink for /tmp/tomcat8-tomcat8-tmp. If I run systemctl restart tomcat8
now, I get this:

Job for tomcat8.service failed because the control process exited with
error code.

The symlink is still present and nothing has changed regarding the file
permissions for my arbitrary file.

I agree that we should improve the init script in this regard but I
actually don't see a major risk like a root escalation for users at the
moment and I suggest to lower the severity of this bug report to important.

> What response time should I have expected of team@security? You had
> close to a whole day... compared to that, Markus replied within the
> hour to the Debian bug. (But he did not yet reply to my next, private
> bug/message... seems public messaging works best!)

In my opinion it is generally understood that you should give people at
least enough time to react to an e-mail and to assess the issue.
Expecting a response time in less than a day is not very reasonable,
especially when there are things like the time difference between
Australia and Europe.

Regards,

Markus




signature.asc
Description: OpenPGP digital signature

Bug#840394: motif: FTBFS: relocation R_X86_64_PC32 against symbol ...

[Joachim Wiedorn]

Hello,

for now motif should be compiled without hardening buildflag 'pie'
(see patch).


--- d01/debian/rules2016-09-28 22:22:07.0 +0200
+++ d02/debian/rules2016-10-14 01:04:31.0 +0200
@@ -2,7 +2,7 @@
 
 export DEB_CFLAGS_MAINT_APPEND=-D_FILE_OFFSET_BITS=64
 export DEB_LDFLAGS_MAINT_APPEND=-Wl,--as-needed
-export DEB_BUILD_MAINT_OPTIONS=hardening=+all
+export DEB_BUILD_MAINT_OPTIONS=hardening=+bindnow
 
 %:
dh $@ --with autoreconf --parallel


---
Have a nice day.

Joachim (Germany)
--- d01/debian/rules	2016-09-28 22:22:07.0 +0200
+++ d02/debian/rules	2016-10-14 01:04:31.0 +0200
@@ -2,7 +2,7 @@
 
 export DEB_CFLAGS_MAINT_APPEND=-D_FILE_OFFSET_BITS=64
 export DEB_LDFLAGS_MAINT_APPEND=-Wl,--as-needed
-export DEB_BUILD_MAINT_OPTIONS=hardening=+all
+export DEB_BUILD_MAINT_OPTIONS=hardening=+bindnow
 
 %:
 	dh $@ --with autoreconf --parallel


pgpJ2M0th12oh.pgp
Description: Digitale Signatur von OpenPGP

Bug#834126: marked as done (open-gram: FTBFS: make[1]: *** [lm_sc.t3g] Aborted (core dumped))

[Debian Bug Tracking System]

Your message dated Fri, 14 Oct 2016 13:35:44 +
with message-id 
and subject line Bug#834126: fixed in open-gram 0.1.22+20131212-2
has caused the Debian Bug report #834126,
regarding open-gram: FTBFS: make[1]: *** [lm_sc.t3g] Aborted (core dumped)
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.)


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

open-gram fails to build from source in unstable/amd64:

  [..]

  
  
**
  ** Starting build 
  **
  
**
  
   Package:  open-gram
   Version:  0.1.22+20131212-1
   Build architecture:   amd64
   Date: Fri, 12 Aug 2016 09:37:09 +0100
   Hostname: 9d181e905f1c
   Uname:Linux 9d181e905f1c 4.6.0-1-amd64 #1 SMP Debian 4.6.4-1 
(2016-07-18) x86_64 GNU/Linux
   /etc/timezone:Europe/London
  
  
**
  ** Installing build dependencies  
  **
  
**
  
  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'open-gram-build-deps' in 
'../open-gram-build-deps_0.1.22+20131212-1_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package open-gram-build-deps.
  (Reading database ... 23221 files and directories currently installed.)
  Preparing to unpack open-gram-build-deps_0.1.22+20131212-1_all.deb ...
  Unpacking open-gram-build-deps (0.1.22+20131212-1) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
sunpinyin-utils
  The following NEW packages will be installed:
sunpinyin-utils
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 141 kB of archives.
  After this operation, 507 kB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 sunpinyin-utils amd64 
2.0.3+git20140127-5 [141 kB]
  Fetched 141 kB in 0s (7150 kB/s)
  Selecting previously unselected package sunpinyin-utils.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 23225 files and directories currently installed.)
  Preparing to unpack .../sunpinyin-utils_2.0.3+git20140127-5_amd64.deb ...
  Unpacking sunpinyin-utils (2.0.3+git20140127-5) ...
  Setting up sunpinyin-utils (2.0.3+git20140127-5) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up open-gram-build-deps (0.1.22+20131212-1) ...
  
  
**
  ** Environment
  **
  
**
  
  
PATH=/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  HOSTNAME=9d181e905f1c
  TERM=xterm
  PAGER=more
  DISPLAY=:0
  DOCKER_IMAGE=lamby-debian-sid
  DEB_BUILD_OPTIONS=parallel=9
  PIP_DOWNLOAD_CACHE=/home/lamby/.cache/pip
  HOME=/home/lamby
  

Bug#840477: marked as done (cryptsetup: initramfs hook cryptroot fails if root is lvm and spans multiple devices/nodes)

[Debian Bug Tracking System]

Your message dated Fri, 14 Oct 2016 13:03:44 +
with message-id 
and subject line Bug#840480: fixed in cryptsetup 2:1.7.2-4
has caused the Debian Bug report #840480,
regarding cryptsetup: initramfs hook cryptroot fails if root is lvm and spans 
multiple devices/nodes
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.)


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

Dear Maintainer,

update-initramfs fails to add cryptsetup to the initramfs with the warning:
update-initramfs: Generating /boot/initrd.img-4.7.0-1-amd64
cryptsetup: WARNING: invalid line in /etc/crypttab for md0p3_cryptflash_crypt - 
cryptsetup: WARNING: invalid line in /etc/crypttab for md0p3_cryptflash_crypt -

On my system, the root filesystem spans two lvm nodes (because I'm using lvm 
caching and one is a raid array while the other is an SSD).
I looked into /usr/share/initramfs-tools/hooks/cryptroot and found the issue 
was caused by not putting a space between the devices when generating the list 
of nodes. I fixed the issue by putting a space in line 233 before $depnode in 
function get_lvm_deps():
printf '%s' " $depnode"

I think this bug was probably introduced in version 2:1.7.2-1, possibly with 
the change:
  * debian/initramfs/cryptroot-hook: Avoid leading space in $rootdevs,
  $resumedevs, etc.

Thanks!
- Cem

-- Package-specific info:
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-4.7.0-1-amd64 root=/dev/mapper/sapphire--vg-root ro 
initrd=/install/initrd.gz quiet

-- /etc/crypttab
flash_crypt /dev/sde none luks
md0p3_crypt /dev/md0p3 none luks

-- /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
#   
 
/dev/mapper/sapphire--vg-root   /   ext4
errors=remount-ro   0   1
# /boot was on /dev/md0p2 during installation
UUID=4cae8b54-da05-4826-9b13-feaaa3335eaf   /boot   ext2
defaults0   2
/dev/mapper/sapphire--vg-home   /home   ext4
defaults0   0
/dev/mapper/sapphire--vg-swap_1 noneswapsw  
0   0
/dev/mapper/sapphire--vg-vault  /mnt/vault  ext4
defaults0   0

-- lsmod
Module  Size  Used by
nls_utf8   16384  1
cifs  630784  2
sha256_ssse3   32768  0
cmac   16384  0
md416384  0
des_generic24576  0
arc4   16384  0
dns_resolver   16384  1 cifs
fscache61440  1 cifs
binfmt_misc20480  1
snd_hda_codec_hdmi 45056  1
nvidia_drm 45056  1
dm_cache_smq   24576  2
drm_kms_helper147456  1 nvidia_drm
intel_rapl 20480  0
dm_cache   57344  3 dm_cache_smq
snd_hda_codec_realtek86016  1
x86_pkg_temp_thermal16384  0
dm_persistent_data 65536  1 dm_cache
intel_powerclamp   16384  0
snd_hda_codec_generic69632  1 snd_hda_codec_realtek
drm   364544  4 drm_kms_helper,nvidia_drm
iTCO_wdt   16384  0
dm_bio_prison  16384  1 dm_cache
iTCO_vendor_support16384  1 iTCO_wdt
dm_bufio   28672  1 dm_persistent_data
snd_usb_audio 176128  0
snd_hda_intel  36864  5
kvm_intel 188416  0
nvidia_modeset765952  5 nvidia_drm
lpc_ich24576  0
snd_hda_codec 135168  4 
snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel
mei_me 32768  0
snd_usbmidi_lib28672  1 snd_usb_audio
snd_rawmidi32768  1 snd_usbmidi_lib
snd_seq_device 16384  1 snd_rawmidi
kvm   573440  1 kvm_intel
pcspkr 16384  0
mfd_core   16384  1 lpc_ich
i2c_i801   20480  0
serio_raw  16384  0
irqbypass  16384  1 kvm
mei94208  1 mei_me
sg 32768  0
snd_hda_core   81920  5 
snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel
snd_hwdep  16384  2 snd_usb_audio,snd_hda_codec
snd_soc_rt5640

Bug#840480: marked as done (cryptsetup initramfs hook warning with multiple encrypted physical volumes)

[Debian Bug Tracking System]

Your message dated Fri, 14 Oct 2016 13:03:44 +
with message-id 
and subject line Bug#840480: fixed in cryptsetup 2:1.7.2-4
has caused the Debian Bug report #840480,
regarding cryptsetup initramfs hook warning with multiple encrypted physical 
volumes
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.)


-- 
840480: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840480
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cryptsetup
Version: 2:1.7.2-3

I have a volume group with 2 physical volumes named ssd.luks and spin.luks.
Both are encrypted with luks. This is the only VG in the system, and it
contains all filesystems. When I run update-initramfs, I get this warning:

update-initramfs: Generating /boot/initrd.img-4.7.0-1-amd64
cryptsetup: WARNING: invalid line in /etc/crypttab for ssd.luksspin.luks -

This happens because when there are multiple luks devices in a volume
group, they are printed without space so the names get concatenated, and
the concatenated device is not found. The attached patch fixes the issue
for me.

Thanks,
 Zoltan
--- /mnt/btroot/root-2016.10.11/usr/share/initramfs-tools/hooks/cryptroot	2016-10-06 03:47:05.0 -0500
+++ /usr/share/initramfs-tools/hooks/cryptroot	2016-10-11 17:01:40.826238533 -0500
@@ -230,7 +230,7 @@
 			get_lvm_deps "$depnode"
 			continue
 		fi
-		printf '%s' "$depnode"
+		printf '%s\n' "$depnode"
 	done
 
 	return 0
--- End Message ---
--- Begin Message ---
Source: cryptsetup
Source-Version: 2:1.7.2-4

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

Debian distribution maintenance software
pp.
Jonas Meurer  (supplier of updated cryptsetup package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 13 Oct 2016 23:11:45 +0200
Source: cryptsetup
Binary: cryptsetup cryptsetup-bin libcryptsetup4 libcryptsetup-dev 
cryptsetup-udeb libcryptsetup4-udeb
Architecture: source amd64
Version: 2:1.7.2-4
Distribution: unstable
Urgency: high
Maintainer: Debian Cryptsetup Team 

Changed-By: Jonas Meurer 
Description:
 cryptsetup - disk encryption support - startup scripts
 cryptsetup-bin - disk encryption support - command line tools
 cryptsetup-udeb - disk encryption support - commandline tools (udeb) (udeb)
 libcryptsetup-dev - disk encryption support - development files
 libcryptsetup4 - disk encryption support - shared library
 libcryptsetup4-udeb - disk encryption support - shared library (udeb) (udeb)
Closes: 840480
Changes:
 cryptsetup (2:1.7.2-4) unstable; urgency=high
 .
   [ Guilhem Moulin ]
   * debian/initramfs/cryptroot-hook:
 + Fix warning printed for lvm devices backed by multiple dm-crypt nodes.
   Regression introduced in 2:1.7.2-1.  Thanks Zoltan Hidvegi, for the
   patch. (Closes: #840480)
 + Don't escape all slash characters "/" in device paths of the form
   /dev/by-label/..., only the label itself.  Regression introduced in
   2:1.7.2-2 as a fix for #839888.
Checksums-Sha1:
 51bc0b3593919008389d14d14a9170d366f4c327 2651 cryptsetup_1.7.2-4.dsc
 908cfe7a93cdb49b0cb165f7c8c238be43ce2b89 87652 cryptsetup_1.7.2-4.debian.tar.xz
 e5866150ca10363c6cb53ff2034bb0b6ea6fe23b 112748 
cryptsetup-bin-dbgsym_1.7.2-4_amd64.deb
 a1fc252de063d030da5ecc022f180830fa212ea1 215336 
cryptsetup-bin_1.7.2-4_amd64.deb
 e1e46667567be1ddda8a8f81cfa232e1193dddc0 17080 
cryptsetup-dbgsym_1.7.2-4_amd64.deb
 b065bde74632364c399d45b9f76f2bc81578b962 38912 
cryptsetup-udeb_1.7.2-4_amd64.udeb
 92ac8a372b3525986d26e47ef7f50fcf03d88b70 168528 cryptsetup_1.7.2-4_amd64.deb
 73085bc06e0035c8f281c7af41e90cb46f4ce0cd 53028 
libcryptsetup-dev_1.7.2-4_amd64.deb
 c9fe51eaa6b5e149585302ef3881a03413d39440 174798 
libcryptsetup4-dbgsym_1.7.2-4_amd64.deb
 382ada2b15724db9d32c0f83286c3fb430f44e13 65780 
libcryptsetup4-udeb_1.7.2-4_amd64.udeb
 6fb1c5f146db86b15116f5610027419350d763b1 106664 
libcryptsetup4_1.7.2-4_amd64.deb
Checksums-Sha256:
 

Processed: valac: Regression in DBus gio-2.0.vapi binding

[Debian Bug Tracking System]

Processing control commands:

> affects -1 mdbus2
Bug #840746 [valac] valac: Regression in DBus gio-2.0.vapi binding
Added indication that 840746 affects mdbus2

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

Bug#840746: valac: Regression in DBus gio-2.0.vapi binding

[Sebastian Reichel]

Package: valac
Version: 0.34.0-1
Severity: serious
Tags: patch upstream
Justification: renders mdbus package completly useless
Forwarded: https://bugzilla.gnome.org/show_bug.cgi?id=772902
Control: affects -1 mdbus2

Hi,

vala 0.34 has updated gio-2.0.vapi file, which removed
"array_null_terminated = true" annotation from a couple of DBus
related objects. This results in mdbus2 package being completly
useless, as it only sees empty arrays.

-- Sebastian

Bug#839364: marked as done (golang: FTBFS: Go version is "go1.6.1", ignoring -next /<>/api/next.txt)

[Debian Bug Tracking System]

Your message dated Fri, 14 Oct 2016 12:03:36 +
with message-id 
and subject line Bug#839690: Removed package(s) from unstable
has caused the Debian Bug report #839364,
regarding golang: FTBFS: Go version is "go1.6.1", ignoring -next 
/<>/api/next.txt
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.)


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> set -ex; \
>   cd src; \
>   export PATH="/<>/bin:$PATH"; \
>   eval "$(go tool dist env)"; \
>   bash run.bash -k -no-rebuild;
> + cd src
> + export 
> PATH=/<>/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> + go tool dist env
> + eval CC="gcc"
> CC_FOR_TARGET="gcc"
> GOROOT="/<>"
> GOBIN="/<>/bin"
> GOARCH="amd64"
> GOOS="linux"
> GOHOSTARCH="amd64"
> GOHOSTOS="linux"
> GOTOOLDIR="/<>/pkg/tool/linux_amd64"
> + CC=gcc
> + CC_FOR_TARGET=gcc
> + GOROOT=/<>
> + GOBIN=/<>/bin
> + GOARCH=amd64
> + GOOS=linux
> + GOHOSTARCH=amd64
> + GOHOSTOS=linux
> + GOTOOLDIR=/<>/pkg/tool/linux_amd64
> + bash run.bash -k -no-rebuild
> 
> # Testing packages.
> okarchive/tar 0.029s
> okarchive/zip 0.085s
> okbufio   0.105s
> okbytes   0.128s
> okcompress/bzip2  0.087s
> okcompress/flate  0.304s
> okcompress/gzip   0.014s
> okcompress/lzw0.004s
> okcompress/zlib   0.032s
> okcontainer/heap  0.010s
> okcontainer/list  0.002s
> okcontainer/ring  0.015s
> okcrypto/aes  0.054s
> okcrypto/cipher   0.004s
> okcrypto/des  0.014s
> okcrypto/dsa  0.005s
> okcrypto/ecdsa0.049s
> okcrypto/elliptic 0.049s
> okcrypto/hmac 0.003s
> okcrypto/md5  0.004s
> okcrypto/rand 0.027s
> okcrypto/rc4  0.147s
> okcrypto/rsa  0.128s
> okcrypto/sha1 0.004s
> okcrypto/sha256   0.012s
> okcrypto/sha512   0.005s
> okcrypto/subtle   0.006s
> okcrypto/tls  1.334s
> okcrypto/x509 1.657s
> okdatabase/sql0.051s
> okdatabase/sql/driver 0.002s
> okdebug/dwarf 0.014s
> okdebug/elf   0.029s
> okdebug/gosym 0.440s
> okdebug/macho 0.012s
> okdebug/pe0.012s
> okdebug/plan9obj  0.003s
> okencoding/ascii850.003s
> okencoding/asn1   0.023s
> okencoding/base32 0.003s
> okencoding/base64 0.010s
> okencoding/binary 0.012s
> okencoding/csv0.004s
> okencoding/gob0.059s
> okencoding/hex0.010s
> okencoding/json   0.287s
> okencoding/pem0.014s
> okencoding/xml0.012s
> okerrors  0.009s
> okexpvar  0.013s
> okflag0.003s
> okfmt 0.174s
> okgo/ast  0.017s
> okgo/build0.095s
> okgo/constant 0.014s
> okgo/doc  0.039s
> okgo/format   0.013s
> okgo/internal/gccgoimporter   0.011s
> okgo/internal/gcimporter  0.212s
> okgo/parser   0.039s
> okgo/printer  0.478s
> okgo/scanner  0.004s
> okgo/token0.027s
> okgo/types0.814s
> okhash/adler320.006s
> okhash/crc32  0.006s
> okhash/crc64  0.006s
> okhash/fnv0.002s
> okhtml0.003s
> okhtml/template   0.045s
> okimage   0.161s
> okimage/color 0.134s
> okimage/draw  0.125s
> okimage/gif   0.127s
> okimage/jpeg  0.237s
> okimage/png   0.051s
> okindex/suffixarray   0.010s
> okinternal/golang.org/x/net/http2/hpack   0.010s
> okinternal/singleflight   0.023s
> okinternal/trace  0.006s
> okio  0.019s
> okio/ioutil   0.015s
> oklog 0.004s
> oklog/syslog  2.019s
> okmath0.003s
> okmath/big0.538s
> okmath/cmplx  0.004s
> okmath/rand   0.120s
> okmime0.010s
> okmime/multipart  0.594s
> okmime/quotedprintable0.234s
> oknet 1.619s
> oknet/http10.044s
> oknet/http/cgi0.198s
> oknet/http/cookiejar  0.005s
> oknet/http/fcgi   0.004s
> oknet/http/httptest   0.007s
> oknet/http/httputil   0.018s
> oknet/http/internal   0.002s
> ok

Bug#624025: marked as done (dsyslog: Uses deprecated _set_priority GnuTLS functions / broken with GnuTLS 3.4.0)

[Debian Bug Tracking System]

Your message dated Fri, 14 Oct 2016 11:50:41 +
with message-id 
and subject line Bug#835369: Removed package(s) from unstable
has caused the Debian Bug report #624025,
regarding dsyslog: Uses deprecated _set_priority GnuTLS functions / broken with 
GnuTLS 3.4.0
to be marked as done.

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

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


-- 
624025: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624025
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dsyslog
Version: 0.6.0
Severity: normal
User: ametz...@downhill.at.eu.org
Usertags: deprecated-gnutls-2.12

This package is using some functions which are marked deprecated in
newer versions of GnuTLS (>=2.12.x). (They are not yet removed, though.)
These functions will be removed in future releases. GnuTLS 2.12.x is
already available in experimental.

Excerpt from buildlog:

output_tls.c:125:4: warning: 'gnutls_certificate_type_set_priority' is 
deprecated (declared at /usr/include/gnutls/compat.h:347)
output_tls.c:222:3: warning: 'gnutls_certificate_type_set_priority' is 
deprecated (declared at /usr/include/gnutls/compat.h:347)


The gnutls_*_set_priority family of functions has been marked deprecated
in 2.12.x. These functions have been superceded by 
gnutls_priority_set_direct(). The replacement function was added in gnutls
stable release 2.2.0 (released 2007-12-14).

cu Andreas


--- End Message ---
--- Begin Message ---
Version: 0.6.0+nmu2+rm

Dear submitter,

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

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

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

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

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

Bug#706493: marked as done (python-abiword: missing python-gtk2 dependency)

[Debian Bug Tracking System]

Your message dated Fri, 14 Oct 2016 11:49:45 +
with message-id 
and subject line Bug#826400: Removed package(s) from unstable
has caused the Debian Bug report #706298,
regarding python-abiword: missing python-gtk2 dependency
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.)


-- 
706298: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706298
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-abiword
Version: 0.8.0-11
Severity: serious

Hi,

It seems another dependency is missing;  after installing the missing
python-gobject dependency (#706017), it then fails for me with:

> $ python -c "import abiword"
> 
> (pyabiword:57272): Gtk-CRITICAL **: IA__gtk_clipboard_get_for_display: 
> assertion `display != NULL' failed
> 
> (pyabiword:57272): Gtk-CRITICAL **: IA__gtk_clipboard_get_for_display: 
> assertion `display != NULL' failed
> Fatal Python error: can't initialise module pyabiword
> Aborted

This is a different error than bug #706017.

I was testing on a GNU/kFreeBSD system, and so kdump/ktrace explain the
reason for this:

>  57378 python2.7 CALL  stat(0xb1ccf0,0x7fffbf30)
>  57378 python2.7 NAMI  "/usr/lib/python2.7/dist-packages/gtk-2.0/gtk"
>  57378 python2.7 RET   stat -1 errno 2 No such file or directory
>  57378 python2.7 CALL  open(0xb1ccf0,0<>0,0)
>  57378 python2.7 NAMI  "/usr/lib/python2.7/dist-packages/gtk-2.0/gtk.so"
>  57378 python2.7 RET   open -1 errno 2 No such file or directory
>  57378 python2.7 CALL  open(0xb1ccf0,0<>0,0)
>  57378 python2.7 NAMI  "/usr/lib/python2.7/dist-packages/gtk-2.0/gtkmodule.so"
>  57378 python2.7 RET   open -1 errno 2 No such file or directory
>  57378 python2.7 CALL  open(0xb1ccf0,0<>0,0)
>  57378 python2.7 NAMI  "/usr/lib/python2.7/dist-packages/gtk-2.0/gtk.py"
>  57378 python2.7 RET   open -1 errno 2 No such file or directory
>  57378 python2.7 CALL  open(0xb1ccf0,0<>0,0)
>  57378 python2.7 NAMI  "/usr/lib/python2.7/dist-packages/gtk-2.0/gtk.pyc"
>  57378 python2.7 RET   open -1 errno 2 No such file or directory
>  57378 python2.7 CALL  stat(0xb1ccf0,0x7fffbf30)
>  57378 python2.7 NAMI  "/usr/lib/pymodules/python2.7/gtk"
>  57378 python2.7 RET   stat -1 errno 2 No such file or directory
>  57378 python2.7 CALL  open(0xb1ccf0,0<>0,0)
>  57378 python2.7 NAMI  "/usr/lib/pymodules/python2.7/gtk.so"
>  57378 python2.7 RET   open -1 errno 2 No such file or directory
>  57378 python2.7 CALL  open(0xb1ccf0,0<>0,0)
>  57378 python2.7 NAMI  "/usr/lib/pymodules/python2.7/gtkmodule.so"
>  57378 python2.7 RET   open -1 errno 2 No such file or directory
>  57378 python2.7 CALL  open(0xb1ccf0,0<>0,0)
>  57378 python2.7 NAMI  "/usr/lib/pymodules/python2.7/gtk.py"
>  57378 python2.7 RET   open -1 errno 2 No such file or directory
>  57378 python2.7 CALL  open(0xb1ccf0,0<>0,0)
>  57378 python2.7 NAMI  "/usr/lib/pymodules/python2.7/gtk.pyc"
>  57378 python2.7 RET   open -1 errno 2 No such file or directory
>  57378 python2.7 CALL  write(0x2,0x7fff9fa0,0x36)
>  57378 python2.7 GIO   fd 2 wrote 54 bytes
>"Fatal Python error: can't initialise module pyabiword
>"

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

Kernel: kFreeBSD 9.0-2-amd64-xenhvm
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages python-abiword depends on:
ii  libabiword-2.9  2.9.2+svn20120603-8
ii  libc0.1 2.13-37
pn  libglib2.0-0
ii  libgtk2.0-0 2.24.10-2
ii  python  2.7.3-4
ii  python2.6   2.6.8-1.1
ii  python2.7   2.7.3-6

python-abiword recommends no packages.

python-abiword suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.8.0-11+rm

Dear submitter,

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

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

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

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

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

Bug#831179: marked as done (pjproject: FTBFS with GCC 6: dh_makeshlibs: failing due to earlier errors)

[Debian Bug Tracking System]

Your message dated Fri, 14 Oct 2016 11:49:06 +
with message-id 
and subject line Bug#831179: fixed in pjproject 2.5.1~dfsg-3
has caused the Debian Bug report #831179,
regarding pjproject: FTBFS with GCC 6: dh_makeshlibs: failing due to earlier 
errors
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.)


-- 
831179: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831179
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pjproject
Version: 2.5.1~dfsg-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64

Hi,

During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html

Relevant part (hopefully):
> make[2]: Entering directory '/«PKGBUILDDIR»'
> mkdir -p /«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu/
> cp -af /«PKGBUILDDIR»/pjsip/lib/libpjsua2-x86_64-pc-linux-gnu.a 
> /«PKGBUILDDIR»/pjsip/lib/libpjsua-x86_64-pc-linux-gnu.a 
> /«PKGBUILDDIR»/pjsip/lib/libpjsip-ua-x86_64-pc-linux-gnu.a 
> /«PKGBUILDDIR»/pjsip/lib/libpjsip-simple-x86_64-pc-linux-gnu.a 
> /«PKGBUILDDIR»/pjsip/lib/libpjsip-x86_64-pc-linux-gnu.a 
> /«PKGBUILDDIR»/pjmedia/lib/libpjmedia-codec-x86_64-pc-linux-gnu.a 
> /«PKGBUILDDIR»/pjmedia/lib/libpjmedia-videodev-x86_64-pc-linux-gnu.a 
> /«PKGBUILDDIR»/pjmedia/lib/libpjmedia-x86_64-pc-linux-gnu.a 
> /«PKGBUILDDIR»/pjmedia/lib/libpjmedia-audiodev-x86_64-pc-linux-gnu.a 
> /«PKGBUILDDIR»/pjnath/lib/libpjnath-x86_64-pc-linux-gnu.a 
> /«PKGBUILDDIR»/pjlib-util/lib/libpjlib-util-x86_64-pc-linux-gnu.a  
> /«PKGBUILDDIR»/pjlib/lib/libpj-x86_64-pc-linux-gnu.a 
> /«PKGBUILDDIR»/pjsip/lib/libpjsua2.so.2v5 
> /«PKGBUILDDIR»/pjsip/lib/libpjsua2.so /«PKGBUILDDIR»/pjsip/lib/libpjsua.so.2 
> /«PKGBUILDDIR»/pjsip/lib/libpjsua.so 
> /«PKGBUILDDIR»/pjsip/lib/libpjsip-ua.so.2 
> /«PKGBUILDDIR»/pjsip/lib/libpjsip-ua.so 
> /«PKGBUILDDIR»/pjsip/lib/libpjsip-simple.so.2 
> /«PKGBUILDDIR»/pjsip/lib/libpjsip-simple.so 
> /«PKGBUILDDIR»/pjsip/lib/libpjsip.so.2 /«PKGBUILDDIR»/pjsip/lib/libpjsip.so 
> /«PKGBUILDDIR»/pjmedia/lib/libpjmedia-codec.so.2 
> /«PKGBUILDDIR»/pjmedia/lib/libpjmedia-codec.so 
> /«PKGBUILDDIR»/pjmedia/lib/libpjmedia-videodev.so.2 
> /«PKGBUILDDIR»/pjmedia/lib/libpjmedia-videodev.so 
> /«PKGBUILDDIR»/pjmedia/lib/libpjmedia.so.2 
> /«PKGBUILDDIR»/pjmedia/lib/libpjmedia.so 
> /«PKGBUILDDIR»/pjmedia/lib/libpjmedia-audiodev.so.2 
> /«PKGBUILDDIR»/pjmedia/lib/libpjmedia-audiodev.so 
> /«PKGBUILDDIR»/pjnath/lib/libpjnath.so.2 
> /«PKGBUILDDIR»/pjnath/lib/libpjnath.so 
> /«PKGBUILDDIR»/pjlib-util/lib/libpjlib-util.so.2 
> /«PKGBUILDDIR»/pjlib-util/lib/libpjlib-util.so 
> /«PKGBUILDDIR»/pjlib/lib/libpj.so.2 /«PKGBUILDDIR»/pjlib/lib/libpj.so 
> /«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu/
> mkdir -p /«PKGBUILDDIR»/debian/tmp/usr/include/
> for d in pjlib pjlib-util pjnath pjmedia pjsip; do \
>   cp -RLf $d/include/* /«PKGBUILDDIR»/debian/tmp/usr/include/; \
> done
> mkdir -p /«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig
> sed -e "s!@PREFIX@!/usr!" libpjproject.pc.in | \
>   sed -e "s!@INCLUDEDIR@!/usr/include!" | \
>   sed -e "s!@LIBDIR@!/usr/lib/x86_64-linux-gnu!" | \
>   sed -e "s/@PJ_VERSION@/2.5.1/" | \
>   sed -e "s!@PJ_LDLIBS@!!" | \
>   sed -e "s!@PJ_LDXXLIBS@!-lpjsua2 -lstdc++ -lpjsua -lpjsip-ua 
> -lpjsip-simple -lpjsip -lpjmedia-codec -lpjmedia -lpjmedia-videodev 
> -lpjmedia-audiodev -lpjmedia -lpjnath -lpjlib-util   -lsrtp -lpj -lm -lrt 
> -lpthread  -lvo-amrwbenc -lopus!" | \
>   sed -e "s!@PJ_INSTALL_CFLAGS@!!" | \
>   sed -e "s!@PJ_INSTALL_CXXFLAGS@!-I/usr/include -DPJ_AUTOCONF=1  
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -DPJ_IS_BIG_ENDIAN=0 -DPJ_IS_LITTLE_ENDIAN=1 -fPIC!" 
> > 
> /«PKGBUILDDIR»/debian/tmp//usr/lib/x86_64-linux-gnu/pkgconfig/libpjproject.pc
> make[2]: Leaving directory '/«PKGBUILDDIR»'
> # Disable it for now. This will wait (and be done properly) in
> # later versions:
> pybuild -d pjsip-apps/src/python --pyver 2.7 --install
> I: pybuild base:184: /usr/bin/python setup.py install --root 
> '/«PKGBUILDDIR»/debian/tmp' 
> running install
> running build
> running build_py
> running build_ext
> running install_lib
> creating 

Bug#706298: marked as done (python-abiword: missing python-gobject-2 dependency)

[Debian Bug Tracking System]

Your message dated Fri, 14 Oct 2016 11:49:45 +
with message-id 
and subject line Bug#826400: Removed package(s) from unstable
has caused the Debian Bug report #706298,
regarding python-abiword: missing python-gobject-2 dependency
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.)


-- 
706298: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706298
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: python-abiword
severity: serious
version: 0.8.0-11

python-abiword currently has a missing dependency on gobject

$ python -c "import abiword"
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/abiword/__init__.py", line 1,
in 
from abiword import *
ImportError: could not import gobject (error was: 'No module named gobject')

Installing python-gobject-2 resolves this problem.
--- End Message ---
--- Begin Message ---
Version: 0.8.0-11+rm

Dear submitter,

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

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

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

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

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

Bug#706017: marked as done (segmentation fault on import)

[Debian Bug Tracking System]

Your message dated Fri, 14 Oct 2016 11:49:45 +
with message-id 
and subject line Bug#826400: Removed package(s) from unstable
has caused the Debian Bug report #706017,
regarding segmentation fault on import
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.)


-- 
706017: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706017
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sugar-jigsawpuzzle-activity
Version: 8-1
Severity: grave

The jigsaw puzzle activity does not start. It shows a message with 
"Jigsaw Puzzle failed to start". See the attached log for a bit more
details.

Gaudenz

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

Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages sugar-jigsawpuzzle-activity depends on:
ii  python2.7.3-4
ii  python-abiword0.8.0-11
ii  python-central0.6.17
ii  python-cjson  1.0.5-4+b1
ii  python-gtk2   2.24.0-3+b1
ii  python-hippocanvas0.3.1-1.1
ii  python-sugar-0.96 [python-sugar]  0.96.0-1
ii  python-sugar-toolkit-0.96 [python-sugar-toolkit]  0.96.1-1
ii  python-telepathy  0.15.19-2.1

Versions of packages sugar-jigsawpuzzle-activity recommends:
ii  sugar-session-0.96 [sugar]  0.96.1-2.1

sugar-jigsawpuzzle-activity suggests no packages.

-- no debconf information
WARNING: gnome-keyring:: couldn't connect to: 
/run/user/gaudenz/keyring-ksGZBG/pkcs11: No such file or directory
/usr/lib/python2.7/dist-packages/abiword/__init__.py:1: Warning: specified 
instance size for type `AbiWidget' is smaller than the parent type's `GtkBin' 
instance size
  from abiword import *
/usr/lib/python2.7/dist-packages/abiword/__init__.py:1: Warning: 
g_type_get_qdata: assertion `node != NULL' failed
  from abiword import *
Terminated by signal 11, pid 3687 data (None, ', mode 'w' 
at 0x1bbc930>, '7a51a54edc0c3581a10b7ec7ca29ab2c04cb7c41')
--- End Message ---
--- Begin Message ---
Version: 0.8.0-11+rm

Dear submitter,

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

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

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

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

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

Bug#727084: marked as done (src:python-abiword: libabiword-3.0 mini-transition)

[Debian Bug Tracking System]

Your message dated Fri, 14 Oct 2016 11:49:45 +
with message-id 
and subject line Bug#826400: Removed package(s) from unstable
has caused the Debian Bug report #727084,
regarding src:python-abiword: libabiword-3.0 mini-transition
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.)


-- 
727084: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727084
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-abiword
Version: 0.8.0-11
Severity: normal

Dear Jonas,

"libabiword-3.0" is in experimental and "python-abiword" is the only
reverse dependency that is still bound to "libabiword-2.9". Please
consider updating your package for this mini-transition.

With minimum changes to Build-Depends and to "configure.in" (see
below) I was able to build "python-abiword" successfully with
"libabiword-3.0", however I can't test the run-time functionality of
the re-built package.


--- a/configure.in
+++ b/configure.in
@@ -16,9 +16,9 @@
 AC_STDC_HEADERS
 AM_PROG_LIBTOOL
 AC_C_CONST
 
-abi_pkg='abiword-2.9 >= 2.9.0'
+abi_pkg='abiword-3.0 >= 3.0.0'
 PKG_CHECK_MODULES(ABIWORD, "$abi_pkg")
 AC_SUBST(ABIWORD_CFLAGS)
 AC_SUBST(ABIWORD_LIBS)


Thanks.

-- 
Best wishes,
 Dmitry Smirnov
 GPG key : 4096R/53968D1B
--- End Message ---
--- Begin Message ---
Version: 0.8.0-11+rm

Dear submitter,

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

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

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

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

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

Bug#736598: marked as done ([src:hotot] Sourceless file)

[Debian Bug Tracking System]

Your message dated Fri, 14 Oct 2016 11:46:25 +
with message-id 
and subject line Bug#743767: Removed package(s) from unstable
has caused the Debian Bug report #736598,
regarding [src:hotot] Sourceless file
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.)


-- 
736598: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736598
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:hotot
Version:   1:0.9.8.14-2
Severity: serious
User: debian...@lists.debian.org
Usertags: source-contains-prebuilt-javascript-object
X-Debbugs-CC: ftpmas...@debian.org

I could not found the source of:
hotot 1:0.9.8.14-2 (src)
data/js/jquery.transit.min.js
data/js/moment.min.js
data/ext/org.hotot.stat/jquery.flot.min.js
data/ext/org.hotot.stat/jquery.flot.pie.min.js


Bastien
--- End Message ---
--- Begin Message ---
Version: 1:0.9.8.14-3+rm

Dear submitter,

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

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

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

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

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

Bug#810133: marked as done (proll: FTBFS: Build-Depends-Indep: sparc-utils which is in nothing newer than oldstable)

[Debian Bug Tracking System]

Your message dated Fri, 14 Oct 2016 11:45:20 +
with message-id 
and subject line Bug#658886: Removed package(s) from unstable
has caused the Debian Bug report #810133,
regarding proll: FTBFS: Build-Depends-Indep: sparc-utils which is in nothing 
newer than oldstable
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.)


-- 
810133: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810133
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: proll
Version: 18-6
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 as sparc-utils is gone:

The following packages have unmet dependencies:
 pbuilder-satisfydepends-dummy : Depends: sparc-utils which is a virtual 
package and is not provided by any available package.



sparc-utils was removed from testing 2014-04-27 and hasn't had any
uploads since 2007.

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

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Version: 18-6+rm

Dear submitter,

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

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

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

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

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

Bug#728578: marked as done (hotot: segfaults on startup)

[Debian Bug Tracking System]

Your message dated Fri, 14 Oct 2016 11:46:25 +
with message-id 
and subject line Bug#743767: Removed package(s) from unstable
has caused the Debian Bug report #728578,
regarding hotot: segfaults on startup
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.)


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

Hi,

hotot segfaults on startup.

gdb session follows:
$ gdb --args python /usr/bin/hotot
GNU gdb (GDB) 7.6 (Debian 7.6-5)
Copyright (C) 2013 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".
For bug reporting instructions, please see:
...
Reading symbols from /usr/bin/python2.7...(no debugging symbols found)...done.
(gdb) r
Starting program: /usr/bin/python2.7 /usr/bin/hotot
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe1f42700 (LWP 21595)]
[New Thread 0x7fffa163d700 (LWP 21596)]
[New Thread 0x7fff9893e700 (LWP 21597)]
[New Thread 0x7fff90212700 (LWP 21600)]
[New Thread 0x7fff8fa11700 (LWP 21601)]
[New Thread 0x7fff8f210700 (LWP 21602)]
java version "1.6.0_27"
OpenJDK Runtime Environment (IcedTea6 1.12.5) (6b27-1.12.5-2)
OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)
[New Thread 0x7fff8e183700 (LWP 21616)]
[New Thread 0x7fff8d982700 (LWP 21617)]
[New Thread 0x7fff8d181700 (LWP 21618)]
[New Thread 0x7fff8c980700 (LWP 21619)]
[New Thread 0x7fff7f7ee700 (LWP 21620)]
[New Thread 0x7fff7efed700 (LWP 21621)]
[New Thread 0x7fff7e6ea700 (LWP 21622)]
[New Thread 0x7fff7dee9700 (LWP 21623)]
[New Thread 0x7fff6bdbd700 (LWP 21624)]
[New Thread 0x7fff6b593700 (LWP 21625)]
[New Thread 0x7fff5fb30700 (LWP 21626)]
[New Thread 0x7fff5f32f700 (LWP 21627)]
** Message: console message: file:///usr/share/hotot/js/hotot.js @274: [init] 
on_load_finish()

** Message: console message: file:///usr/share/hotot/js/hotot.js @274: [init] 
on_load_finish() -> ext.load_builtin_exts();

** Message: console message: file:///usr/share/hotot/js/hotot.js @274: [Load 
Extension] ./ext/org.hotot.cfw/entry.js

[New Thread 0x7fff5e352700 (LWP 21628)]
[New Thread 0x7fff47df7700 (LWP 21629)]
** Message: console message: file:///usr/share/hotot/js/hotot.js @274: [Load 
Extension] ./ext/org.hotot.gmap/entry.js

** Message: console message: file:///usr/share/hotot/js/hotot.js @274: [Load 
Extension] ./ext/org.hotot.sample/entry.js

[init] overlay_variables()
[Load Extension] ./ext/org.hotot.shorturl/entry.js
[Load Extension] ./ext/org.hotot.expandurls/entry.js
[Load Extension] ./ext/org.hotot.translate/entry.js
[Load Extension] ./ext/org.hotot.stat/entry.js
[Load Extension] ./ext/org.hotot.appmask/entry.js
[Load Extension] ./ext/org.hotot.imghp/entry.js
[init] on_load_finish() -> ext.init_exts();
[Init Extension] Hotot Content Firewall
[Init Extension] Hotot GMap
[Init Extension] Sample
[Init Extension] Hotot Short URL
[Init Extension] Expand shortened urls (on hover)
[Init Extension] Hotot Translate
[Init Extension] Hotot User Stat
[Init Extension] AppMask
[Init Extension] Google image search
[init] on_load_finish() -> push settings
[init] on_load_finish() -> i18n.init()
[i18n] Use locale: en
[init] on_load_finish() -> init_ui()
[init] init_dialogs()
[init] done!
[Thread 0x7fff7efed700 (LWP 21621) exited]
[Thread 0x7fff7dee9700 (LWP 21623) exited]
[Req] 
{"type":"GET","url":"https://api.twitter.com/1.1/account/verify_credentials.json?oauth_consumer_key=***_nonce=***_signature=***_signature_method=HMAC-SHA1_timestamp=1383468908_token=***_version=1.0=Hotot","data":{}}
[Req] 
{"type":"GET","url":"https://twitter.com/phoenix_search.phoenix?format=phoenix_entities=true_consumer_key=***_nonce=***_signature=***_signature_method=HMAC-SHA1_timestamp=1383468909_token=***_version=1.0=rpp%3D100%26q%3D%23debian%26page%3D1=%23debian=","data":{}}
[Req] 

Bug#749253: marked as done (hotot-gtk: depends on python-webkit which is deprecated)

[Debian Bug Tracking System]

Your message dated Fri, 14 Oct 2016 11:46:25 +
with message-id 
and subject line Bug#743767: Removed package(s) from unstable
has caused the Debian Bug report #749253,
regarding hotot-gtk: depends on python-webkit which is deprecated
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.)


-- 
749253: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749253
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: hotot-gtk
Version: 1:0.9.8.14-3
Severity: important
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs python-webkit webkit1

Hi,

hotot-gtk depends on python-webkit, which is deprecated and going to
be removed from the archive. hotot-gtk should switch to using the
GObject Introspection bindings for webkit, ideally gir1.2-webkit2-3.0
for Webkit2 and gtk+3 as upstream has already dropped WebKit1 (so
gir1.2-webkit-1.0 and gir1.2-webkit-3.0 are likely to be dropped from
Debian in the near future). This would mean switching to GObject
Introspection for other bindings as well, e.g. GLib and GTK+, so
making the switch to GTK+ 3 at the same time would make a lot of
sense.

For more information on GObject Introspection see [1] and [2].

If you have any question don't hesitate to ask.

Emilio

[1] https://wiki.gnome.org/action/show/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/action/show/Projects/PyGObject 
--- End Message ---
--- Begin Message ---
Version: 1:0.9.8.14-3+rm

Dear submitter,

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

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

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

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

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

Bug#729975: marked as done (hotot: Wheezy version no longer usable with Twitter, uses retired 1.0 API)

[Debian Bug Tracking System]

Your message dated Fri, 14 Oct 2016 11:46:25 +
with message-id 
and subject line Bug#743767: Removed package(s) from unstable
has caused the Debian Bug report #729975,
regarding hotot: Wheezy version no longer usable with Twitter, uses retired 1.0 
API
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.)


-- 
729975: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729975
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: hotot
Version: 1:0.9.7.32+git20111213.1d89daf-1.1
Severity: grave
Tags: upstream
Control: fixed -1 1:0.9.8.14-2

Dear Maintainer,

The version of hotot in wheezy is currently unusable with Twitter (though the
identi.ca backend may work, I did not test). The problem is that it uses
Twitter's 1.0 API, which has been retired on June 11, 2013.

There are two possible solutions:

- upload a new upstream release to wheezy, though I doubt the Release Team
  would accept that;

- or remove hotot from wheezy, and upload a recent version to wheezy-backports.

The second solution should be very easy to implement: I was able to compile
hotot 1:0.9.8.14-2 on wheezy without any change to the source package.

Cheers,

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


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 1:0.9.8.14-3+rm

Dear submitter,

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

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

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

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

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

Bug#760623: marked as done (hotot: Hotot fails to start with import error)

[Debian Bug Tracking System]

Your message dated Fri, 14 Oct 2016 11:46:25 +
with message-id 
and subject line Bug#743767: Removed package(s) from unstable
has caused the Debian Bug report #760623,
regarding hotot: Hotot fails to start with import error
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.)


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

Dear Maintainer,

Hotot fails to start with the following error and backtrace.

Traceback (most recent call last):
  File "/usr/bin/hotot", line 13, in 
from hotot import hotot
  File "/usr/lib/python2.7/dist-packages/hotot/hotot.py", line 10, in 
import view
  File "/usr/lib/python2.7/dist-packages/hotot/view.py", line 4, in 
import webkit
  File "/usr/lib/pymodules/python2.7/webkit/__init__.py", line 21, in 
import webkit
ImportError: /usr/lib/x86_64-linux-gnu/libwebkitgtk-1.0.so.0: undefined symbol: 
cairo_gl_surface_get_width


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

Kernel: Linux 3.14-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages hotot depends on:
ii  hotot-gtk  1:0.9.8.14-3

Versions of packages hotot recommends:
ii  xdg-utils  1.1.0~rc1+git20111210-7.1

hotot suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1:0.9.8.14-3+rm

Dear submitter,

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

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

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

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

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

Bug#840736: gnome-maps: always offline cant browse any map

[Laurent Bigonville]

On Fri, 14 Oct 2016 20:58:34 +1100 Fulano Diego Perez 
 wrote:


Hi,

>
> cannot browse any maps
>
> always reports offline with active internet comms
>
> ignore missing pkgs below - report bug has confusion with this
>

I cannot reproduce this.

Are you using network-manager?

Bug#840736: gnome-maps: always offline cant browse any map

[Fulano Diego Perez]

Package: gnome-maps
Version: 3.22.0-1
Severity: grave
Justification: renders package unusable


cannot browse any maps

always reports offline with active internet comms

ignore missing pkgs below - report bug has confusion with this



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

Kernel: Linux 4.7.0-1-amd64
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)

Versions of packages gnome-maps depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2
ii  geoclue-2.0  2.4.4-1
ii  gir1.2-champlain-0.120.12.14-1
pn  gir1.2-clutter-1.0   
ii  gir1.2-cogl-1.0  1.22.2-2
ii  gir1.2-gdkpixbuf-2.0 2.36.0-1
ii  gir1.2-geoclue-2.0   2.4.4-1
ii  gir1.2-geocodeglib-1.0   3.20.1-1
ii  gir1.2-gfbgraph-0.2  0.2.3-1
ii  gir1.2-glib-2.0  1.50.0-1
ii  gir1.2-goa-1.0   3.22.0-1
ii  gir1.2-gtk-3.0   3.22.1-1
ii  gir1.2-gtkchamplain-0.12 0.12.14-1
ii  gir1.2-gtkclutter-1.01.8.2-1
pn  gir1.2-gweather-3.0  
ii  gir1.2-rest-0.7  0.8.0-1
ii  gir1.2-secret-1  0.18.5-2
ii  gir1.2-soup-2.4  2.56.0-1
ii  gir1.2-webkit2-4.0   2.14.0-1
ii  gjs  1.46.0-1+b1
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-3
ii  libcairo-gobject21.14.6-1+b1
ii  libcairo21.14.6-1+b1
ii  libchamplain-0.12-0  0.12.14-1
pn  libclutter-1.0-0 
ii  libcogl-pango20  1.22.2-2
ii  libcogl-path20   1.22.2-2
ii  libcogl201.22.2-2
ii  libdrm2  2.4.71-1
ii  libegl1-mesa [libegl1-x11]   12.0.3-1
ii  libfolks25   0.11.2-1+b1
ii  libgbm1  12.0.3-1
ii  libgdk-pixbuf2.0-0   2.36.0-1
pn  libgee-0.8-2 
pn  libgeocode-glib0 
ii  libglib2.0-0 2.50.0-2
ii  libglib2.0-bin   2.50.0-2
ii  libgtk-3-0   3.22.1-1
ii  libjson-glib-1.0-0   1.2.2-1
ii  libpango-1.0-0   1.40.3-2
ii  libpangocairo-1.0-0  1.40.3-2
pn  librest-0.7-0
ii  libsoup2.4-1 2.56.0-1
ii  libwayland-client0   1.11.0-2
pn  libwayland-cursor0   
ii  libwayland-egl1-mesa [libwayland-egl1]   12.0.3-1
ii  libwayland-server0   1.11.0-2
ii  libx11-6 2:1.6.3-1
ii  libxcomposite1   1:0.4.4-1
ii  libxdamage1  1:1.1.4-2+b1
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.2-1
ii  libxi6   2:1.7.6-1
pn  libxkbcommon0
ii  libxml2  2.9.4+dfsg1-2
ii  libxrandr2   2:1.5.0-1

gnome-maps recommends no packages.

gnome-maps suggests no packages.

-- no debconf information

Bug#840573: unicon: DFSG-incompatible license

[Adrian Bunk]

On Thu, Oct 13, 2016 at 11:58:00AM +0200, Santiago Vila wrote:
> On Wed, 12 Oct 2016, Joao Eriberto Mota Filho wrote:
> 
> > Source: unicon
> > Severity: serious
> > Tags: upstream
> > Justification: Policy 2.2.1
> > 
> > Dear Maintainer,
> > 
> > The file unicon/ImmModules/cxterm/utils/HZtable.h has the following license:
> > 
> > Copyright 1994,1995 by Yongguang Zhang.  All Rights Reserved
> > 
> > Permission to retain, use, modify, copy, and distribute CXTERM 5.0
> > in source or binary and its documentation (hereafter, the Software)
> > for non-commercial purpose is hereby granted to you without a fee,
> > provided that this entire copyright and permission notice appear in
> > all such copies, that no charge be associated with such copies,
> > that distribution of derivative works (including value-added
> > distributions such as with additional input dictionaries or fonts)
> > include clarification that such added or derived parts are not from
> > the original Software, and that the names of the author(s) not be
> > used to endorse or promote such works.
> > 
> > THE AUTHOR(S) DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, 
> > INCLUDING
> > ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL
> > THE AUTHOR(S) BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES 
> > OR
> > ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
> > WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION,
> > ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS 
> > SOFTWARE.
> > 
> > There is a restriction for commercial use.
> 
> Probably not the intent (as this is an old license), but certainly
> it's the letter.
> 
> BTW: There is a similar wording in the Perl license: "You may not
> charge a fee for this Package itself."
>...

The Perl situation is different.


In Perl this is part of a larger clause in the Artistic licence.

The clause in the Artistic licence explicitely allows charging money for 
a software distribution that includes perl, and that makes it DFSG-free.

This is a borderline case, and likely the DFSG are worded this way to 
allow code under the Artistic licence in main.


unicon does not allow usage for commercial purpose, which is a clear 
violation of DFSG clause 6.

Using Debian in your business, or selling a computer with Debian 
installed, are pretty basic usecases that are not possible with
such licencing.


> Thanks.

cu
Adrian

-- 

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

Bug#840692: [pkg-cinnamon] Bug#840692: nemo-python: plugin is not recognized or loaded by Nemo

[Maximiliano Curia]

Control: tag -1 + unreproducible
Control: severity -1 normal

¡Hola Nathan!

El 2016-10-13 a las 15:25 -0700, Nathan Osman escribió:
Package: nemo-python 
Version: 3.0.0-3 
Severity: grave 
Justification: renders package unusable


The nemo-python extension is not displayed in the "Extensions" list under 
Edit->Plugins. This is further confirmed by the fact that none of the Python 
extensions I have installed work. Running Nemo under KDE, Gnome, and Cinnamon 
doesn't appear to make any difference.


The libnemo-python extension provides a meta extension that allows other 
extensions to be written in python, and as such it's not listed in nemo as an 
individual extension.


Using the provided examples (located in /usr/share/doc/nemo-python/examples/) 
it works fine. Please try testing it with these, the 
/usr/share/doc/nemo-python/examples/README file explains how to 
install this test extensions.


Happy hacking,
--
"It is not the task of the University to offer what society asks for, but to
give what society needs."
-- Edsger W. Dijkstra
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Processed: Re: [pkg-cinnamon] Bug#840692: nemo-python: plugin is not recognized or loaded by Nemo

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + unreproducible
Bug #840692 [nemo-python] nemo-python: plugin is not recognized or loaded by 
Nemo
Added tag(s) unreproducible.
> severity -1 normal
Bug #840692 [nemo-python] nemo-python: plugin is not recognized or loaded by 
Nemo
Severity set to 'normal' from 'grave'

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

Bug#840733: e2fsprogs contains non-free file

[Adrian Bunk]

Source: e2fsprogs
Version: 1.43.3-1
Severity: serious

lib/et/test_cases/imap_err.et:

# Copyright 1998 Carnegie Mellon University
# 
# No warranties, either expressed or implied, are made regarding the
# operation, use, or results of the software.
#
# Permission to use, copy, modify and distribute this software and its
# documentation is hereby granted for non-commercial purposes only
# provided that this copyright notice appears in all copies and in
# supporting documentation.
#
# Permission is also granted to Internet Service Providers and others
# entities to use the software for internal purposes.
#
# The distribution, modification or sale of a product which uses or is
# based on the software, in whole or in part, for commercial purposes or
# benefits requires specific, additional permission from:
#
#  Office of Technology Transfer
#  Carnegie Mellon University
#  5000 Forbes Avenue
#  Pittsburgh, PA  15213-3890
#  (412) 268-4387, fax: (412) 268-7395
#  tech-trans...@andrew.cmu.edu


The "for non-commercial purposes only" is a clear violation
of clause 6 of the DFSG.

Bug#840732: qbrew: FTBFS: install: cannot create regular file '/usr/bin/qbrew': Permission denied

[Chris Lamb]

Source: qbrew
Version: 0.4.1-6
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,

qbrew fails to build from source in unstable/amd64:

  [..]

  Setting up qt5-qmake:amd64 (5.6.1+dfsg-3+b1) ...
  Processing triggers for libc-bin (2.24-3) ...
  Processing triggers for udev (231-9) ...
  Setting up x11proto-gl-dev (1.4.17-1) ...
  Processing triggers for systemd (231-9) ...
  Setting up libmtdev1:amd64 (1.1.5-1) ...
  Setting up libpciaccess0:amd64 (0.13.4-1) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up libxkbcommon0:amd64 (0.6.1-1) ...
  Setting up libgudev-1.0-0:amd64 (230-3) ...
  Setting up libdrm-radeon1:amd64 (2.4.71-1) ...
  Setting up liborc-0.4-0:amd64 (1:0.4.26-1) ...
  Setting up libpcre16-3:amd64 (2:8.39-2) ...
  Setting up libxdmcp6:amd64 (1:1.1.2-1.1) ...
  Setting up libdrm-nouveau2:amd64 (2.4.71-1) ...
  Setting up x11-common (1:7.7+16) ...
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of start.
  Setting up libx11-data (2:1.6.3-1) ...
  Setting up libxau6:amd64 (1:1.0.8-1) ...
  Setting up libdbus-1-3:amd64 (1.10.12-1) ...
  Setting up libavahi-common-data:amd64 (0.6.32-1) ...
  Setting up libwayland-server0:amd64 (1.11.0-2) ...
  Setting up libwebp6:amd64 (0.5.1-2) ...
  Setting up libqt5core5a:amd64 (5.6.1+dfsg-3+b1) ...
  Setting up libgstreamer-plugins-base1.0-0:amd64 (1.8.3-1) ...
  Setting up libqt5dbus5:amd64 (5.6.1+dfsg-3+b1) ...
  Setting up fontconfig-config (2.11.0-6.7) ...
  Setting up libqt5network5:amd64 (5.6.1+dfsg-3+b1) ...
  Setting up x11proto-core-dev (7.0.29-1) ...
  Setting up libwacom2:amd64 (0.22-1) ...
  Setting up libdrm-amdgpu1:amd64 (2.4.71-1) ...
  Setting up libxshmfence-dev:amd64 (1.2-1) ...
  Setting up libgbm1:amd64 (12.0.3-1) ...
  Setting up libqt5test5:amd64 (5.6.1+dfsg-3+b1) ...
  Setting up libinput10:amd64 (1.5.0-1) ...
  Setting up libharfbuzz0b:amd64 (1.2.7-1+b1) ...
  Setting up libxau-dev:amd64 (1:1.0.8-1) ...
  Setting up libdrm-intel1:amd64 (2.4.71-1) ...
  Setting up libxdmcp-dev:amd64 (1:1.1.2-1.1) ...
  Setting up libqt5clucene5:amd64 (5.6.1-2) ...
  Setting up libqt5xml5:amd64 (5.6.1+dfsg-3+b1) ...
  Setting up libqt5sql5:amd64 (5.6.1+dfsg-3+b1) ...
  Setting up libice6:amd64 (2:1.0.9-1+b1) ...
  Setting up libavahi-common3:amd64 (0.6.32-1) ...
  Setting up libxcb1:amd64 (1.12-1) ...
  Setting up x11proto-input-dev (2.3.2-1) ...
  Setting up libqt5concurrent5:amd64 (5.6.1+dfsg-3+b1) ...
  Setting up libxcb-xkb1:amd64 (1.12-1) ...
  Setting up libqt5qml5:amd64 (5.6.1-11) ...
  Setting up libxcb-xinerama0:amd64 (1.12-1) ...
  Setting up libxcb-present0:amd64 (1.12-1) ...
  Setting up libfontconfig1:amd64 (2.11.0-6.7) ...
  Setting up qtbase5-dev-tools (5.6.1+dfsg-3+b1) ...
  Setting up libxcb-dri2-0:amd64 (1.12-1) ...
  Setting up libsm6:amd64 (2:1.2.2-1+b1) ...
  Setting up libxcb-dri3-0:amd64 (1.12-1) ...
  Setting up libxcb-glx0:amd64 (1.12-1) ...
  Setting up libxcb-randr0:amd64 (1.12-1) ...
  Setting up libxcb-xfixes0:amd64 (1.12-1) ...
  Setting up libxcb-icccm4:amd64 (0.4.1-1) ...
  Setting up libxcb-render0:amd64 (1.12-1) ...
  Setting up libxcb-util0:amd64 (0.3.8-3) ...
  Setting up libdrm-dev:amd64 (2.4.71-1) ...
  Setting up libx11-6:amd64 (2:1.6.3-1) ...
  Setting up libxkbcommon-x11-0:amd64 (0.6.1-1) ...
  Setting up libxcb-sync1:amd64 (1.12-1) ...
  Setting up libx11-xcb1:amd64 (2:1.6.3-1) ...
  Setting up x11proto-xext-dev (7.3.0-1) ...
  Setting up libxcomposite1:amd64 (1:0.4.4-1) ...
  Setting up libxcb-shm0:amd64 (1.12-1) ...
  Setting up libxcb-shape0:amd64 (1.12-1) ...
  Setting up libxrender1:amd64 (1:0.9.9-2) ...
  Setting up libxcb1-dev:amd64 (1.12-1) ...
  Setting up libxcb-glx0-dev:amd64 (1.12-1) ...
  Setting up libavahi-client3:amd64 (0.6.32-1) ...
  Setting up libxcb-keysyms1:amd64 (0.4.0-1) ...
  Setting up libx11-dev:amd64 (2:1.6.3-1) ...
  Setting up libxcb-sync-dev:amd64 (1.12-1) ...
  Setting up fontconfig (2.11.0-6.7) ...
  Regenerating fonts cache... done.
  Setting up libcups2:amd64 (2.2.1-1) ...
  Setting up libegl1-mesa:amd64 (12.0.3-1) ...
  Setting up libx11-xcb-dev:amd64 (2:1.6.3-1) ...
  Setting up libxcb-render-util0:amd64 (0.3.9-1) ...
  Setting up libxcb-image0:amd64 (0.4.0-1) ...
  Setting up mesa-common-dev:amd64 (12.0.3-1) ...
  Setting up libxext6:amd64 (2:1.3.3-1) ...
  Setting up libxfixes3:amd64 (1:5.0.2-1) ...
  Setting up x11proto-fixes-dev (1:5.0-2) ...
  Setting up libxcb-dri2-0-dev:amd64 (1.12-1) ...
  Setting up libxcb-render0-dev:amd64 (1.12-1) ...
  Setting up x11proto-damage-dev (1:1.2.1-2) ...
  Setting up libxcb-dri3-dev:amd64 (1.12-1) ...
  Setting up libxext-dev:amd64 (2:1.3.3-1) ...
  Setting up libxcb-shape0-dev:amd64 (1.12-1) ...
  Setting up libxxf86vm1:amd64 

Bug#840575: [buildd-tools-devel] Bug#840575: sbuild bpo: uses non-available option gnupg --pinentry-mode

[Luca Falavigna]

Hi,

2016-10-14 7:36 GMT+02:00 Johannes Schauer :
> don't know if our current sbuild backporter Luca (in CC) would be willing to
> write such a patch, especially considering that
>
>  - it is a feature of sbuild since version 0.67.0 (I corrected the wiki page
>accordingly) to *not* require signing of the internal dummy repository (and
>thus you don't need to run sbuild-update --keygen anymore) and that
>  - the next stable release is not far away.

Indeed, I think it's pointless to write a patch given that we no
longer suggest to sign the internal repository, and also that explains
why I didn't notice this issue since in order to build the sbuild
backport I used the very same version found in unstable/testing,
installed on a machine running stable where my Deb-o-Matic farm is
running on :-)

-- 
Cheers,
Luca

Bug#840728: libp11: FTBFS: openssl-1.0.2/engines: No such file or directory

[Chris Lamb]

Source: libp11
Version: 0.4.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,

libp11 fails to build from source in unstable/amd64:

  [..]

  checking if gcc supports -c -o file.o... (cached) yes
  checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared 
libraries... yes
  checking whether -lc should be explicitly linked in... no
  checking dynamic linker characteristics... GNU/Linux ld.so
  checking how to hardcode library paths into programs... immediate
  checking whether stripping libraries is possible... yes
  checking if libtool supports shared libraries... yes
  checking whether to build shared libraries... yes
  checking whether to build static libraries... yes
  checking for windres... no
  checking for ANSI C header files... (cached) yes
  checking for sys/wait.h that is POSIX.1 compatible... yes
  checking errno.h usability... yes
  checking errno.h presence... yes
  checking for errno.h... yes
  checking fcntl.h usability... yes
  checking fcntl.h presence... yes
  checking for fcntl.h... yes
  checking malloc.h usability... yes
  checking malloc.h presence... yes
  checking for malloc.h... yes
  checking for stdlib.h... (cached) yes
  checking for inttypes.h... (cached) yes
  checking for string.h... (cached) yes
  checking for strings.h... (cached) yes
  checking sys/time.h usability... yes
  checking sys/time.h presence... yes
  checking for sys/time.h... yes
  checking for unistd.h... (cached) yes
  checking locale.h usability... yes
  checking locale.h presence... yes
  checking for locale.h... yes
  checking getopt.h usability... yes
  checking getopt.h presence... yes
  checking for getopt.h... yes
  checking for dlfcn.h... (cached) yes
  checking utmp.h usability... yes
  checking utmp.h presence... yes
  checking for utmp.h... yes
  checking for doxygen... no
  checking for library containing dlopen... -ldl
  checking for __register_atfork... yes
  checking for OPENSSL... yes
  checking that generated files are newer than configure... done
  configure: creating ./config.status
  config.status: creating Makefile
  config.status: creating src/Makefile
  config.status: creating src/libp11.pc
  config.status: creating src/libp11.rc
  config.status: creating src/pkcs11.rc
  config.status: creating doc/Makefile
  config.status: creating doc/doxygen.conf
  config.status: creating examples/Makefile
  config.status: creating tests/Makefile
  config.status: creating src/config.h
  config.status: executing depfiles commands
  config.status: executing libtool commands
  configure: WARNING: unrecognized options: --disable-maintainer-mode
  
  libp11 has been configured with the following options:
  
  Version: 0.4.1
  libp11 directory:/usr/lib/x86_64-linux-gnu
  Engine directory:/usr/lib/x86_64-linux-gnu/openssl-1.0.2/engines
  Default PKCS11 module:   
  API doc support: no
  
  Host:x86_64-pc-linux-gnu
  Compiler:gcc
  Preprocessor flags:  -Wdate-time -D_FORTIFY_SOURCE=2
  Compiler flags:  -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161014102716.2UE5QNAzsC.db.libp11/libp11-0.4.1=.
 -fstack-protector-strong -Wformat -Werror=format-security
  Linker flags:-Wl,-z,relro
  Libraries:   -ldl 
  
  OPENSSL_CFLAGS:  
  OPENSSL_LIBS:-lcrypto
  
 dh_auto_build
make -j1
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20161014102716.2UE5QNAzsC.db.libp11/libp11-0.4.1'
  Making all in src
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20161014102716.2UE5QNAzsC.db.libp11/libp11-0.4.1/src'
  make  all-am
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20161014102716.2UE5QNAzsC.db.libp11/libp11-0.4.1/src'
  /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.   
-Wdate-time -D_FORTIFY_SOURCE=2-g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161014102716.2UE5QNAzsC.db.libp11/libp11-0.4.1=.
 -fstack-protector-strong -Wformat -Werror=format-security -c -o 
pkcs11_la-eng_front.lo `test -f 'eng_front.c' || echo './'`eng_front.c
  libtool: compile:  gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161014102716.2UE5QNAzsC.db.libp11/libp11-0.4.1=.
 -fstack-protector-strong -Wformat -Werror=format-security -c eng_front.c  
-fPIC -DPIC -o .libs/pkcs11_la-eng_front.o
  libtool: compile:  gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161014102716.2UE5QNAzsC.db.libp11/libp11-0.4.1=.
 -fstack-protector-strong -Wformat -Werror=format-security -c eng_front.c -o 
pkcs11_la-eng_front.o >/dev/null 2>&1
  /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.   
-Wdate-time -D_FORTIFY_SOURCE=2-g -O2 

Bug#840725: libhmsbeagle: FTBFS and bd-uninstallable almost everywhere

[Andreas Tille]

Hi Emilio,

this is a known issue which would be fixed if khronos-opencl-clhpp would
be accepted by ftpmaster in new queue.  I've given a hint to frpmaster
about this hoping that this can be solved quickly but unfortunately with
no success so far. :-(

Kind regards

  Andreas.

On Fri, Oct 14, 2016 at 10:11:11AM +0200, Emilio Pozuelo Monfort wrote:
> Source: libhmsbeagle
> Version: 2.1.2+20160525-1
> Severity: serious
> 
> Hi,
> 
> Your package failed to build on i386 with:
> 
> /«BUILDDIR»/libhmsbeagle-2.1.2+20160525/libhmsbeagle/GPU/GPUInterface.h: In 
> member function 'void opencl_device::GPUInterface::PrintfDeviceVector(GPUPtr, 
> int, double, int*, Real)':
> /«BUILDDIR»/libhmsbeagle-2.1.2+20160525/libhmsbeagle/GPU/GPUInterface.h:188:55:
>  error: there are no arguments to 'malloc' that depend on a template 
> parameter, so a declaration of 'malloc' must be available [-fpermissive]
>   Real* hPtr = (Real*) malloc(sizeof(Real) * length);
>^
> 
> 
> Also, the package is bd-uninstallable everywhere else because libpoclu-dev
> is not available.
> 
> See https://buildd.debian.org/status/package.php?p=libhmsbeagle
> 
> Emilio
> 
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable
>   APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), 
> (500, 'unstable-debug')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386, armhf
> 
> Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging

-- 
http://fam-tille.de

Bug#840725: libhmsbeagle: FTBFS and bd-uninstallable almost everywhere

[Emilio Pozuelo Monfort]

Source: libhmsbeagle
Version: 2.1.2+20160525-1
Severity: serious

Hi,

Your package failed to build on i386 with:

/«BUILDDIR»/libhmsbeagle-2.1.2+20160525/libhmsbeagle/GPU/GPUInterface.h: In 
member function 'void opencl_device::GPUInterface::PrintfDeviceVector(GPUPtr, 
int, double, int*, Real)':
/«BUILDDIR»/libhmsbeagle-2.1.2+20160525/libhmsbeagle/GPU/GPUInterface.h:188:55: 
error: there are no arguments to 'malloc' that depend on a template parameter, 
so a declaration of 'malloc' must be available [-fpermissive]
  Real* hPtr = (Real*) malloc(sizeof(Real) * length);
   ^


Also, the package is bd-uninstallable everywhere else because libpoclu-dev
is not available.

See https://buildd.debian.org/status/package.php?p=libhmsbeagle

Emilio

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

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

Bug#840685: tomcat8: DSA-3670 incomplete

[paul . szabo]

Dear Salvatore,

> ... if the attacher created a symlink between the rm and the mkdir
> then mkdir will still fail with -p on a symlink.  (Or do I miss
> something?). ...

Yes, you missed a simple test:

$ mkdir mydir
$ ln -s mydir mylink
$ ls -ld my*
drwx-- 2 psz amstaff 4096 Oct 14 18:46 mydir
lrwxrwxrwx 1 psz amstaff5 Oct 14 18:46 mylink -> mydir
$ mkdir -p mylink || echo failed
$ mkdir -p mylink; echo $?
0
$ mkdir mylink || echo failed
mkdir: cannot create directory `mylink': File exists
failed
$ mkdir mylink; echo $?
mkdir: cannot create directory `mylink': File exists
1
$ ls -ld my*
drwx-- 2 psz amstaff 4096 Oct 14 18:46 mydir
lrwxrwxrwx 1 psz amstaff5 Oct 14 18:46 mylink -> mydir
$ 

showing that "mkdir -p" does not fail (but plain mkdir does).

> On the practicality for Debian systems though this is mitigated by the
> Kernel hardenings which are enabled by default:
> 
> fs.protected_hardlinks=1
> fs.protected_symlink=1
> 
> which will prevent that the target of the symlink in /tmp will be
> changed on the chown call.

Another missing test (besides: who is changing anything?):

# grep . /proc/sys/fs/prot*
/proc/sys/fs/protected_hardlinks:1
/proc/sys/fs/protected_symlinks:1
# cd ~psz
# ls -ld my*
drwx-- 2 psz amstaff 4096 Oct 14 18:46 mydir
lrwxrwxrwx 1 psz amstaff5 Oct 14 18:46 mylink -> mydir
# chown mike mylink
# ls -ld my*
drwx-- 2 mike amstaff 4096 Oct 14 18:46 mydir
lrwxrwxrwx 1 psz  amstaff5 Oct 14 18:46 mylink -> mydir
# 

> So while I think it should be fixed, this would not warrant a DSA,
> since mitigated by default in Debian.

No mitigation: fix and DSA, please!

---

What response time should I have expected of team@security? You had
close to a whole day... compared to that, Markus replied within the
hour to the Debian bug. (But he did not yet reply to my next, private
bug/message... seems public messaging works best!)

Cheers, Paul

Paul Szabo   p...@maths.usyd.edu.au   http://www.maths.usyd.edu.au/u/psz/
School of Mathematics and Statistics   University of SydneyAustralia

Bug#806000: brickos: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Petter Reinholdtsen]

Control: tags -1 + patch

I had a look, and while I do not quite understand the build system and why it
fail to create the directory it need to install, I applied this patch and got
the 'dpkg-buildpackage -A' build working:

diff -ur brickos-0.9.0.dfsg/debian/rules brickos-0.9.0.dfsg-pere/debian/rules
--- brickos-0.9.0.dfsg/debian/rules 2015-02-14 18:21:17.0 +
+++ brickos-0.9.0.dfsg-pere/debian/rules2016-10-14 07:43:21.284198193 
+
@@ -33,6 +33,7 @@
 
 override_dh_auto_install:
#  Install the package into debian/brickos.
+   mkdir -p $(CURDIR)/debian/brickos/usr/bin
$(MAKE) install docs-install inst_prefix=/usr 
prefix=$(CURDIR)/debian/brickos/usr 
mandir=$(CURDIR)/debian/brickos/usr/share/man
#  remove docs we shouldn't install
rm -f 
$(CURDIR)/debian/brickos/usr/share/doc/brickos/html/INSTALL-cygwin*
-- 
Happy hacking
Petter Reinholdtsen

Processed: Re: brickos: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #806000 [src:brickos] brickos: FTBFS when built with dpkg-buildpackage -A 
(No such file or directory)
Added tag(s) patch.

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

Bug#840689: libterm-readline-gnu-perl: FTBFS on 64-bit big endian architectures

[Salvatore Bonaccorso]

Control: tags -1 + confirmed

Hi,

On Thu, Oct 13, 2016 at 11:03:15PM +0200, Emilio Pozuelo Monfort wrote:
> Package: libterm-readline-gnu-perl
> Version: 1.34-1
> Severity: serious
> 
> Hi,
> 
> On a rebuild against libreadline7, your package failed to build on
> big-endian, 64-bit architectures:
> 
> # 2.4 History Variables
> ok 86 - history_inhibit_expansion_function
> ok 87
> ok 88
> ok
> Use of uninitialized value in string eq at t/readline.t line 119.
> Use of uninitialized value in string eq at t/readline.t line 119.
> 
> #   Failed test 'readline_state'
> #   at t/readline.t line 152.
> 
> Full logs at:
> 
> https://buildd.debian.org/status/package.php?p=libterm-readline-gnu-perl

Side-remark: It looks it only started failing on the last rebuild
round, up to 1.34-1+b1 all builds were fine.

Regards,
Salvatore

Processed: Re: Bug#840689: libterm-readline-gnu-perl: FTBFS on 64-bit big endian architectures

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #840689 [libterm-readline-gnu-perl] libterm-readline-gnu-perl: FTBFS on 
64-bit big endian architectures
Added tag(s) confirmed.

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

Processed: Re: [Debian-med-packaging] Bug#834856: python-pysam fails to build on mips64el arch.: failed test

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #834856 [python-pysam] python-pysam fails to build on mips64el arch.: 
failed test
Severity set to 'serious' from 'important'

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

Bug#840685: tomcat8: DSA-3670 incomplete

[Salvatore Bonaccorso]

Hi Paul, hi Markus,

On Fri, Oct 14, 2016 at 08:42:11AM +1100, paul.sz...@sydney.edu.au wrote:
> Dear Markus,
>
> >> [ I contacted t...@security.debian.org about this, but no response ... ]
> > ... Please send them to the security team
> > first and not to a public mailing list.
>
> I did. They did not reply within what seemed a reasonable timeframe.

To be fair one could say, the initial mail was on 'Thu Oct 13 01:38:41
UTC 2016' and the bugreport on 'Thu Oct 13 20:22:50 UTC 2016'. But
thanks for reporting (appreciated!) and it's maybe anyway better to
have it tracked in the BTS in this case:

> >> Recently DSA-3670 was released, and /etc/init.d/tomcat8 modified so...
> > No, we did not modify this part in /etc/init.d/tomcat8. ...
>
> Whoops, sorry, you are right. Now checking, I do not see how I got
> confused. This is a separate, maybe new issue.

Yes, I think, that should be considered a different issue. Please not
that in your attack vector, though if the attacher created a symlink
between the rm and the mkdir then mkdir will still fail with -p on a
symlink.  (Or do I miss something?). So the attacker would need to do
it two-staged, first a directory, which will pass the mkdir -p
successfully, then replace the directory with a symlink which will be
followed.

On the practicality for Debian systems though this is mitigated by the
Kernel hardenings which are enabled by default:

fs.protected_hardlinks=1
fs.protected_symlink=1

which will prevent that the target of the symlink in /tmp will be
changed on the chown call.

So while I think it should be fixed, this would not warrant a DSA,
since mitigated by default in Debian.

Regards,
Salvatore

Bug#840575: [buildd-tools-devel] Bug#840575: sbuild bpo: uses non-available option gnupg --pinentry-mode

[Daniel Kahn Gillmor]

On Fri 2016-10-14 01:36:56 -0400, Johannes Schauer wrote:
>  - it is a feature of sbuild since version 0.67.0 (I corrected the wiki page
>accordingly) to *not* require signing of the internal dummy repository (and
>thus you don't need to run sbuild-update --keygen anymore) and that

awesome, thanks for this improvement (and thanks for all your work on
sbuild)!

Regards,

--dkg

Bug#840097: sysprof ppc binaries removed

[Andreas Henriksson]

Control: severity -1 important

Hello!

The old powerpc binaries has now been removed from unstable.
Porter assistance with identifying if this is a real issue or
a testcase problem would be welcome.

Regards,
Andreas Henriksson

Processed: sysprof ppc binaries removed

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #840097 [sysprof] sysprof: FTBFS on powerpc: 
ERROR:test-capture.c:68:test_reader_basic: assertion failed: (map != NULL)
Severity set to 'important' from 'serious'

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