Bug#835650: Imagemagick regression pin point patch

[Bastien Roucaries]

I suppose 
https://github.com/ImageMagick/ImageMagick/commit/f6242e725c819a69bee2a444f8e4a3c7718b2b3f

Fix it. If so plezse merge  this bug with the other one régression about pdf

Le 1 septembre 2016 00:38:34 GMT+02:00, Frank Heckenbach 
 a écrit :
>> On Wed, Aug 31, 2016 at 8:42 AM, Bastien ROUCARIES
>>  wrote:
>>
>> > Patches are needed for a security point of view but it is likely a
>> > problem of backport intereaction.
>> >
>> > Could you help by pin point the problem.
>> >
>> > as root install a few package needed for imagemagick compilation:
>> > apt-get install git
>> > apt-get build-dep imagemagick
>
>Just for my reference:
>libbz2-dev libdjvulibre-dev libexif-dev libharfbuzz-dev
>libharfbuzz-gobject0 libilmbase-dev libjasper-dev libjbig-dev
>liblcms2-dev liblqr-1-0-dev liblzma-dev libopenexr-dev libpango1.0-dev
>libperl-dev libtiff5-dev libtiffxx5 libwmf-dev pkg-kde-tools xsltproc
>
>> > as a user
>> >  git clone   git://git.debian.org/git/collab-maint/imagemagick.git
>> > cd imagemagick
>>
>> HERE run
>> git checkout debian-patches/6.8.9.9-5+deb8u3
>> 
>> > git checkout debian-patches/6.8.9.9-5+deb8u4
>
>So I ran both (first +deb8u3, then +deb8u4), right?
>(Otherwise, +deb8u3 would be the same as in "good" below.)
>
>> > git bisect start
>> > git bisect bad
>> > git bissect good debian-patches/6.8.9.9-5+deb8u3
>> >
>> >   Once you have specified at least one bad and one good commit, git
>> > bisect selects a commit in the middle of that range of history,
>checks
>> > it out, and outputs something similar to the following:
>> >
>> >Bisecting: 675 revisions left to test after this
>(roughly 10 steps)
>> >
>> >  You should now compile the checked-out version and test it. If
>that
>> > version works correctly, type. Compiling is done by typing
>> > ./configure
>> > make check
>
>That already gave an error (see test-suite.log). (I first ran make
>with "-j16", then reran "make check" (but didn't rebuild) without
>"-j", same result.) I'll be ignoring this (and further test-suite
>errors I got while bisecting).
>
>> > you could run the command without installing by runing the
>convert.sh wrapper
>> > ./magick.sh convert geometry 40% tux.png tux-scaled-old.ppm
>> >
>> > if bad run
>> > git bisect bad
>> > and rerun compile and testing
>> > if good run
>> > git bisect good
>> >
>> > Some pointer could be found in man git bisect
>
>26d910675e0cd1b62e988139dba8eb11931260ac is the first bad commit
>commit 26d910675e0cd1b62e988139dba8eb11931260ac
>Author: Cristy 
>Date:   Sat Jan 30 09:37:10 2016 -0500
>
>Fix out of bound in quantum handling
>
>Bug: https://github.com/ImageMagick/ImageMagick/issues/105
>bug-ubuntu:
>https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1539053
>origin: upstream,
>https://github.com/ImageMagick/ImageMagick/commit/c4e63ad30bc42da691f2b5f82a24516dd6b4dc70
>bug-debian: https://bugs.debian.org/832506
>
>:04 04 41e16d89455879892777d50135af38993b5be722
>e841bf15b62dee866b54eab729a93163d85aee68 M  magick
>
>git diff 3e07cd10a9a2215c9edcc0c0e1541c125371cfbc
>26d910675e0cd1b62e988139dba8eb11931260ac
>shows that the change essentially replaced image->columns by
>MagickMax(image->columns,image->rows) in several places. This might
>explain why the bug only occurs with portrait. I see that some
>callers of GetQuantumExtent() use its result as the length parameter
>to ReadBlob and similar, so it seems strange to use the max of width
>and height here. Others callers might use it for a work buffer where
>this might be correct (and probably what the change was meant to
>fix), but it might be necessary to separate those two cases.
>
>Frank

-- 
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.

Bug#811743: sndobj: FTBFS with GCC 6: narrowing conversion

[Philip Chung]

Control: tags -1 patch

On Tue, 19 Jan 2016 17:48:35 -0800 Martin Michlmayr  wrote:
> Package: sndobj
> Version: 2.6.6.1-5
> Severity: important
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-6 gcc-6-narrowing
> 
> This package fails to build with GCC 6.  GCC 6 has not been released
> yet, but it's expected that GCC 6 will become the default compiler for
> stretch.

Attached is a patch to fix the error. The package now builds on my amd64
system.

Philip Chung
Description: Change GUID definition to prevent FTBFS with GCC 6
Author: Philip Chung 
Bug-Debian: https://bugs.debian.org/811743
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
---
 src/SndWaveX.h |8 
 1 file changed, 4 insertions(+), 4 deletions(-)

--- SndObj-2.6.6.orig/src/SndWaveX.h
+++ SndObj-2.6.6/src/SndWaveX.h
@@ -66,10 +66,10 @@
 #ifndef WIN
 struct GUID 
 { 
-  int			Data1; 
-  short			Data2; 
-  short			Data3; 
-  unsigned char	Data4[8]; 
+  unsigned int   Data1;
+  unsigned short Data2;
+  unsigned short Data3;
+  unsigned char  Data4[8];
 };
 #endif
 

Bug#836255: DTBs are no longer bundled

[Andre Heider]

Source: linux
Version: 4.7.0-1-armmp-lpae
Severity: important

Hi,

starting with 4.7 the DTBs are not part of the package anymore:

# dpkg -L linux-image-4.5.0-2-armmp-lpae|grep dtb|wc -l
349
# dpkg -L linux-image-4.6.0-1-armmp-lpae|grep dtb|wc -l
363
# dpkg -L linux-image-4.7.0-1-armmp-lpae|grep dtb|wc -l
0

which in return makes flash-kernel fail, and the kernel can not be
properly booted (on devices depending on flash-kernel).

Bug#836254: mutt: crashes when selecting private pgp key

[Hilmar Preuße]

Package: mutt
Version: 1.5.23-3
Severity: normal
Tags: upstream patch

Dear maintainer,

sorry, this is a bug report for stable! The bug is already fixed in unstable.
However it is a little bit annoying and a patch is available. Fix in proposed-
updates would be nice.

Steps to reproduce:
1. Write an E-Mail.
2. Before sending select "PGP sign (a)s".
3. Select a private key by hitting enter.
4. mutt crashes.

I got a core dump and a have a gdb backtrace at hand. However the problem is
described here[1] and a patch (working at least for me) is available here[2].
Consider to upload a fix for it to stable.

Hilmar

