Bug#862024: Split More Widely Used Plugins into a Separate Package

2017-12-12 Thread VA
I second this wish, the upgrade suddenly takes a lot of space for who 
knows which obscure format.




Bug#786470: debian-policy: [copyright-format] Add an optional “License-Grant” field

2017-12-12 Thread Steve Langasek
On Thu, Nov 30, 2017 at 09:27:30AM +, Simon McVittie wrote:
> I think the License-Grant field is a useful addition to the format,
> resolving some issues around whether License is meant to be the license,
> the license grant or both, and I would like to be able to start using it.

I strongly disagree with this.  I think this adds more syntax without adding
any more information.

The License: field is already very consistently used to contain whatever
details of the license are required to be shipped with the package - either
a full text of a license, or a license grant with a pointer to
/usr/share/common-licenses.  If people feel that it's insufficiently obvious
that this is the correct usage of the field, by all means, let's document
that better; but let's not make a backwards-incompatible change to the
syntax that doesn't benefit users of the file.

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature


Bug#871727: grinder: FTBFS when debhelper does not export PERL_USE_UNSAFE_INC

2017-12-12 Thread Andreas Tille
Control: tags -1 help

I'm hereby following the kind hint below to get in touch with the Debian
Perl team. :-)

Thanks for any help

  Andreas.

On Thu, Aug 10, 2017 at 06:33:37PM -0400, Dominic Hargreaves wrote:
> Source: grinder
> Version: 0.5.4-1
> Severity: normal
> User: debian-p...@lists.debian.org
> Usertags: debhelper-use-unsafe-inc-removal
> 
> This package FTBFS when debhelper is changed to not export
> PERL_USE_UNSAFE_INC to the build environment. This export was added in
> 2016 at the same time that '.' was removed from INC by default, to
> avoid breakage, but was a temporary change.
> 
> As well as allowing us to (eventually) remove this export from debhelper,
> fixing this bug in your package will also help upstream, since this
> change has been made in perl 5.26 upstream.
> 
> Additionally, it's possible that the problem may also exist at runtime
> for your package (though from experience this is less likely).
> 
> Note that the rebuild testing was against a locally-modified version
> of debhelper, but you can get the same effect by setting debhelper
> compat level 11 in your package, which also removes the same
> export.
> 
> For information about how to fix this class of issues, please refer
> to the upstream release notes (in particular, 'Script authors' and
> 'Module Authors'):
> 
> http://perldoc.perl.org/perldelta.html#Removal-of-the-current-directory-(%22.%22)-from-%40INC
> 
> The relevant build failure logs are below.
> 
> not ok 4 - use t::TestUtils;
> #   Failed test 'use t::TestUtils;'
> #   at t/00-load.t line 12.
> # Tried to use 't::TestUtils'.
> # Error:  Can't locate t/TestUtils.pm in @INC (you may need to install 
> the t::TestUtils module) (@INC contains: inc blib/lib blib/arch /etc/perl 
> /usr/local/lib/x86_64-linux-gnu/perl/5.26.0 /usr/local/share/perl/5.26.0 
> /usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 
> /usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 
> /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at t/00-load.t 
> line 12.
> # BEGIN failed--compilation aborted at t/00-load.t line 12.
> # Testing Grinder 0.5.4, Perl 5.026000, /usr/bin/perl
> 1..4
> 
> Please feel feel free to get in touch with the Debian Perl team at
>   debian-p...@lists.debian.org if you need any more information or
> assistance to fix this issue.  
> 
> Cheers,
> Dominic.
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
> 

-- 
http://fam-tille.de



Bug#851066: flashplugin-nonfree: Mismatch between detected and available versions (Download file not available at people.debian.org)

2017-12-12 Thread Gianluigi Tiesi
Package: flashplugin-nonfree
Followup-For: Bug #851066

please use the attached script, it gets and parses vesion directly without sha 
or checksums
#!/bin/sh

# Copyright (C) 2006-2014 Bart Martens 
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License version 2 as
# published by the Free Software Foundation.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program.  If not, see .

set -e

return_0() {
return 0
}

trap "return_0" 0

die_hard() {
echo "ERROR: $1" >&2
echo "More information might be available at:" >&2
echo "  http://wiki.debian.org/FlashPlayer; >&2
exit 1
}

[ `whoami` = "root" ] || die_hard "must be root"

show_usage() {
echo "Usage:"
echo "  update-flashplugin-nonfree --install"
echo "  update-flashplugin-nonfree --uninstall"
echo "  update-flashplugin-nonfree --status"
echo "Additional options:"
echo "  --verbose"
echo "  --quiet"
exit 1
}

getopt_temp=`getopt -o iusfvqn --long 
install,uninstall,status,fast,verbose,quiet -n 'update-flashplugin-nonfree' -- 
"$@"` || show_usage
eval set -- "$getopt_temp" || show_usage

ACTION=none
fast=no
verbose=no
quiet=no

GREP_OPTIONS=

if [ -e /proc/cpuinfo ]
then
hassse2=yes
grep -q "^flags.*: .* sse2 " /proc/cpuinfo || grep -q "^flags.*: .* 
sse2$" /proc/cpuinfo || hassse2=no
else
hassse2=unknown
fi

while [ true ]
do
case "$1" in
-i|--install)
ACTION="--install"
shift
;;
-u|--uninstall)
ACTION="--uninstall"
shift
;;
-s|--status)
ACTION="--status"
shift
;;
-f|--fast)
fast=yes
shift
;;
-v|--verbose)
verbose=yes
shift
;;
-q|--quiet)
quiet=yes
shift
;;
--)
shift
break
;;
*)
echo "Internal error!" >&2
exit 1
;;
esac
done

[ "$ACTION" != "none" -a $# -eq 0 ] || show_usage
[ "$quiet" != "yes" ] || verbose=no

[ "$verbose" != "yes" ] || echo "options : $getopt_temp"

UNPACKDIR=`mktemp -d /tmp/flashplugin-nonfree.XX` || die_hard "mktemp 
failed"
echo "$UNPACKDIR" | grep -q "^/tmp/flashplugin-nonfree\." || die_hard "paranoia"
cd "$UNPACKDIR" || die_hard "cd failed"

[ "$verbose" != "yes" ] || echo "temporary directory: $UNPACKDIR"

do_cleanup() {
[ "$verbose" != "yes" ] || echo "cleaning up temporary directory 
$UNPACKDIR ..."
cd /
echo "$UNPACKDIR" | grep -q "^/tmp/flashplugin-nonfree\." || die_hard 
"paranoia"
rm -rf "$UNPACKDIR"
}

die_hard_with_a_cleanup() {
return_0
do_cleanup
die_hard "$1"
}

trap "die_hard_with_a_cleanup interrupted" INT

fix_missing_symlink() {

LANG=C update-alternatives --display flash-mozilla.so > /dev/null 2>&1 \
|| return 0

LANG=C update-alternatives --display flash-mozilla.so \
| grep -q "link currently absent" \
|| return 0

[ "$verbose" != "yes" ] || echo "link currently absent, trying to fix"

update-alternatives --auto flash-mozilla.so > /dev/null 2>&1 || true
}

warning_about_alternatives() {

letswarn="no"
LANG=C update-alternatives --display flash-mozilla.so \
| grep "link currently points to 
/usr/lib/flashplugin-nonfree/libflashplayer.so" \
> /dev/null 2>&1 || \
cat <<-EOF

How to use predefined priorities to
automatically select one implementation of "flash"
between the multiple installed alternatives :

update-alternatives --auto flash-mozilla.so

How to manually select one implementation of "flash"
between the multiple installed alternatives :

update-alternatives --config flash-mozilla.so

EOF
}

cachedir=/var/cache/flashplugin-nonfree

wgetquiet=' -nv -q '
wgetfast='-t 3 -T 15 '
wgetalways=' -nd -P . '
wgetprogress=' -v --progress=dot:default '

[ "$verbose" != "yes" ] 

Bug#866073: bioperl: autopkgtest regression

2017-12-12 Thread Andreas Tille
Control: tags -1 help

Hi,

I admit I need help of the Debian Perl team to tackle this.  The issue
persists also in the new version 1.7.2 of bioperl.  Any help would be
welcome.

Kind regards

 Andreas.

On Tue, Jun 27, 2017 at 07:59:00AM +0200, Graham Inggs wrote:
> Source: bioperl
> Version: 1.7.1-2
> 
> Hi Maintainer
> 
> Autopgktests for bioperl started failing on 2017-06-19 [1].  This is
> close to the upload of perl 5.24.1-4, in case it is relevant.
> 
> Regards
> Graham
> 
> 
> [1] https://ci.debian.net/packages/b/bioperl/unstable/amd64/
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
> 

-- 
http://fam-tille.de



Bug#856984: fis-gtm: please enable openssl support

2017-12-12 Thread Andreas Tille
Hi Sebastian,

it would be nice if you could answer the question below.  Otherwise
we would set the bug to wontfix for the moment.

Thank you

Andreas.

On Wed, Mar 29, 2017 at 08:50:57PM +, Shah, Amul wrote:
> If I understood your question correctly, you are asking for the fis-gtm 
> package to either enable openssl OR drop the libssl-dev requirement.
> 
> We dropped the openssl using encryption plugin libraries from the distributed 
> package because of the "openssl advertising clause". To work around the 
> advertising clause, we distribute our encryption plugin libraries as source, 
> letting the end users that desire encryption support compile it for 
> themselves. So we can't enable openssl.
> 
> The fis-gtm package builds the encryption plugin sources as a compatibility 
> test build. That compatibility test build alerted us to the upcoming changes 
> in openssl 1.1. So we won't drop the libssl-dev requirement.
> 
> If the above makes sense, I would like to close this bug. If you have some 
> other option, let me know.
> 
> Thanks,
> Amul
> 
> The information contained in this message is proprietary and/or confidential. 
> If you are not the intended recipient, please: (i) delete the message and all 
> copies; (ii) do not disclose, distribute or use the message in any manner; 
> and (iii) notify the sender immediately. In addition, please be aware that 
> any message addressed to our domain is subject to archiving and review by 
> persons other than the intended recipient. Thank you.
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
> 

-- 
http://fam-tille.de



Bug#884274: ITP: deepin-qt5dxcb-plugin -- Qt platform theme integration plugin for DDE

2017-12-12 Thread Boyuan Yang
Package: wnpp
Severity: wishlist
Owner: Boyuan Yang <073p...@gmail.com>
X-Debbugs-CC: debian-de...@lists.debian.org 
pkg-deepin-de...@lists.alioth.debian.org

* Package name: deepin-qt5dxcb-plugin
  Version : 1.1.5
  Upstream Author : Deepin Technology Co., Ltd.
* URL : https://github.com/linuxdeepin/qt5dxcb-plugin
* License : GPL-3+
  Programming Lang: C++/Qt
  Description : Qt platform theme integration plugin for DDE

Deepin's qt5dxcb-plugin is the Qt platform integration plugin for Deepin
Desktop Environment. It provides an abstract interface between Deepin
applications and Qt tookit for further application theme customization.

It is part of Deepin software and DDE (Deepin Desktop Environment).

I intend to co-maintain this package inside pkg-deepin group.

Regards,
Boyuan Yang

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


Bug#883624: transition: libkf5kipi + marble 17.08

2017-12-12 Thread Pino Toscano
In data sabato 9 dicembre 2017 23:48:10 CET, Pino Toscano ha scritto:
> Uploaded libkf5kipi, marble and libkf5kgeomap few hours ago, and all of
> them already built everywhere.

Can you please rebuild also digikam in experimental?

Thanks,
-- 
Pino Toscano

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


Bug#884273: RM: kalgebra [armel hurd-i386 kfreebsd-amd64 kfreebsd-i386 mips mips64el powerpc ppc64el s390x] -- ROM; requires QtWebEngine

2017-12-12 Thread Pino Toscano
Package: ftp.debian.org
Severity: normal
Control: block 883622 by -1

Hi,

the new version of src:kalgebra requires QtWebEngine for the main
interface: as result, two out of three binaries now are built only on
few architectures.  Hence, please remove kalgebra and kalgebra-common
on the following architectures:
  armel hurd-i386 kfreebsd-amd64 kfreebsd-i386 mips mips64el powerpc
  ppc64el s390x

Thanks,
-- 
Pino



Bug#884272: RM: kuser -- ROM; dead upstream, no more used

2017-12-12 Thread Pino Toscano
Package: ftp.debian.org
Severity: normal

Hi,

please remove kuser: it is an old application, which has not seen new
upstream releases in the last couple of years, and nothing pulls it
anymore.  Plasma 5 already provides an own control modue for managing
users.

Thanks,
-- 
Pino



Bug#884271: nmu: cnrun_2.1.0-1

2017-12-12 Thread Andreas Beckmann
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

nmu cnrun_2.1.0-1 . ANY . experimental . -m "Rebuild against libgsl23."

libgsl2 is gone (at least on the release architectures).


Andreas



Bug#884270: RM: kdeartwork -- ROM; dead upstream, no more used

2017-12-12 Thread Pino Toscano
Package: ftp.debian.org
Severity: normal

Hi,

please remove kdeartwork: it is an old source, which has not seen new
upstream releases in the last couple of years, and nothing pulls it
anymore.

Thanks,
-- 
Pino



Bug#883987: rheolef: FTBFS error: partial specialization ... after instantiation ...

2017-12-12 Thread Graham Inggs
On 12 December 2017 at 21:58, Pierre Saramito  wrote:
>> I think the thing to do here is reassign this bug to src:boost1.62 and
>> mark that it affects src:rheolef.
>
> Do you known how to do that with the Debian bug system ?

You can send mail to cont...@bugs.debian.org to manipulate bugs [1].
In one in email, you can have multiple commands; e.g. 'reassign' and
'affects', and manipulate multiple, even unrelated, bugs.
When merging, the newer bugs always get merged into the oldest bug.
Remember to end your list of commands with 'thanks' or one of the
other recognized commands to stop processing.

[1] https://www.debian.org/Bugs/server-control



Bug#884261: libgl1-mesa-dev: libGL.so is missing from 17.2.5-1

2017-12-12 Thread Julien Cristau
Control: tag -1 moreinfo

On 12/12/2017 07:10 PM, Tom Anderson wrote:
> Package: libgl1-mesa-dev
> Version: 13.0.6-1+b2
> Severity: important
> 
There's some confusion between Subject and the above pseudo-header about
actual affected version.

> The filelist for libgl1-mesa-dev shows libGL.so [1], but the downloaded .deb
> [2] doesn't have libGL.so, making linking programs with -lGL impossible.
> 
> [1] https://packages.debian.org/sid/amd64/libgl1-mesa-dev/filelist
> [2] https://packages.debian.org/sid/amd64/libgl1-mesa-dev/download
> 
libgl1-mesa-dev 17.2.5-1 depends on libglvnd-dev, which does ship libGL.so.

Cheers,
Julien



Bug#883972: samba: FTBFS on kfreebsd: error: storage size of 'cr' isn't known

2017-12-12 Thread Andrew Bartlett
On Wed, 2017-12-13 at 06:03 +0100, Timur I. Bakeyev wrote:
> Hi, guys!

(skip really helpful background)

> I wonder, would it be possible to replace getsockopt(2) here with the
> sendmsg()/recvmsg() and 'SCM_CREDS' type of message, like described
> here, for ex:
> 
> https://davejingtian.org/2015/02/17/retrieve-pid-from-the-packet-in-u
> nix-domain-socket-a-complete-use-case-for-recvmsgsendmsg/
> 
> This seems be less Linux-specific way of obtaining remote peer PID.

Thanks Timur,

Are you able to take charge of this, bring this up on samba-technical
and work with the CTDB folks to find a fix?

Thanks,

Andrew Bartlett
-- 
Andrew Bartlett   http://samba.org/~abartlet/
Authentication Developer, Samba Team  http://samba.org
Samba Developer, Catalyst IT  http://catalyst.net.nz/services/samba



Bug#884239: build-depends on python-django-allauth (not yet in debian)

2017-12-12 Thread Daniel Baumann
close 884239
thanks

Hi,

sorry for the noise, I was mislead by
https://packages.qa.debian.org/python-django-allauth not redirecting to
https://packages.qa.debian.org/d/django-allauth.html; should have
checked better.

Regards,
Daniel



Bug#849864: Bug#883170: Bug#849864: paxrat: Please run paxrat during (early) boot

2017-12-12 Thread intrigeri
Santiago R.R.:
> On Mon, 16 Jan 2017 17:50:15 +0100 intrigeri  wrote:
>> santiag...@riseup.net:
>> > I am not expert on writing systemd units, and I am unable to play with
>> > this soon. So it would be great if you could propose a patch :-)
>> 
>> Sure. I might do it once I start using paxrat on systems without
>> live-config (but paxrat is less needed on those systems, so perhaps
>> I'll go with one of the other options instead).

> Something like the attached would do the trick?

Sorry, my interest in paxrat went down to zero since the grsec
patchset is not available as freely as it used to.

Cheers,
-- 
intrigeri



Bug#884232: ffmpeg: CVE-2017-17555

2017-12-12 Thread Salvatore Bonaccorso
Control: reassign -1 src:aubio 0.4.5-1

Hi Carl,

On Tue, Dec 12, 2017 at 11:20:42PM +0100, Carl Eugen Hoyos wrote:
> This is not a bug in FFmpeg:
> aubio initializes libswresample with 2 channels and then passes data
> that contains just one channel.
> 
> That cant really work or how could it ?
> swresample has no knowledge about what is in the array except what it
> is told
> There are multiple ways to provide this information to swr
> 
> (Answer from Michael on ffmpeg-security)

Thanks for your's and MIchael's analysis/comment. So let's reassign
this to src:aubio since it would need to be fixed there.

Regards,
Salvatore



Bug#884269: samtools: FTBFS: bam_sort.c:43:10: fatal error: htslib/hts_os.h: No such file or directory

2017-12-12 Thread Andreas Beckmann
Source: samtools
Version: 1.6-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

samtools/experimental FTBFS:

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

gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -I.-Wdate-time -D_FORTIFY_SOURCE=2 -c -o 
bam_sort.o bam_sort.c
bam_sort.c:43:10: fatal error: htslib/hts_os.h: No such file or directory
 #include "htslib/hts_os.h"
  ^
compilation terminated.
Makefile:126: recipe for target 'bam_sort.o' failed
make[2]: *** [bam_sort.o] Error 1


Andreas



Bug#884268: kdenlive: Rendering to .webm crashes.

2017-12-12 Thread Kingsley G. Morse Jr.
Package: kdenlive
Version: 17.08.3-2
Severity: normal

Hi Patrick,

I like the free .webm video format.

kdenlive used to render to it for me.

Unfortunately, now it crashes.

Here's how:

1.) $ kdenlive

2.) File->New->Full HD 1080->HD 1080p 25 fps

3.) Project->Add color clip->Clip Color = black

4.) Drag the color clip from

the project bin 

to

the time line

5.) (red) Render (button)
->Generic (HD for web, mobile devices...)
->WebM - the widespread free format (VP8/Vorbis)

6.) Render to File (button)

I expected to see

Rendering finished in 

in the render window's Job Queue tab.

Unfortunately, I saw

Rendering crashed.

The render window's Job Queue tab has an error log
that says

[webm @ 0x9bd0b080] Using AVStream.codec to
pass codec parameters to muxers is deprecated,
use AVStream.codecpar instead. [webm @
0x9bd0b080] Using AVStream.codec to pass codec
parameters to muxers is deprecated, use
AVStream.codecpar instead

Rendering to the 

