Bug#866701: src:zope.security: FTBFS once python3.6 is added to supported python3 versions

[Scott Kitterman]

Package: src:zope.security
Version: 4.0.3-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

There are a stack of test failures now.  Here is an example:


==
ERROR: test___delattr___w_checker_unauthorized 
(zope.security.tests.test_proxy.ProxyCTests)
--
Traceback (most recent call last):
  File "/<>/src/zope/security/tests/test_proxy.py", line 136, in 
test___delattr___w_checker_unauthorized
proxy = self._makeOne(target, checker)
  File "/<>/src/zope/security/tests/test_proxy.py", line 51, in 
_makeOne
return self._getTargetClass()(object, checker)
  File "/<>/src/zope/security/tests/test_proxy.py", line 1340, in 
_getTargetClass
from zope.security.proxy import _Proxy
ImportError: cannot import name '_Proxy'

They are all different tests failing on the same ImportError.  Details in the
build log [1].

Scott K

[1] 
https://buildd.debian.org/status/fetch.php?pkg=zope.security=s390x=4.0.3-2%2Bb2=1498885023=0

Bug#866688: seems just misalignment of version with php-horde-core

[Ivan Sergio Borgonovo]

DB problem seems to be solved after upgrade to

Package: php-horde-core
Version: 2.29.1+debian0-1

but now I'm experiencing other problems with activesync[1]

It could be a good idea to improve dependencies.

I'll wait till all horde packages get updated.

Sorry for the noise.

[1]
Error: Class 'Horde_ActiveSync_Log_Factory' not found in 
/usr/share/php/Horde/Core/Factory/ActiveSyncServer.php:36


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

Processed: affects 866354

[Debian Bug Tracking System]

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

> affects 866354 qpid-proton
Bug #866354 [libstdc++6] armel: symbol _ZTINSt13__future_base12_Result_baseE, 
version GLIBCXX_3.4.15 not defined in file libstdc++.so.6
Bug #866576 [libstdc++6] doxygen: relocation error in libLLVM-3.9.so.1 on armel
Added indication that 866354 affects qpid-proton
Added indication that 866576 affects qpid-proton
> thanks
Stopping processing here.

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

Bug#866354: Also affects qpid-proton

[Scott Kitterman]

>From the most recent armel build log [1]:

/usr/bin/doxygen: relocation error: /usr/lib/arm-linux-
gnueabi/libLLVM-3.9.so.1: symbol _ZTINSt13__future_base12_Result_baseE, 
version GLIBCXX_3.4.15 not defined in file libstdc++.so.6 with link time 
reference
proton-c/docs/api/CMakeFiles/docs-c.dir/build.make:60: recipe for target 
'proton-c/docs/api/CMakeFiles/docs-c' failed

FYI, affects the current python3 transition.

Scott K

[1] 
https://buildd.debian.org/status/fetch.php?pkg=qpid-proton=armel=0.14.0-5%2Bb1=1498878726=0

Processed: Re: Bug#865526: PETSc has strict dependency on MPI version

[Debian Bug Tracking System]

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

> reopen 865526
Bug #865526 {Done: Gianfranco Costamagna } 
[libpetsc3.7.5-dev] libpetsc3.7.5-dev: uninstallable on current sid
Bug reopened
Ignoring request to alter fixed versions of bug #865526 to the same values 
previously set
> retitle 865526 PETSc has strict dependency on MPI version
Bug #865526 [libpetsc3.7.5-dev] libpetsc3.7.5-dev: uninstallable on current sid
Changed Bug title to 'PETSc has strict dependency on MPI version' from 
'libpetsc3.7.5-dev: uninstallable on current sid'.
> severity 865526 normal
Bug #865526 [libpetsc3.7.5-dev] PETSc has strict dependency on MPI version
Severity set to 'normal' from 'grave'
> forwarded 865526 
> https://bitbucket.org/petsc/petsc/commits/ca70f86ee9db8e69523e0e69f12289c6cab9b4cb?at=jed/mpi-semver
Bug #865526 [libpetsc3.7.5-dev] PETSc has strict dependency on MPI version
Set Bug forwarded-to-address to 
'https://bitbucket.org/petsc/petsc/commits/ca70f86ee9db8e69523e0e69f12289c6cab9b4cb?at=jed/mpi-semver'.
> thanks
Stopping processing here.

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

Bug#866695: src:xapian-bindings: FTBFS when rebuilt with python3.6 due to test failures

[Scott Kitterman]

On Saturday, July 01, 2017 03:51:01 AM Olly Betts wrote:
> Control: tags -1 + fixed-upstream pending
> 
> On Fri, Jun 30, 2017 at 10:38:12PM -0400, Scott Kitterman wrote:
> > -> 917'Query(0 * VALUE_RANGE 7 A5 B8)')
> 
> This is unrelated to the Python version change - it's actually due to
> xapian-core 1.4.4 optimising away the redundant "scale weight by 0" as the
> query objects are constructed (it is redundant as VALUE_RANGE always returns
> weight 0).
> 
> It's fixed in upstream xapian-bindings 1.4.4 which is already on my todo
> list to upload.  I'll bump it up so this gets resolved sooner.

OK.  Thanks for the quick response.

Scott K

Bug#864316: marked as done (libapache2-mod-perl: FTBFS in jessie due to apache2 changes)

[Debian Bug Tracking System]

Your message dated Sat, 01 Jul 2017 03:32:39 +
with message-id 
and subject line Bug#864316: fixed in libapache2-mod-perl2 
2.0.9~1624218-2+deb8u2
has caused the Debian Bug report #864316,
regarding libapache2-mod-perl: FTBFS in jessie due to apache2 changes
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.)


-- 
864316: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864316
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libapache2-mod-perl2
Version: 2.0.9~1624218-2+deb8u1
Severity: serious

As per

 
http://perl.debian.net/rebuild-logs/jessie/libapache2-mod-perl2_2.0.9~1624218-2+deb8u1/libapache2-mod-perl2_2.0.9~1624218-2+deb8u1_amd64-2017-06-05T19:42:17Z.build

this package currently fails to build in jessie.

  Test Summary Report
  ---
  t/apache/read.t   (Wstat: 0 Tests: 1 Failed: 1)
Failed test:  1
  t/filter/in_bbs_inject_header.t   (Wstat: 512 Tests: 0 Failed: 0)
Non-zero exit status: 2
Parse errors: Bad plan.  You planned 36 tests but ran 0.
 
This is very similar to #849082 and was most probably caused by 

 apache2 (2.4.10-10+deb8u8) jessie-security; urgency=medium
 .
   * CVE-2016-8743: Enforce more HTTP conformance for request lines and
 request headers, to prevent response splitting and cache pollution
 by malicious clients or downstream proxies.
 If this causes problems with non-conforming clients, some checks can
 be relaxed by adding the new directive 'HttpProtocolOptions unsafe'
 to the configuration.
 Differently than the upstream 2.4.25 release which will also be in the
 Debian 9 (stretch) release, this update for Debian 8 (jessie) accepts
 underscores in host and domain names even while 'HttpProtocolOptions
 strict' is in effect.
 More information is available at
 http://httpd.apache.org/docs/2.4/mod/core.html#httpprotocoloptions

so 370_http_syntax.patch and 380_inject_header_line_terminators.patch
from stretch/sid should help (untested).
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: libapache2-mod-perl2
Source-Version: 2.0.9~1624218-2+deb8u2

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