[1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199341
[2] https://svnweb.freebsd.org/ports/head/mail/mutt/files/patch-
pgpkey.c?view=markup=386495



-- Package-specific info:
Mutt 1.5.23 (2014-03-12)
Copyright (C) 1996-2009 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to redistribute it
under certain conditions; type `mutt -vv' for details.

System: Linux 3.16.0-4-amd64 (x86_64)
ncurses: ncurses 5.9.20140913 (compiled with 5.9)
libidn: 1.29 (compiled with 1.29)
hcache backend: tokyocabinet 1.4.48

Compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.9/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 4.9.2-10' 
--with-bugurl=file:///usr/share/doc/gcc-4.9/README.Bugs 
--enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr 
--program-suffix=-4.9 --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--with-gxx-include-dir=/usr/include/c++/4.9 --libdir=/usr/lib --enable-nls 
--with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug 
--enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-vtable-verify 
--enable-plugin --with-system-zlib --disable-browser-plugin 
--enable-java-awt=gtk --enable-gtk-cairo 
--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.9-amd64/jre --enable-java-home 
--with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.9-amd64 
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.9-amd64 
--with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar 
--enable-objc-gc --enable-multiarch --with-arch-32=i586 --with-abi=m64
  --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic 
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu 
--target=x86_64-linux-gnu
Thread model: posix
gcc version 4.9.2 (Debian 4.9.2-10) 

Configure options: '--prefix=/usr' '--sysconfdir=/etc' 
'--mandir=/usr/share/man' '--with-docdir=/usr/share/doc' 
'--with-mailpath=/var/mail' '--disable-dependency-tracking' 
'--enable-compressed' '--enable-debug' '--enable-fcntl' '--enable-hcache' 
'--enable-gpgme' '--enable-imap' '--enable-smtp' '--enable-pop' '--with-curses' 
'--with-gnutls' '--with-gss' '--with-idn' '--with-mixmaster' '--with-sasl' 
'--without-gdbm' '--without-bdb' '--without-qdbm' '--build' 'x86_64-linux-gnu' 
'build_alias=x86_64-linux-gnu' 'CFLAGS=-g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wall' 'LDFLAGS=-Wl,-z,relro' 
'CPPFLAGS=-D_FORTIFY_SOURCE=2 -I/usr/include/qdbm'

Compilation CFLAGS: -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wall

Compile options:
-DOMAIN
+DEBUG
-HOMESPOOL  +USE_SETGID  +USE_DOTLOCK  +DL_STANDALONE  +USE_FCNTL  -USE_FLOCK   
+USE_POP  +USE_IMAP  +USE_SMTP  
-USE_SSL_OPENSSL  +USE_SSL_GNUTLS  +USE_SASL  +USE_GSS  +HAVE_GETADDRINFO  
+HAVE_REGCOMP  -USE_GNU_REGEX  
+HAVE_COLOR  +HAVE_START_COLOR  +HAVE_TYPEAHEAD  +HAVE_BKGDSET  
+HAVE_CURS_SET  +HAVE_META  +HAVE_RESIZETERM  
+CRYPT_BACKEND_CLASSIC_PGP  +CRYPT_BACKEND_CLASSIC_SMIME  +CRYPT_BACKEND_GPGME  
-EXACT_ADDRESS  -SUN_ATTACHMENT  
+ENABLE_NLS  -LOCALES_HACK  +COMPRESSED  +HAVE_WC_FUNCS  +HAVE_LANGINFO_CODESET 
 +HAVE_LANGINFO_YESEXPR  
+HAVE_ICONV  -ICONV_NONTRANS  +HAVE_LIBIDN  +HAVE_GETSID  +USE_HCACHE  
ISPELL="/usr/bin/ispell"
SENDMAIL="/usr/sbin/sendmail"
MAILPATH="/var/mail"
PKGDATADIR="/usr/share/mutt"
SYSCONFDIR="/etc"
EXECSHELL="/bin/sh"
MIXMASTER="mixmaster"
To contact the developers, please mail to .
To report a bug, please visit http://bugs.mutt.org/.

misc/am-maintainer-mode.patch
features/ifdef.patch
features/xtitles.patch
features/trash-folder.patch
features/purge-message.patch
features/imap_fast_trash.patch
features/sensible_browser_position.patch
features-old/patch-1.5.4.vk.pgp_verbose_mime.patch
features/compressed-folders.patch
features/compressed-folders.debian.patch
debian-specific/Muttrc.patch
debian-specific/Md.etc_mailname_gethostbyname.patch
debian-specific/use_usr_bin_editor.patch
debian-specific/correct_docdir_in_man_page.patch
debian-specific/dont_document_not_present_features.patch
debian-specific/document_debian_defaults.patch
debian-specific/assumed_charset-compat.patch

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

[Salvatore Bonaccorso]

Hi,

On Tue, Aug 30, 2016 at 10:11:33AM +0100, Robert Shearman wrote:
> On Fri, 26 Aug 2016 21:52:11 +0200 Frank Heckenbach
>  wrote:
> > Package: flex
> > Version: 2.5.39-8+deb8u1
> > Severity: normal
> > 
> > After this update, I get the following warning when compiling the
> > flex generated code with gcc, which I didn't get before:
> > 
> > scan.cpp: In function ??int yy_get_next_buffer(yyscan_t)??:
> > scan.cpp:758:18: error: comparison between signed and unsigned integer 
> > expressions [-Werror=sign-compare]
> > scan.cpp:1384:3: note: in expansion of macro ??YY_INPUT??
> > 
> > Looking at the code:
> > 
> > #define YY_INPUT(buf,result,max_size) \
> > if ( YY_CURRENT_BUFFER_LVALUE->yy_is_interactive ) \
> > { \
> > int c = '*'; \
> > size_t n; \
> > for ( n = 0; n < max_size && \
> > 
> > Invoked as:
> > 
> > int num_to_read = ...
> > YY_INPUT( (_CURRENT_BUFFER_LVALUE->yy_ch_buf[number_to_move]),
> > yyg->yy_n_chars, num_to_read );
> > 
> > So indeed an unsigned value (n) is compared with a signed one
> > (num_to_read). If this is correct, the warning can be silenced with
> > a cast of the appropriate one of them.
> 
> I've run into the same bug and agree with Frank's analysis. I've confirmed
> that the following upstream commit fixes it:
> 
> https://github.com/westes/flex/commit/3946924ed5e77420c453bf841603c7278766093a

Could you test the following packages:

https://people.debian.org/~carnil/tmp/flex/

Regards,
Salvatore

Bug#836252: asymptote: only full-page figures produced with pdflatex engine

[Sanjoy Mahajan]

Package: asymptote
Version: 2.38-1
Severity: normal

After updating to TL 2016, my usual invocation of asymptote started
producing full-page figures (the size of US letter paper), rather than
the size requested in the .asy file.

For example, as with this file:

  size(100);

  draw(unitsquare);
  dot("A", (0.5,0.5));

run through

$ asy -k -vvv -noprc -render=0 -f pdf -tex pdflatex -V -wait "test"

Without the typeset text (the "A"), it works fine, as it does using the
latex engine ("-tex latex").

This problem, I have found, has been reported on the asymptote bug
tracker and extensively discussed.  It seems that a change in the
graphicx package caused the problem.

See the discussion here:



The fix is linked from there and is:



For Debian, it just means patching plain.asy (adding a few lines).

That patch also fixes another problem with using asymptote and TL 2016:
that luatex 0.95 (and hence lualatex), which is in TL 2016, uses
\page(height|width) rather than \pdfpage(height|width), which the older
luatexs accepted.

To see that problem, try

$ asy -k -vvv -noprc -render=0 -f pdf -tex lualatex -V -wait "test"

and you get complaints about those commands being undefined.

The patch works for me, at least in my limited testing so far.

-Sanjoy


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

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

Versions of packages asymptote depends on:
ii  freeglut3 2.8.1-3
ii  ghostscript   9.19~dfsg-2
ii  imagemagick   8:6.8.9.9-7.2
ii  install-info  6.1.0.dfsg.1-8
ii  libc6 2.23-5
ii  libfftw3-double3  3.3.4-2+b1
ii  libgc1c2  1:7.4.2-8
ii  libgcc1   1:6.1.1-11
ii  libgl1-mesa-glx [libgl1]  11.2.2-1
ii  libglu1-mesa [libglu1]9.0.0-2.1
ii  libgsl2   2.1+dfsg-2
ii  libncurses5   6.0+20160625-1
ii  libosmesa611.2.2-1
ii  libreadline6  6.3-8+b4
ii  libsigsegv2   2.10-5
ii  libstdc++66.1.1-11
ii  libtinfo5 6.0+20160625-1
ii  python2.7.11-2
ii  python-pil3.3.0-1
ii  python-pil.imagetk3.3.0-1
ii  tex-common6.05
ii  texlive-binaries  2016.20160513.41080-6
ii  texlive-latex-base2016.20160819-2
ii  texlive-pstricks  2016.20160819-1
ii  xdg-utils 1.1.1-1
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages asymptote recommends:
ii  asymptote-doc  2.38-1

Versions of packages asymptote suggests:
ii  evince [pdf-viewer]   3.20.1-1
ii  gv [pdf-viewer]   1:3.7.4-1
ii  mupdf [pdf-viewer]1.9a+ds1-1.2
ii  okular [pdf-viewer]   4:16.04.2-1
ii  xpdf [pdf-viewer] 3.04-1+b1
ii  zathura-pdf-poppler [pdf-viewer]  0.2.6-1

-- no debconf information

Bug#836253: reportbug: Do not hardcode icon in desktop file

[Alex]

Package: reportbug
Version: 6.6.6
Severity: minor

Dear Maintainer,

It would be nice if the reportbug.desktop file did not hardcode the icon path
as
to allow icon themes to change the icon.



-- Package-specific info:
** Environment settings:
INTERFACE="gtk2"

** /home/alex/.reportbugrc:
reportbug_version "6.6.6"
mode standard
ui gtk2
email "agram...@gmail.com"
no-cc
header "X-Debbugs-CC: agram...@gmail.com"
smtphost reportbug.debian.org

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

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

Versions of packages reportbug depends on:
ii  apt   1.3~rc2
ii  python-reportbug  6.6.6
pn  python:any

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail 
pn  debconf-utils  
pn  debsums
pn  dlocate
ii  emacs24-bin-common 24.5+1-6+b2
ii  exim4  4.87-3
ii  exim4-daemon-light [mail-transport-agent]  4.87-3
ii  file   1:5.28-4
ii  gnupg  1.4.20-6
ii  python-gtk22.24.0-5
pn  python-gtkspellcheck   
pn  python-urwid   
ii  python-vte 1:0.28.2-5+b1
ii  xdg-utils  1.1.1-1

Versions of packages python-reportbug depends on:
ii  apt   1.3~rc2
ii  file  1:5.28-4
ii  python-debian 0.1.29
ii  python-debianbts  2.6.1
pn  python:any

python-reportbug suggests no packages.

-- no debconf information

Bug#836251: linux: [armhf] Please enable support for veyron-speedy

[Vagrant Cascadian]

Package: linux
Severity: wishlist
Tags: patch

Please enable support for veyron-speedy (a.k.a. ASUS Chromebook C201)
to linux 4.8.x.

It detects all four cores and 4GB of ram.  Tested working HDMI, LCD
panel, touchpad (w/ some multitouch), keyboard, microSD, cpufreq,
battery and charger. All in all, a fairly complete ARM system!

eMMC may need a small fix/workaround to work reliably, submitted
upstream:

  http://www.spinics.net/lists/devicetree/msg140632.html

Haven't had success getting output form the speakers or headphone
jack, though the OS seems to detect at least one device.

The wifi requires non-free firmware-brcm80211, though I haven't had much
luck with it. USB ethernet and USB wifi adapters work, though.

Thanks!


live well,
  vagrant


diff --git a/debian/config/armhf/config b/debian/config/armhf/config
index 0a9be6f..4fc638c 100644
--- a/debian/config/armhf/config
+++ b/debian/config/armhf/config
@@ -1262,3 +1263,28 @@ CONFIG_SND_SOC_TEGRA_ALC5632=m
 CONFIG_SND_SOC_TEGRA_MAX98090=m
 CONFIG_SND_SOC_TEGRA_RT5677=m
 
+CONFIG_BATTERY_SBS=m
+CONFIG_DRM_PANEL=y
+CONFIG_DRM_PANEL_SIMPLE=m
+CONFIG_BACKLIGHT_PWM=m
+CONFIG_CHARGER_GPIO=m
+CONFIG_MFD_CROS_EC=m
+CONFIG_I2C_CROS_EC_TUNNEL=m
+CONFIG_MOUSE_ELAN_I2C=m
+CONFIG_KEYBOARD_CROS_EC=m
+CONFIG_KEYBOARD_GPIO=m
+CONFIG_POWER_RESET_GPIO=y
+CONFIG_POWER_RESET_GPIO_RESTART=y
+CONFIG_MFD_RK808=y
+CONFIG_COMMON_CLK_RK808=m
+CONFIG_REGULATOR_RK808=m
+CONFIG_RTC_DRV_RK808=y
+CONFIG_PHY_ROCKCHIP_DP=m
+CONFIG_MFD_CROS_EC_SPI=m
+CONFIG_ROCKCHIP_DW_MIPI_DSI=m
+CONFIG_DRM_ANALOGIX_DP=m
+CONFIG_ROCKCHIP_ANALOGIX_DP=m
+CONFIG_PHY_ROCKCHIP_EMMC=m
+CONFIG_ROCKCHIP_IODOMAIN=m
+CONFIG_POWER_AVS=y
+CONFIG_ROCKCHIP_PM_DOMAINS=y


signature.asc
Description: PGP signature

Bug#836250: transition: gloox

[Vincent Cheng]

Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: transition
Severity: normal

Hi,

I'd like to request a transition slot for src:gloox. This is a relatively small
transition, with only 2 source packages affected, both of which aren't
in testing so this bug report might be completely unnecessary (I guess
this bug could be considered a binNMU request for 0ad instead):

0ad (not in testing due to RC bug in dependency, #811612)
uwsgi (FTBFS, #828785 and #833055)

Ben file:

(https://release.debian.org/transitions/html/auto-gloox.html is accurate)

Regards,
Vincent

Bug#836249: ITP: cavewhere -- Cave survey processing and visualisation

[Wookey]

Package: wnpp
Severity: wishlist
Owner: Wookey 

  Package name: cavewhere
  Version : 0~20160817
  Upstream Author : Philip Schuchardt 
  URL : http://www.cavewhere.com/
  License : GPL3
  Programming Lang: C++
  Description : Cave survey processing and visualisation

 GUI cave survey software, with data entry entry covering multiple data
 formats. Data is processed using survex. Sketches are distorted to fit
 and displayed in 3D, allowing very fast turnaround maps to be produced.
 Uses QT and works on Windows, Mac and Linux. Data can be imported from
 Walls and Survex.

This is quite new software, with a user-friendly modern GUI and taking
a different approach to Tunnel and Therion, the other free-software
cave-survey drawing packages. It has a very helpful upstream. It has
several dependencies which are not yet in debian and thus will need
packaging first: libsquish, qmath3d, dewalls, qt-qml-tricks.

Bug#807503: vlc: Snapshot does nothing

[humberto]

Package: vlc
Version: 2.2.4-1~deb8u1
Followup-For: Bug #807503

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


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

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

Versions of packages vlc depends on:
ii  fonts-freefont-ttf  20120503-4
ii  libaa1  1.4p5-43
ii  libavcodec566:11.7-1~deb8u1
ii  libavutil54 6:11.7-1~deb8u1
ii  libc6   2.19-18+deb8u4
ii  libcaca00.99.beta19-2
ii  libegl1-mesa [libegl1-x11]  10.3.2-1+deb8u1
ii  libfreerdp-cache1.1 1.1.0~git20140921.1.440916e+dfsg1-4
ii  libfreerdp-client1.11.1.0~git20140921.1.440916e+dfsg1-4
ii  libfreerdp-codec1.1 1.1.0~git20140921.1.440916e+dfsg1-4
ii  libfreerdp-core1.1  1.1.0~git20140921.1.440916e+dfsg1-4
ii  libfreerdp-crypto1.11.1.0~git20140921.1.440916e+dfsg1-4
ii  libfreerdp-gdi1.1   1.1.0~git20140921.1.440916e+dfsg1-4
ii  libfreerdp-locale1.11.1.0~git20140921.1.440916e+dfsg1-4
ii  libfreerdp-rail1.1  1.1.0~git20140921.1.440916e+dfsg1-4
ii  libfreerdp-utils1.1 1.1.0~git20140921.1.440916e+dfsg1-4
ii  libfreetype62.5.2-3+deb8u1
ii  libfribidi0 0.19.6-3
ii  libgcc1 1:4.9.2-10
ii  libgl1-mesa-glx [libgl1]11.1.3-1~bpo8+1
ii  libgles1-mesa [libgles1]11.1.3-1~bpo8+1
ii  libgles2-mesa [libgles2]11.1.3-1~bpo8+1
ii  libice6 2:1.0.9-1+b1
ii  libpulse0   5.0-13
ii  libqtcore4  4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqtgui4   4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libsdl-image1.2 1.2.12-5+b5
ii  libsdl1.2debian 1.2.15-10+b1
ii  libsm6  2:1.2.2-1+b1
ii  libstdc++6  4.9.2-10
ii  libva-drm1  1.4.1-1
ii  libva-x11-1 1.4.1-1
ii  libva1  1.4.1-1
ii  libvlccore8 2.2.4-1~deb8u1
ii  libvncclient0   0.9.9+dfsg2-6.1+deb8u1
ii  libwinpr-rpc0.1 1.1.0~git20140921.1.440916e+dfsg1-4
ii  libwinpr-sspi0.11.1.0~git20140921.1.440916e+dfsg1-4
ii  libwinpr-utils0.1   1.1.0~git20140921.1.440916e+dfsg1-4
ii  libx11-62:1.6.2-3
ii  libxcb-composite0   1.10-3+b1
ii  libxcb-keysyms1 0.4.0-1
ii  libxcb-randr0   1.10-3+b1
ii  libxcb-render0  1.10-3+b1
ii  libxcb-shape0   1.10-3+b1
ii  libxcb-shm0 1.10-3+b1
ii  libxcb-xfixes0  1.10-3+b1
ii  libxcb-xv0  1.10-3+b1
ii  libxcb1 1.10-3+b1
ii  libxext62:1.3.3-1
ii  libxinerama12:1.1.3-1+b1
ii  libxpm4 1:3.5.11-1+b1
ii  vlc-nox 2.2.4-1~deb8u1
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages vlc recommends:
ii  vlc-plugin-notify  2.2.4-1~deb8u1
ii  vlc-plugin-samba   2.2.4-1~deb8u1
ii  xdg-utils  1.1.0~rc1+git20111210-7.4

Versions of packages vlc suggests:
pn  videolan-doc  

Versions of packages vlc-nox depends on:
ii  liba52-0.7.4   0.7.4-17
ii  libasound2 1.0.28-1
ii  libass50.10.2-3
ii  libavahi-client3   0.6.31-5
ii  libavahi-common3   0.6.31-5
ii  libavc1394-0   0.5.4-2
ii  libavcodec56   6:11.7-1~deb8u1
ii  libavformat56  6:11.7-1~deb8u1
ii  libavutil546:11.7-1~deb8u1
ii  libbasicusageenvironment0  2014.01.13-1
ii  libbluray1 1:0.6.2-1
ii  libc6  2.19-18+deb8u4
ii  libcddb2   1.3.2-5
ii  libcdio13  0.83-4.2
ii  libchromaprint01.2-1
ii  libcrystalhd3  1:0.0~git20110715.fdd2f19-11
ii  libdbus-1-31.8.20-0+deb8u1
ii  libdc1394-22   2.2.3-1
ii  libdca00.0.5-7
ii  libdirectfb-1.2-9  1.2.10.0-5.1
ii  libdvbpsi9 1.2.0-1
ii  libdvdnav4 5.0.1-1
ii  libdvdread45.0.0-1
ii  libebml4   1.3.0-2+deb8u1
ii  libfaad2   2.7-8
ii  libflac8   1.3.0-3
ii  libfontconfig1 2.11.0-6.3+deb8u1
ii  libfreetype6   2.5.2-3+deb8u1
ii  libfribidi00.19.6-3
ii  libgcc1  

Bug#836247: ITP: libsquish -- DXT texture compression library

[Wookey]

On 2016-09-01 10:43 +0800, Paul Wise wrote:
> On Thu, Sep 1, 2016 at 9:18 AM, Wookey wrote:
> 
> > This package is a build-dependency of Cavewhere
> 
> FYI, there are also a number of copies of it already in the archive:
> 
> https://anonscm.debian.org/viewvc/secure-testing/data/embedded-code-copies?r1=44004=44249

Cheers, that's useful info.

7 packagings and it's still not uploaded separately! It was only
supplied as a static library until quite recently, which may explain
it, I guess.

I've finished the basic packaging already. I'll look into those and
see if they have diverged from upstream significantly.

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


signature.asc
Description: Digital signature

Bug#836247: ITP: libsquish -- DXT texture compression library

[Paul Wise]

On Thu, Sep 1, 2016 at 9:18 AM, Wookey wrote:

> This package is a build-dependency of Cavewhere

FYI, there are also a number of copies of it already in the archive:

https://anonscm.debian.org/viewvc/secure-testing/data/embedded-code-copies?r1=44004=44249

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#836248: /usr/bin/dh_sphinxdoc: please provide substvar for Built-Using

[Sean Whitton]

Package: sphinx-common
Version: 1.4.6-1
Severity: normal
File: /usr/bin/dh_sphinxdoc

Dear maintainer,

If a package installs sphinx documentation then it can embed code from
sphinx themes, such as python3-alabaster.  That means it needs a
"Built-Using: python3-alabaster (= foo)".  dh_sphinxdoc could provide a
substvar for this purpose.

I selected severity 'normal' rather than 'wishlist' since without such a
substvar packages using sphinx themes are violating policy.  It is not
really feasible to supply Built-Using without a substvar as then a
exactly-equal build dependency on the sphinx theme in question would be
required.

(Is there some reason why the copy of the theme is not turned into
symlinks by dh_sphinxdoc, as embedded javascript is?)

Thanks.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: i386 (i686)

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

Versions of packages sphinx-common depends on:
ii  libjs-sphinxdoc  1.4.6-1

Versions of packages sphinx-common recommends:
ii  python3-sphinx  1.4.6-1

sphinx-common suggests no packages.

-- no debconf information

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#830658: [pkg-gnupg-maint] Bug#834829: gnupg-agent: gpg-agent looses connection to usb dongle and stops working

[Norbert Preining]

Hi Daniel,

> it's a little bit weird that you say that "updatestartuptty" did not
> change anything:
> 
> > [~] gpg-connect-agent updatestartuptty /bye
> > OK
> > [~]
> >
> >> gpg-connect-agent 'getinfo std_startup_env' /bye
> >
> > [~] gpg-connect-agent 'getinfo std_startup_env' /bye
> > D GPG_TTY=/dev/pts/2
> > D TERM=xterm
> > D DISPLAY=:0
> > D XAUTHORITY=/home/norbert/.Xauthority
> > D XMODIFIERS=@im=fcitx
> > D GTK_IM_MODULE=fcitx
> > D 
> > DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-CY1VsRjJ7v,guid=d93c4131d59dc5ca299bf49f57c6d42e
> > D QT_IM_MODULE=fcitx
> > OK
> > [~]
> 
> can you compare this content of "std_startup_env" with the same query on
> the first login after a reboot, before any invocation of
> "updatestartuptty" ?


Logging in after reboot and systemd started gpg-agent, I get first:

[~] gpg-connect-agent 'getinfo std_startup_env' /bye
OK
[~] gpg-connect-agent updatestartuptty /bye
OK
[~] gpg-connect-agent 'getinfo std_startup_env' /bye
D GPG_TTY=/dev/pts/1
D TERM=xterm
D DISPLAY=:0
D XAUTHORITY=/home/norbert/.Xauthority
D XMODIFIERS=@im=fcitx
D GTK_IM_MODULE=fcitx
D 
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-eav2P5eDYT,guid=ab31db8dd7c34660f839f49857c78567
D QT_IM_MODULE=fcitx
OK
[~]

So ok, something changes.

What I meant is that I still cannot logL
[~] ssh 
sign_and_send_pubkey: signing failed: agent refused operation
sign_and_send_pubkey: signing failed: agent refused operation
user@somehost 's password:


> >> one other question for those following this bug: do you have
> >> the dbus-user-session package installed?
> >
> > dbus-user-session installed.

Maybe that was lost: I do *NOT* have dbus-user-session installed.

> ok, but can you clarify that a pinentry prompt does work for you in
> general?

How should I run it without the /run/user/1000/bus ? 

> sorry, i'm pretty confused by this -- when you say this "actually works"
> can you be clear about what the change is before and after you run this?

Ok, here is what I have seen/am seeing:
There are three methods to start gpg-agent:
1* systemd
2* gpgconf --launch gpg-agent
3* gpg-agent --daemon

1* is discussed above

2* This was my initial report that starting gpg-agent with the gpgconf
method gives me disconnects/usbstick becomes unusable and needs
replugging

3* Is the only method where I have consistent access to the usb stick/
smartcard where my gpg/ssh key is served from, and logging in 
gives me a pinentry - this is what I meant with "working".

1* is broken (sorry, for me not surprising since it involves systemd :-(
2* is *somehow* broken, but not completely
3* is working fine, but is suboptimal because it requires manual start
   of the daemon

> Are you saying that running "gpg-agent --daemon" separately somehow
> allows access to your usb dongle?

In fact what needs to be done is disabling the systemd gpg-agent
(otherwise it is permanently restarted), then killing all gpg-agents,
and starting gpg-agent --daemon by hand is the only way I can get
consistent access to my usb dongle.

All the best

Norbert

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

Bug#836247: ITP: libsquish -- DXT texture compression library

[Wookey]

Package: wnpp
Severity: wishlist
Owner: Wookey 

  Package name: libsquish
  Version : 1.13
  Upstream Author : Simon Brown, Stefan Röttger
  URL : https://sourceforge.net/projects/libsquish
  License : MIT
  Programming Lang: C++
  Description : DXT texture compression library

 libsquish is a software DXT texture compression library. It
 implements the 5 DXT flavours and has SIMD support for x86 (SSE) and
 powerpc (Altivec). It can be used (as a much slower software
 fallback) instead of the hardware implementations present on most
 modern graphics chips.

This package is a build-dependency of Cavewhere
(https://github.com/Cavewhere, http://www.cavewhere.com), used because
using the hardware implementations has been unreliable in practice,
and speed is not critical here..

Bug#836246: libgtk-3-0: Upgrade from 3.20.9 to 3.21.5 broke Mate desktop

[Cesare Leonardi]

Package: libgtk-3-0
Version: 3.20.9-1
Severity: normal

On three pc of mine i had to downgrade the following libraries to have a
functioning desktop:
libgail-3-0
libgtk-3-0
libgtk-3-bin

Up to version 3.20.9-1 all were fine but with 3.21.5-1 and 3.21.5-2 i
had so many issues that i had to find a way to come back to a previous
state.
These are the issue i can document, but certainly there are others:
- caja (file manager) doesn't start at all.
- desktop fonts look ugly, like there isn't any antialias.
- desktop doesn't repaint correctly: if you move an icon, the older is
  still there.
- mate terminal crash if you try to change color settings.

Journalctl reports tons of entries like those, indeed belonging to
applets that updates their visualization frequently:
--
ago 31 19:52:16 barone mate-cpufreq-ap[15177]: gtk_widget_size_allocate(): 
attempt to underallocate CPUFreqApplet's child GtkAlignment 0x8049a148. 
Allocation is 55x24, but minimum required size is 83x24.
ago 31 19:52:16 barone mate-cpufreq-ap[15177]: gtk_widget_size_allocate(): 
attempt to underallocate GtkAlignment's child GtkBox 0x80333fb8. Allocation is 
55x24, but minimum required size is 83x24.
ago 31 19:52:16 barone mate-cpufreq-ap[15177]: gtk_widget_size_allocate(): 
attempt to underallocate CPUFreqApplet's child GtkAlignment 0x8049a250. 
Allocation is 55x24, but minimum required size is 83x24.
ago 31 19:52:16 barone mate-cpufreq-ap[15177]: gtk_widget_size_allocate(): 
attempt to underallocate GtkAlignment's child GtkBox 0x80333ce8. Allocation is 
55x24, but minimum required size is 83x24.
ago 31 19:52:16 barone clock-applet[15178]: gtk_widget_size_allocate(): attempt 
to underallocate toplevel GtkPlug 0x80c171d0. Allocation is 178x24, but minimum 
required size is 178x26.
ago 31 19:52:16 barone clock-applet[15178]: gtk_widget_size_allocate(): attempt 
to underallocate GtkPlug's child MatePanelApplet 0x80adb138. Allocation is 
178x24, but minimum required size is 178x26.
ago 31 19:52:16 barone clock-applet[15178]: gtk_widget_size_allocate(): attempt 
to underallocate MatePanelApplet's child GtkToggleButton 0x80ae9898. Allocation 
is 178x24, but minimum required size is 178x26.
ago 31 19:52:16 barone clock-applet[15178]: gtk_widget_size_allocate(): attempt 
to underallocate GtkToggleButton's child ClockBox 0x80ce14a8. Allocation is 
168x14, but minimum required size is 168x16.
ago 31 19:52:16 barone clock-applet[15178]: gtk_widget_size_allocate(): attempt 
to underallocate ClockBox's child ClockBox 0x80ce1598. Allocation is 18x14, but 
minimum required size is 18x16.
ago 31 19:52:16 barone clock-applet[15178]: gtk_widget_size_allocate(): attempt 
to underallocate ClockBox's child GtkLabel 0x80cddc58. Allocation is 138x14, 
but minimum required size is 138x15.
--

The same issues happened on four different machine, with different
gtk theme, adwaita included: a 686, a 686-pae, two amd64.
On one of them i've installed a fresh Mate Desktop, so i think we could
say that the problem is always reproducible. You can try: i've just
installed task-mate-desktop, without any recommended or suggested packages.

I don't know what other infos i can provide.
I've kept a 686 PC with the broken libraries available in case you need
more infos or in case you want me to make some tests.

Cesare.


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

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

Versions of packages libgtk-3-0 depends on:
ii  adwaita-icon-theme  3.20-3
ii  hicolor-icon-theme  0.15-1
ii  libatk-bridge2.0-0  2.20.1-4
ii  libatk1.0-0 2.20.0-1
ii  libc6   2.23-5
ii  libcairo-gobject2   1.14.6-1+b1
ii  libcairo2   1.14.6-1+b1
ii  libcolord2  1.3.2-1
ii  libcups22.1.4-4
ii  libepoxy0   1.3.1-1
ii  libfontconfig1  2.11.0-6.7
ii  libfreetype62.6.3-3+b1
ii  libgdk-pixbuf2.0-0  2.34.0-1
ii  libglib2.0-02.48.1-3
ii  libgtk-3-common 3.20.9-1
ii  libjson-glib-1.0-0  1.2.2-1
ii  libpango-1.0-0  1.40.1-1
ii  libpangocairo-1.0-0 1.40.1-1
ii  libpangoft2-1.0-0   1.40.1-1
ii  librest-0.7-0   0.8.0-1
ii  libsoup2.4-12.54.1-1
ii  libwayland-client0  1.11.0-2
ii  libwayland-cursor0  1.11.0-2
ii  libwayland-egl1-mesa [libwayland-egl1]  11.2.2-1
ii 

Bug#836245: GUI of reportbug requires an additional package which isn't shipped by default

[Stefan]

Package: reportbug
Version: 6.6.3

Hi, if I start the GUI-Version of reportbug from the menu on a fresh install of 
Debian 8.5 (from the netinstall-cd) with the Mate-Desktop-Enivroment, 
i got a window which says:

„Please install the python-vte package to use the GTK+ 
(known as ‚gtk2‘ in reportbug) interface.
Falling back to ‚text‘ interface."

After installing that mentioned package, everything works fine. But I expected 
that everything is installed to start any application on
a default installation.

During the installation of the system i just selected: 
Debian-Desktop-Enviroment, Mate-Desktop and Debian-systemtools

Debian: 8.5
Kernel: 3.16.7-ckt25-2+deb8u3
Mate-DE: 1.8.1

Regards Stefan

Bug#746415: gnome-terminal: will not start with non-utf-8 locale

[Leandro Doctors]

Hi, all.

I can confirm this also happens with gnome-terminal 3.20.2-4.

Best,
Leandro

Bug#836244: Update debhelper addon to automatically generate dependencies for desktop files using gapplication

[Michael Biebl]

Package: gnome-pkg-tools
Version: 0.19.7
Severity: wishlist

For some background, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835059

We should automatically generate dependencies on libglib2.0-bin, if a
desktop file uses ExecStart=gapplication.
This dependency could be injected via the misc:Depends substvar.


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

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

Versions of packages gnome-pkg-tools depends on:
ii  perl  5.22.2-3

Versions of packages gnome-pkg-tools recommends:
ii  svn-buildpackage  0.8.6

gnome-pkg-tools suggests no packages.

-- no debconf information

Bug#836223: Bug#835653: how-can-i-help: sort "Packages removed from Debian 'testing'" list

[Tomasz Nitecki]

tags 836223 - pending
tags 836223 - newcomer
tags 836223 - patch
severity 836223 wishlist
thanks


On 31/08/16 19:28, Adrian Bunk wrote:
> On Tue, Aug 30, 2016 at 04:34:21PM +0300, Adrian Bunk wrote:
>> Similar, O/RFA -> ITA changes should also not trigger listing as "new".
> 
> After thinking about it further, how-can-i-help should simply stop 
> listing ITA bugs:
> 
> The semantics of ITA is "someone is adopting it, and the new maintainer 
> is expected to make an upload soon".
> 
> At that point it is unlikely that help is needed.
> 
> And many of the rare cases where the new maintainer does need help are 
> already covered by RFS/RFH/#825349.

While I do agree that many ITAs don't need any help, I personally often
check them, as they are sometimes misused (unintentionally) by newcomers
who just assign them to themselves and then vanish. Just one of a
possible use cases of this feature.

Since you can easily configure how-can-i-help to ignore those bugs
(section 'IGNORE SELECTED TYPES OF OPPORTUNITIES' in manpage), I'd
rather leave it as it is.


Regards,
T.




signature.asc
Description: OpenPGP digital signature

Bug#836175: [buildd-tools-devel] Bug#836175: libsbuild-perl: Do not use single quotes in embedded perl script

[Samuel Thibault]

Johannes Schauer, on Wed 31 Aug 2016 19:29:47 +0200, wrote:
> if your setup deviates from the default, please include in your bugreport how
> it does.

Ok, got to reproduce it easily:

# sbuild-createchroot sid /var/tmp/foo http://ftp2.fr.debian.org/debian
# sudo sbuild-adduser samy  

in ~samy/.sbuildrc, just put 

$chroot_mode='sudo';

and then

sbuild -d sid foo_1.1-1

gets the issue.

Samuel

Bug#836230: [Debian-med-packaging] Bug#836230: genometools: FTBFS in testing (a2x: ERROR: "xsltproc" returned non-zero exit status 6)

[Santiago Vila]

This is my build history:

Status: successful  genometools_1.5.9+ds-2_amd64-20160811T2351Z
Status: successful  genometools_1.5.9+ds-2_amd64-20160816T1151Z
Status: successful  genometools_1.5.9+ds-2_amd64-20160821T235102Z
Status: failed  genometools_1.5.9+ds-2_amd64-20160831T144105Z
Status: failed  genometools_1.5.9+ds-2_amd64-20160831T152720Z

All those builds were done in machines with 768 MB of RAM
(and 1GB of swap).

Why it built ok in the past and now it does not build?

Bug#835653: how-can-i-help: sort "Packages removed from Debian 'testing'" list

[Tomasz Nitecki]

On 30/08/16 15:34, Adrian Bunk wrote:
> On Mon, Aug 29, 2016 at 02:52:45PM +0200, Tomasz Nitecki wrote:
>> 
> Note that patch 0003 doesn't actually change anything
> (the order of the sort fields is wrong).
> 
> How has this patch been tested?

Yes, you are right. I didn't test it as I was thinking about it as a
potential optional feature. One that needs to be changed to be useful.


>> I'm also wondering if sorting by removal
>> date as the primary sorting field, wouldn't be more useful in this case
>> (so that the packages that are going to be removed first are at the
>> top)? What do you think?
> 
> I was actually about to suggest something similar, since this part of 
> "how-can-i-help --old --all" makes most sense when it tells you what
> is going to be removed soon.

Nicolas, would you like to change your patch 0003 according to the
comments above and make it optional (preferably activated by a command
line option)? Or would you prefer if I do it?


> 
> Not sure whether it is related to what Paul is doing, but I would call 
> it a bug that how-can-i-help (without --old) lists a package under
> "New packages going to be removed from Debian 'testing'" each time
> a comment to a bug report moved that removal further into the future.
> 
> As an example, "how-can-i-help --all" currently lists fpc and all it's 
> rdeps every day again as "new" due to the discussion in #826300.

At the moment, we are deciding if autoremoval is new based on: source,
version and removal time. If the removal time changes, package is going
to be shown again. We could probably change 'removal time' to 'first
seen' (first appearance of autorm bug), but first I will have to confirm
that this field works as I think it does.

Anyway, I believe that this subject is not related to this (#835653)
pending bug, so how about we move to a new (possibly wishlist?) bug report?


> Similar, O/RFA -> ITA changes should also not trigger listing as "new".

I'll answer this in a reply to your follow up.


Regards,
T.




signature.asc
Description: OpenPGP digital signature

Bug#836230: [Debian-med-packaging] Bug#836230: genometools: FTBFS in testing (a2x: ERROR: "xsltproc" returned non-zero exit status 6)

[Santiago Vila]

severity 836230 normal
retitle 836230 FTBFS in a low memory machine with poor error message
thanks

On Wed, Aug 31, 2016 at 10:10:40PM +0100, Sascha Steinbiss wrote:

> > I tried to build this package in stretch with "dpkg-buildpackage -A"
> > (which is what the "Arch: all" autobuilder would do to build it)
> > but it failed:
> […]
> > a2x: ERROR: "xsltproc"  --stringparam callout.graphics 0 --stringparam 
> > navig.graphics 0 --stringparam admon.textlabel 1 --stringparam 
> > admon.graphics 0  "/etc/asciidoc/docbook-xsl/manpage.xsl" 
> > "/<>/genometools-1.5.9+ds/doc/manpages/gt.xml" returned non-zero 
> > exit
> 
> Unfortunately, I can not reproduce this. For me the package builds with no 
> problem (-A and -B with gbp-buildpackage and cowbuilder in a freshly updated 
> stretch chroot). Build logs can be found at 
> http://dropbox.tetrinetsucht.de/debian/ (too large for paste.debian.net).
> 
> > This used to work in the past, so I would look for build-dependencies
> > which may have changed their behaviour recently.
> 
> Both docbook-xsl and asciidoc, which may be the relevant build-deps here, 
> didn’t have any recent uploads.
> 
> I am wondering if anyone may have any hints?

Sorry, I thought this was easily reproducible because it happened in
two different machines.

But now I see that the two machines have 768 MB of RAM.

I'm now building on machines with more memory, and so far it does not
seem to fail when I have 3GB of RAM.

To reproduce, please try building on a machine with only 768 MB of RAM.

If that's the reason for the build failure, then the problem is that
the build does not say "out of memory" or anything like that. Instead
it says "exit status 6" which does not help very much to know
what exactly went wrong.

Thanks.

Bug#820984: proftpd-basic: cannot preseed / ignores local config changes

[Hilmar Preusse]

On 14.04.16 Florian Ernst (f...@lf.net) wrote:

Hi Flo,

I'm trying to understand the problem.

> please consider the following (abridged) transcript of trying to run
> proftpd-basic from inetd, but ending up having it running standalone:
> 
> root@testvz12:~# debconf-get-selections | grep proftpd || echo '# no match'
> # no match
> root@testvz12:~# echo 'proftpd-basic   shared/proftpd/inetd_or_standalone 
>  select  from inetd' | debconf-set-selections
> root@testvz12:~# debconf-get-selections | grep proftpd || echo '# no match'
> proftpd-basic   shared/proftpd/inetd_or_standalone  select   from inetd
> root@testvz12:~# apt-get install -y openbsd-inetd
> [...]
> root@testvz12:~# DEBIAN_FRONTEND=noninteractive apt-get install -y 
> proftpd-basic
> [...]
> root@testvz12:~# debconf-get-selections | grep proftpd || echo '# no match'
> # Run proftpd:
> proftpd-basic   shared/proftpd/inetd_or_standalone  select  standalone
> root@testvz12:~# ps auxww | grep '[p]roftpd'
> proftpd   2138  0.0  0.2 119900  2524 ?Ss   11:28   0:00 proftpd: 
> (accepting connections)  
> root@testvz12:~# netstat -tulpen | grep 21
> tcp6   0  0 :::21   :::*LISTEN
>   1081069993275  2138/proftpd: (acce
> 
> As you can see, the preseeding had no effect. This is due to
> /var/lib/dpkg/info/proftpd-basic.config unconditionally calling
> "db_set shared/proftpd/inetd_or_standalone standalone" before calling
> "db_input high shared/proftpd/inetd_or_standalone", thus overwriting any
> previous setting. JFTR, apparently it was debbug#707689 which triggered
> adding the explicit db_set.
> 
The patch which "solved" the problem was [1]

diff --git a/debian/proftpd-basic.config b/debian/proftpd-basic.config
index 9e3b174..d787c4e 100644
--- a/debian/proftpd-basic.config
+++ b/debian/proftpd-basic.config
@@ -9,6 +9,7 @@ action=$1
 version=$2
 
 db_title ProFTPD configuration
-
+db_set shared/proftpd/inetd_or_standalone standalone
 db_input high shared/proftpd/inetd_or_standalone || true
-db_go
+db_go || true
+

As you already noticed it introduced a simple default before even the
question was asked what the end user expects.

Unfortunately I'm failing to understand why this change was
introduced. At this time we had a template file with a default
configured [2]:

Template: shared/proftpd/inetd_or_standalone
Type: select
__Choices: from inetd, standalone
Default: standalone

Therefore an explicit "db_set shared/proftpd/inetd_or_standalone
standalone" should not have been ever necessary...and I don't
understand why the problem described in #707689 did even occur.

1. Was there a problem in debconf?
2. Can we simply revert the change made in the past?

At least when looking @the samples in debconf.config &
debconf.templatesdebconf.templates simply removing the line

db_set shared/proftpd/inetd_or_standalone standalone

should do the trick. What am I missing?

> The same applies to any reconfiguring, of course:
> 
> root@testvz12:~# echo 'proftpd-basic   shared/proftpd/inetd_or_standalone 
>  select  from inetd' | debconf-set-selections
> root@testvz12:~# debconf-get-selections | grep proftpd || echo '# no match'
> # Run proftpd:
> proftpd-basic   shared/proftpd/inetd_or_standalone  select   from inetd
> root@testvz12:~# dpkg-reconfigure -fnoninteractive proftpd-basic
> usermod: no changes
> root@testvz12:~# debconf-get-selections | grep proftpd || echo '# no match'
> # Run proftpd:
> proftpd-basic   shared/proftpd/inetd_or_standalone  select  standalone
> 
> As such, the package cannot be preseeded to run from inetd at all.
> 
> Furthermore, given the current .config, any unattended (thus:
> noninteractive) upgrade (or even a mere reinstall) will
> unconditionally overwrite the local configuration just the same,
> leading to proftpd running standalone instead of from inetd.  I
> consider this to be in violation of Debian policy requiring local
> configuration changes to be preserved.
> 
Many thanks!

Hilmar

[1] 
https://anonscm.debian.org/cgit/pkg-proftpd/proftpd-dfsg.git/patch/?id=8e07454023648c213ee9f9f3a1f28716b48a1544
[2] 
https://anonscm.debian.org/cgit/pkg-proftpd/proftpd-dfsg.git/tree/debian/proftpd-basic.templates?id=8e07454023648c213ee9f9f3a1f28716b48a1544
-- 
sigfault


signature.asc
Description: Digital signature

Bug#836238: no command line prompt visible after updating GTK+3 to 3.21.5-1

[Viktor Jägersküpper]

Hello Adrian,

I created a new user, opened mate-terminal, everything seemed ok, then
set the theme to "TraditionalOk" which I used with my standard user and
the bug appeared again. I also purged and reinstalled mate-terminal
after that. Then I played around with the themes. With "High contrast",
"TraditionalGreen" and "TraditionalOk" the command line prompt is not
displayed, so it could be a bug in mate-themes. However, in all other
themes the font colour is white and the background is grey (is this
standard?). When I want to change this, mate-terminal crashes (see bug
836239). So with the three themes mentioned mate-terminal is not really
usable for me.

Viktor

Bug#835650: Imagemagick regression pin point patch

[Frank Heckenbach]

> On Wed, Aug 31, 2016 at 8:42 AM, Bastien ROUCARIES
>  wrote:
>
> > Patches are needed for a security point of view but it is likely a
> > problem of backport intereaction.
> >
> > Could you help by pin point the problem.
> >
> > as root install a few package needed for imagemagick compilation:
> > apt-get install git
> > apt-get build-dep imagemagick

Just for my reference:
libbz2-dev libdjvulibre-dev libexif-dev libharfbuzz-dev libharfbuzz-gobject0 
libilmbase-dev libjasper-dev libjbig-dev liblcms2-dev liblqr-1-0-dev 
liblzma-dev libopenexr-dev libpango1.0-dev libperl-dev libtiff5-dev libtiffxx5 
libwmf-dev pkg-kde-tools xsltproc

> > as a user
> >  git clone   git://git.debian.org/git/collab-maint/imagemagick.git
> > cd imagemagick
>
> HERE run
> git checkout debian-patches/6.8.9.9-5+deb8u3
> 
> > git checkout debian-patches/6.8.9.9-5+deb8u4

So I ran both (first +deb8u3, then +deb8u4), right?
(Otherwise, +deb8u3 would be the same as in "good" below.)

> > git bisect start
> > git bisect bad
> > git bissect good debian-patches/6.8.9.9-5+deb8u3
> >
> >   Once you have specified at least one bad and one good commit, git
> > bisect selects a commit in the middle of that range of history, checks
> > it out, and outputs something similar to the following:
> >
> >Bisecting: 675 revisions left to test after this (roughly 10 
> > steps)
> >
> >  You should now compile the checked-out version and test it. If that
> > version works correctly, type. Compiling is done by typing
> > ./configure
> > make check

That already gave an error (see test-suite.log). (I first ran make
with "-j16", then reran "make check" (but didn't rebuild) without
"-j", same result.) I'll be ignoring this (and further test-suite
errors I got while bisecting).

> > you could run the command without installing by runing the convert.sh 
> > wrapper
> > ./magick.sh convert geometry 40% tux.png tux-scaled-old.ppm
> >
> > if bad run
> > git bisect bad
> > and rerun compile and testing
> > if good run
> > git bisect good
> >
> > Some pointer could be found in man git bisect

26d910675e0cd1b62e988139dba8eb11931260ac is the first bad commit
commit 26d910675e0cd1b62e988139dba8eb11931260ac
Author: Cristy 
Date:   Sat Jan 30 09:37:10 2016 -0500

Fix out of bound in quantum handling

Bug: https://github.com/ImageMagick/ImageMagick/issues/105
bug-ubuntu: 
https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1539053
origin: upstream, 
https://github.com/ImageMagick/ImageMagick/commit/c4e63ad30bc42da691f2b5f82a24516dd6b4dc70
bug-debian: https://bugs.debian.org/832506

:04 04 41e16d89455879892777d50135af38993b5be722 
e841bf15b62dee866b54eab729a93163d85aee68 M  magick

git diff 3e07cd10a9a2215c9edcc0c0e1541c125371cfbc 
26d910675e0cd1b62e988139dba8eb11931260ac
shows that the change essentially replaced image->columns by
MagickMax(image->columns,image->rows) in several places. This might
explain why the bug only occurs with portrait. I see that some
callers of GetQuantumExtent() use its result as the length parameter
to ReadBlob and similar, so it seems strange to use the max of width
and height here. Others callers might use it for a work buffer where
this might be correct (and probably what the change was meant to
fix), but it might be necessary to separate those two cases.

Frank


test-suite.log.bz2
Description: Binary data

Bug#829520: RFS: mbpfan/1.9.1-1 ITP

[Herminio Hernandez, Jr.]

will do apologies

On Wed, Aug 31, 2016 at 2:43 PM, Sean Whitton 
wrote:

> Dear Herminio,
>
> [please CC the RFS so that your e-mail gets recorded and others can
> provide feedback as well as me -- use reply-to-all]
>
> On Tue, Aug 30, 2016 at 10:23:09PM -0700, Herminio Hernandez, Jr. wrote:
> > I have combined the patches using combinediff. I know you want me to
> convert to
> > git. Can you recommend good documentation to convert my package? Thanks!
>
> One easy way is to do this:
>
> apt-get install git-buildpackage
> gbp import-dsc mbpfan_1.9.1-1.dsc
>
> --
> Sean Whitton
>

Bug#836236: prosody: doesn't try IPv4 when IPv6 fails

[Cyril Brulebois]

Cyril Brulebois  (2016-09-01):
> Hi Matthew,
> 
> Matthew Wild  (2016-08-31):
> > Thanks for the report. Can you please bump your log level up to
> > 'debug' (there should be comments in your config file explaining how
> > to do this), and include those logs? The 'info' level logs tend to
> > give a high-level approximate view of issues, but only the debug logs
> > can be relied upon when debugging the low-level individual connection
> > attempts.
> 
> This is very strange. While crans.org was still without IPv6, a simple
> restart locally made prosody look at both IPv6 (fail) and IPv4
> (success). I wonder whether something might have been stuck in a bad
> state within prosody after the initial DNS resolution failures which
> happened for various domains…
> 
> Needless to say, I can't really replicate the issue right now, except
> perhaps by rebooting again (which I can't really since I've got ongoing
> maintenance elsewhere already). I would also need to remove things like
> contact presence information from those logs before posting them…

Just in case it helps you figure out what could have happened, messages
right after reboot for this host:
| Aug 31 02:09:46 s2soutf30410infoBeginning new connection attempt to 
crans.org ([2a01:240:fe3d:4:200:42ff:fe42:4204]:5269)
| Aug 31 02:09:46 mod_s2s warns2s connect() to crans.org 
(2a01:240:fe3d:4:200:42ff:fe42:4204:5269) failed: Network is unreachable
| Aug 31 02:09:46 s2soutf30410infoOut of connection options, can't 
connect to crans.org
| Aug 31 02:09:46 s2soutf30410infoSending error replies for 1 queued 
stanzas because of failed outgoing connection to crans.org
| Aug 31 02:09:46 mod_s2s warnConnection to crans.org failed already, 
destroying session...

Also, a bunch of other hostnames had such issues:
| Aug 31 02:11:27 s2sout1007a70   infoConnection failed (name resolution 
failed). Attempt #2: This time to alt2.xmpp-server.l.google.com.:5269
| Aug 31 02:11:27 s2sout1007a70   infoConnection failed (name resolution 
failed). Attempt #3: This time to alt4.xmpp-server.l.google.com.:5269
| Aug 31 02:11:27 s2sout1007a70   infoConnection failed (name resolution 
failed). Attempt #4: This time to alt3.xmpp-server.l.google.com.:5269
| Aug 31 02:11:27 s2sout1007a70   infoConnection failed (name resolution 
failed). Attempt #5: This time to alt1.xmpp-server.l.google.com.:5269
| Aug 31 02:11:27 s2sout1007a70   infoOut of connection options, can't 
connect to [anotherserver]
| Aug 31 02:11:27 s2sout1007a70   infoSending error replies for 1 queued 
stanzas because of failed outgoing connection to [anotherserver]

so I'm wondering whether there could have been incomplete DNS
resolution(s) at start-up time, which would not have been attempted
again later, leading me to see some contacts offline with “DNS failures”
as error message in Gajim.

After the prosody restart I triggered manually:
| Aug 31 23:37:49 s2sout231c500   infoBeginning new connection attempt to 
crans.org ([2a01:240:fe3d:4:200:42ff:fe42:4204]:5269)
| Aug 31 23:37:49 s2sout231c500   infoBeginning new connection attempt to 
crans.org ([138.231.136.66]:5269)
| Aug 31 23:37:49 s2sout231c500   infooutgoing s2s connection 
mraw.org->crans.org complete

Incidentally, looking at the IPv4 address for crans.org in the log since
the machine reboot, the first occurrence is when I restarted prosody
manually.

So it looks to me like it could be an initial DNS issue (partial and/or
no resolution depending on the domain) which happened at start-up time,
and failed/incomplete resolutions weren't attempted again later on.

Would this seem even remotely plausible?


KiBi.


signature.asc
Description: Digital signature

Bug#828082: Acknowledgement (bind9: FTBFS with openssl 1.1)

[Kurt Roeckx]

On Thu, Sep 01, 2016 at 12:07:07AM +0200, Kurt Roeckx wrote:
> Hi,
> 
> Here is a patch that I think should solve the issue.

The patch was also send upstream.


Kurt

Bug#836243: vmdebootstrap: Releases which are recognised by Debootstrap are not always recognised by Vmdebootstrap

[Will Holland]

Package: vmdebootstrap
Version: 1.6-1
Severity: wishlist
Tags: patch

Dear Maintainer,

Debootstrap allows releases which are not in Debian or Ubuntu if a config file
with the same name is in /usr/share/debootstrap/scripts. On the other hand,
vmdebootstrap will fail if the specified distribution is not recognised as
being in Debian or Ubuntu.

A potential solution to this would be to have an option to specify where 
debootstrap scripts are and then check if the distribution option is the name 
of a script there, as in the patch I put here

https://github.com/williamholland/vmdebootstrap/commit/509c9fa7943954285c632057b09d782b6c59a328

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

Kernel: Linux 3.16.0-4-amd64
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=locale: Cannot set 
LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages vmdebootstrap depends on:
ii  debootstrap 1.0.81
ii  kpartx  0.6.2-2
ii  libjs-sphinxdoc 1.4.5-1
ii  parted  3.2-15
ii  python-cliapp   1.20160724-1
ii  python-distro-info  0.14
ii  python2.7   2.7.12-2
pn  python:any  
ii  qemu-utils  1:2.6+dfsg-3

Versions of packages vmdebootstrap recommends:
ii  dosfstools4.0-2
ii  extlinux  3:6.03+dfsg-14
ii  grub2-common  2.02~beta2-36
ii  python-guestfs1:1.32.7-1
ii  qemu-system   1:2.6+dfsg-3
ii  qemu-user-static  1:2.6+dfsg-3
ii  squashfs-tools1:4.3-3

Versions of packages vmdebootstrap suggests:
pn  cmdtest   
pn  mbr   
pn  pandoc
pn  u-boot:armhf  

-- debconf information excluded

Bug#811684: [NMU] Re: Bug#811684: FTBFS with GCC 6: enumerator value for... is not

[Axel Beckert]

Control: tag -1 + pending

Dear Hector,

Axel Beckert wrote:
> > > compilation terminated due to -Wfatal-errors.
> > > Makefile:379: recipe for target 'mssh.o' failed
> 
> This can be workarounded by removing the pedantic errors flags from CFLAGS:
> 
> --- a/src/Makefile.am
> +++ b/src/Makefile.am
> @@ -1,4 +1,4 @@
> -AM_CFLAGS = -pedantic-errors -Werror -Wall -Wfatal-errors -Wwrite-strings
> +AM_CFLAGS = -Wall -Wfatal-errors -Wwrite-strings
>  
>  AM_CPPFLAGS = $(MSSH_CFLAGS)
>  
> With this patch, mssh builds fine for me. (Patch inspired by the one
> for 1.2.4 QA upload and hence removes "-Werror", too.)

I've just uploaded an NMU with this fix to DELAYED/2. Full source
debdiff attached. Feel free to tell me if I should fast-forward it or
delay it longer.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://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
diff -Nru mssh-2.2/debian/changelog mssh-2.2/debian/changelog
--- mssh-2.2/debian/changelog   2015-06-10 10:35:13.0 +0200
+++ mssh-2.2/debian/changelog   2016-09-01 00:11:23.0 +0200
@@ -1,3 +1,11 @@
+mssh (2.2-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add patch to disable pedantic errors. Works around FTBFS with GCC 6.
+(Closes: #811684)
+
+ -- Axel Beckert   Thu, 01 Sep 2016 00:11:23 +0200
+
 mssh (2.2-1) unstable; urgency=low
 
   * New upstream version
diff -Nru mssh-2.2/debian/patches/disable-pedantic-errors.patch 
mssh-2.2/debian/patches/disable-pedantic-errors.patch
--- mssh-2.2/debian/patches/disable-pedantic-errors.patch   1970-01-01 
01:00:00.0 +0100
+++ mssh-2.2/debian/patches/disable-pedantic-errors.patch   2016-09-01 
00:02:49.0 +0200
@@ -0,0 +1,12 @@
+Description: Disable pedantic errors to fix FTBFS with GCC 6
+Author: Axel Beckert 
+Bug-Debian: https://bugs.debian.org/811684
+
+--- a/src/Makefile.am
 b/src/Makefile.am
+@@ -1,4 +1,4 @@
+-AM_CFLAGS = -pedantic-errors -Werror -Wall -Wfatal-errors -Wwrite-strings
++AM_CFLAGS = -Werror -Wall -Wfatal-errors -Wwrite-strings
+ 
+ AM_CPPFLAGS = $(MSSH_CFLAGS)
+ 
diff -Nru mssh-2.2/debian/patches/series mssh-2.2/debian/patches/series
--- mssh-2.2/debian/patches/series  2015-06-09 13:21:20.0 +0200
+++ mssh-2.2/debian/patches/series  2016-09-01 00:01:04.0 +0200
@@ -0,0 +1 @@
+disable-pedantic-errors.patch


signature.asc
Description: Digital signature

Bug#836242: ITP: python-pytz -- World timezone definitions, modern and historical

[Sebastian Ramacher]

On 2016-08-31 23:58:09, IOhannes m zmoelnig wrote:
> Package: wnpp
> Severity: wishlist
> Owner: IOhannes m zmölnig (Debian/GNU) 
> 
> * Package name: python-pytz
>   Version : 2016.6.1
>   Upstream Author : Stuart Bishop 
> * URL : http://pythonhosted.org/pytz
> * License : MIT
>   Programming Lang: Python
>   Description : World timezone definitions, modern and historical
> 
>  pytz brings the Olson tz database into Python. This library allows
>  accurate and cross platform timezone calculations using Python 2.4
>  or higher. It also solves the issue of ambiguous times at the end
>  of daylight saving time, which you can read more about in the Python
>  Library Reference (``datetime.tzinfo``).
> 
> Binary package names: python-pytz python3-pytz
> I intend to maintain this package under the Python Modules Team umbrella.

Already packaged as python-tz: https://tracker.debian.org/pkg/python-tz.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#776171: same problem

[Fabien]

Same problem occured to me (just after "apt-get upgrade", trying to reboot the 
system). 

Please also see this link: 
 
http://unix.stackexchange.com/questions/274761/debian-wont-shut-down-failed-to-start-poweroff-target-transaction-is-destruct
 

Someone there says that killing the "systemd-sleep" process can help. When I 
tried, my system went to sleep immediately. When I resumed it, it went back to 
life but the screen stayed black (I had quit my desktop session and even 
stopped my desktop manager, so I was on a console, no GUI was running). I tried 
to type "poweroff" without the screen, it didn't work, but when I hit the power 
button, the machine finally stopped correctly...

Bug#828082: Acknowledgement (bind9: FTBFS with openssl 1.1)

[Kurt Roeckx]

Hi,

Here is a patch that I think should solve the issue.

There appears to be same weird things going on related to native
pkcs11 support that I can't figure out.  Patches get applied at
various stages during the build and some fail to apply.  It
properly detects OpenSSL but then says it's disabled.  I have no
idea what is going on.  But I believe my patch does the right
thing.


Kurt

>From 61399410964d61aec3609a1bc76fd260268b3ade Mon Sep 17 00:00:00 2001
From: Kurt Roeckx 
Date: Wed, 31 Aug 2016 23:00:39 +0200
Subject: [PATCH] Add OpenSSL 1.1.0 support

---
 configure.in|   6 +-
 lib/dns/openssl_link.c  |  38 ---
 lib/dns/openssldh_link.c| 255 +---
 lib/dns/openssldsa_link.c   | 170 +
 lib/dns/opensslecdsa_link.c |  31 --
 lib/dns/opensslrsa_link.c   | 246 ++
 lib/isc/aes.c   |  36 +++
 8 files changed, 554 insertions(+), 248 deletions(-)

Index: bind9-9.10.3.dfsg.P4/configure.in
===
--- bind9-9.10.3.dfsg.P4.orig/configure.in
+++ bind9-9.10.3.dfsg.P4/configure.in
@@ -1546,15 +1546,13 @@ shared library configuration (e.g., LD_L
 		AC_MSG_CHECKING(whether linking with OpenSSL requires -ldl)
 		AC_TRY_LINK([
 #include 
-#include 
 ],
-[ DSO_METHOD_dlfcn(); ],
+[ ERR_clear_error(); ],
 		[AC_MSG_RESULT(no)],
 		[LIBS="$LIBS -ldl"
 		AC_TRY_LINK([
 #include 
-#include 
-],[ DSO_METHOD_dlfcn(); ],
+],[ ERR_clear_error(); ],
 		[AC_MSG_RESULT(yes)
 		DST_OPENSSL_LIBS="$DST_OPENSSL_LIBS -ldl"
 		],
Index: bind9-9.10.3.dfsg.P4/lib/dns/openssl_link.c
===
--- bind9-9.10.3.dfsg.P4.orig/lib/dns/openssl_link.c
+++ bind9-9.10.3.dfsg.P4/lib/dns/openssl_link.c
@@ -58,8 +58,10 @@
 
 static RAND_METHOD *rm = NULL;
 
+#if OPENSSL_VERSION_NUMBER < 0x1010L
 static isc_mutex_t *locks = NULL;
 static int nlocks;
+#endif
 
 #ifdef USE_ENGINE
 static ENGINE *e = NULL;
@@ -111,6 +113,7 @@ entropy_add(const void *buf, int num, do
 }
 #endif
 
+#if OPENSSL_VERSION_NUMBER < 0x1010L
 static void
 lock_callback(int mode, int type, const char *file, int line) {
 	UNUSED(file);
@@ -120,6 +123,7 @@ lock_callback(int mode, int type, const
 	else
 		UNLOCK([type]);
 }
+#endif
 
 #if OPENSSL_VERSION_NUMBER < 0x1010L
 static unsigned long
@@ -129,7 +133,11 @@ id_callback(void) {
 #endif
 
 static void *
+#if OPENSSL_VERSION_NUMBER < 0x1010L
 mem_alloc(size_t size) {
+#else
+mem_alloc(size_t size, const char *file, int line) {
+#endif
 #ifdef OPENSSL_LEAKS
 	void *ptr;
 
@@ -143,14 +151,22 @@ mem_alloc(size_t size) {
 }
 
 static void
+#if OPENSSL_VERSION_NUMBER < 0x1010L
 mem_free(void *ptr) {
+#else
+mem_free(void *ptr, const char *file, int line) {
+#endif
 	INSIST(dst__memory_pool != NULL);
 	if (ptr != NULL)
 		isc_mem_free(dst__memory_pool, ptr);
 }
 
 static void *
+#if OPENSSL_VERSION_NUMBER < 0x1010L
 mem_realloc(void *ptr, size_t size) {
+#else
+mem_realloc(void *ptr, size_t size, const char *file, int line) {
+#endif
 #ifdef OPENSSL_LEAKS
 	void *rptr;
 
@@ -179,6 +195,7 @@ dst__openssl_init(const char *engine) {
 	CRYPTO_mem_ctrl(CRYPTO_MEM_CHECK_ON);
 #endif
 	CRYPTO_set_mem_functions(mem_alloc, mem_realloc, mem_free);
+#if OPENSSL_VERSION_NUMBER < 0x1010L
 	nlocks = CRYPTO_num_locks();
 	locks = mem_alloc(sizeof(isc_mutex_t) * nlocks);
 	if (locks == NULL)
@@ -187,13 +204,12 @@ dst__openssl_init(const char *engine) {
 	if (result != ISC_R_SUCCESS)
 		goto cleanup_mutexalloc;
 	CRYPTO_set_locking_callback(lock_callback);
-#if OPENSSL_VERSION_NUMBER < 0x1010L
 	CRYPTO_set_id_callback(id_callback);
 #endif
 
 	ERR_load_crypto_strings();
 
-	rm = mem_alloc(sizeof(RAND_METHOD));
+	rm = malloc(sizeof(RAND_METHOD));
 	if (rm == NULL) {
 		result = ISC_R_NOMEMORY;
 		goto cleanup_mutexinit;
@@ -250,11 +266,13 @@ dst__openssl_init(const char *engine) {
 	rm = NULL;
 #endif
  cleanup_mutexinit:
+#if OPENSSL_VERSION_NUMBER < 0x1010L
 	CRYPTO_set_locking_callback(NULL);
 	DESTROYMUTEXBLOCK(locks, nlocks);
  cleanup_mutexalloc:
 	mem_free(locks);
 	locks = NULL;
+#endif
 	return (result);
 }
 
@@ -267,7 +285,7 @@ dst__openssl_destroy(void) {
 #if OPENSSL_VERSION_NUMBER >= 0x00907000L
 		RAND_cleanup();
 #endif
-		mem_free(rm);
+		free(rm);
 		rm = NULL;
 	}
 #if (OPENSSL_VERSION_NUMBER >= 0x00907000L)
@@ -296,21 +314,20 @@ dst__openssl_destroy(void) {
 	CRYPTO_mem_leaks_fp(stderr);
 #endif
 
+#if OPENSSL_VERSION_NUMBER < 0x1010L
 	if (locks != NULL) {
 		CRYPTO_set_locking_callback(NULL);
 		DESTROYMUTEXBLOCK(locks, nlocks);
 		mem_free(locks);
 		locks = NULL;
 	}
+#endif
 }
 
 static isc_result_t
 toresult(isc_result_t fallback) {
 	isc_result_t result = fallback;
 	unsigned long err = ERR_get_error();
-#ifdef HAVE_OPENSSL_ECDSA
-	int lib = ERR_GET_LIB(err);
-#endif
 	int reason = ERR_GET_REASON(err);
 
 	

Bug#836236: prosody: doesn't try IPv4 when IPv6 fails

[Cyril Brulebois]

Hi Matthew,

Matthew Wild  (2016-08-31):
> Thanks for the report. Can you please bump your log level up to
> 'debug' (there should be comments in your config file explaining how
> to do this), and include those logs? The 'info' level logs tend to
> give a high-level approximate view of issues, but only the debug logs
> can be relied upon when debugging the low-level individual connection
> attempts.

This is very strange. While crans.org was still without IPv6, a simple
restart locally made prosody look at both IPv6 (fail) and IPv4
(success). I wonder whether something might have been stuck in a bad
state within prosody after the initial DNS resolution failures which
happened for various domains…

Needless to say, I can't really replicate the issue right now, except
perhaps by rebooting again (which I can't really since I've got ongoing
maintenance elsewhere already). I would also need to remove things like
contact presence information from those logs before posting them…


KiBi.


signature.asc
Description: Digital signature

Bug#836242: ITP: python-pytz -- World timezone definitions, modern and historical

[IOhannes m zmoelnig]

Package: wnpp
Severity: wishlist
Owner: IOhannes m zmölnig (Debian/GNU) 

* Package name: python-pytz
  Version : 2016.6.1
  Upstream Author : Stuart Bishop 
* URL : http://pythonhosted.org/pytz
* License : MIT
  Programming Lang: Python
  Description : World timezone definitions, modern and historical

 pytz brings the Olson tz database into Python. This library allows
 accurate and cross platform timezone calculations using Python 2.4
 or higher. It also solves the issue of ambiguous times at the end
 of daylight saving time, which you can read more about in the Python
 Library Reference (``datetime.tzinfo``).

Binary package names: python-pytz python3-pytz
I intend to maintain this package under the Python Modules Team umbrella.

Bug#836236: prosody: doesn't try IPv4 when IPv6 fails

[Matthew Wild]

Hi Cyril,

Thanks for the report. Can you please bump your log level up to
'debug' (there should be comments in your config file explaining how
to do this), and include those logs? The 'info' level logs tend to
give a high-level approximate view of issues, but only the debug logs
can be relied upon when debugging the low-level individual connection
attempts.

Thanks!

On 31 August 2016 at 22:16, Cyril Brulebois  wrote:
> Package: prosody
> Version: 0.9.7-2+deb8u3
> Severity: normal
>
> Hi,
>
> My server is trying to initiate a connection to crans.org, which has the
> following DNS bits set up:
> | _xmpp-server._tcp.crans.org. 466 IN   SRV 5 0 5269 xmpp.crans.org.
> |
> | xmpp.crans.org.   466 IN  A   138.231.136.66
> | xmpp.crans.org.   466 IN  
> 2a01:240:fe3d:4:200:42ff:fe42:4204
>
> Logs say:
> | Aug 31 23:02:18 s2soute11b40infoBeginning new connection attempt to 
> crans.org ([2a01:240:fe3d:4:200:42ff:fe42:4204]:5269)
> | Aug 31 23:02:18 s2soute11b40infoOut of connection options, can't 
> connect to crans.org
> | Aug 31 23:02:18 s2soute11b40infoSending error replies for 1 queued 
> stanzas because of failed outgoing connection to crans.org
>
> which is fair enough because:
>  - trying IPv6 first is the right thing to do;
>  - this port appears closed on IPv6 at the time of writing.
>
> But prosody should move to trying a connection on IPv4 instead of simply
> giving up and trying again a moment later.
>
> Thanks for your time.
>
>
> KiBi.

Bug#836228: fix build with ld --as-needed as the default

[Daniel Kahn Gillmor]

Control: tags 836228 + upstream pending

On Wed 2016-08-31 15:14:47 -0400, Matthias Klose wrote:
> Package: src:monkeysphere
> Version: 0.39-1
> Severity: important
> Tags: patch sid stretch
>
> this fixes the build when ld --as-needed is the default behaviour.
>
> patch at
> http://launchpadlibrarian.net/281962610/monkeysphere_0.39-1_0.39-1ubuntu1.diff.gz

Thanks, i've applied a minor variant of this upstream and attributed it
to you.  It'll be in the next release of Monkeysphere (0.40), whenever
that happens.

 --dkg


signature.asc
Description: PGP signature

Bug#835457: how-can-i-help doesn't list some package(s)

[Tomasz Nitecki]

Hey,

On 29/08/16 18:39, Adrian Bunk wrote:
> On Mon, Aug 29, 2016 at 04:25:10PM +0200, Tomasz Nitecki wrote:
>> Adrian, the reason why usbmount is not showing up, is a 1 year time
>> limit counted from the date of removal (line 90 at [1]).
> 
> if it stays that way, it should be documented in the manpage.

I agree. If I leave any time limitation for this opportunity type, I
will add an appropriate information to the manpage.



>> 
> 
> So the benefit of the one-year limit is not really big.
> 
> A few hundred lines more or less in "how-can-i-help --all --old" 
> output wouldn't make a difference.
> 
> "--all --old" is atually much less useful when it is incomplete.
> 
> And the output of "how-can-i-help --old" (without --all) should really 
> list *all* packages I have installed that are in unstable but not in 
> testing. Currently I am getting 17 packages under "removed from testing" 
> on my computer, but any packages (no matter whether I installed them
> recently or many years ago) that were remove from testing more than
> a year ago are not shown.

I gave it some though, and I also agree. I will check if this won't
affect the dump generation time and if it's ok, I'll just remove the
limit altogether.


Regards,
T.




signature.asc
Description: OpenPGP digital signature

Bug#836241: plasma-workspace: Digital clock widget wants qml-module-org-kde-kholidays

[Ignacio R. Morelle]

Package: plasma-workspace
Version: 4:5.7.4-1
Severity: normal

As of the latest upload of Plasma 5.7.4 to unstable, the digital clock widget
requires qml-module-org-kde-kholidays to be installed to provide holiday-
related options in its configuration window. Not having the package installed
results in the Holidays config tab being missing and displaying an error:

  Error: Could not load: file:///usr/lib/x86_64-linux-
gnu/qt5/plugins/plasmacalendarplugins/holidays/HolidaysConfig.qml:29 module
"org.kde.kholidays" is not installed

According to apt-cache rdepends, nothing depends on qml-module-org-kde-
kholidays at the moment other than its debug symbols.



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

Kernel: Linux 4.6.7-nanacore-116 (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 plasma-workspace depends on:
ii  dbus-x11 1.10.10-1
ii  frameworkintegration 5.25.0-1
ii  gdb  7.11.1-2
ii  kde-cli-tools4:5.7.4-1
ii  kded55.25.0-1
ii  kinit5.25.0-1
ii  kio  5.25.0-1
ii  kpackagetool55.25.0-1
ii  libc62.23-5
ii  libcln6  1.3.4-1
ii  libdbusmenu-qt5-20.9.3+16.04.20160218-1
ii  libgcc1  1:6.1.1-11
ii  libgps22 3.16-2
ii  libice6  2:1.0.9-1+b1
ii  libkf5activities55.25.0-1
ii  libkf5auth5  5.25.0-1
ii  libkf5baloo5 5.25.0-1
ii  libkf5bookmarks5 5.25.0-1
ii  libkf5calendarevents55.25.0-1
ii  libkf5completion55.25.0-1
ii  libkf5configcore55.25.0-1
ii  libkf5configgui5 5.25.0-1
ii  libkf5configwidgets5 5.25.0-1
ii  libkf5coreaddons55.25.0-1
ii  libkf5crash5 5.25.0-1
ii  libkf5dbusaddons55.25.0-1
ii  libkf5declarative5   5.25.0-1
ii  libkf5globalaccel-bin5.25.0-1
ii  libkf5globalaccel5   5.25.0-1
ii  libkf5guiaddons5 5.25.0-1
ii  libkf5holidays5  16.04.2-1
ii  libkf5i18n5  5.25.0-1
ii  libkf5iconthemes55.25.0-1
ii  libkf5idletime5  5.25.0-1
ii  libkf5itemviews5 5.25.0-1
ii  libkf5jobwidgets55.25.0-1
ii  libkf5js55.25.0-1
ii  libkf5jsembed5   5.25.0-2
ii  libkf5kdelibs4support5   5.25.0-1
ii  libkf5kiocore5   5.25.0-1
ii  libkf5kiofilewidgets55.25.0-1
ii  libkf5kiowidgets55.25.0-1
ii  libkf5networkmanagerqt6  5.25.0-1
ii  libkf5newstuff5  5.25.0-1
ii  libkf5notifications5 5.25.0-1
ii  libkf5notifyconfig5  5.25.0-1
ii  libkf5package5   5.25.0-1
ii  libkf5plasma55.25.0-1
ii  libkf5plasmaquick5   5.25.0-1
ii  libkf5quickaddons5   5.25.0-1
ii  libkf5runner55.25.0-1
ii  libkf5service-bin5.25.0-1
ii  libkf5service5   5.25.0-1
ii  libkf5solid5 5.25.0-1
ii  libkf5texteditor55.25.0-1
ii  libkf5textwidgets5   5.25.0-1
ii  libkf5wallet-bin 5.25.0-1
ii  libkf5wallet55.25.0-1
ii  libkf5waylandclient5 4:5.25.0-1
ii  libkf5widgetsaddons5 5.25.0-1
ii  libkf5windowsystem5  5.25.0-1
ii  libkf5xmlgui55.25.0-1
ii  libkf5xmlrpcclient5  5.25.0-1
ii  libkscreenlocker55.7.4-1
ii  libksgrd74:5.7.4-1
ii  libkworkspace5-5 4:5.7.4-1
ii  liblegacytaskmanager54:5.7.4-1
ii  libphonon4qt5-4  4:4.9.0-4
ii  libplasma-geolocation-interface5 4:5.7.4-1
ii  libprocesscore7  4:5.7.4-1
ii  libprocessui7

Bug#836240: osmium: FTBFS: Checking geometry/test_haversine.cpp...Segmentation fault (core dumped)

[Chris Lamb]

Source: osmium
Version: 0.0~20160425-e2e4368-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

osmium fails to build from source in unstable/amd64:

  [..]

  Setting up libsm-dev:amd64 (2:1.2.2-1+b1) ...
  Setting up libpoppler-dev:amd64 (0.44.0-3) ...
  Setting up libxpm-dev:amd64 (1:3.5.11-1+b1) ...
  Setting up libgd3:amd64 (2.2.3-3+b1) ...
  Setting up libkmlconvenience1:amd64 (1.3.0-3) ...
  Setting up libhdf4-alt-dev (4.2.12-1) ...
  Setting up libogdi3.2-dev (3.2.0+ds-1) ...
  Setting up libkmlregionator1:amd64 (1.3.0-3) ...
  Setting up libarpack2-dev (3.4.0-1) ...
  Setting up libarmadillo-dev (1:6.700.6+dfsg-1) ...
  Setting up libxt-dev:amd64 (1:1.1.5-1) ...
  Setting up libpoppler-private-dev:amd64 (0.44.0-3) ...
  Setting up libkml-dev:amd64 (1.3.0-3) ...
  Setting up libgd-dev:amd64 (2.2.3-3+b1) ...
  Setting up odbcinst1debian2:amd64 (2.3.1-4.1) ...
  Setting up odbcinst (2.3.1-4.1) ...
  Setting up libgdal20 (2.1.1+dfsg-1+b1) ...
  Setting up unixodbc (2.3.1-4.1) ...
  Setting up unixodbc-dev (2.3.1-4.1) ...
  Setting up libgdal-dev (2.1.1+dfsg-1+b1) ...
  Setting up osmium-build-deps (0.0~20160425-e2e4368-2) ...
  Processing triggers for libc-bin (2.23-5) ...
  Processing triggers for systemd (231-5) ...
  
  
**
  ** Environment
  **
  
**
  
  
PATH=/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  HOSTNAME=931c7fe3a226
  TERM=xterm
  PAGER=more
  DISPLAY=:0
  DOCKER_IMAGE=lamby-debian-sid
  DEB_BUILD_OPTIONS=parallel=9
  PIP_DOWNLOAD_CACHE=/home/lamby/.cache/pip
  HOME=/home/lamby
  LOGNAME=lamby
  SHLVL=1
  
PWD=/home/lamby/temp/cdt.20160831221852.xvL6EupPhb.db.osmium/osmium-0.0~20160425-e2e4368
  OLDPWD=/home/lamby/temp/cdt.20160831221852.xvL6EupPhb.db.osmium
  GPG_TTY=/dev/console
  QUILT_PATCHES=debian/patches
  QUILT_NO_DIFF_INDEX=1
  QUILT_REFRESH_ARGS=-p ab --no-timestamps --no-index
  DEBEMAIL=la...@debian.org
  DEBFULLNAME=Chris Lamb
  EDITOR=vim
  LESS=-cgiFx4M
  GPG_KEY=1E953E27D4311E58
  BLASTER=A220 I5 D1 H5 P330 T6
  _=/usr/bin/env
  
  
**
  ** Building osmium 0.0~20160425-e2e4368-2 on amd64
  **
  
**
  
   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: info: source package osmium
  dpkg-buildpackage: info: source version 0.0~20160425-e2e4368-2
  dpkg-buildpackage: info: source distribution unstable
  dpkg-buildpackage: info: source changed by Bas Couwenberg 

   dpkg-source --before-build osmium-0.0~20160425-e2e4368
  dpkg-buildpackage: info: host architecture amd64
   fakeroot debian/rules clean
  dh clean --parallel
 dh_testdir -O--parallel
 debian/rules override_dh_auto_clean
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160831221852.xvL6EupPhb.db.osmium/osmium-0.0~20160425-e2e4368'
  dh_auto_clean
make -j9 clean
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20160831221852.xvL6EupPhb.db.osmium/osmium-0.0~20160425-e2e4368'
  #rm -fr check-includes-report doc/html
  rm -fr check-includes-report
  make -C test clean
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160831221852.xvL6EupPhb.db.osmium/osmium-0.0~20160425-e2e4368/test'
  find . -name "*.o" -exec rm {} ";"
  find . -name "*.ocov" -exec rm {} ";"
  find . -name "*.gcda" -exec rm {} ";"
  find . -name "*.gcno" -exec rm {} ";"
  rm -rf coverage gcov tests.info test_main test_main_cov tests
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160831221852.xvL6EupPhb.db.osmium/osmium-0.0~20160425-e2e4368/test'
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160831221852.xvL6EupPhb.db.osmium/osmium-0.0~20160425-e2e4368'
  dh_auto_clean -Dosmjs
make -j9 clean
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20160831221852.xvL6EupPhb.db.osmium/osmium-0.0~20160425-e2e4368/osmjs'
  rm -f *.o core osmjs
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160831221852.xvL6EupPhb.db.osmium/osmium-0.0~20160425-e2e4368/osmjs'
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160831221852.xvL6EupPhb.db.osmium/osmium-0.0~20160425-e2e4368'
 dh_clean -O--parallel
   debian/rules build
  dh build --parallel
 dh_testdir -O--parallel
 dh_update_autotools_config -O--parallel
 dh_auto_configure -O--parallel
 debian/rules override_dh_auto_build
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160831221852.xvL6EupPhb.db.osmium/osmium-0.0~20160425-e2e4368'
  

Bug#829520: RFS: mbpfan/1.9.1-1 ITP

[Sean Whitton]

Dear Herminio,

[please CC the RFS so that your e-mail gets recorded and others can
provide feedback as well as me -- use reply-to-all]

On Tue, Aug 30, 2016 at 10:23:09PM -0700, Herminio Hernandez, Jr. wrote:
> I have combined the patches using combinediff. I know you want me to convert 
> to
> git. Can you recommend good documentation to convert my package? Thanks!

One easy way is to do this:

apt-get install git-buildpackage
gbp import-dsc mbpfan_1.9.1-1.dsc

-- 
Sean Whitton

Bug#836238: no command line prompt visible after updating GTK+3 to 3.21.5-1

[John Paul Adrian Glaubitz]

Hello Viktor!

On 08/31/2016 11:32 PM, Viktor Jägersküpper wrote:
> after updating the GTK+3 packages from version 3.20.9-1 to version
> 3.21.5-1 the command line prompt of mate-terminal is not displayed (just
> white background).

This works here without any problems.

> Please tell me if I should give you more information, maybe how I can
> debug this.

Since you already filed a bug report, I assume you already tried a creating
a new user first and after that didn't help, you did fresh installation to
make sure this isn't a local configuration issue. Am I correct?

Adrian

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

Bug#836237: pyacoustid: update for libchromaprint1

[Sebastian Ramacher]

Control: tags -1 - fixed-upstream patch

On 2016-08-31 23:20:03, Sebastian Ramacher wrote:
> Source: pyacoustid
> Version: 1.1.2-1
> Severity: important
> Tags: sid jessie fixed-upstream patch
> 
> chromaprint in experimental bumped its SONAME to libchromaprint1. Hence
> pyacoustid needs to be updated to look for the new library and the hard-coded
> dependency on libchromaprint0 needs to be changed accordingly.
> 
> Patch for the upstream part is at [1].

This change is already packaged so the only thing left to change is the
hard-coded dependencies.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#828606: xmlsec1: FTBFS with openssl 1.1.0

[Sebastian Andrzej Siewior]

control: tags -1 patch

On 2016-06-26 21:52:11 [-0700], John Belmonte wrote:
> I'll have to upgrade to a newer upstream version.  Looks like this was
> addressed in 1.2.21.

1.2.22 plus the patch attached and it builds again :)

Sebastian
>From 7ab8a4ab41ad6096a5bfbe5937680454abe56b44 Mon Sep 17 00:00:00 2001
From: Sebastian Andrzej Siewior 
Date: Wed, 31 Aug 2016 23:25:37 +0200
Subject: [PATCH] openssl: get it build against openssl 1.1.0 and earlier

Tried to get it done as little intrusive as possible. It compiles
against 1.1.0 and 1.0.2h. Testsuite passes/fails in the same way.

Signed-off-by: Sebastian Andrzej Siewior 
---
 src/openssl/evp.c   | 253 +---
 src/openssl/kt_rsa.c|  41 ---
 src/openssl/openssl11_wrapper.h | 153 
 src/openssl/signatures.c| 112 +++---
 src/openssl/x509vfy.c   |  87 +++---
 5 files changed, 444 insertions(+), 202 deletions(-)
 create mode 100644 src/openssl/openssl11_wrapper.h

diff --git a/src/openssl/evp.c b/src/openssl/evp.c
index 328602bc6335..b83efffa1e5a 100644
--- a/src/openssl/evp.c
+++ b/src/openssl/evp.c
@@ -23,6 +23,7 @@
 #include 
 #include 
 #include 
+#include "openssl11_wrapper.h"
 
 /**
  *
@@ -182,7 +183,7 @@ xmlSecOpenSSLEvpKeyDup(EVP_PKEY* pKey) {
 
 xmlSecAssert2(pKey != NULL, NULL);
 
-ret = CRYPTO_add(>references,1,CRYPTO_LOCK_EVP_PKEY);
+ret = EVP_PKEY_up_ref(pKey);
 if(ret <= 0) {
 xmlSecError(XMLSEC_ERRORS_HERE,
 NULL,
@@ -210,7 +211,7 @@ xmlSecOpenSSLEvpKeyAdopt(EVP_PKEY *pKey) {
 
 xmlSecAssert2(pKey != NULL, NULL);
 
-switch(pKey->type) {
+switch(EVP_PKEY_id(pKey)) {
 #ifndef XMLSEC_NO_RSA
 case EVP_PKEY_RSA:
 data = xmlSecKeyDataCreate(xmlSecOpenSSLKeyDataRsaId);
@@ -296,7 +297,7 @@ xmlSecOpenSSLEvpKeyAdopt(EVP_PKEY *pKey) {
 NULL,
 NULL,
 XMLSEC_ERRORS_R_INVALID_TYPE,
-"evp key type %d not supported", pKey->type);
+"evp key type %d not supported", EVP_PKEY_id(pKey));
 return(NULL);
 }
 
@@ -530,9 +531,9 @@ xmlSecOpenSSLKeyDataDsaGetDsa(xmlSecKeyDataPtr data) {
 xmlSecAssert2(xmlSecKeyDataCheckId(data, xmlSecOpenSSLKeyDataDsaId), NULL);
 
 pKey = xmlSecOpenSSLKeyDataDsaGetEvp(data);
-xmlSecAssert2((pKey == NULL) || (pKey->type == EVP_PKEY_DSA), NULL);
+xmlSecAssert2((pKey == NULL) || (EVP_PKEY_id(pKey) == EVP_PKEY_DSA), NULL);
 
-return((pKey != NULL) ? pKey->pkey.dsa : (DSA*)NULL);
+return pKey ? EVP_PKEY_get0_DSA(pKey) : NULL;
 }
 
 /**
@@ -548,7 +549,7 @@ int
 xmlSecOpenSSLKeyDataDsaAdoptEvp(xmlSecKeyDataPtr data, EVP_PKEY* pKey) {
 xmlSecAssert2(xmlSecKeyDataCheckId(data, xmlSecOpenSSLKeyDataDsaId), -1);
 xmlSecAssert2(pKey != NULL, -1);
-xmlSecAssert2(pKey->type == EVP_PKEY_DSA, -1);
+xmlSecAssert2(EVP_PKEY_id(pKey) == EVP_PKEY_DSA, -1);
 
 return(xmlSecOpenSSLEvpKeyDataAdoptEvp(data, pKey));
 }
@@ -593,9 +594,11 @@ xmlSecOpenSSLKeyDataDsaFinalize(xmlSecKeyDataPtr data) {
 static int
 xmlSecOpenSSLKeyDataDsaXmlRead(xmlSecKeyDataId id, xmlSecKeyPtr key,
 xmlNodePtr node, xmlSecKeyInfoCtxPtr keyInfoCtx) {
-xmlSecKeyDataPtr data;
+xmlSecKeyDataPtr data = NULL;
 xmlNodePtr cur;
-DSA *dsa;
+DSA *dsa = NULL;
+BIGNUM *p = NULL, *q = NULL, *g = NULL;
+BIGNUM *priv_key = NULL, *pub_key = NULL;
 int ret;
 
 xmlSecAssert2(id == xmlSecOpenSSLKeyDataDsaId, -1);
@@ -619,7 +622,7 @@ xmlSecOpenSSLKeyDataDsaXmlRead(xmlSecKeyDataId id, xmlSecKeyPtr key,
 "DSA_new",
 XMLSEC_ERRORS_R_CRYPTO_FAILED,
 XMLSEC_ERRORS_NO_MESSAGE);
-return(-1);
+goto err_cleanup;
 }
 
 cur = xmlSecGetNextElementNode(node->children);
@@ -632,18 +635,17 @@ xmlSecOpenSSLKeyDataDsaXmlRead(xmlSecKeyDataId id, xmlSecKeyPtr key,
 XMLSEC_ERRORS_R_INVALID_NODE,
 "node=%s",
 xmlSecErrorsSafeString(xmlSecNodeDSAP));
-DSA_free(dsa);
-return(-1);
+goto err_cleanup;
 }
-if(xmlSecOpenSSLNodeGetBNValue(cur, &(dsa->p)) == NULL) {
+
+if(xmlSecOpenSSLNodeGetBNValue(cur, ) == NULL) {
 xmlSecError(XMLSEC_ERRORS_HERE,
 xmlSecErrorsSafeString(xmlSecKeyDataKlassGetName(id)),
 "xmlSecOpenSSLNodeGetBNValue",
 XMLSEC_ERRORS_R_XMLSEC_FAILED,
 "node=%s",
 xmlSecErrorsSafeString(xmlSecNodeDSAP));
-DSA_free(dsa);
-return(-1);
+goto err_cleanup;
 }
 cur = xmlSecGetNextElementNode(cur->next);
 
@@ -655,18 +657,16 @@ xmlSecOpenSSLKeyDataDsaXmlRead(xmlSecKeyDataId id, 

Bug#836239: crash when changing the background after updating GTK3 to 3.21.5-1

[Viktor Jägersküpper]

Package: mate-terminal
Version: 1.14.1-1
Severity: important

Dear Maintainer,

after updating the GTK+3 packages from version 3.20.9-1 to version
3.21.5-1 mate-terminal crashes when I change the background from "none"
to whatever I want. Downgrading the GTK+3 packages makes the bug disappear.

Please tell me if I should give you more information, maybe how I can
debug this.

Regards
Viktor



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

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

Versions of packages mate-terminal depends on:
ii  gsettings-desktop-schemas  3.21.4-2
ii  libatk1.0-02.20.0-1
ii  libc6  2.23-5
ii  libcairo-gobject2  1.14.6-1+b1
ii  libcairo2  1.14.6-1+b1
ii  libgdk-pixbuf2.0-0 2.34.0-1
ii  libglib2.0-0   2.49.6-1
ii  libgnutls303.5.3-3
ii  libgtk-3-0 3.21.5-1
ii  libice62:1.0.9-1+b1
ii  libmate-desktop-2-17   1.14.1-1
ii  libpango-1.0-0 1.40.2-1
ii  libpangocairo-1.0-01.40.2-1
ii  libsm6 2:1.2.2-1+b1
ii  libstartup-notification0   0.12-4
ii  libvte-2.91-0  0.44.2-1
ii  libx11-6   2:1.6.3-1
ii  mate-desktop-common1.14.1-1
ii  mate-terminal-common   1.14.1-1
ii  zlib1g 1:1.2.8.dfsg-2+b1

mate-terminal recommends no packages.

mate-terminal suggests no packages.

-- no debconf information

Bug#836238: no command line prompt visible after updating GTK+3 to 3.21.5-1

[Viktor Jägersküpper]

Package: mate-terminal
Version: 1.14.1-1
Severity: important

Dear Maintainer,

after updating the GTK+3 packages from version 3.20.9-1 to version
3.21.5-1 the command line prompt of mate-terminal is not displayed (just
white background). Commands are executed although they are not visible.
Downgrading the GTK+3 packages makes the bug disappear.

Please tell me if I should give you more information, maybe how I can
debug this.

Regards
Viktor



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

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

Versions of packages mate-terminal depends on:
ii  gsettings-desktop-schemas  3.21.4-2
ii  libatk1.0-02.20.0-1
ii  libc6  2.23-5
ii  libcairo-gobject2  1.14.6-1+b1
ii  libcairo2  1.14.6-1+b1
ii  libgdk-pixbuf2.0-0 2.34.0-1
ii  libglib2.0-0   2.49.6-1
ii  libgnutls303.5.3-3
ii  libgtk-3-0 3.21.5-1
ii  libice62:1.0.9-1+b1
ii  libmate-desktop-2-17   1.14.1-1
ii  libpango-1.0-0 1.40.2-1
ii  libpangocairo-1.0-01.40.2-1
ii  libsm6 2:1.2.2-1+b1
ii  libstartup-notification0   0.12-4
ii  libvte-2.91-0  0.44.2-1
ii  libx11-6   2:1.6.3-1
ii  mate-desktop-common1.14.1-1
ii  mate-terminal-common   1.14.1-1
ii  zlib1g 1:1.2.8.dfsg-2+b1

mate-terminal recommends no packages.

mate-terminal suggests no packages.

-- no debconf information

Bug#836237: pyacoustid: update for libchromaprint1

[Sebastian Ramacher]

Source: pyacoustid
Version: 1.1.2-1
Severity: important
Tags: sid jessie fixed-upstream patch

chromaprint in experimental bumped its SONAME to libchromaprint1. Hence
pyacoustid needs to be updated to look for the new library and the hard-coded
dependency on libchromaprint0 needs to be changed accordingly.

Patch for the upstream part is at [1].

Cheers

[1] 
https://github.com/beetbox/pyacoustid/commit/56baf698bbb38fc97408ef9a6ab2cf53588e52f7
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#836236: prosody: doesn't try IPv4 when IPv6 fails

[Cyril Brulebois]

Package: prosody
Version: 0.9.7-2+deb8u3
Severity: normal

Hi,

My server is trying to initiate a connection to crans.org, which has the
following DNS bits set up:
| _xmpp-server._tcp.crans.org. 466 IN   SRV 5 0 5269 xmpp.crans.org.
| 
| xmpp.crans.org.   466 IN  A   138.231.136.66
| xmpp.crans.org.   466 IN  
2a01:240:fe3d:4:200:42ff:fe42:4204

Logs say:
| Aug 31 23:02:18 s2soute11b40infoBeginning new connection attempt to 
crans.org ([2a01:240:fe3d:4:200:42ff:fe42:4204]:5269)
| Aug 31 23:02:18 s2soute11b40infoOut of connection options, can't 
connect to crans.org
| Aug 31 23:02:18 s2soute11b40infoSending error replies for 1 queued 
stanzas because of failed outgoing connection to crans.org

which is fair enough because:
 - trying IPv6 first is the right thing to do;
 - this port appears closed on IPv6 at the time of writing.

But prosody should move to trying a connection on IPv4 instead of simply
giving up and trying again a moment later.

Thanks for your time.


KiBi.

Bug#836135: umountiscsi.sh indiscriminately umounts all LVM based filesystems when no iSCSI sessions are found.

[Christian Seiler]

Hello Frank,

On 08/31/2016 10:46 PM, Frank Fegert wrote:
> On Tue, Aug 30, 2016 at 10:24:22PM +0200, Christian Seiler wrote:
>> Your fix is also correct, but I'm not sure I like the endless
>> list of -o -n repeats... I'll think about it for a while and if
>> I can't find a better solution, I'll commit your fix to git.
>> (And if I find a better solution, I'll commit that. ;-))
> 
> By all means, please do! I'm also not particularly happy with this
> temporary fix, but "it did get the job done"[TM] ;-)

I haven't had time to test it yet (might even still have shell
syntax errors), but I've come up with the following:

get_lvm_vgs() {
# handle the case where we didn't get passed any PVs
# at all
[ $# -gt 0 ] || return
# subshell for pwd change
(
cd /dev
$PVS --noheadings -o vg_name "$@" 2>/dev/null
)
}

and later:

for _vg in $(get_lvm_vgs $iscsi_disks $iscsi_partitions $iscsi_multipath_disks 
$iscsi_multipath_partitions) $LVMGROUPS ; do

Will do some tests in the next couple of days and upload a
fixed version.

>> Speaking of: you appear to be interested in a backport of
>> open-iscsi into Jessie because you want to use offloading via
>> iscsiuio. I've been thinking about uploading open-isns and
>> open-iscsi to jessie-backports myself (precisely to have iscsiuio
>> support available for Jessie users), but was unsure whether
>> there's enough people who'd be interested in that. Would that be
>> something you'd use yourself? Or would you want to continue to
>> use your special backported version instead? Since you're
>> actively using iscsiuio, I'd like to hear your opinion on that
>> first.
> 
> No, i'd definitely prefer an "official" backported version of the
> package, provided it's based on reasonably recent open-iscsi upstream
> sources - there are several important fixes as of late not covered by
> the current Jessie package sources.

Ok, then I'll see to that. I'll have to talk to Ritesh (the other
co-maintainer of open-iscsi) first, and probably want to clarify
something with the backports ftp-masters, so it might take a couple
of weeks until it's in, but if you want, I can notify you via email
once I've created the corresponding packages, even if they are
stuck in the NEW queue for a while.

As for "recent-ness" of backports: the rules for jessie-backports
are that Stretch has to be tracked. Since open-iscsi with iscsiuio
will migrate to Stretch tomorrow (barring a last-minute RC bug),
that's going to be the lowest possible version that's going to
land in backports. And until Stretch is released, jessie-backports
would get all further improvements. (Though to be honest, I don't
see that many major changes happening until Stretch; iscsiuio and
the earlier rework of the startup logic were the big ones on my
list, and those are done.)

> I particularly like your idea of
> putting iscsiuio into its own package.

Yes. While it isn't harmful, I don't think having the daemon
started on every system, even those without bnx2 cards, is a
sensible default. ;-)

> What's a real pain though, is the whole hassle with "_netdev", "LVM-
> GROUPS",

So _netdev will need to stay, I don't see how to improve that. I do
want to get rid of LVMGROUPS in the long term (because I think that
is a layering violation), so in Stretch we'll recommend to use
lvmetad for activating LVM volumes (while still supporting the old
way until after the Stretch release). Doesn't help you for Jessie
though, because lvmetad is broken there. (And as far as I understood
it, the fix is too complicated to be pushed via a stable update.)

> and still having to tweak the multipath init script.

Could you be more specific here? What exactly do you need to do?
I still have an item on my TODO list to take a look at multipath
vs. iSCSI in Jessie (in Stretch it works), because there was a
bug report on debian-user about it - I just didn't manage to do
so yet. If you are using that and have already looked into it,
it would be great, then I could probably try to also get that
sorted. (No guarantees for 8.6 though, because that'll happen on
Sep. 17th, so the time window is a bit short there.)

> Compared to the straightforward
> use of targets through full iSOEs like e.g. the QME8262 cards, this
> just feels awkward. Maybe it's just me doing something terribly wrong
> ;-)

If you have specific suggestions for how things could be done
in a simpler manner, even if it's just documentation, then I'm
all ears. I do think it's the job of Debian packaging to provide
a good integration of software. But once you get to know a bit
of software very well, you don't necessarily see all the
usability issues, because you know how to do stuff. So if you
have any suggestions, just tell us.

Regards,
Christian

Bug#836230: [Debian-med-packaging] Bug#836230: genometools: FTBFS in testing (a2x: ERROR: "xsltproc" returned non-zero exit status 6)

[Sascha Steinbiss]

Hi Santiago,

thanks for reporting this.

> I tried to build this package in stretch with "dpkg-buildpackage -A"
> (which is what the "Arch: all" autobuilder would do to build it)
> but it failed:
[…]
> a2x: ERROR: "xsltproc"  --stringparam callout.graphics 0 --stringparam 
> navig.graphics 0 --stringparam admon.textlabel 1 --stringparam admon.graphics 
> 0  "/etc/asciidoc/docbook-xsl/manpage.xsl" 
> "/<>/genometools-1.5.9+ds/doc/manpages/gt.xml" returned non-zero 
> exit

Unfortunately, I can not reproduce this. For me the package builds with no 
problem (-A and -B with gbp-buildpackage and cowbuilder in a freshly updated 
stretch chroot). Build logs can be found at 
http://dropbox.tetrinetsucht.de/debian/ (too large for paste.debian.net).

> This used to work in the past, so I would look for build-dependencies
> which may have changed their behaviour recently.

Both docbook-xsl and asciidoc, which may be the relevant build-deps here, 
didn’t have any recent uploads.

I am wondering if anyone may have any hints?

Cheers
Sascha


signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#835238: astroquery: FTBFS with pytest 3.0.0

[Sebastian Ramacher]

Hi

On 2016-08-31 17:05:41, Vincent Prat wrote:
> I tried to replace all the occurrences of getfuncargvalue in the package,
> and this removes a lot of errors.

Thanks for working on the issue!

> However, there are still some left, apparently due to pytest itself:

If that's a pytest regression, please report it at
https://github.com/pytest-dev/pytest/issues.

Cheers

> 
> |self = 
> |
> |def setup(self):
> |if self.dtest is not None:
> |self.fixture_request = _setup_fixtures(self)
> |globs = dict(getfixture=self.fixture_request.getfixturevalue)
> |>   for name, value in
> self.fixture_request.getfuncargvalue('doctest_namespace').items():
> |
> |/usr/lib/python2.7/dist-packages/_pytest/doctest.py:91:
> |_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _ _
> |
> |self =  'astroquery.utils.url_helpers.urljoin_keep_path'>>
> |argname = 'doctest_namespace'
> |
> |def getfuncargvalue(self, argname):
> |""" Deprecated, use getfixturevalue. """
> |from _pytest import deprecated
> |warnings.warn(
> |deprecated.GETFUNCARGVALUE,
> |>   DeprecationWarning)
> |E   DeprecationWarning: use of getfuncargvalue is deprecated, use
> getfixturevalue
> |
> |/usr/lib/python2.7/dist-packages/_pytest/fixtures.py:446:
> DeprecationWarning
> 
> Cheers,
> 
> Vincent Prat
> 

-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#510589: icedove: Crash back trace

[Sean M. Pappalardo]

Package: icedove
Version: 1:45.2.0-1~deb8u1
Followup-For: Bug #510589

Dear Maintainer,

I've observed random occasional crashes in Icedove since upgrading to v45.0 
(and it still happens with 45.2.)
It usually happens when clicking on a new E-mail message, but not always.

I've been able to get a back-trace of one of the crashes: 
http://paste.debian.net/799001/

Sincerely,
Sean M. Pappalardo


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

Kernel: Linux 4.5.0-0.bpo.2-amd64 (SMP w/4 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 icedove depends on:
ii  debianutils   4.4+b1
ii  fontconfig2.11.0-6.3+deb8u1
ii  libasound21.0.28-1
ii  libatk1.0-0   2.14.0-1
ii  libc6 2.19-18+deb8u4
ii  libcairo2 1.14.0-2.1+deb8u1
ii  libdbus-1-3   1.8.20-0+deb8u1
ii  libdbus-glib-1-2  0.102-1
ii  libevent-2.0-52.0.21-stable-2
ii  libffi6   3.1-2+b2
ii  libfontconfig12.11.0-6.3+deb8u1
ii  libfreetype6  2.5.2-3+deb8u1
ii  libgcc1   1:4.9.2-10
ii  libgdk-pixbuf2.0-02.31.1-2+deb8u5
ii  libglib2.0-0  2.42.1-1+b1
ii  libgtk2.0-0   2.24.25-3+deb8u1
ii  libhunspell-1.3-0 1.3.3-3
ii  libpango-1.0-01.36.8-3
ii  libpangocairo-1.0-0   1.36.8-3
ii  libpangoft2-1.0-0 1.36.8-3
ii  libpixman-1-0 0.32.6-3
ii  libstartup-notification0  0.12-4
ii  libstdc++64.9.2-10
ii  libx11-6  2:1.6.2-3
ii  libxcomposite11:0.4.4-1
ii  libxdamage1   1:1.1.4-2+b1
ii  libxext6  2:1.3.3-1
ii  libxfixes31:5.0.1-2+b2
ii  libxrender1   1:0.9.8-1+b1
ii  libxt61:1.1.4-1+b1
ii  psmisc22.21-2
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages icedove recommends:
ii  hunspell-en-us [hunspell-dictionary]  20070829-6
ii  iceowl-extension  1:45.2.0-1~deb8u1

Versions of packages icedove suggests:
ii  fonts-lyx 2.1.2-2
ii  libgssapi-krb5-2  1.12.1+dfsg-19+deb8u2

-- no debconf information

Bug#836227: libreoffice-writer: Insert menu Table option no longer appears

[Rene Engelhard]

tag 836227 + upstream
tag 836227 + wontfix
thanks

Hi,

On Wed, Aug 31, 2016 at 12:02:25PM -0700, Mark Hedges wrote:
> Severity: normal

Not sure.

> There used to be a "Table" option in the "Insert" menu to insert a table with 
> rows and columns.  It no longer appears.  The control in the default toolbar 
> still appears with the tooltip "Insert Table (Ctrl+F12)".  It seems like it 
> should be in the Insert menu too.  It used to be.

It seems like it shouldn't. Googling for "Libreoffice 5.2 insert table menu"
gives me 
https://design.blog.documentfoundation.org/2016/01/22/way-down-in-the-libreoffice-menus/

And when trying it out, what about Table -> Insert Table?

Sounds like a deliberate change to me. And that this change was already
in 5.1.x.

Can we close it? Or this is merely a wish to get it back? Then I guess
you should file that upstream (I won't pursue that, I don't use LO and
tables in writer that much that I would care much) and try to get it changed
back again. I wouldn't have very much hope there, though given it was a
deliberate change.

Regards,

Rene

Bug#687904: interchange: diff for NMU version 5.7.7-2.1

[gregor herrmann]

Control: tags 687904 + patch
Control: tags 687904 + pending
Control: tags 821994 + pending
Control: tags 834550 + pending

Dear maintainer,

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

Regards.

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Die Quote: You see
diff -u interchange-5.7.7/debian/changelog interchange-5.7.7/debian/changelog
--- interchange-5.7.7/debian/changelog
+++ interchange-5.7.7/debian/changelog
@@ -1,3 +1,22 @@
+interchange (5.7.7-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "FTBFS with '.' removed from perl's @INC":
+patch relocate.pl to "require './scripts/"
+Thanks Dominic Hargreaves for the patch.
+(Closes: #834550)
+  * Additionally add "-I." to a perl call in debian/rules, otherwise the build
+fails later for the same reason.
+  * Fix "Build arch:all+arch:any but is missing build-{arch,indep}
+targets": add build-arch and build-indep targets to debian/rules.
+Patch from Santiago Vila, thanks.
+(Closes: #821994)
+  * (Re?)apply the patch from #625904 to replace Digest::SHA1 with
+Digest::SHA.
+(Closes: #687904)
+
+ -- gregor herrmann   Wed, 31 Aug 2016 22:47:29 +0200
+
 interchange (5.7.7-2) unstable; urgency=low
   
   * Remove superfluous space before question mark from Debconf template
diff -u interchange-5.7.7/debian/rules interchange-5.7.7/debian/rules
--- interchange-5.7.7/debian/rules
+++ interchange-5.7.7/debian/rules
@@ -28,6 +28,8 @@
 IC_VERSION := $(shell dpkg-parsechangelog | perl -ne 'print $$1 if /^Version: (.*?)-(.*)$$/')
 IC_MAJOR_VERSION := $(shell dpkg-parsechangelog | perl -ne 'print $$1 if /^Version: (\d+\.\d+)(.*?)-(.*)$$/')
 
+build-arch: build
+build-indep: build
 build: build-stamp
 build-stamp:
 	dh_testdir
@@ -87,7 +89,7 @@
 		dist/robots.cfg dist/subdomains.cfg $(TMP)/etc/interchange
 # build Interchange control program(s)
 	mkdir -p $(TMP)/usr/lib/cgi-bin/ic
-	$(PERL) scripts/compile_link \
+	$(PERL) -I. scripts/compile_link \
 		--nostrip \
 		--socket=/var/run/interchange/interchange.sock \
 		--port=7786 \
@@ -173 +175 @@
-.PHONY: build clean binary-indep binary-arch binary install
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install
only in patch2:
unchanged:
--- interchange-5.7.7.orig/code/Filter/sha1.filter
+++ interchange-5.7.7/code/Filter/sha1.filter
@@ -5,15 +5,15 @@
 # the Free Software Foundation; either version 2 of the License, or
 # (at your option) any later version. See the LICENSE file for details.
 
-Require module Digest::SHA1
+Require module Digest::SHA
 
 CodeDef sha1 Filter
 CodeDef sha1 Description sha1 sum
 CodeDef sha1 Routine log_either('SHA passwords unavailable. Is Digest::SHA installed?');
 return;
 }
-return Digest::SHA1::sha1_hex(shift);
+return Digest::SHA::sha1_hex(shift);
 }
 
 # Maps the length of the encrypted data to the algorithm that
only in patch2:
unchanged:
--- interchange-5.7.7.orig/relocate.pl
+++ interchange-5.7.7/relocate.pl
@@ -23,7 +23,7 @@
 
 use Config;
 
-require 'scripts/initp.pl';
+require './scripts/initp.pl';
 
 sub doit {
 	my ($key) = @_;


signature.asc
Description: Digital Signature

Bug#836135: umountiscsi.sh indiscriminately umounts all LVM based filesystems when no iSCSI sessions are found.

[Frank Fegert]

Hello Christian,

On Tue, Aug 30, 2016 at 10:24:22PM +0200, Christian Seiler wrote:
> While not having tested this, from just looking at the code with
> your explanation in mind, yes, you're right about that.

thanks for your confirmation!

> Your fix is also correct, but I'm not sure I like the endless
> list of -o -n repeats... I'll think about it for a while and if
> I can't find a better solution, I'll commit your fix to git.
> (And if I find a better solution, I'll commit that. ;-))

By all means, please do! I'm also not particularly happy with this
temporary fix, but "it did get the job done"[TM] ;-)

> Speaking of: you appear to be interested in a backport of
> open-iscsi into Jessie because you want to use offloading via
> iscsiuio. I've been thinking about uploading open-isns and
> open-iscsi to jessie-backports myself (precisely to have iscsiuio
> support available for Jessie users), but was unsure whether
> there's enough people who'd be interested in that. Would that be
> something you'd use yourself? Or would you want to continue to
> use your special backported version instead? Since you're
> actively using iscsiuio, I'd like to hear your opinion on that
> first.

No, i'd definitely prefer an "official" backported version of the
package, provided it's based on reasonably recent open-iscsi upstream
sources - there are several important fixes as of late not covered by
the current Jessie package sources. I particularly like your idea of
putting iscsiuio into its own package.
What's a real pain though, is the whole hassle with "_netdev", "LVM-
GROUPS", and still having to tweak the multipath init script. Well,
that's at least what i ended up with to get the order of things at
boot time at least almost right :-( Compared to the straightforward
use of targets through full iSOEs like e.g. the QME8262 cards, this
just feels awkward. Maybe it's just me doing something terribly wrong
;-)

Thanks & best regards,

Frank

Bug#793486: interchange-cat-standard: fails to install in sid: post-installation script returned error exit status 10

[gregor herrmann]

On Fri, 24 Jul 2015 16:18:34 +0200, Andreas Beckmann wrote:

> Package: interchange-cat-standard
> Version: 5.7.7-2
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> >From the attached log (scroll to the bottom...):
> 
>   Selecting previously unselected package interchange-cat-standard.
>   (Reading database ... 
> (Reading database ... 11471 files and directories currently installed.)
>   Preparing to unpack .../interchange-cat-standard_5.7.7-2_all.deb ...
>   Unpacking interchange-cat-standard (5.7.7-2) ...
>   Setting up interchange-cat-standard (5.7.7-2) ...
>   dpkg: error processing package interchange-cat-standard (--configure):
>subprocess installed post-installation script returned error exit status 10
>   Errors were encountered while processing:
>interchange-cat-standard

This happens in the dbconfig-common part, AFAIK, but I didn't get
further ...


Cheers,
gregor

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Rolling Stones


signature.asc
Description: Digital Signature

Bug#827239: muse: apt reports problems when installing different package

[James Cowgill]

Control: retitle -1 muse: doc-base file is invalid

On 14/06/16 01:23, treaki wrote:
> Package: muse
> Version: 2.1.2-1
> Severity: normal
> 
> hi,
> 
> i dont know if it is precisely this package, but i have installed something 
> else through apt and ive got this message:
> 
> doc-base (0.10.6) wird eingerichtet ...
> 154 Doc-base-Dateien werden registriert ...
> Fehler in »/usr/share/doc-base/muse-manual«, Zeile 10: alle 
> »Format«-Abschnitte sind ungültig.
> Beachten Sie: »install-docs --verbose --check Dateiname« könnte weitere 
> Einzelheiten über den vorhergehenden Fehler ausgeben.
> Dokumente werden mit scrollkeeper registriert ...
> festival-doc (1:2.1~release-8) wird eingerichtet ...
> 
> (german text) sounds like there is a problem with interpreting line 10 of the 
> file /usr/share/doc-base/muse-manual in the step of register up 
> doc-base-files 

Simply installing muse is enough to reproduce this.

English version:

Processing triggers for doc-base (0.10.7) ...
Processing 1 added doc-base file...
Error in `/usr/share/doc-base/muse-manual', line 10: all `Format'
sections are invalid.
Note: `install-docs --verbose --check file_name' may give more details
about the above error.

The doc-base file refers to /usr/share/doc/muse/html/index.html which
doesn't exist.

James



signature.asc
Description: OpenPGP digital signature

Bug#824177: Segfault in (clustered) Samba

[Mathieu Parent]

On Wed, 31 Aug 2016 22:22:58 +0200 Mathieu Parent  wrote:
> Version: 2:4.4.4+dfsg-1
>
> At least, this is fixed in sid.
>
> I need to figure out the status in jessie.

This is in 4.2.13, not yet in jessie (4759f64e94e01e32b36f048d20bf4c94e4398ef3).

Regards

Mathieu Parent

Bug#836235: golang-context-dev: could not access git repo address

[Liang Yan]

Package: golang-context-dev
Severity: minor

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
Try to build a package
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


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

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

Bug#835206: [Packaging] Bug#835206: munin: diff for NMU version 2.0.25-2.1

[Holger Levsen]

On Wed, Aug 31, 2016 at 09:56:02PM +0200, gregor herrmann wrote:
> NMU cancelled as per maintainer's request on IRC.

that was me.

> A maintainer upload is supposed to be pending :)

well, I didn't say that, just that I think we should do one… (and also
address other issues…)


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#836234: ITP: python-iptables -- Python bindings for iptables

[IOhannes m zmoelnig]

Package: wnpp
Severity: wishlist
Owner: IOhannes m zmölnig (Debian/GNU) 

* Package name: python-iptables
  Version : 0.11.0
  Upstream Author : Vilmos Nebehaj 
* URL : https://github.com/ldx/python-iptables
* License : Apache License, Version 2.0
  Programming Lang: Python
  Description : Python bindings for iptables

 Python-iptables provides a pythonesque wrapper via python bindings to iptables
 under Linux. Interoperability with iptables is achieved by using the iptables
 C libraries (libiptc, libxtables, and the iptables extensions), instead of
 calling the iptables binary and parsing its output.
 It is meant primarily for dynamic and/or complex routers and firewalls, where
 rules are often updated or changed, or Python programs wish to interface with
 the Linux iptables framework...

Binary package names: python3-iptables python-iptables
I intend to maintain this package within the Debian Python Modules Team.

Bug#836233: ITP: python-isc-dhcp-leases -- python module for reading dhcp leases files

[IOhannes m zmoelnig]

Package: wnpp
Severity: wishlist
Owner: IOhannes m zmölnig (Debian/GNU) 

* Package name: python-isc-dhcp-leases
  Version : 0.8.1
  Upstream Author : Martijn Braam 
* URL : https://github.com/MartijnBraam/python-isc-dhcp-leases
* License : MIT
  Programming Lang: Python
  Description : python module for reading dhcp leases files

 Small python module for reading /var/lib/dhcp/dhcpd.leases as written by
 isc-dhcp-server.
 .
 This module also supports reading lease files from the isc dhcp daemon running
 in IPv6 mode.

Binary package names: python-isc-dhcp-leases python3-isc-dhcp-leases
I intend to maintain this package within the Debian Python Modules Team.

Bug#836136: new note crash related to tidy

[Mats Sjöberg]

Thanks for the report!

This is essentially the same issue as in #834031.

On 2016-08-30 23:21, Joey Hess wrote:
> Package: pumpa
> Version: 0.9.2-1+b1
> Severity: normal
> 
> pumpa is crashing when I click on New Note
> 
> pumpa: /build/tidy-html5-kAYBhq/tidy-html5-5.2.0/src/config.c:409: 
> prvTidySetOptionBool: Assertion `option_defs[ optId ].type == TidyBoolean' 
> failed.
> Aborted
> 
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages pumpa depends on:
> ii  libaspell15   0.60.7~20110707-3+b1
> ii  libc6 2.23-5
> ii  libgcc1   1:6.2.0-1
> ii  libgl1-mesa-glx [libgl1]  11.2.2-1
> ii  libqt5core5a  5.6.1+dfsg-3+b1
> ii  libqt5dbus5   5.6.1+dfsg-3+b1
> ii  libqt5gui55.6.1+dfsg-3+b1
> ii  libqt5network55.6.1+dfsg-3+b1
> ii  libqt5widgets55.6.1+dfsg-3+b1
> ii  libstdc++66.2.0-1
> ii  libtidy5  1:5.2.0-2
> 
> pumpa recommends no packages.
> 
> pumpa suggests no packages.
> 
> -- no debconf information
> 



signature.asc
Description: OpenPGP digital signature

Bug#830534: gnome-pie doesn't start anymore

[Jörg Frings-Fürst]

Hello Ghent,

first many thanks! 

Am Mittwoch, den 31.08.2016, 20:31 +0200 schrieb Ghent-debian:
> Hi,
> 
>   I join my old config files.
> Today, I tested the old config files with the last version of
> gnome-pie 0.6.9 and no bug with them.
> 

I test the update with your files to find the bug in the code.

Fine that the bug doesn't exist at the latest release.
I think that I can close this bug.


> Kindly,
> Ghent

CU
Jörg

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

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

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

Threema: SYR8SJXB

IRC: j_...@freenode.net
 j_...@oftc.net

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


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

Bug#835472: Gajim 0.16.5-2 crashed after update on startup

[Antonio Ospite]

On Wed, 31 Aug 2016 19:42:00 +0200
"W. Martin Borgert"  wrote:

> Why is demandimport used in the first place?
> 
> If I understand correctly, this function is useful for
> command line tools, so that they have a fast startup.
> 
> But long running GUI programs or servers have no
> advantage from using demandimport, or am I wrong?
> 
> Why not just remove (use of) demandimport from Gajim
> and its plugins? Am I missing something?
> 

That I don't know. If you are willing to ask gajim developers point them
to this report, and please let us know their reply.

I contacted mercurial devs about demandimport failing with the _thread
module, and one of them told me to just blacklist _thread for
demandimport in the gajim-omemo code.

I still feel that the issue should be addressed in a more general way,
but I guess for now I'll suggest the gajim-omemo devs to just blacklist
_thread.

Ciao,
   Antonio

-- 
Antonio Ospite
http://ao2.it

A: Because it messes up the order in which people normally read text.
   See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?

Bug#835237: pytest 3.0.1 is now in unstable

[Sebastian Ramacher]

severity 835237 serious
severity 835240 serious
severity 835241 serious
severity 835243 serious
severity 835245 serious
severity 835247 serious
severity 835250 serious
severity 835238 serious
thanks

pytest 3.0.1 is now in unstable, so raising the severity of the bugs
accordingly.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#835206: [Packaging] Bug#835206: munin: diff for NMU version 2.0.25-2.1

[Stig Sandbeck Mathisen]

Much appreciated, thank you. :)