Lossless/HQ .mkv (HuffYUV (huffyuv + flac) 

format works OK.

ffmpeg can convert that .mkv file to .webm with

$ ffmpeg -i tmp/black.mkv tmp/black.webm

I hoped to find diagnostic info in kdenlive's
render log.

Unfortunately, I couldn't find the log.

See bug 884267.

Thanks,
Kingsley

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 4.4.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages kdenlive depends on:
ii  ffmpeg   7:3.4.1-1
ii  kded55.37.0-2
ii  kdenlive-data17.08.3-2
ii  kinit5.37.0-2
ii  kio  5.37.0-2
ii  libc62.25-3
ii  libgcc1  1:7.2.0-17
ii  libgl1-mesa-glx [libgl1] 17.1.3-2
ii  libglu1-mesa [libglu1]   9.0.0-2.1
ii  libkf5archive5   5.28.0-2
ii  libkf5attica55.37.0-2
ii  libkf5auth5  5.37.0-2
ii  libkf5bookmarks5 5.37.0-2
ii  libkf5codecs55.37.0-2
ii  libkf5completion55.37.0-2
ii  libkf5configcore55.37.0-2
ii  libkf5configgui5 5.37.0-2
ii  libkf5configwidgets5 5.37.0-2
ii  libkf5coreaddons55.37.0-2
ii  libkf5crash5 5.37.0-2
ii  libkf5dbusaddons55.37.0-2
ii  libkf5filemetadata3  5.37.0-2
ii  libkf5guiaddons5 5.28.0-1
ii  libkf5i18n5  5.37.0-2
ii  libkf5iconthemes55.37.0-2
ii  libkf5itemviews5 5.37.0-2
ii  libkf5jobwidgets55.37.0-2
ii  libkf5kiocore5   5.37.0-2
ii  libkf5kiofilewidgets55.37.0-2
ii  libkf5kiowidgets55.37.0-2
ii  libkf5newstuff5  5.37.0-2
ii  libkf5newstuffcore5  5.37.0-2
ii  libkf5notifications5 5.37.0-2
ii  libkf5notifyconfig5  5.37.0-2
ii  libkf5service-bin5.37.0-2
ii  libkf5service5   5.37.0-2
ii  libkf5solid5 5.37.0-2
ii  libkf5sonnetui5  5.28.0-2+b1
ii  libkf5textwidgets5   5.37.0-2
ii  libkf5widgetsaddons5 5.37.0-2
ii  libkf5xmlgui55.37.0-2
ii  libmlt++36.4.1-6+b1
ii  libmlt6  6.4.1-6+b1
ii  libqt5concurrent55.9.2+dfsg-4
ii  libqt5core5a 5.9.2+dfsg-6
ii  libqt5dbus5  5.9.2+dfsg-6
ii  libqt5gui5   5.9.2+dfsg-6
ii  libqt5network5   5.9.2+dfsg-6
ii  libqt5qml5   5.9.2-3
ii  libqt5quick5 5.9.2-3
ii  libqt5script55.9.2+dfsg-1
ii  libqt5svg5   5.9.2-3
ii  libqt5webkit55.212.0~alpha2-5
ii  libqt5widgets5   5.9.2+dfsg-6
ii  libqt5xml5   5.9.2+dfsg-6
ii  libstdc++6   7.2.0-17
ii  libv4l-0 1.12.6-1
ii  melt 6.4.1-6
ii  qml-module-qtquick-controls  5.9.2-2
ii  qml-module-qtquick2  5.9.2-3

Versions of packages kdenlive recommends:
ii  breeze-icon-theme  4:5.25.0-2
ii  dvdauthor  0.7.0-1.3
ii  dvgrab 3.5-2+b3
ii  frei0r-plugins 1.6.1-1+b1
ii  genisoimage9:1.1.11-3
ii  oxygen-icon-theme  5:5.25.0-1
ii  recordmydesktop0.3.8.1+svn602-1+b1
ii  swh-plugins0.4.16+git20160602~repack1-2

Versions of packages kdenlive suggests:
ii  khelpcenter  4:16.08.3-1

-- no debconf information



Bug#883972: samba: FTBFS on kfreebsd: error: storage size of 'cr' isn't known

2017-12-12 Thread Timur I. Bakeyev
Hi, guys!

I've discussed https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215202
issue with the iXsystems FreeBSD src committers, they are going to look
into that. But even if that(or similar) fix will go into upstream it won't
happen very soon. FreeBSD has longer release cycles than Linux, so
meanwhile we need to find the workaround.

The relevant part of the failing code should use 'struct xucread' on
FreeBSD and 'LOCAL_PEERCRED' option to the getsockopt(2), but as it is
already mentioned in the bug report that won't provide you the PID of the
remote peer.

I wonder, would it be possible to replace getsockopt(2) here with the
sendmsg()/recvmsg() and 'SCM_CREDS' type of message, like described here,
for ex:

https://davejingtian.org/2015/02/17/retrieve-pid-from-the-packet-in-unix-domain-socket-a-complete-use-case-for-recvmsgsendmsg/

This seems be less Linux-specific way of obtaining remote peer PID.

With regards,
Timur Bakeyev.


On Sun, Dec 10, 2017 at 2:47 AM, Andrew Bartlett  wrote:

> On Sat, 2017-12-09 at 23:04 +0100, Andreas Beckmann wrote:
> > Source: samba
> > Version: 2:4.7.3+dfsg-1
> > Severity: important
> > User: debian-...@lists.debian.org
> > Usertags: kfreebsd
> >
> > Hi,
> >
> > that 4.7.x uploads of samba FTBFS on kfreebsd:
>
> > [2706/4004] Compiling ctdb/tests/src/ipalloc_read_known_ips.c
> > 08:44:02 runner /usr/bin/gcc -g -O2 
> > -fdebug-prefix-map=/«BUILDDIR»/samba-4.7.3+dfsg=.
> -fstack-protector-strong -Wformat -Werror=format-security -fPIE -fPIC
> -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS 
> -DCTDB_HELPER_BINDIR="/usr/lib/x86_64-kfreebsd-gnu/ctdb"
> -DLOGDIR="/var/log/ctdb" -DCTDB_ETCDIR="/etc/ctdb"
> -DCTDB_VARDIR="/var/lib/ctdb" -DCTDB_RUNDIR="/var/run/ctdb"
> -fstack-protector -DSTATIC_fake_ctdbd_MODULES=NULL
> -DSTATIC_fake_ctdbd_MODULES_PROTO=extern void 
> __fake_ctdbd_dummy_module_proto(void)
> -MD -Wdate-time -D_FORTIFY_SOURCE=2 -Idefault/ctdb -I../ctdb
> -Idefault/include/public -I../include/public -Idefault/source4 -I../source4
> -Idefault/lib -I../lib -Idefault/source4/lib -I../source4/lib
> -Idefault/source4/include -I../source4/include -Idefault/include
> -I../include -Idefault/lib/replace -I../lib/replace -Idefault/ctdb/include
> -I../ctdb/include -Idefault -I.. -Idefault/lib/util/charset
> -I../lib/util/charset -Idefault/libcli/util -I../libcli/util
> -Idefault/lib/crypto -I../lib/crypto -Idefault/lib/async_req
> -I../lib/async_req -Idefault/dynconfig -I../dynconfig -I/usr/local/include
> -D_SAMBA_BUILD_=4 -DHAVE_CONFIG_H=1 -D_GNU_SOURCE=1
> -D_XOPEN_SOURCE_EXTENDED=1 ../ctdb/tests/src/ipalloc_read_known_ips.c -c
> -o default/ctdb/tests/src/ipalloc_read_known_ips_134.o
> > ../ctdb/tests/src/fake_ctdbd.c: In function 'client_send':
> > ../ctdb/tests/src/fake_ctdbd.c:3081:15: error: storage size of 'cr'
> isn't known
> >   struct ucred cr;
> >^~
> > ../ctdb/tests/src/fake_ctdbd.c:3082:25: error: invalid application of
> 'sizeof' to incomplete type 'struct ucred'
> >   socklen_t crl = sizeof(struct ucred);
> >  ^~
> > ../ctdb/tests/src/fake_ctdbd.c:3095:35: error: 'SO_PEERCRED' undeclared
> (first use in this function); did you mean 'SO_PEERLABEL'?
> >   ret = getsockopt(fd, SOL_SOCKET, SO_PEERCRED, , );
> >^~~
> >SO_PEERLABEL
> > ../ctdb/tests/src/fake_ctdbd.c:3095:35: note: each undeclared
> identifier is reported only once for each function it appears in
> > [2707/4004] Compiling lib/pthreadpool/tests.c
> > 08:44:02 runner /usr/bin/gcc -g -O2 
> > -fdebug-prefix-map=/«BUILDDIR»/samba-4.7.3+dfsg=.
> -fstack-protector-strong -Wformat -Werror=format-security -fPIE -fPIC
> -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS 
> -DCTDB_HELPER_BINDIR="/usr/lib/x86_64-kfreebsd-gnu/ctdb"
> -DLOGDIR="/var/log/ctdb" -DCTDB_ETCDIR="/etc/ctdb"
> -DCTDB_VARDIR="/var/lib/ctdb" -DCTDB_RUNDIR="/var/run/ctdb"
> -fstack-protector -DSTATIC_pthreadpooltest_MODULES=NULL
> -DSTATIC_pthreadpooltest_MODULES_PROTO=extern void
> __pthreadpooltest_dummy_module_proto(void) -MD -Wdate-time
> -D_FORTIFY_SOURCE=2 -Idefault/lib/pthreadpool -I../lib/pthreadpool
> -Idefault/include/public -I../include/public -Idefault/source4 -I../source4
> -Idefault/lib -I../lib -Idefault/source4/lib -I../source4/lib
> -Idefault/source4/include -I../source4/include -Idefault/include
> -I../include -Idefault/lib/replace -I../lib/replace -Idefault/ctdb/include
> -I../ctdb/include -Idefault/ctdb -I../ctdb -Idefault -I..
> -Idefault/libcli/util -I../libcli/util -I/usr/local/include
> -D_SAMBA_BUILD_=4 -DHAVE_CONFIG_H=1 -D_GNU_SOURCE=1
> -D_XOPEN_SOURCE_EXTENDED=1 ../lib/pthreadpool/tests.c -c -o
> default/lib/pthreadpool/tests_2.o
> > Waf: Leaving directory `/«BUILDDIR»/samba-4.7.3+dfsg/bin'
> > Build failed:  -> task failed (err #1):
> >   {task: cc fake_ctdbd.c -> fake_ctdbd_134.o}
> > debian/rules:102: recipe for target 'override_dh_auto_build' failed
> > make[1]: *** 

Bug#570935: Patch

2017-12-12 Thread Paul R. Tagliamonte
tags 570935 + patch
thanks

Patch adding a DH_WITH environment var attached.

-- 
:wq
From d19c6cec85781d1e5585c7f97e956dbb44463b1a Mon Sep 17 00:00:00 2001
From: Paul Tagliamonte 
Date: Tue, 12 Dec 2017 23:35:39 -0500
Subject: [PATCH] Add DH_WITH env variable to specify local addons.

This is intended to be used by downstreams or specific local configurations
that require a debhelper addon to be run during multiple builds without
having to patch a large number of rules file. If at all possible, this should
be avoided in favor of a --with flag in the rules file.
---
 debhelper.pod | 12 
 dh|  1 +
 2 files changed, 13 insertions(+)

diff --git a/debhelper.pod b/debhelper.pod
index 00171e2e..88560038 100644
--- a/debhelper.pod
+++ b/debhelper.pod
@@ -961,6 +961,18 @@ your package is built.
 Multiple things to exclude can be separated with colons, as in
 

Bug#884267: kdenlive: Where is kdenlive_render.log.XXXXXXXX?

2017-12-12 Thread Kingsley G. Morse Jr.
Package: kdenlive
Version: 17.08.3-2
Severity: normal

Hi Patrick,

Happy holidays!

I'd like to use kdenlive's render log to find and
fix rendering bugs.

I followed the instructions in kdenlive_render's man 
page to create on by setting the environment variable
named "KDENLIVE_RENDER_LOG".

I set it before before trying to render in
kdenlive

$ export KDENLIVE_RENDER_LOG=1 ; export LANG=C ;  kdenlive

and before running kdenlive_render with a render
script generated by kdenlive

#! /bin/sh
RENDERER="/usr/bin/kdenlive_render"
MELT="/usr/bin/melt"
SOURCE_0=
TARGET_0=
PARAMETERS_0="-pid:7095 in=0 out=1565 $MELT atsc_720p_2997 avformat - 
$SOURCE_0 $TARGET_0 f=webm vcodec=libvpx acodec=vorbis crf=23 vb=0 quality=good 
aq=6 max-intra-rate=1000 cpu-used=4 threads=1 real_time=-1"
KDENLIVE_RENDER_LOG=1
$RENDERER $PARAMETERS_0

I expected to find a render log file named like

/tmp/kdenlive_render.log.

Unfortunately, I didn't.

I wish rendering left a log file.

I think it would make debugging easier.

Thanks,
Kingsley

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 4.4.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages kdenlive depends on:
ii  ffmpeg   7:3.4.1-1
ii  kded55.37.0-2
ii  kdenlive-data17.08.3-2
ii  kinit5.37.0-2
ii  kio  5.37.0-2
ii  libc62.25-3
ii  libgcc1  1:7.2.0-17
ii  libgl1-mesa-glx [libgl1] 17.1.3-2
ii  libglu1-mesa [libglu1]   9.0.0-2.1
ii  libkf5archive5   5.28.0-2
ii  libkf5attica55.37.0-2
ii  libkf5auth5  5.37.0-2
ii  libkf5bookmarks5 5.37.0-2
ii  libkf5codecs55.37.0-2
ii  libkf5completion55.37.0-2
ii  libkf5configcore55.37.0-2
ii  libkf5configgui5 5.37.0-2
ii  libkf5configwidgets5 5.37.0-2
ii  libkf5coreaddons55.37.0-2
ii  libkf5crash5 5.37.0-2
ii  libkf5dbusaddons55.37.0-2
ii  libkf5filemetadata3  5.37.0-2
ii  libkf5guiaddons5 5.28.0-1
ii  libkf5i18n5  5.37.0-2
ii  libkf5iconthemes55.37.0-2
ii  libkf5itemviews5 5.37.0-2
ii  libkf5jobwidgets55.37.0-2
ii  libkf5kiocore5   5.37.0-2
ii  libkf5kiofilewidgets55.37.0-2
ii  libkf5kiowidgets55.37.0-2
ii  libkf5newstuff5  5.37.0-2
ii  libkf5newstuffcore5  5.37.0-2
ii  libkf5notifications5 5.37.0-2
ii  libkf5notifyconfig5  5.37.0-2
ii  libkf5service-bin5.37.0-2
ii  libkf5service5   5.37.0-2
ii  libkf5solid5 5.37.0-2
ii  libkf5sonnetui5  5.28.0-2+b1
ii  libkf5textwidgets5   5.37.0-2
ii  libkf5widgetsaddons5 5.37.0-2
ii  libkf5xmlgui55.37.0-2
ii  libmlt++36.4.1-6+b1
ii  libmlt6  6.4.1-6+b1
ii  libqt5concurrent55.9.2+dfsg-4
ii  libqt5core5a 5.9.2+dfsg-6
ii  libqt5dbus5  5.9.2+dfsg-6
ii  libqt5gui5   5.9.2+dfsg-6
ii  libqt5network5   5.9.2+dfsg-6
ii  libqt5qml5   5.9.2-3
ii  libqt5quick5 5.9.2-3
ii  libqt5script55.9.2+dfsg-1
ii  libqt5svg5   5.9.2-3
ii  libqt5webkit55.212.0~alpha2-5
ii  libqt5widgets5   5.9.2+dfsg-6
ii  libqt5xml5   5.9.2+dfsg-6
ii  libstdc++6   7.2.0-17
ii  libv4l-0 1.12.6-1
ii  melt 6.4.1-6
ii  qml-module-qtquick-controls  5.9.2-2
ii  qml-module-qtquick2  5.9.2-3

Versions of packages kdenlive recommends:
ii  breeze-icon-theme  4:5.25.0-2
ii  dvdauthor  0.7.0-1.3
ii  dvgrab 3.5-2+b3
ii  frei0r-plugins 1.6.1-1+b1
ii  genisoimage9:1.1.11-3
ii  oxygen-icon-theme  5:5.25.0-1
ii  recordmydesktop0.3.8.1+svn602-1+b1
ii  swh-plugins0.4.16+git20160602~repack1-2

Versions of packages kdenlive suggests:
ii  khelpcenter  4:16.08.3-1

-- no debconf information



Bug#881591: e2fsprogs-l10n: Please mark the package Multi-Arch: foreign

2017-12-12 Thread Theodore Ts'o
On Mon, Nov 13, 2017 at 09:38:31AM +, Hugh McMaster wrote:
> 
> The package e2fsprogs-l10n is not multi-arch compatible.
> 
> As the package is Architecture: all and cannot differ across
> architectures, please mark the package Multi-Arch: foreign
> to satisfy Debian's multi-arch hinter.

Thanks for the report.  This will be fixed in the next release of
e2fsprogs.

- Ted



Bug#881590: ss-dev: Please mark the package Multi-Arch: same

2017-12-12 Thread Theodore Ts'o
On Mon, Nov 13, 2017 at 09:34:22AM +, Hugh McMaster wrote:
> 
> The package ss-dev is not multi-arch compatible.
> 
> A comparison of the i386 and amd64 variants shows no file
> conflicts that would prevent this package from being marked
> Multi-Arch: same.
> 
> Multi-arch support is needed so that other Debian packages
> requiring this package can be co-installed on multi-arch
> systems.

Thanks for the report.  This will be fixed in the next release of
e2fsprogs.

- Ted



Bug#881408: comerr-dev: Please mark the package Multi-Arch: same

2017-12-12 Thread Theodore Ts'o
On Sat, Nov 11, 2017 at 11:21:31AM +, Hugh McMaster wrote:
> 
> The package comerr-dev is not currently multi-arch compatible.
> 
> A diff of the i386 and amd64 variants shows no file conflicts
> that would prevent this package from being marked Multi-Arch: same.
> 
> Multi-arch compatibility would greatly benefit other projects,
> which need multi-arch support from this package.

Thanks for the report.  This will be fixed in the next release of
e2fsprogs.

- Ted



Bug#883765: cups-client: Unsupported document-format "application/octet-stream".

2017-12-12 Thread P V Mathew

On 2017-12-12 13:41, intrigeri wrote:

Control: tag -1 + moreinfo
Control: retitle -1 Printing is broken with AppArmor enabled if /var/log is a 
symlink to some other place

Hi,

Thanks Mathew for testing again, and Brian for adding me in the loop!
I'm Cc'ing the AppArmor team so the resolution of this problem does
not depend solely on myself :)

P V Mathew:

as requested have reinstalled apparmor
The following programs are not working
man(from command line) but man2html ok

Interesting, I don't have this problem. I notice that AppArmor
confinement was added in man-db (2.7.6.1-3), and then updated in
man-db (2.7.6.1-4). This is off-topic here so could you please report
a bug against man-db about this, including the corresponding AppArmor
denial logs? Feel free to X-Debbugs-Cc pkg-apparmor-team@.
In the meantime you can "sudo aa-disable /usr/bin/man".


cups started on reboot but by the time logged in, it had stopped.
[...]
Oops. realize now, may be about 2-3 years ago when my var partition got full,
had moved the var/log on to /home/ and sym-linked to it in var. May be
this is not consistent with apparmor(not sure?).

Right, this can cause lots of problems with AppArmor, and not only for
cupsd so I'm not going to suggest solutions that would address your
problem for cupsd only but leave other bits of your system broken.

I recommend you either:

A. bind-mount /home/log on /var/log instead of using a symlink

Thanks.
Works.
After changing all symlinks in similar way all the
reported issues(cups, man,icedove) resolved.
Regards.


B. use an AppArmor alias

# echo '/var/log/ -> /home/log/' >> /etc/apparmor.d/tunables/alias
# systemctl restart apparmor

Works?

If this works, then I suggest the cups maintainers close this bug or
tag it wontfix: with a path-based LSM like AppArmor, there's no
general solution to problems caused by such uncommon customization
applied locally by sysadmins, other than education and documentation
about AppArmor so they're able to adjust their AppArmor
configuration accordingly.

Regards,




Bug#884266: heat-common: fails to install: installed heat-common package post-installation script subprocess returned error exit status 10

2017-12-12 Thread Andreas Beckmann
Package: heat-common
Version: 1:9.0.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package heat-common.
  (Reading database ... 
(Reading database ... 21320 files and directories currently installed.)
  Preparing to unpack .../heat-common_1%3a9.0.2-1_all.deb ...
  Unpacking heat-common (1:9.0.2-1) ...
  Setting up heat-common (1:9.0.2-1) ...
  dpkg: error processing package heat-common (--configure):
   installed heat-common package post-installation script subprocess returned 
error exit status 10
  Errors were encountered while processing:
   heat-common


Does it fail on a debconf question not being asked under 
DEBIAN_FRONTEND=noninteractive?


cheers,

Andreas


heat-common_1:9.0.2-1.log.gz
Description: application/gzip


Bug#883950: debian-policy: allow specifying common licenses with only the identifier

2017-12-12 Thread Scott Kitterman
On Tuesday, December 12, 2017 09:29:27 PM Markus Koschany wrote:
> Hi,
> 
> thanks for reporting. I also intended to make such a proposal and I had
> briefly mentioned it in bug #883966. [1]
> 
> The reason why the short form is allowed is because of Debian Policy 12.5
> 
> "Packages distributed under the Apache license (version 2.0), the
> Artistic license, the GNU GPL (versions 1, 2, or 3), the GNU LGPL
> (versions 2, 2.1, or 3), the GNU FDL (versions 1.2 or 1.3), and the
> Mozilla Public License (version 1.1 or 2.0) should refer to the
> corresponding files under /usr/share/common-licenses, [9] rather than
> quoting them in the copyright file."
> 
> I agree that using boiler plate like this:
> | License: GPL-2+
> | On Debian systems the full text of the GPL-2 can be found in
> | /usr/share/common-licenses/GPL-2
> 
> is still redundant.
> 
> I suggest to change Debian Policy 12.5 and copyright format 1.0 in such
> a way that the following syntax is allowed:
> 
> License: [GPL-2+]
> 
> This would imply the license is identical to the one we ship under
> /usr/share/common-licenses/. Services like sources.debian.org could
> easily parse this field and automatically link to the full license-text.
> 
> I don't have a fixation about using brackets. We could also use
> something else. In the above case Lintian should not warn about a
> missing standalone license or license text in general.
> 
> Regards,
> 
> Markus
> 
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883966#25

Speaking just for myself (not as an FTP Team member), I think that's 
definitely too short.  If debian/copyright isn't going to include the license, 
then I think at a minimum, it needs to point to where to find it.  
/usr/share/common-licenses may be well known to developers, but I don't think 
it's reasonable to assume users will automatically know to look there.

Scott K


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


Bug#884265: aodh-common: fails to install: installed aodh-common package post-installation script subprocess returned error exit status 10

2017-12-12 Thread Andreas Beckmann
Package: aodh-common
Version: 5.0.0-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package aodh-common.
  (Reading database ... 
(Reading database ... 19811 files and directories currently installed.)
  Preparing to unpack .../aodh-common_5.0.0-4_all.deb ...
  Unpacking aodh-common (5.0.0-4) ...
  Setting up aodh-common (5.0.0-4) ...
  dpkg: error processing package aodh-common (--configure):
   installed aodh-common package post-installation script subprocess returned 
error exit status 10
  Errors were encountered while processing:
   aodh-common


Does it fail on a debconf question not being asked in noninteractive mode?


cheers,

Andreas


aodh-common_5.0.0-4.log.gz
Description: application/gzip


Bug#884264: fusionforge-web: fails to install: /usr/share/fusionforge/post-install.d/web/web.sh: line 126: /etc/httpd/conf.modules.d/00-macro.conf: No such file or directory

2017-12-12 Thread Andreas Beckmann
Package: fusionforge-web
Version: 6.0.5-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package fusionforge-web.
  (Reading database ... 
(Reading database ... 13397 files and directories currently installed.)
  Preparing to unpack .../fusionforge-web_6.0.5-2_all.deb ...
  Unpacking fusionforge-web (6.0.5-2) ...
  Setting up fusionforge-web (6.0.5-2) ...
  PHP Deprecated:  Methods with the same name as their class will not be 
constructors in a future version of PHP; FFError has a deprecated constructor 
in /usr/share/fusionforge/common/include/FFError.class.php on line 36
  PHP Deprecated:  Methods with the same name as their class will not be 
constructors in a future version of PHP; FFError has a deprecated constructor 
in /usr/share/fusionforge/common/include/FFError.class.php on line 36
  PHP Deprecated:  Methods with the same name as their class will not be 
constructors in a future version of PHP; FFError has a deprecated constructor 
in /usr/share/fusionforge/common/include/FFError.class.php on line 36
  PHP Deprecated:  Methods with the same name as their class will not be 
constructors in a future version of PHP; FFError has a deprecated constructor 
in /usr/share/fusionforge/common/include/FFError.class.php on line 36
  PHP Deprecated:  Methods with the same name as their class will not be 
constructors in a future version of PHP; FFError has a deprecated constructor 
in /usr/share/fusionforge/common/include/FFError.class.php on line 36
  PHP Deprecated:  Methods with the same name as their class will not be 
constructors in a future version of PHP; FFError has a deprecated constructor 
in /usr/share/fusionforge/common/include/FFError.class.php on line 36
  PHP Deprecated:  Methods with the same name as their class will not be 
constructors in a future version of PHP; FFError has a deprecated constructor 
in /usr/share/fusionforge/common/include/FFError.class.php on line 36
  PHP Deprecated:  Methods with the same name as their class will not be 
constructors in a future version of PHP; FFError has a deprecated constructor 
in /usr/share/fusionforge/common/include/FFError.class.php on line 36
  PHP Deprecated:  Methods with the same name as their class will not be 
constructors in a future version of PHP; FFError has a deprecated constructor 
in /usr/share/fusionforge/common/include/FFError.class.php on line 36
  PHP Deprecated:  Methods with the same name as their class will not be 
constructors in a future version of PHP; FFError has a deprecated constructor 
in /usr/share/fusionforge/common/include/FFError.class.php on line 36
  PHP Deprecated:  Methods with the same name as their class will not be 
constructors in a future version of PHP; FFError has a deprecated constructor 
in /usr/share/fusionforge/common/include/FFError.class.php on line 36
  PHP Deprecated:  Methods with the same name as their class will not be 
constructors in a future version of PHP; FFError has a deprecated constructor 
in /usr/share/fusionforge/common/include/FFError.class.php on line 36
  PHP Deprecated:  Methods with the same name as their class will not be 
constructors in a future version of PHP; FFError has a deprecated constructor 
in /usr/share/fusionforge/common/include/FFError.class.php on line 36
  PHP Deprecated:  Methods with the same name as their class will not be 
constructors in a future version of PHP; FFError has a deprecated constructor 
in /usr/share/fusionforge/common/include/FFError.class.php on line 36
  PHP Deprecated:  Methods with the same name as their class will not be 
constructors in a future version of PHP; FFError has a deprecated constructor 
in /usr/share/fusionforge/common/include/FFError.class.php on line 36
  PHP Deprecated:  Methods with the same name as their class will not be 
constructors in a future version of PHP; FFError has a deprecated constructor 
in /usr/share/fusionforge/common/include/FFError.class.php on line 36
  PHP Deprecated:  Methods with the same name as their class will not be 
constructors in a future version of PHP; FFError has a deprecated constructor 
in /usr/share/fusionforge/common/include/FFError.class.php on line 36
  PHP Deprecated:  Methods with the same name as their class will not be 
constructors in a future version of PHP; FFError has a deprecated constructor 
in /usr/share/fusionforge/common/include/FFError.class.php on line 36
  PHP Deprecated:  Methods with the same name as their class will not be 
constructors in a future version of PHP; FFError has a deprecated constructor 
in /usr/share/fusionforge/common/include/FFError.class.php on line 36
  PHP Deprecated:  Methods with the same name as their class will not be 
constructors in a future version of 

Bug#880207: e2fsprogs-l10n: copyright file missing

2017-12-12 Thread Theodore Ts'o
On Mon, Oct 30, 2017 at 04:23:51PM +0100, Andreas Beckmann wrote:
> 
> a test with piuparts revealed that your package misses the copyright
> file, which is a violation of Policy 12.5:
> https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

Thanks for pointing this out; I've checked in a fix and it will be
addressed in the next release of e2fsprogs.

- Ted



Bug#875688: libreoffice-report-builder: report builder inactive in 5.4

2017-12-12 Thread Lionel Elie Mamane
On Tue, Dec 12, 2017 at 11:35:29PM +0100, Rene Engelhard wrote:
> On Thu, Dec 07, 2017 at 04:28:10PM +0100, Lionel Elie Mamane wrote:
> > The Debian package of 5.4 behaves as if the optional part of
> > LibreOffice "Report Builder" was not installed, although the packages
> > libreoffice-report-builder and libreoffice-report-builder-bin are
> > installed. I haven't diagnosed why.

> Interestingly, in my sid test vm, the 5.4.4 packages from 
> https://people.debian.org/~rene/libreoffice/5.4/ do show it again *but*
> you marked it as found in 6.0.0 beta2 and yes, I don't see it there
> either anymore...

This starts to look like there is some non-determinism in the build
process, and depending on more-or-less random choices made, the bug is
there or not.

If that's the case, it will a PITA to debug... But since AFAIK that
bug happens only on Debian, we should concentrate on the
Debian-specific patches.

Or the non-determinism is in the install process? It depends in what
order the packages are installed / upgraded?

-- 
Lionel



Bug#875688: libreoffice-report-builder: report builder inactive in 5.4

2017-12-12 Thread Lionel Elie Mamane
On Tue, Dec 12, 2017 at 11:35:29PM +0100, Rene Engelhard wrote:
> On Thu, Dec 07, 2017 at 04:28:10PM +0100, Lionel Elie Mamane wrote:

>> The immediate cause is that in file
>>  dbaccess/source/ui/misc/linkeddocuments.cxx
>>  function OLinkedDocumentsAccess::open, the call to impl_open throws a
>>  css::io::WrongFormatException,
>> but what is the underlying reason for that? Probably the internal
>> LibreOffice registry doesn't have properly registered the optional
>> "Report Builder" part (could be an error in
>> /usr/lib/libreoffice/share/registry/reportbuilder.xcd or that file is
>> not loaded), or it fails to load for some reason.

> But it is there and was there. And if it was that, why is it
> different between versions and without any change to what we do with
> that file?

When I wrote "it fails to load for some reason", I meant "Report
Builder fails to load for some reason", and that's the following
files:

/usr/lib/libreoffice/program/librptlo.so
/usr/lib/libreoffice/program/librptuilo.so
/usr/lib/libreoffice/program/librptxmllo.so

-- 
Lionel



Bug#884263: borgbackup: Backport of 1.1.x for stable

2017-12-12 Thread Jerome Charaoui
Package: borgbackup
Version: 1.0.9-1
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Maintainer,

As you may know, BorgBackup 1.1.x introduces a number of useful features such
as 'borg recreate', compression heuristics and automatic removal of stale locks
as well as many bug fixes.

If possible, making this package available in stretch-backports would therefore
be quite useful.

I'm willing to give it a shot, unless you've already started working on it.

Thanks,

- -- Jerome




- -- System Information:
Debian Release: 9.3
  APT prefers stable
  APT policy: (900, 'stable'), (1, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages borgbackup depends on:
ii  libacl12.2.52-3+b1
ii  libc6  2.24-11+deb9u1
ii  liblz4-1   0.0~r131-2+b1
ii  libssl1.1  1.1.0f-3+deb9u1
ii  python33.5.3-1
ii  python3-llfuse 1.2+dfsg-1
ii  python3-msgpack0.4.8-1
ii  python3-pkg-resources  33.1.1-1

borgbackup recommends no packages.

Versions of packages borgbackup suggests:
pn  borgbackup-doc  

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEC1ozuKJtYBCcUJxsg+M719TdTKEFAlownRYSHGplcm9tZUBy
aXNldXAubmV0AAoJEIPjO9fU3UyhSQsP/10Le+7GiGQKe2RSJhv77Z0Pc3P337+b
puurQSq6qJjgLk6dyzInAURGh6R+otV20b2aoSRj68s6noPnbbVlZd5aJtUL+djz
1BoAF+E8cgrbusAXnS3uK15HAvG+MsVYUWMv0hs0Cm40lEDMGWwlx7902Cs3EV8v
RppiL2v135KIVWakRa7VFGQ58FqK+RVTzzdohmOnoIkpu6D36umIDvI86pv228NY
UeY21/BW4QpgFjTkXtThckck44OfgATUr7OqJuQRvfz7bIXec3hPmlLB7l+AHPMu
AiGmQA8zwEwuKWNQ5OZTa101ZxaXfyLW1fbxUxyic5c2KhUTCn9frR10rhBqLN1B
mXwnFOkfmP5f/qCiWqdDNTpZAxadN0MnFF+q83Dr2yveXjFb8fiDdEBuJPKEUu2x
RRU/GaI7MtX7i0wVb85CVRZ+T4Jl+uNUGraWV8uMqk+b4Dx+b9U1TAuAL3W8Wfk4
mRqwlEeRlrX/yeuic6ggG4LX8wJgxIoJSbI/8HguXIzpDDDtRlz+vyu4ZuRCySGl
3wLahuWJfl8JM2YuRBeSRVTYKTjHLizMuRU6OhYa0WwH+3ePsrkHLxkBNhBfBaah
P2YdRp36WToC3J7ieGE2yBj5p3OASIQkVZpVCt2DFBcF+1IwrwAW0YQ+3biEOta5
vckfj1DhToH8
=YlVs
-END PGP SIGNATURE-



Bug#884038: Bug #884038: [git] 2.15.x fails to fetch remote repository

2017-12-12 Thread Nicolas Braud-Santoni
Control: tag -1 + moreinfo

Hi,

On Sun, Dec 10, 2017 at 07:44:14PM +0100, mirq-debo...@rere.qmqm.pl wrote:
> Package: git
> Version: 1:2.15.1-1
> Severity: grave
> 
> --- Please enter the report below this line. ---
> 
> git 2.15.x from testing can't properly fetch from remote repository:

I find myself unable to reproduce the problem:

> $ git clone https://github.com/torvalds/linux.git
> Cloning into 'linux'...
> remote: Counting objects: 5772759, done.
> remote: Compressing objects: 100% (945/945), done.
> remote: Total 5772759 (delta 852), reused 339 (delta 339), pack-reused 5771475
> Receiving objects: 100% (5772759/5772759), 1.94 GiB | 5.39 MiB/s, done.
> Resolving deltas: 100% (4785819/4785819), done.
> 
> git clone https://github.com/torvalds/linux.git  430.98s user 60.46s system 
> 95% cpu 8:34.72 total
> 
> $ git --version
> git version 2.15.1

(Subsequent `git fetch`es worked as intended)


Is this the only repository on which you encounter this problem?
Can you reliably reproduce it? Can you reproduce it in a fresh git-clone?


Best,

  nicoo


signature.asc
Description: PGP signature


Bug#877716: [Aptitude-devel] Bug#877716: qalculate: Removing qalculate removes qalculate-gtk

2017-12-12 Thread Axel Beckert
Hi Mattia,

Mattia Rizzolo wrote:
> Actually, when I tried earlier today, qalculate-gtk was marked as
> automatically installed when installed through the transition qalculate,
> even with apt.

Now that's indeed unexpected. Can you check what "apt-config dump |
fgrep -i Move-Autobit-Sections" yields for you?

Looks like this here:

APT::Move-Autobit-Sections "";
APT::Move-Autobit-Sections:: "oldlibs";
APT::Move-Autobit-Sections:: "contrib/oldlibs";
APT::Move-Autobit-Sections:: "non-free/oldlibs";
APT::Move-Autobit-Sections:: "restricted/oldlibs";
APT::Move-Autobit-Sections:: "universe/oldlibs";
APT::Move-Autobit-Sections:: "multiverse/oldlibs";

(IIRC, this is part of the default value, which also contains
"metapackages" in addition to "oldlibs".)

shirish: It would also be interesting what the output of this command
is on your machine.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#884259: [Pkg-mailman-hackers] Bug#884259: mailman3-suite: postinst fails to finish due to password/keys containing '/'

2017-12-12 Thread Pierre-Elliott Bécue
Le mercredi 13 décembre 2017 à 11:14:53+1100, Stephen Rothwell a écrit :
> Package: mailman3-suite
> Version: 0+20170523-1
> Severity: normal
> 
> Dear Maintainer,
> 
>* What led up to the situation?
> 
> Trying to install mailman3-suite
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> 
> aptitude install mailman3
> 
>* What was the outcome of this action?
> 
> The postinst for mailman3-suite reported an error with "sed" and then hung
> 
>* What outcome did you expect instead?
> 
> I expected the package to install correctly.
> 
> To make the postinst complete, I changed the 'sed' lines to use '|'
> instead of '/' in their 's' expressions in the following invocation
> (base64 will never produce '|' characters):
> 
> # Set custom settings in settings_local.py
> sed -i -e "s|^\(\s*SECRET_KEY\s*=\s*'\)\S\+\('\s*\)$|\1$secretkey\2|" \
>-e 
> "s|^\(\s*MAILMAN_REST_API_PASS\s*=\s*'\)\S\+\('\s*\)|\1$restapipass\2|" \
>-e 
> "s|^\(\s*MAILMAN_ARCHIVER_KEY\s*=\s*'\)\S\+\('\s*\)|\1$archiverkey\2|" \
>-e "s|^\(\s*EMAILNAME\s*=\s*'\)\S\+\('\s*\)|\1$emailname\2|" \
>$settings_local_new
> 
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing
>   APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 
> 'oldstable-updates'), (500, 'stable'), (500, 'oldstable'), (1, 'unstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.11.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_AU.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: sysvinit (via /sbin/init)
> 
> Versions of packages mailman3-suite depends on:
> ii  dbconfig-pgsql2.0.9
> ii  debconf [debconf-2.0] 1.5.65
> ii  lsb-base  9.20170808
> ii  mailman3-core 3.1.0-6
> ii  node-less 1.6.3~dfsg-2
> ii  python2.7.14-1
> ii  python-django-hyperkitty  1.1.4-2
> ii  python-django-postorius   1.1.0-1
> ii  python-psycopg2   2.7.3-1
> ii  python-whoosh 2.7.4+git6-g9134ad92-1
> ii  ruby-sass 3.4.23-1
> ii  ucf   3.0036
> ii  uwsgi 2.0.15-10
> ii  uwsgi-plugin-python   2.0.15-10
> 
> Versions of packages mailman3-suite recommends:
> ii  libapache2-mod-proxy-uwsgi  2.0.15-10
> ii  postgresql  10+188
> 
> mailman3-suite suggests no packages.
> 
> -- Configuration Files:
> /etc/cron.d/mailman3-suite changed [not included]
> 
> -- debconf information:
>   mailman3-suite/pgsql/admin-user: postgres
>   mailman3-suite/internal/skip-preseed: false
>   mailman3-suite/pgsql/authmethod-admin: ident
> * mailman3-suite/remote/host: localhost
>   mailman3-suite/remote/newhost: localhost
>   mailman3-suite/restart-webserver: true
>   mailman3-suite/emailname: ozlabs.org
>   mailman3-suite/purge: false
>   mailman3-suite/db/app-user: mailman3suite@localhost
> * mailman3-suite/dbconfig-install: true
>   mailman3-suite/pgsql/method: TCP/IP
>   mailman3-suite/remote/port:
>   mailman3-suite/install-error: abort
>   mailman3-suite/missing-db-package-error: abort
>   mailman3-suite/pgsql/no-empty-passwords:
>   mailman3-suite/upgrade-backup: true
>   mailman3-suite/superuser-mail: root@localhost
>   mailman3-suite/pgsql/changeconf: false
>   mailman3-suite/dbconfig-reinstall: false
>   mailman3-suite/remove-error: abort
>   mailman3-suite/reconfigure-webserver: apache2
>   mailman3-suite/pgsql/authmethod-user: password
>   mailman3-suite/dbconfig-remove: true
>   mailman3-suite/superuser-name: admin
>   mailman3-suite/database-type: pgsql
>   mailman3-suite/internal/reconfiguring: false
>   mailman3-suite/db/dbname: mailman3suite
>   mailman3-suite/upgrade-error: abort
>   mailman3-suite/pgsql/manualconf:
>   mailman3-suite/passwords-do-not-match:
>   mailman3-suite/dbconfig-upgrade: true
> 

Good evening,

Yes, this issue was spotted, but after the initial upload in NEW of
mailman-suite. The patch is actually in the git repo since Nov. the 13th[1].
I believe for some reason we failed at uploading the new version. Sorry for
that.

CC-ing mejo as I can't upload a fix myself for now.

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2

[1]:
https://anonscm.debian.org/git/pkg-mailman/mailman-suite.git/commit/?id=a7fc6f9ab063a45115fbeb0d824c181b69ad8e1b


signature.asc
Description: PGP signature


Bug#884239: [Pkg-mailman-hackers] Bug#884239: build-depends on python-django-allauth (not yet in debian)

2017-12-12 Thread Pierre-Elliott Bécue
Control: tags -1 moreinfo

Le mardi 12 décembre 2017 à 21:46:16+0100, Daniel Baumann a écrit :
> Package: django-mailman3
> Version: 1.1.0-1
> Severity: serious
> 
> Hi,
> 
> thanks a lot for bringing mailman3 to debian.
> 
> unfortunatly, there seems to be at least python-django-allauth (not in
> debian or NEW yet) missing as specified in django-mailman3 build-depends.

Good evening,

python-django-allauth actually is in Debian unstable since 16/09/2017.

Can you provide me with mode info?

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2


signature.asc
Description: PGP signature


Bug#884208: dewalls FTBFS with nonexisting $HOME

2017-12-12 Thread Wookey
On 2017-12-12 19:23 +0200, Adrian Bunk wrote:
> Source: dewalls
> Version: 1.0.0+ds1-1
> Severity: serious
> 
> https://buildd.debian.org/status/package.php?p=dewalls=sid

Yes. I noticed that. It uses qbs and it seems that it writes to a
config directory in $HOME/.config/QtProject/qbs by default. (And I
forgot to check an sbuild build in a clean no-home chroot).

There is a --settings-dir option to override this, although it has to
be set on all the qbs and qbs-config commands, which is a bit tedious.

I could override $HOME to make it work, but I guess that is poor form
in builds as it's supposed to be set to non-existant to catch this
sort of breakage.

Confirmed that --settings-dir works with all prvious config cleaned out. 

Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/


signature.asc
Description: PGP signature


Bug#883731: audacious: Debian packaging has incorrect license

2017-12-12 Thread John Lindgren
Hi Nicholas et. al,

(tallica: This is re: Debian bug #883731, related to the GPL -> BSD
relicensing of Audacious a few years back.  Please take a look at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883731 for background
if you're interested, otherwise disregard.)

On 12/12/2017 04:39 PM, Nicholas D Steeves wrote:
> For Debian Legal Team: With respect to the translations, I now suspect
> they can probably be transitioned to BSD without issue, because
> copyright is also assigned to the Audacious Translators.  eg, in the
> last GPL-2+ release 3.2.4:
> Copyright (C) Audacious translators

We needed a single copyright line because of the way Transifex is set
up, but it's not meant to indicate copyright assignment.  "Audacious
translators" is not a legal entity and just refers to the individual
translators listed in each .po file, who are the copyright holders.

> John, I removed the offending patch in git for the user-visible
> license provided by the Audacious GUI.  Then I went ahead and did a
> historical relicensing review, in spite of the potential for other
> missing copyright holders due to the Transifex switch.  I am a bit
> concerned about what looks to be a politic of "silence is consent" wrt
> relicensing, and hope that I am wrong, or that I was sloppy in my
> review.  Was the discussing conducted informally off the record?

We took a bit more care with the source code relicensing than with the
translations.  I personally went through Git commit logs and replaced
copyrights of "XMMS team", "BMP team", or "Audacious team" (again, none
of which were legal entities) and replaced them with the names of the
actual contributors.

In many cases, files still credited to "the XMMS team" or "the BMP team"
had been totally rewritten and none of the original code that was under
the XMMS/BMP copyright remained.  Actually, as of today, no original
XMMS code remains in Audacious core (i.e. the "audacious" package) at
all.  The largest body of remaining XMMS code is in the "skins" plugin,
which is still GPL for that very reason.

For the core of Audacious, the remaining copyright holders all gave
consent to relicense their code as BSD, generally by email or via the
IRC channel we had back then.  I don't have any of the emails or IRC
logs saved (sorry) but the date of each of the separate Git commits you
listed reflects the point at which we received permission from the
copyright holders listed in those files.

> Would you please take a look at the following (Ian's reply) for an
> example of how to provide a record of all copyright holder's consent?
> tldr; documented confirmation (eg: via copies of emails or a download
> of a bug report/issue/forum thread) for all contributors who did not
> assign copyright to the Audacious Team in the headers of the files
> they contributed to.

Unfortunately, such documentation doesn't exist, to my knowledge.  I'll
point out any specific information I recall about the commits you mentioned.

> 42cbe57307962e65acc2db24dbe99249453c6aac
The equalizer code was a port from mplayer.  The author, Anders
Johansson, was contacted and gave consent for the relicense, and
incidentally also asked that we retain some of his coding style (see the
previous commit to equalizer.c).

> b308c892f47a55c63ef2675f9b6cf016be037f4c
The session management code was later removed from Audacious, which is
why Ivan and David aren't listed in AUTHORS any longer.

> 31ea4ad1adb84f37ce8fff5b4868df247bd6d913
Michal Lipski (tallica, CC'd) did the footwork in tracking down the
authors of those files, and "where possible" in the commit message
refers to developers who gave consent.  Most of the developers listed in
those files were still around on IRC at the time.

> df1165d2fdd8470b2fd45d2e87cac5373055b55e
"desowin ok'd it" -- desowin is the Tomasz Moń listed in those files.
The rest of us were present on IRC, I think.

> 9a979a5af95eb663435ef99d3b7b5c79b94855be
Jussi Judin was not a core developer at the time; I assume tallica
contacted him.

> 33b58d4d8ba18fcbcc36af5c650414e173e22396
>   * Do you have consent on file to move to BSD license for all
> contributors to XMMS and BMP?

I don't recall the particular IRC discussion referenced in the commit
message, but presumably it was determined that no XMMS/BMP code remained
in those files.

> bc295976816358f9512f99a78e933e6594cce121
The commit message itself lists the copyright holders who gave consent.
Most of those folks were around on IRC and so I would assume that was
how they were contacted.

> 853f96f54bbca608f0c95b5e8bf3fd2146607bdd
Similar, except that (from what I remember) Paula developed that code
under Tony Vroon (Chainsaw)'s mentorship, and he would have vouched for
her consent.

> 3d2ca792a02973fb5e2f33d6273aac825d4f3a55
Here I was reattributing some files to their actual authors based on Git
logs, as I said earlier.  You can see that in this commit, I left the
GPL notice intact on any files whose authors hadn't given consent yet at
that 

Bug#884262: flashplugin-nonfree: link to Adobe Flash Player not found on http://www.adobe.com/

2017-12-12 Thread Kevin Locke
Package: flashplugin-nonfree
Version: 1:3.7
Severity: normal

Dear Maintainer,

update-flashplugin-nonfree --status produces the following output:

Flash Player version installed on this system  : 27.0.0.187
link to Adobe Flash Player not found on http://www.adobe.com/ at 
get-upstream-version.pl line 58.
ERROR: failed to get upstream version
More information might be available at:
  http://wiki.debian.org/FlashPlayer

It appears the following check from
http://people.debian.org/~bartm/flashplugin-nonfree/D5C0FC14/get-upstream-version.pl.gz.pgp
is failing:

if( $page !~ m,(?:Adobe )?Flash Player,s )

Which no longer matches the Flash Player link on https://www.adobe.com:

https://get.adobe.com/flashplayer/; class="Footernav-product-link">

http://www.w3.org/2000/svg; viewBox="0 0 50 50" 
focusable="false">



Adobe Flash Player


Thanks,
Kevin

-- Package-specific info:
Debian version: buster/sid
Architecture: amd64
Package version: 1:3.7
Adobe Flash Player version: [@LNX 27,0,0,187
MD5 checksums:
e02694e947249161a2c6fc705a8ec32e  
/var/cache/flashplugin-nonfree/adobewebpage.html
5bb834820d1563b2df2ed52fd9986b24  
/var/cache/flashplugin-nonfree/install_flash_player_11_linux.x86_64.tar.gz
73418346a75b1e9b2b825dfdcf9a29e6  
/usr/lib/flashplugin-nonfree/libflashplayer.so
Alternatives:
flash-mozilla.so - auto mode
  link best version is /usr/lib/flashplugin-nonfree/libflashplayer.so
  link currently points to 
/usr/lib/flashplugin-nonfree/libflashplayer.so
  link flash-mozilla.so is /usr/lib/mozilla/plugins/flash-mozilla.so
/usr/lib/flashplugin-nonfree/libflashplayer.so - priority 50
lrwxrwxrwx 1 root root 34 Aug  6  2016 
/usr/lib/mozilla/plugins/flash-mozilla.so -> /etc/alternatives/flash-mozilla.so
/usr/lib/mozilla/plugins/flash-mozilla.so: symbolic link to 
/etc/alternatives/flash-mozilla.so

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

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

Versions of packages flashplugin-nonfree depends on:
ii  binutils   2.29.1-10
ii  ca-certificates20170717
ii  debconf [debconf-2.0]  1.5.65
ii  gnupg  2.2.3-1
ii  gnupg2 2.2.3-1
ii  libatk1.0-02.26.0-2
ii  libcairo2  1.15.8-2
ii  libcurl3-gnutls7.57.0-1
ii  libfontconfig1 2.12.6-0.1
ii  libfreetype6   2.8.1-0.1
ii  libgcc11:7.2.0-17
ii  libglib2.0-0   2.54.1-1
ii  libgtk2.0-02.24.31-2
ii  libnspr4   2:4.16-1+b1
ii  libnss32:3.34-1
ii  libpango1.0-0  1.40.12-1
ii  libstdc++6 7.2.0-17
ii  libx11-6   2:1.6.4-3
ii  libxext6   2:1.3.3-1+b2
ii  libxt6 1:1.1.5-1
ii  wget   1.19.2-1

flashplugin-nonfree recommends no packages.

Versions of packages flashplugin-nonfree suggests:
pn  firefox-esr
ii  fonts-dejavu   2.37-1
pn  hal-flash  
pn  iceweasel  
pn  konqueror-nsplugins
pn  ttf-mscorefonts-installer  
pn  ttf-xfree86-nonfree

-- no debconf information



Bug#884230: texlive-base: cmbcsc10 moved to texlive-fonts-extra

2017-12-12 Thread Norbert Preining
reassign 884230 enblend-enfuse
retitle 884230 needs updated build-deps (add texlive-fonts-extra)
thanks

> The root problem is that in 2017.20171128-1 cmbcsc10 moved
> from texlive-base to texlive-fonts-extra, that should be
> moved back to texlive-base.

Why? Just update the build-deps.
Upstream has moved these fonts to tl-fonts-extra, and we follow suite.
Reassigning and retitling this bug.

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13



Bug#884260: phpmd: Package phpmd misses dependency php-xml

2017-12-12 Thread Nicola Spanti
Package: phpmd
Version: 2.4.3-1
Severity: important

Dear Maintainer,

The package phpmd for at least Debian 9 Stretch lacks dependency php-xml. In 
consequence, phpmd crashes.

```
$ phpmd app xml ruleset.xml
PHP Fatal error:  Uncaught Error: Call to undefined function 
PHPMD\simplexml_load_string() in /usr/share/php/PHPMD/RuleSetFactory.php:551
Stack trace:
#0 /usr/share/php/PHPMD/PHPMD.php(208): 
PHPMD\RuleSetFactory->getIgnorePattern('ruleset.xml')
#1 /usr/share/php/PHPMD/TextUI/Command.php(129): 
PHPMD\PHPMD->processFiles('app', 'ruleset.xml', Array, 
Object(PHPMD\RuleSetFactory))
#2 /usr/share/php/PHPMD/TextUI/Command.php(170): 
PHPMD\TextUI\Command->run(Object(PHPMD\TextUI\CommandLineOptions), 
Object(PHPMD\RuleSetFactory))
#3 /usr/bin/phpmd(122): PHPMD\TextUI\Command::main(Array)
#4 {main}
  thrown in /usr/share/php/PHPMD/RuleSetFactory.php on line 551
```

Regards.

-- System Information:
Debian Release: 9.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'oldstable-updates'), (500, 
'oldoldstable'), (500, 'stable'), (500, 'oldstable'), (60, 'testing'), (50, 
'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages phpmd depends on:
ii  pdepend   2.2.4-1
ii  php-cli   1:7.0+49
ii  php-common1:49
ii  php7.0-cli [php-cli]  7.0.19-1

phpmd recommends no packages.

phpmd suggests no packages.

-- no debconf information



Bug#883950: debian-policy: allow specifying common licenses with only the identifier

2017-12-12 Thread Sean Whitton
Hello Markus,

On Tue, Dec 12 2017, Markus Koschany wrote:

> I agree that using boiler plate like this:
>
> | License: GPL-2+
> | On Debian systems the full text of the GPL-2 can be found in
> | /usr/share/common-licenses/GPL-2
>
> is still redundant.
>
> I suggest to change Debian Policy 12.5 and copyright format 1.0 in such
> a way that the following syntax is allowed:
>
> License: [GPL-2+]

This would mean that we are not explicitly stating in our d/copyright
file the difference between GPL-2 and GPL-2+.  To learn of the
difference, a user would need to view the full spec of the copyright
format.

This seems like a regression, as the current format is easily
easy to understand without reference to the spec.  It also means that
the package's copyright information is self-contained and not dependent
on some external document.  This is a feature we should preserve (and
might be legally required to preserve).

-- 
Sean Whitton


signature.asc
Description: PGP signature


Bug#211353: chrony: please add debconf question for entering timeserver

2017-12-12 Thread Vincent Blut

Hi Noah,

On Sat, Dec 09, 2017 at 12:52:09PM -0800, Noah Meyerhans wrote:

On Mon, Nov 16, 2015 at 11:30:05PM +0100, Vincent Blut wrote:

Marking as wontfix as I’m definitely not sure implementing the debconf
mechanism
for such thing is the right approach.


Hi. At a recent debian-cloud sprint, we made the choice to switch from
ntpd to chrony for our cloud images.


Great!

As some of the cloud providers offer their own local NTP services, we'd 
like the ability to specify an entry for such a source in the default 
images for a given service.


Seems fair.

As such, I'd like to ask on behalf of the cloud team that you 
reconsider providing a debconf option to select a time source. I'm 
happy to send patches if that'll help.


Well if that’s something the cloud team wants to further improve their 
integration work, I’d be happy to accept such a patch. However I think 
using debconf in this case is quite fragile. Configuring the preferred 
time source depending on the cloud provider we are running on should 
ideally be done at runtime.


My suggestion would be to maintain the current pool.ntp.org entry as 
the default, and offer a debconf option to override this value at 
debconf's low priority so it won't bother most people installing the 
package.


I’m not sure that overriding the default pool of NTP servers we are 
using is the right approach, we should instead add the time source 
provided by the user to the configuration file and append the “prefer” 
option to it, so that if any issue should arise with that manually 
filled time source, that would leave the user with a sane fallback.



Thanks
noah


Cheers,
Vincent


signature.asc
Description: PGP signature


Bug#884258: machinectl shell should use bash as a default

2017-12-12 Thread Michael Biebl
Am 13.12.2017 um 00:30 schrieb Marco d'Itri:
> Package: systemd-container
> Version: 235-3
> Severity: normal
> 
> Until https://github.com/systemd/systemd/issues/1395 will be fixed, 
> machinectl should be patched to use /bin/bash as the default shell 
> instead of /bin/sh.
> While some people may favour a different interactive shell it is quite 
> obvious that nobody wants to use dash as their interactive shell, so 
> this saves the need to type "exec bash" every time.
> 
> This is a single line change in bus_machine_method_open_shell() in 
> src/machine/machine-dbus.c.

Makes sense. Feel free to commit this change.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Bug#884259: mailman3-suite: postinst fails to finish due to password/keys containing '/'

2017-12-12 Thread Stephen Rothwell
Package: mailman3-suite
Version: 0+20170523-1
Severity: normal

Dear Maintainer,

   * What led up to the situation?

Trying to install mailman3-suite

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

aptitude install mailman3

   * What was the outcome of this action?

The postinst for mailman3-suite reported an error with "sed" and then hung

   * What outcome did you expect instead?

I expected the package to install correctly.

To make the postinst complete, I changed the 'sed' lines to use '|'
instead of '/' in their 's' expressions in the following invocation
(base64 will never produce '|' characters):

# Set custom settings in settings_local.py
sed -i -e "s|^\(\s*SECRET_KEY\s*=\s*'\)\S\+\('\s*\)$|\1$secretkey\2|" \
   -e 
"s|^\(\s*MAILMAN_REST_API_PASS\s*=\s*'\)\S\+\('\s*\)|\1$restapipass\2|" \
   -e 
"s|^\(\s*MAILMAN_ARCHIVER_KEY\s*=\s*'\)\S\+\('\s*\)|\1$archiverkey\2|" \
   -e "s|^\(\s*EMAILNAME\s*=\s*'\)\S\+\('\s*\)|\1$emailname\2|" \
   $settings_local_new

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

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

Versions of packages mailman3-suite depends on:
ii  dbconfig-pgsql2.0.9
ii  debconf [debconf-2.0] 1.5.65
ii  lsb-base  9.20170808
ii  mailman3-core 3.1.0-6
ii  node-less 1.6.3~dfsg-2
ii  python2.7.14-1
ii  python-django-hyperkitty  1.1.4-2
ii  python-django-postorius   1.1.0-1
ii  python-psycopg2   2.7.3-1
ii  python-whoosh 2.7.4+git6-g9134ad92-1
ii  ruby-sass 3.4.23-1
ii  ucf   3.0036
ii  uwsgi 2.0.15-10
ii  uwsgi-plugin-python   2.0.15-10

Versions of packages mailman3-suite recommends:
ii  libapache2-mod-proxy-uwsgi  2.0.15-10
ii  postgresql  10+188

mailman3-suite suggests no packages.

-- Configuration Files:
/etc/cron.d/mailman3-suite changed [not included]

-- debconf information:
  mailman3-suite/pgsql/admin-user: postgres
  mailman3-suite/internal/skip-preseed: false
  mailman3-suite/pgsql/authmethod-admin: ident
* mailman3-suite/remote/host: localhost
  mailman3-suite/remote/newhost: localhost
  mailman3-suite/restart-webserver: true
  mailman3-suite/emailname: ozlabs.org
  mailman3-suite/purge: false
  mailman3-suite/db/app-user: mailman3suite@localhost
* mailman3-suite/dbconfig-install: true
  mailman3-suite/pgsql/method: TCP/IP
  mailman3-suite/remote/port:
  mailman3-suite/install-error: abort
  mailman3-suite/missing-db-package-error: abort
  mailman3-suite/pgsql/no-empty-passwords:
  mailman3-suite/upgrade-backup: true
  mailman3-suite/superuser-mail: root@localhost
  mailman3-suite/pgsql/changeconf: false
  mailman3-suite/dbconfig-reinstall: false
  mailman3-suite/remove-error: abort
  mailman3-suite/reconfigure-webserver: apache2
  mailman3-suite/pgsql/authmethod-user: password
  mailman3-suite/dbconfig-remove: true
  mailman3-suite/superuser-name: admin
  mailman3-suite/database-type: pgsql
  mailman3-suite/internal/reconfiguring: false
  mailman3-suite/db/dbname: mailman3suite
  mailman3-suite/upgrade-error: abort
  mailman3-suite/pgsql/manualconf:
  mailman3-suite/passwords-do-not-match:
  mailman3-suite/dbconfig-upgrade: true


-- 
Cheers,
Stephen Rothwell



Bug#884250: silverjuke: FTBFS against upnp 1.8

2017-12-12 Thread Dr. Tobias Quathamer
control: forwarded -1 https://github.com/silverjuke/silverjuke/issues/81

Am 12.12.2017 um 22:18 schrieb Sebastian Ramacher:
> silverjuke FTBFS against upnp 1.8 (available in experimental):

Hi,

I've forwarded this to upstream, thanks a lot for your report.

Regards,
Tobias



signature.asc
Description: OpenPGP digital signature


Bug#884224: debian-policy: please add CC-BY-3.0 to common licenses

2017-12-12 Thread Sean Whitton
control: forcemerge 795402 -1
control: forcemerge 795402 884225

Hello,

On Tue, Dec 12 2017, Markus Koschany wrote:

> as discussed on debian-devel [1]

Please check for pre-existing books!  Thanks.

-- 
Sean Whitton


signature.asc
Description: PGP signature


Bug#877966: This is happening again

2017-12-12 Thread Julien Cristau
On 12/12/2017 03:39 PM, Tollef Fog Heen wrote:
> ]] Santiago Vila 
> 
>> While building a lot of packages today, I found that this is happening again:
>>
>> 503  Quorum weight not reached [IP: 151.101.112.204 80]
> 
> Hi,
> 
> yeah, we saw an outage on the 9th, need to investigate why it hit us.  I
> suspect it was due to (all dates the the 9th, all times are UTC):
> 
> 21:08:21 mirror push on mirror-conova is done
> 21:08:22 mirror-skroutz declares itself unhealthy due to being out of date
> 21:08:58 mirror-accumu declares itself unhealthy due to being out of date
> 21:09:10 mirror-bytemark declares itself unhealthy due to being out of date
> 21:09:56 mirror-conova declares itself unhealthy due to scheduled shutdown

I've updated ldap so we don't schedule shutdowns of mirror-conova when
it's in the middle of pushing others, which should help a bit.

Cheers,
Julien



Bug#877966: This is happening again

2017-12-12 Thread Julien Cristau
On 12/12/2017 03:39 PM, Tollef Fog Heen wrote:
> DSA, thoughts on this?  Sounds reasonable?
> 
I think the issue is also made worse by mirror-bytemark being
consistently much slower than the other backends, and how ftpsync
behaves in a pathological way when mirrors have very different speeds.

When doing a staged push, we start stage1 for all downstreams.  Each of
those, when it's done, waits for up to $PUSHDELAY, by default 10
minutes, for its siblings to signal they're also done with stage1.  If
all goes well, everyone waits for everyone else to be done with stage1,
then within 5 seconds of each other they run stage2.

If on the other hand one mirror gets ahead (as often happens with
mirror-conova), or one mirror gets behind (as always happens with
mirror-bytemark), then the first mirror to finish stage1 waits 10
minutes, then removes its stage1 lock and starts stage2.  The other
mirrors are never going to find the stage1 lock from the fast mirror, so
they'll each wait the whole 10 minutes, even though they could have
started stage2 at the same time as the first because they finished
within the 10 minutes.

So we're in something of a worst case here where
- the mirror-conova push is local, so it's pretty fast
- mirror-skroutz and mirror-accumu are reasonably fast, but still take a
few minutes more than mirror-conova for stage1
- mirror-bytemark is way slow so consistently needs over 10 minutes more
than mirror-conova for stage1
- after 10 minutes, mirror-conova gives up on waiting for bytemark, and
starts stage2
- by that time mirror-accumu and mirror-skroutz are done with their
stage1, but they still each wait for 10 minutes before starting stage2,
so the delay between mirror-conova and them for finishing stage1 is
preserved for stage2, and they end up out of sync for a while for no
good reason
- at some point later, mirror-bytemark catches up

So I wonder if we should:
- kill mirror-bytemark until we fix the I/O issue that plagues us there
- increase PUSHDELAY
- change ftpsync so the first mirror that times out waiting for stage1
locks touches ${LOCKDIR}/all_stage1 so its siblings don't wait in vain
making the problem worse
- a combination of the above

Cheers,
Julien



Bug#878165: Fix upstream

2017-12-12 Thread Alejandro Lorenzo Gallego
Maybe this is related to kernel bug 197147. If you are running kernel 4.14 you 
are almost guaranteed to have hit it.

The intel team has confirmed there is a problem in the BT firlwamre and have 
published updated firmware that fixes the problem (at least for me). 

So basically, upstream has fixed the issue. In the discussion ( https://
bugzilla.kernel.org/show_bug.cgi?id=197147 ) theree is a .tar.gz with thd new 
firmware files that should be copied to /lib/firmware/intel 

Give it a try, and if it fixes it, the package mantainer should consider, 
please, updating to the latests firmware 

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


Bug#884258: machinectl shell should use bash as a default

2017-12-12 Thread Marco d'Itri
Package: systemd-container
Version: 235-3
Severity: normal

Until https://github.com/systemd/systemd/issues/1395 will be fixed, 
machinectl should be patched to use /bin/bash as the default shell 
instead of /bin/sh.
While some people may favour a different interactive shell it is quite 
obvious that nobody wants to use dash as their interactive shell, so 
this saves the need to type "exec bash" every time.

This is a single line change in bus_machine_method_open_shell() in 
src/machine/machine-dbus.c.

-- 
ciao,
Marco


signature.asc
Description: PGP signature


Bug#884257: digikam: Experimental version no more installable

2017-12-12 Thread Eric Valette
Package: digikam
Version: 4:5.7.0-2
Severity: grave
Justification: renders package unusable

apt-get -t experimental install digikam-private-libs
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 digikam-private-libs : Depends: libmarblewidget-qt5-25 (>= 4:15.12.0) but it 
is not going to be installed
E: Unable to correct problems, you have held broken packages.

dpkg -l libmarblewidget*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersionArchitecture   
Description
+++-===-==-==-
ii  libmarblewidget-qt5-28  4:17.08.3-2amd64  Marble 
globe widget library
tri-yann4:/home/valette# 


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

Kernel: Linux 4.14.5 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages digikam depends on:
ii  digikam-data  4:5.6.0-4
ii  digikam-private-libs  4:5.6.0-4+b1
ii  kipi-plugins  4:5.6.0-4+b1
ii  libc6 2.26-0experimental1
ii  libgcc1   1:7.2.0-17
ii  libkf5configcore5 5.37.0-2
ii  libkf5coreaddons5 5.37.0-2
ii  libkf5filemetadata3   5.37.0-2
ii  libkf5i18n5   5.37.0-2
ii  libqt5core5a  5.9.2+dfsg-6
ii  libqt5gui55.9.2+dfsg-6
ii  libqt5sql55.9.2+dfsg-6
ii  libqt5sql5-mysql  5.9.2+dfsg-6
ii  libqt5sql5-sqlite 5.9.2+dfsg-6
ii  libqt5widgets55.9.2+dfsg-6
ii  libstdc++67.2.0-17
ii  perl  5.26.1-3

Versions of packages digikam recommends:
ii  ffmpegthumbs4:17.08.3-1
ii  firefox [www-browser]   57.0.1-1
ii  firefox-esr [www-browser]   52.5.2esr-1
ii  google-chrome-stable [www-browser]  63.0.3239.84-1
ii  konqueror [www-browser] 4:17.08.1-1
ii  links2 [www-browser]2.14-5
ii  lynx [www-browser]  2.8.9dev16-2
ii  w3m [www-browser]   0.5.3-34

Versions of packages digikam suggests:
pn  digikam-doc 
ii  systemsettings  4:5.10.5-2

-- no debconf information



Bug#884256: pysph: please make the build reproducible

2017-12-12 Thread Chris Lamb
Source: pysph
Version: 0~20160514.git91867dc-4
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: kernel
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0], we noticed
that pysph could not be built reproducibly.

This is because it generates a Python .egg in a directory that is
named with the current kernel version. On the Debian i386 architecture
this can either be i686 or x86_64 when running the 64-bit kernel.

Patch attached that uses --single-version-externally-managed instead,
preventing the generation of the egg in the first place.

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/rules  2017-12-12 21:27:30.217492858 +
--- b/debian/rules  2017-12-12 22:39:47.621834301 +
@@ -13,8 +13,7 @@
 
 override_dh_auto_install:
dh_numpy
-   mkdir -p $(CURDIR)/debian/tmp/usr/lib/python2.7/site-packages/
-   python setup.py install --prefix=$(CURDIR)/debian/tmp/usr
+   python setup.py install --root=$(CURDIR)/debian/tmp 
--single-version-externally-managed --install-layout=deb --no-compile
rm -rf 
$(CURDIR)/debian/tmp/usr/lib/python2.7/site-packages/setuptools.pth
rm -rf $(CURDIR)/debian/tmp/usr/lib/python2.7/site-packages/sit*
 


Bug#884254: pydoctor: please make the output reproducible

2017-12-12 Thread Chris Lamb
forwarded 884254 https://github.com/twisted/pydoctor/pull/146
thanks

I've gone ahead and forwarded this upstream here:

  https://github.com/twisted/pydoctor/pull/146


Regards,

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



Bug#875688: libreoffice-report-builder: report builder inactive in 5.4

2017-12-12 Thread Rene Engelhard
Hi Lionel,

On Thu, Dec 07, 2017 at 04:28:10PM +0100, Lionel Elie Mamane wrote:
> The Debian package of 5.4 behaves as if the optional part of
> LibreOffice "Report Builder" was not installed, although the packages
> libreoffice-report-builder and libreoffice-report-builder-bin are
> installed. I haven't diagnosed why.

Interestingly, in my sid test vm, the 5.4.4 packages from 
https://people.debian.org/~rene/libreoffice/5.4/ do show it again *but*
you marked it as found in 6.0.0 beta2 and yes, I don't see it there
either anymore...

*sigh*

> The immediate cause is that in file
>  dbaccess/source/ui/misc/linkeddocuments.cxx
>  function OLinkedDocumentsAccess::open, the call to impl_open throws a
>  css::io::WrongFormatException,
> but what is the underlying reason for that? Probably the internal
> LibreOffice registry doesn't have properly registered the optional
> "Report Builder" part (could be an error in
> /usr/lib/libreoffice/share/registry/reportbuilder.xcd or that file is
> not loaded), or it fails to load for some reason.

But it is there and was there. And if it was that, why is it different
between versions and without any change to what we do with that file?

Regards,

Rene



Bug#884254: pydoctor: please make the output reproducible

2017-12-12 Thread Chris Lamb
Source: pydoctor
Version: 16.3.0-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: fileordering toolchain
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0], we noticed
that pydoctor generates output that is not reproducible.

This affects other packages such as "subvertpy" amongst others.

Patch attached.

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/pydoctor/model.py b/pydoctor/model.py
index 173e7f4..6159441 100644
--- a/pydoctor/model.py
+++ b/pydoctor/model.py
@@ -621,7 +621,7 @@ class System(object):
 package = self.ensurePackage(package_full_name)
 package.filepath = dirpath
 self.setSourceHref(package)
-for fname in os.listdir(dirpath):
+for fname in sorted(os.listdir(dirpath)):
 fullname = os.path.join(dirpath, fname)
 if os.path.isdir(fullname):
 initname = os.path.join(fullname, '__init__.py')


Bug#884255: pydoctor: Please add Homepage field to debian/control

2017-12-12 Thread Chris Lamb
Source: pydoctor
Version: 16.3.0-1
Severity: wishlist
Tags: patch

Hi,

Patch attached that adds a Homepage field to debian/control.


Regards,

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


Bug#883731: audacious: Debian packaging has incorrect license

2017-12-12 Thread Francesco Poli
On Tue, 12 Dec 2017 16:39:28 -0500 Nicholas D Steeves wrote:

[...]
> This is one of the reasons the FSF demands copyright
> assignment for their projects...they want to be able to relicense at
> any point in the future without having to contact and document consent
> from all contributors.

Yeah, right: they want to do what they like, without asking whether the
contributors are fine with their decisions...
Personally, I consider this FSF copyright assignment policy a very bad
practice!

But I am digressing...

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


pgpwQpqVq4zMN.pgp
Description: PGP signature


Bug#884253: RFP: gpxsee -- GPS log file viewer and analyzer that supports GPX, TCX, KML, FIT, IGC and NMEA files

2017-12-12 Thread Martin Tůma
Package: wnpp
Severity: wishlist

* Package name: gpxsee
  Version : 4.17
  Upstream Author : Martin Tuma 
* URL : http://www.gpxsee.org/
* License : GPL3
  Programming Lang: C++
  Description : GPS log file viewer and analyzer that supports GPX, TCX,
KML, FIT, IGC and NMEA files

Features:
  - User-definable online maps.
  - Offline maps (OziExplorer maps and TrekBuddy maps/atlases).
  - Elevation, speed, heart rate, cadence, power and temperature graphs.
  - Support for multiple tracks in one view.
  - Support for POI files.
  - Print/export to PDF.
  - Full-screen mode.
  - Opens GPX, TCX, FIT, KML, IGC, NMEA and Garmin CSV files.

GPXSee has no other dependencies than QT. There is already
a Debian package at the projects OpenSUSE build service repository
(https://build.opensuse.org/package/show/home:tumic:GPXSee/gpxsee)
that can be used as the base for the "official" Debian package.
GPXSee is part of the official OpenSUSE and Fedora repositories.



Bug#884232: ffmpeg: CVE-2017-17555

2017-12-12 Thread Carl Eugen Hoyos
This is not a bug in FFmpeg:
aubio initializes libswresample with 2 channels and then passes data
that contains just one channel.

That cant really work or how could it ?
swresample has no knowledge about what is in the array except what it
is told
There are multiple ways to provide this information to swr

(Answer from Michael on ffmpeg-security)

Carl Eugen



Bug#880546: Packaging Isabelle was requested before but the plan was dropped

2017-12-12 Thread Torsten Landschoff
Have a look at this bug:

https://bugs.debian.org/494491

It looks for me like upstream would prefer not to have a Isabelle Debian
package. :-(



Bug#835542: flex: comparison between signed and unsigned integer expressions

2017-12-12 Thread Alexander Koeppe
On Fri, 06 Oct 2017 10:58:32 +0200 Pedro Gimeno
 wrote:
> I'm getting the same issue reported in message #5 with flex 2.6.1-1.3
amd64.
>
> $ echo %% | flex ; gcc -c -Wsign-compare lex.yy.c
> lex.yy.c: In function ‘yy_get_next_buffer’:
> lex.yy.c:557:18: warning: comparison between signed and unsigned
integer expressions [-Wsign-compare]
> for ( n = 0; n < max_size && \
> ^
> lex.yy.c:960:3: note: in expansion of macro ‘YY_INPUT’
> YY_INPUT( (_CURRENT_BUFFER_LVALUE->yy_ch_buf[number_to_move]),
> ^~~~
>
> Downgrading to 2.6.1-1.2 did not solve the issue.
>
>

I'm facing exactly the same issue. Seem the bug went back into the package.



Bug#877966: This is happening again

2017-12-12 Thread Tollef Fog Heen
]] Santiago Vila 

> While building a lot of packages today, I found that this is happening again:
> 
> 503  Quorum weight not reached [IP: 151.101.112.204 80]

Hi,

yeah, we saw an outage on the 9th, need to investigate why it hit us.  I
suspect it was due to (all dates the the 9th, all times are UTC):

21:08:21 mirror push on mirror-conova is done
21:08:22 mirror-skroutz declares itself unhealthy due to being out of date
21:08:58 mirror-accumu declares itself unhealthy due to being out of date
21:09:10 mirror-bytemark declares itself unhealthy due to being out of date
21:09:56 mirror-conova declares itself unhealthy due to scheduled shutdown
21:16:44 mirror push on mirror-skroutz is done
21:17:22 mirror-skroutz declares itself healthy
21:17:37 mirror push on mirror-accumu is done
21:17:58 mirror-accumu declares itself healthy
21:19:32 mirror-skroutz hits a bug in mirror-health and declares itself
 unhealthy due to connect timeouts to mirror-conova
21:20:07 mirror-accumu hits a bug in mirror-health and declares itself
 unhealthy due to connect timeouts to mirror-conova
21:26:10 mirror-accumu comes back and is healthy
21:26:11 mirror-skroutz comes back and is healthy
21:26:53 mirror-conova comes back and is healthy

Dec 10:
03:45:34 mirror-bytemark push is done
03:45:47 mirror-bytemark comes back and is healthy

So what happened was essentially that we did a reboot *just* after a
push had finished, leading to a mirror declaring itself unhealthy.

I've fixed the bug that caused the second outage from ~2120 until ~2126
now, so we should not run into that one again at least.

I wonder if the right fix is to ignore timestamps from any unhealthy
hosts, and to reset latest_ts on each iteration through check_uptodate.
If we initialise latest_ts to 0, that will mean we do consider ourselves
healthy in the case of nobody else being healthy.  If somebody else is
newer than us and healthy, we consider ourselves unhealthy.

DSA, thoughts on this?  Sounds reasonable?

Cheers,
-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are



Bug#884115: Ioslides inside rmarkdown has no license

2017-12-12 Thread Andreas Tille
Hi Yihui,

On Tue, Dec 12, 2017 at 02:32:50PM -0600, Yihui Xie wrote:
> 
> I took over the maintenance of the rmarkdown package only recently, and I
> was not the person who introduced ioslides to the rmarkdown package. That
> said, it does seem that the ioslides library's license is missing and
> unclear. I'm not its author, so I cannot add a license to it. I guess it
> will be difficult to get in touch with its original authors.

I'm in touch with a fork author which I assumed the author and hope for
clarification[1]
 
> I don't quite see the benefits of making a Debian package for rmarkdown. It
> is an R package, and it is fairly easy to install from CRAN. Those who use
> R should be able to install it without sudo apt-get, and those who do not
> use R probably won't care about an R package.

I have heard this argument very frequently but it is simply wrong.  We
have some packages in Debian which internally are using R packages.  If
we do not provide this package we need to restrict the functionality of
those packages which is clearly not in our interest.

> On the other hand, I guess a
> Debian version of rmarkdown that does not have ioslides can be confusing.

I wonder whether it is conform with CRAN guidelines to have parts of
code which has no license.  According to Debian rules this is non-free
and can not be distributet.  I would be astonished if CRAN rules would
be more relaxed in this aspect.

Kind regards and thanks for your quick reply

   Andreas.

[1] https://github.com/pauldijou/ioslides/issues/1

-- 
http://fam-tille.de



Bug#838208: libiodbc2 FTCBFS: uses build architecture pkg-config

2017-12-12 Thread Manuel A. Fernandez Montecelo

Control: tags -1 + pending


Hi,

2017-11-01 00:09 Manuel A. Fernandez Montecelo:

Hi,

2016-09-18 15:22 Helmut Grohne:

Source: libiodbc2
Version: 3.52.9-2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

libiodbc2 fails to cross build from source, because it uses the build
architecture pkg-config. Thus it fails finding gtk and that results in
missing files. It seems that ./admin/gtk-2.0.m4 has its own code for
discovering which $PKG_CONFIG to use rather than using a standard
autoconf macro. Thus it does not default to use the triplet-prefixed
pkg-config and does not consider the PKG_CONFIG environment variable
either. The attached patch forces the right pkg-config via the
corresponding cache variable. Please consider applying the patch or
fixing the .m4 file to use standard (working) checks.


Do you have any plans to upload a new version of the package, and if so,
what do you think of this fix?

Are you OK with the fix and would it help if we offer to NMU, to move
this forward?


Uploaded to delayed/10, please tell me if you would like me to to cancel
the NMU; or if it's OK, if I can re-schedule it to happen sooner.

.debdiff attached, it's basically what Helmut already sent as patch.


Cheers.
--
Manuel A. Fernandez Montecelo 
diff -Nru libiodbc2-3.52.9/debian/changelog libiodbc2-3.52.9/debian/changelog
--- libiodbc2-3.52.9/debian/changelog   2014-05-29 13:06:37.0 +0200
+++ libiodbc2-3.52.9/debian/changelog   2017-12-12 22:31:37.0 +0100
@@ -1,3 +1,12 @@
+libiodbc2 (3.52.9-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Helmut Grohne ]
+  * Fix FTCBFS: Force using triplet-prefixed pkg-config. (Closes: #838208)
+
+ -- Manuel A. Fernandez Montecelo   Tue, 12 Dec 2017 22:31:37 
+0100
+
 libiodbc2 (3.52.9-2) unstable; urgency=medium
 
   * Set SYSTEM_DIR to the odbc multiarch path. (Closes: #749427)
diff -Nru libiodbc2-3.52.9/debian/rules libiodbc2-3.52.9/debian/rules
--- libiodbc2-3.52.9/debian/rules   2014-05-29 13:06:37.0 +0200
+++ libiodbc2-3.52.9/debian/rules   2017-12-12 22:30:26.0 +0100
@@ -1,8 +1,9 @@
 #!/usr/bin/make -f
 
-DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
+include /usr/share/dpkg/architecture.mk
 
 export DEB_CFLAGS_MAINT_APPEND = 
-DSYSTEM_DIR=\"/usr/lib/$(DEB_HOST_MULTIARCH)/odbc\"
+export ac_cv_path_PKG_CONFIG=$(DEB_HOST_GNU_TYPE)-pkg-config
 
 %:
dh $@ --parallel --with autoreconf,pkgkde_symbolshelper


Bug#884252: libupnp-dev: missing ThreadPool.h

2017-12-12 Thread James Cowgill
Control: forwarded -1 https://github.com/mrjimenez/pupnp/issues/56
Control: tags -1 fixed-upstream

Hi,

On 12/12/17 21:22, Sebastian Ramacher wrote:
> Source: pupnp-1.8
> Version: 1:1.8.3-1
> Severity: important
> 
> While rebuilding all reverse build dependencies of libupnp-dev, I noticed that
> linux-igd fails with the following error:
> | cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -fdebug-prefix-map=/<>/linux-igd-1.0+cvs20070630=. 
> -fstack-protector-strong -Wformat -Werror=format-security -DDEBUG -pthread 
> -I/usr/include/upnp -D_GNU_SOURCE -c main.c
> | In file included from globals.h:7:0,
> |  from main.c:13:
> | /usr/include/upnp/upnpdebug.h:40:10: fatal error: ThreadPool.h: No such 
> file or directory
> |  #include "ThreadPool.h"
> |   ^~
> | compilation terminated.
> | Makefile:44: recipe for target 'main.o' failed
> 
> Please either include ThreadPool.h in the package or fix the includes of
> upnpdebug.h

This has already been fixed upstream:
https://github.com/mrjimenez/pupnp/commit/9220f76b17816b476f7662bae959d9f403046a37

The above bug has some related info.

Thanks,
James



signature.asc
Description: OpenPGP digital signature


Bug#883731: audacious: Debian packaging has incorrect license

2017-12-12 Thread Nicholas D Steeves
Hi Ian, Francesco, John, and everyone else reading this,

On Mon, Dec 11, 2017 at 12:28:43AM -0500, John Lindgren wrote:
> On 12/10/2017 06:12 PM, Nicholas D Steeves wrote:
> > In particular I'm concerned about lines like this from
> > d/copyright:
> > 
> > "po/uk.po" is © 2005 Mykola Lynnyk and is distributed under the terms of the
> >  GPL.
> > 
> > Where the new po/uk.po is GPL-incompatible 2-clause BSD:
> 
> The line "Copyright (C) 2005 Mykola Lynnyk <...>" appears to have been
> lost accidentally in commit 1a013156d209b, when we switched over to
> Transifex.  I'll see about restoring it.
> 
> As far as our Git history goes back (to October 2005), uk.po had no
> license declaration and was assumed to be under the same license as the
> source files it translated (which at the time was GPLv2+). At the time
> of the BSD relicense, we took the liberty of assuming that such
> translations would automatically switch to the new license along with
> the source files they translated.  No one (to my knowledge) has
> contacted us in the five years since to clarify that their translations
> were intended to be forever GPL-only, but I suppose that to take a more
> cautious approach, Debian could still distribute the package as GPL in
> total.

For Debian Legal Team: With respect to the translations, I now suspect
they can probably be transitioned to BSD without issue, because
copyright is also assigned to the Audacious Translators.  eg, in the
last GPL-2+ release 3.2.4:
Copyright (C) Audacious translators

Would you please confirm?  It would be nice to be able to simplify the
issue of relicensing for the translations :-)  Also, would you please
confirm or deny the necessity of the work outlined in the second half
of this email?


John, I removed the offending patch in git for the user-visible
license provided by the Audacious GUI.  Then I went ahead and did a
historical relicensing review, in spite of the potential for other
missing copyright holders due to the Transifex switch.  I am a bit
concerned about what looks to be a politic of "silence is consent" wrt
relicensing, and hope that I am wrong, or that I was sloppy in my
review.  Was the discussing conducted informally off the record?

By the way, I definitely support every author's right to choose a
preferred license, so I'm not troubled with a transition to BSD
licensing ;-) This is one of the reasons the FSF demands copyright
assignment for their projects...they want to be able to relicense at
any point in the future without having to contact and document consent
from all contributors.

Would you please take a look at the following (Ian's reply) for an
example of how to provide a record of all copyright holder's consent?
tldr; documented confirmation (eg: via copies of emails or a download
of a bug report/issue/forum thread) for all contributors who did not
assign copyright to the Audacious Team in the headers of the files
they contributed to.  I would be happy to generate such a file[s] if
you can point me in the right direction[s].

On Mon, Dec 11, 2017 at 03:03:09PM +, Ian Jackson wrote:
> Nicholas D Steeves writes ("Re: Bug#883731: audacious: Debian packaging has 
> incorrect license"):
> > Will I also need to provide formal copies in debian/COPYING.emails or
> > would a README.copyright or similar pointing to the bug report
> > suffice?  In particular I'm concerned about lines like this from
> > d/copyright:
> 
> Please put all the necessary information in the source package.
> 
> COPYING.emails is only one filename you might choose to use.  If you
> want to download multiple pages, or something, you can put them in
> separate files.  It's probably a good idea to download them with w3m
> -dump or something.  That produces a human-readable file which doesn't
> depend on any external HTML assets.
> 
> This is much better than simply urls, because (sadly), urls often rot.
> The lifetime of the contents in debian/ is controlled by Debian and
> often exceeds, by large factors, the lifetime of upstream source
> repositories, bug trackers, etc.
> 
> It would be a best praqctice to record the contents _and also_ the url
> you got it from, and the date you downloaded it.  That way the
> information you give is verifiable while the url is still active; and
> if the url rots, the information (attribution, etc.) is not lost.
> 
> So in summary, I would 
>   w3m -dump https://bugtracker/whatever > debian/COPYING.issue4391.txt
> and make an overview file (COPYING.emails maybe) referring to
> these other files.

Specific commits I couldn't find documented consent for, and which
didn't have have copyright assigned to the Audacious Team in the last
stable GPL-2+ release (3.2.4).  From the git history I see it was a
lot of work to transition to BSD!  Here are a couple examples
copyright holders that I believe Audacious will need explicit consent
from (see above) for relicensing to BSD:

42cbe57307962e65acc2db24dbe99249453c6aac

Bug#883977: *** stack smashing detected ***: evolution terminated

2017-12-12 Thread gregor herrmann
On Mon, 11 Dec 2017 23:12:46 +0100, Michael Biebl wrote:

> > rebuilding evolution fixes the problem for me.
> > Maybe re-assign to evolution?
> Jeremy did sourceful uploads of evo and eds and other rdeps of libical
> were binNMUed, so I guess this should be fixed after the next update.

Thanks, and yes, works for me with today's evolution version. 


Cheers,
gregor, leaving the bug-closing stip to nomeata


-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Funny van Dannen: Rote Schuhe


signature.asc
Description: Digital Signature


Bug#884252: libupnp-dev: missing ThreadPool.h

2017-12-12 Thread Sebastian Ramacher
Source: pupnp-1.8
Version: 1:1.8.3-1
Severity: important

While rebuilding all reverse build dependencies of libupnp-dev, I noticed that
linux-igd fails with the following error:
| cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>/linux-igd-1.0+cvs20070630=. 
-fstack-protector-strong -Wformat -Werror=format-security -DDEBUG -pthread 
-I/usr/include/upnp -D_GNU_SOURCE -c main.c
| In file included from globals.h:7:0,
|  from main.c:13:
| /usr/include/upnp/upnpdebug.h:40:10: fatal error: ThreadPool.h: No such file 
or directory
|  #include "ThreadPool.h"
|   ^~
| compilation terminated.
| Makefile:44: recipe for target 'main.o' failed

Please either include ThreadPool.h in the package or fix the includes of
upnpdebug.h

Cheers

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

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


signature.asc
Description: PGP signature


Bug#884251: wmaloader: FTBFS against upnp 1.8

2017-12-12 Thread Sebastian Ramacher
Source: wmaloader
Version: 0.1-5.1
Severity: important

wmaloader FTBFS against upnp 1.8 (available in experimental):
| gcc -Wall -O2 -I/usr/include/upnp  -D_REENTRANT   -c -o wmaloader.o 
wmaloader.c
| wmaloader.c:35:10: fatal error: LinkedList.h: No such file or directory
|  #include "LinkedList.h"
|   ^~
| compilation terminated.
| : recipe for target 'wmaloader.o' failed
| make[1]: *** [wmaloader.o] Error 1

Full log at
https://people.debian.org/~sramacher/logs/upnp/wmaloader_amd64-2017-12-12T20:57:00Z.log

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature


Bug#884250: silverjuke: FTBFS against upnp 1.8

2017-12-12 Thread Sebastian Ramacher
Source: silverjuke
Version: 16.5.3-1
Severity: important
Tags: sid buster

silverjuke FTBFS against upnp 1.8 (available in experimental):
| g++ -DPACKAGE_NAME=\"silverjuke\" -DPACKAGE_TARNAME=\"silverjuke\" 
-DPACKAGE_VERSION=\"16.5.3\" -DPACKAGE_STRING=\"silverjuke\ 16.5.3\" 
-DPACKAGE_BUGREPORT=\"r...@b44t.com\" -DPACKAGE_URL=\"\" 
-DPACKAGE=\"silverjuke\" -DVERSION=\"16.5.3\" -DENABLE_NLS=1 -DHAVE_GETTEXT=1 
-DHAVE_DCGETTEXT=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_ENDIAN_H=1 -I.  
-Isrc -I/usr/lib/x86_64-linux-gnu/wx/include/gtk2-unicode-3.0 
-I/usr/include/wx-3.0 -D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXGTK__ -pthread 
-I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libdrm  
-DPKGDATADIR=\"/usr/share/silverjuke\" 
-DPKGDOCDIR=\"/usr/share/doc/silverjuke\" -Wdate-time -D_FORTIFY_SOURCE=2 -Isrc 
-Wall -Wno-unused-but-set-variable -g
-I/usr/lib/x86_64-linux-gnu/wx/include/gtk2-unicode-3.0 -I/usr/include/wx-3.0 
-D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXGTK__ -pthread -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o src/sjmodules/scanner/silverjuke-upnp_scanner.o 
`test -f 'src/sjmodules/scanner/upnp_scanner.cpp' || echo 
'./'`src/sjmodules/scanner/upnp_scanner.cpp
| src/sjmodules/scanner/upnp_scanner.cpp: In function 'int 
client_event_handler(Upnp_EventType, void*, void*)':
| src/sjmodules/scanner/upnp_scanner.cpp:571:49: error: invalid use of 
incomplete type 'struct client_event_handler(Upnp_EventType, void*, 
void*)::Upnp_Discovery'
|  int error = UpnpDownloadXmlDoc(discoverEvent->Location, 
_description_doc);
|  ^~
| src/sjmodules/scanner/upnp_scanner.cpp:568:12: note: forward declaration of 
'struct client_event_handler(Upnp_EventType, void*, void*)::Upnp_Discovery'
|  struct Upnp_Discovery* discoverEvent = (struct Upnp_Discovery*)p_event;
| ^~
| src/sjmodules/scanner/upnp_scanner.cpp:571:51: error: invalid use of 
incomplete type 'struct client_event_handler(Upnp_EventType, void*, 
void*)::Upnp_Discovery'
|  int error = UpnpDownloadXmlDoc(discoverEvent->Location, 
_description_doc);
|^~~~
| src/sjmodules/scanner/upnp_scanner.cpp:568:12: note: forward declaration of 
'struct client_event_handler(Upnp_EventType, void*, void*)::Upnp_Discovery'
|  struct Upnp_Discovery* discoverEvent = (struct Upnp_Discovery*)p_event;
| ^~
| src/sjmodules/scanner/upnp_scanner.cpp:576:96: error: invalid use of 
incomplete type 'struct client_event_handler(Upnp_EventType, void*, 
void*)::Upnp_Discovery'
|   g_upnpModule->LogMinorUpnpError("Cannot download device description", 
error, discoverEvent->Location);
|   
  ^~
| src/sjmodules/scanner/upnp_scanner.cpp:568:12: note: forward declaration of 
'struct client_event_handler(Upnp_EventType, void*, void*)::Upnp_Discovery'
|  struct Upnp_Discovery* discoverEvent = (struct Upnp_Discovery*)p_event;
| ^~
| src/sjmodules/scanner/upnp_scanner.cpp:576:98: error: invalid use of 
incomplete type 'struct client_event_handler(Upnp_EventType, void*, 
void*)::Upnp_Discovery'
|   g_upnpModule->LogMinorUpnpError("Cannot download device description", 
error, discoverEvent->Location);
|   
^~~~
| src/sjmodules/scanner/upnp_scanner.cpp:568:12: note: forward declaration of 
'struct client_event_handler(Upnp_EventType, void*, void*)::Upnp_Discovery'
|  struct Upnp_Discovery* discoverEvent = (struct Upnp_Discovery*)p_event;
| ^~
| src/sjmodules/scanner/upnp_scanner.cpp:582:61: error: invalid use of 
incomplete type 'struct client_event_handler(Upnp_EventType, void*, 
void*)::Upnp_Discovery'
|   parseDeviceDescription(p_description_doc, discoverEvent->Location, 
this_, _->m_mediaServerList);
|  ^~
| src/sjmodules/scanner/upnp_scanner.cpp:568:12: note: forward declaration of 
'struct client_event_handler(Upnp_EventType, void*, void*)::Upnp_Discovery'
|  struct Upnp_Discovery* discoverEvent = (struct Upnp_Discovery*)p_event;
| ^~
| src/sjmodules/scanner/upnp_scanner.cpp:582:63: error: invalid use of 
incomplete type 'struct client_event_handler(Upnp_EventType, void*, 
void*)::Upnp_Discovery'
|   parseDeviceDescription(p_description_doc, discoverEvent->Location, 
this_, _->m_mediaServerList);
|^~~~
| src/sjmodules/scanner/upnp_scanner.cpp:568:12: 

Bug#884249: ring: FTBFS against upnp 1.8

2017-12-12 Thread Sebastian Ramacher
Source: ring
Version: 20171129.2.cf5bbff~ds1-1
Severity: important
Tags: sid buster

ring FTBFS against upnp 1.8 (available in experimental)
| ../../doltlibtool  --tag=CXX   --mode=compile g++-6 -DHAVE_CONFIG_H -I. 
-I../..  -I/<>/daemon/src -I/<>/daemon/src/config 
-I/<>/daemon/src/media -I/<>/daemon/test 
-I/<>/daemon/src/dring  -DPREFIX=\"/usr\" 
-DPROGSHAREDIR=\"/usr/share/ring\" -DENABLE_TRACE -DRING_REVISION=\"\" 
-DRING_DIRTY_REPO=\"dirty\" -DPJSIP_MAX_PKT_LEN=8000 -DPJ_AUTOCONF=1 
-DHAVE_SPEEX_CODEC -DHAVE_GSM_CODEC -DHAVE_OPUS -Wdate-time -D_FORTIFY_SOURCE=2 
-I/<>/daemon/contrib/x86_64-linux-gnu/include -I./ -I../ 
-DPREFIX=\"/usr\" -DPROGSHAREDIR=\"/usr/share/ring\" -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DMSGPACK_DEFAULT_API_VERSION=1 -DPJ_AUTOCONF=1  
-I/<>/daemon/contrib/x86_64-linux-gnu/include -MT 
libclient_la-videomanager.lo -MD -MP -MF .deps/libclient_la-videomanager.Tpo -c 
-o libclient_la-videomanager.lo `test -f 'videomanager.cpp' || echo 
'./'`videomanager.cpp
| In file included from configurationmanager.cpp:43:0:
| /<>/daemon/src/upnp/upnp_context.h:225:48: error: 
'Upnp_Discovery' does not name a type
|  void parseDevice(IXML_Document* doc, const Upnp_Discovery* d_event);
| ^~
| /<>/daemon/src/upnp/upnp_context.h:227:45: error: 
'Upnp_Discovery' does not name a type
|  void parseIGD(IXML_Document* doc, const Upnp_Discovery* d_event);
|  ^~
| Makefile:550: recipe for target 'libclient_la-configurationmanager.lo' failed
| make[5]: *** [libclient_la-configurationmanager.lo] Error 1

Full log at
https://people.debian.org/~sramacher/logs/upnp/ring_amd64-2017-12-12T20:48:40Z.log

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature


Bug#884248: mpd: FTBFS against upnp 1.8

2017-12-12 Thread Sebastian Ramacher
Source: mpd
Version: 0.20.11-1
Severity: important
Tags: sid buster

mpd FTBFS against upnp 1.8 (available in experimental)
| g++ -DHAVE_CONFIG_H -I.  -DNDEBUG -I./src -I/usr/include 
-DSYSTEM_CONFIG_FILE_LOCATION='"/etc/mpd.conf"' -Wdate-time -D_FORTIFY_SOURCE=2 
-D_GNU_SOURCE -pthread -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -fvisibility=hidden 
-fno-threadsafe-statics -fmerge-all-constants -ffast-math -ftree-vectorize 
-ffunction-sections -fdata-sections -Wall -Wextra -Wmissing-declarations 
-Wshadow -Wpointer-arith -Wcast-qual -Wwrite-strings -Wsign-compare -c -o 
src/lib/upnp/ixmlwrap.o src/lib/upnp/ixmlwrap.cxx
| src/lib/upnp/ClientInit.cxx: In function 'void DoInit()':
| src/lib/upnp/ClientInit.cxx:52:31: error: invalid conversion from 'int 
(*)(Upnp_EventType, void*, void*) {aka int (*)(Upnp_EventType_e, void*, 
void*)}' to 'Upnp_FunPtr {aka int (*)(Upnp_EventType_e, const void*, void*)}' 
[-fpermissive]
| _client_handle);
|^
| In file included from src/lib/upnp/ClientInit.hxx:25:0,
|  from src/lib/upnp/ClientInit.cxx:21:
| /usr/include/upnp/upnp.h:989:17: note:   initializing argument 1 of 'int 
UpnpRegisterClient(Upnp_FunPtr, const void*, UpnpClient_Handle*)'
|  EXPORT_SPEC int UpnpRegisterClient(
|  ^~
| Makefile:14352: recipe for target 'src/lib/upnp/ClientInit.o' failed
| make[3]: *** [src/lib/upnp/ClientInit.o] Error 1
| make[3]: *** Waiting for unfinished jobs
| In file included from src/lib/upnp/Discovery.cxx:21:0:
| src/lib/upnp/Discovery.hxx:62:24: error: 'Upnp_Discovery' does not name a 
type; did you mean 'UpnpDiscovery'?
|DiscoveredTask(const Upnp_Discovery *disco)
| ^~
| UpnpDiscovery
| src/lib/upnp/Discovery.hxx:156:14: error: 'Upnp_Discovery' has not been 
declared
|   int OnAlive(Upnp_Discovery *disco);
|   ^~
| src/lib/upnp/Discovery.hxx:157:15: error: 'Upnp_Discovery' has not been 
declared
|   int OnByeBye(Upnp_Discovery *disco);
|^~
| src/lib/upnp/Discovery.hxx: In constructor 
'UPnPDeviceDirectory::DiscoveredTask::DiscoveredTask(const int*)':
| src/lib/upnp/Discovery.hxx:63:16: error: request for member 'Location' in '* 
disco', which is of non-class type 'const int'
| :url(disco->Location),
| ^~~~
| src/lib/upnp/Discovery.hxx:64:22: error: request for member 'DeviceId' in '* 
disco', which is of non-class type 'const int'
|  device_id(disco->DeviceId),
|   ^~~~
| src/lib/upnp/Discovery.hxx:65:41: error: request for member 'Expires' in '* 
disco', which is of non-class type 'const int'
|  expires(std::chrono::seconds(disco->Expires)) {}
|  ^~~
| src/lib/upnp/Discovery.cxx: At global scope:
| src/lib/upnp/Discovery.cxx:156:30: warning: inline variables are only 
available with -std=c++1z or -std=gnu++1z
|  UPnPDeviceDirectory::OnAlive(Upnp_Discovery *disco)
|   ^~
| src/lib/upnp/Discovery.cxx:156:30: error: 'int UPnPDeviceDirectory::OnAlive' 
is not a static data member of 'class UPnPDeviceDirectory'
| src/lib/upnp/Discovery.cxx:156:30: error: 'Upnp_Discovery' was not declared 
in this scope
| src/lib/upnp/Discovery.cxx:156:30: note: suggested alternative: 
'UpnpDiscovery'
|  UPnPDeviceDirectory::OnAlive(Upnp_Discovery *disco)
|   ^~
|   UpnpDiscovery
| src/lib/upnp/Discovery.cxx:156:46: error: 'disco' was not declared in this 
scope
|  UPnPDeviceDirectory::OnAlive(Upnp_Discovery *disco)
|   ^
| src/lib/upnp/Discovery.cxx:169:31: warning: inline variables are only 
available with -std=c++1z or -std=gnu++1z
|  UPnPDeviceDirectory::OnByeBye(Upnp_Discovery *disco)
|^~
| src/lib/upnp/Discovery.cxx:169:31: error: 'int UPnPDeviceDirectory::OnByeBye' 
is not a static data member of 'class UPnPDeviceDirectory'
| src/lib/upnp/Discovery.cxx:169:31: error: 'Upnp_Discovery' was not declared 
in this scope
| src/lib/upnp/Discovery.cxx:169:31: note: suggested alternative: 
'UpnpDiscovery'
|  UPnPDeviceDirectory::OnByeBye(Upnp_Discovery *disco)
|^~
|UpnpDiscovery
| src/lib/upnp/Discovery.cxx:169:47: error: 'disco' was not declared in this 
scope
|  UPnPDeviceDirectory::OnByeBye(Upnp_Discovery *disco)
|^
| src/lib/upnp/Discovery.cxx: In member function 'virtual int 
UPnPDeviceDirectory::Invoke(Upnp_EventType, void*)':
| src/lib/upnp/Discovery.cxx:191:4: error: 'Upnp_Discovery' was not declared in 
this scope
| Upnp_Discovery *disco = (Upnp_Discovery *)evp;
| ^~
| src/lib/upnp/Discovery.cxx:191:4: 

Bug#884247: linphoone: FTBFS against upnp 1.8

2017-12-12 Thread Sebastian Ramacher
Source: linphone
Version: 3.6.1-3
Severity: important
Tags: sid buster

linphone FTBFS against upnp 1.8 (available in experimental):
| libtool: compile:  gcc -DHAVE_CONFIG_H 
-DPACKAGE_PLUGINS_DIR=\"/usr/lib/x86_64-linux-gnu/mediastreamer/plugins\" 
-DLOCALEDIR=\"/usr/share/locale\" -DMS2_INTERNAL -DMS2_FILTERS -I. -I.. 
-I../include/ -I../src/base -I../src/utils -I../src/voip -I../src/audiofilters 
-I../src/otherfilters -I../src/videofilters -Wdate-time -D_FORTIFY_SOURCE=2 
-I../../oRTP/include -D_REENTRANT -I/usr/include/x86_64-linux-gnu 
-DVIDEO_ENABLED -DHAVE_GL -DHAVE_XV -I/usr/include/libdrm -pthread 
-I/usr/include/upnp -D_GNU_SOURCE -DORTP_INET6 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DINET6 -Wall -fdiagnostics-show-option -pthread 
-D_REENTRANT -c upnp/upnp_igd_utils.c  -fPIC -DPIC -o 
upnp/.libs/upnp_igd_utils.o
| upnp/upnp_igd.c:398:86: warning: 'struct Upnp_Discovery' declared inside 
parameter list will not be visible outside of this definition or declaration
|  void upnp_igd_add_device(upnp_igd_context *igd_ctxt, IXML_Document 
*desc_doc, struct Upnp_Discovery *d_event) {
|   
^~
| upnp/upnp_igd.c: In function 'upnp_igd_add_device':
| upnp/upnp_igd.c:422:51: error: dereferencing pointer to incomplete type 
'struct Upnp_Discovery'
|   ret = UpnpResolveURL((baseURL ? baseURL : d_event->Location), relURL, 
presURL);
|^~
| upnp/upnp_igd.c:514:112: warning: passing argument 8 of 
'upnp_igd_send_action' from incompatible pointer type 
[-Wincompatible-pointer-types]
|  upnp_igd_send_action(igd_ctxt, deviceNode, IGD_SERVICE_WANIPCONNECTION, 
"GetNATRSIPStatus", NULL, NULL, 0, upnp_igd_callback, igd_ctxt);
|   
  ^
| upnp/upnp_igd.c:354:5: note: expected 'Upnp_FunPtr {aka int (*)(enum 
Upnp_EventType_e,  const void *, void *)}' but argument is of type 'int 
(*)(Upnp_EventType,  void *, void *) {aka int (*)(enum Upnp_EventType_e,  void 
*, void *)}'
|  int upnp_igd_send_action(upnp_igd_context* igd_ctxt, upnp_igd_device_node 
*device_node, int service,
|  ^~~~
| upnp/upnp_igd.c:517:109: warning: passing argument 8 of 
'upnp_igd_send_action' from incompatible pointer type 
[-Wincompatible-pointer-types]
|  upnp_igd_send_action(igd_ctxt, deviceNode, IGD_SERVICE_WANIPCONNECTION, 
"GetStatusInfo", NULL, NULL, 0, upnp_igd_callback, igd_ctxt);
|   
   ^
| upnp/upnp_igd.c:354:5: note: expected 'Upnp_FunPtr {aka int (*)(enum 
Upnp_EventType_e,  const void *, void *)}' but argument is of type 'int 
(*)(Upnp_EventType,  void *, void *) {aka int (*)(enum Upnp_EventType_e,  void 
*, void *)}'
|  int upnp_igd_send_action(upnp_igd_context* igd_ctxt, upnp_igd_device_node 
*device_node, int service,
|  ^~~~
| upnp/upnp_igd.c:518:116: warning: passing argument 8 of 
'upnp_igd_send_action' from incompatible pointer type 
[-Wincompatible-pointer-types]
|  upnp_igd_send_action(igd_ctxt, deviceNode, IGD_SERVICE_WANIPCONNECTION, 
"GetExternalIPAddress", NULL, NULL, 0, upnp_igd_callback, igd_ctxt);
|   
  ^
| upnp/upnp_igd.c:354:5: note: expected 'Upnp_FunPtr {aka int (*)(enum 
Upnp_EventType_e,  const void *, void *)}' but argument is of type 'int 
(*)(Upnp_EventType,  void *, void *) {aka int (*)(enum Upnp_EventType_e,  void 
*, void *)}'
|  int upnp_igd_send_action(upnp_igd_context* igd_ctxt, upnp_igd_device_node 
*device_node, int service,
|  ^~~~
| upnp/upnp_igd.c: In function 'upnp_igd_callback':
| upnp/upnp_igd.c:888:18: error: dereferencing pointer to incomplete type 
'struct Upnp_Discovery'
|if (d_event->ErrCode != UPNP_E_SUCCESS) {
|   ^~
| upnp/upnp_igd.c:895:48: warning: passing argument 3 of 'upnp_igd_add_device' 
from incompatible pointer type [-Wincompatible-pointer-types]
| upnp_igd_add_device(igd_ctxt, desc_doc, d_event);
| ^~~
| upnp/upnp_igd.c:398:6: note: expected 'struct Upnp_Discovery *' but argument 
is of type 'struct Upnp_Discovery *'
|  void upnp_igd_add_device(upnp_igd_context *igd_ctxt, IXML_Document 
*desc_doc, struct Upnp_Discovery *d_event) {
|   ^~~
| upnp/upnp_igd.c:904:18: error: dereferencing pointer to incomplete type 
'struct Upnp_Discovery'
|if (d_event->ErrCode != UPNP_E_SUCCESS) {
|   ^~
| upnp/upnp_igd.c:914:18: error: dereferencing pointer to incomplete type 
'struct Upnp_Action_Complete'
|if (a_event->ErrCode != 

Bug#884245: gmediaserver: FTBFS against upnp 1.8

2017-12-12 Thread Sebastian Ramacher
Source: gmediaserver
Version: 0.13.0-8
Severity: important
Tags: sid buster

gmediaserver FTBFS against upnp 1.8 (available in experimental):
| gcc -DHAVE_CONFIG_H -I. -I. -I..  -I../lib -I../lib   -Wall 
-I/usr/include/uuid -pthread -I/usr/include/upnp -I/usr/include/taglib -g -O2 
-c upnp.c
| upnp.c:210:36: warning: 'struct Upnp_Subscription_Request' declared inside 
parameter list will not be visible outside of this definition or declaration
|  handle_subscription_request(struct Upnp_Subscription_Request *request)
| ^
| upnp.c: In function 'handle_subscription_request':
| upnp.c:218:57: error: dereferencing pointer to incomplete type 'struct 
Upnp_Subscription_Request'
|  say(3, _("Event device UDN: %s\n"), quotearg(request->UDN));
|  ^~
| upnp.c: At top level:
| upnp.c:261:31: warning: 'struct Upnp_State_Var_Request' declared inside 
parameter list will not be visible outside of this definition or declaration
|  handle_get_var_request(struct Upnp_State_Var_Request *request)
|^~
| upnp.c: In function 'handle_get_var_request':
| upnp.c:269:52: error: dereferencing pointer to incomplete type 'struct 
Upnp_State_Var_Request'
|  error = getnameinfo((struct sockaddr *)>CtrlPtIPAddr, 
sizeof(request->CtrlPtIPAddr),
| ^~
| upnp.c: In function 'handle_action_request':
| upnp.c:317:52: error: dereferencing pointer to incomplete type 'struct 
Upnp_Action_Request'
|  error = getnameinfo((struct sockaddr *)>CtrlPtIPAddr, 
sizeof(request->CtrlPtIPAddr),
| ^~
| upnp.c: In function 'device_callback_event_handler':
| upnp.c:369:37: warning: passing argument 1 of 'handle_subscription_request' 
from incompatible pointer type [-Wincompatible-pointer-types]
|  handle_subscription_request((struct Upnp_Subscription_Request *) 
event);
|  ^
| upnp.c:210:1: note: expected 'struct Upnp_Subscription_Request *' but 
argument is of type 'struct Upnp_Subscription_Request *'
|  handle_subscription_request(struct Upnp_Subscription_Request *request)
|  ^~~
| upnp.c:372:32: warning: passing argument 1 of 'handle_get_var_request' from 
incompatible pointer type [-Wincompatible-pointer-types]
|  handle_get_var_request((struct Upnp_State_Var_Request *) event);
| ^
| upnp.c:261:1: note: expected 'struct Upnp_State_Var_Request *' but argument 
is of type 'struct Upnp_State_Var_Request *'
|  handle_get_var_request(struct Upnp_State_Var_Request *request)
|  ^~
| upnp.c: In function 'init_upnp':
| upnp.c:521:11: warning: implicit declaration of function 
'UpnpSetVirtualDirCallbacks'; did you mean 'UpnpAddVirtualDir'? 
[-Wimplicit-function-declaration]
|  res = UpnpSetVirtualDirCallbacks(_dir_callbacks);
|^~
|UpnpAddVirtualDir
| upnp.c:524:11: error: too few arguments to function 'UpnpAddVirtualDir'
|  res = UpnpAddVirtualDir("/files");
|^
| In file included from upnp.c:23:0:
| /usr/include/upnp/upnp.h:2741:17: note: declared here
|  EXPORT_SPEC int UpnpAddVirtualDir(
|  ^
| upnp.c:527:11: error: too few arguments to function 'UpnpAddVirtualDir'
|  res = UpnpAddVirtualDir("/upnp");
|^
| In file included from upnp.c:23:0:
| /usr/include/upnp/upnp.h:2741:17: note: declared here
|  EXPORT_SPEC int UpnpAddVirtualDir(
|  ^
| upnp.c:544:44: warning: passing argument 5 of 'UpnpRegisterRootDevice2' from 
incompatible pointer type [-Wincompatible-pointer-types]
|strlen(mediaserver_desc), 1, device_callback_event_handler, 
NULL, );
| ^
| In file included from upnp.c:23:0:
| /usr/include/upnp/upnp.h:800:17: note: expected 'Upnp_FunPtr {aka int 
(*)(enum Upnp_EventType_e,  const void *, void *)}' but argument is of type 
'int (*)(Upnp_EventType,  void *, void *) {aka int (*)(enum Upnp_EventType_e,  
void *, void *)}'
|  EXPORT_SPEC int UpnpRegisterRootDevice2(
|  ^~~
| Makefile:598: recipe for target 'upnp.o' failed

Full log at
https://people.debian.org/~sramacher/logs/upnp/gmediaserver_amd64-2017-12-12T20:37:35Z.log

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature


Bug#884243: djmount: FTBFS against upnp 1.8

2017-12-12 Thread Sebastian Ramacher
Source: djmount
Version: 0.71-7.1
Severity: important
Tags: sid buster

djmount FTBFS against upnp 1.8 available in experimental:
| gcc -DHAVE_CONFIG_H -I. -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -I../gl  
-pthread -I/usr/include/upnp  -D_FILE_OFFSET_BITS=64 -I/usr/include/fuse 
-DFUSE_USE_VERSION=22  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -pthread -c 
device_list.c
| device_list.c:42:10: fatal error: upnp/LinkedList.h: No such file or directory
|  #include 
|   ^~~
| compilation terminated.
| Makefile:540: recipe for target 'device_list.o' failed
| make[4]: *** [device_list.o] Error 1

A full log is available at
https://people.debian.org/~sramacher/logs/upnp/djmount_amd64-2017-12-12T20:36:53Z.log.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature


Bug#884246: gmrender-resurrect: FTBFS against upnp 1.8

2017-12-12 Thread Sebastian Ramacher
Source: gmrender-resurrect
Version: 0.0.7~git20170910+repack-1
Severity: important
Tags: sid buster

gmrender-resurrect FTBFS against upnp 1.8 (available in experimental):
| gcc -DHAVE_CONFIG_H -I. -I..  -pthread -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
-I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/upnp 
-DPKG_DATADIR=\"/usr/share/gmediarender\" -Wdate-time -D_FORTIFY_SOURCE=2  -g 
-O2 
-fdebug-prefix-map=/<>/gmrender-resurrect-0.0.7~git20170910+repack=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -Wpointer-arith 
-Wmissing-prototypes -Wmissing-declarations -Wwrite-strings -c -o logging.o 
logging.c
| upnp_device.c: In function 'upnp_add_response':
| upnp_device.c:75:46: error: dereferencing pointer to incomplete type 'struct 
Upnp_Action_Request'
|   rc = UpnpAddToActionResponse(>request->ActionResult,
|   ^~
| upnp_device.c: At top level:
| upnp_device.c:156:47: warning: 'struct Upnp_Subscription_Request' declared 
inside parameter list will not be visible outside of this definition or 
declaration
| struct Upnp_Subscription_Request
|^
| upnp_device.c: In function 'handle_subscription_request':
| upnp_device.c:165:12: error: dereferencing pointer to incomplete type 'struct 
Upnp_Subscription_Request'
| sr_event->ServiceId, sr_event->UDN);
| ^~
| upnp_device.c: At top level:
| upnp_device.c:243:17: warning: 'struct Upnp_State_Var_Request' declared 
inside parameter list will not be visible outside of this definition or 
declaration
|   struct Upnp_State_Var_Request *var_event) {
|  ^~
| upnp_device.c: In function 'handle_var_request':
| upnp_device.c:245:18: error: dereferencing pointer to incomplete type 'struct 
Upnp_State_Var_Request'
|  var_event->ServiceID);
|   ^~
| upnp_device.c: In function 'initialize_device':
| upnp_device.c:433:7: error: too few arguments to function 'UpnpAddVirtualDir'
|   rc = UpnpAddVirtualDir("/upnp");
|^
| In file included from upnp_device.c:41:0:
| /usr/include/upnp/upnp.h:2741:17: note: declared here
|  EXPORT_SPEC int UpnpAddVirtualDir(
|  ^
| upnp_device.c:443:10: warning: passing argument 5 of 
'UpnpRegisterRootDevice2' from incompatible pointer type 
[-Wincompatible-pointer-types]
|   _handler, result_device,
|   ^
| In file included from upnp_device.c:41:0:
| /usr/include/upnp/upnp.h:800:17: note: expected 'Upnp_FunPtr {aka int 
(*)(enum Upnp_EventType_e,  const void *, void *)}' but argument is of type 
'int (*)(Upnp_EventType,  void *, void *) {aka int (*)(enum Upnp_EventType_e,  
void *, void *)}'
|  EXPORT_SPEC int UpnpRegisterRootDevice2(
|  ^~~
| Makefile:396: recipe for target 'upnp_device.o' failed
| make[3]: *** [upnp_device.o] Error 1
| make[3]: *** Waiting for unfinished jobs
| webserver.c:145:60: warning: 'struct File_Info' declared inside parameter 
list will not be visible outside of this definition or declaration
|  static int webserver_get_info(const char *filename, struct File_Info *info)
| ^
| webserver.c: In function 'webserver_get_info':
| webserver.c:151:8: error: dereferencing pointer to incomplete type 'struct 
File_Info'
| info->file_length = virtfile->len;
| ^~
| webserver.c: In function 'webserver_register_callbacks':
| webserver.c:292:41: warning: passing argument 1 of 
'UpnpVirtualDir_set_GetInfoCallback' from incompatible pointer type 
[-Wincompatible-pointer-types]
|  (UpnpVirtualDir_set_GetInfoCallback(webserver_get_info) == UPNP_E_SUCCESS
|  ^~
| In file included from webserver.c:38:0:
| /usr/include/upnp/upnp.h:2590:17: note: expected 'VDCallback_GetInfo {aka int 
(*)(const char *, struct s_UpnpFileInfo *, const void *)}' but argument is of 
type 'int (*)(const char *, struct File_Info *)'
|  EXPORT_SPEC int UpnpVirtualDir_set_GetInfoCallback(VDCallback_GetInfo 
callback);
|  ^~
| webserver.c:293:41: warning: passing argument 1 of 
'UpnpVirtualDir_set_OpenCallback' from incompatible pointer type 
[-Wincompatible-pointer-types]
|   && UpnpVirtualDir_set_OpenCallback(webserver_open) == UPNP_E_SUCCESS
|  ^~
| In file included from webserver.c:38:0:
| /usr/include/upnp/upnp.h:2612:17: note: expected 'VDCallback_Open {aka void * 
(*)(const char *, enum UpnpOpenFileMode,  const void *)}' but argument is of 
type 'void * (*)(const char *, enum UpnpOpenFileMode)'
|  EXPORT_SPEC int 

Bug#884244: dsh: option -N does not work

2017-12-12 Thread Slaven Rezic
Package: dsh
Version: 0.25.10-1.3
Severity: minor

Dear Maintainer,

the documented option -N does not work:

$ dsh -N 1 -m localhost hostname
dsh: invalid option -- 'N'

The equivalent long option --num-topology works.

Also, the manpage does not say that --num-topology & -N expects a number.
It should probably say something like:

   --num-topology | -N number

Regards,
Slaven

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

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

Versions of packages dsh depends on:
ii  libc6  2.24-11+deb9u1
ii  libdshconfig1  0.20.13-1.2

dsh recommends no packages.

Versions of packages dsh suggests:
pn  update-cluster  

-- no debconf information



Bug#884241: bouncycastle: CVE-2017-13098

2017-12-12 Thread Salvatore Bonaccorso
Source: bouncycastle
Version: 1.57-1
Severity: grave
Tags: patch security upstream

Hi,

the following vulnerability was published for bouncycastle.

CVE-2017-13098[0]:
| Information leak by distinguish valid and invalid RSA PKCS #1 v1.5
| paddings based on different server responses.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-13098
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-13098
[1] 
https://github.com/bcgit/bc-java/commit/a00b684465b38d722ca9a3543b8af8568e6bad5c
[2] https://downloads.bouncycastle.org/betas/
[3] https://www.kb.cert.org/vuls/id/144389

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore



Bug#884242: gdb-mingw-w64 FTBFS with g++-mingw-w64 7.2.0-16+20

2017-12-12 Thread Adrian Bunk
Source: gdb-mingw-w64
Version: 10.4
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gdb-mingw-w64.html

...
i686-w64-mingw32-g++ -g -O2 -specs=/usr/share/dpkg/no-pie-compile.specs 
-Wformat -Werror=format-security-I. 
-I/build/1st/gdb-mingw-w64-10.4/upstream/gdb/gdbserver 
-I/build/1st/gdb-mingw-w64-10.4/upstream/gdb/gdbserver/../common 
-I/build/1st/gdb-mingw-w64-10.4/upstream/gdb/gdbserver/../regformats 
-I/build/1st/gdb-mingw-w64-10.4/upstream/gdb/gdbserver/.. 
-I/build/1st/gdb-mingw-w64-10.4/upstream/gdb/gdbserver/../../include 
-I/build/1st/gdb-mingw-w64-10.4/upstream/gdb/gdbserver/../gnulib/import 
-Ibuild-gnulib-gdbserver/import -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
-Wpointer-arith -Wno-unused -Wunused-value -Wunused-function -Wno-switch 
-Wno-char-subscripts -Wempty-body -Wunused-but-set-parameter 
-Wunused-but-set-variable -Wno-sign-compare -Wno-write-strings -Wno-narrowing 
-Wno-format  -DGDBSERVER -c -o agent.o -MT agent.o -MMD -MP -MF .deps/agent.Tpo 
/build/1st/gdb-mingw-w64-10.4/upstream/gdb/gdbserver/../common/agent.c
i686-w64-mingw32-g++ -g -O2 -specs=/usr/share/dpkg/no-pie-compile.specs 
-Wformat -Werror=format-security-I. 
-I/build/1st/gdb-mingw-w64-10.4/upstream/gdb/gdbserver 
-I/build/1st/gdb-mingw-w64-10.4/upstream/gdb/gdbserver/../common 
-I/build/1st/gdb-mingw-w64-10.4/upstream/gdb/gdbserver/../regformats 
-I/build/1st/gdb-mingw-w64-10.4/upstream/gdb/gdbserver/.. 
-I/build/1st/gdb-mingw-w64-10.4/upstream/gdb/gdbserver/../../include 
-I/build/1st/gdb-mingw-w64-10.4/upstream/gdb/gdbserver/../gnulib/import 
-Ibuild-gnulib-gdbserver/import -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
-Wpointer-arith -Wno-unused -Wunused-value -Wunused-function -Wno-switch 
-Wno-char-subscripts -Wempty-body -Wunused-but-set-parameter 
-Wunused-but-set-variable -Wno-sign-compare -Wno-write-strings -Wno-narrowing 
-Wno-format  -DGDBSERVER -c -o ax.o -MT ax.o -MMD -MP -MF .deps/ax.Tpo `echo " 
-Wall -Wpointer-arith -Wno-unused -Wunused-value -Wunused-function -Wno-switch 
-Wno-char-subscripts -Wempty-body -Wunused-but-set-paramet
 er -Wunused-but-set-variable -Wno-sign-compare -Wno-write-strings 
-Wno-narrowing -Wno-format " | sed "s/ -Wformat-nonliteral / 
-Wno-format-nonliteral /g"` 
/build/1st/gdb-mingw-w64-10.4/upstream/gdb/gdbserver/ax.c
i686-w64-mingw32-g++ -g -O2 -specs=/usr/share/dpkg/no-pie-compile.specs 
-Wformat -Werror=format-security-I. 
-I/build/1st/gdb-mingw-w64-10.4/upstream/gdb/gdbserver 
-I/build/1st/gdb-mingw-w64-10.4/upstream/gdb/gdbserver/../common 
-I/build/1st/gdb-mingw-w64-10.4/upstream/gdb/gdbserver/../regformats 
-I/build/1st/gdb-mingw-w64-10.4/upstream/gdb/gdbserver/.. 
-I/build/1st/gdb-mingw-w64-10.4/upstream/gdb/gdbserver/../../include 
-I/build/1st/gdb-mingw-w64-10.4/upstream/gdb/gdbserver/../gnulib/import 
-Ibuild-gnulib-gdbserver/import -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
-Wpointer-arith -Wno-unused -Wunused-value -Wunused-function -Wno-switch 
-Wno-char-subscripts -Wempty-body -Wunused-but-set-parameter 
-Wunused-but-set-variable -Wno-sign-compare -Wno-write-strings -Wno-narrowing 
-Wno-format  -DGDBSERVER -c -o inferiors.o -MT inferiors.o -MMD -MP -MF 
.deps/inferiors.Tpo 
/build/1st/gdb-mingw-w64-10.4/upstream/gdb/gdbserver/inferiors.c
i686-w64-mingw32-g++ -g -O2 -specs=/usr/share/dpkg/no-pie-compile.specs 
-Wformat -Werror=format-security-I. 
-I/build/1st/gdb-mingw-w64-10.4/upstream/gdb/gdbserver 
-I/build/1st/gdb-mingw-w64-10.4/upstream/gdb/gdbserver/../common 
-I/build/1st/gdb-mingw-w64-10.4/upstream/gdb/gdbserver/../regformats 
-I/build/1st/gdb-mingw-w64-10.4/upstream/gdb/gdbserver/.. 
-I/build/1st/gdb-mingw-w64-10.4/upstream/gdb/gdbserver/../../include 
-I/build/1st/gdb-mingw-w64-10.4/upstream/gdb/gdbserver/../gnulib/import 
-Ibuild-gnulib-gdbserver/import -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
-Wpointer-arith -Wno-unused -Wunused-value -Wunused-function -Wno-switch 
-Wno-char-subscripts -Wempty-body -Wunused-but-set-parameter 
-Wunused-but-set-variable -Wno-sign-compare -Wno-write-strings -Wno-narrowing 
-Wno-format  -DGDBSERVER -c -o regcache.o -MT regcache.o -MMD -MP -MF 
.deps/regcache.Tpo 
/build/1st/gdb-mingw-w64-10.4/upstream/gdb/gdbserver/regcache.c
i686-w64-mingw32-g++ -g -O2 -specs=/usr/share/dpkg/no-pie-compile.specs 
-Wformat -Werror=format-security-I. 
-I/build/1st/gdb-mingw-w64-10.4/upstream/gdb/gdbserver 
-I/build/1st/gdb-mingw-w64-10.4/upstream/gdb/gdbserver/../common 
-I/build/1st/gdb-mingw-w64-10.4/upstream/gdb/gdbserver/../regformats 
-I/build/1st/gdb-mingw-w64-10.4/upstream/gdb/gdbserver/.. 
-I/build/1st/gdb-mingw-w64-10.4/upstream/gdb/gdbserver/../../include 
-I/build/1st/gdb-mingw-w64-10.4/upstream/gdb/gdbserver/../gnulib/import 
-Ibuild-gnulib-gdbserver/import -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
-Wpointer-arith -Wno-unused -Wunused-value -Wunused-function -Wno-switch 
-Wno-char-subscripts -Wempty-body -Wunused-but-set-parameter 
-Wunused-but-set-variable 

Bug#884240: ipxe-qemu: e1000e rom is missing

2017-12-12 Thread Nathan Rennie-Waldock
Package: ipxe-qemu
Version: 1.0.0+git-20161027.b991c67-1
Severity: important

qemu 2.7 and higher support e1000e with PXE boot, but the rom is missing:
vagrant@stretch:~$ qemu-system-x86_64 -netdev user,id=hostnet0 -device 
e1000e,netdev=hostnet0,id=net0 -nographic
qemu-system-x86_64: -device e1000e,netdev=hostnet0,id=net0: failed to find 
romfile "efi-e1000e.rom"

Please include this rom.


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

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



Bug#586858: [Pkg-utopia-maintainers] Bug#586858: network-manager: Should auto-detect EAP authentication type

2017-12-12 Thread Michael Biebl
Hi Josh

Am 12.12.2017 um 20:31 schrieb Josh Triplett:
>> Can you still reproduce the issue with a recent version?
> 
> Yes, this is still relevant. NetworkManager still requires manually
> selecting the EAP type, rather than autodetecting it. I don't know why
> this would have been closed as obsolete.

Thanks for reporting back and confirming this is still an issue.
As I don't have an environment to test EAP setups myself, would you mind
following up at the upstream bug report yourself?
This is probably more productive then me playing a bug proxy.

Regards,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Bug#884191: Please do not disable AppArmor silently and prevent its re-activation

2017-12-12 Thread Carsten Schoenert
Hello Cédric,

I lowered down the severity to wishlist, please see
https://www.debian.org/Bugs/Developer#severities

On Tue, Dec 12, 2017 at 03:49:23PM +0100, Cédric Dufour - Idiap Research 
Institute wrote:
> Package: thunderbird
> Version: 1:52.5.0-1~deb8u1
> severity: grave
> 
> As stated as comment to the bug corresponding to the source of this
> issue (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882672):
> 
> > I think we can implement this change by shipping a symlink to the
> > profile in /etc/apparmor.d/disable/. My understanding is that dpkg
> > will treat this removal of a conffile as a change worth preserving on
> > upgrades, i.e. it won't install the symlink again if it's
> > been deleted.
> 
> I deleted the symlink and 'apt-get reinstall thunderbird' and the
> symlink is back, thus preventing re-activation of Thunderbird AppArmor
> profile.

No need for a reinstallation the package, just remove the symlink and
let AppArmor parse the available profiles.

  $ sudo rm /etc/apparmor.d/disable/profile.name
  $ sudo apparmor_parser -r /etc/apparmor.d/profile.name

> Worse, this change affects even Jessie/OldStable, where AppArmor is
> silently disabled without sysadmin knowledge (I stumbled on this by
> mere chance).

We do not make changes between releases normaly, only for things that are
really release depended like the GCC version.

> This is very unfortunate, knowing my company relies on a carefully
> tuned - and working! - AppArmor profile for Thunderbird, as an
> important piece of its overall security setup.
> And we're very happy with it preventing who-knows-which binary to open
> who-knows-what-malware-ridden attachements! No longer now...

Well, AppArmor wasn't included in the Stretch release as a release goal
nor was it widely tested. And now it's has shown that the problems around
the AppArmor profile has growing over and over so we decided to not
bother people by things that are not working really well in recent
AppArmor profiles for Thunderbird. The profile for LibreOffice is
disabled since the beginning of the AppArmor in Debian.

So no, we can't say we have had a god solution around AppArmor and
Thunderbird. It's fine if the existing profile is working good enough on
your side but the reality on most other user installation is showing
some more problems.

> I don't understand all the fuss about users complaining about AppArmor
> profiles not working. AppArmor is about *mandatory* access control,
> iow. explicitly specifying what actions are allowed. You can not
> expect to use AppArmor for what is intended for and ask for it to be
> OK with all possible use cases (in this latter case, you'd better not
> use AppArmor to start with, since it ends up to be nothing but
> security theater). 

Well, user expect usability and not to be treated in every corner by a
system administrator by curtailing access to some resources. Take a look
at recent created bug reports about mostly simple things that do not
work with the current AppArmor profiles.

> As a solution to the issue at hand, I would suggest:
>  - use debconf to prompt the user for AppArmor enable/disable

The debconf mechanism is great for configuring basic *system* stuff but
a golden rule is to not bother "normal" users with questions he can't
really answer because they are simple users. So no, there will probably
never a be a debconf setting here.

>  - default to enable, since it is what makes sense if the apparmor
>package is installed and kernel-enabled (security=apparmor)

That's the plan for the buster release, right now the current profile
isn't robust enough for most of the use cases. The profile needs to be
improved, there are no doubt about that.

>  - do the /etc/apparmor.d/disable symlink magic in postinst, based on
>the debconf choice

That would require the existence if a debconf setup, that will not
happen as written above.

> I hope this can be corrected back to Jessie, since this is serious
> security issue for those who enabled AppArmor knowingly.

We wont change this behavior in the near future.
 
> PS: I marked the severity as "grave" since it does "introduces a
> security hole allowing access to the accounts of users who use the
> package" for those who did rely on AppArmor to control Thunderbird
> bevahior along attachements.

No, the disabling of the AppArmor profile isn't introducing a security
hole right now. Especially as the user or the administrator can easily
turn it on again. Thunderbird isn't that insecure as before without
AppArmor support.

So feel free to re-enable AppArmor on your side, doing this by some
automatic system like ansible, chef, puppet or $whatever makes this
easy. If you can help to improve the existing profile then please do so.

Regards
Carsten



Bug#884239: build-depends on python-django-allauth (not yet in debian)

2017-12-12 Thread Daniel Baumann
Package: django-mailman3
Version: 1.1.0-1
Severity: serious

Hi,

thanks a lot for bringing mailman3 to debian.

unfortunatly, there seems to be at least python-django-allauth (not in
debian or NEW yet) missing as specified in django-mailman3 build-depends.

Regards,
Daniel



Bug#869692: RFS: cyclograph/1.9.1-1

2017-12-12 Thread Jeremy Bicha
wRAR, because I filed the bug (866635) that ended up pushing
cyclograph out of Testing months ago, I feel some responsibility to
help it get back into Testing.

Is there anything else that you are waiting on in order to sponsor cyclograph?

For reference, the repo is at
https://anonscm.debian.org/git/pkg-running/cyclograph.git

Thanks,
Jeremy Bicha



Bug#883950: debian-policy: allow specifying common licenses with only the identifier

2017-12-12 Thread Markus Koschany
Hi,

thanks for reporting. I also intended to make such a proposal and I had
briefly mentioned it in bug #883966. [1]

The reason why the short form is allowed is because of Debian Policy 12.5

"Packages distributed under the Apache license (version 2.0), the
Artistic license, the GNU GPL (versions 1, 2, or 3), the GNU LGPL
(versions 2, 2.1, or 3), the GNU FDL (versions 1.2 or 1.3), and the
Mozilla Public License (version 1.1 or 2.0) should refer to the
corresponding files under /usr/share/common-licenses, [9] rather than
quoting them in the copyright file."

I agree that using boiler plate like this:

| License: GPL-2+
| On Debian systems the full text of the GPL-2 can be found in
| /usr/share/common-licenses/GPL-2

is still redundant.

I suggest to change Debian Policy 12.5 and copyright format 1.0 in such
a way that the following syntax is allowed:

License: [GPL-2+]

This would imply the license is identical to the one we ship under
/usr/share/common-licenses/. Services like sources.debian.org could
easily parse this field and automatically link to the full license-text.

I don't have a fixation about using brackets. We could also use
something else. In the above case Lintian should not warn about a
missing standalone license or license text in general.

Regards,

Markus

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883966#25



signature.asc
Description: OpenPGP digital signature


Bug#884236: fis-gtm FTBFS with linux-libc-dev 4.14.2-1

2017-12-12 Thread Adrian Bunk
Source: fis-gtm
Version: 6.3-002-3
Severity: serious

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

...
/usr/bin/cc -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -D_LARGEFILE64_SOURCE 
-D_XOPEN_SOURCE=600 -I/build/1st/fis-gtm-6.3-002/obj-x86_64-linux-gnu/gen 
-I/build/1st/fis-gtm-6.3-002/sr_linux -I/build/1st/fis-gtm-6.3-002/sr_x86_64 
-I/build/1st/fis-gtm-6.3-002/sr_x86_regs 
-I/build/1st/fis-gtm-6.3-002/sr_unix_gnp 
-I/build/1st/fis-gtm-6.3-002/sr_unix_cm -I/build/1st/fis-gtm-6.3-002/sr_unix 
-I/build/1st/fis-gtm-6.3-002/sr_port_cm -I/build/1st/fis-gtm-6.3-002/sr_port 
-I/build/1st/fis-gtm-6.3-002/obj-x86_64-linux-gnu -I/usr/local/include 
-I/usr/local/ssl/include  -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -ansi -fPIC  
-fsigned-char -Wmissing-prototypes -Wreturn-type -Wpointer-sign 
-fno-omit-frame-pointer -O2 -DNDEBUG   -o 
CMakeFiles/gtm_threadgbl_deftypes.dir/sr_port/gtm_threadgbl_deftypes.c.o   -c 
/build/1st/fis-gtm-6.3-002/sr_port/gtm_threadgbl_deftypes.c
In file included from /build/1st/fis-gtm-6.3-002/sr_port/gdsfhead.h:29:0,
 from 
/build/1st/fis-gtm-6.3-002/sr_port/gtm_threadgbl_deftypes.c:43:
/build/1st/fis-gtm-6.3-002/sr_port/gtm_libaio.h:72:2: warning: parameter names 
(without types) in function declaration
  __u32 PADDED(aio_key, aio_reserved1);
  ^
/build/1st/fis-gtm-6.3-002/sr_port/gtm_libaio.h:72:8: error: field 'PADDED' 
declared as a function
  __u32 PADDED(aio_key, aio_reserved1);
^~
CMakeFiles/gtm_threadgbl_deftypes.dir/build.make:65: recipe for target 
'CMakeFiles/gtm_threadgbl_deftypes.dir/sr_port/gtm_threadgbl_deftypes.c.o' 
failed
make[3]: *** 
[CMakeFiles/gtm_threadgbl_deftypes.dir/sr_port/gtm_threadgbl_deftypes.c.o] 
Error 1


The PADDED define was removed from /usr/include/linux/aio_abi.h



Bug#884238: dsh: --forklimit off by one

2017-12-12 Thread Slaven Rezic
Package: dsh
Version: 0.25.10-1.3
Severity: minor

Dear Maintainer,

experiments (e.g. looking into a run with strace, using "-c --forklimit 1")
show that the number of forks is actually always one greater than specified.
E.g. with "--forklimit 1" there are two processes running at the same time.

Regards,
Slaven

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

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

Versions of packages dsh depends on:
ii  libc6  2.24-11+deb9u1
ii  libdshconfig1  0.20.13-1.2

dsh recommends no packages.

Versions of packages dsh suggests:
pn  update-cluster  

-- no debconf information



Bug#884115: Ioslides inside rmarkdown has no license

2017-12-12 Thread Yihui Xie
Hi Andreas,

I took over the maintenance of the rmarkdown package only recently, and I
was not the person who introduced ioslides to the rmarkdown package. That
said, it does seem that the ioslides library's license is missing and
unclear. I'm not its author, so I cannot add a license to it. I guess it
will be difficult to get in touch with its original authors.

I don't quite see the benefits of making a Debian package for rmarkdown. It
is an R package, and it is fairly easy to install from CRAN. Those who use
R should be able to install it without sudo apt-get, and those who do not
use R probably won't care about an R package. On the other hand, I guess a
Debian version of rmarkdown that does not have ioslides can be confusing.

Regards,
Yihui
--
https://yihui.name

On Tue, Dec 12, 2017 at 1:11 AM, Andreas Tille  wrote:

> Hi Yihui Xie,
>
> I'm considering packaging rmarkdown for Debian since several just
> packaged software would profit from it.  For Debian uploads I need to
> make sure that each file of the source is available and has a proper
> license.  When I inspected the code I stumbled upon ioslides.  This
> project has no license in itself (neither in the code copy inside
> rmarkdown) nor upstream[1].  Besides the missing license I also notice
> that it contains third party components consisting of compressed
> JavaScript which is considered by Debian as "binary code" since you can
> not really change it.
>
> Do you see some means to provide a proper license for all components
> of ioslides and specifically the source code of
>
>inst/rmd/ioslides/ioslides-13.5.1/js/polyfills/dataset.min.js
>inst/rmd/ioslides/ioslides-13.5.1/js/polyfills/history.min.js
>
> where I failed to find the origin?
>
> If not I might consider striping ioslides from the Debian package at
> all by disabling the ioslides_presentation function.  As far as I
> can see rmarkdown is quite featureful even without this.
>
> What do you think?
>
> Kind regards
>
>Andreas.
>
> [1] I checked
> https://code.google.com/p/io-2012-slides/  as well as
> https://github.com/pauldijou/ioslides
>
> --
> http://fam-tille.de
>


Bug#787519: git-buildpackage: Read config from XDG_CONFIG_HOME/debian/gbp.conf

2017-12-12 Thread Félix Sipma
Package: git-buildpackage
Version: 0.9.4
Followup-For: Bug #787519

Would you accept the patch if it used XDG_CONFIG_HOME/git-buildpackage/gbp.conf
instead?

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

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

Versions of packages git-buildpackage depends on:
ii  devscripts 2.17.11
ii  git1:2.15.1-1
ii  man-db 2.7.6.1-4
ii  python33.6.3-2
ii  python3-dateutil   2.6.1-1
ii  python3-pkg-resources  38.2.4-1

Versions of packages git-buildpackage recommends:
ii  pristine-tar  1.42
ii  python3-requests  2.18.1-1
ii  sbuild0.73.0-4

Versions of packages git-buildpackage suggests:
pn  python3-notify2  
ii  sudo 1.8.21p2-2
ii  unzip6.0-21

-- no debconf information


signature.asc
Description: PGP signature


Bug#884237: aubio: CVE-2017-17554

2017-12-12 Thread Salvatore Bonaccorso
Source: aubio
Version: 0.4.5-1
Severity: important
Tags: security upstream

Hi,

the following vulnerability was published for aubio.

CVE-2017-17554[0]:
| A NULL pointer dereference (DoS) Vulnerability was found in the
| function aubio_source_avcodec_readframe in io/source_avcodec.c of aubio
| 0.4.6, which may lead to DoS when playing a crafted audio file.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-17554
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17554

Please adjust the affected versions in the BTS as needed, only 0.4.5-1
has been verfied before filling this bug.

Regards,
Salvatore



Bug#864849: [patch] fix watch file

2017-12-12 Thread Laurent Bigonville
On Fri, 16 Jun 2017 08:56:06 +1000 Vincent McIntyre 
 wrote:


> thanks mate
>
>
> This patch makes uscan do something useful again.
>
> --- a/debian/watch
> +++ b/debian/watch
> @@ -1,2 +1,2 @@
> version=3
> 
-ftp://ftp.kernel.org/pub/linux/daemons/autofs/v5/autofs-(5[^-]*)\.(?:tar\.xz|txz|tar\.bz2|tbz2|tar\.gz|tgz)
> +https://git.kernel.org/pub/scm/linux/storage/autofs/autofs.git/refs/ 
.*tag/\?h=release_(\d)_(\d)_(\d)


Is it really necessary to look in git?

https://www.kernel.org/pub/linux/daemons/autofs/v5/ works well

-ftp://ftp.kernel.org/pub/linux/daemons/autofs/v5/autofs-(5[^-]*)\.(?:tar\.xz|txz|tar\.bz2|tbz2|tar\.gz|tgz)
+http://www.kernel.org/pub/linux/daemons/autofs/v5/autofs-(5[^-]*)\.(?:tar\.xz|txz|tar\.bz2|tbz2|tar\.gz|tgz)



Bug#884235: wolfssl: CVE-2017-13099

2017-12-12 Thread Salvatore Bonaccorso
Source: wolfssl
Version: 3.12.2+dfsg-1
Severity: grave
Tags: patch security upstream
Forwarded: https://github.com/wolfSSL/wolfssl/pull/1229

Hi,

the following vulnerability was published for wolfssl.

CVE-2017-13099[0]:
| ROBOT attack / Fix handling of static RSA padding failures.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-13099
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-13099
[1] https://github.com/wolfSSL/wolfssl/pull/1229

Regards,
Salvatore



Bug#884234: bareos: Stable update fails to configure (no database version defined, FAILED to set Catalog MyCatalog dbdriver = postgresql)

2017-12-12 Thread Anthony DeRobertis

Package: bareos
Version: 14.2.1+20141017gitc6c5b56-3+deb8u3
Severity: serious
Justification: Policy 10.7.3

I've been happily using the bareos packages on jessie for a bit now (thank
you for maintaining them!)

