Bug#914172: [debian-mysql] Bug#914172: mariadb-server-10.1: mariadb-server sec-update (10.1.37-0+deb9u1) uninstalls default-mysql-server, mysql-server, mariadb-server-10.1 & mariadb-client-10.1

2018-11-19 Thread Olaf van der Spek
On Tue, Nov 20, 2018 at 8:45 AM Jeremy Davis  wrote:
> As of the (automated) installation of today's MariaDB server security update 
> (10.1.37-0+deb9u1)
> all of our user's LAMP based appliances uninstalled mariadb-server (i.e. 
> default-mysql-server,
> mysql-server, mariadb-server-10.1 & mariadb-client-10.1) and thus most of web 
> based software
> stopped functioning.

Ouch. IMO apt shouldn't be run in such a way that packages get removed
automatically though..

> We're still not sure exactly what caused this, but would like to note the 
> issue.

Updated dependencies perhaps, in particular:

> * Add libconfig-inifiles-perl to mariadb-client-10.1 depends to fix mytop

Note this is just a guess.

Gr,

Olaf



Bug#913952: marked as done (python-xarray: empty package when only python3 version is python3.7)

2018-11-19 Thread Debian Bug Tracking System
Your message dated Tue, 20 Nov 2018 07:49:45 +
with message-id 
and subject line Bug#913952: fixed in python-xarray 0.11.0-3
has caused the Debian Bug report #913952,
regarding python-xarray: empty package when only python3 version is python3.7
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.)


-- 
913952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913952
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-xarray
Version: 0.11.0-1
Severity: serious
Tags: patch

python-xarray 0.11.0-1 made this surprising addition in its
dh_auto_install override:
rm -rf debian/python3-xarray/usr/lib/python3.7

This results in a basically empty package on Ubuntu 19.04 Alpha where
python3.7 is the only supported python3 version.

I am filing this as serious since python3.7 will soon be the only
supported python3 version in Debian Unstable.

In my next email, I am attaching a patch that might fix this issue. At
least the build completes successfully in both Debian Unstable and
Ubuntu 19.04 but I didn't try running it or running any tests.

Build log

https://launchpad.net/ubuntu/+source/python-xarray/0.11.0-2/+build/15670729

This bug was detected by the 0.11.0-2 autopkgtest on Ubuntu:
https://autopkgtest.ubuntu.com/packages/p/python-xarray/disco/amd64

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: python-xarray
Source-Version: 0.11.0-3

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated python-xarray 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 20 Nov 2018 05:16:34 +
Source: python-xarray
Binary: python-xarray python3-xarray python-xarray-doc
Architecture: source all
Version: 0.11.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Alastair McKinstry 
Description:
 python-xarray - N-D labeled arrays and datasets in Python 2
 python-xarray-doc - documentation for xarray
 python3-xarray - N-D labeled arrays and datasets in Python 3
Closes: 913952
Changes:
 python-xarray (0.11.0-3) unstable; urgency=medium
 .
   * Fix from Jeremy Bicha for FTBFS with python3.7. Closes: #913952
Checksums-Sha1:
 7bc2bc77fb8b89003b5d715c746a0f9e90ebd0d0 3587 python-xarray_0.11.0-3.dsc
 fff3894ce19958f1dbf4c783378efc4ac218102b 10128 
python-xarray_0.11.0-3.debian.tar.xz
 58316315e6deed1d57af016fed9dd24e736a5587 2097936 
python-xarray-doc_0.11.0-3_all.deb
 b20444ffd802e7f77a35548a09890dfef7eac2b9 329984 python-xarray_0.11.0-3_all.deb
 b2804a5ceba85feef0d72bcf90c8c58e661ba1ea 14840 
python-xarray_0.11.0-3_amd64.buildinfo
 9c7d9382f3990a8464625f65bd25d567365b20bf 330152 python3-xarray_0.11.0-3_all.deb
Checksums-Sha256:
 d9bc50655f4e3eecac637230e7d0d0ccc6c96125813e242bc05a0bfe8c9300bf 3587 
python-xarray_0.11.0-3.dsc
 e1cf0cc33cabe039fce6b2ac4ca49fab941a56ba78b37ecee0d46ae2673fee2b 10128 
python-xarray_0.11.0-3.debian.tar.xz
 159bbd02e9892ba198b046f4241356047f53d5d0d7497c91ebeb4267f3556855 2097936 
python-xarray-doc_0.11.0-3_all.deb
 c555cac723a635dc75dcc8d74422c8644ba742da20b1fa6999d8a5028a8f8ef7 329984 
python-xarray_0.11.0-3_all.deb
 c74ae3360591664a48ba928c062f58846ffe2e0b609c137e2172b9e336802c69 14840 
python-xarray_0.11.0-3_amd64.buildinfo
 f17b87d04581767b181cf632d45b732f3326c80955aec1eb1d0d3fabbb5b5a8c 330152 
python3-xarray_0.11.0-3_all.deb
Files:
 a75819e4093233fb50965b8a2e93996a 3587 python optional 
python-xarray_0.11.0-3.dsc
 506956de8a21f4032d49c1c6948dcfeb 10128 python optional 
python-xarray_0.11.0-3.debian.tar.xz
 1a54d2005914da161fba2bd8aa0356b9 2097936 doc optional 
python-xarray-doc_0.11.0-3_all.deb
 fc1dca777920151e75b5cd47abcac284 329984 python optional 
python-xarray_0.11.0-3_all.deb
 3eaf576aae566eb01c00fb16288af976 14840 python optional 
python-xarray_0.11.0-3_amd64.buildinfo
 b5a2cde09d64495460e4e322c599a58b 330152 python optional 
python3-xarray_0.11.0-3_all.deb

-BEGIN PGP SIGNATURE-


Bug#914173: surefire FTBFS

2018-11-19 Thread Adrian Bunk
Source: surefire
Version: 2.22.1-1
Severity: serious
Tags: ftbfs

Some recent change in unstable makes surefire FTBFS:

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

...
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time:  34.876 s
[INFO] Finished at: 2018-11-19T10:35:39-12:00
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-dependency-plugin:3.1.1:copy (main) on project 
surefire-junit47: Error copying artifact from 
/build/1st/surefire-2.22.1/debian/maven-repo/junit/junit/4.x/junit-4.x.jar to 
/build/1st/surefire-2.22.1/surefire-providers/surefire-junit47/target/endorsed/junit-4.x.jar:
 Failed to copy full contents from 
/build/1st/surefire-2.22.1/debian/maven-repo/junit/junit/4.x/junit-4.x.jar to 
/build/1st/surefire-2.22.1/surefire-providers/surefire-junit47/target/endorsed/junit-4.x.jar
 -> [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/MojoExecutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :surefire-junit47
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/surefire-2.22.1 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/1st/surefire-2.22.1/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/build/1st/surefire-2.22.1/debian 
-Dmaven.repo.local=/build/1st/surefire-2.22.1/debian/maven-repo --batch-mode 
package -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1
make: *** [debian/rules:4: build] Error 2



Bug#914167: fatal error: KHR/khrplatform.h: No such file or directory

2018-11-19 Thread Mathieu Malaterre
On Tue, Nov 20, 2018 at 8:31 AM Mathieu Malaterre  wrote:
>
> On Tue, Nov 20, 2018 at 8:19 AM Timo Aaltonen  wrote:
> >
> > On 20.11.2018 9.04, Mathieu Malaterre wrote:
> > > Package: mesa-common-dev
> > > Version: 18.2.5-1
> > > Severity: serious
> > > Tags: ftbfs
> > >
> > > OpenVDB fails to build from source because of:
> > >
> > > In file included from /usr/include/GL/gl.h:2055,
> > >  from viewer/Font.h:40,
> > >  from viewer/Font.cc:31:
> > > /usr/include/GL/glext.h:467:10: fatal error: KHR/khrplatform.h: No
> > > such file or directory
> > >  #include 
> > >   ^~~
> > > compilation terminated.
> > >
> > > ref:
> > > https://buildd.debian.org/status/fetch.php?pkg=openvdb=amd64=5.2.0-5=154226=0
> > >
> > > It would be nice to fix this, upstream seems to have provided a patch:
> > >
> > > https://bugs.freedesktop.org/show_bug.cgi?id=107511
> >
> > That commit is in 18.2.5:
> >
> > commit 2645ea5817f4fd05905b8deda96c268cd69fa48c
> > Author: Eric Engestrom 
> > Date:   Tue Aug 7 12:56:25 2018 +0100
> >
> > configure: install KHR/khrplatform.h when needed
> >
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107511
> > Fixes: f7d42ee7d319256608ad "include: update GL & GLES headers (v2)"
> > Signed-off-by: Eric Engestrom 
> > Tested-by: Brad King 
> > Reviewed-by: Emil Velikov 
> > (cherry picked from commit 87c156183cd668f1341326cc7c88ab6686f27d8f)
> >
> > so something else is wrong.
>
> I must admit I was hoping for some help here. Here is what I see on my side:
>
> $ head -n 467 /usr/include/GL/glext.h  | tail -1
> #include 
>
> So this is a bit mysterious what is happening on all the buildds...

As a side note, the experimental build of OpenVDB (same orig tarball
as the one in sid) went find using the previous version of mesa:

https://buildd.debian.org/status/fetch.php?pkg=openvdb=amd64=5.2.0-4=1542634335=0

...
Get: 164 http://ftp.gr.debian.org/debian unstable/main amd64
mesa-common-dev amd64 18.1.9-1 [587 kB]
...



Bug#914172: mariadb-server-10.1: mariadb-server sec-update (10.1.37-0+deb9u1) uninstalls default-mysql-server, mysql-server, mariadb-server-10.1 & mariadb-client-10.1

2018-11-19 Thread Jeremy Davis
Package: mariadb-server-10.1
Version: unsure exactly - prior to today's security update
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Please excuse me setting the severity as grave. Under the circumstance it seems 
appropriate, but I'm
not 100% sure.

FYI TurnKey Linux is a Debian derivative which builds "software appliances" 
using mostly Debian packages,
many with upstream software pre-installed on top.

It has Debian (and TurnKey) security updates automatically installed daily via 
cron-apt.

As of the (automated) installation of today's MariaDB server security update 
(10.1.37-0+deb9u1)
all of our user's LAMP based appliances uninstalled mariadb-server (i.e. 
default-mysql-server,
mysql-server, mariadb-server-10.1 & mariadb-client-10.1) and thus most of web 
based software
stopped functioning.

The expected outcome was that the packages were simply updated to the latest 
security update and continued
functioning.

We're still not sure exactly what caused this, but would like to note the 
issue. Assitance in ensuring
that this sort of issue doesn't reoccur would also be welcomed.

It only appears to be an issue if security only updates are installed. A full 
upgrade does not cause the
same issue.

The resolution is to simply reinstall default-mysql-server (which depends on 
mariadb-server-10.1 &
mariadb-client-10.1 - mysql-server is an un-needed transitional package).

Please note that this report was created on a freshly launched WordPress 
appliance (based on LAMP)
with security updates installed on firstboot (and without the above menitoned 
fix applied).

Please ask if you need any further info.

Regards,
Jeremy

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

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

Versions of packages mariadb-server-10.1 depends on:
ii  adduser   3.115
ii  debconf [debconf-2.0] 1.5.61
ii  galera-3  25.3.19-2
ii  gawk  1:4.1.4+dfsg-1
ii  init-system-helpers   1.48
ii  iproute2  4.9.0-1+deb9u1
ii  libaio1   0.3.110-3
ii  libc6 2.24-11+deb9u3
ii  libdbi-perl   1.636-1+b1
ii  libpam0g  1.1.8-3.6
ii  libstdc++66.3.0-18+deb9u1
ii  libsystemd0   232-25+deb9u4
ii  lsb-base  9.20161125
ii  lsof  4.89+dfsg-0.1
pn  mariadb-client-10.1   
ii  mariadb-common10.1.37-0+deb9u1
ii  mariadb-server-core-10.1  10.1.37-0+deb9u1
ii  passwd1:4.4-4.1
ii  perl  5.24.1-3+deb9u4
ii  psmisc22.21-2.1+b2
ii  rsync 3.1.2-1+deb9u1
ii  socat 1.7.3.1-2+deb9u1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages mariadb-server-10.1 recommends:
pn  libhtml-template-perl  

Versions of packages mariadb-server-10.1 suggests:
ii  bsd-mailx [mailx]  8.1.2-0.20160123cvs-4
pn  mariadb-test   
pn  netcat-openbsd 
pn  tinyca 



Bug#914167: fatal error: KHR/khrplatform.h: No such file or directory

2018-11-19 Thread Mathieu Malaterre
On Tue, Nov 20, 2018 at 8:19 AM Timo Aaltonen  wrote:
>
> On 20.11.2018 9.04, Mathieu Malaterre wrote:
> > Package: mesa-common-dev
> > Version: 18.2.5-1
> > Severity: serious
> > Tags: ftbfs
> >
> > OpenVDB fails to build from source because of:
> >
> > In file included from /usr/include/GL/gl.h:2055,
> >  from viewer/Font.h:40,
> >  from viewer/Font.cc:31:
> > /usr/include/GL/glext.h:467:10: fatal error: KHR/khrplatform.h: No
> > such file or directory
> >  #include 
> >   ^~~
> > compilation terminated.
> >
> > ref:
> > https://buildd.debian.org/status/fetch.php?pkg=openvdb=amd64=5.2.0-5=154226=0
> >
> > It would be nice to fix this, upstream seems to have provided a patch:
> >
> > https://bugs.freedesktop.org/show_bug.cgi?id=107511
>
> That commit is in 18.2.5:
>
> commit 2645ea5817f4fd05905b8deda96c268cd69fa48c
> Author: Eric Engestrom 
> Date:   Tue Aug 7 12:56:25 2018 +0100
>
> configure: install KHR/khrplatform.h when needed
>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107511
> Fixes: f7d42ee7d319256608ad "include: update GL & GLES headers (v2)"
> Signed-off-by: Eric Engestrom 
> Tested-by: Brad King 
> Reviewed-by: Emil Velikov 
> (cherry picked from commit 87c156183cd668f1341326cc7c88ab6686f27d8f)
>
> so something else is wrong.

I must admit I was hoping for some help here. Here is what I see on my side:

$ head -n 467 /usr/include/GL/glext.h  | tail -1
#include 

So this is a bit mysterious what is happening on all the buildds...



Bug#914167: fatal error: KHR/khrplatform.h: No such file or directory

2018-11-19 Thread Timo Aaltonen
On 20.11.2018 9.04, Mathieu Malaterre wrote:
> Package: mesa-common-dev
> Version: 18.2.5-1
> Severity: serious
> Tags: ftbfs
> 
> OpenVDB fails to build from source because of:
> 
> In file included from /usr/include/GL/gl.h:2055,
>  from viewer/Font.h:40,
>  from viewer/Font.cc:31:
> /usr/include/GL/glext.h:467:10: fatal error: KHR/khrplatform.h: No
> such file or directory
>  #include 
>   ^~~
> compilation terminated.
> 
> ref:
> https://buildd.debian.org/status/fetch.php?pkg=openvdb=amd64=5.2.0-5=154226=0
> 
> It would be nice to fix this, upstream seems to have provided a patch:
> 
> https://bugs.freedesktop.org/show_bug.cgi?id=107511

That commit is in 18.2.5:

commit 2645ea5817f4fd05905b8deda96c268cd69fa48c
Author: Eric Engestrom 
Date:   Tue Aug 7 12:56:25 2018 +0100

configure: install KHR/khrplatform.h when needed

Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107511
Fixes: f7d42ee7d319256608ad "include: update GL & GLES headers (v2)"
Signed-off-by: Eric Engestrom 
Tested-by: Brad King 
Reviewed-by: Emil Velikov 
(cherry picked from commit 87c156183cd668f1341326cc7c88ab6686f27d8f)

so something else is wrong.


-- 
t



Processed: your mail

2018-11-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> affects 914167 src:openvdb
Bug #914167 [mesa-common-dev] fatal error: KHR/khrplatform.h: No such file or 
directory
Added indication that 914167 affects src:openvdb
> forwarded 914167 https://bugs.freedesktop.org/show_bug.cgi?id=107511
Bug #914167 [mesa-common-dev] fatal error: KHR/khrplatform.h: No such file or 
directory
Set Bug forwarded-to-address to 
'https://bugs.freedesktop.org/show_bug.cgi?id=107511'.
> tags 914167 patch fixed-upstream
Bug #914167 [mesa-common-dev] fatal error: KHR/khrplatform.h: No such file or 
directory
Added tag(s) patch and fixed-upstream.
>
End of message, stopping processing here.

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



Bug#914167: fatal error: KHR/khrplatform.h: No such file or directory

2018-11-19 Thread Mathieu Malaterre
Package: mesa-common-dev
Version: 18.2.5-1
Severity: serious
Tags: ftbfs

OpenVDB fails to build from source because of:

In file included from /usr/include/GL/gl.h:2055,
 from viewer/Font.h:40,
 from viewer/Font.cc:31:
/usr/include/GL/glext.h:467:10: fatal error: KHR/khrplatform.h: No
such file or directory
 #include 
  ^~~
compilation terminated.

ref:
https://buildd.debian.org/status/fetch.php?pkg=openvdb=amd64=5.2.0-5=154226=0

It would be nice to fix this, upstream seems to have provided a patch:

https://bugs.freedesktop.org/show_bug.cgi?id=107511



Bug#908681: libsane1: pointless package rename

2018-11-19 Thread Nils Schasse
Hi,

is this related to conflicts with the gnome package in sid?

(apt dist-upgrade)

To be removed:
  colord gnome gnome-color-manager gnome-control-center gnome-core
libsane1 libsane1:i386 sane-utils simple-scan task-gnome-desktop
Held back:
  libtiff5
Upgrade:
  libsane-common

Regards,
Nils


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


Bug#914166: gitlab: CVE-2018-19359: Unauthorized service template creation

2018-11-19 Thread Salvatore Bonaccorso
Source: gitlab
Version: 10.8.7+dfsg-1
Severity: grave
Tags: security upstream

Hi,

The following vulnerability was published for gitlab.

CVE-2018-19359[0]:
Unauthorized service template creation

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-2018-19359
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19359
[1] 
https://about.gitlab.com/2018/11/19/critical-security-release-gitlab-11-dot-4-dot-6-released/

Regards,
Salvatore



Processed: tagging 914154

2018-11-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 914154 + upstream
Bug #914154 [gnome-keyring] CVE-2018-19358
Added tag(s) upstream.
> thanks
Stopping processing here.

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



Bug#913037: marked as done ("test dulwich.tests.test_porcelain.PushTests.test_simple contains race condition")

2018-11-19 Thread Debian Bug Tracking System
Your message dated Tue, 20 Nov 2018 04:34:04 +
with message-id 
and subject line Bug#913037: fixed in dulwich 0.19.9-2
has caused the Debian Bug report #913037,
regarding "test dulwich.tests.test_porcelain.PushTests.test_simple contains 
race condition"
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.)


-- 
913037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913037
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dulwich
Version: 0.19.6-2
Severity: serious
Tags: sid buster

dulwich fails to build on s390x using Python 3.7. Endianess issue?

PYTHONHASHSEED=random PYTHONPATH=/<> python3 -m unittest
dulwich.tests.test_suite
...s..s..s.sss.s..E.ss./<>/dulwich/tests/compat/utils.py:135:
ResourceWarning: unclosed 
  p = subprocess.Popen(args, env=env, **popen_kwargs)