-- 
Stig Sandbeck Mathisen
https://fnord.no/


signature.asc
Description: PGP signature

Bug#835206: munin: diff for NMU version 2.0.25-2.1

[gregor herrmann]

Control: tags 835206 - pending


On Wed, 31 Aug 2016 21:23:41 +0200, gregor herrmann wrote:

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

NMU cancelled as per maintainer's request on IRC.
A maintainer upload is supposed to be pending :)
 

Cheers,
gregor

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: J.J. Cale: Devil In Disguise


signature.asc
Description: Digital Signature

Bug#834731: kdesrc-build: diff for NMU version 1.15.1-1.1

[gregor herrmann]

Control: tags 834731 + pending

Dear maintainer,

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

Regards.

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Beatles
diff -Nru kdesrc-build-1.15.1/debian/changelog kdesrc-build-1.15.1/debian/changelog
--- kdesrc-build-1.15.1/debian/changelog	2012-05-25 12:51:54.0 +0200
+++ kdesrc-build-1.15.1/debian/changelog	2016-08-31 21:43:59.0 +0200
@@ -1,3 +1,13 @@
+kdesrc-build (1.15.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Dominic Hargreaves ]
+  * Fix kdesrc-build-test.pl to work without '.' in @INC
+Closes: #834731
+
+ -- gregor herrmann   Wed, 31 Aug 2016 21:43:59 +0200
+
 kdesrc-build (1.15.1-1) unstable; urgency=low
 
   * New upstream release.
