Bug#903109: network-manager-openvpn: "Cannot specify device when activating VPN" when connect to any VPN

2018-07-11 Thread Shin Ice
Good morning,

the promlem is not only openvpn related, I have the same with a cisco
anyconnect VPN using also network-manager-openconnect.
Rolling back to 1.10.8-1 works just to bring the tunnel back up.

Greetings

--

I'm just a placeholder for a really awesome signature...
...that is still missing *sob*


signature.asc
Description: PGP signature


Bug#888356: retroarch: diff for NMU version 1.3.6+dfsg1-1.1

2018-07-11 Thread Sérgio Benjamim

Hi,

There's a beta package for 1.7.3... you guys should improve it, instead 
updating really really old versions ;)

https://mentors.debian.net/package/retroarch

I'm out of time to improve/finish it right now, sorry.

cheers,
sergio-br2

On 11/07/2018 16:37, Sebastian Ramacher wrote:

Control: tags 888356 + patch
Control: tags 888356 + pending

Dear maintainer,

I've prepared an NMU for retroarch (versioned as 1.3.6+dfsg1-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Cheers




Bug#888328: motion: diff for NMU version 4.1.1-1.1

2018-07-11 Thread Ximin Luo
Sebastian Ramacher:
> Control: tags 888328 + pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for motion (versioned as 4.1.1-1.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
> 

Sorry for the lack of response, I neglected Debian between Feb-May of this year.

Yes the NMU is fine, I will let the DELAYED upload go ahead. I've added your 
patch to the salsa git. Thanks for taking care of it!

X

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git



Bug#898884: fixed in python-pygit2 0.27.0-1

2018-07-11 Thread Pirate Praveen
On Thu, 17 May 2018 10:51:01 + =?utf-8?b?T25kxZllaiBOb3bDvQ==?=
 wrote:
> Source: python-pygit2
> Source-Version: 0.27.0-1

Please upload this to unstable, libgit2 0.27 is in unstable now.



signature.asc
Description: OpenPGP digital signature


Bug#754292: gdb: target remote does not accept IPv6 only names

2018-07-11 Thread Sergio Durigan Junior
On Wednesday, July 09 2014, Michael Richardson wrote:

> Dear Maintainer,
>
> I typed:
> (gdb) target remote lac02.yarn.gatineau.credil.org:9979
> lac02.yarn.gatineau.credil.org: unknown host
> lac02.yarn.gatineau.credil.org:9979: No such file or directory.
>
> but such a name does exist:
> meech-[~] mcr 1009 %host lac02.yarn.gatineau.credil.org
> lac02.yarn.gatineau.credil.org has IPv6 address 2001:4830:116e:1::148
>
> it just doesn't have an A record, since, well.. that legacy v4 is no fun.
>
> I worked around by finding the numerical v4 address and using that.

FWIW, I've pushed a patch upstream to implement IPv6 support for GDB and
gdbserver today.

  
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=c7ab0aef11d91b637bf091aa9176b8dc4aadee46

Cheers,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


signature.asc
Description: PGP signature


Bug#902405: RFS: photoflare/1.5.4-1

2018-07-11 Thread Sergio Durigan Junior
Control: owner -1 !

On Tuesday, June 26 2018, Dylan Aïssi wrote:

> Dear mentors,
>
> I am looking for a sponsor for my package "photoflare"
>
> * Package name: photoflare
>   Version : 1.5.4-1
>   Upstream Author : Dylan Coakley
> * URL : http://photoflare.io/
> * License : GPL-3+
>   Section : graphics
>
> It builds those binary packages:
>
> photoflare - Simple but powerful Image Editor
>
> To access further information about this package, please visit the
> following URL:
>
>   https://mentors.debian.net/package/photoflare
>
>
> Alternatively, one can download the package with dget using this command:
>
> dget -x 
> https://mentors.debian.net/debian/pool/main/p/photoflare/photoflare_1.5.4-1.dsc
>
> Changes since the last upload:
>
>   * Initial release. (Closes: #901871, LP: #1711644)

Thanks for the package, Dylan.  I'm looking into it now.

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


signature.asc
Description: PGP signature


Bug#903270: RFS: sharness/1.0.0-1 [ITP] shell library for running tests

2018-07-11 Thread Sergio Durigan Junior
Control: owner -1 !
Control: tags -1 + moreinfo

On Sunday, July 08 2018, Lars Kruse wrote:

> Dear mentors,

Hi Lars,

> I am looking for a sponsor for my package "sharness"
>
>  Package name: sharness
>  Version : 1.0.0-1
>  Upstream Author : Christian Couder 
>  URL : https://github.com/chriscool/sharness
>  License : GPL-2 or later
>  Section : devel
>
> It builds those binary packages:
>
>   sharness   - shell library for automated tests with TAP output
>
> Sharness is used by a few Debian packages as part of their DEP8 tests
> (via autopkgtest):
>   * gearmand
>   * git-reintegrate
>   * git-remote-bzr
>   * git-remote-hg
>   * hiera-eyaml
>   * jemalloc
>   * mod-gearman
>   * munin
>   * pass-otp
>   * puppet-lint
>   * puppet-module-puppetlabs-concat
>   * puppet-module-puppetlabs-ntp
>   * puppet-module-puppetlabs-stdlib
> (the list was assembled via https://codesearch.debian.net)
>
> Currently these packages embed a copy of the sharness.sh file below
> debian/tests.
> I will file bug reports against these packages (including patches) after
> the sharness package is available, in order to help them getting rid of
> their embedded code copies.

Thanks, that is a nice goal.

> I am part of the munin packaging team, thus the munin package would
> benefit immediately from this new package.
>
> I plan to maintain the sharness package for the foreseeable future.

We had a brief conversation on IRC, where I told you that this package
should be hosted at salsa.d.o.  You told me you created a new repo
there.  Great!

Here are the other things I noticed about the package.  Mostly nits.  I
think we should be good to go once you address them.

1) On d/copyright, you don't list the files under the "debian/"
directory.  These should be listed, and you should be the author.  I
recommend choosing the same license as upstream, just to make things
simpler.

2) On d/control, Standards-Version should now be 4.1.5.

3) Better safe than sorry: on d/control, the Vcs-* fields should point
to your salsa.d.o repo.

4) On d/rules, you can remove the "override_dh_auto_install" target if
you're not using it.

Otherwise, the package looks good to me.  Let me know when you address
these issues and I'll be happy to upload it.

Thanks!

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


signature.asc
Description: PGP signature


Bug#903483: mozjs52: FTBFS on m68k: not supported by build/moz.configure/init.configure

2018-07-11 Thread Finn Thain
On Thu, 12 Jul 2018, John Paul Adrian Glaubitz wrote:

> On 07/11/2018 01:11 PM, Simon McVittie wrote:
> > 
> > Thanks. Does the result work (at least minimally, e.g. the js52 
> > interpreter can print("hello, world")) on real m68k hardware?
> 
> I just did a testbuild with the testsuite enabled and it seems all tests 
> pass except for one:
> 
>  FAILED! SSN_pattern - 8 = 8 expected: NaN
> 
> So, I guess mozjs52 mostly works on m68k.
> 

That was on vs93.physik.fu-berlin.de, right? Isn't that a Qemu instance?

-- 

> Adrian
> 
> 



Bug#903621: ibus-rime: cannot enter Chinese after switching from Russian

2018-07-11 Thread Michael Tsang
Package: ibus-rime
Severity: normal
Tags: l10n

Dear Maintainer,

I have multiple input methods installed in my ibus, including English, Russian
and Swedish and rime. I've added rime input methods which input Chinese by
using Pinyin in Latin alphabet.

If I switch from English to rime, it behaves as expected. However, if I switch
from Russian to rime, when I press the keyboard, Russian characters appears
with no compose window from rime. Because the input method selected in rime
uses Latin alphabet, I expect Latin characters come out and compose Chinese.




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

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

Versions of packages ibus-rime depends on:
ii  ibus   1.5.18-1
ii  libc6  2.27-3
ii  libglib2.0-0   2.56.1-2
ii  libibus-1.0-5  1.5.18-1
ii  libnotify4 0.7.7-3
pn  librime-data   
pn  librime1   

ibus-rime recommends no packages.

ibus-rime suggests no packages.



Bug#888388: freshplayerplugin: diff for NMU version 0.3.5-1.1