/<>/dulwich/tests/compat/utils.py:135: ResourceWarning: unclosed
file <_io.BufferedReader
name='local/.git/objects/pack/pack-f24e9574628e0e791aad98c454328069cfd8e0bd.pack'>
  p = subprocess.Popen(args, env=env, **popen_kwargs)
.ss.sss.sssss
==
ERROR: test_simple (dulwich.tests.test_porcelain.PushTests)
--
Traceback (most recent call last):
  File "/<>/dulwich/tests/test_porcelain.py", line 724, in 
test_simple
self.assertEqual(r_clone[b'HEAD'].id, self.repo[refs_path].id)
  File "/<>/dulwich/repo.py", line 528, in __getitem__
return self.object_store[self.refs[name]]
  File "/<>/dulwich/object_store.py", line 119, in __getitem__
type_num, uncomp = self.get_raw(sha)
  File "/<>/dulwich/object_store.py", line 461, in get_raw
raise KeyError(hexsha)
KeyError: b'a031515918b815701865df2363092b8d577d765f'

--
Ran 1268 tests in 60.038s

FAILED (errors=1, skipped=63)
make[2]: *** [Makefile:32: check] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [debian/rules:28: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:15: build-arch] Error 2
--- End Message ---
--- Begin Message ---
Source: dulwich
Source-Version: 0.19.9-2

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

Debian distribution maintenance software
pp.
Jelmer Vernooij  (supplier of updated dulwich package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 20 Nov 2018 04:09:22 +
Source: dulwich
Binary: python-dulwich pypy-dulwich python3-dulwich
Architecture: source
Version: 0.19.9-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Jelmer Vernooij 
Description:
 pypy-dulwich - Python Git library - pypy module
 python-dulwich - Python Git library
 python3-dulwich - Python Git 

Bug#913037: Bug #913037 in dulwich marked as pending

2018-11-19 Thread Jelmer Vernooij
Control: tag -1 pending

Hello,

Bug #913037 in dulwich reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/python-team/modules/dulwich/commit/0edda7e0191013931b8bab96e1145caeaefc54ed


Add patch 02_skip_flappy_test: Skip flappy test 
dulwich.tests.test_porcelain.PushTests.test_simple, which is subject to a race 
condition. Closes: #913037



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/913037



Processed: Bug #913037 in dulwich marked as pending

2018-11-19 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #913037 [src:dulwich] "test 
dulwich.tests.test_porcelain.PushTests.test_simple contains race condition"
Added tag(s) pending.

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



Bug#913037: (no subject)

2018-11-19 Thread Jelmer Vernooij
retitle 913037 "test dulwich.tests.test_porcelain.PushTests.test_simple 
contains race condition"
thanks

This is not a python3.7-specific issue, but a test that contains a
race condition that means it occasionally fails. This is reproducible
on other python versions as well (when running the test repeatedly).


signature.asc
Description: PGP signature


Processed: your mail

2018-11-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> retitle 913037 "test dulwich.tests.test_porcelain.PushTests.test_simple 
> contains race condition"
Bug #913037 [src:dulwich] dulwich fails to build on s390x using Python 3.7
Changed Bug title to '"test dulwich.tests.test_porcelain.PushTests.test_simple 
contains race condition"' from 'dulwich fails to build on s390x using Python 
3.7'.
> thanks
Stopping processing here.

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



Bug#914065: nheko FTBFS: Could not find a package configuration file provided by "MatrixClient"

2018-11-19 Thread Hubert Chathi
On Mon, 19 Nov 2018 02:31:47 +0100, Axel Beckert  said:

> The cause for this might be much earlier:

> [...]
> CMake Warning at CMakeLists.txt:200 (export):
>   Cannot create package registry file:

> 
> /sbuild-nonexistent/.cmake/packages/MatrixClient/217899eff9ecbd2457b9e7580f99b5aa

>   No such file or directory

Yup, I noticed that too.  I don't know much about CMake, so if anyone
has any insights, it would be much appreciated.

-- 
Hubert Chathi  -- https://www.uhoreg.ca/
Jabber: hub...@uhoreg.ca -- Matrix: @uhoreg:matrix.org
PGP/GnuPG key: 4096R/F24C F749 6C73 DDB8 DCB8  72DE B2DE 88D3 113A 1368



Bug#911876: asyncpg FTBFS: tests fail

2018-11-19 Thread Logan Rosen
Package: asyncpg
Version: 0.17.0-1
Followup-For: Bug #911876
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu disco ubuntu-patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * d/p/fix-large-oid-test.patch: Grab patch from upstream Git to fix large
OID test with PostgreSQL 11.

Thanks for considering the patch.

Logan Rosen

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

Kernel: Linux 4.18.0-10-generic (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)
LSM: AppArmor: enabled
diff -Nru asyncpg-0.17.0/debian/patches/fix-large-oid-test.patch 
asyncpg-0.17.0/debian/patches/fix-large-oid-test.patch
--- asyncpg-0.17.0/debian/patches/fix-large-oid-test.patch  1969-12-31 
19:00:00.0 -0500
+++ asyncpg-0.17.0/debian/patches/fix-large-oid-test.patch  2018-11-19 
22:00:06.0 -0500
@@ -0,0 +1,47 @@
+From ddb0ec2918c370ba6fc2f569835fd02078132058 Mon Sep 17 00:00:00 2001
+From: Elvis Pranskevichus 
+Date: Mon, 22 Oct 2018 19:07:06 -0400
+Subject: [PATCH] Fix large OID test under PostgreSQL 11
+
+PostgreSQL 11 seems to be automatically creating array types for domains
+with OIDs that _precede_ the OID of the array element type, so
+the large OID test trips over with an off-by-one assertion error.
+---
+ tests/test_codecs.py | 14 --
+ 1 file changed, 12 insertions(+), 2 deletions(-)
+
+diff --git a/tests/test_codecs.py b/tests/test_codecs.py
+index 9aac5ea..5498b40 100644
+--- a/tests/test_codecs.py
 b/tests/test_codecs.py
+@@ -1727,10 +1727,12 @@ def _decoder(value):
+ 
+ @unittest.skipIf(os.environ.get('PGHOST'), 'using remote cluster for testing')
+ class TestCodecsLargeOIDs(tb.ConnectedTestCase):
++LARGE_OID = 2147483648
++
+ @classmethod
+ def setup_cluster(cls):
+ cls.cluster = cls.new_cluster(pg_cluster.TempCluster)
+-cls.cluster.reset_wal(oid=2147483648)
++cls.cluster.reset_wal(oid=cls.LARGE_OID)
+ cls.start_cluster(cls.cluster)
+ 
+ async def test_custom_codec_large_oid(self):
+@@ -1739,7 +1741,15 @@ def setup_cluster(cls):
+ oid = await self.con.fetchval('''
+ SELECT oid FROM pg_type WHERE typname = 'test_domain_t'
+ ''')
+-self.assertEqual(oid, 2147483648)
++
++expected_oid = self.LARGE_OID
++if self.server_version >= (11, 0):
++# PostgreSQL 11 automatically create a domain array type
++# _before_ the domain type, so the expected OID is
++# off by one.
++expected_oid += 1
++
++self.assertEqual(oid, expected_oid)
+ 
+ # Test that introspection handles large OIDs
+ v = await self.con.fetchval('SELECT $1::test_domain_t', 10)
diff -Nru asyncpg-0.17.0/debian/patches/series 
asyncpg-0.17.0/debian/patches/series
--- asyncpg-0.17.0/debian/patches/series1969-12-31 19:00:00.0 
-0500
+++ asyncpg-0.17.0/debian/patches/series2018-11-19 22:00:15.0 
-0500
@@ -0,0 +1 @@
+fix-large-oid-test.patch


Bug#913487: marked as done (ddnet accesses the internet during the build)

2018-11-19 Thread Debian Bug Tracking System
Your message dated Tue, 20 Nov 2018 02:48:13 +
with message-id 
and subject line Bug#913487: fixed in ddnet 11.5-1
has caused the Debian Bug report #913487,
regarding ddnet accesses the internet during the build
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.)


-- 
913487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913487
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ddnet
Version: 11.4.6-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ddnet.html
https://buildd.debian.org/status/fetch.php?pkg=ddnet=armel=11.4.6-1=1541728808=0

...
[ RUN  ] Jobs.LookupHost
/<>/src/test/jobs.cpp:72: Failure
Expected equality of these values:
  pJob->m_Result
Which is: -1
  0
[  FAILED  ] Jobs.LookupHost (74 ms)
...
[  PASSED  ] 55 tests.
[  FAILED  ] 1 test, listed below:
[  FAILED  ] Jobs.LookupHost

 1 FAILED TEST
make[5]: *** [CMakeFiles/run_tests.dir/build.make:61: CMakeFiles/run_tests] 
Error 1
--- End Message ---
--- Begin Message ---
Source: ddnet
Source-Version: 11.5-1

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