diff -Nru kdesrc-build-1.15.1/debian/patches/series kdesrc-build-1.15.1/debian/patches/series
--- kdesrc-build-1.15.1/debian/patches/series	1970-01-01 01:00:00.0 +0100
+++ kdesrc-build-1.15.1/debian/patches/series	2016-08-31 21:43:53.0 +0200
@@ -0,0 +1 @@
+test-without-inc
diff -Nru kdesrc-build-1.15.1/debian/patches/test-without-inc kdesrc-build-1.15.1/debian/patches/test-without-inc
--- kdesrc-build-1.15.1/debian/patches/test-without-inc	1970-01-01 01:00:00.0 +0100
+++ kdesrc-build-1.15.1/debian/patches/test-without-inc	2016-08-31 21:43:59.0 +0200
@@ -0,0 +1,15 @@
+Description: Fix kdesrc-build-test.pl to work without '.' in @INC
+Author: Dominic Hargreaves 
+Bug-Debian: https://bugs.debian.org/834731
+
+--- kdesrc-build-1.15.1.orig/kdesrc-build-test.pl
 kdesrc-build-1.15.1/kdesrc-build-test.pl
+@@ -21,7 +21,7 @@ my $fullRun = 0;
+ GetOptions("full-run!" => \$fullRun);
+ 
+ package test; # Tells kdesrc-build not to run
+-require 'kdesrc-build';
++require './kdesrc-build';
+ 
+ # Reset to kdesrc-build's package so we don't have to import symbols back from
+ # kdesrc-build.