I attempted to upgrade bareos to 14.2.1+20141017gitc6c5b56-3+deb8u3
(from +deb8u2) this afternoon, and it failed to configure. Here is
trying to configure it again:

root@Bennu:~# dpkg --configure -a
Setting up bareos-database-common (14.2.1+20141017gitc6c5b56-3+deb8u3) ...
Warning: no database version defined for release 14.2.1+20141017gitc6c5b56 
(14.2.1+20141017gitc6c5b56-3+deb8u2). Using default version: 2003
(config) dbc_go() bareos-database-common configure 2003.
dbc_config() bareos-database-common configure 2003.
dbc_set_dbtype_defaults() .
dbc_register_debconf() .
dbc_read_package_config() .
dbc_preseed_package_debconf() .
dbc_detect_supported_dbtype() pgsql.
dbc_detect_installed_dbtype() pgsql.
_dbc_detect_installed_dbtype() pgsql.
dbc_config() bareos-database-common configure 2003.
dbc_set_dbtype_defaults() pgsql.
dbc_get_app_pass() .
Warning: no database version defined for release 14.2.1+20141017gitc6c5b56 
(14.2.1+20141017gitc6c5b56-3+deb8u2). Using default version: 2003
dbconfig-common: writing config to 
/etc/dbconfig-common/bareos-database-common.conf
dbconfig-common: flushing administrative password
FAILED to set Catalog MyCatalog dbdriver = postgresql 
(/etc/bareos/bareos-dir.conf)