2018-07-11 Thread Vincent Danjean
Le 11/07/2018 à 23:21, Sebastian Ramacher a écrit :
> Control: tags 888388 + pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for freshplayerplugin (versioned as 0.3.5-1.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.

You can upload it asap. Thanks fpr your help.

  Regards,
Vincent

> Cheers
> 


-- 
Vincent Danjean   GPG key ID 0xD17897FA vdanj...@debian.org
GPG key fingerprint: 621E 3509 654D D77C 43F5  CA4A F6AE F2AF D178 97FA
Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html
APT repo:  deb http://people.debian.org/~vdanjean/debian unstable main



Bug#901356: r-cran-caret: new version pulls in loads of development packages

2018-07-11 Thread Rogério Brito
Hi, Andreas and other people.

I'm sending this to the list instead of filing other bugs, so that other
people can take a look and see if I am doing something wrong or not.

On Jun 12 2018, Andreas Tille wrote:
> On Mon, Jun 11, 2018 at 06:32:14PM -0300, Rogério Brito wrote:
> > In fact, looking more closely at the package relationships of r-cran-caret,
> > I see that it both Depends **and** also Suggests libgdal-dev, so, at least
> > one of thoses may be a mistake...
> 
> The list of Depends / Recommends / Suggests is autogenerated by dh-r so
> I need to check whether there is some bug there.

I found other packages that seem to have some dubious dependencies on
libgdal-dev (the previous versions didn't have such dependencies, but the
new one does and it doesn't seem like the package should really depend on it):

* r-cran-bbmle
* r-cran-modeltools
* r-cran-rgl
* r-cran-sn

Have I missed something?


Thanks in advance,

Rogério.

-- 
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
http://cynic.cc/blog/ : github.com/rbrito : profiles.google.com/rbrito
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br



Bug#903620: RM: xvt -- RoQA; unmaintained; upstream dead; better alternative exist

2018-07-11 Thread Boyuan Yang
Package: ftp.debian.org
Severity: normal
X-Debbugs-CC: s...@debian.org sam+...@zoy.org

Dear FTP Masters,

Following the discussion in https://bugs.debian.org/893649 , it is 
obvious that package "xvt" is no longer suitable for Debian.

The package:

* Upstream dead, saw no upstream activity in the 21st century
* Received no maintainer upload since 2006
* Has better alternatives (forks): rxvt and others
* Received no maintainer response for removal request Bug #893649 
since March 2018

Package xvt has no reverse dependencies.

As a result, please remove xvt from Debian Archive.

Dear Sam, if you have any ideas about the removal of xvt, please feel 
free to share them here and manipulate this RM bug if you find 
necessary.

--
Thanks!
Boyuan Yang

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


Bug#901455: FTBFS in sid: package com.sun.tools.doclets.standard is not visible

2018-07-11 Thread peter green

During a recompilation as part of the octave-4.4 transition, libsbml failed to
build (for a reason apparently unrelated to the transition):


Specifically this seems to have been caused by the change of default java 
version from 9 to 10.

In raspbian buster I solved this for the time being by forcing openjdk 9. A 
debdiff can be found at
http://debdiffs.raspbian.org/main/libs/libsbml/libsbml_5.16.0%2bdfsg-2%2brpi1.debdiff

No intent to NMU in Debian.



Bug#903619: haskell-language-python FTBFS build hangs.

2018-07-11 Thread peter green

Package: haskell-language-python
Version: 0.5.4-6

From the amd64 build log.

[16 of 23] Compiling Language.Python.Version2.Parser.Parser ( 
dist-ghc/build/Language/Python/Version2/Parser/Parser.hs, 
dist-ghc/build/Language/Python/Version2/Parser/Parser.o )
E: Build killed with signal TERM after 150 minutes of inactivity

Things look similar on other architectures.



Bug#902855: ITA: enigma -- A game where you control a marble with

2018-07-11 Thread eamanu15
Hello dear Mentors and Erich,

I am working in the enigma package update (I am trying to adopt it). I see
that this package don't have a VCS.

Do you think that is a good idea add enigma to salsa?
If it is true, could anyone create a salsa repo to commit it and give me
access?

Thanks!
Regards!
Emmanuel
-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com


Bug#902226: debian-installer-netboot-images: FTBFS in stretch, even when allowing network access

2018-07-11 Thread Cyril Brulebois
Hi Didier,

Didier 'OdyX' Raboud  (2018-06-27):
> Given my failed attempts, I suspect your patches are the lesser evil
> for solving this. But I'm not convinced that solving this is better
> than ensuring we only ever build "pure-stretch" or
> "pure-stretch-proposed-updates" d-i-n-i's.

No argument here, I'm totally with you.

> > I'll let others comment on this bug report plus proposed solution;
> > Didier maybe?
> 
> Thanks for the explicit ping; I'm not on top of Debian things these
> days.

Thanks for your valuable input. Based on the fact you've made several
attempts already, I decided patches were good enough to include them in
the dini upload for this point release, instead of spending more time
to get a perfect solution (esp. with the next point release coming up in
a few days).

I've opened #903618 to keep track of the improvement over this set of
patches.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature


Bug#900772: closed by Dmitry Smirnov (Bug#900772: fixed in cakephp 2.10.11-1)

2018-07-11 Thread Dmitry Smirnov
On Thursday, 12 July 2018 5:31:03 AM AEST Adrian Bunk wrote:
> cakephp-scripts still depends on php-mcrypt.

Thank you for pointing that out.

-- 
All the best,
 Dmitry Smirnov.

---


I am easily satisfied with the very best.
-- Winston Churchill


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


Bug#903618: debian-installer-netboot-images: Build atomically from a distribution or from a fallback distribution

2018-07-11 Thread Cyril Brulebois
Source: debian-installer-netboot-images
Version: 20170615+deb9u4
Severity: wishlist

Hi,

As a first stab at fixing dini's FTBFS in stable after a point release
has happened (we build against s-p-u before the point release, but d-i
disappears from there after the point release), I've implemented a fall
back to stretch if stretch-proposed-updates doesn't have the requested
d-i version.

More details in the original report:
  https://bugs.debian.org/902226

Right now, this fallback will take place for each build, that is: for
each architecture.

It would be way better to have an early detection, and to stick to the
relevant distribution all way through. We could have an early test with
a given arch (say, amd64), maybe?

Setting severity to wishlist at the moment, even if that's about adding
a notable improvement over a bug fix for a(n admittedly) serious bug.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant



Bug#903616: patch

2018-07-11 Thread dann frazier
tags 903616 + patch
kthxbye
Description: Add IANA ID for NVIDIA hardware
 Add the NVIDIA IANA ID to the hardcoded list used in ipmitool <= 1.8.18.
 After upstream commit "9d41136 ID:491 - Fetch vendor IDs from IANA", ipmitool
 generates a list of vendor IDs dynamically at build time, so we can drop this
 patch in future releases.
Author: dann frazier 
Origin: backport
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903616
Forwarded: not-needed
Last-Update: 2018-07-11
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
Index: ipmitool-1.8.18/include/ipmitool/ipmi.h
===
--- ipmitool-1.8.18.orig/include/ipmitool/ipmi.h
+++ ipmitool-1.8.18/include/ipmitool/ipmi.h
@@ -279,6 +279,7 @@ typedef enum IPMI_OEM {
  /* 4769 for [IBM Corporation] */
  IPMI_OEM_IBM_4769   = 4769,
  IPMI_OEM_MAGNUM = 5593,
+ IPMI_OEM_NVIDIA = 5703,
  IPMI_OEM_TYAN   = 6653,
  IPMI_OEM_QUANTA = 7244,
  IPMI_OEM_NEWISYS= 9237,
Index: ipmitool-1.8.18/lib/ipmi_strings.c
===
--- ipmitool-1.8.18.orig/lib/ipmi_strings.c
+++ ipmitool-1.8.18/lib/ipmi_strings.c
@@ -96,6 +96,7 @@ const struct valstr ipmi_oem_info[] = {
{ IPMI_OEM_IBM_4769,   "IBM Corporation" },
{ IPMI_OEM_IBM_20301,  "IBM eServer X" },
{ IPMI_OEM_ADLINK_24339,   "ADLINK Technology Inc." },
+   { IPMI_OEM_NVIDIA, "NVIDIA Corporation" },
{ 0x , NULL },
 };
 


Bug#903617: ITP: equinox-framework -- Implementation of the OSGi Core Framework R4 specification

2018-07-11 Thread Emmanuel Bourg
Package: wnpp
Severity: wishlist
Owner: Emmanuel Bourg 

* Package name: equinox-framework
  Version : 4.7.3
  Upstream Author : Eclipse Foundation, Inc.
* URL : http://www.eclipse.org/equinox/framework/
* License : EPL-1.0, Apache-2.0
  Programming Lang: Java
  Description : Implementation of the OSGi Core Framework R4 specification

The Equinox Framework component is tasked with being a full implementation
of the OSGi Core Framework R4 specification. In addition, the Framework
component produces launchers, bootstrap infrastructure and application models
that facilitate the use of Equinox OSGi in end-user product scenarios.

This package will be maintained by the Java Team. It's required to update
the Eclipse ecosystem in Debian and complete the transition to Java 11.



Bug#903616: Recognize NVIDIA BMCs

2018-07-11 Thread dann frazier
Package: ipmitool
Version: 1.8.18-5+b1
Severity: normal

'ipmitool mc info' does not recognize NVIDIA BMCs, such as those on the DGX
family of systems, and instead shows the Manufacturer as "Unknown".

-- 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.16.0-2-amd64 (SMP w/4 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

Versions of packages ipmitool depends on:
ii  libc6  2.27-4
ii  libfreeipmi17  1.5.7-2
ii  libncurses66.1+20180210-4
ii  libreadline7   7.0-5
ii  libssl1.1  1.1.0h-4
ii  libtinfo6  6.1+20180210-4
ii  lsb-base   9.20170808

Versions of packages ipmitool recommends:
ii  openipmi  2.0.25-2

ipmitool suggests no packages.

-- no debconf information



Bug#903483: mozjs52: FTBFS on m68k: not supported by build/moz.configure/init.configure

2018-07-11 Thread John Paul Adrian Glaubitz
On 07/11/2018 01:11 PM, Simon McVittie wrote:
> On Wed, 11 Jul 2018 at 13:00:53 +0200, John Paul Adrian Glaubitz wrote:
>> On 07/10/2018 05:55 PM, John Paul Adrian Glaubitz wrote:
>>> Yes, I've seen that. I've most likely forgotten the hunk in question,
>>> I will provide an updated patch sonish, also one for riscv64.
>>
>> Attaching an updated patch.
> 
> Thanks. Does the result work (at least minimally, e.g. the js52
> interpreter can print("hello, world")) on real m68k hardware?

I just did a testbuild with the testsuite enabled and it seems all tests
pass except for one:

 FAILED! SSN_pattern - 8 = 8 expected: NaN

So, I guess mozjs52 mostly works on m68k.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



Bug#903615: gnome-system-log: Crashes on startup with a GLib-GIO error

2018-07-11 Thread Lee Aurich
Package: gnome-system-log
Version: 3.9.90-4+b1
Severity: important

Dear Maintainer,

Installed grome-system-log on stretch debian (installation is current with all
stable patches).

When I launch from the gnome menu, nothing happens.  Launching from terminal
gives the following error messages:

xx:~$ sudo gnome-system-log
[sudo] password for xx:

(process:9522): GLib-GObject-CRITICAL **: g_param_spec_boxed: assertion
'G_TYPE_IS_BOXED (boxed_type)' failed

(process:9522): GLib-GObject-CRITICAL **: g_object_class_install_property:
assertion 'G_IS_PARAM_SPEC (pspec)' failed

(process:9522): GLib-GObject-CRITICAL **: g_param_spec_boxed: assertion
'G_TYPE_IS_BOXED (boxed_type)' failed

(process:9522): GLib-GObject-CRITICAL **: g_object_class_install_property:
assertion 'G_IS_PARAM_SPEC (pspec)' failed

(process:9522): GLib-GObject-CRITICAL **: g_param_spec_boxed: assertion
'G_TYPE_IS_BOXED (boxed_type)' failed

(process:9522): GLib-GObject-CRITICAL **: g_object_class_install_property:
assertion 'G_IS_PARAM_SPEC (pspec)' failed

(process:9522): GLib-GObject-WARNING **: g_object_set_valist: object class
'GtkTextTag' has no property named 'paragraph-background-gdk'

(gnome-system-log:9522): GLib-GIO-ERROR **: g_menu_item_set_detailed_action:
Detailed action name 'win.filter_find ATA' has invalid format
Trace/breakpoint trap
xx:~$



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

Kernel: Linux 4.9.0-6-amd64 (SMP w/2 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/bash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-system-log depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2+b1
ii  gsettings-desktop-schemas3.22.0-1
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-11+deb9u3
ii  libcairo-gobject21.14.8-1
ii  libcairo21.14.8-1
ii  libgdk-pixbuf2.0-0   2.36.5-2+deb9u2
ii  libglib2.0-0 2.50.3-2
ii  libgtk-3-0   3.22.11-1
ii  libpango-1.0-0   1.40.5-1
ii  libpangocairo-1.0-0  1.40.5-1
ii  policykit-1  0.105-18
ii  zlib1g   1:1.2.8.dfsg-5

gnome-system-log recommends no packages.

Versions of packages gnome-system-log suggests:
ii  yelp  3.22.0-1

-- no debconf information



Bug#888367: qtav: diff for NMU version 1.12.0+ds-4.1

2018-07-11 Thread Pino Toscano
In data mercoledì 11 luglio 2018 23:04:15 CEST, Sebastian Ramacher ha scritto:
> On 2018-07-11 22:53:00, Pino Toscano wrote:
> > In data mercoledì 11 luglio 2018 22:40:42 CEST, Sebastian Ramacher ha 
> > scritto:
> > > Control: tags 888367 + pending
> > > 
> > > Dear maintainer,
> > > 
> > > I've prepared an NMU for qtav (versioned as 1.12.0+ds-4.1) and
> > > uploaded it to DELAYED/2. Please feel free to tell me if I
> > > should delay it longer.
> > 
> > Yes, please cancel this. I can take of this this weekend -- it would
> > have been nice to have a ping regarding the transition, instead of
> > silently NMU'ing.
> 
> I wouldn't have sent a mail if I'd wanted to silently NMU.

Well, thanks I guess ...

> Also James pinged with a patch at the end of May …

He mentioned only the upstream fixes, not any detail regarding the
transition. Knowing whether a transition is still far or is approaching
makes a difference, and it helps to schedule work on a package.

-- 
Pino Toscano

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


Bug#888386: opencv: diff for NMU version 3.2.0+dfsg-4.1

2018-07-11 Thread Sebastian Ramacher
Control: tags 888386 + pending

Dear maintainer,

I've prepared an NMU for opencv (versioned as 3.2.0+dfsg-4.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Cheers
-- 
Sebastian Ramacher
diff -Nru opencv-3.2.0+dfsg/debian/changelog opencv-3.2.0+dfsg/debian/changelog
--- opencv-3.2.0+dfsg/debian/changelog	2017-11-11 13:46:48.0 +0100
+++ opencv-3.2.0+dfsg/debian/changelog	2018-07-11 22:59:18.0 +0200
@@ -1,3 +1,10 @@
+opencv (3.2.0+dfsg-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches: Fix building with ffmpeg 4.0. (Closes: #888386)
+
+ -- Sebastian Ramacher   Wed, 11 Jul 2018 22:59:18 +0200
+
 opencv (3.2.0+dfsg-4) unstable; urgency=medium
 
   * Team upload.
diff -Nru opencv-3.2.0+dfsg/debian/patches/ffmpeg4.0.patch opencv-3.2.0+dfsg/debian/patches/ffmpeg4.0.patch
--- opencv-3.2.0+dfsg/debian/patches/ffmpeg4.0.patch	1970-01-01 01:00:00.0 +0100
+++ opencv-3.2.0+dfsg/debian/patches/ffmpeg4.0.patch	2018-07-11 22:58:45.0 +0200
@@ -0,0 +1,100 @@
+Description: Fix FTBFS with FFmpeg 4.0
+Origin: upstream, https://github.com/opencv/opencv/commit/b1d208891b9f6ae3968730b120a5d0dcbba679d0
+Bug: https://github.com/opencv/opencv/pull/10011
+Bug-Debian: https://bugs.debian.org/888386
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+
+--- a/modules/videoio/src/cap_ffmpeg_impl.hpp
 b/modules/videoio/src/cap_ffmpeg_impl.hpp
+@@ -149,6 +149,10 @@ extern "C" {
+ #define AV_PIX_FMT_GRAY16BE PIX_FMT_GRAY16BE
+ #endif
+ 
++#ifndef PKT_FLAG_KEY
++#define PKT_FLAG_KEY AV_PKT_FLAG_KEY
++#endif
++
+ #if LIBAVUTIL_BUILD >= (LIBAVUTIL_VERSION_MICRO >= 100 \
+ ? CALC_FFMPEG_VERSION(52, 38, 100) : CALC_FFMPEG_VERSION(52, 13, 0))
+ #define USE_AV_FRAME_GET_BUFFER 1
+@@ -1538,7 +1542,11 @@ static AVStream *icv_add_video_stream_FF
+ // some formats want stream headers to be seperate
+ if(oc->oformat->flags & AVFMT_GLOBALHEADER)
+ {
++#if LIBAVCODEC_BUILD > CALC_FFMPEG_VERSION(56, 35, 0)
++c->flags |= AV_CODEC_FLAG_GLOBAL_HEADER;
++#else
+ c->flags |= CODEC_FLAG_GLOBAL_HEADER;
++#endif
+ }
+ #endif
+ 
+@@ -1566,23 +1574,24 @@ static int icv_av_write_frame_FFMPEG( AV
+ #endif
+ int ret = OPENCV_NO_FRAMES_WRITTEN_CODE;
+ 
+-if (oc->oformat->flags & AVFMT_RAWPICTURE) {
++#if LIBAVFORMAT_BUILD < CALC_FFMPEG_VERSION(57, 0, 0)
++if (oc->oformat->flags & AVFMT_RAWPICTURE)
++{
+ /* raw video case. The API will change slightly in the near
+futur for that */
+ AVPacket pkt;
+ av_init_packet();
+ 
+-#ifndef PKT_FLAG_KEY
+-#define PKT_FLAG_KEY AV_PKT_FLAG_KEY
+-#endif
+-
+ pkt.flags |= PKT_FLAG_KEY;
+ pkt.stream_index= video_st->index;
+ pkt.data= (uint8_t *)picture;
+ pkt.size= sizeof(AVPicture);
+ 
+ ret = av_write_frame(oc, );
+-} else {
++}
++else
++#endif
++{
+ /* encode the image */
+ AVPacket pkt;
+ av_init_packet();
+@@ -1740,7 +1749,9 @@ void CvVideoWriter_FFMPEG::close()
+ /* write the trailer, if any */
+ if(ok && oc)
+ {
+-if( (oc->oformat->flags & AVFMT_RAWPICTURE) == 0 )
++#if LIBAVFORMAT_BUILD < CALC_FFMPEG_VERSION(57, 0, 0)
++if (!(oc->oformat->flags & AVFMT_RAWPICTURE))
++#endif
+ {
+ for(;;)
+ {
+@@ -2036,7 +2047,11 @@ bool CvVideoWriter_FFMPEG::open( const c
+ 
+ outbuf = NULL;
+ 
+-if (!(oc->oformat->flags & AVFMT_RAWPICTURE)) {
++
++#if LIBAVFORMAT_BUILD < CALC_FFMPEG_VERSION(57, 0, 0)
++if (!(oc->oformat->flags & AVFMT_RAWPICTURE))
++#endif
++{
+ /* allocate output buffer */
+ /* assume we will never get codec output with more than 4 bytes per pixel... */
+ outbuf_size = width*height*4;
+@@ -2335,7 +2350,11 @@ AVStream* OutputMediaStream_FFMPEG::addV
+ // some formats want stream headers to be seperate
+ if (oc->oformat->flags & AVFMT_GLOBALHEADER)
+ {
+-c->flags |= CODEC_FLAG_GLOBAL_HEADER;
++#if LIBAVCODEC_BUILD > CALC_FFMPEG_VERSION(56, 35, 0)
++c->flags |= AV_CODEC_FLAG_GLOBAL_HEADER;
++#else
++c->flags |= CODEC_FLAG_GLOBAL_HEADER;
++#endif
+ }
+ #endif
+ 
diff -Nru opencv-3.2.0+dfsg/debian/patches/series opencv-3.2.0+dfsg/debian/patches/series
--- opencv-3.2.0+dfsg/debian/patches/series	2017-11-11 13:34:40.0 +0100
+++ opencv-3.2.0+dfsg/debian/patches/series	2018-07-11 22:58:48.0 +0200
@@ -5,3 +5,4 @@
 change_jquery.js_path
 disable_dnn.patch
 fix_VFP_asm.patch
+ffmpeg4.0.patch


signature.asc
Description: PGP signature


Bug#888388: freshplayerplugin: diff for NMU version 0.3.5-1.1

2018-07-11 Thread Sebastian Ramacher
Control: tags 888388 + pending

Dear maintainer,

I've prepared an NMU for freshplayerplugin (versioned as 0.3.5-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Cheers
-- 
Sebastian Ramacher
diff -Nru freshplayerplugin-0.3.5/debian/changelog freshplayerplugin-0.3.5/debian/changelog
--- freshplayerplugin-0.3.5/debian/changelog	2016-05-03 10:08:58.0 +0200
+++ freshplayerplugin-0.3.5/debian/changelog	2018-07-11 23:14:16.0 +0200
@@ -1,3 +1,10 @@
+freshplayerplugin (0.3.5-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches: Fix build with ffmpeg 4.0. (Closes: #888388)
+
+ -- Sebastian Ramacher   Wed, 11 Jul 2018 23:14:16 +0200
+
 freshplayerplugin (0.3.5-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru freshplayerplugin-0.3.5/debian/patches/ffmpeg4.0.patch freshplayerplugin-0.3.5/debian/patches/ffmpeg4.0.patch
--- freshplayerplugin-0.3.5/debian/patches/ffmpeg4.0.patch	1970-01-01 01:00:00.0 +0100
+++ freshplayerplugin-0.3.5/debian/patches/ffmpeg4.0.patch	2018-07-11 23:13:36.0 +0200
@@ -0,0 +1,20 @@
+Description: Fix FTBFS with FFmpeg 4.0
+Origin: backport, https://github.com/i-rinat/freshplayerplugin/commit/934aa9c24d34f8203744b56e4ac6e8599446ca02
+Bug-Debian: https://bugs.debian.org/888388
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/src/ppb_video_decoder.c
 b/src/ppb_video_decoder.c
+@@ -542,9 +542,9 @@ initialize_decoder(struct pp_video_decod
+ goto err;
+ }
+ 
+-if (vd->avcodec->capabilities & CODEC_CAP_TRUNCATED) {
+-trace_info("%s, codec have CODEC_CAP_TRUNCATED\n", __func__);
+-vd->avctx->flags |= CODEC_FLAG_TRUNCATED;
++if (vd->avcodec->capabilities & AV_CODEC_CAP_TRUNCATED) {
++trace_info("%s, codec have AV_CODEC_CAP_TRUNCATED\n", __func__);
++vd->avctx->flags |= AV_CODEC_FLAG_TRUNCATED;
+ }
+ 
+ vd->avctx->opaque = vd;
diff -Nru freshplayerplugin-0.3.5/debian/patches/series freshplayerplugin-0.3.5/debian/patches/series
--- freshplayerplugin-0.3.5/debian/patches/series	2016-05-03 10:08:58.0 +0200
+++ freshplayerplugin-0.3.5/debian/patches/series	2018-07-11 23:13:38.0 +0200
@@ -1 +1,2 @@
 typo-from-lintian.patch
+ffmpeg4.0.patch


signature.asc
Description: PGP signature


Bug#903614: xymond_client not part of xymon-client package

2018-07-11 Thread Ondřej Vadinský
Package: xymon-client
Version: 4.3.28-2

Dear maintainers,

When xymon-client is configured to performed tests locally and no xymon server 
is locally installed, xymonclient.sh fails due to the missing xymond_client 
binary.

Steps to reproduce:
1) set LOCALMODE="yes" in /etc/xymon/xymonclient.cfg
2) restart xymon-client service
3) observe the following error message in /var/log/xymon/xymonclient.log:

/usr/lib/xymon/client/bin/xymonclient.sh: 101: /usr/lib/xymon/client/bin/
xymonclient.sh: /usr/lib/xymon/client/bin/xymond_client: not found

4) obviously, no data is sent to the server, and the client-supplied statuses 
will go purple in due time.

System information:
Debian 9.4, Linux 4.9.0-6-amd64

Suggested fix:
Include xymond_client binary that is part of xymon package into the xymon-
client package and place it at the expected location.

Note:
This is, perhaps, an unintended use, to have a locally configured client 
without xymon server on the same host, however, it enables the host admin to 
set the desired status-checks without the need to contact xymon server admins. 
Since some of these status-checks are highly host-dependent, it may be better 
for the host admin to manage such configuration.

Regards,
Ondřej Vadinský



Bug#903408: Uploading new version of autodep8 to unstable

2018-07-11 Thread Antonio Terceiro
On Wed, Jul 11, 2018 at 09:10:46AM +0200, Rafael Laboissière wrote:
> The packages that use the Octave support of autodep8 are starting to fail on
> ci.d.n.  This will become epidemic.  Please, react to my message below.
> 
> Cheers,
> 
> Rafael
> 
> * Rafael Laboissière  [2018-07-10 13:21]:
> 
> > Hi,
> > 
> > I pushed the commit e8a55fa to the Git repository of autodep8.  This
> > versions introduces changes in support/octave/generate that should fix
> > Bug#903408 and Bug#903409.  These bugs were caused by a change done in
> > version 0.5.4 of the dh-octave-autpkgtest.  The necessary changes were
> > made in this latter package.  Notice that I added a versioned dependency
> > to dh-octave-autpkgtest (>= 0.5.5) in support/octave/generate.  I hope
> > that this is the right way to do it in autodep8.
> > 
> > If there are no objections, I will upload a new version of autodep8 to
> > unstable.

Go ahead.

TBH at this point I think you could just add your name to Uploaders:, and
stop asking for permission. :)

> > I guess that the new version number should be 0.13, instead
> > 0.12.1, shouldn't it?

yes. I have been using versions with the third component for bugfix-only
releases, which is not the case.

> > 
> > Best,
> > 
> > Rafael
> > 
> > P.S.: I guess that Standards-Version can be bumped to 4.1.5 without
> > problem.  I will do it if there are no objections.

do it


signature.asc
Description: PGP signature


Bug#903396: patchelf: Makes some binaries impossible to strip

2018-07-11 Thread Felipe Sateler
Hi,


On Mon, Jul 9, 2018 at 8:33 AM Raphaël Hertzog  wrote:

> Package: patchelf
> Version: 0.9-1
> Severity: important
>
> patchelf suffers from an issue where some of the modified ELF binaries can
> no longer be stripped from their debug symbols with an error message like
> this one:
> > Not enough room for program headers, try linking with -N
>
> This has been fixed in https://github.com/NixOS/patchelf/pull/117
> it would be nice if you could package a new git snapshot of the tool
> so that this fix is included.
>

Unfortunately tests fail with a current git snapshot. More info at the
upstream bug report:

https://github.com/NixOS/patchelf/issues/136

-- 

Saludos,
Felipe Sateler



Bug#888367: qtav: diff for NMU version 1.12.0+ds-4.1

2018-07-11 Thread Sebastian Ramacher
On 2018-07-11 22:53:00, Pino Toscano wrote:
> In data mercoledì 11 luglio 2018 22:40:42 CEST, Sebastian Ramacher ha scritto:
> > Control: tags 888367 + pending
> > 
> > Dear maintainer,
> > 
> > I've prepared an NMU for qtav (versioned as 1.12.0+ds-4.1) and
> > uploaded it to DELAYED/2. Please feel free to tell me if I
> > should delay it longer.
> 
> Yes, please cancel this. I can take of this this weekend -- it would
> have been nice to have a ping regarding the transition, instead of
> silently NMU'ing.

I wouldn't have sent a mail if I'd wanted to silently NMU. Also James pinged
with a patch at the end of May …

Anyway, canceled.

> 
> Thanks,
> -- 
> Pino Toscano



-- 
Sebastian Ramacher


signature.asc
Description: PGP signature


Bug#888367: qtav: diff for NMU version 1.12.0+ds-4.1

2018-07-11 Thread Pino Toscano
In data mercoledì 11 luglio 2018 22:40:42 CEST, Sebastian Ramacher ha scritto:
> Control: tags 888367 + pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for qtav (versioned as 1.12.0+ds-4.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.

Yes, please cancel this. I can take of this this weekend -- it would
have been nice to have a ping regarding the transition, instead of
silently NMU'ing.

Thanks,
-- 
Pino Toscano

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


Bug#888328: motion: diff for NMU version 4.1.1-1.1

2018-07-11 Thread Sebastian Ramacher
Control: tags 888328 + pending

Dear maintainer,

I've prepared an NMU for motion (versioned as 4.1.1-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Cheers
-- 
Sebastian Ramacher
diff -Nru motion-4.1.1/debian/changelog motion-4.1.1/debian/changelog
--- motion-4.1.1/debian/changelog	2018-05-18 08:46:40.0 +0200
+++ motion-4.1.1/debian/changelog	2018-07-11 22:47:11.0 +0200
@@ -1,3 +1,10 @@
+motion (4.1.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches: Fix building with ffmpeg 4.0. (Closes: #888328)
+
+ -- Sebastian Ramacher   Wed, 11 Jul 2018 22:47:11 +0200
+
 motion (4.1.1-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru motion-4.1.1/debian/patches/ffmpeg4.0.patch motion-4.1.1/debian/patches/ffmpeg4.0.patch
--- motion-4.1.1/debian/patches/ffmpeg4.0.patch	1970-01-01 01:00:00.0 +0100
+++ motion-4.1.1/debian/patches/ffmpeg4.0.patch	2018-07-11 22:47:11.0 +0200
@@ -0,0 +1,49 @@
+From ff99988d57f4bcb0a7b381374f8106896bda2b15 Mon Sep 17 00:00:00 2001
+From: James Cowgill 
+Date: Fri, 23 Feb 2018 23:04:33 +
+Subject: [PATCH] Fix build errors with FFmpeg 4.0
+
+---
+ ffmpeg.c | 19 ---
+ 1 file changed, 16 insertions(+), 3 deletions(-)
+
+--- a/ffmpeg.c
 b/ffmpeg.c
+@@ -68,6 +68,19 @@
+ #endif
+ 
+ /*/
++#if (LIBAVCODEC_VERSION_MAJOR >= 57)
++
++#define MY_CODEC_FLAG_GLOBAL_HEADER AV_CODEC_FLAG_GLOBAL_HEADER
++#define MY_CODEC_FLAG_QSCALEAV_CODEC_FLAG_QSCALE
++
++#else
++
++#define MY_CODEC_FLAG_GLOBAL_HEADER CODEC_FLAG_GLOBAL_HEADER
++#define MY_CODEC_FLAG_QSCALECODEC_FLAG_QSCALE
++
++#endif
++
++/*/
+ AVFrame *my_frame_alloc(void){
+ AVFrame *pic;
+ #if (LIBAVFORMAT_VERSION_MAJOR >= 55)
+@@ -538,7 +551,7 @@
+ /* The selection of 8000 in the else is a subjective number based upon viewing output files */
+ if (ffmpeg->vbr > 0){
+ ffmpeg->vbr =(int)(((100-ffmpeg->vbr)*(100-ffmpeg->vbr)*(100-ffmpeg->vbr) * 8000) / 100) + 1;
+-ffmpeg->ctx_codec->flags |= CODEC_FLAG_QSCALE;
++ffmpeg->ctx_codec->flags |= MY_CODEC_FLAG_QSCALE;
+ ffmpeg->ctx_codec->global_quality=ffmpeg->vbr;
+ }
+ }
+@@ -663,7 +676,7 @@
+   ffmpeg->ctx_codec->strict_std_compliance = -2;
+   ffmpeg->ctx_codec->level = 3;
+ }
+-ffmpeg->ctx_codec->flags |= CODEC_FLAG_GLOBAL_HEADER;
++ffmpeg->ctx_codec->flags |= MY_CODEC_FLAG_GLOBAL_HEADER;
+ 
+ retcd = ffmpeg_set_quality(ffmpeg);
+ if (retcd < 0){
diff -Nru motion-4.1.1/debian/patches/series motion-4.1.1/debian/patches/series
--- motion-4.1.1/debian/patches/series	2018-05-18 08:33:41.0 +0200
+++ motion-4.1.1/debian/patches/series	2018-07-11 22:46:49.0 +0200
@@ -1 +1,2 @@
 change-paths_set-debian-paths.patch
+ffmpeg4.0.patch


signature.asc
Description: PGP signature


Bug#903613: gatb-core: "dpkg-buildpackage -A" FTBFS

2018-07-11 Thread Adrian Bunk
Source: gatb-core
Version: 1.4.1+dfsg-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=gatb-core=all=1.4.1%2Bdfsg-2=1530877921=0

...
   debian/rules override_dh_install-indep
make[1]: Entering directory '/<>/gatb-core-1.4.1+dfsg'
dh_install -i
mv debian/gatb-core-testdata/usr/share/doc/gatb-core/test/gatb-core-cppunit 
debian/gatb-core/usr/lib/gatb-core
mv: cannot move 
'debian/gatb-core-testdata/usr/share/doc/gatb-core/test/gatb-core-cppunit' to 
'debian/gatb-core/usr/lib/gatb-core': No such file or directory
make[1]: *** [debian/rules:25: override_dh_install-indep] Error 1



Bug#903612: csound FTBFS on !x86: test hang

2018-07-11 Thread Adrian Bunk
Source: csound
Version: 1:6.11.0~dfsg-1
Severity: serious

https://buildd.debian.org/status/package.php?p=csound=sid
(m68k is building with nocheck)

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
OPCODE6DIR64=obj-aarch64-linux-gnu dh_auto_test
cd obj-aarch64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=3 ninja 
test
[0/1] Running tests...
Test project /<>/obj-aarch64-linux-gnu
  Start  1: testCsoundTypeSystem
 1/12 Test  #1: testCsoundTypeSystem .   Passed0.27 sec
  Start  2: testCsoundMessageBuffer
 2/12 Test  #2: testCsoundMessageBuffer ..   Passed0.09 sec
  Start  3: testCsoundOrcSemantics
 3/12 Test  #3: testCsoundOrcSemantics ...   Passed0.29 sec
  Start  4: testCsoundOrcCompileTest
 4/12 Test  #4: testCsoundOrcCompileTest .   Passed5.05 sec
  Start  5: testChannels
 5/12 Test  #5: testChannels .   Passed0.33 sec
  Start  6: testCsoundDataStructures
 6/12 Test  #6: testCsoundDataStructures .   Passed0.03 sec
  Start  7: testIo
 7/12 Test  #7: testIo ...   Passed0.73 sec
  Start  8: testCircularBuffer
 8/12 Test  #8: testCircularBuffer ...   Passed0.03 sec
  Start  9: testPerfThread
 9/12 Test  #9: testPerfThread ...   Passed   13.07 sec
  Start 10: testDebugger
10/12 Test #10: testDebugger .   Passed0.09 sec
  Start 11: testEngine
E: Build killed with signal TERM after 150 minutes of inactivity



Bug#903491: [marble]

2018-07-11 Thread bugs-debian
Package: marble
Version: 4:17.08.3-3

--- Please enter the report below this line. ---
Upstream bug: https://bugs.kde.org/show_bug.cgi?id=394517

So nobody has proposed something yet. Since contributing to Marble is a
bit complicated (I don't have any account for now), here is a small patch.

Adrien

--- System information. ---
Architecture:
Kernel: Linux 4.16.0-2-amd64

Debian Release: buster/sid
500 unstable ftp.fr.debian.org
500 testing download.jitsi.org
1 experimental ftp.fr.debian.org

--- Package information. ---
Depends (Version) | Installed
===-+-=
marble-data (>= 4:17.08.3-3) | 4:17.08.3-3
marble-plugins (= 4:17.08.3-3) | 4:17.08.3-3
kio | 5.47.0-1
libc6 (>= 2.14) | 2.27-4
libgcc1 (>= 1:3.0) | 1:8.1.0-9
libkf5configcore5 (>= 4.98.0) | 5.47.0-1
libkf5configgui5 (>= 4.97.0) | 5.47.0-1
libkf5configwidgets5 (>= 4.96.0) | 5.47.0-1
libkf5coreaddons5 (>= 4.100.0) | 5.47.0-1
libkf5crash5 (>= 4.96.0) | 5.47.0-1
libkf5i18n5 (>= 4.97.0) | 5.47.0-1
libkf5kiowidgets5 (>= 4.99.0) | 5.47.0-1
libkf5newstuff5 (>= 4.95.0) | 5.47.0-1
libkf5parts5 (>= 4.96.0) | 5.47.0-1
libkf5widgetsaddons5 (>= 4.96.0) | 5.47.0-1
libkf5xmlgui5 (>= 4.98.0) | 5.47.0-1
libmarblewidget-qt5-28 (= 4:17.08.3-3) | 4:17.08.3-3
libqt5core5a (>= 5.9.0~beta) | 5.10.1+dfsg-7
libqt5dbus5 (>= 5.4) | 5.10.1+dfsg-7
libqt5gui5 (>= 5.7.0) | 5.10.1+dfsg-7
libqt5network5 (>= 5.4) | 5.10.1+dfsg-7
libqt5printsupport5 (>= 5.4) | 5.10.1+dfsg-7
libqt5widgets5 (>= 5.4) | 5.10.1+dfsg-7
libqt5xml5 (>= 5.4) | 5.10.1+dfsg-7
libstdc++6 (>= 4.1.1) | 8.1.0-9


Package's Recommends field is empty.

Suggests (Version) | Installed
===-+-===
gosmore |
monav-routing-daemon |
routino |
Index: marble-17.08.3/src/plugins/runner/nominatim-reversegeocoding/OsmNominatimReverseGeocodingRunner.cpp
===
--- marble-17.08.3.orig/src/plugins/runner/nominatim-reversegeocoding/OsmNominatimReverseGeocodingRunner.cpp
+++ marble-17.08.3/src/plugins/runner/nominatim-reversegeocoding/OsmNominatimReverseGeocodingRunner.cpp
@@ -49,7 +49,7 @@ void OsmNominatimRunner::returnNoReverse
 void OsmNominatimRunner::reverseGeocoding( const GeoDataCoordinates  )
 {
 m_coordinates = coordinates;
-QString base = "http://nominatim.openstreetmap.org/reverse?format=xml=1;;
+QString base = "https://nominatim.openstreetmap.org/reverse?format=xml=1;;
 // @todo: Alternative URI with addressdetails=1 could be used for shorther placemark name
 QString query = "=%1=%2=%3";
 double lon = coordinates.longitude( GeoDataCoordinates::Degree );
Index: marble-17.08.3/src/plugins/runner/nominatim-search/OsmNominatimSearchRunner.cpp
===
--- marble-17.08.3.orig/src/plugins/runner/nominatim-search/OsmNominatimSearchRunner.cpp
+++ marble-17.08.3/src/plugins/runner/nominatim-search/OsmNominatimSearchRunner.cpp
@@ -50,7 +50,7 @@ void OsmNominatimRunner::returnNoResults
 
 void OsmNominatimRunner::search( const QString , const GeoDataLatLonBox  )
 {
-QString base = "http://nominatim.openstreetmap.org/search?;;
+QString base = "https://nominatim.openstreetmap.org/search?;;
 QString query = "q=%1=xml=1=%2";
 QString url = QString(base + query).arg(searchTerm).arg(MarbleLocale::languageCode());
 if( !preferred.isEmpty() ) {


Bug#888367: qtav: diff for NMU version 1.12.0+ds-4.1

2018-07-11 Thread Sebastian Ramacher
Control: tags 888367 + pending

Dear maintainer,

I've prepared an NMU for qtav (versioned as 1.12.0+ds-4.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Cheers
-- 
Sebastian Ramacher
diff -Nru qtav-1.12.0+ds/debian/changelog qtav-1.12.0+ds/debian/changelog
--- qtav-1.12.0+ds/debian/changelog	2017-11-23 19:55:30.0 +0100
+++ qtav-1.12.0+ds/debian/changelog	2018-07-11 22:32:35.0 +0200
@@ -1,3 +1,10 @@
+qtav (1.12.0+ds-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches: Fix build with ffmpeg 4.0. (Closes: #888367)
+
+ -- Sebastian Ramacher   Wed, 11 Jul 2018 22:32:35 +0200
+
 qtav (1.12.0+ds-4) unstable; urgency=medium
 
   * Team upload.
diff -Nru qtav-1.12.0+ds/debian/patches/0007-Make-QtAV-build-with-newer-versions-of-FFmpeg.patch qtav-1.12.0+ds/debian/patches/0007-Make-QtAV-build-with-newer-versions-of-FFmpeg.patch
--- qtav-1.12.0+ds/debian/patches/0007-Make-QtAV-build-with-newer-versions-of-FFmpeg.patch	1970-01-01 01:00:00.0 +0100
+++ qtav-1.12.0+ds/debian/patches/0007-Make-QtAV-build-with-newer-versions-of-FFmpeg.patch	2018-07-11 22:31:55.0 +0200
@@ -0,0 +1,122 @@
+From 7f6929b49c25ca475a08f87e8b52aa1642d109dd Mon Sep 17 00:00:00 2001
+From: Felix Matouschek 
+Date: Sat, 11 Nov 2017 10:13:06 +0100
+Subject: [PATCH] Make QtAV build with newer versions of FFmpeg
+
+Some defines changed their name in newer versions of FFmpeg, this
+patch uses preprocessor instructions in AVCompat.h to use the
+correct define names. Also filter names retrieved by
+'avfilter_get_by_name' should be used as const variables in
+libavfilter versions starting at 7.0.0.
+---
+ src/AVMuxer.cpp  |  2 +-
+ src/QtAV/private/AVCompat.h  | 12 
+ src/codec/audio/AudioEncoderFFmpeg.cpp   |  4 ++--
+ src/codec/video/VideoEncoderFFmpeg.cpp   |  2 +-
+ src/filter/LibAVFilter.cpp   |  8 +++-
+ src/subtitle/SubtitleProcessorFFmpeg.cpp |  2 +-
+ 6 files changed, 24 insertions(+), 6 deletions(-)
+
+diff --git a/src/AVMuxer.cpp b/src/AVMuxer.cpp
+index 2f0b40d0..d2eb3dde 100644
+--- a/src/AVMuxer.cpp
 b/src/AVMuxer.cpp
+@@ -124,7 +124,7 @@ AVStream *AVMuxer::Private::addStream(AVFormatContext* ctx, const QString 
+ c->time_base = s->time_base;
+ /* Some formats want stream headers to be separate. */
+ if (ctx->oformat->flags & AVFMT_GLOBALHEADER)
+-c->flags |= CODEC_FLAG_GLOBAL_HEADER;
++c->flags |= AV_CODEC_FLAG_GLOBAL_HEADER;
+ // expose avctx to encoder and set properties in encoder?
+ // list codecs for a given format in ui
+ return s;
+diff --git a/src/QtAV/private/AVCompat.h b/src/QtAV/private/AVCompat.h
+index e387868a..6c38596d 100644
+--- a/src/QtAV/private/AVCompat.h
 b/src/QtAV/private/AVCompat.h
+@@ -456,3 +456,15 @@ const char *get_codec_long_name(AVCodecID id);
+  } } while(0)
+ 
+ #endif //QTAV_COMPAT_H
++
++#if LIBAVCODEC_VERSION_INT < AV_VERSION_INT(56,33,0)
++#define AV_CODEC_FLAG_GLOBAL_HEADER CODEC_FLAG_GLOBAL_HEADER
++#endif
++
++#if LIBAVCODEC_VERSION_INT < AV_VERSION_INT(56,56,100)
++#define AV_INPUT_BUFFER_MIN_SIZE FF_MIN_BUFFER_SIZE
++#endif
++
++#if LIBAVCODEC_VERSION_INT < AV_VERSION_INT(56,56,100)
++#define AV_INPUT_BUFFER_PADDING_SIZE FF_INPUT_BUFFER_PADDING_SIZE
++#endif
+diff --git a/src/codec/audio/AudioEncoderFFmpeg.cpp b/src/codec/audio/AudioEncoderFFmpeg.cpp
+index a74f4f31..3811e11a 100644
+--- a/src/codec/audio/AudioEncoderFFmpeg.cpp
 b/src/codec/audio/AudioEncoderFFmpeg.cpp
+@@ -151,8 +151,8 @@ bool AudioEncoderFFmpegPrivate::open()
+ } else {
+ buffer_size = frame_size*format_used.bytesPerSample()*format_used.channels()*2+200;
+ }
+-if (buffer_size < FF_MIN_BUFFER_SIZE)
+-buffer_size = FF_MIN_BUFFER_SIZE;
++if (buffer_size < AV_INPUT_BUFFER_MIN_SIZE)
++buffer_size = AV_INPUT_BUFFER_MIN_SIZE;
+ buffer.resize(buffer_size);
+ return true;
+ }
+diff --git a/src/codec/video/VideoEncoderFFmpeg.cpp b/src/codec/video/VideoEncoderFFmpeg.cpp
+index 7c5ed42d..671efa7d 100644
+--- a/src/codec/video/VideoEncoderFFmpeg.cpp
 b/src/codec/video/VideoEncoderFFmpeg.cpp
+@@ -245,7 +245,7 @@ bool VideoEncoderFFmpegPrivate::open()
+ applyOptionsForContext();
+ AV_ENSURE_OK(avcodec_open2(avctx, codec, ), false);
+ // from mpv ao_lavc
+-const int buffer_size = qMax(qMax(width*height*6+200, FF_MIN_BUFFER_SIZE), sizeof(AVPicture));//??
++const int buffer_size = qMax(qMax(width*height*6+200, AV_INPUT_BUFFER_MIN_SIZE), sizeof(AVPicture));//??
+ buffer.resize(buffer_size);
+ return true;
+ }
+diff --git a/src/filter/LibAVFilter.cpp b/src/filter/LibAVFilter.cpp
+index 19151204..8993a91f 100644
+--- a/src/filter/LibAVFilter.cpp
 b/src/filter/LibAVFilter.cpp
+@@ -120,7 +120,10 @@ public:
+ // pixel_aspect==sar, pixel_aspect is more compatible
+ QString buffersrc_args = args;
+ qDebug("buffersrc_args=%s", 

Bug#888365: gazebo: diff for NMU version 9.0.0+dfsg5-4.1

2018-07-11 Thread Sebastian Ramacher
Control: tags 888365 + pending

Dear maintainer,

I've prepared an NMU for gazebo (versioned as 9.0.0+dfsg5-4.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Cheers
-- 
Sebastian Ramacher
diff -Nru gazebo-9.0.0+dfsg5/debian/changelog gazebo-9.0.0+dfsg5/debian/changelog
--- gazebo-9.0.0+dfsg5/debian/changelog	2018-03-01 13:12:16.0 +0100
+++ gazebo-9.0.0+dfsg5/debian/changelog	2018-07-11 22:07:57.0 +0200
@@ -1,3 +1,11 @@
+gazebo (9.0.0+dfsg5-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches: Fix build with ffmpeg 4.0. Thanks to James Cowgill for the
+patch. (Closes: #888365)
+
+ -- Sebastian Ramacher   Wed, 11 Jul 2018 22:07:57 +0200
+
 gazebo (9.0.0+dfsg5-4) unstable; urgency=medium
 
   * libqtpropertybrowser-dev is not an optional dependency. Remove arch conditionals
diff -Nru gazebo-9.0.0+dfsg5/debian/patches/0009-ffmpeg4.0.patch gazebo-9.0.0+dfsg5/debian/patches/0009-ffmpeg4.0.patch
--- gazebo-9.0.0+dfsg5/debian/patches/0009-ffmpeg4.0.patch	1970-01-01 01:00:00.0 +0100
+++ gazebo-9.0.0+dfsg5/debian/patches/0009-ffmpeg4.0.patch	2018-07-11 22:07:28.0 +0200
@@ -0,0 +1,38 @@
+Description: Fix FTBFS with FFmpeg 4.0
+Author: Steve Peters 
+Origin: upstream, https://bitbucket.org/osrf/gazebo/commits/0c6e09de8c20d8465b59a364dbb887c462f72afa
+Bug-Debian: https://bugs.debian.org/888365
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/gazebo/common/AudioDecoder.cc
 b/gazebo/common/AudioDecoder.cc
+@@ -255,8 +255,13 @@ bool AudioDecoder::SetFile(const std::st
+ return false;
+   }
+ 
++#if LIBAVCODEC_VERSION_INT >= AV_VERSION_INT(56, 60, 100)
++  if (this->codec->capabilities & AV_CODEC_CAP_TRUNCATED)
++this->codecCtx->flags |= AV_CODEC_FLAG_TRUNCATED;
++#else
+   if (this->codec->capabilities & CODEC_CAP_TRUNCATED)
+ this->codecCtx->flags |= CODEC_FLAG_TRUNCATED;
++#endif
+ 
+   // Open codec
+   if (avcodec_open2(this->codecCtx, this->codec, nullptr) < 0)
+--- a/gazebo/common/Video.cc
 b/gazebo/common/Video.cc
+@@ -143,8 +143,13 @@ bool Video::Load(const std::string &_fil
+ 
+   // Inform the codec that we can handle truncated bitstreams -- i.e.,
+   // bitstreams where frame boundaries can fall in the middle of packets
++#if LIBAVCODEC_VERSION_INT >= AV_VERSION_INT(56, 60, 100)
++  if (codec->capabilities & AV_CODEC_CAP_TRUNCATED)
++this->codecCtx->flags |= AV_CODEC_FLAG_TRUNCATED;
++#else
+   if (codec->capabilities & CODEC_CAP_TRUNCATED)
+ this->codecCtx->flags |= CODEC_FLAG_TRUNCATED;
++#endif
+ 
+   // Open codec
+   if (avcodec_open2(this->codecCtx, codec, nullptr) < 0)
diff -Nru gazebo-9.0.0+dfsg5/debian/patches/series gazebo-9.0.0+dfsg5/debian/patches/series
--- gazebo-9.0.0+dfsg5/debian/patches/series	2018-02-16 02:09:07.0 +0100
+++ gazebo-9.0.0+dfsg5/debian/patches/series	2018-07-11 22:07:34.0 +0200
@@ -3,3 +3,4 @@
 0003-use-system-qtpropertybrowser.patch
 0005-fix-problems-on-manpage.patch
 0008-arial-dejavu-fonts-removed-in-dfsg.patch
+0009-ffmpeg4.0.patch


signature.asc
Description: PGP signature


Bug#903611: syncthing FTBFS on 32bit: FAIL: TestBlockSize

2018-07-11 Thread Adrian Bunk
Source: syncthing
Version: 0.14.48+ds1-1
Severity: serious

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

...
--- FAIL: TestBlockSize (0.00s)
protocol_test.go:381: BlockSize(2147483648), size=16777216, expected 
2097152
protocol_test.go:381: BlockSize(3221225472), size=16777216, expected 
2097152
...



Bug#903610: mpv: FTBFS with python 3.7 as the default python3

2018-07-11 Thread James Cowgill
Source: mpv
Version: 0.27.2-1
Severity: important
Forwarded: https://github.com/mpv-player/mpv/issues/5958
Control: found -1 0.28.2-1

As reported upstream in the above bug, mpv will FTBFS when python 3.7 is
made the default version of python.

MPV fix attempt (upgrading waf):
https://github.com/mpv-player/mpv/pull/5975

Waf commit which fixes this:
https://gitlab.com/ita1024/waf/commit/facdc0b173d933073832c768ec1917c553cb369c

Reverting the build system to python2 should also fix this.

James



signature.asc
Description: OpenPGP digital signature


Bug#903609: python-eventlet FTBFS: test failures

2018-07-11 Thread Adrian Bunk
Source: python-eventlet
Version: 0.20.0-4
Severity: serious
Tags: ftbfs

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

...
I: pybuild base:217: cd 
/build/1st/python-eventlet-0.20.0/.pybuild/cpython2_2.7_eventlet/build; 
python2.7 -m nose tests
..Traceback (most recent call last):
  File "eventlet/hubs/poll.py", line 115, in wait
listener.cb(fileno)
  File "eventlet/backdoor.py", line 66, in switch
greenlets.greenlet.switch(self, *args, **kw)
  File "eventlet/backdoor.py", line 58, in run
console.interact()
  File "/usr/lib/python2.7/code.py", line 240, in interact
self.write("\n")
  File "/usr/lib/python2.7/code.py", line 171, in write
sys.stderr.write(data)
  File "eventlet/backdoor.py", line 36, in write
self.f.flush()
  File "/usr/lib/python2.7/socket.py", line 307, in flush
self._sock.sendall(view[write_offset:write_offset+buffer_size])
  File "eventlet/greenio/base.py", line 390, in sendall
tail = self.send(data, flags)
  File "eventlet/greenio/base.py", line 384, in send
return self._send_loop(self.fd.send, data, flags)
  File "eventlet/greenio/base.py", line 371, in _send_loop
return send_method(data, *args)
error: [Errno 32] Broken pipe
Removing descriptor: 6
SS.SS..SS.S..Python
 2.7.15
...127.0.0.1
 - - [10/Aug/2019 17:22:27] code 400, message Bad request syntax ('X')
127.0.0.1 - - [10/Aug/2019 17:22:27] "X" 400 -
.
--
Ran 619 tests in 58.978s

OK (SKIP=95)
Exception TypeError: "'NoneType' object is not callable" in  ignored
Exception TypeError: "'NoneType' object is not callable" in  ignored
...



Bug#894476: #894476: Solved from the Qt side. (rcc: please honour SOURCE_DATE_EPOCH)

2018-07-11 Thread Lisandro Damián Nicanor Pérez Meyer
El mié., 11 de jul. de 2018 17:12, Vagrant Cascadian 
escribió:

> On 2018-07-11, Lisandro Damián Nicanor Pérez Meyer wrote:
> > Version: 5.11.1+dfsg-1
> >
> > The bug upstream has been closed as invalid (see
> https://bugreports.qt.io/
> > browse/QTBUG-62511) Non the less a workaround has been included in Qt
> 5.11,
> > already in experimental. Setting QT_RCC_SOURCE_DATE_OVERRIDE should be
> enough
> > to solve this issue.
>
> The mentioned upstream bug report is simply marked as invalid without
> explanation.
>

The point is that stuff like CMake can change this value. See comments.


This is (currently) an empty search:
>
>   https://codesearch.debian.net/search?q=QT_RCC_SOURCE_DATE_OVERRIDE


Because it did not scan experimental.


> Do you have a link for QT_RCC_SOURCE_DATE_OVERRIDE present in Debian and
> upstream?  This bug doesn't really seem resolved if that variable isn't
> actually getting set by anything or consumed by anything...
>

Right now, in experimental. We hope to get the transition going soon.

Ideally QT_RCC_SOURCE_DATE_OVERRIDE would get set based on
> SOURCE_DATE_EPOCH, otherwise build tools have an arbitrary growing
> number of variables to keep track of for each library, toolchain,
> language, etc. that implements their own way of doing this sort of
> thing, which kind of defeats the purpose of SOURCE_DATE_EPOCH. *sigh*


That's sadly something we can only "fix" by making packages have the right
value set. As per Qt policy the environment variable needs to be prefixed
with QT, so no chance of directly using SOURCE_DATE_EPOCH.

Feel free to jump in in the upstream bug report if you feel like this is
not enough.

Cheers, Lisandro.


Bug#888377: karlyriceditor: diff for NMU version 1.11-2.1

2018-07-11 Thread Sebastian Ramacher
Control: tags 888377 + pending

Dear maintainer,

I've prepared an NMU for karlyriceditor (versioned as 1.11-2.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Cheers
-- 
Sebastian Ramacher
diff -Nru karlyriceditor-1.11/debian/changelog karlyriceditor-1.11/debian/changelog
--- karlyriceditor-1.11/debian/changelog	2016-03-10 16:39:25.0 +0100
+++ karlyriceditor-1.11/debian/changelog	2018-07-11 22:24:38.0 +0200
@@ -1,3 +1,11 @@
+karlyriceditor (1.11-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix build with ffmpeg 4.0. Thanks to James cowgill for the patch. (Closes:
+#888377)
+
+ -- Sebastian Ramacher   Wed, 11 Jul 2018 22:24:38 +0200
+
 karlyriceditor (1.11-2) unstable; urgency=medium
 
   * Partially unpatch the code because FFmpeg is back in Debian.
diff -Nru karlyriceditor-1.11/debian/patches/ffmpeg4.0.patch karlyriceditor-1.11/debian/patches/ffmpeg4.0.patch
--- karlyriceditor-1.11/debian/patches/ffmpeg4.0.patch	1970-01-01 01:00:00.0 +0100
+++ karlyriceditor-1.11/debian/patches/ffmpeg4.0.patch	2018-07-11 22:24:08.0 +0200
@@ -0,0 +1,34 @@
+Description: Fix FTBFS with FFmpeg 4.0
+Author: James Cowgill 
+Bug-Debian: https://bugs.debian.org/888377
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/src/ffmpegvideoencoder.cpp
 b/src/ffmpegvideoencoder.cpp
+@@ -345,7 +345,7 @@ av_log_set_level(AV_LOG_VERBOSE);
+ 
+ 	// Enable interlacing if needed
+ 	if ( m_videoformat->flags & VIFO_INTERLACED )
+-		videoCodecCtx->flags |= CODEC_FLAG_INTERLACED_DCT;
++		videoCodecCtx->flags |= AV_CODEC_FLAG_INTERLACED_DCT;
+ 
+ 	// Enable multithreaded encoding: breaks FLV!
+ 	//videoCodecCtx->thread_count = 4;
+@@ -373,7 +373,7 @@ av_log_set_level(AV_LOG_VERBOSE);
+ 
+ 	// If we have a global header for the format, no need to duplicate the codec info in each keyframe
+ 	if ( outputFormatCtx->oformat->flags & AVFMT_GLOBALHEADER )
+-		videoCodecCtx->flags |= CODEC_FLAG_GLOBAL_HEADER;
++		videoCodecCtx->flags |= AV_CODEC_FLAG_GLOBAL_HEADER;
+ 
+ 	// Open the codec
+ 	if ( ( err = avcodec_open2( videoCodecCtx, videoCodec, 0 )) < 0 )
+@@ -463,7 +463,7 @@ av_log_set_level(AV_LOG_VERBOSE);
+ 			audioCodecCtx->time_base.den = m_profile->sampleRate;
+ 
+ 			if ( outputFormatCtx->oformat->flags & AVFMT_GLOBALHEADER )
+-audioCodecCtx->flags |= CODEC_FLAG_GLOBAL_HEADER;
++audioCodecCtx->flags |= AV_CODEC_FLAG_GLOBAL_HEADER;
+ 
+ 			// Since different audio codecs support different sample formats, look up which one is supported by this specific codec
+ 			if ( isAudioSampleFormatSupported( audioCodec->sample_fmts, AV_SAMPLE_FMT_FLTP ) )
diff -Nru karlyriceditor-1.11/debian/patches/series karlyriceditor-1.11/debian/patches/series
--- karlyriceditor-1.11/debian/patches/series	2016-03-10 16:39:25.0 +0100
+++ karlyriceditor-1.11/debian/patches/series	2018-07-11 22:24:10.0 +0200
@@ -8,3 +8,4 @@
 0008-Fix-segfault-AVFrame-initialization-Libav-FFmpeg.patch
 0010-Make-qmake-respect-external-build-linking-flags.patch
 ffmpeg2.9.patch
+ffmpeg4.0.patch


signature.asc
Description: PGP signature


Bug#903608: https downloads fail

2018-07-11 Thread Joey Hess
Package: git-annex
Version: 6.20180626-1
Severity: normal

Using this git-annex backport on stable, https downloads fail
with "TlsExceptionHostPort (HandshakeFailed Error_EOF)"

I believe this impacts S3 and WebDav too, I saw it with addurl and importfeed.

This is an old bug in a haskell library, see
https://github.com/vincenthz/hs-tls/issues/140

See also, https://github.com/datalad/datalad-container/issues/18

The non-backport version in stable does not use haskell for http, except
for S3 and WebDav. It might have the same problem for those, but the
backport is affected more badly since it relies on the haskell http
library for all http.

-- 
see shy jo


signature.asc
Description: PGP signature


Bug#903530: pyresample FTBFS with Python 3.7 as supported version

2018-07-11 Thread Adrian Bunk
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On Wed, Jul 11, 2018 at 12:42:09PM +0100, Chris Lamb wrote:
> Adrian,

Chris,

> > This is not the first time that you are blaming me for submitting
> > FTBFS bugs, but it is not required for the submitter to state more
> > than the error message (which I did) - it is the maintainer who
> > is supposed to debug problems.
> 
> This might be true but in Debian aren't we trying to work together as a
> team?
> 
> Whilst you may have submitted this original report with the very best
> of intentions, to reply that you were technically within the rules is
> not a particularly productive response in context and hardly going to
> lead to a quick and amicable conclusion. :)

Does immediate downgrading and closing of the bug without looking
at the contents lead to a quick and amicable conclusion?

And quoting from the two emails by Bas Couwenberg in this bug:

- - "Filing this bug is very premature"
- - "Your bugreports are filed blindly"
- - "your bugreport does not state any specific issue"
- - "I very much hate bugreports like that, which I'm very tempted to just 
   blindly close (with `bts close`) from now on."
- - "Provide better bugreports in the future, or I will start closing them 
   blindly."
- - "The issue that your bugreport template is substandard remains."

Please give a signed answer whether you as DPL consider both the 
contents and the quantity of these statements appropriate for
"working together as a team" in Debian.

> Best wishes,

Thanks in advance
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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAltGZlMACgkQiNJCh6LY
mLHREhAAqfCoi413lV7DoLqgcl31qNblBLqLV7vkWJE9i0RY/Q9C/1cvVVCxe0UC
MeNSukWD1bt0nIg6DF5x0+RPW68m3BnZJCKsCSpwmGtOrBWFfDtl9vQkW0av87Xa
x5DjZ4XLnyNr0e0/CnxPEa3VowDUg6afisp2QeKGFgrWgNOo4wgQ4K1Gj3AOGdsX
fGNNBTUtqgGVHfU3fqQmABoqJ6rLQYDk3HpwRtDtG3Xf+smGn24UDKhl9z64mhKl
bDCaIf3oiGNYjWbEkTa/wucjz3zTfRtVAtw/fBwHyb1DMwbKwTtWjy/6ByxOgdeC
yf70WiXcvt4s3EVIVKo1QSIlPlH9uznlrFlrubQIX61a0QTMoc6ZugAtfevTdpK6
1CeRFT6fh9AX2NUKU9hjynEZQkpF7VNsrI9H6aRJMTNc8xRXVmr0aZF7ho7N7079
82HcfSa3WyjUZQseKhPMht0UrCbblBNGNhLK4y99N156wYyRcWJ7CZYU72UG8jKg
MWtmWQgqBL1UoCDtnDkHXDI8jDuOXLTHzL1fMliwL0FvnpVzbcAmmXHOU1oKxYR5
c0sO+lvEez6PBbuG15OAh29z0yaXtieGWdy8JL/5FaZDJCH8dAyxKo1uUViGUq4r
qeg03kmTjKqaYeqvJJNMLKPmXnZ3+DMkUyGDSVurZOEepwMB1Ug=
=W73T
-END PGP SIGNATURE-



Bug#888335: squeezelite: diff for NMU version 1.8-4.1

2018-07-11 Thread Sebastian Ramacher
Control: tags 888335 + pending

Dear maintainer,

I've prepared an NMU for squeezelite (versioned as 1.8-4.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Cheers
-- 
Sebastian Ramacher
diff -Nru squeezelite-1.8/debian/changelog squeezelite-1.8/debian/changelog
--- squeezelite-1.8/debian/changelog	2016-11-12 15:06:01.0 +0100
+++ squeezelite-1.8/debian/changelog	2018-07-11 22:17:50.0 +0200
@@ -1,3 +1,11 @@
+squeezelite (1.8-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches: Fix build with ffmpeg 4.0. Thanks to James Cowgill for the
+patch. (Closes: #888335)
+
+ -- Sebastian Ramacher   Wed, 11 Jul 2018 22:17:50 +0200
+
 squeezelite (1.8-4) unstable; urgency=medium
 
   * Run wrap-and-sort.
diff -Nru squeezelite-1.8/debian/patches/ffmpeg4.0.patch squeezelite-1.8/debian/patches/ffmpeg4.0.patch
--- squeezelite-1.8/debian/patches/ffmpeg4.0.patch	1970-01-01 01:00:00.0 +0100
+++ squeezelite-1.8/debian/patches/ffmpeg4.0.patch	2018-07-11 22:17:26.0 +0200
@@ -0,0 +1,16 @@
+Description: Fix FTBFS with FFmpeg 4.0
+Author: James Cowgill 
+Bug-Debian: https://bugs.debian.org/888335
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/ffmpeg.c
 b/ffmpeg.c
+@@ -264,7 +264,7 @@ static decode_state ff_decode(void) {
+ 		ff->mmsh_bytes_left = ff->mmsh_bytes_pad = ff->mmsh_packet_len = 0;
+ 
+ 		if (!ff->readbuf) {
+-			ff->readbuf = AV(ff, malloc, READ_SIZE +  FF_INPUT_BUFFER_PADDING_SIZE);
++			ff->readbuf = AV(ff, malloc, READ_SIZE +  AV_INPUT_BUFFER_PADDING_SIZE);
+ 		}
+ 
+ 		avio = AVIO(ff, alloc_context, ff->readbuf, READ_SIZE, 0, NULL, _read_data, NULL, NULL);
diff -Nru squeezelite-1.8/debian/patches/series squeezelite-1.8/debian/patches/series
--- squeezelite-1.8/debian/patches/series	2016-11-12 14:49:21.0 +0100
+++ squeezelite-1.8/debian/patches/series	2018-07-11 22:17:30.0 +0200
@@ -2,3 +2,4 @@
 Makefile-portaudio.patch
 ffmpeg_2.9.patch
 rename-logs.patch
+ffmpeg4.0.patch


signature.asc
Description: PGP signature


Bug#903557: systemd-journal-upload manpages are in the wrong package

2018-07-11 Thread Michael Biebl
Am 11.07.2018 um 11:54 schrieb Julian Calaby:

> The manpages for systemd-journal-upload and systemd-journal-upload.service are
> shipped in the systemd package instead of the systemd-journal-remote where the
> files and binaries they document are shipped.

Thanks for your bug report

/usr/share/man/man8/systemd-journal-remote.socket.8.gz
/usr/share/man/man8/systemd-journal-upload.8.gz
/usr/share/man/man8/systemd-journal-remote.service.8.gz
/usr/share/man/man8/systemd-journal-upload.service.8.gz

I think those man pages all belong into systemd-journal-remote.
Did I miss any?

Regards,
Michael



signature.asc
Description: OpenPGP digital signature


Bug#894476: #894476: Solved from the Qt side. (rcc: please honour SOURCE_DATE_EPOCH)

2018-07-11 Thread Vagrant Cascadian
On 2018-07-11, Lisandro Damián Nicanor Pérez Meyer wrote:
> Version: 5.11.1+dfsg-1
>
> The bug upstream has been closed as invalid (see https://bugreports.qt.io/
> browse/QTBUG-62511) Non the less a workaround has been included in Qt 5.11, 
> already in experimental. Setting QT_RCC_SOURCE_DATE_OVERRIDE should be enough 
> to solve this issue.

The mentioned upstream bug report is simply marked as invalid without
explanation.

This is (currently) an empty search:

  https://codesearch.debian.net/search?q=QT_RCC_SOURCE_DATE_OVERRIDE

Do you have a link for QT_RCC_SOURCE_DATE_OVERRIDE present in Debian and
upstream?  This bug doesn't really seem resolved if that variable isn't
actually getting set by anything or consumed by anything...


Ideally QT_RCC_SOURCE_DATE_OVERRIDE would get set based on
SOURCE_DATE_EPOCH, otherwise build tools have an arbitrary growing
number of variables to keep track of for each library, toolchain,
language, etc. that implements their own way of doing this sort of
thing, which kind of defeats the purpose of SOURCE_DATE_EPOCH. *sigh*


live well,
  vagrant


signature.asc
Description: PGP signature


Bug#903606: tesseract-ocr: tesseract quits with error `libtesseract4: Undefined symbol XYZ.'

2018-07-11 Thread enno
Package: tesseract-ocr
Version: 4.00~git2481-555f6ffc-1
Severity: important

Dear Maintainer,

Trying to use tesseract led to error
`libtesseract4: Undefined symbol [...] pixaDisplayTiledInColumns'

After some research, installing libleptonica-dev, libtesseract-dev and 
upgrading liblept5 tesseract works.

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

Kernel: Linux 4.6.1-tapas (SMP w/4 CPU cores)
Locale: LANG=de_AT@euro, LC_CTYPE=de_AT@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages tesseract-ocr depends on:
ii  libc62.27-3
ii  libcairo21.14.6-1+b1
ii  libfontconfig1   2.13.0-5
ii  libgcc1  1:8-20180402-1
ii  libglib2.0-0 2.56.0-4
ii  libgomp1 8-20180402-1
ii  libicu60 60.2-6
ii  liblept5 1.76.0-1
ii  libpango-1.0-0   1.40.1-1
ii  libpangocairo-1.0-0  1.40.1-1
ii  libpangoft2-1.0-01.40.1-1
ii  libstdc++6   8-20180402-1
ii  libtesseract44.00~git2481-555f6ffc-1
ii  tesseract-ocr-eng1:4.00~git30-7274cfa-1
ii  tesseract-ocr-osd1:4.00~git30-7274cfa-1

tesseract-ocr recommends no packages.

tesseract-ocr suggests no packages.

-- no debconf information



Bug#903607: pjproject: FTBFS due to d-devlibdeps errors

2018-07-11 Thread Sebastian Ramacher
Source: pjproject
Version: 2.7.2~dfsg-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Tags: ftbfs

pjproject currently fails to build:
| d-devlibdeps \
|   --override 's/libopus0-dev/libopus-dev/' \
|   --override 's/libvo-amrwbenc0-dev/libvo-amrwbenc-dev/' \
|   --override 's/libsrtp2-1-dev/libsrtp2-dev/' \
|   debian/libpjproject-dev.substvars debian/lib*/usr/lib/*/lib*.so.*
| devlibs error: There is no package matching [libasound2-dev] and noone 
provides it, please report bug to d-shlibs maintainer
| devlibs error: There is no package matching [libavcodec-dev] and noone 
provides it, please report bug to d-shlibs maintainer
| devlibs error: There is no package matching [libavformat-dev] and noone 
provides it, please report bug to d-shlibs maintainer
| devlibs error: There is no package matching [libavutil-dev] and noone 
provides it, please report bug to d-shlibs maintainer
| devlibs error: There is no package matching [libgsm1-dev] and noone provides 
it, please report bug to d-shlibs maintainer
| devlibs error: There is no package matching [libopencore-amrnb-dev] and noone 
provides it, please report bug to d-shlibs maintainer
| devlibs error: There is no package matching [libopencore-amrwb-dev] and noone 
provides it, please report bug to d-shlibs maintainer
| devlibs error: There is no package matching [libopus-dev] and noone provides 
it, please report bug to d-shlibs maintainer
|  --> libpjproject-dev package from same source package.
| devlibs error: There is no package matching [libsdl2-dev] and noone provides 
it, please report bug to d-shlibs maintainer
| devlibs error: There is no package matching [libspeex-dev] and noone provides 
it, please report bug to d-shlibs maintainer
| devlibs error: There is no package matching [libspeexdsp-dev] and noone 
provides it, please report bug to d-shlibs maintainer
| devlibs error: There is no package matching [libsrtp2-dev] and noone provides 
it, please report bug to d-shlibs maintainer
| devlibs error: There is no package matching [libssl-dev] and noone provides 
it, please report bug to d-shlibs maintainer
| devlibs error: There is no package matching [libswscale-dev] and noone 
provides it, please report bug to d-shlibs maintainer
| devlibs error: There is no package matching [libv4l-dev] and noone provides 
it, please report bug to d-shlibs maintainer
| devlibs error: There is no package matching [libvo-amrwbenc-dev] and noone 
provides it, please report bug to d-shlibs maintainer
| devlibs error: There is no package matching [uuid-dev] and noone provides it, 
please report bug to d-shlibs maintainer
| make[1]: *** [debian/rules:88: override_dh_shlibdeps] Error 1
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:18: binary] Error 2
| dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature


Bug#903593: python3-blends: shouldn't write Packages: list in case the udeb option is set

2018-07-11 Thread Ole Streicher
Ho Wolfgang,

On 11.07.2018 18:40, Wolfgang Schweer wrote:
> The Packages: list now contains all alternative packages instead of only 
> the first one, e.g. tftpd-hpa | atftpd lists both packages which breaks 
> installation. I guess the fix for #785678 caused this.
> 
> The Packages: field doesn't seem to be needed for a valid desc file.
> Please consider to think about the alternatives again or maybe apply 
> this change:

I would prefer to apply your change; mainly because it removes the
special handling of udebs in one place (and fewer special cases is
always better).

However, I am not sure about the required format to udeb .desc files. As
you describe it, the situation is:

* the Package: field is not needed for udebs
* but if it is there and contains alternatives, the installation breaks.

Do I understand you correctly?

Best

Ole



Bug#899189: nmu: unison_2.48.3-1

2018-07-11 Thread Adam D. Barratt
On Tue, 2018-07-10 at 15:00 +0200, Stéphane Glondu wrote:
> On 06/07/2018 03:15, Cyril Brulebois wrote:
[...]
> > > with extra unfriendly debug messages (hey, look at those in the
> > > github
> > > bug tracker, the ones we wanted to get rid of).
> > > 
> > > I thought I'd mention the possibly surprising outcome for people
> > > not
> > > following debian-release@ closely.
> > 
> > Also, that seems to completely invalidate the on-disk cache, which
> > is
> > likely the reason why the first run with an upgraded version (on
> > either
> > side, by the way) can take several (dozens of) minutes instead of a
> > couple of seconds.
> 
> Indeed. Care must be taken at each upgrade of Unison, I think Unison
> users are aware of that. This is not specific to Debian. What was
> specific to Debian was the situation of Unison compiled with a
> version
> of OCaml different from the one that is being distributed alongside,
> which this binNMU is meant to fix.
> 
> > It might have been a good idea to mention that in the binNMU
> > request. It
> > might also be a good idea to document those consequences in some
> > way.
> 
> Sorry. Where would be a good place to document this, now?

If it had been noticed earlier, I'd have suggested a source upload with
a NEWS file explaining the issues.

We /could/ add a note to the point release announcement mail, although
that's a fairly unusual occurrence for an individual package.

Regards,

Adam



Bug#888356: retroarch: diff for NMU version 1.3.6+dfsg1-1.1

2018-07-11 Thread Sebastian Ramacher
Control: tags 888356 + patch
Control: tags 888356 + pending

Dear maintainer,

I've prepared an NMU for retroarch (versioned as 1.3.6+dfsg1-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Cheers
-- 
Sebastian Ramacher
diff -Nru retroarch-1.3.6+dfsg1/debian/changelog retroarch-1.3.6+dfsg1/debian/changelog
--- retroarch-1.3.6+dfsg1/debian/changelog	2016-08-24 03:44:14.0 +0200
+++ retroarch-1.3.6+dfsg1/debian/changelog	2018-07-11 21:35:41.0 +0200
@@ -1,3 +1,10 @@
+retroarch (1.3.6+dfsg1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches: Fix build with ffmpeg 4.0. (Closes: #888356)
+
+ -- Sebastian Ramacher   Wed, 11 Jul 2018 21:35:41 +0200
+
 retroarch (1.3.6+dfsg1-1) unstable; urgency=low
 
   * New upstream release.
diff -Nru retroarch-1.3.6+dfsg1/debian/patches/05_ffmpeg4.0.patch retroarch-1.3.6+dfsg1/debian/patches/05_ffmpeg4.0.patch
--- retroarch-1.3.6+dfsg1/debian/patches/05_ffmpeg4.0.patch	1970-01-01 01:00:00.0 +0100
+++ retroarch-1.3.6+dfsg1/debian/patches/05_ffmpeg4.0.patch	2018-07-11 21:35:18.0 +0200
@@ -0,0 +1,58 @@
+From 4f5fc6e4ad8f21c517fab57a2a37669e419c1423 Mon Sep 17 00:00:00 2001
+From: orbea 
+Date: Mon, 20 Nov 2017 13:08:58 -0800
+Subject: [PATCH] Fix build with ffmpeg snapshots.
+
+Fixes https://github.com/libretro/RetroArch/issues/5717
+---
+ record/drivers/record_ffmpeg.c | 10 +-
+ 1 file changed, 5 insertions(+), 5 deletions(-)
+
+diff --git a/record/drivers/record_ffmpeg.c b/record/drivers/record_ffmpeg.c
+index b74875f293..98369638a7 100644
+--- a/record/drivers/record_ffmpeg.c
 b/record/drivers/record_ffmpeg.c
+@@ -348,7 +348,7 @@ static bool ffmpeg_init_audio(ffmpeg_t *handle)
+ 
+if (params->audio_qscale)
+{
+-  audio->codec->flags |= CODEC_FLAG_QSCALE;
++  audio->codec->flags |= AV_CODEC_FLAG_QSCALE;
+   audio->codec->global_quality = params->audio_global_quality;
+}
+else if (params->audio_bit_rate)
+@@ -358,7 +358,7 @@ static bool ffmpeg_init_audio(ffmpeg_t *handle)
+audio->codec->strict_std_compliance = FF_COMPLIANCE_EXPERIMENTAL;
+ 
+if (handle->muxer.ctx->oformat->flags & AVFMT_GLOBALHEADER)
+-  audio->codec->flags |= CODEC_FLAG_GLOBAL_HEADER;
++  audio->codec->flags |= AV_CODEC_FLAG_GLOBAL_HEADER;
+ 
+if (avcodec_open2(audio->codec, codec, params->audio_opts ? >audio_opts : NULL) != 0)
+   return false;
+@@ -378,7 +378,7 @@ static bool ffmpeg_init_audio(ffmpeg_t *handle)
+if (!audio->buffer)
+   return false;
+ 
+-   audio->outbuf_size = FF_MIN_BUFFER_SIZE;
++   audio->outbuf_size = AV_INPUT_BUFFER_MIN_SIZE;
+audio->outbuf = (uint8_t*)av_malloc(audio->outbuf_size);
+if (!audio->outbuf)
+   return false;
+@@ -490,14 +490,14 @@ static bool ffmpeg_init_video(ffmpeg_t *handle)
+ 
+if (params->video_qscale)
+{
+-  video->codec->flags |= CODEC_FLAG_QSCALE;
++  video->codec->flags |= AV_CODEC_FLAG_QSCALE;
+   video->codec->global_quality = params->video_global_quality;
+}
+else if (params->video_bit_rate)
+   video->codec->bit_rate = params->video_bit_rate;
+ 
+if (handle->muxer.ctx->oformat->flags & AVFMT_GLOBALHEADER)
+-  video->codec->flags |= CODEC_FLAG_GLOBAL_HEADER;
++  video->codec->flags |= AV_CODEC_FLAG_GLOBAL_HEADER;
+ 
+if (avcodec_open2(video->codec, codec, params->video_opts ?
+ >video_opts : NULL) != 0)
diff -Nru retroarch-1.3.6+dfsg1/debian/patches/series retroarch-1.3.6+dfsg1/debian/patches/series
--- retroarch-1.3.6+dfsg1/debian/patches/series	2016-07-20 03:02:56.0 +0200
+++ retroarch-1.3.6+dfsg1/debian/patches/series	2018-07-11 21:35:22.0 +0200
@@ -2,3 +2,4 @@
 02_hide_settings.patch
 03_zlib.patch
 04_add_CPPFLAGS.patch
+05_ffmpeg4.0.patch


signature.asc
Description: PGP signature


Bug#888370: avifile: diff for NMU version 1:0.7.48~20090503.ds-20.1

2018-07-11 Thread Sebastian Ramacher
Control: tags 888370 + pending

Dear maintainer,

I've prepared an NMU for avifile (versioned as 1:0.7.48~20090503.ds-20.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Cheers
-- 
Sebastian Ramacher
diff -Nru avifile-0.7.48~20090503.ds/debian/changelog avifile-0.7.48~20090503.ds/debian/changelog
--- avifile-0.7.48~20090503.ds/debian/changelog	2017-07-25 19:18:07.0 +0200
+++ avifile-0.7.48~20090503.ds/debian/changelog	2018-07-11 21:30:18.0 +0200
@@ -1,3 +1,11 @@
+avifile (1:0.7.48~20090503.ds-20.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches: Fix build against ffmpeg 4.0. Thanks to James Cowgill for
+the patch. (Closes: #888370)
+
+ -- Sebastian Ramacher   Wed, 11 Jul 2018 21:30:18 +0200
+
 avifile (1:0.7.48~20090503.ds-20) unstable; urgency=low
 
   * Bump Standards-Version to 4.0.0: nothing needs to be changed
diff -Nru avifile-0.7.48~20090503.ds/debian/patches/ffmpeg4.0.patch avifile-0.7.48~20090503.ds/debian/patches/ffmpeg4.0.patch
--- avifile-0.7.48~20090503.ds/debian/patches/ffmpeg4.0.patch	1970-01-01 01:00:00.0 +0100
+++ avifile-0.7.48~20090503.ds/debian/patches/ffmpeg4.0.patch	2018-07-11 21:29:48.0 +0200
@@ -0,0 +1,54 @@
+Description: Fix FTBFS with FFmpeg 4.0
+Author: James Cowgill 
+Bug-Debian: https://bugs.debian.org/888370
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/lib/aviread/FFReadStream.cpp
 b/lib/aviread/FFReadStream.cpp
+@@ -69,7 +69,7 @@ FFReadStream::FFReadStream(FFReadHandler
+ 	AVCodec* codec = avcodec_find_decoder(avs->codec->codec_id);
+ 	if (codec && avcodec_open2(m_pAvContext, codec, NULL) == 0)
+ 	{
+-		m_pAvContext->flags |= CODEC_FLAG_TRUNCATED;
++		m_pAvContext->flags |= AV_CODEC_FLAG_TRUNCATED;
+ 		m_pAvContext->skip_frame = AVDISCARD_NONKEY;
+ 		//printf("Opened hurryup decoder %p  %p\n", codec, m_pAvContext->codec->decode);
+ 	}
+--- a/plugins/libffmpeg/FFVideoDecoder.cpp
 b/plugins/libffmpeg/FFVideoDecoder.cpp
+@@ -38,7 +38,7 @@ FFVideoDecoder::FFVideoDecoder(AVCodec*
+ if (0 && m_pFormat->biCompression == fccHFYU)
+ {
+ 	// for now disabled
+-	m_pAvCodec->capabilities &= ~(CODEC_CAP_DRAW_HORIZ_BAND | CODEC_CAP_DR1);
++	m_pAvCodec->capabilities &= ~(AV_CODEC_CAP_DRAW_HORIZ_BAND | AV_CODEC_CAP_DR1);
+ 	AVM_WRITE(m_Info.GetPrivateName(), "if you have troubles - use Win32 codec instead\n");
+ 	m_Caps = (CAPS) (m_Caps | CAP_YUY2);
+ }
+@@ -191,7 +191,7 @@ int FFVideoDecoder::DecodeFrame(CImage*
+ 	const char* drtxt = "doesn't support";
+ 
+ 	m_bDirect = false;
+-	if (m_pAvCodec->capabilities & CODEC_CAP_DR1)
++	if (m_pAvCodec->capabilities & AV_CODEC_CAP_DR1)
+ 	{
+ 	drtxt = "not using";
+ 	if (pImage)
+@@ -296,7 +296,7 @@ int FFVideoDecoder::DecodeFrame(CImage*
+ // try using draw_horiz_band if DR1 is unsupported
+ m_pAvContext->draw_horiz_band =
+ 	(!m_bDirect && pImage && pImage->Format() == IMG_FMT_YV12
+-	 && (m_pAvCodec->capabilities & CODEC_CAP_DRAW_HORIZ_BAND)
++	 && (m_pAvCodec->capabilities & AV_CODEC_CAP_DRAW_HORIZ_BAND)
+ 	 && !pImage->Direction() && render) ? draw_slice : 0;
+ m_pAvContext->opaque = this;
+ 
+@@ -330,7 +330,7 @@ int FFVideoDecoder::DecodeFrame(CImage*
+ 	av_frame_unref(pic);
+ 	return hr;
+ }
+-if (!(m_pAvContext->flags & CODEC_FLAG_TRUNCATED))
++if (!(m_pAvContext->flags & AV_CODEC_FLAG_TRUNCATED))
+ {
+ 	hr = (int)size;
+ 	//m_bUsed = true;
diff -Nru avifile-0.7.48~20090503.ds/debian/patches/series avifile-0.7.48~20090503.ds/debian/patches/series
--- avifile-0.7.48~20090503.ds/debian/patches/series	2017-07-25 19:12:23.0 +0200
+++ avifile-0.7.48~20090503.ds/debian/patches/series	2018-07-11 21:29:50.0 +0200
@@ -14,3 +14,4 @@
 ffmpeg_2.9.patch
 port-to-gcc6.patch
 reproducible-build.patch
+ffmpeg4.0.patch


signature.asc
Description: PGP signature


Bug#892764: stretch-pu: package i3-wm/4.13-1

2018-07-11 Thread Adam D. Barratt
Control: reopen -1

On Wed, 2018-07-11 at 21:15 +0200, Michael Stapelberg wrote:
> Thanks, the upload was accepted.
> 
(into stable-new)

However, the package hasn't made it to stable yet (and given the
timing, unfortunately won't until 9.6), so the p-u bug should stay open
until then.

Regards,

Adam



Bug#900772: closed by Dmitry Smirnov (Bug#900772: fixed in cakephp 2.10.11-1)

2018-07-11 Thread Adrian Bunk
Control: reopen -1

On Tue, Jul 03, 2018 at 12:51:09PM +, Debian Bug Tracking System wrote:
>...
>  cakephp (2.10.11-1) unstable; urgency=medium
>...
>* Depends:
>  - php-mcrypt (Closes: #900772).
>...

cakephp-scripts still depends on php-mcrypt.

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#903011: Workaround to bug 903011

2018-07-11 Thread Ryutaroh Matsumoto
Control: tags -1 + patch

I posted a workaround to the upstream as
https://github.com/systemd/systemd/issues/9512#issuecomment-404270548

I do not think it is a right approach.

Ryutaroh



Bug#888385: pianobar: diff for NMU version 2017.08.30-1.1

2018-07-11 Thread Sebastian Ramacher
Control: tags 888385 + pending

Dear maintainer,

I've prepared an NMU for pianobar (versioned as 2017.08.30-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Cheers
-- 
Sebastian Ramacher
diff -Nru pianobar-2017.08.30/debian/changelog pianobar-2017.08.30/debian/changelog
--- pianobar-2017.08.30/debian/changelog	2017-08-30 17:54:29.0 +0200
+++ pianobar-2017.08.30/debian/changelog	2018-07-11 21:19:06.0 +0200
@@ -1,3 +1,10 @@
+pianobar (2017.08.30-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches: Fix build against ffmpeg 4.0. (Closes: #888385)
+
+ -- Sebastian Ramacher   Wed, 11 Jul 2018 21:19:06 +0200
+
 pianobar (2017.08.30-1) UNRELEASED; urgency=medium
 
   * New upstream release.
diff -Nru pianobar-2017.08.30/debian/patches/ffmpeg4.0.patch pianobar-2017.08.30/debian/patches/ffmpeg4.0.patch
--- pianobar-2017.08.30/debian/patches/ffmpeg4.0.patch	1970-01-01 01:00:00.0 +0100
+++ pianobar-2017.08.30/debian/patches/ffmpeg4.0.patch	2018-07-11 21:18:54.0 +0200
@@ -0,0 +1,35 @@
+From 38b16f9957a7bad74e337100b497ffc04ceb9a54 Mon Sep 17 00:00:00 2001
+From: Lars-Dominik Braun 
+Date: Mon, 16 Apr 2018 18:37:57 +0200
+Subject: [PATCH] Remove deprecated header avfiltergraph.h
+
+Has been merged into avfilter.h. Closes #660.
+---
+ src/player.c | 1 -
+ src/player.h | 1 -
+ 2 files changed, 2 deletions(-)
+
+diff --git a/src/player.c b/src/player.c
+index df962fa8..ac39e385 100644
+--- a/src/player.c
 b/src/player.c
+@@ -36,7 +36,6 @@ THE SOFTWARE.
+ #include 
+ #include 
+ #include 
+-#include 
+ #include 
+ #include 
+ #ifdef HAVE_LIBAVFILTER_AVCODEC_H
+diff --git a/src/player.h b/src/player.h
+index 30107f14..e9482c42 100644
+--- a/src/player.h
 b/src/player.h
+@@ -34,7 +34,6 @@ THE SOFTWARE.
+ #include 
+ #include 
+ #include 
+-#include 
+ #include 
+ 
+ #include "settings.h"
diff -Nru pianobar-2017.08.30/debian/patches/series pianobar-2017.08.30/debian/patches/series
--- pianobar-2017.08.30/debian/patches/series	2017-08-30 17:54:29.0 +0200
+++ pianobar-2017.08.30/debian/patches/series	2018-07-11 21:19:00.0 +0200
@@ -0,0 +1 @@
+ffmpeg4.0.patch


signature.asc
Description: PGP signature


Bug#894476: Add metatada

2018-07-11 Thread Lisandro Damián Nicanor Pérez Meyer
forwarded 894476 https://bugreports.qt.io/browse/QTBUG-62511
thanks

Indeed, that's right. Thanks a lot Bernhard!

-- 
Existe un problema cultural, el que lleva -por ejemplo- a los padres a
comprar una computadora y ponerla en la habitación de los varones.  La
computadora tiende a ser vista como un objeto "masculino", por lo cual
el número de mujeres interesadas es menor.
  Margarita Manterola, Debian Developer, en un mail sobre las mujeres
  en el software libre, LugFi.
  http://listas.fi.uba.ar/pipermail/lug/2005-September/020266.html

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


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


Bug#903218: python3-opengl: fails to install with python3.7 installed

2018-07-11 Thread Simon McVittie
On Wed, 11 Jul 2018 at 11:37:37 -0300, eamanu15 wrote:
> This bug maybe have a relationship with  #902788 python3-minimal needs
> Breaks for software/modules broken by 3.7, isn't?

Yes. First someone needs to fix this bug in python3-opengl, and then
the maintainer of python3.7 needs to add
Breaks: python3-opengl (<< the fixed version).

smcv



Bug#903605: cups: CVE-2018-6553

2018-07-11 Thread Salvatore Bonaccorso
Source: cups
Version: 2.2.1-8
Severity: serious
Tags: patch security
Control: fixed -1 2.2.1-8+deb9u2

Hi,

I'm filling this with severity serious, as it indicates a regression
from stable, given the issue was fixed already via DSA-4243-1 in
2.2.1-8+deb9u2.

CVE-2018-6553[0]:
AppArmor profile issue in cups

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-6553
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6553
[1] https://usn.ubuntu.com/usn/usn-3713-1
[2] https://lists.debian.org/debian-security-announce/2018/msg00172.html

Regards,
Salvatore



Bug#896824: ignition-common: diff for NMU version 1.0.1-1.1

2018-07-11 Thread Sebastian Ramacher
Control: tags 896824 + pending

Dear maintainer,

I've prepared an NMU for ignition-common (versioned as 1.0.1-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Cheers
-- 
Sebastian Ramacher
diff -Nru ignition-common-1.0.1/debian/changelog ignition-common-1.0.1/debian/changelog
--- ignition-common-1.0.1/debian/changelog	2018-02-05 17:10:10.0 +0100
+++ ignition-common-1.0.1/debian/changelog	2018-07-11 20:59:01.0 +0200
@@ -1,3 +1,11 @@
+ignition-common (1.0.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches: Fix build with ffmpeg 4.0. Thanks to James Cowgill for the
+patch. (Closes: #896824)
+
+ -- Sebastian Ramacher   Wed, 11 Jul 2018 20:59:01 +0200
+
 ignition-common (1.0.1-1) unstable; urgency=medium
 
   * Imported Upstream version 0.1.0
diff -Nru ignition-common-1.0.1/debian/patches/0005_ffmpeg4.0.patch ignition-common-1.0.1/debian/patches/0005_ffmpeg4.0.patch
--- ignition-common-1.0.1/debian/patches/0005_ffmpeg4.0.patch	1970-01-01 01:00:00.0 +0100
+++ ignition-common-1.0.1/debian/patches/0005_ffmpeg4.0.patch	2018-07-11 20:58:29.0 +0200
@@ -0,0 +1,51 @@
+Description: Fix FTBFS with FFmpeg 4.0
+Origin: upstream, https://bitbucket.org/ignitionrobotics/ign-common/commits/89d45a69d76e
+Bug: https://bitbucket.org/ignitionrobotics/ign-common/pull-requests/120
+Bug-Debian: https://bugs.debian.org/896824
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/src/AudioDecoder.cc
 b/src/AudioDecoder.cc
+@@ -257,8 +257,13 @@ bool AudioDecoder::SetFile(const std::st
+ return false;
+   }
+ 
++#if LIBAVCODEC_VERSION_INT >= AV_VERSION_INT(56, 60, 100)
++  if (this->data->codec->capabilities & AV_CODEC_CAP_TRUNCATED)
++this->data->codecCtx->flags |= AV_CODEC_FLAG_TRUNCATED;
++#else
+   if (this->data->codec->capabilities & CODEC_CAP_TRUNCATED)
+ this->data->codecCtx->flags |= CODEC_FLAG_TRUNCATED;
++#endif
+ 
+   // Open codec
+   if (avcodec_open2(this->data->codecCtx, this->data->codec, nullptr) < 0)
+--- a/src/Util.cc
 b/src/Util.cc
+@@ -291,8 +291,10 @@ void ignition::common::load()
+   if (first)
+   {
+ first = false;
++#if LIBAVCODEC_VERSION_INT < AV_VERSION_INT(58, 9, 100)
+ avcodec_register_all();
+ av_register_all();
++#endif
+ 
+ #if defined(__linux__) && defined(HAVE_AVDEVICE)
+ avdevice_register_all();
+--- a/src/Video.cc
 b/src/Video.cc
+@@ -164,8 +164,13 @@ bool Video::Load(const std::string &_fil
+ 
+   // Inform the codec that we can handle truncated bitstreams -- i.e.,
+   // bitstreams where frame boundaries can fall in the middle of packets
++#if LIBAVCODEC_VERSION_INT >= AV_VERSION_INT(56, 60, 100)
++  if (codec->capabilities & AV_CODEC_CAP_TRUNCATED)
++this->dataPtr->codecCtx->flags |= AV_CODEC_FLAG_TRUNCATED;
++#else
+   if (codec->capabilities & CODEC_CAP_TRUNCATED)
+ this->dataPtr->codecCtx->flags |= CODEC_FLAG_TRUNCATED;
++#endif
+ 
+   // Open codec
+   if (avcodec_open2(this->dataPtr->codecCtx, codec, nullptr) < 0)
diff -Nru ignition-common-1.0.1/debian/patches/series ignition-common-1.0.1/debian/patches/series
--- ignition-common-1.0.1/debian/patches/series	2018-02-05 17:10:10.0 +0100
+++ ignition-common-1.0.1/debian/patches/series	2018-07-11 20:58:37.0 +0200
@@ -2,3 +2,4 @@
 0003_use_c++11_in_gtest.patch
 0002_disable_gui_test.patch
 0004_disable_workerpool_test.patch
+0005_ffmpeg4.0.patch


signature.asc
Description: PGP signature


Bug#903604: pki-server: uninstallable in sid due to tomcat8.0-user dependency

2018-07-11 Thread Andreas Beckmann
Package: pki-server
Version: 10.5.5-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: close -1 10.6.1-1

Hi,

during a test with piuparts I noticed your package is no longer
installable in sid since libtomcatjss-java was ported to tomcat 8.5.


Cheers,

Andreas



Bug#888336: aubio: diff for NMU version 0.4.5-1.1

2018-07-11 Thread Sebastian Ramacher
Control: tags 888336 + patch
Control: tags 888336 + pending

Dear maintainer,

I've prepared an NMU for aubio (versioned as 0.4.5-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Cheers
-- 
Sebastian Ramacher
diff -Nru aubio-0.4.5/debian/changelog aubio-0.4.5/debian/changelog
--- aubio-0.4.5/debian/changelog	2017-07-24 15:11:01.0 +0200
+++ aubio-0.4.5/debian/changelog	2018-07-11 20:52:59.0 +0200
@@ -1,3 +1,10 @@
+aubio (0.4.5-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches: Fix build with ffmpeg 4.0. (Closes: #888336)
+
+ -- Sebastian Ramacher   Wed, 11 Jul 2018 20:52:59 +0200
+
 aubio (0.4.5-1) unstable; urgency=medium
 
   * New upstream version 0.4.5
diff -Nru aubio-0.4.5/debian/patches/ffmpeg4.0.patch aubio-0.4.5/debian/patches/ffmpeg4.0.patch
--- aubio-0.4.5/debian/patches/ffmpeg4.0.patch	1970-01-01 01:00:00.0 +0100
+++ aubio-0.4.5/debian/patches/ffmpeg4.0.patch	2018-07-11 20:52:28.0 +0200
@@ -0,0 +1,25 @@
+From 5690daf759b473b9d13b4547ef37adc2695cf524 Mon Sep 17 00:00:00 2001
+From: James Cowgill 
+Date: Sun, 25 Feb 2018 14:23:25 +
+Subject: [PATCH] Fix build with FFmpeg 4.0
+
+---
+ src/io/source_avcodec.c | 4 
+ 1 file changed, 4 insertions(+)
+
+diff --git a/src/io/source_avcodec.c b/src/io/source_avcodec.c
+index ccdce807..8197445c 100644
+--- a/src/io/source_avcodec.c
 b/src/io/source_avcodec.c
+@@ -58,7 +58,11 @@
+ #include "fmat.h"
+ #include "source_avcodec.h"
+ 
++#if LIBAVCODEC_VERSION_INT < AV_VERSION_INT(56, 56, 0)
+ #define AUBIO_AVCODEC_MAX_BUFFER_SIZE FF_MIN_BUFFER_SIZE
++#else
++#define AUBIO_AVCODEC_MAX_BUFFER_SIZE AV_INPUT_BUFFER_MIN_SIZE
++#endif
+ 
+ struct _aubio_source_avcodec_t {
+   uint_t hop_size;
diff -Nru aubio-0.4.5/debian/patches/series aubio-0.4.5/debian/patches/series
--- aubio-0.4.5/debian/patches/series	2017-07-21 18:37:14.0 +0200
+++ aubio-0.4.5/debian/patches/series	2018-07-11 20:52:40.0 +0200
@@ -1 +1,2 @@
 local_mathjax.patch
+ffmpeg4.0.patch


signature.asc
Description: PGP signature


Bug#903603: ssh upgrade breaks in some openvz container

2018-07-11 Thread Joey Hess
Package: openssh-server
Version: 1:7.7p1-2
Severity: normal

After upgrading some openvz container at a hosting provider to unstable,
ssh stopped working; incoming connections closed before password prompt.

In auth.log, there was this:

ssh_sandbox_child: setrlimit(RLIMIT_NOFILE, { 0, 0 }): Invalid argument 
[preauth]

Seems like there is no way to disable the sandbox any more, 
and so this may cause problems for openvz users.

That openvz was running kernel version 2.6.32-openvz-042stab127.2. I
have avoided openvz until now, so I don't know if such an outdated
kernel is typical of openvz hosting providers.

I can't find mention of RLIMIT_NOFILE not being supported in that old
kernel version though (even with 0, 0), so it may not be the fault of an
outdated kernel, but a limitation of openvz generally that RLIMIT_NOFILE
doesn't work.

-- 
see shy jo


signature.asc
Description: PGP signature


Bug#903601: Acknowledgement (members does not have Bash completion)

2018-07-11 Thread Bernard Rosset
Severity: wishlist



Bug#903602: ITP: yaha -- find split-read mappings on single-end queries

2018-07-11 Thread Steffen Moeller
Package: wnpp
Severity: wishlist
Owner: Steffen Moeller 

* Package name: yaha
* URL : https://github.com/GregoryFaust/yaha
* License : MIT
  Programming Lang: C/C++
  Description : find split-read mappings on single-end queries

Team-maintained on https://salsa.debian.org/med-team/yaha



Bug#903601: members does not have Bash completion

2018-07-11 Thread Bernard Rosset
Package: members
Version: 20080128-5+nmu1+b1

`members` does not have Bash auto-completion capability on the contrary
of the opposite program `groups`, part of the coreutils package.

To fix that, I suggest adding a new file to the package that would put a
file in the /usr/share/bash-completion/completions/ directory, which
would contain the following script (omitting the sandard
overhead/decoration around):
`complete -g members`

This would then allow `members ` to show a list of available
groups' name.
I tested that successfully.

I am using an up-to-date Devuan 2 Ascii based on top of Debian 9 Stretch
(4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07) x86_64 GNU/Linux).

Bernard Rosset
https://rosset.net/



Bug#903595: python3-wxgtk4.0: workaround provided

2018-07-11 Thread Karsten Hilbert
Package: python3-wxgtk4.0
Version: 4.0.1+dfsg-5
Followup-For: Bug #903595

Scott Talbert provided a workaround which I confirmed fixes the
immediate problem:

apt-get install python3-sip/unstable

Karsten

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'unstable'), 
(500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)

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

Versions of packages python3-wxgtk4.0 depends on:
ii  libc6 2.27-3
ii  libgcc1   1:8.1.0-9
ii  libpython3.6  3.6.6-1
ii  libpython3.7  3.7.0-1
ii  libstdc++68.1.0-9
ii  libwxbase3.0-0v5  3.0.4+dfsg-4
ii  libwxgtk3.0-gtk3-0v5  3.0.4+dfsg-4
ii  python3   3.6.5-3
ii  python3-sip   4.19.12+dfsg-1
ii  python3-six   1.11.0-2

python3-wxgtk4.0 recommends no packages.

Versions of packages python3-wxgtk4.0 suggests:
pn  wx3.0-doc  

-- no debconf information



Bug#903566: libssl1.1.0f: segfault in ERR_clear_error

2018-07-11 Thread Sebastian Andrzej Siewior
On 2018-07-11 14:25:46 [+0200], Bernd Zeimetz wrote:
> Hi,
Hi,

> This is fixed since one year in the openssl 1.1.0 stable branch.

so I do have a little side project where I try to bring the latest 1.1.0
stable release into Debian stable via p-u for reasons like this.

Do I understand this correctly that you have a fix localy and would
like that it does not get lost after the next security update? If so I
would leave it for now and attempt to get this closed via the p-u update
or as part the next CVE fix round via security if they play along.

Sebastian



Bug#903600: RM: flif -- ROM; NPOASR; RC-buggy; CVEs; unresponsive upstream

2018-07-11 Thread Paride Legovini
Package: ftp.debian.org
Severity: normal

Dear ftpmasters,

flif (source package) is affected by several unfixed upstream bugs. Some
of these bugs are security issues, in particular:

  CVE-2018-10971 (Debian bug #898406)
  CVE-2018-10972 (Debian bug #898407)
  CVE-2018-11507 (Debian bug #902188)
  CVE-2018-12109 (Debian bug #902196)

and upstream is not responsive. At the moment no packages depends on any
of the binary packages built from flif and, given the state of the
package, dependencies are to be avoided for the time being. For this
reasons, I would like flif to be removed from unstable. I uploaded a
revision to experimental to keep the package available while making it
clear that there are problems with it. The situation is explained in its
NEWS.Debian.

Thank you,

Paride



Bug#903555: ser2net: replies with WONT COM_PORT on DO COM_PORT

2018-07-11 Thread Marc Haber
tags #903555 confirmed
thanks

On Wed, Jul 11, 2018 at 01:18:48PM +0200, Uwe Kleine-König wrote:
> Looking at the upstream repository this bug was fixed in commit
> 59090a089484654e93ea753b87d66a1af37b41b9 two years ago.

I will package the new upstream version in due time.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421



Bug#870646: gdb: Make source package bootstrappable

2018-07-11 Thread Hector Oron
On Thu, Aug 03, 2017 at 12:09:23PM -0700, Daniel Schepler wrote:
> Source: gdb
> Version: 7.12-6
> Severity: wishlist
> 
> The gdb source package's Build-Depends on texlive-base is creating
> some build dependency cycles - for example:
> 
> texlive-base Depends on texlive-binaries
> texlive-bin Build-Depends on libgs-dev
> ghostscript Build-Depends on libopenjp2-7-dev
> openjpeg2 Build-Depends on dh-apache2
> apache2 Build-Depends on libaprutil1-dev
> apr-util Build-Depends on default-libmysqlclient-dev
> default-libmysqlclient-dev Depends on libmariadbclient-dev-compat
> mariadb-10.1 Build-Depends on gdb
> 
> It would be nice if gdb could be bootstrapped without the
> documentation.  Probably the easiest way would be to split out the
> documentation into a gdb-doc package, and then move texlive-base to
> Build-Depends-Indep.

I would need to have a closer look why we have texlive-base listed, as we 
already split out gdb-doc in a separate non-free source package. If you could 
help testing that would be great, it might take me a bit longer to work on 
that, but it certainly is for a great goal (bootstrapping).

Regards


signature.asc
Description: PGP signature


Bug#903599: module-ladspa-sink.c: Failed to load LADSPA plugin: file not found

2018-07-11 Thread Göran Weinholt
Package: pulseaudio
Version: 12.0-1
Severity: normal

Hello maintainer!

LADSPA plugins can no longer be loaded. Here is a command that used to
work (but I'm not sure when it stopped working):

| pacmd load-module module-ladspa-sink sink_name=binaural 
sink_master=alsa_output.usb-SteelSeries_SteelSeries_Siberia_350-00.analog-stereo
 plugin=bs2b label=bs2b control=700,4.5

The log output:

| Jul 11 18:54:10 teapot pulseaudio[4855]: [pulseaudio] ltdl-bind-now.c: Failed 
to open module bs2b.so: bs2b.so: cannot open shared object file: No such file 
or directory
| Jul 11 18:54:10 teapot pulseaudio[4855]: [pulseaudio] module-ladspa-sink.c: 
Failed to load LADSPA plugin: file not found
| Jul 11 18:54:10 teapot pulseaudio[4855]: [pulseaudio] module.c: Failed to 
load module "module-ladspa-sink" (argument: "sink_name=binaural 
sink_master=alsa_output.usb-SteelSeries_SteelSeries_Siberia_350-00.analog-stereo
 plugin=bs2b label=bs2b control=700,4.5"): initialization failed.

The strace output:

| read(36, "load-module module-ladspa-sink sink_name=binaural 
sink_master=alsa_output.usb-SteelSeries_SteelSeries_Siberia_350-00.analog-stereo
 plugin=bs2b label=bs2b control=700,4.5\n", 1024) = 170
| write(5, "W", 1)= 1
| openat(AT_FDCWD, "/usr/lib/pulse-12.0/modules/module-ladspa-sink.la", 
O_RDONLY) = -1 ENOENT (No such file or directory)
| openat(AT_FDCWD, "/lib/module-ladspa-sink.la", O_RDONLY) = -1 ENOENT (No such 
file or directory)
| openat(AT_FDCWD, "/usr/lib/module-ladspa-sink.la", O_RDONLY) = -1 ENOENT (No 
such file or directory)
| openat(AT_FDCWD, 
"/usr/lib/x86_64-linux-gnu/libfakeroot/module-ladspa-sink.la", O_RDONLY) = -1 
ENOENT (No such file or directory)
| openat(AT_FDCWD, "/usr/local/lib/module-ladspa-sink.la", O_RDONLY) = -1 
ENOENT (No such file or directory)
| openat(AT_FDCWD, "/usr/local/lib/x86_64-linux-gnu/module-ladspa-sink.la", 
O_RDONLY) = -1 ENOENT (No such file or directory)
| openat(AT_FDCWD, "/lib/x86_64-linux-gnu/module-ladspa-sink.la", O_RDONLY) = 
-1 ENOENT (No such file or directory)
| openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/module-ladspa-sink.la", O_RDONLY) 
= -1 ENOENT (No such file or directory)
| access("/usr/lib/pulse-12.0/modules/module-ladspa-sink.so", R_OK) = 0
| openat(AT_FDCWD, "LADSPA_PATH/bs2b.la", O_RDONLY) = -1 ENOENT (No such file 
or directory)
| openat(AT_FDCWD, "/lib/bs2b.la", O_RDONLY) = -1 ENOENT (No such file or 
directory)
| openat(AT_FDCWD, "/usr/lib/bs2b.la", O_RDONLY) = -1 ENOENT (No such file or 
directory)
| openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/libfakeroot/bs2b.la", O_RDONLY) = 
-1 ENOENT (No such file or directory)
| openat(AT_FDCWD, "/usr/local/lib/bs2b.la", O_RDONLY) = -1 ENOENT (No such 
file or directory)
| openat(AT_FDCWD, "/usr/local/lib/x86_64-linux-gnu/bs2b.la", O_RDONLY) = -1 
ENOENT (No such file or directory)
| openat(AT_FDCWD, "/lib/x86_64-linux-gnu/bs2b.la", O_RDONLY) = -1 ENOENT (No 
such file or directory)
| openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/bs2b.la", O_RDONLY) = -1 ENOENT 
(No such file or directory)
| access("LADSPA_PATH/bs2b.so", R_OK) = -1 ENOENT (No such file or 
directory)
| access("/lib/bs2b.so", R_OK)= -1 ENOENT (No such file or 
directory)
| access("/usr/lib/bs2b.so", R_OK)= -1 ENOENT (No such file or 
directory)
| access("/usr/lib/x86_64-linux-gnu/libfakeroot/bs2b.so", R_OK) = -1 ENOENT (No 
such file or directory)
| access("/usr/local/lib/bs2b.so", R_OK)  = -1 ENOENT (No such file or 
directory)
| access("/usr/local/lib/x86_64-linux-gnu/bs2b.so", R_OK) = -1 ENOENT (No such 
file or directory)
| access("/lib/x86_64-linux-gnu/bs2b.so", R_OK) = -1 ENOENT (No such file or 
directory)
| access("/usr/lib/x86_64-linux-gnu/bs2b.so", R_OK) = -1 ENOENT (No such file 
or directory)
| openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/pulseaudio/bs2b.so", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
| openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 52
| fstat(52, {st_mode=S_IFREG|0644, st_size=157721, ...}) = 0
| mmap(NULL, 157721, PROT_READ, MAP_PRIVATE, 52, 0) = 0x7f762009c000
| close(52)   = 0
| access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or 
directory)
| openat(AT_FDCWD, "/lib/x86_64-linux-gnu/bs2b.so", O_RDONLY|O_CLOEXEC) = -1 
ENOENT (No such file or directory)
| openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/bs2b.so", O_RDONLY|O_CLOEXEC) = 
-1 ENOENT (No such file or directory)
| openat(AT_FDCWD, "/lib/bs2b.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
| openat(AT_FDCWD, "/usr/lib/bs2b.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
| munmap(0x7f762009c000, 157721)  = 0
| getpid()= 4855
| sendto(31, "<11>Jul 11 18:54:10 pulseaudio[4855]: [pulseaudio] 
ltdl-bind-now.c: Failed to open module bs2b.so: bs2b.so: cannot open shared 
object file: No such file or directory", 165, MSG_NOSIGNAL, NULL, 0) = 165
| openat(AT_FDCWD, 

Bug#903441: dgit: autopkgtest failures in Ubuntu

2018-07-11 Thread Mattia Rizzolo
On Wed, Jul 11, 2018 at 06:33:45PM +0100, Ian Jackson wrote:
> > Do you think it would be (easily) possible to have the test dir saved to
> > the artifacts only in case of failures?
> 
> Yes, but it wouldn't be a good idea in general.  And I have a handle
> on this bug.

why wouldn't it?  I believe storing extra info on failure is a sane
thing to do in general, that has the potential to help out also in
future failures.

> > Otherwise, I'd just commit the thing mentioned in the other mail (dch -D
> > vs dch -r) and see whatever happens on the next regular upload.
> 
> I think I understand a lot more about what's going on now, after
> reading debchange's source code.  It's a bit of a mess, though.

debchange's code is kind of alive, it grew in a somwhat akward
environment :) (assuming the "mess" refers to dch!)

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature


Bug#903598: devscripts: dch -r [something]

2018-07-11 Thread Mattia Rizzolo
Control: notfound -1 2.17.6+dub9u1
Control: found -1 2.17.6
Control: user devscri...@qa.debian.org
Control: usertag -1 debchange
Control: retitle -1 devscripts: dch -r doesn't do anything with the supplied 
string

(so that unstable is affected as well…)

On Wed, Jul 11, 2018 at 06:37:27PM +0100, Ian Jackson wrote:
> Consider
>   dch -r `foo'
> 
> dch ignores `foo', which is `TEXT', in the sense that `foo' does not
> appear in the resulting changelog entry.  *But* if you don't supply
> `foo' dch runs an editor.  And there's no other way to stop it doing
> so because --no-edit is (unaccountably) not supported.

Ton of things use '' (i.e. empty string).  Including debchange's
testsuite :3

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature


Bug#903220: libconfig-model-dpkg-perl: Please change policy to current version of debian policy in sid

2018-07-11 Thread Dominique Dumont
On Tuesday, 10 July 2018 19:44:42 CEST Mattia Rizzolo wrote:
> I'm CCing the lintian maintainers because I don't think they ever
> thought of that file as a public API, so they might want to be aware of
> this new reverse-dependency.

I can also use Lintian::Data API as done there:

https://salsa.debian.org/lintian/lintian/blob/master/checks/standards-version.pm#L49

Thus the data from the internal file would be used through a public API.

All the best



Bug#903598: devscripts: dch -r [something]

2018-07-11 Thread Ian Jackson
Package: devscripts
Version: 2.17.6+deb9u1
Severity: minor

Consider
  dch -r `foo'

dch ignores `foo', which is `TEXT', in the sense that `foo' does not
appear in the resulting changelog entry.  *But* if you don't supply
`foo' dch runs an editor.  And there's no other way to stop it doing
so because --no-edit is (unaccountably) not supported.

This is all rather odd.  (I need noninteractive dch in the dgit test
suite, so please don't just change it without disucssion...)

Thanks,
Ian.

-- Package-specific info:

--- /etc/devscripts.conf ---

--- ~/.devscripts ---
DEBSIGN_KEYID=0x48B50D39
GREP_EXCUSES_AUTOPKGTESTS=1

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

Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages devscripts depends on:
ii  dpkg-dev  1.18.24
ii  libc6 2.24-11+deb9u3
ii  libfile-homedir-perl  1.00-1
ii  perl  5.24.1-3+deb9u4
ii  python3   3.5.3-1

Versions of packages devscripts recommends:
ii  apt 1.4.8
ii  at  3.1.20-3
ii  curl7.52.1-5+deb9u6
ii  dctrl-tools 2.24-2+b1
ii  debian-keyring  2017.05.28
ii  dput0.12.1
ii  dupload 2.8.4
pn  equivs  
ii  fakeroot1.21-3.1
ii  file1:5.30-1+deb9u1
ii  gnupg   2.1.18-8~deb9u2
ii  gnupg2  2.1.18-8~deb9u2
pn  libdistro-info-perl 
ii  libdpkg-perl1.18.24
ii  libencode-locale-perl   1.05-1
ii  libgit-wrapper-perl 0.047-1
ii  liblist-compare-perl0.53-1
ii  liblwp-protocol-https-perl  6.06-2
ii  libsoap-lite-perl   1.20-1
ii  liburi-perl 1.71-1
ii  libwww-perl 6.15-1
pn  licensecheck
ii  lintian 2.5.50.4
ii  man-db  2.7.6.1-2
ii  patch   2.7.5-1+b2
ii  patchutils  0.3.4-2
ii  python3-debian  0.1.30
pn  python3-magic   
ii  sensible-utils  0.0.9+deb9u1
ii  strace  4.15-2
ii  unzip   6.0-21
ii  wdiff   1.2.2-2
ii  wget1.18-5+deb9u2
ii  xz-utils5.2.2-1.2+b1

Versions of packages devscripts suggests:
pn  adequate 
ii  autopkgtest  4.4
pn  bls-standalone   
ii  build-essential  12.3
pn  check-all-the-things 
pn  cvs-buildpackage 
ii  devscripts-el36.3+nmu1
pn  diffoscope   
pn  disorderfs   
pn  dose-extra   
pn  duck 
ii  faketime 0.9.6-7+b1
ii  gnuplot  5.0.5+dfsg1-6+deb9u1
ii  gpgv 2.1.18-8~deb9u2
pn  how-can-i-help   
ii  libauthen-sasl-perl  2.1600-1
ii  libfile-desktopentry-perl0.22-1
pn  libnet-smtps-perl
pn  libterm-size-perl
ii  libtimedate-perl 2.3000-2
ii  libyaml-syck-perl1.29-1+b2
ii  mailutils [mailx]1:3.1.1-1
pn  mozilla-devscripts   
pn  mutt 
ii  openssh-client [ssh-client]  1:7.4p1-10+deb9u3
pn  piuparts 
pn  ratt 
pn  reprotest
pn  svn-buildpackage 
ii  w3m  0.5.3-34+deb9u1

-- no debconf information



Bug#903441: dgit: autopkgtest failures in Ubuntu

2018-07-11 Thread Ian Jackson
Mattia Rizzolo writes ("Re: Bug#903441: dgit: autopkgtest failures in Ubuntu"):
> On Tue, Jul 10, 2018 at 10:57:03PM +0100, Ian Jackson wrote:
> > Can you run the test on bionic with this attached patch ?
> 
> Alas, apparently the infra doesn't like it.  It seems the test run just
> disappears at some point between the runner and the storage…

Huh.

> Do you think it would be (easily) possible to have the test dir saved to
> the artifacts only in case of failures?

Yes, but it wouldn't be a good idea in general.  And I have a handle
on this bug.

> Otherwise, I'd just commit the thing mentioned in the other mail (dch -D
> vs dch -r) and see whatever happens on the next regular upload.

I think I understand a lot more about what's going on now, after
reading debchange's source code.  It's a bit of a mess, though.

Ian.



Bug#903597: mate-desktop: html tags in notification

2018-07-11 Thread treaki

Package: mate-desktop
Version: 1.18.0-2
Severity: normal

Dear Maintainer,

looks like the battery capacity message is not displayed correctly. 
There are html tags within this message that shouldn't be there. I have 
attached you a screenshot.




   * What led up to the situation?
my well used hardware
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
seen a notification with html tags (see attatchment)
   * What was the outcome of this action?
thought that they shouldnt be there
   * What outcome did you expect instead?
a message without tags about how it is to be formated


thanks and keep up the good work

Cheers

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

Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mate-desktop depends on:
ii  hicolor-icon-theme0.17-1
ii  libatk1.0-0   2.26.1-3
ii  libc6 2.27-2
ii  libcairo-gobject2 1.15.10-1
ii  libcairo2 1.15.10-1
ii  libgdk-pixbuf2.0-02.36.11-1
ii  libglib2.0-0  2.56.1-2
ii  libgtk-3-03.22.29-3
ii  libmate-desktop-2-17  1.18.0-2
ii  libpango-1.0-01.40.14-1
ii  libpangocairo-1.0-0   1.40.14-1
ii  libstartup-notification0  0.12-5
ii  libxrandr22:1.5.1-1
ii  mate-desktop-common   1.18.0-2

Versions of packages mate-desktop recommends:
ii  mate-user-guide  1.18.0-1

mate-desktop suggests no packages.

-- no debconf information


Bug#903441: dgit: autopkgtest failures in Ubuntu

2018-07-11 Thread Mattia Rizzolo
On Tue, Jul 10, 2018 at 10:57:03PM +0100, Ian Jackson wrote:
> Can you run the test on bionic with this attached patch ?

Alas, apparently the infra doesn't like it.  It seems the test run just
disappears at some point between the runner and the storage…

Do you think it would be (easily) possible to have the test dir saved to
the artifacts only in case of failures?
Otherwise, I'd just commit the thing mentioned in the other mail (dch -D
vs dch -r) and see whatever happens on the next regular upload.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature


Bug#903596: openmpi: FTBFS with latest pmix 3.0.0-1

2018-07-11 Thread Frédéric Bonnard
Package: src:openmpi
Version: 3.1.1.real-1
Severity: normal

Dear maintainer,

I see that openmpi 3.1.1.real-1 fails to build on ppc64el :
https://buildd.debian.org/status/fetch.php?pkg=openmpi=ppc64el=3.1.1.real-1=1530562845=0
Trying to reproduce the bug, it failed with an other error and on other
architectures as well : 
---
dh_install
dh_install: Cannot find (any matches for) "usr/bin/orte-dvm" (tried in ., 
debian/tmp)
---

This seems to be related to the latest upload of pmix 3.0.0-1 that has a
different version number PMIX_VERSION_MAJOR (it was 2 before and is now
3).
In this case, config/opal_check_pmi.m4 does not set opal_prun_happy to
yes (and OPAL_WANT_PRUN also).
Without OPAL_WANT_PRUN, orte/tools/Makefile.am just skips build of
orte/tools/prun/prun and orte/tools/orte-dvm/orte-dvm .

I don't know if those utilities makes sense or not with pmix 3 but
actually upstream openmpi skipped those in this case, and if it's not a
bug, openmpi in debian should not package them anymore and that may fix
the build.

Regards.

F.


pgpfmH8umWNiM.pgp
Description: PGP signature


Bug#903595: python3-wxgtk4.0: wx import problem

2018-07-11 Thread Karsten Hilbert
Package: python3-wxgtk4.0
Version: 4.0.1+dfsg-5
Severity: important

ncq@hermes:~$ 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.
>>> import wx
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/wx/__init__.py", line 17, in 

from wx.core import *
  File "/usr/lib/python3/dist-packages/wx/core.py", line 12, in 
from ._core import *
RuntimeError: the sip module implements API v12.0 to v12.4 but the 
wx._core module requires API v12.5

Karsten

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'unstable'), 
(500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)

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

Versions of packages python3-wxgtk4.0 depends on:
ii  libc6 2.27-3
ii  libgcc1   1:8.1.0-9
ii  libpython3.6  3.6.6-1
ii  libpython3.7  3.7.0-1
ii  libstdc++68.1.0-9
ii  libwxbase3.0-0v5  3.0.4+dfsg-4
ii  libwxgtk3.0-gtk3-0v5  3.0.4+dfsg-4
ii  python3   3.6.5-3
ii  python3-sip   4.19.8+dfsg-1+b1
ii  python3-six   1.11.0-2

python3-wxgtk4.0 recommends no packages.

Versions of packages python3-wxgtk4.0 suggests:
pn  wx3.0-doc  

-- no debconf information



Bug#903545: [Qa-jenkins-dev] Bug#903545: reproducible: Please don't vary kernel architecture personality

2018-07-11 Thread Vagrant Cascadian
On 2018-07-11, Christoph Berg wrote:
> the only remaining variation in the postgresql-10 builds is the `uname -m`
> information captured in pg_config.h:
>
> /usr/include/postgresql/10/server/pg_config.h:
> #define PG_VERSION_STR "PostgreSQL 10.4 (Debian 10.4-2.pgdg+1) on 
> x86_64-pc-linux-gnu, compiled by gcc (Debian 7.3.0-18) 7.3.0, 64-bit"
> #define PG_VERSION_STR "PostgreSQL 10.4 (Debian 10.4-2.pgdg+1) on 
> i686-pc-linux-gnu, compiled by gcc (Debian 7.3.0-18) 7.3.0, 64-bit"

> This information is also stored in Makefile.global, which is used by
> extension modules to configure themselves for the PostgreSQL server
> they are targetting:
>
> /usr/lib/postgresql/10/lib/pgxs/src/Makefile.global:
> host_tuple = x86_64-pc-linux-gnu
> host_os = linux-gnu
> host_cpu = x86_64
>
> host_tuple = i686-pc-linux-gnu
> host_os = linux-gnu
> host_cpu = i686

The running kernel shouldn't be used to determine the userspace
architecture.

Using "uname -m" for this in not really accurate or reliable; patching
the Makefiles to use the appropriate architecture information according
to dpkg would be one option for debian-based packages, at least. Not
sure what a good approach for an upstream solution would be off the top
of my head.


> The difference stems from altering the kernel personality to report
> the i686 architecture name even on x86_64 aka amd64 systems.

It doesn't alter the kernel personality, it's running an i386 userland
with an amd64 kernel without changing the personality to match the
userland.


> I think this is damaging an otherwise functional environment, i.e.
> systems should always be running with their native architecture
> (x86_64 on amd64, armv7l on armhf, etc) - otherwise the system is just
> broken. Chroots for related architectures should be using the
> corresponding architecture personality, and indeed, schroot can switch
> personality on entering chroots.

I can see the argument that that is a fairly reasonable expectation, but
I don't think it's safe to assume; code should be more robust to handle
when it isn't true.


> Please don't vary kernel architecture personality for reproducibility
> testing.
>
> (Does (or did) this variation even catch real-world reproducibility
> problems in packages?)

It appears to have caught this bug, and several others like it.


live well,
  vagrant


signature.asc
Description: PGP signature


Bug#903594: please describe package differences to keepassx

2018-07-11 Thread Marc Haber
Package: keepassxc
Version: 2.3.1+dfsg.1-1
Severity: wishlist

Hi,

the package description of keepassxc is rather similiar to the one of
keepassx. This makes it hard for innocent bystander to determine whether
to choose keepassx or keepassxc. Please consider (probably in
cooperation with the keepassx maintainer) to give information in the
package description that might make this decision easier for your users.

Greetings
Marc



Bug#807674: printer-driver-gutenprint: Canon S4500: Papersize A3 is missing.

2018-07-11 Thread Brian Potkin
Gerald, don't forget to send mail to the bug (not just to me). I have
bounced all your previous posts there for you.


On Tue 10 Jul 2018 at 20:51:35 +0200, ing_g_kollenda wrote:

> Am Donnerstag, 5. Juli 2018, 23:44:27 schrieben Sie:
> > On Sat 30 Jun 2018 at 17:20:44 +0100, Brian Potkin wrote:
> > > On Fri 29 Jun 2018 at 16:20:11 +0200, ing_g_kollenda wrote:
> > > > i just installed this ppd as a additional accout for my printer. But it
> > > > is not possible to select a A3 paper size.
> > > > 
> > > > When i look into the .ppd i also do not find a definition for a3 paper.
> > > 
> > > The correct PPD is attached. Please try it with both suggested
> > > techniques and do not forget to mail the bug report when you reply.
> > 
> > Any progress on this?
> > 
> > Regards,
> > 
> > Brian.
> 
> Hello Brian,
> 
> today i found some time for research on the problem.
> 
> First of all i merged the A3 lines into my functional debian .ppd. I made 
> some 
> additional changes with the default paper sizes but with no useful effect.
> The resulting .ppd is Canon-S4500-Neu.ppd.
> 
> I am able to select A3 size. I put A3 paper into the printer. When I print a 
> testpage in A3 size the actual printed area is 21,1cm * 27,3cm, the rest of 
> the print is missing (paper is white). So parts of the frame and the legend 
> (Media Limits ...) of the test page is missing. The same happens if i print a 
> A3 page from another program. The actual printed area is too small. In my 
> understanding i added all necessary lines to the .ppd.
> 
> I made another test and selected the paper size tabloid. This is nearly the 
> size of A3 (less width but a little bit longer). When i print a test page in 
> tabloid the test page is ok (a little bit is missing at the end, because of 
> the shorter paper).
> 
> My original .ppd ist functional for A4 printing (i did noch check other 
> papersizes). It is added as Canon-S4500.ppd.
> 
> In my opinion all seems to be correct. But it isn't. I hope you find the 
> reason why the printed area is too small.
> 
> Thank you for your efforts.

I am going call it a day for the moment. Perhaps a new idea might occur
to me in a while.

Thank you for all your investigations.

Cheers,

Brian.



Bug#900308: xserver-xorg-input-libinput: options not applied after strech->buster upgrade

2018-07-11 Thread Ross Vandegrift
This bug is gone after an upgrade yesterday.  I'm still at 0.27.1-1, so
not sure which package ended up fixing this.  But Xorg.log now shows:

[49.791] (II) config/udev: Adding input device Lite-On Technology Corp. 
ThinkPad USB Keyboard with TrackPoint (/dev/input/mouse2)
[49.791] (**) Lite-On Technology Corp. ThinkPad USB Keyboard with 
TrackPoint: Applying InputClass "DisableTrackPointScrolling"

Ross



Bug#873582: python-boto3 package maintainance

2018-07-11 Thread Eric Evans
[ Alexander Gerasiov ]
> Hello Eric,
> 
> I need fresh version of python-boto3 in my project, but Debian package
> is outdated. I've just updated it in my local repo, but would like to
> upload it to Debian too.
> 
> Would you mind against co-maintenance or may be maintenance under DPM
> Team?

I'd be open to co-maintenance, sure.

-- 
Eric Evans
eevans.sym-link.com



Bug#903593: python3-blends: shouldn't write Packages: list in case the udeb option is set

2018-07-11 Thread Wolfgang Schweer
Package: python3-blends
Version: 0.7.1
Severity: wishlist

Hi,

while testing Debian Edu I noticed that installations fail due to 
an incorrect debian-edu-tasks.desc file.

The Packages: list now contains all alternative packages instead of only 
the first one, e.g. tftpd-hpa | atftpd lists both packages which breaks 
installation. I guess the fix for #785678 caused this.

The Packages: field doesn't seem to be needed for a valid desc file.
Please consider to think about the alternatives again or maybe apply 
this change:

--- a/blends.py 2018-07-11 18:05:17.147774296 +0200
+++ b/blends.py 2018-07-11 18:04:46.795867954 +0200
@@ -438,10 +438,6 @@
 for key, value in self.tests.items():
 d['Test-' + key] = value
 d['Key'] = '\n {}'.format(self.package_name)
-if udeb:
-d['Packages'] = 'list\n ' + \
-  '\n '.join(sorted(d.name for d in itertools.chain(
-  *(self.recommends + self.dependencies
 return d
 
 def update(self, cache):


Wolfgang


signature.asc
Description: PGP signature


Bug#903428: javadocs generated by javahelper include jquery

2018-07-11 Thread Markus Koschany
Hi tony,

Am 10.07.2018 um 05:22 schrieb tony mancill:
[...]
> I'm in favor of dropping the -java-doc packages completely and instead
> using our time and effort to improve the state of our runtime libraries,
> toolchain and application packages.  (It would be a different story if
> we were developing a distribution for Java developers who don't have
> ready access to other sources of documentation, but I have a hard time
> imagining that our users would prefer javadocs over functioning and
> secure libraries.)
> 
>> Well, now we have to convince doku to implement this solution, or at
>> least to accept it, without closing the bug report again. Volunteers?
> 
> Hmm... I choose to believe that the bug (we're talking about [1],
> right?) was mass-closed along with everything else that was open against
> src:openjdk-9.  It seems like a reasonable and very "Debian" approach to
> avoid embedding an available system library.  If we really want javadoc,
> we could resubmit (preferably with a patch).

Yes, I was talking about #883981. There are two main issues with javadoc
at the moment. Firstly the syntax checker has been much more strict
since OpenJDK 8 and we currently work around a couple of problems by
simply ignoring javadoc errors, otherwise a lot more packages would be
RC buggy (FTBFS). Maybe this option will even go away in the future and
this would leave us with the following choice; either fix the underlying
error or drop the -doc package. Since we ship a lot of older or even
unmaintained software, which is still somehow useful to us though, I can
imagine that for some people our corresponding -doc packages are still a
good read because there is no equivalent source on the Internet (anymore).

Sure, that's not the sole reason why we should keep javadoc. My main
argument is that we would risk to overlook javadoc related issues in our
tool chain, if we dropped it completely. There should be at least a way
for people to create their own javadoc packages, preferably without too
much hassle. As long as that works, we could get over the rest. But
everything else is a regression.

And secondly then there is this jquery issue. I don't even know why they
need Javascript while HTML5 could do probably the same or even a better
job. Anyway we could fix this at the packaging level by replacing the
embedded copy with symlinks. There is one issue that remains: Should
-doc packages depend on jquery as well? There is a chance that the JRE
(which pulls in the jquery dependency) is not installed on the system.

So in my opinion it's not a choice between two options, javadoc yes or
no because at least for the jquery part this should be manageable.
However the first step is to acknowledge a problem but if bugs get
closed and everyone is more in favor of dropping javadoc completely,
then I also become rather "Meh".

Regards,

Markus



signature.asc
Description: OpenPGP digital signature


Bug#903592: RFS: xtrkcad/1:5.1.1-2

2018-07-11 Thread Jörg Frings-Fürst
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package: sponsorship-requests
Severity: normal

  
Dear mentors,

  I am looking for a sponsor for my package "xtrkcad"

   Package name: xtrkcad
   Version : 1:5.1.1-2
   Upstream Author : XTrkCAD Developers 

   URL : http://sourceforge.net/projects/xtrkcad-fork/
   License : GPL-2+, Expat, permissive, BSD-1-Clause,
 public-domain
   Section : editors

  It builds those binary packages:

   xtrkcad - CAD program for designing model railroad layouts
xtrkcad-common - CAD program for designing model railroad layouts (common files)

  To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/xtrkcad


  Alternatively, one can download the package with dget using this
command:

dget -x 
https://mentors.debian.net/debian/pool/main/x/xtrkcad/xtrkcad_5.1.1-2.dsc


  Changes since the last upload:

  [ Jörg Frings-Fürst ]
  * New debian/patches/0100-messages_h.patch:
- Fix FTBFS at mipsel.
  * debian/control:
- Switch Vcs-* to new location.
  * Declare compliance with Debian Policy 4.1.5 (No changes needed).



  Regards,
   Jörg Frings-Fürst
- -- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema:  SYR8SJXB
Wire: @joergfringsfuerst
Skype:joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAltGL8wACgkQCfifPIyh
0l2WGQ/9GSEON9clbUlOVZbEGuHNvrdCWln90f0eCLirq3koRBI5sH1Xbbs6M4PK
sreHYysn0GxbjNcSO5C9/odB1bswB0hPn06r640N6TV8LgTfLfdXTxGn6VXsw8C3
VYbiOXcAY4RnJIa5tjRXnGB0weLx/L3UnnDoXeaKwtaw7oR+PeQ4Wx6Gs57HNZYM
CaAB5yroCNH/Zy6UbU05JnFGGWEXBNTumdqjT5X6QI77SNBB6hXdTubtSnnXTmQt
Pt3tT2bwGCadr2Yx++dNyRk1Ae9ZrIBYRgVrOx+Gmy9d3A5mkNItnEEpiz9d2b5N
IVFZexARwmEITnVbsjnHc+uGejlllMuRr8vVHkRwS6VhxMfZUewOEtDXxxsE4Ayr
B16uiFy5kP3jJ1Z/9Jc7kbn79Zlg+Kpee6z1lHDR8zwun09Cooddixne6iGbKCQi
mk5I9Wd4T5+SAih3jlyNCnIP/AC4QQCQ3MRRpp59zM7oTdOXuFCxOakQ9znoEMq/
X/BIicbS3YhoaBpP5v5atHMQb087wEbl3Q3s7rUs+Wy65ZNgBdJvJY0sxPA9u17N
RPG1M6IPX4GXiOPbWZa4P+ILCHD5N66OrjWIMdIbgoJbhXKCLDXS/mphhxVAxw6g
JytEtpv9YXupfACJqV4Z2ki3Os6P6S0PkjU9Rm1SBp0p85SWu6s=
=MwyJ
-END PGP SIGNATURE-



Bug#902361: [pkg-go] Bug#902361: Bug#902361: golang-pault-go-archive: Please update to >= 0.0~git20180624.470edde

2018-07-11 Thread Michael Stapelberg
As you have probably guessed by now, I’m very pressed on time. If someone
else could do it, I’d prefer that.

On Mon, Jun 25, 2018 at 4:21 PM, Benjamin Drung <
benjamin.dr...@profitbricks.com> wrote:

> Am Montag, den 25.06.2018, 10:16 -0400 schrieb Paul R. Tagliamonte:
> > I'm happy to tag a release for whoever's packaging. File a bug on the
> > repo before you want to dput 
>
> Michael, will you update the package?
>
> --
> Benjamin Drung
> System Developer
> Debian & Ubuntu Developer
>
> ProfitBricks GmbH
> Greifswalder Str. 207
> 10405 Berlin
>
> Email: benjamin.dr...@profitbricks.com
> URL: https://www.profitbricks.de
>
> Sitz der Gesellschaft: Berlin
> Registergericht: Amtsgericht Charlottenburg, HRB 125506 B
> Geschäftsführer: Achim Weiss, Matthias Steinberg, Christoph Steffens
>
> ___
> Pkg-go-maintainers mailing list
> pkg-go-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/
> pkg-go-maintainers
>



-- 
Best regards,
Michael


Bug#903591: tmpfiles.d file: Line references path below legacy directory /var/run/ in log

2018-07-11 Thread Anthony DeRobertis
Package: postgresql-common
Version: 191
Severity: minor
File: /usr/lib/tmpfiles.d/postgresql.conf

Got this from logcheck:

Jul 10 02:14:18 Zia systemd-tmpfiles[8623]: 
[/usr/lib/tmpfiles.d/postgresql.conf:2] Line references path below legacy 
directory /var/run/, updating /var/run/postgresql → /run/postgresql; please 
update the tmpfiles.d/ drop-in file accordingly.

Apparently systemd complains about /var/run instead of /run now.

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

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

Versions of packages postgresql-common depends on:
ii  adduser   3.117
ii  debconf [debconf-2.0] 1.5.67
ii  lsb-base  9.20170808
ii  postgresql-client-common  191
ii  procps2:3.3.15-2
ii  ssl-cert  1.0.39
ii  ucf   3.0038

Versions of packages postgresql-common recommends:
ii  e2fsprogs  1.44.2-1
ii  logrotate  3.11.0-0.1

Versions of packages postgresql-common suggests:
ii  libjson-perl  2.97001-1

-- Configuration Files:
/etc/postgresql-common/createcluster.conf changed:
ssl = on
cluster_name = '%v/%c'
stats_temp_directory = '/var/run/postgresql/%v-%c.pg_stat_tmp'
log_line_prefix = '%%m [%%p] %%q%%u@%%d '
add_include_dir = 'conf.d'
include_dir '/etc/postgresql-common/createcluster.d'


-- debconf information:
  postgresql-common/catversion-bump:
* postgresql-common/ssl: true
* postgresql-common/obsolete-major:


Bug#901254: gnome-terminal: unable to init server, failed with result 'signal', segfault at 8

2018-07-11 Thread Guillaume Morin
I am experiencing the same issue.  Fwiw the workaround listed in
https://bugzilla.redhat.com/show_bug.cgi?id=1353953 (for a similar
problem) allows me to start gnome-terminal in a shell:
DBUS_SESSION_BUS_ADDRESS=""
eval `dbus-launch --sh-syntax --exit-with-session`

Also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868461 seems to
be the same bug.

-- 
Guillaume Morin 



Bug#903590: general: REBOOT command shuts system off Pi3B+ without rebooting. Even kills the power, i.e. the red light on the Pi goes out

2018-07-11 Thread Jack
Package: general
Severity: grave
Tags: d-i
Justification: renders package unusable

Dear Maintainer,



   * What led up to the situation? Updated to the late June 2018 release of 
Rasbian from March 2018 release
   * What exactly did you do (or not do) that was effective (or
 ineffective)? Reboot.
   * What was the outcome of this action? Shutdown my Pi 3B+, and corrupted my 
USB Boot HDD
   * What outcome did you expect instead? normal re-boot




-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux 9.4 (stretch)
Release:9.4
Codename:   stretch
Architecture: armv7l

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



Bug#903574: Error 2304 in GDM login page when i use smartcard to decrypt disk and to login into Gnome Session

2018-07-11 Thread Guilhem Moulin
Control: reassign -1 cryptsetup-initramfs
Control: retitle -1 opensc: can't use smartcard after pivot_root because pcscd 
isn't killed at local-bottom stage
Control: tag -1 pending

Hi,

On Wed, 11 Jul 2018 at 15:05:47 +0200, Pascal Vibet - ADACIS wrote:
> In /usr/share/initramfs-tools/scripts/local-top/cryptopensc, PSCSD process is 
> start and go in background. But the PID is not store, so i fix it with:
> 36a37
>> echo $? > /var/run/pcscd.pid

I assume you meant ‘$!’ not ‘$?’ here [0].  Thanks for the patch, I
just applied it with minor modifications:


https://salsa.debian.org/cryptsetup-team/cryptsetup/commit/8190cb3bc8a4bb4205abc5f66376a2586896e6df

Cheers,
-- 
Guilhem.

[0] 
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_05_02


signature.asc
Description: PGP signature


Bug#903589: transition: uwsgi

2018-07-11 Thread Andreas Beckmann
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

uwsgi seems to track its abi via a virtual package and therefore didn't
get an automatic tracker. The packages are already in sid ...

Package: uwsgi-core
Source: uwsgi
Version: 2.0.15-12
Provides: uwsgi-abi-8ecc7b0491fca07eb2d7b0c9aaeb180f

Package: uwsgi-core
Source: uwsgi
Version: 2.0.17.1-1
Provides: uwsgi-abi-a411bb8664cd85ae0fd852d2f665558a

I'm not sure whether the hash is the same on all architectures or how
many packages are affected (piuparts found 4 so far), so I'm providing
a ben file based on the haskell one rather than a list of binNMUs.
(Also uwsgi currently ftbfs on some architectures and still building on
others.)

Ben file:

title = "uwsgi";
is_affected = .depends ~ /uwsgi-abi-.*/;
is_good = !.edos-debcheck ~ /uninstallable/;
is_bad = .edos-debcheck ~ /uninstallable/;

Andreas

PS: I have nothing to do with these packages.



Bug#901562: invesalius is marked for autoremoval from testing

2018-07-11 Thread Andreas Tille
On Wed, Jul 11, 2018 at 12:18:28PM -0300, Thiago Franco Moraes wrote:
> 
> I was thinking the second option. I'll create a new version tag,
> something like 3.1.9997, then I'll have a tarball with this version.
> Also, I'll package it using Python3.

Perfect.

Kind regards

   Andreas.

-- 
http://fam-tille.de



Bug#894629: dropping ITP

2018-07-11 Thread Lumin
control: retitle -1 RFP: spacy/2.0.10 -- Industrial-strength Natural Language 
Processing (NLP) with Python and Cython
control: noowner -1

lack of time.



Bug#889951: dropping ITP

2018-07-11 Thread Lumin
control: retitle -1 RFP: nanopb/0.3.9 -- Protocol Buffers with small code size
control: noowner

lack of time.



Bug#903588: dkms-autopkgtest test-builds all binary packages

2018-07-11 Thread Debian/GNU
Package: dkms
Version: 2.3-3
Severity: normal

Dear Maintainer,

Thanks for providing a dkms-autopkgtest script to ease deb-ci!

Unfortunately, it seems that this script can only be used in the most trivial
cases, where a single binary package (providing the dkms module) is build from a
source package.
For source packages that build multiple (independent) binary packages, the test
seems to always fail.

notably, the script tries to build dkms modules out of each binary package
listed in d/control.
however, this only works for the most trivial dkms packages (where only a single
binary package is built)

probably the script should take an (optional) list of arguments to specify
which binary packages it should test.

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

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

Versions of packages dkms depends on:
ii  build-essential  12.5
ii  coreutils8.28-1
ii  dpkg-dev 1.19.0.5
ii  gcc  4:7.3.0-3
ii  kmod 25-1
ii  make 4.2.1-1
ii  patch2.7.6-2

Versions of packages dkms recommends:
ii  fakeroot 1.23-1
ii  linux-headers-amd64  4.16+94
ii  lsb-release  9.20170808
ii  sudo 1.8.23-1

Versions of packages dkms suggests:
pn  menu
pn  python3-apport  

-- no debconf information



  1   2   3   >