signature.asc
Description: Digital Signature

Bug#836230: genometools: FTBFS in testing (a2x: ERROR: "xsltproc" returned non-zero exit status 6)

[Santiago Vila]

Package: src:genometools
Version: 1.5.9+ds-2
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with python2
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>/genometools-1.5.9+ds'
faketime -f "`TZ=UTC date -d @1469271266 +'%Y-%m-%d %H:%M:%S'`" dh_auto_build 
-- useshared=yes x32=no 64bit=yes errorcheck=no all docs manuals
make -j1 useshared=yes x32=no 64bit=yes errorcheck=no all docs manuals
make[2]: Entering directory '/<>/genometools-1.5.9+ds'
[create obj/gt_config.h]
[compile alphabet.o]
[compile array.o]

[... snipped ...]

cp -r gtdata /<>/genometools-1.5.9+ds/debian/tmp/usr/bin
test -d 
/<>/genometools-1.5.9+ds/debian/tmp/usr/include/genometools/core \
  || mkdir -p 
/<>/genometools-1.5.9+ds/debian/tmp/usr/include/genometools/core
cp src/core/*_api.h 
/<>/genometools-1.5.9+ds/debian/tmp/usr/include/genometools/core
test -d 
/<>/genometools-1.5.9+ds/debian/tmp/usr/include/genometools/extended \
  || mkdir -p 
/<>/genometools-1.5.9+ds/debian/tmp/usr/include/genometools/extended
cp src/extended/*_api.h 
/<>/genometools-1.5.9+ds/debian/tmp/usr/include/genometools/extended
test -d 
/<>/genometools-1.5.9+ds/debian/tmp/usr/include/genometools/annotationsketch
 \
  || mkdir -p 
/<>/genometools-1.5.9+ds/debian/tmp/usr/include/genometools/annotationsketch
cp src/annotationsketch/*_api.h \
  
/<>/genometools-1.5.9+ds/debian/tmp/usr/include/genometools/annotationsketch
test -d 
/<>/genometools-1.5.9+ds/debian/tmp/usr/include/genometools/ltr \
  || mkdir -p 
/<>/genometools-1.5.9+ds/debian/tmp/usr/include/genometools/ltr
cp src/ltr/*_api.h 
/<>/genometools-1.5.9+ds/debian/tmp/usr/include/genometools/ltr
cp obj/gt_config.h 
/<>/genometools-1.5.9+ds/debian/tmp/usr/include/genometools
cp src/genometools.h 
/<>/genometools-1.5.9+ds/debian/tmp/usr/include/genometools
test -d /<>/genometools-1.5.9+ds/debian/tmp/usr/lib || mkdir -p 
/<>/genometools-1.5.9+ds/debian/tmp/usr/lib
cp lib/libgenometools.a /<>/genometools-1.5.9+ds/debian/tmp/usr/lib
cp lib/libgenometools.so.0 /<>/genometools-1.5.9+ds/debian/tmp/usr/lib
ln -fs 
/<>/genometools-1.5.9+ds/debian/tmp/usr/lib/libgenometools.so.0 
/<>/genometools-1.5.9+ds/debian/tmp/usr/lib/libgenometools.so
[build config script install]
sed -e 's!@CC@!cc!' -e 's!@CFLAGS@!-g -O2 
-fdebug-prefix-map=/<>/genometools-1.5.9+ds=. -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security!' \
  -e 
's!@CPPFLAGS@!-I\\"/<>/genometools-1.5.9+ds/debian/tmp/usr/include\\" 
-Wdate-time -D_FORTIFY_SOURCE=2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
-DHAVE_MEMMOVE -D_LARGEFILE64_SOURCE=1 -DHAVE_HIDDEN -DLUA_DL_DLOPEN 
-DLUA_USE_MKSTEMP -DHAVE_SQLITE!' \
  -e 's!@CXX@!g++!' -e 's!@CXXFLAGS@!-g -O2 
-fdebug-prefix-map=/<>/genometools-1.5.9+ds=. -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security!' \
  -e 's!@LDFLAGS@!-L/<>/genometools-1.5.9+ds/debian/tmp/usr/lib -fPIE 
-pie -Wl,-z,relro -Wl,-z,now -L/usr/local/lib!' \
  -e 's!@LIBS@! -lm -lbz2 -lz -lexpat -llua5.1 -llua5.1-lpeg -llua5.1 
-llua5.1-md5 -llua5.1 -llua5.1-filesystem -llua5.1 -llua5.1-des56 -llua5.1 
-lbam -ltre -Wl,-z,relro -lm -lpthread -ldl -lpango-1.0 -lgobject-2.0 
-lglib-2.0 -lcairo -lpangocairo-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 
-lcairo -lsqlite3!' -e "s!@VERSION@!`cat VERSION`!" \
  -e 's!@BUILDSTAMP@!"2016-08-31 16:47:11"!' \
  -e 's!@SYSTEM@!Linux!' /<>/genometools-1.5.9+ds/debian/tmp/usr/bin/genometools-config
chmod 755 
/<>/genometools-1.5.9+ds/debian/tmp/usr/bin/genometools-config
bin/gt -createman /tmp/gtmanpages
warning: skipping tool 'mgth' in iterator (not a GtTool object)
warning: skipping tool 'mkfmindex' in iterator (not a GtTool object)
warning: skipping tool 'suffixerator' in iterator (not a GtTool object)
warning: skipping tool 'chkintegrity' in iterator (not a GtTool object)
warning: skipping tool 'chksearch' in iterator (not a GtTool object)
warning: skipping tool 'mkctxmap' in iterator (not a GtTool object)
warning: skipping tool 'mkindex' in iterator (not a GtTool object)
warning: skipping tool 'trsuftab' in iterator (not a GtTool object)
test -d /<>/genometools-1.5.9+ds/doc/manpages || mkdir -p 
/<>/genometools-1.5.9+ds/doc/manpages
rm -f /<>/genometools-1.5.9+ds/doc/manpages/*
scripts/create_manpages /tmp/gtmanpages 
/<>/genometools-1.5.9+ds/doc/manpages
.a2x: WARNING: --destination-dir option is only applicable to HTML based outputs
a2x: ERROR: "xsltproc"  --stringparam callout.graphics 0 --stringparam 
navig.graphics 0 --stringparam admon.textlabel 1 --stringparam admon.graphics 0 
 "/etc/asciidoc/docbook-xsl/manpage.xsl" 
"/<>/genometools-1.5.9+ds/doc/manpages/gt.xml" returned 

Bug#834738: Pending fixes for bugs in the libcatmandu-mab2-perl package

[pkg-perl-maintainers]

tag 834738 + pending
thanks

Some bugs in the libcatmandu-mab2-perl package are closed in revision
15b61db63d0b3a03d465b1109061709c17bdddc6 in branch 'master' by
Dominic Hargreaves

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libcatmandu-mab2-perl.git/commit/?id=15b61db

Commit message:

Fix t/06-sru.t to work without '.' in @INC

Closes: #834738

Bug#836231: linux: [armhf] Please enable B53 mdio switch driver

[Vagrant Cascadian]

Source: linux
Severity: wishlist
Tags: patch

Please enable the B53 mdio switch driver modules introduced in linux
4.8.x, which is used on the Lamobo-R1 (a.k.a. BPI-R1, Bananpi-R1).

live well,
  vagrant

diff --git a/debian/config/armhf/config b/debian/config/armhf/config
index 0a9be6f..18d2f74 100644
--- a/debian/config/armhf/config
+++ b/debian/config/armhf/config
@@ -1262,3 +1262,5 @@ CONFIG_SND_SOC_TEGRA_ALC5632=m
 CONFIG_SND_SOC_TEGRA_MAX98090=m
 CONFIG_SND_SOC_TEGRA_RT5677=m
 
+CONFIG_B53=m
+CONFIG_B53_MDIO_DRIVER=m


signature.asc
Description: PGP signature

Bug#835206: munin: diff for NMU version 2.0.25-2.1

[gregor herrmann]

Control: tags 835206 + pending

Dear maintainer,

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

Regards.

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Ben Weaver: 40 Watt Bulb
diff -Nru munin-2.0.25/debian/changelog munin-2.0.25/debian/changelog
--- munin-2.0.25/debian/changelog	2015-08-30 10:07:44.0 +0200
+++ munin-2.0.25/debian/changelog	2016-08-31 21:19:25.0 +0200
@@ -1,3 +1,12 @@
+munin (2.0.25-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "FTBFS with '.' removed from perl's @INC":
+add patch from Dominic Hargreaves to call perl with "-I.".
+(Closes: #835206)
+
+ -- gregor herrmann   Wed, 31 Aug 2016 21:19:25 +0200
+
 munin (2.0.25-2) unstable; urgency=medium
 
   [ Holger Levsen ]
diff -Nru munin-2.0.25/debian/patches/0001-Pass-I.-to-Build-so-that-it-will-work-without-.-in-I.patch munin-2.0.25/debian/patches/0001-Pass-I.-to-Build-so-that-it-will-work-without-.-in-I.patch
--- munin-2.0.25/debian/patches/0001-Pass-I.-to-Build-so-that-it-will-work-without-.-in-I.patch	1970-01-01 01:00:00.0 +0100
+++ munin-2.0.25/debian/patches/0001-Pass-I.-to-Build-so-that-it-will-work-without-.-in-I.patch	2016-08-31 21:14:41.0 +0200
@@ -0,0 +1,25 @@
+From 8fde7928f0d883adf8f27b0958d0e452a0bd57a1 Mon Sep 17 00:00:00 2001
+From: Dominic Hargreaves 
+Date: Tue, 23 Aug 2016 13:07:24 +0100
+Subject: [PATCH] Pass -I. to Build.PL so that it will work without '.' in @INC
+
+---
+ Makefile | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/Makefile b/Makefile
+index cdc3577..ded00b8 100644
+--- a/Makefile
 b/Makefile
+@@ -449,7 +449,7 @@ t/install:
+ 
+ # This builds */Build from Build.PL
+ %/Build: %/Build.PL
+-	cd $* && $(PERL) Build.PL
++	cd $* && $(PERL) -I. Build.PL
+ 
+ build-%: %/Build
+ 	cd $* && $(PERL) Build
+-- 
+2.1.4
+
diff -Nru munin-2.0.25/debian/patches/series munin-2.0.25/debian/patches/series
--- munin-2.0.25/debian/patches/series	2015-08-30 10:07:44.0 +0200
+++ munin-2.0.25/debian/patches/series	2016-08-31 21:17:17.0 +0200
@@ -1 +1,2 @@
 0001-http_loadtime-plugin-Fix-several-bugs.patch