... which would make sense because I don't have a catalog called
MyCatalog, except reading /usr/lib/bareos/scripts/bareos-config-lib.sh
it turns out its actually nowhere near that robust; it's just looking
for "dbdriver = ..." and failing to find it. That's broken for at least
three reasons:

   1) The documented parameter name is "DB Driver"; see
  
http://doc.bareos.org/master/html/bareos-manual-main-reference.html#directiveDirCatalogDB%20Driver
  and bareos of course doesn't care about capitalization or spacing
  (which is why dbdriver also works).

   2) Config files can include other config files, so the db config may
  not even be in that file at all.

   3) It blindly overwrites any configuration changes made by the admin,
  which isn't permitted by Debian Policy §10.7.3. (In my case,
  bareos-dir.conf is actually a generated file — directly editing it
  is broken.)

Thankfully, there is a fairly easy approach that solves all these
problems: put the default Debian database config in its own file
(possibly under /var/lib/bareos/) and then @-include it into the shipped
bareos-dir.conf. Then you don't have to touch the configuration file.


(I fixed my system by commenting out the apply_dbconfig_settings line in
/var/lib/dpkg/info/bareos-database-common.postinst).


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

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

Versions of packages bareos depends on:
ii  bareos-client14.2.1+20141017gitc6c5b56-3+deb8u3
iu  bareos-director  14.2.1+20141017gitc6c5b56-3+deb8u3
ii  bareos-storage   14.2.1+20141017gitc6c5b56-3+deb8u3