Debian distribution maintenance software
pp.
Yangfl  (supplier of updated ddnet package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 18 Nov 2018 14:09:40 +0800
Source: ddnet
Binary: ddnet ddnet-server ddnet-tools ddnet-data
Architecture: source
Version: 11.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Yangfl 
Description:
 ddnet  - Teeworlds modification with a unique cooperative gameplay
 ddnet-data - Data for DDNet
 ddnet-server - Server for DDNet
 ddnet-tools - Tools for DDNet
Closes: 913487
Changes:
 ddnet (11.5-1) unstable; urgency=medium
 .
   * New upstream release
   * Disable tests that require network (Closes: #913487)
Checksums-Sha1:
 8bb7395e7a6a438afd72cc8e5e037ca4f2552b6a 2390 ddnet_11.5-1.dsc
 53f1e8fd53a64b0d2b1908cc6c9892cef02ff029 13849740 ddnet_11.5.orig.tar.xz
 513b7ecd8dd02d1bc0eaf40888e2c9f250d9fcd4 21004 ddnet_11.5-1.debian.tar.xz
 456e4582c96368404095c58fb56933a38aa80a1d 13499 ddnet_11.5-1_amd64.buildinfo
Checksums-Sha256:
 cd5c13bc73a53de272c9c9d972baa7715bb371fbc85dd362456939abb9ef8ab0 2390 
ddnet_11.5-1.dsc
 4990fdda47ec8e7ae82aedd9655b39115b2cd2b57f4f74b2a0e671be05febf3c 13849740 
ddnet_11.5.orig.tar.xz
 34e544ddd5dececfb0145501a2e335d909f4a6ddc9435870026289240cdffc19 21004 
ddnet_11.5-1.debian.tar.xz
 2898de1ce31792991e235ad018121d8d347a0295da77b33daef8cab07a8dfe1a 13499 
ddnet_11.5-1_amd64.buildinfo
Files:
 5941b4e7505e939e6a1d567f8238c325 2390 games optional ddnet_11.5-1.dsc
 4a858f405680bd03133521ed4bc8c6b7 13849740 games optional ddnet_11.5.orig.tar.xz
 dc7e8cd7951a45996fcdb74a07d4c5f2 21004 games optional 
ddnet_11.5-1.debian.tar.xz
 75529a92d9ae6b3e9832c2b35ee66f0e 13499 games optional 
ddnet_11.5-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAlvza2kACgkQwpPntGGC
Ws4kog//fz1PKCf//wgi6iQQyR0QV73wRrRQWxwyzakJlz6UV0GoOg89S2qd16JI
y4/3pWupCCezcdfgbhRDzDdT6fgEcBXPA/aZinV31XIHhii02BNuVL8wpsfc3eT3
gt/3LA9cyjE68RBrij5i3+xyMOkuz5Ep7tSDHhd94Iy9PABmXVBSYPlEi6crs3HK
UozQvE5jrK+67pLFzpAEXYWVgGp1umdioWTnT5RnGLmPy3S/snfHQJNjXR704P0U
xOZ6h+ZqReyqMASrWML2nGTOIoEJ53W/YS8eNGZe4ZALDzhrvIUVgrq+TfeqwRBB
kNSHV/GBgA+wAjG+b2T99f568mTaADEg0ixLZ+rPUSYHeHL2NHQAcSdyFAJlqlXL
yvsH5PsC+fHKjaYPMqALHuuIhExKLJwgauhbmttCQS65RQ7Ik08976zKIleln3a1
bu3cYqi0MZ/HRvtirVsYKdVaeS9R2zJx8boBumI+3jX+u71fGRtc5Y0uSyHNOacE
zInfk0GNUjD+VGuGbYRLPmbpzGxBfUgAMIZF5Gy2iTCKuPdZG8zHNCHIV8r/3x3J
UI6fJ8/FkNhURKKXx3bDXuX1pfBbZpR3xZgTPrCgc+yXxuel1TFoXnaXmMHwTvuW
viOdWjNDr9dIy9+xlZ+F+8R1UPoapwJQuCpqOo6IpjElYUgxbsM=
=ovBx
-END PGP SIGNATURE End Message ---


Bug#913708: node-mapnik ftbfs in unstable

2018-11-19 Thread Peter Green

tags 913708 +patch
thanks

This was one of the few remaining blockers for the icu transition in raspbian 
buster, so I hacked up a fix.

I am far from an expert (just a maintainer of a Debian derivative who ran into 
this build failure) but here is my interpretation of what is going on.

mapbox::geometry::geometry is a "variant" type which can be one of a variety of 
subtypes.

There is an implementation of encode_geometry_pbf that takes said variant and 
uses some template magic to look up the type stored in the variant and dispatch 
it to the correct implementation.

It looks like a new type "empty" was added to the list of types supported by the variant. When the 
template magic trys to generate the dispatch for the variant the compiler fails to find the routine to 
dispatch to, for reasons I don't fully understand it considers this as "ambiguous" rather than 
"no match".

The fix was to add an implementation of encode_geometry_pbf for mapbox::geometry::empty . 
From reading the existing "multi point" implementation I concluded this 
implementation should simply return false (I am far from an expert) and implemented it as 
such.

The wrinkle was that ideally the fix would be implemented in 
mapnik-vector-tile, but it seems that cannot be built
on 32-bit systems (raspbian is 32-bit), building it in debian buster seems to 
be blocked up by some ICU symbols
issue and building it in Debian sid seems to be blocked up by the hdf5 
transition.

The way I got around that wrinke was making the node-mapnik build process copy 
the headers to the
build-tree, then patch them. That way I could fix the issue from the 
node-mapnik source package.
ugly but it works.

A debdiff should show up soon at 
https://debdiffs.raspbian.org/main/n/node-mapnik no intent to NMU in Debian.



Processed: re: node-mapnik ftbfs in unstable

2018-11-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 913708 +patch
Bug #913708 [src:node-mapnik] node-mapnik ftbfs in unstable
Added tag(s) patch.
> thanks
Stopping processing here.

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



Bug#904111: clamav-daemon causing deadlocks/blocking I/O

2018-11-19 Thread Adam Lambert
Ah, so I think you may have the winner.   I set my temp directory to be
something other than /tmp, and turned ClamAV back on, and it's been running
for about an hour now with  no obvious ill effects.   I will report back if
something else crops up, but I think this may solve it.

Thank you!

On Mon, Nov 19, 2018 at 2:31 PM Sebastian Andrzej Siewior
 wrote:

> On 2018-11-19 21:01:07 [+0100], To Adam Lambert wrote:
> > On 2018-11-12 10:17:32 [-0800], Adam Lambert wrote:
> > > I believe I already supplied all that way back when I opened up this
> bug
> > > report.   But for reference, here it is again:
> >
> > I tried it back then with no luck. Thanks for the info. I will try to
> > reproduce this asap and get back to you.
>
> Okay. It triggers. This
>
> OnAccessIncludePath /tmp
>
> seems to be the root of all evil. Removing this option or adding
>
> TemporaryDirectory /var/tmp/
>
> seems to make it go away. So I *think* the problem is that clamav makes
> temporary files during scanning which in turn it tries to scan and
> blocks itself.
> Can you acknowledge the behaviour?
>
> Sebastian
>


Bug#913808: marked as done (ndctl: Fails to build: missing build-dependencies)

2018-11-19 Thread Debian Bug Tracking System
Your message dated Mon, 19 Nov 2018 23:34:30 +
with message-id 
and subject line Bug#913808: fixed in ndctl 63-1.1
has caused the Debian Bug report #913808,
regarding ndctl: Fails to build: missing build-dependencies
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.)


-- 
913808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913808
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ndctl
Version: 63-1
Severity: serious
Tags: ftbfs

ndctl fails to build in a clean chroot. This can be fixed by adding
bash-completion and systemd to Build-Depends.

It might be nice if the build system would allow building systemd
support without needing the systemd pkgconfig file, because some
people want to be able to build Debian packages without installing
systemd. Several other projects support this but I don't have the time
to work on that right now. (I use systemd anyway.)

There is also a mistake in debian/libndctl6-dev.install . Please
replace powerpc64le-linux-gnu with *

Build logs
-
https://buildd.debian.org/status/package.php?p=ndctl

Build log excerpt
---
checking for BASH_COMPLETION... no
configure: error: Package requirements (bash-completion >= 2.0) were not met:

No package 'bash-completion' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.


Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: ndctl
Source-Version: 63-1.1

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

Debian distribution maintenance software
pp.
Adam Borowski  (supplier of updated ndctl 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: Mon, 19 Nov 2018 13:54:10 +0100
Source: ndctl
Binary: ndctl libndctl6 libndctl6-dev libdaxctl1 libdaxctl1-dev
Architecture: source
Version: 63-1.1
Distribution: unstable
Urgency: medium
Maintainer: Breno Leitao 
Changed-By: Adam Borowski 
Description:
 libdaxctl1 - daxctl1 library used by ndctl
 libdaxctl1-dev - Development files for libdaxctl1
 libndctl6  - ndctl6 library used by ndctl tool
 libndctl6-dev - Development files for libndctl6
 ndctl  - libraries for tool for 'libnvdimm'
Closes: 913713 913737 913808 913809 913887
Changes:
 ndctl (63-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Make debian/copyright betterer. (Closes: #913713)
   * Fix FTBFS on all architectures. (Closes: #913808)
   * Install pkg-config files, make dh_missing fail. (Closes: #913809, #913737)
   * Add provides for soname-less -dev packages. (Closes: #913887)
Checksums-Sha1:
 8fe5f0654804b3e38da100be857557ea09d6ad80 2098 ndctl_63-1.1.dsc
 209fcf9ab7f90c677b8ea76734d15481c9f72325 6768 ndctl_63-1.1.debian.tar.xz
 55153a8a79fb8f366b0fdb070b2cc8ae3dfc20f9 5421 ndctl_63-1.1_source.buildinfo
Checksums-Sha256:
 c60d54907a8a21ebbf181d54ba00a77f9578795ee8ff189905475589c6a2bcec 2098 
ndctl_63-1.1.dsc
 42e5c77128f7bf59f79087eae3955747d4fcf8cb59f10aa34b5cd5167108e052 6768 
ndctl_63-1.1.debian.tar.xz
 518b1ab28b8d6cdaf92ed4335764a862736e153ce0a6675ba683e6bb2d388659 5421 
ndctl_63-1.1_source.buildinfo
Files:
 6320d56826d7621f730b82be93be2549 2098 admin optional ndctl_63-1.1.dsc
 e3af8ff9192aa0216180af5ee359a023 6768 admin optional ndctl_63-1.1.debian.tar.xz
 ad4c12cf8be622f8d0b7ba3fc02e1ca5 5421 admin optional 
ndctl_63-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEkjZVexcMh/iCHArDweDZLphvfH4FAlvzPJwUHGtpbG9ieXRl
QGFuZ2JhbmQucGwACgkQweDZLphvfH5gkQ//SOqPiTJnhf38+lF26atiW1I9457X
tgEL/CAQ2KugSHeTYMac1XNOJGEpCDtVVNPm0WrJjNdoVCuDZLlyqVYhyP4w9bpY
gCITXLl3Rrw9vgKZ6Gy/sxZIP9+lqH0DLJP3YTbJ3QlALPPorVQq2P09nbqkxAof
wlAtBu36GJuBzwPS6JsZ+4o3fO/PNXADUAIEJ2fe7ForUt2SjPTO6NTWGHYiEZb9
5yse5SKAOLWREpKwGfwIEmdmmiqDcENJJOPnt1Ppbvoxew2UBzthdblSipbPUM4Y
vX8xf5ztkQdLSvjtaidU7jKIIj2fd7n/mgPKaUf/GRk68FzDj5w0g7M85R+1xr2w
rqUr+yvzc5pt9vTUW+WsiEGM55qhedhMuhAvBj6P6QUUtYTbXYzFFhsmhr3GZIev
yNcBzXa7nR2VAWpeS13XjF3y/GJ2zw4kQeuWEjKkfEE73WbI3zowTiRbgtWHpzji

Bug#913713: marked as done (ndctl: Incomplete debian/copyright?)

2018-11-19 Thread Debian Bug Tracking System
Your message dated Mon, 19 Nov 2018 23:34:30 +
with message-id 
and subject line Bug#913713: fixed in ndctl 63-1.1
has caused the Debian Bug report #913713,
regarding ndctl: Incomplete debian/copyright?
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.)


-- 
913713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913713
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ndctl
Version: 63-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Breno Leitao , ftpmas...@debian.org

Hi,

I just ACCEPTed ndctl from NEW but noticed it was missing attribution 
in debian/copyright for at least Junio Hamano, Fujitsu, etc.

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: ndctl
Source-Version: 63-1.1

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

Debian distribution maintenance software
pp.
Adam Borowski  (supplier of updated ndctl 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: Mon, 19 Nov 2018 13:54:10 +0100
Source: ndctl
Binary: ndctl libndctl6 libndctl6-dev libdaxctl1 libdaxctl1-dev
Architecture: source
Version: 63-1.1
Distribution: unstable
Urgency: medium
Maintainer: Breno Leitao 
Changed-By: Adam Borowski 
Description:
 libdaxctl1 - daxctl1 library used by ndctl
 libdaxctl1-dev - Development files for libdaxctl1
 libndctl6  - ndctl6 library used by ndctl tool
 libndctl6-dev - Development files for libndctl6
 ndctl  - libraries for tool for 'libnvdimm'
Closes: 913713 913737 913808 913809 913887
Changes:
 ndctl (63-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Make debian/copyright betterer. (Closes: #913713)
   * Fix FTBFS on all architectures. (Closes: #913808)
   * Install pkg-config files, make dh_missing fail. (Closes: #913809, #913737)
   * Add provides for soname-less -dev packages. (Closes: #913887)
Checksums-Sha1:
 8fe5f0654804b3e38da100be857557ea09d6ad80 2098 ndctl_63-1.1.dsc
 209fcf9ab7f90c677b8ea76734d15481c9f72325 6768 ndctl_63-1.1.debian.tar.xz
 55153a8a79fb8f366b0fdb070b2cc8ae3dfc20f9 5421 ndctl_63-1.1_source.buildinfo
Checksums-Sha256:
 c60d54907a8a21ebbf181d54ba00a77f9578795ee8ff189905475589c6a2bcec 2098 
ndctl_63-1.1.dsc
 42e5c77128f7bf59f79087eae3955747d4fcf8cb59f10aa34b5cd5167108e052 6768 
ndctl_63-1.1.debian.tar.xz
 518b1ab28b8d6cdaf92ed4335764a862736e153ce0a6675ba683e6bb2d388659 5421 
ndctl_63-1.1_source.buildinfo
Files:
 6320d56826d7621f730b82be93be2549 2098 admin optional ndctl_63-1.1.dsc
 e3af8ff9192aa0216180af5ee359a023 6768 admin optional ndctl_63-1.1.debian.tar.xz
 ad4c12cf8be622f8d0b7ba3fc02e1ca5 5421 admin optional 
ndctl_63-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEkjZVexcMh/iCHArDweDZLphvfH4FAlvzPJwUHGtpbG9ieXRl
QGFuZ2JhbmQucGwACgkQweDZLphvfH5gkQ//SOqPiTJnhf38+lF26atiW1I9457X
tgEL/CAQ2KugSHeTYMac1XNOJGEpCDtVVNPm0WrJjNdoVCuDZLlyqVYhyP4w9bpY
gCITXLl3Rrw9vgKZ6Gy/sxZIP9+lqH0DLJP3YTbJ3QlALPPorVQq2P09nbqkxAof
wlAtBu36GJuBzwPS6JsZ+4o3fO/PNXADUAIEJ2fe7ForUt2SjPTO6NTWGHYiEZb9
5yse5SKAOLWREpKwGfwIEmdmmiqDcENJJOPnt1Ppbvoxew2UBzthdblSipbPUM4Y
vX8xf5ztkQdLSvjtaidU7jKIIj2fd7n/mgPKaUf/GRk68FzDj5w0g7M85R+1xr2w
rqUr+yvzc5pt9vTUW+WsiEGM55qhedhMuhAvBj6P6QUUtYTbXYzFFhsmhr3GZIev
yNcBzXa7nR2VAWpeS13XjF3y/GJ2zw4kQeuWEjKkfEE73WbI3zowTiRbgtWHpzji
eiVqCdyYHM5ImhYpRn405OnhwS0ebo5QZeetFpKmnyk8jqKCr49gUtra3+Oy38HQ
6Ix7n1bzupjyMqAzZY4L0V0l1lJvzqxvzUZAbMkDvd6N/MopThY0f7Q10zD8CksE
mjtowUQseohddit9FsLYQ1esw5vZ9WcDLlX4ZKw6+DpIy983hvVr50BFlhLHp+6S
+ixTh64nTSsEbHE=
=29M3
-END PGP SIGNATURE End Message ---


Bug#914154: CVE-2018-19358

2018-11-19 Thread Moritz Muehlenhoff
Package: gnome-keyring
Version: 3.28.2-1
Severity: grave
Tags: security

Please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19358,

I'm unfamiliar with the details of gnome-keyring, not sure if the
severity is appropriate, just adjusted as needed.

Cheers,
MOritz



Bug#913600: Bug #913600 in ceph marked as pending

2018-11-19 Thread Gaudenz Steinlin
Control: tag -1 pending

Hello,

Bug #913600 in ceph reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/ceph-team/ceph/commit/ff60a338b54a961f95bf99c45ad25d3a8571aff9


Only enable RADOS GW Beast frontend on supported archs

Only a limited set of architectures supports libboost-context and
libboost-coroutine which are both required for the Beast frontend.
Disable this frontend on unsupported architectures.

Closes: #913600



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/913600



Processed: Bug #913600 in ceph marked as pending

2018-11-19 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #913600 [src:ceph] ceph: bd-uninst on several architectures: 
libboost-context1.67-dev not available
Added tag(s) pending.

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



Bug#904111: clamav-daemon causing deadlocks/blocking I/O

2018-11-19 Thread Sebastian Andrzej Siewior
On 2018-11-19 21:01:07 [+0100], To Adam Lambert wrote:
> On 2018-11-12 10:17:32 [-0800], Adam Lambert wrote:
> > I believe I already supplied all that way back when I opened up this bug
> > report.   But for reference, here it is again:
> 
> I tried it back then with no luck. Thanks for the info. I will try to
> reproduce this asap and get back to you.

Okay. It triggers. This

OnAccessIncludePath /tmp

seems to be the root of all evil. Removing this option or adding

TemporaryDirectory /var/tmp/

seems to make it go away. So I *think* the problem is that clamav makes
temporary files during scanning which in turn it tries to scan and
blocks itself.
Can you acknowledge the behaviour?
 
Sebastian



Processed: severity of 911954 is serious

2018-11-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 911954 serious
Bug #911954 [src:witty] [src:witty] FTBFS with boost1.67
Severity set to 'serious' from 'wishlist'
> thanks
Stopping processing here.

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



Bug#914151: dlz-ldap-enum FTBFS with bind9 9.11.5

2018-11-19 Thread Adrian Bunk
Source: dlz-ldap-enum
Version: 1.1.0-1
Severity: serious
Tags: ftbfs buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dlz-ldap-enum.html

...
/bin/bash ./libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.   
-Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-ffile-prefix-map=/build/1st/dlz-ldap-enum-1.1.0=. -fstack-protector-strong 
-Wformat -Werror=format-security -c -o dlz_ldap_enum_driver.lo 
dlz_ldap_enum_driver.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-O2 -ffile-prefix-map=/build/1st/dlz-ldap-enum-1.1.0=. -fstack-protector-strong 
-Wformat -Werror=format-security -c dlz_ldap_enum_driver.c  -fPIC -DPIC -o 
.libs/dlz_ldap_enum_driver.o
In file included from dlz_ldap_enum_driver.c:73:
sdlz_helper.h:60:2: error: unknown type name 'isc_boolean_t'
  isc_boolean_t   direct;
  ^
dlz_ldap_enum_driver.c:357:19: error: unknown type name 'isc_boolean_t'; did 
you mean 'isc_socket_t'?
void *ptr, isc_boolean_t allnodes, char *tel,
   ^
   isc_socket_t
dlz_ldap_enum_driver.c: In function 'ldap_get_results':
dlz_ldap_enum_driver.c:862:12: warning: implicit declaration of function 
'ldap_process_results'; did you mean 'ldap_get_results'? 
[-Wimplicit-function-declaration]
   result = ldap_process_results((LDAP *) dbi->dbconn, ldap_msg,
^~~~
ldap_get_results
dlz_ldap_enum_driver.c:864:17: error: 'isc_boolean_true' undeclared (first use 
in this function); did you mean 'isc_buffer_free'?
ptr, isc_boolean_true, NULL,
 ^~~~
 isc_buffer_free
dlz_ldap_enum_driver.c:864:17: note: each undeclared identifier is reported 
only once for each function it appears in
dlz_ldap_enum_driver.c:871:17: error: 'isc_boolean_false' undeclared (first use 
in this function); did you mean 'isc_buffer_base'?
ptr, isc_boolean_false, tel,
 ^
 isc_buffer_base
make[2]: *** [Makefile:489: dlz_ldap_enum_driver.lo] Error 1



Bug#881506: xul-ext-gnome-keyring doesn't work with firefox >=57

2018-11-19 Thread Moritz Mühlenhoff
On Mon, Nov 19, 2018 at 07:22:11AM -0500, Jeremy Bicha wrote:
> > Given that Xul is still supported in Thunderbird, let maybe drop the 
> > support for
> > Firefox/Iceweasel (with a NOTE telling people how to migrate their existing
> > secrets) and upgrade to 0.13?
> 
> While upgrading to 0.13 would fix one problem, it still wouldn't be
> able to reach Testing since it depends on libgnome-keyring which is
> being removed from Debian. See https;//bugs.debian.org/892358

And actually, it's also broken on Thunderbird; I installed it and
the addon manager in Thunderbird has greyed it out with a message
stating that it's incompatible with 60.3.

Let's remove it from unstable and stretch?

Cheers,
Moritz



Bug#910874: unattended-upgrades removes packages even if

2018-11-19 Thread Bálint Réczey
forwarded -1 https://github.com/mvo5/unattended-upgrades/pull/156
tags -1 confirmed pending

Hi Jan,

Jan Kowalsky  ezt írta (időpont: 2018. okt.
12., P, 17:57):
>
> Package: unattended-upgrades
> Version: 0.93.1+nmu1
> Severity: serious
>
> Even if I have configured 'Remove-Unused-Dependencies "false";' in
> apt.conf.d/50unattended-upgrades:
>
>
> // Do automatic removal of new unused dependencies after the upgrade
> // (equivalent to apt-get autoremove)
> Unattended-Upgrade::Remove-Unused-Dependencies "false";
>
> it DOES remove packages (see below) as long as apt is configured as:

There are several issues relevant to this bug. First, this option is
misleading and this is fixed here:
https://github.com/mvo5/unattended-upgrades/commit/7f84b1b029e127595fdf3d6928ac2382b640f0ee#diff-4e9bf0f40e9f1a04bed3d01667f4d2f6

The one to be set to false is this one:
Unattended-Upgrade::Remove-New-Unused-Dependencies

Also u-u can incorrectly remove previously unused packages, too which
is being fixed here:
https://github.com/mvo5/unattended-upgrades/pull/156

I'm closing this bug with the PR because the log you attached seem to
contain removal of  packages unrelated to the ones upgraded.

>
> APT::AutoRemove::RecommendsImportant "false";
>
> In my understanding this shouldn't be the case.

Yes, with setting Unattended-Upgrade::Remove-New-Unused-Dependencies
u-u should not remove packages even with the above APT setting.

Thank you for reporting the bug.

Cheers,
Balint

>
> Here is the output of unattended-upgrade:
>
> unattended-upgrade -d -v --dry-run
> Initial blacklisted packages:
> Initial whitelisted packages:
> Starting unattended upgrades script
> Allowed origins are: ['o=Debian,n=stretch,l=Debian-Security',
> 'o=Debian,n=stretch,l=Debian-Security']
> Checking: icedove ([ origin:'Debian' label:'Debian-Security' site:'security.debian.org'
> isTrusted:True>,  origin:'Debian' label:'Debian-Security' site:'security.debian.org'
> isTrusted:True>])
> pkg 'enigmail' now marked delete
> sanity check failed
> Checking: icedove-l10n-de ([ origin:'Debian' label:'Debian-Security' site:'security.debian.org'
> isTrusted:True>,  origin:'Debian' label:'Debian-Security' site:'security.debian.org'
> isTrusted:True>])
> pkg 'enigmail' now marked delete
> sanity check failed
> Checking: iceowl-extension ([ origin:'Debian' label:'Debian-Security' site:'security.debian.org'
> isTrusted:True>,  origin:'Debian' label:'Debian-Security' site:'security.debian.org'
> isTrusted:True>])
> pkg 'enigmail' now marked delete
> sanity check failed
> Checking: libsnmp-base ([ origin:'Debian' label:'Debian-Security' site:'security.debian.org'
> isTrusted:True>,  origin:'Debian' label:'Debian-Security' site:'security.debian.org'
> isTrusted:True>])
> Checking: libsnmp30 ([ origin:'Debian' label:'Debian-Security' site:'security.debian.org'
> isTrusted:True>])
> Checking: lightning ([ origin:'Debian' label:'Debian-Security' site:'security.debian.org'
> isTrusted:True>,  origin:'Debian' label:'Debian-Security' site:'security.debian.org'
> isTrusted:True>])
> pkg 'enigmail' now marked delete
> sanity check failed
> Checking: thunderbird ([ origin:'Debian' label:'Debian-Security' site:'security.debian.org'
> isTrusted:True>])
> pkg 'enigmail' now marked delete
> sanity check failed
> Checking: thunderbird-l10n-de ([ archive:'stable' origin:'Debian' label:'Debian-Security'
> site:'security.debian.org' isTrusted:True>,  archive:'stable' origin:'Debian' label:'Debian-Security'
> site:'security.debian.org' isTrusted:True>])
> pkg 'enigmail' now marked delete
> sanity check failed
> pkgs that look like they should be upgraded: libsnmp-base
> libsnmp30
> Fetched 0 B in 0s (0 B/s)
>
>
> fetch.run() result: 0
>  FileSize: 1594854
> DestFile:'/var/cache/apt/archives/libsnmp-base_5.7.3+dfsg-1.7+deb9u1_all.deb'
> DescURI:
> 'http://security.debian.org/pool/updates/main/n/net-snmp/libsnmp-base_5.7.3+dfsg-1.7+deb9u1_all.deb'
> ID:0 ErrorText: ''>
> check_conffile_prompt('/var/cache/apt/archives/libsnmp-base_5.7.3+dfsg-1.7+deb9u1_all.deb')
> found pkg: libsnmp-base
> No conffiles in deb
> '/var/cache/apt/archives/libsnmp-base_5.7.3+dfsg-1.7+deb9u1_all.deb'
> (There is no member named 'conffiles')
>  FileSize: 2331604
> DestFile:'/var/cache/apt/archives/libsnmp30_5.7.3+dfsg-1.7+deb9u1_amd64.deb'
> DescURI:
> 'http://security.debian.org/pool/updates/main/n/net-snmp/libsnmp30_5.7.3+dfsg-1.7+deb9u1_amd64.deb'
> ID:0 ErrorText: ''>
> check_conffile_prompt('/var/cache/apt/archives/libsnmp30_5.7.3+dfsg-1.7+deb9u1_amd64.deb')
> found pkg: libsnmp30
> No conffiles in deb
> '/var/cache/apt/archives/libsnmp30_5.7.3+dfsg-1.7+deb9u1_amd64.deb'
> (There is no member named 'conffiles')
> blacklist: []
> whitelist: []
> Option --dry-run given, *not* performing real actions
> Packages that will be upgraded: libsnmp-base libsnmp30
> Writing dpkg log to
> '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log'
> found partition of size 2 (['libsnmp-base', 'libsnmp30'])
> found 

Bug#913803: marked as done (python3-pykdl: PyKDL fails to import)

2018-11-19 Thread Debian Bug Tracking System
Your message dated Mon, 19 Nov 2018 22:10:50 +
with message-id 
and subject line Bug#913803: fixed in orocos-kdl 1.4.0-7
has caused the Debian Bug report #913803,
regarding python3-pykdl: PyKDL fails to import
to be marked as done.

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

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


-- 
913803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913803
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pykdl
Version: 1.4.0-6
Severity: grave
Justification: renders package unusable

Steps to reproduce:

$ python3
Python 3.6.6 (default, Jun 27 2018, 14:44:17)
[GCC 8.1.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from PyKDL import *
Traceback (most recent call last):
  File "", line 1, in 
ModuleNotFoundError: No module named 'sip'


Probably just a missing dependency?


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

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

Versions of packages python3-pykdl depends on:
ii  libc6 2.27-6
ii  libgcc1   1:8.2.0-8
ii  liborocos-kdl1.4  1.4.0-5
ii  libpython3.6  3.6.6-1
ii  libstdc++68.2.0-8
ii  python3   3.6.6-1

python3-pykdl recommends no packages.

python3-pykdl suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: orocos-kdl
Source-Version: 1.4.0-7

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated orocos-kdl 
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: Mon, 19 Nov 2018 22:31:27 +0100
Source: orocos-kdl
Binary: liborocos-kdl-dev liborocos-kdl1.4 python3-pykdl
Architecture: source
Version: 1.4.0-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jochen Sprickerhof 
Description:
 liborocos-kdl-dev - Kinematics and Dynamics Library development files
 liborocos-kdl1.4 - Kinematics and Dynamics Library runtime
 python3-pykdl - Kinematics and Dynamics Library Python library
Closes: 913803
Changes:
 orocos-kdl (1.4.0-7) unstable; urgency=medium
 .
   * Add missing dependency (Closes: #913803)
   * Fix typo in changelog
Checksums-Sha1:
 80aa75790652e2b5c0508306cc98d787ee5bea45 2322 orocos-kdl_1.4.0-7.dsc
 62a9c7f35be70a639b7ced6ba22ff086639baa01 6052 orocos-kdl_1.4.0-7.debian.tar.xz
 99b99fab4ff78efe252239cceff7d095a5259fdf 7118 
orocos-kdl_1.4.0-7_source.buildinfo
Checksums-Sha256:
 f7489a0166a2976efe0d907f60dfb5bd217b3a4c6c6603df1774a18bc092098b 2322 
orocos-kdl_1.4.0-7.dsc
 09af248430f3b5f2f4cdadbddffccea9cc91f5b281f748a9503b5c7f4539aa33 6052 
orocos-kdl_1.4.0-7.debian.tar.xz
 192b40e79b837b444da697e903ffec2f15f36ceebff2777dd54f995b1b088f44 7118 
orocos-kdl_1.4.0-7_source.buildinfo
Files:
 65d634710ba979c42f6c0f5b65ee81e7 2322 libs optional orocos-kdl_1.4.0-7.dsc
 6349f9a57209b07b0c0e307b40d25eb4 6052 libs optional 
orocos-kdl_1.4.0-7.debian.tar.xz
 3247dec416b8a5caae036f37219d472b 7118 libs optional 
orocos-kdl_1.4.0-7_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAlvzK+AUHGpzcHJpY2tl
QGRlYmlhbi5vcmcACgkQW//cwljmlDPqpQ/7BdCMMOl4+2mo/+E9CENnGLh9FKnL
qfpYHZBdD2vsICOqMSlf77aYezPBWODQ5SIOscywW+U6nbAJm4uDfh/IO1qzrQNL
LqdnKLPOpoS4CrJXs1FuuHuC/XBBmsXDpXvPCl11yu9UJXf2AO6tiSHQP7KNG8IX
kg45OOsK+T6U5cCnpDRbvNSOqtR+NKoX/kVh1f5T7ZCOtjb0C7DGOwCa9UQouzl8
gtbhGtS2OiVU7c+BuCZqdNAATfxmTBzut+rTX+tTvzNgvoUKP0HFDwYPRz1FhwzZ
eKOUCt6N3McF8+tD1n3QZbIfYtSTn0guGBTkw38IMfXSopTTisJMvmgs5XV450RJ
lrLkwjVASOXnBd5DS+l3WiP2iLLTpvz4zRBxKjrqRvcJIg3hmA/Qsr2PfKyWJZ4y
SeZD5FHHB4csu2DsQeUz7EWvhDmt1rgM5Ev5c8hihM2Z31bl49X3np90D7WOJ1pQ

Bug#914148: qr-code-generator: binary-any builds require packages only in Build-Depends-Indep

2018-11-19 Thread Adrian Bunk
Source: qr-code-generator
Version: 1.2.1-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=qr-code-generator=sid

...
   debian/rules override_dh_auto_clean-indep
make[1]: Entering directory '/<>'
dh_auto_clean --buildsystem=pybuild --sourcedirectory=python/
dh_auto_clean: unable to load build system class 'pybuild': Can't locate 
Debian/Debhelper/Buildsystem/pybuild.pm in @INC (you may need to install the 
Debian::Debhelper::Buildsystem::pybuild module) (@INC contains: /etc/perl 
/usr/local/lib/aarch64-linux-gnu/perl/5.28.0 /usr/local/share/perl/5.28.0 
/usr/lib/aarch64-linux-gnu/perl5/5.28 /usr/share/perl5 
/usr/lib/aarch64-linux-gnu/perl/5.28 /usr/share/perl/5.28 
/usr/local/lib/site_perl /usr/lib/aarch64-linux-gnu/perl-base) at (eval 2) line 
1.
BEGIN failed--compilation aborted at (eval 2) line 1.

make[1]: *** [debian/rules:28: override_dh_auto_clean-indep] Error 2


This module is in dh-python, which is only in Build-Depends-Indep.



Bug#913005: ruby-rack: CVE-2018-16471: Possible XSS vulnerability in Rack

2018-11-19 Thread Salvatore Bonaccorso
Hi Chris,

On Mon, Nov 19, 2018 at 03:17:27AM -0500, Chris Lamb wrote:
> Chris Lamb wrote:
> 
> > Security team, like ruby-i18n, I would be more than happy to prepare
> > and upload a stable security upload of this package when addressing
> > it in jessie LTS.
> […]
> > Ruby team, again, I could easily upload to sid at the same time. Let
> > me know here too.
> 
> Gentle ping on the above two queries? :)

I think those will be no-dsa and can be adressed via a point release,
but we first need to evaluate those further.

Regards,
Salvatore



Bug#914147: libkolabxml FTBFS: symbol differences

2018-11-19 Thread Adrian Bunk
Source: libkolabxml
Version: 1.1.6-3
Severity: serious
Tags: ftbfs

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

...
   dh_makeshlibs -a -O--buildsystem=pybuild
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libkolabxml1v5/DEBIAN/symbols doesn't match 
completely debian/libkolabxml1v5.symbols
--- debian/libkolabxml1v5.symbols (libkolabxml1v5_1.1.6-3+b2_amd64)
+++ dpkg-gensymbolsIUxgTb   2018-11-16 17:42:07.534213410 +
@@ -3937,6 +3937,8 @@
  
(optional=templinst)_ZN3xsd3cxx4tree27element_factory_initializerILm0EcN13icalendar_2_014TznamePropTypeEEC2EPKcS7_S7_S7_@Base
 1.1.0
  
(optional=templinst)_ZN3xsd3cxx4tree27element_factory_initializerILm0EcN13icalendar_2_014TznamePropTypeEED1Ev@Base
 1.1.0
  
(optional=templinst)_ZN3xsd3cxx4tree27element_factory_initializerILm0EcN13icalendar_2_014TznamePropTypeEED2Ev@Base
 1.1.0
+ 
_ZN3xsd3cxx4tree27element_factory_initializerILm0EcN13icalendar_2_015AltrepParamTypeEEC1EPKcS7_S7_S7_@Base
 1.1.6-3+b2
+ 
_ZN3xsd3cxx4tree27element_factory_initializerILm0EcN13icalendar_2_015AltrepParamTypeEEC2EPKcS7_S7_S7_@Base
 1.1.6-3+b2
  
(optional=templinst)_ZN3xsd3cxx4tree27element_factory_initializerILm0EcN13icalendar_2_015AltrepParamTypeEED1Ev@Base
 1.1.0
  
(optional=templinst)_ZN3xsd3cxx4tree27element_factory_initializerILm0EcN13icalendar_2_015AltrepParamTypeEED2Ev@Base
 1.1.0
  
(optional=templinst)_ZN3xsd3cxx4tree27element_factory_initializerILm0EcN13icalendar_2_015CommentPropTypeEEC1EPKcS7_S7_S7_@Base
 1.1.0
@@ -3951,8 +3953,8 @@
  
(optional=templinst)_ZN3xsd3cxx4tree27element_factory_initializerILm0EcN13icalendar_2_015CreatedPropTypeEEC2EPKcS7_S7_S7_@Base
 1.1.0
  
(optional=templinst)_ZN3xsd3cxx4tree27element_factory_initializerILm0EcN13icalendar_2_015CreatedPropTypeEED1Ev@Base
 1.1.0
  
(optional=templinst)_ZN3xsd3cxx4tree27element_factory_initializerILm0EcN13icalendar_2_015CreatedPropTypeEED2Ev@Base
 1.1.0
- (optional=templinst|arch=amd64 
kfreebsd-amd64)_ZN3xsd3cxx4tree27element_factory_initializerILm0EcN13icalendar_2_015CutypeParamTypeEEC1EPKcS7_S7_S7_@Base
 1.1.6
- (optional=templinst|arch=amd64 
kfreebsd-amd64)_ZN3xsd3cxx4tree27element_factory_initializerILm0EcN13icalendar_2_015CutypeParamTypeEEC2EPKcS7_S7_S7_@Base
 1.1.6
+#MISSING: 1.1.6-3+b2# (optional=templinst|arch=amd64 
kfreebsd-amd64)_ZN3xsd3cxx4tree27element_factory_initializerILm0EcN13icalendar_2_015CutypeParamTypeEEC1EPKcS7_S7_S7_@Base
 1.1.6
+#MISSING: 1.1.6-3+b2# (optional=templinst|arch=amd64 
kfreebsd-amd64)_ZN3xsd3cxx4tree27element_factory_initializerILm0EcN13icalendar_2_015CutypeParamTypeEEC2EPKcS7_S7_S7_@Base
 1.1.6
  
(optional=templinst)_ZN3xsd3cxx4tree27element_factory_initializerILm0EcN13icalendar_2_015CutypeParamTypeEED1Ev@Base
 1.1.0
  
(optional=templinst)_ZN3xsd3cxx4tree27element_factory_initializerILm0EcN13icalendar_2_015CutypeParamTypeEED2Ev@Base
 1.1.0
  
(optional=templinst)_ZN3xsd3cxx4tree27element_factory_initializerILm0EcN13icalendar_2_015DtstampPropTypeEEC1EPKcS7_S7_S7_@Base
 1.1.0
@@ -4395,8 +4397,8 @@
  (optional=templinst|arch=!amd64 !hppa 
!kfreebsd-amd64)_ZN3xsd3cxx4tree30element_serializer_initializerILm0EcN13icalendar_2_011UidPropTypeEEC2EPKcS7_S7_S7_@Base
 1.1.6
  
(optional=templinst)_ZN3xsd3cxx4tree30element_serializer_initializerILm0EcN13icalendar_2_011UidPropTypeEED1Ev@Base
 1.1.0
  
(optional=templinst)_ZN3xsd3cxx4tree30element_serializer_initializerILm0EcN13icalendar_2_011UidPropTypeEED2Ev@Base
 1.1.0
- (optional=templinst|arch=!alpha !armel !armhf !hppa !mips64el !ppc64el 
!sparc64)_ZN3xsd3cxx4tree30element_serializer_initializerILm0EcN13icalendar_2_011UrlPropTypeEEC1EPKcS7_S7_S7_@Base
 1.1.0
- (optional=templinst|arch=!alpha !armel !armhf !hppa !mips64el !ppc64el 
!sparc64)_ZN3xsd3cxx4tree30element_serializer_initializerILm0EcN13icalendar_2_011UrlPropTypeEEC2EPKcS7_S7_S7_@Base
 1.1.0
+#MISSING: 1.1.6-3+b2# (optional=templinst|arch=!alpha !armel !armhf !hppa 
!mips64el !ppc64el 
!sparc64)_ZN3xsd3cxx4tree30element_serializer_initializerILm0EcN13icalendar_2_011UrlPropTypeEEC1EPKcS7_S7_S7_@Base
 1.1.0
+#MISSING: 1.1.6-3+b2# (optional=templinst|arch=!alpha !armel !armhf !hppa 
!mips64el !ppc64el 
!sparc64)_ZN3xsd3cxx4tree30element_serializer_initializerILm0EcN13icalendar_2_011UrlPropTypeEEC2EPKcS7_S7_S7_@Base
 1.1.0
  
(optional=templinst)_ZN3xsd3cxx4tree30element_serializer_initializerILm0EcN13icalendar_2_011UrlPropTypeEED1Ev@Base
 1.1.0
  
(optional=templinst)_ZN3xsd3cxx4tree30element_serializer_initializerILm0EcN13icalendar_2_011UrlPropTypeEED2Ev@Base
 1.1.0
  
(optional=templinst)_ZN3xsd3cxx4tree30element_serializer_initializerILm0EcN13icalendar_2_012DirParamTypeEED1Ev@Base
 1.1.0
@@ -4407,40 +4409,40 @@
  (optional=templinst|arch=!arm64 !m68k !powerpc !powerpcspe !ppc64 !s390x 

Bug#914145: liborigin2 FTBFS with boost 1.67

2018-11-19 Thread Adrian Bunk
Source: liborigin2
Version: 2:20110117-2
Severity: serious
Tags: ftbfs

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

...
In file included from Origin800Parser.h:32,
 from Origin610Parser.h:32,
 from Origin600Parser.h:32,
 from Origin600Parser.cpp:29:
Origin750Parser.h: In member function 'boost::posix_time::ptime 
Origin750Parser::doubleToPosixTime(double)':
Origin750Parser.h:74:175: error: no matching function for call to 
'boost::posix_time::seconds::seconds(double)'
   return 
boost::posix_time::ptime(boost::gregorian::date(boost::gregorian::gregorian_calendar::from_julian_day_number(jdt+1)),
 boost::posix_time::seconds((jdt-(int)jdt)*86400));


   ^
In file included from 
/usr/include/boost/date_time/posix_time/posix_time_types.hpp:16,
 from 
/usr/include/boost/date_time/posix_time/time_formatters.hpp:16,
 from /usr/include/boost/date_time/posix_time/posix_time.hpp:24,
 from Origin750Parser.h:36,
 from Origin800Parser.h:32,
 from Origin610Parser.h:32,
 from Origin600Parser.h:32,
 from Origin600Parser.cpp:29:
/usr/include/boost/date_time/posix_time/posix_time_duration.hpp:57:16: note: 
candidate: 'template boost::posix_time::seconds::seconds(const T&, 
typename boost::enable_if >::type*)'
   explicit seconds(T const& s,
^~~
/usr/include/boost/date_time/posix_time/posix_time_duration.hpp:57:16: note:   
template argument deduction/substitution failed:
/usr/include/boost/date_time/posix_time/posix_time_duration.hpp: In 
substitution of 'template boost::posix_time::seconds::seconds(const 
T&, typename boost::enable_if >::type*) [with T = 
double]':
Origin750Parser.h:74:175:   required from here
/usr/include/boost/date_time/posix_time/posix_time_duration.hpp:57:16: error: 
no type named 'type' in 'struct boost::enable_if, 
void>'
/usr/include/boost/date_time/posix_time/posix_time_duration.hpp:53:30: note: 
candidate: 'boost::posix_time::seconds::seconds(const 
boost::posix_time::seconds&)'
   class BOOST_SYMBOL_VISIBLE seconds : public time_duration
  ^~~
/usr/include/boost/date_time/posix_time/posix_time_duration.hpp:53:30: note:   
no known conversion for argument 1 from 'double' to 'const 
boost::posix_time::seconds&'
/usr/include/boost/date_time/posix_time/posix_time_duration.hpp:53:30: note: 
candidate: 'boost::posix_time::seconds::seconds(boost::posix_time::seconds&&)'
/usr/include/boost/date_time/posix_time/posix_time_duration.hpp:53:30: note:   
no known conversion for argument 1 from 'double' to 
'boost::posix_time::seconds&&'



Bug#914146: dogecoin FTBFS with boost 1.67

2018-11-19 Thread Adrian Bunk
Source: dogecoin
Version: 1.10.0-5
Severity: serious
Tags: ftbfs buster sid

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

...
g++ -DHAVE_CONFIG_H -I. -I../src/config  -I. -I./obj -pthread -I/usr/include 
-I./leveldb/include -I./leveldb/helpers/memenv   -I./secp256k1/include   
-Wdate-time -D_FORTIFY_SOURCE=2 -DBOOST_SPIRIT_THREADSAFE -DHAVE_BUILD_INFO 
-D__STDC_FORMAT_MACROS  -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -Wstack-protector -fstack-protector-all -fPIC -c -o 
libbitcoin_server_a-rpcserver.o `test -f 'rpcserver.cpp' || echo 
'./'`rpcserver.cpp
rpcserver.cpp:507:102: error: wrong number of template arguments (2, should be 
1)
 static void RPCAcceptHandler(boost::shared_ptr< 
basic_socket_acceptor > acceptor,

  ^
In file included from /usr/include/boost/asio.hpp:30,
 from rpcprotocol.h:15,
 from rpcserver.h:10,
 from rpcserver.cpp:6:
/usr/include/boost/asio/basic_socket_acceptor.hpp:73:7: note: provided for 
'template class boost::asio::basic_socket_acceptor'
 class basic_socket_acceptor
   ^
rpcserver.cpp:507:104: error: template argument 1 is invalid
 static void RPCAcceptHandler(boost::shared_ptr< 
basic_socket_acceptor > acceptor,

^
rpcserver.cpp:517:95: error: wrong number of template arguments (2, should be 1)
 static void RPCListen(boost::shared_ptr< basic_socket_acceptor > acceptor,

   ^
In file included from /usr/include/boost/asio.hpp:30,
 from rpcprotocol.h:15,
 from rpcserver.h:10,
 from rpcserver.cpp:6:
/usr/include/boost/asio/basic_socket_acceptor.hpp:73:7: note: provided for 
'template class boost::asio::basic_socket_acceptor'
 class basic_socket_acceptor
   ^
rpcserver.cpp:517:97: error: template argument 1 is invalid
 static void RPCListen(boost::shared_ptr< basic_socket_acceptor > acceptor,

 ^
rpcserver.cpp: In function 'void RPCListen(int, boost::asio::ssl::context&, 
bool)':
rpcserver.cpp:522:109: error: base operand of '->' is not a pointer
 boost::shared_ptr< AcceptedConnectionImpl > conn(new 
AcceptedConnectionImpl(acceptor->get_io_service(), context, fUseSSL));

 ^~
rpcserver.cpp:524:13: error: base operand of '->' is not a pointer
 acceptor->async_accept(
 ^~
rpcserver.cpp: At global scope:
rpcserver.cpp:540:102: error: wrong number of template arguments (2, should be 
1)
 static void RPCAcceptHandler(boost::shared_ptr< 
basic_socket_acceptor > acceptor,

  ^
In file included from /usr/include/boost/asio.hpp:30,
 from rpcprotocol.h:15,
 from rpcserver.h:10,
 from rpcserver.cpp:6:
/usr/include/boost/asio/basic_socket_acceptor.hpp:73:7: note: provided for 
'template class boost::asio::basic_socket_acceptor'
 class basic_socket_acceptor
   ^
rpcserver.cpp:540:104: error: template argument 1 is invalid
 static void RPCAcceptHandler(boost::shared_ptr< 
basic_socket_acceptor > acceptor,

^
rpcserver.cpp: In function 'void RPCAcceptHandler(int, 
boost::asio::ssl::context&, bool, boost::shared_ptr, const 
boost::system::error_code&)':
rpcserver.cpp:547:67: error: base operand of '->' is not a pointer
 if (error != boost::asio::error::operation_aborted && acceptor->is_open())
   ^~
rpcserver.cpp:548:45: error: no matching function for call to 'RPCListen(int&, 
boost::asio::ssl::context&, const bool&)'
 RPCListen(acceptor, context, fUseSSL);
 ^
rpcserver.cpp:517:13: note: candidate: 'template void RPCListen(int, boost::asio::ssl::context&, bool)'
 static void RPCListen(boost::shared_ptr< basic_socket_acceptor > acceptor,
 ^
rpcserver.cpp:517:13: note:   template argument deduction/substitution failed:
rpcserver.cpp:548:45: note:   couldn't deduce template parameter 'Protocol'
 RPCListen(acceptor, context, fUseSSL);
 ^
rpcserver.cpp: In function 'void StartRPCThreads()':
rpcserver.cpp:634:77: error: no matching function for call to 

Bug#914144: odil FTBFS with boost 1.67

2018-11-19 Thread Adrian Bunk
Source: odil
Version: 0.9.2-1
Severity: serious
Tags: ftbfs

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

...
   debian/rules override_dh_install-arch
make[1]: Entering directory '/<>'
dh_install
dh_install: Cannot find (any matches for) 
"usr/lib/python2*/dist-packages/odil/*so" (tried in ., debian/tmp)

dh_install: python-odil missing files: usr/lib/python2*/dist-packages/odil/*so
dh_install: Cannot find (any matches for) 
"usr/lib/python2*/dist-packages/odil/*py" (tried in ., debian/tmp)

dh_install: python-odil missing files: usr/lib/python2*/dist-packages/odil/*py
dh_install: Cannot find (any matches for) 
"usr/lib/python3*/dist-packages/odil/*so" (tried in ., debian/tmp)

dh_install: python3-odil missing files: usr/lib/python3*/dist-packages/odil/*so
dh_install: Cannot find (any matches for) 
"usr/lib/python3*/dist-packages/odil/*py" (tried in ., debian/tmp)

dh_install: python3-odil missing files: usr/lib/python3*/dist-packages/odil/*py
dh_install: missing files, aborting
make[1]: *** [debian/rules:107: override_dh_install-arch] Error 25


The Ubuntu diff seems to contain a fix.



Bug#914143: soundscaperenderer FTBFS on armel/armhf

2018-11-19 Thread Adrian Bunk
Source: soundscaperenderer
Version: 0.5.0~dfsg-1
Severity: serious
Tags: ftbfs

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

...
checking for QT... yes
checking GL/glu.h usability... no
checking GL/glu.h presence... no
checking for GL/glu.h... no
checking OpenGL/glu.h usability... no
checking OpenGL/glu.h presence... no
checking for OpenGL/glu.h... no
checking for library containing gluNewQuadric... no
checking for library containing glSelectBuffer... no
configure: error: --enable-gui (graphical user interface (using Qt)) requested 
but not available!
make: *** [/usr/share/cdbs/1/class/autotools.mk:46: debian/stamp-autotools/qt] 
Error 1


The root cause is that on armel/armhf
Qt5 is compiled with OpenGL ES instead of OpenGL.

Ideally it should be fixed to build and work with OpenGL ES,
but if this is not easily possible only soundscaperenderer-nox
should be built for armel and armhf.



Bug#914142: python-visual FTBFS with boost 1.67

2018-11-19 Thread Adrian Bunk
Source: python-visual
Version: 1:5.12-1.6
Severity: serious
Tags: ftbfs buster sid

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

...
In file included from /<>/./include/util/extent.hpp:9,
 from /<>/./src/core/util/extent.cpp:6:
/<>/./include/util/vector.hpp:10:10: fatal error: 
boost/python/numeric.hpp: No such file or directory
 #include 
  ^~
compilation terminated.
make[2]: *** [Makefile:226: extent.lo] Error 1



Bug#914141: python-escript FTBFS with boost 1.67

2018-11-19 Thread Adrian Bunk
Source: python-escript
Version: 5.2-2
Severity: serious
Tags: ftbfs

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

...
Install file: "debian/tmp2/posix/weipa/py/__init__.pyc" as 
"debian/stage2/esys/weipa/__init__.pyc"
/<>/debian/stage2/bin/run-escript 
/<>/debian/tmp2/scripts/release_sanity.py
Traceback (most recent call last):
  File "/<>/debian/tmp2/scripts/release_sanity.py", line 8, in 

from esys.escript import *
  File "escript/py_src/__init__.py", line 28, in 
from esys.escriptcore.escriptcpp import *
ImportError: /<>/debian/stage2/lib/libescript.so: undefined 
symbol: _ZTVN5boost6python17error_already_setE
scons: *** [dummy] Error 1
scons: building terminated because of errors.

*** Config Summary (see config.log and /lib/buildvars for details) ***
Escript revision 6702
  Install prefix:  /<>/debian/stage2
  Python:  /usr/bin/python2 (Version 2.7.15)
   boost:  /usr (Version 1.67.0)
   numpy:  YES (with headers)
  Solver library:  paso
   Direct solver:  NONE
 domains:  dudley, finley, ripley, speckley
  netcdf:  YES (4 + 3)
   weipa:  YES
  openmp:  YES
gdal:  YES
  pyproj:  YES
   scipy:  YES
silo:  YES

  DISABLED features: boomeramg cppunit cuda debug gmsh gzip lapack mkl mpi papi 
parmetis sympy trilinos umfpack visit
  Treating warnings as errors

WARNING: Cannot import sympy. Symbolic toolbox and nonlinear PDEs will not be 
available.
WARNING: matplotlib not found, will skip some unit tests
WARNING: gmsh not available. Skipping tests usersguide/trapezoid.py 
usersguide/quad.py usersguide/brick.py usersguide/refine.py 
cookbook/example04a.py cookbook/example04b.py cookbook/example05a.py 
cookbook/example05b.py cookbook/example05c.py cookbook/example06.py 
cookbook/example08c.py cookbook/example09m.py cookbook/example09a.py 
cookbook/example10m.py inversion/dc_forward.py!

ERROR: build stopped due to errors

make[1]: *** [debian/rules:61: override_dh_auto_build] Error 2


The Ubuntu diff seems to contain a fix.



Bug#914085: marked as done (soundscaperenderer: failed to cofigure cleanly)

2018-11-19 Thread Debian Bug Tracking System
Your message dated Mon, 19 Nov 2018 21:37:02 +
with message-id 
and subject line Bug#914085: fixed in soundscaperenderer 0.5.0~dfsg-2
has caused the Debian Bug report #914085,
regarding soundscaperenderer: failed to cofigure cleanly
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.)


-- 
914085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914085
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: soundscaperenderer
Version: 0.5.0~dfsg-1
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

While upgrading from 0.4.2~dfsg-7 to 0.5.0~dfsg-1, I get the following error:


Setting up soundscaperenderer (0.5.0~dfsg-1) ...
update-alternatives: error: alternative path /usr/bin/ssr-nfc-hoa.qt doesn't 
exist
dpkg: error processing package soundscaperenderer (--configure):
 installed soundscaperenderer package post-installation script subprocess 
returned error exit status 2
Errors were encountered while processing:
 soundscaperenderer
 
Regards

Jean-Luc

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

Kernel: Linux 4.20.0-rc2-i7-0.1 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages soundscaperenderer depends on:
ii  jackd 5
ii  libc6 2.27-8
ii  libecasoundc1v5   2.9.1-7+b3
ii  libfftw3-single3  3.3.8-2
ii  libgcc1   1:8.2.0-9
ii  libgl11.1.0-1
ii  libglu1-mesa [libglu1]9.0.0-2.1
ii  libjack-jackd2-0 [libjack-0.125]  1.9.12~dfsg-2
ii  libqt5core5a  5.11.2+dfsg-7
ii  libqt5gui55.11.2+dfsg-7
ii  libqt5opengl5 5.11.2+dfsg-7
ii  libqt5widgets55.11.2+dfsg-7
ii  libsndfile1   1.0.28-4
ii  libstdc++68.2.0-9
ii  libxml2   2.9.8+dfsg-1
ii  soundscaperenderer-common 0.5.0~dfsg-1

Versions of packages soundscaperenderer recommends:
ii  ecasound  2.9.1-7+b3

soundscaperenderer suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iF0EARECAB0WIQT5el3FKLtmYO4UlQtR0YZfPMac0AUCW/JubgAKCRBR0YZfPMac
0JwNAKCVnrR7Ou1ZWaauTYe8onanljN+UACfX7e/Mk5gbNbcvWVg2IrCC2WgMgE=
=V9iH
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: soundscaperenderer
Source-Version: 0.5.0~dfsg-2

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

Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated 
soundscaperenderer package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 19 Nov 2018 21:08:02 +0100
Source: soundscaperenderer
Binary: soundscaperenderer-nox soundscaperenderer soundscaperenderer-common
Architecture: source
Version: 0.5.0~dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: IOhannes m zmölnig (Debian/GNU) 
Description:
 soundscaperenderer - tool for real-time spatial audio reproduction
 soundscaperenderer-common - tool for real-time spatial audio reproduction 
(common-files)
 soundscaperenderer-nox - tool for real-time spatial audio reproduction 
(without X support)
Closes: 914085
Changes:
 soundscaperenderer (0.5.0~dfsg-2) unstable; urgency=medium
 .
   * Centralize the update-alternative handling (Closes: #914085)
   * B-D on libqt5opengl5-desktop-dev
   * Build and install documentation
   * Added description to ssr-dca manpage
   * Updated d/copyright
 * Refreshed d/copyright_hints
Checksums-Sha1:
 10a6264b148d5790da34d5e87221baa64472871b 2527 

Bug#911276: marked as done (elfutils: ftbfs on arm64 with gcc-8)

2018-11-19 Thread Debian Bug Tracking System
Your message dated Mon, 19 Nov 2018 21:35:34 +
with message-id 
and subject line Bug#911276: fixed in elfutils 0.175-1
has caused the Debian Bug report #911276,
regarding elfutils: ftbfs on arm64 with gcc-8
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.)


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

Dear Maintainer,

elfutils ftbfs on sid on arm64 currently. Current git passes, and git
bisect and logic point to the following upstream commit as fixing it:

commit f881459ffc95b6fad51aa055a158ee14814073aa
Author: Mark Wielaard 
Date:   Wed Apr 11 10:37:45 2018 +0200

aarch64: Add default cfi rule to restore SP from CFA address.

The CFA is set by default to the stack pointer of the previous frame.
So that is also how we can always restore the SP. This default aarch64
CFI rule is necessary on Fedora 28 with GCC8 to make the run-deleted.sh
and run-backtrace-dwarf.sh testcases work.

Signed-off-by: Mark Wielaard 

so this bug can be closed either with an upstream update (this patch is
in 0.171) or a cherry pick of the above commit.

Cheers,
mwh

-- System Information:
Debian Release: buster/sid
  APT prefers bionic-updates
  APT policy: (500, 'bionic-updates'), (500, 'bionic-security'), (500, 
'bionic'), (400, 'bionic-proposed'), (100, 'bionic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.15.0-36-generic (SMP w/4 CPU cores)
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: elfutils
Source-Version: 0.175-1

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

Debian distribution maintenance software
pp.
Kurt Roeckx  (supplier of updated elfutils package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 18 Nov 2018 23:01:23 +0100
Source: elfutils
Binary: elfutils libelf1 libelf-dev libdw-dev libdw1 libasm1 libasm-dev
Architecture: source
Version: 0.175-1
Distribution: unstable
Urgency: medium
Maintainer: Kurt Roeckx 
Changed-By: Kurt Roeckx 
Description:
 elfutils   - collection of utilities to handle ELF objects
 libasm-dev - libasm development libraries and header files
 libasm1- library with a programmable assembler interface
 libdw-dev  - libdw1 development libraries and header files
 libdw1 - library that provides access to the DWARF debug information
 libelf-dev - libelf1 development libraries and header files
 libelf1- library to read and write ELF files
Closes: 907562 911083 911276 911413 911414
Changes:
 elfutils (0.175-1) unstable; urgency=medium
 .
   * New upstream release
 - Build with gcc-8 (Closes: #911276)
 - Drop fix-gcc7-ftbfs.diff
 - Drop GNU_variable_value.patch
 - Drop locviews.patch
 - Update patches
   * Fixes CVE-2018-18521 (Closes: #911413)
   * Fixes CVE-2018-18520 (Closes: #911414)
   * Fixes CVE-2018-18310 (Closes: #911083)
   * Fixes CVE-2018-16403
   * Fixes CVE-2018-16402
   * Fixes CVE-2018-16062 (Closes: #907562)
Checksums-Sha1:
 a68e892c7347f0fe49158e9818e57607cb38c7c5 2568 elfutils_0.175-1.dsc
 361f835640ecffddc6d4543fb044eb53f673026f 8786600 elfutils_0.175.orig.tar.bz2
 a15f78114cad1c7dbe41b2c5710105563b83c481 488 elfutils_0.175.orig.tar.bz2.asc
 28eab328d1e8d8df41b13d9567c9d707dd5901d3 37404 elfutils_0.175-1.debian.tar.xz
 57e40bb1e428465522056af1907d7078559fc83e 8034 elfutils_0.175-1_source.buildinfo
Checksums-Sha256:
 32e42db07fa6c55697db27fb049b327b8bcee95e326c8b64498671dc9f3851ba 2568 
elfutils_0.175-1.dsc
 f7ef925541ee32c6d15ae5cb27da5f119e01a5ccdbe9fe57bf836730d7b7a65b 8786600 
elfutils_0.175.orig.tar.bz2
 103ae1a12d0b67e2d783f36dc780acd533d5c2a9d6241bcd62cfe1f6fa891a16 488 

Bug#911627: python-openflow: diff for NMU version 2017.2b1+dfsg-2.1

2018-11-19 Thread Adrian Bunk
Control: tags 911627 + patch
Control: tags 911627 + pending

Dear maintainer,

I've prepared an NMU for python-openflow (versioned as 2017.2b1+dfsg-2.1)
and uploaded it to DELAYED/14. Please feel free to tell me if I should 
cancel it.

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 python-openflow-2017.2b1+dfsg/debian/changelog python-openflow-2017.2b1+dfsg/debian/changelog
--- python-openflow-2017.2b1+dfsg/debian/changelog	2017-11-13 19:03:47.0 +0200
+++ python-openflow-2017.2b1+dfsg/debian/changelog	2018-11-19 23:29:35.0 +0200
@@ -1,3 +1,11 @@
+python-openflow (2017.2b1+dfsg-2.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Upstream requires Python 3.6, correct the dependencies
+accordingly to fix upgrades from stretch. (Closes: #911627)
+
+ -- Adrian Bunk   Mon, 19 Nov 2018 23:29:35 +0200
+
 python-openflow (2017.2b1+dfsg-2) unstable; urgency=medium
 
   * New upload because the bug #877191 was solved.
diff -Nru python-openflow-2017.2b1+dfsg/debian/control python-openflow-2017.2b1+dfsg/debian/control
--- python-openflow-2017.2b1+dfsg/debian/control	2017-11-13 19:03:47.0 +0200
+++ python-openflow-2017.2b1+dfsg/debian/control	2018-11-19 23:29:28.0 +0200
@@ -4,10 +4,9 @@
 Maintainer: Paulo Henrique de Lima Santana (phls) 
 Build-Depends: debhelper (>= 10),
dh-python,
-   python3.6,
-   python3-all,
+   python3-all (>= 3.6),
python3-setuptools
-X-Python3-Version: >= 3.5
+X-Python3-Version: >= 3.6
 Standards-Version: 4.1.1
 Homepage: https://github.com/kytos/python-openflow
 


Bug#914140: pytango FTBFS with boost 1.67

2018-11-19 Thread Adrian Bunk
Source: pytango
Version: 9.2.4-2
Severity: serious
Tags: ftbfs

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

...
x86_64-linux-gnu-g++ -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions 
-Wl,-z,relro -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall 
-Wstrict-prototypes -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-fdebug-prefix-map=/build/python2.7-A8UpPM/python2.7-2.7.15=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
build/temp.linux-amd64-2.7/<>/ext/api_util.o 
build/temp.linux-amd64-2.7/<>/ext/archive_event_info.o 
build/temp.linux-amd64-2.7/<>/ext/attr_conf_event_data.o 
build/temp.linux-amd64-2.7/<>/ext/attribute_alarm_info.o 
build/temp.linux-amd64-2.7/<>/ext/attribute_dimension.o 
build/temp.linux-amd64-2.7/<>/ext/attribute_event_info.o 
build/temp.linux-amd64-2.7/<>/ext/attribute_info.o 
build/temp.linux-amd64-2.7/<>/ext/attribute_info_ex.o 
build/temp.linux-amd64-2.7/<>/ext/attribute_proxy.o 
build/temp.linux-amd64-2.7/<>/ext/base_types.o 
build/temp.linux-amd64-2.7/<>/ext/callback.o 
build/temp.linux-amd64-2.7/<>/ext/change_event_info.o 
build/temp.linux-amd64-2.7/<>/ext/command_info.o 
build/temp.linux-amd64-2.7/<>/ext/connection.o 
build/temp.linux-amd64-2.7/<>/ext/constants.o 
build/temp.linux-amd64-2.7/<>/ext/data_ready_event_data.o 
build/temp.linux-amd64-2.7/<>/ext/database.o 
build/temp.linux-amd64-2.7/<>/ext/db.o 
build/temp.linux-amd64-2.7/<>/ext/dev_command_info.o 
build/temp.linux-amd64-2.7/<>/ext/dev_error.o 
build/temp.linux-amd64-2.7/<>/ext/device_attribute.o 
build/temp.linux-amd64-2.7/<>/ext/device_attribute_config.o 
build/temp.linux-amd64-2.7/<>/ext/device_attribute_history.o 
build/temp.linux-amd64-2.7/<>/ext/device_data.o 
build/temp.linux-amd64-2.7/<>/ext/device_data_history.o 
build/temp.linux-amd64-2.7/<>/ext/device_info.o 
build/temp.linux-amd64-2.7/<>/ext/device_pipe.o 
build/temp.linux-amd64-2.7/<>/ext/device_proxy.o 
build/temp.linux-amd64-2.7/<>/ext/devintr_change_event_data.o 
build/temp.linux-amd64-2.7/<>/ext/enums.o 
build/temp.linux-amd64-2.7/<>/ext/event_data.o 
build/temp.linux-amd64-2.7/<>/ext/exception.o 
build/temp.linux-amd64-2.7/<>/ext/from_py.o 
build/temp.linux-amd64-2.7/<>/ext/group.o 
build/temp.linux-amd64-2.7/<>/ext/group_reply.o 
build/temp.linux-amd64-2.7/<>/ext/group_reply_list.o 
build/temp.linux-amd64-2.7/<>/ext/locker_info.o 
build/temp.linux-amd64-2.7/<>/ext/locking_thread.o 
build/temp.linux-amd64-2.7/<>/ext/periodic_event_info.o 
build/temp.linux-amd64-2.7/<>/ext/pipe_event_data.o 
build/temp.linux-amd64-2.7/<>/ext/pipe_info.o 
build/temp.linux-amd64-2.7/<>/ext/poll_device.o 
build/temp.linux-amd64-2.7/<>/ext/precompiled_header.o 
build/temp.linux-amd64-2.7/<>/ext/pytango.o 
build/temp.linux-amd64-2.7/<>/ext/pytgutils.o 
build/temp.linux-amd64-2.7/<>/ext/pyutils.o 
build/temp.linux-amd64-2.7/<>/ext/time_val.o 
build/temp.linux-amd64-2.7/<>/ext/to_py.o 
build/temp.linux-amd64-2.7/<>/ext/version.o 
build/temp.linux-amd64-2.7/<>/ext/server/attr.o 
build/temp.linux-amd64-2.7/<>/ext/server/attribute.o 
build/temp.linux-amd64-2.7/<>/ext/server/auto_monitor.o 
build/temp.linux-amd64-2.7/<>/ext/server/command.o 
build/temp.linux-amd64-2.7/<>/ext/server/device_class.o 
build/temp.linux-amd64-2.7/<>/ext/server/device_impl.o 
build/temp.linux-amd64-2.7/<>/ext/server/dserver.o 
build/temp.linux-amd64-2.7/<>/ext/server/encoded_attribute.o 
build/temp.linux-amd64-2.7/<>/ext/server/fwdAttr.o 
build/temp.linux-amd64-2.7/<>/ext/server/log4tango.o 
build/temp.linux-amd64-2.7/<>/ext/server/multi_attribute.o 
build/temp.linux-amd64-2.7/<>/ext/server/multi_class_attribute.o 
build/temp.linux-amd64-2.7/<>/ext/server/pipe.o 
build/temp.linux-amd64-2.7/<>/ext/server/subdev.o 
build/temp.linux-amd64-2.7/<>/ext/server/tango_util.o 
build/temp.linux-amd64-2.7/<>/ext/server/user_default_attr_prop.o 
build/temp.linux-amd64-2.7/<>/ext/server/user_default_pipe_prop.o 
build/temp.linux-amd64-2.7/<>/ext/server/wattribute.o 
-l:libtango.so.9 -lboost_python-py27 -ltango -lomniDynamic4 -lCOS4 -lomniORB4 
-lomnithread -llog4tango -lzmq -o 
/<>/.pybuild/cpython2_2.7_tango/build/tango/_tango.so
/usr/bin/ld: cannot find -lboost_python-py27
collect2: error: ld returned 1 exit status
error: command 'x86_64-linux-gnu-g++' failed with exit status 1
E: pybuild pybuild:338: build: plugin distutils failed with: exit code=1: 
/usr/bin/python setup.py build 
dh_auto_build: pybuild --build -i python{version} -p 2.7 returned exit code 13
make: *** [debian/rules:7: binary-arch] Error 25


The Ubuntu diff seems to contain a fix.



Processed: python-openflow: diff for NMU version 2017.2b1+dfsg-2.1

2018-11-19 Thread Debian Bug Tracking System
Processing control commands:

> tags 911627 + patch
Bug #911627 [python3-openflow] python3-openflow: fails to upgrade from 
'stretch': SyntaxError: invalid syntax
Added tag(s) patch.
> tags 911627 + pending
Bug #911627 [python3-openflow] python3-openflow: fails to upgrade from 
'stretch': SyntaxError: invalid syntax
Added tag(s) pending.

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



Processed: fixed 911590 in 20170907-3

2018-11-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> fixed 911590 20170907-3
Bug #911590 [gocode-auto-complete-el] gocode-auto-complete-el: fails to 
install: go-autocomplete.el:39:13:Error: Cannot open load file: No such file or 
directory, auto-complete
Marked as fixed in versions gocode/20170907-3.
> thanks
Stopping processing here.

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



Processed: merging 912151 914101

2018-11-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> merge 912151 914101
Bug #912151 [src:gtimelog] gtimelog: missing build dependency on python3-cairo
Bug #914101 [src:gtimelog] FTBFS: Missing build-dependency against pycairo
Marked as found in versions gtimelog/0.11.1-1.
Added tag(s) ftbfs.
Bug #912151 [src:gtimelog] gtimelog: missing build dependency on python3-cairo
Marked as found in versions gtimelog/0.11.1-2.
Merged 912151 914101
> thanks
Stopping processing here.

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



Bug#911154: Bug#912120: Bug#911154: netkit-ntalk misses the generator for configure

2018-11-19 Thread Adrian Bunk
On Mon, Nov 05, 2018 at 08:01:21AM +0100, Christoph Biedl wrote:
>...
> Switching to e.g. cmake means a one-time more-or-less complex manual
> transition but afterwards the packaging should be in a sane state for
> quite some time.
> 
> After thinking about this for a few days I agree this is the sanest way
> to go. For the current build system, there are already some extra
> kludges (check out debian/rules if you really want to), and setting up a
> confgen emulation, probably as a debhelper extension ... while this was
> a faszinating project, it would certainly eat up some ressources to set
> up and to maintain. Also, since confgen upstream (see below) described
> the program as a hack and I subscribe to that point of view, it's
> really better to look forward, even for these old packages.
> 
> Still I assume this will be my job - however, the changes will go
> beyond a sound NMU size. So I'll send out patches, and eventually go
> the package salvaging way.
>...

Any update on that?

I might provide fixes for some packages otherwise, but these would be 
autotools conversions since that's the tools I know best.

> Cheers,
> Christoph
>...

cu
Adrian

-- 

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



Bug#913909: [Ceph-maintainers] Bug#913909: Bug#913909: ceph: FTBFS on i386 and mipsel (regression)

2018-11-19 Thread Gaudenz Steinlin

Hi

Salvatore Bonaccorso  writes:

Hi Gaudenz, and hi James, 

On Mon, Nov 19, 2018 at 03:48:14PM +0100, Gaudenz Steinlin 
wrote: 
James Page  writes: 
> https://git.launchpad.net/~ubuntu-server-dev/ubuntu/+source/ceph/tree/debian/patches?h=ubuntu/xenial 
> I think I hit the same issue in Ubuntu a while back for which 
> I picked 3 rocksdb patches - see above URL - 000*.patch. 
 Thanks James. It looks like these patches actually fix the 
build issue.  I already had these patches applied to the build 
in unstable, but I did not make the connection to the infinite 
loop.   Salvatore, do you agree to an upload of 10.2.11-2 with 
these patches to stretch-security? Or how should we proceed? 


Yes we should release a regression update for ceph via 
stretch-security. 


Can you ping us when you have it ready?


I'm currently building a new fixed version (10.2.11-2). Should I 
just upload to stretch-security or do you want to have a look at 
it first?


I attached the debdiff to the previous stretch-security upload.

Gaudenz



ceph_10.2.11-1to2.debdiff
Description: Binary data

>
> Regards,
> Salvatore
>
-- 
PGP: 836E 4F81 EFBB ADA7 0852 79BF A97A 7702 BAF9 1EF5


Processed: fixed 885345 in 10.1.37-0+deb9u1, fixed 898444 in 10.1.37-0+deb9u1, fixed 898445 in 10.1.37-0+deb9u1 ...

2018-11-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> fixed 885345 10.1.37-0+deb9u1
Bug #885345 {Done: Salvatore Bonaccorso } [src:mariadb-10.1] 
mariadb-10.1: CVE-2017-15365: Replication in sql/event_data_objects.cc occurs 
before ACL checks
The source 'mariadb-10.1' and version '10.1.37-0+deb9u1' do not appear to match 
any binary packages
Marked as fixed in versions mariadb-10.1/10.1.37-0+deb9u1.
> fixed 898444 10.1.37-0+deb9u1
Bug #898444 {Done: Salvatore Bonaccorso } [src:mariadb-10.1] 
mariadb-10.1: CVE-2018-2562 CVE-2018-2622 CVE-2018-2640 CVE-2018-2665 
CVE-2018-2668 CVE-2018-2612 (fixed in 10.1.31)
The source 'mariadb-10.1' and version '10.1.37-0+deb9u1' do not appear to match 
any binary packages
Marked as fixed in versions mariadb-10.1/10.1.37-0+deb9u1.
> fixed 898445 10.1.37-0+deb9u1
Bug #898445 {Done: Salvatore Bonaccorso } [src:mariadb-10.1] 
mariadb-10.1: CVE-2018-2782 CVE-2018-2784 CVE-2018-2787 CVE-2018-2766 
CVE-2018-2755 CVE-2018-2819 CVE-2018-2817 CVE-2018-2761 CVE-2018-2781 
CVE-2018-2771 CVE-2018-2813 (fixed in 10.1.33)
The source 'mariadb-10.1' and version '10.1.37-0+deb9u1' do not appear to match 
any binary packages
Marked as fixed in versions mariadb-10.1/10.1.37-0+deb9u1.
> fixed 912848 10.1.37-0+deb9u1
Bug #912848 [src:mariadb-10.1] mariadb-10.1: CVE-2018-3282 CVE-2018-3174 
CVE-2018-3143 CVE-2018-3156 CVE-2018-3251
The source 'mariadb-10.1' and version '10.1.37-0+deb9u1' do not appear to match 
any binary packages
Marked as fixed in versions mariadb-10.1/10.1.37-0+deb9u1.
> thanks
Stopping processing here.

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



Bug#904111: clamav-daemon causing deadlocks/blocking I/O

2018-11-19 Thread Sebastian Andrzej Siewior
On 2018-11-12 10:17:32 [-0800], Adam Lambert wrote:
> I believe I already supplied all that way back when I opened up this bug
> report.   But for reference, here it is again:

I tried it back then with no luck. Thanks for the info. I will try to
reproduce this asap and get back to you.

Sebastian



Processed: fixed in the new version qbittorrent 4.1.3-1+b1

2018-11-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> fixed 913953 4.1.3-1+b1
Bug #913953 [qbittorrent] qbittorrent crashes when starting talks of symbol 
lookup error
Marked as fixed in versions qbittorrent/4.1.3-1.
> thanks
Stopping processing here.

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



Bug#913953: fixed in the new version qbittorrent 4.1.3-1+b1

2018-11-19 Thread shirish शिरीष
fixed 913953 4.1.3-1+b1
thanks



Bug#897348: synaptic still broken

2018-11-19 Thread ael
I have had this same problem for months. It would be nice to be able to
use synaptics again. Have I missed the response to this bug?

The problem is launching from CLI root terminal which used to work.
I *can* launch from a GUI menu, but that is overcomplicated for simple
things.

Running current debian testing.
4.18.0-2-amd64 #1 SMP Debian 4.18.10-2 (2018-11-02) x86_64 GNU/Linux

Package: synaptic
Status: install ok installed
Priority: optional
Section: admin
Installed-Size: 7810
Maintainer: Michael Vogt 
Architecture: amd64
Version: 0.84.5

ael



Bug#790584: gjots2: depends on python-gnome2 which is deprecated

2018-11-19 Thread Jeremy Bicha
On Sat, Oct 13, 2018 at 2:39 PM Jeremy Bicha  wrote:
> gjots2 is now one of the last 3 packages in Debian depending on the
> unmaintained gnome-python libraries.
>
> Please either upgrade gjots2 to the new version or request that gjots2
> be removed from Debian.

Could you be more specific about what exact bugs in the new gjots
version are still blocking your upload?

If I don't hear from you, I guess I'll try to do an NMU of the new version.

By my calculations, gjots2 is 1 of the last 4 packages preventing
libgnome's removal from Debian. Other packages that were blocking the
removal have been removed from Debian, but that seems a bit
unnecessary here if this issue has already been fixed in a version we
could update to.

Thanks,
Jeremy Bicha



Bug#913507: Should be solved by new upstream version

2018-11-19 Thread Christoph Egger
Hi all

I put a new upstream release on salsa which seems to fix it. I'll upload as 
soon as I find my GPG key (hope I didn't leave it at home), but feel free to 
upload the version from salsa if you're faster

  Christoph

[0] https://salsa.debian.org/debian/ncmpcpp/tree/master/debian

smime.p7s
Description: S/MIME cryptographic signature


Processed: Re: thawab: depends on gir1.2-webkit-3.0 which is deprecated

2018-11-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> block 893863 by 866653
Bug #893863 [ftp.debian.org] RM: webkitgtk -- RoM; RoQA; unmaintained, over 100 
CVEs that won't be fixed
893863 was blocked by: 790221 893768 905695 893860 893864 790204 893870 893861
893863 was not blocking any bugs.
Added blocking bug(s) of 893863: 866653
>
End of message, stopping processing here.

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



Processed: Re: gitlab-ci-multi-runner: FTBFS with golang-github-prometheus-client-golang/0.9.0-1

2018-11-19 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + patch
Bug #911437 [src:gitlab-ci-multi-runner] gitlab-ci-multi-runner: FTBFS with 
golang-github-prometheus-client-golang/0.9.0-1
Added tag(s) patch.

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



Bug#911437: gitlab-ci-multi-runner: FTBFS with golang-github-prometheus-client-golang/0.9.0-1

2018-11-19 Thread Andreas Henriksson
Control: tags -1 + patch

Hello Dmitry Smirnov,

It seems you've forgot to push upstream/pristine-tar branches
and tags when you did the last update/upload of the package.
Could you please push them?

I'm attaching a patch to fix the FTBFS bug that seems to have
just gotten this package removed from testing.

Original bug report quoted below for your convenience.

Regards,
Andreas Henriksson


On Sat, Oct 20, 2018 at 03:19:38PM +0800, Shengjing Zhu wrote:
> Source: gitlab-ci-multi-runner
> Version: 11.2.0+dfsg-1
> Severity: serious
> Tags: ftbfs
> 
> Dear Maintainer,
> 
> When rebuild gitlab-ci-multi-runner, it FTBFS,
> 
> # gitlab.com/gitlab-org/gitlab-runner/commands
> src/gitlab.com/gitlab-org/gitlab-runner/commands/multi.go:365:54: too
> many arguments in call to
> "github.com/prometheus/client_golang/prometheus".NewProcessCollector
> have (int, string)
> want 
> ("github.com/prometheus/client_golang/prometheus".ProcessCollectorOpts)
> 
> 
> -- 
> Shengjing Zhu
> 
>From 4356d8d0ebe85391c3882a971a03e3677e70598a Mon Sep 17 00:00:00 2001
From: Andreas Henriksson 
Date: Mon, 19 Nov 2018 19:17:49 +0100
Subject: [PATCH 1/2] Add debian/patches/fix-ftbfs-911437.patch

Closes: #911437
---
 debian/patches/fix-ftbfs-911437.patch | 17 +
 debian/patches/series |  1 +
 2 files changed, 18 insertions(+)
 create mode 100644 debian/patches/fix-ftbfs-911437.patch

diff --git a/debian/patches/fix-ftbfs-911437.patch b/debian/patches/fix-ftbfs-911437.patch
new file mode 100644
index 000..bbe9acc
--- /dev/null
+++ b/debian/patches/fix-ftbfs-911437.patch
@@ -0,0 +1,17 @@
+--- a/commands/multi.go
 b/commands/multi.go
+@@ -362,7 +362,13 @@
+ 	// Go-specific metrics about the process (GC stats, goroutines, etc.).
+ 	registry.MustRegister(prometheus.NewGoCollector())
+ 	// Go-unrelated process metrics (memory usage, file descriptors, etc.).
+-	registry.MustRegister(prometheus.NewProcessCollector(os.Getpid(), ""))
++	registry.MustRegister(prometheus.NewProcessCollector(prometheus.ProcessCollectorOpts{
++		PidFn: func() (int, error) {
++			p := os.Getpid()
++			return p, nil
++		},
++		Namespace: "",
++	}))
+ 
+ 	// Register all executor provider collectors
+ 	for _, provider := range common.GetExecutorProviders() {
diff --git a/debian/patches/series b/debian/patches/series
index a684cc5..282e0a6 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -14,3 +14,4 @@ test--TestMachinePreCreateMode.patch
 test--TestDockerCommandMissing.patch
 test--git.patch
 test--tmp-docker.patch
+fix-ftbfs-911437.patch
-- 
2.19.1



Processed: Re: ln: failed to create symbolic link '/sbin/iptables': File exists

2018-11-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forcemerge 914074 914129
Bug #914074 [iptables] ln: failed to create symbolic link '/sbin/iptables': 
File exists
Bug #914129 [iptables] Report bug: Iptables on Sid
Severity set to 'serious' from 'normal'
Marked as found in versions iptables/1.8.2-1.
Merged 914074 914129
> thanks
Stopping processing here.

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



Bug#873501: kivy FTBFS with Cython 0.26

2018-11-19 Thread Dean Serenevy

I've rebased a minimal patch to fix the buld errors to apply on top of the 
latest salsa master (d3fa496) fixing the FTBFS.

   See attached patch, or forked repo at: 
https://github.com/duelafn/deb-kivy-873501

The new kivy (1.10) will close #873501, #774052, #799833, #849090.

Is there anything else I can do to help get kivy back in the repository?


Thanks,
  Dean Serenevy
From 33ee413f7d3b5c4eae6b181690e8dc3163835a2d Mon Sep 17 00:00:00 2001
From: Dean Serenevy 
Date: Mon, 19 Nov 2018 10:01:06 -0500
Subject: [PATCH] Fix FTBFS ("local changes detected")

---
 debian/changelog   |  5 -
 ...revent-local-changes-detected-build-error.patch | 25 ++
 debian/patches/series  |  1 +
 3 files changed, 30 insertions(+), 1 deletion(-)
 create mode 100644 debian/patches/0001-prevent-local-changes-detected-build-error.patch
 create mode 100644 debian/patches/series

diff --git a/debian/changelog b/debian/changelog
index 55edeb0..829c6d9 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -16,7 +16,10 @@ kivy (1.10.1-1) UNRELEASED; urgency=medium
   * d/control: Remove ancient X-Python3-Version field
   * Convert git repository from git-dpm to gbp layout
   * d/changelog: Remove trailing whitespaces
- 
+
+  [ Dean Serenevy ]
+  * Add debian/patches/0001-prevent-local-changes-detected-build-error.patch
+to fix errors building v1.10 (Closes: #873501, #774052, #799833)
 
  -- Manas Kashyap   Sat, 13 Oct 2018 07:49:44 +
 
diff --git a/debian/patches/0001-prevent-local-changes-detected-build-error.patch b/debian/patches/0001-prevent-local-changes-detected-build-error.patch
new file mode 100644
index 000..6babb67
--- /dev/null
+++ b/debian/patches/0001-prevent-local-changes-detected-build-error.patch
@@ -0,0 +1,25 @@
+From: Dean Serenevy 
+Date: Mon, 19 Nov 2018 09:49:15 -0500
+Subject: prevent "local changes detected" build error
+
+---
+ setup.py | 6 --
+ 1 file changed, 6 deletions(-)
+
+diff --git a/setup.py b/setup.py
+index 0c3e2e4..702e662 100644
+--- a/setup.py
 b/setup.py
+@@ -65,12 +65,6 @@ def get_version(filename='kivy/version.py'):
+ "__date__ = '%(date)s'\n"
+ )
+ 
+-with open(filename, 'w') as f:
+-f.write(cnt % {
+-'version': VERSION,
+-'hash': GIT_REVISION,
+-'date': DATE
+-})
+ return VERSION
+ 
+ 
diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 000..2664ec3
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+0001-prevent-local-changes-detected-build-error.patch
-- 
2.11.0



signature.asc
Description: OpenPGP digital signature


Bug#914074: ln: failed to create symbolic link '/sbin/iptables': File exists

2018-11-19 Thread Chris Lamb
forcemerge 914074 914129
thanks

I believe this is a duplicate of:

  https://bugs.debian.org/914074

(Please continue any discussion there.)


Regards,

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



Bug#912216: syndie: Depends on swt-gtk which will be removed soon

2018-11-19 Thread Jeremy Bicha
Control: tags -1 +patch

I proposed
https://salsa.debian.org/debian/syndie/merge_requests/1

Thanks,
Jeremy Bicha



Processed: Re: syndie: Depends on swt-gtk which will be removed soon

2018-11-19 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 +patch
Bug #912216 [src:syndie] syndie: Depends on swt-gtk which will be removed soon
Added tag(s) patch.

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



Processed: RM: ekiga -- RoQA; unmaintained, depends on ptlib whihch depends on openssl1.0

2018-11-19 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 normal
Bug #911593 [src:ekiga] ekiga: Intent to remove from Debian
Severity set to 'normal' from 'serious'
> tags -1 -sid -buster
Bug #911593 [src:ekiga] ekiga: Intent to remove from Debian
Ignoring request to alter tags of bug #911593 to the same tags previously set
Bug #911593 [src:ekiga] ekiga: Intent to remove from Debian
Ignoring request to alter tags of bug #911593 to the same tags previously set
> retitle -1 RM: ekiga -- RoQA; unmaintained, depends on ptlib whihch depends 
> on openssl1.0
Bug #911593 [src:ekiga] ekiga: Intent to remove from Debian
Changed Bug title to 'RM: ekiga -- RoQA; unmaintained, depends on ptlib whihch 
depends on openssl1.0' from 'ekiga: Intent to remove from Debian'.
> reassign -1 ftp.debian.org
Bug #911593 [src:ekiga] RM: ekiga -- RoQA; unmaintained, depends on ptlib 
whihch depends on openssl1.0
Bug reassigned from package 'src:ekiga' to 'ftp.debian.org'.
No longer marked as found in versions ekiga/4.0.1-9.
Ignoring request to alter fixed versions of bug #911593 to the same values 
previously set

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



Bug#911593: RM: ekiga -- RoQA; unmaintained, depends on ptlib whihch depends on openssl1.0

2018-11-19 Thread Jeremy Bicha
Control: severity -1 normal
Control: tags -1 -sid -buster
Control: retitle -1 RM: ekiga -- RoQA; unmaintained, depends on ptlib whihch 
depends on openssl1.0
Control: reassign -1 ftp.debian.org

Please remove ekiga from Debian.

On behalf of the Debian GNOME team,
Jeremy Bicha



Processed: Bug #913601 in ceph marked as pending

2018-11-19 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #913601 [src:ceph] ceph: FTBFS on mips/el: 
/usr/include/c++/8/bits/atomic_base.h:304: undefined reference to 
`__atomic_fetch_sub_8'
Ignoring request to alter tags of bug #913601 to the same tags previously set

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



Bug#913601: Bug #913601 in ceph marked as pending

2018-11-19 Thread Gaudenz Steinlin
Control: tag -1 pending

Hello,

Bug #913601 in ceph reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/ceph-team/ceph/commit/29b7ac56db9d7f52c81e8f3a5c75234f14ae83a9


Patch to check for atomic support during build

Instead of building with -Wl,--as-needed -latomic an all architectures,
this dynamically detects the need for linking against libatomic. This is
cleaner.

The previous approach of setting the linker flags with
DEB_LDFLAGS_MAINT_APPEND added the flags to early on the command line so
that not all objects were linked against libatomic. This lead to build
failures on at least mips and mipsel.

Closes: #913601



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/913601



Processed: RM: t38modem -- RoQA; unmaintained, depends on ptlib which depends on openssl1.0

2018-11-19 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 normal
Bug #911596 [src:t38modem] t38modem: Intent to remove from Debian
Severity set to 'normal' from 'serious'
> tags -1 -sid -buster
Bug #911596 [src:t38modem] t38modem: Intent to remove from Debian
Removed tag(s) sid.
Bug #911596 [src:t38modem] t38modem: Intent to remove from Debian
Removed tag(s) buster.
> retitle -1 RM: t38modem -- RoQA; depends on ptlib which depends on openssl1.0
Bug #911596 [src:t38modem] t38modem: Intent to remove from Debian
Changed Bug title to 'RM: t38modem -- RoQA; depends on ptlib which depends on 
openssl1.0' from 't38modem: Intent to remove from Debian'.
> reassign -1 ftp.debian.org
Bug #911596 [src:t38modem] RM: t38modem -- RoQA; depends on ptlib which depends 
on openssl1.0
Bug reassigned from package 'src:t38modem' to 'ftp.debian.org'.
No longer marked as found in versions t38modem/2.0.0-4.
Ignoring request to alter fixed versions of bug #911596 to the same values 
previously set

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



Bug#911596: RM: t38modem -- RoQA; unmaintained, depends on ptlib which depends on openssl1.0

2018-11-19 Thread Jeremy Bicha
Control: severity -1 normal
Control: tags -1 -sid -buster
Control: retitle -1 RM: t38modem -- RoQA; depends on ptlib which depends on 
openssl1.0
Control: reassign -1 ftp.debian.org

Please remove t38modem from Debian.

Thanks,
Jeremy Bicha



Processed: RM: ptlib -- RoQA; unmaintained, depends on openssl1.0

2018-11-19 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 normal
Bug #911595 [src:ptlib] ptlib: Intent to remove from Debian
Severity set to 'normal' from 'serious'
> tags -1 -sid -buster
Bug #911595 [src:ptlib] ptlib: Intent to remove from Debian
Removed tag(s) sid.
Bug #911595 [src:ptlib] ptlib: Intent to remove from Debian
Removed tag(s) buster.
> retitle -1 RM: ptlib -- RoQA; unmaintained, depends on openssl1.0
Bug #911595 [src:ptlib] ptlib: Intent to remove from Debian
Changed Bug title to 'RM: ptlib -- RoQA; unmaintained, depends on openssl1.0' 
from 'ptlib: Intent to remove from Debian'.
> reassign -1 ftp.debian.org
Bug #911595 [src:ptlib] RM: ptlib -- RoQA; unmaintained, depends on openssl1.0
Bug reassigned from package 'src:ptlib' to 'ftp.debian.org'.
No longer marked as found in versions ptlib/2.10.11~dfsg-2.1.
Ignoring request to alter fixed versions of bug #911595 to the same values 
previously set

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



Processed: RM: opal -- RoQA; unmaintained, depends on ptlib which depends on openssl1.0

2018-11-19 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 normal
Bug #911594 [src:opal] opal: Intent to remove from Debian
Severity set to 'normal' from 'serious'
> tags -1 -sid -buster
Bug #911594 [src:opal] opal: Intent to remove from Debian
Ignoring request to alter tags of bug #911594 to the same tags previously set
Bug #911594 [src:opal] opal: Intent to remove from Debian
Ignoring request to alter tags of bug #911594 to the same tags previously set
> retitle -1 RM: opal -- RoQA; unmaintained, depends on ptlib which depends on 
> openssl1.0
Bug #911594 [src:opal] opal: Intent to remove from Debian
Changed Bug title to 'RM: opal -- RoQA; unmaintained, depends on ptlib which 
depends on openssl1.0' from 'opal: Intent to remove from Debian'.
> reassign -1 ftp.debian.org
Bug #911594 [src:opal] RM: opal -- RoQA; unmaintained, depends on ptlib which 
depends on openssl1.0
Bug reassigned from package 'src:opal' to 'ftp.debian.org'.
No longer marked as found in versions opal/3.10.10~dfsg2-2.1.
Ignoring request to alter fixed versions of bug #911594 to the same values 
previously set

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



Bug#911595: RM: ptlib -- RoQA; unmaintained, depends on openssl1.0

2018-11-19 Thread Jeremy Bicha
Control: severity -1 normal
Control: tags -1 -sid -buster
Control: retitle -1 RM: ptlib -- RoQA; unmaintained, depends on openssl1.0
Control: reassign -1 ftp.debian.org

Please remove ptlib from Debian.

Thanks,
Jeremy Bicha



Bug#911594: RM: opal -- RoQA; unmaintained, depends on ptlib which depends on openssl1.0

2018-11-19 Thread Jeremy Bicha
Control: severity -1 normal
Control: tags -1 -sid -buster
Control: retitle -1 RM: opal -- RoQA; unmaintained, depends on ptlib which 
depends on openssl1.0
Control: reassign -1 ftp.debian.org

Please remove opal from Debian.

Thanks,
Jeremy Bicha



Processed: [bts-link] source package src:openjpeg2

2018-11-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package src:openjpeg2
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #884738 (http://bugs.debian.org/884738)
> # Bug title: openjpeg2: CVE-2017-17480: stack-based buffer overflow in 
> pgxtovolume function in jp3d/convert.c
> #  * https://github.com/uclouvain/openjpeg/issues/1044
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 884738 + fixed-upstream
Bug #884738 [src:openjpeg2] openjpeg2: CVE-2017-17480: stack-based buffer 
overflow in pgxtovolume function in jp3d/convert.c
Added tag(s) fixed-upstream.
> usertags 884738 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 884738 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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



Processed: forcibly merging 686152 686150

2018-11-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 686150 src:xorg-server 2:1.12.3-1
Bug #686150 [xserver-xorg-core] xorg server 1.12.3: xf86UnloadSubModule() hangs
Bug reassigned from package 'xserver-xorg-core' to 'src:xorg-server'.
Ignoring request to alter found versions of bug #686150 to the same values 
previously set
Ignoring request to alter fixed versions of bug #686150 to the same values 
previously set
Bug #686150 [src:xorg-server] xorg server 1.12.3: xf86UnloadSubModule() hangs
Marked as found in versions xorg-server/2:1.12.3-1.
> forcemerge 686152 686150
Bug #686152 {Done: Julien Cristau } [src:xorg-server] xorg 
server 1.12.3: xf86UnloadSubModule() hangs
Bug #686150 [src:xorg-server] xorg server 1.12.3: xf86UnloadSubModule() hangs
Marked Bug as done
Marked as fixed in versions xorg-server/2:1.12.4-1.
Added tag(s) patch.
Bug #686152 {Done: Julien Cristau } [src:xorg-server] xorg 
server 1.12.3: xf86UnloadSubModule() hangs
Added tag(s) wheezy.
Merged 686150 686152
> thanks
Stopping processing here.

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



Processed: unarchiving 686152

2018-11-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> unarchive 686152
Bug #686152 {Done: Julien Cristau } [src:xorg-server] xorg 
server 1.12.3: xf86UnloadSubModule() hangs
Unarchived Bug 686152
> thanks
Stopping processing here.

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



Bug#914101: FTBFS: Missing build-dependency against pycairo

2018-11-19 Thread Marius Gedminas
On Mon, Nov 19, 2018 at 02:06:57PM +0100, Laurent Bigonville wrote:
> Source: gtimelog
> Version: 0.11.1-2
> Severity: serious
> Justification: fails to build from source
...
> When building gtimelog in a clean (unstable) environment, it FTBFS with
> the following error:
> 
> I: pybuild base:217: python3.7 setup.py test 
> running test
> Searching for pycairo>=1.11.1
...
> No local packages or working download links found for pycairo>=1.11.1
> error: Could not find suitable distribution for 
> Requirement.parse('pycairo>=1.11.1')
> E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: 
> python3.7 setup.py test 

The test suite doesn't need pycairo (or pygobject), but it's hard to
explain this to 'python setup.py test', which assumes all of the usual
install_requires will be needed for the test suite.

It would be best if the Debian package could use 'python3.7 -m gtimelog.tests'
to run the test suite.  I'm not sufficiently familiar with pybuild to
know how to tell it to do that.

As a quick workaround I could modify setup.py to set install_requires=[]
when it finds 'test' in sys.argv, but that feels dirty.

Regards,
Marius Gedminas (upstream author of gtimelog)
-- 
I'm a sorceress, not a miracle worker.
-- The Spellsong War by L. E. Modesitt, Jr.



Bug#913909: [Ceph-maintainers] Bug#913909: Bug#913909: ceph: FTBFS on i386 and mipsel (regression)

2018-11-19 Thread Salvatore Bonaccorso
Hi Gaudenz, and hi James,

On Mon, Nov 19, 2018 at 03:48:14PM +0100, Gaudenz Steinlin wrote:
> James Page  writes:
> > https://git.launchpad.net/~ubuntu-server-dev/ubuntu/+source/ceph/tree/debian/patches?h=ubuntu/xenial
> > 
> > I think I hit the same issue in Ubuntu a while back for which I picked 3
> > rocksdb patches - see above URL - 000*.patch.
> 
> Thanks James. It looks like these patches actually fix the build issue.  I
> already had these patches applied to the build in unstable, but I did not
> make the connection to the infinite loop.
> 
> Salvatore, do you agree to an upload of 10.2.11-2 with these patches to
> stretch-security? Or how should we proceed?

Yes we should release a regression update for ceph via
stretch-security.

Can you ping us when you have it ready?

Regards,
Salvatore



Bug#914104: I agree with removal

2018-11-19 Thread Neil Williams
Things haven't really changed for gpdftext.

It's not impossible for someone to adopt the package in Debian and the
upstream at the same time, it's not a lot of code. However, it seems
that this little niche was a bit too small for anyone else to want to
pick it up once I stopped needing the code.

-- 

Neil Williams
h...@codehelp.co.uk



pgpf6qh7rePve.pgp
Description: OpenPGP digital signature


Bug#908827: marked as done (mesa: Fails to build on Stretch, missing min build dep)

2018-11-19 Thread Debian Bug Tracking System
Your message dated Mon, 19 Nov 2018 15:34:34 +
with message-id 
and subject line Bug#908827: fixed in mesa 18.2.5-1
has caused the Debian Bug report #908827,
regarding mesa: Fails to build on Stretch, missing min build dep
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.)


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

Hi,

Mesa 18.2.0-1 fails to build on Stretch, I can't find the relevant bug report
on freedesktop.org but now it requires xcb-proto >= 1.13.

After compiling and installing xcb-proto and libxcb 1.13-1 from unstable, the
package was built succesfully.



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

Kernel: Linux 4.19.0-rc2-test1 (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)
--- End Message ---
--- Begin Message ---
Source: mesa
Source-Version: 18.2.5-1

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

Debian distribution maintenance software
pp.
Andreas Boll  (supplier of updated mesa 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: Mon, 19 Nov 2018 16:18:34 +0100
Source: mesa
Binary: libxatracker2 libxatracker-dev libd3dadapter9-mesa 
libd3dadapter9-mesa-dev libgbm1 libgbm-dev libegl-mesa0 libegl1-mesa 
libegl1-mesa-dev libwayland-egl1-mesa libgles2-mesa libgles2-mesa-dev 
libglapi-mesa libglx-mesa0 libgl1-mesa-glx libgl1-mesa-dri libgl1-mesa-dev 
mesa-common-dev libosmesa6 libosmesa6-dev mesa-va-drivers mesa-vdpau-drivers 
mesa-vulkan-drivers mesa-opencl-icd
Architecture: source
Version: 18.2.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Andreas Boll 
Description:
 libd3dadapter9-mesa - state-tracker for Direct3D9
 libd3dadapter9-mesa-dev - state-tracker for Direct3D9 -- development files
 libegl-mesa0 - free implementation of the EGL API -- Mesa vendor library
 libegl1-mesa - transitional dummy package
 libegl1-mesa-dev - free implementation of the EGL API -- development files
 libgbm-dev - generic buffer management API -- development files
 libgbm1- generic buffer management API -- runtime
 libgl1-mesa-dev - free implementation of the OpenGL API -- GLX development 
files
 libgl1-mesa-dri - free implementation of the OpenGL API -- DRI modules
 libgl1-mesa-glx - transitional dummy package
 libglapi-mesa - free implementation of the GL API -- shared library
 libgles2-mesa - transitional dummy package
 libgles2-mesa-dev - free implementation of the OpenGL|ES 2.x API -- 
development files
 libglx-mesa0 - free implementation of the OpenGL API -- GLX vendor library
 libosmesa6 - Mesa Off-screen rendering extension
 libosmesa6-dev - Mesa Off-screen rendering extension -- development files
 libwayland-egl1-mesa - transitional dummy package
 libxatracker-dev - X acceleration library -- development files
 libxatracker2 - X acceleration library -- runtime
 mesa-common-dev - Developer documentation for Mesa
 mesa-opencl-icd - free implementation of the OpenCL API -- ICD runtime
 mesa-va-drivers - Mesa VA-API video acceleration drivers
 mesa-vdpau-drivers - Mesa VDPAU video acceleration drivers
 mesa-vulkan-drivers - Mesa Vulkan graphics drivers
Closes: 863972 907136 908827 909720
Changes:
 mesa (18.2.5-1) unstable; urgency=medium
 .
   * New upstream release.
 .
 mesa (18.2.4-1) experimental; urgency=medium
 .
   [ Andreas Boll ]
   * New upstream release.
 - vulkan: Disable randr lease for libxcb < 1.13 (Closes: #908827,
 #909720).
   * Drop version from build-deps libxcb-dri3-dev and libxcb-present-dev.
   * Bump libdrm-dev dependency to 2.4.92.
   * Enable building 

Bug#913953:

2018-11-19 Thread Beta Version
4.1.3-1+b1 fixed that issue for me.


Bug#914111: [Debian-zh-dev] Bug#914111: liblunar: Intent to remove from Debian

2018-11-19 Thread 073plan
X-Debbugs-CC: czc...@debian.org

在 2018-11-19一的 09:55 -0500,Jeremy Bicha写道:
> Source: liblunar
> Version: 2.0.1-3
> Severity: serious
> Tags: buster sid
> X-Debbugs-CC: czc...@debian.org
> 
> liblunar has no reverse dependencies in Debian. Its last maintainer
> upload was 2 years ago (an adoption upload after being orphaned by the
> MIA Team).
> 
> It was removed from Testing a year ago. The 2 current RC bugs have
> trivial patches with no response in over 2 months. While I could do an
> NMU, I don't think Debian needs to have an unmaintained unused
> library.
> 
> Therefore, I intend to remove liblunar from Debian very soon. Please
> respond very
> promptly if you agree or object to its removal.

I have no objections on removal.

@czchen what do you think?

--
Thanks,
Boyuan Yang



Bug#914112: galera-3 FTBFS: error: no matching function for call to 'asio::ssl::context::context(asio::io_service&, asio::ssl::context_base::method)'

2018-11-19 Thread Adrian Bunk
Source: galera-3
Version: 25.3.23-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=galera-3=sid

...
galera/src/ist.cpp: In constructor 
'galera::ist::Receiver::Receiver(gu::Config&, galera::TrxHandle::SlavePool&, 
const char*)':
galera/src/ist.cpp:108:25: error: no matching function for call to 
'asio::ssl::context::context(asio::io_service&, 
asio::ssl::context_base::method)'
 ready_(false)
 ^
In file included from /usr/include/asio/ssl/context.hpp:755,
 from /usr/include/asio/ssl.hpp:18,
 from galerautils/src/gu_asio.hpp:47,
 from galera/src/ist.hpp:15,
 from galera/src/ist.cpp:5:
/usr/include/asio/ssl/impl/context.ipp:62:1: note: candidate: 
'asio::ssl::context::context(asio::ssl::context_base::method)'
 context::context(context::method m)
 ^~~
/usr/include/asio/ssl/impl/context.ipp:62:1: note:   candidate expects 1 
argument, 2 provided
In file included from /usr/include/asio/ssl.hpp:18,
 from galerautils/src/gu_asio.hpp:47,
 from galera/src/ist.hpp:15,
 from galera/src/ist.cpp:5:
/usr/include/asio/ssl/context.hpp:35:7: note: candidate: 
'asio::ssl::context::context(const asio::ssl::context&)'
 class context
   ^~~
/usr/include/asio/ssl/context.hpp:35:7: note:   candidate expects 1 argument, 2 
provided
galera/src/ist.cpp: In constructor 'galera::ist::Sender::Sender(const 
gu::Config&, gcache::GCache&, const string&, int)':
galera/src/ist.cpp:637:22: error: no matching function for call to 
'asio::ssl::context::context(asio::io_service&, 
asio::ssl::context_base::method)'
 use_ssl_   (false)
  ^
In file included from /usr/include/asio/ssl/context.hpp:755,
 from /usr/include/asio/ssl.hpp:18,
 from galerautils/src/gu_asio.hpp:47,
 from galera/src/ist.hpp:15,
 from galera/src/ist.cpp:5:
/usr/include/asio/ssl/impl/context.ipp:62:1: note: candidate: 
'asio::ssl::context::context(asio::ssl::context_base::method)'
 context::context(context::method m)
 ^~~
/usr/include/asio/ssl/impl/context.ipp:62:1: note:   candidate expects 1 
argument, 2 provided
In file included from /usr/include/asio/ssl.hpp:18,
 from galerautils/src/gu_asio.hpp:47,
 from galera/src/ist.hpp:15,
 from galera/src/ist.cpp:5:
/usr/include/asio/ssl/context.hpp:35:7: note: candidate: 
'asio::ssl::context::context(const asio::ssl::context&)'
 class context
   ^~~
/usr/include/asio/ssl/context.hpp:35:7: note:   candidate expects 1 argument, 2 
provided
In file included from galera/src/ist.hpp:15,
 from galera/src/ist.cpp:5:
galerautils/src/gu_asio.hpp: In instantiation of 'void gu::set_fd_options(S&) 
[with S = asio::basic_socket_acceptor]':
galera/src/ist.cpp:317:37:   required from here
galerautils/src/gu_asio.hpp:197:26: error: 'class 
asio::basic_socket_acceptor' has no member named 'native'
 if (fcntl(socket.native(), F_SETFD, flags) == -1)
   ~~~^~
galerautils/src/gu_asio.hpp: In instantiation of 'void gu::set_fd_options(S&) 
[with S = asio::basic_socket]':
galera/src/ist.cpp:366:57:   required from here
galerautils/src/gu_asio.hpp:197:26: error: 'class 
asio::basic_socket' has no member named 'native'
galerautils/src/gu_asio.hpp: In instantiation of 'void gu::set_fd_options(S&) 
[with S = asio::basic_stream_socket]':
galera/src/ist.cpp:372:38:   required from here
galerautils/src/gu_asio.hpp:197:26: error: 'class 
asio::basic_stream_socket' has no member named 'native'
galera/src/ist.cpp: In constructor 
'galera::ist::Receiver::Receiver(gu::Config&, galera::TrxHandle::SlavePool&, 
const char*)':
galera/src/ist.cpp:108:25: error: no matching function for call to 
'asio::ssl::context::context(asio::io_service&, 
asio::ssl::context_base::method)'
 ready_(false)
 ^
In file included from /usr/include/asio/ssl/context.hpp:755,
 from /usr/include/asio/ssl.hpp:18,
 from galerautils/src/gu_asio.hpp:47,
 from galera/src/ist.hpp:15,
 from galera/src/ist.cpp:5:
/usr/include/asio/ssl/impl/context.ipp:62:1: note: candidate: 
'asio::ssl::context::context(asio::ssl::context_base::method)'
 context::context(context::method m)
 ^~~
/usr/include/asio/ssl/impl/context.ipp:62:1: note:   candidate expects 1 
argument, 2 provided
In file included from /usr/include/asio/ssl.hpp:18,
 from galerautils/src/gu_asio.hpp:47,
 from galera/src/ist.hpp:15,
 from galera/src/ist.cpp:5:
/usr/include/asio/ssl/context.hpp:35:7: note: candidate: 
'asio::ssl::context::context(const asio::ssl::context&)'
 class context
   ^~~
/usr/include/asio/ssl/context.hpp:35:7: note:   candidate expects 1 argument, 2 
provided
galera/src/ist.cpp: In 

Bug#914111: liblunar: Intent to remove from Debian

2018-11-19 Thread Jeremy Bicha
Source: liblunar
Version: 2.0.1-3
Severity: serious
Tags: buster sid
X-Debbugs-CC: czc...@debian.org

liblunar has no reverse dependencies in Debian. Its last maintainer
upload was 2 years ago (an adoption upload after being orphaned by the
MIA Team).

It was removed from Testing a year ago. The 2 current RC bugs have
trivial patches with no response in over 2 months. While I could do an
NMU, I don't think Debian needs to have an unmaintained unused
library.

Therefore, I intend to remove liblunar from Debian very soon. Please
respond very
promptly if you agree or object to its removal.

References

https://bugs.debian.org/841812 (original orphan bug)
https://bugs.debian.org/822590 (pygtksourceview dependency bug)
https://bugs.debian.org/906044 (python dependency bug)
https://code.google.com/archive/p/liblunar/

On behalf of the Debian GNOME team,
Jeremy Bicha



Bug#913909: [Ceph-maintainers] Bug#913909: Bug#913909: ceph: FTBFS on i386 and mipsel (regression)

2018-11-19 Thread Gaudenz Steinlin
James Page  writes: 
https://git.launchpad.net/~ubuntu-server-dev/ubuntu/+source/ceph/tree/debian/patches?h=ubuntu/xenial 

I think I hit the same issue in Ubuntu a while back for which I 
picked 3 rocksdb patches - see above URL - 000*.patch.


Thanks James. It looks like these patches actually fix the build 
issue.  I already had these patches applied to the build in 
unstable, but I did not make the connection to the infinite loop.


Salvatore, do you agree to an upload of 10.2.11-2 with these 
patches to stretch-security? Or how should we proceed?


Gaudenz
--
PGP: 836E 4F81 EFBB ADA7 0852 79BF A97A 7702 BAF9 1EF5


signature.asc
Description: PGP signature


Bug#914085: Bug #914085 in soundscaperenderer marked as pending

2018-11-19 Thread IOhannes zmölnig
Control: tag -1 pending

Hello,

Bug #914085 in soundscaperenderer reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/multimedia-team/soundscaperenderer/commit/6da627e3e79b06cf3b26332b8d853896d49df830


Centralize the update-alternative handling

Closes: #914085



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/914085



Processed: Bug #914085 in soundscaperenderer marked as pending

2018-11-19 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #914085 [soundscaperenderer] soundscaperenderer: failed to cofigure cleanly
Added tag(s) pending.

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



Processed: gpdftext: raising severity of gconf dependency bug

2018-11-19 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 serious
Bug #885666 [src:gpdftext] gpdftext: Depends on gconf
Severity set to 'serious' from 'important'

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



Bug#914104: gpdftext: Intent to remove from Debian

2018-11-19 Thread Jeremy Bicha
Source: gpdftext
Version: 0.3.10-3
Severity: serious
Tags: buster sid
X-Debbugs-CC: codeh...@debian.org

gpdftext was orphaned 2 years ago. This is a bit concerning since the
Debian maintainer was also upstream for the package.

Its last maintainer upload was 4 years ago. I did the only QA upload a
year ago to stop using scrollkeeper and modernize the packaging.

gpdftext is one of the last packages in Debian using gconf. Although
gconf will still be in the Debian Buster release, its main purpose
there is to provide the gconf-to-gsettings migration helper.

I intend to remove gpdftext from Debian very soon. Please respond very
promptly if you agree or object to its removal.

References

https://bugs.debian.org/835907 (orphan bug)
https://bugs.debian.org/885666 (gconf dependency bug)
https://web.archive.org/web/20150921230353/https://alioth.debian.org/projects/gpdftext/

On behalf of the Debian GNOME team,
Jeremy Bicha



Bug#913910: atop crashed with "Malloc failed for 1826553824 deviated tasks"

2018-11-19 Thread Vincent Lefevre
On 2018-11-19 10:30:52 +0100, Vincent Lefevre wrote:
> On 2018-11-19 09:58:04 +0100, Vincent Lefevre wrote:
> > Or rebuilding atop with -fsanitize=undefined -fno-sanitize-recover
> > would allow one to see where the problem occurs, since one can get a
> > negative value:
> > 
> >   Malloc failed for -11968 exited processes
> > 
> > probably as the cause of some undefined behavior.

The negative value was due to a type mismatch in a format string.
I've fixed 2 of them in my fork and did a pull request.

> I've done that, but then, I can't reproduce the problem!
> 
> It might be due to a compiler bug, or because the code is too slow
> in this case.

I've also noticed that the failure of system/library calls is not
checked (see my comments in the upstream bug). In case there's a
failure due to some race condition, this could explain the issue.
But it may also be due to something else.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#913510: marked as done (ruby-charlock-holmes FTBFS with ICU 63.1)

2018-11-19 Thread Debian Bug Tracking System
Your message dated Mon, 19 Nov 2018 13:34:40 +
with message-id 
and subject line Bug#913510: fixed in ruby-charlock-holmes 0.7.6-1
has caused the Debian Bug report #913510,
regarding ruby-charlock-holmes FTBFS with ICU 63.1
to be marked as done.

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

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


-- 
913510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913510
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-charlock-holmes
Source-Version: 0.7.5-1
Severity: important
Tags: patch
Usertags: icu63

Dear Maintainer,

ICU 63.1 recently released, packaged and uploaded to experimental.
Its transition is going to start soon. However your package fails to
build with this version. I attach a patch which fixes the problem.
Please check if it works with the version in Sid and upload the
package when it's feasible for you.

Thanks,
Laszlo/GCS
Description: fix FTBFS with ICU 63.1
 Add icu namespace.
Author: Laszlo Boszormenyi (GCS) 
Last-Update: 2018-11-04

---

--- ruby-charlock-holmes-0.7.5.orig/ext/charlock_holmes/transliterator.cpp
+++ ruby-charlock-holmes-0.7.5/ext/charlock_holmes/transliterator.cpp
@@ -36,7 +36,7 @@ static VALUE rb_cTransliterator;
 
 static VALUE rb_transliterator_id_list(VALUE self) {
   UErrorCode status = U_ZERO_ERROR;
-  StringEnumeration *id_list;
+  icu::StringEnumeration *id_list;
   int32_t id_list_size;
   const char *curr_id;
   int32_t curr_id_len;
@@ -44,7 +44,7 @@ static VALUE rb_transliterator_id_list(V
   VALUE rb_curr_id;
 
   id_list_size = 0;
-  id_list = Transliterator::getAvailableIDs(status);
+  id_list = icu::Transliterator::getAvailableIDs(status);
   if(!U_SUCCESS(status)) {
 rb_raise(rb_eArgError, "%s", u_errorName(status));
   }
@@ -78,12 +78,12 @@ static VALUE rb_transliterator_id_list(V
 static VALUE rb_transliterator_transliterate(VALUE self, VALUE rb_txt, VALUE rb_id) {
   UErrorCode status = U_ZERO_ERROR;
   UParseError p_error;
-  Transliterator *trans;
+  icu::Transliterator *trans;
   const char *txt;
   size_t txt_len;
   const char *id;
   size_t id_len;
-  UnicodeString *u_txt;
+  icu::UnicodeString *u_txt;
   std::string result;
   VALUE rb_out;
 
@@ -98,14 +98,14 @@ static VALUE rb_transliterator_translite
   id = RSTRING_PTR(rb_id);
   id_len = RSTRING_LEN(rb_id);
 
-  trans = Transliterator::createInstance(UnicodeString(id, id_len), UTRANS_FORWARD, p_error, status);
+  trans = icu::Transliterator::createInstance(icu::UnicodeString(id, id_len), UTRANS_FORWARD, p_error, status);
   if(!U_SUCCESS(status)) {
 rb_raise(rb_eArgError, "%s", u_errorName(status));
   }
 
-  u_txt = new UnicodeString(txt, txt_len);
+  u_txt = new icu::UnicodeString(txt, txt_len);
   trans->transliterate(*u_txt);
-  StringByteSink sink();
+  icu::StringByteSink sink();
   u_txt->toUTF8(sink);
 
   delete u_txt;
--- End Message ---
--- Begin Message ---
Source: ruby-charlock-holmes
Source-Version: 0.7.6-1

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated ruby-charlock-holmes 
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: Mon, 19 Nov 2018 18:47:44 +0530
Source: ruby-charlock-holmes
Binary: ruby-charlock-holmes
Architecture: source
Version: 0.7.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Pirate Praveen 
Description:
 ruby-charlock-holmes - Ruby character encoding detection library
Closes: 913510
Changes:
 ruby-charlock-holmes (0.7.6-1) unstable; urgency=medium
 .
   * New upstream version 0.7.6
 (This version is compatible with ICU 63.1) (Closes: #913510)
   * Bump Standards-Version to 4.2.1 (no changes needed)
   * Move debian/watch to gemwatch.debian.net
Checksums-Sha1:
 5ddfceec822dd4315b8046117701770dd5acf4d8 2230 ruby-charlock-holmes_0.7.6-1.dsc
 efc4f7a2b8e47bb397313e74ba6198fcd4dfee89 7092 
ruby-charlock-holmes_0.7.6.orig.tar.gz
 951ba912a8bc321e6b1de32bf6caa3b771f0bed7 3084 
ruby-charlock-holmes_0.7.6-1.debian.tar.xz
 

Processed: Re: gyrus: Depends on gconf

2018-11-19 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 serious
Bug #886065 [src:gyrus] gyrus: Depends on gconf
Severity set to 'serious' from 'important'

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



Bug#914102: gyrus: Intent to remove from Debian

2018-11-19 Thread Jeremy Bicha
Source: gyrus
Version: 0.3.10-3
Severity: serious
Tags: buster sid
X-Debbugs-CC: wvdak...@wilsoft.nl

The last release of gyrus was over 5 years ago. gyrus was orphaned in
Debian around the same time. The only upload since then was to remove
a dependency that was being removed from Debian.

gyrus is one of the last packages in Debian using gconf. Although
gconf will still be in the Debian Buster release, its main purpose
there is to provide the gconf-to-gsettings migration helper.

I intend to remove gyrus from Debian very soon. Please respond very
promptly if you agree or object to its removal.

References

https://bugs.debian.org/732011 (orphan bug)
https://bugs.debian.org/886065 (gconf dependency bug)
https://gitlab.gnome.org/Archive/gyrus/commits/master

On behalf of the Debian GNOME team,
Jeremy Bicha



Processed: fixed 887928 in 5.2.1-6

2018-11-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> fixed 887928 5.2.1-6
Bug #887928 {Done: Jeremy Bicha } [src:din] din uses 
deprecated Tcl 8.5
Marked as fixed in versions din/5.2.1-6.
> thanks
Stopping processing here.

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



Bug#914101: FTBFS: Missing build-dependency against pycairo

2018-11-19 Thread Laurent Bigonville
Source: gtimelog
Version: 0.11.1-2
Severity: serious
Justification: fails to build from source

Hi,

When building gtimelog in a clean (unstable) environment, it FTBFS with
the following error:

I: pybuild base:217: python3.7 setup.py test 
running test
Searching for pycairo>=1.11.1

Note: Bypassing https://pypi.org/simple/pycairo/ (disallowed host; see 
http://bit.ly/2hrImnY for details).

Couldn't find index page for 'pycairo' (maybe misspelled?)
Scanning index of all packages (this may take a while)

Note: Bypassing https://pypi.org/simple/ (disallowed host; see 
http://bit.ly/2hrImnY for details).

No local packages or working download links found for pycairo>=1.11.1
error: Could not find suitable distribution for 
Requirement.parse('pycairo>=1.11.1')
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: 
python3.7 setup.py test 

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

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy

-- no debconf information



Bug#914093: marked as done ([mediathekview] Mediathelview hangs in startup)

2018-11-19 Thread Debian Bug Tracking System
Your message dated Mon, 19 Nov 2018 12:37:29 +
with message-id 
and subject line Bug#914093: fixed in mediathekview 13.2.1-2
has caused the Debian Bug report #914093,
regarding [mediathekview] Mediathelview hangs in startup
to be marked as done.

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

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


-- 
914093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914093
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mediathekview
Version: 13.2.1-1
Severity: grave

mediathekview hangs in startup:

. Portable Mode: false
. Proxy Authentication: not configured
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by mediathek.Main (file:/usr/share/
mediathekview/MediathekView.jar) to field sun.awt.X11.XToolkit.awtAppClassName
WARNING: Please consider reporting this to the maintainers of mediathek.Main
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations
WARNING: All illegal access operations will be denied in a future release
. Programmstart: 19.11.2018 09:54:25
. maxMemory: 1073 MB
. Version: MediathekView 13.2.1
. Java:
. Vendor: Oracle Corporation
. VMname: OpenJDK 64-Bit Server VM
. Version: 11.0.1
. Runtimeversion: 11.0.1+13-Debian-2
. Programmpfad: /usr/share/mediathekview/
. Verzeichnis Einstellungen: /home/reinhard/.mediathek3
. 
. 
. 
. == == == == ==
. DURATION 0:  Start  [480,00 ms]
.Klasse:  Main.getPlatformWindow
. == == == == ==
InteropFactory: cannot load com.sun.javafx.embed.swing.newimpl.InteropFactoryN
.  
.  ===
.  Systemparameter
.  -
.  Download-Timeout [s]: 250
.  max. Download-Restart: 5
.  max. Download-Restart-Http: 10
.  Download weiterführen in [s]: 60
.  Download Fehlermeldung anzeigen [s]: 120
.  Downoadprogress anzeigen: true
.  User-Agent: MediathekView
.  ===
.  
. Konfig wurde gelesen!
. == == == == ==
. DURATION 1:  Start Gui  [1,10 s]
.Klasse:  Main.getPlatformWindow
. == == == == ==
. initializeDatabase()
. initializeDatabase() done.
. == == == == ==
. DURATION 2:  Init GUI  [1,72 s]
.Klasse:  Main.getPlatformWindow
. == == == == ==
. == == == == ==
. DURATION 3:  Gui steht!  [433,00 ms]
.Klasse:  Main.getPlatformWindow
. == == == == ==
. Liste Filme lesen von: /home/reinhard/.mediathek3/filme.json
. Creating SQL indices
. Finished creating SQL indices
. Liste Filme gelesen am: 19.11.2018, 09:54
.   erstellt am: 19.11.2018, 09:16
.   Anzahl Filme: 254961
. Die Filmliste ist 37 Minuten alt
Exception in thread "UIFilmlistLoaderThread" java.lang.NoClassDefFoundError: 
com/google/common/cache/CacheBuilder
at mediathek.tool.Filter.(Filter.java:43)
at mediathek.daten.ListeAbo.createAbo(ListeAbo.java:222)
at java.base/java.lang.Iterable.forEach(Iterable.java:75)
at mediathek.daten.ListeAbo.setAboFuerFilm(ListeAbo.java:277)
at 
mediathek.tool.threads.UIFilmlistLoaderThread.performFilterOperations(UIFilmlistLoaderThread.java:
74)
at 
mediathek.tool.threads.UIFilmlistLoaderThread.run(UIFilmlistLoaderThread.java:
102)
Caused by: java.lang.ClassNotFoundException: 
com.google.common.cache.CacheBuilder
at java.base/
jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583)
at java.base/
jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:
178)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
... 6 more


--- System information. ---
Architecture: 
Kernel:   Linux 4.19.0

Debian Release: buster/sid
  500 unstabledebian 
  500 testing debian 
  101 experimentaldebian 

--- Package information. ---
Depends  (Version) | Installed
==-+-
default-jre(>= 2:1.9)  | 2:1.11-70
 OR java9-runtime  | 
java-wrappers  | 0.3
libopenjfx-java(>= 11) | 11+26-5
libcommons-compress-java   | 1.18-1
libcommons-configuration2-java | 2.2-1
libcommons-dbcp2-java  | 2.5.0-1
libcommons-lang3-java  

  1   2   >