+0001-Pass-I.-to-Build-so-that-it-will-work-without-.-in-I.patch


signature.asc
Description: Digital Signature

Bug#836229: vagrant: Configuring and enabling network interfaces fail on Red Hat guests

[SATOH Fumiyasu]

Package: vagrant
Version: 1.8.5+dfsg-1
Severity: important

0012-plugins-don-t-abuse-require_relative.patch has a bug
that results the following problem:

$ vagrant up host0
...
==> host0: Configuring and enabling network interfaces...
/usr/share/vagrant/plugins/guests/redhat/cap/configure_networks.rb:4:in
`require_relative': cannot load such file --
/usr/share/vagrant/lib/vagrant/util/template_renderer (LoadError)
from
/usr/share/vagrant/plugins/guests/redhat/cap/configure_networks.rb:4:in 
`'
...

See the attached patch.

Thank you.

-- 
-- Name: SATOH Fumiyasu @ OSS Technology Corp. (fumiyas @ osstech co jp)
-- Business Home: http://www.OSSTech.co.jp/
-- GitHub Home: https://GitHub.com/fumiyas/
-- PGP Fingerprint: BBE1 A1C9 525A 292E 6729  CDEC ADC2 9DCA 5E1C CBCA
>From 750ead977e49365a0f7a4296046bf06133131401 Mon Sep 17 00:00:00 2001
From: SATOH Fumiyasu 
Date: Thu, 1 Sep 2016 03:11:26 +0900
Subject: [PATCH] 0012-plugins-don-t-abuse-require_relative.patch: Fix previous
 refreshing