bareos recommends no packages.

bareos suggests no packages.

-- no debconf information



Bug#884231: bareos-storage-tape: Bug 808580 exists in jessie (Package tries to chown unexisting /etc/bareos/bareos-sd.d/device-tape-with-autoloader.conf)

2017-12-12 Thread Anthony DeRobertis

Package: bareos-storage-tape
Version: 14.2.1+20141017gitc6c5b56-3+deb8u3
Severity: important
Justification: Policy 10.7.3

# dpkg --configure -a
Setting up bareos-storage-tape (14.2.1+20141017gitc6c5b56-3+deb8u3) ...
chown: cannot access 
‘/etc/bareos/bareos-sd.d/device-tape-with-autoloader.conf’: No such file or 
directory
dpkg: error processing package bareos-storage-tape (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 bareos-storage-tape

This is of course #808580 which has been fixed in newer versions (and 
wasn't reported against the version in jessie). Opening a separate bugs 
since that one is already archived; my apologies if you preferred I 
un-archive and re-open that one instead.


Easy enough to work around on my system by adding an "|| true" to the 
chown line in /var/lib/dpkg/info/bareos-storage-tape.postinst, but this 
seems like something eligible for a (old-)stable update. And quite 
possible it'll break other people's systems too.




Bug#884233: Please precreate /etc/auto.master.d directory

2017-12-12 Thread Laurent Bigonville
Package: autofs
Version: 5.1.2-1
Severity: wishlist

Hi,

The auto.master file reference the /etc/auto.master.d directory, but
that directory is not created by the package.

Would be nice if it was created as part of it.

Kind regards,

Laurent Bigonville

-- 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.14.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy

Versions of packages autofs depends on:
ii  init-system-helpers  1.51
ii  libc62.25-3
ii  libxml2  2.9.4+dfsg1-5.1
ii  ucf  3.0036

Versions of packages autofs recommends:
ii  kmod24-1
ii  nfs-common  1:1.3.4-2.1+b1

autofs suggests no packages.

-- no debconf information



Bug#884232: ffmpeg: CVE-2017-17555

2017-12-12 Thread Salvatore Bonaccorso
Source: ffmpeg
Version: 7:3.4-4
Severity: normal
Tags: security upstream
Control: found -1 7:3.4.1-1

Hi,

the following vulnerability was published for ffmpeg.

CVE-2017-17555[0]:
| The swri_audio_convert function in audioconvert.c in FFmpeg
| libswresample through 3.0.101, as used in FFmpeg 3.4.1, aubio 0.4.6,
| and other products, allows remote attackers to cause a denial of
| service (NULL pointer dereference and application crash) via a crafted
| audio file.

The issue is triggerable/demostrable with the POC attached to [1]:

$ ./aubio/build/examples/aubiomfcc ./crash-2-null-ptr
[mp3 @ 0x61b00080] Format mp3 detected only with low score of 1, 
misdetection possible!
[mp3 @ 0x61b00080] Skipping 3350 bytes of junk at 0.
[mp3 @ 0x61b00080] Estimating duration from bitrate, this may be inaccurate
0.00-18.015953 -0.012183 -0.867832 -0.616462 0.813869 -1.063807 
-0.276262 -0.236723 -1.673019 1.016008 -0.041898 0.450148 -0.699137
ASAN:DEADLYSIGNAL
=
==13255==ERROR: AddressSanitizer: SEGV on unknown address 0x (pc 
0x7fd18a85df33 bp 0x0004 sp 0x7ffec8afd8e8 T0)
==13255==The signal is caused by a READ memory access.
==13255==Hint: address points to the zero page.
#0 0x7fd18a85df32  (/usr/lib/x86_64-linux-gnu/libswresample.so.2+0x11f32)

AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV 
(/usr/lib/x86_64-linux-gnu/libswresample.so.2+0x11f32)
==13255==ABORTING

Backtrace:

Program received signal SIGSEGV, Segmentation fault.
0x72af0f33 in ff_int16_to_float_a_sse2.next ()
at src/libswresample/x86/audio_convert.asm:656
656 src/libswresample/x86/audio_convert.asm: No such file or directory.
(gdb) bt
#0  0x72af0f33 in ff_int16_to_float_a_sse2.next ()
at src/libswresample/x86/audio_convert.asm:656
#1  0x72ae78de in swri_audio_convert (ctx=0x60701740, 
out=out@entry=0x632037d0, in=in@entry=0x632035b0, len=len@entry=384) at 
src/libswresample/audioconvert.c:226
#2  0x72aee190 in swr_convert_internal (s=s@entry=0x63200800, 
out=out@entry=0x63203e30, out_count=out_count@entry=384, 
in=in@entry=0x632035b0, in_count=in_count@entry=384)
at src/libswresample/swresample.c:633
#3  0x72aef252 in swr_convert_internal (in_count=384, 
in=0x632035b0, out_count=384, out=0x63203e30, s=0x63200800) at 
src/libswresample/swresample.c:470
#4  0x72aef252 in swr_convert (s=0x63200800, out_arg=, out_count=, in_arg=, in_count=)
at src/libswresample/swresample.c:800
#5  0x76c08af5 in aubio_source_avcodec_readframe ()
at /usr/lib/x86_64-linux-gnu/libaubio.so.5
#6  0x76c08c65 in aubio_source_avcodec_do () at 
/usr/lib/x86_64-linux-gnu/libaubio.so.5
#7  0x9db4 in examples_common_process (process_func=0x91fb 
, print=0x9266 ) at 
../examples/utils.c:160
#8  0x9875 in main (argc=2, argv=0x7fffeb88) at 
../examples/aubiomfcc.c:66


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-17555
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-17555
[1] 
https://github.com/IvanCql/vulnerability/blob/master/An%20NULL%20pointer%20dereference(DoS)%20Vulnerability%20was%20found%20in%20function%20swri_audio_convert%20of%20ffmpeg%20libswresample.md

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore



  1   2   3   >