Debian distribution maintenance software
pp.
Niko Tyni  (supplier of updated libapache2-mod-perl2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 14 Jun 2017 14:39:56 +0300
Source: libapache2-mod-perl2
Binary: libapache2-mod-perl2 libapache2-mod-perl2-dev libapache2-mod-perl2-doc
Architecture: all source
Version: 2.0.9~1624218-2+deb8u2
Distribution: jessie
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Niko Tyni 
Closes: 864316
Description: 
 libapache2-mod-perl2-dev - Integration of perl with the Apache2 web server - 
development fil
 libapache2-mod-perl2-doc - Integration of perl with the Apache2 web server - 
documentation
 libapache2-mod-perl2 - Integration of perl with the Apache2 web server
Changes:
 libapache2-mod-perl2 (2.0.9~1624218-2+deb8u2) jessie; urgency=medium
 .
   * Patch the test suite for apache2_2.4.10-10+deb8u8 compatibility.
 (Closes: #864316)
Checksums-Sha1: 
 3c0d4d0864c0292f8fb173d9d80302181a8a2d8b 2731 
libapache2-mod-perl2_2.0.9~1624218-2+deb8u2.dsc
 37d5c11a9d69aa624b64f326eee6035047c9a708 28664 
libapache2-mod-perl2_2.0.9~1624218-2+deb8u2.debian.tar.xz
 18b04c2ebafaef666cea49c5f13ecfa7cd63817b 7910 
libapache2-mod-perl2_2.0.9~1624218-2+deb8u2_source.buildinfo
 09f932e19a45baaabfc5c95d36c9293ac4aa8e34 85188 
libapache2-mod-perl2-dev_2.0.9~1624218-2+deb8u2_all.deb
 3683d2e6b8868d1ad1192588f4d630b5829abca3 1305804 
libapache2-mod-perl2-doc_2.0.9~1624218-2+deb8u2_all.deb
Checksums-Sha256: 
 e14365e1bf67cacf25926870492e6c9e27fc416f1e1acf2c29c6ec4e3de57d68 2731 
libapache2-mod-perl2_2.0.9~1624218-2+deb8u2.dsc
 9ad6c56fa8937a2e8e49c48b02b72375e404dadfe47b54c0680492ec1fdcb4e2 28664 

Bug#834153: marked as done (gitolite3 should depend on openssh-client)

[Debian Bug Tracking System]

Your message dated Sat, 01 Jul 2017 03:32:38 +
with message-id 
and subject line Bug#834153: fixed in gitolite3 3.6.1-2+deb8u2
has caused the Debian Bug report #834153,
regarding gitolite3 should depend on openssh-client
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.)


-- 
834153: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834153
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitolite3
Version: 3.6.1-2+deb8u1
Severity: serious

Hi,

`gitolite setup` calls `ssh-keygen -l -f ` to check that is was
passed a valid OpenSSH pubkey.  When this binary is not present,
`gitolite setup` fails (claiming the pubkey is not valid).


As such, it seems that gitolite3 should depend on openssh-client (or some
appropriate | alternative).

Alternatively, gitolite could be patched to only perform the check if
ssh-keygen is available.


Best,

  Keller Fuchs


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

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

Versions of packages gitolite3 depends on:
ii  adduser  3.113+nmu3
ii  debconf [debconf-2.0]1.5.56
ii  git [git-core]   1:2.1.4-2.1+deb8u2
ii  openssh-server [ssh-server]  1:6.7p1-5+deb8u3
ii  perl 5.20.2-3+deb8u6

gitolite3 recommends no packages.

Versions of packages gitolite3 suggests:
pn  git-daemon-run  
pn  gitweb  
--- End Message ---
--- Begin Message ---
Source: gitolite3
Source-Version: 3.6.1-2+deb8u2

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

Debian distribution maintenance software
pp.
David Bremner  (supplier of updated gitolite3 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, 30 Jun 2017 09:56:05 -0300
Source: gitolite3
Binary: gitolite3
Architecture: source all
Version: 3.6.1-2+deb8u2
Distribution: jessie
Urgency: medium
Maintainer: David Bremner 
Changed-By: David Bremner 
Description:
 gitolite3  - SSH-based gatekeeper for git repositories (version 3)
Closes: 834153
Changes:
 gitolite3 (3.6.1-2+deb8u2) jessie; urgency=medium
 .
   * Bug fix: "gitolite3 should depend on openssh-client", thanks to Keller
 Fuchs (Closes: #834153).
Checksums-Sha1:
 71faf428f0e956c35487744a34afa08dcbaa768b 1717 gitolite3_3.6.1-2+deb8u2.dsc
 b18a83e9d2527a56df378cf65ad9bf93f6d2ddb2 18635 gitolite3_3.6.1-2+deb8u2.diff.gz
 9e647013b4bdeb5169e9afb2497e0628a5e9af20 102980 
gitolite3_3.6.1-2+deb8u2_all.deb
Checksums-Sha256:
 5b2e03284148faf455f36df5ffe26d3d5c9c985a7b65961b9400df5d3c4e5fc1 1717 
gitolite3_3.6.1-2+deb8u2.dsc
 ad69214848fb423ec535dec43557b5dc3ce7795f31801a073b4464c3789f0969 18635 
gitolite3_3.6.1-2+deb8u2.diff.gz
 cb8ff7808ec4b193bfcc4794bdd4529cdc68fccdaa1bd2b01ed7737849a6dd44 102980 
gitolite3_3.6.1-2+deb8u2_all.deb
Files:
 446c64b240a07dbbea74819a400d5e61 1717 vcs optional gitolite3_3.6.1-2+deb8u2.dsc
 528bb1e2bcc6100418eb1e6f5e5bcd0b 18635 vcs optional 
gitolite3_3.6.1-2+deb8u2.diff.gz
 c7920adcc02c90ebff898f73fa35f942 102980 vcs optional 
gitolite3_3.6.1-2+deb8u2_all.deb

-BEGIN PGP SIGNATURE-

iQGzBAEBCAAdFiEE3VS2dnyDRXKVCQCp8gKXHaSnniwFAllWTOoACgkQ8gKXHaSn
niwJEgv/fH0g62DV5kdCWvDnzS1ZX65ecUrlbnJjzKwGzSKSmm8CRG3tuDEbjTlZ
o8i7/VVXOS8pL62qGcPkXFx3xguLk1ty2y0A4vPg2Zn8ZR8zfz3DpFS5xKugPwC1
9id2UJjKpvTU1tojIWxSSnNsO5buEDPVBncbLwiFpZLbzsRdze61XJHwKlIOWKsK
s5PendG2M0lvRgb1UDox9bCOXBIOwBsgmCreCP73MME7W21f2ELzebYahgHWZvK3
6AbkY0ldWqr9PfXbgtpaIaPoh1ZpUUqZWSH+aW6rOHATCyX1htPvqM9NF8jarUuK
XD9tmmPSBAY6q/8KCjlEdc+OasipFhzUURspqMK1L4Wzb+FyhrIKpUG1PWQhJDXq
zxUtTZGfJ3VPem8Jr7tMXbBda3nEXlyhtRkPUx562sXegS50hlNpssljIT5wwhDP
rJdapmi0ouypP5kNCLzbb/pwKDrInbcro5wclNtKf48s0rdjmZYGcYIbjcAplu0j
RIw2VxzV
=GwPn
-END PGP 

Bug#865526: PETSc has strict dependency on MPI version

[Drew Parsons]

reopen 865526
retitle 865526 PETSc has strict dependency on MPI version
severity 865526 normal
forwarded 865526 
https://bitbucket.org/petsc/petsc/commits/ca70f86ee9db8e69523e0e69f12289c6cab9b4cb?at=jed/mpi-semver
thanks

Reopening to help track upstream handling of PETSc's MPI dependency
logic.

Until that's fixed, we need to lodge a binNMU for PETSc every time
openmpi (or mpich on m68k, sh4) is updated to a new upstream version.

Drew

Bug#865526: libpetsc3.7.5-dev: uninstallable on current sid

[Drew Parsons]

On Fri, 30 Jun 2017 05:56:30 +0300 Adrian Bunk  wrote:
> 
> This is a release critical bug that should stay open until it is
fixed 
> in sid.


nmu has been filed in #866582 which will fix the bug in this instance.

The strict dependency of PETSc on the MPI version (that requires the
rebuild) is a bit of a nuisance.  It appears in
/usr/lib/petsc/include/petscsys.h.  In 3.7.6 they have a strict
equality on the OMPI version dependency.  I've contacted them about it
and they've made a patch to relax it to a minor version dependency
rather than a release (patch) version dependency, which
should help us.

That patch is held at
https://bitbucket.org/petsc/petsc/commits/ca70f86ee9db8e69523e0e69f1228
9c6cab9b4cb?at=jed/mpi-semver
but looks like it hasn't been merged to upstream master yet.  

We should talk to upstream about it again.

Drew

Processed: Re: Bug#866695: src:xapian-bindings: FTBFS when rebuilt with python3.6 due to test failures

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + fixed-upstream pending
Bug #866695 [src:xapian-bindings] src:xapian-bindings: FTBFS when rebuilt with 
python3.6 due to test failures
Added tag(s) fixed-upstream and pending.

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

Bug#866520: marked as done (python3-pcp: Incorrect substitution variable causes missing depends)

[Debian Bug Tracking System]

Your message dated Sat, 01 Jul 2017 03:05:16 +
with message-id 
and subject line Bug#866520: fixed in pcp 3.12.0
has caused the Debian Bug report #866520,
regarding python3-pcp: Incorrect substitution variable causes missing depends
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.)


-- 
866520: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866520
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pcp
Version: 3.11.10
Severity: serious
Tags: patch
Justification: Policy 3.5

There is a separate depends variable for python3, python3:Depends.  Using the
wrong one for python3-pcp is causing the python3 interpreter related depends
to be missing.  Please see the attached patch.  It also removes a few obsolete
items.  The variable python3:Provides has never existed and python:Provides is
not to be used any longer.

Please see the attached patch.  Since the package is otherwise RC buggy and I
don't have time to attend to the other RC bug, I don't intend to NMU (despite
using that format for debian/changelog).

Scott K
diff -Nru pcp-3.11.10/debian/changelog pcp-3.11.10+nmu1/debian/changelog
--- pcp-3.11.10/debian/changelog	2017-05-17 01:45:38.0 -0400
+++ pcp-3.11.10+nmu1/debian/changelog	2017-06-29 14:41:31.0 -0400
@@ -1,3 +1,10 @@
+pcp (3.11.10+nmu1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix subsitution variable in python3-pcp so correct depends are generated
+
+ -- Scott Kitterman   Thu, 29 Jun 2017 14:40:37 -0400
+
 pcp (3.11.10) unstable; urgency=low
 
   * New release (full details in CHANGELOG).
diff -Nru pcp-3.11.10/debian/control pcp-3.11.10+nmu1/debian/control
--- pcp-3.11.10/debian/control	2017-05-17 01:45:38.0 -0400
+++ pcp-3.11.10+nmu1/debian/control	2017-06-29 14:40:31.0 -0400
@@ -246,7 +246,6 @@
 Section: python
 Architecture: any
 Depends: ${python:Depends}, ${misc:Depends}, ${shlibs:Depends}, libpcp3 (= ${binary:Version}), libpcp-pmda3 (= ${binary:Version}), libpcp-mmv1 (= ${binary:Version}), libpcp-gui2 (= ${binary:Version}), libpcp-import1 (= ${binary:Version})
-Provides: ${python:Provides} 
 Description: Performance Co-Pilot Python PMAPI module
  The PCP Python module contains the language bindings for
  building Performance Metric API client tools using Python.
@@ -259,8 +258,7 @@
 Package: python3-pcp
 Section: python
 Architecture: any
-Depends: ${python:Depends}, ${misc:Depends}, ${shlibs:Depends}, libpcp3 (= ${binary:Version}), libpcp-pmda3 (= ${binary:Version}), libpcp-mmv1 (= ${binary:Version}), libpcp-gui2 (= ${binary:Version}), libpcp-import1 (= ${binary:Version})
-Provides: ${python:Provides} 
+Depends: ${python3:Depends}, ${misc:Depends}, ${shlibs:Depends}, libpcp3 (= ${binary:Version}), libpcp-pmda3 (= ${binary:Version}), libpcp-mmv1 (= ${binary:Version}), libpcp-gui2 (= ${binary:Version}), libpcp-import1 (= ${binary:Version})
 Description: Performance Co-Pilot Python3 PMAPI module
  The PCP Python3 module contains the language bindings for
  building Performance Metric API client tools using Python3.
--- End Message ---
--- Begin Message ---
Source: pcp
Source-Version: 3.12.0

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

Debian distribution maintenance software
pp.
Nathan Scott  (supplier of updated pcp 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, 30 Jun 2017 10:30:27 +1000
Source: pcp
Binary: pcp pcp-conf libpcp3-dev libpcp3 libpcp-gui2-dev libpcp-gui2 
libpcp-mmv1-dev libpcp-mmv1 libpcp-pmda3-dev libpcp-pmda3 libpcp-trace2-dev 
libpcp-trace2 libpcp-import1-dev libpcp-import1 libpcp-web1-dev libpcp-web1 
python-pcp python3-pcp libpcp-pmda-perl libpcp-import-perl 
libpcp-logsummary-perl libpcp-mmv-perl pcp-import-sar2pcp 
pcp-import-ganglia2pcp pcp-import-mrtg2pcp pcp-import-sheet2pcp 
pcp-import-iostat2pcp pcp-import-collectl2pcp pcp-export-pcp2graphite 
pcp-export-pcp2influxdb pcp-export-zabbix-agent pcp-doc pcp-testsuite 

Bug#866695: src:xapian-bindings: FTBFS when rebuilt with python3.6 due to test failures

[Olly Betts]

Control: tags -1 + fixed-upstream pending

On Fri, Jun 30, 2017 at 10:38:12PM -0400, Scott Kitterman wrote:
> -> 917'Query(0 * VALUE_RANGE 7 A5 B8)')

This is unrelated to the Python version change - it's actually due to
xapian-core 1.4.4 optimising away the redundant "scale weight by 0" as the
query objects are constructed (it is redundant as VALUE_RANGE always returns
weight 0).

It's fixed in upstream xapian-bindings 1.4.4 which is already on my todo
list to upload.  I'll bump it up so this gets resolved sooner.

Cheers,
Olly

Bug#866696: src:python-pyeclib: FTBFS on mips64el due to test failures after rebuild with python3.6

[Scott Kitterman]

Package: src:python-pyeclib
Version: 1.4.0-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

See the build log [1].

error: Test failed: 
debian/rules:28: recipe for target 'override_dh_auto_test' failed

Scott K

[1] 
https://buildd.debian.org/status/fetch.php?pkg=python-pyeclib=mips64el=1.4.0-2%2Bb1=1498868288=0

Bug#866695: src:xapian-bindings: FTBFS when rebuilt with python3.6 due to test failures

[Scott Kitterman]

Package: src:xapian-bindings
Version: 1.4.3-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Running test: queryparser_custom_rp... FAILED

pythontest.py:917:Expected equality: got 'Query(VALUE_RANGE 7 A5 B8)', expected 
'Query(0 * VALUE_RANGE 7 A5 B8)'
   915 
   916 expect(str(query),
-> 917'Query(0 * VALUE_RANGE 7 A5 B8)')
   918 
   919 def test_queryparser_custom_rp_deallocation():
Xapian version: 1.4.4
Platform: Linux 4.9.0-3-amd64 (#1 SMP Debian 4.9.30-2+deb9u2 (2017-06-26))

When reporting this problem, please quote all the preceding lines from
"pythontest.py:917" onwards.

Running test: queryparser_custom_rp_deallocation... FAILED

pythontest.py:942:Expected equality: got 'Query(VALUE_RANGE 7 A5 B8)', expected 
'Query(0 * VALUE_RANGE 7 A5 B8)'
   940 
   941 expect(str(query),
-> 942'Query(0 * VALUE_RANGE 7 A5 B8)')
   943 
   944 def test_scale_weight():
Xapian version: 1.4.4
Platform: Linux 4.9.0-3-amd64 (#1 SMP Debian 4.9.30-2+deb9u2 (2017-06-26))

When reporting this problem, please quote all the preceding lines from
"pythontest.py:942" onwards.

Running test: queryparser_custom_vrp... FAILED

pythontest.py:872:Expected equality: got 'Query(VALUE_RANGE 7 A5 B8)', expected 
'Query(0 * VALUE_RANGE 7 A5 B8)'
   870 
   871 expect(str(query),
-> 872'Query(0 * VALUE_RANGE 7 A5 B8)')
   873 
   874 def test_queryparser_custom_vrp_deallocation():
Xapian version: 1.4.4
Platform: Linux 4.9.0-3-amd64 (#1 SMP Debian 4.9.30-2+deb9u2 (2017-06-26))

When reporting this problem, please quote all the preceding lines from
"pythontest.py:872" onwards.

Running test: queryparser_custom_vrp_deallocation... FAILED

pythontest.py:895:Expected equality: got 'Query(VALUE_RANGE 7 A5 B8)', expected 
'Query(0 * VALUE_RANGE 7 A5 B8)'
   893 
   894 expect(str(query),
-> 895'Query(0 * VALUE_RANGE 7 A5 B8)')
   896 
   897 def test_queryparser_custom_rp():
Xapian version: 1.4.4
Platform: Linux 4.9.0-3-amd64 (#1 SMP Debian 4.9.30-2+deb9u2 (2017-06-26))

When reporting this problem, please quote all the preceding lines from
"pythontest.py:895" onwards.

See [1].

Scott K

[1] 
https://buildd.debian.org/status/fetch.php?pkg=xapian-bindings=amd64=1.4.3-1%2Bb1=1498870905=0

Bug#866694: src:pythonmagick: FTBFS with python3.6 as a supported python3

[Scott Kitterman]

Package: src:pythonmagick
Version: 0.9.14-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)

With python3.6 as a supported python3 version, this package FTBFS:

checking for python with minimal version... 3.6
checking for a Python interpreter with version >= 3.6... none
configure: error: no suitable Python interpreter found

See [1].

Scott K

[1] 
https://buildd.debian.org/status/fetch.php?pkg=pythonmagick=amd64=0.9.14-3%2Bb2=1498871134=0

Processed: retitle 866691 to linux-image-*-dbg meta-packages are uninstallable

[Debian Bug Tracking System]

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

> retitle 866691 linux-image-*-dbg meta-packages are uninstallable
Bug #866691 [src:linux-latest] linux-image-*-dbg metapackages are installable
Changed Bug title to 'linux-image-*-dbg meta-packages are uninstallable' from 
'linux-image-*-dbg metapackages are installable'.
> thanks
Stopping processing here.

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

Bug#866691: linux-image-*-dbg metapackages are installable

[Ben Hutchings]

Package: src:linux-latest
Version: 80
Severity: serious

src:linux version 4.9.25-1 moved the debug info packages back to the
main archive and changed their name suffix from -dbgsym back to -dbg.
src:linux-latest needs to be changed accordingly.

Ben.

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

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

Bug#865789: marked as done (git FTBFS on armhf/ppc64el: not ok 3 - git svn branch tests)

[Debian Bug Tracking System]

Your message dated Fri, 30 Jun 2017 23:34:40 +
with message-id 
and subject line Bug#865789: fixed in git 1:2.13.2-3
has caused the Debian Bug report #865789,
regarding git FTBFS on armhf/ppc64el: not ok 3 - git svn branch tests
to be marked as done.

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

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


-- 
865789: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865789
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: git
Version: 1:2.13.1-1
Severity: serious

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

...
expecting success: 
git svn branch a &&
base=$(git rev-parse HEAD:) &&
test $base = $(git rev-parse remotes/origin/a:) &&
git svn branch -m "created branch b blah" b &&
test $base = $(git rev-parse remotes/origin/b:) &&
test_must_fail git branch -m "no branchname" &&
git svn branch -n c &&
test_must_fail git rev-parse remotes/origin/c &&
test_must_fail git svn branch a &&
git svn branch -t tag1 &&
test $base = $(git rev-parse remotes/origin/tags/tag1:) &&
git svn branch --tag tag2 &&
test $base = $(git rev-parse remotes/origin/tags/tag2:) &&
git svn tag tag3 &&
test $base = $(git rev-parse remotes/origin/tags/tag3:) &&
git svn tag -m "created tag4 foo" tag4 &&
test $base = $(git rev-parse remotes/origin/tags/tag4:) &&
test_must_fail git svn tag -m "no tagname" &&
git svn tag -n tag5 &&
test_must_fail git rev-parse remotes/origin/tags/tag5 &&
test_must_fail git svn tag tag1

Copying 
file:///«PKGBUILDDIR»/t/trash%20directory.t9128-git-svn-cmd-branch/svnrepo/trunk
 at r2 to 
file:///«PKGBUILDDIR»/t/trash%20directory.t9128-git-svn-cmd-branch/svnrepo/branches/a...
Found possible branch point: 
file:///«PKGBUILDDIR»/t/trash%20directory.t9128-git-svn-cmd-branch/svnrepo/trunk
 => 
file:///«PKGBUILDDIR»/t/trash%20directory.t9128-git-svn-cmd-branch/svnrepo/branches/a,
 2
Found branch parent: (refs/remotes/origin/a) 
eed7341cd656e2fdb2fb9b36fbe4b039ba13e348
Following parent with do_switch
Successfully followed parent
r3 = 66a689f823e1002a376e324cce35d8c131f72bdc (refs/remotes/origin/a)
Copying 
file:///«PKGBUILDDIR»/t/trash%20directory.t9128-git-svn-cmd-branch/svnrepo/trunk
 at r2 to 
file:///«PKGBUILDDIR»/t/trash%20directory.t9128-git-svn-cmd-branch/svnrepo/branches/b...
Found possible branch point: 
file:///«PKGBUILDDIR»/t/trash%20directory.t9128-git-svn-cmd-branch/svnrepo/trunk
 => 
file:///«PKGBUILDDIR»/t/trash%20directory.t9128-git-svn-cmd-branch/svnrepo/branches/b,
 2
Found branch parent: (refs/remotes/origin/b) 
eed7341cd656e2fdb2fb9b36fbe4b039ba13e348
Following parent with do_switch
Successfully followed parent
r4 = 3f86a479bd31164c206172f5ef7b1fcb7d43e4e1 (refs/remotes/origin/b)
error: git-svn died of signal 11
not ok 3 - git svn branch tests
#   
#   git svn branch a &&
#   base=$(git rev-parse HEAD:) &&
#   test $base = $(git rev-parse remotes/origin/a:) &&
#   git svn branch -m "created branch b blah" b &&
#   test $base = $(git rev-parse remotes/origin/b:) &&
#   test_must_fail git branch -m "no branchname" &&
#   git svn branch -n c &&
#   test_must_fail git rev-parse remotes/origin/c &&
#   test_must_fail git svn branch a &&
#   git svn branch -t tag1 &&
#   test $base = $(git rev-parse remotes/origin/tags/tag1:) &&
#   git svn branch --tag tag2 &&
#   test $base = $(git rev-parse remotes/origin/tags/tag2:) &&
#   git svn tag tag3 &&
#   test $base = $(git rev-parse remotes/origin/tags/tag3:) &&
#   git svn tag -m "created tag4 foo" tag4 &&
#   test $base = $(git rev-parse remotes/origin/tags/tag4:) &&
#   test_must_fail git svn tag -m "no tagname" &&
#   git svn tag -n tag5 &&
#   test_must_fail git rev-parse remotes/origin/tags/tag5 &&
#   test_must_fail git svn tag tag1
#   
...
--- End Message ---
--- Begin Message ---
Source: git
Source-Version: 1:2.13.2-3

We believe that the bug you reported is fixed in the latest version of
git, 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 865...@bugs.debian.org,
and the maintainer will 

Bug#866056: marked as done (syslog-ng FTBFS: FAIL: modules/cryptofuncs/tests/test_cryptofuncs)

[Debian Bug Tracking System]

Your message dated Fri, 30 Jun 2017 22:51:44 +
with message-id 
and subject line Bug#866056: fixed in syslog-ng 3.10.1-1
has caused the Debian Bug report #866056,
regarding syslog-ng FTBFS: FAIL: modules/cryptofuncs/tests/test_cryptofuncs
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.)


-- 
866056: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866056
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: syslog-ng
Version: 3.8.1-10
Severity: serious
Tags: buster sid

Some recent change in unstable makes syslog-ng FTBFS:

https://tests.reproducible-builds.org/debian/history/syslog-ng.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/syslog-ng.html

...
FAIL: modules/cryptofuncs/tests/test_cryptofuncs


[2019-09-01T00:42:25.621155] Plugin module not found in 'module-path';

  ###
  #
  # FAIL: ASSERTION FAILED: FAIL: compilation error doesn't match, error=Cannot 
parse integer value “invalid_length_specification” for --length, 
expected_error=Cannot parse integer value 'invalid_length_specification' for 
--length
; actual=FALSE, expected=TRUE
  #
  ###

FAIL modules/cryptofuncs/tests/test_cryptofuncs (exit status: 1)


Testsuite summary for syslog-ng 3.8.1

# TOTAL: 85
# PASS:  84
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See ./test-suite.log

Makefile:13300: recipe for target 'test-suite.log' failed
make[6]: *** [test-suite.log] Error 1
--- End Message ---
--- Begin Message ---
Source: syslog-ng
Source-Version: 3.10.1-1

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

Debian distribution maintenance software
pp.
SZALAY Attila  (supplier of updated syslog-ng 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, 30 Jun 2017 22:15:28 +0200
Source: syslog-ng
Binary: syslog-ng syslog-ng-dbg syslog-ng-dev syslog-ng-core 
syslog-ng-mod-journal syslog-ng-mod-json syslog-ng-mod-mongodb 
syslog-ng-mod-sql syslog-ng-mod-smtp syslog-ng-mod-amqp syslog-ng-mod-geoip 
syslog-ng-mod-redis syslog-ng-mod-stomp syslog-ng-mod-riemann 
syslog-ng-mod-graphite syslog-ng-mod-python syslog-ng-mod-add-contextual-data
Architecture: source amd64 all
Version: 3.10.1-1
Distribution: unstable
Urgency: medium
Maintainer: syslog-ng maintainers 

Changed-By: SZALAY Attila 
Description:
 syslog-ng  - Enhanced system logging daemon (metapackage)
 syslog-ng-core - Enhanced system logging daemon (core)
 syslog-ng-dbg - Enhanced system logging daemon (debug symbols)
 syslog-ng-dev - Enhanced system logging daemon (development files)
 syslog-ng-mod-add-contextual-data - Enhanced system logging daemon 
(add-contextual-data)
 syslog-ng-mod-amqp - Enhanced system logging daemon (AMQP plugin)
 syslog-ng-mod-geoip - Enhanced system logging daemon (GeoIP plugin)
 syslog-ng-mod-graphite - Enhanced system logging daemon (graphite plugin)
 syslog-ng-mod-journal - Enhanced system logging daemon (systemd journal plugin)
 syslog-ng-mod-json - Enhanced system logging daemon (JSON plugin)
 syslog-ng-mod-mongodb - Enhanced system logging daemon (MongoDB plugin)
 syslog-ng-mod-python - Enhanced system logging daemon (Python plugin)
 syslog-ng-mod-redis - Enhanced system logging daemon (Redis plugin)
 syslog-ng-mod-riemann - Enhanced system logging daemon (Riemann destination)
 syslog-ng-mod-smtp - Enhanced system logging daemon (SMTP plugin)
 syslog-ng-mod-sql - Enhanced system logging daemon (SQL plugin)
 

Bug#866688: can not connect to postgres after last update

[Ivan Sergio Borgonovo]

Package: php-horde-db
Version: 2.4.0-1
Severity: grave

After upgrading I get

  Fatal Error:
  Could not instantiate PDO. PDOException: SQLSTATE[08006] [7] server
 closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
  In /usr/share/php/Horde/Db/Adapter/Pdo/Base.php on line 48

   1. Horde_Registry::appInit() /usr/bin/horde-alarms:23
   2. Horde_Registry->__construct() /usr/share/php/Horde/Registry.php:287
   3. Horde_Session->setup() /usr/share/php/Horde/Registry.php:532
   4. Horde_Injector->createInstance() /usr/share/php/Horde/Session.php:185
   5. Horde_Injector_Binder_Factory->create()
 /usr/share/php/Horde/Injector.php:238
   6. Horde_Core_Factory_SessionHandler->create()
 /usr/share/php/Horde/Injector/Binder/Factory.php:119
   7. Horde_Core_Factory_Db->createDb()
 /usr/share/php/Horde/Core/Factory/SessionHandler.php:69
   8. Horde_Core_Factory_Db->_createDb()
 /usr/share/php/Horde/Core/Factory/Db.php:134
   9. Horde_Db_Adapter_Base->__construct()
 /usr/share/php/Horde/Core/Factory/Db.php:189
  10. Horde_Db_Adapter_Pdo_Pgsql->connect()
 /usr/share/php/Horde/Db/Adapter/Base.php:157
  11. Horde_Db_Adapter_Pdo_Base->connect()
 /usr/share/php/Horde/Db/Adapter/Pdo/Pgsql.php:88

Downgrading to 2.3.4-1 makes it work again.

I'll try to check the code later and give some more clues.

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

Bug#866512: SIGFPE when encoding H.264 video

[Steinar H. Gunderson]

reassign 866512 nageru
tags 866512 + pending
thanks

On Fri, Jun 30, 2017 at 10:22:49AM +0200, Sebastian Ramacher wrote:
>>> 1.8.3-1 just got accepted. Could you please test if the issue persits with 
>>> that
>>> version? If it's still there, we should take this upstream.
>> 1.8.3-1 has same issue.
> Thanks for checking. I've forwarded the issue upstream.

Upstream found out that it's a bug in Nageru, triggered by the fact that
1.8.x now supports VBR rate control. I have a fix in git, which will go into
the 1.6.1 release.

/* Steinar */
-- 
Homepage: https://www.sesse.net/

Processed: Re: Bug#866512: SIGFPE when encoding H.264 video

[Debian Bug Tracking System]

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

> reassign 866512 nageru
Bug #866512 [i965-va-driver] SIGFPE when encoding H.264 video
Bug reassigned from package 'i965-va-driver' to 'nageru'.
No longer marked as found in versions intel-vaapi-driver/1.8.2-2.
Ignoring request to alter fixed versions of bug #866512 to the same values 
previously set
> tags 866512 + pending
Bug #866512 [nageru] SIGFPE when encoding H.264 video
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#865964: [nvidia-legacy-304xx-driver] Does not build against 4.11 kernels

[Luca Boccassi]

On Fri, 2017-06-30 at 01:11 +0200, Andreas Beckmann wrote:
> On 2017-06-27 11:35, Luca Boccassi wrote:
> > > Package: nvidia-legacy-304xx-driver
> > > Does not build against current Sid 4.11 kernels, neither regular
> > > nor
> > Thanks for the report. It's fixed in SVN, pending the next upload.
> 
> Uploaded.
> 
> Looks like we need a similar fix for 340xx. I forward ported your
> patch (in branches/340), the drm module now builds, but thereafter it
> fails with a new error in the uvm module:
> 
> In file included from /usr/src/modules/nvidia-
> kernel/uvm/nvidia_uvm_linux.c:24:0:
> /usr/src/modules/nvidia-kernel/uvm/nvidia_uvm_linux.h: In function
> 'fatal_signal_pending':
> /usr/src/modules/nvidia-kernel/uvm/nvidia_uvm_linux.h:373:16: error:
> implicit declaration of function 'signal_pending' [-Werror=implicit-
> function-declaration]
>  return signal_pending(p) && __fatal_signal_pending(p);
> ^~
> 
> 
> Andreas

Fixed in branches/340.

I have only tested the build (on all architectures + kernels), but it's
two fairly straightforward patches.

Kind regards,
Luca Boccassi

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

Bug#864664: marked as done (CVE-2017-9122 CVE-2017-9123 CVE-2017-9124 CVE-2017-9125 CVE-2017-9126 CVE-2017-9127 CVE-2017-9128)

[Debian Bug Tracking System]

Your message dated Fri, 30 Jun 2017 21:21:07 +
with message-id 
and subject line Bug#864664: fixed in libquicktime 2:1.2.4-11
has caused the Debian Bug report #864664,
regarding CVE-2017-9122 CVE-2017-9123 CVE-2017-9124 CVE-2017-9125 CVE-2017-9126 
CVE-2017-9127 CVE-2017-9128
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.)


-- 
864664: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864664
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libquicktime
Severity: grave
Tags: security

Please see:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9122
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9123
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9124
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9125
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9126
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9127
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9128

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: libquicktime
Source-Version: 2:1.2.4-11

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

Debian distribution maintenance software
pp.
Reinhard Tartler  (supplier of updated libquicktime 
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, 30 Jun 2017 16:16:24 -0400
Source: libquicktime
Binary: libquicktime2 libquicktime-dev libquicktime-doc quicktime-utils 
quicktime-x11utils
Architecture: source
Version: 2:1.2.4-11
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Reinhard Tartler 
Description:
 libquicktime-dev - library for reading and writing Quicktime files 
(development)
 libquicktime-doc - library for reading and writing Quicktime files 
(documentation)
 libquicktime2 - library for reading and writing Quicktime files
 quicktime-utils - library for reading and writing Quicktime files (utilities)
 quicktime-x11utils - library for reading and writing Quicktime files (x11 
utilities)
Closes: 864664
Changes:
 libquicktime (2:1.2.4-11) unstable; urgency=medium
 .
   * Cherry pick security patches from upstream (Closes: #864664)
 - CVE-2017-9122
 - CVE-2017-9123
 - CVE-2017-9124
 - CVE-2017-9125
 - CVE-2017-9126
 - CVE-2017-9127
 - CVE-2017-9128
Checksums-Sha1:
 1e595a94c749f00b82fa6fe9d7638f5a83432012 2700 libquicktime_1.2.4-11.dsc
 34e65a46e47c5e55be8cc776f36c6e7b8c226844 22644 
libquicktime_1.2.4-11.debian.tar.xz
Checksums-Sha256:
 c62105c754253b0eb232f7e8a726a44ed3b9b0b401987d2a7c1f178e76eb1cde 2700 
libquicktime_1.2.4-11.dsc
 3f655fdab37fcad2d2e7d20672ff8bad6eec64a9d5a7dc702c79082346ba878b 22644 
libquicktime_1.2.4-11.debian.tar.xz
Files:
 f3f8179f9d66914f243e49a02b84b326 2700 devel optional libquicktime_1.2.4-11.dsc
 f202c9df441e3305ecbc4d07efcd67ac 22644 devel optional 
libquicktime_1.2.4-11.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE6n5rckvJ+/LRcetya3IL6cXPbZ4FAllWuzAACgkQa3IL6cXP
bZ7KlQ/9EdBa/wdBIRFlysafv6CoFyl5MTSS0e6VVyHqUcgyClbkSUs6BIenAuav
WblABB8x6FrdfvfD9oXMEON9zfNYiM27a9izmEbLmNDCZ/K7nx6kqi7v9qc3x3gr
IVIOWGqg/GZ1hiurbtAEfA0n1XV1o868i7FQ3hNYbAVxR1AGXfqYiqQ6xvTkzcd5
s6KVqlGAGtzZO7dbDXa2k6N2p+oNRG6A+3HT2BbkgvKJjG2U6xWi/Z3GJ+TVP5GF
AmyWNAJu/adBu0hRzVy7lQmVEX7TENJVA6ZOVcdZISfv6W//o4L9XiCSzcoIwAYl
YXi3EbdpUoZnVw7HukiO2Za+GvyMrWgYBoVFrXEuEAwi75BVsgY+lN/i+OS3VH5B
P7QAkJo9qdhE4HuRc7oPa2hZuKDhooLGuEvZCFLzExt9slhDpOG8PU5hvpm50Ie7
uofyaBwrFVoDSEOCKAHnBhrQs3xJGpuH7ZKuGLbddkR2NSE7HbSwssCNXHQGoDNE
CN0pT3Iz1aIhjRUspADkpfeBSmlhwWahXuCD0fdZPzeh3KGkOj7Q+Xvt+U5RlkRQ
dlpl0XXeASW3C+mmwEcq0PxSKer6Ue6UNHFzatvGdKwOnqjwlM+4LUDNP38oA0AW
mDi7YsW3d7vD2uTilVSD0ToON7W5jdlk8C14WKWRcn5HW1cfgzc=
=nwnw
-END PGP SIGNATURE End Message ---

Processed: Mark bijiben fixed-upstream for webkit2gtk porting

[Debian Bug Tracking System]

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

> tags 866633 +fixed-upstream
Bug #866633 [bijiben] bijiben: depends on libwebkitgtk-3.0-0 which is deprecated
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#864664: CVE-2017-9122 CVE-2017-9123 CVE-2017-9124 CVE-2017-9125 CVE-2017-9126 CVE-2017-9127 CVE-2017-9128

[Reinhard Tartler]

On Mon, Jun 12, 2017 at 12:06 PM Moritz Muehlenhoff  wrote:

> Source: libquicktime
> Severity: grave
> Tags: security
>
> Please see:
> http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9122
> http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9123
> http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9124
> http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9125
> http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9126
> http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9127
> http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9128
>
>
I've just uploaded a patch that should fix this. See
https://anonscm.debian.org/cgit/pkg-multimedia/libquicktime.git/commit/?id=4728e38f2045d3d33be3d442a0ab9801990b4339

This is how I tested it:
reproducible with qtinfo:

vagrant@stretch:/tmp/42148$ ls -al
total 48
drwxr-xr-x  2 vagrant vagrant 4096 Jun  9 16:41 .
drwxrwxrwt 11 rootroot4096 Jun 30 20:27 ..
-rw-r--r--  1 vagrant vagrant 6148 Jun  7 09:00 .DS_Store
-rw---  1 vagrant vagrant 1967 May 17 03:52
libquicktime_1.2.4_lqt_frame_duration_heap-buffer-overflow.mp4
-rw---  1 vagrant vagrant 1987 May 17 03:11
libquicktime_1.2.4_lqt_frame_duration_invalid_memory_read.mp4
-rw---  1 vagrant vagrant 6841 May 17 03:11
libquicktime_1.2.4_quicktime_match_32_NULL_pointer_dereference.mp4
-rw---  1 vagrant vagrant 1338 May 17 07:13
libquicktime_1.2.4_quicktime_read_dref_table_heap-buffer-overflow.mp4
-rw-r--r--  1 vagrant vagrant 1259 Dec 16  2014
libquicktime_1.2.4_quicktime_read_moov_infinite_loop.mp4
-rw---  1 vagrant vagrant 1294 May 17 02:42
libquicktime_1.2.4_quicktime_user_atoms_read_atom_heap-buffer-overflow.mp4
-rw---  1 vagrant vagrant 1192 May 18 04:53
libquicktime_1.2.4_quicktime_video_width_heap-buffer-overflow.mp4
vagrant@stretch:/tmp/42148$ qtinfo  *.mp4
Type: MP4
  0 audio tracks.
  1 video tracks.
48x144, depth 24
rate 0.000369 [12:32541] not constant
length 0 frames
compressor avc1.
Native colormodel:  Undefined
Interlace mode: None (Progressive)
No timecodes available
supported.
  0 text tracks.
Type: MP4
  0 audio tracks.
  1 video tracks.
Segmentation fault
vagrant@stretch:/tmp/42148$ qtinfo
libquicktime_1.2.4_lqt_frame_duration_heap-buffer-overflow.mp4
Type: MP4
  0 audio tracks.
  1 video tracks.
48x144, depth 24
rate 0.000367 [12:32660] not constant
length 0 frames
compressor avc1.
Native colormodel:  Undefined
Interlace mode: None (Progressive)
No timecodes available
supported.
  0 text tracks.
vagrant@stretch:/tmp/42148$ qtinfo
libquicktime_1.2.4_lqt_frame_duration_invalid_memory_read.mp4
Type: MP4
  0 audio tracks.
  1 video tracks.
Segmentation fault
vagrant@stretch:/tmp/42148$ qtinfo
libquicktime_1.2.4_quicktime_match_32_NULL_pointer_dereference.mp4
Segmentation fault
vagrant@stretch:/tmp/42148$ qtinfo
libquicktime_1.2.4_quicktime_read_dref_table_heap-buffer-overflow.mp4
Segmentation fault
vagrant@stretch:/tmp/42148$ qtinfo
libquicktime_1.2.4_quicktime_read_moov_infinite_loop.mp4
^C

vagrant@stretch:/tmp/42148$ qtinfo
libquicktime_1.2.4_quicktime_user_atoms_read_atom_heap-buffer-overflow.mp4
[ffmpeg_video] Error: No avcC atom present, decoding is likely to fail
Type: MP4
  0 audio tracks.
  1 video tracks.
Segmentation fault
vagrant@stretch:/tmp/42148$ qtinfo
libquicktime_1.2.4_quicktime_video_width_heap-buffer-overflow.mp4
[codecs] Warning: Could not find video Decoder for fourcc
[codecs] Warning: quicktime_decode_video_stub called
Type: MP4
  0 audio tracks.
  1 video tracks.
Segmentation fault


With the patch applied:

vagrant@stretch:/tmp/42148$ for i in *.mp4; do echo $i; qtinfo $i; echo
; done
libquicktime_1.2.4_lqt_frame_duration_heap-buffer-overflow.mp4
[core] Error: Opening failed (unsupported filetype)
Couldn't open libquicktime_1.2.4_lqt_frame_duration_heap-buffer-overflow.mp4

libquicktime_1.2.4_lqt_frame_duration_invalid_memory_read.mp4
[core] Error: Opening failed (unsupported filetype)
Couldn't open libquicktime_1.2.4_lqt_frame_duration_invalid_memory_read.mp4

libquicktime_1.2.4_quicktime_match_32_NULL_pointer_dereference.mp4
[core] Error: Opening failed (unsupported filetype)
Couldn't open
libquicktime_1.2.4_quicktime_match_32_NULL_pointer_dereference.mp4

libquicktime_1.2.4_quicktime_read_dref_table_heap-buffer-overflow.mp4
[core] Error: Opening failed (unsupported filetype)
Couldn't open
libquicktime_1.2.4_quicktime_read_dref_table_heap-buffer-overflow.mp4

libquicktime_1.2.4_quicktime_read_moov_infinite_loop.mp4
[core] Error: Opening failed (unsupported filetype)
Couldn't open libquicktime_1.2.4_quicktime_read_moov_infinite_loop.mp4

libquicktime_1.2.4_quicktime_user_atoms_read_atom_heap-buffer-overflow.mp4
[core] Error: Opening failed (unsupported filetype)
Couldn't open
libquicktime_1.2.4_quicktime_user_atoms_read_atom_heap-buffer-overflow.mp4

Processed: Bug#864664 marked as pending

[Debian Bug Tracking System]

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

> tag 864664 pending
Bug #864664 [src:libquicktime] CVE-2017-9122 CVE-2017-9123 CVE-2017-9124 
CVE-2017-9125 CVE-2017-9126 CVE-2017-9127 CVE-2017-9128
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#864664: marked as pending

[Reinhard Tartler]

tag 864664 pending
thanks

Hello,

Bug #864664 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://anonscm.debian.org/git/pkg-multimedia/libquicktime.git/commit/?id=4728e38

---
commit 4728e38f2045d3d33be3d442a0ab9801990b4339
Author: Reinhard Tartler 
Date:   Fri Jun 30 16:18:03 2017 -0400

add security patches

diff --git a/debian/changelog b/debian/changelog
index 9a25361..4472aab 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,16 @@
+libquicktime (2:1.2.4-11) unstable; urgency=medium
+
+  * Cherry pick security patches from upstream (Closes: #864664)
+- CVE-2017-9122
+- CVE-2017-9123
+- CVE-2017-9124
+- CVE-2017-9125
+- CVE-2017-9126
+- CVE-2017-9127
+- CVE-2017-9128
+
+ -- Reinhard Tartler   Fri, 30 Jun 2017 16:16:24 -0400
+
 libquicktime (2:1.2.4-10) unstable; urgency=medium
 
   * Fix integer overflow in the quicktime_read_pascal function (CVE-2016-2399)

Bug#790201: geany-plugins: depends on libwebkitgtk-1.0-0 which is deprecated

[Jeremy Bicha]

Fedora "fixed" this issue by disabling geany's webkit plugins.

Thanks,
Jeremy Bicha

Bug#790222: wxwidgets3.0: depends on libwebkitgtk-1.0-0 which is deprecated

[Jeremy Bicha]

Control: tags -1 +fixed-upstream

According to the upstream issue, this is fixed in the 3.0 branch after
the 3.0.3 release.

https://github.com/wxWidgets/wxWidgets/pull/469

Thanks,
Jeremy Bicha

Processed: wxwidgets3.0: depends on libwebkitgtk-1.0-0 which is deprecated

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +fixed-upstream
Bug #790222 [src:wxwidgets3.0] wxwidgets3.0: depends on libwebkitgtk-1.0-0 
which is deprecated
Added tag(s) fixed-upstream.

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

Processed: found 790216 in 0.0.0~git.20120514-1.2

[Debian Bug Tracking System]

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

> found 790216 0.0.0~git.20120514-1.2
Bug #790216 [src:uzbl] uzbl: depends on libwebkitgtk-1.0-0 which is deprecated
Marked as found in versions uzbl/0.0.0~git.20120514-1.2.
> thanks
Stopping processing here.

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

Bug#866655: variety: depends on libwebkitgtk-3.0-0 which is deprecated

[Jeremy Bicha]

On Fri, Jun 30, 2017 at 4:18 PM, James Lu  wrote:
> To speed up the process, is there any simple porting guide between WebKitGTK 
> 3 and WebKit2GTK 4? The only working feature in Variety using WebKit at the 
> moment is Facebook integration, which is difficult for me to test because I 
> don't feel comfortable with programs posting to Facebook on my behalf.

According to this post [1] by one of the webkitgtk developers a year
ago, there is no transition documentation.

[1] 
https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/message/FU4X4Y3EC7KPTMCCYJ4HHY7JNF4OE3LC/

Thanks,
Jeremy Bicha

Bug#865224: uwsgi: ftbfs with multiple supported python3 versions

[Jonas Smedegaard]

Quoting Scott Kitterman (2017-06-30 08:25:19)
> On Tue, 20 Jun 2017 11:26:35 +1200 Michael Hudson-Doyle 
>  wrote:
> > This may well turn out to be a cdbs bug in the end, but uwsgi does 
> > not build when pysupport -r returns more than one version:
> > 
> > https://launchpadlibrarian.net/323025281/buildlog_ubuntu-artful-amd64.uwsgi_2.0.15-1ubuntu3_BUILDING.txt.gz
> > 
> > Picking out the failing lines:
> > 
> > *** asyncio_python27 plugin built and available in 
> > ./asyncio_python27_plugin.so ***
> > touch debian/stamp-uwsgi-plugin-asyncio-python
> > debian/rules:452: *** no python implementation resolved from flavor 
> > "python3.6" among packages python-uwsgidecorators python3-uwsgidecorators.  
> > Stop.
> > 
> > In this build python 3.5 is the default and python 3.6 is supported. 
> > In a build where python 3.6 is default and python 3.5 is supported, 
> > the error complains about python 3.5 instead. And if python 3.6 is 
> > the only supported version, the build completes successfully. So I 
> > think this is really a problem in uwsgi or cdbs' handling of 
> > multiple supported python versions.
> 
> We now have this in Debian, so bumping to serious.

Thanks, both for reporting initially and for bumping!

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#866655: variety: depends on libwebkitgtk-3.0-0 which is deprecated

[James Lu]

Control: forwarded 866655 https://bugs.launchpad.net/variety/+bug/1701724

Hi Jeremy,

To speed up the process, is there any simple porting guide between WebKitGTK 3 
and WebKit2GTK 4? The only working feature in Variety using WebKit at the 
moment is Facebook integration, which is difficult for me to test because I 
don't feel comfortable with programs posting to Facebook on my behalf.

I've forwarded the issue upstream and I'll see how they respond; if there's 
nothing within a week or two I will probably just patch out Facebook 
integration for the time being.

Best,
James

On 30/06/17 09:22 AM, Jeremy Bicha wrote:
> Source: variety
> Severity: serious
> Tags: sid buster
> User: pkg-webkit-maintain...@lists.alioth.debian.org
> Usertags: oldlibs libwebkitgtk-3.0-0 webkit1
> 
> Hi,
> 
> variety depends on gir1.2-webkit-3.0, which is deprecated
> in favor of gir1.2-webkit2-4.0 (provided in Debian by webkit2gtk). It
> should be ported to the new webkitgtk version so we
> can remove the old, unmaintained one.
> 
> Please try to do soon as we're going to try to remove the old webkitgtk soon.
> 
> I am filing this bug as "serious" since the old webkitgtk will not be
> available in the next major stable release of Debian (codenamed
> "buster").
> 
> If you have any question don't hesitate to ask.
> 
> On behalf of the Debian WebKit Maintainers,
> Jeremy Bicha
> 

Processed: Re: Bug#866655: variety: depends on libwebkitgtk-3.0-0 which is deprecated

[Debian Bug Tracking System]

Processing control commands:

> forwarded 866655 https://bugs.launchpad.net/variety/+bug/1701724
Bug #866655 [src:variety] variety: depends on libwebkitgtk-3.0-0 which is 
deprecated
Set Bug forwarded-to-address to 
'https://bugs.launchpad.net/variety/+bug/1701724'.

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

Processed: fixed 866564 in 1:9.9.5.dfsg-9+deb8u12, fixed 866564 in 1:9.10.3.dfsg.P4-12.3+deb9u1, tagging 866564

[Debian Bug Tracking System]

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

> # Add fixing versions for DSA uploads
> fixed 866564 1:9.9.5.dfsg-9+deb8u12
Bug #866564 [src:bind9] bind9: CVE-2017-3142 CVE-2017-3143
The source 'bind9' and version '1:9.9.5.dfsg-9+deb8u12' do not appear to match 
any binary packages
Marked as fixed in versions bind9/1:9.9.5.dfsg-9+deb8u12.
> fixed 866564 1:9.10.3.dfsg.P4-12.3+deb9u1
Bug #866564 [src:bind9] bind9: CVE-2017-3142 CVE-2017-3143
The source 'bind9' and version '1:9.10.3.dfsg.P4-12.3+deb9u1' do not appear to 
match any binary packages
Marked as fixed in versions bind9/1:9.10.3.dfsg.P4-12.3+deb9u1.
> tags 866564 + pending
Bug #866564 [src:bind9] bind9: CVE-2017-3142 CVE-2017-3143
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#866668: src:python-cryptography: Misbuild with more than one supported python3 version

[Tristan Seligmann]

Control: severity -1 important

On Fri, 30 Jun 2017 at 19:33 Scott Kitterman  wrote:

> Technically, it builds, but in a way that's not useful.  It would actually
> be
> better if it had failed (I noticed this from reviewing build logs after the
> python3 interpreter depends weren't generated correctly).
>

In fact, the package works fine on python3.5 as well as python3.6 (the
module imports, and the full test suite passes against the installed
modules), thus I'm downgrading the severity of this bug.

During the build, the extension modules are first built on python3.5, and
it is these modules that land in /usr/lib/python3, with the "abi3" ABI tag.
The extension modules are then built again on python3.6, but these don't
get moved into /usr/lib/python3 due to the files from the python3.5 build
having the same name, thus landing in an incorrect directory in the  final
package and serving no useful purpose.

The reason the package still works is the "abi3" ABI tag; these modules
(like all CFFI-built modules, by default) are using the Python 3 "stable
ABI"[1] so the modules built on python3.5 work fine when imported on
python3.6, and vice-versa. I think what this means is that we only need to
run the Python 3 build once (using the default version?); also, I think the
interpreter depends are in fact correct in light of this. I tested
downgrading to 1.7.1-3 and the module still imports and works on python3.6,
even though 1.7.1-3 was only ever built against python3.5.

However, testing against all supported versions at build time is probably
still appropriate.

I'm looping in debian-python here as others may be surprised by this
combination of effects as well, and we should probably be handling the
issue of modules using the stable ABI consistently. Also, I'm not 100%
certain what the best way forward is here; teach pybuild/dh_python3 about
the stable ABI?

[1] https://docs.python.org/3/c-api/stable.html

Processed: notfixed 863040 in 4.2-1+deb8u2, tagging 863040, found 863040 in 4.2-1 ...

[Debian Bug Tracking System]

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

> #unconfuse the bts: found+fixed in the same version
> notfixed 863040 4.2-1+deb8u2
Bug #863040 {Done: Philip Rinn } [rawtherapee] 
rawtherapee: Crash at lauch time with message: Error in rawtherapee: 
munmap_chunk(): invalid pointer
No longer marked as fixed in versions rawtherapee/4.2-1+deb8u2.
> tags 863040 + unreproducible
Bug #863040 {Done: Philip Rinn } [rawtherapee] 
rawtherapee: Crash at lauch time with message: Error in rawtherapee: 
munmap_chunk(): invalid pointer
Added tag(s) unreproducible.
> found 863040 4.2-1
Bug #863040 {Done: Philip Rinn } [rawtherapee] 
rawtherapee: Crash at lauch time with message: Error in rawtherapee: 
munmap_chunk(): invalid pointer
Marked as found in versions rawtherapee/4.2-1.
> notfixed 849146 2:4.5.2+dfsg-1
Bug #849146 {Done: Mathieu Parent } [samba] samba: empty 
client domain is not mapped to standalone server domain when user name contains 
@
No longer marked as fixed in versions 2:4.5.2+dfsg-1.
> thanks
Stopping processing here.

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

Processed: Re: Bug#866668: src:python-cryptography: Misbuild with more than one supported python3 version

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #88 [src:python-cryptography] src:python-cryptography: Misbuild with 
more than one supported python3 version
Severity set to 'important' from 'serious'

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

Processed: python3-cairo: breaks apt upgrades due to conflict with debconf

[Debian Bug Tracking System]

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

> fixed 83 1.10.0+dfsg-5+b3
Bug #83 [python3-cairo] python3-cairo: It seems to conflict  with debconf
Marked as fixed in versions py3cairo/1.10.0+dfsg-5.
> thanks
Stopping processing here.

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

Bug#866663: python3-cairo: breaks apt upgrades due to conflict with debconf

[Harlan Lieberman-Berg]

fixed 83 1.10.0+dfsg-5+b3
thanks

This looks like an instance of #866572 that was fixed with the next build.

-- 
Harlan Lieberman-Berg
~hlieberman

Bug#866372: marked as done (boxbackup FTBFS on arm64/mips64el: error: 'SYS_open' was not declared in this scope)

[Debian Bug Tracking System]

Your message dated Fri, 30 Jun 2017 19:37:08 +
with message-id 
and subject line Bug#866372: fixed in boxbackup 0.12~gitcf52058f-3
has caused the Debian Bug report #866372,
regarding boxbackup FTBFS on arm64/mips64el: error: 'SYS_open' was not declared 
in this scope
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.)


-- 
866372: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: boxbackup
Version: 0.12~gitcf52058f-2
Severity: serious

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

...
intercept.cpp: In function 'int open(const char*, int, ...)':
intercept.cpp:248:25: error: 'SYS_open' was not declared in this scope
intercept_syscall == SYS_open &&
 ^~~~
intercept.cpp:268:18: error: 'SYS_open' was not declared in this scope
  int r = syscall(SYS_open, path, flags, mode);
  ^~~~
...
common: PASSED
crypto: PASSED
compress: PASSED
raidfile: make failed
basicserver: PASSED
backupstore: PASSED
backupstorefix: PASSED
backupstorepatch: PASSED
backupdiff: PASSED
bbackupd: make failed
s3store: PASSED
httpserver: PASSED
...
--- End Message ---
--- Begin Message ---
Source: boxbackup
Source-Version: 0.12~gitcf52058f-3

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

Debian distribution maintenance software
pp.
Reinhard Tartler  (supplier of updated boxbackup 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, 30 Jun 2017 15:01:19 -0400
Source: boxbackup
Binary: boxbackup-server boxbackup-client
Architecture: source
Version: 0.12~gitcf52058f-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Reinhard Tartler 
Description:
 boxbackup-client - client for the BoxBackup remote backup system
 boxbackup-server - server for the BoxBackup remote backup system
Closes: 866372
Changes:
 boxbackup (0.12~gitcf52058f-3) unstable; urgency=medium
 .
   * QA upload.
   * Run the testsuite on amd64 and i386 only (Closes: #866372)
Checksums-Sha1:
 2c412de1ade8a62c03c726ec68f3d5f4436c6c15 2177 boxbackup_0.12~gitcf52058f-3.dsc
 ecdad32e67c25dd8d47cc0ef825e90220537a162 63920 
boxbackup_0.12~gitcf52058f-3.debian.tar.xz
Checksums-Sha256:
 4f21039380066e888bec0425299ff982253b2481f6f192b1a7156a0418acd746 2177 
boxbackup_0.12~gitcf52058f-3.dsc
 c3d77455c146bcd5ea6510b1035682f0d5c5c63581f9107e1c0b661d997271ca 63920 
boxbackup_0.12~gitcf52058f-3.debian.tar.xz
Files:
 d3130bce5d7e0f6cf2176d6ee7b90dbf 2177 utils optional 
boxbackup_0.12~gitcf52058f-3.dsc
 bd98a2c446b8b325271024a67e3cc9bf 63920 utils optional 
boxbackup_0.12~gitcf52058f-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE6n5rckvJ+/LRcetya3IL6cXPbZ4FAllWpH4ACgkQa3IL6cXP
bZ4kgA//aLpvbCZibW77/wwpFpHV2x4iLgC8j6ebLR5BRfUWaPdW8dW3OaDGEot8
SYA4CMpJjachuCeqwsjSeGoZ/KDcPIbd4+5zxlJ/o1l83Fftyql2H18mD3JhIJMj
RyjzhMxADSVYFtM7yctR3zbumYxxgerNiR3gG7DpfJGsWBfPMIPGmaNORFZE76Qu
6OYBvt9HGQys/kALMq+mGhhTJB9ZYu/0bRHD/a6Z79FpEshRZaiVqvkM+tcEyC1F
4i/cg/I5eWhd6HH1bNOcgduWbulatV9viCNr+3OHKcWMfz11AiSV3WSqogvm2/NT
kUgdPSo8XR0bgB/phqTDzauijJfJmHpzKJ8TGBkcrTA2Ea47EsKZMs38L09EeePs
N6DAxZJYI7tSdTpJphi71zL9XqksV37un0WACAEKDm7Hpd6iE6fXp/A7s1n+0FTL
5ZAlZyPH+UfDOIlVqarKEMDRRHrUvKE9tXF2IxHFoA5ut3VIo+c87Pm6QnwJM+aV
IqlrkO8W0M9pv6tTqfXoa8awFth3icIR5f+wRkLuo1ch+e33KAGKrvQ6NXCfBCpC
Y7b14vbsuwUdVzSY/wi/OMtDmVLT1taXJjz3IL6EHZfxywAUdecg+emStzY7Hr24
ov55QrnphORvBqi9Caflf33cwIBMfmb9wQhAiQD7TsTl0/hR47s=
=p5DN
-END PGP SIGNATURE End Message ---

Bug#790221: [xtrkcad] Raising severity to serious for packages depending on webkitgtk

[Mike Gabriel]

Hi all,

On  Fr 30 Jun 2017 16:26:21 CEST, Jeremy Bicha wrote:


Control: severity -1 serious
Control: tags -1 -stretch

We do not intend to release the next stable release of Debian
(codenamed "buster") with webkitgtk. Therefore, I am raising the
severity of this issue to serious. Please drop the dependency on
webkitgtk because webkitgtk will be removed from Debian soon.

On behalf of the Debian GNOME team,
Jeremy Bicha


@Jörg: please dput xtrkcad 4.3.0 as you have it soon. I haven't seen  
feedback from Daniel, have you?


I have been playing with webkit1 -> webkit2 transitions lately in some  
other context, so I can take a look at this bug (#790221).


Thanks + Greets,
Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpfJ5Phk9RMP.pgp
Description: Digitale PGP-Signatur

Bug#724767: marked as done (Uses deprecated find -perm +xxx syntax, please switch to find -perm /+++)

[Debian Bug Tracking System]

Your message dated Fri, 30 Jun 2017 19:20:10 +
with message-id 
and subject line Bug#724767: fixed in clisp 1:2.49.60+-1
has caused the Debian Bug report #724767,
regarding Uses deprecated find -perm +xxx syntax, please switch to find -perm 
/+++
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.)


-- 
724767: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724767
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: clisp
Version: 1:2.49-8.2
User: ametz...@debian.org
Usertags: find_perm_plus

Hello,

the clisp source package uses find -perm +xxx. This GNU extension
syntax is deprecated and does not work in GNU findutils 4.5.11 and
later. Please change to find -perm /xxx instead.

The new syntax was introduced in 4.2.25 (October 2005) and should
therefore be available on any relevant system.

--
ametzler@argenau:/tmp/BUGS$ grep -lr -- '-perm +' clisp-2.49
clisp-2.49/utils/fix-perms.sh
--

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
--- End Message ---
--- Begin Message ---
Source: clisp
Source-Version: 1:2.49.60+-1

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

Debian distribution maintenance software
pp.
Peter Van Eynde  (supplier of updated clisp 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, 30 Jun 2017 09:47:30 +0200
Source: clisp
Binary: clisp clisp-dev clisp-doc clisp-module-berkeley-db clisp-module-pcre 
clisp-module-bindings-glibc clisp-module-postgresql clisp-module-clx 
clisp-module-rawsock clisp-module-dbus clisp-module-gdbm clisp-module-zlib
Architecture: source amd64 all
Version: 1:2.49.60+-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Common Lisp Team 

Changed-By: Peter Van Eynde 
Description:
 clisp  - GNU CLISP, a Common Lisp implementation
 clisp-dev  - GNU CLISP, a Common Lisp implementation (development files)
 clisp-doc  - GNU CLISP, a Common Lisp implementation (documentation)
 clisp-module-berkeley-db - clisp module that adds an interface to Berkeley DB
 clisp-module-bindings-glibc - clisp module that adds the glibc bindings
 clisp-module-clx - clisp module that adds X11 bindings
 clisp-module-dbus - clisp module that adds an interface to D-Bus
 clisp-module-gdbm - clisp module that adds an interface to GNU DBM
 clisp-module-pcre - clisp module that adds libpcre support
 clisp-module-postgresql - clisp module that adds a PostgreSQL interface
 clisp-module-rawsock - clisp module that adds a low level socket interface
 clisp-module-zlib - clisp module that adds zlib support for vectors
Closes: 724767 801260
Changes:
 clisp (1:2.49.60+-1) unstable; urgency=medium
 .
   * New upstream snapshot release.
 - fixes the -perm problem (Closes: #724767)
   * Imported the changes from experimental:
 * Import patch from Flavio Cruz for hurd, thanks! (Closes: #801260)
 * Remove all patches (apart from hurd/webbugs) for now. Will re-add as
   needed
 * Drop wildcard package; dropped upstream
   * Use the new libsigsegv to build.
Checksums-Sha1:
 755d17e7ba2f20a303e7275723f1b363f08e1dda 4867 clisp_2.49.60+-1.dsc
 9ea18b5355613ab96f6cdad5a5303131c1242bb9 10690323 clisp_2.49.60+.orig.tar.gz
 2a2dabf3e8d2d5b7453e132862d8aa742263682f 30444 clisp_2.49.60+-1.debian.tar.xz
 1b7287d1467bb4f92f52abbee49e79f2f043fc3f 44268 
clisp-dbgsym_2.49.60+-1_amd64.deb
 ac759d6eda7ed6efe6bd24b7eecf81957fdc15cc 1409878 clisp-dev_2.49.60+-1_amd64.deb
 c4c75d03e9f032d631057824a65985671b59381b 1126022 clisp-doc_2.49.60+-1_all.deb
 ebd6bcdc94009694f3077997f4207a0f2030defc 4744 
clisp-module-berkeley-db-dbgsym_2.49.60+-1_amd64.deb
 cc870898ae2de62569ff5bdcb64772c6b3b3af2d 716202 
clisp-module-berkeley-db_2.49.60+-1_amd64.deb
 3e0b7e8f6b40b3d8fd2b91d431ade037f7be4f40 4686 
clisp-module-bindings-glibc-dbgsym_2.49.60+-1_amd64.deb
 

Bug#866677: rkhunter: CVE-2017-7480: File download via http might lead to RCE

[Salvatore Bonaccorso]

Source: rkhunter
Version: 1.4.2-0.4
Severity: grave
Tags: upstream security

Hi,

the following vulnerability was published for rkhunter (somehow
releated will be at least #765895)

CVE-2017-7480[0]:
File download via http might lead to RCE

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-7480
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7480
[1] http://www.openwall.com/lists/oss-security/2017/06/29/2
[2] http://rkhunter.cvs.sourceforge.net/viewvc/rkhunter/rkhunter/files/CHANGELOG
[3] 
http://rkhunter.cvs.sourceforge.net/viewvc/rkhunter/rkhunter/files/rkhunter?r1=1.549=1.550

Regards,
Salvatore

Bug#866676: libxml-libxml-perl: CVE-2017-10672: Use-after-free in XML::LibXML::Node::replaceChild

[Salvatore Bonaccorso]

Source: libxml-libxml-perl
Version: 2.0116+dfsg-1
Severity: grave
Tags: security upstream
Forwarded: https://rt.cpan.org/Ticket/Display.html?id=122246

Hi,

the following vulnerability was published for libxml-libxml-perl.
Filling this one for now as severity grave, but we might adjust later
the severity if not appropriate.

CVE-2017-10672[0]:
| Use-after-free in the XML-LibXML module through 2.0129 for Perl allows
| remote attackers to execute arbitrary code by controlling the arguments
| to a replaceChild call.

There is no upstream fix yet.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-10672
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10672
[1] https://rt.cpan.org/Ticket/Display.html?id=122246

Regards,
Salvatore

Bug#866671: webkitgtk: Unmaintained, not suitable for buster

[Jeremy Bicha]

Source: webkitgtk
Severity: serious
Tags: sid buster
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs libwebkitgtk-3.0-0 webkit1

Hi,

I am opening a tracking bug since we do not want webkitgtk in the next
major stable release of Debian ('buster").

Packages that use webkitgtk should be ported to webkit2gtk. Otherwise,
they will eventually need to be removed from Debian.

On behalf of the Debian WebKit Maintainers,
Jeremy Bicha

Bug#866663: python3-cairo: It seems to conflict with debconf

[Luis Henriques]

On Fri, 30 Jun 2017 18:50:34 +0200 =?utf-8?q?Manolo_D=C3=ADaz?=
 wrote:
> Package: python3-cairo
> Version: 1.10.0+dfsg-5+b2
> Severity: serious
> Justification: Policy 7.4
> 
> Dear Maintainer,
> 
> This happens when I try to upgrade python3-cairo:
> 
> (Reading database ... 254270 files and directories currently installed.)
> Preparing to unpack .../python3-cairo_1.10.0+dfsg-5+b2_amd64.deb ...
> Unpacking python3-cairo (1.10.0+dfsg-5+b2) over (1.10.0+dfsg-5+b1) ...
> dpkg: error processing archive
/var/cache/apt/archives/python3-cairo_1.10.0+dfsg-5+b2_amd64.deb (--unpack):
>  trying to overwrite '/usr/lib/python2.7/dist-packages/debconf.py',
which is also in package debconf 1.5.61
> dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
> Errors were encountered while processing:
>  /var/cache/apt/archives/python3-cairo_1.10.0+dfsg-5+b2_amd64.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> 

I can confirm this bug -- I'm seeing exactly the same conflict.

Cheers,
-- 
Luis

> 
> Kind Regards,
> Manolo D
-az
> 
> -- System Information:
> Debian Release: 9.0
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.11.8 (SMP w/2 CPU cores)
> Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8),
> LANGUAGE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked
> to /usr/bin/dash Init: systemd (via /run/systemd/system)
> 
> Versions of packages python3-cairo depends on:
> ii  libc6  2.24-12
> ii  libcairo2  1.14.8-1
> ii  python33.5.3-1
> 
> python3-cairo recommends no packages.
> 
> python3-cairo suggests no packages.
> 
> -- no debconf information

Bug#858388: cmtk: diff for NMU version 3.3.1-1.2

[Adrian Bunk]

Control: tags 858388 + patch
Control: tags 858388 + pending

Dear maintainer,

I've prepared an NMU for cmtk (versioned as 3.3.1-1.2) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should cancel it or delay it longer.

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

diff -Nru cmtk-3.3.1/debian/changelog cmtk-3.3.1/debian/changelog
--- cmtk-3.3.1/debian/changelog	2017-01-13 20:16:35.0 +0200
+++ cmtk-3.3.1/debian/changelog	2017-06-30 20:37:50.0 +0300
@@ -1,3 +1,10 @@
+cmtk (3.3.1-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS by using libssl-dev. (Closes: #858388)
+
+ -- Adrian Bunk   Fri, 30 Jun 2017 20:37:50 +0300
+
 cmtk (3.3.1-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru cmtk-3.3.1/debian/control cmtk-3.3.1/debian/control
--- cmtk-3.3.1/debian/control	2017-01-13 20:16:14.0 +0200
+++ cmtk-3.3.1/debian/control	2017-06-30 20:37:46.0 +0300
@@ -18,7 +18,7 @@
libwrap0-dev,
libcharls-dev | libdcmtk1-dev | libdcmtk2-dev (<< 3.6.0-8~),
libxml2-dev,
-   libssl1.0-dev | libssl-dev (<< 1.1.0),
+   libssl-dev,
xvfb, bc, dc,
xauth,
 Standards-Version: 3.9.8

Processed: cmtk: diff for NMU version 3.3.1-1.2

[Debian Bug Tracking System]

Processing control commands:

> tags 858388 + patch
Bug #858388 [src:cmtk] cmtk: Please migrate to openssl1.1 in buster
Added tag(s) patch.
> tags 858388 + pending
Bug #858388 [src:cmtk] cmtk: Please migrate to openssl1.1 in buster
Added tag(s) pending.

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

Bug#866668: src:python-cryptography: Misbuild with more than one supported python3 version

[Scott Kitterman]

Package: src:python-cryptography
Version: 1.9-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Technically, it builds, but in a way that's not useful.  It would actually be
better if it had failed (I noticed this from reviewing build logs after the
python3 interpreter depends weren't generated correctly).

The compiled elements of the python3 package are missing for python3.5 and in
the wrong location for python3.6:

 ./usr/lib/python3.6/dist-packages/
 ./usr/lib/python3.6/dist-packages/cryptography/
 ./usr/lib/python3.6/dist-packages/cryptography/hazmat/
 ./usr/lib/python3.6/dist-packages/cryptography/hazmat/bindings/
 
./usr/lib/python3.6/dist-packages/cryptography/hazmat/bindings/_constant_time.abi3.so
 ./usr/lib/python3.6/dist-packages/cryptography/hazmat/bindings/_openssl.abi3.so
 ./usr/lib/python3.6/dist-packages/cryptography/hazmat/bindings/_padding.abi3.so

https://buildd.debian.org/status/fetch.php?pkg=python-cryptography=amd64=1.9-1=1498830154=0

They should be in /usr/lib/python3 and ABI tagged.

Scott K

Processed: Add the tags I forgot

[Debian Bug Tracking System]

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

> tags 82 buster sid
Bug #82 [src:golang-gopkg-mcuadros-go-syslog.v2] 
golang-gopkg-mcuadros-go-syslog.v2 FTBFS: FAIL: rfc6587_test.go:48: 
FormatSuite.TestRFC6587_GetSplitBadSplit
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#866663: python3-cairo: It seems to conflict with debconf

[Manolo Díaz]

Package: python3-cairo
Version: 1.10.0+dfsg-5+b2
Severity: serious
Justification: Policy 7.4

Dear Maintainer,

This happens when I try to upgrade python3-cairo:

(Reading database ... 254270 files and directories currently installed.)
Preparing to unpack .../python3-cairo_1.10.0+dfsg-5+b2_amd64.deb ...
Unpacking python3-cairo (1.10.0+dfsg-5+b2) over (1.10.0+dfsg-5+b1) ...
dpkg: error processing archive 
/var/cache/apt/archives/python3-cairo_1.10.0+dfsg-5+b2_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/python2.7/dist-packages/debconf.py', which is 
also in package debconf 1.5.61
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/python3-cairo_1.10.0+dfsg-5+b2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


Kind Regards,
Manolo Díaz

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

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

Versions of packages python3-cairo depends on:
ii  libc6  2.24-12
ii  libcairo2  1.14.8-1
ii  python33.5.3-1

python3-cairo recommends no packages.

python3-cairo suggests no packages.

-- no debconf information

Processed: closing 866630

[Debian Bug Tracking System]

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

> close 866630 2.5.3-1
Bug #866630 [balsa] balsa: depends on libwebkitgtk-1.0-0 which is deprecated
Marked as fixed in versions balsa/2.5.3-1.
Bug #866630 [balsa] balsa: depends on libwebkitgtk-1.0-0 which is deprecated
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#866630: closing 866630

[Laurent Bigonville]

close 866630 2.5.3-1
thanks

This is fixed in the 2.5 series

Closing this bug

Cheers,

Laurent Bigonville

Bug#866662: golang-gopkg-mcuadros-go-syslog.v2 FTBFS: FAIL: rfc6587_test.go:48: FormatSuite.TestRFC6587_GetSplitBadSplit

[Adrian Bunk]

Source: golang-gopkg-mcuadros-go-syslog.v2
Version: 2.1.1-1
Severity: serious

Some recent change in unstable makes golang-gopkg-mcuadros-go-syslog.v2 FTBFS:

https://tests.reproducible-builds.org/debian/history/golang-gopkg-mcuadros-go-syslog.v2.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-gopkg-mcuadros-go-syslog.v2.html

...
   dh_auto_test -O--buildsystem=golang
go test -v -p 1 gopkg.in/mcuadros/go-syslog.v2 
gopkg.in/mcuadros/go-syslog.v2/format
=== RUN   Test
OK: 12 passed
--- PASS: Test (0.41s)
PASS
ok  gopkg.in/mcuadros/go-syslog.v2  0.423s
=== RUN   Test

--
FAIL: rfc6587_test.go:48: FormatSuite.TestRFC6587_GetSplitBadSplit

rfc6587_test.go:64:
c.Assert(err, ErrorMatches, "strconv.ParseInt: parsing \".2\": invalid 
syntax")
... error string = "strconv.Atoi: parsing \".2\": invalid syntax"
... regex string = "strconv.ParseInt: parsing \".2\": invalid syntax"

OOPS: 4 passed, 1 FAILED
--- FAIL: Test (0.00s)
FAIL
exit status 1
FAILgopkg.in/mcuadros/go-syslog.v2/format   0.010s
dh_auto_test: go test -v -p 1 gopkg.in/mcuadros/go-syslog.v2 
gopkg.in/mcuadros/go-syslog.v2/format returned exit code 1
debian/rules:6: recipe for target 'build' failed
make: *** [build] Error 1

Bug#866661: htmlunit: missing build dependency on junit4

[Adrian Bunk]

Source: htmlunit
Version: 2.8-2
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/htmlunit.html

...
   dh_auto_build
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/htmlunit-2.8 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/1st/htmlunit-2.8/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/build/1st/htmlunit-2.8/debian 
-Dmaven.repo.local=/build/1st/htmlunit-2.8/debian/maven-repo package 
-DskipTests -Dnotimestamp=true -Dlocale=en_US
[INFO] Scanning for projects...
[WARNING] 
[WARNING] Some problems were encountered while building the effective 
model for net.sourceforge.htmlunit:htmlunit:jar:2.8
[WARNING] The expression ${pom.url} is deprecated. Please use 
${project.url} instead.
[WARNING] 
[WARNING] It is highly recommended to fix these problems because they 
threaten the stability of your build.
[WARNING] 
[WARNING] For this reason, future Maven versions might no longer 
support building such malformed projects.
[WARNING] 
[INFO] 
[INFO] 

[INFO] Building HtmlUnit 2.8
[INFO] 

[WARNING] The POM for junit:junit:jar:4.x is missing, no dependency 
information available
[INFO] 

[INFO] BUILD FAILURE
[INFO] 

[INFO] Total time: 0.439 s
[INFO] Finished at: 2018-08-02T10:58:59-12:00
[INFO] Final Memory: 16M/724M
[INFO] 

[ERROR] Failed to execute goal on project htmlunit: 
Could not resolve dependencies for project 
net.sourceforge.htmlunit:htmlunit:jar:2.8: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
junit:junit:jar:4.x has not been downloaded from it before. -> [Help 
1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with 
the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug 
logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, 
please read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/htmlunit-2.8 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/1st/htmlunit-2.8/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/build/1st/htmlunit-2.8/debian 
-Dmaven.repo.local=/build/1st/htmlunit-2.8/debian/maven-repo package 
-DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1
debian/rules:4: recipe for target 'build' failed
make: *** [build] Error 2

Bug#866657: xiphos: depends on libwebkitgtk-3.0-0 which is deprecated

[Jeremy Bicha]

Source: xiphos
Severity: serious
Tags: sid buster
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs libwebkitgtk-3.0-0 webkit1

Hi,

xiphos depends on libwebkitgtk-3.0-0, which is deprecated in
favor of libwebkit2gtk-4.0-37 (provided in Debian by webkit2gtk).
xiphos should be ported to the new webkitgtk version so we
can remove the old, unmaintained one.

Please try to do soon as we're going to try to remove the old webkitgtk soon.

I am filing this bug as "serious" since the old webkitgtk will not be
available in the next major stable release of Debian (codenamed
"buster").

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

On behalf of the Debian WebKit Maintainers,
Jeremy Bicha

Bug#866656: webkitgtk-sharp3: depends on libwebkitgtk-3.0-0 which is deprecated

[Jeremy Bicha]

Source: webkitgtk-sharp3
Severity: serious
Tags: sid buster
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs libwebkitgtk-3.0-0 webkit1

Hi,

webkitgtk-sharp3 depends on libwebkitgtk-3.0-0, which is deprecated in
favor of libwebkit2gtk-4.0-37 (provided in Debian by webkit2gtk).
webkitgtk-sharp3 should be ported to the new webkitgtk version so we
can remove the old, unmaintained one.

Please try to do soon as we're going to try to remove the old webkitgtk soon.

I am filing this bug as "serious" since the old webkitgtk will not be
available in the next major stable release of Debian (codenamed
"buster").

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

On behalf of the Debian WebKit Maintainers,
Jeremy Bicha

Bug#866655: variety: depends on libwebkitgtk-3.0-0 which is deprecated

[Jeremy Bicha]

Source: variety
Severity: serious
Tags: sid buster
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs libwebkitgtk-3.0-0 webkit1

Hi,

variety depends on gir1.2-webkit-3.0, which is deprecated
in favor of gir1.2-webkit2-4.0 (provided in Debian by webkit2gtk). It
should be ported to the new webkitgtk version so we
can remove the old, unmaintained one.

Please try to do soon as we're going to try to remove the old webkitgtk soon.

I am filing this bug as "serious" since the old webkitgtk will not be
available in the next major stable release of Debian (codenamed
"buster").

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

On behalf of the Debian WebKit Maintainers,
Jeremy Bicha

Bug#866659: zekr: depends on libwebkitgtk-3.0-0 which is deprecated

[Jeremy Bicha]

Source: zekr
Severity: serious
Tags: sid buster
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs libwebkitgtk-3.0-0 webkit1

Hi,

zekr depends on libwebkitgtk-3.0-0, which is deprecated in
favor of libwebkit2gtk-4.0-37 (provided in Debian by webkit2gtk).
zekr should be ported to the new webkitgtk version so we
can remove the old, unmaintained one.

Please try to do soon as we're going to try to remove the old webkitgtk soon.

I am filing this bug as "serious" since the old webkitgtk will not be
available in the next major stable release of Debian (codenamed
"buster").

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

On behalf of the Debian WebKit Maintainers,
Jeremy Bicha

Bug#866658: xombrero: depends on libwebkitgtk-3.0-0 which is deprecated

[Jeremy Bicha]

Source: xombrero
Severity: serious
Tags: sid buster
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs libwebkitgtk-3.0-0 webkit1

Hi,

xombrero depends on libwebkitgtk-3.0-0, which is deprecated in
favor of libwebkit2gtk-4.0-37 (provided in Debian by webkit2gtk).
xombrero should be ported to the new webkitgtk version so we
can remove the old, unmaintained one.

Please try to do soon as we're going to try to remove the old webkitgtk soon.

I am filing this bug as "serious" since the old webkitgtk will not be
available in the next major stable release of Debian (codenamed
"buster").

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

On behalf of the Debian WebKit Maintainers,
Jeremy Bicha

Bug#866654: typecatcher: depends on libwebkitgtk-3.0-0 which is deprecated

[Jeremy Bicha]

Source: typecatcher
Severity: serious
Tags: sid buster
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs libwebkitgtk-3.0-0 webkit1

Hi,

typecatcher depends on gir1.2-webkit-3.0, which is deprecated
in favor of gir1.2-webkit2-4.0 (provided in Debian by webkit2gtk). It
should be ported to the new webkitgtk version so we
can remove the old, unmaintained one.

Please try to do soon as we're going to try to remove the old webkitgtk soon.

I am filing this bug as "serious" since the old webkitgtk will not be
available in the next major stable release of Debian (codenamed
"buster").

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

On behalf of the Debian WebKit Maintainers,
Jeremy Bicha

Bug#866653: thawab: depends on gir1.2-webkit-3.0 which is deprecated

[Jeremy Bicha]

Package: thawab
Severity: serious
Tags: sid buster
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs libwebkitgtk-3.0-0 webkit1
Forwarded: https://github.com/ojuba-org/thawab/issues/14

Hi,

thawab depends on gir1.2-webkit-3.0, which is deprecated in
favor of gir1.2-webkit2-4.0 (provided in Debian by webkit2gtk). It
should be ported to the new webkitgtk version so we
can remove the old, unmaintained one.

Please try to do soon as we're going to try to remove the old webkitgtk soon.

I am filing this bug as "serious" since the old webkitgtk will not be
available in the next major stable release of Debian (codenamed
"buster").

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

On behalf of the Debian WebKit Maintainers,
Jeremy Bicha

Bug#866649: sugar-read-activity: depends on libwebkitgtk-3.0-0 which is deprecated

[Jeremy Bicha]

Source: sugar-read-activity
Severity: serious
Tags: sid buster
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs libwebkitgtk-3.0-0 webkit1

Hi,

sugar-read-activity depends on gir1.2-webkit-3.0, which is deprecated
in favor of gir1.2-webkit2-4.0 (provided in Debian by webkit2gtk). It
should be ported to the new webkitgtk version so we
can remove the old, unmaintained one.

Please try to do soon as we're going to try to remove the old webkitgtk soon.

I am filing this bug as "serious" since the old webkitgtk will not be
available in the next major stable release of Debian (codenamed
"buster").

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

On behalf of the Debian WebKit Maintainers,
Jeremy Bicha

Bug#863801: grub-coreboot: fails to upgrade from jessie to stretch if init-select was installed

[Andreas Beckmann]

Hi,

I've now filed a jessie-pu request (#866643) for init-select, with 

  ... $(if [ -x /usr/lib/init-select/get-init ]; then 
/usr/lib/init-select/get-init; fi)

Given that init-select has now been removed from sid, you don't
have to care too much about messing around with init-select.cfg,
you could even take it over by shipping a dummy one (in grub-common?,
together with unversioned Breaks+Replaces: init-select)
for stretch+buster, and finally remove it for buster+1.

(Theoretically you should also be able to
'dpkg-maintscript-helper rm_conffile' a conffile owned by another
package, but with init-select being removed instead of upgraded that
would likely not make dpkg forget that init-select owns that file
and a future reintroduction of init-select could make dpkg honor the 
"local deletion" of the conffile. Taking it back from grub-common
should work as intended.)

Andreas

Bug#866646: freebayes FTBFS with libhts-dev 1.4.1-2

[Adrian Bunk]

Source: freebayes
Version: 1.0.2-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/freebayes.html

...
g++ -O3 -D_FILE_OFFSET_BITS=64 -g -I/usr/include/bamtools -I../ttmath 
-I/usr/include/vcflib -I/usr/include/intervaltree `pkg-config --cflags 
libsmithwaterman` -ldisorder -c freebayes.cpp
In file included from /usr/include/htslib/tbx.h:30:0,
 from /usr/include/tabix.hpp:5,
 from /usr/include/vcflib/Variant.h:18,
 from AlleleParser.h:31,
 from freebayes.cpp:28:
/usr/include/htslib/hts.h:140:5: error: 'json' redeclared as different kind of 
symbol
 json,
 ^~~~
In file included from freebayes.cpp:26:0:
Allele.h:99:19: note: previous declaration 'std::__cxx11::string json(Allele*&)'
 friend string json(Allele* );
   ^~~~
Makefile:92: recipe for target 'freebayes.o' failed
make[2]: *** [freebayes.o] Error 1
make[2]: Leaving directory '/build/1st/freebayes-1.0.2/src'
Makefile:2: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/build/1st/freebayes-1.0.2'
dh_auto_build: make -j1 returned exit code 2
debian/rules:4: recipe for target 'build' failed
make: *** [build] Error 2

Bug#866647: ruby-webkit-gtk: depends on gir1.2-webkit-3.0 which is deprecated

[Jeremy Bicha]

Package: ruby-webkit-gtk
Severity: serious
Tags: sid buster
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs libwebkitgtk-3.0-0 webkit1

Hi,

ruby-webkit-gtk depends on gir1.2-webkit-3.0, which is deprecated in
favor of gir1.2-webkit2-4.0 (provided in Debian by webkit2gtk). It
should be ported to the new webkitgtk version so we
can remove the old, unmaintained one.

I suggest dropping ruby-webkit-gtk since it has no reverse
dependencies in Debian. Upstream offers ruby-webkit2-gtk which you
could optionally package.

Please try to do soon as we're going to try to remove the old webkitgtk soon.

I am filing this bug as "serious" since the old webkitgtk will not be
available in the next major stable release of Debian (codenamed
"buster").

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

On behalf of the Debian WebKit Maintainers,
Jeremy Bicha

Bug#866645: maildir-utils: depends on libwebkitgtk-3.0-0 which is deprecated

[Jeremy Bicha]

Source: maildir-utils
Severity: serious
Tags: sid buster
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs libwebkitgtk-3.0-0 webkit1

Hi,

maildir-utils depends on libwebkitgtk-3.0-0, which is deprecated in
favor of libwebkit2gtk-4.0-37 (provided in Debian by webkit2gtk).
maildir-utils should be ported to the new webkitgtk version so we
can remove the old, unmaintained one.

Please try to do soon as we're going to try to remove the old webkitgtk soon.

I am filing this bug as "serious" since the old webkitgtk will not be
available in the next major stable release of Debian (codenamed
"buster").

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

On behalf of the Debian WebKit Maintainers,
Jeremy Bicha

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 866620 debhelper
Bug #866620 [python3-cairo] Error when installing together with debconf, 
overwriting files
Bug reassigned from package 'python3-cairo' to 'debhelper'.
No longer marked as found in versions py3cairo/1.10.0+dfsg-5.
Ignoring request to alter fixed versions of bug #866620 to the same values 
previously set
> forcemerge 866570 866620
Bug #866570 {Done: Niels Thykier } [debhelper] debhelper: 
dh_install takes filenames as absolute if debian/package.install starts with a 
slash
Bug #866572 {Done: Niels Thykier } [debhelper] libfiu-dev 
file conflicts with many packages
Bug #866592 {Done: Niels Thykier } [debhelper] 
python3-cairo: Unable to upgrade python3-cairo
Bug #866598 {Done: Niels Thykier } [debhelper] 
1.10.0+dfsg-5+b2 uninstallable: conflicts with debconf
Bug #866602 {Done: Niels Thykier } [debhelper] Trying to 
overwrite '/usr/lib/python2.7/dist-packages/debconf.py', which is also in 
package debconf 1.5.61
Bug #866620 [debhelper] Error when installing together with debconf, 
overwriting files
Severity set to 'grave' from 'serious'
Marked Bug as done
Added indication that 866620 affects python3-cairo
Marked as fixed in versions debhelper/10.6.1.
Marked as found in versions debhelper/10.6.
Bug #866572 {Done: Niels Thykier } [debhelper] libfiu-dev 
file conflicts with many packages
Bug #866592 {Done: Niels Thykier } [debhelper] 
python3-cairo: Unable to upgrade python3-cairo
Bug #866598 {Done: Niels Thykier } [debhelper] 
1.10.0+dfsg-5+b2 uninstallable: conflicts with debconf
Bug #866602 {Done: Niels Thykier } [debhelper] Trying to 
overwrite '/usr/lib/python2.7/dist-packages/debconf.py', which is also in 
package debconf 1.5.61
Merged 866570 866572 866592 866598 866602 866620
> thanks
Stopping processing here.

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

Bug#866641: guitarix: depends on libwebkitgtk-1.0-0 which is deprecated

[Jeremy Bicha]

Package: guitarix
Severity: serious
Tags: sid buster
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs libwebkitgtk-1.0-0 webkit1

Hi,

guitarix depends on libwebkitgtk-1.0-0, which is deprecated in
favor of libwebkit2gtk-4.0-37 (provided in Debian by webkit2gtk).
guitarix should be ported to the new webkitgtk version so we can
remove the old, unmaintained one.

Please try to do soon as we're going to try to remove the old webkitgtk soon.

I am filing this bug as "serious" since the old webkitgtk will not be
available in the next major stable release of Debian (codenamed
"buster").

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

On behalf of the Debian WebKit Maintainers,
Jeremy Bicha

Bug#866640: gtkpod: depends on libwebkitgtk-3.0-0 which is deprecated

[Jeremy Bicha]

Source: gtkpod
Severity: serious
Tags: sid buster
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs libwebkitgtk-3.0-0 webkit1

Hi,

gtkpod depends on libwebkitgtk-3.0-0, which is deprecated in
favor of libwebkit2gtk-4.0-37 (provided in Debian by webkit2gtk).
gtkpod should be ported to the new webkitgtk version so we
can remove the old, unmaintained one.

Please try to do soon as we're going to try to remove the old webkitgtk soon.

I am filing this bug as "serious" since the old webkitgtk will not be
available in the next major stable release of Debian (codenamed
"buster").

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

On behalf of the Debian WebKit Maintainers,
Jeremy Bicha

Bug#866639: gnome-web-photo: depends on libwebkitgtk-3.0-0 which is deprecated

[Jeremy Bicha]

Source: gnome-web-photo
Severity: serious
Tags: sid buster
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs libwebkitgtk-3.0-0 webkit1

Hi,

gnome-web-photo depends on libwebkitgtk-3.0-0, which is deprecated in
favor of libwebkit2gtk-4.0-37 (provided in Debian by webkit2gtk).
gnome-web-photo should be ported to the new webkitgtk version so we
can remove the old, unmaintained one.

Please try to do soon as we're going to try to remove the old webkitgtk soon.

I am filing this bug as "serious" since the old webkitgtk will not be
available in the next major stable release of Debian (codenamed
"buster").

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

On behalf of the Debian WebKit Maintainers,
Jeremy Bicha

Bug#866638: geary: depends on libwebkitgtk-3.0-0 which is deprecated

[Jeremy Bicha]

Source: geary
Severity: serious
Tags: sid buster
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs libwebkitgtk-3.0-0 webkit1

Hi,

geary depends on libwebkitgtk-3.0-0, which is deprecated in favor of
libwebkit2gtk-4.0-37 (provided in Debian by webkit2gtk). geary
should be ported to the new webkitgtk version so
we can remove the old, unmaintained one.

Please try to do soon as we're going to try to remove the old webkitgtk soon.

I am filing this bug as "serious" since the old webkitgtk will not be
available in the next major stable release of Debian (codenamed
"buster").

In Ubuntu, I packaged a git snapshot of geary which has been ported to
webkit2gtk.

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

On behalf of the Debian WebKit Maintainers,
Jeremy Bicha

Bug#866637: empathy: depends on libwebkitgtk-3.0-0 which is deprecated

[Jeremy Bicha]

Source: empathy
Severity: serious
Tags: sid buster
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs libwebkitgtk-3.0-0 webkit1

Hi,

empathy depends on libwebkitgtk-3.0-0, which is deprecated in favor of
libwebkit2gtk-4.0-37 (provided in Debian by webkit2gtk). empathy
should be ported to the new webkitgtk version so
we can remove the old, unmaintained one.

Please try to do soon as we're going to try to remove the old webkitgtk soon.

I am filing this bug as "serious" since the old webkitgtk will not be
available in the next major stable release of Debian (codenamed
"buster").

I spoke briefly with Michael Catanzaro today. He said that empathy has
been ported to webkit2gtk in git upstream but it's "a bit buggy".

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

On behalf of the Debian WebKit Maintainers,
Jeremy Bicha

Bug#866635: cyclograph: depends on libwebkitgtk-3.0-0 which is deprecated

[Jeremy Bicha]

Source: cyclograph
Severity: serious
Tags: sid buster
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs libwebkitgtk-3.0-0 webkit1

Hi,

cyclograph depends on libwebkitgtk-3.0-0, which is deprecated
in favor of libwebkit2gtk-4.0-37 (provided in Debian by webkit2gtk).
cyclograph should be ported to the new webkitgtk version so
we can remove the old, unmaintained one.

Please try to do soon as we're going to try to remove the old webkitgtk soon.

I am filing this bug as "serious" since the old webkitgtk will not be
available in the next major stable release of Debian (codenamed
"buster").

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

On behalf of the Debian WebKit Maintainers,
Jeremy Bicha

Bug#866634: cairo-dock-plug-ins: depends on libwebkitgtk-3.0-0 which is deprecated

[Jeremy Bicha]

Source: cairo-dock-plug-ins
Severity: serious
Tags: sid buster
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs libwebkitgtk-3.0-0 webkit1

Hi,

cairo-dock-plug-ins depends on libwebkitgtk-3.0-0, which is deprecated
in favor of
libwebkit2gtk-4.0-37 (provided in Debian by webkit2gtk).
cairo-dock-plug-ins should be ported to the new webkitgtk version so
we can remove the old, unmaintained one.

Please try to do soon as we're going to try to remove the old webkitgtk soon.

I am filing this bug as "serious" since the old webkitgtk will not be
available in the next major stable release of Debian (codenamed
"buster").

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

On behalf of the Debian WebKit Maintainers,
Jeremy Bicha

Bug#866633: bijiben: depends on libwebkitgtk-3.0-0 which is deprecated

[Jeremy Bicha]

Package: bijiben
Severity: serious
Tags: sid buster
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs libwebkitgtk-3.0-0 webkit1

Hi,

bijiben depends on libwebkitgtk-3.0-0, which is deprecated in favor of
libwebkit2gtk-4.0-37 (provided in Debian by webkit2gtk). bijiben
should be ported to the new webkitgtk version so we can remove the
old, unmaintained one.

Please try to do soon as we're going to try to remove the old webkitgtk soon.

I am filing this bug as "serious" since the old webkitgtk will not be
available in the next major stable release of Debian (codenamed
"buster").

More specifically, bijiben 3.24.0 has been ported to webkit2gtk and
has been packaged in Ubuntu 17.10 Alpha.

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

On behalf of the Debian WebKit Maintainers,
Jeremy Bicha

Processed: Re: balsa: depends on libwebkitgtk-1.0-0 which is deprecated

[Debian Bug Tracking System]

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

> reassign 866630 balsa
Bug #866630 [apvlv] balsa: depends on libwebkitgtk-1.0-0 which is deprecated
Bug reassigned from package 'apvlv' to 'balsa'.
Ignoring request to alter found versions of bug #866630 to the same values 
previously set
Ignoring request to alter fixed versions of bug #866630 to the same values 
previously set
>
End of message, stopping processing here.

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

Bug#866632: bibledit-gtk: depends on libwebkitgtk-1.0-0 which is deprecated

[Jeremy Bicha]

Package: bibledit-gtk
Severity: serious
Tags: sid buster
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs libwebkitgtk-1.0-0 webkit1

Hi,

bibledit-gtk depends on libwebkitgtk-1.0-0, which is deprecated in
favor of libwebkit2gtk-4.0-37 (provided in Debian by webkit2gtk).
bibledit-gtk should be ported to the new webkitgtk version so we can
remove the old, unmaintained one.

Please try to do soon as we're going to try to remove the old webkitgtk soon.

I am filing this bug as "serious" since the old webkitgtk will not be
available in the next major stable release of Debian (codenamed
"buster").

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

On behalf of the Debian WebKit Maintainers,
Jeremy Bicha

Bug#866573: marked as done (libfiu-dev file conflicts with many packages)

[Debian Bug Tracking System]

Your message dated Fri, 30 Jun 2017 18:14:56 +0300
with message-id <20170630151456.hb4xycjmn7upifoo@localhost>
and subject line binNMU with fixed debhelper has been done
has caused the Debian Bug report #866573,
regarding libfiu-dev file conflicts with many packages
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.)


-- 
866573: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866573
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libfiu-dev
Version: libfiu-dev/0.95-3+b1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2017-06-30
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships have
detected that libfiu-dev does produce file overwrite errors when installing
together with other packages. Here is what happends when trying to install
it with make:

Selecting previously unselected package libfiu0.
(Reading database ... 11003 files and directories currently installed.)
Preparing to unpack .../libfiu0_0.95-3+b1_amd64.deb ...
Unpacking libfiu0 (0.95-3+b1) ...
Selecting previously unselected package libfiu-dev.
Preparing to unpack .../libfiu-dev_0.95-3+b1_amd64.deb ...
Unpacking libfiu-dev (0.95-3+b1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libfiu-dev_0.95-3+b1_amd64.deb (--unpack):
 trying to overwrite '/usr/share/man/man3/history.3readline.gz', which is also 
in package readline-common 7.0-3
Selecting previously unselected package make.
Preparing to unpack .../make_4.1-9.1_amd64.deb ...
Unpacking make (4.1-9.1) ...
Processing triggers for libc-bin (2.24-12) ...
Processing triggers for man-db (2.7.6.1-2) ...
Errors were encountered while processing:
 /var/cache/apt/archives/libfiu-dev_0.95-3+b1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. A list of all packages with which
libfiu-dev clashes will follow.

-Ralf
--- End Message ---
--- Begin Message ---
Thanks for your report.

libfiu has been rebuilt with a fixed debhelper, closing.

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#866627: libwebp-dev: depends on libwebpdemux3, but src builds libwebpdemux2

[Andreas Beckmann]

Package: libwebp-dev
Version: 0.6.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is not
installable in experimental:

The following packages have unmet dependencies:
 libwebp-dev : Depends: libwebpdemux3 (= 0.6.0-1) but it is not installable


Cheers,

Andreas

Bug#866630: balsa: depends on libwebkitgtk-1.0-0 which is deprecated

[Jeremy Bicha]

Package: apvlv
Severity: serious
Tags: sid buster
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs libwebkitgtk-1.0-0 webkit1

Hi,

balsa depends on libwebkitgtk-1.0-0, which is deprecated in favor of
libwebkit2gtk-4.0-37 (provided in Debian by webkit2gtk). balsa should
be ported to the new webkitgtk version so we can remove the old,
unmaintained one.

Please try to do soon as we're going to try to remove the old webkitgtk soon.

I am filing this bug as "serious" since the old webkitgtk will not be
available in the next major stable release of Debian (codenamed
"buster").

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

On behalf of the Debian WebKit Maintainers,
Jeremy Bicha

Bug#866628: apvlv: depends on libwebkitgtk-3.0-0 which is deprecated

[Jeremy Bicha]

Package: apvlv
Severity: serious
Tags: sid buster
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs libwebkitgtk-3.0-0 webkit1

Hi,

apvlv depends on libwebkitgtk-3.0-0, which is deprecated in favor of
libwebkit2gtk-4.0-37 (provided in Debian by webkit2gtk). apvlv should
be ported to the new webkitgtk version so we can remove the old,
unmaintained one.

Please try to do soon as we're going to try to remove the old webkitgtk soon.

I am filing this bug as "serious" since the old webkitgtk will not be
available in the next major stable release of Debian (codenamed
"buster").

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

On behalf of the Debian WebKit Maintainers,
Jeremy Bicha

Bug#866553: marked as done (python-cryptography FTBFS with python 3.6)

[Debian Bug Tracking System]

Your message dated Fri, 30 Jun 2017 18:08:05 +0300
with message-id <20170630150804.puvws5obpichl6ty@localhost>
and subject line Re: Bug#866553: python-cryptography FTBFS with python 3.6
has caused the Debian Bug report #866553,
regarding python-cryptography FTBFS with python 3.6
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.)


-- 
866553: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866553
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-cryptography
Version: 1.9-1
Severity: serious

https://buildd.debian.org/status/package.php?p=python-cryptography=sid

...
I: pybuild base:184: python3.6 setup.py config 
Traceback (most recent call last):
  File "setup.py", line 321, in 
**keywords_with_side_effects(sys.argv)
  File "/usr/lib/python3.6/distutils/core.py", line 108, in setup
_setup_distribution = dist = klass(attrs)
  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 323, in 
__init__
_Distribution.__init__(self, attrs)
  File "/usr/lib/python3.6/distutils/dist.py", line 281, in __init__
self.finalize_options()
  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 392, in 
finalize_options
ep.load()(self, ep.name, value)
  File "/usr/lib/python3/dist-packages/cffi/setuptools_ext.py", line 188, in 
cffi_modules
add_cffi_module(dist, cffi_module)
  File "/usr/lib/python3/dist-packages/cffi/setuptools_ext.py", line 49, in 
add_cffi_module
execfile(build_file_name, mod_vars)
  File "/usr/lib/python3/dist-packages/cffi/setuptools_ext.py", line 25, in 
execfile
exec(code, glob, glob)
  File "src/_cffi_src/build_openssl.py", line 82, in 
extra_link_args=extra_link_args(compiler_type()),
  File "src/_cffi_src/utils.py", line 61, in build_ffi_for_binding
extra_link_args=extra_link_args,
  File "src/_cffi_src/utils.py", line 69, in build_ffi
ffi = FFI()
  File "/usr/lib/python3/dist-packages/cffi/api.py", line 56, in __init__
import _cffi_backend as backend
ModuleNotFoundError: No module named '_cffi_backend'
E: pybuild pybuild:283: configure: plugin distutils failed with: exit code=1: 
python3.6 setup.py config 
dh_auto_configure: pybuild --configure -i python{version} -p 3.6 3.5 returned 
exit code 13
debian/rules:18: recipe for target 'build-arch' failed
make: *** [build-arch] Error 25
--- End Message ---
--- Begin Message ---
On Fri, Jun 30, 2017 at 04:51:10AM +, Tristan Seligmann wrote:
> On Fri, 30 Jun 2017 at 04:45 Adrian Bunk  wrote:
> 
> >   File "/usr/lib/python3/dist-packages/cffi/api.py", line 56, in __init__
> > import _cffi_backend as backend
> > ModuleNotFoundError: No module named '_cffi_backend'
> >
> 
> The cause of this error is that Python 3.6 was just added to supported, but
> python-cffi has not yet been rebuilt for Python 3.6, and thus
> python3-cffi-backend does not contain a Python 3.6 module.
> python-cryptography was stuck in BD-Uninstallable until now due to
> asn1crypto being in NEW, so I guess this is a case of unfortunate timing.

Thanks for the explanation.

> Should this bug be reassigned to python-cffi?

python-cffi has been binNMU'ed and the failed python-cryptography builds 
given back, closing this bug.

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#790208: marked as done (haskell-webkit: depends on libwebkitgtk-1.0-0 which is deprecated)

[Debian Bug Tracking System]

Your message dated Fri, 30 Jun 2017 17:42:34 +0300
with message-id <20170630144234.zepwutubu7v4qoru@localhost>
and subject line haskell-webkit has been removed from unstable
has caused the Debian Bug report #790208,
regarding haskell-webkit: depends on libwebkitgtk-1.0-0 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.)


-- 
790208: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790208
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-webkit
Severity: important
Tags: sid stretch
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs libwebkitgtk-1.0-0 webkit1

Hi,

haskell-webkit depends on libwebkitgtk-1.0-0, which is deprecated in
favor of libwebkit2gtk-4.0-37. haskell-webkit should be ported to the
new webkitgtk version so we can remove the old, unmaintained one.

As an intermediate step you can port haskell-webkit to
libwebkitgtk-3.0-0, which has a similar API to libwebkitgtk-1.0-0 but
is based on GTK+ 3.0. Thus you'd be porting haskell-webkit to GTK+
3.0 first, using libwebkitgtk-3.0-0, and you could then port to
libwebkit2gtk-4.0-37 later. But note that libwebkitgtk-3.0-0 is also
deprecated.

Please try to do this before the Stretch release as we're going to
try to remove libwebkitgtk-1.0-0 this cycle.

We'll bump this to serious when the list of rdeps is small and we're
getting ready to removing libwebkitgtk-1.0-0 completely.

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

Emilio 
--- End Message ---
--- Begin Message ---
haskell-webkit has been removed from unstable:
  https://bugs.debian.org/792614

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#790207: Upstream luakit based on webkit2gtk

[Florian Bruhin]

Note that upstream recently merged a fork with a major update based on
webkit2: https://luakit.github.io/luakit/

-- 
https://www.qutebrowser.org  | m...@the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072  | https://the-compiler.org/pubkey.asc
 I love long mails!  | https://email.is-not-s.ms/

Bug#866620: Error when installing together with debconf, overwriting files

[Andreas Moog]

Package: python3-cairo
Version: 1.10.0+dfsg-5+b2
Severity: serious

Hello there,

I get the following error when trying to install python3-cairo:

(sid-amd64)root@inkubator:~# apt install python3-cairo debconf
[...]
Unpacking python3-cairo (1.10.0+dfsg-5+b2) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-BrlSR6/32-python3-cairo_1.10.0+dfsg-5+b2_amd64.deb 
(--unpack):
 trying to overwrite '/usr/lib/python2.7/dist-packages/debconf.py', which is 
also in package debconf 1.5.61
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

If you need any more information, feel free to ask.

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

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

Versions of packages python3-cairo depends on:
ii  libc6  2.24-12
ii  libcairo2  1.14.8-1
ii  python33.5.3-3

python3-cairo recommends no packages.

python3-cairo suggests no packages.

-- no debconf information

Processed: Raising severity to serious for packages depending on webkitgtk

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #864938 [cinnamon-screensaver-webkit-plugin] 
cinnamon-screensaver-webkit-plugin: Drop alt dep on gir1.2-webkit2-3.0
Severity set to 'serious' from 'important'
> tags -1 +sid
Bug #864938 [cinnamon-screensaver-webkit-plugin] 
cinnamon-screensaver-webkit-plugin: Drop alt dep on gir1.2-webkit2-3.0
Added tag(s) sid.

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

Processed: Raising severity to serious for packages depending on webkitgtk

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #864937 [cinnamon] cinnamon: Don't depend on gir1.2-javascriptcoregtk-3.0
Severity set to 'serious' from 'important'
> tags -1 +sid
Bug #864937 [cinnamon] cinnamon: Don't depend on gir1.2-javascriptcoregtk-3.0
Added tag(s) sid.

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

Processed: Raising severity to serious for packages depending on webkitgtk

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #790219 [src:webkit-image] webkit-image: depends on libwebkitgtk-1.0-0 
which is deprecated
Severity set to 'serious' from 'important'
> tags -1 -stretch
Bug #790219 [src:webkit-image] webkit-image: depends on libwebkitgtk-1.0-0 
which is deprecated
Removed tag(s) stretch.

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

Processed: Raising severity to serious for packages depending on webkitgtk

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #790204 [src:gnucash] gnucash: depends on libwebkitgtk-1.0-0 which is 
deprecated
Severity set to 'serious' from 'important'
> tags -1 -stretch
Bug #790204 [src:gnucash] gnucash: depends on libwebkitgtk-1.0-0 which is 
deprecated
Removed tag(s) stretch.

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

Processed: Raising severity to serious for packages depending on webkitgtk

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #790222 [src:wxwidgets3.0] wxwidgets3.0: depends on libwebkitgtk-1.0-0 
which is deprecated
Severity set to 'serious' from 'important'
> tags -1 -stretch
Bug #790222 [src:wxwidgets3.0] wxwidgets3.0: depends on libwebkitgtk-1.0-0 
which is deprecated
Removed tag(s) stretch.

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

Processed: Raising severity to serious for packages depending on webkitgtk

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #790221 [src:xtrkcad] xtrkcad: depends on libwebkitgtk-1.0-0 which is 
deprecated
Severity set to 'serious' from 'important'
> tags -1 -stretch
Bug #790221 [src:xtrkcad] xtrkcad: depends on libwebkitgtk-1.0-0 which is 
deprecated
Removed tag(s) stretch.

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

Processed: Raising severity to serious for packages depending on webkitgtk

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #790220 [src:webkit2pdf] webkit2pdf: depends on libwebkitgtk-1.0-0 which is 
deprecated
Severity set to 'serious' from 'important'
> tags -1 -stretch
Bug #790220 [src:webkit2pdf] webkit2pdf: depends on libwebkitgtk-1.0-0 which is 
deprecated
Removed tag(s) stretch.

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

Processed: Raising severity to serious for packages depending on webkitgtk

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #790199 [src:claws-mail] claws-mail: depends on libwebkitgtk-1.0-0 which is 
deprecated
Severity set to 'serious' from 'important'
> tags -1 -stretch
Bug #790199 [src:claws-mail] claws-mail: depends on libwebkitgtk-1.0-0 which is 
deprecated
Removed tag(s) stretch.

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

Processed: Raising severity to serious for packages depending on webkitgtk

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #790207 [src:luakit] luakit: depends on libwebkitgtk-1.0-0 which is 
deprecated
Severity set to 'serious' from 'important'
> tags -1 -stretch
Bug #790207 [src:luakit] luakit: depends on libwebkitgtk-1.0-0 which is 
deprecated
Removed tag(s) stretch.

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

Processed: Raising severity to serious for packages depending on webkitgtk

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #790217 [src:webkit-sharp] webkit-sharp: depends on libwebkitgtk-1.0-0 
which is deprecated
Severity set to 'serious' from 'important'
> tags -1 -stretch
Bug #790217 [src:webkit-sharp] webkit-sharp: depends on libwebkitgtk-1.0-0 
which is deprecated
Removed tag(s) stretch.

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