Configuring and enabling network interfaces fail on Red Hat guests:

$ vagrant up
...
==> host5: Configuring and enabling network interfaces...
/usr/share/vagrant/plugins/guests/redhat/cap/configure_networks.rb:4:in
`require_relative': cannot load such file --
/usr/share/vagrant/lib/vagrant/util/template_renderer (LoadError)
from
/usr/share/vagrant/plugins/guests/redhat/cap/configure_networks.rb:4:in 
`'
...
---
 debian/patches/0012-plugins-don-t-abuse-require_relative.patch | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/patches/0012-plugins-don-t-abuse-require_relative.patch 
b/debian/patches/0012-plugins-don-t-abuse-require_relative.patch
index 4ce5299..24ecaf4 100644
--- a/debian/patches/0012-plugins-don-t-abuse-require_relative.patch
+++ b/debian/patches/0012-plugins-don-t-abuse-require_relative.patch
@@ -153,7 +153,7 @@ index 6cbc9ec..8f5f4c7 100644
  require "tempfile"
  
 -require_relative "../../../../lib/vagrant/util/template_renderer"
-+require_relative "vagrant/util/template_renderer"
++require "vagrant/util/template_renderer"
  
  module VagrantPlugins
module GuestRedHat
-- 
2.9.3

Bug#836228: fix build with ld --as-needed as the default

[Matthias Klose]

Package: src:monkeysphere
Version: 0.39-1
Severity: important
Tags: patch sid stretch

this fixes the build when ld --as-needed is the default behaviour.

patch at
http://launchpadlibrarian.net/281962610/monkeysphere_0.39-1_0.39-1ubuntu1.diff.gz

Bug#836227: libreoffice-writer: Insert menu Table option no longer appears

[Mark Hedges]

Package: libreoffice-writer
Version: 1:5.2.0-2
Severity: normal

There used to be a "Table" option in the "Insert" menu to insert a table with 
rows and columns.  It no longer appears.  The control in the default toolbar 
still appears with the tooltip "Insert Table (Ctrl+F12)".  It seems like it 
should be in the Insert menu too.  It used to be.

I will reply to the ticket with a screenshot.  Thanks.  -Mark

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

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

Versions of packages libreoffice-writer depends on:
ii  dpkg   1.18.10
ii  libabw-0.1-1   0.1.1-3
ii  libc6  2.23-5
ii  libe-book-0.1-10.1.2-3
ii  libetonyek-0.1-1   0.1.6-2
ii  libgcc11:6.1.1-11
ii  libicu57   57.1-3
ii  libmwaw-0.3-3  0.3.8-1
ii  libodfgen-0.1-10.1.6-1
ii  libreoffice-base-core  1:5.2.0-2
ii  libreoffice-core   1:5.2.0-2
ii  librevenge-0.0-0   0.0.4-5
ii  libstdc++6 6.1.1-11
ii  libwpd-0.10-10 0.10.1-2
ii  libwpg-0.3-3   0.3.1-2
ii  libwps-0.4-4   0.4.3-3
ii  libxml22.9.4+dfsg1-1+b1
ii  uno-libs3  5.2.0-2
ii  ure5.2.0-2
ii  zlib1g 1:1.2.8.dfsg-2+b1

Versions of packages libreoffice-writer recommends:
ii  libreoffice-math  1:5.2.0-2

Versions of packages libreoffice-writer suggests:
ii  default-jre [java5-runtime]2:1.8-57
pn  fonts-crosextra-caladea
pn  fonts-crosextra-carlito
ii  libreoffice-base   1:5.2.0-2
pn  libreoffice-gcj
ii  libreoffice-java-common1:5.2.0-2
ii  openjdk-8-jre [java5-runtime]  8u102-b14.1-2

Versions of packages libreoffice-core depends on:
ii  fontconfig2.11.0-6.7
ii  fonts-opensymbol  2:102.7+LibO5.2.0-2
ii  libboost-date-time1.61.0  1.61.0+dfsg-2.1
ii  libc6 2.23-5
ii  libcairo2 1.14.6-1+b1
ii  libclucene-contribs1v52.3.3.4-4.2
ii  libclucene-core1v52.3.3.4-4.2
ii  libcmis-0.5-5v5   0.5.1+git20160603-2
ii  libcups2  2.1.4-4
ii  libcurl3-gnutls   7.50.1-1
ii  libdbus-1-3   1.10.10-1
ii  libdbus-glib-1-2  0.106-1
ii  libdconf1 0.26.0-1
ii  libeot0   0.01-3
ii  libexpat1 2.2.0-1
ii  libexttextcat-2.0-0   3.4.4-1
ii  libfontconfig12.11.0-6.7
ii  libfreetype6  2.6.3-3+b1
ii  libgcc1   1:6.1.1-11
ii  libgl1-mesa-glx [libgl1]  11.2.2-1
ii  libglew1.13   1.13.0-2
ii  libglib2.0-0  2.48.1-3
ii  libgltf-0.0-0v5   0.0.2-4+b1
ii  libglu1-mesa [libglu1]9.0.0-2.1
ii  libgraphite2-31.3.8-1
ii  libharfbuzz-icu0  1.2.7-1+b1
ii  libharfbuzz0b 1.2.7-1+b1
ii  libhunspell-1.4-0 1.4.1-2
ii  libhyphen02.8.8-3
ii  libice6   2:1.0.9-1+b1
ii  libicu57  57.1-3
ii  libjpeg62-turbo   1:1.5.0-1
ii  liblangtag1   0.5.7-2
ii  liblcms2-22.7-1
ii  libldap-2.4-2 2.4.42+dfsg-2+b2
ii  libmythes-1.2-0   2:1.2.4-1
ii  libneon27-gnutls  0.30.1-5
ii  libnspr4  2:4.12-2
ii  libnss3   2:3.25-1
ii  libodfgen-0.1-1   0.1.6-1
ii  libpcre3  2:8.39-2
ii  libpng16-16   1.6.24-2
ii  librdf0   1.0.17-1+b1
ii  libreoffice-common1:5.2.0-2
ii  librevenge-0.0-0  0.0.4-5
ii  libsm62:1.2.2-1+b1
ii  libssl1.0.2   1.0.2h-1
ii  libstdc++66.1.1-11
ii  libx11-6  2:1.6.3-1
ii  libxext6  2:1.3.3-1
ii  libxinerama1  2:1.1.3-1+b1
ii  libxml2   2.9.4+dfsg1-1+b1
ii  libxrandr22:1.5.0-1
ii  libxrender1   1:0.9.9-2
ii  libxslt1.11.1.29-1
ii  uno-libs3 5.2.0-2
ii  ure   5.2.0-2
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages libreoffice-core recommends:
ii  libpaper-utils  1.1.24+nmu4

-- no debconf information

Bug#832103: docker.io: Can't run images after upgrading to 1.11.2~ds1-6

[Felipe Sateler]

On 31 August 2016 at 11:55, Tianon Gravi  wrote:
> On 25 July 2016 at 07:42, Felipe Sateler  wrote:
>> I had this problem too. Restarting the daemon seems to have fixed the
>> issue. I think the docker daemon should be restarted on package
>> upgrades, as most daemons do.
>
> Normally I would tend to agree, but in this case, restarting the
> daemon means that we've force-killed all the user's running
> containers, so I'm more on the fence about it.

Ack.

Anyway, isn't this a condition docker can detect (mismatch between
binaries and the running daemon)? In that case it could print a
suitable help message for the user.

-- 

Saludos,
Felipe Sateler

Bug#835353: pari: diff for NMU version 2.7.6-1.1

[gregor herrmann]

Control: tags 835353 + patch
Control: tags 835353 + pending

Dear maintainer,

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

Regards.

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Funny Van Dannen: Hallo Heimat
diff -Nru pari-2.7.6/debian/changelog pari-2.7.6/debian/changelog
--- pari-2.7.6/debian/changelog	2016-06-21 16:15:31.0 +0200
+++ pari-2.7.6/debian/changelog	2016-08-31 20:55:15.0 +0200
@@ -1,3 +1,13 @@
+pari (2.7.6-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "FTBFS with '.' removed from perl's @INC":
+add patch perl-no-dot-in-inc to call perl with "-I." for the scripts which
+use a module in the same directory.
+(Closes: #835353)
+
+ -- gregor herrmann   Wed, 31 Aug 2016 20:55:15 +0200
+
 pari (2.7.6-1) unstable; urgency=low
 
   * New upstream release
diff -Nru pari-2.7.6/debian/patches/perl-no-dot-in-inc pari-2.7.6/debian/patches/perl-no-dot-in-inc
--- pari-2.7.6/debian/patches/perl-no-dot-in-inc	1970-01-01 01:00:00.0 +0100
+++ pari-2.7.6/debian/patches/perl-no-dot-in-inc	2016-08-31 20:55:05.0 +0200
@@ -0,0 +1,37 @@
+Description: call perl with -I.
+ Perl has removed . from @INC; cf. CVE-2016-1238.
+ Various perl scripts in src/desc "use PARI::822;" which is below this
+ directory and isn't found anymore.
+ Update the relevant makefiles to add -I.
+Origin: vendor
+Bug-Debian: https://bugs.debian.org/835353
+Forwarded: no
+Author: gregor herrmann 
+Last-Update: 2016-08-31
+
+--- a/config/Makefile.SH
 b/config/Makefile.SH
+@@ -666,7 +666,7 @@
+   esac
+ HUGELINE="$HUGELINE
+ $target: $depend
+-	f=$name-$suffix; (cd $desc && \$(PERL) $script > \$\$f) && mv $desc/\$\$f \$@"
++	f=$name-$suffix; (cd $desc && \$(PERL) -I. $script > \$\$f) && mv $desc/\$\$f \$@"
+ done
+ echo "$HUGELINE" >> $file
+ 
+--- a/config/DOC_Make.SH
 b/config/DOC_Make.SH
+@@ -153,10 +153,10 @@
+ 	@-$cfg/genfunclist $desc
+ 
+ $desc/\$(DESC): $src/funclist $desc/merge_822 $desc/PARI/822.pm
+-	cd $desc && \$(PERL) merge_822 ../funclist > def\$(TMPSUF)
++	cd $desc && \$(PERL) -I. merge_822 ../funclist > def\$(TMPSUF)
+ 	mv $desc/def\$(TMPSUF) \$@
+ 
+ usersch3.tex: $desc/\$(DESC) ../src/desc/doc_make usersFUNCS.tex
+-	cd ../src/desc && \$(PERL) doc_make > ../../doc/usersch3.tex
++	cd ../src/desc && \$(PERL) -I. doc_make > ../../doc/usersch3.tex
+ EOT
+ fi
diff -Nru pari-2.7.6/debian/patches/series pari-2.7.6/debian/patches/series
--- pari-2.7.6/debian/patches/series	2015-10-26 11:21:42.0 +0100
+++ pari-2.7.6/debian/patches/series	2016-08-31 20:45:24.0 +0200
@@ -1,2 +1,3 @@
 enable_build_envvar
 perl-warning-non-fatal
+perl-no-dot-in-inc


signature.asc
Description: Digital Signature

Bug#836200: protobuf: Patch to restore New*Callback into google::protobuf namespace

[Sebastiaan Couwenberg]

On 08/31/16 15:50, Bas Couwenberg wrote:

To fix the ostinato build failure with protobuf 3.0.0 (#835435), the
attached patch is required to restore the New*Callback into the
google::protobuf namespace.

The patch was taken from the PR by Srivats P (ostinato upstream) which
should be merged into protobuf upstream soon. [0]

[0] https://github.com/google/protobuf/pull/2024


FYI: The PR has now been merged upstream:


https://github.com/google/protobuf/commit/b9649765f8e5c85523c138ac990a7523a54bfdbe

It's probably wise to not upload a new protobuf revision with this patch 
included before tomorrow when 3.0.0-6 hopefully migrates to testing:


 https://qa.debian.org/excuses.php?package=protobuf

Kind Regards,

Bas

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

Bug#836225: inkscape: no vertical scroll bars

[Mark Hedges]

Package: inkscape
Version: 0.91-9+b1
Severity: important

Hi,

The vertical scroll bar seems to have disappeared.  How do I move the page into 
view?

I will respond to the ticket with a screenshot.

Mark


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

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

Versions of packages inkscape depends on:
ii  libaspell150.60.7~20110707-3+b1
ii  libatk1.0-02.20.0-1
ii  libatkmm-1.6-1v5   2.24.2-1
ii  libc6  2.23-5
ii  libcairo2  1.14.6-1+b1
ii  libcairomm-1.0-1v5 1.12.0-1+b1
ii  libcdr-0.1-1   0.1.3-1+b1
ii  libexif12  0.6.21-2
ii  libfontconfig1 2.11.0-6.7
ii  libfreetype6   2.6.3-3+b1
ii  libgc1c2   1:7.4.2-8
ii  libgcc11:6.1.1-11
ii  libgdk-pixbuf2.0-0 2.34.0-1
ii  libglib2.0-0   2.48.1-3
ii  libglibmm-2.4-1v5  2.48.1-1
ii  libgomp1   6.1.1-11
ii  libgsl22.1+dfsg-2
ii  libgtk2.0-02.24.30-4
ii  libgtkmm-2.4-1v5   1:2.24.4-2+b1
ii  libgtkspell0   2.0.16-1.1
ii  libjpeg62-turbo1:1.5.0-1
ii  liblcms2-2 2.7-1
ii  libmagick++-6.q16-5v5  8:6.8.9.9-7.2
ii  libmagickcore-6.q16-2  8:6.8.9.9-7.2
ii  libmagickwand-6.q16-2  8:6.8.9.9-7.2
ii  libpango-1.0-0 1.40.1-1
ii  libpangocairo-1.0-01.40.1-1
ii  libpangoft2-1.0-0  1.40.1-1
ii  libpangomm-1.4-1v5 2.40.0-1
ii  libpng16-161.6.24-2
ii  libpoppler-glib8   0.44.0-3
ii  libpoppler61   0.44.0-3
ii  libpopt0   1.16-10
ii  librevenge-0.0-0   0.0.4-5
ii  libsigc++-2.0-0v5  2.8.0-2
ii  libstdc++6 6.1.1-11
ii  libvisio-0.1-1 0.1.5-1+b1
ii  libwpg-0.3-3   0.3.1-2
ii  libx11-6   2:1.6.3-1
ii  libxml22.9.4+dfsg1-1+b1
ii  libxslt1.1 1.1.29-1
pn  python:any 
ii  zlib1g 1:1.2.8.dfsg-2+b1

Versions of packages inkscape recommends:
ii  aspell0.60.7~20110707-3+b1
ii  fig2dev [transfig]1:3.2.6-2
ii  imagemagick   8:6.8.9.9-7.2
ii  libimage-magick-perl  8:6.8.9.9-7.2
ii  libwmf-bin0.2.8.4-10.5+b1
ii  python-lxml   3.6.4-1
ii  python-numpy  1:1.11.1~rc1-1
ii  transfig  1:3.2.6-2

Versions of packages inkscape suggests:
ii  dia  0.97.3-1+b1
pn  libsvg-perl  
pn  libxml-xql-perl  
pn  pstoedit 
pn  python-uniconvertor  
ii  ruby 1:2.3.0+4

-- no debconf information

Bug#836175: [buildd-tools-devel] Bug#836175: libsbuild-perl: Do not use single quotes in embedded perl script

[Samuel Thibault]

Johannes Schauer, on Wed 31 Aug 2016 20:04:42 +0200, wrote:
> Control: reassign -1 buildd 0.71.0-1
> 
> Quoting Samuel Thibault (2016-08-31 19:58:15)
> > Johannes Schauer, on Wed 31 Aug 2016 19:54:52 +0200, wrote:
> > > Where did you find documentation saying so?
> > 
> > https://wiki.debian.org/BuilddSetup
> > 
> > which supersedes the old https://buildd.debian.org/docs/buildd-setup.txt
> 
> okay, so you are not having a problem with sbuild but a problem with buildd?

Err, no, it's the sbuild command which is getting the issue. Calling
sbuild right away with not buildd around gets the same "single quote"
warning, and thus error. buildd just calls sbuild with a proper schroot
configuration, actually.

> If you want to use sbuild, then using sbuild-createchroot is the right way to
> do it as also explained in its man page.

I guess the way it creates the chroot at least historically didn't match
what a buildd needs.

Samuel

Bug#836197: Icewm doesn't find some icons

[Eduard Bloch]

Control: notfound 836197 1.3.8+mod+20160825-1

Hallo,
* Jens Stimpfle [Wed, Aug 31 2016, 01:51:32PM]:

> While some applications don't have icons under /usr/share/pixmaps,
> /usr/share/icons/hicolor/SIZE/apps/ and
> /usr/share/icons/hicolor/scalable/apps seem to be popular icon paths
> (possibly encouraged by the freedesktop spec at
> https://specifications.freedesktop.org/icon-theme-spec/icon-theme-spec-latest.html).
> Even icewm has icons there!
> 
> I'm not sure what to think of the freedesktop stuff, but maybe it's
> worth considering changing icewm to search these paths? Or should I

That is exactly what happened in the version uploaded last weekend. If
you wish to solve it quickly, edit .icewm/prefoverride and add

IconPath="/usr/share/icons/hicolor:/usr/share/icons:/usr/share/pixmaps"

Regards,
Eduard.

Bug#830534: gnome-pie doesn't start anymore

[Ghent-debian]

Hi,

I join my old config files.
   Today, I tested the old config files with the last version of 
gnome-pie 0.6.9 and no bug with them.


Kindly,
Ghent


gnome-pie.conf
Description: XML document


pies.conf
Description: XML document

Bug#834677: refcard: FTBFS in testing (xelatex compilation failed)

[victory]

On Wed, 31 Aug 2016 01:41:03 -0400
Jeremy Bicha wrote:

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

> ! I can't find file `IPAPMincho'.
> ! I can't find file `IPAPGothic'.

apparently new Depends are needed, maybe
fonts-ipafont-gothic,
fonts-ipafont-mincho,

-- 
victory
no need to CC me :-)

Bug#835809: Acknowledgement (bitcoind: Blockchain needs 87+ GB of space, not 20+)

[Diederik de Haas]

> You might want to look into the "pruning" feature, that allows you to
> run bitcoind with as little as a few gigabytes.

Thanks, will do. 

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

Bug#835871: Pending fixes for bugs in the libdevel-cover-perl package

[pkg-perl-maintainers]

tag 835871 + pending
thanks

Some bugs in the libdevel-cover-perl package are closed in revision
549aab983c35263463bebae001ad99a92836c8f6 in branch 'master' by gregor
herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libdevel-cover-perl.git/commit/?id=549aab9

Commit message:

Add patch to make build reproducible.

Thanks: Chris Lamb for the bug report and the patch.
Closes: #835871

Bug#836175: [buildd-tools-devel] Bug#836175: libsbuild-perl: Do not use single quotes in embedded perl script

[Johannes Schauer]

Control: reassign -1 buildd 0.71.0-1

Quoting Samuel Thibault (2016-08-31 19:58:15)
> Johannes Schauer, on Wed 31 Aug 2016 19:54:52 +0200, wrote:
> > Where did you find documentation saying so?
> 
> https://wiki.debian.org/BuilddSetup
> 
> which supersedes the old https://buildd.debian.org/docs/buildd-setup.txt

okay, so you are not having a problem with sbuild but a problem with buildd?

Disclaimer: I have *no idea* about the buildd part of sbuild. This is yet
another reason why I do not touch these scripts. If you want to use buildd,
then somebody else has to help you.

If you want to use sbuild, then using sbuild-createchroot is the right way to
do it as also explained in its man page.

Of course, if you find this bug in sbuild, then I'd be happy to fix it.

Thanks!

cheers, josch


signature.asc
Description: signature

Bug#836221: isenkram: Needs to be ported to AppStream 0.10

[Petter Reinholdtsen]

[Matthias Klumpp]
> Hi!
> The latest AppStream release changed its API.
> Please apply the attached patch to make Isenkram work with the AppStream
> version in unstable.

Thanks.  What kind of versioned dependency should the package get?

-- 
Vennlig hilsen
Petter Reinholdtsen

Bug#836224: gnome-shell-extension-taskbar: Please set dependency relationship for gnome-shell versions

[Jeremy Bicha]

Package: gnome-shell-extension-taskbar
Version: 52.0-2

gnome-shell-extension-taskbar should depend on specific gnome-shell
versions. Something like

 gnome-shell (>= 3.10),
 gnome-shell (<< 3.23),

Also, since gnome-shell 3.22 will be released soon (and 3.21.90 is
already in unstable), I recommend including 3.22 in the extension's
metadata.json.

Thanks,
Jeremy Bicha

Bug#836175: [buildd-tools-devel] Bug#836175: libsbuild-perl: Do not use single quotes in embedded perl script

[Samuel Thibault]

Johannes Schauer, on Wed 31 Aug 2016 19:54:52 +0200, wrote:
> Quoting Samuel Thibault (2016-08-31 19:53:19)
> > Johannes Schauer, on Wed 31 Aug 2016 19:49:27 +0200, wrote:
> > > Quoting Samuel Thibault (2016-08-31 19:33:27)
> > > > Johannes Schauer, on Wed 31 Aug 2016 19:29:47 +0200, wrote:
> > > > > Did you not create your chroot with sbuild-createchroot?
> > > > 
> > > > I use /usr/share/sbuild/create-chroot, which does not seem to use
> > > > sbuild-createchroot
> > > 
> > > how did you find that script?
> > 
> > AIUI it's the documented way to create a buildd.
> 
> that's why I'm asking how you found it.
> 
> Where did you find documentation saying so?

https://wiki.debian.org/BuilddSetup

which supersedes the old https://buildd.debian.org/docs/buildd-setup.txt

Samuel

Bug#836052: tj3man unable to open manual index page

[Vincent Bernat]

 ❦ 31 août 2016 19:44 CEST, Christopher Hoskin  :

> Hopefully the attached is what you meant?

Yes. Thanks! I have uploaded the result.
-- 
Format a program to help the reader understand it.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature

Bug#836175: [buildd-tools-devel] Bug#836175: libsbuild-perl: Do not use single quotes in embedded perl script

[Samuel Thibault]

Johannes Schauer, on Wed 31 Aug 2016 19:49:27 +0200, wrote:
> Quoting Samuel Thibault (2016-08-31 19:33:27)
> > Johannes Schauer, on Wed 31 Aug 2016 19:29:47 +0200, wrote:
> > > Did you not create your chroot with sbuild-createchroot?
> > 
> > I use /usr/share/sbuild/create-chroot, which does not seem to use
> > sbuild-createchroot
> 
> how did you find that script?

AIUI it's the documented way to create a buildd.

> > Well, with the proposed patch it works just fine :)
> 
> It will. But the question is: is it the right fix for the problem?
> 
> An alternative solution would be to remove the single quote handling from
> lib/Sbuild/ChrootPlain.pm and lib/Sbuild/ChrootSudo.pm.

Ok.

Samuel

Bug#836175: [buildd-tools-devel] Bug#836175: libsbuild-perl: Do not use single quotes in embedded perl script

[Johannes Schauer]

Hi,

Quoting Samuel Thibault (2016-08-31 19:53:19)
> Johannes Schauer, on Wed 31 Aug 2016 19:49:27 +0200, wrote:
> > Quoting Samuel Thibault (2016-08-31 19:33:27)
> > > Johannes Schauer, on Wed 31 Aug 2016 19:29:47 +0200, wrote:
> > > > Did you not create your chroot with sbuild-createchroot?
> > > 
> > > I use /usr/share/sbuild/create-chroot, which does not seem to use
> > > sbuild-createchroot
> > 
> > how did you find that script?
> 
> AIUI it's the documented way to create a buildd.

that's why I'm asking how you found it.

Where did you find documentation saying so?

Thanks!

cheers, josch


signature.asc
Description: signature

Bug#836175: [buildd-tools-devel] Bug#836175: libsbuild-perl: Do not use single quotes in embedded perl script

[Johannes Schauer]

Hi,

Quoting Samuel Thibault (2016-08-31 19:33:27)
> Johannes Schauer, on Wed 31 Aug 2016 19:29:47 +0200, wrote:
> > Did you not create your chroot with sbuild-createchroot?
> 
> I use /usr/share/sbuild/create-chroot, which does not seem to use
> sbuild-createchroot

how did you find that script? In contrast to sbuild-createchroot it is not even
in $PATH. Also the sbuild man page refers to sbuild-createchroot and not the
create-chroot script. I was not aware that anybody was using it.

I only recently (one year ago) took over sbuild maintenance and lots of bits
only seem to be of historic interest to me. But I didn't remove them yet
because I don't know if somebody still relies on them.

It seems to be doing a very similar job to sbuild-createchroot. For example it
seems to also set up schroot. Have a look into your /etc/schroot/chroot.d/.

> > It is not unlikely that the support for sudo-type chroots in sbuild is
> > broken.  I don't think anybody is using those anymore. If it turns out that
> > you are still for some reason using the sudo backend, then I would like to
> > help you investigate how to best fix it.
> 
> Well, with the proposed patch it works just fine :)

It will. But the question is: is it the right fix for the problem?

An alternative solution would be to remove the single quote handling from
lib/Sbuild/ChrootPlain.pm and lib/Sbuild/ChrootSudo.pm.

Thanks!

cheers, josch


signature.asc
Description: signature

Bug#836052: tj3man unable to open manual index page

[Christopher Hoskin]

Package: tj3
Version: 3.6.0-2
Followup-For: Bug #836052

Dear Vincent,

Hopefully the attached is what you meant?

Thanks for your help.

Christopher
>From 368be815aac6d09839cf347a526a09b0beec5de9 Mon Sep 17 00:00:00 2001
From: Christopher Hoskin 
Date: Wed, 31 Aug 2016 13:48:58 +0100
Subject: [PATCH] Add manual-path.patch to use Debian path for manual

---
 debian/changelog |  8 
 debian/patches/manual-path.patch | 21 +
 debian/patches/series|  1 +
 3 files changed, 30 insertions(+)
 create mode 100644 debian/patches/manual-path.patch

diff --git a/debian/changelog b/debian/changelog
index 14ba371..797fe57 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+tj3 (3.6.0-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "tj3man unable to open manual index page" Added manual-path.patch to 
++change path used to locate manual index page. (Closes: #836052)
+
+ -- Christopher Hoskin   Wed, 31 Aug 2016 18:33:39 +0100
+
 tj3 (3.6.0-2) unstable; urgency=medium
 
   * d/copyright: change GFDL short name to GFDL-NIV. Thanks to Christopher
diff --git a/debian/patches/manual-path.patch b/debian/patches/manual-path.patch
new file mode 100644
index 000..68a5624
--- /dev/null
+++ b/debian/patches/manual-path.patch
@@ -0,0 +1,21 @@
+Description: Use Debian path for manual
+ Changes the path used by tj3man to find the user manual index.html file from
+ one relative to the binary to the absolute path /usr/share/doc/tj3/html/ used
+ by Debian
+Bug-Debian: 836052
+Forwarded: not-needed
+Author: Christopher Hoskin 
+Last-Update: 2016-08-31
+
+--- a/lib/taskjuggler/apps/Tj3Man.rb
 b/lib/taskjuggler/apps/Tj3Man.rb
+@@ -106,8 +106,7 @@
+ # specified keyword.
+ def startBrowser(keyword = nil)
+   # Find the manual relative to this file.
+-  manualDir = File.join(File.dirname(__FILE__), '..', '..', '..',
+-'manual', 'html')
++  manualDir = '/usr/share/doc/tj3/html/'
+   file = "#{manualDir}/#{keyword || 'index'}.html"
+   # Make sure the file exists.
+   unless File.exist?(file)
diff --git a/debian/patches/series b/debian/patches/series
index f43594f..f714ea8 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,3 +1,4 @@
 dont-require-git.patch
 data-search-dirs-debian.patch
 reproducible-build.patch
+manual-path.patch
\ No newline at end of file
-- 
2.9.3

Bug#835472: Gajim 0.16.5-2 crashed after update on startup

[W. Martin Borgert]

Why is demandimport used in the first place?

If I understand correctly, this function is useful for
command line tools, so that they have a fast startup.

But long running GUI programs or servers have no
advantage from using demandimport, or am I wrong?

Why not just remove (use of) demandimport from Gajim
and its plugins? Am I missing something?

Bug#782075: gnome-tweak-tool: Crashes Gnome when reducing Number of Workspaces

[Jens Reyer]

Control: found -1 3.21.91-1

Hi Andreas

I updated my system as requested (had to uninstall the gnome metapackage
and some extensions).

I can still reproduce this for my regular user with mutter/gnome-shell
3.21.91-1, see attachment. All extensions were disabled.

However it now works for a fresh user. Note that in the past I could
reproduce this on two machines, even for fresh users, see buglog.

At least GNOME now (at least since 3.20) doesn't disable all extensions
automatically anymore after a crash :)

Greets
jre
. xenv.sh
jens@hope:~$ gdb --args /usr/bin/gnome-shell --replace
GNU gdb (Debian 7.11.1-2) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/gnome-shell...Reading symbols from 
/usr/lib/debug/.build-id/78/afdb18f04b732ec496f2beb1489f0c899b0a41.debug...done.
done.
(gdb) run
Starting program: /usr/bin/gnome-shell --replace
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffdfaf1700 (LWP 4728)]
[New Thread 0x7fffdd0fe700 (LWP 4743)]
[New Thread 0x7fffdc8fd700 (LWP 4744)]
[New Thread 0x7fffcfdf2700 (LWP 4745)]
[New Thread 0x7fffcf3e9700 (LWP 4748)]
[New Thread 0x7fffcebe8700 (LWP 4749)]
[New Thread 0x7fffce3e7700 (LWP 4750)]
Gjs-Message: JS LOG: Failed to launch ibus-daemon: Failed to execute 
child process "ibus-daemon" (No such file or directory)
Gjs-Message: JS LOG: Failed to add search provider 
/usr/share/gnome-shell/search-providers/org.gnome.bijiben-search-provider.ini: 
TypeError: appInfo is null
[New Thread 0x7fffabfff700 (LWP 4760)]
[New Thread 0x7fffaaf33700 (LWP 4766)]
[Thread 0x7fffdc8fd700 (LWP 4744) exited]
[Thread 0x7fffabfff700 (LWP 4760) exited]
[New Thread 0x7fffabfff700 (LWP 4768)]
[New Thread 0x7fffdc8fd700 (LWP 4769)]
[New Thread 0x7fffa8b9c700 (LWP 4770)]
[New Thread 0x7fff9fffe700 (LWP 4771)]
[New Thread 0x7fff9f7fd700 (LWP 4772)]
[New Thread 0x7fff9effc700 (LWP 4773)]
[Thread 0x7fff9effc700 (LWP 4773) exited]
[Thread 0x7fffa8b9c700 (LWP 4770) exited]
[Thread 0x7fffaaf33700 (LWP 4766) exited]
[Thread 0x7fff9fffe700 (LWP 4771) exited]
[New Thread 0x7fff9fffe700 (LWP 4801)]
[New Thread 0x7fffaaf33700 (LWP 4802)]
[New Thread 0x7fffa8b9c700 (LWP 4803)]
[New Thread 0x7fff9effc700 (LWP 4804)]
[New Thread 0x7fff9e7fb700 (LWP 4805)]
[Thread 0x7fff9e7fb700 (LWP 4805) exited]
[Thread 0x7fff9effc700 (LWP 4804) exited]
[Thread 0x7fffa8b9c700 (LWP 4803) exited]
[Thread 0x7fffaaf33700 (LWP 4802) exited]
[Thread 0x7fff9f7fd700 (LWP 4772) exited]
[Thread 0x7fffdc8fd700 (LWP 4769) exited]
[Thread 0x7fff9fffe700 (LWP 4801) exited]
**
mutter:ERROR:core/screen.c:1206:update_num_workspaces: assertion failed: 
(w->windows == NULL)

Thread 1 "gnome-shell" received signal SIGABRT, Aborted.
0x74a03198 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:54
54  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) t a a bt

Thread 11 (Thread 0x7fffabfff700 (LWP 4768)):
#0  0x74ab2d49 in syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7501df7a in g_cond_wait_until (cond=cond@entry=0x88a248, 
mutex=mutex@entry=0x88a240, end_time=end_time@entry=227780230) at 
././glib/gthread-posix.c:1442
#2  0x74face39 in g_async_queue_pop_intern_unlocked 
(queue=queue@entry=0x88a240, wait=wait@entry=1, 
end_time=end_time@entry=227780230) at ././glib/gasyncqueue.c:422
#3  0x74fad45c in g_async_queue_timeout_pop (queue=0x88a240, 
timeout=timeout@entry=1500) at ././glib/gasyncqueue.c:543
#4  0x750009cd in g_thread_pool_thread_proxy () at 
././glib/gthreadpool.c:167
#5  0x750009cd in g_thread_pool_thread_proxy (data=) at 
././glib/gthreadpool.c:364
#6  0x7405 in g_thread_proxy (data=0x2c16450) at 
././glib/gthread.c:784
#7  0x74d78444 in start_thread (arg=0x7fffabfff700) at 
pthread_create.c:333
#8  0x74ab720d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 0x7fffce3e7700 (LWP 4750)):
#0  0x74d7e07f in pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fffe6582d70 in PR_WaitCondVar (cvar=0x9c6eb0, 
timeout=timeout@entry=4294967295) at ptsynch.c:396
#2  0x706d0536 in